topic Re: Filesystem mount order in Operating System - HP-UX

Filesystem mount order

Albert Smith_1 — Mon, 22 May 2006 15:04:22 GMT

I have a 11i system that is current on all patches and is attached to an EMC Clariion CX700.

My problem is this. It seems that the filesystems are getting mounted out of order. IE. VG00 is half-way mounted then VG03 is mounted then the balance of VG00. From what I can see it looks like it is mount the file systems in a descending alphabetical order.

Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1073152 45362 963609 4% /
/dev/vg00/lvol1 512499 37597 423652 8% /stand
/dev/vg00/lvol8 9437184 602872 8696728 6% /var
/dev/vg00/lvol7 8388608 1320732 6847100 16% /usr
/dev/vg03/lvol28 33603584 17411456 16065632 52% /upg28
/dev/vg03/lvol27 33603584 28675520 4889568 85% /upg27
/dev/vg03/lvol26 33603584 22531464 10985624 67% /upg26
/dev/vg03/lvol25 48971776 28128936 20683808 58% /upg25
/dev/vg03/lvol24 33603584 20483464 13017624 61% /upg24
/dev/vg03/lvol23 33603584 22019496 11493592 66% /upg23
/dev/vg03/lvol22 33603584 20483472 13017616 61% /upg22
/dev/vg03/lvol21 33603584 17411448 16065640 52% /upg21
/dev/vg03/lvol20 33603584 18435448 15049640 55% /upg20
/dev/vg03/lvol19 33603584 19459448 14033640 58% /upg19
/dev/vg03/lvol18 33603584 22531480 10985608 67% /upg18
/dev/vg03/lvol17 33603584 21968328 11544360 66% /upg17
/dev/vg03/lvol16 33603584 24579504 8953584 73% /upg16
/dev/vg03/lvol15 33603584 20915496 12588992 62% /upg15
/dev/vg03/lvol14 33603584 18435448 15049640 55% /upg14
/dev/vg03/lvol13 33603584 16889256 16583752 50% /upg13
/dev/vg03/lvol12 33603584 22531480 10985608 67% /upg12
/dev/vg03/lvol11 33603584 22531488 10985600 67% /upg11
/dev/vg03/lvol10 33603584 19733160 13762120 59% /upg10
/dev/vg03/lvol9 8429568 3182 8163068 0% /upg09
/dev/vg03/lvol8 8429568 8195266 226986 97% /upg08
/dev/vg03/lvol7 8429568 8210922 211820 97% /upg07
/dev/vg03/lvol6 16801792 6176392 10459500 37% /upg06
/dev/vg03/lvol5 16801792 6245008 10391900 38% /upg05
/dev/vg03/lvol4 16801792 16387356 407968 98% /upg04
/dev/vg03/lvol3 16801792 16387356 407968 98% /upg03
/dev/vg03/lvol2 8429568 7678458 727642 91% /upg02
/dev/vg03/lvol1 8429568 6362386 2002646 76% /upg01
/dev/vg00/lvol6 2097152 536530 1463125 27% /tmp
/dev/vg00/lvol5 3547136 768100 2692290 22% /opt
/dev/vg00/lvol4 1048576 1456 981735 0% /home

# mount -p
/dev/vg00/lvol3 / vxfs log 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 0
/dev/vg00/lvol8 /var vxfs delaylog 0 0
/dev/vg00/lvol7 /usr vxfs delaylog 0 0
/dev/vg03/lvol28 /upg28 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol27 /upg27 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol26 /upg26 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol25 /upg25 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol24 /upg24 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol23 /upg23 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol22 /upg22 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol21 /upg21 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol20 /upg20 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol19 /upg19 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol18 /upg18 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol17 /upg17 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol16 /upg16 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol15 /upg15 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol14 /upg14 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol13 /upg13 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol12 /upg12 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol11 /upg11 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol10 /upg10 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol9 /upg09 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol8 /upg08 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol7 /upg07 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol6 /upg06 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol5 /upg05 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol4 /upg04 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol3 /upg03 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol2 /upg02 vxfs delaylog,nodatainlog 0 0
/dev/vg03/lvol1 /upg01 vxfs delaylog,nodatainlog 0 0
/dev/vg00/lvol6 /tmp vxfs delaylog 0 0
/dev/vg00/lvol5 /opt vxfs delaylog 0 0
/dev/vg00/lvol4 /home vxfs delaylog 0 0

# mount -v
/dev/vg00/lvol3 on / type vxfs log on Mon May 22 15:51:16 2006
/dev/vg00/lvol1 on /stand type hfs defaults on Mon May 22 15:51:18 2006
/dev/vg00/lvol8 on /var type vxfs delaylog on Mon May 22 15:51:30 2006
/dev/vg00/lvol7 on /usr type vxfs delaylog on Mon May 22 15:51:30 2006
/dev/vg03/lvol28 on /upg28 type vxfs delaylog,nodatainlog on Mon May 22 15:51:30 2006
/dev/vg03/lvol27 on /upg27 type vxfs delaylog,nodatainlog on Mon May 22 15:51:30 2006
/dev/vg03/lvol26 on /upg26 type vxfs delaylog,nodatainlog on Mon May 22 15:51:30 2006
/dev/vg03/lvol25 on /upg25 type vxfs delaylog,nodatainlog on Mon May 22 15:51:30 2006
/dev/vg03/lvol24 on /upg24 type vxfs delaylog,nodatainlog on Mon May 22 15:51:30 2006
/dev/vg03/lvol23 on /upg23 type vxfs delaylog,nodatainlog on Mon May 22 15:51:30 2006
/dev/vg03/lvol22 on /upg22 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol21 on /upg21 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol20 on /upg20 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol19 on /upg19 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol18 on /upg18 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol17 on /upg17 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol16 on /upg16 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol15 on /upg15 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol14 on /upg14 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol13 on /upg13 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol12 on /upg12 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol11 on /upg11 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol10 on /upg10 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol9 on /upg09 type vxfs delaylog,nodatainlog on Mon May 22 15:51:31 2006
/dev/vg03/lvol8 on /upg08 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol7 on /upg07 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol6 on /upg06 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol5 on /upg05 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol4 on /upg04 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol3 on /upg03 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol2 on /upg02 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg03/lvol1 on /upg01 type vxfs delaylog,nodatainlog on Mon May 22 15:51:32 2006
/dev/vg00/lvol6 on /tmp type vxfs delaylog on Mon May 22 15:51:32 2006
/dev/vg00/lvol5 on /opt type vxfs delaylog on Mon May 22 15:51:32 2006
/dev/vg00/lvol4 on /home type vxfs delaylog on Mon May 22 15:51:33 2006

Can the mount order be adjusted? My fstab is correct:

# cat /etc/fstab
# 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 /home vxfs delaylog 0 2
/dev/vg00/lvol5 /opt vxfs delaylog 0 2
/dev/vg00/lvol6 /tmp vxfs delaylog 0 2
/dev/vg00/lvol7 /usr vxfs delaylog 0 2
/dev/vg00/lvol8 /var vxfs delaylog 0 2

/dev/vg03/lvol1 /upg01 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol2 /upg02 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol3 /upg03 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol4 /upg04 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol5 /upg05 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol6 /upg06 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol7 /upg07 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol8 /upg08 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol9 /upg09 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol10 /upg10 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol11 /upg11 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol12 /upg12 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol13 /upg13 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol14 /upg14 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol15 /upg15 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol16 /upg16 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol17 /upg17 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol18 /upg18 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol19 /upg19 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol20 /upg20 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol21 /upg21 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol22 /upg22 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol23 /upg23 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol24 /upg24 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol25 /upg25 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol26 /upg26 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol27 /upg27 vxfs delaylog,nodatainlog 0 3
/dev/vg03/lvol28 /upg28 vxfs delaylog,nodatainlog 0 3

Thanks for any help offered.

Re: Filesystem mount order

Ninad_1 — Mon, 22 May 2006 15:44:02 GMT

I believe that the mount order usually is precisely as mentioned in /etc/fstab - I wonder why its showing the timestamps which shows what you have explained. But I ma sure that the filesystems are mounted as per /etc/fstab order. In fact that the reason its required to specify the mount points in ascending order - in the sense if you have filesystems mounted at say /dir1 /dir/dir2 , then you need to mention /dir1 first as another filesystem is to be mounted at /dir1/dir2.

Regards,
Ninad

Re: Filesystem mount order

Josiah Henline — Mon, 22 May 2006 16:50:31 GMT

The file systems are mounted as the system is booting by using "/sbin/mountall -l -m". It is part of /sbin/init.d/localmount startup script.

Re: Filesystem mount order

Albert Smith_1 — Mon, 22 May 2006 16:57:08 GMT

How does the mountall affect the order they are mounted in? The way the FileSystems should mount, should be by the order they are listed in /etc/fstab where / /stand need to be the first two listed.

Re: Filesystem mount order

Kevin Wright — Mon, 22 May 2006 17:11:53 GMT

man fstab will provide the information on mount order options in the file

Re: Filesystem mount order

Albert Smith_1 — Mon, 22 May 2006 20:21:16 GMT

After the posting I thought it might be the pass number. But I set the pass number to 0 and I have the same problem.

Re: Filesystem mount order

Senthil Kumar .A_1 — Mon, 22 May 2006 23:06:55 GMT

Hi Albert,

The "pass number" has nothing to do with mount order. It only determines the order in which fsck is performed while boot or using mountall command. The mount order should be governed by the order in which it is mentioned in fstab file. Anyway I will examine the "mount" startup script to see whats going on.

Regards,
Senthil Kumar .A

Re: Filesystem mount order

Albert Smith_1 — Tue, 23 May 2006 05:09:35 GMT

The mount startup script is doing a mountall -l -m. And I agree it should be mounted in order they are presented in the fstab. But according the mount -p and the mount -v and the mnttab that definitly isn't occuring.

Maybe I should open a call to HP about this.

Re: Filesystem mount order

Jannik — Tue, 23 May 2006 08:34:01 GMT

To see the correct mount time use:
strings /etc/mnttab

This i updated automatically with mount and unmount.

/etc/mnttab is accessed by programs that use getmntent() (see getmntent(3X)), It should never be manually edited, nor should setmnt ever be used to create invalid entries in /etc/mnttab (see setmnt(1M)).

Re: Filesystem mount order

Albert Smith_1 — Tue, 23 May 2006 08:38:58 GMT

Please see the orignial post. Here is an updated copy of the mnttab with the modified fsck pass:

# cat /etc/mnttab
/dev/vg00/lvol3 / vxfs log 0 1 1148335719
/dev/vg00/lvol1 /stand hfs defaults 0 0 1148335720
/dev/vg00/lvol8 /var vxfs delaylog 0 0 1148335731
/dev/vg00/lvol7 /usr vxfs delaylog 0 0 1148335732
/dev/vg03/lvol28 /upg28 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol27 /upg27 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol26 /upg26 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol25 /upg25 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol24 /upg24 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol23 /upg23 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol22 /upg22 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol21 /upg21 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol20 /upg20 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol19 /upg19 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol18 /upg18 vxfs delaylog,nodatainlog 0 0 1148335732
/dev/vg03/lvol17 /upg17 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol16 /upg16 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol15 /upg15 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol14 /upg14 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol13 /upg13 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol12 /upg12 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol11 /upg11 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol10 /upg10 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol9 /upg09 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol8 /upg08 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol7 /upg07 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol6 /upg06 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol5 /upg05 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol4 /upg04 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol3 /upg03 vxfs delaylog,nodatainlog 0 0 1148335733
/dev/vg03/lvol2 /upg02 vxfs delaylog,nodatainlog 0 0 1148335734
/dev/vg03/lvol1 /upg01 vxfs delaylog,nodatainlog 0 0 1148335734
/dev/vg00/lvol6 /tmp vxfs delaylog 0 0 1148335734
/dev/vg00/lvol5 /opt vxfs delaylog 0 0 1148335734
/dev/vg00/lvol4 /home vxfs delaylog 0 0 1148335734

As you can see VG03 is mounting then the balance of vg00 and it's in a descending order not how it is placed in the fstab.

Re: Filesystem mount order

Jannik — Wed, 05 Jul 2006 05:34:56 GMT

I would look at commands like:

setmnt and syncer

You could use you own mnt file and direct it into the mount file "setmnt < /tmp/file.mnt" again look at the man pages for setmnt.

remember to look at the warnings.

Re: Filesystem mount order

Bill Hassell — Wed, 05 Jul 2006 06:26:13 GMT

The mount order is undefined per the mount(1m) man page. You might create a wrapper for mount -a to perform each mount one at a time which then appends each mount to the current list. Since this is purely aesthetics for df, bdf and mount displays, it will likely not be changed. Note that information about a specific mountpoint can be queried with df and bdf:

bdf /tmp
df /var

You can even query an individual file to determine the mountpoint:

bdf /usr/olod/bin/sh

No grep is needed.