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.
--Pavel
> When would it be desirable for umountall to unmount file systems in
> all zones? It seems to me that umountall will called during system
> shutdown or just before a similarly crafted mountall. Unless mountall
> is extended to do perform its work in all zones in the absence of the
> -z option, I find the current behavior as dangerous in most usage
> scenarios.
>
> During system shutdown, all zones should be down before the autofs and
> nfs client services stop in the global zones. In the event that some
> zone is not shut down, this means that it is likely stuck in a
> shutting down state and any calls to unmount "stuck" nfs mounts in
> that zone will result in a hung system call and an SMF stop method
> timeout.
>
> It seems to me that there is a real chance[1] that the RPC calls would
> not even be routable to an NFS server. See, for example,
> http://bugs.opensolaris.org/view_bug.do?bug_id=6476438.
>
>
>
>> 4.2. Bug/RFE Number(s):
>> 6502014 NFS mounts in non-global zones are unmounted if NFS
>> is restarted in the global zone
>>
>> 4.5. Interfaces:
>>
>> New option -z for umountall(1M).
>>
>> 4.6. Doc Impact:
>>
>> This will be added to the umountall(1M) manpage:
>>
>> SYNOPSIS
>> umountall [-k] [-s] [-F FSType] [-l | -r] [-z] [-n]
>>
>>
>> umountall [-k] [-s] [-h host] [-z] [-n]
>>
>> ...
>>
>> -z Limit the action(s) only to the mounts
>> coming from the current zone.
>>
>
> I suggest instead that the -z option not be added and the following
> man page change occurs:
>
> umountall causes all mounted file systems in the current
> zone except root, /usr, /var, /var/adm, /var/run, /proc, and
> /dev/fd to be unmounted. If the FSType is specified,
> mountall and umountall limit their actions to the FSType
> specified. There is no guarantee that umountall unmounts
> busy file systems, even if the -k option is specified.
>
>
