Re: [Gptfdisk-general] Bug#649054: cgdisk says: "Partition 1 doesn't begin on a 4149778177-sector b
Brought to you by:
srs5694
Menu
▾
▴
Re: [Gptfdisk-general] Bug#649054: cgdisk says: "Partition 1 doesn't begin on a 4149778177-sector boundary."
|
From: Rod S. <rod...@ro...> - 2012-01-22 20:20:14
|
On 01/03/2012 05:43 PM, Guillaume Delacour wrote: Sorry for taking so long to reply; this message arrived when I was busy, so I put it off, and then forgot about it.... >> If you choose align from the menu, then hit enter without typing anything it >> thinks you want a "4149778177-sector" alignment (and if you go back to the >> option it thinks it's a -145320191 sector alignment). >> >> The strange alignment only seems to show up when you do verify - if you >> actually add a partition it doesn't seem to use the alignment, but I didn't >> test extensively. > > I didn't reproduce this with the same version on sid. I'm not sure > you've encountered the bug with cgdisk but maybe with gdisk (as you > describe the scenario). I haven't been able to reproduce this bug. It would help if I knew: - Which program was involved (gdisk, cgdisk, etc.). - What platform is involved (i386, x86-64, etc.). (The below system information is confusing; it states both i386 and x86-64.) >> I would expect hitting enter without typing anything to leave the old alignment. > > It actually select the default value (which is "hardcoded" at 2048 in > gpt.h: #define DEFAULT_ALIGNMENT 2048). Correct, at least for gdisk. (cgdisk doesn't accept an empty input; you MUST type something with it.) >> And if I can add a side bug, on gdisk it properly detects the alignment (8 in >> my case), but then when you go to change it, it says "default = 2048" which is >> not what the old alignment was. > > I've Cced upstream user list, as i can't test with a real device but > only with a test file i've generated with dd (maybe people have ideas on > your issue). That's not a bug; that's the design intent. Most partitioning tools use 1 MiB alignment by default, so that's what gdisk sets uses as the input default, even if something else was detected when the program launched. >> -- System Information: >> Debian Release: 6.0.3 >> APT prefers stable >> APT policy: (990, 'stable'), (500, 'oldstable'), (1, 'experimental') >> Architecture: i386 (x86_64) >> >> Kernel: Linux 2.6.32 (SMP w/8 CPU cores) >> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/bash >> >> Versions of packages gdisk depends on: >> ii groff-base 1.20.1-10 GNU troff text-formatting system ( >> ii libc6 2.13-10 Embedded GNU C Library: Shared lib >> ii libgcc1 1:4.6.1-4 GCC support library >> ii libicu44 4.4.1-7 International Components for Unico >> ii libncurses5 5.7+20100313-5 shared libraries for terminal hand >> ii libpopt0 1.16-1 lib for parsing cmdline parameters >> ii libstdc++6 4.6.1-4 GNU Standard C++ Library v3 >> ii libuuid1 2.17.2-9 Universally Unique ID library >> >> gdisk recommends no packages. >> >> gdisk suggests no packages. >> >> -- no debconf information >> >> > > > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > > > > _______________________________________________ > Gptfdisk-general mailing list > Gpt...@li... > https://lists.sourceforge.net/lists/listinfo/gptfdisk-general -- Rod Smith rod...@ro... http://www.rodsbooks.com |
