From owner-freebsd-fs@FreeBSD.ORG Sun Dec 18 07:55: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 3766416A41F for ; Sun, 18 Dec 2005 07:55:45 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B5CE43D58 for ; Sun, 18 Dec 2005 07:55:43 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so723360wxc for ; Sat, 17 Dec 2005 23:55:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XBPCBeO7Co3KxUguEbIvuWF6l1qnibSdPmyEUrpBxKr9mzRQZXqeADU45RvaEIY6GHwYYb1g1Yrw4eUQqGxno2O2nZMeKJKTX+4Dm0hcQssjuJ5VfaQMonFL3QWI/Nz8RLzcMWWiBACaL27ivyj++V8ynXBwHOwh0dYZ4NQA1XY= Received: by 10.70.99.11 with SMTP id w11mr3102142wxb; Sat, 17 Dec 2005 23:55:43 -0800 (PST) Received: by 10.70.128.11 with HTTP; Sat, 17 Dec 2005 23:55:43 -0800 (PST) Message-ID: <2b22951e0512172355k36a579f4i42dd72562a3530ed@mail.gmail.com> Date: Sat, 17 Dec 2005 23:55:43 -0800 From: "Cai, Quanqing" To: freebsd-current@freebsd.org, Matthias Andree , Craig Rodrigues In-Reply-To: <20051217141647.GC27992@merlin.emma.line.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051213151908.GA26821@crodrigues.org> <20051216151228.GA34670@crodrigues.org> <20051217141647.GC27992@merlin.emma.line.org> Cc: freebsd-fs@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: Sun, 18 Dec 2005 07:55:45 -0000 On 12/17/05, Matthias Andree wrote: > On Fri, 16 Dec 2005, Craig Rodrigues wrote: > > > 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. [...] > > That's a compelling reason. Seriously. No offense, you could port ext3 too if you like... My company has 20s nfs servers(6 250G RAID 1 units), currently use SuSE9 w/XFS. I used ext3 on some but got long time fsck headache(Yes, I have data=3Djournal in fstab, but journal will fail under heavy load). So personally I prefer XFS. BTW, thank Craig Rodrigues, Alexander Kabaev, Russell Cattelan and all others for porting XFS to FreeBSD, it's a good news for community. We need a journal FS on FreeBSD so badly! Cai, Quanqing From owner-freebsd-fs@FreeBSD.ORG Sun Dec 18 09:25:31 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 2207716A41F; Sun, 18 Dec 2005 09:25:31 +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 15F3E43D45; Sun, 18 Dec 2005 09:25:29 +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 8DDDA44129; Sun, 18 Dec 2005 10:25:28 +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 13716-05; Sun, 18 Dec 2005 10:25:27 +0100 (CET) Received: from m2a2.dyndns.org (p50911889.dip0.t-ipconnect.de [80.145.24.137]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id C9F2E440A8; Sun, 18 Dec 2005 10:25:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id EED9F200717; Sun, 18 Dec 2005 10:25:25 +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 00415-06; Sun, 18 Dec 2005 10:25:23 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id D4FAA200A39; Sun, 18 Dec 2005 10:25:23 +0100 (CET) Date: Sun, 18 Dec 2005 10:25:23 +0100 From: Matthias Andree To: "Cai, Quanqing" Message-ID: <20051218092523.GA4694@merlin.emma.line.org> Mail-Followup-To: "Cai, Quanqing" , freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <20051213151908.GA26821@crodrigues.org> <20051216151228.GA34670@crodrigues.org> <20051217141647.GC27992@merlin.emma.line.org> <2b22951e0512172355k36a579f4i42dd72562a3530ed@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b22951e0512172355k36a579f4i42dd72562a3530ed@mail.gmail.com> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc User-Agent: Mutt/1.5.11 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: Sun, 18 Dec 2005 09:25:31 -0000 On Sat, 17 Dec 2005, Cai, Quanqing wrote: > On 12/17/05, Matthias Andree wrote: > > On Fri, 16 Dec 2005, Craig Rodrigues wrote: > > > > > 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. [...] > > > > That's a compelling reason. Seriously. > > No offense, you could port ext3 too if you like... > > My company has 20s nfs servers(6 250G RAID 1 units), currently use > SuSE9 w/XFS. I used ext3 on some but got long time fsck headache(Yes, > I have data=journal in fstab, but journal will fail under heavy load). > So personally I prefer XFS. Failing journals are either I/O errors (dying hard disk drive) or otherwise Linux kernel bugs. I have not yet seen ext3fs + NFS (or only the journals) break under load (SUSE 9.2 and 10.0) for any other reason than a broken drive or broken cables. If you have a workload that reproduces the problem, report it to SUSE. OTOH, it's "only" one Xeon NFS server with 1 70 GB RAID5 and 1 292 GB RAID5 (MegaRAID SCSI 320-1 with BBU) with half a dozen users at any one time. > BTW, thank Craig Rodrigues, Alexander Kabaev, Russell Cattelan and all > others for porting XFS to FreeBSD, it's a good news for community. We > need a journal FS on FreeBSD so badly! :-) -- Matthias Andree From owner-freebsd-fs@FreeBSD.ORG Sun Dec 18 10:02:43 2005 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3FEC916A41F; Sun, 18 Dec 2005 10:02:40 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43A533E9.8010901@freebsd.org> Date: Sun, 18 Dec 2005 18:03:21 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Craig Rodrigues References: <20051213151908.GA26821@crodrigues.org> <20051216151228.GA34670@crodrigues.org> In-Reply-To: <20051216151228.GA34670@crodrigues.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: Sun, 18 Dec 2005 10:02:43 -0000 Craig Rodrigues wrote: >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. > > > I would like to see writable XFS, this gives us another FS option, how diffcult would it be? :-) From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 07:48:41 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 28D3C16A41F for ; Mon, 19 Dec 2005 07:48:41 +0000 (GMT) (envelope-from namondo@gmail.com) Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67D4C43D5A for ; Mon, 19 Dec 2005 07:48:40 +0000 (GMT) (envelope-from namondo@gmail.com) Received: by nproxy.gmail.com with SMTP id p48so364893nfa for ; Sun, 18 Dec 2005 23:48:39 -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=li0a7MyB+9oNk6EhUJJsOgafkM3ugvzxr7q1yPZnEZUYbkYkjcHjcMasIu5cjsKu979d16pDkkkD0en/rmAlUtz6q/rkXLXdGLvuQz8uq4r1fwbyn0BF2qX9YvC8Vbq8p9ATJin0qEgOG+J+LmoS6+dtR7jbfegTXH6dhDMgPbk= Received: by 10.48.219.18 with SMTP id r18mr231695nfg; Sun, 18 Dec 2005 23:48:38 -0800 (PST) Received: by 10.48.213.13 with HTTP; Sun, 18 Dec 2005 23:48:38 -0800 (PST) Message-ID: <18eab3b50512182348j72f95315x@mail.gmail.com> Date: Mon, 19 Dec 2005 08:48:38 +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: Mon, 19 Dec 2005 07:48:41 -0000 Oliver Fromme wrote: : t c < namondo@gmail.com> 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 ful= l : > (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 This version seems more likely for me. Unfortunatly I can't read the output of dumpfs. I tried to post, but my message was 'moderated', so I put that output on this page: http://dumpfs.szellem.org ct From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 12:20: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 3559D16A420 for ; Mon, 19 Dec 2005 12:20:19 +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 3B59543D69 for ; Mon, 19 Dec 2005 12:20:16 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (rytytm@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBJCKDch037707 for ; Mon, 19 Dec 2005 13:20: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 jBJCKDI8037706; Mon, 19 Dec 2005 13:20:13 +0100 (CET) (envelope-from olli) Date: Mon, 19 Dec 2005 13:20:13 +0100 (CET) Message-Id: <200512191220.jBJCKDI8037706@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <18eab3b50512182348j72f95315x@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: Mon, 19 Dec 2005 12:20:19 -0000 [broken quoting recovered] t c wrote: > Dworking wrote: > > Oliver Fromme wrote: > > : t c < namondo@gmail.com> 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 > > This version seems more likely for me. In the situation give, I think it is rather unlikely. > Unfortunatly I can't read the output > of dumpfs. I tried to post, but my message was 'moderated', so I put that > output on this page: > http://dumpfs.szellem.org You have plenty of blocks free. By the way, you have minfree set to 0%. That's usually not a good idea on general-purpose file systems for multiple users such as /home, and it degrades performance significantly. 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. "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Doug Gwyn From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 12:32:28 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 3DECB16A41F for ; Mon, 19 Dec 2005 12:32:28 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from imap1u.univie.ac.at (murder.univie.ac.at [131.130.1.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99E2143D49 for ; Mon, 19 Dec 2005 12:32:27 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by imap1u.univie.ac.at (8.12.10/8.12.10) with ESMTP id jBJCVt4U020259 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Dec 2005 13:31:56 +0100 (CET) Date: Mon, 19 Dec 2005 13:31:55 +0100 (CET) From: Lukas Ertl To: freebsd-fs@FreeBSD.org In-Reply-To: <200512191220.jBJCKDI8037706@lurza.secnetix.de> Message-ID: <20051219132739.R28071@pcle2.cc.univie.ac.at> References: <200512191220.jBJCKDI8037706@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Mon, 19 Dec 2005 12:32:28 -0000 On Mon, 19 Dec 2005, Oliver Fromme wrote: > > > 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. > > > > This version seems more likely for me. > > In the situation give, I think it is rather unlikely. We have to cope with the same problem here. It's a 662GB filesystem used for Cyrus imapd mail folders. 55GB free space, plenty of free inodes, and yet we get "filesystem full" messages. If we remove some mail folders (postmaster double bounce stuff, thousands of mails per dir), the kernel stops complaining about a full filesystem (until it runs out of $factor_x again). We are now moving to a new machine, where we will split up the large filesystem to smaller ones. regards, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 13:17:30 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 BCC7B16A41F; Mon, 19 Dec 2005 13:17:30 +0000 (GMT) (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 46D5443D79; Mon, 19 Dec 2005 13:17:16 +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 jBJDHGhl052885; Mon, 19 Dec 2005 07:17:16 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43A6B2D8.8000907@centtech.com> Date: Mon, 19 Dec 2005 07:17:12 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lukas Ertl References: <200512191220.jBJCKDI8037706@lurza.secnetix.de> <20051219132739.R28071@pcle2.cc.univie.ac.at> In-Reply-To: <20051219132739.R28071@pcle2.cc.univie.ac.at> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1212/Sun Dec 18 05:09:50 2005 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-fs@freebsd.org 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: Mon, 19 Dec 2005 13:17:30 -0000 Lukas Ertl wrote: > On Mon, 19 Dec 2005, Oliver Fromme wrote: > >> > > 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. >> > >> > This version seems more likely for me. >> >> In the situation give, I think it is rather unlikely. > > > We have to cope with the same problem here. It's a 662GB filesystem > used for Cyrus imapd mail folders. 55GB free space, plenty of free > inodes, and yet we get "filesystem full" messages. If we remove some > mail folders (postmaster double bounce stuff, thousands of mails per > dir), the kernel stops complaining about a full filesystem (until it > runs out of $factor_x again). > > We are now moving to a new machine, where we will split up the large > filesystem to smaller ones. This is interesting - can you touch a new file? Also, can you post (http please) your dumpfs output also? I realize it might be large. The most interesting pieces to me are the superblock and cylindar summary info, plus maybe the first 100 cylindar group info. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 14:00:49 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 44ED516A422 for ; Mon, 19 Dec 2005 14:00:49 +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 CE2BE43D7B for ; Mon, 19 Dec 2005 14:00:46 +0000 (GMT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ojuzmj@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id jBJE0iUh041744 for ; Mon, 19 Dec 2005 15:00:45 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id jBJE0iNM041742; Mon, 19 Dec 2005 15:00:44 +0100 (CET) (envelope-from olli) Date: Mon, 19 Dec 2005 15:00:44 +0100 (CET) Message-Id: <200512191400.jBJE0iNM041742@lurza.secnetix.de> From: Oliver Fromme To: freebsd-fs@FreeBSD.ORG In-Reply-To: <20051219132739.R28071@pcle2.cc.univie.ac.at> 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: Mon, 19 Dec 2005 14:00:49 -0000 Lukas Ertl wrote: > We have to cope with the same problem here. It's a 662GB filesystem used > for Cyrus imapd mail folders. 55GB free space, plenty of free inodes, and > yet we get "filesystem full" messages. If we remove some mail folders > (postmaster double bounce stuff, thousands of mails per dir), the kernel > stops complaining about a full filesystem (until it runs out of $factor_x > again). For an application like that (mail server), it might be beneficial to create the file system with bsize == fsize (e.g. both 8 kbyte), so you won't get any fragments at all. On a related note, many people seem to set minfree to 0%, in order to squeeze more space from the disk. That's almost always a mistake, because it increases fragmentation considerably, especially if the file system has many small write operations, and it reduces performance significantly. 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. "I invented Ctrl-Alt-Delete, but Bill Gates made it famous." -- David Bradley, original IBM PC design team From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 15:00: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 BFDDC16A41F; Mon, 19 Dec 2005 15:00:57 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from pinus.cc.fer.hr (pinus.cc.fer.hr [161.53.73.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD72643D62; Mon, 19 Dec 2005 15:00:54 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [161.53.72.113] (lara.cc.fer.hr [161.53.72.113]) by pinus.cc.fer.hr (8.12.2/8.12.2) with ESMTP id jBJF0iFx020790; Mon, 19 Dec 2005 16:00:44 +0100 (MET) Message-ID: <43A6CACE.30902@fer.hr> Date: Mon, 19 Dec 2005 15:59:26 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthias Andree References: <20051213151908.GA26821@crodrigues.org> <20051216132641.C29205@electra.nolink.net> <20051217141528.GB27992@merlin.emma.line.org> In-Reply-To: <20051217141528.GB27992@merlin.emma.line.org> 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: 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: Mon, 19 Dec 2005 15:00:57 -0000 Matthias Andree wrote: > I was wondering if the way from ext2fs to ext3fs might have been > shorter, code-wise. For what it's worth, IIRC in Linux the code for ext3fs is separated from ext2fs - it's not handled by a bunch of #ifdefs but a separate (and much larger - IIRC at least 2x the code) codebase. From this I think that adding ext3 functionality to FreeBSD will also be similar - like a port of a completely different filesystem from scratch. From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 18:03:27 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 2092516A41F for ; Mon, 19 Dec 2005 18:03:27 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from imap1u.univie.ac.at (murder1.univie.ac.at [131.130.1.183]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83E6243D53 for ; Mon, 19 Dec 2005 18:03:26 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben (korben.prv.univie.ac.at [131.130.7.98]) by imap1u.univie.ac.at (8.12.10/8.12.10) with ESMTP id jBJI2H4U083014 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 19 Dec 2005 19:02:22 +0100 (CET) Date: Mon, 19 Dec 2005 19:02:17 +0100 From: Lukas Ertl To: Eric Anderson In-Reply-To: <43A6B2D8.8000907@centtech.com> Message-ID: References: <200512191220.jBJCKDI8037706@lurza.secnetix.de> <20051219132739.R28071@pcle2.cc.univie.ac.at> <43A6B2D8.8000907@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org 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: Mon, 19 Dec 2005 18:03:27 -0000 On Mon, 19 Dec 2005, Eric Anderson wrote: >> We have to cope with the same problem here. It's a 662GB filesystem used >> for Cyrus imapd mail folders. 55GB free space, plenty of free inodes, and >> yet we get "filesystem full" messages. If we remove some mail folders >> (postmaster double bounce stuff, thousands of mails per dir), the kernel >> stops complaining about a full filesystem (until it runs out of $factor_x >> again). >> > > This is interesting - can you touch a new file? Also, can you post (http > please) your dumpfs output also? I realize it might be large. I'm gonna have to wait until it happens again. > The most interesting pieces to me are the superblock and cylindar summary > info, plus maybe the first 100 cylindar group info. This was taken just now, and there are no "filesystem full" messages currently. regards, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 21:48:28 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 00EA416A41F for ; Mon, 19 Dec 2005 21:48:28 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C06043D7C for ; Mon, 19 Dec 2005 21:48:25 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so952068wxc for ; Mon, 19 Dec 2005 13:48:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PiI/kTy2aigrp+0teHpYb6RpVzE67eadRlaZjL2pwsXNp9rSjelaBryK9c3k+LAgZk6Y8+seZNp/Hfx5eZfF2Fi6XfVbmIrcWuYeAjlh4ehUyqM21yHAniCma5LtpjBGMzRO/oGV4p0iWPqrTIQ9vqey1NiDz4Lp51ApsgH6CvI= Received: by 10.70.98.11 with SMTP id v11mr5112932wxb; Mon, 19 Dec 2005 13:48:23 -0800 (PST) Received: by 10.70.128.11 with HTTP; Mon, 19 Dec 2005 13:48:23 -0800 (PST) Message-ID: <2b22951e0512191348t227c9354i36d6a4a87e7d5698@mail.gmail.com> Date: Mon, 19 Dec 2005 13:48:23 -0800 From: "Cai, Quanqing" To: freebsd-current@freebsd.org, freebsd-fs@freebsd.org, Matthias Andree In-Reply-To: <20051218092523.GA4694@merlin.emma.line.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051213151908.GA26821@crodrigues.org> <20051216151228.GA34670@crodrigues.org> <20051217141647.GC27992@merlin.emma.line.org> <2b22951e0512172355k36a579f4i42dd72562a3530ed@mail.gmail.com> <20051218092523.GA4694@merlin.emma.line.org> Cc: 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: Mon, 19 Dec 2005 21:48:28 -0000 On 12/18/05, Matthias Andree wrote: > On Sat, 17 Dec 2005, Cai, Quanqing wrote: > > > On 12/17/05, Matthias Andree wrote: > > > On Fri, 16 Dec 2005, Craig Rodrigues wrote: > > > > > > > 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. [...] > > > > > > That's a compelling reason. Seriously. > > > > No offense, you could port ext3 too if you like... > > > > My company has 20s nfs servers(6 250G RAID 1 units), currently use > > SuSE9 w/XFS. I used ext3 on some but got long time fsck headache(Yes, > > I have data=3Djournal in fstab, but journal will fail under heavy load)= . > > So personally I prefer XFS. > > Failing journals are either I/O errors (dying hard disk drive) or > otherwise Linux kernel bugs. I have not yet seen ext3fs + NFS (or only > the journals) break under load (SUSE 9.2 and 10.0) for any other reason > than a broken drive or broken cables. If you have a workload that > reproduces the problem, report it to SUSE. No, I don't have time to deal with SuSE regarding failure, the company I am working for is growing so fast, need to add dozens of servers every month. After switch to XFS, I seldom get problems, even if I got problem, I can quickly reboot nfs server because it is using XFS. > > OTOH, it's "only" one Xeon NFS server with 1 70 GB RAID5 and 1 292 GB > RAID5 (MegaRAID SCSI 320-1 with BBU) with half a dozen users at any one > time. Oh, you don't put much load on it. I am using nfs server as storage server of internet application, so they get very high IO load. > > BTW, thank Craig Rodrigues, Alexander Kabaev, Russell Cattelan and all > > others for porting XFS to FreeBSD, it's a good news for community. We > > need a journal FS on FreeBSD so badly! > > :-) > > -- > Matthias Andree > Anyway, I am not tend to start a flame war between ext3 and XFS, I choose ext3 for our MySQL server because MySQL.com suggest me that, they said ext3 has better performance. Sorry, this is out of topic:( Cai, Quanqing From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 21:55:58 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 07BAF16A41F; Mon, 19 Dec 2005 21:55:58 +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 23A5043D46; Mon, 19 Dec 2005 21:55:56 +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 D122344129; Mon, 19 Dec 2005 22:55:55 +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 01976-10; Mon, 19 Dec 2005 22:55:54 +0100 (CET) Received: from m2a2.dyndns.org (p5091366B.dip0.t-ipconnect.de [80.145.54.107]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 086A0440A8; Mon, 19 Dec 2005 22:55:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 538E7201F1F; Mon, 19 Dec 2005 22:55:53 +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 06378-10; Mon, 19 Dec 2005 22:55:51 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 4717B201F20; Mon, 19 Dec 2005 22:55:51 +0100 (CET) Date: Mon, 19 Dec 2005 22:55:51 +0100 From: Matthias Andree To: "Cai, Quanqing" Message-ID: <20051219215551.GA7362@merlin.emma.line.org> Mail-Followup-To: "Cai, Quanqing" , freebsd-current@freebsd.org, freebsd-fs@freebsd.org References: <20051213151908.GA26821@crodrigues.org> <20051216151228.GA34670@crodrigues.org> <20051217141647.GC27992@merlin.emma.line.org> <2b22951e0512172355k36a579f4i42dd72562a3530ed@mail.gmail.com> <20051218092523.GA4694@merlin.emma.line.org> <2b22951e0512191348t227c9354i36d6a4a87e7d5698@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2b22951e0512191348t227c9354i36d6a4a87e7d5698@mail.gmail.com> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc User-Agent: Mutt/1.5.11 X-Virus-Scanned: amavisd-new at dt.e-technik.uni-dortmund.de 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: Mon, 19 Dec 2005 21:55:58 -0000 On Mon, 19 Dec 2005, Cai, Quanqing wrote: > No, I don't have time to deal with SuSE regarding failure, the company > I am working for is growing so fast, need to add dozens of servers > every month. After switch to XFS, I seldom get problems, even if I got > problem, I can quickly reboot nfs server because it is using XFS. Well, you can switch off the routine full checks of ext3fs with tune2fs, should that matter for remaining ext3 file systems.s Without that full check every few weeks, you only have journal recovery, and that is pretty fast. The journal can be offloaded on a separate drive if desired. On the downside, ext3fs and write caches don't mix well, unless you have battery backup units sitting on your RAID controllers (I do, and switching this MegaRAID - RAID5 on 2+1 - to writeback mode improved write speed by a factor of 5 - no database loads though). > > OTOH, it's "only" one Xeon NFS server with 1 70 GB RAID5 and 1 292 GB > > RAID5 (MegaRAID SCSI 320-1 with BBU) with half a dozen users at any one > > time. > > Oh, you don't put much load on it. I am using nfs server as storage > server of internet application, so they get very high IO load. Yup. And personally, if I'd have any stakes in NFS load, I'd probably consider Solaris instead. Linux and NFS is pretty flakey for some, and some people claim only 2.6.11.11 were really stable, I always see tons of fixes for NFS :-/. Myself, I have little NFS troubles with SUSE 9.2 and 10.0, but things used to be worse. > Anyway, I am not tend to start a flame war between ext3 and XFS, I > choose ext3 for our MySQL server because MySQL.com suggest me that, > they said ext3 has better performance. Sorry, this is out of topic:( I'm taking this offline. MySQL is an area I don't know well, whenever I've wanted SQL, I've used SQLite3 or PostgreSQL, so I cannot comment on that. -- Matthias Andree From owner-freebsd-fs@FreeBSD.ORG Mon Dec 19 22:19:11 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 3465A16A420; Mon, 19 Dec 2005 22:19:11 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from lira.ugcs.caltech.edu (lira.ugcs.caltech.edu [131.215.176.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6361C43D64; Mon, 19 Dec 2005 22:19:10 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by lira.ugcs.caltech.edu (Postfix, from userid 3640) id 203416B002; Mon, 19 Dec 2005 14:19:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lira.ugcs.caltech.edu (Postfix) with ESMTP id C27525300A; Mon, 19 Dec 2005 14:19:08 -0800 (PST) Date: Mon, 19 Dec 2005 14:19:08 -0800 (PST) From: Jon Dama To: Matthias Andree In-Reply-To: <20051219215551.GA7362@merlin.emma.line.org> Message-ID: References: <20051213151908.GA26821@crodrigues.org> <20051216151228.GA34670@crodrigues.org> <20051217141647.GC27992@merlin.emma.line.org> <2b22951e0512172355k36a579f4i42dd72562a3530ed@mail.gmail.com> <20051218092523.GA4694@merlin.emma.line.org> <2b22951e0512191348t227c9354i36d6a4a87e7d5698@mail.gmail.com> <20051219215551.GA7362@merlin.emma.line.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-fs@freebsd.org, "Cai, Quanqing" , 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: Mon, 19 Dec 2005 22:19:11 -0000 > On the downside, ext3fs and write caches don't mix well, unless you have > battery backup units sitting on your RAID controllers (I do, and > switching this MegaRAID - RAID5 on 2+1 - to writeback mode improved > write speed by a factor of 5 - no database loads though). This an issue that Kirk has been looking into. Ideally the problem will go away completely when both request barriers and NCQ are implemented. (The latter for people with high-end SATA drives and the former for the rest of the consumers of ATA). -Jon From owner-freebsd-fs@FreeBSD.ORG Tue Dec 20 22:17:44 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 3ADC216A41F for ; Tue, 20 Dec 2005 22:17:44 +0000 (GMT) (envelope-from cell@games-for-you.net) Received: from games-for-you.net (POWER.BOUNCER2.games-for-you.net [67.43.232.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22B1A43D6A for ; Tue, 20 Dec 2005 22:17:29 +0000 (GMT) (envelope-from cell@games-for-you.net) Received: from nooty-booky (unverified [84.163.254.212]) by games-for-you.net (SurgeMail 3.0c2) with ESMTP id 45510 for ; Tue, 20 Dec 2005 17:53:30 -0400 From: "cell@games-for-you.net" To: freebsd-fs@freebsd.org MIME-Version: 1.0 Date: Tue, 20 Dec 2005 23:09:11 +0100 X-Server: High Performance Mail Server - http://surgemail.com Message-ID: <1135115610_42704@games-for-you.net> X-Authenticated-User: cell@games-for-you.net Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Just for you 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, 20 Dec 2005 22:17:44 -0000 - This mail is a HTML mail. Not all elements could be shown in plain = text mode. -