Operating System - HP-UX
1834275 Members
2295 Online
110066 Solutions
New Discussion

Re: Problem with mounting a file system

 
SOLVED
Go to solution
Bunty...
Occasional Contributor

Problem with mounting a file system

Hi,
As I unmounted a old file system and i was mounting another directory, i got this error:

# mount /dev/vg10/lvol6 /bunty/oracle/data
/dev/vg10/lvol6: unrecognized file system

# mount -F vxfs /dev/vg10/lvol6 /bunty/oracle/data
vxfs mount: file system on /dev/vg10/lvol6 has structural damage

Note : i forgot to update /etc/fstab file before mounting.
now i have deleted the old file system entries.

Please suggest
bunty
9 REPLIES 9
Luk Vandenbussche
Honored Contributor
Solution

Re: Problem with mounting a file system

Hi,

Try this

fsck -y /dev/vg10/rlvol6
mount vxfs /dev/vg10/lvol6 /bunty/oracle/data
Geoff Wild
Honored Contributor

Re: Problem with mounting a file system

Try fsck'ing it:

fsck -F vxfs /dev/vg10/rlvol6

Then try the mount - also post a vgdisplay -v vg10

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Steven E. Protter
Exalted Contributor

Re: Problem with mounting a file system

If the fs is really gone, edit the /etc/fstab and then:

mount -a

Any errors will display after a delay.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Bunty...
Occasional Contributor

Re: Problem with mounting a file system

# fsck -F vxfs /dev/vg10/lvol6
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: OLT extent 0 has bad magic
read of primary OLT failed
vxfs fsck: OLT extent 1 has bad magic
read of OLT copy failed
vxfs fsck: no valid OLT, cannot continue
file system check failure, aborting ...

# mount -F vxfs /dev/vg10/lvol6 /bunty/oracle/data/
vxfs mount: file system on /dev/vg10/lvol6 has structural damage

# fsck -F vxfs /dev/vg10/rlvol6
vxfs fsck: file system had I/O error(s) on meta-data.
vxfs fsck: OLT extent 0 has bad magic
read of primary OLT failed
vxfs fsck: OLT extent 1 has bad magic
read of OLT copy failed
vxfs fsck: no valid OLT, cannot continue
file system check failure, aborting ...
Geoff Wild
Honored Contributor

Re: Problem with mounting a file system

I'm afraid your lvol6 is pooched...

lvdisplay -v vg10 and lvdisplay -v /dev/vg10/lvol6 |more - see what devs it has and any errors...

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Geoff Wild
Honored Contributor

Re: Problem with mounting a file system

oops - first one above should be vgdispla -v vg10

Rgds...Geoff
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Deoncia Grayson_1
Honored Contributor

Re: Problem with mounting a file system

you need to do a vgdisplay -v vg10 and lvdisplay -v /dev/vg10/lvol6 as Geof suggested and get a list of disks that belongs to that volume group, you should try to do a pvdisplay on /dev/dsk/c?t?d? and diskinfo on the devices to find out which one is your culprit...
If no one ever took risks, Michelangelo would have painted the Sistine floor. -Neil Simon
Thomas J. Harrold
Trusted Contributor

Re: Problem with mounting a file system

Perhaps someone stepped on your physical device file by mistake. (with dd command, pvcreate -f, etc..)

Definately get a list of you LVM PV's, and cross-compare with /etc/fstab, or any RAW devices you may be using on the system.

-tjh



I learn something new everyday. (usually because I break something new everyday)
Darrel Louis
Honored Contributor

Re: Problem with mounting a file system

Bunty,

You posted a question on the 14th, on how to remove a FS, ( http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=983617 ) did you performed the suggestions provided and did you used the correct disks?

It could be that you've "dd" to a wrong disk.

Good Luck

Darrel