[MINC-users] minc volume integrity checks

[EJ Nikelski]

Hi All,

   A wee bit back, our lab ran into a problem with an XFS driver
causing corruption on our RAID system. This error resulted in quite a
few files having blocks of random garbage written to them ... which,
of course, also affected our minc volumes.  The problem was resolved,
however, I am left with the nagging suspicion that some of our minc
volumes might still be corrupted.  Does anyone have any idea of how I
might scan through all of our volumes and identify at least some of
the corrupted volumes?

   On a related note, as larger and larger volumes find themselves
moved around in a number of ways, might it not be useful to have an
image checksum attribute initialized in the minc header at volume
creation?  Yes, TCP/IP transfers are *supposed* to validate that
blocks are transferred correctly ... but the XFS driver was also not
supposed to corrupt our RAID.  Is this checksum idea a possibility (is
it already in minc2, and I've missed it?), or is this best addressed
in minc3 ;)

-Jim