On 11/10/2017 01:15 PM, Jun-Kai Teoh wrote: >>> Am in the process of backup right now. >>> >>> And yes, the drive/array is mounted. >> >> Ok. I reviewed the other thread. Consider creating a new array >> from scratch after you complete your backups, using consistent >> partitioning across all devices. I would put LVM on top and leave >> part of it unallocated (for emergencies), but that's just my >> preference. > I'm backing up as much as I can, but I don't think I'll be able to > back up everything. I can back up very little of the data, so I'm > trying to prioritize carefully right now. Ah, ok. Well, after you get the important stuff backed up, you can add more devices as spares and try to let MD continue its grow and rebuild operations. It might end up completing. But don't add any more complete devices to the array -- use a partition that starts at 1MB and covers the rest of the device (default for most partition tools nowadays). I recommend that when/if your array is stable again, you add one more spare (with partition) and then use mdadm's --replace operation to move complete-device members to the new member. When each is done, take the newly freed device and partition it and do the next. When you have no more complete-device members and have the last freed device partitioned, consider converting to raid6 with that spare. All of that will take many days, but can be done safely while running the system. > All devices are just 4TB drives, I didn't partition them separately > for the array - or am I misunderstanding what you mean? <-- This is > really common, all of you are far more knowledgeable than I am and I > only understand some of the terms sometimes. MD raid doesn't care if you use whole devices of if you use partitions. But other system utilities can get confused, and can even write a new, unwanted partition table. (I recall seeing that with a NAS product a while back.) So, the 1MB lost is good insurance against stupid tools. Phil -- 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
