On Thu, 2006-06-29 at 08:18 -0400, William L. Maltby wrote:
> 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 <snip>
And to prove I've not ingested enough coffee yet, here's the 4KB
blocksize one I meant to include with the other post.
mke2fs 1.35 (28-Feb-2004)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
410400 inodes, 2441216 blocks
122060 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=2499805184
75 block groups
32768 blocks per group, 32768 fragments per group
5472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632
Writing inode tables: 0/75 ...75done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
--
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/3139ad79/attachment-0004.sig>