Zygo

> [I believe this bug is relevant](https://github.com/kdave/btrfs-progs/issues/657) Yes, that bug appears to be happening as well; however, even without that bug, the same failure would be expected.

I started archiving xscreensavers the day `xroger` disappeared. "upstream" once said I had collected some versions that had been lost, at a time when it was much easier to find...

The 512K size limit applies to _uncompressed_ extents when the `compress-force` mount option is used and compression fails. This arises from this code in `fs/btrfs/inode.c`: ``` $ git grep -p...

> But only for uncompressed extents during compress-force? For compress without `-force`, the 512K issue doesn't seem to occur--extents are 128M long even in files with some compression. That's an...

grepping error messages out of dmesg is fun, but ideally scrub would provide a list of affected files directly. dmesg is rate-limited, so if you have a scratch on your...

Sounds like the same bug as #249, but affecting refind instead of grub.

> De-duplicate on write, hook somewhere into the write process, checksum block, and if found in hash list check for identical and then link instead of write. This requires an...

> I know that I must not run bees and btrfs send/receive at the same time. Why not? bees v0.11-rc3 will pause automatically while btrfs send is running. btrfs send...

The scan halts when the referring file is opened and its `FS_NOCOW_FL` flag checked; files with this flag set are not scanned or deduplicated. bees closes the file immediately. Since...

> Bees walks the extents, and then finds the file to that extent. If that file doesn't have the nocow flag, bees will process it. It's a little worse than...