When creating a huge (TB+) partition, the fdisk module sits for a long time with no output. Then, after that long wait, it produces the following error:
Failed to save partition : parted -s /dev/sdb unit cyl mkpartfs primary ext2 2065 364801 ; parted -s /dev/sdb set 2 raid on failed : Warning: WARNING: the kernel failed to re-read the partition table on /dev/sdb (Device or resource busy). As a result, it may not reflect all of your changes until after reboot. Warning: WARNING: the kernel failed to re-read the partition table on /dev/sdb (Device or resource busy). As a result, it may not reflect all of your changes until after reboot.
(note multiples of the same error)
Also, when performing what I'm pretty sure is the same action on the command line, it returns instantly for each of the necessary steps. Maye I'm missing something...
(parted) mkpart
Partition name? []?
File system type? [ext2]?
Start? 17.0GB
End?
End? 3001GB
Warning: WARNING: the kernel failed to re-read the partition table on /dev/sda
(Device or resource busy). As a result, it may not reflect all of your changes
until after reboot.
(parted) set 2 raid on
Warning: WARNING: the kernel failed to re-read the partition table on /dev/sda
(Device or resource busy). As a result, it may not reflect all of your changes
until after reboot.
Though I see where the multiple errors is coming from.
So, not sure if the long return time is a bug, or it is expected behavior and the only issue is a lack of reassurance that Webmin is doing something productive while the user waits.
Is it maybe formatting the disk with a filesystem? That would explain the long time to return, but doesn't make sense for a Linux RAID partition which is just going to be overwritten by mdadm in a moment, anyway.
Comments
Submitted by JamieCameron on Sat, 02/08/2014 - 12:30 Comment #1
That is odd, as creating a partition should be pretty quick (as creation of the filesystem is separate). How long did this take when you ran it manually?
The
partedcommand is kind of annoying, as it doesn't seem to have a clear separation between empty partitions and partitions with filesystems.