Re: fsck bug in replaying partial frag truncate journal on UFS SU+J?

2014-06-18 Thread takehara . mikihito
Hello, I kept analysis of the problem which I reported previously and found how to fix this problem. (patch in my previou report is wrong.). My understanding is there is a rule that blkno of JOP_FREEBLK or JOP_NEWBLK must be the first position in UFS block for each inode, for fsck_ffs's suj.c

fsck bug in replaying partial frag truncate journal on UFS SU+J?

2014-05-13 Thread takehara . mikihito
Hello, I think fsck_ffs has a bug in replaying partial frag truncate journal on UFS SU+J. Bellow I tested about the issue. I tested blocksize==4KB, fragsize=512byte UFS SU+J. But I think these parameters are not related to this issue. 1) Preparing 4096byte(1block) test file. 2) Use "truncate"

uninitialized journal data written in SU+J ?

2014-04-22 Thread takehara . mikihito
Hello, I'm testing UFS with SU+J. But it seems sometimes broken journal data has written. In softdep_process_journal (ffs_softdep.c), there is a while code to build jsegrec and each entry. But by my test, sometimes there is no entry then break this while code without building jsegrec. If this