Strange file system problems

[Mike_305]

Hi,

We have a file system called /test/test.mc and the problem that I am running into is when I reboot the system this one file system doesn't get mounted automatically. I can mount manually without any problems. I can cut and past the entry from fstab and tested out the syntax on our test system to make sure it???s correct or not and it works fine on test system and the same syntax doesn???t work on my production system.

Also, when I do mount ???v command it shows that it???s using ???log??? instead of ???delaylog???.

Entry in fstab is as below:

/dev/vg01/lvol1 /test/test.mc vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2

And mount ???v reads:

/dev/vg01/lvol1 on /test/test.mc type vxfs log on Sat Aug 24 11:53:3 8 2002

If I do ???umount ???a??? all the file systems gets unmounted but ???mount ???a??? this one file system doesn???t get mounted.

Thanks in advance.

Thanks,

Mike

[harry d brown jr]

Please post your entire fstab because I want to see when /test is mounted.

live free or die
harry

[Jeff Schussele]

Hi Mike,

What does lvdisplay -v /dev/vg01/lvol1 show?

Do this before you manually mount.

I'd suspect a problem with the LV. Maybe even something obscure like a dupe minor number. Check your /dev/vg* dirs thoroughly.

Also check you /etc/lvmrc file in case it's excluding it.

Rgds,
Jeff

[Mike_305]

Hi Harry,

Their is no /test mount point, when I created this file system, the way I did is in sam where is says mount point, I put /test/test.mc

Thanks,

Mike

# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1
/dev/vg00/lvol4 /tmp vxfs delaylog 0 2
/dev/vg00/lvol5 /home vxfs delaylog 0 2
/dev/vg00/lvol6 /opt vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2
/dev/vg01/lvol1 /test/test.mc vxfs rw,suid,nolargefiles,delaylog,dat
ainlog 0 2 # entry from irvfinua

[harry d brown jr]

Mike,

/test exists, right?

Also, the paste was just screwed up, the fstab file doesn't look like that at the end of the file does it?

When you do a

vgdisplay -v vg01

what does it return??

what does

ls -l /dev/vg01

return ??

live free or die
harry

[Michael Tully]

Also include the output of:

# fstyp -v /dev/vg01/lvol1

[James R. Ferguson]

Hi Mike:

The 'delaylog' mount option requires the Online JFS license. If you do not have this Online component, I would expect the mount operation to fail.

Regards!

...JRF...

[harry d brown jr]

Mike,

What's going on with this one??

live free or die
harry

[Mike_305]

Hi,

Sorry Harry could not get back to you last night.

I have other file system with the same type of setup, for example /test/ora and they mount fine, with out any problems.

Michael - output from fstyp;

# fstyp -v /dev/testvg/testmclv
vxfs
version: 3
f_bsize: 8192
f_frsize: 1024
f_blocks: 1024000
f_bfree: 1022643
f_bavail: 958728
f_files: 255692
f_ffree: 255660
f_favail: 255660
f_fsid: 1073807361
f_basetype: vxfs
f_namemax: 254
f_magic: a501fcf5
f_featurebits: 0
f_flag: 0
f_fsindex: 5
f_size: 1024000

I am still working on other outputs and will post them soon.

Appreciate all your help.

Thanks,

Mike

[Mike_305]

The question that I have is in /etc/fstab file its define as delaylog and when I run ???mount ???v??? command it shows ???log??? not delaylog? When I compare with other file systems if the file system is define as delaylog then in ???mount ???v??? output it shows delaylog. Any idea.

Entry from fstab;

/dev/testmcvg/testmclv /test/test.mc vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2

Entry from ???mount ???v???

/dev/testmcvg/testmclv on /test/test.mc type vxfs log on Sat Aug 24 11:53:38 2002

******************************************************************

I have also attach all the output you have requested.

JRF ??? Yes we do have online jfs.

Harry; below the output you requested.

# vgdisplay -v /dev/testmcvg
--- Volume groups ---
VG Name /dev/testmcvg
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 1
Open LV 1
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 8684
VGDA 2
PE Size (Mbytes) 4
Total PE 8681
Alloc PE 250
Free PE 8431
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/testmcvg/testmclv
LV Status available/syncd
LV Size (Mbytes) 1000
Current LE 250
Allocated PE 250
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c3t15d0
PV Status available
Total PE 8681
Free PE


# ll /dev/testmcvg
total 0
crw-r--r-- 1 root sys 64 0x010000 Aug 29 09:20 group
crw-r----- 1 root sys 64 0x010001 Aug 29 09:20 rtestmclv
brw-r----- 1 root sys 64 0x010001 Aug 29 09:20 testmclv
#

Jeff ??? the output you requested.

# lvdisplay -v /dev/testmcvg/testmclv
--- Logical volumes ---
LV Name /dev/testmcvg/testmclv
VG Name /dev/testmcvg
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 1000
Current LE 250
Allocated PE 250
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c3t15d0 250 250

--- Logical extents ---
LE PV1 PE1 Status 1
0000 /dev/dsk/c3t15d0 0000 current
0001 /dev/dsk/c3t15d0 0001 current
0002 /dev/dsk/c3t15d0 0002 current
0003 /dev/dsk/c3t15d0 0003 current

[John Poff]

Mike,

Have you looked in your /etc/rc.log file to see if there are any error messages at boot when the rc scripts try to activate the vg01 volume group and mount that filesystem? Also, check your /etc/lvmrc file and see if the AUTO_VG_ACTIVATE is set for 1 or 0. If you have that off, you will need to add an entry in the custom_vg_activation function at the bottom of the lvmrc file. Usually you see this on boxes in a ServiceGuard environment. It catches me here every so often.

JP

[Mike_305]

Hi John,

Looking at /etc/rc.log it doesn???t like mount option. I am not sure what mount option are incompatible.

AUTO_VG_ACTIVATE=1

and rc.log has this entry;

mountall: cannot mount /dev/testmcvg/testmclv
mountall: diagnostics from mount vxfs mount: mount option(s) incompatible with file system /dev/testmcvg/testmclv
checking quotas

Thanks,

Mike

[John Poff]

Mike,

Two questions. First, (back to James' point earlier), are you running Online JFS on this system? Does 'swlist -l bundle | grep -i jfs' return something like this:

B3929BA B.11.00 HP OnLineJFS (Advanced VxFS)

Second, did you create the filesystem as a vxfs filesystem? (newfs -F vxfs /dev/vg01/rlvol1)

(I typed in this reply once and hit submit and it never showed up, so I'm trying it again.)

JP

[Jeff Schussele]

Hi (again) Mike,

Are you able to activate/deactivate the VG w/o incident?
If you

vgchange -a y /dev/testmcvg

Does it activate OK. If not & it's possibly been in an MC/SG cluster you may need to

vgchange -c n /dev/testmcvg

To make in cluster unaware.

Also I'm not sure if this can cause the problem you're seeing, but I'm wondering if it had been set FOR largefiles at some point in the past - try this

fsadm -F vxfs -o nolargefiles /dev/testmcvg/testmclv

To insure it's set for nolargefiles.

Rgds,
Jeff

[Mike_305]

Hi John,

Yes, I am running online JFS.

B3929BA B.11.00 HP OnLineJFS (Advanced VxFS)

Yes, it's a VXFS file system.

When I do "fstyp ???v /dev/testmcvg/testmclv" shows as vxfs file system. I am not sure how this file system was created but fstyp reports as vxfs file system.

No cluster is running on this system.

Yes, it???s set as nolargefiles.

FSTAB entry:

/dev/testmcvg/testmclv /test.mc vxfs rw,suid,nolargefiles,delaylog,datainlog 0 2

Thanks,

Mike

[John Poff]

Mike,

I've gotten bitten by /etc/fstab entries before also. I remember working through it by going back to the simplest entry for the filesystem and trying 'mount -a' on it. If that worked, I unmounted the filesystem, edited the fstab file, added another option, and tried mounting it again until it blew up.

At least that might point you to the particular option that 'mount' doesn't like. I'm betting on the largefiles option.

JP

[James Murtagh]

Hi Mike,

This usually happens when the filesystem mount options in the fstab conflict with how the filesystem is set up. Can you confirm largefiles is not set on by running :

fsadm -F vxfs /dev/vg01/rlvol1

If this is OK, try mounting the filesystem manually then remounting with :

mount -F vxfs -o remount /dev/vg01/lvol1

Then try unmounting and run mount -a to see if this worked.

When you are mounting this manually, what options are you specifying? If you are not using any, the system will use the defaults, which is probably why you have "log" option after running mount -v.

Regards,

James.

[James R. Ferguson · Accepted solution]

Hi Mike:

To see the largefile bit setting unmount the filesystem and do:

# fsadm /dev/vg01/rlvol1

Either 'largefiles' or 'nolargefiles' will be returned.

Regards!

...JRF...

[Mike_305]

Hi,

I got the answer to the problem. Thanks to all of you. YOU GUYS ARE GREAT.

When I do ???fsadm /dev/testmcvg/rtestmclv??? it reports as below.

nomultifsets
largefiles

and in /etc/fstab it???s marked as ???nolargefiles???, I think that is the problem.

On my next reboot I will change the entry and test the mount point out.

Once again thanks for your help in testing this issue.

Thanks,

Mike

[Jeff Schussele]

Sounds familiar......

[Mike_305]

Thanks