From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Heflin, Roger A." <Roger.A.Heflin@conocophillips.com>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: Stale mounts - very nasty
Date: 14 May 2003 17:29:07 +0200 [thread overview]
Message-ID: <shshe7xbl8c.fsf@charged.uio.no> (raw)
In-Reply-To: <5CA6F03EF05E0046AC5594562398B916A32939@POEXMB3.conoco.net>
>>>>> " " == Roger A Heflin <Heflin> writes:
> Guys, I have one of these, where it went into this state in the
> middle of a copy, ie part of the a file got copied and then the
> nfs partition when into this broken state, all with the server
> doing nothing bad.
> And I have now confirmed that it does it against Sun Solaris 8
> servers, which makes it look like a client problem, and not a
> server problem.
Mind showing us a tcpdump of a copy that fails? I don't buy that
'server doing nothing bad' theory without proof.
Under a reboot, the server may indeed use ESTALE to deny access to
files. Normally you ensure that this doesn't happen by killing nfsd
before you unexport the mounts, and by re-exporting before you start
nfsd (see the NFS list archives about the 'exportfs' ordering bugs in
older versions of nfs-utils).
If the server does return ESTALE, then the client is perfectly correct
in assuming that is a fatal error.
Cheers,
Trond
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-05-14 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 14:04 Stale mounts - very nasty Heflin, Roger A.
2003-05-14 15:29 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-14 16:27 Heflin, Roger A.
2003-05-14 17:05 ` Trond Myklebust
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=shshe7xbl8c.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=Roger.A.Heflin@conocophillips.com \
--cc=nfs@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox