On Wed, Jul 06, 2005 at 08:59:23PM +0200, [EMAIL PROTECTED] wrote: > > (parted) unit B > > (parted) mkpart > > Partition type? [primary]? > > File system type? [ext2]? > > Start? 0 > > End? -1 > > Error: The location -1 is outside of the device /dev/sdx. > Does this only happen with gpt labels?
Well, -1B is very strange. How should we deal with byte units that aren't sector aligned? > > Using units GB, mkpart works but wastes quite a bit > > of space at the end of the disk. Is this really the way you > > want it to work, leaving almost a GB of unused space at the end of > > the disk? I'd consider changing the semantics of "-1" > > to be "last available sector relative to the starting sector > > regardless of unit in effect". This means that if you're trying > > to fill a hole in the disk, all you have to do is get the starting > > location correct and -1 will find the end. Anyway, something to think > > about. > Special semantics for ``-1''? > This introduces an inconsistency. You can always use ``-1s''. We could just make _grow_over_small_freespace() a more generous _grow_over_freespace(), constrained by our new "range" parameter. > > I'd still like to see resize of a partition with no filesystem. > > (Patch previously submitted to maintainer(s).) I'm not excited by the idea. Would letting the "check" command set the partition size to coincide with the detected filesystem's size suffice? Cheers, Andrew _______________________________________________ Bug-parted mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-parted
