Ticket #217 (new defect)

Opened 7 months ago

Last modified 7 months ago

Parted fails to resize raw partitions

Reported by: xbaldauf Assigned to:
Priority: major Milestone:
Component: parted Version:
Keywords: Cc:

Description

When using block devices with a size of >2TiB, GPT disklabels (see http://de.wikipedia.org/wiki/GUID_Partition_Table ) are recommended and the traditional MBR disklabel cannot be employed (because partition offsets >2TiB cannot be addressed).

Thus, traditional "fdisk" cannot be used to setup partitions, but parted needs to be used. However, while parted can create partitions, parted apparently cannot resize partitions with unknown or unsupported content.

For example, consider this 3TB device:

(parted) p Model: Adaptec system (scsi) Disk /mnt/boot/dev/sda: 2999GB Sector size (logical/physical): 512B/512B Partition Table: gpt

Number Start End Size File system Name Flags

1 17,4kB 3000MB 3000MB ext3 boot boot 2 3001MB 1100GB 1097GB primary

(parted) resize 2 3001024512B 2900GB Error: Could not detect file system. (parted)

The second partition actually contains a LVM physical volume, but parted fails to resize the space for this partition properly.

Parted should offer the user the option to just ignore the filesystem content when resizing, especially when enlarging, which is safe for almost all filesystems..

There is even a patch http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419473 fixing this bug, which is already more than 2 years old.

Attachments

Change History

07/27/09 22:20:14 changed by mjevans1983

http://parted.alioth.debian.org/cgi-bin/trac.cgi/ticket/220 is a duplicate of this, I would have thought this fix simple enough to be nearly instant, thought procedural.

07/28/09 07:22:01 changed by mjevans1983

Actually, it might be better if there were a command that clearly did not touch the data within the partition at all.

Something like remap which would literally remap the contents of a partition while doing -nothing- to it.

Another command like move would merely move where a partition was (bulk binary copy of inner data).

remap would default to failing for any 'unsafe' operation, however a mode specified before the partition number would permit 'unsafe' operations without error. most likely 'unsafe' as the specifier. In that case it would not worry about other details and would assume the administrator or their chosen programs know best.

Add/Change #217 (Parted fails to resize raw partitions)




Change Properties
Action