Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1005101: fdisk: -w / --wipe is no longer honoured in ver 2.36
233 views
Skip to first unread message
david barber
Feb 7, 2022, 5:20:03 AM2/7/22
to
Package: fdisk
Version: 2.36.1-8+deb11u1
Severity: normal
X-Debbugs-Cc: barbed...@gmail.com
Dear Maintainer,
fdisk --wipe
- created bootable live Debian using dd
- wanted to create add'l partition for storing data (sdb3)
- previously (deb 10) used fdisk with --wipe=never option, worked successfully
- previous version 2.34 worked as expected, current version 2.36 does not honour the --wipe option
- according to man 8 fdisk, --wipe is still an option
- my workaround was to build a VM (old Debian) and perform the work there (successfully)
- keep up the good work!
David Barber
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fdisk depends on:
ii libc6 2.31-13+deb11u2
ii libfdisk1 2.36.1-8+deb11u1
ii libmount1 2.36.1-8+deb11u1
ii libncursesw6 6.2+20201114-2
ii libsmartcols1 2.36.1-8+deb11u1
ii libtinfo6 6.2+20201114-2
fdisk recommends no packages.
fdisk suggests no packages.
-- no debconf information
Version: 2.36.1-8+deb11u1
Severity: normal
X-Debbugs-Cc: barbed...@gmail.com
Dear Maintainer,
fdisk --wipe
- created bootable live Debian using dd
- wanted to create add'l partition for storing data (sdb3)
- previously (deb 10) used fdisk with --wipe=never option, worked successfully
- previous version 2.34 worked as expected, current version 2.36 does not honour the --wipe option
- according to man 8 fdisk, --wipe is still an option
- my workaround was to build a VM (old Debian) and perform the work there (successfully)
- keep up the good work!
David Barber
-- System Information:
Debian Release: 11.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-11-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fdisk depends on:
ii libc6 2.31-13+deb11u2
ii libfdisk1 2.36.1-8+deb11u1
ii libmount1 2.36.1-8+deb11u1
ii libncursesw6 6.2+20201114-2
ii libsmartcols1 2.36.1-8+deb11u1
ii libtinfo6 6.2+20201114-2
fdisk recommends no packages.
fdisk suggests no packages.
-- no debconf information
Chris Hofstaedtler
Feb 7, 2022, 12:30:04 PM2/7/22
to
Hello David Barber,
* david barber <barbed...@gmail.com> [220207 11:15]:
please:
1) which image (URL) did you use, and what was the exact dd command?
2) do you mean, --wipe=never did nothing at all? Or did it fail? Did
it wipe some data? I.e. what was your expectation and what actually
happened?
Thanks,
Chris
* david barber <barbed...@gmail.com> [220207 11:15]:
> - created bootable live Debian using dd
> - wanted to create add'l partition for storing data (sdb3)
> - previously (deb 10) used fdisk with --wipe=never option, worked successfully
> - previous version 2.34 worked as expected, current version 2.36 does not honour the --wipe option
> - according to man 8 fdisk, --wipe is still an option
> - my workaround was to build a VM (old Debian) and perform the work there (successfully)
> - keep up the good work!
Thank you for your report. Can you clarify a few things for me,
> - wanted to create add'l partition for storing data (sdb3)
> - previously (deb 10) used fdisk with --wipe=never option, worked successfully
> - previous version 2.34 worked as expected, current version 2.36 does not honour the --wipe option
> - according to man 8 fdisk, --wipe is still an option
> - my workaround was to build a VM (old Debian) and perform the work there (successfully)
> - keep up the good work!
please:
1) which image (URL) did you use, and what was the exact dd command?
2) do you mean, --wipe=never did nothing at all? Or did it fail? Did
it wipe some data? I.e. what was your expectation and what actually
happened?
Thanks,
Chris
david barber
Feb 9, 2022, 4:40:03 AM2/9/22
to
Hi Chris,
Sorry, I'm not sure how to reply within the bug tracking system.....this is my first.
1) I'm using this debian live image: 2612133888 Jan 28 00:42 debian-live-11.1.0-amd64-mate.iso
2) See below for results using both -w=never and --wipe=never on the USB stick. -w reports as unsupported wipe mode (!) and --wipe=never seems to have no effect. (warning about ISO9660 comes up even though it was told to NEVER wipe).
My dd command was as follows:
barbed2@vostro:/nas1/ISO-IMAGES$ dd if=debian-live-11.1.0-amd64-mate.iso | sudo dd of=/dev/sdf bs=4M status=progress oflag=direct
barbed2@vostro:/nas1/ISO-IMAGES$ dd if=debian-live-11.1.0-amd64-mate.iso | sudo dd of=/dev/sdf bs=4M status=progress oflag=direct
=================== begin snip ====================
root@vostro:/nas1/ISO-IMAGES# fdisk -w=never /dev/sde
fdisk: unsupported wipe mode
root@vostro:/nas1/ISO-IMAGES# fdisk --wipe=never /dev/sde
Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
The device contains 'iso9660' signature and it may remain on the device. It is recommended to wipe the device with wipefs(8) or fdisk --wipe, in order to avoid possible collisions.
Command (m for help):
fdisk: unsupported wipe mode
root@vostro:/nas1/ISO-IMAGES# fdisk --wipe=never /dev/sde
Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
The device contains 'iso9660' signature and it may remain on the device. It is recommended to wipe the device with wipefs(8) or fdisk --wipe, in order to avoid possible collisions.
Command (m for help):
=================== end snip ====================
Thanks again, pls let me know if there's anything else I can provide.
David
Chris Hofstaedtler
Feb 9, 2022, 4:40:03 AM2/9/22
to
Hi David,
thanks for following up.
* david barber <bar...@gmail.com> [220208 20:16]:
that, as long as 100...@bugs.debian.org is still in the emails
"To:" field. (I have also forwarded your reply to the bug.)
Thanks, I think thats all for now. I will try to reproduce this.
BR,
Chris
thanks for following up.
* david barber <bar...@gmail.com> [220208 20:16]:
> Sorry, I'm not sure how to reply within the bug tracking system.....this is
> my first.
No worries. If you got my original reply, you can just reply to
> my first.
that, as long as 100...@bugs.debian.org is still in the emails
"To:" field. (I have also forwarded your reply to the bug.)
BR,
Chris
david barber
Aug 24, 2022, 10:00:04 PM8/24/22
to
let's see if this adds to the thread...... :-)
---------- Forwarded message ---------
From: david barber <bar...@gmail.com>
Date: Wed, 24 Aug 2022 at 21:47
Subject: bug 1005101
To: <ze...@debian.org>
From: david barber <bar...@gmail.com>
Date: Wed, 24 Aug 2022 at 21:47
Subject: bug 1005101
To: <ze...@debian.org>
Hi Chris,
I was just wondering if anything has progressed, have you been able to reproduce, etc.?
Thanks,
David
Andreas Henriksson
Sep 3, 2022, 1:40:03 PM9/3/22
to
Hello David Barber,
Adding some hints of what I think is going on inline below....
On Tue, Feb 08, 2022 at 02:15:25PM -0500, david barber wrote:
> Hi Chris,
>
> Sorry, I'm not sure how to reply within the bug tracking system.....this is
> my first.
>
> 1) I'm using this debian live image: 2612133888 Jan 28 00:42
> debian-live-11.1.0-amd64-mate.iso
> 2) See below for results using both -w=never and --wipe=never on the USB
> stick. -w reports as unsupported wipe mode (!) and --wipe=never seems to
> have no effect. (warning about ISO9660 comes up even though it was told to
> NEVER wipe).
>
> My dd command was as follows:
> barbed2@vostro:/nas1/ISO-IMAGES$ dd if=debian-live-11.1.0-amd64-mate.iso |
> sudo dd of=/dev/sdf bs=4M status=progress oflag=direct
>
>
> =================== begin snip ====================
> root@vostro:/nas1/ISO-IMAGES# fdisk -w=never /dev/sde
> fdisk: unsupported wipe mode
This one is easy to explain. The syntax you're using is equivalent to:
`fdisk -w -= -e -v -e -r /dev/sde` (and the wipemode argument `/dev/sde`
does not match any of `auto`, `never` or `always) which is obviously not
what you really want. Thus you get the above error message.
(Additionally you're missing a target file but you never get that far
in the parsing.)
Hope this helps clear this one out.
> root@vostro:/nas1/ISO-IMAGES# fdisk --wipe=never /dev/sde
This one probably needs a bit deeper debugging to figure out.
I would normally use `fdisk --wipe never /dev/sde` naturally,
but you're not getting the previous error message so apparently
separating option and optarg using = seems to be accepted syntax.
Not sure what (if anything) goes wrong with this one.
You write "does not honour the --wipe option" and it would be helpful
if you could elaborate on what you expected and what happened.
(It's not obvious to me from the below example.)
Further investigation needed.
>
> Welcome to fdisk (util-linux 2.36.1).
> Changes will remain in memory only, until you decide to write them.
> Be careful before using the write command.
>
> The device contains 'iso9660' signature and it may remain on the device. It
> is recommended to wipe the device with wipefs(8) or fdisk --wipe, in order
> to avoid possible collisions.
>
> Command (m for help):
> =================== end snip ====================
>
>
> Thanks again, pls let me know if there's anything else I can provide.
>
> David
Regards,
Andreas Henriksson
PS. Using "reply all" in your mail user agent should do the right
thing when replying.
Adding some hints of what I think is going on inline below....
On Tue, Feb 08, 2022 at 02:15:25PM -0500, david barber wrote:
> Hi Chris,
>
> Sorry, I'm not sure how to reply within the bug tracking system.....this is
> my first.
>
> 1) I'm using this debian live image: 2612133888 Jan 28 00:42
> debian-live-11.1.0-amd64-mate.iso
> 2) See below for results using both -w=never and --wipe=never on the USB
> stick. -w reports as unsupported wipe mode (!) and --wipe=never seems to
> have no effect. (warning about ISO9660 comes up even though it was told to
> NEVER wipe).
>
> My dd command was as follows:
> barbed2@vostro:/nas1/ISO-IMAGES$ dd if=debian-live-11.1.0-amd64-mate.iso |
> sudo dd of=/dev/sdf bs=4M status=progress oflag=direct
>
>
> =================== begin snip ====================
> root@vostro:/nas1/ISO-IMAGES# fdisk -w=never /dev/sde
> fdisk: unsupported wipe mode
`fdisk -w -= -e -v -e -r /dev/sde` (and the wipemode argument `/dev/sde`
does not match any of `auto`, `never` or `always) which is obviously not
what you really want. Thus you get the above error message.
(Additionally you're missing a target file but you never get that far
in the parsing.)
Hope this helps clear this one out.
> root@vostro:/nas1/ISO-IMAGES# fdisk --wipe=never /dev/sde
I would normally use `fdisk --wipe never /dev/sde` naturally,
but you're not getting the previous error message so apparently
separating option and optarg using = seems to be accepted syntax.
Not sure what (if anything) goes wrong with this one.
You write "does not honour the --wipe option" and it would be helpful
if you could elaborate on what you expected and what happened.
(It's not obvious to me from the below example.)
Further investigation needed.
>
> Welcome to fdisk (util-linux 2.36.1).
> Changes will remain in memory only, until you decide to write them.
> Be careful before using the write command.
>
> The device contains 'iso9660' signature and it may remain on the device. It
> is recommended to wipe the device with wipefs(8) or fdisk --wipe, in order
> to avoid possible collisions.
>
> Command (m for help):
> =================== end snip ====================
>
>
> Thanks again, pls let me know if there's anything else I can provide.
>
> David
Andreas Henriksson
PS. Using "reply all" in your mail user agent should do the right
thing when replying.
0 new messages