lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 5 Jan 2009 19:47:06 -0500
From:	Theodore Tso <tytso@....edu>
To:	Giangiacomo Mariotti <gg.mariotti@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Half-Disaster switching from ext3 to ext4

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ