On Sep 27, 2009, at 3:19 AM, Paul Archer <p...@paularcher.org> wrote:
So, after *much* wrangling, I managed to take on of my drives
offline, relabel/repartition it (because I saw that the first sector
was 34, not 256, and realized there could be an alignment issue),
and get it back into the pool.
Problem is that while it's back, the performance is horrible. It's
resilvering at about (according to iostat) 3.5MB/sec. And at some
point, I was zeroing out the drive (with 'dd if=/dev/zero of=/dev/
dsk/c7d0'), and iostat showed me that the drive was only writing at
around 3.5MB/sec. *And* it showed reads of about the same 3.5MB/sec
even during the dd.
This same hardware and even the same zpool have been run under linux
with zfs-fuse and BSD, and with BSD at least, performance was much
better. A complete resilver under BSD took 6 hours. Right now zpool
is estimating this resilver to take 36.
Could this be a driver problem? Something to do with the fact that
this is a very old SATA card (LSI 150-6)?
This is driving me crazy. I finally got my zpool working under
Solaris so I'd have some stability, and I've got no performance.
It appears your controller is preventing ZFS from enabling write cache.
I'm not familiar with that model. You will need to find a way to
enable the drives write cache manually.
-Ross
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
