From: Tom McNeal <trmcneal@attbi.com>
To: "Bryan J. Smith" <b.j.smith@ieee.org>
Cc: Daniel Forrest <forrest@lmcg.wisc.edu>,
Alan Witz <awitz@magstarinc.com>,
nfs@lists.sourceforge.net
Subject: Re: Corrupt Data when using NFS on Linux -- This should be in the HOWTO
Date: Tue, 29 Oct 2002 10:07:48 -0800 [thread overview]
Message-ID: <3DBECE74.506@attbi.com> (raw)
In-Reply-To: 1035912013.3dbec34dddd7e@webmail.smithconcepts.com
Its easier with the FAQ, but the HOWTO might be the better place.
We'll take a look at it...
Tom
Bryan J. Smith wrote:
> Quoting Daniel Forrest <forrest@lmcg.wisc.edu>:
>
>>The "guaranteed" way to create a lock file over NFS:
>> create tempfile
>> link tempfile lockfile (ignore return code)
>> stat tempfile
>>If the link count is 2, then you have the lock file. Apparently, link
>>may return success even if the link failed or return failure even if
>>the link succeeded (I don't remember which). Doing the stat verifies
>>if you have actually created a link to the temporary file.
>>
>
> I know the HOWTO is more for users/sysadmins, but stuff like this could really
> help in an additional "common workarounds for potential gotchas" section at the
> end of the HOWTO.
>
>
--
------------------------------------------------------------------------
Tom McNeal trmcneal@attbi.com (650)906-0761 (cell)
------------------------------------------------------------------------
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-10-29 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 20:48 Corrupt Data when using NFS on Linux Lever, Charles
2002-10-28 23:05 ` Alan Witz
2002-10-29 1:34 ` Eff Norwood
2002-10-29 17:03 ` Daniel Forrest
2002-10-29 17:20 ` Corrupt Data when using NFS on Linux -- This should be in the HOWTO Bryan J. Smith
2002-10-29 18:07 ` Tom McNeal [this message]
2002-10-29 18:23 ` Bryan J. Smith
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=3DBECE74.506@attbi.com \
--to=trmcneal@attbi.com \
--cc=awitz@magstarinc.com \
--cc=b.j.smith@ieee.org \
--cc=forrest@lmcg.wisc.edu \
--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