Bug in recent large_alloc changes to the ZFS zio code?
kmacy at freebsd.org
Sun Jun 7 22:17:04 UTC 2009
It's been fixed.
On Sun, Jun 7, 2009 at 2:43 PM, ian j hart<ianjhart at ntlworld.com> wrote:
> On Monday 01 June 2009 05:39:26 Kip Macy wrote:
>> On Sun, May 31, 2009 at 12:49 AM, Richard Todd
>> <rmtodd at ichotolot.servalan.com> wrote:
>> > On Sat, May 30, 2009 at 11:54:47PM -0700, Kip Macy wrote:
>> >> http://svn.freebsd.org/changeset/base/192360
>> > Ah. Hmm. So if I'm reading this right, you already backed out that
>> > change in the master SVN repo, right? Well, *something* weird's going
>> > on, because that change never seems to have made it to the CVS version of
>> > the repo or to the cvsup sites, because I'm not seeing it there; see for
>> > yourself at
>> > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/ut
>> >s/common/fs/zfs/ . The commit log for 192360 never showed up in
>> > CVSROOT-src/commitlogs/sys either. So it looks like bits are falling on
>> > the floor somewhere between the SVN and CVS repos.
>> Yup. This is causing problems for other ZFS users on head. It looks
>> like if you use ZFS on head you need to use svn.
>> I'm not in a position to fix this issue.
>> freebsd-current at freebsd.org mailing list
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> Is this (cvs missing updates) still broken?
> I have an issue with zfs which I'm trying to explore. I'd like to make sure I
> have an up to date CURRENT. I only have cvs.
> ian j hart
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
When bad men combine, the good must associate; else they will fall one
by one, an unpitied sacrifice in a contemptible struggle.
More information about the freebsd-current