On Fri, Nov 28, 2008 at 1:59 PM, Pavel Filipensky <Pavel.Filipensky at sun.com> wrote: > Regarding the default behavior and available options for umountall(1M) there > are these possibilities: > > 1) default behavior: don't limit action(s) to the current zone > available options: none > > 2) default behavior:: don't limit action(s) to the current zone > available options: -z ...limit action(s)to the current zone > > 3) default behavior:: limit action(s) to the current zone > available options: none > > 4) default behavior:: limit action(s) to the current zone > available options: -Z ...apply action(s) to all zones > > #1 .. existing situation > #2 .. mine original proposal > #3 .. Mike's proposal > #4 .. another possibility > > > Originally, I was afraid of changing the default behavior of umountall(1M) > to avoid problems > to the existing applications. But it is hard to imagine that there is such > application which > uses umountall(1M) and relies that it will unmount filesystems also in > non-global zones. > As noted by Mike, during system shutdown, all zones should be down before > the autofs and > nfs client services stop in the global zones. > > Unless no one sees a problem with changing the default behavior, let's use > solution #3. > If someone sees a good reason to implement -Z option, let's use solution #4.
I can not think of a case where "umountall -Z ... " is an advisable command, particularly if "mountall -Z ..." is not implemented. The reality is that systems tend to have things that depend on file systems and "umountall -Z" seems unlikely to do the right thing given the likely dependencies. An administrator that is sophisticated enough to manage all of those dependencies properly (which at best is likely "for zone in `zoneadm list`; do ... ; done") can insert the appropriate per-zone umountall or svcadm command. -- Mike Gerdts http://mgerdts.blogspot.com/
