From: Rob McMahon (Rob.McMahon@warwick.ac.uk)
Date: Fri Sep 30 2005 - 06:50:24 EDT
I had two replies (well, apart from the out-of-office ones), one from
Darren Dunham, saying essentially that the only way would be to trawl
through the entire filesystem searching for it, as in:
for every file
find all blocks in file
is block == xx?
and another from Brett Lymn suggesting to tar the filesystem to
/dev/null and watch the errors. This seemed like a really simple plan,
but unfortunately when I tried it I got no fatal errors, they were all
correctable ...
Cheers, and thanks especially to Darren and Brett.
Rob
> When I get an error like
>
>> Sep 23 17:10:27 rusizi scsi: [ID 107833 kern.warning] WARNING:
>> /pci@1f,2000/fibre-channel@1/fp@0,0/ssd@w210000004c517e91,0 (ssd3):
>> Sep 23 17:10:27 rusizi Error for Command: read(10)
>> Error Level: Fatal
>> Sep 23 17:10:27 rusizi scsi: [ID 107833 kern.notice] Requested
>> Block: 7421607 Error Block: 7421607
>> Sep 23 17:10:27 rusizi scsi: [ID 107833 kern.notice] Vendor:
>> NEC Serial Number: 212270000000
>> Sep 23 17:10:27 rusizi scsi: [ID 107833 kern.notice] Sense Key:
>> Hardware Error
>> Sep 23 17:10:27 rusizi scsi: [ID 107833 kern.notice] ASC: 0xc0
>> (<vendor unique code 0xc0>), ASCQ: 0x40, FRU: 0x0
>
>
> How do I get back from the Error Block to the file/inode it was in ?
> I've been trawling through the fsdb man page, but can't quite figure
> it out.
-- E-Mail: Rob.McMahon@warwick.ac.uk PHONE: +44 24 7652 3037 Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:31:55 EDT