From: Theodore Tso <tytso@mit.edu>
To: Giangiacomo Mariotti <gg.mariotti@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Half-Disaster switching from ext3 to ext4
Date: Mon, 5 Jan 2009 19:47:06 -0500 [thread overview]
Message-ID: <20090106004706.GF14500@mit.edu> (raw)
In-Reply-To: <12bfabe40901031923r3a828f71v74a8c6a56746b2ec@mail.gmail.com>
On Sun, Jan 04, 2009 at 04:23:42AM +0100, Giangiacomo Mariotti wrote:
> the partitions(except for root obviously), I synced some times before
> doing that and then I shut down the pc with a "shutdown -h -P now".
> when I booted again the system, /dev/sda2(the partition with the most
> important data. Murphy's law really works!) failed to get mounted with
> a message saying something about corrupted groups(maybe, I don't
> remember exactly). Trying to do a fsck.ext4 -p /dev/sda2, I got
> something like : fsck.ext4 : Invalid argument while checking ext3
> journal for /dev/sda2.
What version of e2fsprogs do you have installed, and can you dig up
the exact error message at mount time? It should be in the your
system logs....
> remounted it, all files were gone! I was starting to use the sleuth
> kit, when I noticed that in the search+found directory there were
> almost all the files, but not all of them and in a rearrenged
> directory structure.
Sounds like the root inode got zapped. As for why, it's hard to say.
It could be a simple disk failure that happend as bad luck. I haven't
seen any other bug reports that report corruption similar to yours, so
without a lot more information or a way to reproduce the error,
there's not much more I can say.
Regards,
- Ted
next prev parent reply other threads:[~2009-01-06 0:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 3:23 Half-Disaster switching from ext3 to ext4 Giangiacomo Mariotti
2009-01-06 0:47 ` Theodore Tso [this message]
2009-01-06 2:11 ` Ken Witherow
2009-01-06 2:44 ` Theodore Tso
2009-01-07 3:11 ` Giangiacomo Mariotti
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=20090106004706.GF14500@mit.edu \
--to=tytso@mit.edu \
--cc=gg.mariotti@gmail.com \
--cc=linux-kernel@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