RE: mtime not updated in client cache?

["Roger Heflin" <rheflin@atipa.com>]

 

> -----Original Message-----
> From: nfs-admin@lists.sourceforge.net 
> [mailto:nfs-admin@lists.sourceforge.net] On Behalf Of Peter Staubach
> Sent: Friday, December 09, 2005 1:20 PM
> To: Lever, Charles
> Cc: nfs@lists.sourceforge.net
> Subject: Re: [NFS] mtime not updated in client cache?
> 
> Lever, Charles wrote:
> 
> >
> >risks understood.
> >
> >however, how is this different from ext3?  a close() on an ext3 file 
> >doesn't even attempt to schedule a flush of the data to 
> disk.  if the 
> >system crashes or the disk dies or the file system fills up, 
> the data 
> >is lost, just like in the NFS case.
> >  
> >
> 
> I think that the difference is that a system crash also 
> terminates the application and there is just more visibility 
> into what happened.

On a local machine, the application can complete successfully, 
and the data won't be written out for up to 30 seconds, and this
can be higher on machines that have huge amounts of ram, and can
hold a lot more in its write cache, so data can be
lost even after the program completes properly if the machine crashes
before the writes are finished.

If you get a hard scsi/disk error when writing data from local cache, there
is not a process to return that error to the program that generated
the data assuming that the program is even still running.

                           Roger



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs