lsscsi-0.17 released
lsscsi is a utility that uses sysfs in linux 2.6 series kernels to list information about SCSI devices and SCSI hosts. Both a compact format (default) which is one line per device and a "classic" format (like the output of 'cat /proc/scsi/scsi') are supported.
Version 0.17 is available at
http://www.torque.net/scsi/lsscsi.html
More information can be found on that page including examples and a Download section for tarballs and rpms.
This version will be required for lsscsi to work properly when lk 2.6.16 is released.
ChangeLog:
Version 0.17 2006/2/6
- fix disappearance of block device names in lk 2.6.16-rc1
Doug Gilbert
Quoted 10 lines · Douglas Gilbert
Version 0.17 is available at
http://www.torque.net/scsi/lsscsi.html
More information can be found on that page including examples and a Download section for tarballs and rpms.
This version will be required for lsscsi to work properly when lk 2.6.16 is released.ChangeLog:
Version 0.17 2006/2/6
- fix disappearance of block device names in lk 2.6.16-rc1
Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
Signature · 1 line
Matthias Andree
Quoted 10 lines · Matthias Andree
Quoted 6 lines · Douglas Gilbert
This version will be required for lsscsi to work properly when lk 2.6.16 is released.
ChangeLog:
Version 0.17 2006/2/6
- fix disappearance of block device names in lk 2.6.16-rc1Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
The former. In lk 2.6.16-rc1 the /sys/class/scsi_device/<hcil>/device/block symlink changed to ".../block:sd<x>" breaking lsscsi 0.16 (and earlier) and sg_map26 (in sg3_utils).
Doug Gilbert
Quoted 9 lines · Douglas Gilbert
Quoted 2 lines · Matthias Andree
Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
The former. In lk 2.6.16-rc1 the /sys/class/scsi_device/<hcil>/device/block symlink changed to ".../block:sd<x>" breaking lsscsi 0.16 (and earlier) and
sg_map26(insg3_utils).
Heck, what was the reason for breaking userspace again?
Why would someone even consider using sysfs at all if it changes incompatibly?
Signature · 1 line
Matthias Andree
Quoted 11 lines · Matthias Andree
Quoted 8 lines · Douglas Gilbert
Quoted 2 lines · Matthias Andree
Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
The former. In lk 2.6.16-rc1 the /sys/class/scsi_device/<hcil>/device/block symlink changed to ".../block:sd<x>" breaking lsscsi 0.16 (and earlier) and
sg_map26(insg3_utils).Heck, what was the reason for breaking userspace again?
Maybe the person responsible can answer. I'm only reacting to a change that broke two of my utilities.
Quoted 2 lines
Why would someone even consider using sysfs at all if it changes incompatibly?
Indeed.
Doug Gilbert
Quoted 11 lines · Douglas Gilbert
Quoted 10 lines · Matthias Andree
Quoted 8 lines · Douglas Gilbert
Quoted 2 lines · Matthias Andree
Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
The former. In lk 2.6.16-rc1 the /sys/class/scsi_device/<hcil>/device/block symlink changed to ".../block:sd<x>" breaking lsscsi 0.16 (and earlier) and
sg_map26(insg3_utils).
Quoted 4 lines
Quoted 1 line
Heck, what was the reason for breaking userspace again?
Maybe the person responsible can answer. I'm only reacting to a change that broke two of my utilities.
Probably better to cc the person responsible if you want an answer.
Quoted 4 lines
Quoted 2 lines
Why would someone even consider using sysfs at all if it changes incompatibly?
Indeed.
There seems to be no committment to making sysfs a stable part of the kernel API. Which is really just another way of saying "we can't be bothered to design it upfront, we'll just let it evolve into a mess and then try to fix it afterwards".
Quoted 22 lines · Matthew Wilcox
Quoted 11 lines · Douglas Gilbert
Quoted 10 lines · Matthias Andree
Quoted 8 lines · Douglas Gilbert
Quoted 2 lines · Matthias Andree
Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
The former. In lk 2.6.16-rc1 the /sys/class/scsi_device/<hcil>/device/block symlink changed to ".../block:sd<x>" breaking lsscsi 0.16 (and earlier) and
sg_map26(insg3_utils).Quoted 4 lines
Quoted 1 line
Heck, what was the reason for breaking userspace again?
Maybe the person responsible can answer. I'm only reacting to a change that broke two of my utilities.
Probably better to cc the person responsible if you want an answer.
Quoted 3 lines
Quoted 2 lines
Why would someone even consider using sysfs at all if it changes incompatibly?
Quoted 6 lines
Quoted 1 line
Indeed.
There seems to be no committment to making sysfs a stable part of the kernel API. Which is really just another way of saying "we can't be bothered to design it upfront, we'll just let it evolve into a mess and then try to fix it afterwards".
I sorta hate to say this, but I was sitting/working a few feet from Pat Mochel about 4 years ago when he was beginning on sysfs, and I told him to watch out, it could end up a mess just like procfs... :(
Signature · 1 line
~Randy
Quoted 12 lines · Matthew Wilcox
Quoted 11 lines · Douglas Gilbert
Quoted 10 lines · Matthias Andree
Quoted 8 lines · Douglas Gilbert
Quoted 2 lines · Matthias Andree
Does this work around new incompatibilities in the kernel or does this fix lsscsi bugs?
The former. In lk 2.6.16-rc1 the /sys/class/scsi_device/<hcil>/device/block symlink changed to ".../block:sd<x>" breaking lsscsi 0.16 (and earlier) and
sg_map26(insg3_utils).
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
Heck, what was the reason for breaking userspace again?
Maybe the person responsible can answer. I'm only reacting to a change that broke two of my utilities.
Probably better to cc the person responsible if you want an answer.
It was changed as there would be more than one "block" symlink in a device's directory if more than one block device was attached to a single struct device. For example, ub and multi-lun devices (there were other reports of this happening for scsi devices too at the time from what I remember.)
So, in that case, your tool would have been broken anyway, so this fix was required to make it correct :)
The fix was to make block devices work the same way as all other class devices, which had this fix a while ago.
thanks,
greg k-h
Quoted 5 lines · Greg KH
It was changed as there would be more than one "block" symlink in a device's directory if more than one block device was attached to a single struct device. For example, ub and multi-lun devices (there were other reports of this happening for scsi devices too at the time from what I remember.)
OK, just post an announcement to l-k when sysfs has stabilized enough to be worth bothering.
Signature · 1 line
Matthias Andree
Quoted 10 lines · Matthias Andree
Quoted 5 lines · Greg KH
It was changed as there would be more than one "block" symlink in a device's directory if more than one block device was attached to a single struct device. For example, ub and multi-lun devices (there were other reports of this happening for scsi devices too at the time from what I remember.)
OK, just post an announcement to l-k when sysfs has stabilized enough to be worth bothering.
Um, this was a "bugfix". The kernel was creating multiple symlinks with the same name, in the same directory, pointing to different locations. How do you expect us to fix that in a format that does not change the name of the symlink?
People sure are grumpy this morning...
greg k-h
Quoted 6 lines · Greg KH
Quoted 2 lines · Matthias Andree
OK, just post an announcement to l-k when sysfs has stabilized enough to be worth bothering.
Um, this was a "bugfix".
Granted.
Quoted 6 lines
The kernel was creating multiple symlinks with
the same name, in the same directory, pointing to different locations. How do you expect us to fix that in a format that does not change the name of the symlink?People sure are grumpy this morning...
If you say so. I'd call it pure pragmatism: if the sysfs interface still changes every other week or so, it's just annoying to chase these changes in applications, so it seems just practical to wait until all the bug fixes that require interface changes are in and the rate of incompatible changes is well below 2/year -- and all the interesting stuff is there.
Signature · 1 line
Matthias Andree