public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ram@ram.fr.eu.org (Raphael Manfredi)
To: linux-kernel@vger.kernel.org
Subject: 2.4.3-ac9/4 - NFS corruption
Date: 1 May 2001 13:21:25 GMT	[thread overview]
Message-ID: <9cmd8l$s38$1@lyon.ram.loc> (raw)

My NFS client runs 2.4.3-ac4 (SMP).
My NFS server uses user-land NFS and runs 2.4.3-ac9 (UP).

I've seens the following in my ~/mail/inbox, NFS mounted:

	^@^@^@^@^@^@est-admin@lists.sourceforge.net  Tue May  1 14:47:02 2001

On the server, the same line reads:

	From test-admin@lists.sourceforge.net  Tue May  1 14:47:02 2001

The above "^@" are NULL bytes, as displayed by "vi".
The data around those NULL bytes were perfect, i.e. there was text before
in the mailbox that was correct.

An "ls -l" on the file yields:

	-rw-------    1 ram      users     1642491 May  1 00:00 inbox

(on the server, and via NFS), which is *abnormal*, since it's 15:18 and
I've just updated the file.  Therfore, the timestamp is corrupted as well
in the inode.

If I create a file, via "> ~/mail/test" on NFS, it reads:

	-rw-r--r--    1 ram      users           0 May  1 15:19 test

with a proper timestamp.

The NFS access is done via a symlink to an NFS-mounted dir, i.e. ~/mail
is actually a symlink to /nfs/lyon/home/ram/mail.

Any hint as to what is happening?  Is that a known problem?

Raphael

             reply	other threads:[~2001-05-01 13:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01 13:21 Raphael Manfredi [this message]
2001-05-01 17:41 ` 2.4.3-ac9/4 - NFS corruption Trond Myklebust
2001-05-02  4:29   ` Raphael Manfredi
2001-05-02 11:24     ` 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='9cmd8l$s38$1@lyon.ram.loc' \
    --to=ram@ram.fr.eu.org \
    --cc=linux-kernel@vger.kernel.org \
    /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