On Thu, 2006-06-29 at 00:05 -0400, Paul wrote:
> Can anyone point me in the right direction for correcting errors on an HD
> when using LVM? I've tried e2fsck and indicates bad block. I've tried
> with -b 8193, 16384, and 32768 and no good.
Keep in mind that backup super-blocks will differ depending on files
system size (IIRC) and block size (IIRC again) and who knows what? If
your FS is "large" or ... anyway, here my backup super blocks an FS made
as indicated
################# m k e 2 f s & m k d i r ################
Filesystem label=/Home01
OS type: Linux
Block size=2048 (log=1)
Fragment size=2048 (log=1)
524288 inodes, 2097152 blocks
20971 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=538968064
128 block groups
16384 blocks per group, 16384 fragments per group
4096 inodes per group
Superblock backups stored on blocks:
16384, 49152, 81920, 114688, 147456, 409600, 442368, 802816,
1327104, 2048000
Writing inode tables: 0/128...127/128 done
Writing inode tables: 0/128...127/128 done
Creating journal (8192 blocks): done
> <snip>
HTH
--
Bill
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.centos.org/pipermail/centos/attachments/20060629/34f3209e/attachment-0004.sig>