10-10-2010
Hai Roland. Is there a problem? What is your problem? It is normal that you get higher throughput with large block sizes. 44 MB/s sequential write performance with a 512 byte block size directly to a device (no write combining) seems pretty decent to me. Is it much larger than the write cache of the controller? What were you expecting?
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi you all, I have a BIG performance problem on an Sun E3500, the scenario is described below:
I have several users (30) accessing via samba to the E3500 using an application built on Visual Foxpro from their Windows PC , the problem is that the first guy that logs in demands 30% of the E3500... (2 Replies)
Discussion started by: alex blanco
2 Replies
2. Filesystems, Disks and Memory
Hello,
i have a a1000 connected to an e6500. There's a raid 10 (12 disks) on the a1000.
If i do a
dd if=/dev/zero of=/mnt/1 bs=1024k count=1000
and then look at iostat it tells me there's a kw/s of 25000.
But if i do a
dd of=/dev/zero if=/mnt/1 bs=1024k count=1000
then i see only a... (1 Reply)
Discussion started by: mbrenner
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I'm running a script on AIX to process lines in a file. I need to enclose the second column in quotation marks and write each line to a new file. I've come up with the following:
#!/bin/ksh
filename=$1
exec >> $filename.new
cat $filename | while read LINE
do
echo $LINE | awk... (2 Replies)
Discussion started by: scooter53080
2 Replies
4. Solaris
Hello,
we have a machine with Solaris Express 11, 2 LSI 9211 8i SAS 2 controllers (multipath to disks), multiport backplane, 16 Seagate Cheetah 15K RPM disks.
Each disk has a sequential performance of 220/230 MB/s and in fact if I do a
dd if=/dev/zero of=/dev/rdsk/<diskID_1> bs=1024k... (1 Reply)
Discussion started by: golemico
1 Replies
5. Solaris
Hello guys,
I have two servers performing the same disk operations. I believe one server is having a disk's impending failure however I have no hard evidence to prove it. This is a pair of Netra 210's with 2 drives in a hardware raid mirror (LSI raid controller). While performing intensive... (4 Replies)
Discussion started by: s ladd
4 Replies
6. AIX
Hi,
I am new registered user here in this UNIX forums.
I am a new system administrator for AIX 6.1. One of our servers performs poorly every time our application (FINACLE) runs many processes/instances. (see below for topas snapshot)
I use NMON or Topas to monitor the server utilization. I... (9 Replies)
Discussion started by: guzzelle
9 Replies
7. Solaris
Hi
We have an M3000 single physical processor and 8gb of memory running Solaris 10. This system runs two Oracle Databases one on Oracle 9i and One on Oracle 10g.
As soon as the Oracle 10g database starts we see an immediate drop in system performance, for example opening an ssh session can... (6 Replies)
Discussion started by: gregsih
6 Replies
8. AIX
Hi Everyone,
I have been struggling for few days with iSCSI and thought I could get some help on the forum...
fresh install of AIX7.1 TL4 on Power 710, The rootvg relies on 3 SAS disks in RAID 0, 32GB Memory
The lpar Profile is using all of the managed system's resources.
I have connected... (11 Replies)
Discussion started by: frenchy59
11 Replies
9. Windows & DOS: Issues & Discussions
Just a quick note for macOS users.
I just installed (and removed) Parallels Desktop 15 Edition on my MacPro (2013) with 64GB memory and 12-cores, which is running the latest version of macOS Catalina as of this post. The reason for this install was to test some RIGOL test gear software which... (6 Replies)
Discussion started by: Neo
6 Replies
VOL(1) General Commands Manual VOL(1)
NAME
vol - split input on or combine output from several volumes
SYNOPSIS
vol [-rw1] [-b blocksize] [-m multiple] [size] device
DESCRIPTION
Vol either reads a large input stream from standard input and distributes it over several volumes or combines volumes and sends them to
standard output. The size of the volumes is determined automatically if the device supports this, but may be specified before the argument
naming the device if automated detection is not possible or if only part of the physical volume is used. The direction of the data is
automatically determined by checking whether the input or output of vol is a file or pipe. Use the -r or -w flag if you want to specify
the direction explicitly, in shell scripts for instance.
Vol waits for each new volume to be inserted, typing return makes it continue. If no size is explicitely given then the size of the device
is determined each time before it is read or written, so it is possible to mix floppies of different sizes. If the size cannot be deter-
mined (probably a tape) then the device is assumed to be infinitely big. Vol can be used both for block or character devices. It will
buffer the data and use a block size appropriate for fixed or variable block sized tapes.
Vol reads or writes 8192 bytes to block devices, usually floppies. Character devices are read or written using a multiple of 512 bytes.
This multiple has an upper limit of 32767 bytes (16-bit machine), 64 kb (32-bit), or even 1 Mb (32-bit VM). The last partial write to a
character device is padded with zeros to the block size. If a character device is a tape device that responds to the mtio(4) status call
then the reported tape block size will be used as the smallest unit. If the tape is a variable block length device then it is read or
written like a block device, 8192 bytes at the time, with a minimum unit of one byte.
All sizes may be suffixed by the letters M, k, b or w to multiply the number by mega, kilo, block (512), or word (2). The volume size by
default in kilobytes if there is no suffix.
OPTIONS
-rw Explicitly specify reading or writing. Almost mandatory in scripts.
-1 Just one volume, start immediately.
-b blocksize
Specify the device block size.
-m multiple
Specify the maximum read or write size of multiple blocks. The -b and -m options allow one to modify the block size assumptions
that are made above. These assumptions are -b 1 -m 8192 for block devices or variable length tapes, and -b 512 -m 65536 for charac-
ter devices (32 bit machine.) These options will not override the tape block size found out with an mtio(4) call. The multiple may
be larger then the default if vol can allocate the memory required.
EXAMPLES
To back up a tree to floppies as a compressed tarfile:
tar cf - . | compress | vol /dev/fd0
To restore a tree from 720 kb images from possibly bigger floppies:
vol 720 /dev/fd0 | uncompress | tar xfp -
Read or write a device with 1024 byte blocks:
vol -b 1k /dev/rsd15
Read or write a variable block length tape using blocking factor 20 as used by default by many tar(1) commands:
vol -m 20b /dev/rst5
Note that -m was used in the last example. It sets the size to use to read or write, -b sets the basic block size that may be written in
multiples.
SEE ALSO
dd(1), tar(1), mt(1), mtio(4).
VOL(1)