blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?

All of lore.kernel.org
 help / color / mirror / Atom feed

* blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
@ 2002-09-05 19:35 ` Friedrich Lobenstock
  2002-09-05 20:02     ` Dag Nygren
                     ` (2 more replies)
  0 siblings, 3 replies; 11+ messages in thread
From: Friedrich Lobenstock @ 2002-09-05 19:35 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste; +Cc: Linux-Kernel Mailingliste

Hi!

I'm having an odd problem here. I use SuSE Linux 8.0 with kernel
2.4.18-64GB-SMP, arkeia as backup software and a Tandberg
VS80 (DLT1) streamer.

After some trial and error I found out that I have to use a fixed block
size for DLT streamers (same applies to LTO ones). This document,
found at HP, tells you in details about which blocksize to use:
   http://www.hp.com/cposupport/information_storage/support_doc/lpg50167.html

Now I told arkeia to use a blocksize of 65536, 32768 and 16384 and it
could not write to the tape. All I got in the log was:

Sep  4 22:04:50 filesrv kernel: st: Unloaded.
Sep  4 22:08:40 filesrv kernel: st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16
Sep  4 22:08:40 filesrv kernel: st0: Block limits 2 - 16777214 bytes.
Sep  4 22:08:41 filesrv kernel: st0: Incorrect block size.
Sep  4 22:08:45 filesrv kernel: st0: Write not multiple of tape block size.

Sep  4 23:20:06 filesrv kernel: st: Unloaded.
Sep  4 23:20:30 filesrv kernel: st: Version 20020205, bufsize 524288, wrt 522240, max init. bufs 16, s/g segs 64
Sep  4 23:20:30 filesrv kernel: st0: Block limits 2 - 16777214 bytes.
Sep  4 23:20:33 filesrv kernel: st0: Incorrect block size.
Sep  4 23:20:35 filesrv kernel: st0: Write not multiple of tape block size.

(As you might have notice in the second case I'm loading st with buffer_kbs=512,
max_buffers=16 and max_sg_segs=64 but that makes no difference compared to the
default values)

BUT now comes the cloo: at and below a blocksize of 8192 it was possible
to write to the tape. At 1024 the backup slowed down from 20 min to 4 hours,
but at 8192 the backup speed is normal (the later on with the st options
you can see above, but haven't tested if that makes a difference).

LTO drives in contrast to DLT drives are happy with a blocksize of 1024
and backup speed is normal at this blocksize.

Everytime when arkeia could not write to the tape I checked with mt to
display the blocksize and I verified that arkeia set it to the value I
told it to. Now with arkeia set to a blocksize of 8192:

filesrv:~ # mt -f /dev/st0 status
drive type = Generic SCSI-2 tape
drive status = 1073750016
sense key error = 0
residue count = 0
file number = 0
block number = 0
Tape block size 8192 bytes. Density code 0x40 (unknown).
Soft error count since last status=0
General status bits on (41010000):
  BOT ONLINE IM_REP_EN

I think there must be something wrong in the scsi tape driver(st).
Can someone shine some light on this?

PS: Reply-to set to linux-scsi.

-- 
MfG / Regards
Friedrich Lobenstock

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 19:35 ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Friedrich Lobenstock
@ 2002-09-05 20:02     ` Dag Nygren
  2002-09-05 20:14   ` 2.5.xx kernels won't run on my Athlon boxes Kirk Reiser
  2002-09-05 21:19   ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Kai Makisara
  2 siblings, 0 replies; 11+ messages in thread
From: Dag Nygren @ 2002-09-05 20:02 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste; +Cc: Linux-Kernel Mailingliste, dag

Hi,

I have successfully been using Legato Networker with a
blocksize of 32k with my DLT here.

But the way Legato wants to do it is to decide about the
blocksize itself.
This means that the driver should NOT decide on the BS, but
pass on anything written through it, meaning a blocksize setting
of 0 (or variable blocksize).

Perhaps Arkeia works the same way ?

Best Luck

-- 
Dag Nygren                               email: dag@newtech.fi
Oy Espoon NewTech Ab                     phone: +358 9 8024910
Träsktorpet 3                              fax: +358 9 8024916
02360 ESBO                              Mobile: +358 400 426312
FINLAND

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with  DLT1 tape drives?
@ 2002-09-05 20:02     ` Dag Nygren
  0 siblings, 0 replies; 11+ messages in thread
From: Dag Nygren @ 2002-09-05 20:02 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste; +Cc: Linux-Kernel Mailingliste, dag

Hi,

I have successfully been using Legato Networker with a
blocksize of 32k with my DLT here.

But the way Legato wants to do it is to decide about the
blocksize itself.
This means that the driver should NOT decide on the BS, but
pass on anything written through it, meaning a blocksize setting
of 0 (or variable blocksize).

Perhaps Arkeia works the same way ?

Best Luck

-- 
Dag Nygren                               email: dag@newtech.fi
Oy Espoon NewTech Ab                     phone: +358 9 8024910
Träsktorpet 3                              fax: +358 9 8024916
02360 ESBO                              Mobile: +358 400 426312
FINLAND

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 20:02     ` Dag Nygren
  (?)
@ 2002-09-05 20:59     ` Friedrich Lobenstock
  2002-09-05 21:28       ` Kai Makisara
                         ` (2 more replies)
  -1 siblings, 3 replies; 11+ messages in thread
From: Friedrich Lobenstock @ 2002-09-05 20:59 UTC (permalink / raw)
  To: Dag Nygren; +Cc: Linux-SCSI Mailingliste, Linux-Kernel Mailingliste

Dag Nygren wrote:
> I have successfully been using Legato Networker with a
> blocksize of 32k with my DLT here.
> 
> But the way Legato wants to do it is to decide about the
> blocksize itself.
> This means that the driver should NOT decide on the BS, but
> pass on anything written through it, meaning a blocksize setting
> of 0 (or variable blocksize).
> 
> Perhaps Arkeia works the same way ?

I used variable blocksize (=0) before but then after about 3.5 gigs stored
on the tape I get scsi-error and arkeia interprets this as end-of-tape.

Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info fld=0x2000, Deferred st09:00: sns = f1  3
Aug  6 02:13:50 filesrv kernel: ASC=80 ASCQ= 1
Aug  6 02:13:50 filesrv kernel: Raw sense data:0xf1 0x00 0x03 0x00 0x00 0x20 0x00 0x16 0x00 0x00 0xe6 0xc2 0x80 0x01 0x00 0x00 0x00 0x00 0x83 0x00 0x37 0x00 0x00 0x00 0x21 0x00 0x90 0x7f 0x3a 0x00
Aug  6 02:13:50 filesrv kernel: klogd 1.4.1, ---------- state change ----------
Aug  6 02:13:50 filesrv kernel: Inspecting /boot/System.map-2.4.18-64GB-SMP
Aug  6 02:13:50 filesrv kernel: Loaded 13537 symbols from /boot/System.map-2.4.18-64GB-SMP.
Aug  6 02:13:50 filesrv kernel: Symbols match kernel version 2.4.18.
Aug  6 02:13:50 filesrv kernel: Loaded 481 symbols from 13 modules.
Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info fld=0x1, Current st09:00: sns = f0  3
Aug  6 02:13:50 filesrv kernel: ASC= c ASCQ= 0
Aug  6 02:13:50 filesrv kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x16 0x00 0x00 0xe6 0xc2 0x0c 0x00 0x00 0x00 0x00 0x00 0x83 0x00 0x37 0x00 0x00 0x00 0x21 0x00 0x90 0x7f 0x3a 0x00

I had this problem with LTO drives too and here the arkeia faq tells one
to set fixed block size.

And when you look a the HP document referenced in my last mail:

    ISSUE: Block sizes of LESS THAN 64 KB for DLT1/DLT VS80 and 32 KB for
           all other DAT and DLT drives can drastically increase the backup/restore
           time and severely affect the performance of the drive.

SOLUTION: Most backup applications allow viewing and adjusting the block
           size used for a particular device. See below for advice on how
           to achieve this for CA ARCserve, Veritas Backup Exec and Tapeware.

(I capitalized "less than" to emphasis its occurance)

I you missed the link here it is again:
   http://www.hp.com/cposupport/information_storage/support_doc/lpg50167.html

Did you check with mt after Legato Networker did a backup which blocksize
it set?

-- 
MfG / Regards
Friedrich Lobenstock

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 20:59     ` Friedrich Lobenstock
@ 2002-09-05 21:28       ` Kai Makisara
  2002-09-05 22:07       ` Dag Nygren
  2002-09-06  0:15       ` jw schultz
  2 siblings, 0 replies; 11+ messages in thread
From: Kai Makisara @ 2002-09-05 21:28 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste

On Thu, 5 Sep 2002, Friedrich Lobenstock wrote:

> Dag Nygren wrote:
> > I have successfully been using Legato Networker with a
> > blocksize of 32k with my DLT here.
> >
> > But the way Legato wants to do it is to decide about the
> > blocksize itself.
> > This means that the driver should NOT decide on the BS, but
> > pass on anything written through it, meaning a blocksize setting
> > of 0 (or variable blocksize).
> >
> > Perhaps Arkeia works the same way ?
>
> I used variable blocksize (=0) before but then after about 3.5 gigs stored
> on the tape I get scsi-error and arkeia interprets this as end-of-tape.
>
> Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info fld=0x2000, Deferred st09:00: sns = f1  3
> Aug  6 02:13:50 filesrv kernel: ASC=80 ASCQ= 1

The sense code 3 is MEDIUM ERROR. The ASC/ASCQ 80 01 is vendor specific.
In other words, you have bad tape (or the drive thinks that it is bad).
This is returned as an error in writing data to tape. Most applications
(hopefully) interpret this as end of tape.

	Kai



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 20:59     ` Friedrich Lobenstock
  2002-09-05 21:28       ` Kai Makisara
@ 2002-09-05 22:07       ` Dag Nygren
  2002-09-06  0:15       ` jw schultz
  2 siblings, 0 replies; 11+ messages in thread
From: Dag Nygren @ 2002-09-05 22:07 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste; +Cc: dag

> Dag Nygren wrote:

> I used variable blocksize (=0) before but then after about 3.5 gigs stored
> on the tape I get scsi-error and arkeia interprets this as end-of-tape.
> 
> Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info fld=0x2000, Deferred st09:00: sns = f1  3
> Aug  6 02:13:50 filesrv kernel: ASC=80 ASCQ= 1
> Aug  6 02:13:50 filesrv kernel: Raw sense data:0xf1 0x00 0x03 0x00 0x00 0x20 0x00 0x16 0x00 0x00 0xe6 0xc2 0x80 0x01 0x00 0x00 0x00 0x00 0x83 0x00 0x37 0x00 0x00 0x00 0x21 0x00 0x90 0x7f 0x3a 0x00
> Aug  6 02:13:50 filesrv kernel: klogd 1.4.1, ---------- state change ----------
> Aug  6 02:13:50 filesrv kernel: Inspecting /boot/System.map-2.4.18-64GB-SMP
> Aug  6 02:13:50 filesrv kernel: Loaded 13537 symbols from /boot/System.map-2.4.18-64GB-SMP.
> Aug  6 02:13:50 filesrv kernel: Symbols match kernel version 2.4.18.
> Aug  6 02:13:50 filesrv kernel: Loaded 481 symbols from 13 modules.
> Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info fld=0x1, Current st09:00: sns = f0  3
> Aug  6 02:13:50 filesrv kernel: ASC= c ASCQ= 0
> Aug  6 02:13:50 filesrv kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 0x00 0x01 0x16 0x00 0x00 0xe6 0xc2 0x0c 0x00 0x00 0x00 0x00 0x00 0x83 0x00 0x37 0x00 0x00 0x00 0x21 0x00 0x90 0x7f 0x3a 0x00

Have you checked what this sense data indicates ?
Do you have the SCSI manual for your DLT ?
Sense Key 0x03 and Additional Sense Key=0xe6

Sense key= 0x03 means MEDIUM_ERROR
ASK=0xe6 is Vendor Specific but could tell you more about the 
medium error

> I had this problem with LTO drives too and here the arkeia faq tells one
> to set fixed block size.

This sounds very strange........

> And when you look a the HP document referenced in my last mail:
> 
>     ISSUE: Block sizes of LESS THAN 64 KB for DLT1/DLT VS80 and 32 KB for
>            all other DAT and DLT drives can drastically increase the backup/restore
>            time and severely affect the performance of the drive.
> 
> SOLUTION: Most backup applications allow viewing and adjusting the block
>            size used for a particular device. See below for advice on how
>            to achieve this for CA ARCserve, Veritas Backup Exec and Tapeware.

And they are certainly right on that, I recently made a study on blocksizes in
Linux-tapes for a customer and the performance was significantly better up to
16 k blocks, after this the perf. increase was in the regions of 2-3 %.

> 
> (I capitalized "less than" to emphasis its occurance)
> 
> I you missed the link here it is again:
>    http://www.hp.com/cposupport/information_storage/support_doc/lpg50167.html
> 
> Did you check with mt after Legato Networker did a backup which blocksize
> it set?

It will not be set to anything else than 0. Using 0 just tells the driver that
it shall write all the data given in ONE write() call to the driver in one 
block
to the device. Thus the application (in this case Legato) can determine which
size of blocks to use.
When using fixed blocks, the driver will split the write into that big chunks 
and
write those onto the tape one by one.

> 
> -- 
> MfG / Regards
> Friedrich Lobenstock
> 
> 



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 20:59     ` Friedrich Lobenstock
  2002-09-05 21:28       ` Kai Makisara
  2002-09-05 22:07       ` Dag Nygren
@ 2002-09-06  0:15       ` jw schultz
  2 siblings, 0 replies; 11+ messages in thread
From: jw schultz @ 2002-09-06  0:15 UTC (permalink / raw)
  To: Linux-Kernel Mailingliste

On Thu, Sep 05, 2002 at 10:59:51PM +0200, Friedrich Lobenstock wrote:
> Dag Nygren wrote:
> >I have successfully been using Legato Networker with a
> >blocksize of 32k with my DLT here.
> >
> >But the way Legato wants to do it is to decide about the
> >blocksize itself.
> >This means that the driver should NOT decide on the BS, but
> >pass on anything written through it, meaning a blocksize setting
> >of 0 (or variable blocksize).
> >
> >Perhaps Arkeia works the same way ?
> 
> I used variable blocksize (=0) before but then after about 3.5 gigs stored
> on the tape I get scsi-error and arkeia interprets this as end-of-tape.
> 
> Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info 
> fld=0x2000, Deferred st09:00: sns = f1  3
> Aug  6 02:13:50 filesrv kernel: ASC=80 ASCQ= 1
> Aug  6 02:13:50 filesrv kernel: Raw sense data:0xf1 0x00 0x03 0x00 0x00 
> 0x20 0x00 0x16 0x00 0x00 0xe6 0xc2 0x80 0x01 0x00 0x00 0x00 0x00 0x83 0x00 
> 0x37 0x00 0x00 0x00 0x21 0x00 0x90 0x7f 0x3a 0x00
> Aug  6 02:13:50 filesrv kernel: klogd 1.4.1, ---------- state change 
> ----------
> Aug  6 02:13:50 filesrv kernel: Inspecting /boot/System.map-2.4.18-64GB-SMP
> Aug  6 02:13:50 filesrv kernel: Loaded 13537 symbols from 
> /boot/System.map-2.4.18-64GB-SMP.
> Aug  6 02:13:50 filesrv kernel: Symbols match kernel version 2.4.18.
> Aug  6 02:13:50 filesrv kernel: Loaded 481 symbols from 13 modules.
> Aug  6 02:13:50 filesrv kernel: st0: Error with sense data: Info fld=0x1, 
> Current st09:00: sns = f0  3
> Aug  6 02:13:50 filesrv kernel: ASC= c ASCQ= 0
> Aug  6 02:13:50 filesrv kernel: Raw sense data:0xf0 0x00 0x03 0x00 0x00 
> 0x00 0x01 0x16 0x00 0x00 0xe6 0xc2 0x0c 0x00 0x00 0x00 0x00 0x00 0x83 0x00 
> 0x37 0x00 0x00 0x00 0x21 0x00 0x90 0x7f 0x3a 0x00
> 
> I had this problem with LTO drives too and here the arkeia faq tells one
> to set fixed block size.
> 
> And when you look a the HP document referenced in my last mail:
> 
>    ISSUE: Block sizes of LESS THAN 64 KB for DLT1/DLT VS80 and 32 KB for
>           all other DAT and DLT drives can drastically increase the 
>           backup/restore
>           time and severely affect the performance of the drive.
> 
> SOLUTION: Most backup applications allow viewing and adjusting the block
>           size used for a particular device. See below for advice on how
>           to achieve this for CA ARCserve, Veritas Backup Exec and Tapeware.
> 
> (I capitalized "less than" to emphasis its occurance)
> 
> I you missed the link here it is again:
>   http://www.hp.com/cposupport/information_storage/support_doc/lpg50167.html
> 
> Did you check with mt after Legato Networker did a backup which blocksize
> it set?

Generally one sets the device block size (driver) to variable
and instructs the backup software to use a largish
block size.  The two are somewhat independent.

HP is right about small block sizes at the app level.
Writing small blocks not only ruins performance but the
latencies mean the tape drive has to do lots of
repositioning which stresses the tape and the drive.

I don't do tape drive firmware but the following is my best
understanding of the situation.  What you tell the
application regarding block size determines the amount of
overhead for headers and the size of the buffer used for
write(2).  Using a large block size at the application level
usually helps performance thereby enabling it to better keep
up with the tape drive.

On the device level each block is terminated by a
end-of-block marker and there is a space (blank tape)
between it and the next block to allow for positioning.  If
you set fixed size blocks it may have to reposition (stop,
rewind, play looking for header) between blocks.  Small
blocks mean wasted tape (reduced capacity) and wear-and-tear
on the drive and media.  As you can imagine repositioning
means reduced throughput.  Having a fixed device block size that
differs from the application block size can cause problems
especially if their relationship is subject to hysteresis.

Using variable block size allows the drive to stream as long
as you can keep up with it.  If you fall behind (buffer
underrun) it will put an end of block and space.  This is
independent of the application block size.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

^ permalink raw reply	[flat|nested] 11+ messages in thread

* 2.5.xx kernels won't run on my Athlon boxes
  2002-09-05 19:35 ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Friedrich Lobenstock
  2002-09-05 20:02     ` Dag Nygren
@ 2002-09-05 20:14   ` Kirk Reiser
  2002-09-05 21:19   ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Kai Makisara
  2 siblings, 0 replies; 11+ messages in thread
From: Kirk Reiser @ 2002-09-05 20:14 UTC (permalink / raw)
  To: Linux-Kernel Mailingliste

Hi Folks:  I'm not even sure where to start outlining this problem.  I
have two Athlon 2100+ xp systems using Epoch EP8K3A mother boards.  I
don't seem to be able to get any 2.5.xx kernels to run on them for
more than a few minutes.  I have tried compiling kernels without
specifying K7 or K6 I've tried with and without the via chip set
options.  The boxes have the via 82C586 chip set.

The 2.4.19 kernels seem to be a bit more stable on them than the
2.5.xx are.  If anyone has any ideas what I can check I'd certainly
appreciate it.  I'll include my .config and output from dmesg below.


  Kirk

Sep  5 14:51:55 itchy kernel: Linux version 2.5.33 (kirk@itchy) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Thu Sep 5 14:41:01 EDT 2002
Sep  5 14:51:55 itchy kernel: Video mode to be used for restore is f01
Sep  5 14:51:55 itchy kernel: BIOS-provided physical RAM map:
Sep  5 14:51:55 itchy kernel:  BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Sep  5 14:51:55 itchy kernel:  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Sep  5 14:51:55 itchy kernel:  BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
Sep  5 14:51:55 itchy kernel:  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Sep  5 14:51:55 itchy kernel: 512MB LOWMEM available.
Sep  5 14:51:55 itchy kernel: On node 0 totalpages: 131072
Sep  5 14:51:55 itchy kernel: zone(0): 4096 pages.
Sep  5 14:51:55 itchy kernel: zone(1): 126976 pages.
Sep  5 14:51:55 itchy kernel: zone(2): 0 pages.
Sep  5 14:51:55 itchy kernel: Kernel command line: BOOT_IMAGE=old ro root=301
Sep  5 14:51:55 itchy kernel: Initializing CPU#0
Sep  5 14:51:55 itchy kernel: Detected 1737.649 MHz processor.
Sep  5 14:51:55 itchy kernel: Console: colour VGA+ 80x50
Sep  5 14:51:55 itchy kernel: Calibrating delay loop... 3424.25 BogoMIPS
Sep  5 14:51:55 itchy kernel: Memory: 516872k/524288k available (1081k kernel code, 7032k reserved, 368k data, 228k init, 0k highmem)
Sep  5 14:51:55 itchy kernel: Security Scaffold v1.0.0 initialized
Sep  5 14:51:55 itchy kernel: Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  5 14:51:55 itchy kernel: Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Sep  5 14:51:55 itchy kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Sep  5 14:51:55 itchy kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Sep  5 14:51:55 itchy kernel: CPU: L2 Cache: 256K (64 bytes/line)
Sep  5 14:51:55 itchy kernel: Intel machine check architecture supported.
Sep  5 14:51:55 itchy kernel: Intel machine check reporting enabled on CPU#0.
Sep  5 14:51:55 itchy kernel: Machine check exception polling timer started.
Sep  5 14:51:55 itchy kernel: CPU: AMD Athlon(tm) XP 2100+ stepping 02
Sep  5 14:51:55 itchy kernel: Enabling fast FPU save and restore... done.
Sep  5 14:51:55 itchy kernel: Enabling unmasked SIMD FPU exception support... done.
Sep  5 14:51:55 itchy kernel: Checking 'hlt' instruction... OK.
Sep  5 14:51:55 itchy kernel: POSIX conformance testing by UNIFIX
Sep  5 14:51:55 itchy kernel: Linux NET4.0 for Linux 2.4
Sep  5 14:51:55 itchy kernel: Based upon Swansea University Computer Society NET3.039
Sep  5 14:51:55 itchy kernel: Initializing RT netlink socket
Sep  5 14:51:55 itchy kernel: PCI: PCI BIOS revision 2.10 entry at 0xfb490, last bus=1
Sep  5 14:51:55 itchy kernel: PCI: Using configuration type 1
Sep  5 14:51:55 itchy kernel: PCI: Probing PCI hardware
Sep  5 14:51:55 itchy kernel: PCI: Probing PCI hardware (bus 00)
Sep  5 14:51:55 itchy kernel: PCI: Using IRQ router default [1106/3099] at 00:00.0
Sep  5 14:51:55 itchy kernel: Starting kswapd
Sep  5 14:51:55 itchy kernel: BIO: pool of 256 setup, 14Kb (56 bytes/bio)
Sep  5 14:51:55 itchy kernel: biovec: init pool 0, 1 entries, 12 bytes
Sep  5 14:51:55 itchy kernel: biovec: init pool 1, 4 entries, 48 bytes
Sep  5 14:51:55 itchy kernel: biovec: init pool 2, 16 entries, 192 bytes
Sep  5 14:51:55 itchy kernel: biovec: init pool 3, 64 entries, 768 bytes
Sep  5 14:51:55 itchy kernel: biovec: init pool 4, 128 entries, 1536 bytes
Sep  5 14:51:55 itchy kernel: biovec: init pool 5, 256 entries, 3072 bytes
Sep  5 14:51:55 itchy kernel: aio_setup: sizeof(struct page) = 40
Sep  5 14:51:55 itchy kernel: Journalled Block Device driver loaded
Sep  5 14:51:55 itchy kernel: Capability LSM initialized
Sep  5 14:51:55 itchy kernel: block: 256 slots per queue, batch=32
Sep  5 14:51:55 itchy kernel: Floppy drive(s): fd0 is 1.44M
Sep  5 14:51:55 itchy kernel: FDC 0 is a post-1991 82077
Sep  5 14:51:55 itchy kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
Sep  5 14:51:55 itchy kernel: 00:09.0: 3Com PCI 3c905C Tornado at 0xd000. Vers LK1.1.18
Sep  5 14:51:55 itchy kernel: phy=0, phyx=24, mii_status=0x782d
Sep  5 14:51:55 itchy kernel: Uniform Multi-Platform E-IDE driver Revision: 6.31
Sep  5 14:51:55 itchy kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Sep  5 14:51:55 itchy kernel: VP_IDE: IDE controller on PCI bus 00 dev 89
Sep  5 14:51:55 itchy kernel: PCI: No IRQ known for interrupt pin A of device 00:11.1. Please try using pci=biosirq.
Sep  5 14:51:55 itchy kernel: VP_IDE: chipset revision 6
Sep  5 14:51:55 itchy kernel: VP_IDE: not 100%% native mode: will probe irqs later
Sep  5 14:51:55 itchy kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Sep  5 14:51:55 itchy kernel: VP_IDE: VIA vt8233a (rev 00) IDE UDMA133 controller on pci00:11.1
Sep  5 14:51:55 itchy kernel:     ide0: BM-DMA at 0xd400-0xd407, BIOS settings: hda:DMA, hdb:pio
Sep  5 14:51:55 itchy kernel:     ide1: BM-DMA at 0xd408-0xd40f, BIOS settings: hdc:DMA, hdd:pio
Sep  5 14:51:55 itchy kernel: hda: MAXTOR 6L080J4, ATA DISK drive
Sep  5 14:51:55 itchy kernel: blk: queue c02cb0e4, I/O limit 4095Mb (mask 0xffffffff)
Sep  5 14:51:55 itchy kernel: hdc: HL-DT-ST GCE-8320B, ATAPI CD/DVD-ROM drive
Sep  5 14:51:55 itchy kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Sep  5 14:51:55 itchy kernel: ide1 at 0x170-0x177,0x376 on irq 15
Sep  5 14:51:55 itchy kernel: hda: host protected area => 1
Sep  5 14:51:55 itchy kernel: hda: 156355584 sectors (80054 MB) w/1819KiB Cache, CHS=9732/255/63, UDMA(133)
Sep  5 14:51:55 itchy kernel:  hda: hda1 hda2 hda3 hda4
Sep  5 14:51:55 itchy kernel: hdc: ATAPI 40X CD-ROM CD-R/RW drive, 8192kB Cache, DMA
Sep  5 14:51:55 itchy kernel: Uniform CD-ROM driver Revision: 3.12
Sep  5 14:51:55 itchy kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Sep  5 14:51:55 itchy kernel: input: AT Set 2 keyboard on isa0060/serio0
Sep  5 14:51:55 itchy kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Sep  5 14:51:55 itchy kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Sep  5 14:51:55 itchy kernel: IP Protocols: ICMP, UDP, TCP, IGMP
Sep  5 14:51:55 itchy kernel: IP: routing cache hash table of 4096 buckets, 32Kbytes
Sep  5 14:51:55 itchy kernel: TCP: Hash tables configured (established 131072 bind 65536)
Sep  5 14:51:55 itchy kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Sep  5 14:51:55 itchy kernel: kjournald starting.  Commit interval 5 seconds
Sep  5 14:51:55 itchy kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep  5 14:51:55 itchy kernel: VFS: Mounted root (ext3 filesystem) readonly.
Sep  5 14:51:55 itchy kernel: Freeing unused kernel memory: 228k freed
Sep  5 14:51:55 itchy kernel: Adding 634556k swap on /dev/hda2.  Priority:-1 extents:1
Sep  5 14:51:55 itchy kernel: EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,1), internal journal
Sep  5 14:51:55 itchy kernel: kjournald starting.  Commit interval 5 seconds
Sep  5 14:51:55 itchy kernel: EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,3), internal journal
Sep  5 14:51:55 itchy kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep  5 14:51:55 itchy kernel: kjournald starting.  Commit interval 5 seconds
Sep  5 14:51:55 itchy kernel: EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,4), internal journal
Sep  5 14:51:55 itchy kernel: EXT3-fs: mounted filesystem with ordered data mode.

-- 

Kirk Reiser				The Computer Braille Facility
e-mail: kirk@braille.uwo.ca		University of Western Ontario
phone: (519) 661-3061



#
# Automatically generated by make menuconfig: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
# CONFIG_EXPERIMENTAL is not set

#
# General setup
#
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
CONFIG_MK7=y
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_USE_3DNOW=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_SMP is not set
# CONFIG_PREEMPT is not set
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_UP_IOAPIC is not set
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_X86_MCE_P4THERMAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
# CONFIG_MTRR is not set

#
# Power management options (ACPI, APM)
#

#
# ACPI Support
#
# CONFIG_ACPI is not set
# CONFIG_PM is not set
# CONFIG_APM is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_NAMES=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
# CONFIG_PCMCIA is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play configuration
#
CONFIG_PNP=y
# CONFIG_ISAPNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_CISS_SCSI_TAPE is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set

#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y

#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDEDISK_VENDOR is not set
# CONFIG_BLK_DEV_IDEDISK_FUJITSU is not set
# CONFIG_BLK_DEV_IDEDISK_IBM is not set
# CONFIG_BLK_DEV_IDEDISK_MAXTOR is not set
# CONFIG_BLK_DEV_IDEDISK_QUANTUM is not set
# CONFIG_BLK_DEV_IDEDISK_SEAGATE is not set
# CONFIG_BLK_DEV_IDEDISK_WD is not set
# CONFIG_BLK_DEV_COMMERIAL is not set
# CONFIG_BLK_DEV_TIVO is not set
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_BLK_DEV_CMD640=y
# CONFIG_BLK_DEV_CMD640_ENHANCED is not set
# CONFIG_BLK_DEV_ISAPNP is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_IDEDMA_TIMEOUT is not set
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_AEC62XX_TUNING is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_WDC_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_AMD74XX_OVERRIDE is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_CMD680 is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_HPT34X_AUTODMA is not set
# CONFIG_BLK_DEV_HPT366 is not set
CONFIG_BLK_DEV_PIIX=y
CONFIG_PIIX_TUNING=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_ADMA100 is not set
# CONFIG_BLK_DEV_PDC202XX is not set
# CONFIG_PDC202XX_BURST is not set
# CONFIG_PDC202XX_FORCE is not set
CONFIG_BLK_DEV_RZ1000=y
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
CONFIG_BLK_DEV_VIA82CXXX=y
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Old non-SCSI/ATAPI CD-ROM drives
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
# CONFIG_BLK_DEV_MD is not set
# CONFIG_MD_LINEAR is not set
# CONFIG_MD_RAID0 is not set
# CONFIG_MD_RAID1 is not set
# CONFIG_MD_RAID5 is not set
# CONFIG_MD_MULTIPATH is not set
# CONFIG_BLK_DEV_LVM is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
# CONFIG_FUSION_BOOT is not set
# CONFIG_FUSION_ISENSE is not set
# CONFIG_FUSION_CTL is not set
# CONFIG_FUSION_LAN is not set

#
# I2O device support
#
# CONFIG_I2O is not set
# CONFIG_I2O_PCI is not set
# CONFIG_I2O_BLOCK is not set
# CONFIG_I2O_LAN is not set
# CONFIG_I2O_SCSI is not set
# CONFIG_I2O_PROC is not set

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_DEV_APPLETALK is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network device support
#
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_SUNLANCE is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNBMAC is not set
# CONFIG_SUNQE is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
# CONFIG_ELMC is not set
# CONFIG_ELMC_II is not set
CONFIG_VORTEX=y
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_E1000_NAPI is not set
# CONFIG_MYRI_SBUS is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_NET_FC is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set
# CONFIG_PHONE_IXJ is not set
# CONFIG_PHONE_IXJ_PCMCIA is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
# CONFIG_GAMEPORT_NS558 is not set
# CONFIG_GAMEPORT_L4 is not set
# CONFIG_GAMEPORT_EMU10K1 is not set
# CONFIG_GAMEPORT_VORTEX is not set
# CONFIG_GAMEPORT_FM801 is not set
# CONFIG_GAMEPORT_CS461x is not set
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_MOUSE_PS2 is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_JOYSTICK_ANALOG is not set
# CONFIG_JOYSTICK_A3D is not set
# CONFIG_JOYSTICK_ADI is not set
# CONFIG_JOYSTICK_COBRA is not set
# CONFIG_JOYSTICK_GF2K is not set
# CONFIG_JOYSTICK_GRIP is not set
# CONFIG_JOYSTICK_GRIP_MP is not set
# CONFIG_JOYSTICK_GUILLEMOT is not set
# CONFIG_JOYSTICK_INTERACT is not set
# CONFIG_JOYSTICK_SIDEWINDER is not set
# CONFIG_JOYSTICK_TMDC is not set
# CONFIG_JOYSTICK_IFORCE is not set
# CONFIG_JOYSTICK_WARRIOR is not set
# CONFIG_JOYSTICK_MAGELLAN is not set
# CONFIG_JOYSTICK_SPACEORB is not set
# CONFIG_JOYSTICK_SPACEBALL is not set
# CONFIG_JOYSTICK_STINGER is not set
# CONFIG_JOYSTICK_TWIDDLER is not set
# CONFIG_JOYSTICK_DB9 is not set
# CONFIG_JOYSTICK_GAMECON is not set
# CONFIG_JOYSTICK_TURBOGRAFX is not set
# CONFIG_INPUT_JOYDUMP is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_TOUCHSCREEN_GUNZE is not set
# CONFIG_INPUT_MISC is not set
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_UINPUT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
# CONFIG_SERIAL_8250_CONSOLE is not set
# CONFIG_SERIAL_8250_CS is not set
# CONFIG_SERIAL_8250_EXTENDED is not set
# CONFIG_SERIAL_8250_MANY_PORTS is not set
# CONFIG_SERIAL_8250_SHARE_IRQ is not set
# CONFIG_SERIAL_8250_DETECT_IRQ is not set
# CONFIG_SERIAL_8250_MULTIPORT is not set
# CONFIG_SERIAL_8250_RSA is not set
# CONFIG_UNIX98_PTYS is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_QFMT_V1 is not set
# CONFIG_QFMT_V2 is not set
# CONFIG_AUTOFS_FS is not set
CONFIG_AUTOFS4_FS=y
# CONFIG_REISERFS_FS is not set
# CONFIG_REISERFS_CHECK is not set
# CONFIG_REISERFS_PROC_INFO is not set
# CONFIG_ADFS_FS is not set
# CONFIG_ADFS_FS_RW is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
# CONFIG_UMSDOS_FS is not set
CONFIG_VFAT_FS=m
# CONFIG_EFS_FS is not set
# CONFIG_JFFS_FS is not set
# CONFIG_JFFS2_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_ISO9660_FS=m
# CONFIG_JOLIET is not set
# CONFIG_ZISOFS is not set
# CONFIG_JFS_FS is not set
# CONFIG_JFS_DEBUG is not set
# CONFIG_JFS_STATISTICS is not set
CONFIG_MINIX_FS=m
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_NTFS_DEBUG is not set
# CONFIG_NTFS_RW is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
# CONFIG_DEVPTS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_QNX4FS_RW is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UDF_RW is not set
# CONFIG_UFS_FS is not set
# CONFIG_UFS_FS_WRITE is not set

#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
CONFIG_NFS_FS=y
# CONFIG_NFS_V3 is not set
# CONFIG_ROOT_NFS is not set
# CONFIG_NFSD is not set
# CONFIG_NFSD_V3 is not set
# CONFIG_NFSD_TCP is not set
CONFIG_SUNRPC=y
CONFIG_LOCKD=y
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_NCPFS_PACKET_SIGNING is not set
# CONFIG_NCPFS_IOCTL_LOCKING is not set
# CONFIG_NCPFS_STRONG is not set
# CONFIG_NCPFS_NFS_NS is not set
# CONFIG_NCPFS_OS2_NS is not set
# CONFIG_NCPFS_SMALLDOS is not set
# CONFIG_NCPFS_NLS is not set
# CONFIG_NCPFS_EXTRAS is not set
# CONFIG_ZISOFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
# CONFIG_SMB_NLS is not set
CONFIG_NLS=y

#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
# CONFIG_NLS_CODEPAGE_437 is not set
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ISO8859_1 is not set
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Console drivers
#
CONFIG_VGA_CONSOLE=y
CONFIG_VIDEO_SELECT=y

#
# Sound
#
# CONFIG_SOUND is not set

#
# USB support
#
# CONFIG_USB is not set

#
# Bluetooth support
#
# CONFIG_BLUEZ is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set

#
# Security options
#
CONFIG_SECURITY_CAPABILITIES=y

#
# Library routines
#
# CONFIG_CRC32 is not set
# CONFIG_ZLIB_INFLATE is not set
# CONFIG_ZLIB_DEFLATE is not set

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 19:35 ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Friedrich Lobenstock
  2002-09-05 20:02     ` Dag Nygren
  2002-09-05 20:14   ` 2.5.xx kernels won't run on my Athlon boxes Kirk Reiser
@ 2002-09-05 21:19   ` Kai Makisara
  2002-09-05 22:15     ` Friedrich Lobenstock
  2 siblings, 1 reply; 11+ messages in thread
From: Kai Makisara @ 2002-09-05 21:19 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste

On Thu, 5 Sep 2002, Friedrich Lobenstock wrote:

> Hi!
>
> I'm having an odd problem here. I use SuSE Linux 8.0 with kernel
> 2.4.18-64GB-SMP, arkeia as backup software and a Tandberg
> VS80 (DLT1) streamer.
>
> After some trial and error I found out that I have to use a fixed block
> size for DLT streamers (same applies to LTO ones). This document,
> found at HP, tells you in details about which blocksize to use:
>    http://www.hp.com/cposupport/information_storage/support_doc/lpg50167.html
>
> Now I told arkeia to use a blocksize of 65536, 32768 and 16384 and it
> could not write to the tape. All I got in the log was:
>
> Sep  4 22:04:50 filesrv kernel: st: Unloaded.
> Sep  4 22:08:40 filesrv kernel: st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16
> Sep  4 22:08:40 filesrv kernel: st0: Block limits 2 - 16777214 bytes.
> Sep  4 22:08:41 filesrv kernel: st0: Incorrect block size.
> Sep  4 22:08:45 filesrv kernel: st0: Write not multiple of tape block size.
                                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
The write() byte count from Arkeia is not a multiple of the tape block
size. If you use fixed block size, you must take care that this constraint
is not violated. When you set the block size to 8192 or something that
multiplies to 8192, this constraint is obeyed. If Arkeia sets the block
size, I don't know why it does not obey the constraint. Seems to be an
application problem.

In most cases, it is best to use variable block mode
(i.e., mt setblk 0) and let the application to decide the tape block size.
In order to have good efficiency, you should make sure that the
application uses large enough byte counts in its write() calls, i.e., set
the Arkeia block size to 65536.

	Kai



^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 21:19   ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Kai Makisara
@ 2002-09-05 22:15     ` Friedrich Lobenstock
  2002-09-06  0:00       ` Willem Riede
  0 siblings, 1 reply; 11+ messages in thread
From: Friedrich Lobenstock @ 2002-09-05 22:15 UTC (permalink / raw)
  To: Linux-SCSI Mailingliste; +Cc: support

Kai Makisara wrote:
> On Thu, 5 Sep 2002, Friedrich Lobenstock wrote:
> 
> 
>>Hi!
>>
>>I'm having an odd problem here. I use SuSE Linux 8.0 with kernel
>>2.4.18-64GB-SMP, arkeia as backup software and a Tandberg
>>VS80 (DLT1) streamer.
>>
>>After some trial and error I found out that I have to use a fixed block
>>size for DLT streamers (same applies to LTO ones). This document,
>>found at HP, tells you in details about which blocksize to use:
>>   http://www.hp.com/cposupport/information_storage/support_doc/lpg50167.html
>>
>>Now I told arkeia to use a blocksize of 65536, 32768 and 16384 and it
>>could not write to the tape. All I got in the log was:
>>
>>Sep  4 22:04:50 filesrv kernel: st: Unloaded.
>>Sep  4 22:08:40 filesrv kernel: st: Version 20020205, bufsize 32768, wrt 30720, max init. bufs 4, s/g segs 16
>>Sep  4 22:08:40 filesrv kernel: st0: Block limits 2 - 16777214 bytes.
>>Sep  4 22:08:41 filesrv kernel: st0: Incorrect block size.
>>Sep  4 22:08:45 filesrv kernel: st0: Write not multiple of tape block size.
> 
>                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> The write() byte count from Arkeia is not a multiple of the tape block
> size. If you use fixed block size, you must take care that this constraint
> is not violated. When you set the block size to 8192 or something that
> multiplies to 8192, this constraint is obeyed. If Arkeia sets the block
> size, I don't know why it does not obey the constraint. Seems to be an
> application problem.
> 
> In most cases, it is best to use variable block mode
> (i.e., mt setblk 0) and let the application to decide the tape block size.
> In order to have good efficiency, you should make sure that the
> application uses large enough byte counts in its write() calls, i.e., set
> the Arkeia block size to 65536.

Hmmm...I whish I could, but LTO and as it seems DLT drives too do not
cope well with variable block sizes.

All blocksizes greater than 8192 do make troubles. At and below this
value all is fine.


-- 
MfG / Regards
Friedrich Lobenstock


^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives?
  2002-09-05 22:15     ` Friedrich Lobenstock
@ 2002-09-06  0:00       ` Willem Riede
  0 siblings, 0 replies; 11+ messages in thread
From: Willem Riede @ 2002-09-06  0:00 UTC (permalink / raw)
  To: linux-scsi

On 2002.09.05 18:15 Friedrich Lobenstock wrote:
> Kai Makisara wrote:
> > On Thu, 5 Sep 2002, Friedrich Lobenstock wrote:
> > 
> >>Now I told arkeia to use a blocksize of 65536, 32768 and 16384 and it
> >>could not write to the tape. All I got in the log was:
> >>
> >>Sep  4 22:08:41 filesrv kernel: st0: Incorrect block size.
> >>Sep  4 22:08:45 filesrv kernel: st0: Write not multiple of tape block size.
> > 
> >                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > The write() byte count from Arkeia is not a multiple of the tape block
> > size. If you use fixed block size, you must take care that this constraint
> > is not violated. When you set the block size to 8192 or something that
> > multiplies to 8192, this constraint is obeyed. If Arkeia sets the block
> > size, I don't know why it does not obey the constraint. Seems to be an
> > application problem.
> > 
> > In most cases, it is best to use variable block mode
> > (i.e., mt setblk 0) and let the application to decide the tape block size.
> > In order to have good efficiency, you should make sure that the
> > application uses large enough byte counts in its write() calls, i.e., set
> > the Arkeia block size to 65536.
> 
> Hmmm...I whish I could, but LTO and as it seems DLT drives too do not
> cope well with variable block sizes.
> 
> All blocksizes greater than 8192 do make troubles. At and below this
> value all is fine.

I had a run in with Arkeia some time ago when used with osst tape devices,
and if I remember correctly, it is best to not tell Arkeia anything about
the block size to use. It will use multiples of 8192 in that case. Given
that you say the DLT drive is happy with 8192 block size that should work.

Regards, Willem Riede.

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2002-09-06  0:11 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <fl@fl.priv.at>
2002-09-05 19:35 ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Friedrich Lobenstock
2002-09-05 20:02   ` Dag Nygren
2002-09-05 20:02     ` Dag Nygren
2002-09-05 20:59     ` Friedrich Lobenstock
2002-09-05 21:28       ` Kai Makisara
2002-09-05 22:07       ` Dag Nygren
2002-09-06  0:15       ` jw schultz
2002-09-05 20:14   ` 2.5.xx kernels won't run on my Athlon boxes Kirk Reiser
2002-09-05 21:19   ` blocksize limitations in scsi tape driver (st) when used with DLT1 tape drives? Kai Makisara
2002-09-05 22:15     ` Friedrich Lobenstock
2002-09-06  0:00       ` Willem Riede

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.