Date: Fri, 22 Jan 2016 00:19:00 -0500 From: Mason Loring Bliss <mason@blisses.org> To: David Christensen <dpchrist@holgerdanske.com> Cc: freebsd-questions@freebsd.org Subject: Re: ZFS performance help sought Message-ID: <20160122051900.GP4538@blisses.org> In-Reply-To: <56A1B969.4020107@holgerdanske.com> References: <20160121205139.GG4538@blisses.org> <56A1B969.4020107@holgerdanske.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 21, 2016 at 09:08:57PM -0800, David Christensen wrote: > 1. Have you tested the disks, cables, and controllers individually using > disk manufacturer diagnostics? E.g. for Seagate, SeaTools for DOS (bootable > CD based on FreeDOS; MS-DOS not required): Yeah. Plus, this only happens with FreeBSD, and I don't believe that Linux is quietly working around some really subtle weirdnesses in my drives. Honestly, the verification you're suggesting would be an absolutely tremendous amount of work and pretty disruptive only to highlight that the hardware is okay and FreeBSD or the way it uses ZFS is doing something odd. I did the "here, let me test the devices" dance when I discovered an OS- agnostic flaw in OpenZFS, and I'm just not going to do it again. I don't want to seem ungrateful for your time in writing up the questions, but I don't see how I can reasonably obtain the data you want. It'd be much less work to just go to a known-good Linux configuration, but that doesn't make FreeBSD better, which is a giant part of my goal in having switched back. The iostat output earlier in the thread showed a snapshot of relative performance, and I'm happy to do more diagnostics that don't involve disassembling this particular box. -- Mason Loring Bliss mason@blisses.org Ewige Blumenkraft! (if awake 'sleep (aref #(sleep dream) (random 2))) -- Hamlet, Act III, Scene I
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160122051900.GP4538>