Date: Fri, 16 May 2008 01:19:33 -0700 From: "Paul Saab" <ps@mu.org> To: "Claus Guttesen" <kometen@gmail.com> Cc: freebsd-stable@freebsd.org, Emil Mikulic <emikulic@gmail.com> Subject: Re: ciss(4) not coping with large arrays? Message-ID: <5c0ff6a70805160119n2f8361c4y7b3c1451f36d3c6e@mail.gmail.com> In-Reply-To: <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com> References: <20080516073932.GA39803@dmr.ath.cx> <b41c75520805160050l3c9acc4fx94bfabccb1f4d1d3@mail.gmail.com> <5c0ff6a70805160103o75461976wce04f697975a176c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, May 16, 2008 at 1:03 AM, Paul Saab <ps@mu.org> wrote: > On Fri, May 16, 2008 at 12:50 AM, Claus Guttesen <kometen@gmail.com> > wrote: > >> > Running today's RELENG_7 (although 7.0-RELEASE has the same problem), >> > GENERIC kernel on an amd64 and I can't seem to get a da(4) device for >> > any arrays bigger than 2TB. >> >> In earlier releases (5 and 6 at least) you couldn't create partitions >> larger than 2 TB. I don't know whether work has been to circumvent >> this in 7 but tools like fsck has to be changed as well. Have you >> tried zfs? > > > zfs has nothing to do with this. The driver is not properly dealing with > the large volume. > > set the kernel tunable in loader.conf > > kern.cam.da.3.minimum_cmd_size=16 > kern.cam.da.4.minimum_cmd_size=16 > > Actually, this has nothing to do with it either.. Please try the following patch: http://yogurt.org/FreeBSD/ciss_large.diff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5c0ff6a70805160119n2f8361c4y7b3c1451f36d3c6e>