On Nov 25, 1:22pm, [email protected] (Paul Ripke) wrote: -- Subject: Re: Unallocated inode
| On Mon, Nov 24, 2014 at 08:01:57PM -0500, Christos Zoulas wrote: | > On Nov 25, 10:59am, [email protected] (Paul Ripke) wrote: | > -- Subject: Re: Unallocated inode | > | > | On Tue, Sep 02, 2014 at 06:15:49PM -0400, Christos Zoulas wrote: | > | > On Sep 2, 2:27pm, [email protected] (Paul Ripke) wrote: | > | > -- Subject: Re: Unallocated inode | > | > | > | > | Yeah, that's what scares me - it was the daily rsync and security cron | > | > | jobs starting to generate errors that alerted me - those inodes must've | > | > | been marked partially allocated only recently. Makes me wish I dumped | > | > | out the contents of those two inodes before running the fsck (maybe | > | > | fsdb should be able to do that?). | > | > | > | > Yes, I think fsdb can do that... | > | | > | Ok, this happened again. And with a tweaked fsdb, I get: | > | | > | fsdb (inum: 125770625)> print | > | command `print | > | ' | > | current inode 125770625: unallocated inode | > | current inode: unallocated | > | I=125770625 MODE=0 SIZE=0 | > | MTIME=Jan 1 10:00:00 1970 [0 nsec] | > | CTIME=Nov 25 10:34:43 2014 [282996506 nsec] | > | ATIME=Jan 1 10:00:00 1970 [0 nsec] | > | OWNER=root GRP=wheel LINKCNT=0 FLAGS=0x0 BLKCNT=0x0 GEN=0x0 | > | | > | Nothing was being touched in that part of the filesystem at the time... | > | I think the CTIME may be related to me mv'ing the file elsewhere, the | > | time somewhat matches. I find this somewhat scary. For reference: | > | > Is that inode accessible from the filesystem? Can you reproduce this | > running find on that subtree? | | Nope, it's inaccessible - again, it was the daily security reports | that alerted me: | | slave:ksh$ find /home/tmp > /dev/null | find: /home/tmp/badfile: Bad file descriptor | | (I renamed the inaccessible file into a convenient location as I | couldn't figure out in 10 seconds how to cd thru directories with | spaces in the names in fsdb...) Looks like a filesystem race/bug, but i am not sure what your usage pattern is that triggers it. christos
