GNU bug report logs - #51482
dd with status=progress does not update its output when the main writing is finished

Previous Next

Package: coreutils;

Reported by: Sworddragon <sworddragon2 <at> gmail.com>

Date: Fri, 29 Oct 2021 14:23:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 51482 in the body.
You can then email your comments to 51482 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-coreutils <at> gnu.org:
bug#51482; Package coreutils. (Fri, 29 Oct 2021 14:23:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to Sworddragon <sworddragon2 <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Fri, 29 Oct 2021 14:23:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sworddragon <sworddragon2 <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: dd with status=progress does not update its output when the main
 writing is finished
Date: Fri, 29 Oct 2021 14:22:02 +0000
[Message part 1 (text/plain, inline)]
Originally found as additional minor bug in ticket #51345 (Knoppix 9.1 with
GNU Coreutils 8.32), I think it is a good idea to create a dedicated report
for it to avoid getting it lost.

When dd is being used with status=progress it appears to update the status
every second but does not do a final update when dd finished its main
writing task (e.g. when dd starts flushing via conv=fsync and it still
blocks for like over a minute) causing the output to be incorrect and
inconsistent across multiple tries.
[Message part 2 (text/html, inline)]

Reply sent to Paul Eggert <eggert <at> cs.ucla.edu>:
You have taken responsibility. (Fri, 28 Jan 2022 02:39:01 GMT) Full text and rfc822 format available.

Notification sent to Sworddragon <sworddragon2 <at> gmail.com>:
bug acknowledged by developer. (Fri, 28 Jan 2022 02:39:01 GMT) Full text and rfc822 format available.

Message #10 received at 51482-done <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Sworddragon <sworddragon2 <at> gmail.com>
Cc: 51482-done <at> debbugs.gnu.org
Subject: Re: bug#51482: dd with status=progress does not update its output
 when the main writing is finished
Date: Thu, 27 Jan 2022 18:38:44 -0800
[Message part 1 (text/plain, inline)]
On 10/29/21 07:22, Sworddragon wrote:

> When dd is being used with status=progress it appears to update the status
> every second but does not do a final update when dd finished its main
> writing task (e.g. when dd starts flushing via conv=fsync and it still
> blocks for like over a minute) causing the output to be incorrect and
> inconsistent across multiple tries.

Thanks for mentioning that. I installed the attached to implement your 
suggestion, and am boldly closing the bug report. Please give it a try 
when you have the chance.
[0001-dd-output-final-progress-before-syncing.patch (text/x-patch, attachment)]

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Fri, 25 Feb 2022 12:24:15 GMT) Full text and rfc822 format available.

This bug report was last modified 2 years and 54 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.