topic Re: failure to mount directory in Operating System - HP-UX

failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:03:39 GMT

Hi guys,

I had to reboot my server and I tried to go to /home directory only to find out there there is nothing there.

I did 'bdf' and I didn't see /home mounted, so I tried to mount /home and here is what I get:

test4:/> mount /home
vxfs mount: /dev/vg00b/lvol5 is corrupted. needs checking

Does anyone know whats going on?

Thanks a lot!

Re: failure to mount directory

Pete Randall — Mon, 22 Jul 2002 14:06:36 GMT

Andi,

Home was not shut down cleanly and needs to be checked via fsck. Run "fsck -y /dev/vg00b/rlvol5", then mount.

Pete

Re: failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:09:18 GMT

Hi Pete,

Here is what I get:

test4:/> fsck -y /dev/vg00b/rvol5
fsck: /etc/default/fs is used for determining the file system type
vxfs fsck: cannot stat /dev/vg00b/rvol5
test4:/>

Re: failure to mount directory

Stefan Farrelly — Mon, 22 Jul 2002 14:10:58 GMT

Try;

fsck -F vxfs -o full /dev/vg00b/rlvol5

And answer Y when prompted, then mount it.

Re: failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:13:11 GMT

Stefan,

Here is what I get:

test4:/> fsck -F vxfs -o full /dev/vg00b/rvol5
vxfs fsck: cannot stat /dev/vg00b/rvol5

Hmm, unrecoverable??

Re: failure to mount directory

S.K. Chan — Mon, 22 Jul 2002 14:22:13 GMT

Typo ?? "rlvol5"

Re: failure to mount directory

A. Clay Stephenson — Mon, 22 Jul 2002 14:24:13 GMT

That should be:
fsck -F vxfs -o full /dev/vg00b/rlvol5

Re: failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:24:47 GMT

Not really ;-(

test4:>fsck -F vxfs -o full /dev/vg00b/rlvol5

file system is larger than device
vxfs fsck: cannot initialize aggregate
file system check failure, aborting ...
test4:/>

Re: failure to mount directory

Stefan Farrelly — Mon, 22 Jul 2002 14:25:14 GMT

Sounds bad. In /dev/vg00b if you do an ls -l do all the major/minor numbers look correct ?

If you grep for /home in /etc/fstab does it match vg00b/lvol5 ? In /etc/fstab is it hfs or vxfs ?

If its hfs, try;
fsck -F hfs -y /dev/vg00b/lvol5

Re: failure to mount directory

MANOJ SRIVASTAVA — Mon, 22 Jul 2002 14:26:24 GMT

Hi

do a fsck -y /dev/vg00b/rlvol5

and then

do mount /dev/vg00b/lvol5 /home

it looks that the filesystem was not umounted so it needs to be checked.

Manoj Srivastava

Re: failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:27:15 GMT

Actually,

fstyp on /dev/vg00b/lvol5 returns vxfs

all minor/major numbers look good!

;-(

Re: failure to mount directory

V. V. Ravi Kumar_1 — Mon, 22 Jul 2002 14:29:36 GMT

hi,

ur typing it wrongly, u type rlvol5 in place of lvol5.

regds

Re: failure to mount directory

Shannon Petry — Mon, 22 Jul 2002 14:32:57 GMT

I have seen many times too, where someone accidentally unplugs an external device, or bumps the scsi address selector. If this is external then check these first. You can get your old address (if it's it" by doing a "strings /etc/lvmtab|more" and look at the devices under /dev/vg00b.

Regards,
Shannon

Re: failure to mount directory

Stefan Farrelly — Mon, 22 Jul 2002 14:33:22 GMT

Just FYI for others who replied - using /dev/vg00b/rlvol5 is not a problem - its actually faster than using lvol5 ! Read the man page on fsck_vxfs

As for your problem, could either be a patch issue (you got some uptodate LVM/JFS patches installed ?) or to check the filesystem at a lower level try;

dd if=/dev/vg00b/rlvol5 of=/dev/null bs=1024k

And does it return xxx blocks in+out or an I/O error ?

Re: failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:36:32 GMT

Hi Stefan,

Here is what I get:

test4:/dev/vg00b> dd if=/dev/vg00b/rlvol5 of=/dev/null bs=1024k
24+0 records in
24+0 records out
test4:/dev/vg00b>

Re: failure to mount directory

Stefan Farrelly — Mon, 22 Jul 2002 14:42:43 GMT

Aha, the dd worked, it read 24MB which should be the size of your /home lvol. Now, the key is your error;

file system is larger than device

Which appears to me is someone has increased the size of the lvol without running extendfs or fsadm on it to match, so if the filesystem doesnt match the size of the lvol you get this error. If you do an lvdisplay /dev/vg00b/lvol5 how big is it ? (I'd have a guess at 20Mb!)

I think your going to need to resize it back to what the filesystem size is from lvdisplay using lvreduce, then fsck it.

Re: failure to mount directory

andi_1 — Mon, 22 Jul 2002 14:44:29 GMT

Hi Stefan,
it seems that it is 24mb....

LV Name /dev/vg00b/lvol5
VG Name /dev/vg00b
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 24
Current LE 6
Allocated PE 6
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

do you still think I should reduce the size of lvol5?

Thanks a lot!

Re: failure to mount directory

Ceesjan van Hattum — Mon, 22 Jul 2002 14:45:37 GMT

In case you used mirrored disks, try to use this features, like vgsync etcetera.

Regards,
Ceesjan

Re: failure to mount directory

Stefan Farrelly — Mon, 22 Jul 2002 14:51:45 GMT

Nope, dont resize it. DD confirms 24MB, as does lvdisplay. Good. The filesystem could still be a different size if someone used fsadm -b to resize it without running lvextend on it. Normally you could try running fsadm -b on it to resize back but this only works on a mounted filesystem and you cant mount yours! I think youre stuck. In cases like this where someone runs fsadm -b to resize or runs lvextend without the other then you next reboot, your dead. You will have to newfs your lvol and recover from backup.

If youre desperate not to recover from backup HP can dialin and run some utils they possess to resize it back manually - but you will need to call HP and persuade them to do this (and have a dialin setup).