All of lore.kernel.org
 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: Wed, 09 Oct 2024 17:44:50 +0000	[thread overview]
Message-ID: <bug-219362-208809-1roYxLE7XJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219362-208809@https.bugzilla.kernel.org/>

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

Michał Pecio (michal.pecio@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.pecio@gmail.com

--- Comment #17 from Michał Pecio (michal.pecio@gmail.com) ---
These operations are asynchronous and they don't even seem to be synchronized
against each other. This is what I got from s followed u:

[ 9oct 19:21] sysrq: Emergency Sync
[  +0,000028] sysrq: Emergency Remount R/O
[  +0,019142] EXT4-fs (sda2): re-mounted ef717e3d-539d-4988-9a02-ca541d643379
ro. Quota mode: disabled.
[  +0,002201] Emergency Sync complete
--- some long error message here
              Emergency Remount complete

If subsequent o would execute before the u is done, the u would only increase
risk of data loss by making the disk busy right before powerdown and by
exercising the remount code against a concurrent loss of power, which might be
a neglected case due to its rarity.

You will never know whom to blame without hours of debugging. Myself, I would
try
sync ; poweroff -f

-- 
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-09 17:44 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 ` [Bug 219362] " bugzilla-daemon
2024-10-08 12:00 ` 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 [this message]
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-1roYxLE7XJ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.