Re: raid1 out of sync, but which files are affected?

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

 



On 26/1/19 9:49 pm, Harald Dunkel wrote:
Hi folks,

I initiated a check of my RAID1 (2 disks) this morning. mismatch_cnt
is at 128 by now.

Apparently I can map block numbers to files using debugfs, looking
closely at block sizes and partition offsets, but how can I tell which
blocks within md0 are affected?

My experience is that as of the last few years you get messages like these in the system log:

# grep 'mismatch sector in range' /var/log/messages-2017
Sep 23 09:47:47 e7 kernel: md127: mismatch sector in range 770366344-770366352


Hopefully I wasn't too blind to see. Every helpful comment is highly
appreciated

Harri



--
Eyal at Home (eyal@xxxxxxxxxxxxxx)



[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