Hope someone can help me with this. I have been using UFS2 write support and, so far, I have not run into any type of file corruption (so thanks!). What I did notice though is that the inode/ufs_inode house keeping is missing inode->i_blocks (ufs_inode->ui_blocks) incremental counter during activities in balloc.c. Being unfamiliar with UFS as a whole, I wasn't sure how to account for fragements into the ufs_inode->ui_blocks so it gets stored when the inode is written to disk. It appears that all the work for converting to and from inode->i_blocks and ufs_inode->ui_blocks is there for inode get/puts. But nothing seems to increment/decrement it and honestly I'm not familiar enough to get started. Could you help point me in the right direction so I could patch this? I am not a file systems developer, but am willing to learn. To recreate: (assuming a loop0 file backed, also occurs on a spinning platter disk) mkfs.ufs -O 2 /dev/loop0 mount -t ufs -o ufstype=ufs2,rw /dev/loop0 /mnt/ufs touch /mnt/ufs/testfile stat /mnt/ufs/testfile cat /var/log/message > /mnt/ufs/testfile stat /mnt/ufs/testfile Tested in 3.0.4 and 2.6.38, also happens on copy operations as well. -- Kevin Landreth p.s. I am not subscribed to the list, please CC me on replies. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
