On Wed, 7 Jul 1999, Itamar S.-T. wrote:
> EXT2-fs error (device sd(8,1)): ext2_read_inode: unable to read inode block
> - inode=150140, block=598034
Hrmmm.
If this is not a physical problem, running fsck on that file system will
clear this inode.
If this is a physical problem, you need to map that block as unusable to
the scsi controller (there are tools to do that, debugfs is one). In this
case, if using debugfs, you'll need to clear the inode, clear the block,
and then mark it as used I guess, so it wont try to use it again. I hope
there are better tools out there, that will mark the block as BAD.
(you can also try badblocks(8) )
--Ariel
>
> --
> Itamar - [EMAIL PROTECTED]
> -----------------------------o-------------------------------------o
> Sealingwax Greeting Cards | The only good morning is a dead one |
> http://www.sealingwax.com/| --Richard Stallman |
>
> =================================================================
> To unsubscribe, send mail to [EMAIL PROTECTED] with
> the word "unsubscribe" inthe message body, e.g., run the command
> echo unsubscribe | mail [EMAIL PROTECTED]
>
--
Ariel Biener
e-mail: [EMAIL PROTECTED] Work phone: 03-640608
fingerprint = 07 D1 E5 3E EF 6D E5 82 0B E9 21 D4 3C 7D 8B BC
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
