linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219362] USB SATA does not correctly shutdown the SSD upon poweroff causing data loss
Date: Tue, 08 Oct 2024 11:53:30 +0000	[thread overview]
Message-ID: <bug-219362-208809-XKCyncgzW0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219362-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219362

--- Comment #1 from gregkh@linuxfoundation.org ---
On Tue, Oct 08, 2024 at 11:43:02AM +0000, bugzilla-daemon@kernel.org wrote:
> I have SATA SSD drive connected via TUSB9261 converter. Eventualy i
> experience
> filesystem inconsistency when i repeatedly shutdown the device like this:
> 
> echo s > /proc/sysrq-trigger;
> echo u > /proc/sysrq-trigger;
> echo o > /proc/sysrq-trigger;

Don't do that, you will end up with an unstable system.  Please always
shutdown like normal.

> Same problem does not occur when i do this:
> 
> echo s > /proc/sysrq-trigger;
> echo u > /proc/sysrq-trigger;
> for i in /sys/block/*/device/delete; do echo 1 > "$i"; done;
> echo o > /proc/sysrq-trigger;

Yes, that is because you are shutting down things in the proper order,
like a normal shutdown will do.

sysrq is not for a normal shutdown, again, do not do that and expect to
have data saved properly.

good luck!

greg k-h

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-10-08 11:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-08 11:43 [Bug 219362] New: USB SATA does not correctly shutdown the SSD upon poweroff causing data loss bugzilla-daemon
2024-10-08 11:53 ` Greg KH
2024-10-08 11:53 ` bugzilla-daemon [this message]
2024-10-08 12:00 ` [Bug 219362] " bugzilla-daemon
2024-10-08 12:08   ` Greg KH
2024-10-08 12:08 ` bugzilla-daemon
2024-10-08 12:22 ` bugzilla-daemon
2024-10-08 13:27   ` Oliver Neukum
2024-10-08 13:27 ` bugzilla-daemon
2024-10-08 15:04 ` bugzilla-daemon
2024-10-08 15:15 ` bugzilla-daemon
2024-10-08 15:17 ` bugzilla-daemon
2024-10-08 16:13 ` bugzilla-daemon
2024-10-08 16:24 ` bugzilla-daemon
2024-10-09 10:08 ` bugzilla-daemon
2024-10-09 10:34   ` Greg KH
2024-10-09 10:34 ` bugzilla-daemon
2024-10-09 10:41 ` bugzilla-daemon
2024-10-09 10:44 ` bugzilla-daemon
2024-10-09 12:54 ` bugzilla-daemon
2024-10-09 13:32 ` bugzilla-daemon
2024-10-09 14:19 ` bugzilla-daemon
2024-10-09 16:13 ` bugzilla-daemon
2024-10-09 17:44 ` bugzilla-daemon
2024-10-10  7:10 ` bugzilla-daemon

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=bug-219362-208809-XKCyncgzW0@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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 NNTP newsgroup(s).