Hi Michael, * Michael Tokarev <[email protected]> [230619 13:00]: > Having said this, I'm not really sure who's in charge here. > Maybe it is the kernel driver who should split the large request into smaller > parts. > > But the end result is that whole thing stops working (and some devices even > fall > off the usb bus and needs to be re-set). And for quite some times I was sure > discard/trim is not supported on USB-connected devices at all, just because > this > quick blkdiscard test always fails like this, - and I thought it is the > command > which is illegal, not its parameter.
I'm not sure what you're asking. Is this a bug? A feature request? blkdiscard is a "low level tool" and I think it works according to its documentation. A less low-level tool is fstrim, that might do what you want? If you want blkdiscard to be smarter - if the smartness shouldn't be in the kernel in the first place - can you suggest this to upstream? Doesn't seem like this is a Debian-specific thing? Thanks, Chris
