Date: Fri, 25 Dec 2009 18:08:21 +0100 From: Solon Lutz <solon@pyro.de> To: Wes Morgan <morganw@chemikals.org> Cc: freebsd-fs@freebsd.org Subject: Re: ZFS RaidZ2 with 24 drives? Message-ID: <168533615.20091225180821@pyro.de> In-Reply-To: <alpine.BSF.2.00.0912250833330.87887@ibyngvyr> References: <568624531.20091215163420@pyro.de> <42952D86-6B4D-49A3-8E4F-7A1A53A954C2@spry.com> <957649379.20091216005253@pyro.de> <26F8D203-A923-47D3-9935-BE4BC6DA09B7@corp.spry.com> <1696529130.20091223212612@pyro.de> <op.u5gbvfgz8527sy@82-170-177-25.ip.telfort.nl> <deb820500912241646p7c8fd726n5c68895105e28907@mail.gmail.com> <1266543768.20091225120330@pyro.de> <deb820500912250311y14cd0975i4e3a28c5fea24789@mail.gmail.com> <982740779.20091225122331@pyro.de> <alpine.BSF.2.00.0912250833330.87887@ibyngvyr>
next in thread | previous in thread | raw e-mail | index | archive | help
> I have my suspicions that this means your filesystem is heavily > fragmented. I've had it happen to me on at least 3 pools, some of which > were not even close to full, yet rebuilding the pool restored much of the > performance. Hopefully with the block pointer rewrite support coming we > will get some tools to address this. Right now I am not even aware of a > tool that will check for fragmentation. Fragmentation is not an issue, as the destination pool was freshly created and the source was created in a continous copy operation... =( Best regards, Solon Lutz +-----------------------------------------------+ | Pyro.Labs Berlin - Creativity for tomorrow | | Wasgenstrasse 75/13 - 14129 Berlin, Germany | | www.pyro.de - phone + 49 - 30 - 48 48 58 58 | | info@pyro.de - fax + 49 - 30 - 80 94 03 52 | +-----------------------------------------------+
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?168533615.20091225180821>