mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mattias Hedenskog" <ml@magog.se>
To: linux-kernel@vger.kernel.org
Subject: Re: XFS breakage in 2.6.18-rc1
Date: Wed, 19 Jul 2006 16:17:50 +0200	[thread overview]
Message-ID: <67dc30140607190717r57ed2fe5w719dcca896110d8@mail.gmail.com> (raw)

> That looks like the death knell of my /, which succumbed on Friday as
> a result (I believe) of the corruption bug that was in 2.6.16/17.
> Ironically enough, I also saw the problem during an aptitude upgrade.

Hi all,

I just want to confirm this bug as well and unfortunately it was my
system disk too who had to take the hit. Im running 2.6.16 and its
reproducible in 2.6.17 and 2.6.18-rc1 as well. When I tried to repair
the fs I got the same error as in the previous post, running xfsprogs
2.8.4. I haven't had the time to debug this issue further because the
box is quite critical but I'll keep an eye on the other disks on the
system still running xfs.

Regards,
Mattias Hedenskog

             reply	other threads:[~2006-07-19 14:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-19 14:17 Mattias Hedenskog [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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-19 21:14   ` 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-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

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=67dc30140607190717r57ed2fe5w719dcca896110d8@mail.gmail.com \
    --to=ml@magog.se \
    --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®