From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Marcelo Leal
<diversos-roWltSPQdMkZWYhx5MAOMFAUjnlXr6A1@public.gmane.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Chris Fanning <christopher.fanning@gmail.com>,
nfs@lists.sourceforge.net
Subject: Re: [NFS] async vs. sync. corrupted fs
Date: Tue, 20 May 2008 12:27:53 -0400 [thread overview]
Message-ID: <1211300873.14155.12.camel@localhost> (raw)
In-Reply-To: <42996ba90805200705o49b4a17bn62cc9962bbcac8b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Tue, 2008-05-20 at 11:05 -0300, Marcelo Leal wrote:
> We already saw xfs filesystem full and NFS server (2.4 kernel),
> produce a disc corruption (partition table goes away).
> But believe me, not in the full disc, but in another one (we can
> reproduce). Always the same disc is corrupted (the first one i guess).
That would be an XFS bug. Have you reported it?
Trond
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
_______________________________________________
Please note that nfs@lists.sourceforge.net is being discontinued.
Please subscribe to linux-nfs@vger.kernel.org instead.
http://vger.kernel.org/vger-lists.html#linux-nfs
next prev parent reply other threads:[~2008-05-20 16:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 10:55 [NFS] async vs. sync. corrupted fs Chris Fanning
[not found] ` <215ff4410805160355x25b8d055x9a0a246aa5875482-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-19 14:54 ` J. Bruce Fields
2008-05-20 8:00 ` Chris Fanning
[not found] ` <215ff4410805200100o20fb83bcm9921127efef27ef9-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-20 13:01 ` Trond Myklebust
2008-05-20 14:05 ` Marcelo Leal
[not found] ` <42996ba90805200705o49b4a17bn62cc9962bbcac8b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-05-20 16:27 ` Trond Myklebust [this message]
2008-05-20 18:56 ` Marcelo Leal
[not found] ` <215ff4410805200100o20fb83bcm9921127efef27ef9-JsoAwUIsXouhRSP0FMvGiw@public.gmane.org m>
2008-05-20 13:36 ` Talpey, Thomas
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=1211300873.14155.12.camel@localhost \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=christopher.fanning@gmail.com \
--cc=diversos-roWltSPQdMkZWYhx5MAOMFAUjnlXr6A1@public.gmane.org \
--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