Lost a filesystem

[Zurida Azah Abdul Rahma_2]

When I do a bdf,I can't see a filesystem(/data1). It's missing.
1) When I type mount /dev/vg01/lvol1 /data1 the message /dev/vg01/lvol1:unrecognized filesystem.

2) When I type mount -a the message vxfs mount:cannot mount /dev/vg01/lvol1

3) When I type umount /data1 the message:cannot find /data1 in /etc/mnttab cannot unmount /data1

Appreciate if somebody can helpm me to solve the problem. Thanks in advance.

[Con O'Kelly]

Hi

It sounds like you have a corrupted filesystem.

The mount command is saying that it can't recognise a filesystem on /dev/vg01/lvol1.

Can you run fsck on /dev/vg01/lvol1?

Cheers
Con

[malay boy]

Hi,
Can you check whether the disk are OK.

Please do :

vgdisplay -v vg01

note the physical disk.

Check the disk using dd command .

dd if=/dev/ of=/dev/null


Easist way :

check dmesg or syslog to check whether hardware are ok or not.

regards
mB

[Norman_21]

Hello,

Try this,

# fuser -cu /data1

check the entery of /data1 in /etc/fstab

let us know how it goes.
Thanks

[Massimo Bianchi]

First step: what chenged since the last time you had the FS ?
a reboot?
a rename ?


Second: please do a "lvdisplay /dev/vg01/lvol1"


and tell us the results.


third: maybe it was used as a swap, and now you forgot the proper name?


check with
swapinfo -tma

Massimo

[Zurida Azah Abdul Rahma_2]

Hi, I've the the following:

1) fsck /dev/vg01/lvol1
Message appreared:cannot open device /dev/vg01/lvol1

2) vgdisplay -v vg01
Everything looks normal

3)fuser -cu /data1
Message appreared:/data1:fuser:could not find file system mounted at /data1

4)Chk in fstab - the entry filesystem /data1 is the there

[Norman_21]

Salams Zuridah,

You might need to try to boot into single user mode and try to mount the file system.
init 1

Also check to make sure that you have the directory /data1 at the root level!

Salamu aliakum
Latif

[T G Manikandan]

Is the VG in available state

check it in the vgdisplay output.
check whether the group is activated.

Else do a

#vgchange -a y /dev/vg01
#mount -a


Thanks

[Massimo Bianchi]

1) fsck /dev/vg01/lvol1
Message appreared:cannot open device /dev/vg01/lvol1

lvdisplay /dev/vg01/lvol1

works???


ll /dev/vg01/lvol1


Is the file there? is a special file?

Massimo

[T G Manikandan]

Try this
Probabily the fstab does not have the vxfs type specified.
#mount -F vxfs /dev/vg01/lvol1 /data1

[Zurida Azah Abdul Rahma_2]

Hi,

I've checked the vg and it is activated.When I do a ll /dev/vg01/lvol1-the files are there.In the /etc/fstab the vxfs type is specified.
Thanks

[Michael Tully]

Please provide the following information.

# fstyp -v /dev/vg01/lvol1

and

the entry from /etc/fstab for this logical volume.

[Zurida Azah Abdul Rahma_2]

Hi Michael,

1) fstyp -v /dev/vg01/lvol1
Message appeared:unknown-fstyp(no matches)

2)In /etc/fstab entry

/dev/vg01/lvol1 /data1 vxfs rw,suid,delaylog,detainlog 0 2

Thanks

[Con O'Kelly]

Hi

Going back to your original post and point 1.
mount /dev/vg01/lvol1 /data1
message /dev/vg01/lvol1:unrecognized filesystem

This implies to me that there is no filesystem on the /dev/vg01/lvol1 or it is badly corrupted.
The fact that you are also unable to run fsck is a worry.
I'm a little surprised at the message from fsck. Can you run it again & post the return code from fsck (run echo $?).

I think you are going to have to look at restoring this filesystem from backup if you have one.
I would recreate the LV(lvcreate) & filesystem (newfs) & then restore the data.

The only other issue is the disk itself is corrupted which someone mentioned earlier in the thread.

Cheers
Con

[Steven E. Protter]

Two options in my opinion:

fsck -F vxfs -o full -y

If the fs was intended to be hfs this might also work with hfs instead of vxfs

I don't think that will work, but its worth a try.

There is no filesystem, so its newfs time.

Make sure you have a backup handy.

newfs -F vxfs

SEP

[Tim Adamson_1]

Did anything change recently on your system? New patches or did you upgrade the vxfs version of the filesystem?


Tim.

[Zurida Azah Abdul Rahma_2]

Hi Con,

I've tried running fsck again. Same message appeared.No device /dev/vg01/lvol1.

[Tim Adamson_1]

If the filesystem was a version 4 type filesystem, then patch PHCO_24635 (11.00) or PHCO_24636 (11.11) fixes a problem like this.

What is the mount(1M) patch you have installed on the system and is the filesystem a version 4???


Tim

[Tim Adamson_1]

Might point out that in all likelihood, you will have to recreate the lvol, newfs, mount and restore the data.

My previous posts were aimed at trying to determine the cause and a way to prevent it in the future.


Tim

[T G Manikandan]

What OS version you are running.

there is a fix for 10.20 version

Also revert as what patch bundles you are running on the system?

Thanks

[Sandro Schaer_1]

difficult case.


ok, let's resume.
- vg is activated and shows no problem with vgdisplay
- /dev/vg01 and /dev/vg01/lvol are available
- fsck shows 'cannot open device'
- mount shows 'cannot mount'


please check the following :

- does /dev/vg01/rlvol1 exist ?
- owner/group/rights of /dev/vg01/lvol1 and /dev/vg01/rlvol1 ?
- any changes done on these files ?

for me it looks like the file /dev/vg01/lvol1 (or rlvol1) is corrupt.

also it might be interesting what 'vgexport -s -p -v -m /tmp/vg01.map /dev/vg01' shows.


have fun
sandro


check owner/group/rights of your /etc/dev/vg01 and /dev/vg01/lvol1

[Massimo Bianchi]

Since we are almost desperate: there is always fsdb, one of the most destructove tool from hpux. i do not know how to use it, but it reads anything.


Also, let's try to read something from the rlvol:

dd if=/dev/vg01/rlvol1 count=50 | xd -t C | more


is there anything ??

Massimo

[Brian Butscher]

Is /dev/vg01/lvol1 on an external disk drive? If so, make sure the disk is turn on and is in a ready state. You may have a bad SCSI connection between the external disk drive and the SCSI adapter.

[Paulo A G Fessel]

Is the LV active?

Take a look at these tests:

[root@berc0004:/etc/opt/ldapux]# lvchange -a n /dev/vg00/lvol1
Logical volume "/dev/vg00/lvol1" has been successfully changed.
[root@berc0004:/etc/opt/ldapux]# fstyp /dev/vg00/lvol1
/dev/vg00/lvol1: No such device or address
[root@berc0004:/etc/opt/ldapux]# fsck /dev/vg00/lvol1
Can't open /dev/vg00/lvol1, errno = 6
[root@berc0004:/etc/opt/ldapux]# lvchange -a y /dev/vg00/lvol1
Logical volume "/dev/vg00/lvol1" has been successfully changed.
[root@berc0004:/etc/opt/ldapux]# fstyp /dev/vg00/lvol1
hfs
[root@berc0004:/etc/opt/ldapux]# fsck /dev/vg00/lvol1
** /dev/vg00/lvol1
** Last Mounted on /stand
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
49 files, 0 icont, 43924 used, 43777 free (81 frags, 5462 blocks)

So you might check whether your lv has been disabled with lvchange -a n. OTOH, I don't even imagine WHY someone would disable the lv.

HTH
Paulo Fessel

[Zurida Azah Abdul Rahma_2]

Hi,

Sandro,
1) I've done -F vxfs -o full /dev/vg01/lvol1
Message appeared: cannot open device /dev/vg01/lvol1

2) Yes. /dev/vg01/rvol1 exist. No changes on the files eg. the ownership etc..

Maximo,
1)I've done dd if=/dev/vg01/rlvol1 count=50|xd -t C|more
Message apperared:xd:Invalid arguement fot -t option
dd:/dev/vg01/rvol1 use a blocksize>= the logical block size 1024.

Paulo,
The lv is not disable.Anyway I tried to disable and enable back. Same thing unable to mount.
When I do a lvchange -a n /dev/vg01/lvol1
Message appeared:"Logical volume" /dev/vg01/lvol1" has been change. Volume group configuration for /dev/vg01 has been saved in /etc/lvmconf /vg01.conf

When I do a lvchange -a y /dev/vg01/lvol1
Message appeared:"Logical volume" /dev/vg01/lvol1" has been change. Volume group configuration for /dev/vg01 has been saved in /etc/lvmconf /vg01.conf