Hello Qu,
Le 18/09/2017 à 01:33, Qu Wenruo a écrit :
That's a bug, and should be fixed.
OK.
But it's a little complicated to fix.
The biggest problem is, until reflink is done and we commit a
transaction, we don't know if the the reflink operation will increase
"rfer" or not.
(Considering a case where both reflink source and destination is inside
the same subvolume)
Yes, we can always try to reserve the size of the data, and cause false
alert, but the handling of reserved data range will be another problem.
I'll check if we can solve it.
Thanks for your explanation. I'm looking forward to hearing good news
about this then :)
Regards,
--
Antoine
--
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
