[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44BE48D5.7020107@mnsu.edu>
Date: Wed, 19 Jul 2006 09:59:33 -0500
From: "Jeffrey E. Hundstad" <jeffrey.hundstad@...u.edu>
To: Mattias Hedenskog <ml@...og.se>
Cc: linux-kernel@...r.kernel.org
Subject: Re: XFS breakage in 2.6.18-rc1
I did try the xfs_repair 2.8.4 for a volume running on 2.6.17.4 and it
annihilated the volume. This volume was not showing signs of crashing.
So... I guess I would certainly not run xfs_repair unless there is good
reason.
--
Jeffrey Hundstad
PS. ...yes, I had a recent backup ;-)
Mattias Hedenskog wrote:
>> 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
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists