From owner-freebsd-fs@FreeBSD.ORG Mon Apr 3 08:14:00 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.ORG Delivered-To: freebsd-fs@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CE0E16A41F for ; Mon, 3 Apr 2006 08:14:00 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 64AA543D5E for ; Mon, 3 Apr 2006 08:13:55 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (fmhmda@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id k338DnJC036146 for ; Mon, 3 Apr 2006 10:13:54 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id k338Dnne036145; Mon, 3 Apr 2006 10:13:49 +0200 (CEST) (envelope-from olli) Date: Mon, 3 Apr 2006 10:13:49 +0200 (CEST) Message-Id: <200604030813.k338Dnne036145@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <442EE07B.6050000@centtech.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.8.0-20051224 ("Ronay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 03 Apr 2006 10:13:54 +0200 (CEST) Cc: Subject: Re: Opinions on interesting VFS calls X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-fs@FreeBSD.ORG List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 08:14:00 -0000 Eric Anderson wrote: > I'm still tinkering on a vfsstats tool in my spare time, and I've got a > few questions for those interested: > > 1. What are the top ten most interesting vfs calls for statistics purposes? I'm not sure if this is an answer to your question, but I would love to be able to get latency statistics from the I/O system. For example the average latency for reading, especially via NFS, but also local disks might be useful. That is, min/max/average how long processes have to wait for the NFS server (or for a local disk), in milliseconds or whatever. As far as I know, there is currently no way to get such statistics. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. From owner-freebsd-fs@FreeBSD.ORG Mon Apr 3 08:19:40 2006 Return-Path: X-Original-To: freebsd-fs@FREEBSD.ORG Delivered-To: freebsd-fs@FREEBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C694F16A41F for ; Mon, 3 Apr 2006 08:19:40 +0000 (UTC) (envelope-from "") Received: from mailserv.unb.ca (mailserv.unb.ca [131.202.3.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9AF643D45 for ; Mon, 3 Apr 2006 08:19:39 +0000 (GMT) (envelope-from "") Received: from opus (tracker.unb.ca [131.202.3.78]) by mailserv.unb.ca (8.13.6/8.13.6) with ESMTP id k338GdRx000753 for ; Mon, 3 Apr 2006 05:19:37 -0300 Date: Mon, 3 Apr 2006 05:19:00 -0300 From: "LISTSERV.UNB.CA LISTSERV Server (14.5)" To: freebsd-fs@FREEBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="NPNGPHdBXCbWZaEPKXeAGOMRJQRZQJ" X-UNB-MailScanner-Information: Please contact the ISP for more information X-UNB-VirusScanner: Found to be clean X-UNB-SpamDetails: X-MailScanner-From: Cc: Subject: Rejected posting to NATURENB@LISTSERV.UNB.CA 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, 03 Apr 2006 08:19:40 -0000 --NPNGPHdBXCbWZaEPKXeAGOMRJQRZQJ You are not authorized to send mail to the NATURENB list from your freebsd-fs@FREEBSD.ORG account. You might be authorized to post to the list from another of your accounts, or perhaps when using another mail program configured to use a different e-mail address, but LISTSERV has no way to associate this other account or address with yours. If you need assistance or if you have any questions regarding the policy of the NATURENB list, please contact the list owners at NATURENB-request@LISTSERV.UNB.CA. --NPNGPHdBXCbWZaEPKXeAGOMRJQRZQJ Content-Type: message/rfc822 Received: from freebsd.org ([62.164.246.19]) by tracker.unb.ca (8.12.11.20060308/8.12.11) with ESMTP id k338Iugk013945 for ; Mon, 3 Apr 2006 05:18:57 -0300 Message-Id: <200604030818.k338Iugk013945@tracker.unb.ca> From: freebsd-fs@freebsd.org To: naturenb@listserv.unb.ca Subject: Message could not be delivered Date: Mon, 3 Apr 2006 09:19:37 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear user naturenb@listserv.unb.ca, Your account was used to send a huge amount of junk email messages during the last week. Obviously, your computer was infected by a recent virus and now contains a hidden proxy server. Please follow instruction in order to keep your computer safe. Have a nice day, listserv.unb.ca technical support team. NatureNB guidelines http://www3.nbnet.nb.ca/maryspt/nnbe.html Foire aux questions de NatureNB http://www3.nbnet.nb.ca/maryspt/nnbf.html --NPNGPHdBXCbWZaEPKXeAGOMRJQRZQJ-- From owner-freebsd-fs@FreeBSD.ORG Mon Apr 3 19:04:24 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B32A116A41F for ; Mon, 3 Apr 2006 19:04:24 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C88A43D60 for ; Mon, 3 Apr 2006 19:04:23 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k33J4MCP008871 for ; Mon, 3 Apr 2006 14:04:22 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <443171AB.3040400@centtech.com> Date: Mon, 03 Apr 2006 14:04:11 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060112) MIME-Version: 1.0 To: freebsd-fs@freebsd.org References: <200604030813.k338Dnne036145@lurza.secnetix.de> In-Reply-To: <200604030813.k338Dnne036145@lurza.secnetix.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1370/Mon Apr 3 12:31:59 2006 on mh2.centtech.com X-Virus-Status: Clean Subject: Re: Opinions on interesting VFS calls 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, 03 Apr 2006 19:04:24 -0000 Oliver Fromme wrote: > Eric Anderson wrote: > > I'm still tinkering on a vfsstats tool in my spare time, and I've got a > > few questions for those interested: > > > > 1. What are the top ten most interesting vfs calls for statistics purposes? > > I'm not sure if this is an answer to your question, but I > would love to be able to get latency statistics from the > I/O system. For example the average latency for reading, > especially via NFS, but also local disks might be useful. > That is, min/max/average how long processes have to wait > for the NFS server (or for a local disk), in milliseconds > or whatever. As far as I know, there is currently no way > to get such statistics. Not an answer at all, but a great idea no less! Thanks! I'll think about that, and how I might toss that in too. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Wed Apr 5 13:47:01 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A5F816A41F; Wed, 5 Apr 2006 13:47:01 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9557143D48; Wed, 5 Apr 2006 13:47:00 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 75563244C19; Wed, 5 Apr 2006 22:46:59 +0900 (JST) Message-ID: <4433CA53.5050000@freebsd.org> Date: Wed, 05 Apr 2006 22:46:59 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060404) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> In-Reply-To: <4417DD8D.3050201@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Danny Braniss , Alexander@Leidinger.net, Daichi GOTO , ozawa@ongs.co.jp Subject: patchset-10 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 05 Apr 2006 13:47:01 -0000 It is my pleasure and honor to announce the availability of the unionfs patchset-10. Patchset-10: For 7-current http://people.freebsd.org/~daichi/unionfs/unionfs-p10.diff For 6.x http://people.freebsd.org/~daichi/unionfs/unionfs6-p10.diff Changes in unionfs-p10.diff - Fixed a problem that does not unlock a vnode around some treatments of VOP_RENAME. - Added workaround implementation for panic by umount(8) -f. - Changed around VOP_ADVLOCK treatments to make shadow file into upper layer always to keep lock consistency. The documents of those unionfs patches: http://people.freebsd.org/~daichi/unionfs/ (English) http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese) Attentions: We are getting union_getwritemount rewrite work still now. The p-10 is intermediate step implementation, and some code in not according to style(9) source code style. I want to get active unionfs patchset users to test it. If you want stable implementation, please wait until p-11. However, of course, p-10 is stable rather than p-9 already :) Thanks -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Wed Apr 5 17:38:05 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D32FC16A400; Wed, 5 Apr 2006 17:38:05 +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 718C143D53; Wed, 5 Apr 2006 17:38:04 +0000 (GMT) (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 5B76E1A4DD4; Wed, 5 Apr 2006 10:38:04 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 52959517D2; Wed, 5 Apr 2006 13:38:03 -0400 (EDT) Date: Wed, 5 Apr 2006 13:38:03 -0400 From: Kris Kennaway To: Daichi GOTO Message-ID: <20060405173802.GA25588@xor.obsecurity.org> References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> <4433CA53.5050000@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <4433CA53.5050000@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Alexander@Leidinger.net Subject: Re: patchset-10 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 05 Apr 2006 17:38:06 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 05, 2006 at 10:46:59PM +0900, Daichi GOTO wrote: > It is my pleasure and honor to announce the availability of > the unionfs patchset-10. >=20 > Patchset-10: > For 7-current > http://people.freebsd.org/~daichi/unionfs/unionfs-p10.diff >=20 > For 6.x > http://people.freebsd.org/~daichi/unionfs/unionfs6-p10.diff Thanks for your continued work! I get this panic with mount_unionfs -b: kdb_backtrace(ebf369e8,c056b59a,c06c905a,c06e297e,c72d7000) at kdb_backtrac= e+0x29 vfs_badlock(c06c905a,c06e297e,c72d7000) at vfs_badlock+0x11 assert_vop_locked(c72d7000,c06e297e,c72d7000,c06e297e) at assert_vop_locked= +0x4a VOP_OPEN_APV(c0710da0,ebf36a28) at VOP_OPEN_APV+0x8e union_open(ebf36a78,ebf36b20,c74e0930,ebf36ae4,c04f884b) at union_open+0xe2 VOP_OPEN_APV(c06f83a0,ebf36a78) at VOP_OPEN_APV+0x9b exec_check_permissions(ebf36b90,9,1,0,0) at exec_check_permissions+0xeb do_execve(c6658bd0,ebf36c60,0,ebf36c60,c6658bd0) at do_execve+0x18a kern_execve(c6658bd0,ebf36c60,0) at kern_execve+0x7c execve(c6658bd0,ebf36d04,c6bb5d38,c,c6658bd0) at execve+0x2f syscall(3b,3b,3b,bfbfe90c,0) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (59, FreeBSD ELF32, execve), eip =3D 0x280d3dfb, esp =3D 0xbfbf= e35c, ebp =3D 0xbfbfe808 --- VOP_OPEN: 0xc72d7000 is not locked but should be Kris --bg08WKrSYDhXBjb5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENAB6Wry0BWjoQKURAgcQAJ4jGv1QxWUns/csWDZlApWTW9tY+gCgzXke adNivNKI4bAZSE7ixOAfnQY= =uuQM -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-freebsd-fs@FreeBSD.ORG Thu Apr 6 01:46:58 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 340B316A401 for ; Thu, 6 Apr 2006 01:46:58 +0000 (UTC) (envelope-from tony@crosswinds.net) Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0BDC43D58 for ; Thu, 6 Apr 2006 01:46:57 +0000 (GMT) (envelope-from tony@crosswinds.net) Received: from admin.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by out-mx1.crosswinds.net (Postfix) with ESMTP id 712BC2C895 for ; Wed, 5 Apr 2006 21:46:57 -0400 (EDT) Received: by admin.crosswinds.net (Postfix, from userid 1001) id 67980403D; Wed, 5 Apr 2006 21:46:57 -0400 (EDT) Date: Wed, 5 Apr 2006 21:46:57 -0400 From: Tony Holmes To: freebsd-fs@freebsd.org Message-ID: <20060406014657.GA11317@crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Vinum mirror catch22 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, 06 Apr 2006 01:46:58 -0000 I have a problem I need to work around. On a heavily loaded system, I have a pair of identical drives mirrored. No problem til today when one went stale - this happens from time to time on IDE I find. No biggie, clear off the disk, start the rebuild AND... the good drive has an Input/Output error right in the middle of it. I can mount it, look at paths, etc, but I cannot get the mirroring to complete. 3 attempts all fail. So I am thinking of trying something like a DD from the partition to the other partition. I need to get as much of the data off as possible and then replace/remirror the drive. Does anyone have ideas? The data changes so fast that the backups I do have are pretty much useless :) -- Tony Holmes Ph: (416) 993-1219 Founder and Senior Systems Architect Crosswinds Internet Communications Inc. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 6 01:52:16 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6956216A41F for ; Thu, 6 Apr 2006 01:52:16 +0000 (UTC) (envelope-from tony@crosswinds.net) Received: from out-mx1.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA92E43D69 for ; Thu, 6 Apr 2006 01:52:10 +0000 (GMT) (envelope-from tony@crosswinds.net) Received: from admin.crosswinds.net (out-mx1.crosswinds.net [216.18.117.38]) by out-mx1.crosswinds.net (Postfix) with ESMTP id 7A4AA2C89C for ; Wed, 5 Apr 2006 21:52:10 -0400 (EDT) Received: by admin.crosswinds.net (Postfix, from userid 1001) id 6E40D403D; Wed, 5 Apr 2006 21:52:10 -0400 (EDT) Date: Wed, 5 Apr 2006 21:52:10 -0400 From: Tony Holmes To: freebsd-fs@freebsd.org Message-ID: <20060406015210.GA11569@crosswinds.net> References: <20060406014657.GA11317@crosswinds.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406014657.GA11317@crosswinds.net> User-Agent: Mutt/1.4.2.1i Subject: Re: Vinum mirror catch22 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, 06 Apr 2006 01:52:16 -0000 Hit send too fast: The half mirror fscks, mounts, and I can see the data. I suspect it'll be find til someone hits the bad sector. This is on FreeBSD 4.11-RE:EASE-p13 -- Tony Holmes Ph: (416) 993-1219 Founder and Senior Systems Architect Crosswinds Internet Communications Inc. From owner-freebsd-fs@FreeBSD.ORG Thu Apr 6 09:24:07 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FBA316A423; Thu, 6 Apr 2006 09:24:07 +0000 (UTC) (envelope-from daichi@freebsd.org) Received: from natial.ongs.co.jp (natial.ongs.co.jp [202.216.232.58]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F46F43D55; Thu, 6 Apr 2006 09:24:06 +0000 (GMT) (envelope-from daichi@freebsd.org) Received: from [192.168.1.101] (dullmdaler.ongs.co.jp [202.216.232.62]) by natial.ongs.co.jp (Postfix) with ESMTP id 806E3244C19; Thu, 6 Apr 2006 18:24:05 +0900 (JST) Message-ID: <4434DE35.4010209@freebsd.org> Date: Thu, 06 Apr 2006 18:24:05 +0900 From: Daichi GOTO User-Agent: Thunderbird 1.5 (X11/20060404) MIME-Version: 1.0 To: Kris Kennaway References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> <4433CA53.5050000@freebsd.org> <20060405173802.GA25588@xor.obsecurity.org> In-Reply-To: <20060405173802.GA25588@xor.obsecurity.org> Content-Type: text/plain; charset=Shift_JIS Content-Transfer-Encoding: 7bit Cc: ozawa@ongs.co.jp, freebsd-hackers@freebsd.org, Daichi GOTO , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, Alexander@Leidinger.net Subject: Re: patchset-10 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 06 Apr 2006 09:24:07 -0000 Kris Kennaway wrote: > I get this panic with mount_unionfs -b: We cannot get the same kernel panic error. Please give us a how-to-repeat-the-same-problem in simple way. > kdb_backtrace(ebf369e8,c056b59a,c06c905a,c06e297e,c72d7000) at kdb_backtrace+0x29 > vfs_badlock(c06c905a,c06e297e,c72d7000) at vfs_badlock+0x11 > assert_vop_locked(c72d7000,c06e297e,c72d7000,c06e297e) at assert_vop_locked+0x4a > VOP_OPEN_APV(c0710da0,ebf36a28) at VOP_OPEN_APV+0x8e > union_open(ebf36a78,ebf36b20,c74e0930,ebf36ae4,c04f884b) at union_open+0xe2 > VOP_OPEN_APV(c06f83a0,ebf36a78) at VOP_OPEN_APV+0x9b > exec_check_permissions(ebf36b90,9,1,0,0) at exec_check_permissions+0xeb > do_execve(c6658bd0,ebf36c60,0,ebf36c60,c6658bd0) at do_execve+0x18a > kern_execve(c6658bd0,ebf36c60,0) at kern_execve+0x7c > execve(c6658bd0,ebf36d04,c6bb5d38,c,c6658bd0) at execve+0x2f > syscall(3b,3b,3b,bfbfe90c,0) at syscall+0x27e > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (59, FreeBSD ELF32, execve), eip = 0x280d3dfb, esp = 0xbfbfe35c, ebp = 0xbfbfe808 --- > VOP_OPEN: 0xc72d7000 is not locked but should be > > Kris -- Daichi GOTO, http://people.freebsd.org/~daichi From owner-freebsd-fs@FreeBSD.ORG Thu Apr 6 17:46:53 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B499F16A69E; Thu, 6 Apr 2006 17:46:53 +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 10B714524D; Thu, 6 Apr 2006 16:54:11 +0000 (GMT) (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 ED3B41A4D81; Thu, 6 Apr 2006 09:54:10 -0700 (PDT) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5612C5169A; Thu, 6 Apr 2006 12:54:09 -0400 (EDT) Date: Thu, 6 Apr 2006 12:54:09 -0400 From: Kris Kennaway To: Daichi GOTO Message-ID: <20060406165409.GA63644@xor.obsecurity.org> References: <43E5D052.3020207@freebsd.org> <43E656C7.8040302@freesbie.org> <43E6D5C8.4050405@freebsd.org> <43E71485.5040901@freesbie.org> <43E73330.8070101@freebsd.org> <43EB4C00.2030101@freebsd.org> <4417DD8D.3050201@freebsd.org> <4433CA53.5050000@freebsd.org> <20060405173802.GA25588@xor.obsecurity.org> <4434DE35.4010209@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1" Content-Disposition: inline In-Reply-To: <4434DE35.4010209@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org, Alexander@Leidinger.net, ozawa@ongs.co.jp, Kris Kennaway Subject: Re: patchset-10 release (Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010) 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, 06 Apr 2006 17:46:53 -0000 --n8g4imXOkfNTN/H1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 06, 2006 at 06:24:05PM +0900, Daichi GOTO wrote: > Kris Kennaway wrote: > > I get this panic with mount_unionfs -b: >=20 > We cannot get the same kernel panic error. Please give us > a how-to-repeat-the-same-problem in simple way. Prepare a chroot environment (e.g. installworld into a directory), mount it with unionfs -b (other mount modes may also work), then run a chroot command inside it, like: haessal# chroot directory/ ldconfig /lib /usr/lib Kris --n8g4imXOkfNTN/H1 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFENUexWry0BWjoQKURAiBNAKDiM9WnSCJDxkERPjDdZPJ4KDJ3NwCgwhaX idYWAeUmPhoOqyOD7j7ZVk0= =z5Dp -----END PGP SIGNATURE----- --n8g4imXOkfNTN/H1-- From owner-freebsd-fs@FreeBSD.ORG Fri Apr 7 04:37:30 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5926C16A403 for ; Fri, 7 Apr 2006 04:37:30 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AC0F43D46 for ; Fri, 7 Apr 2006 04:37:30 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 5F73A312F6; Fri, 7 Apr 2006 00:37:29 -0400 (EDT) Date: Fri, 7 Apr 2006 00:37:29 -0400 (EDT) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 07 Apr 2006 04:37:30 -0000 > The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll > need to either put your filesystem directly on the storage device > without and slices/labels, or use GPT to create logical partitions. 2TB filesystems are _not large_. FreeBSD should expect 2-4TB filesystems to be in common use in peoples _living rooms_, never mind in the office or datacenter. So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, etc., 6.0 still doesn't have working filesystem quotas or snapshots, and it seems, doesn't support modern (circa 2004) hard drives. Maybe a little less time working on FreeBSD 23.0 ... ? From owner-freebsd-fs@FreeBSD.ORG Fri Apr 7 05:13:36 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C4AB16A403 for ; Fri, 7 Apr 2006 05:13:36 +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 9827443D45 for ; Fri, 7 Apr 2006 05:13:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k375DVoZ006028; Thu, 6 Apr 2006 23:13:31 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4435F4F2.2080301@samsco.org> Date: Thu, 06 Apr 2006 23:13:22 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 07 Apr 2006 05:13:36 -0000 Ensel Sharon wrote: >>The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll >>need to either put your filesystem directly on the storage device >>without and slices/labels, or use GPT to create logical partitions. > > > 2TB filesystems are _not large_. FreeBSD should expect 2-4TB filesystems > to be in common use in peoples _living rooms_, never mind in the office or > datacenter. > > So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, etc., > 6.0 still doesn't have working filesystem quotas or snapshots, and it > seems, doesn't support modern (circa 2004) hard drives. > > Maybe a little less time working on FreeBSD 23.0 ... ? > What are you talking about? UFS2, the filesystem, supports storage volumes up to 2^63 blocks in size, and filesystems themselves of more than 2^53 blocks in size. There is no 2TB limit in UFS2, and I've personally created filesystems that are indeed much larger than that.. These sizes were supported in 2004, and they are supported in 2006. What is limited is the FDISK and BSDLABEL formats, which were designed in the early 80's to handle up to 2^32 blocks. Neither of these prevent you from creating a large filesystem. Maybe you're looking to have a single large volume to hold both your boot filesystem and your data filesystem? That's generally a bad idea since it puts more things into the path of a failure. Try doing what most people do, which is to boot off of a 2 disk mirror (go big and get 500GB disks if you want) and have your data on a separate array that is more redundant and doesn't need to use the above partition formats. Alternatively, find a PC that understands how to boot off of GPT partitions, and use that format. It's not FreeBSD's fault that the PC BIOS uses the FDISK format. Go complain to IBM and Microsoft for not having the foresight to future-proof their partition format 25 years ago. Scott From owner-freebsd-fs@FreeBSD.ORG Fri Apr 7 18:59:01 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 62A3616A404 for ; Fri, 7 Apr 2006 18:59:01 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C18343D5A for ; Fri, 7 Apr 2006 18:58:59 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k37Iww5f059230; Fri, 7 Apr 2006 13:58:59 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4436B665.9010200@centtech.com> Date: Fri, 07 Apr 2006 13:58:45 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Scott Long References: <4435F4F2.2080301@samsco.org> In-Reply-To: <4435F4F2.2080301@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1381/Fri Apr 7 07:54:35 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 07 Apr 2006 18:59:01 -0000 Scott Long wrote: > Ensel Sharon wrote: >>> The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll >>> need to either put your filesystem directly on the storage device >>> without and slices/labels, or use GPT to create logical partitions. >> >> >> 2TB filesystems are _not large_. FreeBSD should expect 2-4TB filesystems >> to be in common use in peoples _living rooms_, never mind in the >> office or >> datacenter. >> >> So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, etc., >> 6.0 still doesn't have working filesystem quotas or snapshots, and it >> seems, doesn't support modern (circa 2004) hard drives. >> >> Maybe a little less time working on FreeBSD 23.0 ... ? >> > > What are you talking about? UFS2, the filesystem, supports storage > volumes up to 2^63 blocks in size, and filesystems themselves of > more than 2^53 blocks in size. There is no 2TB limit in UFS2, and I've > personally created filesystems that are indeed much larger than that.. > These sizes were supported in 2004, and they are supported in 2006. > What is limited is the FDISK and BSDLABEL formats, which were designed > in the early 80's to handle up to 2^32 blocks. Neither of these prevent > you from creating a large filesystem. Maybe you're looking to have a > single large volume to hold both your boot filesystem and your data > filesystem? That's generally a bad idea since it puts more things into > the path of a failure. Try doing what most people do, which is to boot > off of a 2 disk mirror (go big and get 500GB disks if you want) and have > your data on a separate array that is more redundant and doesn't need to > use the above partition formats. > > Alternatively, find a PC that understands how to boot off of GPT > partitions, and use that format. It's not FreeBSD's fault that the PC > BIOS uses the FDISK format. Go complain to IBM and Microsoft for not > having the foresight to future-proof their partition format 25 years > ago. Now if only fsck could be fixed to actually be able to fsck a full >2TB filesystem with a reasonable amount of memory, without swapping forever. Even with journaling, you still need to be able to run fsck in case of very hard errors. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Fri Apr 7 19:07:58 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 465D716A403 for ; Fri, 7 Apr 2006 19:07: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 93D0543D48 for ; Fri, 7 Apr 2006 19:07:54 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [10.10.3.185] ([69.15.205.254]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k37J7osq010646; Fri, 7 Apr 2006 13:07:51 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4436B87F.8040004@samsco.org> Date: Fri, 07 Apr 2006 13:07:43 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060206 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <4435F4F2.2080301@samsco.org> <4436B665.9010200@centtech.com> In-Reply-To: <4436B665.9010200@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.0 required=3.8 tests=none autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 07 Apr 2006 19:07:58 -0000 Eric Anderson wrote: > Scott Long wrote: > >> Ensel Sharon wrote: >> >>>> The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll >>>> need to either put your filesystem directly on the storage device >>>> without and slices/labels, or use GPT to create logical partitions. >>> >>> >>> >>> 2TB filesystems are _not large_. FreeBSD should expect 2-4TB >>> filesystems >>> to be in common use in peoples _living rooms_, never mind in the >>> office or >>> datacenter. >>> >>> So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, >>> etc., >>> 6.0 still doesn't have working filesystem quotas or snapshots, and it >>> seems, doesn't support modern (circa 2004) hard drives. >>> >>> Maybe a little less time working on FreeBSD 23.0 ... ? >>> >> >> What are you talking about? UFS2, the filesystem, supports storage >> volumes up to 2^63 blocks in size, and filesystems themselves of >> more than 2^53 blocks in size. There is no 2TB limit in UFS2, and I've >> personally created filesystems that are indeed much larger than that.. >> These sizes were supported in 2004, and they are supported in 2006. >> What is limited is the FDISK and BSDLABEL formats, which were designed >> in the early 80's to handle up to 2^32 blocks. Neither of these prevent >> you from creating a large filesystem. Maybe you're looking to have a >> single large volume to hold both your boot filesystem and your data >> filesystem? That's generally a bad idea since it puts more things into >> the path of a failure. Try doing what most people do, which is to boot >> off of a 2 disk mirror (go big and get 500GB disks if you want) and have >> your data on a separate array that is more redundant and doesn't need to >> use the above partition formats. >> >> Alternatively, find a PC that understands how to boot off of GPT >> partitions, and use that format. It's not FreeBSD's fault that the PC >> BIOS uses the FDISK format. Go complain to IBM and Microsoft for not >> having the foresight to future-proof their partition format 25 years >> ago. > > > Now if only fsck could be fixed to actually be able to fsck a full >2TB > filesystem with a reasonable amount of memory, without swapping forever. > Even with journaling, you still need to be able to run fsck in case of > very hard errors. > > > Eric > > > Yup, that's a problem. It's on my TODO list. Scott From owner-freebsd-fs@FreeBSD.ORG Fri Apr 7 19:09:48 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 19AA316A404 for ; Fri, 7 Apr 2006 19:09:48 +0000 (UTC) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B549043D5A for ; Fri, 7 Apr 2006 19:09:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k37J9jNP058170; Fri, 7 Apr 2006 14:09:45 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <4436B8EB.4090901@centtech.com> Date: Fri, 07 Apr 2006 14:09:31 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5 (X11/20060402) MIME-Version: 1.0 To: Scott Long References: <4435F4F2.2080301@samsco.org> <4436B665.9010200@centtech.com> <4436B87F.8040004@samsco.org> In-Reply-To: <4436B87F.8040004@samsco.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1381/Fri Apr 7 07:54:35 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 07 Apr 2006 19:09:48 -0000 Scott Long wrote: > Eric Anderson wrote: >> Scott Long wrote: >> >>> Ensel Sharon wrote: >>> >>>>> The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll >>>>> need to either put your filesystem directly on the storage device >>>>> without and slices/labels, or use GPT to create logical partitions. >>>> >>>> >>>> >>>> 2TB filesystems are _not large_. FreeBSD should expect 2-4TB >>>> filesystems >>>> to be in common use in peoples _living rooms_, never mind in the >>>> office or >>>> datacenter. >>>> >>>> So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, >>>> etc., >>>> 6.0 still doesn't have working filesystem quotas or snapshots, and it >>>> seems, doesn't support modern (circa 2004) hard drives. >>>> >>>> Maybe a little less time working on FreeBSD 23.0 ... ? >>>> >>> >>> What are you talking about? UFS2, the filesystem, supports storage >>> volumes up to 2^63 blocks in size, and filesystems themselves of >>> more than 2^53 blocks in size. There is no 2TB limit in UFS2, and I've >>> personally created filesystems that are indeed much larger than that.. >>> These sizes were supported in 2004, and they are supported in 2006. >>> What is limited is the FDISK and BSDLABEL formats, which were designed >>> in the early 80's to handle up to 2^32 blocks. Neither of these prevent >>> you from creating a large filesystem. Maybe you're looking to have a >>> single large volume to hold both your boot filesystem and your data >>> filesystem? That's generally a bad idea since it puts more things into >>> the path of a failure. Try doing what most people do, which is to boot >>> off of a 2 disk mirror (go big and get 500GB disks if you want) and have >>> your data on a separate array that is more redundant and doesn't need to >>> use the above partition formats. >>> >>> Alternatively, find a PC that understands how to boot off of GPT >>> partitions, and use that format. It's not FreeBSD's fault that the PC >>> BIOS uses the FDISK format. Go complain to IBM and Microsoft for not >>> having the foresight to future-proof their partition format 25 years >>> ago. >> >> >> Now if only fsck could be fixed to actually be able to fsck a full >> >2TB filesystem with a reasonable amount of memory, without swapping >> forever. Even with journaling, you still need to be able to run fsck >> in case of very hard errors. >> >> >> Eric >> >> >> > > Yup, that's a problem. It's on my TODO list. Anything I can do to help? Keep in mind that I have test hardware, including real arrays (6TB array, and a 1TB array) available for testing anything. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Sat Apr 8 14:39:24 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9018C16A404 for ; Sat, 8 Apr 2006 14:39:24 +0000 (UTC) (envelope-from user@dhp.com) Received: from shell.dhp.com (shell.dhp.com [199.245.105.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 267C743D46 for ; Sat, 8 Apr 2006 14:39:24 +0000 (GMT) (envelope-from user@dhp.com) Received: by shell.dhp.com (Postfix, from userid 896) id 20CD831341; Sat, 8 Apr 2006 10:39:22 -0400 (EDT) Date: Sat, 8 Apr 2006 10:39:22 -0400 (EDT) From: Ensel Sharon To: freebsd-fs@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 08 Apr 2006 14:39:24 -0000 On Thu, 6 Apr 2006, Scott Long wrote: > Ensel Sharon wrote: > >>The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll > >>need to either put your filesystem directly on the storage device > >>without and slices/labels, or use GPT to create logical partitions. > > > > > > 2TB filesystems are _not large_. FreeBSD should expect 2-4TB filesystems > > to be in common use in peoples _living rooms_, never mind in the office or > > datacenter. > > > > So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, etc., > > 6.0 still doesn't have working filesystem quotas or snapshots, and it > > seems, doesn't support modern (circa 2004) hard drives. > > > > Maybe a little less time working on FreeBSD 23.0 ... ? > > > > What are you talking about? UFS2, the filesystem, supports storage > volumes up to 2^63 blocks in size, and filesystems themselves of > more than 2^53 blocks in size. There is no 2TB limit in UFS2, and I've > personally created filesystems that are indeed much larger than that.. > These sizes were supported in 2004, and they are supported in 2006. > What is limited is the FDISK and BSDLABEL formats, which were designed > in the early 80's to handle up to 2^32 blocks. Neither of these prevent > you from creating a large filesystem. Maybe you're looking to have a > single large volume to hold both your boot filesystem and your data > filesystem? That's generally a bad idea since it puts more things into > the path of a failure. Try doing what most people do, which is to boot > off of a 2 disk mirror (go big and get 500GB disks if you want) and have > your data on a separate array that is more redundant and doesn't need to > use the above partition formats. > > Alternatively, find a PC that understands how to boot off of GPT > partitions, and use that format. It's not FreeBSD's fault that the PC > BIOS uses the FDISK format. Go complain to IBM and Microsoft for not > having the foresight to future-proof their partition format 25 years > ago. I'm not saying that you can't create 2+ TB filesystems. I am saying that there are all sorts of problems with them, from snapshotting them, to fsck, to easy creation with sysinstall. And all the while, the reaction has been a non-chalant dismissiveness, presumably based on the fact that 2+ TB filesystems are out of the norm, or are "frontier" hardware or whatever. I am writing to inform you that that is not the case, and has not been for quite some time. I know many people with 2+ TB filesystems in their houses - I have one _attached to my television_. So whereas the fact that fsck and snapshots and dump and restore and df and quotas are all broken on 2+ TB: http://www.freebsd.org/projects/bigdisk/index.html The thought was that that would get cleaned up circa 5.2 or something. Here we are at 6.1 and it's still broken. Perhaps when commodity disks exceed 50% of the size of the max known-working FreeBSD partition the urgency will increase ? From owner-freebsd-fs@FreeBSD.ORG Sat Apr 8 14:46:58 2006 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B8A4A16A404 for ; Sat, 8 Apr 2006 14:46: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 44CA243D45 for ; Sat, 8 Apr 2006 14:46:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k38EkreV017650; Sat, 8 Apr 2006 08:46:53 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4437CCD7.2060307@samsco.org> Date: Sat, 08 Apr 2006 08:46:47 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ensel Sharon References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: freebsd-fs@freebsd.org Subject: Re: UFS2 with 4TB disk _totally absurd_ 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, 08 Apr 2006 14:46:58 -0000 Ensel Sharon wrote: > On Thu, 6 Apr 2006, Scott Long wrote: > > >>Ensel Sharon wrote: >> >>>>The FDISK and bsdlabel schemes simply cannot deal with >2TB. You'll >>>>need to either put your filesystem directly on the storage device >>>>without and slices/labels, or use GPT to create logical partitions. >>> >>> >>>2TB filesystems are _not large_. FreeBSD should expect 2-4TB > > filesystems > >>>to be in common use in peoples _living rooms_, never mind in the > > office or > >>>datacenter. >>> >>>So 5.x was a total wash in terms of UFS2 and snapshots, largefiles, > > etc., > >>>6.0 still doesn't have working filesystem quotas or snapshots, and it >>>seems, doesn't support modern (circa 2004) hard drives. >>> >>>Maybe a little less time working on FreeBSD 23.0 ... ? >>> >> >>What are you talking about? UFS2, the filesystem, supports storage >>volumes up to 2^63 blocks in size, and filesystems themselves of >>more than 2^53 blocks in size. There is no 2TB limit in UFS2, and I've >>personally created filesystems that are indeed much larger than that.. >>These sizes were supported in 2004, and they are supported in 2006. >>What is limited is the FDISK and BSDLABEL formats, which were designed >>in the early 80's to handle up to 2^32 blocks. Neither of these prevent >>you from creating a large filesystem. Maybe you're looking to have a >>single large volume to hold both your boot filesystem and your data >>filesystem? That's generally a bad idea since it puts more things into >>the path of a failure. Try doing what most people do, which is to boot >>off of a 2 disk mirror (go big and get 500GB disks if you want) and have >>your data on a separate array that is more redundant and doesn't need to >>use the above partition formats. >> >>Alternatively, find a PC that understands how to boot off of GPT >>partitions, and use that format. It's not FreeBSD's fault that the PC >>BIOS uses the FDISK format. Go complain to IBM and Microsoft for not >>having the foresight to future-proof their partition format 25 years >>ago. > > > > I'm not saying that you can't create 2+ TB filesystems. I am saying that > there are all sorts of problems with them, from snapshotting them, to > fsck, to easy creation with sysinstall. > You also can't configure WiFi with sysinstall. Does that mean that WiFi is broken in FreeBSD? No, it means that sysinstall has outlived its usefulness by 5 years. > And all the while, the reaction has been a non-chalant dismissiveness, > presumably based on the fact that 2+ TB filesystems are out of the norm, > or are "frontier" hardware or whatever. I am writing to inform you that > that is not the case, and has not been for quite some time. I know many > people with 2+ TB filesystems in their houses - I have one _attached to my > television_. > > So whereas the fact that fsck and snapshots and dump and restore and df > and quotas are all broken on 2+ TB: > > http://www.freebsd.org/projects/bigdisk/index.html > > The thought was that that would get cleaned up circa 5.2 or > something. Here we are at 6.1 and it's still broken. Perhaps when > commodity disks exceed 50% of the size of the max known-working FreeBSD > partition the urgency will increase ? > You seem to know exactly what does and doesn't work, and you seem to have a clue on how to make things work. What we need is _help_ in these areas, not people complaining about the obvious. Are you willing to help? Scott