Mailinglist Archive: opensuse-bugs (8114 mails)

< Previous Next >
[Bug 246959] ext3 self-destruct on openSUSE 10.2 (kernel-default-2.6.18.2-34)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 21 Feb 2007 03:22:54 -0700 (MST)
  • Message-id: <20070221102254.3732FFCA@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=246959


matthias.andree@xxxxxx changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|matthias.andree@xxxxxx |




------- Comment #3 from matthias.andree@xxxxxx 2007-02-21 03:22 MST -------
I'm afraid I don't have a metadata image. My fault, I didn't think of that and
I did not expect corruptions as bad as I've seen, since I have never had such
massive data losses with ext2 or ext3 in 10 years.

WRT the disk drive, it passes S.M.A.R.T. self tests and has not reallocated
more sectors since the original event (7 in total according to smartctl -a) or
logged any I/O errors in the current situation. Even if it had, it should not
have cost more than a few directories, but:

$ sudo find /lost+found/ -type d | wc -l
Password:
20366

That's 20366 directories in lost+found, and they're from all over the map,
inode numbers from 18,000 to 2,000,000, with a bit more than 2 million
available inodes total.

I'd suggest to keep this report around for a few weeks, just to see if any
further similar reports come in -- or if this was a one-time event. The related
bits I found are http://www.ussg.iu.edu/hypermail/linux/kernel/0511.0/0193.html


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >
References