vxfs mount: /dev/vg02/lvol1 is already mounted, /oracle is busy, or allowable number of moun

[naveennella]

I have a problem with a disk that is damage and belongs to the vg02 volume group.

The filesystems that are unable to be mount are /oracle
What will be the procedure to can recover these filesystem ?

# mount -a
vxfs mount: /dev/vg02/lvol1 is already mounted, /oracle is busy,
or allowable number of mount points exceeded
mount: /dev/vg00/lvol8 is already mounted on /var
mount: /dev/vg00/lvol7 is already mounted on /usr
mount: /dev/vg01/lvol2 is already mounted on /usr/sap
mount: /dev/vg00/lvol6 is already mounted on /opt
mount: /dev/vg00/lvol5 is already mounted on /home
mount: /dev/vg00/lvol4 is already mounted on /tmp
mount: /dev/vg00/lvol1 is already mounted on /stand

It says the above message..is there any way to recify that.we dont have any back up of this.please suggest me how to solve the issue..?


regards,

Naveen

[Torsten.]

See

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf


Don't have a backup? Bad luck.
You should learn the lesson and backup your systems.

[naveennella]

Dear Experts,


Iam getting the following error

vxfs mount: /dev/vg02/lvol1 is corrupted. needs checking

When i put mount commmand
# mount -F vxfs /dev/vg02/lvol1 /oracle
vxfs mount: /dev/vg02/lvol1 is corrupted. needs checking

Please have a look into it..

[Torsten.]

Check it

# fsck -F vxfs /dev/vg02/rlvol1

and follow the document I posted earlier.

[naveennella]

Dear Expert,

# fsck -F vxfs /dev/vg02/lvol1
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
vxfs fsck: fsck read failure bno = 13092100, off = 0, len = 8192
full file system check required, exiting ...

This is the output i got..

regards,

Naveen

[Torsten.]

Do the "dd" check (see manual above).

[James R. Ferguson]

Hi Naveen:

Try a full check (as the last error suggested):

# fsck -F vxfs -o full /dev/vg02/rlvol1

However, as Torsten has suggested, look at "When Good Disks Go Bad" guide. You are probably going to need to replace the damaged disk and unless it's mirrored, restore the missing data from a backup.

Regards!

...JRF...

[naveennella]

Dear Expert,

# fsck -F vxfs -o full /dev/vg02/lvol1
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: file system had I/O error(s) on user data.
vxfs fsck: fsck read failure bno = 13092100, off = 0, len = 819
full file system check required, exiting ...

I read that document and checking everything it says ok and good,but i cant understand where it goes wrong.

regards,

Naveen

[Torsten.]

Did you perform the "dd"? How? Results?

[naveennella]

Dear

# dd if=/dev/rdsk/c5t0d3 of=/dev/null bs=1024k count=64&
[1] 4527
# 64+0 records in
64+0 records out

[1] + Done
#
#
#
# dd if=/dev/rdsk/c5t0d1 of=/dev/null bs=1024k count=64&
[1] 4528
# dd read error: Invalid argument
0+0 records in
0+0 records out

[1] + Done(2)

Regards,

Naveen

[Torsten.]

Please post

# vgdisplay -v vg02

[stephen peng]

and post
ioscan -fnCdisk

[naveennella]

# vgdisplay -v vg02
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Volume groups ---
VG Name /dev/vg02
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 4
Act PV 3
Max PE per PV 30000
VGDA 6
PE Size (Mbytes) 4
Total PE 73406
Alloc PE 56320
Free PE 17086
Total PVG 0



# ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
==========================================================================
disk 0 0/0/1/1.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c1t0d0 /dev/rdsk/c1t0d0
disk 1 0/0/1/1.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 0/0/2/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 3 0/0/2/0.2.0 sdisk CLAIMED DEVICE HP 36.4GST336753LC
/dev/dsk/c2t2d0 /dev/rdsk/c2t2d0
disk 5 0/10/0/1.0.0.0 sdisk CLAIMED DEVICE I2O RAID1
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
disk 6 0/10/0/1.0.0.1 sdisk CLAIMED DEVICE I2O RAID1
/dev/dsk/c5t0d1 /dev/rdsk/c5t0d1
disk 7 0/10/0/1.0.0.2 sdisk CLAIMED DEVICE I2O RAID5
/dev/dsk/c5t0d2 /dev/rdsk/c5t0d2
disk 22 0/10/0/1.0.0.3 sdisk CLAIMED DEVICE I2O RAID5
/dev/dsk/c5t0d3 /dev/rdsk/c5t0d3
disk 8 0/10/0/1.0.0.4 sdisk CLAIMED DEVICE I2O RAID5
/dev/dsk/c5t0d4 /dev/rdsk/c5t0d4
Total Spare PVs 0
Total Spare PVs in use 0

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
--- Logical volumes ---
LV Name /dev/vg02/lvol1
LV Status available/syncd
LV Size (Mbytes) 260000
Current LE 65000
Allocated PE 65000
Used PV 3


--- Physical volumes ---
PV Name /dev/dsk/c5t0d2
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 17362
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c5t0d3
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 26044
Free PE 0
Autoswitch On
Proactive Polling On

PV Name /dev/dsk/c5t0d4
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c5t0d1":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.
PV Status available
Total PE 30000
Free PE 17086
Autoswitch On
Proactive Polling On

[Dennis Handly]

>I can't understand where it goes wrong.

fsck(1m) says it is bad.
And if you use dd(1), you should do the whole disk, not just 64 Mb.

[stephen peng]

hopefully this doc could give you more hint:
http://docs.hp.com/en/J6173-90007/J6173-90007.pdf

[chris huys_4]

irdiag -v

[Torsten.]

For whatever reason /dev/dsk/c5t0d1 is not accessible.

This is a hardware RAID (mirror) built from a RAID4SI controller, so follow the advise above and check the controller.

[P Arumugavel]

Please post the /var/adm/syslog/syslog.log.

[Torsten.]

As said,

# irdiag -v

will surely show the reason for this problem.

[P Arumugavel]

Hi naveen,
Refer the below link.

http://docs.hp.com/en/J6173-90007/ch05s01.html#cdggjacb

[naveennella]

Dear Experts,

I removed the case and inserted again then it shows the hard disk in online.And now after doing this if i put bdf

it is showing as

# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 3072000 841232 2213744 28% /
/dev/vg00/lvol1 2008376 129584 1677952 7% /stand
/dev/vg00/lvol8 10240000 3845544 6345616 38% /var
/dev/vg00/lvol7 3678208 1397144 2263296 38% /usr
/dev/vg00/lvol4 1024000 457688 562480 45% /tmp
/dev/vg00/lvol6 4096000 1694880 2386872 42% /opt
/dev/vg00/lvol5 516096 221712 292128 43% /home

I missed two file systems which is vg01 and vg02.both the vg's not showing in the system.Please help me how to get that cg's..


regards,

Naveen