Re: kernels v2.6.x vs. /dev/nst0 ???

* Michael D Schleif <mds AT helices DOT org> [2004:03:07:23:10:40-0600] scribed:
<snip />
> Unfortunately, this is my amanda backup server, and under this kernel it
> no longer communicates with /dev/nst0:
> 
>    # sudo mt -f /dev/nst0 offline
>    mt: No such device. Cannot open '/dev/nst0'.
> 
> Everything else appears to work as expected.  I didn't notice this tape
> problem until this morning, I saw the backup was stuck on holdingdisk.
> 
> Running following results in `0' tape devices found:
> 
>    # sudo /etc/init.d/mt-st modload
> 
> Regardless of kernel, I see this:
> 
>    # cat /proc/scsi/scsi
>    Attached devices:
>    Host: scsi0 Channel: 00 Id: 05 Lun: 00
>      Vendor: HP       Model: C1537A           Rev: L812
>      Type:   Sequential-Access                ANSI SCSI revision: 02
>    . . .
> 
> Now, after reboot back into 2.4.25, /dev/nst0 is working fine, and I am
> flushing last night's backup to tape as I compose this.
<snip />


* "Stefan G. Weichinger" <monitor AT oops.co DOT at> [2004:03:08:10:12:46+0100] 
scribed:
> Hi, Michael,
> 
> on Montag, 08. März 2004 at 06:10 you wrote to amanda-users:
> 
> MDS> Amanda 2.4.4p1
> MDS> Debian Linux
> 
> MDS> I finally took the plunge yesterday, and upgraded my last system to
> MDS> kernel 2.6.3.
> 
> MDS> What do you think?
> 
> Just for the records:
> 
> I compiled and ran various versions and snapshots of AMANDA on all
> Linux-kernels since 2.5.79 on my testbox. No problems.
> 
> Right now I have 2.6.4-rc2 up, with AMANDA 2.4.5b1 on it, running
> fine.
> 
> As Frank said, it is likely that you miss a module.
> How did you configure 2.6.3? A good start would be to take the config
> of your 2.4.25, "make oldconfig" and start testing with this.

I am using the stock Debian kernel:

   kernel-image-2.6.3-1-686

From config-2.6.3-1-686:

   #
   # SCSI device support
   #
   CONFIG_SCSI=m
   CONFIG_SCSI_PROC_FS=y

   #
   # SCSI support type (disk, tape, CD-ROM)
   #
   CONFIG_BLK_DEV_SD=m
   CONFIG_CHR_DEV_ST=m
   CONFIG_CHR_DEV_OSST=m
   CONFIG_BLK_DEV_SR=m
   # CONFIG_BLK_DEV_SR_VENDOR is not set
   CONFIG_CHR_DEV_SG=m

   #
   # Some SCSI devices (e.g. CD jukebox) support multiple LUNs
   #
   CONFIG_SCSI_MULTI_LUN=y
   # CONFIG_SCSI_REPORT_LUNS is not set
   CONFIG_SCSI_CONSTANTS=y
   CONFIG_SCSI_LOGGING=y


From config-2.4.25-1-686:

   #
   # SCSI support type (disk, tape, CD-ROM)
   #
   CONFIG_BLK_DEV_SD=m
   CONFIG_SD_EXTRA_DEVS=40
   CONFIG_CHR_DEV_ST=m
   CONFIG_CHR_DEV_OSST=m
   CONFIG_BLK_DEV_SR=m
   # CONFIG_BLK_DEV_SR_VENDOR is not set
   CONFIG_SR_EXTRA_DEVS=2
   CONFIG_CHR_DEV_SCH=m
   CONFIG_CHR_DEV_SG=m

   #
   # Some SCSI devices (e.g. CD jukebox) support multiple LUNs
   #
   # CONFIG_SCSI_DEBUG_QUEUES is not set
   CONFIG_SCSI_MULTI_LUN=y
   CONFIG_SCSI_CONSTANTS=y
   CONFIG_SCSI_LOGGING=y

What am I missing?

> After that you can still try to add/remove features from you kernel.
> 
> Can you access your 2.6.3-tape-device via mt or create archives on it
> with tar?

That's the point, I cannot (see above).

-- 
Best Regards,

mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know.  The more I know, the more I know I don't know . . .
--
signature.asc
Description: Digital signature