|
|
|
mismatch_cnt questions | |
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] | |
Hello, these questions apparently got buried in another thread, so here goes again ... I have a mismatch_cnt of 384 on a 2-way mirror. The box runs 2.6.17.4 and can't really be rebooted or have its kernel updated easily 1) Where does the mismatch come from? The box hasn't been down since the creation of the array. 2) How much data is 384? Blocks? Chunks? Bytes? 3) Is the "repair" sync action safe to use on the above kernel? Any other methods / additional steps for fixing this? Regards, C. - 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
[Home] [ATA RAID] [Linux SCSI Target Infrastructure] [Linux] [Managing RAID on Linux] [Linux IDE] [Linux SCSI] [Linux Hams] [Device-Mapper] [Kernel] [Linux Books] [Linux Admin] [Linux Net] [GFS] [RPM] [Photos] [Yosemite Photos] [Yosemite News] [AMD 64] [Linux Nework]
![]() |
![]() |