From owner-linux-xfs@oss.sgi.com Mon Aug 1 03:21:17 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Aug 2005 03:21:22 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j71ALGH9003148 for ; Mon, 1 Aug 2005 03:21:16 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [198.149.16.14]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j71AJFxT008748 for ; Mon, 1 Aug 2005 05:19:15 -0500 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.232.87]) by ledzep.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j71AJDsL19793819; Mon, 1 Aug 2005 05:19:13 -0500 (CDT) Received: from hch by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 1DzXO5-0003uS-00; Mon, 01 Aug 2005 05:19:13 -0500 To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Cc: victor@cetuc.puc-rio.br Subject: TAKE 940376 - Fix sparse warnings in kmem_* functions Message-Id: From: Christoph Hellwig Date: Mon, 01 Aug 2005 05:19:13 -0500 X-archive-position: 5701 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 788 Lines: 19 Patch from Victor Fusco Date: Mon Aug 1 03:18:54 PDT 2005 Workarea: maine.americas.sgi.com:/home/daisy40/hch/ptools/xfs-2.6.x Inspected by: victor@cetuc.puc-rio.br,domen@coderock.org The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:196705a fs/xfs/xfs_log_recover.c - 1.298 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_log_recover.c.diff?r1=text&tr1=1.298&r2=text&tr2=1.297&f=h fs/xfs/linux-2.6/kmem.h - 1.30 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/kmem.h.diff?r1=text&tr1=1.30&r2=text&tr2=1.29&f=h fs/xfs/linux-2.6/kmem.c - 1.4 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/kmem.c.diff?r1=text&tr1=1.4&r2=text&tr2=1.3&f=h From owner-linux-xfs@oss.sgi.com Mon Aug 1 08:22:28 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Aug 2005 08:22:33 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j71FMSH9029341 for ; Mon, 1 Aug 2005 08:22:28 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [198.149.16.15]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j71FKRxT031944 for ; Mon, 1 Aug 2005 10:20:27 -0500 Received: from [128.162.232.50] (stout.americas.sgi.com [128.162.232.50]) by flecktone.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j71FKQDN13380428 for ; Mon, 1 Aug 2005 10:20:27 -0500 (CDT) Message-ID: <42EE3DBA.7070009@sgi.com> Date: Mon, 01 Aug 2005 10:20:26 -0500 From: Eric Sandeen User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "'linux-xfs@oss.sgi.com'" Subject: [Announce] updated acl, attr, xfsprogs, xfsdump on oss Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5702 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 268 Lines: 16 I've rebuilt & placed updated acl, attr, xfsprogs, xfsdump packages on oss.sgi.com: ftp://oss.sgi.com/projects/xfs/download/cmd_tars/ ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ Versions: acl-2.2.31 attr-2.4.23 xfsdump-2.2.30 xfsprogs-2.6.36 Thanks, -Eric From owner-linux-xfs@oss.sgi.com Mon Aug 1 08:30:21 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Aug 2005 08:30:25 -0700 (PDT) Received: from mail.linux-sxs.org (mail.linux-sxs.org [64.116.183.6]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j71FUKH9030000 for ; Mon, 1 Aug 2005 08:30:21 -0700 Received: from mail.linux-sxs.org (localhost [127.0.0.1]) by mail.linux-sxs.org (8.13.4/8.13.4/Debian-3) with ESMTP id j71EPi0P014246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 1 Aug 2005 09:25:45 -0500 Received: from localhost (netllama@localhost) by mail.linux-sxs.org (8.13.4/8.13.4/Submit) with ESMTP id j71EPhat014243; Mon, 1 Aug 2005 09:25:44 -0500 X-Authentication-Warning: mail.linux-sxs.org: netllama owned process doing -bs Date: Mon, 1 Aug 2005 09:25:43 -0500 (EST) From: Lonni J Friedman To: Eric Sandeen cc: "'linux-xfs@oss.sgi.com'" Subject: Re: [Announce] updated acl, attr, xfsprogs, xfsdump on oss In-Reply-To: <42EE3DBA.7070009@sgi.com> Message-ID: References: <42EE3DBA.7070009@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: milter-sender/0.62.837 (localhost [127.0.0.1]); Mon, 01 Aug 2005 09:25:45 -0500 Received-SPF: pass (mail.linux-sxs.org: domain of netllama@linux-sxs.org designates 127.0.0.1 as permitted sender) receiver=mail.linux-sxs.org; client-ip=127.0.0.1; helo=mail.linux-sxs.org; envelope-from=netllama@linux-sxs.org; x-software=spfmilter 0.95 http://www.acme.com/software/spfmilter/ with libspf2; X-archive-position: 5703 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 573 Lines: 27 Any notable changes/improvements in these versions? On Mon, 1 Aug 2005, Eric Sandeen wrote: > I've rebuilt & placed updated acl, attr, xfsprogs, xfsdump packages on oss.sgi.com: > > ftp://oss.sgi.com/projects/xfs/download/cmd_tars/ > ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ > > Versions: > > acl-2.2.31 > attr-2.4.23 > xfsdump-2.2.30 > xfsprogs-2.6.36 > > Thanks, > > -Eric > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org LlamaLand http://netllama.linux-sxs.org From owner-linux-xfs@oss.sgi.com Mon Aug 1 08:40:24 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Aug 2005 08:40:27 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j71FeOH9030902 for ; Mon, 1 Aug 2005 08:40:24 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [198.149.16.14]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j71HY6aq012193 for ; Mon, 1 Aug 2005 10:34:06 -0700 Received: from [128.162.232.50] (stout.americas.sgi.com [128.162.232.50]) by ledzep.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j71FcMsL19806684; Mon, 1 Aug 2005 10:38:22 -0500 (CDT) Message-ID: <42EE41EE.1020200@sgi.com> Date: Mon, 01 Aug 2005 10:38:22 -0500 From: Eric Sandeen User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lonni J Friedman CC: "'linux-xfs@oss.sgi.com'" Subject: Re: [Announce] updated acl, attr, xfsprogs, xfsdump on oss References: <42EE3DBA.7070009@sgi.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5704 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 775 Lines: 35 Lonni J Friedman wrote: > Any notable changes/improvements in these versions? It's all in the changelogs :) http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/doc/CHANGES?rev=1.78 http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/doc/CHANGES?rev=1.61 http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/doc/CHANGES?rev=1.78 http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/doc/CHANGES?rev=1.174 -Eric > On Mon, 1 Aug 2005, Eric Sandeen wrote: > > >>I've rebuilt & placed updated acl, attr, xfsprogs, xfsdump packages on oss.sgi.com: >> >>ftp://oss.sgi.com/projects/xfs/download/cmd_tars/ >>ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ >> >>Versions: >> >>acl-2.2.31 >>attr-2.4.23 >>xfsdump-2.2.30 >>xfsprogs-2.6.36 >> >>Thanks, >> >>-Eric >> >> > > From owner-linux-xfs@oss.sgi.com Tue Aug 2 05:14:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Aug 2005 05:15:03 -0700 (PDT) Received: from strike.wu-wien.ac.at (strike.wu-wien.ac.at [137.208.8.200]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j72CEwH9009211 for ; Tue, 2 Aug 2005 05:14:59 -0700 Received: from localhost (localhost.localdomain [127.0.0.1]) by strike.wu-wien.ac.at (Postfix) with ESMTP id 9D5B52000F2; Tue, 2 Aug 2005 14:12:48 +0200 (CEST) Received: from strike.wu-wien.ac.at ([127.0.0.1]) by localhost (strike.wu-wien.ac.at [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 08975-04-3; Tue, 2 Aug 2005 14:12:44 +0200 (CEST) Received: from [137.208.89.100] (ariel.wu-wien.ac.at [137.208.89.100]) by strike.wu-wien.ac.at (Postfix) with ESMTP id 729762000F1; Tue, 2 Aug 2005 14:12:44 +0200 (CEST) Message-ID: <42EF633D.9030005@strike.wu-wien.ac.at> Date: Tue, 02 Aug 2005 14:12:45 +0200 From: Alexander Bergolth User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc3 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: wu.mail.sys.linux.xfs To: Nathan Scott Cc: Joshua Baker-LePain , Steve Lord , Linux xfs mailing list Subject: Re: XFS, 4K stacks, and Red Hat References: <42CD4D38.1090703@xfs.org> <20050708043740.GB1679@frodo> <42D3F44B.308@strike.wu-wien.ac.at> <20050713015626.GD980@frodo> In-Reply-To: <20050713015626.GD980@frodo> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-archive-position: 5705 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: leo@strike.wu-wien.ac.at Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1066 Lines: 30 On 07/13/2005 03:56 AM, Nathan Scott wrote: > On Tue, Jul 12, 2005 at 06:48:11PM +0200, Alexander Bergolth wrote: >>On 07/08/2005 06:37 AM, Nathan Scott wrote: >>>... >>>As other cases pop up (with a reproducible test case please, and >>>no stacking drivers in the way too :), we slowly iron them out.. > ^^^^^^^^^^^^^^^^^^^^^^^^^^ > > *cough* > >>I'm getting frequent stack overflows on one system, using xfs, lvm2, >>sw-raid and libata but I don't know, if they are XFS-related. > > Hmmm - xfs on lvm on md on ide ...? Looks like its death by > a thousand cuts.. thats the sort of case Steve keeps talking > about. You will be able to crash using any filesystem doing > this, eventually - and we haven't even got NFS in the picture > here yet. > > ( Maybe you can do away with one of device mapper / MD here? ) I've switched to linuxant's 16k stack kernels for fedora and the machine didn't crash any more. (Although an 8k stack would probably have been enough.) http://www.linuxant.com/driverloader/wlan/full/downloads-fc3-kernel-i686.php Cheers, --leo From owner-linux-xfs@oss.sgi.com Wed Aug 3 00:23:54 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 00:23:59 -0700 (PDT) Received: from pingus.pingus.org (pingus.pingus.org [82.66.123.179]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j737NqH9031235 for ; Wed, 3 Aug 2005 00:23:53 -0700 Received: from www.pingus.org (localhost [127.0.0.1]) by pingus.pingus.org (Postfix) with ESMTP id 62C463FC6E for ; Wed, 3 Aug 2005 09:21:49 +0200 (CEST) Received: from 194.2.155.29 (SquirrelMail authenticated user brice) by www.pingus.org with HTTP; Wed, 3 Aug 2005 09:21:49 +0200 (CEST) Message-ID: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org> Date: Wed, 3 Aug 2005 09:21:49 +0200 (CEST) Subject: XFS trouble. From: "Brice GIBOUDEAU" To: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5706 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: brice@pingus.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1503 Lines: 38 Hi, I have a Linux (Debian Sarge) server with more than 4Gb of memory, I'm running XFS on other servers for a long time without any problem. (Less or equal to 4Gb of memory) Actually i'm using 2.4.31 kernel, when i add PEA (64Gb of memory) in my kernel i have a memory leak when i'm working on XFS File system. Exemple : --------- I have 2 volumes (/xfs1 & /xfs2) of 1TB with million of small files on /xfs1, i trie to make a backup of file from /xfs1 to /xfs2 (tar -cvf /xfs2/backup.tar /xfs1), after several minutes the memory is full, and i get this messages : -> kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) -> kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) -> kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) -> kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) -> kernel: __alloc_pages: 1-order allocation failed (gfp=0x1f0/0) -> kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) -> kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) -> kswapd/bdflush is using full CPU -> Swap use = 0 If i rebuild my kernel with the "High Memory Support" to 4Go (or less) everything is fine, backup process and system is working for many many days without any error message. Somebody have a solution, or i must switch to an other file system ti use all my memory ? Thanks, Brice GIBOUDEAU PS : The server with more than 4Gb of memory is an HP DL580 with 2 MSA30 and a 4 Channel Smart Array Raid Controler. From owner-linux-xfs@oss.sgi.com Wed Aug 3 01:58:33 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 01:58:38 -0700 (PDT) Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j738wVH9004864 for ; Wed, 3 Aug 2005 01:58:32 -0700 Received: from mailgate3.nec.co.jp (mailgate53.nec.co.jp [10.7.69.161] (may be forged)) by tyo201.gate.nec.co.jp (8.11.7/3.7W01080315) with ESMTP id j738uOE14448 for ; Wed, 3 Aug 2005 17:56:24 +0900 (JST) Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id j738uOY12750 for linux-xfs@oss.sgi.com; Wed, 3 Aug 2005 17:56:24 +0900 (JST) Received: from secsv2.tnes.nec.co.jp (tnesvc1.tnes.nec.co.jp [10.1.101.14]) by mailsv4.nec.co.jp (8.11.7/3.7W-MAILSV4-NEC) with ESMTP id j738uNL22786 for ; Wed, 3 Aug 2005 17:56:23 +0900 (JST) Received: from TNESVC1.tnes.nec.co.jp ([10.1.101.14]) by secsv2.tnes.nec.co.jp (ExpressMail 5.10) with SMTP id 20050803.175358.31003132 for ; Wed, 3 Aug 2005 17:53:58 +0900 Received: FROM noshiro.bsd.tnes.nec.co.jp BY TNESVC1.tnes.nec.co.jp ; Wed Aug 03 17:53:57 2005 +0900 Received: from localhost (localhost.localdomain [127.0.0.1]) by noshiro.bsd.tnes.nec.co.jp (Postfix) with ESMTP id D3498749FA; Wed, 3 Aug 2005 17:56:22 +0900 (JST) Date: Wed, 03 Aug 2005 17:56:22 +0900 (JST) Message-Id: <20050803.175622.607955722.masano@tnes.nec.co.jp> To: lord@xfs.org, linux-xfs@oss.sgi.com Subject: Re: deadlocks on ENOSPC From: ASANO Masahiro In-Reply-To: <42D7AA45.2040608@xfs.org> References: <20050715.150717.28782011.masano@tnes.nec.co.jp> <42D7AA45.2040608@xfs.org> X-Mailer: Mew version 3.3 on XEmacs 21.4.11 (Native Windows TTY Support) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 5707 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: masano@tnes.nec.co.jp Precedence: bulk X-list: linux-xfs Status: O Content-Length: 4218 Lines: 117 Hi, From: Steve Lord Subject: Re: deadlocks on ENOSPC Date: Fri, 15 Jul 2005 07:21:25 -0500 > Hi Masano, > > That is definitely a bug, the extent logic is not supposed to lock > allocation groups out of order. Multiple allocation groups are OK, > but wrapping past the last allocation group back to the first again > is not. The following `break' seems to be guilty. fs/xfs/xfs_alloc.c: in xfs_alloc_fix_freelist() 1967 /* 1968 * Stop if we run out. Won't happen if callers are obeying 1969 * the restrictions correctly. Can happen for free calls 1970 * on a completely full ag. 1971 */ 1972 if (targs.agbno == NULLAGBLOCK) 1973 break; I've tested the deadlock situation several times, and I found that deadlock occur immediately after the above `break'. If kernel quit at that point, the AGF would be just locked until it is committed. It may cause AGF deadlock. xfs_strategy() +-- xfs_bmapi() +-- xfs_bmap_alloc() | +-- xfs_alloc_vextent( XFS_ALLOCTYPE_NEAR_BNO ) | | | +-- xfs_alloc_fix_freelist() | | | | | +-- xfs_alloc_read_agf( AGm ) <-- Get and lock the AGF | | +-- xfs_alloc_ag_vextent() <-- Make the freelist longer | | +-- NULLAGBLOCK && return 0 <-- Quit because of no space | | (the AGF is locked) | +-- NULLFSBLOCK && return 0 : +-- xfs_alloc_vextent( XFS_ALLOCTYPE_FIRST_AG ) | | | +-- xfs_alloc_fix_freelist() | | : +-- xfs_alloc_read_agf( AGn: n breaking order Here is the patch against 2.6.13-rc5 + TAKE 938502. This patch adds XFS_ALLOCTYPE_FIRST_AG_TRYLOCK flag to avoid waiting on locks. 8<--------8<--------8<--------8<--------8<--------8<-------- --- linux-2.6.13-rc5/fs/xfs/xfs_alloc.h.orig 2005-08-03 11:13:27.000000000 +0900 +++ linux-2.6.13-rc5/fs/xfs/xfs_alloc.h 2005-08-03 11:14:48.000000000 +0900 @@ -48,7 +48,8 @@ typedef enum xfs_alloctype XFS_ALLOCTYPE_THIS_AG, /* anywhere in this a.g. */ XFS_ALLOCTYPE_START_BNO, /* near this block else anywhere */ XFS_ALLOCTYPE_NEAR_BNO, /* in this a.g. and near this block */ - XFS_ALLOCTYPE_THIS_BNO /* at exactly this block */ + XFS_ALLOCTYPE_THIS_BNO, /* at exactly this block */ + XFS_ALLOCTYPE_FIRST_AG_TRYLOCK /* ... start at ag 0 with trylock */ } xfs_alloctype_t; /* --- linux-2.6.13-rc5/fs/xfs/xfs_alloc.c.orig 2005-08-03 10:30:33.000000000 +0900 +++ linux-2.6.13-rc5/fs/xfs/xfs_alloc.c 2005-08-03 12:06:31.000000000 +0900 @@ -2322,6 +2322,7 @@ xfs_alloc_vextent( case XFS_ALLOCTYPE_ANY_AG: case XFS_ALLOCTYPE_START_AG: case XFS_ALLOCTYPE_FIRST_AG: + case XFS_ALLOCTYPE_FIRST_AG_TRYLOCK: /* * Rotate through the allocation groups looking for a winner. */ @@ -2341,6 +2342,14 @@ xfs_alloc_vextent( args->type = XFS_ALLOCTYPE_THIS_AG; sagno = 0; flags = 0; + } else if (type == XFS_ALLOCTYPE_FIRST_AG_TRYLOCK) { + /* + * Start with allocation group given by bno. + */ + args->agno = XFS_FSB_TO_AGNO(mp, args->fsbno); + args->type = XFS_ALLOCTYPE_THIS_AG; + sagno = 0; + flags = XFS_ALLOC_FLAG_TRYLOCK; } else { if (type == XFS_ALLOCTYPE_START_AG) args->type = XFS_ALLOCTYPE_THIS_AG; --- linux-2.6.13-rc5/fs/xfs/xfs_bmap.c.orig 2005-08-03 11:13:40.000000000 +0900 +++ linux-2.6.13-rc5/fs/xfs/xfs_bmap.c 2005-08-03 11:16:39.000000000 +0900 @@ -2711,7 +2711,7 @@ xfs_bmap_alloc( } if (args.fsbno == NULLFSBLOCK && nullfb) { args.fsbno = 0; - args.type = XFS_ALLOCTYPE_FIRST_AG; + args.type = XFS_ALLOCTYPE_FIRST_AG_TRYLOCK; args.total = ap->minlen; args.minleft = 0; if ((error = xfs_alloc_vextent(&args))) 8<--------8<--------8<--------8<--------8<--------8<-------- This patch reduces AGF deadlock but is not complete yet. To avoid deadlock on ENOSPC completely, I need to change the definition of XFS_STRAT_WRITE_IMAPS from 2 to 1 too. This workaround is Steve's idea. I don't know whether this patch/approach is right or not. So any comments are welcome. -- masano From owner-linux-xfs@oss.sgi.com Wed Aug 3 03:55:42 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 03:55:46 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j73AtfH9013033 for ; Wed, 3 Aug 2005 03:55:42 -0700 Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j73ArdxT029851 for ; Wed, 3 Aug 2005 05:53:39 -0500 Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j73Aqmdq026464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 05:53:13 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j73AqIh0026435; Wed, 3 Aug 2005 05:52:18 -0500 Date: Wed, 3 Aug 2005 05:52:18 -0500 From: Christoph Hellwig Message-Id: <200508031052.j73AqIh0026435@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Subject: PARTIAL TAKE 934766 - remove unessecary vnode flags X-archive-position: 5709 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1819 Lines: 41 Date: Wed Aug 3 03:28:40 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.4.x Inspected by: nathans, felixb The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.4.x-xfs Modid: xfs-linux:xfs-kern:196852a fs/xfs/xfs_iget.c - 1.204 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iget.c.diff?r1=text&tr1=1.204&r2=text&tr2=1.203&f=h fs/xfs/linux-2.6/xfs_vnode.c - 1.130 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vnode.c.diff?r1=text&tr1=1.130&r2=text&tr2=1.129&f=h fs/xfs/linux-2.6/xfs_vnode.h - 1.107 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vnode.h.diff?r1=text&tr1=1.107&r2=text&tr2=1.106&f=h fs/xfs/linux-2.4/xfs_vnode.c - 1.131 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_vnode.c.diff?r1=text&tr1=1.131&r2=text&tr2=1.130&f=h fs/xfs/linux-2.4/xfs_vnode.h - 1.100 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_vnode.h.diff?r1=text&tr1=1.100&r2=text&tr2=1.99&f=h fs/xfs/linux-2.6/xfs_ksyms.c - 1.24 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_ksyms.c.diff?r1=text&tr1=1.24&r2=text&tr2=1.23&f=h fs/xfs/linux-2.4/xfs_ksyms.c - 1.20 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_ksyms.c.diff?r1=text&tr1=1.20&r2=text&tr2=1.19&f=h Subject: PARTIAL TAKE 934766 - fix 2.4 compilation after iowait changes Date: Wed Aug 3 03:51:58 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.4.x Inspected by: hch The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.4.x-xfs Modid: xfs-linux:xfs-kern:196855a fs/xfs/linux-2.4/xfs_vnode.h - 1.101 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_vnode.h.diff?r1=text&tr1=1.101&r2=text&tr2=1.100&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 3 03:49:19 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 03:49:22 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j73AnJH9012360 for ; Wed, 3 Aug 2005 03:49:19 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j73AlGxT028809 for ; Wed, 3 Aug 2005 05:47:16 -0500 Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by nodin.corp.sgi.com (SGI-8.12.5/8.12.10/SGI_generic_relay-1.2) with ESMTP id j73AlFbT101158693 for ; Wed, 3 Aug 2005 03:47:15 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j73AiOId023580 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 05:44:49 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j73Ahsk4023561; Wed, 3 Aug 2005 05:43:54 -0500 Date: Wed, 3 Aug 2005 05:43:54 -0500 From: Christoph Hellwig Message-Id: <200508031043.j73Ahsk4023561@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Subject: PARTIAL TAKE 934766 - pass the kiocb to the direct I/O ->end_io callback. X-archive-position: 5708 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1867 Lines: 46 Backported from 2.6.13-rc Date: Wed Aug 3 03:36:57 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.6.x Inspected by: nathans, felixb Depends on the following mods for execution: 2.6.x-xfs:linux:196853b The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:196853a fs/xfs/linux-2.6/xfs_aops.c - 1.90 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.90&r2=text&tr2=1.89&f=h Modid: 2.6.x-xfs:linux:196853b Depends on the following mods for execution: xfs-linux:xfs-kern:196853a fs/direct-io.c - 1.11 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/fs/direct-io.c.diff?r1=text&tr1=1.11&r2=text&tr2=1.10&f=h include/linux/fs.h - 1.17 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/include/linux/fs.h.diff?r1=text&tr1=1.17&r2=text&tr2=1.16&f=h Subject: PARTIAL TAKE 934766 - add infrastructure for waiting on I/O completion at inode reclaim time Date: Wed Aug 3 03:43:11 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.6.x Inspected by: nathans,felixb The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:196854a fs/xfs/xfs_vnodeops.c - 1.649 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_vnodeops.c.diff?r1=text&tr1=1.649&r2=text&tr2=1.648&f=h fs/xfs/linux-2.6/xfs_vnode.c - 1.131 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vnode.c.diff?r1=text&tr1=1.131&r2=text&tr2=1.130&f=h fs/xfs/linux-2.6/xfs_vnode.h - 1.108 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vnode.h.diff?r1=text&tr1=1.108&r2=text&tr2=1.107&f=h fs/xfs/linux-2.6/xfs_aops.c - 1.91 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.91&r2=text&tr2=1.90&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 3 03:59:17 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 03:59:20 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j73AxHH9013908 for ; Wed, 3 Aug 2005 03:59:17 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j73CrDSi020240 for ; Wed, 3 Aug 2005 05:53:13 -0700 Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by nodin.corp.sgi.com (SGI-8.12.5/8.12.10/SGI_generic_relay-1.2) with ESMTP id j73AvDbT101236297 for ; Wed, 3 Aug 2005 03:57:14 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j73AsMxa026549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 05:54:47 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j73Arq9t026530; Wed, 3 Aug 2005 05:53:52 -0500 Date: Wed, 3 Aug 2005 05:53:52 -0500 From: Christoph Hellwig Message-Id: <200508031053.j73Arq9t026530@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Subject: PARTIAL TAKE 934766 - Add infrastructure for tracking I/O completions X-archive-position: 5710 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 992 Lines: 21 Date: Wed Aug 3 03:53:39 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.6.x Inspected by: nathans,felixb The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:196856a fs/xfs/linux-2.6/xfs_aops.h - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.h fs/xfs/linux-2.6/xfs_linux.h - 1.130 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_linux.h.diff?r1=text&tr1=1.130&r2=text&tr2=1.129&f=h fs/xfs/linux-2.6/xfs_super.c - 1.337 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_super.c.diff?r1=text&tr1=1.337&r2=text&tr2=1.336&f=h fs/xfs/linux-2.6/xfs_aops.c - 1.92 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.92&r2=text&tr2=1.91&f=h fs/xfs/linux-2.6/xfs_buf.c - 1.199 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_buf.c.diff?r1=text&tr1=1.199&r2=text&tr2=1.198&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 3 04:01:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 04:02:02 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j73B1xH9014503 for ; Wed, 3 Aug 2005 04:01:59 -0700 Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j73AxuxT030919 for ; Wed, 3 Aug 2005 05:59:56 -0500 Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j73Ax5Dw027142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 05:59:30 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j73AwZFZ027123; Wed, 3 Aug 2005 05:58:35 -0500 Date: Wed, 3 Aug 2005 05:58:35 -0500 From: Christoph Hellwig Message-Id: <200508031058.j73AwZFZ027123@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Subject: TAKE 934766 - Delay direct I/O completion to a workqueue X-archive-position: 5711 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 978 Lines: 23 This is nessecary because aio+dio completions may happen from irq context but we need process context for converting unwritten extents. We also queue regular direct I/O completions to workqueue for regularity, there's only one queue_work call per syscall. Date: Wed Aug 3 03:58:24 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.6.x Inspected by: nathans, felixb The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:196857a fs/xfs/linux-2.6/xfs_lrw.c - 1.226 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_lrw.c.diff?r1=text&tr1=1.226&r2=text&tr2=1.225&f=h fs/xfs/linux-2.6/xfs_file.c - 1.125 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_file.c.diff?r1=text&tr1=1.125&r2=text&tr2=1.124&f=h fs/xfs/linux-2.6/xfs_aops.c - 1.93 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.93&r2=text&tr2=1.92&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 3 10:54:26 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 10:54:30 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j73HsQH9016052 for ; Wed, 3 Aug 2005 10:54:26 -0700 Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j73JmPLk012263 for ; Wed, 3 Aug 2005 12:48:25 -0700 Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j73HoWYd011958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 12:50:57 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j73Ho2it011939; Wed, 3 Aug 2005 12:50:02 -0500 Date: Wed, 3 Aug 2005 12:50:02 -0500 From: Christoph Hellwig Message-Id: <200508031750.j73Ho2it011939@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Subject: TAKE 936584 - Delay I/O completion for unwritten extents after conversion X-archive-position: 5712 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 548 Lines: 15 Date: Wed Aug 3 10:49:51 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.6.x Inspected by: sandeen The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:196886a fs/xfs/linux-2.6/xfs_aops.c - 1.94 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.94&r2=text&tr2=1.93&f=h fs/xfs/linux-2.6/xfs_aops.h - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.h.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 3 11:14:43 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 11:14:46 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j73IEhH9017485 for ; Wed, 3 Aug 2005 11:14:43 -0700 Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j73ICexT014273 for ; Wed, 3 Aug 2005 13:12:40 -0500 Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j73IAnag013872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Aug 2005 13:11:14 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j73IAJC9013853; Wed, 3 Aug 2005 13:10:19 -0500 Date: Wed, 3 Aug 2005 13:10:19 -0500 From: Christoph Hellwig Message-Id: <200508031810.j73IAJC9013853@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Subject: TAKE 940531 - streamline the clear_inode path X-archive-position: 5713 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1208 Lines: 22 Date: Wed Aug 3 11:10:09 PDT 2005 Workarea: naboo.americas.sgi.com:/tmp/hch/xfs-2.4.x Inspected by: sandeen The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.4.x-xfs Modid: xfs-linux:xfs-kern:196888a fs/xfs/linux-2.6/xfs_vnode.c - 1.132 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vnode.c.diff?r1=text&tr1=1.132&r2=text&tr2=1.131&f=h fs/xfs/linux-2.6/xfs_vnode.h - 1.109 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vnode.h.diff?r1=text&tr1=1.109&r2=text&tr2=1.108&f=h fs/xfs/linux-2.6/xfs_super.c - 1.338 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_super.c.diff?r1=text&tr1=1.338&r2=text&tr2=1.337&f=h fs/xfs/linux-2.4/xfs_vnode.c - 1.132 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_vnode.c.diff?r1=text&tr1=1.132&r2=text&tr2=1.131&f=h fs/xfs/linux-2.4/xfs_vnode.h - 1.102 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_vnode.h.diff?r1=text&tr1=1.102&r2=text&tr2=1.101&f=h fs/xfs/linux-2.4/xfs_super.c - 1.309 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_super.c.diff?r1=text&tr1=1.309&r2=text&tr2=1.308&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 3 16:03:15 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 16:03:19 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j73N3DH9013353 for ; Wed, 3 Aug 2005 16:03:14 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA29279; Thu, 4 Aug 2005 09:00:56 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j73N0rol21170454; Thu, 4 Aug 2005 09:00:53 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j73N0pSf21619135; Thu, 4 Aug 2005 09:00:51 +1000 (EST) Date: Thu, 4 Aug 2005 09:00:50 +1000 From: David Chinner To: Brice GIBOUDEAU Cc: linux-xfs@oss.sgi.com Subject: Re: XFS trouble. Message-ID: <20050804090050.B21661319@melbourne.sgi.com> References: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org>; from brice@pingus.org on Wed, Aug 03, 2005 at 09:21:49AM +0200 X-archive-position: 5714 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1704 Lines: 42 On Wed, Aug 03, 2005 at 09:21:49AM +0200, Brice GIBOUDEAU wrote: > Hi, > > I have a Linux (Debian Sarge) server with more than 4Gb of memory, I'm > running XFS on other servers for a long time without any problem. (Less or > equal to 4Gb of memory) > Actually i'm using 2.4.31 kernel, when i add PEA (64Gb of memory) in my > kernel i have a memory leak when i'm working on XFS File system. > > Exemple : > --------- > I have 2 volumes (/xfs1 & /xfs2) of 1TB with million of small files on > /xfs1, i trie to make a backup of file from /xfs1 to /xfs2 (tar -cvf > /xfs2/backup.tar /xfs1), after several minutes the memory is full, and i > get this messages : > -> kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) > -> kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) > -> kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) > -> kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) > -> kernel: __alloc_pages: 1-order allocation failed (gfp=0x1f0/0) > -> kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) > -> kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) Sounds more like a lowmem/highmem balance/reclaim VM issue than a memory leak. You could be running out of low memory which, IIRC, holds most of the kernel data and if you're not using highmem I/O, all the bounce buffers to do I/O out of pages in highmem. Where are these failures happening (did you get a stack trace)? Are they in XFS, or somewhere else? What does /proc/meminfo and /proc/slabinfo tell you? That is, what memory is exhausted and what is using it all? Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Wed Aug 3 22:34:15 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 22:34:17 -0700 (PDT) Received: from raad.intranet (dial169-7.awalnet.net [213.184.169.7] (may be forged)) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j745YAH9011352 for ; Wed, 3 Aug 2005 22:34:14 -0700 Received: from i810 (rescueCli [10.254.254.253]) by raad.intranet (8.8.7/8.8.7) with ESMTP id IAA21511; Thu, 4 Aug 2005 08:32:30 +0300 Message-Id: <200508040532.IAA21511@raad.intranet> From: "Al Boldi" To: "'Christoph Hellwig'" Cc: , Subject: RE: TAKE 934766 - Delay direct I/O completion to a workqueue Date: Wed, 3 Aug 2005 17:31:58 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <200508031058.j73AwZFZ027123@naboo.americas.sgi.com> Thread-Index: AcWYsBEwS8fzlusCS/66hgRw2QhNkgAeKvuQ X-archive-position: 5715 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: a1426z@gawab.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 635 Lines: 17 Will this affect XFS behaviour with regards to the non-existent Ordered-Mode? -----Original Message----- From: linux-xfs-bounce@oss.sgi.com [mailto:linux-xfs-bounce@oss.sgi.com] On Behalf Of Christoph Hellwig Sent: Wednesday, August 03, 2005 1:59 PM To: linux-xfs@oss.sgi.com; sgi.bugs.xfs@fido.engr.sgi.com Subject: TAKE 934766 - Delay direct I/O completion to a workqueue This is nessecary because aio+dio completions may happen from irq context but we need process context for converting unwritten extents. We also queue regular direct I/O completions to workqueue for regularity, there's only one queue_work call per syscall. From owner-linux-xfs@oss.sgi.com Wed Aug 3 23:52:16 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Aug 2005 23:52:21 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j746qEH9015368 for ; Wed, 3 Aug 2005 23:52:15 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA08969; Thu, 4 Aug 2005 16:50:06 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j746o1ol21897548; Thu, 4 Aug 2005 16:50:02 +1000 (EST) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j746o0xD21821394; Thu, 4 Aug 2005 16:50:00 +1000 (EST) Date: Thu, 4 Aug 2005 16:50:00 +1000 (EST) From: Timothy Shimmin Message-Id: <200508040650.j746o0xD21821394@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 940491 - sb_qflags are not reset after mounting/unmounting with _no_ quotas X-archive-position: 5716 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tes@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2338 Lines: 53 Need to be able to reset sb_qflags if not mounting with quotas, having previously mounted with quotas. What this means is that if one mounts with quotas, does stuff and then unmounts. Then mounts without quotas, does stuff and then unmounts. Then decides to turn quotas back on and mounts with quotas. What is supposed to happen is that a quotacheck is redone on the filesystem - to get the quota information back up to date. Without this fix, however, this won't happen because the sb_qflags were not being reset on a no quota mount and so it won't tell that it had previously been mounted without quotas. --Tim Date: Thu Aug 4 16:41:05 AEST 2005 Workarea: snort.melbourne.sgi.com:/home/tes/isms/xfs-linux-test Inspected by: nathans@sgi.com The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:23388a xfs_qmops.c - 1.11 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_qmops.c.diff?r1=text&tr1=1.11&r2=text&tr2=1.10&f=h - Add xfs_mount_reset_sbqflags from xfs_qm_bhv.c since we need it for the non-quota case and will use it here. Add a quota stub function for xfs_qminit called xfs_noquota_init() which does the qflags resetting if necessary. xfs_quota.h - 1.40 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_quota.h.diff?r1=text&tr1=1.40&r2=text&tr2=1.39&f=h - Add some QUOTA macros from xfs_qm.h . quota/xfs_qm_bhv.c - 1.12 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/quota/xfs_qm_bhv.c.diff?r1=text&tr1=1.12&r2=text&tr2=1.11&f=h - Remove xfs_mount_reset_sbqflags since it is moving to xfs_qmops.c . quota/xfs_dquot.h - 1.8 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/quota/xfs_dquot.h.diff?r1=text&tr1=1.8&r2=text&tr2=1.7&f=h - Remove some QUOTA macros and put them in xfs_quota.h for use in xfs_qmops.c . quota/xfs_qm.h - 1.11 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/quota/xfs_qm.h.diff?r1=text&tr1=1.11&r2=text&tr2=1.10&f=h - Remove xfs_mount_reset_sbqflags() proto since the function is moving to xfs_qm.c and the proto to xfs_quota.h . quota/xfs_qm.c - 1.25 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/quota/xfs_qm.c.diff?r1=text&tr1=1.25&r2=text&tr2=1.24&f=h - Remove resetting of qflags here and move it to xfs_qmops.c . From owner-linux-xfs@oss.sgi.com Thu Aug 4 01:43:17 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Aug 2005 01:43:23 -0700 (PDT) Received: from apollo.le.ac.uk (ntp2b.le.ac.uk [143.210.16.125]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j748hHH9027656 for ; Thu, 4 Aug 2005 01:43:17 -0700 Received: from [143.210.36.63] (helo=mail.star.le.ac.uk) by apollo.le.ac.uk with esmtp (Exim 4.44) id 1E0bHt-00064j-6z for linux-xfs@oss.sgi.com; Thu, 04 Aug 2005 09:41:13 +0100 Received: by mail.star.le.ac.uk (Postfix, from userid 65534) id E93BA271A05; Thu, 4 Aug 2005 09:41:12 +0100 (BST) Received: from skibble.star.le.ac.uk (skibble.star.le.ac.uk [143.210.36.10]) by mail.star.le.ac.uk (Postfix) with ESMTP id A46EE271A04 for ; Thu, 4 Aug 2005 09:41:12 +0100 (BST) Subject: Patches please for RHEL4 WS xfs From: Grant Denkinson To: linux-xfs@oss.sgi.com Content-Type: text/plain Organization: Dept. Physics & Astronomy, University of Leicester Date: Thu, 04 Aug 2005 09:41:14 +0100 Message-Id: <1123144874.4097.20.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 Content-Transfer-Encoding: 7bit X-UoL-Id: 4d2c26aa1d1a79286f172a4eb0ab5a95@1E0bHt-00064j-6z@apollo.le.ac.uk X-archive-position: 5717 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: gd41@star.le.ac.uk Precedence: bulk X-list: linux-xfs Status: O Content-Length: 806 Lines: 22 I'm running Red Hat Enterprise Linux 4 WS with its standard 2.6.9-5.0.5.ELsmp kernel on a Dell PowerEdge 2650 (Dual Xeon). I'd like to run xfs on top of a logical volume made up of a couple of hardware SCSI arrays. I understand there may be an issue with 4K stacks. I found a patch at http://oss.sgi.com/archives/linux-xfs/2005-03/msg00189.html but this is for AS not WS. Does anyone have a WS specific patch or other suggestions to get xfs going with larger than 4K stack? In the meantime I shall try it with 4K and check for errors. Thanks in advance, Grant -- Grant Denkinson telephone: +44 116 2522078 Computer Systems Manager, fax: +44 116 2523311 XMM-SSC group, Department of Physics & Astronomy, University of Leicester, Leicester, LE1 7RH, England From owner-linux-xfs@oss.sgi.com Thu Aug 4 01:55:45 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Aug 2005 01:55:50 -0700 (PDT) Received: from pingus.pingus.org (pingus.pingus.org [82.66.123.179]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j748thH9028807 for ; Thu, 4 Aug 2005 01:55:44 -0700 Received: from www.pingus.org (localhost [127.0.0.1]) by pingus.pingus.org (Postfix) with ESMTP id 4DB7640A8B; Thu, 4 Aug 2005 10:53:38 +0200 (CEST) Received: from 194.2.155.29 (SquirrelMail authenticated user brice) by www.pingus.org with HTTP; Thu, 4 Aug 2005 10:53:38 +0200 (CEST) Message-ID: <3088.194.2.155.29.1123145618.squirrel@www.pingus.org> In-Reply-To: <20050804090050.B21661319@melbourne.sgi.com> References: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org> <20050804090050.B21661319@melbourne.sgi.com> Date: Thu, 4 Aug 2005 10:53:38 +0200 (CEST) Subject: Re: XFS trouble. From: "Brice GIBOUDEAU" To: "David Chinner" Cc: "Brice GIBOUDEAU" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5718 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: brice@pingus.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 36150 Lines: 1079 Hi, I give more details. > Where are these failures happening (did you get a stack trace)? > Are they in XFS, or somewhere else? No. I don't have a "stack trace" because process don't crash, the server is verry verry verry slow, but nothing crash. If i stop process like my tar in the previous exemple (after getting __alloc_pages: 0-order allocation failed) the system is still slow, only a reboot have an effect. > What does /proc/meminfo and /proc/slabinfo tell you? That is, what > memory is exhausted and what is using it all? Donwstarairs you have the result of slabinfo and meminfo before (Tue Aug 2 02:04:02) and after (Tue Aug 2 02:05:01) the first __alloc_pages message. TOP RESULT : ------------ top - 17:52:59 up 1 day, 7:03, 2 users, load average: 5.88, 7.55, 7.62 Tasks: 59 total, 11 running, 47 sleeping, 0 stopped, 1 zombie Cpu(s): 0.2% user, 99.6% system, 0.0% nice, 0.2% idle Mem: 16568820k total, 15602560k used, 966260k free, 328k buffers 0 0 R 99.9 0.0 77:04.03 kswapd 23190 root 20 0 4392 4392 872 R 77.9 0.0 41:38.31 bpbkar 1 root 20 0 508 508 452 R 44.6 0.0 5:30.29 init 2 root 9 0 0 0 0 S 0.0 0.0 1:29.19 keventd 3 root 19 19 0 0 0 S 0.0 0.0 0:00.85 ksoftirqd_CPU0 4 root 19 19 0 0 0 S 0.0 0.0 0:01.02 ksoftirqd_CPU1 5 root 19 19 0 0 0 S 0.0 0.0 0:00.81 ksoftirqd_CPU2 6 root 19 19 0 0 0 S 0.0 0.0 0:00.72 ksoftirqd_CPU3 8 root 9 0 0 0 0 S 0.0 0.0 1:20.68 bdflush 9 root 9 0 0 0 0 S 0.0 0.0 10:37.94 kupdated 10 root 9 0 0 0 0 S 0.0 0.0 0:00.38 xfsbufd 11 root 9 0 0 0 0 S 0.0 0.0 0:00.54 xfslogd/0 12 root 9 0 0 0 0 S 0.0 0.0 0:00.38 xfslogd/1 13 root 9 0 0 0 0 S 0.0 0.0 0:00.51 xfslogd/2 14 root 9 0 0 0 0 S 0.0 0.0 0:00.43 xfslogd/3 15 root 9 0 0 0 0 S 0.0 0.0 0:00.00 xfsdatad/0 16 root 9 0 0 0 0 S 0.0 0.0 0:00.00 xfsdatad/1 17 root 9 0 0 0 0 S 0.0 0.0 0:00.00 xfsdatad/2 18 root 9 0 0 0 0 S 0.0 0.0 0:00.00 xfsdatad/3 24 root 9 0 0 0 0 S 0.0 0.0 0:00.00 khubd 144 root 9 0 0 0 0 S 0.0 0.0 1:12.80 xfssyncd 145 root 9 0 0 0 0 S 0.0 0.0 0:00.02 xfssyncd 272 root 9 0 808 808 700 S 0.0 0.0 2:09.93 syslogd 275 root 9 0 1364 1360 464 S 0.0 0.0 0:00.07 klogd /proc/meminfo : --------------- Tue Aug 2 02:04:01 CEST 2005 total: used: free: shared: buffers: cached: Mem: 16966471680 15623704576 1342767104 0 180224 14847438848 Swap: 32737632256 0 32737632256 MemTotal: 16568820 kB MemFree: 1311296 kB MemShared: 0 kB Buffers: 176 kB Cached: 14499452 kB SwapCached: 0 kB Active: 1932 kB Inactive: 14497760 kB HighTotal: 15858532 kB HighFree: 1305552 kB LowTotal: 710288 kB LowFree: 5744 kB SwapTotal: 31970344 kB SwapFree: 31970344 kB Tue Aug 2 02:05:01 CEST 2005 total: used: free: shared: buffers: cached: Mem: 16966471680 15621611520 1344860160 0 176128 14843764736 Swap: 32737632256 0 32737632256 MemTotal: 16568820 kB MemFree: 1313340 kB MemShared: 0 kB Buffers: 172 kB Cached: 14495864 kB SwapCached: 0 kB Active: 1828 kB Inactive: 14494268 kB HighTotal: 15858532 kB HighFree: 1308552 kB LowTotal: 710288 kB LowFree: 4788 kB SwapTotal: 31970344 kB SwapFree: 31970344 kB /proc/slabinfo : ---------------- Tue Aug 2 02:04:02 CEST 2005 slabinfo - version: 1.1 (SMP) kmem_cache 96 96 244 6 6 1 : 252 126 tcp_tw_bucket 0 0 128 0 0 1 : 252 126 tcp_bind_bucket 7 112 32 1 1 1 : 252 126 tcp_open_request 1 58 64 1 1 1 : 252 126 inet_peer_cache 2 116 64 2 2 1 : 252 126 ip_fib_hash 9 224 32 2 2 1 : 252 126 ip_dst_cache 23 120 256 8 8 1 : 252 126 arp_cache 1 30 128 1 1 1 : 252 126 uhci_urb_priv 4 56 68 1 1 1 : 252 126 blkdev_requests 6144 6150 128 205 205 1 : 252 126 xfs_chashlist 8281 8466 20 51 51 1 : 252 126 xfs_ili 172 1080 140 40 40 1 : 252 126 xfs_ifork 0 0 56 0 0 1 : 252 126 xfs_efi_item 0 0 260 0 0 1 : 124 62 xfs_efd_item 0 0 260 0 0 1 : 124 62 xfs_buf_item 0 0 148 0 0 1 : 252 126 xfs_dabuf 274 400 16 2 2 1 : 252 126 xfs_da_state 0 0 336 0 0 1 : 124 62 xfs_trans 13 13 596 1 1 2 : 124 62 xfs_inode 208657 208719 408 23191 23191 1 : 124 62 xfs_btree_cur 0 0 132 0 0 1 : 252 126 xfs_bmap_free_item 0 0 12 0 0 1 : 252 126 xfs_buf_t 262 465 256 31 31 1 : 252 126 linvfs_icache 208700 208700 384 20870 20870 1 : 124 62 nfs_write_data 0 0 384 0 0 1 : 124 62 nfs_read_data 0 0 384 0 0 1 : 124 62 nfs_page 0 0 128 0 0 1 : 252 126 journal_head 0 0 48 0 0 1 : 252 126 revoke_table 0 0 12 0 0 1 : 252 126 revoke_record 0 0 32 0 0 1 : 252 126 dnotify_cache 0 0 20 0 0 1 : 252 126 file_lock_cache 2 80 96 2 2 1 : 252 126 fasync_cache 0 0 16 0 0 1 : 252 126 uid_cache 5 448 32 4 4 1 : 252 126 skbuff_head_cache 1261 1395 256 93 93 1 : 252 126 sock 220 228 1024 57 57 1 : 124 62 sigqueue 58 58 132 2 2 1 : 252 126 kiobuf 0 0 64 0 0 1 : 252 126 cdev_cache 136 290 64 5 5 1 : 252 126 bdev_cache 8 58 64 1 1 1 : 252 126 mnt_cache 16 116 64 2 2 1 : 252 126 inode_cache 424 658 512 94 94 1 : 124 62 dentry_cache 1568 4290 128 143 143 1 : 252 126 filp 2695 2730 128 91 91 1 : 252 126 names_cache 6 6 4096 6 6 1 : 60 30 buffer_head 3624879 3751050 128 125034 125035 1 : 252 126 mm_struct 381 465 256 31 31 1 : 252 126 vm_area_struct 1866 2850 128 95 95 1 : 252 126 fs_cache 383 406 64 7 7 1 : 252 126 files_cache 256 273 512 39 39 1 : 124 62 signal_act 204 286 1408 26 26 4 : 60 30 pae_pgd 381 580 64 10 10 1 : 252 126 size-131072(DMA) 0 0 131072 0 0 32 : 0 0 size-131072 0 0 131072 0 0 32 : 0 0 size-65536(DMA) 0 0 65536 0 0 16 : 0 0 size-65536 0 0 65536 0 0 16 : 0 0 size-32768(DMA) 0 0 32768 0 0 8 : 0 0 size-32768 20 20 32768 20 20 8 : 0 0 size-16384(DMA) 0 0 16384 0 0 4 : 0 0 size-16384 2 2 16384 2 2 4 : 0 0 size-8192(DMA) 0 0 8192 0 0 2 : 0 0 size-8192 4 4 8192 4 4 2 : 0 0 size-4096(DMA) 0 0 4096 0 0 1 : 60 30 size-4096 31 31 4096 31 31 1 : 60 30 size-2048(DMA) 0 0 2048 0 0 1 : 60 30 size-2048 358 396 2048 187 198 1 : 60 30 size-1024(DMA) 0 0 1024 0 0 1 : 124 62 size-1024 352 352 1024 88 88 1 : 124 62 size-512(DMA) 0 0 512 0 0 1 : 124 62 size-512 133 184 512 23 23 1 : 124 62 size-256(DMA) 0 0 256 0 0 1 : 252 126 size-256 539 675 256 42 45 1 : 252 126 size-128(DMA) 8 30 128 1 1 1 : 252 126 size-128 1276 3330 128 108 111 1 : 252 126 size-64(DMA) 0 0 128 0 0 1 : 252 126 size-64 539 2010 128 62 67 1 : 252 126 size-32(DMA) 8 58 64 1 1 1 : 252 126 size-32 724 2088 64 34 36 1 : 252 126 Tue Aug 2 02:05:01 CEST 2005 slabinfo - version: 1.1 (SMP) kmem_cache 96 96 244 6 6 1 : 252 126 tcp_tw_bucket 0 0 128 0 0 1 : 252 126 tcp_bind_bucket 7 112 32 1 1 1 : 252 126 tcp_open_request 0 0 64 0 0 1 : 252 126 inet_peer_cache 2 116 64 2 2 1 : 252 126 ip_fib_hash 9 224 32 2 2 1 : 252 126 ip_dst_cache 25 120 256 8 8 1 : 252 126 arp_cache 1 30 128 1 1 1 : 252 126 uhci_urb_priv 4 56 68 1 1 1 : 252 126 blkdev_requests 6144 6150 128 205 205 1 : 252 126 xfs_chashlist 8241 8632 20 52 52 1 : 252 126 xfs_ili 134 513 140 19 19 1 : 252 126 xfs_ifork 0 0 56 0 0 1 : 252 126 xfs_efi_item 0 0 260 0 0 1 : 124 62 xfs_efd_item 0 0 260 0 0 1 : 124 62 xfs_buf_item 0 0 148 0 0 1 : 252 126 xfs_dabuf 0 0 16 0 0 1 : 252 126 xfs_da_state 0 0 336 0 0 1 : 124 62 xfs_trans 0 0 596 0 0 2 : 124 62 xfs_inode 211936 212031 408 23559 23559 1 : 124 62 xfs_btree_cur 0 0 132 0 0 1 : 252 126 xfs_bmap_free_item 0 0 12 0 0 1 : 252 126 xfs_buf_t 50 60 256 4 4 1 : 252 126 linvfs_icache 211936 212020 384 21202 21202 1 : 124 62 nfs_write_data 0 0 384 0 0 1 : 124 62 nfs_read_data 0 0 384 0 0 1 : 124 62 nfs_page 0 0 128 0 0 1 : 252 126 journal_head 0 0 48 0 0 1 : 252 126 revoke_table 0 0 12 0 0 1 : 252 126 revoke_record 0 0 32 0 0 1 : 252 126 dnotify_cache 0 0 20 0 0 1 : 252 126 file_lock_cache 2 80 96 2 2 1 : 252 126 fasync_cache 0 0 16 0 0 1 : 252 126 uid_cache 5 448 32 4 4 1 : 252 126 skbuff_head_cache 534 1365 256 91 91 1 : 252 126 sock 220 228 1024 57 57 1 : 124 62 sigqueue 58 58 132 2 2 1 : 252 126 kiobuf 0 0 64 0 0 1 : 252 126 cdev_cache 136 290 64 5 5 1 : 252 126 bdev_cache 8 58 64 1 1 1 : 252 126 mnt_cache 16 116 64 2 2 1 : 252 126 inode_cache 430 658 512 94 94 1 : 124 62 dentry_cache 522 1710 128 57 57 1 : 252 126 filp 2695 2730 128 91 91 1 : 252 126 names_cache 2 2 4096 2 2 1 : 60 30 buffer_head 3623860 3751020 128 125034 125034 1 : 252 126 mm_struct 381 465 256 31 31 1 : 252 126 vm_area_struct 1866 2850 128 95 95 1 : 252 126 fs_cache 383 406 64 7 7 1 : 252 126 files_cache 256 273 512 39 39 1 : 124 62 signal_act 204 286 1408 26 26 4 : 60 30 pae_pgd 381 580 64 10 10 1 : 252 126 size-131072(DMA) 0 0 131072 0 0 32 : 0 0 size-131072 0 0 131072 0 0 32 : 0 0 size-65536(DMA) 0 0 65536 0 0 16 : 0 0 size-65536 0 0 65536 0 0 16 : 0 0 size-32768(DMA) 0 0 32768 0 0 8 : 0 0 size-32768 20 20 32768 20 20 8 : 0 0 size-16384(DMA) 0 0 16384 0 0 4 : 0 0 size-16384 2 2 16384 2 2 4 : 0 0 size-8192(DMA) 0 0 8192 0 0 2 : 0 0 size-8192 4 4 8192 4 4 2 : 0 0 size-4096(DMA) 0 0 4096 0 0 1 : 60 30 size-4096 28 28 4096 28 28 1 : 60 30 size-2048(DMA) 0 0 2048 0 0 1 : 60 30 size-2048 372 372 2048 186 186 1 : 60 30 size-1024(DMA) 0 0 1024 0 0 1 : 124 62 size-1024 352 352 1024 88 88 1 : 124 62 size-512(DMA) 0 0 512 0 0 1 : 124 62 size-512 112 152 512 19 19 1 : 124 62 size-256(DMA) 0 0 256 0 0 1 : 252 126 size-256 210 210 256 14 14 1 : 252 126 size-128(DMA) 8 30 128 1 1 1 : 252 126 size-128 1200 2520 128 84 84 1 : 252 126 size-64(DMA) 0 0 128 0 0 1 : 252 126 size-64 199 330 128 11 11 1 : 252 126 size-32(DMA) 8 58 64 1 1 1 : 252 126 size-32 357 580 64 10 10 1 : 252 126 SYSLOG : -------- <---It's the first __alloc_pages error message ---> Aug 2 02:04:43 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) Aug 2 02:04:52 sures last message repeated 3 times Aug 2 02:05:01 sures /USR/SBIN/CRON[18051]: (root) CMD (/usr/local/bin/logmem.sh) Aug 2 02:05:09 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) Aug 2 02:05:17 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) Aug 2 02:05:36 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) Aug 2 02:05:41 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) Aug 2 02:06:01 sures last message repeated 3 times Aug 2 02:06:05 sures /USR/SBIN/CRON[18060]: (root) CMD (/usr/local/bin/logmem.sh) Aug 2 02:06:06 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) Aug 2 02:06:09 sures last message repeated 2 times Aug 2 02:06:40 sures last message repeated 3 times Aug 2 02:07:08 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) Aug 2 02:07:08 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0x1f0/0) Aug 2 02:08:12 sures kernel: __alloc_pages: 0-order allocation failed (gfp=0xf0/0) My Kernel CONGIG : ------------------ # # Automatically generated by make menuconfig: don't edit # CONFIG_X86=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # # CONFIG_EXPERIMENTAL is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set CONFIG_MPENTIUM4=y # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_X86_HAS_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_F00F_WORKS_OK=y CONFIG_X86_MCE=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set CONFIG_MICROCODE=y CONFIG_X86_MSR=y CONFIG_X86_CPUID=y # CONFIG_NOHIGHMEM is not set # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y CONFIG_HIGHMEM=y CONFIG_X86_PAE=y CONFIG_HIGHIO=y # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set CONFIG_SMP=y CONFIG_NR_CPUS=32 # CONFIG_X86_NUMA is not set # CONFIG_X86_TSC_DISABLE is not set CONFIG_X86_TSC=y CONFIG_HAVE_DEC_LOCK=y # # General setup # CONFIG_NET=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_ISA=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set # CONFIG_HOTPLUG is not set # CONFIG_PCMCIA is not set # CONFIG_HOTPLUG_PCI is not set CONFIG_SYSVIPC=y # CONFIG_BSD_PROCESS_ACCT is not set CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_OOM_KILLER is not set # CONFIG_PM is not set # CONFIG_APM is not set # # ACPI Support # # CONFIG_ACPI is not set CONFIG_ACPI_BOOT=y # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play configuration # CONFIG_PNP=y CONFIG_ISAPNP=y # # Block devices # CONFIG_BLK_DEV_FD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set CONFIG_BLK_CPQ_CISS_DA=y CONFIG_CISS_SCSI_TAPE=y CONFIG_CISS_MONITOR_THREAD=y # CONFIG_BLK_DEV_DAC960 is not set # CONFIG_BLK_DEV_UMEM is not set # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_RAM is not set # CONFIG_BLK_DEV_INITRD is not set CONFIG_BLK_STATS=y # # Multi-device support (RAID and LVM) # # CONFIG_MD is not set # CONFIG_BLK_DEV_MD is not set # CONFIG_MD_LINEAR is not set # CONFIG_MD_RAID0 is not set # CONFIG_MD_RAID1 is not set # CONFIG_MD_RAID5 is not set # CONFIG_MD_MULTIPATH is not set # CONFIG_BLK_DEV_LVM is not set # # Networking options # CONFIG_PACKET=y # CONFIG_PACKET_MMAP is not set # CONFIG_NETLINK_DEV is not set # CONFIG_NETFILTER is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set CONFIG_IP_ADVANCED_ROUTER=y # CONFIG_IP_MULTIPLE_TABLES is not set # CONFIG_IP_ROUTE_MULTIPATH is not set # CONFIG_IP_ROUTE_TOS is not set CONFIG_IP_ROUTE_VERBOSE=y # CONFIG_IP_PNP is not set # CONFIG_NET_IPIP is not set # CONFIG_NET_IPGRE is not set # CONFIG_INET_ECN is not set CONFIG_SYN_COOKIES=y # CONFIG_VLAN_8021Q is not set # CONFIG_IPX is not set # CONFIG_ATALK is not set # CONFIG_DECNET is not set # CONFIG_BRIDGE is not set # # QoS and/or fair queueing # # CONFIG_NET_SCHED is not set # # Network testing # # CONFIG_NET_PKTGEN is not set # # Telephony Support # # CONFIG_PHONE is not set # CONFIG_PHONE_IXJ is not set # CONFIG_PHONE_IXJ_PCMCIA is not set # # ATA/IDE/MFM/RLL support # CONFIG_IDE=y # # IDE, ATA and ATAPI Block devices # CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set # CONFIG_BLK_DEV_IDE_SATA is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y # CONFIG_IDEDISK_STROKE is not set # CONFIG_BLK_DEV_IDECS is not set # CONFIG_BLK_DEV_DELKIN is not set CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_IDE_TASK_IOCTL is not set # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_CMD640_ENHANCED is not set # CONFIG_BLK_DEV_ISAPNP is not set CONFIG_BLK_DEV_IDEPCI=y # CONFIG_BLK_DEV_GENERIC is not set CONFIG_IDEPCI_SHARE_IRQ=y CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_OFFBOARD is not set # CONFIG_BLK_DEV_IDEDMA_FORCED is not set CONFIG_IDEDMA_PCI_AUTO=y # CONFIG_IDEDMA_ONLYDISK is not set CONFIG_BLK_DEV_IDEDMA=y # CONFIG_IDEDMA_PCI_WIP is not set # CONFIG_BLK_DEV_ADMA100 is not set # CONFIG_BLK_DEV_AEC62XX is not set # CONFIG_BLK_DEV_ALI15X3 is not set # CONFIG_WDC_ALI15X3 is not set # CONFIG_BLK_DEV_AMD74XX is not set # CONFIG_AMD74XX_OVERRIDE is not set # CONFIG_BLK_DEV_ATIIXP is not set # CONFIG_BLK_DEV_CMD64X is not set # CONFIG_BLK_DEV_TRIFLEX is not set # CONFIG_BLK_DEV_CY82C693 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_BLK_DEV_HPT34X is not set # CONFIG_HPT34X_AUTODMA is not set # CONFIG_BLK_DEV_HPT366 is not set CONFIG_BLK_DEV_PIIX=y # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_PDC202XX_OLD is not set # CONFIG_PDC202XX_BURST is not set # CONFIG_BLK_DEV_PDC202XX_NEW is not set # CONFIG_BLK_DEV_RZ1000 is not set # CONFIG_BLK_DEV_SC1200 is not set CONFIG_BLK_DEV_SVWKS=y # CONFIG_BLK_DEV_SIIMAGE is not set # CONFIG_BLK_DEV_SIS5513 is not set # CONFIG_BLK_DEV_SLC90E66 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_VIA82CXXX is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_IDEDMA_AUTO=y # CONFIG_IDEDMA_IVB is not set # CONFIG_DMA_NONPCI is not set # CONFIG_BLK_DEV_ATARAID is not set # CONFIG_BLK_DEV_ATARAID_PDC is not set # CONFIG_BLK_DEV_ATARAID_HPT is not set # CONFIG_BLK_DEV_ATARAID_MEDLEY is not set # CONFIG_BLK_DEV_ATARAID_SII is not set # # SCSI support # CONFIG_SCSI=y CONFIG_BLK_DEV_SD=y CONFIG_SD_EXTRA_DEVS=40 CONFIG_CHR_DEV_ST=y CONFIG_CHR_DEV_OSST=y CONFIG_BLK_DEV_SR=y CONFIG_BLK_DEV_SR_VENDOR=y CONFIG_SR_EXTRA_DEVS=2 CONFIG_CHR_DEV_SG=y CONFIG_SCSI_DEBUG_QUEUES=y CONFIG_SCSI_MULTI_LUN=y CONFIG_SCSI_CONSTANTS=y CONFIG_SCSI_LOGGING=y # # SCSI low-level drivers # # CONFIG_BLK_DEV_3W_XXXX_RAID is not set # CONFIG_SCSI_7000FASST is not set # CONFIG_SCSI_ACARD is not set # CONFIG_SCSI_AHA152X is not set # CONFIG_SCSI_AHA1542 is not set # CONFIG_SCSI_AHA1740 is not set CONFIG_SCSI_AIC7XXX=y CONFIG_AIC7XXX_CMDS_PER_DEVICE=32 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 # CONFIG_AIC7XXX_PROBE_EISA_VL is not set # CONFIG_AIC7XXX_BUILD_FIRMWARE is not set # CONFIG_AIC7XXX_DEBUG_ENABLE is not set CONFIG_AIC7XXX_DEBUG_MASK=0 # CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set # CONFIG_SCSI_AIC79XX is not set # CONFIG_SCSI_DPT_I2O is not set # CONFIG_SCSI_ADVANSYS is not set # CONFIG_SCSI_IN2000 is not set # CONFIG_SCSI_AM53C974 is not set # CONFIG_SCSI_MEGARAID is not set CONFIG_SCSI_MEGARAID2=y # CONFIG_SCSI_SATA is not set # CONFIG_SCSI_SATA_AHCI is not set # CONFIG_SCSI_SATA_SVW is not set # CONFIG_SCSI_ATA_PIIX is not set # CONFIG_SCSI_SATA_NV is not set # CONFIG_SCSI_SATA_QSTOR is not set # CONFIG_SCSI_SATA_PROMISE is not set # CONFIG_SCSI_SATA_SX4 is not set # CONFIG_SCSI_SATA_SIL is not set # CONFIG_SCSI_SATA_SIS is not set # CONFIG_SCSI_SATA_ULI is not set # CONFIG_SCSI_SATA_VIA is not set # CONFIG_SCSI_SATA_VITESSE is not set # CONFIG_SCSI_BUSLOGIC is not set # CONFIG_SCSI_CPQFCTS is not set # CONFIG_SCSI_DMX3191D is not set # CONFIG_SCSI_DTC3280 is not set # CONFIG_SCSI_EATA is not set # CONFIG_SCSI_EATA_DMA is not set # CONFIG_SCSI_EATA_PIO is not set # CONFIG_SCSI_FUTURE_DOMAIN is not set # CONFIG_SCSI_GDTH is not set # CONFIG_SCSI_GENERIC_NCR5380 is not set # CONFIG_SCSI_IPS is not set # CONFIG_SCSI_INITIO is not set # CONFIG_SCSI_INIA100 is not set # CONFIG_SCSI_NCR53C406A is not set # CONFIG_SCSI_NCR53C7xx is not set # CONFIG_SCSI_SYM53C8XX_2 is not set # CONFIG_SCSI_NCR53C8XX is not set # CONFIG_SCSI_SYM53C8XX is not set # CONFIG_SCSI_PAS16 is not set # CONFIG_SCSI_PCI2000 is not set # CONFIG_SCSI_PCI2220I is not set # CONFIG_SCSI_PSI240I is not set # CONFIG_SCSI_QLOGIC_FAS is not set # CONFIG_SCSI_QLOGIC_ISP is not set # CONFIG_SCSI_QLOGIC_FC is not set # CONFIG_SCSI_QLOGIC_1280 is not set # CONFIG_SCSI_SEAGATE is not set # CONFIG_SCSI_SIM710 is not set # CONFIG_SCSI_SYM53C416 is not set # CONFIG_SCSI_DC390T is not set # CONFIG_SCSI_T128 is not set # CONFIG_SCSI_U14_34F is not set # CONFIG_SCSI_ULTRASTOR is not set # CONFIG_SCSI_NSP32 is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # CONFIG_FUSION_BOOT is not set # CONFIG_FUSION_ISENSE is not set # CONFIG_FUSION_CTL is not set # CONFIG_FUSION_LAN is not set # # I2O device support # # CONFIG_I2O is not set # CONFIG_I2O_PCI is not set # CONFIG_I2O_BLOCK is not set # CONFIG_I2O_LAN is not set # CONFIG_I2O_SCSI is not set # CONFIG_I2O_PROC is not set # # Network device support # CONFIG_NETDEVICES=y # # ARCnet devices # # CONFIG_ARCNET is not set # CONFIG_DUMMY is not set # CONFIG_BONDING is not set # CONFIG_EQUALIZER is not set # CONFIG_TUN is not set # CONFIG_NET_SB1000 is not set # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y # CONFIG_SUNLANCE is not set # CONFIG_HAPPYMEAL is not set # CONFIG_SUNBMAC is not set # CONFIG_SUNQE is not set # CONFIG_SUNGEM is not set # CONFIG_NET_VENDOR_3COM is not set # CONFIG_LANCE is not set # CONFIG_NET_VENDOR_SMC is not set # CONFIG_NET_VENDOR_RACAL is not set # CONFIG_AT1700 is not set # CONFIG_DEPCA is not set # CONFIG_HP100 is not set # CONFIG_NET_ISA is not set CONFIG_NET_PCI=y # CONFIG_PCNET32 is not set # CONFIG_AMD8111_ETH is not set # CONFIG_ADAPTEC_STARFIRE is not set # CONFIG_AC3200 is not set # CONFIG_APRICOT is not set # CONFIG_B44 is not set # CONFIG_CS89x0 is not set # CONFIG_TULIP is not set # CONFIG_DE4X5 is not set # CONFIG_DGRS is not set # CONFIG_DM9102 is not set CONFIG_EEPRO100=y # CONFIG_EEPRO100_PIO is not set # CONFIG_E100 is not set # CONFIG_LNE390 is not set # CONFIG_FEALNX is not set # CONFIG_NATSEMI is not set # CONFIG_NE2K_PCI is not set # CONFIG_FORCEDETH is not set # CONFIG_NE3210 is not set # CONFIG_ES3210 is not set # CONFIG_8139CP is not set # CONFIG_8139TOO is not set # CONFIG_8139TOO_PIO is not set # CONFIG_8139TOO_TUNE_TWISTER is not set # CONFIG_8139TOO_8129 is not set # CONFIG_8139_OLD_RX_RESET is not set # CONFIG_SIS900 is not set # CONFIG_EPIC100 is not set # CONFIG_SUNDANCE is not set # CONFIG_SUNDANCE_MMIO is not set # CONFIG_TLAN is not set # CONFIG_VIA_RHINE is not set # CONFIG_VIA_RHINE_MMIO is not set # CONFIG_WINBOND_840 is not set # CONFIG_NET_POCKET is not set # # Ethernet (1000 Mbit) # # CONFIG_ACENIC is not set # CONFIG_DL2K is not set # CONFIG_E1000 is not set # CONFIG_MYRI_SBUS is not set # CONFIG_NS83820 is not set # CONFIG_HAMACHI is not set # CONFIG_YELLOWFIN is not set # CONFIG_R8169 is not set # CONFIG_SK98LIN is not set CONFIG_TIGON3=y # CONFIG_FDDI is not set # CONFIG_PLIP is not set # CONFIG_PPP is not set # CONFIG_SLIP is not set # # Wireless LAN (non-hamradio) # # CONFIG_NET_RADIO is not set # # Token Ring devices # # CONFIG_TR is not set # CONFIG_NET_FC is not set # # Wan interfaces # # CONFIG_WAN is not set # # Amateur Radio support # # CONFIG_HAMRADIO is not set # # IrDA (infrared) support # # CONFIG_IRDA is not set # # ISDN subsystem # # CONFIG_ISDN is not set # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Input core support # CONFIG_INPUT=y CONFIG_INPUT_KEYBDEV=y CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_UINPUT is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL=y # CONFIG_SERIAL_CONSOLE is not set # CONFIG_SERIAL_EXTENDED is not set # CONFIG_SERIAL_NONSTANDARD is not set CONFIG_UNIX98_PTYS=y CONFIG_UNIX98_PTY_COUNT=256 # # I2C support # # CONFIG_I2C is not set # # Mice # # CONFIG_BUSMOUSE is not set CONFIG_MOUSE=y CONFIG_PSMOUSE=y # CONFIG_82C710_MOUSE is not set # CONFIG_PC110_PAD is not set # CONFIG_MK712_MOUSE is not set # # Joysticks # # CONFIG_INPUT_GAMEPORT is not set # CONFIG_INPUT_NS558 is not set # CONFIG_INPUT_LIGHTNING is not set # CONFIG_INPUT_PCIGAME is not set # CONFIG_INPUT_CS461X is not set # CONFIG_INPUT_EMU10K1 is not set # CONFIG_INPUT_SERIO is not set # CONFIG_INPUT_SERPORT is not set # CONFIG_INPUT_ANALOG is not set # CONFIG_INPUT_A3D is not set # CONFIG_INPUT_ADI is not set # CONFIG_INPUT_COBRA is not set # CONFIG_INPUT_GF2K is not set # CONFIG_INPUT_GRIP is not set # CONFIG_INPUT_INTERACT is not set # CONFIG_INPUT_TMDC is not set # CONFIG_INPUT_SIDEWINDER is not set # CONFIG_INPUT_IFORCE_USB is not set # CONFIG_INPUT_IFORCE_232 is not set # CONFIG_INPUT_WARRIOR is not set # CONFIG_INPUT_MAGELLAN is not set # CONFIG_INPUT_SPACEORB is not set # CONFIG_INPUT_SPACEBALL is not set # CONFIG_INPUT_STINGER is not set # CONFIG_INPUT_DB9 is not set # CONFIG_INPUT_GAMECON is not set # CONFIG_INPUT_TURBOGRAFX is not set # CONFIG_QIC02_TAPE is not set # CONFIG_IPMI_HANDLER is not set # CONFIG_IPMI_PANIC_EVENT is not set # CONFIG_IPMI_DEVICE_INTERFACE is not set # CONFIG_IPMI_KCS is not set # CONFIG_IPMI_WATCHDOG is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set # CONFIG_SCx200 is not set # CONFIG_SCx200_GPIO is not set # CONFIG_AMD_RNG is not set # CONFIG_INTEL_RNG is not set # CONFIG_HW_RANDOM is not set # CONFIG_AMD_PM768 is not set # CONFIG_NVRAM is not set # CONFIG_RTC is not set # CONFIG_DTLK is not set # CONFIG_R3964 is not set # CONFIG_APPLICOM is not set # # Ftape, the floppy tape device driver # # CONFIG_FTAPE is not set # CONFIG_AGP is not set # # Direct Rendering Manager (XFree86 DRI support) # CONFIG_DRM=y # CONFIG_DRM_OLD is not set CONFIG_DRM_NEW=y CONFIG_DRM_TDFX=y # CONFIG_DRM_GAMMA is not set # CONFIG_DRM_R128 is not set CONFIG_DRM_RADEON=y # CONFIG_DRM_I810 is not set # CONFIG_DRM_I810_XFREE_41 is not set # CONFIG_DRM_I830 is not set # CONFIG_DRM_MGA is not set # CONFIG_DRM_SIS is not set # CONFIG_MWAVE is not set # CONFIG_OBMOUSE is not set # # Multimedia devices # # CONFIG_VIDEO_DEV is not set # # File systems # # CONFIG_QUOTA is not set # CONFIG_QFMT_V2 is not set # CONFIG_AUTOFS_FS is not set CONFIG_AUTOFS4_FS=y # CONFIG_REISERFS_FS is not set # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set # CONFIG_ADFS_FS is not set # CONFIG_ADFS_FS_RW is not set # CONFIG_AFFS_FS is not set # CONFIG_HFS_FS is not set # CONFIG_HFSPLUS_FS is not set # CONFIG_BEFS_FS is not set # CONFIG_BEFS_DEBUG is not set # CONFIG_BFS_FS is not set CONFIG_EXT3_FS=y CONFIG_JBD=y # CONFIG_JBD_DEBUG is not set CONFIG_FAT_FS=y # CONFIG_MSDOS_FS is not set # CONFIG_UMSDOS_FS is not set CONFIG_VFAT_FS=y # CONFIG_EFS_FS is not set # CONFIG_JFFS_FS is not set # CONFIG_JFFS2_FS is not set # CONFIG_CRAMFS is not set CONFIG_TMPFS=y CONFIG_RAMFS=y CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y # CONFIG_JFS_FS is not set # CONFIG_JFS_DEBUG is not set # CONFIG_JFS_STATISTICS is not set # CONFIG_MINIX_FS is not set # CONFIG_VXFS_FS is not set # CONFIG_NTFS_FS is not set # CONFIG_NTFS_RW is not set # CONFIG_HPFS_FS is not set CONFIG_PROC_FS=y # CONFIG_DEVFS_FS is not set # CONFIG_DEVFS_MOUNT is not set # CONFIG_DEVFS_DEBUG is not set CONFIG_DEVPTS_FS=y # CONFIG_QNX4FS_FS is not set # CONFIG_QNX4FS_RW is not set # CONFIG_ROMFS_FS is not set CONFIG_EXT2_FS=y # CONFIG_SYSV_FS is not set # CONFIG_UDF_FS is not set # CONFIG_UDF_RW is not set # CONFIG_UFS_FS is not set # CONFIG_UFS_FS_WRITE is not set CONFIG_XFS_FS=y # CONFIG_XFS_QUOTA is not set # CONFIG_XFS_RT is not set # CONFIG_XFS_TRACE is not set # CONFIG_XFS_DEBUG is not set # # Network File Systems # # CONFIG_CODA_FS is not set # CONFIG_INTERMEZZO_FS is not set CONFIG_NFS_FS=y CONFIG_NFS_V3=y # CONFIG_NFS_DIRECTIO is not set # CONFIG_ROOT_NFS is not set # CONFIG_NFSD is not set # CONFIG_NFSD_V3 is not set # CONFIG_NFSD_TCP is not set CONFIG_SUNRPC=y CONFIG_LOCKD=y CONFIG_LOCKD_V4=y # CONFIG_SMB_FS is not set # CONFIG_NCP_FS is not set # CONFIG_NCPFS_PACKET_SIGNING is not set # CONFIG_NCPFS_IOCTL_LOCKING is not set # CONFIG_NCPFS_STRONG is not set # CONFIG_NCPFS_NFS_NS is not set # CONFIG_NCPFS_OS2_NS is not set # CONFIG_NCPFS_SMALLDOS is not set # CONFIG_NCPFS_NLS is not set # CONFIG_NCPFS_EXTRAS is not set CONFIG_ZISOFS_FS=y # # Partition Types # # CONFIG_PARTITION_ADVANCED is not set CONFIG_MSDOS_PARTITION=y # CONFIG_SMB_NLS is not set CONFIG_NLS=y # # Native Language Support # CONFIG_NLS_DEFAULT="iso8859-1" # CONFIG_NLS_CODEPAGE_437 is not set # CONFIG_NLS_CODEPAGE_737 is not set # CONFIG_NLS_CODEPAGE_775 is not set CONFIG_NLS_CODEPAGE_850=y # CONFIG_NLS_CODEPAGE_852 is not set # CONFIG_NLS_CODEPAGE_855 is not set # CONFIG_NLS_CODEPAGE_857 is not set # CONFIG_NLS_CODEPAGE_860 is not set # CONFIG_NLS_CODEPAGE_861 is not set # CONFIG_NLS_CODEPAGE_862 is not set # CONFIG_NLS_CODEPAGE_863 is not set # CONFIG_NLS_CODEPAGE_864 is not set # CONFIG_NLS_CODEPAGE_865 is not set # CONFIG_NLS_CODEPAGE_866 is not set # CONFIG_NLS_CODEPAGE_869 is not set # CONFIG_NLS_CODEPAGE_936 is not set # CONFIG_NLS_CODEPAGE_950 is not set # CONFIG_NLS_CODEPAGE_932 is not set # CONFIG_NLS_CODEPAGE_949 is not set # CONFIG_NLS_CODEPAGE_874 is not set # CONFIG_NLS_ISO8859_8 is not set # CONFIG_NLS_CODEPAGE_1250 is not set # CONFIG_NLS_CODEPAGE_1251 is not set CONFIG_NLS_ISO8859_1=y # CONFIG_NLS_ISO8859_2 is not set # CONFIG_NLS_ISO8859_3 is not set # CONFIG_NLS_ISO8859_4 is not set # CONFIG_NLS_ISO8859_5 is not set # CONFIG_NLS_ISO8859_6 is not set # CONFIG_NLS_ISO8859_7 is not set # CONFIG_NLS_ISO8859_9 is not set # CONFIG_NLS_ISO8859_13 is not set # CONFIG_NLS_ISO8859_14 is not set # CONFIG_NLS_ISO8859_15 is not set # CONFIG_NLS_KOI8_R is not set # CONFIG_NLS_KOI8_U is not set # CONFIG_NLS_UTF8 is not set # # Console drivers # CONFIG_VGA_CONSOLE=y # CONFIG_VIDEO_SELECT is not set # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB=y # CONFIG_USB_DEBUG is not set # CONFIG_USB_DEVICEFS is not set # CONFIG_USB_BANDWIDTH is not set # CONFIG_USB_EHCI_HCD is not set CONFIG_USB_UHCI_ALT=y # CONFIG_USB_OHCI is not set # CONFIG_USB_SL811HS_ALT is not set # CONFIG_USB_SL811HS is not set # CONFIG_USB_AUDIO is not set # CONFIG_USB_EMI26 is not set # CONFIG_USB_MIDI is not set CONFIG_USB_STORAGE=y # CONFIG_USB_STORAGE_DEBUG is not set # CONFIG_USB_STORAGE_DATAFAB is not set # CONFIG_USB_STORAGE_FREECOM is not set # CONFIG_USB_STORAGE_ISD200 is not set # CONFIG_USB_STORAGE_DPCM is not set # CONFIG_USB_STORAGE_HP8200e is not set # CONFIG_USB_STORAGE_SDDR09 is not set # CONFIG_USB_STORAGE_SDDR55 is not set # CONFIG_USB_STORAGE_JUMPSHOT is not set # CONFIG_USB_ACM is not set # CONFIG_USB_PRINTER is not set CONFIG_USB_HID=y CONFIG_USB_HIDINPUT=y CONFIG_USB_HIDDEV=y # CONFIG_USB_AIPTEK is not set # CONFIG_USB_WACOM is not set # CONFIG_USB_KBTAB is not set # CONFIG_USB_POWERMATE is not set # CONFIG_USB_DC2XX is not set # CONFIG_USB_MDC800 is not set # CONFIG_USB_SCANNER is not set # CONFIG_USB_MICROTEK is not set # CONFIG_USB_HPUSBSCSI is not set # CONFIG_USB_PEGASUS is not set # CONFIG_USB_RTL8150 is not set # CONFIG_USB_KAWETH is not set # CONFIG_USB_CATC is not set # CONFIG_USB_CDCETHER is not set # CONFIG_USB_USBNET is not set # CONFIG_USB_USS720 is not set # # USB Serial Converter support # # CONFIG_USB_SERIAL is not set # CONFIG_USB_RIO500 is not set # CONFIG_USB_AUERSWALD is not set # CONFIG_USB_TIGL is not set # CONFIG_USB_BRLVGER is not set # CONFIG_USB_LCD is not set # # Support for USB gadgets # # CONFIG_USB_GADGET is not set # # Bluetooth support # # CONFIG_BLUEZ is not set # # Kernel hacking # # CONFIG_DEBUG_KERNEL is not set CONFIG_LOG_BUF_SHIFT=0 # # Cryptographic options # # CONFIG_CRYPTO is not set # # Library routines # CONFIG_CRC32=y CONFIG_ZLIB_INFLATE=y # CONFIG_ZLIB_DEFLATE is not set > > Cheers, > > Dave. > -- > Dave Chinner > R&D Software Enginner > SGI Australian Software Group > Thanks, Brice GIBOUDEAU From owner-linux-xfs@oss.sgi.com Thu Aug 4 15:29:10 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Aug 2005 15:29:15 -0700 (PDT) Received: from quail.cita.utoronto.ca (quail.cita.utoronto.ca [128.100.76.6]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j74MT9H9032728 for ; Thu, 4 Aug 2005 15:29:10 -0700 Received: from cita.utoronto.ca (lemming.cita.utoronto.ca [128.100.76.53]) by quail.cita.utoronto.ca (8.12.11/8.12.11) with ESMTP id j74MR5jk028094; Thu, 4 Aug 2005 18:27:05 -0400 Received: from lemming.cita.utoronto.ca (localhost [127.0.0.1]) by cita.utoronto.ca (8.13.4/8.13.4) with ESMTP id j74MR5tl007057; Thu, 4 Aug 2005 18:27:05 -0400 Received: (from rjh@localhost) by lemming.cita.utoronto.ca (8.13.4/8.13.4/Submit) id j74MR3TG007054; Thu, 4 Aug 2005 18:27:03 -0400 Date: Thu, 4 Aug 2005 18:27:03 -0400 From: Robin Humble To: Grant Denkinson Cc: linux-xfs@oss.sgi.com Subject: Re: Patches please for RHEL4 WS xfs Message-ID: <20050804222703.GB1922@lemming.cita.utoronto.ca> References: <1123144874.4097.20.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1123144874.4097.20.camel@localhost> User-Agent: Mutt/1.4.2.1i X-archive-position: 5721 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rjh@cita.utoronto.ca Precedence: bulk X-list: linux-xfs Status: O Content-Length: 728 Lines: 23 On Thu, Aug 04, 2005 at 09:41:14AM +0100, Grant Denkinson wrote: >I'm running Red Hat Enterprise Linux 4 WS with its standard >2.6.9-5.0.5.ELsmp kernel on a Dell PowerEdge 2650 (Dual Xeon). > >I'd like to run xfs on top of a logical volume made up of a couple of >hardware SCSI arrays. > >I understand there may be an issue with 4K stacks. I found a patch at >http://oss.sgi.com/archives/linux-xfs/2005-03/msg00189.html but this is >for AS not WS. The kernels for RHEL AS and WS appear to be identical. Certainly the .src.rpms have the same md5sum and same version numbers and I can't immeditately see any switches to config them differently in the spec file. Also: http://itinfo.mit.edu/answer.php?id=7783 cheers, robin From owner-linux-xfs@oss.sgi.com Thu Aug 4 15:36:47 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Aug 2005 15:36:51 -0700 (PDT) Received: from mail.linux-sxs.org (mail.linux-sxs.org [64.116.183.6]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j74MajH9001023 for ; Thu, 4 Aug 2005 15:36:46 -0700 Received: from mail.linux-sxs.org (localhost [127.0.0.1]) by mail.linux-sxs.org (8.13.4/8.13.4/Debian-3) with ESMTP id j74LVwbB004251 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Aug 2005 16:31:59 -0500 Received: from localhost (netllama@localhost) by mail.linux-sxs.org (8.13.4/8.13.4/Submit) with ESMTP id j74LVvRp004248; Thu, 4 Aug 2005 16:31:58 -0500 X-Authentication-Warning: mail.linux-sxs.org: netllama owned process doing -bs Date: Thu, 4 Aug 2005 16:31:57 -0500 (EST) From: Lonni J Friedman To: Robin Humble cc: linux-xfs@oss.sgi.com Subject: Re: Patches please for RHEL4 WS xfs In-Reply-To: <20050804222703.GB1922@lemming.cita.utoronto.ca> Message-ID: References: <1123144874.4097.20.camel@localhost> <20050804222703.GB1922@lemming.cita.utoronto.ca> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: milter-sender/0.62.837 (localhost [127.0.0.1]); Thu, 04 Aug 2005 16:31:59 -0500 Received-SPF: pass (mail.linux-sxs.org: domain of netllama@linux-sxs.org designates 127.0.0.1 as permitted sender) receiver=mail.linux-sxs.org; client-ip=127.0.0.1; helo=mail.linux-sxs.org; envelope-from=netllama@linux-sxs.org; x-software=spfmilter 0.95 http://www.acme.com/software/spfmilter/ with libspf2; X-archive-position: 5722 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 853 Lines: 23 On Thu, 4 Aug 2005, Robin Humble wrote: > On Thu, Aug 04, 2005 at 09:41:14AM +0100, Grant Denkinson wrote: > >I'm running Red Hat Enterprise Linux 4 WS with its standard > >2.6.9-5.0.5.ELsmp kernel on a Dell PowerEdge 2650 (Dual Xeon). > > > >I'd like to run xfs on top of a logical volume made up of a couple of > >hardware SCSI arrays. > > > >I understand there may be an issue with 4K stacks. I found a patch at > >http://oss.sgi.com/archives/linux-xfs/2005-03/msg00189.html but this is > >for AS not WS. > > The kernels for RHEL AS and WS appear to be identical. They are. RH uses the same kernel between all their EL offerings of the same version (v3, v4, etc). -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org LlamaLand http://netllama.linux-sxs.org From owner-linux-xfs@oss.sgi.com Thu Aug 4 17:43:16 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Aug 2005 17:43:23 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j750hEH9011298 for ; Thu, 4 Aug 2005 17:43:15 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA01096; Fri, 5 Aug 2005 10:41:00 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j750edol22463839; Fri, 5 Aug 2005 10:40:39 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j750ebLj22442391; Fri, 5 Aug 2005 10:40:37 +1000 (EST) Date: Fri, 5 Aug 2005 10:40:37 +1000 From: David Chinner To: Brice GIBOUDEAU Cc: linux-xfs@oss.sgi.com Subject: Re: XFS trouble. Message-ID: <20050805104037.A22198673@melbourne.sgi.com> References: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org> <20050804090050.B21661319@melbourne.sgi.com> <3088.194.2.155.29.1123145618.squirrel@www.pingus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3088.194.2.155.29.1123145618.squirrel@www.pingus.org>; from brice@pingus.org on Thu, Aug 04, 2005 at 10:53:38AM +0200 X-archive-position: 5723 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2707 Lines: 89 On Thu, Aug 04, 2005 at 10:53:38AM +0200, Brice GIBOUDEAU wrote: > Hi, > > I give more details. Ta. Looks like lowmem exhaustion: > /proc/meminfo : > --------------- > > Tue Aug 2 02:04:01 CEST 2005 > total: used: free: shared: buffers: cached: > Mem: 16966471680 15623704576 1342767104 0 180224 14847438848 > Swap: 32737632256 0 32737632256 > MemTotal: 16568820 kB > MemFree: 1311296 kB > MemShared: 0 kB > Buffers: 176 kB > Cached: 14499452 kB Large page cache... > SwapCached: 0 kB > Active: 1932 kB > Inactive: 14497760 kB Mostly inactive... > HighTotal: 15858532 kB > HighFree: 1305552 kB > LowTotal: 710288 kB > LowFree: 5744 kB And very little low memory free. > LowTotal: 710288 kB > LowFree: 4788 kB Yup, not much there at all. > /proc/slabinfo : > ---------------- > > Tue Aug 2 02:04:02 CEST 2005 > slabinfo - version: 1.1 (SMP) > xfs_inode 208657 208719 408 23191 23191 1 : 124 62 > linvfs_icache 208700 208700 384 20870 20870 1 : 124 62 > buffer_head 3624879 3751050 128 125034 125035 1 : 252 126 So we have 80MiB in xfs inodes, another 80MiB in linvfs_icache, and 460MiB in buffer heads. So that's a total of 620MiB of your 700MiB of low memory right there, and probably the source of the memory exhaustion. The buffer heads are the real problem - and that's related to the size of the page cache. IIRC we have at least one buffer head per page. With 14499452k of page cache, that's at least 3,624,863 buffer heads needed at one per page. Looks pretty close, to me. This does look like a highmem/lowmem reclaim issue to me - the pagecache in the highmem area needs to be reclaimed to free up buffer heads in the lowmem region. because there is lots of free memory in the highmem region, I doubt the reclaim code is freeing it up sufficiently. One quick thing to try is limit the machine to, say, 12GiB of RAM (mem=xxx boot option) and that will limit buffer head usage to less that 400MiB of low memory. That should prevent you from exhausting lowmem by bounding the maximum size of the kernel pagecache at a point below where lowmem exhaustion occurs. Another option is to go to a 2.6 kernel as, IIRC, XFS no longer has the buffer-head-per-cached-page behaviour in 2.6. Hence you won't consume anywhere near as much lowmem on a 2.6 kernel when the kernel lets the page cache grow so large.... Yet another option is to move to a 64bit platform that doesn't have this lowmem/highmem memory architecture... HTH. Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Thu Aug 4 22:51:54 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Aug 2005 22:52:00 -0700 (PDT) Received: from ASMET022.rail.nsw.gov.au (mail.ric.nsw.gov.au [203.41.133.81]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j755ppH9032533 for ; Thu, 4 Aug 2005 22:51:53 -0700 Received: from (10.100.10.91) by ASMET022.rail.nsw.gov.au via smtp id 6d6d_d03bea0e_0574_11da_9750_001143dc6559; Fri, 05 Aug 2005 15:50:22 +1000 Received: from msmet100.rail.nsw.gov.au ([10.35.6.45]) by MSSYDES99.rail.nsw.gov.au with Microsoft SMTPSVC(6.0.3790.0); Fri, 5 Aug 2005 15:47:56 +1000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: XFS and HP DataProtector - A possbile work-around Date: Fri, 5 Aug 2005 15:47:55 +1000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: XFS and HP DataProtector - A possbile work-around Thread-Index: AcWZgg+vevuS3d47TT6OkZuAz8DzCw== From: "Collaros, John" Importance: normal Priority: normal To: X-OriginalArrivalTime: 05 Aug 2005 05:47:56.0455 (UTC) FILETIME=[3AB2BB70:01C59981] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j755psH9032535 X-archive-position: 5724 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: John.Collaros@railcorp.nsw.gov.au Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1556 Lines: 33 Hi All I am replying to a thread I read dated 22/12/2003 . I have found a way to get data protector to be able to read the xfs file system. I am using Debian Linux, and the agents install into /usr/omni. On each host that uses the xfs file system, Inside /usr/omni/bin there is a hidden file .util Search for a section in sub getBdf (line 348 of this version which is A.05.10) The line is part of a case gpl/i386/inux) /bin/df -P -t ext2 -t ext -t minix -t xiafs -t reiserfs -t ext3 2>/dev/null | sed 'ld' | awk '{print $6}' ;; Just add -t xfs before the 2> and you'll see you Cell Manager will be able to see the filesystems. Hope this helps. John Collaros Network Engineer, Network Support Applications Communications & Control Systems RailCorp This e-mail and any attachments may contain confidential information that is intended solely for the use of the intended recipient and may be subject to copyright. If you receive this e-mail in error, please notify the sender immediately and delete the e-mail and its attachments from your system. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. Any opinion expressed in this e-mail and any attachments is not an opinion of RailCorp unless stated or apparent from its content. RailCorp is not responsible for any unauthorised alterations to this e-mail or any attachments. RailCorp will not incur any liability resulting directly or indirectly as a result of the recipient accessing any of the attached files that may contain a virus. From owner-linux-xfs@oss.sgi.com Fri Aug 5 02:10:37 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Aug 2005 02:10:44 -0700 (PDT) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j759APH9019314 for ; Fri, 5 Aug 2005 02:10:36 -0700 Received: from hch by pentafluge.infradead.org with local (Exim 4.52 #1 (Red Hat Linux)) id 1E0yBg-0001rD-9h; Fri, 05 Aug 2005 10:08:20 +0100 Date: Fri, 5 Aug 2005 10:08:20 +0100 From: Christoph Hellwig To: Al Boldi Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE 934766 - Delay direct I/O completion to a workqueue Message-ID: <20050805090820.GA6925@infradead.org> References: <200508031058.j73AwZFZ027123@naboo.americas.sgi.com> <200508040532.IAA21511@raad.intranet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200508040532.IAA21511@raad.intranet> User-Agent: Mutt/1.4.2.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html X-archive-position: 5725 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 146 Lines: 6 On Wed, Aug 03, 2005 at 05:31:58PM +0300, Al Boldi wrote: > Will this affect XFS behaviour with regards to the non-existent > Ordered-Mode? No. From owner-linux-xfs@oss.sgi.com Fri Aug 5 21:18:29 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Aug 2005 21:18:37 -0700 (PDT) Received: from raad.intranet (dial169-195.awalnet.net [213.184.169.195] (may be forged)) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j764IQH9015741 for ; Fri, 5 Aug 2005 21:18:28 -0700 Received: from i810 (ws159.intranet [10.0.0.159]) by raad.intranet (8.8.7/8.8.7) with ESMTP id HAA27397; Sat, 6 Aug 2005 07:14:07 +0300 Message-Id: <200508060414.HAA27397@raad.intranet> From: "Al Boldi" To: "'Christoph Hellwig'" Cc: Subject: RE: TAKE 934766 - Delay direct I/O completion to a workqueue Date: Sat, 6 Aug 2005 04:13:06 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20050805090820.GA6925@infradead.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Thread-Index: AcWaNl2mC1eoh8ZxTFG/7FR/mklGMAAE5OqQ X-archive-position: 5727 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: a1426z@gawab.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 356 Lines: 16 Christoph Hellwig wrote: { On Wed, Aug 03, 2005 at 05:31:58PM +0300, Al Boldi wrote: > Will this affect XFS behaviour with regards to the non-existent > Ordered-Mode? No. } Is there a way to coax XFS into doing something like ordered mode? I remember that this ordered-mode behaviour was available before XFS was added into the vanilla-Kernel! -- Al From owner-linux-xfs@oss.sgi.com Sun Aug 7 09:43:38 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 09:43:41 -0700 (PDT) Received: from barcikacomp.hu (adsl-174-227.adsl-fixip.axelero.hu [195.228.227.174]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j77GhbH9026993 for ; Sun, 7 Aug 2005 09:43:37 -0700 Received: from localhost (linux [127.0.0.1]) by barcikacomp.hu (Postfix) with ESMTP id 477A32FD29 for ; Sun, 7 Aug 2005 18:33:46 +0200 (CEST) Received: from barcikacomp.hu ([127.0.0.1]) by localhost (linux.barcikacomp.hu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03433-09 for ; Sun, 7 Aug 2005 18:33:42 +0200 (CEST) Received: from lsc.hu (client-121-22.kabelszatnet-2002.hu [195.38.121.22]) by barcikacomp.hu (Postfix) with ESMTP id B24392FC6D for ; Sun, 7 Aug 2005 18:33:41 +0200 (CEST) Subject: sdx problems From: Laszlo Boszormenyi To: linux-xfs@oss.sgi.com Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-WBkTW8vVbfmIRT47Hik1" Date: Sun, 07 Aug 2005 18:44:40 +0200 Message-Id: <1123433081.8928.17.camel@lsc.hu> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 X-archive-position: 5735 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: gcs@lsc.hu Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2007 Lines: 56 --=-WBkTW8vVbfmIRT47Hik1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, I'm using XFS for a very long time under Linux (was an Irix sysadmin too), but now I have some serious questions. One of my disks is failing, a 9Gb IBM SCSI disk. It seems that only the first some sectors have read-errors, including the primary superblock. :-( So I have imaged the disk with dd to a file, and run xfs_repair on it. It said: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... It found eight secondary superblocks, with the following messages: found candidate secondary superblock... unable to verify superblock, continuing... What does verify superblock means? I think it checks some offsets, that may not be correct because dd does not copy sectors with errors; so some sectors are missing from the beginning, moving all offsets closer to the beginning of the image. Anyone can confirm this? So all I may do is to find out this offset and put the exact number of bytes at the beginning of the image, right? Information about the system: - it's a PIII with onboard SCSI controller, - disk is an IBM SCSI one, 9 Gb, with only one partition with XFS, formatted under 2.6 AFAICR, - current kernel is 2.6.12, under Debian Sarge, so xfsprogs is 2.6.20. What other things should I try out? Thanks for any pointers in advance, Laszlo/GCS --=20 BorsodChem Joint-Stock Company www.debian.org Linux Support Center Software engineer Debian Developer Developer +36-48-511211/23-85 +36-20-4441745 --=-WBkTW8vVbfmIRT47Hik1 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBC9jp4MDatjqUaT90RAt50AJ9S0L05SlrWbCJT/Oni31exZ5sI1QCaAiD2 mnlscuIgSwZqzhhovvAQ8dM= =D6oJ -----END PGP SIGNATURE----- --=-WBkTW8vVbfmIRT47Hik1-- From owner-linux-xfs@oss.sgi.com Sun Aug 7 10:01:03 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 10:01:07 -0700 (PDT) Received: from marpa.dotforge.ch (marpa.dotforge.ch [212.147.103.250]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j77H12H9028403 for ; Sun, 7 Aug 2005 10:01:03 -0700 Received: from smtp.nofida.ch (unknown [81.13.177.141]) by marpa.dotforge.ch (Postfix) with ESMTP id 24ABD1B67E; Sun, 7 Aug 2005 18:58:50 +0200 (CEST) Received: by smtp.nofida.ch (Postfix, from userid 101) id AF35711AB0; Sun, 7 Aug 2005 18:58:45 +0200 (CEST) Received: from [192.168.74.20] (galadriel.nofida.ch [192.168.74.20]) by smtp.nofida.ch (Postfix) with ESMTP id 5AFAA11AAE; Sun, 7 Aug 2005 18:58:33 +0200 (CEST) Subject: Re: sdx problems From: Marcel de Riedmatten To: Laszlo Boszormenyi Cc: Linux xfs list In-Reply-To: <1123433081.8928.17.camel@lsc.hu> References: <1123433081.8928.17.camel@lsc.hu> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-K81vh2SDSYAqyYn+Prfj" Message-Id: <1123433913.4383.11.camel@galadriel.nofida.ch> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Sun, 07 Aug 2005 18:58:33 +0200 X-archive-position: 5736 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mdr@dotforge.ch Precedence: bulk X-list: linux-xfs Status: O Content-Length: 839 Lines: 35 --=-K81vh2SDSYAqyYn+Prfj Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: quoted-printable Le dim 07/08/2005 =E0 18:44, Laszlo Boszormenyi a =E9crit : > Hi, Hi > What other things should I try out? You want dd_rescue instead of dd. It will replace unreadable sectors with zeros so that offsets keep meaning something. http://www.garloff.de/kurt/linux/ddrescue --=20 Marcel de Riedmatten --=-K81vh2SDSYAqyYn+Prfj Content-Type: application/pgp-signature; name=signature.asc Content-Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBC9j24wEgIdc/nA8oRAnYXAJ4it7bu6Ds8GSiXm0i2XzTHpUGgOgCfeNmF ECUvU5PG6rDDVZoaUgtLTjM= =KGMP -----END PGP SIGNATURE----- --=-K81vh2SDSYAqyYn+Prfj-- From owner-linux-xfs@oss.sgi.com Sun Aug 7 12:09:41 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 12:09:45 -0700 (PDT) Received: from relay02.roc.ny.frontiernet.net (relay02.roc.ny.frontiernet.net [66.133.182.165]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j77J9eH9004323 for ; Sun, 7 Aug 2005 12:09:41 -0700 Received: from filter07.roc.ny.frontiernet.net (filter07.roc.ny.frontiernet.net [66.133.183.74]) by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id F22473701CF; Sun, 7 Aug 2005 19:07:33 +0000 (UTC) Received: from relay02.roc.ny.frontiernet.net ([66.133.182.165]) by filter07.roc.ny.frontiernet.net (filter07.roc.ny.frontiernet.net [66.133.183.74]) (amavisd-new, port 10024) with LMTP id 02436-07-84; Sun, 7 Aug 2005 19:07:33 +0000 (UTC) Received: from [192.168.1.65] (67-137-96-87.dsl2.brv.mn.frontiernet.net [67.137.96.87]) by relay02.roc.ny.frontiernet.net (Postfix) with ESMTP id BD5E637017F; Sun, 7 Aug 2005 19:07:11 +0000 (UTC) Message-ID: <42F65BE1.805@xfs.org> Date: Sun, 07 Aug 2005 14:07:13 -0500 From: Stephen Lord User-Agent: Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Al Boldi Cc: "'Christoph Hellwig'" , linux-xfs@oss.sgi.com Subject: Re: TAKE 934766 - Delay direct I/O completion to a workqueue References: <200508060414.HAA27397@raad.intranet> In-Reply-To: <200508060414.HAA27397@raad.intranet> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5737 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@xfs.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 626 Lines: 26 Al Boldi wrote: > Christoph Hellwig wrote: { > On Wed, Aug 03, 2005 at 05:31:58PM +0300, Al Boldi wrote: > >>Will this affect XFS behaviour with regards to the non-existent >>Ordered-Mode? > > > No. > } > > Is there a way to coax XFS into doing something like ordered mode? > > I remember that this ordered-mode behaviour was available before XFS was > added into the vanilla-Kernel! > > -- > Al > The journalling modes in ext3 are all inside the jdb layer and ext3, xfs has a completely different journalling implementation and I/O path. Getting xfs to do a data=ordered mode is a fairly fundamental change. Steve From owner-linux-xfs@oss.sgi.com Sun Aug 7 13:34:11 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 13:34:15 -0700 (PDT) Received: from barcikacomp.hu (adsl-174-227.adsl-fixip.axelero.hu [195.228.227.174]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j77KYAH9013260 for ; Sun, 7 Aug 2005 13:34:11 -0700 Received: from localhost (linux [127.0.0.1]) by barcikacomp.hu (Postfix) with ESMTP id BDDC22FD29 for ; Sun, 7 Aug 2005 22:24:17 +0200 (CEST) Received: from barcikacomp.hu ([127.0.0.1]) by localhost (linux.barcikacomp.hu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 10197-01 for ; Sun, 7 Aug 2005 22:24:13 +0200 (CEST) Received: from lsc.hu (client-121-22.kabelszatnet-2002.hu [195.38.121.22]) by barcikacomp.hu (Postfix) with ESMTP id 484D52FC6D for ; Sun, 7 Aug 2005 22:24:13 +0200 (CEST) Subject: Re: sdx problems From: Laszlo Boszormenyi To: Linux xfs list In-Reply-To: <1123433913.4383.11.camel@galadriel.nofida.ch> References: <1123433081.8928.17.camel@lsc.hu> <1123433913.4383.11.camel@galadriel.nofida.ch> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-lihy84JMaVXI8WMTIgeJ" Date: Sun, 07 Aug 2005 22:35:13 +0200 Message-Id: <1123446913.4240.3.camel@lsc.hu> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 X-archive-position: 5738 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: gcs@lsc.hu Precedence: bulk X-list: linux-xfs Status: O Content-Length: 900 Lines: 30 --=-lihy84JMaVXI8WMTIgeJ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2005-08-07 at 18:58 +0200, Marcel de Riedmatten wrote: > You want dd_rescue instead of dd. It will replace unreadable sectors > with zeros so that offsets keep meaning something. >=20 > http://www.garloff.de/kurt/linux/ddrescue Just for the record: it helped me out; the first eight sectors was shown up as unreadable, the rest was copied without problems. Then xfs_repair did its work correctly. Thank you very much! Laszlo/GCS --=-lihy84JMaVXI8WMTIgeJ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBC9nCBMDatjqUaT90RAvfJAJ94Y78B7nQnztnffM6/hUlV3CqPegCgmFmR eGdiETYPKlYA3xoZfjJxU3A= =H5ar -----END PGP SIGNATURE----- --=-lihy84JMaVXI8WMTIgeJ-- From owner-linux-xfs@oss.sgi.com Sun Aug 7 20:15:24 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 20:15:29 -0700 (PDT) Received: from mercury.acsalaska.net (mercury.acsalaska.net [209.112.173.226]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j783FOH9012344 for ; Sun, 7 Aug 2005 20:15:24 -0700 Received: from erbenson.alaska.net (66-230-90-89-dial-as4.nwc.acsalaska.net [66.230.90.89]) by mercury.acsalaska.net (8.13.4/8.13.4) with ESMTP id j783DFPH068302 for ; Sun, 7 Aug 2005 19:13:16 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 296AE3958 for ; Sun, 7 Aug 2005 18:55:36 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 26B5F40FF35; Sun, 7 Aug 2005 18:55:36 -0800 (AKDT) Date: Sun, 7 Aug 2005 18:55:36 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: XFS and AMD64 Message-ID: <20050808025536.GA2029@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.51; SA 3.0.3; spamdefang 1.113 X-archive-position: 5740 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1591 Lines: 49 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I am looking into building a high end multi-user host system, and as such it will require a great deal of memory (2-4+ GB). I would prefer to use a 64 bit architecture to avoid the pitfalls of 32bit+highmem. I also need i386 binary compatibility, as near as I can tell AMD64 looks like the best candidate. Since I need utmost i386 binary compatibility I would most likely need to run a 32 bit user-space with a 64 bit kernel. The Debian AMD64 pages claim this type of setup will work but certain configurations do not, one example they state is XFS. Can anyone elaborate as to what the issues are? I assume it has something to do with the XFS user-land tools not playing well with a 64 bit kernel (as opposed to 64 bit XFS user-land). Does anyone else have any experience with working with 64 bit architectures and XFS, particularly with 32 bit i386 user-land (or if you know of a hassle free way to get full i386 compatibility with mostly 64 bit user-land that would be nice too.). Any other recommendations/advice in regards to 64 bit architecture would be welcome as well. Thanks. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iEYEARECAAYFAkL2yacACgkQJKx7GixEevwSQACdEsl+v8wyVgUBINfv/OgJF140 eZ0An2DgHHd8DHdTsLUVfoYgutJ37gUE =bU2Z -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-linux-xfs@oss.sgi.com Sun Aug 7 22:35:54 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 22:35:56 -0700 (PDT) Received: from raad.intranet (dial169-205.awalnet.net [213.184.169.205] (may be forged)) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j785ZlH9028047 for ; Sun, 7 Aug 2005 22:35:52 -0700 Received: from ws159.intranet (ws159.intranet [10.0.0.159]) by raad.intranet (8.8.7/8.8.7) with ESMTP id IAA10141; Mon, 8 Aug 2005 08:33:44 +0300 From: Al Boldi To: Stephen Lord Subject: Re: TAKE 934766 - Delay direct I/O completion to a workqueue Date: Mon, 8 Aug 2005 08:20:16 +0300 User-Agent: KMail/1.5 Cc: linux-xfs@oss.sgi.com References: <200508060414.HAA27397@raad.intranet> <42F65BE1.805@xfs.org> In-Reply-To: <42F65BE1.805@xfs.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200508080820.16590.a1426z@gawab.com> X-archive-position: 5742 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: a1426z@gawab.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 358 Lines: 11 On Sunday 07 August 2005 10:07 pm, Stephen Lord wrote: > > The journalling modes in ext3 are all inside the jdb layer and > ext3, xfs has a completely different journalling implementation and > I/O path. Getting xfs to do a data=ordered mode is a fairly > fundamental change. > Still, what would be so hard to delay a metaData sync after a fileData sync? From owner-linux-xfs@oss.sgi.com Sun Aug 7 23:30:30 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Aug 2005 23:30:33 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j786UTH9031942 for ; Sun, 7 Aug 2005 23:30:30 -0700 Received: from p54B05F7C.dip.t-dialin.net [84.176.95.124] (helo=[172.17.8.5]) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKxQS-1E217W2C2l-00030m; Mon, 08 Aug 2005 08:28:22 +0200 Message-ID: <42F6FB86.3050608@online.de> Date: Mon, 08 Aug 2005 08:28:22 +0200 From: "u.schmeling" User-Agent: Mozilla Thunderbird 1.0 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS internal error xlog_valid_rec_header Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:4a225b4a0f08b207b61c9716b240a121 X-archive-position: 5743 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: u.schmeling@online.de Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1676 Lines: 42 Hi, have some XFS problems, running kernel 2.6.12.3, xfs on an enbd network raid1: Filesystem "md6": XFS internal error xlog_valid_rec_header(1) at line 3500 of file fs/xfs/xfs_log_recover.c. Caller 0xf89783d5 [] xlog_valid_rec_header+0x108/0x190 [xfs] [] xlog_do_recovery_pass+0x1b5/0xb80 [xfs] [] xlog_do_recovery_pass+0x1b5/0xb80 [xfs] [] __wake_up+0x3e/0x60 [] xlog_do_log_recovery+0x73/0xe0 [xfs] [] xlog_do_recover+0x3b/0x180 [xfs] [] xlog_recover+0xee/0x100 [xfs] [] xlog_alloc_log+0x25e/0x330 [xfs] [] xfs_log_mount+0x9d/0x130 [xfs] [] xfs_mountfs+0x909/0xea0 [xfs] [] .text.lock.xfs_buf+0x4b/0x51 [xfs] [] _atomic_dec_and_lock+0x2c/0x60 [] _spin_unlock+0xd/0x30 [] xfs_readsb+0x1b8/0x230 [xfs] [] xfs_ioinit+0x1c/0x30 [xfs] [] xfs_mount+0x2be/0x4c0 [xfs] [] vfs_mount+0x60/0x70 [xfs] [] vfs_mount+0x60/0x70 [xfs] [] linvfs_fill_super+0x9e/0x210 [xfs] [] snprintf+0x27/0x30 [] disk_name+0xb4/0xd0 [] sb_set_blocksize+0x2e/0x60 [] get_sb_bdev+0xe9/0x160 [] linvfs_get_sb+0x30/0x40 [xfs] [] linvfs_fill_super+0x0/0x210 [xfs] [] do_kern_mount+0x63/0xf0 [] do_new_mount+0x9e/0x100 [] do_mount+0x193/0x1d0 [] copy_mount_options+0x63/0xc0 [] sys_mount+0x9f/0xe0 [] sysenter_past_esp+0x54/0x75 XFS: log mount/recovery failed: error 990 Is a solution available for that, or is this combination known to not to work? regards Uwe From owner-linux-xfs@oss.sgi.com Mon Aug 8 02:28:23 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 02:28:32 -0700 (PDT) Received: from dy.hu (ns.dynamicweb.hu [195.228.155.139]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j789SJH9002438 for ; Mon, 8 Aug 2005 02:28:23 -0700 Received: from LocalHost (3e44b3e9.adsl.enternet.hu [62.68.179.233]) by dy.hu (8.12.8/8.12.8) with SMTP id j789U4iM011781 for ; Mon, 8 Aug 2005 11:30:04 +0200 From: djani22@dynamicweb.hu Message-ID: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> To: Subject: XFS repair problem. Date: Mon, 8 Aug 2005 11:25:27 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5744 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: djani22@dynamicweb.hu Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1956 Lines: 69 Hello all! I have a "big" filesystem (8TB), and a BIG problem! I can't fix it! [root@dy-base xfsprogs-2.5.6]# xfs_check /dev/md31 xfs_check: out of memory [root@dy-base xfsprogs-2.5.6]# free total used free shared buffers cached Mem: 4149468 4015820 133648 0 16 3718360 -/+ buffers/cache: 297444 3852024 Swap: 0 0 0 The xfs_check always do this, and I don't use it.... But, in this time, the xfs_repair is fails ALWAYS too! I have tryed it 23 times! The different results: 1. Simple segfault. 2. xfs_repair: dir2.c:1471: process_dir2_data: Assertion `(((irec_p)->ino_confirmed & ((__uint64_t)1 << ((ino_off)))) == 0LL ? 0: 1)' failed. 3. rebuilding directory inode 4211081386 xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. 4. xfs_repair: dino_chunks.c:594: process_inode_chunk: Assertion `((first_irec->ino_startnum) & ((__uint32_t)((1ULL << (((mp)->m_sb.sb_inopblog))) - 1))) == 0' failed. 5. - traversing filesystem starting at / ... xfs_repair: incore_ino.c:609: add_inode_reached: Assertion `ino_rec->ino_un.backptrs != ((void *)0)' failed. 6. - agno = 254 xfs_repair: dir2.c:1471: process_dir2_data: Assertion `(((irec_p)->ino_confirmed & ((__uint64_t)1 << ((ino_off)))) == 0LL ? 0: 1)' failed. 7. - agno = 254 xfs_repair: dir2.c:939: process_sf_dir2: Assertion `(((irec_p)->ino_confirmed & ((__uint64_t)1 << ((ino_off)))) == 0LL ? 0 : 1)' failed. The data on fs and the service is VERY important for me. The all logs is there: http://download.netcenter.hu/xfs/xfs.log.tar.gz (215kb) But unfortunately the first log is missing. Can you help me? The system: Dual xeon, 4G ram. The xfs is on RAID 0, 32k chunks OS: RH9.0, kernel 2.6.13-rc3 xfsprogs: xfsprogs-2.5.6-1.i386.rpm (sorry for my english) Thanks a lot! Janos [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Mon Aug 8 05:01:38 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 05:01:43 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j78C1bH9019837 for ; Mon, 8 Aug 2005 05:01:38 -0700 Received: (qmail invoked by alias); 08 Aug 2005 11:59:29 -0000 Received: from G0995.g.pppool.de (EHLO [192.168.10.11]) [80.185.9.149] by mail.gmx.net (mp011) with SMTP; 08 Aug 2005 13:59:29 +0200 X-Authenticated: #2986359 Message-ID: <42F74915.6060207@gmx.net> Date: Mon, 08 Aug 2005 13:59:17 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: Ethan Benson Subject: Re: XFS and AMD64 References: <20050808025536.GA2029@plato.local.lan> In-Reply-To: <20050808025536.GA2029@plato.local.lan> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5745 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 736 Lines: 22 Ethan Benson schrieb: > Does anyone else have any experience with working with 64 bit > architectures and XFS, particularly with 32 bit i386 user-land (or if > you know of a hassle free way to get full i386 compatibility with mostly 64 > bit user-land that would be nice too.). i'm running 64bit kernel+userland with a few 32bit-binary-only apps on an XFS rootfs. no difficulties so far. > recommendations/advice in regards to 64 bit architecture would be > welcome as well. if you really can't get a 32bit-binary to run, you can set up a 32bit userland chroot environment, there are many howtos about how to do that. but i have never used such a setup myself. Christian. -- BOFH excuse #254: Interference from lunar radiation From owner-linux-xfs@oss.sgi.com Mon Aug 8 05:11:33 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 05:11:42 -0700 (PDT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j78CBWH9020755 for ; Mon, 8 Aug 2005 05:11:33 -0700 Received: (qmail invoked by alias); 08 Aug 2005 12:09:24 -0000 Received: from G0995.g.pppool.de (EHLO [192.168.10.11]) [80.185.9.149] by mail.gmx.net (mp004) with SMTP; 08 Aug 2005 14:09:24 +0200 X-Authenticated: #2986359 Message-ID: <42F74B6D.8060002@gmx.net> Date: Mon, 08 Aug 2005 14:09:17 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: djani22@dynamicweb.hu Subject: Re: XFS repair problem. References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> In-Reply-To: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5746 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1204 Lines: 48 djani22@dynamicweb.hu schrieb: > Hello all! > > I have a "big" filesystem (8TB), and a BIG problem! > I can't fix it! > > [root@dy-base xfsprogs-2.5.6]# xfs_check /dev/md31 -------------------------^ please use current version of xfsprogs: ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-2.6.36.src.tar.gz > xfs_check: out of memory > [root@dy-base xfsprogs-2.5.6]# free > total used free shared buffers cached > Mem: 4149468 4015820 133648 0 16 3718360 > -/+ buffers/cache: 297444 3852024 > Swap: 0 0 0 does it help, if you enable some swapspace? > But, in this time, the xfs_repair is fails ALWAYS too! > I have tryed it 23 times! > > The different results: > > 1. Simple segfault. did you check for bad memory? an overnight run of memtest86+ could tell... > The data on fs and the service is VERY important for me. hm, how did you *backup* 8TB of data anyway? > Dual xeon, 4G ram. > The xfs is on RAID 0, 32k chunks any chance you can run top(1) next to xfs_repair to see how many memory is used? thanks, Christian. -- BOFH excuse #194: We only support a 1200 bps connection. From owner-linux-xfs@oss.sgi.com Mon Aug 8 07:52:47 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 07:52:56 -0700 (PDT) Received: from dy.hu (ns.dynamicweb.hu [195.228.155.139]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j78EqhH9002272 for ; Mon, 8 Aug 2005 07:52:46 -0700 Received: from LocalHost (3e44b3e9.adsl.enternet.hu [62.68.179.233]) by dy.hu (8.12.8/8.12.8) with SMTP id j78EsUiM021558 for ; Mon, 8 Aug 2005 16:54:30 +0200 From: djani22@dynamicweb.hu Message-ID: <014d01c59c28$744dae40$0400a8c0@LocalHost> To: Subject: Fw: XFS repair problem. Date: Mon, 8 Aug 2005 16:49:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 5748 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: djani22@dynamicweb.hu Precedence: bulk X-list: linux-xfs Status: O Content-Length: 3548 Lines: 140 ----- Original Message ----- From: To: "evilninja" Sent: Monday, August 08, 2005 3:55 PM Subject: Re: XFS repair problem. > ----- Original Message ----- > From: "evilninja" > To: > Cc: > Sent: Monday, August 08, 2005 2:09 PM > Subject: Re: XFS repair problem. > > > > djani22@dynamicweb.hu schrieb: > > > Hello all! > > > > > > I have a "big" filesystem (8TB), and a BIG problem! > > > I can't fix it! > > > > > > [root@dy-base xfsprogs-2.5.6]# xfs_check /dev/md31 > > -------------------------^ > > > > please use current version of xfsprogs: > > > > ftp://oss.sgi.com/projects/xfs/cmd_tars/xfsprogs-2.6.36.src.tar.gz > > OK, I try it! > > > > > > xfs_check: out of memory > > > [root@dy-base xfsprogs-2.5.6]# free > > > total used free shared buffers > cached > > > Mem: 4149468 4015820 133648 0 16 > 3718360 > > > -/+ buffers/cache: 297444 3852024 > > > Swap: 0 0 0 > > > > does it help, if you enable some swapspace? > > I can't. > No raw disks in this system. > Only the swap over the network is the possible way, but I dont think so.... > > > > > > But, in this time, the xfs_repair is fails ALWAYS too! > > > I have tryed it 23 times! > > > > > > The different results: > > > > > > 1. Simple segfault. > > > > did you check for bad memory? an overnight run of memtest86+ could tell... > > No, but this is a 14 day system, and before I start it, I have tested it, > witth this test. :-) > > In the system is 4GB DDR2 -ECC ram. > I don't think, it is the problem.... :-) > > And additionaly, only the xfs_repair generate segfaults... > > > > > > > The data on fs and the service is VERY important for me. > > > > hm, how did you *backup* 8TB of data anyway? > > Yes, you have right! > I don't use backup. > > This is a free web storage. > The service is more importanat, than data... :-/ > But I dont want to loose ~3000 webpages.... > > > > > > Dual xeon, 4G ram. > > > The xfs is on RAID 0, 32k chunks > > > > any chance you can run top(1) next to xfs_repair to see how many memory is > > used? > > Max 945MB > top line: > 17595 root 18 0 945M 941M 764 R 31.4 23.2 0:44 3 xfs_repair > > The new version: > > 1. time > > Phase 6 - check inode connectivity... > - resetting contents of realtime bitmap and summary inodes > - ensuring existence of lost+found directory > - traversing filesystem starting at / ... > - traversal finished ... > - traversing all unattached subtrees ... > rebuilding directory inode 4211081386 > xfs_repair: phase6.c:2603: longform_dir2_rebuild_finish: Assertion `error == > 0' failed. > > 2-3-4-5 times the end of log is the same: > rebuilding directory inode 4211081386 > xfs_repair: phase6.c:2603: longform_dir2_rebuild_finish: Assertion `error == > 0'failed. > > No segfault in this version. > > But the xfs_check's problem still here.... > [root@dy-base /]# /usr/local/bin/xfs_check /dev/md31 > xfs_check: out of memory > top: > Mem: 4149468k av, 192640k used, 3956828k free, 0k shrd, 0k > buff > 74608k active, 64068k inactive > Swap: 0k av, 0k used, 0k free 127160k > cached > > > How can I siply delete that inode? (4211081386) > > Thanks for all help! > > > > > thanks, > > Christian. > > -- > > BOFH excuse #194: > > > > We only support a 1200 bps connection. > From owner-linux-xfs@oss.sgi.com Mon Aug 8 10:41:07 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 10:41:15 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j78Hf5H9015738 for ; Mon, 8 Aug 2005 10:41:06 -0700 Received: (qmail invoked by alias); 08 Aug 2005 17:38:57 -0000 Received: from G0995.g.pppool.de (EHLO [192.168.10.11]) [80.185.9.149] by mail.gmx.net (mp009) with SMTP; 08 Aug 2005 19:38:57 +0200 X-Authenticated: #2986359 Message-ID: <42F798AF.5080505@gmx.net> Date: Mon, 08 Aug 2005 19:38:55 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: djani22@dynamicweb.hu Subject: Re: XFS repair problem References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> In-Reply-To: <00d801c59c20$e0354080$0400a8c0@LocalHost> X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5749 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1382 Lines: 51 djani22@dynamicweb.hu schrieb: > I can't. > No raw disks in this system. > Only the swap over the network is the possible way, but I dont think so.... you can use a swapfile too: % dd if=/dev/zero of=/var/.swap bs=1M count=1024 % mkswap /var/.swap % swapon /var/.swap > No, but this is a 14 day system, and before I start it, I have tested it, > witth this test. :-) > > In the system is 4GB DDR2 -ECC ram. > I don't think, it is the problem.... :-) ok. >>hm, how did you *backup* 8TB of data anyway? > > Yes, you have right! > I don't use backup. ouch :-\ > Max 945MB > top line: > 17595 root 18 0 945M 941M 764 R 31.4 23.2 0:44 3 xfs_repair maybe the xfs-gurus on this list can comment on that? is this normal? > How can I siply delete that inode? (4211081386) iirc xfs_db can do some magic with your xfs, but i've never used it on real data and can't recommend using it. sorry, but i'm not no xfs-expert and can't help you any further with the errors above. maybe opening a bug via http://oss.sgi.com/bugzilla/ could ring some attention. good luck, Christian. PS: and you might set a realname in your MUA: X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-GMX-Antispam: 5 (Score=1.338; FROM_ENDS_IN_NUMS NO_REAL_NAME) -- BOFH excuse #123: user to computer ratio too high. From owner-linux-xfs@oss.sgi.com Mon Aug 8 14:51:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 14:52:06 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j78LprH9000860 for ; Mon, 8 Aug 2005 14:51:58 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id HAA08090; Tue, 9 Aug 2005 07:49:31 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j78Ln2ol26087517; Tue, 9 Aug 2005 07:49:03 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j78LmxZZ26101920; Tue, 9 Aug 2005 07:48:59 +1000 (EST) Date: Tue, 9 Aug 2005 07:48:59 +1000 From: David Chinner To: evilninja Cc: linux-xfs@oss.sgi.com, djani22@dynamicweb.hu Subject: Re: XFS repair problem Message-ID: <20050809074858.B25981667@melbourne.sgi.com> References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <42F798AF.5080505@gmx.net>; from evilninja@gmx.net on Mon, Aug 08, 2005 at 07:38:55PM +0200 X-archive-position: 5752 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 514 Lines: 21 On Mon, Aug 08, 2005 at 07:38:55PM +0200, evilninja wrote: > djani22@dynamicweb.hu schrieb: > > > Max 945MB > > top line: > > 17595 root 18 0 945M 941M 764 R 31.4 23.2 0:44 3 xfs_repair > > maybe the xfs-gurus on this list can comment on that? is this normal? For large filesystems with lots of files in them, yes. It is not unusual to see xfs_repair consume multiple gigabytes of memory in this situation. Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Mon Aug 8 19:10:55 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Aug 2005 19:11:00 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j792ArH9022594 for ; Mon, 8 Aug 2005 19:10:54 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA14275; Tue, 9 Aug 2005 12:08:41 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7928Pol26589096; Tue, 9 Aug 2005 12:08:25 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7928Nbq26611444; Tue, 9 Aug 2005 12:08:23 +1000 (EST) Date: Tue, 9 Aug 2005 12:08:23 +1000 From: David Chinner To: djani22@dynamicweb.hu Cc: linux-xfs@oss.sgi.com Subject: Re: XFS repair problem Message-ID: <20050809120823.E13484145@melbourne.sgi.com> References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <20050809074858.B25981667@melbourne.sgi.com> <005301c59c7d$2eedab20$0400a8c0@LocalHost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <005301c59c7d$2eedab20$0400a8c0@LocalHost>; from djani22@dynamicweb.hu on Tue, Aug 09, 2005 at 02:56:28AM +0200 X-archive-position: 5754 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1126 Lines: 36 On Tue, Aug 09, 2005 at 02:56:28AM +0200, djani22@dynamicweb.hu wrote: > More info: > > I try xfs_check and xfs_ncheck (and more progs) with +200GB swap, but no > different! > less than 1 second and get : out of memory. Swap won't help if you're running an ia32 (32bit) kernel - you have a per-process memory limit of 1-4GiB (depending on kernel and config). The amount of physical memory and swap does not change this limitation. > It really looks like BUG! Expected behaviour. It's documented in the xfs_check(8) man page. > 2 months before when I try xfs_check with "only" 2TB, and only 2GB ram > system, it works! Memory consumption of the various xfs userspace tools is related to the size of the filesystem and the number of inodes in it. The larger the filesystem and the larger the number of inodes it has in it, the more memory is required to repair it. Your filesystem (8TiB) may simply bee too large for your system to be able to repair. Try mounting it on a 64bit system with more RAM in it and repairing it from there. Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Tue Aug 9 00:04:46 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 00:04:52 -0700 (PDT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7974jH9012784 for ; Tue, 9 Aug 2005 00:04:46 -0700 Received: from p54B043DA.dip.t-dialin.net [84.176.67.218] (helo=[172.17.8.5]) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0ML2Dk-1E2O8D0htP-0002au; Tue, 09 Aug 2005 09:02:37 +0200 Message-ID: <42F8550C.80305@online.de> Date: Tue, 09 Aug 2005 09:02:36 +0200 From: "u.schmeling" User-Agent: Mozilla Thunderbird 1.0 (X11/20041207) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS internal error xlog_valid_rec_header Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:4a225b4a0f08b207b61c9716b240a121 X-archive-position: 5756 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: u.schmeling@online.de Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1642 Lines: 42 Hi, have some XFS problems, running kernel 2.6.12.3, xfs on an enbd network raid1: Filesystem "md6": XFS internal error xlog_valid_rec_header(1) at line 3500 of file fs/xfs/xfs_log_recover.c. Caller 0xf89783d5 [] xlog_valid_rec_header+0x108/0x190 [xfs] [] xlog_do_recovery_pass+0x1b5/0xb80 [xfs] [] xlog_do_recovery_pass+0x1b5/0xb80 [xfs] [] __wake_up+0x3e/0x60 [] xlog_do_log_recovery+0x73/0xe0 [xfs] [] xlog_do_recover+0x3b/0x180 [xfs] [] xlog_recover+0xee/0x100 [xfs] [] xlog_alloc_log+0x25e/0x330 [xfs] [] xfs_log_mount+0x9d/0x130 [xfs] [] xfs_mountfs+0x909/0xea0 [xfs] [] .text.lock.xfs_buf+0x4b/0x51 [xfs] [] _atomic_dec_and_lock+0x2c/0x60 [] _spin_unlock+0xd/0x30 [] xfs_readsb+0x1b8/0x230 [xfs] [] xfs_ioinit+0x1c/0x30 [xfs] [] xfs_mount+0x2be/0x4c0 [xfs] [] vfs_mount+0x60/0x70 [xfs] [] vfs_mount+0x60/0x70 [xfs] [] linvfs_fill_super+0x9e/0x210 [xfs] [] snprintf+0x27/0x30 [] disk_name+0xb4/0xd0 [] sb_set_blocksize+0x2e/0x60 [] get_sb_bdev+0xe9/0x160 [] linvfs_get_sb+0x30/0x40 [xfs] [] linvfs_fill_super+0x0/0x210 [xfs] [] do_kern_mount+0x63/0xf0 [] do_new_mount+0x9e/0x100 [] do_mount+0x193/0x1d0 [] copy_mount_options+0x63/0xc0 [] sys_mount+0x9f/0xe0 [] sysenter_past_esp+0x54/0x75 XFS: log mount/recovery failed: error 990 Is a solution available for that, or is this combination known to not to work? regards Uwe From owner-linux-xfs@oss.sgi.com Tue Aug 9 01:05:11 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 01:05:17 -0700 (PDT) Received: from soloth.lewis.org (soloth.lewis.org [69.28.69.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7985AH9019959 for ; Tue, 9 Aug 2005 01:05:11 -0700 Received: from soloth.lewis.org (localhost.localdomain [127.0.0.1]) by soloth.lewis.org (8.12.11/8.12.11) with ESMTP id j79832qr022879 for ; Tue, 9 Aug 2005 04:03:02 -0400 Received: from localhost (jlewis@localhost) by soloth.lewis.org (8.12.11/8.12.11/Submit) with ESMTP id j79832Bv022875 for ; Tue, 9 Aug 2005 04:03:02 -0400 X-Authentication-Warning: soloth.lewis.org: jlewis owned process doing -bs Date: Tue, 9 Aug 2005 04:03:02 -0400 (EDT) From: Jon Lewis To: linux-xfs Subject: xfs and nfs on 2.4 kernels? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5757 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlewis@lewis.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 876 Lines: 17 Are there any known issues with XFS and NFS in 2.4? I just had a server (running and old kernel) lock up and get upgraded to 2.4.31-xfscvs20050617 (it's been running on our test server almost 2 months) on reboot. After the reboot, the two NFS clients of this server were having serious issues. They could ls the exported/mounted directory, but could not read files or directories within that directory. Attempts to do so would result in "Stale NFS file handle" errors. After a bunch of reboots on the server and clients, NFS mostly works, but still gives occasional Stale NFS file handle errors. ---------------------------------------------------------------------- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ From owner-linux-xfs@oss.sgi.com Tue Aug 9 07:44:02 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 07:44:11 -0700 (PDT) Received: from pingus.pingus.org (pingus.pingus.org [82.66.123.179]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j79Ei0H9014751 for ; Tue, 9 Aug 2005 07:44:01 -0700 Received: from www.pingus.org (localhost [127.0.0.1]) by pingus.pingus.org (Postfix) with ESMTP id 16CA840470; Tue, 9 Aug 2005 16:41:45 +0200 (CEST) Received: from 194.2.155.16 (SquirrelMail authenticated user brice) by www.pingus.org with HTTP; Tue, 9 Aug 2005 16:41:45 +0200 (CEST) Message-ID: <39182.194.2.155.16.1123598505.squirrel@www.pingus.org> In-Reply-To: <20050805104037.A22198673@melbourne.sgi.com> References: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org> <20050804090050.B21661319@melbourne.sgi.com> <3088.194.2.155.29.1123145618.squirrel@www.pingus.org> <20050805104037.A22198673@melbourne.sgi.com> Date: Tue, 9 Aug 2005 16:41:45 +0200 (CEST) Subject: Re: XFS trouble. From: "Brice GIBOUDEAU" To: "David Chinner" Cc: "Brice GIBOUDEAU" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5759 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: brice@pingus.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 3177 Lines: 106 Hi, Thanks for all this informations. I'm testing an other solution, it's using a patch who increase the quantity of low memory. http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.23pre6aa3/00_3.5G-address-space-5 http://lwn.net/Articles/39925/ I will reply to this Email if the patch work correctly. Thx, Brice GIBOUDEAU > On Thu, Aug 04, 2005 at 10:53:38AM +0200, Brice GIBOUDEAU wrote: >> Hi, >> >> I give more details. > > Ta. Looks like lowmem exhaustion: > >> /proc/meminfo : >> --------------- >> >> Tue Aug 2 02:04:01 CEST 2005 >> total: used: free: shared: buffers: cached: >> Mem: 16966471680 15623704576 1342767104 0 180224 14847438848 >> Swap: 32737632256 0 32737632256 >> MemTotal: 16568820 kB >> MemFree: 1311296 kB >> MemShared: 0 kB >> Buffers: 176 kB >> Cached: 14499452 kB > > Large page cache... > >> SwapCached: 0 kB >> Active: 1932 kB >> Inactive: 14497760 kB > > Mostly inactive... > >> HighTotal: 15858532 kB >> HighFree: 1305552 kB >> LowTotal: 710288 kB >> LowFree: 5744 kB > > And very little low memory free. > >> LowTotal: 710288 kB >> LowFree: 4788 kB > > Yup, not much there at all. > >> /proc/slabinfo : >> ---------------- >> >> Tue Aug 2 02:04:02 CEST 2005 >> slabinfo - version: 1.1 (SMP) >> xfs_inode 208657 208719 408 23191 23191 1 : 124 62 >> linvfs_icache 208700 208700 384 20870 20870 1 : 124 62 >> buffer_head 3624879 3751050 128 125034 125035 1 : 252 126 > > So we have 80MiB in xfs inodes, another 80MiB in linvfs_icache, and > 460MiB in buffer heads. So that's a total of 620MiB of your 700MiB > of low memory right there, and probably the source of the memory > exhaustion. > > The buffer heads are the real problem - and that's related to the > size of the page cache. IIRC we have at least one buffer head per > page. With 14499452k of page cache, that's at least 3,624,863 buffer > heads needed at one per page. Looks pretty close, to me. > > This does look like a highmem/lowmem reclaim issue to me - the > pagecache in the highmem area needs to be reclaimed to free > up buffer heads in the lowmem region. because there is lots > of free memory in the highmem region, I doubt the reclaim > code is freeing it up sufficiently. > > One quick thing to try is limit the machine to, say, 12GiB of RAM > (mem=xxx boot option) and that will limit buffer head usage to less > that 400MiB of low memory. That should prevent you from exhausting > lowmem by bounding the maximum size of the kernel pagecache at > a point below where lowmem exhaustion occurs. > > Another option is to go to a 2.6 kernel as, IIRC, XFS no longer > has the buffer-head-per-cached-page behaviour in 2.6. Hence you > won't consume anywhere near as much lowmem on a 2.6 kernel when > the kernel lets the page cache grow so large.... > > Yet another option is to move to a 64bit platform that doesn't have > this lowmem/highmem memory architecture... > > HTH. > > Cheers, > > Dave. > -- > Dave Chinner > R&D Software Enginner > SGI Australian Software Group > From owner-linux-xfs@oss.sgi.com Tue Aug 9 09:41:40 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 09:41:45 -0700 (PDT) Received: from soloth.lewis.org (soloth.lewis.org [69.28.69.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j79GfdH9027340 for ; Tue, 9 Aug 2005 09:41:40 -0700 Received: from soloth.lewis.org (localhost.localdomain [127.0.0.1]) by soloth.lewis.org (8.12.11/8.12.11) with ESMTP id j79GdVLo025889 for ; Tue, 9 Aug 2005 12:39:31 -0400 Received: from localhost (jlewis@localhost) by soloth.lewis.org (8.12.11/8.12.11/Submit) with ESMTP id j79GdVaY025885 for ; Tue, 9 Aug 2005 12:39:31 -0400 X-Authentication-Warning: soloth.lewis.org: jlewis owned process doing -bs Date: Tue, 9 Aug 2005 12:39:31 -0400 (EDT) From: Jon Lewis To: linux-xfs Subject: Re: xfs and nfs on 2.4 kernels? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5760 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlewis@lewis.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1529 Lines: 30 On Tue, 9 Aug 2005, Jon Lewis wrote: > Are there any known issues with XFS and NFS in 2.4? I just had a server > (running and old kernel) lock up and get upgraded to 2.4.31-xfscvs20050617 > (it's been running on our test server almost 2 months) on reboot. After the > reboot, the two NFS clients of this server were having serious issues. They > could ls the exported/mounted directory, but could not read files or > directories within that directory. Attempts to do so would result in "Stale > NFS file handle" errors. > > After a bunch of reboots on the server and clients, NFS mostly works, but > still gives occasional Stale NFS file handle errors. We eventually found that even after we thought it was "mostly working" it really wasn't. Only the failure mode had changed from "Stale NFS file handle" and an inability to access below the mounted directory to full directory traversal, but i/o errors when trying to read files. We ended up having to downgrade to an older kernel. I did a cvs recheckout, and I see there have been xfs changes in 2.4 in the past two months, but I'm very hesitant to try again unless its known that XFS+NFS was broken in CVS 2-3 months ago and is believed to be fixed now. Had anyone else run into this? ---------------------------------------------------------------------- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ From owner-linux-xfs@oss.sgi.com Tue Aug 9 13:12:49 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 13:12:57 -0700 (PDT) Received: from mail1.catalyst.net.nz (godel.catalyst.net.nz [202.78.240.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j79KCmH9018092 for ; Tue, 9 Aug 2005 13:12:49 -0700 Received: from leibniz.catalyst.net.nz ([202.78.240.7] helo=[192.168.2.99]) by mail1.catalyst.net.nz with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1E2aQm-0004Rn-Ec for linux-xfs@oss.sgi.com; Wed, 10 Aug 2005 08:10:36 +1200 Message-ID: <42F90DC5.9070702@catalyst.net.nz> Date: Wed, 10 Aug 2005 08:10:45 +1200 From: Steve Wray User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: XFS repair problem References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <20050809074858.B25981667@melbourne.sgi.com> <005301c59c7d$2eedab20$0400a8c0@LocalHost> <20050809120823.E13484145@melbourne.sgi.com> In-Reply-To: <20050809120823.E13484145@melbourne.sgi.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-archive-position: 5761 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stevew-lists@catalyst.net.nz Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1030 Lines: 28 David Chinner wrote: > On Tue, Aug 09, 2005 at 02:56:28AM +0200, djani22@dynamicweb.hu wrote: > >>More info: >> >>I try xfs_check and xfs_ncheck (and more progs) with +200GB swap, but no >>different! >>less than 1 second and get : out of memory. > [snip] > Your filesystem (8TiB) may simply bee too large for your system to > be able to repair. Try mounting it on a 64bit system with more RAM > in it and repairing it from there. Sorry, but is this a joke? Just checking because it seems quite unhelpful to suggest that one should remove a drive and install it in a machine with a fairly specific hardware spec to repair a filesystem. Surely xfs could/should have a repair mode that actually works on the hardware that the filesystem is installed on? Alternatively, so that others can avoid the situation of having to go and get their hands on a 64 bit machine to repair their xfs filesystems, is there a cutoff point heuristic? Ie: how big does an xfs filesystem have to be for it to require a 64 bit architecture to fix? From owner-linux-xfs@oss.sgi.com Tue Aug 9 21:20:08 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 21:20:11 -0700 (PDT) Received: from dedicated.mountainviewdata.com (207-234-129-26.ptr.primarydns.com [207.234.129.26]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7A4K7H9025338 for ; Tue, 9 Aug 2005 21:20:08 -0700 Received: from allanlaptop (unknown [219.237.156.28]) by dedicated.mountainviewdata.com (Postfix) with ESMTP id 33DED9FDF7 for ; Tue, 9 Aug 2005 21:12:40 -0700 (PDT) From: "Tang Lingbo (Allan)" To: Subject: XFS report error on LVM snapshot Date: Wed, 10 Aug 2005 12:17:24 +0800 Organization: Mountain View Data, Inc. Message-ID: <003d01c59d62$70c59540$0209010a@winauth.cn.mvd> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-archive-position: 5765 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: allan@mountainviewdata.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 911 Lines: 34 Hi, I get error message when I try to use LVM snapshot with XFS. === error message === XFS mounting filesystem lvm(58,4) Ending clean XFS mount for filesystem: lvm(58,4) lvm - lvm_map: ll_rw_blk write for readonly LV /dev/vg0/test21 xfs_force_shutdown(lvm(58,4),0x1) called from line 353 of file xfs_rw.c. Return address = 0xc026ad2b Filesystem "lvm(58,4)": I/O Error Detected. Shutting down filesystem: lvm(58,4) Please umount the filesystem, and rectify the problem(s) XFS mounting filesystem lvm(58,4) Ending clean XFS mount for filesystem: lvm(58,4) =================== Operations: 1. make XFS on LVM and do some changes; 2. add snap LV for file system; 3. mount the snapshot LV under original file system with option "ro,nouuid"; System: kernel-2.4.21-27.0.2.EL.sgi9.i686.rpm xfs-modules-1.3.3-2.4.21_27.0.2.EL.sgi9.i686.rpm Could you give some idea to remove the messages? Thanks! Regards, Allan From owner-linux-xfs@oss.sgi.com Tue Aug 9 23:59:30 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Aug 2005 23:59:35 -0700 (PDT) Received: from twinlark.arctic.org (twinlark.arctic.org [207.7.145.18]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7A6xUH9005530 for ; Tue, 9 Aug 2005 23:59:30 -0700 Received: (qmail 9273 invoked from network); 10 Aug 2005 06:57:21 -0000 Received: from unknown (HELO localhost) (127.0.0.1) by 127.0.0.1 with ESMTPS (AES256-SHA); 10 Aug 2005 06:57:21 -0000 Date: Tue, 9 Aug 2005 23:57:21 -0700 (PDT) From: dean gaudet To: "Tang Lingbo (Allan)" cc: linux-xfs@oss.sgi.com Subject: Re: XFS report error on LVM snapshot In-Reply-To: <003d01c59d62$70c59540$0209010a@winauth.cn.mvd> Message-ID: References: <003d01c59d62$70c59540$0209010a@winauth.cn.mvd> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 5766 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dean-list-linux-xfs@arctic.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1053 Lines: 32 On Wed, 10 Aug 2005, Tang Lingbo (Allan) wrote: > Hi, > > I get error message when I try to use LVM snapshot with XFS. > > === error message === > XFS mounting filesystem lvm(58,4) > Ending clean XFS mount for filesystem: lvm(58,4) > lvm - lvm_map: ll_rw_blk write for readonly LV /dev/vg0/test21 > xfs_force_shutdown(lvm(58,4),0x1) called from line 353 of file xfs_rw.c. > Return address = 0xc026ad2b > Filesystem "lvm(58,4)": I/O Error Detected. Shutting down filesystem: > lvm(58,4) > Please umount the filesystem, and rectify the problem(s) > XFS mounting filesystem lvm(58,4) > Ending clean XFS mount for filesystem: lvm(58,4) > > =================== yeah this is the same thing i reported in bugzilla: http://oss.sgi.com/bugzilla/show_bug.cgi?id=413 unfortunately i've found xfs+snapshots to be completely unusable on any filesystem with non-trivial workload -- no data corruption (yet), but the snapshot fails regularly. see also: http://oss.sgi.com/bugzilla/show_bug.cgi?id=412 http://oss.sgi.com/bugzilla/show_bug.cgi?id=414 -dean From owner-linux-xfs@oss.sgi.com Wed Aug 10 02:01:30 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 02:01:38 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7A91TH9017536 for ; Wed, 10 Aug 2005 02:01:30 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA20859; Wed, 10 Aug 2005 18:59:13 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7A8wqol28001401; Wed, 10 Aug 2005 18:58:52 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7A8wnrq28099629; Wed, 10 Aug 2005 18:58:49 +1000 (EST) Date: Wed, 10 Aug 2005 18:58:49 +1000 From: David Chinner To: Steve Wray Cc: linux-xfs@oss.sgi.com Subject: Re: XFS repair problem Message-ID: <20050810185849.A27595508@melbourne.sgi.com> References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <20050809074858.B25981667@melbourne.sgi.com> <005301c59c7d$2eedab20$0400a8c0@LocalHost> <20050809120823.E13484145@melbourne.sgi.com> <42F90DC5.9070702@catalyst.net.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <42F90DC5.9070702@catalyst.net.nz>; from stevew-lists@catalyst.net.nz on Wed, Aug 10, 2005 at 08:10:45AM +1200 X-archive-position: 5767 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 3222 Lines: 83 On Wed, Aug 10, 2005 at 08:10:45AM +1200, Steve Wray wrote: > David Chinner wrote: > > On Tue, Aug 09, 2005 at 02:56:28AM +0200, djani22@dynamicweb.hu wrote: > > > >>More info: > >> > >>I try xfs_check and xfs_ncheck (and more progs) with +200GB swap, but no > >>different! > >>less than 1 second and get : out of memory. > > > [snip] > > Your filesystem (8TiB) may simply bee too large for your system to > > be able to repair. Try mounting it on a 64bit system with more RAM > > in it and repairing it from there. > > Sorry, but is this a joke? A joke? Absolutely not. Acheivable XFS filesystem sizes outgrew the capability of 32 bit Irix systems to repair them several years ago. Now that linux supports larger than 2TiB filesystems on 32 bit systems, this is true for Linux as well. FWIW, look at the irix man pages for xfs_check and xfs_repair: http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=man&fname=/usr/share/catman/a_man/cat1/xfs_check.z&srch=xfs_check http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi?coll=0650&db=man&fname=/usr/share/catman/a_man/cat1/xfs_repair.z&srch=xfs_repair A quote so you don't have to follow the links: xfs_repair is an n32 binary and will run on all Irix platforms. However, when repairing a multi-terabyte filesystem, the memory requirements exceed what is available to n32 binaries. For those filesystems, xfs_repair64, 64-bit binary, should be used. This has also been mentioned before on this list in similar circumstances: http://marc.theaimsgroup.com/?l=linux-xfs&m=109890988924676&w=2 As for moving disks to other machines to repair them - that's not unusual, either. e.g: http://marc.theaimsgroup.com/?l=linux-xfs&m=107435532601553&w=2 > Surely xfs could/should have a repair mode that actually works on the > hardware that the filesystem is installed on? Surely it could. When can we expect a patch? ;) > Alternatively, so that others can avoid the situation of having to go > and get their hands on a 64 bit machine to repair their xfs filesystems, > is there a cutoff point heuristic? Ie: how big does an xfs filesystem > have to be for it to require a 64 bit architecture to fix? From some quick tests I just ran, for 32bit binaries xfs_check needs around 1GiB RAM per TiB of filesystem plus about 100MiB RAM per 1million inodes in the filesystem (more if you have lots of fragmented files). Double this for 64bit binaries. e.g. it took 1.5GiB RAM for 32bit xfs_check and 2.7GiB RAM for a 64bit xfs_check on a 1.1TiB filesystem with 3million inodes in it. For xfs_repair, there is no one-size fits all formula as memory consumption depends not only on the size of the filesystem but what is in the filesystem, how it is laid out, what is corrupted in the filesystem, etc. For example, the filesystem I checked above only required ~150MiB for repair to run but that is a consistent filesystem. I've seen equivalently size filesystems (~1TiB) take close to 1GiB of RAM to repair when they've been significantly corrupted. Sorry I can't be more precise than this, but it should give you some idea of what to expect.... Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Wed Aug 10 06:25:45 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 06:25:49 -0700 (PDT) Received: from mx2.suse.de (ns2.suse.de [195.135.220.15]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7ADPiH9003182 for ; Wed, 10 Aug 2005 06:25:45 -0700 Received: from Relay2.suse.de (mail2.suse.de [195.135.221.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.suse.de (Postfix) with ESMTP id 56EED1D573; Wed, 10 Aug 2005 15:23:34 +0200 (CEST) Received: from verdi.suse.de (verdi.suse.de [10.11.0.38]) by Relay2.suse.de (Postfix) with ESMTP id 49DC616CA7; Wed, 10 Aug 2005 15:23:33 +0200 (CEST) To: Ethan Benson Cc: linux-xfs@oss.sgi.com Subject: Re: XFS and AMD64 References: <20050808025536.GA2029@plato.local.lan> From: Andi Kleen Date: 10 Aug 2005 15:23:32 +0200 In-Reply-To: <20050808025536.GA2029@plato.local.lan> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 5768 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs Status: O Content-Length: 522 Lines: 14 Ethan Benson writes: > > Since I need utmost i386 binary compatibility I would most likely need > to run a 32 bit user-space with a 64 bit kernel. The Debian AMD64 > pages claim this type of setup will work but certain configurations do > not, one example they state is XFS. There is a problem when a unclean log from the 32bit kernel is replayed on the 64bit kernel (or the other way round). Just make sure you always have clean unmounts when you switch between 32bit and 64bit kernels. -Andi From owner-linux-xfs@oss.sgi.com Wed Aug 10 10:06:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 10:07:03 -0700 (PDT) Received: from smtpout02-04.prod.mesa1.secureserver.net (smtpout02-04.prod.mesa1.secureserver.net [64.202.165.194]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7AH6wH9021288 for ; Wed, 10 Aug 2005 10:06:59 -0700 Received: (qmail 7630 invoked from network); 10 Aug 2005 17:04:48 -0000 Received: from unknown (64.253.100.129) by smtpout02-04.prod.mesa1.secureserver.net (64.202.165.194) with ESMTP; 10 Aug 2005 17:04:47 -0000 Message-ID: <000601c59dce$44c08a60$9601a8c0@webajm.local> From: "Adam Marx" To: Subject: XFS - hard drive dying Date: Wed, 10 Aug 2005 13:09:27 -0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5771 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: A.Marx@webajm.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2041 Lines: 43 I'm experiencing some problems with my XFS filesystem mainly due to a drive that is crashing. The system had been very stable and nothing has been changed. This is some of the information from dmsg: XFS mounting filesystem dm-0 Starting XFS recovery on filesystem: dm-0 (dev: dm-0) hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08001 ("xfs_trans_read_buf") error 5 buf count 512 xfs_force_shutdown(dm-0,0x1) called from line 422 of file fs/xfs/xfs_trans_buf.c. Return address = 0xe2e521b4 Filesystem "dm-0": I/O Error Detected. Shutting down filesystem: dm-0 Please umount the filesystem, and rectify the problem(s) hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#1)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown ..... I tried to do a repair on the XFS system for information first and it generated the following: [root@myth ~]# xfs_repair -n /dev/VGforMyth/video Phase 1 - find and verify superblock... superblock read failed, offset 342003548160, size 2048, ag 4294967295, rval 36 fatal error -- Input/output error This drive is still under warranty and I want to recover any information from the drive that is possible before sending off for replacement. Any help or suggestions would be greatly appreciated. Thanks. Adam, [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Wed Aug 10 10:20:14 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 10:20:19 -0700 (PDT) Received: from lucidpixels.com (lucidpixels.com [66.45.37.187]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7AHKDH9022404 for ; Wed, 10 Aug 2005 10:20:13 -0700 Received: by lucidpixels.com (Postfix, from userid 1001) id 601EF201062F; Wed, 10 Aug 2005 13:18:00 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by lucidpixels.com (Postfix) with ESMTP id 89D08A0037EB; Wed, 10 Aug 2005 13:18:00 -0400 (EDT) Date: Wed, 10 Aug 2005 13:17:59 -0400 (EDT) From: Justin Piszcz X-X-Sender: jpiszcz@p34 To: Adam Marx cc: linux-xfs@oss.sgi.com Subject: Re: XFS - hard drive dying In-Reply-To: <000601c59dce$44c08a60$9601a8c0@webajm.local> Message-ID: References: <000601c59dce$44c08a60$9601a8c0@webajm.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5772 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jpiszcz@lucidpixels.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2347 Lines: 53 You can try putting it in the freezer for an hour or so, then hooking it up immediately and attempting to either dd the drive or mount/repair it and copy the data off immediately. Justin. On Wed, 10 Aug 2005, Adam Marx wrote: > > I'm experiencing some problems with my XFS filesystem mainly due to a drive that is crashing. The system had been very stable and nothing has been changed. This is some of the information from dmsg: > > XFS mounting filesystem dm-0 > Starting XFS recovery on filesystem: dm-0 (dev: dm-0) > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 > ide: failed opcode was: unknown > end_request: I/O error, dev hdd, sector 371098047 > I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08001 ("xfs_trans_read_buf") error 5 buf count 512 > xfs_force_shutdown(dm-0,0x1) called from line 422 of file fs/xfs/xfs_trans_buf.c. Return address = 0xe2e521b4 > Filesystem "dm-0": I/O Error Detected. Shutting down filesystem: dm-0 > Please umount the filesystem, and rectify the problem(s) > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 > ide: failed opcode was: unknown > end_request: I/O error, dev hdd, sector 371098047 > I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#1)") error 5 buf count 512 > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 > ide: failed opcode was: unknown > ..... > > I tried to do a repair on the XFS system for information first and it generated the following: > > [root@myth ~]# xfs_repair -n /dev/VGforMyth/video > Phase 1 - find and verify superblock... > superblock read failed, offset 342003548160, size 2048, ag 4294967295, rval 36 > > fatal error -- Input/output error > > > This drive is still under warranty and I want to recover any information from the drive that is possible before sending off for replacement. Any help or suggestions would be greatly appreciated. > > Thanks. > > Adam, > > > > > [[HTML alternate version deleted]] > > From owner-linux-xfs@oss.sgi.com Wed Aug 10 14:59:44 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 14:59:48 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7ALxhH9011442 for ; Wed, 10 Aug 2005 14:59:43 -0700 Received: (qmail invoked by alias); 10 Aug 2005 21:57:32 -0000 Received: from G03aa.g.pppool.de (EHLO [192.168.10.11]) [80.185.3.170] by mail.gmx.net (mp017) with SMTP; 10 Aug 2005 23:57:32 +0200 X-Authenticated: #2986359 Message-ID: <42FA784A.2050301@gmx.net> Date: Wed, 10 Aug 2005 23:57:30 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: XFS and AMD64 References: <20050808025536.GA2029@plato.local.lan> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5776 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 719 Lines: 21 Andi Kleen schrieb: > > There is a problem when a unclean log from the 32bit kernel is replayed > on the 64bit kernel (or the other way round). Just make sure > you always have clean unmounts when you switch between 32bit and 64bit > kernels. hm, but how is the OP supposed to get his fs checked? as i understand it he has successfully run a 8TB xfs in 32bit. now it's somehow corrupt and the log was not replayed yet. but now he's forced to use a 64bit machine to make xfs_repair work (which takes up > 4GB of memory). so he *has* to switch from 32bit to 64bit with an unclean fs :-\ Christian (who's far away from having multi-terabyte-storage systems..) -- BOFH excuse #274: It was OK before you touched it. From owner-linux-xfs@oss.sgi.com Wed Aug 10 16:13:28 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 16:13:34 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7ANDQH9016208 for ; Wed, 10 Aug 2005 16:13:27 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA08720; Thu, 11 Aug 2005 09:11:12 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7ANAvol28372631; Thu, 11 Aug 2005 09:10:57 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7ANAt2G27432037; Thu, 11 Aug 2005 09:10:55 +1000 (EST) Date: Thu, 11 Aug 2005 09:10:55 +1000 From: David Chinner To: evilninja Cc: linux-xfs@oss.sgi.com Subject: Re: XFS and AMD64 Message-ID: <20050811091055.B28436909@melbourne.sgi.com> References: <20050808025536.GA2029@plato.local.lan> <42FA784A.2050301@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <42FA784A.2050301@gmx.net>; from evilninja@gmx.net on Wed, Aug 10, 2005 at 11:57:30PM +0200 X-archive-position: 5777 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1355 Lines: 41 On Wed, Aug 10, 2005 at 11:57:30PM +0200, evilninja wrote: > Andi Kleen schrieb: > > > > There is a problem when a unclean log from the 32bit kernel is replayed > > on the 64bit kernel (or the other way round). Just make sure > > you always have clean unmounts when you switch between 32bit and 64bit > > kernels. > > hm, but how is the OP supposed to get his fs checked? I don't think was the question the OP asked. It was a 32bit userspace/64bit kernel interop question. > as i understand it > he has successfully run a 8TB xfs in 32bit. now it's somehow corrupt and > the log was not replayed yet. Different thread. Please keep in mind that log replay is completely separate to repairing the filesystem and doesn't run in userspace nor does it consume much memory. You should always attempt to do log replay on the same system and kernel or, in the case of hardware failures, on a machine of the same architecture and endianness. > but now he's forced to use a 64bit machine > to make xfs_repair work (which takes up > 4GB of memory). > so he *has* to switch from 32bit to 64bit with an unclean fs :-\ No, you only run xfs_repair after you've replayed the log. Once you've replayed the log you can move the filesystem to any machine you like to repair it. Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Wed Aug 10 17:16:39 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 17:16:43 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7B0GbH9023865 for ; Wed, 10 Aug 2005 17:16:38 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA10213; Thu, 11 Aug 2005 10:14:21 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7B0E9ol27858657; Thu, 11 Aug 2005 10:14:09 +1000 (EST) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7B0E79h28514503; Thu, 11 Aug 2005 10:14:07 +1000 (EST) Date: Thu, 11 Aug 2005 10:14:07 +1000 (EST) From: Timothy Shimmin Message-Id: <200508110014.j7B0E79h28514503@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 940491 - forgot to export xfs_mount_reset_sbqflags X-archive-position: 5778 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tes@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1022 Lines: 26 Thanks to Chris Pascoe for pointing out this omission. Need to export xfs_mount_reset_sbqflags when using modules since I've moved this function definition out of the quota code but it still needs to be called from the quota code as well. --Tim Date: Thu Aug 11 10:12:14 AEST 2005 Workarea: snort.melbourne.sgi.com:/home/tes/isms/xfs-linux-test Inspected by: nathans@sgi.com The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:23467a linux-2.6/xfs_ksyms.c - 1.25 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_ksyms.c.diff?r1=text&tr1=1.25&r2=text&tr2=1.24&f=h linux-2.4/xfs_ksyms.c - 1.21 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_ksyms.c.diff?r1=text&tr1=1.21&r2=text&tr2=1.20&f=h - Need to export xfs_mount_reset_sbqflags when using modules since I've moved this function definition out of the quota code but it still needs to be called from the quota code as well. From owner-linux-xfs@oss.sgi.com Wed Aug 10 19:50:41 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 19:50:44 -0700 (PDT) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [63.240.76.28]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7B2oeH9032627 for ; Wed, 10 Aug 2005 19:50:40 -0700 Received: from c-66-30-115-133.hsd1.ma.comcast.net ([66.30.115.133]) by comcast.net (sccrmhc13) with ESMTP id <20050811024827013007v557e>; Thu, 11 Aug 2005 02:48:27 +0000 Received: from c-66-30-115-133.hsd1.ma.comcast.net (localhost.127.in-addr.arpa [127.0.0.1]) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1) with ESMTP id j7B2mZ0I033454; Wed, 10 Aug 2005 22:48:35 -0400 (EDT) (envelope-from rodrigc@c-66-30-115-133.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1/Submit) id j7B2mZhW033453; Wed, 10 Aug 2005 22:48:35 -0400 (EDT) (envelope-from rodrigc) Date: Wed, 10 Aug 2005 22:48:35 -0400 From: Craig Rodrigues To: linux-xfs@oss.sgi.com Subject: xfsprogs 2.6.36 does not compile on FreeBSD Message-ID: <20050811024835.GA33420@crodrigues.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-archive-position: 5779 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rodrigc@crodrigues.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 4221 Lines: 170 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline i, I tried to get xfsprogs 2.6.36 to compile on FreeBSD, but it didn't work. Some comments: - does not exist on FreeBSD, so remove it from freebsd.c - doesn't exist on FreeBSD, so add the appropriate autoconf test and do not hardcode HAVE_MNTENT_H in paths.c - getmntinfo() exists on FreeBSD, so add the appropriate autoconf test - must be included before on FreeBSD Please provide feedback on the attached patches. Thanks. (BTW, I maintain a port of xfsprogs in the FreeBSD ports collection.) -- Craig Rodrigues rodrigc@crodrigues.org --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-builddefs.in" --- include/builddefs.in.orig Mon Aug 1 10:20:48 2005 +++ include/builddefs.in Wed Aug 10 21:15:46 2005 @@ -100,6 +100,7 @@ HAVE_MADVISE = @have_madvise@ HAVE_MINCORE = @have_mincore@ HAVE_SENDFILE = @have_sendfile@ +HAVE_GETMNTINFO = @have_getmntinfo@ ifeq ($(PKG_PLATFORM),linux) PCFLAGS = -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-configure.in" --- configure.in.orig Mon Aug 1 10:20:46 2005 +++ configure.in Wed Aug 10 21:26:41 2005 @@ -43,6 +43,7 @@ AC_HAVE_MADVISE AC_HAVE_MINCORE AC_HAVE_SENDFILE +AC_HAVE_GETMNTINFO AC_TYPE_PSINT AC_TYPE_PSUNSIGNED @@ -50,3 +51,5 @@ AC_MANUAL_FORMAT AC_OUTPUT(include/builddefs) + +AC_CHECK_HEADERS([mntent.h]) --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-package_libcdev.m4" --- m4/package_libcdev.m4.orig Mon Aug 1 10:20:51 2005 +++ m4/package_libcdev.m4 Wed Aug 10 21:39:09 2005 @@ -65,3 +65,23 @@ AC_MSG_RESULT(no)) AC_SUBST(have_sendfile) ]) + +# +# Check if we have a working getmntinfo system call +# +AC_DEFUN([AC_HAVE_GETMNTINFO], + [ AC_MSG_CHECKING([for getmntinfo ]) + AC_TRY_COMPILE([ +#define _GNU_SOURCE +#define _FILE_OFFSET_BITS 64 +#include +#include +#include + ], [ + getmntinfo(0, 0); + ], have_getmntinfo=yes + AC_MSG_RESULT(yes), + AC_MSG_RESULT(no)) + AC_SUBST(have_getmntinfo) + ]) + --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch-libxcmd_Makefile --- libxcmd/Makefile.orig Wed Aug 10 21:44:47 2005 +++ libxcmd/Makefile Wed Aug 10 21:45:32 2005 @@ -33,6 +33,10 @@ TOPDIR = .. include $(TOPDIR)/include/builddefs +ifeq ($(HAVE_GETMNTINFO),yes) +LCFLAGS += -DHAVE_GETMNTINFO +endif + LTLIBRARY = libxcmd.la LT_CURRENT = 0 LT_REVISION = 0 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-libxcmd_paths.c" --- libxcmd/paths.c.orig Mon Aug 1 10:20:50 2005 +++ libxcmd/paths.c Wed Aug 10 21:50:35 2005 @@ -42,8 +42,6 @@ #include #include -#define HAVE_MNTENT_H 1 /* TODO - configure me (+HAVE_GETMNTINFO) */ - int fs_count; struct fs_path *fs_table; struct fs_path *fs_path; @@ -255,8 +253,8 @@ break; } /* TODO: external log and realtime device? */ - if ((error = fs_table_insert(dir, 0, FS_MOUNT_POINT, - fsname, fslog, fsrt); + if (error = fs_table_insert(dir, 0, FS_MOUNT_POINT, + fsname, fslog, fsrt)) break; } if (!error && path && !found) --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-quota_util.c" --- quota/util.c.orig Wed Aug 10 22:07:40 2005 +++ quota/util.c Wed Aug 10 22:08:00 2005 @@ -30,6 +30,7 @@ * http://oss.sgi.com/projects/GenInfo/SGIGPLNoticeExplan/ */ +#include #include #include #include --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="patch-quota_freebsd.c" --- quota/freebsd.c.orig Wed Aug 10 22:15:47 2005 +++ quota/freebsd.c Wed Aug 10 22:15:57 2005 @@ -31,7 +31,6 @@ */ #include "quota.h" -#include int xfsquotactl( --FCuugMFkClbJLl1L-- From owner-linux-xfs@oss.sgi.com Wed Aug 10 20:38:52 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 20:38:56 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7B3coH9006526 for ; Wed, 10 Aug 2005 20:38:51 -0700 Received: from chook.melbourne.sgi.com (chook.melbourne.sgi.com [134.14.54.237]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id NAA15085 for ; Thu, 11 Aug 2005 13:36:39 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16302) id 1C08649BA506; Thu, 11 Aug 2005 13:37:29 +1000 (EST) To: linux-xfs@oss.sgi.com Subject: TAKE 907752 - userspace updates Message-Id: <20050811033729.1C08649BA506@chook.melbourne.sgi.com> Date: Thu, 11 Aug 2005 13:37:29 +1000 (EST) From: nathans@sgi.com (Nathan Scott) X-archive-position: 5780 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 3549 Lines: 72 Fix hyphens in this man page - not all were back-slashed. Date: Wed Aug 10 10:25:03 AEST 2005 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-cmds Inspected by: nathans The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb Modid: master-melb:xfs-cmds:23446a xfsprogs/man/man8/xfs_quota.8 - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/man/man8/xfs_quota.8.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h Update Polish translation, and fix an error reporting botch in attr code. Date: Wed Aug 10 15:04:41 AEST 2005 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-cmds Inspected by: nathans The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb Modid: master-melb:xfs-cmds:23447a attr/VERSION - 1.54 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/VERSION.diff?r1=text&tr1=1.54&r2=text&tr2=1.53&f=h attr/doc/CHANGES - 1.62 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/doc/CHANGES.diff?r1=text&tr1=1.62&r2=text&tr2=1.61&f=h attr/debian/changelog - 1.55 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/debian/changelog.diff?r1=text&tr1=1.55&r2=text&tr2=1.54&f=h attr/libattr/attr_copy_file.c - 1.6 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/libattr/attr_copy_file.c.diff?r1=text&tr1=1.6&r2=text&tr2=1.5&f=h attr/po/pl.po - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/po/pl.po.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h Fix builds for FreeBSD, thanks to Craig Rodrigues. Date: Thu Aug 11 13:35:55 AEST 2005 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-cmds Inspected by: rodrigc@crodrigues.org The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb Modid: master-melb:xfs-cmds:23478a xfsprogs/configure.in - 1.34 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/configure.in.diff?r1=text&tr1=1.34&r2=text&tr2=1.33&f=h xfsprogs/VERSION - 1.131 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/VERSION.diff?r1=text&tr1=1.131&r2=text&tr2=1.130&f=h xfsprogs/doc/CHANGES - 1.175 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/doc/CHANGES.diff?r1=text&tr1=1.175&r2=text&tr2=1.174&f=h xfsprogs/include/builddefs.in - 1.43 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/include/builddefs.in.diff?r1=text&tr1=1.43&r2=text&tr2=1.42&f=h xfsprogs/debian/changelog - 1.118 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/debian/changelog.diff?r1=text&tr1=1.118&r2=text&tr2=1.117&f=h xfsprogs/aclocal.m4 - 1.18 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/aclocal.m4.diff?r1=text&tr1=1.18&r2=text&tr2=1.17&f=h xfsprogs/m4/package_libcdev.m4 - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/m4/package_libcdev.m4.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h xfsprogs/libxcmd/paths.c - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/libxpaths.c.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h xfsprogs/libxcmd/Makefile - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/libxMakefile.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h xfsprogs/quota/freebsd.c - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/quota/freebsd.c.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h xfsprogs/quota/util.c - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/quota/util.c.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 10 21:52:18 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Aug 2005 21:52:23 -0700 (PDT) Received: from arke.acsalaska.net (arke.acsalaska.net [209.112.173.225]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7B4qHH9011394 for ; Wed, 10 Aug 2005 21:52:18 -0700 Received: from erbenson.alaska.net (66-230-89-87-dial-as3.nwc.acsalaska.net [66.230.89.87]) by arke.acsalaska.net (8.13.4/8.13.4) with ESMTP id j7B4o6JV031449 for ; Wed, 10 Aug 2005 20:50:06 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id E59C63958 for ; Wed, 10 Aug 2005 20:50:04 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 2325440FF35; Wed, 10 Aug 2005 20:50:05 -0800 (AKDT) Date: Wed, 10 Aug 2005 20:50:05 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS and AMD64 Message-ID: <20050811045004.GD2029@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050808025536.GA2029@plato.local.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3Pql8miugIZX0722" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.51; SA 3.0.4; spamdefang 1.113 X-archive-position: 5781 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1307 Lines: 44 --3Pql8miugIZX0722 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 10, 2005 at 03:23:32PM +0200, Andi Kleen wrote: > Ethan Benson writes: > >=20 > > Since I need utmost i386 binary compatibility I would most likely need > > to run a 32 bit user-space with a 64 bit kernel. The Debian AMD64 > > pages claim this type of setup will work but certain configurations do > > not, one example they state is XFS. >=20 > There is a problem when a unclean log from the 32bit kernel is replayed > on the 64bit kernel (or the other way round). Just make sure=20 > you always have clean unmounts when you switch between 32bit and 64bit > kernels. that shouldn't be a problem, I am not going to be flipping back and forth between kernels.=20=20 so is 32 bit userspace xfsutils kosher with a 64 bit xfs kernel? or are there silly ioctl() issues? Thanks --=20 Ethan Benson http://www.alaska.net/~erbenson/ --3Pql8miugIZX0722 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iEYEARECAAYFAkL62PwACgkQJKx7GixEevzSNACfSuUxMdqB2ESrv7UndAmnFCpt 7LMAn0/6jPCUdkCtzuEMDEkvPXsUNgU3 =CcBC -----END PGP SIGNATURE----- --3Pql8miugIZX0722-- From owner-linux-xfs@oss.sgi.com Thu Aug 11 00:26:49 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Aug 2005 00:26:56 -0700 (PDT) Received: from mail.g-house.de (ns2.g-housing.de [81.169.133.75]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7B7QmH9027125 for ; Thu, 11 Aug 2005 00:26:49 -0700 Received: from g03aa.g.pppool.de ([80.185.3.170] helo=mail.housecafe.de) by mail.g-house.de with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1E37Th-0001BN-Mj for linux-xfs@oss.sgi.com; Thu, 11 Aug 2005 09:27:49 +0200 Received: from localhost ([127.0.0.1] helo=housecafe.dyndns.org) by mail.housecafe.de with esmtp (Exim 4.52) id 1E37Nv-0002Bd-8Z for linux-xfs@oss.sgi.com; Thu, 11 Aug 2005 09:21:51 +0200 Received: from 195.126.66.126 (SquirrelMail authenticated user evil) by housecafe.dyndns.org with HTTP; Thu, 11 Aug 2005 09:21:51 +0200 (CEST) Message-ID: <24606.195.126.66.126.1123744911.squirrel@housecafe.dyndns.org> In-Reply-To: <20050811091055.B28436909@melbourne.sgi.com> References: <20050808025536.GA2029@plato.local.lan> <42FA784A.2050301@gmx.net> <20050811091055.B28436909@melbourne.sgi.com> Date: Thu, 11 Aug 2005 09:21:51 +0200 (CEST) Subject: Re: XFS and AMD64 From: "Christian" To: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5783 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 759 Lines: 27 On Thu, August 11, 2005 1:10, David Chinner said: >> as i understand it >> he has successfully run a 8TB xfs in 32bit. now it's somehow corrupt and >> the log was not replayed yet. > > Different thread. erm, yes :-\ i mixed it up and it was more a "what if.." question. "what if i have 8TB of corrupt xfs data on a 32bit system". but you've answered it below. > Please keep in mind that log replay is completely separate to > repairing the filesystem and doesn't run in userspace nor does it ah, that i did not know. > No, you only run xfs_repair after you've replayed the log. Once > you've replayed the log you can move the filesystem to any machine > you like to repair it. ok, i think i got it now. thank you, Christian. -- make bzImage, not war From owner-linux-xfs@oss.sgi.com Thu Aug 11 01:25:01 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Aug 2005 01:25:06 -0700 (PDT) Received: from amanpulo.hosting.qsr.com.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7B8P1H9031329 for ; Thu, 11 Aug 2005 01:25:01 -0700 Received: from localhost (localhost [127.0.0.1]) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id 94F8A1C519BF for ; Thu, 11 Aug 2005 16:22:47 +0800 (PHT) Received: from musang.free.net.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id 3291E1C5198C for ; Thu, 11 Aug 2005 16:22:43 +0800 (PHT) Received: by musang.free.net.ph (Postfix, from userid 1000) id 17E5616AFA7FA; Thu, 11 Aug 2005 16:22:41 +0800 (PHT) Date: Thu, 11 Aug 2005 16:22:41 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Re: XFS repair problem Message-ID: <20050811082241.GJ2779@free.net.ph> Mail-Followup-To: linux-xfs@oss.sgi.com References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <20050809074858.B25981667@melbourne.sgi.com> <005301c59c7d$2eedab20$0400a8c0@LocalHost> <20050809120823.E13484145@melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050809120823.E13484145@melbourne.sgi.com> X-Personal-URL: http://jijo.free.net.ph User-Agent: Mutt/1.5.9i X-archive-position: 5784 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jijo@free.net.ph Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1530 Lines: 40 On Tue, Aug 09, 2005 at 12:08:23PM +1000, David Chinner wrote: > Swap won't help if you're running an ia32 (32bit) kernel - you have a > per-process memory limit of 1-4GiB (depending on kernel and config). > The amount of physical memory and swap does not change this > limitation. I have an ia32 box running Debian Sarge (xfsprogs 2.6.20) with Linux 2.6.12.4, 3GB physical memory, and at present 2GB swap. We don't have a 64-bit system with more RAM to which we can transfer our filesystems, if ever, so I'd like to know: 1. What kernel configuration do we need to enable in particular to maximize the per-process memory limit? 2. What limit should I follow for per-filesystem size, so that I can be confident that even when the filesystem has reasonably many inodes both xfs_check and xfs_repair will work without hitting the per-process memory limit of Linux on ia32? Also, I am using LVM2 (2.01.04) to allow me to build my XFS filesystems across multiple physical volumes (each physical volume is an external hardware RAID 5 enclosure connected to the system via SCSI). I wonder: 1. Are there any known issues with XFS and LVM2 when the total volume group size gets very big (eg: >2TiB)? Or does XFS not care and will this be a purely LVM issue? 2. Aside from problems with snapshots, are there any known issues with running XFS on top of LVM2? Cheers! --> Jijo -- Federico Sevilla III : jijo.free.net.ph : When we speak of free software GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price. From owner-linux-xfs@oss.sgi.com Thu Aug 11 14:54:51 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Aug 2005 14:54:55 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7BLsoH9017209 for ; Thu, 11 Aug 2005 14:54:50 -0700 Received: by zproxy.gmail.com with SMTP id 18so311752nzp for ; Thu, 11 Aug 2005 14:52:39 -0700 (PDT) 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=C+CXFw8rargBsmJAs5TcJ2N5T0l61ZJ+IE9BeshN/OoYpDA4RERvHAw4khhCQhFRdo6IHIQL623Ak8qjZ128NQi50BmbWqdoyMV6MirHqxobdEpfEtl2a3sFwXG7CBlqeeddlWCIeMROUYBZY2uGLj/jZ643pvEZ7GSPj2O22v0= Received: by 10.36.37.17 with SMTP id k17mr889392nzk; Thu, 11 Aug 2005 14:52:39 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Thu, 11 Aug 2005 14:52:39 -0700 (PDT) Message-ID: Date: Thu, 11 Aug 2005 17:52:39 -0400 From: A JM To: linux-xfs@oss.sgi.com Subject: XFS - hard drive dying In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7BLspH9017212 X-archive-position: 5790 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2017 Lines: 50 Sorry for the double post. I'm experiencing some problems with my XFS filesystem mainly due to a drive that is crashing. The system had been very stable and nothing has been changed. This is some of the information from dmsg: XFS mounting filesystem dm-0 Starting XFS recovery on filesystem: dm-0 (dev: dm-0) hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08001 ("xfs_trans_read_buf") error 5 buf count 512 xfs_force_shutdown(dm-0,0x1) called from line 422 of file fs/xfs/xfs_trans_buf.c. Return address = 0xe2e521b4 Filesystem "dm-0": I/O Error Detected. Shutting down filesystem: dm-0 Please umount the filesystem, and rectify the problem(s) hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#1)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown ..... I tried to do a repair on the XFS system for information first and it generated the following: [root@myth ~]# xfs_repair -n /dev/VGforMyth/video Phase 1 - find and verify superblock... superblock read failed, offset 342003548160, size 2048, ag 4294967295, rval 36 fatal error -- Input/output error This drive is still under warranty and I want to recover any information from the drive that is possible before sending off for replacement. Any help or suggestions would be greatly appreciated. Thanks. Adam, From owner-linux-xfs@oss.sgi.com Thu Aug 11 16:48:41 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Aug 2005 16:48:47 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7BNmdH9032549 for ; Thu, 11 Aug 2005 16:48:40 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA11625 for ; Fri, 12 Aug 2005 09:46:26 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7BNkBol29742490 for ; Fri, 12 Aug 2005 09:46:11 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7BNkAcT29800628 for linux-xfs@oss.sgi.com; Fri, 12 Aug 2005 09:46:10 +1000 (EST) Date: Fri, 12 Aug 2005 09:46:10 +1000 From: David Chinner To: linux-xfs@oss.sgi.com Subject: Re: XFS and AMD64 Message-ID: <20050812094610.B29659413@melbourne.sgi.com> References: <20050808025536.GA2029@plato.local.lan> <20050811045004.GD2029@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20050811045004.GD2029@plato.local.lan>; from erbenson@alaska.net on Wed, Aug 10, 2005 at 08:50:05PM -0800 X-archive-position: 5791 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 633 Lines: 23 On Wed, Aug 10, 2005 at 08:50:05PM -0800, Ethan Benson wrote: > > so is 32 bit userspace xfsutils kosher with a 64 bit xfs kernel? or > are there silly ioctl() issues? See debian bug 257265. Looks like silly ioctl issues were reported for sparc64 (64bit kernel, 32bit userspace) about a year ago and a fix was put into the 2.6.8-1 kernel package. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=257265 If the debian AMD64 kernel is not built from this package (or it's descendent) you'll need to check to see if this mod is in that kernel.` Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Thu Aug 11 17:34:48 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Aug 2005 17:34:55 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7C0YlH9008796 for ; Thu, 11 Aug 2005 17:34:48 -0700 Received: by zproxy.gmail.com with SMTP id 18so326273nzp for ; Thu, 11 Aug 2005 17:32:37 -0700 (PDT) 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:content-transfer-encoding:content-disposition; b=Uew4n6OeZ2O3BqLAdnvV3V5Adq8j96cvXgB7l9eUmRSGkEDCf6sbyuU00wFbYIODHda1pItCMlCmXJR8TRTwuBe9cYz1dzmly3A0TM88o/4jisiiQjX0htB67nCbfiTSDLkh0/cYrdBnJAOjFMzF9EfuA8KdpnKNaiWJdG6KSEM= Received: by 10.36.82.9 with SMTP id f9mr2295735nzb; Thu, 11 Aug 2005 17:32:37 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Thu, 11 Aug 2005 17:32:37 -0700 (PDT) Message-ID: Date: Thu, 11 Aug 2005 20:32:37 -0400 From: A JM To: linux-xfs@oss.sgi.com Subject: Re: XFS - hard drive dying Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7C0YmH9008803 X-archive-position: 5792 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 599 Lines: 19 Some other usfeul information? Here is some info from trying XFS utilities. [root@myth ~]# xfs_repair -n -v /dev/VGforMyth/video Phase 1 - find and verify superblock... superblock read failed, offset 342003548160, size 2048, ag 4294967295, rval 36 fatal error -- Input/output error [root@myth ~]# xfs_check /dev/VGforMyth/video agi unlinked bucket 39 is 167 in ag 1 (inode=67109031) can't read btree block 29/1 can't read btree block 29/2 can't read btree block 29/3 agf_freeblks 2314760, counted 0 in ag 29 agf_longest 2314760, counted 0 in ag 29 can't read superblock for ag 36 [root@myth ~]# From owner-linux-xfs@oss.sgi.com Fri Aug 12 00:25:56 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Aug 2005 00:26:06 -0700 (PDT) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7C7PtH9032277 for ; Fri, 12 Aug 2005 00:25:56 -0700 Received: from hch by pentafluge.infradead.org with local (Exim 4.52 #1 (Red Hat Linux)) id 1E3TtI-00059X-Lk; Fri, 12 Aug 2005 08:23:44 +0100 Date: Fri, 12 Aug 2005 08:23:44 +0100 From: Christoph Hellwig To: David Chinner Cc: linux-xfs@oss.sgi.com Subject: Re: XFS and AMD64 Message-ID: <20050812072344.GA19680@infradead.org> References: <20050808025536.GA2029@plato.local.lan> <20050811045004.GD2029@plato.local.lan> <20050812094610.B29659413@melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050812094610.B29659413@melbourne.sgi.com> User-Agent: Mutt/1.4.2.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html X-archive-position: 5798 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 815 Lines: 20 On Fri, Aug 12, 2005 at 09:46:10AM +1000, David Chinner wrote: > On Wed, Aug 10, 2005 at 08:50:05PM -0800, Ethan Benson wrote: > > > > so is 32 bit userspace xfsutils kosher with a 64 bit xfs kernel? or > > are there silly ioctl() issues? > > See debian bug 257265. Looks like silly ioctl issues were reported > for sparc64 (64bit kernel, 32bit userspace) about a year ago and a > fix was put into the 2.6.8-1 kernel package. > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=257265 > > If the debian AMD64 kernel is not built from this package (or it's > descendent) you'll need to check to see if this mod is in that > kernel.` That's just for growfs. We have compatibility shims for some ioctls, but the complicated ones (all the handle stuff, bulkstat) doesn't work and can't be easily made to work. From owner-linux-xfs@oss.sgi.com Fri Aug 12 03:38:36 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Aug 2005 03:38:42 -0700 (PDT) Received: from mail.g-house.de (ns2.g-housing.de [81.169.133.75]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7CAcZH9028737 for ; Fri, 12 Aug 2005 03:38:36 -0700 Received: from g147d.g.pppool.de ([80.185.20.125] helo=[192.168.10.31]) by mail.g-house.de with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1E3Wx3-0001CK-W6; Fri, 12 Aug 2005 12:39:52 +0200 Message-ID: <42FC7C02.1090106@g-house.de> Date: Fri, 12 Aug 2005 12:37:54 +0200 From: Christian User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: A JM Subject: Re: XFS - hard drive dying References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5802 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evil@g-house.de Precedence: bulk X-list: linux-xfs Status: O Content-Length: 677 Lines: 20 A JM schrieb: > Starting XFS recovery on filesystem: dm-0 (dev: dm-0) > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, > low=1999296, sector=371098047 since it really looks like a bad drive, try to get your data to another (good) harddrive with "dd" or better "dd_rescue" [1]. then use a current version of xfsprogs [2] to check/repair the rescued data. Christian. [1] http://www.garloff.de/kurt/linux/ddrescue/ [2] ftp://oss.sgi.com/projects/xfs/cmd_tars/ -- BOFH excuse #53: Little hamster in running wheel had coronary; waiting for replacement to be Fedexed from Wyoming From owner-linux-xfs@oss.sgi.com Fri Aug 12 04:21:38 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Aug 2005 04:22:39 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7CBLbH9006720 for ; Fri, 12 Aug 2005 04:21:37 -0700 Received: by zproxy.gmail.com with SMTP id 18so381431nzp for ; Fri, 12 Aug 2005 04:19:26 -0700 (PDT) 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=fq/pnSatGDtIrkVRoR+6NUF90V4YfXcZg/5w8cLCypv/aLJQmUC/FDejtKZC4GhYfCgRVpI8xn/JbPcTK2XZzPNTbs/Jszm9ldOurDUCHTtinPYpj/We53NooHo6c8VsQsUtl5ua/X9B/8K+xslCyezN0MgMVA3SRN+sx+AEVnk= Received: by 10.36.37.17 with SMTP id k17mr1408940nzk; Fri, 12 Aug 2005 04:19:26 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Fri, 12 Aug 2005 04:19:26 -0700 (PDT) Message-ID: Date: Fri, 12 Aug 2005 07:19:26 -0400 From: A JM To: Christian Subject: Re: XFS - hard drive dying Cc: linux-xfs@oss.sgi.com In-Reply-To: <42FC7C02.1090106@g-house.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FC7C02.1090106@g-house.de> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7CBLcH9006722 X-archive-position: 5805 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 987 Lines: 33 So the dd_rhelp command line for the entire drive to recover to another drive would read like? (dd_rhelp /dev/VGforMyth/video /dev/hdc/video) Does this need to be done in "single user" mode? Thanks for some hope.... AJM, On 8/12/05, Christian wrote: > A JM schrieb: > > Starting XFS recovery on filesystem: dm-0 (dev: dm-0) > > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, > > low=1999296, sector=371098047 > > since it really looks like a bad drive, try to get your data to another > (good) harddrive with "dd" or better "dd_rescue" [1]. then use a current > version of xfsprogs [2] to check/repair the rescued data. > > Christian. > > [1] http://www.garloff.de/kurt/linux/ddrescue/ > [2] ftp://oss.sgi.com/projects/xfs/cmd_tars/ > -- > BOFH excuse #53: > > Little hamster in running wheel had coronary; waiting for replacement to > be Fedexed from Wyoming > From owner-linux-xfs@oss.sgi.com Fri Aug 12 05:27:00 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Aug 2005 05:27:03 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7CCQxH9019572 for ; Fri, 12 Aug 2005 05:27:00 -0700 Received: (qmail invoked by alias); 12 Aug 2005 12:24:47 -0000 Received: from G147d.g.pppool.de (EHLO [192.168.10.11]) [80.185.20.125] by mail.gmx.net (mp003) with SMTP; 12 Aug 2005 14:24:47 +0200 X-Authenticated: #2986359 Message-ID: <42FC950C.2020500@gmx.net> Date: Fri, 12 Aug 2005 14:24:44 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: A JM Subject: Re: XFS - hard drive dying References: <42FC7C02.1090106@g-house.de> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5806 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 814 Lines: 30 A JM schrieb: > So the dd_rhelp command line for the entire drive to recover to > another drive would read like? (dd_rhelp /dev/VGforMyth/video > /dev/hdc/video) i don't know much about LVM but when /dev/VGforMyth/video is your bad drive, /dev/hdc/video should be the good drive of the *same* size: % dd_rescue /dev/VGforMyth/video /dev/hdc/video i guess the "outfile" could be a FILE too: % dd_rescue /dev/VGforMyth/video /tmp/VGforMyth.img later on you could loopmount VGforMyth.img or use losetup to check the filesystem. > Does this need to be done in "single user" mode? not necessarily, but for unmounting /dev/VGforMyth/video all applications that have a lock on the data must be shutdown. i'd recommend "single user" mode. Christian. -- BOFH excuse #59: failed trials, system needs redesigned From owner-linux-xfs@oss.sgi.com Sat Aug 13 17:00:22 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 13 Aug 2005 17:00:25 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7E00MH9017341 for ; Sat, 13 Aug 2005 17:00:22 -0700 Received: by zproxy.gmail.com with SMTP id 18so569585nzp for ; Sat, 13 Aug 2005 16:58:09 -0700 (PDT) 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:content-transfer-encoding:content-disposition; b=mqD6RKLxgMSKFK5G4ee5RoSlhgox7TRlkKacR/wpl7b9VYXO+2IBeMDZ8JNi3VywbP0L3FYwZZ8IdkROD9Dh1kpEBD91RBdQLCDzyxXIaWoc9xIxlomCJZvFjOqOevQQePZngMdp/zlWPOAWRIBDmHovqkV0HIvBgxA7SrZqDsU= Received: by 10.36.37.12 with SMTP id k12mr1232359nzk; Sat, 13 Aug 2005 16:58:09 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Sat, 13 Aug 2005 16:58:09 -0700 (PDT) Message-ID: Date: Sat, 13 Aug 2005 19:58:09 -0400 From: A JM To: linux-xfs@oss.sgi.com Subject: Re: XFS - hard drive dying Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7E00MH9017351 X-archive-position: 5840 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 821 Lines: 20 I tried using dd_rescue on my drive and it appeard to be copying over the data until I got the message that there wasn't enough space on the target disk? Very strange since they are the exact same size disk. Anyway I thought I would try to run xfs_repair and see what happened. I get the message on the intial startup of "Phase 1 find and verify superblock... bad primary superblock - bad magic number! attempting to find secondary superblock" It continues on and then I get the following message "Found candidate secondary superblock error reading superblock 22 -- seek to offset 209002168320 failed unable to verify superblock continuing" It then appears to loop and repeat itself. Anyone have any suggestions? Why the disk space error? shoudl I format the replacement drive before attempting dd_rescue? Thanks, From owner-linux-xfs@oss.sgi.com Sun Aug 14 12:21:00 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Aug 2005 12:21:04 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7EJKxH9000848 for ; Sun, 14 Aug 2005 12:21:00 -0700 Received: (qmail invoked by alias); 14 Aug 2005 19:18:45 -0000 Received: from G1ddf.g.pppool.de (EHLO [192.168.10.11]) [80.185.29.223] by mail.gmx.net (mp019) with SMTP; 14 Aug 2005 21:18:45 +0200 X-Authenticated: #2986359 Message-ID: <42FF9912.2020106@gmx.net> Date: Sun, 14 Aug 2005 21:18:42 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" CC: A JM Subject: Re: XFS - hard drive dying References: <42FC7C02.1090106@g-house.de> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5856 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1181 Lines: 40 (please respond on-list, so everyone can help, especially when i enjoyed an offline-weekend ;-)) A JM schrieb: > I have an identical drive to the one that is failing. Does that drive > need to be formatted for this to work? no, if you dd(_rescue) to the device (the good harddrive) itsself, it does not have to be formatted. even if it was formatted, say with ext3 - it will all be overwritten by dd. IOW the target disk should contain no (valuable) data. if you dd to a file: % dd_rescue /dev/VGforMyth/video /tmp/VGforMyth.img then /tmp/ has to be accessible (and thus mounted) of course. > What in particular would you run on the new disk after moving the data? > > xfs_repair -n -v /dev/hdc/video yes, looks good. but what exactly is "/dev/hdc/video" ? is it a volume group or something? my new IDE disk on the 2nd IDE-channel (master) would appear as "/dev/hdc". without the "/video". if you saved the data to a file you might add "-f" to xfs_repair (although my xfs_repair-v2.6.28 does without the option too): % xfs_repair -f -n -v /tmp/VGforMyth.img good luck, Christian. -- BOFH excuse #445: Browser's cookie is corrupted -- someone's been nibbling on it. From owner-linux-xfs@oss.sgi.com Sun Aug 14 12:34:37 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Aug 2005 12:34:43 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7EJYaH9003393 for ; Sun, 14 Aug 2005 12:34:36 -0700 Received: (qmail invoked by alias); 14 Aug 2005 19:32:22 -0000 Received: from G1ddf.g.pppool.de (EHLO [192.168.10.11]) [80.185.29.223] by mail.gmx.net (mp023) with SMTP; 14 Aug 2005 21:32:22 +0200 X-Authenticated: #2986359 Message-ID: <42FF9C45.7010907@gmx.net> Date: Sun, 14 Aug 2005 21:32:21 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: A JM Subject: Re: XFS - hard drive dying References: In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5857 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 925 Lines: 24 A JM schrieb: > I tried using dd_rescue on my drive and it appeard to be copying over > the data until I got the message that there wasn't enough space on the > target disk? Very strange since they are the exact same size disk. strange indeed, but since you're using LVM (right?) - did you double-check your setup and if your target disk is really big enough for /dev/VGforMyth/video ? > Anyway I thought I would try to run xfs_repair and see what happened. > I get the message on the intial startup of "Phase 1 find and verify > superblock... bad primary superblock - bad magic number! attempting > to find secondary superblock" are you sure that this is an XFS filesystem? perhaps you could post the fstab line of how /dev/VGforMyth/video was actually mounted. and you can try to use xfs_logprint to see if any ERROR messages pop up. Christian. -- BOFH excuse #116: the real ttys became pseudo ttys and vice-versa. From owner-linux-xfs@oss.sgi.com Sun Aug 14 13:05:31 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Aug 2005 13:05:36 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7EK5TH9006627 for ; Sun, 14 Aug 2005 13:05:30 -0700 Received: (qmail invoked by alias); 14 Aug 2005 20:03:16 -0000 Received: from G1ddf.g.pppool.de (EHLO [192.168.10.11]) [80.185.29.223] by mail.gmx.net (mp020) with SMTP; 14 Aug 2005 22:03:16 +0200 X-Authenticated: #2986359 Message-ID: <42FFA383.7020807@gmx.net> Date: Sun, 14 Aug 2005 22:03:15 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: XFS - hard drive dying References: <42FC7C02.1090106@g-house.de> <42FF9912.2020106@gmx.net> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5859 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1769 Lines: 49 A JM schrieb: > Yes, "/dev/hdc/video" was a typo on my behalf it should read "/dev/hdc". ok. > Here a link to my latest > post(http://oss.sgi.com/archives/linux-xfs/2005-08/msg00139.html). yes, i commented on that :-) > I've got to figure this data is recoverable since the drive is still > functional? I guess that could bequestionable. *if* the data is functional, then you can get your data. dd'ing is fine, but it'll stop on read errors which are likely to happen if the drive is damaged. dd_rescue will continue its work and has some nice other features too (see http://www.garloff.de/kurt/linux/ddrescue/ again) > So, if I'm runing out of space on the new drive what would happen if I > save it to a file? (% dd_rescue /dev/VGforMyth/video > /tmp/VGforMyth.img) Will it be reduced in size? Would I then run > xfs_repair on it? /tmp/VGforMyth.img will be the size of /dev/VGforMyth/video. it may be smaller if some sectors could not be read. say dd_rescue can't read 100 sectors from /dev/VGforMyth/video, then /tmp/VGforMyth.img will be 100 sectors smaller. > Would that also possible fix the superblock error: "Found candidate > secondary superblock error reading superblock 22 -- seek to offset > 209002168320 failed unable to verify superblock continuing" fixing XFS filesystems is a job for xfs_repair. dd_rescue has nothing to do with it. please try to finish step one (dd_rescue), then continue with xfs_repair. > This drive was part of a volume group "VGforMyth/video" and was the > second drive in the group. I believe itwas formatted using ext3 if I > recall correctly. erm, if it is ext3....then you should be using e2fsprogs and eventually posting on ext3-users@redhat.com right? Christian. -- BOFH excuse #48: bad ether in the cables From owner-linux-xfs@oss.sgi.com Sun Aug 14 14:24:43 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Aug 2005 14:24:47 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7ELOhH9016911 for ; Sun, 14 Aug 2005 14:24:43 -0700 Received: by zproxy.gmail.com with SMTP id 18so641065nzp for ; Sun, 14 Aug 2005 14:22:30 -0700 (PDT) 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=SNkN2BF3K/1IoOnDtOG/cmbwkLyvzqMSoW6Q9sLAp0ZnXWgWOLSRofMMJfJXhQVC0z3p+XrHOcaZZOuj5dxu3s14+D3miNYSCjqROdAyVFfDA7IZljB0FxGFh8kFJZ5fWov0CQX0qkEAFCQfqS4BcHudT8lJ97bkmIJ8G1s995M= Received: by 10.37.22.45 with SMTP id z45mr4494117nzi; Sun, 14 Aug 2005 14:22:29 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Sun, 14 Aug 2005 14:22:29 -0700 (PDT) Message-ID: Date: Sun, 14 Aug 2005 17:22:29 -0400 From: A JM To: linux-xfs@oss.sgi.com Subject: Re: XFS - hard drive dying Cc: evilninja In-Reply-To: <42FFA383.7020807@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FC7C02.1090106@g-house.de> <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7ELOhH9016913 X-archive-position: 5860 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 218 Lines: 8 Yes, I think your correct like an idiot I should verify the file system on the drive, I assumed it's XFS... Can that be determined from the original disk in the LVM? How can I tell what it was formatted as? Thanks. From owner-linux-xfs@oss.sgi.com Mon Aug 15 09:30:33 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 09:30:36 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7FGUVH9017843 for ; Mon, 15 Aug 2005 09:30:32 -0700 Received: (qmail invoked by alias); 15 Aug 2005 16:28:16 -0000 Received: from G1ddf.g.pppool.de (EHLO [192.168.10.11]) [80.185.29.223] by mail.gmx.net (mp012) with SMTP; 15 Aug 2005 18:28:16 +0200 X-Authenticated: #2986359 Message-ID: <4300C29D.1030302@gmx.net> Date: Mon, 15 Aug 2005 18:28:13 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: A JM Subject: Re: XFS - hard drive dying References: <42FC7C02.1090106@g-house.de> <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5879 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 500 Lines: 23 A JM schrieb: > Can that be determined from the original disk in the LVM? How can I > tell what it was formatted as? you can probably look into your /etc/fstab, because the disk was working, didn't it? or you can use file(1): % file -s /dev/VGforMyth/video here: % file -s /dev/sda6 /dev/sda6: SGI XFS filesystem data (blksz 4096, inosz 256, v2 dirs) % file -s /dev/sda5 /dev/sda5: Linux rev 1.0 ext2 filesystem data Christian. -- BOFH excuse #171: NOTICE: alloc: /dev/null: filesystem full From owner-linux-xfs@oss.sgi.com Mon Aug 15 09:42:55 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 09:43:00 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7FGgrH9019161 for ; Mon, 15 Aug 2005 09:42:54 -0700 Received: by zproxy.gmail.com with SMTP id 18so740458nzp for ; Mon, 15 Aug 2005 09:40:32 -0700 (PDT) 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=q41QAEebda83CfcN0BiFm4jfIMCI/UsE7YLU0g3SBtexZ4dXTRaI0wjkX9SCbkQXE+jPwYw28DQ7eOmJ45sWDNNmhoGOWCm6EGsugxkRrr2JDwesXz1LCRF/kh+DjoRoZCq9vOZJRuZ7kESUDFYJL/doEBEK9a33bh8zvE2CiFs= Received: by 10.36.224.6 with SMTP id w6mr5231947nzg; Mon, 15 Aug 2005 09:40:32 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Mon, 15 Aug 2005 09:40:32 -0700 (PDT) Message-ID: Date: Mon, 15 Aug 2005 12:40:32 -0400 From: A JM To: evilninja Subject: Re: XFS - hard drive dying Cc: linux-xfs@oss.sgi.com In-Reply-To: <4300C29D.1030302@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FC7C02.1090106@g-house.de> <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7FGgtH9019173 X-archive-position: 5880 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1833 Lines: 44 It was working fine... Here is the output I'm getting and a copy of the fstab and the LVM. [root@myth ~]# file -s /dev/VGforMyth/video /dev/VGforMyth/video: ERROR: cannot open `/dev/VGforMyth/video' (No such file or directory) [root@myth ~]# file -s /dev/hdb4 /dev/hdb4: x86 boot sector, extended partition table # This file is edited by fstab-sync - see 'man fstab-sync' for details LABEL=/ / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 /dev/hdb2 swap swap defaults 0 0 /dev/VGforMyth/video /video auto defaults 0 0 /dev/hdc /mnt/dvd udf iso9660 ro,user,noauto,managed 0 0 #/dev/hda1 /video2 auto defaults 0 0 /dev/fd0 /media/floppy auto pamconsole,exec,noauto,managed 0 0 [root@myth ~]# pvdisplay /dev/hdb4 Couldn't find device with uuid 'WADUfY-swMe-siya-B81s-YE5d-KwUS-qc4N2U'. Couldn't find all physical volumes for volume group VGforMyth. format_text: _vg_read failed to read VG VGforMyth Couldn't find device with uuid 'WADUfY-swMe-siya-B81s-YE5d-KwUS-qc4N2U'. Couldn't find all physical volumes for volume group VGforMyth. format_text: _vg_read failed to read VG VGforMyth --- NEW Physical volume --- PV Name /dev/hdb4 VG Name PV Size 141.57 GB Allocatable NO PE Size (KByte) 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID MPO1WG-5QLW-m5Ef-eGDF-AAlX-Ht4A-zCSHKa From owner-linux-xfs@oss.sgi.com Mon Aug 15 11:21:23 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 11:21:28 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7FILMH9028137 for ; Mon, 15 Aug 2005 11:21:22 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [198.149.16.15]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7FIJ8xT032712 for ; Mon, 15 Aug 2005 13:19:08 -0500 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7FIJ8DN14318905 for ; Mon, 15 Aug 2005 13:19:08 -0500 (CDT) Received: from sgi.com (penguin.americas.sgi.com [128.162.240.135]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id j7FIJ7LL3072921; Mon, 15 Aug 2005 13:19:07 -0500 (CDT) Received: from penguin.americas.sgi.com (localhost.localdomain [127.0.0.1]) by sgi.com (8.12.8/8.12.8) with ESMTP id j7FIJ6gc004839; Mon, 15 Aug 2005 13:19:06 -0500 Received: (from sandeen@localhost) by penguin.americas.sgi.com (8.12.8/8.12.8/Submit) id j7FIJ6EF004837; Mon, 15 Aug 2005 13:19:06 -0500 Date: Mon, 15 Aug 2005 13:19:06 -0500 From: Eric Sandeen Message-Id: <200508151819.j7FIJ6EF004837@penguin.americas.sgi.com> To: sgi.bugs.xfs@fido.engr.sgi.com, linux-xfs@oss.sgi.com Subject: TAKE 938899 - add ioctl32 handlers for 2.4; fix up a few for 2.6 X-archive-position: 5881 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@penguin.americas.sgi.com Precedence: bulk X-list: linux-xfs add handlers to fix xfs_flock_t alignment issues in compat ioctls Date: Mon Aug 15 11:18:30 PDT 2005 Workarea: penguin.americas.sgi.com:/src/eric/xfs-trees/xfs-GUT-clean Inspected by: nathans,hch The following file(s) were checked into: bonnie.engr.sgi.com:/isms/xfs-kern/xfs-linux Modid: xfs-linux:xfs-kern:197403a linux-2.6/xfs_ioctl32.c - 1.7 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_ioctl32.c.diff?r1=text&tr1=1.7&r2=text&tr2=1.6&f=h - add handlers to fix xfs_flock_t alignment issues in compat ioctls From owner-linux-xfs@oss.sgi.com Mon Aug 15 13:26:10 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 13:26:14 -0700 (PDT) Received: from mail.g-house.de (ns2.g-housing.de [81.169.133.75]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7FKQ9H9006662 for ; Mon, 15 Aug 2005 13:26:10 -0700 Received: from g18e9.g.pppool.de ([80.185.24.233] helo=mail.housecafe.de) by mail.g-house.de with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1E4lV5-0004yd-W2; Mon, 15 Aug 2005 22:24:04 +0200 Received: from localhost ([127.0.0.1] helo=housecafe.dyndns.org) by mail.housecafe.de with esmtp (Exim 4.52) id 1E4lUs-00007i-Ba; Mon, 15 Aug 2005 22:23:50 +0200 Received: from 195.126.66.126 (SquirrelMail authenticated user evil) by housecafe.dyndns.org with HTTP; Mon, 15 Aug 2005 22:23:50 +0200 (CEST) Message-ID: <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> In-Reply-To: References: <42FC7C02.1090106@g-house.de> <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> Date: Mon, 15 Aug 2005 22:23:50 +0200 (CEST) Subject: Re: XFS - hard drive dying From: "Christian" To: "A JM" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5882 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs On Mon, August 15, 2005 18:40, A JM wrote: > [root@myth ~]# file -s /dev/VGforMyth/video > /dev/VGforMyth/video: ERROR: cannot open `/dev/VGforMyth/video' (No > such file or directory) so, how did you try to make the backup with "dd" then? and how did your /etc/fstab work at all, if the device is not present? > [root@myth ~]# file -s /dev/hdb4 > /dev/hdb4: x86 boot sector, extended partition table what is /dev/hdb4? > /dev/VGforMyth/video /video auto defaults 0 0 please don't use "auto" for known filesystems. if it is "Ext3" filesystem, use "ext3": /dev/VGforMyth/video /video ext3 defaults 0 0 Christian. -- make bzImage, not war From owner-linux-xfs@oss.sgi.com Mon Aug 15 14:01:02 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 14:01:06 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7FL11H9008640 for ; Mon, 15 Aug 2005 14:01:02 -0700 Received: by zproxy.gmail.com with SMTP id 18so773169nzp for ; Mon, 15 Aug 2005 13:58:47 -0700 (PDT) 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=e6412UDBzyhA9Ry1xeMz6A+PO4wkmG2iBSuFKcpHUZsC84AheqUlgYVpFCyxOSJ4UV6LVwAaj5NiHA5MrhURGsCXJlcTI02nPbmXPv5s375RK71JCcol2rLYUYEPQSiYYF40HvLIhMmFjkbRZ9bAx/rk5w74/ipzH+shSmJD8Co= Received: by 10.36.138.6 with SMTP id l6mr5418657nzd; Mon, 15 Aug 2005 13:58:45 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Mon, 15 Aug 2005 13:58:45 -0700 (PDT) Message-ID: Date: Mon, 15 Aug 2005 16:58:45 -0400 From: A JM To: Christian Subject: Re: XFS - hard drive dying Cc: linux-xfs@oss.sgi.com In-Reply-To: <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7FL12H9008643 X-archive-position: 5883 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs "so, how did you try to make the backup with "dd" then? and how did your /etc/fstab work at all, if the device is not present?" There are 2 drives in this box, /dev/hdb and /dev/hdd. The device /dev/hdd is the drive that is crashing. Device /dev/hdb has a partition on it, /dev/hdb4 that was the initial LVM (VGforMyth/video) and all of /dev/hdd was then included in the LVM when it was added to the box. F.Y.I. - I do get an error when the system is booting I believe it says "error in fstab line 9" or something to that effect when booting to X. As far as running "dd" on it, I simply added the new hard drive (200 gig) as device /dev/hda and booted up the system. I get a warning from S.M.A.R.T about backing up the drive then then I boot into "init 1" and run "dd" #dd_rescue /dev/VGforMyth/video /dev/hdc and off it goes until I get an error about 3 hrs. later that it ran out of space on the new drive. Now as I'm thinking about would "dd" think it's running out of space because it is using both drives that were in the LVM not just the drive that crashing? That would certainly be more than 200 gig. "what is /dev/hdb4?" As noted above /dev/hdb4 is the other part of the LVM. "please don't use "auto" for known filesystems. if it is "Ext3" filesystem, use "ext3":" I will make change to the fstab as soon as I know for sure what type of filesystem it contains. Thanks. AJM, From owner-linux-xfs@oss.sgi.com Mon Aug 15 14:56:22 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 14:56:27 -0700 (PDT) Received: from mail.g-house.de (ns2.g-housing.de [81.169.133.75]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7FLuLH9012084 for ; Mon, 15 Aug 2005 14:56:22 -0700 Received: from g18e9.g.pppool.de ([80.185.24.233] helo=mail.housecafe.de) by mail.g-house.de with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1E4muP-0003bK-LT; Mon, 15 Aug 2005 23:54:18 +0200 Received: from localhost ([127.0.0.1] helo=housecafe.dyndns.org) by mail.housecafe.de with esmtp (Exim 4.52) id 1E4muB-0001VT-Rk; Mon, 15 Aug 2005 23:54:03 +0200 Received: from 195.126.66.126 (SquirrelMail authenticated user evil) by housecafe.dyndns.org with HTTP; Mon, 15 Aug 2005 23:54:03 +0200 (CEST) Message-ID: <44568.195.126.66.126.1124142843.squirrel@housecafe.dyndns.org> In-Reply-To: References: <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> Date: Mon, 15 Aug 2005 23:54:03 +0200 (CEST) Subject: [OT] Re: XFS - hard drive dying From: "Christian" To: "A JM" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5884 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs On Mon, August 15, 2005 22:58, A JM wrote: > There are 2 drives in this box, /dev/hdb and /dev/hdd. The device > /dev/hdd is the drive that is crashing. Device /dev/hdb has a > partition on it, /dev/hdb4 that was the initial LVM (VGforMyth/video) > and all of /dev/hdd was then included in the LVM when it was added to > the box. aha. but you did not set up LVM when you did "file -s /dev/VGforMyth/video", did you? > F.Y.I. - I do get an error when the system is booting I believe it > says "error in fstab line 9" or something to that effect when booting > to X. hm. as said before, i dunno much about basic LVM setup :-( > Now as I'm thinking about would "dd" think it's running out of space > because it is using both drives that were in the LVM not just the > drive that crashing? That would certainly be more than 200 gig. no, dd does not "think". either the target-drive is big enough or it's not. as always: good luck, Christian. -- make bzImage, not war From owner-linux-xfs@oss.sgi.com Mon Aug 15 16:49:27 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 16:49:33 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7FNnQH9022339 for ; Mon, 15 Aug 2005 16:49:27 -0700 Received: by zproxy.gmail.com with SMTP id 18so789693nzp for ; Mon, 15 Aug 2005 16:47:12 -0700 (PDT) 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=b9dLKgJoRKt13j46XyvBIeCwsy2+JyiM/b3vUHSNSOzZTb1rGvHiDhXIzM5LnMdA1aTW1OPOZhFSpgwNOm30MmPzQHqAUxJXX+RkuCZ0rJNAMlP4KBametka+iwNFsIx61nhnGLZsFqkHX6OAQfEDF4mCWa6UiWmdk6KwxTTSTM= Received: by 10.36.129.8 with SMTP id b8mr5631633nzd; Mon, 15 Aug 2005 16:47:12 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Mon, 15 Aug 2005 16:47:12 -0700 (PDT) Message-ID: Date: Mon, 15 Aug 2005 19:47:12 -0400 From: A JM To: Christian Subject: Re: [OT] Re: XFS - hard drive dying Cc: linux-xfs@oss.sgi.com In-Reply-To: <44568.195.126.66.126.1124142843.squirrel@housecafe.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FF9912.2020106@gmx.net> <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> <44568.195.126.66.126.1124142843.squirrel@housecafe.dyndns.org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7FNnRH9022341 X-archive-position: 5887 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 788 Lines: 23 [root@myth ~]# mount /dev/hdb3 on / type ext3 (rw) none on /proc type proc (rw) none on /sys type sysfs (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) usbfs on /proc/bus/usb type usbfs (rw) none on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nfsd on /proc/fs/nfsd type nfsd (rw) [root@myth ~]# mount /dev/VGforMyth/video [mntent]: line 9 in /etc/fstab is bad mount: special device /dev/VGforMyth/video does not exist [root@myth ~]# file -s /dev/VGforMyth/video /dev/VGforMyth/video: ERROR: cannot open `/dev/VGforMyth/video' (No such file or directory) What do you think about the LVM spread over 2 disks and "dd" determining the file size from that as opposed to just a single drive? From owner-linux-xfs@oss.sgi.com Mon Aug 15 18:19:32 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Aug 2005 18:19:41 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [216.148.227.118]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7G1JVH9026940 for ; Mon, 15 Aug 2005 18:19:32 -0700 Received: from c-66-30-115-133.hsd1.ma.comcast.net ([66.30.115.133]) by comcast.net (rwcrmhc13) with ESMTP id <20050816011627015004qr10e>; Tue, 16 Aug 2005 01:16:27 +0000 Received: from c-66-30-115-133.hsd1.ma.comcast.net (localhost.127.in-addr.arpa [127.0.0.1]) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1) with ESMTP id j7G1GQYh023158 for ; Mon, 15 Aug 2005 21:16:27 -0400 (EDT) (envelope-from rodrigc@c-66-30-115-133.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1/Submit) id j7G1GQI1023157 for linux-xfs@oss.sgi.com; Mon, 15 Aug 2005 21:16:26 -0400 (EDT) (envelope-from rodrigc) Date: Mon, 15 Aug 2005 21:16:26 -0400 From: Craig Rodrigues To: linux-xfs@oss.sgi.com Subject: Use "const char *name" in extattr functions? Message-ID: <20050816011626.GA23116@crodrigues.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="sdtB3X0nJg68CQEu" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-archive-position: 5888 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rodrigc@crodrigues.org Precedence: bulk X-list: linux-xfs Content-Length: 5257 Lines: 151 --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I've been trying to get the FreeBSD API for extended attributes working with XFS. The FreeBSD API uses "const char *" strings for the attribute name. For example: int VOP_GETEXTATTR(struct vnode *vp, int attrnamespace, const char *name, struct uio *uio, size_t *size, struct ucred *cred, struct thread *td); GCC gave me some problems when I tried passing "const char *" to functions which took "char *" parameters for the attribute name. In the cases which I am interested in, the name parameter is not changed, so it could easily be const. Could the use of attribute names be changed to const in areas of the XFS code where the name parameter is not actually modified? I'm thinking of something like the attached patch. -- Craig Rodrigues rodrigc@crodrigues.org --sdtB3X0nJg68CQEu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="extattr_patch.txt" Index: xfs_attr.c =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_attr.c,v retrieving revision 1.120 diff -u -u -r1.120 xfs_attr.c --- xfs_attr.c 18 May 2005 09:29:33 -0000 1.120 +++ xfs_attr.c 16 Aug 2005 01:13:07 -0000 @@ -122,7 +122,7 @@ *========================================================================*/ int -xfs_attr_fetch(xfs_inode_t *ip, char *name, int namelen, +xfs_attr_fetch(xfs_inode_t *ip, const char *name, int namelen, char *value, int *valuelenp, int flags, struct cred *cred) { xfs_da_args_t args; @@ -177,7 +177,7 @@ } int -xfs_attr_get(bhv_desc_t *bdp, char *name, char *value, int *valuelenp, +xfs_attr_get(bhv_desc_t *bdp, const char *name, char *value, int *valuelenp, int flags, struct cred *cred) { xfs_inode_t *ip = XFS_BHVTOI(bdp); @@ -202,7 +202,7 @@ /*ARGSUSED*/ int /* error */ -xfs_attr_set(bhv_desc_t *bdp, char *name, char *value, int valuelen, int flags, +xfs_attr_set(bhv_desc_t *bdp, const char *name, char *value, int valuelen, int flags, struct cred *cred) { xfs_da_args_t args; @@ -462,7 +462,7 @@ */ /*ARGSUSED*/ int /* error */ -xfs_attr_remove(bhv_desc_t *bdp, char *name, int flags, struct cred *cred) +xfs_attr_remove(bhv_desc_t *bdp, const char *name, int flags, struct cred *cred) { xfs_da_args_t args; xfs_inode_t *dp; Index: xfs_attr.h =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_attr.h,v retrieving revision 1.32 diff -u -u -r1.32 xfs_attr.h --- xfs_attr.h 18 May 2005 09:29:33 -0000 1.32 +++ xfs_attr.h 16 Aug 2005 01:13:07 -0000 @@ -172,15 +172,15 @@ /* * Overall external interface routines. */ -int xfs_attr_get(bhv_desc_t *, char *, char *, int *, int, struct cred *); -int xfs_attr_set(bhv_desc_t *, char *, char *, int, int, struct cred *); -int xfs_attr_remove(bhv_desc_t *, char *, int, struct cred *); +int xfs_attr_get(bhv_desc_t *, const char *, char *, int *, int, struct cred *); +int xfs_attr_set(bhv_desc_t *, const char *, char *, int, int, struct cred *); +int xfs_attr_remove(bhv_desc_t *, const char *, int, struct cred *); int xfs_attr_list(bhv_desc_t *, char *, int, int, struct attrlist_cursor_kern *, struct cred *); int xfs_attr_inactive(struct xfs_inode *dp); int xfs_attr_shortform_getvalue(struct xfs_da_args *); -int xfs_attr_fetch(struct xfs_inode *, char *, int, +int xfs_attr_fetch(struct xfs_inode *, const char *, int, char *, int *, int, struct cred *); #endif /* __XFS_ATTR_H__ */ Index: xfs_da_btree.c =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_da_btree.c,v retrieving revision 1.153 diff -u -u -r1.153 xfs_da_btree.c --- xfs_da_btree.c 22 Jun 2005 03:43:05 -0000 1.153 +++ xfs_da_btree.c 16 Aug 2005 01:13:08 -0000 @@ -1626,7 +1626,7 @@ * This is implemented with some source-level loop unrolling. */ xfs_dahash_t -xfs_da_hashname(uchar_t *name, int namelen) +xfs_da_hashname(const uchar_t *name, int namelen) { xfs_dahash_t hash; Index: xfs_da_btree.h =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_da_btree.h,v retrieving revision 1.58 diff -u -u -r1.58 xfs_da_btree.h --- xfs_da_btree.h 18 May 2005 09:29:33 -0000 1.58 +++ xfs_da_btree.h 16 Aug 2005 01:13:08 -0000 @@ -168,7 +168,7 @@ * Structure to ease passing around component names. */ typedef struct xfs_da_args { - uchar_t *name; /* string (maybe not NULL terminated) */ + const uchar_t *name; /* string (maybe not NULL terminated) */ int namelen; /* length of string (maybe no NULL) */ uchar_t *value; /* set of bytes (maybe contain NULLs) */ int valuelen; /* length of value */ @@ -314,7 +314,7 @@ int xfs_da_shrink_inode(xfs_da_args_t *args, xfs_dablk_t dead_blkno, xfs_dabuf_t *dead_buf); -uint xfs_da_hashname(uchar_t *name_string, int name_length); +uint xfs_da_hashname(const uchar_t *name_string, int name_length); uint xfs_da_log2_roundup(uint i); xfs_da_state_t *xfs_da_state_alloc(void); void xfs_da_state_free(xfs_da_state_t *state); --sdtB3X0nJg68CQEu-- From owner-linux-xfs@oss.sgi.com Tue Aug 16 03:57:58 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 03:58:04 -0700 (PDT) Received: from kylehp.net ([222.47.66.118]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7GAvIH9004009; Tue, 16 Aug 2005 03:57:27 -0700 Message-ID: <99FC9E98.B0AB484@kylehp.net> Date: Tue, 16 Aug 2005 03:13:16 +0800 Reply-To: "emmett dallmier" From: "emmett dallmier" User-Agent: phpmailer [version 1.65] X-Accept-Language: en-us MIME-Version: 1.0 To: "Edmundo Alonzo" , , , Subject: RE: Significant Re: Your Order # 3258 spirit Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-archive-position: 5892 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: margo@kylehp.net Precedence: bulk X-list: linux-xfs Content-Length: 895 Lines: 21 At this site we value your input and that is why we take the most time selecting the season's most popular wholesale repliica bags, watches or whatever luxury, and these are all offered on our famous e shop voted #1 by fashion explorer. http://uk.geocities.com/rainsnaregreat/?nsysstnt Omega, rolex, AP,Oris, Gucci, Cartier, Breitling, TAG, RADO, IWC, Tissto, V.C, Patek.p, Mont Blanc, BVGARI, Panerai, A.Lange@Sohne, Hermes, Movado, Longines, LV, Maurice L, Technomarine, Christian Dior, Fendi, DKNY, Chanel, Baune& Mercier, Ebel, Concord, Corum, Piaget, Jaeger LEC, Chopard, Girard-P, Titoni, Tudor, Breguet, Blancpain, Franck Muller, Dunhill, Versace, Zenith, Calvin Klein You love "Grease" baby I love "Snatch" But even so we're a perfect match fbquantize einnreq frbool xm05 extroverted-sensate freiheit Yes it's gone and on, and on, and onYes it's gone and on, and on, and on From owner-linux-xfs@oss.sgi.com Tue Aug 16 06:43:04 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 06:43:17 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.202]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7GDh3H9016980 for ; Tue, 16 Aug 2005 06:43:04 -0700 Received: by zproxy.gmail.com with SMTP id 18so864386nzp for ; Tue, 16 Aug 2005 06:40:48 -0700 (PDT) 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=nI60Aieu36dnRtRWxayu13eLM+ElqdUxGjv3LuPdkIAQHAGJG/TOCzLC2OI+8k2NwjhD3pAzmBT6glyWGCULBky2Ofd2v5qqqHIRL8oyauVsGsKfY4rMDJV8r38LjWlmGs1iHtR/4+GStjrz4pXsjjggh0kqvTPp6hW9IyQPlac= Received: by 10.36.108.15 with SMTP id g15mr3516188nzc; Tue, 16 Aug 2005 06:40:48 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Tue, 16 Aug 2005 06:40:48 -0700 (PDT) Message-ID: Date: Tue, 16 Aug 2005 09:40:48 -0400 From: A JM To: Christian Subject: Re: [OT] Re: XFS - hard drive dying Cc: linux-xfs@oss.sgi.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> <44568.195.126.66.126.1124142843.squirrel@housecafe.dyndns.org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7GDh4H9016984 X-archive-position: 5893 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 83594 Lines: 1577 This is from the log file after reinstalling the drive in the box before the crash when it was in working order. If I read this correctly it is an XFS filesystem?? EXT3 FS on hdb3, internal journal SGI XFS with ACLs, security attributes, large block numbers, no debug enabled SGI XFS Quota Management subsystem XFS mounting filesystem dm-0 Starting XFS recovery on filesystem: dm-0 (dev: dm-0) hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08001 ("xfs_trans_read_buf") error 5 buf count 512 xfs_force_shutdown(dm-0,0x1) called from line 422 of file fs/xfs/xfs_trans_buf.c. Return address = 0xe2e521b4 Filesystem "dm-0": I/O Error Detected. Shutting down filesystem: dm-0 Please umount the filesystem, and rectify the problem(s) hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#1)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098056, high=22, low=1999304, sector=371098055 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098055 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08000 ("xfs_trans_read_buf") error 5 buf count 8192 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xfs_trans_read_buf") error 5 buf count 512 hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, high=22, low=1999296, sector=371098047 ide: failed opcode was: unknown end_request: I/O error, dev hdd, sector 371098047 I/O error in filesystem ("dm-0") meta-data dev dm-0 block 0x27d08002 ("xlog_recover_process_iunlinks(#2)") error 5 buf count 512 Ending XFS recovery on filesystem: dm-0 (dev: dm-0) Adding 522104k swap on /dev/hdb2. Priority:-1 extents:1 From owner-linux-xfs@oss.sgi.com Tue Aug 16 07:42:35 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 07:42:41 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7GEgZH9021482 for ; Tue, 16 Aug 2005 07:42:35 -0700 Received: by zproxy.gmail.com with SMTP id 18so872796nzp for ; Tue, 16 Aug 2005 07:40:20 -0700 (PDT) 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=XAh9N3ctznkTPOQuL9mCZgrZEHNRzGrT86Ggk7mY2sL/gBfVVf6evgAIvvJlH2MkoJKQ8DOCZxzfdbQKupNWcw+CjBhLSgJL8YomD5CuJS2HEoEvQX33nMdM+eh7xd25/mNCmeSl16Rb03vD4OnKpCbT9pIMzIfb1+ZK3RgcK00= Received: by 10.37.14.76 with SMTP id r76mr4544713nzi; Tue, 16 Aug 2005 07:40:17 -0700 (PDT) Received: by 10.36.138.16 with HTTP; Tue, 16 Aug 2005 07:40:17 -0700 (PDT) Message-ID: Date: Tue, 16 Aug 2005 10:40:17 -0400 From: A JM To: Christian Subject: Re: [OT] Re: XFS - hard drive dying Cc: linux-xfs@oss.sgi.com In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> <44568.195.126.66.126.1124142843.squirrel@housecafe.dyndns.org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7GEgZH9021485 X-archive-position: 5896 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbtalent@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 881 Lines: 25 Thi is from the boot log showing what I think is the drives being similiar in size, but there are differences? Probing IDE interface ide0... hda: Maxtor 6L200R0, ATA DISK drive hdb: Maxtor 6Y160P0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Probing IDE interface ide1... hdc: Hewlett-Packard DVD Writer 300, ATAPI CD/DVD-ROM drive hdd: Maxtor 6Y200P0, ATA DISK drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 1024KiB hda: 398297088 sectors (203928 MB) w/16384KiB Cache, CHS=24792/255/63, UDMA(33) hda: cache flushes supported hda: hda1 hdb: max request size: 1024KiB hdb: 320173056 sectors (163928 MB) w/7936KiB Cache, CHS=19929/255/63, UDMA(33) hdb: cache flushes supported hdb: hdb1 hdb2 hdb3 hdb4 hdd: max request size: 1024KiB hdd: 398297088 sectors (203928 MB) w/7936KiB Cache, CHS=24792/255/63, UDMA(133) hdd: cache flushes supported hdd: hdd1 From owner-linux-xfs@oss.sgi.com Tue Aug 16 12:46:02 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 12:46:08 -0700 (PDT) Received: from dynamicweb.hu ([195.228.155.139]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7GJk0H9015592 for ; Tue, 16 Aug 2005 12:46:02 -0700 Received: from LocalHost (3e44bb10.adsl.enternet.hu [62.68.187.16]) by dynamicweb.hu (8.12.8/8.12.8) with SMTP id j7GJlw9W008634 for ; Tue, 16 Aug 2005 21:47:59 +0200 From: djani22@dynamicweb.hu Message-ID: <022d01c5a29a$bf3df860$0400a8c0@LocalHost> To: References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> Subject: Re: XFS-log +performance question Date: Tue, 16 Aug 2005 21:43:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 5897 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: djani22@dynamicweb.hu Precedence: bulk X-list: linux-xfs Content-Length: 717 Lines: 27 Hello list, I have a little performance problem on my 8TB system. I use 4 disk nodes. The 4 disk node is joined with RAID0, chunksize 32k. (4x 2TB) The problem is, the node-2. and node-3. is much more loaded then another. I searching this problems source for a long time, and I found one reason: The XFS's log is always on node 3 (on the third 32k chunk). Am I right? It is possible to get out the log to an alternative free and fast device without re-"format" the whole filesystem? Additionally the node-2 and node-3 reads about 4x - 5x more blocks than the 1 and 4, but I don't know why. If somebody has an idea, let me know! :-) This is the blottleneck of my system, but I can't fix it. :( Thanks Janos From owner-linux-xfs@oss.sgi.com Tue Aug 16 13:00:24 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 13:00:27 -0700 (PDT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.195]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7GK0NH9016641 for ; Tue, 16 Aug 2005 13:00:24 -0700 Received: by wproxy.gmail.com with SMTP id i13so19201wra for ; Tue, 16 Aug 2005 12:58:08 -0700 (PDT) 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:content-transfer-encoding:content-disposition; b=T25Qq0Jz7hPynyg6oZe8KE8j2qgt6XQVIPIbr8kOuCUNRzeDIaFQ/u7S+lCiBEaXwd9AaCGuLw7BEpRYMKHzOY8NYRxdF8YNPKONBKCEHOKkojBEx92FClmc6QAu2kHiEZa0V46SXJg9lh9gOk6Hp6smDoK0i4WuoeQEzrrlSCM= Received: by 10.54.34.33 with SMTP id h33mr4540127wrh; Tue, 16 Aug 2005 12:58:08 -0700 (PDT) Received: by 10.54.47.12 with HTTP; Tue, 16 Aug 2005 12:58:08 -0700 (PDT) Message-ID: Date: Tue, 16 Aug 2005 13:58:08 -0600 From: Nick I To: linux-xfs@oss.sgi.com Subject: Thanks for the help Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7GK0OH9016643 X-archive-position: 5898 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: clusterbuilder@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 801 Lines: 20 Hi, Thanks you everyone for submitting links about HPC related projects and sites to Cluster Builder (http://www.clusterbuilder.org). Upon suggestions sent by the HPC community, I added sections for Grid middleware and end-user applications under the "Software" category. I want to continue making Cluster Builder a helpful research tool for HPC related information. So I'd like to know, based upon your experience, if there are any other important components you run on your cluster that I failed to note, or are there changes you would make in how I listed the applications. Please go ahead and respond to this email in the user list so that others can give their opinions as well. Links that you mention in the user list I will be sure to include on Cluster Builder. Thanks for the help, Nick From owner-linux-xfs@oss.sgi.com Tue Aug 16 17:04:19 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 17:04:45 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7H04HH9002835 for ; Tue, 16 Aug 2005 17:04:18 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA19633; Wed, 17 Aug 2005 10:01:56 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7H01Tg81838491; Wed, 17 Aug 2005 10:01:30 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7H01ST71838833; Wed, 17 Aug 2005 10:01:28 +1000 (EST) Date: Wed, 17 Aug 2005 10:01:28 +1000 From: David Chinner To: djani22@dynamicweb.hu Cc: linux-xfs@oss.sgi.com Subject: Re: XFS-log +performance question Message-ID: <20050817000128.GA1798768@melbourne.sgi.com> References: <001001c59bfb$1fe7aae0$0400a8c0@LocalHost> <42F74B6D.8060002@gmx.net> <00d801c59c20$e0354080$0400a8c0@LocalHost> <42F798AF.5080505@gmx.net> <022d01c5a29a$bf3df860$0400a8c0@LocalHost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <022d01c5a29a$bf3df860$0400a8c0@LocalHost> User-Agent: Mutt/1.4.1i X-archive-position: 5900 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1233 Lines: 45 On Tue, Aug 16, 2005 at 09:43:07PM +0200, djani22@dynamicweb.hu wrote: > Hello list, > > I have a little performance problem on my 8TB system. ...... > I searching this problems source for a long time, and I found one reason: > > The XFS's log is always on node 3 (on the third 32k chunk). > Am I right? The internal log is located in the middle (by block number) of the filesystem by default. Where this is physically located on disk depends on your device layout. If you really have a RAID0 stripe, then the log will be striped across all the disks in the RAID0 stripe. > It is possible to get out the log to an alternative free and fast device > without re-"format" the whole filesystem? Ob-FAQ: Google is your friend. See the link below for details. However, I'll repeat the BFW here: PRACTICE THIS ON A DEVICE YOU DO NOT CARE ABOUT FIRST!!! http://oss.sgi.com/archives/linux-xfs/2003-11/msg00171.html > Additionally the node-2 and node-3 reads about 4x - 5x more blocks than the > 1 and 4, but I don't know why. > If somebody has an idea, let me know! :-) We never read from the log, so I doubt the log is responsible for this. Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Tue Aug 16 21:23:23 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Aug 2005 21:23:27 -0700 (PDT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7H4NLH9019046 for ; Tue, 16 Aug 2005 21:23:22 -0700 Received: (qmail invoked by alias); 17 Aug 2005 04:21:05 -0000 Received: from G3578.g.pppool.de (EHLO [192.168.10.11]) [80.185.53.120] by mail.gmx.net (mp014) with SMTP; 17 Aug 2005 06:21:05 +0200 X-Authenticated: #2986359 Message-ID: <4302BB34.9030400@gmx.net> Date: Wed, 17 Aug 2005 06:21:08 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: [OT] Re: XFS - hard drive dying References: <42FFA383.7020807@gmx.net> <4300C29D.1030302@gmx.net> <14367.195.126.66.126.1124137430.squirrel@housecafe.dyndns.org> <44568.195.126.66.126.1124142843.squirrel@housecafe.dyndns.org> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5901 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 1227 Lines: 35 A JM schrieb: > This is from the log file after reinstalling the drive in the box > before the crash when it was in working order. > > If I read this correctly it is an XFS filesystem?? > > > EXT3 FS on hdb3, internal journal > SGI XFS with ACLs, security attributes, large block numbers, no debug enabled > SGI XFS Quota Management subsystem > XFS mounting filesystem dm-0 > Starting XFS recovery on filesystem: dm-0 (dev: dm-0) > hdd: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdd: dma_intr: error=0x40 { UncorrectableError }, LBAsect=371098048, [..] so, hdb3 is ext3, but the errors show up on hdd and dm-0 is complaining, so i guess dm-0 is made of hdd and....? > Thi is from the boot log showing what I think is the drives being > similiar in size, but there are differences? ok, the drives are the same. but that's what LVM is for: it usually hold several groups of physical storage devices. so even when your hda is big enough to hold all data of hdd - if dm-0 is made of hdd + some_other_disk, then dm-0 is probably bigger than hda. but all this has nothing to do with xfs any more... Christian. -- BOFH excuse #222: I'm not sure. Try calling the Internet's head office -- it's in the book. From owner-linux-xfs@oss.sgi.com Wed Aug 17 13:47:42 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Aug 2005 13:47:54 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.197]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7HKlfH9003602 for ; Wed, 17 Aug 2005 13:47:41 -0700 Received: by zproxy.gmail.com with SMTP id 18so173056nzp for ; Wed, 17 Aug 2005 13:45:25 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:mime-version:content-disposition:content-type:content-transfer-encoding:message-id; b=N+ateX/ZLGAqkn/+VBGKoNG34fq0F14OJUDr4qz4vi9rM50CMs0HyKgXcIxn/k5iu0CWJI7UMiId8VygZZ+/oCg7/D/B+1UfcI5xU0c5wbpclNgh0bTDrO0VC2KQDZP/fepSNQsceDdiaQLhaJWCHd3Nbny61qiYTC1s85Ic/K4= Received: by 10.36.126.9 with SMTP id y9mr838355nzc; Wed, 17 Aug 2005 13:45:25 -0700 (PDT) Received: from ?172.16.2.11? ([213.237.34.34]) by mx.gmail.com with ESMTP id 39sm1061680nzk.2005.08.17.13.45.23; Wed, 17 Aug 2005 13:45:25 -0700 (PDT) From: Jesper Juhl To: xfs-masters@oss.sgi.com Subject: [PATCH] pull XFS support out of Kconfig submenu Date: Wed, 17 Aug 2005 22:45:48 +0200 User-Agent: KMail/1.8.2 Cc: nathans@sgi.com, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200508172245.49043.jesper.juhl@gmail.com> X-archive-position: 5903 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jesper.juhl@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 1034 Lines: 41 It seems slightly odd to me that XFS support should be in a separate submenu, when all the other filesystems are not using submenus but are directly selectable from the Filesystems menu. This patch makes XFS Kconfig entries behave like everything else. Ignore if there's a good reason for the menu, please consider applying otherwise. Please Cc: me on replies. Signed-off-by: Jesper Juhl --- fs/xfs/Kconfig | 5 +---- 1 files changed, 1 insertion(+), 4 deletions(-) --- linux-2.6.13-rc6-git9-orig/fs/xfs/Kconfig 2005-06-17 21:48:29.000000000 +0200 +++ linux-2.6.13-rc6-git9/fs/xfs/Kconfig 2005-08-17 22:38:26.000000000 +0200 @@ -1,5 +1,3 @@ -menu "XFS support" - config XFS_FS tristate "XFS filesystem support" select EXPORTFS if NFSD!=n @@ -22,6 +20,7 @@ config XFS_EXPORT bool + depends on XFS_FS default y if XFS_FS && EXPORTFS config XFS_RT @@ -81,5 +80,3 @@ Linux website . If you don't know what Access Control Lists are, say N. - -endmenu From owner-linux-xfs@oss.sgi.com Thu Aug 18 02:57:27 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Aug 2005 02:57:35 -0700 (PDT) Received: from pingus.pingus.org (pingus.pingus.org [82.66.123.179]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7I9vQH9013224 for ; Thu, 18 Aug 2005 02:57:27 -0700 Received: from www.pingus.org (localhost [127.0.0.1]) by pingus.pingus.org (Postfix) with ESMTP id 21BE240B27; Thu, 18 Aug 2005 11:55:09 +0200 (CEST) Received: from 194.2.155.29 (SquirrelMail authenticated user brice) by www.pingus.org with HTTP; Thu, 18 Aug 2005 11:55:09 +0200 (CEST) Message-ID: <2766.194.2.155.29.1124358909.squirrel@www.pingus.org> In-Reply-To: <39182.194.2.155.16.1123598505.squirrel@www.pingus.org> References: <3761.194.2.155.29.1123053709.squirrel@www.pingus.org> <20050804090050.B21661319@melbourne.sgi.com> <3088.194.2.155.29.1123145618.squirrel@www.pingus.org> <20050805104037.A22198673@melbourne.sgi.com> <39182.194.2.155.16.1123598505.squirrel@www.pingus.org> Date: Thu, 18 Aug 2005 11:55:09 +0200 (CEST) Subject: Re: XFS trouble. From: "Brice GIBOUDEAU" To: "Brice GIBOUDEAU" Cc: "David Chinner" , "Brice GIBOUDEAU" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-archive-position: 5906 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: brice@pingus.org Precedence: bulk X-list: linux-xfs Content-Length: 3384 Lines: 114 Patch is working fine, the server is stable. Thanks for your support. Brice GIBOUDEAU > Hi, > > Thanks for all this informations. > I'm testing an other solution, it's using a patch who increase the > quantity of low memory. > http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.23pre6aa3/00_3.5G-address-space-5 > http://lwn.net/Articles/39925/ > > I will reply to this Email if the patch work correctly. > > Thx, > Brice GIBOUDEAU > > > >> On Thu, Aug 04, 2005 at 10:53:38AM +0200, Brice GIBOUDEAU wrote: >>> Hi, >>> >>> I give more details. >> >> Ta. Looks like lowmem exhaustion: >> >>> /proc/meminfo : >>> --------------- >>> >>> Tue Aug 2 02:04:01 CEST 2005 >>> total: used: free: shared: buffers: cached: >>> Mem: 16966471680 15623704576 1342767104 0 180224 14847438848 >>> Swap: 32737632256 0 32737632256 >>> MemTotal: 16568820 kB >>> MemFree: 1311296 kB >>> MemShared: 0 kB >>> Buffers: 176 kB >>> Cached: 14499452 kB >> >> Large page cache... >> >>> SwapCached: 0 kB >>> Active: 1932 kB >>> Inactive: 14497760 kB >> >> Mostly inactive... >> >>> HighTotal: 15858532 kB >>> HighFree: 1305552 kB >>> LowTotal: 710288 kB >>> LowFree: 5744 kB >> >> And very little low memory free. >> >>> LowTotal: 710288 kB >>> LowFree: 4788 kB >> >> Yup, not much there at all. >> >>> /proc/slabinfo : >>> ---------------- >>> >>> Tue Aug 2 02:04:02 CEST 2005 >>> slabinfo - version: 1.1 (SMP) >>> xfs_inode 208657 208719 408 23191 23191 1 : 124 62 >>> linvfs_icache 208700 208700 384 20870 20870 1 : 124 62 >>> buffer_head 3624879 3751050 128 125034 125035 1 : 252 126 >> >> So we have 80MiB in xfs inodes, another 80MiB in linvfs_icache, and >> 460MiB in buffer heads. So that's a total of 620MiB of your 700MiB >> of low memory right there, and probably the source of the memory >> exhaustion. >> >> The buffer heads are the real problem - and that's related to the >> size of the page cache. IIRC we have at least one buffer head per >> page. With 14499452k of page cache, that's at least 3,624,863 buffer >> heads needed at one per page. Looks pretty close, to me. >> >> This does look like a highmem/lowmem reclaim issue to me - the >> pagecache in the highmem area needs to be reclaimed to free >> up buffer heads in the lowmem region. because there is lots >> of free memory in the highmem region, I doubt the reclaim >> code is freeing it up sufficiently. >> >> One quick thing to try is limit the machine to, say, 12GiB of RAM >> (mem=xxx boot option) and that will limit buffer head usage to less >> that 400MiB of low memory. That should prevent you from exhausting >> lowmem by bounding the maximum size of the kernel pagecache at >> a point below where lowmem exhaustion occurs. >> >> Another option is to go to a 2.6 kernel as, IIRC, XFS no longer >> has the buffer-head-per-cached-page behaviour in 2.6. Hence you >> won't consume anywhere near as much lowmem on a 2.6 kernel when >> the kernel lets the page cache grow so large.... >> >> Yet another option is to move to a 64bit platform that doesn't have >> this lowmem/highmem memory architecture... >> >> HTH. >> >> Cheers, >> >> Dave. >> -- >> Dave Chinner >> R&D Software Enginner >> SGI Australian Software Group >> > > > From owner-linux-xfs@oss.sgi.com Thu Aug 18 11:51:25 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Aug 2005 11:51:34 -0700 (PDT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.205]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7IIpOH9004647 for ; Thu, 18 Aug 2005 11:51:25 -0700 Received: by rproxy.gmail.com with SMTP id j1so397118rnf for ; Thu, 18 Aug 2005 11:49:06 -0700 (PDT) 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=QLPsjlDatmodWKloXIcKPc1Cb4eW/ghXqjzgBIC1XVZo94aQJE7zRY/pQ7F5nxfmrJESWXElA3nD/HS0E8AunYGsYQrtP/VMAQUeNWok1msPTDmddX2YtqAd3BFcp8Hu0t1TrMyguwqdQN4+EcJ51fV1CIya78DZG8ppiyi/fv8= Received: by 10.11.99.5 with SMTP id w5mr33552cwb; Thu, 18 Aug 2005 11:49:05 -0700 (PDT) Received: by 10.11.94.48 with HTTP; Thu, 18 Aug 2005 11:49:05 -0700 (PDT) Message-ID: Date: Thu, 18 Aug 2005 18:49:05 +0000 From: kristina clair To: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) In-Reply-To: <428D0D1E.9070607@wildbrain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <428511F8.6020303@wildbrain.com> <20050518175925.GA22738@taniwha.stupidest.org> <20050518195251.GY422@unthought.net> <428BA8E4.2040108@wildbrain.com> <428D0D1E.9070607@wildbrain.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7IIpPH9004654 X-archive-position: 5907 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kclair@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 2862 Lines: 72 I've just come across this oops. We're running gentoo with a 2.6.11 kernel, xfs + nfs + lvm (+hardware raid). nfsd was not responding, and the load was at 27. the machine was responsive, other than nfsd. everything had been responsive for at least 9 months previous to this. It seems like from what I've read of this thread, most of the other reports have been from earlier kernel versions? Is there any recommended fix at this point? Thanks, Kristina xfs_iget_core: ambiguous vns: vp/0xc54858a0, invp/0xd391aa08 ------------[ cut here ]------------ kernel BUG at fs/xfs/support/debug.c:106! invalid operand: 0000 [#1] SMP Modules linked in: iptable_filter ip_tables usbcore xfs dm_snapshot 3w_9xxx e1000 CPU: 0 EIP: 0060:[] Not tainted VLI EFLAGS: 00010246 (2.6.11) EIP is at cmn_err+0xa1/0xc0 [xfs] eax: f8e0f284 ebx: f8dfdce0 ecx: c03d2890 edx: 00000293 esi: f8dfd3d7 edi: f8e0fb7e ebp: 00000000 esp: f6e17b34 ds: 007b es: 007b ss: 0068 Process nfsd (pid: 6689, threadinfo=f6e17000 task=f7fef530) Stack: f8dfd3d7 f8dfd39e f8e0fb40 00000293 f6e17000 f8dfdce0 00000000 e7598760 f8dc77e0 00000000 f8dfdce0 c54858a0 d391aa08 c3120bf4 482c5825 00000000 f72d81c0 482c5825 f70afc00 c0172e7c f72d81bc 00000000 00000000 e7598760 Call Trace: [] xfs_iget_core+0x4e0/0x630 [xfs] [] iget_locked+0xac/0xe0 [] xfs_iget+0x174/0x1b0 [xfs] [] xfs_vget+0x78/0x100 [xfs] [] vfs_vget+0x43/0x50 [xfs] [] linvfs_get_dentry+0x51/0x90 [xfs] [] find_exported_dentry+0x44/0x650 [] kfree_skbmem+0x24/0x30 [] tcp_recvmsg+0x2e0/0x730 [] dst_output+0x0/0x30 [] sock_common_recvmsg+0x58/0x80 [] sock_recvmsg+0xf3/0x110 [] schedule+0x39c/0xc00 [] default_wake_function+0x0/0x20 [] recalc_task_prio+0x88/0x150 [] activate_task+0x90/0xb0 [] try_to_wake_up+0x252/0x280 [] __wake_up_common+0x41/0x70 [] __wake_up+0x3e/0x60 [] svc_expkey_lookup+0x3a5/0x410 [] svc_sock_enqueue+0x142/0x2a0 [] linvfs_decode_fh+0x5a/0x90 [xfs] [] nfsd_acceptable+0x0/0x110 [] fh_verify+0x20c/0x5b0 [] nfsd_acceptable+0x0/0x110 [] svcauth_unix_set_client+0xb5/0xd0 [] nfsd_access+0x2f/0x100 [] nfsd3_proc_access+0x8c/0xd0 [] nfsd_dispatch+0xd7/0x200 [] svc_process+0x4b1/0x6a0 [] default_wake_function+0x0/0x20 [] nfsd+0x1cb/0x350 [] nfsd+0x0/0x350 [] kernel_thread_helper+0x5/0x10 Code: b8 40 fb e0 f8 89 44 24 08 8b 04 ad a0 f2 e0 f8 89 44 24 04 e8 01 0a 32 c7 8b 54 24 0c b8 84 f2 e0 f8 e8 93 b8 56 c7 85 ed 75 08 <0f> 0b 6a 00 be d3 df f8 83 c4 10 5b 5e 5f 5d c3 eb 0d 90 90 90 From owner-linux-xfs@oss.sgi.com Thu Aug 18 15:58:00 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Aug 2005 15:58:04 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7IMvwH9032704 for ; Thu, 18 Aug 2005 15:57:59 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA16580; Fri, 19 Aug 2005 08:55:27 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7IMtYkt4077383; Fri, 19 Aug 2005 08:55:35 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7IMtUYT4076389; Fri, 19 Aug 2005 08:55:30 +1000 (EST) Date: Fri, 19 Aug 2005 08:55:29 +1000 From: Nathan Scott To: Russell Cattelan Cc: Jesper Juhl , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: [xfs-masters] Re: [PATCH] pull XFS support out of Kconfig submenu Message-ID: <20050819085529.A4075975@wobbly.melbourne.sgi.com> References: <200508172245.49043.jesper.juhl@gmail.com> <20050818135356.GA16845@taniwha.stupidest.org> <1124378546.25069.107.camel@naboo.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1124378546.25069.107.camel@naboo.americas.sgi.com>; from cattelan@thebarn.com on Thu, Aug 18, 2005 at 10:22:26AM -0500 X-archive-position: 5908 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 421 Lines: 17 On Thu, Aug 18, 2005 at 10:22:26AM -0500, Russell Cattelan wrote: > .. fs/xfs/Kconfig but using submenu was simply a convince thing > to group all the XFS options together. s/convince/convenience/ > If the submenu is really causing people distress go ahead and > remove it. Since it's a cosmetic change it's not going to impact > anything. Yep, I guess we should just queue this up for 2.6.14. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Aug 18 16:00:43 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Aug 2005 16:00:49 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7IN0gH9000886 for ; Thu, 18 Aug 2005 16:00:42 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA16641; Fri, 19 Aug 2005 08:58:18 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7IMwQkt4080982; Fri, 19 Aug 2005 08:58:26 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7IMwNax4081146; Fri, 19 Aug 2005 08:58:23 +1000 (EST) Date: Fri, 19 Aug 2005 08:58:23 +1000 From: Nathan Scott To: kristina clair Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) Message-ID: <20050819085823.B4075975@wobbly.melbourne.sgi.com> References: <20050518175925.GA22738@taniwha.stupidest.org> <20050518195251.GY422@unthought.net> <428BA8E4.2040108@wildbrain.com> <428D0D1E.9070607@wildbrain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from kclair@gmail.com on Thu, Aug 18, 2005 at 06:49:05PM +0000 X-archive-position: 5909 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 386 Lines: 12 On Thu, Aug 18, 2005 at 06:49:05PM +0000, kristina clair wrote: > I've just come across this oops. We're running gentoo with a 2.6.11 > kernel, xfs + nfs + lvm (+hardware raid). Check whether your kernel has this fix included: http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4120db47198d21d8cd3b2cdbbe1ea6118a50bcd4 cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Aug 18 16:35:03 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Aug 2005 16:35:06 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7INZ2H9008351 for ; Thu, 18 Aug 2005 16:35:03 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [198.149.16.15]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7J1V2gV004092 for ; Thu, 18 Aug 2005 18:31:02 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7INVjDN14551517; Thu, 18 Aug 2005 18:31:45 -0500 (CDT) Received: from sgi.com (penguin.americas.sgi.com [128.162.240.135]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id j7INViLL3365896; Thu, 18 Aug 2005 18:31:44 -0500 (CDT) Received: from penguin.americas.sgi.com (localhost.localdomain [127.0.0.1]) by sgi.com (8.12.8/8.12.8) with ESMTP id j7INVhgc026360; Thu, 18 Aug 2005 18:31:43 -0500 Received: (from sandeen@localhost) by penguin.americas.sgi.com (8.12.8/8.12.8/Submit) id j7INVgPD026358; Thu, 18 Aug 2005 18:31:42 -0500 Date: Thu, 18 Aug 2005 18:31:42 -0500 From: Eric Sandeen Message-Id: <200508182331.j7INVgPD026358@penguin.americas.sgi.com> To: sgi.bugs.xfs@fido.engr.sgi.com, linux-xfs@oss.sgi.com, jesper.juhl@gmail.com Subject: TAKE 941397 - tidy up Kconfig menu X-archive-position: 5910 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@penguin.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 425 Lines: 17 tidy up Kconfig menu Date: Thu Aug 18 16:30:08 PDT 2005 Workarea: penguin.americas.sgi.com:/src/eric/xfs-trees/xfs-GUT-clean Inspected by: nathans The following file(s) were checked into: bonnie.engr.sgi.com:/isms/xfs-kern/xfs-linux Modid: xfs-linux:xfs-kern:197653a Kconfig - 1.4 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/Kconfig.diff?r1=text&tr1=1.4&r2=text&tr2=1.3&f=h - tidy up Kconfig menu From owner-linux-xfs@oss.sgi.com Thu Aug 18 19:01:08 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Aug 2005 19:01:13 -0700 (PDT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7J218H9020478 for ; Thu, 18 Aug 2005 19:01:08 -0700 Received: from c-66-30-115-133.hsd1.ma.comcast.net ([66.30.115.133]) by comcast.net (rwcrmhc11) with ESMTP id <2005081901584801300ohn1ae>; Fri, 19 Aug 2005 01:58:48 +0000 Received: from c-66-30-115-133.hsd1.ma.comcast.net (localhost.127.in-addr.arpa [127.0.0.1]) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1) with ESMTP id j7J1wmS3007701 for ; Thu, 18 Aug 2005 21:58:48 -0400 (EDT) (envelope-from rodrigc@c-66-30-115-133.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1/Submit) id j7J1wlcG007700 for linux-xfs@oss.sgi.com; Thu, 18 Aug 2005 21:58:47 -0400 (EDT) (envelope-from rodrigc) Date: Thu, 18 Aug 2005 21:58:47 -0400 From: Craig Rodrigues To: linux-xfs@oss.sgi.com Subject: XFS for FreeBSD, new snapshot available Message-ID: <20050819015847.GA7687@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-archive-position: 5911 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rodrigc@crodrigues.org Precedence: bulk X-list: linux-xfs Content-Length: 1046 Lines: 34 Hi, On behalf of the XFS for FreeBSD project, I would like to announce a new snapshot which you can download and try. The snapshot is available here: http://people.freebsd.org/~rodrigc/xfs/ NOTES: - works only with latest FreeBSD-CURRENT and FreeBSD-6 kernels - read-only access to XFS partitions only - highly experimental and not finished yet, this is a work in progress - do not use for production work NEW THINGS: - several kernel panics fixed - preliminary support for reading extended attributes - xfsprogs in ports ( sysutils/xfsprogs ), needed for mkfs.xfs The XFS for FreeBSD project is porting the SGI XFS filesystem to FreeBSD, based on publically available GPL'd sources of SGI's XFS for Linux. The XFS for FreeBSD project is not affiliated with SGI, and SGI should not be contacted with bug reports regarding XFS for FreeBSD. Many thanks to Russell Cattelan and Alexander Kabaev for their work on this project. We would appreciate your feedback and bug reports. -- Craig Rodrigues rodrigc@crodrigues.org From owner-linux-xfs@oss.sgi.com Fri Aug 19 08:01:48 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 19 Aug 2005 08:02:00 -0700 (PDT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7JF1lH9010122 for ; Fri, 19 Aug 2005 08:01:48 -0700 Received: by rproxy.gmail.com with SMTP id j1so554320rnf for ; Fri, 19 Aug 2005 07:59:30 -0700 (PDT) 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=nkqRYVZqtCEe1MFdaatQ626NXak5A7Vh0QC+ThZ+f2yzz7nPPQusMcC/iswnleEhRkhZrMGwb6oKtaFJIUMfJnRFeZ/0KnQYQSKT22nvXx6y5PdYRyLlS0lnAtx1qCBtf7lBh/kUjiRr4V2mPBybIcjHtXJpDPE+HOHCG6Y3DWM= Received: by 10.11.99.5 with SMTP id w5mr46404cwb; Fri, 19 Aug 2005 07:59:30 -0700 (PDT) Received: by 10.11.94.48 with HTTP; Fri, 19 Aug 2005 07:59:30 -0700 (PDT) Message-ID: Date: Fri, 19 Aug 2005 14:59:30 +0000 From: kristina clair To: Nathan Scott Subject: Re: kernel OOPS for XFS in xfs_iget_core (using NFS+SMP+MD) Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: <20050819085823.B4075975@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <20050518175925.GA22738@taniwha.stupidest.org> <428BA8E4.2040108@wildbrain.com> <428D0D1E.9070607@wildbrain.com> <20050819085823.B4075975@wobbly.melbourne.sgi.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7JF1mH9010124 X-archive-position: 5914 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kclair@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 684 Lines: 28 No, it doesn't. Is that something that should help? Now that the error has occurred once, it occurred again within 24 hours. Thanks, Kristina On 8/18/05, Nathan Scott wrote: > On Thu, Aug 18, 2005 at 06:49:05PM +0000, kristina clair wrote: > > I've just come across this oops. We're running gentoo with a 2.6.11 > > kernel, xfs + nfs + lvm (+hardware raid). > > Check whether your kernel has this fix included: > http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4120db47198d21d8cd3b2cdbbe1ea6118a50bcd4 > > cheers. > > -- > Nathan > -- kristina clair, latest stable version: 2.9 latest beta version: 3.0-pre From owner-linux-xfs@oss.sgi.com Fri Aug 19 16:46:02 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 19 Aug 2005 16:46:07 -0700 (PDT) Received: from mailout.stusta.mhn.de ([141.84.69.5]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7JNjwH9005540 for ; Fri, 19 Aug 2005 16:46:02 -0700 Received: (qmail 9469 invoked from network); 19 Aug 2005 23:43:30 -0000 Received: from r063144.stusta.swh.mhn.de (10.150.63.144) by mailhub.stusta.mhn.de with SMTP; 19 Aug 2005 23:43:30 -0000 Received: by r063144.stusta.swh.mhn.de (Postfix, from userid 1000) id 83563BB76A; Sat, 20 Aug 2005 01:43:30 +0200 (CEST) Date: Sat, 20 Aug 2005 01:43:30 +0200 From: Adrian Bunk To: xfs-masters@oss.sgi.com Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: [2.6 patch] fs/xfs/linux-2.6/xfs_buf.h: "extern inline" doesn't make sense Message-ID: <20050819234330.GF3615@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i X-archive-position: 5917 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bunk@stusta.de Precedence: bulk X-list: linux-xfs Content-Length: 569 Lines: 17 "extern inline" doesn't make sense. Signed-off-by: Adrian Bunk --- linux-2.6.13-rc6-mm1-full/fs/xfs/linux-2.6/xfs_buf.h.old 2005-08-19 23:23:40.000000000 +0200 +++ linux-2.6.13-rc6-mm1-full/fs/xfs/linux-2.6/xfs_buf.h 2005-08-19 23:23:47.000000000 +0200 @@ -452,7 +452,7 @@ #define XFS_BUF_PTR(bp) (xfs_caddr_t)((bp)->pb_addr) -extern inline xfs_caddr_t xfs_buf_offset(xfs_buf_t *bp, size_t offset) +static inline xfs_caddr_t xfs_buf_offset(xfs_buf_t *bp, size_t offset) { if (bp->pb_flags & PBF_MAPPED) return XFS_BUF_PTR(bp) + offset; From owner-linux-xfs@oss.sgi.com Sat Aug 20 02:36:04 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Aug 2005 02:36:08 -0700 (PDT) Received: from mail.butterblume.org ([193.151.7.122]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7K9a3H9027954 for ; Sat, 20 Aug 2005 02:36:04 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.butterblume.org (Postfix) with ESMTP id E8B85804F for ; Sat, 20 Aug 2005 11:33:39 +0200 (CEST) Received: from butterblume (xdsl-81-173-183-126.netcologne.de [81.173.183.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.butterblume.org (Postfix) with ESMTP id 8F0637E9C for ; Sat, 20 Aug 2005 11:33:39 +0200 (CEST) Date: Sat, 20 Aug 2005 11:33:41 +0200 From: Markus Meyer To: linux-xfs@oss.sgi.com Subject: Find file for inode Message-ID: <20050820093341.GA15491@butterblume> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline X-GPG-Fingerprint: B87120ED/A293 CEE1 43FB 22B2 F3F5 72D3 147D 6B31 B871 20ED User-Agent: mutt-ng devel-20050619 (Debian) X-archive-position: 5919 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mm@butterblume.org Precedence: bulk X-list: linux-xfs Content-Length: 1059 Lines: 36 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi folks, My Smartmontools reported a defect block on one of my disks with an XFS on them. So I wanted to follow the Badblocks-Howto [1] to find the corresponding Inode and the file that I can "repair" the block and restore the file. But I have no idea how to accomplish this on XFS.=20 Is there anyone around who can help me? Well there aren't that many docs around and the man pages are not a big help (or maybe I'm just blind). I'm running Debian Linux under 2.6.12.=20 Cheers, --=20 Markus Meyer - encrypted email preferred -> GPG: B87120ED [1] http://smartmontools.sourceforge.net/BadBlockHowTo.txt --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD4DBQFDBvj1FH1rMbhxIO0RAhwfAJiB2sNlQR4bI3eNAXgnl1FiYGsDAJ43I/jN EabZihgC1cB8S3Q09jAjDQ== =iUSW -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-linux-xfs@oss.sgi.com Sat Aug 20 02:52:33 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Aug 2005 02:52:36 -0700 (PDT) Received: from amanpulo.hosting.qsr.com.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7K9qWH9029443 for ; Sat, 20 Aug 2005 02:52:33 -0700 Received: from localhost (localhost [127.0.0.1]) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id 5DBC41C4B47D for ; Sat, 20 Aug 2005 17:50:12 +0800 (PHT) Received: from musang.free.net.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id 82DC71C4A877 for ; Sat, 20 Aug 2005 17:50:08 +0800 (PHT) Received: by musang.free.net.ph (Postfix, from userid 1000) id 97F041602A36B; Sat, 20 Aug 2005 17:50:05 +0800 (PHT) Date: Sat, 20 Aug 2005 17:50:05 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050820095005.GI2340@free.net.ph> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050820093341.GA15491@butterblume> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050820093341.GA15491@butterblume> X-Personal-URL: http://jijo.free.net.ph User-Agent: Mutt/1.5.9i X-archive-position: 5920 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jijo@free.net.ph Precedence: bulk X-list: linux-xfs Content-Length: 1053 Lines: 23 On Sat, Aug 20, 2005 at 11:33:41AM +0200, Markus Meyer wrote: > My Smartmontools reported a defect block on one of my disks with an > XFS on them. So I wanted to follow the Badblocks-Howto [1] to find the > corresponding Inode and the file that I can "repair" the block and > restore the file. But I have no idea how to accomplish this on XFS. > Is there anyone around who can help me? Well there aren't that many > docs around and the man pages are not a big help (or maybe I'm just > blind). > > I'm running Debian Linux under 2.6.12. AFAIK you can't do this with XFS. The best thing to do will be to replace your hard drive. If you can't do that, try running badblocks(8) in non-destructive read-write mode. This will attempt to read and then write on every block of your drive. The write, in particular, should trigger a remap using your drive's spare blocks, and may "fix" things. --> Jijo -- Federico Sevilla III : jijo.free.net.ph : When we speak of free software GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price. From owner-linux-xfs@oss.sgi.com Sat Aug 20 02:57:16 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Aug 2005 02:57:19 -0700 (PDT) Received: from amanpulo.hosting.qsr.com.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7K9vFH9030185 for ; Sat, 20 Aug 2005 02:57:16 -0700 Received: from localhost (localhost [127.0.0.1]) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id E484D1C4B46C for ; Sat, 20 Aug 2005 17:54:57 +0800 (PHT) Received: from musang.free.net.ph (amanpulo.hosting.qsr.com.ph [64.34.170.22]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by amanpulo.hosting.qsr.com.ph (Postfix) with ESMTP id D45F01C4A877 for ; Sat, 20 Aug 2005 17:54:53 +0800 (PHT) Received: by musang.free.net.ph (Postfix, from userid 1000) id F0FC21602A36B; Sat, 20 Aug 2005 17:54:50 +0800 (PHT) Date: Sat, 20 Aug 2005 17:54:50 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050820095450.GJ2340@free.net.ph> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050820093341.GA15491@butterblume> <20050820095005.GI2340@free.net.ph> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050820095005.GI2340@free.net.ph> X-Personal-URL: http://jijo.free.net.ph User-Agent: Mutt/1.5.9i X-archive-position: 5921 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jijo@free.net.ph Precedence: bulk X-list: linux-xfs Content-Length: 1590 Lines: 34 On Sat, Aug 20, 2005 at 05:50:05PM +0800, Federico Sevilla III wrote: > On Sat, Aug 20, 2005 at 11:33:41AM +0200, Markus Meyer wrote: > > My Smartmontools reported a defect block on one of my disks with an > > XFS on them. So I wanted to follow the Badblocks-Howto [1] to find > > the corresponding Inode and the file that I can "repair" the block > > and restore the file. But I have no idea how to accomplish this on > > XFS. Is there anyone around who can help me? Well there aren't that > > many docs around and the man pages are not a big help (or maybe I'm > > just blind). > > > > I'm running Debian Linux under 2.6.12. > > AFAIK you can't do this with XFS. The best thing to do will be to > replace your hard drive. If you can't do that, try running > badblocks(8) in non-destructive read-write mode. This will attempt to > read and then write on every block of your drive. The write, in > particular, should trigger a remap using your drive's spare blocks, > and may "fix" things. I was a tad too quick with that reply. In hindsight, I'm not sure if the procedure in the Badblocks HOWTO that you linked to can or cannot be done with XFS. Maybe there's something that can be conjured up using xfs_db(8). We can wait for the XFS experts to chime in. The badblocks(8) approach holds, though. You can even give it start and end blocks, to limit the area it will "scrub". Check the manual page for more information. --> Jijo -- Federico Sevilla III : jijo.free.net.ph : When we speak of free software GNU/Linux Specialist : GnuPG 0x93B746BE : we refer to freedom, not price. From owner-linux-xfs@oss.sgi.com Sat Aug 20 03:18:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Aug 2005 03:19:04 -0700 (PDT) Received: from mail.butterblume.org ([193.151.7.122]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7KAIwH9032051 for ; Sat, 20 Aug 2005 03:18:58 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.butterblume.org (Postfix) with ESMTP id BADAA804F for ; Sat, 20 Aug 2005 12:16:36 +0200 (CEST) Received: from butterblume (xdsl-81-173-183-126.netcologne.de [81.173.183.126]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.butterblume.org (Postfix) with ESMTP id 64A6D7E9C for ; Sat, 20 Aug 2005 12:16:36 +0200 (CEST) Date: Sat, 20 Aug 2005 12:16:38 +0200 From: Markus Meyer To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050820101638.GC15491@butterblume> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050820093341.GA15491@butterblume> <20050820095005.GI2340@free.net.ph> <20050820095450.GJ2340@free.net.ph> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="S1BNGpv0yoYahz37" Content-Disposition: inline In-Reply-To: <20050820095450.GJ2340@free.net.ph> X-GPG-Fingerprint: B87120ED/A293 CEE1 43FB 22B2 F3F5 72D3 147D 6B31 B871 20ED User-Agent: mutt-ng devel-20050619 (Debian) X-archive-position: 5922 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mm@butterblume.org Precedence: bulk X-list: linux-xfs Content-Length: 953 Lines: 35 --S1BNGpv0yoYahz37 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On [Sat, Aug 20 17:54], Federico Sevilla III wrote: Hi Federico, >I was a tad too quick with that reply. In hindsight, I'm not sure if the >procedure in the Badblocks HOWTO that you linked to can or cannot be >done with XFS. Maybe there's something that can be conjured up using >xfs_db(8). We can wait for the XFS experts to chime in. So far I'm running "badblocks" until the experts wake up and had their first coffee. Thx. Cheers, --=20 Markus Meyer - encrypted email preferred -> GPG: B87120ED --S1BNGpv0yoYahz37 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDBwMGFH1rMbhxIO0RAmYmAJ9+4rQ6TVawO6rMH7mxfbhxMf1jegCfS0ux 3jxQg9egZhlBwO3H0Ls4r5Q= =XDSE -----END PGP SIGNATURE----- --S1BNGpv0yoYahz37-- From owner-linux-xfs@oss.sgi.com Sat Aug 20 10:59:52 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Aug 2005 10:59:54 -0700 (PDT) Received: from ylpvm43.prodigy.net (ylpvm43-ext.prodigy.net [207.115.57.74]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7KHxpH9010007 for ; Sat, 20 Aug 2005 10:59:51 -0700 Received: from pimout1-ext.prodigy.net (pimout1-int.prodigy.net [207.115.5.65]) by ylpvm43.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id j7KHve5t004072 for ; Sat, 20 Aug 2005 13:57:40 -0400 X-ORBL: [63.205.185.3] Received: from stupidest.org (adsl-63-205-185-3.dsl.snfc21.pacbell.net [63.205.185.3]) by pimout1-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id j7KHvVpT115046 for ; Sat, 20 Aug 2005 13:57:32 -0400 Received: by taniwha.stupidest.org (Postfix, from userid 38689) id 713E1528F22; Sat, 20 Aug 2005 10:57:30 -0700 (PDT) Date: Sat, 20 Aug 2005 10:57:30 -0700 From: Chris Wedgwood To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050820175730.GA8803@taniwha.stupidest.org> References: <20050820093341.GA15491@butterblume> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050820093341.GA15491@butterblume> X-archive-position: 5923 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs Content-Length: 857 Lines: 21 On Sat, Aug 20, 2005 at 11:33:41AM +0200, Markus Meyer wrote: > My Smartmontools reported a defect block on one of my disks with an > XFS on them. Details? > So I wanted to follow the Badblocks-Howto [1] to find the > corresponding Inode and the file that I can "repair" the block and > restore the file. But I have no idea how to accomplish this on XFS. If it's a small number of bad blocks and they are not increasing over time; you can stomp over them which in most cases will cause the drive to reallocate them (Reallocated_Sector_Ct) and then you can run xfs_repair to fix any filesystem nasties. Chances are though some of the errors are in data blocks. I have a perl script somewhere to find which file contain(s) a given blocks (basically xfs_bmap on all files for agiven volume and scan this). I'll have to see where I put it if you want it. From owner-linux-xfs@oss.sgi.com Sun Aug 21 15:45:47 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Aug 2005 15:45:54 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7LMjjH9004301 for ; Sun, 21 Aug 2005 15:45:46 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA22276; Mon, 22 Aug 2005 08:43:21 +1000 Received: from frodo.melbourne.sgi.com (root@frodo.melbourne.sgi.com [134.14.55.153]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7LMhUkt4170466; Mon, 22 Aug 2005 08:43:30 +1000 (EST) Received: from frodo.melbourne.sgi.com (nathans@localhost [127.0.0.1]) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) with ESMTP id j7LMZPQg000876; Mon, 22 Aug 2005 08:35:25 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id j7LMZNpP000874; Mon, 22 Aug 2005 08:35:23 +1000 Date: Mon, 22 Aug 2005 08:35:23 +1000 From: Nathan Scott To: "Tang Lingbo (Allan)" Cc: linux-xfs@oss.sgi.com Subject: Re: XFS report error on LVM snapshot Message-ID: <20050821223523.GA845@frodo> References: <003d01c59d62$70c59540$0209010a@winauth.cn.mvd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003d01c59d62$70c59540$0209010a@winauth.cn.mvd> User-Agent: Mutt/1.5.3i X-archive-position: 5928 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 778 Lines: 25 On Wed, Aug 10, 2005 at 12:17:24PM +0800, Tang Lingbo (Allan) wrote: > Hi, > > I get error message when I try to use LVM snapshot with XFS. > > === error message === > XFS mounting filesystem lvm(58,4) > Ending clean XFS mount for filesystem: lvm(58,4) > lvm - lvm_map: ll_rw_blk write for readonly LV /dev/vg0/test21 Could you put a call to the kernel dump_stack() routine where this printk is, and send the result? (looks like its a 2.4 kernel? and if so, looks like the printk is from drivers/md/lvm.c::lvm_map) > Could you give some idea to remove the messages? This should be easy to fix - looks like we have somewhere that its somehow possible to issue a write when we're mounted read-only ... we just need to find the offending piece of code. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Aug 21 15:59:08 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Aug 2005 15:59:11 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7LMx6H9005240 for ; Sun, 21 Aug 2005 15:59:07 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA22488 for ; Mon, 22 Aug 2005 08:56:45 +1000 Received: from frodo.melbourne.sgi.com (root@frodo.melbourne.sgi.com [134.14.55.153]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7LMuskt4173439 for ; Mon, 22 Aug 2005 08:56:55 +1000 (EST) Received: from frodo.melbourne.sgi.com (nathans@localhost [127.0.0.1]) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) with ESMTP id j7LMmoQg000972 for ; Mon, 22 Aug 2005 08:48:50 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id j7LMmnsZ000970 for linux-xfs@oss.sgi.com; Mon, 22 Aug 2005 08:48:49 +1000 Date: Mon, 22 Aug 2005 08:48:49 +1000 From: Nathan Scott To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050821224849.GB845@frodo> References: <20050820093341.GA15491@butterblume> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050820093341.GA15491@butterblume> User-Agent: Mutt/1.5.3i Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7LMx8H9005242 X-archive-position: 5929 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1539 Lines: 49 On Sat, Aug 20, 2005 at 11:33:41AM +0200, Markus Meyer wrote: > Hi folks, > > My Smartmontools reported a defect block on one of my disks with an XFS > on them. So I wanted to follow the Badblocks-Howto [1] to find the > corresponding Inode and the file that I can "repair" the block and > restore the file. But I have no idea how to accomplish this on XFS. > Is there anyone around who can help me? Well there aren't that many docs > around and the man pages are not a big help (or maybe I'm just blind). From a quick read of the howto you fwd'd (thanks, interesting), this is how that same information can be extracted for XFS - in this case I've started from filesystem block number 98319.. # xfs_db /dev/sdb5 xfs_db> blockget -b 98319 setting block 3/15 to symlink setting inode to 393291 for block 3/15 inode 393291 block 98319 at offset 0 xfs_db> blockget -i 393291 already have block usage information xfs_db> blockfree xfs_db> blockget -i 393291 inode 393291 add link, now 1 inode 393291 add link, now 2 inode 393291 mode 0120777 fmt extents afmt extents nex 1 anex 0 nblk 1 sz 319 inode 393291 nlink 2 not dir inode 393291 extent [0,98319,1,0] setting inode to 393291 for block 3/15 xfs_db> blockfree xfs_db> blockget -n xfs_db> ncheck -i 393291 393291 pd/d8/d15/d1a/l4a xfs_db> Oh, and initially you'll need to get from disk address (512 bytes) to a filesystem block number - use the convert command: xfs_db> convert fsb 98319 daddr 0x19020 (102432) xfs_db> convert daddr 102432 fsb 0x1800f (98319) cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Aug 22 04:08:14 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 04:08:22 -0700 (PDT) Received: from amail.email.aralion.co.kr (211-232-22-136.nexg.net [211.232.22.136] (may be forged)) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7MB8CH9012769; Mon, 22 Aug 2005 04:08:13 -0700 MIME-Version: 1.0 Subject: URG; need your support. plz Date: Mon, 22 Aug 2005 20:12:14 +0900 X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Message-ID: <82B6D98DE3D52D49AB9F043EFAFC50772C3260@amail.email.aralion.co.kr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: URG; need your support. plz Thread-Index: AcWnClmV7Wxs9dfiRXGyiFedI5PjPQ== X-Priority: 1 Priority: Urgent Importance: high From: =?ks_c_5601-1987?B?wMyx3byu?= To: , , Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5931 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: leekumseok@aralion.co.kr Precedence: bulk X-list: linux-xfs Content-Length: 3727 Lines: 84 Dear sgi xfs developer team. Need your definite judgment. plz Must conclude whether problem that I am such why happened. There is question. 1. Are you if is case that do xfs_repair automatically after system reboot if xfs internal error by i/o error happened? 2. Why does logical block address out of lange happen? 3. Is method that can recognize 1TB in kernel 2.4? Inform method and danger that do to correct and support more than 1TB i/o source in kernel. 4. When lun disk was realized as absurd, does xfs amend data guidance to look normally? Examine lower error log. Indicate problem. Kernel: 2.4.23-xfs HBA: LSI53C1030 SCSI device sdc: 4294950912 512-byte hdwr sectors (2199015 MB) XFS mounting filesystem lvm (LVM version 1.0.7) ------------------------/var/log/messages/------------------------------------- Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294950824 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294951144 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294951464 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294951784 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294952104 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294952424 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294952744 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294953064 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294953384 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294953704 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294954024 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294954344 Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294954664 ... Jul 19 21:52:20 SGNAS kernel: SCSI Error: (0:3:0) Status=02h (CHECK CONDITION) Jul 19 21:52:20 SGNAS kernel: Key=5h (ILLEGAL REQUEST); FRU=00h Jul 19 21:52:20 SGNAS kernel: ASC/ASCQ=21h/00h "" <------------- ASC Code 'logical block address out of range' Jul 19 21:52:20 SGNAS kernel: CDB: 2A 00 FF FF FF E0 00 01 40 00 Jul 19 21:52:20 SGNAS kernel: Jul 19 21:52:20 SGNAS kernel: I/O error: dev 08:21, sector 4294967232 Jul 19 21:52:45 SGNAS kernel: I/O error: dev 08:21, sector 4294958728 Jul 19 22:01:00 SGNAS CROND[9677]: (root) CMD (run-parts /etc/cron.hourly) Jul 19 22:33:47 SGNAS kernel: Filesystem "lvm(58,3)": XFS internal error xfs_btree_check_lblock at line 222 of file xfs_btree.c. Caller 0xc01ae3e3 Jul 19 22:33:47 SGNAS kernel: f7be98dc c01b150a c0339c67 00000001 f5041800 c0339c5b 000000de c01ae3e3 Jul 19 22:33:47 SGNAS kernel: c01b1fa6 f5041800 de7f3594 f75d0f20 ea1d15a0 00000000 00000008 00000000 Jul 19 22:33:47 SGNAS kernel: 00000000 de7f3594 f5041800 ea1d15a0 00000000 c01ae3e3 cce0cf10 e2156000 Jul 19 22:33:47 SGNAS kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Jul 19 22:33:47 SGNAS kernel: xfs_force_shutdown(lvm(58,3),0x8) called from line 1070 of file xfs_trans.c. Return address = 0xc02027bb Jul 19 22:33:47 SGNAS kernel: Filesystem "lvm(58,3)": Corruption of in-memory data detected. Shutting down filesystem: lvm(58,3) Jul 19 22:33:47 SGNAS kernel: Please umount the filesystem, and rectify the problem(s) Thanks your support. Have a nice day :-) Best regards, [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Mon Aug 22 05:47:35 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 05:47:40 -0700 (PDT) Received: from mail.butterblume.org ([193.151.7.122]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7MClYH9002675 for ; Mon, 22 Aug 2005 05:47:35 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.butterblume.org (Postfix) with ESMTP id 7C61C804F for ; Mon, 22 Aug 2005 14:45:06 +0200 (CEST) Received: from butterblume (xdsl-81-173-145-188.netcologne.de [81.173.145.188]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.butterblume.org (Postfix) with ESMTP id ECB747E9C for ; Mon, 22 Aug 2005 14:45:05 +0200 (CEST) Date: Mon, 22 Aug 2005 14:45:08 +0200 From: Markus Meyer To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050822124508.GC29623@butterblume> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050820093341.GA15491@butterblume> <20050821224849.GB845@frodo> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6zdv2QT/q3FMhpsV" Content-Disposition: inline In-Reply-To: <20050821224849.GB845@frodo> X-GPG-Fingerprint: B87120ED/A293 CEE1 43FB 22B2 F3F5 72D3 147D 6B31 B871 20ED User-Agent: mutt-ng/devel (Linux) X-archive-position: 5932 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mm@butterblume.org Precedence: bulk X-list: linux-xfs Content-Length: 1225 Lines: 44 --6zdv2QT/q3FMhpsV Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On [Mon, Aug 22 08:48], Nathan Scott wrote: >xfs_db> blockfree >xfs_db> blockget -n Thx at first. =46rom this point on the thing ran for nearly two hours so I quit it. This is nothing near a usable "solution". That's not against you. XFS is nice as long as it works. But then it gets really complicated. The programs interface is cryptic and the documentation is written in Geekish :) ASAP I'll switch back to EXT3.=20 >Oh, and initially you'll need to get from disk address (512 bytes) to >a filesystem block number - use the convert command: > >xfs_db> convert fsb 98319 daddr >0x19020 (102432) >xfs_db> convert daddr 102432 fsb >0x1800f (98319) OK, this I just can't wrap my head around. Sorry. Cheers, --=20 Markus Meyer - encrypted email preferred -> GPG: B87120ED --6zdv2QT/q3FMhpsV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCcjUFH1rMbhxIO0RAn87AKCqXKcd7/19vbY38+ZBCK9XGz7hiwCdF5X6 BCRR2RP7Uvu/ubgBNS7kUek= =A+YF -----END PGP SIGNATURE----- --6zdv2QT/q3FMhpsV-- From owner-linux-xfs@oss.sgi.com Mon Aug 22 14:11:06 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 14:11:12 -0700 (PDT) Received: from falconstorex.falconstor.com (host169.155.212.98.conversent.net [155.212.98.169]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7MLB6H9022769 for ; Mon, 22 Aug 2005 14:11:06 -0700 To: linux-xfs@oss.sgi.com Subject: XFS for ARM MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.0.1 February 07, 2003 From: Lan.Chen@falconstor.com Message-ID: Date: Mon, 22 Aug 2005 14:06:40 -0700 X-MIMETrack: Serialize by Router on FalconstorEX/FalconStor(Release 5.0.6a |January 17, 2001) at 08/22/2005 05:08:37 PM, Serialize complete at 08/22/2005 05:08:37 PM Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5934 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Lan.Chen@falconstor.com Precedence: bulk X-list: linux-xfs Content-Length: 449 Lines: 18 Hi, I need XFS for a Xcale based ARM platform(Inq80331). My target linux is Timesys which does not include any XFS code. By simply copying and cross-compiling the XFS from /usr/src/linux-2.4.21/fs, there are lots of problems. Timesys does not support things like SMP and spin_locks while XFS uses them extensively. If available, I wonder where I can find ported XFS for the ARM platform. Thanks. -Lan [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Mon Aug 22 14:26:58 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 14:27:09 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7MLQuH9024503 for ; Mon, 22 Aug 2005 14:26:57 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id HAA15198 for ; Tue, 23 Aug 2005 07:24:34 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7MLOhkt4196766 for ; Tue, 23 Aug 2005 07:24:44 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7MLOg3J4196892 for linux-xfs@oss.sgi.com; Tue, 23 Aug 2005 07:24:42 +1000 (EST) Date: Tue, 23 Aug 2005 07:24:41 +1000 From: Nathan Scott To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050823072441.A4197429@wobbly.melbourne.sgi.com> References: <20050820093341.GA15491@butterblume> <20050821224849.GB845@frodo> <20050822124508.GC29623@butterblume> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20050822124508.GC29623@butterblume>; from mm@butterblume.org on Mon, Aug 22, 2005 at 02:45:08PM +0200 X-archive-position: 5935 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1131 Lines: 41 On Mon, Aug 22, 2005 at 02:45:08PM +0200, Markus Meyer wrote: > On [Mon, Aug 22 08:48], Nathan Scott wrote: > >xfs_db> blockfree > >xfs_db> blockget -n > > Thx at first. > From this point on the thing ran for nearly two hours so I quit it. This This probably depends on filesystem size and number of inodes, for my test case on a relatively small filesystem it finished immediately. I guess, since your looking into this, you may also have bad blocks being remapped underneath the filesystem... and its possible thats increasing your run time too. > interface is cryptic and the documentation is written in Geekish :) Erm, any interfaces or docs in particular you didn't understand? > ASAP I'll switch back to EXT3. OK, whatever makes your boat float. > >Oh, and initially you'll need to get from disk address (512 bytes) to > >a filesystem block number - use the convert command: > > > >xfs_db> convert fsb 98319 daddr > >0x19020 (102432) > >xfs_db> convert daddr 102432 fsb > >0x1800f (98319) > > OK, this I just can't wrap my head around. Sorry. Its described further in the xfs_db(8) man page. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Aug 22 18:53:50 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 18:53:57 -0700 (PDT) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7N1rnH9019550 for ; Mon, 22 Aug 2005 18:53:49 -0700 Received: from saturn (c211-28-166-127.eburwd2.vic.optusnet.com.au [211.28.166.127]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j7N1pEIp001629; Tue, 23 Aug 2005 11:51:18 +1000 Received: from [192.168.1.54] (helo=kennedy.flamingspork.com) by saturn with esmtp (Exim 3.36 #1 (Debian)) id 1E7Osc-0002jG-00; Tue, 23 Aug 2005 12:51:14 +1000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by kennedy.flamingspork.com (Postfix) with ESMTP id 672E61C2005D; Tue, 23 Aug 2005 11:44:29 +1000 (EST) Subject: Re: XFS for ARM From: Stewart Smith To: Lan.Chen@falconstor.com Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-IvytjKF39lOqqmbW6C3u" Date: Tue, 23 Aug 2005 11:44:28 +1000 Message-Id: <1124761468.19951.186.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 X-archive-position: 5936 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stewart@flamingspork.com Precedence: bulk X-list: linux-xfs Content-Length: 1073 Lines: 34 --=-IvytjKF39lOqqmbW6C3u Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2005-08-22 at 14:06 -0700, Lan.Chen@falconstor.com wrote: > By simply copying and cross-compiling the XFS from=20 > /usr/src/linux-2.4.21/fs, there are lots of problems. > Timesys does not support things like SMP and spin_locks while XFS uses=20 > them extensively. your kernel should have implementations (null implementations maybe) of these calls. This is how a UP kernel is built instead of an SMP one. --=20 Stewart Smith (stewart@flamingspork.com) http://www.flamingspork.com/ --=-IvytjKF39lOqqmbW6C3u Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iQCVAwUAQwp/fIwDm44RooHBAQI7fgP+Ls8h4xbUeXBVQcN6pWC/hbtTJT+2uEmq mIPz79QNJTAJN9dcwy53PnQ3M10UGAaUr+E0LTIVj11nasgZ9CoelSDLmzpIvQrC paOwkCvF7a1GUv3/kN3oiavs+1nn7Jt7mCncc5oUK1w02G7hmb/4SXxiPvF48396 812oZrg9i2c= =0YP4 -----END PGP SIGNATURE----- --=-IvytjKF39lOqqmbW6C3u-- From owner-linux-xfs@oss.sgi.com Mon Aug 22 18:54:55 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 18:55:08 -0700 (PDT) Received: from burningspeed.com ([222.92.144.119]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7N1sqH9019691; Mon, 22 Aug 2005 18:54:54 -0700 Message-ID: <3CEBE754.6DD302F@burningspeed.com> Date: Mon, 22 Aug 2005 23:21:53 +0300 Reply-To: "toney colvin" From: "toney colvin" User-Agent: AspMail 3.0 X-Accept-Language: en-us MIME-Version: 1.0 To: "Asa Hovis" , , Subject: FW: Remarkable Locate the top-selliing medicinees at decreased prices at our PharrmaNet. beograd Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-archive-position: 5937 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: indoah@burningspeed.com Precedence: bulk X-list: linux-xfs Content-Length: 1005 Lines: 35 Be assured, with our premium quality generiics. We have a great aassortment on them. Privilege the finest geeneric meddicines on PhaarmaStore at the very 'privilege' prices for our privileged shopper and be privileged. http://uk.geocities.com/johnterminatefunny/?fnvxt With-us, all the ordeering process would be at ease & faster deeliveries. All the items are reduced. Check our site for this current special pricing. Select our site for a quick and professional case profile check. It is complimentary. I was wondering, how to loose flabbiness without hard work? The oral medication with the diets plan is really working for me. Within a few months, I've reduced 20 pounds. It's thrilling. Currently I am in perfect shape. Thank you for making my dream comes true. Shirlie West, CA How can anyone be so lonely Part of a success that never ends effemina flarlanghn agassiz q2 flastnam coverley I Can't Make Sense Of Whats Strolling By What You Gonna Do Yeah Maybe I Ain't So Shy From owner-linux-xfs@oss.sgi.com Mon Aug 22 22:28:34 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 22:28:40 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7N5SXH9009820 for ; Mon, 22 Aug 2005 22:28:34 -0700 Received: from spindle.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7N7P5Fe026081 for ; Tue, 23 Aug 2005 00:25:05 -0700 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by spindle.corp.sgi.com (SGI-8.12.5/8.12.9/generic_config-1.2) with ESMTP id j7N5P9sS85698914; Mon, 22 Aug 2005 22:25:09 -0700 (PDT) Message-ID: <430AB334.200@sgi.com> Date: Tue, 23 Aug 2005 00:25:08 -0500 From: Eric Sandeen User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?UTF-8?B?w4DDjMKxw53CvMKu?= CC: linux-xfs@oss.sgi.com Subject: Re: URG; need your support. plz References: <82B6D98DE3D52D49AB9F043EFAFC50772C3260@amail.email.aralion.co.kr> In-Reply-To: <82B6D98DE3D52D49AB9F043EFAFC50772C3260@amail.email.aralion.co.kr> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-archive-position: 5938 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 4177 Lines: 95 이금석 wrote: > Dear sgi xfs developer team. > > > Need your definite judgment. plz > Must conclude whether problem that I am such why happened. > > There is question. > > 1. Are you if is case that do xfs_repair automatically after system reboot if xfs internal error by i/o error happened? > > 2. Why does logical block address out of lange happen? > > 3. Is method that can recognize 1TB in kernel 2.4? > Inform method and danger that do to correct and support more than 1TB i/o source in kernel. In general, linux 2.4 kernels are not safe > 1T. It is highly dependent on whether the filesystem, vfs, IO layers, and lower level drivers are all 32-bit safe. > 4. When lun disk was realized as absurd, does xfs amend data guidance to look normally? Your best bet would probably be to run xfs_repair under a 2.6 kernel with CONFIG_LBD enabled. -Eric > > Examine lower error log. > > Indicate problem. > > > > Kernel: 2.4.23-xfs > > HBA: LSI53C1030 > > SCSI device sdc: 4294950912 512-byte hdwr sectors (2199015 MB) > > XFS mounting filesystem lvm (LVM version 1.0.7) > > ------------------------/var/log/messages/------------------------------------- > > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294950824 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294951144 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294951464 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294951784 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294952104 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294952424 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294952744 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294953064 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294953384 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294953704 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294954024 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294954344 > Jul 19 21:52:19 SGNAS kernel: I/O error: dev 08:21, sector 4294954664 > ... > > Jul 19 21:52:20 SGNAS kernel: SCSI Error: (0:3:0) Status=02h (CHECK CONDITION) > Jul 19 21:52:20 SGNAS kernel: Key=5h (ILLEGAL REQUEST); FRU=00h > Jul 19 21:52:20 SGNAS kernel: ASC/ASCQ=21h/00h "" <------------- ASC Code 'logical block address out of range' > Jul 19 21:52:20 SGNAS kernel: CDB: 2A 00 FF FF FF E0 00 01 40 00 > Jul 19 21:52:20 SGNAS kernel: > Jul 19 21:52:20 SGNAS kernel: I/O error: dev 08:21, sector 4294967232 > Jul 19 21:52:45 SGNAS kernel: I/O error: dev 08:21, sector 4294958728 > Jul 19 22:01:00 SGNAS CROND[9677]: (root) CMD (run-parts /etc/cron.hourly) > Jul 19 22:33:47 SGNAS kernel: Filesystem "lvm(58,3)": XFS internal error xfs_btree_check_lblock at line 222 of file xfs_btree.c. Caller 0xc01ae3e3 > Jul 19 22:33:47 SGNAS kernel: f7be98dc c01b150a c0339c67 00000001 f5041800 c0339c5b 000000de c01ae3e3 > Jul 19 22:33:47 SGNAS kernel: c01b1fa6 f5041800 de7f3594 f75d0f20 ea1d15a0 00000000 00000008 00000000 > Jul 19 22:33:47 SGNAS kernel: 00000000 de7f3594 f5041800 ea1d15a0 00000000 c01ae3e3 cce0cf10 e2156000 > Jul 19 22:33:47 SGNAS kernel: Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] > Jul 19 22:33:47 SGNAS kernel: xfs_force_shutdown(lvm(58,3),0x8) called from line 1070 of file xfs_trans.c. Return address = 0xc02027bb > Jul 19 22:33:47 SGNAS kernel: Filesystem "lvm(58,3)": Corruption of in-memory data detected. Shutting down filesystem: lvm(58,3) > Jul 19 22:33:47 SGNAS kernel: Please umount the filesystem, and rectify the problem(s) > > > > > > Thanks your support. > > > > Have a nice day :-) > > > > Best regards, > > > > [[HTML alternate version deleted]] > From owner-linux-xfs@oss.sgi.com Mon Aug 22 22:59:01 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 22:59:11 -0700 (PDT) Received: from mail.butterblume.org ([193.151.7.122]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7N5x0H9013234 for ; Mon, 22 Aug 2005 22:59:01 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.butterblume.org (Postfix) with ESMTP id 67B2C804F for ; Tue, 23 Aug 2005 07:56:37 +0200 (CEST) Received: from butterblume (xdsl-81-173-144-122.netcologne.de [81.173.144.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.butterblume.org (Postfix) with ESMTP id E7C157DFE for ; Tue, 23 Aug 2005 07:56:36 +0200 (CEST) Date: Tue, 23 Aug 2005 07:56:37 +0200 From: Markus Meyer To: linux-xfs@oss.sgi.com Subject: Re: Find file for inode Message-ID: <20050823055637.GA22266@butterblume> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050820093341.GA15491@butterblume> <20050821224849.GB845@frodo> <20050822124508.GC29623@butterblume> <20050823072441.A4197429@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC" Content-Disposition: inline In-Reply-To: <20050823072441.A4197429@wobbly.melbourne.sgi.com> X-GPG-Fingerprint: B87120ED/A293 CEE1 43FB 22B2 F3F5 72D3 147D 6B31 B871 20ED User-Agent: mutt-ng/devel (Linux) X-archive-position: 5939 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mm@butterblume.org Precedence: bulk X-list: linux-xfs Content-Length: 2096 Lines: 62 --wRRV7LY7NUeQGEoC Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On [Tue, Aug 23 07:24], Nathan Scott wrote: Hi Nathan, >I guess, since your looking into this, you may also have bad >blocks being remapped underneath the filesystem... and its >possible thats increasing your run time too. It's a 40GB ATA-5 disk... >Erm, any interfaces or docs in particular you didn't understand? I only use XFS on my home system and I don't want to study for two days to understand whats going on there. At work I have to do this everytime as a UNIX admin. At home I just want to be the "normal" user. But the=20 missing "transparency" in the XFS tools don't allow that. Setting up XFS is starightforward but as soon as you get block errors or other problems you run against a wall since the lack of "understandable" documentation and tools. >OK, whatever makes your boat float. Well, sorry for that. It's childish because I was _really_ tired when I wrote this. >Its described further in the xfs_db(8) man page. See above. It takes too much brain energy to understand it. I'm not that stupid but at home I'm really lazy and need tools and programs that just work or where I easily can understand the important parts. Since I needed the disk I zeroed it disk with "dd" to reallocate the=20 bad blocks, reformatted it and restored the data onto it. I'm still=20 using XFS on it. But I really wish that the tools get more transparent and the documentation would not sound like a technical study. Thx and cheers, --=20 Markus Meyer - encrypted email preferred -> GPG: B87120ED http://butterblume.org - JAB: butterbluemchen@amessage.de --- Was die neuen Unwissenden holen m=FCssen: Schl=FCssel zum Verf=FCgungsraum --wRRV7LY7NUeQGEoC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDCrqVFH1rMbhxIO0RAmfiAJ9qz3cd40mbnkICqfiqoFhFpvax8QCfRdP3 EZH9CH0wl+5+n2TIz4Bg3VA= =N46v -----END PGP SIGNATURE----- --wRRV7LY7NUeQGEoC-- From owner-linux-xfs@oss.sgi.com Mon Aug 22 23:00:18 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Aug 2005 23:00:23 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7N60GH9013768 for ; Mon, 22 Aug 2005 23:00:17 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA26633; Tue, 23 Aug 2005 15:57:51 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7N5vng87367499; Tue, 23 Aug 2005 15:57:49 +1000 (EST) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7N5vm9l7366619; Tue, 23 Aug 2005 15:57:48 +1000 (EST) Date: Tue, 23 Aug 2005 15:57:48 +1000 (EST) From: Timothy Shimmin Message-Id: <200508230557.j7N5vm9l7366619@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 940366 - panic in xfs_trans_brelse in quota code X-archive-position: 5940 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tes@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2101 Lines: 51 Please apply if you mount with quotas on XFS. This has been seen as a panic in xfs_trans_brelse() being called from xfs quota code. On a debug kernel, an assertion will fire off. It typically happens during a chown on a file - presumably to a userid which quotas have not seen before and causes a gap in the quota file to be filled. --- Fixes a bug in the quota code when allocating a new dquot record which can cause an extent hole to be filled and a free extent to be processed. In this case, we make a few mistakes: forget to pass back the transaction, forget to put a hold on the buffer and forget to add the buf to the new transaction. xfstests/118 reproduces the bug and tests the fix. --Tim Date: Tue Aug 23 15:47:26 AEST 2005 Workarea: snort.melbourne.sgi.com:/home/tes/isms/xfs-linux-test2 Inspected by: dgc@sgi.com The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:23594a xfs_trans.h - 1.131 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_trans.h.diff?r1=text&tr1=1.131&r2=text&tr2=1.130&f=h - create xfs_trans_bhold_release prototype. xfs_trans_buf.c - 1.121 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_trans_buf.c.diff?r1=text&tr1=1.121&r2=text&tr2=1.120&f=h - create xfs_trans_bhold_release. quota/xfs_dquot.c - 1.18 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/quota/xfs_dquot.c.diff?r1=text&tr1=1.18&r2=text&tr2=1.17&f=h - In allocation of quota records, if the bmap returns free extents then xfs_bmap_finish will create a new transaction to process them. We need to pass this transaction back, put a hold on the buffer and join the buffer to the new transaction. linux-2.6/xfs_ksyms.c - 1.26 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_ksyms.c.diff?r1=text&tr1=1.26&r2=text&tr2=1.25&f=h linux-2.4/xfs_ksyms.c - 1.22 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_ksyms.c.diff?r1=text&tr1=1.22&r2=text&tr2=1.21&f=h - Export 3 trans buffer functions needed by the quota code. From owner-linux-xfs@oss.sgi.com Tue Aug 23 00:44:54 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 00:44:59 -0700 (PDT) Received: from dedicated.mountainviewdata.com (207-234-129-26.ptr.primarydns.com [207.234.129.26]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7N7irH9029570 for ; Tue, 23 Aug 2005 00:44:53 -0700 Received: from allanlaptop (unknown [221.219.14.198]) by dedicated.mountainviewdata.com (Postfix) with ESMTP id D14119FDF4; Tue, 23 Aug 2005 00:37:03 -0700 (PDT) From: "Tang Lingbo (Allan)" To: "'Nathan Scott'" Cc: Subject: RE: XFS report error on LVM snapshot Date: Tue, 23 Aug 2005 15:41:55 +0800 Organization: Mountain View Data, Inc. Message-ID: <001001c5a7b6$28235da0$0209010a@winauth.cn.mvd> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: <20050821223523.GA845@frodo> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-yoursite-MailScanner-Information: Please contact the ISP for more information X-yoursite-MailScanner: Found to be clean X-archive-position: 5941 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: allan@mountainviewdata.com Precedence: bulk X-list: linux-xfs Content-Length: 670 Lines: 23 Hi Nathan, > > I get error message when I try to use LVM snapshot with XFS. > > > > === error message === > > XFS mounting filesystem lvm(58,4) > > Ending clean XFS mount for filesystem: lvm(58,4) > > lvm - lvm_map: ll_rw_blk write for readonly LV /dev/vg0/test21 > > Could you put a call to the kernel dump_stack() routine where this > printk is, and send the result? (looks like its a 2.4 kernel? and > if so, looks like the printk is from drivers/md/lvm.c::lvm_map) > The kernel is built by "kernel-2.4.21-27.0.2.EL.sgi9.src.rpm" which is downloaded from sgi website. I will try to do the test as you said. Please hold on for a while. Thanks! Regards, Allan From owner-linux-xfs@oss.sgi.com Tue Aug 23 02:26:52 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 02:26:56 -0700 (PDT) Received: from war.OCF.Berkeley.EDU (war.OCF.Berkeley.EDU [192.58.221.244]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7N9QqH9006864 for ; Tue, 23 Aug 2005 02:26:52 -0700 Received: from conquest.OCF.Berkeley.EDU (IDENT:1@conquest.OCF.Berkeley.EDU [192.58.221.248]) by war.OCF.Berkeley.EDU (8.13.4/8.9.3) with ESMTP id j7N9OSOb004893 for ; Tue, 23 Aug 2005 02:24:29 -0700 (PDT) (envelope-from ihaque@OCF.Berkeley.EDU) Received: from localhost (ihaque@localhost) by conquest.OCF.Berkeley.EDU (8.11.7/8.11.7) with ESMTP id j7N9OSt25133 for ; Tue, 23 Aug 2005 02:24:28 -0700 (PDT) X-Authentication-Warning: conquest.OCF.Berkeley.EDU: ihaque owned process doing -bs Date: Tue, 23 Aug 2005 02:24:28 -0700 (PDT) From: Imran Saeedul Haque To: linux-xfs@oss.sgi.com Subject: XFS/NFS incompatibility Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5942 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ihaque@OCF.Berkeley.EDU Precedence: bulk X-list: linux-xfs Content-Length: 722 Lines: 17 xfs version 2.6.25 (as reported by mkfs.xfs); kernel 2.6.11-gentoo-r4. I am unable to mount over NFS any exported XFS file systems. Trying to do so gives me: "mount: [mount location] failed, reason given by server: Permission denied" with [mount location] of course referring to the export. This happens over many different export locations. As a test, I created a 256M loopback filesystem, and exported it, keeping it, the directory could be remote-mounted fine. With an XFS filesystem, I get the permission denied error; the mount works fine if the loopback contains a ReiserFS or ext2 filesystem. The filesystems are exported rw; I've tried using both nohide and no_subtree_check, to no avail. Suggestions? From owner-linux-xfs@oss.sgi.com Tue Aug 23 02:45:48 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 02:46:01 -0700 (PDT) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7N9jmH9008798 for ; Tue, 23 Aug 2005 02:45:48 -0700 Received: from hch by pentafluge.infradead.org with local (Exim 4.52 #1 (Red Hat Linux)) id 1E7VJX-00018x-2z; Tue, 23 Aug 2005 10:43:27 +0100 Date: Tue, 23 Aug 2005 10:43:27 +0100 From: Christoph Hellwig To: Lan.Chen@falconstor.com Cc: linux-xfs@oss.sgi.com Subject: Re: XFS for ARM Message-ID: <20050823094326.GA4129@infradead.org> References: 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-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html X-archive-position: 5943 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Content-Length: 499 Lines: 14 On Mon, Aug 22, 2005 at 02:06:40PM -0700, Lan.Chen@falconstor.com wrote: > Hi, > > I need XFS for a Xcale based ARM platform(Inq80331). > My target linux is Timesys which does not include any XFS code. Your problem. If you use the broken mes timesys ships complain to them. XFS works just fine with recent linux 2.6.x on all platforms, including arm. > If available, I wonder where I can find ported XFS for the ARM platform. http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.tar.bz2 From owner-linux-xfs@oss.sgi.com Tue Aug 23 03:00:49 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 03:00:54 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7NA0lH9010597 for ; Tue, 23 Aug 2005 03:00:48 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA01284; Tue, 23 Aug 2005 19:58:19 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7N9wSkt4211734; Tue, 23 Aug 2005 19:58:29 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7N9wQkv4208795; Tue, 23 Aug 2005 19:58:26 +1000 (EST) Date: Tue, 23 Aug 2005 19:58:26 +1000 From: Nathan Scott To: Imran Saeedul Haque Cc: linux-xfs@oss.sgi.com Subject: Re: XFS/NFS incompatibility Message-ID: <20050823195826.A4211296@wobbly.melbourne.sgi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from ihaque@OCF.Berkeley.EDU on Tue, Aug 23, 2005 at 02:24:28AM -0700 X-archive-position: 5944 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 423 Lines: 16 On Tue, Aug 23, 2005 at 02:24:28AM -0700, Imran Saeedul Haque wrote: > xfs version 2.6.25 (as reported by mkfs.xfs); kernel 2.6.11-gentoo-r4. > > I am unable to mount over NFS any exported XFS file systems. Trying to do > so gives me: > "mount: [mount location] failed, reason given by server: Permission denied" > ... > Suggestions? Does this happen on mainline (kernel.org, not gentoo) kernels? cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Aug 23 04:36:50 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 04:36:54 -0700 (PDT) Received: from soloth.lewis.org (soloth.lewis.org [69.28.69.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7NBanH9024741 for ; Tue, 23 Aug 2005 04:36:49 -0700 Received: from soloth.lewis.org (localhost.localdomain [127.0.0.1]) by soloth.lewis.org (8.12.11/8.12.11) with ESMTP id j7NBYS0B016639; Tue, 23 Aug 2005 07:34:28 -0400 Received: from localhost (jlewis@localhost) by soloth.lewis.org (8.12.11/8.12.11/Submit) with ESMTP id j7NBYRsZ016635; Tue, 23 Aug 2005 07:34:27 -0400 X-Authentication-Warning: soloth.lewis.org: jlewis owned process doing -bs Date: Tue, 23 Aug 2005 07:34:27 -0400 (EDT) From: Jon Lewis To: Nathan Scott cc: linux-xfs@oss.sgi.com Subject: Re: XFS/NFS incompatibility In-Reply-To: <20050823195826.A4211296@wobbly.melbourne.sgi.com> Message-ID: References: <20050823195826.A4211296@wobbly.melbourne.sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5945 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlewis@lewis.org Precedence: bulk X-list: linux-xfs Content-Length: 1029 Lines: 26 On Tue, 23 Aug 2005, Nathan Scott wrote: > On Tue, Aug 23, 2005 at 02:24:28AM -0700, Imran Saeedul Haque wrote: >> xfs version 2.6.25 (as reported by mkfs.xfs); kernel 2.6.11-gentoo-r4. >> >> I am unable to mount over NFS any exported XFS file systems. Trying to do >> so gives me: >> "mount: [mount location] failed, reason given by server: Permission denied" >> ... >> Suggestions? > > Does this happen on mainline (kernel.org, not gentoo) kernels? I posted about a week ago that SGI's 2.4.31-xfscvs20050617 is also totally unusable as an NFS server (exporting XFS), though the failure mode is slightly different. Mount's succeed. File access by clients fail. I suspect there's been some common bug introduced into both the 2.4 and 2.6 XFS drivers. ---------------------------------------------------------------------- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ From owner-linux-xfs@oss.sgi.com Tue Aug 23 04:40:56 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 04:41:01 -0700 (PDT) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7NBetH9025452 for ; Tue, 23 Aug 2005 04:40:56 -0700 Received: from hch by pentafluge.infradead.org with local (Exim 4.52 #1 (Red Hat Linux)) id 1E7X6u-0001bb-IJ; Tue, 23 Aug 2005 12:38:32 +0100 Date: Tue, 23 Aug 2005 12:38:32 +0100 From: Christoph Hellwig To: Imran Saeedul Haque Cc: linux-xfs@oss.sgi.com Subject: Re: XFS/NFS incompatibility Message-ID: <20050823113832.GA6157@infradead.org> References: 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-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html X-archive-position: 5946 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Content-Length: 1227 Lines: 23 On Tue, Aug 23, 2005 at 02:24:28AM -0700, Imran Saeedul Haque wrote: > xfs version 2.6.25 (as reported by mkfs.xfs); kernel 2.6.11-gentoo-r4. > > I am unable to mount over NFS any exported XFS file systems. Trying to do > so gives me: > "mount: [mount location] failed, reason given by server: Permission denied" > > with [mount location] of course referring to the export. This happens over > many different export locations. > > As a test, I created a 256M loopback filesystem, and exported it, keeping > it, the directory could be remote-mounted fine. With an XFS filesystem, I > get the permission denied error; the mount works fine if the loopback > contains a ReiserFS or ext2 filesystem. The filesystems are exported rw; > I've tried using both nohide and no_subtree_check, to no avail. I've been doing lots of nfs testing on 2.6.12 + oss.sgi.com CVS and current 2.6.13-rc TOT the last days and it works just fine. Did you try exporting a real partitions instead of a loopback blockdevice? While I don't know what problems a loop device could cause this is on of the odd things in your setup. The other is of course an odd gentoo build, but I don't know how even gentoo folks could mess up nfs exporting. From owner-linux-xfs@oss.sgi.com Tue Aug 23 11:03:03 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 11:03:09 -0700 (PDT) Received: from calmail-fe1.berkeley.edu (mailfarm.Berkeley.EDU [128.32.61.106]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7NI33H9031316 for ; Tue, 23 Aug 2005 11:03:03 -0700 Received: from [66.87.74.129] (account ihaque@calmail.berkeley.edu HELO [192.168.0.6]) by calmail-fe1.berkeley.edu (CommuniGate Pro SMTP 4.2.6) with ESMTP-TLS id 133270660; Tue, 23 Aug 2005 11:00:39 -0700 Message-ID: <430B6441.8090807@ocf.berkeley.edu> Date: Tue, 23 Aug 2005 11:00:33 -0700 From: Imran Haque User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nathan Scott CC: linux-xfs@oss.sgi.com Subject: Re: XFS/NFS incompatibility References: <20050823195826.A4211296@wobbly.melbourne.sgi.com> In-Reply-To: <20050823195826.A4211296@wobbly.melbourne.sgi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5947 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ihaque@ocf.berkeley.edu Precedence: bulk X-list: linux-xfs Content-Length: 411 Lines: 12 Nathan Scott wrote: > Does this happen on mainline (kernel.org, not gentoo) kernels? > > cheers. > It seemed to work alright in the mainline kernels. Oddly enough, after running the mainline kernels...it started working in the gentoo kernel as well. (And yes, I had tried rebooting the gentoo kernels last night; didn't do anything). The NFS configuration didn't change either. Curiouser and curiouser. From owner-linux-xfs@oss.sgi.com Tue Aug 23 14:00:12 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 14:00:16 -0700 (PDT) Received: from mail.g-house.de (ns2.g-housing.de [81.169.133.75]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7NL0BH9020032 for ; Tue, 23 Aug 2005 14:00:12 -0700 Received: from g0f23.g.pppool.de ([80.185.15.35] helo=mail.housecafe.de) by mail.g-house.de with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1E7frG-0003cC-8C; Tue, 23 Aug 2005 22:58:58 +0200 Received: from prinz64.housecafe.de ([192.168.10.11]) by mail.housecafe.de with esmtp (Exim 4.52) id 1E7fq0-00034X-8P; Tue, 23 Aug 2005 22:57:40 +0200 Message-ID: <430B8DC3.2090105@gmx.net> Date: Tue, 23 Aug 2005 22:57:39 +0200 From: _evil User-Agent: Mozilla Thunderbird 1.0+ (Windows/20050721) MIME-Version: 1.0 To: linux-xfs@oss.sgi.com CC: Imran Saeedul Haque Subject: Re: XFS/NFS incompatibility References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5948 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 436 Lines: 13 Imran Saeedul Haque schrieb: > xfs version 2.6.25 (as reported by mkfs.xfs); kernel 2.6.11-gentoo-r4. > > I am unable to mount over NFS any exported XFS file systems. Trying to > do so gives me: > "mount: [mount location] failed, reason given by server: Permission denied" what gives you the impression, that this is related to XFS? are you exporting directories on other filesystems too? if not, can you try? thanks, Christian. From owner-linux-xfs@oss.sgi.com Tue Aug 23 22:44:48 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 22:44:56 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7O5ikH9010541 for ; Tue, 23 Aug 2005 22:44:47 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA25252; Wed, 24 Aug 2005 15:42:22 +1000 Received: from frodo.melbourne.sgi.com (root@frodo.melbourne.sgi.com [134.14.55.153]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7O5gUkt4232430; Wed, 24 Aug 2005 15:42:31 +1000 (EST) Received: from frodo.melbourne.sgi.com (nathans@localhost [127.0.0.1]) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) with ESMTP id j7O5YKoT001868; Wed, 24 Aug 2005 15:34:20 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id j7O5YJfA001866; Wed, 24 Aug 2005 15:34:19 +1000 Date: Wed, 24 Aug 2005 15:34:19 +1000 From: Nathan Scott To: Craig Rodrigues Cc: linux-xfs@oss.sgi.com Subject: Re: Use "const char *name" in extattr functions? Message-ID: <20050824053418.GC1553@frodo> References: <20050816011626.GA23116@crodrigues.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050816011626.GA23116@crodrigues.org> User-Agent: Mutt/1.5.3i X-archive-position: 5949 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1234 Lines: 33 Hi Craig, On Mon, Aug 15, 2005 at 09:16:26PM -0400, Craig Rodrigues wrote: > GCC gave me some problems when I tried passing "const char *" to > functions which took "char *" parameters for the attribute name. With your patch gcc is still giving me problems, and it needed a fair bit of tweaking just to get it to compile on Linux. There was some issue because this... > typedef struct xfs_da_args { > - uchar_t *name; /* string (maybe not NULL terminated) */ > + const uchar_t *name; /* string (maybe not NULL terminated) */ > int namelen; /* length of string (maybe no NULL) */ > uchar_t *value; /* set of bytes (maybe contain NULLs) */ > int valuelen; /* length of value */ meant assignments to args.name in attr get/set/remove produced compiler warnings which I just couldn't shake for some (still unknown) reason... In the end, I gave it up as a waste of time :) - I suggest you either cast it to (char *) in the high level platform-specific wrappers around the core XFS ext attr code (as is already done for linux-2.6/xfs_iops.c actually). If you really want to go with your patch, please make it compile on Linux with a recent gcc, without warnings (of course!), and resend... thanks. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Aug 23 22:55:06 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 22:55:13 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7O5t6H9011730 for ; Tue, 23 Aug 2005 22:55:06 -0700 Received: from internal-mail-relay.corp.sgi.com (internal-mail-relay.corp.sgi.com [198.149.32.51]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7O5qixT014843 for ; Wed, 24 Aug 2005 00:52:44 -0500 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by internal-mail-relay.corp.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7O5qi2Z261338759 for ; Tue, 23 Aug 2005 22:52:44 -0700 (PDT) X-ASG-Debug-ID: 1124862762-27115-41-6 X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by cuda.sgi.com (Spam Firewall) with ESMTP id B7809D018283 for ; Tue, 23 Aug 2005 22:52:43 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j7MC4k74027900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2005 07:04:47 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j7MC4jU7027899; Mon, 22 Aug 2005 07:04:45 -0500 Date: Mon, 22 Aug 2005 07:04:45 -0500 From: Christoph Hellwig Message-Id: <200508221204.j7MC4jU7027899@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com Cc: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com X-ASG-Orig-Subj: TAKE 934766 - remove some dead code from pagebuf Subject: TAKE 934766 - remove some dead code from pagebuf X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.3440 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 5951 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@relay.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 558 Lines: 15 Date: Mon Aug 22 05:04:32 PDT 2005 Workarea: naboo.americas.sgi.com:/go/space/hch/xfs-2.6.x Inspected by: nathans The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:197783a fs/xfs/linux-2.6/xfs_buf.h - 1.104 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_buf.h.diff?r1=text&tr1=1.104&r2=text&tr2=1.103&f=h fs/xfs/linux-2.6/xfs_buf.c - 1.200 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_buf.c.diff?r1=text&tr1=1.200&r2=text&tr2=1.199&f=h From owner-linux-xfs@oss.sgi.com Tue Aug 23 22:55:06 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 22:55:11 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7O5t5H9011725 for ; Tue, 23 Aug 2005 22:55:06 -0700 Received: from hastur.corp.sgi.com (hastur.corp.sgi.com [198.149.32.33]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7O5qixT014840 for ; Wed, 24 Aug 2005 00:52:44 -0500 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by hastur.corp.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7O5qMeS186319874 for ; Tue, 23 Aug 2005 22:52:22 -0700 (PDT) X-ASG-Debug-ID: 1124862762-27115-41-4 X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by cuda.sgi.com (Spam Firewall) with ESMTP id 144EDD01816A for ; Tue, 23 Aug 2005 22:52:43 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j7O5afQa011358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 24 Aug 2005 00:36:42 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j7O5adK9011354; Wed, 24 Aug 2005 00:36:39 -0500 Date: Wed, 24 Aug 2005 00:36:39 -0500 From: Christoph Hellwig Message-Id: <200508240536.j7O5adK9011354@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com X-ASG-Orig-Subj: TAKE 941429 - Retry linux inode cacech lookup if we found a stale inode Subject: TAKE 941429 - Retry linux inode cacech lookup if we found a stale inode X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.3440 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 5950 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@relay.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 418 Lines: 15 This fixes crashes under high nfs load Date: Tue Aug 23 22:35:11 PDT 2005 Workarea: naboo.americas.sgi.com:/go/space/hch/xfs-2.6.x Inspected by: dgc The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:197929a fs/xfs/xfs_iget.c - 1.205 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iget.c.diff?r1=text&tr1=1.205&r2=text&tr2=1.204&f=h From owner-linux-xfs@oss.sgi.com Tue Aug 23 22:55:06 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 22:55:15 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7O5t6H9011733 for ; Tue, 23 Aug 2005 22:55:06 -0700 Received: from hastur.corp.sgi.com (hastur.corp.sgi.com [198.149.32.33]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7O5qixT014848 for ; Wed, 24 Aug 2005 00:52:44 -0500 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by hastur.corp.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7O5qNeS186341221 for ; Tue, 23 Aug 2005 22:52:23 -0700 (PDT) X-ASG-Debug-ID: 1124862762-27115-41-8 X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by cuda.sgi.com (Spam Firewall) with ESMTP id 1DD39D018269 for ; Tue, 23 Aug 2005 22:52:44 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j7MBhXXv005831 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 Aug 2005 06:43:35 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j7MBhVwI005824; Mon, 22 Aug 2005 06:43:31 -0500 Date: Mon, 22 Aug 2005 06:43:31 -0500 From: Christoph Hellwig Message-Id: <200508221143.j7MBhVwI005824@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com X-ASG-Orig-Subj: TAKE 940531 - allow a null behaviour pointer in linvfs_clear_inode Subject: TAKE 940531 - allow a null behaviour pointer in linvfs_clear_inode X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.3440 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 5952 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@relay.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 566 Lines: 15 Date: Mon Aug 22 04:43:22 PDT 2005 Workarea: naboo.americas.sgi.com:/go/space/hch/xfs-2.4.x Inspected by: sandeen The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.4.x-xfs Modid: xfs-linux:xfs-kern:197782a fs/xfs/linux-2.6/xfs_super.c - 1.340 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_super.c.diff?r1=text&tr1=1.340&r2=text&tr2=1.339&f=h fs/xfs/linux-2.4/xfs_super.c - 1.311 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_super.c.diff?r1=text&tr1=1.311&r2=text&tr2=1.310&f=h From owner-linux-xfs@oss.sgi.com Tue Aug 23 23:25:49 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 23:25:51 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7O6PliL015841 for ; Tue, 23 Aug 2005 23:25:48 -0700 Received: from chook.melbourne.sgi.com (chook.melbourne.sgi.com [134.14.54.237]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA26257; Wed, 24 Aug 2005 16:23:20 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16346) id A8CF049B49F3; Wed, 24 Aug 2005 16:23:19 +1000 (EST) To: linux-xfs@oss.sgi.com Cc: sgi.bugs.xfs@engr.sgi.com Subject: TAKE 923981 - pb_flags access is racy Message-Id: <20050824062319.A8CF049B49F3@chook.melbourne.sgi.com> Date: Wed, 24 Aug 2005 16:23:19 +1000 (EST) From: dgc@sgi.com (David Chinner) X-archive-position: 5953 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1931 Lines: 45 Fix racy access to pb_flags. pagebuf_rele() modified pb_flags after the pagebuf had been unlocked if the buffer was delwri. At high load, this could result in a race when the superblock was being synced that would result the flags being incorrect and the iodone functions being executed incorrectly. This then leads to iclog callback failures or AIL list corruptions resulting in filesystem shutdowns. Date: Wed Aug 24 16:22:21 AEST 2005 Workarea: chook.melbourne.sgi.com:/build/dgc/isms/xfs-linux Inspected by: nathans,hch The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:23616a xfsidbg.c - 1.280 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfsidbg.c.diff?r1=text&tr1=1.280&r2=text&tr2=1.279&f=h - Add _PBF_DELWRI_Q flag to kdb pagebuf output. linux-2.6/xfs_buf.h - 1.105 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_buf.h.diff?r1=text&tr1=1.105&r2=text&tr2=1.104&f=h - Add _PBF_DELWRI_Q flag. linux-2.6/xfs_buf.c - 1.201 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_buf.c.diff?r1=text&tr1=1.201&r2=text&tr2=1.200&f=h - Move delwri buffer processing to before the buffer is unlocked so flags are modified while the buffer is still locked. Also use a flag to keep track of whether we are already in the delwri queue. linux-2.4/xfs_buf.h - 1.110 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_buf.h.diff?r1=text&tr1=1.110&r2=text&tr2=1.109&f=h - Add _PBF_DELWRI_Q flag. linux-2.4/xfs_buf.c - 1.207 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.4/xfs_buf.c.diff?r1=text&tr1=1.207&r2=text&tr2=1.206&f=h - Move delwri buffer processing to before the buffer is unlocked so flags are modified while the buffer is still locked. Also use a flag to keep track of whether we are already in the delwri queue. From owner-linux-xfs@oss.sgi.com Tue Aug 23 23:43:47 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Aug 2005 23:43:50 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7O6hjiL017759 for ; Tue, 23 Aug 2005 23:43:46 -0700 Received: from chook.melbourne.sgi.com (chook.melbourne.sgi.com [134.14.54.237]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA26640; Wed, 24 Aug 2005 16:41:19 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16346) id 0CAC149B49F3; Wed, 24 Aug 2005 16:41:19 +1000 (EST) To: linux-xfs@oss.sgi.com Cc: sgi.bugs.xfs@engr.sgi.com Subject: TAKE 941651 - fix up kdb xfs pagebuf tracing functions Message-Id: <20050824064119.0CAC149B49F3@chook.melbourne.sgi.com> Date: Wed, 24 Aug 2005 16:41:19 +1000 (EST) From: dgc@sgi.com (David Chinner) X-archive-position: 5954 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 578 Lines: 19 Fix various kdb pagebuf tracing options that are currently broken. Date: Wed Aug 24 16:40:31 AEST 2005 Workarea: chook.melbourne.sgi.com:/build/dgc/isms/xfs-linux Inspected by: nathans The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:23617a xfsidbg.c - 1.281 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfsidbg.c.diff?r1=text&tr1=1.281&r2=text&tr2=1.280&f=h - prevent infinite loops when tracing specific pagebufs or offsets and allow pagebuf tracing at offset zero. From owner-linux-xfs@oss.sgi.com Wed Aug 24 00:23:45 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Aug 2005 00:23:53 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7O7NjiL027235 for ; Wed, 24 Aug 2005 00:23:45 -0700 Received: from hastur.corp.sgi.com (hastur.corp.sgi.com [198.149.32.33]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7O9KR47012172 for ; Wed, 24 Aug 2005 02:20:27 -0700 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by hastur.corp.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7O7L0eS186293773 for ; Wed, 24 Aug 2005 00:21:00 -0700 (PDT) X-ASG-Debug-ID: 1124868082-32539-26-0 X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by cuda.sgi.com (Spam Firewall) with ESMTP id 743B8D01942A for ; Wed, 24 Aug 2005 00:21:23 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j7O7LLcI022679; Wed, 24 Aug 2005 02:21:21 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j7O7LJSd022675; Wed, 24 Aug 2005 02:21:19 -0500 Date: Wed, 24 Aug 2005 02:21:19 -0500 From: Christoph Hellwig Message-Id: <200508240721.j7O7LJSd022675@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com X-ASG-Orig-Subj: TAKE 941429 - use delay(), msleep() doesn't exist on 2.4.x Subject: TAKE 941429 - use delay(), msleep() doesn't exist on 2.4.x X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.3441 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 5955 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@relay.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 378 Lines: 13 Date: Wed Aug 24 00:21:10 PDT 2005 Workarea: naboo.americas.sgi.com:/go/space/hch/xfs-2.6.x Inspected by: dgc The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:197934a fs/xfs/xfs_iget.c - 1.206 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iget.c.diff?r1=text&tr1=1.206&r2=text&tr2=1.205&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 24 09:10:20 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Aug 2005 09:10:26 -0700 (PDT) Received: from aaa.dreamhost.com (aaa.dreamhost.com [64.111.107.16]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7OGAKiL020664 for ; Wed, 24 Aug 2005 09:10:20 -0700 Received: from [192.168.1.60] (66-117-129-57.dsl.lmi.net [66.117.129.57]) by aaa.dreamhost.com (Postfix) with ESMTP id 22AA814F20 for ; Wed, 24 Aug 2005 09:07:54 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v733) To: linux-xfs@oss.sgi.com Message-Id: From: asa hammond Subject: FS internal error xfs_da_do_buf(2) at line 2273 of file fs/xfs/xfs_da_btree.c. Date: Wed, 24 Aug 2005 09:07:52 -0700 X-Mailer: Apple Mail (2.733) Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5956 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: asa@assembleco.com Precedence: bulk X-list: linux-xfs Content-Length: 4076 Lines: 153 I am having an unfortunate day and last night. dmesg gives me: XFS mounting filesystem sda6 Ending clean XFS mount for filesystem: sda6 0x0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Filesystem "sda6": XFS internal error xfs_da_do_buf(2) at line 2273 of file fs/xfs/xfs_da_btree.c. Caller 0xf9bcf522 Call Trace: [] xfs_da_do_buf+0x5ee/0x900 [xfs] [] xfs_da_read_buf+0x42/0x50 [xfs] [] xfs_da_read_buf+0x42/0x50 [xfs] [] journal_mark_dirty+0x116/0x260 [reiserfs] [] xfs_da_read_buf+0x42/0x50 [xfs] [] xfs_dir2_block_getdents+0x9f/0x2e0 [xfs] [] xfs_dir2_block_getdents+0x9f/0x2e0 [xfs] [] __alloc_pages+0xad/0x310 [] xfs_bmap_last_offset+0x122/0x140 [xfs] [] xfs_dir2_isblock+0x1a/0x70 [xfs] [] xfs_dir2_getdents+0xc9/0x150 [xfs] [] xfs_dir2_put_dirent64_direct+0x0/0xb0 [xfs] [] xfs_dir2_put_dirent64_direct+0x0/0xb0 [xfs] [] xfs_readdir+0x58/0xb0 [xfs] [] linvfs_getattr+0x0/0x40 [xfs] [] linvfs_readdir+0x100/0x206 [xfs] [] filldir64+0x0/0x150 [] vfs_readdir+0x95/0xc0 [] filldir64+0x0/0x150 [] sys_getdents64+0xa3/0x150 [] sysenter_past_esp+0x52/0x79 xfs_repair cannot find a correct primary or secondary superblock. if I print the raw superblock I get the following: manga:~ # xfs_db /dev/sda6 xfs_db> sb 0 xfs_db> p magicnum = 0x58465342 blocksize = 4096 dblocks = 74537575 rblocks = 0 rextents = 0 uuid = 15b4a8d0-9161-4b3c-9419-5151cacd715c logstart = 37748740 rootino = 128 rbmino = 129 rsumino = 130 rextsize = 16 agblocks = 1048576 agcount = 72 rbmblocks = 0 logblocks = 8192 versionnum = 0x2094 sectsize = 512 inodesize = 256 inopblock = 16 fname = "\000\000\000\000\000\000\000\000\000\000\000\000" blocklog = 12 sectlog = 9 inodelog = 8 inopblog = 4 agblklog = 20 rextslog = 0 inprogress = 0 imax_pct = 25 icount = 466816 ifree = 49645 fdblocks = 5154603 frextents = 0 uquotino = 0 gquotino = 0 qflags = 0 flags = 0 shared_vn = 0 inoalignmt = 2 unit = 0 width = 0 dirblklog = 0 logsectlog = 0 logsectsize = 0 logsunit = 0 features2 = 0 the particulars: Suse enterprise server 9 dell poweredge 2850 I have a large 360 gig raid 5 array broken into several partitions. dev/sda1 * 1 5 40131 de Dell Utility /dev/sda2 6 129 996030 82 Linux swap /dev/sda3 130 4992 39062047+ 83 Linux /dev/sda4 4993 44542 317685375 5 Extended /dev/sda5 4993 7424 19535008+ 83 Linux /dev/sda6 7425 44542 298150303+ 83 Linux sda5 and sda6 are both xfs mounts so my sda5 filesystem went corrupt somehow. I backed up all the data and using yast partition manager, deleted the partition. now what used to be sda6 looks like sda5 to the partition manager something like the following table /dev/sda5 7425 44542 298150303+ 83 Linux so I added a new partition to replace the one I deleted, /dev/sda6 4993 7424 19535008+ 83 Linux and set the type to reiserfs. and quit yast partition manager. I was given errors about unable to modify partition sda6 etc... I may not have unmounted sda6 correctly before modding partition table. bad me. So I reopen YAST partition manager and now there is only /dev/sda5 which mysteriously starts at 4993 and ends 44542. OK so that is a bit weird/disconcerting. but when I fdisk the partition table my old partitions are still there. I fear that yast may have written some part of reiser into sda6 which it thought was sda5 at the time. argh. I have fixed the order of the partitions and I feel like I have them back to normal(I deleted them all and reentered them into fdisk) I have tried gpart, it wrote a very wrong partition table. Anyone have any advice? Thank you. Asa Assemble p.510.524.8255 f.510.295.2710 742 Gilman St, Berkeley CA 94710-1327 [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Wed Aug 24 20:48:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Aug 2005 20:49:09 -0700 (PDT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7P3mwiL031853 for ; Wed, 24 Aug 2005 20:48:59 -0700 Received: from c-66-30-115-133.hsd1.ma.comcast.net ([66.30.115.133]) by comcast.net (sccrmhc12) with ESMTP id <200508250346340120008anue>; Thu, 25 Aug 2005 03:46:34 +0000 Received: from c-66-30-115-133.hsd1.ma.comcast.net (localhost.127.in-addr.arpa [127.0.0.1]) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1) with ESMTP id j7P3kXOe001691; Wed, 24 Aug 2005 23:46:33 -0400 (EDT) (envelope-from rodrigc@c-66-30-115-133.hsd1.ma.comcast.net) Received: (from rodrigc@localhost) by c-66-30-115-133.hsd1.ma.comcast.net (8.13.4/8.13.1/Submit) id j7P3kXQZ001690; Wed, 24 Aug 2005 23:46:33 -0400 (EDT) (envelope-from rodrigc) Date: Wed, 24 Aug 2005 23:46:28 -0400 From: Craig Rodrigues To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: Use "const char *name" in extattr functions? Message-ID: <20050825034628.GA1656@crodrigues.org> References: <20050816011626.GA23116@crodrigues.org> <20050824053418.GC1553@frodo> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <20050824053418.GC1553@frodo> User-Agent: Mutt/1.5.9i X-archive-position: 5958 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rodrigc@crodrigues.org Precedence: bulk X-list: linux-xfs Content-Length: 50890 Lines: 2368 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Aug 24, 2005 at 03:34:19PM +1000, Nathan Scott wrote: > If you really want to go > with your patch, please make it compile on Linux with a recent > gcc, without warnings (of course!), and resend... thanks. What compiler are you using? I made a slight addition to my patch, and compiled the linux-2.6-xfs tree from SGI's CVS with: gcc version 3.3.5 (Debian 1:3.3.5-2) and did not get any compiler warnings in any of the XFS code. I am attaching my patch and my kernel config file. -- Craig Rodrigues rodrigc@crodrigues.org --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="extattr_patch.txt" Index: xfs_attr.c =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_attr.c,v retrieving revision 1.120 diff -u -u -r1.120 xfs_attr.c --- xfs_attr.c 18 May 2005 09:29:33 -0000 1.120 +++ xfs_attr.c 25 Aug 2005 03:41:34 -0000 @@ -122,7 +122,7 @@ *========================================================================*/ int -xfs_attr_fetch(xfs_inode_t *ip, char *name, int namelen, +xfs_attr_fetch(xfs_inode_t *ip, const char *name, int namelen, char *value, int *valuelenp, int flags, struct cred *cred) { xfs_da_args_t args; @@ -177,7 +177,7 @@ } int -xfs_attr_get(bhv_desc_t *bdp, char *name, char *value, int *valuelenp, +xfs_attr_get(bhv_desc_t *bdp, const char *name, char *value, int *valuelenp, int flags, struct cred *cred) { xfs_inode_t *ip = XFS_BHVTOI(bdp); @@ -202,7 +202,7 @@ /*ARGSUSED*/ int /* error */ -xfs_attr_set(bhv_desc_t *bdp, char *name, char *value, int valuelen, int flags, +xfs_attr_set(bhv_desc_t *bdp, const char *name, char *value, int valuelen, int flags, struct cred *cred) { xfs_da_args_t args; @@ -462,7 +462,7 @@ */ /*ARGSUSED*/ int /* error */ -xfs_attr_remove(bhv_desc_t *bdp, char *name, int flags, struct cred *cred) +xfs_attr_remove(bhv_desc_t *bdp, const char *name, int flags, struct cred *cred) { xfs_da_args_t args; xfs_inode_t *dp; Index: xfs_attr.h =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_attr.h,v retrieving revision 1.32 diff -u -u -r1.32 xfs_attr.h --- xfs_attr.h 18 May 2005 09:29:33 -0000 1.32 +++ xfs_attr.h 25 Aug 2005 03:41:35 -0000 @@ -172,15 +172,15 @@ /* * Overall external interface routines. */ -int xfs_attr_get(bhv_desc_t *, char *, char *, int *, int, struct cred *); -int xfs_attr_set(bhv_desc_t *, char *, char *, int, int, struct cred *); -int xfs_attr_remove(bhv_desc_t *, char *, int, struct cred *); +int xfs_attr_get(bhv_desc_t *, const char *, char *, int *, int, struct cred *); +int xfs_attr_set(bhv_desc_t *, const char *, char *, int, int, struct cred *); +int xfs_attr_remove(bhv_desc_t *, const char *, int, struct cred *); int xfs_attr_list(bhv_desc_t *, char *, int, int, struct attrlist_cursor_kern *, struct cred *); int xfs_attr_inactive(struct xfs_inode *dp); int xfs_attr_shortform_getvalue(struct xfs_da_args *); -int xfs_attr_fetch(struct xfs_inode *, char *, int, +int xfs_attr_fetch(struct xfs_inode *, const char *, int, char *, int *, int, struct cred *); #endif /* __XFS_ATTR_H__ */ Index: xfs_da_btree.c =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_da_btree.c,v retrieving revision 1.153 diff -u -u -r1.153 xfs_da_btree.c --- xfs_da_btree.c 22 Jun 2005 03:43:05 -0000 1.153 +++ xfs_da_btree.c 25 Aug 2005 03:41:35 -0000 @@ -1626,7 +1626,7 @@ * This is implemented with some source-level loop unrolling. */ xfs_dahash_t -xfs_da_hashname(uchar_t *name, int namelen) +xfs_da_hashname(const uchar_t *name, int namelen) { xfs_dahash_t hash; Index: xfs_da_btree.h =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/xfs_da_btree.h,v retrieving revision 1.58 diff -u -u -r1.58 xfs_da_btree.h --- xfs_da_btree.h 18 May 2005 09:29:33 -0000 1.58 +++ xfs_da_btree.h 25 Aug 2005 03:41:35 -0000 @@ -168,7 +168,7 @@ * Structure to ease passing around component names. */ typedef struct xfs_da_args { - uchar_t *name; /* string (maybe not NULL terminated) */ + const uchar_t *name; /* string (maybe not NULL terminated) */ int namelen; /* length of string (maybe no NULL) */ uchar_t *value; /* set of bytes (maybe contain NULLs) */ int valuelen; /* length of value */ @@ -314,7 +314,7 @@ int xfs_da_shrink_inode(xfs_da_args_t *args, xfs_dablk_t dead_blkno, xfs_dabuf_t *dead_buf); -uint xfs_da_hashname(uchar_t *name_string, int name_length); +uint xfs_da_hashname(const uchar_t *name_string, int name_length); uint xfs_da_log2_roundup(uint i); xfs_da_state_t *xfs_da_state_alloc(void); void xfs_da_state_free(xfs_da_state_t *state); Index: linux-2.6/xfs_vnode.h =================================================================== RCS file: /cvs/linux-2.6-xfs/fs/xfs/linux-2.6/xfs_vnode.h,v retrieving revision 1.109 diff -u -u -r1.109 xfs_vnode.h --- linux-2.6/xfs_vnode.h 3 Aug 2005 18:10:09 -0000 1.109 +++ linux-2.6/xfs_vnode.h 25 Aug 2005 03:41:35 -0000 @@ -218,11 +218,11 @@ typedef int (*vop_bmap_t)(bhv_desc_t *, xfs_off_t, ssize_t, int, struct xfs_iomap *, int *); typedef int (*vop_reclaim_t)(bhv_desc_t *); -typedef int (*vop_attr_get_t)(bhv_desc_t *, char *, char *, int *, int, +typedef int (*vop_attr_get_t)(bhv_desc_t *, const char *, char *, int *, int, struct cred *); -typedef int (*vop_attr_set_t)(bhv_desc_t *, char *, char *, int, int, +typedef int (*vop_attr_set_t)(bhv_desc_t *, const char *, char *, int, int, struct cred *); -typedef int (*vop_attr_remove_t)(bhv_desc_t *, char *, int, struct cred *); +typedef int (*vop_attr_remove_t)(bhv_desc_t *, const char *, int, struct cred *); typedef int (*vop_attr_list_t)(bhv_desc_t *, char *, int, int, struct attrlist_cursor_kern *, struct cred *); typedef void (*vop_link_removed_t)(bhv_desc_t *, vnode_t *, int); --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="config.xt" # # Automatically generated make config: don't edit # Linux kernel version: 2.6.12 # Wed Aug 24 23:03:06 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_IOMAP=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # CONFIG_CLEAN_COMPILE is not set CONFIG_BROKEN=y CONFIG_BROKEN_ON_SMP=y CONFIG_LOCK_KERNEL=y CONFIG_INIT_ENV_ARG_LIMIT=32 # # General setup # CONFIG_LOCALVERSION="" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_POSIX_MQUEUE=y CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set CONFIG_SYSCTL=y CONFIG_AUDIT=y CONFIG_AUDITSYSCALL=y CONFIG_HOTPLUG=y CONFIG_KOBJECT_UEVENT=y # CONFIG_IKCONFIG is not set # CONFIG_CPUSETS is not set # CONFIG_EMBEDDED is not set CONFIG_KALLSYMS=y # CONFIG_KALLSYMS_ALL is not set # CONFIG_KALLSYMS_EXTRA_PASS is not set CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SHMEM=y CONFIG_CC_ALIGN_FUNCTIONS=0 CONFIG_CC_ALIGN_LABELS=0 CONFIG_CC_ALIGN_LOOPS=0 CONFIG_CC_ALIGN_JUMPS=0 # CONFIG_TINY_SHMEM is not set CONFIG_BASE_SMALL=0 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y CONFIG_MODULE_FORCE_UNLOAD=y CONFIG_OBSOLETE_MODPARM=y # CONFIG_MODVERSIONS is not set # CONFIG_MODULE_SRCVERSION_ALL is not set CONFIG_KMOD=y CONFIG_STOP_MACHINE=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_ELAN is not set # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_X86_GENERICARCH is not set # CONFIG_X86_ES7000 is not set CONFIG_M386=y # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUMM is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MCRUSOE is not set # CONFIG_MEFFICEON is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MGEODEGX1 is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_GENERIC=y CONFIG_X86_L1_CACHE_SHIFT=7 CONFIG_RWSEM_GENERIC_SPINLOCK=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_INTEL_USERCOPY=y CONFIG_HPET_TIMER=y CONFIG_SMP=y CONFIG_NR_CPUS=32 # CONFIG_SCHED_SMT is not set CONFIG_PREEMPT=y CONFIG_PREEMPT_BKL=y CONFIG_X86_LOCAL_APIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_MCE=y # CONFIG_X86_MCE_NONFATAL is not set # CONFIG_X86_MCE_P4THERMAL is not set CONFIG_TOSHIBA=m CONFIG_I8K=m # CONFIG_X86_REBOOTFIXUPS is not set CONFIG_MICROCODE=m CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # # Firmware Drivers # CONFIG_EDD=m # CONFIG_NOHIGHMEM is not set CONFIG_HIGHMEM4G=y # CONFIG_HIGHMEM64G is not set CONFIG_HIGHMEM=y # CONFIG_HIGHPTE is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_EFI is not set CONFIG_IRQBALANCE=y # CONFIG_REGPARM is not set CONFIG_SECCOMP=y # # Power management options (ACPI, APM) # CONFIG_PM=y # CONFIG_PM_DEBUG is not set CONFIG_SOFTWARE_SUSPEND=y CONFIG_PM_STD_PARTITION="" # # ACPI (Advanced Configuration and Power Interface) Support # CONFIG_ACPI=y CONFIG_ACPI_BOOT=y CONFIG_ACPI_INTERPRETER=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_SLEEP_PROC_FS=y CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m CONFIG_ACPI_PROCESSOR=m CONFIG_ACPI_THERMAL=m CONFIG_ACPI_ASUS=m CONFIG_ACPI_IBM=m CONFIG_ACPI_TOSHIBA=m CONFIG_ACPI_BLACKLIST_YEAR=0 # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUS=y CONFIG_ACPI_EC=y CONFIG_ACPI_POWER=y CONFIG_ACPI_PCI=y CONFIG_ACPI_SYSTEM=y CONFIG_X86_PM_TIMER=y # CONFIG_ACPI_CONTAINER is not set # # APM (Advanced Power Management) BIOS Support # CONFIG_APM=m # CONFIG_APM_IGNORE_USER_SUSPEND is not set CONFIG_APM_DO_ENABLE=y # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set CONFIG_APM_ALLOW_INTS=y # CONFIG_APM_REAL_MODE_POWER_OFF is not set # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_TABLE=y # CONFIG_CPU_FREQ_DEBUG is not set CONFIG_CPU_FREQ_STAT=y # CONFIG_CPU_FREQ_STAT_DETAILS is not set CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m # CONFIG_CPU_FREQ_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_GOV_CONSERVATIVE is not set # # CPUFreq processor drivers # CONFIG_X86_ACPI_CPUFREQ=m CONFIG_X86_POWERNOW_K6=m CONFIG_X86_POWERNOW_K7=m CONFIG_X86_POWERNOW_K7_ACPI=y CONFIG_X86_POWERNOW_K8=m CONFIG_X86_POWERNOW_K8_ACPI=y CONFIG_X86_GX_SUSPMOD=m CONFIG_X86_SPEEDSTEP_CENTRINO=m CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y CONFIG_X86_SPEEDSTEP_ICH=m CONFIG_X86_SPEEDSTEP_SMI=m CONFIG_X86_P4_CLOCKMOD=m # CONFIG_X86_CPUFREQ_NFORCE2 is not set CONFIG_X86_LONGRUN=m CONFIG_X86_LONGHAUL=m # # shared options # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF=y CONFIG_X86_SPEEDSTEP_LIB=m CONFIG_X86_SPEEDSTEP_RELAXED_CAP_CHECK=y # # Bus options (PCI, PCMCIA, EISA, MCA, ISA) # CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GOMMCONFIG is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_MMCONFIG=y # CONFIG_PCIEPORTBUS is not set # CONFIG_PCI_MSI is not set CONFIG_PCI_LEGACY_PROC=y CONFIG_PCI_NAMES=y # CONFIG_PCI_DEBUG is not set CONFIG_ISA_DMA_API=y CONFIG_ISA=y CONFIG_EISA=y CONFIG_EISA_VLB_PRIMING=y CONFIG_EISA_PCI_EISA=y CONFIG_EISA_VIRTUAL_ROOT=y CONFIG_EISA_NAMES=y CONFIG_MCA=y CONFIG_MCA_LEGACY=y CONFIG_MCA_PROC_FS=y CONFIG_SCx200=m # # PCCARD (PCMCIA/CardBus) support # # CONFIG_PCCARD is not set # # PCI Hotplug Support # CONFIG_HOTPLUG_PCI=m CONFIG_HOTPLUG_PCI_FAKE=m CONFIG_HOTPLUG_PCI_COMPAQ=m # CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set CONFIG_HOTPLUG_PCI_IBM=m CONFIG_HOTPLUG_PCI_ACPI=m # CONFIG_HOTPLUG_PCI_ACPI_IBM is not set CONFIG_HOTPLUG_PCI_CPCI=y CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m CONFIG_HOTPLUG_PCI_SHPC=m # CONFIG_HOTPLUG_PCI_SHPC_POLL_EVENT_MODE is not set # # Executable file formats # CONFIG_BINFMT_ELF=y CONFIG_BINFMT_AOUT=m CONFIG_BINFMT_MISC=m # # Device Drivers # # # Generic Driver Options # CONFIG_STANDALONE=y CONFIG_PREVENT_FIRMWARE_BUILD=y CONFIG_FW_LOADER=m # CONFIG_DEBUG_DRIVER is not set # # Memory Technology Devices (MTD) # CONFIG_MTD=m # CONFIG_MTD_DEBUG is not set CONFIG_MTD_CONCAT=m # CONFIG_MTD_PARTITIONS is not set # # User Modules And Translation Layers # CONFIG_MTD_CHAR=m CONFIG_MTD_BLOCK=m CONFIG_MTD_BLOCK_RO=m CONFIG_FTL=m CONFIG_NFTL=m CONFIG_NFTL_RW=y CONFIG_INFTL=m # # RAM/ROM/Flash chip drivers # CONFIG_MTD_CFI=m CONFIG_MTD_JEDECPROBE=m CONFIG_MTD_GEN_PROBE=m # CONFIG_MTD_CFI_ADV_OPTIONS is not set CONFIG_MTD_MAP_BANK_WIDTH_1=y CONFIG_MTD_MAP_BANK_WIDTH_2=y CONFIG_MTD_MAP_BANK_WIDTH_4=y # CONFIG_MTD_MAP_BANK_WIDTH_8 is not set # CONFIG_MTD_MAP_BANK_WIDTH_16 is not set # CONFIG_MTD_MAP_BANK_WIDTH_32 is not set CONFIG_MTD_CFI_I1=y CONFIG_MTD_CFI_I2=y # CONFIG_MTD_CFI_I4 is not set # CONFIG_MTD_CFI_I8 is not set CONFIG_MTD_CFI_INTELEXT=m CONFIG_MTD_CFI_AMDSTD=m CONFIG_MTD_CFI_AMDSTD_RETRY=0 CONFIG_MTD_CFI_STAA=m CONFIG_MTD_CFI_UTIL=m CONFIG_MTD_RAM=m CONFIG_MTD_ROM=m CONFIG_MTD_ABSENT=m # CONFIG_MTD_OBSOLETE_CHIPS is not set # # Mapping drivers for chip access # CONFIG_MTD_COMPLEX_MAPPINGS=y CONFIG_MTD_PHYSMAP=m CONFIG_MTD_PHYSMAP_START=0x8000000 CONFIG_MTD_PHYSMAP_LEN=0x4000000 CONFIG_MTD_PHYSMAP_BANKWIDTH=2 CONFIG_MTD_SC520CDP=m CONFIG_MTD_AMD76XROM=m # CONFIG_MTD_ICHXROM is not set CONFIG_MTD_SCB2_FLASH=m CONFIG_MTD_L440GX=m CONFIG_MTD_PCI=m # # Self-contained MTD device drivers # CONFIG_MTD_PMC551=m CONFIG_MTD_PMC551_BUGFIX=y # CONFIG_MTD_PMC551_DEBUG is not set CONFIG_MTD_SLRAM=m # CONFIG_MTD_PHRAM is not set CONFIG_MTD_MTDRAM=m CONFIG_MTDRAM_TOTAL_SIZE=4096 CONFIG_MTDRAM_ERASE_SIZE=128 CONFIG_MTD_BLKMTD=m # CONFIG_MTD_BLOCK2MTD is not set # # Disk-On-Chip Device Drivers # CONFIG_MTD_DOC2000=m CONFIG_MTD_DOC2001=m CONFIG_MTD_DOC2001PLUS=m CONFIG_MTD_DOCPROBE=m CONFIG_MTD_DOCECC=m # CONFIG_MTD_DOCPROBE_ADVANCED is not set CONFIG_MTD_DOCPROBE_ADDRESS=0 # # NAND Flash Device Drivers # CONFIG_MTD_NAND=m # CONFIG_MTD_NAND_VERIFY_WRITE is not set CONFIG_MTD_NAND_IDS=m # CONFIG_MTD_NAND_DISKONCHIP is not set # # Parallel port support # # CONFIG_PARPORT is not set # # Plug and Play support # CONFIG_PNP=y # CONFIG_PNP_DEBUG is not set # # Protocols # CONFIG_ISAPNP=y CONFIG_PNPBIOS=y CONFIG_PNPBIOS_PROC_FS=y CONFIG_PNPACPI=y # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_PS2=m CONFIG_BLK_DEV_XD=m CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m CONFIG_CISS_SCSI_TAPE=y CONFIG_BLK_DEV_DAC960=m CONFIG_BLK_DEV_UMEM=m # CONFIG_BLK_DEV_COW_COMMON is not set CONFIG_BLK_DEV_LOOP=m CONFIG_BLK_DEV_CRYPTOLOOP=m CONFIG_BLK_DEV_NBD=m # CONFIG_BLK_DEV_SX8 is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_COUNT=16 CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_LBD=y # CONFIG_CDROM_PKTCDVD is not set # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_AS=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y # CONFIG_ATA_OVER_ETH is not set # # ATA/ATAPI/MFM/RLL support # CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y # # Please see Documentation/ide.txt for help/info on IDE drives # # CONFIG_BLK_DEV_IDE_SATA is not set # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_IDEDISK_MULTI_MODE=y CONFIG_BLK_DEV_IDECD=m CONFIG_BLK_DEV_IDETAPE=m CONFIG_BLK_DEV_IDEFLOPPY=m CONFIG_BLK_DEV_IDESCSI=m CONFIG_IDE_TASK_IOCTL=y # # IDE chipset support/bugfixes # CONFIG_IDE_GENERIC=y CONFIG_BLK_DEV_CMD640=y CONFIG_BLK_DEV_CMD640_ENHANCED=y CONFIG_BLK_DEV_IDEPNP=y CONFIG_BLK_DEV_IDEPCI=y CONFIG_IDEPCI_SHARE_IRQ=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_BLK_DEV_GENERIC=y CONFIG_BLK_DEV_OPTI621=y CONFIG_BLK_DEV_RZ1000=y CONFIG_BLK_DEV_IDEDMA_PCI=y # CONFIG_BLK_DEV_IDEDMA_FORCED is not set # CONFIG_IDEDMA_PCI_AUTO is not set CONFIG_BLK_DEV_AEC62XX=y CONFIG_BLK_DEV_ALI15X3=y # CONFIG_WDC_ALI15X3 is not set CONFIG_BLK_DEV_AMD74XX=y CONFIG_BLK_DEV_ATIIXP=y CONFIG_BLK_DEV_CMD64X=y CONFIG_BLK_DEV_TRIFLEX=y CONFIG_BLK_DEV_CY82C693=y CONFIG_BLK_DEV_CS5520=y CONFIG_BLK_DEV_CS5530=y CONFIG_BLK_DEV_HPT34X=y # CONFIG_HPT34X_AUTODMA is not set CONFIG_BLK_DEV_HPT366=y CONFIG_BLK_DEV_SC1200=y CONFIG_BLK_DEV_PIIX=y CONFIG_BLK_DEV_NS87415=y CONFIG_BLK_DEV_PDC202XX_OLD=y # CONFIG_PDC202XX_BURST is not set CONFIG_BLK_DEV_PDC202XX_NEW=y CONFIG_PDC202XX_FORCE=y CONFIG_BLK_DEV_SVWKS=y CONFIG_BLK_DEV_SIIMAGE=y CONFIG_BLK_DEV_SIS5513=y CONFIG_BLK_DEV_SLC90E66=y CONFIG_BLK_DEV_TRM290=y CONFIG_BLK_DEV_VIA82CXXX=y # CONFIG_IDE_ARM is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_IDEDMA=y CONFIG_IDEDMA_IVB=y # CONFIG_IDEDMA_AUTO is not set # CONFIG_BLK_DEV_HD is not set # # SCSI device support # CONFIG_SCSI=m # CONFIG_SCSI_PROC_FS is not set # # SCSI support type (disk, tape, CD-ROM) # # CONFIG_BLK_DEV_SD is not set # CONFIG_CHR_DEV_ST is not set # CONFIG_CHR_DEV_OSST is not set # CONFIG_BLK_DEV_SR is not set CONFIG_CHR_DEV_SG=m # # Some SCSI devices (e.g. CD jukebox) support multiple LUNs # # CONFIG_SCSI_MULTI_LUN is not set # CONFIG_SCSI_CONSTANTS is not set # CONFIG_SCSI_LOGGING is not set # # SCSI Transport Attributes # CONFIG_SCSI_SPI_ATTRS=m CONFIG_SCSI_FC_ATTRS=m # CONFIG_SCSI_ISCSI_ATTRS is not set # # SCSI low-level drivers # CONFIG_BLK_DEV_3W_XXXX_RAID=m # CONFIG_SCSI_3W_9XXX is not set CONFIG_SCSI_7000FASST=m CONFIG_SCSI_ACARD=m CONFIG_SCSI_AHA152X=m CONFIG_SCSI_AHA1542=m CONFIG_SCSI_AHA1740=m CONFIG_SCSI_AACRAID=m CONFIG_SCSI_AIC7XXX=m CONFIG_AIC7XXX_CMDS_PER_DEVICE=253 CONFIG_AIC7XXX_RESET_DELAY_MS=15000 CONFIG_AIC7XXX_PROBE_EISA_VL=y # CONFIG_AIC7XXX_DEBUG_ENABLE is not set CONFIG_AIC7XXX_DEBUG_MASK=0 # CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set CONFIG_SCSI_AIC7XXX_OLD=m CONFIG_SCSI_AIC79XX=m CONFIG_AIC79XX_CMDS_PER_DEVICE=32 CONFIG_AIC79XX_RESET_DELAY_MS=15000 CONFIG_AIC79XX_ENABLE_RD_STRM=y # CONFIG_AIC79XX_DEBUG_ENABLE is not set CONFIG_AIC79XX_DEBUG_MASK=0 # CONFIG_AIC79XX_REG_PRETTY_PRINT is not set CONFIG_SCSI_DPT_I2O=m CONFIG_SCSI_ADVANSYS=m CONFIG_SCSI_IN2000=m # CONFIG_MEGARAID_NEWGEN is not set # CONFIG_MEGARAID_LEGACY is not set CONFIG_SCSI_SATA=y # CONFIG_SCSI_SATA_AHCI is not set CONFIG_SCSI_SATA_SVW=y CONFIG_SCSI_ATA_PIIX=y # CONFIG_SCSI_SATA_NV is not set CONFIG_SCSI_SATA_PROMISE=y # CONFIG_SCSI_SATA_QSTOR is not set CONFIG_SCSI_SATA_SX4=y CONFIG_SCSI_SATA_SIL=y CONFIG_SCSI_SATA_SIS=y # CONFIG_SCSI_SATA_ULI is not set CONFIG_SCSI_SATA_VIA=y CONFIG_SCSI_SATA_VITESSE=y CONFIG_SCSI_BUSLOGIC=m # CONFIG_SCSI_OMIT_FLASHPOINT is not set # CONFIG_SCSI_CPQFCTS is not set CONFIG_SCSI_DMX3191D=m CONFIG_SCSI_DTC3280=m CONFIG_SCSI_EATA=m # CONFIG_SCSI_EATA_TAGGED_QUEUE is not set # CONFIG_SCSI_EATA_LINKED_COMMANDS is not set CONFIG_SCSI_EATA_MAX_TAGS=16 CONFIG_SCSI_EATA_PIO=m CONFIG_SCSI_FUTURE_DOMAIN=m CONFIG_SCSI_FD_MCS=m CONFIG_SCSI_GDTH=m CONFIG_SCSI_GENERIC_NCR5380=m CONFIG_SCSI_GENERIC_NCR5380_MMIO=m CONFIG_SCSI_GENERIC_NCR53C400=y CONFIG_SCSI_IBMMCA=m CONFIG_IBMMCA_SCSI_ORDER_STANDARD=y # CONFIG_IBMMCA_SCSI_DEV_RESET is not set CONFIG_SCSI_IPS=m CONFIG_SCSI_INITIO=m CONFIG_SCSI_INIA100=m CONFIG_SCSI_NCR53C406A=m CONFIG_SCSI_NCR_D700=m CONFIG_SCSI_SYM53C8XX_2=m CONFIG_SCSI_SYM53C8XX_DMA_ADDRESSING_MODE=0 CONFIG_SCSI_SYM53C8XX_DEFAULT_TAGS=16 CONFIG_SCSI_SYM53C8XX_MAX_TAGS=64 # CONFIG_SCSI_SYM53C8XX_IOMAPPED is not set # CONFIG_SCSI_IPR is not set CONFIG_SCSI_NCR_Q720=m CONFIG_SCSI_NCR53C8XX_DEFAULT_TAGS=8 CONFIG_SCSI_NCR53C8XX_MAX_TAGS=32 CONFIG_SCSI_NCR53C8XX_SYNC=20 # CONFIG_SCSI_NCR53C8XX_PROFILE is not set CONFIG_SCSI_MCA_53C9X=m CONFIG_SCSI_PAS16=m # CONFIG_SCSI_PCI2000 is not set # CONFIG_SCSI_PCI2220I is not set CONFIG_SCSI_PSI240I=m CONFIG_SCSI_QLOGIC_FAS=m CONFIG_SCSI_QLOGIC_ISP=m CONFIG_SCSI_QLOGIC_FC=m CONFIG_SCSI_QLOGIC_FC_FIRMWARE=y CONFIG_SCSI_QLOGIC_1280=m # CONFIG_SCSI_QLOGIC_1280_1040 is not set CONFIG_SCSI_QLA2XXX=m CONFIG_SCSI_QLA21XX=m CONFIG_SCSI_QLA22XX=m CONFIG_SCSI_QLA2300=m CONFIG_SCSI_QLA2322=m CONFIG_SCSI_QLA6312=m # CONFIG_SCSI_LPFC is not set CONFIG_SCSI_SEAGATE=m CONFIG_SCSI_SIM710=m CONFIG_53C700_IO_MAPPED=y CONFIG_SCSI_SYM53C416=m CONFIG_SCSI_DC395x=m CONFIG_SCSI_DC390T=m CONFIG_SCSI_T128=m CONFIG_SCSI_U14_34F=m # CONFIG_SCSI_U14_34F_TAGGED_QUEUE is not set # CONFIG_SCSI_U14_34F_LINKED_COMMANDS is not set CONFIG_SCSI_U14_34F_MAX_TAGS=8 CONFIG_SCSI_ULTRASTOR=m CONFIG_SCSI_NSP32=m CONFIG_SCSI_DEBUG=m # # Old CD-ROM drivers (not SCSI, not IDE) # # CONFIG_CD_NO_IDESCSI is not set # # Multi-device support (RAID and LVM) # CONFIG_MD=y CONFIG_BLK_DEV_MD=m CONFIG_MD_LINEAR=m CONFIG_MD_RAID0=m CONFIG_MD_RAID1=m # CONFIG_MD_RAID10 is not set CONFIG_MD_RAID5=m CONFIG_MD_RAID6=m CONFIG_MD_MULTIPATH=m # CONFIG_MD_FAULTY is not set CONFIG_BLK_DEV_DM=m CONFIG_DM_CRYPT=m # CONFIG_DM_SNAPSHOT is not set # CONFIG_DM_MIRROR is not set # CONFIG_DM_ZERO is not set # CONFIG_DM_MULTIPATH is not set # # Fusion MPT device support # # CONFIG_FUSION is not set # # IEEE 1394 (FireWire) support # # CONFIG_IEEE1394 is not set # # I2O device support # CONFIG_I2O=m CONFIG_I2O_CONFIG=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m # # Networking support # CONFIG_NET=y # # Networking options # CONFIG_PACKET=m CONFIG_PACKET_MMAP=y CONFIG_UNIX=y CONFIG_NET_KEY=y CONFIG_INET=y CONFIG_IP_MULTICAST=y CONFIG_IP_ADVANCED_ROUTER=y CONFIG_IP_MULTIPLE_TABLES=y CONFIG_IP_ROUTE_FWMARK=y # CONFIG_IP_ROUTE_MULTIPATH is not set # CONFIG_IP_ROUTE_VERBOSE is not set # CONFIG_IP_PNP is not set CONFIG_NET_IPIP=m CONFIG_NET_IPGRE=m # CONFIG_NET_IPGRE_BROADCAST is not set # CONFIG_IP_MROUTE is not set # CONFIG_ARPD is not set CONFIG_SYN_COOKIES=y CONFIG_INET_AH=m CONFIG_INET_ESP=m CONFIG_INET_IPCOMP=m CONFIG_INET_TUNNEL=m CONFIG_IP_TCPDIAG=y # CONFIG_IP_TCPDIAG_IPV6 is not set # # IP: Virtual Server Configuration # CONFIG_IP_VS=m # CONFIG_IP_VS_DEBUG is not set CONFIG_IP_VS_TAB_BITS=12 # # IPVS transport protocol load balancing support # CONFIG_IP_VS_PROTO_TCP=y CONFIG_IP_VS_PROTO_UDP=y CONFIG_IP_VS_PROTO_ESP=y CONFIG_IP_VS_PROTO_AH=y # # IPVS scheduler # CONFIG_IP_VS_RR=m CONFIG_IP_VS_WRR=m CONFIG_IP_VS_LC=m CONFIG_IP_VS_WLC=m CONFIG_IP_VS_LBLC=m CONFIG_IP_VS_LBLCR=m CONFIG_IP_VS_DH=m CONFIG_IP_VS_SH=m CONFIG_IP_VS_SED=m CONFIG_IP_VS_NQ=m # # IPVS application helper # CONFIG_IP_VS_FTP=m CONFIG_IPV6=m CONFIG_IPV6_PRIVACY=y CONFIG_INET6_AH=m CONFIG_INET6_ESP=m CONFIG_INET6_IPCOMP=m CONFIG_INET6_TUNNEL=m CONFIG_IPV6_TUNNEL=m CONFIG_NETFILTER=y # CONFIG_NETFILTER_DEBUG is not set CONFIG_BRIDGE_NETFILTER=y # # IP: Netfilter Configuration # CONFIG_IP_NF_CONNTRACK=m # CONFIG_IP_NF_CT_ACCT is not set # CONFIG_IP_NF_CONNTRACK_MARK is not set # CONFIG_IP_NF_CT_PROTO_SCTP is not set CONFIG_IP_NF_FTP=m CONFIG_IP_NF_IRC=m CONFIG_IP_NF_TFTP=m CONFIG_IP_NF_AMANDA=m CONFIG_IP_NF_QUEUE=m CONFIG_IP_NF_IPTABLES=m CONFIG_IP_NF_MATCH_LIMIT=m CONFIG_IP_NF_MATCH_IPRANGE=m CONFIG_IP_NF_MATCH_MAC=m CONFIG_IP_NF_MATCH_PKTTYPE=m CONFIG_IP_NF_MATCH_MARK=m CONFIG_IP_NF_MATCH_MULTIPORT=m CONFIG_IP_NF_MATCH_TOS=m CONFIG_IP_NF_MATCH_RECENT=m CONFIG_IP_NF_MATCH_ECN=m CONFIG_IP_NF_MATCH_DSCP=m CONFIG_IP_NF_MATCH_AH_ESP=m CONFIG_IP_NF_MATCH_LENGTH=m CONFIG_IP_NF_MATCH_TTL=m CONFIG_IP_NF_MATCH_TCPMSS=m CONFIG_IP_NF_MATCH_HELPER=m CONFIG_IP_NF_MATCH_STATE=m CONFIG_IP_NF_MATCH_CONNTRACK=m CONFIG_IP_NF_MATCH_OWNER=m CONFIG_IP_NF_MATCH_PHYSDEV=m # CONFIG_IP_NF_MATCH_ADDRTYPE is not set # CONFIG_IP_NF_MATCH_REALM is not set # CONFIG_IP_NF_MATCH_SCTP is not set # CONFIG_IP_NF_MATCH_COMMENT is not set # CONFIG_IP_NF_MATCH_HASHLIMIT is not set CONFIG_IP_NF_FILTER=m CONFIG_IP_NF_TARGET_REJECT=m CONFIG_IP_NF_TARGET_LOG=m CONFIG_IP_NF_TARGET_ULOG=m CONFIG_IP_NF_TARGET_TCPMSS=m CONFIG_IP_NF_NAT=m CONFIG_IP_NF_NAT_NEEDED=y CONFIG_IP_NF_TARGET_MASQUERADE=m CONFIG_IP_NF_TARGET_REDIRECT=m CONFIG_IP_NF_TARGET_NETMAP=m CONFIG_IP_NF_TARGET_SAME=m CONFIG_IP_NF_NAT_SNMP_BASIC=m CONFIG_IP_NF_NAT_IRC=m CONFIG_IP_NF_NAT_FTP=m CONFIG_IP_NF_NAT_TFTP=m CONFIG_IP_NF_NAT_AMANDA=m CONFIG_IP_NF_MANGLE=m CONFIG_IP_NF_TARGET_TOS=m CONFIG_IP_NF_TARGET_ECN=m CONFIG_IP_NF_TARGET_DSCP=m CONFIG_IP_NF_TARGET_MARK=m CONFIG_IP_NF_TARGET_CLASSIFY=m CONFIG_IP_NF_RAW=m CONFIG_IP_NF_TARGET_NOTRACK=m CONFIG_IP_NF_ARPTABLES=m CONFIG_IP_NF_ARPFILTER=m CONFIG_IP_NF_ARP_MANGLE=m # # IPv6: Netfilter Configuration (EXPERIMENTAL) # CONFIG_IP6_NF_QUEUE=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_LIMIT=m CONFIG_IP6_NF_MATCH_MAC=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_MULTIPORT=m CONFIG_IP6_NF_MATCH_OWNER=m CONFIG_IP6_NF_MATCH_MARK=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_AHESP=m CONFIG_IP6_NF_MATCH_LENGTH=m CONFIG_IP6_NF_MATCH_EUI64=m # CONFIG_IP6_NF_MATCH_PHYSDEV is not set CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_TARGET_MARK=m CONFIG_IP6_NF_RAW=m # # DECnet: Netfilter Configuration # CONFIG_DECNET_NF_GRABULATOR=m # # Bridge: Netfilter Configuration # CONFIG_BRIDGE_NF_EBTABLES=m CONFIG_BRIDGE_EBT_BROUTE=m CONFIG_BRIDGE_EBT_T_FILTER=m CONFIG_BRIDGE_EBT_T_NAT=m CONFIG_BRIDGE_EBT_802_3=m CONFIG_BRIDGE_EBT_AMONG=m CONFIG_BRIDGE_EBT_ARP=m CONFIG_BRIDGE_EBT_IP=m CONFIG_BRIDGE_EBT_LIMIT=m CONFIG_BRIDGE_EBT_MARK=m CONFIG_BRIDGE_EBT_PKTTYPE=m CONFIG_BRIDGE_EBT_STP=m CONFIG_BRIDGE_EBT_VLAN=m CONFIG_BRIDGE_EBT_ARPREPLY=m CONFIG_BRIDGE_EBT_DNAT=m CONFIG_BRIDGE_EBT_MARK_T=m CONFIG_BRIDGE_EBT_REDIRECT=m CONFIG_BRIDGE_EBT_SNAT=m CONFIG_BRIDGE_EBT_LOG=m # CONFIG_BRIDGE_EBT_ULOG is not set CONFIG_XFRM=y CONFIG_XFRM_USER=m # # SCTP Configuration (EXPERIMENTAL) # CONFIG_IP_SCTP=m # CONFIG_SCTP_DBG_MSG is not set # CONFIG_SCTP_DBG_OBJCNT is not set CONFIG_SCTP_HMAC_NONE=y # CONFIG_SCTP_HMAC_SHA1 is not set # CONFIG_SCTP_HMAC_MD5 is not set CONFIG_ATM=m CONFIG_ATM_CLIP=m CONFIG_ATM_CLIP_NO_ICMP=y CONFIG_ATM_LANE=m CONFIG_ATM_MPOA=m CONFIG_ATM_BR2684=m # CONFIG_ATM_BR2684_IPFILTER is not set CONFIG_BRIDGE=m CONFIG_VLAN_8021Q=m CONFIG_DECNET=m CONFIG_DECNET_ROUTER=y CONFIG_DECNET_ROUTE_FWMARK=y CONFIG_LLC=y CONFIG_LLC2=m CONFIG_IPX=m CONFIG_IPX_INTERN=y CONFIG_ATALK=m CONFIG_DEV_APPLETALK=y CONFIG_LTPC=m CONFIG_COPS=m CONFIG_COPS_DAYNA=y CONFIG_COPS_TANGENT=y CONFIG_IPDDP=m CONFIG_IPDDP_ENCAP=y CONFIG_IPDDP_DECAP=y CONFIG_X25=m CONFIG_LAPB=m # CONFIG_NET_DIVERT is not set CONFIG_ECONET=m CONFIG_ECONET_AUNUDP=y CONFIG_ECONET_NATIVE=y CONFIG_WAN_ROUTER=m # # QoS and/or fair queueing # CONFIG_NET_SCHED=y CONFIG_NET_SCH_CLK_JIFFIES=y # CONFIG_NET_SCH_CLK_GETTIMEOFDAY is not set # CONFIG_NET_SCH_CLK_CPU is not set CONFIG_NET_SCH_CBQ=m CONFIG_NET_SCH_HTB=m CONFIG_NET_SCH_HFSC=m CONFIG_NET_SCH_ATM=m CONFIG_NET_SCH_PRIO=m CONFIG_NET_SCH_RED=m CONFIG_NET_SCH_SFQ=m CONFIG_NET_SCH_TEQL=m CONFIG_NET_SCH_TBF=m CONFIG_NET_SCH_GRED=m CONFIG_NET_SCH_DSMARK=m # CONFIG_NET_SCH_NETEM is not set CONFIG_NET_SCH_INGRESS=m CONFIG_NET_QOS=y CONFIG_NET_ESTIMATOR=y CONFIG_NET_CLS=y # CONFIG_NET_CLS_BASIC is not set CONFIG_NET_CLS_TCINDEX=m CONFIG_NET_CLS_ROUTE4=m CONFIG_NET_CLS_ROUTE=y CONFIG_NET_CLS_FW=m CONFIG_NET_CLS_U32=m # CONFIG_CLS_U32_PERF is not set # CONFIG_NET_CLS_IND is not set # CONFIG_CLS_U32_MARK is not set CONFIG_NET_CLS_RSVP=m CONFIG_NET_CLS_RSVP6=m # CONFIG_NET_EMATCH is not set # CONFIG_NET_CLS_ACT is not set CONFIG_NET_CLS_POLICE=y # # Network testing # CONFIG_NET_PKTGEN=m CONFIG_NETPOLL=y CONFIG_NETPOLL_RX=y CONFIG_NETPOLL_TRAP=y CONFIG_NET_POLL_CONTROLLER=y CONFIG_HAMRADIO=y # # Packet Radio protocols # CONFIG_AX25=m CONFIG_AX25_DAMA_SLAVE=y CONFIG_NETROM=m CONFIG_ROSE=m # # AX.25 network device drivers # CONFIG_MKISS=m CONFIG_6PACK=m CONFIG_BPQETHER=m CONFIG_DMASCC=m CONFIG_SCC=m CONFIG_SCC_DELAY=y CONFIG_SCC_TRXECHO=y CONFIG_BAYCOM_SER_FDX=m CONFIG_BAYCOM_SER_HDX=m CONFIG_YAM=m CONFIG_IRDA=m # # IrDA protocols # CONFIG_IRLAN=m CONFIG_IRNET=m CONFIG_IRCOMM=m CONFIG_IRDA_ULTRA=y # # IrDA options # CONFIG_IRDA_CACHE_LAST_LSAP=y CONFIG_IRDA_FAST_RR=y # CONFIG_IRDA_DEBUG is not set # # Infrared-port device drivers # # # SIR device drivers # CONFIG_IRTTY_SIR=m # # Dongle support # CONFIG_DONGLE=y CONFIG_ESI_DONGLE=m CONFIG_ACTISYS_DONGLE=m CONFIG_TEKRAM_DONGLE=m CONFIG_LITELINK_DONGLE=m CONFIG_MA600_DONGLE=m CONFIG_GIRBIL_DONGLE=m CONFIG_MCP2120_DONGLE=m CONFIG_OLD_BELKIN_DONGLE=m CONFIG_ACT200L_DONGLE=m # # Old SIR device drivers # CONFIG_IRPORT_SIR=m # # Old Serial dongle support # CONFIG_DONGLE_OLD=y CONFIG_ESI_DONGLE_OLD=m CONFIG_ACTISYS_DONGLE_OLD=m CONFIG_TEKRAM_DONGLE_OLD=m CONFIG_GIRBIL_DONGLE_OLD=m CONFIG_LITELINK_DONGLE_OLD=m CONFIG_MCP2120_DONGLE_OLD=m CONFIG_OLD_BELKIN_DONGLE_OLD=m CONFIG_ACT200L_DONGLE_OLD=m CONFIG_MA600_DONGLE_OLD=m # # FIR device drivers # CONFIG_NSC_FIR=m CONFIG_WINBOND_FIR=m CONFIG_TOSHIBA_FIR=m CONFIG_SMC_IRCC_FIR=m CONFIG_ALI_FIR=m CONFIG_VLSI_FIR=m CONFIG_VIA_FIR=m CONFIG_BT=m CONFIG_BT_L2CAP=m CONFIG_BT_SCO=m CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_BNEP=m CONFIG_BT_BNEP_MC_FILTER=y CONFIG_BT_BNEP_PROTO_FILTER=y # CONFIG_BT_HIDP is not set # # Bluetooth device drivers # CONFIG_BT_HCIUART=m CONFIG_BT_HCIUART_H4=y CONFIG_BT_HCIUART_BCSP=y CONFIG_BT_HCIUART_BCSP_TXCRC=y CONFIG_BT_HCIVHCI=m CONFIG_NETDEVICES=y CONFIG_DUMMY=m CONFIG_BONDING=m CONFIG_EQUALIZER=m CONFIG_TUN=m CONFIG_NET_SB1000=m # # ARCnet devices # CONFIG_ARCNET=m CONFIG_ARCNET_1201=m CONFIG_ARCNET_1051=m CONFIG_ARCNET_RAW=m # CONFIG_ARCNET_CAP is not set CONFIG_ARCNET_COM90xx=m CONFIG_ARCNET_COM90xxIO=m CONFIG_ARCNET_RIM_I=m CONFIG_ARCNET_COM20020=m CONFIG_ARCNET_COM20020_ISA=m CONFIG_ARCNET_COM20020_PCI=m # # Ethernet (10 or 100Mbit) # CONFIG_NET_ETHERNET=y CONFIG_MII=m CONFIG_HAPPYMEAL=m CONFIG_SUNGEM=m CONFIG_NET_VENDOR_3COM=y CONFIG_EL1=m CONFIG_EL2=m CONFIG_ELPLUS=m CONFIG_EL16=m CONFIG_EL3=m CONFIG_3C515=m CONFIG_ELMC=m CONFIG_ELMC_II=m CONFIG_VORTEX=m CONFIG_TYPHOON=m CONFIG_LANCE=m CONFIG_NET_VENDOR_SMC=y CONFIG_WD80x3=m CONFIG_ULTRAMCA=m CONFIG_ULTRA=m CONFIG_ULTRA32=m CONFIG_SMC9194=m CONFIG_NET_VENDOR_RACAL=y CONFIG_NI5010=m CONFIG_NI52=m CONFIG_NI65=m # # Tulip family network device support # CONFIG_NET_TULIP=y CONFIG_DE2104X=m CONFIG_TULIP=m # CONFIG_TULIP_MWI is not set # CONFIG_TULIP_MMIO is not set # CONFIG_TULIP_NAPI is not set CONFIG_DE4X5=m CONFIG_WINBOND_840=m CONFIG_DM9102=m CONFIG_AT1700=m CONFIG_DEPCA=m CONFIG_HP100=m CONFIG_NET_ISA=y CONFIG_E2100=m CONFIG_EWRK3=m CONFIG_EEXPRESS=m CONFIG_EEXPRESS_PRO=m CONFIG_HPLAN_PLUS=m CONFIG_HPLAN=m CONFIG_LP486E=m CONFIG_ETH16I=m CONFIG_NE2000=m CONFIG_ZNET=m CONFIG_SEEQ8005=m CONFIG_SKMC=m CONFIG_NE2_MCA=m CONFIG_IBMLANA=m CONFIG_NET_PCI=y CONFIG_PCNET32=m CONFIG_AMD8111_ETH=m CONFIG_AMD8111E_NAPI=y CONFIG_ADAPTEC_STARFIRE=m # CONFIG_ADAPTEC_STARFIRE_NAPI is not set CONFIG_AC3200=m CONFIG_APRICOT=m CONFIG_B44=m CONFIG_FORCEDETH=m CONFIG_CS89x0=m CONFIG_DGRS=m CONFIG_EEPRO100=m CONFIG_E100=m CONFIG_LNE390=m CONFIG_FEALNX=m CONFIG_NATSEMI=m CONFIG_NE2K_PCI=m CONFIG_NE3210=m CONFIG_ES3210=m # CONFIG_8139CP is not set CONFIG_8139TOO=m # CONFIG_8139TOO_PIO is not set CONFIG_8139TOO_TUNE_TWISTER=y CONFIG_8139TOO_8129=y # CONFIG_8139_OLD_RX_RESET is not set CONFIG_SIS900=m CONFIG_EPIC100=m CONFIG_SUNDANCE=m # CONFIG_SUNDANCE_MMIO is not set CONFIG_TLAN=m CONFIG_VIA_RHINE=m CONFIG_VIA_RHINE_MMIO=y CONFIG_NET_POCKET=y CONFIG_ATP=m CONFIG_DE600=m CONFIG_DE620=m # # Ethernet (1000 Mbit) # CONFIG_ACENIC=m # CONFIG_ACENIC_OMIT_TIGON_I is not set CONFIG_DL2K=m CONFIG_E1000=m # CONFIG_E1000_NAPI is not set CONFIG_NS83820=m CONFIG_HAMACHI=m CONFIG_YELLOWFIN=m CONFIG_R8169=m # CONFIG_R8169_NAPI is not set # CONFIG_R8169_VLAN is not set CONFIG_SK98LIN=m # CONFIG_VIA_VELOCITY is not set CONFIG_TIGON3=m # CONFIG_BNX2 is not set # # Ethernet (10000 Mbit) # CONFIG_IXGB=m # CONFIG_IXGB_NAPI is not set CONFIG_S2IO=m # CONFIG_S2IO_NAPI is not set # CONFIG_2BUFF_MODE is not set # # Token Ring devices # CONFIG_TR=y CONFIG_IBMTR=m CONFIG_IBMOL=m CONFIG_IBMLS=m CONFIG_3C359=m CONFIG_TMS380TR=m CONFIG_TMSPCI=m CONFIG_SKISA=m CONFIG_PROTEON=m CONFIG_ABYSS=m CONFIG_MADGEMC=m CONFIG_SMCTR=m # # Wireless LAN (non-hamradio) # CONFIG_NET_RADIO=y # # Obsolete Wireless cards support (pre-802.11) # CONFIG_STRIP=m CONFIG_ARLAN=m CONFIG_WAVELAN=m # # Wireless 802.11b ISA/PCI cards support # CONFIG_AIRO=m CONFIG_HERMES=m CONFIG_PLX_HERMES=m CONFIG_TMD_HERMES=m CONFIG_PCI_HERMES=m CONFIG_ATMEL=m CONFIG_PCI_ATMEL=m # # Prism GT/Duette 802.11(a/b/g) PCI/Cardbus support # CONFIG_PRISM54=m CONFIG_NET_WIRELESS=y # # Wan interfaces # CONFIG_WAN=y CONFIG_HOSTESS_SV11=m CONFIG_COSA=m CONFIG_DSCC4=m CONFIG_DSCC4_PCISYNC=y # CONFIG_DSCC4_PCI_RST is not set CONFIG_LANMEDIA=m CONFIG_SEALEVEL_4021=m CONFIG_SYNCLINK_SYNCPPP=m CONFIG_HDLC=m CONFIG_HDLC_RAW=y CONFIG_HDLC_RAW_ETH=y CONFIG_HDLC_CISCO=y CONFIG_HDLC_FR=y CONFIG_HDLC_PPP=y CONFIG_HDLC_X25=y CONFIG_PCI200SYN=m CONFIG_WANXL=m CONFIG_PC300=m CONFIG_PC300_MLPPP=y CONFIG_N2=m CONFIG_C101=m CONFIG_FARSYNC=m CONFIG_DLCI=m CONFIG_DLCI_COUNT=24 CONFIG_DLCI_MAX=8 CONFIG_SDLA=m CONFIG_WAN_ROUTER_DRIVERS=y CONFIG_VENDOR_SANGOMA=m CONFIG_WANPIPE_CHDLC=y CONFIG_WANPIPE_FR=y CONFIG_WANPIPE_X25=y CONFIG_WANPIPE_PPP=y CONFIG_WANPIPE_MULTPPP=y CONFIG_CYCLADES_SYNC=m CONFIG_CYCLOMX_X25=y CONFIG_LAPBETHER=m CONFIG_X25_ASY=m CONFIG_SBNI=m CONFIG_SBNI_MULTILINE=y # # ATM drivers # CONFIG_ATM_TCP=m CONFIG_ATM_LANAI=m CONFIG_ATM_ENI=m # CONFIG_ATM_ENI_DEBUG is not set CONFIG_ATM_ENI_TUNE_BURST=y # CONFIG_ATM_ENI_BURST_TX_16W is not set CONFIG_ATM_ENI_BURST_TX_8W=y CONFIG_ATM_ENI_BURST_TX_4W=y CONFIG_ATM_ENI_BURST_TX_2W=y # CONFIG_ATM_ENI_BURST_RX_16W is not set # CONFIG_ATM_ENI_BURST_RX_8W is not set CONFIG_ATM_ENI_BURST_RX_4W=y CONFIG_ATM_ENI_BURST_RX_2W=y CONFIG_ATM_FIRESTREAM=m CONFIG_ATM_ZATM=m # CONFIG_ATM_ZATM_DEBUG is not set CONFIG_ATM_NICSTAR=m CONFIG_ATM_NICSTAR_USE_SUNI=y CONFIG_ATM_NICSTAR_USE_IDT77105=y CONFIG_ATM_IDT77252=m # CONFIG_ATM_IDT77252_DEBUG is not set # CONFIG_ATM_IDT77252_RCV_ALL is not set CONFIG_ATM_IDT77252_USE_SUNI=y CONFIG_ATM_AMBASSADOR=m # CONFIG_ATM_AMBASSADOR_DEBUG is not set CONFIG_ATM_HORIZON=m # CONFIG_ATM_HORIZON_DEBUG is not set CONFIG_ATM_IA=m # CONFIG_ATM_IA_DEBUG is not set CONFIG_ATM_FORE200E_MAYBE=m CONFIG_ATM_FORE200E_PCA=y CONFIG_ATM_FORE200E_PCA_DEFAULT_FW=y CONFIG_ATM_FORE200E_USE_TASKLET=y CONFIG_ATM_FORE200E_TX_RETRY=16 CONFIG_ATM_FORE200E_DEBUG=0 CONFIG_ATM_FORE200E=m CONFIG_ATM_HE=m # CONFIG_ATM_HE_USE_SUNI is not set CONFIG_FDDI=y CONFIG_DEFXX=m CONFIG_SKFP=m CONFIG_HIPPI=y CONFIG_ROADRUNNER=m # CONFIG_ROADRUNNER_LARGE_RINGS is not set CONFIG_PPP=m CONFIG_PPP_MULTILINK=y CONFIG_PPP_FILTER=y CONFIG_PPP_ASYNC=m CONFIG_PPP_SYNC_TTY=m CONFIG_PPP_DEFLATE=m CONFIG_PPP_BSDCOMP=m CONFIG_PPPOE=m CONFIG_PPPOATM=m CONFIG_SLIP=m CONFIG_SLIP_COMPRESSED=y CONFIG_SLIP_SMART=y CONFIG_SLIP_MODE_SLIP6=y # CONFIG_NET_FC is not set CONFIG_SHAPER=m CONFIG_NETCONSOLE=m # # ISDN subsystem # # CONFIG_ISDN is not set # # Telephony Support # # CONFIG_PHONE is not set # # Input device support # CONFIG_INPUT=y # # Userland interfaces # CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 CONFIG_INPUT_JOYDEV=m CONFIG_INPUT_TSDEV=m CONFIG_INPUT_TSDEV_SCREEN_X=240 CONFIG_INPUT_TSDEV_SCREEN_Y=320 CONFIG_INPUT_EVDEV=m # CONFIG_INPUT_EVBUG is not set # # Input Device Drivers # CONFIG_INPUT_KEYBOARD=y CONFIG_KEYBOARD_ATKBD=y CONFIG_KEYBOARD_SUNKBD=m CONFIG_KEYBOARD_LKKBD=m CONFIG_KEYBOARD_XTKBD=m CONFIG_KEYBOARD_NEWTON=m CONFIG_INPUT_MOUSE=y CONFIG_MOUSE_PS2=y CONFIG_MOUSE_SERIAL=m CONFIG_MOUSE_INPORT=m # CONFIG_MOUSE_ATIXL is not set CONFIG_MOUSE_LOGIBM=m CONFIG_MOUSE_PC110PAD=m CONFIG_MOUSE_VSXXXAA=m CONFIG_INPUT_JOYSTICK=y CONFIG_JOYSTICK_ANALOG=m CONFIG_JOYSTICK_A3D=m CONFIG_JOYSTICK_ADI=m CONFIG_JOYSTICK_COBRA=m CONFIG_JOYSTICK_GF2K=m CONFIG_JOYSTICK_GRIP=m CONFIG_JOYSTICK_GRIP_MP=m CONFIG_JOYSTICK_GUILLEMOT=m CONFIG_JOYSTICK_INTERACT=m CONFIG_JOYSTICK_SIDEWINDER=m CONFIG_JOYSTICK_TMDC=m CONFIG_JOYSTICK_IFORCE=m CONFIG_JOYSTICK_IFORCE_232=y CONFIG_JOYSTICK_WARRIOR=m CONFIG_JOYSTICK_MAGELLAN=m CONFIG_JOYSTICK_SPACEORB=m CONFIG_JOYSTICK_SPACEBALL=m CONFIG_JOYSTICK_STINGER=m # CONFIG_JOYSTICK_TWIDJOY is not set # CONFIG_JOYSTICK_JOYDUMP is not set CONFIG_INPUT_TOUCHSCREEN=y CONFIG_TOUCHSCREEN_GUNZE=m # CONFIG_TOUCHSCREEN_ELO is not set # CONFIG_TOUCHSCREEN_MTOUCH is not set # CONFIG_TOUCHSCREEN_MK712 is not set CONFIG_INPUT_MISC=y CONFIG_INPUT_PCSPKR=m CONFIG_INPUT_UINPUT=m # # Hardware I/O ports # CONFIG_SERIO=y CONFIG_SERIO_I8042=y CONFIG_SERIO_SERPORT=m CONFIG_SERIO_CT82C710=m CONFIG_SERIO_PCIPS2=m CONFIG_SERIO_LIBPS2=y # CONFIG_SERIO_RAW is not set CONFIG_GAMEPORT=m CONFIG_GAMEPORT_NS558=m CONFIG_GAMEPORT_L4=m CONFIG_GAMEPORT_EMU10K1=m CONFIG_GAMEPORT_VORTEX=m CONFIG_GAMEPORT_FM801=m # CONFIG_GAMEPORT_CS461X is not set # # Character devices # CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_HW_CONSOLE=y CONFIG_SERIAL_NONSTANDARD=y CONFIG_COMPUTONE=m CONFIG_ROCKETPORT=m CONFIG_CYCLADES=m # CONFIG_CYZ_INTR is not set CONFIG_DIGIEPCA=m CONFIG_ESPSERIAL=m CONFIG_MOXA_INTELLIO=m CONFIG_MOXA_SMARTIO=m CONFIG_ISI=m CONFIG_SYNCLINK=m CONFIG_SYNCLINKMP=m CONFIG_N_HDLC=m CONFIG_RISCOM8=m CONFIG_SPECIALIX=m # CONFIG_SPECIALIX_RTSCTS is not set CONFIG_SX=m CONFIG_RIO=m CONFIG_RIO_OLDPCI=y CONFIG_STALDRV=y CONFIG_STALLION=m CONFIG_ISTALLION=m # # Serial drivers # CONFIG_SERIAL_8250=m CONFIG_SERIAL_8250_ACPI=y CONFIG_SERIAL_8250_NR_UARTS=4 # CONFIG_SERIAL_8250_EXTENDED is not set # # Non-8250 serial port support # CONFIG_SERIAL_CORE=m # CONFIG_SERIAL_JSM is not set CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 # # IPMI # CONFIG_IPMI_HANDLER=m # CONFIG_IPMI_PANIC_EVENT is not set CONFIG_IPMI_DEVICE_INTERFACE=m CONFIG_IPMI_SI=m CONFIG_IPMI_WATCHDOG=m # CONFIG_IPMI_POWEROFF is not set # # Watchdog Cards # # CONFIG_WATCHDOG is not set CONFIG_HW_RANDOM=m CONFIG_NVRAM=m CONFIG_RTC=m CONFIG_GEN_RTC=m CONFIG_GEN_RTC_X=y CONFIG_DTLK=m CONFIG_R3964=m CONFIG_APPLICOM=m CONFIG_SONYPI=m # # Ftape, the floppy tape device driver # CONFIG_FTAPE=m CONFIG_ZFTAPE=m CONFIG_ZFT_DFLT_BLK_SZ=10240 # # The compressor will be built as a module only! # CONFIG_ZFT_COMPRESSOR=m CONFIG_FT_NR_BUFFERS=3 CONFIG_FT_PROC_FS=y CONFIG_FT_NORMAL_DEBUG=y # CONFIG_FT_FULL_DEBUG is not set # CONFIG_FT_NO_TRACE is not set # CONFIG_FT_NO_TRACE_AT_ALL is not set # # Hardware configuration # CONFIG_FT_STD_FDC=y # CONFIG_FT_MACH2 is not set # CONFIG_FT_PROBE_FC10 is not set # CONFIG_FT_ALT_FDC is not set CONFIG_FT_FDC_THR=8 CONFIG_FT_FDC_MAX_RATE=2000 CONFIG_FT_ALPHA_CLOCK=0 CONFIG_AGP=m CONFIG_AGP_ALI=m CONFIG_AGP_ATI=m CONFIG_AGP_AMD=m CONFIG_AGP_AMD64=m CONFIG_AGP_INTEL=m CONFIG_AGP_NVIDIA=m CONFIG_AGP_SIS=m CONFIG_AGP_SWORKS=m CONFIG_AGP_VIA=m CONFIG_AGP_EFFICEON=m # CONFIG_DRM is not set # CONFIG_MWAVE is not set CONFIG_SCx200_GPIO=m CONFIG_RAW_DRIVER=m # CONFIG_HPET is not set CONFIG_MAX_RAW_DEVS=256 CONFIG_HANGCHECK_TIMER=m # # TPM devices # # CONFIG_TCG_TPM is not set # # I2C support # CONFIG_I2C=m # CONFIG_I2C_CHARDEV is not set # # I2C Algorithms # CONFIG_I2C_ALGOBIT=m CONFIG_I2C_ALGOPCF=m # CONFIG_I2C_ALGOPCA is not set # # I2C Hardware Bus support # CONFIG_I2C_ALI1535=m CONFIG_I2C_ALI1563=m CONFIG_I2C_ALI15X3=m CONFIG_I2C_AMD756=m # CONFIG_I2C_AMD756_S4882 is not set CONFIG_I2C_AMD8111=m CONFIG_I2C_ELEKTOR=m CONFIG_I2C_I801=m CONFIG_I2C_I810=m CONFIG_I2C_PIIX4=m CONFIG_I2C_ISA=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_PARPORT_LIGHT=m CONFIG_I2C_PROSAVAGE=m CONFIG_I2C_SAVAGE4=m CONFIG_SCx200_I2C=m CONFIG_SCx200_I2C_SCL=12 CONFIG_SCx200_I2C_SDA=13 CONFIG_SCx200_ACB=m CONFIG_I2C_SIS5595=m CONFIG_I2C_SIS630=m CONFIG_I2C_SIS96X=m # CONFIG_I2C_STUB is not set CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m CONFIG_I2C_VOODOO3=m # CONFIG_I2C_PCA_ISA is not set # # Hardware Sensors Chip support # CONFIG_I2C_SENSOR=m CONFIG_SENSORS_ADM1021=m # CONFIG_SENSORS_ADM1025 is not set # CONFIG_SENSORS_ADM1026 is not set # CONFIG_SENSORS_ADM1031 is not set CONFIG_SENSORS_ASB100=m CONFIG_SENSORS_DS1621=m CONFIG_SENSORS_FSCHER=m # CONFIG_SENSORS_FSCPOS is not set CONFIG_SENSORS_GL518SM=m # CONFIG_SENSORS_GL520SM is not set CONFIG_SENSORS_IT87=m # CONFIG_SENSORS_LM63 is not set CONFIG_SENSORS_LM75=m # CONFIG_SENSORS_LM77 is not set CONFIG_SENSORS_LM78=m CONFIG_SENSORS_LM80=m CONFIG_SENSORS_LM83=m CONFIG_SENSORS_LM85=m # CONFIG_SENSORS_LM87 is not set CONFIG_SENSORS_LM90=m # CONFIG_SENSORS_LM92 is not set CONFIG_SENSORS_MAX1619=m # CONFIG_SENSORS_PC87360 is not set # CONFIG_SENSORS_SMSC47B397 is not set # CONFIG_SENSORS_SIS5595 is not set # CONFIG_SENSORS_SMSC47M1 is not set CONFIG_SENSORS_VIA686A=m CONFIG_SENSORS_W83781D=m CONFIG_SENSORS_W83L785TS=m CONFIG_SENSORS_W83627HF=m # # Other I2C Chip support # # CONFIG_SENSORS_DS1337 is not set CONFIG_SENSORS_EEPROM=m CONFIG_SENSORS_PCF8574=m CONFIG_SENSORS_PCF8591=m CONFIG_SENSORS_RTC8564=m # CONFIG_I2C_DEBUG_CORE is not set # CONFIG_I2C_DEBUG_ALGO is not set # CONFIG_I2C_DEBUG_BUS is not set # CONFIG_I2C_DEBUG_CHIP is not set # # Dallas's 1-wire bus # # CONFIG_W1 is not set # # Misc devices # # CONFIG_IBM_ASM is not set # # Multimedia devices # CONFIG_VIDEO_DEV=m # # Video For Linux # # # Video Adapters # CONFIG_VIDEO_BT848=m CONFIG_VIDEO_PMS=m CONFIG_VIDEO_CPIA=m CONFIG_VIDEO_SAA5246A=m CONFIG_VIDEO_SAA5249=m CONFIG_TUNER_3036=m CONFIG_VIDEO_STRADIS=m CONFIG_VIDEO_ZORAN=m CONFIG_VIDEO_ZORAN_BUZ=m CONFIG_VIDEO_ZORAN_DC10=m CONFIG_VIDEO_ZORAN_DC30=m CONFIG_VIDEO_ZORAN_LML33=m CONFIG_VIDEO_ZORAN_LML33R10=m # CONFIG_VIDEO_ZR36120 is not set CONFIG_VIDEO_MEYE=m CONFIG_VIDEO_SAA7134=m # CONFIG_VIDEO_SAA7134_DVB is not set CONFIG_VIDEO_MXB=m CONFIG_VIDEO_DPC=m CONFIG_VIDEO_HEXIUM_ORION=m CONFIG_VIDEO_HEXIUM_GEMINI=m CONFIG_VIDEO_CX88=m # CONFIG_VIDEO_CX88_DVB is not set # CONFIG_VIDEO_OVCAMCHIP is not set # # Radio Adapters # CONFIG_RADIO_CADET=m CONFIG_RADIO_RTRACK=m CONFIG_RADIO_RTRACK2=m CONFIG_RADIO_AZTECH=m CONFIG_RADIO_GEMTEK=m CONFIG_RADIO_GEMTEK_PCI=m CONFIG_RADIO_MAXIRADIO=m CONFIG_RADIO_MAESTRO=m CONFIG_RADIO_SF16FMI=m CONFIG_RADIO_SF16FMR2=m CONFIG_RADIO_TERRATEC=m CONFIG_RADIO_TRUST=m CONFIG_RADIO_TYPHOON=m CONFIG_RADIO_TYPHOON_PROC_FS=y CONFIG_RADIO_ZOLTRIX=m # # Digital Video Broadcasting Devices # CONFIG_DVB=y CONFIG_DVB_CORE=m # # Supported SAA7146 based PCI Adapters # CONFIG_DVB_AV7110=m CONFIG_DVB_AV7110_OSD=y CONFIG_DVB_BUDGET=m CONFIG_DVB_BUDGET_CI=m CONFIG_DVB_BUDGET_AV=m CONFIG_DVB_BUDGET_PATCH=m # # Supported FlexCopII (B2C2) Adapters # # CONFIG_DVB_B2C2_FLEXCOP is not set CONFIG_DVB_B2C2_SKYSTAR=m # # Supported BT878 Adapters # CONFIG_DVB_BT8XX=m # # Supported DVB Frontends # # # Customise DVB Frontends # # # DVB-S (satellite) frontends # CONFIG_DVB_STV0299=m CONFIG_DVB_CX24110=m CONFIG_DVB_TDA8083=m # CONFIG_DVB_TDA80XX is not set CONFIG_DVB_MT312=m CONFIG_DVB_VES1X93=m # # DVB-T (terrestrial) frontends # CONFIG_DVB_SP8870=m CONFIG_DVB_SP887X=m CONFIG_DVB_CX22700=m # CONFIG_DVB_CX22702 is not set CONFIG_DVB_L64781=m CONFIG_DVB_TDA1004X=m CONFIG_DVB_NXT6000=m CONFIG_DVB_MT352=m # CONFIG_DVB_DIB3000MB is not set # CONFIG_DVB_DIB3000MC is not set # # DVB-C (cable) frontends # CONFIG_DVB_ATMEL_AT76C651=m CONFIG_DVB_VES1820=m CONFIG_DVB_TDA10021=m CONFIG_DVB_STV0297=m # # ATSC (North American/Korean Terresterial DTV) frontends # CONFIG_DVB_NXT2002=m CONFIG_DVB_OR51211=m # CONFIG_DVB_OR51132 is not set CONFIG_VIDEO_SAA7146=m CONFIG_VIDEO_SAA7146_VV=m CONFIG_VIDEO_VIDEOBUF=m CONFIG_VIDEO_TUNER=m CONFIG_VIDEO_BUF=m CONFIG_VIDEO_BTCX=m CONFIG_VIDEO_IR=m CONFIG_VIDEO_TVEEPROM=m # # Graphics support # # CONFIG_FB is not set # CONFIG_VIDEO_SELECT is not set # # Console display driver support # CONFIG_VGA_CONSOLE=y # CONFIG_MDA_CONSOLE is not set CONFIG_DUMMY_CONSOLE=y # # Sound # # CONFIG_SOUND is not set # # USB support # CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y # CONFIG_USB is not set # # USB Gadget Support # # CONFIG_USB_GADGET is not set # # MMC/SD Card support # # CONFIG_MMC is not set # # InfiniBand support # # CONFIG_INFINIBAND is not set # # File systems # CONFIG_EXT2_FS=y CONFIG_EXT2_FS_XATTR=y CONFIG_EXT2_FS_POSIX_ACL=y CONFIG_EXT2_FS_SECURITY=y CONFIG_EXT3_FS=m CONFIG_EXT3_FS_XATTR=y CONFIG_EXT3_FS_POSIX_ACL=y CONFIG_EXT3_FS_SECURITY=y CONFIG_JBD=m CONFIG_JBD_DEBUG=y CONFIG_FS_MBCACHE=y CONFIG_REISERFS_FS=m # CONFIG_REISERFS_CHECK is not set # CONFIG_REISERFS_PROC_INFO is not set CONFIG_REISERFS_FS_XATTR=y CONFIG_REISERFS_FS_POSIX_ACL=y CONFIG_REISERFS_FS_SECURITY=y CONFIG_JFS_FS=m CONFIG_JFS_POSIX_ACL=y # CONFIG_JFS_SECURITY is not set # CONFIG_JFS_DEBUG is not set CONFIG_JFS_STATISTICS=y CONFIG_FS_POSIX_ACL=y CONFIG_XFS_FS=m CONFIG_XFS_EXPORT=y CONFIG_XFS_QUOTA=m CONFIG_XFS_DMAPI=y CONFIG_XFS_SECURITY=y CONFIG_XFS_POSIX_ACL=y CONFIG_XFS_RT=y CONFIG_XFS_DEBUG=y CONFIG_XFS_TRACE=y CONFIG_MINIX_FS=m CONFIG_ROMFS_FS=m CONFIG_DMAPI=m # CONFIG_DMAPI_DEBUG is not set CONFIG_QUOTA=y CONFIG_QFMT_V1=m CONFIG_QFMT_V2=m CONFIG_QUOTACTL=y CONFIG_DNOTIFY=y CONFIG_AUTOFS_FS=m CONFIG_AUTOFS4_FS=m # # CD-ROM/DVD Filesystems # CONFIG_ISO9660_FS=y CONFIG_JOLIET=y CONFIG_ZISOFS=y CONFIG_ZISOFS_FS=y CONFIG_UDF_FS=m CONFIG_UDF_NLS=y # # DOS/FAT/NT Filesystems # CONFIG_FAT_FS=y CONFIG_MSDOS_FS=m CONFIG_VFAT_FS=y CONFIG_FAT_DEFAULT_CODEPAGE=437 CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1" CONFIG_NTFS_FS=m # CONFIG_NTFS_DEBUG is not set CONFIG_NTFS_RW=y # # Pseudo filesystems # CONFIG_PROC_FS=y CONFIG_PROC_KCORE=y CONFIG_SYSFS=y # CONFIG_DEVFS_FS is not set # CONFIG_DEVPTS_FS_XATTR is not set CONFIG_TMPFS=y # CONFIG_TMPFS_XATTR is not set CONFIG_HUGETLBFS=y CONFIG_HUGETLB_PAGE=y CONFIG_RAMFS=y # # Miscellaneous filesystems # CONFIG_ADFS_FS=m CONFIG_ADFS_FS_RW=y CONFIG_AFFS_FS=m CONFIG_HFS_FS=m CONFIG_HFSPLUS_FS=m CONFIG_BEFS_FS=m # CONFIG_BEFS_DEBUG is not set CONFIG_BFS_FS=m CONFIG_EFS_FS=m CONFIG_JFFS_FS=m CONFIG_JFFS_FS_VERBOSE=0 # CONFIG_JFFS_PROC_FS is not set CONFIG_JFFS2_FS=m CONFIG_JFFS2_FS_DEBUG=0 CONFIG_JFFS2_FS_NAND=y # CONFIG_JFFS2_FS_NOR_ECC is not set # CONFIG_JFFS2_COMPRESSION_OPTIONS is not set CONFIG_JFFS2_ZLIB=y CONFIG_JFFS2_RTIME=y # CONFIG_JFFS2_RUBIN is not set CONFIG_CRAMFS=m CONFIG_VXFS_FS=m CONFIG_HPFS_FS=m CONFIG_QNX4FS_FS=m CONFIG_QNX4FS_RW=y CONFIG_SYSV_FS=m CONFIG_UFS_FS=m CONFIG_UFS_FS_WRITE=y # # Network File Systems # CONFIG_NFS_FS=m CONFIG_NFS_V3=y CONFIG_NFS_V4=y CONFIG_NFS_DIRECTIO=y CONFIG_NFSD=m CONFIG_NFSD_V3=y CONFIG_NFSD_V4=y CONFIG_NFSD_TCP=y CONFIG_LOCKD=m CONFIG_LOCKD_V4=y CONFIG_EXPORTFS=m CONFIG_SUNRPC=m CONFIG_SUNRPC_GSS=m CONFIG_RPCSEC_GSS_KRB5=m # CONFIG_RPCSEC_GSS_SPKM3 is not set CONFIG_SMB_FS=m # CONFIG_SMB_NLS_DEFAULT is not set CONFIG_CIFS=m # CONFIG_CIFS_STATS is not set # CONFIG_CIFS_XATTR is not set # CONFIG_CIFS_EXPERIMENTAL is not set CONFIG_NCP_FS=m CONFIG_NCPFS_PACKET_SIGNING=y CONFIG_NCPFS_IOCTL_LOCKING=y CONFIG_NCPFS_STRONG=y CONFIG_NCPFS_NFS_NS=y CONFIG_NCPFS_OS2_NS=y CONFIG_NCPFS_SMALLDOS=y CONFIG_NCPFS_NLS=y CONFIG_NCPFS_EXTRAS=y CONFIG_CODA_FS=m # CONFIG_CODA_FS_OLD_API is not set CONFIG_AFS_FS=m CONFIG_RXRPC=m # # Partition Types # CONFIG_PARTITION_ADVANCED=y # CONFIG_ACORN_PARTITION is not set CONFIG_OSF_PARTITION=y CONFIG_AMIGA_PARTITION=y CONFIG_ATARI_PARTITION=y CONFIG_MAC_PARTITION=y CONFIG_MSDOS_PARTITION=y CONFIG_BSD_DISKLABEL=y CONFIG_MINIX_SUBPARTITION=y CONFIG_SOLARIS_X86_PARTITION=y CONFIG_UNIXWARE_DISKLABEL=y CONFIG_LDM_PARTITION=y # CONFIG_LDM_DEBUG is not set CONFIG_SGI_PARTITION=y CONFIG_ULTRIX_PARTITION=y CONFIG_SUN_PARTITION=y # CONFIG_EFI_PARTITION is not set # # Native Language Support # CONFIG_NLS=y CONFIG_NLS_DEFAULT="iso8859-1" CONFIG_NLS_CODEPAGE_437=m CONFIG_NLS_CODEPAGE_737=m CONFIG_NLS_CODEPAGE_775=m CONFIG_NLS_CODEPAGE_850=m CONFIG_NLS_CODEPAGE_852=m CONFIG_NLS_CODEPAGE_855=m CONFIG_NLS_CODEPAGE_857=m CONFIG_NLS_CODEPAGE_860=m CONFIG_NLS_CODEPAGE_861=m CONFIG_NLS_CODEPAGE_862=m CONFIG_NLS_CODEPAGE_863=m CONFIG_NLS_CODEPAGE_864=m CONFIG_NLS_CODEPAGE_865=m CONFIG_NLS_CODEPAGE_866=m CONFIG_NLS_CODEPAGE_869=m CONFIG_NLS_CODEPAGE_936=m CONFIG_NLS_CODEPAGE_950=m CONFIG_NLS_CODEPAGE_932=m CONFIG_NLS_CODEPAGE_949=m CONFIG_NLS_CODEPAGE_874=m CONFIG_NLS_ISO8859_8=m CONFIG_NLS_CODEPAGE_1250=m CONFIG_NLS_CODEPAGE_1251=m # CONFIG_NLS_ASCII is not set CONFIG_NLS_ISO8859_1=m CONFIG_NLS_ISO8859_2=m CONFIG_NLS_ISO8859_3=m CONFIG_NLS_ISO8859_4=m CONFIG_NLS_ISO8859_5=m CONFIG_NLS_ISO8859_6=m CONFIG_NLS_ISO8859_7=m CONFIG_NLS_ISO8859_9=m CONFIG_NLS_ISO8859_13=m CONFIG_NLS_ISO8859_14=m CONFIG_NLS_ISO8859_15=m CONFIG_NLS_KOI8_R=m CONFIG_NLS_KOI8_U=m CONFIG_NLS_UTF8=m # # Profiling support # # CONFIG_PROFILING is not set # # Kernel hacking # # CONFIG_PRINTK_TIME is not set CONFIG_DEBUG_KERNEL=y CONFIG_MAGIC_SYSRQ=y CONFIG_LOG_BUF_SHIFT=15 # CONFIG_SCHEDSTATS is not set # CONFIG_DEBUG_SLAB is not set CONFIG_DEBUG_PREEMPT=y # CONFIG_DEBUG_SPINLOCK is not set # CONFIG_DEBUG_SPINLOCK_SLEEP is not set # CONFIG_DEBUG_KOBJECT is not set # CONFIG_DEBUG_HIGHMEM is not set CONFIG_DEBUG_BUGVERBOSE=y # CONFIG_DEBUG_INFO is not set # CONFIG_DEBUG_FS is not set # CONFIG_FRAME_POINTER is not set CONFIG_EARLY_PRINTK=y # CONFIG_DEBUG_STACKOVERFLOW is not set # CONFIG_KPROBES is not set # CONFIG_DEBUG_STACK_USAGE is not set # # Page alloc debug is incompatible with Software Suspend on i386 # # CONFIG_4KSTACKS is not set CONFIG_X86_FIND_SMP_CONFIG=y CONFIG_X86_MPPARSE=y # CONFIG_KDB is not set # # Security options # # CONFIG_KEYS is not set # CONFIG_SECURITY is not set # # Cryptographic options # CONFIG_CRYPTO=y CONFIG_CRYPTO_HMAC=y # CONFIG_CRYPTO_NULL is not set # CONFIG_CRYPTO_MD4 is not set CONFIG_CRYPTO_MD5=m CONFIG_CRYPTO_SHA1=m # CONFIG_CRYPTO_SHA256 is not set # CONFIG_CRYPTO_SHA512 is not set # CONFIG_CRYPTO_WP512 is not set # CONFIG_CRYPTO_TGR192 is not set CONFIG_CRYPTO_DES=m # CONFIG_CRYPTO_BLOWFISH is not set # CONFIG_CRYPTO_TWOFISH is not set # CONFIG_CRYPTO_SERPENT is not set # CONFIG_CRYPTO_AES_586 is not set # CONFIG_CRYPTO_CAST5 is not set # CONFIG_CRYPTO_CAST6 is not set # CONFIG_CRYPTO_TEA is not set # CONFIG_CRYPTO_ARC4 is not set # CONFIG_CRYPTO_KHAZAD is not set # CONFIG_CRYPTO_ANUBIS is not set CONFIG_CRYPTO_DEFLATE=m # CONFIG_CRYPTO_MICHAEL_MIC is not set # CONFIG_CRYPTO_CRC32C is not set # CONFIG_CRYPTO_TEST is not set # # Hardware crypto devices # # CONFIG_CRYPTO_DEV_PADLOCK is not set # # Library routines # CONFIG_CRC_CCITT=m CONFIG_CRC32=y CONFIG_LIBCRC32C=m CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_IRQ_PROBE=y CONFIG_X86_SMP=y CONFIG_X86_HT=y CONFIG_X86_BIOS_REBOOT=y CONFIG_X86_TRAMPOLINE=y CONFIG_PC=y --tKW2IUtsqtDRztdT-- From owner-linux-xfs@oss.sgi.com Fri Aug 26 00:18:42 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 00:18:46 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7Q7IeiL023862 for ; Fri, 26 Aug 2005 00:18:41 -0700 Received: by zproxy.gmail.com with SMTP id m22so276165nzf for ; Fri, 26 Aug 2005 00:16:17 -0700 (PDT) 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:content-transfer-encoding:content-disposition; b=H1aqn3oxnUgtd3WJnFVKpvL4095aa0uJP7bGGThD+exy3OPl7XiL+nxhxgX4kHlOy7dZPOX0UZVE5MFPVHukhg6scp24miZBm8ierYyPXxn4Pth0crWrW8Hjed5IrdkMXJ3luSff1uLriJnVkQfauhpuj6277ijAtet3TW0uZBE= Received: by 10.36.215.10 with SMTP id n10mr216089nzg; Fri, 26 Aug 2005 00:16:16 -0700 (PDT) Received: by 10.37.12.27 with HTTP; Fri, 26 Aug 2005 00:16:16 -0700 (PDT) Message-ID: <4f52331f050826001612f8e323@mail.gmail.com> Date: Fri, 26 Aug 2005 00:16:16 -0700 From: Fong Vang To: linux-xfs@oss.sgi.com Subject: file system defragmentation Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7Q7IgiL023864 X-archive-position: 5960 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sudoyang@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 320 Lines: 8 I've read in many places that file systems on Linux do not suffer the same fragmentation problems of Windows systems. No one has provided a clear explanation as to why fragmentation is not an issue for file systems such as XFS. Also, is there a way to determine the percentage of fragmentation on an XFS file system? From owner-linux-xfs@oss.sgi.com Fri Aug 26 02:56:09 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 02:56:12 -0700 (PDT) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7Q9u7iL010956 for ; Fri, 26 Aug 2005 02:56:08 -0700 Received: from yourf8dc21866e (c220-237-101-11.carlnfd3.nsw.optusnet.com.au [220.237.101.11]) by mail23.syd.optusnet.com.au (8.12.11/8.12.11) with SMTP id j7Q9rh8w011537 for ; Fri, 26 Aug 2005 19:53:43 +1000 Message-ID: <000601c5aa24$0b7f8be0$0b65eddc@yourf8dc21866e> From: "Bassam Batshon" To: Subject: Date: Fri, 26 Aug 2005 19:53:43 +1000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5961 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bbatshon@optusnet.com.au Precedence: bulk X-list: linux-xfs Content-Length: 64 Lines: 4 is XFS faster than reiser4 [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Fri Aug 26 03:13:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 03:14:05 -0700 (PDT) Received: from sommereik.ii.uib.no (sommereik.ii.uib.no [129.177.16.236]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7QADwiL013005 for ; Fri, 26 Aug 2005 03:13:59 -0700 Received: from loko.ii.uib.no ([129.177.20.21]:37146) by sommereik.ii.uib.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1E8bBO-0002oN-7p; Fri, 26 Aug 2005 12:11:34 +0200 Received: (from janfrode@localhost) by loko.ii.uib.no (8.12.11/8.12.11/Submit) id j7QABVRc024692; Fri, 26 Aug 2005 12:11:31 +0200 Date: Fri, 26 Aug 2005 12:11:31 +0200 From: Jan-Frode Myklebust To: Fong Vang Cc: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation Message-ID: <20050826101131.GA24544@ii.uib.no> References: <4f52331f050826001612f8e323@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4f52331f050826001612f8e323@mail.gmail.com> X-archive-position: 5962 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Jan-Frode.Myklebust@bccs.uib.no Precedence: bulk X-list: linux-xfs Content-Length: 1445 Lines: 48 On Fri, Aug 26, 2005 at 12:16:16AM -0700, Fong Vang wrote: > I've read in many places that file systems on Linux do not suffer the > same fragmentation problems of Windows systems. No one has provided a > clear explanation as to why fragmentation is not an issue for file > systems such as XFS. I think it is a problem for XFS also.. at least for our slow growing mailserver with lots of mbox-files. > Also, is there a way to determine the percentage of fragmentation on > an XFS file system? # xfs_db -c frag -r /dev/sdc1 actual 59707, ideal 46970, fragmentation factor 21.33% and individual file fragmentation can be checked with xfs_bmap: # xfs_bmap usersmbox usersmbox: 0: [0..744815]: 31464808..32209623 1: [744816..744831]: 31464792..31464807 2: [744832..744959]: 31464664..31464791 3: [744960..745063]: 31464048..31464151 4: [745064..745215]: 31463896..31464047 5: [745216..745335]: 31463768..31463887 6: [745336..745471]: 31463632..31463767 7: [745472..745583]: 31463504..31463615 and you can defrag either individual files: # xfs_fsr usersmbox # xfs_bmap usersmbox usersmbox: 0: [0..747423]: 142372792..143120215 or a whole live partiion: # xfs_fsr /dev/sdc1 (btw: i think xfs_db -c frag will be a bit slow in reporting the updated fragmentation after a xfs_fsr, at least that's the impression I got the last time I ran it) -jf From owner-linux-xfs@oss.sgi.com Fri Aug 26 08:03:46 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 08:03:49 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc13.comcast.net [216.148.227.118]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7QF3jiL006622 for ; Fri, 26 Aug 2005 08:03:46 -0700 Received: from doctorno.local (c-24-22-219-79.hsd1.wa.comcast.net[24.22.219.79]) by comcast.net (rwcrmhc13) with ESMTP id <20050826150050015009p407e>; Fri, 26 Aug 2005 15:00:51 +0000 Received: from goldfinger.local (goldfinger.local [10.0.0.20]) by doctorno.local (8.13.3/8.13.3) with ESMTP id j7QF0m2T005765; Fri, 26 Aug 2005 08:00:48 -0700 (PDT) (envelope-from dgs@doctorno.local) Received: from goldfinger.local (localhost [127.0.0.1]) by goldfinger.local (8.12.11/8.12.11) with ESMTP id j7QF4UbA018897; Fri, 26 Aug 2005 08:04:30 -0700 (PDT) Received: (from dgs@localhost) by goldfinger.local (8.12.11/8.12.11) id j7QF4SqF025483; Fri, 26 Aug 2005 08:04:28 -0700 (PDT) Date: Fri, 26 Aug 2005 08:04:28 -0700 From: DGS To: Bassam Batshon Cc: linux-xfs@oss.sgi.com Subject: Re: your mail Message-ID: <20050826150428.GA11719@goldfinger.local> References: <000601c5aa24$0b7f8be0$0b65eddc@yourf8dc21866e> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000601c5aa24$0b7f8be0$0b65eddc@yourf8dc21866e> User-Agent: Mutt/1.5.6i X-archive-position: 5965 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgs@gs.washington.edu Precedence: bulk X-list: linux-xfs Content-Length: 370 Lines: 15 On Fri, Aug 26, 2005 at 07:53:43PM +1000, Bassam Batshon wrote: > is XFS faster than reiser4 > Of course! Compare: XFS - three letters ReiserFS - eight letters So XFS is 37.5% faster to write and say. Indeed, XFS is faster than EXT2 or EXT3, but only just as compared to JFS. ReiserFS turns out to be the slowest of the commonly used Linux file systems dgs From owner-linux-xfs@oss.sgi.com Fri Aug 26 08:51:12 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 08:51:19 -0700 (PDT) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.207]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7QFpAiL014965 for ; Fri, 26 Aug 2005 08:51:11 -0700 Received: by zproxy.gmail.com with SMTP id m22so318253nzf for ; Fri, 26 Aug 2005 08:48:47 -0700 (PDT) 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=cDy4XLOoeidz9MyGo/94YKkABWUb7A+5pRVziJ/iVbIkIZas0QwuqZp+nCIGZU40wUUpqFsoaw5oVc31m6gZC0COVT/vKxXcSBu1uB3ynFRaOHaulwKz8OTUWmhUOsLHuToW/2wjftzK7hLVcVo1Wjs2LOnYY/lxM+1hQp/PTtU= Received: by 10.36.57.2 with SMTP id f2mr263130nza; Fri, 26 Aug 2005 08:48:47 -0700 (PDT) Received: by 10.37.12.27 with HTTP; Fri, 26 Aug 2005 08:48:47 -0700 (PDT) Message-ID: <4f52331f0508260848782f240a@mail.gmail.com> Date: Fri, 26 Aug 2005 08:48:47 -0700 From: Fong Vang To: Jan-Frode Myklebust Subject: Re: file system defragmentation Cc: linux-xfs@oss.sgi.com In-Reply-To: <20050826101131.GA24544@ii.uib.no> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <4f52331f050826001612f8e323@mail.gmail.com> <20050826101131.GA24544@ii.uib.no> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7QFpCiL014973 X-archive-position: 5966 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sudoyang@gmail.com Precedence: bulk X-list: linux-xfs Content-Length: 1666 Lines: 51 On 8/26/05, Jan-Frode Myklebust wrote: > On Fri, Aug 26, 2005 at 12:16:16AM -0700, Fong Vang wrote: > > I've read in many places that file systems on Linux do not suffer the > > same fragmentation problems of Windows systems. No one has provided a > > clear explanation as to why fragmentation is not an issue for file > > systems such as XFS. > > > I think it is a problem for XFS also.. at least for our slow growing > mailserver with lots of mbox-files. > > > > Also, is there a way to determine the percentage of fragmentation on > > an XFS file system? > > # xfs_db -c frag -r /dev/sdc1 > actual 59707, ideal 46970, fragmentation factor 21.33% > > and individual file fragmentation can be checked with xfs_bmap: > > # xfs_bmap usersmbox > usersmbox: > 0: [0..744815]: 31464808..32209623 > 1: [744816..744831]: 31464792..31464807 > 2: [744832..744959]: 31464664..31464791 > 3: [744960..745063]: 31464048..31464151 > 4: [745064..745215]: 31463896..31464047 > 5: [745216..745335]: 31463768..31463887 > 6: [745336..745471]: 31463632..31463767 > 7: [745472..745583]: 31463504..31463615 > > and you can defrag either individual files: > > # xfs_fsr usersmbox > # xfs_bmap usersmbox > usersmbox: > 0: [0..747423]: 142372792..143120215 > > or a whole live partiion: > > # xfs_fsr /dev/sdc1 > > (btw: i think xfs_db -c frag will be a bit slow in reporting the updated > fragmentation after a xfs_fsr, at least that's the impression I got > the last time I ran it) This is very useful. Thank you. How stable is xfs_fsr? > -jf > From owner-linux-xfs@oss.sgi.com Fri Aug 26 09:16:47 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 09:16:50 -0700 (PDT) Received: from julesburg.uits.indiana.edu (julesburg.uits.indiana.edu [129.79.1.75]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7QGGkiL017241 for ; Fri, 26 Aug 2005 09:16:47 -0700 Received: from iu-mssg-smtp04.ads.iu.edu (iu-mssg-smtp04.exchange.iu.edu [129.79.1.223]) by julesburg.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id j7QGELFL000351 for ; Fri, 26 Aug 2005 11:14:22 -0500 (EST) Received: from iu-mssg-mbx09.ads.iu.edu ([129.79.1.238]) by iu-mssg-smtp04.ads.iu.edu with Microsoft SMTPSVC(5.0.2195.6713); Fri, 26 Aug 2005 11:14:21 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Subject: RE: your mail Date: Fri, 26 Aug 2005 11:14:21 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: your mail Thread-Index: AcWqTxFy6zYqsHT5TrOhJYmovsKXvgACPTLl From: "Wilkins, Vern" Cc: X-OriginalArrivalTime: 26 Aug 2005 16:14:21.0519 (UTC) FILETIME=[37D11DF0:01C5AA59] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7QGGliL017247 X-archive-position: 5967 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vwilkins@indiana.edu Precedence: bulk X-list: linux-xfs Content-Length: 1440 Lines: 33 I ran a huge number of benchmarks a while back and found reiser4 to be faster than xfs on many, if not most tests I ran. There were a few instances where I found xfs to be slightly faster, but many more instances where reiser4 was a lot faster (mostly on various size deletes if I remember right). I don't think I still have all the results around but I did some pretty extensive comparisons betweeen jfs, xfs, reiser4, reiser3 and ext3. jfs and xfs did come out very close in all my tests also, with jfs showing exceptionally low cpu utilization. Reiser3 and Reiser4 did show higher cpu utilization on almost all my tests. Even though I found reiser4 to be faster, I still prefer xfs for it's stability, ease of use (it's been in the vanilla kernel for a long time), the options such as security labels and acl support, and the ability to defrag with the open-source utilities. -----Original Message----- From: linux-xfs-bounce@oss.sgi.com on behalf of DGS Sent: Fri 8/26/2005 10:04 AM To: Bassam Batshon Cc: linux-xfs@oss.sgi.com Subject: Re: your mail On Fri, Aug 26, 2005 at 07:53:43PM +1000, Bassam Batshon wrote: > is XFS faster than reiser4 > Of course! Compare: XFS - three letters ReiserFS - eight letters So XFS is 37.5% faster to write and say. Indeed, XFS is faster than EXT2 or EXT3, but only just as compared to JFS. ReiserFS turns out to be the slowest of the commonly used Linux file systems dgs From owner-linux-xfs@oss.sgi.com Fri Aug 26 09:22:18 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Aug 2005 09:22:24 -0700 (PDT) Received: from rockridge.uits.indiana.edu (rockridge.uits.indiana.edu [129.79.1.74]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7QGMHiL018138 for ; Fri, 26 Aug 2005 09:22:18 -0700 Received: from iu-mssg-smtp04.ads.iu.edu (iu-mssg-smtp04.exchange.iu.edu [129.79.1.223]) by rockridge.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id j7QGJeAP014843 for ; Fri, 26 Aug 2005 11:19:51 -0500 (EST) Received: from iu-mssg-mbx09.ads.iu.edu ([129.79.1.238]) by iu-mssg-smtp04.ads.iu.edu with Microsoft SMTPSVC(5.0.2195.6713); Fri, 26 Aug 2005 11:19:52 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Subject: RE: file system defragmentation Date: Fri, 26 Aug 2005 11:19:52 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: file system defragmentation Thread-Index: AcWqVbmBVTGYpCZNRf2WLdsWanmsuQAA5CiT From: "Wilkins, Vern" Cc: X-OriginalArrivalTime: 26 Aug 2005 16:19:52.0539 (UTC) FILETIME=[FD1EC2B0:01C5AA59] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7QGMIiL018140 X-archive-position: 5968 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vwilkins@indiana.edu Precedence: bulk X-list: linux-xfs Content-Length: 2526 Lines: 67 I agree, all the talk of certain filesystems not needing defragmentation (not just XFS), is all just talk. In the real world I have seen heavy defragmentation on all my machines, regardless of filesystem. All it takes is a limited amount of freespace and/or a lot of file creation/deletion. Mail servers as already mentioned are a good example of the heavy file creation/deletion scenario, as are audio/video editing workstations. On a/v editing workstations I have seen greater than 90% fragmentation in a fairly short time using virtually any filesystem. The ability to easily defrag XFS is pretty significant in my choice of filesystems. -----Original Message----- From: linux-xfs-bounce@oss.sgi.com on behalf of Fong Vang Sent: Fri 8/26/2005 10:48 AM To: Jan-Frode Myklebust Cc: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation On 8/26/05, Jan-Frode Myklebust wrote: > On Fri, Aug 26, 2005 at 12:16:16AM -0700, Fong Vang wrote: > > I've read in many places that file systems on Linux do not suffer the > > same fragmentation problems of Windows systems. No one has provided a > > clear explanation as to why fragmentation is not an issue for file > > systems such as XFS. > > > I think it is a problem for XFS also.. at least for our slow growing > mailserver with lots of mbox-files. > > > > Also, is there a way to determine the percentage of fragmentation on > > an XFS file system? > > # xfs_db -c frag -r /dev/sdc1 > actual 59707, ideal 46970, fragmentation factor 21.33% > > and individual file fragmentation can be checked with xfs_bmap: > > # xfs_bmap usersmbox > usersmbox: > 0: [0..744815]: 31464808..32209623 > 1: [744816..744831]: 31464792..31464807 > 2: [744832..744959]: 31464664..31464791 > 3: [744960..745063]: 31464048..31464151 > 4: [745064..745215]: 31463896..31464047 > 5: [745216..745335]: 31463768..31463887 > 6: [745336..745471]: 31463632..31463767 > 7: [745472..745583]: 31463504..31463615 > > and you can defrag either individual files: > > # xfs_fsr usersmbox > # xfs_bmap usersmbox > usersmbox: > 0: [0..747423]: 142372792..143120215 > > or a whole live partiion: > > # xfs_fsr /dev/sdc1 > > (btw: i think xfs_db -c frag will be a bit slow in reporting the updated > fragmentation after a xfs_fsr, at least that's the impression I got > the last time I ran it) This is very useful. Thank you. How stable is xfs_fsr? > -jf > From owner-linux-xfs@oss.sgi.com Sat Aug 27 13:44:47 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 27 Aug 2005 13:44:51 -0700 (PDT) Received: from smtp110.mail.sc5.yahoo.com (smtp110.mail.sc5.yahoo.com [66.163.170.8]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7RKiliL018243 for ; Sat, 27 Aug 2005 13:44:47 -0700 Received: (qmail 78365 invoked from network); 27 Aug 2005 20:42:22 -0000 Received: from unknown (HELO ?192.168.1.64?) (thebs413@67.65.154.138 with login) by smtp110.mail.sc5.yahoo.com with SMTP; 27 Aug 2005 20:42:22 -0000 Subject: Will we ever see XFS supported in Red Hat Enterprise Linux? From: "Bryan J. Smith" To: linux-xfs@oss.sgi.com Content-Type: text/plain Date: Sat, 27 Aug 2005 15:46:09 -0500 Message-Id: <1125175569.4518.94.camel@bert64.mobile.smithconcepts.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-6) Content-Transfer-Encoding: 7bit X-archive-position: 5973 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 2314 Lines: 44 I know this is not a Red Hat support list and SGI can't speak for Red Hat. But after several years, let alone the release of kernel 2.6 with XFS support, I'm still scratching my head on why XFS is not being offered in Red Hat Enterprise Linux. Because of such, I am still deploying Fedora Core 3 when I need XFS in a distribution. Like others, I have often see the regular comment that Red Hat believes XFS offers no features over Ext3. I seriously beg to differ like others, especially when it comes to backing up EAs like ACLs and SELinux attributes. That's a show-stopper right there. And there are the serious scalability issues beyond 1.1TB. I don't know why Red Hat can't accept the fact that XFS is a perfect complement to Ext3. I still use Ext3 for the "essential" filesystems, and most smaller static/binary filesystems -- and I'm glad Tweedie came up with a solution for many of use back in the kernel 2.2 timeframe using a variant of the trusted Ext2 filesystem. But I prefer XFS for large user data, several types of service data, as well as any image/media repositories -- especially since XFS has all the features of Ext3 and more since almost day 1. Is it really a Not Invented Here (NIH) type attitude? Or does Red Hat not want to have to support a 2nd filesystem? Again, most of the comments I see from Red Hat developers are very applicable to ReiserFS and JFS, but not applicable to XFS at all. And given some of the serious "deficiencies" of Ext3 for the "larger enterprise," I still cannot understand why Red Hat does not complement Ext3 with XFS where Ext3 is a serious limitation. They are only hurting their own product IMHO, so I really can't understand the logic of continuing with only Ext3. XFS complements Ext3 perfectly, especially for Red Hat's focus on ACLs, SELinux, NFS, etc... Recent Blog entry (written for more of the "newbie" UNIX administrator, prompted by a recent CentOS thread): http://thebs413.blogspot.com/2005/08/filesystem-fundamentals-and-practices.html -- Bryan J. Smith b.j.smith@ieee.org http://thebs413.blogspot.com ---------------------------------------------------------------------- The best things in life are NOT free - which is why life is easiest if you save all the bills until you can share them with the perfect woman From owner-linux-xfs@oss.sgi.com Sat Aug 27 17:19:19 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 27 Aug 2005 17:19:27 -0700 (PDT) Received: from web34115.mail.mud.yahoo.com (web34115.mail.mud.yahoo.com [66.163.178.113]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7S0JJiL000549 for ; Sat, 27 Aug 2005 17:19:19 -0700 Received: (qmail 14851 invoked by uid 60001); 28 Aug 2005 00:16:54 -0000 Message-ID: <20050828001654.14849.qmail@web34115.mail.mud.yahoo.com> Received: from [130.76.96.19] by web34115.mail.mud.yahoo.com via HTTP; Sat, 27 Aug 2005 17:16:54 PDT X-RocketYMMF: thebs413 Date: Sat, 27 Aug 2005 17:16:54 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? -- Notes ... To: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5975 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 4693 Lines: 108 Since a few people brought this up off-list, let me make some notes on my specific XFS deployments ... 1. Kernel 2.4 I have _never_ used the XFS backport to kernel 2.4. Frankly, I don't trust it. Not because of XFS, but because of kernel 2.4. I have only used the official XFS releases for kernel 2.4, largely those for Red Hat 7.x. In fact, I kept deploying only Red Hat Linux 7.3 with XFS until late last year (once Fedora Core 3 came out), tapping FedoraLegacy.ORG for updates. Again, this means I'm back at kernel 2.4.20 -- and I really never trusted newer 2.4 kernels anyway! I have not had the NFS issues others have complained about, and I've had a real crutch on xfsdump for backups including ACL information, as well as quota support. 2. Kernel 2.6 With Fedora Core 3, I started deploying XFS. I was very disappointed when Red Hat forked Red Hat Enterprise Linux 4 development and did not bring XFS over. I think it was a huge mistake and Red Hat could offer a lot to XFS if they had to maintain it equally with Ext3 under RHEL. Again, I will assert it is in their best interested to do so. With Fedora Core 3 I have quotas, NFS, ACLs and, now, SELinux. Fedora Core 3 should be supported until mid-December when Fedora Core 5 is currently planned for Test 2. Reality will probably dictate that FC5T2 slip to early next year -- and even then, with Fedora Core 3's stability and popularity, I see FedoraLegacy support continuing it for some time (unlike Fedora Core 2 or 4). 3. LVM/MD Usage -- I limit mine to volume slicing Let me start by saying that I'm a huge fan of volume management. I use both LVM and LVM2 for flexible, on-line additions/modifications of logical volumes. In a nutshell, I largely use it to slice my disks with more flexibility -- reserving space, create new volumes as necessary and the occassional expansion (although I typically try to stick to new mounts/symlinks). But with that said, let it be known that I don't trust LVM and especially not LVM2 with snapshots, more complex resizing and definitely not any RAID operations. I do not trust DeviceMapper (DM) with either LVM2 or EMVS right now. Why? All I keep reading is about is race condition after race condition after race condition. And in each case, it's not limited to XFS. And when it comes to MD, I really avoid it. I always have. I've seen a lot of people talk about how software RAID is better, faster, etc... I've seen people state that it allows them to use different disk controllers and other hardware, and not be tied to a vendor. They also claim its more flexible and gives them more options. While I believe they are sincere, I've just had a different set of hardware RAID experiences. First off, I've limited myself to only 3Ware and select LSI Logic (including former Mylex) products over the last 5 years. 3Ware uses an ASIC-driven "storage switch" and I have only deployed LSI Logic (and former Mylex) products that are XScale (which is based on StrongARM). These are very, very high performing -- able to move a lot of data with not only little CPU overhead, but more importantly, without the extensive use and duplication of data streams through the CPU-memory interconnect. I.e., it's not the XORs that get you, but the duplicated data streams tying up the interconnect that data services could be using. [ Same reason why hardware switches/routers are better networking equipment than PCs -- these "storage switch - I/O processors" are the same. ] Their on-board RAID intelligence is self-contained meaning their drivers are simple, GPL block drivers. Secondly, I've also had excellent "forward product" volume compatibility -- especially with 3Ware of 3+ generations over 5 years, full support moving from older to newer, far, far better and longer than MD (let alone LVM/LVM2). And many people have never seen 3Ware's 3DM/3DM2 tools for administration and monitoring, they are much easier to deploy and have saved my butt in several cases. LSI's tools are getting better too. So it is this abstraction of RAID into hardware that removes the multiple layers that often cause the "race conditions" between LVM-MD and other kernel-level operations. This is not just an issue for XFS, not just an issue for Ext3 and Linux in general, but many other OSes as well. Which is why I have been deploying XFS for a long time, provided I "do my homework," alongside Ext3. All the issues I heard about off-list have surrounded configurations that are an issue with Ext3 as well. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Sat Aug 27 20:18:11 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 27 Aug 2005 20:18:14 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7S3IAiL009666 for ; Sat, 27 Aug 2005 20:18:10 -0700 Received: from spindle.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7S3FjxT013382 for ; Sat, 27 Aug 2005 22:15:45 -0500 Received: from [127.0.0.1] (sshgate.corp.sgi.com [198.149.36.12]) by spindle.corp.sgi.com (SGI-8.12.5/8.12.9/generic_config-1.2) with ESMTP id j7S3FhsS84973766; Sat, 27 Aug 2005 20:15:44 -0700 (PDT) Message-ID: <43112C5D.8090202@sgi.com> Date: Sat, 27 Aug 2005 22:15:41 -0500 From: Eric Sandeen User-Agent: Mozilla Thunderbird 1.0.6 (Macintosh/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkins, Vern" CC: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5977 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1153 Lines: 16 Wilkins, Vern wrote: > I agree, all the talk of certain filesystems not needing defragmentation (not just XFS), is all just talk. In the real world I have seen heavy defragmentation on all my machines, regardless of filesystem. All it takes is a limited amount of freespace and/or a lot of file creation/deletion. Mail servers as already mentioned are a good example of the heavy file creation/deletion scenario, as are audio/video editing workstations. On a/v editing workstations I have seen greater than 90% fragmentation in a fairly short time using virtually any filesystem. The ability to easily defrag XFS is pretty significant in my choice of filesystems. > There are, however, things that can be done to limit/reduce filesystem fragmentation. XFS uses delayed allocation, meaning that blocks for a file are not immediately allocated - this allows the allocator to allocate more blocks at a time, and do a more efficient job of keeping blocks in a file unfragmented. On the other hand, some applications are just brutal for filesystems - go download a linux distro iso image via bittorrent & see how many extents you get! -Eric From owner-linux-xfs@oss.sgi.com Sat Aug 27 20:43:33 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 27 Aug 2005 20:43:39 -0700 (PDT) Received: from web34103.mail.mud.yahoo.com (web34103.mail.mud.yahoo.com [66.163.178.101]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7S3hXiL014647 for ; Sat, 27 Aug 2005 20:43:33 -0700 Received: (qmail 73923 invoked by uid 60001); 28 Aug 2005 03:41:08 -0000 Message-ID: <20050828034108.73921.qmail@web34103.mail.mud.yahoo.com> Received: from [130.76.96.18] by web34103.mail.mud.yahoo.com via HTTP; Sat, 27 Aug 2005 20:41:08 PDT X-RocketYMMF: thebs413 Date: Sat, 27 Aug 2005 20:41:08 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: Re: file system defragmentation To: Eric Sandeen , "Wilkins, Vern" Cc: linux-xfs@oss.sgi.com In-Reply-To: <43112C5D.8090202@sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5978 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 696 Lines: 19 Eric Sandeen wrote: > XFS uses delayed allocation, meaning that blocks for a > file are not immediately allocated - this allows the > allocator to allocate more blocks at a time, and do a more > efficient job of keeping blocks in a file unfragmented. XFS further uses extents to allocation different areas of the disk for small files away from larger files. This combined with delayed allocation means that larger files are not put near small files, and both types (especially small files) are fit much better. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Sun Aug 28 04:35:44 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 04:35:49 -0700 (PDT) Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7SBZiiL010757 for ; Sun, 28 Aug 2005 04:35:44 -0700 Received: from chaos.egr.duke.edu (localhost.localdomain [127.0.0.1]) by chaos.egr.duke.edu (8.12.11/8.12.11) with ESMTP id j7SBXIh0030106; Sun, 28 Aug 2005 07:33:18 -0400 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.12.11/8.12.11/Submit) with ESMTP id j7SBXICB030102; Sun, 28 Aug 2005 07:33:18 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Sun, 28 Aug 2005 07:33:18 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: jlb@chaos.egr.duke.edu To: "Bryan J. Smith" cc: linux-xfs@oss.sgi.com Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? In-Reply-To: <1125175569.4518.94.camel@bert64.mobile.smithconcepts.com> Message-ID: References: <1125175569.4518.94.camel@bert64.mobile.smithconcepts.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 5979 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlb17@duke.edu Precedence: bulk X-list: linux-xfs Content-Length: 805 Lines: 24 On Sat, 27 Aug 2005 at 3:46pm, Bryan J. Smith wrote > They are only hurting their own product IMHO, so I really can't > understand the logic of continuing with only Ext3. XFS complements Ext3 > perfectly, especially for Red Hat's focus on ACLs, SELinux, NFS, etc... > See this thread on the nahant mailing list for their most recent thoughts on this: Starts here: https://www.redhat.com/archives/nahant-list/2005-June/msg00280.html Most relevant message (IMO): https://www.redhat.com/archives/nahant-list/2005-June/msg00304.html Basically, they *really* like 4K stacks, XFS doesn't, and they won't go back to 8K or spend the time making XFS work with 4K. Oh, and, again, they don't see that XFS buys you over ext3. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Sun Aug 28 07:13:57 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 07:14:00 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7SEDuiL017186 for ; Sun, 28 Aug 2005 07:13:56 -0700 Received: (qmail invoked by alias); 28 Aug 2005 14:11:30 -0000 Received: from G1eb6.g.pppool.de (EHLO [192.168.10.11]) [80.185.30.182] by mail.gmx.net (mp022) with SMTP; 28 Aug 2005 16:11:30 +0200 X-Authenticated: #2986359 Message-ID: <4311C60F.9050002@gmx.net> Date: Sun, 28 Aug 2005 16:11:27 +0200 From: evilninja User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050804) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? References: <1125175569.4518.94.camel@bert64.mobile.smithconcepts.com> In-Reply-To: X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-archive-position: 5980 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: evilninja@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 432 Lines: 15 Joshua Baker-LePain schrieb: > > Basically, they *really* like 4K stacks, XFS doesn't, and they won't go > back to 8K or spend the time making XFS work with 4K. it really feels strange that everyon is saying "XFS & CONFIG_4KSTACKS=y" does not work - but it does work here [1] with no major hassles. Christian. [1] 2.6.12.5, i386, debian/unstable -- BOFH excuse #242: Software uses US measurements, but the OS is in metric... From owner-linux-xfs@oss.sgi.com Sun Aug 28 07:49:00 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 07:49:04 -0700 (PDT) Received: from web34110.mail.mud.yahoo.com (web34110.mail.mud.yahoo.com [66.163.178.108]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7SEmxiL018772 for ; Sun, 28 Aug 2005 07:49:00 -0700 Received: (qmail 43839 invoked by uid 60001); 28 Aug 2005 14:46:34 -0000 Message-ID: <20050828144634.43837.qmail@web34110.mail.mud.yahoo.com> Received: from [130.76.96.18] by web34110.mail.mud.yahoo.com via HTTP; Sun, 28 Aug 2005 07:46:34 PDT X-RocketYMMF: thebs413 Date: Sun, 28 Aug 2005 07:46:34 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? To: Joshua Baker-LePain Cc: linux-xfs@oss.sgi.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5981 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 3036 Lines: 75 Joshua Baker-LePain wrote: > See this thread on the nahant mailing list for their most > recent thoughts on this: > Starts here: > https://www.redhat.com/archives/nahant-list/2005-June/msg00280.html > Most relevant message (IMO): > https://www.redhat.com/archives/nahant-list/2005-June/msg00304.html > Basically, they *really* like 4K stacks, That's right. It totally slipped my mind on that with 2.6. To be honest, I haven't been deploying XFS as much since the official XFS 1.2 on Red Hat Linux 7.x (plus one 1.3 on Red Hat Linux 9). The Red Hat Linux 7.x installs definitely have the most time, and I very much trust and appreciate its availability. But my Fedora Core 3 tests have been positive, even if they aren't official. I have _avoided_ anything but the official XFS releases prior, including the 2.4 backport. I don't use the 3rd party RPM sets and I don't use the CentOS Plus kernel (although it probably is no less reliable than FC3's). > XFS doesn't, and they won't go back to 8K or spend the time > making XFS work with 4K. I was just happy with (so far) the capabilities of my few Fedora Core 3 installs with XFS. Seems to be handling Quotas, XATTRs for ACLs/SELinux and NFS services without issue. So they are using 4K stacks, and it seems to work for me on FC3's 2.6 implementation, but I haven't hammered it yet like I have RHL7.x in the past. BTW, I can understand Red Hat's insistance on sticking with 4K stacks because of the reduced issues for x86. I remember reading a bit awhile back when I had to deal with early 2.6 workstations (using nVidia's driver). So, what are the "real issues" of using 4K stacks for XFS (among others)? Is it just a shift in the trust from the proven Irix/MIPS history? Or is it more than that? > Oh, and, again, they don't see that XFS buys you over ext3. That's gotta stop. No offense, but that seems to be 100% political statement. I can't be the only consultant deploying RHEL who constantly wishes he could offer clients a way to backup all XATTRs on files without some added procedures/hacks. I mean, if Red Hat is pushing for SELinux so damn hard, WTF can't they include a solid backup mechanism for it on Ext3? I just want to smack Red Hat silly on the existance of xfsdump (and xfs_copy) and xfs_fsr among others. Where are the freak'n tools and support? It's almost ironic that all the "lack of kernel-interface/user-space support" Red Hat claims about JFS and ReiserFS (which is true) is not applied equally in reverse on Ext3! And then there's the big damn size issue. That's the kicker. I'm trying put to in >1.1TB (>1TiB) filesystems and I have to start explaining the limitations to clients. That just eats right into the MS FUD / Windows pundit non-sense. I'm not some ReiserFS puke or JFS enthusiast, I've got XFS in production. But it's all old systems. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Sun Aug 28 08:27:30 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 08:27:39 -0700 (PDT) Received: from web34111.mail.mud.yahoo.com (web34111.mail.mud.yahoo.com [66.163.178.109]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7SFRTiL025173 for ; Sun, 28 Aug 2005 08:27:30 -0700 Received: (qmail 92542 invoked by uid 60001); 28 Aug 2005 15:25:04 -0000 Message-ID: <20050828152504.92540.qmail@web34111.mail.mud.yahoo.com> Received: from [130.76.96.18] by web34111.mail.mud.yahoo.com via HTTP; Sun, 28 Aug 2005 08:25:04 PDT X-RocketYMMF: thebs413 Date: Sun, 28 Aug 2005 08:25:04 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: RHEL 64-bit with 4+GiB mem and 4+TB disk calls for XFS To: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5982 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 3521 Lines: 73 I guess I'm just starting to get back into this because I'm starting to run into real system integration projects where data volumes are exceeding 4+TB. I know this is not a staple for Red Hat where they are either catering to grid computing clusters or web servers, possibly Oracle SQL databases using "raw" slices (instead of filesystems), but they are still the "flagship" carrier of any distribution when it comes to file services with NFS (or NFS+SMB) in my book. I'm not looking for dealing with x86 issues. The configurations I'm talking about are 4+TB disks on systems with 4+GiB mem (pretty much 1GiB per DDR channel is commodity, and that's a minimum of 4GiB for 4 DDR channels on Opteron 2xx). I'm also not doing software RAID, but using 3Ware and LSI Logic hardware**. From all I've read, x86-64 in PAE mode using 52-bit register (48-bit "Long Mode") is 4K pages, although I do note 2M and 4M pages as well. Again, I guess since I'm just getting back into XFS as a solution, as my last serious set of runs was in the XFS 1.2 / Red Hat Linux 7.x time-frame. Fedora Core 3 has been a good test, but I'm always leery of deploying anything that is not SGI blessed -- not even stock kernels -- and I believe the Fedora Core 3 offers little in an XFS implementation beyond the stock kernel. XFS is the absolute perfect complement to Ext3 for 100+GB volumes, especially 1+TB volumes. Red Hat can choose to ignore us system integrators and lose a lot of business. In fact, I'm really getting to the point I'm half-way serious about getting some investors to build a new enterprise distribution and offer Service Level Agreements (SLAs). The distribution would always be based on a fork of the 2rd or 3rd Fedora Core release, as I typically do agree with Red Hat's design decisions at the core -- but not the end-focus of Red Hat Enterprise Linux. I cannot trust Red Hat's focus as of late, and I 100% agree with Sun when they say that Red Hat is not addressing the filesystem aspect (among other things). Otherwise, if I had to implement a commodity 2 or 4-way Opteron 2xx/8xx solution today, I would go Solaris 10. -- Bryan **SIDE NOTE: I rather tire of people who make claims about how "bad" hardware RAID and how "good" software RAID is by using "not even current 5 years ago" i960-based hardware RAID solutions as examples, along with the farce of "universal compatibility" which LVM/MD has _not_ done as well over time -- especially with volumes on LSI Logic, let alone 3Ware, solutions. There are those of us who have serious, multiple 8+ disk volumes who have been using 3Ware and LSI Logic solutions for at least 5 years with hardware mirroring/XORs. We don't have the "race conditions" between software volume/filesystem layers, and we don't overload our system interconnect with needless data replication. Even Intel is now starting to put its XScale I/O Processors (IOPs) on server chipsets/mainboards as _standard_ for off-loading network/storage (RAID, network, iSCSI HBA, etc...), because their IOPs at 500+MHz are better than using the traditional CPU/memory interconnect. I.e., there is a reason why we don't use PCs for network switches and routers, and today's serial ATA (SATA) and serial attached SCSI (SAS) storage controllers are basically "storage switches" in the exact same regard overhead/performance-wise. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Sun Aug 28 11:21:38 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 11:21:45 -0700 (PDT) Received: from sommereik.ii.uib.no (sommereik.ii.uib.no [129.177.16.236]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7SILbiL001236 for ; Sun, 28 Aug 2005 11:21:38 -0700 Received: from loko.ii.uib.no ([129.177.20.21]:38545) by sommereik.ii.uib.no with esmtps (TLSv1:AES256-SHA:256) (Exim 4.43) id 1E9RkN-00013R-3T; Sun, 28 Aug 2005 20:19:11 +0200 Received: (from janfrode@localhost) by loko.ii.uib.no (8.12.11/8.12.11/Submit) id j7SIJ8F6023538; Sun, 28 Aug 2005 20:19:08 +0200 Date: Sun, 28 Aug 2005 20:19:08 +0200 From: Jan-Frode Myklebust To: Fong Vang Cc: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation Message-ID: <20050828181908.GA23467@ii.uib.no> References: <4f52331f050826001612f8e323@mail.gmail.com> <20050826101131.GA24544@ii.uib.no> <4f52331f0508260848782f240a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4f52331f0508260848782f240a@mail.gmail.com> X-archive-position: 5983 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Jan-Frode.Myklebust@bccs.uib.no Precedence: bulk X-list: linux-xfs Content-Length: 300 Lines: 11 On Fri, Aug 26, 2005 at 08:48:47AM -0700, Fong Vang wrote: > > This is very useful. Thank you. How stable is xfs_fsr? I don't know about any stability issues with it.. AFAIK on IRIX it's by default run by cron once a week for all file systems, so I would expect it to be a safe command. -jf From owner-linux-xfs@oss.sgi.com Sun Aug 28 16:00:44 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 16:00:47 -0700 (PDT) Received: from astra.simleu.ro ([80.97.44.14]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7SN0hiL018347 for ; Sun, 28 Aug 2005 16:00:44 -0700 Received: from saytrin.hq.k1024.org (unknown [62.217.245.194]) by astra.simleu.ro (Postfix) with ESMTP id 1518256 for ; Mon, 29 Aug 2005 01:58:14 +0300 (EEST) Received: by saytrin.hq.k1024.org (Postfix, from userid 4004) id 9F5371800AA; Mon, 29 Aug 2005 01:55:52 +0300 (EEST) Date: Mon, 29 Aug 2005 01:55:52 +0300 From: Iustin Pop To: linux-xfs@oss.sgi.com Subject: Shrink support - idea/plan/problems Message-ID: <20050828225552.GB17330@saytrin.hq.k1024.org> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Linux: This message was written on Linux X-Header: /usr/include gives great headers User-Agent: Mutt/1.5.10i X-archive-position: 5984 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: iusty@k1024.org Precedence: bulk X-list: linux-xfs Content-Length: 3773 Lines: 72 Hello to all, I have a proposal to implement a very simple shrink operation. Simple meaning that the user has to deal with clearing the removed space, and it doesn't work with a real-time part. The idea is based on my guesswork through the sources and on the correctness of the following assumptions: - an AG contains only bnobt blocks, cntbt blocks, inobt blocks and user data blocks; - there is some way of computing the number of blocks used by the above btrees; - a way to block allocations to an ag can be implemented (I'm thinking about an in-core flag for AGs which xfs_alloc_vextend should use) Kernel-side, the steps are (somewhat reverse of xfs_growfs_data_private): 1. compute new number of AGs and blocks; 2. check to see if we don't trip over the log (if it is internal); 3. for each AG to be fully removed, block allocations in AG and check: a. check that agf->agf_length = XFS_PREALLOC_BLOCKS() + ags->agf_free + sum(block in bnobt, cntbt, inobt) ; this means that no user data is held in this AG; b. check that agi->agi_count == agi->agi_free; this means that no inodes are used in this AG; 4. if the (new) last AG will have number of blocks smaller than sb_agblocks, allocate an extent occupying exactly the space to be removed; if it is not possible, it means that some data is using that space; also this takes care of modifying the freespace lists, etc. for this AG; 5. update the superblocks with new agcount, dblocks, fdblocks; I have a patch which does some parts of this (works ok on empty filesystems), with the following issues: - 3a I don't know how to implement; judging from the logical structure of the btrees, a walk function starting at the root and following ptrs field until level 0 and counting each block could do it; however, the xfs_bmap_btree and xfs_ialloc_btree stuff is very complicated; - in 4, I use xfs_alloc_vextent with the args parameter filled by guesswork; it seems to work and the file system is ok (as reported by xfs_check and xfs_repair); however, more information is needed here - in xfs_growfs_data_private, if new AGs are added, some mp->m_perag is resized; presumably also for shrink, although I don't know what issues are with just shrinking that structure; - I don't understand from xfs_growfs_data_private if locking is needed or if some problems if the AGs we are modifying are present in some caches; the grow operation implementation seems very simple :) All in all, I'm able to shrink and grow at will (no panics, df reports ok, xfs_check and xfs_repair are not complaining) an empty filesystem (down to the middle where the log is) and which no-one is accessing :) The current version of the patch just adds a new function in xfs_fsops.c and modifies xfs_growfs_data_private to call that function is the number of data blocks is lower than the current number. For helping the user clear the space, an userspace program can compute all items having blocks/attribute blocks in that region, and the inodes present in the affected AGs; however, if any btree has blocks in the portion to be removed from the last AG (if not shrinking down to a multiple of sb_agblocks), I think that cannot be computed (from userspace). For actual moving the data off those blocks, there would be: - a program using xfsctl(XFS_IOC_SWAPEXT, ...) for clearing data blocks or manual copy (after disabling allocations to those AGs); - either a version of xfs_reno for clearing inodes or manual copy of those items (but somehow after disabling allocations to those AGs); What do you think? Is it a reasonable idea to try to finish this? And does anyone have pointers toward the issues described above? Thanks, Iustin Pop From owner-linux-xfs@oss.sgi.com Sun Aug 28 17:25:29 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 17:25:35 -0700 (PDT) Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7T0PSiL026147 for ; Sun, 28 Aug 2005 17:25:29 -0700 Received: from doufu (doufu.siksai.co.uk [82.133.8.9]) by smtp.nildram.co.uk (Postfix) with ESMTP id ADC8924C93D for ; Mon, 29 Aug 2005 01:17:24 +0100 (BST) Received: from xiao.siksai.co.uk ([82.133.8.12] ident=rhowe) by doufu with smtp (Exim 4.50) id 1E9XL2-0004le-Bp for linux-xfs@oss.sgi.com; Mon, 29 Aug 2005 01:17:24 +0100 Received: by xiao.siksai.co.uk (sSMTP sendmail emulation); Mon, 29 Aug 2005 01:17:24 +0100 From: "Russell Howe" Date: Mon, 29 Aug 2005 01:17:24 +0100 To: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation Message-ID: <20050829001723.GA10587@xiao.rsnet> Mail-Followup-To: linux-xfs@oss.sgi.com References: <43112C5D.8090202@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43112C5D.8090202@sgi.com> User-Agent: Mutt/1.5.10i X-archive-position: 5985 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rhowe@siksai.co.uk Precedence: bulk X-list: linux-xfs Content-Length: 467 Lines: 13 On Sat, Aug 27, 2005 at 10:15:41PM -0500, Eric Sandeen wrote: > On the other hand, some applications are just brutal for filesystems - > go download a linux distro iso image via bittorrent & see how many > extents you get! must hack bittorrent to use the preallocation ioctl... (presumably this would fix the problem for bittorrent) -- Russell Howe | Why be just another cog in the machine, rhowe@siksai.co.uk | when you can be the spanner in the works? From owner-linux-xfs@oss.sgi.com Sun Aug 28 19:56:18 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 19:56:22 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7T2uGiL002169 for ; Sun, 28 Aug 2005 19:56:17 -0700 Received: from chook.melbourne.sgi.com (chook.melbourne.sgi.com [134.14.54.237]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA25623 for ; Mon, 29 Aug 2005 12:53:49 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16302) id 96CEC49BB22F; Mon, 29 Aug 2005 12:53:48 +1000 (EST) To: linux-xfs@oss.sgi.com Subject: TAKE 904196 - relayfs Message-Id: <20050829025348.96CEC49BB22F@chook.melbourne.sgi.com> Date: Mon, 29 Aug 2005 12:53:48 +1000 (EST) From: nathans@sgi.com (Nathan Scott) X-archive-position: 5986 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 3608 Lines: 62 Merge relayfs and the initial block device tracing patch from Jens. Date: Mon Aug 29 12:52:47 AEST 2005 Workarea: chook.melbourne.sgi.com:/build/nathans/2.6.x-xfs Inspected by: nathans The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb Modid: 2.6.x-xfs-melb:linux:23656a Documentation/filesystems/relayfs.txt - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/Documentation/filesystems/relayfs.txt fs/relayfs/inode.c - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/relayfs/inode.c fs/relayfs/relay.c - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/relayfs/relay.c drivers/block/blktrace.c - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/drivers/block/blktrace.c split-patches/relayfs-api-cleanup - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/split-patches/relayfs-api-cleanup split-patches/relayfs-add-read-support-fix - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/split-patches/relayfs-add-read-support-fix split-patches/relayfs-add-read-support - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/split-patches/relayfs-add-read-support split-patches/relayfs - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/split-patches/relayfs split-patches/jens-blk-trace - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/split-patches/jens-blk-trace fs/relayfs/Makefile - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/relayfs/Makefile fs/relayfs/buffers.c - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/relayfs/buffers.c fs/relayfs/buffers.h - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/relayfs/buffers.h include/linux/relayfs_fs.h - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/include/linux/relayfs_fs.h fs/relayfs/relay.h - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/relayfs/relay.h include/linux/blktrace.h - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/include/linux/blktrace.h drivers/block/Kconfig - 1.11 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/drivers/block/Kconfig.diff?r1=text&tr1=1.11&r2=text&tr2=1.10&f=h drivers/block/Makefile - 1.8 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/drivers/block/Makefile.diff?r1=text&tr1=1.8&r2=text&tr2=1.7&f=h drivers/block/elevator.c - 1.10 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/drivers/block/elevator.c.diff?r1=text&tr1=1.10&r2=text&tr2=1.9&f=h drivers/block/ioctl.c - 1.7 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/drivers/block/ioctl.c.diff?r1=text&tr1=1.7&r2=text&tr2=1.6&f=h drivers/block/ll_rw_blk.c - 1.15 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/drivers/block/ll_rw_blk.c.diff?r1=text&tr1=1.15&r2=text&tr2=1.14&f=h fs/Kconfig - 1.22 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/Kconfig.diff?r1=text&tr1=1.22&r2=text&tr2=1.21&f=h fs/Makefile - 1.10 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/fs/Makefile.diff?r1=text&tr1=1.10&r2=text&tr2=1.9&f=h include/linux/blkdev.h - 1.14 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/include/linux/blkdev.h.diff?r1=text&tr1=1.14&r2=text&tr2=1.13&f=h include/linux/fs.h - 1.18 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/include/linux/fs.h.diff?r1=text&tr1=1.18&r2=text&tr2=1.17&f=h split-patches/series - 1.20 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.6-xfs/split-patches/series.diff?r1=text&tr1=1.20&r2=text&tr2=1.19&f=h From owner-linux-xfs@oss.sgi.com Sun Aug 28 21:33:27 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 21:33:35 -0700 (PDT) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.245.74]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7T4XQiL012185 for ; Sun, 28 Aug 2005 21:33:26 -0700 Received: from [192.168.3.20] (shiva [192.168.3.20]) by ishtar.tlinx.org (8.13.3/8.12.10/SuSE Linux 0.7) with ESMTP id j7T4UwFQ001250 for ; Sun, 28 Aug 2005 21:31:00 -0700 Message-ID: <43128F82.4010004@tlinx.org> Date: Sun, 28 Aug 2005 21:30:58 -0700 From: "Linda A. Walsh" User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en, en_US MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation References: <4f52331f050826001612f8e323@mail.gmail.com> <20050826101131.GA24544@ii.uib.no> <4f52331f0508260848782f240a@mail.gmail.com> In-Reply-To: <4f52331f0508260848782f240a@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 5987 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xfs@tlinx.org Precedence: bulk X-list: linux-xfs Content-Length: 911 Lines: 34 XFS_FSR has been very stable -- I've been running it since before xfs was merged into the kernel. I have the following file, named "fsr" in my /etc/cron.daily: fsr: #!/bin/bash /usr/sbin/xfs_fsr ---- I would think /bin/sh or /bin/sh would work equally well. _File_ fragmentation is a virtual non-issue on my disks, however, xfs_fsr only works on my file data. It doesn't work on directory data. On a 118G partition nearing 79% capacity, printing the defragmentation data from xfs_db: files: actual 316870, ideal 316652, fragmentation factor 0.07% directories: actual 2538, ideal 1330, fragmentation factor 47.60% I don't know about other data types (attr, symlink, quota, realtime, realtime control) as I don't believe I have any of those types on my volumes...But, hey, file fragmentation seems to be handled! :-) Linda Fong Vang wrote: >This is very useful. Thank you. How stable is xfs_fsr? > From owner-linux-xfs@oss.sgi.com Sun Aug 28 21:42:10 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Aug 2005 21:42:13 -0700 (PDT) Received: from ausmail2.core.coremetrics.com (app.clientdynamics.net [66.45.103.235] (may be forged)) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7T4g9iL013005 for ; Sun, 28 Aug 2005 21:42:09 -0700 Received: from [10.120.50.10] (al1achen.core.coremetrics.com [10.120.50.10]) by ausmail2.core.coremetrics.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZ713LBV; Sun, 28 Aug 2005 23:38:19 -0500 Message-ID: <4312913F.6040205@coremetrics.com> Date: Sun, 28 Aug 2005 23:38:23 -0500 From: Austin Gonyou User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Linda A. Walsh" CC: linux-xfs@oss.sgi.com Subject: Re: file system defragmentation References: <43128F82.4010004@tlinx.org> In-Reply-To: <43128F82.4010004@tlinx.org> Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 5988 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: austin@coremetrics.com Precedence: bulk X-list: linux-xfs Content-Length: 1612 Lines: 54 I believe in the FAQ/man-info page for xfs_fsr, it refers to the fact that it will only work on file data and that the percent of frag is a factor of the size of files, number of inodes, and number of files. This is important because if you run a mail/news/file server of some sort, and you have *high* frag, then there's probably a performance problem there. If you have large files, say, 2GB files, and have tons of them, (read RDBMS), then each file if it were fragged, would yield a higher amount of fragmentation per file. Just remember that when using FSR. ;) Austin Linda A. Walsh wrote: > XFS_FSR has been very stable -- I've been running it since before > xfs was merged into the kernel. > > I have the following file, named "fsr" in my /etc/cron.daily: > fsr: > #!/bin/bash > /usr/sbin/xfs_fsr > ---- > I would think /bin/sh or /bin/sh would work equally well. > > _File_ fragmentation is a virtual non-issue on my disks, however, > xfs_fsr only works on my file data. It doesn't work > on directory data. On a 118G partition nearing 79% capacity, > printing the defragmentation data from xfs_db: > > files: > actual 316870, ideal 316652, fragmentation factor 0.07% > > directories: > actual 2538, ideal 1330, fragmentation factor 47.60% > > I don't know about other data types (attr, symlink, quota, > realtime, realtime control) as I don't believe I have > any of those types on my volumes...But, hey, file fragmentation > seems to be handled! :-) > > Linda > > > Fong Vang wrote: > > >This is very useful. Thank you. How stable is xfs_fsr? > > > [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Mon Aug 29 10:54:10 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 10:54:18 -0700 (PDT) Received: from soloth.lewis.org (soloth.lewis.org [69.28.69.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7THs9iL013074 for ; Mon, 29 Aug 2005 10:54:10 -0700 Received: from soloth.lewis.org (localhost.localdomain [127.0.0.1]) by soloth.lewis.org (8.12.11/8.12.11) with ESMTP id j7THpht3006091 for ; Mon, 29 Aug 2005 13:51:43 -0400 Received: from localhost (jlewis@localhost) by soloth.lewis.org (8.12.11/8.12.11/Submit) with ESMTP id j7THphAV006087 for ; Mon, 29 Aug 2005 13:51:43 -0400 X-Authentication-Warning: soloth.lewis.org: jlewis owned process doing -bs Date: Mon, 29 Aug 2005 13:51:43 -0400 (EDT) From: Jon Lewis To: linux-xfs@oss.sgi.com Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? In-Reply-To: <20050828144634.43837.qmail@web34110.mail.mud.yahoo.com> Message-ID: References: <20050828144634.43837.qmail@web34110.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5990 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlewis@lewis.org Precedence: bulk X-list: linux-xfs Content-Length: 2116 Lines: 42 On Sun, 28 Aug 2005, Bryan J. Smith wrote: > To be honest, I haven't been deploying XFS as much since the > official XFS 1.2 on Red Hat Linux 7.x (plus one 1.3 on Red > Hat Linux 9). The Red Hat Linux 7.x installs definitely have > the most time, and I very much trust and appreciate its > availability. If these releases were so stable, could someone from SGI please put them back up on the oss.sgi.com FTP server? I've got a RH 8.0 based system (switching/upgrading the entire distro hoping for XFS stability is not an option...if I have to do that, I'm abandoning XFS) that's really not behaving well using Red Hat's kernel RPMs rebuilt with the XFS 1.3.0 release. If there's something more stable that works (never did hear back about why NFSD in the SGI xfs-cvs 2.4 kernel is broken), I'd like to give it a try before copying a couple hundred GB of mail to EXT3. > And then there's the big damn size issue. That's the kicker. > I'm trying put to in >1.1TB (>1TiB) filesystems and I have > to start explaining the limitations to clients. That just > eats right into the MS FUD / Windows pundit non-sense. huh? From what I've read, ext3 can handle up to 4TB filesystems. What problems do you run into with >1TB, but <4TB? I realize, XFS being 64-bit means it can have filesystems of inconceivable size...but after recent threads on this list about how xfs_repair needs considerable RAM in order to repair large fs's, abusing XFS's fs size limit seems a really bad idea. You may end up with a damaged fs that requires 128gb of RAM to repair. Then what will you do with that multi-TB damaged fs? > I'm not some ReiserFS puke or JFS enthusiast, I've got XFS in > production. But it's all old systems. Same here. Unfortunately, it was put into production without sufficient testing and has never been entirely stable. ---------------------------------------------------------------------- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ From owner-linux-xfs@oss.sgi.com Mon Aug 29 11:19:06 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 11:19:13 -0700 (PDT) Received: from web34109.mail.mud.yahoo.com (web34109.mail.mud.yahoo.com [66.163.178.107]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7TIJ6iL014983 for ; Mon, 29 Aug 2005 11:19:06 -0700 Received: (qmail 83328 invoked by uid 60001); 29 Aug 2005 18:16:40 -0000 Message-ID: <20050829181640.83323.qmail@web34109.mail.mud.yahoo.com> Received: from [130.76.96.17] by web34109.mail.mud.yahoo.com via HTTP; Mon, 29 Aug 2005 11:16:39 PDT X-RocketYMMF: thebs413 Date: Mon, 29 Aug 2005 11:16:39 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? To: Jon Lewis , linux-xfs@oss.sgi.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5991 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 2127 Lines: 58 Jon Lewis wrote: > If these releases were so stable, could someone from SGI > please put them back up on the oss.sgi.com FTP server? Actually, that would be nice since Red Hat Linux 7.3 is still supported by FedoraLegacy.ORG, Progeny and select, mission critical hardware/software companies like FalconStor. Then again, the Red Hat Linux 9 / XFS 1.3.1 releases _are_ on the SGI site. I only had 1 system running with those, and have far less time with them, but they were fairly good AFAICT. > I've got a RH 8.0 based system (switching/upgrading the > entire distro hoping for XFS stability is not an option... > if I have to do that, I'm abandoning XFS) that's really not > behaving well using Red Hat's kernel RPMs rebuilt with the > XFS 1.3.0 release. As I mentioned off-list, Red Hat Linux 8.0 is a ".0" release and not well trusted. And your issues are compounded by the fact that you are running a 3rd party "hacked together" XFS release. > huh? From what I've read, ext3 can handle up to 4TB > filesystems. Yes, it has been extended from 1.1TB to 2.2TB to 4.4TB to, now, 8.8TB with all sorts of hacks in 2.6. That's not what I call "trusted." > What problems do you run into with >1TB, but <4TB? I > realize, XFS being 64-bit means it can have filesystems > of inconceivable size...but after recent threads on this > list about how xfs_repair needs considerable RAM in order > to repair large fs's, abusing XFS's fs size limit seems a > really bad idea. I haven't been installing Opteron systems with less than 4GiB of RAM since they first came out. Heck, 16GiB RAM is pretty much standard when I install a 4-way Opteron. > Same here. Unfortunately, it was put into production > without sufficient testing and has never been entirely > stable. I assume you're referring to the previous integrator, not SGI, XFS or anything else. I tire of fly-by-night system integrators who put in hacked kernels and ".0" releases. -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Mon Aug 29 11:44:10 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 11:44:14 -0700 (PDT) Received: from soloth.lewis.org (soloth.lewis.org [69.28.69.2]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7TIi9iL016861 for ; Mon, 29 Aug 2005 11:44:09 -0700 Received: from soloth.lewis.org (localhost.localdomain [127.0.0.1]) by soloth.lewis.org (8.12.11/8.12.11) with ESMTP id j7TIfgRX006704 for ; Mon, 29 Aug 2005 14:41:42 -0400 Received: from localhost (jlewis@localhost) by soloth.lewis.org (8.12.11/8.12.11/Submit) with ESMTP id j7TIfgLq006700 for ; Mon, 29 Aug 2005 14:41:42 -0400 X-Authentication-Warning: soloth.lewis.org: jlewis owned process doing -bs Date: Mon, 29 Aug 2005 14:41:42 -0400 (EDT) From: Jon Lewis To: linux-xfs@oss.sgi.com Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? In-Reply-To: <20050829181640.83323.qmail@web34109.mail.mud.yahoo.com> Message-ID: References: <20050829181640.83323.qmail@web34109.mail.mud.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-archive-position: 5992 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlewis@lewis.org Precedence: bulk X-list: linux-xfs Content-Length: 2755 Lines: 58 On Mon, 29 Aug 2005, Bryan J. Smith wrote: > Actually, that would be nice since Red Hat Linux 7.3 is still > supported by FedoraLegacy.ORG, Progeny and select, mission > critical hardware/software companies like FalconStor. > > Then again, the Red Hat Linux 9 / XFS 1.3.1 releases _are_ on > the SGI site. I only had 1 system running with those, and > have far less time with them, but they were fairly good > AFAICT. AFAIK, putting a Red Hat 9 kernel on an 8.0 system is going to cause trouble (NPTL will cause problems), but I suspect I'll have less trouble using a 7.3 kernel on an 8.0 system. I could be wrong. I should probably download SGI's RH9 srpm and see if it can be made to work without too much trouble on a 8.0 based system. > As I mentioned off-list, Red Hat Linux 8.0 is a ".0" release > and not well trusted. And your issues are compounded by the > fact that you are running a 3rd party "hacked together" XFS > release. The servers we have running 8.0 are highly specialized and are running 3rd party software for those functions anyway (qmail based mail servers), and so they really don't rely on much of the distro other than the kernel. I'm not too concerned with distro version...just kernel/fs stability. That's why I tried the 2.4.31 kernel from SGI's xfs-cvs, but I found its nfsd not entirely functional. If I'm going to have to shut down long enough for an OS upgrade, and then deal with anything broken by the upgrade, I'd rather just swap out the disk array for another running ext3, and then copy all the old mail in, with much less "completely down" time. > I haven't been installing Opteron systems with less than 4GiB > of RAM since they first came out. Heck, 16GiB RAM is pretty > much standard when I install a 4-way Opteron. But how much RAM is required to xfs_repair a 5TB fs? Does anyone even know? How about a 25TB fs? Even if XFS allows you to create such fs's, it doesn't mean you're not much better off doing it the old fashioned way and tying several smaller fs's together via directory structure rather than creating one giant one. What sort of data are your clients storing that they "need" such large fs's? > I assume you're referring to the previous integrator, not > SGI, XFS or anything else. I tire of fly-by-night system > integrators who put in hacked kernels and ".0" releases. Not an integrator...ex-staff/coworkers choosing to use unsupported FS's requiring 3rd party "hacked together" kernels. ---------------------------------------------------------------------- Jon Lewis | I route Senior Network Engineer | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________ From owner-linux-xfs@oss.sgi.com Mon Aug 29 11:50:16 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 11:50:25 -0700 (PDT) Received: from mail.butterblume.org ([193.151.7.122]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7TIoFiL017580 for ; Mon, 29 Aug 2005 11:50:16 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.butterblume.org (Postfix) with ESMTP id 37C1A7EF5 for ; Mon, 29 Aug 2005 20:47:44 +0200 (CEST) Received: from butterblume (xdsl-81-173-188-15.netcologne.de [81.173.188.15]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.butterblume.org (Postfix) with ESMTP id D7DEF7E8D for ; Mon, 29 Aug 2005 20:47:43 +0200 (CEST) Date: Mon, 29 Aug 2005 20:47:47 +0200 From: Markus Meyer To: linux-xfs@oss.sgi.com Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? Message-ID: <20050829184747.GA15581@butterblume> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20050829181640.83323.qmail@web34109.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/9DWx/yDrRhgMJTb" Content-Disposition: inline In-Reply-To: <20050829181640.83323.qmail@web34109.mail.mud.yahoo.com> User-Agent: mutt-ng/devel (Linux) X-archive-position: 5993 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mm@butterblume.org Precedence: bulk X-list: linux-xfs Content-Length: 933 Lines: 35 --/9DWx/yDrRhgMJTb Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On [Mon, Aug 29 11:16], Bryan J. Smith wrote: Hi Brian, >I haven't been installing Opteron systems with less than 4GiB >of RAM since they first came out. Heck, 16GiB RAM is pretty >much standard when I install a 4-way Opteron. So you say that using XFS on a system with 512 MiB and a 80 GiB hardrive is no option? What about all those users who use XFS at home because it's stable and very easy to setup? Cheers, --=20 Markus Meyer - encrypted email preferred -> GPG: B87120ED --/9DWx/yDrRhgMJTb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDE1hTFH1rMbhxIO0RAgkRAJ96YCZqeL9iQRTRLPjqELkaS4MatgCghmnc 1CAtGHBGEYW4X28w7qbbcis= =H7cR -----END PGP SIGNATURE----- --/9DWx/yDrRhgMJTb-- From owner-linux-xfs@oss.sgi.com Mon Aug 29 12:01:11 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 12:01:23 -0700 (PDT) Received: from web34110.mail.mud.yahoo.com (web34110.mail.mud.yahoo.com [66.163.178.108]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7TJ1AiL018557 for ; Mon, 29 Aug 2005 12:01:11 -0700 Received: (qmail 90594 invoked by uid 60001); 29 Aug 2005 18:58:44 -0000 Message-ID: <20050829185844.90592.qmail@web34110.mail.mud.yahoo.com> Received: from [130.76.96.17] by web34110.mail.mud.yahoo.com via HTTP; Mon, 29 Aug 2005 11:58:44 PDT X-RocketYMMF: thebs413 Date: Mon, 29 Aug 2005 11:58:44 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? To: Jon Lewis , linux-xfs@oss.sgi.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5994 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 3164 Lines: 92 Jon Lewis wrote: > AFAIK, putting a Red Hat 9 kernel on an 8.0 system I _never_ advocated that. I advocated you upgrade to Red Hat Linux 9 (which is really the ".1" release of Red Hat Linux 8.0). > The servers we have running 8.0 are highly specialized and > are running 3rd party software for those functions anyway > (qmail based mail servers), Red Hat Linux 9 is ABI compatible with Red Hat Linux 8.0. You should be able to run any and all software. > and so they really don't rely on much of the distro other > than the kernel. I'm not too concerned with distro > version...just kernel/fs stability. Then do a "partial upgrade" from Red Hat Linux 8.0 to Red Hat Linux 9 using the yum backport via "yum update" instead of "yum upgrade." The former will not deprecate packages. You'll also open your system to the available updates from Fedora Legacy. Red Hat Linux 8.0 support was dropped long ago, but Red Hat Linux 9 support continues -- and it will likely continue at FL.org longer than Red Hat Linux 7.3 will. > That's why I tried the 2.4.31 kernel from SGI's xfs-cvs, > but I found its nfsd not entirely functional. There are all sorts of issues in running Red Hat Linux 8.0. You want to stick with Red Hat Linux 9 or Fedora Core 1. The are like the ".1" and ".2" revisions beyond Red Hat Linux 8.0. If you're still in doubt, see my (now aged) Red Hat ABI (application binary interface) compatibility tables here: http://www.geocities.com/thebs413/RH-Distribution-FAQ-3.html#ss3.1 I have yet to find anything for Red Hat Linux 8.0 that didn't work under Red Hat Linux 9 / Fedora Core 1. > If I'm going to have to shut down long enough for an OS > upgrade, and then deal with anything broken by the upgrade, Don't shut down. To a partial, _live_ upgrade using the yum backport. You can get it from here: http://download.fedoralegacy.org/apt/redhat/9/i386/RPMS.legacy-utils/yum-2.0.5-0.9.2.legacy.noarch.rpm Note, you'll probably want to update your RPM on Red Hat Linux 8.0 before doing anything (if you didn't do so in early 2004): http://download.fedoralegacy.org/apt/redhat/8.0/i386/RPMS.legacy-utils/ You're first step will be to target the YUM at FedoraLegacy for Red Hat Linux 9. Then run: yum install redhat-release And from there, start doing select YUM updates -- GLibC, etc... Then add in your kernel and reboot. > I'd rather just swap out the disk array for another running > ext3, and then copy all the old mail in, with much less > "completely down" time. I differ. You can do a "live" update. > Not an integrator...ex-staff/coworkers choosing to use > unsupported FS's Not unsupported. SGI had _official_ XFS releases for select Red Hat Linux releases. If you go outside of those, you deserve what you get. Same deal for ReiserFS, I've seen many, many distros (outside of SuSE) do some _stupid_, half-baked ReiserFS support. > requiring 3rd party "hacked together" kernels. I think you have it backwards. ;-> -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Mon Aug 29 12:10:28 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 12:10:34 -0700 (PDT) Received: from web34110.mail.mud.yahoo.com (web34110.mail.mud.yahoo.com [66.163.178.108]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7TJASiL019645 for ; Mon, 29 Aug 2005 12:10:28 -0700 Received: (qmail 94898 invoked by uid 60001); 29 Aug 2005 19:08:01 -0000 Message-ID: <20050829190801.94896.qmail@web34110.mail.mud.yahoo.com> Received: from [130.76.96.17] by web34110.mail.mud.yahoo.com via HTTP; Mon, 29 Aug 2005 12:08:01 PDT X-RocketYMMF: thebs413 Date: Mon, 29 Aug 2005 12:08:01 -0700 (PDT) From: "Bryan J. Smith" Reply-To: b.j.smith@ieee.org Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? To: Markus Meyer , linux-xfs@oss.sgi.com In-Reply-To: <20050829184747.GA15581@butterblume> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-archive-position: 5995 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Content-Length: 767 Lines: 26 Markus Meyer wrote: > So you say that using XFS on a system with 512 MiB and a 80 > GiB hardrive is no option? What about all those users who use > XFS at home because it's stable and very easy to setup? I'm not saying anything. I personally prefer XFS for data filesystems -- both the inode/mega-data features as well as the ability to backup via xfsdump, defrag with xfs_fsr (largely for service data filesystems like IMAP), etc... But Ext3 is fine for sub-100GB in my experience. -- Bryan P.S. Anal note: Hard drive storage is typically in GB (10^9), memory in GiB (2^30). -- Bryan J. Smith | Sent from Yahoo Mail mailto:b.j.smith@ieee.org | (please excuse any http://thebs413.blogspot.com/ | missing headers) From owner-linux-xfs@oss.sgi.com Mon Aug 29 18:36:31 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Aug 2005 18:36:41 -0700 (PDT) Received: from mail21.syd.optusnet.com.au (mail21.syd.optusnet.com.au [211.29.133.158]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7U1aUiL018232 for ; Mon, 29 Aug 2005 18:36:30 -0700 Received: from saturn (c211-28-166-127.eburwd2.vic.optusnet.com.au [211.28.166.127]) by mail21.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id j7U1Xts6005384; Tue, 30 Aug 2005 11:33:58 +1000 Received: from [192.168.1.54] (helo=kennedy.flamingspork.com) by saturn with esmtp (Exim 3.36 #1 (Debian)) id 1E9vwg-00068t-00; Tue, 30 Aug 2005 12:33:54 +1000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by kennedy.flamingspork.com (Postfix) with ESMTP id 7816C1C47DCA; Tue, 30 Aug 2005 11:25:29 +1000 (EST) Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? From: Stewart Smith To: Jon Lewis Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <20050828144634.43837.qmail@web34110.mail.mud.yahoo.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-5l/LOlnxnKQd4CyRhI/3" Date: Tue, 30 Aug 2005 11:25:28 +1000 Message-Id: <1125365128.6439.88.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.2.1.1 X-archive-position: 5997 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stewart@flamingspork.com Precedence: bulk X-list: linux-xfs Content-Length: 1896 Lines: 54 --=-5l/LOlnxnKQd4CyRhI/3 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2005-08-29 at 13:51 -0400, Jon Lewis wrote: > huh? From what I've read, ext3 can handle up to 4TB filesystems. What= =20 > problems do you run into with >1TB, but <4TB? I realize, XFS being 64-bi= t=20 > means it can have filesystems of inconceivable size...but after recent=20 > threads on this list about how xfs_repair needs considerable RAM in order= =20 > to repair large fs's, abusing XFS's fs size limit seems a really bad idea= .=20 > You may end up with a damaged fs that requires 128gb of RAM to repair.=20 > Then what will you do with that multi-TB damaged fs? the fsck times and memory requirements aren't just an XFS thing. They affect everyone. It's just that there's more multi TB XFS filesystems out there. (It's also not just filesystems that are affected by this - think about databases too. There's a lot more rows in a database then there are files on a filesystem). For the time being, at certain sizes, people just have to get used to the idea that if you ever have to run a consistency check it's either: - going to require a lot of memory or - not complete in reasonable time There's a break even point for when the research and development needed to overcome this is viable - but it's not quite yet. --=20 Stewart Smith (stewart@flamingspork.com) http://www.flamingspork.com/ --=-5l/LOlnxnKQd4CyRhI/3 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iQCVAwUAQxO1iIwDm44RooHBAQJiaQP+MC+LqcGpv6EkXx6lOX12Q7Bbkc4MjQwg CiSXsxkukmPX5G2ADFfMHPh3irUQTMCCyexwW4y3l8K67Nk48w1CybvMfRYaefR6 c3II8PjUuVB0LLuHi5UocYLkltqVWshe3jgyZ7YxWn8LR1oiuEx3KhJIYkYWfNav ueRVRPiMkQU= =s1tO -----END PGP SIGNATURE----- --=-5l/LOlnxnKQd4CyRhI/3-- From owner-linux-xfs@oss.sgi.com Tue Aug 30 11:23:42 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Aug 2005 11:23:46 -0700 (PDT) Received: from mail.max-t.com (h216-18-124-229.gtcust.grouptelecom.net [216.18.124.229]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7UINgiL009766 for ; Tue, 30 Aug 2005 11:23:42 -0700 Received: from localhost ([127.0.0.1] helo=ftp.max-t.com) by mail.max-t.com with esmtp (Exim 4.44) id 1EAAjO-0006fH-G2; Tue, 30 Aug 2005 14:21:10 -0400 Received: from 192.168.1.140 (SquirrelMail authenticated user arajekar); by ftp.max-t.com with HTTP; Tue, 30 Aug 2005 14:21:10 -0400 (EDT) Message-ID: <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> Date: Tue, 30 Aug 2005 14:21:10 -0400 (EDT) Subject: application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT From: "Ashutosh Rajekar" To: linux-xfs@oss.sgi.com, help@myri.com Cc: ocrete@max-t.com User-Agent: SquirrelMail/1.4.3a-11.EL3.centos.1 X-Mailer: SquirrelMail/1.4.3a-11.EL3.centos.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-SA-Exim-Connect-IP: 127.0.0.1 X-SA-Exim-Mail-From: arajekar@max-t.com X-SA-Exim-Scanned: No (on mail.max-t.com); SAEximRunCond expanded to false X-archive-position: 6000 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: arajekar@max-t.com Precedence: bulk X-list: linux-xfs Content-Length: 1513 Lines: 38 Hi, We are running into a peculiar case of not being able to read files off of an XFS filesystem anymore. This used to work earlier for us when we were using a combination of linux kernel 2.4.27 (on RedHat 9.0) with GM 2.0.21. We recently changed the distribution to Centos 4.1, and are using kernel version 2.6.12.1. The hardware platform is a Dell 2650, connected via a LSI Logic FC929 host bus adaptor to an Adaptec Eurologic FC2502. The application opens a GM port, and registers a few blocks of about 516K memory using gm_dma_malloc(). The same buffers are used to write data to and read from files residing on an XFS filesystem, created using parameters "/sbin/mkfs.xfs -f -i size=2048 -d agsize=4193792k -l version=2,su=64k,size=128m /dev/sdc". The application tries to write and read data using a 4K aligned offset inside the 516K buffer, and does this using O_DIRECT. Writing works fine, but reading a buffer back simple hangs that thread process, inside a call to "filp->f_op->read( ...)". Disabling the O_DIRECT flag makes things work fine. Using standard memory allocated (i.e. memory not registered with GM using gm_dma_malloc()) using a malloc() or a posix_memalign() makes sure it works fine too. I am guessing this is an issue between gm_dma_malloc() pinning and locking the memory for DMA transfers; and XFS not being able to handle memory page locking/pinning when initiation a DIRECT I/O from that buffer, but only when reading. Any clues or suggestions? Thanks and regards, Ashutosh From owner-linux-xfs@oss.sgi.com Tue Aug 30 11:29:32 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Aug 2005 11:29:41 -0700 (PDT) Received: from pentafluge.infradead.org (pentafluge.infradead.org [213.146.154.40]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7UITViL010656 for ; Tue, 30 Aug 2005 11:29:32 -0700 Received: from hch by pentafluge.infradead.org with local (Exim 4.52 #1 (Red Hat Linux)) id 1EAAp6-0000Sn-7O; Tue, 30 Aug 2005 19:27:04 +0100 Date: Tue, 30 Aug 2005 19:27:04 +0100 From: Christoph Hellwig To: Ashutosh Rajekar Cc: linux-xfs@oss.sgi.com, help@myri.com, ocrete@max-t.com Subject: Re: application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT Message-ID: <20050830182704.GA1761@infradead.org> References: <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> User-Agent: Mutt/1.4.2.1i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html X-archive-position: 6001 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Content-Length: 469 Lines: 11 On Tue, Aug 30, 2005 at 02:21:10PM -0400, Ashutosh Rajekar wrote: > Hi, > > We are running into a peculiar case of not being able to read files off of > an XFS filesystem anymore. This used to work earlier for us when we were > using a combination of linux kernel 2.4.27 (on RedHat 9.0) with GM 2.0.21. > We recently changed the distribution to Centos 4.1, and are using kernel > version 2.6.12.1. Whaterever "GM" is, it's memory allocator is doing something buggy. From owner-linux-xfs@oss.sgi.com Tue Aug 30 12:17:59 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Aug 2005 12:18:03 -0700 (PDT) Received: from myri.com (h-66-166-126-70.lsanca54.covad.net [66.166.126.70]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7UJHwiL013651 for ; Tue, 30 Aug 2005 12:17:58 -0700 Received: from sw.sw.myri.com (sw.sw.myri.com [172.31.128.1]) by myri.com (8.12.9+Sun/8.12.9) with ESMTP id j7UJFJ7J006240; Tue, 30 Aug 2005 12:15:19 -0700 (PDT) Received: from idefix.sw.myri.com ([172.31.161.2]) by sw.sw.myri.com with esmtp (Exim 3.36 #1 (Debian)) id 1EABZo-00051f-00; Tue, 30 Aug 2005 12:15:20 -0700 Message-ID: <4314B047.1000002@myri.com> Date: Tue, 30 Aug 2005 15:15:19 -0400 From: Myricom Technical Support Organization: Myricom, Inc. User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ashutosh Rajekar CC: linux-xfs@oss.sgi.com, ocrete@max-t.com, Myricom Technical Support Subject: Re: [Myricom help #36078] application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT References: <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> In-Reply-To: <44876.192.168.1.140.1125426070.squirrel@ftp.max-t.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 6002 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: help@myri.com Precedence: bulk X-list: linux-xfs Content-Length: 894 Lines: 27 Hi, Ashutosh, > Disabling the O_DIRECT flag makes things work fine. Using standard memory > allocated (i.e. memory not registered with GM using gm_dma_malloc()) using > a malloc() or a posix_memalign() makes sure it works fine too. > > I am guessing this is an issue between gm_dma_malloc() pinning and locking > the memory for DMA transfers; and XFS not being able to handle memory page > locking/pinning when initiation a DIRECT I/O from that buffer, but only > when reading. Yes, this is a fundamental problem of conflictual use between O_DIRECT and memory registration in GM. (We are surprised to hear that this ever worked with some Linux kernels.) I have forwarded your question to our GM software developers, and they are pondering ways of allocating the initial memory differently that may allow this to work. Susan -- Susan Blackford Member of Technical Staff Myricom Inc. From owner-linux-xfs@oss.sgi.com Tue Aug 30 13:18:40 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Aug 2005 13:18:46 -0700 (PDT) Received: from omx1.americas.sgi.com (omx1-ext.sgi.com [192.48.179.11]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7UKIeiL022030 for ; Tue, 30 Aug 2005 13:18:40 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [198.149.16.15]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7UKGCxT012418 for ; Tue, 30 Aug 2005 15:16:12 -0500 Received: from [128.162.232.50] (stout.americas.sgi.com [128.162.232.50]) by flecktone.americas.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7UKGBDN15057624; Tue, 30 Aug 2005 15:16:11 -0500 (CDT) Message-ID: <4314BE8B.40305@sgi.com> Date: Tue, 30 Aug 2005 15:16:11 -0500 From: Eric Sandeen User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jon Lewis CC: linux-xfs@oss.sgi.com Subject: Re: Will we ever see XFS supported in Red Hat Enterprise Linux? References: <20050828144634.43837.qmail@web34110.mail.mud.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 6003 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 585 Lines: 19 Jon Lewis wrote: > On Sun, 28 Aug 2005, Bryan J. Smith wrote: > >> To be honest, I haven't been deploying XFS as much since the >> official XFS 1.2 on Red Hat Linux 7.x (plus one 1.3 on Red >> Hat Linux 9). The Red Hat Linux 7.x installs definitely have >> the most time, and I very much trust and appreciate its >> availability. > > > If these releases were so stable, could someone from SGI please put them > back up on the oss.sgi.com FTP server? ftp://oss.sgi.com/projects/xfs/README & associated fallout. Older revisions are no longer available from oss.sgi.com. -Eric From owner-linux-xfs@oss.sgi.com Tue Aug 30 15:56:22 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Aug 2005 15:56:28 -0700 (PDT) Received: from myri.com (h-66-166-126-70.lsanca54.covad.net [66.166.126.70]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7UMuLiL001213 for ; Tue, 30 Aug 2005 15:56:21 -0700 Received: from sw.sw.myri.com (sw.sw.myri.com [172.31.128.1]) by myri.com (8.12.9+Sun/8.12.9) with ESMTP id j7UMrd7J019477; Tue, 30 Aug 2005 15:53:40 -0700 (PDT) Received: from susan-home.sw.myri.com ([172.31.194.51]) by sw.sw.myri.com with esmtp (Exim 3.36 #1 (Debian)) id 1EAEz7-0001cW-00; Tue, 30 Aug 2005 15:53:41 -0700 Message-ID: <4314E374.4060002@myri.com> Date: Tue, 30 Aug 2005 18:53:40 -0400 From: Myricom Technical Support Organization: Myricom, Inc. User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: arajekar@max-t.com CC: linux-xfs@oss.sgi.com, ocrete@max-t.com, Myricom Technical Support Subject: Re: [Myricom help #36078] application sleeps indefinitely trying to read gm_dma_malloc'ed buffer through O_DIRECT]] Content-Type: multipart/mixed; boundary="------------080104020907030505000807" X-archive-position: 6004 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: help@myri.com Precedence: bulk X-list: linux-xfs Content-Length: 3174 Lines: 111 This is a multi-part message in MIME format. --------------080104020907030505000807 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Ashutosh, From one of our GM software developers: I suggest they try the attached patch which should solve their problem. Basically the incompatibility is that gm-registration of any "process-private" memory requires the gm driver to lock the corresponding pages for the duration of the registration (which is the life of the gm-port for gm_dma_malloc() buffers). During that time those pages cannot be used for reading through O_DIRECT (because O_DIRECT also requires obtaining a lock on the pages at some point). The patch changes gm_dma_malloc() to allocate memory with map(MAP_SHARED|MAP_ANONYMOUS). The gm-registration of such pages does not require a lock and should be compatible with any O_DIRECT activity (or any other activity that we can think of at this point). Note that this patch potentially introduces a small semantic change for programs that uses fork(), but should not be a problem as we don't expect programs using forks() to rely on any specific sharing semantics for the gm_dma_malloc'ed() buffers. Please apply this patch to GM-2 and let us know how this works for you. Thanks, Susan -- Susan Blackford Member of Technical Staff Myricom Inc. --------------080104020907030505000807 Content-Type: text/x-patch; name="dma-odirect.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dma-odirect.patch" Index: libgm/gm_dma_malloc.c =================================================================== RCS file: /repository/gm/libgm/gm_dma_malloc.c,v retrieving revision 1.8.22.1 diff -u -r1.8.22.1 gm_dma_malloc.c --- libgm/gm_dma_malloc.c 28 May 2004 19:09:10 -0000 1.8.22.1 +++ libgm/gm_dma_malloc.c 30 Aug 2005 20:55:55 -0000 @@ -246,6 +246,26 @@ } #endif /* GM_KERNEL */ + +#if GM_KERNEL || !GM_OS_LINUX +#define gm_alloc_pages_for_dma gm_alloc_pages +#define gm_alloc_free_pages_for_dma gm_free_pages +#else +#include + +void *gm_alloc_pages_for_dma(gm_size_t length) +{ + void * ptr = mmap(0, length, PROT_READ | PROT_WRITE, MAP_SHARED | MAP_ANONYMOUS, -1, 0); + return (ptr == MAP_FAILED) ? 0 : ptr; +} + +void gm_free_pages_for_dma(void *addr, gm_size_t length) +{ + munmap(addr, length); +} +#endif + + /**************************************************************** * Environment abstraction * @@ -272,7 +292,7 @@ /* allocate some pages */ - addr = gm_alloc_pages (length); + addr = gm_alloc_pages_for_dma (length); if (addr == 0) { status = GM_OUT_OF_MEMORY; @@ -300,7 +320,7 @@ GM_RETURN_STATUS (GM_SUCCESS); abort_with_pages: - gm_free_pages (addr, length); + gm_free_pages_for_dma (addr, length); abort_with_nothing: GM_RETURN_STATUS (status); } @@ -447,7 +467,7 @@ #if !GM_KERNEL && GM_CAN_REGISTER_MEMORY { gm_deregister_memory (p, ptr, length); - gm_free_pages (ptr, length); + gm_free_pages_for_dma (ptr, length); } #elif !GM_KERNEL && !GM_CAN_REGISTER_MEMORY { --------------080104020907030505000807-- From owner-linux-xfs@oss.sgi.com Wed Aug 31 01:40:42 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 01:40:53 -0700 (PDT) Received: from omx2.sgi.com (omx2-ext.sgi.com [192.48.171.19]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7V8efiL025680 for ; Wed, 31 Aug 2005 01:40:42 -0700 Received: from internal-mail-relay.corp.sgi.com (internal-mail-relay.corp.sgi.com [198.149.32.51]) by omx2.sgi.com (8.12.11/8.12.9/linux-outbound_gateway-1.1) with ESMTP id j7VAc3Q5018247 for ; Wed, 31 Aug 2005 03:38:03 -0700 Received: from cuda.sgi.com (cuda2.sgi.com [192.48.168.29]) by internal-mail-relay.corp.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id j7V8bv2Z262793517 for ; Wed, 31 Aug 2005 01:37:57 -0700 (PDT) X-ASG-Debug-ID: 1125477476-21202-21-0 X-Barracuda-URL: http://cuda.sgi.com:80/cgi-bin/mark.cgi Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by cuda.sgi.com (Spam Firewall) with ESMTP id 10B47D056989 for ; Wed, 31 Aug 2005 01:37:56 -0700 (PDT) Received: from naboo.americas.sgi.com (localhost [127.0.0.1]) by naboo.americas.sgi.com (8.13.3/8.13.3) with ESMTP id j7V8bsFY006492; Wed, 31 Aug 2005 03:37:55 -0500 Received: (from hch@localhost) by naboo.americas.sgi.com (8.13.3/8.13.3/Submit) id j7V8bqI6006491; Wed, 31 Aug 2005 03:37:52 -0500 Date: Wed, 31 Aug 2005 03:37:52 -0500 From: Christoph Hellwig Message-Id: <200508310837.j7V8bqI6006491@naboo.americas.sgi.com> To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@fido.engr.sgi.com X-ASG-Orig-Subj: PARTIAL TAKE 942063 - Switch kernel thread handling to the kthread_ API Subject: PARTIAL TAKE 942063 - Switch kernel thread handling to the kthread_ API X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=3.5 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=9.0 tests= X-Barracuda-Spam-Report: Code version 3.02, rules version 3.0.3611 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-archive-position: 6006 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@relay.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 872 Lines: 19 Date: Wed Aug 31 01:37:36 PDT 2005 Workarea: naboo.americas.sgi.com:/go/space/hch/xfs-2.6.x Inspected by: nathans The following file(s) were checked into: bonnie.engr.sgi.com:/isms/linux/2.6.x-xfs Modid: xfs-linux:xfs-kern:198388a fs/xfs/linux-2.6/xfs_vfs.h - 1.53 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vfs.h.diff?r1=text&tr1=1.53&r2=text&tr2=1.52&f=h fs/xfs/linux-2.6/xfs_vfs.c - 1.64 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_vfs.c.diff?r1=text&tr1=1.64&r2=text&tr2=1.63&f=h fs/xfs/linux-2.6/xfs_super.c - 1.342 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_super.c.diff?r1=text&tr1=1.342&r2=text&tr2=1.341&f=h fs/xfs/linux-2.6/xfs_buf.c - 1.203 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_buf.c.diff?r1=text&tr1=1.203&r2=text&tr2=1.202&f=h From owner-linux-xfs@oss.sgi.com Wed Aug 31 10:41:16 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 10:41:22 -0700 (PDT) Received: from poczta.eisp.pl (eisp.pl [70.85.58.164]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VHfGiL009824 for ; Wed, 31 Aug 2005 10:41:16 -0700 Received: by poczta.eisp.pl (Postfix, from userid 2264) id 9D1DD69AA3F; Wed, 31 Aug 2005 19:38:42 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by poczta.eisp.pl (Postfix) with ESMTP id 98EA94846398 for ; Wed, 31 Aug 2005 19:38:42 +0200 (CEST) Date: Wed, 31 Aug 2005 19:38:42 +0200 (CEST) From: Kamil Kaczkowski X-X-Sender: kamil@virgo To: linux-xfs@oss.sgi.com Subject: 2.4.31 xfs oopses Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 6007 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: K.Kaczkowski@eisp.pl Precedence: bulk X-list: linux-xfs Content-Length: 5366 Lines: 143 Hello. I've experienced frequent system crashes on Linux 2.4.31(Debian Woody, 2 x Xeon, scsi) lately. Unfortunately I'm unable to run memtest right now(24h production server), so it's possible that the hardware is to blame, however I decided to post oopses here in hope that some of the xfs gurus here can comment on the possibility that this is something else than bad hardware. 2 oopses included below happened in almost the same conditions(backup running, high i/o load). Filesystems has been checked with xfs_check, no problems found. Thanks in advance for all help. oops1: Unable to handle kernel paging request at virtual address f908492c c01701eb000000031d75063 *pgd = 0000000031d75063 Oops: 0002 CPU: 0010:[] Not tainted EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010046ebx: 0173fe45 ecx: f3385000 edx: 00000034 eax: 4c2e646f ebx: 0173fe45 ecx: f3385000 edx: 00000034 esi: c281d310 edi: 0000002a ebp: c285bb50 esp: c2855e00 ds: 0018 es: 0018 ss: 0018age=c2855000) Process kswapd (pid: 7, stackpage=c2855000)00000000 c281d318 c281d320 c0170628 Stack: c285b800 d28b4d80 00000282 00000001 00000000 c281d318 c281d320 c0170628 c281d310 c285ba00 0000007e ea172ae0 ea172a90 00000000 d28b4d80 c02186d5 d28b4d80 c01ef27f d28b4d80 00000060 ea172a90 c485db00 f73de270 c01ef2ef Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 89 44 99 18 89 59 14 8b 41 10 8d 50 ff 89 51 10 83 f8 01 75 >>EIP; c01701eb <===== >>eax; 4c2e646f Before first symbol >>ebx; 0173fe45 Before first symbol >>ecx; f3385000 <_end+32f9dbec/384bebec> >>esi; c281d310 <_end+2435efc/384bebec> >>ebp; c285bb50 <_end+247473c/384bebec> >>esp; c2855e00 <_end+246e9ec/384bebec> Trace; c0170628 Trace; c02186d5 Trace; c01ef27f Trace; c01ef2ef Trace; c01eb8b1 Trace; c020af2c Trace; c020ada5 Trace; c0215063 Trace; c02154d9 Trace; c0208176 Trace; c0208084 Trace; c02155f3 Trace; c021408a Trace; c01908fe Trace; c0190bc9 Trace; c0190d37 Trace; c0171e78 Trace; c0171fce Trace; c0172036 Trace; c017214d Trace; c0145890 Code; c01701eb 00000000 <_EIP>: Code; c01701eb <===== 0: 89 44 99 18 mov %eax,0x18(%ecx,%ebx,4) <===== Code; c01701ef 4: 89 59 14 mov %ebx,0x14(%ecx) Code; c01701f2 7: 8b 41 10 mov 0x10(%ecx),%eax Code; c01701f5 a: 8d 50 ff lea 0xffffffff(%eax),%edx Code; c01701f8 d: 89 51 10 mov %edx,0x10(%ecx) Code; c01701fb 10: 83 f8 01 cmp $0x1,%eax Code; c01701fe 13: 75 00 jne 15 <_EIP+0x15> c0170200 oops2: Unable to handle kernel paging request at virtual address 30c9c439 c01eb12e *pgd = 0000000000000000 Oops: 0000 CPU: 2 EIP: 0010:[xfs_iget_core+98/1216] Not tainted EFLAGS: 00010202 eax: 30c9c401 ebx: f73fc33c ecx: f73c0c00 edx: 0f844a71 esi: f6e1c000 edi: 00000002 ebp: f73c0d28 esp: f6e1de14 ds: 0018 es: 0018 ss: 0018 Process php (pid: 2603, stackpage=f6e1d000) Stack: d39f9b00 d39f9b20 00000000 f73c0c00 f73fc340 30c9c401 c01eb600 d39f9b00 f73c0c00 00000000 0f844a71 00000000 00000000 00000000 f6e1dedc 00000000 00000000 d39f9b20 00000000 f1ef4d40 f1ef4d60 f6e1dedc c0203b29 f73c0c00 Call Trace: [xfs_iget+116/340] [xfs_dir_lookup_int+101/208] [xfs_lookup+62/104] [linvfs_lookup+63/132] [real_lookup+122/268] Code: 39 50 38 0f 85 29 01 00 00 8b 4c 24 2c 39 48 3c 0f 85 1c 01 >>eax; 30c9c401 Before first symbol >>ebx; f73fc33c <_end+37014f28/384bebec> >>ecx; f73c0c00 <_end+36fd97ec/384bebec> >>edx; 0f844a71 Before first symbol >>esi; f6e1c000 <_end+36a34bec/384bebec> >>ebp; f73c0d28 <_end+36fd9914/384bebec> >>esp; f6e1de14 <_end+36a36a00/384bebec> Code; 00000000 Before first symbol 00000000 <_EIP>: Code; 00000000 Before first symbol 0: 39 50 38 cmp %edx,0x38(%eax) Code; 00000003 Before first symbol 3: 0f 85 29 01 00 00 jne 132 <_EIP+0x132> 00000132 Before first symbol Code; 00000009 Before first symbol 9: 8b 4c 24 2c mov 0x2c(%esp,1),%ecx Code; 0000000d Before first symbol d: 39 48 3c cmp %ecx,0x3c(%eax) Code; 00000010 Before first symbol 10: 0f 85 1c 01 00 00 jne 132 <_EIP+0x132> 00000132 Before first symbol -- Kamil Kaczkowski K.Kaczkowski@eisp.pl From owner-linux-xfs@oss.sgi.com Wed Aug 31 13:54:55 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 13:55:01 -0700 (PDT) Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VKssiL025516 for ; Wed, 31 Aug 2005 13:54:55 -0700 Received: from localhost.localdomain (leviathan [131.128.51.64]) by leviathan.ele.uri.edu (8.12.9/8.12.9) with ESMTP id j7VKqO4r015217; Wed, 31 Aug 2005 16:52:24 -0400 (EDT) Subject: how to defragment xfs? From: Ming Zhang Reply-To: mingz@ele.uri.edu To: xfs Content-Type: text/plain Organization: no-dole-available Date: Wed, 31 Aug 2005 16:52:23 -0400 Message-Id: <1125521544.6617.45.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-archive-position: 6009 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mingz@ele.uri.edu Precedence: bulk X-list: linux-xfs Content-Length: 66 Lines: 9 Hi folks I wonder how I can defragment the xfs? Thanks! Ming From owner-linux-xfs@oss.sgi.com Wed Aug 31 14:54:20 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 14:54:26 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7VLsJiL028593 for ; Wed, 31 Aug 2005 14:54:19 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id HAA18751; Thu, 1 Sep 2005 07:51:44 +1000 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7VLpMg815850892; Thu, 1 Sep 2005 07:51:22 +1000 (EST) Received: (from dgc@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7VLpKAf15798974; Thu, 1 Sep 2005 07:51:20 +1000 (EST) Date: Thu, 1 Sep 2005 07:51:20 +1000 From: David Chinner To: Ming Zhang Cc: xfs Subject: Re: how to defragment xfs? Message-ID: <20050831215120.GA16009129@melbourne.sgi.com> References: <1125521544.6617.45.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1125521544.6617.45.camel@localhost.localdomain> User-Agent: Mutt/1.4.1i X-archive-position: 6010 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dgc@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 354 Lines: 19 On Wed, Aug 31, 2005 at 04:52:23PM -0400, Ming Zhang wrote: > Hi folks > > I wonder how I can defragment the xfs? Ob-FAQ: Google is your friend: http://www.google.com/search?q=how+to+defragment+XFS xfs_fsr(8) is what you want - it's in the xfsdump package IIRC... Cheers, Dave. -- Dave Chinner R&D Software Enginner SGI Australian Software Group From owner-linux-xfs@oss.sgi.com Wed Aug 31 14:58:07 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 14:58:13 -0700 (PDT) Received: from mail.linux-sxs.org (mail.linux-sxs.org [64.116.183.6]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VLw4iL029137 for ; Wed, 31 Aug 2005 14:58:06 -0700 Received: from mail.linux-sxs.org (localhost [127.0.0.1]) by mail.linux-sxs.org (8.13.4/8.13.4/Debian-3) with ESMTP id j7VKrrIA014660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 31 Aug 2005 15:53:55 -0500 Received: from localhost (netllama@localhost) by mail.linux-sxs.org (8.13.4/8.13.4/Submit) with ESMTP id j7VKrrYv014657; Wed, 31 Aug 2005 15:53:53 -0500 X-Authentication-Warning: mail.linux-sxs.org: netllama owned process doing -bs Date: Wed, 31 Aug 2005 15:53:53 -0500 (EST) From: Lonni J Friedman To: David Chinner cc: xfs Subject: Re: how to defragment xfs? In-Reply-To: <20050831215120.GA16009129@melbourne.sgi.com> Message-ID: References: <1125521544.6617.45.camel@localhost.localdomain> <20050831215120.GA16009129@melbourne.sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: milter-sender/0.62.837 (localhost [127.0.0.1]); Wed, 31 Aug 2005 15:53:55 -0500 Received-SPF: pass (mail.linux-sxs.org: domain of netllama@linux-sxs.org designates 127.0.0.1 as permitted sender) receiver=mail.linux-sxs.org; client-ip=127.0.0.1; helo=mail.linux-sxs.org; envelope-from=netllama@linux-sxs.org; x-software=spfmilter 0.95 http://www.acme.com/software/spfmilter/ with libspf2; X-archive-position: 6011 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 582 Lines: 19 On Thu, 1 Sep 2005, David Chinner wrote: > On Wed, Aug 31, 2005 at 04:52:23PM -0400, Ming Zhang wrote: > > Hi folks > > > > I wonder how I can defragment the xfs? > > Ob-FAQ: Google is your friend: > > http://www.google.com/search?q=how+to+defragment+XFS > > xfs_fsr(8) is what you want - it's in the xfsdump package IIRC... And that assumes that you need to defragment your fs in the first place. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org LlamaLand http://netllama.linux-sxs.org From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:04:52 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:04:58 -0700 (PDT) Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VM4piL029743 for ; Wed, 31 Aug 2005 15:04:52 -0700 Received: from localhost.localdomain (leviathan [131.128.51.64]) by leviathan.ele.uri.edu (8.12.9/8.12.9) with ESMTP id j7VM2J4r016871; Wed, 31 Aug 2005 18:02:20 -0400 (EDT) Subject: Re: how to defragment xfs? From: Ming Zhang Reply-To: mingz@ele.uri.edu To: David Chinner Cc: xfs In-Reply-To: <20050831215120.GA16009129@melbourne.sgi.com> References: <1125521544.6617.45.camel@localhost.localdomain> <20050831215120.GA16009129@melbourne.sgi.com> Content-Type: text/plain Organization: no-dole-available Date: Wed, 31 Aug 2005 18:02:18 -0400 Message-Id: <1125525738.6617.69.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-archive-position: 6012 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mingz@ele.uri.edu Precedence: bulk X-list: linux-xfs Content-Length: 1995 Lines: 74 Thanks all! My fault. I remember there is a command for xfs or reiserfs to do this and i can not figure out the name. then i check xfs_* on my box and none of them doing this job. so i assumed it is for reiserfs. it is quite weired that my FC box does not have this command in xfsprogs. [mingz@amd64 ~]$ rpm -q xfsprogs xfsprogs-2.6.13-2 [mingz@amd64 ~]$ rpm -ql xfsprogs /lib64/libhandle.so.1 /lib64/libhandle.so.1.0.3 /sbin/fsck.xfs /sbin/mkfs.xfs /sbin/xfs_repair /usr/sbin/xfs_admin /usr/sbin/xfs_bmap /usr/sbin/xfs_check /usr/sbin/xfs_copy /usr/sbin/xfs_db /usr/sbin/xfs_freeze /usr/sbin/xfs_growfs /usr/sbin/xfs_info /usr/sbin/xfs_io /usr/sbin/xfs_logprint /usr/sbin/xfs_mkfile /usr/sbin/xfs_ncheck /usr/sbin/xfs_rtcp /usr/share/doc/xfsprogs-2.6.13 /usr/share/doc/xfsprogs-2.6.13/CHANGES /usr/share/doc/xfsprogs-2.6.13/COPYING /usr/share/doc/xfsprogs-2.6.13/CREDITS /usr/share/doc/xfsprogs-2.6.13/PORTING /usr/share/doc/xfsprogs-2.6.13/README /usr/share/doc/xfsprogs-2.6.13/README.LVM /usr/share/doc/xfsprogs-2.6.13/README.quota /usr/share/man/man5/xfs.5.gz /usr/share/man/man8/fsck.xfs.8.gz /usr/share/man/man8/mkfs.xfs.8.gz /usr/share/man/man8/xfs_admin.8.gz /usr/share/man/man8/xfs_bmap.8.gz /usr/share/man/man8/xfs_check.8.gz /usr/share/man/man8/xfs_copy.8.gz /usr/share/man/man8/xfs_db.8.gz /usr/share/man/man8/xfs_freeze.8.gz /usr/share/man/man8/xfs_growfs.8.gz /usr/share/man/man8/xfs_info.8.gz /usr/share/man/man8/xfs_io.8.gz /usr/share/man/man8/xfs_logprint.8.gz /usr/share/man/man8/xfs_mkfile.8.gz /usr/share/man/man8/xfs_ncheck.8.gz /usr/share/man/man8/xfs_repair.8.gz /usr/share/man/man8/xfs_rtcp.8.gz On Thu, 2005-09-01 at 07:51 +1000, David Chinner wrote: > On Wed, Aug 31, 2005 at 04:52:23PM -0400, Ming Zhang wrote: > > Hi folks > > > > I wonder how I can defragment the xfs? > > Ob-FAQ: Google is your friend: > > http://www.google.com/search?q=how+to+defragment+XFS > > xfs_fsr(8) is what you want - it's in the xfsdump package IIRC... > > Cheers, > > Dave. From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:10:52 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:10:57 -0700 (PDT) Received: from FPNYEXCBE01.opus-i.corp (mail4.opus-i.net [209.10.181.136]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VMApiL030628 for ; Wed, 31 Aug 2005 15:10:52 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: how to defragment xfs? Date: Wed, 31 Aug 2005 18:08:16 -0400 Message-ID: <14BC3454F4B4614FBC4F3FB19A84C3720D4666@FPNYEXCBE01.opus-i.corp> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: how to defragment xfs? Thread-Index: AcWudsuAZntAmY43RryX2MKkBTIKSwAATlqw From: "Allan Haywood" To: "Lonni J Friedman" , "David Chinner" Cc: "xfs" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7VMAqiL030630 X-archive-position: 6013 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: allanh@datallegro.com Precedence: bulk X-list: linux-xfs Content-Length: 864 Lines: 39 On Thu, 1 Sep 2005, David Chinner wrote: > On Wed, Aug 31, 2005 at 04:52:23PM -0400, Ming Zhang wrote: > > Hi folks > > > > I wonder how I can defragment the xfs? > > Ob-FAQ: Google is your friend: > > http://www.google.com/search?q=how+to+defragment+XFS > > xfs_fsr(8) is what you want - it's in the xfsdump package IIRC... And that assumes that you need to defragment your fs in the first place. ---------------------------- You can use the following command to check fragmentation: xfs_db -c frag -r /dev/md0 replace /dev/md0 with the name of the device you want to check. This is what the output will look like: actual 184, ideal 176, fragmentation factor 4.35% Allan Haywood Data Warehouse Systems Specialist DATAllegro 65 Enterprise Aliso Viejo, CA 92656 949.330.7633 direct 949.330.7691 fax E-mail: allanh@datallegro.com Web: www.Datallegro.com From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:21:01 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:21:06 -0700 (PDT) Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VML1iL031345 for ; Wed, 31 Aug 2005 15:21:01 -0700 Received: from localhost.localdomain (leviathan [131.128.51.64]) by leviathan.ele.uri.edu (8.12.9/8.12.9) with ESMTP id j7VMHt4r017175; Wed, 31 Aug 2005 18:17:55 -0400 (EDT) Subject: RE: how to defragment xfs? From: Ming Zhang Reply-To: mingz@ele.uri.edu To: Allan Haywood Cc: Lonni J Friedman , David Chinner , xfs In-Reply-To: <14BC3454F4B4614FBC4F3FB19A84C3720D4666@FPNYEXCBE01.opus-i.corp> References: <14BC3454F4B4614FBC4F3FB19A84C3720D4666@FPNYEXCBE01.opus-i.corp> Content-Type: text/plain Organization: no-dole-available Date: Wed, 31 Aug 2005 18:17:55 -0400 Message-Id: <1125526675.6617.76.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-archive-position: 6014 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mingz@ele.uri.edu Precedence: bulk X-list: linux-xfs Content-Length: 1085 Lines: 50 On Wed, 2005-08-31 at 18:08 -0400, Allan Haywood wrote: > On Thu, 1 Sep 2005, David Chinner wrote: > > On Wed, Aug 31, 2005 at 04:52:23PM -0400, Ming Zhang wrote: > > > Hi folks > > > > > > I wonder how I can defragment the xfs? > > > > Ob-FAQ: Google is your friend: > > > > http://www.google.com/search?q=how+to+defragment+XFS > > > > xfs_fsr(8) is what you want - it's in the xfsdump package IIRC... > > And that assumes that you need to defragment your fs in the first place. > thanks! how to defragment the whole FS? this is only to check fragment right? > ---------------------------- > > You can use the following command to check fragmentation: > > xfs_db -c frag -r /dev/md0 > > replace /dev/md0 with the name of the device you want to check. > > This is what the output will look like: > > actual 184, ideal 176, fragmentation factor 4.35% > > > Allan Haywood > Data Warehouse Systems Specialist > DATAllegro > 65 Enterprise > Aliso Viejo, CA 92656 > 949.330.7633 direct > 949.330.7691 fax > E-mail: allanh@datallegro.com > Web: www.Datallegro.com > > > > From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:38:52 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:38:58 -0700 (PDT) Received: from larry.melbourne.sgi.com (mverd138.asia.info.net [61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id j7VMcpiL032633 for ; Wed, 31 Aug 2005 15:38:51 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA19855; Thu, 1 Sep 2005 08:36:17 +1000 Received: from wobbly.melbourne.sgi.com (localhost [127.0.0.1]) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id j7VMaRkt4461043; Thu, 1 Sep 2005 08:36:27 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id j7VMaPMn4459731; Thu, 1 Sep 2005 08:36:25 +1000 (EST) Date: Thu, 1 Sep 2005 08:36:25 +1000 From: Nathan Scott To: Ming Zhang Cc: xfs Subject: Re: how to defragment xfs? Message-ID: <20050901083625.A4424896@wobbly.melbourne.sgi.com> References: <1125521544.6617.45.camel@localhost.localdomain> <20050831215120.GA16009129@melbourne.sgi.com> <1125525738.6617.69.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1125525738.6617.69.camel@localhost.localdomain>; from mingz@ele.uri.edu on Wed, Aug 31, 2005 at 06:02:18PM -0400 X-archive-position: 6015 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 434 Lines: 17 On Wed, Aug 31, 2005 at 06:02:18PM -0400, Ming Zhang wrote: > Thanks all! > > My fault. I remember there is a command for xfs or reiserfs to do this > and i can not figure out the name. then i check xfs_* on my box and none > of them doing this job. so i assumed it is for reiserfs. > > it is quite weired that my FC box does not have this command in > xfsprogs. Its in the "xfsdump" package, not "xfsprogs". cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:40:46 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:40:57 -0700 (PDT) Received: from FPNYEXCBE01.opus-i.corp (mail4.opus-i.net [209.10.181.136]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VMekiL000577 for ; Wed, 31 Aug 2005 15:40:46 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: how to defragment xfs? Date: Wed, 31 Aug 2005 18:38:12 -0400 Message-ID: <14BC3454F4B4614FBC4F3FB19A84C3720D466B@FPNYEXCBE01.opus-i.corp> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: how to defragment xfs? Thread-Index: AcWuefHJ0pPk5aQPR1K0F5rBsjkmTgAAo/ow From: "Allan Haywood" To: Cc: "Lonni J Friedman" , "David Chinner" , "xfs" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7VMekiL000579 X-archive-position: 6016 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: allanh@datallegro.com Precedence: bulk X-list: linux-xfs Content-Length: 706 Lines: 42 thanks! how to defragment the whole FS? this is only to check fragment right? ---------------------- Correct, it only checks, it doesn't make any changes to fragmentation at all. > ---------------------------- > > You can use the following command to check fragmentation: > > xfs_db -c frag -r /dev/md0 > > replace /dev/md0 with the name of the device you want to check. > > This is what the output will look like: > > actual 184, ideal 176, fragmentation factor 4.35% > > > Allan Haywood > Data Warehouse Systems Specialist > DATAllegro > 65 Enterprise > Aliso Viejo, CA 92656 > 949.330.7633 direct > 949.330.7691 fax > E-mail: allanh@datallegro.com > Web: www.Datallegro.com > > > > From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:41:01 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:41:05 -0700 (PDT) Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VMf1iL000629 for ; Wed, 31 Aug 2005 15:41:01 -0700 Received: from localhost.localdomain (leviathan [131.128.51.64]) by leviathan.ele.uri.edu (8.12.9/8.12.9) with ESMTP id j7VMcQ4r017738; Wed, 31 Aug 2005 18:38:28 -0400 (EDT) Subject: Re: how to defragment xfs? From: Ming Zhang Reply-To: mingz@ele.uri.edu To: Nathan Scott Cc: xfs In-Reply-To: <20050901083625.A4424896@wobbly.melbourne.sgi.com> References: <1125521544.6617.45.camel@localhost.localdomain> <20050831215120.GA16009129@melbourne.sgi.com> <1125525738.6617.69.camel@localhost.localdomain> <20050901083625.A4424896@wobbly.melbourne.sgi.com> Content-Type: text/plain Organization: no-dole-available Date: Wed, 31 Aug 2005 18:38:26 -0400 Message-Id: <1125527906.6617.78.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-archive-position: 6017 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mingz@ele.uri.edu Precedence: bulk X-list: linux-xfs Content-Length: 1172 Lines: 38 On Thu, 2005-09-01 at 08:36 +1000, Nathan Scott wrote: > On Wed, Aug 31, 2005 at 06:02:18PM -0400, Ming Zhang wrote: > > Thanks all! > > > > My fault. I remember there is a command for xfs or reiserfs to do this > > and i can not figure out the name. then i check xfs_* on my box and none > > of them doing this job. so i assumed it is for reiserfs. > > > > it is quite weired that my FC box does not have this command in > > xfsprogs. > > Its in the "xfsdump" package, not "xfsprogs". > > cheers. > [root@amd64 mingz]# yum install xfsdump Setting up Install Process Setting up Repos base 100% |=========================| 1.1 kB 00:00 updates-released 100% |=========================| 951 B 00:00 Reading repository metadata in from local files base : ################################################## 2852/2852 primary.xml.gz 100% |=========================| 445 kB 00:20 MD Read : ################################################## 1117/1117 updates-re: ################################################## 1117/1117 No Match for argument: xfsdump Nothing to do i guess my FC3 X86_64 does not have it yet. Ming From owner-linux-xfs@oss.sgi.com Wed Aug 31 15:51:02 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 15:51:06 -0700 (PDT) Received: from FPNYEXCBE01.opus-i.corp (mail4.opus-i.net [209.10.181.136]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VMooiL001870 for ; Wed, 31 Aug 2005 15:51:02 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: how to defragment xfs? Date: Wed, 31 Aug 2005 18:48:16 -0400 Message-ID: <14BC3454F4B4614FBC4F3FB19A84C3720D466E@FPNYEXCBE01.opus-i.corp> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: how to defragment xfs? Thread-Index: AcWufMh8Yd3XAnGNSl+SZkXiteJVogAAE4HQ From: "Allan Haywood" To: , "Nathan Scott" Cc: "xfs" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id j7VMp2iL001876 X-archive-position: 6018 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: allanh@datallegro.com Precedence: bulk X-list: linux-xfs Content-Length: 1511 Lines: 51 On Thu, 2005-09-01 at 08:36 +1000, Nathan Scott wrote: > On Wed, Aug 31, 2005 at 06:02:18PM -0400, Ming Zhang wrote: > > Thanks all! > > > > My fault. I remember there is a command for xfs or reiserfs to do this > > and i can not figure out the name. then i check xfs_* on my box and none > > of them doing this job. so i assumed it is for reiserfs. > > > > it is quite weired that my FC box does not have this command in > > xfsprogs. > > Its in the "xfsdump" package, not "xfsprogs". > > cheers. > [root@amd64 mingz]# yum install xfsdump Setting up Install Process Setting up Repos base 100% |=========================| 1.1 kB 00:00 updates-released 100% |=========================| 951 B 00:00 Reading repository metadata in from local files base : ################################################## 2852/2852 primary.xml.gz 100% |=========================| 445 kB 00:20 MD Read : ################################################## 1117/1117 updates-re: ################################################## 1117/1117 No Match for argument: xfsdump Nothing to do i guess my FC3 X86_64 does not have it yet. Ming ------------------ Try running "xfs_fsr" without the quotes. You don't have to unmount any file systems, or do anything special for it to run. Also the defaults should be fine for you. You can read the man page for more info on how it runs. Also try running using -v, it outputs details of what it is doing which is kinda interesting. From owner-linux-xfs@oss.sgi.com Wed Aug 31 16:46:22 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 16:46:26 -0700 (PDT) Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VNkLiL008737 for ; Wed, 31 Aug 2005 16:46:22 -0700 Received: from localhost.localdomain (leviathan [131.128.51.64]) by leviathan.ele.uri.edu (8.12.9/8.12.9) with ESMTP id j7VNhQ4r019111; Wed, 31 Aug 2005 19:43:26 -0400 (EDT) Subject: RE: how to defragment xfs? From: Ming Zhang Reply-To: mingz@ele.uri.edu To: Allan Haywood Cc: Nathan Scott , xfs In-Reply-To: <14BC3454F4B4614FBC4F3FB19A84C3720D466E@FPNYEXCBE01.opus-i.corp> References: <14BC3454F4B4614FBC4F3FB19A84C3720D466E@FPNYEXCBE01.opus-i.corp> Content-Type: text/plain Organization: no-dole-available Date: Wed, 31 Aug 2005 19:43:26 -0400 Message-Id: <1125531806.6617.102.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-archive-position: 6020 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mingz@ele.uri.edu Precedence: bulk X-list: linux-xfs Content-Length: 1772 Lines: 57 my problem is i do not have this command at all in my FC box. I will compile one from source. thx ming On Wed, 2005-08-31 at 18:48 -0400, Allan Haywood wrote: > On Thu, 2005-09-01 at 08:36 +1000, Nathan Scott wrote: > > On Wed, Aug 31, 2005 at 06:02:18PM -0400, Ming Zhang wrote: > > > Thanks all! > > > > > > My fault. I remember there is a command for xfs or reiserfs to do > this > > > and i can not figure out the name. then i check xfs_* on my box and > none > > > of them doing this job. so i assumed it is for reiserfs. > > > > > > it is quite weired that my FC box does not have this command in > > > xfsprogs. > > > > Its in the "xfsdump" package, not "xfsprogs". > > > > cheers. > > > > [root@amd64 mingz]# yum install xfsdump > Setting up Install Process > Setting up Repos > base 100% |=========================| 1.1 kB > 00:00 > updates-released 100% |=========================| 951 B > 00:00 > Reading repository metadata in from local files > base : ################################################## 2852/2852 > primary.xml.gz 100% |=========================| 445 kB > 00:20 > MD Read : ################################################## 1117/1117 > updates-re: ################################################## 1117/1117 > No Match for argument: xfsdump > Nothing to do > > > i guess my FC3 X86_64 does not have it yet. > > Ming > > ------------------ > > Try running "xfs_fsr" without the quotes. > > You don't have to unmount any file systems, or do anything special for > it to run. Also the defaults should be fine for you. You can read the > man page for more info on how it runs. > > Also try running using -v, it outputs details of what it is doing which > is kinda interesting. > From owner-linux-xfs@oss.sgi.com Wed Aug 31 16:45:13 2005 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 31 Aug 2005 16:45:20 -0700 (PDT) Received: from leviathan.ele.uri.edu (leviathan.ele.uri.edu [131.128.51.64]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id j7VNjCiL008548 for ; Wed, 31 Aug 2005 16:45:13 -0700 Received: from localhost.localdomain (leviathan [131.128.51.64]) by leviathan.ele.uri.edu (8.12.9/8.12.9) with ESMTP id j7VNg34r019071; Wed, 31 Aug 2005 19:42:04 -0400 (EDT) Subject: RE: how to defragment xfs? From: Ming Zhang Reply-To: mingz@ele.uri.edu To: Allan Haywood Cc: Lonni J Friedman , David Chinner , xfs In-Reply-To: <14BC3454F4B4614FBC4F3FB19A84C3720D466B@FPNYEXCBE01.opus-i.corp> References: <14BC3454F4B4614FBC4F3FB19A84C3720D466B@FPNYEXCBE01.opus-i.corp> Content-Type: text/plain Organization: no-dole-available Date: Wed, 31 Aug 2005 19:42:03 -0400 Message-Id: <1125531723.6617.99.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-2) Content-Transfer-Encoding: 7bit X-archive-position: 6019 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mingz@ele.uri.edu Precedence: bulk X-list: linux-xfs Content-Length: 936 Lines: 51 On Wed, 2005-08-31 at 18:38 -0400, Allan Haywood wrote: > thanks! > > > how to defragment the whole FS? > > > this is only to check fragment right? > > ---------------------- > > Correct, it only checks, it doesn't make any changes to fragmentation at > all. > ic. so check if need to do before actually to do it. i guess this is what u mean. ming > > > ---------------------------- > > > > You can use the following command to check fragmentation: > > > > xfs_db -c frag -r /dev/md0 > > > > replace /dev/md0 with the name of the device you want to check. > > > > This is what the output will look like: > > > > actual 184, ideal 176, fragmentation factor 4.35% > > > > > > Allan Haywood > > Data Warehouse Systems Specialist > > DATAllegro > > 65 Enterprise > > Aliso Viejo, CA 92656 > > 949.330.7633 direct > > 949.330.7691 fax > > E-mail: allanh@datallegro.com > > Web: www.Datallegro.com > > > > > > > > >