Kai Krakow

Could you show your fstab?

Try adding the option `x-systemd.automount` to the `/disk` partition. Also, you can remove `space_cache=v2` - that is a one-time mount option and will be stored in the superblock, it cannot...

@Zygo we should probably document that users should add `x-systemd.automount` to their late-boot btrfs mount points - or otherwise bees may simply start too early (because the systemd service knows...

> No, they are mounted normally, from fstab. BTW, with systemd, that is late boot stage... systemd only mounts the minimum of needed filesystems in the early boot stage (to...

I researched a little, I think we should go with ```ini [Unit] After=local-fs.target [Install] WantedBy=multi-user.target ``` Actually, `basic.target` should not pull dependencies but be used as a synchronisation point only...

I implemented nocow detection of file flags in my PR #21, I didn't test if it would detect a file system mounted with "nodatacow". But I also wonder: Would it...

I'm not sure how `xfs_io` works. But bees does not dedupe extents directly, it instead rewrites new extents based on the hash table into a temporary file, then dedupes all...

@Gatak More or less "nowhere"... I think bees creates it in the root subvolume, acquires an open file descriptor of it, then immediately deletes it, only then it's writing file...

Maybe the order of parameters is important? There's some fixes in #136 which may help your problem.

Did you try the patches? Actually it may fix your problem because some cmdline options may access partially uninitialized objects in bees without this patch. Usually that's only a problem...