16 Nov, 2011

1 commit

  • A long time ago, probably in 2002, one of the distros, or maybe more than
    one, loaded block drivers prior to loading the SCSI mid layer. This meant
    that the cciss driver, being a block driver, could not engage the SCSI mid
    layer at init time without panicking, and relied on being poked by a
    userland program after the system was up (and the SCSI mid layer was
    therefore present) to engage the SCSI mid layer.

    This is no longer the case, and cciss can safely rely on the SCSI mid
    layer being present at init time and engage the SCSI mid layer straight
    away. This means that users will see their tape drives and medium
    changers at driver load time without need for a script in /etc/rc.d that
    does this:

    for x in /proc/driver/cciss/cciss*
    do
    echo "engage scsi" > $x
    done

    However, if no tape drives or medium changers are detected, the SCSI mid
    layer will not be engaged. If a tape drive or medium change is later
    hot-added to the system it will then be necessary to use the above script
    or similar for the device(s) to be acceesible.

    Signed-off-by: Stephen M. Cameron
    Signed-off-by: Andrew Morton
    Signed-off-by: Jens Axboe

    Stephen M. Cameron
     

08 Aug, 2011

1 commit


06 May, 2011

1 commit

  • This is to allow number of commands reserved for use by SCSI tape drives
    and medium changers to be adjusted at driver load time via the kernel
    parameter cciss_tape_cmds, with a default value of 6, and a range
    of 2 - 16 inclusive. Previously, the driver limited the number of
    commands which could be queued to the SCSI half of the the driver
    to only 2. This is to fix the problem that if you had more than
    two tape drives, you couldn't, for example, erase or rewind them all
    at the same time.

    Signed-off-by: Stephen M. Cameron
    Signed-off-by: Jens Axboe

    Stephen M. Cameron
     

15 Nov, 2008

1 commit