From: Holger P. <wb...@pa...> - 2007-02-19 17:40:44
|
Hi, Tony Del Porto wrote on 05.02.2007 at 17:49:49 [Re: [BackupPC-users] cannot cleanup /var/lib/backuppc/trash]: > > I'm having a similar issue: > > [...] > > Looking at the trash directory, there are a bunch of directories of > varying ages. There are no files in the directories, but they can't > be removed because their link count isn't 2. For example: > > [...] > > [nebula]$ ls -la f%2f/fusr/fshare/femacs/f21.4/flisp/fobsolete > total 8 > drwxr-x--- 5 backuppc backuppc 512 Oct 17 00:53 . > drwxr-x--- 3 backuppc backuppc 6144 Oct 17 00:53 .. > I can't really imagine how that would happen aside from file system corruption. You can't usually create hard links to directories, though I believe some UNIX systems *might* allow root to do such a thing. Have you run an fsck on the file system in question? Can you actually find other directory entries pointing to the same inode ('ls -li fobsolete' and 'find -inum ...')? Chantal Rosmuller wrote on 13.02.2007 at 12:41:55 [Re: [BackupPC-users] cannot cleanup /var/lib/backuppc/trash]: > > On Saturday 03 February 2007 01:26, Holger Parplies wrote: > > [...] > > - immutable bit set on a file (presuming it's an ext2/ext3)? > > Yes the immutable bit is set on some directories below /var/lib/backuppc/trash > but the question is: how did that happen? I have no idea how that would happen, but *as root* you can remove them with 'chattr -i <filenames>' (or even 'chattr -R -i trash'). Since the attribute can only be set or cleared as root, it seems unlikely that BackupPC set it. Maybe file system corruption? I'd run an fsck just in case. Did this happen only once or are you constantly getting more and more immutable directories? Talking about fsck, does anyone know if fsck has problems with BackupPC-pool- type file systems (large link counts, links spread across many directories)? Regards, Holger |