Thanks for the response, Duncan. On 01/05/14 17:58, Duncan wrote: > > Tho you are slightly outdated on your btrfs-progs version, 3.14.1 being > current. But I think the code in question is kernel code and the progs > simply report it, so I don't think that can be the problem in this case.
Yes, I'm aware that 3.14 version of btrfs progs was already there, but this is just for couple of weeks and I'm pretty sure that the kernel code (which does the real time accounting) is broken. > So if you are doing snapshots, you can try not doing them (switching to > conventional backup if necessary) and see if that stabilizes your > numbers. If so, you know there's still more problems in that area. > > Of course if the subvolumes involved aren't snapshotted, then the problem > must be elsewhere, but I do know the snapshotting case /is/ reasonably > difficult to get right... while staying within a reasonable performance > envelope at least. > I have already searched and found some patches around this issue, but I thought I'd also mention the issue on this mailing list and hoped that I somehow missed something. The subvolumes are highly probable to be snapshotted, so this might indeed be the case. Cheers, Alin. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
