Defining mount points

[Millicent Howze-Simmons]

I am trying to figure out how /usr, /tmp, /home, /var and /opt mount points are still accessible even though when you do a BDF only three display. Can someone show me how this was done?
------------:
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 67158016 29303096 37565800 44% /

/dev/vg00/lvol1 298928 55408 213624 21% /stand

/dev/vg01/lvol1 71671808 14005160 57216328 20% /altboot

[Robert-Jan Goossens]

Your /usr, /tmp, /home, /var and /opt are probably directories inside the / (root) filesystem. The sysadmin who has setup this server, created one very large root filesytem.

Regards,
Robert-Jan

[Millicent Howze-Simmons]

Not sure how to do that..
I know I too create directories under /(root) but how do you move a whole filesystem ... or it appears that way. These mount points are still under one Volume Group but are not shown when displaying "BDF"

[spex]

$ bdf
will show you which filesystem (remember, directories are also files) belongs to.

[Patrick Wallek · Accepted solution]

That's the thing. They are NOT actually mount points in the sense you are thinking.

If you cd into /opt and the do a 'bdf .' you will likely see:

/dev/vg00/lvol3 67158016 29303096 37565800 44% /

I don't think it would be possible to do this , at least not easily, on a running system. This almost had to be done when the system was installed.

In the install interface you can control what mountpoints are built and at what size. The person that installed this machine remove all mount points except / and /stand. He/she then increased the size of / to what it is. When the directories were created they were just created under / and NOT as separate mount points.

[Geoff Wild]

Looks like /usr, /tmp, /home, /var and /opt are not mount points - only directories...

What do you see with:

vgdisplay -v vg00

grep vg00 /etc/fstab

Rgds...Geoff

[Millicent Howze-Simmons]

Patrick, THANK YOU. I believe I will start from scratch and do just that.

[A. Clay Stephenson]

This was a fairly common configuration for workstations when disks were small but for servers this was always a bad way (if legal) to configure a box. Essentially, you have one large root filesystem with the the "file systems" you are looking for as directories rather than mount points. This was the way UNIX boxes were done about 20 years ago but it's pretty much state of the art stupid now.

[A. Clay Stephenson]

If the machine is configured (except for the file system layouts) pretty much as you want it then you might consider taking an Ignite image and then doing an guided restore which will allow you to layout the file systems as you like. This will preserve your kernel tunings, printer configurations, dns settings, patches, and installed software while allowing you to fix the other problems.

[Millicent Howze-Simmons]

Stephen,
Thanks for your response.
I am setting this system up per private party software instructions (special reasons).