On 30.09.2014 22:36, Darrick J. Wong wrote:
sysfs will tell you:
$ ls /sys/block/sd*
lrwxrwxrwx 1 root root 0 Sep 30 13:31 /sys/block/sda ->
../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda/
^^^^
Nice, thanks. The error came from /dev/sdb definitely.
Both drives, individually.
md should be fine with that, since you're only running the read test.
You're right, of course, what was I thinking. :)
OK, 2 x badblocks already running. Will report tomorrow how it ended.
It would be fun to be able to poke around with an 'e2image /dev/md2' file, but
given the 1TB volume that might be unmanageable.
Yeah. Together with the fact that fs has millions of files + not enough
space on other disk, I'll have to pass on that one.
But, I'm pretty sure that it will come out clean. The md check I did
last night would surely detected bad blocks if there were any. Or
not?
Let's hope so, unless it's some weird transient error...
The worst kind. :( Dunno. I guess tomorrow I'll try unlink from debugfs.
Then e2fsck. First, we'll see if there are any bad blocks around.
Regards,
--
Zlatko
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
