From owner-freebsd-fs@FreeBSD.ORG Sun May 20 02:53:25 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7656C16A400 for ; Sun, 20 May 2007 02:53:25 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout05.yourhostingaccount.com (mailout05.yourhostingaccount.com [65.254.253.41]) by mx1.freebsd.org (Postfix) with ESMTP id 495FD13C45A for ; Sun, 20 May 2007 02:53:25 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan30.yourhostingaccount.com ([10.1.15.30] helo=mailscan30.yourhostingaccount.com) by mailout05.yourhostingaccount.com with esmtp (Exim) id 1Hpb4Y-00088o-KQ for freebsd-fs@freebsd.org; Sat, 19 May 2007 22:23:02 -0400 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] ident=exim) by mailscan30.yourhostingaccount.com with spamscanlookuphost (Exim) id 1Hpb4Y-00060c-JH for freebsd-fs@freebsd.org; Sat, 19 May 2007 22:23:02 -0400 Received: from authsmtp09.yourhostingaccount.com ([10.1.18.9] helo=authsmtp09.yourhostingaccount.com) by mailscan30.yourhostingaccount.com with esmtp (Exim) id 1Hpb4Y-00060Z-DC for freebsd-fs@freebsd.org; Sat, 19 May 2007 22:23:02 -0400 Received: from cpe-65-185-51-114.columbus.res.rr.com ([65.185.51.114] helo=vixen42) by authsmtp09.yourhostingaccount.com with esmtpa (Exim) id 1Hpb4Y-0006xL-60 for freebsd-fs@freebsd.org; Sat, 19 May 2007 22:23:02 -0400 Date: Sat, 19 May 2007 22:25:27 -0400 From: "Zane C.B." To: freebsd-fs@freebsd.org Message-ID: <20070519222527.680ba5c2@vixen42> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 65.185.51.114 X-EN-OrigHost: cpe-65-185-51-114.columbus.res.rr.com Subject: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 02:53:25 -0000 Is passing a password to mount_smbfs non-interactively possible? I know it can't accept it on STDIN by piping it into it. Currently looking at modifying it to accept a environmental variable for it. From owner-freebsd-fs@FreeBSD.ORG Sun May 20 16:33:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A2AE16A469 for ; Sun, 20 May 2007 16:33:41 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout13.yourhostingaccount.com (mailout13.yourhostingaccount.com [65.254.253.105]) by mx1.freebsd.org (Postfix) with ESMTP id EC6CD13C468 for ; Sun, 20 May 2007 16:33:40 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan51.yourhostingaccount.com ([10.1.15.51] helo=mailscan51.yourhostingaccount.com) by mailout13.yourhostingaccount.com with esmtp (Exim) id 1HpoLj-0002a5-V8 for freebsd-fs@freebsd.org; Sun, 20 May 2007 12:33:39 -0400 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] ident=exim) by mailscan51.yourhostingaccount.com with spamscanlookuphost (Exim) id 1HpoLj-0000ZD-P2 for freebsd-fs@freebsd.org; Sun, 20 May 2007 12:33:39 -0400 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] helo=authsmtp08.yourhostingaccount.com) by mailscan51.yourhostingaccount.com with esmtp (Exim) id 1HpoLj-0000Z2-25; Sun, 20 May 2007 12:33:39 -0400 Received: from cpe-65-185-51-114.columbus.res.rr.com ([65.185.51.114] helo=vixen42) by authsmtp08.yourhostingaccount.com with esmtpa (Exim) id 1HpoLi-0000nc-FI; Sun, 20 May 2007 12:33:38 -0400 Date: Sun, 20 May 2007 12:36:07 -0400 From: "Zane C.B." To: Hiroharu Tamaru Message-ID: <20070520123607.4aba7f35@vixen42> In-Reply-To: References: <20070519222527.680ba5c2@vixen42> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 65.185.51.114 X-EN-OrigHost: cpe-65-185-51-114.columbus.res.rr.com Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 16:33:41 -0000 On Mon, 21 May 2007 01:19:58 +0900 Hiroharu Tamaru wrote: > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > Is passing a password to mount_smbfs non-interactively possible? I > > know it can't accept it on STDIN by piping it into it. > > mount_smbfs(8) : > -N Do not ask for a password. At run time, mount_smbfs > reads the ~/.nsmbrc file for additional configuration parameters > and a password. If no password is found, mount_smbfs prompts for > it. > > /usr/share/examples/smbfs/dot.nsmbrc : > [FSERVER:JOE] > # use persistent password cache for user 'joe' > password=$$1767877DF > > I'm using -N for shares w/o passwords; I've never tried .nsmbrc > password myself This is not useful if ~/ is not mounted and you are planning of mounting it using mount_smbfs. That is entirely what I am trying to get to work here. From owner-freebsd-fs@FreeBSD.ORG Sun May 20 16:49:28 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9E2CA16A484 for ; Sun, 20 May 2007 16:49:28 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail3.ecc.u-tokyo.ac.jp (mail3.ecc.u-tokyo.ac.jp [133.11.205.99]) by mx1.freebsd.org (Postfix) with ESMTP id 4674B13C480 for ; Sun, 20 May 2007 16:49:28 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail1.ecc.u-tokyo.ac.jp (mail1.ecc.u-tokyo.ac.jp [133.11.50.203]) by mail3.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 2E04C5B14E2 for ; Mon, 21 May 2007 01:20:38 +0900 (JST) Received: from spam005.ecc.u-tokyo.ac.jp (spam005.ecc.u-tokyo.ac.jp [133.11.50.198]) by mail1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 559BF2A2AEA for ; Mon, 21 May 2007 01:20:36 +0900 (JST) Received: from gin.myn.rcast.u-tokyo.ac.jp (157.82.72.158 [157.82.72.158]) by spam005.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.97) with ESMTP id for ; Mon, 21 May 2007 01:19:59 +0900 Date: Mon, 21 May 2007 01:19:58 +0900 Message-ID: From: Hiroharu Tamaru To: "Zane C.B." In-Reply-To: <20070519222527.680ba5c2@vixen42> References: <20070519222527.680ba5c2@vixen42> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 157.82.72.158 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 16:49:28 -0000 At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > Is passing a password to mount_smbfs non-interactively possible? I > know it can't accept it on STDIN by piping it into it. mount_smbfs(8) : -N Do not ask for a password. At run time, mount_smbfs reads the ~/.nsmbrc file for additional configuration parameters and a password. If no password is found, mount_smbfs prompts for it. /usr/share/examples/smbfs/dot.nsmbrc : [FSERVER:JOE] # use persistent password cache for user 'joe' password=$$1767877DF I'm using -N for shares w/o passwords; I've never tried .nsmbrc password myself From owner-freebsd-fs@FreeBSD.ORG Sun May 20 16:59:19 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E0CC16A421 for ; Sun, 20 May 2007 16:59:19 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail1.ecc.u-tokyo.ac.jp (mail1.ecc.u-tokyo.ac.jp [133.11.50.203]) by mx1.freebsd.org (Postfix) with ESMTP id 16C6013C45E for ; Sun, 20 May 2007 16:59:19 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from spam004.ecc.u-tokyo.ac.jp (spam004.ecc.u-tokyo.ac.jp [133.11.50.197]) by mail1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 0DD982A2AEB for ; Mon, 21 May 2007 01:59:18 +0900 (JST) Received: from gin.myn.rcast.u-tokyo.ac.jp (157.82.72.158 [157.82.72.158]) by spam004.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.97) with ESMTP id for ; Mon, 21 May 2007 01:58:58 +0900 Date: Mon, 21 May 2007 01:58:58 +0900 Message-ID: From: Hiroharu Tamaru To: "Zane C.B." In-Reply-To: <20070520123607.4aba7f35@vixen42> References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 157.82.72.158 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 16:59:19 -0000 At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote: > > On Mon, 21 May 2007 01:19:58 +0900 > Hiroharu Tamaru wrote: > > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > > Is passing a password to mount_smbfs non-interactively possible? I > > > know it can't accept it on STDIN by piping it into it. > > > > mount_smbfs(8) : > > -N Do not ask for a password. At run time, mount_smbfs > > reads the ~/.nsmbrc file for additional configuration parameters > > and a password. If no password is found, mount_smbfs prompts for > > it. > > > > /usr/share/examples/smbfs/dot.nsmbrc : > > [FSERVER:JOE] > > # use persistent password cache for user 'joe' > > password=$$1767877DF > > > > I'm using -N for shares w/o passwords; I've never tried .nsmbrc > > password myself > > This is not useful if ~/ is not mounted and you are planning of > mounting it using mount_smbfs. You never said that. Who's mounting ~user in that case? root? From owner-freebsd-fs@FreeBSD.ORG Sun May 20 17:08:15 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B87B516A469 for ; Sun, 20 May 2007 17:08:15 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout13.yourhostingaccount.com (mailout13.yourhostingaccount.com [65.254.253.105]) by mx1.freebsd.org (Postfix) with ESMTP id 702CD13C483 for ; Sun, 20 May 2007 17:08:15 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan29.yourhostingaccount.com ([10.1.15.29] helo=mailscan29.yourhostingaccount.com) by mailout13.yourhostingaccount.com with esmtp (Exim) id 1HpotC-0001N2-IE for freebsd-fs@freebsd.org; Sun, 20 May 2007 13:08:14 -0400 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by mailscan29.yourhostingaccount.com with spamscanlookuphost (Exim) id 1HpotC-0007wF-DZ for freebsd-fs@freebsd.org; Sun, 20 May 2007 13:08:14 -0400 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by mailscan29.yourhostingaccount.com with esmtp (Exim) id 1HpotB-0007vx-HO; Sun, 20 May 2007 13:08:13 -0400 Received: from cpe-65-185-51-114.columbus.res.rr.com ([65.185.51.114] helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1HpotB-0006Wm-7H; Sun, 20 May 2007 13:08:13 -0400 Date: Sun, 20 May 2007 13:10:42 -0400 From: "Zane C.B." To: Hiroharu Tamaru Message-ID: <20070520131042.2ce78ae0@vixen42> In-Reply-To: References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 65.185.51.114 X-EN-OrigHost: cpe-65-185-51-114.columbus.res.rr.com Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 17:08:15 -0000 On Mon, 21 May 2007 01:58:58 +0900 Hiroharu Tamaru wrote: > At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote: > > > > On Mon, 21 May 2007 01:19:58 +0900 > > Hiroharu Tamaru wrote: > > > > > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > > > Is passing a password to mount_smbfs non-interactively > > > > possible? I know it can't accept it on STDIN by piping it > > > > into it. > > > > > > mount_smbfs(8) : > > > -N Do not ask for a password. At run time, > > > mount_smbfs reads the ~/.nsmbrc file for additional > > > configuration parameters and a password. If no password is > > > found, mount_smbfs prompts for it. > > > > > > /usr/share/examples/smbfs/dot.nsmbrc : > > > [FSERVER:JOE] > > > # use persistent password cache for user 'joe' > > > password=$$1767877DF > > > > > > I'm using -N for shares w/o passwords; I've never tried .nsmbrc > > > password myself > > > > This is not useful if ~/ is not mounted and you are planning of > > mounting it using mount_smbfs. > > You never said that. > Who's mounting ~user in that case? root? Yeah, looking at doing it through PAM. From owner-freebsd-fs@FreeBSD.ORG Sun May 20 17:39:26 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4994E16A46C for ; Sun, 20 May 2007 17:39:26 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail1.ecc.u-tokyo.ac.jp (mail1.ecc.u-tokyo.ac.jp [133.11.50.203]) by mx1.freebsd.org (Postfix) with ESMTP id A81D213C44B for ; Sun, 20 May 2007 17:39:25 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from spam001.ecc.u-tokyo.ac.jp (spam001.ecc.u-tokyo.ac.jp [133.11.50.194]) by mail1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 573C02A2AFC for ; Mon, 21 May 2007 02:39:24 +0900 (JST) Received: from gin.myn.rcast.u-tokyo.ac.jp (157.82.72.158 [157.82.72.158]) by spam001.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.97) with ESMTP id for ; Mon, 21 May 2007 02:39:17 +0900 Date: Mon, 21 May 2007 02:39:17 +0900 Message-ID: From: Hiroharu Tamaru To: "Zane C.B." In-Reply-To: <20070520131042.2ce78ae0@vixen42> References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> <20070520131042.2ce78ae0@vixen42> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 157.82.72.158 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 17:39:26 -0000 At Sun, 20 May 2007 13:10:42 -0400, Zane C.B. wrote: > > On Mon, 21 May 2007 01:58:58 +0900 > Hiroharu Tamaru wrote: > > > At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote: > > > > > > On Mon, 21 May 2007 01:19:58 +0900 > > > Hiroharu Tamaru wrote: > > > > > > > > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > > > > Is passing a password to mount_smbfs non-interactively > > > > > possible? I know it can't accept it on STDIN by piping it > > > > > into it. > > > > > > > > mount_smbfs(8) : > > > > -N Do not ask for a password. At run time, > > > > mount_smbfs reads the ~/.nsmbrc file for additional > > > > configuration parameters and a password. If no password is > > > > found, mount_smbfs prompts for it. > > > > > > > > /usr/share/examples/smbfs/dot.nsmbrc : > > > > [FSERVER:JOE] > > > > # use persistent password cache for user 'joe' > > > > password=$$1767877DF > > > > > > > > I'm using -N for shares w/o passwords; I've never tried .nsmbrc > > > > password myself > > > > > > This is not useful if ~/ is not mounted and you are planning of > > > mounting it using mount_smbfs. > > > > You never said that. > > Who's mounting ~user in that case? root? > > Yeah, looking at doing it through PAM. OK. finally, I see your picture and why you said ENV; For a hack: With the root creds in effect, /root/.nsmbrc is consulted and /etc/nsmb.conf is always consulted (as written in that file). Write the password in either of it, mount, and wipe it out. Other than that, I've no idea. You'd need to wipe out the environment vars if you use it too. From owner-freebsd-fs@FreeBSD.ORG Sun May 20 17:44:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6AC5D16A421 for ; Sun, 20 May 2007 17:44:20 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout03.yourhostingaccount.com (mailout03.yourhostingaccount.com [65.254.254.78]) by mx1.freebsd.org (Postfix) with ESMTP id 24DDB13C4CC for ; Sun, 20 May 2007 17:44:18 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan05.yourhostingaccount.com ([10.1.15.5] helo=mailscan05.yourhostingaccount.com) by mailout03.yourhostingaccount.com with esmtp (Exim) id 1HppS4-00024a-O6 for freebsd-fs@freebsd.org; Sun, 20 May 2007 13:44:16 -0400 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] ident=exim) by mailscan05.yourhostingaccount.com with spamscanlookuphost (Exim) id 1HppS4-00020G-Pj for freebsd-fs@freebsd.org; Sun, 20 May 2007 13:44:16 -0400 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] helo=authsmtp08.yourhostingaccount.com) by mailscan05.yourhostingaccount.com with esmtp (Exim) id 1HppS3-000204-Pu; Sun, 20 May 2007 13:44:15 -0400 Received: from cpe-65-185-51-114.columbus.res.rr.com ([65.185.51.114] helo=vixen42) by authsmtp08.yourhostingaccount.com with esmtpa (Exim) id 1HppS3-0004jX-AQ; Sun, 20 May 2007 13:44:15 -0400 Date: Sun, 20 May 2007 13:46:45 -0400 From: "Zane C.B." To: Hiroharu Tamaru Message-ID: <20070520134645.3d77b75c@vixen42> In-Reply-To: References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> <20070520131042.2ce78ae0@vixen42> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 65.185.51.114 X-EN-OrigHost: cpe-65-185-51-114.columbus.res.rr.com Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 17:44:20 -0000 On Mon, 21 May 2007 02:39:17 +0900 Hiroharu Tamaru wrote: > At Sun, 20 May 2007 13:10:42 -0400, Zane C.B. wrote: > > > > On Mon, 21 May 2007 01:58:58 +0900 > > Hiroharu Tamaru wrote: > > > > > At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote: > > > > > > > > On Mon, 21 May 2007 01:19:58 +0900 > > > > Hiroharu Tamaru wrote: > > > > > > > > > > > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > > > > > Is passing a password to mount_smbfs non-interactively > > > > > > possible? I know it can't accept it on STDIN by piping it > > > > > > into it. > > > > > > > > > > mount_smbfs(8) : > > > > > -N Do not ask for a password. At run time, > > > > > mount_smbfs reads the ~/.nsmbrc file for additional > > > > > configuration parameters and a password. If no password is > > > > > found, mount_smbfs prompts for it. > > > > > > > > > > /usr/share/examples/smbfs/dot.nsmbrc : > > > > > [FSERVER:JOE] > > > > > # use persistent password cache for user 'joe' > > > > > password=$$1767877DF > > > > > > > > > > I'm using -N for shares w/o passwords; I've never > > > > > tried .nsmbrc password myself > > > > > > > > This is not useful if ~/ is not mounted and you are planning > > > > of mounting it using mount_smbfs. > > > > > > You never said that. > > > Who's mounting ~user in that case? root? > > > > Yeah, looking at doing it through PAM. > > OK. finally, I see your picture and why you said ENV; > > For a hack: > With the root creds in effect, /root/.nsmbrc is consulted > and /etc/nsmb.conf is always consulted (as written in that file). > Write the password in either of it, mount, and wipe it out. Not useful since that would require passwords being in that file. > Other than that, I've no idea. > You'd need to wipe out the environment vars if you use it too. Decided against that since D.E.S. pointed out that it would be exposed in /proc. From owner-freebsd-fs@FreeBSD.ORG Sun May 20 18:23:10 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0B35316A46C for ; Sun, 20 May 2007 18:23:10 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from mail1.ecc.u-tokyo.ac.jp (mail1.ecc.u-tokyo.ac.jp [133.11.50.203]) by mx1.freebsd.org (Postfix) with ESMTP id 6758A13C4DE for ; Sun, 20 May 2007 18:23:09 +0000 (UTC) (envelope-from tamaru@myn.rcast.u-tokyo.ac.jp) Received: from spam004.ecc.u-tokyo.ac.jp (spam004.ecc.u-tokyo.ac.jp [133.11.50.197]) by mail1.ecc.u-tokyo.ac.jp (Postfix) with ESMTP id 144AA2A2AE2 for ; Mon, 21 May 2007 03:23:08 +0900 (JST) Received: from gin.myn.rcast.u-tokyo.ac.jp (157.82.72.158 [157.82.72.158]) by spam004.ecc.u-tokyo.ac.jp (SpamBlock.pst 3.4.97) with ESMTP id for ; Mon, 21 May 2007 03:22:47 +0900 Date: Mon, 21 May 2007 03:22:46 +0900 Message-ID: From: Hiroharu Tamaru To: "Zane C.B." In-Reply-To: <20070520134645.3d77b75c@vixen42> References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> <20070520131042.2ce78ae0@vixen42> <20070520134645.3d77b75c@vixen42> User-Agent: User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-IP: 157.82.72.158 X-FROM-DOMAIN: myn.rcast.u-tokyo.ac.jp X-FROM-EMAIL: tamaru@myn.rcast.u-tokyo.ac.jp Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 18:23:10 -0000 At Sun, 20 May 2007 13:46:45 -0400, Zane C.B. wrote: > > On Mon, 21 May 2007 02:39:17 +0900 > Hiroharu Tamaru wrote: > > > At Sun, 20 May 2007 13:10:42 -0400, Zane C.B. wrote: > > > > > > On Mon, 21 May 2007 01:58:58 +0900 > > > Hiroharu Tamaru wrote: > > > > > > > At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote: > > > > > > > > > > On Mon, 21 May 2007 01:19:58 +0900 > > > > > Hiroharu Tamaru wrote: > > > > > > > > > > > > > > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > > > > > > Is passing a password to mount_smbfs non-interactively > > > > > > > possible? I know it can't accept it on STDIN by piping it > > > > > > > into it. > > > > > > > > > > > > mount_smbfs(8) : > > > > > > -N Do not ask for a password. At run time, > > > > > > mount_smbfs reads the ~/.nsmbrc file for additional > > > > > > configuration parameters and a password. If no password is > > > > > > found, mount_smbfs prompts for it. > > > > > > > > > > > > /usr/share/examples/smbfs/dot.nsmbrc : > > > > > > [FSERVER:JOE] > > > > > > # use persistent password cache for user 'joe' > > > > > > password=$$1767877DF > > > > > > > > > > > > I'm using -N for shares w/o passwords; I've never > > > > > > tried .nsmbrc password myself > > > > > > > > > > This is not useful if ~/ is not mounted and you are planning > > > > > of mounting it using mount_smbfs. > > > > > > > > You never said that. > > > > Who's mounting ~user in that case? root? > > > > > > Yeah, looking at doing it through PAM. > > > > OK. finally, I see your picture and why you said ENV; > > > > For a hack: > > With the root creds in effect, /root/.nsmbrc is consulted > > and /etc/nsmb.conf is always consulted (as written in that file). > > Write the password in either of it, mount, and wipe it out. > > Not useful since that would require passwords being in that file. Yeah, I well see that the password lives longer if a file is used (even if you symlink it onto a memory file system), but root can always peek inside the memory as well, and root can often intercept syscalls as well. Anyway, that's why I called it a hack. > > Other than that, I've no idea. > > You'd need to wipe out the environment vars if you use it too. > > Decided against that since D.E.S. pointed out that it would be > exposed in /proc. Yeah, I thought it'd be tough too. If you are going to modify mount_smbfs anyway, you could give it a pipe or a socket as an ARG or ENV, or have it unnamed and inherit it? The password is then send via the pipe or the socket. FWIW, IIRC, some version of ssh-agent used unnamed socket or pipe to limit its access to its descendants only. I don't know if the reason for the change of that enforcement was security-wise or not. From owner-freebsd-fs@FreeBSD.ORG Sun May 20 20:28:44 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E03B16A400 for ; Sun, 20 May 2007 20:28:44 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63012.mail.re1.yahoo.com (web63012.mail.re1.yahoo.com [69.147.96.223]) by mx1.freebsd.org (Postfix) with SMTP id 38F6213C46C for ; Sun, 20 May 2007 20:28:42 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 99675 invoked by uid 60001); 20 May 2007 20:28:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=XDQ7dgs/72jH4wAcFFcx/5Pib+9mvmCSzhv4ozxzj68h1D6Zs7Yk8xTQMDutMZ/goUbDoqncleMe7rQzEEU3gOHaEPjRjeVCDvxnQlBIKuwcsc4zLBsPtxReaDbgjZ3QZghURmnXgMvDLVZLQr0aK1StS2KyHsWhi8PsnumjX6A=; X-YMail-OSG: ZWRTDAsVM1kylkDJ4h1yqQfwrLCZ22pPxPogsCtxl11QQhtT5v.AKJV.lsC7whGwYNHqwNtgnOeYq_bkT8C0HFMZwPZ_44X_vPsZ Received: from [24.118.228.153] by web63012.mail.re1.yahoo.com via HTTP; Sun, 20 May 2007 13:28:41 PDT Date: Sun, 20 May 2007 13:28:41 -0700 (PDT) From: Gore Jarold To: Scott Long In-Reply-To: <464F3178.1020909@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <653845.99663.qm@web63012.mail.re1.yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: dangers of delaying an fsck on busy fileserver ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 20:28:44 -0000 --- Scott Long wrote: > Gore Jarold wrote: > > --- Scott Long wrote: > > > > > >> In an ideal world, the only consequence of > delaying > >> bgfsck is that > >> not all filesystem blocks will be marked free > that > >> should be. So > >> if you deleted a large tree of files before the > >> crash, those blocks > >> might still show up in use until bgfsck > completes. > > > > > > Thank you. Would _you_ do this with valuable data > ? > > > > Very good question =-) If you're using softupdates > then any > damage will have been done when the hard shutdown > happens; bgfsck > won't create any new damage. The biggest problem of > bgfsck beyond > the i/o slowness and near deadlocks that it can > create (modulo the > fixes that the Kostik is working on) is that if it > does encounter > damage that it can't fix automatically, it exits and > leaves the > filesystem inconsistent. So you need to keep a very > close eye on > your logs and check for this, then schedule downtime > when it happens > so you can babysit a full fsck. Ahhh... I think you may have misunderstood my original question. What I am saying is, I don't _ever_ want to do a background fsck. My systems are too busy (and have too large of disks) to deal with the (current) baggage of making a 4 TB snapshot and then bg_fsck'ing. What I am saying is the following: - I set background_fsck_delay="86400" - I tell datacenter techs NOT to call me when the system crashes - just to hit reset. - users bang on the system, as normal, for X hours - all the while the filesystems are _dirty_ and nothing is being done about it - I wake up hours later, unmount the filesystems, and foreground fsck them My goal in all of this is to keep from being woken up in the middle of the night. I don't care about the downtime to the system when I eventually do foreground fsck them, I just don't want to do it in the middle of the night _and_ I don't want my users to have to sit around waiting for me to do the fsck _on top of_ the fsck downtime itself. So ... comments ? I _suspect_ the conclusions are about the same - running on a dirty FS is the same as running on a dirty FS while being bg_fsck'd ... but I want to make sure... ____________________________________________________________________________________Get the free Yahoo! toolbar and rest assured with the added security of spyware protection. http://new.toolbar.yahoo.com/toolbar/features/norton/index.php From owner-freebsd-fs@FreeBSD.ORG Sun May 20 21:39:58 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3657216A400 for ; Sun, 20 May 2007 21:39:58 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id DA33413C465 for ; Sun, 20 May 2007 21:39:57 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l4KLdqGT078009; Sun, 20 May 2007 15:39:54 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4650C028.9060400@samsco.org> Date: Sun, 20 May 2007 15:39:52 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Gore Jarold References: <653845.99663.qm@web63012.mail.re1.yahoo.com> In-Reply-To: <653845.99663.qm@web63012.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Sun, 20 May 2007 15:39:54 -0600 (MDT) X-Spam-Status: No, score=-1.4 required=5.5 tests=ALL_TRUSTED autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-fs@freebsd.org Subject: Re: dangers of delaying an fsck on busy fileserver ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 21:39:58 -0000 Gore Jarold wrote: > --- Scott Long wrote: > >> Gore Jarold wrote: >>> --- Scott Long wrote: >>> >>> >>>> In an ideal world, the only consequence of >> delaying >>>> bgfsck is that >>>> not all filesystem blocks will be marked free >> that >>>> should be. So >>>> if you deleted a large tree of files before the >>>> crash, those blocks >>>> might still show up in use until bgfsck >> completes. >>> >>> Thank you. Would _you_ do this with valuable data >> ? >> Very good question =-) If you're using softupdates >> then any >> damage will have been done when the hard shutdown >> happens; bgfsck >> won't create any new damage. The biggest problem of >> bgfsck beyond >> the i/o slowness and near deadlocks that it can >> create (modulo the >> fixes that the Kostik is working on) is that if it >> does encounter >> damage that it can't fix automatically, it exits and >> leaves the >> filesystem inconsistent. So you need to keep a very >> close eye on >> your logs and check for this, then schedule downtime >> when it happens >> so you can babysit a full fsck. > > > Ahhh... I think you may have misunderstood my original > question. What I am saying is, I don't _ever_ want to > do a background fsck. My systems are too busy (and > have too large of disks) to deal with the (current) > baggage of making a 4 TB snapshot and then > bg_fsck'ing. > > What I am saying is the following: > > - I set background_fsck_delay="86400" > > - I tell datacenter techs NOT to call me when the > system crashes - just to hit reset. > > - users bang on the system, as normal, for X hours - > all the while the filesystems are _dirty_ and nothing > is being done about it > > - I wake up hours later, unmount the filesystems, and > foreground fsck them > > My goal in all of this is to keep from being woken up > in the middle of the night. I don't care about the > downtime to the system when I eventually do foreground > fsck them, I just don't want to do it in the middle of > the night _and_ I don't want my users to have to sit > around waiting for me to do the fsck _on top of_ the > fsck downtime itself. > > So ... comments ? I _suspect_ the conclusions are > about the same - running on a dirty FS is the same as > running on a dirty FS while being bg_fsck'd ... but I > want to make sure... > So yeah, the only consequence of doing the preen but not the bgfsck is that you might loose some free space after a crash. How much depends on your workload. If you're deleting large files or large trees of files, the loss might be significant. It sounds like you understand how to manage that, though, so it'll probably be a fine solution for you. Scott From owner-freebsd-fs@FreeBSD.ORG Sun May 20 23:22:44 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA22916A421 for ; Sun, 20 May 2007 23:22:44 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailout12.yourhostingaccount.com (mailout12.yourhostingaccount.com [65.254.253.98]) by mx1.freebsd.org (Postfix) with ESMTP id 8480013C458 for ; Sun, 20 May 2007 23:22:44 +0000 (UTC) (envelope-from SRS0=AAamUv=KV=vvelox.net=v.velox@yourhostingaccount.com) Received: from mailscan41.yourhostingaccount.com ([10.1.15.41] helo=mailscan41.yourhostingaccount.com) by mailout12.yourhostingaccount.com with esmtp (Exim) id 1HpujZ-0001JI-Je for freebsd-fs@freebsd.org; Sun, 20 May 2007 19:22:41 -0400 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] ident=exim) by mailscan41.yourhostingaccount.com with spamscanlookuphost (Exim) id 1HpujZ-0007Pg-Gs for freebsd-fs@freebsd.org; Sun, 20 May 2007 19:22:41 -0400 Received: from authsmtp10.yourhostingaccount.com ([10.1.18.10] helo=authsmtp10.yourhostingaccount.com) by mailscan41.yourhostingaccount.com with esmtp (Exim) id 1HpujY-0007PO-6V; Sun, 20 May 2007 19:22:40 -0400 Received: from cpe-65-185-51-114.columbus.res.rr.com ([65.185.51.114] helo=vixen42) by authsmtp10.yourhostingaccount.com with esmtpa (Exim) id 1HpujX-00026u-QS; Sun, 20 May 2007 19:22:40 -0400 Date: Sun, 20 May 2007 19:25:11 -0400 From: "Zane C.B." To: Hiroharu Tamaru Message-ID: <20070520192511.7ea7188a@vixen42> In-Reply-To: References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> <20070520131042.2ce78ae0@vixen42> <20070520134645.3d77b75c@vixen42> X-Mailer: Claws Mail 2.9.1 (GTK+ 2.10.12; i386-portbld-freebsd6.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-EN-UserInfo: 0d1ca1697cdb7a831d4877828571b7ab:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox2 Sender: "Zane C.B." X-EN-OrigIP: 65.185.51.114 X-EN-OrigHost: cpe-65-185-51-114.columbus.res.rr.com Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 May 2007 23:22:45 -0000 On Mon, 21 May 2007 03:22:46 +0900 Hiroharu Tamaru wrote: > At Sun, 20 May 2007 13:46:45 -0400, > Zane C.B. wrote: > > > > On Mon, 21 May 2007 02:39:17 +0900 > > Hiroharu Tamaru wrote: > > > > > At Sun, 20 May 2007 13:10:42 -0400, Zane C.B. wrote: > > > > > > > > On Mon, 21 May 2007 01:58:58 +0900 > > > > Hiroharu Tamaru wrote: > > > > > > > > > At Sun, 20 May 2007 12:36:07 -0400, Zane C.B. wrote: > > > > > > > > > > > > On Mon, 21 May 2007 01:19:58 +0900 > > > > > > Hiroharu Tamaru wrote: > > > > > > > > > > > > > > > > > > > > At Sat, 19 May 2007 22:25:27 -0400, Zane C.B. wrote: > > > > > > > > Is passing a password to mount_smbfs non-interactively > > > > > > > > possible? I know it can't accept it on STDIN by > > > > > > > > piping it into it. > > > > > > > > > > > > > > mount_smbfs(8) : > > > > > > > -N Do not ask for a password. At run time, > > > > > > > mount_smbfs reads the ~/.nsmbrc file for additional > > > > > > > configuration parameters and a password. If no > > > > > > > password is found, mount_smbfs prompts for it. > > > > > > > > > > > > > > /usr/share/examples/smbfs/dot.nsmbrc : > > > > > > > [FSERVER:JOE] > > > > > > > # use persistent password cache for user 'joe' > > > > > > > password=$$1767877DF > > > > > > > > > > > > > > I'm using -N for shares w/o passwords; I've never > > > > > > > tried .nsmbrc password myself > > > > > > > > > > > > This is not useful if ~/ is not mounted and you are > > > > > > planning of mounting it using mount_smbfs. > > > > > > > > > > You never said that. > > > > > Who's mounting ~user in that case? root? > > > > > > > > Yeah, looking at doing it through PAM. > > > > > > OK. finally, I see your picture and why you said ENV; > > > > > > For a hack: > > > With the root creds in effect, /root/.nsmbrc is consulted > > > and /etc/nsmb.conf is always consulted (as written in that > > > file). Write the password in either of it, mount, and wipe it > > > out. > > > > Not useful since that would require passwords being in that file. > > Yeah, I well see that the password lives longer if a file is > used (even if you symlink it onto a memory file system), but > root can always peek inside the memory as well, and root can > often intercept syscalls as well. > Anyway, that's why I called it a hack. > > > > Other than that, I've no idea. > > > You'd need to wipe out the environment vars if you use it too. > > > > Decided against that since D.E.S. pointed out that it would be > > exposed in /proc. > > Yeah, I thought it'd be tough too. > > If you are going to modify mount_smbfs anyway, you could > give it a pipe or a socket as an ARG or ENV, or have it > unnamed and inherit it? The password is then send via the > pipe or the socket. Doing it as a ARG would be very unsecure and as a ENV unsecure if procfs is in use. I created a patch for pam_exec, but D.E.S. pointed out the procfs issue to me. > FWIW, IIRC, some version of ssh-agent used unnamed socket or > pipe to limit its access to its descendants only. I don't > know if the reason for the change of that enforcement was > security-wise or not. Yeah, going to have to look at that and expand my C skills some more. From owner-freebsd-fs@FreeBSD.ORG Mon May 21 03:55:52 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8001616A400 for ; Mon, 21 May 2007 03:55:52 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3C9AB13C4AE for ; Mon, 21 May 2007 03:55:52 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (andersonbox1.centtech.com [192.168.42.21]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id l4L3tlVR070845; Sun, 20 May 2007 22:55:48 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <46511843.4010205@freebsd.org> Date: Sun, 20 May 2007 22:55:47 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Gore Jarold References: <653845.99663.qm@web63012.mail.re1.yahoo.com> In-Reply-To: <653845.99663.qm@web63012.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3272/Sun May 20 20:06:25 2007 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-1.6 required=8.0 tests=AWL, BAYES_05, WHILE_YOU_SLEEP autolearn=no version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: dangers of delaying an fsck on busy fileserver ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 03:55:52 -0000 On 05/20/07 15:28, Gore Jarold wrote: > --- Scott Long wrote: > >> Gore Jarold wrote: >>> --- Scott Long wrote: >>> >>> >>>> In an ideal world, the only consequence of >> delaying >>>> bgfsck is that >>>> not all filesystem blocks will be marked free >> that >>>> should be. So >>>> if you deleted a large tree of files before the >>>> crash, those blocks >>>> might still show up in use until bgfsck >> completes. >>> >>> Thank you. Would _you_ do this with valuable data >> ? >> Very good question =-) If you're using softupdates >> then any >> damage will have been done when the hard shutdown >> happens; bgfsck >> won't create any new damage. The biggest problem of >> bgfsck beyond >> the i/o slowness and near deadlocks that it can >> create (modulo the >> fixes that the Kostik is working on) is that if it >> does encounter >> damage that it can't fix automatically, it exits and >> leaves the >> filesystem inconsistent. So you need to keep a very >> close eye on >> your logs and check for this, then schedule downtime >> when it happens >> so you can babysit a full fsck. > > > Ahhh... I think you may have misunderstood my original > question. What I am saying is, I don't _ever_ want to > do a background fsck. My systems are too busy (and > have too large of disks) to deal with the (current) > baggage of making a 4 TB snapshot and then > bg_fsck'ing. > > What I am saying is the following: > > - I set background_fsck_delay="86400" > > - I tell datacenter techs NOT to call me when the > system crashes - just to hit reset. > > - users bang on the system, as normal, for X hours - > all the while the filesystems are _dirty_ and nothing > is being done about it > > - I wake up hours later, unmount the filesystems, and > foreground fsck them > > My goal in all of this is to keep from being woken up > in the middle of the night. I don't care about the > downtime to the system when I eventually do foreground > fsck them, I just don't want to do it in the middle of > the night _and_ I don't want my users to have to sit > around waiting for me to do the fsck _on top of_ the > fsck downtime itself. > > So ... comments ? I _suspect_ the conclusions are > about the same - running on a dirty FS is the same as > running on a dirty FS while being bg_fsck'd ... but I > want to make sure... So can't you turn off background fsck, and set fsck_y_enable="YES"? That would allow your NOC to hit reset, and it'll come back and fsck in the foreground while you sleep. Eric From owner-freebsd-fs@FreeBSD.ORG Mon May 21 04:26:33 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D059D16A46E for ; Mon, 21 May 2007 04:26:33 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 7E51D13C46A for ; Mon, 21 May 2007 04:26:33 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l4L4QShV084063; Sun, 20 May 2007 22:26:29 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <46511F74.4090303@samsco.org> Date: Sun, 20 May 2007 22:26:28 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Eric Anderson References: <653845.99663.qm@web63012.mail.re1.yahoo.com> <46511843.4010205@freebsd.org> In-Reply-To: <46511843.4010205@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Sun, 20 May 2007 22:26:29 -0600 (MDT) X-Spam-Status: No, score=-1.0 required=5.5 tests=ALL_TRUSTED,WHILE_YOU_SLEEP autolearn=failed version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-fs@freebsd.org, Gore Jarold Subject: Re: dangers of delaying an fsck on busy fileserver ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 04:26:33 -0000 Eric Anderson wrote: > On 05/20/07 15:28, Gore Jarold wrote: >> --- Scott Long wrote: >> >>> Gore Jarold wrote: >>>> --- Scott Long wrote: >>>> >>>> >>>>> In an ideal world, the only consequence of >>> delaying >>>>> bgfsck is that >>>>> not all filesystem blocks will be marked free >>> that >>>>> should be. So >>>>> if you deleted a large tree of files before the >>>>> crash, those blocks >>>>> might still show up in use until bgfsck >>> completes. >>>> >>>> Thank you. Would _you_ do this with valuable data >>> ? >>> Very good question =-) If you're using softupdates >>> then any >>> damage will have been done when the hard shutdown >>> happens; bgfsck >>> won't create any new damage. The biggest problem of >>> bgfsck beyond >>> the i/o slowness and near deadlocks that it can >>> create (modulo the >>> fixes that the Kostik is working on) is that if it >>> does encounter >>> damage that it can't fix automatically, it exits and >>> leaves the filesystem inconsistent. So you need to keep a very >>> close eye on >>> your logs and check for this, then schedule downtime >>> when it happens >>> so you can babysit a full fsck. >> >> >> Ahhh... I think you may have misunderstood my original >> question. What I am saying is, I don't _ever_ want to >> do a background fsck. My systems are too busy (and >> have too large of disks) to deal with the (current) >> baggage of making a 4 TB snapshot and then >> bg_fsck'ing. >> >> What I am saying is the following: >> >> - I set background_fsck_delay="86400" >> >> - I tell datacenter techs NOT to call me when the >> system crashes - just to hit reset. >> >> - users bang on the system, as normal, for X hours - >> all the while the filesystems are _dirty_ and nothing >> is being done about it >> >> - I wake up hours later, unmount the filesystems, and >> foreground fsck them >> >> My goal in all of this is to keep from being woken up >> in the middle of the night. I don't care about the >> downtime to the system when I eventually do foreground >> fsck them, I just don't want to do it in the middle of >> the night _and_ I don't want my users to have to sit >> around waiting for me to do the fsck _on top of_ the >> fsck downtime itself. >> >> So ... comments ? I _suspect_ the conclusions are >> about the same - running on a dirty FS is the same as >> running on a dirty FS while being bg_fsck'd ... but I >> want to make sure... > > So can't you turn off background fsck, and set fsck_y_enable="YES"? That > would allow your NOC to hit reset, and it'll come back and fsck in the > foreground while you sleep. > > Eric > > It sounds like he's trying to avoid the immediate downtime that a fgfsck represents and instead defer it to a later time when it's more convenient. In theory, UFS+SU should allow this. Scott From owner-freebsd-fs@FreeBSD.ORG Mon May 21 04:46:40 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8287716A400 for ; Mon, 21 May 2007 04:46:40 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 5687113C4C8 for ; Mon, 21 May 2007 04:46:40 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id C4A4528431; Sun, 20 May 2007 23:14:45 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 4FFB661C42; Sun, 20 May 2007 23:14:45 -0500 (CDT) Date: Sun, 20 May 2007 23:14:45 -0500 From: "Matthew D. Fuller" To: "Zane C.B." Message-ID: <20070521041445.GB78897@over-yonder.net> References: <20070519222527.680ba5c2@vixen42> <20070520123607.4aba7f35@vixen42> <20070520131042.2ce78ae0@vixen42> <20070520134645.3d77b75c@vixen42> <20070520192511.7ea7188a@vixen42> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070520192511.7ea7188a@vixen42> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.14-fullermd.3 (2007-02-12) Cc: freebsd-fs@freebsd.org Subject: Re: mount_smbfs and non-interactively passing a password to it X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 04:46:40 -0000 On Sun, May 20, 2007 at 07:25:11PM -0400 I heard the voice of Zane C.B., and lo! it spake thus: > On Mon, 21 May 2007 03:22:46 +0900 > Hiroharu Tamaru wrote: > > > FWIW, IIRC, some version of ssh-agent used unnamed socket or pipe > > to limit its access to its descendants only. I don't know if the > > reason for the change of that enforcement was security-wise or > > not. > > Yeah, going to have to look at that and expand my C skills some > more. Note pw(8)'s '-h' option to pass the password over a given FD. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-fs@FreeBSD.ORG Mon May 21 12:46:48 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E630616A46B for ; Mon, 21 May 2007 12:46:48 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id B317013C44B for ; Mon, 21 May 2007 12:46:48 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l4LCkl71070833; Mon, 21 May 2007 07:46:48 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <465194B7.6070807@freebsd.org> Date: Mon, 21 May 2007 07:46:47 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070420) MIME-Version: 1.0 To: Scott Long References: <653845.99663.qm@web63012.mail.re1.yahoo.com> <46511843.4010205@freebsd.org> <46511F74.4090303@samsco.org> In-Reply-To: <46511F74.4090303@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3273/Mon May 21 00:31:50 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=8.0 tests=AWL, BAYES_00, WHILE_YOU_SLEEP autolearn=no version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org, Gore Jarold Subject: Re: dangers of delaying an fsck on busy fileserver ? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 12:46:49 -0000 On 05/20/07 23:26, Scott Long wrote: > Eric Anderson wrote: >> On 05/20/07 15:28, Gore Jarold wrote: >>> --- Scott Long wrote: >>> >>>> Gore Jarold wrote: >>>>> --- Scott Long wrote: >>>>> >>>>> >>>>>> In an ideal world, the only consequence of >>>> delaying >>>>>> bgfsck is that >>>>>> not all filesystem blocks will be marked free >>>> that >>>>>> should be. So >>>>>> if you deleted a large tree of files before the >>>>>> crash, those blocks >>>>>> might still show up in use until bgfsck >>>> completes. >>>>> Thank you. Would _you_ do this with valuable data >>>> ? >>>> Very good question =-) If you're using softupdates >>>> then any >>>> damage will have been done when the hard shutdown >>>> happens; bgfsck >>>> won't create any new damage. The biggest problem of >>>> bgfsck beyond >>>> the i/o slowness and near deadlocks that it can >>>> create (modulo the >>>> fixes that the Kostik is working on) is that if it >>>> does encounter >>>> damage that it can't fix automatically, it exits and >>>> leaves the filesystem inconsistent. So you need to keep a very >>>> close eye on >>>> your logs and check for this, then schedule downtime >>>> when it happens >>>> so you can babysit a full fsck. >>> >>> Ahhh... I think you may have misunderstood my original >>> question. What I am saying is, I don't _ever_ want to >>> do a background fsck. My systems are too busy (and >>> have too large of disks) to deal with the (current) >>> baggage of making a 4 TB snapshot and then >>> bg_fsck'ing. >>> >>> What I am saying is the following: >>> >>> - I set background_fsck_delay="86400" >>> >>> - I tell datacenter techs NOT to call me when the >>> system crashes - just to hit reset. >>> >>> - users bang on the system, as normal, for X hours - >>> all the while the filesystems are _dirty_ and nothing >>> is being done about it >>> >>> - I wake up hours later, unmount the filesystems, and >>> foreground fsck them >>> >>> My goal in all of this is to keep from being woken up >>> in the middle of the night. I don't care about the >>> downtime to the system when I eventually do foreground >>> fsck them, I just don't want to do it in the middle of >>> the night _and_ I don't want my users to have to sit >>> around waiting for me to do the fsck _on top of_ the >>> fsck downtime itself. >>> >>> So ... comments ? I _suspect_ the conclusions are >>> about the same - running on a dirty FS is the same as >>> running on a dirty FS while being bg_fsck'd ... but I >>> want to make sure... >> So can't you turn off background fsck, and set fsck_y_enable="YES"? That >> would allow your NOC to hit reset, and it'll come back and fsck in the >> foreground while you sleep. >> >> Eric >> >> > > It sounds like he's trying to avoid the immediate downtime that a fgfsck > represents and instead defer it to a later time when it's more > convenient. In theory, UFS+SU should allow this. Yea, from what I read though, it sounded like he just wanted to sleep without having to watch fsck's run. :) Eric From owner-freebsd-fs@FreeBSD.ORG Mon May 21 16:10:07 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 01E7C16A468; Mon, 21 May 2007 16:10:07 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (www.unsane.co.uk [85.233.185.162]) by mx1.freebsd.org (Postfix) with ESMTP id 4DCEC13C44B; Mon, 21 May 2007 16:10:05 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from prawn.unsane.co.uk (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id l4LFeKLo093159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 21 May 2007 16:40:21 +0100 (BST) (envelope-from jhary@unsane.co.uk) Message-ID: <4651BD6F.5050301@unsane.co.uk> Date: Mon, 21 May 2007 16:40:31 +0100 From: Vince User-Agent: Thunderbird 2.0.0.0 (X11/20070516) MIME-Version: 1.0 To: Craig Boston , Kris Kennaway , freebsd-current@FreeBSD.org, Pawel Jakub Dawidek , freebsd-fs@FreeBSD.org References: <20070407131353.GE63916@garage.freebsd.pl> <4617A3A6.60804@kasimir.com> <20070407165759.GG8831@cicely12.cicely.de> <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> In-Reply-To: <20070410014233.GD8189@nowhere> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 16:10:07 -0000 Craig Boston wrote: > On Mon, Apr 09, 2007 at 08:30:35PM -0500, Craig Boston wrote: >> Even the vm.zone breakdown seems to be gone in current so apparently my >> knowledge of such things is becoming obsolete :) > > But vmstat -m still works > > ... > > solaris 145806 122884K - 15319671 16,32,64,128,256,512,1024,2048,4096 > ... > > Whoa! That's a lot of kernel memory. Meanwhile... > > kstat.zfs.misc.arcstats.size: 33554944 > (which is just barely above vfs.zfs.arc_min) > > So I don't think it's the arc cache (yeah I know that's redundant) that > is the problem. Seems like something elsewhere in zfs is allocating > large amounts of memory and not letting it go, and even the cache is > having to shrink to its minimum size due to the memory pressure. > > It didn't panic this time, so when the tar finished I tried a "zfs > unmount /usr/ports". This caused the "solaris" entry to drop down to > about 64MB, so it's not a leak. It could just be that ZFS needs lots of > memory to operate if it keeps a lot of metadata for each file in memory. > > The sheer # of allocations still seems excessive though. It was well > over 20 million by the time the tar process exited. > I dont suppose that there are any other tunables people could suggest? I got a shiny new(well old but new to me) dual opteron board and dual 250 sata drives and though i'd try putting it in as my home server with everything but / on zfs since i've had my /usr/ports on my laptop as compressed zfs since very shortly after it was commited. After a few kmem_map: too small" panics I re-read this thread and put vm.kmem_size_max and vm.kmem_size up to 512M and vfs.zfs.arc_min vfs.zfs.arc_max down to 65 megs. This did get me past "portsnap extract" but a make buildworld still got me the same panic. vmstat -z showed a steady growth. This is with a generic -CURRENT from friday. I'm happy to provide any useful information once I get home and reboot it. Thanks, Vince > Craig > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Mon May 21 16:19:03 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EF2A416A400 for ; Mon, 21 May 2007 16:19:03 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63013.mail.re1.yahoo.com (web63013.mail.re1.yahoo.com [69.147.96.240]) by mx1.freebsd.org (Postfix) with SMTP id B4C4413C448 for ; Mon, 21 May 2007 16:19:03 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 56107 invoked by uid 60001); 21 May 2007 16:19:02 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=d5+XSBsNKTO8TxsPpH2K8wiuwGjITXELcStnkpVQyFjdcxF3lCl+20ESaSIanwywTcOvByB+cq6icblTz5ziYSzgOYSqqhxUA/j3EV7uwT7USJUCrqdJuCAjsSRAtCP1mGPuclqeGBgbJ6EwzeHbbS84kGE0MpiNaP3ejrymQSE=; X-YMail-OSG: gQNlbbIVM1n5m4izZr6Jm2xhMystNPq.RCYz1QPS_TNXiLi3bH36ef2AbMh2EsQqW8xKCwIoJVm.zcMatH1k5AwGn3mAnQ2gHdUg Received: from [24.118.228.153] by web63013.mail.re1.yahoo.com via HTTP; Mon, 21 May 2007 09:19:02 PDT Date: Mon, 21 May 2007 09:19:02 -0700 (PDT) From: Gore Jarold To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <829849.56057.qm@web63013.mail.re1.yahoo.com> Subject: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 16:19:04 -0000 (I love FreeBSD. This is not a troll. If all you have to contribute is "stop spreading FUD" or "write some code yourself" please accept my apologies.) I have been extremely dissatisfied with the stability of the FreeBSD UFS/UFS2 implementation throughout all of 5.x and 6.x. I can take any random release from this period and halt/lock/crash it with basic and uninteresting filesystem operations. In early 5.x it was simply big inode movements from disk to disk. Later it was multiple snapshots. In 6.x any number of seemingly benign operations (filling a disk, using quotas, dense (lots of inodes) deletes and copies) and each time some or all of these problems are solved in one release, slightly different versions of the same problem show up in the next one. For instance, snapshot stability got a lot better from 6.0 to 6.2, but now 6.2 has problems just moving and deleting lots of inodes. I am running _nothing interesting_. I don't even run snapshots anymore ... and as you can see from other posts, I am crashing/halting/etc. all over the place. This is on systems that do nothing but TCP (scp, ftp) file service and some big (rm, cp) movements of inodes once in a while. In other words, my setup is as vanilla as it gets. It's not the hardware (happens on 3ware, adaptec, etc.) (different systems). It's not my esoteric config (I take generic kernel and just delete the devices I don't use) ... also I have no custom sysctls/loader.conf So I am at my wits end. Since early 2004 there has not been a single release version of FreeBSD (well, except _perhaps_ 6.1-RELEASE ...) that I don't regularly knock over with _simple, generic movements of files_. So my plea for help is as follows: a) am I really the only person in the world that moves around millions of inodes throughout the day ? Am I the only person in the world that has ever filled up a snapshotted FS (or a quota'd FS, for that matter) ? Am I the only person in the world that does a mass deletion of several hundred thousand inodes several times per day ? OR: b) am I just stupid ? Is everyone doing this, and there is 3 pages of sysctls and kernel tunes that everyone does to their system when they are going to use it this way ? Am I just naive for taking a release and paring down GENERIC and attempting to run as-is out of the box without major tuning ? If so, can I see those tunes/sysctls ? I am _really_ hoping that it is (b) ... I would much rather look back on all of this frustration as my own fault than have the burden of proving all of this (as I will no doubt be called upon to do). (1) Thanks. Please add your comments... (1) just load up 6.2 and cp/rm a few million inodes around. Or turn on quotas and fill your filesystem up. Kaboom. ____________________________________________________________________________________ Park yourself in front of a world of choices in alternative vehicles. Visit the Yahoo! Auto Green Center. http://autos.yahoo.com/green_center/ From owner-freebsd-fs@FreeBSD.ORG Mon May 21 16:21:40 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C23C16A468; Mon, 21 May 2007 16:21:40 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from mxfep03.bredband.com (mxfep03.bredband.com [195.54.107.76]) by mx1.freebsd.org (Postfix) with ESMTP id A0F4C13C43E; Mon, 21 May 2007 16:21:39 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from ironport.bredband.com ([195.54.107.82] [195.54.107.82]) by mxfep03.bredband.com with ESMTP id <20070521162138.BCLQ23113.mxfep03.bredband.com@ironport.bredband.com>; Mon, 21 May 2007 18:21:38 +0200 Received: from c-5416e555.03-51-73746f3.cust.bredbandsbolaget.se (HELO scode.mine.nu) ([85.229.22.84]) by ironport.bredband.com with ESMTP; 21 May 2007 18:21:38 +0200 Received: from scode.mine.nu (localhost [127.0.0.1]) by scode.mine.nu (Postfix) with ESMTP id 4C2E5C446; Mon, 21 May 2007 18:21:37 +0200 (CEST) Message-ID: <4651C707.2080301@infidyne.com> Date: Mon, 21 May 2007 18:21:27 +0200 From: Peter Schuller User-Agent: Thunderbird 2.0.0.0 (X11/20070501) MIME-Version: 1.0 To: Vince References: <20070407131353.GE63916@garage.freebsd.pl> <4617A3A6.60804@kasimir.com> <20070407165759.GG8831@cicely12.cicely.de> <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> In-Reply-To: <4651BD6F.5050301@unsane.co.uk> X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig8D68A48824DCB6A968FC5F92" Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 16:21:40 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig8D68A48824DCB6A968FC5F92 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > I dont suppose that there are any other tunables people could suggest? = I > got a shiny new(well old but new to me) dual opteron board and dual 250= > sata drives and though i'd try putting it in as my home server with > everything but / on zfs since i've had my /usr/ports on my laptop as > compressed zfs since very shortly after it was commited. > After a few kmem_map: too small" panics I re-read this thread and put > vm.kmem_size_max and vm.kmem_size up to 512M and vfs.zfs.arc_min > vfs.zfs.arc_max down to 65 megs. This did get me past "portsnap extract= " > but a make buildworld still got me the same panic. vmstat -z showed a > steady growth. This is with a generic -CURRENT from friday. I'm happy t= o > provide any useful information once I get home and reboot it. Decrease kern.maxvnodes. To 3/4 I believe was the recommendation, or 2/3. I have it pretty significantly turned down to get rid of the issue. --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --------------enig8D68A48824DCB6A968FC5F92 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGUccQDNor2+l1i30RCKslAKCijpvn86Ho6iQM/C7upTpLyh01DQCaAvwO f6eQoNLSy9BVsnkm/dD689c= =oFZZ -----END PGP SIGNATURE----- --------------enig8D68A48824DCB6A968FC5F92-- From owner-freebsd-fs@FreeBSD.ORG Mon May 21 16:24:33 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30C1616A421; Mon, 21 May 2007 16:24:33 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id DFC6813C447; Mon, 21 May 2007 16:24:32 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 60515208E; Mon, 21 May 2007 18:24:29 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 5097F2086; Mon, 21 May 2007 18:24:29 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 37DA8576F; Mon, 21 May 2007 18:24:29 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Vince References: <20070407131353.GE63916@garage.freebsd.pl> <4617A3A6.60804@kasimir.com> <20070407165759.GG8831@cicely12.cicely.de> <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> Date: Mon, 21 May 2007 18:24:29 +0200 In-Reply-To: <4651BD6F.5050301@unsane.co.uk> (jhary@unsane.co.uk's message of "Mon\, 21 May 2007 16\:40\:31 +0100") Message-ID: <86lkfiqh4y.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@FreeBSD.org, Craig Boston , freebsd-current@FreeBSD.org, Pawel Jakub Dawidek , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 16:24:33 -0000 Vince writes: > I dont suppose that there are any other tunables people could suggest? sysctl kern.maxvnodes=3D50000 Also, disabling atime on all ZFS file systems will greatly improve performance and reduce the frequency of ATA stalls. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Mon May 21 16:40:44 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E7EC16A469; Mon, 21 May 2007 16:40:44 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id E570813C44C; Mon, 21 May 2007 16:40:43 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 2FDAA487F0; Mon, 21 May 2007 18:40:41 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 79E5545683; Mon, 21 May 2007 18:40:37 +0200 (CEST) Date: Mon, 21 May 2007 18:40:33 +0200 From: Pawel Jakub Dawidek To: Dag-Erling Sm??rgrav Message-ID: <20070521164033.GA2975@garage.freebsd.pl> References: <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <86lkfiqh4y.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline In-Reply-To: <86lkfiqh4y.fsf@dwp.des.no> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: Craig Boston , freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Kris Kennaway , ups@FreeBSD.org, Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 16:40:44 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 21, 2007 at 06:24:29PM +0200, Dag-Erling Sm??rgrav wrote: > Vince writes: > > I dont suppose that there are any other tunables people could suggest? >=20 > sysctl kern.maxvnodes=3D50000 >=20 > Also, disabling atime on all ZFS file systems will greatly improve > performance and reduce the frequency of ATA stalls. Does anyone seen this problem on amd64? Because after discussion with ups@ at devsummit, I don't think this is a problem there. UMA uses direct mapping on amd64 for small allocation (just like vnode structures). --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGUcuBForvXbEpPzQRAikeAKCu8N5XjfHwFHFaPAKScUFnWErHzQCgsjMu dVFQjRGwAqAgHSqViJO/VdI= =B8wJ -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- From owner-freebsd-fs@FreeBSD.ORG Mon May 21 17:00:03 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 91C3716A41F for ; Mon, 21 May 2007 17:00:03 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.226]) by mx1.freebsd.org (Postfix) with ESMTP id 44AEB13C45E for ; Mon, 21 May 2007 17:00:03 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by wr-out-0506.google.com with SMTP id 70so1331461wra for ; Mon, 21 May 2007 10:00:02 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=I8ct6k7H4pYFGl2lUTtEInRaiDLYNPa11jxoiVTm6DqPvxBjSEZ6vctkbVmFFzkZ4QtA+RdgQdP+iH6uo+1Ro7k3C5EEGQqIvhHLf3gb6RqePZRkXBW1b67I+NEunnrjivXvUfRlvQUZYoNk7onQwm7z0MMqytKf3QiUnkA7G4w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=knahjLeRJ8d00Wg63gfq21a7OvNv18Fj0WWI1YAWyzO7r04dFPi2x+1W/pY7UBuNYayM9cupm2pg1KPJ65kwlEXEG+vMy7bOZix+UPLypkgpVj5rgV4n+MqJ3h4Wjn6F7pLsvum6wEY2bEUe9tRbe4ZOunU8uE415a9FHao6Whg= Received: by 10.114.26.1 with SMTP id 1mr2778899waz.1179766802111; Mon, 21 May 2007 10:00:02 -0700 (PDT) Received: by 10.114.194.12 with HTTP; Mon, 21 May 2007 10:00:02 -0700 (PDT) Message-ID: Date: Mon, 21 May 2007 19:00:02 +0200 From: "Claus Guttesen" To: "Pawel Jakub Dawidek" In-Reply-To: <20070521164033.GA2975@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070407180319.GH8831@cicely12.cicely.de> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <86lkfiqh4y.fsf@dwp.des.no> <20070521164033.GA2975@garage.freebsd.pl> Cc: Craig Boston , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Kris Kennaway , ups@freebsd.org, Dag-Erling Sm??rgrav , Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 17:00:03 -0000 > > > I dont suppose that there are any other tunables people could suggest? > > sysctl kern.maxvnodes=50000 > > > > Also, disabling atime on all ZFS file systems will greatly improve > > performance and reduce the frequency of ATA stalls. > > Does anyone seen this problem on amd64? Because after discussion with > ups@ at devsummit, I don't think this is a problem there. UMA uses > direct mapping on amd64 for small allocation (just like vnode > structures). I have just done a clean install of current (amd64) and upgraded to gcc 4.2 and installed xorg with /usr/local, /usr/src, /usr/obj on zfs. No problems, except that one particular file would make my system swap 1.1 GB a couple of times before the file eventually compiled :-) When I tried to generate a xorg.conf file my machine stopped and I had to push the reset-button. I thought it was a mix of zfs and X so I moved /usr/local from zfs to ufs and disabled zfs and rebooted but it still stopped. After I copied an old xorg.conf X would start fine. So it was probably due to a bad probe. I'm compiling kdebase atm. and still no need to adjust settings. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare. From owner-freebsd-fs@FreeBSD.ORG Mon May 21 17:38:58 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BC6A116A46C for ; Mon, 21 May 2007 17:38:58 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7E5F313C45B for ; Mon, 21 May 2007 17:38:58 +0000 (UTC) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id B336C8442A for ; Mon, 21 May 2007 19:12:13 +0200 (CEST) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 32412-07 for ; Mon, 21 May 2007 19:12:07 +0200 (CEST) Received: from japan.t-online.private (unknown [192.168.2.3]) by people.fsn.hu (Postfix) with ESMTP id 09DD28442E for ; Mon, 21 May 2007 19:12:06 +0200 (CEST) Message-ID: <4651D2E1.6090100@fsn.hu> Date: Mon, 21 May 2007 19:12:01 +0200 From: Attila Nagy User-Agent: Thunderbird 2.0.0.0 (X11/20070421) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at fsn.hu Subject: softdep_waitidle: Failed to flush worklist X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 17:38:58 -0000 Hello, I have some read only NFS servers, which share a virtual IP (with CARP) to provide fault resilience. One of them is the master server, on which I occasionally modify the NFS share's content. To make this possible, I have a real UFS file system, on which I have a smaller file. This holds the file system image, which I rsync to the other servers, if needed. The setup: # mdconfig -lu 0 md0 vnode 19G /data/nfsimg # mount | grep nfs /dev/md0 on /nfs (ufs, NFS exported, local, soft-updates) The modify process is like this: #mount -o rw -u /nfs [modify content] #mount -o ro -u /nfs [rsync /data/nfsimg to the other machines] This has worked like a charm until now. Since I've upgraded the OS to RELENG_6 as of today, I get the following line into the syslog everytime I modify something on /nfs and want to do a read only remount: softdep_waitidle: Failed to flush worklist for 0xffffff0054e00630 and the remount command (mount -o ro -u /nfs) fails with: mount: /dev/md0: Device busy Before the upgrade (RELENG_6 from Sep 29 2006), I couldn't notice this behaviour, so something must have changed in the last 3/4 year. :) Of course I can turn softupdates off, but it would be interesting to know what causes this difference... -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 http://www.fsn.hu/ From owner-freebsd-fs@FreeBSD.ORG Mon May 21 18:27:34 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E6D4E16A478 for ; Mon, 21 May 2007 18:27:33 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (grnl-static-02-0046.dsl.iowatelecom.net [69.66.56.110]) by mx1.freebsd.org (Postfix) with ESMTP id 6C5A313C4C4 for ; Mon, 21 May 2007 18:27:33 +0000 (UTC) (envelope-from brooks@lor.one-eyed-alien.net) Received: from lor.one-eyed-alien.net (localhost [127.0.0.1]) by lor.one-eyed-alien.net (8.13.8/8.13.8) with ESMTP id l4LHmJfu065632; Mon, 21 May 2007 12:48:19 -0500 (CDT) (envelope-from brooks@lor.one-eyed-alien.net) Received: (from brooks@localhost) by lor.one-eyed-alien.net (8.13.8/8.13.8/Submit) id l4LHmJAJ065631; Mon, 21 May 2007 12:48:19 -0500 (CDT) (envelope-from brooks) Date: Mon, 21 May 2007 12:48:19 -0500 From: Brooks Davis To: Gore Jarold Message-ID: <20070521174818.GA64826@lor.one-eyed-alien.net> References: <829849.56057.qm@web63013.mail.re1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <829849.56057.qm@web63013.mail.re1.yahoo.com> User-Agent: Mutt/1.5.15 (2007-04-06) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (lor.one-eyed-alien.net [127.0.0.1]); Mon, 21 May 2007 12:48:19 -0500 (CDT) Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 18:27:34 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 21, 2007 at 09:19:02AM -0700, Gore Jarold wrote: >=20 > I have been extremely dissatisfied with the stability > of the FreeBSD UFS/UFS2 implementation throughout all > of 5.x and 6.x. I can take any random release from > this period and halt/lock/crash it with basic and > uninteresting filesystem operations. In early 5.x it > was simply big inode movements from disk to disk.=20 > Later it was multiple snapshots. In 6.x any number of > seemingly benign operations (filling a disk, using > quotas, dense (lots of inodes) deletes and copies) and > each time some or all of these problems are solved in > one release, slightly different versions of the same > problem show up in the next one. For instance, > snapshot stability got a lot better from 6.0 to 6.2, > but now 6.2 has problems just moving and deleting lots > of inodes. >=20 > I am running _nothing interesting_. I don't even run > snapshots anymore ... and as you can see from other > posts, I am crashing/halting/etc. all over the place.=20 > This is on systems that do nothing but TCP (scp, ftp) > file service and some big (rm, cp) movements of inodes > once in a while. In other words, my setup is as > vanilla as it gets. >=20 > It's not the hardware (happens on 3ware, adaptec, > etc.) (different systems). >=20 > It's not my esoteric config (I take generic kernel and > just delete the devices I don't use) ... also I have > no custom sysctls/loader.conf >=20 > So I am at my wits end. Since early 2004 there has > not been a single release version of FreeBSD (well, > except _perhaps_ 6.1-RELEASE ...) that I don't > regularly knock over with _simple, generic movements > of files_. >=20 > So my plea for help is as follows: >=20 > a) am I really the only person in the world that moves > around millions of inodes throughout the day ? Am I > the only person in the world that has ever filled up a > snapshotted FS (or a quota'd FS, for that matter) ?=20 > Am I the only person in the world that does a mass > deletion of several hundred thousand inodes several > times per day ? >=20 > OR: >=20 > b) am I just stupid ? Is everyone doing this, and > there is 3 pages of sysctls and kernel tunes that > everyone does to their system when they are going to > use it this way ? Am I just naive for taking a > release and paring down GENERIC and attempting to run > as-is out of the box without major tuning ? >=20 > If so, can I see those tunes/sysctls ? >=20 > I am _really_ hoping that it is (b) ... I would much > rather look back on all of this frustration as my own > fault than have the burden of proving all of this (as > I will no doubt be called upon to do). (1) >=20 > Thanks. Please add your comments... I'd say it's certaintly (a). Consider that a full source tree contains a few under 85K files so that's a reasionable bound on average workloads. Deliberatly producing a kernel that required tuning to just us the APIs without crashing would be stupid and we wouldn't go it without a very good reason and very large warnings all over the place. Lousy performance might be expected, but crashing wouldn't be. > (1) just load up 6.2 and cp/rm a few million inodes > around. Or turn on quotas and fill your filesystem > up. Kaboom. It's not clear to me what you mean by "cp/rm a few million inodes around." The organization of those inodes into files and directories could conceviably have a major impact on the problem. If you could provide a script that fails for you, that would really help. -- Brooks --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGUdtiXY6L6fI4GtQRAieyAKCCJvWlq6utDMgzvpSz+UpVG4dQ2ACfRNzl Y+PAEfyzR23shzuDLvxMR5w= =h8VM -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J-- From owner-freebsd-fs@FreeBSD.ORG Mon May 21 19:16:35 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75BF016A468 for ; Mon, 21 May 2007 19:16:35 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63006.mail.re1.yahoo.com (web63006.mail.re1.yahoo.com [69.147.96.217]) by mx1.freebsd.org (Postfix) with SMTP id 3D2FA13C4AD for ; Mon, 21 May 2007 19:16:35 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 33803 invoked by uid 60001); 21 May 2007 19:16:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=N3cDez3AF3mzdt4BYATqleKfRsT6r1BxgTZ+/f9KyitlECL+FPRxSRXvynThOMQ3/uI9lFPAnc+ShPbFHk/UEjgmtuAW5teNYa5v4tPnCW8tlc8AQqQR6iVOFvG9HASPzi6AEapXyTHBuakOB6Ny932gclJJrR3yFvZzDNw6CWU=; X-YMail-OSG: 9Xolaz8VM1nIxZskhUo7f81KaIN.4V_ayoOMFAyG9rkJkC4XzHcSC0qFtgM20.J6SGhMfzKtaavgp3ZnSP8r17xwzcjFPVESi2gE Received: from [24.118.228.153] by web63006.mail.re1.yahoo.com via HTTP; Mon, 21 May 2007 12:16:33 PDT Date: Mon, 21 May 2007 12:16:33 -0700 (PDT) From: Gore Jarold To: Brooks Davis In-Reply-To: <20070521174818.GA64826@lor.one-eyed-alien.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <475187.33232.qm@web63006.mail.re1.yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 19:16:35 -0000 --- Brooks Davis wrote: > > a) am I really the only person in the world that > moves > > around millions of inodes throughout the day ? Am > I > > the only person in the world that has ever filled > up a > > snapshotted FS (or a quota'd FS, for that matter) > ? > > Am I the only person in the world that does a mass > > deletion of several hundred thousand inodes > several > > times per day ? > > > > OR: > > > > b) am I just stupid ? Is everyone doing this, and > > there is 3 pages of sysctls and kernel tunes that > > everyone does to their system when they are going > to > > use it this way ? Am I just naive for taking a > > release and paring down GENERIC and attempting to > run > > as-is out of the box without major tuning ? > > > > If so, can I see those tunes/sysctls ? > > > > I am _really_ hoping that it is (b) ... I would > much > > rather look back on all of this frustration as my > own > > fault than have the burden of proving all of this > (as > > I will no doubt be called upon to do). (1) > > > > Thanks. Please add your comments... > > I'd say it's certaintly (a). Consider that a full > source tree contains > a few under 85K files so that's a reasionable bound > on average > workloads. Deliberatly producing a kernel that > required tuning to just > us the APIs without crashing would be stupid and we > wouldn't go it > without a very good reason and very large warnings > all over the place. > Lousy performance might be expected, but crashing > wouldn't be. Ok - your initial comments / impression are reassuring. It's hard to believe that the simple file movements I do are so alien to mainstream use, but I'll accept your judgement. > > (1) just load up 6.2 and cp/rm a few million > inodes > > around. Or turn on quotas and fill your > filesystem > > up. Kaboom. > > It's not clear to me what you mean by "cp/rm a few > million inodes > around." The organization of those inodes into > files and directories > could conceviably have a major impact on the > problem. If you could > provide a script that fails for you, that would > really help. Specifically, I have private departmental fileservers that other fileservers rsync to using Mike Rubel-style rsync snapshots: http://www.mikerubel.org/computers/rsync_snapshots/ This means that the remote system runs a script like this: ssh user@host rm -rf backup.2 ssh user@host mv backup.1 backup.2 ssh user@host cp -al backup.0 backup.1 rsync /files user@host:/backup.0 The /files in question range from .2 to 2.2 million files, all told. This means that when this script runs, it first either deletes OR unlinks up to 2 million items. Then it does a (presumably) zero cost move operation. Then it does a hard-link-creating cp of the same (up to 2 million) items. As I write this, I realize this isn't _totally_ generic, since I am using GNU cp rather than the built-in FreeBSD cp, but that is _truly_ the extent of customization on this system. So that's that. Run that a few times from a few servers and 6.2 locks up. Can't ping. For trivias sake, it does the same thing if you fill up one of its filesystems with quotas turned on. For further trivias sake, 6.1 is (seemingly) not susceptible to this, but it is certainly susceptible to other situations that I regularly produce. What do you think of this (more specific) workload, and are there any tunings that immediately jump to mind ? ____________________________________________________________________________________Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC From owner-freebsd-fs@FreeBSD.ORG Mon May 21 19:34:06 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E999516A400; Mon, 21 May 2007 19:34:06 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id D6E9813C4C6; Mon, 21 May 2007 19:34:06 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 3050E1A3C19; Mon, 21 May 2007 12:35:05 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 03B22513BC; Mon, 21 May 2007 15:34:05 -0400 (EDT) Date: Mon, 21 May 2007 15:34:05 -0400 From: Kris Kennaway To: Gore Jarold Message-ID: <20070521193405.GA80086@xor.obsecurity.org> References: <20070521174818.GA64826@lor.one-eyed-alien.net> <475187.33232.qm@web63006.mail.re1.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <475187.33232.qm@web63006.mail.re1.yahoo.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, Brooks Davis Subject: How to report bugs (Re: VERY frustrated with FreeBSD/UFS stability - please help or comment...) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 19:34:07 -0000 On Mon, May 21, 2007 at 12:16:33PM -0700, Gore Jarold wrote: > > > a) am I really the only person in the world that > > moves > > > around millions of inodes throughout the day ? Am > > I > > > the only person in the world that has ever filled > > up a > > > snapshotted FS (or a quota'd FS, for that matter) > > ? There are known panics that may occur when a snapshot grows to fill a filesystem. I am told that these are fundamentally difficult to avoid. You are certainly not the only persion who operates on millions of inodes, but it is disingenuous to suggest that this is either a "mainstream" or "simple" workload. Also, I personally know of several people who do this without apparent problem, so that is further evidence that whatever problems you are seeing are something specific to your workload or configuration, or you are just unlucky. The larger issue here is that apparently you have been suffering in silence for many years with your various frustrations and they have finally exploded into this email. This is really a poor way to approach the goal of getting your problems solved: it is fundamentally a failure of your expectations to think that without adequately reporting your bugs that they will somehow get fixed. When you encounter a FreeBSD bug, file a bug report ("PR"). We have extensive documentation on how to write effective bug reports, but to summarize some key steps: 1) Provide a reproducible test case. As Brooks noted, this is a key step that will greatly increase the chances of your bug being reproduced, identified and fixed. You failed to do it before now, so we were left completely in the dark. 2) Provide sufficient debugging when the problem occurs. Consult the developers handbook for a full discussion, but it involves things like configuring a debugger, obtaining process traces, enabling additional debugging options, etc. Without these two things there is really very little that a developer can do to try and guess what might possibly be happening on your system. However, it appears that we might now be making some progress: > ssh user@host rm -rf backup.2 > ssh user@host mv backup.1 backup.2 > ssh user@host cp -al backup.0 backup.1 > rsync /files user@host:/backup.0 > > The /files in question range from .2 to 2.2 million > files, all told. This means that when this script > runs, it first either deletes OR unlinks up to 2 > million items. Then it does a (presumably) zero cost > move operation. Then it does a hard-link-creating cp > of the same (up to 2 million) items. Please provide additional details of how the filesystems in question are configured, your kernel configuration, hardware configuration, and the debugging data referred to in 2) above. Thanks, Kris From owner-freebsd-fs@FreeBSD.ORG Mon May 21 19:53:06 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C2FB016A400 for ; Mon, 21 May 2007 19:53:06 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from mxfep01.bredband.com (mxfep01.bredband.com [195.54.107.70]) by mx1.freebsd.org (Postfix) with ESMTP id 1091E13C447 for ; Mon, 21 May 2007 19:53:05 +0000 (UTC) (envelope-from peter.schuller@infidyne.com) Received: from ironport.bredband.com ([195.54.107.82] [195.54.107.82]) by mxfep01.bredband.com with ESMTP id <20070521195304.GGVA28445.mxfep01.bredband.com@ironport.bredband.com> for ; Mon, 21 May 2007 21:53:04 +0200 Received: from c-5416e555.03-51-73746f3.cust.bredbandsbolaget.se (HELO scode.mine.nu) ([85.229.22.84]) by ironport.bredband.com with ESMTP; 21 May 2007 21:53:04 +0200 Received: from scode.mine.nu (localhost [127.0.0.1]) by scode.mine.nu (Postfix) with ESMTP id D7657C4A6; Mon, 21 May 2007 21:53:03 +0200 (CEST) Message-ID: <4651F897.9010201@infidyne.com> Date: Mon, 21 May 2007 21:52:55 +0200 From: Peter Schuller User-Agent: Thunderbird 2.0.0.0 (X11/20070501) MIME-Version: 1.0 To: Gore Jarold References: <475187.33232.qm@web63006.mail.re1.yahoo.com> In-Reply-To: <475187.33232.qm@web63006.mail.re1.yahoo.com> X-Enigmail-Version: 0.95.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig25ACEE43BEE4E26F9223C575" Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 19:53:06 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig25ACEE43BEE4E26F9223C575 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable > Specifically, I have private departmental fileservers > that other fileservers rsync to using Mike Rubel-style > rsync snapshots: FWIW, since you wondered about being alone in the world, I tend to do similar things but with rdiff-backup, with total file count ranging from a few hundred thousand to a few million. But I also routinely do stuff like rsyncing entire chroots with multiple ports/pkgsrc trees and whatnot. I mostly haven't experienced the problems you describe. (Always with UFS2 and softupdates, if you discount recent stuff with ZFS.) The one thing I *have* experienced is filesystems going nuts after filling them. Specifically I end up with a negative amount of space free, and as soon as you release more space df -h quickly reports the amount of free space dropping (you can see it interactively churning for a few secs) until it settles at some negative amount again and you're back to square one. This has happened once or twice in the past, but not recently. Not sure which release it did happen on; might have been 5.x. It's worth noting that the one thing I don't do is creating multiple links to the same file with any frequency, as happens with the rsync incremental backup approach. --=20 / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --------------enig25ACEE43BEE4E26F9223C575 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGUfifDNor2+l1i30RCPnSAJ96g/g6YVfJP+j7YqJJrZTnZQeJvACbBWxF K7uaXttacujQiocP3Mo4L7w= =N3bs -----END PGP SIGNATURE----- --------------enig25ACEE43BEE4E26F9223C575-- From owner-freebsd-fs@FreeBSD.ORG Mon May 21 19:56:35 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4555A16A400 for ; Mon, 21 May 2007 19:56:35 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 336E813C45D for ; Mon, 21 May 2007 19:56:35 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 8B8921A4D84; Mon, 21 May 2007 12:57:33 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5CE9D51417; Mon, 21 May 2007 15:56:34 -0400 (EDT) Date: Mon, 21 May 2007 15:56:34 -0400 From: Kris Kennaway To: Peter Schuller Message-ID: <20070521195634.GA80608@xor.obsecurity.org> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <4651F897.9010201@infidyne.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4651F897.9010201@infidyne.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 19:56:35 -0000 On Mon, May 21, 2007 at 09:52:55PM +0200, Peter Schuller wrote: > > Specifically, I have private departmental fileservers > > that other fileservers rsync to using Mike Rubel-style > > rsync snapshots: > > FWIW, since you wondered about being alone in the world, I tend to do > similar things but with rdiff-backup, with total file count ranging from > a few hundred thousand to a few million. But I also routinely do stuff > like rsyncing entire chroots with multiple ports/pkgsrc trees and > whatnot. I mostly haven't experienced the problems you describe. (Always > with UFS2 and softupdates, if you discount recent stuff with ZFS.) > > The one thing I *have* experienced is filesystems going nuts after > filling them. Specifically I end up with a negative amount of space > free, and as soon as you release more space df -h quickly reports the > amount of free space dropping (you can see it interactively churning for > a few secs) until it settles at some negative amount again and you're > back to square one. This has happened once or twice in the past, but not > recently. Not sure which release it did happen on; might have been 5.x. Yeah, this was an old bug in the 5.x timeframe. As far as I recall it was fixed at some point in the past. > It's worth noting that the one thing I don't do is creating multiple > links to the same file with any frequency, as happens with the rsync > incremental backup approach. I do a lot of hard linking on my system and have not encountered issues. Kris From owner-freebsd-fs@FreeBSD.ORG Mon May 21 20:33:05 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C08C416A4D7 for ; Mon, 21 May 2007 20:33:05 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 4BD9713C46A for ; Mon, 21 May 2007 20:33:05 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 84546 invoked by uid 2001); 21 May 2007 20:35:56 -0000 Date: Mon, 21 May 2007 15:35:56 -0500 From: "Rick C. Petty" To: Kris Kennaway Message-ID: <20070521203556.GA84210@keira.kiwi-computer.com> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <4651F897.9010201@infidyne.com> <20070521195634.GA80608@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070521195634.GA80608@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 20:33:05 -0000 On Mon, May 21, 2007 at 03:56:34PM -0400, Kris Kennaway wrote: > > > > The one thing I *have* experienced is filesystems going nuts after > > filling them. Specifically I end up with a negative amount of space > > free, and as soon as you release more space df -h quickly reports the > > amount of free space dropping (you can see it interactively churning for > > a few secs) until it settles at some negative amount again and you're > > back to square one. This has happened once or twice in the past, but not > > recently. Not sure which release it did happen on; might have been 5.x. > > Yeah, this was an old bug in the 5.x timeframe. As far as I recall it > was fixed at some point in the past. Hmm, this recently happened to me in 6.2-STABLE. I was unable to replicate it so filing a PR was pointless. What I saw happen was that /usr filled up completely (I caught it before it hit 100% full, but watched helplessly as it switched from time to space optimization). I even did a "du -hd0 /usr" and saw it only using about 20% of the file system. lsof and fstat weren't terribly helpful. After shutting down to single-user mode, I saw it full even though I deleted a lot of superfluous files, and du/df differences were still present. I restarted and fsck cleaned up the 80% "used" space, stating the superblock free maps were incorrect, which explains the discrepency. Why it happened, I'm still baffled. -- Rick C. Petty From owner-freebsd-fs@FreeBSD.ORG Mon May 21 20:37:27 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D60D16A468 for ; Mon, 21 May 2007 20:37:27 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63004.mail.re1.yahoo.com (web63004.mail.re1.yahoo.com [69.147.96.215]) by mx1.freebsd.org (Postfix) with SMTP id C50F313C45D for ; Mon, 21 May 2007 20:37:26 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 4865 invoked by uid 60001); 21 May 2007 20:37:26 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=gbJFQ8rcTs2A2F9k7fe0YxOcvYE5mEOomrpEhdB40Tqsx6eKiy4KyytYg8t3000HsaLbPJsDibeYRzlpLdY/c4Lz9pWJf+uZ+BursY78DGvtRA6mg3OZ1lUKZDKT0goU7aUTeGfk7sN3/kCTPmbPUZN/ZobIflXN+T6CL6pSDaI=; X-YMail-OSG: IzfD_y4VM1m_AL09KoqKoXejWQKifWxS65TMEiD30xkhT9qF47FsNxQQBVxnjzYHfOIA2_DEgQPPuZuf4A4cSLPDkUIgbfnyGIDX.XbatuoML6ItjOqpowWKBQVDoVpH Received: from [24.118.228.153] by web63004.mail.re1.yahoo.com via HTTP; Mon, 21 May 2007 13:37:25 PDT Date: Mon, 21 May 2007 13:37:25 -0700 (PDT) From: Gore Jarold To: Kris Kennaway In-Reply-To: <20070521193405.GA80086@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <38676.4493.qm@web63004.mail.re1.yahoo.com> Cc: freebsd-fs@freebsd.org, Brooks Davis Subject: Re: How to report bugs (Re: VERY frustrated with FreeBSD/UFS stability - please help or comment...) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 20:37:27 -0000 --- Kris Kennaway wrote: > On Mon, May 21, 2007 at 12:16:33PM -0700, Gore > Jarold wrote: > > > > > a) am I really the only person in the world > that > > > moves > > > > around millions of inodes throughout the day ? > Am > > > I > > > > the only person in the world that has ever > filled > > > up a > > > > snapshotted FS (or a quota'd FS, for that > matter) > > > ? (snip) > You are certainly not the only persion who operates > on millions of > inodes, but it is disingenuous to suggest that this > is either a > "mainstream" or "simple" workload. Also, I > personally know of several > people who do this without apparent problem, so that > is further > evidence that whatever problems you are seeing are > something specific > to your workload or configuration, or you are just > unlucky. Ok. In my defense, I have to say that as a non-developer, end user, it's hard to watch people installing ZFS on FreeBSD and running with journaling and newfs'ing raw disk with 7.0-current, etc., and not feel like I am an extremely pedestrian use case. I had no idea I was so cutting edge :) > The larger issue here is that apparently you have > been suffering in > silence for many years with your various > frustrations and they have > finally exploded into this email. This is really a > poor way to > approach the goal of getting your problems solved: > it is fundamentally > a failure of your expectations to think that without > adequately > reporting your bugs that they will somehow get > fixed. I need to clarify and respond to this ... my point was that every release since 5.0 has had some new and interesting instability in this regard. Every time a new release comes out, it seems to be "fixed", only to reveal some other new and interesting instability. So, no, I have not silently suffered with _any one_ particular problem - they never seem to last more than one release or two. It is only now, however, that I have come to realize that I am in the same spot (overall) today as I was in early 2004. The details are slightly different, but the end result is that my rsyncs and cps and rms are too much for FreeBSD, and have been for 3 years now. So what I am saying is, individual causes of instability (seem to) come and go, but I am not any better of today than I was with 5.0. I have just realized this, and that is why I make my frustration known today. > Without these two things there is really very little > that a developer > can do to try and guess what might possibly be > happening on your > system. However, it appears that we might now be > making some > progress: > > > ssh user@host rm -rf backup.2 > > ssh user@host mv backup.1 backup.2 > > ssh user@host cp -al backup.0 backup.1 > > rsync /files user@host:/backup.0 > > > > The /files in question range from .2 to 2.2 > million > > files, all told. This means that when this script > > runs, it first either deletes OR unlinks up to 2 > > million items. Then it does a (presumably) zero > cost > > move operation. Then it does a hard-link-creating > cp > > of the same (up to 2 million) items. > > Please provide additional details of how the > filesystems in question > are configured, your kernel configuration, hardware > configuration, and > the debugging data referred to in 2) above. I will collect all of this and submit it the next time the system crashes... ____________________________________________________________________________________ Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ From owner-freebsd-fs@FreeBSD.ORG Mon May 21 20:39:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8A0FC16A46D for ; Mon, 21 May 2007 20:39:41 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7630813C4BB for ; Mon, 21 May 2007 20:39:41 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 893321A3C19; Mon, 21 May 2007 13:40:39 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 2FF065156C; Mon, 21 May 2007 16:39:39 -0400 (EDT) Date: Mon, 21 May 2007 16:39:39 -0400 From: Kris Kennaway To: "Rick C. Petty" Message-ID: <20070521203938.GA81333@xor.obsecurity.org> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <4651F897.9010201@infidyne.com> <20070521195634.GA80608@xor.obsecurity.org> <20070521203556.GA84210@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070521203556.GA84210@keira.kiwi-computer.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 20:39:41 -0000 On Mon, May 21, 2007 at 03:35:56PM -0500, Rick C. Petty wrote: > On Mon, May 21, 2007 at 03:56:34PM -0400, Kris Kennaway wrote: > > > > > > The one thing I *have* experienced is filesystems going nuts after > > > filling them. Specifically I end up with a negative amount of space > > > free, and as soon as you release more space df -h quickly reports the > > > amount of free space dropping (you can see it interactively churning for > > > a few secs) until it settles at some negative amount again and you're > > > back to square one. This has happened once or twice in the past, but not > > > recently. Not sure which release it did happen on; might have been 5.x. > > > > Yeah, this was an old bug in the 5.x timeframe. As far as I recall it > > was fixed at some point in the past. > > Hmm, this recently happened to me in 6.2-STABLE. I was unable to replicate > it so filing a PR was pointless. What I saw happen was that /usr filled up > completely (I caught it before it hit 100% full, but watched helplessly as > it switched from time to space optimization). I even did a "du -hd0 /usr" > and saw it only using about 20% of the file system. lsof and fstat weren't > terribly helpful. After shutting down to single-user mode, I saw it full > even though I deleted a lot of superfluous files, and du/df differences > were still present. I restarted and fsck cleaned up the 80% "used" space, > stating the superblock free maps were incorrect, which explains the > discrepency. Why it happened, I'm still baffled. OK, it may be that the bug is still around in some form, or it could be a different issue. One thing to check is whether you have a snapshot active, because this will cause a very similar behaviour. Kris From owner-freebsd-fs@FreeBSD.ORG Mon May 21 20:47:28 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 76E4916A41F; Mon, 21 May 2007 20:47:28 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5820813C457; Mon, 21 May 2007 20:47:28 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 88D4A1A3C19; Mon, 21 May 2007 13:48:26 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1032751369; Mon, 21 May 2007 16:47:26 -0400 (EDT) Date: Mon, 21 May 2007 16:47:26 -0400 From: Kris Kennaway To: Gore Jarold Message-ID: <20070521204726.GB81333@xor.obsecurity.org> References: <20070521193405.GA80086@xor.obsecurity.org> <38676.4493.qm@web63004.mail.re1.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline In-Reply-To: <38676.4493.qm@web63004.mail.re1.yahoo.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, Brooks Davis , Kris Kennaway Subject: Re: How to report bugs (Re: VERY frustrated with FreeBSD/UFS stability - please help or comment...) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 20:47:28 -0000 --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 21, 2007 at 01:37:25PM -0700, Gore Jarold wrote: > > The larger issue here is that apparently you have > > been suffering in > > silence for many years with your various > > frustrations and they have > > finally exploded into this email. This is really a > > poor way to > > approach the goal of getting your problems solved: > > it is fundamentally > > a failure of your expectations to think that without > > adequately > > reporting your bugs that they will somehow get > > fixed. >=20 >=20 > I need to clarify and respond to this ... my point was > that every release since 5.0 has had some new and > interesting instability in this regard. Every time a > new release comes out, it seems to be "fixed", only to > reveal some other new and interesting instability. >=20 > So, no, I have not silently suffered with _any one_ > particular problem - they never seem to last more than > one release or two. It is only now, however, that I > have come to realize that I am in the same spot > (overall) today as I was in early 2004. The details > are slightly different, but the end result is that my > rsyncs and cps and rms are too much for FreeBSD, and > have been for 3 years now. >=20 > So what I am saying is, individual causes of > instability (seem to) come and go, but I am not any > better of today than I was with 5.0. I have just > realized this, and that is why I make my frustration > known today. OK, but nevertheless the point stands. When you encounter a critical issue in FreeBSD, the sensible way to go about addressing it is to file a suitably complete PR, instead of just gritting your teeth, raising your blood pressure, and hoping that someone else will accidentally fix it in the next release. Of course, filing a PR is not a guarantee that it will be fixed (e.g. the "snapshot fills a filesystem" problems, which result from deeper architectural issues and in practise may require contracting a developer to get fixed), but at least you will have done your part. > > Without these two things there is really very little > > that a developer > > can do to try and guess what might possibly be > > happening on your > > system. However, it appears that we might now be > > making some > > progress: > >=20 > > > ssh user@host rm -rf backup.2 > > > ssh user@host mv backup.1 backup.2 > > > ssh user@host cp -al backup.0 backup.1 > > > rsync /files user@host:/backup.0 > > >=20 > > > The /files in question range from .2 to 2.2 > > million > > > files, all told. This means that when this script > > > runs, it first either deletes OR unlinks up to 2 > > > million items. Then it does a (presumably) zero > > cost > > > move operation. Then it does a hard-link-creating > > cp > > > of the same (up to 2 million) items. > >=20 > > Please provide additional details of how the > > filesystems in question > > are configured, your kernel configuration, hardware > > configuration, and > > the debugging data referred to in 2) above. >=20 >=20 > I will collect all of this and submit it the next time > the system crashes... Thanks. Kris --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGUgVdWry0BWjoQKURAr9JAKCr6i/tp9SPtbOEsSFRbrX+AnuU0wCgjdMp or9FdqbWJsKlFv+2uI7VePs= =mZMg -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- From owner-freebsd-fs@FreeBSD.ORG Mon May 21 21:11:58 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 98DFC16A469 for ; Mon, 21 May 2007 21:11:58 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from smtp7.server.rpi.edu (smtp7.server.rpi.edu [128.113.2.227]) by mx1.freebsd.org (Postfix) with ESMTP id 5E55D13C4CA for ; Mon, 21 May 2007 21:11:58 +0000 (UTC) (envelope-from gad@FreeBSD.org) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp7.server.rpi.edu (8.13.1/8.13.1) with ESMTP id l4LJv1WF007883; Mon, 21 May 2007 15:57:02 -0400 Mime-Version: 1.0 Message-Id: In-Reply-To: <829849.56057.qm@web63013.mail.re1.yahoo.com> References: <829849.56057.qm@web63013.mail.re1.yahoo.com> Date: Mon, 21 May 2007 15:57:01 -0400 To: Gore Jarold , freebsd-fs@FreeBSD.org From: Garance A Drosehn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-RPI-SA-Score: undef - spam scanning disabled X-CanItPRO-Stream: default X-Canit-Stats-ID: Bayes signature not available X-Scanned-By: CanIt (www . roaringpenguin . com) on 128.113.2.227 Cc: Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 21:11:58 -0000 At 9:19 AM -0700 5/21/07, Gore Jarold wrote: >(I love FreeBSD. This is not a troll. If all you >have to contribute is "stop spreading FUD" or "write >some code yourself" please accept my apologies.) Okay, I can believe that. No problem. >So my plea for help is as follows: > >a) am I really the only person in the world that moves >around millions of inodes throughout the day ? Am I >the only person in the world that has ever filled up a >snapshotted FS (or a quota'd FS, for that matter) ? >Am I the only person in the world that does a mass >deletion of several hundred thousand inodes several >times per day ? I think this is the main issue. I did have some problems with snapshots due to running out of disk-space, etc. But those were due to errors on my part, and were not "normal" operating practice. The few errors I have run into were pretty easy to avoid, simply by re-arranging my disk partitions and paying a little more attention to what I was doing. For instance, I found out that it's bad to automatically do a snapshot before an installworld, and then do multiple installworlds in the same day, while forgetting about all those snapshots building up. Sooner or later you have to run out of disk space, and it's really bad to do that in the middle of an installworld! But once I realized what the issue was, I switched to doing one snapshot per week, instead of one per installworld. I really had no practical reason for the snapshot-per-installworld, so it did not bother me to drop that. I imagine I've had days where I've deleted one hundred-thousand inodes in a day, but it would be rare. And it'd be even more rare that I'd remove several hundred-thousand inodes multiple times in the same day. The one time I was doing something like that, I put the most volatile data on a partition by itself, and I'd simply 'newfs' the partition instead of going through and removing each file. I didn't do that to avoid any bugs, I only did it because it was quicker, and I also knew it would get me back to the exact same starting point for my next run. And since part of what I was doing was benchmarking various things, it was important that each run had the exact same starting point. I think that your usage is just much larger than the "standard" freebsd user, so you're hitting edge-cases that the rest of us are blissfully missing. -- Garance Alistair Drosehn = drosehn@rpi.edu Senior Systems Programmer or gad@FreeBSD.org Rensselaer Polytechnic Institute; Troy, NY; USA From owner-freebsd-fs@FreeBSD.ORG Mon May 21 22:09:38 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CA89016A468 for ; Mon, 21 May 2007 22:09:38 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: from kiwi-computer.com (keira.kiwi-computer.com [63.224.10.3]) by mx1.freebsd.org (Postfix) with SMTP id 3ADCB13C44C for ; Mon, 21 May 2007 22:09:38 +0000 (UTC) (envelope-from rick@kiwi-computer.com) Received: (qmail 86217 invoked by uid 2001); 21 May 2007 22:12:32 -0000 Date: Mon, 21 May 2007 17:12:32 -0500 From: "Rick C. Petty" To: Kris Kennaway Message-ID: <20070521221232.GA86033@keira.kiwi-computer.com> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <4651F897.9010201@infidyne.com> <20070521195634.GA80608@xor.obsecurity.org> <20070521203556.GA84210@keira.kiwi-computer.com> <20070521203938.GA81333@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070521203938.GA81333@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd@kiwi-computer.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 22:09:38 -0000 On Mon, May 21, 2007 at 04:39:39PM -0400, Kris Kennaway wrote: > On Mon, May 21, 2007 at 03:35:56PM -0500, Rick C. Petty wrote: > > > > Hmm, this recently happened to me in 6.2-STABLE. I was unable to replicate > > it so filing a PR was pointless. What I saw happen was that /usr filled up > > completely (I caught it before it hit 100% full, but watched helplessly as > > it switched from time to space optimization). I even did a "du -hd0 /usr" > > and saw it only using about 20% of the file system. lsof and fstat weren't > > terribly helpful. After shutting down to single-user mode, I saw it full > > even though I deleted a lot of superfluous files, and du/df differences > > were still present. I restarted and fsck cleaned up the 80% "used" space, > > stating the superblock free maps were incorrect, which explains the > > discrepency. Why it happened, I'm still baffled. > > OK, it may be that the bug is still around in some form, or it could > be a different issue. One thing to check is whether you have a > snapshot active, because this will cause a very similar behaviour. I don't use snapshots, except for bgfsck, which wasn't necessary because everything preened clean. Like I said, it would be difficult to chase down. I should probably just enable kernel DDB in case it happens again. -- Rick C. Petty From owner-freebsd-fs@FreeBSD.ORG Mon May 21 22:46:48 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 83F2A16A421 for ; Mon, 21 May 2007 22:46:48 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 6EADD13C447 for ; Mon, 21 May 2007 22:46:48 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E74451A3C19; Mon, 21 May 2007 15:47:46 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7DB125135C; Mon, 21 May 2007 18:46:47 -0400 (EDT) Date: Mon, 21 May 2007 18:46:47 -0400 From: Kris Kennaway To: "Rick C. Petty" Message-ID: <20070521224647.GA83380@xor.obsecurity.org> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <4651F897.9010201@infidyne.com> <20070521195634.GA80608@xor.obsecurity.org> <20070521203556.GA84210@keira.kiwi-computer.com> <20070521203938.GA81333@xor.obsecurity.org> <20070521221232.GA86033@keira.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070521221232.GA86033@keira.kiwi-computer.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, Kris Kennaway Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 May 2007 22:46:48 -0000 On Mon, May 21, 2007 at 05:12:32PM -0500, Rick C. Petty wrote: > On Mon, May 21, 2007 at 04:39:39PM -0400, Kris Kennaway wrote: > > On Mon, May 21, 2007 at 03:35:56PM -0500, Rick C. Petty wrote: > > > > > > Hmm, this recently happened to me in 6.2-STABLE. I was unable to replicate > > > it so filing a PR was pointless. What I saw happen was that /usr filled up > > > completely (I caught it before it hit 100% full, but watched helplessly as > > > it switched from time to space optimization). I even did a "du -hd0 /usr" > > > and saw it only using about 20% of the file system. lsof and fstat weren't > > > terribly helpful. After shutting down to single-user mode, I saw it full > > > even though I deleted a lot of superfluous files, and du/df differences > > > were still present. I restarted and fsck cleaned up the 80% "used" space, > > > stating the superblock free maps were incorrect, which explains the > > > discrepency. Why it happened, I'm still baffled. > > > > OK, it may be that the bug is still around in some form, or it could > > be a different issue. One thing to check is whether you have a > > snapshot active, because this will cause a very similar behaviour. > > I don't use snapshots, except for bgfsck, which wasn't necessary because > everything preened clean. > > Like I said, it would be difficult to chase down. I should probably just > enable kernel DDB in case it happens again. Yeah, if you can force a dump when something like this happens then it may help to track it down. Sometimes it is hard to reconstruct the sequence of events leading to such a point though. Kris From owner-freebsd-fs@FreeBSD.ORG Tue May 22 04:53:26 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5FBA516A46B for ; Tue, 22 May 2007 04:53:26 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from optimus.centralmiss.com (ns.centralmiss.com [206.156.254.79]) by mx1.freebsd.org (Postfix) with ESMTP id 3970313C489 for ; Tue, 22 May 2007 04:53:26 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (adsl-072-148-013-213.sip.jan.bellsouth.net [72.148.13.213]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by optimus.centralmiss.com (Postfix) with ESMTP id 67D2E28431; Mon, 21 May 2007 23:53:25 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id E3B9C61C43; Mon, 21 May 2007 23:53:24 -0500 (CDT) Date: Mon, 21 May 2007 23:53:24 -0500 From: "Matthew D. Fuller" To: Attila Nagy Message-ID: <20070522045324.GB83502@over-yonder.net> References: <4651D2E1.6090100@fsn.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4651D2E1.6090100@fsn.hu> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.14-fullermd.3 (2007-02-12) Cc: freebsd-fs@freebsd.org Subject: Re: softdep_waitidle: Failed to flush worklist X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 04:53:26 -0000 On Mon, May 21, 2007 at 07:12:01PM +0200 I heard the voice of Attila Nagy, and lo! it spake thus: > > The modify process is like this: > #mount -o rw -u /nfs > [modify content] > #mount -o ro -u /nfs > [rsync /data/nfsimg to the other machines] > > This has worked like a charm until now. Since I've upgraded the OS to > RELENG_6 as of today, I get the following > line into the syslog everytime I modify something on /nfs and want to do > a read only remount: > softdep_waitidle: Failed to flush worklist for 0xffffff0054e00630 > and the remount command (mount -o ro -u /nfs) fails with: > mount: /dev/md0: Device busy You'll find you can't umount it either. I've been experiencing this for a while on -CURRENT. I didn't manage to get any interest on the current@ list. See the thread at with a script to reproduce it on a md filesystem. Still experienced after my last upgrade in March ). -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-fs@FreeBSD.ORG Tue May 22 08:31:12 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 680) id 3FF6116A46C; Tue, 22 May 2007 08:31:12 +0000 (UTC) Date: Tue, 22 May 2007 08:31:12 +0000 From: Darren Reed To: Vince Message-ID: <20070522083112.GA5136@hub.freebsd.org> References: <20070407165759.GG8831@cicely12.cicely.de> <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4651BD6F.5050301@unsane.co.uk> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@FreeBSD.org, Craig Boston , freebsd-current@FreeBSD.org, Pawel Jakub Dawidek , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 08:31:12 -0000 On Mon, May 21, 2007 at 04:40:31PM +0100, Vince wrote: ... > I dont suppose that there are any other tunables people could suggest? I > got a shiny new(well old but new to me) dual opteron board and dual 250 > sata drives and though i'd try putting it in as my home server with > everything but / on zfs since i've had my /usr/ports on my laptop as > compressed zfs since very shortly after it was commited. > After a few kmem_map: too small" panics I re-read this thread and put > vm.kmem_size_max and vm.kmem_size up to 512M and vfs.zfs.arc_min > vfs.zfs.arc_max down to 65 megs. This did get me past "portsnap extract" > but a make buildworld still got me the same panic. vmstat -z showed a > steady growth. This is with a generic -CURRENT from friday. I'm happy to > provide any useful information once I get home and reboot it. Are you running the opterons with a 32 or 64 bit kernel? I set vfs.zfs.arc_max to somewhere between 75% and 80% of vm.kmem_size_max. Darren From owner-freebsd-fs@FreeBSD.ORG Tue May 22 08:44:12 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 37E6A16A421 for ; Tue, 22 May 2007 08:44:12 +0000 (UTC) (envelope-from jhs@tower.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id C0AAF13C489 for ; Tue, 22 May 2007 08:44:11 +0000 (UTC) (envelope-from jhs@tower.berklix.net) Received: from js.berklix.net (p549A73F2.dip.t-dialin.net [84.154.115.242]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l4M8hko6087567; Tue, 22 May 2007 10:43:47 +0200 (CEST) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.13.6/8.13.6) with ESMTP id l4M8hd0M064167; Tue, 22 May 2007 10:43:40 +0200 (CEST) (envelope-from jhs@tower.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id l4M8inVN090608; Tue, 22 May 2007 10:44:49 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200705220844.l4M8inVN090608@fire.jhs.private> To: Gore Jarold In-reply-to: <829849.56057.qm@web63013.mail.re1.yahoo.com> References: <829849.56057.qm@web63013.mail.re1.yahoo.com> Comments: In-reply-to Gore Jarold message dated "Mon, 21 May 2007 09:19:02 -0700." Date: Tue, 22 May 2007 10:44:49 +0200 From: "Julian H. Stacey" Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 08:44:12 -0000 Gore Jarold wrote: > I have been extremely dissatisfied with the stability > of the FreeBSD UFS/UFS2 implementation throughout all Are you using external USB drives ? If so, suspect range widens, both hardware & software. I sometimes see some problems on my laptop USB with at least 6.1 & 6.2-rel, some of which could also materialise on a tower with USB (& reshuffling space, moving 30G of src/ ports/ packages/ distfiles/ & music between internal & 2 external drives is a way to get trouble. - External drive hangs. Apparently it used to hang on previous owner's XP too (but was that drive or XP or owner or ?). It has a FREECOM USB2-IDE Controller in enclosure). - Failure to flush blocks on halt (not sure if seen this with no USB). - Carbus Belkin USB2 card gets far too hot, painful to touch at times (& my brother's same type card he used in same type laptop under XP, died after he `cooked' his card in my laptop. Never gets so hot under MS-XP but I have no idea how (or desire) to load an MS-XP hard. (I wonder if perhaps MS-XP switched the card to power saving mode whereas maybe FreeBSD left it on all the time). - Potentialy USB2 ZediWorks hub, or cable, but no reason to suspect those. Of course many externals also use own power, & I can't say I've yet monitored all external power supply under load with both DVM & scope :-) I've known hubs drop to 1% of traffic because capacitors in power block dried out; also had a tower (new everything except old power & chassis) be unstable, & crash when scsi cdrom spun up, which gliched power. There's always power to consider, especially if everything at max. -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com Ihr Rauch = mein allergischer Kopfschmerz. Dump cigs: Try snuff. From owner-freebsd-fs@FreeBSD.ORG Tue May 22 09:01:24 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 67C3716A41F; Tue, 22 May 2007 09:01:24 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from unsane.co.uk (www.unsane.co.uk [85.233.185.162]) by mx1.freebsd.org (Postfix) with ESMTP id BF6CE13C480; Tue, 22 May 2007 09:01:23 +0000 (UTC) (envelope-from jhary@unsane.co.uk) Received: from prawn.unsane.co.uk (150.117-84-212.staticip.namesco.net [212.84.117.150]) (authenticated bits=0) by unsane.co.uk (8.14.0/8.14.0) with ESMTP id l4M916U7039252 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 May 2007 10:01:08 +0100 (BST) (envelope-from jhary@unsane.co.uk) Message-ID: <4652B15D.5060505@unsane.co.uk> Date: Tue, 22 May 2007 10:01:17 +0100 From: Vince User-Agent: Thunderbird 2.0.0.0 (X11/20070516) MIME-Version: 1.0 To: Darren Reed References: <20070407165759.GG8831@cicely12.cicely.de> <20070407180319.GH8831@cicely12.cicely.de> <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> In-Reply-To: <20070522083112.GA5136@hub.freebsd.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Craig Boston , freebsd-current@freebsd.org, Pawel Jakub Dawidek , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 09:01:24 -0000 Darren Reed wrote: > On Mon, May 21, 2007 at 04:40:31PM +0100, Vince wrote: > ... >> I dont suppose that there are any other tunables people could suggest? I >> got a shiny new(well old but new to me) dual opteron board and dual 250 >> sata drives and though i'd try putting it in as my home server with >> everything but / on zfs since i've had my /usr/ports on my laptop as >> compressed zfs since very shortly after it was commited. >> After a few kmem_map: too small" panics I re-read this thread and put >> vm.kmem_size_max and vm.kmem_size up to 512M and vfs.zfs.arc_min >> vfs.zfs.arc_max down to 65 megs. This did get me past "portsnap extract" >> but a make buildworld still got me the same panic. vmstat -z showed a >> steady growth. This is with a generic -CURRENT from friday. I'm happy to >> provide any useful information once I get home and reboot it. > > Are you running the opterons with a 32 or 64 bit kernel? > > I set vfs.zfs.arc_max to somewhere between 75% and 80% of vm.kmem_size_max. > I'm running i386 more because I had a i386 CD lying around to install from and wont be using more than 3Gigs of RAM, than through informed choice. It looks like setting kern.maxvnodes=50000 has solved it for now. (after almost a day of uptime including building world and adding the 2nd disk to the zfs mirror) [root@crab ~]# vmstat -m | grep sol solaris 188066 139903K - 164899933 16,32,64,128,256,512,1024,2048,4096 I may reinstall at a later date as this is still very much a box to play with, but I gather there is no great gain from going 64 bit other than not having to play with PAE if you've got lots or RAM. Thanks to everyone who made suggestions, Vince > Darren > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue May 22 09:10:00 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A145E16A469; Tue, 22 May 2007 09:10:00 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id E8CAB13C448; Tue, 22 May 2007 09:09:59 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 958A448801; Tue, 22 May 2007 11:09:58 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 14DA7487F0; Tue, 22 May 2007 11:09:54 +0200 (CEST) Date: Tue, 22 May 2007 11:09:47 +0200 From: Pawel Jakub Dawidek To: Vince Message-ID: <20070522090947.GA3005@garage.freebsd.pl> References: <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline In-Reply-To: <4652B15D.5060505@unsane.co.uk> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: Darren Reed , freebsd-fs@freebsd.org, Kris Kennaway , freebsd-current@freebsd.org, Craig Boston Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 09:10:00 -0000 --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 22, 2007 at 10:01:17AM +0100, Vince wrote: > Darren Reed wrote: > > On Mon, May 21, 2007 at 04:40:31PM +0100, Vince wrote: > > ... > >> I dont suppose that there are any other tunables people could suggest?= I > >> got a shiny new(well old but new to me) dual opteron board and dual 250 > >> sata drives and though i'd try putting it in as my home server with > >> everything but / on zfs since i've had my /usr/ports on my laptop as > >> compressed zfs since very shortly after it was commited. > >> After a few kmem_map: too small" panics I re-read this thread and put > >> vm.kmem_size_max and vm.kmem_size up to 512M and vfs.zfs.arc_min > >> vfs.zfs.arc_max down to 65 megs. This did get me past "portsnap extrac= t" > >> but a make buildworld still got me the same panic. vmstat -z showed a > >> steady growth. This is with a generic -CURRENT from friday. I'm happy = to > >> provide any useful information once I get home and reboot it. > >=20 > > Are you running the opterons with a 32 or 64 bit kernel? > >=20 > > I set vfs.zfs.arc_max to somewhere between 75% and 80% of vm.kmem_size_= max. > >=20 > I'm running i386 more because I had a i386 CD lying around to install > from and wont be using more than 3Gigs of RAM, than through informed > choice. It looks like setting kern.maxvnodes=3D50000 has solved it for = now. >=20 > (after almost a day of uptime including building world and adding the > 2nd disk to the zfs mirror) > [root@crab ~]# vmstat -m | grep sol > solaris 188066 139903K - 164899933 > 16,32,64,128,256,512,1024,2048,4096 >=20 > I may reinstall at a later date as this is still very much a box to play > with, but I gather there is no great gain from going 64 bit other than > not having to play with PAE if you've got lots or RAM. I expect there is a huge difference in performance between i386 and amd64. I'm currently setting up environment to compare ZFS on FreeBSD/i386, FreeBSD/amd64 and Solaris. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGUrNbForvXbEpPzQRAjubAKCbBilKQ/6Q//R9DNeB0I8G4oe6uwCg8Pq4 eJKqrg+/FVDZxNjAtg5KqDk= =/RNi -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- From owner-freebsd-fs@FreeBSD.ORG Tue May 22 09:17:40 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA6B516A41F; Tue, 22 May 2007 09:17:40 +0000 (UTC) (envelope-from kvs@binarysolutions.dk) Received: from solow.pil.dk (relay.pil.dk [195.41.47.164]) by mx1.freebsd.org (Postfix) with ESMTP id 9B2E613C45D; Tue, 22 May 2007 09:17:40 +0000 (UTC) (envelope-from kvs@binarysolutions.dk) Received: from coruscant.localhost (fw2.pil.dk [83.90.227.58]) by solow.pil.dk (Postfix) with ESMTP id 5404A1CC0ED; Tue, 22 May 2007 11:17:39 +0200 (CEST) Received: by coruscant.localhost (Postfix, from userid 502) id 7EF223ACCAF; Tue, 22 May 2007 11:17:37 +0200 (CEST) To: Pawel Jakub Dawidek References: <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070522090947.GA3005@garage.freebsd.pl> From: Kenneth Vestergaard Schmidt Date: Tue, 22 May 2007 11:17:37 +0200 In-Reply-To: <20070522090947.GA3005@garage.freebsd.pl> (Pawel Jakub Dawidek's message of "Tue\, 22 May 2007 11\:09\:47 +0200") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.96 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Craig Boston , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Kris Kennaway , Darren Reed , Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 09:17:40 -0000 Pawel Jakub Dawidek writes: >> I may reinstall at a later date as this is still very much a box to play >> with, but I gather there is no great gain from going 64 bit other than >> not having to play with PAE if you've got lots or RAM. > > I expect there is a huge difference in performance between i386 and > amd64. I'm currently setting up environment to compare ZFS on > FreeBSD/i386, FreeBSD/amd64 and Solaris. I've had precious little time to do more testing on our amd64-setup, but it seems that vm.kmem.size_max is a 32-bit uint, so we can't really use much RAM for ZFS. --=20 vh Kenneth Schmidt pil.dk support Tr=E6t af virusmails? http://pil.dk/produkter/mail/antivirus/ From owner-freebsd-fs@FreeBSD.ORG Tue May 22 11:39:44 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7180B16A46B for ; Tue, 22 May 2007 11:39:44 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 2C73913C45A for ; Tue, 22 May 2007 11:39:44 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 05DD42084; Tue, 22 May 2007 13:39:40 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id EA7E32083; Tue, 22 May 2007 13:39:39 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id D251957B2; Tue, 22 May 2007 13:39:39 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Gore Jarold References: <475187.33232.qm@web63006.mail.re1.yahoo.com> Date: Tue, 22 May 2007 13:39:39 +0200 In-Reply-To: <475187.33232.qm@web63006.mail.re1.yahoo.com> (Gore Jarold's message of "Mon\, 21 May 2007 12\:16\:33 -0700 \(PDT\)") Message-ID: <86r6p9xf2c.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, Brooks Davis Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 11:39:44 -0000 Gore Jarold writes: > Specifically, I have private departmental fileservers that other > fileservers rsync to using Mike Rubel-style rsync snapshots: > > http://www.mikerubel.org/computers/rsync_snapshots/ > > This means that the remote system runs a script like this: > > ssh user@host rm -rf backup.2 > ssh user@host mv backup.1 backup.2 > ssh user@host cp -al backup.0 backup.1 > rsync /files user@host:/backup.0 This is extremely inefficient, as you have discovered. Speaking in the abstract, what you want to do every day is the following: client1% rsync --archive --delete /vol server:/backup/client1 client2% rsync --archive --delete /vol server:/backup/client2 server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done No copying or deleting; you take a snapshot when the rsync job is done, and the next day you rsync again to the same directory; only what has actually changed will be transferred, and there is no need to create and populate full copies of each directory tree every time. The easiest way to do this (if you're not afraid to run experimental code) is to use ZFS on the server, as it lets you easily create separate file systems for each client, and creates and maintains snapshots far more cheaply than FFS. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Tue May 22 12:06:49 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41FEF16A469 for ; Tue, 22 May 2007 12:06:49 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.embarqhsd.net [65.40.24.38]) by mx1.freebsd.org (Postfix) with ESMTP id A8CF013C4B7 for ; Tue, 22 May 2007 12:06:48 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.8/8.13.1) with ESMTP id l4MC6XHP089580; Tue, 22 May 2007 08:06:33 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.8/8.13.1/Submit) id l4MC6Rsw089579; Tue, 22 May 2007 08:06:27 -0400 (EDT) (envelope-from bv) Date: Tue, 22 May 2007 08:06:27 -0400 From: Bill Vermillion To: Dag-Erling Sm??rgrav Message-ID: <20070522120627.GB89056@wjv.com> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86r6p9xf2c.fsf@dwp.des.no> User-Agent: Mutt/1.4.2.2i Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on bilver.wjv.com Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 12:06:49 -0000 The time has come the Dag-Erling Sm??rgrav said, to talk of many things but all that was heard on Tue, May 22, 2007 at 13:39 was whether pigs have wings - or: > Gore Jarold writes: > > Specifically, I have private departmental fileservers that other > > fileservers rsync to using Mike Rubel-style rsync snapshots: > > http://www.mikerubel.org/computers/rsync_snapshots/ > > This means that the remote system runs a script like this: > > ssh user@host rm -rf backup.2 > > ssh user@host mv backup.1 backup.2 > > ssh user@host cp -al backup.0 backup.1 > > rsync /files user@host:/backup.0 > This is extremely inefficient, as you have discovered. > Speaking in the abstract, what you want to do every day is the > following: > client1% rsync --archive --delete /vol server:/backup/client1 > client2% rsync --archive --delete /vol server:/backup/client2 > server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done > No copying or deleting; you take a snapshot when the rsync job > is done, and the next day you rsync again to the same directory; > only what has actually changed will be transferred, and there > is no need to create and populate full copies of each directory > tree every time. And one other way to 'copy' files/directories >>IF<< they are on the same file system, is to use cpio with the -pdlm option. All that does is build another directory with all files in the first liked statically to the second. Then you just 'rm' the files in the first. Since there is NO COPYING - this is quick, won't scatter files around as they remain where they were originally but with just a new directory pointing to them. Probably not the best way for something done regularly but a very quick and efficient way to move files around in a system with very low overhead and is quite fast. It also has the plus for the new directory is that it gets you a clean directory, which can be a perfomance gain if the original had lots of file, many of which were deleted. > The easiest way to do this (if you're not afraid to run > experimental code) is to use ZFS on the server, as it lets you > easily create separate file systems for each client, and creates > and maintains snapshots far more cheaply than FFS. I've been watching the ZFS and I'm going to wait awhile, but it will be awhile before I put in on my servers. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-fs@FreeBSD.ORG Tue May 22 12:30:18 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A325316A421 for ; Tue, 22 May 2007 12:30:18 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6E77013C447 for ; Tue, 22 May 2007 12:30:18 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id l4MCUGrB014811; Tue, 22 May 2007 07:30:16 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4652E254.8020501@freebsd.org> Date: Tue, 22 May 2007 07:30:12 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: Gore Jarold References: <38676.4493.qm@web63004.mail.re1.yahoo.com> In-Reply-To: <38676.4493.qm@web63004.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3281/Tue May 22 03:50:43 2007 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: freebsd-fs@freebsd.org, Brooks Davis , Kris Kennaway Subject: Re: How to report bugs (Re: VERY frustrated with FreeBSD/UFS stability - please help or comment...) X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 12:30:19 -0000 On 05/21/07 15:37, Gore Jarold wrote: > --- Kris Kennaway wrote: > >> On Mon, May 21, 2007 at 12:16:33PM -0700, Gore >> Jarold wrote: >> >>>>> a) am I really the only person in the world >> that >>>> moves >>>>> around millions of inodes throughout the day ? >> Am >>>> I >>>>> the only person in the world that has ever >> filled >>>> up a >>>>> snapshotted FS (or a quota'd FS, for that >> matter) >>>> ? > > > (snip) > > >> You are certainly not the only persion who operates >> on millions of >> inodes, but it is disingenuous to suggest that this >> is either a >> "mainstream" or "simple" workload. Also, I >> personally know of several >> people who do this without apparent problem, so that >> is further >> evidence that whatever problems you are seeing are >> something specific >> to your workload or configuration, or you are just >> unlucky. > > > Ok. In my defense, I have to say that as a > non-developer, end user, it's hard to watch people > installing ZFS on FreeBSD and running with journaling > and newfs'ing raw disk with 7.0-current, etc., and not > feel like I am an extremely pedestrian use case. > > I had no idea I was so cutting edge :) > > > >> The larger issue here is that apparently you have >> been suffering in >> silence for many years with your various >> frustrations and they have >> finally exploded into this email. This is really a >> poor way to >> approach the goal of getting your problems solved: >> it is fundamentally >> a failure of your expectations to think that without >> adequately >> reporting your bugs that they will somehow get >> fixed. > > > I need to clarify and respond to this ... my point was > that every release since 5.0 has had some new and > interesting instability in this regard. Every time a > new release comes out, it seems to be "fixed", only to > reveal some other new and interesting instability. > > So, no, I have not silently suffered with _any one_ > particular problem - they never seem to last more than > one release or two. It is only now, however, that I > have come to realize that I am in the same spot > (overall) today as I was in early 2004. The details > are slightly different, but the end result is that my > rsyncs and cps and rms are too much for FreeBSD, and > have been for 3 years now. > > So what I am saying is, individual causes of > instability (seem to) come and go, but I am not any > better of today than I was with 5.0. I have just > realized this, and that is why I make my frustration > known today. > > >> Without these two things there is really very little >> that a developer >> can do to try and guess what might possibly be >> happening on your >> system. However, it appears that we might now be >> making some >> progress: >> >>> ssh user@host rm -rf backup.2 >>> ssh user@host mv backup.1 backup.2 >>> ssh user@host cp -al backup.0 backup.1 >>> rsync /files user@host:/backup.0 >>> >>> The /files in question range from .2 to 2.2 >> million >>> files, all told. This means that when this script >>> runs, it first either deletes OR unlinks up to 2 >>> million items. Then it does a (presumably) zero >> cost >>> move operation. Then it does a hard-link-creating >> cp >>> of the same (up to 2 million) items. >> Please provide additional details of how the >> filesystems in question >> are configured, your kernel configuration, hardware >> configuration, and >> the debugging data referred to in 2) above. > > > I will collect all of this and submit it the next time > the system crashes... For whatever it might be worth, I'm doing a very similar task (using rsnapshot), for backing up a decent amount of data, with a nightly difference of a million or so files, touching ~200million files nightly. I currently have 5 10TB filesystems running, with 20TB more coming online today or tomorrow. Here's a df output: # df -ilk Filesystem 1024-blocks Used Avail Capacity iused ifree %iused Mounted on /dev/amrd0s3a 20308398 1114658 17569070 6% 23080 2614742 1% / devfs 1 1 0 100% 0 0 100% /dev /dev/amrd0s3e 18441132 3794030 13171812 22% 96 2402206 0% /tmp /dev/amrd0s3d 20308398 3164982 15518746 17% 250111 2387711 9% /usr /dev/ufs/vol1 9926678106 5030793092 4101750766 55% 38875256 1244237702 3% /vol1 /dev/ufs/vol2 9926678106 3668501950 5464041908 40% 67622249 1215490709 5% /vol2 /dev/ufs/vol3 9926678106 5937797134 3194746724 65% 97153 1283015805 0% /vol3 /dev/ufs/vol10 9925732858 8054663156 1077011074 88% 97873355 1185121843 8% /vol10 /dev/ufs/vol11 9925732858 7288510876 1843163354 80% 126038333 1156956865 10% /vol11 I have roughly 50-60 hardlinks per file (for about 80% of the files). Obviously fsck is not an option (due to memory/time constraints) so I've been using gjournaling (thanks to PJD). I *do* have one issue that has cropped up on one of these file systems, which I just recently found. I'll send a separate email with details. I don't use snapshots, or background fsck on these at all, nor do I use quotas. So, it can be done, and it can be done with pretty good reliability (whatever that might mean to any particular person). Eric From owner-freebsd-fs@FreeBSD.ORG Tue May 22 12:42:17 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1B9316A473; Tue, 22 May 2007 12:42:17 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A069F13C480; Tue, 22 May 2007 12:42:17 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id AB62F2087; Tue, 22 May 2007 14:42:13 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 386D22086; Tue, 22 May 2007 14:42:13 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 1CA3557B7; Tue, 22 May 2007 14:42:13 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: bv@wjv.com References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <20070522120627.GB89056@wjv.com> Date: Tue, 22 May 2007 14:42:12 +0200 In-Reply-To: <20070522120627.GB89056@wjv.com> (Bill Vermillion's message of "Tue\, 22 May 2007 08\:06\:27 -0400") Message-ID: <86iralxc63.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 12:42:18 -0000 Bill Vermillion writes: > And one other way to 'copy' files/directories >>IF<< they are > on the same file system, is to use cpio with the -pdlm option. > > All that does is build another directory with all files in the > first liked statically to the second. Then you just 'rm' the files > in the first. Since there is NO COPYING - this is quick, won't > scatter files around as they remain where they were originally but > with just a new directory pointing to them. This is exactly what the OP already does (cp -rl) but it is nowhere near as fast as you claim when you have thousands of directories and millions of files. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Tue May 22 12:45:09 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 423CA16A400 for ; Tue, 22 May 2007 12:45:09 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 21C4513C44C for ; Tue, 22 May 2007 12:45:09 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id l4MCj5M4017431; Tue, 22 May 2007 07:45:05 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4652E5CD.6000901@freebsd.org> Date: Tue, 22 May 2007 07:45:01 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: Gore Jarold References: <475187.33232.qm@web63006.mail.re1.yahoo.com> In-Reply-To: <475187.33232.qm@web63006.mail.re1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3281/Tue May 22 03:50:43 2007 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 12:45:09 -0000 On 05/21/07 14:16, Gore Jarold wrote: > --- Brooks Davis wrote: > > >>> a) am I really the only person in the world that >> moves >>> around millions of inodes throughout the day ? Am >> I >>> the only person in the world that has ever filled >> up a >>> snapshotted FS (or a quota'd FS, for that matter) >> ? >>> Am I the only person in the world that does a mass >>> deletion of several hundred thousand inodes >> several >>> times per day ? >>> >>> OR: >>> >>> b) am I just stupid ? Is everyone doing this, and >>> there is 3 pages of sysctls and kernel tunes that >>> everyone does to their system when they are going >> to >>> use it this way ? Am I just naive for taking a >>> release and paring down GENERIC and attempting to >> run >>> as-is out of the box without major tuning ? >>> >>> If so, can I see those tunes/sysctls ? >>> >>> I am _really_ hoping that it is (b) ... I would >> much >>> rather look back on all of this frustration as my >> own >>> fault than have the burden of proving all of this >> (as >>> I will no doubt be called upon to do). (1) >>> >>> Thanks. Please add your comments... >> I'd say it's certaintly (a). Consider that a full >> source tree contains >> a few under 85K files so that's a reasionable bound >> on average >> workloads. Deliberatly producing a kernel that >> required tuning to just >> us the APIs without crashing would be stupid and we >> wouldn't go it >> without a very good reason and very large warnings >> all over the place. >> Lousy performance might be expected, but crashing >> wouldn't be. > > > Ok - your initial comments / impression are > reassuring. It's hard to believe that the simple file > movements I do are so alien to mainstream use, but > I'll accept your judgement. > > > >>> (1) just load up 6.2 and cp/rm a few million >> inodes >>> around. Or turn on quotas and fill your >> filesystem >>> up. Kaboom. >> It's not clear to me what you mean by "cp/rm a few >> million inodes >> around." The organization of those inodes into >> files and directories >> could conceviably have a major impact on the >> problem. If you could >> provide a script that fails for you, that would >> really help. > > > Specifically, I have private departmental fileservers > that other fileservers rsync to using Mike Rubel-style > rsync snapshots: > > http://www.mikerubel.org/computers/rsync_snapshots/ > > This means that the remote system runs a script like > this: > > ssh user@host rm -rf backup.2 > ssh user@host mv backup.1 backup.2 > ssh user@host cp -al backup.0 backup.1 > rsync /files user@host:/backup.0 > > The /files in question range from .2 to 2.2 million > files, all told. This means that when this script > runs, it first either deletes OR unlinks up to 2 > million items. Then it does a (presumably) zero cost > move operation. Then it does a hard-link-creating cp > of the same (up to 2 million) items. > > As I write this, I realize this isn't _totally_ > generic, since I am using GNU cp rather than the > built-in FreeBSD cp, but that is _truly_ the extent of > customization on this system. A few quick comments: - why use GNU cp when you can use our own cp? You could do 'cp -Rpl' instead. - You could probably save some time, and use rsyncs '--link-dest' option Eric From owner-freebsd-fs@FreeBSD.ORG Tue May 22 12:54:28 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6DD1116A469; Tue, 22 May 2007 12:54:28 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3EBC213C469; Tue, 22 May 2007 12:54:28 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id l4MCsMUI018953; Tue, 22 May 2007 07:54:22 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4652E7F9.10005@freebsd.org> Date: Tue, 22 May 2007 07:54:17 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> In-Reply-To: <86r6p9xf2c.fsf@dwp.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88.4/3281/Tue May 22 03:50:43 2007 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 12:54:28 -0000 On 05/22/07 06:39, Dag-Erling Smørgrav wrote: > Gore Jarold writes: >> Specifically, I have private departmental fileservers that other >> fileservers rsync to using Mike Rubel-style rsync snapshots: >> >> http://www.mikerubel.org/computers/rsync_snapshots/ >> >> This means that the remote system runs a script like this: >> >> ssh user@host rm -rf backup.2 >> ssh user@host mv backup.1 backup.2 >> ssh user@host cp -al backup.0 backup.1 >> rsync /files user@host:/backup.0 > > This is extremely inefficient, as you have discovered. > > Speaking in the abstract, what you want to do every day is the > following: > > client1% rsync --archive --delete /vol server:/backup/client1 > client2% rsync --archive --delete /vol server:/backup/client2 > server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done > > No copying or deleting; you take a snapshot when the rsync job is done, > and the next day you rsync again to the same directory; only what has > actually changed will be transferred, and there is no need to create and > populate full copies of each directory tree every time. That's good for small file systems, but if you have a multi-terabyte file system, you're not going to be too happy about those results. The snapshot will take a *very* long time, on a nearly full file system. Eric From owner-freebsd-fs@FreeBSD.ORG Tue May 22 13:01:46 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CB0E16A469; Tue, 22 May 2007 13:01:46 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id ED7EE13C448; Tue, 22 May 2007 13:01:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 33D1A2084; Tue, 22 May 2007 15:01:42 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on tim.des.no Received: from dwp.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id ABE262083; Tue, 22 May 2007 15:01:41 +0200 (CEST) Received: by dwp.des.no (Postfix, from userid 1001) id 8D48457BB; Tue, 22 May 2007 15:01:41 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Eric Anderson References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <4652E7F9.10005@freebsd.org> Date: Tue, 22 May 2007 15:01:41 +0200 In-Reply-To: <4652E7F9.10005@freebsd.org> (Eric Anderson's message of "Tue\, 22 May 2007 07\:54\:17 -0500") Message-ID: <86646lxb9m.fsf@dwp.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 13:01:46 -0000 Eric Anderson writes: > Dag-Erling Sm=C3=B8rgrav writes: > > Speaking in the abstract, what you want to do every day is the > > following: > > > > client1% rsync --archive --delete /vol server:/backup/client1 > > client2% rsync --archive --delete /vol server:/backup/client2 > > server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; d= one > That's good for small file systems, but if you have a multi-terabyte > file system, you're not going to be too happy about those results. > The snapshot will take a *very* long time, on a nearly full file > system. I did write "in the abstract". I am well aware that this will not work well with FFS. You left out the part where I recommended using ZFS instead. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-fs@FreeBSD.ORG Tue May 22 13:03:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 453A716A468; Tue, 22 May 2007 13:03:41 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.embarqhsd.net [65.40.24.38]) by mx1.freebsd.org (Postfix) with ESMTP id EF55613C46E; Tue, 22 May 2007 13:03:40 +0000 (UTC) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.8/8.13.1) with ESMTP id l4MD3YPS090239; Tue, 22 May 2007 09:03:35 -0400 (EDT) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.8/8.13.1/Submit) id l4MD3TZH090238; Tue, 22 May 2007 09:03:29 -0400 (EDT) (envelope-from bv) Date: Tue, 22 May 2007 09:03:24 -0400 From: Bill Vermillion To: Dag-Erling Sm??rgrav Message-ID: <20070522130324.GA89918@wjv.com> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <20070522120627.GB89056@wjv.com> <86iralxc63.fsf@dwp.des.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86iralxc63.fsf@dwp.des.no> User-Agent: Mutt/1.4.2.2i Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on bilver.wjv.com Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bv@wjv.com List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 13:03:41 -0000 On Tue, May 22, 2007 at 14:42 Dag-Erling Sm??rgrav said 'Who you talkin' to? You talkin' to Dag-Erling Sm??rgrav? I didn't do nuttin'. I said: > Bill Vermillion writes: > > And one other way to 'copy' files/directories >>IF<< they are > > on the same file system, is to use cpio with the -pdlm option. > > > > All that does is build another directory with all files in the > > first liked statically to the second. Then you just 'rm' the files > > in the first. Since there is NO COPYING - this is quick, won't > > scatter files around as they remain where they were originally but > > with just a new directory pointing to them. > This is exactly what the OP already does (cp -rl) but it is nowhere near > as fast as you claim when you have thousands of directories and millions > of files. > DES > -- > Dag-Erling Sm??rgrav - des@des.no Sorry. I missed the -rl option. I started usind the cpio -pdlm option many years ago and never used the cp -rl. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-fs@FreeBSD.ORG Tue May 22 13:03:57 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F0CB16A41F; Tue, 22 May 2007 13:03:57 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id F370013C457; Tue, 22 May 2007 13:03:56 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l4MD3sKD030203; Tue, 22 May 2007 08:03:55 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4652EA36.1010804@freebsd.org> Date: Tue, 22 May 2007 08:03:50 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <4652E7F9.10005@freebsd.org> <86646lxb9m.fsf@dwp.des.no> In-Reply-To: <86646lxb9m.fsf@dwp.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.88.4/3281/Tue May 22 03:50:43 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 13:03:57 -0000 On 05/22/07 08:01, Dag-Erling Smørgrav wrote: > Eric Anderson writes: >> Dag-Erling Smørgrav writes: >>> Speaking in the abstract, what you want to do every day is the >>> following: >>> >>> client1% rsync --archive --delete /vol server:/backup/client1 >>> client2% rsync --archive --delete /vol server:/backup/client2 >>> server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done >> That's good for small file systems, but if you have a multi-terabyte >> file system, you're not going to be too happy about those results. >> The snapshot will take a *very* long time, on a nearly full file >> system. > > I did write "in the abstract". I am well aware that this will not work > well with FFS. You left out the part where I recommended using ZFS > instead. > > DES True.. I left out the ZFS part, because your mksnap_ffs command is what I was referring to, and it only applies to FFS, so the ZFS comment wasn't relevant to my particular comment. Eric From owner-freebsd-fs@FreeBSD.ORG Tue May 22 13:07:55 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 905E816A421 for ; Tue, 22 May 2007 13:07:55 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh2.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6573713C465 for ; Tue, 22 May 2007 13:07:55 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from neutrino.centtech.com (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.8/8.13.8) with ESMTP id l4MD7qJ5021298; Tue, 22 May 2007 08:07:53 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <4652EB24.20000@freebsd.org> Date: Tue, 22 May 2007 08:07:48 -0500 From: Eric Anderson User-Agent: Thunderbird 2.0.0.0 (X11/20070521) MIME-Version: 1.0 To: Attila Nagy References: <4651D2E1.6090100@fsn.hu> In-Reply-To: <4651D2E1.6090100@fsn.hu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3281/Tue May 22 03:50:43 2007 on mh2.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh2.centtech.com Cc: freebsd-fs@freebsd.org Subject: Re: softdep_waitidle: Failed to flush worklist X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 13:07:55 -0000 On 05/21/07 12:12, Attila Nagy wrote: > Hello, > > I have some read only NFS servers, which share a virtual IP (with CARP) > to provide fault resilience. One of them is the > master server, on which I occasionally modify the NFS share's content. > To make this possible, I have a real UFS file system, on which I have a > smaller file. This holds the file system image, which I rsync to the > other servers, if needed. > > The setup: > # mdconfig -lu 0 > md0 vnode 19G /data/nfsimg > # mount | grep nfs > /dev/md0 on /nfs (ufs, NFS exported, local, soft-updates) > > The modify process is like this: > #mount -o rw -u /nfs > [modify content] > #mount -o ro -u /nfs > [rsync /data/nfsimg to the other machines] > > This has worked like a charm until now. Since I've upgraded the OS to > RELENG_6 as of today, I get the following > line into the syslog everytime I modify something on /nfs and want to do > a read only remount: > softdep_waitidle: Failed to flush worklist for 0xffffff0054e00630 > and the remount command (mount -o ro -u /nfs) fails with: > mount: /dev/md0: Device busy > > Before the upgrade (RELENG_6 from Sep 29 2006), I couldn't notice this > behaviour, so something must have changed in the last 3/4 year. :) > > Of course I can turn softupdates off, but it would be interesting to > know what causes this difference... > I used to see that on some filesystems (2TB) when I would do a large number of writes, then immediately mount -u -ro like you are doing. I dodged it by putting a sleep and sync between the finish of my writes, and the mount update (I think it was 30 seconds). I never tracked it down to anything, and honestly forgot until now that I did that. Eric From owner-freebsd-fs@FreeBSD.ORG Tue May 22 13:11:12 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 636DE16A421 for ; Tue, 22 May 2007 13:11:12 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [82.230.37.243]) by mx1.freebsd.org (Postfix) with ESMTP id 1992F13C458 for ; Tue, 22 May 2007 13:11:11 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 8703339490 for ; Tue, 22 May 2007 15:11:10 +0200 (CEST) Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 73394-14 for ; Tue, 22 May 2007 15:11:08 +0200 (CEST) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id 9069739415; Tue, 22 May 2007 15:11:08 +0200 (CEST) Date: Tue, 22 May 2007 15:11:08 +0200 From: Ollivier Robert To: freebsd-fs@freebsd.org Message-ID: <20070522131107.GA73155@keltia.freenix.fr> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <86r6p9xf2c.fsf@dwp.des.no> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 6.2 / Dell D820 SMP User-Agent: Mutt/1.5.15 (2007-04-06) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 13:11:12 -0000 According to Dag-Erling Smørgrav: > client2% rsync --archive --delete /vol server:/backup/client2 > server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done My experience with the sysutils/freebsd-snapshot, which enable automatic snapshot creation (à la NetApp) is that after a few created snapshots, the whole system just locks up. This was in 6.0-6.1 days, maybe 6.2 has improved but they seem very fragile :( I am eagerly waiting for ZFS. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin sidhe.keltia.net Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007 i386 From owner-freebsd-fs@FreeBSD.ORG Tue May 22 14:33:15 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 79F0E16A473 for ; Tue, 22 May 2007 14:33:15 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: from web63013.mail.re1.yahoo.com (web63013.mail.re1.yahoo.com [69.147.96.240]) by mx1.freebsd.org (Postfix) with SMTP id 2383E13C483 for ; Tue, 22 May 2007 14:33:14 +0000 (UTC) (envelope-from gore_jarold@yahoo.com) Received: (qmail 96404 invoked by uid 60001); 22 May 2007 14:33:14 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=omHusMgFXXP6dSGYajknodUg9DAh/Rh/ds9KYYE7R/O4KqukFhxjsQmmG3mRdIuG9lLM0LfgpQOkgBtU7OBL7/2r0yW6T/8B4cPmbiqtO8sBYg0Fc3BmN5w2cPZvq2mtOSU3ZyA3hOx+rhOuL8fp9LsbwLNnBg0vl1as1MU04gc=; X-YMail-OSG: aq6x5OUVM1k0RHmj4W9JSJxmbM9AAK1lseg4t3JwYz66Zrb5s3oxG17n11F7JO_E1w-- Received: from [24.118.228.153] by web63013.mail.re1.yahoo.com via HTTP; Tue, 22 May 2007 07:33:14 PDT Date: Tue, 22 May 2007 07:33:14 -0700 (PDT) From: Gore Jarold To: Eric Anderson , Dag-Erling "Smørgrav" In-Reply-To: <4652E7F9.10005@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <468430.96293.qm@web63013.mail.re1.yahoo.com> Cc: freebsd-fs@freebsd.org, Brooks Davis , Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 14:33:15 -0000 --- Eric Anderson wrote: > On 05/22/07 06:39, Dag-Erling Smørgrav wrote: > > Gore Jarold writes: > >> Specifically, I have private departmental > fileservers that other > >> fileservers rsync to using Mike Rubel-style rsync > snapshots: > >> > >> > http://www.mikerubel.org/computers/rsync_snapshots/ > >> > >> This means that the remote system runs a script > like this: > >> > >> ssh user@host rm -rf backup.2 > >> ssh user@host mv backup.1 backup.2 > >> ssh user@host cp -al backup.0 backup.1 > >> rsync /files user@host:/backup.0 > > > > This is extremely inefficient, as you have > discovered. > > > > Speaking in the abstract, what you want to do > every day is the > > following: > > > > client1% rsync --archive --delete /vol > server:/backup/client1 > > client2% rsync --archive --delete /vol > server:/backup/client2 > > server% for vol in /backup/* ; do mksnap_ffs $vol > $vol/.snap/`date` ; done > > > > No copying or deleting; you take a snapshot when > the rsync job is done, > > and the next day you rsync again to the same > directory; only what has > > actually changed will be transferred, and there is > no need to create and > > populate full copies of each directory tree every > time. > > > That's good for small file systems, but if you have > a multi-terabyte > file system, you're not going to be too happy about > those results. The > snapshot will take a *very* long time, on a nearly > full file system. And in addition, you're using snapshots, which adds a lot more instability, IMO. There are many PRs (most solved, I hope) that indicate instability running snapshots, not to mention the risk of filling a filesystem accidently, etc. ____________________________________________________________________________________ Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ From owner-freebsd-fs@FreeBSD.ORG Tue May 22 17:36:13 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BF16016A400; Tue, 22 May 2007 17:36:13 +0000 (UTC) (envelope-from aedwards@sandvine.com) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id 2DFED13C457; Tue, 22 May 2007 17:36:12 +0000 (UTC) (envelope-from aedwards@sandvine.com) Received: from exchange-2.sandvine.com ([192.168.16.12]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 22 May 2007 13:35:10 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 22 May 2007 13:35:09 -0400 Message-ID: <5230D3C40B842D4F9FB3CD368021BEF72F093F@exchange-2.sandvine.com> In-Reply-To: <5230D3C40B842D4F9FB3CD368021BEF72F092A@exchange-2.sandvine.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ufs dead-locks on freebsd 6.2 Thread-Index: AceZgA8XJQM9a6noQX+h86ioyzHh9wAHOkwgAAtyb/AAsywZQA== References: <5230D3C40B842D4F9FB3CD368021BEF72F0926@exchange-2.sandvine.com> <5230D3C40B842D4F9FB3CD368021BEF72F092A@exchange-2.sandvine.com> From: "Andrew Edwards" To: , X-OriginalArrivalTime: 22 May 2007 17:35:10.0284 (UTC) FILETIME=[8BCD70C0:01C79C97] Cc: Subject: RE: Ufs dead-locks on freebsd 6.2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 17:36:13 -0000 It's been a couple of days with no response, how do I know if anyone is looking into this problem? > -----Original Message----- > From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] > On Behalf Of Andrew Edwards > Sent: Saturday, May 19, 2007 12:34 AM > To: freebsd-fs@freebsd.org; freebsd-performance@freebsd.org > Subject: RE: Ufs dead-locks on freebsd 6.2 >=20 > Fsck didn't help but below is a list of processes that were stuck in > disk. Also, one potential problem I've hit is I have mrtg scripts that > get launched from cron every min. MRTG is supposed to have a locking > mechanism to prevent the same script from running at the same time but I > suspect since the filesystem was unaccessible the cron jobs just kept > piling up and piling up until the system would eventually crash. I > caught it when the load avg. was at 620 and killed all the cron's I > could. That brought the load avg. down to under 1 however system is > still taking up 30% of the processor time and the disks are basically > idle. I can still do an ls -l on the root of all my mounted ufs and nfs > filesystems but on one it's taking a considerable amount longer than the > rest. This particular rsync that I was running is copying into the /d2 > fs. >=20 > The system is still running and I can make tpc connections and > somethings I have running from inetd work but ssh stops responding right > away and I can't logon via the console. So, I've captured a core dump > of the system and rebooted so that I could use it again. Are there any > suggestion as to what to do next? I'm debaiting installing an adaptec > raid and rebuilding the system to see if I get the same problem, my > worry is that it's the intel raid drivers that are causing this problem > and I have 4 other systems with the same card. >=20 >=20 > PID TT STAT TIME COMMAND > 2 ?? DL 0:04.86 [g_event] > 3 ?? DL 2:05.90 [g_up] > 4 ?? DL 1:07.95 [g_down] > 5 ?? DL 0:00.00 [xpt_thrd] > 6 ?? DL 0:00.00 [kqueue taskq] > 7 ?? DL 0:00.00 [thread taskq] > 8 ?? DL 0:06.96 [pagedaemon] > 9 ?? DL 0:00.00 [vmdaemon] > 15 ?? DL 0:22.28 [yarrow] > 24 ?? DL 0:00.01 [usb0] > 25 ?? DL 0:00.00 [usbtask] > 27 ?? DL 0:00.01 [usb1] > 29 ?? DL 0:00.01 [usb2] > 36 ?? DL 1:28.73 [pagezero] > 37 ?? DL 0:08.76 [bufdaemon] > 38 ?? DL 0:00.54 [vnlru] > 39 ?? DL 1:08.12 [syncer] > 40 ?? DL 0:04.00 [softdepflush] > 41 ?? DL 0:11.05 [schedcpu] > 27182 ?? Ds 0:05.75 /usr/sbin/syslogd -l /var/run/log -l > /var/named/var/run/log -b 127.0.0.1 -a 10.128.0.0/10 > 27471 ?? Is 0:01.10 /usr/local/bin/postmaster -D > /usr/local/pgsql/data (postgres) > 27594 ?? Is 0:00.04 /usr/libexec/ftpd -m -D -l -l > 27602 ?? DL 0:00.28 [smbiod1] > 96581 ?? D 0:00.00 cron: running job (cron) > 96582 ?? D 0:00.00 cron: running job (cron) > 96583 ?? D 0:00.00 cron: running job (cron) > 96585 ?? D 0:00.00 cron: running job (cron) > 96586 ?? D 0:00.00 cron: running job (cron) > 96587 ?? D 0:00.00 cron: running job (cron) > 96588 ?? D 0:00.00 cron: running job (cron) > 96589 ?? D 0:00.00 cron: running job (cron) > 96590 ?? D 0:00.00 cron: running job (cron) > 96591 ?? D 0:00.00 cron: running job (cron) > 96592 ?? D 0:00.00 cron: running job (cron) > 96593 ?? D 0:00.00 cron: running job (cron) > 96594 ?? D 0:00.00 cron: running job (cron) > 96607 ?? D 0:00.00 cron: running job (cron) > 96608 ?? D 0:00.00 cron: running job (cron) > 96609 ?? D 0:00.00 cron: running job (cron) > 96610 ?? D 0:00.00 cron: running job (cron) > 96611 ?? D 0:00.00 cron: running job (cron) > 96612 ?? D 0:00.00 cron: running job (cron) > 96613 ?? D 0:00.00 cron: running job (cron) > 96614 ?? D 0:00.00 cron: running job (cron) > 96615 ?? D 0:00.00 cron: running job (cron) > 96616 ?? D 0:00.00 cron: running job (cron) > 96617 ?? D 0:00.00 cron: running job (cron) > 96631 ?? D 0:00.00 cron: running job (cron) > 96632 ?? D 0:00.00 cron: running job (cron) > 96633 ?? D 0:00.00 cron: running job (cron) > 96634 ?? D 0:00.00 cron: running job (cron) > 96635 ?? D 0:00.00 cron: running job (cron) > 96636 ?? D 0:00.00 cron: running job (cron) > 96637 ?? D 0:00.00 cron: running job (cron) > 96638 ?? D 0:00.00 cron: running job (cron) > 96639 ?? D 0:00.00 cron: running job (cron) > 96642 ?? D 0:00.00 cron: running job (cron) > 96650 ?? D 0:00.00 cron: running job (cron) > 29393 p0 D+ 22:04.58 /usr/local/bin/rsync >=20 > real 0m0.012s > user 0m0.000s > sys 0m0.010s > / >=20 > real 0m0.019s > user 0m0.000s > sys 0m0.016s > /var >=20 > real 0m0.028s > user 0m0.008s > sys 0m0.018s > /diskless >=20 > real 0m0.017s > user 0m0.008s > sys 0m0.007s > /usr >=20 > real 0m0.016s > user 0m0.000s > sys 0m0.015s > /d2 >=20 > real 0m0.024s > user 0m0.000s > sys 0m0.023s > /exports/home >=20 > real 0m2.559s > user 0m0.216s > sys 0m2.307s >=20 > -----Original Message----- > From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] > On Behalf Of Andrew Edwards > Sent: Friday, May 18, 2007 6:44 PM > To: freebsd-fs@freebsd.org; freebsd-performance@freebsd.org > Subject: RE: Ufs dead-locks on freebsd 6.2 >=20 > Okay, I let memtest run for a full day and there has been no memory > errors. What do I do next? Just to be on the safe side I'll fsck all > of my fs's and try to reproduce the problem again. >=20 > I also don't know what zonelimit is, I see this on similarily configured > machines but running 5.4. I know it's related to network as I > periodically get network connections to work i.e. ssh, ftp (both server > and client side) but eventually the box will deadlock. Should I start a > different thread on this? Happens about once every 30 days on two > server although I havn't checked the exact timing. >=20 > -----Original Message----- > From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] > On Behalf Of Eric Anderson > Sent: Friday, May 18, 2007 3:09 PM > To: Kris Kennaway > Cc: freebsd-fs@freebsd.org > Subject: Re: Ufs dead-locks on freebsd 6.2 >=20 > On 05/18/07 14:00, Kris Kennaway wrote: > > On Thu, May 17, 2007 at 11:38:20PM -0500, Eric Anderson wrote: > >> On 05/17/07 12:47, Kostik Belousov wrote: > >>> On Thu, May 17, 2007 at 01:03:37PM -0400, Andrew Edwards wrote: > >>>> Here it is. > >>>> > >>>> db> show vnode 0xccd47984 > >>>> vnode 0xccd47984: tag ufs, type VDIR > >>>> usecount 5135, writecount 0, refcount 5137 mountedhere 0 > >>>> flags (VV_ROOT) > >>>> v_object 0xcd02518c ref 0 pages 1 > >>>> #0 0xc0593f0d at lockmgr+0x4ed > >>>> #1 0xc06b8e0e at ffs_lock+0x76 > >>>> #2 0xc0739787 at VOP_LOCK_APV+0x87 > >>>> #3 0xc0601c28 at vn_lock+0xac > >>>> #4 0xc05ee832 at lookup+0xde > >>>> #5 0xc05ee4b2 at namei+0x39a > >>>> #6 0xc05e2ab0 at unp_connect+0xf0 > >>>> #7 0xc05e1a6a at uipc_connect+0x66 > >>>> #8 0xc05d9992 at soconnect+0x4e > >>>> #9 0xc05dec60 at kern_connect+0x74 > >>>> #10 0xc05debdf at connect+0x2f > >>>> #11 0xc0723e2b at syscall+0x25b > >>>> #12 0xc070ee0f at Xint0x80_syscall+0x1f > >>>> > >>>> ino 2, on dev amrd0s1a > >>> It seems to be the sort of things that cannot happen. VOP_LOCK() > >>> returned 0, but vnode was not really locked. > >>> > >>> Although claiming that kernel code cannot have such bug is too > >>> optimistic, I would first make sure that: > >>> 1. You checked the memory of the machine. > >>> 2. Your kernel is built from pristine sources. > >> > >> This looks precisely like a lock I was seeing on one of my NFS > servers. > >> Only one of the filesystems would cause it, but it was the same one > >> each time, not necessarily under any kind of load. Things like > >> mountd would get wedged in state 'ufs', and other things would get > >> stuck in one of the lock states (I can't recall). > > > > ...so you cannot conclude that it looks "precisely like" this case. > > > > Please, don't confuse bug reports by this kind of claim unless you > > have made a detailed comparison of the debugging traces to yours. >=20 >=20 > Understood - my mistake. >=20 > Eric >=20 >=20 > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" From owner-freebsd-fs@FreeBSD.ORG Tue May 22 19:22:58 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E6A416A48F for ; Tue, 22 May 2007 19:22:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1D86C13C480 for ; Tue, 22 May 2007 19:22:58 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id B0AB41A4D84; Tue, 22 May 2007 12:23:57 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3916B521E7; Tue, 22 May 2007 15:22:57 -0400 (EDT) Date: Tue, 22 May 2007 15:22:57 -0400 From: Kris Kennaway To: Ollivier Robert Message-ID: <20070522192257.GA77895@xor.obsecurity.org> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <20070522131107.GA73155@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070522131107.GA73155@keltia.freenix.fr> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 May 2007 19:22:58 -0000 On Tue, May 22, 2007 at 03:11:08PM +0200, Ollivier Robert wrote: > According to Dag-Erling Sm?rgrav: > > client2% rsync --archive --delete /vol server:/backup/client2 > > server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done > > My experience with the sysutils/freebsd-snapshot, which enable automatic > snapshot creation (? la NetApp) is that after a few created snapshots, the > whole system just locks up. This was in 6.0-6.1 days, maybe 6.2 has > improved but they seem very fragile :( It is fair to say that snapshots were not designed to be used in this way and have manifested lots of tricky bugs under different usage conditions. People like Kostik and Tor have fixed lots of them over the course of 6.x, but of course there may be others. > I am eagerly waiting for ZFS. ZFS snapshots are certainly a thing of beauty. Kris From owner-freebsd-fs@FreeBSD.ORG Wed May 23 08:55:32 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 680) id F14B116A41F; Wed, 23 May 2007 08:55:32 +0000 (UTC) Date: Wed, 23 May 2007 08:55:32 +0000 From: Darren Reed To: Vince Message-ID: <20070523085532.GA27542@hub.freebsd.org> References: <20070407191517.GN63916@garage.freebsd.pl> <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4652B15D.5060505@unsane.co.uk> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, Craig Boston , freebsd-current@freebsd.org, Pawel Jakub Dawidek , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 08:55:33 -0000 On Tue, May 22, 2007 at 10:01:17AM +0100, Vince wrote: ... > I may reinstall at a later date as this is still very much a box to play > with, but I gather there is no great gain from going 64 bit other than > not having to play with PAE if you've got lots or RAM. It's not RAM that ZFS really likes but your KVA (Kernel Virtual Address) space. With a 32bit kernel you are more likely to experience problems with KVA shortage than you are RAM shortage when using ZFS. Darren From owner-freebsd-fs@FreeBSD.ORG Wed May 23 09:04:46 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C7CD16A400; Wed, 23 May 2007 09:04:46 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (keltia.freenix.org [82.230.37.243]) by mx1.freebsd.org (Postfix) with ESMTP id B513013C44B; Wed, 23 May 2007 09:04:45 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 2213F396E2; Wed, 23 May 2007 11:04:44 +0200 (CEST) Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 97122-05; Wed, 23 May 2007 11:04:43 +0200 (CEST) Received: by keltia.freenix.fr (Postfix/TLS, from userid 101) id B382E396DB; Wed, 23 May 2007 11:04:43 +0200 (CEST) Date: Wed, 23 May 2007 11:04:43 +0200 From: Ollivier Robert To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, Kris Kennaway Message-ID: <20070523090443.GA97506@keltia.freenix.fr> References: <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070523085532.GA27542@hub.freebsd.org> X-Operating-System: MacOS X / Macbook Pro - FreeBSD 6.2 / Dell D820 SMP User-Agent: Mutt/1.5.15 (2007-04-06) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Cc: Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 09:04:46 -0000 According to Darren Reed: > It's not RAM that ZFS really likes but your KVA (Kernel Virtual Address) > space. With a 32bit kernel you are more likely to experience problems > with KVA shortage than you are RAM shortage when using ZFS. It was discussed a bit at the DevSummit in BSDCan and an interesting question was raised. ZFS has its own buffer cache and tries as best as it can to bypass our own, taking its toll on memory and KVA. I don't think we could replace our buffer cache with ARC due to the license but it would be nice to reduce the duplication there. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr Darwin sidhe.keltia.net Kernel Version 8.9.1: Thu Feb 22 20:55:00 PST 2007 i386 From owner-freebsd-fs@FreeBSD.ORG Wed May 23 09:32:39 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 574D316A502; Wed, 23 May 2007 09:32:39 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 38A8913C447; Wed, 23 May 2007 09:32:39 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6186F1A3C19; Wed, 23 May 2007 02:33:37 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 993B2522DD; Wed, 23 May 2007 05:32:32 -0400 (EDT) Date: Wed, 23 May 2007 05:32:31 -0400 From: Kris Kennaway To: Darren Reed Message-ID: <20070523093231.GA29797@xor.obsecurity.org> References: <20070407212413.GK8831@cicely12.cicely.de> <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <20070523085532.GA27542@hub.freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: Craig Boston , Pawel Jakub Dawidek , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Kris Kennaway , Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 09:32:39 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 23, 2007 at 08:55:32AM +0000, Darren Reed wrote: > On Tue, May 22, 2007 at 10:01:17AM +0100, Vince wrote: > ... > > I may reinstall at a later date as this is still very much a box to play > > with, but I gather there is no great gain from going 64 bit other than > > not having to play with PAE if you've got lots or RAM. >=20 > It's not RAM that ZFS really likes but your KVA (Kernel Virtual Address) > space. With a 32bit kernel you are more likely to experience problems > with KVA shortage than you are RAM shortage when using ZFS. Currently in FreeBSD the issues are 1) space in the kmem_map, which is memory shared between various kernel systems and bounded to be smaller than the amount of address space dedicated to the kernel (KVA). The size of kmem_map depends on the amount of RAM in the system by default (but can be overridden at compile or boot time), 2) the size of the KVA, the "container" that all of the addressible data in the kernel must fit into. The first is actually the major issue for most people. This is partly because the mechanisms that are supposed to provide backpressure to reduce memory usage when space is becoming tight need some further adaptation and extension to work with ZFS, and also partly because ZFS typically wants to allocate hundreds of megabytes out the kmem_map which is just not sized with this expectation in mind (it would usually be "wasted" in the pre-ZFS world). Problem 2) only becomes an issue when you try to increase the size of kmem_map to deal with problem 1), and you find that when you make it too large you exceed the size of the "container", i.e. the total amount of KVA. In this situation you could just increase KVA, but of course there are tradeoffs (e.g. less address space available to user processes). Plain ZFS (i.e. as it exists in Solaris) actually has very different ideas about the memory it should be allowed to use. These ideas were completely inappropriate on FreeBSD and were mostly corrected here: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/contrib/opensolaris/uts/commo= n/fs/zfs/arc.c.diff?r1=3D1.5;r2=3D1.6 /* Start out with 1/8 of all memory */ - arc_c =3D physmem * PAGESIZE / 8; + arc_c =3D kmem_size() / 8; - /* set min cache to 1/32 of all memory, or 64MB, whichever is more */ - arc_c_min =3D MAX(arc_c / 4, 64<<20); - /* set max to 3/4 of all memory, or all but 1GB, whichever is more */ + /* set min cache to 1/32 of all memory, or 16MB, whichever is more */ + arc_c_min =3D MAX(arc_c / 4, 64<<18); + /* set max to 1/2 of all memory, or all but 1GB, whichever is more */ i.e. plain ZFS wants to use 3/4 of the *physical* RAM in the system (or all but 1GB). i.e. if you have 16GB in your system then zfs will try to use up to 15GB of it for caching leaving only 1GB for everything else (kernel + userland). I would actually be interested to know how Solaris gets away with this. It sounds like there must be less of a distinction between memory allocated to the kernel and to userland, and the ability for memory to flow between these two with some form of backpressure when userland wants memory that is currently gobbled by up solaris ZFS. This kind of system probably makes good sense (although maybe there are trade-offs), but anyway it's not how FreeBSD does it. Kris --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGVAouWry0BWjoQKURAluEAKDw4ijRNrHhbzhpkFBHSKL0vEI1lgCfe+sB FtA8Wrj0CQZJMa+uNAOXIrg= =9fDI -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- From owner-freebsd-fs@FreeBSD.ORG Wed May 23 10:06:32 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6F87916A469; Wed, 23 May 2007 10:06:32 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 5916E13C448; Wed, 23 May 2007 10:06:32 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id BC0051A4D80; Wed, 23 May 2007 03:07:32 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7AFE8513AD; Wed, 23 May 2007 06:06:31 -0400 (EDT) Date: Wed, 23 May 2007 06:06:31 -0400 From: Kris Kennaway To: Kris Kennaway Message-ID: <20070523100631.GA30143@xor.obsecurity.org> References: <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070523093231.GA29797@xor.obsecurity.org> User-Agent: Mutt/1.4.2.2i Cc: Craig Boston , Pawel Jakub Dawidek , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Darren Reed , Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 10:06:32 -0000 On Wed, May 23, 2007 at 05:32:31AM -0400, Kris Kennaway wrote: > I would actually be interested to know how Solaris gets away with > this. It sounds like there must be less of a distinction between > memory allocated to the kernel and to userland, and the ability for > memory to flow between these two with some form of backpressure when > userland wants memory that is currently gobbled by up solaris ZFS. > > This kind of system probably makes good sense (although maybe there > are trade-offs), but anyway it's not how FreeBSD does it. After some further thought I guess the difference is just that on a 64-bit kernel you don't have KVA issues and can indeed map all of physical RAM into the kernel for caching. Kris From owner-freebsd-fs@FreeBSD.ORG Wed May 23 15:59:04 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DC0E616A46C; Wed, 23 May 2007 15:59:04 +0000 (UTC) (envelope-from bp@barryp.org) Received: from eden.barryp.org (host-42-60-230-24.midco.net [24.230.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id AAE4F13C468; Wed, 23 May 2007 15:59:04 +0000 (UTC) (envelope-from bp@barryp.org) Received: from geo.med.und.nodak.edu ([134.129.166.11]) by eden.barryp.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HqtEt-000I3b-5R; Wed, 23 May 2007 10:59:03 -0500 Message-ID: <46546489.1030304@barryp.org> Date: Wed, 23 May 2007 10:58:01 -0500 From: Barry Pederson User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: freebsd.ruomad@free.fr References: <46458EDE.5060909@free.fr> <464BFBCB.1030300@free.fr> <20070517105346.GA3012@garage.freebsd.pl> <1179934338.46545e8270392@imp.free.fr> In-Reply-To: <1179934338.46545e8270392@imp.free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: zfs root is not mounted automatically X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 15:59:05 -0000 freebsd.ruomad@free.fr wrote: >>> Anyone has an idea on how to get the normal mode to work automatically (not >> that I cannot live with verbose dmesg, but...) >> >> I'll look into this once I'm back from BSDCan. >> > > Hello Pawel, > > I rebuilded everything (thanks to gcc 4.2) : world and ports. > The problem remains and has sort of grown worse as now even the verbose boot > does not result in my root being mounted properly (automatically). > > Do you have a clue or some idea of what I can test now to help solving this > problem. > Am I the only one to see this ? Bruno: So does it mount OK after you manually enter the root? I'm having a problem very frequently where it picks up the zfs_load="YES" vfs.root.mountfrom="zfs:tank/root" OK in the loader, but hangs when booting at: ------ . . . WARNING: ZFS is considered to be an experimental feature in FreeBSD ZFS filesystem version 6 ZFS storage pool version 6 Trying to mount root from zfs:tank/root ------ and then it just sits there. But on other occasions, it gets past that and boots fine. This is without recompiling or anything - so I'm not sure what's changing (LOR?) Anyhow, not sure if that's the same what you're seeing, but I thought I'd mention it. Barry From owner-freebsd-fs@FreeBSD.ORG Wed May 23 16:44:51 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A5BAD16A468; Wed, 23 May 2007 16:44:51 +0000 (UTC) (envelope-from bp@barryp.org) Received: from eden.barryp.org (host-42-60-230-24.midco.net [24.230.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 755D213C484; Wed, 23 May 2007 16:44:51 +0000 (UTC) (envelope-from bp@barryp.org) Received: from geo.med.und.nodak.edu ([134.129.166.11]) by eden.barryp.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63 (FreeBSD)) (envelope-from ) id 1HqtxB-000Ip1-Rh; Wed, 23 May 2007 11:44:50 -0500 Message-ID: <46546F44.8050003@barryp.org> Date: Wed, 23 May 2007 11:43:48 -0500 From: Barry Pederson User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: freebsd.ruomad@free.fr References: <46458EDE.5060909@free.fr> <464BFBCB.1030300@free.fr> <20070517105346.GA3012@garage.freebsd.pl> <1179934338.46545e8270392@imp.free.fr> <46546489.1030304@barryp.org> <1179941589.46547ad55ac68@imp.free.fr> In-Reply-To: <1179941589.46547ad55ac68@imp.free.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek Subject: Re: zfs root is not mounted automatically X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 16:44:51 -0000 freebsd.ruomad@free.fr wrote: > Not sure if it's the same ? > The point is that the I get the messgaes > Trying to mount root from zfs:tank/root > and the mountroot> prompt > BEFORE the following messages > ZFS filesystem version 6 > ZFS storage pool version 6 > > If I enter : zfs:system at the prompt, it boots allright. > On occasions, booting in verbose mode, I got the "version 6" messages before > trying to mount root, and then everything just works fine. > It's not the case since my last buildworld though :( This jumps out at me from one of your earlier messages as being something different from what I've see on my fairly stock setup: fuse4bsd: version 0.3.0, FUSE ABI 7.8 Is that a kernel module loaded from your /boot/loader.conf ? Have you tried without that? Barry From owner-freebsd-fs@FreeBSD.ORG Wed May 23 16:51:14 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 08C4D16A46E; Wed, 23 May 2007 16:51:14 +0000 (UTC) (envelope-from freebsd.ruomad@free.fr) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by mx1.freebsd.org (Postfix) with ESMTP id BD3AA13C468; Wed, 23 May 2007 16:51:13 +0000 (UTC) (envelope-from freebsd.ruomad@free.fr) Received: from imp3-g19.free.fr (imp3-g19.free.fr [212.27.42.3]) by smtp5-g19.free.fr (Postfix) with ESMTP id 2B21344FC9; Wed, 23 May 2007 18:51:13 +0200 (CEST) Received: by imp3-g19.free.fr (Postfix, from userid 33) id EDC9D12AB1; Wed, 23 May 2007 19:51:12 +0200 (CEST) Received: from 194.250.38.4 ([194.250.38.4]) by imp.free.fr (IMP) with HTTP for ; Wed, 23 May 2007 19:51:12 +0200 Message-ID: <1179942672.46547f10d83a7@imp.free.fr> Date: Wed, 23 May 2007 19:51:12 +0200 From: freebsd.ruomad@free.fr To: Barry Pederson References: <46458EDE.5060909@free.fr> <464BFBCB.1030300@free.fr> <20070517105346.GA3012@garage.freebsd.pl> <1179934338.46545e8270392@imp.free.fr> <46546489.1030304@barryp.org> <1179941589.46547ad55ac68@imp.free.fr> <46546F44.8050003@barryp.org> In-Reply-To: <46546F44.8050003@barryp.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 194.250.38.4 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek , freebsd.ruomad@free.fr Subject: Re: zfs root is not mounted automatically X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 16:51:14 -0000 Selon Barry Pederson : > freebsd.ruomad@free.fr wrote: > > > Not sure if it's the same ? > > The point is that the I get the messgaes > > Trying to mount root from zfs:tank/root > > and the mountroot> prompt > > BEFORE the following messages > > ZFS filesystem version 6 > > ZFS storage pool version 6 > > > > If I enter : zfs:system at the prompt, it boots allright. > > On occasions, booting in verbose mode, I got the "version 6" messages > before > > trying to mount root, and then everything just works fine. > > It's not the case since my last buildworld though :( > > This jumps out at me from one of your earlier messages as being > something different from what I've see on my fairly stock setup: > > fuse4bsd: version 0.3.0, FUSE ABI 7.8 > > Is that a kernel module loaded from your /boot/loader.conf ? Have you > tried without that? > It's a kernel module loaded for ntfs access (fusefs-ntfs) to my win$ partition. No I didn't try to disable it, but I will do it and report. Do you think it might be some conflict between these 2 ? Thanks Bruno From owner-freebsd-fs@FreeBSD.ORG Wed May 23 17:34:16 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16A6A16A41F for ; Wed, 23 May 2007 17:34:16 +0000 (UTC) (envelope-from freebsd.ruomad@free.fr) Received: from postfix1-g20.free.fr (postfix1-g20.free.fr [212.27.60.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9FC7C13C4AD for ; Wed, 23 May 2007 17:34:15 +0000 (UTC) (envelope-from freebsd.ruomad@free.fr) Received: from smtp5-g19.free.fr (smtp5-g19.free.fr [212.27.42.35]) by postfix1-g20.free.fr (Postfix) with ESMTP id 5ACF21062866 for ; Wed, 23 May 2007 18:33:11 +0200 (CEST) Received: from imp3-g19.free.fr (imp3-g19.free.fr [212.27.42.3]) by smtp5-g19.free.fr (Postfix) with ESMTP id A525F44FC9; Wed, 23 May 2007 18:33:09 +0200 (CEST) Received: by imp3-g19.free.fr (Postfix, from userid 33) id 6CE2D12AB1; Wed, 23 May 2007 19:33:09 +0200 (CEST) Received: from 194.250.38.4 ([194.250.38.4]) by imp.free.fr (IMP) with HTTP for ; Wed, 23 May 2007 19:33:09 +0200 Message-ID: <1179941589.46547ad55ac68@imp.free.fr> Date: Wed, 23 May 2007 19:33:09 +0200 From: freebsd.ruomad@free.fr To: Barry Pederson References: <46458EDE.5060909@free.fr> <464BFBCB.1030300@free.fr> <20070517105346.GA3012@garage.freebsd.pl> <1179934338.46545e8270392@imp.free.fr> <46546489.1030304@barryp.org> In-Reply-To: <46546489.1030304@barryp.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.5 X-Originating-IP: 194.250.38.4 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org, Pawel Jakub Dawidek , freebsd.ruomad@free.fr Subject: Re: zfs root is not mounted automatically X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 17:34:16 -0000 Selon Barry Pederson : > freebsd.ruomad@free.fr wrote: > >>> Anyone has an idea on how to get the normal mode to work automatically > (not > >> that I cannot live with verbose dmesg, but...) > >> > >> I'll look into this once I'm back from BSDCan. > >> > > > > Hello Pawel, > > > > I rebuilded everything (thanks to gcc 4.2) : world and ports. > > The problem remains and has sort of grown worse as now even the verbose > boot > > does not result in my root being mounted properly (automatically). > > > > Do you have a clue or some idea of what I can test now to help solving this > > problem. > > Am I the only one to see this ? > > Bruno: > > So does it mount OK after you manually enter the root? > > I'm having a problem very frequently where it picks up the > > zfs_load="YES" > vfs.root.mountfrom="zfs:tank/root" > > OK in the loader, but hangs when booting at: > . > WARNING: ZFS is considered to be an experimental feature in FreeBSD > ZFS filesystem version 6 > ZFS storage pool version 6 > Trying to mount root from zfs:tank/root > ------ > > and then it just sits there. But on other occasions, it gets past that > and boots fine. This is without recompiling or anything - so I'm not > sure what's changing (LOR?) > > Anyhow, not sure if that's the same what you're seeing, but I thought > I'd mention it. > Not sure if it's the same ? The point is that the I get the messgaes Trying to mount root from zfs:tank/root and the mountroot> prompt BEFORE the following messages ZFS filesystem version 6 ZFS storage pool version 6 If I enter : zfs:system at the prompt, it boots allright. On occasions, booting in verbose mode, I got the "version 6" messages before trying to mount root, and then everything just works fine. It's not the case since my last buildworld though :( Bruno From owner-freebsd-fs@FreeBSD.ORG Wed May 23 18:19:06 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4651F16A421; Wed, 23 May 2007 18:19:06 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 306F013C455; Wed, 23 May 2007 18:19:06 +0000 (UTC) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 012F11A4D83; Wed, 23 May 2007 11:20:07 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3513C52EE3; Wed, 23 May 2007 14:19:05 -0400 (EDT) Date: Wed, 23 May 2007 14:19:04 -0400 From: Kris Kennaway To: Ivan Voras Message-ID: <20070523181903.GA60674@xor.obsecurity.org> References: <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 18:19:06 -0000 On Wed, May 23, 2007 at 12:11:52PM +0200, Ivan Voras wrote: > Kris Kennaway wrote: > > >i.e. plain ZFS wants to use 3/4 of the *physical* RAM in the system > >(or all but 1GB). i.e. if you have 16GB in your system then zfs will > >try to use up to 15GB of it for caching leaving only 1GB for > >everything else (kernel + userland). > > > >I would actually be interested to know how Solaris gets away with > >this. It sounds like there must be less of a distinction between > >memory allocated to the kernel and to userland, and the ability for > >memory to flow between these two with some form of backpressure when > >userland wants memory that is currently gobbled by up solaris ZFS. > > Isn't it adequately explained with Sparc being a 64-bit platform? Not entirely, because solaris also runs on i386 (this is what was confusing me). I guess the answer is that ZFS has similar issues on Solaris i386 that it did on FreeBSD i386. Kris From owner-freebsd-fs@FreeBSD.ORG Wed May 23 18:44:02 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CF5916A469 for ; Wed, 23 May 2007 18:44:02 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.freebsd.org (Postfix) with ESMTP id 3511213C543 for ; Wed, 23 May 2007 18:44:00 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by ug-out-1314.google.com with SMTP id g33so590404ugd for ; Wed, 23 May 2007 11:44:00 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=K2IZVSC3Zsxh79LEks0h2pjny9U/BdjpGQyytbwqjZJXp/8Fe5MKQ8U+cOn/MCGfjvSBascDKxhYmwfIUENNwexPRjrqGcrDQHiH3FttDVLo7GRZ8IWNVc/CtSvtXD0RtcaIj7wtmJXvImXwg0smdxDTYYBUJEqpDD8pWNIWakQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=RlRx6QlLa3QykO21QuMDvift8Z0SzK5NTXZsUvSaz3ko9kBIxzp7YLx75IjIcoPgQWDZdhlc05Tzm24DUOgGuyv9yqCx2IYB2zv4h0n2uPuT2+xDf2Om1w+u6gAl1r75jLN2U0UlldIqQXEXcAdQoVcL0SMwDXaxtP6S8oPydew= Received: by 10.78.123.5 with SMTP id v5mr232204huc.1179945134036; Wed, 23 May 2007 11:32:14 -0700 (PDT) Received: by 10.78.107.13 with HTTP; Wed, 23 May 2007 11:32:13 -0700 (PDT) Message-ID: Date: Wed, 23 May 2007 11:32:13 -0700 From: "Kip Macy" To: "Kris Kennaway" In-Reply-To: <20070523181903.GA60674@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070410003837.GB8189@nowhere> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <20070523181903.GA60674@xor.obsecurity.org> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Ivan Voras Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 18:44:02 -0000 > Not entirely, because solaris also runs on i386 (this is what was > confusing me). I guess the answer is that ZFS has similar issues on > Solaris i386 that it did on FreeBSD i386. My understanding is that Sun has more or less abandoned 32-bit x86 in favor of x86_64. -Kip From owner-freebsd-fs@FreeBSD.ORG Wed May 23 21:06:40 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EE2616A41F; Wed, 23 May 2007 21:06:40 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id 000D613C447; Wed, 23 May 2007 21:06:39 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id EC9DC48809; Wed, 23 May 2007 23:06:37 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 7771948804; Wed, 23 May 2007 23:06:32 +0200 (CEST) Date: Wed, 23 May 2007 23:06:26 +0200 From: Pawel Jakub Dawidek To: Bruno Damour Message-ID: <20070523210625.GC11105@garage.freebsd.pl> References: <46458EDE.5060909@free.fr> <464BFBCB.1030300@free.fr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline In-Reply-To: <464BFBCB.1030300@free.fr> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: zfs root is not mounted automatically X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 21:06:40 -0000 --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 17, 2007 at 08:52:59AM +0200, Bruno Damour wrote: > Bruno Damour wrote: > >Hello, > >I have successfullty moved my root to zfs (some work, though) following = Pawel instruction. > >Anyway, it still refuses to boot without asking root device from cmd lin= e : > > > >acd0: DVDR at ata0-master UDMA66 > >ad10: 238475MB at ata5-master SATA150 > >ad12: 305245MB at ata6-master SATA150 > >pcm0: > >pcm0: > >WARNING: ZFS is considered to be an experimental feature in FreeBSD. > >SMP: AP CPU #1 Launched! > >Trying to mount root from zfs:system > > > >Manual root filesystem specification: > > : Mount using filesystem > > eg. ufs:da0s1a > > ? List valid disk boot devices > > Abort manual input > > > >mountroot> ZFS filesystem version 6 > >ZFS storage pool version 6 > >zfs:system > >Trying to mount root from zfs:system > >fuse4bsd: version 0.3.0, FUSE ABI 7.8 > > > >It first fails to mount my zfs:system > >I get the mountroot cmd line, and if I type zfs:system, boot resumes and= completes allright. > > > >Any idea of how to get rid of this ? Can you try this patch: http://people.freebsd.org/~pjd/patches/zfs_root.patch --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --KFztAG8eRSV9hGtP Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGVKzRForvXbEpPzQRAnCAAKCAglkQcAUYN6cgKEFygbZUZvgs/gCfRNU4 0Qfnf+ciqIl2QU2OA9Kw7iY= =FGaV -----END PGP SIGNATURE----- --KFztAG8eRSV9hGtP-- From owner-freebsd-fs@FreeBSD.ORG Wed May 23 22:56:18 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4A53F16A421; Wed, 23 May 2007 22:56:18 +0000 (UTC) (envelope-from freebsd.ruomad@free.fr) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.freebsd.org (Postfix) with ESMTP id 14AE913C4AE; Wed, 23 May 2007 22:56:17 +0000 (UTC) (envelope-from freebsd.ruomad@free.fr) Received: from vil1.ruomad.net (vln78-1-82-238-160-33.fbx.proxad.net [82.238.160.33]) by smtp2-g19.free.fr (Postfix) with ESMTP id C2BFA93FBC; Thu, 24 May 2007 00:56:16 +0200 (CEST) Message-ID: <4654C690.5010003@free.fr> Date: Thu, 24 May 2007 00:56:16 +0200 From: Bruno Damour User-Agent: Thunderbird 2.0.0.0 (X11/20070522) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <46458EDE.5060909@free.fr> <464BFBCB.1030300@free.fr> <20070523210625.GC11105@garage.freebsd.pl> In-Reply-To: <20070523210625.GC11105@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: zfs root is not mounted automatically X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 22:56:18 -0000 Pawel Jakub Dawidek wrote: > On Thu, May 17, 2007 at 08:52:59AM +0200, Bruno Damour wrote: > >> Bruno Damour wrote: >> >>> Hello, >>> I have successfullty moved my root to zfs (some work, though) following Pawel instruction. >>> Anyway, it still refuses to boot without asking root device from cmd line : >>> >>> acd0: DVDR at ata0-master UDMA66 >>> ad10: 238475MB at ata5-master SATA150 >>> ad12: 305245MB at ata6-master SATA150 >>> pcm0: >>> pcm0: >>> WARNING: ZFS is considered to be an experimental feature in FreeBSD. >>> SMP: AP CPU #1 Launched! >>> Trying to mount root from zfs:system >>> >>> Manual root filesystem specification: >>> : Mount using filesystem >>> eg. ufs:da0s1a >>> ? List valid disk boot devices >>> Abort manual input >>> >>> mountroot> ZFS filesystem version 6 >>> ZFS storage pool version 6 >>> zfs:system >>> Trying to mount root from zfs:system >>> fuse4bsd: version 0.3.0, FUSE ABI 7.8 >>> >>> It first fails to mount my zfs:system >>> I get the mountroot cmd line, and if I type zfs:system, boot resumes and completes allright. >>> >>> Any idea of how to get rid of this ? >>> > > Can you try this patch: > > http://people.freebsd.org/~pjd/patches/zfs_root.patch > > Works allright. I tested it with : - normal boot - single user boot - verbose boot and everything works as expected. Thanks a lot for your work ! ZFS is great Bruno From owner-freebsd-fs@FreeBSD.ORG Thu May 24 05:03:03 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BADE16A47D; Thu, 24 May 2007 05:03:03 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx03.syd.optusnet.com.au (fallbackmx03.syd.optusnet.com.au [211.29.133.136]) by mx1.freebsd.org (Postfix) with ESMTP id 2176413C448; Thu, 24 May 2007 05:02:58 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from mail31.syd.optusnet.com.au (mail31.syd.optusnet.com.au [211.29.132.102]) by fallbackmx03.syd.optusnet.com.au (8.12.11.20060308/8.12.11) with ESMTP id l4NBlsmw007666; Wed, 23 May 2007 21:47:54 +1000 Received: from besplex.bde.org (c211-30-216-190.carlnfd3.nsw.optusnet.com.au [211.30.216.190]) by mail31.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id l4NBjE4x001436 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 May 2007 21:45:15 +1000 Date: Wed, 23 May 2007 21:45:16 +1000 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Kris Kennaway In-Reply-To: <20070523100631.GA30143@xor.obsecurity.org> Message-ID: <20070523212559.V10628@besplex.bde.org> References: <20070410003505.GA8189@nowhere> <20070410003837.GB8189@nowhere> <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <20070523100631.GA30143@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Craig Boston , Pawel Jakub Dawidek , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Darren Reed , Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 05:03:03 -0000 On Wed, 23 May 2007, Kris Kennaway wrote: > On Wed, May 23, 2007 at 05:32:31AM -0400, Kris Kennaway wrote: > >> I would actually be interested to know how Solaris gets away with >> this. It sounds like there must be less of a distinction between >> memory allocated to the kernel and to userland, and the ability for >> memory to flow between these two with some form of backpressure when >> userland wants memory that is currently gobbled by up solaris ZFS. >> >> This kind of system probably makes good sense (although maybe there >> are trade-offs), but anyway it's not how FreeBSD does it. > > After some further thought I guess the difference is just that on a > 64-bit kernel you don't have KVA issues and can indeed map all of > physical RAM into the kernel for caching. This should probably happen for 64-bit kernels in FreeBSD too. FreeBSD sizes the buffer map part of KVA in the same way on all arches, to squeeze it into the limited available space on i386's, and has large complexity and some loss of performance in the buffer cache in order to work with the limited KVA. (Very old versions had less complexity and a large loss of performance.) Bruce From owner-freebsd-fs@FreeBSD.ORG Thu May 24 09:57:14 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 680) id 506CD16A46B; Thu, 24 May 2007 09:57:14 +0000 (UTC) Date: Thu, 24 May 2007 09:57:14 +0000 From: Darren Reed To: Bruce Evans Message-ID: <20070524095714.GA52149@hub.freebsd.org> References: <20070410011125.GB38535@xor.obsecurity.org> <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <20070523100631.GA30143@xor.obsecurity.org> <20070523212559.V10628@besplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070523212559.V10628@besplex.bde.org> User-Agent: Mutt/1.4.2.1i Cc: Craig Boston , Pawel Jakub Dawidek , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Kris Kennaway , Vince Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 09:57:14 -0000 On Wed, May 23, 2007 at 09:45:16PM +1000, Bruce Evans wrote: > On Wed, 23 May 2007, Kris Kennaway wrote: > > >On Wed, May 23, 2007 at 05:32:31AM -0400, Kris Kennaway wrote: > > > >>I would actually be interested to know how Solaris gets away with > >>this. It sounds like there must be less of a distinction between > >>memory allocated to the kernel and to userland, and the ability for > >>memory to flow between these two with some form of backpressure when > >>userland wants memory that is currently gobbled by up solaris ZFS. > >> > >>This kind of system probably makes good sense (although maybe there > >>are trade-offs), but anyway it's not how FreeBSD does it. > > > >After some further thought I guess the difference is just that on a > >64-bit kernel you don't have KVA issues and can indeed map all of > >physical RAM into the kernel for caching. > > This should probably happen for 64-bit kernels in FreeBSD too. FreeBSD > sizes the buffer map part of KVA in the same way on all arches, to squeeze > it into the limited available space on i386's, and has large complexity > and some loss of performance in the buffer cache in order to work with > the limited KVA. (Very old versions had less complexity and a large loss > of performance.) Do we support variable page sizes in the kernel for amd64? Darren From owner-freebsd-fs@FreeBSD.ORG Thu May 24 10:01:25 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 680) id 94B4F16A46E; Thu, 24 May 2007 10:01:25 +0000 (UTC) Date: Thu, 24 May 2007 10:01:25 +0000 From: Darren Reed To: Kip Macy Message-ID: <20070524100125.GB52149@hub.freebsd.org> References: <20070410013034.GC8189@nowhere> <20070410014233.GD8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <20070523181903.GA60674@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Ivan Voras , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 10:01:25 -0000 On Wed, May 23, 2007 at 11:32:13AM -0700, Kip Macy wrote: > >Not entirely, because solaris also runs on i386 (this is what was > >confusing me). I guess the answer is that ZFS has similar issues on > >Solaris i386 that it did on FreeBSD i386. > > My understanding is that Sun has more or less abandoned 32-bit x86 in > favor of x86_64. I don't know where you got that from or how your arrived at that conclusion... While I don't know of any hardware that is *only* 32bit and sold by Sun, Solaris 10 runs on 32bit PCs and will do for the foreseeable future as I'm sure a good part of the opensolaris community would be upset if it were to be abandoned. Darren From owner-freebsd-fs@FreeBSD.ORG Thu May 24 12:21:22 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2E6E316A468 for ; Thu, 24 May 2007 12:21:22 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from qsrv03ps.mx.bigpond.com (qsrv03ps.mx.bigpond.com [144.140.82.183]) by mx1.freebsd.org (Postfix) with ESMTP id B7FEA13C4B8 for ; Thu, 24 May 2007 12:21:21 +0000 (UTC) (envelope-from andrew@areilly.bpa.nu) Received: from oaamta03ps.mx.bigpond.com ([144.132.228.157]) by omta03ps.mx.bigpond.com with ESMTP id <20070524090738.YOUU8709.omta03ps.mx.bigpond.com@oaamta03ps.mx.bigpond.com> for ; Thu, 24 May 2007 09:07:38 +0000 Received: from areilly.bpa.nu ([144.132.228.157]) by oaamta03ps.mx.bigpond.com with ESMTP id <20070524090737.CAMR25364.oaamta03ps.mx.bigpond.com@areilly.bpa.nu> for ; Thu, 24 May 2007 09:07:37 +0000 Received: (qmail 66348 invoked by uid 501); 24 May 2007 09:07:29 -0000 Date: Thu, 24 May 2007 19:07:29 +1000 From: Andrew Reilly To: Eric Anderson Message-ID: <20070524090729.GA65213@duncan.reilly.home> References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <4652E5CD.6000901@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4652E5CD.6000901@freebsd.org> User-Agent: Mutt/1.4.2.2i Cc: freebsd-fs@freebsd.org, Gore Jarold Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 12:21:22 -0000 On Tue, May 22, 2007 at 07:45:01AM -0500, Eric Anderson wrote: > - why use GNU cp when you can use our own cp? You could do 'cp -Rpl' > instead. Indeed. Another option (my preference) is pax -rw -l -p e. Seems to work quite nicely (thanks to the OP for pointing out this variation on rsync backups, which I've been using for my laptop for a while...) Cheers, -- Andrew From owner-freebsd-fs@FreeBSD.ORG Thu May 24 13:46:17 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D4BA316A421 for ; Thu, 24 May 2007 13:46:17 +0000 (UTC) (envelope-from klim_serega@ufps.chita.ru) Received: from ufps.chita.ru (ufps.chita.ru [213.59.235.130]) by mx1.freebsd.org (Postfix) with ESMTP id B8C4113C44B for ; Thu, 24 May 2007 13:46:16 +0000 (UTC) (envelope-from klim_serega@ufps.chita.ru) Received: from ufps.chita.ru (localhost.ufps.chita.ru [127.0.0.1]) by ufps.chita.ru (Postfix) with ESMTP id C1F0C410E60 for ; Thu, 24 May 2007 23:46:14 +1000 (YAKST) Received: from [10.200.110.142] (unknown [87.103.236.113]) by ufps.chita.ru (Postfix) with ESMTP id 64F0F410E30 for ; Thu, 24 May 2007 23:46:14 +1000 (YAKST) From: "Zver Z." To: freebsd-fs@freebsd.org Content-Type: multipart/mixed; boundary="=-ETfS36tLs1IuwtALdwwE" Date: Thu, 24 May 2007 23:31:14 +1000 Message-Id: <1180013474.1217.14.camel@XATA.RU> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV v0.9 on ufps.chita.ru X-Mailman-Approved-At: Thu, 24 May 2007 14:03:12 +0000 Subject: System crash while trying to unmount manually ejected USB Flash drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 13:46:17 -0000 --=-ETfS36tLs1IuwtALdwwE Content-Type: text/plain Content-Transfer-Encoding: 7bit test patch FreeBSD 6.2, (pycckie ya ploho znay engl, esli shto pishite na mail) _________________________________________________________________________________ It'is current problem) _________________________________________________________________________________ --- /sys/kern/vfs_subr.c Mon Dec 4 17:47:53 2006 +++ vfs_subr.c Thu May 17 20:31:58 2007 @@ -1029,8 +1029,10 @@ * enabled under INVARIANTS */ BO_LOCK(bo); - if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) - panic("vinvalbuf: dirty bufs"); + if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) { + printf("bufobj_invalbuf: warning panic not run, error=%d\n", error); + flags = 0; + } } } /* _________________________________________________________________________________ panic whith msdosfs on flash(page fault) _________________________________________________________________________________ --- /sys/fs/msdosfs/msdosfs_vnops.c Mon Mar 13 12:05:13 2006 +++ msdosfs_vnops.c Thu May 17 11:44:23 2007 @@ -1834,7 +1834,9 @@ printf("\tstartcluster %lu, dircluster %lu, diroffset %lu, ", dep->de_StartCluster, dep->de_dirclust, dep->de_diroffset); - printf("on dev %s\n", devtoname(dep->de_dev)); + if (dep->de_dev != NULL) { + printf("on dev %s\n", devtoname(dep->de_dev)); + } return (0); } _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/fs/msdosfs/msdosfs_vfsops.c Wed Dec 20 12:05:30 2006 +++ msdosfs_vfsops.c Wed May 16 21:24:03 2007 @@ -766,8 +766,10 @@ /* If the volume was mounted read/write, mark it clean now. */ if ((pmp->pm_flags & MSDOSFSMNT_RONLY) == 0) { error = markvoldirty(pmp, 0); - if (error && (flags & FORCECLOSE) == 0) + if (error && (flags & FORCECLOSE) == 0 && (error & ENXIO) == 0) return (error); + if (error & ENXIO) + error = 0; } #ifdef MSDOSFS_DEBUG { _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/ufs/ffs/ffs_vfsops.c Mon May 21 22:06:40 2007 +++ ffs_vfsops.c Mon May 21 22:07:35 2007 @@ -979,10 +979,12 @@ if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & (FS_UNCLEAN|FS_NEEDSFSCK) ? 0 : 1; error = ffs_sbupdate(ump, MNT_WAIT, 0); - if (error) { + if (error && (error & ENXIO) == 0) { fs->fs_clean = 0; return (error); } + if (error & ENXIO) + error = 0; } DROP_GIANT(); g_topology_lock(); _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/kern/vfs_mount.c Wed Oct 25 01:02:39 2006 +++ vfs_mount.c Thu May 17 11:48:49 2007 @@ -1194,6 +1194,10 @@ (flags & MNT_FORCE)) { error = VFS_UNMOUNT(mp, flags, td); } + if (error & ENXIO) { + printf("dounmount: error=%d\n", error); + error = VFS_UNMOUNT(mp, 0, td); + } vn_finished_write(mp); if (error) { /* Undo cdir/rdir and rootvnode changes made above. */ _________________________________________________________________________________ sorry my english))) --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=vfs_subr.patch Content-Type: text/x-patch; name=vfs_subr.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/kern/vfs_subr.c Mon Dec 4 17:47:53 2006 +++ vfs_subr.c Thu May 17 20:31:58 2007 @@ -1029,8 +1029,10 @@ * enabled under INVARIANTS */ BO_LOCK(bo); - if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) - panic("vinvalbuf: dirty bufs"); + if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) { + printf("bufobj_invalbuf: warning panic not run, error=%d\n", error); + flags = 0; + } } } /* --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=vfs_mount.patch Content-Type: text/x-patch; name=vfs_mount.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/kern/vfs_mount.c Wed Oct 25 01:02:39 2006 +++ vfs_mount.c Thu May 17 11:48:49 2007 @@ -1194,6 +1194,10 @@ (flags & MNT_FORCE)) { error = VFS_UNMOUNT(mp, flags, td); } + if (error & ENXIO) { + printf("dounmount: error=%d\n", error); + error = VFS_UNMOUNT(mp, 0, td); + } vn_finished_write(mp); if (error) { /* Undo cdir/rdir and rootvnode changes made above. */ --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=msdosfs_vnops.patch Content-Type: text/x-patch; name=msdosfs_vnops.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/fs/msdosfs/msdosfs_vnops.c Mon Mar 13 12:05:13 2006 +++ msdosfs_vnops.c Thu May 17 11:44:23 2007 @@ -1834,7 +1834,9 @@ printf("\tstartcluster %lu, dircluster %lu, diroffset %lu, ", dep->de_StartCluster, dep->de_dirclust, dep->de_diroffset); - printf("on dev %s\n", devtoname(dep->de_dev)); + if (dep->de_dev != NULL) { + printf("on dev %s\n", devtoname(dep->de_dev)); + } return (0); } --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=msdosfs_vfsops.patch Content-Type: text/x-patch; name=msdosfs_vfsops.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/fs/msdosfs/msdosfs_vfsops.c Wed Dec 20 12:05:30 2006 +++ msdosfs_vfsops.c Wed May 16 21:24:03 2007 @@ -766,8 +766,10 @@ /* If the volume was mounted read/write, mark it clean now. */ if ((pmp->pm_flags & MSDOSFSMNT_RONLY) == 0) { error = markvoldirty(pmp, 0); - if (error && (flags & FORCECLOSE) == 0) + if (error && (flags & FORCECLOSE) == 0 && (error & ENXIO) == 0) return (error); + if (error & ENXIO) + error = 0; } #ifdef MSDOSFS_DEBUG { --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=ffs_vfsops.patch Content-Type: text/x-patch; name=ffs_vfsops.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/ufs/ffs/ffs_vfsops.c Mon May 21 22:06:40 2007 +++ ffs_vfsops.c Mon May 21 22:07:35 2007 @@ -979,10 +979,12 @@ if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & (FS_UNCLEAN|FS_NEEDSFSCK) ? 0 : 1; error = ffs_sbupdate(ump, MNT_WAIT, 0); - if (error) { + if (error && (error & ENXIO) == 0) { fs->fs_clean = 0; return (error); } + if (error & ENXIO) + error = 0; } DROP_GIANT(); g_topology_lock(); --=-ETfS36tLs1IuwtALdwwE-- From owner-freebsd-fs@FreeBSD.ORG Thu May 24 13:46:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 32F8116A4C5 for ; Thu, 24 May 2007 13:46:20 +0000 (UTC) (envelope-from klim_serega@ufps.chita.ru) Received: from ufps.chita.ru (ufps.chita.ru [213.59.235.130]) by mx1.freebsd.org (Postfix) with ESMTP id 17BD013C455 for ; Thu, 24 May 2007 13:46:19 +0000 (UTC) (envelope-from klim_serega@ufps.chita.ru) Received: from ufps.chita.ru (localhost.ufps.chita.ru [127.0.0.1]) by ufps.chita.ru (Postfix) with ESMTP id A9D3441106F for ; Thu, 24 May 2007 23:46:17 +1000 (YAKST) Received: from [10.200.110.142] (unknown [87.103.236.113]) by ufps.chita.ru (Postfix) with ESMTP id 09B0141106C for ; Thu, 24 May 2007 23:46:17 +1000 (YAKST) From: "Zver Z." To: freebsd-fs@freebsd.org Content-Type: multipart/mixed; boundary="=-V00SXU+c5/QNwVIHHifs" Date: Thu, 24 May 2007 23:42:11 +1000 Message-Id: <1180014131.1422.3.camel@XATA.RU> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV v0.9 on ufps.chita.ru X-Mailman-Approved-At: Thu, 24 May 2007 14:03:12 +0000 Subject: System crash while trying to unmount manually ejected USB Flash drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 13:46:20 -0000 --=-V00SXU+c5/QNwVIHHifs Content-Type: text/plain Content-Transfer-Encoding: 7bit test patch FreeBSD 6.2, (pycckie ya ploho znay engl, esli shto pishite na mail) _________________________________________________________________________________ It'is current problem |:-) _________________________________________________________________________________ --- /sys/kern/vfs_subr.c Mon Dec 4 17:47:53 2006 +++ vfs_subr.c Thu May 17 20:31:58 2007 @@ -1029,8 +1029,10 @@ * enabled under INVARIANTS */ BO_LOCK(bo); - if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) - panic("vinvalbuf: dirty bufs"); + if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) { + printf("bufobj_invalbuf: warning panic not run, error=%d\n", error); + flags = 0; + } } } /* _________________________________________________________________________________ panic whith msdosfs on flash(page fault) _________________________________________________________________________________ --- /sys/fs/msdosfs/msdosfs_vnops.c Mon Mar 13 12:05:13 2006 +++ msdosfs_vnops.c Thu May 17 11:44:23 2007 @@ -1834,7 +1834,9 @@ printf("\tstartcluster %lu, dircluster %lu, diroffset %lu, ", dep->de_StartCluster, dep->de_dirclust, dep->de_diroffset); - printf("on dev %s\n", devtoname(dep->de_dev)); + if (dep->de_dev != NULL) { + printf("on dev %s\n", devtoname(dep->de_dev)); + } return (0); } _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/fs/msdosfs/msdosfs_vfsops.c Wed Dec 20 12:05:30 2006 +++ msdosfs_vfsops.c Wed May 16 21:24:03 2007 @@ -766,8 +766,10 @@ /* If the volume was mounted read/write, mark it clean now. */ if ((pmp->pm_flags & MSDOSFSMNT_RONLY) == 0) { error = markvoldirty(pmp, 0); - if (error && (flags & FORCECLOSE) == 0) + if (error && (flags & FORCECLOSE) == 0 && (error & ENXIO) == 0) return (error); + if (error & ENXIO) + error = 0; } #ifdef MSDOSFS_DEBUG { _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/ufs/ffs/ffs_vfsops.c Mon May 21 22:06:40 2007 +++ ffs_vfsops.c Mon May 21 22:07:35 2007 @@ -979,10 +979,12 @@ if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & (FS_UNCLEAN|FS_NEEDSFSCK) ? 0 : 1; error = ffs_sbupdate(ump, MNT_WAIT, 0); - if (error) { + if (error && (error & ENXIO) == 0) { fs->fs_clean = 0; return (error); } + if (error & ENXIO) + error = 0; } DROP_GIANT(); g_topology_lock(); _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/kern/vfs_mount.c Wed Oct 25 01:02:39 2006 +++ vfs_mount.c Thu May 17 11:48:49 2007 @@ -1194,6 +1194,10 @@ (flags & MNT_FORCE)) { error = VFS_UNMOUNT(mp, flags, td); } + if (error & ENXIO) { + printf("dounmount: error=%d\n", error); + error = VFS_UNMOUNT(mp, 0, td); + } vn_finished_write(mp); if (error) { /* Undo cdir/rdir and rootvnode changes made above. */ _________________________________________________________________________________ sorry my english))) --=-V00SXU+c5/QNwVIHHifs Content-Disposition: attachment; filename=ffs_vfsops.patch Content-Type: text/x-patch; name=ffs_vfsops.patch; charset=koi8-r Content-Transfer-Encoding: 7bit --- /sys/ufs/ffs/ffs_vfsops.c Mon May 21 22:06:40 2007 +++ ffs_vfsops.c Mon May 21 22:07:35 2007 @@ -979,10 +979,12 @@ if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & (FS_UNCLEAN|FS_NEEDSFSCK) ? 0 : 1; error = ffs_sbupdate(ump, MNT_WAIT, 0); - if (error) { + if (error && (error & ENXIO) == 0) { fs->fs_clean = 0; return (error); } + if (error & ENXIO) + error = 0; } DROP_GIANT(); g_topology_lock(); --=-V00SXU+c5/QNwVIHHifs Content-Disposition: attachment; filename=msdosfs_vfsops.patch Content-Type: text/x-patch; name=msdosfs_vfsops.patch; charset=koi8-r Content-Transfer-Encoding: 7bit --- /sys/fs/msdosfs/msdosfs_vfsops.c Wed Dec 20 12:05:30 2006 +++ msdosfs_vfsops.c Wed May 16 21:24:03 2007 @@ -766,8 +766,10 @@ /* If the volume was mounted read/write, mark it clean now. */ if ((pmp->pm_flags & MSDOSFSMNT_RONLY) == 0) { error = markvoldirty(pmp, 0); - if (error && (flags & FORCECLOSE) == 0) + if (error && (flags & FORCECLOSE) == 0 && (error & ENXIO) == 0) return (error); + if (error & ENXIO) + error = 0; } #ifdef MSDOSFS_DEBUG { --=-V00SXU+c5/QNwVIHHifs Content-Disposition: attachment; filename=msdosfs_vnops.patch Content-Type: text/x-patch; name=msdosfs_vnops.patch; charset=koi8-r Content-Transfer-Encoding: 7bit --- /sys/fs/msdosfs/msdosfs_vnops.c Mon Mar 13 12:05:13 2006 +++ msdosfs_vnops.c Thu May 17 11:44:23 2007 @@ -1834,7 +1834,9 @@ printf("\tstartcluster %lu, dircluster %lu, diroffset %lu, ", dep->de_StartCluster, dep->de_dirclust, dep->de_diroffset); - printf("on dev %s\n", devtoname(dep->de_dev)); + if (dep->de_dev != NULL) { + printf("on dev %s\n", devtoname(dep->de_dev)); + } return (0); } --=-V00SXU+c5/QNwVIHHifs Content-Disposition: attachment; filename=vfs_mount.patch Content-Type: text/x-patch; name=vfs_mount.patch; charset=koi8-r Content-Transfer-Encoding: 7bit --- /sys/kern/vfs_mount.c Wed Oct 25 01:02:39 2006 +++ vfs_mount.c Thu May 17 11:48:49 2007 @@ -1194,6 +1194,10 @@ (flags & MNT_FORCE)) { error = VFS_UNMOUNT(mp, flags, td); } + if (error & ENXIO) { + printf("dounmount: error=%d\n", error); + error = VFS_UNMOUNT(mp, 0, td); + } vn_finished_write(mp); if (error) { /* Undo cdir/rdir and rootvnode changes made above. */ --=-V00SXU+c5/QNwVIHHifs Content-Disposition: attachment; filename=vfs_subr.patch Content-Type: text/x-patch; name=vfs_subr.patch; charset=koi8-r Content-Transfer-Encoding: 7bit --- /sys/kern/vfs_subr.c Mon Dec 4 17:47:53 2006 +++ vfs_subr.c Thu May 17 20:31:58 2007 @@ -1029,8 +1029,10 @@ * enabled under INVARIANTS */ BO_LOCK(bo); - if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) - panic("vinvalbuf: dirty bufs"); + if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) { + printf("bufobj_invalbuf: warning panic not run, error=%d\n", error); + flags = 0; + } } } /* --=-V00SXU+c5/QNwVIHHifs-- From owner-freebsd-fs@FreeBSD.ORG Thu May 24 13:53:20 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 423EA16A421 for ; Thu, 24 May 2007 13:53:20 +0000 (UTC) (envelope-from klim_serega@ufps.chita.ru) Received: from ufps.chita.ru (ufps.chita.ru [213.59.235.130]) by mx1.freebsd.org (Postfix) with ESMTP id 2B2E913C45D for ; Thu, 24 May 2007 13:53:19 +0000 (UTC) (envelope-from klim_serega@ufps.chita.ru) Received: from ufps.chita.ru (localhost.ufps.chita.ru [127.0.0.1]) by ufps.chita.ru (Postfix) with ESMTP id DD85B41102B for ; Thu, 24 May 2007 23:35:17 +1000 (YAKST) Received: from [10.200.110.142] (unknown [87.103.236.113]) by ufps.chita.ru (Postfix) with ESMTP id 7FB30411021 for ; Thu, 24 May 2007 23:35:17 +1000 (YAKST) From: "Zver Z." To: freebsd-fs@freebsd.org Content-Type: multipart/mixed; boundary="=-ETfS36tLs1IuwtALdwwE" Date: Thu, 24 May 2007 23:31:14 +1000 Message-Id: <1180013474.1217.14.camel@XATA.RU> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1.1 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV v0.9 on ufps.chita.ru X-Mailman-Approved-At: Thu, 24 May 2007 14:03:12 +0000 Subject: System crash while trying to unmount manually ejected USB Flash drive X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 13:53:20 -0000 --=-ETfS36tLs1IuwtALdwwE Content-Type: text/plain Content-Transfer-Encoding: 7bit test patch FreeBSD 6.2, (pycckie ya ploho znay engl, esli shto pishite na mail) _________________________________________________________________________________ It'is current problem) _________________________________________________________________________________ --- /sys/kern/vfs_subr.c Mon Dec 4 17:47:53 2006 +++ vfs_subr.c Thu May 17 20:31:58 2007 @@ -1029,8 +1029,10 @@ * enabled under INVARIANTS */ BO_LOCK(bo); - if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) - panic("vinvalbuf: dirty bufs"); + if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) { + printf("bufobj_invalbuf: warning panic not run, error=%d\n", error); + flags = 0; + } } } /* _________________________________________________________________________________ panic whith msdosfs on flash(page fault) _________________________________________________________________________________ --- /sys/fs/msdosfs/msdosfs_vnops.c Mon Mar 13 12:05:13 2006 +++ msdosfs_vnops.c Thu May 17 11:44:23 2007 @@ -1834,7 +1834,9 @@ printf("\tstartcluster %lu, dircluster %lu, diroffset %lu, ", dep->de_StartCluster, dep->de_dirclust, dep->de_diroffset); - printf("on dev %s\n", devtoname(dep->de_dev)); + if (dep->de_dev != NULL) { + printf("on dev %s\n", devtoname(dep->de_dev)); + } return (0); } _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/fs/msdosfs/msdosfs_vfsops.c Wed Dec 20 12:05:30 2006 +++ msdosfs_vfsops.c Wed May 16 21:24:03 2007 @@ -766,8 +766,10 @@ /* If the volume was mounted read/write, mark it clean now. */ if ((pmp->pm_flags & MSDOSFSMNT_RONLY) == 0) { error = markvoldirty(pmp, 0); - if (error && (flags & FORCECLOSE) == 0) + if (error && (flags & FORCECLOSE) == 0 && (error & ENXIO) == 0) return (error); + if (error & ENXIO) + error = 0; } #ifdef MSDOSFS_DEBUG { _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/ufs/ffs/ffs_vfsops.c Mon May 21 22:06:40 2007 +++ ffs_vfsops.c Mon May 21 22:07:35 2007 @@ -979,10 +979,12 @@ if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & (FS_UNCLEAN|FS_NEEDSFSCK) ? 0 : 1; error = ffs_sbupdate(ump, MNT_WAIT, 0); - if (error) { + if (error && (error & ENXIO) == 0) { fs->fs_clean = 0; return (error); } + if (error & ENXIO) + error = 0; } DROP_GIANT(); g_topology_lock(); _________________________________________________________________________________ _________________________________________________________________________________ --- /sys/kern/vfs_mount.c Wed Oct 25 01:02:39 2006 +++ vfs_mount.c Thu May 17 11:48:49 2007 @@ -1194,6 +1194,10 @@ (flags & MNT_FORCE)) { error = VFS_UNMOUNT(mp, flags, td); } + if (error & ENXIO) { + printf("dounmount: error=%d\n", error); + error = VFS_UNMOUNT(mp, 0, td); + } vn_finished_write(mp); if (error) { /* Undo cdir/rdir and rootvnode changes made above. */ _________________________________________________________________________________ sorry my english))) --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=vfs_subr.patch Content-Type: text/x-patch; name=vfs_subr.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/kern/vfs_subr.c Mon Dec 4 17:47:53 2006 +++ vfs_subr.c Thu May 17 20:31:58 2007 @@ -1029,8 +1029,10 @@ * enabled under INVARIANTS */ BO_LOCK(bo); - if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) - panic("vinvalbuf: dirty bufs"); + if (bo->bo_numoutput > 0 || bo->bo_dirty.bv_cnt > 0) { + printf("bufobj_invalbuf: warning panic not run, error=%d\n", error); + flags = 0; + } } } /* --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=vfs_mount.patch Content-Type: text/x-patch; name=vfs_mount.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/kern/vfs_mount.c Wed Oct 25 01:02:39 2006 +++ vfs_mount.c Thu May 17 11:48:49 2007 @@ -1194,6 +1194,10 @@ (flags & MNT_FORCE)) { error = VFS_UNMOUNT(mp, flags, td); } + if (error & ENXIO) { + printf("dounmount: error=%d\n", error); + error = VFS_UNMOUNT(mp, 0, td); + } vn_finished_write(mp); if (error) { /* Undo cdir/rdir and rootvnode changes made above. */ --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=msdosfs_vnops.patch Content-Type: text/x-patch; name=msdosfs_vnops.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/fs/msdosfs/msdosfs_vnops.c Mon Mar 13 12:05:13 2006 +++ msdosfs_vnops.c Thu May 17 11:44:23 2007 @@ -1834,7 +1834,9 @@ printf("\tstartcluster %lu, dircluster %lu, diroffset %lu, ", dep->de_StartCluster, dep->de_dirclust, dep->de_diroffset); - printf("on dev %s\n", devtoname(dep->de_dev)); + if (dep->de_dev != NULL) { + printf("on dev %s\n", devtoname(dep->de_dev)); + } return (0); } --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=msdosfs_vfsops.patch Content-Type: text/x-patch; name=msdosfs_vfsops.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/fs/msdosfs/msdosfs_vfsops.c Wed Dec 20 12:05:30 2006 +++ msdosfs_vfsops.c Wed May 16 21:24:03 2007 @@ -766,8 +766,10 @@ /* If the volume was mounted read/write, mark it clean now. */ if ((pmp->pm_flags & MSDOSFSMNT_RONLY) == 0) { error = markvoldirty(pmp, 0); - if (error && (flags & FORCECLOSE) == 0) + if (error && (flags & FORCECLOSE) == 0 && (error & ENXIO) == 0) return (error); + if (error & ENXIO) + error = 0; } #ifdef MSDOSFS_DEBUG { --=-ETfS36tLs1IuwtALdwwE Content-Disposition: attachment; filename=ffs_vfsops.patch Content-Type: text/x-patch; name=ffs_vfsops.patch; charset=KOI8-R Content-Transfer-Encoding: 7bit --- /sys/ufs/ffs/ffs_vfsops.c Mon May 21 22:06:40 2007 +++ ffs_vfsops.c Mon May 21 22:07:35 2007 @@ -979,10 +979,12 @@ if (fs->fs_ronly == 0) { fs->fs_clean = fs->fs_flags & (FS_UNCLEAN|FS_NEEDSFSCK) ? 0 : 1; error = ffs_sbupdate(ump, MNT_WAIT, 0); - if (error) { + if (error && (error & ENXIO) == 0) { fs->fs_clean = 0; return (error); } + if (error & ENXIO) + error = 0; } DROP_GIANT(); g_topology_lock(); --=-ETfS36tLs1IuwtALdwwE-- From owner-freebsd-fs@FreeBSD.ORG Thu May 24 14:56:12 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 86F2B16A421 for ; Thu, 24 May 2007 14:56:12 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.237]) by mx1.freebsd.org (Postfix) with ESMTP id 283A513C480 for ; Thu, 24 May 2007 14:56:12 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: by qb-out-0506.google.com with SMTP id b14so354228qbc for ; Thu, 24 May 2007 07:56:11 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=NAY6o1jWqrzlsxzr5IPlr7l4k+XWdgT3xm1FkcX28d8noQlYYgYALyz75d0drU6P/QaG0V46jlgR3kgzoxBUYdNj6SHP7o8fC33d+nummWxpqWlmWn3q8LapiRFE3VMrj+XTeLL6WCNtor3ErE6XdD2y9UpYNwd3w5Csm9DoaP0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=LnvAZ3TXKrS3ultp046yzA3ZeMpt6ydvhSsWTW7CxMEbxHo8wSzmfpCFHz1z2zivnsB3Qu+u+wGgAXlVeBrsaZKmLrWaSEihbiGQeMaoTU80WGyatwrLbmfTq15H8n24A2W6lia/bGhYJN9+adJRGQTieY3I3uIsu2XXArTdpQY= Received: by 10.100.248.18 with SMTP id v18mr1561930anh.1180017011303; Thu, 24 May 2007 07:30:11 -0700 (PDT) Received: by 10.100.8.19 with HTTP; Thu, 24 May 2007 07:30:11 -0700 (PDT) Message-ID: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> Date: Thu, 24 May 2007 16:30:11 +0200 From: "Richard Noorlandt" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 14:56:12 -0000 Hi everybody, I'm currently configuring a large fileserver (Dual Opteron and an Areca 1160 for hardware RAID), and I'm running into some partitioning problems. Currently, I have 6 500 GB drives to put in a main RAID-6 array, giving me 2 TB of usable storage. Now, I want this 2 TB to be partitioned in several separate partitions of various sizes. The last partition will be 1 TB, and will be the most important partition on the array. Now my problem is that this 1 TB partition must be able to grow beyond 2 TB at a later stage (after adding extra HD's). If I understand correctly, it is not possible to grow a UFS partition beyond 2 TB when the drive is partitioned with fdisk. One should use GPT instead. However, it appears that GPT currently has no way to resize partitions, giving me no possibility to enlarge the 1TB partition and run growfs. Does anyone have a suggestion? Or am I overlooking something? I can hardly imagine that what I want is very rare, so I think there must be some solution. Best regards, Richard From owner-freebsd-fs@FreeBSD.ORG Thu May 24 15:19:47 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3BDFE16A41F for ; Thu, 24 May 2007 15:19:47 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30307.mail.mud.yahoo.com (web30307.mail.mud.yahoo.com [209.191.69.69]) by mx1.freebsd.org (Postfix) with SMTP id DE67F13C447 for ; Thu, 24 May 2007 15:19:46 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 52122 invoked by uid 60001); 24 May 2007 15:19:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=KwcmxU6p3zKVEraIyifSAUJVKhDkZbe1aZ86EQXdo/GPOmnXBj+YK3veYTy6NvNPjEsjDZM5OK10MNsUiaiRkDZvBGh1Wq7gikel3T5astUUVZjwJerHbvpkzbv7ammvlNtpZBUIwoVfR6hkxm0XFkrc1uY6TkDhL99M3POowkI=; X-YMail-OSG: F9mB79sVM1kMMtyJ.UVx6ok45WpvC.ggJ37rHbxsVbELN4W..2Oaj02ISNJOxrdMLoqWkFa4hAV3CaVu6_1.oKi7Rktb9MsO9vGDfr8pYt_But7dVjTXBu4Q68pCfg-- Received: from [213.54.162.102] by web30307.mail.mud.yahoo.com via HTTP; Thu, 24 May 2007 08:19:45 PDT Date: Thu, 24 May 2007 08:19:45 -0700 (PDT) From: Arne "Wörner" To: Richard Noorlandt , freebsd-fs@freebsd.org In-Reply-To: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <82231.51840.qm@web30307.mail.mud.yahoo.com> Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 15:19:47 -0000 --- Richard Noorlandt wrote: > Does anyone have a suggestion? Or am I overlooking something? I can hardly > imagine that what I want is very rare, so I think there must be some > solution. > 1. A better implementation for GPT is on its way... I think, the time frame was "several weeks"... It is in the archive of this list or freebsd-geom@... 2. I wonder, why u dont just delete all GPT partitions and re-create them (after u wrote down offset and size of the previous config)... :-) -Arne ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news From owner-freebsd-fs@FreeBSD.ORG Thu May 24 15:55:59 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C47D16A400 for ; Thu, 24 May 2007 15:55:59 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.236]) by mx1.freebsd.org (Postfix) with ESMTP id A1D4D13C458 for ; Thu, 24 May 2007 15:55:58 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: by qb-out-0506.google.com with SMTP id b14so384593qbc for ; Thu, 24 May 2007 08:55:57 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=sL66bJJv48ZoN2ON5rPuBWrAmHhW1n6+MDBGUR0KmT0EXWp1zqy7cyVk1AF5P/2RNhcEJkQVNS4Mkzax8Sx6C4M4FrXNuRTLK7OlcilXLwp6yyKkZKoooIhjXp0HBG7XQKbC2Nx1YA0SV90WRtuBD70Y9i7W1rYrf/BMv6EwPGc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=MejfPPt2YMfrxJSho49wdIC83lAR+xAyrvs5JHw2KoVmvJsU6rljndDuIV3WOClX0l6582DCX7xds7LPtkIIUJfghAmyx3Av1tETaHxhOhqxpU4yMBpKZacbbd/hEsjmDEjK9/KhcUZGf25Y/BguzyQo+FKuWxBO8xWyR2UegRc= Received: by 10.100.247.11 with SMTP id u11mr1651503anh.1180022157167; Thu, 24 May 2007 08:55:57 -0700 (PDT) Received: by 10.100.8.19 with HTTP; Thu, 24 May 2007 08:55:57 -0700 (PDT) Message-ID: <99c92b5f0705240855n4fb4c4d8xd5dbee26bdb52222@mail.gmail.com> Date: Thu, 24 May 2007 17:55:57 +0200 From: "Richard Noorlandt" To: freebsd-fs@freebsd.org In-Reply-To: <82231.51840.qm@web30307.mail.mud.yahoo.com> MIME-Version: 1.0 References: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> <82231.51840.qm@web30307.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 15:55:59 -0000 2007/5/24, Arne W=F6rner : > > --- Richard Noorlandt wrote: > > Does anyone have a suggestion? Or am I overlooking something? I can > hardly > > imagine that what I want is very rare, so I think there must be some > > solution. > > > 1. A better implementation for GPT is on its way... I think, the time > frame was > "several weeks"... It is in the archive of this list or freebsd-geom@... Will it be possible to create the tables with the current GPT tool, and later grow them safely with the new tool when it's available? It'll take some time before I need the extra TB's, so waiting a few weeks before I can grow the partitions and FS is no problem. As long as I can grow it without losing data. 2. I wonder, why u dont just delete all GPT partitions and re-create them > (after u wrote down offset and size of the previous config)... :-) > Wouldn't this destroy the data that's on the partitions? The problem is tha= t I have no way to backup or temporary store the data on the array. So all growing must be done without wiping the contents of the FS. Best regards, Richard From owner-freebsd-fs@FreeBSD.ORG Thu May 24 16:21:45 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A177B16A400 for ; Thu, 24 May 2007 16:21:45 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30305.mail.mud.yahoo.com (web30305.mail.mud.yahoo.com [209.191.69.67]) by mx1.freebsd.org (Postfix) with SMTP id 67B6113C448 for ; Thu, 24 May 2007 16:21:45 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 23723 invoked by uid 60001); 24 May 2007 16:21:44 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=KRhyDbHvYg2kh3xltc44Ai8ofVGGkFt7zkv7bkI0a2lZCXiKT9PxhQdlR4hPZi1xQPLfxxLfGU4cqyvIoSPh+MfRrZUq32PiMLWQH4tvj4eq6HWLD70sQyJs0kBXkvCLi7uAzG4RS1KIaj3TYNxeNEhPla6qYIbQ4/F/5PQrmv8=; X-YMail-OSG: 2CjIt6cVM1kmi12rp6BGgfgwC6mK6trNEPcXs3LTFA4GKIs6pUU.o53SIk5vHZ5zBYYN53Gi2gj5Qc0GhzYqFKWpV5TJxa_tTNNXDXU27ayj.D5rO2bY2oKUTLgz5g-- Received: from [213.54.162.102] by web30305.mail.mud.yahoo.com via HTTP; Thu, 24 May 2007 09:21:44 PDT Date: Thu, 24 May 2007 09:21:44 -0700 (PDT) From: Arne "Wörner" To: Richard Noorlandt , freebsd-fs@freebsd.org In-Reply-To: <99c92b5f0705240855n4fb4c4d8xd5dbee26bdb52222@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <889751.23477.qm@web30305.mail.mud.yahoo.com> Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 16:21:45 -0000 --- Richard Noorlandt wrote: > 2007/5/24, Arne Wörner : > > 1. A better implementation for GPT is on its way... I think, the time > > frame was > > "several weeks"... It is in the archive of this list or freebsd-geom@... > > Will it be possible to create the tables with the current GPT tool, and > later grow them safely with the new tool when it's available? It'll take > some time before I need the extra TB's, so waiting a few weeks before I can > grow the partitions and FS is no problem. As long as I can grow it without > losing data. > Dont know... > > 2. I wonder, why u dont just delete all GPT partitions and re-create them > > (after u wrote down offset and size of the previous config)... :-) > > > > Wouldn't this destroy the data that's on the partitions? The problem is that > I have no way to backup or temporary store the data on the array. So all > growing must be done without wiping the contents of the FS. > Dont know... I dont know how GPT works... But fdisk for example just fumbles around in the first 63 sectors of a disk... And I would strongly guess, that GPT does it similar... U could try it with a little test disk... or so... -Arne ____________________________________________________________________________________Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545469 From owner-freebsd-fs@FreeBSD.ORG Thu May 24 16:40:37 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 68B0316A468 for ; Thu, 24 May 2007 16:40:37 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: from ik-out-1112.google.com (ik-out-1112.google.com [66.249.90.181]) by mx1.freebsd.org (Postfix) with ESMTP id E19C413C4BD for ; Thu, 24 May 2007 16:40:36 +0000 (UTC) (envelope-from kip.macy@gmail.com) Received: by ik-out-1112.google.com with SMTP id c21so232956ika for ; Thu, 24 May 2007 09:40:35 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=PNPxWiqoYl2TRJTXju1eAYbsUIeyAtEViVzKe2UvVbgSQQo961B7xmoPCpeJ6HxT/nw1GJXviEBBaUWdjICxvygpUS5ed5oOGyn1OHPoeDDGDu4aFt3YkB8Ie6vLJlywtGX4gIbRT/kiaCEIPmnP8TQnsl9v/IIen5aRdbgtkMs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gGNIDgnht6xqJ8lzaxZ1T2f47P7tagyOjoW5KuYe25wxoSnsFmJpc0z98fwGomiCmGeae9GhfSbqdK4VwqqKWhcHmdkmU6Y8Yt1hmydS78iKakxpDP2Osi9HtI+yL/qABUmTOg2eDy+VvvAF+OQASF9YJccfznfrSzSgrXjmSDU= Received: by 10.78.171.13 with SMTP id t13mr595336hue.1180024835462; Thu, 24 May 2007 09:40:35 -0700 (PDT) Received: by 10.78.107.13 with HTTP; Thu, 24 May 2007 09:40:35 -0700 (PDT) Message-ID: Date: Thu, 24 May 2007 09:40:35 -0700 From: "Kip Macy" To: "Darren Reed" In-Reply-To: <20070524100125.GB52149@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070410013034.GC8189@nowhere> <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <20070523181903.GA60674@xor.obsecurity.org> <20070524100125.GB52149@hub.freebsd.org> Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Ivan Voras , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 16:40:37 -0000 > While I don't know of any hardware that is *only* 32bit and > sold by Sun, Solaris 10 runs on 32bit PCs and will do for the > foreseeable future as I'm sure a good part of the opensolaris > community would be upset if it were to be abandoned. Abandoned is the wrong word, but supported is definitely not the same as new development being targeted at. -Kip From owner-freebsd-fs@FreeBSD.ORG Thu May 24 17:34:52 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1015816A41F for ; Thu, 24 May 2007 17:34:52 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from sccrmhc15.comcast.net (sccrmhc15.comcast.net [204.127.200.85]) by mx1.freebsd.org (Postfix) with ESMTP id C8DCA13C455 for ; Thu, 24 May 2007 17:34:51 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from masq.tychl.net (tychl.no-ip.org[67.174.137.176]) by comcast.net (sccrmhc15) with ESMTP id <2007052417345101500pjbdae>; Thu, 24 May 2007 17:34:51 +0000 Received: from localhost (localhost [127.0.0.1]) by masq.tychl.net (Postfix) with ESMTP id D662E1CB4B; Thu, 24 May 2007 13:34:50 -0400 (EDT) X-Virus-Scanned: amavisd-new at tychl.net Received: from masq.tychl.net ([127.0.0.1]) by localhost (masq.tychl.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id LnrxqwdB3ev7; Thu, 24 May 2007 13:34:48 -0400 (EDT) Received: from [127.0.0.1] (unknown [172.16.160.245]) by masq.tychl.net (Postfix) with ESMTP id 0461B1CB4A; Thu, 24 May 2007 13:34:47 -0400 (EDT) Message-ID: <4655CCBB.2020403@tychl.net> Date: Thu, 24 May 2007 13:34:51 -0400 From: Nick Gustas User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Richard Noorlandt , freebsd-fs@freebsd.org References: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> In-Reply-To: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 17:34:52 -0000 Richard Noorlandt wrote: > Hi everybody, > > I'm currently configuring a large fileserver (Dual Opteron and an > Areca 1160 > for hardware RAID), and I'm running into some partitioning problems. > Currently, I have 6 500 GB drives to put in a main RAID-6 array, > giving me 2 > TB of usable storage. Now, I want this 2 TB to be partitioned in several > separate partitions of various sizes. The last partition will be 1 TB, > and > will be the most important partition on the array. > > Now my problem is that this 1 TB partition must be able to grow beyond > 2 TB > at a later stage (after adding extra HD's). If I understand correctly, > it is > not possible to grow a UFS partition beyond 2 TB when the drive is > partitioned with fdisk. One should use GPT instead. However, it > appears that > GPT currently has no way to resize partitions, giving me no > possibility to > enlarge the 1TB partition and run growfs. > > Does anyone have a suggestion? Or am I overlooking something? I can > hardly > imagine that what I want is very rare, so I think there must be some > solution. > > Best regards, > > Richard > _______________________________________________ > freebsd-fs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-fs > To unsubscribe, send any mail to "freebsd-fs-unsubscribe@freebsd.org" You should be able to simply finish the online expansion of the array, recreate your GPT partitions and run growfs. I recently did a OCE on an array with a single GPT partition containing ZFS on a 3ware controller and it worked fine. destroying the GPT partitioning doesn't hurt any data as long as you put it back the same way. order of operations was: OCE finished, one drive added to array. zpool export threeware gpt destroy da0 gpt create da0 gpt add da0 zpool import threeware everything was fine, all the data was there, just a bigger partition. I see no reason this wouldn't work with UFS over 2TB assuming you have some of the growfs patches that have been posted in the last few weeks. In your case I would record the commands you used to create the gpt partitions in the first place, or at least the output of gpt show assuming two main partitions you aren't going to resize, and a third you are going to resize. OCE finished umount /partitions gpt destroy da0 gpt add -i 1 -s youroriginalsizehere da0 gpt add -i 2 -s youroriginalsizehere da0 gpt add -i 3 da0 #use remainder of disk for your last partition, whatever that may be. growfs /dev/da0p3 mount /partitions All your data in the first two partitions should be fine with intact original data, and assuming growfs did its job, your third should be there too I have a few minutes and a free 7.0 system handy here. I don't have time to do an actual array expansion, but, I can do the gpt commands that you would use example below: da0 at twa0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 100.000MB/s transfers da0: 762918MB (1562456064 512 byte sectors: 255H 63S/T 97258C) lets say you used this sequence of commands to get started: AMD64# gpt create da0 AMD64# gpt add -i 1 -s 100000000 da0 da0p1 added AMD64# gpt add -i 2 -s 100000000 da0 da0p2 added AMD64# gpt add -i 3 -s 1000000000 da0 da0p3 added AMD64# gpt show da0 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 100000000 1 GPT part - FreeBSD UFS/UFS2 100000034 100000000 2 GPT part - FreeBSD UFS/UFS2 200000034 1000000000 3 GPT part - FreeBSD UFS/UFS2 1200000034 362455997 1562456031 32 Sec GPT table 1562456063 1 Sec GPT header again, I don't have time free to expand the array, so I initially capped the size of p3 to simulate AMD64# newfs /dev/da0p1 /dev/da0p1: 48828.1MB (100000000 sectors) block size 16384, fragment size 2048 using 266 cylinder groups of 183.72MB, 11758 blks, 23552 inodes. AMD64# newfs /dev/da0p2 /dev/da0p2: 48828.1MB (100000000 sectors) block size 16384, fragment size 2048 using 266 cylinder groups of 183.72MB, 11758 blks, 23552 inodes. AMD64# newfs /dev/da0p3 /dev/da0p3: 488281.2MB (1000000000 sectors) block size 16384, fragment size 2048 using 2658 cylinder groups of 183.72MB, 11758 blks, 23552 inodes. super-block backups (for fsck -b #) at: AMD64# mkdir /1 /2 /3 AMD64# mount /dev/da0p1 /1 AMD64# mount /dev/da0p2 /2 AMD64# mount /dev/da0p3 /3 AMD64# df -h /1 /2 /3 Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 46G 4.0K 42G 0% /1 /dev/da0p2 46G 4.0K 42G 0% /2 /dev/da0p3 462G 4.0K 425G 0% /3 AMD64# cp /COPYRIGHT /1 AMD64# cp /COPYRIGHT /2 AMD64# cp /COPYRIGHT /3 AMD64# md5 /1/COPYRIGHT /2/COPYRIGHT /3/COPYRIGHT MD5 (/1/COPYRIGHT) = 0b9d198f2b3abf7587682d7291dbcb8b MD5 (/2/COPYRIGHT) = 0b9d198f2b3abf7587682d7291dbcb8b MD5 (/3/COPYRIGHT) = 0b9d198f2b3abf7587682d7291dbcb8b AMD64# umount /1 AMD64# umount /2 AMD64# umount /3 (array instantly expanded here) AMD64# gpt destroy da0 AMD64# gpt create da0 AMD64# gpt add -i 1 -s 100000000 da0 da0p1 added AMD64# gpt add -i 2 -s 100000000 da0 da0p2 added AMD64# gpt add -i 3 da0 da0p3 added AMD64# growfs /dev/da0p3 We strongly recommend you to make a backup before growing the Filesystem Did you backup your data (Yes/No) ? Yes new file systemsize is: 340613999 frags Warning: 33020 sector(s) cannot be allocated. growfs: 665245.6MB (1362422976 sectors) block size 16384, fragment size 2048 using 3621 cylinder groups of 183.72MB, 11758 blks, 23552 inodes. AMD64# mount /dev/da0p1 /1 AMD64# mount /dev/da0p2 /2 AMD64# mount /dev/da0p3 /3 AMD64# df -h /1 /2 /3 Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 46G 12K 42G 0% /1 /dev/da0p2 46G 12K 42G 0% /2 /dev/da0p3 629G 12K 579G 0% /3 AMD64# md5 /1/COPYRIGHT /2/COPYRIGHT /3/COPYRIGHT MD5 (/1/COPYRIGHT) = 0b9d198f2b3abf7587682d7291dbcb8b MD5 (/2/COPYRIGHT) = 0b9d198f2b3abf7587682d7291dbcb8b MD5 (/3/COPYRIGHT) = 0b9d198f2b3abf7587682d7291dbcb8b growfs scares me more than gpt destroy :) hope this helps! From owner-freebsd-fs@FreeBSD.ORG Thu May 24 17:37:46 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1118D16A41F for ; Thu, 24 May 2007 17:37:46 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.236]) by mx1.freebsd.org (Postfix) with ESMTP id ABA7913C44C for ; Thu, 24 May 2007 17:37:45 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: by qb-out-0506.google.com with SMTP id b14so439574qbc for ; Thu, 24 May 2007 10:37:44 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=g/s+jzFTPuiAsx16/MTNgV7I52ABn/xOCc2K1HWe/ViNMDPj+m/dTVb0x55AeyC2xieLwXWavCOdGJHiikvQCZo2Z38P6dm10g3maci5qjYolJMEmjfEwXZd111nZxAHjHpCM/wXh2LsWrMLqeUa+GpKyFmml6mDoQP7037I3yI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=AO9c3t/L2nyf5cZwVMc3rcIqGdmyxNtSN115H0uAuWrc4QqVe/RMuEqTCu4n/BpCUxEk0GCRmuCeVXNWGTlrOp+GASr+N3/aduxEPuXg6ZTfxWTaV0d31uTUQbPkBfnWMZPU3kCXWnlZ+ezGqB7kbJBXvr0neIrgTfd7l7uIlCc= Received: by 10.100.173.19 with SMTP id v19mr1846488ane.1180028264440; Thu, 24 May 2007 10:37:44 -0700 (PDT) Received: by 10.100.8.19 with HTTP; Thu, 24 May 2007 10:37:44 -0700 (PDT) Message-ID: <99c92b5f0705241037p2d84cb4dp2f19c81795b4f6e6@mail.gmail.com> Date: Thu, 24 May 2007 19:37:44 +0200 From: "Richard Noorlandt" To: freebsd-fs@freebsd.org In-Reply-To: <4c948f810705240924j17788423xde7c2cbfe3cfc036@mail.gmail.com> MIME-Version: 1.0 References: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> <82231.51840.qm@web30307.mail.mud.yahoo.com> <99c92b5f0705240855n4fb4c4d8xd5dbee26bdb52222@mail.gmail.com> <4c948f810705240924j17788423xde7c2cbfe3cfc036@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 17:37:46 -0000 2007/5/24, JH : > > On 5/24/07, Richard Noorlandt wrote: > > > > Will it be possible to create the tables with the current GPT tool, and > > later grow them safely with the new tool when it's available? > > > > It sounds like you're at the newfs stage this week, so it's the perfect > opportunity for testing. Actually I already have been doing some tests with array growth. That's how I found out that I was in trouble.... "Trust, but verify." > > Advice heard on the list is fine, but you really want to see the growfs > operation happen safely on your setup. Make the filesystem, fill it to > 90% full with a few big and little dummy files, then follow the modification > advice, create new files so you're back at 90% full, and verify that md5's > of the old files are still intact. The two professions where we find the > most time spent on rehearsals are acting and system administration. I totally agree with you here. Ideas from the mailinglist are very valuable, but I first want to test things myself. My data is too valuable for me to just do something and cross my fingers. Anyway, I guess I'll try the delete and recreate strategy on GPT when I have time, and see what happens. But I'm afraid it will destroy the data, so other/more suggestions are still welcome. Best regards, Richard From owner-freebsd-fs@FreeBSD.ORG Thu May 24 21:22:23 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2725416A421 for ; Thu, 24 May 2007 21:22:23 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.232]) by mx1.freebsd.org (Postfix) with ESMTP id BE3D813C46E for ; Thu, 24 May 2007 21:22:22 +0000 (UTC) (envelope-from lists.freebsd@gmail.com) Received: by qb-out-0506.google.com with SMTP id b14so567473qbc for ; Thu, 24 May 2007 14:22:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=lyyuvdZPz9CkqA5fSKgAh2+SPyvLjV4fdI7waH47Oc/0jmC4EDem1YpTc/cWjOtWsAZ76vACICEpibBqObmwMBVAn06dea1h2DDKW+0NZ9Jna4OnCFuv3/s72N++0DXPeGV37iI+vg2f3JJRzYd1NTxUmY0KY9N3cR4NTIQFTkY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=qJQ8IBEx+VeeY9yQPzDH6JSvqnqBk9GeOTosnDvB1VwSKYaHc2YB98rH/dk4sWOxydWx77swB+GZ6mTiiEFVAdAaVBR+jZ+/H+ZwNFEzYHoySiKRdtacrFiEr+5/piu4pHKWgzf6KPQv143WdAQbANPnLXXqKsbD9pDDcEE3+zE= Received: by 10.100.3.20 with SMTP id 20mr2188787anc.1180041741062; Thu, 24 May 2007 14:22:21 -0700 (PDT) Received: by 10.100.8.19 with HTTP; Thu, 24 May 2007 14:22:21 -0700 (PDT) Message-ID: <99c92b5f0705241422g7372fed6s606227cd02e6ab63@mail.gmail.com> Date: Thu, 24 May 2007 23:22:21 +0200 From: "Richard Noorlandt" To: freebsd-fs@freebsd.org In-Reply-To: <4655CCBB.2020403@tychl.net> MIME-Version: 1.0 References: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> <4655CCBB.2020403@tychl.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 21:22:23 -0000 2007/5/24, Nick Gustas : > > You should be able to simply finish the online expansion of the array, > recreate your GPT partitions and run growfs. I recently did a OCE on an > array with a single GPT partition containing ZFS on a 3ware controller > and it worked fine. destroying the GPT partitioning doesn't hurt any > data as long as you put it back the same way. > > order of operations was: > > OCE finished, one drive added to array. > zpool export threeware > gpt destroy da0 > gpt create da0 > gpt add da0 > zpool import threeware > > everything was fine, all the data was there, just a bigger partition. > > > I see no reason this wouldn't work with UFS over 2TB assuming you have > some of the growfs patches that have been posted in the last few weeks. I have been on this list for only a few days now, so I don't know anything about these growfs patches. But I'll guess I can find them somewhere. Unless they're scattered all over the place ;-) I run 6.2-RELEASE by the way. What's the easiest way to get the right growfs version with the necessary patches? growfs scares me more than gpt destroy :) > > hope this helps! Meddling with a FS that has data on it is always scary, no matter what tools you use. But your detailed description helps a lot. So once I updated growfs I'll try this approach myself. Best regards, Richard From owner-freebsd-fs@FreeBSD.ORG Thu May 24 21:31:41 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A3EA16A421 for ; Thu, 24 May 2007 21:31:41 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30309.mail.mud.yahoo.com (web30309.mail.mud.yahoo.com [209.191.69.71]) by mx1.freebsd.org (Postfix) with SMTP id CB6CB13C4B0 for ; Thu, 24 May 2007 21:31:40 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 58290 invoked by uid 60001); 24 May 2007 21:31:40 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=cNIvisK9bdkvBTVvYdYQxhpgWAYK7imoNLHjJ06hkiNiEniyz32Py63T99wIzO7nLHI+GqerVu+Dlx6P0JmH+9wRYKhWnBbuYd20tVlMvVBfZbZPrZ7vnyyM/XDNSvwDjL0aGv7GTgk8+W/cLUB58xihyIFGRBRJ1BkgZv5AmG4=; X-YMail-OSG: _iT_w_0VM1n0Ll2uJRTYKOvDTK9gGyHaE70xkUfsTRkuhCXmXCvg9sG_.FRGIRT3wDP7oAFU3CUjZRosXprNbzlyW39m.fwbcNUY0KFm5uiuj7saMni9B_UBUh5CaQ-- Received: from [213.54.162.102] by web30309.mail.mud.yahoo.com via HTTP; Thu, 24 May 2007 14:31:39 PDT Date: Thu, 24 May 2007 14:31:39 -0700 (PDT) From: Arne "Wörner" To: Richard Noorlandt , freebsd-fs@freebsd.org In-Reply-To: <99c92b5f0705241422g7372fed6s606227cd02e6ab63@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <145992.57985.qm@web30309.mail.mud.yahoo.com> Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 21:31:41 -0000 --- Richard Noorlandt wrote: > I have been on this list for only a few days now, so I don't know anything > about these growfs patches. But I'll guess I can find them somewhere. Unless > they're scattered all over the place ;-) > > I run 6.2-RELEASE by the way. What's the easiest way to get the right growfs > version with the necessary patches? > These two patches r enough: http://docs.freebsd.org/cgi/mid.cgi?26D278C6-C000-48D0-AED4-0E6F703706FA http://docs.freebsd.org/cgi/mid.cgi?125170.23599.qm -Arne ____________________________________________________________________________________Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 From owner-freebsd-fs@FreeBSD.ORG Thu May 24 23:57:10 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 739B516A41F for ; Thu, 24 May 2007 23:57:10 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.152]) by mx1.freebsd.org (Postfix) with ESMTP id 590DD13C484 for ; Thu, 24 May 2007 23:57:10 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from masq.tychl.net (tychl.no-ip.org[67.174.137.176]) by comcast.net (rwcrmhc12) with ESMTP id <20070524235709m1200biople>; Thu, 24 May 2007 23:57:09 +0000 Received: from localhost (localhost [127.0.0.1]) by masq.tychl.net (Postfix) with ESMTP id 99D621CB4B; Thu, 24 May 2007 19:56:58 -0400 (EDT) X-Virus-Scanned: amavisd-new at tychl.net Received: from masq.tychl.net ([127.0.0.1]) by localhost (masq.tychl.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id VlknO10ZSpqJ; Thu, 24 May 2007 19:56:54 -0400 (EDT) Received: from [192.168.0.11] (unknown [192.168.0.11]) by masq.tychl.net (Postfix) with ESMTP id 168E51CB4A; Thu, 24 May 2007 19:56:54 -0400 (EDT) Message-ID: <4656264D.8010505@tychl.net> Date: Thu, 24 May 2007 19:57:01 -0400 From: Nick Gustas User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: Richard Noorlandt , freebsd-fs@freebsd.org References: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> <4655CCBB.2020403@tychl.net> <99c92b5f0705241422g7372fed6s606227cd02e6ab63@mail.gmail.com> In-Reply-To: <99c92b5f0705241422g7372fed6s606227cd02e6ab63@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 May 2007 23:57:10 -0000 Richard Noorlandt wrote: > I have been on this list for only a few days now, so I don't know > anything > about these growfs patches. But I'll guess I can find them somewhere. > Unless > they're scattered all over the place ;-) > > I run 6.2-RELEASE by the way. What's the easiest way to get the right > growfs > version with the necessary patches? > > > Meddling with a FS that has data on it is always scary, no matter what > tools > you use. But your detailed description helps a lot. So once I updated > growfs > I'll try this approach myself. > > Best regards, > > Richard I did a diff between the growfs.c from a 6.2-STABLE machine and what I have now from list patches and GCC error fixing. *WARNING* it appears to work, and compiles clean, but doesn't actually make a correct filesystem! I don't know enough C to get past this, though I suspect it's close and some study might get me there. http://masq.tychl.net/growfs.patch I don't have more than 2TB of free space handy at the moment, so I used a md device, you absolutely need to try this on a _TEST_ machine with a copy of real disk/data first. AMD64# mdconfig -a -t swap -s 3T md0 AMD64# gpt create md0 AMD64# gpt show md0 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6442450877 6442450911 32 Sec GPT table 6442450943 1 Sec GPT header AMD64# gpt add -s 4000000000 md0 md0p1 added AMD64# gpt show md0 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 4000000000 1 GPT part - FreeBSD UFS/UFS2 4000000034 2442450877 6442450911 32 Sec GPT table 6442450943 1 Sec GPT header about 1.8T AMD64# newfs -b 65536 -f 8192 /dev/md0p1 /dev/md0p1: 1953125.0MB (4000000000 sectors) block size 65536, fragment size 8192 using 658 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. super-block backups (for fsck -b #) at: 256, 6080896, 12161536, 18242176, 24322816, 30403456, 36484096, 42564736, 48645376, 54726016, 60806656, 66887296, 72967936, 79048576, 85129216, 91209856, 97290496, 103371136, 109451776, 115532416, 121613056, 127693696, 133774336, 139854976, *snip* 3940254976, 3946335616, 3952416256, 3958496896, 3964577536, 3970658176, 3976738816, 3982819456, 3988900096, 3994980736 AMD64# mount /dev/md0p1 /mnt AMD64# df -h /mnt Filesystem Size Used Avail Capacity Mounted on /dev/md0p1 1.8T 16K 1.7T 0% /mnt AMD64# umount /dev/md0p1 AMD64# gpt remove -i 1 md0 md0p1 removed AMD64# gpt add md0 md0p1 added AMD64# gpt show md0 start size index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 34 6442450877 1 GPT part - FreeBSD UFS/UFS2 6442450911 32 Sec GPT table 6442450943 1 Sec GPT header AMD64# ./growfs /dev/md0p1 We strongly recommend you to make a backup before growing the Filesystem Did you backup your data (Yes/No) ? Yes new file systemsize is: 402653179 frags Warning: 3053104 sector(s) cannot be allocated. growfs: 3144237.2MB (6439397760 sectors) block size 65536, fragment size 8192 using 1059 cylinder groups of 2969.06MB, 47505 blks, 95232 inodes. super-block backups (for fsck -b #) at: 4001061376, 4007142016, 4013222656, 4019303296, 4025383936, 4031464576, 4037545216, 4043625856, 4049706496, 4055787136, 4061867776, 4067948416, 4074029056, 4080109696, 4086190336, 4092270976, 4098351616, 4104432256, 4110512896, 4116593536, 4122674176, 4128754816, 4134835456, 4140916096, 4146996736, 4153077376, 4159158016, 4165238656, 4171319296, 4177399936, 4183480576, 4189561216, 4195641856, 4201722496, 4207803136, 4213883776, 4219964416, 4226045056, 4232125696, 4238206336, 4244286976, 4250367616, 4256448256, 4262528896, 4268609536, 4274690176, 4280770816, 4286851456, 4292932096, 4299012736, 4305093376, 4311174016, 4317254656, 4323335296, 4329415936, 4335496576, 4341577216, 4347657856, 4353738496, 4359819136, 4365899776, 4371980416, 4378061056, 4384141696, 4390222336, 4396302976, 4402383616, 4408464256, 4414544896, 4420625536, 4426706176, 4432786816, 4438867456, 4444948096, 4451028736, 4457109376, 4463190016, 4469270656, 4475351296, 4481431936, 4487512576, 4493593216, 4499673856, 4505754496, 4511835136, 4517915776, 4523996416, 4530077056, 4536157696, 4542238336, 4548318976, 4554399616, 4560480256, 4566560896, 4572641536, 4578722176, 4584802816, 4590883456, 4596964096, 4603044736, 4609125376, 4615206016, 4621286656, 4627367296, 4633447936, 4639528576, 4645609216, 4651689856, 4657770496, 4663851136, 4669931776, 4676012416, 4682093056, 4688173696, 4694254336, 4700334976, 4706415616, 4712496256, 4718576896, 4724657536, 4730738176, 4736818816, 4742899456, 4748980096, 4755060736, 4761141376, 4767222016, 4773302656, 4779383296, 4785463936, 4791544576, 4797625216, 4803705856, 4809786496, 4815867136, 4821947776, 4828028416, 4834109056, 4840189696, 4846270336, 4852350976, 4858431616, 4864512256, 4870592896, 4876673536, 4882754176, 4888834816, 4894915456, 4900996096, 4907076736, 4913157376, 4919238016, 4925318656, 4931399296, 4937479936, 4943560576, 4949641216, 4955721856, 4961802496, 4967883136, 4973963776, 4980044416, 4986125056, 4992205696, 4998286336, 5004366976, 5010447616, 5016528256, 5022608896, 5028689536, 5034770176, 5040850816, 5046931456, 5053012096, 5059092736, 5065173376, 5071254016, 5077334656, 5083415296, 5089495936, 5095576576, 5101657216, 5107737856, 5113818496, 5119899136, 5125979776, 5132060416, 5138141056, 5144221696, 5150302336, 5156382976, 5162463616, 5168544256, 5174624896, 5180705536, 5186786176, 5192866816, 5198947456, 5205028096, 5211108736, 5217189376, 5223270016, 5229350656, 5235431296, 5241511936, 5247592576, 5253673216, 5259753856, 5265834496, 5271915136, 5277995776, 5284076416, 5290157056, 5296237696, 5302318336, 5308398976, 5314479616, 5320560256, 5326640896, 5332721536, 5338802176, 5344882816, 5350963456, 5357044096, 5363124736, 5369205376, 5375286016, 5381366656, 5387447296, 5393527936, 5399608576, 5405689216, 5411769856, 5417850496, 5423931136, 5430011776, 5436092416, 5442173056, 5448253696, 5454334336, 5460414976, 5466495616, 5472576256, 5478656896, 5484737536, 5490818176, 5496898816, 5502979456, 5509060096, 5515140736, 5521221376, 5527302016, 5533382656, 5539463296, 5545543936, 5551624576, 5557705216, 5563785856, 5569866496, 5575947136, 5582027776, 5588108416, 5594189056, 5600269696, 5606350336, 5612430976, 5618511616, 5624592256, 5630672896, 5636753536, 5642834176, 5648914816, 5654995456, 5661076096, 5667156736, 5673237376, 5679318016, 5685398656, 5691479296, 5697559936, 5703640576, 5709721216, 5715801856, 5721882496, 5727963136, 5734043776, 5740124416, 5746205056, 5752285696, 5758366336, 5764446976, 5770527616, 5776608256, 5782688896, 5788769536, 5794850176, 5800930816, 5807011456, 5813092096, 5819172736, 5825253376, 5831334016, 5837414656, 5843495296, 5849575936, 5855656576, 5861737216, 5867817856, 5873898496, 5879979136, 5886059776, 5892140416, 5898221056, 5904301696, 5910382336, 5916462976, 5922543616, 5928624256, 5934704896, 5940785536, 5946866176, 5952946816, 5959027456, 5965108096, 5971188736, 5977269376, 5983350016, 5989430656, 5995511296, 6001591936, 6007672576, 6013753216, 6019833856, 6025914496, 6031995136, 6038075776, 6044156416, 6050237056, 6056317696, 6062398336, 6068478976, 6074559616, 6080640256, 6086720896, 6092801536, 6098882176, 6104962816, 6111043456, 6117124096, 6123204736, 6129285376, 6135366016, 6141446656, 6147527296, 6153607936, 6159688576, 6165769216, 6171849856, 6177930496, 6184011136, 6190091776, 6196172416, 6202253056, 6208333696, 6214414336, 6220494976, 6226575616, 6232656256, 6238736896, 6244817536, 6250898176, 6256978816, 6263059456, 6269140096, 6275220736, 6281301376, 6287382016, 6293462656, 6299543296, 6305623936, 6311704576, 6317785216, 6323865856, 6329946496, 6336027136, 6342107776, 6348188416, 6354269056, 6360349696, 6366430336, 6372510976, 6378591616, 6384672256, 6390752896, 6396833536, 6402914176, 6408994816, 6415075456, 6421156096, 6427236736, 6433317376 AMD64# mount /dev/md0p1 /mnt AMD64# df -h /mnt Filesystem Size Used Avail Capacity Mounted on /dev/md0p1 3.0T 16K 2.7T 0% /mnt proper output, looks like it works, but, run fsck... AMD64# umount /dev/md0p1 AMD64# fsck_ufs -y /dev/md0p1 ** /dev/md0p1 ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes 322311525761044 BAD I=62663420 77308202712 BAD I=62663420 322414604976148 BAD I=62663420 77308202720 BAD I=62663420 322517684191252 BAD I=62663420 77308202728 BAD I=62663420 322620763406356 BAD I=62663420 77308202736 BAD I=62663420 322723842621460 BAD I=62663420 17178660600 BAD I=62663420 77308202704 BAD I=62663420 EXCESSIVE BAD BLKS I=62663420 CONTINUE? yes 322311525761044 BAD I=62866824 77308202712 BAD I=62866824 322414604976148 BAD I=62866824 77308202720 BAD I=62866824 322517684191252 BAD I=62866824 77308202728 BAD I=62866824 322620763406356 BAD I=62866824 77308202736 BAD I=62866824 322723842621460 BAD I=62866824 17178660600 BAD I=62866824 77308202704 BAD I=62866824 EXCESSIVE BAD BLKS I=62866824 CONTINUE? yes etc etc etc etc etc Hopefully someone can go from here and fix what I'm missing. From owner-freebsd-fs@FreeBSD.ORG Fri May 25 00:44:52 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E165116A469 for ; Fri, 25 May 2007 00:44:52 +0000 (UTC) (envelope-from janm@transactionware.com) Received: from mail.transactionware.com (mail.transactionware.com [203.14.245.7]) by mx1.freebsd.org (Postfix) with SMTP id 464EE13C483 for ; Fri, 25 May 2007 00:44:52 +0000 (UTC) (envelope-from janm@transactionware.com) Received: (qmail 69371 invoked from network); 25 May 2007 00:18:30 -0000 Received: from midgard.transactionware.com (192.168.1.55) by dm.transactionware.com with SMTP; 25 May 2007 00:18:30 -0000 Received: (qmail 91291 invoked by uid 907); 25 May 2007 00:18:09 -0000 Received: from [192.168.1.51] (HELO janmxp) (192.168.1.51) by midgard.transactionware.com (qpsmtpd/0.32) with ESMTP; Fri, 25 May 2007 10:18:09 +1000 From: "Jan Mikkelsen" To: "'Richard Noorlandt'" , References: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> In-Reply-To: <99c92b5f0705240730o146c1bb4x326591687e445cd@mail.gmail.com> Date: Fri, 25 May 2007 10:18:09 +1000 Organization: Transactionware Message-ID: <000701c79e62$2c9c4190$85d4c4b0$@com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AceeFJuTTmzGjD7bQteNMkKjjGFHBwATGrMg Content-Language: en-au Cc: Subject: RE: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 00:44:53 -0000 Richard Noorlandt wrote: > I'm currently configuring a large fileserver (Dual Opteron and > an Areca 1160 > for hardware RAID), and I'm running into some partitioning > problems. > Currently, I have 6 500 GB drives to put in a main RAID-6 > array, giving me 2 > TB of usable storage. Now, I want this 2 TB to be partitioned > in several > separate partitions of various sizes. The last partition will > be 1 TB, and > will be the most important partition on the array. > > Now my problem is that this 1 TB partition must be able to > grow beyond 2 TB > at a later stage (after adding extra HD's). If I understand > correctly, it is > not possible to grow a UFS partition beyond 2 TB when the > drive is > partitioned with fdisk. One should use GPT instead. However, > it appears that > GPT currently has no way to resize partitions, giving me no > possibility to > enlarge the 1TB partition and run growfs. > > Does anyone have a suggestion? Or am I overlooking something? > I can hardly > imagine that what I want is very rare, so I think there must > be some > solution. You can use the Areca controller to create separate devices/LUNs, and then ignore fdisk/gpt/labels altogether for the large filesystem you want to grow, and just stick the filesystem directly on /dev/da1, or whatever it ends up being. As a bonus, you don't have to do all the calculations to figure out where the partitions should start. See: http://lists.freebsd.org/pipermail/freebsd-fs/2006-October/002312.h tml Regards, Jan Mikkelsen. From owner-freebsd-fs@FreeBSD.ORG Fri May 25 04:44:29 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 680) id 8A80B16A468; Fri, 25 May 2007 04:44:29 +0000 (UTC) Date: Fri, 25 May 2007 04:44:29 +0000 From: Darren Reed To: Kip Macy Message-ID: <20070525044429.GA56657@hub.freebsd.org> References: <4651BD6F.5050301@unsane.co.uk> <20070522083112.GA5136@hub.freebsd.org> <4652B15D.5060505@unsane.co.uk> <20070523085532.GA27542@hub.freebsd.org> <20070523093231.GA29797@xor.obsecurity.org> <20070523181903.GA60674@xor.obsecurity.org> <20070524100125.GB52149@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Ivan Voras , Kris Kennaway Subject: Re: ZFS committed to the FreeBSD base. X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 04:44:29 -0000 On Thu, May 24, 2007 at 09:40:35AM -0700, Kip Macy wrote: > >While I don't know of any hardware that is *only* 32bit and > >sold by Sun, Solaris 10 runs on 32bit PCs and will do for the > >foreseeable future as I'm sure a good part of the opensolaris > >community would be upset if it were to be abandoned. > > Abandoned is the wrong word, but supported is definitely not the same > as new development being targeted at. I disagree with that completely. You're obviously unaware of a lot of development that is going on inside [Open]Solaris on the driver front. But that aside, 32bit x86 is aging rapidly and within the next few years will be just as legacy as your 486 is and in maybe 5-10 the same as 386. So I wouldn't say that they have or are abandoned 32bit x86, rather that there is just no future in it, so effort is scaled appropriately. Even in open source this rings true - NetBSD is getting close to removing some of the more venerable platforms, not because they're abandoning them but because for one reason or another it no longer makes sense. Darren From owner-freebsd-fs@FreeBSD.ORG Fri May 25 04:50:59 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9F99616A421 for ; Fri, 25 May 2007 04:50:59 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30301.mail.mud.yahoo.com (web30301.mail.mud.yahoo.com [209.191.69.63]) by mx1.freebsd.org (Postfix) with SMTP id 7763F13C487 for ; Fri, 25 May 2007 04:50:59 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 7897 invoked by uid 60001); 25 May 2007 04:50:58 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=xIu/dlemaS1eppUQW8bj6VVAs0wadecWORo6P7/zsAFDw4LfSa+8J8i88pkZ3MbPikHn8Uv7C4YT+EJ98D3cUCvIojMVNXSfCyX2pCzLMxBtEBizClsp819/eXUC1VYPR0cWo6QYQRoFLor870Ii3eS3t9/mNJq8Akok6Y8COzg=; X-YMail-OSG: xVrb..8VM1nIVXFDEgYfqcTLl5S5G15jhS3IVKt66NczWxRl3efK7fmQ_6d3qjqYWO1PBrHtheCs1ScIuYhUGOZ9rbu6WrQQezpdPAwHHLCBv47oXG0- Received: from [85.212.48.7] by web30301.mail.mud.yahoo.com via HTTP; Thu, 24 May 2007 21:50:58 PDT Date: Thu, 24 May 2007 21:50:58 -0700 (PDT) From: Arne "Wörner" To: Nick Gustas , Richard Noorlandt , freebsd-fs@freebsd.org In-Reply-To: <4656264D.8010505@tychl.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <888834.6894.qm@web30301.mail.mud.yahoo.com> Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 04:50:59 -0000 --- Nick Gustas wrote: > Richard Noorlandt wrote: > > I have been on this list for only a few days now, so I don't know > > anything > > about these growfs patches. But I'll guess I can find them somewhere. > > Unless > > they're scattered all over the place ;-) > > > > I run 6.2-RELEASE by the way. What's the easiest way to get the right > > growfs > > version with the necessary patches? > > > > > > Meddling with a FS that has data on it is always scary, no matter what > > tools > > you use. But your detailed description helps a lot. So once I updated > > growfs > > I'll try this approach myself. > > > > Best regards, > > > > Richard > > > > I did a diff between the growfs.c from a 6.2-STABLE machine and what I > have now from list patches and GCC error fixing. *WARNING* it appears > to work, and compiles clean, but doesn't actually make a correct > filesystem! I don't know enough C to get past this, though I suspect > it's close and some study might get me there. > > http://masq.tychl.net/growfs.patch > Where have u found this: @@ -425,8 +425,8 @@ acg.cg_nextfreeoff = acg.cg_freeoff + howmany(sblock.fs_fpg, CHAR_BIT); if (sblock.fs_contigsumsize > 0) { acg.cg_clustersumoff = - roundup(acg.cg_nextfreeoff, sizeof(u_int32_t)); - acg.cg_clustersumoff -= sizeof(u_int32_t); + roundup(acg.cg_nextfreeoff, sizeof(u_int64_t)); + acg.cg_clustersumoff -= sizeof(u_int64_t); acg.cg_clusteroff = acg.cg_clustersumoff + (sblock.fs_contigsumsize + 1) * sizeof(u_int32_t); acg.cg_nextfreeoff = acg.cg_clusteroff + ??? That looks wrong... And this looks unnecessary, because there will never be a struct, that has a size of more than 2^31: :-) @@ -2109,7 +2108,7 @@ (osblock.fs_magic == FS_UFS2_MAGIC && osblock.fs_sblockloc == sblock_try[i])) && osblock.fs_bsize <= MAXBSIZE && - osblock.fs_bsize >= (int32_t) sizeof(struct fs)) + osblock.fs_bsize >= (int64_t) sizeof(struct fs)) break; } if (sblock_try[i] == -1) { I softly recommend, that u correct the patch accordingly (both changes r not necessary or even wrong) asap, so that nobody can try that... > ** /dev/md0p1 > ** Last Mounted on /mnt > ** Phase 1 - Check Blocks and Sizes > 322311525761044 BAD I=62663420 > 77308202712 BAD I=62663420 > 322414604976148 BAD I=62663420 > 77308202720 BAD I=62663420 > 322517684191252 BAD I=62663420 > 77308202728 BAD I=62663420 > 322620763406356 BAD I=62663420 > 77308202736 BAD I=62663420 > 322723842621460 BAD I=62663420 > 17178660600 BAD I=62663420 > 77308202704 BAD I=62663420 > EXCESSIVE BAD BLKS I=62663420 > CONTINUE? yes > Hmm... That might be a "normal" bug in growfs... Did u try the unpatched version with a smaller fs? -Arne ____________________________________________________________________________________Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433 From owner-freebsd-fs@FreeBSD.ORG Fri May 25 05:07:42 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 33D6816A400 for ; Fri, 25 May 2007 05:07:42 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30309.mail.mud.yahoo.com (web30309.mail.mud.yahoo.com [209.191.69.71]) by mx1.freebsd.org (Postfix) with SMTP id 00BEB13C4AD for ; Fri, 25 May 2007 05:07:39 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 96260 invoked by uid 60001); 25 May 2007 05:07:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=vIGoCGwxiGFpu7k5Y4NzR20jnFL/wDcExUrAOIKlvxkhuYG7LpWMWqFU2fxKxfuGr0698oamu1a08f9Jr58GfS5zClCVW+dAAncdUCwsnJX8YDK59XamCyW677FupQSW9GVzGtY2xw4jh+dBTjRoRY0h76r9l98askJ+UZVKJrw=; X-YMail-OSG: 7zhfg3wVM1k7t9WNwm1nvYcQw8BrNOuz21QGLj6C2LzTwY00RHFlIAcAwZDTOYJud7mw3NcB1dfi2MN0CVT18SdEy0nksoj4gY02VFWF4JRn02QlMjs- Received: from [85.212.48.7] by web30309.mail.mud.yahoo.com via HTTP; Thu, 24 May 2007 22:07:39 PDT Date: Thu, 24 May 2007 22:07:39 -0700 (PDT) From: Arne "Wörner" To: Nick Gustas , Richard Noorlandt , freebsd-fs@freebsd.org In-Reply-To: <4656264D.8010505@tychl.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <452653.95653.qm@web30309.mail.mud.yahoo.com> Cc: Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 05:07:42 -0000 --- Nick Gustas wrote: > Richard Noorlandt wrote: > > I have been on this list for only a few days now, so I don't know > > anything > > about these growfs patches. But I'll guess I can find them somewhere. > > Unless > > they're scattered all over the place ;-) > > > > I run 6.2-RELEASE by the way. What's the easiest way to get the right > > growfs > > version with the necessary patches? > > > > > > Meddling with a FS that has data on it is always scary, no matter what > > tools > > you use. But your detailed description helps a lot. So once I updated > > growfs > > I'll try this approach myself. > > > > Best regards, > > > > Richard > > > > I did a diff between the growfs.c from a 6.2-STABLE machine and what I > have now from list patches and GCC error fixing. *WARNING* it appears > to work, and compiles clean, but doesn't actually make a correct > filesystem! I don't know enough C to get past this, though I suspect > it's close and some study might get me there. > > http://masq.tychl.net/growfs.patch > This look wrong, too: @@ -417,7 +417,7 @@ acg.cg_initediblk = 0; acg.cg_old_btotoff = start; acg.cg_old_boff = acg.cg_old_btotoff + - sblock.fs_old_cpg * sizeof(int32_t); + sblock.fs_old_cpg * sizeof(int64_t); acg.cg_iusedoff = acg.cg_old_boff + sblock.fs_old_cpg * sizeof(u_int16_t); } Where have u found that? -Arne ____________________________________________________________________________________You snooze, you lose. Get messages ASAP with AutoCheck in the all-new Yahoo! Mail Beta. http://advision.webevents.yahoo.com/mailbeta/newmail_html.html From owner-freebsd-fs@FreeBSD.ORG Fri May 25 06:59:15 2007 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A2D2F16A46B for ; Fri, 25 May 2007 06:59:15 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from mailout01.verio.de (mailout01.verio.de [213.198.86.6]) by mx1.freebsd.org (Postfix) with ESMTP id 675C013C46C for ; Fri, 25 May 2007 06:59:15 +0000 (UTC) (envelope-from garyj@jennejohn.org) Received: from localhost (localhost [127.0.0.1]) by mailout01.verio.de (MAiL) with ESMTP id D4B723E8C8 for ; Fri, 25 May 2007 08:59:24 +0200 (CEST) Received: from mmm808.verio.de (mmm808.verio.de [213.198.55.120]) by mailout01.verio.de (MAiL) with ESMTP id 5C45A3E8F5 for ; Fri, 25 May 2007 08:59:23 +0200 (CEST) Received: (qmail 33510 invoked from network); 25 May 2007 06:59:12 -0000 Received: from unknown (HELO peedub.jennejohn.org) (89.59.13.187) by with SMTP; 25 May 2007 06:59:12 -0000 Received: from peedub.jennejohn.org (localhost [127.0.0.1]) by peedub.jennejohn.org (8.14.1/8.14.1) with SMTP id l4P6x7W6001820 for ; Fri, 25 May 2007 08:59:10 +0200 (CEST) (envelope-from garyj@jennejohn.org) Date: Fri, 25 May 2007 08:59:07 +0200 From: Gary Jennejohn To: freebsd-fs@FreeBSD.org Message-Id: <20070525085907.2e3a89c3.garyj@jennejohn.org> Organization: DENX Softwre Engineering GmbH X-Mailer: Sylpheed 2.4.0 (GTK+ 2.10.12; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Strange ZFS behavior after lock up X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 06:59:15 -0000 I was testing the thread lock patch yesterday when the machine locked up an I had to do a hard reset. Now I have to import my ZFS storage pools by hand at every boot. Maybe I don't understand something, but it seems to me that ZFS should automatically pick up my storage pools after I re-import them. Or am I wrong here and need to do something more than just import them? --- Gary Jennejohn / garyjATjennejohnDOTorg gjATfreebsdDOTorg garyjATdenxDOTde From owner-freebsd-fs@FreeBSD.ORG Fri May 25 08:19:02 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49D2616A400 for ; Fri, 25 May 2007 08:19:02 +0000 (UTC) (envelope-from cristi@net.utcluj.ro) Received: from bavaria.utcluj.ro (bavaria.utcluj.ro [193.226.5.35]) by mx1.freebsd.org (Postfix) with ESMTP id 0356613C458 for ; Fri, 25 May 2007 08:19:01 +0000 (UTC) (envelope-from cristi@net.utcluj.ro) Received: from localhost (localhost [127.0.0.1]) by bavaria.utcluj.ro (Postfix) with ESMTP id 528B650856; Fri, 25 May 2007 11:19:00 +0300 (EEST) X-Virus-Scanned: by the daemon playing with your mail on bavaria.utcluj.ro Received: from bavaria.utcluj.ro ([127.0.0.1]) by localhost (bavaria.utcluj.ro [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxKAhWDCXqvC; Fri, 25 May 2007 11:18:37 +0300 (EEST) Received: from [172.20.100.73] (unknown [217.73.161.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by bavaria.utcluj.ro (Postfix) with ESMTP id 7D38750821; Fri, 25 May 2007 11:18:37 +0300 (EEST) Message-ID: <46569BDF.3030700@net.utcluj.ro> Date: Fri, 25 May 2007 11:18:39 +0300 From: Cristian KLEIN Organization: Data Communication Center - Technical University of Cluj-Napoca User-Agent: Thunderbird 1.5.0.10 (X11/20070306) MIME-Version: 1.0 To: Ollivier Robert References: <475187.33232.qm@web63006.mail.re1.yahoo.com> <86r6p9xf2c.fsf@dwp.des.no> <20070522131107.GA73155@keltia.freenix.fr> In-Reply-To: <20070522131107.GA73155@keltia.freenix.fr> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org Subject: Re: VERY frustrated with FreeBSD/UFS stability - please help or comment... X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 08:19:02 -0000 Ollivier Robert wrote: > According to Dag-Erling Smørgrav: >> client2% rsync --archive --delete /vol server:/backup/client2 >> server% for vol in /backup/* ; do mksnap_ffs $vol $vol/.snap/`date` ; done > > My experience with the sysutils/freebsd-snapshot, which enable automatic > snapshot creation (à la NetApp) is that after a few created snapshots, the > whole system just locks up. This was in 6.0-6.1 days, maybe 6.2 has > improved but they seem very fragile :( Nope. They did not. :) I had a server which crashed a few hours after enabling snapshots. Now that I removed them, the system is rock solid again. I have been unable to reproduce the problem (interesting how some problems show up only on production systems), so I was unable to file a PR. IMHO, all these issues should be written in the errata. I can affort not using snapshot, but having an instable system (and an angry boss) is killing me. From owner-freebsd-fs@FreeBSD.ORG Fri May 25 11:42:16 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E9D0B16A469 for ; Fri, 25 May 2007 11:42:16 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.77.83]) by mx1.freebsd.org (Postfix) with ESMTP id AB86713C45D for ; Fri, 25 May 2007 11:42:16 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from masq.tychl.net (tychl.no-ip.org[67.174.137.176]) by comcast.net (sccrmhc13) with ESMTP id <2007052511421501300it724e>; Fri, 25 May 2007 11:42:15 +0000 Received: from localhost (localhost [127.0.0.1]) by masq.tychl.net (Postfix) with ESMTP id 2431B1CB4B; Fri, 25 May 2007 07:42:05 -0400 (EDT) X-Virus-Scanned: amavisd-new at tychl.net Received: from masq.tychl.net ([127.0.0.1]) by localhost (masq.tychl.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id IEQpyZT54YhP; Fri, 25 May 2007 07:42:02 -0400 (EDT) Received: from [127.0.0.1] (unknown [192.168.0.55]) by masq.tychl.net (Postfix) with ESMTP id 80FB01CB4A; Fri, 25 May 2007 07:42:02 -0400 (EDT) Message-ID: <4656CB8C.5040809@tychl.net> Date: Fri, 25 May 2007 07:42:04 -0400 From: Nick Gustas User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: "Arne \"WXrner\"" References: <452653.95653.qm@web30309.mail.mud.yahoo.com> In-Reply-To: <452653.95653.qm@web30309.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 11:42:17 -0000 Arne WXrner wrote: > --- Nick Gustas wrote: > > >> I did a diff between the growfs.c from a 6.2-STABLE machine and what I >> have now from list patches and GCC error fixing. *WARNING* it appears >> to work, and compiles clean, but doesn't actually make a correct >> filesystem! I don't know enough C to get past this, though I suspect >> it's close and some study might get me there. >> >> http://masq.tychl.net/growfs.patch >> >> > This look wrong, too: > @@ -417,7 +417,7 @@ > acg.cg_initediblk = 0; > acg.cg_old_btotoff = start; > acg.cg_old_boff = acg.cg_old_btotoff + > - sblock.fs_old_cpg * sizeof(int32_t); > + sblock.fs_old_cpg * sizeof(int64_t); > acg.cg_iusedoff = acg.cg_old_boff + > sblock.fs_old_cpg * sizeof(u_int16_t); > } > Where have u found that? > > -Arne > > > > ____________________________________________________________________________________You snooze, you lose. Get messages ASAP with AutoCheck > in the all-new Yahoo! Mail Beta. > http://advision.webevents.yahoo.com/mailbeta/newmail_html.html > Well, originally I tried just the patches from the two messages you referred to, and it didn't work, fsck -y would scroll endlessly after the grow, and the output of growfs itself wasn't right. I figured something must still be missing, so I went at it until the compilation warnings went away, and the output looked right. However since I'm not a programmer, or UFS internals guy, I was probably a bit overzealous in my 32/64 bit searching. I figured I'd post what I had done, with a warning, in the hopes someone would correct me. Anyhow, I made the three changes you mentioned, and growfs still compiles clean, and runs with proper display, but running fsck -y on the grown file system scrolls for a long time with tons of errors and eventually bombs out asking me to run it again. running it again doesn't help. I've updated http://masq.tychl.net/growfs.patch with the changes you suggested. Keep in mind I'm no C programmer, but I can follow direction and would love to see growfs 2+TB clean :) From owner-freebsd-fs@FreeBSD.ORG Fri May 25 11:55:06 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2FEFF16A421 for ; Fri, 25 May 2007 11:55:06 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30305.mail.mud.yahoo.com (web30305.mail.mud.yahoo.com [209.191.69.67]) by mx1.freebsd.org (Postfix) with SMTP id CC3AB13C483 for ; Fri, 25 May 2007 11:55:05 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 91218 invoked by uid 60001); 25 May 2007 11:55:05 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=5mdh8Yl6Ki9hrsd1ELVSLYXufTK6cXeJUtykVHtHcROoi755DoZdbf3Nu93xHHRIqHN83zo7y/N8+S9+NSeLKAXEs3Ki69psKmsdCDHWWZnsPa9D7OLQPFEznUXiZHvQOA8aXAfPcu38n69pmKBini5Flpq6Ow3UCPPLwmKvUds=; X-YMail-OSG: BGTdkrAVM1nNB9lMkJPp2djgmGVGJAmdKhlnoKt._7Wl6amit1_6sDh89OgFrnqIDa3W_tOCHUC70al4wHpZrtd_kxBHgEqD1MNN7MtqGCmDz8OLE5Q- Received: from [85.212.48.7] by web30305.mail.mud.yahoo.com via HTTP; Fri, 25 May 2007 04:55:05 PDT Date: Fri, 25 May 2007 04:55:05 -0700 (PDT) From: Arne "Wörner" To: Nick Gustas In-Reply-To: <4656CB8C.5040809@tychl.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <102362.90990.qm@web30305.mail.mud.yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 11:55:06 -0000 --- Nick Gustas wrote: > Anyhow, I made the three changes you mentioned, and growfs still > compiles clean, > Does that mean, that there r no warnings? > and runs with proper display, but running fsck -y on the > grown file system scrolls for a long time with tons of errors and > eventually bombs out asking me to run it again. running it again doesn't > help. > Did u try to run the original R6.2 growfs on a smaller fs? I have heard, that growfs has a general malfunction, so that it produces things, that fsck finds funny... If u repeat fsck often, those warnings will disapear... :-)) > I've updated > > http://masq.tychl.net/growfs.patch > > with the changes you suggested. > > Keep in mind I'm no C programmer, but I can follow direction and would > love to see growfs 2+TB clean :) > Yup - its ok... I dont know so much about UFS, too... I was just wondering a bit... :-) -Arne ____________________________________________________________________________________Need a vacation? Get great deals to amazing places on Yahoo! Travel. http://travel.yahoo.com/ From owner-freebsd-fs@FreeBSD.ORG Fri May 25 12:38:24 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B5C616A46F for ; Fri, 25 May 2007 12:38:24 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [204.127.192.82]) by mx1.freebsd.org (Postfix) with ESMTP id 11A0B13C465 for ; Fri, 25 May 2007 12:38:24 +0000 (UTC) (envelope-from freebsd-fs@tychl.net) Received: from masq.tychl.net (tychl.no-ip.org[67.174.137.176]) by comcast.net (rwcrmhc12) with ESMTP id <20070525123823m1200bkf86e>; Fri, 25 May 2007 12:38:23 +0000 Received: from localhost (localhost [127.0.0.1]) by masq.tychl.net (Postfix) with ESMTP id 1C3E61CB4B; Fri, 25 May 2007 08:38:23 -0400 (EDT) X-Virus-Scanned: amavisd-new at tychl.net Received: from masq.tychl.net ([127.0.0.1]) by localhost (masq.tychl.net [127.0.0.1]) (amavisd-new, port 10024) with SMTP id bXPtDSt6iEtg; Fri, 25 May 2007 08:38:19 -0400 (EDT) Received: from [127.0.0.1] (67-39-225-23.ded.ameritech.net [67.39.225.23]) by masq.tychl.net (Postfix) with ESMTP id E9D691CB4A; Fri, 25 May 2007 08:38:18 -0400 (EDT) Message-ID: <4656D8B5.4090806@tychl.net> Date: Fri, 25 May 2007 08:38:13 -0400 From: Nick Gustas User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: "Arne \"WXrner\"" References: <102362.90990.qm@web30305.mail.mud.yahoo.com> In-Reply-To: <102362.90990.qm@web30305.mail.mud.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 12:38:24 -0000 Arne WXrner wrote: > --- Nick Gustas wrote: > >> Anyhow, I made the three changes you mentioned, and growfs still >> compiles clean, >> >> > Does that mean, that there r no warnings? > > yep AMD64# pwd /usr/src/sbin/growfs.edit AMD64# make cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -c growfs.c cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wno-pointer-sign -o growfs growfs.o gzip -cn growfs.8 > growfs.8.gz No complaints about arg 3 being the wrong datatype or signed vs unsigned errors, at least on AMD64. Doesn't mean it'll do what we need though! :) >> and runs with proper display, but running fsck -y on the >> grown file system scrolls for a long time with tons of errors and >> eventually bombs out asking me to run it again. running it again doesn't >> help. >> >> > Did u try to run the original R6.2 growfs on a smaller fs? I have heard, that > growfs has a general malfunction, so that it produces things, that fsck finds > funny... If u repeat fsck often, those warnings will disapear... :-)) > > It seems you are right, I just tried to grow a ~500GB filesystem to about 990GB on a i386 6.2 server, fsck had a fit even though the file system was mountable. Second run of fsck is still going! I thought I had tried growfs successfully on a sub 2TB FS sometime around 5.4 or 5.5, maybe I was mistaken. It was on a 4TB server, so when growfs gave a weird display when I tried it to grow a 2TB FS to 3TB, I never tried it again and bought all the drives I needed to fill the chassis right away. >> I've updated >> >> http://masq.tychl.net/growfs.patch >> >> with the changes you suggested. >> >> Keep in mind I'm no C programmer, but I can follow direction and would >> love to see growfs 2+TB clean :) >> >> > Yup - its ok... I dont know so much about UFS, too... I was just wondering a > bit... :-) > > -Arne > > > From owner-freebsd-fs@FreeBSD.ORG Fri May 25 13:28:21 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1618D16A468; Fri, 25 May 2007 13:28:21 +0000 (UTC) (envelope-from fernando@schapachnik.com.ar) Received: from mail.fac.org.ar (mail.fac.org.ar [200.59.49.21]) by mx1.freebsd.org (Postfix) with ESMTP id 68E7913C44B; Fri, 25 May 2007 13:28:18 +0000 (UTC) (envelope-from fernando@schapachnik.com.ar) Received: from servidor1.cursosvirtuales.com.ar (www.cursosvirtuales.com.ar [200.59.46.198]) by mail.fac.org.ar (8.12.11/8.12.11) with ESMTP id l4PDRum5051467; Fri, 25 May 2007 10:28:00 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from servidor1.cursosvirtuales.com.ar (localhost [127.0.0.1]) by servidor1.cursosvirtuales.com.ar (8.12.11/8.12.11) with ESMTP id l4PDRo7m057540; Fri, 25 May 2007 10:27:54 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from schapachnik.com.ar (uucp@localhost) by servidor1.cursosvirtuales.com.ar (8.12.11/8.12.11/Submit) with UUCP id l4PDRo0V057538; Fri, 25 May 2007 10:27:50 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: from funes.schapachnik.com.ar (localhost [127.0.0.1]) by funes.schapachnik.com.ar (8.13.8/8.13.8) with ESMTP id l4PDRmsO001759; Fri, 25 May 2007 10:27:48 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) Received: (from fpscha@localhost) by funes.schapachnik.com.ar (8.13.8/8.13.8/Submit) id l4PDRggF001745; Fri, 25 May 2007 10:27:42 -0300 (ART) (envelope-from fernando@schapachnik.com.ar) X-Authentication-Warning: funes.schapachnik.com.ar: fpscha set sender to fernando@schapachnik.com.ar using -f Date: Fri, 25 May 2007 10:27:42 -0300 From: Fernando Schapachnik To: Julian Elischer Message-ID: <20070525132742.GA1717@funes.schapachnik.com.ar> References: <20070519003910.GA3254@funes.schapachnik.com.ar> <464E834C.7060407@freebsd.org> <20070519173235.GI1340@funes.schapachnik.com.ar> <464F46A3.3030509@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <464F46A3.3030509@elischer.org> User-Agent: Mutt/1.4.2.1i X-OS: FreeBSD 6.2 - http://www.freebsd.org Cc: freebsd-fs@freebsd.org Subject: Re: Recovering a badly broken disk X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 13:28:21 -0000 En un mensaje anterior, Julian Elischer escribió: > > check recoverdisk Unluckily that didn't work either because beyond 65 MB all reads give CRC errors. The data recovery shop says that except for the damaged first sectors, the rest were copied verbatim are were OK. What's strange is that the in-disk backup partitions mounts fine, ls reports the right .tbz files with reasonable sizes but still the five of them only are readable up to 65 MB (their size is around 170 MB). Any ideas? Thanks. Fernando P. Schapachnik fernando@schapachnik.com.ar From owner-freebsd-fs@FreeBSD.ORG Fri May 25 14:48:40 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8EE6F16A46C for ; Fri, 25 May 2007 14:48:40 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: from web30313.mail.mud.yahoo.com (web30313.mail.mud.yahoo.com [209.191.69.75]) by mx1.freebsd.org (Postfix) with SMTP id 3DF9413C468 for ; Fri, 25 May 2007 14:48:40 +0000 (UTC) (envelope-from arne_woerner@yahoo.com) Received: (qmail 60513 invoked by uid 60001); 25 May 2007 14:48:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=XsWW+GkmpXmFysrXc1cODNlOIQkawPkRYiAcFwkAMPXHzpingxjk2qwU20Ea9g7YapwdNhpuFIWMEVOwFLPtWQq7WYcmYU1nuFLMGItyCeHI8lCtf4bzKWmU45CSLksiT7UDicNLn7CKTpMAB2ssx/9r5JjkuHNKpOMJafbl/do=; X-YMail-OSG: mWACoG0VM1ndMtjd2zmMI0FFTwZdhb.x_Ie3bnR5Z2npJmdVfpYrAUQ3Kf8gen2pnRcaJwMWif3YJAJCBTlNdcBZccuShGaXZmx1sbLI4nBse5vPuGzGdCrPyL6bEA-- Received: from [85.212.48.7] by web30313.mail.mud.yahoo.com via HTTP; Fri, 25 May 2007 07:48:39 PDT Date: Fri, 25 May 2007 07:48:39 -0700 (PDT) From: Arne "Wörner" To: Nick Gustas In-Reply-To: <4656D8B5.4090806@tychl.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <669449.60013.qm@web30313.mail.mud.yahoo.com> Cc: freebsd-fs@freebsd.org Subject: Re: Growing UFS beyond 2 TB X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 14:48:40 -0000 --- Nick Gustas wrote: > No complaints about arg 3 being the wrong datatype or signed vs unsigned > errors, at least on AMD64. Doesn't mean it'll do what we need though! :) > Cool... > It seems you are right, I just tried to grow a ~500GB filesystem to > about 990GB on a i386 6.2 server, fsck had a fit even though the file > system was mountable. Second run of fsck is still going! > Yup... I saw that, too... Although I am unable to reproduce that with an empty file system... When I saw it the first time, I used a quite full file system... > I thought I had tried growfs successfully on a sub 2TB FS sometime > around 5.4 or 5.5, maybe I was mistaken. It was on a 4TB server, so when > growfs gave a weird display when I tried it to grow a 2TB FS to 3TB, I > never tried it again and bought all the drives I needed to fill the > chassis right away. > Sometimes it works with no prob... -Arne ____________________________________________________________________________________ The fish are biting. Get more visitors on your site using Yahoo! Search Marketing. http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php From owner-freebsd-fs@FreeBSD.ORG Fri May 25 16:06:15 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 45CE416A400 for ; Fri, 25 May 2007 16:06:15 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id 07E7213C43E for ; Fri, 25 May 2007 16:06:14 +0000 (UTC) (envelope-from howard0su@gmail.com) Received: by py-out-1112.google.com with SMTP id a29so1505515pyi for ; Fri, 25 May 2007 09:06:14 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WS/BktjJBzpWRe8mjdpVlW8q+FZvJhJlT+0h+fbhJObN7hNJ9VJfMD8YjfpZjw+oPklAthiwpml91fu3LMBrX1CXQ1Lz4viEkOAF/euFDlRYP80FW0ZjvEtS7D44c1HClPdjTKmth4X0ywGf06eY6ScasxL2aDyZ3USaCoj4AfQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KeHg2Lks5x9+8TqVCKfowC14mHOwXCO9WIggHctFqP71OzCQA5XHh6uTdS2hg2+Iz7xjkmiWXxKl1wGHZs/ENFTuSfpbqs/BnLJWw28Yit5IX5rCy96Oso4jXIb/Sx3SpVcI+CGHgZTMucgpA3z13l/+wDurFTFSmMu7uZUXaDQ= Received: by 10.35.88.17 with SMTP id q17mr2476859pyl.1180109174110; Fri, 25 May 2007 09:06:14 -0700 (PDT) Received: by 10.35.79.18 with HTTP; Fri, 25 May 2007 09:06:14 -0700 (PDT) Message-ID: Date: Sat, 26 May 2007 00:06:14 +0800 From: "Howard Su" To: fs@freebsd.org, hacker@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: call for help on TMPFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2007 16:06:15 -0000 i updated the latest status in http://wiki.freebsd.org/TMPFS with the patch. i want some help on the panic. i even don't have idea on how to narrow it down. also testing and bug report is welcome. -- -Howard From owner-freebsd-fs@FreeBSD.ORG Sat May 26 01:01:09 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7A7EC16A41F; Sat, 26 May 2007 01:01:09 +0000 (UTC) (envelope-from aedwards@sandvine.com) Received: from gw.sandvine.com (gw.sandvine.com [199.243.201.138]) by mx1.freebsd.org (Postfix) with ESMTP id 1604513C45E; Sat, 26 May 2007 01:01:08 +0000 (UTC) (envelope-from aedwards@sandvine.com) Received: from exchange-2.sandvine.com ([192.168.16.12]) by gw.sandvine.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 25 May 2007 21:01:08 -0400 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Fri, 25 May 2007 21:01:07 -0400 Message-ID: <5230D3C40B842D4F9FB3CD368021BEF72F09AC@exchange-2.sandvine.com> In-Reply-To: <5230D3C40B842D4F9FB3CD368021BEF72F093F@exchange-2.sandvine.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Ufs dead-locks on freebsd 6.2 Thread-Index: AceZgA8XJQM9a6noQX+h86ioyzHh9wAHOkwgAAtyb/AAsywZQACkuL8g From: "Andrew Edwards" To: , X-OriginalArrivalTime: 26 May 2007 01:01:08.0285 (UTC) FILETIME=[580D9ED0:01C79F31] Cc: Subject: RE: Ufs dead-locks on freebsd 6.2 X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 01:01:09 -0000 I guess I feel similar to Gore Jarold with his posting about being frustrated with ufs. I have a serious problem, it's preventing me from upgrading my production systems to freebsd 6+, I can reproduce this problem easily but I can't seem to get anyone to assist me. At the suggestion of one of our internal developers I have enabled memguard to help find the cause of the panic and I'm posting the current backtrace etc. as recommended from the developers handbook on debgging dead-locks. If someone can help me it would be greatly appreciated. db> bt Tracing pid 26543 tid 105117 td 0xd41c6a80 kdb_enter(c0785f13) at kdb_enter+0x2b vfs_badlock(c0785f2c,c0786051,cd3dc414) at vfs_badlock+0x47 assert_vop_locked(cd3dc414,c0786051) at assert_vop_locked+0x4a vop_lock_post(fa048bec,0,1002,cd3dc414,fa048c08,...) at vop_lock_post+0x2a VOP_LOCK_APV(c07dc2e0,fa048bec) at VOP_LOCK_APV+0xa0 vn_lock(cd3dc414,1002,d41c6a80,0,0,...) at vn_lock+0xac vn_statfile(cd3f0870,fa048c74,cd39f280,d41c6a80) at vn_statfile+0x63 kern_fstat(d41c6a80,3,fa048c74) at kern_fstat+0x35 fstat(d41c6a80,fa048d04) at fstat+0x19 syscall(3b,805003b,bfbf003b,8054000,8054000,...) at syscall+0x25b Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (189, FreeBSD ELF32, fstat), eip =3D 0x6814b08f, esp =3D 0xbfbfec2c, ebp =3D 0xbfbfeca8 --- db> show pcpu cpuid =3D 1 curthread =3D 0xd41c6a80: pid 26543 "cron" curpcb =3D 0xfa048d90 fpcurthread =3D none idlethread =3D 0xccb5c600: pid 10 "idle: cpu1" APIC ID =3D 6 currentldt =3D 0x50 spin locks held: db> show allpcpu Current CPU: 1 cpuid =3D 0 curthread =3D 0xcd01ec00: pid 898 "cron" curpcb =3D 0xf5ad7d90 fpcurthread =3D none idlethread =3D 0xccb5c780: pid 11 "idle: cpu0" APIC ID =3D 0 currentldt =3D 0x50 spin locks held: cpuid =3D 1 curthread =3D 0xd41c6a80: pid 26543 "cron" curpcb =3D 0xfa048d90 fpcurthread =3D none idlethread =3D 0xccb5c600: pid 10 "idle: cpu1" APIC ID =3D 6 currentldt =3D 0x50 spin locks held: db> show locks exclusive sx user map r =3D 0 (0xd4135734) locked @ /usr/src/sys/vm/vm_map.c:3074 db> show alllocks Process 26543 (cron) thread 0xd41c6a80 (105117) exclusive sx user map r =3D 0 (0xd4135734) locked @ /usr/src/sys/vm/vm_map.c:3074 db> show lockedvnods Locked vnodes 0xce00cc3c: tag ufs, type VREG usecount 1, writecount 1, refcount 11 mountedhere 0 flags () v_object 0xcdae9b58 ref 0 pages 96 lock type ufs: EXCL (count 1) by thread 0xccffb300 (pid 18081) with 1 pending#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc06015c4 at vn_write+0x138 #5 0xc05c4544 at dofilewrite+0x7c #6 0xc05c43e3 at kern_writev+0x3b #7 0xc05c4309 at write+0x45 #8 0xc0723e2b at syscall+0x25b #9 0xc070ee0f at Xint0x80_syscall+0x1f ino 494730, on dev amrd0s1d 0xccf936cc: tag ufs, type VDIR usecount 1, writecount 0, refcount 2494 mountedhere 0 flags (VV_ROOT) v_object 0xd18598c4 ref 0 pages 0 lock type ufs: EXCL (count 1) by thread 0xcdff7000 (pid 19300) with 2492 pending#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05f5d12 at vget+0xbe #5 0xc05ed9f9 at vfs_hash_get+0x8d #6 0xc06b7b8f at ffs_vget+0x27 #7 0xc06c1435 at ufs_root+0x19 #8 0xc05eef1c at lookup+0x7c8 #9 0xc05ee4b2 at namei+0x39a #10 0xc0600a13 at vn_open_cred+0x5b #11 0xc06009b6 at vn_open+0x1e #12 0xc05fa126 at kern_open+0xb6 #13 0xc05fa03a at open+0x1a #14 0xc0723e2b at syscall+0x25b #15 0xc070ee0f at Xint0x80_syscall+0x1f ino 2, on dev amrd0s1d 0xcd00a000: tag ufs, type VDIR usecount 1, writecount 0, refcount 3 mountedhere 0 flags () v_object 0xce083210 ref 0 pages 0 lock type ufs: EXCL (count 1) by thread 0xcd574d80 (pid 89705) with 1 pending#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05f5d12 at vget+0xbe #5 0xc05ea48e at cache_lookup+0x34a #6 0xc05ea9c2 at vfs_cache_lookup+0x92 #7 0xc0737847 at VOP_LOOKUP_APV+0x87 #8 0xc05eebf8 at lookup+0x4a4 #9 0xc05ee4b2 at namei+0x39a #10 0xc0600a13 at vn_open_cred+0x5b #11 0xc06009b6 at vn_open+0x1e #12 0xc05fa126 at kern_open+0xb6 #13 0xc05fa03a at open+0x1a #14 0xc0723e2b at syscall+0x25b #15 0xc070ee0f at Xint0x80_syscall+0x1f ino 494592, on dev amrd0s1d 0xcd23f15c: tag ufs, type VREG usecount 1, writecount 1, refcount 4 mountedhere 0 flags () v_object 0xcd16ec60 ref 0 pages 12 lock type ufs: EXCL (count 1) by thread 0xccff8300 (pid 713)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc06015c4 at vn_write+0x138 #5 0xc05c4544 at dofilewrite+0x7c #6 0xc05c43e3 at kern_writev+0x3b #7 0xc05c4309 at write+0x45 #8 0xc0723e2b at syscall+0x25b #9 0xc070ee0f at Xint0x80_syscall+0x1f ino 494620, on dev amrd0s1d 0xd02a0984: tag ufs, type VREG usecount 1, writecount 1, refcount 3 mountedhere 0 flags () v_object 0xcd89fad4 ref 0 pages 3 lock type ufs: EXCL (count 1) by thread 0xccffb000 (pid 603)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 188453, on dev amrd0s1d 0xd0b442b8: tag ufs, type VREG usecount 1, writecount 1, refcount 2 mountedhere 0 flags () v_object 0xcffc88c4 ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xcd590480 (pid 18304)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424403, on dev amrd0s1d 0xd24d3c3c: tag ufs, type VREG usecount 1, writecount 1, refcount 2 mountedhere 0 flags () v_object 0xd13b3ce4 ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xcd59ec00 (pid 18735)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424405, on dev amrd0s1d 0xd09d6414: tag ufs, type VREG usecount 1, writecount 1, refcount 3 mountedhere 0 flags () v_object 0xcfd71b58 ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xcd6cfc00 (pid 20083)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424406, on dev amrd0s1d 0xce0762b8: tag ufs, type VREG usecount 1, writecount 1, refcount 3 mountedhere 0 flags () v_object 0xd14fcdec ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xcd01e000 (pid 17274)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424408, on dev amrd0s1d 0xce91f414: tag ufs, type VREG usecount 1, writecount 1, refcount 3 mountedhere 0 flags () v_object 0xd24af9cc ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xce03d780 (pid 20575)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424409, on dev amrd0s1d 0xd1701d98: tag ufs, type VREG usecount 1, writecount 1, refcount 3 mountedhere 0 flags () v_object 0xd0c8d39c ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xcd6ce180 (pid 21143)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424411, on dev amrd0s1d 0xcedf7828: tag ufs, type VREG usecount 1, writecount 1, refcount 3 mountedhere 0 flags () v_object 0xd2c37948 ref 0 pages 1 lock type ufs: EXCL (count 1) by thread 0xcd576000 (pid 21114)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc05fd950 at fsync+0x9c #5 0xc0723e2b at syscall+0x25b #6 0xc070ee0f at Xint0x80_syscall+0x1f ino 424412, on dev amrd0s1d 0xd1679570: tag ufs, type VREG usecount 1, writecount 1, refcount 69 mountedhere 0 flags () v_object 0xd1fd0318 ref 0 pages 9308 lock type ufs: EXCL (count 1) by thread 0xcd59ea80 (pid 65735)#0 0xc0593f0d at lockmgr+0x4ed #1 0xc06b8e0e at ffs_lock+0x76 #2 0xc0739787 at VOP_LOCK_APV+0x87 #3 0xc0601c28 at vn_lock+0xac #4 0xc06015c4 at vn_write+0x138 #5 0xc05c4544 at dofilewrite+0x7c #6 0xc05c43e3 at kern_writev+0x3b #7 0xc05c4309 at write+0x45 #8 0xc0723e2b at syscall+0x25b #9 0xc070ee0f at Xint0x80_syscall+0x1f ino 112037039, on dev amrd1s1d db> alltrace Tracing command pid 26548 tid 105114 td 0xd41c7000 *** error reading from address b4ba72d3 *** -----Original Message----- From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] On Behalf Of Andrew Edwards Sent: Tuesday, May 22, 2007 1:35 PM To: freebsd-fs@freebsd.org; freebsd-performance@freebsd.org Subject: RE: Ufs dead-locks on freebsd 6.2 It's been a couple of days with no response, how do I know if anyone is looking into this problem? > -----Original Message----- > From: owner-freebsd-fs@freebsd.org [mailto:owner-freebsd-fs@freebsd.org] > On Behalf Of Andrew Edwards > Sent: Saturday, May 19, 2007 12:34 AM > To: freebsd-fs@freebsd.org; freebsd-performance@freebsd.org > Subject: RE: Ufs dead-locks on freebsd 6.2 >=20 > Fsck didn't help but below is a list of processes that were stuck in=20 > disk. Also, one potential problem I've hit is I have mrtg scripts that > get launched from cron every min. MRTG is supposed to have a locking=20 > mechanism to prevent the same script from running at the same time but I > suspect since the filesystem was unaccessible the cron jobs just kept=20 > piling up and piling up until the system would eventually crash. I=20 > caught it when the load avg. was at 620 and killed all the cron's I=20 > could. That brought the load avg. down to under 1 however system is=20 > still taking up 30% of the processor time and the disks are basically=20 > idle. I can still do an ls -l on the root of all my mounted ufs and nfs > filesystems but on one it's taking a considerable amount longer than the > rest. This particular rsync that I was running is copying into the /d2 > fs. >=20 > The system is still running and I can make tpc connections and=20 > somethings I have running from inetd work but ssh stops responding right > away and I can't logon via the console. So, I've captured a core dump > of the system and rebooted so that I could use it again. Are there any > suggestion as to what to do next? I'm debaiting installing an adaptec > raid and rebuilding the system to see if I get the same problem, my=20 > worry is that it's the intel raid drivers that are causing this problem > and I have 4 other systems with the same card. >=20 >=20 > PID TT STAT TIME COMMAND > 2 ?? DL 0:04.86 [g_event] > 3 ?? DL 2:05.90 [g_up] > 4 ?? DL 1:07.95 [g_down] > 5 ?? DL 0:00.00 [xpt_thrd] > 6 ?? DL 0:00.00 [kqueue taskq] > 7 ?? DL 0:00.00 [thread taskq] > 8 ?? DL 0:06.96 [pagedaemon] > 9 ?? DL 0:00.00 [vmdaemon] > 15 ?? DL 0:22.28 [yarrow] > 24 ?? DL 0:00.01 [usb0] > 25 ?? DL 0:00.00 [usbtask] > 27 ?? DL 0:00.01 [usb1] > 29 ?? DL 0:00.01 [usb2] > 36 ?? DL 1:28.73 [pagezero] > 37 ?? DL 0:08.76 [bufdaemon] > 38 ?? DL 0:00.54 [vnlru] > 39 ?? DL 1:08.12 [syncer] > 40 ?? DL 0:04.00 [softdepflush] > 41 ?? DL 0:11.05 [schedcpu] > 27182 ?? Ds 0:05.75 /usr/sbin/syslogd -l /var/run/log -l > /var/named/var/run/log -b 127.0.0.1 -a 10.128.0.0/10 > 27471 ?? Is 0:01.10 /usr/local/bin/postmaster -D > /usr/local/pgsql/data (postgres) > 27594 ?? Is 0:00.04 /usr/libexec/ftpd -m -D -l -l > 27602 ?? DL 0:00.28 [smbiod1] > 96581 ?? D 0:00.00 cron: running job (cron) > 96582 ?? D 0:00.00 cron: running job (cron) > 96583 ?? D 0:00.00 cron: running job (cron) > 96585 ?? D 0:00.00 cron: running job (cron) > 96586 ?? D 0:00.00 cron: running job (cron) > 96587 ?? D 0:00.00 cron: running job (cron) > 96588 ?? D 0:00.00 cron: running job (cron) > 96589 ?? D 0:00.00 cron: running job (cron) > 96590 ?? D 0:00.00 cron: running job (cron) > 96591 ?? D 0:00.00 cron: running job (cron) > 96592 ?? D 0:00.00 cron: running job (cron) > 96593 ?? D 0:00.00 cron: running job (cron) > 96594 ?? D 0:00.00 cron: running job (cron) > 96607 ?? D 0:00.00 cron: running job (cron) > 96608 ?? D 0:00.00 cron: running job (cron) > 96609 ?? D 0:00.00 cron: running job (cron) > 96610 ?? D 0:00.00 cron: running job (cron) > 96611 ?? D 0:00.00 cron: running job (cron) > 96612 ?? D 0:00.00 cron: running job (cron) > 96613 ?? D 0:00.00 cron: running job (cron) > 96614 ?? D 0:00.00 cron: running job (cron) > 96615 ?? D 0:00.00 cron: running job (cron) > 96616 ?? D 0:00.00 cron: running job (cron) > 96617 ?? D 0:00.00 cron: running job (cron) > 96631 ?? D 0:00.00 cron: running job (cron) > 96632 ?? D 0:00.00 cron: running job (cron) > 96633 ?? D 0:00.00 cron: running job (cron) > 96634 ?? D 0:00.00 cron: running job (cron) > 96635 ?? D 0:00.00 cron: running job (cron) > 96636 ?? D 0:00.00 cron: running job (cron) > 96637 ?? D 0:00.00 cron: running job (cron) > 96638 ?? D 0:00.00 cron: running job (cron) > 96639 ?? D 0:00.00 cron: running job (cron) > 96642 ?? D 0:00.00 cron: running job (cron) > 96650 ?? D 0:00.00 cron: running job (cron) > 29393 p0 D+ 22:04.58 /usr/local/bin/rsync >=20 > real 0m0.012s > user 0m0.000s > sys 0m0.010s > / >=20 > real 0m0.019s > user 0m0.000s > sys 0m0.016s > /var >=20 > real 0m0.028s > user 0m0.008s > sys 0m0.018s > /diskless >=20 > real 0m0.017s > user 0m0.008s > sys 0m0.007s > /usr >=20 > real 0m0.016s > user 0m0.000s > sys 0m0.015s > /d2 >=20 > real 0m0.024s > user 0m0.000s > sys 0m0.023s > /exports/home >=20 > real 0m2.559s > user 0m0.216s > sys 0m2.307s >=20 From owner-freebsd-fs@FreeBSD.ORG Sat May 26 10:01:32 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C1CC516A400 for ; Sat, 26 May 2007 10:01:32 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 3400713C44B for ; Sat, 26 May 2007 10:01:32 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so495975uge for ; Sat, 26 May 2007 03:01:31 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oo4BfX9n+q6o2Netk7ahDsfWpIUjLs5t98pUekgxXGvhb5fR7Sjc3N3rd3PX0o/ZCmrMUtxLdDymeOQ5AM4Chcun9xthh9DFV8x9tXAwmYIxJTiocgv8bBDJJIbiZ5wBmXR9xbvssRIi2nZ1PPHM5cViE/g8mY258/NFpG2HArc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=B8bIOKZvgnbYHBov5UEt7pi/9StQdIfO4cW9+0qJRYWxFGlEldcKZRZ1lNxrTyqIePjV7NbQaamChieKHve4rrPkzbY6MsEQnNmSPRIKAwgS5nGWq/AsC6Vxz4HYa1wmexpS3osZEs0IoyXiIDjOcXIfhMja0hmEsYo+F15i0R0= Received: by 10.78.166.7 with SMTP id o7mr1146176hue.1180172183765; Sat, 26 May 2007 02:36:23 -0700 (PDT) Received: by 10.78.190.11 with HTTP; Sat, 26 May 2007 02:36:23 -0700 (PDT) Message-ID: <70e8236f0705260236x527b0484m96bc77ae51d8b287@mail.gmail.com> Date: Sat, 26 May 2007 10:36:23 +0100 From: "Joao Barros" To: freebsd-current , freebsd-fs@freebsd.org, "Pawel Jakub Dawidek" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: ZFS: LOR in dbuf.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 10:01:32 -0000 Hi Pawel, I upgraded my sources last night (just before your 2 commits) and now I get this constant LOR every 5 seconds: lock order reversal: 1st 0xc7b90c20 zfs:&dr->dt.di.dr_mtx (zfs:&dr->dt.di.dr_mtx) @ /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1866 2nd 0xc48e17e4 zfs:&db->db_mtx (zfs:&db->db_mtx) @ /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1888 KDB: stack backtrace: db_trace_self_wrapper(c0a1ae29,e67a45a0,c076d9ee,c0a1d252,c48e17e4,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c0a1d252,c48e17e4,c0d1b6f4,c0d1b6f4,c0d1b5d1,...) at kdb_backtrace+0x29 witness_checkorder(c48e17e4,9,c0d1b5d1,760,c48e17a8,...) at witness_checkorder+0x6de _sx_xlock(c48e17e4,c0d1b5d1,760,c1474788,1,...) at _sx_xlock+0x7a dbuf_sync_list(c7b90c38,c894de80,74a,2,c48e0910,...) at dbuf_sync_list+0x16f dbuf_sync_list(c48e09d0,c894de80,257,3,3,...) at dbuf_sync_list+0x107 dnode_sync(c48e0910,c894de80,7,3,3,...) at dnode_sync+0x1cd dmu_objset_sync(c4441000,c47a4678,c894de80,0,c4441698,...) at dmu_objset_sync+0x130 dsl_pool_sync(c4441600,49482,0,0,0,...) at dsl_pool_sync+0x190 spa_sync(c403d000,49482,0,c4441740,c444171c,...) at spa_sync+0x3f8 txg_sync_thread(c4441600,e67a4d38,c0a14eb6,324,c44b3900,...) at txg_sync_thread+0x15a fork_exit(c0ce46e0,c4441600,e67a4d38) at fork_exit+0xf1 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xe67a4d70, ebp = 0 --- Let me know if you need more info. -- Joao Barros From owner-freebsd-fs@FreeBSD.ORG Sat May 26 10:05:12 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B9D016A477; Sat, 26 May 2007 10:05:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 109A913C484; Sat, 26 May 2007 10:05:12 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 42ED41FFD99; Sat, 26 May 2007 12:05:10 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id E60281FFC58; Sat, 26 May 2007 12:05:05 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 300C944487F; Sat, 26 May 2007 10:04:46 +0000 (UTC) Date: Sat, 26 May 2007 10:04:46 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Joao Barros In-Reply-To: <70e8236f0705260236x527b0484m96bc77ae51d8b287@mail.gmail.com> Message-ID: <20070526100322.N13311@maildrop.int.zabbadoz.net> References: <70e8236f0705260236x527b0484m96bc77ae51d8b287@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-fs@freebsd.org, freebsd-current , Pawel Jakub Dawidek Subject: Re: ZFS: LOR in dbuf.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 10:05:12 -0000 On Sat, 26 May 2007, Joao Barros wrote: > Hi Pawel, > > I upgraded my sources last night (just before your 2 commits) and now > I get this constant LOR every 5 seconds: > > lock order reversal: > 1st 0xc7b90c20 zfs:&dr->dt.di.dr_mtx (zfs:&dr->dt.di.dr_mtx) @ > /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1866 > 2nd 0xc48e17e4 zfs:&db->db_mtx (zfs:&db->db_mtx) @ > /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1888 please check http://sources.zabbadoz.net/freebsd/lor.html and follow the instruction there. Read to the end of the page. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-fs@FreeBSD.ORG Sat May 26 10:21:09 2007 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 078BA16A468 for ; Sat, 26 May 2007 10:21:09 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 5EFA413C458 for ; Sat, 26 May 2007 10:21:08 +0000 (UTC) (envelope-from joao.barros@gmail.com) Received: by ug-out-1314.google.com with SMTP id u2so498640uge for ; Sat, 26 May 2007 03:21:07 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; 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; b=SpwTPtY3tfvzssvMqNETAxlsqEYcvgCBKQ9U6RJbfWy8o76BgGyXt49ju9DwfZ7Ur6zTRhS1sacHVVIXQiUGiLyZNr0ScMJgArNdF5QSytHyhi9gucgWkAskkJ6RPQncKTi5qNCsD7IuHcHmOEf7iG2ImSi6gt/I2ON8/1c7Ulw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=rjqAGemb+4McvtzxrWEXUVVxk3KFc9QZfRLD3ueyGl3WdjPlJyespdr6sRAFyXbxOmSOYNakJHu8r/T1QH82+SQLJTiHWRAe+hVRCgv27YjgxjkYhQy4vB9TY9dTvNWGCOp1C2P0sWIJcohPKMl2m/b5KGEEdgvevZAbwwUI2vQ= Received: by 10.78.204.7 with SMTP id b7mr1153245hug.1180174866706; Sat, 26 May 2007 03:21:06 -0700 (PDT) Received: by 10.78.190.11 with HTTP; Sat, 26 May 2007 03:21:06 -0700 (PDT) Message-ID: <70e8236f0705260321i3ee8b15fo189d265a23a3e5e@mail.gmail.com> Date: Sat, 26 May 2007 11:21:06 +0100 From: "Joao Barros" To: "Bjoern A. Zeeb" In-Reply-To: <20070526100322.N13311@maildrop.int.zabbadoz.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <70e8236f0705260236x527b0484m96bc77ae51d8b287@mail.gmail.com> <20070526100322.N13311@maildrop.int.zabbadoz.net> Cc: freebsd-fs@freebsd.org, freebsd-current , Pawel Jakub Dawidek Subject: Re: ZFS: LOR in dbuf.c X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 10:21:09 -0000 On 5/26/07, Bjoern A. Zeeb wrote: > On Sat, 26 May 2007, Joao Barros wrote: > > > Hi Pawel, > > > > I upgraded my sources last night (just before your 2 commits) and now > > I get this constant LOR every 5 seconds: > > > > lock order reversal: > > 1st 0xc7b90c20 zfs:&dr->dt.di.dr_mtx (zfs:&dr->dt.di.dr_mtx) @ > > /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1866 > > 2nd 0xc48e17e4 zfs:&db->db_mtx (zfs:&db->db_mtx) @ > > /usr/src/sys/modules/zfs/../../contrib/opensolaris/uts/common/fs/zfs/dbuf.c:1888 > > please check http://sources.zabbadoz.net/freebsd/lor.html and follow > the instruction there. Read to the end of the page. > > -- > Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT > I swear I checked your page before sending the email, but didn't actually searched the page, just browsed to the end and looked for dbuf.c Just to note that the way this LOR is happening now (5 seconds recurrent) didn't happen before , with sources from May 26. I had some occasional LORs but never this like this, that's the reason I went looking for a recent (last) LOR on your page :) -- Joao Barros From owner-freebsd-fs@FreeBSD.ORG Sat May 26 20:04:23 2007 Return-Path: X-Original-To: fs@freebsd.org Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C3A316A400 for ; Sat, 26 May 2007 20:04:23 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id C85E813C468 for ; Sat, 26 May 2007 20:04:22 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0843845683; Sat, 26 May 2007 21:40:13 +0200 (CEST) Received: from localhost (154.81.datacomsa.pl [195.34.81.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id B539345685; Sat, 26 May 2007 21:40:08 +0200 (CEST) Date: Sat, 26 May 2007 21:40:00 +0200 From: Pawel Jakub Dawidek To: Howard Su Message-ID: <20070526194000.GC27289@garage.freebsd.pl> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt" Content-Disposition: inline In-Reply-To: X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r804 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=BAYES_00 autolearn=ham version=3.0.4 Cc: fs@freebsd.org Subject: Re: call for help on TMPFS X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 May 2007 20:04:23 -0000 --yLVHuoLXiP9kZBkt Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 26, 2007 at 12:06:14AM +0800, Howard Su wrote: > i updated the latest status in http://wiki.freebsd.org/TMPFS with the > patch. i want some help on the panic. i even don't have idea on how to > narrow it down. also testing and bug report is welcome. I think you are missing some cases in lookup where you should add SAVENAME flag. I'd start from adding this (or similar) assertions: KASSERT((ap->a_cnp->cn_flags & SAVENAME), ("No SAVENAME")); to the following functions: tmpfs_create() tmpfs_remove() tmpfs_mkdir() tmpfs_rmdir() tmpfs_rename() (assert both: fcnp and tcnp) tmpfs_symlink() tmpfs_link() --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --yLVHuoLXiP9kZBkt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGWI0QForvXbEpPzQRAntBAKDe7O19akBrFqJTM/x1vZFKDlxWsgCcDXld mhG5oxvNflUaQ6AAEiUZ1f8= =IekL -----END PGP SIGNATURE----- --yLVHuoLXiP9kZBkt--