Parted bug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Parted |
New
|
Undecided
|
Unassigned |
Bug Description
when you try to make a partition with fs like this
# parted /dev/sda 1 fat16
you get this message:
root@ample-
WARNING: you are attempting to use parted to operate on (mkfs) a file system.
parted's file system manipulation code is not as robust as what you'll find in
dedicated, file-system-
you use parted only to manipulate partition tables, whenever possible.
Support for performing most operations on most types of file systems
will be removed in an upcoming release.
Warning: The existing file system will be destroyed and all data on the partition will be lost. Do you want to continue?
parted: invalid token: 1
Yes/No? Yes
Partition number? 1
File system type? [ext2]? fat16
Backtrace has 9 calls on stack:
9: /lib/x86_
8: /lib/x86_
7: /lib/x86_
6: /lib/x86_
5: parted() [0x4083b1]
4: parted(
3: parted(main+0x146d) [0x4064ed]
2: /lib/x86_
1: parted() [0x406617]
You found a bug in GNU Parted! Here's what you have to do:
Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:
Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:
http://
Please check this version prior to bug reporting.
If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:
http://
for further information.
Your report should contain the version of this release (2.3)
along with the error message below, the output of
parted DEVICE unit co print unit s print
and the following history of commands you entered.
Also include any additional information about your setup you
consider important.
Assertion (bs != NULL) at ../../.
Aborted (core dumped)
# dpkg -l | grep parted
ii libparted0debia
ii parted 2.3-19ubuntu1.
This is not a MAAS bug as MAAS doesn't perform the installation. It is also not a curtin bug as curtin doesn't use parted either. Please file this bug accordingly.