On Sat, Mar 06, 2021 at 06:27:06PM +0100, Aaron Dewes wrote: > > > On Sat, Mar 06, 2021 at 05:34:32PM +0100, Aaron Dewes wrote: > > > Hello! > > > > > > Sorry if this suggestion/question sounds stupid, I don't have experience > > > with the kernel code and this mailing list. > > > > > > I'm a contributor to Umbrel (getumbrel.com), and we provide a software > > > that allows to run a bitcoin node easily, and we've run into many people > > > having UAS issues > > What specific UAS issues? And why not just fix those instead? > > Sorry, I should've been more specific. When I said UAS issues, I meant > that we've had many users who used drives that were incompatible with > UAS, and that script is our way to detect that and fix it, because the > kernel apparently often doesn't detect that, and I think that way would > be a way to actually automatically detect such issues. The kernel _does_ autodetect drives that don't claim to support uas. Are you saying that your users have drives which claim to support uas but don't actually support it? If that's so, can you tell us what drives they are so we can put this information into the kernel? And can you tell us what errors the users encounter? Also, how can you be sure that the drives don't support uas at all, as opposed to supporting uas in general but not a few specific commands? > Currently, drivers/usb/storage/unusual_devs.h disables UAS for a few > devices, but autodetecting would be better in my opinion. Autodetecting the way you want wouldn't really work very well. It would require the user to plug in the drive and initiate some actiity on it which would generate a flurry of errors, so that the kernel could see that it should try usb-storage instead. Then the user would have to unplug the drive and plug it in a second time so that usb-storage could manage it. Alan Stern
