From: ed1989 <edshrock@live.com>
To: linux-ext4@vger.kernel.org
Subject: I lost 15G from ext4 fsck failures tonight!
Date: Thu, 28 May 2009 21:55:42 -0700 (PDT) [thread overview]
Message-ID: <23774225.post@talk.nabble.com> (raw)
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.
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.
I don't see what the benefit of ext4 really is, when data loss doesn't seem
to be a concern among ext4 developers. I would expect that data loss should
be the primary concern.
I am most likely going to move back to ext3 or else to some other stable
filesystem like xfs.
--
View this message in context: http://www.nabble.com/I-lost-15G-from-ext4-fsck-failures-tonight%21-tp23774225p23774225.html
Sent from the linux-ext4 mailing list archive at Nabble.com.
next reply other threads:[~2009-05-29 4:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 4:55 ed1989 [this message]
2009-05-29 5:22 ` I lost 15G from ext4 fsck failures tonight! Christian Kujau
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=23774225.post@talk.nabble.com \
--to=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;
as well as URLs for NNTP newsgroup(s).