mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Christian Kujau <evil@g-house.de>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS breakage in 2.6.18-rc1
Date: Mon, 24 Jul 2006 09:01:38 +1000	[thread overview]
Message-ID: <20060724090138.C2083275@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607221722500.8407@prinz64.housecafe.de>; from evil@g-house.de on Sat, Jul 22, 2006 at 05:27:24PM +0100

On Sat, Jul 22, 2006 at 05:27:24PM +0100, Christian Kujau wrote:
> On Wed, 19 Jul 2006, Nathan Scott wrote:
> > 2.6.18-rc1 should be fine (contains the corruption fix).  Did you
> > mkfs and restore?  Or at least get a full repair run?  If you did,
> > and you still see issues in .18-rc1, please let me know asap.
> 
> well, at least for me, corruption/errors *started* with 2.6.18-rc1:
> ...
> I downgraded to 2.6.17.5 and the errors stopped. Now I've upgraded to 
> 2.6.18-rc2 and see the same errors:
> 
> xfs_da_do_buf: bno 16777216
> dir: inode 24472381

This is an ondisk corruption - downgrading the kernel will not
resolve it.  The problem must be triggered by a combination of
operations on a directory; I'm certain that if you access inode
24472381 on your filesystem on 2.6.17, that it'll shutdown your
filesystem too.  See the FAQ entry for a description on how to
translate inums to paths, and also the repair -n step to detect
any corruption ondisk.

cheers.

-- 
Nathan

  reply	other threads:[~2006-07-23 23:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 22:29 Torsten Landschoff
2006-07-18 22:57 ` Nathan Scott
2006-07-19  8:08   ` Alistair John Strachan
2006-07-19 22:56     ` Nathan Scott
2006-07-20 10:29       ` Kasper Sandberg
2006-07-19 10:21   ` Kasper Sandberg
2006-07-19 12:43     ` Alistair John Strachan
2006-07-19 15:25       ` Kasper Sandberg
2006-07-19 22:59     ` Nathan Scott
2006-07-20  7:13     ` FAQ updated (was Re: XFS breakage...) Nathan Scott
2006-07-20 12:42       ` Hans-Peter Jansen
2006-07-20 13:28       ` David Greaves
2006-07-20 16:11         ` Chris Wedgwood
2006-07-20 22:14           ` Nathan Scott
2006-07-20 22:18             ` Justin Piszcz
2006-07-20 22:24               ` Nathan Scott
2006-07-20 22:43                 ` Justin Piszcz
2006-07-20 22:52                   ` Nathan Scott
2006-07-20 22:55                     ` Justin Piszcz
2006-07-20 22:57                       ` Justin Piszcz
2006-07-20 23:00                       ` Nathan Scott
2006-07-20 23:10                         ` Justin Piszcz
2006-07-20 23:12                           ` Chris Wedgwood
2006-07-20 23:15                             ` Justin Piszcz
2006-07-20 23:19                             ` Nathan Scott
2006-07-20 15:13       ` Kevin Radloff
2006-07-20 16:51         ` Alistair John Strachan
2006-07-31 16:25       ` Jan Kasprzak
2006-07-31 16:38         ` Justin Piszcz
2006-08-02  4:32         ` Nathan Scott
2006-07-19 21:14   ` XFS breakage in 2.6.18-rc1 Torsten Landschoff
2006-07-19 23:09     ` Nathan Scott
2006-07-22 16:27   ` Christian Kujau
2006-07-23 23:01     ` Nathan Scott [this message]
2006-07-28 17:01       ` Christian Kujau
2006-07-28 21:48         ` Nathan Scott
2006-07-29 20:22           ` Ralf Hildebrandt
2006-07-29 22:28             ` David Chatterton
2006-07-18 23:06 ` Kevin Radloff
2006-07-19 14:17 Mattias Hedenskog
2006-07-19 14:59 ` Jeffrey E. Hundstad
2006-07-19 23:01   ` Nathan Scott
2006-07-20  5:51     ` Jeffrey Hundstad
2006-07-19 21:09 ` Torsten Landschoff
2006-07-20 10:46   ` Jan Engelhardt

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=20060724090138.C2083275@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.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

all inboxes | Powered by JetHome®