> On Nov 16, 2017, at 9:35 AM, Larkin Lowrey <llowrey@xxxxxxxxx> wrote: > > Is it not possible to permanently remove a journal and return to resync mode? > > Here's what I tried: > > # mdadm --readonly /dev/md124 > > # cat /proc/mdstat > Personalities : [raid10] [raid0] [raid6] [raid5] [raid4] > md124 : active (read-only) raid5 md123[7] md127p4[15](J) sdp1[13] sdl1[10] sdg1[12] sdf1[11] sdo1[14] sdj1[8] sdq1[9] md122[6] > 62509129728 blocks super 1.2 level 5, 512k chunk, algorithm 2 [9/9] [UUUUUUUUU] > > # mdadm /dev/md124 --fail /dev/md127p4 > mdadm: set /dev/md127p4 faulty in /dev/md124 > > # mdadm /dev/md124 --remove /dev/md127p4 > mdadm: hot removed /dev/md127p4 from /dev/md124 > > # cat /sys/block/md124/md/consistency_policy > journal > > # echo resync > /sys/block/md124/md/consistency_policy > > # cat /sys/block/md124/md/consistency_policy > resync Could you please try the following command here: echo active > /sys/block/md124/md/array_state > # mdadm --stop /dev/md124 > mdadm: stopped /dev/md124 > > # mdadm --assemble /dev/md124 /dev/md12[23] /dev/sd[goqpjfl]1 > mdadm: Not safe to assemble with missing or stale journal device, consider --force. > -- 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
