From: Walt H <waltabbyh@comcast.net>
To: Nathan Scott <nathans@sgi.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Linux XFS Mailing List <linux-xfs@oss.sgi.com>
Subject: Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?)
Date: Sun, 21 Sep 2003 18:28:34 -0700 [thread overview]
Message-ID: <3F6E5042.40502@comcast.net> (raw)
In-Reply-To: <20030922011241.GA1043@frodo>
Nathan Scott wrote:
> The fix is below, I'd be interested in whether or not you still have
> problems after applying this.
>
> thanks.
>
That appears to have cleared it up. I tried the tests I discovered in my
earlier e-mail of creating bogus lost+found etc... and couldn't get the
filesystem to fail. Mind you, I only ran an rsync over a 2GB filesystem,
but previously the problem was exhibited 100% of the time. I'll bang on
this for a while. Hopefully you don't hear back from me right away :)
Thanks,
-Walt
prev parent reply other threads:[~2003-09-22 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-21 15:47 2.6.0-test5-mm3 & XFS FS Corruption Walt H
2003-09-21 18:08 ` 2.6.0-test5-mm3 & XFS FS Corruption (or not?) Walt H
2003-09-21 19:48 ` Steve Lord
2003-09-22 1:01 ` Walt H
2003-09-22 1:12 ` Nathan Scott
2003-09-22 1:28 ` Walt H [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=3F6E5042.40502@comcast.net \
--to=waltabbyh@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
--cc=nathans@sgi.com \
/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