On Wednesday 06 January 2010 11:14, Richard Troth wrote:
>For reasons that I won't go into, we found that LVM might get started
>before /var is mounted. (Activating volume groups; stuff like that.)
>But the stock locking directory for LVM is /var/lock/lvm. I've tried
>a couple of variants ... with no problems ... but am again asking the
>group for greater wisdom.
>
>Does anyone see a problem with using /dev/shm as the LVM lock dir?
>(Is always writable, but is shared by other things.)
>
>How about /etc/lvm/lock? (Needs to be created. Might not always be
> writable.)
If you're doing a vgscan, you'll need /etc/lvm writable as well as any lock
directory. I didn't try using /dev/shm, but I suspect it would be OK as long
as you're using pathnames no one else would use.
I do something similar with shared DASD, but I use a tmpfs for this. Mount it
on /var, make the lvm/lock subdirectories, and bind-mount another
sub-directory onto /etc/lvm if /etc isn't writable either. Then the LVM
tools can do their stuff.
Another option (with LVM2) is to use the --ignorelockingfailure option of
vgscan. Because you're doing this during the boot sequence, you have
complete control and nothing else will be running an LVM tool, so you don't
really need the locks, right?
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software
275 Grove Street · Newton, MA 02466-2272 · USA
Tel: +1.617.614.4321
Email: [email protected]
Web: www.rocketsoftware.com
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
