Date: Sun, 22 Apr 2007 23:10:30 +0200 From: Peter Schuller <peter.schuller@infidyne.com> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Stefan Esser <se@FreeBSD.org> Subject: Re: ZFS: amd64, devd, root file system. Message-ID: <462BCF46.6030704@infidyne.com> In-Reply-To: <20070414102313.GC10527@garage.freebsd.pl> References: <20070409011723.GB74547@garage.freebsd.pl> <20070409094319.GB76673@garage.freebsd.pl> <46209D21.2010704@FreeBSD.org> <20070414102313.GC10527@garage.freebsd.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig69D91C5C4686F069537DB143 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > This is not the first report that it doesn't work as it should. FWIW, I had some trouble converting my root to ZFS too. I had load_zfs=3D"YES" and the appropriate vfs.root.mountfrom option in loader.conf, but the kernel did not know of any available zfs:* devices that were candidates for root mounts (according to the output of "?"). It may just have been a matter of zpool.cache not being up to date with the volume I was trying to use for root; I do not remember whether the version on /boot was recent enough for that. In general it feels a bit unclear what will happen with zpool.cache when having root on ZFS. Is it guaranteed that only userland tools modify or read this file? In my case the devices in the ZFS pool were glabel:ed, so the issue of drives moving about and such should not have affected me (plus at the point where I had this problem I had not yet started shuffling drives). glabel has successfully loaded and tasted all relevant devices prior to ZFS loading, judging by the kernel output (glabel label detection prior to the ZFS pool version output). In this case I ended up just putting /usr on zfs, leaving / on UFS. Doing so was no problem; the only snag was that putting /usr in /etc/fstab would cause some rc script to try to run fsck_zfs. I ended up not even putting in in /etc/fstab, and having /usr be a symlink to the ZFS managed mountpoint (in this case, /zpromusr). > One was > that /boot/defaults/loader.conf wasn't fresh enough, and there were no:= >=20 > zpool_cache_load=3D"YES" > zpool_cache_type=3D"/boot/zfs/zpool.cache" > zpool_cache_name=3D"/boot/zfs/zpool.cache" >=20 > lines at the end. Can you verify you have them? This is confirmed to not be the issue in my case. --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller@infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --------------enig69D91C5C4686F069537DB143 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGK89ODNor2+l1i30RCMM6AKCC2BWS56NADSVYJedSEAlVtW2//gCgmv27 ZzvGkDgnHjZC0pFZQ7BzpXU= =Ft18 -----END PGP SIGNATURE----- --------------enig69D91C5C4686F069537DB143--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?462BCF46.6030704>