Curtis Gedak wrote: > Jim Meyering wrote: >> Curtis Gedak wrote: >> >>> Jim Meyering wrote: >>> >>>> ... I just tried to add a couple partitions (in free space), >>>> and each time, I got this: >>>> >>>> $ sudo ./parted -s $dev u B mkpart F13-root $s2 $e2 >>>> 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. >>>> >>>> I thought the intent was to avoid such warnings when they do not apply. >>>> The kernel was indeed notified of the creation of the two new >>>> partitions, and I was able to create file systems on them. >>>> >>>> >>> Do you have an active LVM on a partition on the drive? >>> >> >> Thanks, but no. >> >> > Okay, so the problem is not due to an active LVM partition. Some > testing has shown me that the patches to reenable BLKPG ioctls > actually fix the problem of editing other unmounted partitions on a > device with an active LVM partition. > > Was the command in your testing actually the following or was there a typo? > > $ sudo ./parted -s $dev u B mkpart F13-root $s2 $e2
That is precisely the command I used. > If this was the command then what is a partition type of "F13-root"? It's a GPT partition table, so that's its name, not its type. (yes, mkpart's partition-table-type-sensitive semantics is horribly user-unfriendly) _______________________________________________ bug-parted mailing list bug-parted@gnu.org http://lists.gnu.org/mailman/listinfo/bug-parted