Zygo

> > In the reports, it looks like btrfs receive is somehow allocating about twice as much space for data as it is using > How exactly did you determine...

@adam900710 > Note your reports have very low data usage percentage (55.96%), which is not common just by send/receive/tar operations. That is the key point here. The data usage percentage...

The inode in `inode-resolve` only works with the subvol (root) named in the dmesg message, i.e. you'll need `subvol-resolve` on `257` to find the path to pass to `inode-resolve`. Deleted...

Some more context from the upstream link: > csum 0xc341dc86 expected csum 0xc341fc86 > bdev /dev/mapper/luks-e117a149-a0c5-401b-8032-d03580a55c9b That's a single-bit error, which frequently means bad or misconfigured host RAM. The device...

466 chunks were considered by the balance filter so far (out of the total number of chunks on the filesystem, which was not printed). 101 chunks matched the filter criteria....

> I believe that this balance then should only operate on metadata chunks? Yes (including the system chunk, which is a special kind of metadata). > According to the wiki,...

> The average time required per block considered in the metadata balance has dropped from 12m to 3m over the last 24 hours Considered doesn't really mean anything. Most of...

Each chunk is composed of 2 stripes, each of which is written to 2 different drives. The 5th device is unused because raid10 can use only an even number of...

Sorry, `vrange` is the correct filter name, not `vaddr`.

With the `vrange` filter, the balance will never repeat work (*), so you can stop and start the script at any time. The balances will become no-ops when the `vrange`...