doug-gilbert

The output from the various sg3-utils is designed to be _human_ readable first and foremost. My thinking was if you wanted to machine parse it that you would dump the...

Advice: to have the least number of side effects in the Linux SCSI pass-through use either /dev/sg* or /dev/bsg* device. IOW unhelpful things can happen when you use a block...

Try adding the --long option to the sg_format command line. Also an extra verbose option (i.e. '-vv') would help looking at the failed output. It is possible that IBM have...

I think that it is important that you run 'sg_readcap PD1' on that disk. It could be 4096+n byte sector size. I have been told that IBM allow 5xx byte...

IBM's HPSS might be using the Linux sg driver, or possibly the bsg driver. They bypass the st driver. I'm adding st driver like statistics (similar place, same names (e.g....

Yes, that would be fine. The sysfs attributes have the same names as st. The interpretation of "read" and "write" is a bit different: for sg "read" is data-in (i.e....

The --verbose (-v) can be given multiple times. Each time increases the level of verbosity. Try -vvv in this case and respond if it doesn't give you the data buffer...

This was also reported in my account: https://github.com/doug-gilbert/sg3_utils/issues/40 and has been fixed there.

I did know about github releases. So I just issued one over at https://github.com/doug-gilbert/sg3_utils/releases . It is a cut and paste from Announce post that I sent to the linux-scsi...

No. A subversion server running on a RPi in my basement is the primary repo! Long before I had a github account the owner of this account offered to set...