From blu@sac.sfbay.sun.com Mon May 18 05:44:13 2009 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 n4ICiDAd026877 for ; Mon, 18 May 2009 05:44:13 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by newsunmail1brm.central.sun.com (8.13.7+Sun/8.13.7/ENSMAIL,v2.2) with ESMTP id n4ICiAvd046583; Mon, 18 May 2009 06:44:12 -0600 (MDT) 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 <0KJU00L09BDO9500@nwk-avmta-2.sfbay.sun.com>; Mon, 18 May 2009 05:44:12 -0700 (PDT) Received: from dm-sfbay-02.sfbay.sun.com ([129.146.11.31]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJU00KFGBDN6O20@nwk-avmta-2.sfbay.sun.com>; Mon, 18 May 2009 05:44:11 -0700 (PDT) Received: from sac.sfbay.sun.com (sac.SFBay.Sun.COM [129.146.226.132]) by dm-sfbay-02.sfbay.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n4ICiAoh018229; Mon, 18 May 2009 05:44:10 -0700 (PDT) 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 n4ICi9R1026872; Mon, 18 May 2009 05:44:09 -0700 (PDT) Received: (from blu@localhost) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8/Submit) id n4ICi9IS026868; Mon, 18 May 2009 05:44:09 -0700 (PDT) Date: Mon, 18 May 2009 05:44:09 -0700 (PDT) From: Brian Utterback Subject: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. [PSARC/2009/309 FastTrack timeout 05/25/2009] To: PSARC-ext@sun.com Cc: Owen.Roberts@sun.com Message-id: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 Status: RO Content-Length: 4102 Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI This information is Copyright 2009 Sun Microsystems 1. Introduction 1.1. Project/Component Working Name: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. 1.2. Name of Document Author/Supplier: Author: Owen Roberts 1.3 Date of This Document: 18 May, 2009 4. Technical Description Proposal: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. Detail: The default maximum ufs log size has been 64 Mbytes since ufs logging was integrated into Solaris 7. The algorithhm used to determine the size of the log being approximately 1 Mbyte of log allocated for every 1 Gbyte of file system up to a maximum specified by the kernel variable ldl_maxlogsize which is set to 64 Mbytes. It has not been possible to increase the default maximum size of the ufs log in the past due to the restriction of lufsboot only being able to handle a 64 Mbyte dirty log. A larger dirty log would result in memory exhaustion in this early stage of the boot process. The requirement to increase the maximum default ufs log size is to overcome a problem now seen due to larger file systems. In certain circumstances it is possible to fill the log in a single file system transaction resulting in a file system hang. With the introduction of new boot to the sparc architecture in Solaris 10 update 6 (new boot for the x86 architecture was delivered in Solaris 10 update 1) the 64 Mbyte constraint is no longer applicable allowing the opportunity to provide a solution for the full log hang as documented in the bugs 4673568 and 6709826. The work around to CRs 4673568 and 6709826 is to either disable ufs logging (which potentially exposes customers to delayed boots while waiting for an fsck to complete), or for customers to manually increase the ldl_maxlogsize as per the Sun Alert 200854. The decision to increase the ldl_maxlogsize to 512 Mbytes was based on the fact that this size log would prevent a full log hang in a 16 TByte file system which is the maximum ufs file system size. Release binding: Patch Documenation Impact: Update to the ufs (7FS) man page. 147c147 < The UFS log is allocated from free blocks on the file system, and is sized at approximately 1 Mbyte per 1 Gbyte of file system, up to a maximum of 64 Mbytes. The log is continually flushed as it fills up. The log is also flushed when the file system is unmounted or as a result of a \fBlockfs\fR command. --- > The UFS log is allocated from free blocks on the file system, and is sized at approximately 1 Mbyte per 1 Gbyte of file system, up to 256 Mbytes. The log size may be larger (up to a maximum of 512 Mbytes) based upon the number of cylinder groups present in the file system. The log is continually flushed as it fills up. The log is also flushed when the file system is unmounted or as a result of a \fBlockfs\fR command. Update to the mount_ufs (1M) man page. 134c134 < The log is allocated from free blocks in the file system, and is sized approximately 1 Mbyte per 1 Gbyte of file system, up to a maximum of 64 Mbytes. --- > The log is allocated from free blocks in the file system, and is sized approximately 1 Mbyte per 1 Gbyte of file system, up to 256 Mbytes. The log size may be larger (up to a maximum of 512 Mbytes) based upon the number of cylinder groups present in the file system. Update to the System Administration Guide answerbook under the "The UFS File System" section. References: 1. PSARC 2004/454 Solaris Boot Architecture 2. PSARC 2006/525 new-boot sparc 3. CR 4673568 system hangs with ufs logging suspect 4. CR 6709826 ufs log size should be large enough by default to avoid panic described in Sun Alert 200854 5. Sun Alert 200854 Solaris System May Hang Due to Insufficient Log Space Allocation on UFS With Logging Enabled 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 carlsonj@phorcys.east.sun.com Mon May 18 05:53:58 2009 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 n4ICrwuJ027153 for ; Mon, 18 May 2009 05:53:58 -0700 (PDT) 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 n4ICrvDP052429 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.COM>; Mon, 18 May 2009 06:53:58 -0600 (MDT) 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 <0KJU00C0DBTXG700@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 05:53:57 -0700 (PDT) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJU0046XBTXNEC0@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 05:53:57 -0700 (PDT) Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n4ICrs79038203; Mon, 18 May 2009 08:53:54 -0400 (EDT) Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n4ICqxbL022929; Mon, 18 May 2009 08:52:59 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n4ICqx6t022926; Mon, 18 May 2009 08:52:59 -0400 (EDT) Date: Mon, 18 May 2009 08:52:59 -0400 From: James Carlson Subject: Re: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. [PSARC/2009/309 FastTrack timeout 05/25/2009] In-reply-to: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> To: Brian Utterback Cc: PSARC-ext@sun.com, Owen.Roberts@sun.com Message-id: <18961.23083.839610.646718@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> Status: RO Content-Length: 549 Brian Utterback writes: > The decision to increase the ldl_maxlogsize to 512 Mbytes was > based on the fact that this size log would prevent a full log > hang in a 16 TByte file system which is the maximum ufs file > system size. What's the intermediate size of 256MB (in the man page text) about? Other than that, +1. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From Owen.Roberts@sun.com Mon May 18 10:46:25 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n4IHkOI7005001 for ; Mon, 18 May 2009 10:46:24 -0700 (PDT) Received: from nwk-avmta-2.sfbay.sun.com (nwk-avmta-2.SFBay.Sun.COM [129.145.155.6]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n4IHjUhE011823 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Tue, 19 May 2009 01:46:23 +0800 (SGT) 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 <0KJU00E1JPD5XU00@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 10:46:17 -0700 (PDT) Received: from gmp-eb-inf-1.sun.com ([192.18.6.21]) by nwk-avmta-2.sfbay.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJU00A50PD4UQB0@nwk-avmta-2.sfbay.sun.com> for PSARC-ext@sun.com (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 10:46:16 -0700 (PDT) Received: from fe-emea-10.sun.com (gmp-eb-lb-1-fe3.eu.sun.com [192.18.6.10]) by gmp-eb-inf-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n4IHkFIf022738 for ; Mon, 18 May 2009 17:46:15 +0000 (GMT) Received: from conversion-daemon.fe-emea-10.sun.com by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) id <0KJU00F00P9DI100@fe-emea-10.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 18:46:15 +0100 (BST) Received: from [192.168.10.17] ([unknown] [129.150.116.247]) by fe-emea-10.sun.com (Sun Java(tm) System Messaging Server 7u2-7.02 64bit (built Apr 16 2009)) with ESMTPSA id <0KJU00B2WPD0RE20@fe-emea-10.sun.com>; Mon, 18 May 2009 18:46:13 +0100 (BST) Date: Mon, 18 May 2009 18:46:11 +0100 From: Owen Roberts - Solaris Sustaining Subject: Re: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. [PSARC/2009/309 FastTrack timeout 05/25/2009] In-reply-to: <18961.23083.839610.646718@gargle.gargle.HOWL> Sender: Owen.Roberts@sun.com To: James Carlson Cc: Brian Utterback , PSARC-ext@sun.com Message-id: <4A119EE3.7080804@sun.com> MIME-version: 1.0 Content-type: text/plain; CHARSET=US-ASCII; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> <18961.23083.839610.646718@gargle.gargle.HOWL> User-Agent: Thunderbird 2.0.0.14 (X11/20080531) Status: RO Content-Length: 1136 James Carlson wrote: > Brian Utterback writes: >> The decision to increase the ldl_maxlogsize to 512 Mbytes was >> based on the fact that this size log would prevent a full log >> hang in a 16 TByte file system which is the maximum ufs file >> system size. > > What's the intermediate size of 256MB (in the man page text) about? > > Other than that, +1. > We wanted to keep the 1MB of log for 1GB of file system algorithm, but not unduly use file system space in the log, so capped that allocation at a 256MB log. A 256MB log should cover file systems that contain the number of cylinder groups seen up to 13TB in size, so would be more than sufficient for the majority of customers (and is the work around specified in sunalert 200854). There is also the possibility that users will specify their own geometry which would contain a greater number of cylinder groups than would be expected for that size of file system. To cover those eventualities (> 13TB & non-default geometry) the log space requirement based on the number of cylinder groups is calculated, and that can increase the log size allocated up to 512MB. Owen From carlsonj@phorcys.east.sun.com Mon May 18 10:58:57 2009 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 n4IHwu6b006298 for ; Mon, 18 May 2009 10:58:56 -0700 (PDT) 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 n4IHwu8Q033718 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@Sun.COM>; Mon, 18 May 2009 11:58:56 -0600 (MDT) 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 <0KJU00M09PY6D700@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 11:58:54 -0600 (MDT) Received: from dm-east-02.east.sun.com ([129.148.13.5]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KJU007PFPY5FYC0@brm-avmta-1.central.sun.com> for PSARC-ext@Sun.COM (ORCPT PSARC-ext@Sun.COM); Mon, 18 May 2009 11:58:54 -0600 (MDT) Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n4IHwq1v018870; Mon, 18 May 2009 13:58:52 -0400 (EDT) Received: from phorcys.east.sun.com (phorcys.local [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n4IHvuOJ024441; Mon, 18 May 2009 13:57:56 -0400 (EDT) Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n4IHvulK024438; Mon, 18 May 2009 13:57:56 -0400 (EDT) Date: Mon, 18 May 2009 13:57:56 -0400 From: James Carlson Subject: Re: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. [PSARC/2009/309 FastTrack timeout 05/25/2009] In-reply-to: <4A119EE3.7080804@sun.com> To: Owen Roberts - Solaris Sustaining Cc: Brian Utterback , PSARC-ext@sun.com Message-id: <18961.41380.327704.334222@gargle.gargle.HOWL> MIME-version: 1.0 X-Mailer: VM 7.01 under Emacs 21.3.1 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> <18961.23083.839610.646718@gargle.gargle.HOWL> <4A119EE3.7080804@sun.com> Status: RO Content-Length: 934 Owen Roberts - Solaris Sustaining writes: > A 256MB log should cover file systems that contain the number of cylinder > groups seen up to 13TB in size, so would be more than sufficient for the > majority of customers (and is the work around specified in sunalert 200854). > There is also the possibility that users will specify their own geometry > which would contain a greater number of cylinder groups than would be > expected for that size of file system. > > To cover those eventualities (> 13TB & non-default geometry) the log space > requirement based on the number of cylinder groups is calculated, and that > can increase the log size allocated up to 512MB. Ah, ok. Thanks; that explains it well. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 From brian.utterback@sun.com Thu May 21 09:33:24 2009 Received: from sunmail4.singapore.sun.com (sunmail4.Singapore.Sun.COM [129.158.71.19]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id n4LGXM5M018186 for ; Thu, 21 May 2009 09:33:22 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail4.singapore.sun.com (8.13.4+Sun/8.13.3/ENSMAIL,v2.2) with ESMTP id n4LGXIgZ011206 for <@sunmail2sca.sfbay.sun.com:PSARC-ext@sun.com>; Fri, 22 May 2009 00:33:21 +0800 (SGT) 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 <0KK0000095ZJX500@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 21 May 2009 09:33:19 -0700 (PDT) Received: from dm-east-01.east.sun.com ([129.148.9.192]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KK0002MW5ZID990@nwk-avmta-1.sfbay.Sun.COM> for PSARC-ext@sun.com (ORCPT PSARC-ext@sun.com); Thu, 21 May 2009 09:33:19 -0700 (PDT) Received: from [129.148.9.87] (sr1-ubur-08.East.Sun.COM [129.148.9.87]) by dm-east-01.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n4LGXEoT004917; Thu, 21 May 2009 12:33:15 -0400 (EDT) Date: Thu, 21 May 2009 12:33:14 -0400 From: Brian Utterback Subject: Re: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. [PSARC/2009/309 FastTrack timeout 05/25/2009] In-reply-to: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> To: Brian Utterback Cc: PSARC-ext@sun.com, Owen.Roberts@sun.com Message-id: <4A15824A.9070106@sun.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT X-PMX-Version: 5.4.1.325704 References: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> User-Agent: Thunderbird 2.0.0.22pre (X11/20090422) Status: RO Content-Length: 4610 This case was approved at yesterdays PSARC meeting. Brian Utterback wrote: > Template Version: @(#)sac_nextcase 1.68 02/23/09 SMI > This information is Copyright 2009 Sun Microsystems > 1. Introduction > 1.1. Project/Component Working Name: > Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. > 1.2. Name of Document Author/Supplier: > Author: Owen Roberts > 1.3 Date of This Document: > 18 May, 2009 > 4. Technical Description > Proposal: > > Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. > > > Detail: > > The default maximum ufs log size has been 64 Mbytes since ufs > logging was integrated into Solaris 7. The algorithhm used to > determine the size of the log being approximately 1 Mbyte of log > allocated for every 1 Gbyte of file system up to a maximum > specified by the kernel variable ldl_maxlogsize which is set > to 64 Mbytes. > > It has not been possible to increase the default maximum size of > the ufs log in the past due to the restriction of lufsboot only > being able to handle a 64 Mbyte dirty log. A larger dirty log would > result in memory exhaustion in this early stage of the boot process. > > The requirement to increase the maximum default ufs log size > is to overcome a problem now seen due to larger file systems. > In certain circumstances it is possible to fill the log in a single > file system transaction resulting in a file system hang. > With the introduction of new boot to the sparc architecture in > Solaris 10 update 6 (new boot for the x86 architecture was > delivered in Solaris 10 update 1) the 64 Mbyte constraint is no > longer applicable allowing the opportunity to provide a solution > for the full log hang as documented in the bugs 4673568 and > 6709826. > > The work around to CRs 4673568 and 6709826 is to either disable > ufs logging (which potentially exposes customers to delayed > boots while waiting for an fsck to complete), or for customers > to manually increase the ldl_maxlogsize as per the Sun Alert > 200854. > > The decision to increase the ldl_maxlogsize to 512 Mbytes was > based on the fact that this size log would prevent a full log > hang in a 16 TByte file system which is the maximum ufs file > system size. > > > Release binding: > > Patch > > > Documenation Impact: > > Update to the ufs (7FS) man page. > > 147c147 > < The UFS log is allocated from free blocks on the file system, and is sized at approximately 1 Mbyte per 1 Gbyte of file system, up to a maximum of 64 Mbytes. The log is continually flushed as it fills up. The log is also flushed when the file system is unmounted or as a result of a \fBlockfs\fR command. > --- >> The UFS log is allocated from free blocks on the file system, and is sized at approximately 1 Mbyte per 1 Gbyte of file system, up to 256 Mbytes. The log size may be larger (up to a maximum of 512 Mbytes) based upon the number of cylinder groups present in the file system. The log is continually flushed as it fills up. The log is also flushed when the file system is unmounted or as a result of a \fBlockfs\fR command. > > Update to the mount_ufs (1M) man page. > > 134c134 > < The log is allocated from free blocks in the file system, and is sized approximately 1 Mbyte per 1 Gbyte of file system, up to a maximum of 64 Mbytes. > --- >> The log is allocated from free blocks in the file system, and is sized approximately 1 Mbyte per 1 Gbyte of file system, up to 256 Mbytes. The log size may be larger (up to a maximum of 512 Mbytes) based upon the number of cylinder groups present in the file system. > > Update to the System Administration Guide answerbook under the "The UFS File System" section. > > > References: > > 1. PSARC 2004/454 Solaris Boot Architecture > > 2. PSARC 2006/525 new-boot sparc > > 3. CR 4673568 system hangs with ufs logging suspect > > 4. CR 6709826 ufs log size should be large enough by default to avoid panic described in Sun Alert 200854 > > 5. Sun Alert 200854 Solaris System May Hang Due to Insufficient Log Space Allocation on UFS With Logging Enabled > > 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 > -- blu "The advertising giveth and the EULA taketh away." ---------------------------------------------------------------------- Brian Utterback - Solaris RPE, Sun Microsystems, Inc. Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom From cedric.blancher@googlemail.com Sun May 24 15:36:31 2009 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 n4OMaVmJ006121 for ; Sun, 24 May 2009 15:36:31 -0700 (PDT) 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 n4OMaQB7021814; Sun, 24 May 2009 15:36:28 -0700 (PDT) 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 <0KK60090Z6SR4M00@brm-avmta-1.central.sun.com>; Sun, 24 May 2009 16:36:27 -0600 (MDT) Received: from sca-ea-mail-2.sun.com ([192.18.43.25]) by brm-avmta-1.central.sun.com (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0KK6003BS6SMMMB0@brm-avmta-1.central.sun.com>; Sun, 24 May 2009 16:36:23 -0600 (MDT) Received: from relay15i.sun.com (ip125.net129179-4.block1.us.syntegra.com [129.179.4.125]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n4OMaMVS000511; Sun, 24 May 2009 22:36:22 +0000 (GMT) Received: from mmp14es.mmp.us.syntegra.com ([160.41.208.14] [160.41.208.14]) by relay15i.sun.com with ESMTP id BT-MMP-3207857; Sun, 24 May 2009 22:36:22 +0000 (Z) Received: from relay15i.sun.com (relay15i.sun.com [129.179.4.125]) by mmp14es.mmp.us.syntegra.com with ESMTP id BT-MMP-182696; Sun, 24 May 2009 22:36:21 +0000 (Z) Received: from mail-bw0-f224.google.com ([209.85.218.224] [209.85.218.224]) by relay1i.sun.com with ESMTP id BT-MMP-17684527; Sun, 24 May 2009 22:36:21 +0000 (Z) Received: by bwz24 with SMTP id 24so2996337bwz.8 for ; Sun, 24 May 2009 15:35:20 -0700 (PDT) Received: by 10.204.115.139 with SMTP id i11mr6305488bkq.199.1243204520457; Sun, 24 May 2009 15:35:20 -0700 (PDT) Date: Mon, 25 May 2009 00:35:20 +0200 From: Cedric Blancher Subject: Re: Increase the maximum default ufs log size (ldl_maxlogsize) from 64 Mbytes to 512 Mbytes. [PSARC/2009/309 FastTrack timeout 05/25/2009] In-reply-to: <4A119EE3.7080804@sun.com> To: Owen Roberts - Solaris Sustaining Cc: James Carlson , PSARC-ext@sun.com, Brian Utterback Message-id: MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=1K5xdRqNDEuMUknc1QLLPtfOZ+TOE0J+vwW27KVf97E=; b=L/ShY1TmOhciq8y3GjVCOxPlNB48rDnpk3BBtToKJtpHJ5Jj2btO0y1uM6+CRmrFlm U/uZYK0DF7gDtSzmq9DvBd91lYfzu7GZ3KlHWOL3WNrawLgQDf/PZaIbVGtrN9Vy3Qmw e1IQQlBvyq2VwSK4sr+G58fvNzf977/4Kcx7o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=CJtO31aTJKCrM0ontv5kARwBxnFoJNtdAhjmBbVS4NSbXuw/eZMkF3B5N6jFp+/88Z HR4ZaJIwfSHl7joQW/1O07LKg6o+yhb6/a5qgR+HWh1IFrSzZwE0ZRHomWT0GjvvIAlJ U6lI5fnWHgaUwWNGFRi1rgwrehqRPt1o46P9Y= X-PMX-Version: 5.4.1.325704 X-Brightmail-Tracker: AAAAAA== X-Antispam: No, score=0.0/5.0, scanned in 0.181sec at (localhost [127.0.0.1]) by smf-spamd v1.3.1 - http://smfs.sf.net/ References: <200905181244.n4ICi9IS026868@sac.sfbay.sun.com> <18961.23083.839610.646718@gargle.gargle.HOWL> <4A119EE3.7080804@sun.com> Status: RO Content-Length: 608 On 18/05/2009, Owen Roberts - Solaris Sustaining wrote: > James Carlson wrote: > To cover those eventualities (> 13TB & non-default geometry) the log space > requirement based on the number of cylinder groups is calculated, and that > can increase the log size allocated up to 512MB. Will an increased log size improve file system performance if many small files are created and destroyed? For example will a larger log improve performance of a rm -R directory.with.40000.files or tar -xf tar.with.40000.files? -- Cedric Blancher Institute Pasteur