From: Peter Staubach <staubach@redhat.com>
To: Roger Heflin <rheflin@atipa.com>
Cc: "'Lever, Charles'" <Charles.Lever@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: mtime not updated in client cache?
Date: Fri, 09 Dec 2005 16:05:29 -0500 [thread overview]
Message-ID: <4399F199.60500@redhat.com> (raw)
In-Reply-To: <EXCHG2003JY4kJSFsxf000003dd@EXCHG2003.microtech-ks.com>
Roger Heflin wrote:
>
>
>
>
>>-----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.
>
Right. But the difference is that these things are visible on the system.
The user can know that there may be a problem. If such a thing happens on
the NFS server, without the client's knowledge, then there is no way of
telling why the data is not there, just that it is not.
Thanx...
ps
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-12-09 21:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 19:07 mtime not updated in client cache? Lever, Charles
2005-12-09 19:20 ` Peter Staubach
2005-12-09 19:55 ` Roger Heflin
2005-12-09 21:05 ` Peter Staubach [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-09 15:56 Lever, Charles
2005-12-09 16:10 ` Trond Myklebust
2005-12-09 16:40 ` Peter Staubach
2005-11-29 0:09 Vince Busam
2005-11-29 0:45 ` Trond Myklebust
2005-12-01 1:06 ` Vince Busam
2005-12-01 1:15 ` Trond Myklebust
2005-12-08 1:22 ` Vince Busam
2005-12-08 3:38 ` Trond Myklebust
2005-12-09 14:06 ` Peter Staubach
2005-12-09 14:16 ` Trond Myklebust
2005-12-09 14:24 ` Peter Staubach
2005-12-09 15:19 ` Trond Myklebust
2005-12-13 1:51 ` Vince Busam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4399F199.60500@redhat.com \
--to=staubach@redhat.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=rheflin@atipa.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.