Date: Wed, 6 Aug 2008 12:15:04 +0200 From: "Claus Guttesen" <kometen@gmail.com> To: "Pawel Jakub Dawidek" <pjd@freebsd.org> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS patches. Message-ID: <b41c75520808060315t4a5d7b16p55cd61526df5c96c@mail.gmail.com> In-Reply-To: <b41c75520808010638j4e40e68gd2ae92ebbd3dd66c@mail.gmail.com> References: <20080727125413.GG1345@garage.freebsd.pl> <b41c75520807310808jbc5c4f1v968255c4695a245d@mail.gmail.com> <b41c75520808010519g5393c362p4ef5a02ca070fece@mail.gmail.com> <b41c75520808010638j4e40e68gd2ae92ebbd3dd66c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> I have a areca arc-1680 sas-card and an external sas-cabinet with 16 >>> sas-drives each 1 TB (931 binary GB). They have been setup in three >>> raidz-partitions with five disks each in one zpool and one spare. >>> >> My conclusion about it's stability was a bit hasty. I was copying >> approx. 400 GB from a nfs-share mounted from a solaris 9 on sparc >> using tcp and read- and write-size of 32768. The files are images >> slightly less than 1 MB and a thumbnail (approx. 983000 files). > > There seems to be a hardware-related problem to my setup. I'm getting > some 'arcmsr0: scsi id=1 lun=4 ccb='0xffffff02d5cc8e00' outstanding > command timeout' (in solaris). I'll check with my vendor. I did not > see such errors in FreeBSD. I changed the configration on the areca arc-1680-card and put all disks in throughput-mode and is now able to copy large amounts of data (more than 1 TB) without problems. I have 'zpool offline'd a disk and 'zpool replace'd it with a spare. The resilver is progressing as normal and the zpool is accessible. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b41c75520808060315t4a5d7b16p55cd61526df5c96c>