Good morning Phil,
Please find some updates below.
> I think the situation looks worse now. The reshape finished and resync
> has begun. During the resync I've found many errors concerning
> /dev/sdf which is the part of the md127. Example below:
The resync operation actually completed and the details of md127 looks
as follows:
[root@sysresccd ~]# mdadm --detail /dev/md127
/dev/md127:
Version : 1.2
Creation Time : Thu Dec 25 12:15:20 2014
Raid Level : raid6
Array Size : 7813771264 (7451.79 GiB 8001.30 GB)
Used Dev Size : 3906885632 (3725.90 GiB 4000.65 GB)
Raid Devices : 4
Total Devices : 4
Persistence : Superblock is persistent
Intent Bitmap : Internal
Update Time : Wed Sep 4 03:15:29 2019
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Layout : left-symmetric
Chunk Size : 512K
Name : debnas:0
UUID : a3d7766c:aeb658d3:8e2d29b7:4de30dab
Events : 223869
Number Major Minor RaidDevice State
5 8 1 0 active sync /dev/sda1
4 8 49 1 active sync /dev/sdd1
3 8 81 2 active sync /dev/sdf1
6 8 97 3 active sync /dev/sdg1
`dmesg` didn't report any more read errors in /dev/sdf and the
`smartctl -a` for this drive looks unchanged in terms of
current_pending_sectors.
>
> The contents of `/proc/mdstat` are the following:
>
Right now it looks as follows:
[root@sysresccd ~]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md127 : active raid6 sda1[5] sdg1[6] sdd1[4] sdf1[3]
7813771264 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/30 pages [0KB], 65536KB chunk
unused devices: <none>
> Is the data in danger in this state?
The data seems to be intact. I've collected the log from `dmesg` to
review later what was the files at the corrected and uncorrected
sectors to see if they are still correct.
Also, answering the question from your previous mail:
> Uhm? Why are you running perf during this reshape?
I did not run it on purpose. It has been executed by SystemRescueCD. I
don't know what it exactly is and what may be the consequences of it
running during the reshape. Quick Google search didn't result in much
more information than it's a module to control the performance.
Best regards,
Krzysztof Jakobczyk
