Great that sdm can now create an image with btrfs rootfs!
I haven't looked in the scrips/sourcecode, but I see those 2 things:
a) BTRFS warning (device mmcblk0p2): v1 space cache is not supported for page size 16304 with sectorsize 4096
b) [ 4.954310] BTRFS info (device mmcblk0p2): using free space tree
I don't have a Pi5 so not experienced 16k CPU pagesizes, but logmessage a) means to me that you need to create the btrfs root filesystem with the v2 space cache. The logmessage in b) means the filesystem is using the v2 space cache. Debian Bullseye is kernel 5.10 and matching btrfs-progs by default creates filesystems with v1 space cache. You need to explicitly tell to use v2. Debian Bookworm is 6.1, that defaults to v2.
So it is just a matter of using newer btrfs-progs. In latest Opensuse Tumbleweed (6.10) I see this:You can add/fix both online and offline the usage of v2. I did many times online, on a other/newer Linux system just mount the filesystem once with options added
clear_cache, space_cache=v2
After that the Pi5 should boot/mount.
Another thing I think I see is that when kernel8 is used, it might be that _2712 initramfs is used, but not sure.
Some side note, I am using newer than Bookworm because option block-group-tree needs btrfs-progs >= 6.3 and Bookworm is 6.2. It radically speeds up mounting for multi-TB HDDs. The kernel supports it, so you could use another/newer system to enable that flag, must be done unmounted anyway.
See also: https://btrfs.readthedocs.io/en/latest/ ... ation.html
I haven't looked in the scrips/sourcecode, but I see those 2 things:
a) BTRFS warning (device mmcblk0p2): v1 space cache is not supported for page size 16304 with sectorsize 4096
b) [ 4.954310] BTRFS info (device mmcblk0p2): using free space tree
I don't have a Pi5 so not experienced 16k CPU pagesizes, but logmessage a) means to me that you need to create the btrfs root filesystem with the v2 space cache. The logmessage in b) means the filesystem is using the v2 space cache. Debian Bullseye is kernel 5.10 and matching btrfs-progs by default creates filesystems with v1 space cache. You need to explicitly tell to use v2. Debian Bookworm is 6.1, that defaults to v2.
So it is just a matter of using newer btrfs-progs. In latest Opensuse Tumbleweed (6.10) I see this:
Code:
# mkfs.btrfs -O list-allFilesystem features available:mixed-bg - mixed data and metadata block groups (compat=2.6.37, safe=2.6.37)quota - hierarchical quota group support (qgroups) (compat=3.4)extref - increased hardlink limit per file to 65536 (compat=3.7, safe=3.12, default=3.12)raid56 - raid56 extended format (compat=3.9)skinny-metadata - reduced-size metadata extent refs (compat=3.10, safe=3.18, default=3.18)no-holes - no explicit hole extents for files (compat=3.14, safe=4.0, default=5.15)fst - free-space-tree aliasfree-space-tree - free space tree, improved space tracking (space_cache=v2) (compat=4.5, safe=4.9, default=5.15)raid1c34 - RAID1 with 3 or 4 copies (compat=5.5)zoned - support zoned (SMR/ZBC/ZNS) devices (compat=5.12)bgt - block-group-tree aliasblock-group-tree - block group tree, more efficient block group tracking to reduce mount time (compat=6.1)squota - squota support (simple accounting qgroups) (compat=6.7)clear_cache, space_cache=v2
After that the Pi5 should boot/mount.
Another thing I think I see is that when kernel8 is used, it might be that _2712 initramfs is used, but not sure.
Some side note, I am using newer than Bookworm because option block-group-tree needs btrfs-progs >= 6.3 and Bookworm is 6.2. It radically speeds up mounting for multi-TB HDDs. The kernel supports it, so you could use another/newer system to enable that flag, must be done unmounted anyway.
See also: https://btrfs.readthedocs.io/en/latest/ ... ation.html
Statistics: Posted by redvli — Mon Aug 05, 2024 12:11 pm