From: Nathan Scott <nathans@sgi.com>
To: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is XFS trustworthy in the latest 2.6.16
Date: Tue, 8 Aug 2006 20:10:25 +1000 [thread overview]
Message-ID: <20060808201025.A2536447@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <eb9lp9$3h2$1@sea.gmane.org>; from Manuel.Spam@nurfuerspam.de on Tue, Aug 08, 2006 at 11:34:10AM +0200
On Tue, Aug 08, 2006 at 11:34:10AM +0200, Manuel Reimer wrote:
> Nathan Scott schrieb:
> > On Tue, Aug 08, 2006 at 09:34:48AM +0200, Manuel Reimer wrote:
> >> Hello,
> >>
> >> could someone please tell me if XFS is trustworthy in the latest 2.6.16?
> >> There have been some bugs:
> >>
> >> http://bugzilla.kernel.org/show_bug.cgi?id=6380
> >> http://bugzilla.kernel.org/show_bug.cgi?id=6757
> >
> > These are the same problem. 2.6.16 is unaffected.
>
> But the bug has been filed for 2.6.16.4.
Indeed, once the corruption exists ondisk all kernels will detect it.
Read through the entire bug, many details come toward the end.
> Did you want to say, that the latest 2.6.16 is unaffected?
All 2.6.16's are unaffected.
> >> want a stable kernel and 2.6.16 seems to fit all my needs.
> >
> > For XFS, its goodness. 2.6.18 will be good too, and 2.6.17.7+.
>
> What exactly did you want to tell with this sentence. Sorry, but my
> native language is german...
Sorry, I meant to say "theres nothing wrong with 2.6.16".
> Is it a good solution to stay on the 2.6.16 branch? Of course I could
Yes, thats fine.
cheers.
--
Nathan
prev parent reply other threads:[~2006-08-08 10:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 7:34 Manuel Reimer
2006-08-08 8:50 ` Nathan Scott
2006-08-08 9:00 ` Jeffrey Hundstad
2006-08-08 9:34 ` Manuel Reimer
2006-08-08 10:10 ` Nathan Scott [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=20060808201025.A2536447@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=Manuel.Spam@nurfuerspam.de \
--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
all inboxes | Powered by JetHome®