Date: Tue, 18 Aug 2009 17:03:34 +0200 From: Thomas Backman <serenity@exscape.org> To: Gavin Atkinson <gavin@FreeBSD.org> Cc: FreeBSD current <freebsd-current@FreeBSD.org>, Pawel Dawidek Jakub <pjd@FreeBSD.org> Subject: Re: Bad news re: new (20080817) ZFS patches and send/recv (broken again) Message-ID: <2254F332-3304-4521-884E-F6BC5BBE544C@exscape.org> In-Reply-To: <1250607450.41855.39.camel@buffy.york.ac.uk> References: <AA349CA1-6BB8-44BC-B05E-37CC4F3480E0@exscape.org> <25E11A9B-9FDE-4C34-8C6F-8A7883E9876A@exscape.org> <B8CBCAE0-D057-4469-B481-21A4F2F6A4B0@exscape.org> <1250607450.41855.39.camel@buffy.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 18, 2009, at 16:57, Gavin Atkinson wrote: > On Tue, 2009-08-18 at 16:20 +0200, Thomas Backman wrote: >> OK, I tried to reproduce this in a VM... And I have to say I was a >> bit >> surprised: after doing an installkernel/installworld, but BEFORE >> REBOOTING (I install in "multi"-user (one user via ssh), never had a >> problem with that), the same issue has appeared, so I'm guessing >> zfs.ko can't be to blame here? >> What the heck? > > So, you're using a new zfs binary, with an old kernel? This isn't > supported and there's every chance it will fail in odd ways. > > Gavin Well, yes, but it fails no matter what... In the previous case, I installed as usual, rebooted as usual and it still fails the exact same way.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2254F332-3304-4521-884E-F6BC5BBE544C>