> Maybe the disk has so many other errors that it has run out of spare
> blocks to remap to.
Unlikely, at a total of 6 remapped blocks?
> I'd get a new disk pretty quick...
It's under warranty, so that would cost real money. I'm not sure whether
they'd replace it in this state:
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Self-test execution status: ( 112) The previous self-test completed having
the read element of the test failed.
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Extended offline Completed: read failure 00% 2716
0x0067fdcc
# 2 Short offline Completed without error 00% 2715 -
The extended test consistently fails, the rest is ok (still).
> [...] or a bug in smartmontools or the kernel.
No, the errors started occuring before I upgraded. The current
smartmontools is better: it sends me email about it.
> You'll be able to work out what file is affected using debugreiserfs.
I don't see how - the only argument taking a block number is -1, and
that's "print the block". Combined with -p and/or -S it spits something,
but it's not a filename. I was hoping for something like
find-me-the-filename --lba 0x0067fdcc /dev/hda
(and there are several partitions on it)
Thanks,
Volker
Btw IMHO running smartmontools is a must, if you aren't already start
sooner than later.
--
Volker Kuhlmann is possibly list0570 with the domain in header
http://volker.dnsalias.net/ Please do not CC list postings to me.
