From: Eliot Moss <moss@cs.umass.edu>
To: Hashim Aziz <hashaziz@hotmail.com>, cygwin <cygwin@cygwin.com>
Subject: Re: [cygwin] DD bug fails to wipe last 48 sectors of a disk
Date: Tue, 23 Jun 2020 11:29:45 -0400 [thread overview]
Message-ID: <239d7547-efe8-4b59-6f4f-8a387baf8048@cs.umass.edu> (raw)
In-Reply-To: <DB7PR01MB519396195ADB3E3E1217B22BD5940@DB7PR01MB5193.eurprd01.prod.exchangelabs.com>
On 6/23/2020 11:28 AM, Hashim Aziz via Cygwin wrote:
> I hadn't checked with 512 byte block sizes because of the amount of time it would have taken, but sure enough have just finished trying with bs=512 and no block size at all (so dd's default block size, which is either 512 or 1024) and although each wipe took over 24 hours, they did indeed wipe all of the sectors. So it seems that there's a bug with regards to how Cygwin handles the last block when a large (i.e. sane) block size is selected, and that this bug doesn't occur on actual UNIX-based systems.
Well, that certainly points the finger at last-block handling ... EM
next prev parent reply other threads:[~2020-06-23 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 18:19 Hashim Aziz
[not found] ` <1d1801d64677$bea56050$3bf020f0$@pdinc.us>
2020-06-20 17:31 ` [cygwin] " Hashim Aziz
2020-06-20 20:26 ` Eliot Moss
2020-06-23 15:28 ` Hashim Aziz
2020-06-23 15:29 ` Eliot Moss [this message]
2020-06-23 16:06 ` Nicholas Clark
2020-06-23 19:46 ` Hashim Aziz
2020-06-24 10:21 ` Andrey Repin
2020-06-25 12:08 ` Hashim Aziz
2020-06-25 13:25 ` Brian Inglis
2020-06-28 14:34 ` Christian Franke
2020-06-28 17:50 ` Jason Pyeron
2020-06-28 20:28 ` Brian Inglis
2020-06-23 19:33 ` Brian Inglis
2020-12-29 0:46 ` Hashim Aziz
2020-12-29 2:41 ` Jason Pyeron
2020-12-29 17:54 ` Brian Inglis
2020-12-30 1:35 ` Jason Pyeron
[not found] ` <DB7PR01MB5193B13815933B913D11DDC2D5D20@DB7PR01MB5193.eurprd01.prod.exchangelabs.com>
2021-01-04 21:08 ` Jason Pyeron
2020-08-04 22:42 ` Hashim Aziz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=239d7547-efe8-4b59-6f4f-8a387baf8048@cs.umass.edu \
--to=moss@cs.umass.edu \
--cc=cygwin@cygwin.com \
--cc=hashaziz@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).