[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.01.0905282211440.7424@bogon>
Date: Thu, 28 May 2009 22:22:13 -0700 (PDT)
From: Christian Kujau <lists@...dbynature.de>
To: ed1989 <edshrock@...e.com>
cc: linux-ext4@...r.kernel.org
Subject: Re: I lost 15G from ext4 fsck failures tonight!
On Thu, 28 May 2009, ed1989 wrote:
> I moved some data off of a 115G ext4 filesystem on an LVM logical volume.
> Then I resized the ext4 filesystem. Unfortunately, 15G of the remaining 95G
> in data was lost to /lost+found due to repeated fsck errors.
Did you run fsck (which version?) before or after the resizing process?
IIRC resize2fs recommends running e2fsck before doing anything. Do you
have a log of the errors reported by e2fsck? Also, were there any errors
in your syslog (i.e. /var/log/messages, dmesg, etc.)
> I have also had the problem of ext4 destroying my kde4 configuration files
> so that my kde4 desktop would revert back to the defaults occasionally.
This has been discussed on this list (and elsewhere) before, in short:
it's not really ext4 destroying but more like kde4 not really writing its
configuration files. But this is an oversimplified version of the real
issues, please search the archives for details.
> I am most likely going to move back to ext3 or else to some other stable
> filesystem like xfs.
Out of curiosity: why did you switch to ext4?
Christian.
--
BOFH excuse #310:
asynchronous inode failure
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists