Bug 489982

(In reply to comment #0)
> BTW, I see special-case for cciss in upstream HAL:
> http://cgit.freedesktop.org/hal/tree/hald/linux/blockdev.c#n942
> Don't we need to backport this?  

Yes.

[root@hp-dl380g5-01 mj]# rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}\n' hal
hal-0.5.8.1-49.el5.x86_64
hal-0.5.8.1-49.el5.i386
[root@hp-dl380g5-01 mj]# service haldaemon restartStopping HAL daemon: [  OK  ]
Starting HAL daemon: [  OK  ]
[root@hp-dl380g5-01 mj]# hal-find-by-capability --capability storage

- rebooted box

[root@hp-dl380g5-01 ~]# hal-find-by-capability --capability storage
[root@hp-dl380g5-01 ~]#

Investigating whether upstream scsi-misc commit id below will resolve hal issue for cciss.

7fe063268e73681cdca1a6496a25f93d3332f517

Adding Mike Miller to bugzilla.  I believe Mike maintains the cciss driver.

The patch I generated from the upstream commit 7fe063268e73681cdca1a6496a25f93d3332f517 did not apply cleanly to rhel5.4.

A backport will be required.

Adding Ron Pacheco to the bugzilla.

Coping email from Mike Miller:

This patch should resolve the missing links in sysfs:
 
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=404443081ce5e6f68b5f7eda16c959835ff200c0
 
Sorry for any duplicates.
 
-- mikem

Applying the patch does result in /sys/block/cciss!cXdY/device/* being created.

The hal command gives the same number of devices on this host both before and after the patch is applied so it looks like the problem is not completely resolved by the patch in comment 21.

I'm not sure I understand comment 22. Why would the number of devices change?

In comment 12, the hal command was run and no devices showed up.  The host that I was experimenting on has devices and adapters besides cciss.  I would have expected to see other devices after the driver update if I understand the hal command correctly.

So the cciss devices still didn't show up after the patch? Sorry to ask so many questions, but I know nothing about hal. Does hal need modification to find cciss devices?

Richard,

Please update this bugzilla with your findings on dl585-03 and answer Mike Miller's question in comment 28.

Thanks, Rob

Mike, the device also needs the cciss bus_type assigned, so the subsystem becomes cciss, and it also shows up in /sys/bus/cciss/devices/. This is why HAL cannot add the device. The bus type should have been added in the kernel driver backport -- See http://patchwork.kernel.org/patch/26781/ for the description. 

When /sys/bus/cciss is created there should be needed a 4 line trivial patch to hal to recognise the cciss bus, and label it correctly.

Created attachment 354572 [details]
Patch to add /sys/bus/cciss/.... attribute

This patch adds new sysfs attributes for cciss including bus. The other patches mentioned rework the scan thread.

This BZ will be used for the change to hal that is required to special-case cciss. 

I have cloned this BZ to allow for the corresponding kernel change that is needed to make the cciss driver provide the necessary information in sysfs. The kernel BZ is 513070.

Richard,

The patch is applied and dl585-03 is booted w/ the updated driver loaded.

[root@dl585-03 devices]# ls /sys/bus/cciss/
devices/       drivers/       drivers_probe

Rob

Comment on attachment 354572 [details]
Patch to add /sys/bus/cciss/.... attribute

See 2nd attachment to bz513070, where this patch is slightly modified to remove a previous commit

I've applied the trivial patch to hal and scratch built it here: http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1902446

With this build installed (and the fixed kernel build), the cciss bus is recognised, and the storage devices populated.

[root@dl585-03 packages]# hal-find-by-capability --capability storage
/org/freedesktop/Hal/devices/storage_serial_35000c5000020d907
/org/freedesktop/Hal/devices/storage_serial_35000c5000020d933
/org/freedesktop/Hal/devices/storage_serial_3600508b400105e210000900000490000_0
/org/freedesktop/Hal/devices/storage_serial_3600508b400105e210000900000490000
/org/freedesktop/Hal/devices/storage_serial_3600601601040190000c7da47f286dc11_0
/org/freedesktop/Hal/devices/storage_serial_36006016010401900be062253f286dc11_0
/org/freedesktop/Hal/devices/storage_serial_360060160104019008e275c5af286dc11_0
/org/freedesktop/Hal/devices/storage_serial_360060160104019000ad1c4510660dd11_0
/org/freedesktop/Hal/devices/storage_serial_3600601601040190002e7ff73e23bdd11_0
/org/freedesktop/Hal/devices/storage_serial_3600601601040190000c7da47f286dc11
/org/freedesktop/Hal/devices/storage_serial_36006016010401900be062253f286dc11
/org/freedesktop/Hal/devices/storage_serial_360060160104019008e275c5af286dc11
/org/freedesktop/Hal/devices/storage_serial_360060160104019000ad1c4510660dd11
/org/freedesktop/Hal/devices/storage_serial_3600601601040190002e7ff73e23bdd11
/org/freedesktop/Hal/devices/storage_model_TSSTcorpCD_ROM_TS_L162C
/org/freedesktop/Hal/devices/platform_floppy_0_storage

Built as hal-0_5_8_1-51_el5 in http://brewweb.devel.redhat.com/brew/taskinfo?taskID=1902492

Note for QA people: you need the fixed kernel in https://bugzilla.redhat.com/show_bug.cgi?id=513070 before this will work. Not having the fixed kernel means that the new code is not used, and so is harmless.

ok so it looks good cciss device is shown among other when listing by storage capability

Alan, Subhendu: any idea how to test together with RHEV? I do not know where should this device be shown/used .. I can create img on mounted cciss partition but I probably meant to install it directly to cciss partition..

(In reply to comment #45)
> ok so it looks good cciss device is shown among other when listing by storage
> capability
> 
> Alan, Subhendu: any idea how to test together with RHEV? I do not know where
> should this device be shown/used .. I can create img on mounted cciss partition
> but I probably meant to install it directly to cciss partition..  

We are doing a RHEVH build tomorrow and will tag the newer hal package to get picked up in that build.  Then we can have RHEVH qe team (llim) do the RHEVH verification steps if that is acceptable to you.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1359.html