Ticket #7 (closed bug: fixed)

Opened 8 months ago

Last modified 4 months ago

faulty inode count warning

Reported by: carns@mcs.anl.gov Assigned to: carns
Priority: minor Component: kmod
Version: HEAD Keywords: inode alloc dealloc
Cc:

Description

The message is meant as a safety check to make sure that we properly account for all inodes that the kernel module allocates (which is a good thing). However, it keeps the counters globally rather than per super block. This means that you can trigger the message by just doing this: 

mount -t pvfs2 tcp://localhost:3334/pvfs2-fs /mnt/pvfs2
mount -t pvfs2 tcp://localhost:3334/pvfs2-fs /mnt/pvfs2-a
mount -t pvfs2 tcp://localhost:3334/pvfs2-fs /mnt/pvfs2-b
mount -t pvfs2 tcp://localhost:3334/pvfs2-fs /mnt/pvfs2-c

umount /mnt/pvfs2-c
umount /mnt/pvfs2-b
umount /mnt/pvfs2-a
umount /mnt/pvfs2

dmesg

[92701.204000] pvfs2_kill_sb: (WARNING) number of inode allocs (135) != number of inode deallocs (132)
[92702.704000] pvfs2_kill_sb: (WARNING) number of inode allocs (135) != number of inode deallocs (133)
[92703.960000] pvfs2_kill_sb: (WARNING) number of inode allocs (135) != number of inode deallocs (134)

I think we probably can just move "pvfs2_inode_alloc_count" and "pvfs2_inode_dealloc_count" to be tracked within the sb struct.

-Phil

Change History

02/15/08 16:39:09 changed by carns

  • owner changed from carns@mcs.anl.gov to carns.

02/15/08 16:40:12 changed by carns

  • status changed from new to assigned.

05/13/08 13:19:23 changed by carns

  • status changed from assigned to closed.
  • resolution set to fixed.

Fixed now in trunk. Counters are now tracked per superblock.