Re: Odd file in /lost+found after softupdate inconsistency in fsck

2008-03-06 Thread Peter Jeremy
On Thu, Mar 06, 2008 at 04:22:09PM +0900, Tod McQuillin wrote: >So, it's a shapshot -- is it still usable? Is it safe to delete it? If snapinfo can't find it then it's not usable. In either case, it's safe to delete it. >I'm not in the habit of making snapshots ... but it might have come from a

Re: Odd file in /lost+found after softupdate inconsistency in fsck

2008-03-05 Thread Tod McQuillin
On Thu, 6 Mar 2008, Peter Jeremy wrote: On Wed, Mar 05, 2008 at 09:43:15PM +0900, Tod McQuillin wrote: /home/lost+found# ls -lksh total 24432 24432 -r 1 root operator40G Mar 5 20:12 #005 It is 40G in size but only occupies 24432k on disk, so it is a sparse file. The file p

Re: Odd file in /lost+found after softupdate inconsistency in fsck

2008-03-05 Thread Andriy Gapon
on 05/03/2008 14:43 Tod McQuillin said the following: > Hi all, > > My server froze up tonight after a 2 month uptime running 6.3-PRERELEASE > from Dec 28 2007. > > I had to fsck /home by hand because of an inconsistency fsck couldn't > repair automatically -- something to do with an unexpected

Re: Odd file in /lost+found after softupdate inconsistency in fsck

2008-03-05 Thread Peter Jeremy
On Wed, Mar 05, 2008 at 09:43:15PM +0900, Tod McQuillin wrote: >/home/lost+found# ls -lksh >total 24432 >24432 -r 1 root operator40G Mar 5 20:12 #005 > >It is 40G in size but only occupies 24432k on disk, so it is a sparse file. The file permissions and sparseness matches a sna

Odd file in /lost+found after softupdate inconsistency in fsck

2008-03-05 Thread Tod McQuillin
Hi all, My server froze up tonight after a 2 month uptime running 6.3-PRERELEASE from Dec 28 2007. I had to fsck /home by hand because of an inconsistency fsck couldn't repair automatically -- something to do with an unexpected softupdate inconsistency. After that, I ended up with some fil