GNU bug report logs - #78857
shred bug

Previous Next

Package: coreutils;

Reported by: KhorneTraditionalist <KhorneTraditionalist <at> proton.me>

Date: Sat, 21 Jun 2025 20:12:02 UTC

Severity: normal

To reply to this bug, email your comments to 78857 AT debbugs.gnu.org.

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#78857; Package coreutils. (Sat, 21 Jun 2025 20:12:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to KhorneTraditionalist <KhorneTraditionalist <at> proton.me>:
New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org. (Sat, 21 Jun 2025 20:12:02 GMT) Full text and rfc822 format available.

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

From: KhorneTraditionalist <KhorneTraditionalist <at> proton.me>
To: "bug-coreutils <at> gnu.org" <bug-coreutils <at> gnu.org>
Subject: shred bug
Date: Sat, 21 Jun 2025 14:57:26 +0000
[Message part 1 (text/plain, inline)]
Hi!
I've started shredding a drive /dev/sdc on the latest stable linux mint (debian), then I've connected another drive for work, and the shredding command was cancelled with an error "Error writing at offset [offset]: No such device". Apparently, Mint has automounted and assigned the name /dev/sdc to the new drive and this has confused the shred command and it stopped working. Fortunately, at least, it did not proceed to shred my working drive. Maybe, shred could reserve the drive name for itself until shredding could be completed so that automounting other drive could not lead to such issues?
[Message part 2 (text/html, inline)]

Information forwarded to bug-coreutils <at> gnu.org:
bug#78857; Package coreutils. (Sat, 21 Jun 2025 21:44:01 GMT) Full text and rfc822 format available.

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

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: KhorneTraditionalist <KhorneTraditionalist <at> proton.me>
Cc: 78857 <at> debbugs.gnu.org
Subject: Re: bug#78857: shred bug
Date: Sat, 21 Jun 2025 14:43:16 -0700
On 2025-06-21 07:57, KhorneTraditionalist via GNU coreutils Bug Reports 
wrote:
>   Maybe, shred could reserve the drive name for itself until shredding could be completed so that automounting other drive could not lead to such issues?

shred opens the named file at startup and never uses the file name 
again, so there'd be no point to reserving the drive name (assuming 
something like that could be done).

I expect the problem you observed was due to udev, not to automounting. 
If so, if mounting using a UUID should avoid the problem, whatever it is 
(I can't easily reproduce it).




This bug report was last modified 3 days ago.

Previous Next


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