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).
