Andrey Borzenkov <[EMAIL PROTECTED]> writes:
> Anyone knows about it? Reading devfs it appears that just a single drive is
> suppoted (devfsd expects /dev/cciss/{disc,partN}) while driver apparently
> supports more than one (8 if I am not wrong).
static entries format is cciss/c<CONTROLLER_ID>d<DISK_ID>p<PART_ID>
> But in kernel sources for 2.4.21-0.25mdk there is no trace of cciss
> driver ever creating ANY devfs entry at all.
i once had an access to such a machine.
i can only tell you that devfsd recreate the same devices nodes as old
static ones.
i think we now had one of these pets in qa labs.
> The question came from Andrew Morton re. devfs support for block devices in
> 2.6. For all I can tell the correct structure should be at least
>
> /dev/cciss/hostN/targetM... for controller N; may be full bus and lun are
> overhead, but I do not know this hardware so cannot decide. In any case
> current devfsd patch looks bogus.
if i remember correcly, current driver works smoothly with cciss
driver.
i do not remember what is the exact naming scheme, but it should be
something like /dev/cciss/<FORGOT_DIR_NAME>/{disk,partX)
so there *should* be no problems.
