public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 214327] New: Cant't shutdown or reboot: loop messages "ext4_writepages: jbd2_start: err -30"
Date: Mon, 06 Sep 2021 08:25:39 +0000	[thread overview]
Message-ID: <bug-214327-13602@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 214327
           Summary: Cant't shutdown or reboot: loop messages
                    "ext4_writepages: jbd2_start: err -30"
           Product: File System
           Version: 2.5
    Kernel Version: 5.14.1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: antdev66@gmail.com
        Regression: No

Created attachment 298677
  --> https://bugzilla.kernel.org/attachment.cgi?id=298677&action=edit
reboot/shutdown phase

Hello,
I have my workflow on Debian/Sid, with kernel compiled by
https://www.kernel.org/, currently at version 5.14.1, on asus x555ln notebook.

The problem occurs when the external USB 3 harddisk is disconnected from
itself: in some cases it is no longer reconnected and if I try to do "sync"
from console, this command appears freezed.

If I reboot, at the end the system log shows that it has reached the
"Rebooting" phase but remains in loops on the message indicated above (see
image file).

When this happens, the system should recognize that the harddisk is no longer
available or stalled, to interrupt the write of the cache and terminate the
reboot or shutdown phase.

Thanks,
Antonio


-- DETAILS --

dmesg:

scsi host4: uas
scsi 4:0:0:0: Direct-Access     ASMT     2115             0    PQ: 0 ANSI: 6
sd 4:0:0:0: Attached scsi generic sg0 type 0
sd 4:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Mode Sense: 43 00 00 00
sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
DPO or FUA
sd 4:0:0:0: [sda] Optimal transfer size 33553920 bytes
 sda: sda1
sd 4:0:0:0: [sda] Attached SCSI disk
usb 3-1: USB disconnect, device number 8
xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or
ep state.
sd 4:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN 
sd 4:0:0:0: [sda] tag#28 CDB: Read(10) 28 00 00 00 01 08 00 00 f8 00

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

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

                 reply	other threads:[~2021-09-06  8:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-214327-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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