Re: mismatch_cnt, random bitflips, silent corruption(?), mdadm/sw raid[156]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx> wrote:
> Options/alternatives for maintaining data integrity?
> 3. Keep an md5sum for each file on the filesystem and run daily checks?

I'm doing this since about 6 years now with all of my files and I never
experienced any silent corruption.
I also regularly experience MD mismatch_cnt effects on RAID1 with ext2/3
filesystems with heavy file removal/creation load (even before MD
implemented its self-check features - I cmp-ed and corrected them
manually before) and they all seem to have been related to metadata,
i.e. inodes.


regards
   Mario
-- 
[mod_nessus for iauth]
<delta> "scanning your system...found depreciated OS...found
        hole...installing new OS...please reboot and reconnect now"

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux