From: "David C. Partridge" <david.partridge@perdrix.co.uk>
To: "'Oliver Neukum'" <oneukum@suse.com>, <linux-usb@vger.kernel.org>
Subject: RE: Issues with LaCie USB3 drive and UAS
Date: Mon, 9 Nov 2020 09:51:29 -0000 [thread overview]
Message-ID: <001601d6b67d$e97a1e30$bc6e5a90$@perdrix.co.uk> (raw)
In-Reply-To: <eceedea7ca5d950eb8ea4d186a6b01a04d0a804f.camel@suse.com>
I'm sure you are right in your diagnosis (absent any knowledge to the contrary).
Now what's the treatment?
Would uas black-list provide a work-araound? If so a detailed recipe will be needed by me ...
Fix to the code? Ideal, but takes lots longer, so a work-around may be needed for a while
David
-----Original Message-----
From: Oliver Neukum [mailto:oneukum@suse.com]
Sent: 09 November 2020 09:30
To: David C. Partridge; linux-usb@vger.kernel.org
Subject: Re: Issues with LaCie USB3 drive and UAS
Am Sonntag, den 08.11.2020, 10:56 +0000 schrieb David C. Partridge:
> 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
Write Same? What you are seeing is that the error handling is running
non-stop. I suspect that the device does not understand WRITE SAME.
Regards
Oliver
next prev parent reply other threads:[~2020-11-09 9:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-08 10:56 Issues with LaCie USB3 drive and UAS David C. Partridge
2020-11-09 9:29 ` Oliver Neukum
2020-11-09 9:51 ` David C. Partridge [this message]
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='001601d6b67d$e97a1e30$bc6e5a90$@perdrix.co.uk' \
--to=david.partridge@perdrix.co.uk \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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).