Re: After partition resize, RAID5 array does not assemble on boot

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

 



Jules Bean wrote:
David Greaves wrote:
I don't really see that it's "safer" though. I would have thought it was
quicker but potentially less safe.

Avoiding a lot of time stress testing the disks in degraded mode isn't 'safer'?

Stress testing the disks by an md rebuild is a feature! It increases confidence that they work.

;)

Seriously, I understand your point now. Yes, a rebuild-free partition resize would be a nice feature. So would a "help, please find my superblock by exhaustive scanning" utility ;)

Since this code must work when a partition is added on a totally new drive, and when the partition is grown DOWN from the low end, clearly the default must be a rebuild. And running "repair" before doing this stuff is a really good idea!

What is needed is to do something like assume-clean on the old data and a sync on the new chunks. I don't see that there is a remotely safe way to do that, currently, although if you were willing to be unsafe you could remove a partition, grow it at the "top" end, and reassemble with --assume-clean. Sprinkling with holy water first might be a good thing. I'm just thinking out loud here, there are probably good reasons why this wouldn't work.

--
Bill Davidsen <davidsen@xxxxxxx>
 "Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark

--
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

[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