From rsb@sac.sfbay.sun.com Thu Dec 11 14:24:35 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBBMOYKE001672 for ; Thu, 11 Dec 2008 14:24:34 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBBMOSpN023129; Thu, 11 Dec 2008 22:24:33 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBQ00M05GWWC000@brm-avmta-1.central.sun.com>; Thu, 11 Dec 2008 15:24:32 -0700 (MST) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBQ00DJEGWV9J90@brm-avmta-1.central.sun.com>; Thu, 11 Dec 2008 15:24:31 -0700 (MST) Received: from sac.sfbay.sun.com (new-sac.SFBay.Sun.COM [129.146.175.65]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBBMOTVr020148; Thu, 11 Dec 2008 14:24:29 -0800 (PST) Received: from sac.sfbay.sun.com (localhost [127.0.0.1]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBBMOSZg001646; Thu, 11 Dec 2008 14:24:28 -0800 (PST) Received: (from rsb@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id mBBMOSm9001642; Thu, 11 Dec 2008 16:24:28 -0600 (CST) Date: Thu, 11 Dec 2008 16:24:28 -0600 (CST) From: rich.brown@sun.com Subject: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] To: PSARC-ext@sun.com Cc: pavel.filipensky@sun.com, rich.brown@sun.com Message-id: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 3618 I'm sponsoring this case for Pavel Filipensky to add the '-Z' option to umountall(1M). This case times out on 12/18/2008. Micro/patch binding is requested for this case. Template Version: @(#)sac_nextcase %I% %G% SMI This information is Copyright 2008 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: umountall -Z 1.2. Name of Document Author/Supplier: Author: Pavel Filipensky 1.3 Date of This Document: 11 December, 2008 4. Technical Description This case proposes two changes: 1) It introduces a new command line option, -Z, to umountall(1M). When the umountall(1M) command is run in the global zone, this option applies the unmounting action(s) only to the file systems mounted in non-global zones. The use of -Z option in non-global zones will have no effect. 2) The default behavior of umountall(1M) is changed to limit the unmounting action(s) to the current zone. Rationale for limiting the default scope to the current zone: Currently, running umountall(1M) in the global zone unmounts file systems from the global zone and from non-global zones as well. This is causing following bugs: 6502014 NFS mounts in non-global zones are unmounted if NFS is restarted in the global zone 6512906 Autofs mounts in non-global zones are unmounted when autofs is restarted in the global zone 6777323 smb mounts in non-global zones are unmounted when smb/client is restarted in the global zone Limiting the default scope of umountall(1M) to the current zone will fix the bugs above. Rationale for adding the new -Z option: The -Z option will be used in the stop method of svc:/system/zones:default. This will take care of the case when we try to stop zones and some of them fail to shut down. It is better to try to unmount the filesystems mounted in them to free resources on the servers. There are no side effects of using -Z option on other suboptions to umountall(1). Using -Z never changes the behaviour of other suboptions, -Z only changes their scope. The webrev for these changes is available here: http://cr.opensolaris.org/~pavelf/6779275 Related CR: 6779275 umountall(1M) -Z ... limit unmounting action(s) to the non-global zones EXPORTED INTERFACES umountall(1M) option Stability Level -Z Committed DOCUMENTATION IMPACT (See 6780521) manpage umountall(1M) changes: 1. a new -Z option 2. change in the default behavior Changes are as follows: SYNOPSIS mountall [-F FSType] [-l | -r] [file_system_table] umountall [-k] [-s] [-F FSType] [-l | -r] [-n] [-Z] + umountall [-k] [-s] [-h host] [-n] [-Z] + [...] 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, moun- tall and umountall limit their actions to the FSType speci- [...] -s Do not perform the umount operation in parallel. -Z Apply the action(s) only to the file systems + mounted in non-global zones. By default, umoun- + tall unmounts only file systems mounted in the + current zone. Has no effect if used in a non- + global zone. + FILES [...] 6. Resources and Schedule 6.4. Steering Committee requested information 6.4.1. Consolidation C-team Name: ON 6.5. ARC review type: FastTrack 6.6. ARC Exposure: open From peter.tribble@gmail.com Thu Dec 11 14:59:22 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBBMxL83003077 for ; Thu, 11 Dec 2008 14:59:22 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBBMxCp2014852; Thu, 11 Dec 2008 22:59:19 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBQ00C09IIUQL00@nwk-avmta-2.sfbay.sun.com>; Thu, 11 Dec 2008 14:59:18 -0800 (PST) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBQ00MZUIIU7TD0@nwk-avmta-2.sfbay.sun.com>; Thu, 11 Dec 2008 14:59:18 -0800 (PST) Received: from relay22.sun.com (relay22.sun.com [192.12.251.34] (may be forged)) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBBMxHwR002197; Thu, 11 Dec 2008 22:59:18 +0000 (GMT) Received: from mms22es.mms.us.syntegra.com ([150.143.232.30] [150.143.232.30]) by relay22i.sun.com with ESMTP id BT-MMP-1212798; Thu, 11 Dec 2008 22:59:17 +0000 (Z) Received: from relay24.sun.com (relay24.sun.com [192.12.251.74]) by mms22es.mms.us.syntegra.com with ESMTP id BT-MMP-18973574; Thu, 11 Dec 2008 22:59:17 +0000 (Z) Received: from fg-out-1718.google.com ([72.14.220.157] [72.14.220.157]) by relay24i.sun.com with ESMTP id BT-MMP-23327084; Thu, 11 Dec 2008 22:59:17 +0000 (Z) Received: by fg-out-1718.google.com with SMTP id e21so596594fga.6 for ; Thu, 11 Dec 2008 14:58:27 -0800 (PST) Received: by 10.86.80.17 with SMTP id d17mr1663878fgb.14.1229036307202; Thu, 11 Dec 2008 14:58:27 -0800 (PST) Received: by 10.86.87.7 with HTTP; Thu, 11 Dec 2008 14:58:27 -0800 (PST) Date: Thu, 11 Dec 2008 22:58:27 +0000 From: Peter Tribble Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> To: rich.brown@sun.com Cc: PSARC-ext@sun.com, pavel.filipensky@sun.com Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT Content-disposition: inline DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=8QnU37vLTn8rOs7bJqGHE16sZNSwrs8xhAW6hzeSSBo=; b=D4xLHS4yDC8fIno3nk9Ox7A7haXV/FW4mI414t7HCriQrzA405lqnScBB7RBFQXiwl bLR8+ONoABBdTyutvop7pPGSicGmzWafLWiPV+uTTKhxTVU4VJ9bApXqtKXhpnyrdtUl O9LmsART+qXeXw+n2WpVhDGOEZt1QnPt0IIGI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=f8o/jC0HWMicwoalHcQONrLLrJrSbuRvOSx7DF6pQbbEb6ugwGgFx6Ol9vdddqEa1+ pWVzSGiLMnHrYzZB1vINFAdQBvq/EvlYY/eG4J5S5fKIW1PNyjULV8q0msDKzWSNgHs6 aNyxyqvxlQ6etuwQ4wnlX+68mzchUriZISw0E= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=0.0/5.0, scanned in 0.185sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> Status: RO Content-Length: 1185 On Thu, Dec 11, 2008 at 10:24 PM, wrote: > > I'm sponsoring this case for Pavel Filipensky to add the '-Z' option to > umountall(1M). This case times out on 12/18/2008. > > Micro/patch binding is requested for this case. > > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > umountall -Z > 1.2. Name of Document Author/Supplier: > Author: Pavel Filipensky > 1.3 Date of This Document: > 11 December, 2008 > 4. Technical Description > > This case proposes two changes: > > 1) It introduces a new command line option, -Z, to umountall(1M). When > the umountall(1M) command is run in the global zone, this option > applies the unmounting action(s) only to the file systems mounted in > non-global zones. The use of -Z option in non-global zones will > have no effect. To clarify, what happens if I run umountall -Z in a non-global zone? Does it ignore the -Z flag and run umountall anyway? Or does it not unmount anything? -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/ From Pavel.Filipensky@sun.com Fri Dec 12 00:47:05 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBC8l5cm001965 for ; Fri, 12 Dec 2008 00:47:05 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBC8l4qX041220 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 12 Dec 2008 01:47:05 -0700 (MST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBR00I0R9QG2600@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 12 Dec 2008 01:47:04 -0700 (MST) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBR00EKC9QEKW10@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 12 Dec 2008 01:47:03 -0700 (MST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBC8l2cD012971 for ; Fri, 12 Dec 2008 08:47:02 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBR00F019HWP100@fe-emea-09.sun.com> (original mail from Pavel.Filipensky@Sun.COM) for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 12 Dec 2008 08:47:02 +0000 (GMT) Received: from [129.157.16.189] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBR00KNR9Q66900@fe-emea-09.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Fri, 12 Dec 2008 08:47:01 +0000 (GMT) Date: Fri, 12 Dec 2008 09:46:54 +0100 From: Pavel Filipensky Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: Sender: Pavel.Filipensky@sun.com To: Peter Tribble Cc: Rich.Brown@sun.com, PSARC-ext@sun.com Reply-to: Pavel.Filipensky@sun.com Message-id: <494224FE.9050708@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 1457 On 12/11/08 23:58, Peter Tribble wrote: > On Thu, Dec 11, 2008 at 10:24 PM, wrote: > >> I'm sponsoring this case for Pavel Filipensky to add the '-Z' option to >> umountall(1M). This case times out on 12/18/2008. >> >> Micro/patch binding is requested for this case. >> >> >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> umountall -Z >> 1.2. Name of Document Author/Supplier: >> Author: Pavel Filipensky >> 1.3 Date of This Document: >> 11 December, 2008 >> 4. Technical Description >> >> This case proposes two changes: >> >> 1) It introduces a new command line option, -Z, to umountall(1M). When >> the umountall(1M) command is run in the global zone, this option >> applies the unmounting action(s) only to the file systems mounted in >> non-global zones. The use of -Z option in non-global zones will >> have no effect. >> > > 'umountall -Z' when run in a non-global zone, ignores the -Z flag and runs umountall anyway. The wording in manpage could be changed from: Has no effect if used in a non-global zone. to Option -Z is ignored if used in a non-global zone. > To clarify, what happens if I run > > umountall -Z > > in a non-global zone? Does it ignore the -Z flag and run umountall anyway? > Or does it not unmount anything? > > From Brian.Ruthven@sun.com Fri Dec 12 02:20:08 2008 Received: from newsunmail1brm.central.sun.com (newsunmail1brm.Central.Sun.COM [129.147.62.245]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBCAK7YO003640 for ; Fri, 12 Dec 2008 02:20:08 -0800 (PST) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBCAK6OI031639 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 12 Dec 2008 03:20:07 -0700 (MST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBR00805E1H5O00@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 02:20:05 -0800 (PST) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBR003RGE1GMR90@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 02:20:05 -0800 (PST) Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe2.eu.sun.com [192.18.6.11]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBCAK47I000339 for ; Fri, 12 Dec 2008 10:20:04 +0000 (GMT) Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBR00B01D0WSW00@fe-emea-09.sun.com> (original mail from Brian.Ruthven@Sun.COM) for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 10:20:04 +0000 (GMT) Received: from [129.156.173.239] by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBR007Z2E0SUH70@fe-emea-09.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 10:19:40 +0000 (GMT) Date: Fri, 12 Dec 2008 10:19:40 +0000 From: Brian Ruthven - Sun UK Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> Sender: Brian.Ruthven@sun.com To: Rich.Brown@sun.com Cc: PSARC-ext@sun.com, Pavel.Filipensky@sun.com Message-id: <49423ABC.3010701@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.9 (X11/20071119) Status: RO Content-Length: 5137 Is it ever likely to be useful to do "umountall -Z zonename" ? Perhaps to help release resources from a single zone, rather than having to umountall across all zones simultaneously? [ My thinking behind this is the recent change to lpstat where the -l flag suddenly started taking an additional parameter, and that broke all sorts of customer scripts which were used to the "lpstat -lp" command. I'd like to avoid a future incompatibility, but it depends on the expected target audience of this flag... ] Does this additional flag need to be added to the man page at all? Could it simply be a "private" flag? Is the -Z flag ever expected to be run by the average sysadmin on the command-line, or would it be confined to the zones stop method? As long as the change to the default behaviour is noted (and frankly I would have expected umountall to operate in the current zone only anyway), and if the only place it is likely to be used is the zones stop method, I imagine the -Z could be an "undocumented" flag (cf. "savecore -m", only used in the bootup sequence). Thanks, Brian Rich.Brown@Sun.COM wrote: > I'm sponsoring this case for Pavel Filipensky to add the '-Z' option to > umountall(1M). This case times out on 12/18/2008. > > Micro/patch binding is requested for this case. > > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > umountall -Z > 1.2. Name of Document Author/Supplier: > Author: Pavel Filipensky > 1.3 Date of This Document: > 11 December, 2008 > 4. Technical Description > > This case proposes two changes: > > 1) It introduces a new command line option, -Z, to umountall(1M). When > the umountall(1M) command is run in the global zone, this option > applies the unmounting action(s) only to the file systems mounted in > non-global zones. The use of -Z option in non-global zones will > have no effect. > > 2) The default behavior of umountall(1M) is changed to limit the > unmounting action(s) to the current zone. > > > Rationale for limiting the default scope to the current zone: > > Currently, running umountall(1M) in the global zone unmounts file > systems from the global zone and from non-global zones as well. This > is causing following bugs: > > 6502014 NFS mounts in non-global zones are unmounted if NFS is restarted in the global zone > 6512906 Autofs mounts in non-global zones are unmounted when autofs is restarted in the global zone > 6777323 smb mounts in non-global zones are unmounted when smb/client is restarted in the global zone > > Limiting the default scope of umountall(1M) to the current zone will > fix the bugs above. > > Rationale for adding the new -Z option: > > The -Z option will be used in the stop method of > svc:/system/zones:default. This will take care of the case when we try > to stop zones and some of them fail to shut down. It is better to try > to unmount the filesystems mounted in them to free resources on the > servers. > > There are no side effects of using -Z option on other suboptions to > umountall(1). Using -Z never changes the behaviour of other > suboptions, -Z only changes their scope. > > > The webrev for these changes is available here: > http://cr.opensolaris.org/~pavelf/6779275 > > > Related CR: > > 6779275 umountall(1M) -Z ... limit unmounting action(s) to the non-global zones > > EXPORTED INTERFACES > > umountall(1M) option Stability Level > > -Z Committed > > DOCUMENTATION IMPACT (See 6780521) > > manpage umountall(1M) changes: > 1. a new -Z option > 2. change in the default behavior > > > Changes are as follows: > > SYNOPSIS > mountall [-F FSType] [-l | -r] [file_system_table] > > umountall [-k] [-s] [-F FSType] [-l | -r] [-n] [-Z] + > > umountall [-k] [-s] [-h host] [-n] [-Z] + > [...] > 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, moun- > tall and umountall limit their actions to the FSType speci- > [...] > -s Do not perform the umount operation in parallel. > > -Z Apply the action(s) only to the file systems + > mounted in non-global zones. By default, umoun- + > tall unmounts only file systems mounted in the + > current zone. Has no effect if used in a non- + > global zone. + > > FILES > [...] > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open > > -- Brian Ruthven Sun Microsystems UK Solaris Revenue Product Engineering Tel: +44 (0)1252 422 312 Sparc House, Guillemont Park, Camberley, GU17 9QG From Pavel.Filipensky@sun.com Fri Dec 12 04:24:20 2008 Received: from sunmail3mpk.sfbay.sun.com (sunmail3mpk.SFBay.Sun.COM [129.146.11.52]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBCCOJ1m021354 for ; Fri, 12 Dec 2008 04:24:20 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail3mpk.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBCCOIFO019454 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 12 Dec 2008 04:24:19 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBR00G0DJSIMF00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 05:24:18 -0700 (MST) Received: from gmp-eb-inf-2.sun.com ([192.18.6.24]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBR00EWIJSHK6E0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 05:24:18 -0700 (MST) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id mBCCOHYO001380 for ; Fri, 12 Dec 2008 12:24:17 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBR00501JBKIG00@fe-emea-10.sun.com> (original mail from Pavel.Filipensky@Sun.COM) for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 12:24:17 +0000 (GMT) Received: from [129.157.16.189] by fe-emea-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBR0064UJRELGD0@fe-emea-10.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Fri, 12 Dec 2008 12:23:48 +0000 (GMT) Date: Fri, 12 Dec 2008 13:23:38 +0100 From: Pavel Filipensky Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: <49423ABC.3010701@sun.com> Sender: Pavel.Filipensky@sun.com To: Brian Ruthven - Sun UK Cc: Rich.Brown@sun.com, PSARC-ext@sun.com Reply-to: Pavel.Filipensky@sun.com Message-id: <494257CA.7000606@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> <49423ABC.3010701@sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 5573 Hi Brian, On 12/12/08 11:19, Brian Ruthven - Sun UK wrote: > > Is it ever likely to be useful to do "umountall -Z zonename" ? # zlogin zonename umountall is a way to do that > Perhaps to help release resources from a single zone, rather than > having to umountall across all zones simultaneously? > > [ My thinking behind this is the recent change to lpstat where the -l > flag suddenly started taking an additional parameter, and that broke > all sorts of customer scripts which were used to the "lpstat -lp" > command. I'd like to avoid a future incompatibility, but it depends on > the expected target audience of this flag... ] > > Does this additional flag need to be added to the man page at all? > Could it simply be a "private" flag? Is the -Z flag ever expected to > be run by the average sysadmin on the command-line, or would it be > confined to the zones stop method? -Z option might be interesting for experienced admins and for developers - how they should get to know about the existence of that flag? -Z is proposed to be mentioned in 'Usage' as well: # umountall -? Usage: umountall [-k] [-s] [-F FSType] [-l|-r] [-Z] [-n] umountall [-k] [-s] [-h host] [-Z] [-n] Thanks, Pavel > > As long as the change to the default behaviour is noted (and frankly I > would have expected umountall to operate in the current zone only > anyway), and if the only place it is likely to be used is the zones > stop method, I imagine the -Z could be an "undocumented" flag (cf. > "savecore -m", only used in the bootup sequence). > > Thanks, > Brian > > > Rich.Brown@Sun.COM wrote: >> I'm sponsoring this case for Pavel Filipensky to add the '-Z' option to >> umountall(1M). This case times out on 12/18/2008. >> >> Micro/patch binding is requested for this case. >> >> >> Template Version: @(#)sac_nextcase %I% %G% SMI >> This information is Copyright 2008 Sun Microsystems >> 1. Introduction >> 1.1. Project/Component Working Name: >> umountall -Z >> 1.2. Name of Document Author/Supplier: >> Author: Pavel Filipensky >> 1.3 Date of This Document: >> 11 December, 2008 >> 4. Technical Description >> >> This case proposes two changes: >> >> 1) It introduces a new command line option, -Z, to umountall(1M). When >> the umountall(1M) command is run in the global zone, this option >> applies the unmounting action(s) only to the file systems mounted in >> non-global zones. The use of -Z option in non-global zones will >> have no effect. >> >> 2) The default behavior of umountall(1M) is changed to limit the >> unmounting action(s) to the current zone. >> >> Rationale for limiting the default scope to the current zone: >> >> Currently, running umountall(1M) in the global zone unmounts file >> systems from the global zone and from non-global zones as well. This >> is causing following bugs: >> >> 6502014 NFS mounts in non-global zones are unmounted if NFS is >> restarted in the global zone >> 6512906 Autofs mounts in non-global zones are unmounted when autofs >> is restarted in the global zone >> 6777323 smb mounts in non-global zones are unmounted when >> smb/client is restarted in the global zone >> >> Limiting the default scope of umountall(1M) to the current zone will >> fix the bugs above. >> >> Rationale for adding the new -Z option: >> >> The -Z option will be used in the stop method of >> svc:/system/zones:default. This will take care of the case when we try >> to stop zones and some of them fail to shut down. It is better to try >> to unmount the filesystems mounted in them to free resources on the >> servers. >> >> There are no side effects of using -Z option on other suboptions to >> umountall(1). Using -Z never changes the behaviour of other >> suboptions, -Z only changes their scope. >> >> >> The webrev for these changes is available here: >> http://cr.opensolaris.org/~pavelf/6779275 >> >> >> Related CR: >> >> 6779275 umountall(1M) -Z ... limit unmounting action(s) to the >> non-global zones >> >> EXPORTED INTERFACES >> >> umountall(1M) option Stability Level >> >> -Z Committed >> DOCUMENTATION IMPACT (See 6780521) >> >> manpage umountall(1M) changes: >> 1. a new -Z option >> 2. change in the default behavior >> >> >> Changes are as follows: >> >> SYNOPSIS >> mountall [-F FSType] [-l | -r] [file_system_table] >> umountall [-k] [-s] [-F FSType] [-l | -r] [-n] [-Z] + >> umountall [-k] [-s] [-h host] [-n] [-Z] + >> [...] >> 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, moun- >> tall and umountall limit their actions to the FSType speci- >> [...] >> -s Do not perform the umount operation in parallel. >> -Z Apply the action(s) only to the file >> systems + >> mounted in non-global zones. By default, umoun- + >> tall unmounts only file systems mounted in the + >> current zone. Has no effect if used in a non- + >> global zone. + >> FILES >> [...] >> >> 6. Resources and Schedule >> 6.4. Steering Committee requested information >> 6.4.1. Consolidation C-team Name: >> ON >> 6.5. ARC review type: FastTrack >> 6.6. ARC Exposure: open >> >> > From Rich.Brown@sun.com Mon Dec 15 08:54:04 2008 Received: from sunmail2sca.sfbay.sun.com (sunmail2sca.SFBay.Sun.COM [129.145.155.234]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBFGs4Ai027138 for ; Mon, 15 Dec 2008 08:54:04 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail2sca.sfbay.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id mBFGs21U026318 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Mon, 15 Dec 2008 08:54:03 -0800 (PST) Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KBX00H0FGA36000@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Mon, 15 Dec 2008 09:54:03 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KBX00LRMGA164D0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Mon, 15 Dec 2008 09:54:02 -0700 (MST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBFGs1fs022662 for ; Mon, 15 Dec 2008 16:54:01 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KBX00D01ECLPD00@mail-amer.sun.com> (original mail from Rich.Brown@Sun.COM) for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Mon, 15 Dec 2008 09:54:01 -0700 (MST) Received: from [129.147.9.135] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KBX00FHPG7LZ320@mail-amer.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Mon, 15 Dec 2008 09:52:34 -0700 (MST) Date: Mon, 15 Dec 2008 10:52:33 -0600 From: Rich Brown Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: <494257CA.7000606@Sun.COM> Sender: Rich.Brown@sun.com To: Pavel.Filipensky@sun.com, Brian Ruthven - Sun UK Cc: PSARC-ext@sun.com Reply-to: Rich.Brown@sun.com Message-id: <49468B51.1000101@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> <49423ABC.3010701@sun.com> <494257CA.7000606@Sun.COM> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 2108 On 12/12/08 06:23, Pavel Filipensky wrote: > Hi Brian, > > On 12/12/08 11:19, Brian Ruthven - Sun UK wrote: >> >> Is it ever likely to be useful to do "umountall -Z zonename" ? > # zlogin zonename umountall > is a way to do that >> Perhaps to help release resources from a single zone, rather than >> having to umountall across all zones simultaneously? >> >> [ My thinking behind this is the recent change to lpstat where the -l >> flag suddenly started taking an additional parameter, and that broke >> all sorts of customer scripts which were used to the "lpstat -lp" >> command. I'd like to avoid a future incompatibility, but it depends on >> the expected target audience of this flag... ] >> >> Does this additional flag need to be added to the man page at all? >> Could it simply be a "private" flag? Is the -Z flag ever expected to >> be run by the average sysadmin on the command-line, or would it be >> confined to the zones stop method? > -Z option might be interesting for experienced admins and for developers > - how they should get to know about the existence of that flag? > -Z is proposed to be mentioned in 'Usage' as well: > > # umountall -? > Usage: > umountall [-k] [-s] [-F FSType] [-l|-r] [-Z] [-n] > umountall [-k] [-s] [-h host] [-Z] [-n] > > Thanks, > Pavel >> >> As long as the change to the default behaviour is noted (and frankly I >> would have expected umountall to operate in the current zone only >> anyway), and if the only place it is likely to be used is the zones >> stop method, I imagine the -Z could be an "undocumented" flag (cf. >> "savecore -m", only used in the bootup sequence). >> >> Thanks, >> Brian >> In my opinion, adminstrative utilities with a system-wide effect, such as umountall(1M), should have all of their options documented. An administrator may have a use for it or may simply want to know what s/he just accidently did (oops!). I don't see an advantage to make this option private. Unless there's a compelling reason to keep this private, then let's let the proposal stand as a publicly documented option. Rich From Richard.Matthews@sun.com Wed Dec 17 09:28:00 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBHHRxkZ004620 for ; Wed, 17 Dec 2008 09:28:00 -0800 (PST) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBHHRuvE027046 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 17 Dec 2008 17:27:58 GMT Received: from pmxchannel-daemon.nwk-avmta-2.sfbay.sun.com by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC100F0N76KPE00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 17 Dec 2008 09:27:56 -0800 (PST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC100CPM76J2Y70@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Wed, 17 Dec 2008 09:27:56 -0800 (PST) Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBHHRt7N027665 for ; Wed, 17 Dec 2008 17:27:55 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KC100F012OTZD00@mail-amer.sun.com> (original mail from Richard.Matthews@Sun.COM) for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 17 Dec 2008 10:27:55 -0700 (MST) Received: from Rick-Matthews-MacBook-Pro-15.local ([129.150.32.179]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KC1006X9760KO60@mail-amer.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Wed, 17 Dec 2008 10:27:38 -0700 (MST) Date: Wed, 17 Dec 2008 11:27:38 -0600 From: Rick Matthews Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: <49468B51.1000101@Sun.COM> Sender: Richard.Matthews@sun.com To: Rich.Brown@sun.com, Pavel.Filipensky@sun.com Cc: psarc-ext@sun.com Message-id: <4949368A.3010400@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> <49423ABC.3010701@sun.com> <494257CA.7000606@Sun.COM> <49468B51.1000101@Sun.COM> User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105) Status: RO Content-Length: 2763 I agree with Rich on the avoidance of an "undocumented" parameter, unless absolutely necessary. +1 Rich Brown wrote: > On 12/12/08 06:23, Pavel Filipensky wrote: >> Hi Brian, >> >> On 12/12/08 11:19, Brian Ruthven - Sun UK wrote: >>> >>> Is it ever likely to be useful to do "umountall -Z zonename" ? >> # zlogin zonename umountall >> is a way to do that >>> Perhaps to help release resources from a single zone, rather than >>> having to umountall across all zones simultaneously? >>> >>> [ My thinking behind this is the recent change to lpstat where the >>> -l flag suddenly started taking an additional parameter, and that >>> broke all sorts of customer scripts which were used to the "lpstat >>> -lp" command. I'd like to avoid a future incompatibility, but it >>> depends on the expected target audience of this flag... ] >>> >>> Does this additional flag need to be added to the man page at all? >>> Could it simply be a "private" flag? Is the -Z flag ever expected to >>> be run by the average sysadmin on the command-line, or would it be >>> confined to the zones stop method? >> -Z option might be interesting for experienced admins and for >> developers - how they should get to know about the existence of that >> flag? >> -Z is proposed to be mentioned in 'Usage' as well: >> >> # umountall -? >> Usage: >> umountall [-k] [-s] [-F FSType] [-l|-r] [-Z] [-n] >> umountall [-k] [-s] [-h host] [-Z] [-n] >> >> Thanks, >> Pavel >>> >>> As long as the change to the default behaviour is noted (and frankly >>> I would have expected umountall to operate in the current zone only >>> anyway), and if the only place it is likely to be used is the zones >>> stop method, I imagine the -Z could be an "undocumented" flag (cf. >>> "savecore -m", only used in the bootup sequence). >>> >>> Thanks, >>> Brian >>> > > In my opinion, adminstrative utilities with a system-wide effect, such > as umountall(1M), should have all of their options documented. An > administrator may have a use for it or may simply want to know what > s/he just accidently did (oops!). I don't see an advantage to make this > option private. > > Unless there's a compelling reason to keep this private, then let's let > the proposal stand as a publicly documented option. > > Rich -- --------------------------------------------------------------------- Rick Matthews email: Rick.Matthews@sun.com Sun Microsystems, Inc. phone:+1(651) 554-1518 1270 Eagan Industrial Road phone(internal): 54418 Suite 160 fax: +1(651) 554-1540 Eagan, MN 55121-1231 USA main: +1(651) 554-1500 --------------------------------------------------------------------- From Rich.Brown@sun.com Wed Dec 17 10:18:58 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id mBHIIvrO008721 for ; Wed, 17 Dec 2008 10:18:57 -0800 (PST) Received: from brm-avmta-1.central.sun.com (brm-avmta-1.Central.Sun.COM [129.147.4.11]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id mBHIIt5i000474 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Wed, 17 Dec 2008 18:18:56 GMT Received: from pmxchannel-daemon.brm-avmta-1.central.sun.com by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0KC10081F9JJZW00@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 11:18:55 -0700 (MST) Received: from brmea-mail-2.sun.com ([192.18.98.43]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KC100L4H9JIB2B0@brm-avmta-1.central.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 11:18:54 -0700 (MST) Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id mBHIIsSJ024126 for ; Wed, 17 Dec 2008 18:18:54 +0000 (GMT) Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0KC100A018BZ2H00@mail-amer.sun.com> (original mail from Rich.Brown@Sun.COM) for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 11:18:54 -0700 (MST) Received: from [129.147.9.135] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0KC100D499JA9T00@mail-amer.sun.com> for PSARC-ext@Sun.Com (ORCPT PSARC-ext@Sun.Com); Wed, 17 Dec 2008 11:18:47 -0700 (MST) Date: Wed, 17 Dec 2008 12:18:46 -0600 From: Rich Brown Subject: Re: umountall -Z [PSARC/2008/765 FastTrack timeout 12/18/2008] In-reply-to: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> Sender: Rich.Brown@sun.com To: PSARC-ext@sun.com, Pavel.Filipensky@sun.com Cc: Rich.Brown@sun.com Reply-to: Rich.Brown@sun.com Message-id: <49494286.3030109@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200812112224.mBBMOSm9001642@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.16 (X11/20080807) Status: RO Content-Length: 4004 This case was approved at today's PSARC meeting. I've updated the IAM file to reflect the approval. Thanks all, Rich On 12/11/08 16:24, Rich.Brown@Sun.COM wrote: > I'm sponsoring this case for Pavel Filipensky to add the '-Z' option to > umountall(1M). This case times out on 12/18/2008. > > Micro/patch binding is requested for this case. > > > Template Version: @(#)sac_nextcase %I% %G% SMI > This information is Copyright 2008 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > umountall -Z > 1.2. Name of Document Author/Supplier: > Author: Pavel Filipensky > 1.3 Date of This Document: > 11 December, 2008 > 4. Technical Description > > This case proposes two changes: > > 1) It introduces a new command line option, -Z, to umountall(1M). When > the umountall(1M) command is run in the global zone, this option > applies the unmounting action(s) only to the file systems mounted in > non-global zones. The use of -Z option in non-global zones will > have no effect. > > 2) The default behavior of umountall(1M) is changed to limit the > unmounting action(s) to the current zone. > > > Rationale for limiting the default scope to the current zone: > > Currently, running umountall(1M) in the global zone unmounts file > systems from the global zone and from non-global zones as well. This > is causing following bugs: > > 6502014 NFS mounts in non-global zones are unmounted if NFS is restarted in the global zone > 6512906 Autofs mounts in non-global zones are unmounted when autofs is restarted in the global zone > 6777323 smb mounts in non-global zones are unmounted when smb/client is restarted in the global zone > > Limiting the default scope of umountall(1M) to the current zone will > fix the bugs above. > > Rationale for adding the new -Z option: > > The -Z option will be used in the stop method of > svc:/system/zones:default. This will take care of the case when we try > to stop zones and some of them fail to shut down. It is better to try > to unmount the filesystems mounted in them to free resources on the > servers. > > There are no side effects of using -Z option on other suboptions to > umountall(1). Using -Z never changes the behaviour of other > suboptions, -Z only changes their scope. > > > The webrev for these changes is available here: > http://cr.opensolaris.org/~pavelf/6779275 > > > Related CR: > > 6779275 umountall(1M) -Z ... limit unmounting action(s) to the non-global zones > > EXPORTED INTERFACES > > umountall(1M) option Stability Level > > -Z Committed > > DOCUMENTATION IMPACT (See 6780521) > > manpage umountall(1M) changes: > 1. a new -Z option > 2. change in the default behavior > > > Changes are as follows: > > SYNOPSIS > mountall [-F FSType] [-l | -r] [file_system_table] > > umountall [-k] [-s] [-F FSType] [-l | -r] [-n] [-Z] + > > umountall [-k] [-s] [-h host] [-n] [-Z] + > [...] > 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, moun- > tall and umountall limit their actions to the FSType speci- > [...] > -s Do not perform the umount operation in parallel. > > -Z Apply the action(s) only to the file systems + > mounted in non-global zones. By default, umoun- + > tall unmounts only file systems mounted in the + > current zone. Has no effect if used in a non- + > global zone. + > > FILES > [...] > > > 6. Resources and Schedule > 6.4. Steering Committee requested information > 6.4.1. Consolidation C-team Name: > ON > 6.5. ARC review type: FastTrack > 6.6. ARC Exposure: open >