On Tue, Feb 04, 2025 at 07:52:38AM -0500, Martin K. Petersen wrote: > I have been told that some arrays use it to disable PI when writing the > RAID parity blocks. I guess that makes sense if the array firmware is > mixing data and parity blocks in a single write operation. For my test > tool I just use WRPROTECT=3 to disable checking when writing "bad" PI. Hmm, why would you disable PI for parity blocks? But yes, outside of Linux there might be uses. Just thinking of a "perfect" format for our needs. > > > > That would also work fine. NVMe supports 4byte crc32c + 2 byte app tag + > > 12 byte guard tag / storage tag and 8-byte crc64 + 2 byte app tag + 6 > > byte guard / storage tag, although Linux only supports the latter so far. > > Yep, the CRC32C variant should be easy to wire up. I've thought about > the storage tag but haven't really come up with a good use case. It's > essentially the same situation as with the app tag. Exactly, it's an app tag by other means.
