s
point. I suggest that you contact VMWare for support.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
to work
around this other than not using parted on these disk.
Thanks,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
https://www.gnu.org/software/parted/api/index.html has been updated for
libparted 3.6 using Doxygen 1.9.6
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
I can track down what generates those pages. I'm not even
sure Doxygen will generate useful output with the current codebase, I
know I've never tried.
Thanks,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
hought:*
>
> parted codes need refresh according to kernel of return value.
Thanks, I'll have to dig into this when I have time. As a workaround you
don't need to attach the file to a loop device, parted can run on the
file directly.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
On Fri, Oct 06, 2023 at 12:12:44AM +0200, Jan Palus wrote:
> On 04.10.2023 13:52, Brian C. Lane wrote:
> > On Tue, Oct 03, 2023 at 07:01:52PM +0200, Jan Palus wrote:
> > > autoconf macro PARTED_CHECK_LIBPARTED requires ped_get_version() to
> > > return 3 part version s
ot;.
>
>
>
Thanks for the report. Where is this causing problems for you? As far as
I can tell that code has been there since the start of the git history,
and I've never seen a failure. I'm actually not sure it ever gets called
by anything -- nothing uses the PARTED_CHECK_LIBPARTED m
doesn't make sense to parted. And even if it did, the only useful
command would be print. You wouldn't want to run mkpart on multiple
devices at once.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
This is uncovered by lld linker linking fatresize package
> due to this linker defaulting to --no-allow-shlib-undefined.
Thanks! Merged into master.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
a bug with whatever distribution you are
running.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
o the parted-devel mailing list:
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/parted-devel
(and you can also ask questions there, the audience should be wider than
the bug tracker).
Thanks!
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
7.
Those releases use older versions of parted, so the current release
isn't expected to build on them.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
GiB
the 2nd print claims.
My initial guess is that this disk is reporting inaccurate information
and that's confusing parted. I'd look at the bootup output from dmesg to
see what the kernel saw at boot time, and to check for disk errors in
dmesg/journald output.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
dditional question arises for my understanding though, how come a
> partition
> with CHS address of the first sector equal to the last one is usable ?
Well, nothing should be actually using the CHS values these days. So
it's possible that's a bug that doesn't matter in practice, but I'll
have to l
Disks. Judging from the positive responses to
> the patch, it seems it just slipped through the cracks. I hope it's
> still the right solution.
I have it on my list of things for the new year, but I'd like to get
more feedback on it. It looks simple enough, but you know how that can
go..
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
p or
whatever). When you rerun parted without actually creating that
filesystem it doesn't show anything because it hasn't detected a
filesystem on the partition. If you create an ext4 filesystem on that
partition it will show ext4.
Note that in the current master version of parted it can show the actual
part
sible to use a msdos disklabel with UEFI, it should be using GPT.
I'm also not sure why a UEFI system wouldn't boot with the MBR written.
It should just ignore it and use the ESP partition.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
ype to ntfs will set the
partition type for an NTFS filesystem, but will not actually format it.
You need to use mkfs.ntfs to do that.
Good Luck,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
your application?
https://alioth-lists.debian.net/pipermail/parted-devel/2022-August/005819.html
Thanks,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
rk again.
I'm not entirely sure what to do about this. It's obviously a change in
behavior, but it's a result of a big improvement in the code that I'd
rather not revert. I should have bumped the library version to indicate
this.
I'm cc'ing this to the parted-devel list to get more input on how t
k like a parted problem.
Please include the cmdline you ran, the version of parted you are
running, and whatever other relevant details if you want help figuring
out what's wrong.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
filesystem on it, the logical partition
does.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
s.gnu.org.
>
> Please do not send mail to help-debb...@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 55009: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=55009
> GNU Bug Tracking System
> Contact help-debb...@gnu.org with probl
D specific attributes when writing the GPT header. Previously
they were set to 0.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
On Thu, Apr 07, 2022 at 06:19:02AM +0800, Steven Shiau wrote:
>
> On 4/7/22 00:27, Brian C. Lane wrote:
> > On Wed, Apr 06, 2022 at 02:20:56PM +0800, Steven Shiau wrote:
> >
> >> So my questions: (1) Is there any option we can use to ignore the
> >> error/
artitions is an error, and script mode tries
pretty hard to make sure you can't accidentally destroy your data.
Please include the output from
parted /dev/sda unit s print
so we can see what parted thinks the sector locations and lengths are.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax
On Wed, Mar 30, 2022 at 09:57:24AM -0700, Brian C. Lane wrote:
> Here are the compressed sources and a GPG detached signature[*]:
> http://alpha.gnu.org/gnu/parted/parted-3.4.64.tar.xz
> http://alpha.gnu.org/gnu/parted/parted-3.4.64.tar.xz.sig
There is now a 3.4.64.2 alpha build,
Without arguments, 'print' displays the entire partition table. However "
> --
> 2.34.1
>
>
>
>
Pushed to master, thanks.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
they were set to 0.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
signature.asc
Description: PGP signature
ny info on what
object it was trying to reference.
Can you provide any other details? Maybe try running it with gdb?
Thanks,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
On Mon, Feb 07, 2022 at 08:52:33AM -0800, Brian C. Lane wrote:
> On Sat, Feb 05, 2022 at 10:44:29AM +, Kerin Millar wrote:
> > Hello,
> >
> > The attached patch rectifies some test failures that were reported at
> > https://bugs.gentoo.org/774363. Whet
:) I'd prefer a solution that continues to use hex
so that future users don't have to figure out what's going on.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
estion. There isn't anything parted can do about that.
Also, version 2.4 is quite old at this point -- but even with a newer
version you would have the same problem.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
artition that they didn't leave the required space before the first
logical partition. There's nothing that parted can do about that.
Although given how often this seems to come up I may look at adding an
actual error output instead of using the assert.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
appen, it is a pretty fine line between losing just the backup GPT and
losing the end of the last partition (assuming it is fully utilized).
I'm not sure it's worth adding extra code and the potential for new bugs
if this isn't a common practice.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
B 16.7MB 16.7MB primary
>
>
> The fault result is cause by commit 61dd3d4:
> Use BLKSSZGET to get device sector size in _device_probe_geometry()
I would strongly suggest that you don't use cyl as a unit. There is no
good reason to be doing that in 2021.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
;chromeos_kernel" and "palo". state should
> be ei‐
> ther "on" or "off".
>
> it also works for the flag "*bios_grub*" not listed above
>
Thanks, I've fixed this on the master branch.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
extended partition's metadata. There isn't
anything parted can do about that, and the only way to fix that is to
re-partition your disk.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
0.
> I suppose this bug#51407 can be closed. Thanks again.
The kernel doesn't call parted. So this is bound to be something else.
Thanks,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
pture any unexpected error codes from the kernel.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
with --script it will automatically fix the size of the disk
and write the backup partition table.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
that you need to run mkfs.ext4
on the new partition. The partition value in parted is to tell parted
what you plan to use it for so that it can setup the UUID or partition
type correctly.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
On Fri, Jul 16, 2021 at 11:15:46AM +0100, Ross Burton wrote:
> The tests t1100-busy-label.sh and t1101-busy-partition.sh both fail if
> vfat file system support is not enabled instead of skipping.
This has been fixed. Thanks for the help!
Brian
--
Brian C. Lane (PST8PDT) - weldr.io -
ds up the lowest we can go is 267 on
the fat32 test because fat32 won't work on anything smaller than 256.
All the others have been reduced to 10, so hopefully this is enough to
squeak by on a small system.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
it are also disabled.
I can't get things to compile at all if I turn on discover mode on
Fedora so I can't test whether that's the only change needed.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
o this
is telling you that sector 122880 (60*1024*1024) is already in use and
it has to use the next sector instead. The other units use a snap
algorithm with a radius of half the unit size (eg. 500k for MB) so it
doesn't have this problem, and it is the default so that's why the
output units are in MB.
Bri
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
ph or
not Ceph they need to find a better way.
My suggestion would be to use GPT partition tables and a ceph related
UUID for the partition type. Or names for the partitions.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
.
Thanks for the clarification.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
BIOS cylinder,head,sector geometry: 55,255,9. Each cylinder is 9400kB.
> Partition Table: loop
> Disk Flags:
>
> Thanks!
>
> Eric (Wood)
>
That looks like parted wasn't used to partition the disk, the file
system is starting at sector 0 and the table is 'loop'.
I'm not clear on what you think is wrong with parted.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
on 2 and partition 5 also use
some of that space. This is likely confusing parted, so I'd say it isn't
a bug, it's just trying to do the best it can with the available space.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
n-root. But I did expect a
> terse(r) error message.
>
> For example, the following error message is expectedly terse.
>
> $ partprobe /dev/sdf
> Error: Error opening /dev/sdf: Permission denied
The first line says that, the rest provides additional context what can
sometimes be useful.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
the
primary.
If this happens again (hope not!) make a copy of the first and last 1M
of the disk and email it to me so I can poke at it.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
hem an email with the new
version.
I've also added a note to the README-release file, since this part of
the process wasn't mentioned anywhere.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
e.
Yes, parted calls fsync when it is done with the device. It always opens
the device in RW mode and always fsync's it when closing it to make sure
any changes make it to disk.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
How did you get valgrind to hit that? I'm not seeing it complain about
bsd.c on Fedora.
I've pushed this fix to master.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
s, etc.).
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
he case there's nothing parted can do about it.
> See also:
>
>
>
> *pi@raspberrypi:~ $ sudo parted sdb unit co print unit s printError: Could
> not stat device sdb - No such file or directory.Retry/Cancel? c*
You told it to use sdb, not /dev/sdb in that case :)
Brian
--
Bri
a loss when things go wrong. The script mode defaults to 'safe' for
all of the prompts like this to avoid unexpected surprises.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
] == ENOMEM
>
> Accordingly to the changes made in block/partitions/core.c
> That is making parted working again.
I dug into this and it's a kernel bug that will be fixed in 5.9 rc5 as
well as backported to 5.8.10 so changing it in parted isn't the right
solution.
Thanks,
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
] == ENOMEM
>
> Accordingly to the changes made in block/partitions/core.c
> That is making parted working again.
Thanks for tracking that down.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
ke sgpart or debian does have a problem though, they
should be notifying the kernel of the change when you resize the
partition. If I do the same steps on Fedora, using sgdisk or parted I
don't need to run partprobe for lsblk to show the updated size.
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax
ve the size of the disk ?
When using non-IEC units like MB, GB parted will round the request to
+/- 50% of the unit. Usually it will snap to someplace near what you
expect, but not always, depending on the surrounding partitions.
To specify exact locations use either sectors ('s') or IEC units
on't try to turn -1
into an option:
parted --script -- /dev/sda mkpart primary 515 -1
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
> 3: parted(main+0x139b) [0x563d15d1380b]
> 2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3)
> [0x7f1212b160b3]
> 1: parted(_start+0x2e) [0x563d15d1389e]
What happens if you rerun it and just do `print devices` without trying
resizepart first?
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
2048s != 0s
Ignore/Cancel?
This means that it needs to be multiples of 2048 sectors to be aligned
(this example is just an example with a disk image).
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
modified after that.
>
> Doing the test manually without ansible context shows it's parted itself
> which apply this change:
No, parted doesn't do anything to ownership or permissions. My guess is
that udev is doing something when the device is opened/closed. How does
ceph set the ownership?
--
artitions that are
> currently mounted or in use.
>
> Still get the follow message
> raf@raf-desktop:~$ gparted
parted is not gparted, those errors don't look like something that we
output.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
ent reported by the device, so if it
reports 512b that's what it will use. There's no way to override this
and have it calculate a different alignment automatically.
But you can use the MiB units to set the sizes yourself so that you can
make them start exactly where you want them.
--
Brian C. L
cannot think of a good reason to remove or resize a mounted
partition. Why not unmount it first and avoid the issue completely?
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
that has shrunk.
Given the amount of work that would be needed to support this, and that
this is a corner case I don't think it's something I want to tackle.
Really, you shouldn't be copying pieces of disks around. Make a new
partition and copy the data -- it's safer that way.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
> 2 273MB 15.9GB 15.7GB primary ext4
>
> (parted) resizepart 2
> End? [15.9GB]?
> free(): invalid pointer
> zsh: abort sudo parted /dev/sdc
Thanks, that should be fixed by
https://github.com/bcl/parted/commit/883813c365482d06d05a1998e066792c48156f23
which I'll push today.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
Update of sr #109945 (project parted):
Status:None => Invalid
Open/Closed:Open => Closed
___
Follow-up Comment #1:
I would suggest not
Update of sr #110102 (project parted):
Status:None => Wont Do
Open/Closed:Open => Closed
___
Follow-up Comment #1:
I don't think it's
ces
> print list
> resize
> resizepart
> 2
Thanks for the report! I actually have a fix for this that got lost.
https://github.com/bcl/parted/commits/master-1701411
I'll re-send those to the list after I test them against the current
master.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart
Update of sr #109955 (project parted):
Open/Closed:Open => Closed
___
Follow-up Comment #2:
That's expected, this is an alpha release. It's the first release that I've
done so I'm taking
.gnu.org/git/parted.git
>
> instead of:
>
> git clone https://git.savannah.gnu.org/git/parted.git
Thanks, fixed.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted
b19fe8d3c4b94e172fc0bd2c7c I added a message
that describes the failure with a bit more detail. It will print
something like:
% !=
I'm guessing Ubuntu doesn't have that patch, and the 3.2 tarball is
getting *really* old at this point (which is why I'm working toward a
3.3 release soon).
Brian
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted
364,7 @@
> max_part = i;
> }
>
> - label->d_npartitions = PED_CPU_TO_LE16 (max_part) + 1;
> + label->d_npartitions = PED_CPU_TO_LE16 (max_part + 1);
> label->d_checksum = xbsd_dkcksum (label);
>
> alpha_bootblock_checksum (bsd_specific->boot_code);
Ack, thanks!
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted
On Wed, Jul 31, 2019 at 01:55:30PM -0700, Brian C. Lane wrote:
> On Wed, Jul 31, 2019 at 08:14:52PM +0200, Andreas Hellquist wrote:
> > Parted version 3.2 crashed when trying to select a usb storage device
> > without a filesystem and partitions using "select DEVICE".
ing like wipefs on the disk before creating the new partitions.
Thanks,
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted
e version provided with Debian? I'm not sure
exactly which version wheezy included, but I'm sure it was newer than
1.8.1 and buster has 3.2
https://packages.debian.org/search?keywords=parted=names=all=all
The version you are trying to use is ancient, and I would not recommend
using it at all.
--
Bria
On Thu, Jun 20, 2019 at 09:50:57PM +, Slater, Joseph wrote:
> Since I do not expect to ever submit another patch for parted, I decided to
> attach one here rather than join the maillist.
Thanks, sent this along with changes to all the other uses of it to the
parted devel list.
--
B
an the partitions, so the device entries
are probably being recreated by udev, changing their ownership back to
whatever udev thinks they should be.
--
Brian C. Lane (PST8PDT) - weldr.io - lorax - parted
gracefully :-)
Given the number of times this has come up it's probably worth looking
into changing the assertion to something more understandable.
--
Brian C. Lane (PST8PDT)
fedora 29 package parted-3.2-36.fc29.x86_64
patches are on the parted-devel mailing list. Ends up it was an
uninitialized pointer.
--
Brian C. Lane (PST8PDT)
t run it like this:
parted -s ./disk.img resizepart 1
Or without -s and hit enter at the default prompt. Something is wrong
with the handling of the *end_input I think (looking into it now).
--
Brian C. Lane (PST8PDT)
THIS is the patchset pushed to master and in Fedora's parted-3.2-41
build for rawhide. Accidentally closed the wrong one earlier.
--
Brian C. Lane (PST8PDT)
Sorry, I closed the wrong bug. Hopefully mklabel gpt works for you :)
--
Brian C. Lane (PST8PDT)
for metadata.
Some partitioning tools don't enforce this, and parted does so you get
an assertion until you recreate the partition layout.
--
Brian C. Lane (PST8PDT)
Pushed these to master, also included in parted-3.2-41 build for Fedora
Rawhide.
--
Brian C. Lane (PST8PDT)
Closing this
--
Brian C. Lane (PST8PDT)
Closing this.
--
Brian C. Lane (PST8PDT)
rted /dev/sdc
>
> mklabel gtp yes
Try mklabel gpt :)
--
Brian C. Lane (PST8PDT)
On Tue, Feb 12, 2019 at 04:41:47PM +, Mike Small wrote:
> "Brian C. Lane" writes:
>
> > On Fri, Feb 08, 2019 at 11:03:55PM +, Mike Small wrote:
> >> Hi,
> >>
> >> Someone shared with me a case where parted 3.2 (3.2-15 as packaged in
>
(sizeof(struct nilfs2_super_block) % geom->dev->sector_size
> == 0) ? 0 : 1;
This calculation is correct, but I find it hard to read. If you use the
same technique as it does for sectors it would be easier to understand
in the future, and I don't think the superblock size is going to change.
--
Brian C. Lane (PST8PDT)
iB
I don't understand what you mean by it applying to one unit at a time.
Can you give an example of what isn't working as expected?
--
Brian C. Lane (PST8PDT)
Disks start at partition 0. But you can't use it because then you'd be
overwriting the MBR.
--
Brian C. Lane (PST8PDT)
1 - 100 of 261 matches
Mail list logo
