Closed farblos closed 2 years ago
I have seen #58 but that has been closed some 3 years ago. Plus I'm running on a "recommended kernel" according to the readme ...
Can you provide output from btrfs-search-metadata file
for both of the filenames mentioned in the BtrfsExtentSame
arguments? The clue is probably in there somewhere.
In general, there's a number of reasons why extent-same might return EINVAL
, and some of them are relatively rare and require more work to detect than simply trying the extent-same call and ignoring the error. Assuming bees isn't doing something very wrong here, we could simply ignore them, or push them down to a more verbose log level.
Sry, my testbed is gone already - I have migrated to a "competitor". Not because of this issue, just because it fitted my needs better.
Thanks anyway, closing this issue.
Kernel (running on ARM 64bit):
Bees: 0.7 running through beesd and systemd unit.
Distribution: Oracle Linux Server release 7.9
During a test done with cpio while bees is running I frequently get the following exceptions in the journal: