Oh, this combination of parameters and features causes lvcreate to incorrectly calculate the extents it needs and the command fails. (Needed to calculate them manually to fully use the drives. Probably could just have yolo-ed it with 89%FREE instead or something)
lvcreate --type raid6 --size 100%FREE --config allocation/raid_stripe_all_devices=1 --name raid6Data --raidintegrity y --raidintegritymode journal --raidintegrityblocksize 512 --autobackup y lvm_vg_<<UUID>>
@lispi314 good question.
After all physical device <=> physical volume partution <=> logical volume groups (w/ RAID) <=> filesystems were used in classic #Linux-RAID transparently to each other.
But yeah, you are correct in that an integrity checkibg module was overdue...
@lispi314 @mos_8502 nodds in agreement
Note that "Hardware-#RAID" is a hack for OSes without proper integrated RAID support (i.e. Windows) and #dmraid on #Linux requires the OS to be aware if the entire storage achitecture and correct thibgs accordingly.
@ascherbaum yeah, makes sense...
Usually the system should resync /boot shortly after mounting in the pre-#dmraid #RAID1 configuration...
@ernstdemoor @nixCraft that's because on basically all #Linux #Filesystems, #RAID and #Encryption is handled by dedicaded subsystems like #dmraid and #dmcrypt / #LUKS respectably, thus not on filesystem but OS level...
This allows extra cursed shit like a an encrypted & RAID-5 running NTFS - Tho that won't be useable by anything but Linix and I disrecommend it almost as hard as mixing hardware RAID controllers and/or dmraid with ZFS.
Remember: NEVER EVER LIE TO ZFS!!!
Klaus Frank
Kevin Karhan 
Kevin Karhan 