On Mon, 2014-03-24 at 21:49 +0100, Piotr Szymaniak wrote: > That was some time ago, so I'm unable to answer this question. But > nilfs-tune shows 4KB blocks: > > ~ # nilfs-tune -l /dev/sdf3 > nilfs-tune 2.1.6 > Filesystem volume name: (none) > Filesystem UUID: 53760664-f9ed-4c8d-af42-c6ee2f16d956 > Filesystem magic number: 0x3434 > Filesystem revision #: 2.0 > Filesystem features: (none) > Filesystem state: invalid or mounted,error > Filesystem OS type: Linux > Block size: 4096 > Filesystem created: Fri Aug 3 08:37:06 2012
I suspect that you used this NILFS2 volume with kernel version that it was trouble with segments creation. So, you can have volume corruption because of this bug that it was fixed. (1) What Linux kernel version do use currently? (2) How long did you use old kernel versions? (3) What workloads did you use for this volume? (4) Had you situations of simultaneous working of several threads with intensive operations with volume (for example, simultaneous compilation and checking for updates)? Thanks, Vyacheslav Dubeyko. -- To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
