3ware RAID selinux smartd

Kevin H. Hobbs hobbsk at ohiou.edu
Wed Mar 14 13:46:43 UTC 2007

On Tue, 2007-03-13 at 15:24 -0400, Daniel J Walsh wrote:
> > Against what should the bug be filed, udev?
> >
> >   
> udev,

I just filed a bug against udev for the /dev/twa* devices. The URL is :


The contents of that bug are :

The character devices, /dev/twa* are needed by smartd in order to
monitor the disks attached to 3ware 9000 series controllers. We have a
3ware Inc 9550SX SATA-RAID controller and the device /dev/twa0 does not
exist on boot. A udev rule should exist to create these devices on boot.
That udev rule should set the security context fixed_disk_device_t on
the created devices or smartd will not be able to open them.

We are currently using udev-095-17.fc6, kernel-2.6.19-1.2911.6.5.fc6,
and smartmontools-5.36-3.2.fc6.

I currently have the 3ware monitor daemon 3DM2 installed. It creates the
devices. Once the devices exist, I am able to use smartctl to access the
disks. smartd is not able to access the disks because they do not have
the correct context. When I manually set the context of /dev/twa* to
have fixed_disk_device_t smartd is able to monitor the devices.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20070314/23248329/attachment-0002.bin 

More information about the users mailing list