mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kevin Radloff" <radsaq@gmail.com>
To: "Torsten Landschoff" <torsten@debian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: XFS breakage in 2.6.18-rc1
Date: Tue, 18 Jul 2006 19:06:06 -0400	[thread overview]
Message-ID: <3b0ffc1f0607181606x1e6b1744j52a77a68cbaf2917@mail.gmail.com> (raw)
In-Reply-To: <20060718222941.GA3801@stargate.galaxy>

On 7/18/06, Torsten Landschoff <torsten@debian.org> wrote:
> Hi friends,
>
> 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:
[snip]
> That problem occured during a dist-upgrade, dm-6 is my /usr partition. Funny
> enough this happened a few months after finally replaced my ancient disk
> with a RAID1 array to make sure I do not lose data ;)
>
>
> In any case it seems like the XFS driver in 2.6.18-rc1 is decently broken.
> After booting into 2.6.17 again, I could use /usr again but random files
> contain null bytes, firefox segfaults instead of starting up and a number
> 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 ;-)
>
> If more information from my logs is required, I can make it available (and any
> part of the partition if required).

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.

Also see this thread:

http://marc.theaimsgroup.com/?l=linux-kernel&m=115070320401919&w=2

-- 
Kevin 'radsaq' Radloff
radsaq@gmail.com
http://thesaq.com/

  parent reply	other threads:[~2006-07-18 23:06 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
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 [this message]
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=3b0ffc1f0607181606x1e6b1744j52a77a68cbaf2917@mail.gmail.com \
    --to=radsaq@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torsten@debian.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®