xfs
[Top] [All Lists]

Re: your mail

To: Gorazd Golob <gorazd.golob@xxxxxxxxxxxx>
Subject: Re: your mail
From: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Date: Sat, 27 May 2006 19:52:17 -0400 (EDT)
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <1148770618.16702.8.camel@dacun.noviforum.si>
References: <1148752776.16365.6.camel@dacun.noviforum.si> <Pine.LNX.4.64.0605271601080.31148@p34> <1148770618.16702.8.camel@dacun.noviforum.si>
Sender: xfs-bounce@xxxxxxxxxxx
The first thing everyone is going to tell you to do is upgrade your kernel to the latest stable, as of this minute that is 2.6.16.18.

See if you can reproduce the problem there.

You'll probably have to reboot/boot knoppix and run xfs_repair on the existing filesystem first, though.


On Sun, 28 May 2006, Gorazd Golob wrote:

nope - real device..

On Sat, 2006-05-27 at 16:01 -0400, Justin Piszcz wrote:
Are you using loop-aes?

On Sat, 27 May 2006, Gorazd Golob wrote:

Hi!

Anyone have idea what does that mean?

[376278.129936] Filesystem "sdb1": Corruption of in-memory data
detected.  Shutting down filesystem: sdb1
[376278.135533] Please umount the filesystem, and rectify the problem(s)

Kernel is 2.6.15.6-1, SMP, x86_64 bit. Also I'm not able to unmount file
system - and according to lsof it's not in use. umout is telling me
"device is busy".

Thanks, gorazd







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