--On Sunday, September 19, 2010 2:39 PM -0700 Aaron <drizzt...@gmail.com> wrote:

Doh! Forgot to reply to the mailing list.


Nope, that didn't work either. Darn. Maybe I'll just have to modify
the /etc/rc.d/zfs script to run the for loop first :(

Do you load zfs.ko in loader.conf? I have built a few NAS systems on NanoBSD and found that I had to wait loading zfs until I had go the cache file copied from backup storage as I am using the diskless setup.

Could it be that you need to run your script before loading zfs.ko?

Cheers,
        Göran


On Sun, Sep 19, 2010 at 14:04, Boris Samorodov <b...@ipt.ru> wrote:
On Sun, 19 Sep 2010 13:55:41 -0700 Aaron wrote:
On Sun, Sep 19, 2010 at 13:27, Boris Samorodov <b...@ipt.ru> wrote:
> On Sun, 19 Sep 2010 12:40:52 -0700 Aaron wrote:
>
>> # PROVIDE: gnop
>
> What if you try "PROVIDE: disks" instead?

No good. I also tried the following in the gnop script:

# PROVIDE: gnop
# REQUIRE: mountcritlocal
# BEFORE: zfs

/etc/rc.d/geli has this:
-----
# PROVIDE: disks
# REQUIRE: initrandom
# KEYWORD: nojail
-----

Seems that that should work for you. If not I'm out of ideas
for now.

The services -r looks promising, but the dmesg is still the same :(
 When I disable zfs auto-mount, and then run it manually after boot,
it uses the .nop devices that were created correctly as it should.

EXCERPT services -r
/etc/rc.d/mdconfig
/etc/rc.d/mountcritlocal
/etc/rc.d/gnop
/etc/rc.d/zfs

--
WBR, Boris Samorodov (bsam)
Research Engineer, http://www.ipt.ru Telephone & Internet SP
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
"freebsd-questions-unsubscr...@freebsd.org"




_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to