after some fruitful discussions with Jörg, it turned out that my mtwrite
patch prevents tar, star, gtar, and unzip from setting the file times
correctly. I've investigated this issue and updated the patch accordingly.
Unfortunately, I encountered an issue concerning semaphores, which seem
to
No, that is definitely not expected.
One thing that can hose you is having a single disk that performs
really badly. I've seen disks as slow as 5 MB/sec due to vibration,
bad sectors, etc. To see if you have such a disk, try my diskqual.sh
script (below). On my desktop system, which has 8
On Mon, 14 Apr 2008, Jeff Bonwick wrote:
disks=`format /dev/null | grep c.t.d | nawk '{print $2}'`
I had to change the above line to
disks=`format /dev/null | grep ' c.t' | nawk '{print $2}'`
in order to match my mutipathed devices.
./diskqual.sh
c1t0d0 130 MB/sec
c1t1d0 13422 MB/sec
Hi!
I just want to check with the community to see if this is normal.
I have used a X4500 with 500Gb disks and I'm not impressed by the copy
performance.
I can run several jobs in parallel and get close to 400mb/s but I need better
performance
from a single copy. I have tried to be EVIL as
On my drive array (capable of 260MB/second single-process writes and
450MB/second single-process reads) 'zfs iostat' reports a read rate of
about 59MB/second and a write rate of about 59MB/second when executing
'cp -r' on a directory containing thousands of 8MB files. This seems
very similar
Bob Friesenhahn schrieb:
On my drive array (capable of 260MB/second single-process writes and
450MB/second single-process reads) 'zfs iostat' reports a read rate of
about 59MB/second and a write rate of about 59MB/second when executing
'cp -r' on a directory containing thousands of 8MB
