On Fri, 2015-04-03 at 15:19 +0100, Ruediger Meier wrote: > Hi, > > eject(1) fails for scsi_debug module version 1.85 (kernel 3.19). > > The Problem is that command ALLOW_MEDIUM_REMOVAL now returns > driverstatus==DRIVER_SENSE with sensecode==0x20 (INVALID COMMAND > OPERATION CODE). > > If I ignore that senscode then the other two START_STOP commands finish > successfully. > > Should this be fixed in eject(1) or in scsi_debug or is it just a bad > idea to eject scsi_debug devices? This documentations says > ALLOW_MEDIUM_REMOVAL is supported. > http://sg.danny.cz/sg/sdebug.html > > I guess the issue came with this kernel commit: Then the kernel needs fixing. Breaking userspace is a no no, plain and simple. Who knows what other program(s) might be affected. Thanks, Davidlohr -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
