On Sun, Sep 15, 2013 at 11:13 AM, Andriy Gapon wrote:
> Unfortunately, I am not sure if it is possible to obtain anu useful
> information
> from ddb and saving a crash dump is not possible in pre-init environment.
> I could write a patch that would print some useful debugging info.
> Will you abl
on 16/09/2013 07:42 kpn...@pobox.com said the following:
> What happens if mountpoint is inherited instead of being set to one of
> those two values?
Would you like to test this and tell us?
I am 99.9% confident that mountpoint and canmount properties are never examined
in kernel. They are honor
on 15/09/2013 17:16 J David said the following:
> Thanks very much for the info Andriy.
>
> On Fri, Sep 13, 2013 at 9:22 AM, Andriy Gapon wrote:
>> Another piece of information is that neither mountpoint nor canmount property
>> affects ZFS root mounting.
>
> It is mountpoint=legacy that boots o
Thanks very much for the info Andriy.
On Fri, Sep 13, 2013 at 9:22 AM, Andriy Gapon wrote:
> Another piece of information is that neither mountpoint nor canmount property
> affects ZFS root mounting.
It is mountpoint=legacy that boots on this machine and mountpoint=/
that can't find init, with n
Now some high level information on how ZFS boot works and a little bit more
detailed information on how a root filesystem is chosen in ZFS case. The
information is applicable to recent versions of FreeBSD in head, stable/9
(including upcoming 9.2) and stable/8 (including 8.4).
- boot0-like stage
First, a note that below I try to reply not only to this specific message but to
the whole thread.
on 09/09/2013 04:02 J David said the following:
> After setting up a new machine to boot from a ZFS root using the 9.1
> install, it worked fine, but when the kernel & world was updated to
> releng/
On 09/09/2013 21:20, J David wrote:
On Sun, Sep 8, 2013 at 11:11 PM, Darren Pilgrim
wrote:
You can use zfs.root.mountfrom="zfs:data/root" in /boot/loader.conf
instead of an fstab entry.
That has been in loader.conf the whole time.
Mountpoint=legacy is required either way.
It isn't. There
On Sun, Sep 8, 2013 at 11:11 PM, Darren Pilgrim
wrote:
> You can use zfs.root.mountfrom="zfs:data/root" in /boot/loader.conf instead
> of an fstab entry.
That has been in loader.conf the whole time.
> Mountpoint=legacy is required either way.
It isn't. There is another machine right next to it
once you have it all working and understood have a look at the following
port ''usr/ports/sysutils/beadm'' It may make things a little easier to
manage in the future. In my experience BE's on zfs rock.
On 9 September 2013 02:02, J David wrote:
> After setting up a new machine to boot from a ZFS
On 9/8/2013 7:52 PM, J David wrote:
On Sun, Sep 8, 2013 at 10:22 PM, Darren Pilgrim
wrote:
Did you build and install new boot blocks?
Yes.
Oddly, setting:
zfs set mountpoint=legacy data/root (plus the appropriate fstab entry)
You can use zfs.root.mountfrom="zfs:data/root" in /boot/loader
On Sun, Sep 8, 2013 at 10:22 PM, Darren Pilgrim
wrote:
> Did you build and install new boot blocks?
Yes.
Oddly, setting:
zfs set mountpoint=legacy data/root (plus the appropriate fstab entry)
instead of
zfs set mountpoint=/ data/root
seems to produce a bootable system, although it absolutel
On 9/8/2013 6:02 PM, J David wrote:
Trying to mount root from zfs:data/root []…
Mounting from zfs:data/root failed with error 2: unknown file system.
Did you build and install new boot blocks?
___
freebsd-stable@freebsd.org mailing list
http://lists.
12 matches
Mail list logo
