NILFS warning (device sdb1): nilfs_truncate_bmap: failed , to truncate bmap (ino=424, err=-2)
Hi,
I had a system freeze this morning. This was the error appearing in /var/log/messages shortly before the freeze.
NILFS warning (device sdb1): nilfs_truncate_bmap: failed ,to truncate bmap (ino=424, err=-2)
cleanerd has been running for 4 hours.This occured 5 minutes after I killed cleanerd. At the moment were this was occuring, I was also deleting about //250gbytes of files. So it's no sure if it is cleaner related or not.
The kernel was 2.6.28.8 with nilfs 2.0.11
If have done a find / in order to list all the files after a reboot, and no further nilfs2 error messages have been logged.
Bye,
David Arendt
A message that is not in the archive (sent off-list or not yet received): 49C4D621.6040202-/[email protected]
Hi,
Quoted 13 lines · David Arendt
Hi,
I had a system freeze this morning. This was the error appearing in
/var/log/messagesshortly before the freeze.NILFS warning (device sdb1):
nilfs_truncate_bmap: failed ,to truncate bmap (ino=424, err=-2)cleanerd has been running for 4 hours.This occured 5 minutes after I killed cleanerd. At the moment were this was occuring, I was also deleting about //250gbytes of files. So it's no sure if it is cleaner related or not.
Quoted 7 lines
The kernel was 2.6.28.8 with nilfs 2.0.11
If have done a find / in order to list all the files after a reboot, and no further nilfs2 error messages have been logged.
Bye,
David Arendt
The error code indicates that a nilfs delete routine unexpectedly met a hole block or failed to translate vblocknr to on-disk block address while it is truncating btree of a huge file.
Maybe GC is involved.
I don't know the warning is relating to the freeze.
This seems to require digging deeply into the function and GC, so I'll queue it at a bugtrack for now.
Thanks for reporting.
Ryusuke