# Storage pool has an incompatible minimum I/O size

**URL:** <https://forums.linbit.com/t/storage-pool-has-an-incompatible-minimum-i-o-size/1182>\
**Category:** LINSTOR\
**Created:** [March 19, 2026, 6:50pm UTC](https://forums.linbit.com/t/storage-pool-has-an-incompatible-minimum-i-o-size/1182 "2026-03-19T18:50:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CirrusMS](https://avatars.discourse-cdn.com/v4/letter/c/e9c0ed/32.png) [@CirrusMS](https://forums.linbit.com/u/CirrusMS)\
**Post date:** [March 19, 2026, 6:50pm UTC](https://forums.linbit.com/t/storage-pool-has-an-incompatible-minimum-i-o-size/1182/1 "2026-03-19T18:50:20Z")

</div>

Hello,

one node from my 4 node cluster suddenly started to reject resource create with: storage pool has an incompatible minimum I/O size. This node already hosts 25 diskfull resources.

All my nodes provides zfs\_thin type storage pools. Failing one has ashift 9 and 3 nodes ashift 12.

Is there any way to force failing node to utilize 4K sectors?

Why this ashift inconsistency wasn’t a problem before linstor-satellite service restart I did today? Cluster uses version 1.33.1 since February.