Hi Adrian,
Thanks for dump logs.
segment: segnum = 85092
partial segment
creation time = 2008-11-26 17:41:05
partial segment
creation time = 2008-11-26 17:41:06
segment: segnum = 85093
partial segment -> pseg 174270464
creation time = 2008-11-26 17:41:06
ino = 3, cno = 0, nblocks = 86, ndatblk = 80
partial segment -> pseg 174271740
creation time = 2008-11-26 17:41:11
ino = 3, cno = 0, nblocks = 8, ndatblk = 3
partial segment -> pseg 174271758
creation time = 2008-11-26 17:42:47
ino = 3, cno = 0, nblocks = 735, ndatblk = 722
segment: segnum = 85094
partial segment -> pseg 174272512 <-- pointed by superblock
creation time = 2008-10-28 20:27:55
ino = 3, cno = 0, nblocks = 61, ndatblk = 51
partial segment
creation time = 2008-10-28 20:29:14
segment: segnum = 85095
partial segment
creation time = 2008-10-28 20:29:15
According to your logs, the segment pointed by
the superblock was not written as suspected.
This never occurs if the block device is
supporting 'write barrier' feature properly.
Could you tell me the kernel version that you are using?
I feel that an additional disk flush operation may be
needed for older kernels or such devices. (Of course,
first priority should be on making fsck.)
Regards,
Ryusuke Konishi
_______________________________________________
users mailing list
[email protected]
https://www.nilfs.org/mailman/listinfo/users
