Quantcast
Channel: Debian User Forums
Viewing all articles
Browse latest Browse all 3260

System and Network configuration • [Solved] gdisk - is this an expected behavior?

$
0
0

Code:

# gdisk /dev/sdaGPT fdisk (gdisk) version 1.0.9Partition table scan:  MBR: protective  BSD: not present  APM: not present  GPT: presentFound valid GPT with protective MBR; using GPT.Command (? for help): pDisk /dev/sda: 35156244480 sectors, 16.4 TiBModel: SMC2208         Sector size (logical/physical): 512/4096 bytesDisk identifier (GUID): 0B4BEE7E-C2CC-4220-87A8-DED5CDFF7240Partition table holds up to 128 entriesMain partition table begins at sector 2 and ends at sector 33First usable sector is 34, last usable sector is 35156244446Partitions will be aligned on 2048-sector boundariesTotal free space is 35156244413 sectors (16.4 TiB)Number  Start (sector)    End (sector)  Size       Code  NameCommand (? for help): nPartition number (1-128, default 1): First sector (34-35156244446, default = 2048) or {+-}size{KMGTP}: Last sector (2048-35156244446, default = 35156242431) or {+-}size{KMGTP}: +16.3TCurrent type is 8300 (Linux filesystem)Hex code or GUID (L to show codes, Enter = 8300): 8e00Changed type of partition to 'Linux LVM'
imo, till here everything looks good, but this is what i get:

Code:

Command (? for help): pDisk /dev/sda: 35156244480 sectors, 16.4 TiBModel: SMC2208         Sector size (logical/physical): 512/4096 bytesDisk identifier (GUID): 0B4BEE7E-C2CC-4220-87A8-DED5CDFF7240Partition table holds up to 128 entriesMain partition table begins at sector 2 and ends at sector 33First usable sector is 34, last usable sector is 35156244446Partitions will be aligned on 2048-sector boundariesTotal free space is 35156244397 sectors (16.4 TiB)Number  Start (sector)    End (sector)  Size       Code  Name   1            2048            2063   8.0 KiB     8E00  Linux LVMCommand (? for help): dUsing 1Command (? for help): q
here is the thing, it accepted +16.3T ( accepted in this case means: it did not error out )

so why did it end up adding 16 blocks? and still not error out?

i am thinking it might not like the decimal point, but i guess i should be notified about it - not only that, but it should not "decide" to add 16 blocks in size instead.... 8KB LVM type 8e? i mean sure, but...

i see it this way, if it does not error out ( which it does in that spot when you type in some gibberish ), means the input is accepted, validated, good to go - and not partially just discarded without letting the user know.

edit: typo: 15 -> 16 blocks

Statistics: Posted by ksu — 2024-03-08 05:09 — Replies 1 — Views 67



Viewing all articles
Browse latest Browse all 3260

Trending Articles