Attempted to user reserve space on ssd attached as USB drive. Did I do something wrong?

[pasha-19]

I read most drives have a 7% reserve and 10% is often recommended so I tried to add 4839M to the reserve. The following documents my results.

This happened using both PINN 3.9.3 and 3.9.2
This last attempt using 3.9.2 was not booted until after
installation usb/ssd drive was taken to another system where FDISK printed the allocations.

I added the following to the cmdline.txt file using the PINN windows

remotetimeout=60 networktimeout=30 vncshare ssh reserve=+4839

My USB ssd drive has 238311M

I installed for a raspi 3b

batoceri-RPI3        extra space  127846M  Total 131872M  (128G)
bullseye32                         28800M         32768M  (32G)
data                                3584M          4096M  (4G)
projectspace 1 (for bookworm32)    31744M         32768M  (32G)
projectspace 2 (for bookworm64)    31744M         32768M  (32G)
(unused space)                      4839M          4839M  (the same amount I asked for reserve space above)
                                          Total  238311M  (seems to be correct)

Disk /dev/sda: 232.89 GiB, 250059350016 bytes, 488397168 sectors
Disk model: ASM225CM        
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 33553920 bytes
Disklabel type: dos
Disk identifier: 0x02457c90

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            8192    268287    260096   127M  e W95 FAT16 (LBA)
/dev/sda2          268288 488397167 488128880 232.8G  5 Extended
/dev/sda5          270336    335869     65534    32M 83 Linux
/dev/sda6          335872   6942719   6606848   3.2G  c W95 FAT32 (LBA)
/dev/sda7         6946816 268779517 261832702 124.9G 83 Linux
/dev/sda8       268779520 269301759    522240   255M  c W95 FAT32 (LBA)
/dev/sda9       269303808 335896573  66592766  31.8G 83 Linux
/dev/sda10      335896576 344285181   8388606     4G 83 Linux
/dev/sda11      344285184 345333757   1048574   512M  c W95 FAT32 (LBA)
/dev/sda12      345333760 411394045  66060286  31.5G 83 Linux
/dev/sda13      411394048 412442621   1048574   512M  c W95 FAT32 (LBA)
/dev/sda14      412442624 488397167  75954544  36.2G 83 Linux

The resulting FDISK output confirms that /dev/sda14 is larger than requested
75954544 - 66060286 = 9894258 sectors = 4947129k ~= 4831.___M

It appears most if not all of my reserve space wound up in /dev/sda14.
it also appears to be in the enclosing extended partition.

Did I do something wrong or is this a problem?

I fixed the allocation with gparted the updated partitions follow.
(i resized /dev/sda14 and the extended partition -4831M per FDISK calc)

/dev/sda1            8192    268287    260096   127M  e W95 FAT16 (LBA)
/dev/sda2          268288 478502911 478234624   228G  5 Extended
/dev/sda5          270336    335869     65534    32M 83 Linux
/dev/sda6          335872   6942719   6606848   3.2G  c W95 FAT32 (LBA)
/dev/sda7         6946816 268779517 261832702 124.9G 83 Linux
/dev/sda8       268779520 269301759    522240   255M  c W95 FAT32 (LBA)
/dev/sda9       269303808 335896573  66592766  31.8G 83 Linux
/dev/sda10      335896576 344285181   8388606     4G 83 Linux
/dev/sda11      344285184 345333757   1048574   512M  c W95 FAT32 (LBA)
/dev/sda12      345333760 411394045  66060286  31.5G 83 Linux
/dev/sda13      411394048 412442621   1048574   512M  c W95 FAT32 (LBA)
/dev/sda14      412442624 478502911  66060288  31.5G 83 Linux

[JonnyTech]

MB / GB vs MiB / GiB ??

https://en.m.wikipedia.org/wiki/Byte#Multiple-byte_units

[procount]

Please refer to the manual at https://github.com/procount/pinn/blob/master/README_PINN.md#cmdline-options
I think you may be getting confused between reserve and provision.
You can set the reserve value from the Edit Options dialog, but the provision must be set manually in cmdline.txt.
These settings only take affect after using the runinstaller option, which will wipe your entire drive.