It is not fast_commit, it works fine with cqe. In fact, I have replicated all my settings on the vanilla image and it works with cqe. It is a mystery. ![:shock:]( "Shocked")
What I did to the old image (the one not working with cqe) - shrunk the size of ext4 by gparted to be able to dd it to 64GB SD cards. Maybe it is the alignment of the end of the FS? But why it works without cqe and the errors show only when cqe is enabled? Does the cqe change something?![:?:]( "Question")
The not working image is aligned like this:
```
$ sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 119.25 GiB, 128043712512 bytes, 250085376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e07cda8
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 1056767 1048576 512M c W95 FAT32 (LBA)
/dev/mmcblk0p2 1056768 52357119 51300352 24.5G 83 Linux
```
What I did to the old image (the one not working with cqe) - shrunk the size of ext4 by gparted to be able to dd it to 64GB SD cards. Maybe it is the alignment of the end of the FS? But why it works without cqe and the errors show only when cqe is enabled? Does the cqe change something?
The not working image is aligned like this:
```
$ sudo fdisk -l /dev/mmcblk0
Disk /dev/mmcblk0: 119.25 GiB, 128043712512 bytes, 250085376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e07cda8
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 1056767 1048576 512M c W95 FAT32 (LBA)
/dev/mmcblk0p2 1056768 52357119 51300352 24.5G 83 Linux
```
Statistics: Posted by fik — Thu Apr 04, 2024 8:20 am