On Wed, Jan 05, 2011 at 00:43:11 +0100, Adam Hamsik wrote: > On Jan,Wednesday 5 2011, at 12:13 AM, Valeriy E. Ushakov wrote: > > > On Tue, Jan 04, 2011 at 23:41:00 +0100, Adam Hamsik wrote: > > > >> Ok I will change it to /var/spool/lock/lvm tomorrow and I will update > >> hier to mention those directories, too. Is that ok ? > > > > IMO, no. As I explained upthread, our /var/spool/lock is specifically > > for uucp, see its permissions. > > > > Please don't create /var/spool/lock/lvm > > Then please suggest another directory which is persistent between > reboots and others are willing to accept it.
I have no idea what lvm locks are and what are they for and I don't remember you ever epxlained that in this thread. You also never explained why you ... would like to have something persistent between reboots. So, does lvm requre locks to persist reboots or not for correct operation? lvm.conf(5) says ... use flocks on files in locking_dir ... to avoid conflicting LVM2 commands running concurrently on a single machine. and flocks don't persist across reboots. -uwe