Bad Disk Blocks with fsck???

Bad Disk Blocks with fsck???

Post by BIG_ » Sat, 23 Jan 1999 04:00:00



Hello,

In the example below, does fsck delete the contents of the bad block or does
it move the data to another block in the LV.  Also, is there a way to check
how many blocks are marked bad on a disk and where does the fsck program get
the block number from (3817871)?

** Checking /dev/rtesterlv (/test)
** Phase 1 - Check Blocks and Sizes
Cannot read: block 3817871; CLEAR? y
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Inode Map
** Phase 6 - Check Block Map
Filesystem integrity is not guaranteed
8 files 126616 blocks 3903848 free
***** Filesystem was modified *****

Thanks,
S.Singh

 
 
 

Bad Disk Blocks with fsck???

Post by BIG_ » Sat, 23 Jan 1999 04:00:00


Hello,

In the example below, does fsck delete the contents of the bad block or does
it move the data to another block in the LV.  Also, is there a way to check
how many blocks are marked bad on a disk and where does the fsck program get
the block number from (3817871)?

** Checking /dev/rtesterlv (/test)
** Phase 1 - Check Blocks and Sizes
Cannot read: block 3817871; CLEAR? y
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Inode Map
** Phase 6 - Check Block Map
Filesystem integrity is not guaranteed
8 files 126616 blocks 3903848 free
***** Filesystem was modified *****

Thanks,
S.Singh

 
 
 

Bad Disk Blocks with fsck???

Post by BIG_ » Sat, 23 Jan 1999 04:00:00


Hello,

In the example below, does fsck delete the contents of the bad block or does
it move the data to another block in the LV.  Also, is there a way to check
how many blocks are marked bad on a disk and where does the fsck program get
the block number from (3817871)?

** Checking /dev/rtesterlv (/test)
** Phase 1 - Check Blocks and Sizes
Cannot read: block 3817871; CLEAR? y
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Inode Map
** Phase 6 - Check Block Map
Filesystem integrity is not guaranteed
8 files 126616 blocks 3903848 free
***** Filesystem was modified *****

Thanks,
S.Singh

 
 
 

Bad Disk Blocks with fsck???

Post by Jerald H. Mathew » Sat, 23 Jan 1999 04:00:00


: In the example below, does fsck delete the contents of the bad block or does
: it move the data to another block in the LV.  Also, is there a way to check
: how many blocks are marked bad on a disk and where does the fsck program get
: the block number from (3817871)?

This is not a disk drive defect, it is only an INODE that has lost its
integrity. The number seems kind of large for an INODE number. When it
is fixed the data represented by that INDOE is usually stored in a file
in the lost+found directory of that partition. To recover the space,
if you don't need the data, just remove the file from lost+found.

--
Regards,
Jerry M.
Seen on a Tee Shirt, "Never GREP a YACC by the INODE".