Thank you for your considerations.
Anyway, it doesn't work. I've tried 'mke2fs -n' option and e2fck -b {many
backups of superblock}. But I couldn't check the file system corrupted.
Any other way?
[EMAIL PROTECTED]:~# mke2fs -n /dev/data_vg/lvol1
mke2fs 1.26 (3-Feb-2002)
Filesystem label=
OS type:
from `man mke2fs':
...
-n causes mke2fs to not actually create a filesystem, but
display
what it would do if it were to create a filesystem. This
can be
used to determine the location of the backup superblocks
for a
particular filesystem, so lon
You should be able to use a backup superblock on that filesystem. You
can use e2fsck -b x where x is the location of the backup
superblock. This location changes depending on block size of the
filesystem. If your filesystem was created with 4k block size the your
first backup super bloc
Hello, gurus!
Please help me. We're using Linux on zSeries (RedHat 7.2) now. After z/VM
crashed,
linux server(ceuna) have some filesystem error like the below.
Are there any way to recover this problem?
[EMAIL PROTECTED]:~# pvscan
pvscan -- reading all physical volumes (this may take a while...)