xfs
[Top] [All Lists]

Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable

To: "Avuton Olrich" <avuton@xxxxxxxxx>
Subject: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
From: Duncan Sands <duncan.sands@xxxxxxxxxxxxxx>
Date: Sun, 25 Jun 2006 15:55:17 +0200
Cc: "Nathan Scott" <nathans@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <200606251209.23766.duncan.sands@xxxxxxxxxxxxxx>
References: <3aa654a40606190044q43dca571qdc06ee13d82d979@xxxxxxxxxxxxxx> <3aa654a40606200120v5baf0304ka205f1ad8f136ad9@xxxxxxxxxxxxxx> <200606251209.23766.duncan.sands@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: KMail/1.9.1
On Sunday 25 June 2006 12:09, Duncan Sands wrote:
> I just got a new XFS crash running 2.6.17, again with problems at block
> 16777216 - I'll try to make a copy of the corrupted filesystem available.
> Interestingly enough, I'm also seeing ext3 corruption.  The usual
> manifestation is that a program fails to run, with a message about it
> not being in executable format (if it happens again I will take a note of
> the exact message).  I've had no problems at all with 2.6.17.  It seems
> to be happening randomly, which makes me suspect a race condition
> (uniprocessor machine, but preemptable kernel), or memory corruption.
> I will rebuild the kernel with all kernel debugging options turned
> on, once I recover the filesystem.

Sorry, that should say: "I've had no problems at all with 2.6.15".
Also, xfs_repair successfully repaired the filesystem this time.
I've kept a copy of the filesystem in case anyone is interested.

Duncan.


<Prev in Thread] Current Thread [Next in Thread>