From: Jonathan Woithe <jwoithe@just42.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org
Subject: Re: Samsung T5 SSD: "Synchronize Cache(10) failed" on removal
Date: Sun, 10 Sep 2023 18:41:31 +0930 [thread overview]
Message-ID: <ZP2IQxeiAZpC+578@marvin.atrad.com.au> (raw)
In-Reply-To: <62aaef13-c782-4d18-a59e-f8c1b24b595f@rowland.harvard.edu>
Hi Alan
On Sat, Sep 09, 2023 at 12:14:49PM -0400, Alan Stern wrote:
> > If on the other hand it' is something best fixed, please let me know how I
> > can assist with this.
>
> The most likely situation where this would indicate a real problem would
> be if you had mounted a filesystem on the drive, written some data, and
> then unplugged it without unmounting first. If you haven't done that
> then you don't have to worry about anything.
Thanks for confirming this. The scenarios I've outlined all involve drives
which have definitely been unmounted before they were unplugged. Thus, so
long as the unmount has been done then this error can be ignored.
I guess what drew my attention to the message is that USB flash drives do
not show the "Synchronize Cache(10) failed" error when unplugged. I guess
the different behaviour may be the result of varying caching arrangements
(or other low level structural details) across the devices.
> On the other hand, if you would like to get rid of those annoying error
> messages, you can do so by telling the kernel that the drive is about to
> be removed before you unplug it. You do this by writing to the "remove"
> attribute file in the USB device's sysfs device directory; this is the
> equivalent of using the "Safely remove a device" button in Windows.
> Some GUIs may provide an easy-to-use mechanism for doing this, such as
> an "eject" selection on a device menu.
I've noticed separate "Eject" and "Unmount" items under various desktop
environments and always wondered why they were separated. Thanks for
providing the missing information. I personally run a very simple window
manager (fvwm2) so don't get device menus. If the message gets to me I'll
look into arranging for the sysfs attribute write. However, knowing now
that it's essentially a quirk of the way the device interacts with the
subsystem I will be happy to simply leave things as they are.
Thank you again for taking the time to respond.
Regards
jonathan
next prev parent reply other threads:[~2023-09-10 9:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 8:06 Samsung T5 SSD: "Synchronize Cache(10) failed" on removal Jonathan Woithe
2023-09-09 16:14 ` Alan Stern
2023-09-10 9:11 ` Jonathan Woithe [this message]
2023-09-10 14:35 ` Alan Stern
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=ZP2IQxeiAZpC+578@marvin.atrad.com.au \
--to=jwoithe@just42.net \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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