[this is a resend using my subscribed email]
On 1/12/25 22:57, Barry Scott wrote:
On 1 Dec 2025, at 11:33, [email protected] wrote:
I thought that maybe deleting those files left behind some delayed work that
did not complete, and the umount/eject did not wait for.
The kernel caches changes in memory and as a background task writes out the
changes.
When you umount the command should not return until all the writes to the
device have been written out.
Does umount take a second or two before returning after you write a large file
to the device?
Not long at all. And I tried to wait for a while too.
I tried a small test to see if I could duplicate what you see and I do not see
error messages.
As you have error free operation on ubuntu it's less likely to be a hardware
error.
Maybe try the USB in a different USB port, it might be the USB port that is the
problem?
Also it may be power save mode that is not providing enough power via the USB
port.
Check your power settings and see if a low power mode is selected.
I tried a different socket. Same thing.
On another machine (a laptop) I booted 6.12.17-amd64 (from a clonezilla image)
and then did the same
mount/eject dance and got the same errors.
BTW, my server is running 6.17.8-200.fc42.x86_64 (the latest for this distro).
Maybe relevant, this is a 500GB USB 3.0 SSD disk.
I do not have another similar disk. I tried a few SATA caddies (also USB 3.0)
and they do not show this problem.
I recall similar but much shorter reports before, but this many errors is a
recent thing.
It seems that this disk is not accessible after a umount. Maybe specific to
this model (Seagate Expansion SSD)?
Or related to the controller in it?
Barry
--
Eyal at Home ([email protected])
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
