Btrfsck errors (fs tree 565 refs 125 not found) - how serious

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

For about 3 weeks I've been using btrfs on my desktop machine, using
the snapshot-functionality quite a lot.

Today I ran btrfsck and got about ~10MB of output which looks like:

fs tree 565 refs 125 not found
	unresolved ref root 807 dir 813347 index 277 namelen 39 name
snapshot_1368273601_2013-05-11_14:00:01 error 600
	unresolved ref root 808 dir 813347 index 277 namelen 39 name
snapshot_1368273601_2013-05-11_14:00:01 error 600
.......

fs tree 566 refs 125 not found
	unresolved ref root 807 dir 813347 index 278 namelen 39 name
snapshot_1368274201_2013-05-11_14:10:01 error 600
	unresolved ref root 808 dir 813347 index 278 namelen 39 name
snapshot_1368274201_2013-05-11_14:10:01 error 600
......


while the log contained a lot of different values for "fs tree", the
refs which were not found stays fairly constant:

refs: 125, 397, 398, 406, 407, 420

How serious are those issues, should I be worried?
Would it help if I find ways to reproduce this behaviour on a fresh
btrfs filesystem?

Thank you in advance, Clemens
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux