Zygo

It's currently a quality-of-implementation issue. If you were using `--workaround-btrfs-send` before 5.3, it still works on 5.3. The "deferred subvol scan" feature is an _alternative_ to `--workaround-btrfs-send`, so it's a...

> Under what scenarios --workaround-btrfs-send is still needed for Kernel 5.11.0 or later None. Well, OK, one: you can't start a btrfs send if there is a dedupe call running...

bees could check the inode for the +C attribute and avoid the exceptions. It would probably be better to just not dedup nodatacow files at all, as the nodatacow bit...

This kernel patch sounds like it might fix the NFS issue: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b1517622f2524f531113b12c27b9a0ea69c38983 It would affect an NFS server running bees where the NFS client does a lot of writes of...

I could see cases where nodatacow and snapshots could be used together, to create a filesystem that is mostly nocow except during backups. dedup could make sense in some situations...

The beesd script (or OpenRC or ...) sets the mount options. You can put any mount options you like, bees requires only `subvol=` or `subvol=/` or `subvolid=5`, and `rw`. `noatime`...

OK, so send had _two_ bugs after all. Are you willing to report this to the linux-btrfs mailing list?

Kernel bugzilla is worth a shot. Best case, it's a simple fix. Worst case, it'll get ignored, and I'll forward it to the mailing list when I get a few...

> Does this happen with the other duperemove tool too, or just bees? It's a kernel bug, so it should affect all deduplicators on btrfs.

@Gatak, @kakra: Temporary files are created in the root subvol with `O_TMPFILE`. They never have names, they are created by the kernel with a zero link count. The root subvol...