From owner-freebsd-fs@FreeBSD.ORG Tue Dec 13 15:19:07 2005 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 C29E716A41F; Tue, 13 Dec 2005 15:19:07 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A0E143D62; Tue, 13 Dec 2005 15:19:06 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from c-24-63-58-245.hsd1.ma.comcast.net ([24.63.58.245]) by comcast.net (rwcrmhc13) with ESMTP id <20051213151905015004r42re>; Tue, 13 Dec 2005 15:19:05 +0000 Received: from c-24-63-58-245.hsd1.ma.comcast.net (localhost [127.0.0.1]) by c-24-63-58-245.hsd1.ma.comcast.net (8.13.4/8.13.1) with ESMTP id jBDFJ9qJ026852; Tue, 13 Dec 2005 10:19:09 -0500 (EST) (envelope-from rodrigc@c-24-63-58-245.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-24-63-58-245.hsd1.ma.comcast.net (8.13.4/8.13.1/Submit) id jBDFJ8cr026851; Tue, 13 Dec 2005 10:19:08 -0500 (EST) (envelope-from rodrigc) Date: Tue, 13 Dec 2005 10:19:08 -0500 From: Craig Rodrigues To: freebsd-current@freebsd.org Message-ID: <20051213151908.GA26821@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: freebsd-fs@freebsd.org Subject: XFS (read-only) support committed to CURRENT 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, 13 Dec 2005 15:19:07 -0000 Hi, Read-only XFS support has been committed to FreeBSD-CURRENT. Write access to XFS is not supported at this time. The XFS for FreeBSD source code is based off of GPL'd sources provided by SGI. You can compile it into your kernel by adding "XFS" to your kernel config file, or you can "kldload xfs". If you have an XFS partition on your system, you can try mounting it with: mount -t xfs [device] [mntpoint] Additional utilities such as mkfs.xfs are available in the sysutils/xfsprogs port. Many thanks to Alexander Kabaev and Russell Cattelan for starting and doing most of the work on the XFS for FreeBSD port, and also to SGI for making the XFS source code freely available. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 10:13:02 2005 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 78CEC16A41F for ; Thu, 15 Dec 2005 10:13:02 +0000 (GMT) (envelope-from namondo@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DC1643D75 for ; Thu, 15 Dec 2005 10:12:52 +0000 (GMT) (envelope-from namondo@gmail.com) Received: by nproxy.gmail.com with SMTP id p48so119200nfa for ; Thu, 15 Dec 2005 02:12:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=e1r/bf/UQCmt0QQcCvfhVMb0jyaGTuXCqqjxwadKRVSgc1WVFgGjSKtphGNdz4Q48J1Vu/Z4BCIw7gOhL2v1GUq2QExYTaPP3LCOMYJmKVitDXiPK6Dos8EMuWgiXLGqmXEWbWEpfwf1uRg/yJHz5clbJHIPxqP4JavscygBDt0= Received: by 10.48.127.10 with SMTP id z10mr72752nfc; Thu, 15 Dec 2005 02:12:51 -0800 (PST) Received: by 10.48.213.13 with HTTP; Thu, 15 Dec 2005 02:12:50 -0800 (PST) Message-ID: <18eab3b50512150212k4624d38er@mail.gmail.com> Date: Thu, 15 Dec 2005 11:12:50 +0100 From: t c To: freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: filesystem full - freebsd 5.3 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, 15 Dec 2005 10:13:02 -0000 Hello, I've got the following error messages in dmesg.today, but there are lots inodes (and free space) on that partition (/home): pid 50371 (rateup), uid 0 inumber 1130885 on /home: filesystem full pid 42486 (httpd), uid 80 inumber 1059960 on /home: filesystem full pid 50614 (virtual), uid 1004 inumber 966735 on /home: filesystem full (many times each row...) root@ns:~# df -hi Filesystem Size Used Avail Capacity iused ifree %iused Mounted on /dev/ad0s1a 4.8G 1.2G 3.2G 27% 159048 500406 24% / devfs 1.0K 1.0K 0B 100% 0 0 100% /dev /dev/ad0s1e 22G 16G 6.0G 72% 114104 2829894 4% /home /dev/ad0s1d 9.7G 3.2G 5.7G 36% 14119 1304791 1% /var devfs 1.0K 1.0K 0B 100% 0 0 100% /var/named/dev root@ns:/etc# mount /dev/ad0s1a on / (ufs, local) devfs on /dev (devfs, local) /dev/ad0s1e on /home (ufs, local, soft-updates) /dev/ad0s1d on /var (ufs, local, soft-updates) devfs on /var/named/dev (devfs, local) I've found a similar problem in the archives - without solution.... Any suggestion? Thanks in advance: amondo From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 13:40:16 2005 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 5A8B316A41F for ; Thu, 15 Dec 2005 13:40:16 +0000 (GMT) (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 80B2C43D5D for ; Thu, 15 Dec 2005 13:40:15 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (mbcncv@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFDeA5x057457 for ; Thu, 15 Dec 2005 14:40:14 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFDeAYB057456; Thu, 15 Dec 2005 14:40:10 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 14:40:10 +0100 (CET) Message-Id: <200512151340.jBFDeAYB057456@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <18eab3b50512150212k4624d38er@mail.gmail.com> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: filesystem full - freebsd 5.3 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: Thu, 15 Dec 2005 13:40:16 -0000 t c wrote: > I've got the following error messages in dmesg.today, but there are lots > inodes (and free space) on that partition (/home): > > pid 50371 (rateup), uid 0 inumber 1130885 on /home: filesystem full > pid 42486 (httpd), uid 80 inumber 1059960 on /home: filesystem full > pid 50614 (virtual), uid 1004 inumber 966735 on /home: filesystem full > (many times each row...) Maybe the file system was really full at the time those problems were logged. Then some cronjob (e.g. logrotate or whatever) cleaned up, and now you don't see any traces of the problem anymore. If you want to find out, you could monitor your free space continously. The easiest way to do that would probably be a small shell script which appends `df -k /home` to a log file in /var. You can call the script every 5 minutes via cron, for example. Usually, when there are messages reporting that the file system is full, it really _is_ full at that time. In theory there could be some inconsistencies or other damage of the filesystem, but in that case you should also get other error messages. If you want to be sure, umount the file system and fsck it. I bet there will be no errors. 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. "... there are two ways of constructing a software design: One way is to make it so simple that there are _obviously_ no deficiencies and the other way is to make it so complicated that there are no _obvious_ deficiencies." -- C.A.R. Hoare, ACM Turing Award Lecture, 1980 From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 15:24:18 2005 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 5BC8416A41F for ; Thu, 15 Dec 2005 15:24:18 +0000 (GMT) (envelope-from dworkin@village.org) Received: from green-dome.village.org (green-dome.village.org [168.103.84.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55FFF43D53 for ; Thu, 15 Dec 2005 15:24:16 +0000 (GMT) (envelope-from dworkin@village.org) Received: from green-dome.village.org (localhost.village.org [127.0.0.1]) by green-dome.village.org (8.11.0/8.11.0) with ESMTP id jBFFOFm04575 for ; Thu, 15 Dec 2005 08:24:15 -0700 (MST) Message-Id: <200512151524.jBFFOFm04575@green-dome.village.org> To: freebsd-fs@freebsd.org From: dlm-fb@weaselfish.com In-reply-to: Your message of Thu, 15 Dec 2005 14:40:10 +0100 Date: Thu, 15 Dec 2005 08:24:15 -0700 Subject: Re: filesystem full - freebsd 5.3 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, 15 Dec 2005 15:24:18 -0000 Oliver Fromme wrote: : t c wrote: : > I've got the following error messages in dmesg.today, but there are lots : > inodes (and free space) on that partition (/home): : > : > pid 50371 (rateup), uid 0 inumber 1130885 on /home: filesystem full : > pid 42486 (httpd), uid 80 inumber 1059960 on /home: filesystem full : > pid 50614 (virtual), uid 1004 inumber 966735 on /home: filesystem full : > (many times each row...) : [...] : Usually, when there are messages reporting that the file : system is full, it really _is_ full at that time. : In theory there could be some inconsistencies or other : damage of the filesystem, but in that case you should also : get other error messages. If you want to be sure, umount : the file system and fsck it. I bet there will be no : errors. Perhaps more likely, he was trying to allocate full-size blocks, and the only things available were fragments. The output from df doesn't distinguish between the two types of available space. You can use dumpfs(8) to do that. Dworkin From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 16:14:45 2005 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 2FA2716A41F for ; Thu, 15 Dec 2005 16:14:45 +0000 (GMT) (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 2A5CD43D6A for ; Thu, 15 Dec 2005 16:14:38 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (rgripy@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFGEbj5063067 for ; Thu, 15 Dec 2005 17:14:37 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFGEbGO063066; Thu, 15 Dec 2005 17:14:37 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 17:14:37 +0100 (CET) Message-Id: <200512151614.jBFGEbGO063066@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <200512151524.jBFFOFm04575@green-dome.village.org> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: filesystem full - freebsd 5.3 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: Thu, 15 Dec 2005 16:14:45 -0000 dlm-fb@weaselfish.com wrote: > Oliver Fromme wrote: > : t c wrote: > : > I've got the following error messages in dmesg.today, but there are lots > : > inodes (and free space) on that partition (/home): > : > > : > pid 50371 (rateup), uid 0 inumber 1130885 on /home: filesystem full > : > pid 42486 (httpd), uid 80 inumber 1059960 on /home: filesystem full > : > pid 50614 (virtual), uid 1004 inumber 966735 on /home: filesystem full > : > (many times each row...) > : [...] > : Usually, when there are messages reporting that the file > : system is full, it really _is_ full at that time. > : In theory there could be some inconsistencies or other > : damage of the filesystem, but in that case you should also > : get other error messages. If you want to be sure, umount > : the file system and fsck it. I bet there will be no > : errors. > > Perhaps more likely, he was trying to allocate full-size blocks, and > the only things available were fragments. I considered mentioning the fragments issue, too, but I don't think it applies in this case. His file system is 22 Gbyte with 6 Gbyte free. I think it is very unlikely that those 6 Gbyte are all fragments. 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. "Documentation is like sex; when it's good, it's very, very good, and when it's bad, it's better than nothing." -- Dick Brandon From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 16:29:19 2005 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 A602316A41F for ; Thu, 15 Dec 2005 16:29:19 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D63843D4C for ; Thu, 15 Dec 2005 16:29:18 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002122505.msg for ; Thu, 15 Dec 2005 16:28:13 +0000 Message-ID: <01ca01c60194$8bc244b0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: References: <200512151614.jBFGEbGO063066@lurza.secnetix.de> Date: Thu, 15 Dec 2005 16:28:08 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Thu, 15 Dec 2005 16:28:13 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-fs@FreeBSD.ORG X-MDAV-Processed: multiplay.co.uk, Thu, 15 Dec 2005 16:28:15 +0000 Cc: Subject: Re: filesystem full - freebsd 5.3 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, 15 Dec 2005 16:29:19 -0000 Out of inodes? Steve ----- Original Message ----- From: "Oliver Fromme" ... > I considered mentioning the fragments issue, too, but I > don't think it applies in this case. His file system is > 22 Gbyte with 6 Gbyte free. I think it is very unlikely > that those 6 Gbyte are all fragments. ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 16:41:57 2005 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 833F816A41F for ; Thu, 15 Dec 2005 16:41:57 +0000 (GMT) (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 6FCF143D49 for ; Thu, 15 Dec 2005 16:41:56 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (spslgh@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBFGfsuH064465 for ; Thu, 15 Dec 2005 17:41:55 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBFGfsfs064464; Thu, 15 Dec 2005 17:41:54 +0100 (CET) (envelope-from olli) Date: Thu, 15 Dec 2005 17:41:54 +0100 (CET) Message-Id: <200512151641.jBFGfsfs064464@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <01ca01c60194$8bc244b0$b3db87d4@multiplay.co.uk> X-Newsgroups: list.freebsd-fs User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.11-STABLE (i386)) Cc: Subject: Re: filesystem full - freebsd 5.3 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: Thu, 15 Dec 2005 16:41:57 -0000 Steven Hartland wrote: > Out of inodes? No. See the first message in this thread. 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. "The scanf() function is a large and complex beast that often does something almost but not quite entirely unlike what you desired." -- Chris Torek From owner-freebsd-fs@FreeBSD.ORG Thu Dec 15 18:52:38 2005 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 895C516A41F for ; Thu, 15 Dec 2005 18:52:38 +0000 (GMT) (envelope-from dworkin@village.org) Received: from green-dome.village.org (green-dome.village.org [168.103.84.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A26A43D5F for ; Thu, 15 Dec 2005 18:52:35 +0000 (GMT) (envelope-from dworkin@village.org) Received: from green-dome.village.org (localhost.village.org [127.0.0.1]) by green-dome.village.org (8.11.0/8.11.0) with ESMTP id jBFIqWm05440 for ; Thu, 15 Dec 2005 11:52:32 -0700 (MST) Message-Id: <200512151852.jBFIqWm05440@green-dome.village.org> To: freebsd-fs@freebsd.org From: dlm-fb@weaselfish.com In-reply-to: Your message of Thu, 15 Dec 2005 17:14:37 +0100 Date: Thu, 15 Dec 2005 11:52:32 -0700 Subject: Re: filesystem full - freebsd 5.3 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, 15 Dec 2005 18:52:38 -0000 Oliver Fromme wrote: : I considered mentioning the fragments issue, too, but I : don't think it applies in this case. His file system is : 22 Gbyte with 6 Gbyte free. I think it is very unlikely : that those 6 Gbyte are all fragments. I've had 100GB+ filesystems that were 50% full, and everything free was an isolated fragment (or short run but under the size of a block). Web caches, news, and similar small-file applications can be pretty pessimal for ufs, so mentioning the possibility seemed worthwhile. Dworkin From owner-freebsd-fs@FreeBSD.ORG Fri Dec 16 11:15:23 2005 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 78BB516A41F; Fri, 16 Dec 2005 11:15:23 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id B731F43D5A; Fri, 16 Dec 2005 11:15:22 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 815E7440CE; Fri, 16 Dec 2005 12:15:21 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14955-03; Fri, 16 Dec 2005 12:15:20 +0100 (CET) Received: from m2a2.dyndns.org (p50912389.dip0.t-ipconnect.de [80.145.35.137]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id CB259440A4; Fri, 16 Dec 2005 12:15:19 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 2EECB20094B; Fri, 16 Dec 2005 12:15:19 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29815-14; Fri, 16 Dec 2005 12:15:17 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 2772D200EAA; Fri, 16 Dec 2005 12:15:17 +0100 (CET) From: Matthias Andree To: Craig Rodrigues In-Reply-To: <20051213151908.GA26821@crodrigues.org> (Craig Rodrigues's message of "Tue, 13 Dec 2005 10:19:08 -0500") References: <20051213151908.GA26821@crodrigues.org> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Fri, 16 Dec 2005 12:15:17 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at dt.e-technik.uni-dortmund.de Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: XFS (read-only) support committed to CURRENT 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, 16 Dec 2005 11:15:23 -0000 Craig Rodrigues writes: > Read-only XFS support has been committed to FreeBSD-CURRENT. > Write access to XFS is not supported at this time. > The XFS for FreeBSD source code is based off of GPL'd sources > provided by SGI. Hm. Does this mean that FreeBSD's XFS implementation is GPL'd like ext2fs is? If so, allow me a question why XFS was chosen in preference to ext3fs? Ext3fs appears to have some advantages, easy migration from and to ext2fs, shrinkable, data journalling, data ordering (write data blocks before the file metadata is written) and so on. I don't mean this should become an advocacy discussion, as XFS surely has advantages, too, real-time capability and so on - but ext2fs is already there and has write support. Just curious. -- Matthias Andree From owner-freebsd-fs@FreeBSD.ORG Fri Dec 16 12:34:33 2005 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 ABBDF16A422 for ; Fri, 16 Dec 2005 12:34:33 +0000 (GMT) (envelope-from lerik@nolink.net) Received: from electra.nolink.net (electra.nolink.net [195.139.204.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65B8C43D78 for ; Fri, 16 Dec 2005 12:34:25 +0000 (GMT) (envelope-from lerik@nolink.net) Received: (qmail 50431 invoked by uid 1000); 16 Dec 2005 12:34:23 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 16 Dec 2005 12:34:23 -0000 Date: Fri, 16 Dec 2005 13:34:23 +0100 (CET) From: Lars Erik Gullerud To: Matthias Andree In-Reply-To: Message-ID: <20051216132641.C29205@electra.nolink.net> References: <20051213151908.GA26821@crodrigues.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: XFS (read-only) support committed to CURRENT 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, 16 Dec 2005 12:34:33 -0000 On Fri, 16 Dec 2005, Matthias Andree wrote: > Craig Rodrigues writes: > >> Read-only XFS support has been committed to FreeBSD-CURRENT. >> Write access to XFS is not supported at this time. >> The XFS for FreeBSD source code is based off of GPL'd sources >> provided by SGI. > > Hm. Does this mean that FreeBSD's XFS implementation is GPL'd like > ext2fs is? If so, allow me a question why XFS was chosen in preference > to ext3fs? What do you mean by "chosen in preference to", the two are hardly mutually exclusive...? UFS2 is still FreeBSD's native filesystem, however FreeBSD also supports handling a range of other filesystems like ext2fs, NTFS, etc. - and now also XFS. If you happen to want/need ext3fs more than XFS then you can always add the required bits yourself and send patches, or pay someone to do it? Someone wanted XFS support, so someone went ahead and worked on it - not to the exclusion of any other filesystem that anyone else might want/need support for... > Ext3fs appears to have some advantages, easy migration from and to > ext2fs, shrinkable, data journalling, data ordering (write data blocks > before the file metadata is written) and so on. ...and this has what to do with the fact that FreeBSD now supports XFS? > I don't mean this should become an advocacy discussion, as XFS surely > has advantages, too, real-time capability and so on - but ext2fs is > already there and has write support. Then use ext2fs. Isn't the availability of multiple choices great? /leg From owner-freebsd-fs@FreeBSD.ORG Fri Dec 16 15:07:54 2005 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 117B916A41F for ; Fri, 16 Dec 2005 15:07:54 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from wjv.com (fl-65-40-24-38.sta.sprint-hsd.net [65.40.24.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4739443D58 for ; Fri, 16 Dec 2005 15:07:52 +0000 (GMT) (envelope-from bv@bilver.wjv.com) Received: from bilver.wjv.com (localhost.wjv.com [127.0.0.1]) by wjv.com (8.13.5/8.13.1) with ESMTP id jBGF7peN044129 for ; Fri, 16 Dec 2005 10:07:51 -0500 (EST) (envelope-from bv@bilver.wjv.com) Received: (from bv@localhost) by bilver.wjv.com (8.13.5/8.13.1/Submit) id jBGF7fYk044128 for freebsd-fs@freebsd.org; Fri, 16 Dec 2005 10:07:41 -0500 (EST) (envelope-from bv) Date: Fri, 16 Dec 2005 10:07:41 -0500 From: Bill Vermillion To: freebsd-fs@freebsd.org Message-ID: <20051216150741.GA43981@wjv.com> References: <20051213151908.GA26821@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: W.J.Vermillion / Orlando - Winter Park ReplyTo: bv@wjv.com User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-3.8 required=5.0 tests=ALL_TRUSTED,BAYES_00, J_CHICKENPOX_32 autolearn=ham version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on bilver.wjv.com Subject: Re: XFS (read-only) support committed to CURRENT 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: Fri, 16 Dec 2005 15:07:54 -0000 At Fri, Dec 16, 2005 at 12:15 , our malformed and occasionally flatulent friend Matthias Andree spewed forth this fount of brain juice: > Craig Rodrigues writes: > > Read-only XFS support has been committed to FreeBSD-CURRENT. > > Write access to XFS is not supported at this time. > > The XFS for FreeBSD source code is based off of GPL'd sources > > provided by SGI. > Hm. Does this mean that FreeBSD's XFS implementation is GPL'd like > ext2fs is? If so, allow me a question why XFS was chosen in preference > to ext3fs? > Ext3fs appears to have some advantages, easy migration from and to > ext2fs, shrinkable, data journalling, data ordering (write data blocks > before the file metadata is written) and so on. > I don't mean this should become an advocacy discussion, as XFS surely > has advantages, too, real-time capability and so on - but ext2fs is > already there and has write support. If you check back far enough you'll see the XFS originally came from SGI and was optimized for exceptionally large file systems and had exceptionally high performance capabililites. As I recall it was out long before ext3fs and was it was probably close to 3 or 4 years before SGI changed platforms and also implemented XFS for Linux. ISTR it came out with the IRIX 6.x system. Tests they made with over a million files in a directory showed almost no perormance hits and block sizes over a megabyte long made it ideal for the targest SGI was using as that time - such as real time video streaming - such as the experimental Time/Warner experiment here locally. The 2TB storage they had online at that time was huge - and that was almost 10 years ago. This comment is in addtion to the ones others have made. Bill -- Bill Vermillion - bv @ wjv . com From owner-freebsd-fs@FreeBSD.ORG Fri Dec 16 15:12:53 2005 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 3CD1C16A420; Fri, 16 Dec 2005 15:12:53 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from rwcrmhc12.comcast.net (rwcrmhc14.comcast.net [216.148.227.89]) by mx1.FreeBSD.org (Postfix) with ESMTP id 589A143D68; Fri, 16 Dec 2005 15:12:31 +0000 (GMT) (envelope-from rodrigc@crodrigues.org) Received: from c-24-63-58-245.hsd1.ma.comcast.net ([24.63.58.245]) by comcast.net (rwcrmhc14) with ESMTP id <20051216151221014008mjnje>; Fri, 16 Dec 2005 15:12:22 +0000 Received: from c-24-63-58-245.hsd1.ma.comcast.net (localhost [127.0.0.1]) by c-24-63-58-245.hsd1.ma.comcast.net (8.13.4/8.13.1) with ESMTP id jBGFCTaB034694; Fri, 16 Dec 2005 10:12:29 -0500 (EST) (envelope-from rodrigc@c-24-63-58-245.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-24-63-58-245.hsd1.ma.comcast.net (8.13.4/8.13.1/Submit) id jBGFCT4r034693; Fri, 16 Dec 2005 10:12:29 -0500 (EST) (envelope-from rodrigc) Date: Fri, 16 Dec 2005 10:12:28 -0500 From: Craig Rodrigues To: Matthias Andree Message-ID: <20051216151228.GA34670@crodrigues.org> References: <20051213151908.GA26821@crodrigues.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 Subject: Re: XFS (read-only) support committed to CURRENT 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, 16 Dec 2005 15:12:53 -0000 On Fri, Dec 16, 2005 at 12:15:17PM +0100, Matthias Andree wrote: > Hm. Does this mean that FreeBSD's XFS implementation is GPL'd like > ext2fs is? If so, allow me a question why XFS was chosen in preference > to ext3fs? Your comment makes no sense. What does being GPL have to do with choosing ext2fs vs. XFS? We ported XFS to FreeBSD because we felt like it, and it was fun. ext3fs is irrelevant. -- Craig Rodrigues rodrigc@crodrigues.org From owner-freebsd-fs@FreeBSD.ORG Fri Dec 16 18:41:34 2005 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 DB96416A41F; Fri, 16 Dec 2005 18:41:34 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CEA343D58; Fri, 16 Dec 2005 18:41:24 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id jBGIfC9l066308; Fri, 16 Dec 2005 10:41:12 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id jBGIfBDB066307; Fri, 16 Dec 2005 10:41:11 -0800 (PST) (envelope-from jmg) Date: Fri, 16 Dec 2005 10:41:11 -0800 From: John-Mark Gurney To: Matthias Andree Message-ID: <20051216184111.GG55657@funkthat.com> Mail-Followup-To: Matthias Andree , Craig Rodrigues , freebsd-fs@freebsd.org, freebsd-current@freebsd.org References: <20051213151908.GA26821@crodrigues.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 X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: XFS (read-only) support committed to CURRENT X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2005 18:41:35 -0000 Matthias Andree wrote this message on Fri, Dec 16, 2005 at 12:15 +0100: > Craig Rodrigues writes: > > > Read-only XFS support has been committed to FreeBSD-CURRENT. > > Write access to XFS is not supported at this time. > > The XFS for FreeBSD source code is based off of GPL'd sources > > provided by SGI. > > Hm. Does this mean that FreeBSD's XFS implementation is GPL'd like > ext2fs is? You could of just looked at the source code yourself: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/gnu/fs/xfs/xfs_cap.c?rev=1.1&content-type=text/x-cvsweb-markup (And for the others, yes it is GPL'd) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-fs@FreeBSD.ORG Sat Dec 17 14:16:10 2005 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 8D1E316A41F for ; Sat, 17 Dec 2005 14:16:10 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 4582B43D67 for ; Sat, 17 Dec 2005 14:16:06 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 17 Dec 2005 14:16:02 -0000 Received: from p509137D6.dip0.t-ipconnect.de (EHLO merlin) [80.145.55.214] by mail.gmx.net (mp036) with SMTP; 17 Dec 2005 15:16:02 +0100 X-Authenticated: #428038 Date: Sat, 17 Dec 2005 15:15:28 +0100 From: Matthias Andree To: Lars Erik Gullerud Message-ID: <20051217141528.GB27992@merlin.emma.line.org> Mail-Followup-To: Lars Erik Gullerud , Craig Rodrigues , freebsd-fs@freebsd.org, freebsd-current@freebsd.org References: <20051213151908.GA26821@crodrigues.org> <20051216132641.C29205@electra.nolink.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051216132641.C29205@electra.nolink.net> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc User-Agent: Mutt/1.5.11 X-Y-GMX-Trusted: 0 Cc: freebsd-fs@freebsd.org, Matthias Andree , freebsd-current@freebsd.org Subject: Re: XFS (read-only) support committed to CURRENT 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, 17 Dec 2005 14:16:10 -0000 On Fri, 16 Dec 2005, Lars Erik Gullerud wrote: > >Ext3fs appears to have some advantages, easy migration from and to > >ext2fs, shrinkable, data journalling, data ordering (write data blocks > >before the file metadata is written) and so on. > > ...and this has what to do with the fact that FreeBSD now supports XFS? I was wondering if the way from ext2fs to ext3fs might have been shorter, code-wise. I will skip lots of good points in defense of XFS, and I really don't mind it being supported by XFS (in fact I'm looking forward to write support). > >I don't mean this should become an advocacy discussion, as XFS surely > >has advantages, too, real-time capability and so on - but ext2fs is > >already there and has write support. > > Then use ext2fs. Isn't the availability of multiple choices great? Yes, it is :-) -- Matthias Andree