On Tue, May 25, 2010 at 1:05 PM, Matthew Seaman <m.sea...@infracaninophile.co.uk> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 25/05/2010 11:40:23, Stefan Bethke wrote: >> For the record: I'm now running -stable as of last night, compiled >> without issue on ZFS filesystems throughout. No idea what caused the >> issue in the first place, and what made it disappear though, but >> updating to the correctly built -stable made the build on ZFS work >> again. (It also involved an accidential upgrade and downgrade via >> -current, since I checked out the wrong tag with csup. Yikes.) > > I've a new machine that's been running 8-STABLE on ZFS for about a week > now. Had no problems installing and then upgrading to recent 8-STABLE > although I did start with installing an 8-STABLE snapshot rather than > 8.0-RELEASE. (See: http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror) > > Verb. Sap. If you're booting from ZFS, beware of updating the zpool > version without due care and attention. 8.0-RELEASE was on version 13, > 8-STABLE is now on version 14. (Use 'zpool update' to see what the > status is on your machine -- this just gives you a report, and doesn't > update anything.) Updating the zpool version is pretty smooth and > simple, but *remember to immediately rebuild and reinstall gptzfsboot or > zfsboot bootcode on your drives*. If you don't do that, your system > won't be able to find the pool with the root filesystem and so won't be > able to reboot. > >
Old thread, I know. But I encountered this error today and my solution was that /tmp was tmpfs and it was full. Cleaning that up fixed the error. -- chs, _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
