Should have mentioned this above but I forgot and it does seem relevant.
When using a Pi5 there is a potential gotcha with BTRFS: if there is a mismatch between page size between the kernel and filesystem, the filesystem cannot be mounted. I believe this has already been reported.
In practice this means a BTRFS filesystem created with the default kernel on a Pi5 cannot be mounted on an earlier Pi model and that a BTRFS filesystem created on an earlier PI cannot be mounted on a Pi5 using the default kernel.
The only workaround I'm aware of is to ensure that the Pi5 (and presumably 500 and CM5 - can't test as I don't have those) is using kernel8.img and not kernel_2712.img.
I know because I got caught out by this.
Oh, and mergerfs might also be an option.
When using a Pi5 there is a potential gotcha with BTRFS: if there is a mismatch between page size between the kernel and filesystem, the filesystem cannot be mounted. I believe this has already been reported.
In practice this means a BTRFS filesystem created with the default kernel on a Pi5 cannot be mounted on an earlier Pi model and that a BTRFS filesystem created on an earlier PI cannot be mounted on a Pi5 using the default kernel.
The only workaround I'm aware of is to ensure that the Pi5 (and presumably 500 and CM5 - can't test as I don't have those) is using kernel8.img and not kernel_2712.img.
I know because I got caught out by this.
Oh, and mergerfs might also be an option.
Statistics: Posted by thagrol — Thu Jan 16, 2025 8:56 pm