Hi,
Ok, here comes the funny part:
I have got several messages from the kernel about one of my XFS (sdb2) have
corrupted inodes, but my xfs_repair (v. 2.8.11) says the FS is clean and
shine.
Should i upgrade my xfs_repair, or this is another bug? :-)
Thanks,
Janos
----- Original Message -----
From: "Dave Chinner" <[email protected]>
To: "Janos Haar" <[email protected]>
Cc: <[email protected]>; <[email protected]>;
<[email protected]>; <[email protected]>; <[email protected]>;
<[email protected]>
Sent: Thursday, April 08, 2010 4:58 AM
Subject: Re: Kernel crash in xfs_iflush_cluster (was Somebody take a look
please!...)
> On Thu, Apr 08, 2010 at 04:45:13AM +0200, Janos Haar wrote:
>> Hello,
>>
>> Sorry, but still have the problem with 2.6.33.2.
>
> Yeah, these still a fix that needs to be back ported to .33
> to solve this problem. It's in the series for 2.6.32.x, so maybe
> pulling the 2.6.32-stable-queue tree in the meantime is your best
> bet.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> [email protected]
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
On Mon, Apr 12, 2010 at 12:44:37AM +0200, Janos Haar wrote:
> Hi,
>
> Ok, here comes the funny part:
> I have got several messages from the kernel about one of my XFS
> (sdb2) have corrupted inodes, but my xfs_repair (v. 2.8.11) says the
> FS is clean and shine.
> Should i upgrade my xfs_repair, or this is another bug? :-)
v2.8.11 is positively ancient. :/
I'd upgrade (current is 3.1.1) and re-run repair again.
Cheers,
Dave.
--
Dave Chinner
[email protected]