public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
To: Nathan Scott <nathans@sgi.com>
Cc: Manuel Reimer <Manuel.Spam@nurfuerspam.de>, linux-kernel@vger.kernel.org
Subject: Re: Is XFS trustworthy in the latest 2.6.16
Date: Tue, 08 Aug 2006 04:00:21 -0500	[thread overview]
Message-ID: <44D852A5.3080008@mnsu.edu> (raw)
In-Reply-To: <20060808185017.A2528231@wobbly.melbourne.sgi.com>

Nathan Scott wrote:
> 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.
>
>   
>> 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+.
>
> cheers.
>
>   

If you have run 2.6.17 to 2.6.17.6 or early 2.6.18-rc? however; please 
run a xfs_repair v.2.6.10; because the corruption may/will have already 
taken place and a silent time bomb may be waiting.  Three machines 
already died with symptom of the corruption on kernels that no longer 
have the problem.

-- 
Jeffrey Hundstad




  reply	other threads:[~2006-08-08  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-08  7:34 Is XFS trustworthy in the latest 2.6.16 Manuel Reimer
2006-08-08  8:50 ` Nathan Scott
2006-08-08  9:00   ` Jeffrey Hundstad [this message]
2006-08-08  9:34   ` Manuel Reimer
2006-08-08 10:10     ` Nathan Scott

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=44D852A5.3080008@mnsu.edu \
    --to=jeffrey.hundstad@mnsu.edu \
    --cc=Manuel.Spam@nurfuerspam.de \
    --cc=linux-kernel@vger.kernel.org \
    --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