public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <lists@nerdbynature.de>
To: ed1989 <edshrock@live.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: I lost 15G from ext4 fsck failures tonight!
Date: Thu, 28 May 2009 22:22:13 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.01.0905282211440.7424@bogon> (raw)
In-Reply-To: <23774225.post@talk.nabble.com>

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

  reply	other threads:[~2009-05-29  5:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29  4:55 I lost 15G from ext4 fsck failures tonight! ed1989
2009-05-29  5:22 ` Christian Kujau [this message]
2009-05-29 13:58 ` Theodore Tso

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.01.0905282211440.7424@bogon \
    --to=lists@nerdbynature.de \
    --cc=edshrock@live.com \
    --cc=linux-ext4@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox