Date: Wed, 14 Aug 2013 09:03:42 -0500 (CDT) From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us> To: Willem Jan Withagen <wjw@digiware.nl> Cc: fs@freebsd.org Subject: Re: Fwd: Disk scheduling activity... Message-ID: <alpine.GSO.2.01.1308140859070.2267@freddy.simplesystems.org> In-Reply-To: <520B8B1E.7060002@digiware.nl> References: <520B8B1E.7060002@digiware.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Aug 2013, Willem Jan Withagen wrote: > > Just a point of information or curiosity, and I don't think/know if it > is any problem... > > I have the raidz array with 8 disks, which I'm using to backup to. > It is configured > 4 disks on a mvs controller > 4 disks on an Areca controller (JBODs with battery) > Both controllers are on a PCI-E slot > > Most of the time the source just fully loads the pipe and sends 1Gbit/s. > > When that happens I see this alternating pattern of writing either to > the 4 mvs disks, or writing to the Areca disks. > But almost never are all disk accesses at the same time. > And really never, never is there a mix of writing between the controller > sets. Are all 8 disks in the same raidz vdev? Are you basing write activity on the drive LEDs? The Areca controller may be caching the writes in its battery-backed cache and deferring the writes to when zfs tells it to flush its cache. The other controller may be issuing the writes right away. This would explain apparent 'split' writing behavior. There is even the possibilty that one of the controllers ignores the cache flush request and performs the writes later when it feels like it. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.2.01.1308140859070.2267>