From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: <linux-usb@vger.kernel.org>
Subject: Issues with LaCie USB3 drive and UAS
Date: Sun, 8 Nov 2020 10:56:36 -0000 [thread overview]
Message-ID: <004f01d6b5bd$d4f08ff0$7ed1afd0$@perdrix.co.uk> (raw)
LUbuntu 20.04.1
root@charon:/home/amonra# lsusb
Bus 002 Device 006: ID 059f:105f LaCie, Ltd 2Big Quadra USB3
Trying to format the above drive using mkfs.ext4 /dev/sdc2
Initially got a 120s Kernel timeout which I resolved by setting the timeout
to 0
However I got LOTS of message groups in the system log looking like this:
Nov 04 06:18:51 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 uas_zap_pending 0
uas-tag 1 inflight:
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Write Same(10)
41 00 e8 ea 47 fc 00 00 04 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 uas_zap_pending 0
uas-tag 2 inflight:
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 CDB: Write Same(10)
41 00 e8 e6 48 00 00 ff ff 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 uas_zap_pending 0
uas-tag 3 inflight:
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 CDB: Write Same(10)
41 00 e8 e9 47 fd 00 ff ff 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 uas_zap_pending 0
uas-tag 4 inflight:
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 CDB: Write Same(10)
41 00 e8 e8 47 fe 00 ff ff 00
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 uas_zap_pending 0
uas-tag 5 inflight:
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 CDB: Write Same(10)
41 00 e8 e7 47 ff 00 ff ff 00
Nov 04 06:18:51 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 6 using xhci_hcd
Nov 04 06:18:51 charon kernel: scsi host5: uas_eh_device_reset_handler
success
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#0 CDB: Write Same(10)
41 00 e8 ea 47 fc 00 00 04 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907667964 op 0x9:(WRITE_ZEROES) flags 0x1000800 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#1 CDB: Write Same(10)
41 00 e8 e6 48 00 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907405824 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#2 CDB: Write Same(10)
41 00 e8 e9 47 fd 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907602429 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#3 CDB: Write Same(10)
41 00 e8 e8 47 fe 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907536894 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 FAILED Result:
hostbyte=DID_RESET driverbyte=DRIVER_OK
Nov 04 06:18:51 charon kernel: sd 5:0:0:0: [sdc] tag#4 CDB: Write Same(10)
41 00 e8 e7 47 ff 00 ff ff 00
Nov 04 06:18:51 charon kernel: blk_update_request: I/O error, dev sdc,
sector 3907471359 op 0x9:(WRITE_ZEROES) flags 0x1000000 phys_seg 0 prio
class 0
and while the command apparently ended cleanly it took a *very long* time
(hours)
root@charon:/home/amonra# mkfs.ext4 /dev/sdc2
mke2fs 1.45.5 (07-Jan-2020)
Creating filesystem with 976701696 4k blocks and 244178944 inodes
Filesystem UUID: f45b0cd6-131a-4a3a-988f-c5a848611445
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544
Allocating group tables: done
Writing inode tables: done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: done
root@charon:/home/amonra# fsck /dev/sdc2
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sdc2: clean, 11/244178944 files, 15615751/976701696 blocks
root@charon:/home/amonra#
I'm not 100% convinced it did ...
If I just attach and mount the drive I get:
Nov 08 10:25:40 charon kernel: EXT4-fs (sdc2): recovery complete
Nov 08 10:25:40 charon kernel: EXT4-fs (sdc2): mounted filesystem with
ordered data mode. Opts: (null)
Nov 08 10:26:12 charon kernel: sd 5:0:0:0: [sdc] tag#17 uas_eh_abort_handler
0 uas-tag 1 inflight: OUT
Nov 08 10:26:12 charon kernel: sd 5:0:0:0: [sdc] tag#17 CDB: Write Same(10)
41 00 00 06 b7 98 00 10 00 00
Nov 08 10:26:12 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 08 10:26:12 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Nov 08 10:26:12 charon kernel: scsi host5: uas_eh_device_reset_handler
success
I then see a lot of message groups like this in the log:
Nov 08 10:31:21 charon kernel: INFO: task jbd2/sdc2-8:104742 blocked for
more than 241 seconds.
Nov 08 10:31:21 charon kernel: Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:31:21 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:31:21 charon kernel: jbd2/sdc2-8 D 0 104742 2
0x80004000
Nov 08 10:31:21 charon kernel: Call Trace:
Nov 08 10:31:21 charon kernel: __schedule+0x2e3/0x740
Nov 08 10:31:21 charon kernel: schedule+0x42/0xb0
Nov 08 10:31:21 charon kernel: jbd2_journal_commit_transaction+0x258/0x17e8
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:31:21 charon kernel: ? wait_woken+0x80/0x80
Nov 08 10:31:21 charon kernel: ? try_to_del_timer_sync+0x54/0x80
Nov 08 10:31:21 charon kernel: kjournald2+0xb6/0x280
Nov 08 10:31:21 charon kernel: ? wait_woken+0x80/0x80
Nov 08 10:31:21 charon kernel: kthread+0x104/0x140
Nov 08 10:31:21 charon kernel: ? commit_timeout+0x20/0x20
Nov 08 10:31:21 charon kernel: ? kthread_park+0x90/0x90
Nov 08 10:31:21 charon kernel: ret_from_fork+0x35/0x40
Nov 08 10:31:21 charon kernel: INFO: task ext4lazyinit:104744 blocked for
more than 241 seconds.
Nov 08 10:31:21 charon kernel: Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:31:21 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:31:21 charon kernel: ext4lazyinit D 0 104744 2
0x80004000
Nov 08 10:31:21 charon kernel: Call Trace:
Nov 08 10:31:21 charon kernel: __schedule+0x2e3/0x740
Nov 08 10:31:21 charon kernel: schedule+0x42/0xb0
Nov 08 10:31:21 charon kernel: schedule_timeout+0x10e/0x160
Nov 08 10:31:21 charon kernel: io_schedule_timeout+0x1e/0x50
Nov 08 10:31:21 charon kernel: wait_for_completion_io+0xb1/0x120
Nov 08 10:31:21 charon kernel: ? wake_up_q+0x70/0x70
Nov 08 10:31:21 charon kernel: submit_bio_wait+0x60/0x90
Nov 08 10:31:21 charon kernel: blkdev_issue_zeroout+0x13f/0x220
Nov 08 10:31:21 charon kernel: ext4_init_inode_table+0x195/0x386
Nov 08 10:31:21 charon kernel: ext4_lazyinit_thread+0x2c7/0x3b0
Nov 08 10:31:21 charon kernel: kthread+0x104/0x140
Nov 08 10:31:21 charon kernel: ? ext4_unregister_li_request+0x70/0x70
Nov 08 10:31:21 charon kernel: ? kthread_park+0x90/0x90
Nov 08 10:31:21 charon kernel: ret_from_fork+0x35/0x40
Nov 08 10:32:14 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 08 10:32:14 charon kernel: sd 5:0:0:0: [sdc] tag#9 uas_zap_pending 0
uas-tag 1 inflight:
Nov 08 10:32:14 charon kernel: sd 5:0:0:0: [sdc] tag#9 CDB: Write Same(10)
41 00 00 06 b7 98 00 10 00 00
Nov 08 10:32:14 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Nov 08 10:32:14 charon kernel: scsi host5: uas_eh_device_reset_handler
success
Nov 08 10:32:28 charon systemd[1]: Started Run anacron jobs.
Nov 08 10:32:28 charon anacron[107039]: Anacron 2.3 started on 2020-11-08
Nov 08 10:32:28 charon anacron[107039]: Normal exit (0 jobs run)
Nov 08 10:32:28 charon systemd[1]: anacron.service: Succeeded.
Nov 08 10:33:22 charon kernel: INFO: task jbd2/sdc2-8:104742 blocked for
more than 362 seconds.
Nov 08 10:33:22 charon kernel: Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:33:22 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:33:22 charon kernel: jbd2/sdc2-8 D 0 104742 2
0x80004000
Nov 08 10:33:22 charon kernel: Call Trace:
Nov 08 10:33:22 charon kernel: __schedule+0x2e3/0x740
Nov 08 10:33:22 charon kernel: schedule+0x42/0xb0
Nov 08 10:33:22 charon kernel: jbd2_journal_commit_transaction+0x258/0x17e8
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x40/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel: ? __switch_to_asm+0x34/0x70
Nov 08 10:33:22 charon kernel: ? wait_woken+0x80/0x80
Nov 08 10:33:22 charon kernel: ? try_to_del_timer_sync+0x54/0x80
Nov 08 10:33:22 charon kernel: kjournald2+0xb6/0x280
Nov 08 10:33:22 charon kernel: ? wait_woken+0x80/0x80
Nov 08 10:33:22 charon kernel: kthread+0x104/0x140
Nov 08 10:33:22 charon kernel: ? commit_timeout+0x20/0x20
Nov 08 10:33:22 charon kernel: ? kthread_park+0x90/0x90
Nov 08 10:33:22 charon kernel: ret_from_fork+0x35/0x40
Nov 08 10:33:22 charon kernel: INFO: task ext4lazyinit:104744 blocked for
more than 362 seconds.
Nov 08 10:33:22 charon kernel: Not tainted 5.4.0-52-generic #57-Ubuntu
Nov 08 10:33:22 charon kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Nov 08 10:33:22 charon kernel: ext4lazyinit D 0 104744 2
0x80004000
Nov 08 10:33:22 charon kernel: Call Trace:
Nov 08 10:33:22 charon kernel: __schedule+0x2e3/0x740
Nov 08 10:33:22 charon kernel: schedule+0x42/0xb0
Nov 08 10:33:22 charon kernel: schedule_timeout+0x10e/0x160
Nov 08 10:33:22 charon kernel: io_schedule_timeout+0x1e/0x50
Nov 08 10:33:22 charon kernel: wait_for_completion_io+0xb1/0x120
Nov 08 10:33:22 charon kernel: ? wake_up_q+0x70/0x70
Nov 08 10:33:22 charon kernel: submit_bio_wait+0x60/0x90
Nov 08 10:33:22 charon kernel: blkdev_issue_zeroout+0x13f/0x220
Nov 08 10:33:22 charon kernel: ext4_init_inode_table+0x195/0x386
Nov 08 10:33:22 charon kernel: ext4_lazyinit_thread+0x2c7/0x3b0
Nov 08 10:33:22 charon kernel: kthread+0x104/0x140
Nov 08 10:33:22 charon kernel: ? ext4_unregister_li_request+0x70/0x70
Nov 08 10:33:22 charon kernel: ? kthread_park+0x90/0x90
Nov 08 10:33:22 charon kernel: ret_from_fork+0x35/0x40
Nov 08 10:34:15 charon kernel: scsi host5: uas_eh_device_reset_handler start
Nov 08 10:34:15 charon kernel: sd 5:0:0:0: [sdc] tag#1 uas_zap_pending 0
uas-tag 1 inflight:
Nov 08 10:34:15 charon kernel: sd 5:0:0:0: [sdc] tag#1 CDB: Write Same(10)
41 00 00 06 b7 98 00 10 00 00
Nov 08 10:34:15 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device
number 2 using xhci_hcd
Nov 08 10:34:15 charon kernel: scsi host5: uas_eh_device_reset_handler
success
Any guidance and help much appreciated.
David
next reply other threads:[~2020-11-08 11:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 10:56 David C. Partridge [this message]
2020-11-09 9:29 ` Issues with LaCie USB3 drive and UAS Oliver Neukum
2020-11-09 9:51 ` David C. Partridge
2020-11-09 10:13 ` Oliver Neukum
2020-11-09 11:21 ` David C. Partridge
2020-11-09 15:21 ` David C. Partridge
2020-11-09 16:47 ` David C. Partridge
2020-11-11 11:43 ` Oliver Neukum
2020-11-11 15:50 ` David C. Partridge
2020-11-11 19:18 ` Oliver Neukum
2020-11-11 20:54 ` David C. Partridge
2020-11-23 14:59 ` Oliver Neukum
2020-11-25 12:25 ` David C. Partridge
2020-11-26 8:24 ` Oliver Neukum
2020-11-26 9:33 ` David C. Partridge
2020-11-26 10:22 ` Oliver Neukum
[not found] ` <0000 01d6c89c$086812e0$193838a0$@perdrix.co.uk>
2020-12-02 11:12 ` David C. Partridge
[not found] ` <612be9a9cd6ffdb9492781e174859c7b4e69 4a86.camel@suse.com>
2020-12-02 11:38 ` Oliver Neukum
2020-12-02 13:39 ` David C. Partridge
2020-12-03 2:11 ` David C. Partridge
2020-12-03 13:16 ` Oliver Neukum
2020-12-03 14:30 ` David C. Partridge
2020-12-07 10:53 ` David C. Partridge
2020-12-08 14:03 ` Oliver Neukum
2020-12-08 16:06 ` David C. Partridge
2020-12-08 16:27 ` Alan Stern
2020-12-08 16:47 ` David C. Partridge
2020-12-08 17:45 ` 'Alan Stern'
2020-12-08 20:00 ` David C. Partridge
2020-12-09 11:11 ` Oliver Neukum
2020-12-03 14:06 ` Oliver Neukum
2020-12-03 14:46 ` David C. Partridge
2020-12-03 16:16 ` 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='004f01d6b5bd$d4f08ff0$7ed1afd0$@perdrix.co.uk' \
--to=david.partridge@perdrix.co.uk \
--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).