raid 5 creation fails on usb3 connected drives kernel 4.4.x, 4.5

DISCUSSION Greg KH 4 participants 5 messages Apr 16, 2016 – Apr 17, 2016 11 messages not in the archive SCSI

lore

Share & tools

lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): 5708D6F2.7000608-ncau/[email protected]

Greg KH

author

2016-04-16 16:08 UTC #10 lore raw

Quoted 32 lines · Brian Chadwick

Quoted 31 lines · Greg KH
Quoted 30 lines · Brian Chadwick
Quoted 29 lines · Greg KH
Quoted 28 lines · Brian Chadwick
Quoted 27 lines · Greg KH
Quoted 26 lines · Brian Chadwick
Quoted 25 lines · Greg KH
Quoted 24 lines · Brian Chadwick
SETUP:
i7 16GB Computer.
1 x PCI-x USB3 adaptor card (i think uses xhci-hcd)04:00.0 USB controller:
Renesas Technology Corp. uPD720202 USB 3.0 Host Controller (rev 02)
Kernel driver in use: xhci_hcd
2 x USB3 to dual SATA HDD docks. uses JMicron JMS56x Series controllers, uses uas.ko kernel module
Bus 004 Device 002: ID 152d:9561 JMicron Technology Corp. / JMicron USA Technology Corp.
Bus 004 Device 003: ID 152d:9561 JMicron Technology Corp. / JMicron USA Technology Corp.
3 x Western Digital 320GB 3.5" SATA drives
USE:
RAID 5
KERNEL:
4.3.5

Quoted 7 lines

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
System works perfectly as expected.
Change to kernel 4.4.x or 4.5 and RAID 5 doesnt work. I am not sure whether its actually RAID 5 at fault or if its the USB Attached SCSI driver uas.ko, or maybe the host driver xhci-hcd.
Can you run 'git bisect' to try to track down the offending commit?

Quoted 26 lines

Hi, well to my surprise git bisect has come up with a commit about which I had no inkling. I may have to go to another mailing list it doesnt look like a usb problem.
This is the final output of 'git bisect view' :
commit 64d513ac31bd02a3c9b69ef04444f36c196f9a9d
Author: Christoph Hellwig <[email protected]>
Date:   Thu Oct 8 09:28:04 2015 +0100
scsi: use host wide tags by default
This patch changes the !blk-mq path to the same defaults as the blk-mq I/O path by always enabling block tagging, and always using host wide tags. We've had blk-mq available for a few releases so bugs with this mode should have been ironed out, and this ensures we get better coverage of over tagging setup over different configs.
Signed-off-by Christoph Hellwig <[email protected]>
Acked-by Jens Axboe <axboe-tSWWG44O7X1aa/[email protected]>
Reviewed-by Hannes Reinecke <[email protected]>
Signed-off-by James Bottomley <[email protected]>

Quoted 3 lines

Thank you for your help in narrowing this down, and in educating me about git bisect (its a neat tool) ... I await your advice as how to proceed from here.

Sorry for the delay, nice work tracking down the problem.

Christoph, any ideas? This patch is breaking this user's system as described above. Is there a more recent fix for this, or did something forget to get changed in the large patch you did here?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

James Bottomley

maintainer

2016-04-16 16:25 UTC #11 lore raw

Quoted 92 lines · Greg KH

Quoted 43 lines · Brian Chadwick
Quoted 42 lines · Greg KH
Quoted 41 lines · Brian Chadwick
Quoted 40 lines · Greg KH
Quoted 38 lines · Brian Chadwick
Quoted 37 lines · Greg KH
Quoted 35 lines · Brian Chadwick
Quoted 34 lines · Greg KH
Quoted 32 lines · Brian Chadwick
SETUP:
i7 16GB Computer.
1 x PCI-x USB3 adaptor card (i think uses xhci
-hcd)04:00.0 USB controller:
Renesas Technology Corp. uPD720202 USB 3.0 Host
Controller (rev 02)
Kernel driver in use: xhci_hcd
2 x USB3 to dual SATA HDD docks. uses JMicron JMS56x Series controllers,
uses uas.ko kernel module
Bus 004 Device 002: ID 152d:9561 JMicron Technology Corp. / JMicron USA
Technology Corp.
Bus 004 Device 003: ID 152d:9561 JMicron Technology Corp. / JMicron USA
Technology Corp.
3 x Western Digital 320GB 3.5" SATA drives
USE:
RAID 5
KERNEL:
4.3.5
System works perfectly as expected.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Change to kernel 4.4.x or 4.5 and RAID 5 doesnt
work. I am not sure whether
its actually RAID 5 at fault or if its the USB
Attached SCSI driver uas.ko,
or maybe the host driver xhci-hcd.
Can you run 'git bisect' to try to track down the
offending commit?
<instructions about git-bisect snipped>
Quoted 32 lines
Hi, well to my surprise git bisect has come up with a commit about which I
had no inkling. I may have to go to another mailing list it doesnt look like
a usb problem.
This is the final output of 'git bisect view' :
commit 64d513ac31bd02a3c9b69ef04444f36c196f9a9d
Author: Christoph Hellwig <[email protected]>
Date:   Thu Oct 8 09:28:04 2015 +0100
scsi: use host wide tags by default
This patch changes the !blk-mq path to the same defaults as the
blk-mq
I/O path by always enabling block tagging, and always using
host wide
tags. We've had blk-mq available for a few releases so bugs
with
this mode should have been ironed out, and this ensures we get
better
coverage of over tagging setup over different configs.
Signed-off-by Christoph Hellwig <[email protected]>
Acked-by Jens Axboe <[email protected]>
Reviewed-by Hannes Reinecke <[email protected]>
Signed-off-by James Bottomley <[email protected]>
Quoted 5 lines
Thank you for your help in narrowing this down, and in educating me about
git bisect (its a neat tool) ... I await your advice as how to proceed from
here.

Quoted 6 lines

Sorry for the delay, nice work tracking down the problem.
Christoph, any ideas? This patch is breaking this user's system as described above. Is there a more recent fix for this, or did something
forget to get changed in the large patch you did here?

If this is UAS connected devices, then this is likely the fix:

http://marc.info/?l=linux-scsi&m=146045685829613

James

Greg KH

2016-04-16 16:46 UTC #12 lore raw

Quoted 95 lines · James Bottomley

Quoted 94 lines · Greg KH
Quoted 43 lines · Brian Chadwick
Quoted 42 lines · Greg KH
Quoted 41 lines · Brian Chadwick
Quoted 40 lines · Greg KH
Quoted 38 lines · Brian Chadwick
Quoted 37 lines · Greg KH
Quoted 35 lines · Brian Chadwick
Quoted 34 lines · Greg KH
Quoted 32 lines · Brian Chadwick
SETUP:
i7 16GB Computer.
1 x PCI-x USB3 adaptor card (i think uses xhci
-hcd)04:00.0 USB controller:
Renesas Technology Corp. uPD720202 USB 3.0 Host
Controller (rev 02)
Kernel driver in use: xhci_hcd
2 x USB3 to dual SATA HDD docks. uses JMicron JMS56x Series controllers,
uses uas.ko kernel module
Bus 004 Device 002: ID 152d:9561 JMicron Technology Corp. / JMicron USA
Technology Corp.
Bus 004 Device 003: ID 152d:9561 JMicron Technology Corp. / JMicron USA
Technology Corp.
3 x Western Digital 320GB 3.5" SATA drives
USE:
RAID 5
KERNEL:
4.3.5
System works perfectly as expected.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Change to kernel 4.4.x or 4.5 and RAID 5 doesnt
work. I am not sure whether
its actually RAID 5 at fault or if its the USB
Attached SCSI driver uas.ko,
or maybe the host driver xhci-hcd.
Can you run 'git bisect' to try to track down the
offending commit?
<instructions about git-bisect snipped>
Quoted 32 lines
Hi, well to my surprise git bisect has come up with a commit about which I
had no inkling. I may have to go to another mailing list it doesnt look like
a usb problem.
This is the final output of 'git bisect view' :
commit 64d513ac31bd02a3c9b69ef04444f36c196f9a9d
Author: Christoph Hellwig <[email protected]>
Date:   Thu Oct 8 09:28:04 2015 +0100
scsi: use host wide tags by default
This patch changes the !blk-mq path to the same defaults as the
blk-mq
I/O path by always enabling block tagging, and always using
host wide
tags. We've had blk-mq available for a few releases so bugs
with
this mode should have been ironed out, and this ensures we get
better
coverage of over tagging setup over different configs.
Signed-off-by Christoph Hellwig <[email protected]>
Acked-by Jens Axboe <[email protected]>
Reviewed-by Hannes Reinecke <[email protected]>
Signed-off-by James Bottomley <[email protected]>
Quoted 5 lines
Thank you for your help in narrowing this down, and in educating me about
git bisect (its a neat tool) ... I await your advice as how to proceed from
here.
Sorry for the delay, nice work tracking down the problem.

Quoted 8 lines

Quoted 4 lines
Christoph, any ideas? This patch is breaking this user's system as described above. Is there a more recent fix for this, or did something
forget to get changed in the large patch you did here?
If this is UAS connected devices, then this is likely the fix:
http://marc.info/?l=linux-scsi&m=146045685829613

Ah, nice, it's planned to go to Linus later today...

Brian, can you test that patch out to see if it resolves your issue or not?

thanks,

greg k-h

A message that is not in the archive (sent off-list or not yet received): [email protected]

Brian Chadwick

2016-04-17 04:41 UTC #14 lore raw

Quoted 101 lines · Greg KH

Quoted 93 lines · James Bottomley
Quoted 92 lines · Greg KH
Quoted 43 lines · Brian Chadwick
Quoted 42 lines · Greg KH
Quoted 41 lines · Brian Chadwick
Quoted 40 lines · Greg KH
Quoted 38 lines · Brian Chadwick
Quoted 37 lines · Greg KH
Quoted 35 lines · Brian Chadwick
Quoted 34 lines · Greg KH
Quoted 32 lines · Brian Chadwick
SETUP:
i7 16GB Computer.
1 x PCI-x USB3 adaptor card (i think uses xhci
-hcd)04:00.0 USB controller:
Renesas Technology Corp. uPD720202 USB 3.0 Host
Controller (rev 02)
Kernel driver in use: xhci_hcd
2 x USB3 to dual SATA HDD docks. uses JMicron JMS56x Series controllers,
uses uas.ko kernel module
Bus 004 Device 002: ID 152d:9561 JMicron Technology Corp. / JMicron USA
Technology Corp.
Bus 004 Device 003: ID 152d:9561 JMicron Technology Corp. / JMicron USA
Technology Corp.
3 x Western Digital 320GB 3.5" SATA drives
USE:
RAID 5
KERNEL:
4.3.5
System works perfectly as expected.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Change to kernel 4.4.x or 4.5 and RAID 5 doesnt
work. I am not sure whether
its actually RAID 5 at fault or if its the USB
Attached SCSI driver uas.ko,
or maybe the host driver xhci-hcd.
Can you run 'git bisect' to try to track down the
offending commit?
<instructions about git-bisect snipped>
Quoted 32 lines
Hi, well to my surprise git bisect has come up with a commit about which I
had no inkling. I may have to go to another mailing list it doesnt look like
a usb problem.
This is the final output of 'git bisect view' :
commit 64d513ac31bd02a3c9b69ef04444f36c196f9a9d
Author: Christoph Hellwig<[email protected]>
Date:   Thu Oct 8 09:28:04 2015 +0100
scsi: use host wide tags by default
This patch changes the !blk-mq path to the same defaults as the
blk-mq
I/O path by always enabling block tagging, and always using
host wide
tags. We've had blk-mq available for a few releases so bugs
with
this mode should have been ironed out, and this ensures we get
better
coverage of over tagging setup over different configs.
Signed-off-by Christoph Hellwig<[email protected]>
Acked-by Jens Axboe<axboe-tSWWG44O7X1aa/[email protected]>
Reviewed-by Hannes Reinecke<[email protected]>
Signed-off-by James Bottomley<[email protected]>
Quoted 5 lines
Thank you for your help in narrowing this down, and in educating me about
git bisect (its a neat tool) ... I await your advice as how to proceed from
here.
Sorry for the delay, nice work tracking down the problem.
Quoted 7 lines
Quoted 4 lines
Christoph, any ideas? This patch is breaking this user's system as described above. Is there a more recent fix for this, or did something
forget to get changed in the large patch you did here?
If this is UAS connected devices, then this is likely the fix:
http://marc.info/?l=linux-scsi&m=146045685829613

Quoted 9 lines

Ah, nice, it's planned to go to Linus later today...
Brian, can you test that patch out to see if it resolves your issue or not?
thanks,
greg k-h

Hi Greg, that patch has resolved the issue; I tested in 4.4.7 and 4.5.1. I am not sure how to test in the git tree so I'll just wait for git pull to get the change.

Many thanks to you and any others for your help and education.

Cheers

Brian C.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

Greg KH

2016-04-17 04:56 UTC #15 lore raw

Quoted 107 lines · Brian Chadwick

Quoted 106 lines · Greg KH
Quoted 93 lines · James Bottomley
Quoted 92 lines · Greg KH
Quoted 43 lines · Brian Chadwick
Quoted 42 lines · Greg KH
Quoted 41 lines · Brian Chadwick
Quoted 40 lines · Greg KH
Quoted 38 lines · Brian Chadwick
Quoted 37 lines · Greg KH
Quoted 35 lines · Brian Chadwick
Quoted 34 lines · Greg KH
Quoted 32 lines · Brian Chadwick
SETUP:
i7 16GB Computer.
1 x PCI-x USB3 adaptor card (i think uses xhci
-hcd)04:00.0 USB controller:
Renesas Technology Corp. uPD720202 USB 3.0 Host
Controller (rev 02)
Kernel driver in use: xhci_hcd
2 x USB3 to dual SATA HDD docks. uses JMicron
JMS56x Series controllers,
uses uas.ko kernel module
Bus 004 Device 002: ID 152d:9561 JMicron Technology
Corp. / JMicron USA
Technology Corp.
Bus 004 Device 003: ID 152d:9561 JMicron Technology
Corp. / JMicron USA
Technology Corp.
3 x Western Digital 320GB 3.5" SATA drives
USE:
RAID 5
KERNEL:
4.3.5
System works perfectly as expected.
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 5 lines
Change to kernel 4.4.x or 4.5 and RAID 5 doesnt
work. I am not sure whether
its actually RAID 5 at fault or if its the USB
Attached SCSI driver uas.ko,
or maybe the host driver xhci-hcd.
Can you run 'git bisect' to try to track down the
offending commit?
<instructions about git-bisect snipped>
Quoted 32 lines
Hi, well to my surprise git bisect has come up with a commit about which I
had no inkling. I may have to go to another mailing list it doesnt look like
a usb problem.
This is the final output of 'git bisect view' :
commit 64d513ac31bd02a3c9b69ef04444f36c196f9a9d
Author: Christoph Hellwig<[email protected]>
Date:   Thu Oct 8 09:28:04 2015 +0100
scsi: use host wide tags by default
This patch changes the !blk-mq path to the same defaults as the
blk-mq
I/O path by always enabling block tagging, and always using
host wide
tags. We've had blk-mq available for a few releases so bugs
with
this mode should have been ironed out, and this ensures we get
better
coverage of over tagging setup over different configs.
Signed-off-by Christoph Hellwig<[email protected]>
Acked-by Jens Axboe<[email protected]>
Reviewed-by Hannes Reinecke<[email protected]>
Signed-off-by James Bottomley<[email protected]>
Quoted 5 lines
Thank you for your help in narrowing this down, and in educating me about
git bisect (its a neat tool) ... I await your advice as how to proceed from
here.
Sorry for the delay, nice work tracking down the problem.
Quoted 7 lines
Quoted 4 lines
Christoph, any ideas? This patch is breaking this user's system as described above. Is there a more recent fix for this, or did something
forget to get changed in the large patch you did here?
If this is UAS connected devices, then this is likely the fix:
http://marc.info/?l=linux-scsi&m=146045685829613
Ah, nice, it's planned to go to Linus later today...
Brian, can you test that patch out to see if it resolves your issue or not?

Quoted 7 lines

Quoted 4 lines
thanks,
greg k-h
Hi Greg, that patch has resolved the issue; I tested in 4.4.7 and 4.5.1. I am not sure how to test in the git tree so I'll just wait for git pull to get the change.

This patch is in Linus's tree now and I'll suck it into the next release of the 4.4 and 4.5-stable trees soon.

thanks for testing and letting me know it works,

greg k-h