|
Re: tar's default block size & shoe-shinning
2006-06-20 09:17:29
On Tue, 20 Jun 2006 at 9:47am, Cyrille Bollu wrote
The server is a Dell PowerEdge 2850 with 2 Intel Xeon 3GHz processors and
8GB RAM.
I have one big RAID5 array made of 6 Seagate Cheetah ST3300007LC 10Krpm
300GB
(http://support.euro.dell.com/support/edocs/storage/p76311sc/intro.htm).
All connected to channel 0 of a Dell PowerEdge Expandable RAID Controller
4e/Di (h
ttp://support.euro.dell.com/support/edocs/storage/RAID/perc4e/en/ug/index.htm).
See hereunder for more info.
How much benchmarking/optimization have you done with the array?
I'm running Linux RedHat ES 3.3.
That's an awfully old point release. Any reason for that?
scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 3960D Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36
<Adaptec 3960D Ultra160 SCSI adapter>
aic7899: Ultra160 Wide Channel B, SCSI Id=7, 32/253 SCBs
blk: queue f77c5618, I/O limit 524287Mb (mask 0x7fffffffff)
(scsi0:A:6): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)
Vendor: IBM Model: ULTRIUM-TD3 Rev: 5480
Type: Sequential-Access ANSI SCSI revision: 03
So you're tape drive is on a U160 adapter rather than a U320 one. I think
the problem is in the array though, not the tape drive.
I'd look hard at optimizing the array (although if it's in production,
that may be tough).
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
|
|
|
