Bug#488115: gc_approx tries to remove lost+found if cache is a separate filesystem

2008-06-26 Thread Petr Rockai
Hi, Eric Cooper <[EMAIL PROTECTED]> writes: > I don't want to add code just to check for the special case where > approx's cache directory is the root of an ext2/3 filesystem. An easy > workaround (no chown required) is to make a top-level directory, say > "cache", in your dedicated filesystem, a

Bug#488115: gc_approx tries to remove lost+found if cache is a separate filesystem

2008-06-26 Thread Eric Cooper
On Thu, Jun 26, 2008 at 03:54:45PM +0200, Petr Rockai wrote: > I have just created a filesystem for approx cache. First of all, gc_approx > fails if it doesn't own lost+found. I chowned it, and now it tries to unlink > lost+found (which it is denied). It sort of works now, but it would be better >

Bug#488115: gc_approx tries to remove lost+found if cache is a separate filesystem

2008-06-26 Thread Petr Rockai
Package: approx Version: 3.2.0+b1 Severity: normal Hi, I have just created a filesystem for approx cache. First of all, gc_approx fails if it doesn't own lost+found. I chowned it, and now it tries to unlink lost+found (which it is denied). It sort of works now, but it would be better to not need