Date: Mon, 20 Sep 2010 17:19:04 -0700 From: Aaron <drizzt321@gmail.com> To: Robert Bonomi <bonomi@mail.r-bonomi.com> Cc: freebsd-questions@freebsd.org Subject: Re: Problem running custom startup script at proper time Message-ID: <AANLkTinrrasdknoSn5cF1fJB_2pCG2EQZGbZYW5fK1Vx@mail.gmail.com> In-Reply-To: <201009201600.o8KG0iNk013372@mail.r-bonomi.com> References: <201009201600.o8KG0iNk013372@mail.r-bonomi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Sep 20, 2010 at 09:00, Robert Bonomi <bonomi@mail.r-bonomi.com> wro= te: >> From owner-freebsd-questions@freebsd.org =A0Sun Sep 19 16:37:49 2010 >> From: Aaron <drizzt321@gmail.com> >> Date: Sun, 19 Sep 2010 14:39:08 -0700 >> To: freebsd-questions@freebsd.org >> Subject: Re: Problem running custom startup script at proper time >> >> 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 :( > > How about just modifying the REQUIRE header on it to include =A0'gnop' > the sequencer that selects the order to run rc.d things in sorts based > on the REQUIRE/PROVIDES dependencies. > Nope, that didn't fix it. I even tried editing /etc/rc.d/zfs and included the gnop commands in the zfs_start(). The gnop still started up _after_ the ZFS in dmesg. However, I did figure it out after looking at the services that were starting up. There is apparent a 'zvol' script, which was the culprit. It was loading some ZFS stuff before the 'zfs' script. Once I set the 'gnop' script to startup before the 'zvol' script, worked like a charm. My zpool status now shows that it's using the gnop devices. Yay!! >> >> On Sun, Sep 19, 2010 at 14:04, Boris Samorodov <bsam@ipt.ru> wrote: >> > On Sun, 19 Sep 2010 13:55:41 -0700 Aaron wrote: >> >> On Sun, Sep 19, 2010 at 13:27, Boris Samorodov <bsam@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 :( >> >> =3DA0When I disable zfs auto-mount, and then run it manually after bo= ot, >> >> 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-unsubscribe@freebsd.= org" >> > > / >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinrrasdknoSn5cF1fJB_2pCG2EQZGbZYW5fK1Vx>