All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Nathan Scott <nathans@sgi.com>
Cc: Torsten Landschoff <torsten@debian.org>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS breakage in 2.6.18-rc1
Date: Wed, 19 Jul 2006 12:21:08 +0200	[thread overview]
Message-ID: <1153304468.3706.4.camel@localhost> (raw)
In-Reply-To: <20060719085731.C1935136@wobbly.melbourne.sgi.com>

On Wed, 2006-07-19 at 08:57 +1000, Nathan Scott wrote:
> On Wed, Jul 19, 2006 at 12:29:41AM +0200, Torsten Landschoff wrote:
> > Hi friends, 
> 
> Hi Torsten,
> 
> > I upgraded to 2.6.18-rc1 on sunday, with the following results (taken
> > from my /var/log/kern.log), which ultimately led me to reinstall my 
> > system:
> > 
> > Jul 17 07:33:53 pulsar kernel: xfs_da_do_buf: bno 16777216
> > Jul 17 07:33:53 pulsar kernel: dir: inode 54526538
> 
> I suspect you had some residual directory corruption from using the
> 2.6.17 XFS (which is known to have a lurking dir2 corruption issue,
> fixed in the latest -stable point release).
This has me very worried.

i just upgraded to .18-rc1-git5 when it came out, i used .17-rc3 before.
does this mean my .17-rc3 may have corrupted my filesystem?

what action do you suggest i do now?

> 
> > of programs fail in mysterious ways. I tried to recover using xfs_repair
> > but I feel that my partition is thorougly borked. Of course no data was 
> > lost due to backups but still I'd like this bug to be fixed ;-)
> 
> 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.
> 
> thanks.
> 

  parent reply	other threads:[~2006-07-19 11:23 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 22:29 XFS breakage in 2.6.18-rc1 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 [this message]
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  7:58       ` Martin Steigerwald
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
2006-07-25 20:16       ` Jan Engelhardt
2006-07-25 23:10         ` Nathan Scott
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
  -- strict thread matches above, loose matches on Subject: below --
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=1153304468.3706.4.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.com \
    --cc=torsten@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.