Re: Unallocated inode

[Paul Ripke <stix%stix.id.au@localhost>]

On Fri, 29 Aug 2014 09:43:39 +0000, Christos Zoulas wrote:
>On Fri, Aug 29, 2014 at 04:56:46PM +1000, Paul Ripke wrote:
>> I'm currently running kernel:
>> NetBSD slave 6.1_STABLE NetBSD 6.1_STABLE (SLAVE) #4: Fri May 23 23:42:30 
>> EST 2014
>> stix@slave:/home/netbsd/netbsd-6/obj.amd64/home/netbsd/netbsd-6/src/sys/arch/amd64/compile/SLAVE
>>  amd64
>> Built from netbsd-6 branch synced around the build time. Over the
>> last year, I have seen 2 instances where I've had cleared inodes,
>> causing obvious errors:
>> 
>> slave:ksh$ sudo find /home -xdev -ls > /dev/null
>> find: /home/netbsd/cvsroot/pkgsrc/japanese/p5-Jcode/pkg/Attic/PLIST,v: Bad 
>> file descriptor
>> find: 
>> /home/netbsd/cvsroot/pkgsrc/print/texlive-pdftools/patches/Attic/patch-ac,v: 
>> Bad file descriptor
>> 
>> fsdb tells me they're "unallocated inode"s, which I can easily fix,
>> but does anyone have any idea what might be causing them? This
>> appears similar to issues reported previously:
>> http://mail-index.netbsd.org/tech-kern/2013/10/19/msg015770.html
>> 
>> My filesystem is FFSv2 with wapbl, sitting on a raidframe mirror
>> over two SATA drives.
>
>Try unmounting it, and then running fsck -fn on it. Does it report
>errors?
>
>christos

Oh, yes, indeed. And fixes them fine:

** /dev/rraid0g
** File system is already clean
** Last Mounted on /home
** Phase 1 - Check Blocks and Sizes
PARTIALLY ALLOCATED INODE I=106999488
CLEAR? [yn] y

PARTIALLY ALLOCATED INODE I=106999489
CLEAR? [yn] y

** Phase 2 - Check Pathnames
UNALLOCATED  I=106999489  OWNER=0 MODE=0
SIZE=0 MTIME=Jan  1 10:00 1970  
NAME=/netbsd/cvsroot/pkgsrc/japanese/p5-Jcode/pkg/Attic/PLIST,v

REMOVE? [yn] y

UNALLOCATED  I=106999488  OWNER=0 MODE=0
SIZE=0 MTIME=Jan  1 10:00 1970  
NAME=/netbsd/cvsroot/pkgsrc/print/texlive-pdftools/patches/Attic/patch-ac,v

REMOVE? [yn] y

** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
FREE BLK COUNT(S) WRONG IN SUPERBLK
SALVAGE? [yn] y

SUMMARY INFORMATION BAD
SALVAGE? [yn] y

BLK(S) MISSING IN BIT MAPS
SALVAGE? [yn] y

5197833 files, 528560982 used, 396039539 free (1740275 frags, 49287408 blocks, 
0.2% fragmentation)

***** FILE SYSTEM WAS MODIFIED *****

Running a second fsck pass comes up clean. What surprises me is that my
machine has been up ~100 days... I find it hard to believe that a power
loss or similar unclean shutdown would generate filesystem corruption
that could sit silent for that long before suddenly emerging.

Cheers,
-- 
Paul Ripke

"Great minds discuss ideas, average minds discuss events, small minds discuss 
people."
-- Disputed: Often attributed to Eleanor Roosevelt. 1948.