Could you attach a copy of this MBR?
Massimiliano Pagani -Tecniplast S.p.A. writes:
> Hello, I was trying to use Parted to resize a partition on an USB thumb
> drive. More precisely the partition exceeded the size of the disk. Below you
> can find the complete output of the session and yet be
Jens Schmidt writes:
> OK. Thank you.
>
> But I can't believe that a segmentation fault is the common way to say
> that a partition table doesn't conform to your reference setting.
It was an assertion failure, not a seg fault.
This has nothing to do with alignment; it is because your first and
second extended partitions have no space between them to hold the EBR.
This space has been required by parted always and in the past all other
partitioning tools were believed to honor this requirement, but for some
unknown reaso
Matthijs Kooijman writes:
> Hi folks,
>
> I believe I found a bug in the dos partition table writer. Let me start
> with the cause. There's this bit of code:
>
> if (!table->boot_code[0]) {
> memset (table->boot_code, 0, 512);
> memcpy (table->boot_code, MBR_BOO
This is probably specific to the old version of parted in 16.04. Please
try upgrading to 18.04 or building parted yourself from git.
Nick Elsmore writes:
> parted crashes when I follow the below command history. I am able to
> reproduce this issue. parted launches fine and selects fine in ot
Brian C. Lane writes:
> Given the number of times this has come up it's probably worth looking
> into changing the assertion to something more understandable.
I'd rather actually fix it to support having the EBR be located
somewhere else. I have been meaning to do that for a few years now ;)
Can you provide a copy of your partition table so that we can try to
reproduce this?
Jozef Mlich writes:
> Hi,
>
> I was trying to resize partition in image file and it ended with crash
>
> /usr/sbin/parted ./rootfs.img resizepart 1
> (gdb) bt full
> #0 0x77d79123 in free () from /lib64/
Mikhail Kagalenko writes:
> Assertion (metadata_length > 0) at ../../../libparted/labels/dos.c:2313 in
> function add_logical_part_metadata() failed.
This happens because parted requires a space between logical partitions
to put the EBR. Some other unknown parittioning tool under unknown
circum
That was meant to be to -done.
Phillip Susi writes:
> 'loop' is an intentional pseudo disklabel that means there is no
> partition table.
'loop' is an intentional pseudo disklabel that means there is no
partition table.
Ricky Tigg writes:
> Hi. Initial situation:
>
> (parted) print
> Error: /dev/sdc: unrecognised disk label
> Model: Kingston DataTraveler 102 (scsi)
> Disk /dev/sdc: 8007MB
> Sector size (logical/physical): 512B/512B
Unfortunately to figure out what went wrong would require examining the
partition table, which it appears you have destroyed. If you happened
to have saved a copy and can provide it, please do so and we can reopen
the bug.
Marc Stenson writes:
> Hello,
>
> While parted 2.3 had no issues with wha
Unfortunately, I can not read it since you actually attached an odt file
instead of simply copy/paste like you said. If you still have this
information, please send it in plain text.
Alex Mackay writes:
> Hello,
>
> I was using parted and it told me I found a bug. I wasn't using anything
> other
Was the kernel able to correctly read the partition table at boot or
after running blockdev --rereadpt? If fdisk and the kernel are both
happy with it then it may just be a bug in parted.
Paul Ausbeck writes:
> When I posted the original problem I was sort of hoping to get some recovery
> adv
Closing bug since it is unrelated to parted, and not a bug.
Brent W. Baccala writes:
> Hi -
>
> I just using gparted 0.32.0 on Ubuntu Bionic 18.04 to move and resize a
> partition.
>
> Initially, there was a 25 GB partition and a 100 GB partition followed by a
> 574 GB partition. The operation
This doesn't appear to be related to parted. You should check dmesg for
more information on why mkfs failed.
carl hansen writes:
> start reading at the end.
>
>
> GParted 0.32.0 --enable-libparted-dmraid --enable-online-resize
>
>Libparted 3.2
>
>Create Primary Partition #1 (ext4, 3.
This was fixed in commit 9e196cc2902255c32. What triggered it was the
fact that you ran parted /dev/sda1 when you meant /dev/sda.
anarchonerd writes:
> Hello,
>
> I hope I am contacting the right adress here or that it, in case I
> didn't, can get forwarded. I just got an error
> message from
Nikolaus Rath writes:
> /dev/sdb6 739131392 739588095456704 223M 83 Linux
> /dev/sdb7 739588096 773142527 3355443216G 8e Linux LVM
sdb7 starts in the very next sector after sdb6, so there is no room here
for the EBR.
On 9/22/2018 4:48 AM, ПИван Петров wrote:
> 6, 7 columns shows "about parted" instead partition information (may be
> only in russian version). ubuntu 18.04.1Rus = bug; Kali 2018.3 = no bug
This was fixed upstream two years ago in commit
b81a1115c4e5855bbed8a34fcf27bcdd50456374. It appears that d
On 7/19/2018 6:56 PM, Laurence Perkins (OE) wrote:
> I'm running parted 3.2, which appears to be the latest available
> release on the gnu.org ftp site, as well as in my distribution
> (Gentoo). However it's also older than that commit, so it probably
> does not have it.
Yea, we really need to
On 6/21/2018 4:17 AM, Natanael Copa wrote:
> A wild guess is that xbsd_dkcksum does not work properly on big endian
> machines.
It looks like it handles endianess correctly, but I did notice that it
is using something called "u_short" instead of uint16_t. I wonder if on
your machine "u_short" isn
On 6/7/2018 11:23 AM, Brian C. Lane wrote:
> parted doesn't wipe signatures. Use something like wipefs for that :)
Sure it does; see ped_disk_clobber(). It wipes the first and last 8k of
the disk, which gets most signatures, but I'm guessing ZFS is not in
that range. LVM is another oddly placed
On 5/28/2018 11:10 AM, 李进良 wrote:
> Is there any patch or configure option to enable set a partuuid when
> creating partition with parted command? Now I really need this function
> because a special partuuid is used in kernel command line
> (root=PARTUUID=) and secure boot is enabled, the kern
Please provide the full output.
On 5/25/2018 3:58 PM, Robert Hollis wrote:
> Backtrace has 17 calls on stack:
> 17: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x44) [0x7f3913501e94]
> 16: /lib/x86_64-linux-gnu/libparted.so.2(+0x1e4bf) [0x7f39135154bf]
> 15: /lib/x86_64-linux-gnu/libparted.
On 5/10/2018 2:52 PM, Phil Susi wrote:
> Ok, after looking at the code it wasn't very hard to slap a few of the
> right bytes into an empty file and trick atari_probe. I've fixed it
> now. Will post the patch tomorrow. Thanks.
Nevermind; it wasn't a logical error. As long as at least one parti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/15/2016 09:35 AM, Anatoly Pugachev wrote:
> You found a bug in GNU Parted! Here's what you have to do:
>
> Assertion (bios_geom->cylinders == (PedSector) (dev->length /
> cyl_size)) at ../../../libparted/labels/sun.c:190 in function
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
It seems this was already fixed:
commit f5c628dd51c7d77ff939554425159ab6e8aef1c0
Author: Brian C. Lane
Date: Mon Jul 13 16:43:11 2015 -0700
parted: Fix crash with name command and no disklabel (#1226067)
A typo (the last I think) f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks like this was fixed a while back:
commit a3877115f1956949096d77aca5a703a47ed68397
Author: Felix Janda
Date: Sun May 3 10:33:31 2015 +0200
libparted/fs/xfs/platform_defs.h: Include for loff_t
This is needed for compilation with musl libc
S
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Looks like this was fixed a while back:
commit a3877115f1956949096d77aca5a703a47ed68397
Author: Felix Janda
Date: Sun May 3 10:33:31 2015 +0200
libparted/fs/xfs/platform_defs.h: Include for loff_t
This is needed for compilation with mu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/10/2016 04:00 PM, Curtis Gedak wrote:
> Attached is a patch to fix the issue with jump instruction and boot
> code is corrupted with random bytes after fat is resized.
>
> Thanks goes to Tom Yan, Dirk Eberhardt, and others who reported
> the p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/18/2016 07:28 PM, Ed Falat wrote:
> A bug has been detected in GNU Parted. Refer to the web site of
> parted http://www.gnu.org/software/parted/parted.html for more
> information of what could be useful for bug submitting! Please
> email a bu
Patches for new features are welcome ( writing a whole new front end
is not easy, but if you were to take a stab at writing it we could
include and maintain it ). As this is not a bug report, I am closing it.
On 03/12/2016 04:38 AM, Paul Wise wrote:
> Hi all,
>
> It would be great to have a cons
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/09/2016 05:33 PM, a wrote:
> Hello, (sorry if duplicate, but my previous send doesn't seem to
> appear on the mailing list !)
>
> I got a problem here with my MBR partition table and parted 3.2
> which only detects a "loop" partition table whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/08/2016 11:07 PM, Kerim Güney wrote:
> Hello all,
>
> I'm trying to figure out how to create "/dev/mmcblk\d+p\d+",
> "/dev/mmcblk\d+boot\d+ and "/dev/mmcblk\d+rpmb" partitions using
> parted.
>
> Can someone help me figure this out?
I'm rea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The patch is not correct because as a library, libparted can not
simply write directly to stderr; it must throw an exception instead.
In all probability the bug lies in parted itself, which should not be
calling ped_disk_get_partition on a NULL disk
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/24/2015 05:51 AM, Ankur Tank wrote:
> Thank you for replying Phillip, 1. How do we measure performance
> improvement before and after partition alignment ?
hdparm -t or dd between the drive and /dev/null or /dev/zero and the
drive ( for a des
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: forcemerge -1 22191
On 12/17/2015 11:57 AM, Brian C. Lane wrote:
> What type of disklabel is it? If it is GPT then primary, etc.
> isn't used. We should figure out how to make this clearer in the
> docs.
I guess we should change the man pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Control: forcemerge -1 22179
Control: close -1
Partitions can not possibly be created on a fraction of a sector.
Optimal alignment is much larger than a single sector: typically 1
MiB. Create your partitions on 1 MiB boundaries. When you specify
t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/08/2015 01:59 PM, Brian C. Lane wrote:
> Nak. As far as I can tell this fs isn't going anywhere, nor should
> it IMO.
While I agree that it isn't really going anywhere and it is a bit
silly that a handful of people are still clinging to it, bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/18/2015 12:07 PM, David Billsbrough wrote:
> Where in a virtual disk is the structures that store MBR, GPT,
> Inode structures and reserve areas for bad block data that is
> contained on a real physical hard drive?
Obviously the same place the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Closing since parted no longer supports creating filesystems.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCgAGBQJWXlBtAAoJEBB5UWFcu6UWMhUIAKAEwXrh8dHqBHCVMkyEmOfF
grIOuycEYfMDB7LXpJe0wOqpZp6Ta6+GCLO8Gs6cmtG1wo2r46RBXfJi5i+t4yYo
lcjx5w4qO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Closing since parted no longer supports creating filesystems.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEcBAEBCgAGBQJWXlBtAAoJEBB5UWFcu6UWMhUIAKAEwXrh8dHqBHCVMkyEmOfF
grIOuycEYfMDB7LXpJe0wOqpZp6Ta6+GCLO8Gs6cmtG1wo2r46RBXfJi5i+t4yYo
lcjx5w4qO
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
You are using an ancient version of parted and this has been fixed
some time ago; please upgrade. As for what is happening: you had
partitioned the drive using GPT and put an EFI system partition on it
so it could boot. The camera does not recogniz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/25/2015 05:12 PM, Mirko ML wrote:
> following message: Assertion (head_size <= 63) at
> ../../../libparted/labels/dos.c:662 in function
> probe_partition_for_geom() failed.
This was fixed several years ago; please upgrade.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/29/2015 06:20 AM, Holger Lietz wrote:
> Es wurde ein Bug in GNU parted entdeckt. Bitte lesen Sie die
> Webseite http://www.gnu.org/software/parted/parted.html für
> Informationen, was wichtig für einen Fehlerbericht sein könnte.
> Bitte senden
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure this isn't actually intentional. What should parted do
when run in scripting mode? There all exceptions are unhandled, so a
sane default action must be taken. I think this particular error
really should be a warning, and the default is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/17/2015 08:19 PM, Jerry Hadorn wrote:
> Could anyone tell me what this means and how do I fix? I’m trying
> to remove CM9 ice cream sandwich from a HP touch pad, in which CM
> freezes at boot up. I am a novice at this so if you could explain
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/9/2015 2:38 PM, Hans Ameel wrote:
> I have a disk with what seems a corrupt GPT partition table.
>
> When using parted in a stock installation of Debian 7; I get the
> folowing dump;
>
> I hope to have been of service reporting this bug. Glad to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/1/2015 3:22 PM, Hans Spath wrote:
> $ dd if=/dev/zero of=zero bs=1K count=1 1+0 records in 1+0 records
> out 1024 bytes (1.0 kB) copied, 0.000146148 s, 7.0 MB/s
>
> $ parted zero disk_set WARNING: You are not superuser. Watch out
> for permissio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/24/2014 10:02 PM, Kẏra wrote:
> Since quick formatting a disk doesn't actually wipe the data on a
> disk, and only overwrites a small part of it, it should be possible
> to have an option to back up the portion that will be overwritten.
> That po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please provide the exact and full message.
On 12/21/2014 3:06 PM, ingegnue wrote:
> Running version 3.2 on Parabola GNU/Linux-libre. Was going to turn
> on the boot flag of an otherwise prepped FAT32 flash drive.
>
> "The bug has most likely not affe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/05/2014 08:48 PM, Donald wrote:
> The following error message occurred while playing with parted:
>
> Assertion (head_size <= 63) at ../../../libparted/labels/dos.c:662
> in function probe_partition_for_geom() failed.
This was fixed long ago;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/24/2014 11:46 AM, Brian C. Lane wrote:
> Thanks for the report, but there isn't much we can do with that.
> It looks like you are using parted 2.3 which is fairly old at this
> point. I would suggest you start with reporting it to the
> maintai
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/12/2014 10:11 AM, Ulrich Windl wrote:
> Hello,
>
> after having created a new GPT partitioning on a HP rx6600 (that
> is going to retire), trying to install Linux failed, because the
> partitioning is not detected by parted 2.3 (the version use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2014 1:05 AM, Nuzhna Pomoshch wrote:
> This would confirm that (again, these are 512 byte sectors):
>
> # dmsetup table disk1 0 2097152 linear 253:2 256
Are you using parted 3.2, or an older version?
-BEGIN PGP SIGNATURE-
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/11/2014 2:57 AM, Ulrich Windl wrote:
dE schrieb am 08.11.2014 um 06:25 in
Nachricht
> <545da93a.4090...@gmail.com>: [...]
>> Can you provide a screenshot of Windows disk management utility?
>
> You'll have to cope with the German Vers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/7/2014 10:12 AM, Ulrich Windl wrote:
> I have a system that features a damaged partition table for an 1TB
> disk with 4kB sectors. While Windows 7 boot without any complaint,
> and diskpart is happy, GNU parted doesn't display the existing
> part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/5/2014 5:06 AM, Ulrich Windl wrote:
> Hi!
>
> This appeared when trying to report a bug for GNU parted using
> http://parted.alioth.debian.org/cgi-bin/trac.cgi/newticket :
That web site is no good any more. This is the place for reporting bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/4/2014 9:56 AM, dE wrote:
> Yes, the kernel reports both -- the logical and the physical.
> Parted knows about it, it shows both the logical and physical
> sector size, but then also it uses the logical sector size. It
> should not. There must be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/01/2014 07:10 AM, dE wrote:
> Can someone please add an option to set the sector size to custom
> or/and the physical sector size?
Why? Not using the correct sector size doesn't make sense and will
result in incorrect operation.
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 11/01/2014 07:08 AM, dE wrote:
> align-check min claims that the partition is aligned.
The default alignment is optimal, which normally equates to 1 MiB. If
you want minimal alignment you need to run parted with -a min.
-BEGIN PGP SIGNATU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/2/2014 6:11 PM, Price, Eric - Exelis.Contractor wrote:
> Sir:
>
> I download a tarball from:
>
> http://ftp.gnu.org/gnu/parted/
>
> I untar it – it seems to untar correctly
>
> The instructions say to ./configure and make (from the man page)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Again, please don't remove the bug from the Cc list.
On 10/2/2014 6:52 PM, Price, Eric - Exelis.Contractor wrote:
> We are restoring a Windows 2000 image it will not boot up after
> restauration - the problem is specific to out SCSI RAID drives
A 14
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please keep the bug in the Cc list so that others can follow the
conversation ( possibly in the distant future ).
On 10/1/2014 5:23 PM, Price, Eric - Exelis.Contractor wrote:
> Sir:
>
> A little background on our problem we are copying disk images of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/24/2014 1:48 PM, Price, Eric - Exelis.Contractor wrote:
> Sir: We are experiencing some odd behavior with the parted
> command. I am trying to reconstruct a partition table entry on a
> scsi raid drive. When we do this our ending CHS is off by one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/13/2014 7:53 AM, Ludovic Courtès wrote:
> Hello,
>
> t0251-gpt-unicode.sh requires the C.UTF-8 locale and fails if it
> isn’t available.
>
> What about:
>
> 1. Exiting with 77 when the locale is unavailable?
>
> 2. Choosing another locale, suc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/3/2014 6:53 PM, Mark H Weaver wrote:
> parted-3.2 fails the same test when built on GNU Guix because the
> "C.UTF-8" locale is not available (see below). Changing
> t0251-gpt-unicode.sh to use "en_US.UTF-8" fixes the problem.
What? It should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reopen 17943
thanks
On 7/21/2014 12:32 PM, Curtis Gedak wrote:
> This error is likely not a great concern, though I should mention
> that this is a stock install of Debian 7 from the
> debian-7.0.0-i386-xfce-CD-1.iso where I selected "Canada" as the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/17/2014 3:35 PM, Curtis Gedak wrote:
> Hi Phillip,
>
> In my Debian 7 VM I ran 'apt-get update' and 'apt-get upgrade' to
> ensure that I had the latest packages.
>
> Next I removed the entire parted-3.1.90 directory, rebuilt parted,
> and then r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/14/2014 03:28 PM, Brian C. Lane wrote:
> The compelling reason for the change, other than just following
> mdadm's suggestion is Doug's example scenario from the bz entry:
>
> "It's possible, although it means you have a broken setup, that
> y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/14/2014 01:11 PM, Rod Smith wrote:
>> How is this at all related? Windows already ignores 0x83.
>
> It does with the default set of drivers. What if somebody loads a
> Linux filesystem driver, though? I don't happen to know what
> actually ha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/14/2014 06:58 PM, Chris Murphy wrote:
> This is just changing the goal posts. You asked why change, I
> provided several reasons, you come back with "hand waving" for
> only one of those reasons, and ignore the three comments in the
> bug repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/2014 4:03 PM, Chris Murphy wrote:
> They look at the type code first. If it's a type code they support,
> but the partition isn't something they expect, they actively
> suggest the user initialize the partition. It's similar for
> Windows.
Rig
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/2014 2:33 PM, Chris Murphy wrote:
> I haven't test it, but as Apple long ago deprecated fstab in favor
> of automounting anything it recognizes, I'd expect it would
> automount this configuration. But what does happen isn't as
> important as wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/2014 12:26 PM, Chris Murphy wrote:
>> How is this at all related? Windows already ignores 0x83.
>
> It does not ignore EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 on GPT
> disks. Yet parted for *years* has wrongly used this type code by
> default fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/14/2014 11:40 AM, Brian C. Lane wrote:
> It ends up that 0xFD is only supposed to be used for mdraid 0.9
> metadata. For 1.0 and later they want 0xDA so that it isn't auto
> assembled and gets ignored by everything else.
Says who? 1.x won't be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/13/2014 9:07 PM, Chris Murphy wrote:
>> Why does it matter? Linux doesn't pay attention to the
>> partition type code anyhow. I've always just used 0x83.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1118065#c5
> https://bugzilla.redhat.com/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 07/10/2014 07:58 PM, Chris Murphy wrote:
> This is in master branch.
>
> libparted/labels/dos.c 98 #define PARTITION_LINUX_RAID0xfd
>
>
> This type code and metadata version 0.9 are long deprecated.
> Parted lacks support for the "non-f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/24/2014 9:04 PM, snyh wrote:
> http://www.gnu.org/software/parted/api/group__PedDisk.html#gb7bdf36cd2beb7b015088ed305830775
>
> s/table off a device/table of device/
That's not a typo. Grammatically I suppose it should be "off of" but
it is qui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/12/2014 10:13 AM, dimonik, dimonik wrote:
> Hello, it seems i found a bug :)
>
> Package: parted
>
> Version 2.3-20
>
> OS: Linux 3.13-1-amd64 #1 SMP Debian 3.13.7-1 (2014-03-25) x86_64
> GNU/Linux
>
> VERSION $ apt-cache policy parted part
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/22/2014 03:01 PM, Brian C. Lane wrote:
> Sure enough, I was missing that one. Looks good, and passes all
> tests on all arches.
Patches pushed.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/05/2014 07:32 PM, Brian C. Lane wrote:
>> Just noticed I didn't Cc you on this, was that an ack on this one
>> with the fixed test?
>
> Yes. Also, I'm on the lists so no need for explicit cc's
Patch pushed.
-BEGIN PGP SIGNATURE-
Vers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/21/2014 8:42 PM, Brian C. Lane wrote:
> The problem is that the ntfs probe has a fixed 512b buffer and
> tries to read a whole sector into it. The fat probes may also have
> similar issues.
You must be using an out of date tree; commit 80678bdd95
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/8/2014 11:22 AM, Brian C. Lane wrote:
>> Can you look into why/what fails on your system? I also notice
>> yours says version 3.1 while mine is 3.1.98-c457. Did you check
>> out 3.1 instead of master and then not run bootstrap/configure
>> after
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/07/2014 06:49 PM, Brian C. Lane wrote:
> NAK. These make a pile of the tests fail:
>
> == GNU parted 3.1:
> tests/test-suite.log == #
> TOTAL: 77 # PASS: 27 # SKI
fat and ntfs boot sectors are very similar to an MBR so if you had one of
these filesystems on an unpartitioned disk, parted detected them as a dos
partition table. Have the dos label code call the fat and ntfs filesystem
probes and if they recognize the sector ( their tests are more stringent )
t
"libparted: avoid disturbing partitions" put the remove of the old
partition in second pass. If you simultaneously removed partitions 1
and 2, and created a new partition #1 that overlapped the previous second
partition, the sync would fail because it would try to create the new,
larger partition
The loop label type was using the existence of a partition as a proxy for
a filesystem being detected, and loop_write() would try to write a loop
signature if there was no filesystem, and erase it if there was. Because
of this, creating a partition without writing a filesystem to it caused
loop_wr
The loop label represents an unpartitioned disk, but creates
a dummy partition to represent the whole disk. This dummy partition
was actually being loaded into the kernel. Don't do that.
---
NEWS | 4
libparted/arch/linux.c | 3 +++
2 files changed, 7 insertions(+)
diff -
Partprobe was not syncing loop labels. This resulted it failing to remove
existing partitions when switching to a loop label.
---
NEWS | 3 +++
partprobe/partprobe.c | 4 +---
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/NEWS b/NEWS
index 385a120..f99c6fe 100644
We were limiting partition sync operations to the lesser number allowed
by the device, or the label. This meant that when creating a new label
over an old label that had more partitions than the new one allows, the
higher partitions would not be removed. Use the greater of the two values
for the
ped_partition_get_path() was returning "/dev/foo1" instead of
"/dev/foo" on loop labels. This caused gparted to run tools like mkfs on
a device node that did not actually exist.
---
NEWS | 3 +++
libparted/arch/linux.c | 10 --
2 files changed, 11 insertions(+), 2 delet
If you deleted the fake partition on a loop label, loop_write() would write
the loop signature to the device, zeroing out all other bytes in the first
sector. When the disk contained an ext[234] filesystem and was using 2k
sectors, this would trash the super block residing in the 1-2kb part of the
I have refactored the loop fixes making them cleaner, and breaking them out
into separate patches for easier review.
Phillip Susi (9):
libparted: don't detect fat and ntfs boot sectors as dos MBR
libparted: remove old partitions *first* before adding new ones
libparted: remove al
Verify previous fixes to loop labels.
---
tests/Makefile.am | 1 +
tests/t1102-loop-label.sh | 104 ++
2 files changed, 105 insertions(+)
create mode 100644 tests/t1102-loop-label.sh
diff --git a/tests/Makefile.am b/tests/Makefile.am
index e0
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/18/2014 06:55 PM, Phillip Susi wrote:
> I could have sworn I fixed that test before, but here it is
>
> 8<>8
>
> gpt was using a static local variable to suppress repeatedly
> reporting
I could have sworn I fixed that test before, but here it is
8<>8
gpt was using a static local variable to suppress repeatedly reporting
an error if you chose to ignore it. This is incorrect as the variable is
global to all disks, and ignoring the error on one should n
The changes to fix filesystem detection on non 512 byte sector sizes broke
fat filesystem resizing.
---
libparted/fs/r/fat/fat.c| 6 +-
libparted/fs/r/fat/resize.c | 10 ++
2 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/libparted/fs/r/fat/fat.c b/libparted/fs/r/fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/17/2014 06:14 PM, Brian C. Lane wrote:
> On Sat, Mar 29, 2014 at 04:31:39PM -0400, Phillip Susi wrote:
>> This test was ignoring the requested sector size and always
>> using 512 bytes per sector. Fix it to use the requested
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/17/2014 06:12 PM, Brian C. Lane wrote:
> On Sat, Mar 29, 2014 at 01:49:09PM -0400, Phillip Susi wrote:
>> Enable probing for filesystems with non 512 byte sectors, and fix
>> up each filesystem to correctly handle that. Remo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have no idea why this was sent, and the issue is specific to debian,
not gnu parted.
On 4/12/2014 3:10 PM, Glenn Morris wrote:
>
> The following seems to be some kind of automated email that was
> intended for bug-parted@gnu.org. But because it see
1 - 100 of 243 matches
Mail list logo
