Is having multiple directories assigned to LVM in a directory a bad thing?

Latest response

Working thru an issue today and noticed that there are two directories:

/var
/var/log/audit

I noticed that:

/var is part of /dev/VolGroup06/LogVol00

and

/var/log/audit is part of /dev/VolGroup04/LogVol00

So my question is having a subdirectory part of a LVM while the root directory is also part of an LVM, will this cause an issue or problem for the OS?

thanks

CM
Log in to join the conversation

Responses

R. Hinton's picture Guru 6827 points
2 September 2015 1:28 PM

I use this sort of LVM setup, with /var/ and /var/log/audit (and in some cases, also /var/log, and /var/lib/tomcat7 for heavy tomcat instantiations)

I usually set up my logical volumes to be named "var" instead of ""LogVol00", or "audit" instead of "LogVolXY" and so forth. I know of one person who is very adept and contributes in this forum who names their volume groups after the type of tiered storage, such as tier1 (probably fast storage), or "tier2" after storage that is not as fast as tier1 (that link is worth reading).

I've created raid10 raid arrays for certain customers, and made the volume group "raid10" and the logical volume "raid10" as well. Chances are there is an even better naming method than what I have suggested, and it may be good to devote some thought to names.

I've been using most of what's called a "STIG" partitioning, and overwhelmingly it works fine in my environments.

Lastly, see Tom Jones' comments in this discussion https://access.redhat.com/discussions/1571653 about /var/tmp before doing that. [edited Tom Jones made a couple of different posts that are salient in that matter in that discussion, and also elsewhere that I can not immediately find].

CM Expert 1105 points
2 September 2015 1:50 PM

The reason I'm asking this question is that I have a RHEL VM where I've lost a LVM (VolGroup06) and I'm not able to mount it, or view it (using vgs or vgscan or using vgchange -ay VolGroup06).

Working with Red Hat Phone Support they thought that maybe because of having those different LVMs with one partition was causing the issue.

With that I searched around online and wasn't able to find any information on that so that lead me to ask the question here.

Since I'm part of DoD, I'm using STIG Partitioning and each partition based on the needs, I'm using LVM as well.

Also I'm still using VolGroup and LogVol for my naming conventions. I guess its going to take me more time to come up with maybe something better?

thanks

R. Hinton's picture Guru 6827 points
2 September 2015 2:00 PM

I too am using STIG partitioning, similar reasons. I've personally used several logical volumes assigned to one volume group for stig partitioning. I can not think of an instance where I've suffered the symptoms you've mentioned.

Regarding naming conventions, There are numerous methods for naming, I've found something that seems sensible for my environment/conditions, however there's some more ideas in those links/discussions I provided. I just got tired of uselessly named volume and logical volume names, and attempted to come up with a naming convention that gives me some clue as to what it really is instead of "VolGroupXY" and "LogVolXY". There's probably folks who use superior methods to mine, and I've learned from some salient examples such as the discussions I've linked to (previous posts, this topic) with very astute people such as PixelDrift and Tom Jones, James Radke, among others...

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.