Bug#562234: Cache file location in violation of FHS

2010-12-09 Thread Alasdair G Kergon
On Thu, Dec 09, 2010 at 08:46:50AM +0100, Goswin von Brederlow wrote: In what case does it break? That's the wrong question:) You should ask: Under what conditions are its hard-coded assumptions about LVM metadata true? Alasdair -- To UNSUBSCRIBE, email to

Bug#562234: Cache file location in violation of FHS

2010-12-09 Thread Goswin von Brederlow
Alasdair G Kergon a...@redhat.com writes: On Thu, Dec 09, 2010 at 08:46:50AM +0100, Goswin von Brederlow wrote: In what case does it break? That's the wrong question:) You should ask: Under what conditions are its hard-coded assumptions about LVM metadata true? Alasdair Way to avoid

Bug#562234: Cache file location in violation of FHS

2010-12-08 Thread Goswin von Brederlow
Hi, the current cache file location (/etc/lvm) makes problems with a read-only / so something has to be done. On the other hand configuring it to /var/backups/ seems to work just fine all around. No problems so far even during boot (when /var isn't there yet). Since grub2 can now too boot

Bug#562234: Cache file location in violation of FHS

2010-12-08 Thread Alasdair G Kergon
/etc/lvm has several functions. Read-only config - leave it where it is. cache_dir - in general can be cleared on each boot so a tmpfs location would be fine or /var/cache or something Metadata backups ideally would be stored persistently outside lvm but otherwise /var/backups sounds OK (The

Bug#562234: Cache file location in violation of FHS

2010-12-08 Thread Goswin von Brederlow
Alasdair G Kergon a...@redhat.com writes: /etc/lvm has several functions. Read-only config - leave it where it is. Obviously. I was only meaning the writable parts. cache_dir - in general can be cleared on each boot so a tmpfs location would be fine or /var/cache or something Maybe

Bug#562234: Cache file location in violation of FHS

2010-06-24 Thread Christoph Anton Mitterer
Hi. I'm not sure whether it's a good idea to make such exceptions to FHS. I mean that would dilute it more and more. Alasdair, could you please tell us which concrete problems you've had? btw: /boot is not always on non-LVM or really available. I for example have my /boot on an USB-stick...

Bug#562234: Cache file location in violation of FHS

2009-12-30 Thread Paul Menzel
Dear Debian hackers, Am Donnerstag, den 24.12.2009, 15:52 +1300 schrieb martin f krafft: /etc/lvm/cache should live in /var, not /etc, since it is automatically maintained, and not a configuration file anyhow. If it cannot live in /var because that might not be mounted, use /lib/init/rw and

Bug#562234: Cache file location in violation of FHS

2009-12-30 Thread Alasdair G Kergon
If Debian wants to have a go at moving these files about, there are settings available in lvm.conf to do that. But it's an unnecessary overhead, not trivial to get the scripts right, introduces new failure modes (and recovery paths) and you might do better discussing revising the FHS to cater

Bug#562234: Cache file location in violation of FHS

2009-12-23 Thread martin f krafft
Package: lvm2 Version: 2.02.54-1 Severity: serious /etc/lvm/cache should live in /var, not /etc, since it is automatically maintained, and not a configuration file anyhow. If it cannot live in /var because that might not be mounted, use /lib/init/rw and then later move it. -- System Information: