public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin-announce@cygwin.com
Subject: ddrescue 1.28-2
Date: Mon, 19 Feb 2024 09:47:54 +0100	[thread overview]
Message-ID: <683d6ac0-c125-0abe-620e-d343593cc8ec@t-online.de> (raw)

The following packages have been uploaded to the Cygwin distribution:

* ddrescue-1.28-2

GNU ddrescue is a data recovery tool.  It copies data from
one file or block device (hard disc, cdrom, etc) to another, trying
hard to rescue data in case of read errors.  Ddrescue does not
truncate the output file if not asked to.  So, every time you run
it on the same output file, it tries to fill in the gaps.

https://www.gnu.org/software/ddrescue/ddrescue.html

Changes since previous Cygwin package 1.28-1:
- ddrescue no longer aborts immediately if a read fails with EACCES.

This change is Cygwin-specific. It is a workaround for the following 
interesting behavior of Windows occasionally observed when USB devices 
are read:
If a read error occurs after at least one successful read, Windows 
returns ERROR_CRC(23) which is mapped to the errno EIO by Cygwin. But 
then each additional read fails with ERROR_MEDIA_CHANGED(1110) which is 
mapped to the fallback errno EACCES. This persists until the file handle 
is closed.
If a read error occurs immediately after opening the file handle, even 
the this first read fails with ERROR_MEDIA_CHANGED.

With this workaround, such devices could be processed by ddrescue if the 
option -O (--reopen-on-error) is also specified.

The source package supports reproducible builds.

Regards,
Christian


                 reply	other threads:[~2024-02-19  8:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=683d6ac0-c125-0abe-620e-d343593cc8ec@t-online.de \
    --to=christian.franke@t-online.de \
    --cc=cygwin-announce@cygwin.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).