That warning message can be safely ignored, I believe. It is actually
generated by the pvfs2 client kernel module rather than the pvfs2 server.
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)
There are probably other combinations of mounts and umounts that could
cause the message too. We'll see about getting that message corrected,
but in the meantime I think you can just ignore it.
-Phil
Scully wrote:
Hi,
I am trying the pvfs-2.7.0 on a i386 machine, linux-2.6.16.53.
I set a meta server, a io server and a client. After start the client, I
just did:
pvfs2-ping, showed OK
mount pvfs2 file system to /mnt/pvfs2, showed OK,
ls /mnt/pvfs2, showed OK,
umount, OK
But when I did "/etc/init.d/pvfs2-server stop", it showed can not find
pid file.
Then, I did "killall pvfs2-server", it showed OK.
But when I checked the log messages, I got
{
# dmesg
[50483.569623] pvfs2_kill_sb: (WARNING) number of inode allocs (14) !=
number of inode deallocs (12)
[50555.607475] pvfs2_kill_sb: (WARNING) number of inode allocs (14) !=
number of inode deallocs (13)
[50581.028863] pvfs2_kill_sb: (WARNING) number of inode allocs (15) !=
number of inode deallocs (14)
}
/tmp/pvfs2-server.log and /tmp/pvfs2-client.log are OK.
What causes those warnings? Was anything wrong? Thank you.
------------------------------------------------------------------------
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
_______________________________________________
Pvfs2-users mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-users
