On 10/3/07, David Bustos <David.Bustos at sun.com> wrote: > Word on the street is that the kernel dumps to the end of the swap > device. Since we start swapping from the beginning, it's possible to > clobber the dump, but less likely with larger swap devices. Apparently > there has been talk of fixing this up, but it doesn't seem to be > a priority.
There is a prototype out there (posted to the list yesterday) of using SMF instead of vfstab for handling mounts. This could make it really easy to get the dependencies right without unnecessarily slowing down the boot process. An application that is known to need to use swap could just set the appropriate dependency. Presumably this would mean that dumpadm would be responsible for updating SMF dependencies or there could be multiple dumpadm services (dumpadm:swap, dumpadm:dedicated) that do the right thing based upon the dumpadm.conf or replacement properties in the service properties. One of the things previously discussed at sysadmin-discuss was having savecore (called by dumpadm service) save to an NFS mounted directory. It seems as though at path dependency could form an implicit dependency on any required mounts (be they vfstab, smf, autofs, or something else) without having to analyze and muck with the dependencies when file system mount configurations are changed. Mike -- Mike Gerdts http://mgerdts.blogspot.com/
