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...)
pvscan -- ACTIVE PV "/dev/dasdg1" of VG "ora_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdh1" of VG "ora_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdi1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdj1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdk1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdl1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdm1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdn1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdo1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdp1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdq1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdr1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasds1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdz1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdaa1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdab1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdac1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdad1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdae1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- ACTIVE PV "/dev/dasdaf1" of VG "data_vg" [2.29 GB / 0 free]
pvscan -- total: 20 [45.84 GB] / in use: 20 [45.84 GB] / in no VG: 0 [0]
[EMAIL PROTECTED]:~# lvscan
lvscan -- ACTIVE "/dev/data_vg/lvol1" [39.95 GB]
lvscan -- ACTIVE "/dev/data_vg/lvol2" [1.18 GB]
lvscan -- ACTIVE "/dev/ora_vg/ora_lv1" [4.57 GB]
lvscan -- 3 logical volumes with 45.70 GB total in 2 volume groups
lvscan -- 3 active logical volumes
[EMAIL PROTECTED]:~# lvdisplay /dev/data_vg/lvol1
--- Logical volume ---
LV Name /dev/data_vg/lvol1
VG Name data_vg
LV Write Access read/write
LV Status available
LV # 1
# open 0
LV Size 39.95 GB
Current LE 10227
Allocated LE 10227
Allocation next free
Read ahead sectors 120
Block device 58:1
[EMAIL PROTECTED]:~# lvdisplay /dev/data_vg/lvol2
--- Logical volume ---
LV Name /dev/data_vg/lvol2
VG Name data_vg
LV Write Access read/write
LV Status available
LV # 2
# open 0
LV Size 1.18 GB
Current LE 303
Allocated LE 303
Allocation next free
Read ahead sectors 120
Block device 58:2
[EMAIL PROTECTED]:~# vgdisplay
--- Volume group ---
VG Name data_vg
VG Access read/write
VG Status available/resizable
VG # 1
MAX LV 256
Cur LV 2
Open LV 0
MAX LV Size 255.99 GB
Max PV 256
Cur PV 18
Act PV 18
VG Size 41.13 GB
PE Size 4 MB
Total PE 10530
Alloc PE / Size 10530 / 41.13 GB
Free PE / Size 0 / 0
VG UUID bdggwE-vRSw-w05h-CPZJ-nUnU-S5fe-io4wh6
--- Volume group ---
VG Name ora_vg
VG Access read/write
VG Status available/resizable
VG # 0
MAX LV 256
Cur LV 1
Open LV 1
MAX LV Size 255.99 GB
Max PV 256
Cur PV 2
Act PV 2
VG Size 4.57 GB
PE Size 4 MB
Total PE 1170
Alloc PE / Size 1170 / 4.57 GB
Free PE / Size 0 / 0
VG UUID 3Tp2pa-bKCn-JEWF-sp3E-9U7H-bIzO-v1Y4Rk
[EMAIL PROTECTED]:~# tune2fs -l /dev/data_vg/lvol1
tune2fs 1.26 (3-Feb-2002)
tune2fs: Bad magic number in super-block while trying to open
/dev/data_vg/lvol1
Couldn't find valid filesystem superblock.
[EMAIL PROTECTED]:~# tune2fs -l /dev/data_vg/lvol2
tune2fs 1.26 (3-Feb-2002)
tune2fs: Bad magic number in super-block while trying to open
/dev/data_vg/lvol2
Couldn't find valid filesystem superblock.
[EMAIL PROTECTED]:~# e2fsck /dev/data_vg/lvol1
e2fsck 1.26 (3-Feb-2002)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open
/dev/data_vg/lvol1
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[EMAIL PROTECTED]:~# e2fsck /dev/data_vg/lvol2
e2fsck 1.26 (3-Feb-2002)
Couldn't find ext2 superblock, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open
/dev/data_vg/lvol2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
[EMAIL PROTECTED]:~# e2fsck -b 8193 /dev/data_vg/lvol2
e2fsck 1.26 (3-Feb-2002)
e2fsck: Bad magic number in super-block while trying to open
/dev/data_vg/lvol2
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
--
Jae-hwa Park <[EMAIL PROTECTED]>
THE CHALLENGES, that's why I choose LINUX!!!
For more information on me, visit http://php.sarang.net
