On 01/08/2018 11:16 PM, Wols Lists wrote:
On 08/01/18 07:31, Guoqing Jiang wrote:
On 01/06/2018 11:44 PM, mdraid.pkoch@xxxxxxxx wrote:
Dear MD-experts:
I was under the impression that growing a RAID10 device could be done
with an active filesystem running on the device.
It depends on whether the specific filesystem provides related tool or
not, eg,
resize2fs can serve ext fs:
Sorry Guoqing, but I think you've *completely* missed the point :-(
Yes, I just want to point is it is more safer to umount fs first, then
do the reshape.
There is another deadlock issue which mentioned by BingJing, it happened
during
reshape stage while some I/O come from vfs layer, though it is not the
same issue,
https://raid.wiki.kernel.org/index.php/Growing#Extending_the_filesystem
And you can use xfs_growfs for your purpose.
You extend the filesystem *after* you've grown the array. The act of
growing the array has caused the filesystem to crash. That should NOT
happen - the act of growing the array should be *invisible* to the
filesystem.
In other words, one or more of the following three are true :-
1) The OP has been caught by some random act of God
2) There's a serious flaw in "mdadm --grow"
3) There's a serious flaw in xfs
IMHO, there could be potential issue inside raid10/5, so I choose 2.
Anyway, I will
try to simulate the scenario and see what will happen ...
Thanks,
Guoqing
--
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
