The impact to ADM (an HSM) of a disorderly shutdown (crash/powerfailure/etc) is that we must scan the ADM managed file systems to identify file changes we might have missed.
We will attempt to cleanly cover as many scenarios as we can, but the rest will require a scan. -Joe Richard Elling wrote: > For those of us (RAS guys) who worry about unscheduled shutdowns, > what is the impact of an unscheduled shutdown? > -- richard > > Joe Blount wrote: >> Hi, >> >> I'm working on a manifest for the ADM event manager, which needs to >> be started in time to receive ZFS mount notifications, and shut down >> late enough to receive unmount notifications. Failures of this >> service should not hinder other non-ADM services, and we don't need >> to handle root ZFS file systems. >> >> So I thought this would accomplish what I need: >> <!-- >> Wait for /, /usr, /var, /var/adm, /var/run, and /tmp to be mounted. >> --> >> <dependency >> name='filesystem-usr' >> grouping='require_all' >> restart_on='none' >> type='service'> >> <service_fmri value='svc:/system/filesystem/usr' /> >> </dependency> >> >> <!-- >> Make other filesystem wait until sunwhsm_evm has tried to >> come up >> --> >> <dependent >> name='filesystem-minimal' >> restart_on='none' >> grouping='optional_all'> >> <service_fmri value='svc:/system/filesystem/minimal'/> >> </dependent> >> >> This appears to work correctly during startup ? the event manager is >> started in time for ZFS mounts. >> >> But during shutdowns, the event manager is getting shutdown before >> ZFS unmounts. >> >> Based on what I've found searching, and I expected SMF dependencies >> to be applied in reverse order for nevada builds greater than 12 (CR >> 6207705). I'm on nevada 79. >> >> What am I missing? >> >> (ADM link: http://opensolaris.org/os/project/adm/) >> >> Thanks, >> Joe >> >> >> This message posted from opensolaris.org >> _______________________________________________ >> smf-discuss mailing list >> smf-discuss at opensolaris.org >> >
