Hi!
I'm using nilfs on thumb drives to sync Bitcoin wallets and it's forks.
Sometimes, when I quit the bitcoin-qt application, this is what happens
(in dmesg)
[159141.505498] nilfs_btree_propagate: key = 10, level == 0
[159141.715622] nilfs_btree_propagate: key = 10, level == 0
[159141.716134] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[159146.715145] nilfs_btree_propagate: key = 10, level == 0
[159146.715152] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[159151.715018] nilfs_btree_propagate: key = 10, level == 0
[159151.715026] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[159156.714892] nilfs_btree_propagate: key = 10, level == 0
...
...
...
[160276.691089] nilfs_btree_propagate: key = 10, level == 0
[160276.691096] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
[160281.690959] nilfs_btree_propagate: key = 10, level == 0
[160281.690967] NILFS warning (device dm-0): nilfs_clean_segments:
segment construction failed. (err=-2)
I can still access the thumbdrive and it's contents. In the mean time
many processes remain at D state and I have to force restart.
The devices used are perfectly fine. I've 3 of them, 2 of them are used
as a single LVM volume and another one uses the whole device as a nilfs
FS (no partition table).
--
To unsubscribe from this list: send the line "unsubscribe linux-nilfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html