previously, i had automount turned on in /etc/default/zfs (which still
is unchanged). But the filesystems no longer automount, thus forcing
me to wait and later manually "sudo zfs mount -a".
Oh, btw, i forgot to mention that this time, i has serious problems to
perform the update because the pool was unable to unmount prior to the
update. That is why i went back to an earlier OS configuration first,
unshared the network folders to allow for a safe pool export. then i
updated from there and imported the pool again.
On Thu, 2011-08-25 at 22:42 -0700, UbuntuNewbie wrote: > Hi all,
> tonight, my machine updated from the ppa.
> previously, i had automount turned on in /etc/default/zfs (which still > is unchanged). But the filesystems no longer automount, thus forcing > me to wait and later manually "sudo zfs mount -a".
> Can i change that? Is this intentional?
No. I started merging the upstream init script into the customized KQ init script, particularly the `zfs share -a` command.
It seems that some systems without an NFS service choked on the sharenfs property. The fix is to install the nfs-kernel-server package or unset the sharenfs property.
The nfs-kernel-server package is currently a suggestion. I'm thinking about whether to promote it to a recommendation or dependency, or to protect it with a ZFS_SHARE='n' in the /etc/defaults/zfs file.
A dud release was pushed to the staging area, but it failed testing and was not published to the regular PPA. Don't use the staging area unless you are willing to test for breakages.
> On Thu, 2011-08-25 at 22:42 -0700, UbuntuNewbie wrote:
> > Hi all,
> > tonight, my machine updated from the ppa.
> > previously, i had automount turned on in /etc/default/zfs (which still
> > is unchanged). But the filesystems no longer automount, thus forcing
> > me to wait and later manually "sudo zfs mount -a".
> > Can i change that? Is this intentional?
> No. I started merging the upstream init script into the customized KQ
> init script, particularly the `zfs share -a` command.
i see, ...makes sense
> It seems that some systems without an NFS service choked on the sharenfs
> property. The fix is to install the nfs-kernel-server package or unset
> the sharenfs property.
ok, i had indeed played with that, had the package and the property.
But since i failed at getting it to behave as expected, i reverted
both to the earlier state (unset property, package removed).
just checked that again, just to be certain.
> The nfs-kernel-server package is currently a suggestion. I'm thinking
> about whether to promote it to a recommendation or dependency, or to
> protect it with a ZFS_SHARE='n' in the /etc/defaults/zfs file.
> A dud release was pushed to the staging area, but it failed testing and
> was not published to the regular PPA. Don't use the staging area unless
> you are willing to test for breakages.
To be honest: i wouldnt even know, how to access the staging area. I
have only 0.6.0.31 and have to manually mount after boot, although the
default is set to 'yes'
On Sun, 2011-08-28 at 07:46 -0700, UbuntuNewbie wrote: > > The nfs-kernel-server package is currently a suggestion. I'm thinking > > about whether to promote it to a recommendation or dependency, or to > > protect it with a ZFS_SHARE='n' in the /etc/defaults/zfs file.
> > A dud release was pushed to the staging area, but it failed testing and > > was not published to the regular PPA. Don't use the staging area unless > > you are willing to test for breakages.
> To be honest: i wouldnt even know, how to access the staging area. I > have only 0.6.0.31 and have to manually mount after boot, although the > default is set to 'yes'
This comment was for people that are lurking on the list.
The staging area for ZFS should be hidden, but Launchpad currently requires a privileged account to change the setting.
> Anything else that i could/should check?
What happens if you run `/etc/init.d/zfs start` manually?
It sounds like 0.6.0.31 update could have a bug, but I haven't found it yet. Anybody that has an init problem should complain about it here to give me a hint for fixing it.
On 28 August 2011 17:38, Darik Horn <dajh...@vanadac.com> wrote:
> On Sun, 2011-08-28 at 07:46 -0700, UbuntuNewbie wrote:
>> Anything else that i could/should check?
> What happens if you run `/etc/init.d/zfs start` manually?
> It sounds like 0.6.0.31 update could have a bug, but I haven't found it > yet. Anybody that has an init problem should complain about it here to > give me a hint for fixing it.
> Provide system details, version numbers, etc.
Same here!
System: Linux ubuntu1104 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:02:55 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
I need to do more tests to narrow down, but sure seems like, if any
drive is having an issue, all zpools fail to automount. I had this
error the other day:
sd 1:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate
failed
So here's what I have noticed. I couldn't automount zfs zpools on
Lucid (using PPA install), then I noticed that error on that drive. I
pulled that drive, and then on reboot, automount worked again.
Interestingly, I have 3 zpools, and all of them would not automount.
with a swapped drive, automounts were working fine. Then, just for
fun, I put that drive back into my raidz2 pool, and sure enough, the
pools all failed to mount.
Oddly, I have this same drive in the pool, but not getting that error
in my logs. I also have the pool resilvered working fine. Going to
do some reboots and see if what happens now.
Greg
PS > THANK YOU!!! To all of you working on this project!! I know I am
not alone in thinking "I sure wish I had ZFS on my Linux servers!"
Running it on my home server now and loving it. I am installing two
new servers at a client in the next month or so, and I am just trying
to resist the urge to setup the data array's with ZFS! Its not quite
there yet, but I am very excited and looking forward to converting LVM
arrays!!
On Aug 29, 3:29 am, UbuntuNewbie <chessdo...@googlemail.com> wrote:
Ok, I guess it has nothing to do with my "one drive". I just tried
several different combinations of add/removing the separate zpools,
but automount doesn't work every time. Only once did it automount the
third pool while the 1st and 2nd were removed, but on a following
attempt, it didn't automount it.
Greg
On Aug 29, 11:37 am, Greg <rethe...@gmail.com> wrote:
> I need to do more tests to narrow down, but sure seems like, if any
> drive is having an issue, all zpools fail to automount. I had this
> error the other day:
> sd 1:0:0:0: [sdb] Add. Sense: Unrecovered read error - auto reallocate
> failed
> So here's what I have noticed. I couldn't automount zfs zpools on
> Lucid (using PPA install), then I noticed that error on that drive. I
> pulled that drive, and then on reboot, automount worked again.
> Interestingly, I have 3 zpools, and all of them would not automount.
> with a swapped drive, automounts were working fine. Then, just for
> fun, I put that drive back into my raidz2 pool, and sure enough, the
> pools all failed to mount.
> Oddly, I have this same drive in the pool, but not getting that error
> in my logs. I also have the pool resilvered working fine. Going to
> do some reboots and see if what happens now.
> Greg
> PS > THANK YOU!!! To all of you working on this project!! I know I am
> not alone in thinking "I sure wish I had ZFS on my Linux servers!"
> Running it on my home server now and loving it. I am installing two
> new servers at a client in the next month or so, and I am just trying
> to resist the urge to setup the data array's with ZFS! Its not quite
> there yet, but I am very excited and looking forward to converting LVM
> arrays!!
> On Aug 29, 3:29 am, UbuntuNewbie <chessdo...@googlemail.com> wrote:
> > > What happens if you run `/etc/init.d/zfs start` manually?
> > Works fine. Then no manual mount required. That is, what ran
> > automatically prior to the update.
> > > Provide system details, version numbers, etc.
> > Ubuntu natty 64 - version since problem update is 0.6.0.31 (zfs)
I managed to login as root fast enough this morning to get the following error messages when trying to 'zfs mount -a':
Unable to open /dev/zfs: No such file or directory. Verify that the ZFS module stack is loaded by running '/sbin/modprobe zfs'. Unable to open /dev/zfs: No such file or directory. Verify that the ZFS module stack is loaded by running '/sbin/modprobe zfs'.
I tried it several times and after about 30 seconds 'zfs mount -a' worked fine.
My guess is that the loading of modules is not finished when 'zfs mount -a' is run in the init.d scripts and thus the zfs filesystems do not get mounted.
Now that I think about it I remembered having problems with login when I entered my username and password too soon after startup in gdm, the zfs mount was not done at this point giving all sorts of strange error messages from Gnome...
I guess it could be necessary to defer mounting of zfs until all modules are loaded and also make eg. gdm dependent on the zfs startup in the init.d scripts. This would increase "time to login" tough, also for people how do not have the /home folder on zfs.
> My guess is that the loading of modules is not finished when 'zfs
> mount -a' is run in the init.d scripts and thus the zfs filesystems do
> not get mounted.
i had the same thought, that some parallizing on boot/init could have
created the problem. And having many cores plus booting from SSD could
make me more vulnerable to the problem than others.
Anyway. Already prior to this issue, i had login happening BEFORE all
zfs filesystems were mounted, thus some failures occurred simply
because i started programs too soon. In the meantime i always checked
for zfs before doing anything. But since the update in question, even
waiting did not help. :-(
>> My guess is that the loading of modules is not finished when 'zfs >> mount -a' is run in the init.d scripts and thus the zfs filesystems do >> not get mounted.
> i had the same thought, that some parallizing on boot/init could have > created the problem. And having many cores plus booting from SSD could > make me more vulnerable to the problem than others.
> Anyway. Already prior to this issue, i had login happening BEFORE all > zfs filesystems were mounted, thus some failures occurred simply > because i started programs too soon. In the meantime i always checked > for zfs before doing anything. But since the update in question, even > waiting did not help. :-(
> On 30 August 2011 12:06, UbuntuNewbie <chessdo...@googlemail.com> wrote: > > Nice observation, Andreas.
> >> My guess is that the loading of modules is not finished when 'zfs > >> mount -a' is run in the init.d scripts and thus the zfs filesystems do > >> not get mounted.
> > i had the same thought, that some parallizing on boot/init could have > > created the problem. And having many cores plus booting from SSD could > > make me more vulnerable to the problem than others.
> > Anyway. Already prior to this issue, i had login happening BEFORE all > > zfs filesystems were mounted, thus some failures occurred simply > > because i started programs too soon. In the meantime i always checked > > for zfs before doing anything. But since the update in question, even > > waiting did not help. :-(
> On 30 August 2011 12:06, UbuntuNewbie <chessdo...@googlemail.com > <mailto:chessdo...@googlemail.com>> wrote: > > Nice observation, Andreas.
> >> My guess is that the loading of modules is not finished when 'zfs > >> mount -a' is run in the init.d scripts and thus the zfs > filesystems do > >> not get mounted.
> > i had the same thought, that some parallizing on boot/init could > have > > created the problem. And having many cores plus booting from SSD > could > > make me more vulnerable to the problem than others.
> > Anyway. Already prior to this issue, i had login happening > BEFORE all > > zfs filesystems were mounted, thus some failures occurred simply > > because i started programs too soon. In the meantime i always > checked > > for zfs before doing anything. But since the update in question, > even > > waiting did not help. :-(
I'm working on some zfs (and related) upstart scripts. When I get them tuned well, would anyone like them to be uploaded? Most of the not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so anything except zfs itsself can just be tweaked to use those events to start it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS is started so I can run emergency logins on 4 5 6 if anything goes wrong, but won't be cleanly presented with a prompt until zfs is live to alleviate some of these zfs race issues). Also, zfs upstart script handles waiting for udev to settle and ensuring proper zfs module insertion, could be modified to run zpool clear before mounting in case devices didn't finish loading before module loaded, etc. I'm planning to ensure every obvious case is handled without breaking anything along the way.
On 31 August 2011 22:50, Felipe Scarel <fbsca...@gmail.com> wrote:
> I applied your patch and got a minor error: > # /etc/init.d/zfs start > Starting ZFS subsystem filesystems[: 86: 0: unexpected operator > zfs[20399]: Unable to mount zfs, waiting... > Changed to "let COUNT++" and to use bash instead of sh, seems fine.
I changed "COUNT=$(( COUNT + 1 ))" to "COUNT=$(( $COUNT + 1 ))", this should do the trick too...
On 31 August 2011 23:49, Christ Schlacta <aarc...@aarcane.org> wrote:
> I'm working on some zfs (and related) upstart scripts. When I get them > tuned well, would anyone like them to be uploaded? Most of the > not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so > anything except zfs itsself can just be tweaked to use those events to start > it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS > is started so I can run emergency logins on 4 5 6 if anything goes wrong, > but won't be cleanly presented with a prompt until zfs is live to alleviate > some of these zfs race issues). Also, zfs upstart script handles waiting > for udev to settle and ensuring proper zfs module insertion, could be > modified to run zpool clear before mounting in case devices didn't finish > loading before module loaded, etc. I'm planning to ensure every obvious > case is handled without breaking anything along the way.
Upstart scripts would be great, time permitting I am willing to test them.
I had a really hard time yesterday to try to generate a upstart zfs event from the init.d scripts so that gdm is only started if zfs is ready (for /home on zfs). Not sure if this even possible...
> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote: >> I'm working on some zfs (and related) upstart scripts. When I get them >> tuned well, would anyone like them to be uploaded? Most of the >> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so >> anything except zfs itsself can just be tweaked to use those events to start >> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS >> is started so I can run emergency logins on 4 5 6 if anything goes wrong, >> but won't be cleanly presented with a prompt until zfs is live to alleviate >> some of these zfs race issues). Also, zfs upstart script handles waiting >> for udev to settle and ensuring proper zfs module insertion, could be >> modified to run zpool clear before mounting in case devices didn't finish >> loading before module loaded, etc. I'm planning to ensure every obvious >> case is handled without breaking anything along the way. > Upstart scripts would be great, time permitting I am willing to test them.
> I had a really hard time yesterday to try to generate a upstart zfs > event from the init.d scripts so that gdm is only started if zfs is > ready (for /home on zfs). Not sure if this even possible...
> Andi
I have some stringent requirements for zfs to be up before a number of services. I start zfs by default on 2345, so most core stuff is settled, then start everything else on zfs started, so setting gdm to start on started zfs, you'll be good to go. I've been researching all the start on clauses, and all the mechanisms to make stuff work together nicely, and I think I've got most of it in place. I just need to know what ZFS needs to do aside from modprobe zfs and zfs mount -a
I'd love to use a script if you have time to make one. I'll put it on
my home server right away and help test for you if you like. Is it
possible to have it start on 12345? I suppose you wouldn't need it on
1 normally, or maybe not *want* it to on 1, and if you were to boot
into single user, you could manually mount zfs anyway, right?
Also, I am assuming we would want zfs to auto mount without the
scripts in the future? right? And that zfs should be mounting as
early as possible, before any services get going. (I am thinking
mysql, pgsql, apache, samba, that kind of stuff)
Thanks guys!
Greg
On Aug 31, 10:57 pm, Christ Schlacta <aarc...@aarcane.org> wrote:
> > On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote:
> >> I'm working on some zfs (and related) upstart scripts. When I get them
> >> tuned well, would anyone like them to be uploaded? Most of the
> >> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so
> >> anything except zfs itsself can just be tweaked to use those events to start
> >> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS
> >> is started so I can run emergency logins on 4 5 6 if anything goes wrong,
> >> but won't be cleanly presented with a prompt until zfs is live to alleviate
> >> some of these zfs race issues). Also, zfs upstart script handles waiting
> >> for udev to settle and ensuring proper zfs module insertion, could be
> >> modified to run zpool clear before mounting in case devices didn't finish
> >> loading before module loaded, etc. I'm planning to ensure every obvious
> >> case is handled without breaking anything along the way.
> > Upstart scripts would be great, time permitting I am willing to test them.
> > I had a really hard time yesterday to try to generate a upstart zfs
> > event from the init.d scripts so that gdm is only started if zfs is
> > ready (for /home on zfs). Not sure if this even possible...
> > Andi
> I have some stringent requirements for zfs to be up before a number of
> services. I start zfs by default on 2345, so most core stuff is
> settled, then start everything else on zfs started, so setting gdm to
> start on started zfs, you'll be good to go. I've been researching all
> the start on clauses, and all the mechanisms to make stuff work together
> nicely, and I think I've got most of it in place. I just need to know
> what ZFS needs to do aside from modprobe zfs and zfs mount -a
The runlevels are strange in linux. Linux starts in a base runlevel, not sure what it is called, but it does some basic stuff then switches to runlevel 2, 3, 4, or 5 depending on which distro you're using. most modern distros use 2, but 2, 3, 4, and 5 are identical for most configurations and 3, 4, and 5 are unused.
Once in runlevel 2, init starts running user defined scripts including but not limited to scripts for non-root filesystems, services, etc. Sysv init lets you specify the start order by prefixing init scripts with an integer. an application 00_mountall will run before 20_httpd and 20_mysql, which can in theory run together (but usually don't) and will NEVER run BEFORE 21_ldap, for example.
Upstart is a bit different. upstart lets you specify ANY service to depend on any other. If you need mysql started before apache, then you can specify, in your apache config file, "start on started mysql", or if you only ever need mysql when apache is running, you might put "start on starting apache" in your mysql config file. The dependencies can go either way, and which is right obviously depends on your situation.
Which brings us to ZFS. We have three conditions around ZFS which matter significantly. "Do we need this to run before ZFS" "Does ZFS need this to run before zfs can start" and "Do we need to run this after ZFS". These are "start on" conditions, and are intended to be user-defined. Picking good defaults is of course important, but no default will provide 100% of the people the perfect answer. Using the upstart starting and started conditions allow us to handle these. for the first condition:
Do we need this to run before ZFS? in the upstart config for that job, we enter "start on starting zfs" this will ensure that before ZFS is started, this job has started
for the second: Does ZFS need this to run before ZFS can start? In the upstart config for ZFS we can enter "start on starting servicename", and make sure something starts our other service. for the last, "do we need to run this after zfs?" we simply add "start on started zfs" to the other service's config and it starts immediately when ZFS starts.
I'm off to restart my system a few times to make sure ZFS is starting properly, then I'll make a few minor tweaks as needed and post the upstart script to the list.
> I'd love to use a script if you have time to make one. I'll put it on > my home server right away and help test for you if you like. Is it > possible to have it start on 12345? I suppose you wouldn't need it on > 1 normally, or maybe not *want* it to on 1, and if you were to boot > into single user, you could manually mount zfs anyway, right?
> Also, I am assuming we would want zfs to auto mount without the > scripts in the future? right? And that zfs should be mounting as > early as possible, before any services get going. (I am thinking > mysql, pgsql, apache, samba, that kind of stuff)
> Thanks guys!
> Greg
> On Aug 31, 10:57 pm, Christ Schlacta<aarc...@aarcane.org> wrote: >> On 8/31/2011 22:40, Andreas Neustifter wrote:
>>> Hi Christ! >>> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote: >>>> I'm working on some zfs (and related) upstart scripts. When I get them >>>> tuned well, would anyone like them to be uploaded? Most of the >>>> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so >>>> anything except zfs itsself can just be tweaked to use those events to start >>>> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS >>>> is started so I can run emergency logins on 4 5 6 if anything goes wrong, >>>> but won't be cleanly presented with a prompt until zfs is live to alleviate >>>> some of these zfs race issues). Also, zfs upstart script handles waiting >>>> for udev to settle and ensuring proper zfs module insertion, could be >>>> modified to run zpool clear before mounting in case devices didn't finish >>>> loading before module loaded, etc. I'm planning to ensure every obvious >>>> case is handled without breaking anything along the way. >>> Upstart scripts would be great, time permitting I am willing to test them. >>> I had a really hard time yesterday to try to generate a upstart zfs >>> event from the init.d scripts so that gdm is only started if zfs is >>> ready (for /home on zfs). Not sure if this even possible... >>> Andi >> I have some stringent requirements for zfs to be up before a number of >> services. I start zfs by default on 2345, so most core stuff is >> settled, then start everything else on zfs started, so setting gdm to >> start on started zfs, you'll be good to go. I've been researching all >> the start on clauses, and all the mechanisms to make stuff work together >> nicely, and I think I've got most of it in place. I just need to know >> what ZFS needs to do aside from modprobe zfs and zfs mount -a
Oh wow! I had no idea! One day I saw "upstart" mentioned in Ubuntu
and I had no idea it was a whole new startup system! Hahaha! I kept
thinking, "whats the big deal, I'll start this how I am used to?"
Thanks for such a great description, gonna do some playing with that
now. Sounds way more useful with those dependencies. I just never
took the time to lookup what they were talking about, and now the name
"upstart" make so much more sense. LOL!
Thanks!
Greg
On Sep 1, 11:06 am, Christ Schlacta <aarc...@aarcane.org> wrote:
> The runlevels are strange in linux. Linux starts in a base runlevel,
> not sure what it is called, but it does some basic stuff then switches
> to runlevel 2, 3, 4, or 5 depending on which distro you're using. most
> modern distros use 2, but 2, 3, 4, and 5 are identical for most
> configurations and 3, 4, and 5 are unused.
> Once in runlevel 2, init starts running user defined scripts including
> but not limited to scripts for non-root filesystems, services, etc.
> Sysv init lets you specify the start order by prefixing init scripts
> with an integer. an application 00_mountall will run before 20_httpd
> and 20_mysql, which can in theory run together (but usually don't) and
> will NEVER run BEFORE 21_ldap, for example.
> Upstart is a bit different. upstart lets you specify ANY service to
> depend on any other. If you need mysql started before apache, then you
> can specify, in your apache config file, "start on started mysql", or if
> you only ever need mysql when apache is running, you might put "start on
> starting apache" in your mysql config file. The dependencies can go
> either way, and which is right obviously depends on your situation.
> Which brings us to ZFS. We have three conditions around ZFS which
> matter significantly. "Do we need this to run before ZFS" "Does ZFS
> need this to run before zfs can start" and "Do we need to run this after
> ZFS". These are "start on" conditions, and are intended to be
> user-defined. Picking good defaults is of course important, but no
> default will provide 100% of the people the perfect answer.
> Using the upstart starting and started conditions allow us to handle
> these. for the first condition:
> Do we need this to run before ZFS? in the upstart config for that job,
> we enter "start on starting zfs" this will ensure that before ZFS is
> started, this job has started
> for the second:
> Does ZFS need this to run before ZFS can start? In the upstart config
> for ZFS we can enter "start on starting servicename", and make sure
> something starts our other service.
> for the last, "do we need to run this after zfs?" we simply add "start
> on started zfs" to the other service's config and it starts immediately
> when ZFS starts.
> I'm off to restart my system a few times to make sure ZFS is starting
> properly, then I'll make a few minor tweaks as needed and post the
> upstart script to the list.
> On 9/1/2011 09:40, Greg wrote:
> > I'd love to use a script if you have time to make one. I'll put it on
> > my home server right away and help test for you if you like. Is it
> > possible to have it start on 12345? I suppose you wouldn't need it on
> > 1 normally, or maybe not *want* it to on 1, and if you were to boot
> > into single user, you could manually mount zfs anyway, right?
> > Also, I am assuming we would want zfs to auto mount without the
> > scripts in the future? right? And that zfs should be mounting as
> > early as possible, before any services get going. (I am thinking
> > mysql, pgsql, apache, samba, that kind of stuff)
> > Thanks guys!
> > Greg
> > On Aug 31, 10:57 pm, Christ Schlacta<aarc...@aarcane.org> wrote:
> >> On 8/31/2011 22:40, Andreas Neustifter wrote:
> >>> Hi Christ!
> >>> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote:
> >>>> I'm working on some zfs (and related) upstart scripts. When I get them
> >>>> tuned well, would anyone like them to be uploaded? Most of the
> >>>> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so
> >>>> anything except zfs itsself can just be tweaked to use those events to start
> >>>> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS
> >>>> is started so I can run emergency logins on 4 5 6 if anything goes wrong,
> >>>> but won't be cleanly presented with a prompt until zfs is live to alleviate
> >>>> some of these zfs race issues). Also, zfs upstart script handles waiting
> >>>> for udev to settle and ensuring proper zfs module insertion, could be
> >>>> modified to run zpool clear before mounting in case devices didn't finish
> >>>> loading before module loaded, etc. I'm planning to ensure every obvious
> >>>> case is handled without breaking anything along the way.
> >>> Upstart scripts would be great, time permitting I am willing to test them.
> >>> I had a really hard time yesterday to try to generate a upstart zfs
> >>> event from the init.d scripts so that gdm is only started if zfs is
> >>> ready (for /home on zfs). Not sure if this even possible...
> >>> Andi
> >> I have some stringent requirements for zfs to be up before a number of
> >> services. I start zfs by default on 2345, so most core stuff is
> >> settled, then start everything else on zfs started, so setting gdm to
> >> start on started zfs, you'll be good to go. I've been researching all
> >> the start on clauses, and all the mechanisms to make stuff work together
> >> nicely, and I think I've got most of it in place. I just need to know
> >> what ZFS needs to do aside from modprobe zfs and zfs mount -a
Attached is zfs-init.tar. un-tar it wherever, it will create zfs-init/ . inside zfs-init are a readme file, and a directory structure that mirrors / on a ubuntu system. copy the files to their intended location, and read the readme file to test. (sudo cp -r zfs-init/./ / should work, but is ill advised.)
read etc/default/zfs carefully. I added a new option to it.
please provide feedback if anything needs to be changed, or if I've done anything wrong. I used the existing zfs init script as a template to start zfs.
> Oh wow! I had no idea! One day I saw "upstart" mentioned in Ubuntu > and I had no idea it was a whole new startup system! Hahaha! I kept > thinking, "whats the big deal, I'll start this how I am used to?" > Thanks for such a great description, gonna do some playing with that > now. Sounds way more useful with those dependencies. I just never > took the time to lookup what they were talking about, and now the name > "upstart" make so much more sense. LOL!
> Thanks!
> Greg
> On Sep 1, 11:06 am, Christ Schlacta<aarc...@aarcane.org> wrote: >> The runlevels are strange in linux. Linux starts in a base runlevel, >> not sure what it is called, but it does some basic stuff then switches >> to runlevel 2, 3, 4, or 5 depending on which distro you're using. most >> modern distros use 2, but 2, 3, 4, and 5 are identical for most >> configurations and 3, 4, and 5 are unused.
>> Once in runlevel 2, init starts running user defined scripts including >> but not limited to scripts for non-root filesystems, services, etc. >> Sysv init lets you specify the start order by prefixing init scripts >> with an integer. an application 00_mountall will run before 20_httpd >> and 20_mysql, which can in theory run together (but usually don't) and >> will NEVER run BEFORE 21_ldap, for example.
>> Upstart is a bit different. upstart lets you specify ANY service to >> depend on any other. If you need mysql started before apache, then you >> can specify, in your apache config file, "start on started mysql", or if >> you only ever need mysql when apache is running, you might put "start on >> starting apache" in your mysql config file. The dependencies can go >> either way, and which is right obviously depends on your situation.
>> Which brings us to ZFS. We have three conditions around ZFS which >> matter significantly. "Do we need this to run before ZFS" "Does ZFS >> need this to run before zfs can start" and "Do we need to run this after >> ZFS". These are "start on" conditions, and are intended to be >> user-defined. Picking good defaults is of course important, but no >> default will provide 100% of the people the perfect answer. >> Using the upstart starting and started conditions allow us to handle >> these. for the first condition:
>> Do we need this to run before ZFS? in the upstart config for that job, >> we enter "start on starting zfs" this will ensure that before ZFS is >> started, this job has started
>> for the second: >> Does ZFS need this to run before ZFS can start? In the upstart config >> for ZFS we can enter "start on starting servicename", and make sure >> something starts our other service. >> for the last, "do we need to run this after zfs?" we simply add "start >> on started zfs" to the other service's config and it starts immediately >> when ZFS starts.
>> I'm off to restart my system a few times to make sure ZFS is starting >> properly, then I'll make a few minor tweaks as needed and post the >> upstart script to the list.
>> On 9/1/2011 09:40, Greg wrote:
>>> I'd love to use a script if you have time to make one. I'll put it on >>> my home server right away and help test for you if you like. Is it >>> possible to have it start on 12345? I suppose you wouldn't need it on >>> 1 normally, or maybe not *want* it to on 1, and if you were to boot >>> into single user, you could manually mount zfs anyway, right? >>> Also, I am assuming we would want zfs to auto mount without the >>> scripts in the future? right? And that zfs should be mounting as >>> early as possible, before any services get going. (I am thinking >>> mysql, pgsql, apache, samba, that kind of stuff) >>> Thanks guys! >>> Greg >>> On Aug 31, 10:57 pm, Christ Schlacta<aarc...@aarcane.org> wrote: >>>> On 8/31/2011 22:40, Andreas Neustifter wrote: >>>>> Hi Christ! >>>>> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote: >>>>>> I'm working on some zfs (and related) upstart scripts. When I get them >>>>>> tuned well, would anyone like them to be uploaded? Most of the >>>>>> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so >>>>>> anything except zfs itsself can just be tweaked to use those events to start >>>>>> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS >>>>>> is started so I can run emergency logins on 4 5 6 if anything goes wrong, >>>>>> but won't be cleanly presented with a prompt until zfs is live to alleviate >>>>>> some of these zfs race issues). Also, zfs upstart script handles waiting >>>>>> for udev to settle and ensuring proper zfs module insertion, could be >>>>>> modified to run zpool clear before mounting in case devices didn't finish >>>>>> loading before module loaded, etc. I'm planning to ensure every obvious >>>>>> case is handled without breaking anything along the way. >>>>> Upstart scripts would be great, time permitting I am willing to test them. >>>>> I had a really hard time yesterday to try to generate a upstart zfs >>>>> event from the init.d scripts so that gdm is only started if zfs is >>>>> ready (for /home on zfs). Not sure if this even possible... >>>>> Andi >>>> I have some stringent requirements for zfs to be up before a number of >>>> services. I start zfs by default on 2345, so most core stuff is >>>> settled, then start everything else on zfs started, so setting gdm to >>>> start on started zfs, you'll be good to go. I've been researching all >>>> the start on clauses, and all the mechanisms to make stuff work together >>>> nicely, and I think I've got most of it in place. I just need to know >>>> what ZFS needs to do aside from modprobe zfs and zfs mount -a
We live now in the age of computers, and in this age is contained the age of linux. I've found my equilibrium with linux, at long last. I love linux, and could never live without it. Linux runs my servers, my embedded systems, and a bunch of other stuff, but Linux, sadly, will never be my primary desktop OS. I couldn't live without the games that aren't available on linux, and need to use windows-only apps for school, and so, I keep windows 7 on my desktop. and it's pretty, and it's stable, and it's protected by linux on my firewall. I'm content.
Sure, windows 7 may be lacking in some of the features I love (multiple virtual desktops, pretty 3D desktop, live wallpapers, a solid console underpinning, and a metric asston of security and customization features too numerous to count), but I can get the important ones (solid console underpinning and an asston of security) using available windows products like putty, which keep me in touch with my linux roots.
The age of Linux truly IS now, it's just that Linux will never truly be the universal desktop OS like windows is now. (at least in the forseeable future)
> Oh wow! I had no idea! One day I saw "upstart" mentioned in Ubuntu > and I had no idea it was a whole new startup system! Hahaha! I kept > thinking, "whats the big deal, I'll start this how I am used to?" > Thanks for such a great description, gonna do some playing with that > now. Sounds way more useful with those dependencies. I just never > took the time to lookup what they were talking about, and now the name > "upstart" make so much more sense. LOL!
> Thanks!
> Greg
> On Sep 1, 11:06 am, Christ Schlacta<aarc...@aarcane.org> wrote: >> The runlevels are strange in linux. Linux starts in a base runlevel, >> not sure what it is called, but it does some basic stuff then switches >> to runlevel 2, 3, 4, or 5 depending on which distro you're using. most >> modern distros use 2, but 2, 3, 4, and 5 are identical for most >> configurations and 3, 4, and 5 are unused.
>> Once in runlevel 2, init starts running user defined scripts including >> but not limited to scripts for non-root filesystems, services, etc. >> Sysv init lets you specify the start order by prefixing init scripts >> with an integer. an application 00_mountall will run before 20_httpd >> and 20_mysql, which can in theory run together (but usually don't) and >> will NEVER run BEFORE 21_ldap, for example.
>> Upstart is a bit different. upstart lets you specify ANY service to >> depend on any other. If you need mysql started before apache, then you >> can specify, in your apache config file, "start on started mysql", or if >> you only ever need mysql when apache is running, you might put "start on >> starting apache" in your mysql config file. The dependencies can go >> either way, and which is right obviously depends on your situation.
>> Which brings us to ZFS. We have three conditions around ZFS which >> matter significantly. "Do we need this to run before ZFS" "Does ZFS >> need this to run before zfs can start" and "Do we need to run this after >> ZFS". These are "start on" conditions, and are intended to be >> user-defined. Picking good defaults is of course important, but no >> default will provide 100% of the people the perfect answer. >> Using the upstart starting and started conditions allow us to handle >> these. for the first condition:
>> Do we need this to run before ZFS? in the upstart config for that job, >> we enter "start on starting zfs" this will ensure that before ZFS is >> started, this job has started
>> for the second: >> Does ZFS need this to run before ZFS can start? In the upstart config >> for ZFS we can enter "start on starting servicename", and make sure >> something starts our other service. >> for the last, "do we need to run this after zfs?" we simply add "start >> on started zfs" to the other service's config and it starts immediately >> when ZFS starts.
>> I'm off to restart my system a few times to make sure ZFS is starting >> properly, then I'll make a few minor tweaks as needed and post the >> upstart script to the list.
>> On 9/1/2011 09:40, Greg wrote:
>>> I'd love to use a script if you have time to make one. I'll put it on >>> my home server right away and help test for you if you like. Is it >>> possible to have it start on 12345? I suppose you wouldn't need it on >>> 1 normally, or maybe not *want* it to on 1, and if you were to boot >>> into single user, you could manually mount zfs anyway, right? >>> Also, I am assuming we would want zfs to auto mount without the >>> scripts in the future? right? And that zfs should be mounting as >>> early as possible, before any services get going. (I am thinking >>> mysql, pgsql, apache, samba, that kind of stuff) >>> Thanks guys! >>> Greg >>> On Aug 31, 10:57 pm, Christ Schlacta<aarc...@aarcane.org> wrote: >>>> On 8/31/2011 22:40, Andreas Neustifter wrote: >>>>> Hi Christ! >>>>> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote: >>>>>> I'm working on some zfs (and related) upstart scripts. When I get them >>>>>> tuned well, would anyone like them to be uploaded? Most of the >>>>>> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so >>>>>> anything except zfs itsself can just be tweaked to use those events to start >>>>>> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS >>>>>> is started so I can run emergency logins on 4 5 6 if anything goes wrong, >>>>>> but won't be cleanly presented with a prompt until zfs is live to alleviate >>>>>> some of these zfs race issues). Also, zfs upstart script handles waiting >>>>>> for udev to settle and ensuring proper zfs module insertion, could be >>>>>> modified to run zpool clear before mounting in case devices didn't finish >>>>>> loading before module loaded, etc. I'm planning to ensure every obvious >>>>>> case is handled without breaking anything along the way. >>>>> Upstart scripts would be great, time permitting I am willing to test them. >>>>> I had a really hard time yesterday to try to generate a upstart zfs >>>>> event from the init.d scripts so that gdm is only started if zfs is >>>>> ready (for /home on zfs). Not sure if this even possible... >>>>> Andi >>>> I have some stringent requirements for zfs to be up before a number of >>>> services. I start zfs by default on 2345, so most core stuff is >>>> settled, then start everything else on zfs started, so setting gdm to >>>> start on started zfs, you'll be good to go. I've been researching all >>>> the start on clauses, and all the mechanisms to make stuff work together >>>> nicely, and I think I've got most of it in place. I just need to know >>>> what ZFS needs to do aside from modprobe zfs and zfs mount -a
I suppose that's why they are not mounting if the ZFS module is
dependent on SPL, and SPL is not loading. Not sure what to do with
this one.
Just a quick note about my sys, using Ubuntu Lucid x64 on an almost
clean load of the system of 10.04.3. Using the PPA install.
Greg
On Sep 1, 1:25 pm, Christ Schlacta <aarc...@aarcane.org> wrote:
> Attached is zfs-init.tar. un-tar it wherever, it will create zfs-init/
> . inside zfs-init are a readme file, and a directory structure that
> mirrors / on a ubuntu system. copy the files to their intended
> location, and read the readme file to test. (sudo cp -r zfs-init/./ /
> should work, but is ill advised.)
> read etc/default/zfs carefully. I added a new option to it.
> please provide feedback if anything needs to be changed, or if I've done
> anything wrong. I used the existing zfs init script as a template to
> start zfs.
> On 9/1/2011 13:12, Greg wrote:
> > Oh wow! I had no idea! One day I saw "upstart" mentioned in Ubuntu
> > and I had no idea it was a whole new startup system! Hahaha! I kept
> > thinking, "whats the big deal, I'll start this how I am used to?"
> > Thanks for such a great description, gonna do some playing with that
> > now. Sounds way more useful with those dependencies. I just never
> > took the time to lookup what they were talking about, and now the name
> > "upstart" make so much more sense. LOL!
> > Thanks!
> > Greg
> > On Sep 1, 11:06 am, Christ Schlacta<aarc...@aarcane.org> wrote:
> >> The runlevels are strange in linux. Linux starts in a base runlevel,
> >> not sure what it is called, but it does some basic stuff then switches
> >> to runlevel 2, 3, 4, or 5 depending on which distro you're using. most
> >> modern distros use 2, but 2, 3, 4, and 5 are identical for most
> >> configurations and 3, 4, and 5 are unused.
> >> Once in runlevel 2, init starts running user defined scripts including
> >> but not limited to scripts for non-root filesystems, services, etc.
> >> Sysv init lets you specify the start order by prefixing init scripts
> >> with an integer. an application 00_mountall will run before 20_httpd
> >> and 20_mysql, which can in theory run together (but usually don't) and
> >> will NEVER run BEFORE 21_ldap, for example.
> >> Upstart is a bit different. upstart lets you specify ANY service to
> >> depend on any other. If you need mysql started before apache, then you
> >> can specify, in your apache config file, "start on started mysql", or if
> >> you only ever need mysql when apache is running, you might put "start on
> >> starting apache" in your mysql config file. The dependencies can go
> >> either way, and which is right obviously depends on your situation.
> >> Which brings us to ZFS. We have three conditions around ZFS which
> >> matter significantly. "Do we need this to run before ZFS" "Does ZFS
> >> need this to run before zfs can start" and "Do we need to run this after
> >> ZFS". These are "start on" conditions, and are intended to be
> >> user-defined. Picking good defaults is of course important, but no
> >> default will provide 100% of the people the perfect answer.
> >> Using the upstart starting and started conditions allow us to handle
> >> these. for the first condition:
> >> Do we need this to run before ZFS? in the upstart config for that job,
> >> we enter "start on starting zfs" this will ensure that before ZFS is
> >> started, this job has started
> >> for the second:
> >> Does ZFS need this to run before ZFS can start? In the upstart config
> >> for ZFS we can enter "start on starting servicename", and make sure
> >> something starts our other service.
> >> for the last, "do we need to run this after zfs?" we simply add "start
> >> on started zfs" to the other service's config and it starts immediately
> >> when ZFS starts.
> >> I'm off to restart my system a few times to make sure ZFS is starting
> >> properly, then I'll make a few minor tweaks as needed and post the
> >> upstart script to the list.
> >> On 9/1/2011 09:40, Greg wrote:
> >>> I'd love to use a script if you have time to make one. I'll put it on
> >>> my home server right away and help test for you if you like. Is it
> >>> possible to have it start on 12345? I suppose you wouldn't need it on
> >>> 1 normally, or maybe not *want* it to on 1, and if you were to boot
> >>> into single user, you could manually mount zfs anyway, right?
> >>> Also, I am assuming we would want zfs to auto mount without the
> >>> scripts in the future? right? And that zfs should be mounting as
> >>> early as possible, before any services get going. (I am thinking
> >>> mysql, pgsql, apache, samba, that kind of stuff)
> >>> Thanks guys!
> >>> Greg
> >>> On Aug 31, 10:57 pm, Christ Schlacta<aarc...@aarcane.org> wrote:
> >>>> On 8/31/2011 22:40, Andreas Neustifter wrote:
> >>>>> Hi Christ!
> >>>>> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote:
> >>>>>> I'm working on some zfs (and related) upstart scripts. When I get them
> >>>>>> tuned well, would anyone like them to be uploaded? Most of the
> >>>>>> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so
> >>>>>> anything except zfs itsself can just be tweaked to use those events to start
> >>>>>> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS
> >>>>>> is started so I can run emergency logins on 4 5 6 if anything goes wrong,
> >>>>>> but won't be cleanly presented with a prompt until zfs is live to alleviate
> >>>>>> some of these zfs race issues). Also, zfs upstart script handles waiting
> >>>>>> for udev to settle and ensuring proper zfs module insertion, could be
> >>>>>> modified to run zpool clear before mounting in case devices didn't finish
> >>>>>> loading before module loaded, etc. I'm planning to ensure every obvious
> >>>>>> case is handled without breaking anything along the way.
> >>>>> Upstart scripts would be great, time permitting I am willing to test them.
> >>>>> I had a really hard time yesterday to try to generate a upstart zfs
> >>>>> event from the init.d scripts so that gdm is only started if zfs is
> >>>>> ready (for /home on zfs). Not sure if this even possible...
> >>>>> Andi
> >>>> I have some stringent requirements for zfs to be up before a number of
> >>>> services. I start zfs by default on 2345, so most core stuff is
> >>>> settled, then start everything else on zfs started, so setting gdm to
> >>>> start on started zfs, you'll be good to go. I've been researching all
> >>>> the start on clauses, and all the mechanisms to make stuff work together
> >>>> nicely, and I think I've got most of it in place. I just need to know
> >>>> what ZFS needs to do aside from modprobe zfs and zfs mount -a
then reboot your computer. if SPL is loading, then you should import, export, import, export, then import again each of your pools (use import -N to skip mounting to speed the process up)
> I suppose that's why they are not mounting if the ZFS module is > dependent on SPL, and SPL is not loading. Not sure what to do with > this one. > Just a quick note about my sys, using Ubuntu Lucid x64 on an almost > clean load of the system of 10.04.3. Using the PPA install.
> Greg
> On Sep 1, 1:25 pm, Christ Schlacta<aarc...@aarcane.org> wrote: >> Attached is zfs-init.tar. un-tar it wherever, it will create zfs-init/ >> . inside zfs-init are a readme file, and a directory structure that >> mirrors / on a ubuntu system. copy the files to their intended >> location, and read the readme file to test. (sudo cp -r zfs-init/./ / >> should work, but is ill advised.)
>> read etc/default/zfs carefully. I added a new option to it.
>> please provide feedback if anything needs to be changed, or if I've done >> anything wrong. I used the existing zfs init script as a template to >> start zfs.
>> On 9/1/2011 13:12, Greg wrote:
>>> Oh wow! I had no idea! One day I saw "upstart" mentioned in Ubuntu >>> and I had no idea it was a whole new startup system! Hahaha! I kept >>> thinking, "whats the big deal, I'll start this how I am used to?" >>> Thanks for such a great description, gonna do some playing with that >>> now. Sounds way more useful with those dependencies. I just never >>> took the time to lookup what they were talking about, and now the name >>> "upstart" make so much more sense. LOL! >>> Thanks! >>> Greg >>> On Sep 1, 11:06 am, Christ Schlacta<aarc...@aarcane.org> wrote: >>>> The runlevels are strange in linux. Linux starts in a base runlevel, >>>> not sure what it is called, but it does some basic stuff then switches >>>> to runlevel 2, 3, 4, or 5 depending on which distro you're using. most >>>> modern distros use 2, but 2, 3, 4, and 5 are identical for most >>>> configurations and 3, 4, and 5 are unused. >>>> Once in runlevel 2, init starts running user defined scripts including >>>> but not limited to scripts for non-root filesystems, services, etc. >>>> Sysv init lets you specify the start order by prefixing init scripts >>>> with an integer. an application 00_mountall will run before 20_httpd >>>> and 20_mysql, which can in theory run together (but usually don't) and >>>> will NEVER run BEFORE 21_ldap, for example. >>>> Upstart is a bit different. upstart lets you specify ANY service to >>>> depend on any other. If you need mysql started before apache, then you >>>> can specify, in your apache config file, "start on started mysql", or if >>>> you only ever need mysql when apache is running, you might put "start on >>>> starting apache" in your mysql config file. The dependencies can go >>>> either way, and which is right obviously depends on your situation. >>>> Which brings us to ZFS. We have three conditions around ZFS which >>>> matter significantly. "Do we need this to run before ZFS" "Does ZFS >>>> need this to run before zfs can start" and "Do we need to run this after >>>> ZFS". These are "start on" conditions, and are intended to be >>>> user-defined. Picking good defaults is of course important, but no >>>> default will provide 100% of the people the perfect answer. >>>> Using the upstart starting and started conditions allow us to handle >>>> these. for the first condition: >>>> Do we need this to run before ZFS? in the upstart config for that job, >>>> we enter "start on starting zfs" this will ensure that before ZFS is >>>> started, this job has started >>>> for the second: >>>> Does ZFS need this to run before ZFS can start? In the upstart config >>>> for ZFS we can enter "start on starting servicename", and make sure >>>> something starts our other service. >>>> for the last, "do we need to run this after zfs?" we simply add "start >>>> on started zfs" to the other service's config and it starts immediately >>>> when ZFS starts. >>>> I'm off to restart my system a few times to make sure ZFS is starting >>>> properly, then I'll make a few minor tweaks as needed and post the >>>> upstart script to the list. >>>> On 9/1/2011 09:40, Greg wrote: >>>>> I'd love to use a script if you have time to make one. I'll put it on >>>>> my home server right away and help test for you if you like. Is it >>>>> possible to have it start on 12345? I suppose you wouldn't need it on >>>>> 1 normally, or maybe not *want* it to on 1, and if you were to boot >>>>> into single user, you could manually mount zfs anyway, right? >>>>> Also, I am assuming we would want zfs to auto mount without the >>>>> scripts in the future? right? And that zfs should be mounting as >>>>> early as possible, before any services get going. (I am thinking >>>>> mysql, pgsql, apache, samba, that kind of stuff) >>>>> Thanks guys! >>>>> Greg >>>>> On Aug 31, 10:57 pm, Christ Schlacta<aarc...@aarcane.org> wrote: >>>>>> On 8/31/2011 22:40, Andreas Neustifter wrote: >>>>>>> Hi Christ! >>>>>>> On 31 August 2011 23:49, Christ Schlacta<aarc...@aarcane.org> wrote: >>>>>>>> I'm working on some zfs (and related) upstart scripts. When I get them >>>>>>>> tuned well, would anyone like them to be uploaded? Most of the >>>>>>>> not-quite-zfs scripts work on "started zfs" and "stopping zfs" events, so >>>>>>>> anything except zfs itsself can just be tweaked to use those events to start >>>>>>>> it. (I plan to start tty 4, 5, 6 regularly, but 1, 2, and 3 only when ZFS >>>>>>>> is started so I can run emergency logins on 4 5 6 if anything goes wrong, >>>>>>>> but won't be cleanly presented with a prompt until zfs is live to alleviate >>>>>>>> some of these zfs race issues). Also, zfs upstart script handles waiting >>>>>>>> for udev to settle and ensuring proper zfs module insertion, could be >>>>>>>> modified to run zpool clear before mounting in case devices didn't finish >>>>>>>> loading before module loaded, etc. I'm planning to ensure every obvious >>>>>>>> case is handled without breaking anything along the way. >>>>>>> Upstart scripts would be great, time permitting I am willing to test them. >>>>>>> I had a really hard time yesterday to try to generate a upstart zfs >>>>>>> event from the init.d scripts so that gdm is only started if zfs is >>>>>>> ready (for /home on zfs). Not sure if this even possible... >>>>>>> Andi >>>>>> I have some stringent requirements for zfs to be up before a number of >>>>>> services. I start zfs by default on 2345, so most core stuff is >>>>>> settled, then start everything else on zfs started, so setting gdm to >>>>>> start on started zfs, you'll be good to go. I've been researching all >>>>>> the start on clauses, and all the mechanisms to make stuff work together >>>>>> nicely, and I think I've got most of it in place. I just need to know >>>>>> what ZFS needs to do aside from modprobe zfs and zfs mount -a
