From owner-linux-xfs@oss.sgi.com Sat Apr 1 21:37:22 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 01 Apr 2006 21:37:29 -0800 (PST) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.200]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k325bLgC014943 for ; Sat, 1 Apr 2006 21:37:22 -0800 Received: by uproxy.gmail.com with SMTP id u2so621941uge for ; Sun, 02 Apr 2006 22:32:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=WI0sQvjO2xD51X/+okK8AaTg0KBXKs+uGOjQg6pIXrdryRmxs4A0UVoK+hcEDJxgTxIaidA7M0z6dnOLKCS4LXEIfERdYK4o0/cYSkwbvX7cJ3D786FEHjWvxyVCCHw7tD3C39rqU0ozQaBnQoAR1d1frNXkrFNHQZGb2MbWXAI= Received: by 10.78.20.13 with SMTP id 13mr41814hut; Sun, 02 Apr 2006 20:55:10 -0700 (PDT) Received: by 10.78.40.1 with HTTP; Sun, 2 Apr 2006 20:55:10 -0700 (PDT) Message-ID: <6b22a6b40604022055s27c9400bjabafbdd593fd3119@mail.gmail.com> Date: Mon, 3 Apr 2006 13:55:10 +1000 From: "Gerard Neil" To: linux-xfs@oss.sgi.com Subject: xfsdump and chattr +d : undocumented but really useful behaviour 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 k325bMgC014946 X-archive-position: 7573 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: xyzzy@devferret.org Precedence: bulk X-list: linux-xfs Status: O Content-Length: 785 Lines: 20 I've been running a gentoo linux server (currently 2.6.15) using xfs and xfsdump for a couple of years now. I've just discovered that if the the no-dump (d) attribute is set on a directory (using chattr +d), then any new directories/files created in that directory automatically acquire the attribute too. This is *really* useful when used in conjunction with xfsdump -e, because it means I can easily exclude entire subtrees from dumps. If this is really how the no-dump attribute is supposed to behave on xfs, then I suggest documenting this in the xfsdump man page. The current "excluding individual files" section is confusing with respect to chattr +d, and certainly doesn't mention this useful behaviour. I can't find it documented anywhere else, either... Regards, Gerard From owner-linux-xfs@oss.sgi.com Sun Apr 2 07:37:25 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 02 Apr 2006 07:37: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 k32EbOgC002074 for ; Sun, 2 Apr 2006 07:37:24 -0700 Received: from internal-mail-relay1.corp.sgi.com (internal-mail-relay1.corp.sgi.com [198.149.32.52]) by omx1.americas.sgi.com (8.12.10/8.12.9/linux-outbound_gateway-1.1) with ESMTP id k33EWmnx018878 for ; Mon, 3 Apr 2006 09:32:48 -0500 Received: from [128.162.233.24] (fsgi275.americas.sgi.com [128.162.233.24]) by internal-mail-relay1.corp.sgi.com (8.12.9/8.12.10/SGI_generic_relay-1.2) with ESMTP id k33EcOpG5131407; Mon, 3 Apr 2006 07:38:24 -0700 (PDT) Message-ID: <4431320D.2040500@sgi.com> Date: Mon, 03 Apr 2006 09:32:45 -0500 From: Bill Kendall User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gerard Neil CC: linux-xfs@oss.sgi.com Subject: Re: xfsdump and chattr +d : undocumented but really useful behaviour References: <6b22a6b40604022055s27c9400bjabafbdd593fd3119@mail.gmail.com> In-Reply-To: <6b22a6b40604022055s27c9400bjabafbdd593fd3119@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 7574 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: wkendall@sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1003 Lines: 30 Hi Gerard, This is a popular question lately. The man page was updated a couple months back, around version 2.2.34 or so. Regards, Bill On 04/02/06 22:55, Gerard Neil wrote: > I've been running a gentoo linux server (currently 2.6.15) using xfs > and xfsdump for a couple of years now. > > I've just discovered that if the the no-dump (d) attribute is set on a > directory (using chattr +d), then any new directories/files created in > that directory automatically acquire the attribute too. > > This is *really* useful when used in conjunction with xfsdump -e, > because it means I can easily exclude entire subtrees from dumps. > > If this is really how the no-dump attribute is supposed to behave on > xfs, then I suggest documenting this in the xfsdump man page. The > current "excluding individual files" section is confusing with respect > to chattr +d, and certainly doesn't mention this useful behaviour. I > can't find it documented anywhere else, either... > > Regards, > > Gerard > From owner-linux-xfs@oss.sgi.com Sun Apr 2 23:04:23 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 02 Apr 2006 23:04:27 -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 k3364LgC015313 for ; Sun, 2 Apr 2006 23:04:22 -0700 Received: from puffy.melbourne.sgi.com (puffy.melbourne.sgi.com [134.14.55.166]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id OAA09492; Tue, 4 Apr 2006 14:53:42 +1000 Received: by puffy.melbourne.sgi.com (Postfix, from userid 1000) id 0392E10D; Tue, 4 Apr 2006 14:50:24 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.melbourne.sgi.com Subject: TAKE 951422 - libdir paths in xfs-cmds Makefiles are wrong for many 64bit platforms Message-Id: <20060404045024.0392E10D@puffy.melbourne.sgi.com> Date: Tue, 4 Apr 2006 14:50:24 +1000 (EST) From: tes@puffy.melbourne.sgi.com (Timothy Shimmin) X-archive-position: 7575 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@puffy.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 6609 Lines: 100 fix lib64 installs Date: Tue Apr 4 14:51:15 AEST 2006 Workarea: puffy.melbourne.sgi.com:/home/tes/isms/xfs-cmds Inspected by: nathans@sgi.com The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb Modid: master-melb:xfs-cmds:25657a dmapi/m4/multilib.m4 - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/m4/multilib.m4 xfstests/m4/multilib.m4 - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/multilib.m4 xfsdump/m4/multilib.m4 - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/m4/multilib.m4 acl/m4/multilib.m4 - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/m4/multilib.m4 xfsprogs/m4/multilib.m4 - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/m4/multilib.m4 attr/m4/multilib.m4 - 1.1 - new http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/m4/multilib.m4 acl/configure.in - 1.29 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/configure.in.diff?r1=text&tr1=1.29&r2=text&tr2=1.28&f=h acl/Makefile - 1.19 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/Makefile.diff?r1=text&tr1=1.19&r2=text&tr2=1.18&f=h acl/include/builddefs.in - 1.32 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/include/builddefs.in.diff?r1=text&tr1=1.32&r2=text&tr2=1.31&f=h attr/configure.in - 1.18 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/configure.in.diff?r1=text&tr1=1.18&r2=text&tr2=1.17&f=h attr/Makefile - 1.16 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/Makefile.diff?r1=text&tr1=1.16&r2=text&tr2=1.15&f=h attr/include/builddefs.in - 1.28 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/include/builddefs.in.diff?r1=text&tr1=1.28&r2=text&tr2=1.27&f=h xfsprogs/configure.in - 1.35 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/configure.in.diff?r1=text&tr1=1.35&r2=text&tr2=1.34&f=h xfsprogs/Makefile - 1.27 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/Makefile.diff?r1=text&tr1=1.27&r2=text&tr2=1.26&f=h xfsprogs/include/builddefs.in - 1.46 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/include/builddefs.in.diff?r1=text&tr1=1.46&r2=text&tr2=1.45&f=h xfsdump/configure.in - 1.38 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/configure.in.diff?r1=text&tr1=1.38&r2=text&tr2=1.37&f=h xfsdump/Makefile - 1.19 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/Makefile.diff?r1=text&tr1=1.19&r2=text&tr2=1.18&f=h xfsdump/include/builddefs.in - 1.25 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/include/builddefs.in.diff?r1=text&tr1=1.25&r2=text&tr2=1.24&f=h xfstests/Makefile - 1.12 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/Makefile.diff?r1=text&tr1=1.12&r2=text&tr2=1.11&f=h dmapi/configure.in - 1.21 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/configure.in.diff?r1=text&tr1=1.21&r2=text&tr2=1.20&f=h dmapi/Makefile - 1.12 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/Makefile.diff?r1=text&tr1=1.12&r2=text&tr2=1.11&f=h dmapi/include/builddefs.in - 1.24 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/include/builddefs.in.diff?r1=text&tr1=1.24&r2=text&tr2=1.23&f=h acl/m4/Makefile - 1.4 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/m4/Makefile.diff?r1=text&tr1=1.4&r2=text&tr2=1.3&f=h acl/aclocal.m4 - 1.10 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/aclocal.m4.diff?r1=text&tr1=1.10&r2=text&tr2=1.9&f=h attr/m4/Makefile - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/m4/Makefile.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h attr/aclocal.m4 - 1.8 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/attr/aclocal.m4.diff?r1=text&tr1=1.8&r2=text&tr2=1.7&f=h acl/m4/package_attrdev.m4 - 1.5 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/acl/m4/package_attrdev.m4.diff?r1=text&tr1=1.5&r2=text&tr2=1.4&f=h dmapi/m4/package_xfslibs.m4 - 1.7 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/m4/package_xfslibs.m4.diff?r1=text&tr1=1.7&r2=text&tr2=1.6&f=h dmapi/aclocal.m4 - 1.9 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/aclocal.m4.diff?r1=text&tr1=1.9&r2=text&tr2=1.8&f=h dmapi/m4/Makefile - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/dmapi/m4/Makefile.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h xfsprogs/aclocal.m4 - 1.21 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/aclocal.m4.diff?r1=text&tr1=1.21&r2=text&tr2=1.20&f=h xfsprogs/m4/Makefile - 1.5 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsprogs/m4/Makefile.diff?r1=text&tr1=1.5&r2=text&tr2=1.4&f=h xfsdump/m4/package_xfslibs.m4 - 1.7 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/m4/package_xfslibs.m4.diff?r1=text&tr1=1.7&r2=text&tr2=1.6&f=h xfsdump/aclocal.m4 - 1.15 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/aclocal.m4.diff?r1=text&tr1=1.15&r2=text&tr2=1.14&f=h xfsdump/m4/package_attrdev.m4 - 1.5 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/m4/package_attrdev.m4.diff?r1=text&tr1=1.5&r2=text&tr2=1.4&f=h xfsdump/m4/package_dmapidev.m4 - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/m4/package_dmapidev.m4.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h xfsdump/m4/Makefile - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/m4/Makefile.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h xfstests/m4/Makefile - 1.7 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/Makefile.diff?r1=text&tr1=1.7&r2=text&tr2=1.6&f=h xfstests/m4/package_acldev.m4 - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/package_acldev.m4.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h xfstests/m4/package_attrdev.m4 - 1.7 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/package_attrdev.m4.diff?r1=text&tr1=1.7&r2=text&tr2=1.6&f=h xfstests/m4/package_dmapidev.m4 - 1.2 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/package_dmapidev.m4.diff?r1=text&tr1=1.2&r2=text&tr2=1.1&f=h xfstests/m4/package_gdbmdev.m4 - 1.3 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/package_gdbmdev.m4.diff?r1=text&tr1=1.3&r2=text&tr2=1.2&f=h xfstests/m4/package_xfslibs.m4 - 1.8 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/m4/package_xfslibs.m4.diff?r1=text&tr1=1.8&r2=text&tr2=1.7&f=h xfstests/aclocal.m4 - 1.16 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfstests/aclocal.m4.diff?r1=text&tr1=1.16&r2=text&tr2=1.15&f=h From owner-linux-xfs@oss.sgi.com Mon Apr 3 01:45:49 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 01:45:55 -0700 (PDT) Received: from pproxy.gmail.com (pproxy.gmail.com [64.233.166.180]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k338jmgC011020 for ; Mon, 3 Apr 2006 01:45:49 -0700 Received: by pproxy.gmail.com with SMTP id i75so1793338pye for ; Tue, 04 Apr 2006 01:41:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=K5rJgszvnBb7QZmNNc1jamABP8wrft/ibXg+UaVBdf+tsajdK5TQOfVLPqHPh2/EmoXfMj8XPcwwhKJZT/oxKxJZm32zKgCQeVAQHqUxvTvoCghiyL3Phs4JLRxU8ndHsJU13kB5rUMqHh9op8Vn9S4b67UNZvJcpwDsCgCh9c0= Received: by 10.35.43.10 with SMTP id v10mr498086pyj; Tue, 04 Apr 2006 00:42:50 -0700 (PDT) Received: by 10.35.99.11 with HTTP; Tue, 4 Apr 2006 00:42:50 -0700 (PDT) Message-ID: Date: Tue, 4 Apr 2006 03:42:50 -0400 From: "Evgeniy Sharapov" Reply-To: sen@fnal.gov To: linux-xfs@oss.sgi.com Subject: XFS partition recovery MIME-Version: 1.0 Content-Type: text/plain Content-Disposition: inline Content-Transfer-Encoding: 7bit X-archive-position: 7576 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: evgeniy.sharapov@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 13202 Lines: 310 I have XFS /home partition (fortunately not /). I can not mount it because of the error during reading the superblock. After running xfs_repair -nLv /dev/hda7 I got <------cut---------> ................................ would clear inode number in entry at offset 2416... entry "20060331122258" at block 2 offset 2448 in directory inode 16922661 references free inode 184775172 would clear inode number in entry at offset 2448... entry "20060331122336" at block 2 offset 2480 in directory inode 16922661 references free inode 201635562 would clear inode number in entry at offset 2480... entry "20060331122347" at block 2 offset 2512 in directory inode 16922661 references free inode 218356061 would clear inode number in entry at offset 2512... entry "20060331122411" at block 2 offset 2544 in directory inode 16922661 references free inode 235060608 would clear inode number in entry at offset 2544... entry "20060331122457" at block 2 offset 2576 in directory inode 16922661 references free inode 252033667 would clear inode number in entry at offset 2576... entry "20060331122757" at block 2 offset 2640 in directory inode 16922661 references free inode 17026280 would clear inode number in entry at offset 2640... entry "20060331122931" at block 2 offset 2672 in directory inode 16922661 references free inode 33982501 would clear inode number in entry at offset 2672... entry "20060331123023" at block 2 offset 2704 in directory inode 16922661 references free inode 50472830 would clear inode number in entry at offset 2704... entry "20060331124300" at block 2 offset 2736 in directory inode 16922661 references free inode 67334620 would clear inode number in entry at offset 2736... entry "20060331124322" at block 2 offset 2768 in directory inode 16922661 references free inode 87134914 would clear inode number in entry at offset 2768... - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 entry "saved_state" in shortform directory 117927296 references free inode 119856305 would have junked entry "saved_state" in directory inode 117927296 - agno = 8 - agno = 9 entry "lock" at block 0 offset 1400 in directory inode 151094696 references free inode 151094596 would clear inode number in entry at offset 1400... - agno = 10 - agno = 11 - agno = 12 - agno = 13 entry "prefs.js" at block 0 offset 184 in directory inode 218120250 references free inode 218356930 would clear inode number in entry at offset 184... entry "crashrecovery.bak" at block 0 offset 2064 in directory inode 218120250 references free inode 218356062 would clear inode number in entry at offset 2064... data fork in ino 218351246 claims dup extent, off - 0, start - 13762894, cnt 16 bad data fork in inode 218351246 would have cleared inode 218351246 data fork in ino 218356062 claims dup extent, off - 0, start - 13762907, cnt 1 bad data fork in inode 218356062 would have cleared inode 218356062 - agno = 14 - agno = 15 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem starting at / ... entry "saved_state" in shortform directory inode 117927296 points to free inode 119856305 would junk entry "saved_state" entry "lock" in directory inode 151094696 points to free inode 151094596, would junk entry entry "prefs.js" in directory inode 218120250 points to free inode 218356930, would junk entry entry "history.dat" in directory inode 218120250 points to free inode 218351246, would junk entry entry "crashrecovery.bak" in directory inode 218120250 points to free inode 218356062, would junk entry entry "20060331104725" in directory inode 16922661 points to free inode 167995662, would junk entry entry "20060331122258" in directory inode 16922661 points to free inode 184775172, would junk entry entry "20060331122336" in directory inode 16922661 points to free inode 201635562, would junk entry entry "20060331122347" in directory inode 16922661 points to free inode 218356061, would junk entry entry "20060331122411" in directory inode 16922661 points to free inode 235060608, would junk entry entry "20060331122457" in directory inode 16922661 points to free inode 252033667, would junk entry entry "20060331122757" in directory inode 16922661 points to free inode 17026280, would junk entry entry "20060331122931" in directory inode 16922661 points to free inode 33982501, would junk entry entry "20060331123023" in directory inode 16922661 points to free inode 50472830, would junk entry entry "20060331124300" in directory inode 16922661 points to free inode 67334620, would junk entry entry "20060331124322" in directory inode 16922661 points to free inode 87134914, would junk entry entry "E61AF434d01" in directory inode 432031 points to free inode 482273, would junk entry entry "4F7AC625d01" in directory inode 432031 points to free inode 565461, would junk entry entry "5BE8CE43d01" in directory inode 432031 points to free inode 565462, would junk entry entry "CA71364Cd01" in directory inode 432031 points to free inode 565463, would junk entry entry "5265B4CEd01" in directory inode 432031 points to free inode 557310, would junk entry entry "5ACFE1DBd01" in directory inode 432031 points to free inode 565464, would junk entry entry "A0038D5Dd01" in directory inode 432031 points to free inode 565465, would junk entry entry "CC8B81C1d01" in directory inode 432031 points to free inode 565466, would junk entry entry "21566C16d01" in directory inode 432031 points to free inode 565467, would junk entry entry "87FD77F2d01" in directory inode 432031 points to free inode 565468, would junk entry entry "043B9D90d01" in directory inode 432031 points to free inode 565469, would junk entry entry "FAC61E89d01" in directory inode 432031 points to free inode 565470, would junk entry entry "624CE5DFd01" in directory inode 432031 points to free inode 565471, would junk entry entry "2852617Bd01" in directory inode 432031 points to free inode 565492, would junk entry entry "54132227d01" in directory inode 432031 points to free inode 565493, would junk entry entry "2EEAE483d01" in directory inode 432031 points to free inode 565494, would junk entry entry "5053272Ad01" in directory inode 432031 points to free inode 565495, would junk entry entry "5A393CB6d01" in directory inode 432031 points to free inode 565496, would junk entry entry "E9D34479d01" in directory inode 432031 points to free inode 565497, would junk entry entry "48BFCCC0d01" in directory inode 432031 points to free inode 565498, would junk entry entry "C9CC7FE0d01" in directory inode 432031 points to free inode 565499, would junk entry entry "81B890F9d01" in directory inode 432031 points to free inode 565500, would junk entry entry "95EC210Ed01" in directory inode 432031 points to free inode 565501, would junk entry entry "D503BEA1d01" in directory inode 432031 points to free inode 565502, would junk entry entry "24F4B5ACd01" in directory inode 432031 points to free inode 565503, would junk entry entry "27BE8468d01" in directory inode 432031 points to free inode 565517, would junk entry entry "80F5F487d01" in directory inode 432031 points to free inode 565518, would junk entry entry "6B2A05DCd01" in directory inode 432031 points to free inode 565519, would junk entry entry "7AA62CD4d01" in directory inode 432031 points to free inode 565520, would junk entry entry "E442E09Ed01" in directory inode 432031 points to free inode 565521, would junk entry entry "652077F6d01" in directory inode 432031 points to free inode 565522, would junk entry entry "3452818Ed01" in directory inode 432031 points to free inode 565523, would junk entry entry "BDAB8D3Ed01" in directory inode 432031 points to free inode 565524, would junk entry entry "F34FA42Cd01" in directory inode 432031 points to free inode 565525, would junk entry entry "D2DCB468d01" in directory inode 432031 points to free inode 565526, would junk entry entry "FB102E32d01" in directory inode 432031 points to free inode 565527, would junk entry entry "10131699d01" in directory inode 432031 points to free inode 565528, would junk entry entry "DF9813B6d01" in directory inode 432031 points to free inode 565529, would junk entry entry "BF6B7290d01" in directory inode 432031 points to free inode 565530, would junk entry entry "2B2187FAd01" in directory inode 432031 points to free inode 565531, would junk entry entry "D102BB46d01" in directory inode 432031 points to free inode 565532, would junk entry entry "31334C17d01" in directory inode 432031 points to free inode 565533, would junk entry entry "C34B8538d01" in directory inode 432031 points to free inode 565534, would junk entry entry "C3508538d01" in directory inode 432031 points to free inode 565535, would junk entry entry "A2BD676Fd01" in directory inode 432031 points to free inode 565553, would junk entry entry "2750656Ed01" in directory inode 432031 points to free inode 565554, would junk entry entry "575336C8d01" in directory inode 432031 points to free inode 565555, would junk entry entry "773A2D72d01" in directory inode 432031 points to free inode 565556, would junk entry entry "D4C08B1Bd01" in directory inode 432031 points to free inode 565557, would junk entry entry "3D8E1824d01" in directory inode 432031 points to free inode 565558, would junk entry entry "2EC1600Cd01" in directory inode 432031 points to free inode 565559, would junk entry entry "124C7A75d01" in directory inode 432031 points to free inode 565560, would junk entry entry "6999FFD2d01" in directory inode 432031 points to free inode 565561, would junk entry entry "8250BEA1d01" in directory inode 432031 points to free inode 565562, would junk entry entry "26C76F3Fd01" in directory inode 432031 points to free inode 565563, would junk entry entry "2E243691d01" in directory inode 432031 points to free inode 565564, would junk entry entry "5C6481DFd01" in directory inode 432031 points to free inode 565565, would junk entry entry "3BD10BA5d01" in directory inode 432031 points to free inode 565566, would junk entry entry "55345258d01" in directory inode 432031 points to free inode 565567, would junk entry entry "E8F09616d01" in directory inode 432031 points to free inode 575999, would junk entry entry "2C0CEBA4d01" in directory inode 432031 points to free inode 576000, would junk entry entry "2C0FEBA4d01" in directory inode 432031 points to free inode 576001, would junk entry entry "5E9DDAECd01" in directory inode 432031 points to free inode 576002, would junk entry entry "FB688CBEd01" in directory inode 432031 points to free inode 576003, would junk entry bad hash table for directory inode 432031 (no data entry): would rebuild - traversal finished ... - traversing all unattached subtrees ... - traversals finished ... - moving disconnected inodes to lost+found ... disconnected inode 218356929, would move to lost+found disconnected inode 218356931, would move to lost+found disconnected inode 218356932, would move to lost+found disconnected inode 218356933, would move to lost+found disconnected inode 218356934, would move to lost+found Phase 7 - verify link counts... would have reset inode 16922661 nlinks from 330 to 331 No modify flag set, skipping filesystem flush and exiting. <----/cut-----------> Nothing unusual, i.e. There's no message about fatally corrupted filesystem. But xfs_repair fails when it's run in fixing mode. <-------cut------------> senntb ~ # xfs_repair -v /dev/hda7 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... xfs_repair: read failed: Input/output error senntb ~ # xfs_repair -v /dev/hda7 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... xfs_repair: read failed: Input/output error senntb ~ # xfs_repair -v /dev/hda7 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... xfs_repair: read failed: Input/output error senntb ~ # <-------/cut------------> The same error when I start it with -L option added. I found here ( http://docs.cray.com/books/S-2377-22/html-S-2377-22/fixed6bhdyq9i26.html) that I have to <-------cut-------------> If xfs_repair failed in phase 2 or later, follow these steps: 1. Mount the file system using mount -r (read-only). 2. Make a file system backup with xfsdump. 3. Use mkfs to a make new file system on the same disk partition or XLV logical volume. 4. Restore the files from the backup with xfsrestore <-------/cut-------------> But I can't mount my home partition in read-only mode. <-------cut-------------> senntb ~ # mount -r /home mount: /dev/hda7: can't read superblock senntb ~ # <-------/cut-------------> I'm lost. How can I recover my /home partition ? It's really important. -- Evgeniy N. Sharapov ============================== Lehigh University Industrial & Systems Eng. Dpt. Bethlehem, Pennsylvania, USA ============================== phone: 630 779 3208 mail: ens205@lehigh.edu, sen@fnal.gov icq : 345482263 [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Mon Apr 3 14:26:27 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 14:26:29 -0700 (PDT) Received: from mail.charite.de (mail.charite.de [160.45.207.131]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k33LQPgC027063 for ; Mon, 3 Apr 2006 14:26:26 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.charite.de (Postfix) with ESMTP id ED533220CDA; Tue, 4 Apr 2006 23:21:46 +0200 (CEST) Received: from mail.charite.de ([127.0.0.1]) by localhost (mail.charite.de [127.0.0.1]) (amavisd-new, port 10025) with LMTP id 4sv8zhUnTL3k; Tue, 4 Apr 2006 23:21:44 +0200 (CEST) Received: from postamt.charite.de (postamt.charite.de [160.45.207.132]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.charite.de (Postfix) with ESMTP id BA7DD220CD5; Tue, 4 Apr 2006 23:21:44 +0200 (CEST) Received: by postamt.charite.de (Postfix, from userid 7945) id 7B6F9220781; Tue, 4 Apr 2006 23:21:44 +0200 (CEST) Date: Tue, 4 Apr 2006 23:21:44 +0200 From: Ralf Hildebrandt To: linux-kernel@vger.kernel.org Cc: linux-xfs@oss.sgi.com Subject: 2.6.16.1: XFS internal error xfs_btree_check_lblock at line 215 of file fs/xfs/xfs_btree.c Message-ID: <20060404212144.GM15722@charite.de> Mail-Followup-To: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.9i X-archive-position: 7578 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: Ralf.Hildebrandt@charite.de Precedence: bulk X-list: linux-xfs Status: O Content-Length: 7005 Lines: 91 I was running xfs_fsr on our /home at night when this happened: (Kernel 2.6.16.1) Security Events =-=-=-=-=-=-=-= Apr 2 00:26:17 postamt kernel: xfs_force_shutdown(sda5,0x8) called from line 1032 of file fs/xfs/xfs_trans.c. Return address = 0xb1128274 System Events =-=-=-=-=-=-= Apr 2 00:17:10 postamt fsr[28019]: /home start inode=0 Apr 2 00:25:29 postamt fsr[28938]: /home start inode=0 Apr 2 00:26:17 postamt kernel: Filesystem "sda5": XFS internal error xfs_btree_check_lblock at line 215 of file fs/xfs/xfs_btree.c. Caller 0xb10dba58 Apr 2 00:26:17 postamt kernel: [xfs_btree_check_lblock+82/407] xfs_btree_check_lblock+0x52/0x197 Apr 2 00:26:17 postamt kernel: [xfs_bmbt_lookup+636/1471] xfs_bmbt_lookup+0x27c/0x5bf Apr 2 00:26:17 postamt kernel: [xfs_bmbt_lookup+636/1471] xfs_bmbt_lookup+0x27c/0x5bf Apr 2 00:26:17 postamt kernel: [xfs_bmap_del_extent+491/2774] xfs_bmap_del_extent+0x1eb/0xad6 Apr 2 00:26:17 postamt kernel: [xfs_mod_incore_sb_batch+60/134] xfs_mod_incore_sb_batch+0x3c/0x86 Apr 2 00:26:17 postamt kernel: [kmem_zone_alloc+61/176] kmem_zone_alloc+0x3d/0xb0 Apr 2 00:26:17 postamt kernel: [xfs_bmap_search_extents+117/279] xfs_bmap_search_extents+0x75/0x117 Apr 2 00:26:17 postamt kernel: [xfs_bunmapi+1851/4334] xfs_bunmapi+0x73b/0x10ee Apr 2 00:26:17 postamt kernel: [xfs_trans_ijoin+43/134] xfs_trans_ijoin+0x2b/0x86 Apr 2 00:26:17 postamt kernel: [xfs_itruncate_finish+617/942] xfs_itruncate_finish+0x269/0x3ae Apr 2 00:26:17 postamt kernel: [xfs_trans_ijoin+43/134] xfs_trans_ijoin+0x2b/0x86 Apr 2 00:26:17 postamt kernel: [xfs_inactive+1058/1282] xfs_inactive+0x422/0x502 Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag0: Input/output error Apr 2 00:26:17 postamt kernel: [linvfs_clear_inode+140/164] linvfs_clear_inode+0x8c/0xa4 Apr 2 00:26:17 postamt kernel: [dquot_drop+0/106] dquot_drop+0x0/0x6a Apr 2 00:26:17 postamt kernel: [clear_inode+173/290] clear_inode+0xad/0x122 Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag1: Input/output error Apr 2 00:26:17 postamt kernel: [truncate_inode_pages+23/27] truncate_inode_pages+0x17/0x1b Apr 2 00:26:17 postamt kernel: [generic_delete_inode+207/284] generic_delete_inode+0xcf/0x11c Apr 2 00:26:17 postamt kernel: [iput+83/101] iput+0x53/0x65 Apr 2 00:26:17 postamt kernel: [dput+106/302] dput+0x6a/0x12e Apr 2 00:26:17 postamt kernel: [__fput+258/350] __fput+0x102/0x15e Apr 2 00:26:17 postamt kernel: [filp_close+60/123] filp_close+0x3c/0x7b Apr 2 00:26:17 postamt kernel: [sys_close+86/143] sys_close+0x56/0x8f Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag2: Input/output error Apr 2 00:26:17 postamt kernel: [sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75 Apr 2 00:26:17 postamt kernel: Filesystem "sda5": XFS internal error xfs_trans_cancel at line 1031 of file fs/xfs/xfs_trans.c. Caller 0xb1118f9f Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag3: Input/output error Apr 2 00:26:17 postamt kernel: [xfs_trans_cancel+211/270] xfs_trans_cancel+0xd3/0x10e Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag4: Input/output error Apr 2 00:26:17 postamt kernel: [xfs_inactive+1080/1282] xfs_inactive+0x438/0x502 Apr 2 00:26:17 postamt kernel: [xfs_inactive+1080/1282] xfs_inactive+0x438/0x502 Apr 2 00:26:17 postamt kernel: [linvfs_clear_inode+140/164] linvfs_clear_inode+0x8c/0xa4 Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag5: Input/output error Apr 2 00:26:17 postamt kernel: [dquot_drop+0/106] dquot_drop+0x0/0x6a Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag6: Input/output error Apr 2 00:26:17 postamt kernel: [clear_inode+173/290] clear_inode+0xad/0x122 Apr 2 00:26:17 postamt kernel: [truncate_inode_pages+23/27] truncate_inode_pages+0x17/0x1b Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag7: Input/output error Apr 2 00:26:17 postamt kernel: [generic_delete_inode+207/284] generic_delete_inode+0xcf/0x11c Apr 2 00:26:17 postamt kernel: [iput+83/101] iput+0x53/0x65 Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag8: Input/output error Apr 2 00:26:17 postamt kernel: [dput+106/302] dput+0x6a/0x12e Apr 2 00:26:17 postamt kernel: [__fput+258/350] __fput+0x102/0x15e Apr 2 00:26:17 postamt kernel: [filp_close+60/123] filp_close+0x3c/0x7b Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag9: Input/output error Apr 2 00:26:17 postamt kernel: [sys_close+86/143] sys_close+0x56/0x8f Apr 2 00:26:17 postamt kernel: [sysenter_past_esp+84/117] sysenter_past_esp+0x54/0x75 Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag10: Input/output error Apr 2 00:26:17 postamt kernel: Filesystem "sda5": Corruption of in-memory data detected. Shutting down filesystem: sda5 Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag11: Input/output error Apr 2 00:26:17 postamt kernel: Please umount the filesystem, and rectify the problem(s) Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag12: Input/output error Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag13: Input/output error Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag14: Input/output error Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr/ag15: Input/output error Apr 2 00:26:17 postamt fsr[28938]: could not remove tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29047]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29047]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29048]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29048]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29049]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29049]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29050]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29050]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29051]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29051]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29052]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29052]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[29053]: /home start inode=0 Apr 2 00:26:17 postamt fsr[29053]: could not create tmpdir: /home/.fsr: Input/output error Apr 2 00:26:17 postamt fsr[25409]: Completed all 10 passes -- Ralf Hildebrandt (i.A. des IT-Zentrums) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-962 IT-Zentrum Standort CBF send no mail to spamtrap@charite.de From owner-linux-xfs@oss.sgi.com Mon Apr 3 15:12:28 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 15:12:31 -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 k33MCPgC000512 for ; Mon, 3 Apr 2006 15:12:27 -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 IAA01614; Wed, 5 Apr 2006 08:07:37 +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 k34M7YJC1100643; Wed, 5 Apr 2006 08:07:34 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id k34M7WU81103108; Wed, 5 Apr 2006 08:07:32 +1000 (EST) Date: Wed, 5 Apr 2006 08:07:31 +1000 From: Nathan Scott To: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com Subject: Re: 2.6.16.1: XFS internal error xfs_btree_check_lblock at line 215 of file fs/xfs/xfs_btree.c Message-ID: <20060405080731.B1071351@wobbly.melbourne.sgi.com> References: <20060404212144.GM15722@charite.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20060404212144.GM15722@charite.de>; from Ralf.Hildebrandt@charite.de on Tue, Apr 04, 2006 at 11:21:44PM +0200 X-archive-position: 7579 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: 508 Lines: 14 On Tue, Apr 04, 2006 at 11:21:44PM +0200, Ralf Hildebrandt wrote: > I was running xfs_fsr on our /home at night when this happened: > (Kernel 2.6.16.1) > ... > Apr 2 00:26:17 postamt kernel: Filesystem "sda5": XFS internal error xfs_btree_check_lblock at line 215 of file fs/xfs/xfs_btree.c. Caller 0xb10dba58 > Apr 2 00:26:17 postamt kernel: [xfs_btree_check_lblock+82/407] xfs_btree_check_lblock+0x52/0x197 What does xfs_repair report? Is it (the forced shutdown) reproducible? thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Apr 3 15:26:03 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 15:26: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 k33MQ1gC002127 for ; Mon, 3 Apr 2006 15:26:02 -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 IAA01892; Wed, 5 Apr 2006 08:21:15 +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 k34MLCJC1102450; Wed, 5 Apr 2006 08:21:13 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id k34ML9671103849; Wed, 5 Apr 2006 08:21:09 +1000 (EST) Date: Wed, 5 Apr 2006 08:21:08 +1000 From: Nathan Scott To: sen@fnal.gov Cc: linux-xfs@oss.sgi.com Subject: Re: XFS partition recovery Message-ID: <20060405082108.A1101521@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 evgeniy.sharapov@gmail.com on Tue, Apr 04, 2006 at 03:42:50AM -0400 X-archive-position: 7580 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: 1192 Lines: 35 On Tue, Apr 04, 2006 at 03:42:50AM -0400, Evgeniy Sharapov wrote: > I have XFS /home partition (fortunately not /). I can not mount it because > of the error during reading the superblock. > ... Actually, looks like the superblock is fine, which is good - your error message seems to be coming from a failed read in the log. > - zero log... > xfs_repair: read failed: Input/output error > senntb ~ # xfs_repair -v /dev/hda7 > Phase 1 - find and verify superblock... > Phase 2 - using internal log > - zero log... > xfs_repair: read failed: Input/output error > senntb ~ # > <-------/cut------------> So, your IDE device is returning IO errors - you're in pretty bad shape. You have two options: - use dd (or dd_rescue) with error-skipping-mode enabled to get what data remains off to a working device. Then run xfs_repair on that. - restore from your last good backup, probably again to a different device since the one above looks like its on its last legs. > http://docs.cray.com/books/S-2377-22/html-S-2377-22/fixed6bhdyq9i26.html) Yeah, from a quick look that procedure will only help you if you've got a mountable filesystem, as you noticed. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Apr 3 17:48:08 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 17:48:13 -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 k340m6gC028630 for ; Mon, 3 Apr 2006 17:48:07 -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 KAA04437; Wed, 5 Apr 2006 10:43:23 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16302) id 4B4704822BFF; Wed, 5 Apr 2006 10:43:22 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 951661 - fix SB imaxpct validation Message-Id: <20060405004322.4B4704822BFF@chook.melbourne.sgi.com> Date: Wed, 5 Apr 2006 10:43:22 +1000 (EST) From: nathans@sgi.com (Nathan Scott) X-archive-position: 7581 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: 514 Lines: 15 Fix superblock validation regression for the zero imaxpct case. Thanks to kjamieson for noticing. Date: Wed Apr 5 10:42:53 AEST 2006 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-linux Inspected by: dgc,kjamieson@bycast.com The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:25675a xfs_mount.c - 1.377 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_mount.c.diff?r1=text&tr1=1.377&r2=text&tr2=1.376&f=h From owner-linux-xfs@oss.sgi.com Mon Apr 3 17:50:04 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 17:50: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 k340o2gC029011 for ; Mon, 3 Apr 2006 17:50:03 -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 KAA04492; Wed, 5 Apr 2006 10:45:21 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16302) id 809624822BFF; Wed, 5 Apr 2006 10:45:21 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 951662 - fix writepage nonblock mode Message-Id: <20060405004521.809624822BFF@chook.melbourne.sgi.com> Date: Wed, 5 Apr 2006 10:45:21 +1000 (EST) From: nathans@sgi.com (Nathan Scott) X-archive-position: 7582 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: 536 Lines: 15 Fix a writepage regression where we accidentally stopped honouring nonblock mode with the new IO path code (since 2.6.16). Date: Wed Apr 5 10:44:55 AEST 2006 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-linux Inspected by: dgc The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-kern/xfs-linux-melb Modid: xfs-linux-melb:xfs-kern:25676a linux-2.6/xfs_aops.c - 1.124 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/linux-2.6/xfs_aops.c.diff?r1=text&tr1=1.124&r2=text&tr2=1.123&f=h From owner-linux-xfs@oss.sgi.com Mon Apr 3 18:02:13 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 18:02:14 -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 k3412AgC032145 for ; Mon, 3 Apr 2006 18:02:11 -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 KAA04752; Wed, 5 Apr 2006 10:57:28 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16302) id 20C394822BFF; Wed, 5 Apr 2006 10:57:27 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 951418 - xfs_fsr Message-Id: <20060405005727.20C394822BFF@chook.melbourne.sgi.com> Date: Wed, 5 Apr 2006 10:57:27 +1000 (EST) From: nathans@sgi.com (Nathan Scott) X-archive-position: 7583 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: 458 Lines: 14 Fix some memory and file descriptor leaks in xfs_fsr. Date: Wed Apr 5 10:57:02 AEST 2006 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-cmds Inspected by: dgc The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb Modid: master-melb:xfs-cmds:25680a xfsdump/fsr/xfs_fsr.c - 1.20 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/fsr/xfs_fsr.c.diff?r1=text&tr1=1.20&r2=text&tr2=1.19&f=h From owner-linux-xfs@oss.sgi.com Mon Apr 3 18:05:17 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 18:05: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 k3415FgC000444 for ; Mon, 3 Apr 2006 18:05:16 -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 LAA04887; Wed, 5 Apr 2006 11:00:34 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16302) id 5059A4822BFF; Wed, 5 Apr 2006 11:00:34 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: TAKE 951419 - xfs_fsr Message-Id: <20060405010034.5059A4822BFF@chook.melbourne.sgi.com> Date: Wed, 5 Apr 2006 11:00:34 +1000 (EST) From: nathans@sgi.com (Nathan Scott) X-archive-position: 7584 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: 511 Lines: 15 Fix incorrect handling of several extended inode flags/fields by xfs_fsr (project IDs, extsize, realtime). Date: Wed Apr 5 10:59:32 AEST 2006 Workarea: chook.melbourne.sgi.com:/build/nathans/xfs-cmds Inspected by: dgc The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/xfs-cmds/master-melb Modid: master-melb:xfs-cmds:25682a xfsdump/fsr/xfs_fsr.c - 1.22 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-cmds/xfsdump/fsr/xfs_fsr.c.diff?r1=text&tr1=1.22&r2=text&tr2=1.21&f=h From owner-linux-xfs@oss.sgi.com Mon Apr 3 19:27:32 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 19:27:32 -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 k342RTgC014276 for ; Mon, 3 Apr 2006 19:27:31 -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 MAA05957; Wed, 5 Apr 2006 12:22:46 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16346) id ACC6C4822BFF; Wed, 5 Apr 2006 12:22:44 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: PARTIAL TAKE 951551 - System bogged down - shrink_icache_memory Message-Id: <20060405022244.ACC6C4822BFF@chook.melbourne.sgi.com> Date: Wed, 5 Apr 2006 12:22:44 +1000 (EST) From: dgc@sgi.com (David Chinner) X-archive-position: 7585 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: 1091 Lines: 27 Fix inode reclaim scalability regression. When a filesystem has millions of inodes cached and has sparse cluster population, removing inodes from the cluster hash consumes excessive amounts of CPU time. Reduce the CPU cost by making removal O(1) via use of a double linked list for the hash chains. Date: Wed Apr 5 12:21:54 AEST 2006 Workarea: chook.melbourne.sgi.com:/build/dgc/isms/2.6.x-xfs Inspected by: nathans,tes The following file(s) were checked into: longdrop.melbourne.sgi.com:/isms/linux/2.6.x-xfs-melb Modid: xfs-linux-melb:xfs-kern:25683a fs/xfs/xfs_iget.c - 1.212 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_iget.c.diff?r1=text&tr1=1.212&r2=text&tr2=1.211&f=h - Convert cluster hash list to a double linked list to speed xfs_iextract() when large numbers of inodes are cached. fs/xfs/xfs_inode.h - 1.212 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_inode.h.diff?r1=text&tr1=1.212&r2=text&tr2=1.211&f=h - Convert cluster hash list to a double linked list to speed xfs_iextract() when large numbers of inodes are cached. From owner-linux-xfs@oss.sgi.com Mon Apr 3 22:13:06 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 03 Apr 2006 22:13:07 -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 k345D4gC003798 for ; Mon, 3 Apr 2006 22:13:05 -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 PAA08005; Wed, 5 Apr 2006 15:08:18 +1000 Received: by chook.melbourne.sgi.com (Postfix, from userid 16346) id 651FF4822BFF; Wed, 5 Apr 2006 15:08:16 +1000 (EST) To: linux-xfs@oss.sgi.com, sgi.bugs.xfs@engr.sgi.com Subject: PARTIAL TAKE 946321 - Inode use-after-free during an unpin Message-Id: <20060405050816.651FF4822BFF@chook.melbourne.sgi.com> Date: Wed, 5 Apr 2006 15:08:16 +1000 (EST) From: dgc@sgi.com (David Chinner) X-archive-position: 7586 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: 961 Lines: 25 Fix an inode use-after-free durin an unpin. When reclaiming inodes that have been unlinked, we may need to execute transactions during reclaim. By the time the transaction has hit the disk, the linux inode and xfs vnode may already have been freed so we can't reference them safely. Use the known xfs inode state to determine if it is safe to reference the vnode and linux inode during the unpin operation. Date: Wed Apr 5 15:06:48 AEST 2006 Workarea: chook.melbourne.sgi.com:/build/dgc/isms/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: xfs-linux-melb:xfs-kern:25687a fs/xfs/xfs_inode.c - 1.436 - changed http://oss.sgi.com/cgi-bin/cvsweb.cgi/xfs-linux/xfs_inode.c.diff?r1=text&tr1=1.436&r2=text&tr2=1.435&f=h - Don't try to mark an inode dirty during an unpin if it is being reclaimed. If it is being reclaimed, the inode may have already been freed. From owner-linux-xfs@oss.sgi.com Tue Apr 4 17:10:28 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 04 Apr 2006 17:10:30 -0700 (PDT) Received: from smtp.latinmail.com (smtp.latinmail.com [62.37.236.186]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k350ARgC024328 for ; Tue, 4 Apr 2006 17:10:28 -0700 Received: by smtp.latinmail.com (Postfix, from userid 65534) id 00DBCA55195; Wed, 5 Apr 2006 17:30:15 +0200 (CEST) Received: from unknown (unknown [172.17.224.53]) by smtp.latinmail.com (Postfix) with SMTP id DE7E2A53B63; Wed, 5 Apr 2006 17:30:15 +0200 (CEST) From: "Amobe Seko Philipe" To: "amobe.seko.philipe1@latinmail.com" Subject: Bonjour Content-Type: multipart/mixed; boundary="latinmail.com_ltwebml02.localdomain_23cb7995f275e04cd83b2bad00558740" Importance: normal MIME-Version: 1.0 Message-Id: <20060405153015.DE7E2A53B63@smtp.latinmail.com> Date: Wed, 5 Apr 2006 17:30:15 +0200 (CEST) X-Bogosity: No, tests=bogofilter, spamicity=0.226399, version=0.15.13 X-archive-position: 7587 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: amobe.seko.philipe1@latinmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 3250 Lines: 63 --latinmail.com_ltwebml02.localdomain_23cb7995f275e04cd83b2bad00558740 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Administrateur Ex=E9cutif du Comit=E9 d'Attribution des March=E9s et Contrats Corporation Nationale P=E9troli=E8re CI Email. amobe.seko.philipe1@latinmail.com / docteur_amobesekop@mail2doctor.com Tel : 22 508 569 621 (C.N.P.C.I) Bonjour, Je suis Docteur Amob=E9 S=E9ko Philipe, de la R=E9publique de C=F4te d'Ivoi= re, Administrateur Ex=E9cutif du Comit=E9 d'Attribution des March=E9s et Co= ntrats =E0 la Corporation Nationale P=E9troli=E8re de C=F4te d'Ivoire (C.N.P.C.I). J'ai =E9t=E9 dans cette posi= tion durant les cinq derni=E8res ann=E9es mais, je n'ai rien qui puisse mon= trer cela, j'aurais aim=E9 qu'ensemble, nous formions un partenariat d'affaires avec pour crit=E8res exclusifs l'ho= nn=EAtet=E9 et la confiance, partenariat dans lequel tous les deux, nous ti= rerons =E9norm=E9ment profit. En ma qualit=E9 d=92Administrateur Ex=E9cutif du Comit=E9 d'Attribution de = March=E9s et Contrats, je vous octroierai une faveur d'un contrat de 21 mil= lions ($ 21.000.000,00 USD) pour la fourniture =E0 nos Forages, Plateformes et Raffineries, de Turbines= =E0 Gaz, Turbocompresseurs, Foreuses verticales, Enrobeuses, Anneaux Pipel= ines et d'=E9quipements, ainsi une avance sur frais de 10,5 millions US sera mobili= s=E9e =E0 vous en tant que fournisseur au d=E9part pour commencer le travai= l. Mais aussit=F4t que les frais avanc=E9s de 10,5 millions sont en votre poss= ession, vous ne ferez aucune fourniture d'aucune sorte. Vous et moi m=EAme = partagerons, sur la base de 15% pour vous et 85% pour moi , les premiers frais avanc=E9s pour l= 'avance forfaitaire, de la sorte la seconde tranche du paiement servirait = =E0 r=E9gler un fournisseur agr=E9=E9 avec qui nous ferons de la sous-trait= ance pour la fourniture du mat=E9riel en temps exigible, le plus important= r=E9side dans la livraison du mat=E9riel en temps opportun car nous avons un boom de la consommation p=E9troli=E8re, donc un d=E9fit nouve= au =E0 relever de 350 000 nouveaux foyers =E0 fournir en gaz domestique et = environ 280 000 nouveaux v=E9hicules qui s'ajoutent au parc automobile national de notre pa= ys qui ont besoin dans l'imm=E9diat d'=EAtre servi en hydrocarbures pour le= urs consommations journali=E8res. Cette situation a conduit le Comit=E9 d'Attribution =E0 ouv= rir un march=E9 dont le projet de r=E9alisation n'exc=E8dera pas les 3 ( tr= ois) semaines, depuis la date d'attribution du march=E9 au fournisseur jusqu'=E0 la livraison du mat=E9ri= el dans nos locaux techniques. La raison pour laquelle je voudrais que nous partagions cette a= vance est que je suis l=92Administrateur Ex=E9cutif du Comit=E9 depuis cinq= ann=E9es, et je n'ai m=EAme pas une maison personnelle m'appartenant, mon = salaire tr=E8s l=E9ger, repr=E9sente celui d'un cadre africain de pays sous= -d=E9velopp=E9s. Je ne suis pas =E0 mesure de prendre soin ad=E9quatement d= e mes enfants. En fait, les choses sont tr=E8s difficiles pour moi et si je= pars =E0 la retraite, je n'aurai rien sur quoi reposer. --latinmail.com_ltwebml02.localdomain_23cb7995f275e04cd83b2bad00558740-- From owner-linux-xfs@oss.sgi.com Tue Apr 4 20:02:47 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 04 Apr 2006 20:02: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 k3532jgC009929 for ; Tue, 4 Apr 2006 20:02: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 MAA25573; Thu, 6 Apr 2006 12:58:01 +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 k362vxJC1137623; Thu, 6 Apr 2006 12:57:59 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id k362vu9R1136362; Thu, 6 Apr 2006 12:57:56 +1000 (EST) Date: Thu, 6 Apr 2006 12:57:56 +1000 From: Nathan Scott To: LKML Cc: linux-xfs@oss.sgi.com Subject: Re: Bonnie++ Burps on XFS Message-ID: <20060406125756.H1110920@wobbly.melbourne.sgi.com> References: <20060406023445.GB5806@kurtwerks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20060406023445.GB5806@kurtwerks.com>; from kwall@kurtwerks.com on Wed, Apr 05, 2006 at 10:34:45PM -0400 X-archive-position: 7588 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: 794 Lines: 24 On Wed, Apr 05, 2006 at 10:34:45PM -0400, Kurt Wall wrote: > I've been using bonnie++ off and on for a long time. Suddenly, it has > started failing when run against an XFS filesystem situated on a SATA > drive. Here's the output of a run: [ Please report these things to linux-xfs@oss.sgi.com... ] > Delete files in sequential order...Bonnie: drastic I/O error (rmdir): Anything in your system log? > clear if the problems is XFS, some other piece of the kernel, or > bonnie++. Neither dmesg nor syslog shows anything amiss. I suppose > I could strace the run, but I'm not especially eager to deal with > a multi-gigabyte output file if there is a more focused method to > isolate the problem. See if 2.6.16.1 fails too for starters then we'll take it from there. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Apr 4 22:17:56 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 04 Apr 2006 22:18:02 -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 k355HsgC030037 for ; Tue, 4 Apr 2006 22:17:55 -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 PAA27111; Thu, 6 Apr 2006 15:13:08 +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 k365D5JC1139218; Thu, 6 Apr 2006 15:13:05 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id k365D1Jm1137350; Thu, 6 Apr 2006 15:13:01 +1000 (EST) Date: Thu, 6 Apr 2006 15:13:01 +1000 From: Nathan Scott To: Kurt Wall Cc: LKML , linux-xfs@oss.sgi.com Subject: Re: Bonnie++ Burps on XFS Message-ID: <20060406151301.I1110920@wobbly.melbourne.sgi.com> References: <20060406023445.GB5806@kurtwerks.com> <20060406125756.H1110920@wobbly.melbourne.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: <20060406125756.H1110920@wobbly.melbourne.sgi.com>; from nathans@sgi.com on Thu, Apr 06, 2006 at 12:57:56PM +1000 X-archive-position: 7589 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: 658 Lines: 22 On Thu, Apr 06, 2006 at 12:57:56PM +1000, Nathan Scott wrote: > On Wed, Apr 05, 2006 at 10:34:45PM -0400, Kurt Wall wrote: > > I've been using bonnie++ off and on for a long time. Suddenly, it has > > started failing when run against an XFS filesystem situated on a SATA > > drive. Here's the output of a run: > > [ Please report these things to linux-xfs@oss.sgi.com... ] > > > Delete files in sequential order...Bonnie: drastic I/O error (rmdir): > > Anything in your system log? Lemme answer that for you - "no". I've reproduced the problem, I'll get back to you once I've nutted out whats gone wrong. Thanks for reporting it. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Apr 5 02:10:59 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 05 Apr 2006 02:11:04 -0700 (PDT) Received: from mail.ukfsn.org (s2.ukfsn.org [217.158.120.143]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k359AxgC015920 for ; Wed, 5 Apr 2006 02:10:59 -0700 Received: from localhost.localdomain (i-83-67-36-194.freedom2surf.net [83.67.36.194]) by mail.ukfsn.org (Postfix) with ESMTP id 83F37E719C; Thu, 6 Apr 2006 08:57:09 +0100 (BST) Received: from [10.0.0.90] (helo=[10.0.0.90]) by localhost.localdomain with esmtp (Exim 4.50) id 1FRPPH-00066w-IG; Thu, 06 Apr 2006 08:59:55 +0100 Message-ID: <4434CA7A.6020802@dgreaves.com> Date: Thu, 06 Apr 2006 08:59:54 +0100 From: David Greaves User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nathan Scott Cc: Kurt Wall , LKML , linux-xfs@oss.sgi.com Subject: Re: Bonnie++ Burps on XFS References: <20060406023445.GB5806@kurtwerks.com> <20060406125756.H1110920@wobbly.melbourne.sgi.com> <20060406151301.I1110920@wobbly.melbourne.sgi.com> In-Reply-To: <20060406151301.I1110920@wobbly.melbourne.sgi.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-archive-position: 7590 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: david@dgreaves.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1663 Lines: 69 Nathan Scott wrote: >On Thu, Apr 06, 2006 at 12:57:56PM +1000, Nathan Scott wrote: > > >>On Wed, Apr 05, 2006 at 10:34:45PM -0400, Kurt Wall wrote: >> >> >>>I've been using bonnie++ off and on for a long time. Suddenly, it has >>>started failing when run against an XFS filesystem situated on a SATA >>>drive. Here's the output of a run: >>> >>> >>[ Please report these things to linux-xfs@oss.sgi.com... ] >> >> >> >>>Delete files in sequential order...Bonnie: drastic I/O error (rmdir): >>> >>> >>Anything in your system log? >> >> > >Lemme answer that for you - "no". I've reproduced the problem, >I'll get back to you once I've nutted out whats gone wrong. > >Thanks for reporting it. > >cheers. > > > Me too. 2.6.16 I had filesystem corruption and needed ran xfs_repair. After I finished I removed most of the lost and found bits but was left with: haze:/scratch/lost+found# ll total 28 drwxr-xr-x 4 root root 38 2006-04-02 08:29 ./ drwxrwxrwx 26 root root 4096 2006-04-04 18:25 ../ drwxrwxr-x 2 1046 1046 8192 2006-04-02 08:30 658616481/ drwxrwxr-x 2 1046 1046 8192 2006-04-02 08:22 823441168/ haze:/scratch/lost+found# rmdir * rmdir: `658616481': Directory not empty rmdir: `823441168': Directory not empty haze:/scratch/lost+found# ll * 658616481: total 12 drwxrwxr-x 2 1046 1046 8192 2006-04-02 08:30 ./ drwxr-xr-x 4 root root 38 2006-04-02 08:29 ../ 823441168: total 12 drwxrwxr-x 2 1046 1046 8192 2006-04-02 08:22 ./ drwxr-xr-x 4 root root 38 2006-04-02 08:29 ../ Obviously I had an fs corruption (due to raid failure due to some bogus libata errors) so this may not be the same thing. David -- From owner-linux-xfs@oss.sgi.com Wed Apr 5 04:02:20 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 05 Apr 2006 04:02:25 -0700 (PDT) Received: from elfstone.noviforum.si (elfstone.noviforum.si [193.189.169.107]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k35B2JgC026399 for ; Wed, 5 Apr 2006 04:02:19 -0700 Received: from localhost (localhost [127.0.0.1]) by elfstone.noviforum.si (ESMTP) with ESMTP id D235F1B914 for ; Thu, 6 Apr 2006 11:30:23 +0200 (CEST) Received: from dacun.noviforum.si (dacun.noviforum.si [192.168.2.26]) by elfstone.noviforum.si (ESMTP) with ESMTP id ACAE21B912 for ; Thu, 6 Apr 2006 11:30:23 +0200 (CEST) Subject: dcache.c From: Gorazd Golob To: linux-xfs@oss.sgi.com Content-Type: text/plain Date: Thu, 06 Apr 2006 11:34:13 +0200 Message-Id: <1144316053.23522.13.camel@dacun.noviforum.si> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 Content-Transfer-Encoding: 7bit X-archive-position: 7592 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: gorazd.golob@noviforum.si Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1962 Lines: 47 Hello! Does this error have something to do with XFS or straight VFS? All partitions on systems are XFS. tnx, Gorazd [636117.626297] kernel BUG at fs/dcache.c:795! [636117.635583] invalid operand: 0000 [#5] [636117.644775] SMP [636117.653858] Modules linked in: [636117.662962] CPU: 1 [636117.662963] EIP: 0060:[] Not tainted VLI [636117.662965] EFLAGS: 00010202 (2.6.15.6-1) [636117.690389] EIP is at d_instantiate+0x1e/0x5f [636117.699631] eax: e43d1b7c ebx: e43d1bbc ecx: 00008000 edx: dfb3494c [636117.709144] esi: dfb3494c edi: e43d1b7c ebp: dfb347d0 esp: cfcb1d7c [636117.718682] ds: 007b es: 007b ss: 0068 [636117.728195] Process java (pid: 20902, threadinfo=cfcb0000 task=f68e9540) [636117.728527] Stack: 000081a4 00000000 00000000 c02f91e8 e43d1b7c dfb3494c cfcb1e3c cfcb1da8 [636117.738436] 00000000 dfb347b0 dfb3494c dfb3492c c017331f e43d194c dd2e6055 00000001 [636117.748284] dd2e6057 e43d194c cfcb1e14 ed111dac ffffffec c0180f47 ed111dac c06f8b00 [636117.758029] Call Trace: [636117.776745] [] linvfs_mknod+0x170/0x270 [636117.786377] [] sys_stat64+0x18/0x36 [636117.796020] [] dput+0x54/0x1e8 [636117.805665] [] __link_path_walk+0x5fb/0xed7 [636117.815453] [] mntput_no_expire+0x22/0x89 [636117.825225] [] permission+0x85/0xaa [636117.834949] [] linvfs_create+0x0/0xd [636117.844653] [] vfs_create+0x9e/0xf4 [636117.854239] [] open_namei+0xca/0x66c [636117.863769] [] filp_open+0x38/0x60 [636117.873169] [] sys_stat64+0x18/0x36 [636117.882422] [] do_sys_open+0x5b/0xf6 [636117.891487] [] syscall_call+0x7/0xb [636117.900374] Code: 04 24 e8 0a fe ff ff 83 c4 18 5b 5f c3 83 ec 0c 89 7c 24 08 8b 7c 24 10 89 1c 24 89 74 24 04 8d 5f 40 8b 74 24 14 39 5f 40 74 08 <0f> 0b 1b 03 7b 84 5d c0 b8 00 8b 6f c0 e8 49 f4 40 00 85 f6 74 [636117.946096] From owner-linux-xfs@oss.sgi.com Wed Apr 5 08:04:39 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 05 Apr 2006 08:04:43 -0700 (PDT) Received: from spooner.celestial.com (spooner.celestial.com [192.136.111.35]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k35F4dgC018988 for ; Wed, 5 Apr 2006 08:04:39 -0700 Received: from localhost (localhost [127.0.0.1]) by spooner.celestial.com (Postfix) with ESMTP id 076DB30E3E23; Thu, 6 Apr 2006 06:48:17 -0700 (PDT) Received: from spooner.celestial.com ([127.0.0.1]) by localhost (spooner.celestial.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 21471-02; Thu, 6 Apr 2006 06:48:16 -0700 (PDT) Received: from luther.kurtwerks.com (c-67-165-68-161.hsd1.pa.comcast.net [67.165.68.161]) by spooner.celestial.com (Postfix) with ESMTP id C86503036D31; Thu, 6 Apr 2006 06:48:16 -0700 (PDT) Received: by luther.kurtwerks.com (Postfix, from userid 1000) id 99CD034A418; Thu, 6 Apr 2006 09:48:15 -0400 (EDT) Date: Thu, 6 Apr 2006 09:48:15 -0400 From: Kurt Wall To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: Bonnie++ Burps on XFS Message-ID: <20060406134815.GA5678@kurtwerks.com> References: <20060406023445.GB5806@kurtwerks.com> <20060406125756.H1110920@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406125756.H1110920@wobbly.melbourne.sgi.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: Linux 2.6.16krw X-Woot: Woot! X-archive-position: 7593 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: kwall@kurtwerks.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 781 Lines: 30 On Thu, Apr 06, 2006 at 12:57:56PM +1000, Nathan Scott took 29 lines to write: > On Wed, Apr 05, 2006 at 10:34:45PM -0400, Kurt Wall wrote: > > I've been using bonnie++ off and on for a long time. Suddenly, it has > > started failing when run against an XFS filesystem situated on a SATA > > drive. Here's the output of a run: > > [ Please report these things to linux-xfs@oss.sgi.com... ] Will do (note CC). > > Delete files in sequential order...Bonnie: drastic I/O error (rmdir): > > Anything in your system log? No. > See if 2.6.16.1 fails too for starters then we'll take it from there. As soon as the test completes on 2.6.16, I'll spin up a 2.6.16.1 kernel and try that. > cheers. Thanks, Kurt -- Chemistry is applied theology. -- Augustus Stanley Owsley III From owner-linux-xfs@oss.sgi.com Wed Apr 5 12:18:56 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 06 Apr 2006 12:15:27 -0700 (PDT) Received: from saraswathi.solana.com ([198.99.130.12]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k35JIpgC009036 for ; Wed, 5 Apr 2006 12:18:55 -0700 Received: from ccure.user-mode-linux.org (littleton.addtoit.com [198.99.130.129]) by saraswathi.solana.com (8.13.1/8.13.1) with ESMTP id k36Hs8T1020291; Thu, 6 Apr 2006 13:54:08 -0400 Received: from ccure.user-mode-linux.org (localhost.localdomain [127.0.0.1]) by ccure.user-mode-linux.org (8.13.6/8.13.4) with ESMTP id k36GtMvc005146; Thu, 6 Apr 2006 12:55:23 -0400 Message-Id: <200604061655.k36GtMvc005146@ccure.user-mode-linux.org> X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.0.4 To: akpm@osdl.org cc: linux-xfs@oss.sgi.com, Daniel Phillips , linux-kernel@vger.kernel.org, user-mode-linux-devel@lists.sourceforge.net Subject: [PATCH 1/2] Add GFP_NOWAIT Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Apr 2006 12:55:22 -0400 From: Jeff Dike X-archive-position: 7594 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: jdike@addtoit.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1426 Lines: 34 Introduce GFP_NOWAIT, as an alias for GFP_ATOMIC & ~__GFP_HIGH. This also changes XFS, which is the only in-tree user of this idiom that I could find. The XFS piece is compile-tested only. Signed-off-by: Jeff Dike Index: linux-2.6.16/fs/xfs/linux-2.6/xfs_buf.c =================================================================== --- linux-2.6.16.orig/fs/xfs/linux-2.6/xfs_buf.c 2006-04-06 12:16:14.000000000 -0400 +++ linux-2.6.16/fs/xfs/linux-2.6/xfs_buf.c 2006-04-06 12:16:54.000000000 -0400 @@ -182,7 +182,7 @@ free_address( { a_list_t *aentry; - aentry = kmalloc(sizeof(a_list_t), GFP_ATOMIC & ~__GFP_HIGH); + aentry = kmalloc(sizeof(a_list_t), GFP_NOWAIT); if (likely(aentry)) { spin_lock(&as_lock); aentry->next = as_free_head; Index: linux-2.6.16/include/linux/gfp.h =================================================================== --- linux-2.6.16.orig/include/linux/gfp.h 2006-03-21 11:50:12.000000000 -0500 +++ linux-2.6.16/include/linux/gfp.h 2006-04-06 12:15:18.000000000 -0400 @@ -57,6 +57,8 @@ struct vm_area_struct; __GFP_NOFAIL|__GFP_NORETRY|__GFP_NO_GROW|__GFP_COMP| \ __GFP_NOMEMALLOC|__GFP_HARDWALL) +/* This equals 0, but use constants in case they ever change */ +#define GFP_NOWAIT (GFP_ATOMIC & ~__GFP_HIGH) /* GFP_ATOMIC means both !wait (__GFP_WAIT not set) and use emergency pool */ #define GFP_ATOMIC (__GFP_HIGH) #define GFP_NOIO (__GFP_WAIT) From owner-linux-xfs@oss.sgi.com Thu Apr 6 15:12:25 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 06 Apr 2006 15:12:36 -0700 (PDT) Received: from larry.melbourne.sgi.com ([61.14.31.138]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with SMTP id k36MCNgC001296 for ; Thu, 6 Apr 2006 15:12:24 -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 IAA07326; Fri, 7 Apr 2006 08:12:02 +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 k36MBuJC1159397; Fri, 7 Apr 2006 08:11:57 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id k36MBmKo1159170; Fri, 7 Apr 2006 08:11:48 +1000 (EST) Date: Fri, 7 Apr 2006 08:11:48 +1000 From: Nathan Scott To: Jeff Dike Cc: akpm@osdl.org, linux-xfs@oss.sgi.com, Daniel Phillips , linux-kernel@vger.kernel.org, user-mode-linux-devel@lists.sourceforge.net Subject: Re: [PATCH 1/2] Add GFP_NOWAIT Message-ID: <20060407081148.J1110920@wobbly.melbourne.sgi.com> References: <200604061655.k36GtMvc005146@ccure.user-mode-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200604061655.k36GtMvc005146@ccure.user-mode-linux.org>; from jdike@addtoit.com on Thu, Apr 06, 2006 at 12:55:22PM -0400 X-archive-position: 7595 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: 396 Lines: 16 On Thu, Apr 06, 2006 at 12:55:22PM -0400, Jeff Dike wrote: > Introduce GFP_NOWAIT, as an alias for GFP_ATOMIC & ~__GFP_HIGH. > > This also changes XFS, which is the only in-tree user of this idiom that I > could find. The XFS piece is compile-tested only. Looks fine, thanks Jeff. > Signed-off-by: Jeff Dike Acked-by: Nathan Scott cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Apr 6 19:08:57 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 06 Apr 2006 19:09:02 -0700 (PDT) Received: from spooner.celestial.com ([192.136.111.35]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k3728vgC023744 for ; Thu, 6 Apr 2006 19:08:57 -0700 Received: from localhost (localhost [127.0.0.1]) by spooner.celestial.com (Postfix) with ESMTP id 77E3630E6E2B; Thu, 6 Apr 2006 19:08:50 -0700 (PDT) Received: from spooner.celestial.com ([127.0.0.1]) by localhost (spooner.celestial.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 17763-02; Thu, 6 Apr 2006 19:08:50 -0700 (PDT) Received: from luther.kurtwerks.com (c-67-165-68-161.hsd1.pa.comcast.net [67.165.68.161]) by spooner.celestial.com (Postfix) with ESMTP id 3546B301DE1B; Thu, 6 Apr 2006 19:08:50 -0700 (PDT) Received: by luther.kurtwerks.com (Postfix, from userid 1000) id 8881C2958; Thu, 6 Apr 2006 22:08:49 -0400 (EDT) Date: Thu, 6 Apr 2006 22:08:48 -0400 From: Kurt Wall To: linux-xfs@oss.sgi.com Cc: nathans@sgi.com Subject: Re: Bonnie++ Burps on XFS Message-ID: <20060407020848.GA24446@kurtwerks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060406023445.GB5806@kurtwerks.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: Linux 2.6.16krw X-Woot: Woot! X-archive-position: 7596 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: kwall@kurtwerks.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 304 Lines: 13 Running Bonnie++ against XFS on 2.6.16 does not encounter the same fault. I'm running it against a 2.6.16.1 test now and will report the results shortly. Regards, Kurt -- Commitment, n.: Commitment can be illustrated by a breakfast of ham and eggs. The chicken was involved, the pig was committed. From owner-linux-xfs@oss.sgi.com Fri Apr 7 00:23:33 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 07 Apr 2006 00:24: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 k377NVgC024561 for ; Fri, 7 Apr 2006 00:23:32 -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 RAA13941; Fri, 7 Apr 2006 17:23:31 +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 k377NQJC1169741; Fri, 7 Apr 2006 17:23:28 +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 k378JUDh002811; Fri, 7 Apr 2006 18:19:31 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id k378JSNb002809; Fri, 7 Apr 2006 18:19:28 +1000 Date: Fri, 7 Apr 2006 18:19:28 +1000 From: Nathan Scott To: Kurt Wall Cc: linux-xfs@oss.sgi.com Subject: Re: Bonnie++ Burps on XFS Message-ID: <20060407081928.GD1598@frodo> References: <20060406023445.GB5806@kurtwerks.com> <20060407020848.GA24446@kurtwerks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060407020848.GA24446@kurtwerks.com> User-Agent: Mutt/1.5.3i X-archive-position: 7597 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: 566 Lines: 22 On Thu, Apr 06, 2006 at 10:08:48PM -0400, Kurt Wall wrote: > > Running Bonnie++ against XFS on 2.6.16 does not encounter the > same fault. I'm running it against a 2.6.16.1 test now and will > report the results shortly. Hi Kurt, I've got this narrowed down to a few XFS mods now, I'm still binary chopping through the last few to narrow it down to one (test case takes awhile for me). Should have it narrowed right down on Monday, and will get the owner of the offending change to fix it up then. I think you'll find 2.6.16.1 is OK too. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Apr 7 01:50:34 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 07 Apr 2006 01:50:37 -0700 (PDT) Received: from shark.2a.pl ([195.117.102.3]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k378oUgC000452 for ; Fri, 7 Apr 2006 01:50:33 -0700 Received: from localhost (av.2a.pl [10.0.0.99]) by shark.2a.pl (ESMTP) with ESMTP id 269C0A6E8E for ; Fri, 7 Apr 2006 10:50:23 +0200 (CEST) Received: from shark.2a.pl ([10.0.0.3]) by localhost (av.2a.pl [10.0.0.99]) (amavisd-new, port 10024) with ESMTP id 85147-02 for ; Fri, 7 Apr 2006 10:49:12 +0200 (CEST) Received: from [127.0.0.1] (bya38.internetdsl.tpnet.pl [83.19.4.38]) by shark.2a.pl (ESMTP) with ESMTP id 6CE49A6E7B for ; Fri, 7 Apr 2006 10:50:14 +0200 (CEST) Message-ID: <443627B1.5090100@ursynow.2a.pl> Date: Fri, 07 Apr 2006 10:49:53 +0200 From: =?ISO-8859-2?Q?Artur_Mak=F3wka?= User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: server crashing Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 7598 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: juice@ursynow.2a.pl Precedence: bulk X-list: linux-xfs Status: O Content-Length: 3869 Lines: 82 Hello, i have heavy-traffic server that is crashing every few days. When it crashes i cannot login through ssh and no services are working. One time it 'crashed' when i was logged in though (i had luck), and i saw 'Input/Output Error' when this happened as i tried to run any command (like ps, ls or anything) it is RAID 0 array made from two sata drives. it happened yet another time today, after hard reset. machine was only responding to pings, all other actions was not possible, it was likely in this Input/Output error mode. i saw this in logs: Apr 7 10:24:52 alpha324 kernel: [] find_get_pages_tag+0x46/0x90 Apr 7 10:24:52 alpha324 kernel: [] linvfs_writepage+0x72/0x130 Apr 7 10:24:52 alpha324 kernel: [] linvfs_writepage+0x0/0x130 Apr 7 10:24:52 alpha324 kernel: [] mpage_writepages+0x25c/0x440 Apr 7 10:24:52 alpha324 kernel: [] xfs_iflush+0x371/0x4e0 Apr 7 10:24:52 alpha324 kernel: [] linvfs_writepage+0x0/0x130 Apr 7 10:24:52 alpha324 kernel: [] do_writepages+0x39/0x40 Apr 7 10:24:52 alpha324 kernel: [] __sync_single_inode+0x65/0x240 Apr 7 10:24:52 alpha324 kernel: [] __writeback_single_inode+0x46/0x180 Apr 7 10:24:52 alpha324 kernel: [] sync_sb_inodes+0x1ce/0x2b0 Apr 7 10:24:52 alpha324 kernel: [] writeback_inodes+0x4d/0xa0 Apr 7 10:24:52 alpha324 kernel: [] wb_kupdate+0xb5/0x130 Apr 7 10:24:52 alpha324 kernel: [] pdflush+0x0/0x30 Apr 7 10:24:52 alpha324 kernel: [] __pdflush+0x9d/0x140 Apr 7 10:24:52 alpha324 kernel: [] pdflush+0x28/0x30 Apr 7 10:24:52 alpha324 kernel: [] wb_kupdate+0x0/0x130 Apr 7 10:24:52 alpha324 kernel: [] kthread+0xb6/0xc0 Apr 7 10:24:52 alpha324 kernel: [] kthread+0x0/0xc0 Apr 7 10:24:52 alpha324 kernel: [] kernel_thread_helper+0x5/0xc Apr 7 10:24:52 alpha324 kernel: XFS internal error XFS_WANT_CORRUPTED_RETURN at line 298 of file fs/xfs/xfs_alloc.c. Caller 0xc01f5091 Apr 7 10:24:52 alpha324 kernel: [] xfs_alloc_fixup_trees+0x2ba/0x420 Apr 7 10:24:52 alpha324 kernel: [] xfs_alloc_ag_vextent_near+0x871/0xc80 Apr 7 10:24:52 alpha324 kernel: [] xfs_btree_init_cursor+0x38/0x1d0 Apr 7 10:24:52 alpha324 kernel: [] xfs_alloc_ag_vextent_near+0x871/0xc80 Apr 7 10:24:52 alpha324 kernel: [] xfs_alloc_ag_vextent+0x7d/0x110 Apr 7 10:24:52 alpha324 kernel: [] xfs_alloc_vextent+0x25a/0x590 Apr 7 10:24:52 alpha324 kernel: [] xfs_bmap_alloc+0x13f0/0x1a00 Apr 7 10:24:52 alpha324 kernel: [] kobject_release+0x0/0x10 Apr 7 10:24:52 alpha324 kernel: [] scsi_finish_command+0x24/0xb0 Apr 7 10:24:52 alpha324 kernel: [] xfs_bmap_do_search_extents+0xe5/0x470 This is longer, but it just mainly repeats itself. (at least it looks like to me, if you want full output, please let me know) When previous crashes happened, i ran xfs_repair and i thought it will help, but apparently it didnt. Of course i'm going to run it anyways at night, but i doubt this will help this time. i'm using kernel 2.6.15.7 but i was also using 2.6.14 kernels and 2.6.16.1 for just a test few days ago, and that didnt help. my xfs system is mounted like this: /dev/md0 on / type xfs (rw,noatime) on this server traffic is heavy, but not in terms of number of MB/s. It is just like constant 2-3 MB/s. It is rather number of I/O request heavy - i have like 200 apaches running constantly, many pure-ftpds, postfix, mysql and such. Although LA is usually around 2-3 maximum. Is it possible that this is some kind of XFS bug? (i don't have this list subscribed, if you dont mind replying to my mail...) thanks in advance and please let me know if you need any more info From owner-linux-xfs@oss.sgi.com Fri Apr 7 05:44:24 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 07 Apr 2006 05:44:27 -0700 (PDT) Received: from spooner.celestial.com (spooner.celestial.com [192.136.111.35]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k37CiNgC021800 for ; Fri, 7 Apr 2006 05:44:24 -0700 Received: from localhost (localhost [127.0.0.1]) by spooner.celestial.com (Postfix) with ESMTP id BA37930E6E4F; Fri, 7 Apr 2006 05:44:26 -0700 (PDT) Received: from spooner.celestial.com ([127.0.0.1]) by localhost (spooner.celestial.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 20411-05; Fri, 7 Apr 2006 05:44:26 -0700 (PDT) Received: from luther.kurtwerks.com (c-67-165-68-161.hsd1.pa.comcast.net [67.165.68.161]) by spooner.celestial.com (Postfix) with ESMTP id 6181230E6E45; Fri, 7 Apr 2006 05:44:26 -0700 (PDT) Received: by luther.kurtwerks.com (Postfix, from userid 1000) id 8845B6AF3C9; Fri, 7 Apr 2006 08:44:22 -0400 (EDT) Date: Fri, 7 Apr 2006 08:44:21 -0400 From: Kurt Wall To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: Bonnie++ Burps on XFS Message-ID: <20060407124421.GA5521@kurtwerks.com> References: <20060406023445.GB5806@kurtwerks.com> <20060407020848.GA24446@kurtwerks.com> <20060407081928.GD1598@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060407081928.GD1598@frodo> User-Agent: Mutt/1.4.2.1i X-Operating-System: Linux 2.6.16krw X-Woot: Woot! X-archive-position: 7599 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: kwall@kurtwerks.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1202 Lines: 39 On Fri, Apr 07, 2006 at 06:19:28PM +1000, Nathan Scott took 22 lines to write: > On Thu, Apr 06, 2006 at 10:08:48PM -0400, Kurt Wall wrote: > > > > Running Bonnie++ against XFS on 2.6.16 does not encounter the > > same fault. I'm running it against a 2.6.16.1 test now and will > > report the results shortly. > > Hi Kurt, Hello, Nathan, > I've got this narrowed down to a few XFS mods now, I'm still > binary chopping through the last few to narrow it down to one > (test case takes awhile for me). > > Should have it narrowed right down on Monday, and will get the > owner of the offending change to fix it up then. No problem. When I booted to 2.6.16 and ran xfs_repair on my benchmark XFS partition, it fixed some sort of corruption and I was able to delete the empty directories. I find it curious that it only happens on SATA drives, so I'll be interested to see what the problem and solution ends up being. If it matters, the SATA drive in question uses the sata_sil driver. > I think you'll find 2.6.16.1 is OK too. Indeed I did. The test finished up over night without incident. Regards, Kurt -- Paul's Law: In America, it's not how much an item costs, it's how much you save. From owner-linux-xfs@oss.sgi.com Sun Apr 9 08:16:37 2006 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 09 Apr 2006 08:16:40 -0700 (PDT) Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.168]) by oss.sgi.com (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id k39FGZgC013667 for ; Sun, 9 Apr 2006 08:16:36 -0700 Received: by uproxy.gmail.com with SMTP id u2so441028uge for ; Sun, 09 Apr 2006 08:16:37 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type; b=YH0mPoCLrShweXcBfIo4c71k6aavKP4OIOjOFSMvrAgPQghWaC3OwjyJMscoBNpRICSuuUcMIQ9P84xu/hQyxjFqRUXYtD/VJSgZ09624SldSngjcblL5qRVJ3G5d+ARiKXqsf5Z+xQfIufakuDD6w9XZ7e+rPNpf3ZPQRi7kXU= Received: by 10.66.249.10 with SMTP id w10mr2523431ugh; Sun, 09 Apr 2006 07:15:14 -0700 (PDT) Received: from ?192.168.1.9? ( [84.210.202.203]) by mx.gmail.com with ESMTP id k1sm20433ugf.2006.04.09.07.15.13; Sun, 09 Apr 2006 07:15:14 -0700 (PDT) Message-ID: <443916EC.10809@gmail.com> Date: Sun, 09 Apr 2006 16:15:08 +0200 From: =?ISO-8859-1?Q?Christian_R=F8snes?= User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: BUG: soft lockup detected on CPU#5 / xfsdatad Content-Type: multipart/mixed; boundary="------------050705090807090309030205" X-archive-position: 7601 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: christian.rosnes@gmail.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 42970 Lines: 932 This is a multi-part message in MIME format. --------------050705090807090309030205 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hi I'm not sure if this is XFS specific, but here goes: This night a brand new Intel Xeon 2.80GHz 2cpu/dual-core server running: Debian 3.1 X86-64 (64-bit), Vanilla Linux 2.6.16 compiled from source, PostgreSQL 8.1.3 (64-bit) reported two 'BUG: soft lockup detected on CPU#5!' messages. A PostgreSQL 'vacuum analyze' job was running at the time (this job runs 4 times a day on this server). The server had been running previously for about 7 days without any problems. Both the root- and database-partition(/dev/sdb1) are xfs partitions. The database partition is residing on a DELL SAN. Any ideas what might have caused this 'soft lockup' ? Thanks Christian Also, please find enclosed a text file ('bug.2006.04.09.txt') containing additional information about this server. Bug message: =================================================== BUG: soft lockup detected on CPU#5 Apr 9 01:05:30 db2 kernel: CPU 5: Apr 9 01:05:30 db2 kernel: Modules linked in: qla2400 qla2xxx ipv6 ide_floppy generic hw_random tsdev mousedev joydev usbhid shpchp pci_hotplug ehci_hcd uhci_hcd usbcore siimage piix psmouse ide_generic ide_disk ide_cd ide_core genrtc unix Apr 9 01:05:30 db2 kernel: Pid: 242, comm: xfsdatad/5 Not tainted 2.6.16FC #1 Apr 9 01:05:30 db2 kernel: RIP: 0010:[] {_spin_unlock_irqrestore+8} Apr 9 01:05:30 db2 kernel: RSP: 0018:ffff81023f90dda0 EFLAGS: 00000292 Apr 9 01:05:30 db2 kernel: RAX: ffff810008e2bff0 RBX: ffffffff80127606 RCX: ffff810008e2bff0 Apr 9 01:05:30 db2 kernel: RDX: ffff810008e2bff0 RSI: 0000000000000292 RDI: ffff810008e2bfe8 Apr 9 01:05:30 db2 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff81015489e280 Apr 9 01:05:30 db2 kernel: R10: 0000000000000200 R11: 0000000000000000 R12: ffffffff801412fe Apr 9 01:05:30 db2 kernel: R13: ffff81023f90dd58 R14: ffff81023f90dda8 R15: ffff810008e2bff0 Apr 9 01:05:30 db2 kernel: FS: 0000000000000000(0000) GS:ffff8101ffe2aa40(0000) knlGS:0000000000000000 Apr 9 01:05:30 db2 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Apr 9 01:05:30 db2 kernel: CR2: 00002aef2ca6fabf CR3: 000000018f9d3000 CR4: 00000000000006a0 Apr 9 01:05:30 db2 kernel: Apr 9 01:05:30 db2 kernel: Call Trace: {__wake_up_bit+41} {end_buffer_async_write+297} Apr 9 01:05:30 db2 kernel: {xfs_destroy_ioend+22} {xfs_destroy_ioend+31} Apr 9 01:05:30 db2 kernel: {run_workqueue+179} {keventd_create_kthread+0} Apr 9 01:05:30 db2 kernel: {worker_thread+301} {thread_return+0} Apr 9 01:05:30 db2 kernel: {default_wake_function+0} {default_wake_function+0} Apr 9 01:05:30 db2 kernel: {worker_thread+0} {worker_thread+0} Apr 9 01:05:30 db2 kernel: {kthread+147} {child_rip+8} Apr 9 01:05:30 db2 kernel: {keventd_create_kthread+0} {kthread+0} Apr 9 01:05:30 db2 kernel: {child_rip+0} Apr 9 01:05:47 db2 kernel: CPU 5: Apr 9 01:05:47 db2 kernel: Modules linked in: qla2400 qla2xxx ipv6 ide_floppy generic hw_random tsdev mousedev joydev usbhid shpchp pci_hotplug ehci_hcd uhci_hcd usbcore siimage piix psmouse ide_generic ide_disk ide_cd ide_core genrtc unix Apr 9 01:05:47 db2 kernel: Pid: 242, comm: xfsdatad/5 Not tainted 2.6.16FC #1 Apr 9 01:05:47 db2 kernel: RIP: 0010:[] {_spin_unlock_irqrestore+8} Apr 9 01:05:47 db2 kernel: RSP: 0018:ffff81023f90dda0 EFLAGS: 00000292 Apr 9 01:05:47 db2 kernel: RAX: ffff810008e28870 RBX: ffffffff80127606 RCX: ffff810008e28870 Apr 9 01:05:47 db2 kernel: RDX: ffff810008e28870 RSI: 0000000000000292 RDI: ffff810008e28868 Apr 9 01:05:47 db2 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff81023f0b8f40 Apr 9 01:05:47 db2 kernel: R10: 0000000000000200 R11: 0000000000000000 R12: ffffffff801412fe Apr 9 01:05:47 db2 kernel: R13: ffff81023f90dd58 R14: ffff81023f90dda8 R15: ffff810008e28870 Apr 9 01:05:47 db2 kernel: FS: 0000000000000000(0000) GS:ffff8101ffe2aa40(0000) knlGS:0000000000000000 Apr 9 01:05:47 db2 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Apr 9 01:05:47 db2 kernel: CR2: 00002aef2c103abf CR3: 0000000210474000 CR4: 00000000000006a0 Apr 9 01:05:47 db2 kernel: Apr 9 01:05:47 db2 kernel: Call Trace: {__wake_up_bit+41} {end_buffer_async_write+297} Apr 9 01:05:47 db2 kernel: {xfs_destroy_ioend+22} {xfs_destroy_ioend+31} Apr 9 01:05:47 db2 kernel: {run_workqueue+179} {keventd_create_kthread+0} Apr 9 01:05:47 db2 kernel: {worker_thread+301} {thread_return+0} Apr 9 01:05:47 db2 kernel: {default_wake_function+0} {default_wake_function+0} Apr 9 01:05:47 db2 kernel: {worker_thread+0} {worker_thread+0} Apr 9 01:05:47 db2 kernel: {kthread+147} {child_rip+8} Apr 9 01:05:47 db2 kernel: {keventd_create_kthread+0} {kthread+0} Apr 9 01:05:47 db2 kernel: {child_rip+0} --------------050705090807090309030205 Content-Type: text/plain; name="bug.2006.04.09.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="bug.2006.04.09.txt" Bug text: Apr 9 01:05:30 db2 kernel: CPU 5: Apr 9 01:05:30 db2 kernel: Modules linked in: qla2400 qla2xxx ipv6 ide_floppy generic hw_random tsdev mousedev joydev usbhid shpchp pci_hotplug ehci_hcd uhci_hcd usbcore siimage piix psmouse ide_generic ide_disk ide_cd ide_core genrtc unix Apr 9 01:05:30 db2 kernel: Pid: 242, comm: xfsdatad/5 Not tainted 2.6.16FC #1 Apr 9 01:05:30 db2 kernel: RIP: 0010:[] {_spin_unlock_irqrestore+8} Apr 9 01:05:30 db2 kernel: RSP: 0018:ffff81023f90dda0 EFLAGS: 00000292 Apr 9 01:05:30 db2 kernel: RAX: ffff810008e2bff0 RBX: ffffffff80127606 RCX: ffff810008e2bff0 Apr 9 01:05:30 db2 kernel: RDX: ffff810008e2bff0 RSI: 0000000000000292 RDI: ffff810008e2bfe8 Apr 9 01:05:30 db2 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff81015489e280 Apr 9 01:05:30 db2 kernel: R10: 0000000000000200 R11: 0000000000000000 R12: ffffffff801412fe Apr 9 01:05:30 db2 kernel: R13: ffff81023f90dd58 R14: ffff81023f90dda8 R15: ffff810008e2bff0 Apr 9 01:05:30 db2 kernel: FS: 0000000000000000(0000) GS:ffff8101ffe2aa40(0000) knlGS:0000000000000000 Apr 9 01:05:30 db2 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Apr 9 01:05:30 db2 kernel: CR2: 00002aef2ca6fabf CR3: 000000018f9d3000 CR4: 00000000000006a0 Apr 9 01:05:30 db2 kernel: Apr 9 01:05:30 db2 kernel: Call Trace: {__wake_up_bit+41} {end_buffer_async_write+297} Apr 9 01:05:30 db2 kernel: {xfs_destroy_ioend+22} {xfs_destroy_ioend+31} Apr 9 01:05:30 db2 kernel: {run_workqueue+179} {keventd_create_kthread+0} Apr 9 01:05:30 db2 kernel: {worker_thread+301} {thread_return+0} Apr 9 01:05:30 db2 kernel: {default_wake_function+0} {default_wake_function+0} Apr 9 01:05:30 db2 kernel: {worker_thread+0} {worker_thread+0} Apr 9 01:05:30 db2 kernel: {kthread+147} {child_rip+8} Apr 9 01:05:30 db2 kernel: {keventd_create_kthread+0} {kthread+0} Apr 9 01:05:30 db2 kernel: {child_rip+0} Apr 9 01:05:47 db2 kernel: CPU 5: Apr 9 01:05:47 db2 kernel: Modules linked in: qla2400 qla2xxx ipv6 ide_floppy generic hw_random tsdev mousedev joydev usbhid shpchp pci_hotplug ehci_hcd uhci_hcd usbcore siimage piix psmouse ide_generic ide_disk ide_cd ide_core genrtc unix Apr 9 01:05:47 db2 kernel: Pid: 242, comm: xfsdatad/5 Not tainted 2.6.16FC #1 Apr 9 01:05:47 db2 kernel: RIP: 0010:[] {_spin_unlock_irqrestore+8} Apr 9 01:05:47 db2 kernel: RSP: 0018:ffff81023f90dda0 EFLAGS: 00000292 Apr 9 01:05:47 db2 kernel: RAX: ffff810008e28870 RBX: ffffffff80127606 RCX: ffff810008e28870 Apr 9 01:05:47 db2 kernel: RDX: ffff810008e28870 RSI: 0000000000000292 RDI: ffff810008e28868 Apr 9 01:05:47 db2 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: ffff81023f0b8f40 Apr 9 01:05:47 db2 kernel: R10: 0000000000000200 R11: 0000000000000000 R12: ffffffff801412fe Apr 9 01:05:47 db2 kernel: R13: ffff81023f90dd58 R14: ffff81023f90dda8 R15: ffff810008e28870 Apr 9 01:05:47 db2 kernel: FS: 0000000000000000(0000) GS:ffff8101ffe2aa40(0000) knlGS:0000000000000000 Apr 9 01:05:47 db2 kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Apr 9 01:05:47 db2 kernel: CR2: 00002aef2c103abf CR3: 0000000210474000 CR4: 00000000000006a0 Apr 9 01:05:47 db2 kernel: Apr 9 01:05:47 db2 kernel: Call Trace: {__wake_up_bit+41} {end_buffer_async_write+297} Apr 9 01:05:47 db2 kernel: {xfs_destroy_ioend+22} {xfs_destroy_ioend+31} Apr 9 01:05:47 db2 kernel: {run_workqueue+179} {keventd_create_kthread+0} Apr 9 01:05:47 db2 kernel: {worker_thread+301} {thread_return+0} Apr 9 01:05:47 db2 kernel: {default_wake_function+0} {default_wake_function+0} Apr 9 01:05:47 db2 kernel: {worker_thread+0} {worker_thread+0} Apr 9 01:05:47 db2 kernel: {kthread+147} {child_rip+8} Apr 9 01:05:47 db2 kernel: {keventd_create_kthread+0} {kthread+0} Apr 9 01:05:47 db2 kernel: {child_rip+0} =================================================== Running: sh ./ver_linux If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes. Linux db2 2.6.16FC #1 SMP Wed Mar 22 12:31:28 CET 2006 x86_64 GNU/Linux Gnu C 3.3.5 Gnu make 3.80 binutils 2.15 util-linux 2.12p mount 2.12p module-init-tools 3.2-pre1 e2fsprogs 1.37 reiserfsprogs line reiser4progs line xfsprogs 2.6.20 PPP 2.4.3 nfs-utils 1.0.6 Linux C Library 2.3.2 Dynamic linker (ldd) 2.3.2 Procps 3.2.1 Net-tools 1.60 Console-tools 0.2.3 Sh-utils 5.2.1 Modules Loaded qla2400 qla2xxx ipv6 ide_floppy generic hw_random tsdev mousedev joydev usbhid shpchp pci_hotplug ehci_hcd uhci_hcd usbcore siimage piix psmouse ide_generic ide_disk ide_cd ide_core genrtc unix =================================================== df: Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda3 63208996 5892208 57316788 10% / tmpfs 4087716 0 4087716 0% /dev/shm /dev/sda1 466662 14176 427587 4% /boot /dev/sdb1 178170116 4246400 173923716 3% /san =================================================== mount: /dev/sda3 on / type xfs (rw,noatime) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext2 (rw,noatime) usbfs on /proc/bus/usb type usbfs (rw) /dev/sdb1 on /san type xfs (rw,noatime) =================================================== ===================================================== Running: cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7 0: 226 0 0 0 0 277717661 0 0 IO-APIC-edge timer 1: 0 0 0 0 0 9 0 0 IO-APIC-edge i8042 9: 0 0 0 0 0 0 0 0 IO-APIC-level acpi 14: 0 0 0 0 0 13 0 0 IO-APIC-edge ide0 169: 0 0 0 0 0 5649134 0 0 IO-APIC-level uhci_hcd:usb1, qla2400 185: 0 0 0 0 0 545423724 0 0 IO-APIC-level eth0 201: 0 0 0 0 0 215363073 0 0 IO-APIC-level megaraid 209: 0 0 0 0 0 63 0 0 IO-APIC-level ide2, ehci_hcd:usb4 217: 0 0 0 0 0 0 0 0 IO-APIC-level uhci_hcd:usb2 225: 0 0 0 0 0 0 0 0 IO-APIC-level uhci_hcd:usb3 NMI: 62452 249384 63225 62699 62361 249362 63203 62677 LOC: 277687412 277301786 277700824 277701522 277687319 277301693 277700731 277701429 ERR: 7 MIS: 0 ===================================================== Running: cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5591.58 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 1 siblings : 4 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.49 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 2 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.50 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 3 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 1 siblings : 4 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.61 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 4 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.63 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 5 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 1 siblings : 4 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.60 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 6 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 0 siblings : 4 core id : 1 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.65 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: processor : 7 vendor_id : GenuineIntel cpu family : 15 model : 4 model name : Intel(R) Xeon(TM) CPU 2.80GHz stepping : 8 cpu MHz : 2793.213 cache size : 2048 KB physical id : 1 siblings : 4 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl est cid cx16 xtpr lahf_lm bogomips : 5586.54 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 48 bits virtual power management: ===================================================== Running: cat /proc/modules qla2400 201856 0 - Live 0xffffffff880f6000 qla2xxx 141548 2 qla2400, Live 0xffffffff880d2000 ipv6 292736 34 - Live 0xffffffff88130000 ide_floppy 22272 0 - Live 0xffffffff88129000 generic 7172 0 [permanent], Live 0xffffffff880cf000 hw_random 7720 0 - Live 0xffffffff880cc000 tsdev 10240 0 - Live 0xffffffff880c8000 mousedev 14956 0 - Live 0xffffffff880c3000 joydev 12800 0 - Live 0xffffffff880be000 usbhid 42784 0 - Live 0xffffffff880b2000 shpchp 51488 0 - Live 0xffffffff880a4000 pci_hotplug 32512 1 shpchp, Live 0xffffffff8809b000 ehci_hcd 35976 0 - Live 0xffffffff88091000 uhci_hcd 36896 0 - Live 0xffffffff88086000 usbcore 148008 4 usbhid,ehci_hcd,uhci_hcd, Live 0xffffffff88060000 siimage 14336 0 [permanent], Live 0xffffffff8805b000 piix 14212 0 [permanent], Live 0xffffffff88056000 psmouse 44048 0 - Live 0xffffffff8804a000 ide_generic 2816 0 [permanent], Live 0xffffffff88048000 ide_disk 19584 0 - Live 0xffffffff88042000 ide_cd 47240 0 - Live 0xffffffff88035000 ide_core 153892 7 ide_floppy,generic,siimage,piix,ide_generic,ide_disk,ide_cd, Live 0xffffffff8800e000 genrtc 12108 0 - Live 0xffffffff8800a000 unix 33560 164 - Live 0xffffffff88000000 ===================================================== Running: cat /proc/ioports 0000-001f : dma1 0020-0021 : pic1 0040-0043 : timer0 0050-0053 : timer1 0060-006f : keyboard 0080-008f : dma page reg 00a0-00a1 : pic2 00c0-00df : dma2 00f0-00ff : fpu 01f0-01f7 : ide0 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial 0800-087f : 0000:00:1f.0 0800-0803 : PM1a_EVT_BLK 0804-0805 : PM1a_CNT_BLK 0808-080b : PM_TMR 0828-082f : GPE0_BLK 0880-08bf : 0000:00:1f.0 0cf8-0cff : PCI conf1 aca0-acbf : 0000:00:1d.2 aca0-acbf : uhci_hcd acc0-acdf : 0000:00:1d.1 acc0-acdf : uhci_hcd ace0-acff : 0000:00:1d.0 ace0-acff : uhci_hcd b000-bfff : PCI Bus #09 b800-b8ff : 0000:09:0d.0 bc70-bc7f : 0000:09:06.0 bc80-bcbf : 0000:09:05.1 bc80-bc87 : serial bcd0-bcd3 : 0000:09:06.0 bcd8-bcdf : 0000:09:06.0 bce4-bce7 : 0000:09:06.0 bce8-bcef : 0000:09:05.0 bcf0-bcf7 : 0000:09:06.0 bcf8-bcff : 0000:09:05.0 c000-dfff : PCI Bus #05 c000-cfff : PCI Bus #07 ccc0-ccff : 0000:07:08.0 ccc0-ccff : e1000 d000-dfff : PCI Bus #06 dcc0-dcff : 0000:06:07.0 dcc0-dcff : e1000 e000-efff : PCI Bus #04 ec00-ecff : 0000:04:00.0 ec00-ecff : qla2400 fc00-fc0f : 0000:00:1f.1 fc08-fc0f : ide1 ===================================================== Running: cat /proc/iomem 00000000-0009ffff : System RAM 000a0000-000bffff : Video RAM area 000c0000-000c7fff : Video ROM 000cb000-000cbfff : Adapter ROM 000cc000-000ccfff : Adapter ROM 000cd000-000d0bff : Adapter ROM 000d1000-000d31ff : Adapter ROM 000d3800-000d3dff : Adapter ROM 000f0000-000fffff : System ROM 00100000-bffbffff : System RAM 00100000-003e4cda : Kernel code 003e4cdb-00520b0f : Kernel data bffc0000-bffcfbff : ACPI Tables bffcfc00-bfffefff : reserved c0000000-c00003ff : 0000:00:1f.1 c8000000-d7ffffff : PCI Bus #09 c8000000-cfffffff : 0000:09:0d.0 d0000000-d007ffff : 0000:09:06.0 d0080000-d009ffff : 0000:09:0d.0 d00a0000-d00affff : 0000:09:05.0 d7f00000-d7f7ffff : 0000:09:05.1 d7fff000-d7ffffff : 0000:09:05.0 d8000000-d80fffff : PCI Bus #01 d8000000-d80fffff : PCI Bus #02 d80f0000-d80fffff : 0000:02:0e.0 d80f0000-d80fffff : MegaRAID: LSI Logic Corporation df300000-df4fffff : PCI Bus #09 df3e0000-df3effff : 0000:09:0d.0 df3fec00-df3fecff : 0000:09:06.0 df3fec00-df3fecff : SiI680 df3ff000-df3fffff : 0000:09:05.1 df500000-df9fffff : PCI Bus #05 df600000-df7fffff : PCI Bus #07 df6e0000-df6fffff : 0000:07:08.0 df6e0000-df6fffff : e1000 df800000-df9fffff : PCI Bus #06 df8e0000-df8fffff : 0000:06:07.0 df8e0000-df8fffff : e1000 dfa00000-dfbfffff : PCI Bus #04 dfafc000-dfafffff : 0000:04:00.0 dfafc000-dfafffff : qla2400 dfb00000-dfb3ffff : 0000:04:00.0 dfc00000-dfefffff : PCI Bus #01 dfd00000-dfefffff : PCI Bus #02 dfdc0000-dfdfffff : 0000:02:0e.0 dfdc0000-dfdfffff : MegaRAID: LSI Logic Corporation dfe00000-dfe1ffff : 0000:02:0e.0 dff00000-dff003ff : 0000:00:1d.7 dff00000-dff003ff : ehci_hcd e0000000-fec8ffff : reserved fed00000-fed003ff : reserved fee00000-fee0ffff : reserved ffb00000-ffffffff : reserved 100000000-1ffffdfff : System RAM 1ffffe000-1ffffffff : reserved 200000000-23fffffff : System RAM ===================================================== Running: lspci -vvv 0000:00:00.0 Host bridge: Intel Corp. Server Memory Controller Hub (rev 09) Subsystem: Dell: Unknown device 016d Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Address: fee00000 Data: 0000 Capabilities: [64] #10 [0041] 0000:00:04.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B0 (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Address: fee00000 Data: 0000 Capabilities: [64] #10 [0141] 0000:00:05.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port B1 (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Address: fee00000 Data: 0000 Capabilities: [64] #10 [0041] 0000:00:06.0 PCI bridge: Intel Corp. Memory Controller Hub PCI Express Port C0 (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Message Signalled Interrupts: 64bit- Queue=0/1 Enable- Address: fee00000 Data: 0000 Capabilities: [64] #10 [0141] 0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell: Unknown device 016d Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- FastB2B- 0000:00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- Region 1: I/O ports at Region 2: I/O ports at Region 3: I/O ports at Region 4: I/O ports at fc00 [size=16] Region 5: Memory at c0000000 (32-bit, non-prefetchable) [size=1K] 0000:01:00.0 PCI bridge: Intel Corp. 80332 [Dobson] I/O processor (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: [44] #10 [0071] Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [6c] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d8] 0000:01:00.2 PCI bridge: Intel Corp. 80332 [Dobson] I/O processor (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: [44] #10 [0071] Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [6c] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d8] 0000:02:0e.0 RAID bus controller: Dell PowerEdge Expandable RAID controller 4 (rev 06) Subsystem: Dell PowerEdge Expandable RAID Controller 4e/Di Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping+ SERR+ FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Reset- FastB2B- Capabilities: [44] #10 [0071] Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [6c] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d8] 0000:05:00.2 PCI bridge: Intel Corp. PCI Bridge Hub B (rev 09) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B- Capabilities: [44] #10 [0071] Capabilities: [5c] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Address: 0000000000000000 Data: 0000 Capabilities: [6c] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d8] 0000:06:07.0 Ethernet controller: Intel Corp. 82541GI/PI Gigabit Ethernet Controller (rev 05) Subsystem: Dell: Unknown device 016d Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort-