El 25 de març de 2012 23:07, Christoph Egger <christ...@debian.org> ha escrit: > Robert Millan <r...@debian.org> writes: >> I'm not sure if people in debian-bsd can help with this. I myself >> can't. Maybe you should try to reproduce this in a pure FreeBSD >> environment by trying to import the pool from a FreeBSD system. If it >> can be imported with kFreeBSD 8.x (either GNU or BSD userland), but >> not with pure FreeBSD 9.0, then it's IMHO worth reporting to ZFS >> experts in freebsd-fs. > > I was now able to reproduce the problem in a 10-CURRENT build done on > pure freebsd 9.0-STABLE with default cc though the failing box is (of > course) still kfreebsd.
I was hit by this too. Really annoying :-( > There should be no othyer debian influcenes before the reoot filesystem > comes available apart from grub right? Going to take this upstream if > so. There might be something written on disk by Debian kernel that upstream kernel doesn't. Probably not file system corruption since it's clearly recoverable (as I write, my system just came back to normal after simply booting a D-I image and importing the pool there). But as the data is there, if upstream kernels can't access it I think it's probably relevant to them. If you bring this upstream, I recommend writing to freebsd-fs, it's much easier to get attention there than by filing a PR. -- Robert Millan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
