From: Andi Kleen <ak@suse.de>
To: okir@suse.de
Cc: neilb@suse.de, trond.myklebust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: LTP NFS data corruption in 2.6.15-git9 II
Date: Fri, 13 Jan 2006 21:38:43 +0100 [thread overview]
Message-ID: <200601132138.43460.ak@suse.de> (raw)
In-Reply-To: <200601132137.10615.ak@suse.de>
On Friday 13 January 2006 21:37, Andi Kleen wrote:
>
> FWIW - i was just running LTP- for 2.6.15-git9 on a x86-64 nfs root machine
> talking to 2.6.15 machine with NFSv3/UDP. During the IO tests I got
> this. Export was with rw,async.
>
> The network was 100 GBit/s so I wouldn't assume it was caused by
> fragment reordering [Why UDP? That is what the kernel nfs root
> mounter selected]
>
> To reproduce just run LTP 20051103 runltp over NFS.
As a followup the test machine got a lot of
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
do_vfs_lock: VFS is out of sync with lock manager!
messages after the test.
-Andi
-------------------------------------------------------
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
prev parent reply other threads:[~2006-01-13 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 20:37 LTP NFS data corruption in 2.6.15-git9 Andi Kleen
2006-01-13 20:38 ` Andi Kleen [this message]
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=200601132138.43460.ak@suse.de \
--to=ak@suse.de \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
--cc=trond.myklebust@fys.uio.no \
/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.