From owner-linux-xfs@oss.sgi.com Sun Jun 1 03:50:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 03:50:35 -0700 (PDT) Received: from mail.mnsu.edu (Mail.MNSU.EDU [134.29.1.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h51AoI2x025865 for ; Sun, 1 Jun 2003 03:50:19 -0700 Received: from hundstad.net (dyn5390.MavNet.MNSU.EDU [134.29.77.239]) by mail.mnsu.edu (8.12.9/8.12.9) with ESMTP id h51AoCeN031316 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 1 Jun 2003 05:50:12 -0500 Message-ID: <3ED9DA64.8010703@hundstad.net> Date: Sun, 01 Jun 2003 05:50:12 -0500 From: "Jeffrey E. Hundstad" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: crash on linux-2.4.21-rc6-xfs (latest cvs) X-Priority: 2 (high) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4190 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jeffrey@hundstad.net Precedence: bulk X-list: linux-xfs For the record I just has linux-2.4.21-rc6-xfs (latest cvs) crash. It was looking over at the linux kernel mailing list and it seem that other folks have been having problem with the 2.4.21-rc? series of kernels hanging on high i/o with high memory usage. ...and that's when I'm crashing also. It does seem like I can make this crash pretty much "at will" at this point. ...start a backup... wait an hour... and BOOM. Since the theory is that the box that is crashing is a production server I'm going to back off to my stable but prone to root exploit 2.4.18-xfs kernel. I'll try to set up a box that is just as crashy but debugabble. Does anyone have a URL or text location to where I can learn to use the kernel debugger or whatever to give good reports after an oops, 'cause I think I may have the ideal circumstance to cause the crashes. Thanks! -- jeffrey hundstad From owner-linux-xfs@oss.sgi.com Sun Jun 1 04:27:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 04:27:48 -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.9) with SMTP id h51BRN2x031994 for ; Sun, 1 Jun 2003 04:27:25 -0700 Received: (qmail 10393 invoked from network); 1 Jun 2003 11:27:22 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 1 Jun 2003 11:27:21 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 9E471D8F46; Sun, 1 Jun 2003 21:27:16 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 9878691336; Sun, 1 Jun 2003 21:27:16 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: "Jeffrey E. Hundstad" Cc: linux-xfs@oss.sgi.com Subject: Re: crash on linux-2.4.21-rc6-xfs (latest cvs) In-reply-to: Your message of "Sun, 01 Jun 2003 05:50:12 EST." <3ED9DA64.8010703@hundstad.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jun 2003 21:27:11 +1000 Message-ID: <3512.1054466831@ocs3.intra.ocs.com.au> X-archive-position: 4191 X-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 On Sun, 01 Jun 2003 05:50:12 -0500, "Jeffrey E. Hundstad" wrote: >For the record I just has linux-2.4.21-rc6-xfs (latest cvs) crash. It >was looking over at the linux kernel mailing list and it seem that other >folks have been having problem with the 2.4.21-rc? series of kernels >hanging on high i/o with high memory usage. ...and that's when I'm >crashing also. It does seem like I can make this crash pretty much "at >will" at this point. ...start a backup... wait an hour... and BOOM. >Since the theory is that the box that is crashing is a production server >I'm going to back off to my stable but prone to root exploit 2.4.18-xfs >kernel. I'll try to set up a box that is just as crashy but >debugabble. Does anyone have a URL or text location to where I can >learn to use the kernel debugger or whatever to give good reports after >an oops, 'cause I think I may have the ideal circumstance to cause the >crashes. Thanks! From your comments, it is unlikely to be an XFS problem. OTOH you have a kernel with the latest kdb, so let's investigate this a bit more. Are you running SMP or UP, if UP does your motherboard have an IO APIC? What sort of error are you seeing, is it a straight hang, does the NMI watchdog kick in, are you running the NMI watchdog? Or do you get an oops? The answer to those questions will guide the debugging effort. In any case, you will need a serial console and a second machine to capture the debug data. Compile with CONFIG_VT=y CONFIG_VT_CONSOLE=y CONFIG_SERIAL=y CONFIG_SERIAL_CONSOLE=y Boot with 'console=tty0 console=ttyS0,38400'. Run a null modem from ttyS0 (COM1) to a second machine and capture the output using your favourite terminal emulator, I use minicom. From owner-linux-xfs@oss.sgi.com Sun Jun 1 12:04:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 12:04:59 -0700 (PDT) Received: from mail.mnsu.edu (Mail.MNSU.EDU [134.29.1.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h51J4e2x010643 for ; Sun, 1 Jun 2003 12:04:41 -0700 Received: from hundstad.net (dyn5390.MavNet.MNSU.EDU [134.29.77.239]) by mail.mnsu.edu (8.12.9/8.12.9) with ESMTP id h51J4VeN013786 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 1 Jun 2003 14:04:31 -0500 Message-ID: <3EDA4E3E.6040800@hundstad.net> Date: Sun, 01 Jun 2003 14:04:30 -0500 From: "Jeffrey E. Hundstad" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Keith Owens CC: linux-xfs@oss.sgi.com Subject: Re: crash on linux-2.4.21-rc6-xfs (latest cvs) References: <3512.1054466831@ocs3.intra.ocs.com.au> In-Reply-To: <3512.1054466831@ocs3.intra.ocs.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4192 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jeffrey@hundstad.net Precedence: bulk X-list: linux-xfs 1. Are you running SMP or UP? SMP 2 if UP does your motherboard have an IO APIC? -NA- 3. What sort of error are you seeing, is it a straight hang, does the NMI watchdog kick in, are you running the NMI watchdog? Huh? I've not seen NMI or watchdog in the kernel messages. 4. Or do you get an oops? I'm getting oopses. Several have been posted. BTW: I don't actually have KDB compiled into the kernel at the moment. I'll do that too ;-) -- Thanks for taking time, Jeffrey Hundstad From owner-linux-xfs@oss.sgi.com Sun Jun 1 15:11:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 15:11:30 -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.9) with SMTP id h51MB82x015243 for ; Sun, 1 Jun 2003 15:11:10 -0700 Received: (qmail 2517 invoked from network); 1 Jun 2003 22:11:03 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 1 Jun 2003 22:11:03 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id B9F88D8F46; Mon, 2 Jun 2003 08:10:55 +1000 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id B6EC291336; Mon, 2 Jun 2003 08:10:55 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: "Jeffrey E. Hundstad" Cc: linux-xfs@oss.sgi.com Subject: Re: crash on linux-2.4.21-rc6-xfs (latest cvs) In-reply-to: Your message of "Sun, 01 Jun 2003 14:04:30 EST." <3EDA4E3E.6040800@hundstad.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Jun 2003 08:10:50 +1000 Message-ID: <8151.1054505450@ocs3.intra.ocs.com.au> X-archive-position: 4193 X-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 On Sun, 01 Jun 2003 14:04:30 -0500, "Jeffrey E. Hundstad" wrote: >3. What sort of error are you seeing, is it a straight hang, does the NMI >watchdog kick in, are you running the NMI watchdog? > >Huh? I've not seen NMI or watchdog in the kernel messages. > >4. Or do you get an oops? > >I'm getting oopses. Several have been posted. That makes it easier. Next time it hangs, enter these kdb commands and capture the output on the serial console. set LINES 10000 set BTAPROMPT 0 -md1c320 system_utsname -id %eip-0x40 -cpu -ps -dmesg 200 -bt -bta Those are my standard set of commands for first line debugging on i386. From owner-linux-xfs@oss.sgi.com Sun Jun 1 19:23:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 19:23:48 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h522NV2x020012 for ; Sun, 1 Jun 2003 19:23:31 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h522dDVe030566 for ; Sun, 1 Jun 2003 21:39:14 -0500 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 h522M7Qd2572875 for ; Mon, 2 Jun 2003 12:22:07 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h522M6jP2709306 for linux-xfs@oss.sgi.com; Mon, 2 Jun 2003 12:22:06 +1000 (EST) Date: Mon, 2 Jun 2003 12:22:06 +1000 (EST) From: Nathan Scott Message-Id: <200306020222.h522M6jP2709306@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - logprint X-archive-position: 4194 X-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 Fix xfs_logprint handling of version 2 logs, sync libxlog with some kernel recovery code fixes (still coming). Date: Sun Jun 1 18:40:16 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:150120a cmd/xfsprogs/logprint/log_print_trans.c - 1.9 cmd/xfsprogs/libxlog/xfs_log_recover.c - 1.24 From owner-linux-xfs@oss.sgi.com Sun Jun 1 20:17:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 20:17:25 -0700 (PDT) Received: from iris.acsalaska.net (iris.slb.nwc.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h523H62x021071 for ; Sun, 1 Jun 2003 20:17:07 -0700 Received: from erbenson.alaska.net (115-pm14.nwc.alaska.net [209.112.141.115]) by iris.acsalaska.net (8.12.9/8.12.9) with ESMTP id h523H5hs091348 for ; Sun, 1 Jun 2003 19:17: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 779603A09 for ; Sun, 1 Jun 2003 19:17:04 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 28ECF40FF44; Sun, 1 Jun 2003 19:17:04 -0800 (AKDT) Date: Sun, 1 Jun 2003 19:17:04 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: libhandle, open_by_handle() Message-ID: <20030602031704.GR32642@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rE45P3aZNSuYx5ND" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4195 X-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 --rE45P3aZNSuYx5ND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I am trying to figure out how libhandle is used and have run into some difficulties. when i use the following code: if (path_to_handle(path, &handle, &hlen) !=3D 0) { perror("path_to_handle"); return 1; } if ((fd =3D open_by_handle(handle, hlen, O_RDWR)) =3D=3D -1) perror("open_by_handle"); open_by_handle returns EBADF, the docs are not clear on whether it wants a handle or a fshandle, so i tried with a fshandle and this time it returns ENOTDIR if i try to open a regular file, and EINVAL if i try to open a directory. am i missing something obvious? or does this simply not work in linux? also when looking at the libhandle source i noticed a few cases where it calls exit(1) rather then return 1; from functions (path_to_handle does this if its internal open() call fails) this is really bad form for a shared library. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --rE45P3aZNSuYx5ND 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 iEYEARECAAYFAj7awa8ACgkQJKx7GixEevy5/QCgnPX5Es+5usINGjn+AIt96Uxx AHgAoI3I6HS2+ah0kVCrVxN5tmy6+gqb =n7tP -----END PGP SIGNATURE----- --rE45P3aZNSuYx5ND-- From owner-linux-xfs@oss.sgi.com Sun Jun 1 20:24:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 20:24:39 -0700 (PDT) Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h523OZ2x021527 for ; Sun, 1 Jun 2003 20:24:35 -0700 Received: from attbi.com (12-253-73-46.client.attbi.com[12.253.73.46]) by attbi.com (rwcrmhc51) with SMTP id <2003060120131105100254d1e>; Sun, 1 Jun 2003 20:13:12 +0000 Message-ID: <3EDA5EEC.50205@attbi.com> Date: Sun, 01 Jun 2003 14:15:40 -0600 From: "D. Stimits" Reply-To: stimits@attbi.com 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: Re: crash on linux-2.4.21-rc6-xfs (latest cvs) References: <3512.1054466831@ocs3.intra.ocs.com.au> <3EDA4E3E.6040800@hundstad.net> In-Reply-To: <3512.1054466831@ocs3.intra.ocs.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4196 X-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@attbi.com Precedence: bulk X-list: linux-xfs Jeffrey E. Hundstad wrote: > 1. Are you running SMP or UP? > > SMP > > 2 if UP does your motherboard have an IO APIC? > > -NA- > > 3. What sort of error are you seeing, is it a straight hang, does the NMI > watchdog kick in, are you running the NMI watchdog? > > Huh? I've not seen NMI or watchdog in the kernel messages. > > 4. Or do you get an oops? > > I'm getting oopses. Several have been posted. > > > BTW: I don't actually have KDB compiled into the kernel at the moment. > I'll do that too ;-) > Try adding kernel parameter "noapic" to the boot. There are a few chipsets that do this due to wrong or inadequate IO-APIC, especially under heavy IO loads. If the problem goes away, chances are it is the chipset support. D. Stimits, stimits AT attbi DOT com From owner-linux-xfs@oss.sgi.com Sun Jun 1 20:45:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 20:45:07 -0700 (PDT) Received: from mail.mnsu.edu (Mail.MNSU.EDU [134.29.1.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h523j02x022007 for ; Sun, 1 Jun 2003 20:45:03 -0700 Received: from mnsu.edu (j3gum-1.MavNet.MNSU.EDU [134.29.64.64]) by mail.mnsu.edu (8.12.9/8.12.9) with ESMTP id h523ineN029408 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 1 Jun 2003 22:44:49 -0500 Message-ID: <3EDAC831.9020908@mnsu.edu> Date: Sun, 01 Jun 2003 22:44:49 -0500 From: "Jeffrey E. Hundstad" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: stimits@attbi.com CC: linux-xfs@oss.sgi.com Subject: Re: crash on linux-2.4.21-rc6-xfs (latest cvs) References: <3512.1054466831@ocs3.intra.ocs.com.au> <3EDA4E3E.6040800@hundstad.net> <3EDA5EEC.50205@attbi.com> In-Reply-To: <3EDA5EEC.50205@attbi.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4197 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jeffrey.hundstad@mnsu.edu Precedence: bulk X-list: linux-xfs I may try this.... but keep in mind it worked for years before the 2.4.21-rcX kernels came out it was on 2.4.18 for a year. D. Stimits wrote: > Jeffrey E. Hundstad wrote: > >> 1. Are you running SMP or UP? >> >> SMP >> >> 2 if UP does your motherboard have an IO APIC? >> >> -NA- >> >> 3. What sort of error are you seeing, is it a straight hang, does the >> NMI >> watchdog kick in, are you running the NMI watchdog? >> >> Huh? I've not seen NMI or watchdog in the kernel messages. >> >> 4. Or do you get an oops? >> >> I'm getting oopses. Several have been posted. >> >> >> BTW: I don't actually have KDB compiled into the kernel at the moment. >> I'll do that too ;-) >> > > Try adding kernel parameter "noapic" to the boot. There are a few > chipsets that do this due to wrong or inadequate IO-APIC, especially > under heavy IO loads. If the problem goes away, chances are it is the > chipset support. > > D. Stimits, stimits AT attbi DOT com > > From owner-linux-xfs@oss.sgi.com Sun Jun 1 21:50:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 21:51:11 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h524ou2x022899 for ; Sun, 1 Jun 2003 21:50:56 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h524ouHb022898 for linux-xfs@oss.sgi.com; Sun, 1 Jun 2003 21:50:56 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h524os31022884 for ; Sun, 1 Jun 2003 21:50:54 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h524IeYL022625; Sun, 1 Jun 2003 21:18:40 -0700 Date: Sun, 1 Jun 2003 21:18:40 -0700 Message-Id: <200306020418.h524IeYL022625@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 248] xfs_check: Segmentation fault X-Bugzilla-Reason: AssignedTo X-archive-position: 4198 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=248 ------- Additional Comments From nathans@sgi.com 2003-01-06 21:18 PDT ------- > I recently had my XFS file system crash on me, and I did a dd of the partition Did you mount the filesystem (and hence recover the log) in between the crash and the dd? thanks. ------- 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 Sun Jun 1 23:14:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Jun 2003 23:15:02 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h526Ef2x025166 for ; Sun, 1 Jun 2003 23:14:44 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h524D6E0014866 for ; Sun, 1 Jun 2003 21:13:07 -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 h524BoQd2786286 for ; Mon, 2 Jun 2003 14:11:50 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h524Bne62768135 for linux-xfs@oss.sgi.com; Mon, 2 Jun 2003 14:11:49 +1000 (EST) Date: Mon, 2 Jun 2003 14:11:49 +1000 (EST) From: Nathan Scott Message-Id: <200306020411.h524Bne62768135@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - libhandle X-archive-position: 4199 X-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 xfsprogs update to tidy up some libhandle code Date: Sun Jun 1 21:11:24 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:150123a cmd/xfsprogs/VERSION - 1.79 cmd/xfsprogs/doc/CHANGES - 1.111 cmd/xfsprogs/debian/changelog - 1.72 cmd/xfsprogs/libhandle/handle.c - 1.15 cmd/xfsprogs/libhandle/Makefile - 1.11 From owner-linux-xfs@oss.sgi.com Mon Jun 2 02:30:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 02:31:01 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h529UO2x007374 for ; Mon, 2 Jun 2003 02:30:28 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h523v6E0013779 for ; Sun, 1 Jun 2003 20:57:06 -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 NAA12764 for ; Mon, 2 Jun 2003 13:55: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 h523tntt086069 for ; Mon, 2 Jun 2003 13:55:49 +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 h523r4vJ003388 for ; Mon, 2 Jun 2003 13:53:04 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h523r4jJ003386 for linux-xfs@oss.sgi.com; Mon, 2 Jun 2003 13:53:04 +1000 Date: Mon, 2 Jun 2003 13:53:04 +1000 From: Nathan Scott To: linux-xfs@oss.sgi.com Subject: Re: libhandle, open_by_handle() Message-ID: <20030602035304.GB2320@frodo> References: <20030602031704.GR32642@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030602031704.GR32642@plato.local.lan> User-Agent: Mutt/1.5.3i X-archive-position: 4200 X-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 On Sun, Jun 01, 2003 at 07:17:04PM -0800, Ethan Benson wrote: > > Hi, > > I am trying to figure out how libhandle is used and have run into some > difficulties. > > am i missing something obvious? or does this simply not work in linux? it should work - xfsdump uses these interfaces extensively. > also when looking at the libhandle source i noticed a few cases where also might help to refer to xfsdump source, and the xfs_ioctl function in the XFS kernel source. off the top of my head, I don't know what the problem might be, nothing obvious. > it calls exit(1) rather then return 1; from functions (path_to_handle > does this if its internal open() call fails) this is really bad form > for a shared library. yup, fixed, thanks. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jun 2 03:07:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 03:08:03 -0700 (PDT) Received: from malik.acsalaska.net (malik.slb.nwc.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h52A7j2x009946 for ; Mon, 2 Jun 2003 03:07:46 -0700 Received: from erbenson.alaska.net (174-pm11.nwc.alaska.net [209.112.140.174]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h52A7i1e076528 for ; Mon, 2 Jun 2003 02:07:44 -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 72DBC3A09 for ; Mon, 2 Jun 2003 02:07:43 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 1521340FF44; Mon, 2 Jun 2003 02:07:43 -0800 (AKDT) Date: Mon, 2 Jun 2003 02:07:42 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: libhandle, open_by_handle() Message-ID: <20030602100742.GS32642@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030602031704.GR32642@plato.local.lan> <20030602035304.GB2320@frodo> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TYoqghpzCwoKvQG2" Content-Disposition: inline In-Reply-To: <20030602035304.GB2320@frodo> 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-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4201 X-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 --TYoqghpzCwoKvQG2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 02, 2003 at 01:53:04PM +1000, Nathan Scott wrote: > On Sun, Jun 01, 2003 at 07:17:04PM -0800, Ethan Benson wrote: > >=20 > > Hi, > >=20 > > I am trying to figure out how libhandle is used and have run into some > > difficulties. > >=20 > > am i missing something obvious? or does this simply not work in linux? >=20 > it should work - xfsdump uses these interfaces extensively. >=20 > > also when looking at the libhandle source i noticed a few cases where >=20 > also might help to refer to xfsdump source, and the xfs_ioctl function > in the XFS kernel source. off the top of my head, I don't know what > the problem might be, nothing obvious. i couldn't make any sense of it, my calls look identical to xfsdumps'=20=20 --=20 Ethan Benson http://www.alaska.net/~erbenson/ --TYoqghpzCwoKvQG2 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 iEYEARECAAYFAj7bIe4ACgkQJKx7GixEevye4wCfbZWy7fkTozSIntIubQcerk7q LUQAmwTfeKSxkjUmt8X8/MjOH0sCd1gE =miLu -----END PGP SIGNATURE----- --TYoqghpzCwoKvQG2-- From owner-linux-xfs@oss.sgi.com Mon Jun 2 08:35:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 08:35:45 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h52FZT2x022657 for ; Mon, 2 Jun 2003 08:35: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.2/linux-outbound_gateway-1.2) with ESMTP id h52FZOE0027804 for ; Mon, 2 Jun 2003 08:35:24 -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 h52FZNQK2743105 for ; Mon, 2 Jun 2003 10:35:24 -0500 (CDT) Received: from penguin.americas.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 h52FZNRn97086350 for ; Mon, 2 Jun 2003 10:35:23 -0500 (CDT) From: Steve Lord Received: by penguin.americas.sgi.com (8.11.6/SGI-client-1.7) id h52FZhU09414; Mon, 2 Jun 2003 10:35:43 -0500 Message-Id: <200306021535.h52FZhU09414@penguin.americas.sgi.com> Date: Mon, 2 Jun 2003 10:35:43 -0500 Subject: TAKE - fix error return sign in mntupdate and statfs To: linux-xfs@oss.sgi.com X-archive-position: 4202 X-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 fix sign of error return in mount update and statfs operations, mount update could have returned either sign, and statfs was just wrong. Date: Mon Jun 2 08:34:46 PDT 2003 Workarea: penguin.americas.sgi.com:/src/lord/xfs-merge.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:150137a linux/fs/xfs/xfs_vfsops.c - 1.420 - update parseargs code to return positive errors to be consistent with other parts of xfs and so the callers can treat it consistently with the other error values they can get. linux/fs/xfs/linux/xfs_super.c - 1.258 - convert sign of error return before returning to linux vfs in mntupdate and statfs call. From owner-linux-xfs@oss.sgi.com Mon Jun 2 11:59:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 12:00:18 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h52Ixu2x027422 for ; Mon, 2 Jun 2003 11:59:57 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h52Ivscs006676 for ; Mon, 2 Jun 2003 13:57:54 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h52Ivsu4006674 for linux-xfs@oss.sgi.com; Mon, 2 Jun 2003 13:57:54 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Kernel dump from 2.4.18-27SGI_XFS1.2.0 From: Austin Gonyou To: XFS List Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1054580273.3848.93.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 02 Jun 2003 13:57:54 -0500 X-archive-position: 4203 X-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 Here is the stack trace from this kernel. This is 2.4.18-27 errata + XFS 1.2.0 release. I did re-work the spec file, but only to disable options we don't want and also re-worked the config to our liking. I have one patch I apply, but it is to scsi_scan.c for a BLIST entry for our hardware. Overall, the core kernel config and source is relatively unchanged. We patch nothing else, and just use RH's src.rpm to create our i686 rpm. Usually, right before the crash, all the fiber channel devices go unaccessible, local are still ok, and whole system is XFS, then the poof. This only seems to occur during the load test I put this thing through. If anyone would like to see it, I'd be happy to provide the info. The ksymoops output is below: ksymoops 2.4.1 on i686 2.4.18-27SGI_XFS_1.2.0_CMsmp. Options used -V (specified) -k /proc/ksyms (specified) -l /proc/modules (specified) -o /lib/modules/2.4.18-27SGI_XFS_1.2.0_CMsmp (specified) -m /boot/System.map-2.4.18-27SGI_XFS_1.2.0_CMsmp (specified) Unable to handle kernel NULL pointer dereference at virtual address 00000034 c0190213 *pde = 19e18001 Oops: 0000 CPU: 2 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 00000000 ebx: 00000001 ecx: c99c9a08 edx: 00000000 esi: 00000000 edi: dab14eec ebp: 00000000 esp: d5d77820 ds: 0018 es: 0018 ss: 0018 Process spew-fork.pl (pid: 28924, stackpage=d5d77000) Stack: dab14eec 00000000 00000000 00000000 dab14f2c 00000000 00000001 f6b7e800 00000000 00000001 00000001 00000003 00000001 00000000 c84a5300 f710bc80 00000001 00000004 c018ca3d dab14eec 00000002 d5d778e8 d5d778e8 f6b7e800 Call Trace: [] (0xd5d77868)) [] (0xd5d778fc)) [] (0xd5d7790c)) [] (0xd5d77938)) [] (0xd5d77940)) [] (0xd5d77974)) [] (0xd5d7797c)) [] (0xd5d77998)) [] (0xd5d77a28)) [] (0xd5d77adc)) [] (0xd5d77b14)) [] (0xd5d77b30)) [] (0xd5d77ba4)) [] (0xd5d77bfc)) [] (0xd5d77c38)) [] (0xd5d77c78)) [] (0xd5d77cb4)) [] (0xd5d77cd4)) [] (0xd5d77d00)) [] (0xd5d77d20)) [] (0xd5d77d40)) [] (0xd5d77d84)) [] (0xd5d77dac)) [] (0xd5d77db8)) [] (0xd5d77dc0)) [] (0xd5d77de4)) [] (0xd5d77df0)) [] (0xd5d77e0c)) [] (0xd5d77e24)) [] (0xd5d77e40)) [] (0xd5d77e9c)) [] (0xd5d77eb8)) [] (0xd5d77ee4)) [] (0xd5d77f28)) [] (0xd5d77f5c)) [] (0xd5d77f74)) [] (0xd5d77f98)) [] (0xd5d77fc0)) Code: 8b 70 34 50 8b 5c 24 24 53 56 57 e8 2d 62 01 00 83 c4 1c 85 >>EIP; c0190213 <===== Trace; c018ca3d Trace; c018c796 Trace; c018ebaa Trace; c019bc64 Trace; c023f340 Trace; c01a514f Trace; c01a514f Trace; c019d7b4 Trace; c019f13d Trace; c01c4b46 Trace; c01d0e00 Trace; c01e4e65 Trace; c01e5bfa Trace; c01e535a Trace; c01dfed7 Trace; c01dfa04 Trace; c01e5444 Trace; c01e48bc Trace; c01df441 Trace; c01e00b5 Trace; c013f6d2 Trace; c0140deb Trace; c0141119 <__block_prepare_write+e9/2f0> Trace; c014113a <__block_prepare_write+10a/2f0> Trace; c0140883 <__refile_buffer+53/60> Trace; c0140799 Trace; c01413d1 <__block_commit_write+b1/e0> Trace; c0141b76 Trace; c01dfdf0 Trace; c012f661 Trace; c0112217 Trace; c01c1f22 Trace; c01e45a4 Trace; c01e06d1 Trace; c013e456 Trace; c0122195 Trace; c01128d9 Trace; c0108c93 Code; c0190213 00000000 <_EIP>: Code; c0190213 <===== 0: 8b 70 34 mov 0x34(%eax),%esi <===== Code; c0190216 3: 50 push %eax Code; c0190217 4: 8b 5c 24 24 mov 0x24(%esp,1),%ebx Code; c019021b 8: 53 push %ebx Code; c019021c 9: 56 push %esi Code; c019021d a: 57 push %edi Code; c019021e b: e8 2d 62 01 00 call 1623d <_EIP+0x1623d> c01a6450 Code; c0190223 10: 83 c4 1c add $0x1c,%esp Code; c0190226 13: 85 00 test %eax,(%eax) -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Mon Jun 2 15:15:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 15:16:12 -0700 (PDT) Received: from hotmail.com (bay2-dav57.bay2.hotmail.com [65.54.246.192]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h52MFU2x003701 for ; Mon, 2 Jun 2003 15:15:50 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 2 Jun 2003 15:15:25 -0700 Received: from 66.26.227.241 by bay2-dav57.bay2.hotmail.com with DAV; Mon, 02 Jun 2003 22:15:24 +0000 X-Originating-IP: [66.26.227.241] X-Originating-Email: [s_wendy_cheng@hotmail.com] From: "Wendy Cheng" To: "xfs mailing list" References: <3512.1054466831@ocs3.intra.ocs.com.au> Subject: xfs performance tuning Date: Mon, 2 Jun 2003 18:15:11 -0400 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 Message-ID: X-OriginalArrivalTime: 02 Jun 2003 22:15:25.0289 (UTC) FILETIME=[775A1590:01C32954] X-archive-position: 4204 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: s_wendy_cheng@hotmail.com Precedence: bulk X-list: linux-xfs We're trying out XFS using SPECsfs benchmark and could only get ~ half of the IOPS when compared with EXT2. It might not be a fair comparison since EXT2 is not a journaling file system but would love to know any tuning parameter to boost the number. Could someone help out ? Thanks... We're on 2.4.20 kernel. Wendy From owner-linux-xfs@oss.sgi.com Mon Jun 2 18:30:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 18:31:03 -0700 (PDT) Received: from hotmail.com (bay2-dav29.bay2.hotmail.com [65.54.246.86]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h531UP2x009358 for ; Mon, 2 Jun 2003 18:30:25 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 2 Jun 2003 18:30:15 -0700 Received: from 66.26.227.241 by bay2-dav29.bay2.hotmail.com with DAV; Tue, 03 Jun 2003 01:30:15 +0000 X-Originating-IP: [66.26.227.241] X-Originating-Email: [s_wendy_cheng@hotmail.com] From: "Wendy Cheng" To: "Nathan Scott" Cc: "xfs mailing list" References: <3512.1054466831@ocs3.intra.ocs.com.au> <20030602230713.GC714@frodo> Subject: Re: xfs performance tuning Date: Mon, 2 Jun 2003 21:29:56 -0400 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 Message-ID: X-OriginalArrivalTime: 03 Jun 2003 01:30:15.0855 (UTC) FILETIME=[AF78E3F0:01C3296F] X-archive-position: 4205 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: s_wendy_cheng@hotmail.com Precedence: bulk X-list: linux-xfs Great thanks ! - but these are kind of obivous. Are there more ? :). Could I turn off / delay kupdated and assume that when incore log buffers are full, it would be automatically flushed into disk without kupdated's help ? We have lots of memory to spare and have turned on highmem IO. Wendy --------- ----- Original Message ----- From: "Nathan Scott" To: "Wendy Cheng" Cc: "xfs mailing list" Sent: Monday, June 02, 2003 7:07 PM Subject: Re: xfs performance tuning | On Mon, Jun 02, 2003 at 06:15:11PM -0400, Wendy Cheng wrote: | > We're trying out XFS using SPECsfs benchmark and | > could only get ~ half of the IOPS when compared | > with EXT2. It might not be a fair comparison since EXT2 | > is not a journaling file system but would love to know | > any tuning parameter to boost the number. Could someone | > help out ? Thanks... | | I would suggest starting with the mkfs options "-l size=XXX" and | "-i size=XXX" (log size and inode size). Increasing the number | of incore log buffers you're using ("-o logbufs=XXX" mount option) | might help you too. | | cheers. | | -- | Nathan | From owner-linux-xfs@oss.sgi.com Mon Jun 2 22:23:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Jun 2003 22:24:15 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h535Nv2x020667 for ; Mon, 2 Jun 2003 22:23:57 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h535NoE0008114 for ; Mon, 2 Jun 2003 22:23:51 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA25312; Tue, 3 Jun 2003 15: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 h535MXtt089892; Tue, 3 Jun 2003 15: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 h535Jk8X001848; Tue, 3 Jun 2003 15:19:46 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h535JkEZ001846; Tue, 3 Jun 2003 15:19:46 +1000 Date: Tue, 3 Jun 2003 15:19:46 +1000 From: Nathan Scott To: Wendy Cheng Cc: xfs mailing list Subject: Re: xfs performance tuning Message-ID: <20030603051946.GA1165@frodo> References: <3512.1054466831@ocs3.intra.ocs.com.au> <20030602230713.GC714@frodo> 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: 4206 X-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 On Mon, Jun 02, 2003 at 09:29:56PM -0400, Wendy Cheng wrote: > Great thanks ! - but these are kind of obivous. Why not post the XFS and ext2 numbers you are seeing currently with your current filesystem geometry (esp. xfs_info output), mount options, and kernel build options, and then any benchmark variations that that the suggested options make, then it might be clearer where to look. There are plenty more knobs to tweak, yes. You should also check that you are not doing any extra checks (e.g. do you have debug or ACLs enabled?) that are not being done in ext2. cheers. > Are there more ? :). Could I turn off / delay > kupdated and assume that when incore log buffers > are full, it would be automatically flushed into > disk without kupdated's help ? We have lots > of memory to spare and have turned on highmem IO. > > Wendy > --------- > ----- Original Message ----- > From: "Nathan Scott" > To: "Wendy Cheng" > Cc: "xfs mailing list" > Sent: Monday, June 02, 2003 7:07 PM > Subject: Re: xfs performance tuning > > > | On Mon, Jun 02, 2003 at 06:15:11PM -0400, Wendy Cheng wrote: > | > We're trying out XFS using SPECsfs benchmark and > | > could only get ~ half of the IOPS when compared > | > with EXT2. It might not be a fair comparison since EXT2 > | > is not a journaling file system but would love to know > | > any tuning parameter to boost the number. Could someone > | > help out ? Thanks... > | > | I would suggest starting with the mkfs options "-l size=XXX" and > | "-i size=XXX" (log size and inode size). Increasing the number > | of incore log buffers you're using ("-o logbufs=XXX" mount option) > | might help you too. > | > | cheers. > | > | -- > | Nathan > | -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jun 3 01:54:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 01:54:37 -0700 (PDT) Received: from mail.arkena.dk (mail.arkena.dk [195.190.149.7]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h538sI2x030461 for ; Tue, 3 Jun 2003 01:54:19 -0700 Received: from thomas.arkena.com (staalanden.arkena.dk [80.62.194.202]) by mail.arkena.dk (Postfix) with ESMTP id E5D0975 for ; Tue, 3 Jun 2003 10:54:16 +0200 (CEST) Received: by thomas.arkena.com (Postfix, from userid 1000) id CD997804; Tue, 3 Jun 2003 10:54:16 +0200 (CEST) Date: Tue, 3 Jun 2003 10:54:16 +0200 From: Thomas Kirk To: xfs mailing list Subject: Re: xfs performance tuning Message-ID: <20030603085416.GA7845@thomas.arkena.com> Mail-Followup-To: xfs mailing list References: <3512.1054466831@ocs3.intra.ocs.com.au> <20030602230713.GC714@frodo> <20030603051946.GA1165@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030603051946.GA1165@frodo> User-Agent: Mutt/1.5.3i X-archive-position: 4207 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: thomas@arkena.dk Precedence: bulk X-list: linux-xfs Hep On Tue, Jun 03, 2003 at 03:19:46PM +1000, Nathan Scott wrote: > There are plenty more knobs to tweak, yes. You should also > check that you are not doing any extra checks (e.g. do you have > debug or ACLs enabled?) that are not being done in ext2. Does ACL decrase XFS performance considerable? -- Venlig hilsen/Kind regards Thomas Kirk ARKENA tlf/phone +4570233456 thomas(at)arkena(dot)com Http://www.arkena.com "It's not easy to juggle a pregnant wife and a troubled child, but somehow I managed to squeeze in 8 hours of TV a day." -- Homer Simpson From owner-linux-xfs@oss.sgi.com Tue Jun 3 02:21:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 02:21:27 -0700 (PDT) Received: from beijing.raidtec.cn ([61.242.91.236]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h539LB2x001534 for ; Tue, 3 Jun 2003 02:21:12 -0700 Received: from juerleechina (unknown [192.168.123.86]) by beijing.raidtec.cn (Postfix) with SMTP id F25364339E for ; Tue, 3 Jun 2003 17:30:13 +0800 (CST) Message-ID: <005001c329b1$75d63a70$567ba8c0@raidtec.china> Reply-To: "Juer Lee" From: "Juer Lee" To: Subject: Quota management Date: Tue, 3 Jun 2003 17:21:05 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 237 X-archive-position: 4208 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: juer.lee@raidtec.ie Precedence: bulk X-list: linux-xfs Hi, XFS guys, Does any body know the quota entry limitation( if there are any) on XFS filesystem? -- I mean how many users or groups of quota can I set on a XFS filesystem. Thanks in advance. Juer [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Tue Jun 3 05:12:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 05:12:56 -0700 (PDT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.22]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53CC92x007808 for ; Tue, 3 Jun 2003 05:12:34 -0700 Received: from [213.221.5.155] (port=35101 helo=someone) by mx2.mail.ru with esmtp id 19NAe3-000POv-00 for linux-xfs@oss.sgi.com; Tue, 03 Jun 2003 16:12:04 +0400 From: =?koi8-r?b?5M3J1NLJyiDzyc7R18nO?= To: linux-xfs@oss.sgi.com Subject: Shrink filesystem... Date: Tue, 3 Jun 2003 16:12:35 +0400 User-Agent: KMail/1.5.2 Organization: Mail.ru MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200306031612.36159.sinyavin@corp.mail.ru> X-archive-position: 4209 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sinyavin@corp.mail.ru Precedence: bulk X-list: linux-xfs Hello! I know the question about how to shrink XFS filesystem has been discussed many times, but once more... Well, I have a 40Gb XFS filesystem. It has grown from 20Gb by editing partition table and running xfs_growfs. No data has been written to filesystem after growth. Ok, now some theory... I need to shrink filesystem by 512Mb, or 64 cylinders. I have internal log that is not crossing the bottom 64cyl boundary, data block, and have no realtime block. When filesystem grown, number of allocation groups has been incremented and more dblocks allocated. So, to shrink filesystem I need to kill some allocation groups and decrease number of dblocks. That was theory. But how to implement this in practice? What I've tred: - I ran sfdisk and decreased size of partition by 64 cylinders. After that filesystem becomes unmountable, mount complains with 'illegal seek'. This looks ok and it is safe to restore old partition size with sfdisk. - Then I tried to run xfs_repair. Hmmm, xfs_repair gone to infinite loop trying to recover superblock in 21th allocation group. This seems to be a bug in xfs_repair... - Ok, ran xfs_admin and looked at agcount and dblocks in superblock 0. Then I decreased agcount by 2 and dblocks by 2 * number of blocks per ag. After that filesystem became unmountable, complaining bad geometry data in superblock. xfs_check gives away with tons of errors... For now I stopped my experiments and restored agcount/dblocks values at superblock, restored partitions size by sfdisk, and filesystem became mountable again. And here is question to XFS hackers: can I? :) As far as I see, no problem in cutting filesystem tail if no data has been written to FS. But how to make it with xfs_admin? Thanks and sorry for my not-so-perfect English. ;) Dmitry. sinyavin@corp.mail.ru From owner-linux-xfs@oss.sgi.com Tue Jun 3 09:05:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 09:05:30 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53G4l2x014338 for ; Tue, 3 Jun 2003 09:05:08 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h53G2h1r003170 for ; Tue, 3 Jun 2003 11:02:43 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h53G2hSB003168 for linux-xfs@oss.sgi.com; Tue, 3 Jun 2003 11:02:43 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Re: Kernel dump from 2.4.18-27SGI_XFS1.2.0 From: Austin Gonyou To: XFS List In-Reply-To: <1054580273.3848.93.camel@portageek.digitalroadkill.net> References: <1054580273.3848.93.camel@portageek.digitalroadkill.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1054656163.3105.36.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 03 Jun 2003 11:02:43 -0500 X-archive-position: 4210 X-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 I hate to be a pain, but does anyone on this list know anything about the below stack trace? On Mon, 2003-06-02 at 13:57, Austin Gonyou wrote: > Here is the stack trace from this kernel. This is 2.4.18-27 errata + > XFS > 1.2.0 release. I did re-work the spec file, but only to disable > options > we don't want and also re-worked the config to our liking. I have one > patch I apply, but it is to scsi_scan.c for a BLIST entry for our > hardware. Overall, the core kernel config and source is relatively > unchanged. We patch nothing else, and just use RH's src.rpm to create > our i686 rpm. Usually, right before the crash, all the fiber channel > devices go unaccessible, local are still ok, and whole system is XFS, > then the poof. This only seems to occur during the load test I put > this > thing through. If anyone would like to see it, I'd be happy to provide > the info. > > > The ksymoops output is below: > > > ksymoops 2.4.1 on i686 2.4.18-27SGI_XFS_1.2.0_CMsmp. Options used > -V (specified) > -k /proc/ksyms (specified) > -l /proc/modules (specified) > -o /lib/modules/2.4.18-27SGI_XFS_1.2.0_CMsmp (specified) > -m /boot/System.map-2.4.18-27SGI_XFS_1.2.0_CMsmp (specified) > > > Unable to handle kernel NULL pointer dereference at virtual address > 00000034 > c0190213 > *pde = 19e18001 > Oops: 0000 > CPU: 2 > EIP: 0010:[] Not tainted > Using defaults from ksymoops -t elf32-i386 -a i386 > EFLAGS: 00010246 > eax: 00000000 ebx: 00000001 ecx: c99c9a08 edx: 00000000 > esi: 00000000 edi: dab14eec ebp: 00000000 esp: d5d77820 > ds: 0018 es: 0018 ss: 0018 > Process spew-fork.pl (pid: 28924, stackpage=d5d77000) > Stack: dab14eec 00000000 00000000 00000000 dab14f2c 00000000 00000001 > f6b7e800 > 00000000 00000001 00000001 00000003 00000001 00000000 c84a5300 > f710bc80 > 00000001 00000004 c018ca3d dab14eec 00000002 d5d778e8 d5d778e8 > f6b7e800 > Call Trace: [] (0xd5d77868)) > [] (0xd5d778fc)) > [] (0xd5d7790c)) > [] (0xd5d77938)) > [] (0xd5d77940)) > [] (0xd5d77974)) > [] (0xd5d7797c)) > [] (0xd5d77998)) > [] (0xd5d77a28)) > [] (0xd5d77adc)) > [] (0xd5d77b14)) > [] (0xd5d77b30)) > [] (0xd5d77ba4)) > [] (0xd5d77bfc)) > [] (0xd5d77c38)) > [] (0xd5d77c78)) > [] (0xd5d77cb4)) > [] (0xd5d77cd4)) > [] (0xd5d77d00)) > [] (0xd5d77d20)) > [] (0xd5d77d40)) > [] (0xd5d77d84)) > [] (0xd5d77dac)) > [] (0xd5d77db8)) > [] (0xd5d77dc0)) > [] (0xd5d77de4)) > [] (0xd5d77df0)) > [] (0xd5d77e0c)) > [] (0xd5d77e24)) > [] (0xd5d77e40)) > [] (0xd5d77e9c)) > [] (0xd5d77eb8)) > [] (0xd5d77ee4)) > [] (0xd5d77f28)) > [] (0xd5d77f5c)) > [] (0xd5d77f74)) > [] (0xd5d77f98)) > [] (0xd5d77fc0)) > Code: 8b 70 34 50 8b 5c 24 24 53 56 57 e8 2d 62 01 00 83 c4 1c 85 > > >>EIP; c0190213 <===== > Trace; c018ca3d > Trace; c018c796 > Trace; c018ebaa > Trace; c019bc64 > Trace; c023f340 > Trace; c01a514f > Trace; c01a514f > Trace; c019d7b4 > Trace; c019f13d > Trace; c01c4b46 > Trace; c01d0e00 > Trace; c01e4e65 > Trace; c01e5bfa > Trace; c01e535a > Trace; c01dfed7 > Trace; c01dfa04 > Trace; c01e5444 > Trace; c01e48bc > Trace; c01df441 > Trace; c01e00b5 > Trace; c013f6d2 > Trace; c0140deb > Trace; c0141119 <__block_prepare_write+e9/2f0> > Trace; c014113a <__block_prepare_write+10a/2f0> > Trace; c0140883 <__refile_buffer+53/60> > Trace; c0140799 > Trace; c01413d1 <__block_commit_write+b1/e0> > Trace; c0141b76 > Trace; c01dfdf0 > Trace; c012f661 > Trace; c0112217 > Trace; c01c1f22 > Trace; c01e45a4 > Trace; c01e06d1 > Trace; c013e456 > Trace; c0122195 > Trace; c01128d9 > Trace; c0108c93 > Code; c0190213 > 00000000 <_EIP>: > Code; c0190213 <===== > 0: 8b 70 34 mov 0x34(%eax),%esi <===== > Code; c0190216 > 3: 50 push %eax > Code; c0190217 > 4: 8b 5c 24 24 mov 0x24(%esp,1),%ebx > Code; c019021b > 8: 53 push %ebx > Code; c019021c > 9: 56 push %esi > Code; c019021d > a: 57 push %edi > Code; c019021e > b: e8 2d 62 01 00 call 1623d <_EIP+0x1623d> c01a6450 > > Code; c0190223 > 10: 83 c4 1c add $0x1c,%esp > Code; c0190226 > 13: 85 00 test %eax,(%eax) > > > > > -- > Austin Gonyou > Coremetrics, Inc. -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Tue Jun 3 09:36:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 09:36:40 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53GZv2x015049 for ; Tue, 3 Jun 2003 09:36:23 -0700 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19NEi8-0003yj-00 for ; Tue, 03 Jun 2003 18:32:32 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: linux-xfs@oss.sgi.com Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19NEhd-0003xB-00 for ; Tue, 03 Jun 2003 18:32:01 +0200 From: Nicholas Wourms Subject: oss.sgi.com xfs-cmds repo is messed up Date: Tue, 03 Jun 2003 12:33:20 -0400 Lines: 8 Message-ID: <3EDCCDD0.9060900@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en X-archive-position: 4211 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nwourms@myrealbox.com Precedence: bulk X-list: linux-xfs Hi, It seems like the scripts have screwed up and replaced everything in xfs-cmds/ with xfs-cmds/linux/. Please fix, thanks in advance! Cheers, Nicholas From owner-linux-xfs@oss.sgi.com Tue Jun 3 10:20:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 10:20:43 -0700 (PDT) Received: from hotmail.com (bay2-dav10.bay2.hotmail.com [65.54.246.114]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53HKQ2x015928 for ; Tue, 3 Jun 2003 10:20:26 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 3 Jun 2003 10:20:20 -0700 Received: from 66.26.227.241 by bay2-dav10.bay2.hotmail.com with DAV; Tue, 03 Jun 2003 17:20:20 +0000 X-Originating-IP: [66.26.227.241] X-Originating-Email: [s_wendy_cheng@hotmail.com] From: "Wendy Cheng" To: "Nathan Scott" Cc: "xfs mailing list" References: <3512.1054466831@ocs3.intra.ocs.com.au> <20030602230713.GC714@frodo> <20030603051946.GA1165@frodo> Subject: Re: xfs performance tuning Date: Tue, 3 Jun 2003 13:19:24 -0400 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 Message-ID: X-OriginalArrivalTime: 03 Jun 2003 17:20:20.0905 (UTC) FILETIME=[69213990:01C329F4] X-archive-position: 4212 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: s_wendy_cheng@hotmail.com Precedence: bulk X-list: linux-xfs Nathan, Thanks - will comply and send out the info. Also we just built a profiling kernel (thanks to SGI again for the kernprof tool). Need to run this first to see what's going on. Wendy -------- ----- Original Message ----- From: "Nathan Scott" To: "Wendy Cheng" Cc: "xfs mailing list" Sent: Tuesday, June 03, 2003 1:19 AM Subject: Re: xfs performance tuning | On Mon, Jun 02, 2003 at 09:29:56PM -0400, Wendy Cheng wrote: | > Great thanks ! - but these are kind of obivous. | | Why not post the XFS and ext2 numbers you are seeing currently | with your current filesystem geometry (esp. xfs_info output), | mount options, and kernel build options, and then any benchmark | variations that that the suggested options make, then it might | be clearer where to look. | | There are plenty more knobs to tweak, yes. You should also | check that you are not doing any extra checks (e.g. do you have | debug or ACLs enabled?) that are not being done in ext2. | | cheers. | | | > Are there more ? :). Could I turn off / delay | > kupdated and assume that when incore log buffers | > are full, it would be automatically flushed into | > disk without kupdated's help ? We have lots | > of memory to spare and have turned on highmem IO. | > | > Wendy | > --------- | > ----- Original Message ----- | > From: "Nathan Scott" | > To: "Wendy Cheng" | > Cc: "xfs mailing list" | > Sent: Monday, June 02, 2003 7:07 PM | > Subject: Re: xfs performance tuning | > | > | > | On Mon, Jun 02, 2003 at 06:15:11PM -0400, Wendy Cheng wrote: | > | > We're trying out XFS using SPECsfs benchmark and | > | > could only get ~ half of the IOPS when compared | > | > with EXT2. It might not be a fair comparison since EXT2 | > | > is not a journaling file system but would love to know | > | > any tuning parameter to boost the number. Could someone | > | > help out ? Thanks... | > | | > | I would suggest starting with the mkfs options "-l size=XXX" and | > | "-i size=XXX" (log size and inode size). Increasing the number | > | of incore log buffers you're using ("-o logbufs=XXX" mount option) | > | might help you too. | > | | > | cheers. | > | | > | -- | > | Nathan | > | | | -- | Nathan | | | From owner-linux-xfs@oss.sgi.com Tue Jun 3 12:47:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 12:47:38 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53Jkx2x020129 for ; Tue, 3 Jun 2003 12:47: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.2/linux-outbound_gateway-1.2) with ESMTP id h53K2mVe002148 for ; Tue, 3 Jun 2003 15:02:49 -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 h53JkqqX2990684; Tue, 3 Jun 2003 14:46:53 -0500 (CDT) Received: from [128.162.232.98] (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h53JkqRn95727670; Tue, 3 Jun 2003 14:46:52 -0500 (CDT) Subject: Re: oss.sgi.com xfs-cmds repo is messed up From: Rusell Cattelan To: Nicholas Wourms Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EDCCDD0.9060900@myrealbox.com> References: <3EDCCDD0.9060900@myrealbox.com> Content-Type: text/plain Organization: Message-Id: <1054669607.54773.8.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 03 Jun 2003 14:46:47 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4213 X-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 On Tue, 2003-06-03 at 11:33, Nicholas Wourms wrote: > Hi, > > It seems like the scripts have screwed up and replaced everything in > xfs-cmds/ with xfs-cmds/linux/. Please fix, thanks in advance! My bad. Fixed -Russell From owner-linux-xfs@oss.sgi.com Tue Jun 3 12:57:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 12:57:51 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53JvQ2x022072 for ; Tue, 3 Jun 2003 12:57:47 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h53JvLE0022298 for ; Tue, 3 Jun 2003 12:57: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 h53JvKqX2994841 for ; Tue, 3 Jun 2003 14:57:20 -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 h53JvKRn95782370 for ; Tue, 3 Jun 2003 14:57:20 -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 h53JvJv9030711 for ; Tue, 3 Jun 2003 14:57:19 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h53JvJWN030709 for linux-xfs@oss.sgi.com; Tue, 3 Jun 2003 14:57:19 -0500 Date: Tue, 3 Jun 2003 14:57:19 -0500 From: Russell Cattelan Message-Id: <200306031957.h53JvJWN030709@chuckle.americas.sgi.com> Subject: TAKE - Update the 1.3 tree to TOT X-archive-position: 4214 X-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 Date: Tue Jun 3 12:56:55 PDT 2003 Workarea: chuckle.americas.sgi.com:/misc/xfs2/XFS/xfs-cmds-r1.3 Merged by: cattelan Merged mods: xfs-cmds:slinx:149987a,xfs-cmds:slinx:149990a,xfs-cmds:slinx:149993a xfs-cmds:slinx:150000a,xfs-cmds:slinx:150001a xfs-cmds:slinx:150061a,xfs-cmds:slinx:150092a xfs-cmds:slinx:150094a,xfs-cmds:slinx:150119a xfs-cmds:slinx:150120a,xfs-cmds:slinx:150121a xfs-cmds:slinx:150123a,xfs-cmds:slinx:150128a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/xfs-cmds-r1.3 Modid: xfs-cmds-r1.3:slinx:150236a acl/VERSION - 1.49 acl/doc/CHANGES - 1.57 acl/debian/control - 1.16 acl/debian/changelog - 1.43 - Merge of xfs-cmds:slinx:149990a originally by nathans on 05/25/03 acl debian packaging updates xfsprogs/VERSION - 1.78 xfsprogs/doc/CHANGES - 1.110 - Merge of xfs-cmds:slinx:150094a originally by nathans on 05/29/03 Update xfsprogs - minor xfs_io update, fix xfs_logprint handling of a corrupt v2 log device should that occur. Merge of xfs-cmds:slinx:150123a originally by nathans on 06/01/03 xfsprogs update to tidy up some libhandle code xfsprogs/logprint/log_print_all.c - 1.9 - Merge of xfs-cmds:slinx:150000a originally by nathans on 05/26/03 Fix missed xlog macro in xfs_logprint after recent changes xfsprogs/logprint/log_print_trans.c - 1.9 - Merge of xfs-cmds:slinx:150120a originally by nathans on 06/01/03 Fix xfs_logprint handling of version 2 logs, sync libxlog with recovery code xfsprogs/libxlog/xfs_log_recover.c - 1.23 - Merge of xfs-cmds:slinx:150094a originally by nathans on 05/29/03 Update xfsprogs - minor xfs_io update, fix xfs_logprint handling of a corrupt v2 log device should that occur. fix xfs_logprint handling of corrupt v2 log devices. Merge of xfs-cmds:slinx:150120a originally by nathans on 06/01/03 Fix xfs_logprint handling of version 2 logs, sync libxlog with recovery code xfsprogs/debian/changelog - 1.71 - Merge of xfs-cmds:slinx:150094a originally by nathans on 05/29/03 Update xfsprogs - minor xfs_io update, fix xfs_logprint handling of a corrupt v2 log device should that occur. Merge of xfs-cmds:slinx:150123a originally by nathans on 06/01/03 xfsprogs update to tidy up some libhandle code xfsprogs/libhandle/handle.c - 1.15 xfsprogs/libhandle/Makefile - 1.11 - Merge of xfs-cmds:slinx:150123a originally by nathans on 06/01/03 xfsprogs update to tidy up some libhandle code xfsdump/VERSION - 1.51 xfsdump/doc/CHANGES - 1.59 xfsdump/debian/changelog - 1.41 xfsdump/invutil/Makefile - 1.9 - Merge of xfs-cmds:slinx:150061a originally by nathans on 05/29/03 Fix Makefile error in xfsinvutil disabling optional ncurses support xfstests/common.rc - 1.22 - Merge of xfs-cmds:slinx:150001a originally by fsgqa on 05/26/03 Fix for external log/rt on the test device for auto-qa Merge of xfs-cmds:slinx:150092a originally by fsgqa on 05/29/03 QA update - do not remount filesystems if corruption detected as this writes to the log Merge of xfs-cmds:slinx:150119a originally by fsgqa on 06/01/03 QA test updates. Fix mounting of test fs/dev so that external log/rt devices can be used. Merge of xfs-cmds:slinx:150121a originally by fsgqa on 06/01/03 Ensure QA tests are run with all the mount options requested xfstests/016 - 1.15 xfstests/018 - 1.18 - Merge of xfs-cmds:slinx:149993a originally by fsgqa on 05/25/03 QA test updates for external log/rt devices. Make sure we don't run this test with mutually exclusive mkfs options. xfstests/031 - 1.10 - Merge of xfs-cmds:slinx:150119a originally by fsgqa on 06/01/03 QA test updates. Fix test so that it works with larger inode sizes also. xfstests/044 - 1.15 xfstests/049 - 1.8 - Merge of xfs-cmds:slinx:149993a originally by fsgqa on 05/25/03 QA test updates for external log/rt devices. Make sure we don't run this test with mutually exclusive mkfs options. xfstests/050 - 1.18 - Merge of xfs-cmds:slinx:149987a originally by fsgqa on 05/25/03 Revert part of last change to QA test 050, add comment instead xfstests/common.config - 1.33 - Merge of xfs-cmds:slinx:149993a originally by fsgqa on 05/25/03 QA test updates for external log/rt devices. Update my local config for bruce to allow external log with TEST filesystem. xfstests/group - 1.28 - Merge of xfs-cmds:slinx:150128a originally by fsgqa on 06/01/03 Remove temporary QA test hack to work around a failing large sector test xfstests/tools/auto-qa - 1.41 - Merge of xfs-cmds:slinx:149993a originally by fsgqa on 05/25/03 QA test updates for external log/rt devices. Allow TEST filesystem to be created with an external log/rt device too. xfsprogs/po/xfsprogs.pot - 1.7 - Merge of xfs-cmds:slinx:150094a originally by nathans on 05/29/03 Update xfsprogs - minor xfs_io update, fix xfs_logprint handling of a corrupt v2 log device should that occur. update with new strings. xfsprogs/io/open.c - 1.5 - Merge of xfs-cmds:slinx:150094a originally by nathans on 05/29/03 Update xfsprogs - minor xfs_io update, fix xfs_logprint handling of a corrupt v2 log device should that occur. Add couple of additional commands. From owner-linux-xfs@oss.sgi.com Tue Jun 3 15:08:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 15:08:24 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53M7k2x027305 for ; Tue, 3 Jun 2003 15:08:07 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h53JvaE0022308 for ; Tue, 3 Jun 2003 12:57:37 -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 h53JvZqX2991587 for ; Tue, 3 Jun 2003 14:57:36 -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 h53JvZRn96620822 for ; Tue, 3 Jun 2003 14:57:35 -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 h53JvZv9030759 for ; Tue, 3 Jun 2003 14:57:35 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h53JvZwh030757 for linux-xfs@oss.sgi.com; Tue, 3 Jun 2003 14:57:35 -0500 Date: Tue, 3 Jun 2003 14:57:35 -0500 From: Russell Cattelan Message-Id: <200306031957.h53JvZwh030757@chuckle.americas.sgi.com> Subject: TAKE - Update the 1.3 tree to TOT X-archive-position: 4215 X-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 Date: Tue Jun 3 12:56:37 PDT 2003 Workarea: chuckle.americas.sgi.com:/go/xfs2/XFS/x2.4-xfs-r1.3 Merged by: cattelan Merged mods: 2.4.x-xfs:slinx:150093a,2.4.x-xfs:slinx:150096a,2.4.x-xfs:slinx:150097a 2.4.x-xfs:slinx:150122a,2.4.x-xfs:slinx:150137a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs-r1.3 Modid: 2.4.x-xfs-r1.3:slinx:150235a linux/mm/memory.c - 1.80 linux/kernel/sched.c - 1.51 - Merge of 2.4.x-xfs:slinx:150097a originally by kaos on 05/29/03 Upgrade 2.4.x-xfs to kdb v4.2 linux/kernel/ksyms.c - 1.145 linux/include/asm-ppc/delay.h - 1.7 linux/include/asm-i386/processor.h - 1.35 linux/fs/block_dev.c - 1.36 linux/drivers/video/controlfb.c - 1.20 linux/drivers/char/tty_io.c - 1.43 linux/drivers/block/ll_rw_blk.c - 1.86 linux/arch/i386/kernel/process.c - 1.42 linux/arch/i386/kernel/ioport.c - 1.5 - Merge of 2.4.x-xfs:slinx:150096a originally by kaos on 05/29/03 Upgrade XFS to 2.4.21-rc6 linux/arch/i386/Makefile - 1.26 - Merge of 2.4.x-xfs:slinx:150097a originally by kaos on 05/29/03 Upgrade 2.4.x-xfs to kdb v4.2 linux/Makefile - 1.188 - Merge of 2.4.x-xfs:slinx:150096a originally by kaos on 05/29/03 Upgrade XFS to 2.4.21-rc6 Merge of 2.4.x-xfs:slinx:150097a originally by kaos on 05/29/03 Upgrade 2.4.x-xfs to kdb v4.2 linux/Documentation/Configure.help - 1.146 - Merge of 2.4.x-xfs:slinx:150096a originally by kaos on 05/29/03 Upgrade XFS to 2.4.21-rc6 linux/include/asm-i386/kmap_types.h - 1.7 - Merge of 2.4.x-xfs:slinx:150097a originally by kaos on 05/29/03 Upgrade 2.4.x-xfs to kdb v4.2 linux/include/linux/pci_ids.h - 1.65 linux/drivers/ide/ide.c - 1.41 linux/drivers/ide/ide-dma.c - 1.16 linux/drivers/ide/Config.in - 1.21 - Merge of 2.4.x-xfs:slinx:150096a originally by kaos on 05/29/03 Upgrade XFS to 2.4.21-rc6 linux/fs/xfs/xfs_log_recover.c - 1.269 - Merge of 2.4.x-xfs:slinx:150093a originally by nathans on 05/29/03 V2 log update - tighten checks for corrupt log during recovery Merge of 2.4.x-xfs:slinx:150122a originally by nathans on 06/01/03 Version 2 log code fixes in recovery. Several recovery fixes, particularly for version 2 logs. Do a better job at sanity checking log headers as we read them in, fix the version check for v2 log records, and if the log head==tail do not do any of the special case v2 log header buffer-resizing code as doing so is invalid. linux/fs/xfs/xfs_vfsops.c - 1.420 - Merge of 2.4.x-xfs:slinx:150137a originally by lord on 06/02/03 fix sign of error return in mount update and statfs operations, mount update could have returned either sign, and statfs was just wrong. update parseargs code to return positive errors to be consistent with other parts of xfs and so the callers can treat it consistently with the other error values they can get. linux/fs/xfs/linux/xfs_super.c - 1.258 - Merge of 2.4.x-xfs:slinx:150137a originally by lord on 06/02/03 fix sign of error return in mount update and statfs operations, mount update could have returned either sign, and statfs was just wrong. convert sign of error return before returning to linux vfs in mntupdate and statfs call. linux/kdb/kdb_bt.c - 1.16 linux/include/linux/kdbprivate.h - 1.25 linux/include/linux/kdb.h - 1.31 linux/kdb/kdbsupport.c - 1.18 linux/kdb/kdbmain.c - 1.38 linux/include/asm-i386/kdb.h - 1.16 linux/kdb/kdb_io.c - 1.19 linux/Documentation/kdb/kdb_bt.man - 1.11 linux/arch/i386/kdb/kdbasupport.c - 1.26 linux/arch/i386/kdb/kdba_io.c - 1.21 linux/arch/i386/kdb/kdba_bt.c - 1.21 linux/kernel/kallsyms.c - 1.15 linux/kdb/modules/kdbm_pg.c - 1.68 linux/kdb/ChangeLog - 1.30 linux/arch/i386/kdb/ChangeLog - 1.19 - Merge of 2.4.x-xfs:slinx:150097a originally by kaos on 05/29/03 Upgrade 2.4.x-xfs to kdb v4.2 linux/arch/x86_64/ia32/ia32_ioctl.c - 1.4 linux/arch/x86_64/ia32/socket32.c - 1.3 linux/arch/x86_64/kernel/entry.S - 1.3 linux/arch/x86_64/kernel/ioport.c - 1.3 linux/arch/x86_64/lib/csum-copy.S - 1.3 linux/include/asm-x86_64/system.h - 1.3 - Merge of 2.4.x-xfs:slinx:150096a originally by kaos on 05/29/03 Upgrade XFS to 2.4.21-rc6 linux/drivers/usb/host/usb-uhci.c - 1.2 - Merge of 2.4.x-xfs:slinx:150097a originally by kaos on 05/29/03 Upgrade 2.4.x-xfs to kdb v4.2 linux/drivers/ide/ppc/pmac.c - 1.2 linux/drivers/ide/pci/via82cxxx.c - 1.2 linux/drivers/ide/pci/siimage.h - 1.2 linux/drivers/ide/pci/siimage.c - 1.3 linux/drivers/char/ipmi/ipmi_watchdog.c - 1.2 linux/drivers/char/ipmi/ipmi_msghandler.c - 1.2 linux/drivers/char/ipmi/ipmi_kcs_sm.c - 1.2 linux/drivers/char/ipmi/ipmi_kcs_intf.c - 1.2 - Merge of 2.4.x-xfs:slinx:150096a originally by kaos on 05/29/03 Upgrade XFS to 2.4.21-rc6 From owner-linux-xfs@oss.sgi.com Tue Jun 3 15:11:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 15:11:04 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53MB02x027777 for ; Tue, 3 Jun 2003 15:11:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h53MAsE0032265 for ; Tue, 3 Jun 2003 15:10:55 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id IAA03182; Wed, 4 Jun 2003 08:09:35 +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 h53M9Xtt091680; Wed, 4 Jun 2003 08:09:33 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h53M9VpM091752; Wed, 4 Jun 2003 08:09:31 +1000 (EST) Date: Wed, 4 Jun 2003 08:09:30 +1000 From: Nathan Scott To: Juer Lee Cc: linux-xfs@oss.sgi.com Subject: Re: Quota management Message-ID: <20030604080930.B91882@wobbly.melbourne.sgi.com> References: <005001c329b1$75d63a70$567ba8c0@raidtec.china> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <005001c329b1$75d63a70$567ba8c0@raidtec.china>; from juer.lee@raidtec.ie on Tue, Jun 03, 2003 at 05:21:05PM +0800 X-archive-position: 4216 X-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 On Tue, Jun 03, 2003 at 05:21:05PM +0800, Juer Lee wrote: > Hi, XFS guys, > > Does any body know the quota entry limitation( if there are any) on XFS filesystem? -- I mean how many users or groups of quota can I set on a XFS filesystem. > XFS uses a 32 bit value for the uid/gid, which matches the size of of the uid/gid values used in the core Linux kernel, so there are no limitations introduced by XFS quota. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jun 3 15:16:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Jun 2003 15:17:02 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h53MGw2x028235 for ; Tue, 3 Jun 2003 15:16: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.2/linux-outbound_gateway-1.2) with SMTP id h53MWlVe013117 for ; Tue, 3 Jun 2003 17:32: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 IAA03255 for ; Wed, 4 Jun 2003 08:15:35 +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 h53MFYtt091439 for ; Wed, 4 Jun 2003 08:15:34 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h53MFXj2088581 for linux-xfs@oss.sgi.com; Wed, 4 Jun 2003 08:15:33 +1000 (EST) Date: Wed, 4 Jun 2003 08:15:33 +1000 From: Nathan Scott To: xfs mailing list Subject: Re: xfs performance tuning Message-ID: <20030604081533.C91882@wobbly.melbourne.sgi.com> References: <3512.1054466831@ocs3.intra.ocs.com.au> <20030602230713.GC714@frodo> <20030603051946.GA1165@frodo> <20030603085416.GA7845@thomas.arkena.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030603085416.GA7845@thomas.arkena.com>; from thomas@arkena.dk on Tue, Jun 03, 2003 at 10:54:16AM +0200 X-archive-position: 4217 X-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 On Tue, Jun 03, 2003 at 10:54:16AM +0200, Thomas Kirk wrote: > Hep > > On Tue, Jun 03, 2003 at 03:19:46PM +1000, Nathan Scott wrote: > > > There are plenty more knobs to tweak, yes. You should also > > check that you are not doing any extra checks (e.g. do you have > > debug or ACLs enabled?) that are not being done in ext2. > > Does ACL decrase XFS performance considerable? > Having ACLs enabled means slightly more work must be done, but not much. Having an ACL set on an inode means still more work must be done, including additional disk IO when the ACL is not being stored directly in the inode, so that can have an impact on benchmarks. Since ext2 wont be doing ACl stuff in the stock 2.4.20 kernels, it makes for a more direct comparison if ACLs are not enabled in XFS too, of course. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Jun 4 05:40:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 05:41:14 -0700 (PDT) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54CeX2x001330 for ; Wed, 4 Jun 2003 05:40:54 -0700 Received: from auto-nb1.xs4all.nl (a80-126-90-136.adsl.xs4all.nl [80.126.90.136]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id h54CeRKa025638; Wed, 4 Jun 2003 14:40:28 +0200 (CEST) Message-Id: <4.3.2.7.2.20030604143455.024e1e88@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 04 Jun 2003 14:39:57 +0200 To: Austin Gonyou , XFS List From: Seth Mos Subject: Re: Kernel dump from 2.4.18-27SGI_XFS1.2.0 In-Reply-To: <1054580273.3848.93.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4218 X-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 At 13:57 2-6-2003 -0500, Austin Gonyou wrote: >Here is the stack trace from this kernel. This is 2.4.18-27 errata + XFS >1.2.0 release. I did re-work the spec file, but only to disable options >we don't want and also re-worked the config to our liking. I have one >patch I apply, but it is to scsi_scan.c for a BLIST entry for our >hardware. Overall, the core kernel config and source is relatively >unchanged. We patch nothing else, and just use RH's src.rpm to create >our i686 rpm. Usually, right before the crash, all the fiber channel >devices go unaccessible, local are still ok, and whole system is XFS, >then the poof. This only seems to occur during the load test I put this >thing through. If anyone would like to see it, I'd be happy to provide >the info. I'm afraid I can't help you with that. I did patch the kernel but I'm not skilled enough to actually be a kernel hacker. :-/ Noon else responded yet, which is a shame. Can you tell me what hardware you are using? It doesn't really sound like a XFS issue is the problem here, my best guess is that something might be causing a reset in the fibre channel array which is causing a driver to stall. I currently have the same problem with megaraid cards without optimizations and the megaraid v2 driver. During high disk IO is stalls so long that the write eventually returns a error and the box hangs. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Wed Jun 4 07:52:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 07:52:46 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54Epx2x005238 for ; Wed, 4 Jun 2003 07:52:19 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h54Enqkn002822; Wed, 4 Jun 2003 09:49:52 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h54Enqvb002818; Wed, 4 Jun 2003 09:49:52 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Re: Kernel dump from 2.4.18-27SGI_XFS1.2.0 From: Austin Gonyou To: Seth Mos Cc: XFS List In-Reply-To: <4.3.2.7.2.20030604143455.024e1e88@pop.xs4all.nl> References: <4.3.2.7.2.20030604143455.024e1e88@pop.xs4all.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1054738191.1927.33.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 04 Jun 2003 09:49:52 -0500 X-archive-position: 4219 X-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 On Wed, 2003-06-04 at 07:39, Seth Mos wrote: > At 13:57 2-6-2003 -0500, Austin Gonyou wrote: > >Here is the stack trace from this kernel. This is 2.4.18-27 errata + > XFS > >1.2.0 release. I did re-work the spec file, but only to disable > options > >we don't want and also re-worked the config to our liking. I have one > >patch I apply, but it is to scsi_scan.c for a BLIST entry for our > >hardware. Overall, the core kernel config and source is relatively > >unchanged. We patch nothing else, and just use RH's src.rpm to create > >our i686 rpm. Usually, right before the crash, all the fiber channel > >devices go unaccessible, local are still ok, and whole system is XFS, > >then the poof. This only seems to occur during the load test I put > this > >thing through. If anyone would like to see it, I'd be happy to > provide > >the info. > > I'm afraid I can't help you with that. I did patch the kernel but I'm > not > skilled enough to actually be a kernel hacker. :-/ Understood. Though you seem to have some pretty good skillz either way. ;) > Noon else responded yet, which is a shame. Yeah, that does suck, but I'm glad you did. I think in time this will get sorted out, but this is one of the best stack traces I've been able to get from any of the crashes I've ever had. :) > Can you tell me what hardware you are using? This is a Dell 6650 4x 1.6Ghz and a single qla2310. (our production configuration is qla2200F's but will eventually get back to 2300 series.) > It doesn't really sound like a > XFS issue is the problem here, my best guess is that something might > be > causing a reset in the fibre channel array which is causing a driver > to stall. I believe it may not be, since I've noticed that only the FC attatched LUNs have the problem, prior to the box hanging. Since I'm load-testing this box right now, it is a short period of time between storage outage, and crash. That was why I was very happy to even get a stack trace at all. > I currently have the same problem with megaraid cards without > optimizations > and the megaraid v2 driver. During high disk IO is stalls so long that > the > write eventually returns a error and the box hangs. IC. I have changed the driver set I'm using from the 6.01-FO drivers, to the 6.04-FO drivers. The box actually seems *much* more responsive but I'm going to watch the swap and see if there's some kind of memory leak issue possibly with the amount of IO I'm doing. (i.e. driver leaking under the load possibly?) Overall, I was just interested to see if anyone on this list can say what they believe the problem might be, given the stack trace and any other information I can offer. I think XFS was noted because the IO was going on, and all the FS are XFS anyway. Just a though. > Cheers > > -- > Seth > It might just be your lucky day, if you only knew. -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Wed Jun 4 11:29:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 11:29:10 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54IT62x032034 for ; Wed, 4 Jun 2003 11:29:07 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h54IT1E0015347 for ; Wed, 4 Jun 2003 11:29:01 -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 h54IT0qX3157856 for ; Wed, 4 Jun 2003 13:29:01 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h54IT0Rn99868594 for ; Wed, 4 Jun 2003 13:29:00 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h54IT0X15545; Wed, 4 Jun 2003 13:29:00 -0500 Message-Id: <200306041829.h54IT0X15545@jen.americas.sgi.com> Date: Wed, 4 Jun 2003 13:29:00 -0500 Subject: TAKE - fix initial directory size after mkdir To: linux-xfs@oss.sgi.com X-archive-position: 4221 X-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 Update linux directory inode contents after the initial mkdir, right now size shows up as zero which is wrong. Not a big thing since the next time the dir was touched, the correct size would show up. Date: Wed Jun 4 11:28:04 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: 2.4.x-xfs:slinx:150334a linux/fs/xfs/linux/xfs_iops.c - 1.192 - update linux inode fields in a directory after it is created. From owner-linux-xfs@oss.sgi.com Wed Jun 4 11:27:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 11:27:42 -0700 (PDT) Received: from smtpzilla5.xs4all.nl (smtpzilla5.xs4all.nl [194.109.127.141]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54IRP2x031868 for ; Wed, 4 Jun 2003 11:27:26 -0700 Received: from auto-nb1.xs4all.nl (a80-126-90-136.adsl.xs4all.nl [80.126.90.136]) by smtpzilla5.xs4all.nl (8.12.9/8.12.9) with ESMTP id h54IRO8l007092 for ; Wed, 4 Jun 2003 20:27:25 +0200 (CEST) Message-Id: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 04 Jun 2003 20:26:21 +0200 To: linux-xfs@oss.sgi.com From: Seth Mos Subject: XFS feature request Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4220 X-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 Hello, Upon a filesystem error the XFS filesystem normally unmounts the fs and often takes the box along with it. What I would like to see is XFS remounting the fs readonly upon error, or at least on the not so severe errors. One of my remote boxen (200Km and a 1:30 drive at 160km/h) played this trick once because a one of the disks from the raid set dissapeared from underneath. The filesystem was intact and did not need to be repaired. The box just needed to be rebooted. On another occasion the root fs of our database server had a duplicate inode error which was triggered by trying to xfsdump the root fs. If the root filesystem was remounted ro instead of unmounted the database server would have survived and we had a chance to stop everything and prevent dataloss since all the databases and log files and such live on another fs. I think this is a good compromise instead of unmounting. It might be wise to make it a mount option if possible to not break existing behaviour. ext2/3 does this same way afaik. cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Wed Jun 4 11:56:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 11:57:06 -0700 (PDT) Received: from mail.modwest.com (marshall.modwest.com [216.129.251.30]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54IuR2x000554 for ; Wed, 4 Jun 2003 11:56:49 -0700 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.modwest.com (Postfix) with ESMTP id D74B440F6CA8 for ; Wed, 4 Jun 2003 12:56:25 -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 02272-09 for ; Wed, 4 Jun 2003 12:56:25 -0000 (MDT) Received: from [10.0.0.135] (unknown [69.24.111.150]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.modwest.com (Postfix) with ESMTP id 7BFE440F5CCB for ; Wed, 4 Jun 2003 12:56:25 -0600 (MDT) Date: Wed, 04 Jun 2003 12:56:45 -0600 From: Michael Loftis To: linux-xfs@oss.sgi.com Subject: Re: XFS feature request Message-ID: <8187140.1054731405@[10.0.0.135]> In-Reply-To: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> References: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> 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: 4222 X-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 This has also recently been a problem for us. The whole 'something looks a little odd so I'm going to just tank and take the whole system with me' knee-jerk reaction XFS has is very problematic. It's the biggest reason I'm moving operations away from it. --On Wednesday, June 04, 2003 20:26 +0200 Seth Mos wrote: > Hello, > > Upon a filesystem error the XFS filesystem normally unmounts the fs and > often takes the box along with it. > ... -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting From owner-linux-xfs@oss.sgi.com Wed Jun 4 13:03:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 13:03:19 -0700 (PDT) Received: from www.linux-works.org ([164.64.40.100]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54K2f2x002257 for ; Wed, 4 Jun 2003 13:03:03 -0700 Received: from linux-works.org (dpc6682204234.direcpc.com [66.82.204.234]) (authenticated bits=0) by www.linux-works.org (8.12.8/8.12.8) with ESMTP id h54K2ID8007207 for ; Wed, 4 Jun 2003 14:02:27 -0600 Message-ID: <3EDE5047.9070308@linux-works.org> Date: Wed, 04 Jun 2003 14:02:15 -0600 From: Andrew Mathews User-Agent: Mozilla/5.0 (X11; U; Linux i686; 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: Re: XFS feature request References: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> <8187140.1054731405@[10.0.0.135]> X-Enigmail-Version: 0.75.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4223 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: andrew_mathews@linux-works.org Precedence: bulk X-list: linux-xfs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Loftis wrote: | This has also recently been a problem for us. The whole 'something | looks a little odd so I'm going to just tank and take the whole system | with me' knee-jerk reaction XFS has is very problematic. It's the | biggest reason I'm moving operations away from it. | | --On Wednesday, June 04, 2003 20:26 +0200 Seth Mos | wrote: | |> Hello, |> |> Upon a filesystem error the XFS filesystem normally unmounts the fs and |> often takes the box along with it. |> ... | | -- | Michael Loftis | Modwest Sr. Systems Administrator | Powerful, Affordable Web Hosting | Not to diminish Set's original request, but to address this comment... I guess your term "knee-jerk reaction" is subjective. I'd much rather have a recoverable system than an unrecoverable one, which is exactly what you'll have if the filesystem is put into an unstable state (corruption) and isn't intelligent enough to protect itself from further damage. It's also one of the reasons we won't use anything other than XFS in a production environment. - -- Andrew Mathews - --------------------------------------------------------------------- ~ 1:56pm up 5 days, 4:49, 12 users, load average: 1.16, 1.13, 1.09 - --------------------------------------------------------------------- A statesman is a politician who's been dead 10 or 15 years. -- Harry S. Truman - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org iD8DBQE+3lBHidHQ0m/kEssRAhouAJwJPdLuIKyUzmxSAj2nySsT2zCGfgCeO4lf 33cLIwDjO7/T/iY8LSDp5qQ= =T97e -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Wed Jun 4 13:34:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 13:34:22 -0700 (PDT) Received: from mail.mnsu.edu (Mail.MNSU.EDU [134.29.1.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h54KXi2x003224 for ; Wed, 4 Jun 2003 13:34:05 -0700 Received: from mnsu.edu (j3gum-3.MNSU.EDU [134.29.1.30]) by mail.mnsu.edu (8.12.9/8.12.9) with ESMTP id h54KXMeN027573 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 4 Jun 2003 15:33:23 -0500 Message-ID: <3EDE5792.3080305@mnsu.edu> Date: Wed, 04 Jun 2003 15:33:22 -0500 From: "Jeffrey E. Hundstad" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Mathews CC: linux-xfs@oss.sgi.com Subject: Re: XFS feature request References: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> <8187140.1054731405@[10.0.0.135]> <3EDE5047.9070308@linux-works.org> In-Reply-To: <3EDE5047.9070308@linux-works.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4224 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jeffrey.hundstad@mnsu.edu Precedence: bulk X-list: linux-xfs It might be nice to have an option on mount to determine what to do in order to please both points of view. I believe ext2 has this. As per mount(8): errors=continue / errors=remount-ro / errors=panic Define the behaviour when an error is encountered. (Either ignore errors and just mark the file system erroneous and continue, or remount the file system read-only, or panic and halt the system.) The default is set in the filesystem superblock, and can be changed using tune2fs(8). Andrew Mathews wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Michael Loftis wrote: > | This has also recently been a problem for us. The whole 'something > | looks a little odd so I'm going to just tank and take the whole system > | with me' knee-jerk reaction XFS has is very problematic. It's the > | biggest reason I'm moving operations away from it. > | > | --On Wednesday, June 04, 2003 20:26 +0200 Seth Mos > | wrote: > | > |> Hello, > |> > |> Upon a filesystem error the XFS filesystem normally unmounts the fs > and > |> often takes the box along with it. > |> ... > | > | -- > | Michael Loftis > | Modwest Sr. Systems Administrator > | Powerful, Affordable Web Hosting > | > > Not to diminish Set's original request, but to address this comment... > > I guess your term "knee-jerk reaction" is subjective. I'd much rather > have a recoverable system than an unrecoverable one, which is exactly > what you'll have if the filesystem is put into an unstable state > (corruption) and isn't intelligent enough to protect itself from further > damage. It's also one of the reasons we won't use anything other than > XFS in a production environment. > > - -- > Andrew Mathews > - --------------------------------------------------------------------- > ~ 1:56pm up 5 days, 4:49, 12 users, load average: 1.16, 1.13, 1.09 > - --------------------------------------------------------------------- > A statesman is a politician who's been dead 10 or 15 years. > -- Harry S. Truman > - -- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org > > iD8DBQE+3lBHidHQ0m/kEssRAhouAJwJPdLuIKyUzmxSAj2nySsT2zCGfgCeO4lf > 33cLIwDjO7/T/iY8LSDp5qQ= > =T97e > -----END PGP SIGNATURE----- > > From owner-linux-xfs@oss.sgi.com Wed Jun 4 20:53:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 20:54:14 -0700 (PDT) Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h553ru2x024845 for ; Wed, 4 Jun 2003 20:53:58 -0700 Received: from whitestar.arts.usyd.edu.au (whitestar.arts.usyd.edu.au [129.78.16.20]) by plato.arts.usyd.edu.au (8.12.9/8.12.6) with ESMTP id h553rtrj022255 for ; Thu, 5 Jun 2003 13:53:55 +1000 (EST) Subject: Re: XFS feature request From: Matthew Geier Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EDE5047.9070308@linux-works.org> References: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> <8187140.1054731405@[10.0.0.135]> <3EDE5047.9070308@linux-works.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 05 Jun 2003 14:07:00 +1000 Message-Id: <1054786020.18819.52.camel@whitestar.arts.usyd.edu.au> Mime-Version: 1.0 X-archive-position: 4225 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: matthew@arts.usyd.edu.au Precedence: bulk X-list: linux-xfs On Thu, 2003-06-05 at 06:02, Andrew Mathews wrote: > Not to diminish Set's original request, but to address this comment... > > I guess your term "knee-jerk reaction" is subjective. I'd much rather > have a recoverable system than an unrecoverable one, which is exactly > what you'll have if the filesystem is put into an unstable state > (corruption) and isn't intelligent enough to protect itself from further > damage. I've had my DEC box, running a now oldish DU 4.0 do that to our main user file system - it found problems and tried to limp along, eventually corrupting the disk to 'mkfs time' to get the system working again. None of the online Dec ADFS tools would touch it. Cuts both ways, yes. So my experience is let it take the system out, letting it limp along will just trash the FS further, which in the long run might cost your MORE downtime. (Quicker to run repair programs than to restore from tape!) From owner-linux-xfs@oss.sgi.com Wed Jun 4 21:49:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Jun 2003 21:49:53 -0700 (PDT) Received: from shell.wgops.com (postfix@dsl092-192-108.sea1.dsl.speakeasy.net [66.92.192.108]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h554nU2x026927 for ; Wed, 4 Jun 2003 21:49:31 -0700 Received: by shell.wgops.com (Postfix, from userid 65534) id 7B956C2; Wed, 4 Jun 2003 22:49:30 -0600 (MDT) Received: from [10.1.2.77] (jobe.wgops.com [10.1.2.77]) by shell.wgops.com (Postfix) with ESMTP id 432F0BB for ; Wed, 4 Jun 2003 22:49:29 -0600 (MDT) Date: Wed, 04 Jun 2003 22:49:28 -0600 From: Michael Loftis To: linux-xfs@oss.sgi.com Subject: Re: XFS feature request Message-ID: <86984947.1054766968@[10.1.2.77]> In-Reply-To: <3EDE5047.9070308@linux-works.org> References: <4.3.2.7.2.20030604201642.033c22e0@pop.xs4all.nl> <8187140.1054731405@[10.0.0.135]> <3EDE5047.9070308@linux-works.org> 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-archive-position: 4226 X-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 Mostly I'd much prefer the option of just going R/O on a filesystem, living with the possibility that what I'm *reading* isn't right than a whole system just going black and having to get onself physically present to ascertain the problem. I don't believe that unmounting the filesystem is *always* the right thing to do. It is in some cases, but there are cases where you'd much rather the system just went read-only and refused to flush anything off to it. --On Wednesday, June 04, 2003 2:02 PM -0600 Andrew Mathews wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Michael Loftis wrote: >| This has also recently been a problem for us. The whole 'something >| looks a little odd so I'm going to just tank and take the whole system >| with me' knee-jerk reaction XFS has is very problematic. It's the >| biggest reason I'm moving operations away from it. >| >| --On Wednesday, June 04, 2003 20:26 +0200 Seth Mos >| wrote: >| >|> Hello, >|> >|> Upon a filesystem error the XFS filesystem normally unmounts the fs and >|> often takes the box along with it. >|> ... >| >| -- >| Michael Loftis >| Modwest Sr. Systems Administrator >| Powerful, Affordable Web Hosting >| > > Not to diminish Set's original request, but to address this comment... > > I guess your term "knee-jerk reaction" is subjective. I'd much rather > have a recoverable system than an unrecoverable one, which is exactly > what you'll have if the filesystem is put into an unstable state > (corruption) and isn't intelligent enough to protect itself from further > damage. It's also one of the reasons we won't use anything other than > XFS in a production environment. > > - -- > Andrew Mathews > - --------------------------------------------------------------------- > ~ 1:56pm up 5 days, 4:49, 12 users, load average: 1.16, 1.13, 1.09 > - --------------------------------------------------------------------- > A statesman is a politician who's been dead 10 or 15 years. > -- Harry S. Truman > - -- > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org > > iD8DBQE+3lBHidHQ0m/kEssRAhouAJwJPdLuIKyUzmxSAj2nySsT2zCGfgCeO4lf > 33cLIwDjO7/T/iY8LSDp5qQ= > =T97e > -----END PGP SIGNATURE----- > > From owner-linux-xfs@oss.sgi.com Thu Jun 5 08:28:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 08:28:34 -0700 (PDT) Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h55FSF2x030148 for ; Thu, 5 Jun 2003 08:28:17 -0700 Received: from chihiro.cern.ch (pcitadc13.cern.ch [137.138.34.18]) by smtp3.cern.ch (8.12.1/8.12.1) with ESMTP id h55FS8Jn005373 for ; Thu, 5 Jun 2003 17:28:08 +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 3A364100087; Thu, 5 Jun 2003 17:28:04 +0200 (CEST) Date: Thu, 5 Jun 2003 17:28:04 +0200 From: KELEMEN Peter To: linux-xfs@oss.sgi.com Subject: kernel BUG at xfs_aops.c:610! Message-ID: <20030605152804.GA2344@chihiro.cern.ch> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline 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 h55FS8Jn005373 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h55FSI2x030149 X-archive-position: 4227 X-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 Hello, Running lilo(8) results in a reproducible oops on a P4 2.4 GHz with XFS root filesystem. Kernel is RedHat 2.4.20-18.7 plus some local patches, compiled with gcc-3.3. Peter kernel BUG at xfs_aops.c:610! invalid operand: 0000 nls_iso8859-1 isofs zlib_inflate sg ipt_LOG ipt_state ip_conntrack ipt_REJECT iptable_filter ip_tables ext3 jbd raid1 md ide-scsi scsi_mod ide-cd cdrom i810_audio ac97_codec soundcore e100 rtc CPU: 0 EIP: 0010:[linvfs_get_block_core+455/480] Not tainted EFLAGS: 00010202 EIP is at pagebuf_offset_R4f61bdbe [] 0x2227 (2.4.20-18.7.cern) eax: 00000000 ebx: 00000000 ecx: 00000001 edx: ffffffff esi: 00000001 edi: c525559c ebp: c8f57ea4 esp: c8f57e34 ds: 0018 es: 0018 ss: 0018 Process lilo.real (pid: 1507, stackpage=c8f57000) Stack: cfda46d8 00000000 00000000 00001000 00000001 00000000 c8f57e78 c8f57e74 00000003 00000097 c8f57e7c 00000006 ffffffff ffffffff 00000000 00000000 00000001 ffffffff ffffffff c1a7ab80 00000000 00000000 00000000 00010000 Call Trace: [linvfs_get_block_direct+54/64] pagebuf_offset_R4f61bdbe [] 0x22f6 (0xc8f57ea8)) [generic_block_bmap+54/64] generic_block_bmap_R6dc95e6f [] 0x36 (0xc8f57ec8)) [fsync_buffers_list+181/384] fsync_buffers_list_Rd2e9eab8 [] 0xb5 (0xc8f57f00)) [xfs_iunlock+98/112] xfs_next_bit_R501ed594 [] 0x29b62 (0xc8f57f14)) [xfs_rwunlock+46/128] xfs_next_bit_R501ed594 [] 0x48a1e (0xc8f57f2c)) [linvfs_bmap+160/176] pagebuf_offset_R4f61bdbe [] 0x24a0 (0xc8f57f40)) [linvfs_get_block_direct+0/64] pagebuf_offset_R4f61bdbe [] 0x22c0 (0xc8f57f4c)) [file_ioctl+183/384] kill_fasync_R7c5fddf5 [] 0xe7 (0xc8f57f70)) [sys_ioctl+200/576] kill_fasync_R7c5fddf5 [] 0x278 (0xc8f57f94)) [system_call+51/56] __up_wakeup [] 0x12af (0xc8f57fc0)) Code: 0f 0b 62 02 8c 17 28 c0 eb d4 eb 0d 90 90 90 90 90 90 90 90 -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen Péter / \ / \ Peter.Kelemen@cern.ch .+' `+...+' `+...+' `+...+' `+...+' From owner-linux-xfs@oss.sgi.com Thu Jun 5 11:06:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 11:07:11 -0700 (PDT) Received: from smtp.covadmail.net ([63.65.120.66]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h55I6l2x002196 for ; Thu, 5 Jun 2003 11:06:52 -0700 Received: (covad.net 30491 invoked from network); 5 Jun 2003 18:06:39 -0000 Received: from unknown (HELO boywonderfx.com) (66.167.1.42) by sun-qmail08 with SMTP; 5 Jun 2003 18:06:39 -0000 Message-ID: <3EDF86B0.3020409@boywonderfx.com> Date: Thu, 05 Jun 2003 11:06:40 -0700 From: Michael Whang User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: grub not working after xfs kernel upgrade Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4228 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mwhang@boywonderfx.com Precedence: bulk X-list: linux-xfs Im dual booting SGI_XFS 2.4.18-18 with windows XP which works fine. Id like to update the kernel to SGI_XFS 2.4.18-27. When i rpm -ivh this kernel, it seems to go smoothly. Grub is also updated. When I reboot the machine upon boot, all I see is "GRUB" in the upper left corner. Ive been told to reinstall the boot loader by runing the command /sbin/grub-install /dev/hda, but this seems to hang as well. Any suggestions? Is there anyone else that has experienced this? Mike From owner-linux-xfs@oss.sgi.com Thu Jun 5 12:34:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 12:34:55 -0700 (PDT) Received: from badboy.mail.pas.earthlink.net (badboy.mail.pas.earthlink.net [207.217.120.20]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h55JYa2x003403 for ; Thu, 5 Jun 2003 12:34:38 -0700 Received: from albatross.mail.pas.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by badboy.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id h55IxXK20865 for ; Thu, 5 Jun 2003 11:59:34 -0700 (PDT) Received: from [65.102.60.133] (helo=software1.logiplex.internal) by albatross.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19Nzpb-000073-00; Thu, 05 Jun 2003 11:51:23 -0700 Subject: Re: grub not working after xfs kernel upgrade From: Cliff Wells To: Michael Whang Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EDF86B0.3020409@boywonderfx.com> References: <3EDF86B0.3020409@boywonderfx.com> Content-Type: text/plain Organization: Logiplex Corporation Message-Id: <1054839082.2139.33.camel@software1.logiplex.internal> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.92 (Preview Release) Date: 05 Jun 2003 11:51:22 -0700 Content-Transfer-Encoding: 7bit X-archive-position: 4229 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: LogiplexSoftware@earthlink.net Precedence: bulk X-list: linux-xfs On Thu, 2003-06-05 at 11:06, Michael Whang wrote: > Im dual booting SGI_XFS 2.4.18-18 with windows XP which works fine. Id > like to update the kernel to SGI_XFS 2.4.18-27. When i rpm -ivh this > kernel, it seems to go smoothly. Grub is also updated. When I reboot > the machine upon boot, all I see is "GRUB" in the upper left corner. > Ive been told to reinstall the boot loader by runing the command > /sbin/grub-install /dev/hda, but this seems to hang as well. Any > suggestions? Is there anyone else that has experienced this? Boot from a rescue disk and run the following: # grub grub> root (hd0,0) grub> setup (hd0) grub> quit This assumes /boot resides on hda1. If it doesn't, change the (hd0,0) parameter accordingly (hd0 being hda, hd0,0 being hda1). -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 (800) 735-0555 From owner-linux-xfs@oss.sgi.com Thu Jun 5 16:56:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 16:56:24 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h55Nu92x018089 for ; Thu, 5 Jun 2003 16:56:09 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h55Nu1E0018693 for ; Thu, 5 Jun 2003 16:56:03 -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 JAA00309 for ; Fri, 6 Jun 2003 09:54:46 +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 h55Nsjtt099572 for ; Fri, 6 Jun 2003 09:54:45 +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 h55Nsf97000992 for ; Fri, 6 Jun 2003 09:54:41 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h55NsfjZ000990 for linux-xfs@oss.sgi.com; Fri, 6 Jun 2003 09:54:41 +1000 Date: Fri, 6 Jun 2003 09:54:41 +1000 From: Nathan Scott To: linux-xfs@oss.sgi.com Subject: Re: kernel BUG at xfs_aops.c:610! Message-ID: <20030605235441.GB764@frodo> References: <20030605152804.GA2344@chihiro.cern.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030605152804.GA2344@chihiro.cern.ch> User-Agent: Mutt/1.5.3i Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h55Nu92x018090 X-archive-position: 4230 X-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 On Thu, Jun 05, 2003 at 05:28:04PM +0200, KELEMEN Peter wrote: > Hello, > > Running lilo(8) results in a reproducible oops on a P4 2.4 GHz > with XFS root filesystem. Kernel is RedHat 2.4.20-18.7 plus some > local patches, compiled with gcc-3.3. > > Peter > > kernel BUG at xfs_aops.c:610! Can you give some context around line 610 in fs/xfs/linux/xfs_aops.c from your XFS source, Peter? (there is no BUG() call there anymore). I think I know what this is (I have seen something like this, if I'm second guessing where this is in the code correctly, under very high stress), but we don't have a fix for it yet. Are you saying above that you have an easy case for reproducing it? That would be handy. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jun 5 18:21:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 18:22:11 -0700 (PDT) Received: from hotmail.com (bay1-f9.bay1.hotmail.com [65.54.245.9]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h561Lw2x002672 for ; Thu, 5 Jun 2003 18:21:58 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 5 Jun 2003 18:21:53 -0700 Received: from 66.167.1.42 by by1fd.bay1.hotmail.msn.com with HTTP; Fri, 06 Jun 2003 01:21:52 GMT X-Originating-IP: [66.167.1.42] X-Originating-Email: [mwhang77@hotmail.com] From: "Michael Whang" To: linux-xfs@oss.sgi.com Subject: redhat, windows and MBR Date: Thu, 05 Jun 2003 18:21:52 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 06 Jun 2003 01:21:53.0072 (UTC) FILETIME=[03078B00:01C32BCA] X-archive-position: 4231 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mwhang77@hotmail.com Precedence: bulk X-list: linux-xfs can anyone tell me exactly what happens with the MBR as you install redhat with XFS and windows XP? Where are the kernel images...where is /boot? Im trying to dual boot xfs and xp. I installed XFS and it was booting fine. Then I installed XP, after which the boot loader screen did not come up anymore. So i booted off of floppy to change the active partition back to the /boot partition, but now all i get is "error loading operating system." Any help would be appreciated. Mike _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From owner-linux-xfs@oss.sgi.com Thu Jun 5 21:58:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 21:59:11 -0700 (PDT) Received: from jaded.anu.edu.au (neocom@dsl-202-45-99-76.ACT.netspace.net.au [202.45.99.76]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h564wo2x026224 for ; Thu, 5 Jun 2003 21:58:51 -0700 Received: by jaded.anu.edu.au (Postfix, from userid 1000) id D7E9B50245C9; Fri, 6 Jun 2003 14:58:26 +1000 (EST) Date: Fri, 6 Jun 2003 14:58:26 +1000 From: Patrick Cole To: linux-xfs@oss.sgi.com Subject: XFS Raid5 in Raid0 poor performance Message-ID: <20030606045826.GA3070@jaded.neocom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-archive-position: 4232 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: z@amused.net Precedence: bulk X-list: linux-xfs The problem: I have a file server which backs up to tape nightly (which is not of great importance). It was initially running Ext3 and could write to tape at mostly native speed (~15MB/s). I decided I wanted to change it over to XFS to get online defragmenting and better performance but the latter has not been the case: Version 1.02c ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP icufs2 4G 11105 98 24850 15 15788 12 10841 98 49210 32 581.4 6 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 431 15 +++++ +++ 452 12 518 15 +++++ +++ 230 6 icufs2,4G,11105,98,24850,15,15788,12,10841,98,49210,32,581.4,6,16,431,15,+++++,+++,452,12,518,15,+++++,+++,230,6 These are the results of a bonnie test on the machine, and show the pooer performance the filesystem is giving in this application. The reason for this we suspect is because of the raid setup we are running. Here is how it is setup: Two controllers (3ware Escalade) 8way each Raid0 (256KB chunk size) { Raid5 (32KB chunk size) { Drive 1 Drive 2 Drive 3 Drive 4 Drive 5 Drive 6 Drive 7 (Parity) Drive 8 (Hot spare) } Raid5 (32KB chunk size) { Drive 1 Drive 2 Drive 3 Drive 4 Drive 5 Drive 6 Drive 7 (Parity) Drive 8 (Hot spare) } } So it's something like raid0(raid5(1-8),raid5(1-8)) each drive being about 120GB giving a total of around 1.3 TB. Here are the bonnie results from an IDENTICAL machine running Ext3: Version 1.03 ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP cbisfs2 4G 12224 99 86949 72 46664 54 13741 99 87315 61 582.4 4 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 1390 95 +++++ +++ +++++ +++ 1452 99 +++++ +++ 2981 98 cbisfs2,4G,12224,99,86949,72,46664,54,13741,99,87315,61,582.4,4,16,1390,95,+++++,+++,+++++,+++,1452,99,+++++,+++,2981,98 This is more the kind of performance you would expect out of this kind of setup. As you can see the block sequential output is almost four times better on Ext3 with this setup, while the block sequential input is almost twice as good. The other thing worth noting is that the create and delete performance is reduced to next to nothing! I get 3 x better create performance with XFS on my single drive ATA100 workstation, with slower CPUs. Some input/ideas/fixes would be appreciated. Btw, the filesystem was created using xfsprogs 2.0.6. After talking with sandeen he suggested that the newer utils had some changes relating to setting to the sunit and stripe perameters of the filesystem. Is this the case? Cheers Patrick -- Patrick Cole Programmer, the John Curtin School of Medical Research, ANU Office 02 6125 6794 Mobile 0438 763337 PGP 1024R/60D74C7D C8E0BC7969BE7899AA0FEB16F84BFE5A From owner-linux-xfs@oss.sgi.com Thu Jun 5 23:06:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Jun 2003 23:07:14 -0700 (PDT) Received: from jaded.anu.edu.au (neocom@dsl-202-45-99-76.ACT.netspace.net.au [202.45.99.76]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5666t2x028941 for ; Thu, 5 Jun 2003 23:06:57 -0700 Received: by jaded.anu.edu.au (Postfix, from userid 1000) id 11D8650245C9; Fri, 6 Jun 2003 16:06:29 +1000 (EST) Date: Fri, 6 Jun 2003 16:06:29 +1000 From: Patrick Cole To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Raid5 in Raid0 poor performance Message-ID: <20030606060629.GA3560@jaded.neocom> References: <20030606045826.GA3070@jaded.neocom> <20030606054045.GC1239@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030606054045.GC1239@frodo> User-Agent: Mutt/1.4i X-archive-position: 4233 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: z@amused.net Precedence: bulk X-list: linux-xfs Fri, Jun 06, 2003 at 03:40:45PM +1000, Nathan Scott wrote: > > Some input/ideas/fixes would be appreciated. > > Oh - I wonder if the layering of RAID like this is causing the > mkfs code to get confused. (is Martin lurking on the list?) > > I'd suggest trying a mkfs on one of the RAID5 devices, then pass > those sunit and swidth values into mkfs rather than using the > ones which it figures out on the fly from your RAID0 device, and > see if that helps at all. That wouldn't be advisable as the inner chunk size is only 32KB. To get maximal performance from the raid it would need to write/read 2 x 256KB (512KB) to the outer raid for each I/O op. It would be nice if the number of data disks in each raid5 was a power of two, but it works out a write of 192KB would cover all 6 disks. 256KB or 128KB is the closest approximation. > > Btw, the filesystem was created using xfsprogs 2.0.6. After talking with sandeen > > he suggested that the newer utils had some changes relating to setting to the sunit > > and stripe perameters of the filesystem. Is this the case? > > There were changes recently in the MD stripe detection code, just > to change it so that it wouldn't quit out of mkfs in certain cases > and instead warn and carry on - so that wouldn't affect you here. > It's a good idea to get the latest tools though - you might find > version 2 logs to be of some help here too, and there was a recent > mkfs fix for those recently. Check out: meta-data=/ isize=256 agcount=336, agsize=1048544 blks = sectsz=512 data = bsize=4096 blocks=351630368, imaxpct=25 = sunit=32 swidth=64 blks, unwritten=1 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=32768, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=262144 blocks=0, rtextents=0 What exactly is sunit? Is it meant to be the stripe chunk size for the given device? If it is, then it should be 256, not 32. That could be the reason for the shoddy performance? Cheers Patrick -- Patrick Cole Programmer, the John Curtin School of Medical Research, ANU Office 02 6125 6794 Mobile 0438 763337 PGP 1024R/60D74C7D C8E0BC7969BE7899AA0FEB16F84BFE5A From owner-linux-xfs@oss.sgi.com Fri Jun 6 00:29:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 00:31:42 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h567Tu2x030585 for ; Fri, 6 Jun 2003 00:29:57 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h565gJE0031624 for ; Thu, 5 Jun 2003 22:42:21 -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 PAA03729; Fri, 6 Jun 2003 15:41: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 h565f0tt100478; Fri, 6 Jun 2003 15:41:01 +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 h565et97001879; Fri, 6 Jun 2003 15:40:55 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h565ejp0001877; Fri, 6 Jun 2003 15:40:45 +1000 Date: Fri, 6 Jun 2003 15:40:45 +1000 From: Nathan Scott To: Patrick Cole Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Raid5 in Raid0 poor performance Message-ID: <20030606054045.GC1239@frodo> References: <20030606045826.GA3070@jaded.neocom> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030606045826.GA3070@jaded.neocom> User-Agent: Mutt/1.5.3i X-archive-position: 4234 X-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 Hi, On Fri, Jun 06, 2003 at 02:58:26PM +1000, Patrick Cole wrote: > ... > > Two controllers (3ware Escalade) 8way each > > Raid0 (256KB chunk size) { > Raid5 (32KB chunk size) { > Drive 1 > Drive 2 > Drive 3 > Drive 4 > Drive 5 > Drive 6 > Drive 7 (Parity) > Drive 8 (Hot spare) > } > Raid5 (32KB chunk size) { > Drive 1 > Drive 2 > Drive 3 > Drive 4 > Drive 5 > Drive 6 > Drive 7 (Parity) > Drive 8 (Hot spare) > } > } > > Some input/ideas/fixes would be appreciated. Oh - I wonder if the layering of RAID like this is causing the mkfs code to get confused. (is Martin lurking on the list?) I'd suggest trying a mkfs on one of the RAID5 devices, then pass those sunit and swidth values into mkfs rather than using the ones which it figures out on the fly from your RAID0 device, and see if that helps at all. > Btw, the filesystem was created using xfsprogs 2.0.6. After talking with sandeen > he suggested that the newer utils had some changes relating to setting to the sunit > and stripe perameters of the filesystem. Is this the case? There were changes recently in the MD stripe detection code, just to change it so that it wouldn't quit out of mkfs in certain cases and instead warn and carry on - so that wouldn't affect you here. It's a good idea to get the latest tools though - you might find version 2 logs to be of some help here too, and there was a recent mkfs fix for those recently. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Jun 6 03:15:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 03:16:05 -0700 (PDT) Received: from flood.physik.tu-cottbus.de (flood.physik.TU-Cottbus.De [141.43.75.21]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56AFZ2x005915 for ; Fri, 6 Jun 2003 03:15:36 -0700 Received: from emmy.physik.tu-cottbus.de (emmy.physik.tu-cottbus.de [141.43.75.40]) by flood.physik.tu-cottbus.de (Postfix) with ESMTP id 2B426701E05 for ; Fri, 6 Jun 2003 11:46:04 +0200 (CEST) Received: by emmy.physik.tu-cottbus.de (Postfix, from userid 7224) id DA812181D48; Fri, 6 Jun 2003 11:46:03 +0200 (CEST) Date: Fri, 6 Jun 2003 11:46:03 +0200 From: Ionut Georgescu To: linux-xfs@oss.sgi.com Subject: Re: redhat, windows and MBR Message-ID: <20030606094603.GA1338@physik.tu-cottbus.de> 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: User-Agent: Mutt/1.5.3i X-archive-position: 4235 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: george@physik.tu-cottbus.de Precedence: bulk X-list: linux-xfs WinXP overwrites the MBR and will always change the active partition to the WinXP partition when it boots. What I did was to install grub in the MBR (has been posted on the list). Windows will then leave the MBR intact. Ionut On Thu, Jun 05, 2003 at 06:21:52PM -0700, Michael Whang wrote: > can anyone tell me exactly what happens with the MBR as you install redhat > with XFS and windows XP? Where are the kernel images...where is /boot? Im > trying to dual boot xfs and xp. I installed XFS and it was booting fine. > Then I installed XP, after which the boot loader screen did not come up > anymore. So i booted off of floppy to change the active partition back to > the /boot partition, but now all i get is "error loading operating system." > Any help would be appreciated. > > > Mike > > _________________________________________________________________ > The new MSN 8: advanced junk mail protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail > > -- *************** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you * can do anything the computer is able to do." From owner-linux-xfs@oss.sgi.com Fri Jun 6 03:19:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 03:19:22 -0700 (PDT) Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56AJE2x006381 for ; Fri, 6 Jun 2003 03:19:15 -0700 Received: from chihiro.cern.ch (pcitadc13.cern.ch [137.138.34.18]) by smtp3.cern.ch (8.12.1/8.12.1) with ESMTP id h56AJ7WU000936 for ; Fri, 6 Jun 2003 12:19:07 +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 F15802050CD; Fri, 6 Jun 2003 12:19:07 +0200 (CEST) Date: Fri, 6 Jun 2003 12:19:07 +0200 From: KELEMEN Peter To: linux-xfs@oss.sgi.com Subject: Re: kernel BUG at xfs_aops.c:610! Message-ID: <20030606101907.GA12434@chihiro.cern.ch> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030605152804.GA2344@chihiro.cern.ch> <20030605235441.GB764@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20030605235441.GB764@frodo> 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 h56AJ7WU000936 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h56AJG2x006385 X-archive-position: 4236 X-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 * Nathan Scott (nathans@sgi.com) [20030606 09:54]: Nathan, > Can you give some context around line 610 in fs/xfs/linux/xfs_aops.c > from your XFS source, Peter? (there is no BUG() call there anymore). Sure, here it is: 602 if (create && 603 ((!buffer_mapped(bh_result) && !buffer_uptodate(bh_result)) || 604 (offset >= inode->i_size))) { 605 set_bit(BH_New, &bh_result->b_state); 606 } 607 608 if (pbmap.pbm_flags & PBMF_DELAY) { 609 if (unlikely(direct)) 610 BUG(); 611 612 if (create) { 613 set_bit(BH_Mapped, &bh_result->b_state); 614 } 615 set_bit(BH_Delay, &bh_result->b_state); 616 } fs/xfs/linux/xfs_version.h says it is: #define XFS_VERSION_STRING "1.2.0" > I think I know what this is (I have seen something like this, if I'm > second guessing where this is in the code correctly, under very high > stress), but we don't have a fix for it yet. Are you saying above > that you have an easy case for reproducing it? That would be handy. Yes, I have reproduced the exact same oops several times, unfortunately it damaged my root XFS filesystem beyond repair. I'm currently building it again and see if I can get the oops back. Peter -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen Péter / \ / \ Peter.Kelemen@cern.ch .+' `+...+' `+...+' `+...+' `+...+' From owner-linux-xfs@oss.sgi.com Fri Jun 6 04:01:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 04:01:19 -0700 (PDT) Received: from goliath.sylaba.poznan.pl (root@goliath.sylaba.poznan.pl [195.216.104.3]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56B1E2x007619 for ; Fri, 6 Jun 2003 04:01:15 -0700 Received: from goliath.sylaba.poznan.pl (smmsp@localhost.sylaba.poznan.pl [127.0.0.1]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h56B1Cb5006066 for ; Fri, 6 Jun 2003 13:01:12 +0200 (CEST) Received: by goliath.sylaba.poznan.pl (8.12.8/8.12.8/Submit) id h56B1BKu006065 for linux-xfs@oss.sgi.com.KAV; Fri, 6 Jun 2003 13:01:11 +0200 (CEST) Received: from venus.local.navi.pl (ps103.poznan.sdi.tpnet.pl [217.97.72.103]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h56B1Ab5006042; Fri, 6 Jun 2003 13:01:11 +0200 (CEST) Received: from venus.local.navi.pl (venus.local.navi.pl [127.0.0.1]) by venus.local.navi.pl (8.12.5/8.12.5) with ESMTP id h56B3G4O003407; Fri, 6 Jun 2003 13:03:17 +0200 Subject: Re: redhat, windows and MBR From: Olaf =?iso-8859-2?Q?Fr=B1czyk?= To: Ionut Georgescu Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030606094603.GA1338@physik.tu-cottbus.de> References: <20030606094603.GA1338@physik.tu-cottbus.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 06 Jun 2003 13:03:16 +0200 Message-Id: <1054897397.2474.5.camel@venus> Mime-Version: 1.0 X-archive-position: 4237 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: olaf@cbk.poznan.pl Precedence: bulk X-list: linux-xfs On Fri, 2003-06-06 at 11:46, Ionut Georgescu wrote: > WinXP overwrites the MBR and will always change the active partition to > the WinXP partition when it boots. What I did was to install grub in the > MBR (has been posted on the list). Windows will then leave the MBR > intact. Will it work with lilo also? Do you know what WinXP checks to not overwrite MBR? Regards, Olaf From owner-linux-xfs@oss.sgi.com Fri Jun 6 04:39:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 04:39:26 -0700 (PDT) Received: from flood.physik.tu-cottbus.de (flood.physik.TU-Cottbus.De [141.43.75.21]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56Bct2x009229 for ; Fri, 6 Jun 2003 04:38:56 -0700 Received: from emmy.physik.tu-cottbus.de (emmy.physik.tu-cottbus.de [141.43.75.40]) by flood.physik.tu-cottbus.de (Postfix) with ESMTP id 1BD44701E04 for ; Fri, 6 Jun 2003 13:11:03 +0200 (CEST) Received: by emmy.physik.tu-cottbus.de (Postfix, from userid 7224) id D4283181D48; Fri, 6 Jun 2003 13:11:02 +0200 (CEST) Date: Fri, 6 Jun 2003 13:11:02 +0200 From: Ionut Georgescu To: linux-xfs@oss.sgi.com Subject: Re: redhat, windows and MBR Message-ID: <20030606111102.GB1338@physik.tu-cottbus.de> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20030606094603.GA1338@physik.tu-cottbus.de> <1054897397.2474.5.camel@venus> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1054897397.2474.5.camel@venus> User-Agent: Mutt/1.5.3i X-archive-position: 4238 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: george@physik.tu-cottbus.de Precedence: bulk X-list: linux-xfs I think WinXP alone won't touch any MBR it doesn't understand. Only the installer overwrites everything. Ionut On Fri, Jun 06, 2003 at 01:03:16PM +0200, Olaf Fr?czyk wrote: > On Fri, 2003-06-06 at 11:46, Ionut Georgescu wrote: > > WinXP overwrites the MBR and will always change the active partition to > > the WinXP partition when it boots. What I did was to install grub in the > > MBR (has been posted on the list). Windows will then leave the MBR > > intact. > Will it work with lilo also? > Do you know what WinXP checks to not overwrite MBR? > > Regards, > > Olaf > > > > > -- *************** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you * can do anything the computer is able to do." From owner-linux-xfs@oss.sgi.com Fri Jun 6 06:29:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 06:31:00 -0700 (PDT) Received: from goliath.sylaba.poznan.pl (root@goliath.sylaba.poznan.pl [195.216.104.3]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56DTr2x011289 for ; Fri, 6 Jun 2003 06:29:57 -0700 Received: from goliath.sylaba.poznan.pl (smmsp@localhost.sylaba.poznan.pl [127.0.0.1]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h56DTpAn001172 for ; Fri, 6 Jun 2003 15:29:51 +0200 (CEST) Received: by goliath.sylaba.poznan.pl (8.12.8/8.12.8/Submit) id h56DTocI001165 for linux-xfs@oss.sgi.com.KAV; Fri, 6 Jun 2003 15:29:50 +0200 (CEST) Received: from venus.local.navi.pl (ps103.poznan.sdi.tpnet.pl [217.97.72.103]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h56DTlAn001070 for ; Fri, 6 Jun 2003 15:29:49 +0200 (CEST) Received: from venus.local.navi.pl (venus.local.navi.pl [127.0.0.1]) by venus.local.navi.pl (8.12.5/8.12.5) with ESMTP id h56DVr4O003982 for ; Fri, 6 Jun 2003 15:31:53 +0200 Subject: How to monitor access/modification of files on XFS? From: Olaf =?iso-8859-2?Q?Fr=B1czyk?= To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 06 Jun 2003 15:31:53 +0200 Message-Id: <1054906313.2474.14.camel@venus> Mime-Version: 1.0 X-archive-position: 4239 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: olaf@cbk.poznan.pl Precedence: bulk X-list: linux-xfs Hi, I need to monitor access to XFS filesystem: file and directory: creation/modification/delete/rename/rights change with user names and time stamp. Is such possibility in kernel/XFS fs code (for 2.4 kernels)? Regards, Olaf Fraczyk From owner-linux-xfs@oss.sgi.com Fri Jun 6 07:45:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 07:46:12 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56Ejq2x013876 for ; Fri, 6 Jun 2003 07:45:55 -0700 Received: from pinckneya.peachtree.sgi.com (pinckneya.peachtree.sgi.com [169.238.221.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h56EjkE0005910 for ; Fri, 6 Jun 2003 07:45:47 -0700 Received: from pengo.peachtree.sgi.com by pinckneya.peachtree.sgi.com via ESMTP (950413.SGI.8.6.12/930416.SGI) id KAA00684; Fri, 6 Jun 2003 10:43:48 -0400 Date: Fri, 6 Jun 2003 10:43:48 -0400 From: Jon Morgan X-X-Sender: jmorgan@pengo.peachtree.sgi.com To: Olaf =?iso-8859-2?Q?Fr=B1czyk?= cc: linux-xfs@oss.sgi.com Subject: Re: How to monitor access/modification of files on XFS? In-Reply-To: <1054906313.2474.14.camel@venus> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id h56Ejt2x013886 X-archive-position: 4240 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jmorgan@sgi.com Precedence: bulk X-list: linux-xfs Take a look at http://oss.sgi.com/projects/fam/ ----------------------------------- Jon Morgan On 6 Jun 2003, Olaf [iso-8859-2] Fr±czyk wrote: > Hi, > > I need to monitor access to XFS filesystem: > file and directory: > creation/modification/delete/rename/rights change > with user names and time stamp. > Is such possibility in kernel/XFS fs code (for 2.4 kernels)? > > Regards, > > Olaf Fraczyk > > > > > > > From owner-linux-xfs@oss.sgi.com Fri Jun 6 08:41:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Jun 2003 08:41:13 -0700 (PDT) Received: from mail.sura.ru (mail.sura.ru [80.95.32.19]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h56Few2x016851 for ; Fri, 6 Jun 2003 08:41:00 -0700 Received: from 10.0.0.21 (host-80-95-32-106.leasedlines.sura.ru [80.95.32.106]) by mail.sura.ru (Postfix) with ESMTP id 31DD9150 for ; Fri, 6 Jun 2003 19:40:54 +0400 (MSD) Date: Fri, 6 Jun 2003 19:45:10 +0400 From: spied@yandex.ru X-Mailer: The Bat! (v1.61) Personal Reply-To: spied@yandex.ru X-Priority: 3 (Normal) Message-ID: <19985916953.20030606194510@yandex.ru> To: linux-xfs@oss.sgi.com Subject: sync mount MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4241 X-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 i want use root xfs partition in sync mode (i don't need high wite speed on it, and it's corruption stop server) how can i do it? i fast see sources - "-o sync" option is ignored, but exist option "-o wsync". what do wsync flag? can i use it to avoid possible filesystem damage? i use linux kernel 2.4.20-xfs from sgi and xfsprogs 2.0.3-1 from debian ps: sorry, my english is very bad From owner-linux-xfs@oss.sgi.com Sat Jun 7 00:10:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Jun 2003 00:12:32 -0700 (PDT) Received: from iris.acsalaska.net (iris.slb.nwc.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h577AL2x021375 for ; Sat, 7 Jun 2003 00:10:22 -0700 Received: from erbenson.alaska.net (25-pm1.nwc.alaska.net [209.112.138.25]) by iris.acsalaska.net (8.12.9/8.12.9) with ESMTP id h577AJk4061692 for ; Fri, 6 Jun 2003 23:10: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 AEECE3A09 for ; Fri, 6 Jun 2003 23:10:18 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 3062440FF44; Fri, 6 Jun 2003 23:10:18 -0800 (AKDT) Date: Fri, 6 Jun 2003 23:10:18 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: sync mount Message-ID: <20030607071018.GJ32642@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <19985916953.20030606194510@yandex.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="y/A/1bIHS6WQt0eA" Content-Disposition: inline In-Reply-To: <19985916953.20030606194510@yandex.ru> 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-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4242 X-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 --y/A/1bIHS6WQt0eA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 06, 2003 at 07:45:10PM +0400, spied@yandex.ru wrote: > i want use root xfs partition in sync mode (i don't need high wite > speed on it, and it's corruption stop server) /dev/hda3 / xfs defaults,sync 0 1 > how can i do it? i fast see sources - "-o sync" option is ignored, but it is not ignored. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --y/A/1bIHS6WQt0eA 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 iEYEARECAAYFAj7hj9kACgkQJKx7GixEevxI1wCglcKciVU+SmOBPN+rzPGSa91x JyYAn2vVC4Spk3gERpkyEHtRVy61hoJw =y0q9 -----END PGP SIGNATURE----- --y/A/1bIHS6WQt0eA-- From owner-linux-xfs@oss.sgi.com Sat Jun 7 07:08:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Jun 2003 07:09:11 -0700 (PDT) Received: from hermes.fachschaften.tu-muenchen.de (hermes.fachschaften.tu-muenchen.de [129.187.202.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h57E8p2x001282 for ; Sat, 7 Jun 2003 07:08:52 -0700 Received: (qmail 24313 invoked from network); 7 Jun 2003 14:08:46 -0000 Received: from mimas.fachschaften.tu-muenchen.de (129.187.202.58) by hermes.fachschaften.tu-muenchen.de with QMQP; 7 Jun 2003 14:08:46 -0000 Date: Sat, 7 Jun 2003 16:08:44 +0200 From: Adrian Bunk To: lord@sgi.com, linux-xfs@oss.sgi.com Cc: linux-kernel@vger.kernel.org Subject: 2.5.70-mm5: XFS compile error if CONFIG_SYSCTL && !CONFIG_PROC_FS Message-ID: <20030607140844.GM15311@fs.tum.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-archive-position: 4243 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bunk@fs.tum.de Precedence: bulk X-list: linux-xfs I'm getting the following compile error in 2.5.70-mm5 if CONFIG_SYSCTL && !CONFIG_PROC_FS: <-- snip --> ... CC fs/xfs/linux/xfs_sysctl.o fs/xfs/linux/xfs_sysctl.c: In function `xfs_stats_clear_proc_handler': fs/xfs/linux/xfs_sysctl.c:61: `xfsstats' undeclared (first use in this function) fs/xfs/linux/xfs_sysctl.c:61: (Each undeclared identifier is reported only once fs/xfs/linux/xfs_sysctl.c:61: for each function it appears in.) make[2]: *** [fs/xfs/linux/xfs_sysctl.o] Error 1 <-- snip --> cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed From owner-linux-xfs@oss.sgi.com Sat Jun 7 22:49:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Jun 2003 22:50:16 -0700 (PDT) Received: from hermod.slb.nwc.acsalaska.net (hermod.slb.nwc.acsalaska.net [209.112.155.45]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h585nl2x025909 for ; Sat, 7 Jun 2003 22:49:48 -0700 Received: from erbenson.alaska.net (38-pm1.nwc.alaska.net [209.112.138.38]) by hermod.slb.nwc.acsalaska.net (8.12.9/8.12.9) with ESMTP id h585nexK054234 for ; Sat, 7 Jun 2003 21:49: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 7B54A3A06 for ; Sat, 7 Jun 2003 21:49:39 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id AE16A40FF44; Sat, 7 Jun 2003 21:49:39 -0800 (AKDT) Date: Sat, 7 Jun 2003 21:49:39 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: [PATCH] Implement immutable/append-only flags in XFS #1 Message-ID: <20030608054939.GA8350@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="+g7M9IMkV8truYOl" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4244 X-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 --+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Over time there has been many requests for ext2 file flags such as immutable, append-only, sync, noatime be implemented in XFS. So, here it is. I have implemented all of the above flags in 2.4.20 and 2.4.21-rc7 XFS. The patch is relatively small and non-invasive, and from my testing appears to cause no backwards compatibility issues (older kernels ignore, and leave alone the new flags). Also xfs_repair and xfs_check do not seem to have any problems with the new flags either. However during my testing I did discover 3 issues: 1: The Linux VFS contains a bug which allows timestamp modification of immutable/append-only files. I have fixed this issue, and will send the patch to the linux-kernel mailing list shortly. I have included that patch in this mail for completeness. 2: xfsrestore breaks when immutable or append-only files are included in the dump. The problem is xfsrestore restores the file inode flags too soon, and then loses the access it needs to restore extended attributes, uid, gid, and permissions. I am not familiar enough with xfsrestore to really propose the fix, however i believe just changing it to restore at the very least immutable/append-only flags very last after all other restoration is complete should suffice to solve this problem. 3: I just found an undocumented behavior with regards to ext2's file flags; when set on a directory any new file/dir created will inherit the flags of the parent directory. I am not entirely convinced this is a good idea, at least for *all* flags. In ext2 this behavior has been half broken for as near as i can tell, forever up to 2.4.20 (2.4.21 fixes it), the brokenness is that the vfs is not immediately informed of any of the flags except sync, thus they don't actually go into affect on new files until the inode is revalidated (which could take quite some time). In addition ext2 only refrains from doing this on symlinks, not device special files; this means if you create a device node in a append-only directory the only way you will ever be able to remove it is with debugfs. (ioctl() calls on a device file go to the driver handling the node, not to the filesystem holding the node, thus chattr won't help you). My question on #3 is whether we want this behavior in XFS? my current patch does NOT implement it. My opinion is that the only flag this really makes sense for is sync, since setting the sync flag on a directory does not actually do anything for you (it only affects files), so making all new files created under a sync directory is seemingly sensible (and probably what the user would expect, more or less). this might make sense for noatime too, but I am less convinced of this. I am definitely not convinced its a sensible idea for append-only since it ends up allowing non-privileged users to create append-only files, which is not normally permitted. Also automatically setting the append-only flag on a newly created file won't necessarily make it append-only immediately, since a caller doing open("append-only-dir/file" O_RDWR|O_CREAT) will retain full read/write access so long as the file descriptor is kept open (the same is true if you chmod() a file, open descriptors retain access even if they could not get it on a new open()). So for now I submit the patch without the ext2 inheritance behavior, if you believe we should implement the ext2 behavior either partially, or fully I should be able to do that (though a suggestion on the best place in XFS to do this task would be welcome). I have also implemented the EXT2_IOC_SETFLAGS/EXT2_IOC_GETFLAGS ioctl()s so chattr/lsattr will work on xfs, this part of the patch is optional, if excluded then either lsattr/chattr would need to be modified to use XFS_IOC_FSSETXATTR and XFS_IOC_FSGETXATTR ioctls. I have included a (somewhat hideous) test program to check as many things as i could think of to ensure immutable/append-only are properly enforced, the only thing lacking in it is tests of all the XFS ioctls, perhaps someone familiar with xfs ioctls could add these (i tried to do at least the libhandle cases, but couldn't get libhandle to work). Important: this test program creates a test area with full world read/write permissions to ensure regular file permissions are not tainting the test, therefore it is NOT SAFE to run on systems with untrusted users. the usage is t_immutable -c /some/dir which will create a test area as /some/dir and run tests in it. t_immutable -C will create the test area without running any tests, and t_immutable -r will remove a test area. t_immutable /some/dir will run the tests on a previously created test area. Note if you run t_immutable on an ext2 filesystem in 2.4.21 kernels you will need to use debugfs to get rid of the device node it creates (same on kernels prior to 2.4.21 if you leave the test area around long enough). see above for why. feedback is welcome. diffstat output follows: fs/xfs/linux/xfs_ext2_ioctl.h | 45 +++++++++++++++++++ fs/xfs/linux/xfs_ioctl.c | 99 ++++++++++++++++++++++++++++++++++++++++++ fs/xfs/linux/xfs_iops.c | 6 ++ fs/xfs/linux/xfs_super.c | 16 ++++++ fs/xfs/linux/xfs_vnode.c | 17 +++++++ fs/xfs/xfs_acl.c | 2 fs/xfs/xfs_cap.c | 2 fs/xfs/xfs_dinode.h | 24 +++++++--- fs/xfs/xfs_fs.h | 7 ++ fs/xfs/xfs_inode.c | 5 +- fs/xfs/xfs_itable.c | 8 +++ fs/xfs/xfs_vnodeops.c | 16 ++++++ 12 files changed, 238 insertions(+), 9 deletions(-) -- Ethan Benson http://www.alaska.net/~erbenson/ --+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xfs-xflags.diff" diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ext2_ioctl.h linux-2.4-xfs/linux/fs/xfs/linux/xfs_ext2_ioctl.h --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ext2_ioctl.h Wed Dec 31 14:00:00 1969 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_ext2_ioctl.h Fri Jun 6 04:21:00 2003 @@ -0,0 +1,45 @@ +/* + * Copyright (c) 2000-2003 Silicon Graphics, Inc. All Rights Reserved. + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of version 2 of the GNU General Public License as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it would be useful, but + * WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + * + * Further, this software is distributed without any warranty that it is + * free of the rightful claim of any third person regarding infringement + * or the like. Any license provided herein, whether implied or + * otherwise, applies only to this software file. Patent licenses, if + * any, provided herein do not apply to combinations of this program with + * other software, or any other product whatsoever. + * + * You should have received a copy of the GNU General Public License along + * with this program; if not, write the Free Software Foundation, Inc., 59 + * Temple Place - Suite 330, Boston MA 02111-1307, USA. + * + * Contact information: Silicon Graphics, Inc., 1600 Amphitheatre Pkwy, + * Mountain View, CA 94043, or: + * + * http://www.sgi.com + * + * For further information regarding this notice, see: + * + * http://oss.sgi.com/projects/GenInfo/SGIGPLNoticeExplan/ + */ +#ifndef __XFS_EXT2_IOCTL_H__ +#define __XFS_EXT2_IOCTL_H__ + +/* ext2 ioctls (EXT2_IOC_GETFLAGS and EXT2_IOC_SETFLAGS) to support + * chattr/lsattr */ +#define XFS_IOC_EXT2_GETFLAGS _IOR('f', 1, long) +#define XFS_IOC_EXT2_SETFLAGS _IOW('f', 2, long) + +#define EXT2_FLAG_SYNC 0x00000008 /* Synchronous updates */ +#define EXT2_FLAG_IMMUTABLE 0x00000010 /* Immutable file */ +#define EXT2_FLAG_APPEND 0x00000020 /* writes to file may only append */ +#define EXT2_FLAG_NOATIME 0x00000080 /* do not update atime */ + +#endif /* __XFS_EXT2_IOCTL_H__ */ diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ioctl.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_ioctl.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ioctl.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_ioctl.c Fri Jun 6 04:29:58 2003 @@ -66,6 +66,7 @@ #include "xfs_utils.h" #include "xfs_dfrag.h" #include "xfs_fsops.h" +#include "xfs_ext2_ioctl.h" #include #include @@ -327,6 +328,12 @@ if (permflag & O_TRUNC) permflag |= 2; + if (!(permflag & O_APPEND) && (permflag & FMODE_WRITE) && IS_APPEND(inode)) + return -XFS_ERROR(EPERM); + + if ((permflag & FMODE_WRITE) && IS_IMMUTABLE(inode)) + return -XFS_ERROR(EACCES); + /* Can't write directories. */ if ( S_ISDIR(inode->i_mode) && (permflag & FMODE_WRITE)) { iput(inode); @@ -447,6 +454,9 @@ if (error) return -error; + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) + return -XFS_ERROR(EPERM); + if (copy_from_user(&fsd, dmhreq.data, sizeof(fsd))) { VN_RELE(vp); return -XFS_ERROR(EFAULT); @@ -532,11 +542,21 @@ NULL, ops[i].am_error); break; case ATTR_OP_SET: + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) { + kfree(ops); + VN_RELE(vp); + return -XFS_ERROR(EPERM); + } VOP_ATTR_SET(vp,ops[i].am_attrname, ops[i].am_attrvalue, ops[i].am_length, ops[i].am_flags, NULL, ops[i].am_error); break; case ATTR_OP_REMOVE: + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) { + kfree(ops); + VN_RELE(vp); + return -XFS_ERROR(EPERM); + } VOP_ATTR_REMOVE(vp, ops[i].am_attrname, ops[i].am_flags, NULL, ops[i].am_error); break; @@ -842,6 +862,75 @@ error = xfs_errortag_clearall(mp); return -error; + case XFS_IOC_EXT2_GETFLAGS: { + unsigned int flags = 0; + + if (vp->v_inode.i_flags & S_IMMUTABLE) + flags |= EXT2_FLAG_IMMUTABLE; /* EXT2_IMMUTABLE_FL */ + if (vp->v_inode.i_flags & S_APPEND) + flags |= EXT2_FLAG_APPEND; /* EXT2_APPEND_FL */ + if (vp->v_inode.i_flags & S_SYNC) + flags |= EXT2_FLAG_SYNC; /* EXT2_SYNC_FL */ + if (vp->v_inode.i_flags & S_NOATIME) + flags |= EXT2_FLAG_NOATIME; /* EXT2_NOATIME_FL */ + + if (copy_to_user((unsigned int *)arg, &flags, sizeof(flags))) + return -XFS_ERROR(EFAULT); + return 0; + } + + case XFS_IOC_EXT2_SETFLAGS: { + vattr_t va; + unsigned int flags; + int attr_flags = 0; + + if (copy_from_user(&flags, (unsigned int *)arg, sizeof(flags))) + return -XFS_ERROR(EFAULT); + + /* we need to do getattr to preserve XFS xflags ext2 + * has no knowledge of */ + + va.va_mask = XFS_AT_XFLAGS; + VOP_GETATTR(vp, &va, 0, NULL, error); + if (error) + return -error; + + if (flags & (EXT2_FLAG_IMMUTABLE|EXT2_FLAG_APPEND) || + va.va_xflags & (XFS_XFLAG_IMMUTABLE|XFS_XFLAG_APPEND)) + if (!capable(CAP_LINUX_IMMUTABLE)) + return -XFS_ERROR(EPERM); + + /* don't silently ignore unsupported ext2 flags */ + if (flags & ~(EXT2_FLAG_IMMUTABLE|EXT2_FLAG_APPEND| + EXT2_FLAG_SYNC|EXT2_FLAG_NOATIME)) + return -XFS_ERROR(EOPNOTSUPP); + + if (flags & EXT2_FLAG_IMMUTABLE) /* EXT2_IMMUTABLE_FL */ + va.va_xflags |= XFS_XFLAG_IMMUTABLE; + else + va.va_xflags &= ~XFS_XFLAG_IMMUTABLE; + if (flags & EXT2_FLAG_APPEND) /* EXT2_APPEND_FL */ + va.va_xflags |= XFS_XFLAG_APPEND; + else + va.va_xflags &= ~XFS_XFLAG_APPEND; + if (flags & EXT2_FLAG_SYNC) /* EXT2_SYNC_FL */ + va.va_xflags |= XFS_XFLAG_SYNC; + else + va.va_xflags &= ~XFS_XFLAG_SYNC; + if (flags & EXT2_FLAG_NOATIME) /* EXT2_NOATIME_FL */ + va.va_xflags |= XFS_XFLAG_NOATIME; + else + va.va_xflags &= ~XFS_XFLAG_NOATIME; + + if (filp->f_flags & (O_NDELAY|O_NONBLOCK)) + attr_flags |= ATTR_NONBLOCK; + + VOP_SETATTR(vp, &va, attr_flags, NULL, error); + if (!error) + vn_revalidate(vp); /* push immutable/append flags into vfs inode */ + return -error; + } + default: return -ENOTTY; } @@ -859,6 +948,9 @@ int attr_flags = 0; int error; + if (vp->v_inode.i_flags & (S_IMMUTABLE|S_APPEND)) + return -XFS_ERROR(EPERM); + if (filp->f_flags & O_RDONLY) return -XFS_ERROR(EBADF); @@ -1012,6 +1104,11 @@ if (copy_from_user(&fa, (struct fsxattr *)arg, sizeof(fa))) return -XFS_ERROR(EFAULT); + if (fa.fsx_xflags & (XFS_XFLAG_IMMUTABLE|XFS_XFLAG_APPEND) || + va.va_xflags & (XFS_XFLAG_IMMUTABLE|XFS_XFLAG_APPEND)) + if (!capable(CAP_LINUX_IMMUTABLE)) + return -XFS_ERROR(EPERM); + va.va_mask = XFS_AT_XFLAGS | XFS_AT_EXTSIZE; va.va_xflags = fa.fsx_xflags; va.va_extsize = fa.fsx_extsize; @@ -1020,6 +1117,8 @@ attr_flags |= ATTR_NONBLOCK; VOP_SETATTR(vp, &va, attr_flags, NULL, error); + if (!error) + vn_revalidate(vp); /* push immutable/append flags into vfs inode */ return -error; } diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_iops.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_iops.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_iops.c Thu May 1 13:05:53 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_iops.c Fri Jun 6 03:22:27 2003 @@ -615,6 +615,9 @@ return error; } + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) + return -EPERM; + /* Convert Linux syscall to XFS internal ATTR flags */ if (flags & XATTR_CREATE) xflags |= ATTR_CREATE; @@ -764,6 +767,9 @@ error = xfs_cap_vremove(vp); return error; } + + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) + return -EPERM; if (strncmp(name, xfs_namespaces[ROOT_NAMES].name, xfs_namespaces[ROOT_NAMES].namelen) == 0) { diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_super.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_super.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_super.c Mon Jun 2 07:34:46 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_super.c Fri Jun 6 03:22:27 2003 @@ -147,6 +147,22 @@ inode->i_atime = ip->i_d.di_atime.t_sec; inode->i_mtime = ip->i_d.di_mtime.t_sec; inode->i_ctime = ip->i_d.di_ctime.t_sec; + if (ip->i_d.di_flags & XFS_DIFLAG_IMMUTABLE) + inode->i_flags |= S_IMMUTABLE; + else + inode->i_flags &= ~S_IMMUTABLE; + if (ip->i_d.di_flags & XFS_DIFLAG_APPEND) + inode->i_flags |= S_APPEND; + else + inode->i_flags &= ~S_APPEND; + if (ip->i_d.di_flags & XFS_DIFLAG_SYNC) + inode->i_flags |= S_SYNC; + else + inode->i_flags &= ~S_SYNC; + if (ip->i_d.di_flags & XFS_DIFLAG_NOATIME) + inode->i_flags |= S_NOATIME; + else + inode->i_flags &= ~S_NOATIME; vp->v_flag &= ~VMODIFIED; } diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_vnode.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_vnode.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_vnode.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_vnode.c Fri Jun 6 03:22:27 2003 @@ -224,6 +224,23 @@ inode->i_mtime = va.va_mtime.tv_sec; inode->i_ctime = va.va_ctime.tv_sec; inode->i_atime = va.va_atime.tv_sec; + if (va.va_xflags & XFS_XFLAG_IMMUTABLE) + inode->i_flags |= S_IMMUTABLE; + else + inode->i_flags &= ~S_IMMUTABLE; + if (va.va_xflags & XFS_XFLAG_APPEND) + inode->i_flags |= S_APPEND; + else + inode->i_flags &= ~S_APPEND; + if (va.va_xflags & XFS_XFLAG_SYNC) + inode->i_flags |= S_SYNC; + else + inode->i_flags &= ~S_SYNC; + if (va.va_xflags & XFS_XFLAG_NOATIME) + inode->i_flags |= S_NOATIME; + else + inode->i_flags &= ~S_NOATIME; + VUNMODIFY(vp); } return -error; diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_acl.c linux-2.4-xfs/linux/fs/xfs/xfs_acl.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_acl.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_acl.c Fri Jun 6 03:22:27 2003 @@ -388,6 +388,8 @@ vattr_t va; int error; + if (vp->v_inode.i_flags & (S_IMMUTABLE|S_APPEND)) + return EPERM; if (kind == _ACL_TYPE_DEFAULT && vp->v_type != VDIR) return ENOTDIR; if (vp->v_vfsp->vfs_flag & VFS_RDONLY) diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_cap.c linux-2.4-xfs/linux/fs/xfs/xfs_cap.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_cap.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_cap.c Fri Jun 6 04:24:17 2003 @@ -192,6 +192,8 @@ if (vp->v_vfsp->vfs_flag & VFS_RDONLY) return EROFS; + if (vp->v_inode.i_flags & (S_IMMUTABLE|S_APPEND)) + return EPERM; if ((error = _MAC_VACCESS(vp, NULL, VWRITE))) return error; va.va_mask = XFS_AT_UID; diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_dinode.h linux-2.4-xfs/linux/fs/xfs/xfs_dinode.h --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_dinode.h Tue Apr 15 15:16:46 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_dinode.h Fri Jun 6 03:59:35 2003 @@ -468,13 +468,23 @@ * There should be a one-to-one correspondence between these flags and the * XFS_XFLAG_s. */ -#define XFS_DIFLAG_REALTIME_BIT 0 /* file's blocks come from rt area */ -#define XFS_DIFLAG_PREALLOC_BIT 1 /* file space has been preallocated */ -#define XFS_DIFLAG_NEWRTBM_BIT 2 /* for rtbitmap inode, new format */ -#define XFS_DIFLAG_REALTIME (1 << XFS_DIFLAG_REALTIME_BIT) -#define XFS_DIFLAG_PREALLOC (1 << XFS_DIFLAG_PREALLOC_BIT) -#define XFS_DIFLAG_NEWRTBM (1 << XFS_DIFLAG_NEWRTBM_BIT) +#define XFS_DIFLAG_REALTIME_BIT 0 /* file's blocks come from rt area */ +#define XFS_DIFLAG_PREALLOC_BIT 1 /* file space has been preallocated */ +#define XFS_DIFLAG_NEWRTBM_BIT 2 /* for rtbitmap inode, new format */ +#define XFS_DIFLAG_IMMUTABLE_BIT 3 /* inode is immutable */ +#define XFS_DIFLAG_APPEND_BIT 4 /* inode is append-only */ +#define XFS_DIFLAG_SYNC_BIT 5 /* inode is written synchronously */ +#define XFS_DIFLAG_NOATIME_BIT 6 /* do not update atime */ +#define XFS_DIFLAG_REALTIME (1 << XFS_DIFLAG_REALTIME_BIT) +#define XFS_DIFLAG_PREALLOC (1 << XFS_DIFLAG_PREALLOC_BIT) +#define XFS_DIFLAG_NEWRTBM (1 << XFS_DIFLAG_NEWRTBM_BIT) +#define XFS_DIFLAG_IMMUTABLE (1 << XFS_DIFLAG_IMMUTABLE_BIT) +#define XFS_DIFLAG_APPEND (1 << XFS_DIFLAG_APPEND_BIT) +#define XFS_DIFLAG_SYNC (1 << XFS_DIFLAG_SYNC_BIT) +#define XFS_DIFLAG_NOATIME (1 << XFS_DIFLAG_NOATIME_BIT) #define XFS_DIFLAG_ALL \ - (XFS_DIFLAG_REALTIME|XFS_DIFLAG_PREALLOC|XFS_DIFLAG_NEWRTBM) + (XFS_DIFLAG_REALTIME|XFS_DIFLAG_PREALLOC|XFS_DIFLAG_NEWRTBM| \ + XFS_DIFLAG_IMMUTABLE|XFS_DIFLAG_APPEND|XFS_DIFLAG_SYNC| \ + XFS_DIFLAG_NOATIME) #endif /* __XFS_DINODE_H__ */ diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_fs.h linux-2.4-xfs/linux/fs/xfs/xfs_fs.h --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_fs.h Sun Mar 30 18:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_fs.h Fri Jun 6 03:22:27 2003 @@ -71,9 +71,14 @@ */ #define XFS_XFLAG_REALTIME 0x00000001 #define XFS_XFLAG_PREALLOC 0x00000002 +#define XFS_XFLAG_IMMUTABLE 0x00000008 +#define XFS_XFLAG_APPEND 0x00000010 +#define XFS_XFLAG_SYNC 0x00000020 +#define XFS_XFLAG_NOATIME 0x00000040 #define XFS_XFLAG_HASATTR 0x80000000 /* no DIFLAG for this */ #define XFS_XFLAG_ALL \ - ( XFS_XFLAG_REALTIME|XFS_XFLAG_PREALLOC|XFS_XFLAG_HASATTR ) + ( XFS_XFLAG_REALTIME|XFS_XFLAG_PREALLOC|XFS_XFLAG_IMMUTABLE| \ + XFS_XFLAG_APPEND|XFS_XFLAG_SYNC|XFS_XFLAG_NOATIME|XFS_XFLAG_HASATTR ) /* diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_inode.c linux-2.4-xfs/linux/fs/xfs/xfs_inode.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_inode.c Wed May 21 17:07:13 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_inode.c Fri Jun 6 03:22:27 2003 @@ -3485,6 +3485,9 @@ if (IS_RDONLY(inode) && (S_ISREG(imode) || S_ISDIR(imode) || S_ISLNK(imode))) return XFS_ERROR(EROFS); + + if (IS_IMMUTABLE(inode)) + return XFS_ERROR(EACCES); } /* @@ -3608,7 +3611,7 @@ * Don't update access timestamps on reads if mounted "noatime" * Throw it away if anyone asks us. */ - if (ip->i_mount->m_flags & XFS_MOUNT_NOATIME && + if ((ip->i_mount->m_flags & XFS_MOUNT_NOATIME || IS_NOATIME(inode)) && ((flags & (XFS_ICHGTIME_ACC|XFS_ICHGTIME_MOD|XFS_ICHGTIME_CHG)) == XFS_ICHGTIME_ACC)) return; diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_itable.c linux-2.4-xfs/linux/fs/xfs/xfs_itable.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_itable.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_itable.c Fri Jun 6 03:22:27 2003 @@ -163,6 +163,14 @@ XFS_XFLAG_REALTIME : 0) | ((di_flags & XFS_DIFLAG_PREALLOC) ? XFS_XFLAG_PREALLOC : 0) | + ((di_flags & XFS_DIFLAG_IMMUTABLE) ? + XFS_XFLAG_IMMUTABLE : 0) | + ((di_flags & XFS_DIFLAG_APPEND) ? + XFS_XFLAG_APPEND : 0) | + ((di_flags & XFS_DIFLAG_SYNC) ? + XFS_XFLAG_SYNC : 0) | + ((di_flags & XFS_DIFLAG_NOATIME) ? + XFS_XFLAG_NOATIME : 0) | (XFS_CFORK_Q_ARCH(dic, arch) ? XFS_XFLAG_HASATTR : 0); diff -urN -x CVS linux-2.4-xfs.orig/linux/fs/xfs/xfs_vnodeops.c linux-2.4-xfs/linux/fs/xfs/xfs_vnodeops.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_vnodeops.c Tue May 6 12:53:19 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_vnodeops.c Fri Jun 6 04:02:57 2003 @@ -266,6 +266,14 @@ XFS_XFLAG_REALTIME : 0) | ((ip->i_d.di_flags & XFS_DIFLAG_PREALLOC) ? XFS_XFLAG_PREALLOC : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_IMMUTABLE) ? + XFS_XFLAG_IMMUTABLE : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_APPEND) ? + XFS_XFLAG_APPEND : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_SYNC) ? + XFS_XFLAG_SYNC : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_NOATIME) ? + XFS_XFLAG_NOATIME : 0) | (XFS_IFORK_Q(ip) ? XFS_XFLAG_HASATTR : 0); vap->va_extsize = ip->i_d.di_extsize << mp->m_sb.sb_blocklog; @@ -829,6 +837,14 @@ ip->i_d.di_flags |= XFS_DIFLAG_REALTIME; ip->i_iocore.io_flags |= XFS_IOCORE_RT; } + if (vap->va_xflags & XFS_XFLAG_IMMUTABLE) + ip->i_d.di_flags |= XFS_DIFLAG_IMMUTABLE; + if (vap->va_xflags & XFS_XFLAG_APPEND) + ip->i_d.di_flags |= XFS_DIFLAG_APPEND; + if (vap->va_xflags & XFS_XFLAG_SYNC) + ip->i_d.di_flags |= XFS_DIFLAG_SYNC; + if (vap->va_xflags & XFS_XFLAG_NOATIME) + ip->i_d.di_flags |= XFS_DIFLAG_NOATIME; /* can't set PREALLOC this way, just ignore it */ } xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE); --+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="open.c.diff" --- linux.orig/fs/open.c Sun Jun 1 20:39:38 2003 +++ linux/fs/open.c Sun Jun 1 20:54:14 2003 @@ -272,6 +272,9 @@ /* Don't worry, the checks are done in inode_change_ok() */ newattrs.ia_valid = ATTR_CTIME | ATTR_MTIME | ATTR_ATIME; if (times) { + error = -EPERM; + if (IS_APPEND(inode) || IS_IMMUTABLE(inode)) + goto dput_and_out; error = get_user(newattrs.ia_atime, ×->actime); if (!error) error = get_user(newattrs.ia_mtime, ×->modtime); @@ -280,6 +283,9 @@ newattrs.ia_valid |= ATTR_ATIME_SET | ATTR_MTIME_SET; } else { + error = -EACCES; + if (IS_IMMUTABLE(inode)) + goto dput_and_out; if (current->fsuid != inode->i_uid && (error = permission(inode,MAY_WRITE)) != 0) goto dput_and_out; @@ -318,6 +324,9 @@ newattrs.ia_valid = ATTR_CTIME | ATTR_MTIME | ATTR_ATIME; if (utimes) { struct timeval times[2]; + error = -EPERM; + if (IS_APPEND(inode) || IS_IMMUTABLE(inode)) + goto dput_and_out; error = -EFAULT; if (copy_from_user(×, utimes, sizeof(times))) goto dput_and_out; @@ -325,6 +334,10 @@ newattrs.ia_mtime = times[1].tv_sec; newattrs.ia_valid |= ATTR_ATIME_SET | ATTR_MTIME_SET; } else { + error = -EACCES; + if (IS_IMMUTABLE(inode)) + goto dput_and_out; + if (current->fsuid != inode->i_uid && (error = permission(inode,MAY_WRITE)) != 0) goto dput_and_out; --+g7M9IMkV8truYOl-- From owner-linux-xfs@oss.sgi.com Sun Jun 8 04:02:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Jun 2003 04:03:19 -0700 (PDT) Received: from phoenix.infradead.org (carisma.slowglass.com [195.224.96.167]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h58B2B2x004333 for ; Sun, 8 Jun 2003 04:02:12 -0700 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 19Oxw0-00007u-00; Sun, 08 Jun 2003 12:02:00 +0100 Date: Sun, 8 Jun 2003 12:01:59 +0100 From: Christoph Hellwig To: Adrian Bunk Cc: lord@sgi.com, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: 2.5.70-mm5: XFS compile error if CONFIG_SYSCTL && !CONFIG_PROC_FS Message-ID: <20030608120159.A450@infradead.org> Mail-Followup-To: Christoph Hellwig , Adrian Bunk , lord@sgi.com, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org References: <20030607140844.GM15311@fs.tum.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030607140844.GM15311@fs.tum.de>; from bunk@fs.tum.de on Sat, Jun 07, 2003 at 04:08:44PM +0200 X-archive-position: 4245 X-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 On Sat, Jun 07, 2003 at 04:08:44PM +0200, Adrian Bunk wrote: > I'm getting the following compile error in 2.5.70-mm5 if CONFIG_SYSCTL > && !CONFIG_PROC_FS: > > <-- snip --> > > ... > CC fs/xfs/linux/xfs_sysctl.o > fs/xfs/linux/xfs_sysctl.c: In function `xfs_stats_clear_proc_handler': > fs/xfs/linux/xfs_sysctl.c:61: `xfsstats' undeclared (first use in this function) > fs/xfs/linux/xfs_sysctl.c:61: (Each undeclared identifier is reported only once > fs/xfs/linux/xfs_sysctl.c:61: for each function it appears in.) > make[2]: *** [fs/xfs/linux/xfs_sysctl.o] Error 1 This should fix it: --- 1.10/fs/xfs/linux/xfs_sysctl.c Mon May 19 20:29:41 2003 +++ edited/fs/xfs/linux/xfs_sysctl.c Sat Jun 7 12:01:27 2003 @@ -36,12 +36,12 @@ #include -STATIC ulong xfs_min[XFS_PARAM] = { 0, 0, 0, 0, 0, 0, HZ }; -STATIC ulong xfs_max[XFS_PARAM] = { 1, 1, 1, 1, 127, 3, HZ * 60 }; +STATIC ulong xfs_min[XFS_PARAM] = { 0, 0, 0, 0, 0, HZ, 0 }; +STATIC ulong xfs_max[XFS_PARAM] = { 1, 1, 1, 127, 3, HZ * 60, 1 }; static struct ctl_table_header *xfs_table_header; - +#ifdef CONFIG_PROC_FS STATIC int xfs_stats_clear_proc_handler( ctl_table *ctl, @@ -66,35 +66,39 @@ return ret; } +#endif /* CONFIG_PROC_FS */ STATIC ctl_table xfs_table[] = { - {XFS_STATS_CLEAR, "stats_clear", &xfs_params.stats_clear, - sizeof(ulong), 0644, NULL, &xfs_stats_clear_proc_handler, - &sysctl_intvec, NULL, &xfs_min[0], &xfs_max[0]}, - {XFS_RESTRICT_CHOWN, "restrict_chown", &xfs_params.restrict_chown, sizeof(ulong), 0644, NULL, &proc_doulongvec_minmax, - &sysctl_intvec, NULL, &xfs_min[1], &xfs_max[1]}, + &sysctl_intvec, NULL, &xfs_min[0], &xfs_max[0]}, {XFS_SGID_INHERIT, "irix_sgid_inherit", &xfs_params.sgid_inherit, sizeof(ulong), 0644, NULL, &proc_doulongvec_minmax, - &sysctl_intvec, NULL, &xfs_min[2], &xfs_max[2]}, + &sysctl_intvec, NULL, &xfs_min[1], &xfs_max[1]}, {XFS_SYMLINK_MODE, "irix_symlink_mode", &xfs_params.symlink_mode, sizeof(ulong), 0644, NULL, &proc_doulongvec_minmax, - &sysctl_intvec, NULL, &xfs_min[3], &xfs_max[3]}, + &sysctl_intvec, NULL, &xfs_min[2], &xfs_max[2]}, {XFS_PANIC_MASK, "panic_mask", &xfs_params.panic_mask, sizeof(ulong), 0644, NULL, &proc_doulongvec_minmax, - &sysctl_intvec, NULL, &xfs_min[4], &xfs_max[4]}, + &sysctl_intvec, NULL, &xfs_min[3], &xfs_max[3]}, {XFS_ERRLEVEL, "error_level", &xfs_params.error_level, sizeof(ulong), 0644, NULL, &proc_doulongvec_minmax, - &sysctl_intvec, NULL, &xfs_min[5], &xfs_max[5]}, + &sysctl_intvec, NULL, &xfs_min[4], &xfs_max[4]}, {XFS_SYNC_INTERVAL, "sync_interval", &xfs_params.sync_interval, sizeof(ulong), 0644, NULL, &proc_doulongvec_minmax, + &sysctl_intvec, NULL, &xfs_min[5], &xfs_max[5]}, + + /* please keep this the last entry */ +#ifdef CONFIG_PROC_FS + {XFS_STATS_CLEAR, "stats_clear", &xfs_params.stats_clear, + sizeof(ulong), 0644, NULL, &xfs_stats_clear_proc_handler, &sysctl_intvec, NULL, &xfs_min[6], &xfs_max[6]}, +#endif {0} }; ===== fs/xfs/linux/xfs_sysctl.h 1.8 vs edited ===== --- 1.8/fs/xfs/linux/xfs_sysctl.h Mon May 19 20:29:41 2003 +++ edited/fs/xfs/linux/xfs_sysctl.h Sat Jun 7 12:01:07 2003 @@ -42,7 +42,6 @@ #define XFS_PARAM (sizeof(struct xfs_param) / sizeof(ulong)) typedef struct xfs_param { - ulong stats_clear; /* Reset all XFS statistics to zero. */ ulong restrict_chown; /* Root/non-root can give away files. */ ulong sgid_inherit; /* Inherit ISGID bit if process' GID is */ /* not a member of the parent dir GID. */ @@ -50,6 +49,7 @@ ulong panic_mask; /* bitmask to specify panics on errors. */ ulong error_level; /* Degree of reporting for internal probs*/ ulong sync_interval; /* time between sync calls */ + ulong stats_clear; /* Reset all XFS statistics to zero. */ } xfs_param_t; /* @@ -68,13 +68,13 @@ */ enum { - XFS_STATS_CLEAR = 1, - XFS_RESTRICT_CHOWN = 2, - XFS_SGID_INHERIT = 3, - XFS_SYMLINK_MODE = 4, - XFS_PANIC_MASK = 5, - XFS_ERRLEVEL = 6, - XFS_SYNC_INTERVAL = 7, + XFS_RESTRICT_CHOWN = 1, + XFS_SGID_INHERIT = 2, + XFS_SYMLINK_MODE = 3, + XFS_PANIC_MASK = 4, + XFS_ERRLEVEL = 5, + XFS_SYNC_INTERVAL = 6, + XFS_STATS_CLEAR = 7, }; extern xfs_param_t xfs_params; From owner-linux-xfs@oss.sgi.com Sun Jun 8 05:52:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Jun 2003 05:53:15 -0700 (PDT) Received: from hermes.fachschaften.tu-muenchen.de (hermes.fachschaften.tu-muenchen.de [129.187.202.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h58Cqs2x011075 for ; Sun, 8 Jun 2003 05:52:55 -0700 Received: (qmail 15771 invoked from network); 8 Jun 2003 12:52:50 -0000 Received: from mimas.fachschaften.tu-muenchen.de (129.187.202.58) by hermes.fachschaften.tu-muenchen.de with QMQP; 8 Jun 2003 12:52:50 -0000 Date: Sun, 8 Jun 2003 14:52:49 +0200 From: Adrian Bunk To: Christoph Hellwig , lord@sgi.com, linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: 2.5.70-mm5: XFS compile error if CONFIG_SYSCTL && !CONFIG_PROC_FS Message-ID: <20030608125249.GE16164@fs.tum.de> References: <20030607140844.GM15311@fs.tum.de> <20030608120159.A450@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030608120159.A450@infradead.org> User-Agent: Mutt/1.4.1i X-archive-position: 4246 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bunk@fs.tum.de Precedence: bulk X-list: linux-xfs On Sun, Jun 08, 2003 at 12:01:59PM +0100, Christoph Hellwig wrote: > On Sat, Jun 07, 2003 at 04:08:44PM +0200, Adrian Bunk wrote: > > I'm getting the following compile error in 2.5.70-mm5 if CONFIG_SYSCTL > > && !CONFIG_PROC_FS: > > > > <-- snip --> > > > > ... > > CC fs/xfs/linux/xfs_sysctl.o > > fs/xfs/linux/xfs_sysctl.c: In function `xfs_stats_clear_proc_handler': > > fs/xfs/linux/xfs_sysctl.c:61: `xfsstats' undeclared (first use in this function) > > fs/xfs/linux/xfs_sysctl.c:61: (Each undeclared identifier is reported only once > > fs/xfs/linux/xfs_sysctl.c:61: for each function it appears in.) > > make[2]: *** [fs/xfs/linux/xfs_sysctl.o] Error 1 > > This should fix it: >... Thanks, I can confirm your patch fixes the problem. cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed From owner-linux-xfs@oss.sgi.com Sun Jun 8 11:51:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Jun 2003 11:51:47 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h58IpS2x026182 for ; Sun, 8 Jun 2003 11:51:28 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h58IpS1q026181 for linux-xfs@oss.sgi.com; Sun, 8 Jun 2003 11:51:28 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h58IpP31026167 for ; Sun, 8 Jun 2003 11:51:26 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h58I6jc8025904; Sun, 8 Jun 2003 11:06:45 -0700 Date: Sun, 8 Jun 2003 11:06:45 -0700 Message-Id: <200306081806.h58I6jc8025904@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 249] New: Installing RedHat9 with SGI-XFS installer leades to network admin problem X-Bugzilla-Reason: AssignedTo X-archive-position: 4247 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=249 Summary: Installing RedHat9 with SGI-XFS installer leades to network admin problem Product: Linux XFS Version: 1.2.x Platform: All OS/Version: Linux Status: NEW Severity: major Priority: High Component: xfstests AssignedTo: xfs-master@oss.sgi.com ReportedBy: ljoeckel@t-online.de After installing with the 1.2 SGI-XFS installation image i got the following exception after running the admin-tool 'System-Settings -> Network': ========================================== Component: redhat-config-network Version: 1.2.0 Summary: TB /usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py:198:__init__:NameError: global name 'timeout_add' is not defined Traceback (most recent call last): File "/usr/sbin/redhat-config-network-gui", line 154, in ? window = mainDialog() File "/usr/src/build/226257-noarch/install/usr/share/redhat-config-network/netconfpkg/gui/maindialog.py", line 198, in __init__ NameError: global name 'timeout_add' is not defined ========================================================= I've reinstalled Linux with the original RedHat9 CD's and with them it works. ------- 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 Sun Jun 8 14:33:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Jun 2003 14:34:01 -0700 (PDT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h58LXf2x027561 for ; Sun, 8 Jun 2003 14:33:42 -0700 Received: from online.no (126.80-202-103.nextgentel.com [80.202.103.126]) by mail.broadpark.no (Postfix) with ESMTP id 408C7787D1 for ; Sun, 8 Jun 2003 23:33:35 +0200 (MEST) Message-ID: <3EE3AA47.312D4DBC@online.no> Date: Sun, 08 Jun 2003 23:27:35 +0200 From: Knut J Bjuland X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.20-13.9SGI_XFS_1.2.0custom i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: where can I find the SRPMS for 1.3pre1 or is available for 2.4.20-18rh Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4248 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: knutjbj@online.no Precedence: bulk X-list: linux-xfs where can I find the SRPMS for 1.3pre1 or is available for 2.4.20-18rh? From owner-linux-xfs@oss.sgi.com Mon Jun 9 00:10:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 00:10:23 -0700 (PDT) Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h597AJ2x005633 for ; Mon, 9 Jun 2003 00:10:20 -0700 Received: from online.no (126.80-202-103.nextgentel.com [80.202.103.126]) by mail.broadpark.no (Postfix) with ESMTP id 42F8678F49 for ; Mon, 9 Jun 2003 09:10:11 +0200 (MEST) Message-ID: <3EE43169.6CE0CF33@online.no> Date: Mon, 09 Jun 2003 09:04:09 +0200 From: Knut J Bjuland X-Mailer: Mozilla 4.8 [en] (X11; U; Linux 2.4.20-13.9SGI_XFS_1.2.0custom i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: error when patching redhat 2.4.20-18.9 with xfs 1.3-pre1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4249 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: knutjbj@online.no Precedence: bulk X-list: linux-xfs I get this error messeage. from :1: /usr/src/redhat/BUILD/kernel-2.4.20/linux-2.4.20/include/linux/modules/sunrpc_syms.ver:38:1: warning: this is the location of the previous definition super.c: In function `read_super_block': super.c:869: warning: int format, long unsigned int arg (arg 2) super.c:944:14: warning: multi-line string literals are deprecated xfs_super.c: In function `syncd': xfs_super.c:430: structure has no member named `sigmask_lock' xfs_super.c:432: too many arguments to function `recalc_sigpending_Rfb6af58d' make[3]: *** [xfs_super.o] Error 1 make[2]: *** [_modsubdir_linux] Error 2 make[1]: *** [_modsubdir_xfs] Error 2 make: *** [_mod_fs] Error 2 + exit 1 From owner-linux-xfs@oss.sgi.com Mon Jun 9 00:41:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 00:41:56 -0700 (PDT) Received: from malik.acsalaska.net (malik.slb.nwc.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h597fX2x007549 for ; Mon, 9 Jun 2003 00:41:34 -0700 Received: from erbenson.alaska.net (148-pm19.nwc.alaska.net [209.112.142.148]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h597fS7f035771 for ; Sun, 8 Jun 2003 23:41:28 -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 3D5323A0C for ; Sun, 8 Jun 2003 23:41:26 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id DCE0740FF44; Sun, 8 Jun 2003 23:41:26 -0800 (AKDT) Date: Sun, 8 Jun 2003 23:41:26 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: [PATCH] Implement immutable/append-only flags in XFS #2 Message-ID: <20030609074126.GA17899@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-ACS-Spam-Status: no X-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4250 X-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 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi, I finally figured out libhandle and added tests for it to my test program and found a small bug in the check for append-only opens within open_by_handle. This updated patch fixes this. also I neglected to attach my test program in the last mail, just as well as its rather large, you can get it from http://penguinppc.org/~eb/t_immutable.c After adding the libhandle tests I found that I get the following message on umount of the relevant partition after running my test program: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... This occurs on both 2.4.20 and 2.4.21-rc7. -- Ethan Benson http://www.alaska.net/~erbenson/ --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xfs-xflags.diff" diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ext2_ioctl.h linux-2.4-xfs/linux/fs/xfs/linux/xfs_ext2_ioctl.h --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ext2_ioctl.h Wed Dec 31 14:00:00 1969 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_ext2_ioctl.h Fri Jun 6 04:21:00 2003 @@ -0,0 +1,45 @@ +/* + * Copyright (c) 2000-2003 Silicon Graphics, Inc. All Rights Reserved. + * + * This program is free software; you can redistribute it and/or modify it + * under the terms of version 2 of the GNU General Public License as + * published by the Free Software Foundation. + * + * This program is distributed in the hope that it would be useful, but + * WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. + * + * Further, this software is distributed without any warranty that it is + * free of the rightful claim of any third person regarding infringement + * or the like. Any license provided herein, whether implied or + * otherwise, applies only to this software file. Patent licenses, if + * any, provided herein do not apply to combinations of this program with + * other software, or any other product whatsoever. + * + * You should have received a copy of the GNU General Public License along + * with this program; if not, write the Free Software Foundation, Inc., 59 + * Temple Place - Suite 330, Boston MA 02111-1307, USA. + * + * Contact information: Silicon Graphics, Inc., 1600 Amphitheatre Pkwy, + * Mountain View, CA 94043, or: + * + * http://www.sgi.com + * + * For further information regarding this notice, see: + * + * http://oss.sgi.com/projects/GenInfo/SGIGPLNoticeExplan/ + */ +#ifndef __XFS_EXT2_IOCTL_H__ +#define __XFS_EXT2_IOCTL_H__ + +/* ext2 ioctls (EXT2_IOC_GETFLAGS and EXT2_IOC_SETFLAGS) to support + * chattr/lsattr */ +#define XFS_IOC_EXT2_GETFLAGS _IOR('f', 1, long) +#define XFS_IOC_EXT2_SETFLAGS _IOW('f', 2, long) + +#define EXT2_FLAG_SYNC 0x00000008 /* Synchronous updates */ +#define EXT2_FLAG_IMMUTABLE 0x00000010 /* Immutable file */ +#define EXT2_FLAG_APPEND 0x00000020 /* writes to file may only append */ +#define EXT2_FLAG_NOATIME 0x00000080 /* do not update atime */ + +#endif /* __XFS_EXT2_IOCTL_H__ */ diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ioctl.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_ioctl.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_ioctl.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_ioctl.c Sun Jun 8 22:33:34 2003 @@ -66,6 +66,7 @@ #include "xfs_utils.h" #include "xfs_dfrag.h" #include "xfs_fsops.h" +#include "xfs_ext2_ioctl.h" #include #include @@ -327,6 +328,13 @@ if (permflag & O_TRUNC) permflag |= 2; + if ((!(permflag & O_APPEND) || (permflag & O_TRUNC)) && + (permflag & FMODE_WRITE) && IS_APPEND(inode)) + return -XFS_ERROR(EPERM); + + if ((permflag & FMODE_WRITE) && IS_IMMUTABLE(inode)) + return -XFS_ERROR(EACCES); + /* Can't write directories. */ if ( S_ISDIR(inode->i_mode) && (permflag & FMODE_WRITE)) { iput(inode); @@ -447,6 +455,9 @@ if (error) return -error; + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) + return -XFS_ERROR(EPERM); + if (copy_from_user(&fsd, dmhreq.data, sizeof(fsd))) { VN_RELE(vp); return -XFS_ERROR(EFAULT); @@ -532,11 +543,21 @@ NULL, ops[i].am_error); break; case ATTR_OP_SET: + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) { + kfree(ops); + VN_RELE(vp); + return -XFS_ERROR(EPERM); + } VOP_ATTR_SET(vp,ops[i].am_attrname, ops[i].am_attrvalue, ops[i].am_length, ops[i].am_flags, NULL, ops[i].am_error); break; case ATTR_OP_REMOVE: + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) { + kfree(ops); + VN_RELE(vp); + return -XFS_ERROR(EPERM); + } VOP_ATTR_REMOVE(vp, ops[i].am_attrname, ops[i].am_flags, NULL, ops[i].am_error); break; @@ -842,6 +863,75 @@ error = xfs_errortag_clearall(mp); return -error; + case XFS_IOC_EXT2_GETFLAGS: { + unsigned int flags = 0; + + if (vp->v_inode.i_flags & S_IMMUTABLE) + flags |= EXT2_FLAG_IMMUTABLE; /* EXT2_IMMUTABLE_FL */ + if (vp->v_inode.i_flags & S_APPEND) + flags |= EXT2_FLAG_APPEND; /* EXT2_APPEND_FL */ + if (vp->v_inode.i_flags & S_SYNC) + flags |= EXT2_FLAG_SYNC; /* EXT2_SYNC_FL */ + if (vp->v_inode.i_flags & S_NOATIME) + flags |= EXT2_FLAG_NOATIME; /* EXT2_NOATIME_FL */ + + if (copy_to_user((unsigned int *)arg, &flags, sizeof(flags))) + return -XFS_ERROR(EFAULT); + return 0; + } + + case XFS_IOC_EXT2_SETFLAGS: { + vattr_t va; + unsigned int flags; + int attr_flags = 0; + + if (copy_from_user(&flags, (unsigned int *)arg, sizeof(flags))) + return -XFS_ERROR(EFAULT); + + /* we need to do getattr to preserve XFS xflags ext2 + * has no knowledge of */ + + va.va_mask = XFS_AT_XFLAGS; + VOP_GETATTR(vp, &va, 0, NULL, error); + if (error) + return -error; + + if (flags & (EXT2_FLAG_IMMUTABLE|EXT2_FLAG_APPEND) || + va.va_xflags & (XFS_XFLAG_IMMUTABLE|XFS_XFLAG_APPEND)) + if (!capable(CAP_LINUX_IMMUTABLE)) + return -XFS_ERROR(EPERM); + + /* don't silently ignore unsupported ext2 flags */ + if (flags & ~(EXT2_FLAG_IMMUTABLE|EXT2_FLAG_APPEND| + EXT2_FLAG_SYNC|EXT2_FLAG_NOATIME)) + return -XFS_ERROR(EOPNOTSUPP); + + if (flags & EXT2_FLAG_IMMUTABLE) /* EXT2_IMMUTABLE_FL */ + va.va_xflags |= XFS_XFLAG_IMMUTABLE; + else + va.va_xflags &= ~XFS_XFLAG_IMMUTABLE; + if (flags & EXT2_FLAG_APPEND) /* EXT2_APPEND_FL */ + va.va_xflags |= XFS_XFLAG_APPEND; + else + va.va_xflags &= ~XFS_XFLAG_APPEND; + if (flags & EXT2_FLAG_SYNC) /* EXT2_SYNC_FL */ + va.va_xflags |= XFS_XFLAG_SYNC; + else + va.va_xflags &= ~XFS_XFLAG_SYNC; + if (flags & EXT2_FLAG_NOATIME) /* EXT2_NOATIME_FL */ + va.va_xflags |= XFS_XFLAG_NOATIME; + else + va.va_xflags &= ~XFS_XFLAG_NOATIME; + + if (filp->f_flags & (O_NDELAY|O_NONBLOCK)) + attr_flags |= ATTR_NONBLOCK; + + VOP_SETATTR(vp, &va, attr_flags, NULL, error); + if (!error) + vn_revalidate(vp); /* push immutable/append flags into vfs inode */ + return -error; + } + default: return -ENOTTY; } @@ -859,6 +949,9 @@ int attr_flags = 0; int error; + if (vp->v_inode.i_flags & (S_IMMUTABLE|S_APPEND)) + return -XFS_ERROR(EPERM); + if (filp->f_flags & O_RDONLY) return -XFS_ERROR(EBADF); @@ -1012,6 +1105,11 @@ if (copy_from_user(&fa, (struct fsxattr *)arg, sizeof(fa))) return -XFS_ERROR(EFAULT); + if (fa.fsx_xflags & (XFS_XFLAG_IMMUTABLE|XFS_XFLAG_APPEND) || + va.va_xflags & (XFS_XFLAG_IMMUTABLE|XFS_XFLAG_APPEND)) + if (!capable(CAP_LINUX_IMMUTABLE)) + return -XFS_ERROR(EPERM); + va.va_mask = XFS_AT_XFLAGS | XFS_AT_EXTSIZE; va.va_xflags = fa.fsx_xflags; va.va_extsize = fa.fsx_extsize; @@ -1020,6 +1118,8 @@ attr_flags |= ATTR_NONBLOCK; VOP_SETATTR(vp, &va, attr_flags, NULL, error); + if (!error) + vn_revalidate(vp); /* push immutable/append flags into vfs inode */ return -error; } diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_iops.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_iops.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_iops.c Thu May 1 13:05:53 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_iops.c Fri Jun 6 03:22:27 2003 @@ -615,6 +615,9 @@ return error; } + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) + return -EPERM; + /* Convert Linux syscall to XFS internal ATTR flags */ if (flags & XATTR_CREATE) xflags |= ATTR_CREATE; @@ -764,6 +767,9 @@ error = xfs_cap_vremove(vp); return error; } + + if (IS_IMMUTABLE(inode) || IS_APPEND(inode)) + return -EPERM; if (strncmp(name, xfs_namespaces[ROOT_NAMES].name, xfs_namespaces[ROOT_NAMES].namelen) == 0) { diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_super.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_super.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_super.c Mon Jun 2 07:34:46 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_super.c Fri Jun 6 03:22:27 2003 @@ -147,6 +147,22 @@ inode->i_atime = ip->i_d.di_atime.t_sec; inode->i_mtime = ip->i_d.di_mtime.t_sec; inode->i_ctime = ip->i_d.di_ctime.t_sec; + if (ip->i_d.di_flags & XFS_DIFLAG_IMMUTABLE) + inode->i_flags |= S_IMMUTABLE; + else + inode->i_flags &= ~S_IMMUTABLE; + if (ip->i_d.di_flags & XFS_DIFLAG_APPEND) + inode->i_flags |= S_APPEND; + else + inode->i_flags &= ~S_APPEND; + if (ip->i_d.di_flags & XFS_DIFLAG_SYNC) + inode->i_flags |= S_SYNC; + else + inode->i_flags &= ~S_SYNC; + if (ip->i_d.di_flags & XFS_DIFLAG_NOATIME) + inode->i_flags |= S_NOATIME; + else + inode->i_flags &= ~S_NOATIME; vp->v_flag &= ~VMODIFIED; } diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_vnode.c linux-2.4-xfs/linux/fs/xfs/linux/xfs_vnode.c --- linux-2.4-xfs.orig/linux/fs/xfs/linux/xfs_vnode.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/linux/xfs_vnode.c Fri Jun 6 03:22:27 2003 @@ -224,6 +224,23 @@ inode->i_mtime = va.va_mtime.tv_sec; inode->i_ctime = va.va_ctime.tv_sec; inode->i_atime = va.va_atime.tv_sec; + if (va.va_xflags & XFS_XFLAG_IMMUTABLE) + inode->i_flags |= S_IMMUTABLE; + else + inode->i_flags &= ~S_IMMUTABLE; + if (va.va_xflags & XFS_XFLAG_APPEND) + inode->i_flags |= S_APPEND; + else + inode->i_flags &= ~S_APPEND; + if (va.va_xflags & XFS_XFLAG_SYNC) + inode->i_flags |= S_SYNC; + else + inode->i_flags &= ~S_SYNC; + if (va.va_xflags & XFS_XFLAG_NOATIME) + inode->i_flags |= S_NOATIME; + else + inode->i_flags &= ~S_NOATIME; + VUNMODIFY(vp); } return -error; diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_acl.c linux-2.4-xfs/linux/fs/xfs/xfs_acl.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_acl.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_acl.c Fri Jun 6 03:22:27 2003 @@ -388,6 +388,8 @@ vattr_t va; int error; + if (vp->v_inode.i_flags & (S_IMMUTABLE|S_APPEND)) + return EPERM; if (kind == _ACL_TYPE_DEFAULT && vp->v_type != VDIR) return ENOTDIR; if (vp->v_vfsp->vfs_flag & VFS_RDONLY) diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_cap.c linux-2.4-xfs/linux/fs/xfs/xfs_cap.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_cap.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_cap.c Fri Jun 6 04:24:17 2003 @@ -192,6 +192,8 @@ if (vp->v_vfsp->vfs_flag & VFS_RDONLY) return EROFS; + if (vp->v_inode.i_flags & (S_IMMUTABLE|S_APPEND)) + return EPERM; if ((error = _MAC_VACCESS(vp, NULL, VWRITE))) return error; va.va_mask = XFS_AT_UID; diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_dinode.h linux-2.4-xfs/linux/fs/xfs/xfs_dinode.h --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_dinode.h Tue Apr 15 15:16:46 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_dinode.h Fri Jun 6 03:59:35 2003 @@ -468,13 +468,23 @@ * There should be a one-to-one correspondence between these flags and the * XFS_XFLAG_s. */ -#define XFS_DIFLAG_REALTIME_BIT 0 /* file's blocks come from rt area */ -#define XFS_DIFLAG_PREALLOC_BIT 1 /* file space has been preallocated */ -#define XFS_DIFLAG_NEWRTBM_BIT 2 /* for rtbitmap inode, new format */ -#define XFS_DIFLAG_REALTIME (1 << XFS_DIFLAG_REALTIME_BIT) -#define XFS_DIFLAG_PREALLOC (1 << XFS_DIFLAG_PREALLOC_BIT) -#define XFS_DIFLAG_NEWRTBM (1 << XFS_DIFLAG_NEWRTBM_BIT) +#define XFS_DIFLAG_REALTIME_BIT 0 /* file's blocks come from rt area */ +#define XFS_DIFLAG_PREALLOC_BIT 1 /* file space has been preallocated */ +#define XFS_DIFLAG_NEWRTBM_BIT 2 /* for rtbitmap inode, new format */ +#define XFS_DIFLAG_IMMUTABLE_BIT 3 /* inode is immutable */ +#define XFS_DIFLAG_APPEND_BIT 4 /* inode is append-only */ +#define XFS_DIFLAG_SYNC_BIT 5 /* inode is written synchronously */ +#define XFS_DIFLAG_NOATIME_BIT 6 /* do not update atime */ +#define XFS_DIFLAG_REALTIME (1 << XFS_DIFLAG_REALTIME_BIT) +#define XFS_DIFLAG_PREALLOC (1 << XFS_DIFLAG_PREALLOC_BIT) +#define XFS_DIFLAG_NEWRTBM (1 << XFS_DIFLAG_NEWRTBM_BIT) +#define XFS_DIFLAG_IMMUTABLE (1 << XFS_DIFLAG_IMMUTABLE_BIT) +#define XFS_DIFLAG_APPEND (1 << XFS_DIFLAG_APPEND_BIT) +#define XFS_DIFLAG_SYNC (1 << XFS_DIFLAG_SYNC_BIT) +#define XFS_DIFLAG_NOATIME (1 << XFS_DIFLAG_NOATIME_BIT) #define XFS_DIFLAG_ALL \ - (XFS_DIFLAG_REALTIME|XFS_DIFLAG_PREALLOC|XFS_DIFLAG_NEWRTBM) + (XFS_DIFLAG_REALTIME|XFS_DIFLAG_PREALLOC|XFS_DIFLAG_NEWRTBM| \ + XFS_DIFLAG_IMMUTABLE|XFS_DIFLAG_APPEND|XFS_DIFLAG_SYNC| \ + XFS_DIFLAG_NOATIME) #endif /* __XFS_DINODE_H__ */ diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_fs.h linux-2.4-xfs/linux/fs/xfs/xfs_fs.h --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_fs.h Sun Mar 30 18:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_fs.h Fri Jun 6 03:22:27 2003 @@ -71,9 +71,14 @@ */ #define XFS_XFLAG_REALTIME 0x00000001 #define XFS_XFLAG_PREALLOC 0x00000002 +#define XFS_XFLAG_IMMUTABLE 0x00000008 +#define XFS_XFLAG_APPEND 0x00000010 +#define XFS_XFLAG_SYNC 0x00000020 +#define XFS_XFLAG_NOATIME 0x00000040 #define XFS_XFLAG_HASATTR 0x80000000 /* no DIFLAG for this */ #define XFS_XFLAG_ALL \ - ( XFS_XFLAG_REALTIME|XFS_XFLAG_PREALLOC|XFS_XFLAG_HASATTR ) + ( XFS_XFLAG_REALTIME|XFS_XFLAG_PREALLOC|XFS_XFLAG_IMMUTABLE| \ + XFS_XFLAG_APPEND|XFS_XFLAG_SYNC|XFS_XFLAG_NOATIME|XFS_XFLAG_HASATTR ) /* diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_inode.c linux-2.4-xfs/linux/fs/xfs/xfs_inode.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_inode.c Wed May 21 17:07:13 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_inode.c Fri Jun 6 03:22:27 2003 @@ -3485,6 +3485,9 @@ if (IS_RDONLY(inode) && (S_ISREG(imode) || S_ISDIR(imode) || S_ISLNK(imode))) return XFS_ERROR(EROFS); + + if (IS_IMMUTABLE(inode)) + return XFS_ERROR(EACCES); } /* @@ -3608,7 +3611,7 @@ * Don't update access timestamps on reads if mounted "noatime" * Throw it away if anyone asks us. */ - if (ip->i_mount->m_flags & XFS_MOUNT_NOATIME && + if ((ip->i_mount->m_flags & XFS_MOUNT_NOATIME || IS_NOATIME(inode)) && ((flags & (XFS_ICHGTIME_ACC|XFS_ICHGTIME_MOD|XFS_ICHGTIME_CHG)) == XFS_ICHGTIME_ACC)) return; diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_itable.c linux-2.4-xfs/linux/fs/xfs/xfs_itable.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_itable.c Thu May 1 08:22:06 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_itable.c Fri Jun 6 03:22:27 2003 @@ -163,6 +163,14 @@ XFS_XFLAG_REALTIME : 0) | ((di_flags & XFS_DIFLAG_PREALLOC) ? XFS_XFLAG_PREALLOC : 0) | + ((di_flags & XFS_DIFLAG_IMMUTABLE) ? + XFS_XFLAG_IMMUTABLE : 0) | + ((di_flags & XFS_DIFLAG_APPEND) ? + XFS_XFLAG_APPEND : 0) | + ((di_flags & XFS_DIFLAG_SYNC) ? + XFS_XFLAG_SYNC : 0) | + ((di_flags & XFS_DIFLAG_NOATIME) ? + XFS_XFLAG_NOATIME : 0) | (XFS_CFORK_Q_ARCH(dic, arch) ? XFS_XFLAG_HASATTR : 0); diff -urN -x CVS -x xfs_log.c linux-2.4-xfs.orig/linux/fs/xfs/xfs_vnodeops.c linux-2.4-xfs/linux/fs/xfs/xfs_vnodeops.c --- linux-2.4-xfs.orig/linux/fs/xfs/xfs_vnodeops.c Tue May 6 12:53:19 2003 +++ linux-2.4-xfs/linux/fs/xfs/xfs_vnodeops.c Fri Jun 6 04:02:57 2003 @@ -266,6 +266,14 @@ XFS_XFLAG_REALTIME : 0) | ((ip->i_d.di_flags & XFS_DIFLAG_PREALLOC) ? XFS_XFLAG_PREALLOC : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_IMMUTABLE) ? + XFS_XFLAG_IMMUTABLE : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_APPEND) ? + XFS_XFLAG_APPEND : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_SYNC) ? + XFS_XFLAG_SYNC : 0) | + ((ip->i_d.di_flags & XFS_DIFLAG_NOATIME) ? + XFS_XFLAG_NOATIME : 0) | (XFS_IFORK_Q(ip) ? XFS_XFLAG_HASATTR : 0); vap->va_extsize = ip->i_d.di_extsize << mp->m_sb.sb_blocklog; @@ -829,6 +837,14 @@ ip->i_d.di_flags |= XFS_DIFLAG_REALTIME; ip->i_iocore.io_flags |= XFS_IOCORE_RT; } + if (vap->va_xflags & XFS_XFLAG_IMMUTABLE) + ip->i_d.di_flags |= XFS_DIFLAG_IMMUTABLE; + if (vap->va_xflags & XFS_XFLAG_APPEND) + ip->i_d.di_flags |= XFS_DIFLAG_APPEND; + if (vap->va_xflags & XFS_XFLAG_SYNC) + ip->i_d.di_flags |= XFS_DIFLAG_SYNC; + if (vap->va_xflags & XFS_XFLAG_NOATIME) + ip->i_d.di_flags |= XFS_DIFLAG_NOATIME; /* can't set PREALLOC this way, just ignore it */ } xfs_trans_log_inode(tp, ip, XFS_ILOG_CORE); --r5Pyd7+fXNt84Ff3-- From owner-linux-xfs@oss.sgi.com Mon Jun 9 00:44:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 00:44:51 -0700 (PDT) Received: from goliath.sylaba.poznan.pl (root@goliath.sylaba.poznan.pl [195.216.104.3]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h597ij2x007966 for ; Mon, 9 Jun 2003 00:44:46 -0700 Received: from goliath.sylaba.poznan.pl (smmsp@localhost.sylaba.poznan.pl [127.0.0.1]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h597ifDF002554 for ; Mon, 9 Jun 2003 09:44:41 +0200 (CEST) Received: by goliath.sylaba.poznan.pl (8.12.8/8.12.8/Submit) id h597ifJS002553 for linux-xfs@oss.sgi.com.KAV; Mon, 9 Jun 2003 09:44:41 +0200 (CEST) Received: from venus.local.navi.pl (ps103.poznan.sdi.tpnet.pl [217.97.72.103]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h597ieDF002545; Mon, 9 Jun 2003 09:44:40 +0200 (CEST) Received: from venus.local.navi.pl (venus.local.navi.pl [127.0.0.1]) by venus.local.navi.pl (8.12.5/8.12.5) with ESMTP id h597komT002134; Mon, 9 Jun 2003 09:46:50 +0200 Subject: Re: How to monitor access/modification of files on XFS? From: Olaf =?iso-8859-2?Q?Fr=B1czyk?= To: Jon Morgan Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain; charset=UTF-8 X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 09 Jun 2003 09:46:49 +0200 Message-Id: <1055144810.1695.18.camel@venus> Mime-Version: 1.0 X-MIME-Autoconverted: from quoted-printable to 8bit by goliath.sylaba.poznan.pl id h597ieDF002545 X-MIME-Autoconverted: from 8bit to quoted-printable by goliath.sylaba.poznan.pl id h597ifDF002554 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h597il2x007967 X-archive-position: 4251 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: olaf@cbk.poznan.pl Precedence: bulk X-list: linux-xfs Hi, It is useful to monitor particular files or directories. It doesn't monitor subdirectories. So it is not useful for monitoring the whole filesystem. Is there any way to do it? Regards, Olaf Fraczyk On Fri, 2003-06-06 at 16:43, Jon Morgan wrote: > > Take a look at http://oss.sgi.com/projects/fam/ > > ----------------------------------- > Jon Morgan > > On 6 Jun 2003, Olaf [iso-8859-2] Fr±czyk wrote: > > > Hi, > > > > I need to monitor access to XFS filesystem: > > file and directory: > > creation/modification/delete/rename/rights change > > with user names and time stamp. > > Is such possibility in kernel/XFS fs code (for 2.4 kernels)? > > > > Regards, > > > > Olaf Fraczyk > > > > > > > > > > > > > > > > From owner-linux-xfs@oss.sgi.com Mon Jun 9 02:45:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 02:45:40 -0700 (PDT) Received: from mail.aspec.ru (mail.aspec.ru [217.14.198.4]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h599jI2x018722 for ; Mon, 9 Jun 2003 02:45:20 -0700 Received: from [192.168.22.229] (HELO belkam.com) by mail.aspec.ru (CommuniGate Pro SMTP 4.0.6) with ESMTP id 1512248 for linux-xfs@oss.sgi.com; Mon, 09 Jun 2003 14:45:11 +0500 Message-ID: <3EE456CD.7040703@belkam.com> Date: Mon, 09 Jun 2003 14:43:41 +0500 From: Dmitry Melekhov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314 X-Accept-Language: ru, en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: tape backup tool ? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4252 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dm@belkam.com Precedence: bulk X-list: linux-xfs Hello! We run xfs on our backup server, and I want to store ACLs to tape too. I decided to use star, because it supports ACLs and it allows to restore single file. I wrote backup to tape with following command: /usr/bin/star c --file=/dev/st0 -acl -H=exustar ./ But when I try to restore sometimes star can restore acls: backup:/BACKUP/test # star -x -acl -H=exustar --file=/dev/st0 star: current './' newer. star: Invalid argument. Cannot set ACL 'user::rwx,group::rwx,group:belbank:rwx #effective,mask::r-x,other::---' for 'apps/belbank/BACKUP/client/'. star: Invalid argument. Cannot set ACL 'user::rwx,group::rwx,group:belbank:rwx #effective,mask::r-x,other::---' for 'apps/belbank/BACKUP/client/1/'. Any ideas? Or, may be, someone knows better tool for tape backup? Thank you! From owner-linux-xfs@oss.sgi.com Mon Jun 9 02:52:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 02:52:31 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h599qS2x019490 for ; Mon, 9 Jun 2003 02:52:29 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 1290D1451F; Mon, 9 Jun 2003 11:52:23 +0200 (MEST) Date: Mon, 9 Jun 2003 11:52:22 +0200 From: Andi Kleen To: Dmitry Melekhov Cc: linux-xfs@oss.sgi.com Subject: Re: tape backup tool ? Message-ID: <20030609095222.GA6057@wotan.suse.de> References: <3EE456CD.7040703@belkam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE456CD.7040703@belkam.com> X-archive-position: 4253 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs > Or, may be, someone knows better tool for tape backup? xfsdump perhaps? -Andi From owner-linux-xfs@oss.sgi.com Mon Jun 9 06:59:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 06:59:13 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h59Dx52x029641 for ; Mon, 9 Jun 2003 06:59:06 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h59EFGVe026821 for ; Mon, 9 Jun 2003 09:15:16 -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 h59DwxqX3850960; Mon, 9 Jun 2003 08:58:59 -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 h59DwxYl11719122; Mon, 9 Jun 2003 08:58:59 -0500 (CDT) Date: Mon, 9 Jun 2003 08:58:59 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Knut J Bjuland cc: linux-xfs@oss.sgi.com Subject: Re: error when patching redhat 2.4.20-18.9 with xfs 1.3-pre1 In-Reply-To: <3EE43169.6CE0CF33@online.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4254 X-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 What patch did you use? We have not release a patch for RH 2.4.20-18, but the same patches as are in the 2.4.20-13 SRPM should work just fine. -Eric On Mon, 9 Jun 2003, Knut J Bjuland wrote: > I get this error messeage. > > from :1: > /usr/src/redhat/BUILD/kernel-2.4.20/linux-2.4.20/include/linux/modules/sunrpc_syms.ver:38:1: > warning: this is the location of the previous definition > super.c: In function `read_super_block': > super.c:869: warning: int format, long unsigned int arg (arg 2) > super.c:944:14: warning: multi-line string literals are deprecated > xfs_super.c: In function `syncd': > xfs_super.c:430: structure has no member named `sigmask_lock' > xfs_super.c:432: too many arguments to function > `recalc_sigpending_Rfb6af58d' > make[3]: *** [xfs_super.o] Error 1 > make[2]: *** [_modsubdir_linux] Error 2 > make[1]: *** [_modsubdir_xfs] Error 2 > make: *** [_mod_fs] Error 2 > + exit 1 > > > From owner-linux-xfs@oss.sgi.com Mon Jun 9 10:26:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 10:27:06 -0700 (PDT) Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h59HQg2x008238 for ; Mon, 9 Jun 2003 10:26:43 -0700 Received: from pcitadc13.cern.ch (pcitadc13.cern.ch [137.138.34.18]) by smtp3.cern.ch (8.12.1/8.12.1) with ESMTP id h59H1jWU024847; Mon, 9 Jun 2003 19:01:46 +0200 (MET DST) Received: by pcitadc13.cern.ch (Postfix, from userid 32266) id 927F0BC95; Mon, 9 Jun 2003 19:01:48 +0200 (CEST) Date: Mon, 9 Jun 2003 19:01:48 +0200 From: KELEMEN Peter To: linux-xfs@oss.sgi.com Cc: Peter.Kelemen@cern.ch Subject: [2.4.21-rc7-ac1] internal XFS error in QA 013 Message-ID: <20030609190148.A24226@pcitadc13.cern.ch> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="M9NhX3UHpAaciwkO" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i 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 X-archive-position: 4255 X-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 --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by smtp3.cern.ch id h59H1jWU024847 Hello, Under RedHat 7.3 with latest userspace RPMs compiled, QA 013 triggers an internal XFS error in xfs_inode.c:415 xfs_itobp(). Messages printed by a CONFIG_XFS_DEBUG enabled kernel are attached, so are the ksymoops-processed call traces of 013 failure. Additionally, debug messages printed during 017 and 049 are attached as well. gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) Peter --=20 .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen P=E9ter / \ / \ Peter.Kelemen@cern.ch .+' `+...+' `+...+' `+...+' `+...+' --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="013.debug" Filesystem "ide0(3,11)": xfs_dilocate: agno (458) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (328) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (418) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (193) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (63) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (88) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (261) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (409) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (214) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (391) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (434) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (44) >= mp->m_sb.sb_agcount (28) XFS: device 0x30b- bad inode magic/vsn daddr 0x29450c0 #0 (magic=bcf2) 0x0: bc f2 69 c6 9c d0 55 e7 40 6e f7 bc 3a 7c 82 00 Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d cf6d3ba8 cf6d3c64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 029450c0 00000000 00000000 0000bcf2 029450d0 00000000 00000003 00000001 029450c0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Filesystem "ide0(3,11)": xfs_dilocate: agno (71) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (204) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (452) >= mp->m_sb.sb_agcount (28) XFS mounting filesystem ide0(3,11) Filesystem "ide0(3,11)": xfs_dilocate: agno (289) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (60) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (430) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (361) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (227) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (405) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (372) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (207) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (89) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (429) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (391) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (427) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (404) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (117) >= mp->m_sb.sb_agcount (28) XFS: device 0x30b- bad inode magic/vsn daddr 0x4b9d60 #0 (magic=0) 0x0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d c458fba8 c458fc64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 004b9d60 00000000 00000000 00000000 004b9d70 00000000 00000003 00000001 004b9d60 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Filesystem "ide0(3,11)": xfs_dilocate: agno (68) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (186) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (136) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (470) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (263) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (118) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (126) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (368) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (496) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (245) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (188) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (95) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (166) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (439) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (489) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (320) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (98) >= mp->m_sb.sb_agcount (28) XFS: device 0x30b- bad inode magic/vsn daddr 0x60efe0 #0 (magic=db04) 0x0: db 04 24 83 c4 f4 db 3c 24 9b 8b c3 e8 4f fd ff Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d cb649ba8 cb649c64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 0060efe0 00000000 00000000 0000db04 0060eff0 00000000 00000003 00000001 0060efe0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] XFS: device 0x30b- bad inode magic/vsn daddr 0x2f4d430 #0 (magic=8e02) 0x0: 8e 02 d6 a0 1e e0 fa 01 9d 82 f2 62 4f 11 63 89 Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d c458fba8 c458fc64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 02f4d430 00000000 00000000 00008e02 02f4d440 00000000 00000003 00000001 02f4d430 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Filesystem "ide0(3,11)": xfs_dilocate: agno (108) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (266) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (442) >= mp->m_sb.sb_agcount (28) XFS mounting filesystem ide0(3,11) XFS mounting filesystem ide0(3,10) XFS mounting filesystem ide0(3,11) XFS mounting filesystem ide0(3,10) XFS mounting filesystem ide0(3,10) XFS mounting filesystem ide0(3,11) XFS mounting filesystem ide0(3,10) XFS mounting filesystem ide0(3,11) Filesystem "ide0(3,11)": xfs_dilocate: agno (245) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (326) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (375) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (269) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (129) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (355) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (301) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (207) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (305) >= mp->m_sb.sb_agcount (28) XFS mounting filesystem ide0(3,11) Filesystem "ide0(3,11)": xfs_dilocate: agno (196) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (441) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (408) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (269) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (76) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (455) >= mp->m_sb.sb_agcount (28) XFS: device 0x30b- bad inode magic/vsn daddr 0x275b0f0 #0 (magic=8057) 0x0: 80 57 44 1c 39 23 3c 35 a7 e2 ab 48 48 cb 2d ea Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d cb443ba8 cb443c64 d2cb90ac d2cffb4f 00000001 c93e7000 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 0275b0f0 00000000 00000000 00008057 0275b100 00000000 00000003 00000001 0275b0f0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Filesystem "ide0(3,11)": xfs_dilocate: agno (400) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (57) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (503) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (293) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (67) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (359) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (353) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (288) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (111) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (334) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (326) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (443) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (418) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (186) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (38) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (227) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (281) >= mp->m_sb.sb_agcount (28) XFS: device 0x30b- bad inode magic/vsn daddr 0x23d3020 #0 (magic=206f) 0x0: 20 6f 66 20 35 31 32 20 62 79 74 65 20 75 6e 69 Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d cb443ba8 cb443c64 d2cb90ac d2cffb4f 00000001 c93e7000 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 023d3020 00000000 00000000 0000206f 023d3030 00000000 00000003 00000001 023d3020 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Filesystem "ide0(3,11)": xfs_dilocate: agno (57) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (446) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (170) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (490) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (376) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (242) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (282) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (348) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (371) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (28) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (289) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (427) >= mp->m_sb.sb_agcount (28) XFS: device 0x30b- bad inode magic/vsn daddr 0x33863b0 #0 (magic=6de9) 0x0: 6d e9 e6 a9 6b 03 16 9b e9 08 84 6d 3e 90 19 a8 Filesystem "ide0(3,11)": XFS internal error xfs_itobp at line 415 of file xfs_inode.c. Caller 0xd2cba74d ccad3ba8 ccad3c64 d2cb90ac d2cffb4f 00000001 c93e7000 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 033863b0 00000000 00000000 00006de9 033863c0 00000000 00000003 00000001 033863b0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Filesystem "ide0(3,11)": xfs_dilocate: agno (387) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (189) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (506) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (171) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (161) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (365) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (235) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (254) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (296) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (322) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (482) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (116) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (306) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (489) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (422) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (457) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (346) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (43) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (202) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (314) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (122) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (234) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (461) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (441) >= mp->m_sb.sb_agcount (28) Filesystem "ide0(3,11)": xfs_dilocate: agno (397) >= mp->m_sb.sb_agcount (28) --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k1 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal cf6d3ba8 cf6d3c64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 029450c0 00000000 00000000 0000bcf2 029450d0 00000000 00000003 00000001 029450c0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2cff62b <[xfs].rodata.end+168c/24dc1> Trace; d2cff61c <[xfs].rodata.end+167d/24dc1> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; c013e221 Trace; d2ceba69 <[xfs]validate_fields+29/50> Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; d2cebc6b <[xfs]linvfs_mkdir+1b/20> Trace; c0134029 Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k2 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal c458fba8 c458fc64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 004b9d60 00000000 00000000 00000000 004b9d70 00000000 00000003 00000001 004b9d60 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2cc3db8 <[xfs]xlog_write+348/550> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; c013e221 Trace; d2cec33c <[xfs]linvfs_setattr+19c/1b0> Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; c01330a5 Trace; c0134029 Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k3 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal cb649ba8 cb649c64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 0060efe0 00000000 00000000 0000db04 0060eff0 00000000 00000003 00000001 0060efe0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2cd586f <[xfs]xfs_trans_tail_ail+f/30> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; c013e221 Trace; d2cabcc9 <[xfs]xfs_dir2_sf_getdents+3b9/420> Trace; d2caba77 <[xfs]xfs_dir2_sf_getdents+167/420> Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; c0134029 Trace; c01418ac Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k4 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal c458fba8 c458fc64 d2cb90ac d2cffb4f 00000001 c93e7400 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 02f4d430 00000000 00000000 00008e02 02f4d440 00000000 00000003 00000001 02f4d430 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2cc3db8 <[xfs]xlog_write+348/550> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; c013e221 Trace; d2cec33c <[xfs]linvfs_setattr+19c/1b0> Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; c01330a5 Trace; c0134029 Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k5 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal cb443ba8 cb443c64 d2cb90ac d2cffb4f 00000001 c93e7000 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 0275b0f0 00000000 00000000 00008057 0275b100 00000000 00000003 00000001 0275b0f0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; d2cc2943 <[xfs]xlog_assign_tail_lsn+13/30> Trace; d2cc5082 <[xfs]xlog_state_release_iclog+22/120> Trace; d2cc2027 <[xfs]xfs_log_release_iclog+17/50> Trace; d2cd5142 <[xfs]xfs_trans_commit+382/3f0> Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; d2cde198 <[xfs]xfs_release+c8/100> Trace; c0134029 Trace; d2ce836a <[xfs]linvfs_release+1a/30> Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k6 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal cb443ba8 cb443c64 d2cb90ac d2cffb4f 00000001 c93e7000 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 023d3020 00000000 00000000 0000206f 023d3030 00000000 00000003 00000001 023d3020 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2ce52bf <[xfs]_pagebuf_page_io+37f/3b0> Trace; d2ce4f00 <[xfs]_pagebuf_end_io_complete_pages+0/20> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; c0123ce0 Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; d2cd5aa3 <[xfs]xfs_trans_unlocked_item+23/40> Trace; d2cde198 <[xfs]xfs_release+c8/100> Trace; c0134029 Trace; d2ce836a <[xfs]linvfs_release+1a/30> Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=k7 ksymoops 2.4.4 on i686 2.4.21-rc7-ac1-XFSDEBUG. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc7-ac1-XFSDEBUG/ (default) -m /boot/System.map-2.4.21-rc7-ac1-XFSDEBUG (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Reading Oops report from the terminal ccad3ba8 ccad3c64 d2cb90ac d2cffb4f 00000001 c93e7000 d2cffb14 0000019f d2cba74d d2cba74d d2d0cf00 0000030b 033863b0 00000000 00000000 00006de9 033863c0 00000000 00000003 00000001 033863b0 00000000 00000010 00000000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Trace; d2cb90ac <[xfs]xfs_itobp+2fc/340> Trace; d2cffb4f <[xfs].rodata.end+1bb0/24dc1> Trace; d2cffb14 <[xfs].rodata.end+1b75/24dc1> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2d0cf00 <[xfs].rodata.end+ef61/24dc1> Trace; d2cee6f0 <[xfs]linvfs_alloc_inode+0/40> Trace; d2cba74d <[xfs]xfs_iread+7d/1f0> Trace; d2cb7871 <[xfs]xfs_iget_core+181/570> Trace; d2cb7ce6 <[xfs]xfs_iget+86/170> Trace; d2cc0098 <[xfs]xfs_bulkstat_one+e8/580> Trace; d2cc0f87 <[xfs]xfs_bulkstat_single+47/120> Trace; c013e221 Trace; d2cea020 <[xfs]xfs_ioc_bulkstat+190/240> Trace; d2cdd274 <[xfs]xfs_access+34/40> Trace; d2ce9704 <[xfs]xfs_ioctl+344/a00> Trace; c0105866 <__switch_to+66/110> Trace; c013d61e Trace; c013ea1a Trace; c0134029 Trace; d2ce86d6 <[xfs]linvfs_ioctl+46/53> Trace; c0105866 <__switch_to+66/110> Trace; c0105866 <__switch_to+66/110> Trace; c014182e Trace; c0105866 <__switch_to+66/110> Trace; c01342b6 Trace; c0106d7b Trace; c0105866 <__switch_to+66/110> 2 warnings issued. Results may not be reliable. --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="017.debug" Filesystem "ide0(3,10)": xfs_dilocate: agno (2802) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1422) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2360) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3790) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3878) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1622) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2872) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2694) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2112) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1652) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1091) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (877) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3827) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (511) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (4033) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2006) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2544) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1704) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (960) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3400) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2042) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2586) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2151) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1442) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (569) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3678) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agbno (0x7dfd) >= mp->m_sb.sb_agblocks (0x7d81) Filesystem "ide0(3,10)": xfs_dilocate: agno (1500) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3416) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (939) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2159) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2043) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3755) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1601) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (379) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1166) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3105) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1114) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (753) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3063) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3507) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2040) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3311) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1372) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (430) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (823) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1642) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3920) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (213) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (4057) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (3902) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (1138) >= mp->m_sb.sb_agcount (8) Filesystem "ide0(3,10)": xfs_dilocate: agno (2186) >= mp->m_sb.sb_agcount (8) --M9NhX3UHpAaciwkO Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="049.debug" loop: loaded (max 8 devices) XFS mounting filesystem loop(7,0) Filesystem "loop(7,0)": xfs_dilocate: agno (15065) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agno (11678) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x18ad) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (1244) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x1602) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (16158) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x1980) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (1370) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agno (13568) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agno (12817) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x17bf) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (2374) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x1699) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (11831) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x14b5) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (150) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x1ef6) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (5466) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x147c) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (5464) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agno (6160) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agno (16110) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x1df6) >= mp->m_sb.sb_agblocks (0x1400) Filesystem "loop(7,0)": xfs_dilocate: agno (1646) >= mp->m_sb.sb_agcount (1) Filesystem "loop(7,0)": xfs_dilocate: agbno (0x167e) >= mp->m_sb.sb_agblocks (0x1400) --M9NhX3UHpAaciwkO-- From owner-linux-xfs@oss.sgi.com Mon Jun 9 11:20:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 11:20:39 -0700 (PDT) Received: from mxzilla4.xs4all.nl (mxzilla4.xs4all.nl [194.109.6.48]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h59IKO2x010188 for ; Mon, 9 Jun 2003 11:20:25 -0700 Received: from xs1.xs4all.nl (xs1.xs4all.nl [194.109.3.11]) by mxzilla4.xs4all.nl (8.12.3/8.12.3) with ESMTP id h59IKMTC060286 for ; Mon, 9 Jun 2003 20:20:23 +0200 (CEST) Received: from xs1.xs4all.nl (knuffie@localhost.xs4all.nl [127.0.0.1]) by xs1.xs4all.nl (8.12.9/8.11.6) with ESMTP id h59IKMrR086401 for ; Mon, 9 Jun 2003 20:20:22 +0200 (CEST) (envelope-from knuffie@xs1.xs4all.nl) Received: from localhost (Unknown UID 104317@localhost) by xs1.xs4all.nl (8.12.9/8.12.8/Submit) with ESMTP id h59IKM8g086398 for ; Mon, 9 Jun 2003 20:20:22 +0200 (CEST) (envelope-from knuffie@xs1.xs4all.nl) X-Authentication-Warning: xs1.xs4all.nl: Unknown UID 104317 owned process doing -bs Date: Mon, 9 Jun 2003 20:20:22 +0200 (CEST) From: Seth Mos To: linux-xfs@oss.sgi.com Subject: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 Message-ID: <20030609201720.J86243-100000@xs1.xs4all.nl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4256 X-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 Woot! New cannon fodder has just arrived. They compile, not boot tested, few changes. These will need to be recompiled on Red Hat Linux 9 with the posix threading support enabled in the spec file. http://iserv.nl/files/xfs/2.4.20-18/ Get'm while there hot. Cheers Seth From owner-linux-xfs@oss.sgi.com Mon Jun 9 11:50:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 11:50:33 -0700 (PDT) Received: from poptart.bithose.com (ip-204-97-176-41.modem.logical.net [204.97.176.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h59Io92x010941 for ; Mon, 9 Jun 2003 11:50:10 -0700 Received: from poptart.bithose.com (localhost [127.0.0.1]) by poptart.bithose.com (8.12.9/8.12.9) with ESMTP id h59Io8kK121053; Mon, 9 Jun 2003 14:50:08 -0400 (EDT) Received: from localhost (jakari@localhost) by poptart.bithose.com (8.12.9/8.12.9/Submit) with ESMTP id h59Io7tQ098966; Mon, 9 Jun 2003 14:50:07 -0400 (EDT) X-Authentication-Warning: poptart.bithose.com: jakari owned process doing -bs Date: Mon, 9 Jun 2003 14:50:07 -0400 (EDT) From: Jameel Akari To: Seth Mos cc: Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 In-Reply-To: <20030609201720.J86243-100000@xs1.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4257 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jakari@bithose.com Precedence: bulk X-list: linux-xfs On Mon, 9 Jun 2003, Seth Mos wrote: > http://iserv.nl/files/xfs/2.4.20-18/ > New cannon fodder has just arrived. "There was supposed to be an Earth-shattering kaboom!" Nope, it seems to work for me on a mostly normal RH8 box. dmesg below. I'll have to grab the srpm later and play with it.. unless you happened to build the NTFS and UFS fs modules. (I'm testing various backups and restores on this box.. I should probably make sure xfsdump and friends are up to date.) Thanks, -- #!/jameel/akari sleep 4800; make clean && make breakfast She's a runner: Linux version 2.4.20-18.7SGI_XFS_1.2.0 (root@babbel.coltex.nl) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-1 13)) #1 Mon Jun 9 19:33:48 CEST 2003 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000018000000 (usable) BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 384MB LOWMEM available. On node 0 totalpages: 98304 zone(0): 4096 pages. zone(1): 94208 pages. zone(2): 0 pages. Kernel command line: auto BOOT_IMAGE=linux_2.4.20 ro BOOT_FILE=/boot/vmlinuz-2.4.20-18.7SGI_XFS_1.2.0 root=LABEL=/ Initializing CPU#0 Detected 497.843 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 992.87 BogoMIPS Memory: 381960k/393216k available (1578k kernel code, 8692k reserved, 1048k data, 120k init, 0k highmem) Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode cache hash table entries: 32768 (order: 6, 262144 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 512K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 0383f9ff 00000000 00000000 00000000 CPU: Common caps: 0383f9ff 00000000 00000000 00000000 CPU: Intel Pentium III (Katmai) stepping 03 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 PCI: PCI BIOS revision 2.10 entry at 0xedb20, last bus=1 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Using IRQ router PIIX [8086/7110] at 00:14.0 Limiting direct PCI/PCI transfers. 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) Starting kswapd VFS: Disk quotas vdquot_6.5.1 SGI XFS 1.2.0 with ACLs, quota, no debug enabled 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 National Semiconductor PC87306 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 PIIX4: IDE controller at PCI slot 00:14.1 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0x10a0-0x10a7, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0x10a8-0x10af, BIOS settings: hdc:DMA, hdd:pio hda: ST320424A, ATA DISK drive blk: queue c03ecb40, I/O limit 4095Mb (mask 0xffffffff) hdc: Compaq CRD-8322B, 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: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=2586/240/63, UDMA(33) ide-floppy driver 0.99.newide Partition check: hda: hda1 hda2 < hda5 hda6 hda7 hda8 > 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. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 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: 190k freed VFS: Mounted root (ext2 filesystem). SCSI subsystem driver Revision: 1.00 PCI: Found IRQ 11 for device 00:0d.0 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs blk: queue c1fab414, I/O limit 4095Mb (mask 0xffffffff) Vendor: EXABYTE Model: EXB-8505SMBANSH2 Rev: 07T0 Type: Sequential-Access ANSI SCSI revision: 02 blk: queue c1fab814, I/O limit 4095Mb (mask 0xffffffff) Vendor: COMPAQ Model: DLT8000 Rev: 0250 Type: Sequential-Access ANSI SCSI revision: 02 blk: queue c1faba14, I/O limit 4095Mb (mask 0xffffffff) XFS mounting filesystem ide0(3,1) Ending clean XFS mount for filesystem: ide0(3,1) Freeing unused kernel memory: 120k freed usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.275 $ time 19:42:51 Jun 9 2003 usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:14.2 usb-uhci.c: USB UHCI at I/O 0x1080, IRQ 11 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 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: 393080k swap-space (priority 1) XFS mounting filesystem ide0(3,8) Ending clean XFS mount for filesystem: ide0(3,8) XFS mounting filesystem ide0(3,5) Ending clean XFS mount for filesystem: ide0(3,5) XFS mounting filesystem ide0(3,6) Ending clean XFS mount for filesystem: ide0(3,6) st: Version 20030406, bufsize 32768, max init. bufs 4, s/g segs 16 Attached scsi tape st0 at scsi0, channel 0, id 5, lun 0 Attached scsi tape st1 at scsi0, channel 0, id 6, lun 0 parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP] parport0: irq 7 detected ip_tables: (C) 2000-2002 Netfilter core team eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin and others PCI: Found IRQ 11 for device 00:0e.0 divert: allocating divert_blk for eth0 eth0: OEM i82557/i82558 10/100 Ethernet, 00:D0:B7:52:F9:AD, IRQ 11. Board assembly 734938-003, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x04f4518b). From owner-linux-xfs@oss.sgi.com Mon Jun 9 13:15:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 13:16:10 -0700 (PDT) Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h59KFo2x015004 for ; Mon, 9 Jun 2003 13:15:51 -0700 Received: from lxplus088.cern.ch (lxplus088.cern.ch [137.138.4.110]) by smtp3.cern.ch (8.12.1/8.12.1) with ESMTP id h59KFfWU029062 for ; Mon, 9 Jun 2003 22:15:42 +0200 (MET DST) Received: by lxplus088.cern.ch (Postfix, from userid 32266) id A92D01C08D; Mon, 9 Jun 2003 22:15:42 +0200 (CEST) Date: Mon, 9 Jun 2003 22:15:42 +0200 From: Peter Kelemen To: linux-xfs@oss.sgi.com Subject: Re: [2.4.21-rc7-ac1] internal XFS error in QA 013 Message-ID: <20030609201542.GA32683@lxplus088.cern.ch> References: <20030609190148.A24226@pcitadc13.cern.ch> <1055180470.13428.117.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055180470.13428.117.camel@jen.americas.sgi.com> User-Agent: Mutt/1.4i X-archive-position: 4258 X-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 On Mon, Jun 09, 2003 at 12:41:10PM -0500, Steve Lord wrote: Steve, > There is now code in xfs to dump out the locations in the code > where it finds metadata errors. This one is a little bogus in > this case. Thanks for the explanation. Maybe it would be a good idea to propagate this into -ac as more people might run into the same. Peter From owner-linux-xfs@oss.sgi.com Mon Jun 9 21:02:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Jun 2003 21:03:05 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5A42m2x028621 for ; Mon, 9 Jun 2003 21:02:49 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h59HfBE0027759 for ; Mon, 9 Jun 2003 10:41:11 -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 h59HfAqX3877530; Mon, 9 Jun 2003 12:41:10 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h59HfARn103522069; Mon, 9 Jun 2003 12:41:10 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h59HfAY14733; Mon, 9 Jun 2003 12:41:10 -0500 Subject: Re: [2.4.21-rc7-ac1] internal XFS error in QA 013 From: Steve Lord To: KELEMEN Peter Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030609190148.A24226@pcitadc13.cern.ch> References: <20030609190148.A24226@pcitadc13.cern.ch> Content-Type: multipart/mixed; boundary="=-2wCP70RVCq6J71MQoJKd" Organization: Message-Id: <1055180470.13428.117.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 09 Jun 2003 12:41:10 -0500 X-archive-position: 4259 X-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 --=-2wCP70RVCq6J71MQoJKd Content-Type: text/plain Content-Transfer-Encoding: 7bit On Mon, 2003-06-09 at 12:01, KELEMEN Peter wrote: > Hello, > > Under RedHat 7.3 with latest userspace RPMs compiled, QA 013 > triggers an internal XFS error in xfs_inode.c:415 xfs_itobp(). > Messages printed by a CONFIG_XFS_DEBUG enabled kernel are > attached, so are the ksymoops-processed call traces of 013 > failure. > > Additionally, debug messages printed during 017 and 049 are > attached as well. > > gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) > > Peter These messages are not an actual error. These tests feed random values into system calls, and using the bulkstat call it is attempting to read inodes of the disk where there are no inodes. There is now code in xfs to dump out the locations in the code where it finds metadata errors. This one is a little bogus in this case. Try the attached patch which shuts this particular warning up by default. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com --=-2wCP70RVCq6J71MQoJKd Content-Disposition: attachment; filename=inode.patch Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; name=inode.patch; charset=ISO-8859-1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Index: linux/fs/xfs/xfs_inode.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- /usr/tmp/TmpDir.14720-0/linux/fs/xfs/xfs_inode.c_1.375 Mon Jun 9 12:39= :36 2003 +++ linux/fs/xfs/xfs_inode.c Wed May 21 20:55:51 2003 @@ -412,7 +413,7 @@ mp->m_dev, (unsigned long long)imap.im_blkno, i, INT_GET(dip->di_core.di_magic, ARCH_CONVERT)); #endif - XFS_CORRUPTION_ERROR("xfs_itobp", XFS_ERRLEVEL_LOW, + XFS_CORRUPTION_ERROR("xfs_itobp", XFS_ERRLEVEL_HIGH, mp, dip); xfs_trans_brelse(tp, bp); return XFS_ERROR(EFSCORRUPTED); --=-2wCP70RVCq6J71MQoJKd-- From owner-linux-xfs@oss.sgi.com Tue Jun 10 03:53:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 03:54:09 -0700 (PDT) Received: from students.fct.unl.pt ([193.136.120.10]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5AAri2x027232 for ; Tue, 10 Jun 2003 03:53:45 -0700 Received: from localhost (pjsm@localhost) by students.fct.unl.pt (8.11.6/8.11.6) with ESMTP id h5AArMW31488; Tue, 10 Jun 2003 11:53:22 +0100 X-Authentication-Warning: students.fct.unl.pt: pjsm owned process doing -bs Date: Tue, 10 Jun 2003 11:53:22 +0100 (WEST) From: Paulo Matos To: Seth Mos cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 In-Reply-To: <20030609201720.J86243-100000@xs1.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 h5AArMW31488 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5AArm2x027250 X-archive-position: 4260 X-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 On Mon, 9 Jun 2003, Seth Mos wrote: > New cannon fodder has just arrived. > > They compile, not boot tested, few changes. > > These will need to be recompiled on Red Hat Linux 9 with the posix > threading support enabled in the spec file. > > http://iserv.nl/files/xfs/2.4.20-18/ > Hi Seth! Was those built under redhat 7.3 or any other? -- 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 Jun 10 04:41:42 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 04:41:58 -0700 (PDT) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5ABfe2x030752 for ; Tue, 10 Jun 2003 04:41:41 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.28]) by smtpzilla1.xs4all.nl (8.12.9/8.12.9) with ESMTP id h5ABfbBB070583; Tue, 10 Jun 2003 13:41:37 +0200 (CEST) Message-Id: <4.3.2.7.2.20030610133612.0326eba0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Jun 2003 13:41:28 +0200 To: Paulo Matos From: Seth Mos Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <20030609201720.J86243-100000@xs1.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4261 X-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 At 11:53 10-6-2003 +0100, Paulo Matos wrote: >On Mon, 9 Jun 2003, Seth Mos wrote: > > > New cannon fodder has just arrived. > > > > They compile, not boot tested, few changes. > > > > These will need to be recompiled on Red Hat Linux 9 with the posix > > threading support enabled in the spec file. > > > > http://iserv.nl/files/xfs/2.4.20-18/ > > > > Hi Seth! > Was those built under redhat 7.3 or any other? Yes, 7.3 it is. I have no boxes running anything newer. It looks like we will be switching to Red Hat ES pretty soon for the database box which would mean that I can't use the XFS filesystem anymore since it is not covered by the support contract. Some other boxes for which I do not care about the support anyways will keep using XFS. That means I'll probably would need to make some sort of installer for Red Hat ES with XFS support in order to install or upgrade. The biggest problem with ES is the use of the "ancient" 2.4.9 kernel with more patches then you can shake a stick at. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Tue Jun 10 09:10:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 09:10:50 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5AGAU2x011799 for ; Tue, 10 Jun 2003 09:10:30 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5AGQjmO005414 for ; Tue, 10 Jun 2003 11:26:45 -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 h5AGAOqX4020948 for ; Tue, 10 Jun 2003 11:10:24 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5AGAORn112086467 for ; Tue, 10 Jun 2003 11:10:24 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5AGAOW23197; Tue, 10 Jun 2003 11:10:24 -0500 Message-Id: <200306101610.h5AGAOW23197@jen.americas.sgi.com> Date: Tue, 10 Jun 2003 11:10:24 -0500 Subject: TAKE - avoid recovery on root fs during boot To: linux-xfs@oss.sgi.com X-archive-position: 4262 X-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 if we remount the fs readonly, there is no need to put out dummy log records to clear the log as these actually have the effect of dirtying it in a readonly unmount. Date: Tue Jun 10 09:09:42 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: 2.4.x-xfs:slinx:150738a linux/fs/xfs/xfs_log.c - 1.273 - make xlog_need_covered pay attention to the readonly flag. From owner-linux-xfs@oss.sgi.com Tue Jun 10 10:16:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 10:17:00 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5AHGb2x023322 for ; Tue, 10 Jun 2003 10:16:37 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5AHGWE0001433 for ; Tue, 10 Jun 2003 10:16:32 -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 h5AHGVqX4019129 for ; Tue, 10 Jun 2003 12:16:32 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5AHGVRn112751765 for ; Tue, 10 Jun 2003 12:16:31 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5AHGVr25895; Tue, 10 Jun 2003 12:16:31 -0500 Message-Id: <200306101716.h5AHGVr25895@jen.americas.sgi.com> Date: Tue, 10 Jun 2003 12:16:31 -0500 Subject: TAKE - make xfs regression tests less chatty To: linux-xfs@oss.sgi.com X-archive-position: 4263 X-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 make doing an iread from a bad location less chatty by default as some code paths can actually do this and handle the result. Date: Tue Jun 10 10:16:05 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:150747a linux/fs/xfs/xfs_inode.c - 1.376 - turn down the logging level on xfs_iread failures From owner-linux-xfs@oss.sgi.com Tue Jun 10 10:56:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 10:56:26 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5AHuC2x028732 for ; Tue, 10 Jun 2003 10:56:13 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5AICSmO012106 for ; Tue, 10 Jun 2003 13:12:28 -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 h5AHu7qX4030227 for ; Tue, 10 Jun 2003 12:56:07 -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 h5AHu7Rn107082214 for ; Tue, 10 Jun 2003 12:56:07 -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 h5AHu5i9004523 for ; Tue, 10 Jun 2003 12:56:06 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h5AHu58p004521 for linux-xfs@oss.sgi.com; Tue, 10 Jun 2003 12:56:05 -0500 Date: Tue, 10 Jun 2003 12:56:05 -0500 From: Russell Cattelan Message-Id: <200306101756.h5AHu58p004521@chuckle.americas.sgi.com> Subject: TAKE - Merge over a few small fixes X-archive-position: 4264 X-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 Date: Tue Jun 10 10:55:50 PDT 2003 Workarea: chuckle.americas.sgi.com:/go/xfs2/XFS/x2.4-xfs-r1.3 Merged by: cattelan Merged mods: 2.4.x-xfs:slinx:150334a,2.4.x-xfs:slinx:150738a,2.4.x-xfs:slinx:150747a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs-r1.3 Modid: 2.4.x-xfs-r1.3:slinx:150751a linux/fs/xfs/xfs_log.c - 1.273 - Merge of 2.4.x-xfs:slinx:150738a originally by lord on 06/10/03 if we remount the fs readonly, there is no need to put out dummy log records to clear the log as these actually have the effect of dirtying it in a readonly unmount. make xlog_need_covered pay attention to the readonly flag. linux/fs/xfs/xfs_inode.c - 1.376 - Merge of 2.4.x-xfs:slinx:150747a originally by lord on 06/10/03 make doing an iread from a bad location less chatty by default as some code paths can actually do this and handle the result. turn down the logging level on xfs_iread failures linux/fs/xfs/linux/xfs_iops.c - 1.192 - Merge of 2.4.x-xfs:slinx:150334a originally by lord on 06/04/03 Update linux directory inode contents after the initial mkdir, right now size shows up as zero which is wrong. update linux inode fields in a directory after it is created. From owner-linux-xfs@oss.sgi.com Tue Jun 10 17:30:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 17:31:12 -0700 (PDT) Received: from smtp.covadmail.net ([63.65.120.66]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5B0Ur2x014348 for ; Tue, 10 Jun 2003 17:30:54 -0700 Received: (covad.net 6447 invoked from network); 11 Jun 2003 00:30:45 -0000 Received: from unknown (HELO boywonderfx.com) (66.167.1.42) by sun-qmail09 with SMTP; 11 Jun 2003 00:30:45 -0000 Message-ID: <3EE67830.3020506@boywonderfx.com> Date: Tue, 10 Jun 2003 17:30:40 -0700 From: Michael Whang User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS/XP Dual Boot? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4265 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mwhang@boywonderfx.com Precedence: bulk X-list: linux-xfs Has anyone successfully dual booted XFS with windows XP? Please let me know if so and how. Mike From owner-linux-xfs@oss.sgi.com Tue Jun 10 21:00:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 21:01:06 -0700 (PDT) Received: from mail.aspec.ru (mail.aspec.ru [217.14.198.4]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5B40o2x031690 for ; Tue, 10 Jun 2003 21:00:52 -0700 Received: from [192.168.22.229] (HELO belkam.com) by mail.aspec.ru (CommuniGate Pro SMTP 4.0.6) with ESMTP id 1519567 for linux-xfs@oss.sgi.com; Wed, 11 Jun 2003 09:00:43 +0500 Message-ID: <3EE6A90F.9040306@belkam.com> Date: Wed, 11 Jun 2003 08:59:11 +0500 From: Dmitry Melekhov User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314 X-Accept-Language: ru, en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: tape backup tool ? References: <3EE456CD.7040703@belkam.com> <20030609095222.GA6057@wotan.suse.de> In-Reply-To: <20030609095222.GA6057@wotan.suse.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4266 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dm@belkam.com Precedence: bulk X-list: linux-xfs Andi Kleen wrote: >>Or, may be, someone knows better tool for tape backup? > > > xfsdump perhaps? Hmm. Sorry for such stupid question... Is it possible to restore one file from tape with xfsrestore? From owner-linux-xfs@oss.sgi.com Tue Jun 10 22:40:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 22:40:46 -0700 (PDT) Received: from dingdong.cryptoapps.com (postfix@uslink-66.173.43-133.uslink.net [66.173.43.133] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5B5eS2x001798 for ; Tue, 10 Jun 2003 22:40:30 -0700 Received: by dingdong.cryptoapps.com (Postfix, from userid 1001) id 69F9CFB838; Wed, 11 Jun 2003 00:43:08 -0500 (CDT) Date: Wed, 11 Jun 2003 00:43:08 -0500 From: Chris Wedgwood To: Dmitry Melekhov Cc: linux-xfs@oss.sgi.com Subject: Re: tape backup tool ? Message-ID: <20030611054308.GA7800@dingdong.cryptoapps.com> References: <3EE456CD.7040703@belkam.com> <20030609095222.GA6057@wotan.suse.de> <3EE6A90F.9040306@belkam.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE6A90F.9040306@belkam.com> X-archive-position: 4267 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Wed, Jun 11, 2003 at 08:59:11AM +0500, Dmitry Melekhov wrote: > Hmm. Sorry for such stupid question... Is it possible to restore one > file from tape with xfsrestore? You can specify a subtree with -s --cw From owner-linux-xfs@oss.sgi.com Tue Jun 10 22:44:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Jun 2003 22:44:17 -0700 (PDT) Received: from dingdong.cryptoapps.com (postfix@uslink-66.173.43-133.uslink.net [66.173.43.133] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5B5iC2x002328 for ; Tue, 10 Jun 2003 22:44:13 -0700 Received: by dingdong.cryptoapps.com (Postfix, from userid 1001) id A5721FB838; Wed, 11 Jun 2003 00:46:52 -0500 (CDT) Date: Wed, 11 Jun 2003 00:46:52 -0500 From: Chris Wedgwood To: Michael Whang Cc: linux-xfs@oss.sgi.com Subject: Re: XFS/XP Dual Boot? Message-ID: <20030611054652.GC7800@dingdong.cryptoapps.com> References: <3EE67830.3020506@boywonderfx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EE67830.3020506@boywonderfx.com> X-archive-position: 4268 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Tue, Jun 10, 2003 at 05:30:40PM -0700, Michael Whang wrote: > Has anyone successfully dual booted XFS with windows XP? Please let > me know if so and how. I did I a long time ago (no windows now)... I don't recall any issues but you will need to install your boot-loader in the MBR as XFS stores the first superblock in the first sector of the partition which some bootloaded need to be told about. --cw From owner-linux-xfs@oss.sgi.com Wed Jun 11 02:35:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 02:35:53 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5B9ZV2x013302 for ; Wed, 11 Jun 2003 02:35:32 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id D67771432B for ; Wed, 11 Jun 2003 11:35:25 +0200 (MEST) Date: Wed, 11 Jun 2003 11:35:25 +0200 From: Andi Kleen To: linux-xfs@oss.sgi.com Subject: [PATCH] Give logbufs a better default Message-ID: <20030611093525.GA2329@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-archive-position: 4269 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs A long standing problem in XFS is that in the default configuration metadata performance is not that great because it uses not enough log buffers. There are FAQs around to fix this, but it would be better if the kernel did the right thing by default. The main problem is probably that XFS still uses the default from the early 90ies, which are probably not that good anymore for today's machines. This patch changes the logbufs= default based on the available memory. If you have 128MB or less it uses 3 logbufs (normally 96K per file system) For 400MB or less it uses 5 (160K) For anything bigger 8 (256K) It is still a kind of bandaid. I think the better solution would be to dynamically allocate new log buffers as needed until some limit (and block if the memory cannot be allocated). This should not be that bad because vmalloc/vfree are not that expensive anymore and with some luck you can even get a physically continuous buffer (e.g. on a 16byte page size ia64 system) Patch for XFS 1.3pre1. -Andi --- linux/fs/xfs/xfs_log.c-o 2003-06-10 14:27:57.000000000 +0200 +++ linux/fs/xfs/xfs_log.c 2003-06-11 11:29:55.000000000 +0200 @@ -1072,9 +1072,15 @@ * This is the normal path. If m_logbufs == -1, then the * admin has chosen to use the system defaults for logbuffers. */ - if (mp->m_logbufs == -1) - log->l_iclog_bufs = XLOG_NUM_ICLOGS; - else + if (mp->m_logbufs == -1) { + if (xfs_physmem <= btoc(128*1024*1024)) { + log->l_iclog_bufs = 3; + } else if (xfs_physmem <= btoc(400*1024*1024)) { + log->l_iclog_bufs = 5; + } else { + log->l_iclog_bufs = 8; /* 256K with 32K bufs */ + } + } else log->l_iclog_bufs = mp->m_logbufs; #if defined(DEBUG) || defined(XLOG_NOLOG) From owner-linux-xfs@oss.sgi.com Wed Jun 11 02:39:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 02:39:24 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5B9d72x013905 for ; Wed, 11 Jun 2003 02:39:08 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 23DD61432B for ; Wed, 11 Jun 2003 11:39:02 +0200 (MEST) Date: Wed, 11 Jun 2003 11:39:02 +0200 From: Andi Kleen To: linux-xfs@oss.sgi.com Subject: [PATCH] Better defaults to mkfs logsize Message-ID: <20030611093902.GB2329@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-archive-position: 4270 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs Here is a patch to mkfs in the same spirit as the earlier logbufs patch. Another limiting factor for XFS metadata performance is the default logsize, which is usually too small (compared to other Linux journaling fs and good defaults) The patch scales the log size for an inline log much more aggressively. If the file system is bigger than 1GB you will get at least 10MB of log. The maximum size of the log (64MB) is reached at 128GB already, not at 1TB. I guess even the maximum could be still enlarged (64MB is rather small these days), but I didn't do that for now. -Andi diff -u xfsprogs/mkfs/xfs_mkfs.c-o xfsprogs/mkfs/xfs_mkfs.c --- xfsprogs/mkfs/xfs_mkfs.c-o 2003-06-11 11:10:34.000000000 +0200 +++ xfsprogs/mkfs/xfs_mkfs.c 2003-06-11 11:27:24.000000000 +0200 @@ -1423,6 +1423,9 @@ [dirblocklog - XFS_MIN_BLOCKSIZE_LOG]; ASSERT(i); min_logblocks = MAX(XFS_MIN_LOG_BLOCKS, i * XFS_MIN_LOG_FACTOR); + if (dblocks >= (1024*1024*1024)>>blocklog) { + min_logblocks = MAX(min_logblocks, (10*1024*1024)>>blocklog); + } if (logsize && xi.logBBsize > 0 && logblocks > DTOBT(xi.logBBsize)) { fprintf(stderr, _("size %s specified for log subvolume is too large, maximum is %lld blocks\n"), @@ -1443,11 +1446,11 @@ else if (loginternal && !logsize) { /* * logblocks grows from min_logblocks to XFS_MAX_LOG_BLOCKS - * at 1TB + * at 128GB * - * 8192 = 1TB / MAX_LOG_BYTES + * 2048 = 128GB / MAX_LOG_BYTES */ - logblocks = (dblocks << blocklog) / 8192; + logblocks = (dblocks << blocklog) / 2048; logblocks = logblocks >> blocklog; logblocks = MAX(min_logblocks, logblocks); logblocks = MAX(logblocks, From owner-linux-xfs@oss.sgi.com Wed Jun 11 07:59:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 07:59:17 -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.9) with SMTP id h5BEx02x010668 for ; Wed, 11 Jun 2003 07:59:00 -0700 Received: from comcast.net (localhost [127.0.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id 5018374A02; Wed, 11 Jun 2003 07:58:54 -0700 (PDT) Message-ID: <3EE743AE.7060606@comcast.net> Date: Wed, 11 Jun 2003 07:58:54 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Melekhov Cc: linux-xfs@oss.sgi.com Subject: Re: tape backup tool ? References: <3EE456CD.7040703@belkam.com> <20030609095222.GA6057@wotan.suse.de> <3EE6A90F.9040306@belkam.com> In-Reply-To: <3EE6A90F.9040306@belkam.com> X-Enigmail-Version: 0.74.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4271 X-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 Dmitry Melekhov wrote: > Andi Kleen wrote: > >>> Or, may be, someone knows better tool for tape backup? >> >> >> >> xfsdump perhaps? > > > Hmm. Sorry for such stupid question... Is it possible to restore one > file from tape with xfsrestore? > > > > You can run xfsrestore interactively with the -i switch. That'll get you a shell like environment where you can cd into a directory and mark specific files for extraction. -Walt From owner-linux-xfs@oss.sgi.com Wed Jun 11 08:42:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 08:42:38 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BFgH2x011532 for ; Wed, 11 Jun 2003 08:42:18 -0700 Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BFwZmO004797 for ; Wed, 11 Jun 2003 10:58:35 -0500 Received: from wrlarun (sshgate.corp.sgi.com [169.238.216.146]) by cthulhu.engr.sgi.com (SGI-8.12.5/8.12.5) with SMTP id h5BFfAg013781702; Wed, 11 Jun 2003 08:41:11 -0700 (PDT) Message-ID: <028201c3302f$80e2f6e0$6800a8c0@attbi.com> From: "John Hawkes" To: "Michael Whang" , References: <3EE67830.3020506@boywonderfx.com> Subject: Re: XFS/XP Dual Boot? Date: Wed, 11 Jun 2003 08:38:27 -0700 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 5.00.2919.6600 X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-archive-position: 4272 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hawkes@sgi.com Precedence: bulk X-list: linux-xfs > Has anyone successfully dual booted XFS with windows XP? Please let me > know if so and how. I dual-boot XP and non-XFS Red Hat (7.2?). I used Partition Magic to carve up the disk, and RH's Grub to perform the dual-boot. I couldn't get Boot Magic to do the dual-boot for various reasons. Grub works fine. John Hawkes From owner-linux-xfs@oss.sgi.com Wed Jun 11 08:59:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 08:59:27 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BFx62x012232 for ; Wed, 11 Jun 2003 08:59: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.2/linux-outbound_gateway-1.2) with ESMTP id h5BFx13X018455 for ; Wed, 11 Jun 2003 08:59:01 -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 h5BFx0qX4165673 for ; Wed, 11 Jun 2003 10:59:01 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5BFx0Rn113600053 for ; Wed, 11 Jun 2003 10:59:00 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5BFx0m15358; Wed, 11 Jun 2003 10:59:00 -0500 Message-Id: <200306111559.h5BFx0m15358@jen.americas.sgi.com> Date: Wed, 11 Jun 2003 10:59:00 -0500 Subject: TAKE - fix O_DIRECT and uninitialized user memory To: linux-xfs@oss.sgi.com X-archive-position: 4273 X-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 Fix O_DIRECT using uninitialized memory, user space is passing in the same zero page at lots of addresses. The xfs code was locking the user pages which is unneccessary, end result deadlock on ourselves. Date: Wed Jun 11 08:58:15 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: 2.4.x-xfs:slinx:150885a linux/fs/xfs/pagebuf/page_buf.c - 1.120 - In pagebuf_lookup, create a pagebuf which is lockable so we do not lock the pages within it during I/O. Only O_DIRECT does I/O on this type of pagebuf. From owner-linux-xfs@oss.sgi.com Wed Jun 11 09:15:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 09:15:57 -0700 (PDT) Received: from hotmail.com (sea2-f43.sea2.hotmail.com [207.68.165.43]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BGFe2x012999 for ; Wed, 11 Jun 2003 09:15:41 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 11 Jun 2003 09:15:35 -0700 Received: from 144.189.40.222 by sea2fd.sea2.hotmail.msn.com with HTTP; Wed, 11 Jun 2003 16:15:34 GMT X-Originating-IP: [144.189.40.222] X-Originating-Email: [hagit_guy@hotmail.com] From: "hagit guy" To: linux-xfs@oss.sgi.com Subject: shutting down xfs is FAILED Date: Wed, 11 Jun 2003 19:15:34 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 11 Jun 2003 16:15:35.0151 (UTC) FILETIME=[B05837F0:01C33034] X-archive-position: 4274 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hagit_guy@hotmail.com Precedence: bulk X-list: linux-xfs Hi I have a problem with my RedHat 7.1 While shutting down, the "shutting down xfs" is FAILED. Then, after booting Linux, the system doesnt raise well and I cant see anything on the screen Please help me I am atack and cant do anything!!!! Thanks HAgit _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail From owner-linux-xfs@oss.sgi.com Wed Jun 11 09:24:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 09:24:23 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BGO82x013461 for ; Wed, 11 Jun 2003 09:24:08 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BGeQmO007943 for ; Wed, 11 Jun 2003 11:40:26 -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 h5BGO1qX4131949; Wed, 11 Jun 2003 11:24:02 -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 h5BGO1Yk11830875; Wed, 11 Jun 2003 11:24:01 -0500 (CDT) Subject: Re: shutting down xfs is FAILED From: Eric Sandeen To: hagit guy Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1055348640.11070.20.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Jun 2003 11:24:01 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4275 X-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 The only thing which will say Shutting down XFS: [FAILED] when you shut down your system is the X Font Server, which is unfortunately unrelated to the topic of this list (the XFS Filesystem). -Eric On Wed, 2003-06-11 at 11:15, hagit guy wrote: > Hi > I have a problem with my RedHat 7.1 > While shutting down, the "shutting down xfs" is FAILED. > Then, after booting Linux, the system doesnt raise well and I cant see > anything on the screen > Please help me > I am atack and cant do anything!!!! > Thanks > HAgit > > _________________________________________________________________ > The new MSN 8: advanced junk mail protection and 2 months FREE* > http://join.msn.com/?page=features/junkmail -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Wed Jun 11 09:25:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 09:25:26 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BGPK2x013647 for ; Wed, 11 Jun 2003 09:25:21 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BGfdmO008023 for ; Wed, 11 Jun 2003 11:41:39 -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 h5BGPEqX4176631; Wed, 11 Jun 2003 11:25:14 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 19Q8PS-0007CL-00; Wed, 11 Jun 2003 11:25:14 -0500 Date: Wed, 11 Jun 2003 11:25:14 -0500 From: Nathan Straz To: hagit guy Cc: linux-xfs@oss.sgi.com Subject: Re: shutting down xfs is FAILED Message-ID: <20030611162514.GA24173@sgi.com> Mail-Followup-To: hagit guy , linux-xfs@oss.sgi.com References: 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: 4276 X-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 On Wed, Jun 11, 2003 at 07:15:34PM +0300, hagit guy wrote: > I have a problem with my RedHat 7.1 > While shutting down, the "shutting down xfs" is FAILED. I think this message is probably referring to the X Font Server. XFS, the file system, doesn't have an initscript. > Then, after booting Linux, the system doesnt raise well and I cant see > anything on the screen You'll need to be more detailed than that. Is your X server not starting? Do you see mount errors while you boot? -- 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 Wed Jun 11 11:04:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 11:04:28 -0700 (PDT) Received: from andrei.myip.org (12-234-128-127.client.attbi.com [12.234.128.127]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BI442x018132 for ; Wed, 11 Jun 2003 11:04:05 -0700 Received: by andrei.myip.org (Postfix, from userid 102) id B882B2FA84; Wed, 11 Jun 2003 11:04:03 -0700 (PDT) Received: from stantz.corp.sgi.com (unknown [130.62.4.42]) by andrei.myip.org (Postfix) with ESMTP id 3D1972FA81 for ; Wed, 11 Jun 2003 11:04:02 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id D9CFC1967C for ; Wed, 11 Jun 2003 11:03:51 -0700 (PDT) Subject: Re: XFS/XP Dual Boot? From: Florin Andrei Reply-To: linux-xfs@oss.sgi.com To: linux-xfs@oss.sgi.com In-Reply-To: <20030611054652.GC7800@dingdong.cryptoapps.com> References: <3EE67830.3020506@boywonderfx.com> <20030611054652.GC7800@dingdong.cryptoapps.com> Content-Type: text/plain Organization: SGI Message-Id: <1055354631.11354.5.camel@stantz.corp.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Jun 2003 11:03:51 -0700 Content-Transfer-Encoding: 7bit X-archive-position: 4277 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: florin@sgi.com Precedence: bulk X-list: linux-xfs On Tue, 2003-06-10 at 22:46, Chris Wedgwood wrote: > On Tue, Jun 10, 2003 at 05:30:40PM -0700, Michael Whang wrote: > > > Has anyone successfully dual booted XFS with windows XP? Please let > > me know if so and how. > > I did I a long time ago (no windows now)... I don't recall any issues > but you will need to install your boot-loader in the MBR as XFS stores > the first superblock in the first sector of the partition which some > bootloaded need to be told about. If you have a small /boot partition (which is usually recommended) then you can format it Ext3 (or even Ext2 mounted sync), declare it bootable and install the bootloader in its superblock. That's basically what i almost always do. -- Florin Andrei "Privacy is such a 20th century concept." - Darren Reed From owner-linux-xfs@oss.sgi.com Wed Jun 11 11:13:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 11:13:23 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BID82x018846 for ; Wed, 11 Jun 2003 11:13: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.2/linux-outbound_gateway-1.2) with ESMTP id h5BID2E0027247 for ; Wed, 11 Jun 2003 11:13: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 h5BID2qX4196964 for ; Wed, 11 Jun 2003 13:13:02 -0500 (CDT) Received: from [128.162.232.98] (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5BID2Rn110113768 for ; Wed, 11 Jun 2003 13:13:02 -0500 (CDT) Subject: Re: XFS/XP Dual Boot? From: Russell Cattelan To: linux-xfs@oss.sgi.com In-Reply-To: <1055354631.11354.5.camel@stantz.corp.sgi.com> References: <3EE67830.3020506@boywonderfx.com> <20030611054652.GC7800@dingdong.cryptoapps.com> <1055354631.11354.5.camel@stantz.corp.sgi.com> Content-Type: text/plain Organization: Message-Id: <1055355202.6325.4.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 11 Jun 2003 13:13:22 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4278 X-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 On Wed, 2003-06-11 at 13:03, Florin Andrei wrote: > On Tue, 2003-06-10 at 22:46, Chris Wedgwood wrote: > > On Tue, Jun 10, 2003 at 05:30:40PM -0700, Michael Whang wrote: > > > > > Has anyone successfully dual booted XFS with windows XP? Please let > > > me know if so and how. > > > > I did I a long time ago (no windows now)... I don't recall any issues > > but you will need to install your boot-loader in the MBR as XFS stores > > the first superblock in the first sector of the partition which some > > bootloaded need to be told about. > > If you have a small /boot partition (which is usually recommended) then > you can format it Ext3 (or even Ext2 mounted sync), declare it bootable > and install the bootloader in its superblock. > That's basically what i almost always do. swap will also work. although you need to make it type 0x83 to install the boot block and then switch it back to a swap partition. From owner-linux-xfs@oss.sgi.com Wed Jun 11 12:41:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 12:42:13 -0700 (PDT) Received: from poptart.bithose.com (ip-204-97-176-41.modem.logical.net [204.97.176.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BJfo2x024428 for ; Wed, 11 Jun 2003 12:41:53 -0700 Received: from poptart.bithose.com (localhost [127.0.0.1]) by poptart.bithose.com (8.12.9/8.12.9) with ESMTP id h5BJfnkK124777 for ; Wed, 11 Jun 2003 15:41:49 -0400 (EDT) Received: from localhost (jakari@localhost) by poptart.bithose.com (8.12.9/8.12.9/Submit) with ESMTP id h5BJfmT9124728 for ; Wed, 11 Jun 2003 15:41:49 -0400 (EDT) X-Authentication-Warning: poptart.bithose.com: jakari owned process doing -bs Date: Wed, 11 Jun 2003 15:41:48 -0400 (EDT) From: Jameel Akari To: Subject: xfsdump problems In-Reply-To: <20030609201720.J86243-100000@xs1.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4279 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jakari@bithose.com Precedence: bulk X-list: linux-xfs xfsdump installed from RPM (from oss.sgi.com), version 2.2.3-1 When attempting to run a dump (local or remote) it aborts with: xfsdump: drive_scsitape.c:1985: do_get_write_buf: Assertion `contextp->dc_nextp < contextp->dc_recendp' failed. Ok, so what am I doing wrong here? I don't see anything in the list archives that sticks out. #xfsdump -b1024 -o -v2 -f /dev/st0 / xfsdump: using scsi tape (drive_scsitape) strategy xfsdump: version 2.2.3 (dump format 3.0) - Running single-threaded ============================= dump label dialog please enter label for this dump session (timeout in 300 sec) -> rootvol session label entered: "rootvol" --------------------------------- end dialog xfsdump: WARNING: most recent level 0 dump was interrupted, but not resuming that dump since resume (-R) option not specified xfsdump: level 0 dump of spoonman:/ xfsdump: dump date: Wed Jun 11 15:30:11 2003 xfsdump: session id: 75aefb89-e293-4aab-a3eb-32fdee045d2a xfsdump: session label: "rootvol" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: ino map phase 3: skipping (no pruning necessary) xfsdump: ino map phase 4: skipping (size estimated in phase 2) xfsdump: ino map phase 5: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 161284288 bytes xfsdump: preparing drive xfsdump: fixed block size tape drive at /dev/st0 xfsdump: WARNING: media may contain data. Overwrite option specified =========================== media overwrite dialog overwrite data on media in drive 0? 1: don't overwrite (timeout in 3600 sec) 2: overwrite (default) -> media will be overwritten --------------------------------- end dialog ============================= media label dialog please enter label for media in drive 0 (timeout in 300 sec) -> root01 media label entered: "root01" --------------------------------- end dialog xfsdump: creating dump session media file 0 (media 0, file 0) xfsdump: dumping ino map xfsdump: drive_scsitape.c:1985: do_get_write_buf: Assertion `contextp->dc_nextp < contextp->dc_recendp' failed. Aborted The drive is an 8mm and seems to work: [root@spoonman root]# mt -f /dev/st0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 1024 bytes. Density code 0x8c (EXB-8505 compressed). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN I'm running a test on it with plain "tar" to make sure. Thanks in advance, -- #!/jameel/akari sleep 4800; make clean && make breakfast From owner-linux-xfs@oss.sgi.com Wed Jun 11 13:33:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 13:33:39 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BKXO2x027335 for ; Wed, 11 Jun 2003 13:33:24 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BKnhmO025831 for ; Wed, 11 Jun 2003 15:49:43 -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 h5BKXIqX4217015; Wed, 11 Jun 2003 15:33:18 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5BKXERn113803010; Wed, 11 Jun 2003 15:33:18 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5BKXEK16363; Wed, 11 Jun 2003 15:33:14 -0500 Subject: Re: [PATCH] Give logbufs a better default From: Steve Lord To: Andi Kleen Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030611093525.GA2329@wotan.suse.de> References: <20030611093525.GA2329@wotan.suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1055363594.6614.44.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 11 Jun 2003 15:33:14 -0500 X-archive-position: 4280 X-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 On Wed, 2003-06-11 at 04:35, Andi Kleen wrote: > A long standing problem in XFS is that in the default configuration > metadata performance is not that great because it uses not enough > log buffers. There are FAQs around to fix this, but it would be better > if the kernel did the right thing by default. > > The main problem is probably that XFS still uses the default from the > early 90ies, which are probably not that good anymore for today's machines. > > This patch changes the logbufs= default based on the available memory. > If you have 128MB or less it uses 3 logbufs (normally 96K per file system) > For 400MB or less it uses 5 (160K) > For anything bigger 8 (256K) Hi Andi, Just wondering why you picked odd numbers? > > It is still a kind of bandaid. I think the better solution would be to > dynamically allocate new log buffers as needed until some limit > (and block if the memory cannot be allocated). This should not be that > bad because vmalloc/vfree are not that expensive anymore and with some > luck you can even get a physically continuous buffer (e.g. on a 16byte page size > ia64 system) Interesting idea, one issue is that during recovery, the maximum amount of outstanding I/O there might of been (i.e. number of iclog buffers) is a factor in how much work there is to do. Adding new ones dynamically might be possible, but there is this 'interesting' state machine on the log buffers to deal with there. Thanks Steve > > Patch for XFS 1.3pre1. > > -Andi > > > --- linux/fs/xfs/xfs_log.c-o 2003-06-10 14:27:57.000000000 +0200 > +++ linux/fs/xfs/xfs_log.c 2003-06-11 11:29:55.000000000 +0200 > @@ -1072,9 +1072,15 @@ > * This is the normal path. If m_logbufs == -1, then the > * admin has chosen to use the system defaults for logbuffers. > */ > - if (mp->m_logbufs == -1) > - log->l_iclog_bufs = XLOG_NUM_ICLOGS; > - else > + if (mp->m_logbufs == -1) { > + if (xfs_physmem <= btoc(128*1024*1024)) { > + log->l_iclog_bufs = 3; > + } else if (xfs_physmem <= btoc(400*1024*1024)) { > + log->l_iclog_bufs = 5; > + } else { > + log->l_iclog_bufs = 8; /* 256K with 32K bufs */ > + } > + } else > log->l_iclog_bufs = mp->m_logbufs; > > #if defined(DEBUG) || defined(XLOG_NOLOG) -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:28:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:28:45 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLST2x028924 for ; Wed, 11 Jun 2003 14:28:30 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 792FA14C25; Wed, 11 Jun 2003 23:28:23 +0200 (MEST) Date: Wed, 11 Jun 2003 23:28:23 +0200 From: Andi Kleen To: Steve Lord Cc: Andi Kleen , linux-xfs@oss.sgi.com, mason@suse.com Subject: Re: [PATCH] Give logbufs a better default Message-ID: <20030611212822.GA8166@wotan.suse.de> References: <20030611093525.GA2329@wotan.suse.de> <1055363594.6614.44.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055363594.6614.44.camel@jen.americas.sgi.com> X-archive-position: 4281 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs On Wed, Jun 11, 2003 at 03:33:14PM -0500, Steve Lord wrote: > On Wed, 2003-06-11 at 04:35, Andi Kleen wrote: > > A long standing problem in XFS is that in the default configuration > > metadata performance is not that great because it uses not enough > > log buffers. There are FAQs around to fix this, but it would be better > > if the kernel did the right thing by default. > > > > The main problem is probably that XFS still uses the default from the > > early 90ies, which are probably not that good anymore for today's machines. > > > > This patch changes the logbufs= default based on the available memory. > > If you have 128MB or less it uses 3 logbufs (normally 96K per file system) > > For 400MB or less it uses 5 (160K) > > For anything bigger 8 (256K) > > Hi Andi, > > Just wondering why you picked odd numbers? Usual handwaving. Of course i should have picked power of two just to make it look more scientific, but the range was a bit too small for that ;) 3 was the old default, which seems ok for small systems. Small system is arbitarily defined as <= 128MB memory. 8 is the current maximum (is there a reason for that btw? could it be simply raised?) I wanted to get 8 on my 512MB test box. And usually the memory counting variable has some loss, so I choose 400MB as the boundary. 5 is somewhere between 3 and 8 for the boxes inbetween. > > > > > It is still a kind of bandaid. I think the better solution would be to > > dynamically allocate new log buffers as needed until some limit > > (and block if the memory cannot be allocated). This should not be that > > bad because vmalloc/vfree are not that expensive anymore and with some > > luck you can even get a physically continuous buffer (e.g. on a 16byte page size ^^^KByte of course > > ia64 system) > > Interesting idea, one issue is that during recovery, the maximum amount > of outstanding I/O there might of been (i.e. number of iclog buffers) > is a factor in how much work there is to do. Adding new ones dynamically Hmm, I thought that recovery work was bounded by the on disk log size? How do the pending buffers come into play? They look more likely to make you lose a bit more data in case of a crash, but your new sync daemon with a timer should take care of that (it will still be much better with this than it was ever before) Processing 10MB (new minimum with the mkfs patch for 1GB+) or even 64MB at mount shouldn't be a big issue on a modern box. > might be possible, but there is this 'interesting' state machine on the > log buffers to deal with there. I have not really looked into the state machine yet. You are saying it has some scalability problems with more buffers or are the data structures just nasty enough to adding more buffers dynamically could be difficult? Thanks for your comments, -Andi From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:31:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:31:24 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLVD2x029322 for ; Wed, 11 Jun 2003 14:31:16 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h5BLSaN6005400; Wed, 11 Jun 2003 16:28:36 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h5BLSZ3m005398; Wed, 11 Jun 2003 16:28:35 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 From: Austin Gonyou To: Seth Mos Cc: Paulo Matos , XFS List In-Reply-To: <4.3.2.7.2.20030610133612.0326eba0@pop.xs4all.nl> References: <4.3.2.7.2.20030610133612.0326eba0@pop.xs4all.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1055366915.1925.55.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 11 Jun 2003 16:28:35 -0500 X-archive-position: 4282 X-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 On Tue, 2003-06-10 at 06:41, Seth Mos wrote: > Yes, 7.3 it is. I have no boxes running anything newer. It looks like > we > will be switching to Red Hat ES pretty soon for the database box which > would mean that I can't use the XFS filesystem anymore since it is not > covered by the support contract. > > Some other boxes for which I do not care about the support anyways > will > keep using XFS. That means I'll probably would need to make some sort > of > installer for Red Hat ES with XFS support in order to install or > upgrade. Could it be possible to modularize the XFS? Kind of like an XFS patch-less install? I dunno if that's possible, somewhat like how some of these driver installers work now a days for linux? > The biggest problem with ES is the use of the "ancient" 2.4.9 kernel > with > more patches then you can shake a stick at. If you check their .src.rpm which is freely available for that kernel, you should see that they patch up to 2.4.18 I believe, with a ton of other back-port stuff. -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:34:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:34:46 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLYe2x029962 for ; Wed, 11 Jun 2003 14:34:41 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h5BLW8N6005446; Wed, 11 Jun 2003 16:32:08 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h5BLW84q005444; Wed, 11 Jun 2003 16:32:08 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Re: XFS feature request From: Austin Gonyou To: Michael Loftis Cc: XFS List In-Reply-To: <86984947.1054766968@[10.1.2.77]> References: <86984947.1054766968@[10.1.2.77]> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1055367128.2003.57.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 11 Jun 2003 16:32:08 -0500 X-archive-position: 4283 X-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 Given the path of comments here. I'd say that's why the ext2 FS has 3 options for error handling! :) On Wed, 2003-06-04 at 23:49, Michael Loftis wrote: > Mostly I'd much prefer the option of just going R/O on a filesystem, > living > with the possibility that what I'm *reading* isn't right than a whole > system just going black and having to get onself physically present to > ascertain the problem. > > I don't believe that unmounting the filesystem is *always* the right > thing > to do. It is in some cases, but there are cases where you'd much > rather > the system just went read-only and refused to flush anything off to > it. > > --On Wednesday, June 04, 2003 2:02 PM -0600 Andrew Mathews > wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Michael Loftis wrote: > >| This has also recently been a problem for us. The whole 'something > >| looks a little odd so I'm going to just tank and take the whole > system > >| with me' knee-jerk reaction XFS has is very problematic. It's the > >| biggest reason I'm moving operations away from it. > >| > >| --On Wednesday, June 04, 2003 20:26 +0200 Seth Mos > > >| wrote: > >| > >|> Hello, > >|> > >|> Upon a filesystem error the XFS filesystem normally unmounts the > fs and > >|> often takes the box along with it. > >|> ... > >| > >| -- > >| Michael Loftis > >| Modwest Sr. Systems Administrator > >| Powerful, Affordable Web Hosting > >| > > > > Not to diminish Set's original request, but to address this > comment... > > > > I guess your term "knee-jerk reaction" is subjective. I'd much > rather > > have a recoverable system than an unrecoverable one, which is > exactly > > what you'll have if the filesystem is put into an unstable state > > (corruption) and isn't intelligent enough to protect itself from > further > > damage. It's also one of the reasons we won't use anything other > than > > XFS in a production environment. > > > > - -- > > Andrew Mathews > > - > --------------------------------------------------------------------- > > ~ 1:56pm up 5 days, 4:49, 12 users, load average: 1.16, 1.13, > 1.09 > > - > --------------------------------------------------------------------- > > A statesman is a politician who's been dead 10 or 15 years. > > -- Harry S. Truman > > - -- > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.0.7 (GNU/Linux) > > Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org > > > > iD8DBQE+3lBHidHQ0m/kEssRAhouAJwJPdLuIKyUzmxSAj2nySsT2zCGfgCeO4lf > > 33cLIwDjO7/T/iY8LSDp5qQ= > > =T97e > > -----END PGP SIGNATURE----- > > > > > > -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:36:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:36:51 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLal2x030456 for ; Wed, 11 Jun 2003 14:36:47 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BLaf3X023927 for ; Wed, 11 Jun 2003 14:36: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 h5BLafqX4226984; Wed, 11 Jun 2003 16:36:41 -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 h5BLafYk11905308; Wed, 11 Jun 2003 16:36:41 -0500 (CDT) Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 From: Eric Sandeen To: Austin Gonyou Cc: Seth Mos , Paulo Matos , XFS List In-Reply-To: <1055366915.1925.55.camel@portageek.digitalroadkill.net> References: <4.3.2.7.2.20030610133612.0326eba0@pop.xs4all.nl> <1055366915.1925.55.camel@portageek.digitalroadkill.net> Content-Type: text/plain Organization: Message-Id: <1055367400.11067.143.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Jun 2003 16:36:41 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4284 X-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 On Wed, 2003-06-11 at 16:28, Austin Gonyou wrote: > > Could it be possible to modularize the XFS? Kind of like an XFS > patch-less install? I dunno if that's possible, somewhat like how some > of these driver installers work now a days for linux? You need core kernel changes to support XFS... especially in 2.4.9! So a patch-less install.... nope. OTOH we are talking about distributing the next release in 2 packages, an "xfs-ready" kernel, and an xfs-module RPM. That way xfs can beupdated without a new kernel install, as long as the interface does not change. Not sure if we'll get this done, but I've been kicking it around. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:43:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:43:57 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLhr2x031337 for ; Wed, 11 Jun 2003 14:43:53 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h5BLfJN6005540; Wed, 11 Jun 2003 16:41:19 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h5BLfJIn005538; Wed, 11 Jun 2003 16:41:19 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 From: Austin Gonyou To: Eric Sandeen Cc: Seth Mos , Paulo Matos , XFS List In-Reply-To: <1055367400.11067.143.camel@stout.americas.sgi.com> References: <1055367400.11067.143.camel@stout.americas.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1055367678.1925.59.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 11 Jun 2003 16:41:19 -0500 X-archive-position: 4285 X-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 This would greatly help those of us possibly moving to ES or AS. :) On Wed, 2003-06-11 at 16:36, Eric Sandeen wrote: > On Wed, 2003-06-11 at 16:28, Austin Gonyou wrote: > > > > > Could it be possible to modularize the XFS? Kind of like an XFS > > patch-less install? I dunno if that's possible, somewhat like how > some > > of these driver installers work now a days for linux? > > You need core kernel changes to support XFS... especially in 2.4.9! > So > a patch-less install.... nope. > > OTOH we are talking about distributing the next release in 2 packages, > an "xfs-ready" kernel, and an xfs-module RPM. That way xfs can > beupdated without a new kernel install, as long as the interface does > not change. > > Not sure if we'll get this done, but I've been kicking it around. > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. 651-683-3102 -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:44:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:44:42 -0700 (PDT) Received: from taz2.fiberhosting.com (IDENT:bw0uQSNpjo8Ecr6Q4Gbarig8sBr4+Av/@KNIGHT.01.dios.net [65.222.230.112]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLib2x031624 for ; Wed, 11 Jun 2003 14:44:38 -0700 Received: (qmail 24186 invoked by uid 2526); 11 Jun 2003 21:44:36 -0000 To: Eric Sandeen Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 Message-ID: <1055367876.3ee7a2c43f7ef@webmail.smithconcepts.com> Date: Wed, 11 Jun 2003 17:44:36 -0400 (EDT) From: "Bryan J. Smith" Cc: Austin Gonyou , Seth Mos , Paulo Matos , XFS List References: <4.3.2.7.2.20030610133612.0326eba0@pop.xs4all.nl> <1055366915.1925.55.camel@portageek.digitalroadkill.net> <1055367400.11067.143.camel@stout.americas.sgi.com> In-Reply-To: <1055367400.11067.143.camel@stout.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.7 X-Originating-IP: 216.53.154.101 X-archive-position: 4286 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Quoting Eric Sandeen : > OTOH we are talking about distributing the next release in 2 packages, > an "xfs-ready" kernel, and an xfs-module RPM. That way xfs can > beupdated without a new kernel install, as long as the interface does > not change. > Not sure if we'll get this done, but I've been kicking it around. So what you're saying is that [nearly] all of the core kernel changes are static? That is, other than to accomodate changes by the kernel between versions that affect select XFS added portions? Has this been so since the 1.0 release? Does 2.5/2.6 completely take care of providing these interfaces? -- Bryan J. Smith, E.I. mailto:b.j.smith@ieee.org http://thebs.org CCDA/CCNA CIWSA/MCIWA LPIC2/RHCE MCSA http://thebs.org/certs.pdf ----------------------------------------------------------------- Microsoft(R): The 'Data Longevity is Optional' Company From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:47:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:47:38 -0700 (PDT) Received: from taz2.fiberhosting.com (IDENT:QmKXsvpLEP2XzSfqrs+EFG6x4klomDMB@KNIGHT.01.dios.net [65.222.230.112]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLlY2x032394 for ; Wed, 11 Jun 2003 14:47:35 -0700 Received: (qmail 24505 invoked by uid 2526); 11 Jun 2003 21:47:33 -0000 To: Austin Gonyou Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 Message-ID: <1055368053.3ee7a3752d861@webmail.smithconcepts.com> Date: Wed, 11 Jun 2003 17:47:33 -0400 (EDT) From: "Bryan J. Smith" Cc: Eric Sandeen , Seth Mos , Paulo Matos , XFS List References: <1055367400.11067.143.camel@stout.americas.sgi.com> <1055367678.1925.59.camel@portageek.digitalroadkill.net> In-Reply-To: <1055367678.1925.59.camel@portageek.digitalroadkill.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: IMP/PHP IMAP webmail program 2.2.7 X-Originating-IP: 216.53.154.101 X-archive-position: 4287 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: b.j.smith@ieee.org Precedence: bulk X-list: linux-xfs Quoting Austin Gonyou : > This would greatly help those of us possibly moving to ES or AS. :) Hmmm, do you think this would make Red Hat might be more "open" to including those core changes in its own kernels? I.e., as long as they didn't affect Ext3, but kept XFS itself separate. I am, of course, talking from a standpoint of great ignorance on the matter. So feel free to smack me straight. -- Bryan J. Smith, E.I. mailto:b.j.smith@ieee.org http://thebs.org CCDA/CCNA CIWSA/MCIWA LPIC2/RHCE MCSA http://thebs.org/certs.pdf ----------------------------------------------------------------- Microsoft(R): The 'Data Longevity is Optional' Company From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:51:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:51:04 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLp02x000492 for ; Wed, 11 Jun 2003 14:51:00 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BLopE0029976 for ; Wed, 11 Jun 2003 14:50:52 -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 h5BLopqX4225569; Wed, 11 Jun 2003 16:50:51 -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 h5BLooYk11907429; Wed, 11 Jun 2003 16:50:50 -0500 (CDT) Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 From: Eric Sandeen To: "Bryan J. Smith" Cc: Austin Gonyou , Seth Mos , Paulo Matos , XFS List In-Reply-To: <1055367876.3ee7a2c43f7ef@webmail.smithconcepts.com> References: <4.3.2.7.2.20030610133612.0326eba0@pop.xs4all.nl> <1055366915.1925.55.camel@portageek.digitalroadkill.net> <1055367400.11067.143.camel@stout.americas.sgi.com> <1055367876.3ee7a2c43f7ef@webmail.smithconcepts.com> Content-Type: text/plain Organization: Message-Id: <1055368250.11070.148.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Jun 2003 16:50:50 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4288 X-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 On Wed, 2003-06-11 at 16:44, Bryan J. Smith wrote: > So what you're saying is that [nearly] all of the core kernel changes are static? That is, other than > to accomodate changes by the kernel between versions that affect select XFS added portions? for a given kernel rev, the xfs<->kernel interface has stabilized quite a lot, yes. Not to say it will never change, of course. > Has this been so since the 1.0 release? ahh... nope. :) > Does 2.5/2.6 completely take care of providing these interfaces? XFS is in 2.5, so it's mostly a moot point. It's possible that from time to time, updated XFS in CVS will require a kernel change that is not in Linus' tree, of course. Is that what you're asking? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Wed Jun 11 14:54:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 14:54:52 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BLsm2x001057 for ; Wed, 11 Jun 2003 14:54:49 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BLsh3X026575 for ; Wed, 11 Jun 2003 14:54:43 -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 h5BLshqX4229726; Wed, 11 Jun 2003 16:54:43 -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 h5BLsgYk11864880; Wed, 11 Jun 2003 16:54:42 -0500 (CDT) Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 From: Eric Sandeen To: Austin Gonyou Cc: Seth Mos , Paulo Matos , XFS List In-Reply-To: <1055367678.1925.59.camel@portageek.digitalroadkill.net> References: <1055367400.11067.143.camel@stout.americas.sgi.com> <1055367678.1925.59.camel@portageek.digitalroadkill.net> Content-Type: text/plain Organization: Message-Id: <1055368482.11067.152.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 11 Jun 2003 16:54:42 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4289 X-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 On Wed, 2003-06-11 at 16:41, Austin Gonyou wrote: > This would greatly help those of us possibly moving to ES or AS. :) Not unless Red Hat included the necessary core patches... Any kernel module we build is still tied to the specific kernel it was built against. It's just that if we release kernel-2.4.20-18.9sgi1, we can release xfs-modules-1.3pre1, xfs-modules-1.3pre2, etc against it. That module still won't have anything to do with a 2.4.9 ES kernel. So you can change the xfs module that loads into a given kernel, but you can't throw any old kernel against a given xfs module. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Wed Jun 11 15:04:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 15:04:28 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BM4M2x001878 for ; Wed, 11 Jun 2003 15:04:22 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5BMKfmO000337 for ; Wed, 11 Jun 2003 17:20:41 -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 h5BM4GqX4235743; Wed, 11 Jun 2003 17:04:16 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5BM4GRn113684244; Wed, 11 Jun 2003 17:04:16 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5BM4GU16424; Wed, 11 Jun 2003 17:04:16 -0500 Subject: Re: [PATCH] Give logbufs a better default From: Steve Lord To: Andi Kleen Cc: linux-xfs@oss.sgi.com, Chris Mason In-Reply-To: <20030611212822.GA8166@wotan.suse.de> References: <20030611093525.GA2329@wotan.suse.de> <1055363594.6614.44.camel@jen.americas.sgi.com> <20030611212822.GA8166@wotan.suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1055369055.6611.95.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 11 Jun 2003 17:04:15 -0500 X-archive-position: 4290 X-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 On Wed, 2003-06-11 at 16:28, Andi Kleen wrote: > On Wed, Jun 11, 2003 at 03:33:14PM -0500, Steve Lord wrote: > > On Wed, 2003-06-11 at 04:35, Andi Kleen wrote: > > > A long standing problem in XFS is that in the default configuration > > > metadata performance is not that great because it uses not enough > > > log buffers. There are FAQs around to fix this, but it would be better > > > if the kernel did the right thing by default. > > > > > > The main problem is probably that XFS still uses the default from the > > > early 90ies, which are probably not that good anymore for today's machines. > > > > > > This patch changes the logbufs= default based on the available memory. > > > If you have 128MB or less it uses 3 logbufs (normally 96K per file system) > > > For 400MB or less it uses 5 (160K) > > > For anything bigger 8 (256K) > > > > Hi Andi, > > > > Just wondering why you picked odd numbers? > > Usual handwaving. Of course i should have picked power of two just to > make it look more scientific, but the range was a bit too small for that ;) > > 3 was the old default, which seems ok for small systems. Small system > is arbitarily defined as <= 128MB memory. 2 was the default, but OK. > > 8 is the current maximum (is there a reason for that btw? could it be simply > raised?) It could be. > > I wanted to get 8 on my 512MB test box. And usually the memory counting > variable has some loss, so I choose 400MB as the boundary. > > 5 is somewhere between 3 and 8 for the boxes inbetween. > > > > > > > > > It is still a kind of bandaid. I think the better solution would be to > > > dynamically allocate new log buffers as needed until some limit > > > (and block if the memory cannot be allocated). This should not be that > > > bad because vmalloc/vfree are not that expensive anymore and with some > > > luck you can even get a physically continuous buffer (e.g. on a 16byte page size > ^^^KByte > of course > > > > ia64 system) > > > > Interesting idea, one issue is that during recovery, the maximum amount > > of outstanding I/O there might of been (i.e. number of iclog buffers) > > is a factor in how much work there is to do. Adding new ones dynamically > > Hmm, I thought that recovery work was bounded by the on disk log size? How do > the pending buffers come into play? They look more likely to make > you lose a bit more data in case of a crash, but your new sync daemon > with a timer should take care of that (it will still be much better > with this than it was ever before) > > Processing 10MB (new minimum with the mkfs patch for 1GB+) or even 64MB > at mount shouldn't be a big issue on a modern box. Without going and looking at the code again, I think the issue is that we have to do an extra scan over MAX_ICLOG_SIZE*MAX_ICLOG_NUM log space looking at each 512 byte header and ensuring that it all made it out to disk. There is also code to zero forwards from the head of the log found during recovery to write over any out of order writes which might have made it out to disk during the last mount. If the zeroing is not done then it is possible that we could crash again, and during recovery this time recognize that chunk of log from mount -2 and being from mount -1 and replay it incorrectly. > > > > might be possible, but there is this 'interesting' state machine on the > > log buffers to deal with there. > > I have not really looked into the state machine yet. You are saying > it has some scalability problems with more buffers or are the data structures > just nasty enough to adding more buffers dynamically could be difficult? > Not scalability, the log buffers are really just a pipeline between transactions and the on disk log, making it longer is always possible. Its just a matter of working out where it is safe to insert one (and delete one for that matter) whilst the state machine is active. Take a look at xlog_state_do_callback, not as bad as xfs mkfs ;-) Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Wed Jun 11 16:29:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 16:29:56 -0700 (PDT) Received: from shell.wgops.com (postfix@dsl092-192-108.sea1.dsl.speakeasy.net [66.92.192.108]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5BNTb2x005499 for ; Wed, 11 Jun 2003 16:29:37 -0700 Received: from [10.1.2.77] (jobe.wgops.com [10.1.2.77]) by shell.wgops.com (Postfix) with ESMTP id 6A69D4; Wed, 11 Jun 2003 17:29:36 -0600 (MDT) Date: Wed, 11 Jun 2003 17:29:33 -0600 From: Michael Loftis To: Austin Gonyou Cc: XFS List Subject: Re: XFS feature request Message-ID: <74613418.1055352573@[10.1.2.77]> In-Reply-To: <1055367128.2003.57.camel@portageek.digitalroadkill.net> References: <86984947.1054766968@[10.1.2.77]> <1055367128.2003.57.camel@portageek.digitalroadkill.net> 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-archive-position: 4291 X-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 True...There may be situations where having the filesystem degrade into nothing more than a semi-useful source of random entropy for PRNG may be ok :) --On Wednesday, June 11, 2003 4:32 PM -0500 Austin Gonyou wrote: > Given the path of comments here. I'd say that's why the ext2 FS has 3 > options for error handling! :) > > On Wed, 2003-06-04 at 23:49, Michael Loftis wrote: >> Mostly I'd much prefer the option of just going R/O on a filesystem, >> living >> with the possibility that what I'm *reading* isn't right than a whole >> system just going black and having to get onself physically present to >> ascertain the problem. >> >> I don't believe that unmounting the filesystem is *always* the right >> thing >> to do. It is in some cases, but there are cases where you'd much >> rather >> the system just went read-only and refused to flush anything off to >> it. >> >> --On Wednesday, June 04, 2003 2:02 PM -0600 Andrew Mathews >> wrote: >> >> > -----BEGIN PGP SIGNED MESSAGE----- >> > Hash: SHA1 >> > >> > Michael Loftis wrote: >> >| This has also recently been a problem for us. The whole 'something >> >| looks a little odd so I'm going to just tank and take the whole >> system >> >| with me' knee-jerk reaction XFS has is very problematic. It's the >> >| biggest reason I'm moving operations away from it. >> >| >> >| --On Wednesday, June 04, 2003 20:26 +0200 Seth Mos >> >> >| wrote: >> >| >> >|> Hello, >> >|> >> >|> Upon a filesystem error the XFS filesystem normally unmounts the >> fs and >> >|> often takes the box along with it. >> >|> ... >> >| >> >| -- >> >| Michael Loftis >> >| Modwest Sr. Systems Administrator >> >| Powerful, Affordable Web Hosting >> >| >> > >> > Not to diminish Set's original request, but to address this >> comment... >> > >> > I guess your term "knee-jerk reaction" is subjective. I'd much >> rather >> > have a recoverable system than an unrecoverable one, which is >> exactly >> > what you'll have if the filesystem is put into an unstable state >> > (corruption) and isn't intelligent enough to protect itself from >> further >> > damage. It's also one of the reasons we won't use anything other >> than >> > XFS in a production environment. >> > >> > - -- >> > Andrew Mathews >> > - >> --------------------------------------------------------------------- >> > ~ 1:56pm up 5 days, 4:49, 12 users, load average: 1.16, 1.13, >> 1.09 >> > - >> --------------------------------------------------------------------- >> > A statesman is a politician who's been dead 10 or 15 years. >> > -- Harry S. Truman >> > - -- >> > -----BEGIN PGP SIGNATURE----- >> > Version: GnuPG v1.0.7 (GNU/Linux) >> > Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org >> > >> > iD8DBQE+3lBHidHQ0m/kEssRAhouAJwJPdLuIKyUzmxSAj2nySsT2zCGfgCeO4lf >> > 33cLIwDjO7/T/iY8LSDp5qQ= >> > =T97e >> > -----END PGP SIGNATURE----- >> > >> > >> >> > -- > Austin Gonyou > Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Wed Jun 11 17:12:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 17:13:04 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5C0Co2x007365 for ; Wed, 11 Jun 2003 17:12:50 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5B4OZtm006890 for ; Tue, 10 Jun 2003 21:24:36 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id h5B4NQA05645; Wed, 11 Jun 2003 14:23:26 +1000 Date: Wed, 11 Jun 2003 14:23:26 +1000 From: Keith Owens Message-Id: <200306110423.h5B4NQA05645@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade XFS to 2.4.21-rc8 X-archive-position: 4292 X-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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Upgrade XFS to 2.4.21-rc8 Date: Tue Jun 10 21:17:38 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/kaos/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:150861a linux/mm/memory.c - 1.81 linux/fs/ext2/balloc.c - 1.17 linux/drivers/char/rocket_int.h - 1.4 linux/Makefile - 1.191 linux/include/linux/iobuf.h - 1.17 linux/mm/shmem.c - 1.35 From owner-linux-xfs@oss.sgi.com Wed Jun 11 18:59:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 19:00:11 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5C1xp2x011582 for ; Wed, 11 Jun 2003 18:59:51 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5AKtRtm023862 for ; Tue, 10 Jun 2003 13:55:27 -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 h5AKtQqX4065301 for ; Tue, 10 Jun 2003 15:55:27 -0500 (CDT) Received: from penguin.americas.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 h5AKtQRn109373045 for ; Tue, 10 Jun 2003 15:55:26 -0500 (CDT) From: Steve Lord Received: by penguin.americas.sgi.com (8.11.6/SGI-client-1.7) id h5AKrXU23274; Tue, 10 Jun 2003 15:53:33 -0500 Message-Id: <200306102053.h5AKrXU23274@penguin.americas.sgi.com> Date: Tue, 10 Jun 2003 15:53:33 -0500 Subject: TAKE - break dependency between CONFIG_PROCFS and CONFIG_SYSCTL in xfs To: linux-xfs@oss.sgi.com X-archive-position: 4293 X-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 This is 2.4, the 2.5 version which was reported will follow shortly Date: Tue Jun 10 13:54:23 PDT 2003 Workarea: penguin.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: 2.4.x-xfs:slinx:150782a linux/fs/xfs/linux/xfs_sysctl.h - 1.13 - move clear stats sysctl to the end linux/fs/xfs/linux/xfs_sysctl.c - 1.20 - make the clear stats interface conditional on procfs, the only way we display stats is via procfs anyway. From owner-linux-xfs@oss.sgi.com Wed Jun 11 23:58:48 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Jun 2003 23:59:07 -0700 (PDT) Received: from smtpzilla5.xs4all.nl (smtpzilla5.xs4all.nl [194.109.127.141]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5C6wk2x024716 for ; Wed, 11 Jun 2003 23:58:47 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.28]) by smtpzilla5.xs4all.nl (8.12.9/8.12.9) with ESMTP id h5C6wgZq052589; Thu, 12 Jun 2003 08:58:42 +0200 (CEST) Message-Id: <4.3.2.7.2.20030612084340.04047428@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jun 2003 08:58:38 +0200 To: Michael Loftis , Austin Gonyou From: Seth Mos Subject: Re: XFS feature request Cc: XFS List In-Reply-To: <74613418.1055352573@[10.1.2.77]> References: <1055367128.2003.57.camel@portageek.digitalroadkill.net> <86984947.1054766968@[10.1.2.77]> <1055367128.2003.57.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4294 X-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 At 17:29 11-6-2003 -0600, Michael Loftis wrote: >True...There may be situations where having the filesystem degrade into >nothing more than a semi-useful source of random entropy for PRNG may be ok :) > >--On Wednesday, June 11, 2003 4:32 PM -0500 Austin Gonyou > wrote: > >>Given the path of comments here. I'd say that's why the ext2 FS has 3 >>options for error handling! :) The rootfs should remount ro so the box doesn't die instantly and takes down the entire machine. This is exactly what happened here once. The duplicate inode was not found by tar but xfsdump did a bulkstat and noticed it. Because of this the rootfs unmounted and caused all 40 users to be effectively kicked off the machine which is not very nice. In my opinion the rootfs should be the last to dissapear and be remounted ro instead. If the other volumes take a nose dive that's ok, but I _need_ to have at least my root filesystem to fix something. In this case the corruption must have been there for at least 6 months or so and we didn't even notice. The rootfs is completely backuped every day by tar which was not enough for XFS to notice it was there. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Thu Jun 12 01:59:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 01:59:05 -0700 (PDT) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.58.33]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5C8wx2x031560 for ; Thu, 12 Jun 2003 01:59:00 -0700 Received: from Shiva (shiva [192.168.3.20]) by ishtar.tlinx.org (8.12.6/8.12.2/SuSE Linux 0.6) with ESMTP id h5C8wrMO019112 for ; Thu, 12 Jun 2003 01:58:53 -0700 From: "l.a walsh" To: Subject: RE: XFS/XP Dual Boot? Date: Thu, 12 Jun 2003 01:58:47 -0700 Message-ID: <001201c330c0$d5eb2f40$1403a8c0@sc.tlinx.org> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 In-Reply-To: <1055355202.6325.4.camel@rose.americas.sgi.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-archive-position: 4295 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xfs@tlinx.org Precedence: bulk X-list: linux-xfs This is all handled transparently by the SuSE installation process. Just check that you want XFS for all your linux partitions, tell hit by how much you want it to shrink your win partition, and let it go. It installs all the appropriate loader info in the right places and sets up the config files to allow booting into win or lin. It's so simple, even my mom could do it. Perhaps you are using a more primitive Distro? :-) -linda > -----Original Message----- > From: linux-xfs-bounce@oss.sgi.com > [mailto:linux-xfs-bounce@oss.sgi.com] On Behalf Of Russell Cattelan > Sent: Wed, Jun 11, 2003 11:13a > To: linux-xfs@oss.sgi.com > Subject: Re: XFS/XP Dual Boot? > > > On Wed, 2003-06-11 at 13:03, Florin Andrei wrote: > > On Tue, 2003-06-10 at 22:46, Chris Wedgwood wrote: > > > On Tue, Jun 10, 2003 at 05:30:40PM -0700, Michael Whang wrote: > > > > > > > Has anyone successfully dual booted XFS with windows > XP? Please let > > > > me know if so and how. > > > > > > I did I a long time ago (no windows now)... I don't > recall any issues > > > but you will need to install your boot-loader in the MBR > as XFS stores > > > the first superblock in the first sector of the partition > which some > > > bootloaded need to be told about. > > > > If you have a small /boot partition (which is usually > recommended) then > > you can format it Ext3 (or even Ext2 mounted sync), declare > it bootable > > and install the bootloader in its superblock. > > That's basically what i almost always do. > swap will also work. > although you need to make it type 0x83 to install the boot > block and then switch it back to a swap partition. > > > > From owner-linux-xfs@oss.sgi.com Thu Jun 12 03:21:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 03:21:40 -0700 (PDT) Received: from pao-ex01.pao.digeo.com (pao-ex01.pao.digeo.com [12.47.58.20]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CALP2x003415 for ; Thu, 12 Jun 2003 03:21:26 -0700 Received: from mnm ([172.17.144.18]) by pao-ex01.pao.digeo.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 12 Jun 2003 03:21:20 -0700 Date: Thu, 12 Jun 2003 03:22:19 -0700 From: Andrew Morton To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - fix O_DIRECT and uninitialized user memory Message-Id: <20030612032219.1842b0a2.akpm@digeo.com> In-Reply-To: <200306111559.h5BFx0m15358@jen.americas.sgi.com> References: <200306111559.h5BFx0m15358@jen.americas.sgi.com> X-Mailer: Sylpheed version 0.9.0pre1 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Jun 2003 10:21:20.0607 (UTC) FILETIME=[5E0FEEF0:01C330CC] X-archive-position: 4296 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: akpm@digeo.com Precedence: bulk X-list: linux-xfs Steve Lord wrote: > > - In pagebuf_lookup, create a pagebuf which is lockable so we > do not lock the pages within it during I/O. Only O_DIRECT > does I/O on this type of pagebuf. oops. What happens if an application passes multiple presentations of the same page into a single non-O_DIRECT write() or read()? ie: mmap(buf, 4096, PROT_READ, MAP_FIXED, fd1, 0); mmap(buf+4096, 4096, PROT_READ, MAP_FIXED, fd1, 0); write(fd2, buf, 8192); ? From owner-linux-xfs@oss.sgi.com Thu Jun 12 03:25:17 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 03:25:20 -0700 (PDT) Received: from pao-ex01.pao.digeo.com (pao-ex01.pao.digeo.com [12.47.58.20]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CAPH2x003889 for ; Thu, 12 Jun 2003 03:25:17 -0700 Received: from mnm ([172.17.144.18]) by pao-ex01.pao.digeo.com with Microsoft SMTPSVC(5.0.2195.5329); Thu, 12 Jun 2003 03:25:12 -0700 Date: Thu, 12 Jun 2003 03:26:11 -0700 From: Andrew Morton To: lord@sgi.com, linux-xfs@oss.sgi.com Subject: Re: TAKE - fix O_DIRECT and uninitialized user memory Message-Id: <20030612032611.6247b44e.akpm@digeo.com> In-Reply-To: <20030612032219.1842b0a2.akpm@digeo.com> References: <200306111559.h5BFx0m15358@jen.americas.sgi.com> <20030612032219.1842b0a2.akpm@digeo.com> X-Mailer: Sylpheed version 0.9.0pre1 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Jun 2003 10:25:12.0291 (UTC) FILETIME=[E8281B30:01C330CC] X-archive-position: 4297 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: akpm@digeo.com Precedence: bulk X-list: linux-xfs Andrew Morton wrote: > > oops. > > What happens if an application passes multiple presentations of > the same page into a single non-O_DIRECT write() or read()? > > ie: > > mmap(buf, 4096, PROT_READ, MAP_FIXED, fd1, 0); > mmap(buf+4096, 4096, PROT_READ, MAP_FIXED, fd1, 0); > write(fd2, buf, 8192); oops. Forget I said that. I'll go back to sleep now. From owner-linux-xfs@oss.sgi.com Thu Jun 12 03:40:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 03:41:16 -0700 (PDT) Received: from students.fct.unl.pt ([193.136.120.10]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CAev2x004833 for ; Thu, 12 Jun 2003 03:40:58 -0700 Received: from localhost (pjsm@localhost) by students.fct.unl.pt (8.11.6/8.11.6) with ESMTP id h5CAeHF27815; Thu, 12 Jun 2003 11:40:18 +0100 X-Authentication-Warning: students.fct.unl.pt: pjsm owned process doing -bs Date: Thu, 12 Jun 2003 11:40:17 +0100 (WEST) From: Paulo Matos To: Eric Sandeen cc: "Bryan J. Smith" , Austin Gonyou , Seth Mos , XFS List Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 In-Reply-To: <1055368250.11070.148.camel@stout.americas.sgi.com> 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 h5CAeHF27815 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5CAex2x004846 X-archive-position: 4298 X-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 On 11 Jun 2003, Eric Sandeen wrote: > > Does 2.5/2.6 completely take care of providing these interfaces? > > XFS is in 2.5, so it's mostly a moot point. It's possible that from > time to time, updated XFS in CVS will require a kernel change that is > not in Linus' tree, of course. Does 2.6 will include XFS completely, or will we live with two branches, one on kernel tree and another side away? A little off-topic question, anyone know if there is an expected release date for 2.6? -- 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 Jun 12 03:58:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 03:59:03 -0700 (PDT) Received: from K-7.stesmi.com (as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CAwv2x005820 for ; Thu, 12 Jun 2003 03:58:59 -0700 Received: from stesmi.com (as4-1-7.has.s.bonet.se [217.215.31.238]) by K-7.stesmi.com (8.12.8/8.12.5) with ESMTP id h5CAwi8Y028074; Thu, 12 Jun 2003 12:58:45 +0200 Message-ID: <3EE85CE4.4060203@stesmi.com> Date: Thu, 12 Jun 2003 12:58:44 +0200 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paulo Matos CC: Eric Sandeen , "Bryan J. Smith" , Austin Gonyou , Seth Mos , XFS List Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-RAVMilter-Version: 8.4.2(snapshot 20021217) (K-7.stesmi.com) X-archive-position: 4299 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stesmi@stesmi.com Precedence: bulk X-list: linux-xfs Paulo Matos wrote: > On 11 Jun 2003, Eric Sandeen wrote: > > >>>Does 2.5/2.6 completely take care of providing these interfaces? >> >>XFS is in 2.5, so it's mostly a moot point. It's possible that from >>time to time, updated XFS in CVS will require a kernel change that is >>not in Linus' tree, of course. > > > Does 2.6 will include XFS completely, or will we live with two > branches, one on kernel tree and another side away? > A little off-topic question, anyone know if there is an expected > release date for 2.6? > The way things usually work in the linux kernel world is that something goes in to the kernel. The main work is done outside the main tree and fixes and changes are moved at times from the development tree (if you call it that) and in to the main kernel tree (linus' tree). Examples of that: ACPI, pcmcia, USB and I can go on and on .. // Stefan From owner-linux-xfs@oss.sgi.com Thu Jun 12 04:01:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 04:01:29 -0700 (PDT) Received: from smtpzilla5.xs4all.nl (smtpzilla5.xs4all.nl [194.109.127.141]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CB1N2x006361 for ; Thu, 12 Jun 2003 04:01:24 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.28]) by smtpzilla5.xs4all.nl (8.12.9/8.12.9) with ESMTP id h5CB185V002909; Thu, 12 Jun 2003 13:01:09 +0200 (CEST) Message-Id: <4.3.2.7.2.20030612125805.0352e038@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jun 2003 13:00:48 +0200 To: Paulo Matos , Eric Sandeen From: Seth Mos Subject: Re: 2.4.20-18 Red Hat errata kernel with XFS 1.2.0 Cc: "Bryan J. Smith" , Austin Gonyou , XFS List In-Reply-To: References: <1055368250.11070.148.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4300 X-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 At 11:40 12-6-2003 +0100, Paulo Matos wrote: >On 11 Jun 2003, Eric Sandeen wrote: > > > > Does 2.5/2.6 completely take care of providing these interfaces? > > > > XFS is in 2.5, so it's mostly a moot point. It's possible that from > > time to time, updated XFS in CVS will require a kernel change that is > > not in Linus' tree, of course. > > Does 2.6 will include XFS completely, or will we live with two >branches, one on kernel tree and another side away? XFS filesystems are included although I think dmapi is excluded untill it is usable on multiple filesystems. It should be inline with current CVS. CVS might be a little ahead since that is what the developers commit to. > A little off-topic question, anyone know if there is an expected >release date for 2.6? My best guess is somewhere this fall... 11 oct 2003?? Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Thu Jun 12 05:36:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 05:37:19 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CCav2x010463 for ; Thu, 12 Jun 2003 05:36: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.2/linux-outbound_gateway-1.2) with ESMTP id h59FAGtm007093 for ; Mon, 9 Jun 2003 08:10:17 -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 h59FAGqX3858832 for ; Mon, 9 Jun 2003 10:10:16 -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 h59FAFYk11696289 for ; Mon, 9 Jun 2003 10:10:16 -0500 (CDT) Subject: Re: error when patching redhat 2.4.20-18.9 with xfs 1.3-pre1 From: Eric Sandeen To: linux-xfs@oss.sgi.com In-Reply-To: <3EE49972.D89B83D6@online.no> References: <3EE49972.D89B83D6@online.no> Content-Type: text/plain Organization: Message-Id: <1055171415.23002.16.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 09 Jun 2003 10:10:15 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4301 X-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 I think I see the problem; the rpms on the web site are actually 2.4.20-13.7 or 13.8, you have 18.9, and there are a few different patches in there (rh 7 & 8 vs. rh 9). I'll talk to Russell today. -Eric From owner-linux-xfs@oss.sgi.com Thu Jun 12 07:39:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 07:39:54 -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.9) with SMTP id h5CEdd2x013814 for ; Thu, 12 Jun 2003 07:39:39 -0700 Received: from comcast.net (localhost [127.0.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id 25FED74A02 for ; Thu, 12 Jun 2003 07:39:34 -0700 (PDT) Message-ID: <3EE890A6.8030300@comcast.net> Date: Thu, 12 Jun 2003 07:39:34 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030605 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linux XFS Mailing List Subject: xfsdump man page X-Enigmail-Version: 0.74.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4302 X-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 Just wanted to comment on the man page for xfsdump. We recently needed to exclude some files from out nightly backups, so rather than specifiy which dirs to backup/exclude, I tried to use the SKIP_FILE attribute. After setting the attr, the backup proceeded as normal and included the supposedly excluded files. The problem I had, was that under the -e section of the man page, the attr is specified as "SGI_XFS-DUMP_SKIP_FILE" when it really should be "SGI_XFSDUMP_SKIP_FILE". Looks like due to its placement it got hyphenated. Unfortunately, it's in double quotes and I read it is a literal. After correcting this, it works as expected. I did notice that if I had read the entire man page, there are examples of how to set this attr later on. The examples do use the correct attr, just not the section on -e. -Walt From owner-linux-xfs@oss.sgi.com Thu Jun 12 11:20:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 11:21:14 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CIKt2x028525 for ; Thu, 12 Jun 2003 11:20:56 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5CIbHmO023097 for ; Thu, 12 Jun 2003 13:37:17 -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 h5CIKnqX4353523 for ; Thu, 12 Jun 2003 13:20:49 -0500 (CDT) Received: from penguin.americas.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 h5CIKhRn112272481 for ; Thu, 12 Jun 2003 13:20:43 -0500 (CDT) From: Steve Lord Received: by penguin.americas.sgi.com (8.11.6/SGI-client-1.7) id h5CIIIm10218; Thu, 12 Jun 2003 13:18:18 -0500 Message-Id: <200306121818.h5CIIIm10218@penguin.americas.sgi.com> Date: Thu, 12 Jun 2003 13:18:18 -0500 Subject: TAKE - fix possible sleep under spinlock X-archive-position: 4303 X-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 Move the pagebuf_runall_queues out from under a spinlock, if it sleeps (which it might), this is not the right place for it to be. There is also no reason for it to be under a spinlock. Date: Thu Jun 12 11:19:25 PDT 2003 Workarea: penguin.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: 2.4.x-xfs:slinx:151032a linux/fs/xfs/pagebuf/page_buf.c - 1.121 - move pagebuf_runall_queues out from under the pbd_delwrite_lock spinlock. From owner-linux-xfs@oss.sgi.com Thu Jun 12 13:17:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 13:17:24 -0700 (PDT) Received: from poptart.bithose.com (ip-204-97-176-41.modem.logical.net [204.97.176.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5CKGu2x001521 for ; Thu, 12 Jun 2003 13:17:01 -0700 Received: from poptart.bithose.com (localhost [127.0.0.1]) by poptart.bithose.com (8.12.9/8.12.9) with ESMTP id h5CKGtkK126705 for ; Thu, 12 Jun 2003 16:16:55 -0400 (EDT) Received: from localhost (jakari@localhost) by poptart.bithose.com (8.12.9/8.12.9/Submit) with ESMTP id h5CKGt9x126662 for ; Thu, 12 Jun 2003 16:16:55 -0400 (EDT) X-Authentication-Warning: poptart.bithose.com: jakari owned process doing -bs Date: Thu, 12 Jun 2003 16:16:55 -0400 (EDT) From: Jameel Akari To: Subject: Re: xfsdump problems (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4304 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jakari@bithose.com Precedence: bulk X-list: linux-xfs Forgot to reply also to list.. some more followups... On Thu, 12 Jun 2003, Axel Thimm wrote: > On Wed, Jun 11, 2003 at 03:41:48PM -0400, Jameel Akari wrote: > > > > xfsdump installed from RPM (from oss.sgi.com), > > version 2.2.3-1 > > > > When attempting to run a dump (local or remote) it aborts with: > > xfsdump: drive_scsitape.c:1985: do_get_write_buf: Assertion > > `contextp->dc_nextp < contextp->dc_recendp' failed. > Does this bug also show up with the xfsdump from http://atrpms.physik.fu-berlin.de/? Yes, same result. I actually need this to work on RH7.3 clients, so 8.0 RPMS won't help there. Interestingly, this is not a problem when using the DLT-IV drive, just the 8mm drive. I backed up about 10GB worth on the DLT-IV without a problem, using xfsdump 2.2.3. The 8mm drive seems to work with tar; mt doesn't show anything interesting going on. Could the fact that the 8mm advertises a fixed block size and/or is compressed make a difference? I'm just guessing at this point. Not to confuse things too much, but I can't get remote backups using ssh to work on the DLT drive either. This is currently more critical than the old slow 8mm job.. local backups on the DLT work great; remote with ssh gives you: ... xfsdump: cannot determine tape block size after two tries xfsdump: assuming media is corrupt or contains non-xfsdump data xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump media file header at beginning of media It seems that it can't tell what blocksize the device is.. but DLT is variable-length blocksize. I am using the syntax: #xfsdump -v5 -f root@spoonman:/dev/st1 /boot On the server attached to the DLT I see: Jun 11 17:17:04 spoonman kernel: st1: Failed to read 1048576 byte block with 245760 byte read. If I crank up debugging on the remote xfsdump (RMTSTATUS=2, -v5) I see: xfsdump: tape op: opening drive rmtopen: RMTHOST(0) = Linux rmtcommand: fd = 0, buf = O/dev/st1 2 xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: hdr_mfilesz 0Mb, min_recmfilesize 0Mb, fsize 256Mb, marksep 16Mb xfsdump: recommended tape media file size set to 0x10000000 bytes xfsdump: recommended tape media mark separation set to 0x1000000 bytes xfsdump: determining tape record size: trying 245760 (0x3c000) bytes xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: tape positioned at BOT: doing redundant rewind xfsdump: tape op: rewind 0 rmtcommand: fd = 0, buf = I6 0 xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: tape op: reading 245760 bytes rmtcommand: fd = 0, buf = R245760 xfsdump: tape op read of 245760 bytes failed: errno == 12 (Cannot allocate memory) xfsdump: read returned ENOMEM: trying new record size xfsdump: determining tape record size: trying 2097152 (0x200000) bytes xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = onl xfsdump: tape position unknown: searching backward for file mark or BOT xfsdump: tape op: get fileno rmtcommand: fd = 0, buf = S xfsdump: In first file, do a rewind to achieve bsf xfsdump: tape op: rewind 0 rmtcommand: fd = 0, buf = I6 0 xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: tape positioned at BOT: doing redundant rewind xfsdump: tape op: rewind 0 rmtcommand: fd = 0, buf = I6 0 xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: tape op: reading 2097152 bytes rmtcommand: fd = 0, buf = R2097152 xfsdump: tape op read of 2097152 bytes short: nread == 1048576 xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = onl xfsdump: nread less than selected record size on fixed blocksize drive indicates wrong blocksize xfsdump: cannot determine tape block size after two tries xfsdump: assuming media is corrupt or contains non-xfsdump data xfsdump: tape op: rewind 0 rmtcommand: fd = 0, buf = I6 0 xfsdump: tape op: get status rmtcommand: fd = 0, buf = S xfsdump: tape status = bot onl xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump media file header at beginning of media xfsdump: content.c: 5884: mlog_exit_hint called: hint: CORRUPTION (corrupt data encountered) The tape is fine; it has locally-generated xfsdumps on it. I'm going to try -b 1048576 but that seems wrong somehow.. it really should figure it out on its own. From owner-linux-xfs@oss.sgi.com Thu Jun 12 18:32:14 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 18:32:27 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5D1WD2x014860 for ; Thu, 12 Jun 2003 18:32:14 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5D1mYmO016562 for ; Thu, 12 Jun 2003 20:48:35 -0500 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 h5D1UlQd4080037 for ; Fri, 13 Jun 2003 11:30:47 +1000 (EST) Received: (from ivanr@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5D1Uli94091974 for linux-xfs@oss.sgi.com; Fri, 13 Jun 2003 11:30:47 +1000 (EST) Date: Fri, 13 Jun 2003 11:30:47 +1000 (EST) From: Ivan Rayner Message-Id: <200306130130.h5D1Uli94091974@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - linux-xfs: xfsdump man page X-archive-position: 4305 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ivanr@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Stop the hyphenation of SGI_XFSDUMP_SKIP_FILE attribute name in the xfsdump.8 manpage. Ivan Date: Thu Jun 12 18:29:21 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/ivanr/isms/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:151117a cmd/xfsdump/man/man8/xfsdump.8 - 1.12 - stop hyphenation of SGI_XFSDUMP_SKIP_FILE attribute name From owner-linux-xfs@oss.sgi.com Thu Jun 12 19:47:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 19:47:31 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5D2lH2x017092 for ; Thu, 12 Jun 2003 19:47:18 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5D33fmO017992 for ; Thu, 12 Jun 2003 22:03:41 -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 h5D2lCqX4403796 for ; Thu, 12 Jun 2003 21:47:12 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5D2lBRn114346008 for ; Thu, 12 Jun 2003 21:47:11 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5D2lBY21779; Thu, 12 Jun 2003 21:47:11 -0500 Message-Id: <200306130247.h5D2lBY21779@jen.americas.sgi.com> Date: Thu, 12 Jun 2003 21:47:11 -0500 Subject: TAKE - fix deadlock from new sync code changes To: linux-xfs@oss.sgi.com X-archive-position: 4306 X-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 Fix deadlock caused by race between xfs_iunpin marking an inode dirty, and the same inode being reallocated and reused by create. The unlock_new_inode and mark_inode_dirty manage to corrupt the i_state flags and end up leaving I_LOCK|I_NEW set. Date: Thu Jun 12 19:46:25 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: 2.4.x-xfs:slinx:151120a linux/fs/xfs/xfs_inode.c - 1.377 - do not call mark_inode_dirty in xfs_iunpin when I_NEW is set, it is in the process of going into a transaction which will also mark it dirty. From owner-linux-xfs@oss.sgi.com Thu Jun 12 20:11:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 20:12:07 -0700 (PDT) Received: from zok.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5D3Bk2x017868 for ; Thu, 12 Jun 2003 20:11:47 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5D3Be3X030747 for ; Thu, 12 Jun 2003 20:11:41 -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 h5D3BeqX4405664 for ; Thu, 12 Jun 2003 22:11:40 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5D3BeRn111179428 for ; Thu, 12 Jun 2003 22:11:40 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5D3Bel22631; Thu, 12 Jun 2003 22:11:40 -0500 Message-Id: <200306130311.h5D3Bel22631@jen.americas.sgi.com> Date: Thu, 12 Jun 2003 22:11:40 -0500 Subject: TAKE - inode create / reclaim deadlock To: linux-xfs@oss.sgi.com X-archive-position: 4307 X-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 Fix deadlock between xfs_finish_reclaim and xfs_iget_core. An inode being reclaimed and removed from memory by one thread while another thread is attempting to reuse the inode and bring it back to life. There was a window between the iget starting to reuse the inode and the reclaim starting. Close the window by marking the inode as being reused under the hash lock, and by abandoning the reclaim if this is detected when it obtains the hash lock. This has been around for a long time, but I can only hit it with 4 cpus and a lot of parallel create/remove activity - and the new sync code. Date: Thu Jun 12 20:08:42 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: 2.4.x-xfs:slinx:151123a linux/fs/xfs/xfs_vnodeops.c - 1.592 - Set XFS_IRECLAIMABLE when disconnecting an xfs_inode from the linux inode. This is safe from the iget path because of the I_LOCK which is held in both cases. In xfs_finish_reclaim, after obtaining the hash lock, check that XFS_IRECLAIMABLE is set in the case where there is no vnode, abandon the reclaim if it is not. We can also reduce the locking use in a couple of paths here. linux/fs/xfs/xfs_iget.c - 1.189 - When a candidate inode is found in xfs_iget_core which has the potential to be reclaimed, remove the XFS_IRECLAIMABLE flag under the inode hash lock. linux/fs/xfs/xfs_inode.h - 1.182 - Define XFS_IRECLAIMABLE From owner-linux-xfs@oss.sgi.com Thu Jun 12 20:53:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 20:53:05 -0700 (PDT) Received: from kerberos.suse.cz (kerberos.suse.cz [195.47.106.10]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5D3qw2x019319 for ; Thu, 12 Jun 2003 20:52:59 -0700 Received: from chimera.suse.cz (chimera.suse.cz [10.20.0.2]) by kerberos.suse.cz (SuSE SMTP server) with ESMTP id 2BF0883153 for ; Wed, 11 Jun 2003 14:35:20 +0200 (CEST) Received: from alienAngel.upjs.sk (test12.suse.cz [10.20.3.140]) by chimera.suse.cz (Postfix) with ESMTP id 2AD294538 for ; Wed, 11 Jun 2003 14:33:57 +0200 (CEST) Received: from localhost (ja@localhost) by alienAngel.upjs.sk (8.12.6/8.12.6/Submit) with ESMTP id h5BCWXGh018645 for ; Wed, 11 Jun 2003 14:32:33 +0200 X-Authentication-Warning: alienAngel.home.sk: ja owned process doing -bs Date: Wed, 11 Jun 2003 14:32:33 +0200 (CEST) From: Jan Derfinak X-X-Sender: ja@alienAngel.home.sk To: linux-xfs@oss.sgi.com Subject: Re: tape backup tool ? In-Reply-To: <20030611054308.GA7800@dingdong.cryptoapps.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4308 X-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 On Wed, 11 Jun 2003, Chris Wedgwood wrote: > On Wed, Jun 11, 2003 at 08:59:11AM +0500, Dmitry Melekhov wrote: > > > Hmm. Sorry for such stupid question... Is it possible to restore one > > file from tape with xfsrestore? > > You can specify a subtree with -s Or use -i (interactive) option. Select file(s) and restore it. jan -- From owner-linux-xfs@oss.sgi.com Thu Jun 12 22:45:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 22:46:18 -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.9) with SMTP id h5D5jt2x023020 for ; Thu, 12 Jun 2003 22:45: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 DED074E256; Fri, 13 Jun 2003 07:45:46 +0200 (CEST) Received: from ssba-bsl.ch.sauter-bc.com (ssba-bsl.ch.sauter-bc.com [10.1.6.20]) by mailhub.ch.sauter-bc.com (Postfix) with ESMTP id 9929B32CCF; Fri, 13 Jun 2003 07:45:46 +0200 (CEST) Received: from ch.sauter-bc.com (sup.ch.sauter-bc.com [10.1.200.117]) by ssba-bsl.ch.sauter-bc.com (Postfix) with ESMTP id 2CEDD30881D; Fri, 13 Jun 2003 07:45:46 +0200 (CEST) Message-ID: <3EE9650A.914C6998@ch.sauter-bc.com> Date: Fri, 13 Jun 2003 07:45:46 +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 MIME-Version: 1.0 To: Jameel Akari Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump problems (fwd) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4309 X-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 Jameel Akari schrieb: > > Forgot to reply also to list.. some more followups... > > On Thu, 12 Jun 2003, Axel Thimm wrote: > > > On Wed, Jun 11, 2003 at 03:41:48PM -0400, Jameel Akari wrote: > > > > > > xfsdump installed from RPM (from oss.sgi.com), > > > version 2.2.3-1 > > > > > > When attempting to run a dump (local or remote) it aborts with: > > > xfsdump: drive_scsitape.c:1985: do_get_write_buf: Assertion > > > `contextp->dc_nextp < contextp->dc_recendp' failed. > > > Does this bug also show up with the xfsdump from http://atrpms.physik.fu-berlin.de/? > > Yes, same result. I actually need this to work on RH7.3 clients, so 8.0 > RPMS won't help there. > > Interestingly, this is not a problem when using the DLT-IV drive, just the > 8mm drive. I backed up about 10GB worth on the DLT-IV without a problem, > using xfsdump 2.2.3. I remember similar problems when I tried xfsdump on DAT (DDS3) long time ago. I don't remember the problem but I remember that I just didn't get it to work. Using DLT on the same box worked without problem. Simon > > The 8mm drive seems to work with tar; mt doesn't show anything > interesting going on. Could the fact that the 8mm advertises a fixed > block size and/or is compressed make a difference? I'm just guessing at > this point. > > Not to confuse things too much, but I can't get remote backups using ssh > to work on the DLT drive either. This is currently more critical than the > old slow 8mm job.. local backups on the DLT work great; remote with ssh > gives you: > ... > xfsdump: cannot determine tape block size after two tries > xfsdump: assuming media is corrupt or contains non-xfsdump data > xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump > media file header at beginning of media > > It seems that it can't tell what blocksize the device is.. but DLT is > variable-length blocksize. I am using the syntax: > #xfsdump -v5 -f root@spoonman:/dev/st1 /boot > > On the server attached to the DLT I see: > > Jun 11 17:17:04 spoonman kernel: st1: Failed to read 1048576 byte block > with 245760 byte read. > > If I crank up debugging on the remote xfsdump (RMTSTATUS=2, -v5) I see: > > xfsdump: tape op: opening drive > rmtopen: RMTHOST(0) = Linux > rmtcommand: fd = 0, buf = O/dev/st1 > 2 > > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: hdr_mfilesz 0Mb, min_recmfilesize 0Mb, fsize 256Mb, marksep 16Mb > xfsdump: recommended tape media file size set to 0x10000000 bytes > xfsdump: recommended tape media mark separation set to 0x1000000 bytes > xfsdump: determining tape record size: trying 245760 (0x3c000) bytes > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: tape positioned at BOT: doing redundant rewind > xfsdump: tape op: rewind 0 > rmtcommand: fd = 0, buf = I6 > 0 > > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: tape op: reading 245760 bytes > rmtcommand: fd = 0, buf = R245760 > > xfsdump: tape op read of 245760 bytes failed: errno == 12 (Cannot allocate > memory) > xfsdump: read returned ENOMEM: trying new record size > xfsdump: determining tape record size: trying 2097152 (0x200000) bytes > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = onl > xfsdump: tape position unknown: searching backward for file mark or BOT > xfsdump: tape op: get fileno > rmtcommand: fd = 0, buf = S > xfsdump: In first file, do a rewind to achieve bsf > xfsdump: tape op: rewind 0 > rmtcommand: fd = 0, buf = I6 > 0 > > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: tape positioned at BOT: doing redundant rewind > xfsdump: tape op: rewind 0 > rmtcommand: fd = 0, buf = I6 > 0 > > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: tape op: reading 2097152 bytes > rmtcommand: fd = 0, buf = R2097152 > > xfsdump: tape op read of 2097152 bytes short: nread == 1048576 > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = onl > xfsdump: nread less than selected record size on fixed blocksize drive > indicates wrong blocksize > xfsdump: cannot determine tape block size after two tries > xfsdump: assuming media is corrupt or contains non-xfsdump data > xfsdump: tape op: rewind 0 > rmtcommand: fd = 0, buf = I6 > 0 > > xfsdump: tape op: get status > rmtcommand: fd = 0, buf = S > xfsdump: tape status = bot onl > xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump > media file header at beginning of media > xfsdump: content.c: 5884: mlog_exit_hint called: hint: CORRUPTION (corrupt > data encountered) > > The tape is fine; it has locally-generated xfsdumps on it. > > I'm going to try -b 1048576 but that seems wrong somehow.. it really > should figure it out on its own. From owner-linux-xfs@oss.sgi.com Thu Jun 12 23:05:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Jun 2003 23:05:23 -0700 (PDT) Received: from shell.wgops.com (postfix@dsl092-192-108.sea1.dsl.speakeasy.net [66.92.192.108]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5D64x2x024133 for ; Thu, 12 Jun 2003 23:05:01 -0700 Received: from [10.1.2.77] (jobe.wgops.com [10.1.2.77]) by shell.wgops.com (Postfix) with ESMTP id EF1A34; Fri, 13 Jun 2003 00:04:55 -0600 (MDT) Date: Fri, 13 Jun 2003 00:04:53 -0600 From: Michael Loftis To: Jameel Akari , linux-xfs@oss.sgi.com Subject: Re: xfsdump problems (fwd) Message-ID: <46075022.1055462693@[10.1.2.77]> In-Reply-To: References: 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-archive-position: 4310 X-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 FWIW -- in the past I've had to pipe through dd on the remote machine to get dump-to-tape to work. This was using tar and dump commands though... command looked soemthign like: tar zcvf - /dir | ssh $taper dd of=/dev/tape --On Thursday, June 12, 2003 4:16 PM -0400 Jameel Akari wrote: > > Forgot to reply also to list.. some more followups... > It seems that it can't tell what blocksize the device is.. but DLT is > variable-length blocksize. I am using the syntax: ># xfsdump -v5 -f root@spoonman:/dev/st1 /boot > > On the server attached to the DLT I see: > > Jun 11 17:17:04 spoonman kernel: st1: Failed to read 1048576 byte block > with 245760 byte read. > From owner-linux-xfs@oss.sgi.com Fri Jun 13 01:23:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 01:23:38 -0700 (PDT) Received: from sundancer.oche.de (sundancer.oche.de [194.94.252.29]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5D8ND2x029530 for ; Fri, 13 Jun 2003 01:23:14 -0700 Received: by sundancer.oche.de (Postfix, from userid 10) id 37FC951B9C; Fri, 13 Jun 2003 10:23:06 +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 h5D8DVGs023349 for ; Fri, 13 Jun 2003 10:13:31 +0200 (CEST) Received: (from news@localhost) by foehn.quickstep.oche.de (8.12.9/8.12.8/Submit) id h5D8DUVW023348 for linux-xfs@oss.sgi.com; Fri, 13 Jun 2003 10:13:30 +0200 (CEST) To: linux-xfs@oss.sgi.com Path: not-for-mail From: Martin Spott Newsgroups: list.linux-xfs Subject: Re: xfsdump problems (fwd) Date: 13 Jun 2003 08:13:29 GMT Organization: home Lines: 15 Message-ID: References: <46075022.1055462693@[10.1.2.77]> NNTP-Posting-Host: foehn.quickstep.oche.de X-Trace: foehn.quickstep.oche.de 1055492009 23334 192.168.48.2 (13 Jun 2003 08:13:29 GMT) X-Complaints-To: usenet@foehn.quickstep.oche.de NNTP-Posting-Date: 13 Jun 2003 08:13:29 GMT User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (SunOS/5.8 (sun4m)) X-archive-position: 4311 X-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 Michael Loftis wrote: > FWIW -- in the past I've had to pipe through dd on the remote machine to > get dump-to-tape to work. This was using tar and dump commands though... All these things remind me that I had lots of trouble with SCSI tape drives used for dumping Sybase databases on Linux to a tape. Writing with 'tar' usually worked pretty fine. I'm under the impression that 'xfsdump' and Sybase's 'backupserver' are triggering some sort of bug in the Linux SCSI and/oder tape driver that gets circumvented in certain situations (or with 'tar'), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Jun 13 05:54:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 05:54: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.9) with SMTP id h5DCsa2x013383 for ; Fri, 13 Jun 2003 05:54:37 -0700 Received: from puariko.homeip.net (pD9E7D8DC.dip.t-dialin.net [217.231.216.220]) by heretic.physik.fu-berlin.de (8.12.8/8.12.8) with ESMTP id h5DCsPFt002404 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 13 Jun 2003 14:54:27 +0200 Received: (from thimm@localhost) by puariko.nirvana (8.12.8/8.12.8/Submit) id h5DCsNZd014133; Fri, 13 Jun 2003 14:54:23 +0200 Date: Fri, 13 Jun 2003 14:54:23 +0200 From: Axel Thimm To: linux-xfs Subject: kernel-2.4.20-18.9.2atrpms: latest RHL 9 errata & XFS 1.2 Message-ID: <20030613125423.GA11990@puariko.nirvana> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-archive-position: 4312 X-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 --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have merged in the XFS patches from 1.2 into the latest release RedHat kernel for Red Hat 9. You can find them under http://atrpms.physik.fu-berlin.de/name/kernel/ The XFS enabled kernel for Red Hat 8.0 (based on kernel-2.4.18-27.8) is still available, but obsoleted due to security flaws. Sorry, I have no RH8.0 machines anymore to build/test 8.0 kernels. _Probably_ you can grab the src.rpm and simply rebuild on Red Hat 8.0. Note that there are also some additional patches. * base kernel sources: Taken from redhat errata (2.4.20-18.9) * XFS: merged patches found in 1.2 * i2c-2.7.0 and lm_sensors-2.7.0. You should also get the updated userland tools. * (note: only available upon request) 3ware kernel driver update for Escalade 7xxx series. Try to keep in sync with your firmware and userland tools. * v4l2-api (from http://bytesex.org/v4l/) Implemenation note: The XFS changes to the kernel*.config files have been extracted and provided as appendable files (a modular and a static one), which get appended at rpm build time. That way kernel*.src.rpm from both XFS enabled and stock Red Hat setups can coexist in extracted form and kernel errata updates are easier and faster to perform (no need to mangle with kernel*.config anymore). --=20 Axel.Thimm@physik.fu-berlin.de --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+6cl/QBVS1GOamfERAiz8AJ97nLACTeLStVbU9SLuhFKyI/m5oQCeNvVf 4jXHL7plfB300EHLTOELaYo= =IavI -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft-- From owner-linux-xfs@oss.sgi.com Fri Jun 13 07:06:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 07:06:52 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DE6d2x016314 for ; Fri, 13 Jun 2003 07:06:39 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DE6X3X012323 for ; Fri, 13 Jun 2003 07:06: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 h5DE6XqX4506664 for ; Fri, 13 Jun 2003 09:06:33 -0500 (CDT) Received: from penguin.americas.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 h5DE6WRn114622491 for ; Fri, 13 Jun 2003 09:06:32 -0500 (CDT) From: Steve Lord Received: by penguin.americas.sgi.com (8.11.6/SGI-client-1.7) id h5DE3tC06098; Fri, 13 Jun 2003 09:03:55 -0500 Message-Id: <200306131403.h5DE3tC06098@penguin.americas.sgi.com> Date: Fri, 13 Jun 2003 09:03:55 -0500 Subject: TAKE 893003 - Corruption to XFS realtime filesystem To: linux-xfs@oss.sgi.com X-archive-position: 4313 X-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 Close window to prevent a file with delayed write extents from being converted to a realtime file. Date: Fri Jun 13 07:03:22 PDT 2003 Workarea: penguin.americas.sgi.com:/src/lord/xfs-linux.2.4 Inspected by: felixb gwehrman Author: cwf Merged by: lord Merged mods: grove2:irix:150953a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:150953a linux/fs/xfs/xfs_vnodeops.c - 1.593 - Merge of grove2:irix:150953a by lord. add check to xfs_setattr to avoid file with delalloc setting rt flag From owner-linux-xfs@oss.sgi.com Fri Jun 13 09:42:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 09:43:05 -0700 (PDT) Received: from hotmail.com (sea2-dav49.sea2.hotmail.com [207.68.164.21]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DGgp2x024693 for ; Fri, 13 Jun 2003 09:42:51 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 13 Jun 2003 09:42:46 -0700 Received: from 24.53.86.135 by sea2-dav49.sea2.hotmail.com with DAV; Fri, 13 Jun 2003 16:42:45 +0000 X-Originating-IP: [24.53.86.135] X-Originating-Email: [steve_cranage@hotmail.com] From: "Steve Cranage" To: Subject: DMAPI Mount option? Date: Fri, 13 Jun 2003 10:42:17 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Message-ID: X-OriginalArrivalTime: 13 Jun 2003 16:42:46.0148 (UTC) FILETIME=[D1521C40:01C331CA] Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 366 X-archive-position: 4314 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: steve_cranage@hotmail.com Precedence: bulk X-list: linux-xfs I dl'd and installed kernel-2.4.20-SGI_XFS1.3pre1.i686.rpm acl-2.2.4 attr-2.2.0 dmapi-2.0.5 xfsdump-2.2.6 xfsprogs-2.3.9 on a RH 9.0 distribution, and have been able to create and mount an xfs with no problem, except the dmi/dmapi mount options are not accepted. What is the correct syntax to mount an xfs with DMAPI support? [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Fri Jun 13 09:49:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 09:49:43 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DGnc2x025326 for ; Fri, 13 Jun 2003 09:49:38 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DH64mO004633 for ; Fri, 13 Jun 2003 12:06:04 -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 h5DGnXqX4474182; Fri, 13 Jun 2003 11:49:33 -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 h5DGnWYk12052078; Fri, 13 Jun 2003 11:49:32 -0500 (CDT) Subject: Re: DMAPI Mount option? From: Eric Sandeen To: Steve Cranage Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1055522972.18491.8.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 13 Jun 2003 11:49:32 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4315 X-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 Try "modinfo xfs" to see how xfs is configured, pretty sure CONFIG_XFS_DMAPI is turned off. You can rebuild from the .src.rpm after modifying the config files to turn this back on. Most people are not using dmapi, I think, so it's not config'd on in that kernel. -Eric On Fri, 2003-06-13 at 12:42, Steve Cranage wrote: > I dl'd and installed > > kernel-2.4.20-SGI_XFS1.3pre1.i686.rpm > acl-2.2.4 > attr-2.2.0 > dmapi-2.0.5 > xfsdump-2.2.6 > xfsprogs-2.3.9 > > on a RH 9.0 distribution, and have been able to create and mount an xfs with no problem, except the dmi/dmapi mount options are not accepted. What is the correct syntax to mount an xfs with DMAPI support? > > > [[HTML alternate version deleted]] -- Eric Sandeen 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 Jun 13 09:50:10 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 09:50:13 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DGoA2x025479 for ; Fri, 13 Jun 2003 09:50:10 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DH6amO004681 for ; Fri, 13 Jun 2003 12:06:36 -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 h5DGo4qX4526787; Fri, 13 Jun 2003 11:50:04 -0500 (CDT) Received: from chewtoy.americas.sgi.com (chewtoy.americas.sgi.com [128.162.233.33]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5DGo4Rn115596394; Fri, 13 Jun 2003 11:50:04 -0500 (CDT) Received: from chewtoy.americas.sgi.com by chewtoy.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id LAA27478; Fri, 13 Jun 2003 11:50:04 -0500 (CDT) Message-Id: <200306131650.LAA27478@chewtoy.americas.sgi.com> To: "Steve Cranage" cc: linux-xfs@oss.sgi.com Subject: Re: DMAPI Mount option? Date: Fri, 13 Jun 2003 11:50:03 -0500 From: Dean Roehrich X-archive-position: 4316 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: roehrich@sgi.com Precedence: bulk X-list: linux-xfs >From: "Steve Cranage" >I dl'd and installed > >kernel-2.4.20-SGI_XFS1.3pre1.i686.rpm >acl-2.2.4 >attr-2.2.0 >dmapi-2.0.5 >xfsdump-2.2.6 >xfsprogs-2.3.9 > >on a RH 9.0 distribution, and have been able to create and mount an xfs with n >o problem, except the dmi/dmapi mount options are not accepted. What is the co >rrect syntax to mount an xfs with DMAPI support? You also need the mtpt= option: # mount -o dmapi -o mtpt=/mnts/dmi1 /dev/hda12 /mnts/dmi1 Dean From owner-linux-xfs@oss.sgi.com Fri Jun 13 10:19:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 10:19:41 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DHJc2x027912 for ; Fri, 13 Jun 2003 10:19: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.2/linux-outbound_gateway-1.2) with ESMTP id h5DHJXE0025728 for ; Fri, 13 Jun 2003 10:19: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 h5DHJWqX4527842 for ; Fri, 13 Jun 2003 12:19:32 -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 h5DHJWRn111740201 for ; Fri, 13 Jun 2003 12:19:32 -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 h5DHJV5g019178 for ; Fri, 13 Jun 2003 12:19:32 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h5DHJVTH019176 for linux-xfs@oss.sgi.com; Fri, 13 Jun 2003 12:19:31 -0500 Date: Fri, 13 Jun 2003 12:19:31 -0500 From: Russell Cattelan Message-Id: <200306131719.h5DHJVTH019176@chuckle.americas.sgi.com> Subject: TAKE - Get the version RIGHT X-archive-position: 4317 X-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 Date: Fri Jun 13 10:19:16 PDT 2003 Workarea: chuckle.americas.sgi.com:/go/xfs2/XFS/x2.4-xfs-r1.3 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs-r1.3 Modid: 2.4.x-xfs-r1.3:slinx:151146a linux/fs/xfs/linux/xfs_version.h - 1.168 From owner-linux-xfs@oss.sgi.com Fri Jun 13 10:19:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 10:19:45 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DHJg2x027915 for ; Fri, 13 Jun 2003 10:19:42 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DHJbE0025732 for ; Fri, 13 Jun 2003 10:19:37 -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 h5DHJbqX4530434 for ; Fri, 13 Jun 2003 12:19:37 -0500 (CDT) Received: from penguin.americas.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 h5DHJaRn116311873 for ; Fri, 13 Jun 2003 12:19:36 -0500 (CDT) From: Steve Lord Received: by penguin.americas.sgi.com (8.11.6/SGI-client-1.7) id h5DHGui07363; Fri, 13 Jun 2003 12:16:56 -0500 Message-Id: <200306131716.h5DHGui07363@penguin.americas.sgi.com> Date: Fri, 13 Jun 2003 12:16:56 -0500 Subject: TAKE - Change version string from 2.4.21-rc8-xfs to 2.4.21-xfs To: linux-xfs@oss.sgi.com X-archive-position: 4318 X-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 Date: Fri Jun 13 10:17:41 PDT 2003 Workarea: penguin.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: 2.4.x-xfs:slinx:151145a linux/Makefile - 1.192 - rc8 became the release From owner-linux-xfs@oss.sgi.com Fri Jun 13 10:46:42 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 10:46:57 -0700 (PDT) Received: from loutre (AReims-101-1-3-138.w193-252.abo.wanadoo.fr [193.252.223.138]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DHke2x001858 for ; Fri, 13 Jun 2003 10:46:41 -0700 Received: from cykl by loutre with local (Exim 3.35 #1 (Debian)) id 19Qsd8-0005XC-00 for ; Fri, 13 Jun 2003 19:46:26 +0200 Date: Fri, 13 Jun 2003 19:46:26 +0200 From: cykl To: linux-xfs@oss.sgi.com Subject: RedHat 9-XFS install problem Message-ID: <20030613174626.GA28269@madchat.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LZvS9be/3tNcYl/X" Content-Disposition: inline X-Operating-System: "CykliX" User-Agent: Mutt/1.5.3i X-archive-position: 4319 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cykl@mAdchAt.org Precedence: bulk X-list: linux-xfs --LZvS9be/3tNcYl/X Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi, today i have tried the Sgi RH9-xfs installer and i have a little problem. Installation works fine for firsts packages but after a moment he asked me the RH CD 4 !!! Shrike has only 3 CDs... There is a problem or i have missed something ! Can you explain me what is wrong and how correct this ?=20 [Note : i have used the ftp://oss.sgi.com/projects/xfs/download/Release-1.2/installer/forRH-9.0-SGI= -XFS-1.2.0-v1.iso iso and ftp.redhat.com isos You can ask me more details if it necessary ] Thanks Cykl --=20 Le naturisme, sur les d=E9pliant c'est des jeunes filles =E0 poil sur la plage mais quand tu y es, c'est que des retrait=E9s de la SNCF. --LZvS9be/3tNcYl/X Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+6g3y87RReLVV2p8RAqYDAJ0VYDXDp3+mhuJXbMqx6NCb54j8BQCfVb2f s8Czzgj0H3OlGk3pZrIjI1s= =cuyg -----END PGP SIGNATURE----- --LZvS9be/3tNcYl/X-- From owner-linux-xfs@oss.sgi.com Fri Jun 13 11:12:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 11:12:41 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DICQ2x003561 for ; Fri, 13 Jun 2003 11:12:26 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DICL3X001357 for ; Fri, 13 Jun 2003 11:12:21 -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 h5DICKqX4462882; Fri, 13 Jun 2003 13:12:20 -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 h5DICKYk12052949; Fri, 13 Jun 2003 13:12:20 -0500 (CDT) Subject: Re: RedHat 9-XFS install problem From: Eric Sandeen To: cykl Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030613174626.GA28269@madchat.org> References: <20030613174626.GA28269@madchat.org> Content-Type: text/plain Organization: Message-Id: <1055527939.18491.16.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 13 Jun 2003 13:12:20 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4320 X-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 It wants the XFS boot cd. -Eric On Fri, 2003-06-13 at 12:46, cykl wrote: > hi, > > today i have tried the Sgi RH9-xfs installer and i have a little problem. > Installation works fine for firsts packages but after a moment he asked me > the RH CD 4 !!! > > Shrike has only 3 CDs... > > There is a problem or i have missed something ! > > Can you explain me what is wrong and how correct this ? > > [Note : i have used the > ftp://oss.sgi.com/projects/xfs/download/Release-1.2/installer/forRH-9.0-SGI-XFS-1.2.0-v1.iso > iso and ftp.redhat.com isos > > You can ask me more details if it necessary > ] > > Thanks > > Cykl -- Eric Sandeen 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 Jun 13 11:13:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 11:13:09 -0700 (PDT) Received: from pinga.salk.edu (ccmi.salk.edu [192.31.153.187]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DID52x003723 for ; Fri, 13 Jun 2003 11:13:06 -0700 Received: from ccmi.salk.edu (muk.dyndns.org [24.30.128.10]) by pinga.salk.edu (8.12.9/8.12.9) with SMTP id h5DICvXf021500; Fri, 13 Jun 2003 11:12:58 -0700 Date: Fri, 13 Jun 2003 11:12:51 -0700 From: David Chambers To: cykl , linux-xfs@oss.sgi.com Subject: Re: RedHat 9-XFS install problem Message-Id: <20030613111251.3e9016c0.davidc@ccmi.salk.edu> In-Reply-To: <20030613174626.GA28269@madchat.org> References: <20030613174626.GA28269@madchat.org> X-Mailer: Sylpheed version 0.9.0claws (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5DID62x003724 X-archive-position: 4321 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: davidc@ccmi.salk.edu Precedence: bulk X-list: linux-xfs CD4 is the SGI disk you booted from. (the one burned from "forRH-9.0-SGI-XFS-1.2.0-v1.iso") - David On Fri, 13 Jun 2003 19:46:26 +0200 cykl wrote: > hi, > > today i have tried the Sgi RH9-xfs installer and i have a little problem. > Installation works fine for firsts packages but after a moment he asked me > the RH CD 4 !!! > > Shrike has only 3 CDs... > > There is a problem or i have missed something ! > > Can you explain me what is wrong and how correct this ? > > [Note : i have used the > ftp://oss.sgi.com/projects/xfs/download/Release-1.2/installer/forRH-9.0-SGI-XFS-1.2.0-v1.iso > iso and ftp.redhat.com isos > > You can ask me more details if it necessary > ] > > Thanks > > Cykl > -- > Le naturisme, sur les dépliant c'est des jeunes filles à poil sur la > plage mais quand tu y es, c'est que des retraités de la SNCF. > From owner-linux-xfs@oss.sgi.com Fri Jun 13 11:32:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 11:32:33 -0700 (PDT) Received: from hotmail.com (sea2-dav32.sea2.hotmail.com [207.68.164.89]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DIWI2x005199 for ; Fri, 13 Jun 2003 11:32:18 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 13 Jun 2003 11:32:12 -0700 Received: from 24.53.86.135 by sea2-dav32.sea2.hotmail.com with DAV; Fri, 13 Jun 2003 18:32:12 +0000 X-Originating-IP: [24.53.86.135] X-Originating-Email: [steve_cranage@hotmail.com] From: "Steve Cranage" To: "Eric Sandeen" Cc: References: <1055522972.18491.8.camel@stout.americas.sgi.com> Subject: Re: DMAPI Mount option? Date: Fri, 13 Jun 2003 12:32:12 -0700 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Message-ID: X-OriginalArrivalTime: 13 Jun 2003 18:32:12.0934 (UTC) FILETIME=[1B6E2260:01C331DA] X-archive-position: 4322 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: steve_cranage@hotmail.com Precedence: bulk X-list: linux-xfs The state of CONFIG_XFS_DMAPI isn't revealed by modinfo, but I did build my own kernel with DMAPI on, and no luck. It still chokes with either a dmapi or dmi option. ----- Original Message ----- From: "Eric Sandeen" To: "Steve Cranage" Cc: Sent: Friday, June 13, 2003 9:49 AM Subject: Re: DMAPI Mount option? > Try "modinfo xfs" to see how xfs is configured, pretty sure > CONFIG_XFS_DMAPI is turned off. > > You can rebuild from the .src.rpm after modifying the config files to > turn this back on. > > Most people are not using dmapi, I think, so it's not config'd on in > that kernel. > > -Eric > > > On Fri, 2003-06-13 at 12:42, Steve Cranage wrote: > > I dl'd and installed > > > > kernel-2.4.20-SGI_XFS1.3pre1.i686.rpm > > acl-2.2.4 > > attr-2.2.0 > > dmapi-2.0.5 > > xfsdump-2.2.6 > > xfsprogs-2.3.9 > > > > on a RH 9.0 distribution, and have been able to create and mount an xfs with no problem, except the dmi/dmapi mount options are not accepted. What is the correct syntax to mount an xfs with DMAPI support? > > > > > > [[HTML alternate version deleted]] > -- > Eric Sandeen 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 Jun 13 11:32:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 11:33:03 -0700 (PDT) Received: from hotmail.com (sea2-dav10.sea2.hotmail.com [207.68.164.114]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DIWx2x005336 for ; Fri, 13 Jun 2003 11:32:59 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 13 Jun 2003 11:32:54 -0700 Received: from 24.53.86.135 by sea2-dav10.sea2.hotmail.com with DAV; Fri, 13 Jun 2003 18:32:53 +0000 X-Originating-IP: [24.53.86.135] X-Originating-Email: [steve_cranage@hotmail.com] From: "Steve Cranage" To: "Dean Roehrich" Cc: References: <200306131650.LAA27478@chewtoy.americas.sgi.com> Subject: Re: DMAPI Mount option? Date: Fri, 13 Jun 2003 12:32:53 -0700 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Message-ID: X-OriginalArrivalTime: 13 Jun 2003 18:32:54.0017 (UTC) FILETIME=[33EAE710:01C331DA] X-archive-position: 4323 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: steve_cranage@hotmail.com Precedence: bulk X-list: linux-xfs That doesn't work either. ----- Original Message ----- From: "Dean Roehrich" To: "Steve Cranage" Cc: Sent: Friday, June 13, 2003 9:50 AM Subject: Re: DMAPI Mount option? > > >From: "Steve Cranage" > >I dl'd and installed > > > >kernel-2.4.20-SGI_XFS1.3pre1.i686.rpm > >acl-2.2.4 > >attr-2.2.0 > >dmapi-2.0.5 > >xfsdump-2.2.6 > >xfsprogs-2.3.9 > > > >on a RH 9.0 distribution, and have been able to create and mount an xfs with n > >o problem, except the dmi/dmapi mount options are not accepted. What is the co > >rrect syntax to mount an xfs with DMAPI support? > > You also need the mtpt= option: > > # mount -o dmapi -o mtpt=/mnts/dmi1 /dev/hda12 /mnts/dmi1 > > Dean > From owner-linux-xfs@oss.sgi.com Fri Jun 13 11:35:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 11:35:47 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DIZg2x006204 for ; Fri, 13 Jun 2003 11:35:43 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DGXP3X024790 for ; Fri, 13 Jun 2003 09:33:25 -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 h5DGXOqX4521792 for ; Fri, 13 Jun 2003 11:33:24 -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 h5DGXORn112709485 for ; Fri, 13 Jun 2003 11:33:24 -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 h5DGXO5g016173 for ; Fri, 13 Jun 2003 11:33:24 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h5DGXORq016171 for linux-xfs@oss.sgi.com; Fri, 13 Jun 2003 11:33:24 -0500 Date: Fri, 13 Jun 2003 11:33:24 -0500 From: Russell Cattelan Message-Id: <200306131633.h5DGXORq016171@chuckle.americas.sgi.com> Subject: TAKE 893003 - Merge over latest inode hang fixes X-archive-position: 4324 X-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 Date: Fri Jun 13 09:33:06 PDT 2003 Workarea: chuckle.americas.sgi.com:/go/xfs2/XFS/x2.4-xfs-r1.3 Merged by: cattelan Merged mods: 2.4.x-xfs:slinx:150782a,2.4.x-xfs:slinx:150885a,2.4.x-xfs:slinx:151120a 2.4.x-xfs:slinx:151123a,2.4.x-xfs:slinx:150953a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs-r1.3 Modid: 2.4.x-xfs-r1.3:slinx:151139a linux/fs/xfs/xfs_vnodeops.c - 1.592 - Merge of 2.4.x-xfs:slinx:151123a originally by lord on 06/12/03 Fix deadlock between xfs_finish_reclaim and xfs_iget_core. An inode being reclaimed and removed from memory by one thread while another thread is attempting to reuse the inode and bring it back to life. There was a window between the iget starting to reuse the inode and the reclaim starting. Close the window by marking the inode as being reused under the hash lock, and by abandoning the reclaim if this is detected when it obtains the hash lock. Set XFS_IRECLAIMABLE when disconnecting an xfs_inode from the linux inode. This is safe from the iget path because of the I_LOCK which is held in both cases. In xfs_finish_reclaim, after obtaining the hash lock, check that XFS_IRECLAIMABLE is set in the case where there is no vnode, abandon the reclaim if it is not. We can also reduce the locking use in a couple of paths here. Merge of 2.4.x-xfs:slinx:150953a originally by cwf on 06/13/03 Close window to prevent a file with delayed write extents from being converted to a realtime file. Merge of grove2:irix:150953a by lord. add check to xfs_setattr to avoid file with delalloc setting rt flag linux/fs/xfs/xfs_iget.c - 1.189 - Merge of 2.4.x-xfs:slinx:151123a originally by lord on 06/12/03 Fix deadlock between xfs_finish_reclaim and xfs_iget_core. An inode being reclaimed and removed from memory by one thread while another thread is attempting to reuse the inode and bring it back to life. There was a window between the iget starting to reuse the inode and the reclaim starting. Close the window by marking the inode as being reused under the hash lock, and by abandoning the reclaim if this is detected when it obtains the hash lock. When a candidate inode is found in xfs_iget_core which has the potential to be reclaimed, remove the XFS_IRECLAIMABLE flag under the inode hash lock. linux/fs/xfs/xfs_inode.c - 1.377 - Merge of 2.4.x-xfs:slinx:151120a originally by lord on 06/12/03 Fix deadlock caused by race between xfs_iunpin marking an inode dirty, and the same inode being reallocated and reused by create. The unlock_new_inode and mark_inode_dirty manage to corrupt the i_state flags and end up leaving I_LOCK|I_NEW set. do not call mark_inode_dirty in xfs_iunpin when I_NEW is set, it is in the process of going into a transaction which will also mark it dirty. linux/fs/xfs/xfs_inode.h - 1.182 - Merge of 2.4.x-xfs:slinx:151123a originally by lord on 06/12/03 Fix deadlock between xfs_finish_reclaim and xfs_iget_core. An inode being reclaimed and removed from memory by one thread while another thread is attempting to reuse the inode and bring it back to life. There was a window between the iget starting to reuse the inode and the reclaim starting. Close the window by marking the inode as being reused under the hash lock, and by abandoning the reclaim if this is detected when it obtains the hash lock. Define XFS_IRECLAIMABLE linux/fs/xfs/linux/xfs_sysctl.h - 1.13 - Merge of 2.4.x-xfs:slinx:150782a originally by lord on 06/10/03 break dependency between CONFIG_PROCFS and CONFIG_SYSCTL in xfs move clear stats sysctl to the end linux/fs/xfs/linux/xfs_sysctl.c - 1.20 - Merge of 2.4.x-xfs:slinx:150782a originally by lord on 06/10/03 break dependency between CONFIG_PROCFS and CONFIG_SYSCTL in xfs make the clear stats interface conditional on procfs, the only way we display stats is via procfs anyway. linux/fs/xfs/pagebuf/page_buf.c - 1.120 - Merge of 2.4.x-xfs:slinx:150885a originally by lord on 06/11/03 Fix O_DIRECT using uninitialized memory, user space is passing in the same zero page at lots of addresses. The xfs code was locking the user pages which is unneccessary, end result deadlock on ourselves. In pagebuf_lookup, create a pagebuf which is lockable so we do not lock the pages within it during I/O. Only O_DIRECT does I/O on this type of pagebuf. From owner-linux-xfs@oss.sgi.com Fri Jun 13 12:42:40 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 12:42:59 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DJge2x010162 for ; Fri, 13 Jun 2003 12:42:40 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DJgY3X010036 for ; Fri, 13 Jun 2003 12:42:34 -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 h5DJgYqX4546418; Fri, 13 Jun 2003 14:42:34 -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 h5DJgXYk11824628; Fri, 13 Jun 2003 14:42:34 -0500 (CDT) Subject: Re: DMAPI Mount option? From: Eric Sandeen To: Steve Cranage Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <1055522972.18491.8.camel@stout.americas.sgi.com> Content-Type: text/plain Organization: Message-Id: <1055533353.18491.18.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 13 Jun 2003 14:42:33 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4325 X-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 On Fri, 2003-06-13 at 14:32, Steve Cranage wrote: > The state of CONFIG_XFS_DMAPI isn't revealed by modinfo, but I did build > my own kernel with DMAPI on, and no luck. It still chokes with either a > dmapi or dmi option. If you don't see "With dmapi" in modinfo output, then it's not enabled. We need more info than "doesn't work" - what error do you get? -Eric -- Eric Sandeen 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 Jun 13 13:03:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 13:03:27 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DK3C2x011277 for ; Fri, 13 Jun 2003 13:03: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.2/linux-outbound_gateway-1.2) with ESMTP id h5DK363X012017 for ; Fri, 13 Jun 2003 13:03:07 -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 h5DK36qX4544502; Fri, 13 Jun 2003 15:03:06 -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 h5DK36Yk12056444; Fri, 13 Jun 2003 15:03:06 -0500 (CDT) Subject: Re: DMAPI Mount option? From: Eric Sandeen To: Steve Cranage Cc: linux-xfs@oss.sgi.com In-Reply-To: <1055533353.18491.18.camel@stout.americas.sgi.com> References: <1055522972.18491.8.camel@stout.americas.sgi.com> <1055533353.18491.18.camel@stout.americas.sgi.com> Content-Type: text/plain Organization: Message-Id: <1055534585.18488.24.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 13 Jun 2003 15:03:06 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4326 X-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 I apologize, "dmapi" is -not- in the version string... quota, acl, realtime, debug etc are, but not dmapi. Sorry about that. -Eric On Fri, 2003-06-13 at 14:42, Eric Sandeen wrote: > On Fri, 2003-06-13 at 14:32, Steve Cranage wrote: > > The state of CONFIG_XFS_DMAPI isn't revealed by modinfo, but I did build > > my own kernel with DMAPI on, and no luck. It still chokes with either a > > dmapi or dmi option. > > If you don't see "With dmapi" in modinfo output, then it's not enabled. > > We need more info than "doesn't work" - what error do you get? > > -Eric -- Eric Sandeen 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 Jun 13 13:17:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 13:18:01 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DKHu2x012294 for ; Fri, 13 Jun 2003 13:17:57 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DIhlE0004440 for ; Fri, 13 Jun 2003 11:43:48 -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 h5DIhlqX4536326; Fri, 13 Jun 2003 13:43:47 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 19QtWd-0007Fx-00; Fri, 13 Jun 2003 13:43:47 -0500 Date: Fri, 13 Jun 2003 13:43:47 -0500 From: Nathan Straz To: Steve Cranage Cc: linux-xfs@oss.sgi.com Subject: Re: DMAPI Mount option? Message-ID: <20030613184346.GB20822@sgi.com> Mail-Followup-To: Steve Cranage , linux-xfs@oss.sgi.com References: <1055522972.18491.8.camel@stout.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: 4327 X-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 On Fri, Jun 13, 2003 at 12:32:12PM -0700, Steve Cranage wrote: > The state of CONFIG_XFS_DMAPI isn't revealed by modinfo, but I did build > my own kernel with DMAPI on, and no luck. It still chokes with either a > dmapi or dmi option. Whenever you have a problem mounting, always check the output of dmesg. There is usually a helpful hint there. Are there any error messages in dmesg when your mount command fails? -- 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 Fri Jun 13 13:48:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 13:48:04 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DKm02x013816 for ; Fri, 13 Jun 2003 13:48: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.2/linux-outbound_gateway-1.2) with ESMTP id h5DL4RmO019266 for ; Fri, 13 Jun 2003 16:04:27 -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 h5DKltqX4553605 for ; Fri, 13 Jun 2003 15:47:55 -0500 (CDT) Received: from penguin.americas.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 h5DKlsRn88716554 for ; Fri, 13 Jun 2003 15:47:55 -0500 (CDT) From: Steve Lord Received: by penguin.americas.sgi.com (8.11.6/SGI-client-1.7) id h5DKjCA13051; Fri, 13 Jun 2003 15:45:12 -0500 Message-Id: <200306132045.h5DKjCA13051@penguin.americas.sgi.com> Date: Fri, 13 Jun 2003 15:45:12 -0500 Subject: TAKE - fix pagebuf tracing interface To: linux-xfs@oss.sgi.com X-archive-position: 4328 X-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 fix the sysctl & /proc interface for pagebuf so you can turn tracing on and off again Date: Fri Jun 13 13:47:22 PDT 2003 Workarea: penguin.americas.sgi.com:/data/lwork/folsom3/lord/xfs-linux.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:151168a linux/fs/xfs/pagebuf/page_buf_internal.h - 1.23 - transpose debug and stats_clear config vars in structure From owner-linux-xfs@oss.sgi.com Fri Jun 13 14:12:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 14:12:15 -0700 (PDT) Received: from hotmail.com (sea2-dav44.sea2.hotmail.com [207.68.164.16]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DLC02x014543 for ; Fri, 13 Jun 2003 14:12:01 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 13 Jun 2003 14:11:55 -0700 Received: from 24.53.86.135 by sea2-dav44.sea2.hotmail.com with DAV; Fri, 13 Jun 2003 21:11:55 +0000 X-Originating-IP: [24.53.86.135] X-Originating-Email: [steve_cranage@hotmail.com] From: "Steve Cranage" To: "Eric Sandeen" Cc: References: <1055522972.18491.8.camel@stout.americas.sgi.com> <1055533353.18491.18.camel@stout.americas.sgi.com> <1055534585.18488.24.camel@stout.americas.sgi.com> Subject: Re: DMAPI Mount option? Date: Fri, 13 Jun 2003 15:11:20 -0700 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 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Message-ID: X-OriginalArrivalTime: 13 Jun 2003 21:11:55.0593 (UTC) FILETIME=[6B23DB90:01C331F0] X-archive-position: 4329 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: steve_cranage@hotmail.com Precedence: bulk X-list: linux-xfs Success! I rebuilt the system using the RH9 installer iso, fixed that kernel by doing a make oldconfig, and enabling the DMAPI option in the config file, then doing the mount with both dmapi and mnpt options. Thanks much! ----- Original Message ----- From: "Eric Sandeen" To: "Steve Cranage" Cc: Sent: Friday, June 13, 2003 1:03 PM Subject: Re: DMAPI Mount option? > I apologize, "dmapi" is -not- in the version string... quota, acl, > realtime, debug etc are, but not dmapi. Sorry about that. > > -Eric > > On Fri, 2003-06-13 at 14:42, Eric Sandeen wrote: > > On Fri, 2003-06-13 at 14:32, Steve Cranage wrote: > > > The state of CONFIG_XFS_DMAPI isn't revealed by modinfo, but I did build > > > my own kernel with DMAPI on, and no luck. It still chokes with either a > > > dmapi or dmi option. > > > > If you don't see "With dmapi" in modinfo output, then it's not enabled. > > > > We need more info than "doesn't work" - what error do you get? > > > > -Eric > -- > Eric Sandeen 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 Jun 13 14:24:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 14:24:30 -0700 (PDT) Received: from mail11.atl.registeredsite.com (nobody@mail11.atl.registeredsite.com [64.224.219.85]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DLOR2x015093 for ; Fri, 13 Jun 2003 14:24:28 -0700 Received: from imta02a2.registeredsite.com (imta02a2.registeredsite.com [64.225.255.11]) by mail11.atl.registeredsite.com (8.12.8/8.12.9) with ESMTP id h5DLOO7Y019270 for ; Fri, 13 Jun 2003 17:24:25 -0400 Received: from yourn3ty7athd5 ([207.239.96.20]) by imta02a2.registeredsite.com with SMTP id <20030613212424.XTMI16584.imta02a2.registeredsite.com@yourn3ty7athd5> for ; Fri, 13 Jun 2003 17:24:24 -0400 From: "Ripin Natani" To: Subject: security issues ... Date: Fri, 13 Jun 2003 17:24:19 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 4330 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rnatani@platformlogic.com Precedence: bulk X-list: linux-xfs Hi, I am trying to choose between ext3, reiserfs and xfs and my particular criteria is security. Can someone tell me the pros and cons ? Also is there any possible potential security threats in xfs ? Also, like in ext3 can the journal file be made visible and manipulated in any lethal way ? Thanks, -Ripin. From owner-linux-xfs@oss.sgi.com Fri Jun 13 14:30:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 14:30:27 -0700 (PDT) Received: from mail.slb.com (nammta01.sugar-land.nam.slb.com [163.188.150.130]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DLUA2x015597 for ; Fri, 13 Jun 2003 14:30:17 -0700 Received: from conversion-daemon.nammta01.sugar-land.nam.slb.com by nammta01.sugar-land.nam.slb.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) id <0HGF00D01V5MS9@nammta01.sugar-land.nam.slb.com> for linux-xfs@oss.sgi.com; Fri, 13 Jun 2003 21:24:53 +0000 (GMT) Received: from wgmail1.houston.nam.slb.com (wgmail1.houston.nam.slb.com [137.144.106.50]) by nammta01.sugar-land.nam.slb.com (iPlanet Messaging Server 5.2 HotFix 1.14 (built Mar 18 2003)) with ESMTP id <0HGF001VMVH2FC@nammta01.sugar-land.nam.slb.com> for linux-xfs@oss.sgi.com; Fri, 13 Jun 2003 21:24:39 +0000 (GMT) Received: from BOJAVAN1.houston.westerngeco.slb.com (localhost [127.0.0.1]) by wgmail1.houston.nam.slb.com (Switch-2.2.6/Switch-2.2.6) with ESMTP id h5DLLA525530 for ; Fri, 13 Jun 2003 16:21:10 -0500 (CDT) Date: Fri, 13 Jun 2003 16:24:35 -0500 From: Vangel Bojaxhi Subject: Linux XFS for Redhat 9.0 X-Sender: VBojaxhi@wgmail1.houston.nam.slb.com To: linux-xfs@oss.sgi.com Message-id: <5.1.0.14.2.20030613161827.040d3008@wgmail1.houston.nam.slb.com> MIME-version: 1.0 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-archive-position: 4331 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: vbojaxhi@houston.westerngeco.slb.com Precedence: bulk X-list: linux-xfs To whom it may concern I am interested to find out the XFS Kernel and User space software, for the standard Red Hat Version 9, Kernel version 2.4.X-XX. Appreciate your help. Regards / Vangel WesternGeco Houston ( 713)-689-2509 From owner-linux-xfs@oss.sgi.com Fri Jun 13 14:31:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 14:31:33 -0700 (PDT) Received: from dingdong.cryptoapps.com (postfix@uslink-66.173.43-133.uslink.net [66.173.43.133] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5DLVT2x015805 for ; Fri, 13 Jun 2003 14:31:30 -0700 Received: by dingdong.cryptoapps.com (Postfix, from userid 1001) id 91761FB838; Fri, 13 Jun 2003 16:34:46 -0500 (CDT) Date: Fri, 13 Jun 2003 16:34:46 -0500 From: Chris Wedgwood To: Ripin Natani Cc: linux-xfs@oss.sgi.com Subject: Re: security issues ... Message-ID: <20030613213446.GA22207@dingdong.cryptoapps.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-archive-position: 4332 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Fri, Jun 13, 2003 at 05:24:19PM -0400, Ripin Natani wrote: > Also is there any possible potential security threats in xfs? If there is, just as for any other filesystem people when made aware of it will work to fix this. > Also, like in ext3 can the journal file be made visible and > manipulated in any lethal way ? In the sense you mean, by having a visible inode to mess with then answer is usually no. With some effort though you can break things, but this applies to everything at some level or other and XFS is probably as hard to break if not harder than most filesystems. --cw From owner-linux-xfs@oss.sgi.com Fri Jun 13 17:12:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 17:12:44 -0700 (PDT) Received: from maul.jdc.home (Nm@12-226-0-64.client.attbi.com [12.226.0.64]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5E0CP2x024663 for ; Fri, 13 Jun 2003 17:12:26 -0700 Received: from warblade.jdc.home (warblade.jdc.home [10.1.1.2]) by maul.jdc.home (Postfix) with ESMTP id 2DE6834000B4 for ; Fri, 13 Jun 2003 20:12:24 -0400 (EDT) Subject: Another sparc64 recovery oops From: Jim Crilly To: linux-xfs@oss.sgi.com Content-Type: text/plain Message-Id: <1055549543.1427.44.camel@warblade.jdc.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.92 (Preview Release) Date: 13 Jun 2003 20:12:24 -0400 Content-Transfer-Encoding: 7bit X-archive-position: 4333 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jim@why.dont.jablowme.net Precedence: bulk X-list: linux-xfs I recently had a power flicker and had an Ultra2 running XFS oops on recovery, I put 2.4.21-rc8 on it to see if that was affected to and it appears to be. Luckily I can run xfs_repair and it'll fix the filesystem, but I have to use -L to clear the log which isn't preferable. Anyway here's the oops, if you're interested. This isn't anything production so if anyone has anything they'd like me to test I'll be more than happy. Thanks, Jim. ksymoops 2.4.8 on sparc64 2.4.21-rc8-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.21-rc8-xfs/ (default) -m /boot/System.map-2.4.21-rc8-xfs (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Unable to handle kernel NULL pointer dereference tsk->{mm,active_mm}->context = 000000000000043b tsk->{mm,active_mm}->pgd = fffff800273d4000 \|/ ____ \|/ "@'/ .. \`@" /_| \__/ |_\ \__U_/ mount(72): Oops CPU[0]: local_irq_count[0] irqs_running[0] TSTATE: 0000000011009605 TPC: 00000000004c4598 TNPC: 00000000004c4570 Y: 06000000 Not tainted Using defaults from ksymoops -t elf32-sparc -a sparc g0: 0000000000000000 g1: 00000000000000c2 g2: 0000000000000040 g3: 0000000000000000 g4: fffff80000000000 g5: 0000000000000000 g6: fffff80027488000 g7: 0000000000000000 o0: 0000000000000000 o1: 0000000000000040 o2: 0000000000000000 o3: 0000000000000000 o4: 0000000000000000 o5: 00000000ffffffe0 sp: fffff8002748a5a1 ret_pc: 00000000004f4a60 l0: 000000000000000e l1: 0000000000000000 l2: 0000000003f430ec l3: 000000003f430ec0 l4: 0000000000000002 l5: fffff80000bcf174 l6: 0000000000605800 l7: 0000000000000000 i0: fffff80027247000 i1: fffff80000bcefe0 i2: fffff80026b86e60 i3: fffff80000bcf160 i4: fffff80000bcf220 i5: 0000000000000004 i6: fffff8002748a661 i7: 00000000004f4f2c Caller[00000000004f4f2c] Caller[00000000004f5d54] Caller[00000000004f5e44] Caller[00000000004f5f8c] Caller[00000000004f6c40] Caller[00000000004f7098] Caller[00000000004f70d0] Caller[00000000004f72a0] Caller[00000000004eeee8] Caller[00000000004f8a80] Caller[00000000004ecd28] Caller[00000000004ff8a0] Caller[0000000000513ca0] Caller[0000000000513a80] Caller[00000000004794f4] Caller[00000000004797ac] Caller[000000000049028c] Caller[00000000004905b0] Caller[0000000000431e10] Caller[0000000000410e34] Caller[00000000000125fc] Instruction DUMP: 8730e000 80a2601f 384ffff7 80a26000 32480004 d002c000 10680029 90103fff >>PC; 004c4598 <===== >>ret_pc; 004f4a60 >>l6; 00605800 >>i7; 004f4f2c Trace; 004f4f2c Trace; 004f5d54 Trace; 004f5e44 Trace; 004f5f8c Trace; 004f6c40 Trace; 004f7098 Trace; 004f70d0 Trace; 004f72a0 Trace; 004eeee8 Trace; 004f8a80 Trace; 004ecd28 Trace; 004ff8a0 Trace; 00513ca0 Trace; 00513a80 Trace; 004794f4 Trace; 004797ac Trace; 0049028c Trace; 004905b0 Trace; 00431e10 Trace; 00410e34 Trace; 000125fc Before first symbol Code; 004c458c 00000000 <_PC>: Code; 004c458c 0: 87 30 e0 00 srl %g3, 0, %g3 Code; 004c4590 4: 80 a2 60 1f cmp %o1, 0x1f Code; 004c4594 8: 38 4f ff f7 unknown Code; 004c4598 <===== c: c4 02 c0 00 ld [ %o3 ], %g2 <===== Code; 004c459c 10: 80 a2 60 00 cmp %o1, 0 Code; 004c45a0 14: 32 48 00 04 unknown Code; 004c45a4 18: d0 02 c0 00 ld [ %o3 ], %o0 Code; 004c45a8 1c: 10 68 00 29 unknown Code; 004c45ac 20: 90 10 3f ff mov -1, %o0 CPU[1]: local_irq_count[0] irqs_running[0] TSTATE: 0000000480009604 TPC: 0000000000478130 TNPC: 0000000000478134 Y: 00000000 Not tainted g0: fffff80000b674f1 g1: 0000000000000000 g2: 0000000000000000 g3: fffff80000b67da0 g4: fffff80000000000 g5: fffff80000b50000 g6: fffff80000b64000 g7: 00000000000000ff o0: 0000000100000000 o1: 000000000000065e o2: 000000000073a000 o3: 00000000006ac000 o4: fffff8000039b36c o5: 0000000000701800 sp: fffff80000b67521 ret_pc: 0000000000446fa8 l0: 000000000000065e l1: fffff80000b67da0 l2: 0000000000731800 l3: 0000000000000000 l4: 00000000006235d0 l5: 0000000000000000 l6: 0000000000723800 l7: 0000000000000000 i0: 0000000000000000 i1: 0000000000000001 i2: 0000000000000000 i3: 0000000000000000 i4: 00000000005fcc00 i5: 0000000000000000 i6: fffff80000b675e1 i7: 0000000000477db0 Warning (Oops_read): Code line not seen, dumping what data is available >>PC; 00478130 <__mark_dirty+310/380> <===== >>g0; 00b674f1 <_end+3d11b9/1869d88> >>g3; 00b67da0 <_end+3d1a68/1869d88> >>g5; 00b50000 <_end+3b9cc8/1869d88> >>g6; 00b64000 <_end+3cdcc8/1869d88> >>o2; 0073a000 >>o3; 006ac000 >>o5; 00701800 >>sp; 00b67521 <_end+3d11e9/1869d88> >>ret_pc; 00446fa8 >>l1; 00b67da0 <_end+3d1a68/1869d88> >>l2; 00731800 >>l4; 006235d0 >>l6; 00723800 >>i4; 005fcc00 >>i6; 00b675e1 <_end+3d12a9/1869d88> >>i7; 00477db0 From owner-linux-xfs@oss.sgi.com Fri Jun 13 17:58:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Jun 2003 17:58:26 -0700 (PDT) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5E0wB2x026756 for ; Fri, 13 Jun 2003 17:58:11 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5DM60E0000358 for ; Fri, 13 Jun 2003 15:06:02 -0700 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h5DM60qX4557253 for ; Fri, 13 Jun 2003 17:06:00 -0500 (CDT) Received: from [128.162.232.98] (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5DM5wRn116315801 for ; Fri, 13 Jun 2003 17:05:58 -0500 (CDT) Subject: [ANNOUNCE] XFS 1.3.0 PreRelease #2 From: Russell Cattelan To: linux-xfs@oss.sgi.com Content-Type: text/plain Organization: Message-Id: <1055541959.6325.70.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 13 Jun 2003 17:05:59 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4334 X-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 So pre1 never really got announced but people seem to find it anyways. But it's probably a good idea let people know what is going on. :-) We have split thing up a bit in the hopes of making xfs more of an independent release from the kernels. The core kernel patches has not changed and hopefully won't change in foreseeable future. ftp://oss.sgi.com/projects/xfs/Release-1.3/kernel_patches/linux-2.4.20-core-xfs-1.3.0.patch.gzftp://oss.sgi.com/projects/xfs/Release-1.3/kernel_patches/linux-2.4.21-core-xfs-1.3.0.patch.gz The bulk of xfs: ftp://oss.sgi.com/projects/xfs/Release-1.3/pre2/kernel_patches/linux-xfs-1.3.0pre2.patch.gz And since somebody recently found a nice little program called interdiff. A delta patch that will go from pre1 to pre2 ftp://oss.sgi.com/projects/xfs/Release-1.3/pre2/kernel_patches/linux-xfs-1.3.0pre1-pre2.patch.gz The kernel rpm's are in the works and hopefully will be done sometime this weekend (or not since it suppose to be really nice this weekend). Please don't not regard this stuff as extremely well tested, but it does got through nightly regression testing. So use as own risk for the moment (but please to help flush out any problems) -Russell Cattelan From owner-linux-xfs@oss.sgi.com Sun Jun 15 11:15:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Jun 2003 11:15:23 -0700 (PDT) Received: from mail.lst.de (verein.lst.de [212.34.189.10]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5FIFH2x024430 for ; Sun, 15 Jun 2003 11:15:18 -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 h5FIFDDC005238 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 15 Jun 2003 20:15:13 +0200 Received: (from hch@localhost) by verein.lst.de (8.12.3/8.12.3/Debian-6.3) id h5FIFC2i005236; Sun, 15 Jun 2003 20:15:12 +0200 Date: Sun, 15 Jun 2003 20:15:12 +0200 From: Christoph Hellwig To: splord@sgi.com Cc: linux-xfs@oss.sgi.com Subject: [PATCH] simplify xfs_mountfs Message-ID: <20030615181512.GA5212@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: 4335 X-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 The dev argument to xfs_mountfs can't be zero so it and the code depending on that are superflous. Spotted by Al Viro. --- 1.6/fs/xfs/xfs_iocore.c Fri May 2 22:01:27 2003 +++ edited/fs/xfs/xfs_iocore.c Sat Jun 14 21:35:35 2003 @@ -77,8 +77,7 @@ struct xfs_mount_args *mntargs, int flags) { - return xfs_mountfs(vfsp, XFS_VFSTOM(vfsp), - vfsp->vfs_super->s_bdev->bd_dev, flags); + return xfs_mountfs(vfsp, XFS_VFSTOM(vfsp), flags); } xfs_ioops_t xfs_iocore_xfs = { --- 1.30/fs/xfs/xfs_mount.c Mon May 19 21:11:14 2003 +++ edited/fs/xfs/xfs_mount.c Sat Jun 14 21:35:11 2003 @@ -620,7 +620,6 @@ xfs_mountfs( vfs_t *vfsp, xfs_mount_t *mp, - dev_t dev, int mfsi_flags) { xfs_buf_t *bp; @@ -633,11 +632,10 @@ __uint64_t ret64; __int64_t update_flags; uint quotamount, quotaflags; - int agno, noio; + int agno; int uuid_mounted = 0; int error = 0; - noio = dev == 0 && mp->m_sb_bp != NULL; if (mp->m_sb_bp == NULL) { if ((error = xfs_readsb(mp))) { return (error); @@ -826,22 +824,20 @@ error = XFS_ERROR(E2BIG); goto error1; } - if (!noio) { - error = xfs_read_buf(mp, mp->m_ddev_targp, - d - XFS_FSS_TO_BB(mp, 1), - XFS_FSS_TO_BB(mp, 1), 0, &bp); - if (!error) { - xfs_buf_relse(bp); - } else { - cmn_err(CE_WARN, "XFS: size check 2 failed"); - if (error == ENOSPC) { - error = XFS_ERROR(E2BIG); - } - goto error1; + error = xfs_read_buf(mp, mp->m_ddev_targp, + d - XFS_FSS_TO_BB(mp, 1), + XFS_FSS_TO_BB(mp, 1), 0, &bp); + if (!error) { + xfs_buf_relse(bp); + } else { + cmn_err(CE_WARN, "XFS: size check 2 failed"); + if (error == ENOSPC) { + error = XFS_ERROR(E2BIG); } + goto error1; } - if (!noio && ((mfsi_flags & XFS_MFSI_CLIENT) == 0) && + if (((mfsi_flags & XFS_MFSI_CLIENT) == 0) && mp->m_logdev_targp != mp->m_ddev_targp) { d = (xfs_daddr_t)XFS_FSB_TO_BB(mp, mp->m_sb.sb_logblocks); if (XFS_BB_TO_FSB(mp, d) != mp->m_sb.sb_logblocks) { @@ -918,10 +914,6 @@ * Initialize the precomputed transaction reservations values. */ xfs_trans_init(mp); - if (noio) { - ASSERT((mfsi_flags & XFS_MFSI_CLIENT) == 0); - return 0; - } /* * Allocate and initialize the inode hash table for this --- 1.15/fs/xfs/xfs_mount.h Mon May 19 21:11:14 2003 +++ edited/fs/xfs/xfs_mount.h Sat Jun 14 21:35:21 2003 @@ -539,7 +539,7 @@ extern xfs_mount_t *xfs_mount_init(void); extern void xfs_mod_sb(xfs_trans_t *, __int64_t); extern void xfs_mount_free(xfs_mount_t *mp, int remove_bhv); -extern int xfs_mountfs(struct vfs *, xfs_mount_t *mp, dev_t, int); +extern int xfs_mountfs(struct vfs *, xfs_mount_t *mp, int); extern int xfs_unmountfs(xfs_mount_t *, struct cred *); extern void xfs_unmountfs_close(xfs_mount_t *, struct cred *); From owner-linux-xfs@oss.sgi.com Sun Jun 15 17:43:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Jun 2003 17:43:46 -0700 (PDT) Received: from web7303.mail.kr.yahoo.com (web7303.mail.yahoo.co.kr [211.119.129.144]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5G0hS2x028512 for ; Sun, 15 Jun 2003 17:43:29 -0700 Message-ID: <20030616004321.72992.qmail@web7303.mail.kr.yahoo.com> Received: from [165.213.1.1] by web7303.mail.kr.yahoo.com via HTTP; Mon, 16 Jun 2003 09:43:21 JST Date: Mon, 16 Jun 2003 09:43:21 +0900 (JST) From: =?euc-kr?q?Kwon=20SoonSon?= Subject: realtime block/extent/volume support in XFS? To: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=euc-kr Content-Transfer-Encoding: 8bit X-archive-position: 4336 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ksoonson@yahoo.co.kr Precedence: bulk X-list: linux-xfs Hi folks: Could anyone please let me know if there was any update on realtime block/extent/volume support in XFS on linux since release 1.1 or 1.2? The 1.1/1.2 release note says that it does not recommend using realtime feature in linux and not tested on it either. If there was any update since then, please let me know. I'd love to hear that. I would like to know if the realtime feature is appropriate for production site. Thanks very much... _____________________________________________________________________ °íÈ­Áú µ¿¿µ»óÀÌ °¡µæ - ¾ßÈÄ!ÇÁ¸®¹Ì¾ö VOD http://kr.broadcast.yahoo.com ½ÅÂ÷,Áß°íÂ÷,Á÷°Å·¡ ¸Å¹°ÀÌ ÇÑÀÚ¸®¿¡ - ¾ßÈÄ! ÀÚµ¿Â÷ http://autos.yahoo.co.kr/autos/ From owner-linux-xfs@oss.sgi.com Sun Jun 15 18:35:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Jun 2003 18:36:18 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5G1Zs2x029326 for ; Sun, 15 Jun 2003 18:35:56 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5G1qTmO011572 for ; Sun, 15 Jun 2003 20:52:29 -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 h5G1ZnqX4757708; Sun, 15 Jun 2003 20:35:49 -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 h5G1ZmYl12195605; Sun, 15 Jun 2003 20:35:48 -0500 (CDT) Date: Sun, 15 Jun 2003 20:35:48 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: =?euc-kr?q?Kwon=20SoonSon?= cc: linux-xfs@oss.sgi.com Subject: Re: realtime block/extent/volume support in XFS? In-Reply-To: <20030616004321.72992.qmail@web7303.mail.kr.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by tolkor.sgi.com id h5G1qTmO011572 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5G1Zu2x029327 X-archive-position: 4337 X-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 I did some work on realtime a month or so ago, to get basic functionality working again. So it basically seems to work, but it has not had heavy testing. Basically the same as before, I guess. It is probably about time to start spending some time on this feature. In terms of using it for a production site, (when it is supported), that depends on what you want to do. It would be appropriate for something like video streams, for example. The main difference is that it allocates in larger (potentially quite large) chunks, and has a more deterministic allocator. All realtime writes are also done with O_DIRECT (direct I/O) and some xfs-specific userspace calls, so your app would have to support it. -Eric On Mon, 16 Jun 2003, [euc-kr] Kwon SoonSon wrote: > Hi folks: > Could anyone please let me know if there was > any update on realtime block/extent/volume support > in XFS on linux since release 1.1 or 1.2? > > The 1.1/1.2 release note says that it does not > recommend > using realtime feature in linux and not tested on it > either. > > If there was any update since then, please let me > know. I'd love to hear that. > > I would like to know if the realtime feature is > appropriate > for production site. > > Thanks very much... > > _____________________________________________________________________ > °íÈ­Áú µ¿¿µ»óÀÌ °¡µæ - ¾ßÈÄ!ÇÁ¸®¹Ì¾ö VOD > http://kr.broadcast.yahoo.com > ½ÅÂ÷,Áß°íÂ÷,Á÷°Å·¡ ¸Å¹°ÀÌ ÇÑÀÚ¸®¿¡ - ¾ßÈÄ! ÀÚµ¿Â÷ > http://autos.yahoo.co.kr/autos/ > > From owner-linux-xfs@oss.sgi.com Mon Jun 16 03:54:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 03:54:41 -0700 (PDT) Received: from quail.cita.utoronto.ca (quail.cita.utoronto.ca [128.100.76.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GAsK2x027761 for ; Mon, 16 Jun 2003 03:54:20 -0700 Received: from cita.utoronto.ca (falcon.cita.utoronto.ca [128.100.76.51]) by quail.cita.utoronto.ca (8.12.8/8.12.8) with ESMTP id h5GAsENj019540 for ; Mon, 16 Jun 2003 06:54:14 -0400 Received: from falcon.cita.utoronto.ca (localhost [127.0.0.1]) by cita.utoronto.ca (8.12.8/8.12.8) with ESMTP id h5GAsF0l014003 for ; Mon, 16 Jun 2003 06:54:15 -0400 Received: (from rjh@localhost) by falcon.cita.utoronto.ca (8.12.8/8.12.8/Submit) id h5GAsF1R014001 for linux-xfs@oss.sgi.com; Mon, 16 Jun 2003 06:54:15 -0400 Date: Mon, 16 Jun 2003 06:54:14 -0400 From: Robin Humble To: linux-xfs@oss.sgi.com Subject: problem with cvs Message-ID: <20030616105414.GA13950@falcon.cita.utoronto.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-archive-position: 4338 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rjh@cita.utoronto.ca Precedence: bulk X-list: linux-xfs I'm getting this message when I do a cvs update: cvs [server aborted]: EOF in key in RCS file /cvs/linux-2.5-xfs/linux/fs/xfs/xfs_rw.h,v It's happened ~4 times now over the last day or so, and after I removed the offending file from my copy it still occurs, so I think it's a problem at oss. cheers, robin From owner-linux-xfs@oss.sgi.com Mon Jun 16 07:23:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 07:23:40 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GENM2x009634 for ; Mon, 16 Jun 2003 07:23:23 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5GEdwmO007797 for ; Mon, 16 Jun 2003 09:39:58 -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 h5GENGqX4819660 for ; Mon, 16 Jun 2003 09:23:16 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5GENGRn120622154 for ; Mon, 16 Jun 2003 09:23:16 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5GENGp12620; Mon, 16 Jun 2003 09:23:16 -0500 Message-Id: <200306161423.h5GENGp12620@jen.americas.sgi.com> Date: Mon, 16 Jun 2003 09:23:16 -0500 Subject: TAKE - remove some dead code To: linux-xfs@oss.sgi.com X-archive-position: 4339 X-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 Remove a dead code path from mount, noticed by Al Viro. Date: Mon Jun 16 07:22:52 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: 2.4.x-xfs:slinx:151226a linux/fs/xfs/xfs_iocore.c - 1.42 linux/fs/xfs/xfs_mount.h - 1.173 - drop dev arg from xfs_mountfs linux/fs/xfs/xfs_mount.c - 1.330 - drop dev arg from xfs_mountfs, and the noio path which is never executed. From owner-linux-xfs@oss.sgi.com Mon Jun 16 08:11:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 08:12:15 -0700 (PDT) Received: from badboy.mail.pas.earthlink.net (badboy.mail.pas.earthlink.net [207.217.120.20]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GFBk2x011062 for ; Mon, 16 Jun 2003 08:11:47 -0700 Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by badboy.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id h5GF47K14620 for ; Mon, 16 Jun 2003 08:04:07 -0700 (PDT) Received: from jtrostel.gtri.gatech.edu ([130.207.208.27]) by heron.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 19RvOk-0002qk-00; Mon, 16 Jun 2003 07:55:55 -0700 Subject: Re: problem with cvs From: John Trostel Reply-To: jtrostel@mindspring.com To: Robin Humble Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030616105414.GA13950@falcon.cita.utoronto.ca> References: <20030616105414.GA13950@falcon.cita.utoronto.ca> Content-Type: text/plain Message-Id: <1055775761.21174.0.camel@jtrostel.gtri.gatech.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 16 Jun 2003 11:02:41 -0400 Content-Transfer-Encoding: 7bit X-ELNK-Trace: 4406d925d35d96b29c7f779228e2f6aeda0071232e20db4d121e087ac5ce62b351fd476d76addcf9350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-archive-position: 4340 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jtrostel@mindspring.com Precedence: bulk X-list: linux-xfs I tried removing that file and then doing a 'cvs update -d -P'. It works fine from here. (Replaced the file and keep right on truckin') On Mon, 2003-06-16 at 06:54, Robin Humble wrote: > I'm getting this message when I do a cvs update: > cvs [server aborted]: EOF in key in RCS file /cvs/linux-2.5-xfs/linux/fs/xfs/xfs_rw.h,v > > It's happened ~4 times now over the last day or so, and after I removed > the offending file from my copy it still occurs, so I think it's a > problem at oss. > > cheers, > robin -- John M. Trostel Atlanta, Georgia USA jtrostel@mindspring.com GPG Key Fingerprint: FE1F DFCE 4BF1 A8A8 5766 CBCB B0C3 FD47 3F78 A1FC From owner-linux-xfs@oss.sgi.com Mon Jun 16 08:42:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 08:43:06 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GFgi2x012587 for ; Mon, 16 Jun 2003 08:42:45 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5GFxKmO012140 for ; Mon, 16 Jun 2003 10:59:20 -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 h5GFgcqX4826180 for ; Mon, 16 Jun 2003 10:42:38 -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 h5GFgbRn117774326 for ; Mon, 16 Jun 2003 10:42:37 -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 h5GFgb5g025858 for ; Mon, 16 Jun 2003 10:42:37 -0500 Received: (from cattelan@localhost) by chuckle.americas.sgi.com (8.12.8/8.12.8/Submit) id h5GFgaVo025856 for linux-xfs@oss.sgi.com; Mon, 16 Jun 2003 10:42:36 -0500 Date: Mon, 16 Jun 2003 10:42:36 -0500 From: Russell Cattelan Message-Id: <200306161542.h5GFgaVo025856@chuckle.americas.sgi.com> Subject: TAKE - Merge the 1.3 tree to TOT... mostly just bring it up to 2.4.21 X-archive-position: 4341 X-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 Date: Mon Jun 16 08:42:12 PDT 2003 Workarea: chuckle.americas.sgi.com:/go/xfs2/XFS/x2.4-xfs-r1.3 Merged by: cattelan Merged mods: 2.4.x-xfs:slinx:150285a,2.4.x-xfs:slinx:150861a,2.4.x-xfs:slinx:151032a 2.4.x-xfs:slinx:151145a,2.4.x-xfs:slinx:151168a 2.4.x-xfs:slinx:151226a,2.4.x-xfs:slinx:151227a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs-r1.3 Modid: 2.4.x-xfs-r1.3:slinx:151232a linux/net/ipv6/tcp_ipv6.c - 1.38 linux/net/ipv6/reassembly.c - 1.13 linux/net/ipv6/af_inet6.c - 1.21 linux/net/ipv4/sysctl_net_ipv4.c - 1.16 linux/net/ipv4/ip_fragment.c - 1.18 linux/net/ipv4/af_inet.c - 1.34 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 linux/mm/memory.c - 1.81 - Merge of 2.4.x-xfs:slinx:150861a originally by kaos on 06/10/03 Upgrade XFS to 2.4.21-rc8 linux/include/scsi/sg.h - 1.15 linux/include/net/transp_v6.h - 1.3 linux/include/linux/sysctl.h - 1.54 linux/include/asm-sparc64/auxio.h - 1.5 linux/include/asm-sparc/winmacro.h - 1.6 linux/include/asm-sparc/uaccess.h - 1.9 linux/include/asm-sparc/system.h - 1.12 linux/include/asm-sparc/ptrace.h - 1.3 linux/include/asm-sparc/processor.h - 1.19 linux/include/asm-sparc/kgdb.h - 1.3 linux/include/asm-sparc/floppy.h - 1.7 linux/include/asm-sparc/auxio.h - 1.3 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 linux/fs/ext2/balloc.c - 1.17 - Merge of 2.4.x-xfs:slinx:150861a originally by kaos on 06/10/03 Upgrade XFS to 2.4.21-rc8 linux/drivers/scsi/sg.c - 1.28 linux/drivers/sbus/char/envctrl.c - 1.16 linux/drivers/net/sunlance.c - 1.28 linux/drivers/fc4/socal.c - 1.12 linux/drivers/fc4/soc.c - 1.12 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 linux/drivers/char/rocket_int.h - 1.4 - Merge of 2.4.x-xfs:slinx:150861a originally by kaos on 06/10/03 Upgrade XFS to 2.4.21-rc8 linux/arch/sparc64/kernel/traps.c - 1.19 linux/arch/sparc64/kernel/sys_sparc32.c - 1.48 linux/arch/sparc64/kernel/sys_sparc.c - 1.25 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.41 linux/arch/sparc64/kernel/smp.c - 1.38 linux/arch/sparc64/kernel/ioctl32.c - 1.54 linux/arch/sparc64/kernel/entry.S - 1.21 linux/arch/sparc64/kernel/auxio.c - 1.8 linux/arch/sparc/prom/misc.c - 1.4 linux/arch/sparc/mm/sun4c.c - 1.34 linux/arch/sparc/mm/srmmu.c - 1.31 linux/arch/sparc/kernel/wuf.S - 1.5 linux/arch/sparc/kernel/wof.S - 1.5 linux/arch/sparc/kernel/windows.c - 1.5 linux/arch/sparc/kernel/traps.c - 1.10 linux/arch/sparc/kernel/trampoline.S - 1.4 linux/arch/sparc/kernel/sys_sparc.c - 1.15 linux/arch/sparc/kernel/sunos_asm.S - 1.4 linux/arch/sparc/kernel/sparc_ksyms.c - 1.29 linux/arch/sparc/kernel/smp.c - 1.16 linux/arch/sparc/kernel/signal.c - 1.21 linux/arch/sparc/kernel/rtrap.S - 1.9 linux/arch/sparc/kernel/process.c - 1.25 linux/arch/sparc/kernel/head.S - 1.11 linux/arch/sparc/kernel/etrap.S - 1.5 linux/arch/sparc/kernel/entry.S - 1.13 linux/arch/sparc/kernel/auxio.c - 1.5 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 linux/Makefile - 1.189 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 Merge of 2.4.x-xfs:slinx:150861a originally by kaos on 06/10/03 Upgrade XFS to 2.4.21-rc8 Merge of 2.4.x-xfs:slinx:151145a originally by lord on 06/13/03 Change version string from 2.4.21-rc8-xfs to 2.4.21-xfs rc8 became the release linux/include/linux/iobuf.h - 1.17 - Merge of 2.4.x-xfs:slinx:150861a originally by kaos on 06/10/03 Upgrade XFS to 2.4.21-rc8 linux/arch/sparc64/kernel/power.c - 1.10 linux/include/asm-sh/page.h - 1.12 linux/drivers/net/tokenring/olympic.c - 1.20 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 linux/fs/xfs/xfs_iocore.c - 1.42 linux/fs/xfs/xfs_mount.h - 1.173 - Merge of 2.4.x-xfs:slinx:151226a originally by lord on 06/16/03 Remove a dead code path from mount, noticed by Al Viro. drop dev arg from xfs_mountfs linux/fs/xfs/xfs_mount.c - 1.330 - Merge of 2.4.x-xfs:slinx:151226a originally by lord on 06/16/03 Remove a dead code path from mount, noticed by Al Viro. drop dev arg from xfs_mountfs, and the noio path which is never executed. linux/fs/xfs/linux/xfs_vfs.h - 1.41 - Merge of 2.4.x-xfs:slinx:151227a originally by lord on 06/16/03 SYNC_FSDATA and SYNC_REFCACHE are supposed to be distinct values, they ended up the same somehow. make SYNC_FSDATA and SYNC_REFCACHE different linux/mm/shmem.c - 1.35 - Merge of 2.4.x-xfs:slinx:150861a originally by kaos on 06/10/03 Upgrade XFS to 2.4.21-rc8 linux/drivers/sbus/char/bbc_envctrl.c - 1.2 linux/drivers/sbus/char/bbc_i2c.c - 1.2 linux/arch/sh/kernel/pcibios.c - 1.3 linux/arch/sh/kernel/io_7751se.c - 1.3 - Merge of 2.4.x-xfs:slinx:150285a originally by kaos on 06/03/03 Upgrade XFS to 2.4.21-rc7 linux/fs/xfs/pagebuf/page_buf.c - 1.121 - Merge of 2.4.x-xfs:slinx:151032a originally by lord on 06/12/03 Move the pagebuf_runall_queues out from under a spinlock, if it sleeps (which it might), this is not the right place for it to be. There is also no reason for it to be under a spinlock. move pagebuf_runall_queues out from under the pbd_delwrite_lock spinlock. linux/fs/xfs/pagebuf/page_buf_internal.h - 1.23 - Merge of 2.4.x-xfs:slinx:151168a originally by lord on 06/13/03 fix the sysctl & /proc interface for pagebuf so you can turn tracing on and off again transpose debug and stats_clear config vars in structure From owner-linux-xfs@oss.sgi.com Mon Jun 16 08:44:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 08:44:23 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GFiJ2x012879 for ; Mon, 16 Jun 2003 08:44:19 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5GG0tmO012223 for ; Mon, 16 Jun 2003 11:00:55 -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 h5GFiDqX4833051; Mon, 16 Jun 2003 10:44:13 -0500 (CDT) Received: from [128.162.232.98] (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5GFiDRn115054397; Mon, 16 Jun 2003 10:44:13 -0500 (CDT) Subject: Re: problem with cvs From: Russell Cattelan To: Robin Humble Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030616105414.GA13950@falcon.cita.utoronto.ca> References: <20030616105414.GA13950@falcon.cita.utoronto.ca> Content-Type: text/plain Organization: Message-Id: <1055778230.25758.28.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 16 Jun 2003 10:43:50 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4342 X-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 On Mon, 2003-06-16 at 05:54, Robin Humble wrote: > I'm getting this message when I do a cvs update: > cvs [server aborted]: EOF in key in RCS file /cvs/linux-2.5-xfs/linux/fs/xfs/xfs_rw.h,v > > It's happened ~4 times now over the last day or so, and after I removed > the offending file from my copy it still occurs, so I think it's a > problem at oss. There does appear to a problem with the files. The tree has been removed, the cvs push scripts will rebuild it from scratch in an hour or so. Russell From owner-linux-xfs@oss.sgi.com Mon Jun 16 09:10:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 09:10:31 -0700 (PDT) Received: from imf17aec.bellsouth.net (mail100.mail.bellsouth.net [205.152.58.40]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GGAF2x014867 for ; Mon, 16 Jun 2003 09:10:16 -0700 Received: from tiger2 ([66.156.3.41]) by imf17aec.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id <20030616161007.TGPH13122.imf17aec.bellsouth.net@tiger2> for ; Mon, 16 Jun 2003 12:10:07 -0400 Date: Mon, 16 Jun 2003 12:18:02 -0400 From: Greg Freemyer Subject: NFS performance (with XFS 1.3pre or 2.4.21 cvs) To: xfs mailing list Mime-Version: 1.0 Organization: Norcross Group X-Mailer: GoldMine [6.00.21021] Content-Type: Text/plain Message-Id: <20030616161007.TGPH13122.imf17aec.bellsouth.net@tiger2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5GGAG2x014883 X-archive-position: 4343 X-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@NorcrossGroup.com Precedence: bulk X-list: linux-xfs I normally use the SuSE 8.2 standard kernel (2.4.20 + XFS 1.2 + lots of other patches) The NFS performance is pretty poor. Has anyone done any NFS performance testing with XFS 1.3pre, or recent 2.4.21 cvs? Thanks Greg -- Greg Freemyer From owner-linux-xfs@oss.sgi.com Mon Jun 16 09:17:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 09:18:02 -0700 (PDT) Received: from localhost.fsl.noaa.gov (woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GGHu2x016375 for ; Mon, 16 Jun 2003 09:17:57 -0700 Received: from localhost (woody [127.0.0.1]) by localhost.fsl.noaa.gov (8.12.5/8.12.5) with ESMTP id h5GGPnKv005093; Mon, 16 Jun 2003 10:25:49 -0600 Subject: Re: NFS performance (with XFS 1.3pre or 2.4.21 cvs) From: Craig Tierney To: Greg Freemyer Cc: xfs mailing list In-Reply-To: <20030616161007.TGPH13122.imf17aec.bellsouth.net@tiger2> References: <20030616161007.TGPH13122.imf17aec.bellsouth.net@tiger2> Content-Type: text/plain Organization: Message-Id: <1055780748.19561.134.camel@woody> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 16 Jun 2003 10:25:49 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 4344 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ctierney@hpti.com Precedence: bulk X-list: linux-xfs On Mon, 2003-06-16 at 10:18, Greg Freemyer wrote: > I normally use the SuSE 8.2 standard kernel (2.4.20 + XFS 1.2 + lots of other patches) > > The NFS performance is pretty poor. > > Has anyone done any NFS performance testing with XFS 1.3pre, or recent 2.4.21 cvs? What do yo mean by 'the NFS performance is pretty poor'? I am running Redhat 8.0 with the kernel upgraded to 2.4.20 + XFS 1.2 and I am happy with the NFS performance. I would like it to be better, but I am not blaming XFS for the performance issue. My NFS performance is 50% of the underlying disk speed. I run with NFS v3, UDP, 8k rsize and wsize. The performance of XFS is better than EXT3 for my tests. I usually use multiple instances of dd from multiple nodes. I care about big files not small files. The small file performance and interactivity is satisfactory though. What are you getting and what do you expect? Craig > > Thanks > Greg -- Craig Tierney From owner-linux-xfs@oss.sgi.com Mon Jun 16 09:37:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 09:37:39 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GGbY2x018105 for ; Mon, 16 Jun 2003 09:37: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.2/linux-outbound_gateway-1.2) with ESMTP id h5GEZ0E0013100 for ; Mon, 16 Jun 2003 07:35:00 -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 h5GEZ0qX4828083 for ; Mon, 16 Jun 2003 09:35:00 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5GEYxRn123045691 for ; Mon, 16 Jun 2003 09:34:59 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5GEYpZ12696; Mon, 16 Jun 2003 09:34:51 -0500 Message-Id: <200306161434.h5GEYpZ12696@jen.americas.sgi.com> Date: Mon, 16 Jun 2003 09:34:51 -0500 Subject: TAKE - make two sync related constants different To: linux-xfs@oss.sgi.com X-archive-position: 4345 X-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 SYNC_FSDATA and SYNC_REFCACHE are supposed to be distinct values, they ended up the same somehow. Little actual effect except on nfs servers where the reference cache was getting purged faster than planned. Date: Mon Jun 16 07:32: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: 2.4.x-xfs:slinx:151227a linux/fs/xfs/linux/xfs_vfs.h - 1.41 - make SYNC_FSDATA and SYNC_REFCACHE different From owner-linux-xfs@oss.sgi.com Mon Jun 16 09:51:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 09:51:23 -0700 (PDT) Received: from imf21aec.bellsouth.net (mail102.mail.bellsouth.net [205.152.58.42]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GGpJ2x019124 for ; Mon, 16 Jun 2003 09:51:19 -0700 Received: from tiger2 ([66.156.3.41]) by imf21aec.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id <20030616165114.FLWH16037.imf21aec.bellsouth.net@tiger2>; Mon, 16 Jun 2003 12:51:14 -0400 Date: Mon, 16 Jun 2003 12:59:09 -0400 From: Greg Freemyer Subject: re[2]: NFS performance (with XFS 1.3pre or 2.4.21 cvs) To: Craig Tierney cc: xfs mailing list Mime-Version: 1.0 Organization: Norcross Group X-Mailer: GoldMine [6.00.21021] Content-Type: Text/plain Message-Id: <20030616165114.FLWH16037.imf21aec.bellsouth.net@tiger2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5GGpK2x019129 X-archive-position: 4346 X-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@NorcrossGroup.com Precedence: bulk X-list: linux-xfs >> On Mon, 2003-06-16 at 10:18, Greg Freemyer wrote: >> > I normally use the SuSE 8.2 standard kernel (2.4.20 + XFS 1.2 + lots of >> other patches) >> > >> > The NFS performance is pretty poor. >> > >> > Has anyone done any NFS performance testing with XFS 1.3pre, or recent >> 2.4.21 cvs? >> What do yo mean by 'the NFS performance is pretty poor'? I am running >> Redhat 8.0 with the kernel upgraded to 2.4.20 + XFS 1.2 and I am happy >> with the NFS performance. I would like it to be better, but I am not >> blaming XFS for the performance issue. My NFS performance is >> 50% of the underlying disk speed. I run with NFS v3, UDP, 8k rsize and >> wsize. The performance of XFS is better than EXT3 for my tests. >> I usually use multiple instances of dd from multiple nodes. I care >> about big files not small files. The small file performance and >> interactivity is satisfactory though. >> What are you getting and what do you expect? >> Craig Craig, We have done some basic testing with iometer and 4 clients (I think) and 100Mbit lan (dedicated in a lab). With Samba Shares I can get almost 100% efficiency across the lan (i.e. 10 MB/sec of data) With NFS (NVS v3, UDP, default rsize/wsize), I'm only getting about 10% efficiency (i.e. 1 MB/sec of data). I have not cared too much previously, but I need to start using NFS soon, and I need to pick between 3 choices: 1) Work with the SuSE kernel and try to tune it. 2) Use a pure XFS 1.2 kernel (2.4.19 based) 3) Go with a XFS 1.3pre kernel (currently 2.4.20, but apparently soon to be 2.4.21) If the latest XFS 1.3pre or cvs code seems to be working well with NFS, that is my preference. Greg -- Greg Freemyer From owner-linux-xfs@oss.sgi.com Mon Jun 16 10:03:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 10:03:22 -0700 (PDT) Received: from localhost.fsl.noaa.gov (woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GH3H2x020038 for ; Mon, 16 Jun 2003 10:03:17 -0700 Received: from localhost (woody [127.0.0.1]) by localhost.fsl.noaa.gov (8.12.5/8.12.5) with ESMTP id h5GHBCKv005189; Mon, 16 Jun 2003 11:11:12 -0600 Subject: Re: re[2]: NFS performance (with XFS 1.3pre or 2.4.21 cvs) From: Craig Tierney To: Greg Freemyer Cc: xfs mailing list In-Reply-To: <20030616165114.FLWH16037.imf21aec.bellsouth.net@tiger2> References: <20030616165114.FLWH16037.imf21aec.bellsouth.net@tiger2> Content-Type: text/plain Organization: Message-Id: <1055783471.17968.150.camel@woody> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 16 Jun 2003 11:11:12 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 4347 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ctierney@hpti.com Precedence: bulk X-list: linux-xfs On Mon, 2003-06-16 at 10:59, Greg Freemyer wrote: > >> On Mon, 2003-06-16 at 10:18, Greg Freemyer wrote: > >> > I normally use the SuSE 8.2 standard kernel (2.4.20 + XFS 1.2 + lots of > >> other patches) > >> > > >> > The NFS performance is pretty poor. > >> > > >> > Has anyone done any NFS performance testing with XFS 1.3pre, or recent > >> 2.4.21 cvs? > > >> What do yo mean by 'the NFS performance is pretty poor'? I am running > >> Redhat 8.0 with the kernel upgraded to 2.4.20 + XFS 1.2 and I am happy > >> with the NFS performance. I would like it to be better, but I am not > >> blaming XFS for the performance issue. My NFS performance is > >> 50% of the underlying disk speed. I run with NFS v3, UDP, 8k rsize and > >> wsize. The performance of XFS is better than EXT3 for my tests. > >> I usually use multiple instances of dd from multiple nodes. I care > >> about big files not small files. The small file performance and > >> interactivity is satisfactory though. > > >> What are you getting and what do you expect? > > >> Craig > > Craig, > > We have done some basic testing with iometer and 4 clients (I think) and 100Mbit lan (dedicated in a lab). > > With Samba Shares I can get almost 100% efficiency across the lan (i.e. 10 MB/sec of data) > > With NFS (NVS v3, UDP, default rsize/wsize), I'm only getting about 10% efficiency (i.e. 1 MB/sec of data). > > I have not cared too much previously, but I need to start using NFS soon, and I need to pick between 3 choices: > > 1) Work with the SuSE kernel and try to tune it. > 2) Use a pure XFS 1.2 kernel (2.4.19 based) > 3) Go with a XFS 1.3pre kernel (currently 2.4.20, but apparently soon to be 2.4.21) > > If the latest XFS 1.3pre or cvs code seems to be working well with NFS, that is my preference. > I do not have this problem. I get about 11 MB/s over Fast ethernet. This with very fast disk. The default settings for NFS are not as optimal as they should be. The default rsize/wsize is 1024. You should increase this to 8192. Also, write sync is on by default and will hurt performance. I turn that off (I don't need it). You have to set nosync on the server and the clients. Also look at the NFS performance HOWTO for other suggestions and tweaks. http://nfs.sourceforge.net/nfs-howto/performance.html > Greg -- Craig Tierney From owner-linux-xfs@oss.sgi.com Mon Jun 16 10:17:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 10:17:21 -0700 (PDT) Received: from imf25aec.bellsouth.net (mail104.mail.bellsouth.net [205.152.58.44]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GHH62x020967 for ; Mon, 16 Jun 2003 10:17:07 -0700 Received: from tiger2 ([66.156.3.41]) by imf25aec.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id <20030616171701.BMNO20256.imf25aec.bellsouth.net@tiger2>; Mon, 16 Jun 2003 13:17:01 -0400 Date: Mon, 16 Jun 2003 13:24:57 -0400 From: Greg Freemyer Subject: re[4]: NFS performance (with XFS 1.3pre or 2.4.21 cvs) To: Craig Tierney cc: xfs mailing list Mime-Version: 1.0 Organization: Norcross Group X-Mailer: GoldMine [6.00.21021] Content-Type: Text/plain Message-Id: <20030616171701.BMNO20256.imf25aec.bellsouth.net@tiger2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5GHH72x020971 X-archive-position: 4348 X-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@NorcrossGroup.com Precedence: bulk X-list: linux-xfs >> I do not have this problem. I get about 11 MB/s over >> Fast ethernet. This with very fast disk. The default >> settings for NFS are not as optimal as they should be. >> The default rsize/wsize is 1024. You should increase >> this to 8192. Also, write sync is on by default and >> will hurt performance. I turn that off (I don't need it). >> You have to set nosync on the server and the clients. >> Also look at the NFS performance HOWTO for other >> suggestions and tweaks. >> http://nfs.sourceforge.net/nfs-howto/performance.html Thanks for the tuning help. I will give it a try today or tomorrow. Greg From owner-linux-xfs@oss.sgi.com Mon Jun 16 13:00:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 13:01:01 -0700 (PDT) Received: from smtp.covadmail.net ([63.65.120.66]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GK0j2x008645 for ; Mon, 16 Jun 2003 13:00:46 -0700 Received: (covad.net 4484 invoked from network); 16 Jun 2003 20:00:36 -0000 Received: from unknown (HELO boywonderfx.com) (66.167.1.42) by sun-qmail14 with SMTP; 16 Jun 2003 20:00:36 -0000 Message-ID: <3EEE21E3.20108@boywonderfx.com> Date: Mon, 16 Jun 2003 13:00:35 -0700 From: Michael Whang User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: 2k/XFS dual-boot disk clone Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4349 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mwhang@boywonderfx.com Precedence: bulk X-list: linux-xfs Has anyone successfully cloned a dual boot windows/XFS disk? What is the best program to use. I tried using norton ghost but have encountered the following error: Unable to find a free MBR slot in the Virtual Partition DLL. This is usually due to there being no free primary partition slots left on the boot disk. What can i do resolve this? Mike From owner-linux-xfs@oss.sgi.com Mon Jun 16 14:01:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 14:01:35 -0700 (PDT) Received: from karnickel.franken.de (karnickel.4msp.de [217.6.190.222]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5GL1D2x012007 for ; Mon, 16 Jun 2003 14:01:15 -0700 Received: from karnickel.franken.de (localhost [127.0.0.1]) by karnickel.franken.de (8.12.9/8.12.9) with ESMTP id h5GL1C1J029649 for ; Mon, 16 Jun 2003 23:01:12 +0200 (CEST) Received: (from uucp@localhost) by karnickel.franken.de (8.12.9/8.12.2/Submit) with UUCP id h5GL1C0u029648 for linux-xfs@oss.sgi.com; Mon, 16 Jun 2003 23:01:12 +0200 (CEST) (envelope-from erik@debian.franken.de) Received: by tpl.lokalnetz (Postfix, from userid 1000) id DBB378F78B2; Mon, 16 Jun 2003 22:57:18 +0200 (CEST) Date: Mon, 16 Jun 2003 22:57:18 +0200 To: linux-xfs@oss.sgi.com Subject: Bug in xfs_repair Message-ID: <20030616205718.GA6783@debian.franken.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="liOOAslEiF7prFVr" Content-Disposition: inline User-Agent: Mutt/1.5.4i From: erik@debian.franken.de (Erik Tews) X-archive-position: 4350 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erik@debian.franken.de Precedence: bulk X-list: linux-xfs --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi I think I found a bug in xfs_repair. It saegfaults when I run it on a filesystem which is a little bit corrupt. After I ran it with efence, I got these backtraces. I think it cannot handle this block-out-of-range condition correctly. I have attached all important informations. --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=backtrace (gdb) bt #0 0x0807918f in scanfunc_bno (ablock=0x405bd000, level=0, bno=338, agno=9, suspect=0, isroot=1) at scan.c:569 #1 0x0807760a in scan_sbtree (root=338, nlevels=1, agno=9, suspect=0, func=0x8078d05 , isroot=1) at scan.c:84 #2 0x0807b401 in scan_ag (agno=9) at swab.h:125 #3 0x0806570f in phase2 (mp=0xbfffdc70) at phase2.c:149 #4 0x0807c9e9 in main (argc=2, argv=0xbfffdc70) at xfs_repair.c:506 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=xfs-check-log dir 128 block 0 entry /ost+found bad inode number -72057594037927937 dir 128 block 0 extra leaf entry 21aa60c 28 dir ino 128 missing leaf entry for 821aa62d/28 block 9/65529 out of range block 9/65530 out of range block 9/65531 out of range block 9/65532 out of range block 9/65533 out of range block 9/65534 out of range block 9/65535 out of range block 9/65536 out of range block 9/65537 out of range block 9/65538 out of range block 9/65539 out of range block 9/65540 out of range block 9/65541 out of range block 9/65542 out of range block 9/65543 out of range block 9/65544 out of range block 9/65545 out of range block 9/65546 out of range block 9/65547 out of range block 9/65548 out of range blocks 9/65529..65548 claimed by block 9/338 block 9/65529 out of range block 9/65530 out of range block 9/65531 out of range block 9/65532 out of range block 9/65533 out of range block 9/65534 out of range block 9/65535 out of range block 9/65536 out of range block 9/65537 out of range block 9/65538 out of range block 9/65539 out of range block 9/65540 out of range block 9/65541 out of range block 9/65542 out of range block 9/65543 out of range block 9/65544 out of range block 9/65545 out of range block 9/65546 out of range block 9/65547 out of range block 9/65548 out of range blocks 9/65529..65548 claimed by block 9/902 block 10/4200613472 out of range blocks 10/4200613472..4200613472 claimed by block 10/0 block 10/2742227945 out of range blocks 10/2742227945..2742227945 claimed by block 10/0 block 10/1030081898 out of range blocks 10/1030081898..1030081898 claimed by block 10/0 block 10/1266619198 out of range blocks 10/1266619198..1266619198 claimed by block 10/0 link count mismatch for inode 3594 (name ?), nlink 1, counted 3 link count mismatch for inode 59683 (name ?), nlink 2, counted 1 block 9/65529 type unknown not expected block 9/65530 type unknown not expected block 9/65531 type unknown not expected block 9/65532 type unknown not expected block 9/65533 type unknown not expected block 9/65534 type unknown not expected link count mismatch for inode 9446615 (name ?), nlink 2, counted 1 block 10/4 type unknown not expected block 10/5 type unknown not expected block 10/6 type unknown not expected block 10/7 type unknown not expected sb_ifree 57790, counted 57791 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=xfs-repair-log Electric Fence 2.1 Copyright (C) 1987-1998 Bruce Perens. Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... --liOOAslEiF7prFVr-- From owner-linux-xfs@oss.sgi.com Mon Jun 16 17:32:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 17:33:01 -0700 (PDT) Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H0Wg2x022234 for ; Mon, 16 Jun 2003 17:32:43 -0700 Received: from whitestar.arts.usyd.edu.au (whitestar.arts.usyd.edu.au [129.78.16.20]) by plato.arts.usyd.edu.au (8.12.9/8.12.6) with ESMTP id h5H0Wfrj009244 for ; Tue, 17 Jun 2003 10:32:41 +1000 (EST) Subject: Not strictly an XFS question From: Matthew Geier To: XFS List Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 17 Jun 2003 10:32:53 +1000 Message-Id: <1055809974.11774.13.camel@whitestar.arts.usyd.edu.au> Mime-Version: 1.0 X-archive-position: 4351 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: matthew@arts.usyd.edu.au Precedence: bulk X-list: linux-xfs Using XFS 2.4.21 cvs on a Athlon/Nforce2 PC, on an otherwise standard RedHat 9 install. When I burn a CD, the system locks hard. Only signs of life are blinking keyboard lights. Have to press reset. I can't seem to find exactly what the blinking lights mean. I assume something really BAD has happened to the kernel... Works with the standard RD kernel (but the HD doesn't run in the fasted DMA mode it supports and firewire doesn't work at all). I don't actually have any XFS file systems on this box - the XFS/RH9 boot disk people have done won't boot on this machine. I do use XFS on other boxen hence using the XFS kernel on this particular machine. From owner-linux-xfs@oss.sgi.com Mon Jun 16 18:57:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 18:57:34 -0700 (PDT) Received: from maul.jdc.home (Nm@12-226-0-64.client.attbi.com [12.226.0.64]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H1v92x025002 for ; Mon, 16 Jun 2003 18:57:09 -0700 Received: from warblade.jdc.home (warblade.jdc.home [10.1.1.2]) by maul.jdc.home (Postfix) with ESMTP id C1FAC34000BA; Mon, 16 Jun 2003 21:26:07 -0400 (EDT) Subject: Re: Not strictly an XFS question From: Jim Crilly To: Matthew Geier Cc: XFS List In-Reply-To: <1055809974.11774.13.camel@whitestar.arts.usyd.edu.au> References: <1055809974.11774.13.camel@whitestar.arts.usyd.edu.au> Content-Type: text/plain Message-Id: <1055813167.4517.1.camel@warblade.jdc.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.92 (Preview Release) Date: 16 Jun 2003 21:26:07 -0400 Content-Transfer-Encoding: 7bit X-archive-position: 4352 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jim@why.dont.jablowme.net Precedence: bulk X-list: linux-xfs The blinking lights mean the kernel has entered kdb. Your best bet, if possible, is to setup a serial console to another machine so you can use kdb to atleast see why the kernel crashed. Jim. On Mon, 2003-06-16 at 20:32, Matthew Geier wrote: > Using XFS 2.4.21 cvs on a Athlon/Nforce2 PC, on an otherwise standard > RedHat 9 install. When I burn a CD, the system locks hard. Only signs of > life are blinking keyboard lights. Have to press reset. I can't seem to > find exactly what the blinking lights mean. I assume something really > BAD has happened to the kernel... > > Works with the standard RD kernel (but the HD doesn't run in the fasted > DMA mode it supports and firewire doesn't work at all). > > I don't actually have any XFS file systems on this box - the XFS/RH9 > boot disk people have done won't boot on this machine. I do use XFS on > other boxen hence using the XFS kernel on this particular machine. > > > From owner-linux-xfs@oss.sgi.com Mon Jun 16 19:05:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 19:06:12 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H25t2x025595 for ; Mon, 16 Jun 2003 19:05:55 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5H25nE0026473 for ; Mon, 16 Jun 2003 19:05:50 -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 h5H25mqX4913899; Mon, 16 Jun 2003 21:05:48 -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 h5H25lYl11735314; Mon, 16 Jun 2003 21:05:47 -0500 (CDT) Date: Mon, 16 Jun 2003 21:05:47 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Jim Crilly cc: Matthew Geier , XFS List Subject: Re: Not strictly an XFS question In-Reply-To: <1055813167.4517.1.camel@warblade.jdc.home> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4353 X-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 If you're at the console, you should not need a serial console unless you are in X. If you are in X, the system can drop into kdb but there is no way to get to the kdb prompt. However, since you didn't see the prompt I'll assume you -are- in x. :) You might try blindly typing "go" and see if your system comes back. At this point a reboot is probably in order, but a check of your system logs might give you a hint as to what went wrong. -Eric On 16 Jun 2003, Jim Crilly wrote: > The blinking lights mean the kernel has entered kdb. Your best bet, if > possible, is to setup a serial console to another machine so you can use > kdb to atleast see why the kernel crashed. > > Jim. From owner-linux-xfs@oss.sgi.com Mon Jun 16 19:11:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 19:11:19 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H2BE2x026078 for ; Mon, 16 Jun 2003 19:11:15 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h5H2RpmO016910 for ; Mon, 16 Jun 2003 21:27:51 -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 MAA23814; Tue, 17 Jun 2003 12:09:49 +1000 Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id 0C2A4D8F46; Tue, 17 Jun 2003 12:09:50 +1000 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 0978391336; Tue, 17 Jun 2003 12:09:50 +1000 (EST) X-Mailer: exmh version 2.5 01/15/2001 with nmh-1.0.4 From: Keith Owens To: Matthew Geier Cc: XFS List Subject: Re: Not strictly an XFS question In-reply-to: Your message of "17 Jun 2003 10:32:53 +1000." <1055809974.11774.13.camel@whitestar.arts.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 17 Jun 2003 12:09:45 +1000 Message-ID: <4572.1055815785@kao2.melbourne.sgi.com> X-archive-position: 4354 X-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 On 17 Jun 2003 10:32:53 +1000, Matthew Geier wrote: > > Using XFS 2.4.21 cvs on a Athlon/Nforce2 PC, on an otherwise standard >RedHat 9 install. When I burn a CD, the system locks hard. Only signs of >life are blinking keyboard lights. Have to press reset. I can't seem to >find exactly what the blinking lights mean. I assume something really >BAD has happened to the kernel... Either a panic or an oops that has dropped into kdb. Both panic and kdb flash the keyboard lights to tell you that something is wrong. If you reproduce the problem on a text console (not under X) then you will see the error messages. See also Documentation/oops-tracing.txt. From owner-linux-xfs@oss.sgi.com Mon Jun 16 23:05:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 23:05:39 -0700 (PDT) Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H65F2x031256 for ; Mon, 16 Jun 2003 23:05:18 -0700 Received: from whitestar.arts.usyd.edu.au (whitestar.arts.usyd.edu.au [129.78.16.20]) by plato.arts.usyd.edu.au (8.12.9/8.12.6) with ESMTP id h5H65Erj021867 for ; Tue, 17 Jun 2003 16:05:14 +1000 (EST) Subject: Re: Not strictly an XFS question From: Matthew Geier Cc: XFS List In-Reply-To: <4572.1055815785@kao2.melbourne.sgi.com> References: <4572.1055815785@kao2.melbourne.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 17 Jun 2003 16:05:29 +1000 Message-Id: <1055829929.11774.30.camel@whitestar.arts.usyd.edu.au> Mime-Version: 1.0 X-archive-position: 4355 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: matthew@arts.usyd.edu.au Precedence: bulk X-list: linux-xfs Thanks all, I got kdb to go and saw the fault. (Kernal BUG at ide-iops.c:1262). In testing it appears to NOT happen when X is not running. I've got a geforce video card and am running the Nvidia drivers, so I have a tainted kernel. At this point I think I'm stuck with it, as it works before the kernel is 'tainted' with the Nvidia display driver module... So I know what is dying now, even if I can't fix it :-) From owner-linux-xfs@oss.sgi.com Mon Jun 16 23:58:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Jun 2003 23:58:43 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H6wQ2x000420 for ; Mon, 16 Jun 2003 23:58:27 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h5H7F3mO025824 for ; Tue, 17 Jun 2003 02:15:04 -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 QAA25963; Tue, 17 Jun 2003 16:57:04 +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 h5H6v3tt156337; Tue, 17 Jun 2003 16:57:03 +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 h5H6uipg002934; Tue, 17 Jun 2003 16:56:44 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h5H6uh9t002932; Tue, 17 Jun 2003 16:56:43 +1000 Date: Tue, 17 Jun 2003 16:56:43 +1000 From: Nathan Scott To: Erik Tews Cc: linux-xfs@oss.sgi.com Subject: Re: Bug in xfs_repair Message-ID: <20030617065643.GG794@frodo> References: <20030616205718.GA6783@debian.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030616205718.GA6783@debian.franken.de> User-Agent: Mutt/1.5.3i X-archive-position: 4356 X-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 On Mon, Jun 16, 2003 at 10:57:18PM +0200, Erik Tews wrote: > Hi hi there, > I think I found a bug in xfs_repair. It saegfaults when I run it on a Yep, that looks like a new bug. > filesystem which is a little bit corrupt. After I ran it with efence, I > got these backtraces. I think it cannot handle this block-out-of-range > condition correctly. I have attached all important informations. Hmm.. these are always difficult to diagnose when I haven't got the filesystem right in front of me (so I can sit in gdb and xfs_repair at the same time for interactive debugging). What is almost certainly happening is we are moving past the end of the buffer we've read in (ie. the one pointed to by "ablock" below). This is likely because of either corruption in values in the buffer itself which repair has not catered for, or corruption of some other related control value we're using (many of these will be hanging off the "mp" variable you see in the stack trace. If you can figure out whats causing the pointer to walk past the end of the buffer, you've nailed the problem. Hmmm, what else? From the trace we can see we're walking the by-block freespace btree in the ninth allocation group, and in particular we're up to (ag-relative) block number 338 (you can use the xfs_db "convert" command to get the real disk address - iirc, theres an example on the man page describing how to do that). For a quick fix, you may be able to zero that block using xfs_db/dd, but it'd be even better to figure out the underlying cause of the segv... > (gdb) bt > #0 0x0807918f in scanfunc_bno (ablock=0x405bd000, level=0, bno=338, agno=9, suspect=0, isroot=1) at scan.c:569 > #1 0x0807760a in scan_sbtree (root=338, nlevels=1, agno=9, suspect=0, func=0x8078d05 , isroot=1) at scan.c:84 > #2 0x0807b401 in scan_ag (agno=9) at swab.h:125 > #3 0x0806570f in phase2 (mp=0xbfffdc70) at phase2.c:149 > #4 0x0807c9e9 in main (argc=2, argv=0xbfffdc70) at xfs_repair.c:506 > ... > Phase 2 - using internal log > - zero log... > - scan filesystem freespace and inode maps... cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jun 17 01:27:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 01:28:20 -0700 (PDT) Received: from goliath.sylaba.poznan.pl (root@goliath.sylaba.poznan.pl [195.216.104.3]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5H8Ru2x006534 for ; Tue, 17 Jun 2003 01:27:57 -0700 Received: from goliath.sylaba.poznan.pl (smmsp@localhost.sylaba.poznan.pl [127.0.0.1]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h5H8RsvS028403 for ; Tue, 17 Jun 2003 10:27:54 +0200 (CEST) Received: by goliath.sylaba.poznan.pl (8.12.8/8.12.8/Submit) id h5H8RrPG028391 for linux-xfs@oss.sgi.com.KAV; Tue, 17 Jun 2003 10:27:53 +0200 (CEST) Received: from venus.local.navi.pl (ps103.poznan.sdi.tpnet.pl [217.97.72.103]) by goliath.sylaba.poznan.pl (8.12.8/8.12.8) with ESMTP id h5H8RmvS028334; Tue, 17 Jun 2003 10:27:51 +0200 (CEST) Received: from venus.local.navi.pl (venus.local.navi.pl [127.0.0.1]) by venus.local.navi.pl (8.12.5/8.12.5) with ESMTP id h5H8U53h002114; Tue, 17 Jun 2003 10:30:05 +0200 Subject: Re: 2k/XFS dual-boot disk clone From: Olaf =?iso-8859-2?Q?Fr=B1czyk?= To: Michael Whang Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EEE21E3.20108@boywonderfx.com> References: <3EEE21E3.20108@boywonderfx.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 17 Jun 2003 10:30:05 +0200 Message-Id: <1055838605.1752.8.camel@venus> Mime-Version: 1.0 X-archive-position: 4357 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: olaf@cbk.poznan.pl Precedence: bulk X-list: linux-xfs On Mon, 2003-06-16 at 22:00, Michael Whang wrote: > Has anyone successfully cloned a dual boot windows/XFS disk? What is > the best program to use. I tried using norton ghost but have > encountered the following error: > > Unable to find a free MBR slot in the Virtual Partition DLL. This is > usually due to there being no free primary partition slots left on the > boot disk. > > What can i do resolve this? I assume you have hda: your system drive hdb: disk you want to copy hdc: destination disk size of hdc >= size of hdb You can do: cat /dev/hdb > /dev/hdc It will do a perfect copy, but with stock 2.4.xx kernels your system will be very unresponsive for the copying time. With RH kernels it works almost smoothly. Or you can use dd dd if=/dev/hdb of=/dev/hdc bs=1024 This will do the same and you will be able to use the system for other things during copy :) Regards, Olaf From owner-linux-xfs@oss.sgi.com Tue Jun 17 03:12:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 03:12:16 -0700 (PDT) Received: from maillog.promise.com.tw (maillog.promise.com.tw [210.244.60.166]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HABw2x011640 for ; Tue, 17 Jun 2003 03:11:59 -0700 Received: from ptt.promise.com.tw (IDENT:root@ptt [192.168.202.253]) by maillog.promise.com.tw (8.11.3/8.11.3) with ESMTP id h5HA7IY58997 for ; Tue, 17 Jun 2003 18:07:18 +0800 (CST) (envelope-from scottl@promise.com.tw) Received: from sn1 (IDENT:root@localhost [127.0.0.1]) by ptt.promise.com.tw (8.9.3/8.9.3) with SMTP id SAA26418; Tue, 17 Jun 2003 18:00:12 +0800 Reply-To: From: "Scott Liu" To: Cc: "'Grace Ho'" , "'Jenny'" , "'Myst Lin \(E-mail\)'" , "'Peter'" Subject: How to reconstruct an xfs filesystem and restore all datas? Date: Tue, 17 Jun 2003 18:12:57 +0800 Message-ID: <003501c334b9$06d6cb40$89cca8c0@sn1> MIME-Version: 1.0 Content-Type: text/plain; charset="big5" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id h5HAC02x011642 X-archive-position: 4358 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: scottl@promise.com.tw Precedence: bulk X-list: linux-xfs Dears, I got a BIG problem. A partition created of xfs filesystem and have a lot of datas in. BUT remiss, I done "mkfs.xfs" of this partition and then I LOST all datas. How to reconstruct this xfs filesystem and restore all datas? Thanks a lot and best regards. Scott Liu From owner-linux-xfs@oss.sgi.com Tue Jun 17 04:04:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 04:04:58 -0700 (PDT) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HB4S2x015928 for ; Tue, 17 Jun 2003 04:04:32 -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 h5HB4PMW002420; Tue, 17 Jun 2003 13:04:27 +0200 (CEST) Message-Id: <4.3.2.7.2.20030617130346.036456d8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 17 Jun 2003 13:04:25 +0200 To: , From: Seth Mos Subject: Re: How to reconstruct an xfs filesystem and restore all datas? Cc: "'Grace Ho'" , "'Jenny'" , "'Myst Lin \(E-mail\)'" , "'Peter'" In-Reply-To: <003501c334b9$06d6cb40$89cca8c0@sn1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4359 X-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 At 18:12 17-6-2003 +0800, Scott Liu wrote: >Dears, >I got a BIG problem. >A partition created of xfs filesystem and have a lot of datas in. >BUT remiss, I done "mkfs.xfs" of this partition and then I LOST all datas. >How to reconstruct this xfs filesystem and restore all datas? Tape? Backups? There is no way to reconstruct a reformatted filesystem. Sorry -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Tue Jun 17 04:12:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 04:12:45 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HBCN2x016558 for ; Tue, 17 Jun 2003 04:12:28 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 58B8A14DD2; Tue, 17 Jun 2003 13:12:18 +0200 (MEST) Date: Tue, 17 Jun 2003 13:12:17 +0200 From: Andi Kleen To: Seth Mos Cc: scottl@promise.com.tw, linux-xfs@oss.sgi.com, "'Grace Ho'" , "'Jenny'" , "'Myst Lin (E-mail)'" , "'Peter'" Subject: Re: How to reconstruct an xfs filesystem and restore all datas? Message-ID: <20030617111217.GB25912@wotan.suse.de> References: <003501c334b9$06d6cb40$89cca8c0@sn1> <4.3.2.7.2.20030617130346.036456d8@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.3.2.7.2.20030617130346.036456d8@pop.xs4all.nl> X-archive-position: 4360 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs On Tue, Jun 17, 2003 at 01:04:25PM +0200, Seth Mos wrote: > At 18:12 17-6-2003 +0800, Scott Liu wrote: > >Dears, > >I got a BIG problem. > >A partition created of xfs filesystem and have a lot of datas in. > >BUT remiss, I done "mkfs.xfs" of this partition and then I LOST all datas. > >How to reconstruct this xfs filesystem and restore all datas? > > Tape? Backups? > > There is no way to reconstruct a reformatted filesystem. The raw data is probably still mostly there, just all the directories and inodes are likely gone. Luckily XFS is quite good at laying out data sequentially. So with some luck it is possible to extract the data from the raw image e.g. when it's source code you can just use strings on the block device for good results. If it is other data you may need to write some program that looks for the signatures and tries to recover. -Andi From owner-linux-xfs@oss.sgi.com Tue Jun 17 04:21:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 04:21:37 -0700 (PDT) Received: from maillog.promise.com.tw (maillog.promise.com.tw [210.244.60.166]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HBLK2x017165 for ; Tue, 17 Jun 2003 04:21:21 -0700 Received: from ptt.promise.com.tw (IDENT:root@ptt [192.168.202.253]) by maillog.promise.com.tw (8.11.3/8.11.3) with ESMTP id h5HBGeY64431; Tue, 17 Jun 2003 19:16:41 +0800 (CST) (envelope-from scottl@promise.com.tw) Received: from sn1 (IDENT:root@localhost [127.0.0.1]) by ptt.promise.com.tw (8.9.3/8.9.3) with SMTP id TAA29488; Tue, 17 Jun 2003 19:09:35 +0800 Reply-To: From: "Scott Liu" To: "'Seth Mos'" , Cc: "'Grace Ho'" , "'Jenny'" , "'Myst Lin \(E-mail\)'" , "'Peter'" Subject: RE: How to reconstruct an xfs filesystem and restore all datas? Date: Tue, 17 Jun 2003 19:22:22 +0800 Message-ID: <003601c334c2$b9d1cca0$89cca8c0@sn1> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal In-Reply-To: <4.3.2.7.2.20030617130346.036456d8@pop.xs4all.nl> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id h5HBLL2x017166 X-archive-position: 4361 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: scottl@promise.com.tw Precedence: bulk X-list: linux-xfs Dears, Sorry, that's on a hard disk. Best Regards, Scott Liu -----Original Message----- From: Seth Mos [mailto:knuffie@xs4all.nl] Sent: Tuesday, June 17, 2003 7:04 PM To: scottl@promise.com.tw; linux-xfs@oss.sgi.com Cc: 'Grace Ho'; 'Jenny'; 'Myst Lin (E-mail)'; 'Peter' Subject: Re: How to reconstruct an xfs filesystem and restore all datas? At 18:12 17-6-2003 +0800, Scott Liu wrote: >Dears, >I got a BIG problem. >A partition created of xfs filesystem and have a lot of datas in. >BUT remiss, I done "mkfs.xfs" of this partition and then I LOST all datas. >How to reconstruct this xfs filesystem and restore all datas? Tape? Backups? There is no way to reconstruct a reformatted filesystem. Sorry -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Tue Jun 17 05:29:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 05:29:27 -0700 (PDT) Received: from karnickel.franken.de (karnickel.4msp.de [217.6.190.222]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HCT22x018765 for ; Tue, 17 Jun 2003 05:29:04 -0700 Received: from karnickel.franken.de (localhost [127.0.0.1]) by karnickel.franken.de (8.12.9/8.12.9) with ESMTP id h5HCT1JR076688; Tue, 17 Jun 2003 14:29:01 +0200 (CEST) Received: (from uucp@localhost) by karnickel.franken.de (8.12.9/8.12.2/Submit) with UUCP id h5HCT07e076675; Tue, 17 Jun 2003 14:29:00 +0200 (CEST) (envelope-from erik@debian.franken.de) Received: by tpl.lokalnetz (Postfix, from userid 1000) id E1FF18FD7C1; Tue, 17 Jun 2003 14:26:02 +0200 (CEST) Date: Tue, 17 Jun 2003 14:26:02 +0200 To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: Bug in xfs_repair Message-ID: <20030617122602.GC2285@debian.franken.de> References: <20030616205718.GA6783@debian.franken.de> <20030617065643.GG794@frodo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030617065643.GG794@frodo> User-Agent: Mutt/1.5.4i From: erik@debian.franken.de (Erik Tews) X-archive-position: 4362 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erik@debian.franken.de Precedence: bulk X-list: linux-xfs On Tue, Jun 17, 2003 at 04:56:43PM +1000, Nathan Scott wrote: > On Mon, Jun 16, 2003 at 10:57:18PM +0200, Erik Tews wrote: > > Hi > > hi there, > > > I think I found a bug in xfs_repair. It saegfaults when I run it on a > > Yep, that looks like a new bug. > > > filesystem which is a little bit corrupt. After I ran it with efence, I > > got these backtraces. I think it cannot handle this block-out-of-range > > condition correctly. I have attached all important informations. > > Hmm.. these are always difficult to diagnose when I haven't got the > filesystem right in front of me (so I can sit in gdb and xfs_repair > at the same time for interactive debugging). I got gdb here, so if you tell me what infos you need, I cann see if I can get them. > What is almost certainly happening is we are moving past the end of > the buffer we've read in (ie. the one pointed to by "ablock" below). > This is likely because of either corruption in values in the buffer > itself which repair has not catered for, or corruption of some other > related control value we're using (many of these will be hanging off > the "mp" variable you see in the stack trace. > > If you can figure out whats causing the pointer to walk past the end > of the buffer, you've nailed the problem. I think is is wrong metadata. I resized the filesystem without any errors but this could be the reason for that. > Hmmm, what else? From the trace we can see we're walking the by-block > freespace btree in the ninth allocation group, and in particular we're > up to (ag-relative) block number 338 (you can use the xfs_db "convert" > command to get the real disk address - iirc, theres an example on the > man page describing how to do that). For a quick fix, you may be able > to zero that block using xfs_db/dd, but it'd be even better to figure > out the underlying cause of the segv... I got a full backup of the filesystem, so there is no need to fix the filesystem, but it could be intresting for you to fix xfs_repair to make it not saegfault on similar filesystems. The b-variable it at 65536, so it is the following line from xfs_check where xfs_repair has his problems: block 9/65536 out of range Could we perhaps add a safety-check for get_agbno_state to make it no touch such blocks with these errors? > > (gdb) bt > > #0 0x0807918f in scanfunc_bno (ablock=0x405bd000, level=0, bno=338, agno=9, suspect=0, isroot=1) at scan.c:569 > > #1 0x0807760a in scan_sbtree (root=338, nlevels=1, agno=9, suspect=0, func=0x8078d05 , isroot=1) at scan.c:84 > > #2 0x0807b401 in scan_ag (agno=9) at swab.h:125 > > #3 0x0806570f in phase2 (mp=0xbfffdc70) at phase2.c:149 > > #4 0x0807c9e9 in main (argc=2, argv=0xbfffdc70) at xfs_repair.c:506 > > ... > > Phase 2 - using internal log > > - zero log... > > - scan filesystem freespace and inode maps... > > > cheers. > > -- > Nathan From owner-linux-xfs@oss.sgi.com Tue Jun 17 05:47:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 05:48:10 -0700 (PDT) Received: from f00f.org (adsl-63-203-70-212.dsl.snfc21.pacbell.net [63.203.70.212]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HClt2x021388 for ; Tue, 17 Jun 2003 05:47:55 -0700 Received: by f00f.org (Postfix, from userid 10000) id 1AA9314872B7; Tue, 17 Jun 2003 05:48:19 -0700 (PDT) Date: Tue, 17 Jun 2003 05:48:19 -0700 From: Chris Wedgwood To: Matthew Geier Cc: XFS List Subject: Re: Not strictly an XFS question Message-ID: <20030617124819.GA1810@f00f.org> References: <4572.1055815785@kao2.melbourne.sgi.com> <1055829929.11774.30.camel@whitestar.arts.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055829929.11774.30.camel@whitestar.arts.usyd.edu.au> X-archive-position: 4363 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Tue, Jun 17, 2003 at 04:05:29PM +1000, Matthew Geier wrote: > I've got a geforce video card and am running the Nvidia drivers, so > I have a tainted kernel. At this point I think I'm stuck with it, as > it works before the kernel is 'tainted' with the Nvidia display > driver module... The earlier nv drivers did nasty things but it seems to be mostly gone now. If you do have a problem as a result of the nv drivers (and they are recent) then please report it to nvidia. > So I know what is dying now, even if I can't fix it :-) Maybe I missed something here, but what kernel gives you this problem? I doubt it's related the the nv drivers at all and may have been fixed in a more recent kernel. --cw From owner-linux-xfs@oss.sgi.com Tue Jun 17 06:00:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 06:00:43 -0700 (PDT) Received: from dingdong.cryptoapps.com (postfix@uslink-66.173.43-133.uslink.net [66.173.43.133] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HD0L2x021973 for ; Tue, 17 Jun 2003 06:00:22 -0700 Received: by dingdong.cryptoapps.com (Postfix, from userid 1001) id E401DFB838; Tue, 17 Jun 2003 08:04:38 -0500 (CDT) Date: Tue, 17 Jun 2003 08:04:38 -0500 From: Chris Wedgwood To: Scott Liu Cc: linux-xfs@oss.sgi.com, "'Grace Ho'" , "'Jenny'" , "'Myst Lin (E-mail)'" , "'Peter'" Subject: Re: How to reconstruct an xfs filesystem and restore all datas? Message-ID: <20030617130438.GB3510@dingdong.cryptoapps.com> References: <003501c334b9$06d6cb40$89cca8c0@sn1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003501c334b9$06d6cb40$89cca8c0@sn1> X-archive-position: 4364 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Tue, Jun 17, 2003 at 06:12:57PM +0800, Scott Liu wrote: > A partition created of xfs filesystem and have a lot of datas in. > BUT remiss, I done "mkfs.xfs" of this partition and then I LOST all > datas. How to reconstruct this xfs filesystem and restore all > datas? mkfs.fs will have obliterated most if not all useful metadata making recovery painful at best. It depends what kind of data you have there and how fragmented it was --- but you might have a chance of recovery for some of it if you can use a heuristic to detect the data your after and hope that it's mostly contiguous. I've done this several times for people who've trashed disks for of images mostly because asynchronous writes ensure most files are not-fragmented and most images (jpegs) are easy to scan-for and recover. --cw From owner-linux-xfs@oss.sgi.com Tue Jun 17 06:05:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 06:06:18 -0700 (PDT) Received: from dingdong.cryptoapps.com (postfix@uslink-66.173.43-133.uslink.net [66.173.43.133] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HD5m2x022793 for ; Tue, 17 Jun 2003 06:05:48 -0700 Received: by dingdong.cryptoapps.com (Postfix, from userid 1001) id 095E5FB838; Tue, 17 Jun 2003 08:10:06 -0500 (CDT) Date: Tue, 17 Jun 2003 08:10:06 -0500 From: Chris Wedgwood To: Steve Lord Cc: Andi Kleen , linux-xfs@oss.sgi.com, Chris Mason Subject: Re: [PATCH] Give logbufs a better default Message-ID: <20030617131006.GC3510@dingdong.cryptoapps.com> References: <20030611093525.GA2329@wotan.suse.de> <1055363594.6614.44.camel@jen.americas.sgi.com> <20030611212822.GA8166@wotan.suse.de> <1055369055.6611.95.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1055369055.6611.95.camel@jen.americas.sgi.com> X-archive-position: 4365 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Wed, Jun 11, 2003 at 05:04:15PM -0500, Steve Lord wrote: > > 8 is the current maximum (is there a reason for that btw? could it > > be simply raised?) > > It could be. I have a filesystem with an external log where I've increase logbufs to 8 and also the size to 256k. With this I see *much* better performance for somethings like cp -Rl and rm, but not reliably... there are times when the performance is worse. It's not clear how to choose sensible values other than by trial and error. --cw From owner-linux-xfs@oss.sgi.com Tue Jun 17 06:07:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 06:07:13 -0700 (PDT) Received: from zcars04e.nortelnetworks.com (zcars04e.nortelnetworks.com [47.129.242.56]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HD742x023350 for ; Tue, 17 Jun 2003 06:07:05 -0700 Received: from zcard307.ca.nortel.com (zcard307.ca.nortel.com [47.129.242.67]) by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h5HD6hs07780; Tue, 17 Jun 2003 09:06:43 -0400 (EDT) Received: from zcard04u.ca.nortel.com ([47.129.242.92]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id M7BYHT0H; Tue, 17 Jun 2003 09:06:44 -0400 Received: from pcary03q.ca.nortel.com ([47.129.117.125]) by zcard04u.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 2WPY8RTZ; Tue, 17 Jun 2003 09:06:43 -0400 Subject: Re: Not strictly an XFS question X-Sybari-Space: 00000000 00000000 00000000 00000000 From: "Sean Kormilo" To: Chris Wedgwood Cc: Matthew Geier , XFS List In-Reply-To: <20030617124819.GA1810@f00f.org> References: <4572.1055815785@kao2.melbourne.sgi.com> <1055829929.11774.30.camel@whitestar.arts.usyd.edu.au> <20030617124819.GA1810@f00f.org> Content-Type: text/plain Organization: Message-Id: <1055855202.19073.64.camel@pcary03q.ca.nortel.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.3 Date: 17 Jun 2003 09:06:42 -0400 Content-Transfer-Encoding: 7bit X-archive-position: 4366 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: skormilo@nortelnetworks.com Precedence: bulk X-list: linux-xfs I had the same basic trouble getting Mandrake Linux 9.1 to install on my NForce2 based system (with NVidia graphics card) and 1GB RAM. The following is the solution listed by Mandrake: Error scenario: Booting the installer, a machine with a lot of memory (1GB or more) hangs with flashing caps/scroll lock LEDs (Bugzilla #3198). Why: It seems as though there is framebuffer trouble with certain video cards on machines with a high amount of memory. Solution: At the installer splash screen when you first boot off the CD or floppy disks, press F1 and type "linux vga=0". You might try something similar with RedHat. Sean. > On Tue, Jun 17, 2003 at 04:05:29PM +1000, Matthew Geier wrote: > > > I've got a geforce video card and am running the Nvidia drivers, so > > I have a tainted kernel. At this point I think I'm stuck with it, as > > it works before the kernel is 'tainted' with the Nvidia display > > driver module... > > The earlier nv drivers did nasty things but it seems to be mostly gone > now. If you do have a problem as a result of the nv drivers (and they > are recent) then please report it to nvidia. > > > So I know what is dying now, even if I can't fix it :-) > > Maybe I missed something here, but what kernel gives you this problem? > I doubt it's related the the nv drivers at all and may have been fixed > in a more recent kernel. > > > --cw -- Sean C. Kormilo, STORM Software Architect, Nortel Networks email: skormilo@nortelnetworks.com From owner-linux-xfs@oss.sgi.com Tue Jun 17 06:25:17 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 06:25:34 -0700 (PDT) Received: from batleth.sapienti-sat.org (batleth.sapienti-sat.org [80.190.100.240]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HDPF2x024917 for ; Tue, 17 Jun 2003 06:25:16 -0700 Received: from localhost (localhost.sapienti-sat.org [127.0.0.1]) by batleth.sapienti-sat.org (Postfix) with SMTP id 4E8E7102535 for ; Tue, 17 Jun 2003 15:25:14 +0200 (CEST) Received: from warp9.sapienti-sat.org (pD9E7F7BA.dip.t-dialin.net [217.231.247.186]) by batleth.sapienti-sat.org (Postfix) with ESMTP id 06BA610011F for ; Tue, 17 Jun 2003 15:25:14 +0200 (CEST) Received: from localhost (localhost.sapienti-sat.org [127.0.0.1]) by warp9.sapienti-sat.org (Postfix) with SMTP id 650DDBF for ; Tue, 17 Jun 2003 15:25:10 +0200 (CEST) Received: from koschikode.com (pktomo.sapienti-sat.org [192.168.200.10]) by warp9.sapienti-sat.org (Postfix) with ESMTP id A7AD2B9 for ; Tue, 17 Jun 2003 15:25:09 +0200 (CEST) Message-ID: <3EEF16B5.7090805@koschikode.com> Date: Tue, 17 Jun 2003 15:25:09 +0200 From: Juri Haberland User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 X-Accept-Language: de-de, en-us, en MIME-Version: 1.0 To: XFS List Subject: Re: Not strictly an XFS question References: <4572.1055815785@kao2.melbourne.sgi.com> <1055829929.11774.30.camel@whitestar.arts.usyd.edu.au> In-Reply-To: <1055829929.11774.30.camel@whitestar.arts.usyd.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4367 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: juri@koschikode.com Precedence: bulk X-list: linux-xfs Matthew Geier wrote: > Thanks all, I got kdb to go and saw the fault. (Kernal BUG at > ide-iops.c:1262). > In testing it appears to NOT happen when X is not running. > > I've got a geforce video card and am running the Nvidia drivers, so I > have a tainted kernel. At this point I think I'm stuck with it, as it > works before the kernel is 'tainted' with the Nvidia display driver > module... > > So I know what is dying now, even if I can't fix it :-) You're not alone. I read a couple of similiar reports on linux-kernel. So it is in no way XFS related; it seems to happen also with stock 2.4.21. Cheers, Juri From owner-linux-xfs@oss.sgi.com Tue Jun 17 07:26:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 07:27:06 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HEQR2x026190 for ; Tue, 17 Jun 2003 07:26:27 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5HEgrmO008657 for ; Tue, 17 Jun 2003 09:42:53 -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 h5HEQ7qX4986224 for ; Tue, 17 Jun 2003 09:26:07 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5HEQ7Rn112849697 for ; Tue, 17 Jun 2003 09:26:07 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5HEQ7A20216; Tue, 17 Jun 2003 09:26:07 -0500 Message-Id: <200306171426.h5HEQ7A20216@jen.americas.sgi.com> Date: Tue, 17 Jun 2003 09:26:07 -0500 Subject: TAKE - merge up to 2.5.70 To: linux-xfs@oss.sgi.com X-archive-position: 4368 X-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 2.5.71 will follow shortly Date: Mon Jun 2 12:14:24 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:150160a linux/drivers/scsi/arm/queue.h - 1.1 linux/include/linux/usb_gadget.h - 1.1 linux/drivers/net/arm/Kconfig - 1.1 linux/drivers/char/drm/gamma_context.h - 1.1 linux/drivers/char/agp/uninorth-agp.c - 1.1 linux/arch/m68knommu/platform/5282/MOTOROLA/crt0_ram.S - 1.1 linux/arch/m68knommu/platform/5282/Makefile - 1.1 linux/arch/m68knommu/platform/5282/config.c - 1.1 linux/arch/m68knommu/platform/5282/pit.c - 1.1 linux/include/asm-i386/mach-bigsmp/mach_apicdef.h - 1.1 linux/include/asm-i386/genapic.h - 1.1 linux/include/asm-i386/mach-default/mach_apicdef.h - 1.1 linux/include/asm-i386/mach-generic/mach_apic.h - 1.1 linux/include/asm-i386/mach-generic/mach_ipi.h - 1.1 linux/net/sctp/chunk.c - 1.1 linux/drivers/net/arm/Makefile - 1.1 linux/drivers/net/arm/am79c961a.c - 1.1 linux/Documentation/iostats.txt - 1.1 linux/include/net/ipcomp.h - 1.1 linux/include/linux/pci-dynids.h - 1.1 linux/include/asm-i386/mach-generic/mach_mpparse.h - 1.1 linux/include/asm-arm/traps.h - 1.1 linux/include/acpi/amlresrc.h - 1.1 linux/drivers/net/arm/am79c961a.h - 1.1 linux/drivers/net/arm/ether00.c - 1.1 linux/include/acpi/acdisasm.h - 1.1 linux/arch/x86_64/ia32/vsyscall.S - 1.1 linux/drivers/net/arm/ether1.c - 1.1 linux/arch/x86_64/ia32/vsyscall.lds - 1.1 linux/include/asm-i386/mach-numaq/mach_apicdef.h - 1.1 linux/include/asm-i386/mach-summit/mach_apicdef.h - 1.1 linux/arch/ppc/boot/openfirmware/dummy.c - 1.1 linux/drivers/net/arm/ether1.h - 1.1 linux/drivers/net/arm/ether3.c - 1.1 linux/arch/x86_64/kernel/vsyscall.S - 1.1 linux/arch/ppc/boot/prep/dummy.c - 1.1 linux/drivers/net/arm/ether3.h - 1.1 linux/drivers/net/arm/etherh.c - 1.1 linux/arch/x86_64/kernel/warmreboot.S - 1.1 linux/drivers/net/bonding/Makefile - 1.1 linux/drivers/net/bonding/bond_3ad.c - 1.1 linux/drivers/net/bonding/bond_3ad.h - 1.1 linux/drivers/net/bonding/bond_alb.c - 1.1 linux/arch/ppc/boot/simple/dummy.c - 1.1 linux/drivers/net/bonding/bond_alb.h - 1.1 linux/dev/null - 1.1 linux/fs/ext3/xattr_security.c - 1.1 linux/fs/ext2/xattr_security.c - 1.1 linux/drivers/net/bonding/bond_main.c - 1.1 linux/drivers/net/bonding/bonding.h - 1.1 linux/drivers/net/irda/smsc-ircc2.c - 1.1 linux/fs/devpts/xattr_security.c - 1.1 linux/fs/devpts/xattr.h - 1.1 linux/drivers/net/irda/smsc-ircc2.h - 1.1 linux/drivers/net/irda/smsc-sio.h - 1.1 linux/drivers/net/sungem_phy.c - 1.1 linux/drivers/net/sungem_phy.h - 1.1 linux/fs/devpts/xattr.c - 1.1 linux/drivers/usb/gadget/zero.c - 1.1 linux/drivers/usb/gadget/usbstring.c - 1.1 linux/drivers/usb/gadget/net2280.h - 1.1 linux/drivers/usb/gadget/net2280.c - 1.1 linux/drivers/usb/gadget/ether.c - 1.1 linux/drivers/usb/gadget/Makefile - 1.1 linux/net/ipx/ipx_route.c - 1.1 linux/drivers/usb/gadget/Kconfig - 1.1 linux/drivers/atm/he.c - 1.1 linux/drivers/atm/he.h - 1.1 linux/drivers/i2c/busses/i2c-sis96x.c - 1.1 linux/drivers/scsi/arm/Kconfig - 1.1 linux/drivers/scsi/arm/Makefile - 1.1 linux/drivers/scsi/scsi_priv.h - 1.1 linux/drivers/scsi/scsi_logging.h - 1.1 linux/drivers/scsi/arm/acornscsi-io.S - 1.1 linux/drivers/base/map.c - 1.1 linux/drivers/scsi/scsi_devinfo.h - 1.1 linux/drivers/scsi/scsi_devinfo.c - 1.1 linux/drivers/char/agp/isoch.c - 1.1 linux/drivers/char/agp/nvidia-agp.c - 1.1 linux/include/asm-i386/mach-visws/mach_apicdef.h - 1.1 linux/drivers/scsi/arm/acornscsi.c - 1.1 linux/drivers/scsi/arm/acornscsi.h - 1.1 linux/drivers/scsi/arm/arxescsi.c - 1.1 linux/include/linux/kobj_map.h - 1.1 linux/drivers/scsi/arm/cumana_1.c - 1.1 linux/drivers/scsi/arm/cumana_2.c - 1.1 linux/drivers/scsi/arm/ecoscsi.c - 1.1 linux/drivers/scsi/arm/eesox.c - 1.1 linux/net/ipv6/ipcomp6.c - 1.1 linux/include/linux/cdev.h - 1.1 linux/include/linux/atmbr2684.h - 1.1 linux/drivers/scsi/arm/fas216.c - 1.1 linux/drivers/scsi/arm/fas216.h - 1.1 linux/include/linux/atm_he.h - 1.1 linux/drivers/scsi/arm/msgqueue.c - 1.1 linux/drivers/scsi/arm/msgqueue.h - 1.1 linux/drivers/scsi/arm/oak.c - 1.1 linux/include/asm-x86_64/vsyscall32.h - 1.1 linux/arch/ppc64/kernel/proc_ppc64.c - 1.1 linux/include/asm-ppc64/systemcfg.h - 1.1 linux/include/asm-ppc/agp.h - 1.1 linux/drivers/scsi/arm/powertec.c - 1.1 linux/include/asm-m68knommu/mcfpit.h - 1.1 linux/include/asm-m68knommu/m5282sim.h - 1.1 linux/net/atm/br2684.c - 1.1 linux/drivers/scsi/arm/queue.c - 1.1 linux/drivers/scsi/arm/scsi.h - 1.1 linux/drivers/char/drm/gamma_old_dma.h - 1.1 linux/drivers/char/drm/gamma_lock.h - 1.1 linux/net/core/flow.c - 1.1 linux/arch/i386/mach-generic/bigsmp.c - 1.1 linux/arch/i386/mach-generic/default.c - 1.1 linux/arch/i386/mach-generic/probe.c - 1.1 linux/arch/i386/mach-generic/summit.c - 1.1 linux/net/core/net-sysfs.c - 1.1 linux/drivers/char/drm/gamma_lists.h - 1.1 linux/net/decnet/netfilter/Kconfig - 1.1 linux/net/decnet/netfilter/Makefile - 1.1 linux/net/decnet/netfilter/dn_rtmsg.c - 1.1 linux/net/ipv4/netfilter/ip_fw_compat.h - 1.1 linux/scripts/ver_linux - 1.13 linux/net/wanrouter/wanproc.c - 1.25 linux/net/wanrouter/wanmain.c - 1.18 linux/net/unix/af_unix.c - 1.57 linux/net/sunrpc/xprt.c - 1.43 linux/net/sunrpc/xdr.c - 1.13 linux/net/sunrpc/svcsock.c - 1.31 linux/net/sunrpc/sunrpc_syms.c - 1.22 linux/net/sunrpc/sched.c - 1.40 linux/net/sunrpc/pmap_clnt.c - 1.11 linux/net/sunrpc/clnt.c - 1.31 linux/net/socket.c - 1.57 linux/net/sched/sch_sfq.c - 1.12 linux/net/sched/sch_csz.c - 1.11 linux/net/sched/sch_api.c - 1.17 linux/net/sched/cls_api.c - 1.9 linux/net/packet/af_packet.c - 1.42 linux/net/netsyms.c - 1.68 linux/net/netrom/nr_route.c - 1.9 linux/net/netrom/nr_loopback.c - 1.9 linux/net/netlink/netlink_dev.c - 1.21 linux/net/netlink/af_netlink.c - 1.29 linux/net/irda/irttp.c - 1.23 linux/net/irda/irqueue.c - 1.13 linux/net/irda/irproc.c - 1.13 linux/net/irda/irlmp_frame.c - 1.15 linux/net/irda/irlmp_event.c - 1.23 linux/net/irda/irlmp.c - 1.27 linux/net/irda/irlap_frame.c - 1.20 linux/net/irda/irlap_event.c - 1.30 linux/net/irda/irlap.c - 1.23 linux/net/irda/irlan/irlan_provider.c - 1.8 linux/net/irda/irlan/irlan_eth.c - 1.18 linux/net/irda/irlan/irlan_common.c - 1.23 linux/net/irda/irlan/irlan_client.c - 1.15 linux/net/irda/iriap_event.c - 1.11 linux/net/irda/iriap.c - 1.23 linux/net/irda/irda_device.c - 1.32 linux/net/irda/af_irda.c - 1.47 linux/net/ipx/af_ipx.c - 1.37 linux/net/ipx/Makefile - 1.12 linux/net/ipv6/udp.c - 1.41 linux/net/ipv6/tcp_ipv6.c - 1.52 linux/net/ipv6/sit.c - 1.31 linux/net/ipv6/route.c - 1.34 linux/net/ipv6/reassembly.c - 1.18 linux/net/ipv6/raw.c - 1.34 linux/net/ipv6/protocol.c - 1.9 linux/net/ipv6/proc.c - 1.16 linux/net/ipv6/ndisc.c - 1.34 linux/net/ipv6/mcast.c - 1.26 linux/net/ipv6/ip6_output.c - 1.23 linux/net/ipv6/ip6_input.c - 1.18 linux/net/ipv6/ip6_fib.c - 1.18 linux/net/ipv6/icmp.c - 1.29 linux/net/ipv6/exthdrs.c - 1.12 linux/net/ipv6/datagram.c - 1.14 linux/net/ipv6/af_inet6.c - 1.35 linux/net/ipv6/addrconf.c - 1.37 linux/net/ipv6/Makefile - 1.15 linux/net/ipv4/udp.c - 1.43 linux/net/ipv4/tcp_ipv4.c - 1.62 linux/net/ipv4/tcp.c - 1.56 linux/net/ipv4/sysctl_net_ipv4.c - 1.19 linux/net/ipv4/syncookies.c - 1.19 linux/net/ipv4/route.c - 1.49 linux/net/ipv4/raw.c - 1.33 linux/net/ipv4/protocol.c - 1.10 linux/net/ipv4/proc.c - 1.19 linux/net/ipv4/ipconfig.c - 1.38 linux/net/ipv4/ip_sockglue.c - 1.26 linux/net/ipv4/ip_output.c - 1.47 linux/net/ipv4/ip_input.c - 1.23 linux/net/ipv4/ip_gre.c - 1.31 linux/net/ipv4/icmp.c - 1.39 linux/net/ipv4/fib_semantics.c - 1.14 linux/net/ipv4/fib_hash.c - 1.13 linux/net/ipv4/fib_frontend.c - 1.16 linux/net/ipv4/devinet.c - 1.22 linux/net/ipv4/arp.c - 1.30 linux/net/ipv4/af_inet.c - 1.54 linux/net/core/sock.c - 1.35 linux/net/core/skbuff.c - 1.35 linux/net/core/rtnetlink.c - 1.17 linux/net/core/neighbour.c - 1.21 linux/net/core/dst.c - 1.16 linux/net/core/dev.c - 1.74 linux/net/core/Makefile - 1.16 linux/net/ax25/af_ax25.c - 1.32 linux/net/appletalk/ddp.c - 1.28 linux/mm/vmscan.c - 1.128 linux/mm/vmalloc.c - 1.49 linux/mm/swapfile.c - 1.74 linux/mm/slab.c - 1.57 linux/mm/page_alloc.c - 1.109 linux/mm/mmap.c - 1.77 linux/mm/memory.c - 1.106 linux/mm/filemap.c - 1.156 linux/lib/string.c - 1.16 linux/lib/inflate.c - 1.6 linux/lib/Makefile - 1.21 linux/kernel/sysctl.c - 1.66 linux/kernel/sys.c - 1.52 linux/kernel/signal.c - 1.55 linux/kernel/sched.c - 1.101 linux/kernel/panic.c - 1.22 linux/kernel/module.c - 1.43 linux/kernel/ksyms.c - 1.190 linux/kernel/kmod.c - 1.31 linux/kernel/fork.c - 1.90 linux/kernel/exit.c - 1.68 linux/kernel/exec_domain.c - 1.22 linux/kernel/acct.c - 1.26 linux/kernel/Makefile - 1.44 linux/ipc/shm.c - 1.64 linux/ipc/sem.c - 1.26 linux/ipc/msg.c - 1.20 linux/init/main.c - 1.107 linux/include/scsi/scsi.h - 1.11 linux/include/net/udp.h - 1.14 linux/include/net/transp_v6.h - 1.4 linux/include/net/tcp.h - 1.46 linux/include/net/sock.h - 1.47 linux/include/net/protocol.h - 1.13 linux/include/net/neighbour.h - 1.9 linux/include/net/irda/irport.h - 1.12 linux/include/net/irda/irlmp_event.h - 1.6 linux/include/net/irda/irlan_common.h - 1.9 linux/include/net/irda/iriap.h - 1.10 linux/include/net/ipx.h - 1.11 linux/include/net/ipv6.h - 1.16 linux/include/net/ip_fib.h - 1.10 linux/include/net/ip6_route.h - 1.12 linux/include/net/ip6_fib.h - 1.7 linux/include/net/ip.h - 1.26 linux/include/net/if_inet6.h - 1.12 linux/include/net/flow.h - 1.5 linux/include/net/ax25.h - 1.10 linux/include/linux/wireless.h - 1.12 linux/include/linux/wanrouter.h - 1.12 linux/include/linux/wanpipe.h - 1.11 linux/include/linux/wait.h - 1.19 linux/include/linux/tty_driver.h - 1.9 linux/include/linux/tty.h - 1.23 linux/include/linux/tpqic02.h - 1.6 linux/include/linux/time.h - 1.15 linux/include/linux/sysrq.h - 1.8 linux/include/linux/sysctl.h - 1.73 linux/include/linux/swap.h - 1.76 linux/include/linux/sunrpc/xprt.h - 1.19 linux/include/linux/sunrpc/xdr.h - 1.13 linux/include/linux/sunrpc/svc.h - 1.15 linux/include/linux/string.h - 1.12 linux/include/linux/socket.h - 1.15 linux/include/linux/smp_lock.h - 1.8 linux/include/linux/smp.h - 1.27 linux/include/linux/slab.h - 1.31 linux/include/linux/skbuff.h - 1.34 linux/include/linux/signal.h - 1.14 linux/include/linux/shm.h - 1.16 linux/include/linux/sem.h - 1.11 linux/include/linux/sched.h - 1.104 linux/include/linux/rtnetlink.h - 1.17 linux/include/linux/ptrace.h - 1.8 linux/include/linux/proc_fs.h - 1.39 linux/include/linux/ppp_defs.h - 1.4 linux/include/linux/pci.h - 1.75 linux/include/linux/pagemap.h - 1.55 linux/include/linux/nfsd/nfsd.h - 1.21 linux/include/linux/nfsd/export.h - 1.18 linux/include/linux/nfs_fs_sb.h - 1.12 linux/include/linux/nfs.h - 1.9 linux/include/linux/netlink.h - 1.13 linux/include/linux/netdevice.h - 1.45 linux/include/linux/net.h - 1.18 linux/include/linux/msg.h - 1.11 linux/include/linux/msdos_fs.h - 1.27 linux/include/linux/mount.h - 1.20 linux/include/linux/module.h - 1.50 linux/include/linux/mm.h - 1.119 linux/include/linux/major.h - 1.32 linux/include/linux/list.h - 1.28 linux/include/linux/kmod.h - 1.12 linux/include/linux/kernel.h - 1.46 linux/include/linux/ipx.h - 1.4 linux/include/linux/ipv6_route.h - 1.3 linux/include/linux/ipv6.h - 1.8 linux/include/linux/ip.h - 1.11 linux/include/linux/interrupt.h - 1.29 linux/include/linux/if_frad.h - 1.6 linux/include/linux/if_ether.h - 1.12 linux/include/linux/if_arcnet.h - 1.4 linux/include/linux/i2c.h - 1.25 linux/include/linux/genhd.h - 1.37 linux/include/linux/fs.h - 1.214 linux/include/linux/file.h - 1.19 linux/include/linux/elf.h - 1.27 linux/include/linux/console.h - 1.12 linux/include/linux/capability.h - 1.14 linux/include/linux/blkdev.h - 1.84 linux/include/linux/arcdevice.h - 1.10 linux/include/asm-sparc64/hardirq.h - 1.20 linux/include/asm-sparc64/elf.h - 1.18 linux/include/asm-sparc/smp.h - 1.13 linux/include/asm-sparc/io-unit.h - 1.5 linux/include/asm-sparc/hardirq.h - 1.17 linux/include/asm-sparc/elf.h - 1.8 linux/include/asm-sparc/bitops.h - 1.19 linux/include/asm-ppc/spinlock.h - 1.19 linux/include/asm-ppc/pgtable.h - 1.43 linux/include/asm-ppc/linux_logo.h - 1.10 linux/include/asm-ppc/hardirq.h - 1.24 linux/include/asm-ppc/elf.h - 1.14 linux/include/asm-mips/elf.h - 1.12 linux/include/asm-m68k/pgtable.h - 1.18 linux/include/asm-m68k/macintosh.h - 1.8 linux/include/asm-m68k/machdep.h - 1.10 linux/include/asm-m68k/irq.h - 1.8 linux/include/asm-m68k/io.h - 1.12 linux/include/asm-m68k/ide.h - 1.11 linux/include/asm-m68k/hardirq.h - 1.10 linux/include/asm-m68k/elf.h - 1.8 linux/include/asm-m68k/atari_stdma.h - 1.3 linux/include/asm-i386/unistd.h - 1.36 linux/include/asm-i386/uaccess.h - 1.24 linux/include/asm-i386/types.h - 1.7 linux/include/asm-i386/system.h - 1.36 linux/include/asm-i386/spinlock.h - 1.29 linux/include/asm-i386/smp.h - 1.28 linux/include/asm-i386/processor.h - 1.54 linux/include/asm-i386/mmu_context.h - 1.26 linux/include/asm-i386/ipc.h - 1.4 linux/include/asm-i386/fixmap.h - 1.16 linux/include/asm-i386/elf.h - 1.14 linux/include/asm-arm/processor.h - 1.28 linux/include/asm-arm/elf.h - 1.9 linux/include/asm-arm/bugs.h - 1.6 linux/include/asm-arm/bitops.h - 1.16 linux/include/asm-arm/arch-rpc/time.h - 1.9 linux/include/asm-arm/arch-nexuspci/time.h - 1.10 linux/include/asm-arm/arch-ebsa285/time.h - 1.16 linux/include/asm-arm/arch-ebsa110/time.h - 1.12 linux/include/asm-arm/arch-arc/time.h - 1.9 linux/include/asm-alpha/spinlock.h - 1.16 linux/include/asm-alpha/hardirq.h - 1.18 linux/include/asm-alpha/elf.h - 1.9 linux/fs/vfat/vfatfs_syms.c - 1.10 linux/fs/ufs/super.c - 1.41 linux/fs/ufs/dir.c - 1.23 linux/fs/sysv/inode.c - 1.38 linux/fs/sysv/dir.c - 1.19 linux/fs/super.c - 1.101 linux/fs/stat.c - 1.33 linux/fs/smbfs/inode.c - 1.46 linux/fs/select.c - 1.25 linux/fs/romfs/inode.c - 1.43 linux/fs/readdir.c - 1.23 linux/fs/read_write.c - 1.34 linux/fs/qnx4/inode.c - 1.43 linux/fs/qnx4/dir.c - 1.16 linux/fs/proc/root.c - 1.31 linux/fs/proc/inode.c - 1.31 linux/fs/proc/base.c - 1.51 linux/fs/pipe.c - 1.39 linux/fs/open.c - 1.49 linux/fs/ntfs/super.c - 1.25 linux/fs/ntfs/inode.c - 1.27 linux/fs/nls/nls_base.c - 1.15 linux/fs/nfsd/vfs.c - 1.68 linux/fs/nfsd/nfssvc.c - 1.33 linux/fs/nfsd/nfsctl.c - 1.42 linux/fs/nfsd/export.c - 1.53 linux/fs/nfs/write.c - 1.51 linux/fs/nfs/symlink.c - 1.19 linux/fs/nfs/nfsroot.c - 1.18 linux/fs/nfs/inode.c - 1.66 linux/fs/nfs/file.c - 1.43 linux/fs/nfs/dir.c - 1.51 linux/fs/ncpfs/ncplib_kernel.c - 1.14 linux/fs/ncpfs/inode.c - 1.43 linux/fs/namei.c - 1.70 linux/fs/msdos/msdosfs_syms.c - 1.12 linux/fs/minix/inode.c - 1.41 linux/fs/minix/dir.c - 1.16 linux/fs/locks.c - 1.40 linux/fs/lockd/mon.c - 1.13 linux/fs/lockd/host.c - 1.10 linux/fs/isofs/inode.c - 1.43 linux/fs/ioctl.c - 1.19 linux/fs/inode.c - 1.97 linux/fs/hfs/super.c - 1.21 linux/fs/filesystems.c - 1.30 linux/fs/file_table.c - 1.33 linux/fs/fcntl.c - 1.32 linux/fs/fat/misc.c - 1.17 linux/fs/fat/inode.c - 1.58 linux/fs/ext2/super.c - 1.47 linux/fs/ext2/dir.c - 1.30 linux/fs/ext2/Makefile - 1.11 linux/fs/exec.c - 1.83 linux/fs/dquot.c - 1.69 linux/fs/devpts/inode.c - 1.22 linux/fs/devpts/Makefile - 1.7 linux/fs/dcache.c - 1.53 linux/fs/coda/sysctl.c - 1.19 linux/fs/coda/psdev.c - 1.27 linux/fs/coda/inode.c - 1.30 linux/fs/buffer.c - 1.156 linux/fs/block_dev.c - 1.76 linux/fs/binfmt_misc.c - 1.30 linux/fs/binfmt_elf.c - 1.56 linux/fs/autofs/init.c - 1.11 linux/fs/affs/super.c - 1.33 linux/fs/adfs/super.c - 1.27 linux/fs/Makefile - 1.77 linux/drivers/video/vesafb.c - 1.30 linux/drivers/video/tgafb.c - 1.27 linux/drivers/video/retz3fb.c - 1.24 linux/drivers/video/pm2fb.c - 1.22 linux/drivers/video/fbmem.c - 1.65 linux/drivers/video/atafb.c - 1.22 linux/drivers/video/amifb.c - 1.30 linux/drivers/usb/Makefile - 1.61 linux/drivers/sgi/char/shmiq.c - 1.21 linux/drivers/sgi/char/sgiserial.c - 1.17 linux/drivers/scsi/wd7000.c - 1.26 linux/drivers/scsi/ultrastor.h - 1.7 linux/drivers/scsi/ultrastor.c - 1.20 linux/drivers/scsi/u14-34f.h - 1.17 linux/drivers/scsi/u14-34f.c - 1.33 linux/drivers/scsi/tmscsim.c - 1.24 linux/drivers/scsi/t128.h - 1.9 linux/drivers/scsi/t128.c - 1.15 linux/drivers/scsi/sym53c8xx.h - 1.15 linux/drivers/scsi/sym53c8xx.c - 1.46 linux/drivers/scsi/sym53c416.h - 1.9 linux/drivers/scsi/sym53c416.c - 1.19 linux/drivers/scsi/st.c - 1.65 linux/drivers/scsi/sr.c - 1.66 linux/drivers/scsi/sgiwd93.h - 1.8 linux/drivers/scsi/sgiwd93.c - 1.17 linux/drivers/scsi/sg.c - 1.53 linux/drivers/scsi/seagate.h - 1.8 linux/drivers/scsi/seagate.c - 1.26 linux/drivers/scsi/sd.c - 1.86 linux/drivers/scsi/scsi_syms.c - 1.32 linux/drivers/scsi/scsi_proc.c - 1.18 linux/drivers/scsi/scsi_ioctl.c - 1.30 linux/drivers/scsi/scsi_error.c - 1.44 linux/drivers/scsi/scsi_debug.h - 1.14 linux/drivers/scsi/scsi_debug.c - 1.34 linux/drivers/scsi/scsi.h - 1.51 linux/drivers/scsi/scsi.c - 1.76 linux/drivers/scsi/qlogicisp.h - 1.7 linux/drivers/scsi/qlogicisp.c - 1.35 linux/drivers/scsi/qlogicfc.h - 1.14 linux/drivers/scsi/qlogicfc.c - 1.39 linux/drivers/scsi/psi240i.h - 1.8 linux/drivers/scsi/psi240i.c - 1.13 linux/drivers/scsi/ppa.h - 1.14 linux/drivers/scsi/ppa.c - 1.25 linux/drivers/scsi/pluto.h - 1.7 linux/drivers/scsi/pluto.c - 1.20 linux/drivers/scsi/pci2220i.h - 1.11 linux/drivers/scsi/pci2220i.c - 1.30 linux/drivers/scsi/pci2000.h - 1.11 linux/drivers/scsi/pci2000.c - 1.27 linux/drivers/scsi/pas16.h - 1.8 linux/drivers/scsi/pas16.c - 1.16 linux/drivers/scsi/ncr53c8xx.h - 1.12 linux/drivers/scsi/ncr53c8xx.c - 1.35 linux/drivers/scsi/mesh.c - 1.15 linux/drivers/scsi/megaraid.h - 1.20 linux/drivers/scsi/megaraid.c - 1.46 linux/drivers/scsi/mac_esp.c - 1.15 linux/drivers/scsi/mac_NCR5380.c - 1.10 linux/drivers/scsi/mac53c94.c - 1.11 linux/drivers/scsi/inia100.h - 1.16 linux/drivers/scsi/inia100.c - 1.28 linux/drivers/scsi/ini9100u.h - 1.14 linux/drivers/scsi/ini9100u.c - 1.24 linux/drivers/scsi/in2000.h - 1.14 linux/drivers/scsi/in2000.c - 1.18 linux/drivers/scsi/imm.h - 1.13 linux/drivers/scsi/imm.c - 1.24 linux/drivers/scsi/ide-scsi.c - 1.53 linux/drivers/scsi/ibmmca.h - 1.11 linux/drivers/scsi/ibmmca.c - 1.25 linux/drivers/scsi/hosts.h - 1.40 linux/drivers/scsi/hosts.c - 1.45 linux/drivers/scsi/gvp11.c - 1.16 linux/drivers/scsi/gdth.h - 1.15 linux/drivers/scsi/gdth.c - 1.29 linux/drivers/scsi/g_NCR5380.h - 1.11 linux/drivers/scsi/g_NCR5380.c - 1.23 linux/drivers/scsi/fd_mcs.h - 1.8 linux/drivers/scsi/fd_mcs.c - 1.14 linux/drivers/scsi/fcal.h - 1.7 linux/drivers/scsi/fcal.c - 1.15 linux/drivers/scsi/esp.c - 1.34 linux/drivers/scsi/eata_pio.c - 1.22 linux/drivers/scsi/eata.h - 1.17 linux/drivers/scsi/eata.c - 1.36 linux/drivers/scsi/dtc.h - 1.8 linux/drivers/scsi/dtc.c - 1.15 linux/drivers/scsi/dc390.h - 1.10 linux/drivers/scsi/atp870u.h - 1.10 linux/drivers/scsi/atp870u.c - 1.27 linux/drivers/scsi/atari_scsi.c - 1.13 linux/drivers/scsi/atari_dma_emul.c - 1.4 linux/drivers/scsi/atari_NCR5380.c - 1.11 linux/drivers/scsi/aha1740.h - 1.8 linux/drivers/scsi/aha1740.c - 1.17 linux/drivers/scsi/aha1542.h - 1.10 linux/drivers/scsi/aha1542.c - 1.36 linux/drivers/scsi/advansys.h - 1.11 linux/drivers/scsi/advansys.c - 1.36 linux/drivers/scsi/a3000.c - 1.15 linux/drivers/scsi/a2091.c - 1.18 linux/drivers/scsi/NCR5380.c - 1.20 linux/drivers/scsi/Makefile - 1.53 linux/drivers/scsi/BusLogic.h - 1.14 linux/drivers/scsi/BusLogic.c - 1.24 linux/drivers/scsi/AM53C974.h - 1.7 linux/drivers/scsi/AM53C974.c - 1.20 linux/drivers/scsi/53c7xx.c - 1.25 linux/drivers/sbus/char/vfc_dev.c - 1.19 linux/drivers/sbus/char/bpp.c - 1.26 linux/drivers/pci/quirks.c - 1.38 linux/drivers/net/yellowfin.c - 1.36 linux/drivers/net/via-rhine.c - 1.43 linux/drivers/net/tlan.c - 1.34 linux/drivers/net/sunqe.c - 1.26 linux/drivers/net/sunhme.c - 1.44 linux/drivers/net/smc-mca.c - 1.17 linux/drivers/net/slip.h - 1.7 linux/drivers/net/slip.c - 1.25 linux/drivers/net/seeq8005.c - 1.19 linux/drivers/net/rrunner.c - 1.27 linux/drivers/net/rcpci45.c - 1.28 linux/drivers/net/rclanmtl.h - 1.8 linux/drivers/net/ppp_deflate.c - 1.12 linux/drivers/net/pcnet32.c - 1.43 linux/drivers/net/ne2k-pci.c - 1.27 linux/drivers/net/myri_sbus.c - 1.20 linux/drivers/net/mace.c - 1.21 linux/drivers/net/irda/w83977af_ir.c - 1.30 linux/drivers/net/irda/irport.c - 1.30 linux/drivers/net/irda/Makefile - 1.24 linux/drivers/net/hp100.c - 1.29 linux/drivers/net/hamradio/scc.c - 1.32 linux/drivers/net/hamradio/mkiss.h - 1.5 linux/drivers/net/hamradio/mkiss.c - 1.17 linux/drivers/net/hamradio/dmascc.c - 1.16 linux/drivers/net/fmv18x.c - 1.20 linux/drivers/net/ewrk3.c - 1.28 linux/drivers/net/epic100.c - 1.36 linux/drivers/net/eepro100.c - 1.59 linux/drivers/net/depca.c - 1.27 linux/drivers/net/defxx.c - 1.25 linux/drivers/net/cs89x0.h - 1.7 linux/drivers/net/cs89x0.c - 1.30 linux/drivers/net/bmac.c - 1.24 linux/drivers/net/atari_pamsnet.c - 1.16 linux/drivers/net/atari_bionet.c - 1.17 linux/drivers/net/apne.c - 1.14 linux/drivers/net/am79c961a.h - 1.7 linux/drivers/net/am79c961a.c - 1.19 linux/drivers/net/acenic.h - 1.23 linux/drivers/net/acenic.c - 1.46 linux/drivers/net/Space.c - 1.43 linux/drivers/net/Makefile - 1.72 linux/drivers/net/82596.c - 1.26 linux/drivers/net/3c59x.c - 1.49 linux/drivers/net/3c505.c - 1.35 linux/drivers/macintosh/macserial.c - 1.29 linux/drivers/macintosh/adb.c - 1.26 linux/drivers/isdn/sc/init.c - 1.10 linux/drivers/isdn/pcbit/drv.c - 1.17 linux/drivers/isdn/isdnloop/isdnloop.c - 1.18 linux/drivers/isdn/icn/icn.c - 1.22 linux/drivers/isdn/hisax/teleint.c - 1.18 linux/drivers/isdn/hisax/tei.c - 1.13 linux/drivers/isdn/hisax/sedlbauer.c - 1.26 linux/drivers/isdn/hisax/niccy.c - 1.24 linux/drivers/isdn/hisax/elsa.c - 1.27 linux/drivers/isdn/hisax/diva.c - 1.23 linux/drivers/isdn/hisax/config.c - 1.38 linux/drivers/isdn/hisax/callc.c - 1.23 linux/drivers/isdn/act2000/module.c - 1.13 linux/drivers/char/vt.c - 1.38 linux/drivers/char/vc_screen.c - 1.17 linux/drivers/char/tty_ioctl.c - 1.10 linux/drivers/char/tty_io.c - 1.70 linux/drivers/char/tpqic02.c - 1.28 linux/drivers/char/sysrq.c - 1.36 linux/drivers/char/synclink.c - 1.37 linux/drivers/char/stallion.c - 1.30 linux/drivers/char/specialix.c - 1.20 linux/drivers/char/serial167.c - 1.21 linux/drivers/char/rocket.c - 1.23 linux/drivers/char/riscom8.c - 1.20 linux/drivers/char/random.c - 1.40 linux/drivers/char/pcxx.c - 1.18 linux/drivers/char/n_hdlc.c - 1.21 linux/drivers/char/misc.c - 1.37 linux/drivers/char/mem.c - 1.53 linux/drivers/char/lp.c - 1.39 linux/drivers/char/keyboard.c - 1.35 linux/drivers/char/istallion.c - 1.29 linux/drivers/char/isicom.c - 1.26 linux/drivers/char/ftape/zftape/zftape-vtbl.h - 1.6 linux/drivers/char/ftape/zftape/zftape-init.c - 1.19 linux/drivers/char/esp.c - 1.22 linux/drivers/char/dtlk.c - 1.22 linux/drivers/char/dsp56k.c - 1.23 linux/drivers/char/cyclades.c - 1.31 linux/drivers/cdrom/cm206.c - 1.34 linux/drivers/block/z2ram.c - 1.30 linux/drivers/block/rd.c - 1.73 linux/drivers/block/paride/pt.c - 1.23 linux/drivers/block/paride/pg.c - 1.23 linux/drivers/block/loop.c - 1.84 linux/drivers/block/ll_rw_blk.c - 1.133 linux/drivers/block/genhd.c - 1.53 linux/drivers/block/floppy.c - 1.67 linux/drivers/block/ataflop.c - 1.40 linux/drivers/block/amiflop.c - 1.41 linux/drivers/block/acsi_slm.c - 1.16 linux/drivers/block/acsi.c - 1.48 linux/drivers/acorn/scsi/queue.h - 1.7 linux/drivers/acorn/scsi/queue.c - 1.10 linux/drivers/acorn/scsi/powertec.c - 1.22 linux/drivers/acorn/scsi/oak.c - 1.16 linux/drivers/acorn/scsi/msgqueue.h - 1.5 linux/drivers/acorn/scsi/msgqueue.c - 1.7 linux/drivers/acorn/scsi/fas216.h - 1.9 linux/drivers/acorn/scsi/fas216.c - 1.19 linux/drivers/acorn/scsi/eesox.c - 1.22 linux/drivers/acorn/scsi/ecoscsi.c - 1.16 linux/drivers/acorn/scsi/cumana_2.c - 1.22 linux/drivers/acorn/scsi/cumana_1.c - 1.15 linux/drivers/acorn/scsi/acornscsi.h - 1.9 linux/drivers/acorn/scsi/acornscsi.c - 1.26 linux/drivers/acorn/scsi/acornscsi-io.S - 1.4 linux/drivers/acorn/scsi/Makefile - 1.12 linux/drivers/acorn/net/etherh.c - 1.21 linux/drivers/acorn/net/ether3.h - 1.7 linux/drivers/acorn/net/ether3.c - 1.19 linux/drivers/acorn/net/ether1.h - 1.7 linux/drivers/acorn/net/ether1.c - 1.18 linux/drivers/acorn/net/Makefile - 1.9 linux/drivers/acorn/block/fd1772.c - 1.37 linux/drivers/Makefile - 1.44 linux/arch/sparc64/solaris/socksys.c - 1.20 linux/arch/sparc64/mm/init.c - 1.57 linux/arch/sparc64/kernel/sys_sunos32.c - 1.48 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.58 linux/arch/sparc64/kernel/process.c - 1.46 linux/arch/sparc64/kernel/ioctl32.c - 1.72 linux/arch/sparc64/defconfig - 1.93 linux/arch/sparc/prom/bootstr.c - 1.6 linux/arch/sparc/mm/srmmu.c - 1.46 linux/arch/sparc/mm/init.c - 1.37 linux/arch/sparc/kernel/traps.c - 1.13 linux/arch/sparc/kernel/sys_sunos.c - 1.42 linux/arch/sparc/kernel/sparc_ksyms.c - 1.40 linux/arch/sparc/kernel/smp.c - 1.22 linux/arch/sparc/kernel/sclow.S - 1.6 linux/arch/sparc/kernel/ptrace.c - 1.19 linux/arch/sparc/kernel/process.c - 1.36 linux/arch/sparc/kernel/ioport.c - 1.27 linux/arch/sparc/kernel/entry.S - 1.19 linux/arch/sparc/defconfig - 1.39 linux/arch/ppc/mm/init.c - 1.50 linux/arch/ppc/kernel/smp.c - 1.50 linux/arch/ppc/kernel/setup.c - 1.56 linux/arch/ppc/kernel/process.c - 1.50 linux/arch/ppc/kernel/ppc_ksyms.c - 1.57 linux/arch/ppc/kernel/misc.S - 1.57 linux/arch/ppc/kernel/Makefile - 1.41 linux/arch/ppc/boot/Makefile - 1.24 linux/arch/ppc/amiga/bootinfo.c - 1.7 linux/arch/ppc/Makefile - 1.40 linux/arch/mips/mm/init.c - 1.17 linux/arch/mips/kernel/sysmips.c - 1.10 linux/arch/mips/kernel/setup.c - 1.17 linux/arch/mips/kernel/irixelf.c - 1.17 linux/arch/m68k/sun3x/time.h - 1.5 linux/arch/m68k/sun3x/time.c - 1.8 linux/arch/m68k/q40/q40ints.c - 1.11 linux/arch/m68k/q40/config.c - 1.19 linux/arch/m68k/mvme16x/config.c - 1.13 linux/arch/m68k/mvme16x/16xints.c - 1.4 linux/arch/m68k/mvme147/config.c - 1.16 linux/arch/m68k/mvme147/147ints.c - 1.4 linux/arch/m68k/mm/init.c - 1.18 linux/arch/m68k/mac/macints.c - 1.14 linux/arch/m68k/mac/config.c - 1.15 linux/arch/m68k/kernel/time.c - 1.11 linux/arch/m68k/kernel/sys_m68k.c - 1.10 linux/arch/m68k/kernel/setup.c - 1.23 linux/arch/m68k/kernel/ptrace.c - 1.14 linux/arch/m68k/kernel/ints.c - 1.9 linux/arch/m68k/kernel/entry.S - 1.22 linux/arch/m68k/hp300/time.h - 1.3 linux/arch/m68k/hp300/time.c - 1.6 linux/arch/m68k/hp300/ints.h - 1.3 linux/arch/m68k/hp300/ints.c - 1.7 linux/arch/m68k/hp300/config.c - 1.8 linux/arch/m68k/bvme6000/config.c - 1.13 linux/arch/m68k/bvme6000/bvmeints.c - 1.4 linux/arch/m68k/atari/time.c - 1.7 linux/arch/m68k/atari/stdma.c - 1.6 linux/arch/m68k/atari/config.c - 1.13 linux/arch/m68k/atari/ataints.c - 1.12 linux/arch/m68k/apollo/dn_ints.c - 1.10 linux/arch/m68k/apollo/config.c - 1.12 linux/arch/m68k/amiga/config.c - 1.19 linux/arch/m68k/amiga/cia.c - 1.9 linux/arch/m68k/amiga/amiints.c - 1.11 linux/arch/i386/mm/ioremap.c - 1.22 linux/arch/i386/mm/init.c - 1.56 linux/arch/i386/mm/fault.c - 1.33 linux/arch/i386/lib/usercopy.c - 1.11 linux/arch/i386/kernel/vm86.c - 1.30 linux/arch/i386/kernel/traps.c - 1.78 linux/arch/i386/kernel/trampoline.S - 1.10 linux/arch/i386/kernel/sys_i386.c - 1.15 linux/arch/i386/kernel/smp.c - 1.57 linux/arch/i386/kernel/signal.c - 1.37 linux/arch/i386/kernel/setup.c - 1.93 linux/arch/i386/kernel/ptrace.c - 1.29 linux/arch/i386/kernel/process.c - 1.71 linux/arch/i386/kernel/ldt.c - 1.18 linux/arch/i386/kernel/irq.c - 1.58 linux/arch/i386/kernel/ioport.c - 1.10 linux/arch/i386/kernel/io_apic.c - 1.61 linux/arch/i386/kernel/i386_ksyms.c - 1.71 linux/arch/i386/kernel/head.S - 1.33 linux/arch/i386/kernel/entry.S - 1.79 linux/arch/i386/kernel/apm.c - 1.63 linux/arch/i386/kernel/Makefile - 1.49 linux/arch/i386/boot/setup.S - 1.34 linux/arch/i386/Makefile - 1.52 linux/arch/arm/kernel/traps.c - 1.37 linux/arch/arm/kernel/sys_arm.c - 1.24 linux/arch/arm/kernel/setup.c - 1.43 linux/arch/arm/kernel/ptrace.c - 1.27 linux/arch/arm/kernel/irq.c - 1.30 linux/arch/arm/kernel/entry-armv.S - 1.44 linux/arch/arm/kernel/calls.S - 1.23 linux/arch/alpha/mm/init.c - 1.28 linux/arch/alpha/kernel/smp.c - 1.45 linux/arch/alpha/kernel/setup.c - 1.38 linux/arch/alpha/kernel/ptrace.c - 1.20 linux/arch/alpha/kernel/process.c - 1.35 linux/arch/alpha/kernel/irq.c - 1.32 linux/arch/alpha/kernel/entry.S - 1.37 linux/Makefile - 1.247 linux/MAINTAINERS - 1.140 linux/Documentation/sysctl/vm.txt - 1.11 linux/Documentation/pci.txt - 1.20 linux/Documentation/networking/ip-sysctl.txt - 1.18 linux/Documentation/ioctl-number.txt - 1.22 linux/Documentation/ide.txt - 1.12 linux/Documentation/Changes - 1.65 linux/CREDITS - 1.102 linux/net/decnet/dn_route.c - 1.28 linux/net/decnet/dn_nsp_out.c - 1.15 linux/net/decnet/dn_nsp_in.c - 1.21 linux/net/decnet/dn_neigh.c - 1.14 linux/net/decnet/dn_fib.c - 1.12 linux/net/decnet/dn_dev.c - 1.19 linux/net/decnet/af_decnet.c - 1.40 linux/net/decnet/TODO - 1.11 linux/net/decnet/Makefile - 1.11 linux/include/net/dn_route.h - 1.10 linux/include/net/dn_fib.h - 1.7 linux/include/net/dn_dev.h - 1.8 linux/include/linux/ide.h - 1.78 linux/include/linux/cycx_x25.h - 1.4 linux/include/linux/cycx_drv.h - 1.6 linux/include/linux/cycx_cfm.h - 1.3 linux/include/linux/cyclomx.h - 1.9 linux/include/linux/blkpg.h - 1.5 linux/include/asm-m68k/hdreg.h - 1.2 linux/fs/hpfs/super.c - 1.25 linux/fs/efs/super.c - 1.20 linux/drivers/video/cyber2000fb.c - 1.40 linux/drivers/net/irda/smc-ircc.c - 1.30 linux/drivers/isdn/hisax/avm_pci.c - 1.22 linux/drivers/isdn/eicon/eicon_pci.c - 1.11 linux/drivers/isdn/eicon/eicon_mod.c - 1.22 linux/drivers/isdn/eicon/eicon_idi.c - 1.19 linux/drivers/acorn/scsi/arxescsi.c - 1.18 linux/arch/i386/vmlinux.lds.S - 1.21 linux/Documentation/kernel-parameters.txt - 1.26 linux/drivers/tc/zs.c - 1.14 linux/drivers/char/dz.c - 1.22 linux/arch/mips/baget/vacserial.c - 1.17 linux/arch/mips/arc/misc.c - 1.7 linux/drivers/char/ppdev.c - 1.38 linux/drivers/block/cpqarray.c - 1.71 linux/drivers/parport/parport_mfc3.c - 1.13 linux/drivers/parport/parport_atari.c - 1.7 linux/drivers/parport/parport_amiga.c - 1.11 linux/drivers/char/raw.c - 1.38 linux/drivers/net/ppp_generic.c - 1.37 linux/drivers/char/sx.c - 1.35 linux/fs/partitions/msdos.c - 1.29 linux/fs/partitions/check.c - 1.70 linux/arch/i386/kernel/i8259.c - 1.39 linux/drivers/net/sis900.c - 1.45 linux/drivers/net/sb1000.c - 1.23 linux/drivers/net/fc/iph5526.c - 1.26 linux/drivers/char/ip2main.c - 1.28 linux/drivers/atm/zatm.c - 1.19 linux/drivers/atm/nicstar.h - 1.7 linux/drivers/atm/nicstar.c - 1.24 linux/drivers/atm/horizon.c - 1.18 linux/drivers/atm/eni.c - 1.21 linux/drivers/atm/atmtcp.c - 1.13 linux/drivers/atm/ambassador.c - 1.22 linux/drivers/atm/Makefile - 1.26 linux/net/sched/sch_atm.c - 1.13 linux/net/core/netfilter.c - 1.23 linux/net/atm/svc.c - 1.14 linux/net/atm/signaling.c - 1.11 linux/net/atm/resources.h - 1.4 linux/net/atm/resources.c - 1.12 linux/net/atm/raw.c - 1.8 linux/net/atm/pvc.c - 1.13 linux/net/atm/proc.c - 1.20 linux/net/atm/mpoa_proc.c - 1.11 linux/net/atm/mpc.c - 1.15 linux/net/atm/lec.c - 1.21 linux/net/atm/ipcommon.c - 1.4 linux/net/atm/common.h - 1.6 linux/net/atm/common.c - 1.23 linux/net/atm/clip.c - 1.16 linux/net/atm/atm_misc.c - 1.6 linux/net/atm/addr.c - 1.6 linux/net/atm/Makefile - 1.14 linux/include/net/atmclip.h - 1.6 linux/include/linux/netfilter_ipv4.h - 1.9 linux/include/linux/atmdev.h - 1.15 linux/arch/ppc/kernel/entry.S - 1.35 linux/drivers/block/DAC960.h - 1.24 linux/drivers/block/DAC960.c - 1.69 linux/arch/sparc64/kernel/power.c - 1.16 linux/arch/sh/mm/init.c - 1.22 linux/drivers/scsi/ips.h - 1.23 linux/drivers/scsi/ips.c - 1.40 linux/net/irda/ircomm/ircomm_tty_attach.c - 1.17 linux/net/irda/ircomm/ircomm_tty.c - 1.28 linux/net/irda/ircomm/ircomm_ttp.c - 1.8 linux/net/irda/ircomm/ircomm_lmp.c - 1.10 linux/net/irda/ircomm/ircomm_event.c - 1.7 linux/net/irda/ircomm/ircomm_core.c - 1.20 linux/include/asm-i386/kmap_types.h - 1.14 linux/drivers/pcmcia/tcic.c - 1.26 linux/drivers/pcmcia/i82365.c - 1.39 linux/drivers/pcmcia/ds.c - 1.28 linux/drivers/pcmcia/cs_internal.h - 1.16 linux/drivers/pcmcia/cs.c - 1.38 linux/drivers/net/sun3lance.c - 1.17 linux/arch/m68k/sun3/sun3ints.c - 1.7 linux/arch/m68k/sun3/prom/printf.c - 1.2 linux/arch/m68k/sun3/prom/init.c - 1.3 linux/arch/m68k/sun3/config.c - 1.12 linux/arch/m68k/mac/via.c - 1.7 linux/arch/m68k/mac/psc.c - 1.6 linux/arch/m68k/mac/oss.c - 1.5 linux/arch/m68k/mac/iop.c - 1.9 linux/fs/udf/dir.c - 1.24 linux/include/asm-m68k/sun3ints.h - 1.6 linux/fs/udf/super.c - 1.37 linux/include/linux/spinlock.h - 1.25 linux/include/asm-ppc/pci.h - 1.20 linux/drivers/net/starfire.c - 1.32 linux/drivers/net/pcmcia/3c589_cs.c - 1.27 linux/drivers/char/drm/gamma_dma.c - 1.16 linux/drivers/char/drm/drmP.h - 1.25 linux/drivers/net/wan/cycx_main.c - 1.16 linux/drivers/net/wan/cycx_drv.c - 1.8 linux/drivers/net/wan/cosa.c - 1.33 linux/arch/i386/kernel/smpboot.c - 1.63 linux/include/linux/pci_ids.h - 1.91 linux/drivers/net/wan/x25_asy.c - 1.11 linux/drivers/net/wan/sdlamain.c - 1.18 linux/drivers/net/wan/sdla_x25.c - 1.18 linux/drivers/net/wan/sdla_ppp.c - 1.23 linux/drivers/net/wan/sdla_fr.c - 1.23 linux/drivers/net/wan/sdla.c - 1.17 linux/drivers/net/wan/dlci.c - 1.12 linux/drivers/net/wan/cycx_x25.c - 1.18 linux/drivers/scsi/sim710.c - 1.15 linux/drivers/net/pcmcia/xirc2ps_cs.c - 1.24 linux/drivers/net/pcmcia/nmclan_cs.c - 1.19 linux/drivers/net/pcmcia/fmvj18x_cs.c - 1.23 linux/drivers/net/pcmcia/smc91c92_cs.c - 1.21 linux/mm/bootmem.c - 1.26 linux/drivers/net/ppp_synctty.c - 1.14 linux/fs/proc/proc_misc.c - 1.61 linux/fs/bfs/inode.c - 1.31 linux/fs/bfs/dir.c - 1.24 linux/drivers/net/setup.c - 1.23 linux/drivers/scsi/sun3_scsi.c - 1.18 linux/drivers/pci/pci.ids - 1.60 linux/drivers/net/sk98lin/skge.c - 1.25 linux/include/asm-arm/arch-cl7500/time.h - 1.9 linux/include/linux/mmzone.h - 1.37 linux/include/linux/agpgart.h - 1.6 linux/include/linux/agp_backend.h - 1.29 linux/drivers/char/agp/Makefile - 1.16 linux/kernel/timer.c - 1.45 linux/drivers/scsi/scsi_lib.c - 1.64 linux/drivers/char/agp/agp.h - 1.37 linux/include/linux/i2c-id.h - 1.17 linux/drivers/i2c/i2c-dev.c - 1.29 linux/drivers/i2c/i2c-core.c - 1.27 linux/Documentation/video4linux/bttv/Sound-FAQ - 1.12 linux/Documentation/video4linux/bttv/CARDLIST - 1.17 linux/drivers/pcmcia/pci_socket.c - 1.18 linux/fs/openpromfs/inode.c - 1.26 linux/fs/cramfs/inode.c - 1.36 linux/include/linux/input.h - 1.26 linux/drivers/telephony/phonedev.c - 1.11 linux/drivers/net/arcnet/rfc1201.c - 1.6 linux/drivers/net/arcnet/rfc1051.c - 1.4 linux/drivers/net/arcnet/com90xx.c - 1.10 linux/drivers/net/arcnet/com90io.c - 1.11 linux/drivers/net/arcnet/com20020-pci.c - 1.16 linux/drivers/net/arcnet/com20020-isa.c - 1.9 linux/drivers/net/arcnet/arcnet.c - 1.16 linux/drivers/net/arcnet/arc-rawmode.c - 1.4 linux/net/sched/sch_ingress.c - 1.13 linux/drivers/pnp/quirks.c - 1.14 linux/net/decnet/dn_table.c - 1.9 linux/net/decnet/dn_rules.c - 1.6 linux/drivers/ieee1394/raw1394.c - 1.28 linux/drivers/ieee1394/ohci1394.c - 1.32 linux/arch/arm/lib/copy_page.S - 1.6 linux/arch/i386/kernel/apic.c - 1.44 linux/arch/i386/kernel/mpparse.c - 1.38 linux/drivers/char/moxa.c - 1.18 linux/drivers/char/mxser.c - 1.24 linux/include/asm-i386/mpspec.h - 1.15 linux/include/asm-i386/apicdef.h - 1.12 linux/drivers/scsi/scsi_scan.c - 1.47 linux/drivers/scsi/3w-xxxx.h - 1.19 linux/drivers/scsi/3w-xxxx.c - 1.31 linux/drivers/net/wan/sdla_chdlc.c - 1.25 linux/drivers/net/tokenring/madgemc.c - 1.11 linux/fs/autofs4/init.c - 1.8 linux/fs/autofs4/root.c - 1.19 linux/drivers/net/irda/nsc-ircc.c - 1.27 linux/drivers/net/macmace.c - 1.10 linux/drivers/char/vme_scc.c - 1.17 linux/arch/ia64/kernel/head.S - 1.15 linux/arch/ia64/kernel/gate.S - 1.15 linux/drivers/atm/iphase.c - 1.21 linux/arch/ia64/kernel/fw-emu.c - 1.12 linux/arch/ia64/kernel/entry.S - 1.37 linux/arch/ia64/kernel/efi.c - 1.22 linux/arch/ia64/kernel/acpi.c - 1.22 linux/arch/ia64/kernel/Makefile - 1.21 linux/drivers/acorn/char/pcf8583.c - 1.9 linux/arch/ia64/ia32/sys_ia32.c - 1.45 linux/arch/ia64/ia32/ia32_entry.S - 1.24 linux/arch/ia64/ia32/binfmt_elf32.c - 1.18 linux/drivers/acorn/char/i2c.c - 1.9 linux/arch/ppc/kernel/pci-dma.c - 1.6 linux/arch/ia64/dig/machvec.c - 1.3 linux/arch/ia64/tools/print_offsets.c - 1.17 linux/arch/ia64/Makefile - 1.27 linux/arch/ia64/kernel/irq.c - 1.28 linux/arch/ia64/kernel/setup.c - 1.26 linux/arch/ia64/kernel/signal.c - 1.25 linux/arch/ia64/kernel/smp.c - 1.23 linux/arch/ia64/kernel/time.c - 1.22 linux/arch/ia64/kernel/traps.c - 1.22 linux/arch/ia64/kernel/unaligned.c - 1.14 linux/arch/ia64/kernel/unwind.c - 1.15 linux/arch/ia64/lib/copy_user.S - 1.12 linux/arch/ia64/kernel/machvec.c - 1.7 linux/arch/ia64/lib/do_csum.S - 1.9 linux/arch/ia64/kernel/sal.c - 1.10 linux/arch/ia64/kernel/ptrace.c - 1.23 linux/arch/ia64/kernel/process.c - 1.28 linux/arch/ia64/kernel/perfmon.c - 1.25 linux/arch/ia64/kernel/mca.c - 1.20 linux/arch/ia64/mm/init.c - 1.27 linux/arch/ia64/mm/fault.c - 1.16 linux/arch/ia64/kernel/mca_asm.S - 1.11 linux/drivers/scsi/qla1280.h - 1.12 linux/drivers/scsi/qla1280.c - 1.27 linux/include/asm-ia64/iosapic.h - 1.9 linux/include/asm-ia64/io.h - 1.12 linux/include/asm-ia64/ia32.h - 1.19 linux/include/asm-ia64/hardirq.h - 1.18 linux/include/asm-ia64/bitops.h - 1.14 linux/include/asm-ia64/atomic.h - 1.9 linux/include/asm-ia64/acpi-ext.h - 1.10 linux/include/asm-ia64/serial.h - 1.3 linux/include/asm-ia64/sal.h - 1.15 linux/include/asm-ia64/processor.h - 1.33 linux/include/linux/raid/md.h - 1.24 linux/include/asm-ia64/machvec.h - 1.14 linux/include/asm-ia64/pci.h - 1.19 linux/include/asm-ia64/pal.h - 1.11 linux/include/asm-ia64/page.h - 1.22 linux/include/asm-ia64/ptrace.h - 1.13 linux/include/asm-ia64/machvec_init.h - 1.7 linux/include/asm-ia64/machvec_sn1.h - 1.9 linux/include/asm-ia64/mca.h - 1.9 linux/include/asm-ia64/spinlock.h - 1.14 linux/include/asm-ia64/uaccess.h - 1.11 linux/include/asm-ia64/unwind.h - 1.7 linux/include/asm-ia64/system.h - 1.26 linux/drivers/scsi/sun3_NCR5380.c - 1.11 linux/drivers/net/8139too.c - 1.51 linux/drivers/macintosh/via-pmu68k.c - 1.10 linux/drivers/macintosh/via-maciisi.c - 1.4 linux/drivers/macintosh/via-macii.c - 1.5 linux/drivers/char/amiserial.c - 1.21 linux/arch/m68k/mac/baboon.c - 1.8 linux/arch/arm/mm/consistent.c - 1.16 linux/include/linux/devfs_fs_kernel.h - 1.22 linux/drivers/scsi/pcmcia/qlogic_stub.c - 1.15 linux/drivers/scsi/pcmcia/fdomain_stub.c - 1.16 linux/fs/devfs/base.c - 1.57 linux/drivers/scsi/pcmcia/aha152x_stub.c - 1.16 linux/drivers/net/skfp/skfddi.c - 1.17 linux/net/bridge/br_stp_timer.c - 1.5 linux/net/bridge/br_stp_if.c - 1.7 linux/net/bridge/br_forward.c - 1.10 linux/net/bridge/br_fdb.c - 1.7 linux/net/bridge/br_device.c - 1.9 linux/net/bridge/br_stp.c - 1.7 linux/net/bridge/br_private_timer.h - 1.2 linux/net/bridge/br_private_stp.h - 1.5 linux/net/bridge/br_private.h - 1.12 linux/net/bridge/br_ioctl.c - 1.8 linux/net/bridge/br_input.c - 1.15 linux/net/bridge/br_if.c - 1.13 linux/drivers/video/matrox/matroxfb_base.c - 1.23 linux/drivers/net/tulip/tulip_core.c - 1.47 linux/drivers/net/tulip/tulip.h - 1.18 linux/drivers/net/tulip/interrupt.c - 1.21 linux/drivers/net/ioc3-eth.c - 1.23 linux/drivers/char/nwbutton.h - 1.3 linux/drivers/char/nwbutton.c - 1.9 linux/include/asm-mips64/elf.h - 1.10 linux/arch/mips64/mm/init.c - 1.12 linux/drivers/atm/fore200e.c - 1.20 linux/arch/mips64/kernel/syscall.c - 1.12 linux/arch/mips64/arc/misc.c - 1.4 linux/arch/mips64/kernel/setup.c - 1.8 linux/drivers/net/bonding.c - 1.21 linux/lib/brlock.c - 1.8 linux/include/linux/if_bonding.h - 1.8 linux/include/linux/brlock.h - 1.12 linux/drivers/video/riva/fbdev.c - 1.26 linux/drivers/char/sh-sci.c - 1.24 linux/net/econet/af_econet.c - 1.20 linux/include/linux/usb.h - 1.59 linux/drivers/usb/serial/usb-serial.h - 1.32 linux/drivers/usb/serial/usb-serial.c - 1.18 linux/arch/ia64/kernel/irq_ia64.c - 1.15 linux/drivers/ide/ide.c - 1.86 linux/drivers/ide/ide-tape.c - 1.46 linux/drivers/ide/ide-proc.c - 1.28 linux/drivers/ide/ide-probe.c - 1.54 linux/drivers/ide/ide-geometry.c - 1.21 linux/drivers/ide/ide-disk.c - 1.60 linux/drivers/ide/ide-cd.c - 1.62 linux/drivers/ide/Makefile - 1.37 linux/drivers/block/elevator.c - 1.31 linux/include/linux/elevator.h - 1.18 linux/drivers/net/wan/comx.c - 1.20 linux/drivers/net/wan/comx-proto-ppp.c - 1.6 linux/drivers/net/wan/comx-proto-lapb.c - 1.9 linux/drivers/net/wan/comx-proto-fr.c - 1.13 linux/drivers/net/wan/comx-hw-mixcom.c - 1.13 linux/drivers/net/wan/comx-hw-locomx.c - 1.9 linux/drivers/net/wan/comx-hw-comx.c - 1.12 linux/drivers/net/tokenring/lanstreamer.c - 1.16 linux/net/ipv4/netfilter/ipt_unclean.c - 1.12 linux/net/ipv4/netfilter/ipt_tos.c - 1.6 linux/net/ipv4/netfilter/ipt_state.c - 1.7 linux/net/ipv4/netfilter/ipt_owner.c - 1.11 linux/net/ipv4/netfilter/ipt_multiport.c - 1.8 linux/net/ipv4/netfilter/ipt_mark.c - 1.6 linux/net/ipv4/netfilter/ipt_mac.c - 1.8 linux/net/ipv4/netfilter/ipt_limit.c - 1.7 linux/net/ipv4/netfilter/ipt_TOS.c - 1.10 linux/net/ipv4/netfilter/ipt_REJECT.c - 1.21 linux/net/ipv4/netfilter/ipt_REDIRECT.c - 1.8 linux/net/ipv4/netfilter/ipt_MIRROR.c - 1.11 linux/net/ipv4/netfilter/ipt_MASQUERADE.c - 1.11 linux/net/ipv4/netfilter/ipt_MARK.c - 1.6 linux/net/ipv4/netfilter/ipt_LOG.c - 1.12 linux/net/ipv4/netfilter/ipfwadm_core.c - 1.18 linux/net/ipv4/netfilter/ipchains_core.c - 1.15 linux/net/ipv4/netfilter/ip_tables.c - 1.20 linux/net/ipv4/netfilter/ip_nat_standalone.c - 1.25 linux/net/ipv4/netfilter/ip_nat_rule.c - 1.11 linux/net/ipv4/netfilter/ip_nat_proto_unknown.c - 1.3 linux/net/ipv4/netfilter/ip_nat_proto_udp.c - 1.3 linux/net/ipv4/netfilter/ip_nat_proto_tcp.c - 1.5 linux/net/ipv4/netfilter/ip_nat_proto_icmp.c - 1.2 linux/net/ipv4/netfilter/ip_nat_ftp.c - 1.12 linux/net/ipv4/netfilter/ip_nat_core.c - 1.21 linux/net/ipv4/netfilter/ip_fw_compat_redir.c - 1.7 linux/net/ipv4/netfilter/ip_fw_compat_masq.c - 1.12 linux/net/ipv4/netfilter/ip_fw_compat.c - 1.18 linux/net/ipv4/netfilter/ip_conntrack_ftp.c - 1.15 linux/net/ipv4/netfilter/ip_conntrack_core.c - 1.24 linux/include/linux/netfilter_ipv4/ipfwadm_core.h - 1.2 linux/include/linux/netfilter_ipv4/ip_tables.h - 1.8 linux/include/linux/netfilter_ipv4/ip_nat_protocol.h - 1.2 linux/include/linux/netfilter_ipv4/ip_nat_helper.h - 1.6 linux/include/linux/netfilter_ipv4/ip_nat_core.h - 1.3 linux/include/linux/netfilter_ipv4/ip_conntrack.h - 1.15 linux/include/linux/netfilter_ipv4/compat_firewall.h - 1.2 linux/drivers/scsi/dmx3191d.h - 1.7 linux/drivers/scsi/dmx3191d.c - 1.14 linux/drivers/net/pcmcia/ibmtr_cs.c - 1.14 linux/include/asm-arm/arch-shark/time.h - 1.10 linux/fs/ramfs/inode.c - 1.36 linux/drivers/usb/serial/visor.h - 1.17 linux/arch/ia64/kernel/smpboot.c - 1.20 linux/arch/ia64/ia32/ia32_traps.c - 1.7 linux/drivers/net/wan/lmc/lmc_main.c - 1.15 linux/drivers/char/rio/riotty.c - 1.11 linux/drivers/char/rio/rioinit.c - 1.9 linux/drivers/char/rio/rio_linux.h - 1.6 linux/drivers/char/rio/rio_linux.c - 1.24 linux/arch/s390/kernel/process.c - 1.19 linux/include/asm-s390/uaccess.h - 1.11 linux/arch/s390/defconfig - 1.19 linux/include/asm-s390/system.h - 1.13 linux/include/asm-s390/hardirq.h - 1.8 linux/include/asm-s390/elf.h - 1.7 linux/arch/s390/kernel/head.S - 1.11 linux/drivers/s390/net/iucv.c - 1.14 linux/drivers/s390/char/con3215.c - 1.17 linux/drivers/s390/block/dasd.c - 1.43 linux/include/asm-s390/posix_types.h - 1.4 linux/include/asm-s390/pgtable.h - 1.20 linux/include/asm-arm/arch-sa1100/time.h - 1.9 linux/arch/s390/kernel/traps.c - 1.18 linux/arch/s390/kernel/s390_ksyms.c - 1.12 linux/arch/s390/kernel/smp.c - 1.21 linux/arch/s390/mm/init.c - 1.16 linux/net/ipv6/netfilter/ip6_tables.c - 1.19 linux/include/asm-arm/arch-l7200/time.h - 1.7 linux/arch/i386/kernel/msr.c - 1.20 linux/Documentation/filesystems/Locking - 1.23 linux/drivers/char/drm/mga_drv.h - 1.14 linux/drivers/char/drm/mga_dma.c - 1.13 linux/drivers/char/drm/i810_dma.c - 1.23 linux/drivers/usb/storage/transport.h - 1.19 linux/drivers/usb/storage/transport.c - 1.43 linux/arch/alpha/kernel/core_titan.c - 1.12 linux/arch/alpha/kernel/sys_titan.c - 1.9 linux/include/asm-i386/i387.h - 1.10 linux/drivers/acpi/tables/tbxface.c - 1.18 linux/drivers/acpi/tables/tbutils.c - 1.20 linux/drivers/acpi/tables/tbinstal.c - 1.20 linux/drivers/acpi/tables/tbget.c - 1.20 linux/drivers/acpi/resources/rsxface.c - 1.17 linux/drivers/acpi/parser/psxface.c - 1.17 linux/drivers/acpi/parser/pswalk.c - 1.14 linux/drivers/acpi/parser/psargs.c - 1.20 linux/drivers/acpi/namespace/nsxfname.c - 1.16 linux/drivers/acpi/namespace/nsutils.c - 1.21 linux/drivers/acpi/namespace/nssearch.c - 1.20 linux/drivers/acpi/namespace/nsload.c - 1.20 linux/fs/jffs/inode-v23.c - 1.36 linux/drivers/acpi/namespace/nsalloc.c - 1.18 linux/drivers/acpi/hardware/hwregs.c - 1.22 linux/drivers/acpi/hardware/hwgpe.c - 1.19 linux/drivers/acpi/events/evxfregn.c - 1.18 linux/drivers/acpi/events/evxfevnt.c - 1.18 linux/drivers/acpi/events/evxface.c - 1.21 linux/drivers/acpi/events/evrgnini.c - 1.18 linux/drivers/acpi/events/evregion.c - 1.20 linux/drivers/acpi/events/evmisc.c - 1.20 linux/drivers/acpi/ec.c - 1.20 linux/drivers/acpi/dispatcher/dswexec.c - 1.19 linux/drivers/acpi/dispatcher/dsopcode.c - 1.21 linux/arch/ia64/ia32/ia32_ioctl.c - 1.10 linux/drivers/acpi/dispatcher/dsobject.c - 1.26 linux/drivers/acpi/dispatcher/dsmethod.c - 1.18 linux/arch/ia64/kernel/brl_emu.c - 1.6 linux/arch/ia64/kernel/ia64_ksyms.c - 1.20 linux/arch/ia64/kernel/palinfo.c - 1.14 linux/drivers/ieee1394/video1394.c - 1.30 linux/arch/ia64/lib/io.c - 1.6 linux/drivers/mtd/mtdchar.c - 1.14 linux/include/linux/mtd/mtd.h - 1.6 linux/drivers/net/tun.c - 1.20 linux/net/ipv4/tcp_minisocks.c - 1.26 linux/include/asm-arm/mach/dma.h - 1.4 linux/include/asm-arm/mach/arch.h - 1.9 linux/drivers/usb/storage/sddr09.c - 1.23 linux/drivers/usb/storage/freecom.c - 1.22 linux/drivers/net/natsemi.c - 1.29 linux/drivers/media/video/videodev.c - 1.18 linux/drivers/media/video/tvmixer.c - 1.15 linux/drivers/media/video/tuner.c - 1.18 linux/drivers/media/video/tda9875.c - 1.14 linux/drivers/media/video/tda7432.c - 1.14 linux/drivers/media/video/saa7185.c - 1.12 linux/drivers/media/video/saa7111.c - 1.11 linux/drivers/media/video/saa7110.c - 1.11 linux/drivers/media/video/saa5249.c - 1.16 linux/drivers/media/video/msp3400.c - 1.19 linux/drivers/media/video/cpia_pp.c - 1.11 linux/drivers/media/video/cpia.c - 1.21 linux/drivers/media/video/bttv.h - 1.14 linux/drivers/media/video/bttv-if.c - 1.13 linux/drivers/media/video/bttv-driver.c - 1.30 linux/drivers/media/video/bttv-cards.c - 1.20 linux/drivers/isdn/hysdn/hycapi.c - 1.14 linux/drivers/input/mousedev.c - 1.20 linux/drivers/input/joydev.c - 1.17 linux/drivers/input/input.c - 1.20 linux/drivers/input/evdev.c - 1.18 linux/arch/arm/tools/mach-types - 1.26 linux/drivers/macintosh/adbhid.c - 1.11 linux/drivers/md/md.c - 1.75 linux/drivers/net/hamachi.c - 1.24 linux/drivers/net/sundance.c - 1.24 linux/drivers/scsi/cpqfcTS.h - 1.8 linux/drivers/scsi/cpqfcTSinit.c - 1.30 linux/include/asm-arm/arch-tbox/time.h - 1.6 linux/include/asm-ppc/highmem.h - 1.13 linux/include/linux/divert.h - 1.3 linux/net/core/dv.c - 1.7 linux/drivers/usb/serial/belkin_sa.c - 1.31 linux/drivers/media/video/tvaudio.h - 1.4 linux/drivers/media/video/tvaudio.c - 1.18 linux/drivers/media/video/bttvp.h - 1.13 linux/net/irda/irsyms.c - 1.13 linux/net/irda/irnet/irnet_ppp.c - 1.13 linux/net/irda/irnet/irnet_irda.c - 1.15 linux/net/irda/irnet/irnet.h - 1.16 linux/arch/parisc/kernel/drivers.c - 1.5 linux/include/asm-parisc/hardirq.h - 1.3 linux/drivers/video/stifb.c - 1.10 linux/arch/parisc/mm/init.c - 1.9 linux/arch/i386/kernel/dmi_scan.c - 1.29 linux/include/asm-m68k/sun3_pgtable.h - 1.5 linux/drivers/scsi/mvme147.c - 1.4 linux/include/asm-parisc/elf.h - 1.4 linux/include/asm-m68k/motorola_pgtable.h - 1.3 linux/arch/parisc/hpux/wrappers.S - 1.3 linux/drivers/acpi/tables/tbconvrt.c - 1.18 linux/mm/shmem.c - 1.58 linux/drivers/scsi/osst.c - 1.26 linux/include/asm-ia64/sn/addrs.h - 1.5 linux/drivers/char/drm/r128_cce.c - 1.10 linux/arch/ia64/kernel/iosapic.c - 1.16 linux/arch/ia64/lib/swiotlb.c - 1.13 linux/arch/ia64/sn/io/klconflib.c - 1.5 linux/arch/ia64/sn/io/l1_command.c - 1.4 linux/fs/reiserfs/super.c - 1.34 linux/fs/reiserfs/tail_conversion.c - 1.19 linux/drivers/acpi/acpi_ksyms.c - 1.19 linux/fs/reiserfs/prints.c - 1.20 linux/drivers/char/drm/radeon_cp.c - 1.14 linux/drivers/char/drm/radeon_drm.h - 1.11 linux/drivers/char/drm/radeon_drv.h - 1.13 linux/drivers/acpi/hardware/hwtimer.c - 1.15 linux/fs/reiserfs/ioctl.c - 1.10 linux/fs/reiserfs/inode.c - 1.40 linux/fs/reiserfs/file.c - 1.15 linux/fs/reiserfs/do_balan.c - 1.15 linux/fs/reiserfs/dir.c - 1.17 linux/include/linux/reiserfs_fs.h - 1.36 linux/include/linux/reiserfs_fs_i.h - 1.8 linux/include/linux/reiserfs_fs_sb.h - 1.17 linux/fs/reiserfs/bitmap.c - 1.23 linux/drivers/usb/storage/unusual_devs.h - 1.20 linux/arch/cris/kernel/setup.c - 1.13 linux/drivers/s390/net/netiucv.c - 1.18 linux/drivers/s390/net/fsm.c - 1.7 linux/drivers/s390/net/ctcmain.c - 1.16 linux/drivers/s390/block/xpram.c - 1.34 linux/drivers/net/pci-skeleton.c - 1.16 linux/arch/s390/kernel/debug.c - 1.11 linux/net/ipv4/netfilter/ipt_tcpmss.c - 1.4 linux/net/ipv4/netfilter/ipt_TCPMSS.c - 1.9 linux/include/asm-arm/arch-integrator/time.h - 1.6 linux/drivers/scsi/aic7xxx_old/aic7xxx.h - 1.11 linux/drivers/scsi/aic7xxx_old.c - 1.31 linux/drivers/scsi/aic7xxx/aic7xxx_proc.c - 1.7 linux/drivers/scsi/aic7xxx/aic7xxx_pci.c - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_osm.h - 1.16 linux/drivers/scsi/aic7xxx/aic7xxx_inline.h - 1.8 linux/arch/arm/mach-integrator/mm.c - 1.4 linux/drivers/scsi/aic7xxx/aic7xxx.h - 1.10 linux/drivers/scsi/aic7xxx/aic7770.c - 1.8 linux/drivers/scsi/aic7xxx/Makefile - 1.13 linux/drivers/net/sungem.h - 1.10 linux/drivers/net/sungem.c - 1.28 linux/drivers/net/wan/sdla_ft1.c - 1.7 linux/drivers/net/wan/wanpipe_multppp.c - 1.11 linux/drivers/s390/char/tuball.c - 1.11 linux/drivers/s390/char/tubfs.c - 1.12 linux/drivers/s390/char/tubio.h - 1.10 linux/drivers/s390/char/tubtty.c - 1.11 linux/net/wanrouter/af_wanpipe.c - 1.17 linux/drivers/s390/net/ctctty.c - 1.9 linux/drivers/block/paride/bpck6.c - 1.7 linux/arch/s390/math-emu/math.c - 1.6 linux/include/asm-ia64/perfmon.h - 1.10 linux/net/ipv4/netfilter/ip_nat_helper.c - 1.11 linux/arch/ia64/kernel/efivars.c - 1.10 linux/include/linux/if_wanpipe.h - 1.5 linux/include/linux/if_wanpipe_common.h - 1.5 linux/fs/freevxfs/vxfs_super.c - 1.14 linux/drivers/net/fealnx.c - 1.20 linux/drivers/net/wireless/airport.c - 1.12 linux/drivers/net/wireless/orinoco_cs.c - 1.16 linux/drivers/media/video/bt856.c - 1.11 linux/drivers/media/video/bt819.c - 1.9 linux/drivers/media/video/adv7175.c - 1.12 linux/fs/char_dev.c - 1.10 linux/arch/ppc/boot/utils/Makefile - 1.6 linux/arch/ppc/boot/prep/Makefile - 1.15 linux/arch/cris/drivers/eeprom.c - 1.11 linux/arch/ppc/boot/images/Makefile - 1.8 linux/include/asm-m68k/raw_io.h - 1.5 linux/include/net/bluetooth/l2cap.h - 1.7 linux/drivers/bluetooth/hci_usb.c - 1.22 linux/net/bluetooth/af_bluetooth.c - 1.15 linux/drivers/mtd/nftlcore.c - 1.32 linux/drivers/mtd/maps/sa1100-flash.c - 1.9 linux/drivers/mtd/chips/sharp.c - 1.6 linux/drivers/mtd/chips/jedec.c - 1.8 linux/drivers/mtd/chips/chipreg.c - 1.4 linux/drivers/mtd/chips/cfi_cmdset_0002.c - 1.5 linux/drivers/mtd/chips/cfi_cmdset_0001.c - 1.4 linux/drivers/media/radio/miropcm20-rds.c - 1.8 linux/drivers/acpi/utilities/utxface.c - 1.12 linux/drivers/acpi/utilities/utobject.c - 1.13 linux/drivers/acpi/utilities/utmisc.c - 1.18 linux/drivers/acpi/utilities/utglobal.c - 1.21 linux/drivers/acpi/utilities/uteval.c - 1.14 linux/drivers/acpi/utilities/utdelete.c - 1.15 linux/drivers/acpi/utilities/utcopy.c - 1.18 linux/drivers/net/wireless/airo.c - 1.29 linux/drivers/acpi/executer/exconfig.c - 1.14 linux/drivers/acpi/executer/exdump.c - 1.18 linux/drivers/usb/serial/cyberjack.c - 1.24 linux/drivers/usb/serial/pl2303.c - 1.31 linux/drivers/isdn/tpam/tpam_main.c - 1.10 linux/fs/sysv/super.c - 1.15 linux/drivers/net/irda/ali-ircc.c - 1.17 linux/drivers/net/sk98lin/skproc.c - 1.8 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.20 linux/drivers/media/video/zr36067.c - 1.14 linux/drivers/net/au1000_eth.c - 1.11 linux/drivers/usb/usb-skeleton.c - 1.26 linux/drivers/char/ser_a2232.c - 1.9 linux/drivers/net/dl2k.c - 1.22 linux/drivers/message/fusion/mptscsih.h - 1.12 linux/drivers/message/fusion/mptscsih.c - 1.18 linux/drivers/message/fusion/mptctl.c - 1.15 linux/drivers/ieee1394/sbp2.c - 1.23 linux/drivers/ieee1394/sbp2.h - 1.15 linux/drivers/video/aty/atyfb_base.c - 1.21 linux/drivers/char/drm/radeon.h - 1.9 linux/drivers/char/drm/drm_vm.h - 1.19 linux/drivers/char/drm/drm_proc.h - 1.8 linux/drivers/char/drm/drm_memory.h - 1.5 linux/drivers/char/drm/drm_lists.h - 1.5 linux/drivers/char/drm/drm_drv.h - 1.14 linux/drivers/char/drm/drm_bufs.h - 1.8 linux/drivers/char/drm/drm_agpsupport.h - 1.14 linux/include/asm-arm/arch-anakin/time.h - 1.5 linux/arch/ppc/mm/cachemap.c - 1.7 linux/arch/ppc/kernel/l2cr.S - 1.8 linux/drivers/video/sstfb.c - 1.16 linux/drivers/video/radeonfb.c - 1.17 linux/drivers/scsi/dpti.h - 1.7 linux/drivers/scsi/dpt_i2o.c - 1.22 linux/drivers/char/serial_tx3912.c - 1.11 linux/arch/mips/au1000/common/serial.c - 1.11 linux/drivers/isdn/hisax/st5481_init.c - 1.8 linux/drivers/net/ns83820.c - 1.20 linux/drivers/scsi/NCR_D700.c - 1.7 linux/drivers/scsi/NCR_D700.h - 1.3 linux/drivers/scsi/lasi700.c - 1.8 linux/drivers/scsi/lasi700.h - 1.5 linux/fs/jffs2/malloc.c - 1.6 linux/fs/jffs2/super.c - 1.16 linux/include/asm-generic/tlb.h - 1.13 linux/include/asm-arm/tlb.h - 1.8 linux/drivers/char/mwave/mwavedd.h - 1.4 linux/fs/namespace.c - 1.29 linux/drivers/usb/serial/ir-usb.c - 1.27 linux/drivers/message/i2o/i2o_core.c - 1.13 linux/Documentation/video4linux/bttv/Cards - 1.6 linux/drivers/net/8139cp.c - 1.25 linux/drivers/atm/lanai.c - 1.9 linux/drivers/net/irda/sa1100_ir.c - 1.8 linux/drivers/pcmcia/i82092.c - 1.13 linux/include/asm-arm/arch-epxa10db/time.h - 1.5 linux/net/ipv6/netfilter/ip6t_LOG.c - 1.6 linux/net/ipv4/netfilter/ipt_ttl.c - 1.3 linux/net/ipv4/netfilter/ipt_length.c - 1.3 linux/net/ipv4/netfilter/ip_nat_snmp_basic.c - 1.8 linux/net/ipv4/netfilter/ip_nat_irc.c - 1.5 linux/net/ipv4/netfilter/ip_conntrack_irc.c - 1.9 linux/net/8021q/vlanproc.c - 1.9 linux/net/8021q/vlan.c - 1.11 linux/include/linux/if_vlan.h - 1.5 linux/drivers/char/i8k.c - 1.6 linux/drivers/atm/idt77252.c - 1.11 linux/drivers/scsi/sym53c8xx_2/sym53c8xx.h - 1.8 linux/drivers/scsi/sym53c8xx_2/sym_glue.c - 1.15 linux/net/atm/pppoatm.c - 1.6 linux/fs/ext3/fsync.c - 1.6 linux/fs/ext3/namei.c - 1.20 linux/fs/ext3/super.c - 1.36 linux/drivers/hotplug/pci_hotplug_core.c - 1.20 linux/drivers/hotplug/cpqphp_pci.c - 1.11 linux/drivers/hotplug/cpqphp_ctrl.c - 1.9 linux/drivers/hotplug/cpqphp_core.c - 1.14 linux/drivers/hotplug/cpqphp.h - 1.7 linux/include/linux/seq_file.h - 1.5 linux/fs/intermezzo/methods.c - 1.10 linux/fs/intermezzo/super.c - 1.13 linux/fs/intermezzo/sysctl.c - 1.9 linux/fs/intermezzo/vfs.c - 1.15 linux/include/linux/ext3_fs.h - 1.17 linux/fs/reiserfs/procfs.c - 1.13 linux/fs/seq_file.c - 1.10 linux/fs/ext3/dir.c - 1.11 linux/fs/ext3/Makefile - 1.9 linux/include/linux/bio.h - 1.21 linux/drivers/isdn/hisax/hisax_fcpcipnp.c - 1.15 linux/fs/bio.c - 1.30 linux/include/linux/device.h - 1.32 linux/init/do_mounts.c - 1.28 linux/include/linux/namespace.h - 1.5 linux/include/asm-arm/arch-clps711x/time.h - 1.3 linux/arch/arm/mach-footbridge/dc21285.c - 1.6 linux/arch/arm/mach-rpc/dma.c - 1.6 linux/drivers/block/cciss_scsi.c - 1.11 linux/drivers/block/cciss_scsi.h - 1.3 linux/include/linux/init_task.h - 1.19 linux/net/ipv4/tcp_diag.c - 1.6 linux/drivers/ieee1394/dv1394.c - 1.16 linux/net/core/wireless.c - 1.8 linux/drivers/net/wireless/netwave_cs.c - 1.8 linux/drivers/net/wireless/wavelan.c - 1.7 linux/drivers/net/wireless/wavelan.p.h - 1.6 linux/drivers/net/wireless/wavelan_cs.c - 1.10 linux/drivers/isdn/hisax/hisax_fcclassic.c - 1.5 linux/drivers/net/wireless/wavelan_cs.p.h - 1.6 linux/include/net/iw_handler.h - 1.6 linux/net/ipv4/netfilter/ipt_esp.c - 1.6 linux/net/ipv4/netfilter/ipt_ah.c - 1.6 linux/net/ipv4/netfilter/ipt_ULOG.c - 1.8 linux/drivers/base/core.c - 1.26 linux/drivers/base/Makefile - 1.14 linux/drivers/pci/pci-driver.c - 1.14 linux/fs/xattr.c - 1.14 linux/drivers/input/joystick/amijoy.c - 1.7 linux/Documentation/filesystems/porting - 1.15 linux/sound/sound_core.c - 1.10 linux/arch/ppc/8xx_io/cs4218_tdm.c - 1.6 linux/sound/pci/emu10k1/emufx.c - 1.15 linux/arch/ppc/boot/common/dummy.c - 1.3 linux/arch/ppc/boot/simple/Makefile - 1.14 linux/sound/oss/soundcard.c - 1.9 linux/sound/oss/sonicvibes.c - 1.9 linux/sound/oss/sequencer.c - 1.5 linux/sound/oss/opl3sa2.c - 1.11 linux/sound/oss/msnd_pinnacle.c - 1.6 linux/sound/oss/maestro.c - 1.12 linux/sound/oss/i810_audio.c - 1.13 linux/sound/oss/gus_wave.c - 1.7 linux/sound/oss/esssolo1.c - 1.11 linux/sound/oss/es1370.c - 1.11 linux/sound/oss/emu10k1/mixer.c - 1.4 linux/sound/oss/dmasound/dmasound_q40.c - 1.6 linux/sound/oss/dmasound/dmasound_paula.c - 1.5 linux/sound/oss/dmasound/dmasound_core.c - 1.6 linux/sound/oss/dmasound/dmasound_atari.c - 1.6 linux/sound/oss/dmasound/dmasound.h - 1.3 linux/arch/ppc/platforms/apus_setup.c - 1.8 linux/arch/ppc/platforms/zx4500_setup.c - 1.7 linux/sound/oss/dev_table.c - 1.2 linux/sound/oss/cs46xx.c - 1.11 linux/sound/oss/cs4281/cs4281pm-24.c - 1.3 linux/sound/oss/cs4281/cs4281m.c - 1.8 linux/sound/oss/cmpci.c - 1.8 linux/sound/oss/btaudio.c - 1.7 linux/arch/x86_64/Makefile - 1.18 linux/arch/x86_64/defconfig - 1.16 linux/arch/x86_64/ia32/Makefile - 1.12 linux/arch/x86_64/ia32/ia32_binfmt.c - 1.11 linux/arch/x86_64/ia32/ia32_ioctl.c - 1.18 linux/arch/x86_64/ia32/ia32_signal.c - 1.13 linux/arch/x86_64/ia32/ia32entry.S - 1.14 linux/arch/x86_64/ia32/ptrace32.c - 1.7 linux/arch/x86_64/ia32/sys_ia32.c - 1.21 linux/arch/x86_64/kernel/Makefile - 1.18 linux/arch/x86_64/kernel/apic.c - 1.15 linux/arch/x86_64/kernel/bluesmoke.c - 1.9 linux/arch/x86_64/kernel/early_printk.c - 1.8 linux/arch/x86_64/kernel/entry.S - 1.12 linux/arch/x86_64/kernel/head.S - 1.11 linux/arch/x86_64/kernel/io_apic.c - 1.8 linux/arch/x86_64/kernel/ioport.c - 1.6 linux/arch/x86_64/kernel/irq.c - 1.13 linux/arch/x86_64/kernel/ldt.c - 1.9 linux/arch/x86_64/kernel/mpparse.c - 1.9 linux/arch/x86_64/kernel/pci-dma.c - 1.6 linux/arch/x86_64/kernel/process.c - 1.18 linux/arch/x86_64/kernel/ptrace.c - 1.12 linux/arch/x86_64/kernel/setup.c - 1.12 linux/arch/x86_64/kernel/setup64.c - 1.13 linux/arch/x86_64/kernel/signal.c - 1.14 linux/arch/x86_64/kernel/smpboot.c - 1.15 linux/arch/x86_64/kernel/sys_x86_64.c - 1.8 linux/arch/x86_64/kernel/traps.c - 1.16 linux/arch/x86_64/kernel/x8664_ksyms.c - 1.12 linux/arch/x86_64/mm/fault.c - 1.11 linux/arch/x86_64/mm/init.c - 1.14 linux/arch/x86_64/mm/ioremap.c - 1.10 linux/sound/oss/ac97_codec.c - 1.7 linux/sound/isa/sb/sb_mixer.c - 1.7 linux/sound/isa/sb/sb16_csp.c - 1.8 linux/sound/isa/ad1848/ad1848_lib.c - 1.11 linux/sound/i2c/i2c.c - 1.5 linux/sound/drivers/opl3/opl3_oss.c - 1.6 linux/sound/core/timer.c - 1.14 linux/sound/core/sound.c - 1.17 linux/sound/core/seq/seq_queue.c - 1.10 linux/sound/core/seq/seq_ports.c - 1.9 linux/sound/core/seq/seq_instr.c - 1.5 linux/sound/core/seq/seq_device.c - 1.8 linux/sound/core/seq/seq_clientmgr.c - 1.12 linux/sound/core/seq/oss/seq_oss_timer.h - 1.2 linux/sound/core/seq/oss/seq_oss_timer.c - 1.3 linux/sound/core/seq/oss/seq_oss_synth.c - 1.8 linux/sound/core/seq/oss/seq_oss_rw.c - 1.3 linux/sound/core/seq/oss/seq_oss_midi.c - 1.9 linux/sound/core/seq/oss/seq_oss_ioctl.c - 1.3 linux/sound/core/seq/oss/seq_oss_device.h - 1.3 linux/sound/core/rawmidi.c - 1.15 linux/sound/core/pcm_native.c - 1.17 linux/sound/core/pcm.c - 1.10 linux/sound/core/oss/mixer_oss.c - 1.9 linux/sound/core/init.c - 1.11 linux/sound/core/info.c - 1.15 linux/sound/core/hwdep.c - 1.8 linux/sound/core/control.c - 1.12 linux/sound/Makefile - 1.14 linux/include/asm-x86_64/segment.h - 1.8 linux/include/asm-x86_64/processor.h - 1.15 linux/include/asm-x86_64/pgtable.h - 1.16 linux/include/asm-x86_64/pda.h - 1.9 linux/include/asm-x86_64/pci.h - 1.7 linux/include/asm-x86_64/page.h - 1.10 linux/include/asm-x86_64/irq.h - 1.3 linux/include/asm-x86_64/io.h - 1.7 linux/include/asm-x86_64/ia32.h - 1.10 linux/include/asm-x86_64/i387.h - 1.9 linux/include/asm-x86_64/hardirq.h - 1.4 linux/include/asm-x86_64/floppy.h - 1.3 linux/include/asm-x86_64/elf.h - 1.6 linux/include/asm-x86_64/e820.h - 1.5 linux/include/asm-x86_64/debugreg.h - 1.3 linux/include/asm-x86_64/calling.h - 1.5 linux/include/asm-x86_64/apic.h - 1.6 linux/include/sound/trident.h - 1.8 linux/include/sound/seq_kernel.h - 1.6 linux/include/asm-x86_64/system.h - 1.13 linux/include/asm-x86_64/user.h - 1.5 linux/include/asm-x86_64/thread_info.h - 1.9 linux/arch/ppc64/mm/fault.c - 1.8 linux/arch/ppc64/mm/init.c - 1.15 linux/include/asm-ppc64/elf.h - 1.8 linux/include/asm-ppc64/io.h - 1.5 linux/arch/ppc64/boot/addnote.c - 1.2 linux/arch/ppc64/kernel/LparData.c - 1.7 linux/arch/ppc64/kernel/Makefile - 1.17 linux/arch/ppc64/kernel/align.c - 1.7 linux/arch/ppc64/kernel/chrp_setup.c - 1.14 linux/arch/ppc64/kernel/entry.S - 1.17 linux/arch/ppc64/kernel/head.S - 1.13 linux/arch/ppc64/kernel/htab.c - 1.12 linux/arch/ppc64/kernel/iSeries_setup.c - 1.10 linux/arch/ppc64/kernel/ioctl32.c - 1.19 linux/arch/ppc64/kernel/irq.c - 1.11 linux/arch/ppc64/kernel/misc.S - 1.20 linux/arch/ppc64/kernel/open_pic.c - 1.9 linux/arch/ppc64/kernel/open_pic_defs.h - 1.2 linux/arch/ppc64/kernel/pSeries_lpar.c - 1.12 linux/arch/ppc64/kernel/pacaData.c - 1.5 linux/arch/ppc64/kernel/pci.c - 1.13 linux/arch/ppc64/kernel/pci_dma.c - 1.9 linux/arch/ppc64/kernel/process.c - 1.16 linux/arch/ppc64/kernel/prom.c - 1.14 linux/arch/ppc64/kernel/ras.c - 1.4 linux/arch/ppc64/kernel/rtas-proc.c - 1.5 linux/arch/ppc64/kernel/rtas.c - 1.7 linux/arch/ppc64/kernel/setup.c - 1.12 linux/arch/ppc64/kernel/signal.c - 1.15 linux/arch/ppc64/kernel/signal32.c - 1.16 linux/arch/ppc64/kernel/smp.c - 1.18 linux/arch/ppc64/kernel/sys_ppc32.c - 1.22 linux/arch/ppc64/kernel/syscalls.c - 1.8 linux/arch/ppc64/kernel/traps.c - 1.13 linux/arch/ppc64/kernel/udbg.c - 1.6 linux/arch/ppc64/kernel/xics.c - 1.11 linux/include/asm-ppc64/ucontext.h - 1.3 linux/arch/ppc64/xmon/xmon.c - 1.12 linux/include/asm-ppc64/mmu.h - 1.6 linux/include/asm-ppc64/module.h - 1.3 linux/include/asm-ppc64/unistd.h - 1.15 linux/include/asm-ppc64/types.h - 1.3 linux/include/asm-ppc64/signal.h - 1.5 linux/include/asm-ppc64/sigcontext.h - 1.3 linux/include/asm-ppc64/rtas.h - 1.6 linux/include/asm-ppc64/ptrace.h - 1.2 linux/include/asm-ppc64/processor.h - 1.15 linux/include/asm-ppc64/proc_fs.h - 1.2 linux/include/asm-ppc64/pgtable.h - 1.12 linux/include/asm-ppc64/page.h - 1.13 linux/drivers/net/e1000/e1000_main.c - 1.20 linux/drivers/net/e1000/Makefile - 1.8 linux/drivers/net/e1000/e1000.h - 1.13 linux/drivers/net/e1000/e1000_ethtool.c - 1.10 linux/drivers/isdn/hisax/hisax_hfcpci.c - 1.7 linux/drivers/hotplug/ibmphp_core.c - 1.13 linux/fs/jfs/super.c - 1.22 linux/Documentation/networking/generic-hdlc.txt - 1.3 linux/drivers/net/tg3.c - 1.21 linux/drivers/net/tulip/de2104x.c - 1.9 linux/drivers/net/tulip/de4x5.c - 1.13 linux/drivers/net/tulip/dmfe.c - 1.8 linux/drivers/net/tulip/winbond-840.c - 1.12 linux/drivers/net/tulip/xircom_cb.c - 1.8 linux/drivers/net/tulip/xircom_tulip_cb.c - 1.6 linux/drivers/net/e100/e100.h - 1.15 linux/drivers/net/e100/e100_phy.c - 1.7 linux/drivers/net/e100/e100_main.c - 1.20 linux/include/linux/futex.h - 1.7 linux/kernel/futex.c - 1.17 linux/arch/ia64/sn/kernel/machvec.c - 1.3 linux/mm/mincore.c - 1.4 linux/include/asm-ia64/machvec_sn2.h - 1.6 linux/arch/ia64/kernel/salinfo.c - 1.3 linux/arch/ia64/sn/io/sn2/pcibr/pcibr_slot.c - 1.4 linux/arch/ia64/sn/io/sn1/ml_SN_intr.c - 1.4 linux/fs/nfsctl.c - 1.8 linux/Documentation/BK-usage/bk-kernel-howto.txt - 1.5 linux/Documentation/networking/NAPI_HOWTO.txt - 1.5 linux/net/ipv4/netfilter/arp_tables.c - 1.6 linux/drivers/media/video/video-buf.c - 1.9 linux/drivers/net/wan/comx-hw-munich.c - 1.11 linux/fs/libfs.c - 1.14 linux/drivers/ieee1394/eth1394.c - 1.9 linux/drivers/ide/ide-tcq.c - 1.6 linux/drivers/net/e1000/e1000_hw.h - 1.7 linux/drivers/usb/class/bluetty.c - 1.18 linux/drivers/usb/class/cdc-acm.c - 1.19 linux/drivers/usb/core/hcd.c - 1.22 linux/drivers/usb/core/hub.c - 1.25 linux/drivers/usb/core/inode.c - 1.14 linux/include/asm-arm/arch-pxa/time.h - 1.5 linux/drivers/usb/input/hid-core.c - 1.20 linux/include/asm-arm/arch-pxa/irqs.h - 1.3 linux/drivers/usb/media/dabusb.h - 1.3 linux/drivers/usb/core/usb.c - 1.33 linux/arch/arm/mach-pxa/irq.c - 1.6 linux/arch/arm/mach-pxa/lubbock.c - 1.8 linux/drivers/usb/host/ehci-hcd.c - 1.21 linux/drivers/usb/host/ehci-q.c - 1.19 linux/drivers/usb/host/ehci.h - 1.12 linux/drivers/usb/host/ohci-hcd.c - 1.21 linux/drivers/base/sys.c - 1.10 linux/drivers/base/base.h - 1.17 linux/drivers/net/e1000/e1000_hw.c - 1.7 linux/drivers/usb/image/mdc800.c - 1.15 linux/drivers/usb/image/scanner.c - 1.23 linux/drivers/usb/image/scanner.h - 1.16 linux/drivers/ieee1394/amdtp.c - 1.10 linux/drivers/usb/input/hid-input.c - 1.9 linux/drivers/usb/input/hiddev.c - 1.15 linux/drivers/usb/input/usbkbd.c - 1.13 linux/drivers/usb/media/dabusb.c - 1.13 linux/drivers/usb/media/ov511.c - 1.14 linux/drivers/net/e100/e100_test.c - 1.8 linux/drivers/usb/media/se401.c - 1.15 linux/drivers/usb/net/usbnet.c - 1.20 linux/drivers/usb/net/rtl8150.c - 1.15 linux/drivers/usb/net/pegasus.c - 1.15 linux/drivers/usb/media/vicam.c - 1.13 linux/drivers/usb/net/kaweth.c - 1.16 linux/drivers/usb/net/catc.c - 1.8 linux/drivers/usb/misc/uss720.c - 1.7 linux/drivers/usb/misc/auerswald.c - 1.17 linux/drivers/usb/misc/rio500.c - 1.11 linux/drivers/usb/misc/tiglusb.c - 1.13 linux/include/asm-ia64/percpu.h - 1.5 linux/include/asm-ia64/machvec_hpzx1.h - 1.6 linux/drivers/isdn/i4l/isdn_x25iface.c - 1.3 linux/drivers/isdn/i4l/isdn_ppp.c - 1.14 linux/drivers/isdn/i4l/isdn_common.c - 1.13 linux/arch/ia64/hp/zx1/hpzx1_misc.c - 1.9 linux/arch/ia64/hp/zx1/hpzx1_machvec.c - 1.3 linux/arch/ia64/hp/zx1/Makefile - 1.5 linux/arch/ia64/hp/sim/hpsim_machvec.c - 1.2 linux/arch/ia64/hp/sim/hpsim_console.c - 1.4 linux/arch/ia64/hp/sim/simserial.c - 1.11 linux/arch/ia64/hp/sim/simscsi.h - 1.6 linux/arch/ia64/hp/sim/simscsi.c - 1.10 linux/arch/ia64/hp/sim/simeth.c - 1.5 linux/arch/ia64/hp/common/sba_iommu.c - 1.9 linux/drivers/isdn/hardware/avm/avm_cs.c - 1.4 linux/drivers/usb/misc/brlvger.c - 1.14 linux/drivers/isdn/hardware/avm/t1pci.c - 1.6 linux/drivers/isdn/hardware/avm/t1isa.c - 1.5 linux/drivers/isdn/hardware/avm/c4.c - 1.7 linux/drivers/isdn/hardware/avm/b1pcmcia.c - 1.4 linux/include/linux/brlvger.h - 1.3 linux/drivers/isdn/hardware/avm/b1pci.c - 1.7 linux/drivers/isdn/hardware/avm/b1isa.c - 1.4 linux/drivers/isdn/hardware/avm/b1dma.c - 1.5 linux/drivers/isdn/hardware/avm/b1.c - 1.5 linux/drivers/isdn/capi/capi.c - 1.10 linux/drivers/isdn/capi/kcapi.c - 1.6 linux/drivers/isdn/capi/capifs.c - 1.7 linux/drivers/scsi/aic7xxx/aic7xxx_core.c - 1.10 linux/drivers/char/pcmcia/synclink_cs.c - 1.12 linux/Documentation/networking/3c509.txt - 1.3 linux/drivers/usb/host/uhci-hcd.c - 1.20 linux/drivers/usb/host/uhci-hcd.h - 1.6 linux/drivers/macintosh/apm_emu.c - 1.6 linux/net/ipv6/ipv6_syms.c - 1.10 linux/drivers/pci/hotplug.c - 1.11 linux/drivers/pci/pool.c - 1.8 linux/drivers/pci/probe.c - 1.15 linux/fs/fs-writeback.c - 1.16 linux/net/bluetooth/sco.c - 1.10 linux/net/bluetooth/l2cap.c - 1.11 linux/drivers/bluetooth/hci_ldisc.c - 1.8 linux/mm/page-writeback.c - 1.24 linux/include/asm-ppc64/naca.h - 1.3 linux/include/asm-i386/suspend.h - 1.6 linux/kernel/suspend.c - 1.24 linux/drivers/base/bus.c - 1.17 linux/drivers/char/drm/i830_dma.c - 1.11 linux/drivers/video/pm3fb.c - 1.7 linux/drivers/acorn/scsi/scsi.h - 1.6 linux/drivers/char/hvc_console.c - 1.11 linux/drivers/usb/core/message.c - 1.19 linux/drivers/acpi/osl.c - 1.18 linux/include/asm-s390/tlbflush.h - 1.6 linux/drivers/usb/host/ohci-sa1111.c - 1.14 linux/drivers/usb/class/usb-midi.c - 1.13 linux/drivers/s390/cio/blacklist.c - 1.4 linux/scripts/fixdep.c - 1.8 linux/drivers/s390/net/lcs.c - 1.13 linux/drivers/s390/cio/chsc.c - 1.8 linux/drivers/usb/core/hcd-pci.c - 1.10 linux/arch/i386/kernel/suspend.c - 1.12 linux/drivers/s390/cio/cio.c - 1.7 linux/drivers/s390/block/dasd_ioctl.c - 1.11 linux/arch/x86_64/lib/copy_user.S - 1.4 linux/arch/x86_64/pci/irq.c - 1.6 linux/include/asm-x86_64/suspend.h - 1.5 linux/arch/arm/kernel/asm-offsets.c - 1.3 linux/arch/x86_64/kernel/asm-offsets.c - 1.3 linux/drivers/isdn/hisax/avma1_cs.c - 1.4 linux/drivers/input/tsdev.c - 1.8 linux/drivers/input/serio/rpckbd.c - 1.7 linux/drivers/input/serio/i8042.c - 1.13 linux/drivers/input/mouse/rpcmouse.c - 1.9 linux/drivers/input/mouse/amimouse.c - 1.7 linux/drivers/input/keyboard/amikbd.c - 1.10 linux/drivers/usb/core/file.c - 1.6 linux/drivers/acpi/toshiba_acpi.c - 1.8 linux/drivers/acpi/tables/tbgetall.c - 1.10 linux/drivers/usb/input/pid.c - 1.6 linux/drivers/usb/input/xpad.c - 1.10 linux/drivers/usb/input/hid-lgff.c - 1.4 linux/drivers/input/serio/sa1111ps2.c - 1.6 linux/security/dummy.c - 1.10 linux/drivers/usb/serial/io_ti.c - 1.11 linux/drivers/serial/sa1100.c - 1.10 linux/drivers/serial/core.c - 1.13 linux/drivers/input/serio/ambakmi.c - 1.4 linux/drivers/char/agp/ali-agp.c - 1.8 linux/drivers/char/agp/sis-agp.c - 1.8 linux/drivers/char/agp/frontend.c - 1.8 linux/drivers/char/agp/hp-agp.c - 1.8 linux/drivers/char/agp/i460-agp.c - 1.8 linux/drivers/acpi/namespace/nsxfeval.c - 1.10 linux/drivers/serial/amba.c - 1.12 linux/drivers/acpi/namespace/nsdumpdv.c - 1.8 linux/include/asm-generic/rmap.h - 1.4 linux/drivers/char/agp/sworks-agp.c - 1.7 linux/drivers/char/agp/via-agp.c - 1.9 linux/include/asm-ppc64/mmzone.h - 1.7 linux/arch/i386/mm/pgtable.c - 1.9 linux/drivers/serial/21285.c - 1.11 linux/include/linux/security.h - 1.9 linux/arch/ppc64/kernel/rtas_flash.c - 1.5 linux/Documentation/vm/overcommit-accounting - 1.4 linux/drivers/usb/class/usblp.c - 1.9 linux/drivers/usb/misc/usblcd.c - 1.6 linux/drivers/input/misc/uinput.c - 1.5 linux/net/ipv4/netfilter/ipt_DSCP.c - 1.3 linux/net/ipv4/netfilter/ipt_ECN.c - 1.5 linux/arch/ia64/kernel/perfmon_mckinley.h - 1.4 linux/net/ipv4/netfilter/ipt_pkttype.c - 1.3 linux/net/ipv4/netfilter/ipt_helper.c - 1.4 linux/arch/i386/kernel/cpu/mtrr/if.c - 1.4 linux/net/ipv4/netfilter/ipt_ecn.c - 1.3 linux/net/ipv4/netfilter/ipt_dscp.c - 1.3 linux/net/ipv4/netfilter/ipt_conntrack.c - 1.5 linux/include/linux/aio.h - 1.6 linux/drivers/base/class.c - 1.11 linux/include/net/sctp/user.h - 1.5 linux/net/sctp/ulpevent.c - 1.7 linux/net/sctp/protocol.c - 1.17 linux/net/sctp/Makefile - 1.6 linux/include/net/sctp/sctp.h - 1.13 linux/net/sctp/adler32.c - 1.5 linux/net/sctp/associola.c - 1.13 linux/net/sctp/bind_addr.c - 1.9 linux/net/sctp/command.c - 1.4 linux/net/sctp/crc32c.c - 1.3 linux/net/sctp/endpointola.c - 1.9 linux/net/sctp/input.c - 1.13 linux/net/sctp/inqueue.c - 1.4 linux/net/sctp/ipv6.c - 1.15 linux/net/sctp/objcnt.c - 1.3 linux/net/sctp/output.c - 1.10 linux/include/net/sctp/ulpqueue.h - 1.5 linux/net/sctp/outqueue.c - 1.12 linux/net/sctp/primitive.c - 1.6 linux/include/net/sctp/ulpevent.h - 1.4 linux/include/asm-ia64/kmap_types.h - 1.4 linux/include/net/sctp/constants.h - 1.6 linux/net/sctp/tsnmap.c - 1.4 linux/include/net/sctp/sm.h - 1.11 linux/net/sctp/sm_make_chunk.c - 1.14 linux/include/net/sctp/command.h - 1.6 linux/net/sctp/sm_sideeffect.c - 1.15 linux/net/sctp/sm_statefuns.c - 1.14 linux/include/net/sctp/tsnmap.h - 1.3 linux/include/net/sctp/structs.h - 1.14 linux/include/linux/efi.h - 1.2 linux/net/sctp/socket.c - 1.15 linux/net/sctp/transport.c - 1.9 linux/net/sctp/ulpqueue.c - 1.8 linux/include/asm-alpha/kmap_types.h - 1.4 linux/include/asm-i386/mmzone.h - 1.8 linux/drivers/ide/ppc/pmac.c - 1.8 linux/drivers/ide/pci/via82cxxx.c - 1.9 linux/drivers/ide/pci/sis5513.c - 1.10 linux/drivers/ide/pci/serverworks.h - 1.5 linux/drivers/ide/pci/serverworks.c - 1.10 linux/drivers/ide/pci/piix.h - 1.6 linux/drivers/ide/pci/piix.c - 1.9 linux/drivers/ide/pci/hpt366.c - 1.11 linux/drivers/ide/pci/amd74xx.h - 1.7 linux/drivers/ide/pci/amd74xx.c - 1.13 linux/drivers/ide/legacy/umc8672.c - 1.5 linux/drivers/ide/legacy/qd65xx.c - 1.4 linux/drivers/ide/legacy/q40ide.c - 1.3 linux/drivers/ide/legacy/pdc4030.c - 1.7 linux/drivers/ide/legacy/ht6560b.c - 1.4 linux/drivers/ide/legacy/dtc2278.c - 1.4 linux/drivers/ide/legacy/ali14xx.c - 1.4 linux/arch/um/drivers/line.c - 1.8 linux/arch/um/drivers/mmapper_kern.c - 1.5 linux/arch/um/kernel/irq.c - 1.7 linux/arch/um/kernel/mem.c - 1.10 linux/arch/um/kernel/sys_call_table.c - 1.6 linux/arch/um/kernel/umid.c - 1.5 linux/arch/um/os-Linux/drivers/tuntap_user.c - 1.3 linux/drivers/ide/ide-iops.c - 1.9 linux/include/asm-um/pgtable.h - 1.8 linux/drivers/ide/arm/icside.c - 1.5 linux/drivers/ide/arm/rapide.c - 1.4 linux/drivers/char/vt_ioctl.c - 1.5 linux/arch/x86_64/vmlinux.lds.S - 1.10 linux/arch/s390/vmlinux.lds.S - 1.11 linux/arch/i386/mm/hugetlbpage.c - 1.14 linux/Documentation/driver-model/binding.txt - 1.3 linux/Documentation/driver-model/bus.txt - 1.4 linux/Documentation/driver-model/class.txt - 1.3 linux/Documentation/driver-model/device.txt - 1.3 linux/Documentation/driver-model/driver.txt - 1.5 linux/Documentation/driver-model/interface.txt - 1.3 linux/Documentation/driver-model/overview.txt - 1.5 linux/Documentation/driver-model/platform.txt - 1.3 linux/include/asm-i386/numnodes.h - 1.3 linux/kernel/pid.c - 1.5 linux/net/bridge/netfilter/ebtables.c - 1.9 linux/net/bridge/netfilter/ebtable_nat.c - 1.6 linux/net/bridge/netfilter/ebtable_filter.c - 1.6 linux/net/bridge/netfilter/ebt_vlan.c - 1.5 linux/arch/i386/kernel/reboot.c - 1.5 linux/arch/ppc64/kernel/asm-offsets.c - 1.3 linux/net/bridge/netfilter/ebt_log.c - 1.4 linux/net/bridge/netfilter/ebt_ip.c - 1.5 linux/arch/i386/mach-generic/Makefile - 1.6 linux/net/bridge/netfilter/ebt_arp.c - 1.4 linux/drivers/acpi/scan.c - 1.7 linux/arch/ppc64/mm/numa.c - 1.3 linux/arch/ppc/boot/openfirmware/Makefile - 1.7 linux/arch/ia64/pci/pci.c - 1.6 linux/arch/ia64/mm/hugetlbpage.c - 1.8 linux/drivers/block/deadline-iosched.c - 1.9 linux/include/linux/cpu.h - 1.4 linux/include/asm-ppc64/topology.h - 1.6 linux/kernel/cpufreq.c - 1.13 linux/include/linux/cpufreq.h - 1.13 linux/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c - 1.11 linux/arch/i386/kernel/cpu/cpufreq/longhaul.c - 1.11 linux/sound/usb/usbmixer.c - 1.6 linux/sound/usb/usbaudio.c - 1.11 linux/mm/truncate.c - 1.6 linux/net/x25/x25_proc.c - 1.2 linux/net/llc/llc_proc.c - 1.6 linux/net/ipx/ipx_proc.c - 1.3 linux/drivers/usb/serial/console.c - 1.3 linux/drivers/usb/misc/usbtest.c - 1.11 linux/drivers/scsi/nsp32.c - 1.8 linux/drivers/scsi/aacraid/sa.c - 1.3 linux/drivers/scsi/aacraid/linit.c - 1.11 linux/drivers/scsi/aacraid/dpcsup.c - 1.2 linux/drivers/scsi/aacraid/commsup.c - 1.4 linux/drivers/scsi/aacraid/comminit.c - 1.3 linux/drivers/scsi/aacraid/commctrl.c - 1.2 linux/drivers/scsi/aacraid/aacraid.h - 1.5 linux/drivers/scsi/aacraid/aachba.c - 1.8 linux/drivers/scsi/aacraid/README - 1.2 linux/drivers/isdn/i4l/isdn_net_lib.c - 1.7 linux/net/bluetooth/rfcomm/tty.c - 1.8 linux/net/bluetooth/rfcomm/sock.c - 1.9 linux/net/bluetooth/rfcomm/core.c - 1.10 linux/net/bluetooth/bnep/sock.c - 1.6 linux/net/bluetooth/bnep/core.c - 1.9 linux/include/net/bluetooth/rfcomm.h - 1.6 linux/net/appletalk/atalk_proc.c - 1.3 linux/drivers/net/irda/donauboe.c - 1.5 linux/fs/cifs/TODO - 1.5 linux/fs/cifs/cifs_debug.c - 1.9 linux/fs/cifs/cifs_fs_sb.h - 1.3 linux/fs/cifs/cifsfs.c - 1.9 linux/fs/nfsd/nfs4xdr.c - 1.11 linux/fs/cifs/cifsglob.h - 1.6 linux/fs/cifs/cifspdu.h - 1.6 linux/fs/cifs/cifsproto.h - 1.8 linux/fs/cifs/cifssmb.c - 1.10 linux/fs/cifs/connect.c - 1.9 linux/fs/cifs/file.c - 1.9 linux/fs/cifs/inode.c - 1.8 linux/fs/cifs/link.c - 1.5 linux/fs/cifs/md5.c - 1.3 linux/fs/nfsd/nfs4proc.c - 1.7 linux/fs/ext3/hash.c - 1.2 linux/fs/cifs/AUTHORS - 1.3 linux/net/sunrpc/cache.c - 1.6 linux/fs/cifs/CHANGES - 1.8 linux/fs/cifs/transport.c - 1.7 linux/drivers/isdn/hardware/eicon/um_idi.c - 1.3 linux/arch/i386/kernel/timers/Makefile - 1.6 linux/arch/i386/kernel/timers/timer.c - 1.5 linux/drivers/isdn/hardware/eicon/maintidi.c - 1.2 linux/drivers/isdn/hardware/eicon/i4lididrv.c - 1.6 linux/drivers/isdn/hardware/eicon/i4l_idi.c - 1.4 linux/drivers/isdn/hardware/eicon/capifunc.c - 1.4 linux/include/linux/nfsd/xdr4.h - 1.7 linux/drivers/isdn/hardware/eicon/capimain.c - 1.4 linux/drivers/isdn/hardware/eicon/divasfunc.c - 1.3 linux/drivers/isdn/hardware/eicon/divasmain.c - 1.7 linux/drivers/isdn/hardware/eicon/divasi.c - 1.4 linux/drivers/isdn/hardware/eicon/divamnt.c - 1.4 linux/drivers/mtd/cmdline.c - 1.3 linux/fs/nfs/nfs4xdr.c - 1.8 linux/net/rxrpc/proc.c - 1.3 linux/drivers/oprofile/buffer_sync.c - 1.12 linux/drivers/oprofile/cpu_buffer.c - 1.6 linux/drivers/oprofile/oprof.c - 1.6 linux/drivers/oprofile/oprofilefs.c - 1.4 linux/net/rxrpc/krxtimod.c - 1.6 linux/drivers/char/tipar.c - 1.7 linux/fs/afs/kafstimod.c - 1.6 linux/kernel/rcupdate.c - 1.3 linux/arch/i386/oprofile/init.c - 1.6 linux/drivers/block/scsi_ioctl.c - 1.9 linux/arch/x86_64/kernel/pci-gart.c - 1.8 linux/fs/afs/super.c - 1.3 linux/fs/dcookies.c - 1.4 linux/arch/x86_64/kernel/e820.c - 1.5 linux/arch/x86_64/kernel/reboot.c - 1.4 linux/arch/x86_64/kernel/acpi.c - 1.6 linux/include/asm-i386/edd.h - 1.5 linux/arch/x86_64/mm/pageattr.c - 1.5 linux/drivers/pnp/pnpbios/core.c - 1.11 linux/arch/i386/mm/highmem.c - 1.4 linux/drivers/pnp/resource.c - 1.9 linux/drivers/pnp/core.c - 1.8 linux/arch/sparc/kernel/asm-offsets.c - 1.2 linux/include/linux/sysfs.h - 1.8 linux/drivers/pnp/isapnp/core.c - 1.11 linux/include/linux/kobject.h - 1.9 linux/drivers/net/Kconfig - 1.13 linux/Documentation/kobject.txt - 1.5 linux/drivers/net/irda/Kconfig - 1.4 linux/net/decnet/Kconfig - 1.2 linux/scripts/kconfig/menu.c - 1.4 linux/net/ipv4/Kconfig - 1.6 linux/include/linux/eventpoll.h - 1.7 linux/arch/i386/Kconfig - 1.18 linux/net/bridge/br_netfilter.c - 1.6 linux/arch/i386/mach-voyager/voyager_smp.c - 1.7 linux/scripts/kconfig/conf.c - 1.4 linux/arch/ia64/Kconfig - 1.10 linux/drivers/media/dvb/dvb-core/dvbdev.c - 1.6 linux/scripts/Makefile.build - 1.10 linux/include/asm-parisc/kmap_types.h - 1.3 linux/arch/parisc/kernel/ioctl32.c - 1.6 linux/drivers/md/dm-target.c - 1.4 linux/drivers/md/dm-ioctl.c - 1.9 linux/include/linux/pfkeyv2.h - 1.6 linux/drivers/scsi/Kconfig - 1.12 linux/drivers/char/agp/Kconfig - 1.9 linux/arch/ppc/Kconfig - 1.10 linux/drivers/char/drm/Kconfig - 1.5 linux/drivers/hotplug/Kconfig - 1.4 linux/drivers/hotplug/acpiphp_glue.c - 1.8 linux/arch/sparc/Kconfig - 1.11 linux/arch/sparc64/Kconfig - 1.12 linux/drivers/ide/Kconfig - 1.9 linux/fs/befs/linuxvfs.c - 1.8 linux/arch/x86_64/Kconfig - 1.14 linux/fs/Kconfig - 1.13 linux/lib/kobject.c - 1.8 linux/net/sctp/Kconfig - 1.4 linux/crypto/Kconfig - 1.7 linux/crypto/autoload.c - 1.3 linux/crypto/md4.c - 1.2 linux/crypto/md5.c - 1.2 linux/crypto/tcrypt.c - 1.8 linux/net/ipv4/netfilter/ipt_physdev.c - 1.5 linux/net/Kconfig - 1.8 linux/drivers/acorn/net/Kconfig - 1.2 linux/drivers/acorn/scsi/Kconfig - 1.2 linux/net/sched/Kconfig - 1.4 linux/drivers/atm/Kconfig - 1.3 linux/net/ipv6/Kconfig - 1.4 linux/drivers/usb/Kconfig - 1.3 linux/sound/oss/Kconfig - 1.8 linux/drivers/usb/class/Kconfig - 1.6 linux/include/net/xfrm.h - 1.12 linux/init/Kconfig - 1.9 linux/fs/mbcache.c - 1.5 linux/net/bluetooth/hci_proc.c - 1.3 linux/fs/hugetlbfs/inode.c - 1.10 linux/fs/ext3/xattr.h - 1.5 linux/fs/ext3/xattr.c - 1.8 linux/fs/ext2/xattr.h - 1.5 linux/fs/ext2/xattr.c - 1.8 linux/fs/eventpoll.c - 1.9 linux/include/asm-m68knommu/cacheflush.h - 1.4 linux/include/asm-m68knommu/coldfire.h - 1.2 linux/include/asm-m68knommu/hardirq.h - 1.3 linux/mm/fremap.c - 1.8 linux/drivers/scsi/sun3_scsi_vme.c - 1.5 linux/include/asm-m68knommu/mcfdma.h - 1.2 linux/include/asm-m68knommu/mcfsim.h - 1.2 linux/drivers/parisc/led.c - 1.5 linux/drivers/parisc/ccio-dma.c - 1.7 linux/include/linux/hugetlb.h - 1.8 linux/include/asm-m68knommu/mcfuart.h - 1.2 linux/drivers/net/fec.h - 1.2 linux/drivers/net/fec.c - 1.5 linux/drivers/media/video/v4l2-common.c - 1.2 linux/drivers/media/video/saa7134/saa7134.h - 1.5 linux/drivers/media/video/saa7134/saa7134-video.c - 1.7 linux/drivers/media/video/saa7134/saa7134-vbi.c - 1.5 linux/drivers/media/video/saa7134/saa7134-tvaudio.c - 1.6 linux/drivers/media/video/saa7134/saa7134-ts.c - 1.6 linux/drivers/media/video/saa7134/saa7134-reg.h - 1.2 linux/drivers/media/video/saa7134/saa7134-oss.c - 1.5 linux/drivers/media/video/saa7134/saa7134-i2c.c - 1.8 linux/drivers/media/video/saa7134/saa7134-core.c - 1.5 linux/drivers/media/video/saa7134/saa7134-cards.c - 1.5 linux/include/asm-m68knommu/pgtable.h - 1.2 linux/arch/m68knommu/Kconfig - 1.9 linux/arch/m68knommu/Makefile - 1.5 linux/arch/m68knommu/defconfig - 1.2 linux/arch/m68knommu/kernel/setup.c - 1.3 linux/arch/m68knommu/kernel/time.c - 1.4 linux/arch/m68knommu/platform/5206/config.c - 1.3 linux/arch/m68knommu/platform/5206e/config.c - 1.3 linux/arch/m68knommu/platform/5249/MOTOROLA/crt0_ram.S - 1.2 linux/arch/m68knommu/platform/5249/config.c - 1.3 linux/arch/m68knommu/platform/5272/config.c - 1.3 linux/arch/m68knommu/platform/5307/Makefile - 1.4 linux/arch/m68knommu/platform/5307/config.c - 1.3 linux/arch/m68knommu/platform/5407/CLEOPATRA/crt0_ram.S - 1.2 linux/arch/m68knommu/platform/5407/MOTOROLA/crt0_ram.S - 1.2 linux/arch/m68knommu/platform/5407/config.c - 1.3 linux/arch/m68knommu/platform/68328/ints.c - 1.3 linux/arch/m68knommu/platform/68EZ328/config.c - 1.2 linux/arch/m68knommu/platform/68VZ328/de2/config.c - 1.3 linux/arch/m68knommu/platform/68VZ328/de2/crt0_fixed.S - 1.3 linux/arch/m68knommu/platform/68VZ328/de2/crt0_himem.S - 1.2 linux/arch/m68knommu/platform/68VZ328/de2/crt0_ram.S - 1.2 linux/arch/m68knommu/platform/68VZ328/de2/crt0_rom.S - 1.2 linux/arch/m68knommu/vmlinux.lds.S - 1.7 linux/include/asm-v850/hardirq.h - 1.3 linux/drivers/net/irda/irtty-sir.c - 1.5 linux/drivers/net/irda/sir_dongle.c - 1.3 linux/drivers/net/irda/sir_kthread.c - 1.6 linux/drivers/serial/mcfserial.c - 1.7 linux/net/key/af_key.c - 1.11 linux/arch/ppc/syslib/open_pic.c - 1.5 linux/net/core/pktgen.c - 1.4 linux/net/ipv4/esp.c - 1.10 linux/drivers/s390/net/cu3088.c - 1.4 linux/drivers/scsi/scsi_sysfs.c - 1.9 linux/arch/i386/kernel/suspend_asm.S - 1.3 linux/drivers/s390/char/sclp.c - 1.4 linux/drivers/s390/char/sclp_con.c - 1.4 linux/drivers/s390/char/sclp_tty.c - 1.7 linux/drivers/mca/mca-legacy.c - 1.2 linux/drivers/s390/char/sclp_tty.h - 1.3 linux/drivers/s390/char/tape_34xx.c - 1.3 linux/drivers/s390/char/tape_block.c - 1.5 linux/drivers/acpi/namespace/nsparse.c - 1.6 linux/Documentation/scsi/aic7xxx.txt - 1.4 linux/drivers/usb/serial/bus.c - 1.6 linux/drivers/s390/char/tape_char.c - 1.3 linux/arch/sparc64/kernel/module.c - 1.6 linux/include/asm-sparc64/compat.h - 1.9 linux/drivers/s390/char/tape_core.c - 1.4 linux/drivers/video/console/fbcon.c - 1.7 linux/drivers/video/console/fbcon.h - 1.5 linux/drivers/video/console/sticore.c - 1.4 linux/drivers/s390/char/tape_proc.c - 1.2 linux/drivers/s390/char/tape_std.c - 1.2 linux/drivers/acpi/events/evgpe.c - 1.9 linux/drivers/acpi/dispatcher/dsinit.c - 1.7 linux/drivers/char/agp/amd-k7-agp.c - 1.7 linux/drivers/char/agp/amd-k8-agp.c - 1.7 linux/drivers/char/agp/backend.c - 1.7 linux/drivers/char/agp/generic.c - 1.7 linux/arch/arm/kernel/module.c - 1.5 linux/fs/compat.c - 1.6 linux/drivers/s390/cio/css.c - 1.3 linux/drivers/s390/cio/device.c - 1.5 linux/drivers/s390/cio/device.h - 1.3 linux/drivers/s390/cio/device_fsm.c - 1.4 linux/include/asm-s390/cio.h - 1.3 linux/include/asm-s390/ccwdev.h - 1.4 linux/include/asm-ppc64/compat.h - 1.8 linux/include/linux/moduleloader.h - 1.5 linux/arch/v850/kernel/module.c - 1.5 linux/drivers/char/agp/intel-agp.c - 1.8 linux/net/core/link_watch.c - 1.3 linux/drivers/s390/cio/device_ops.c - 1.4 linux/drivers/s390/cio/qdio.c - 1.5 linux/arch/s390/kernel/module.c - 1.7 linux/arch/ppc/kernel/module.c - 1.5 linux/drivers/ieee1394/iso.c - 1.5 linux/drivers/ieee1394/iso.h - 1.3 linux/mm/nommu.c - 1.3 linux/drivers/ide/ide-io.c - 1.9 linux/kernel/compat.c - 1.6 linux/drivers/net/r8169.c - 1.5 linux/arch/i386/kernel/module.c - 1.6 linux/kernel/intermodule.c - 1.3 linux/drivers/char/watchdog/pcwd.c - 1.8 linux/arch/sparc/kernel/module.c - 1.6 linux/include/linux/xfrm.h - 1.5 linux/arch/x86_64/ia32/syscall32.c - 1.4 linux/Documentation/DMA-API.txt - 1.3 linux/arch/x86_64/kernel/module.c - 1.6 linux/Documentation/scsi/aic79xx.txt - 1.3 linux/drivers/char/agp/generic-3.0.c - 1.5 linux/include/asm-x86_64/compat.h - 1.9 linux/drivers/i2c/busses/Kconfig - 1.7 linux/drivers/i2c/busses/Makefile - 1.5 linux/drivers/i2c/busses/i2c-amd756.c - 1.5 linux/drivers/i2c/busses/i2c-amd8111.c - 1.6 linux/drivers/i2c/chips/adm1021.c - 1.7 linux/drivers/i2c/chips/lm75.c - 1.7 linux/arch/i386/kernel/sysenter.c - 1.8 linux/include/asm-ia64/intrinsics.h - 1.5 linux/include/asm-ia64/dma-mapping.h - 1.2 linux/include/asm-ia64/compat.h - 1.5 linux/drivers/scsi/aic7xxx/aic79xx.h - 1.5 linux/drivers/scsi/aic7xxx/aic79xx.reg - 1.5 linux/drivers/scsi/aic7xxx/aic79xx.seq - 1.4 linux/drivers/scsi/aic7xxx/aic79xx_core.c - 1.6 linux/include/asm-i386/mach-summit/mach_mpparse.h - 1.5 linux/include/asm-i386/mach-summit/mach_ipi.h - 1.2 linux/include/asm-i386/mach-summit/mach_apic.h - 1.6 linux/include/asm-i386/mach-numaq/mach_apic.h - 1.5 linux/include/asm-i386/mach-default/mach_mpparse.h - 1.4 linux/include/asm-i386/mach-default/mach_ipi.h - 1.2 linux/include/asm-i386/mach-default/mach_apic.h - 1.5 linux/drivers/scsi/aic7xxx/aic79xx_inline.h - 1.4 linux/drivers/scsi/aic7xxx/aic79xx_osm.c - 1.8 linux/drivers/scsi/aic7xxx/aic79xx_osm.h - 1.6 linux/drivers/scsi/aic7xxx/aic79xx_pci.c - 1.6 linux/drivers/scsi/aic7xxx/aic79xx_proc.c - 1.3 linux/drivers/scsi/aic7xxx/aic79xx_reg.h_shipped - 1.4 linux/drivers/scsi/aic7xxx/aic79xx_reg_print.c_shipped - 1.4 linux/drivers/scsi/aic7xxx/aic79xx_seq.h_shipped - 1.4 linux/drivers/scsi/aic7xxx/aic7xxx_osm.c - 1.10 linux/drivers/scsi/aic7xxx/aiclib.c - 1.4 linux/drivers/scsi/aic7xxx/aiclib.h - 1.4 linux/include/asm-ppc64/xics.h - 1.2 linux/Documentation/driver-model/porting.txt - 1.2 linux/arch/alpha/kernel/module.c - 1.4 linux/drivers/media/video/bt832.c - 1.3 linux/drivers/media/video/v4l1-compat.c - 1.2 linux/drivers/media/video/tda9887.c - 1.5 linux/drivers/net/amd8111e.c - 1.4 linux/include/linux/sunrpc/rpc_pipe_fs.h - 1.2 linux/net/sunrpc/rpc_pipe.c - 1.7 linux/include/asm-i386/mach-bigsmp/mach_ipi.h - 1.2 linux/arch/i386/kernel/cpu/cpufreq/gx-suspmod.c - 1.6 linux/drivers/char/ipmi/ipmi_devintf.c - 1.6 linux/drivers/char/ipmi/ipmi_kcs_intf.c - 1.6 linux/include/asm-i386/mach-bigsmp/mach_apic.h - 1.4 linux/arch/parisc/kernel/module.c - 1.4 linux/include/asm-sparc/bug.h - 1.2 linux/drivers/char/ipmi/ipmi_watchdog.c - 1.3 linux/drivers/char/ipmi/ipmi_msghandler.c - 1.5 linux/arch/ppc/ocp/Makefile - 1.3 linux/arch/ppc64/kernel/module.c - 1.3 linux/fs/proc/task_mmu.c - 1.3 linux/arch/alpha/kernel/core_marvel.c - 1.6 linux/drivers/eisa/eisa-bus.c - 1.6 linux/include/asm-alpha/agp_backend.h - 1.2 linux/include/acpi/acconfig.h - 1.6 linux/include/acpi/acdebug.h - 1.4 linux/include/acpi/acutils.h - 1.4 linux/include/acpi/actypes.h - 1.5 linux/include/acpi/actables.h - 1.3 linux/include/acpi/acpixf.h - 1.6 linux/include/acpi/acpiosxf.h - 1.6 linux/include/acpi/acpi_bus.h - 1.2 linux/arch/arm/common/sa1111-pcipool.c - 1.2 linux/arch/arm/common/sa1111.c - 1.6 linux/include/acpi/acobject.h - 1.4 linux/include/acpi/acnamesp.h - 1.3 linux/include/acpi/acmacros.h - 1.4 linux/include/acpi/aclocal.h - 1.6 linux/include/acpi/acevents.h - 1.5 linux/include/acpi/acexcep.h - 1.3 linux/include/acpi/acglobal.h - 1.5 linux/include/acpi/achware.h - 1.5 linux/drivers/cpufreq/proc_intf.c - 1.2 linux/scripts/file2alias.c - 1.4 linux/drivers/char/agp/alpha-agp.c - 1.3 linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c - 1.4 linux/net/sctp/ssnmap.c - 1.2 linux/drivers/usb/input/hid-tmff.c - 1.2 linux/arch/x86_64/mm/k8topology.c - 1.3 linux/include/linux/mod_devicetable.h - 1.3 linux/drivers/net/typhoon.c - 1.4 linux/arch/x86_64/mm/numa.c - 1.3 linux/arch/i386/kernel/acpi/sleep.c - 1.3 linux/kernel/posix-timers.c - 1.8 linux/include/asm-i386/mach-visws/mach_apic.h - 1.2 linux/arch/m68knommu/platform/68VZ328/ucdimm/config.c - 1.3 linux/drivers/acpi/events/evgpeblk.c - 1.4 linux/net/ipv6/netfilter/ip6t_frag.c - 1.4 linux/net/sctp/proc.c - 1.2 linux/fs/sysfs/bin.c - 1.4 linux/net/ipv6/netfilter/ip6t_rt.c - 1.4 linux/net/ipv6/netfilter/ip6t_ipv6header.c - 1.4 linux/drivers/video/cg14.c - 1.4 linux/drivers/video/bw2.c - 1.4 linux/net/ipv6/netfilter/ip6t_esp.c - 1.4 linux/drivers/video/cg3.c - 1.4 linux/drivers/video/ffb.c - 1.5 linux/drivers/video/p9100.c - 1.4 linux/net/ipv6/netfilter/ip6t_ah.c - 1.4 linux/arch/i386/kernel/srat.c - 1.3 linux/fs/sysfs/mount.c - 1.3 linux/drivers/video/tcx.c - 1.4 linux/init/do_mounts_rd.c - 1.4 linux/drivers/i2c/busses/i2c-ali15x3.c - 1.4 linux/drivers/pci/bus.c - 1.3 linux/include/media/audiochip.h - 1.2 linux/net/compat.c - 1.4 linux/include/media/tuner.h - 1.2 linux/arch/arm/kernel/pm.c - 1.2 linux/net/ipv6/ah6.c - 1.6 linux/include/media/video-buf.h - 1.2 linux/drivers/i2c/busses/i2c-piix4.c - 1.4 linux/drivers/i2c/busses/i2c-i801.c - 1.4 linux/drivers/video/leo.c - 1.3 linux/net/ipv6/esp6.c - 1.6 linux/arch/ia64/sn/io/sn2/klconflib.c - 1.2 linux/arch/m68knommu/platform/5307/timers.c - 1.2 linux/sound/core/sgbuf.c - 1.3 linux/sound/core/memalloc.c - 1.3 linux/net/nonet.c - 1.2 linux/drivers/video/logo/logo.c - 1.5 linux/net/ipv6/xfrm6_state.c - 1.3 linux/net/ipv6/xfrm6_policy.c - 1.3 linux/include/net/compat.h - 1.3 linux/net/ipv6/anycast.c - 1.2 linux/net/ipv4/xfrm4_state.c - 1.3 linux/drivers/i2c/busses/i2c-isa.c - 1.3 linux/drivers/video/cirrusfb.c - 1.3 linux/drivers/usb/misc/speedtch.c - 1.5 linux/net/xfrm/xfrm_user.c - 1.2 linux/net/xfrm/xfrm_state.c - 1.3 linux/net/xfrm/xfrm_policy.c - 1.3 linux/net/xfrm/xfrm_input.c - 1.2 linux/net/xfrm/xfrm_algo.c - 1.3 linux/drivers/pcmcia/sa11xx_core.c - 1.2 linux/drivers/i2c/chips/via686a.c - 1.4 linux/drivers/i2c/chips/w83781d.c - 1.4 linux/net/ipv4/netfilter/ip_conntrack_amanda.c - 1.4 linux/net/ipv4/netfilter/ip_conntrack_tftp.c - 1.3 linux/net/ipv4/netfilter/ip_nat_amanda.c - 1.2 linux/net/ipv4/netfilter/ip_nat_tftp.c - 1.3 linux/arch/x86_64/kernel/acpi/wakeup.S - 1.2 linux/crypto/deflate.c - 1.2 linux/arch/ppc/platforms/pmac_cpufreq.c - 1.3 linux/arch/s390/kernel/compat_ioctl.c - 1.3 linux/drivers/media/common/saa7146_fops.c - 1.2 linux/drivers/media/common/saa7146_video.c - 1.2 linux/drivers/media/video/dpc7146.c - 1.2 linux/drivers/media/video/mxb.c - 1.3 linux/include/linux/nfsd/state.h - 1.2 linux/drivers/i2c/i2c-keywest.c - 1.2 linux/drivers/i2c/busses/i2c-viapro.c - 1.3 linux/include/asm-s390/compat.h - 1.2 linux/net/ipv4/xfrm4_tunnel.c - 1.3 linux/include/asm-h8300/hardirq.h - 1.2 linux/drivers/block/floppy98.c - 1.3 linux/fs/nfsd/nfs4state.c - 1.2 linux/arch/ia64/kernel/acpi-ext.c - 1.2 linux/net/ipv4/ipcomp.c - 1.3 linux/arch/s390/kernel/compat_exec.c - 1.2 linux/arch/s390/kernel/compat_wrapper.S - 1.2 linux/arch/s390/kernel/entry64.S - 1.2 linux/arch/s390/kernel/head64.S - 1.2 linux/arch/s390/kernel/syscalls.S - 1.2 linux/drivers/net/ixgb/ixgb_main.c - 1.2 linux/drivers/scsi/dc395x.c - 1.2 linux/include/linux/compat_ioctl.h - 1.2 linux/drivers/i2c/chips/it87.c - 1.2 linux/drivers/char/drm/drm_memory_debug.h - 1.2 linux/fs/xfs/linux/xfs_syncd.c - 1.4 Subject: TAKE - Update linux directory inode contents after the initial mkdir, right now size shows up as zero which is wrong. Date: Wed Jun 4 11:39:36 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:150334a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:150334a linux/fs/xfs/linux/xfs_iops.c - 1.202 - Merge of 2.4.x-xfs:slinx:150334a by lord. update linux inode fields in a directory after it is created. Subject: TAKE - make doing an iread from a bad location less chatty by default as some code paths can actually do this and handle the result. Date: Tue Jun 10 10:20:30 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:150747a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:150747a linux/fs/xfs/xfs_inode.c - 1.375 - Merge of 2.4.x-xfs:slinx:150747a by lord. turn down the logging level on xfs_iread failures Subject: TAKE - break dependency between CONFIG_PROCFS and CONFIG_SYSCTL in xfs Date: Tue Jun 10 14:20:12 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:150782a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:150782a linux/fs/xfs/linux/xfs_sysctl.h - 1.13 - Merge of 2.4.x-xfs:slinx:150782a by lord. move clear stats sysctl to the end linux/fs/xfs/linux/xfs_sysctl.c - 1.18 - Merge of 2.4.x-xfs:slinx:150782a by lord. make the clear stats interface conditional on procfs, the only way we display stats is via procfs anyway. Subject: TAKE - fix type of get_sb function, add missing const to dev_name param Date: Tue Jun 10 14:23:33 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:150785a linux/fs/xfs/linux/xfs_super.c - 1.271 - fix args of linvfs_get_sb Subject: TAKE - Fix deadlock caused by race between xfs_iunpin marking an inode dirty, and the same inode being reallocated and reused by create. The unlock_new_inode and mark_inode_dirty manage to corrupt the i_state flags and end up leaving I_LOCK|I_NEW set. Date: Thu Jun 12 19:53:37 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:151120a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:151120a linux/fs/xfs/xfs_inode.c - 1.376 - Merge of 2.4.x-xfs:slinx:151120a by lord. do not call mark_inode_dirty in xfs_iunpin when I_NEW is set, it is in the process of going into a transaction which will also mark it dirty. Subject: TAKE - Fix deadlock between xfs_finish_reclaim and xfs_iget_core. An inode being reclaimed and removed from memory by one thread while another thread is attempting to reuse the inode and bring it back to life. There was a window between the iget starting to reuse the inode and the reclaim starting. Close the window by marking the inode as being reused under the hash lock, and by abandoning the reclaim if this is detected when it obtains the hash lock. Date: Thu Jun 12 20:32:14 PDT 2003 Workarea: penguin.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:151123a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:151123a linux/fs/xfs/xfs_vnodeops.c - 1.593 - Merge of 2.4.x-xfs:slinx:151123a by lord. Set XFS_IRECLAIMABLE when disconnecting an xfs_inode from the linux inode. This is safe from the iget path because of the I_LOCK which is held in both cases. In xfs_finish_reclaim, after obtaining the hash lock, check that XFS_IRECLAIMABLE is set in the case where there is no vnode, abandon the reclaim if it is not. We can also reduce the locking use in a couple of paths here. linux/fs/xfs/xfs_iget.c - 1.185 - Merge of 2.4.x-xfs:slinx:151123a by lord. When a candidate inode is found in xfs_iget_core which has the potential to be reclaimed, remove the XFS_IRECLAIMABLE flag under the inode hash lock. linux/fs/xfs/xfs_inode.h - 1.183 - Merge of 2.4.x-xfs:slinx:151123a by lord. Define XFS_IRECLAIMABLE Subject: TAKE - Remove a dead code path from mount, noticed by Al Viro. Date: Mon Jun 16 07:37:44 PDT 2003 Workarea: penguin.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:151226a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:151226a linux/fs/xfs/xfs_iocore.c - 1.42 linux/fs/xfs/xfs_mount.h - 1.172 - Merge of 2.4.x-xfs:slinx:151226a by lord. drop dev arg from xfs_mountfs linux/fs/xfs/xfs_mount.c - 1.332 - Merge of 2.4.x-xfs:slinx:151226a by lord. drop dev arg from xfs_mountfs, and the noio path which is never executed. Subject: TAKE - SYNC_FSDATA and SYNC_REFCACHE are supposed to be distinct values, they ended up the same somehow. Date: Mon Jun 16 07:48:30 PDT 2003 Workarea: penguin.americas.sgi.com:/src/lord/xfs-merge.2.5 Author: lord Merged by: lord Merged mods: 2.4.x-xfs:slinx:151227a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:151227a linux/fs/xfs/linux/xfs_vfs.h - 1.40 - Merge of 2.4.x-xfs:slinx:151227a by lord. make SYNC_FSDATA and SYNC_REFCACHE different Subject: TAKE - merge up to 2.5.71 Date: Tue Jun 17 07:16:27 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:151330a linux/include/net/ip6_tunnel.h - 1.1 linux/arch/sh/boards/overdrive/setup.c - 1.1 linux/arch/sh/boards/overdrive/time.c - 1.1 linux/include/sound/ak4xxx-adda.h - 1.1 linux/Documentation/DocBook/gadget.tmpl - 1.1 linux/drivers/mtd/maps/ebony.c - 1.1 linux/drivers/mtd/maps/dilnetpc.c - 1.1 linux/drivers/mtd/maps/h720x-flash.c - 1.1 linux/drivers/mtd/maps/ich2rom.c - 1.1 linux/include/sound/opl4.h - 1.1 linux/drivers/mtd/maps/lasat.c - 1.1 linux/drivers/mtd/maps/beech-mtd.c - 1.1 linux/sound/pci/azt3328.h - 1.1 linux/drivers/mtd/maps/arctic-mtd.c - 1.1 linux/drivers/mtd/maps/amd76xrom.c - 1.1 linux/Documentation/rocket.txt - 1.1 linux/drivers/mtd/maps/lubbock-flash.c - 1.1 linux/include/asm-ppc64/cputable.h - 1.1 linux/sound/pcmcia/vx/vxpocket.h - 1.1 linux/sound/pcmcia/vx/vxpocket.c - 1.1 linux/include/linux/topology.h - 1.1 linux/sound/pcmcia/vx/vxp_ops.c - 1.1 linux/sound/pcmcia/vx/vxp_mixer.c - 1.1 linux/drivers/mtd/inftlmount.c - 1.1 linux/include/linux/tiocl.h - 1.1 linux/sound/pcmcia/vx/vxp440.c - 1.1 linux/drivers/mtd/inftlcore.c - 1.1 linux/drivers/mtd/maps/map_funcs.c - 1.1 linux/sound/pcmcia/vx/vx_entry.c - 1.1 linux/drivers/mtd/maps/mbx860.c - 1.1 linux/sound/pcmcia/vx/Makefile - 1.1 linux/drivers/mtd/maps/nettel.c - 1.1 linux/drivers/mtd/maps/pb1xxx-flash.c - 1.1 linux/drivers/mtd/devices/ms02-nv.h - 1.1 linux/include/linux/sysdev.h - 1.1 linux/drivers/mtd/devices/ms02-nv.c - 1.1 linux/drivers/mtd/maps/redwood.c - 1.1 linux/drivers/mtd/maps/scb2_flash.c - 1.1 linux/sound/pcmcia/Makefile - 1.1 linux/drivers/mtd/devices/doc2001plus.c - 1.1 linux/sound/pcmcia/Kconfig - 1.1 linux/drivers/mtd/maps/tsunami_flash.c - 1.1 linux/drivers/mtd/mtd_blkdevs.c - 1.1 linux/sound/pci/azt3328.c - 1.1 linux/drivers/mtd/cmdlinepart.c - 1.1 linux/sound/parisc/Kconfig - 1.1 linux/drivers/mtd/mtdblock.h - 1.1 linux/drivers/mtd/nand/autcpu12.c - 1.1 linux/sound/pci/vx222/vx222_ops.c - 1.1 linux/arch/arm/common/platform.c - 1.1 linux/sound/pci/vx222/vx222.h - 1.1 linux/drivers/mtd/nand/edb7312.c - 1.1 linux/sound/pci/vx222/vx222.c - 1.1 linux/drivers/mtd/nand/nand_ids.c - 1.1 linux/net/ipv6/ip6_tunnel.c - 1.1 linux/sound/pci/vx222/Makefile - 1.1 linux/drivers/mtd/chips/cfi_cmdset_0020.c - 1.1 linux/sound/drivers/opl4/opl4_lib.c - 1.1 linux/include/asm-arm26/ide.h - 1.1 linux/arch/m68knommu/platform/5307/ints.c - 1.1 linux/arch/arm/mach-integrator/core.c - 1.1 linux/drivers/net/wireless/atmel.c - 1.1 linux/drivers/net/wireless/atmel_cs.c - 1.1 linux/drivers/net/wireless/orinoco_tmd.c - 1.1 linux/sound/drivers/opl4/opl4_mixer.c - 1.1 linux/arch/sh/cchips/hd6446x/hd64461/io.c - 1.1 linux/drivers/pci/hotplug/Kconfig - 1.1 linux/drivers/pci/hotplug/Makefile - 1.1 linux/drivers/pci/hotplug/acpiphp.h - 1.1 linux/drivers/pci/hotplug/acpiphp_core.c - 1.1 linux/drivers/pci/hotplug/acpiphp_glue.c - 1.1 linux/sound/drivers/opl4/opl4_synth.c - 1.1 linux/drivers/pci/hotplug/acpiphp_pci.c - 1.1 linux/drivers/pci/hotplug/acpiphp_res.c - 1.1 linux/drivers/pci/hotplug/cpci_hotplug.h - 1.1 linux/drivers/pci/hotplug/cpci_hotplug_core.c - 1.1 linux/include/linux/mtd/inftl.h - 1.1 linux/drivers/pci/hotplug/cpci_hotplug_pci.c - 1.1 linux/include/linux/mtd/blktrans.h - 1.1 linux/drivers/pci/hotplug/cpcihp_generic.c - 1.1 linux/arch/arm26/ACKNOWLEDGEMENTS - 1.1 linux/arch/arm26/Config.help - 1.1 linux/arch/arm26/Kconfig - 1.1 linux/arch/arm26/Makefile - 1.1 linux/arch/arm26/boot/Makefile - 1.1 linux/arch/arm26/boot/compressed/Makefile - 1.1 linux/arch/arm26/boot/compressed/head.S - 1.1 linux/arch/arm26/boot/compressed/hw-bse.c - 1.1 linux/arch/arm26/boot/compressed/ll_char_wr.S - 1.1 linux/arch/arm26/boot/compressed/misc.c - 1.1 linux/arch/arm26/boot/compressed/ofw-shark.c - 1.1 linux/arch/arm26/boot/compressed/uncompress.h - 1.1 linux/arch/arm26/boot/compressed/vmlinux.lds.in - 1.1 linux/arch/arm26/boot/install.sh - 1.1 linux/arch/arm26/config.in - 1.1 linux/arch/arm26/defconfig - 1.1 linux/arch/arm26/kernel/Makefile - 1.1 linux/arch/arm26/kernel/arch.c - 1.1 linux/arch/arm26/kernel/armksyms.c - 1.1 linux/arch/arm26/kernel/asm-offsets.c - 1.1 linux/arch/arm26/kernel/compat.c - 1.1 linux/arch/arm26/kernel/dma.c - 1.1 linux/arch/arm26/kernel/ecard.c - 1.1 linux/arch/arm26/kernel/entry.S - 1.1 linux/arch/arm26/kernel/fiq.c - 1.1 linux/arch/arm26/kernel/init_task.c - 1.1 linux/arch/arm26/kernel/irq.c - 1.1 linux/arch/arm26/kernel/process.c - 1.1 linux/arch/arm26/kernel/ptrace.c - 1.1 linux/arch/arm26/kernel/ptrace.h - 1.1 linux/arch/arm26/kernel/semaphore.c - 1.1 linux/arch/arm26/kernel/setup.c - 1.1 linux/arch/arm26/kernel/signal.c - 1.1 linux/arch/arm26/kernel/sys_arm.c - 1.1 linux/arch/arm26/kernel/time-acorn.c - 1.1 linux/arch/arm26/kernel/time.c - 1.1 linux/arch/arm26/kernel/traps.c - 1.1 linux/arch/arm26/lib/Makefile - 1.1 linux/arch/arm26/lib/ashldi3.c - 1.1 linux/arch/arm26/lib/ashrdi3.c - 1.1 linux/arch/arm26/lib/backtrace.S - 1.1 linux/arch/arm26/lib/changebit.S - 1.1 linux/arch/arm26/lib/clearbit.S - 1.1 linux/arch/arm26/lib/copy_page.S - 1.1 linux/arch/arm26/lib/csumipv6.S - 1.1 linux/arch/arm26/lib/csumpartial.S - 1.1 linux/arch/arm26/lib/csumpartialcopy.S - 1.1 linux/arch/arm26/lib/csumpartialcopygeneric.S - 1.1 linux/arch/arm26/lib/csumpartialcopyuser.S - 1.1 linux/arch/arm26/lib/delay.S - 1.1 linux/arch/arm26/lib/ecard.S - 1.1 linux/arch/arm26/lib/findbit.S - 1.1 linux/arch/arm26/lib/floppydma.S - 1.1 linux/arch/arm26/lib/gcclib.h - 1.1 linux/arch/arm26/lib/getuser.S - 1.1 linux/arch/arm26/lib/io-acorn.S - 1.1 linux/arch/arm26/lib/io-readsb.S - 1.1 linux/arch/arm26/lib/io-readsl-armv3.S - 1.1 linux/arch/arm26/lib/io-readsw-armv3.S - 1.1 linux/arch/arm26/lib/io-writesb.S - 1.1 linux/arch/arm26/lib/io-writesl.S - 1.1 linux/arch/arm26/lib/io-writesw-armv3.S - 1.1 linux/arch/arm26/lib/kbd.c - 1.1 linux/arch/arm26/lib/lib1funcs.S - 1.1 linux/arch/arm26/lib/longlong.h - 1.1 linux/arch/arm26/lib/lshrdi3.c - 1.1 linux/arch/arm26/lib/memchr.S - 1.1 linux/arch/arm26/lib/memcpy.S - 1.1 linux/arch/arm26/lib/memset.S - 1.1 linux/arch/arm26/lib/memzero.S - 1.1 linux/arch/arm26/lib/muldi3.c - 1.1 linux/arch/arm26/lib/putuser.S - 1.1 linux/arch/arm26/lib/setbit.S - 1.1 linux/arch/arm26/lib/strchr.S - 1.1 linux/arch/arm26/lib/strrchr.S - 1.1 linux/arch/arm26/lib/testchangebit.S - 1.1 linux/arch/arm26/lib/testclearbit.S - 1.1 linux/arch/arm26/lib/testsetbit.S - 1.1 linux/arch/arm26/lib/uaccess-kernel.S - 1.1 linux/arch/arm26/lib/uaccess-user.S - 1.1 linux/arch/arm26/lib/ucmpdi2.c - 1.1 linux/arch/arm26/lib/udivdi3.c - 1.1 linux/arch/arm26/machine/Makefile - 1.1 linux/arch/arm26/machine/arch.c - 1.1 linux/arch/arm26/machine/dma.c - 1.1 linux/arch/arm26/machine/head.S - 1.1 linux/arch/arm26/machine/irq.c - 1.1 linux/arch/arm26/machine/oldlatches.c - 1.1 linux/arch/arm26/machine/small_page.c - 1.1 linux/arch/arm26/mm/Makefile - 1.1 linux/arch/arm26/mm/extable.c - 1.1 linux/arch/arm26/mm/fault.c - 1.1 linux/arch/arm26/mm/fault.h - 1.1 linux/arch/arm26/mm/init.c - 1.1 linux/arch/arm26/mm/mm-memc.c - 1.1 linux/arch/arm26/mm/proc-funcs.S - 1.1 linux/arch/arm26/nwfpe/ARM-gcc.h - 1.1 linux/arch/arm26/nwfpe/ChangeLog - 1.1 linux/arch/arm26/nwfpe/Makefile - 1.1 linux/arch/arm26/nwfpe/double_cpdo.c - 1.1 linux/arch/arm26/nwfpe/entry.S - 1.1 linux/arch/arm26/nwfpe/extended_cpdo.c - 1.1 linux/arch/arm26/nwfpe/fpa11.c - 1.1 linux/arch/arm26/nwfpe/fpa11.h - 1.1 linux/arch/arm26/nwfpe/fpa11.inl - 1.1 linux/arch/arm26/nwfpe/fpa11_cpdo.c - 1.1 linux/arch/arm26/nwfpe/fpa11_cpdt.c - 1.1 linux/arch/arm26/nwfpe/fpa11_cprt.c - 1.1 linux/arch/arm26/nwfpe/fpmodule.c - 1.1 linux/arch/arm26/nwfpe/fpmodule.h - 1.1 linux/arch/arm26/nwfpe/fpmodule.inl - 1.1 linux/arch/arm26/nwfpe/fpopcode.c - 1.1 linux/arch/arm26/nwfpe/fpopcode.h - 1.1 linux/arch/arm26/nwfpe/fpsr.h - 1.1 linux/arch/arm26/nwfpe/milieu.h - 1.1 linux/arch/arm26/nwfpe/single_cpdo.c - 1.1 linux/arch/arm26/nwfpe/softfloat-macros - 1.1 linux/arch/arm26/nwfpe/softfloat-specialize - 1.1 linux/arch/arm26/nwfpe/softfloat.c - 1.1 linux/arch/arm26/nwfpe/softfloat.h - 1.1 linux/arch/arm26/vmlinux-armo.lds.in - 1.1 linux/arch/arm26/vmlinux.lds.S - 1.1 linux/sound/drivers/vx/Makefile - 1.1 linux/include/asm-arm26/signal.h - 1.1 linux/include/asm-arm26/socket.h - 1.1 linux/arch/sh/boards/unknown/io.c - 1.1 linux/include/asm-arm26/smp.h - 1.1 linux/include/asm-arm26/sizes.h - 1.1 linux/drivers/pci/hotplug/cpcihp_zt5550.c - 1.1 linux/drivers/pci/hotplug/cpcihp_zt5550.h - 1.1 linux/drivers/pci/hotplug/cpqphp.h - 1.1 linux/drivers/pci/hotplug/cpqphp_core.c - 1.1 linux/drivers/pci/hotplug/cpqphp_ctrl.c - 1.1 linux/drivers/pci/hotplug/cpqphp_nvram.c - 1.1 linux/include/linux/ip6_tunnel.h - 1.1 linux/arch/sh/boards/unknown/Makefile - 1.1 linux/drivers/i2c/i2c-iop3xx.h - 1.1 linux/drivers/i2c/i2c-iop3xx.c - 1.1 linux/sound/pci/ice1712/aureon.h - 1.1 linux/sound/pci/ice1712/aureon.c - 1.1 linux/arch/i386/kernel/cpu/cpufreq/speedstep-centrino.c - 1.1 linux/arch/i386/kernel/cpu/cpufreq/speedstep-ich.c - 1.1 linux/sound/pci/ice1712/ak4xxx.c - 1.1 linux/drivers/pci/hotplug/cpqphp_nvram.h - 1.1 linux/drivers/pci/hotplug/cpqphp_pci.c - 1.1 linux/drivers/pci/hotplug/cpqphp_sysfs.c - 1.1 linux/include/asm-arm26/sigcontext.h - 1.1 linux/drivers/i2c/chips/lm85.c - 1.1 linux/drivers/pci/hotplug/ibmphp.h - 1.1 linux/drivers/pci/hotplug/ibmphp_core.c - 1.1 linux/drivers/pci/hotplug/ibmphp_ebda.c - 1.1 linux/include/asm-arm26/serial.h - 1.1 linux/drivers/pci/hotplug/ibmphp_hpc.c - 1.1 linux/arch/i386/kernel/summit.c - 1.1 linux/drivers/pci/hotplug/ibmphp_pci.c - 1.1 linux/drivers/pci/hotplug/ibmphp_res.c - 1.1 linux/drivers/pci/hotplug/pci_hotplug.h - 1.1 linux/drivers/pci/hotplug/pci_hotplug_core.c - 1.1 linux/drivers/pci/hotplug/pcihp_skeleton.c - 1.1 linux/include/asm-arm26/semaphore-helper.h - 1.1 linux/arch/sh/boards/sh2000/io.c - 1.1 linux/include/asm-arm26/resource.h - 1.1 linux/include/asm-arm26/segment.h - 1.1 linux/arch/sh/boards/se/7751/irq.c - 1.1 linux/include/asm-arm26/scatterlist.h - 1.1 linux/include/asm-arm26/rmap.h - 1.1 linux/arch/sh/boards/se/7751/io.c - 1.1 linux/include/asm-arm26/io.h - 1.1 linux/include/asm-arm26/ioc.h - 1.1 linux/include/sound/vx_core.h - 1.1 linux/arch/sh/boards/se/7751/Makefile - 1.1 linux/include/asm-arm26/ioctl.h - 1.1 linux/arch/sh/cchips/hd6446x/hd64465/setup.c - 1.1 linux/arch/sh/boards/se/7751/led.c - 1.1 linux/arch/sh/boards/se/770x/mach.c - 1.1 linux/arch/sh/cchips/hd6446x/hd64465/io.c - 1.1 linux/include/asm-arm26/ptrace.h - 1.1 linux/include/asm-arm26/procinfo.h - 1.1 linux/arch/sh/boards/se/770x/io.c - 1.1 linux/drivers/char/rocket.h - 1.1 linux/net/ipv4/esp4.c - 1.1 linux/net/ipv4/ah4.c - 1.1 linux/drivers/serial/8250_acpi.c - 1.1 linux/drivers/serial/8250_hcdp.c - 1.1 linux/drivers/serial/8250_hcdp.h - 1.1 linux/sound/drivers/opl4/Makefile - 1.1 linux/sound/parisc/harmony.c - 1.1 linux/sound/parisc/Makefile - 1.1 linux/arch/sh/cchips/hd6446x/hd64465/gpio.c - 1.1 linux/arch/sh/cchips/hd6446x/hd64465/Makefile - 1.1 linux/sound/drivers/opl4/opl4_local.h - 1.1 linux/arch/sh/cchips/hd6446x/hd64461/Makefile - 1.1 linux/sound/drivers/opl4/opl4_proc.c - 1.1 linux/sound/drivers/opl4/opl4_seq.c - 1.1 linux/include/asm-arm26/ioctls.h - 1.1 linux/arch/sh/cchips/hd6446x/hd64461/setup.c - 1.1 linux/sound/drivers/opl4/yrw801.c - 1.1 linux/arch/sh/boards/unknown/setup.c - 1.1 linux/sound/drivers/vx/vx_cmd.c - 1.1 linux/sound/drivers/vx/vx_cmd.h - 1.1 linux/sound/drivers/vx/vx_core.c - 1.1 linux/sound/drivers/vx/vx_hwdep.c - 1.1 linux/sound/drivers/vx/vx_mixer.c - 1.1 linux/sound/drivers/vx/vx_pcm.c - 1.1 linux/sound/drivers/vx/vx_uer.c - 1.1 linux/sound/i2c/other/Makefile - 1.1 linux/sound/i2c/other/ak4xxx-adda.c - 1.1 linux/fs/compat_ioctl.c - 1.1 linux/include/asm-arm26/a.out.h - 1.1 linux/include/asm-arm26/arch.h - 1.1 linux/include/asm-arm26/assembler.h - 1.1 linux/include/asm-arm26/atomic.h - 1.1 linux/include/asm-arm26/bitops.h - 1.1 linux/include/asm-arm26/bug.h - 1.1 linux/include/asm-arm26/bugs.h - 1.1 linux/include/asm-arm26/byteorder.h - 1.1 linux/include/asm-i386/mach-generic/mach_apicdef.h - 1.1 linux/include/asm-arm26/cache.h - 1.1 linux/include/asm-arm26/xor.h - 1.1 linux/include/asm-arm26/user.h - 1.1 linux/include/asm-arm26/unistd.h - 1.1 linux/include/asm-arm26/uncompress.h - 1.1 linux/include/asm-arm26/unaligned.h - 1.1 linux/include/asm-arm26/ucontext.h - 1.1 linux/include/asm-arm26/uaccess.h - 1.1 linux/include/asm-arm26/cacheflush.h - 1.1 linux/include/asm-arm26/calls.h - 1.1 linux/include/asm-arm26/checksum.h - 1.1 linux/include/asm-arm26/uaccess-asm.h - 1.1 linux/include/asm-arm26/constants.h - 1.1 linux/include/asm-arm26/types.h - 1.1 linux/include/asm-arm26/topology.h - 1.1 linux/include/asm-arm26/tlbflush.h - 1.1 linux/include/asm-arm26/tlb.h - 1.1 linux/include/asm-arm26/timex.h - 1.1 linux/include/asm-arm26/thread_info.h - 1.1 linux/include/asm-arm26/termios.h - 1.1 linux/include/asm-arm26/termbits.h - 1.1 linux/include/asm-arm26/system.h - 1.1 linux/include/asm-arm26/current.h - 1.1 linux/include/asm-arm26/sysirq.h - 1.1 linux/include/asm-arm26/delay.h - 1.1 linux/include/asm-arm26/suspend.h - 1.1 linux/include/asm-arm26/div64.h - 1.1 linux/include/asm-arm26/dma.h - 1.1 linux/include/asm-arm26/string.h - 1.1 linux/include/asm-arm26/ecard.h - 1.1 linux/include/asm-arm26/elf.h - 1.1 linux/include/asm-arm26/errno.h - 1.1 linux/include/asm-arm26/fcntl.h - 1.1 linux/include/asm-arm26/fiq.h - 1.1 linux/include/asm-arm26/floppy.h - 1.1 linux/include/asm-arm26/fpstate.h - 1.1 linux/include/asm-arm26/hardirq.h - 1.1 linux/include/asm-arm26/hardware.h - 1.1 linux/include/asm-arm26/statfs.h - 1.1 linux/include/asm-arm26/stat.h - 1.1 linux/include/asm-arm26/spinlock.h - 1.1 linux/include/asm-arm26/softirq.h - 1.1 linux/include/asm-arm26/sockios.h - 1.1 linux/arch/sh/boards/sh2000/Makefile - 1.1 linux/arch/sh/boards/sh2000/setup.c - 1.1 linux/arch/sh/boards/sh2000/mach.c - 1.1 linux/arch/sh/boards/unknown/mach.c - 1.1 linux/include/asm-arm26/siginfo.h - 1.1 linux/arch/sh/boards/se/7751/setup.c - 1.1 linux/include/asm-arm26/shmparam.h - 1.1 linux/include/asm-arm26/shmbuf.h - 1.1 linux/include/asm-arm26/setup.h - 1.1 linux/sound/isa/sscape.c - 1.1 linux/arch/sh/boards/se/7751/pci.c - 1.1 linux/include/asm-arm26/sembuf.h - 1.1 linux/include/asm-arm26/semaphore.h - 1.1 linux/arch/sh/boards/se/7751/mach.c - 1.1 linux/arch/sh/boards/se/770x/led.c - 1.1 linux/arch/sh/boards/se/770x/irq.c - 1.1 linux/arch/sh/boards/se/770x/setup.c - 1.1 linux/arch/ppc64/kernel/cputable.c - 1.1 linux/arch/sh/boards/saturn/setup.c - 1.1 linux/arch/sh/boards/se/770x/Makefile - 1.1 linux/arch/sh/boards/saturn/smp.c - 1.1 linux/include/asm-arm26/processor.h - 1.1 linux/include/asm-arm26/proc-fns.h - 1.1 linux/include/asm-arm26/posix_types.h - 1.1 linux/include/asm-arm26/poll.h - 1.1 linux/include/asm-arm26/pgtable.h - 1.1 linux/include/asm-arm26/pgalloc.h - 1.1 linux/include/asm-arm26/percpu.h - 1.1 linux/include/asm-arm26/pci.h - 1.1 linux/include/asm-arm26/parport.h - 1.1 linux/include/asm-arm26/param.h - 1.1 linux/include/asm-arm26/page.h - 1.1 linux/include/asm-arm26/oldlatches.h - 1.1 linux/include/asm-arm26/namei.h - 1.1 linux/include/asm-arm26/msgbuf.h - 1.1 linux/include/asm-arm26/module.h - 1.1 linux/include/asm-arm26/mmu_context.h - 1.1 linux/include/asm-arm26/mmu.h - 1.1 linux/include/asm-arm26/mman.h - 1.1 linux/include/asm-arm26/memory.h - 1.1 linux/include/asm-arm26/mc146818rtc.h - 1.1 linux/include/asm-arm26/map.h - 1.1 linux/include/asm-arm26/mach-types.h - 1.1 linux/include/asm-arm26/locks.h - 1.1 linux/include/asm-arm26/linux_logo.h - 1.1 linux/include/asm-arm26/linkage.h - 1.1 linux/include/asm-arm26/limits.h - 1.1 linux/include/asm-arm26/leds.h - 1.1 linux/include/asm-arm26/kmap_types.h - 1.1 linux/include/asm-arm26/keyboard.h.old - 1.1 linux/include/asm-arm26/irqchip.h - 1.1 linux/include/asm-arm26/irq.h - 1.1 linux/include/asm-arm26/ipcbuf.h - 1.1 linux/include/asm-arm26/ipc.h - 1.1 linux/arch/sh/boards/adx/Makefile - 1.1 linux/arch/sh/boards/adx/io.c - 1.1 linux/arch/sh/boards/adx/irq.c - 1.1 linux/arch/sh/boards/adx/irq_maskreg.c - 1.1 linux/arch/sh/boards/adx/mach.c - 1.1 linux/arch/sh/boards/adx/setup.c - 1.1 linux/arch/sh/boards/bigsur/Makefile - 1.1 linux/arch/sh/boards/bigsur/io.c - 1.1 linux/arch/sh/boards/bigsur/irq.c - 1.1 linux/arch/sh/boards/bigsur/led.c - 1.1 linux/arch/sh/boards/bigsur/mach.c - 1.1 linux/arch/sh/boards/bigsur/pci.c - 1.1 linux/arch/sh/boards/bigsur/setup.c - 1.1 linux/arch/sh/boards/cat68701/Makefile - 1.1 linux/arch/sh/boards/cat68701/io.c - 1.1 linux/arch/sh/boards/cat68701/irq.c - 1.1 linux/arch/sh/boards/cat68701/mach.c - 1.1 linux/arch/sh/boards/cat68701/setup.c - 1.1 linux/arch/sh/boards/cqreek/Makefile - 1.1 linux/arch/sh/boards/cqreek/io.c - 1.1 linux/arch/sh/boards/cqreek/irq.c - 1.1 linux/arch/sh/boards/cqreek/mach.c - 1.1 linux/arch/sh/boards/cqreek/setup.c - 1.1 linux/arch/sh/boards/dmida/Makefile - 1.1 linux/arch/sh/boards/dmida/mach.c - 1.1 linux/arch/sh/boards/dreamcast/Makefile - 1.1 linux/arch/sh/boards/dreamcast/io.c - 1.1 linux/arch/sh/boards/dreamcast/irq.c - 1.1 linux/arch/sh/boards/dreamcast/mach.c - 1.1 linux/arch/sh/boards/dreamcast/pci.c - 1.1 linux/arch/sh/boards/dreamcast/rtc.c - 1.1 linux/arch/sh/boards/dreamcast/setup.c - 1.1 linux/arch/sh/boards/ec3104/Makefile - 1.1 linux/arch/sh/boards/ec3104/io.c - 1.1 linux/arch/sh/boards/ec3104/irq.c - 1.1 linux/arch/sh/boards/ec3104/mach.c - 1.1 linux/arch/sh/boards/ec3104/setup.c - 1.1 linux/arch/sh/boards/harp/Makefile - 1.1 linux/arch/sh/boards/harp/irq.c - 1.1 linux/arch/sh/boards/harp/led.c - 1.1 linux/arch/sh/boards/harp/mach.c - 1.1 linux/arch/sh/boards/harp/pcidma.c - 1.1 linux/arch/sh/boards/harp/setup.c - 1.1 linux/arch/sh/boards/hp6xx/hp620/Makefile - 1.1 linux/arch/sh/boards/hp6xx/hp620/mach.c - 1.1 linux/arch/sh/boards/hp6xx/hp680/Makefile - 1.1 linux/arch/sh/boards/hp6xx/hp680/mach.c - 1.1 linux/arch/sh/boards/hp6xx/hp690/Makefile - 1.1 linux/arch/sh/boards/hp6xx/hp690/mach.c - 1.1 linux/arch/sh/boards/overdrive/Makefile - 1.1 linux/arch/sh/boards/overdrive/fpga.c - 1.1 linux/arch/sh/boards/overdrive/galileo.c - 1.1 linux/arch/sh/boards/overdrive/io.c - 1.1 linux/arch/sh/boards/overdrive/irq.c - 1.1 linux/arch/sh/boards/overdrive/led.c - 1.1 linux/arch/sh/boards/overdrive/mach.c - 1.1 linux/arch/sh/boards/overdrive/pcidma.c - 1.1 linux/include/asm-arm26/hdreg.h - 1.1 linux/include/asm-arm26/ian_char.h - 1.1 linux/arch/sh/boards/saturn/Makefile - 1.1 linux/arch/sh/boards/saturn/io.c - 1.1 linux/arch/sh/boards/saturn/irq.c - 1.1 linux/arch/sh/boards/saturn/mach.c - 1.1 linux/net/x25/x25_timer.c - 1.11 linux/net/x25/x25_subr.c - 1.10 linux/net/x25/x25_out.c - 1.10 linux/net/x25/x25_in.c - 1.14 linux/net/x25/x25_facilities.c - 1.8 linux/net/x25/af_x25.c - 1.35 linux/net/wanrouter/wanproc.c - 1.26 linux/net/unix/garbage.c - 1.14 linux/net/unix/af_unix.c - 1.58 linux/net/sunrpc/xprt.c - 1.44 linux/net/sunrpc/svcsock.c - 1.32 linux/net/sunrpc/sunrpc_syms.c - 1.23 linux/net/sunrpc/clnt.c - 1.32 linux/net/sunrpc/auth.c - 1.15 linux/net/socket.c - 1.58 linux/net/rose/rose_timer.c - 1.9 linux/net/rose/rose_subr.c - 1.9 linux/net/rose/rose_route.c - 1.12 linux/net/rose/rose_out.c - 1.7 linux/net/rose/rose_in.c - 1.8 linux/net/rose/af_rose.c - 1.32 linux/net/packet/af_packet.c - 1.43 linux/net/netsyms.c - 1.69 linux/net/netrom/nr_timer.c - 1.9 linux/net/netrom/nr_subr.c - 1.8 linux/net/netrom/nr_out.c - 1.7 linux/net/netrom/nr_in.c - 1.7 linux/net/netrom/af_netrom.c - 1.30 linux/net/netlink/af_netlink.c - 1.30 linux/net/irda/af_irda.c - 1.48 linux/net/ipx/af_ipx.c - 1.38 linux/net/ipv6/udp.c - 1.42 linux/net/ipv6/tcp_ipv6.c - 1.53 linux/net/ipv6/sysctl_net_ipv6.c - 1.6 linux/net/ipv6/sit.c - 1.32 linux/net/ipv6/route.c - 1.35 linux/net/ipv6/reassembly.c - 1.19 linux/net/ipv6/raw.c - 1.35 linux/net/ipv6/proc.c - 1.17 linux/net/ipv6/ndisc.c - 1.35 linux/net/ipv6/mcast.c - 1.27 linux/net/ipv6/ipv6_sockglue.c - 1.25 linux/net/ipv6/ip6_output.c - 1.24 linux/net/ipv6/ip6_input.c - 1.19 linux/net/ipv6/ip6_fib.c - 1.19 linux/net/ipv6/icmp.c - 1.30 linux/net/ipv6/datagram.c - 1.15 linux/net/ipv6/af_inet6.c - 1.36 linux/net/ipv6/addrconf.c - 1.38 linux/net/ipv6/Makefile - 1.16 linux/net/ipv4/udp.c - 1.44 linux/net/ipv4/tcp_timer.c - 1.29 linux/net/ipv4/tcp_output.c - 1.40 linux/net/ipv4/tcp_ipv4.c - 1.63 linux/net/ipv4/tcp_input.c - 1.51 linux/net/ipv4/tcp.c - 1.57 linux/net/ipv4/sysctl_net_ipv4.c - 1.20 linux/net/ipv4/syncookies.c - 1.20 linux/net/ipv4/route.c - 1.50 linux/net/ipv4/raw.c - 1.34 linux/net/ipv4/ipmr.c - 1.29 linux/net/ipv4/ipip.c - 1.32 linux/net/ipv4/ip_sockglue.c - 1.27 linux/net/ipv4/ip_output.c - 1.48 linux/net/ipv4/ip_input.c - 1.24 linux/net/ipv4/ip_gre.c - 1.32 linux/net/ipv4/ip_fragment.c - 1.20 linux/net/ipv4/icmp.c - 1.40 linux/net/ipv4/devinet.c - 1.23 linux/net/ipv4/af_inet.c - 1.55 linux/net/ipv4/Makefile - 1.20 linux/net/core/sock.c - 1.36 linux/net/core/rtnetlink.c - 1.18 linux/net/core/neighbour.c - 1.22 linux/net/core/iovec.c - 1.10 linux/net/core/filter.c - 1.10 linux/net/core/dst.c - 1.17 linux/net/core/dev.c - 1.75 linux/net/core/datagram.c - 1.17 linux/net/ax25/ax25_subr.c - 1.10 linux/net/ax25/ax25_std_timer.c - 1.7 linux/net/ax25/ax25_std_in.c - 1.7 linux/net/ax25/ax25_route.c - 1.10 linux/net/ax25/ax25_ip.c - 1.10 linux/net/ax25/ax25_in.c - 1.14 linux/net/ax25/ax25_ds_timer.c - 1.8 linux/net/ax25/ax25_ds_in.c - 1.8 linux/net/ax25/ax25_dev.c - 1.7 linux/net/ax25/af_ax25.c - 1.33 linux/net/appletalk/ddp.c - 1.29 linux/net/appletalk/aarp.c - 1.17 linux/mm/vmscan.c - 1.129 linux/mm/slab.c - 1.58 linux/mm/page_alloc.c - 1.110 linux/mm/mmap.c - 1.78 linux/mm/memory.c - 1.107 linux/mm/filemap.c - 1.157 linux/lib/Makefile - 1.22 linux/kernel/time.c - 1.17 linux/kernel/sysctl.c - 1.67 linux/kernel/sys.c - 1.53 linux/kernel/softirq.c - 1.37 linux/kernel/signal.c - 1.56 linux/kernel/sched.c - 1.102 linux/kernel/resource.c - 1.22 linux/kernel/module.c - 1.44 linux/kernel/ksyms.c - 1.191 linux/kernel/kmod.c - 1.32 linux/kernel/fork.c - 1.91 linux/kernel/exec_domain.c - 1.23 linux/ipc/sem.c - 1.27 linux/init/main.c - 1.108 linux/include/scsi/sg.h - 1.20 linux/include/net/x25.h - 1.14 linux/include/net/udp.h - 1.15 linux/include/net/tcp.h - 1.47 linux/include/net/sock.h - 1.48 linux/include/net/snmp.h - 1.14 linux/include/net/route.h - 1.24 linux/include/net/rose.h - 1.7 linux/include/net/netrom.h - 1.7 linux/include/net/ipx.h - 1.12 linux/include/net/ipv6.h - 1.17 linux/include/net/ip6_route.h - 1.13 linux/include/net/ip6_fib.h - 1.8 linux/include/net/ip.h - 1.27 linux/include/net/flow.h - 1.6 linux/include/net/ax25.h - 1.11 linux/include/net/af_unix.h - 1.8 linux/include/linux/wanrouter.h - 1.13 linux/include/linux/udp.h - 1.8 linux/include/linux/tty_driver.h - 1.10 linux/include/linux/trdevice.h - 1.6 linux/include/linux/timex.h - 1.8 linux/include/linux/tcp.h - 1.16 linux/include/linux/sysctl.h - 1.74 linux/include/linux/sunrpc/auth.h - 1.11 linux/include/linux/stallion.h - 1.6 linux/include/linux/smp.h - 1.28 linux/include/linux/slab.h - 1.32 linux/include/linux/signal.h - 1.15 linux/include/linux/serialP.h - 1.19 linux/include/linux/serial167.h - 1.5 linux/include/linux/serial.h - 1.19 linux/include/linux/selection.h - 1.3 linux/include/linux/sched.h - 1.105 linux/include/linux/rtnetlink.h - 1.18 linux/include/linux/rocket.h - 1.3 linux/include/linux/reboot.h - 1.6 linux/include/linux/ptrace.h - 1.9 linux/include/linux/proc_fs.h - 1.40 linux/include/linux/ppp-comp.h - 1.5 linux/include/linux/pci.h - 1.76 linux/include/linux/netdevice.h - 1.46 linux/include/linux/msdos_fs_sb.h - 1.13 linux/include/linux/msdos_fs_i.h - 1.8 linux/include/linux/msdos_fs.h - 1.28 linux/include/linux/module.h - 1.51 linux/include/linux/loop.h - 1.13 linux/include/linux/list.h - 1.29 linux/include/linux/kernel.h - 1.47 linux/include/linux/istallion.h - 1.5 linux/include/linux/isicom.h - 1.6 linux/include/linux/isdn.h - 1.33 linux/include/linux/ipv6.h - 1.9 linux/include/linux/init.h - 1.27 linux/include/linux/if_ec.h - 1.7 linux/include/linux/if_arp.h - 1.15 linux/include/linux/i2c.h - 1.26 linux/include/linux/hippidevice.h - 1.5 linux/include/linux/hayesesp.h - 1.4 linux/include/linux/genhd.h - 1.38 linux/include/linux/fs.h - 1.215 linux/include/linux/fddidevice.h - 1.6 linux/include/linux/etherdevice.h - 1.8 linux/include/linux/dcache.h - 1.37 linux/include/linux/cyclades.h - 1.12 linux/include/linux/blkdev.h - 1.85 linux/include/linux/bitops.h - 1.6 linux/include/linux/atalk.h - 1.9 linux/include/asm-ppc/uaccess.h - 1.15 linux/include/asm-ppc/types.h - 1.15 linux/include/asm-ppc/system.h - 1.30 linux/include/asm-ppc/semaphore.h - 1.12 linux/include/asm-ppc/ptrace.h - 1.13 linux/include/asm-ppc/processor.h - 1.43 linux/include/asm-ppc/prep_nvram.h - 1.7 linux/include/asm-ppc/pgtable.h - 1.44 linux/include/asm-ppc/pci-bridge.h - 1.14 linux/include/asm-ppc/mmu_context.h - 1.17 linux/include/asm-ppc/ipc.h - 1.5 linux/include/asm-ppc/io.h - 1.22 linux/include/asm-ppc/hardirq.h - 1.25 linux/include/asm-ppc/dma.h - 1.11 linux/include/asm-mips/pci.h - 1.16 linux/include/asm-m68k/pgtable.h - 1.19 linux/include/asm-i386/stat.h - 1.7 linux/include/asm-i386/smp.h - 1.29 linux/include/asm-i386/pgtable.h - 1.48 linux/include/asm-i386/msr.h - 1.20 linux/include/asm-i386/fixmap.h - 1.17 linux/include/asm-arm/uaccess.h - 1.13 linux/include/asm-arm/hardware.h - 1.7 linux/include/asm-alpha/unistd.h - 1.30 linux/include/asm-alpha/unaligned.h - 1.4 linux/include/asm-alpha/uaccess.h - 1.11 linux/include/asm-alpha/string.h - 1.6 linux/include/asm-alpha/ptrace.h - 1.4 linux/include/asm-alpha/pci.h - 1.21 linux/include/asm-alpha/bitops.h - 1.17 linux/fs/vfat/namei.c - 1.39 linux/fs/smbfs/sock.c - 1.19 linux/fs/smbfs/proc.c - 1.28 linux/fs/proc/proc_tty.c - 1.10 linux/fs/proc/inode.c - 1.32 linux/fs/proc/base.c - 1.52 linux/fs/nfsd/nfssvc.c - 1.34 linux/fs/ncpfs/sock.c - 1.19 linux/fs/ncpfs/inode.c - 1.44 linux/fs/namei.c - 1.71 linux/fs/msdos/namei.c - 1.37 linux/fs/inode.c - 1.98 linux/fs/filesystems.c - 1.31 linux/fs/fcntl.c - 1.33 linux/fs/fat/misc.c - 1.18 linux/fs/fat/inode.c - 1.59 linux/fs/fat/file.c - 1.29 linux/fs/fat/dir.c - 1.24 linux/fs/fat/cache.c - 1.21 linux/fs/exec.c - 1.84 linux/fs/dquot.c - 1.70 linux/fs/dcache.c - 1.54 linux/fs/coda/inode.c - 1.31 linux/fs/buffer.c - 1.157 linux/fs/binfmt_elf.c - 1.57 linux/fs/attr.c - 1.22 linux/drivers/video/pm2fb.c - 1.23 linux/drivers/video/Makefile - 1.55 linux/drivers/sgi/char/sgiserial.h - 1.5 linux/drivers/sgi/char/sgiserial.c - 1.18 linux/drivers/scsi/wd7000.c - 1.27 linux/drivers/scsi/wd33c93.h - 1.13 linux/drivers/scsi/wd33c93.c - 1.15 linux/drivers/scsi/tmscsim.c - 1.25 linux/drivers/scsi/t128.h - 1.10 linux/drivers/scsi/sym53c8xx.c - 1.47 linux/drivers/scsi/st.h - 1.20 linux/drivers/scsi/st.c - 1.66 linux/drivers/scsi/sr.h - 1.14 linux/drivers/scsi/sr.c - 1.67 linux/drivers/scsi/sg.c - 1.54 linux/drivers/scsi/sd.c - 1.87 linux/drivers/scsi/scsi_syms.c - 1.33 linux/drivers/scsi/scsi_proc.c - 1.19 linux/drivers/scsi/scsi_debug.h - 1.15 linux/drivers/scsi/scsi_debug.c - 1.35 linux/drivers/scsi/scsi.h - 1.52 linux/drivers/scsi/scsi.c - 1.77 linux/drivers/scsi/qlogicisp.c - 1.36 linux/drivers/scsi/qlogicfc.c - 1.40 linux/drivers/scsi/ppa.h - 1.15 linux/drivers/scsi/ppa.c - 1.26 linux/drivers/scsi/pci2220i.c - 1.31 linux/drivers/scsi/pci2000.c - 1.28 linux/drivers/scsi/pas16.h - 1.9 linux/drivers/scsi/ncr53c8xx.c - 1.36 linux/drivers/scsi/megaraid.h - 1.21 linux/drivers/scsi/megaraid.c - 1.47 linux/drivers/scsi/mac_scsi.h - 1.7 linux/drivers/scsi/mac_NCR5380.c - 1.11 linux/drivers/scsi/inia100.c - 1.29 linux/drivers/scsi/in2000.h - 1.15 linux/drivers/scsi/in2000.c - 1.19 linux/drivers/scsi/imm.h - 1.14 linux/drivers/scsi/imm.c - 1.25 linux/drivers/scsi/ide-scsi.c - 1.54 linux/drivers/scsi/ibmmca.h - 1.12 linux/drivers/scsi/ibmmca.c - 1.26 linux/drivers/scsi/hosts.h - 1.41 linux/drivers/scsi/hosts.c - 1.46 linux/drivers/scsi/gdth_proc.h - 1.8 linux/drivers/scsi/gdth_proc.c - 1.18 linux/drivers/scsi/gdth.h - 1.16 linux/drivers/scsi/gdth.c - 1.30 linux/drivers/scsi/g_NCR5380.h - 1.12 linux/drivers/scsi/g_NCR5380.c - 1.24 linux/drivers/scsi/fdomain.c - 1.32 linux/drivers/scsi/fd_mcs.h - 1.9 linux/drivers/scsi/fd_mcs.c - 1.15 linux/drivers/scsi/fcal.h - 1.8 linux/drivers/scsi/fcal.c - 1.16 linux/drivers/scsi/esp.c - 1.35 linux/drivers/scsi/eata_pio.c - 1.23 linux/drivers/scsi/eata.c - 1.37 linux/drivers/scsi/dtc.h - 1.9 linux/drivers/scsi/dc390.h - 1.11 linux/drivers/scsi/atp870u.h - 1.11 linux/drivers/scsi/atp870u.c - 1.28 linux/drivers/scsi/atari_scsi.h - 1.8 linux/drivers/scsi/atari_NCR5380.c - 1.12 linux/drivers/scsi/aic7xxx/aic7xxx.seq - 1.14 linux/drivers/scsi/aic7xxx/aic7xxx.reg - 1.12 linux/drivers/scsi/aha1740.h - 1.9 linux/drivers/scsi/aha1740.c - 1.18 linux/drivers/scsi/aha152x.c - 1.41 linux/drivers/scsi/advansys.h - 1.12 linux/drivers/scsi/advansys.c - 1.37 linux/drivers/scsi/NCR53C9x.h - 1.10 linux/drivers/scsi/NCR53C9x.c - 1.26 linux/drivers/scsi/NCR5380.h - 1.8 linux/drivers/scsi/NCR5380.c - 1.21 linux/drivers/scsi/BusLogic.h - 1.15 linux/drivers/scsi/BusLogic.c - 1.25 linux/drivers/scsi/AM53C974.c - 1.21 linux/drivers/sbus/sbus.c - 1.21 linux/drivers/sbus/char/envctrl.c - 1.22 linux/drivers/pci/proc.c - 1.34 linux/drivers/pci/pci.c - 1.67 linux/drivers/pci/Makefile - 1.34 linux/drivers/net/tlan.c - 1.35 linux/drivers/net/sunqe.c - 1.27 linux/drivers/net/slip.c - 1.26 linux/drivers/net/rrunner.c - 1.28 linux/drivers/net/ptifddi_asm.h - 1.3 linux/drivers/net/ptifddi.h - 1.5 linux/drivers/net/ptifddi.c - 1.10 linux/drivers/net/ppp_deflate.c - 1.13 linux/drivers/net/pcnet32.c - 1.44 linux/drivers/net/net_init.c - 1.23 linux/drivers/net/irda/w83977af_ir.c - 1.31 linux/drivers/net/irda/irtty.c - 1.32 linux/drivers/net/irda/irport.c - 1.31 linux/drivers/net/hp100.c - 1.30 linux/drivers/net/hamradio/mkiss.c - 1.18 linux/drivers/net/hamradio/dmascc.c - 1.17 linux/drivers/net/ethertap.c - 1.14 linux/drivers/net/eepro.c - 1.31 linux/drivers/net/dummy.c - 1.11 linux/drivers/net/dgrs.c - 1.26 linux/drivers/net/defxx.c - 1.26 linux/drivers/net/bmac.c - 1.25 linux/drivers/net/acenic.c - 1.47 linux/drivers/net/Space.c - 1.44 linux/drivers/net/Makefile - 1.73 linux/drivers/net/3c509.c - 1.47 linux/drivers/macintosh/via-pmu.c - 1.27 linux/drivers/macintosh/via-cuda.c - 1.15 linux/drivers/macintosh/nvram.c - 1.13 linux/drivers/macintosh/macserial.h - 1.11 linux/drivers/macintosh/macserial.c - 1.30 linux/drivers/macintosh/adb.c - 1.27 linux/drivers/char/vt.c - 1.39 linux/drivers/char/tty_io.c - 1.71 linux/drivers/char/synclink.c - 1.38 linux/drivers/char/stallion.c - 1.31 linux/drivers/char/specialix_io8.h - 1.4 linux/drivers/char/specialix.c - 1.21 linux/drivers/char/serial167.c - 1.22 linux/drivers/char/selection.c - 1.8 linux/drivers/char/rtc.c - 1.41 linux/drivers/char/rocket_int.h - 1.6 linux/drivers/char/rocket.c - 1.24 linux/drivers/char/riscom8.h - 1.4 linux/drivers/char/riscom8.c - 1.21 linux/drivers/char/pty.c - 1.20 linux/drivers/char/pcxx.h - 1.5 linux/drivers/char/pcxx.c - 1.19 linux/drivers/char/n_hdlc.c - 1.22 linux/drivers/char/mem.c - 1.54 linux/drivers/char/istallion.c - 1.30 linux/drivers/char/isicom.c - 1.27 linux/drivers/char/esp.c - 1.23 linux/drivers/char/epca.c - 1.29 linux/drivers/char/cyclades.c - 1.32 linux/drivers/char/Makefile - 1.85 linux/drivers/block/nbd.c - 1.56 linux/drivers/block/loop.c - 1.85 linux/drivers/block/ll_rw_blk.c - 1.134 linux/drivers/block/genhd.c - 1.54 linux/drivers/block/acsi.c - 1.49 linux/drivers/acorn/char/Makefile - 1.17 linux/drivers/Makefile - 1.45 linux/arch/sparc64/solaris/timod.c - 1.24 linux/arch/sparc64/prom/console.c - 1.3 linux/arch/sparc64/prom/Makefile - 1.16 linux/arch/sparc64/lib/Makefile - 1.18 linux/arch/sparc64/kernel/systbls.S - 1.45 linux/arch/sparc64/kernel/sys_sparc.c - 1.30 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.59 linux/arch/sparc64/kernel/ioctl32.c - 1.73 linux/arch/sparc64/kernel/ebus.c - 1.21 linux/arch/sparc64/kernel/Makefile - 1.34 linux/arch/sparc64/defconfig - 1.94 linux/arch/sparc64/boot/Makefile - 1.9 linux/arch/sparc/prom/console.c - 1.9 linux/arch/sparc/prom/Makefile - 1.8 linux/arch/sparc/lib/Makefile - 1.15 linux/arch/sparc/kernel/ebus.c - 1.16 linux/arch/ppc/mm/init.c - 1.51 linux/arch/ppc/kernel/traps.c - 1.32 linux/arch/ppc/kernel/syscalls.c - 1.16 linux/arch/ppc/kernel/signal.c - 1.24 linux/arch/ppc/kernel/setup.c - 1.57 linux/arch/ppc/kernel/process.c - 1.51 linux/arch/ppc/kernel/ppc_ksyms.c - 1.58 linux/arch/ppc/kernel/ppc_htab.c - 1.21 linux/arch/ppc/kernel/pci.c - 1.35 linux/arch/ppc/kernel/misc.S - 1.58 linux/arch/ppc/kernel/irq.c - 1.46 linux/arch/ppc/kernel/head.S - 1.44 linux/arch/ppc/kernel/align.c - 1.12 linux/arch/ppc/boot/Makefile - 1.25 linux/arch/ppc/8xx_io/uart.c - 1.28 linux/arch/ppc/8xx_io/fec.c - 1.20 linux/arch/ppc/8xx_io/enet.c - 1.19 linux/arch/mips/sni/pci.c - 1.14 linux/arch/mips/lib/Makefile - 1.13 linux/arch/mips/kernel/irq.c - 1.17 linux/arch/m68k/lib/Makefile - 1.12 linux/arch/i386/lib/Makefile - 1.21 linux/arch/i386/kernel/time.c - 1.40 linux/arch/i386/kernel/smp.c - 1.58 linux/arch/i386/kernel/setup.c - 1.94 linux/arch/i386/kernel/irq.c - 1.59 linux/arch/i386/kernel/io_apic.c - 1.62 linux/arch/i386/kernel/entry.S - 1.80 linux/arch/i386/kernel/Makefile - 1.50 linux/arch/arm/mm/init.c - 1.38 linux/arch/arm/lib/Makefile - 1.29 linux/arch/arm/kernel/process.c - 1.38 linux/arch/arm/Makefile - 1.46 linux/arch/alpha/lib/csum_partial_copy.c - 1.6 linux/arch/alpha/lib/Makefile - 1.23 linux/arch/alpha/kernel/traps.c - 1.30 linux/arch/alpha/kernel/sys_sio.c - 1.18 linux/arch/alpha/kernel/smp.c - 1.46 linux/arch/alpha/kernel/signal.c - 1.24 linux/arch/alpha/kernel/ptrace.c - 1.21 linux/arch/alpha/kernel/irq.c - 1.33 linux/arch/alpha/kernel/head.S - 1.7 linux/Makefile - 1.248 linux/MAINTAINERS - 1.141 linux/Documentation/sysctl/vm.txt - 1.12 linux/Documentation/networking/ip-sysctl.txt - 1.19 linux/Documentation/filesystems/fat_cvf.txt - 1.5 linux/Documentation/Changes - 1.66 linux/Documentation/00-INDEX - 1.17 linux/net/decnet/dn_timer.c - 1.9 linux/net/decnet/dn_nsp_out.c - 1.16 linux/net/decnet/dn_nsp_in.c - 1.22 linux/net/decnet/af_decnet.c - 1.41 linux/include/net/dn_nsp.h - 1.7 linux/include/net/dn_fib.h - 1.8 linux/include/net/dn.h - 1.11 linux/include/linux/ide.h - 1.79 linux/drivers/sbus/char/aurora.h - 1.4 linux/drivers/sbus/char/aurora.c - 1.27 linux/drivers/net/irda/toshoboe.c - 1.34 linux/drivers/acorn/char/keyb_arc.c - 1.12 linux/arch/ppc/xmon/xmon.c - 1.23 linux/arch/ppc/xmon/start.c - 1.23 linux/arch/ppc/xmon/ppc-opc.c - 1.5 linux/arch/i386/vmlinux.lds.S - 1.22 linux/Documentation/kernel-parameters.txt - 1.27 linux/drivers/tc/zs.h - 1.5 linux/drivers/tc/zs.c - 1.15 linux/drivers/char/dz.h - 1.3 linux/drivers/char/dz.c - 1.23 linux/arch/mips/dec/prom/Makefile - 1.9 linux/arch/mips/baget/vacserial.c - 1.18 linux/arch/mips/baget/prom/Makefile - 1.7 linux/arch/mips/arc/Makefile - 1.8 linux/drivers/block/cpqarray.c - 1.72 linux/drivers/parport/parport_pc.c - 1.57 linux/include/asm-sparc64/parport.h - 1.13 linux/drivers/net/ppp_generic.c - 1.38 linux/drivers/net/ppp_async.c - 1.18 linux/drivers/char/sx.c - 1.36 linux/drivers/char/generic_serial.c - 1.17 linux/include/linux/isapnp.h - 1.17 linux/include/linux/irq.h - 1.12 linux/fs/partitions/mac.c - 1.8 linux/arch/i386/kernel/i8259.c - 1.40 linux/drivers/net/sis900.c - 1.46 linux/drivers/net/sb1000.c - 1.24 linux/drivers/net/fc/iph5526.c - 1.27 linux/drivers/char/ip2main.c - 1.29 linux/drivers/char/ip2/i2lib.h - 1.7 linux/drivers/char/ip2/i2lib.c - 1.10 linux/drivers/atm/nicstar.c - 1.25 linux/drivers/atm/ambassador.c - 1.23 linux/drivers/atm/Makefile - 1.27 linux/net/sched/sch_atm.c - 1.14 linux/net/core/netfilter.c - 1.24 linux/net/atm/svc.c - 1.15 linux/net/atm/signaling.c - 1.12 linux/net/atm/raw.c - 1.9 linux/net/atm/proc.c - 1.21 linux/net/atm/mpc.h - 1.3 linux/net/atm/mpc.c - 1.16 linux/net/atm/lec.h - 1.9 linux/net/atm/lec.c - 1.22 linux/net/atm/common.c - 1.24 linux/net/atm/clip.c - 1.17 linux/net/atm/atm_misc.c - 1.7 linux/include/linux/fcdevice.h - 1.4 linux/include/linux/atmdev.h - 1.16 linux/arch/ppc/kernel/entry.S - 1.36 linux/arch/arm/vmlinux-armv.lds.in - 1.29 linux/arch/arm/vmlinux-armo.lds.in - 1.25 linux/arch/arm/kernel/bios32.c - 1.37 linux/arch/alpha/kernel/pci.c - 1.34 linux/drivers/block/DAC960.c - 1.70 linux/arch/sparc64/kernel/pci.c - 1.36 linux/arch/sh/vmlinux.lds.S - 1.19 linux/arch/sh/lib/Makefile - 1.11 linux/arch/sh/kernel/irq.c - 1.19 linux/arch/sh/kernel/Makefile - 1.20 linux/arch/sh/Makefile - 1.16 linux/drivers/scsi/ips.c - 1.41 linux/net/irda/ircomm/ircomm_tty.c - 1.29 linux/include/net/irda/ircomm_tty.h - 1.13 linux/include/asm-i386/pci.h - 1.22 linux/drivers/pcmcia/tcic.c - 1.27 linux/drivers/pcmcia/rsrc_mgr.c - 1.21 linux/drivers/pcmcia/ricoh.h - 1.9 linux/drivers/pcmcia/i82365.c - 1.40 linux/drivers/pcmcia/ds.c - 1.29 linux/drivers/pcmcia/cs_internal.h - 1.17 linux/drivers/pcmcia/cs.c - 1.39 linux/drivers/pcmcia/cistpl.c - 1.20 linux/include/pcmcia/ss.h - 1.14 linux/drivers/pcmcia/cardbus.c - 1.32 linux/drivers/pcmcia/bulkmem.c - 1.17 linux/drivers/pcmcia/Makefile - 1.24 linux/drivers/pci/syscall.c - 1.5 linux/arch/m68k/vmlinux-sun3.lds - 1.18 linux/include/pcmcia/ds.h - 1.9 linux/include/pcmcia/cs.h - 1.11 linux/drivers/pcmcia/ti113x.h - 1.10 linux/drivers/pcmcia/yenta.h - 1.5 linux/include/linux/spinlock.h - 1.26 linux/include/asm-sparc64/pci.h - 1.18 linux/include/asm-sparc/pci.h - 1.15 linux/include/asm-ppc/pci.h - 1.21 linux/drivers/net/pcmcia/pcnet_cs.c - 1.25 linux/include/linux/acpi.h - 1.37 linux/Documentation/filesystems/proc.txt - 1.20 linux/drivers/net/tokenring/olympic.c - 1.27 linux/drivers/net/tokenring/ibmtr.c - 1.24 linux/include/linux/pci_ids.h - 1.92 linux/drivers/net/wan/z85230.h - 1.7 linux/drivers/net/wan/sdladrv.c - 1.11 linux/drivers/net/wan/sdla.c - 1.18 linux/drivers/net/wan/sbni.c - 1.23 linux/drivers/net/pcmcia/fmvj18x_cs.c - 1.24 linux/mm/highmem.c - 1.52 linux/mm/bootmem.c - 1.27 linux/include/linux/highmem.h - 1.31 linux/include/asm-arm/pci.h - 1.25 linux/fs/proc/proc_misc.c - 1.62 linux/fs/proc/kcore.c - 1.15 linux/drivers/net/setup.c - 1.24 linux/drivers/scsi/sun3_scsi.h - 1.7 linux/drivers/pci/pci.ids - 1.61 linux/drivers/net/sk98lin/h/skdrv2nd.h - 1.6 linux/drivers/net/sk98lin/skge.c - 1.26 linux/drivers/video/fbmon.c - 1.7 linux/arch/ppc/mm/mem_pieces.c - 1.9 linux/arch/ppc/kernel/head_4xx.S - 1.14 linux/include/linux/mmzone.h - 1.38 linux/kernel/timer.c - 1.46 linux/drivers/scsi/scsi_lib.c - 1.65 linux/include/linux/i2c-id.h - 1.18 linux/drivers/i2c/i2c-elektor.c - 1.17 linux/drivers/i2c/i2c-dev.c - 1.30 linux/drivers/i2c/i2c-core.c - 1.28 linux/drivers/i2c/Makefile - 1.14 linux/include/linux/i2c-dev.h - 1.13 linux/drivers/pcmcia/yenta.c - 1.41 linux/drivers/pcmcia/pci_socket.h - 1.11 linux/drivers/pcmcia/pci_socket.c - 1.19 linux/drivers/telephony/ixj.c - 1.29 linux/drivers/net/arcnet/rfc1201.c - 1.7 linux/drivers/net/arcnet/rfc1051.c - 1.5 linux/drivers/net/arcnet/arcnet.c - 1.17 linux/drivers/net/arcnet/arc-rawmode.c - 1.5 linux/Documentation/usb/proc_usb_info.txt - 1.6 linux/net/sched/sch_ingress.c - 1.14 linux/drivers/net/tokenring/smctr.c - 1.21 linux/drivers/ieee1394/ieee1394_core.c - 1.32 linux/drivers/ieee1394/ohci1394.c - 1.33 linux/drivers/ieee1394/ieee1394_transactions.c - 1.16 linux/arch/i386/kernel/apic.c - 1.45 linux/drivers/ieee1394/ieee1394.h - 1.8 linux/arch/i386/kernel/mpparse.c - 1.39 linux/drivers/char/moxa.c - 1.19 linux/drivers/char/mxser.c - 1.25 linux/include/asm-i386/mpspec.h - 1.16 linux/drivers/pci/setup-res.c - 1.16 linux/drivers/pci/setup-irq.c - 1.4 linux/drivers/scsi/scsi_scan.c - 1.48 linux/drivers/scsi/3w-xxxx.h - 1.20 linux/drivers/scsi/3w-xxxx.c - 1.32 linux/drivers/net/wan/sdla_chdlc.c - 1.26 linux/drivers/net/tokenring/tmspci.c - 1.11 linux/drivers/net/tokenring/madgemc.c - 1.12 linux/drivers/net/tokenring/abyss.c - 1.10 linux/arch/m68k/atari/hades-pci.c - 1.6 linux/Documentation/DMA-mapping.txt - 1.19 linux/include/asm-m68k/pci.h - 1.7 linux/drivers/net/irda/nsc-ircc.c - 1.28 linux/drivers/char/vme_scc.c - 1.18 linux/drivers/atm/iphase.c - 1.22 linux/arch/ia64/vmlinux.lds.S - 1.25 linux/arch/ia64/kernel/irq.c - 1.29 linux/arch/ia64/kernel/smp.c - 1.24 linux/arch/ia64/lib/Makefile - 1.19 linux/arch/ia64/mm/init.c - 1.28 linux/drivers/scsi/qla1280.h - 1.13 linux/drivers/scsi/qla1280.c - 1.28 linux/include/asm-ia64/hardirq.h - 1.19 linux/include/linux/raid/raid0.h - 1.5 linux/include/asm-ia64/smp.h - 1.14 linux/include/linux/raid/md.h - 1.25 linux/include/asm-ia64/pgtable.h - 1.23 linux/include/asm-ia64/pci.h - 1.20 linux/include/linux/raid/linear.h - 1.6 linux/include/asm-ia64/ptrace.h - 1.14 linux/drivers/scsi/sun3_NCR5380.c - 1.12 linux/drivers/net/8139too.c - 1.52 linux/drivers/macintosh/via-pmu68k.c - 1.11 linux/drivers/char/amiserial.c - 1.22 linux/arch/arm/mm/consistent.c - 1.17 linux/drivers/isdn/hysdn/hysdn_init.c - 1.9 linux/fs/devfs/base.c - 1.58 linux/drivers/net/skfp/skfddi.c - 1.18 linux/net/bridge/br_stp_timer.c - 1.6 linux/net/bridge/br_stp_if.c - 1.8 linux/net/bridge/br_device.c - 1.10 linux/net/bridge/br_stp_bpdu.c - 1.5 linux/net/bridge/br_stp.c - 1.8 linux/net/bridge/br_private.h - 1.13 linux/net/bridge/br_notify.c - 1.5 linux/net/bridge/br_input.c - 1.16 linux/net/bridge/br_if.c - 1.14 linux/arch/mips/ddb5074/pci.c - 1.12 linux/drivers/video/matrox/matroxfb_misc.h - 1.3 linux/drivers/video/matrox/matroxfb_misc.c - 1.8 linux/drivers/video/matrox/matroxfb_maven.c - 1.8 linux/drivers/video/matrox/matroxfb_crtc2.h - 1.3 linux/drivers/video/matrox/matroxfb_crtc2.c - 1.14 linux/drivers/video/matrox/matroxfb_base.h - 1.16 linux/drivers/video/matrox/matroxfb_base.c - 1.24 linux/drivers/video/matrox/matroxfb_accel.h - 1.4 linux/drivers/video/matrox/matroxfb_accel.c - 1.10 linux/drivers/video/matrox/matroxfb_Ti3026.c - 1.8 linux/drivers/video/matrox/matroxfb_DAC1064.c - 1.14 linux/drivers/video/matrox/i2c-matroxfb.c - 1.10 linux/include/linux/matroxfb.h - 1.3 linux/include/asm-mips64/pci.h - 1.12 linux/arch/mips64/sgi-ip22/Makefile - 1.8 linux/drivers/atm/fore200e.c - 1.21 linux/arch/mips64/lib/Makefile - 1.8 linux/arch/mips64/arc/Makefile - 1.8 linux/drivers/char/epca.h - 1.4 linux/drivers/video/riva/fbdev.c - 1.27 linux/include/asm-sh/pci.h - 1.16 linux/drivers/char/sh-sci.c - 1.25 linux/arch/sh/kernel/irq_imask.c - 1.8 linux/net/econet/af_econet.c - 1.21 linux/include/linux/usb.h - 1.60 linux/drivers/usb/serial/usb-serial.h - 1.33 linux/drivers/usb/serial/usb-serial.c - 1.19 linux/drivers/ide/ide.c - 1.87 linux/drivers/ide/ide-proc.c - 1.29 linux/drivers/ide/ide-floppy.c - 1.45 linux/drivers/ide/ide-disk.c - 1.61 linux/drivers/ide/ide-cd.c - 1.63 linux/Documentation/DocBook/Makefile - 1.42 linux/scripts/kernel-doc - 1.14 linux/scripts/docproc.c - 1.6 linux/include/linux/generic_serial.h - 1.6 linux/drivers/scsi/sym53c8xx_comm.h - 1.16 linux/drivers/net/tokenring/lanstreamer.c - 1.17 linux/Documentation/DocBook/kernel-api.tmpl - 1.29 linux/net/ipv4/netfilter/iptable_mangle.c - 1.16 linux/net/ipv4/netfilter/iptable_filter.c - 1.10 linux/net/ipv4/netfilter/ipt_owner.c - 1.12 linux/net/ipv4/netfilter/ipfwadm_core.c - 1.19 linux/net/ipv4/netfilter/ipchains_core.c - 1.16 linux/net/ipv4/netfilter/ip_queue.c - 1.21 linux/net/ipv4/netfilter/ip_conntrack_core.c - 1.25 linux/drivers/scsi/dmx3191d.h - 1.8 linux/drivers/scsi/dmx3191d.c - 1.15 linux/drivers/net/pcmcia/ibmtr_cs.c - 1.15 linux/include/linux/usbdevice_fs.h - 1.11 linux/drivers/video/sa1100fb.c - 1.24 linux/drivers/usb/serial/keyspan_pda.c - 1.36 linux/drivers/usb/serial/ftdi_sio.c - 1.48 linux/drivers/usb/serial/whiteheat.c - 1.40 linux/drivers/usb/serial/visor.c - 1.52 linux/drivers/usb/serial/omninet.c - 1.34 linux/drivers/net/wan/lmc/lmc_ver.h - 1.4 linux/drivers/net/wan/lmc/lmc_var.h - 1.6 linux/drivers/net/wan/lmc/lmc_proto.c - 1.7 linux/drivers/net/wan/lmc/lmc_media.c - 1.6 linux/drivers/net/wan/lmc/lmc_main.c - 1.16 linux/drivers/net/wan/lmc/lmc_debug.c - 1.4 linux/include/linux/if_pppox.h - 1.11 linux/drivers/usb/serial/digi_acceleport.c - 1.37 linux/drivers/net/pppox.c - 1.13 linux/drivers/net/pppoe.c - 1.29 linux/arch/ppc/8260_io/uart.c - 1.18 linux/arch/ppc/8260_io/enet.c - 1.12 linux/drivers/char/rio/rioboot.c - 1.10 linux/drivers/char/rio/rio_linux.c - 1.25 linux/include/linux/raid/raid5.h - 1.13 linux/include/linux/raid/raid1.h - 1.15 linux/drivers/s390/char/con3215.c - 1.18 linux/include/asm-s390/pgtable.h - 1.21 linux/arch/s390/lib/Makefile - 1.9 linux/arch/sh/kernel/irq_ipr.c - 1.7 linux/arch/sh/kernel/io_se.c - 1.6 linux/arch/sh/kernel/setup_se.c - 1.4 linux/arch/sh/kernel/io_generic.c - 1.6 linux/kernel/kallsyms.c - 1.20 linux/drivers/usb/storage/usb.h - 1.22 linux/drivers/usb/storage/usb.c - 1.39 linux/drivers/usb/storage/transport.h - 1.20 linux/drivers/usb/storage/transport.c - 1.44 linux/arch/alpha/kernel/core_titan.c - 1.13 linux/drivers/usb/storage/scsiglue.c - 1.33 linux/drivers/usb/storage/protocol.c - 1.12 linux/drivers/usb/serial/keyspan.h - 1.19 linux/drivers/acpi/tables.c - 1.11 linux/drivers/mtd/Makefile - 1.14 linux/drivers/mtd/ftl.c - 1.35 linux/drivers/mtd/mtdblock.c - 1.36 linux/drivers/mtd/mtdchar.c - 1.15 linux/drivers/mtd/mtdcore.c - 1.6 linux/arch/sh/kernel/setup_hd64461.c - 1.5 linux/arch/sh/kernel/io_hd64461.c - 1.5 linux/arch/sh/boot/compressed/Makefile - 1.5 linux/include/linux/mtd/cfi.h - 1.9 linux/include/linux/mtd/compatmac.h - 1.6 linux/include/linux/mtd/doc2000.h - 1.6 linux/include/linux/mtd/flashchip.h - 1.3 linux/include/linux/mtd/jedec.h - 1.3 linux/include/linux/mtd/map.h - 1.9 linux/include/linux/mtd/mtd.h - 1.7 linux/include/linux/mtd/nand.h - 1.3 linux/include/linux/mtd/nftl.h - 1.5 linux/include/linux/mtd/pmc551.h - 1.4 linux/drivers/net/tun.c - 1.21 linux/net/ipv4/tcp_minisocks.c - 1.27 linux/include/net/tcp_ecn.h - 1.6 linux/include/linux/irq_cpustat.h - 1.8 linux/include/linux/if_tun.h - 1.4 linux/fs/nfs/unlink.c - 1.9 linux/drivers/usb/storage/freecom.c - 1.23 linux/drivers/media/video/zr36120.c - 1.18 linux/drivers/media/video/cpia_usb.c - 1.20 linux/drivers/media/video/bw-qcam.c - 1.13 linux/drivers/media/radio/radio-cadet.c - 1.16 linux/drivers/isdn/eicon/linchr.c - 1.8 linux/drivers/isdn/eicon/Divas_mod.c - 1.9 linux/arch/sh/kernel/setup_cqreek.c - 1.6 linux/arch/sh/kernel/mach_unknown.c - 1.4 linux/arch/sh/kernel/mach_se.c - 1.4 linux/arch/sh/kernel/mach_hp600.c - 1.5 linux/arch/sh/kernel/led_se.c - 1.3 linux/arch/sh/kernel/io_unknown.c - 1.3 linux/drivers/md/raid1.c - 1.36 linux/drivers/md/raid5.c - 1.43 linux/Documentation/kbuild/makefiles.txt - 1.10 linux/arch/ppc/8260_io/fcc_enet.c - 1.9 linux/drivers/block/cciss.c - 1.57 linux/drivers/md/linear.c - 1.22 linux/drivers/md/md.c - 1.76 linux/drivers/md/raid0.c - 1.19 linux/drivers/media/radio/radio-maestro.c - 1.10 linux/drivers/net/sundance.c - 1.25 linux/drivers/scsi/cpqfcTS.h - 1.9 linux/drivers/scsi/cpqfcTSinit.c - 1.31 linux/drivers/usb/storage/initializers.c - 1.4 linux/drivers/usb/storage/initializers.h - 1.3 linux/net/core/dv.c - 1.8 linux/drivers/usb/serial/belkin_sa.c - 1.32 linux/drivers/video/sis/sis_main.c - 1.18 linux/include/asm-i386/cpufeature.h - 1.8 linux/include/asm-ppc/module.h - 1.8 linux/include/linux/ethtool.h - 1.15 linux/arch/alpha/lib/memmove.S - 1.3 linux/drivers/usb/serial/mct_u232.c - 1.31 linux/include/asm-parisc/pci.h - 1.8 linux/drivers/usb/serial/empeg.c - 1.36 linux/arch/parisc/lib/Makefile - 1.7 linux/arch/i386/kernel/dmi_scan.c - 1.30 linux/include/linux/mtd/partitions.h - 1.3 linux/include/linux/mtd/nand_ids.h - 1.2 linux/drivers/mtd/nftlmount.c - 1.8 linux/drivers/mtd/mtdpart.c - 1.5 linux/drivers/video/matrox/matroxfb_g450.c - 1.7 linux/include/linux/shmem_fs.h - 1.10 linux/mm/shmem.c - 1.59 linux/drivers/scsi/osst.h - 1.9 linux/drivers/scsi/osst.c - 1.27 linux/arch/ia64/sn/io/pci_bus_cvlink.c - 1.6 linux/fs/reiserfs/super.c - 1.35 linux/drivers/acpi/acpi_ksyms.c - 1.20 linux/fs/reiserfs/prints.c - 1.21 linux/fs/reiserfs/journal.c - 1.43 linux/fs/reiserfs/inode.c - 1.41 linux/fs/reiserfs/file.c - 1.16 linux/include/linux/reiserfs_fs.h - 1.37 linux/include/linux/reiserfs_fs_sb.h - 1.18 linux/drivers/usb/storage/unusual_devs.h - 1.21 linux/arch/cris/drivers/ethernet.c - 1.12 linux/arch/cris/drivers/serial.c - 1.15 linux/arch/cris/drivers/serial.h - 1.7 linux/arch/cris/lib/Makefile - 1.6 linux/drivers/s390/block/xpram.c - 1.35 linux/drivers/net/pci-skeleton.c - 1.17 linux/drivers/usb/serial/io_edgeport.c - 1.36 linux/drivers/scsi/aic7xxx_old/aic7xxx_proc.c - 1.8 linux/drivers/scsi/aic7xxx_old.c - 1.32 linux/drivers/scsi/aic7xxx/aic7xxx_proc.c - 1.8 linux/drivers/scsi/aic7xxx/aic7xxx_pci.c - 1.10 linux/drivers/scsi/aic7xxx/aic7xxx_osm.h - 1.17 linux/drivers/scsi/aic7xxx/aic7xxx_inline.h - 1.9 linux/arch/arm/mach-integrator/Makefile - 1.8 linux/arch/arm/mach-integrator/arch.c - 1.9 linux/arch/arm/mach-integrator/irq.c - 1.5 linux/arch/arm/mach-integrator/mm.c - 1.5 linux/arch/arm/mach-integrator/pci_v3.c - 1.14 linux/drivers/scsi/aic7xxx/aic7xxx.h - 1.11 linux/drivers/net/sungem.h - 1.11 linux/drivers/net/sungem.c - 1.29 linux/drivers/isdn/hisax/sedlbauer_cs.c - 1.8 linux/drivers/s390/char/tuball.c - 1.12 linux/drivers/s390/char/tubio.h - 1.11 linux/drivers/s390/char/tubtty.c - 1.12 linux/net/wanrouter/af_wanpipe.c - 1.18 linux/drivers/net/saa9730.c - 1.7 linux/drivers/s390/net/ctctty.c - 1.10 linux/drivers/sbus/char/bbc_envctrl.c - 1.5 linux/drivers/sbus/char/bbc_i2c.c - 1.4 linux/drivers/isdn/hisax/elsa_cs.c - 1.5 linux/arch/sh/kernel/setup_hd64465.c - 1.4 linux/arch/sh/kernel/setup_ec3104.c - 1.5 linux/arch/sh/kernel/setup_dc.c - 1.6 linux/arch/sh/kernel/pci_st40.h - 1.2 linux/arch/sh/kernel/pci_st40.c - 1.8 linux/arch/sh/kernel/mach_ec3104.c - 1.3 linux/arch/sh/kernel/mach_dmida.c - 1.3 linux/arch/sh/kernel/mach_dc.c - 1.6 linux/arch/sh/kernel/mach_cat68701.c - 1.3 linux/arch/sh/kernel/irq_intc2.c - 1.6 linux/arch/sh/kernel/io_hd64465.c - 1.3 linux/arch/sh/kernel/io_ec3104.c - 1.3 linux/arch/sh/kernel/io_dc.c - 1.4 linux/arch/sh/kernel/io_cat68701.c - 1.3 linux/arch/sh/kernel/hd64465_gpio.c - 1.5 linux/arch/mips/mips-boards/generic/pci.c - 1.7 linux/arch/mips/ddb5476/pci.c - 1.7 linux/arch/ia64/sn/io/pciba.c - 1.6 linux/include/linux/if_wanpipe.h - 1.6 linux/drivers/net/irda/irda-usb.c - 1.32 linux/drivers/net/wireless/Makefile - 1.10 linux/drivers/net/wireless/airport.c - 1.13 linux/drivers/net/wireless/hermes.c - 1.9 linux/drivers/net/wireless/hermes.h - 1.11 linux/drivers/net/wireless/orinoco.c - 1.18 linux/drivers/net/wireless/orinoco.h - 1.13 linux/drivers/net/wireless/orinoco_cs.c - 1.17 linux/fs/char_dev.c - 1.11 linux/arch/ppc/boot/prep/vreset.c - 1.6 linux/arch/ppc/boot/lib/zlib.c - 1.4 linux/arch/ppc/boot/lib/Makefile - 1.5 linux/arch/ppc/boot/common/misc-common.c - 1.10 linux/arch/ppc/boot/common/Makefile - 1.6 linux/include/net/bluetooth/hci_core.h - 1.11 linux/include/net/bluetooth/l2cap.h - 1.8 linux/drivers/bluetooth/hci_usb.c - 1.23 linux/net/bluetooth/af_bluetooth.c - 1.16 linux/net/bluetooth/hci_sock.c - 1.15 linux/drivers/mtd/nand/nand.c - 1.3 linux/drivers/mtd/nftlcore.c - 1.33 linux/drivers/mtd/nand/spia.c - 1.7 linux/drivers/mtd/nand/nand_ecc.c - 1.5 linux/drivers/mtd/redboot.c - 1.4 linux/drivers/mtd/nand/Makefile - 1.7 linux/drivers/mtd/mtdblock_ro.c - 1.20 linux/drivers/mtd/maps/vmax301.c - 1.4 linux/drivers/mtd/maps/sun_uflash.c - 1.4 linux/drivers/mtd/maps/sc520cdp.c - 1.4 linux/drivers/mtd/maps/sbc_gxx.c - 1.5 linux/drivers/mtd/maps/sa1100-flash.c - 1.10 linux/drivers/mtd/maps/rpxlite.c - 1.4 linux/drivers/mtd/maps/pnc2000.c - 1.4 linux/drivers/mtd/maps/physmap.c - 1.4 linux/drivers/mtd/maps/octagon-5066.c - 1.4 linux/drivers/mtd/maps/ocelot.c - 1.4 linux/include/linux/mtd/nand_ecc.h - 1.2 linux/include/linux/mtd/cfi_endian.h - 1.3 linux/drivers/mtd/maps/nora.c - 1.4 linux/drivers/mtd/maps/netsc520.c - 1.4 linux/drivers/mtd/maps/iq80310.c - 1.5 linux/drivers/mtd/maps/elan-104nc.c - 1.6 linux/drivers/mtd/maps/dc21285.c - 1.5 linux/drivers/mtd/maps/dbox2-flash.c - 1.4 linux/drivers/mtd/maps/cstm_mips_ixx.c - 1.4 linux/drivers/mtd/maps/cfi_flagadm.c - 1.4 linux/drivers/mtd/maps/Makefile - 1.9 linux/drivers/mtd/devices/slram.c - 1.4 linux/drivers/mtd/devices/pmc551.c - 1.6 linux/drivers/mtd/devices/mtdram.c - 1.3 linux/drivers/mtd/devices/docprobe.c - 1.4 linux/drivers/mtd/devices/docecc.c - 1.5 linux/drivers/mtd/devices/doc2001.c - 1.3 linux/drivers/mtd/devices/doc2000.c - 1.4 linux/drivers/mtd/devices/Makefile - 1.5 linux/drivers/mtd/chips/sharp.c - 1.7 linux/drivers/mtd/chips/map_rom.c - 1.4 linux/drivers/mtd/chips/map_ram.c - 1.4 linux/drivers/mtd/chips/jedec.c - 1.9 linux/drivers/mtd/chips/chipreg.c - 1.5 linux/drivers/mtd/chips/cfi_probe.c - 1.4 linux/drivers/mtd/chips/cfi_cmdset_0002.c - 1.6 linux/drivers/mtd/chips/cfi_cmdset_0001.c - 1.5 linux/drivers/mtd/chips/amd_flash.c - 1.6 linux/drivers/mtd/chips/Makefile - 1.8 linux/arch/sh/kernel/setup_sh2000.c - 1.3 linux/drivers/acorn/char/mouse_ps2.c - 1.7 linux/arch/sh/stboards/setup.c - 1.2 linux/arch/sh/stboards/pcidma.c - 1.3 linux/arch/sh/stboards/mach.c - 1.3 linux/arch/sh/stboards/led.c - 1.2 linux/arch/sh/stboards/irq.c - 1.2 linux/arch/sh/stboards/harp.h - 1.2 linux/arch/sh/stboards/Makefile - 1.5 linux/drivers/usb/serial/cyberjack.c - 1.25 linux/drivers/usb/serial/pl2303.c - 1.32 linux/arch/sh/kernel/setup_bigsur.c - 1.3 linux/arch/sh/kernel/pci-sh7751.c - 1.8 linux/arch/sh/kernel/pci-dc.c - 1.6 linux/arch/sh/kernel/pci-bigsur.c - 1.2 linux/arch/sh/kernel/pci-7751se.c - 1.4 linux/arch/sh/kernel/mach_bigsur.c - 1.3 linux/arch/sh/kernel/led_bigsur.c - 1.2 linux/arch/sh/kernel/io_sh2000.c - 1.2 linux/arch/sh/kernel/io_bigsur.c - 1.2 linux/drivers/net/irda/ali-ircc.c - 1.18 linux/drivers/net/sk98lin/skproc.c - 1.9 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.21 linux/drivers/scsi/pcmcia/nsp_cs.h - 1.10 linux/arch/cris/drivers/lpslave/e100lpslavenet.c - 1.7 linux/drivers/media/video/zoran_procfs.c - 1.3 linux/drivers/usb/usb-skeleton.c - 1.27 linux/drivers/char/ser_a2232.c - 1.10 linux/drivers/char/ser_a2232.h - 1.3 linux/drivers/net/dl2k.h - 1.11 linux/drivers/message/fusion/mptscsih.h - 1.13 linux/drivers/message/fusion/mptscsih.c - 1.19 linux/drivers/message/fusion/mptlan.c - 1.11 linux/drivers/message/fusion/mptbase.c - 1.12 linux/drivers/message/fusion/linux_compat.h - 1.9 linux/drivers/ieee1394/sbp2.c - 1.24 linux/drivers/usb/storage/jumpshot.c - 1.11 linux/drivers/usb/storage/isd200.c - 1.16 linux/drivers/usb/storage/datafab.c - 1.11 linux/drivers/acorn/char/defkeymap-acorn.map - 1.2 linux/arch/arm/mach-sa1100/xp860.c - 1.11 linux/arch/arm/mach-sa1100/pfs168.c - 1.12 linux/arch/arm/mach-sa1100/neponset.c - 1.16 linux/arch/arm/mach-sa1100/jornada720.c - 1.11 linux/arch/arm/mach-sa1100/irq.c - 1.13 linux/arch/arm/mach-sa1100/generic.c - 1.14 linux/arch/ppc/mm/pgtable.c - 1.12 linux/drivers/video/radeonfb.c - 1.18 linux/drivers/scsi/dpti.h - 1.8 linux/drivers/scsi/dpt_i2o.c - 1.23 linux/drivers/char/serial_tx3912.c - 1.12 linux/arch/sh/kernel/rtc-aica.c - 1.2 linux/arch/sh/kernel/setup_7751se.c - 1.2 linux/arch/sh/kernel/setup_adx.c - 1.2 linux/arch/sh/kernel/mach_adx.c - 1.3 linux/arch/sh/kernel/mach_7751se.c - 1.3 linux/arch/sh/kernel/led_7751se.c - 1.2 linux/arch/sh/kernel/irq_maskreg.c - 1.2 linux/arch/sh/kernel/io_adx.c - 1.2 linux/arch/sh/kernel/io_7751se.c - 1.3 linux/arch/mips64/sgi-ip32/ip32-pci.c - 1.5 linux/arch/mips/au1000/common/serial.c - 1.12 linux/arch/mips64/mips-boards/generic/pci.c - 1.5 linux/arch/mips/ddb5xxx/ddb5477/pci.c - 1.2 linux/drivers/isdn/hisax/st5481_init.c - 1.9 linux/drivers/net/ns83820.c - 1.21 linux/drivers/scsi/53c700.c - 1.18 linux/drivers/scsi/NCR_D700.c - 1.8 linux/drivers/parport/parport_cs.c - 1.7 linux/fs/jffs2/background.c - 1.17 linux/fs/jffs2/build.c - 1.5 linux/fs/jffs2/compr.c - 1.5 linux/fs/jffs2/compr_rtime.c - 1.5 linux/fs/jffs2/compr_zlib.c - 1.7 linux/fs/jffs2/dir.c - 1.13 linux/fs/jffs2/erase.c - 1.9 linux/fs/jffs2/file.c - 1.13 linux/fs/jffs2/gc.c - 1.11 linux/fs/jffs2/malloc.c - 1.7 linux/fs/jffs2/nodelist.c - 1.8 linux/fs/jffs2/nodelist.h - 1.8 linux/fs/jffs2/nodemgmt.c - 1.8 linux/fs/jffs2/read.c - 1.7 linux/include/linux/raid/multipath.h - 1.8 linux/fs/jffs2/readinode.c - 1.8 linux/fs/jffs2/scan.c - 1.8 linux/fs/jffs2/super.c - 1.17 linux/fs/jffs2/write.c - 1.9 linux/include/linux/jffs2_fs_sb.h - 1.9 linux/drivers/md/multipath.c - 1.20 linux/include/linux/jffs2.h - 1.6 linux/arch/i386/kernel/nmi.c - 1.16 linux/drivers/mtd/maps/l440gx.c - 1.3 linux/drivers/mtd/maps/integrator-flash.c - 1.4 linux/drivers/mtd/chips/map_absent.c - 1.3 linux/drivers/mtd/chips/jedec_probe.c - 1.5 linux/drivers/mtd/devices/lart.c - 1.2 linux/drivers/mtd/maps/cdb89712.c - 1.3 linux/drivers/mtd/chips/gen_probe.c - 1.2 linux/drivers/mtd/maps/tqm8xxl.c - 1.3 linux/fs/namespace.c - 1.30 linux/drivers/mtd/afs.c - 1.3 linux/drivers/mtd/maps/solutionengine.c - 1.3 linux/drivers/net/wireless/orinoco_plx.c - 1.8 linux/drivers/usb/serial/ir-usb.c - 1.28 linux/drivers/pcmcia/sa1100_generic.c - 1.17 linux/arch/arm/mach-sa1100/graphicsmaster.c - 1.16 linux/arch/arm/mach-sa1100/adsbitsy.c - 1.14 linux/arch/arm/lib/putuser.S - 1.4 linux/drivers/message/i2o/i2o_core.c - 1.14 linux/drivers/net/8139cp.c - 1.26 linux/drivers/net/irda/sa1100_ir.c - 1.9 linux/drivers/pcmcia/i82092.c - 1.14 linux/drivers/pcmcia/i82092aa.h - 1.5 linux/net/ipv6/netfilter/ip6t_owner.c - 1.5 linux/net/8021q/vlan_dev.c - 1.9 linux/net/8021q/vlan.h - 1.6 linux/net/8021q/vlan.c - 1.12 linux/drivers/atm/idt77252.c - 1.12 linux/fs/jbd/journal.c - 1.23 linux/drivers/scsi/sym53c8xx_2/sym_glue.c - 1.16 linux/net/atm/pppoatm.c - 1.7 linux/fs/ext3/inode.c - 1.37 linux/drivers/hotplug/pci_hotplug_core.c - 1.21 linux/drivers/hotplug/pci_hotplug.h - 1.6 linux/drivers/hotplug/cpqphp_pci.c - 1.12 linux/drivers/hotplug/cpqphp_nvram.h - 1.2 linux/drivers/hotplug/cpqphp_nvram.c - 1.7 linux/drivers/hotplug/cpqphp_ctrl.c - 1.10 linux/drivers/hotplug/cpqphp_core.c - 1.15 linux/drivers/hotplug/cpqphp.h - 1.8 linux/drivers/hotplug/Makefile - 1.10 linux/fs/intermezzo/vfs.c - 1.16 linux/include/linux/acpi_serial.h - 1.3 linux/include/linux/bio.h - 1.22 linux/fs/bio.c - 1.31 linux/include/linux/device.h - 1.33 linux/drivers/usb/serial/ipaq.c - 1.23 linux/drivers/usb/serial/kl5kusb105.c - 1.21 linux/arch/arm/mach-sa1100/system3.c - 1.15 linux/arch/arm/mach-sa1100/dma.c - 1.4 linux/drivers/block/cciss_scsi.c - 1.12 linux/include/linux/init_task.h - 1.20 linux/drivers/ide/ide-taskfile.c - 1.31 linux/net/ipv4/tcp_diag.c - 1.7 linux/drivers/ieee1394/dv1394.c - 1.17 linux/net/ipv6/netfilter/ip6_queue.c - 1.11 linux/net/ipv4/netfilter/ipt_ULOG.c - 1.9 linux/drivers/hotplug/pcihp_skeleton.c - 1.3 linux/drivers/base/interface.c - 1.14 linux/drivers/base/core.c - 1.27 linux/drivers/pci/pci-driver.c - 1.15 linux/lib/zlib_inflate/infblock.c - 1.2 linux/lib/zlib_inflate/infutil.h - 1.3 linux/lib/zlib_inflate/infutil.c - 1.2 linux/lib/zlib_inflate/inftrees.h - 1.2 linux/lib/zlib_inflate/inftrees.c - 1.2 linux/lib/zlib_inflate/inflate.c - 1.4 linux/lib/zlib_inflate/inffixed.h - 1.2 linux/lib/zlib_inflate/inffast.h - 1.2 linux/lib/zlib_inflate/inffast.c - 1.2 linux/lib/zlib_inflate/infcodes.h - 1.2 linux/lib/zlib_inflate/infcodes.c - 1.2 linux/lib/zlib_inflate/infblock.h - 1.2 linux/lib/zlib_deflate/deflate.c - 1.2 linux/lib/zlib_deflate/defutil.h - 1.2 linux/lib/zlib_deflate/deftree.c - 1.2 linux/include/linux/zlib.h - 1.3 linux/include/linux/zutil.h - 1.2 linux/include/linux/zconf.h - 1.2 linux/include/asm-i386/thread_info.h - 1.10 linux/include/asm-sparc64/thread_info.h - 1.7 linux/sound/ppc/tumbler.c - 1.8 linux/sound/ppc/pmac.h - 1.5 linux/sound/ppc/pmac.c - 1.10 linux/sound/ppc/keywest.c - 1.7 linux/sound/ppc/awacs.c - 1.8 linux/sound/pci/ymfpci/ymfpci_main.c - 1.13 linux/sound/pci/ymfpci/ymfpci.c - 1.12 linux/sound/pci/trident/trident_synth.c - 1.6 linux/sound/pci/trident/trident_main.c - 1.14 linux/sound/pci/sonicvibes.c - 1.13 linux/sound/pci/rme9652/rme9652.c - 1.18 linux/sound/pci/nm256/nm256.c - 1.14 linux/sound/pci/maestro3.c - 1.16 linux/sound/pci/korg1212/korg1212.c - 1.20 linux/sound/pci/intel8x0.c - 1.19 linux/arch/ppc/4xx_io/serial_sicc.c - 1.6 linux/sound/pci/fm801.c - 1.14 linux/sound/pci/ens1370.c - 1.20 linux/sound/pci/emu10k1/irq.c - 1.5 linux/sound/pci/emu10k1/emufx.c - 1.16 linux/sound/pci/cs46xx/cs46xx_lib.c - 1.18 linux/arch/ppc/boot/ld.script - 1.5 linux/sound/pci/cmipci.c - 1.16 linux/sound/pci/ali5451/ali5451.c - 1.19 linux/sound/pci/ac97/ac97_codec.c - 1.17 linux/sound/pci/ac97/Makefile - 1.11 linux/sound/pci/Makefile - 1.9 linux/arch/ppc/boot/simple/misc-embedded.c - 1.6 linux/sound/oss/via82cxxx_audio.c - 1.11 linux/sound/oss/trident.c - 1.15 linux/sound/oss/sonicvibes.c - 1.10 linux/sound/oss/skeleton.c - 1.2 linux/sound/oss/rme96xx.c - 1.10 linux/sound/oss/nec_vrc5477.c - 1.8 linux/sound/oss/mpu401.c - 1.9 linux/sound/oss/maestro3.c - 1.9 linux/sound/oss/maestro.c - 1.13 linux/sound/oss/ite8172.c - 1.8 linux/sound/oss/i810_audio.c - 1.14 linux/sound/oss/esssolo1.c - 1.12 linux/sound/oss/es1371.c - 1.12 linux/sound/oss/es1370.c - 1.12 linux/sound/oss/emu10k1/audio.c - 1.5 linux/arch/ppc/platforms/Makefile - 1.14 linux/arch/ppc/platforms/chrp_pci.c - 1.4 linux/arch/ppc/platforms/gemini_pci.c - 1.4 linux/arch/ppc/platforms/pmac_pci.c - 1.5 linux/arch/ppc/platforms/prep_pci.c - 1.8 linux/arch/ppc/platforms/residual.c - 1.5 linux/sound/oss/cs46xx.c - 1.12 linux/sound/oss/cs4281/cs4281m.c - 1.9 linux/sound/oss/cmpci.c - 1.9 linux/arch/x86_64/defconfig - 1.17 linux/arch/x86_64/ia32/Makefile - 1.13 linux/arch/x86_64/ia32/ia32_ioctl.c - 1.19 linux/arch/x86_64/ia32/ia32entry.S - 1.15 linux/arch/x86_64/kernel/apic.c - 1.16 linux/arch/x86_64/kernel/bluesmoke.c - 1.10 linux/arch/x86_64/kernel/i8259.c - 1.6 linux/arch/x86_64/kernel/irq.c - 1.14 linux/arch/x86_64/kernel/nmi.c - 1.11 linux/arch/x86_64/kernel/process.c - 1.19 linux/arch/x86_64/kernel/setup.c - 1.13 linux/arch/x86_64/kernel/smp.c - 1.14 linux/arch/x86_64/kernel/smpboot.c - 1.16 linux/arch/x86_64/kernel/sys_x86_64.c - 1.9 linux/arch/x86_64/kernel/time.c - 1.13 linux/arch/x86_64/kernel/traps.c - 1.17 linux/arch/x86_64/kernel/vsyscall.c - 1.10 linux/arch/x86_64/kernel/x8664_ksyms.c - 1.13 linux/arch/x86_64/lib/Makefile - 1.11 linux/arch/x86_64/lib/usercopy.c - 1.6 linux/arch/x86_64/mm/fault.c - 1.12 linux/sound/oss/awe_wave.c - 1.7 linux/sound/isa/wavefront/wavefront.c - 1.12 linux/sound/isa/sb/sb8_midi.c - 1.5 linux/sound/isa/sb/sb8_main.c - 1.6 linux/sound/isa/sb/sb8.c - 1.11 linux/sound/isa/sb/sb16.c - 1.13 linux/sound/isa/sb/es968.c - 1.12 linux/sound/isa/sb/emu8000.c - 1.9 linux/sound/isa/opti9xx/opti92x-ad1848.c - 1.13 linux/sound/isa/opl3sa2.c - 1.16 linux/sound/isa/gus/interwave.c - 1.14 linux/sound/isa/gus/gus_synth.c - 1.7 linux/sound/isa/gus/gus_irq.c - 1.5 linux/sound/isa/es18xx.c - 1.16 linux/sound/isa/cs423x/cs4236_lib.c - 1.6 linux/sound/isa/cs423x/cs4236.c - 1.15 linux/sound/isa/cs423x/cs4231_lib.c - 1.13 linux/sound/isa/cs423x/Makefile - 1.9 linux/sound/isa/cmi8330.c - 1.12 linux/sound/isa/azt2320.c - 1.11 linux/sound/isa/als100.c - 1.11 linux/sound/isa/ad1816a/ad1816a.c - 1.9 linux/sound/isa/Makefile - 1.9 linux/sound/i2c/cs8427.c - 1.7 linux/sound/i2c/Makefile - 1.10 linux/sound/drivers/opl3/opl3_lib.c - 1.8 linux/sound/drivers/opl3/Makefile - 1.12 linux/sound/drivers/mpu401/mpu401_uart.c - 1.13 linux/sound/drivers/mpu401/Makefile - 1.12 linux/sound/drivers/dummy.c - 1.14 linux/sound/drivers/Makefile - 1.7 linux/sound/core/timer.c - 1.15 linux/sound/core/sound_oss.c - 1.6 linux/sound/core/sound.c - 1.18 linux/sound/core/seq/seq_memory.c - 1.8 linux/sound/core/seq/seq_clientmgr.c - 1.13 linux/sound/core/seq/oss/seq_oss.c - 1.5 linux/sound/core/seq/instr/Makefile - 1.12 linux/sound/core/seq/Makefile - 1.18 linux/sound/core/rawmidi.c - 1.16 linux/sound/core/pcm_native.c - 1.18 linux/sound/core/pcm_lib.c - 1.14 linux/sound/core/pcm.c - 1.11 linux/sound/core/oss/pcm_oss.c - 1.18 linux/sound/core/oss/mixer_oss.c - 1.10 linux/sound/core/init.c - 1.12 linux/sound/core/info.c - 1.16 linux/sound/core/hwdep.c - 1.9 linux/sound/core/control.c - 1.13 linux/sound/core/Makefile - 1.19 linux/sound/Makefile - 1.15 linux/include/asm-x86_64/processor.h - 1.16 linux/include/asm-x86_64/pgtable.h - 1.17 linux/include/asm-x86_64/pci.h - 1.8 linux/include/asm-x86_64/mc146818rtc.h - 1.2 linux/include/asm-x86_64/hardirq.h - 1.5 linux/include/asm-x86_64/fixmap.h - 1.4 linux/include/asm-x86_64/cpufeature.h - 1.4 linux/include/asm-x86_64/checksum.h - 1.4 linux/include/asm-x86_64/bootsetup.h - 1.3 linux/include/asm-x86_64/apicdef.h - 1.3 linux/include/asm-x86_64/apic.h - 1.7 linux/include/sound/version.h - 1.18 linux/include/sound/sndmagic.h - 1.8 linux/include/sound/sb.h - 1.7 linux/include/sound/pcm.h - 1.12 linux/include/sound/mpu401.h - 1.7 linux/include/sound/initval.h - 1.9 linux/include/sound/info.h - 1.7 linux/include/sound/cs8427.h - 1.2 linux/include/sound/core.h - 1.18 linux/include/sound/asequencer.h - 1.4 linux/include/sound/ac97_codec.h - 1.14 linux/include/asm-x86_64/smp.h - 1.7 linux/include/asm-ppc/thread_info.h - 1.8 linux/include/asm-alpha/thread_info.h - 1.6 linux/include/asm-x86_64/vsyscall.h - 1.6 linux/include/asm-x86_64/uaccess.h - 1.8 linux/include/asm-x86_64/timex.h - 1.7 linux/include/asm-x86_64/thread_info.h - 1.10 linux/arch/ppc64/mm/init.c - 1.16 linux/include/asm-ppc64/elf.h - 1.9 linux/arch/ppc64/boot/Makefile - 1.12 linux/arch/ppc64/boot/main.c - 1.6 linux/arch/ppc64/boot/zlib.c - 1.3 linux/arch/ppc64/defconfig - 1.17 linux/arch/ppc64/kernel/Makefile - 1.18 linux/arch/ppc64/kernel/align.c - 1.8 linux/arch/ppc64/kernel/chrp_setup.c - 1.15 linux/arch/ppc64/kernel/head.S - 1.14 linux/arch/ppc64/kernel/htab.c - 1.13 linux/arch/ppc64/kernel/iSeries_pci.c - 1.9 linux/arch/ppc64/kernel/iSeries_setup.c - 1.11 linux/arch/ppc64/kernel/ioctl32.c - 1.20 linux/arch/ppc64/kernel/irq.c - 1.12 linux/arch/ppc64/kernel/misc.S - 1.21 linux/arch/ppc64/kernel/pSeries_pci.c - 1.12 linux/arch/ppc64/kernel/pacaData.c - 1.6 linux/arch/ppc64/kernel/pci.c - 1.14 linux/arch/ppc64/kernel/pci_dma.c - 1.10 linux/arch/ppc64/kernel/process.c - 1.17 linux/arch/ppc64/kernel/prom.c - 1.15 linux/arch/ppc64/kernel/ras.c - 1.5 linux/arch/ppc64/kernel/setup.c - 1.13 linux/arch/ppc64/kernel/signal.c - 1.16 linux/arch/ppc64/kernel/signal32.c - 1.17 linux/arch/ppc64/kernel/smp.c - 1.19 linux/arch/ppc64/kernel/stab.c - 1.8 linux/arch/ppc64/kernel/sys32.S - 1.10 linux/arch/ppc64/kernel/sys_ppc32.c - 1.23 linux/arch/ppc64/kernel/syscalls.c - 1.9 linux/arch/ppc64/kernel/traps.c - 1.14 linux/arch/ppc64/lib/Makefile - 1.9 linux/arch/ppc64/lib/string.S - 1.7 linux/include/asm-ppc64/machdep.h - 1.11 linux/include/asm-ppc64/module.h - 1.4 linux/include/asm-ppc64/unistd.h - 1.16 linux/include/asm-ppc64/thread_info.h - 1.8 linux/include/asm-ppc64/uaccess.h - 1.7 linux/include/asm-ppc64/system.h - 1.11 linux/include/asm-ppc64/smp.h - 1.7 linux/include/asm-ppc64/signal.h - 1.6 linux/include/asm-ppc64/processor.h - 1.16 linux/include/asm-ppc64/pgtable.h - 1.13 linux/include/asm-ppc64/pci.h - 1.6 linux/include/asm-ppc64/pci-bridge.h - 1.7 linux/drivers/net/e1000/e1000_main.c - 1.21 linux/include/asm-arm/thread_info.h - 1.7 linux/drivers/net/tokenring/3c359.c - 1.7 linux/drivers/hotplug/ibmphp_res.c - 1.6 linux/drivers/hotplug/ibmphp_pci.c - 1.5 linux/Documentation/filesystems/jfs.txt - 1.5 linux/drivers/hotplug/ibmphp_hpc.c - 1.8 linux/drivers/hotplug/ibmphp_ebda.c - 1.7 linux/drivers/hotplug/ibmphp_core.c - 1.14 linux/drivers/hotplug/ibmphp.h - 1.5 linux/fs/jfs/inode.c - 1.22 linux/fs/jfs/jfs_dmap.c - 1.13 linux/fs/jfs/namei.c - 1.17 linux/fs/jfs/jfs_xtree.c - 1.10 linux/arch/arm/mach-footbridge/isa-irq.c - 1.6 linux/fs/jfs/super.c - 1.23 linux/arch/arm/mach-sa1100/badge4.c - 1.11 linux/drivers/net/tg3.c - 1.22 linux/drivers/net/tulip/de4x5.c - 1.14 linux/Documentation/sound/alsa/CMIPCI.txt - 1.4 linux/drivers/net/e100/e100_main.c - 1.21 linux/fs/jffs2/wbuf.c - 1.6 linux/fs/jffs2/os-linux.h - 1.8 linux/fs/jffs2/fs.c - 1.7 linux/include/linux/netfilter_arp/arp_tables.h - 1.2 linux/fs/libfs.c - 1.15 linux/drivers/ieee1394/eth1394.c - 1.10 linux/drivers/net/tc35815.c - 1.10 linux/drivers/usb/image/microtek.c - 1.10 linux/drivers/usb/class/audio.c - 1.16 linux/drivers/usb/class/bluetty.c - 1.19 linux/drivers/usb/class/cdc-acm.c - 1.20 linux/drivers/usb/core/devices.c - 1.7 linux/drivers/usb/core/devio.c - 1.15 linux/include/asm-generic/percpu.h - 1.5 linux/drivers/usb/core/hcd.c - 1.23 linux/drivers/usb/core/hub.c - 1.26 linux/drivers/usb/core/hub.h - 1.7 linux/drivers/usb/core/inode.c - 1.15 linux/drivers/usb/input/hid-core.c - 1.21 linux/drivers/usb/core/usb.c - 1.34 linux/drivers/usb/media/konicawc.c - 1.12 linux/arch/arm/mach-pxa/lubbock.c - 1.9 linux/drivers/usb/host/ohci-q.c - 1.23 linux/drivers/usb/media/stv680.c - 1.13 linux/drivers/base/sys.c - 1.11 linux/drivers/base/power.c - 1.9 linux/drivers/base/base.h - 1.18 linux/drivers/usb/image/hpusbscsi.c - 1.12 linux/drivers/usb/image/hpusbscsi.h - 1.5 linux/drivers/usb/image/mdc800.c - 1.16 linux/drivers/usb/image/microtek.h - 1.4 linux/drivers/usb/image/scanner.c - 1.24 linux/drivers/usb/image/scanner.h - 1.17 linux/drivers/usb/input/hid-input.c - 1.10 linux/drivers/usb/input/hid.h - 1.9 linux/drivers/usb/input/hiddev.c - 1.16 linux/drivers/usb/input/usbkbd.c - 1.14 linux/drivers/usb/input/usbmouse.c - 1.12 linux/drivers/usb/input/wacom.c - 1.11 linux/drivers/usb/media/dabusb.c - 1.14 linux/drivers/ieee1394/eth1394.h - 1.7 linux/drivers/usb/media/dsbr100.c - 1.8 linux/drivers/usb/media/ibmcam.c - 1.9 linux/drivers/usb/media/ov511.c - 1.15 linux/drivers/usb/media/pwc-if.c - 1.11 linux/drivers/usb/serial/safe_serial.c - 1.11 linux/drivers/usb/media/se401.c - 1.16 linux/drivers/usb/net/usbnet.c - 1.21 linux/drivers/usb/net/rtl8150.c - 1.16 linux/drivers/usb/media/ultracam.c - 1.9 linux/drivers/usb/net/pegasus.h - 1.13 linux/drivers/usb/net/pegasus.c - 1.16 linux/drivers/usb/media/vicam.c - 1.14 linux/drivers/usb/net/kaweth.c - 1.17 linux/drivers/usb/net/cdc-ether.c - 1.13 linux/drivers/usb/net/catc.c - 1.9 linux/include/linux/percpu.h - 1.5 linux/drivers/usb/misc/auerswald.c - 1.18 linux/drivers/usb/misc/emi26.c - 1.7 linux/drivers/usb/misc/rio500.c - 1.12 linux/arch/ppc64/kernel/pSeries_htab.c - 1.5 linux/include/asm-ia64/percpu.h - 1.6 linux/drivers/isdn/i4l/isdn_tty.h - 1.4 linux/drivers/isdn/i4l/isdn_tty.c - 1.11 linux/arch/ia64/hp/sim/hpsim_console.c - 1.5 linux/arch/ia64/hp/sim/simserial.c - 1.12 linux/arch/ia64/hp/sim/simeth.c - 1.6 linux/arch/ia64/hp/common/sba_iommu.c - 1.10 linux/drivers/isdn/hardware/avm/avm_cs.c - 1.5 linux/drivers/isdn/capi/capi.c - 1.11 linux/include/sound/uda1341.h - 1.4 linux/drivers/scsi/aic7xxx/aic7xxx_core.c - 1.11 linux/drivers/char/synclinkmp.c - 1.10 linux/drivers/char/pcmcia/synclink_cs.c - 1.13 linux/sound/arm/sa11xx-uda1341.c - 1.11 linux/sound/i2c/l3/uda1341.c - 1.8 linux/drivers/macintosh/apm_emu.c - 1.7 linux/drivers/net/wan/pc300_tty.c - 1.8 linux/arch/i386/pci/common.c - 1.10 linux/drivers/net/wireless/ieee802_11.h - 1.3 linux/drivers/net/wireless/orinoco_pci.c - 1.5 linux/net/ipv6/ipv6_syms.c - 1.11 linux/arch/i386/pci/i386.c - 1.5 linux/arch/i386/pci/irq.c - 1.6 linux/drivers/pci/access.c - 1.4 linux/drivers/pci/hotplug.c - 1.12 linux/drivers/pci/pool.c - 1.9 linux/drivers/pci/power.c - 1.2 linux/drivers/pci/probe.c - 1.16 linux/fs/fs-writeback.c - 1.17 linux/include/linux/page-flags.h - 1.20 linux/net/bluetooth/sco.c - 1.11 linux/net/bluetooth/l2cap.c - 1.12 linux/mm/page-writeback.c - 1.25 linux/drivers/pci/search.c - 1.3 linux/include/asm-ppc64/paca.h - 1.4 linux/include/linux/writeback.h - 1.13 linux/include/net/bluetooth/sco.h - 1.2 linux/drivers/base/bus.c - 1.18 linux/drivers/base/driver.c - 1.12 linux/drivers/char/hvc_console.c - 1.12 linux/arch/ppc64/lib/copyuser.S - 1.4 linux/drivers/acpi/pci_root.c - 1.9 linux/drivers/acpi/pci_irq.c - 1.13 linux/drivers/acpi/thermal.c - 1.14 linux/drivers/acpi/processor.c - 1.21 linux/drivers/acpi/osl.c - 1.19 linux/drivers/usb/class/usb-midi.c - 1.14 linux/drivers/s390/net/lcs.c - 1.14 linux/arch/i386/kernel/suspend.c - 1.13 linux/include/asm-s390/thread_info.h - 1.5 linux/drivers/usb/input/aiptek.c - 1.11 linux/arch/x86_64/pci/x86-64.c - 1.4 linux/arch/x86_64/lib/csum-wrappers.c - 1.2 linux/arch/x86_64/lib/csum-partial.c - 1.2 linux/arch/x86_64/lib/csum-copy.S - 1.3 linux/arch/x86_64/lib/copy_page.S - 1.3 linux/arch/x86_64/lib/clear_page.S - 1.3 linux/arch/x86_64/pci/irq.c - 1.7 linux/arch/x86_64/lib/memcpy.S - 1.3 linux/arch/x86_64/lib/memset.S - 1.4 linux/net/llc/llc_if.c - 1.8 linux/include/asm-x86_64/suspend.h - 1.6 linux/arch/alpha/kernel/asm-offsets.c - 1.5 linux/arch/x86_64/kernel/asm-offsets.c - 1.4 linux/net/llc/llc_sap.c - 1.9 linux/net/llc/llc_mac.c - 1.10 linux/net/llc/llc_c_ac.c - 1.10 linux/net/llc/llc_main.c - 1.11 linux/net/llc/llc_conn.c - 1.10 linux/include/net/llc_c_ev.h - 1.6 linux/include/net/llc_conn.h - 1.8 linux/drivers/scsi/aic7xxx/aic7xxx_reg.h_shipped - 1.6 linux/sound/pci/rme9652/hdsp.c - 1.13 linux/drivers/scsi/aic7xxx/aic7xxx_seq.h_shipped - 1.6 linux/include/net/irda/af_irda.h - 1.4 linux/sound/pci/rme9652/hammerfall_mem.c - 1.10 linux/drivers/isdn/hisax/avma1_cs.c - 1.5 linux/drivers/acorn/char/defkeymap-acorn.c_shipped - 1.2 linux/drivers/usb/input/pid.c - 1.7 linux/drivers/usb/input/powermate.c - 1.10 linux/drivers/usb/input/xpad.c - 1.11 linux/drivers/usb/input/hid-lgff.c - 1.5 linux/security/security.c - 1.6 linux/security/dummy.c - 1.11 linux/security/capability.c - 1.9 linux/drivers/usb/serial/io_ti.c - 1.12 linux/drivers/serial/core.c - 1.14 linux/drivers/char/agp/frontend.c - 1.9 linux/drivers/serial/Makefile - 1.10 linux/drivers/char/agp/sworks-agp.c - 1.8 linux/kernel/cpu.c - 1.4 linux/include/asm-ppc64/mmzone.h - 1.8 linux/drivers/serial/8250.c - 1.16 linux/include/linux/serial_core.h - 1.14 linux/include/linux/security.h - 1.10 linux/include/asm-m68k/thread_info.h - 1.4 linux/fs/jfs/resize.c - 1.7 linux/drivers/serial/sunzilog.c - 1.12 linux/drivers/serial/sunsab.c - 1.7 linux/drivers/serial/sunsu.c - 1.13 linux/include/asm-sparc/thread_info.h - 1.4 linux/drivers/usb/misc/usblcd.c - 1.7 linux/fs/aio.c - 1.14 linux/arch/alpha/vmlinux.lds.S - 1.10 linux/arch/i386/kernel/cpu/mtrr/main.c - 1.4 linux/include/linux/aio.h - 1.7 linux/arch/mips64/vmlinux.lds.S - 1.4 linux/drivers/base/class.c - 1.12 linux/net/sctp/sysctl.c - 1.5 linux/include/net/sctp/user.h - 1.6 linux/net/sctp/protocol.c - 1.18 linux/include/net/sctp/sctp.h - 1.14 linux/net/sctp/associola.c - 1.14 linux/net/sctp/bind_addr.c - 1.10 linux/net/sctp/endpointola.c - 1.10 linux/net/sctp/input.c - 1.14 linux/net/sctp/ipv6.c - 1.16 linux/net/sctp/objcnt.c - 1.4 linux/net/sctp/output.c - 1.11 linux/net/sctp/outqueue.c - 1.13 linux/net/sctp/sm_make_chunk.c - 1.15 linux/net/sctp/sm_sideeffect.c - 1.16 linux/net/sctp/sm_statefuns.c - 1.15 linux/include/net/sctp/structs.h - 1.15 linux/net/sctp/sm_statetable.c - 1.8 linux/net/sctp/socket.c - 1.16 linux/net/sctp/transport.c - 1.10 linux/net/sctp/ulpqueue.c - 1.9 linux/arch/i386/mm/discontig.c - 1.9 linux/drivers/ide/setup-pci.c - 1.11 linux/drivers/ide/pci/pdc202xx_new.c - 1.12 linux/drivers/ide/pci/hpt366.c - 1.12 linux/drivers/ide/pci/cs5530.c - 1.8 linux/include/asm-um/thread_info.h - 1.4 linux/drivers/ide/legacy/pdc4030.c - 1.8 linux/drivers/ide/legacy/ide-cs.c - 1.6 linux/arch/um/drivers/daemon_kern.c - 1.4 linux/arch/um/drivers/line.c - 1.9 linux/arch/um/drivers/mcast_kern.c - 1.5 linux/arch/um/drivers/net_kern.c - 1.6 linux/arch/um/drivers/ssl.c - 1.6 linux/arch/um/drivers/stdio_console.c - 1.9 linux/arch/um/include/line.h - 1.5 linux/arch/um/kernel/irq.c - 1.8 linux/arch/um/os-Linux/drivers/ethertap_kern.c - 1.4 linux/arch/um/os-Linux/drivers/tuntap_kern.c - 1.4 linux/arch/um/sys-ppc/Makefile - 1.4 linux/include/asm-um/processor-ppc.h - 1.2 linux/arch/m68k/vmlinux-std.lds - 1.8 linux/drivers/char/vt_ioctl.c - 1.6 linux/arch/ppc64/vmlinux.lds.S - 1.8 linux/arch/x86_64/vmlinux.lds.S - 1.11 linux/arch/sparc64/vmlinux.lds.S - 1.10 linux/arch/sparc/vmlinux.lds.S - 1.11 linux/arch/cris/vmlinux.lds.S - 1.5 linux/arch/ppc/vmlinux.lds.S - 1.10 linux/arch/s390/vmlinux.lds.S - 1.12 linux/arch/mips/vmlinux.lds.S - 1.5 linux/arch/parisc/vmlinux.lds.S - 1.9 linux/arch/ppc/boot/common/mpc10x_memory.c - 1.4 linux/net/bridge/netfilter/ebtables.c - 1.10 linux/arch/ppc64/kernel/asm-offsets.c - 1.4 linux/net/bridge/netfilter/ebt_redirect.c - 1.3 linux/drivers/base/platform.c - 1.6 linux/arch/i386/mach-visws/visws_apic.c - 1.6 linux/arch/ppc/boot/of1275/Makefile - 1.4 linux/arch/ppc64/mm/numa.c - 1.4 linux/arch/ia64/pci/pci.c - 1.7 linux/drivers/pci/pci.h - 1.3 linux/drivers/block/deadline-iosched.c - 1.10 linux/drivers/base/cpu.c - 1.8 linux/include/linux/cpu.h - 1.5 linux/sound/sparc/cs4231.c - 1.5 linux/Documentation/vm/hugetlbpage.txt - 1.6 linux/include/asm-ppc64/topology.h - 1.7 linux/sound/pci/ac97/ac97_patch.h - 1.6 linux/sound/pci/ac97/ac97_patch.c - 1.8 linux/sound/isa/dt019x.c - 1.7 linux/kernel/cpufreq.c - 1.14 linux/net/llc/af_llc.c - 1.7 linux/include/linux/cpufreq.h - 1.14 linux/arch/i386/kernel/cpu/cpufreq/powernow-k6.c - 1.10 linux/arch/i386/kernel/cpu/cpufreq/speedstep.c - 1.11 linux/arch/i386/kernel/cpu/cpufreq/Makefile - 1.6 linux/arch/i386/kernel/cpu/cpufreq/longrun.c - 1.10 linux/sound/usb/usbquirks.h - 1.9 linux/sound/usb/usbmixer.c - 1.7 linux/sound/usb/usbaudio.h - 1.8 linux/sound/usb/usbaudio.c - 1.12 linux/sound/pci/via82xx.c - 1.11 linux/sound/pci/ice1712/ice1712.h - 1.7 linux/sound/pci/ice1712/ice1712.c - 1.9 linux/sound/pci/ice1712/ews.c - 1.7 linux/sound/pci/ice1712/delta.c - 1.6 linux/sound/pci/ice1712/ak4524.c - 1.8 linux/sound/pci/ice1712/Makefile - 1.6 linux/net/x25/x25_proc.c - 1.3 linux/net/llc/llc_proc.c - 1.7 linux/net/ipx/ipx_proc.c - 1.4 linux/drivers/scsi/nsp32.c - 1.9 linux/drivers/scsi/aacraid/linit.c - 1.12 linux/drivers/mtd/maps/scx200_docflash.c - 1.2 linux/net/bluetooth/bnep/netdev.c - 1.3 linux/net/bluetooth/rfcomm/tty.c - 1.9 linux/net/bluetooth/rfcomm/sock.c - 1.10 linux/net/bluetooth/rfcomm/core.c - 1.11 linux/net/bluetooth/bnep/sock.c - 1.7 linux/net/bluetooth/bnep/core.c - 1.10 linux/include/net/bluetooth/rfcomm.h - 1.7 linux/net/appletalk/atalk_proc.c - 1.4 linux/drivers/net/irda/donauboe.c - 1.6 linux/fs/cifs/cifsfs.c - 1.10 linux/fs/cifs/connect.c - 1.10 linux/arch/alpha/kernel/systbls.S - 1.5 linux/fs/cifs/netmisc.c - 1.6 linux/fs/cifs/smberr.h - 1.2 linux/arch/um/drivers/pcap_kern.c - 1.3 linux/drivers/isdn/hardware/eicon/divamnt.c - 1.5 linux/drivers/mtd/cmdline.c - 1.4 linux/sound/usb/usbmixer_maps.c - 1.3 linux/drivers/mtd/maps/autcpu12-nvram.c - 1.3 linux/drivers/mtd/maps/ceiva.c - 1.3 linux/drivers/mtd/maps/edb7312.c - 1.3 linux/drivers/mtd/maps/epxa10db-flash.c - 1.4 linux/drivers/mtd/maps/fortunet.c - 1.3 linux/net/rxrpc/transport.c - 1.3 linux/drivers/mtd/maps/impa7.c - 1.3 linux/drivers/mtd/maps/pci.c - 1.3 linux/drivers/mtd/maps/pcmciamtd.c - 1.4 linux/drivers/mtd/mtdconcat.c - 1.2 linux/drivers/oprofile/buffer_sync.c - 1.13 linux/drivers/oprofile/event_buffer.h - 1.5 linux/drivers/oprofile/oprof.c - 1.7 linux/include/asm-x86_64/proto.h - 1.10 linux/fs/nfs/nfs4state.c - 1.3 linux/kernel/rcupdate.c - 1.4 linux/include/linux/oprofile.h - 1.5 linux/arch/i386/oprofile/nmi_int.c - 1.10 linux/drivers/block/scsi_ioctl.c - 1.10 linux/arch/x86_64/kernel/pci-gart.c - 1.9 linux/drivers/block/ioctl.c - 1.5 linux/arch/x86_64/kernel/reboot.c - 1.5 linux/drivers/pnp/pnpbios/core.c - 1.12 linux/drivers/pnp/resource.c - 1.10 linux/fs/sysfs/inode.c - 1.11 linux/include/linux/sysfs.h - 1.9 linux/drivers/pnp/isapnp/core.c - 1.12 linux/drivers/pnp/pnpbios/proc.c - 1.4 linux/include/linux/kobject.h - 1.10 linux/sound/isa/Kconfig - 1.4 linux/drivers/mtd/nand/Kconfig - 1.2 linux/drivers/mtd/maps/Kconfig - 1.5 linux/drivers/net/Kconfig - 1.14 linux/drivers/mtd/devices/Kconfig - 1.2 linux/drivers/mtd/chips/Kconfig - 1.2 linux/Documentation/kobject.txt - 1.6 linux/drivers/mtd/Kconfig - 1.2 linux/sound/core/Kconfig - 1.2 linux/arch/alpha/Kconfig - 1.12 linux/arch/arm/Kconfig - 1.12 linux/sound/Kconfig - 1.3 linux/security/Kconfig - 1.5 linux/drivers/md/dm-linear.c - 1.5 linux/scripts/kconfig/zconf.y - 1.4 linux/scripts/kconfig/zconf.tab.c_shipped - 1.5 linux/scripts/kconfig/zconf.l - 1.5 linux/scripts/kconfig/symbol.c - 1.4 linux/scripts/kconfig/qconf.h - 1.4 linux/scripts/kconfig/qconf.cc - 1.5 linux/scripts/kconfig/menu.c - 1.5 linux/scripts/kconfig/mconf.c - 1.5 linux/scripts/kconfig/lkc_proto.h - 1.2 linux/net/ipv4/Kconfig - 1.7 linux/arch/i386/Kconfig - 1.19 linux/net/bridge/br_netfilter.c - 1.7 linux/scripts/kconfig/lkc.h - 1.3 linux/drivers/media/video/Kconfig - 1.5 linux/drivers/net/wireless/Kconfig - 1.7 linux/scripts/kconfig/lex.zconf.c_shipped - 1.5 linux/scripts/kconfig/expr.h - 1.5 linux/scripts/kconfig/expr.c - 1.2 linux/scripts/kconfig/confdata.c - 1.4 linux/scripts/kconfig/conf.c - 1.5 linux/include/linux/device-mapper.h - 1.3 linux/arch/ia64/Kconfig - 1.11 linux/scripts/Makefile.lib - 1.7 linux/sound/oss/dmasound/Kconfig - 1.2 linux/include/asm-parisc/thread_info.h - 1.3 linux/scripts/Makefile.build - 1.11 linux/drivers/char/Kconfig - 1.9 linux/drivers/pcmcia/Kconfig - 1.5 linux/drivers/md/dm.h - 1.4 linux/drivers/md/dm.c - 1.7 linux/drivers/md/dm-target.c - 1.5 linux/drivers/md/dm-table.c - 1.7 linux/drivers/md/dm-stripe.c - 1.5 linux/drivers/md/dm-ioctl.c - 1.10 linux/drivers/scsi/Kconfig - 1.13 linux/drivers/char/agp/Kconfig - 1.10 linux/arch/ppc/Kconfig - 1.11 linux/arch/ppc64/Kconfig - 1.10 linux/net/ipv4/ah.c - 1.11 linux/drivers/hotplug/Kconfig - 1.5 linux/drivers/hotplug/acpiphp.h - 1.4 linux/drivers/hotplug/acpiphp_core.c - 1.3 linux/arch/sh/Kconfig - 1.9 linux/drivers/hotplug/acpiphp_glue.c - 1.9 linux/drivers/hotplug/acpiphp_pci.c - 1.4 linux/drivers/hotplug/acpiphp_res.c - 1.3 linux/drivers/i2c/Kconfig - 1.6 linux/arch/sparc64/Kconfig - 1.13 linux/drivers/ide/Kconfig - 1.10 linux/arch/x86_64/Kconfig - 1.15 linux/sound/pci/Kconfig - 1.5 linux/fs/Kconfig - 1.14 linux/lib/kobject.c - 1.9 linux/crypto/Kconfig - 1.8 linux/drivers/serial/Kconfig - 1.8 linux/drivers/video/Kconfig - 1.11 linux/drivers/usb/serial/Kconfig - 1.7 linux/net/ipv6/Kconfig - 1.5 linux/drivers/usb/core/Kconfig - 1.3 linux/include/net/xfrm.h - 1.13 linux/fs/hugetlbfs/inode.c - 1.11 linux/fs/eventpoll.c - 1.10 linux/include/linux/node.h - 1.2 linux/include/linux/hugetlb.h - 1.9 linux/include/asm-v850/thread_info.h - 1.3 linux/drivers/mtd/maps/uclinux.c - 1.3 linux/include/asm-i386/node.h - 1.3 linux/include/asm-i386/memblk.h - 1.3 linux/include/asm-i386/cpu.h - 1.3 linux/include/asm-v850/sim.h - 1.4 linux/drivers/base/node.c - 1.8 linux/drivers/base/memblk.c - 1.6 linux/drivers/base/firmware.c - 1.5 linux/include/asm-m68knommu/thread_info.h - 1.3 linux/arch/v850/vmlinux.lds.S - 1.8 linux/arch/v850/lib/Makefile - 1.3 linux/arch/m68knommu/Kconfig - 1.10 linux/arch/m68knommu/kernel/Makefile - 1.5 linux/arch/m68knommu/kernel/ints.c - 1.4 linux/arch/m68knommu/kernel/process.c - 1.3 linux/arch/m68knommu/kernel/setup.c - 1.4 linux/arch/m68knommu/lib/Makefile - 1.3 linux/arch/m68knommu/mm/memory.c - 1.2 linux/arch/m68knommu/platform/5206/ARNEWSH/crt0_ram.S - 1.2 linux/arch/m68knommu/platform/5206/config.c - 1.4 linux/arch/m68knommu/platform/5206e/config.c - 1.4 linux/arch/m68knommu/platform/5307/Makefile - 1.5 linux/arch/m68knommu/platform/68328/entry.S - 1.5 linux/arch/m68knommu/platform/68328/pilot/crt0_rom.S - 1.3 linux/arch/m68knommu/platform/68VZ328/de2/config.c - 1.4 linux/arch/m68knommu/vmlinux.lds.S - 1.8 linux/arch/v850/kernel/simcons.c - 1.5 linux/arch/v850/kernel/rte_mb_a_pci.c - 1.6 linux/include/asm-v850/rte_cb.h - 1.3 linux/arch/v850/kernel/rte_ma1_cb.c - 1.4 linux/arch/v850/kernel/rte_cb_multi.c - 1.5 linux/arch/v850/kernel/rte_cb_leds.c - 1.3 linux/arch/v850/kernel/ptrace.c - 1.2 linux/arch/v850/kernel/process.c - 1.5 linux/include/asm-v850/nb85e_cache.h - 1.3 linux/arch/v850/kernel/memcons.c - 1.4 linux/arch/v850/kernel/mach.h - 1.3 linux/arch/v850/kernel/ma.c - 1.3 linux/arch/v850/kernel/irq.c - 1.7 linux/include/asm-v850/bitops.h - 1.3 linux/arch/v850/kernel/head.S - 1.3 linux/arch/v850/kernel/entry.S - 1.6 linux/arch/v850/Kconfig - 1.10 linux/Documentation/kbuild/kconfig-language.txt - 1.3 linux/drivers/hotplug/cpcihp_zt5550.h - 1.2 linux/drivers/hotplug/cpcihp_zt5550.c - 1.2 linux/drivers/hotplug/cpcihp_generic.c - 1.2 linux/drivers/hotplug/cpci_hotplug_pci.c - 1.6 linux/drivers/hotplug/cpci_hotplug_core.c - 1.6 linux/drivers/hotplug/cpci_hotplug.h - 1.2 linux/drivers/serial/68328serial.c - 1.6 linux/drivers/serial/68328serial.h - 1.4 linux/drivers/serial/68360serial.c - 1.10 linux/drivers/serial/mcfserial.c - 1.8 linux/drivers/serial/mcfserial.h - 1.3 linux/drivers/serial/nb85e_uart.c - 1.7 linux/arch/ppc/syslib/prom.c - 1.3 linux/net/key/af_key.c - 1.12 linux/arch/ppc/syslib/Makefile - 1.6 linux/net/ipv4/esp.c - 1.11 linux/drivers/scsi/scsi_sysfs.c - 1.10 linux/security/root_plug.c - 1.3 linux/drivers/s390/char/sclp_con.c - 1.5 linux/drivers/s390/char/sclp_tty.c - 1.8 linux/drivers/s390/char/sclp_tty.h - 1.4 linux/Documentation/scsi/aic7xxx.txt - 1.5 linux/Documentation/scsi/scsi_mid_low_api.txt - 1.4 linux/drivers/usb/serial/bus.c - 1.7 linux/drivers/usb/serial/kobil_sct.c - 1.8 linux/drivers/char/agp/amd-k8-agp.c - 1.8 linux/drivers/char/agp/generic.c - 1.8 linux/drivers/char/agp/intel-agp.c - 1.9 linux/arch/ppc/kernel/module.c - 1.6 linux/drivers/ieee1394/iso.c - 1.6 linux/drivers/char/watchdog/i810-tco.c - 1.5 linux/kernel/compat.c - 1.7 linux/drivers/net/r8169.c - 1.6 linux/include/linux/xfrm.h - 1.6 linux/arch/v850/as85ep1-rom.ld - 1.2 linux/arch/x86_64/kernel/suspend.c - 1.5 linux/Documentation/sound/alsa/ALSA-Configuration.txt - 1.5 linux/drivers/i2c/chips/Kconfig - 1.6 linux/drivers/i2c/chips/Makefile - 1.4 linux/sound/pci/ice1712/envy24ht.h - 1.3 linux/drivers/scsi/aic7xxx/aic79xx.h - 1.6 linux/drivers/scsi/aic7xxx/aic79xx.reg - 1.6 linux/drivers/scsi/aic7xxx/aic79xx.seq - 1.5 linux/drivers/scsi/aic7xxx/aic79xx_core.c - 1.7 linux/include/asm-i386/mach-summit/mach_mpparse.h - 1.6 linux/include/asm-i386/mach-summit/mach_apic.h - 1.7 linux/include/asm-i386/mach-numaq/mach_apic.h - 1.6 linux/drivers/scsi/aic7xxx/aic79xx_inline.h - 1.5 linux/drivers/scsi/aic7xxx/aic79xx_osm.c - 1.9 linux/drivers/scsi/aic7xxx/aic79xx_osm.h - 1.7 linux/drivers/scsi/aic7xxx/aic79xx_osm_pci.c - 1.5 linux/drivers/scsi/aic7xxx/aic79xx_pci.c - 1.7 linux/drivers/scsi/aic7xxx/aic79xx_proc.c - 1.4 linux/drivers/scsi/aic7xxx/aic79xx_reg.h_shipped - 1.5 linux/include/asm-arm/dma-mapping.h - 1.5 linux/drivers/scsi/aic7xxx/aic79xx_reg_print.c_shipped - 1.5 linux/drivers/scsi/aic7xxx/aic79xx_seq.h_shipped - 1.5 linux/drivers/scsi/aic7xxx/aic7xxx_osm.c - 1.11 linux/drivers/scsi/aic7xxx/aic7xxx_osm_pci.c - 1.5 linux/drivers/scsi/aic7xxx/aiclib.h - 1.5 linux/drivers/video/i810/i810.h - 1.5 linux/drivers/video/i810/i810_main.c - 1.6 linux/drivers/video/i810/i810_main.h - 1.5 linux/include/asm-ppc/ocp.h - 1.3 linux/drivers/net/amd8111e.c - 1.5 linux/drivers/net/amd8111e.h - 1.2 linux/include/asm-parisc/bug.h - 1.4 linux/include/linux/sunrpc/rpc_pipe_fs.h - 1.3 linux/include/asm-ia64/bug.h - 1.2 linux/net/sunrpc/rpc_pipe.c - 1.8 linux/arch/i386/kernel/cpu/cpufreq/gx-suspmod.c - 1.7 linux/net/sunrpc/auth_gss/gss_mech_switch.c - 1.2 linux/net/sunrpc/auth_gss/auth_gss.c - 1.4 linux/include/asm-sh/bug.h - 1.2 linux/include/asm-i386/mach-bigsmp/mach_apic.h - 1.5 linux/include/asm-mips64/bug.h - 1.2 linux/include/asm-i386/bug.h - 1.3 linux/include/asm-cris/bug.h - 1.2 linux/include/asm-sparc/bug.h - 1.3 linux/include/asm-s390/bug.h - 1.2 linux/include/asm-arm/bug.h - 1.3 linux/include/asm-alpha/bug.h - 1.2 linux/include/asm-sparc64/bug.h - 1.3 linux/include/linux/sunrpc/gss_api.h - 1.2 linux/include/asm-ppc/bug.h - 1.3 linux/include/asm-m68k/bug.h - 1.2 linux/include/asm-mips/bug.h - 1.2 linux/crypto/sha512.c - 1.2 linux/include/asm-x86_64/bug.h - 1.2 linux/arch/ppc64/kernel/module.c - 1.4 linux/arch/alpha/kernel/core_marvel.c - 1.7 linux/include/asm-generic/vmlinux.lds.h - 1.3 linux/include/asm-ppc64/bug.h - 1.2 linux/include/asm-alpha/agp_backend.h - 1.3 linux/include/asm-m68knommu/bug.h - 1.2 linux/arch/arm/common/Makefile - 1.2 linux/include/asm-um/bug.h - 1.2 linux/Documentation/sound/alsa/DocBook/writing-an-alsa-driver.tmpl - 1.6 linux/Documentation/sound/alsa/OSS-Emulation.txt - 1.2 linux/arch/i386/kernel/cpu/cpufreq/acpi.c - 1.5 linux/arch/alpha/kernel/srmcons.c - 1.3 linux/arch/arm/common/sa1111.c - 1.7 linux/drivers/cpufreq/proc_intf.c - 1.3 linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c - 1.5 linux/drivers/acpi/sleep/main.c - 1.3 linux/drivers/usb/input/hid-tmff.c - 1.3 linux/drivers/net/tokenring/proteon.c - 1.2 linux/drivers/net/tokenring/skisa.c - 1.2 linux/arch/i386/kernel/cpu/cpufreq/Kconfig - 1.3 linux/kernel/posix-timers.c - 1.9 linux/include/asm-v850/bug.h - 1.2 linux/Documentation/cpu-freq/user-guide.txt - 1.3 linux/drivers/base/init.c - 1.2 linux/drivers/char/watchdog/amd7xx_tco.c - 1.3 linux/net/sctp/proc.c - 1.3 linux/fs/sysfs/bin.c - 1.5 linux/drivers/hotplug/cpqphp_sysfs.c - 1.2 linux/drivers/scsi/scsi_pc98.c - 1.3 linux/drivers/usb/input/kbtab.c - 1.3 linux/fs/sysfs/file.c - 1.4 linux/drivers/pci/bus.c - 1.4 linux/scripts/kconfig/gconf.c - 1.4 linux/drivers/char/hw_random.c - 1.4 linux/arch/ia64/sn/io/sn2/pci_bus_cvlink.c - 1.3 linux/arch/arm/kernel/pm.c - 1.3 linux/net/ipv6/esp6.c - 1.7 linux/sound/pci/ice1712/revo.c - 1.2 linux/sound/pci/ice1712/ice1724.c - 1.3 linux/sound/core/sgbuf.c - 1.4 linux/sound/core/memalloc.c - 1.4 linux/net/ipv6/xfrm6_policy.c - 1.4 linux/net/ipv4/xfrm4_policy.c - 1.3 linux/net/ipv4/xfrm4_input.c - 1.4 linux/drivers/video/cirrusfb.c - 1.4 linux/drivers/video/aty/aty128fb.c - 1.4 linux/net/xfrm/xfrm_user.c - 1.3 linux/net/xfrm/xfrm_state.c - 1.4 linux/net/xfrm/xfrm_policy.c - 1.4 linux/drivers/pcmcia/sa11xx_core.h - 1.2 linux/drivers/pcmcia/sa11xx_core.c - 1.3 linux/drivers/i2c/chips/w83781d.c - 1.5 linux/arch/arm/lib/div64.S - 1.2 linux/arch/x86_64/kernel/acpi/boot.c - 1.2 linux/include/video/edid.h - 1.2 linux/drivers/mtd/maps/iq80321.c - 1.3 linux/include/asm-h8300/bug.h - 1.2 linux/arch/h8300/lib/Makefile - 1.2 linux/arch/h8300/platform/h8300h/generic/rom.ld - 1.2 linux/net/ipv4/xfrm4_tunnel.c - 1.4 linux/fs/nfs/idmap.c - 1.2 linux/arch/ia64/kernel/module.c - 1.2 linux/net/ipv4/ipcomp.c - 1.4 linux/include/asm-h8300/thread_info.h - 1.2 linux/include/asm-arm/arch-iop3xx/iop321.h - 1.3 linux/include/asm-h8300/pci.h - 1.2 linux/Documentation/scsi/dc395x.txt - 1.2 linux/drivers/net/ixgb/ixgb_main.c - 1.3 linux/drivers/scsi/dc395x.c - 1.3 linux/include/linux/compat_ioctl.h - 1.3 linux/include/asm-i386/mach-generic/mach_apic.h - 1.2 linux/drivers/net/bonding/bond_3ad.c - 1.2 linux/dev/null - 1.2 linux/drivers/net/bonding/bond_main.c - 1.2 linux/drivers/usb/gadget/net2280.c - 1.2 linux/drivers/usb/gadget/ether.c - 1.2 linux/net/ipx/ipx_route.c - 1.2 linux/drivers/atm/he.c - 1.2 linux/drivers/scsi/scsi_priv.h - 1.2 linux/drivers/scsi/scsi_devinfo.h - 1.2 linux/drivers/scsi/scsi_devinfo.c - 1.2 linux/drivers/char/agp/isoch.c - 1.2 linux/drivers/scsi/arm/acornscsi.c - 1.2 linux/drivers/scsi/arm/arxescsi.c - 1.2 linux/drivers/scsi/arm/cumana_1.c - 1.2 linux/drivers/scsi/arm/cumana_2.c - 1.2 linux/drivers/scsi/arm/ecoscsi.c - 1.2 linux/drivers/scsi/arm/eesox.c - 1.2 linux/net/ipv6/ipcomp6.c - 1.2 linux/drivers/scsi/arm/oak.c - 1.2 linux/drivers/scsi/arm/powertec.c - 1.2 linux/net/atm/br2684.c - 1.2 linux/net/core/flow.c - 1.2 linux/arch/i386/mach-generic/default.c - 1.2 linux/net/core/net-sysfs.c - 1.2 linux/net/decnet/netfilter/dn_rtmsg.c - 1.2 From owner-linux-xfs@oss.sgi.com Tue Jun 17 10:11:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 10:12:06 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HHBi2x001688 for ; Tue, 17 Jun 2003 10:11:45 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5HHSOmO021001 for ; Tue, 17 Jun 2003 12:28:24 -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 h5HHBcqX5012403 for ; Tue, 17 Jun 2003 12:11:38 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5HHBcRn126068494 for ; Tue, 17 Jun 2003 12:11:38 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5HHBci22073; Tue, 17 Jun 2003 12:11:38 -0500 Message-Id: <200306171711.h5HHBci22073@jen.americas.sgi.com> Date: Tue, 17 Jun 2003 12:11:38 -0500 Subject: TAKE - merge up to 2.5.72 To: linux-xfs@oss.sgi.com X-archive-position: 4369 X-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 Date: Tue Jun 17 10:09:40 PDT 2003 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.5 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:151346a linux/include/asm-i386/mach-numaq/mach_mpspec.h - 1.1 linux/include/asm-i386/mach-es7000/mach_apic.h - 1.1 linux/include/asm-i386/mach-es7000/mach_apicdef.h - 1.1 linux/arch/sh/tools/machgen.sh - 1.1 linux/drivers/input/serio/pcips2.c - 1.1 linux/drivers/input/mouse/synaptics.h - 1.1 linux/drivers/input/mouse/synaptics.c - 1.1 linux/include/asm-i386/mach-bigsmp/mach_mpspec.h - 1.1 linux/arch/sh/tools/Makefile - 1.1 linux/drivers/input/mouse/psmouse.h - 1.1 linux/arch/i386/mach-es7000/es7000.h - 1.1 linux/arch/i386/mach-es7000/es7000.c - 1.1 linux/drivers/input/mouse/psmouse-base.c - 1.1 linux/arch/sh/tools/mach-types - 1.1 linux/arch/i386/mach-es7000/setup.c - 1.1 linux/include/asm-i386/mpspec_def.h - 1.1 linux/include/asm-i386/mach-summit/mach_mpspec.h - 1.1 linux/include/asm-i386/mach-es7000/mach_ipi.h - 1.1 linux/include/asm-i386/mach-es7000/mach_wakecpu.h - 1.1 linux/arch/i386/mach-es7000/Makefile - 1.1 linux/include/asm-i386/mach-es7000/mach_mpparse.h - 1.1 linux/arch/i386/mach-es7000/topology.c - 1.1 linux/include/asm-i386/mach-default/mach_mpspec.h - 1.1 linux/include/asm-i386/mach-generic/mach_mpspec.h - 1.1 linux/include/asm-i386/mach-es7000/mach_mpspec.h - 1.1 linux/net/x25/af_x25.c - 1.36 linux/net/unix/garbage.c - 1.15 linux/net/unix/af_unix.c - 1.59 linux/net/socket.c - 1.59 linux/net/rose/af_rose.c - 1.33 linux/net/packet/af_packet.c - 1.44 linux/net/netrom/af_netrom.c - 1.31 linux/net/netlink/af_netlink.c - 1.31 linux/net/ipx/af_ipx.c - 1.39 linux/net/ipv6/udp.c - 1.43 linux/net/ipv6/tcp_ipv6.c - 1.54 linux/net/ipv6/raw.c - 1.36 linux/net/ipv6/ip6_input.c - 1.20 linux/net/ipv6/icmp.c - 1.31 linux/net/ipv4/udp.c - 1.45 linux/net/ipv4/tcp_timer.c - 1.30 linux/net/ipv4/tcp_ipv4.c - 1.64 linux/net/ipv4/tcp.c - 1.58 linux/net/ipv4/route.c - 1.51 linux/net/ipv4/raw.c - 1.35 linux/net/ipv4/ip_input.c - 1.25 linux/net/ipv4/icmp.c - 1.41 linux/net/ipv4/af_inet.c - 1.56 linux/net/core/dev.c - 1.76 linux/net/ax25/af_ax25.c - 1.34 linux/net/appletalk/ddp.c - 1.30 linux/mm/vmscan.c - 1.130 linux/kernel/time.c - 1.18 linux/kernel/sysctl.c - 1.68 linux/kernel/sched.c - 1.103 linux/kernel/fork.c - 1.92 linux/init/main.c - 1.109 linux/include/net/x25.h - 1.15 linux/include/net/udp.h - 1.16 linux/include/net/tcp.h - 1.48 linux/include/net/sock.h - 1.49 linux/include/net/route.h - 1.25 linux/include/net/rawv6.h - 1.6 linux/include/net/raw.h - 1.6 linux/include/net/ipx.h - 1.13 linux/include/net/af_unix.h - 1.9 linux/include/linux/timex.h - 1.9 linux/include/linux/time.h - 1.16 linux/include/linux/slab.h - 1.33 linux/include/linux/netdevice.h - 1.47 linux/include/linux/list.h - 1.30 linux/include/linux/ioport.h - 1.17 linux/include/linux/blkdev.h - 1.86 linux/include/linux/atalk.h - 1.10 linux/include/linux/arcdevice.h - 1.11 linux/include/asm-sparc/timer.h - 1.3 linux/include/asm-ppc/unistd.h - 1.33 linux/include/asm-i386/timex.h - 1.7 linux/include/asm-alpha/ide.h - 1.15 linux/fs/inode.c - 1.99 linux/drivers/scsi/sr.c - 1.68 linux/drivers/scsi/sd.c - 1.88 linux/drivers/net/slip.c - 1.27 linux/drivers/net/eepro100.c - 1.60 linux/drivers/net/Space.c - 1.45 linux/drivers/char/rtc.c - 1.42 linux/drivers/char/keyboard.c - 1.36 linux/drivers/char/epca.c - 1.30 linux/arch/sparc64/kernel/time.c - 1.34 linux/arch/sparc64/kernel/sys_sparc32.c - 1.75 linux/arch/sparc64/defconfig - 1.95 linux/arch/sparc/kernel/time.c - 1.27 linux/arch/sparc/kernel/pcic.c - 1.29 linux/arch/ppc/kernel/time.c - 1.26 linux/arch/ppc/defconfig - 1.46 linux/arch/m68k/kernel/time.c - 1.12 linux/arch/i386/kernel/time.c - 1.41 linux/arch/i386/kernel/io_apic.c - 1.63 linux/arch/i386/Makefile - 1.53 linux/arch/arm/kernel/time.c - 1.26 linux/arch/alpha/kernel/time.c - 1.31 linux/arch/alpha/kernel/osf_sys.c - 1.39 linux/Makefile - 1.249 linux/net/decnet/dn_nsp_in.c - 1.23 linux/net/decnet/af_decnet.c - 1.42 linux/include/linux/ide.h - 1.80 linux/fs/efs/super.c - 1.21 linux/include/asm-i386/apic.h - 1.22 linux/drivers/net/ppp_generic.c - 1.39 linux/drivers/net/fc/iph5526.c - 1.28 linux/arch/sh/kernel/time.c - 1.20 linux/drivers/pcmcia/tcic.c - 1.28 linux/drivers/pcmcia/rsrc_mgr.c - 1.22 linux/drivers/pcmcia/i82365.c - 1.41 linux/drivers/pcmcia/ds.c - 1.30 linux/drivers/pcmcia/cs_internal.h - 1.18 linux/drivers/pcmcia/cs.c - 1.40 linux/drivers/pcmcia/cistpl.c - 1.21 linux/include/pcmcia/ss.h - 1.15 linux/drivers/pcmcia/cardbus.c - 1.33 linux/drivers/pcmcia/bulkmem.c - 1.18 linux/drivers/pcmcia/yenta.h - 1.6 linux/include/asm-ppc/pci.h - 1.22 linux/fs/proc/proc_misc.c - 1.63 linux/arch/ppc/configs/walnut_defconfig - 1.22 linux/arch/ppc/configs/pmac_defconfig - 1.13 linux/arch/ppc/configs/oak_defconfig - 1.22 linux/arch/ppc/configs/mbx_defconfig - 1.17 linux/arch/ppc/configs/gemini_defconfig - 1.24 linux/arch/ppc/configs/common_defconfig - 1.34 linux/arch/ppc/configs/apus_defconfig - 1.21 linux/kernel/timer.c - 1.47 linux/drivers/pcmcia/yenta.c - 1.42 linux/include/linux/input.h - 1.27 linux/drivers/net/arcnet/rfc1201.c - 1.8 linux/drivers/net/arcnet/rfc1051.c - 1.6 linux/drivers/net/arcnet/arcnet.c - 1.18 linux/drivers/net/arcnet/arc-rawmode.c - 1.6 linux/arch/i386/kernel/apic.c - 1.46 linux/arch/i386/kernel/mpparse.c - 1.40 linux/include/asm-i386/mpspec.h - 1.17 linux/include/asm-i386/io_apic.h - 1.11 linux/drivers/scsi/scsi_scan.c - 1.49 linux/arch/ia64/kernel/time.c - 1.23 linux/include/asm-ia64/timex.h - 1.4 linux/net/econet/af_econet.c - 1.22 linux/drivers/ide/ide.c - 1.88 linux/drivers/ide/ide-probe.c - 1.55 linux/drivers/ide/ide-disk.c - 1.62 linux/drivers/ide/ide-cd.c - 1.64 linux/arch/s390/kernel/time.c - 1.13 linux/fs/jffs/intrep.c - 1.23 linux/arch/ppc/configs/rpxlite_defconfig - 1.17 linux/arch/ppc/configs/rpxcllf_defconfig - 1.18 linux/arch/ppc/configs/est8260_defconfig - 1.19 linux/arch/ppc/configs/bseip_defconfig - 1.17 linux/drivers/net/tun.c - 1.22 linux/net/ipv4/tcp_minisocks.c - 1.28 linux/drivers/input/input.c - 1.21 linux/drivers/input/evdev.c - 1.19 linux/arch/parisc/kernel/entry.S - 1.9 linux/drivers/parport/parport_gsc.c - 1.11 linux/include/asm-parisc/unistd.h - 1.9 linux/drivers/video/stifb.c - 1.11 linux/arch/parisc/mm/init.c - 1.10 linux/include/asm-parisc/pgtable.h - 1.11 linux/include/asm-parisc/processor.h - 1.11 linux/arch/parisc/kernel/traps.c - 1.9 linux/arch/parisc/kernel/time.c - 1.8 linux/arch/parisc/kernel/syscall.S - 1.12 linux/arch/parisc/kernel/signal.c - 1.10 linux/arch/i386/kernel/dmi_scan.c - 1.31 linux/arch/parisc/kernel/process.c - 1.10 linux/arch/parisc/kernel/pdc_cons.c - 1.7 linux/arch/parisc/kernel/parisc_ksyms.c - 1.9 linux/include/asm-parisc/elf.h - 1.5 linux/include/asm-parisc/fixmap.h - 1.3 linux/arch/parisc/kernel/irq.c - 1.12 linux/arch/parisc/kernel/Makefile - 1.12 linux/arch/parisc/Makefile - 1.15 linux/include/asm-parisc/timex.h - 1.3 linux/mm/shmem.c - 1.60 linux/arch/ppc/configs/power3_defconfig - 1.15 linux/arch/ppc/configs/ibmchrp_defconfig - 1.15 linux/arch/cris/kernel/time.c - 1.10 linux/drivers/net/wan/dscc4.c - 1.20 linux/arch/ppc/configs/TQM860L_defconfig - 1.17 linux/arch/ppc/configs/TQM850L_defconfig - 1.15 linux/arch/ppc/configs/TQM823L_defconfig - 1.15 linux/arch/ppc/configs/SPD823TS_defconfig - 1.15 linux/arch/ppc/configs/SM850_defconfig - 1.15 linux/arch/ppc/configs/IVMS8_defconfig - 1.17 linux/net/wanrouter/af_wanpipe.c - 1.19 linux/include/net/bluetooth/bluetooth.h - 1.10 linux/net/bluetooth/af_bluetooth.c - 1.17 linux/net/bluetooth/hci_sock.c - 1.16 linux/drivers/char/sonypi.h - 1.13 linux/drivers/media/video/meye.h - 1.8 linux/drivers/media/video/meye.c - 1.15 linux/drivers/char/sonypi.c - 1.15 linux/drivers/message/fusion/mptbase.c - 1.13 linux/drivers/scsi/dpt_i2o.c - 1.24 linux/Documentation/input/input-programming.txt - 1.3 linux/drivers/pcmcia/sa1100_generic.c - 1.18 linux/drivers/pcmcia/i82092.c - 1.15 linux/drivers/pcmcia/i82092aa.h - 1.6 linux/drivers/ide/ide-taskfile.c - 1.32 linux/net/ipv4/tcp_diag.c - 1.8 linux/drivers/input/joystick/analog.c - 1.6 linux/drivers/input/gameport/gameport.c - 1.7 linux/drivers/input/serio/Makefile - 1.9 linux/arch/ppc/configs/FADS_defconfig - 1.6 linux/arch/ppc/configs/TQM8260_defconfig - 1.5 linux/arch/ppc/configs/adir_defconfig - 1.6 linux/arch/ppc/configs/ash_defconfig - 1.6 linux/arch/ppc/configs/cpci405_defconfig - 1.8 linux/arch/ppc/configs/ep405_defconfig - 1.6 linux/arch/ppc/configs/ev64260_defconfig - 1.6 linux/arch/ppc/configs/k2_defconfig - 1.10 linux/arch/ppc/configs/lopec_defconfig - 1.7 linux/arch/ppc/configs/mcpn765_defconfig - 1.6 linux/arch/ppc/configs/menf1_defconfig - 1.10 linux/arch/ppc/configs/mvme5100_defconfig - 1.8 linux/arch/ppc/configs/pcore_defconfig - 1.5 linux/arch/ppc/configs/pplus_defconfig - 1.10 linux/arch/ppc/configs/prpmc750_defconfig - 1.6 linux/arch/ppc/configs/prpmc800_defconfig - 1.6 linux/arch/ppc/configs/redwood5_defconfig - 1.7 linux/arch/ppc/configs/redwood_defconfig - 1.6 linux/arch/ppc/configs/sandpoint_defconfig - 1.11 linux/arch/ppc/configs/spruce_defconfig - 1.6 linux/arch/ppc/configs/zx4500_defconfig - 1.6 linux/sound/oss/es1371.c - 1.13 linux/arch/x86_64/Makefile - 1.19 linux/arch/x86_64/ia32/sys_ia32.c - 1.22 linux/arch/x86_64/kernel/Makefile - 1.19 linux/arch/x86_64/kernel/apic.c - 1.17 linux/arch/x86_64/kernel/bluesmoke.c - 1.11 linux/arch/x86_64/kernel/cpuid.c - 1.6 linux/arch/x86_64/kernel/ldt.c - 1.10 linux/arch/x86_64/kernel/msr.c - 1.8 linux/arch/x86_64/kernel/nmi.c - 1.12 linux/arch/x86_64/kernel/process.c - 1.20 linux/arch/x86_64/kernel/setup.c - 1.14 linux/arch/x86_64/kernel/signal.c - 1.15 linux/arch/x86_64/kernel/smpboot.c - 1.17 linux/arch/x86_64/kernel/time.c - 1.14 linux/arch/x86_64/kernel/traps.c - 1.18 linux/arch/x86_64/lib/delay.c - 1.3 linux/arch/x86_64/mm/init.c - 1.15 linux/include/asm-x86_64/pgtable.h - 1.18 linux/include/asm-x86_64/pci.h - 1.9 linux/include/asm-x86_64/page.h - 1.11 linux/include/asm-x86_64/io.h - 1.8 linux/include/asm-x86_64/fixmap.h - 1.5 linux/include/asm-x86_64/timex.h - 1.8 linux/arch/ppc64/kernel/sys_ppc32.c - 1.24 linux/arch/ppc64/kernel/time.c - 1.15 linux/drivers/pcmcia/sa1111_generic.c - 1.10 linux/drivers/usb/input/hid-core.c - 1.22 linux/drivers/usb/input/hid-input.c - 1.11 linux/drivers/usb/input/hid.h - 1.10 linux/drivers/usb/input/hiddev.c - 1.17 linux/net/ipv6/ipv6_syms.c - 1.12 linux/net/bluetooth/sco.c - 1.12 linux/net/bluetooth/l2cap.c - 1.13 linux/arch/x86_64/pci/x86-64.c - 1.5 linux/arch/x86_64/pci/changelog - 1.2 linux/arch/x86_64/pci/irq.c - 1.8 linux/arch/x86_64/pci/legacy.c - 1.4 linux/drivers/net/irda/ma600.c - 1.4 linux/arch/x86_64/pci/pci.h - 1.5 linux/arch/x86_64/pci/Makefile - 1.5 linux/arch/x86_64/pci/fixup.c - 1.3 linux/arch/x86_64/pci/direct.c - 1.5 linux/arch/x86_64/pci/acpi.c - 1.3 linux/arch/x86_64/pci/common.c - 1.6 linux/include/net/llc_sap.h - 1.6 linux/net/llc/llc_sap.c - 1.10 linux/net/llc/llc_main.c - 1.12 linux/net/llc/llc_conn.c - 1.11 linux/drivers/input/keyboard/atkbd.c - 1.11 linux/drivers/input/mouse/psmouse.c - 1.13 linux/drivers/input/mouse/Makefile - 1.5 linux/drivers/input/keyboard/sunkbd.c - 1.9 linux/drivers/input/serio/i8042-io.h - 1.5 linux/drivers/input/misc/pcspkr.c - 1.3 linux/include/net/sctp/structs.h - 1.16 linux/net/sctp/socket.c - 1.17 linux/drivers/ide/legacy/pdc4030.c - 1.9 linux/arch/um/kernel/time.c - 1.6 linux/drivers/ide/ide-iops.c - 1.10 linux/drivers/char/vt_ioctl.c - 1.7 linux/arch/ppc/vmlinux.lds.S - 1.11 linux/net/llc/af_llc.c - 1.8 linux/net/x25/x25_proc.c - 1.4 linux/net/llc/llc_proc.c - 1.8 linux/net/ipx/ipx_proc.c - 1.5 linux/drivers/scsi/aacraid/aachba.c - 1.9 linux/net/bluetooth/rfcomm/tty.c - 1.10 linux/net/bluetooth/rfcomm/sock.c - 1.11 linux/net/appletalk/atalk_proc.c - 1.5 linux/arch/ppc/configs/cedar_defconfig - 1.4 linux/include/asm-x86_64/proto.h - 1.11 linux/arch/x86_64/kernel/pci-nommu.c - 1.2 linux/arch/x86_64/kernel/pci-gart.c - 1.10 linux/arch/x86_64/kernel/aperture.c - 1.4 linux/arch/alpha/Kconfig - 1.13 linux/arch/arm/Kconfig - 1.13 linux/arch/cris/Kconfig - 1.8 linux/arch/i386/Kconfig - 1.20 linux/arch/ia64/Kconfig - 1.12 linux/include/asm-parisc/pdc_chassis.h - 1.3 linux/include/asm-parisc/module.h - 1.4 linux/arch/m68k/Kconfig - 1.12 linux/arch/mips/Kconfig - 1.9 linux/arch/mips64/Kconfig - 1.10 linux/arch/parisc/Kconfig - 1.10 linux/arch/parisc/kernel/ioctl32.c - 1.7 linux/arch/parisc/kernel/processor.c - 1.5 linux/arch/parisc/kernel/smp.c - 1.5 linux/arch/parisc/kernel/sys_parisc32.c - 1.12 linux/drivers/md/dm.h - 1.5 linux/drivers/md/dm.c - 1.8 linux/drivers/md/dm-ioctl.c - 1.11 linux/arch/ppc/Kconfig - 1.12 linux/arch/ppc64/Kconfig - 1.11 linux/arch/sh/Kconfig - 1.10 linux/arch/sparc/Kconfig - 1.12 linux/arch/sparc64/Kconfig - 1.14 linux/drivers/ide/Kconfig - 1.11 linux/arch/x86_64/Kconfig - 1.16 linux/drivers/input/mouse/Kconfig - 1.6 linux/include/net/xfrm.h - 1.14 linux/drivers/input/serio/Kconfig - 1.7 linux/drivers/parisc/superio.c - 1.4 linux/drivers/parisc/led.c - 1.6 linux/drivers/parisc/iosapic.c - 1.4 linux/drivers/parisc/gsc.h - 1.3 linux/drivers/parisc/gsc.c - 1.3 linux/drivers/parisc/eisa_eeprom.c - 1.5 linux/drivers/parisc/eisa.c - 1.6 linux/drivers/parisc/dino.c - 1.7 linux/drivers/parisc/Kconfig - 1.5 linux/arch/v850/kernel/time.c - 1.5 linux/arch/m68knommu/Kconfig - 1.11 linux/arch/m68knommu/kernel/setup.c - 1.5 linux/arch/m68knommu/platform/5206e/eLITE/crt0_ram.S - 1.2 linux/arch/m68knommu/platform/68328/config.c - 1.2 linux/arch/v850/Kconfig - 1.11 linux/drivers/serial/mcfserial.c - 1.9 linux/net/key/af_key.c - 1.13 linux/drivers/video/console/sticore.c - 1.5 linux/include/linux/moduleparam.h - 1.3 linux/drivers/ide/ide-io.c - 1.10 linux/kernel/compat.c - 1.8 linux/include/asm-i386/mach-summit/mach_apic.h - 1.8 linux/include/asm-i386/mach-numaq/mach_apic.h - 1.7 linux/include/asm-i386/mach-default/mach_apic.h - 1.6 linux/arch/ppc/configs/redwood6_defconfig - 1.2 linux/arch/ppc/configs/rainier_defconfig - 1.2 linux/arch/ppc/configs/beech_defconfig - 1.2 linux/arch/ppc/configs/sycamore_defconfig - 1.2 linux/include/asm-parisc/compat.h - 1.7 linux/net/sunrpc/rpc_pipe.c - 1.9 linux/arch/parisc/oprofile/init.c - 1.5 linux/include/asm-i386/mach-bigsmp/mach_apic.h - 1.6 linux/arch/parisc/kernel/module.c - 1.5 linux/arch/i386/kernel/cpu/cpufreq/powernow-k7.c - 1.6 linux/include/asm-x86_64/mmzone.h - 1.3 linux/arch/x86_64/kernel/wakeup.S - 1.3 linux/kernel/posix-timers.c - 1.10 linux/include/asm-i386/mach-visws/mach_apic.h - 1.3 linux/net/ipv6/ah6.c - 1.7 linux/net/ipv6/xfrm6_input.c - 1.5 linux/include/asm-i386/mach-pc9800/setup_arch_pre.h - 1.2 linux/net/xfrm/xfrm_state.c - 1.5 linux/drivers/pcmcia/sa11xx_core.h - 1.3 linux/drivers/pcmcia/sa11xx_core.c - 1.4 linux/arch/h8300/Kconfig - 1.3 linux/include/linux/compat_ioctl.h - 1.4 linux/arch/x86_64/ia32/vsyscall.S - 1.2 linux/net/core/flow.c - 1.3 linux/net/core/net-sysfs.c - 1.3 linux/arch/arm26/kernel/time.c - 1.2 linux/fs/compat_ioctl.c - 1.2 From owner-linux-xfs@oss.sgi.com Tue Jun 17 11:14:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 11:14:53 -0700 (PDT) Received: from s383.jpl.nasa.gov (s383.jpl.nasa.gov [137.78.170.215]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HIEb2x011521 for ; Tue, 17 Jun 2003 11:14:38 -0700 Received: from jpl.nasa.gov (mulan [137.78.61.94]) by s383.jpl.nasa.gov (8.12.9/8.12.9) with ESMTP id h5HIEWdE008636 for ; Tue, 17 Jun 2003 11:14:32 -0700 (PDT) Message-ID: <3EEF5A88.6000106@jpl.nasa.gov> Date: Tue, 17 Jun 2003 11:14:32 -0700 From: Bryan Whitehead Organization: Jet Propulsion Laboratory User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030428 X-Accept-Language: en-us, en, zh, zh-cn, zh-hk, zh-sg, zh-tw, ja MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS fs corruption Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4370 X-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 please CC me I'm running Mandrake 9.0 on a number of computer systems at JPL, and am having wierd fs corruption problems. What will happen is after heavy io and writing to many files we'll be able to "see" the file but won't be able to access it. for example I'll run "ls -la devel" in the directory and will see: -rw-rw-r-- 1 mamops optint 890 Jun 13 12:48 devel when I try to cat, less, or more, the file I get nothing. vi will give a read error. the kernel running is: 2.4.19-32mdkenterprise I know you don't usually mess with vendor kernels but I was wondering if you've see this before, so i can be pushed in the right direction to find a solution.... -- Bryan Whitehead SysAdmin - JPL - Interferometry and Large Optical Systems Phone: 818 354 2903 driver@jpl.nasa.gov From owner-linux-xfs@oss.sgi.com Tue Jun 17 12:24:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 12:24:48 -0700 (PDT) Received: from ahriman.bucharest.roedu.net (ahriman.bucharest.roedu.net [141.85.128.71]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HJOS2x016741 for ; Tue, 17 Jun 2003 12:24:29 -0700 Received: (qmail 25717 invoked by uid 1000); 17 Jun 2003 19:50:43 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jun 2003 19:50:43 -0000 Date: Tue, 17 Jun 2003 22:50:43 +0300 (EEST) From: Mihai RUSU X-X-Sender: To: Linux XFS List Subject: problems booting/recovery after crash (xfs cvs) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4371 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dizzy@roedu.net Precedence: bulk X-list: linux-xfs Hi After 2.4.21 kernel release I wanted to try it out on some of the machines here. For that I checked out CVS (SGI-XFS CVS-2003-06-16_05:00_UTC with no debug enabled) compiled and booted. After 20 hours of uptime the machine had to be rebooted hard (well ,that was actually a mistake but thats not the point) by unplugging it. After power on, it booted until the first "big" XFS filesystem recovery were it hanged (disk activity on that fs stopped after some seconds). When I say big I mean a ~140 gb partition (before that one, there was another XFS partitions which didnt had the hanging problem but which is a lot smaller, 16gb, and also which has internal journal different from the one were it hangs which has external jurnal). I have tried many kernels from the lilo boot menu and no one succeded except for the 2.4.9-34 kernel (contributed kernel from the 1.1 release dir). The kernels that I have tried and not succeded were 2.4.21-cvs (the version mentioned above) and 2.4.18-18SGI_XFS_1.2.0. I also mention that all this kernels I have compiled them myself using gcc 2.95.3. Another strange thing is that in the kernel logs I couldnt find the boot messages of the boot tries before that last one (2.4.9-34) that worked. When 2.4.9-34 booted also gave me some interesting kernel logs: Jun 17 15:41:08 s1 kernel: Starting XFS recovery on filesystem: dac960(48,9) (dev: 8/6) Jun 17 15:41:08 s1 kernel: xfs_inotobp: xfs_imap() returned an error 22 on dac960(48,9). Returning error. Jun 17 15:41:08 s1 kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on dac960(48,9). Returning error. Jun 17 15:41:08 s1 kernel: xfs_inactive: xfs_ifree() returned an error = 22 on dac960(48,9) Jun 17 15:41:08 s1 kernel: xfs_force_shutdown(dac960(48,9),0x1) called from line 1962 of file xfs_vnodeops.c. Return address = 0xc01cf242 Jun 17 15:41:08 s1 kernel: I/O Error Detected. Shutting down filesystem: dac960(48,9) Jun 17 15:41:08 s1 kernel: Please umount the filesystem, and rectify the problem(s) Jun 17 15:41:08 s1 kernel: Ending XFS recovery on filesystem: dac960(48,9) (dev: 8/6) After 2.4.9-34 booted I rebooted the machine (software) and it booted 2.4.29-cvs just fine. Because I never had problems with that machine before (hardware problems) and because it did it only on XFS recovery I presume its a XFS bug ? I would like to know what can I do to make sure it doesnt happen again. Thanks :) ---------------------------- Mihai RUSU Disclaimer: Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of any company, unless otherwise specifically stated. From owner-linux-xfs@oss.sgi.com Tue Jun 17 13:10:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 13:10:48 -0700 (PDT) Received: from eolus.bluedomino.net (bluedomino.net [66.216.88.206] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HKAY2x019390 for ; Tue, 17 Jun 2003 13:10:35 -0700 Received: from MFAC10 ([::ffff:216.221.72.246]) (AUTH: CRAM-MD5 galb@mfac.com) by eolus.bluedomino.net with esmtp; Tue, 17 Jun 2003 15:08:58 -0500 From: "Chris Galbraith" To: linux-xfs@oss.sgi.com Date: Tue, 17 Jun 2003 16:11:03 -0400 MIME-Version: 1.0 Subject: Redhat 8.0 and XFS Reply-to: galb@mfac.com Message-ID: <3EEF3D97.24929.4D4F6FD9@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-archive-position: 4372 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: galb@mfac.com Precedence: bulk X-list: linux-xfs Hi There; Forgive the stupid question, but I am looking for the "best" way to get XFS up and running for a Redhat 8.0 system running an SMP kernel 2.4.20-18.9. I am starting with a virgin kernel from Redhat - 2.4.18-18 which does not have XFS but want to upgrade to XFS and to 2.4.20- 18.9. Any comments as to the steps I should take, and where best to download the required patches/rpms/source code? To date I have tried to first upgrade the kernel to 2.4.20-18.9, and then try and find patches to add the XFS capability, but this method fails when applying the patch (too many missing files and the date stamps seem wrong). I have also tried using an SGI linux iso, but that failed upon trying to install anaconda. I did the media check, and the disk comes back clean, so I am not sure what to make of that. Any help would be greatly appreciated. -- Chris Galbraith Phone: (613) 547-5395 FAX: (613) 547-5397 From owner-linux-xfs@oss.sgi.com Tue Jun 17 13:28:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 13:28:30 -0700 (PDT) Received: from mail.mnsu.edu (Mail.MNSU.EDU [134.29.1.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HKS62x020749 for ; Tue, 17 Jun 2003 13:28:07 -0700 Received: from mnsu.edu (dyn5390.MavNet.MNSU.EDU [134.29.77.239]) by mail.mnsu.edu (8.12.9/8.12.9) with ESMTP id h5HJuXeN019319 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 17 Jun 2003 14:56:33 -0500 Message-ID: <3EEF7271.30500@mnsu.edu> Date: Tue, 17 Jun 2003 14:56:33 -0500 From: "Jeffrey E. Hundstad" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mihai RUSU , Linux XFS List Subject: Re: problems booting/recovery after crash (xfs cvs) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4373 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jeffrey.hundstad@mnsu.edu Precedence: bulk X-list: linux-xfs Are you using an IDE controller. If you are using: CONFIG_BLK_DEV_PDC202XX_OLD=y or CONFIG_BLK_DEV_PDC202XX_NEW=y be sure to read linux/drivers/ide/pci/pdc202xx_old.c: * Promise Ultra33 cards with BIOS v1.20 through 1.28 will need this * compiled into the kernel if you have more than one card installed. * Note that BIOS v1.29 is reported to fix the problem. Since this is * safe chipset tuning, including this support is harmless If you have the newer bios use _NEW. If you have a bios before 1.28 you need _OLD. I can *confirm* that if you DO NOT follow this advice you will get oopses and hangs on your machines when XFS (or any other disk i/o) is busy. BTW: I can also confim this was my problem earlier this month also. Thanks to those who helped me. -- jeffrey hundstad Mihai RUSU wrote: >Hi > >After 2.4.21 kernel release I wanted to try it out on some of the machines >here. For that I checked out CVS (SGI-XFS CVS-2003-06-16_05:00_UTC with >no debug enabled) compiled and booted. After 20 hours of uptime the >machine had to be rebooted hard (well ,that was actually a mistake but >thats not the point) by unplugging it. After power on, it booted until the >first "big" XFS filesystem recovery were it hanged (disk activity on that >fs stopped after some seconds). When I say big I mean a ~140 gb partition >(before that one, there was another XFS partitions which didnt had the >hanging problem but which is a lot smaller, 16gb, and also which has >internal journal different from the one were it hangs which has external >jurnal). I have tried many kernels from the lilo boot menu and no one >succeded except for the 2.4.9-34 kernel (contributed kernel from the 1.1 >release dir). The kernels that I have tried and not succeded were >2.4.21-cvs (the version mentioned above) and 2.4.18-18SGI_XFS_1.2.0. I >also mention that all this kernels I have compiled them myself using gcc >2.95.3. > >Another strange thing is that in the kernel logs I couldnt find the boot >messages of the boot tries before that last one (2.4.9-34) that worked. >When 2.4.9-34 booted also gave me some interesting kernel logs: > >Jun 17 15:41:08 s1 kernel: Starting XFS recovery on filesystem: >dac960(48,9) (dev: 8/6) >Jun 17 15:41:08 s1 kernel: xfs_inotobp: xfs_imap() returned an error 22 >on dac960(48,9). Returning error. >Jun 17 15:41:08 s1 kernel: xfs_iunlink_remove: xfs_inotobp() returned an error >22 on dac960(48,9). Returning error. >Jun 17 15:41:08 s1 kernel: xfs_inactive: xfs_ifree() returned an error = >22 on dac960(48,9) >Jun 17 15:41:08 s1 kernel: xfs_force_shutdown(dac960(48,9),0x1) called >from line 1962 of file xfs_vnodeops.c. Return address = 0xc01cf242 >Jun 17 15:41:08 s1 kernel: I/O Error Detected. Shutting down filesystem: >dac960(48,9) >Jun 17 15:41:08 s1 kernel: Please umount the filesystem, and rectify the >problem(s) >Jun 17 15:41:08 s1 kernel: Ending XFS recovery on filesystem: dac960(48,9) >(dev: 8/6) > >After 2.4.9-34 booted I rebooted the machine (software) and it booted >2.4.29-cvs just fine. > >Because I never had problems with that machine before (hardware problems) >and because it did it only on XFS recovery I presume its a XFS bug ? > >I would like to know what can I do to make sure it doesnt happen again. >Thanks :) > >---------------------------- >Mihai RUSU > >Disclaimer: Any views or opinions presented within this e-mail are solely >those of the author and do not necessarily represent those of any company, >unless otherwise specifically stated. > > > > From owner-linux-xfs@oss.sgi.com Tue Jun 17 14:25:17 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 14:25:30 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HLPG2x026849 for ; Tue, 17 Jun 2003 14:25:17 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5HLfvmO006496 for ; Tue, 17 Jun 2003 16:41:57 -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 h5HLPAqX5060138; Tue, 17 Jun 2003 16:25:10 -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 h5HLPAYk12408332; Tue, 17 Jun 2003 16:25:10 -0500 (CDT) Subject: Re: Redhat 8.0 and XFS From: Eric Sandeen To: galb@mfac.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EEF3D97.24929.4D4F6FD9@localhost> References: <3EEF3D97.24929.4D4F6FD9@localhost> Content-Type: text/plain Organization: Message-Id: <1055885109.20132.2.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 17 Jun 2003 16:25:10 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4374 X-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 The 8.0/XFS installer should work, but it is a bit rough around the edges. There should be an xfs-capable kernel based on Red Hat's 2.4.20-18.9 kernel in a bit, you can take the SRPM from that, compare the .spec files from 2.4.20-18.7 to turn off some RH9-specific patches, and build yourself an 8.0 kernel. Then it's the whole root filesystem migration dance, if the installer won't work for you. -Eric From owner-linux-xfs@oss.sgi.com Tue Jun 17 16:01:04 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 16:01:21 -0700 (PDT) Received: from ahriman.bucharest.roedu.net (ahriman.bucharest.roedu.net [141.85.128.71]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HN132x004468 for ; Tue, 17 Jun 2003 16:01:04 -0700 Received: (qmail 13766 invoked by uid 1000); 17 Jun 2003 23:27:19 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 17 Jun 2003 23:27:19 -0000 Date: Wed, 18 Jun 2003 02:27:19 +0300 (EEST) From: Mihai RUSU X-X-Sender: To: "Jeffrey E. Hundstad" cc: Linux XFS List Subject: Re: problems booting/recovery after crash (xfs cvs) In-Reply-To: <3EEF7271.30500@mnsu.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4375 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dizzy@roedu.net Precedence: bulk X-list: linux-xfs Hi Thanks for the help but I am using DAC960 Mylex RAID controller (I dont even compile ATA/IDE support in kernel). On Tue, 17 Jun 2003, Jeffrey E. Hundstad wrote: > Are you using an IDE controller. > > If you are using: > CONFIG_BLK_DEV_PDC202XX_OLD=y > or > CONFIG_BLK_DEV_PDC202XX_NEW=y > > be sure to read linux/drivers/ide/pci/pdc202xx_old.c: > * Promise Ultra33 cards with BIOS v1.20 through 1.28 will need this > * compiled into the kernel if you have more than one card installed. > * Note that BIOS v1.29 is reported to fix the problem. Since this is > * safe chipset tuning, including this support is harmless > > If you have the newer bios use _NEW. If you have a bios before 1.28 you > need _OLD. I can *confirm* that if you DO NOT follow this advice you > will get oopses and hangs on your machines when XFS (or any other disk > i/o) is busy. > > BTW: I can also confim this was my problem earlier this month also. > Thanks to those who helped me. > > -- > jeffrey hundstad > > Mihai RUSU wrote: > > >Hi > > > >After 2.4.21 kernel release I wanted to try it out on some of the machines > >here. For that I checked out CVS (SGI-XFS CVS-2003-06-16_05:00_UTC with > >no debug enabled) compiled and booted. After 20 hours of uptime the > >machine had to be rebooted hard (well ,that was actually a mistake but > >thats not the point) by unplugging it. After power on, it booted until the > >first "big" XFS filesystem recovery were it hanged (disk activity on that > >fs stopped after some seconds). When I say big I mean a ~140 gb partition > >(before that one, there was another XFS partitions which didnt had the > >hanging problem but which is a lot smaller, 16gb, and also which has > >internal journal different from the one were it hangs which has external > >jurnal). I have tried many kernels from the lilo boot menu and no one > >succeded except for the 2.4.9-34 kernel (contributed kernel from the 1.1 > >release dir). The kernels that I have tried and not succeded were > >2.4.21-cvs (the version mentioned above) and 2.4.18-18SGI_XFS_1.2.0. I > >also mention that all this kernels I have compiled them myself using gcc > >2.95.3. > > > >Another strange thing is that in the kernel logs I couldnt find the boot > >messages of the boot tries before that last one (2.4.9-34) that worked. > >When 2.4.9-34 booted also gave me some interesting kernel logs: > > > >Jun 17 15:41:08 s1 kernel: Starting XFS recovery on filesystem: > >dac960(48,9) (dev: 8/6) > >Jun 17 15:41:08 s1 kernel: xfs_inotobp: xfs_imap() returned an error 22 > >on dac960(48,9). Returning error. > >Jun 17 15:41:08 s1 kernel: xfs_iunlink_remove: xfs_inotobp() returned an error > >22 on dac960(48,9). Returning error. > >Jun 17 15:41:08 s1 kernel: xfs_inactive: xfs_ifree() returned an error = > >22 on dac960(48,9) > >Jun 17 15:41:08 s1 kernel: xfs_force_shutdown(dac960(48,9),0x1) called > >from line 1962 of file xfs_vnodeops.c. Return address = 0xc01cf242 > >Jun 17 15:41:08 s1 kernel: I/O Error Detected. Shutting down filesystem: > >dac960(48,9) > >Jun 17 15:41:08 s1 kernel: Please umount the filesystem, and rectify the > >problem(s) > >Jun 17 15:41:08 s1 kernel: Ending XFS recovery on filesystem: dac960(48,9) > >(dev: 8/6) > > > >After 2.4.9-34 booted I rebooted the machine (software) and it booted > >2.4.29-cvs just fine. > > > >Because I never had problems with that machine before (hardware problems) > >and because it did it only on XFS recovery I presume its a XFS bug ? > > > >I would like to know what can I do to make sure it doesnt happen again. > >Thanks :) > > > >---------------------------- > >Mihai RUSU > > > >Disclaimer: Any views or opinions presented within this e-mail are solely > >those of the author and do not necessarily represent those of any company, > >unless otherwise specifically stated. > > > > > > > > > > ---------------------------- Mihai RUSU Disclaimer: Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of any company, unless otherwise specifically stated. From owner-linux-xfs@oss.sgi.com Tue Jun 17 16:11:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 16:11:29 -0700 (PDT) Received: from mail.modwest.com (marshall.modwest.com [216.129.251.30]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5HNBA2x004993 for ; Tue, 17 Jun 2003 16:11:11 -0700 Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.modwest.com (Postfix) with ESMTP id BE4CC40EB3DD; Tue, 17 Jun 2003 17:11:09 -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 01698-19; Tue, 17 Jun 2003 17:11:09 -0000 (MDT) Received: from [10.0.0.135] (unknown [69.24.111.150]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mail.modwest.com (Postfix) with ESMTP id 47C6C40F4CF5; Tue, 17 Jun 2003 17:11:09 -0600 (MDT) Date: Tue, 17 Jun 2003 17:11:48 -0600 From: Michael Loftis To: Mihai RUSU , Linux XFS List Subject: Re: problems booting/recovery after crash (xfs cvs) Message-ID: <113491687.1055869908@[10.0.0.135]> In-Reply-To: References: 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: 4376 X-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 Boot single again (with latest kernel or whatever works) don't mount the filesystem and run an xfs_repair. Recently I experienced almost the exact same thing. (only our machine room is loud and the machine has no external indication of drive I/O so I can't comment on that) -- ours was a problem with the root partition though which required a boot from a rescue disk. --On Tuesday, June 17, 2003 22:50 +0300 Mihai RUSU wrote: > Hi > > After 2.4.21 kernel release I wanted to try it out on some of the machines > here. For that I checked out CVS (SGI-XFS CVS-2003-06-16_05:00_UTC with > no debug enabled) compiled and booted. After 20 hours of uptime the > machine had to be rebooted hard (well ,that was actually a mistake but > thats not the point) by unplugging it. After power on, it booted until the > first "big" XFS filesystem recovery were it hanged (disk activity on that > fs stopped after some seconds). When I say big I mean a ~140 gb partition > (before that one, there was another XFS partitions which didnt had the > hanging problem but which is a lot smaller, 16gb, and also which has > internal journal different from the one were it hangs which has external > jurnal). I have tried many kernels from the lilo boot menu and no one > succeded except for the 2.4.9-34 kernel (contributed kernel from the 1.1 > release dir). The kernels that I have tried and not succeded were > 2.4.21-cvs (the version mentioned above) and 2.4.18-18SGI_XFS_1.2.0. I > also mention that all this kernels I have compiled them myself using gcc > 2.95.3. > > Another strange thing is that in the kernel logs I couldnt find the boot > messages of the boot tries before that last one (2.4.9-34) that worked. > When 2.4.9-34 booted also gave me some interesting kernel logs: > > Jun 17 15:41:08 s1 kernel: Starting XFS recovery on filesystem: > dac960(48,9) (dev: 8/6) > Jun 17 15:41:08 s1 kernel: xfs_inotobp: xfs_imap() returned an error 22 > on dac960(48,9). Returning error. > Jun 17 15:41:08 s1 kernel: xfs_iunlink_remove: xfs_inotobp() returned an > error 22 on dac960(48,9). Returning error. > Jun 17 15:41:08 s1 kernel: xfs_inactive: xfs_ifree() returned an error = > 22 on dac960(48,9) > Jun 17 15:41:08 s1 kernel: xfs_force_shutdown(dac960(48,9),0x1) called > from line 1962 of file xfs_vnodeops.c. Return address = 0xc01cf242 > Jun 17 15:41:08 s1 kernel: I/O Error Detected. Shutting down filesystem: > dac960(48,9) > Jun 17 15:41:08 s1 kernel: Please umount the filesystem, and rectify the > problem(s) > Jun 17 15:41:08 s1 kernel: Ending XFS recovery on filesystem: dac960(48,9) > (dev: 8/6) > > After 2.4.9-34 booted I rebooted the machine (software) and it booted > 2.4.29-cvs just fine. > > Because I never had problems with that machine before (hardware problems) > and because it did it only on XFS recovery I presume its a XFS bug ? > > I would like to know what can I do to make sure it doesnt happen again. > Thanks :) > > ---------------------------- > Mihai RUSU > > Disclaimer: Any views or opinions presented within this e-mail are solely > those of the author and do not necessarily represent those of any company, > unless otherwise specifically stated. > > -- Michael Loftis Modwest Sr. Systems Administrator Powerful, Affordable Web Hosting From owner-linux-xfs@oss.sgi.com Tue Jun 17 16:52:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 16:52:15 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5HNqB2x006661 for ; Tue, 17 Jun 2003 16:52:11 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5HNqBRt006660 for linux-xfs@oss.sgi.com; Tue, 17 Jun 2003 16:52:11 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5HNq931006645 for ; Tue, 17 Jun 2003 16:52:09 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5HNCRZW005278; Tue, 17 Jun 2003 16:12:27 -0700 Date: Tue, 17 Jun 2003 16:12:27 -0700 Message-Id: <200306172312.h5HNCRZW005278@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 249] Installing RedHat9 with SGI-XFS installer leades to network admin problem X-Bugzilla-Reason: AssignedTo X-archive-position: 4377 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=249 cattelan@thebarn.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From cattelan@thebarn.com 2003-17-06 16:12 PDT ------- Unfortunatly we do not have time to fix installer bugs. If anybody can make this a FS bug then we will look at it. The installer it purely an "as is" thing. ------- 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 Jun 17 17:21:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 17:21:19 -0700 (PDT) Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5I0LG2x007700 for ; Tue, 17 Jun 2003 17:21:16 -0700 Received: from [10.0.0.10] (c-24-245-56-70.mn.client2.attbi.com [24.245.56.70]) by lips.thebarn.com (8.12.9/8.12.6) with ESMTP id h5I0L8uw075647; Tue, 17 Jun 2003 19:21:08 -0500 (CDT) (envelope-from cattelan@thebarn.com) Subject: Re: Bug in xfs_repair From: Russell Cattelan To: Erik Tews Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030616205718.GA6783@debian.franken.de> References: <20030616205718.GA6783@debian.franken.de> Content-Type: text/plain Organization: Message-Id: <1055895612.1068.2.camel@lupo.thebarn.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 17 Jun 2003 19:20:12 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4379 X-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 Please file a bug http://oss.sgi.com/bugzilla/ So this doesn't get lost On Mon, 2003-06-16 at 15:57, Erik Tews wrote: > Hi > > I think I found a bug in xfs_repair. It saegfaults when I run it on a > filesystem which is a little bit corrupt. After I ran it with efence, I > got these backtraces. I think it cannot handle this block-out-of-range > condition correctly. I have attached all important informations. -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Tue Jun 17 17:20:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 17:20:40 -0700 (PDT) Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5I0KM2x007603 for ; Tue, 17 Jun 2003 17:20:23 -0700 Received: from [10.0.0.10] (c-24-245-56-70.mn.client2.attbi.com [24.245.56.70]) by lips.thebarn.com (8.12.9/8.12.6) with ESMTP id h5I0KLuw075636; Tue, 17 Jun 2003 19:20:21 -0500 (CDT) (envelope-from cattelan@thebarn.com) Subject: Re: problems booting/recovery after crash (xfs cvs) From: Russell Cattelan To: Michael Loftis Cc: Mihai RUSU , Linux XFS List In-Reply-To: <113491687.1055869908@[10.0.0.135]> References: <113491687.1055869908@[10.0.0.135]> Content-Type: text/plain Organization: Message-Id: <1055895565.1068.0.camel@lupo.thebarn.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 17 Jun 2003 19:19:25 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4378 X-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 BTW file a bug http://oss.sgi.com/bugzilla/ so this doesn't get lost On Tue, 2003-06-17 at 18:11, Michael Loftis wrote: > Boot single again (with latest kernel or whatever works) don't mount the > filesystem and run an xfs_repair. > > Recently I experienced almost the exact same thing. (only our machine room > is loud and the machine has no external indication of drive I/O so I can't > comment on that) -- ours was a problem with the root partition though > which required a boot from a rescue disk. > > > > --On Tuesday, June 17, 2003 22:50 +0300 Mihai RUSU wrote: > > > Hi > > > > After 2.4.21 kernel release I wanted to try it out on some of the machines > > here. For that I checked out CVS (SGI-XFS CVS-2003-06-16_05:00_UTC with > > no debug enabled) compiled and booted. After 20 hours of uptime the > > machine had to be rebooted hard (well ,that was actually a mistake but > > thats not the point) by unplugging it. After power on, it booted until the > > first "big" XFS filesystem recovery were it hanged (disk activity on that > > fs stopped after some seconds). When I say big I mean a ~140 gb partition > > (before that one, there was another XFS partitions which didnt had the > > hanging problem but which is a lot smaller, 16gb, and also which has > > internal journal different from the one were it hangs which has external > > jurnal). I have tried many kernels from the lilo boot menu and no one > > succeded except for the 2.4.9-34 kernel (contributed kernel from the 1.1 > > release dir). The kernels that I have tried and not succeded were > > 2.4.21-cvs (the version mentioned above) and 2.4.18-18SGI_XFS_1.2.0. I > > also mention that all this kernels I have compiled them myself using gcc > > 2.95.3. > > > > Another strange thing is that in the kernel logs I couldnt find the boot > > messages of the boot tries before that last one (2.4.9-34) that worked. > > When 2.4.9-34 booted also gave me some interesting kernel logs: > > > > Jun 17 15:41:08 s1 kernel: Starting XFS recovery on filesystem: > > dac960(48,9) (dev: 8/6) > > Jun 17 15:41:08 s1 kernel: xfs_inotobp: xfs_imap() returned an error 22 > > on dac960(48,9). Returning error. > > Jun 17 15:41:08 s1 kernel: xfs_iunlink_remove: xfs_inotobp() returned an > > error 22 on dac960(48,9). Returning error. > > Jun 17 15:41:08 s1 kernel: xfs_inactive: xfs_ifree() returned an error = > > 22 on dac960(48,9) > > Jun 17 15:41:08 s1 kernel: xfs_force_shutdown(dac960(48,9),0x1) called > > from line 1962 of file xfs_vnodeops.c. Return address = 0xc01cf242 > > Jun 17 15:41:08 s1 kernel: I/O Error Detected. Shutting down filesystem: > > dac960(48,9) > > Jun 17 15:41:08 s1 kernel: Please umount the filesystem, and rectify the > > problem(s) > > Jun 17 15:41:08 s1 kernel: Ending XFS recovery on filesystem: dac960(48,9) > > (dev: 8/6) > > > > After 2.4.9-34 booted I rebooted the machine (software) and it booted > > 2.4.29-cvs just fine. > > > > Because I never had problems with that machine before (hardware problems) > > and because it did it only on XFS recovery I presume its a XFS bug ? > > > > I would like to know what can I do to make sure it doesnt happen again. > > Thanks :) > > > > ---------------------------- > > Mihai RUSU > > > > Disclaimer: Any views or opinions presented within this e-mail are solely > > those of the author and do not necessarily represent those of any company, > > unless otherwise specifically stated. > > > > > > > > -- > Michael Loftis > Modwest Sr. Systems Administrator > Powerful, Affordable Web Hosting -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Tue Jun 17 17:39:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 17:39:33 -0700 (PDT) Received: from cfa.harvard.edu (cfa.harvard.edu [131.142.10.1]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5I0dR2x012134 for ; Tue, 17 Jun 2003 17:39:27 -0700 Received: from cfassp43.cfa.harvard.edu (cfassp43 [131.142.24.227]) by cfa.harvard.edu (8.9.2/8.9.2/cfunix Mast-Sol 0.5) with ESMTP id UAA29721 for ; Tue, 17 Jun 2003 20:39:26 -0400 (EDT) Received: from localhost (gbakos@localhost) by cfassp43.cfa.harvard.edu (8.9.2/8.9.2/cfunix S 0.5) with ESMTP id UAA21273 for ; Tue, 17 Jun 2003 20:39:26 -0400 (EDT) X-Authentication-Warning: cfassp43.cfa.harvard.edu: gbakos owned process doing -bs Date: Tue, 17 Jun 2003 20:39:25 -0400 (EDT) From: Gaspar Bakos To: linux-xfs@oss.sgi.com Subject: migrate to 1.2 from 1.1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4380 X-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 Dear all, I am migrating from kernel 2.4.18 + xfs-1.1-2.4.18 patch to 2.4.20 kernel and the relevant xfs-1.2-2.4.20 patch. All partitions on my (RH7.3) computer are XFS v1.1 (including sw RAID-1, the root partition, etc). Question is: what shall I do? Will the newly patched 2.4.20 kernel mount the older xfs partitions without making any damage? How can they be migrated to xfs 1.2? Do I have to upgrade the xfstools before the reboot? Will LILO and the MBR will be affected by the new filesystem? Cheers Gaspar From owner-linux-xfs@oss.sgi.com Tue Jun 17 17:53:14 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 17:53:17 -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.9) with SMTP id h5I0rD2x012628 for ; Tue, 17 Jun 2003 17:53:13 -0700 Received: from comcast.net (localhost [127.0.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id 2E00174A14; Tue, 17 Jun 2003 17:53:08 -0700 (PDT) Message-ID: <3EEFB7F4.4080705@comcast.net> Date: Tue, 17 Jun 2003 17:53:08 -0700 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gaspar Bakos Cc: linux-xfs@oss.sgi.com Subject: Re: migrate to 1.2 from 1.1 References: In-Reply-To: X-Enigmail-Version: 0.76.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4381 X-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 Gaspar Bakos wrote: > Dear all, > > I am migrating from kernel 2.4.18 + xfs-1.1-2.4.18 patch to > 2.4.20 kernel and the relevant xfs-1.2-2.4.20 patch. > > All partitions on my (RH7.3) computer are XFS v1.1 (including sw RAID-1, > the root partition, etc). > > Question is: what shall I do? Will the newly patched 2.4.20 kernel mount > the older xfs partitions without making any damage? How can they be > migrated to xfs 1.2? Do I have to upgrade the xfstools before the reboot? > Will LILO and the MBR will be affected by the new filesystem? > > Cheers > Gaspar > > > The on-disk filesystem format didn't change from 1.1 to 1.2 - You shouldn't have to do anything to the filesystem. Just update the kernel and boot into it. -Walt From owner-linux-xfs@oss.sgi.com Tue Jun 17 18:07:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 18:07:40 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5I17M2x013208 for ; Tue, 17 Jun 2003 18:07:23 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5I17HE0011095 for ; Tue, 17 Jun 2003 18:07:17 -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 h5I17GqX5089969; Tue, 17 Jun 2003 20:07:16 -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 h5I17GYl12437579; Tue, 17 Jun 2003 20:07:16 -0500 (CDT) Date: Tue, 17 Jun 2003 20:07:16 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Walt H cc: Gaspar Bakos , Subject: Re: migrate to 1.2 from 1.1 In-Reply-To: <3EEFB7F4.4080705@comcast.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4382 X-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 It would probably be best to also update your userspace to at least the versions that went with XFS 1.2, although this will not affect your ability to boot, mount, etc. -Eric On Tue, 17 Jun 2003, Walt H wrote: > The on-disk filesystem format didn't change from 1.1 to 1.2 - You > shouldn't have to do anything to the filesystem. Just update the kernel > and boot into it. > > -Walt > > > From owner-linux-xfs@oss.sgi.com Tue Jun 17 19:16:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 19:16:51 -0700 (PDT) Received: from maillog.promise.com.tw (maillog.promise.com.tw [210.244.60.166]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5I2GT2x014731 for ; Tue, 17 Jun 2003 19:16:30 -0700 Received: from ptt.promise.com.tw (IDENT:root@ptt [192.168.202.253]) by maillog.promise.com.tw (8.11.3/8.11.3) with ESMTP id h5I2BdY31678; Wed, 18 Jun 2003 10:11:39 +0800 (CST) (envelope-from scottl@promise.com.tw) Received: from sn1 (IDENT:root@localhost [127.0.0.1]) by ptt.promise.com.tw (8.9.3/8.9.3) with SMTP id KAA05320; Wed, 18 Jun 2003 10:04:40 +0800 Reply-To: From: "Scott Liu" To: "'Chris Wedgwood'" Cc: , "'Grace Ho'" , "'Jenny'" , "'Myst Lin \(E-mail\)'" , "'Peter'" Subject: RE: How to reconstruct an xfs filesystem and restore all datas? Date: Wed, 18 Jun 2003 10:17:30 +0800 Message-ID: <000d01c3353f$c6117330$89cca8c0@sn1> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20030617130438.GB3510@dingdong.cryptoapps.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id h5I2GV2x014732 X-archive-position: 4383 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: scottl@promise.com.tw Precedence: bulk X-list: linux-xfs Dear Chris, Thanks. But I don't know how to do "a heuristic to detect the data" and then recover the datas? May you describe this more detail and let us know the methods of this? Best Regards, Scott Liu -----Original Message----- From: Chris Wedgwood [mailto:cw@f00f.org] Sent: Tuesday, June 17, 2003 9:05 PM To: Scott Liu Cc: linux-xfs@oss.sgi.com; 'Grace Ho'; 'Jenny'; 'Myst Lin (E-mail)'; 'Peter' Subject: Re: How to reconstruct an xfs filesystem and restore all datas? On Tue, Jun 17, 2003 at 06:12:57PM +0800, Scott Liu wrote: > A partition created of xfs filesystem and have a lot of datas in. > BUT remiss, I done "mkfs.xfs" of this partition and then I LOST all > datas. How to reconstruct this xfs filesystem and restore all > datas? mkfs.fs will have obliterated most if not all useful metadata making recovery painful at best. It depends what kind of data you have there and how fragmented it was --- but you might have a chance of recovery for some of it if you can use a heuristic to detect the data your after and hope that it's mostly contiguous. I've done this several times for people who've trashed disks for of images mostly because asynchronous writes ensure most files are not-fragmented and most images (jpegs) are easy to scan-for and recover. --cw From owner-linux-xfs@oss.sgi.com Tue Jun 17 20:52:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 20:52:28 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5I3qC2x017406 for ; Tue, 17 Jun 2003 20:52:12 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5I3qCq4017405 for linux-xfs@oss.sgi.com; Tue, 17 Jun 2003 20:52:12 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5I3q931017391 for ; Tue, 17 Jun 2003 20:52:10 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5I2v5mv016240; Tue, 17 Jun 2003 19:57:05 -0700 Date: Tue, 17 Jun 2003 19:57:05 -0700 Message-Id: <200306180257.h5I2v5mv016240@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 250] New: log recovery hangs after crash X-Bugzilla-Reason: AssignedTo X-archive-position: 4384 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=250 Summary: log recovery hangs after crash Product: Linux XFS Version: Current Platform: IA32 OS/Version: Linux Status: NEW Severity: normal Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: dizzy@roedu.net Hi After 2.4.21 kernel release I wanted to try it out on some of the machines here. For that I checked out CVS (SGI-XFS CVS-2003-06-16_05:00_UTC with no debug enabled) compiled and booted. After 20 hours of uptime the machine had to be rebooted hard (well ,that was actually a mistake but thats not the point) by unplugging it. After power on, it booted until the first "big" XFS filesystem recovery were it hanged (when log recovery started it showed disk activity but it stopped after some seconds). When I say big I mean a ~140 gb partition (before that one, the system did log recovery and mounted another XFS partition which didnt had the hanging problem but which is a lot smaller, 16gb, and also which has internal journal different from the one were it hangs which has external jurnal). I have tried many kernels from the lilo boot menu and no one succeded except for the 2.4.9-34 kernel (contributed kernel from the 1.1 release dir). The kernels that I have tried and not succeded were 2.4.21-cvs (the version on which the power off happened) and 2.4.18-18SGI_XFS_1.2.0. I also mention that all this kernels I have compiled them myself using gcc 2.95.3. Another strange thing is that in the kernel logs I couldnt find the boot messages of the boot tries before that last one (2.4.9-34) that worked. When 2.4.9-34 booted also gave me some interesting kernel logs: Jun 17 15:41:08 s1 kernel: Starting XFS recovery on filesystem: dac960(48,9) (dev: 8/6) Jun 17 15:41:08 s1 kernel: xfs_inotobp: xfs_imap() returned an error 22 on dac960(48,9). Returning error. Jun 17 15:41:08 s1 kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on dac960(48,9). Returning error. Jun 17 15:41:08 s1 kernel: xfs_inactive: xfs_ifree() returned an error = 22 on dac960(48,9) Jun 17 15:41:08 s1 kernel: xfs_force_shutdown(dac960(48,9),0x1) called from line 1962 of file xfs_vnodeops.c. Return address = 0xc01cf242 Jun 17 15:41:08 s1 kernel: I/O Error Detected. Shutting down filesystem: dac960(48,9) Jun 17 15:41:08 s1 kernel: Please umount the filesystem, and rectify the problem(s) Jun 17 15:41:08 s1 kernel: Ending XFS recovery on filesystem: dac960(48,9) (dev: 8/6) After 2.4.9-34 booted, I rebooted the machine (software) and it booted 2.4.29-cvs just fine. Because I never had problems with that machine before (hardware problems) and because it did it only on XFS recovery I presume its a XFS bug ? Thanks for any help :) ------- 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 Jun 17 23:20:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Jun 2003 23:20:32 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5I6K82x020046 for ; Tue, 17 Jun 2003 23:20:09 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5I6aomO029832 for ; Wed, 18 Jun 2003 01:36:50 -0500 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by nodin.corp.sgi.com (8.12.9/8.11.4/nodin-1.0) with ESMTP id h5I6J14X1737797 for ; Tue, 17 Jun 2003 23:19:02 -0700 (PDT) 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 h5I6HhJA059470 for ; Wed, 18 Jun 2003 16:17:43 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5I6HgWc059532 for linux-xfs@oss.sgi.com; Wed, 18 Jun 2003 16:17:42 +1000 (EST) Date: Wed, 18 Jun 2003 16:17:42 +1000 (EST) From: Nathan Scott Message-Id: <200306180617.h5I6HgWc059532@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs-2.5.0 X-archive-position: 4385 X-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 xfsprogs update - Andi's mkfs default log size change and enabling large sector support being the two big items; several other small fixes too. There is one remaining kernel issue with large (non-512 byte) sectors (remount fails to flush the final superblock write - see test 017), but other than that it looks pretty solid in my testing. cheers. Date: Tue Jun 17 23:04:16 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:151433a cmd/xfsprogs/VERSION - 1.80 cmd/xfsprogs/doc/CHANGES - 1.112 cmd/xfsprogs/debian/changelog - 1.73 - bump to 2.5.0 for default mkfs changes and large sector support. cmd/xfsprogs/doc/CREDITS - 1.14 - Add Andi Kleen's details. cmd/xfsprogs/man/man8/mkfs.xfs.8 - 1.17 - document large sector support a bit better. cmd/xfsprogs/mkfs/xfs_mkfs.c - 1.47 - incorporate Andi Kleen's default log size changes, enable large sectors. cmd/xfsprogs/libdisk/md.c - 1.12 - no longer warns on devices with the clean flag not set for Keith. cmd/xfsprogs/include/platform_defs.h.in - 1.26 - trivial offset consistency fixup. cmd/xfsprogs/include/xfs_sb.h - 1.10 cmd/xfsprogs/include/xfs_mount.h - 1.38 cmd/xfsprogs/include/xfs_inode.h - 1.33 cmd/xfsprogs/include/xfs_types.h - 1.20 - sync with kernel code. cmd/xfsprogs/repair/sb.c - 1.13 - fix up some of the sector size checks, fix a 32 to 64 bit number compare which can overflow for some agcount/agblocks values. cmd/xfsprogs/libxfs/rdwr.c - 1.19 - rewrite libxfs_device_zero so that it copes with partial writes. cmd/xfsprogs/libxfs/xfs_inode.c - 1.23 - sync with kernel code. cmd/xfsprogs/io/pread.c - 1.6 cmd/xfsprogs/io/truncate.c - 1.4 cmd/xfsprogs/io/resblks.c - 1.5 cmd/xfsprogs/io/pwrite.c - 1.4 cmd/xfsprogs/io/prealloc.c - 1.5 cmd/xfsprogs/io/open.c - 1.6 - fix rounding-down-input problems in some commands (strtoul/strtoull). From owner-linux-xfs@oss.sgi.com Wed Jun 18 04:18:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 04:18:22 -0700 (PDT) Received: from geo.atl.net (geo.atlantel.fr [194.206.120.243]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5IBI52x007988 for ; Wed, 18 Jun 2003 04:18:07 -0700 Received: from geo.atl.net (geo.atlantel.fr [194.206.120.243]) by atlantel.org (Rockliffe SMTPRA 5.2.5) with SMTP id for ; Wed, 18 Jun 2003 13:18:01 +0200 Received: FROM marguerite.atlantel.fr BY geo.atl.net ; Wed Jun 18 13:18:00 2003 +0200 Received: from srvexchange.intrafp.net (ca-bordeaux-1-40.w80-8.abo.wanadoo.fr [80.8.73.40]) by marguerite.atlantel.fr (Postfix) with ESMTP id 03575B6ED6 for ; Wed, 18 Jun 2003 13:18:00 +0200 (CEST) Subject: Acl not included in sources for red-hat patched kernel Date: Wed, 18 Jun 2003 13:16:54 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <42867CB2F247BC4CABC84FEFC7C9B2262BD929@srvexchange.intrafp.net> X-MS-Has-Attach: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 X-MS-TNEF-Correlator: Thread-Topic: Acl not included in sources for red-hat patched kernel Thread-Index: AcM1ix9Ojrgwh3CYQs6OW8Yhbw7qPA== From: "Fabrice Clerc" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5IBI72x007989 X-archive-position: 4386 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: f.clerc@florapartner.com Precedence: bulk X-list: linux-xfs Hello, Please excuse my poor English. I have to use a red-hat kernel on my Debian serveur, because the red-hat kernel is the only one patched for a proper support of my adaptec ata raid card. I need the acl support on my server, so I need an XFS patched kernel on this support. I first tried to patch with your patch a red-hat source kernel, but it didn't work for some reason (concurrent patches seem to have been made on the red-hat kernel that prevent your patch from working properly). So I tried to compile your pre-patched red-hat kernel. While configuring this kernel, i saw that there was no acl option for XFS, there are only dmapi and quota options. This makes I can't use acls on my XFS file systems. The acl option exists on debian kernel sources patched with xfs (these kernels don't work properly with my raid card, unfortunately) This is a true problem for me. -has this option been placed somewhere else in the kernel configuration? -has this option been forgotten, or removed for some reasons? -what can i do to use acls on a red-hat kernel with XFS? Thanks for helping me, if you can. -- Fabrice Clerc Service Informatique Flora Partner From owner-linux-xfs@oss.sgi.com Wed Jun 18 05:51:40 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 05:52:04 -0700 (PDT) Received: from mail.sura.ru (mail.sura.ru [80.95.32.19]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5ICpd2x021937 for ; Wed, 18 Jun 2003 05:51:40 -0700 Received: from 10.0.0.21 (host-80-95-32-106.leasedlines.sura.ru [80.95.32.106]) by mail.sura.ru (Postfix) with ESMTP id 97C8C12C for ; Wed, 18 Jun 2003 16:51:36 +0400 (MSD) Date: Wed, 18 Jun 2003 16:51:47 +0400 From: spied@yandex.ru X-Mailer: The Bat! (v1.61) Personal Reply-To: spied@yandex.ru X-Priority: 3 (Normal) Message-ID: <135191341281.20030618165147@yandex.ru> To: linux-xfs@oss.sgi.com Subject: cvs error MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4387 X-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 i use linux-2.4-xfs from oss.sgi.com if i try do "cvs -z3 update", update stop on "cvs server: Updating linux/scripts/usb", but "cvs update" work fine From owner-linux-xfs@oss.sgi.com Wed Jun 18 05:57:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 05:57:55 -0700 (PDT) Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5ICvo2x022701 for ; Wed, 18 Jun 2003 05:57:51 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtpzilla3.xs4all.nl (8.12.9/8.12.9) with ESMTP id h5ICvnZs033964; Wed, 18 Jun 2003 14:57:49 +0200 (CEST) Message-Id: <4.3.2.7.2.20030618145704.02c43430@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jun 2003 14:57:35 +0200 To: spied@yandex.ru, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: cvs error In-Reply-To: <135191341281.20030618165147@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4388 X-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 At 16:51 18-6-2003 +0400, spied@yandex.ru wrote: >i use linux-2.4-xfs from oss.sgi.com > >if i try do "cvs -z3 update", update stop on "cvs server: Updating >linux/scripts/usb", but "cvs update" work fine I think you need to update your cvs tools. I think you can find it in the security errata for your os. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Wed Jun 18 06:05:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 06:06:13 -0700 (PDT) Received: from dingdong.cryptoapps.com (postfix@uslink-66.173.43-133.uslink.net [66.173.43.133] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5ID5r2x023373 for ; Wed, 18 Jun 2003 06:05:54 -0700 Received: by dingdong.cryptoapps.com (Postfix, from userid 1001) id 474E0FB838; Wed, 18 Jun 2003 08:10:26 -0500 (CDT) Date: Wed, 18 Jun 2003 08:10:26 -0500 From: "'Chris Wedgwood'" To: Scott Liu Cc: linux-xfs@oss.sgi.com, "'Grace Ho'" , "'Jenny'" , "'Myst Lin (E-mail)'" , "'Peter'" Subject: Re: How to reconstruct an xfs filesystem and restore all datas? Message-ID: <20030618131026.GA9640@dingdong.cryptoapps.com> References: <20030617130438.GB3510@dingdong.cryptoapps.com> <000d01c3353f$c6117330$89cca8c0@sn1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000d01c3353f$c6117330$89cca8c0@sn1> X-archive-position: 4389 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Wed, Jun 18, 2003 at 10:17:30AM +0800, Scott Liu wrote: > But I don't know how to do "a heuristic to detect the data" and then > recover the datas? It means scan for patterns that look like your data --- what those patterns are will depend on the data. > May you describe this more detail and let us know the methods of > this? What data did you loose? --cw From owner-linux-xfs@oss.sgi.com Wed Jun 18 06:47:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 06:48:06 -0700 (PDT) Received: from mail.sura.ru (mail.sura.ru [80.95.32.19]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5IDll2x026370 for ; Wed, 18 Jun 2003 06:47:48 -0700 Received: from 10.0.0.21 (host-80-95-32-106.leasedlines.sura.ru [80.95.32.106]) by mail.sura.ru (Postfix) with ESMTP id 8EA2B128 for ; Wed, 18 Jun 2003 17:47:46 +0400 (MSD) Date: Wed, 18 Jun 2003 17:47:57 +0400 From: spied@yandex.ru X-Mailer: The Bat! (v1.61) Personal Reply-To: spied@yandex.ru X-Priority: 3 (Normal) Message-ID: <95194711328.20030618174757@yandex.ru> Cc: linux-xfs@oss.sgi.com Subject: Re[2]: cvs error In-Reply-To: <4.3.2.7.2.20030618145704.02c43430@pop.xs4all.nl> References: <4.3.2.7.2.20030618145704.02c43430@pop.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-archive-position: 4390 X-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 >>i use linux-2.4-xfs from oss.sgi.com >> >>if i try do "cvs -z3 update", update stop on "cvs server: Updating >>linux/scripts/usb", but "cvs update" work fine SM> I think you need to update your cvs tools. I think you can find it in the SM> security errata for your os. i use debian woody and cvs version 1.11.1p1debian-8.1 From owner-linux-xfs@oss.sgi.com Wed Jun 18 06:54:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 06:54:50 -0700 (PDT) Received: from mail.automatix.de (237.230.131.213.rev.inetbone.net [213.131.230.237]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5IDsM2x026838 for ; Wed, 18 Jun 2003 06:54:27 -0700 Received: from uucp by mail.automatix.de with local-bsmtp (Exim 3.35 #1) id 19SdOG-0004op-00 for linux-xfs@oss.sgi.com; Wed, 18 Jun 2003 15:54:20 +0200 Received: from pc2.s.automatix.de ([192.168.11.12] ident=jojo) by s.automatix.de with esmtp (Exim 3.36 #1) id 19Sd8m-0000ez-00; Wed, 18 Jun 2003 15:38:20 +0200 From: Juergen Sauer Reply-To: juergen.sauer@automatix.de Organization: AutomatiX GmbH To: Seth Mos , spied@yandex.ru, linux-xfs@oss.sgi.com Subject: Re: cvs error Date: Wed, 18 Jun 2003 15:38:19 +0200 User-Agent: KMail/1.5.2 References: <4.3.2.7.2.20030618145704.02c43430@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20030618145704.02c43430@pop.xs4all.nl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200306181538.19067.juergen.sauer@automatix.de> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5IDsR2x026840 X-archive-position: 4391 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: juergen.sauer@automatix.de Precedence: bulk X-list: linux-xfs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am Mittwoch, 18. Juni 2003 14:57 schrieb Seth Mos: > At 16:51 18-6-2003 +0400, spied@yandex.ru wrote: > >i use linux-2.4-xfs from oss.sgi.com > > > >if i try do "cvs -z3 update", update stop on "cvs server: Updating > >linux/scripts/usb", but "cvs update" work fine > > I think you need to update your cvs tools. I think you can find it in the > security errata for your os. This occours on Debian 3.0/r1 also, including all security patches out of security.debian.org. So, it might be a server problem ? mfG Jürgen automatiX Linux Support Crew - -- Jürgen Sauer - AutomatiX GmbH, +49-4209-4699, jojo@automatix.de ** ** Das Linux Systemhaus - Service - Support - Server - Lösungen ** ** http://www.automatix.de ICQ: #344389676 ** -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+8GtLW7UKI9EqarERAsSeAJ9f9YSijMZyDGT3iX2cqhxMr8M3IQCggBfM /zb8MqE4EeI4DQCJnjEJDfI= =d6vk -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Wed Jun 18 06:56:59 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 06:57:01 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5IDuw2x027256 for ; Wed, 18 Jun 2003 06:56:58 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5IEDfmO013355 for ; Wed, 18 Jun 2003 09:13:41 -0500 Received: from thistle-e236.americas.sgi.com (thistle-e236.americas.sgi.com [128.162.236.204]) by flecktone.americas.sgi.com (8.12.9/8.12.9/generic_config-1.2) with ESMTP id h5IDuqqX5158096 for ; Wed, 18 Jun 2003 08:56:52 -0500 (CDT) Received: from clink.americas.sgi.com (clink.americas.sgi.com [128.162.236.153]) by thistle-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5IDuq0L10495094 for ; Wed, 18 Jun 2003 08:56:52 -0500 (CDT) Received: from clink.americas.sgi.com (localhost [127.0.0.1]) by clink.americas.sgi.com (SGI-8.12.5/8.12.5/erikj-IRIX6519-news) with ESMTP id h5IDuqRo025690 for ; Wed, 18 Jun 2003 08:56:52 -0500 (CDT) Received: (from roehrich@localhost) by clink.americas.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5IDupVx025688 for linux-xfs@oss.sgi.com; Wed, 18 Jun 2003 08:56:51 -0500 (CDT) Date: Wed, 18 Jun 2003 08:56:51 -0500 (CDT) From: Dean Roehrich Message-Id: <200306181356.h5IDupVx025688@clink.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - X-archive-position: 4392 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: roehrich@clink.americas.sgi.com Precedence: bulk X-list: linux-xfs When dumping vfs info, print vfs_flag in hex Date: Wed Jun 18 06:56:28 PDT 2003 Workarea: clink.americas.sgi.com:/data/clink/a67/roehrich/2.4.x-xfs Author: roehrich Merged by: roehrich Merged mods: 2.4.x-xfs-kern:slinx:148371a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:148371a linux/fs/xfs/xfsidbg.c - 1.227 - Merge of 2.4.x-xfs-kern:slinx:148371a by roehrich. In print_vfs(), print vfs_flag in hex From owner-linux-xfs@oss.sgi.com Wed Jun 18 06:58:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 06:58:15 -0700 (PDT) Received: from rrzd2.rz.uni-regensburg.de (root@rrzd2.rz.uni-regensburg.de [132.199.1.12]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5IDw92x027676 for ; Wed, 18 Jun 2003 06:58:10 -0700 Received: from rss1.rz.uni-regensburg.de (rss1.rz.uni-regensburg.de [132.199.1.200]) by rrzd2.rz.uni-regensburg.de (8.12.3/8.12.3/Debian -4) with SMTP id h5IDw7TB030108 for ; Wed, 18 Jun 2003 15:58:07 +0200 Received: (qmail 4039 invoked from network); 18 Jun 2003 15:58:07 +0200 Received: from pc9391.physik.uni-regensburg.de (HELO pc9391) (guc28561@132.199.98.219) by rss1.rz.uni-regensburg.de with SMTP; 18 Jun 2003 15:58:07 +0200 Date: Wed, 18 Jun 2003 15:58:07 +0200 From: Christian Guggenberger To: juergen.sauer@automatix.de Cc: Seth Mos , spied@yandex.ru, linux-xfs@oss.sgi.com Subject: Re: cvs error Message-ID: <20030618155807.A25901@pc9391.uni-regensburg.de> References: <4.3.2.7.2.20030618145704.02c43430@pop.xs4all.nl> <200306181538.19067.juergen.sauer@automatix.de> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit In-Reply-To: <200306181538.19067.juergen.sauer@automatix.de>; from juergen.sauer@automatix.de on Wed, Jun 18, 2003 at 15:38:19 +0200 X-Mailer: Balsa 1.2.4 Lines: 25 X-archive-position: 4393 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Christian.Guggenberger@physik.uni-regensburg.de Precedence: bulk X-list: linux-xfs On 18.06.2003 15:38 Juergen Sauer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Am Mittwoch, 18. Juni 2003 14:57 schrieb Seth Mos: > > At 16:51 18-6-2003 +0400, spied@yandex.ru wrote: > > >i use linux-2.4-xfs from oss.sgi.com > > > > > >if i try do "cvs -z3 update", update stop on "cvs server: Updating > > >linux/scripts/usb", but "cvs update" work fine > > > > I think you need to update your cvs tools. I think you can find it in the > > security errata for your os. > > This occours on Debian 3.0/r1 also, including all security patches > out of security.debian.org. > > So, it might be a server problem ? > you really need cvs-1.11.5 or newer. So you might want to backport Debian/unstable's cvs to woody... Christian From owner-linux-xfs@oss.sgi.com Wed Jun 18 07:56:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 07:56:56 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5IEub2x029622 for ; Wed, 18 Jun 2003 07:56:38 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5I2wPE0028857 for ; Tue, 17 Jun 2003 19:58:25 -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 h5I2v7JA011104 for ; Wed, 18 Jun 2003 12:57:08 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5I2v210011089 for linux-xfs@oss.sgi.com; Wed, 18 Jun 2003 12:57:02 +1000 (EST) Date: Wed, 18 Jun 2003 12:57:02 +1000 (EST) From: Nathan Scott Message-Id: <200306180257.h5I2v210011089@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - remount readonly X-archive-position: 4394 X-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 Turn log head/tail check into an assert - this condition should never be true here. Date: Tue Jun 17 19:50:02 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:151422a linux/fs/xfs/xfs_log_recover.c - 1.271 Fix remount readonly so it really wont write dummy log records. Date: Tue Jun 17 19:53:59 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:151423a linux/fs/xfs/xfs_vfsops.c - 1.421 linux/fs/xfs/linux/xfs_vfs.h - 1.42 From owner-linux-xfs@oss.sgi.com Wed Jun 18 09:52:14 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 09:52:32 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5IGqE2x002136 for ; Wed, 18 Jun 2003 09:52:14 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5IGqENv002135 for linux-xfs@oss.sgi.com; Wed, 18 Jun 2003 09:52:14 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5IGqC31002120 for ; Wed, 18 Jun 2003 09:52:12 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5IGXxnZ001575; Wed, 18 Jun 2003 09:33:59 -0700 Date: Wed, 18 Jun 2003 09:33:59 -0700 Message-Id: <200306181633.h5IGXxnZ001575@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 249] Installing RedHat9 with SGI-XFS installer leades to network admin problem X-Bugzilla-Reason: AssignedTo X-archive-position: 4395 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=249 ------- Additional Comments From logiplexsoftware@earthlink.net 2003-18-06 09:33 PDT ------- This problem is fixed by getting a more recent version of redhat-config-network: http://people.redhat.com/harald/redhat-config-network/index.html ------- 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 Wed Jun 18 14:52:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Jun 2003 14:52:32 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5ILqF2x011037 for ; Wed, 18 Jun 2003 14:52:15 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5ILqFKL011036 for linux-xfs@oss.sgi.com; Wed, 18 Jun 2003 14:52:15 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5ILqD31011022 for ; Wed, 18 Jun 2003 14:52:13 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5IL9qqV010404; Wed, 18 Jun 2003 14:09:52 -0700 Date: Wed, 18 Jun 2003 14:09:52 -0700 Message-Id: <200306182109.h5IL9qqV010404@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 251] New: FIOQSIZE not defined for x86-64 X-Bugzilla-Reason: AssignedTo X-archive-position: 4396 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=251 Summary: FIOQSIZE not defined for x86-64 Product: Linux XFS Version: Current Platform: AMD OS/Version: Linux Status: NEW Severity: normal Priority: Medium Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: software@smugmug.com /include/asm-x86_64/ioctls.h doesn't get patched with the latest weekly snapshot (June 17, 2003 for 2.4.21) to include the #define for FIOQSIZE like the other archs do. ------- 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 Jun 19 07:29:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 07:29:55 -0700 (PDT) Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JETZ2x003864 for ; Thu, 19 Jun 2003 07:29:36 -0700 Received: from westrelay04.boulder.ibm.com (westrelay04.boulder.ibm.com [9.17.193.32]) by e31.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h5JETTu8255866 for ; Thu, 19 Jun 2003 10:29:29 -0400 Received: from austin.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay04.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h5JETSVd115538 for ; Thu, 19 Jun 2003 08:29:29 -0600 Received: from popmail.austin.ibm.com (popmail.austin.ibm.com [9.41.248.164]) by austin.ibm.com (8.12.9/8.12.9) with ESMTP id h5JETSIB113816 for ; Thu, 19 Jun 2003 09:29:28 -0500 Received: from austin.ibm.com (patches.austin.ibm.com [9.53.94.35]) by popmail.austin.ibm.com (AIX4.3/8.9.3p2/8.7-client1.01) with ESMTP id JAA36678 for ; Thu, 19 Jun 2003 09:29:27 -0500 Message-ID: <3EF1C932.4080706@austin.ibm.com> Date: Thu, 19 Jun 2003 09:31:14 -0500 From: Steven Pratt User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: hangs running dbench with 16 clients Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4397 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: slpratt@austin.ibm.com Precedence: bulk X-list: linux-xfs While trying to do performance regression testing on 2.5.xx kernels, we are seeing hangs when runnuing xfs with 16 clients quite often. No error messages, just that dbench does not complete. XFS is hte only filesystem the causes this behavior with dbench, It is very reproducibly on the 2.5.7x kernels. Has anyone else seen this? What kind of debug information would you need. Steve From owner-linux-xfs@oss.sgi.com Thu Jun 19 08:00:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 08:00:49 -0700 (PDT) Received: from mail1.arkeia.com (knox-gw.knox-software.easynet.fr [212.180.90.105]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JF0U2x004610 for ; Thu, 19 Jun 2003 08:00:32 -0700 Received: from vulcain.knox.com (vulcain.knox.com [192.168.7.145]) by mail1.arkeia.com (Postfix) with ESMTP id 665441A175 for ; Thu, 19 Jun 2003 17:00:24 +0200 (CEST) Received: from aym by vulcain.knox.com with local (Exim 3.36 #1 (Debian)) id 19T0tm-0000JI-00 for ; Thu, 19 Jun 2003 17:00:26 +0200 Date: Thu, 19 Jun 2003 17:00:26 +0200 From: Andre Majorel To: linux-xfs@oss.sgi.com Subject: ACLs on both ext2/ext3 and XFS Message-ID: <20030619150026.GA576@teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.3i X-archive-position: 4398 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: amajorel@teaser.fr Precedence: bulk X-list: linux-xfs What's the wisdom on building a kernel with ACL support for both ext2/ext3 and XFS ? I tried applying patches in this order : linux-2.4.20.tar.bz2 ea-2.4.20-0.8.58.diff.gz acl-2.4.20-0.8.57.diff.gz nfsacl-2.4.20-0.8.59.diff.gz xfs-2.4.20-split-only.bz2 xfs-2.4.20-split-quota32.bz2 xfs-2.4.20-split-kernel.bz2 xfs-2.4.20-split-misc.bz2 xfs-2.4.20-split-acl.bz2 It goes fine modulo a bunch of "(offset N lines)" messages but as soon as I reach xfs-2.4.20-split-acl.bz2, problems appear ("Reversed (or previously applied) patch detected! Assume -R?"). -- André Majorel http://www.teaser.fr/~amajorel/ From owner-linux-xfs@oss.sgi.com Thu Jun 19 08:09:45 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 08:10:02 -0700 (PDT) Received: from blake.timetraveller.org ([203.23.43.9]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JF9h2x005178 for ; Thu, 19 Jun 2003 08:09:44 -0700 Received: from blake.timetraveller.org (blake.timetraveller.org [203.23.43.10]) by blake.timetraveller.org (8.12.3/8.12.3) with ESMTP id h5JF9c8U031868 for ; Fri, 20 Jun 2003 01:09:38 +1000 Date: Thu, 19 Jun 2003 11:09:38 -0400 (EDT) From: Robert Brockway To: linux-xfs@oss.sgi.com Subject: RE: How to reconstruct an xfs filesystem and restore all datas? In-Reply-To: <003601c334c2$b9d1cca0$89cca8c0@sn1> Message-ID: References: <003601c334c2$b9d1cca0$89cca8c0@sn1> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4399 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: robert@timetraveller.org Precedence: bulk X-list: linux-xfs On Tue, 17 Jun 2003, Scott Liu wrote: > Dears, > Sorry, that's on a hard disk. I believe the previous poster was asking if you had any backups, eg tape. The cheapest way to protect your data is to have offsite backups. It protects from a myriad of different problems (accedental deletions like yours, hard drive crashes, the building burning down, etc). Generally, if you lose data, but didn't keep any backups, there is little sympathy out there. The message about backups have been hounded in to people for _decades_ and problems like this still occur regularly. I don't know if this is a home system or a busines system. Business users fail to backup at their own peril. Home users can also setup an effective backup for quite a low price. At home, I use an external firewire drive (actually an IDE drive in an external firewire casing), and keep it offsite. The few hundred dollars the hardware cost (now cheaper anyway) is only a small fraction of the value I place on my personal data. As other have noted, recovery from data still on disk may be possible. There are companies who specialise in data recovery - but they cost. In the end the cheapest way to protect data is to back it up and keep it offsite. It may be too late for your data unless you have the capability to examine the filesystem at a low level and attempt to recover the data, or the money to pay someone else to do it. Rob -- Robert Brockway B.Sc. email: robert@timetraveller.org ICQ: 104781119 Linux counter project ID #16440 (http://counter.li.org) "The earth is but one country and mankind its citizens" -Baha'u'llah From owner-linux-xfs@oss.sgi.com Thu Jun 19 08:27:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 08:27:26 -0700 (PDT) Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.133]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JFR42x005763 for ; Thu, 19 Jun 2003 08:27:07 -0700 Received: from westrelay05.boulder.ibm.com (westrelay05.boulder.ibm.com [9.17.193.33]) by e35.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h5JFQwxe257286; Thu, 19 Jun 2003 11:26:58 -0400 Received: from austin.ibm.com (d03av03.boulder.ibm.com [9.17.193.83]) by westrelay05.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h5JFQu8A080440; Thu, 19 Jun 2003 09:26:57 -0600 Received: from popmail.austin.ibm.com (popmail.austin.ibm.com [9.41.248.164]) by austin.ibm.com (8.12.9/8.12.9) with ESMTP id h5JFQuGg118644; Thu, 19 Jun 2003 10:26:56 -0500 Received: from austin.ibm.com (patches.austin.ibm.com [9.53.94.35]) by popmail.austin.ibm.com (AIX4.3/8.9.3p2/8.7-client1.01) with ESMTP id KAA65810; Thu, 19 Jun 2003 10:26:56 -0500 Message-ID: <3EF1D6AA.4050200@austin.ibm.com> Date: Thu, 19 Jun 2003 10:28:42 -0500 From: Steven Pratt User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: hangs running dbench with 16 clients References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4400 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: slpratt@austin.ibm.com Precedence: bulk X-list: linux-xfs Steve Lord wrote: >On Thu, 2003-06-19 at 09:31, Steven Pratt wrote: > > >>While trying to do performance regression testing on 2.5.xx kernels, we >>are seeing hangs when runnuing xfs with 16 clients quite often. No >>error messages, just that dbench does not complete. XFS is hte only >>filesystem the causes this behavior with dbench, It is very >>reproducibly on the 2.5.7x kernels. Has anyone else seen this? What >>kind of debug information would you need. >> >>Steve >> >> > >Hi Steve, > >Is this the performance regression tests which get run on 2.5 kernels? >I have seen the results, never a comment about hangs before. > Yes, this is the nightly regression runs that we have been doing on the 2.5 kernel series. We have been more worried about changes in performance than functional issues to this point (that is our mission), Since I am running multiple runs of dbench and averaging results, having one run die still allows us to get numbers. I just looked over the results again and I see problem both on single client and on 16 client runs. I seem to remember that we have problem more often on 64 client runs but dropped that version for lack of runtime. Should also not that this may not be as reproducible as I first mentioned, seems more like 1 out of 8 runs or so dies. >Unfortunately, we have been somewhat tied up with 2.4 things and >2.5 is not getting as much air time - and kdb does not work which >makes debugging much more interesting. Let me try it out and see >what happens, and details about the setup you see this in would >be appreciated. > Understand about 2.5 work. Here is a link to the test machine setup information. http://ltcperf.ncsa.uiuc.edu/data/2.5.71/2.4.20-vs-2.5.71/HardwareSoftware.html > We also have a bunch of code with fixes here we need >to sync to Linus, it is always possible you are hitting one of >those, did you ever try pulling from the cvs tree on oss.sgi.com? >The xfs in there is more upto date, if that makes the problem >go away, then I need to get an update to Linus sooner rather than >later. > > No, we are not doing anything except standard trees at the moment. This is 99% automated so anything like CVS does not fit well. If you had a patch against any recent version of 2.5 I could give that a go. Steve From owner-linux-xfs@oss.sgi.com Thu Jun 19 08:40:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 08:40:32 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JFeC2x006643 for ; Thu, 19 Jun 2003 08:40:13 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5JFuxmO026970 for ; Thu, 19 Jun 2003 10:56:59 -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 h5JFe6qX5390232; Thu, 19 Jun 2003 10:40:06 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5JFe6Rn128767417; Thu, 19 Jun 2003 10:40:06 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5JFe6H07556; Thu, 19 Jun 2003 10:40:06 -0500 Subject: Re: hangs running dbench with 16 clients From: Steve Lord To: Steven Pratt Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EF1D6AA.4050200@austin.ibm.com> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056037205.1773.101.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 19 Jun 2003 10:40:06 -0500 X-archive-position: 4401 X-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 On Thu, 2003-06-19 at 10:28, Steven Pratt wrote: > Steve Lord wrote: > > >On Thu, 2003-06-19 at 09:31, Steven Pratt wrote: > > > > > >>While trying to do performance regression testing on 2.5.xx kernels, we > >>are seeing hangs when runnuing xfs with 16 clients quite often. No > >>error messages, just that dbench does not complete. XFS is hte only > >>filesystem the causes this behavior with dbench, It is very > >>reproducibly on the 2.5.7x kernels. Has anyone else seen this? What > >>kind of debug information would you need. > >> > >>Steve > >> > >> > > > >Hi Steve, > > > >Is this the performance regression tests which get run on 2.5 kernels? > >I have seen the results, never a comment about hangs before. > > > Yes, this is the nightly regression runs that we have been doing on the > 2.5 kernel series. We have been more worried about changes in > performance than functional issues to this point (that is our mission), > Since I am running multiple runs of dbench and averaging results, having > one run die still allows us to get numbers. I just looked over the > results again and I see problem both on single client and on 16 client > runs. I seem to remember that we have problem more often on 64 client > runs but dropped that version for lack of runtime. Should also not that > this may not be as reproducible as I first mentioned, seems more like 1 > out of 8 runs or so dies. OK, I have dbench 16 running in a loop here, if it keeps going for a couple of hours I will send you a diff from 2.5.72 and we can see if it fixes things for you. I will try a second box with a vanilla Linus kernel and see if I can hit it there. So far no hangs, but there do seem to be temporary stalls occasionally which is odd. > > >Unfortunately, we have been somewhat tied up with 2.4 things and > >2.5 is not getting as much air time - and kdb does not work which > >makes debugging much more interesting. Let me try it out and see > >what happens, and details about the setup you see this in would > >be appreciated. > > > Understand about 2.5 work. Here is a link to the test machine setup > information. > http://ltcperf.ncsa.uiuc.edu/data/2.5.71/2.4.20-vs-2.5.71/HardwareSoftware.html > Hmm, I don't have 8 cpus in all the boxes I can use for this right now, never mind 8 cpus in each! Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Jun 19 10:20:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 10:21:05 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JHKm2x009659 for ; Thu, 19 Jun 2003 10:20:48 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5JEnDE0008665 for ; Thu, 19 Jun 2003 07:49:14 -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 h5JEnDqX5385047; Thu, 19 Jun 2003 09:49:13 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5JEnCRn128685604; Thu, 19 Jun 2003 09:49:12 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5JEnCL07497; Thu, 19 Jun 2003 09:49:12 -0500 Subject: Re: hangs running dbench with 16 clients From: Steve Lord To: Steven Pratt Cc: linux-xfs@oss.sgi.com In-Reply-To: <3EF1C932.4080706@austin.ibm.com> References: <3EF1C932.4080706@austin.ibm.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056034152.1772.92.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 19 Jun 2003 09:49:12 -0500 X-archive-position: 4402 X-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 On Thu, 2003-06-19 at 09:31, Steven Pratt wrote: > While trying to do performance regression testing on 2.5.xx kernels, we > are seeing hangs when runnuing xfs with 16 clients quite often. No > error messages, just that dbench does not complete. XFS is hte only > filesystem the causes this behavior with dbench, It is very > reproducibly on the 2.5.7x kernels. Has anyone else seen this? What > kind of debug information would you need. > > Steve Hi Steve, Is this the performance regression tests which get run on 2.5 kernels? I have seen the results, never a comment about hangs before. Unfortunately, we have been somewhat tied up with 2.4 things and 2.5 is not getting as much air time - and kdb does not work which makes debugging much more interesting. Let me try it out and see what happens, and details about the setup you see this in would be appreciated. We also have a bunch of code with fixes here we need to sync to Linus, it is always possible you are hitting one of those, did you ever try pulling from the cvs tree on oss.sgi.com? The xfs in there is more upto date, if that makes the problem go away, then I need to get an update to Linus sooner rather than later. Thanks Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Jun 19 10:41:54 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 10:42:07 -0700 (PDT) Received: from mail.cnes.com (mail.cnes.com [208.179.92.38]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JHfr2x011644 for ; Thu, 19 Jun 2003 10:41:53 -0700 Received: from oz.cnes.com (wall.cnes.com [208.179.92.60]) by mail.cnes.com (8.12.9/8.12.9) with ESMTP id h5JHfmDv018749 for ; Thu, 19 Jun 2003 10:41:48 -0700 Received: from localhost (localhost [127.0.0.1]) by oz.cnes.com (8.9.3/8.9.3) with ESMTP id KAA12846 for ; Thu, 19 Jun 2003 10:41:47 -0700 (PDT) Date: Thu, 19 Jun 2003 10:41:47 -0700 From: Scott Jepson To: linux-xfs@oss.sgi.com Subject: Frag. check Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4403 X-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@cnes.com Precedence: bulk X-list: linux-xfs Hi, Could someone tell me if there is a command or program that would tell me how much of the drive is fragmented? This would be helpful in determing when to run xfs_fsr. Thanks, -Scott ---------------------------------------------------------------- Scott Jepson, Managing Partner Email: scott@cnes.com Creative Network Services, LLC http://www.cnes.com (310)470-6140 ---------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Thu Jun 19 11:59:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 12:00:11 -0700 (PDT) Received: from click.cz (black.click.cz [62.141.0.10]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JIxp2x012682 for ; Thu, 19 Jun 2003 11:59:52 -0700 Received: from alienAngel.upjs.sk (gprsh1.isp.t-mobile.cz [62.141.24.1]) by click.cz (8.12.9/8.12.9) with ESMTP id h5JIxaUr020579; Thu, 19 Jun 2003 20:59:44 +0200 (MET DST) Received: from localhost (ja@localhost) by alienAngel.upjs.sk (8.12.6/8.12.6/Submit) with ESMTP id h5JIx1gX025308; Thu, 19 Jun 2003 20:59:03 +0200 X-Authentication-Warning: alienAngel.home.sk: ja owned process doing -bs Date: Thu, 19 Jun 2003 20:59:01 +0200 (CEST) From: Jan Derfinak X-X-Sender: ja@alienAngel.home.sk To: Scott Jepson cc: linux-xfs@oss.sgi.com Subject: Re: Frag. check In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4404 X-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 On Thu, 19 Jun 2003, Scott Jepson wrote: > Hi, > Could someone tell me if there is a command or program that would > tell me how much of the drive is fragmented? This would be helpful > in determing when to run xfs_fsr. xfs_db -r -c frag /dev/XXX jan -- From owner-linux-xfs@oss.sgi.com Thu Jun 19 12:37:10 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 12:37:28 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JJb92x027231 for ; Thu, 19 Jun 2003 12:37:10 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5JGqmE0018071 for ; Thu, 19 Jun 2003 09:52:48 -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 h5JFwRqX5399652; Thu, 19 Jun 2003 10:58: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 h5JFwQYk12571560; Thu, 19 Jun 2003 10:58:27 -0500 (CDT) Subject: Re: hangs running dbench with 16 clients From: Eric Sandeen To: Steven Pratt Cc: Steve Lord , linux-xfs@oss.sgi.com In-Reply-To: <3EF1D6AA.4050200@austin.ibm.com> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> Content-Type: text/plain Organization: Message-Id: <1056038306.8113.8.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 19 Jun 2003 10:58:26 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 4405 X-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 Hi Steve - nightly patches from "latest" 2.5 to xfs CVS can be found at: ftp://oss.sgi.com/projects/xfs/download/patches-2.5 there seems to be some old cruft there, you probably want: ftp://oss.sgi.com/projects/xfs/download/patches-2.5/linux-2.5.72-xfs-2003-06-18.patch.bz2 That patch is the whole diff, including kdb changes. -Eric On Thu, 2003-06-19 at 10:28, Steven Pratt wrote: > No, we are not doing anything except standard trees at the moment. This > is 99% automated so anything like CVS does not fit well. If you had a > patch against any recent version of 2.5 I could give that a go. > > Steve -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Thu Jun 19 12:41:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 12:41:46 -0700 (PDT) Received: from mail.cnes.com (mail.cnes.com [208.179.92.38]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JJff2x001496 for ; Thu, 19 Jun 2003 12:41:41 -0700 Received: from oz.cnes.com (wall.cnes.com [208.179.92.60]) by mail.cnes.com (8.12.9/8.12.9) with ESMTP id h5JJfZDv019938 for ; Thu, 19 Jun 2003 12:41:36 -0700 Received: from localhost (localhost [127.0.0.1]) by oz.cnes.com (8.9.3/8.9.3) with ESMTP id MAA13050 for ; Thu, 19 Jun 2003 12:41:35 -0700 (PDT) Date: Thu, 19 Jun 2003 12:41:35 -0700 From: Scott Jepson To: linux-xfs@oss.sgi.com Subject: Re: Frag. check In-Reply-To: <1056049096.11908.151.camel@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4406 X-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@cnes.com Precedence: bulk X-list: linux-xfs Thanks guys. -Scott ---------------------------------------------------------------- Scott Jepson, Managing Partner Email: scott@cnes.com Creative Network Services, LLC http://www.cnes.com (310)470-6140 ---------------------------------------------------------------- On 19 Jun 2003, Steve Lord wrote: > Date: 19 Jun 2003 13:58:18 -0500 > From: Steve Lord > To: Scott Jepson > Cc: linux-xfs@oss.sgi.com > Subject: Re: Frag. check > > On Thu, 2003-06-19 at 12:41, Scott Jepson wrote: > > Hi, > > Could someone tell me if there is a command or program that would > > tell me how much of the drive is fragmented? This would be helpful > > in determing when to run xfs_fsr. > > > > Thanks, > > -Scott > > > > xfs_db -r /dev/xxx -c freesp > > freesp has options for more details if you look in the man page or help > text for xfs_db. > > Steve > > -- > > Steve Lord voice: +1-651-683-3511 > Principal Engineer, Filesystem Software email: lord@sgi.com > > From owner-linux-xfs@oss.sgi.com Thu Jun 19 12:52:47 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 12:53:00 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JJqj2x004752 for ; Thu, 19 Jun 2003 12:52:46 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 4EBBE14F30; Thu, 19 Jun 2003 21:52:40 +0200 (MEST) Date: Thu, 19 Jun 2003 21:52:39 +0200 From: Andi Kleen To: Steve Lord Cc: Steven Pratt , linux-xfs@oss.sgi.com Subject: Re: hangs running dbench with 16 clients Message-ID: <20030619195239.GB13952@wotan.suse.de> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1056037205.1773.101.camel@jen.americas.sgi.com> X-archive-position: 4407 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs > > >2.5 is not getting as much air time - and kdb does not work which http://www.ccur.com/realtime/oss/ has a 2.5.69 kdb which could be probably used with .72 with minor changes. But I can recommend kgdb, which in its latest iterations (e.g. the one in the -mm tree) is more powerful and of course is source level. -Andi From owner-linux-xfs@oss.sgi.com Thu Jun 19 12:59:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 12:59:33 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JJxS2x005232 for ; Thu, 19 Jun 2003 12:59:29 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5JKGGmO012024 for ; Thu, 19 Jun 2003 15:16:16 -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 h5JJxNqX5434760; Thu, 19 Jun 2003 14:59:23 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5JJxMRn127251225; Thu, 19 Jun 2003 14:59:23 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5JJxMI15292; Thu, 19 Jun 2003 14:59:22 -0500 Subject: Re: hangs running dbench with 16 clients From: Steve Lord To: Andi Kleen Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030619195239.GB13952@wotan.suse.de> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> <20030619195239.GB13952@wotan.suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056052761.1772.172.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 19 Jun 2003 14:59:22 -0500 X-archive-position: 4408 X-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 On Thu, 2003-06-19 at 14:52, Andi Kleen wrote: > > > >2.5 is not getting as much air time - and kdb does not work which > > http://www.ccur.com/realtime/oss/ has a 2.5.69 kdb which could > be probably used with .72 with minor changes. > > But I can recommend kgdb, which in its latest iterations > (e.g. the one in the -mm tree) is more powerful and of course > is source level. Thanks Andi, Got to try kgdb one day, just need to find the time! The one thing missing there is kdb has all this xfs support code in it for walking data structures and formatting them up nicely. I know you can do structure walks, but kdb understands a lot about xfs. Meanwhile dbench has been running on vanilla 2.5.72 and TOT xfs for several hours here without a hang. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:01:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:01:27 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JK1N2x006648 for ; Thu, 19 Jun 2003 13:01:23 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5JKIBmO012274 for ; Thu, 19 Jun 2003 15:18:11 -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 h5JIwKqX5404699; Thu, 19 Jun 2003 13:58:20 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5JIwKRn125932864; Thu, 19 Jun 2003 13:58:20 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5JIwKi13139; Thu, 19 Jun 2003 13:58:20 -0500 Subject: Re: Frag. check From: Steve Lord To: Scott Jepson Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056049096.11908.151.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 19 Jun 2003 13:58:18 -0500 X-archive-position: 4409 X-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 On Thu, 2003-06-19 at 12:41, Scott Jepson wrote: > Hi, > Could someone tell me if there is a command or program that would > tell me how much of the drive is fragmented? This would be helpful > in determing when to run xfs_fsr. > > Thanks, > -Scott > xfs_db -r /dev/xxx -c freesp freesp has options for more details if you look in the man page or help text for xfs_db. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:13:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:13:44 -0700 (PDT) Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.131]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKDM2x008274 for ; Thu, 19 Jun 2003 13:13:23 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e33.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h5JKDGkj300952; Thu, 19 Jun 2003 16:13:16 -0400 Received: from austin.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay02.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h5JKDFj1073556; Thu, 19 Jun 2003 14:13:16 -0600 Received: from popmail.austin.ibm.com (popmail.austin.ibm.com [9.41.248.164]) by austin.ibm.com (8.12.9/8.12.9) with ESMTP id h5JKDFIB118650; Thu, 19 Jun 2003 15:13:15 -0500 Received: from austin.ibm.com (dyn94122365.austin.ibm.com [9.41.223.65]) by popmail.austin.ibm.com (AIX4.3/8.9.3p2/8.7-client1.01) with ESMTP id PAA32762; Thu, 19 Jun 2003 15:13:14 -0500 Message-ID: <3EF219C4.90005@austin.ibm.com> Date: Thu, 19 Jun 2003 15:15:00 -0500 From: Steven Pratt User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Sandeen CC: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: hangs running dbench with 16 clients References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056038306.8113.8.camel@stout.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4410 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: slpratt@austin.ibm.com Precedence: bulk X-list: linux-xfs Eric Sandeen wrote: >Hi Steve - nightly patches from "latest" 2.5 to xfs CVS can be found at: > >ftp://oss.sgi.com/projects/xfs/download/patches-2.5 > >there seems to be some old cruft there, you probably want: > >ftp://oss.sgi.com/projects/xfs/download/patches-2.5/linux-2.5.72-xfs-2003-06-18.patch.bz2 > >That patch is the whole diff, including kdb changes. > > > Well here are the results from running linux-2.5.72-xfs-2003-06-18.patch.bz2 kernel bug at fs/xfs/pagebuf/page_buf.c:1288! invalid operand: 0000 [#1] CPU: 7 EIP: 0060:[] Not tainted EFLAGS: 00010202 EIP is at bio_end_io_pagebuf+0xd7/0x160 eax: 00000001 ebx: f6aef980 ecx: 00000000 edx: c1887ef8 esi: f5e79770 edi: 00000000 ebp: f5e469e0 esp: f690d9b4 ds: 007b es: 007b ss: 0068 Process dbench (pid: 11047, threadinfo=f690c000 task=f60f8060) Stack: 00010000 00000000 00000000 fffe0005 00000009 00001000 f5e469e0 00000000 f7fae000 00000200 c015acf5 f5e469e0 00000200 00000000 f5b65878 00000200 f5e469e0 c02f79a1 f5e469e0 00000200 00000000 f690db24 f5e469e0 00000000 Call Trace: [] bio_endio+0x55/0x80 [] __end_that_request_first+0x221/0x250 [] scsi_end_request+0x3b/0xc0 [] scsi_io_completion+0x14d/0x470 [] mempool_free+0x41/0x80 [] sd_rw_intr+0x4e/0x1a0 [] scsi_finish_command+0x8c/0xc0 [] scsi_softirq+0xb8/0xe0 [] do_softirq+0xc7/0xd0 [] do_IRQ+0xf7/0x120 [] common_interrupt+0x18/0x20 [] setup_port+0x4b/0xf0 [] get_request+0xad/0x1a0 [] __make_request+0xc6/0x4c0 [] generic_make_request+0x120/0x1b0 [] autoremove_wake_function+0x0/0x50 [] bio_add_page+0x16a/0x170 [] submit_bio+0x54/0xa0 [] pagebuf_iorequest+0x241/0x3e0 [] default_wake_function+0x0/0x30 [] default_wake_function+0x0/0x30 [] xfs_bdstrat_cb+0x0/0x50 [] xfs_bdstrat_cb+0x3e/0x50 [] pagebuf_iostart+0x52/0xb0 [] xfs_iflush+0x21b/0x4f0 [] xfs_inode_item_push+0x1e/0x40 [] xfs_trans_push_ail+0xdf/0x230 [] xlog_grant_push_ail+0x154/0x1d0 48 59521 94.40 MB/sec [] xfs_log_reserve+0xb6/0xd0 [] xfs_trans_reserve+0x7d/0x1c0 [] xfs_create+0x294/0x7d0 [] scsi_softirq+0xb8/0xe0 [] xfs_iunlock+0x3e/0x80 [] linvfs_mknod+0x1da/0x250 [] linvfs_create+0x27/0x30 [] vfs_create+0x71/0xc0 [] open_namei+0x3af/0x410 [] filp_open+0x43/0x70 [] sys_open+0x5b/0x90 [] syscall_call+0x7/0xb Code: 0f 0b 08 05 07 dd 41 c0 eb a8 89 d0 e8 a8 fe ea ff eb 9f 8d <0>Kernel panic: Fatal exception in interrupt In interrupt handler - not syncing From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:14:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:14:51 -0700 (PDT) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKEj2x008663 for ; Thu, 19 Jun 2003 13:14:46 -0700 Received: from myrealbox.com nwourms@smtp-send.myrealbox.com [130.127.122.186] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.34 $ on Novell NetWare via secured & encrypted transport (TLS); Thu, 19 Jun 2003 13:14:44 -0700 Message-ID: <3EF2198F.2000700@myrealbox.com> Date: Thu, 19 Jun 2003 16:14:07 -0400 From: Nicholas Wourms User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.2) Gecko/20030208 MultiZilla/v1.1.20 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andi Kleen CC: Steven Pratt , linux-xfs@oss.sgi.com Subject: Re: hangs running dbench with 16 clients References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> <20030619195239.GB13952@wotan.suse.de> X-Enigmail-Version: 0.75.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4411 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nwourms@myrealbox.com Precedence: bulk X-list: linux-xfs Andi Kleen wrote: >>>>2.5 is not getting as much air time - and kdb does not work which >>> > > http://www.ccur.com/realtime/oss/ has a 2.5.69 kdb which could > be probably used with .72 with minor changes. > > But I can recommend kgdb, which in its latest iterations > (e.g. the one in the -mm tree) is more powerful and of course > is source level. > Well that's all fine & good if you have the extra dumb (or not-so-dumb) terminals lying around to use it, but not everyone does. Furthermore, getting things "set-up" for kgdb is just a PITA compared to kdb just working as OOOPS happen (again, who wants to dedicate a machine to kgdb full-time?). Perhaps what might be done is to merge the two debuggers to give the user the choice of in-kernel debugging or remote core debugging. In other words, make the debugging of ooops/panics a boot argument? I don't know much about kgdb, so as to how practical this might be is another question. Cheers, Nicholas P.S. - Thanks for the link to the updated patch, been waiting for something like this for awhile... From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:16:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:16:09 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKG42x009145 for ; Thu, 19 Jun 2003 13:16:05 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 0CBF714EF8; Thu, 19 Jun 2003 22:15:59 +0200 (MEST) Date: Thu, 19 Jun 2003 22:15:58 +0200 From: Andi Kleen To: Steve Lord Cc: Andi Kleen , linux-xfs@oss.sgi.com Subject: Re: hangs running dbench with 16 clients Message-ID: <20030619201558.GE13952@wotan.suse.de> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> <20030619195239.GB13952@wotan.suse.de> <1056052761.1772.172.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1056052761.1772.172.camel@jen.americas.sgi.com> X-archive-position: 4412 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs > The one thing missing there is kdb has all this xfs support code > in it for walking data structures and formatting them up nicely. > I know you can do structure walks, but kdb understands a lot about > xfs. I guess you could rewrite that using gdb macros, but it would be some work ;-) Actually I think the -mm kgdb supports remote calls, so you could do you could do p kdb_xfs_command() and catch the output using the gdbconsole. > > Meanwhile dbench has been running on vanilla 2.5.72 and TOT xfs for > several hours here without a hang. I can give it a try on a 4CPU box and see if sometimes turns up. -Andi From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:32:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:32:21 -0700 (PDT) Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKW52x009784 for ; Thu, 19 Jun 2003 13:32:05 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id C063714F3B; Thu, 19 Jun 2003 22:31:59 +0200 (MEST) Date: Thu, 19 Jun 2003 22:31:59 +0200 From: Andi Kleen To: Nicholas Wourms Cc: Andi Kleen , Steven Pratt , linux-xfs@oss.sgi.com Subject: Re: hangs running dbench with 16 clients Message-ID: <20030619203159.GF13952@wotan.suse.de> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> <20030619195239.GB13952@wotan.suse.de> <3EF2198F.2000700@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EF2198F.2000700@myrealbox.com> X-archive-position: 4413 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak@suse.de Precedence: bulk X-list: linux-xfs > Well that's all fine & good if you have the extra dumb (or not-so-dumb) > terminals lying around to use it, but not everyone does. Furthermore, > getting things "set-up" for kgdb is just a PITA compared to kdb just > working as OOOPS happen (again, who wants to dedicate a machine to kgdb > full-time?). Perhaps what might be done is to merge the two debuggers For oopses crash dumps are actually more practical. You have two main use cases: - Serious debugging of broken code. Nothing can beat source level here, assembly level is just a pita. - Post Mortem Analysis after a crash Tools like crash or lkcd do this quite well, with less overhead. kdb sits somewhere inbetween, but does nothing well. > to give the user the choice of in-kernel debugging or remote core > debugging. In other words, make the debugging of ooops/panics a boot > argument? I don't know much about kgdb, so as to how practical this > might be is another question. It's not practical. kdb is much more complex than kgdb. There used to be a user land proxy to run kdb from kgdb, but it never worked really well and the latest kgdb stubs are much more powerful. -Andi (who worked on a KDB port to another architecture, but gave up and switched to kgdb because implementing dwarf2 unwinding in the kernel is just too ugly) From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:33:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:33:36 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKXU2x010200 for ; Thu, 19 Jun 2003 13:33:31 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5JKoImO015485 for ; Thu, 19 Jun 2003 15:50:18 -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 h5JKXPqX5418833; Thu, 19 Jun 2003 15:33:25 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5JKXPRn112710751; Thu, 19 Jun 2003 15:33:25 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5JKXPM15383; Thu, 19 Jun 2003 15:33:25 -0500 Subject: Re: hangs running dbench with 16 clients From: Steve Lord To: Andi Kleen Cc: linux-xfs@oss.sgi.com In-Reply-To: <20030619201558.GE13952@wotan.suse.de> References: <3EF1C932.4080706@austin.ibm.com> <1056034152.1772.92.camel@jen.americas.sgi.com> <3EF1D6AA.4050200@austin.ibm.com> <1056037205.1773.101.camel@jen.americas.sgi.com> <20030619195239.GB13952@wotan.suse.de> <1056052761.1772.172.camel@jen.americas.sgi.com> <20030619201558.GE13952@wotan.suse.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056054804.11908.180.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 19 Jun 2003 15:33:25 -0500 X-archive-position: 4414 X-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 On Thu, 2003-06-19 at 15:15, Andi Kleen wrote: > > The one thing missing there is kdb has all this xfs support code > > in it for walking data structures and formatting them up nicely. > > I know you can do structure walks, but kdb understands a lot about > > xfs. > > I guess you could rewrite that using gdb macros, but it would > be some work ;-) > > Actually I think the -mm kgdb supports remote calls, so you could do > you could do p kdb_xfs_command() and catch the output using the > gdbconsole. Ugh ugh ugh, 'In my copious free time' as the saying goes around here! > > > > > Meanwhile dbench has been running on vanilla 2.5.72 and TOT xfs for > > several hours here without a hang. > > I can give it a try on a 4CPU box and see if sometimes turns up. Well, I have pushed almost a Tbyte of data through dbench today and it just keeps plugging away here. So, not much I can do here to figure it out. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:39:53 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:40:11 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKdq2x010725 for ; Thu, 19 Jun 2003 13:39:53 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h5JKdkE0005882 for ; Thu, 19 Jun 2003 13:39:46 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id GAA25316; Fri, 20 Jun 2003 06:38:26 +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 h5JKcP3K008325; Fri, 20 Jun 2003 06:38:25 +1000 (EST) Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5JKcOUv008336; Fri, 20 Jun 2003 06:38:24 +1000 (EST) Date: Fri, 20 Jun 2003 06:38:24 +1000 From: Nathan Scott To: Andre Majorel Cc: linux-xfs@oss.sgi.com Subject: Re: ACLs on both ext2/ext3 and XFS Message-ID: <20030620063824.A8301@wobbly.melbourne.sgi.com> References: <20030619150026.GA576@teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030619150026.GA576@teaser.fr>; from amajorel@teaser.fr on Thu, Jun 19, 2003 at 05:00:26PM +0200 X-archive-position: 4415 X-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 On Thu, Jun 19, 2003 at 05:00:26PM +0200, Andre Majorel wrote: > What's the wisdom on building a kernel with ACL support for both > ext2/ext3 and XFS ? I tried applying patches in this order : > > linux-2.4.20.tar.bz2 > ea-2.4.20-0.8.58.diff.gz > acl-2.4.20-0.8.57.diff.gz > nfsacl-2.4.20-0.8.59.diff.gz > xfs-2.4.20-split-only.bz2 > xfs-2.4.20-split-quota32.bz2 > xfs-2.4.20-split-kernel.bz2 > xfs-2.4.20-split-misc.bz2 > xfs-2.4.20-split-acl.bz2 > > It goes fine modulo a bunch of "(offset N lines)" messages but as > soon as I reach xfs-2.4.20-split-acl.bz2, problems appear > ("Reversed (or previously applied) patch detected! Assume -R?"). The spilt ACL patch should not be needed if you have already applied Andreas' ACL patches - IIRC, this contains just the VFS changes to get ACLs functional (which is common between both patch sets). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jun 19 13:57:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 13:58:14 -0700 (PDT) Received: from mail1.arkeia.com (knox-gw.knox-software.easynet.fr [212.180.90.105]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5JKvo2x011282 for ; Thu, 19 Jun 2003 13:57:52 -0700 Received: from vulcain.knox.com (vulcain.knox.com [192.168.7.145]) by mail1.arkeia.com (Postfix) with ESMTP id 5EDA71A1B9; Thu, 19 Jun 2003 22:57:44 +0200 (CEST) Received: from aym by vulcain.knox.com with local (Exim 3.36 #1 (Debian)) id 19T6TZ-0000fL-00; Thu, 19 Jun 2003 22:57:45 +0200 Date: Thu, 19 Jun 2003 22:57:45 +0200 From: Andre Majorel To: Nathan Scott Cc: linux-xfs@oss.sgi.com Subject: Re: ACLs on both ext2/ext3 and XFS Message-ID: <20030619205745.GC576@teaser.fr> References: <20030619150026.GA576@teaser.fr> <20030620063824.A8301@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030620063824.A8301@wobbly.melbourne.sgi.com> User-Agent: Mutt/1.5.3i X-archive-position: 4416 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: amajorel@teaser.fr Precedence: bulk X-list: linux-xfs On 2003-06-20 06:38 +1000, Nathan Scott wrote: > On Thu, Jun 19, 2003 at 05:00:26PM +0200, Andre Majorel wrote: > > What's the wisdom on building a kernel with ACL support for both > > ext2/ext3 and XFS ? I tried applying patches in this order : > > > > linux-2.4.20.tar.bz2 > > ea-2.4.20-0.8.58.diff.gz > > acl-2.4.20-0.8.57.diff.gz > > nfsacl-2.4.20-0.8.59.diff.gz > > xfs-2.4.20-split-only.bz2 > > xfs-2.4.20-split-quota32.bz2 > > xfs-2.4.20-split-kernel.bz2 > > xfs-2.4.20-split-misc.bz2 > > xfs-2.4.20-split-acl.bz2 > > > > It goes fine modulo a bunch of "(offset N lines)" messages but as > > soon as I reach xfs-2.4.20-split-acl.bz2, problems appear > > ("Reversed (or previously applied) patch detected! Assume -R?"). > > The spilt ACL patch should not be needed if you have already > applied Andreas' ACL patches - IIRC, this contains just the > VFS changes to get ACLs functional (which is common between > both patch sets). Actually, it would seem that it contains things not in Andrea's patches. It creates include/linux/posix_acl_xattr.h and adds a few bits here and there. The following worked for me : tar -xjvf linux-2.4.20.tar.bz2 cd linux-2.4.20 zcat ../ea-2.4.20-0.8.58.diff.gz | patch -p1 zcat ../acl-2.4.20-0.8.57.diff.gz | patch -p1 zcat ../nfsacl-2.4.20-0.8.59.diff.gz | patch -p1 bzcat ../xfs-2.4.20-split-only.bz2 | patch -p1 bzcat ../xfs-2.4.20-split-quota32.bz2 | patch -p1 bzcat ../xfs-2.4.20-split-kernel.bz2 | patch -p1 bzcat ../xfs-2.4.20-split-misc.bz2 | patch -p1 # -N is required -- there's overlap between Grünbacher's and SGI's diffs bzcat ../xfs-2.4.20-split-acl.bz2 | patch -p1 -N bzcat ../xfs-2.4.20-split-dmapi.bz2 | patch -p1 Thank you. -- André Majorel http://www.teaser.fr/~amajorel/ From owner-linux-xfs@oss.sgi.com Thu Jun 19 16:52:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 16:52:46 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5JNqN2x014941 for ; Thu, 19 Jun 2003 16:52:23 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5JNqNIF014940 for linux-xfs@oss.sgi.com; Thu, 19 Jun 2003 16:52:23 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5JNqI31014925 for ; Thu, 19 Jun 2003 16:52:19 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5JN6XTE014732; Thu, 19 Jun 2003 16:06:33 -0700 Date: Thu, 19 Jun 2003 16:06:33 -0700 Message-Id: <200306192306.h5JN6XTE014732@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] New: linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4417 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 Summary: linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. Product: Linux XFS Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: knutjbj@online.no to reproduce use rpm when boot in to system. rpm -q kernel rpmdb: unable to join the environment error: db4 error(11) from dbenv->open: Resource temporarily unavailable error: cannot open Packages index using db3 - Resource temporarily unavailable (11) error: cannot open Packages database in /var/lib/rpm package kernel is not installed execve("/bin/rpm", ["rpm", "-q", "kernel"], [/* 34 vars */]) = 0 uname({sys="Linux", node="knut", ...}) = 0 brk(0) = 0x806777c old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40016000 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/tls/i686/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/tls/i686/mmx", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/tls/i686/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/tls/i686", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/tls/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/tls/mmx", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/tls/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/tls", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/i686/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/i686/mmx", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/i686/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/i686", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib/mmx", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("/opt/adabas/lib/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) stat64("/opt/adabas/lib", 0xbfffd0d0) = -1 ENOENT (No such file or directory) open("tls/i686/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("tls/i686/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("tls/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("tls/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("i686/mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("i686/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("mmx/librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("librpm-4.2.so", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat64(3, {st_mode=S_IFREG|0644, st_size=131448, ...}) = 0 old_mmap(NULL, 131448, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40017000 workaround to rpm to work export LD_KERNEL_ASSUME=2.2.5 ------- 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 Jun 19 18:59:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 18:59:19 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5K1x52x016512 for ; Thu, 19 Jun 2003 18:59:05 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5K1x5QQ016511 for linux-xfs@oss.sgi.com; Thu, 19 Jun 2003 18:59:05 -0700 Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5K1x32x016499; Thu, 19 Jun 2003 18:59: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.2/linux-outbound_gateway-1.2) with ESMTP id h5K2FpmO002719; Thu, 19 Jun 2003 21:15:51 -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 h5K1IPqX5465704; Thu, 19 Jun 2003 20:18: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 h5K1IPYl12629261; Thu, 19 Jun 2003 20:18:25 -0500 (CDT) Date: Thu, 19 Jun 2003 20:18:25 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: bugzilla-daemon@oss.sgi.com cc: xfs-master@oss.sgi.com Subject: Re: [Bug 252] New: linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. In-Reply-To: <200306192306.h5JN6XTE014732@oss.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4418 X-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 Nice catch, we just found this. Anyway, it seems to be related to O_DIRECT + nptl - patch1300 in the srpm disables O_DIRECT for all filesystems. We removed this patch and added one that only disables it for the security-vulnerable filesystems (not xfs). if this patch is added back in to the mix, rpm is fine again. Still confused, will investigate. -Eric From owner-linux-xfs@oss.sgi.com Thu Jun 19 23:52:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 23:52:36 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5K6qL2x020729 for ; Thu, 19 Jun 2003 23:52:21 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5K6qLZK020728 for linux-xfs@oss.sgi.com; Thu, 19 Jun 2003 23:52:21 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5K6qJ35020700 for ; Thu, 19 Jun 2003 23:52:20 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5K6lxWu020660; Thu, 19 Jun 2003 23:47:59 -0700 Date: Thu, 19 Jun 2003 23:47:59 -0700 Message-Id: <200306200647.h5K6lxWu020660@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4419 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From knutjbj@online.no 2003-19-06 23:47 PDT ------- I belive this to be a bug in rpm see https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=88273. ------- 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 Jun 19 23:52:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Jun 2003 23:52:36 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5K6qL2x020730 for ; Thu, 19 Jun 2003 23:52:21 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5K6qLtL020727 for linux-xfs@oss.sgi.com; Thu, 19 Jun 2003 23:52:21 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5K6qJ33020700 for ; Thu, 19 Jun 2003 23:52:20 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5K6hmIA020639; Thu, 19 Jun 2003 23:43:48 -0700 Date: Thu, 19 Jun 2003 23:43:48 -0700 Message-Id: <200306200643.h5K6hmIA020639@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4419 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From knutjbj@online.no 2003-19-06 23:43 PDT ------- This is a problem also in standard Redhat 9 http://www.redhat.com/advice/ask_shadowman.html ------- 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 Jun 20 01:51:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 01:51:56 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5K8pc2x026904 for ; Fri, 20 Jun 2003 01:51:38 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5K8pSE0026635 for ; Fri, 20 Jun 2003 01:51:30 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id h5K8oHV02116; Fri, 20 Jun 2003 18:50:17 +1000 Date: Fri, 20 Jun 2003 18:50:17 +1000 From: Keith Owens Message-Id: <200306200850.h5K8oHV02116@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade XFS to kdb v4.3 X-archive-position: 4420 X-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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Upgrade XFS to kdb v4.3 Date: Fri Jun 20 01:29:35 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/kaos/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:151670a linux/Documentation/kdb/dump.txt - 1.1 linux/init/main.c - 1.71 linux/include/linux/sysctl.h - 1.55 linux/drivers/sbus/char/sunkeymap.c - 1.4 linux/drivers/sbus/char/sunkbd.c - 1.19 linux/drivers/sbus/char/su.c - 1.22 linux/drivers/sbus/char/sab82532.c - 1.25 linux/drivers/char/serial.c - 1.62 linux/arch/i386/kernel/smp.c - 1.43 linux/arch/i386/config.in - 1.75 linux/Documentation/Configure.help - 1.147 linux/Documentation/kdb/kdb_rd.man - 1.7 linux/kdb/kdb_bt.c - 1.17 linux/kdb/modules/kdbm_vm.c - 1.24 linux/include/linux/kdbprivate.h - 1.26 linux/include/linux/kdb.h - 1.32 linux/kdb/kdbmain.c - 1.39 linux/include/asm-i386/kdb.h - 1.17 linux/kdb/kdb_io.c - 1.20 linux/Documentation/kdb/kdb_bp.man - 1.7 linux/Documentation/kdb/kdb_bt.man - 1.12 linux/kdb/ChangeLog - 1.31 linux/arch/i386/kdb/ChangeLog - 1.20 From owner-linux-xfs@oss.sgi.com Fri Jun 20 03:29:35 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 03:29:55 -0700 (PDT) Received: from unicorn.drogon.net (unicorn.drogon.net [195.10.246.4]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KATY2x003798 for ; Fri, 20 Jun 2003 03:29:35 -0700 Received: from localhost (gordon@localhost) by unicorn.drogon.net (8.9.3/8.9.3) with ESMTP id LAA00941 for ; Fri, 20 Jun 2003 11:29:28 +0100 Date: Fri, 20 Jun 2003 11:29:27 +0100 (BST) From: Gordon Henderson To: linux-xfs@oss.sgi.com Subject: XFS, md (raid5) and "switching cache buffer size" Message-ID: Distribution: world Organization: Home for lost Drogons MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4421 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: gordon@drogon.net Precedence: bulk X-list: linux-xfs I've searched all I can, but find no real solution to the problem of the linux raid driver constantly outputting a stream of : Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 4096 --> 512 Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 4096 --> 512 Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 Jun 20 10:15:39 red kernel: raid5: switching cache buffer size, 0 --> 4096 Jun 20 10:15:39 red kernel: raid5: switching cache buffer size, 4096 --> 512 etc. messages when doing stuff with an xfs mounted filesystem. I've tried putting the log on a separate raid1, and on a separate raw ide partition too and I still see these. Sure, I can turn them off, but it doesn't help the performance much. Is there a majike rune to the mkfs.xfs command that I've overlooked? Reading archives, etc. seems to suggest that making the logfile have a 4K block size would fix it, and/or putting it on a separate device, but from what I've already tried, it would seem to suggest that it already has a 4K block size anyway. Last one I tried was: # mkfs.xfs -f -b size=4096 -l logdev=/dev/hdm5,version=2 /dev/md5 That puts the logfile on a separate partition on the hd device, another partition on that drive is part of the raid5 array, but I don't think that would affect it (should it?) Obviously I'd ideally like the logfile to be on a mirror or raid partition, but I thought I'd try to simplest solution to try to get to the bottom of this. meta-data=/dev/md5 isize=256 agcount=38, agsize=1048568 blks data = bsize=4096 blocks=39688448, imaxpct=25 = sunit=8 swidth=32 blks, unwritten=0 naming =version 2 bsize=4096 log =/dev/hdm5 bsize=4096 blocks=8024, version=2 = sunit=8 blks realtime =none extsz=131072 blocks=0, rtextents=0 # mount -ologdev=/dev/hdm5 /dev/md5 /mnt The system is Linux red 2.4.21-ac1 #3 SMP Wed Jun 18 20:31:28 BST 2003 i686 unknown with xfsprogs-2.3.5 Any clues would be appreciated, even if it's just to comment out the printk in the raid5 code - performance isn't a real issue, but being up and runinng immediately rather than waiting an hour for an ext2 fsck (this box will have 4 x 150Gb partitions) is an issue should it ever crash. Gordon From owner-linux-xfs@oss.sgi.com Fri Jun 20 03:48:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 03:48:38 -0700 (PDT) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KAmU2x006614 for ; Fri, 20 Jun 2003 03:48:33 -0700 Received: from auto-nb1.xs4all.nl (coltex.xs4all.nl [213.84.127.28]) by smtpzilla1.xs4all.nl (8.12.9/8.12.9) with ESMTP id h5KAmSRY052061; Fri, 20 Jun 2003 12:48:28 +0200 (CEST) Message-Id: <4.3.2.7.2.20030620124626.03c5b760@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 20 Jun 2003 12:48:27 +0200 To: Gordon Henderson , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: XFS, md (raid5) and "switching cache buffer size" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4422 X-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 At 11:29 20-6-2003 +0100, Gordon Henderson wrote: >I've searched all I can, but find no real solution to the problem of the >linux raid driver constantly outputting a stream of : > >Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 >Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 4096 --> 512 >Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 >Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 4096 --> 512 >Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 >Jun 20 10:15:39 red kernel: raid5: switching cache buffer size, 0 --> 4096 >Jun 20 10:15:39 red kernel: raid5: switching cache buffer size, 4096 --> 512 The message is harmless. You can safely ignore it or disable it in the source. It was originally there to see how many times there would be a less then 4k write thus resulting in a switching buffer size. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Fri Jun 20 10:35:37 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 10:35:55 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KHZa2x031185 for ; Fri, 20 Jun 2003 10:35:37 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5KHqRmO006432 for ; Fri, 20 Jun 2003 12:52:27 -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 h5KHZSqX5557068; Fri, 20 Jun 2003 12:35:28 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5KHZSRn128180759; Fri, 20 Jun 2003 12:35:28 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5KHZSY27003; Fri, 20 Jun 2003 12:35:28 -0500 Subject: Re: XFS, md (raid5) and "switching cache buffer size" From: Steve Lord To: Gordon Henderson Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056130527.26411.102.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 20 Jun 2003 12:35:28 -0500 X-archive-position: 4423 X-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 On Fri, 2003-06-20 at 05:29, Gordon Henderson wrote: > I've searched all I can, but find no real solution to the problem of the > linux raid driver constantly outputting a stream of : > > Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 > Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 4096 --> 512 > Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 > Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 4096 --> 512 > Jun 20 10:15:38 red kernel: raid5: switching cache buffer size, 512 --> 4096 > Jun 20 10:15:39 red kernel: raid5: switching cache buffer size, 0 --> 4096 > Jun 20 10:15:39 red kernel: raid5: switching cache buffer size, 4096 --> 512 > > etc. messages when doing stuff with an xfs mounted filesystem. I've tried > putting the log on a separate raid1, and on a separate raw ide partition > too and I still see these. Sure, I can turn them off, but it doesn't help > the performance much. Is there a majike rune to the mkfs.xfs command that > I've overlooked? > > Reading archives, etc. seems to suggest that making the logfile have a 4K > block size would fix it, and/or putting it on a separate device, but from > what I've already tried, it would seem to suggest that it already has a 4K > block size anyway. > > Last one I tried was: > > # mkfs.xfs -f -b size=4096 -l logdev=/dev/hdm5,version=2 /dev/md5 > > That puts the logfile on a separate partition on the hd device, another > partition on that drive is part of the raid5 array, but I don't think that > would affect it (should it?) > > Obviously I'd ideally like the logfile to be on a mirror or raid > partition, but I thought I'd try to simplest solution to try to get to the > bottom of this. > > meta-data=/dev/md5 isize=256 agcount=38, agsize=1048568 > blks > data = bsize=4096 blocks=39688448, imaxpct=25 > = sunit=8 swidth=32 blks, unwritten=0 > naming =version 2 bsize=4096 > log =/dev/hdm5 bsize=4096 blocks=8024, version=2 > = sunit=8 blks > realtime =none extsz=131072 blocks=0, rtextents=0 > > # mount -ologdev=/dev/hdm5 /dev/md5 /mnt > > The system is > > Linux red 2.4.21-ac1 #3 SMP Wed Jun 18 20:31:28 BST 2003 i686 unknown > > with xfsprogs-2.3.5 > > Any clues would be appreciated, even if it's just to comment out the > printk in the raid5 code - performance isn't a real issue, but being up > and runinng immediately rather than waiting an hour for an ext2 fsck (this > box will have 4 x 150Gb partitions) is an issue should it ever crash. > > Gordon With the most recent xfs user space (xfsprogs-2.5.0-0) and a kernel from cvs, try this and see if it helps: mkfs -t xfs -f -s size=4096 -l size=16384b /dev/mdxxxx This will make the xfs sector size 4K and change the on disk layout, you get a version 2 log aligned on 4K boundaries too. I have not tried it, but this could make your problem go away. Note that large sector support is brand new, so could probably do with some exposure in the wild. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Fri Jun 20 10:50:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 10:50:38 -0700 (PDT) Received: from hotmail.com (sea2-f60.sea2.hotmail.com [207.68.165.60]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KHoV2x031753 for ; Fri, 20 Jun 2003 10:50:32 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 20 Jun 2003 10:50:26 -0700 Received: from 208.244.233.175 by sea2fd.sea2.hotmail.msn.com with HTTP; Fri, 20 Jun 2003 17:50:26 GMT X-Originating-IP: [208.244.233.175] X-Originating-Email: [rgsmith72@hotmail.com] From: "Rick Smith" To: linux-xfs@oss.sgi.com Subject: guaranteed increasing extent allocation Date: Fri, 20 Jun 2003 10:50:26 -0700 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 20 Jun 2003 17:50:26.0722 (UTC) FILETIME=[6E80C820:01C33754] X-archive-position: 4424 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rgsmith72@hotmail.com Precedence: bulk X-list: linux-xfs Hello, Is there a way to guarantee that if you reserve space for a series of files at once using the XFS_RESVSP64 ioctl (in say, a for-loop before I/O takes place) that the extents for each respective allocation will be greater than the previous file's extents for the current reserve set? In other words, we are looking to maintain high performance for files read/written in sequence by laying them out in the filesystem in order to minimize disk head seeks. With a fresh XFS filesystem, we seem to get consecutive extent allocation, but as the filesystem ages and files are created and deleted, it seems less and less likely to be able to reserve consecutive files. Can this be done currently or would a new ioctl be necessary to reserve files relative to each other be the ticket? I have included a couple examples of what we are seeing below. Any help appreciated. Rick Smith The following shows 4 files reserved with XFS_RESVSP64 in a for-loop with each consecutive file reserved in-front (with a lower starting extent) than the previous one (xfs_bmap-v): test.20.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1417438960..1417449759 168 (8154160..8164959) 10800 test.21.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1417428160..1417438959 168 (8143360..8154159) 10800 test.22.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1417417360..1417428159 168 (8132560..8143359) 10800 test.23.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1417406560..1417417359 168 (8121760..8132559) 10800 The following shows an alternating reserve location for files reserved in order: test.6.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1405059864..1405070663 167 (4163664..4174463) 10800 test.7.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1404984224..1404995023 167 (4088024..4098823) 10800 test.8.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1405070664..1405081463 167 (4174464..4185263) 10800 test.9.data: EXT: FILE-OFFSET BLOCK-RANGE AG AG-OFFSET TOTAL 0: [0..10799]: 1404973424..1404984223 167 (4077224..4088023) 10800 _________________________________________________________________ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail From owner-linux-xfs@oss.sgi.com Fri Jun 20 12:05:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 12:06:01 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KJ5j2x032746 for ; Fri, 20 Jun 2003 12:05: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.2/linux-outbound_gateway-1.2) with ESMTP id h5KJ5dE0003967 for ; Fri, 20 Jun 2003 12:05:40 -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 h5KJ5dqX5575778 for ; Fri, 20 Jun 2003 14:05:39 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5KJ5dRn106243576 for ; Fri, 20 Jun 2003 14:05:39 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5KJ5cE29984; Fri, 20 Jun 2003 14:05:38 -0500 Message-Id: <200306201905.h5KJ5cE29984@jen.americas.sgi.com> Date: Fri, 20 Jun 2003 14:05:38 -0500 Subject: TAKE - fix initializer for sync interval To: linux-xfs@oss.sgi.com X-archive-position: 4425 X-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 the intializers for the /proc interface to xfs got out of order, and we are syncing 1000 times faster than we are supposed to! Date: Fri Jun 20 12:05:03 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: 2.4.x-xfs:slinx:151712a linux/fs/xfs/linux/xfs_globals.c - 1.49 - reorder initializer constants to fix sync rate From owner-linux-xfs@oss.sgi.com Fri Jun 20 12:53:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 12:53:07 -0700 (PDT) Received: from argo.starforce.com (argo.starforce.com [216.158.58.233]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KJr22x004140 for ; Fri, 20 Jun 2003 12:53:02 -0700 Received: from argo.starforce.com (dwild@localhost [127.0.0.1]) by argo.starforce.com (8.12.9/8.12.9) with ESMTP id h5KJr4SJ027921 for ; Fri, 20 Jun 2003 15:53:04 -0400 Received: from localhost (dwild@localhost) by argo.starforce.com (8.12.9/8.12.9/Submit) with ESMTP id h5KJr3hR027917 for ; Fri, 20 Jun 2003 15:53:03 -0400 X-Authentication-Warning: argo.starforce.com: dwild owned process doing -bs Date: Fri, 20 Jun 2003 15:53:03 -0400 (EDT) From: dwild+xfs@starforce.com X-X-Sender: dwild@argo.starforce.com To: linux-xfs@oss.sgi.com Subject: xfsdump patch for automatic media changes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4426 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dwild+xfs@starforce.com Precedence: bulk X-list: linux-xfs I'm new here, so if people aren't supposed to post patches to the list just let me know. I needed the capability for xfsdump to change a tape in a jukebox when the tape ran out, and the -c flag just didn't work right. So, this patch alters the -c flag to work when the program is running in the background with the -F flag enabled. I use it to call a perl script that does backup accounting/tape changes/etc then passes control back to xfsdump. It hasn't broken anything yet =) -dwild ----- diff -ur xfsdump-2.2.6/dump/content.c xfsdump-2.2.6.X/dump/content.c --- xfsdump-2.2.6/dump/content.c 2002-12-30 18:09:33.000000000 -0500 +++ xfsdump-2.2.6.1/dump/content.c 2003-06-20 14:39:34.000000000 -0400 @@ -6095,7 +6095,8 @@ changemedia: /* if the drive does not support media change, quit. */ - if ( ! ( dcaps & DRIVE_CAP_REMOVABLE )) { + + if ( ! ( dcaps & DRIVE_CAP_REMOVABLE ) && (media_change_alert_program == NULL)) { return RV_ERROR; } @@ -6113,7 +6114,7 @@ /* if dialogs not allowed, we are done. */ - if ( ! dlog_allowed( )) { + if ( ! dlog_allowed( ) && (media_change_alert_program == NULL)) { return RV_QUIT; /* this return value will cause approp. msg */ } @@ -6125,7 +6126,7 @@ /* if media change prompt declined or times out, * we are done */ - if ( drivecnt > 1 && ! stdoutpiped ) { + if ( drivecnt > 1 && ! stdoutpiped && dlog_allowed( )) { ix_t thrdix = drivep->d_index; ASSERT( sistr ); mlog( MLOG_NORMAL | MLOG_NOTE | MLOG_MEDIA, _( @@ -6142,7 +6143,11 @@ } ok = BOOL_TRUE; } else { - ok = Media_prompt_change( drivep ); + if (media_change_alert_program != NULL) { + ok = BOOL_TRUE; + } else { + ok = Media_prompt_change( drivep ); + } } if ( intr_allowed && cldmgr_stop_requested( )) { return RV_INTR; From owner-linux-xfs@oss.sgi.com Fri Jun 20 13:52:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 13:52:41 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5KKqP2x009273 for ; Fri, 20 Jun 2003 13:52:25 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5KKqPep009272 for linux-xfs@oss.sgi.com; Fri, 20 Jun 2003 13:52:25 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5KKqN31009258 for ; Fri, 20 Jun 2003 13:52:23 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5KJrESH004202; Fri, 20 Jun 2003 12:53:14 -0700 Date: Fri, 20 Jun 2003 12:53:14 -0700 Message-Id: <200306201953.h5KJrESH004202@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4427 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Additional Comments From sandeen@sgi.com 2003-20-06 12:53 PDT ------- This seems to have something to do with O_DIRECT not getting turned off for ext3. in the kernel you tested, we removed the global O_DIRECT disable, and disabled it at the filesystem level - but only for filesystems which can even -DO- O_DIRECT. Since ext3 can't do O_DIRECT, I did not disable the flag in ext3_open_file(). Adding this line: filp->f_flags &= ~O_DIRECT; to the top of ext3_open_file() fixes it for a machine where your rpm database is on ext3. Knut - What filesystem type is on your root fs? -Eric ------- 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 Jun 20 16:49:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 16:50:05 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5KNno2x011873 for ; Fri, 20 Jun 2003 16:49:50 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5KKFDE0021347 for ; Fri, 20 Jun 2003 13:15: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 h5KKFCqX5579864; Fri, 20 Jun 2003 15:15:13 -0500 (CDT) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5KKFCRn128798199; Fri, 20 Jun 2003 15:15:12 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id h5KKFC831232; Fri, 20 Jun 2003 15:15:12 -0500 Subject: Re: xfsdump patch for automatic media changes From: Steve Lord To: dwild+xfs@starforce.com Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1056140111.26408.269.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 20 Jun 2003 15:15:12 -0500 X-archive-position: 4428 X-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 On Fri, 2003-06-20 at 14:53, dwild+xfs@starforce.com wrote: > I'm new here, so if people aren't supposed to post patches to the list > just let me know. > > I needed the capability for xfsdump to change a tape in a jukebox when the > tape ran out, and the -c flag just didn't work right. So, this patch > alters the -c flag to work when the program is running in the background > with the -F flag enabled. > > I use it to call a perl script that does backup accounting/tape > changes/etc then passes control back to xfsdump. It hasn't broken > anything yet =) > > -dwild > Thanks, patches are always welcome, it just sometimes takes us a little while to turn them around. Thanks, Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Fri Jun 20 19:41:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 19:42:08 -0700 (PDT) Received: from pilot21.cl.msu.edu (pilot21.cl.msu.edu [35.9.5.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5L2fs2x014199 for ; Fri, 20 Jun 2003 19:41:55 -0700 Received: from jasonscomp (gabrie16-4.user.msu.edu [35.11.65.109]) by pilot21.cl.msu.edu (8.11.6p2/8.10.2) with ESMTP id h5L2fqF45658 for ; Fri, 20 Jun 2003 22:41:52 -0400 From: "Jason Gabriele" To: Subject: redhat 9 xfs install problems Date: Fri, 20 Jun 2003 22:42:13 -0400 Message-ID: <000601c3379e$b89c5740$6501a8c0@jasonscomp> 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: 4429 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: gabrie16@msu.edu Precedence: bulk X-list: linux-xfs Hi. I am having difficulties installing redhat 9 on xfs using the sgi installer (1.2). everything installs fine but after it reboots the bios errors saying it cannot start the os. This is with using the entire drive for linux and using the automatic partitioning and default GRUB settings. Ive tried using LILO but then it just hangs. Has anyone had this problem? Im not exactly sure how bios read information off harddrives but is there some way my board isn't fully compatible with XFS? I have the latest version of Epoxs bios which they just released a week ago. Thanks Jason System: Athlon 1700+ Epox 8RDA+ 256mb ram 160GB Maxtor Geforce2 GTS From owner-linux-xfs@oss.sgi.com Fri Jun 20 19:46:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 19:46:18 -0700 (PDT) Received: from mail.vasoftware.com (mail@mail.vasoftware.com [198.186.202.175]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5L2kC2x014569 for ; Fri, 20 Jun 2003 19:46:13 -0700 Received: from adsl-67-123-173-22.dsl.sntc01.pacbell.net ([67.123.173.22] helo=linux-sxs.org) by mail.vasoftware.com with asmtp (Cipher TLSv1:RC4-MD5:128) (Exim 3.31-VA-mm2 #1 (Debian)) id 19TYOH-0005JB-00 by VAauthid with fixed_plain; Fri, 20 Jun 2003 19:46:10 -0700 Message-ID: <3EF3C6E6.1010002@linux-sxs.org> Date: Fri, 20 Jun 2003 19:45:58 -0700 From: "Net Llama!" Organization: HAL-III User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Gabriele CC: linux-xfs@oss.sgi.com Subject: Re: redhat 9 xfs install problems References: <000601c3379e$b89c5740$6501a8c0@jasonscomp> In-Reply-To: <000601c3379e$b89c5740$6501a8c0@jasonscomp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4430 X-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 On 06/20/03 19:42, Jason Gabriele wrote: > Hi. I am having difficulties installing redhat 9 on xfs using the sgi > installer (1.2). everything installs fine but after it reboots the bios > errors saying it cannot start the os. This is with using the entire > drive for linux and using the automatic partitioning and default GRUB > settings. Ive tried using LILO but then it just hangs. Has anyone had > this problem? Im not exactly sure how bios read information off > harddrives but is there some way my board isn't fully compatible with > XFS? I have the latest version of Epoxs bios which they just released a > week ago. To the best of my knowledge grub will not work with the RH XFS installs. What do you mean by LILO hanging? Do you get different results if you attempt a normal non-xfs RH9 installation? Have you ever installed Linux on this box before? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo: http://netllama.ipfox.com 7:40pm up 6 days, 23 min, 1 user, load average: 0.00, 0.11, 0.14 From owner-linux-xfs@oss.sgi.com Fri Jun 20 23:52:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Jun 2003 23:52:39 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5L6qQ2x020172 for ; Fri, 20 Jun 2003 23:52:26 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5L6qQx6020171 for linux-xfs@oss.sgi.com; Fri, 20 Jun 2003 23:52:26 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5L6qO31020157 for ; Fri, 20 Jun 2003 23:52:25 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5L6k0tH020112; Fri, 20 Jun 2003 23:46:00 -0700 Date: Fri, 20 Jun 2003 23:46:00 -0700 Message-Id: <200306210646.h5L6k0tH020112@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4431 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From knutjbj@online.no 2003-20-06 23:45 PDT ------- MY rpm database is loacated on a root XFS partion. ------- 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 Sat Jun 21 07:52:28 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Jun 2003 07:52:44 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5LEqS2x027800 for ; Sat, 21 Jun 2003 07:52:28 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5LEqScG027799 for linux-xfs@oss.sgi.com; Sat, 21 Jun 2003 07:52:28 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5LEqQ31027785 for ; Sat, 21 Jun 2003 07:52:26 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5LEB4EW026960; Sat, 21 Jun 2003 07:11:04 -0700 Date: Sat, 21 Jun 2003 07:11:04 -0700 Message-Id: <200306211411.h5LEB4EW026960@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4432 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From knutjbj@online.no 2003-21-06 07:11 PDT ------- I got rpm to work by upgrading to latest rpm from rawhide along with a new db4 and compat-db4. A reboot and rpm --rebuilddb fix it. ------- 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 Sat Jun 21 08:52:29 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Jun 2003 08:52:42 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5LFqT2x028592 for ; Sat, 21 Jun 2003 08:52:29 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5LFqTgG028591 for linux-xfs@oss.sgi.com; Sat, 21 Jun 2003 08:52:29 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5LFqQ31028577 for ; Sat, 21 Jun 2003 08:52:26 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5LF62oG028375; Sat, 21 Jun 2003 08:06:03 -0700 Date: Sat, 21 Jun 2003 08:06:03 -0700 Message-Id: <200306211506.h5LF62oG028375@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4433 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From sandeen@sgi.com 2003-21-06 08:06 PDT ------- Ok, I've verified the problem on xfs root as well. :( It looks like having O_DIRECT set on the filp causes problems regardless of the underlying filesystem - _even_ if that filesystem doesn't support O_DIRECT! -Eric ------- 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 Sat Jun 21 16:52:30 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Jun 2003 16:52:51 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5LNqU2x032269 for ; Sat, 21 Jun 2003 16:52:30 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5LNqTlQ032268 for linux-xfs@oss.sgi.com; Sat, 21 Jun 2003 16:52:29 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5LNqS31032254 for ; Sat, 21 Jun 2003 16:52:28 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5LNBbW8032055; Sat, 21 Jun 2003 16:11:37 -0700 Date: Sat, 21 Jun 2003 16:11:37 -0700 Message-Id: <200306212311.h5LNBbW8032055@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 253] New: xfs_repair saegfaults while doing insecure memory-operations X-Bugzilla-Reason: AssignedTo X-archive-position: 4434 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=253 Summary: xfs_repair saegfaults while doing insecure memory- operations Product: Linux XFS Version: Current Platform: IA32 OS/Version: Linux Status: NEW Severity: major Priority: Medium Component: xfsprogs AssignedTo: xfs-master@oss.sgi.com ReportedBy: sgi@debian.franken.de Hi I think I found a bug in xfs_repair. It saegfaults when I run it on a filesystem which is a little bit corrupt. After I ran it with efence, I got these backtraces. I think it cannot handle this block-out-of-range condition correctly. I have attached all important informations. Here is the output of xfs_check: dir 128 block 0 entry /ost+found bad inode number -72057594037927937 dir 128 block 0 extra leaf entry 21aa60c 28 dir ino 128 missing leaf entry for 821aa62d/28 block 9/65529 out of range block 9/65530 out of range block 9/65531 out of range block 9/65532 out of range block 9/65533 out of range block 9/65534 out of range block 9/65535 out of range block 9/65536 out of range block 9/65537 out of range block 9/65538 out of range block 9/65539 out of range block 9/65540 out of range block 9/65541 out of range block 9/65542 out of range block 9/65543 out of range block 9/65544 out of range block 9/65545 out of range block 9/65546 out of range block 9/65547 out of range block 9/65548 out of range blocks 9/65529..65548 claimed by block 9/338 block 9/65529 out of range block 9/65530 out of range block 9/65531 out of range block 9/65532 out of range block 9/65533 out of range block 9/65534 out of range block 9/65535 out of range block 9/65536 out of range ^^^^^ This is the block where gdb tells me that xfs_repair saegfaults block 9/65537 out of range block 9/65538 out of range block 9/65539 out of range block 9/65540 out of range block 9/65541 out of range block 9/65542 out of range block 9/65543 out of range block 9/65544 out of range block 9/65545 out of range block 9/65546 out of range block 9/65547 out of range block 9/65548 out of range blocks 9/65529..65548 claimed by block 9/902 block 10/4200613472 out of range blocks 10/4200613472..4200613472 claimed by block 10/0 block 10/2742227945 out of range blocks 10/2742227945..2742227945 claimed by block 10/0 block 10/1030081898 out of range blocks 10/1030081898..1030081898 claimed by block 10/0 block 10/1266619198 out of range blocks 10/1266619198..1266619198 claimed by block 10/0 link count mismatch for inode 3594 (name ?), nlink 1, counted 3 link count mismatch for inode 59683 (name ?), nlink 2, counted 1 block 9/65529 type unknown not expected block 9/65530 type unknown not expected block 9/65531 type unknown not expected block 9/65532 type unknown not expected block 9/65533 type unknown not expected block 9/65534 type unknown not expected link count mismatch for inode 9446615 (name ?), nlink 2, counted 1 block 10/4 type unknown not expected block 10/5 type unknown not expected block 10/6 type unknown not expected block 10/7 type unknown not expected sb_ifree 57790, counted 57791 Here is the output of xfs_repair: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Segmentation fault Here is a gdb backtrace on the core: (gdb) bt #0 0x0807918f in scanfunc_bno (ablock=0x405bd000, level=0, bno=338, agno=9, +suspect=0, isroot=1) at scan.c:569 #1 0x0807760a in scan_sbtree (root=338, nlevels=1, agno=9, suspect=0, +func=0x8078d05 , isroot=1) at scan.c:84 #2 0x0807b401 in scan_ag (agno=9) at swab.h:125 #3 0x0806570f in phase2 (mp=0xbfffdc70) at phase2.c:149 #4 0x0807c9e9 in main (argc=2, argv=0xbfffdc70) at xfs_repair.c:506 the blocknumber is at 65536 and the ag-number is at 9. Everything is done with efence. ------- 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 Sat Jun 21 19:11:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Jun 2003 19:11:49 -0700 (PDT) Received: from mail.apex-internet.com (98.mucb.detr.sfldmibv.dsl.att.net [12.101.210.98]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5M2BT2x002483 for ; Sat, 21 Jun 2003 19:11:31 -0700 Received: from apex-internet.com (WWW1.APEX-INTERNET.COM [192.168.2.15]) by mail.apex-internet.com (8.11.6/8.11.6) with SMTP id h5M2BNZ23232; Sat, 21 Jun 2003 22:11:23 -0400 Message-Id: <200306220211.h5M2BNZ23232@mail.apex-internet.com> Date: Sun, 22 Jun 2003 02:11:23 -0000 To: Subject: upgrading to 2.4.19 kernel From: "Chris Szilagyi" X-Mailer: TWIG 2.7.4 X-archive-position: 4435 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: chris@apex-internet.com Precedence: bulk X-list: linux-xfs Hello, I've got a couple systems running Red Hat 7.1 with XFS 1.0.1 (using the pre-built kernel supplied by SGI, 2.4.3_SGI_XFS_1.0.1). I would like to upgrade the kernel to a more recent version to solve some problems, like to 2.4.19. Will I break anything by compiling a new 2.4.19 kernel from the source and applying the patches for 2.4.19 for XFS?? If this would work, can somebody tell me which patches to use on 2.4.19 (i.e. which ones are known to be the most stable)??? Thanks in advance... -- Chris From owner-linux-xfs@oss.sgi.com Sat Jun 21 19:35:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Jun 2003 19:35:23 -0700 (PDT) Received: from mail.apex-internet.com (98.mucb.detr.sfldmibv.dsl.att.net [12.101.210.98]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5M2Z32x003035 for ; Sat, 21 Jun 2003 19:35:04 -0700 Received: from apex-internet.com (WWW1.APEX-INTERNET.COM [192.168.2.15]) by mail.apex-internet.com (8.11.6/8.11.6) with SMTP id h5M2YwZ23249; Sat, 21 Jun 2003 22:34:58 -0400 Message-Id: <200306220234.h5M2YwZ23249@mail.apex-internet.com> Date: Sun, 22 Jun 2003 02:34:58 -0000 To: Subject: upgrading XFS in kernel... From: "Chris Szilagyi" X-Mailer: TWIG 2.7.4 X-archive-position: 4436 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: chris@apex-internet.com Precedence: bulk X-list: linux-xfs Hello, One more question to clarify my previous inquiry. Since I'm currently running the stock SGI XFS 1.0.1 kernel, and all of the utils for Red Hat 7.1 with XFS 1.0.1, will upgrading the kernel with support for say XFS 1.2 break the utils that were used for XFS 1.0.1? Thanks a lot for the help. -- Chris From owner-linux-xfs@oss.sgi.com Sun Jun 22 05:52:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 05:52:50 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5MCqX2x015677 for ; Sun, 22 Jun 2003 05:52:33 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5MCqXCe015676 for linux-xfs@oss.sgi.com; Sun, 22 Jun 2003 05:52:33 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5MCqU31015662 for ; Sun, 22 Jun 2003 05:52:30 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5MBuvw2015334; Sun, 22 Jun 2003 04:56:57 -0700 Date: Sun, 22 Jun 2003 04:56:57 -0700 Message-Id: <200306221156.h5MBuvw2015334@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4437 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From Axel.Thimm@physik.fu-berlin.de 2003-22-06 04:56 PDT ------- Maybe this is simply a (known) rpm bug? Did you try with the latest rpm binaries (no errata yet, get them from ftp://ftp.rpm.org/pub/rpm/)? O_DIRECT was disabled there, I think. Have a look at the following bug reports, they may be usefull: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=90809 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=89662 ------- 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 Sun Jun 22 09:52:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 09:52:48 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5MGqW2x018124 for ; Sun, 22 Jun 2003 09:52:32 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5MGqWLQ018123 for linux-xfs@oss.sgi.com; Sun, 22 Jun 2003 09:52:32 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5MGqV31018109 for ; Sun, 22 Jun 2003 09:52:31 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5MGo1WV018079; Sun, 22 Jun 2003 09:50:01 -0700 Date: Sun, 22 Jun 2003 09:50:01 -0700 Message-Id: <200306221650.h5MGo1WV018079@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 252] linux-2.4.20-18.9RH breaks rpm, something to do with nptl add rpm. X-Bugzilla-Reason: AssignedTo X-archive-position: 4438 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=252 ------- Additional Comments From knutjbj@online.no 2003-22-06 09:50 PDT ------- rpm from rawhide has O_DIRECTE disabled also. ------- 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 Sun Jun 22 18:25:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 18:25:52 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5N1PW2x003971 for ; Sun, 22 Jun 2003 18:25:32 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5N1PQE0006551 for ; Sun, 22 Jun 2003 18:25:26 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by nodin.corp.sgi.com (8.12.9/8.11.4/nodin-1.0) with ESMTP id h5N1OO5E4099067 for ; Sun, 22 Jun 2003 18:24:25 -0700 (PDT) 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 h5N1N5JA471831; Mon, 23 Jun 2003 11:23:05 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5N1N5DS471171; Mon, 23 Jun 2003 11:23:05 +1000 (EST) Date: Mon, 23 Jun 2003 11:23:05 +1000 (EST) From: Nathan Scott Message-Id: <200306230123.h5N1N5DS471171@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Cc: nathans@sgi.com Subject: TAKE - xfsprogs X-archive-position: 4439 X-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 [ Lets see if _this_ one makes it out to oss, last few haven't :( ] Update the summary section in mkfs.xfs.8, adding -s option Date: Wed Jun 18 19:57:44 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:151554a cmd/xfsprogs/man/man8/mkfs.xfs.8 - 1.18 Fix ordering of values in a print statement, trivial typo Date: Thu Jun 19 20:25:23 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:151663a cmd/xfsprogs/io/pwrite.c - 1.5 Update libdisk driver detection code to work for devices with multiple majors Date: Sun Jun 22 18:22:03 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:151803a cmd/xfsprogs/VERSION - 1.81 cmd/xfsprogs/doc/CHANGES - 1.113 cmd/xfsprogs/libdisk/md.c - 1.13 cmd/xfsprogs/libdisk/drivers.c - 1.13 cmd/xfsprogs/libdisk/xvm.c - 1.9 cmd/xfsprogs/libdisk/lvm.c - 1.11 cmd/xfsprogs/include/volume.h - 1.7 cmd/xfsprogs/debian/changelog - 1.74 cmd/xfsprogs/libdisk/evms.c - 1.4 From owner-linux-xfs@oss.sgi.com Sun Jun 22 18:46:21 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 18:46:34 -0700 (PDT) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5N1kK2x004538 for ; Sun, 22 Jun 2003 18:46:21 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5N23HmO031594 for ; Sun, 22 Jun 2003 21:03:18 -0500 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id h5N1jAt26872; Mon, 23 Jun 2003 11:45:10 +1000 Date: Mon, 23 Jun 2003 11:45:10 +1000 From: Keith Owens Message-Id: <200306230145.h5N1jAt26872@sherman.melbourne.sgi.com> Subject: TAKE - Upgrade XFS to kdb v4.3 -2 X-archive-position: 4440 X-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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Upgrade XFS to kdb v4.3 -2 Date: Sun Jun 22 18:44:17 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/kaos/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:151804a linux/kdb/ChangeLog - 1.32 linux/arch/i386/kdb/ChangeLog - 1.21 From owner-linux-xfs@oss.sgi.com Sun Jun 22 18:49:41 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 18:49:55 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5N1nf2x004988 for ; Sun, 22 Jun 2003 18:49:41 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5N1nZE0013127 for ; Sun, 22 Jun 2003 18:49:35 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by nodin.corp.sgi.com (8.12.9/8.11.4/nodin-1.0) with ESMTP id h5N1mR5E3591365 for ; Sun, 22 Jun 2003 18:48:28 -0700 (PDT) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id h5N1lM126937; Mon, 23 Jun 2003 11:47:22 +1000 Date: Mon, 23 Jun 2003 11:47:22 +1000 From: Keith Owens Message-Id: <200306230147.h5N1lM126937@sherman.melbourne.sgi.com> Subject: TAKE - Remove spurious comment change X-archive-position: 4441 X-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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Remove spurious comment change Date: Sun Jun 22 18:46:38 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/kaos/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:151805a linux/fs/buffer.c - 1.120 From owner-linux-xfs@oss.sgi.com Sun Jun 22 21:28:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 21:28:34 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5N4SJ2x006394 for ; Sun, 22 Jun 2003 21:28:19 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h5N2U6E0024390 for ; Sun, 22 Jun 2003 19:30:08 -0700 Received: from kao1.melbourne.sgi.com (kao1.melbourne.sgi.com [134.14.55.179]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA21961 for ; Mon, 23 Jun 2003 12:28:51 +1000 Received: by kao1.melbourne.sgi.com (Postfix, from userid 16331) id 7E6E4181575; Mon, 23 Jun 2003 12:28:38 +1000 (EST) Received: from kao1.melbourne.sgi.com (localhost [127.0.0.1]) by kao1.melbourne.sgi.com (Postfix) with ESMTP id 6A642102EBE for ; Mon, 23 Jun 2003 12:28:38 +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.21 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jun 2003 12:28:33 +1000 Message-ID: <16842.1056335313@kao1.melbourne.sgi.com> X-archive-position: 4442 X-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 ftp://oss.sgi.com/projects/xfs/download/patches/2.4.21. For some time the XFS group have been producing split patches for XFS, separating the core XFS changes from additional patches such as kdb, xattr, 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.22/README for the terminally impatient :). From owner-linux-xfs@oss.sgi.com Sun Jun 22 23:12:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Jun 2003 23:12:20 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5N6C22x010328 for ; Sun, 22 Jun 2003 23:12:03 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5N6T0mO009924 for ; Mon, 23 Jun 2003 01:29:01 -0500 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id h5N6AsC12643; Mon, 23 Jun 2003 16:10:54 +1000 Date: Mon, 23 Jun 2003 16:10:54 +1000 From: Keith Owens Message-Id: <200306230610.h5N6AsC12643@sherman.melbourne.sgi.com> Subject: TAKE - Tweak i386 kdb bt heuristics X-archive-position: 4443 X-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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs This change is being checked into the XFS tree first, because that group seems to have the most problems with the i386 kdb backtrace. The backtrace heuristics have been tweaked so it now does two passes looking for the next return address. The first pass only considers code that can be validated as branching to the current function. Iff the first pass fails, then do a second pass allowing for code that does branch by register. Such code cannot be validated and must be assumed to be valid, sometimes resulting in false positives. If you still have backtrace problems on i386, capture the output from these kdb commands and send it to kaos@sgi.com. set LINES 2000 bt set KDBDEBUG 0x19 bt Date: Sun Jun 22 23:01:23 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/kaos/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:151810a linux/arch/i386/kdb/kdbasupport.c - 1.27 From owner-linux-xfs@oss.sgi.com Mon Jun 23 04:52:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Jun 2003 04:52:57 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5NBqd2x018614 for ; Mon, 23 Jun 2003 04:52:39 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5NBqdvZ018613 for linux-xfs@oss.sgi.com; Mon, 23 Jun 2003 04:52:39 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5NBqZ31018599 for ; Mon, 23 Jun 2003 04:52:35 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5NBSKtS018132; Mon, 23 Jun 2003 04:28:20 -0700 Date: Mon, 23 Jun 2003 04:28:20 -0700 Message-Id: <200306231128.h5NBSKtS018132@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 250] log recovery hangs after crash X-Bugzilla-Reason: AssignedTo X-archive-position: 4444 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=250 ------- Additional Comments From dizzy@roedu.net 2003-23-06 04:28 PDT ------- It happened again :-/ This time the kernel just crashed (couldnt get a panic message) then on reboot neither 2.4.21-cvs or 2.4.18-4SGI_XFS1.2 couldnt replay the journal. Again, 2.4.9-34SGI_XFS1.1 could. So this seems to me to be 2 issues: - one issue appeared beetween xfs 1.2.0 and current cvs which leaves the log in a "strange" state from which neither current xfs or xfs1.2 can recover (this problem never appeared when running just 2.4.18-4SGI_XFS1.2) - one issue of the log recovery code appeared between xfs1.1 and xfs1.2, couse 2.4.9-34SGI_XFS1.1 can do log recovery when 2.4.18-4SGI_XFS1.2 and current CVS cannot ------- 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 Jun 23 08:52:38 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Jun 2003 08:52:58 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5NFqc2x021539 for ; Mon, 23 Jun 2003 08:52:38 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5NFqbAB021538 for linux-xfs@oss.sgi.com; Mon, 23 Jun 2003 08:52:37 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5NFqa31021524 for ; Mon, 23 Jun 2003 08:52:36 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5NFCRO0021257; Mon, 23 Jun 2003 08:12:27 -0700 Date: Mon, 23 Jun 2003 08:12:27 -0700 Message-Id: <200306231512.h5NFCRO0021257@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 250] log recovery hangs after crash X-Bugzilla-Reason: AssignedTo X-archive-position: 4445 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=250 ------- Additional Comments From sandeen@sgi.com 2003-23-06 08:12 PDT ------- If the whole system hangs, can you get into KDB and type "ps" to find the pid of the mount process, then type "btp " to get the backtrace and see where it's stuck. No need for all of the information, just the list of functions in the backtrace would be a good start. I'm a little confused, you say it is hanging, but you report a shutdown on device dac960(48,9) - is this the same large filesystem? The error ("22" == EINVAL) in the shutdown messages looks like it originates in xfs_dilocate, perhaps you could either remove all of the #ifdef DEBUG/#endif lines in that function, or rebuild xfs with CONFIG_XFS_DEBUG, and that might give us more info. -Eric ------- 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 Jun 23 10:25:46 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Jun 2003 10:26:08 -0700 (PDT) Received: from conure.mail.pas.earthlink.net (conure.mail.pas.earthlink.net [207.217.120.54]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5NHPj2x023579 for ; Mon, 23 Jun 2003 10:25:45 -0700 Received: from [65.102.60.133] (helo=software1.logiplex.internal) by conure.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 19UV4Z-0004zM-00; Mon, 23 Jun 2003 10:25:43 -0700 Subject: Re: redhat 9 xfs install problems From: Cliff Wells To: Jason Gabriele Cc: linux-xfs@oss.sgi.com In-Reply-To: <000601c3379e$b89c5740$6501a8c0@jasonscomp> References: <000601c3379e$b89c5740$6501a8c0@jasonscomp> Content-Type: text/plain Organization: Logiplex Corporation Message-Id: <1056389142.16269.10.camel@software1.logiplex.internal> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 23 Jun 2003 10:25:43 -0700 Content-Transfer-Encoding: 7bit X-archive-position: 4446 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: LogiplexSoftware@earthlink.net Precedence: bulk X-list: linux-xfs On Fri, 2003-06-20 at 19:42, Jason Gabriele wrote: > Hi. I am having difficulties installing redhat 9 on xfs using the sgi > installer (1.2). everything installs fine but after it reboots the bios > errors saying it cannot start the os. This is with using the entire > drive for linux and using the automatic partitioning and default GRUB > settings. Ive tried using LILO but then it just hangs. Has anyone had > this problem? Im not exactly sure how bios read information off > harddrives but is there some way my board isn't fully compatible with > XFS? I have the latest version of Epoxs bios which they just released a > week ago. The way I've done it is to first install using GRUB as the bootloader. Of course the system won't boot when you are finished, but all that is required is the following: 1. *KNOW* which partition is your /boot partition (/dev/hda1, etc) [the following will assume /boot on hda1 and / on hda2] 2. Boot from the XFS CD, at the "boot:" prompt, type "linux rescue" 3. Don't mount any partitions when prompted 4. Once you get a root prompt, mount your root partition and boot partition under /mnt/sysimage (i.e. "mount /dev/hda2 /mnt/sysimage ; mount /dev/hda1 /mnt/sysimage/boot") 5. Type "chroot /mnt/sysimage" 6. Type in "grub" 7. At the grub prompt type the following: root (hd0,0) setup (hd0) quit *** NOTE!!! the above values assume your /boot is on hda1!!! **** Change it accordingly (i.e. root(hd0,1) would be hda2, root(hd1,0) would be hdb1, etc. Putting in the wrong values can hose things up in a not so nice way ;) 8. Exit from chroot and rescue mode by pressing ctrl+d twice. 9. Enjoy =) Regards, -- Cliff Wells, Software Engineer Logiplex Corporation (www.logiplex.net) (503) 978-6726 (800) 735-0555 From owner-linux-xfs@oss.sgi.com Mon Jun 23 17:52:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Jun 2003 17:52:55 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5O0qd2x031108 for ; Mon, 23 Jun 2003 17:52:39 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5O0qddZ031107 for linux-xfs@oss.sgi.com; Mon, 23 Jun 2003 17:52:39 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5O0qb31031092 for ; Mon, 23 Jun 2003 17:52:37 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5O0Gm38030873; Mon, 23 Jun 2003 17:16:48 -0700 Date: Mon, 23 Jun 2003 17:16:48 -0700 Message-Id: <200306240016.h5O0Gm38030873@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 254] New: Bootloader X-Bugzilla-Reason: AssignedTo X-archive-position: 4447 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=254 Summary: Bootloader Product: Linux XFS Version: 1.2.x Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: Medium Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: xpxp2002@hotmail.com After running up2date on my Red Hat 9 PC, I restarted to find that GRUB would not load the kernel. I am assuming that it overwrote the XFS kernel patches. How can I recover the data from this volume? ------- 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 Jun 24 00:24:20 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 00:24:40 -0700 (PDT) Received: from wormhole.wms-hn.de (wormhole.wms-hn.de [141.7.87.2]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5O7OI2x006809 for ; Tue, 24 Jun 2003 00:24:19 -0700 Received: from notebook.rz.uni-karlsruhe.de (vpn-cl1-028.rz.uni-karlsruhe.de [129.13.68.28]) (authenticated (0 bits)) by wormhole.wms-hn.de (8.11.6/8.11.6/SuSE Linux 0.5) with ESMTP id h5O7OBU26135 for ; Tue, 24 Jun 2003 09:24:11 +0200 Subject: Problem with xfsdump From: Tilo Lutz To: linux-xfs@oss.sgi.com Content-Type: text/plain Message-Id: <1056439296.5675.6.camel@notebook.rz.uni-karlsruhe.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 24 Jun 2003 09:21:36 +0200 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-archive-position: 4448 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: TiloLutz@gmx.de Precedence: bulk X-list: linux-xfs Hi I have a problem using xfsdump to backup on a remote system. I use an onstream-tape wich is only able safe data with a blocksize of 32768. Is it possible xfsdump is ignorier the "-b" parameter if data will be stored on a remote host? If I run xfsdump -f backup@$IP:/dev/nst0 -o -l 0 -L "`date`" -M "Server" -F -b 32768 / I get the following error on remote host: st0: Illegal blocksize. But blocksize is OK. The same command works on the remote host itself and tar is working on both machines. Any ideas whats wrong? Regards, Tilo Lutz From owner-linux-xfs@oss.sgi.com Tue Jun 24 02:59:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 02:59:28 -0700 (PDT) Received: from moe ([203.154.157.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5O9x52x019614 for ; Tue, 24 Jun 2003 02:59:06 -0700 Received: from moe ([127.0.0.1]) by moe with esmtp (Exim 4.10) id 19UkJx-0003fn-00 for linux-xfs@oss.sgi.com; Tue, 24 Jun 2003 16:42:37 +0700 From: "Jason H. Smith" To: linux-xfs@oss.sgi.com Subject: XFS as initrd file system Date: Tue, 24 Jun 2003 16:42:32 +0700 User-Agent: KMail/1.5.2 X-GPG-Fingerprint: 03EE 9EB8 E500 874A F509 7B95 9B9A 84A1 26E9 4F79 X-GPG-Publickey: http://www.ece.utexas.edu/~jhs/public_key.gpg MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_N0B++5d5zqj4cBu"; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200306241642.37639.jhs@oes.co.th> X-archive-position: 4449 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jhs@oes.co.th Precedence: bulk X-list: linux-xfs --Boundary-02=_N0B++5d5zqj4cBu Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline Hi. I'm trying to make an XFS-only system. The kernel mounts XFS=20 filesystems fine, but I'm having problems migrating from an ext2 initrd=20 image to XFS. I've tried 4, 8, and 32 megabyte initrd sizes; and various block sizes=20 (mkfs.xfs -b), but I get the same error from the kernel at the initrd=20 phase: XFS: device supports only 1024 byte sectors (not 512) Kernel panic: VFS: Unable to mount root fs on 00:00 This same setup works if I use ext2 as the initrd filesystem, but I do not= =20 want ext2 in my kernel for something as trivial as initrd. Thanks much for any thoughts. My searches got many false positives about= =20 XFS modules and such in the initrd environment; but that is not my=20 problem at all. --=20 Jason Smith Open Enterprise Systems Bangkok, Thailand --Boundary-02=_N0B++5d5zqj4cBu Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA++B0Nm5qEoSbpT3kRAoHpAJ9poKA7qHgxhu8dRaCeul1+Qs2DcwCghDOq Ot0P6Qwp8sal2FeixXQa6lw= =P2LE -----END PGP SIGNATURE----- --Boundary-02=_N0B++5d5zqj4cBu-- From owner-linux-xfs@oss.sgi.com Tue Jun 24 03:15:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 03:15:37 -0700 (PDT) Received: from malik.acsalaska.net (malik.slb.nwc.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OAFI2x020206 for ; Tue, 24 Jun 2003 03:15:18 -0700 Received: from erbenson.alaska.net (32-pm5.nwc.alaska.net [209.112.139.32]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h5OAFGrh073327 for ; Tue, 24 Jun 2003 02:15:16 -0800 (AKDT) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id A191E3A06 for ; Tue, 24 Jun 2003 02:15:15 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 643D540FF44; Tue, 24 Jun 2003 02:15:15 -0800 (AKDT) Date: Tue, 24 Jun 2003 02:15:15 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS as initrd file system Message-ID: <20030624101515.GD1363@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200306241642.37639.jhs@oes.co.th> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eqp4TxRxnD4KrmFZ" Content-Disposition: inline In-Reply-To: <200306241642.37639.jhs@oes.co.th> 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-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4450 X-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 --eqp4TxRxnD4KrmFZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 24, 2003 at 04:42:32PM +0700, Jason H. Smith wrote: Content-Description: signed data > Hi. I'm trying to make an XFS-only system. The kernel mounts XFS=20 > filesystems fine, but I'm having problems migrating from an ext2 initrd= =20 > image to XFS. well do you really need to use initrd? > I've tried 4, 8, and 32 megabyte initrd sizes; and various block sizes=20 > (mkfs.xfs -b), but I get the same error from the kernel at the initrd=20 > phase: >=20 > XFS: device supports only 1024 byte sectors (not 512) > Kernel panic: VFS: Unable to mount root fs on 00:00 hmm, sounds like a task for the new xfsprogs 2.5.0 mkfs.xfs which has a -s switch to set the sector size to something other then 512 (i think its -s anyway), this would probably also require a current cvs kernel. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --eqp4TxRxnD4KrmFZ 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 iEYEARECAAYFAj74JLMACgkQJKx7GixEevybpQCfXc4p1N4kMy0eK0KFuKhVuvc1 EpMAnA0bpPd8mcDgmZINDXnLq7sjlXYu =+HwV -----END PGP SIGNATURE----- --eqp4TxRxnD4KrmFZ-- From owner-linux-xfs@oss.sgi.com Tue Jun 24 03:26:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 03:26:22 -0700 (PDT) Received: from moe ([203.154.157.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OAQ32x020681 for ; Tue, 24 Jun 2003 03:26:05 -0700 Received: from moe ([127.0.0.1]) by moe with esmtp (Exim 4.10) id 19Ukk0-0003tq-00 for linux-xfs@oss.sgi.com; Tue, 24 Jun 2003 17:09:32 +0700 From: "Jason H. Smith" To: linux-xfs@oss.sgi.com Subject: Re: XFS as initrd file system Date: Tue, 24 Jun 2003 17:09:31 +0700 User-Agent: KMail/1.5.2 References: <200306241642.37639.jhs@oes.co.th> <20030624101515.GD1363@plato.local.lan> In-Reply-To: <20030624101515.GD1363@plato.local.lan> X-GPG-Fingerprint: 03EE 9EB8 E500 874A F509 7B95 9B9A 84A1 26E9 4F79 X-GPG-Publickey: http://www.ece.utexas.edu/~jhs/public_key.gpg MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_bNC++9l7xzUsPe/"; charset="tis-620" Content-Transfer-Encoding: 7bit Message-Id: <200306241709.31621.jhs@oes.co.th> X-archive-position: 4451 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jhs@oes.co.th Precedence: bulk X-list: linux-xfs --Boundary-02=_bNC++9l7xzUsPe/ Content-Type: text/plain; charset="tis-620" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline Hi again. Thanks for the speedy feedback! On Tuesday 24 June 2003 05:15 pm, Ethan Benson wrote: > well do you really need to use initrd? Unfortunately, initrd is an integral part of the system for other reasons.= =20=20 Personally, I'm looking forward to the new initramfs stuff in 2.5. > hmm, sounds like a task for the new xfsprogs 2.5.0 mkfs.xfs which has > a -s switch to set the sector size to something other then 512 (i > think its -s anyway), this would probably also require a current cvs > kernel. Thanks for the information. --=20 Jason Smith Open Enterprise Systems Bangkok, Thailand --Boundary-02=_bNC++9l7xzUsPe/ Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA++CNbm5qEoSbpT3kRAtZVAJ4/FoccyNKkx+fdTPwbTgx9DfC0cgCgksMm sbIUdnIBD92Rue8WlelvL6U= =0pFD -----END PGP SIGNATURE----- --Boundary-02=_bNC++9l7xzUsPe/-- From owner-linux-xfs@oss.sgi.com Tue Jun 24 06:57:24 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 06:57:48 -0700 (PDT) Received: from argo.starforce.com (argo.starforce.com [216.158.58.233]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5ODvK2x024318 for ; Tue, 24 Jun 2003 06:57:23 -0700 Received: from argo.starforce.com (dwild@localhost [127.0.0.1]) by argo.starforce.com (8.12.9/8.12.9) with ESMTP id h5ODvImf015163; Tue, 24 Jun 2003 09:57:18 -0400 Received: from localhost (dwild@localhost) by argo.starforce.com (8.12.9/8.12.9/Submit) with ESMTP id h5ODvIbj015159; Tue, 24 Jun 2003 09:57:18 -0400 X-Authentication-Warning: argo.starforce.com: dwild owned process doing -bs Date: Tue, 24 Jun 2003 09:57:18 -0400 (EDT) From: dwild+xfs@starforce.com X-X-Sender: dwild@argo.starforce.com To: Tilo Lutz cc: linux-xfs@oss.sgi.com Subject: Re: Problem with xfsdump In-Reply-To: <1056439296.5675.6.camel@notebook.rz.uni-karlsruhe.de> Message-ID: References: <1056439296.5675.6.camel@notebook.rz.uni-karlsruhe.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4452 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dwild+xfs@starforce.com Precedence: bulk X-list: linux-xfs On Tue, 24 Jun 2003, Tilo Lutz wrote: > I have a problem using xfsdump to backup on a remote > system. I use an onstream-tape wich is only able > safe data with a blocksize of 32768. > Is it possible xfsdump is ignorier the "-b" parameter > if data will be stored on a remote host? > If I run xfsdump -f backup@$IP:/dev/nst0 -o -l 0 -L "`date`" -M > "Server" -F -b 32768 / I get the following error on > remote host: st0: Illegal blocksize. > But blocksize is OK. The same command works on the remote host > itself and tar is working on both machines. > Any ideas whats wrong? I had the same problem, and I ended up adding the '-m' flag to get around it. Here's my command line (lto1 drive, 1024k block size): xfsdump -o -b 1048576 -m -F -L $LOCALNAME:$FS -d 256 -e -p 60 -l $LEVEL -f $DRIVEHOST:$DRIVEPATH -c "$MEDIACHANGE" $FS It seems remote drive handling still needs some work, but this may be a limitation in rmt, not xfsdump. mp From owner-linux-xfs@oss.sgi.com Tue Jun 24 07:06:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 07:06:43 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OE6c2x024896 for ; Tue, 24 Jun 2003 07:06:38 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5OENhmO011268 for ; Tue, 24 Jun 2003 09:23:43 -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 h5OE6WqX6053257; Tue, 24 Jun 2003 09:06: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 h5OE6UYl12971958; Tue, 24 Jun 2003 09:06:32 -0500 (CDT) Date: Tue, 24 Jun 2003 09:06:30 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: "Jason H. Smith" cc: linux-xfs@oss.sgi.com Subject: Re: XFS as initrd file system In-Reply-To: <200306241709.31621.jhs@oes.co.th> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4453 X-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 Ethan is on the right track, it sounds like your root device is a funky 1024-byte sector beast. In general, XFS cannot do this, although as Ethan said, Nathan does have new code in CVS that I think is well on the way to working correctly. I'm not sure I'd call it a supported feature quite yet though. The -b option to mkfs changes the filesystem block size, btw, so that does not help with the device sector size. Out of curiosity, what is your root device? -Eric On Tue, 24 Jun 2003, Jason H. Smith wrote: > Hi again. Thanks for the speedy feedback! > > On Tuesday 24 June 2003 05:15 pm, Ethan Benson wrote: > > well do you really need to use initrd? > > Unfortunately, initrd is an integral part of the system for other reasons. > Personally, I'm looking forward to the new initramfs stuff in 2.5. > > > hmm, sounds like a task for the new xfsprogs 2.5.0 mkfs.xfs which has > > a -s switch to set the sector size to something other then 512 (i > > think its -s anyway), this would probably also require a current cvs > > kernel. > > Thanks for the information. > > -- > Jason Smith > Open Enterprise Systems > Bangkok, Thailand > From owner-linux-xfs@oss.sgi.com Tue Jun 24 07:17:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 07:17:20 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OEHE2x025392 for ; Tue, 24 Jun 2003 07:17:14 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5OEYJmO011805 for ; Tue, 24 Jun 2003 09:34:19 -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 h5OEH9qX6053785; Tue, 24 Jun 2003 09:17:09 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 19Uobc-0000Fw-00; Tue, 24 Jun 2003 09:17:08 -0500 Date: Tue, 24 Jun 2003 09:17:08 -0500 From: Nathan Straz To: "Jason H. Smith" Cc: linux-xfs@oss.sgi.com Subject: Re: XFS as initrd file system Message-ID: <20030624141708.GB2008@sgi.com> Mail-Followup-To: "Jason H. Smith" , linux-xfs@oss.sgi.com References: <200306241642.37639.jhs@oes.co.th> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200306241642.37639.jhs@oes.co.th> User-Agent: Mutt/1.5.3i X-archive-position: 4454 X-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 On Tue, Jun 24, 2003 at 04:42:32PM +0700, Jason H. Smith wrote: > Hi. I'm trying to make an XFS-only system. The kernel mounts XFS > filesystems fine, but I'm having problems migrating from an ext2 initrd > image to XFS. ... > This same setup works if I use ext2 as the initrd filesystem, but I do not > want ext2 in my kernel for something as trivial as initrd. IMHO, a journaled file system is a little overkill for an initrd image. If you want an alternative to ext2, you might want to look at cramfs. I think using XFS for an initrd image is best kept to an academic exercise. -- 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 Tue Jun 24 07:55:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 07:56:06 -0700 (PDT) Received: from THOR.goeci.com ([66.28.220.99]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OEtp2x026390 for ; Tue, 24 Jun 2003 07:55:52 -0700 Received: by THOR.goeci.com with Internet Mail Service (5.5.2653.19) id ; Tue, 24 Jun 2003 10:55:45 -0400 Message-ID: <2D92FEBFD3BE1346A6C397223A8DD3FC092341@THOR.goeci.com> From: Murthy Kambhampaty To: linux-xfs@oss.sgi.com Subject: cmds not visible in CVS? Date: Tue, 24 Jun 2003 10:55:45 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-archive-position: 4455 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: murthy.kambhampaty@goeci.com Precedence: bulk X-list: linux-xfs The CVS repository seems not to have the linux-2.4-xfs/cmd folder (noticed yesterday and today): "cvs server: cannot open directory /cvs/linux-2.4-xfs/cmd: No such file or directory" Is this temporary, or is there an alternate location for the latest userspace programs? Thanks for the help, Murthy From owner-linux-xfs@oss.sgi.com Tue Jun 24 08:05:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 08:05:39 -0700 (PDT) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OF5X2x027466 for ; Tue, 24 Jun 2003 08:05:33 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by tolkor.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5OFMcmO014430 for ; Tue, 24 Jun 2003 10:22:38 -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 h5OF5RqX6065520; Tue, 24 Jun 2003 10:05:27 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 19UpMN-0000Xw-00; Tue, 24 Jun 2003 10:05:27 -0500 Date: Tue, 24 Jun 2003 10:05:27 -0500 From: Nathan Straz To: Murthy Kambhampaty Cc: linux-xfs@oss.sgi.com Subject: Re: cmds not visible in CVS? Message-ID: <20030624150527.GC2008@sgi.com> Mail-Followup-To: Murthy Kambhampaty , linux-xfs@oss.sgi.com References: <2D92FEBFD3BE1346A6C397223A8DD3FC092341@THOR.goeci.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2D92FEBFD3BE1346A6C397223A8DD3FC092341@THOR.goeci.com> User-Agent: Mutt/1.5.3i X-archive-position: 4456 X-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 On Tue, Jun 24, 2003 at 10:55:45AM -0400, Murthy Kambhampaty wrote: > The CVS repository seems not to have the linux-2.4-xfs/cmd folder (noticed > yesterday and today): > "cvs server: cannot open directory /cvs/linux-2.4-xfs/cmd: No such file or > directory" > > Is this temporary, or is there an alternate location for the latest > userspace programs? The xfs-cmds were moved out of the kernel trees since they didn't need to be there. Check out the xfs-cmds module. The CVS download instructions on the XFS web page include this information too. -- 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 Tue Jun 24 08:35:05 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 08:35:24 -0700 (PDT) Received: from mail.asianet.co.th (mail1.asianet.co.th [203.144.222.229]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OFZ42x028104 for ; Tue, 24 Jun 2003 08:35:05 -0700 Received: from virscan1.asianet.co.th (HELO mx.asianet.co.th) ([203.144.222.197]) (envelope-sender ) by mail1.asianet.co.th (qmail-ldap-1.03) with SMTP for ; 24 Jun 2003 22:25:46 +0700 Received: from ppp-203.144.203.64.revip.asianet.co.th (HELO 192.168.1.116) ([203.144.203.64]) (envelope-sender ) by mx1.asianet.co.th (qmail-ldap-1.03) with SMTP for ; 24 Jun 2003 22:25:45 +0700 From: "Jason H. Smith" To: linux-xfs@oss.sgi.com Subject: Re: XFS as initrd file system Date: Tue, 24 Jun 2003 22:08:38 +0700 User-Agent: KMail/1.5.2 References: <200306241642.37639.jhs@oes.co.th> <20030624141708.GB2008@sgi.com> In-Reply-To: <20030624141708.GB2008@sgi.com> X-GPG-Fingerprint: 03EE 9EB8 E500 874A F509 7B95 9B9A 84A1 26E9 4F79 X-GPG-Publickey: http://www.ece.utexas.edu/~jhs/public_key.gpg MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_9lG++wN++s125MP"; charset="tis-620" Content-Transfer-Encoding: 7bit Message-Id: <200306242208.46076.jhs@oes.co.th> X-archive-position: 4457 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jhs@oes.co.th Precedence: bulk X-list: linux-xfs --Boundary-02=_9lG++wN++s125MP Content-Type: text/plain; charset="tis-620" Content-Transfer-Encoding: quoted-printable Content-Description: signed data Content-Disposition: inline On Tuesday 24 June 2003 09:17 pm, Nathan Straz wrote: > IMHO, a journaled file system is a little overkill for an initrd image. > If you want an alternative to ext2, you might want to look at cramfs.=20 > I think using XFS for an initrd image is best kept to an academic > exercise. That's a good point. The argument for XFS is that the kernel already has= =20 XFS (it later mounts standard hard drives); so why bloat the kernel with=20 another filesystem? (Okay, cramfs isn't that much bloat, but it still=20 violates the KISS principle.) But in truth, I already have it working; just that an XFS-only kernel=20 strikes me as the most elegant (compare: compiling a whole new filesystem= =20 for the 5 seconds spent in initrd). Anyway this initrd madness will go=20 away in 2.6, so there's some good news. Thanks everybody for the helpful input. --=20 Jason Smith Open Enterprise Systems Bangkok, Thailand --Boundary-02=_9lG++wN++s125MP Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQA++Gl9m5qEoSbpT3kRAlQ2AKC2qi7J1gc/0xls/txZuYN0a9VQfQCgjIpv AxggUFpLgvXDvXNL8DwKpSA= =vvAP -----END PGP SIGNATURE----- --Boundary-02=_9lG++wN++s125MP-- From owner-linux-xfs@oss.sgi.com Tue Jun 24 09:26:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 09:26:54 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OGQc2x029942 for ; Tue, 24 Jun 2003 09:26:39 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h5OGQBW1003496 for ; Tue, 24 Jun 2003 11:26:11 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h5OGQALw003494 for linux-xfs@oss.sgi.com; Tue, 24 Jun 2003 11:26:10 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: XFS as a module for RH AS or ES From: Austin Gonyou To: XFS List Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1056471969.2919.14.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 24 Jun 2003 11:26:10 -0500 X-archive-position: 4458 X-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 I was curious as to the status of this possible effort. Is this something actively pursued? How long will it be? What parts would need to be stable before using in an enterprise production environmet, etc? (i.e. XFS environment module would need to be created so one could use a binary only kernel + xfs without patches) Which XFS codebase could be used as the module?(1.2+?) I ask all this because it would be very nice for us to use this if we could even possibly buy support or something to get all our server OS parts supported, that would be nice. -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Tue Jun 24 12:26:23 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Jun 2003 12:26:36 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5OJQN2x032680 for ; Tue, 24 Jun 2003 12:26:23 -0700 Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5OJQHE0028413 for ; Tue, 24 Jun 2003 12:26:17 -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 h5OJQHRc004730 for ; Tue, 24 Jun 2003 14:26:17 -0500 Received: (from sandeen@localhost) by stout.americas.sgi.com (8.12.8/8.12.8/Submit) id h5OJQGuH004728 for linux-xfs@oss.sgi.com; Tue, 24 Jun 2003 14:26:16 -0500 Date: Tue, 24 Jun 2003 14:26:16 -0500 From: Eric Sandeen Message-Id: <200306241926.h5OJQGuH004728@stout.americas.sgi.com> Subject: TAKE - Fix default /proc/sys/fs/xfs values again X-archive-position: 4459 X-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 Fix values in xfs_params after re-ordering.... .. and add initializers so this doesn't get messed up again! Date: Tue Jun 24 12:25: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: 2.4.x-xfs:slinx:151941a linux/fs/xfs/linux/xfs_globals.c - 1.50 From owner-linux-xfs@oss.sgi.com Wed Jun 25 02:07:32 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 02:07:53 -0700 (PDT) Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5P97U2x029050 for ; Wed, 25 Jun 2003 02:07:32 -0700 Received: from auto-nb1.xs4all.nl (a80-126-90-136.adsl.xs4all.nl [80.126.90.136]) by smtpzilla2.xs4all.nl (8.12.9/8.12.9) with ESMTP id h5P97QV4068234; Wed, 25 Jun 2003 11:07:26 +0200 (CEST) Message-Id: <4.3.2.7.2.20030625105031.039361b0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 25 Jun 2003 11:07:24 +0200 To: Austin Gonyou , XFS List From: Seth Mos Subject: Re: XFS as a module for RH AS or ES In-Reply-To: <1056471969.2919.14.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4460 X-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 At 11:26 24-6-2003 -0500, Austin Gonyou wrote: >I was curious as to the status of this possible effort. I am working on a installer but it will not use the 2.4.9 enterprise kernel as it originally did. >Is this something actively pursued? How long will it be? Every know and then I spend some hours on it. So far I have CD set that has the XFS kernel bits and userland tools on it. The biggest problem is the modification of the installer. Since the license for the Red Hat installer prohibits redistributing with the Red Hat trademark logo's and material this needs a lot of work. Basically Red Hat ES is 7.2 with a few patches. The differences are not that huge. >What parts would need to be stable before using in an enterprise >production environmet, etc? (i.e. XFS environment module would need to >be created so one could use a binary only kernel + xfs without patches) >Which XFS codebase could be used as the module?(1.2+?) There is no way to make XFS possible as a module without patching the kernel. Especially something as "old" as the 2.4.9 enterprise kernel. What I am searching for is someone that would attempt fitting XFS 1.2 (or 1.3pre) into the 2.4.9 enterprise kernel. it won't be pretty. You can fetch the Red Hat kernel from their ftp server. ftp://updates.redhat.com/enterprise/2.1ES/en/os/SRPMS/kernel-2.4.9-e.25.src.rpm For now I stick with the 2.4.20-18 kernel with XFS during and after installation. >I ask all this because it would be very nice for us to use this if we >could even possibly buy support or something to get all our server OS >parts supported, that would be nice. As soon as you recompile a kernel or install a significant third party library you will already void the support contract. Red Hat only supports plain vanilla RHEL ES installs and I fully understand since support would otherwise be a nightmare. We bought the basic ES product for $350 only to find that it doesn't support the raid controller in the new server it is supposed to be installed on. Yay. Red Hat says that the machine is not listed in their hardware compatability list and as such will not do anything with the support call. To make it even sillier, the driver for the raid controller in question is in the rpm but not available during installer time... aaarrrgh. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Wed Jun 25 07:22:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 07:23:12 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PEMo2x004456 for ; Wed, 25 Jun 2003 07:22:51 -0700 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19VB5L-0004YR-00 for ; Wed, 25 Jun 2003 16:17:19 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: linux-xfs@oss.sgi.com Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19VB4C-0004TA-00 for ; Wed, 25 Jun 2003 16:16:08 +0200 From: Nicholas Wourms Subject: Re: XFS as a module for RH AS or ES Date: Wed, 25 Jun 2003 10:16:23 -0400 Lines: 27 Message-ID: <3EF9AEB7.1060501@myrealbox.com> References: <1056471969.2919.14.camel@portageek.digitalroadkill.net> <4.3.2.7.2.20030625105031.039361b0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.2) Gecko/20030208 MultiZilla/v1.1.20 X-Accept-Language: en-us, en X-Enigmail-Version: 0.75.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-archive-position: 4461 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nwourms@myrealbox.com Precedence: bulk X-list: linux-xfs Seth Mos wrote: [SNIP] > We bought the basic ES product for $350 only to find that it doesn't > support the raid controller in the new server it is supposed to be > installed on. Yay. Red Hat says that the machine is not listed in their > hardware compatability list and as such will not do anything with the > support call. To make it even sillier, the driver for the raid > controller in question is in the rpm but not available during installer > time... aaarrrgh. Hi Seth, I spoke with Rik van Riel the other day regarding an enterprise kernel beta I found on rawhide and he said the 2.4.2{0|1} version of the Red Hat enteprise kernel should be going into "official" freeze any day now. Based on that, he predicts that a formal release of that kernel should happen soon (mid July?) (I'm assuming a new version of the AS/ES product will be released as well). Unfortunately, while it uses the more current -rc-ac patchset (which had xfs support), apparently they stripped the xfs bits from it. Still, it should be better then screwing around with 2.4.9 :-). Perhaps you might want to e-mail him and express interest in helping to get xfs support into anaconda (since xfs is pretty popular in the enterprise). Cheers, Nicholas From owner-linux-xfs@oss.sgi.com Wed Jun 25 11:09:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 11:09:30 -0700 (PDT) Received: from flood.physik.tu-cottbus.de (flood.physik.TU-Cottbus.De [141.43.75.21]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PI912x010279 for ; Wed, 25 Jun 2003 11:09:02 -0700 Received: from harpo.physik.tu-cottbus.de (harpo.physik.tu-cottbus.de [141.43.75.44]) by flood.physik.tu-cottbus.de (Postfix) with ESMTP id D2F7C701E05 for ; Wed, 25 Jun 2003 19:25:44 +0200 (CEST) Received: by harpo.physik.tu-cottbus.de (Postfix, from userid 7224) id 0D45F805; Wed, 25 Jun 2003 19:25:43 +0200 (CEST) Date: Wed, 25 Jun 2003 19:25:43 +0200 From: Ionut Georgescu To: linux-xfs@oss.sgi.com Subject: FAQ - debian installer Message-ID: <20030625172543.GI2903@physik.tu-cottbus.de> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i X-archive-position: 4462 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: george@physik.tu-cottbus.de Precedence: bulk X-list: linux-xfs Hi, browsing the XFS website for a Changelog for the upcoming 1.3 Release, I found my webpage (http://www.physik.tu-cottbus.de/~george/woody_xfs/) listed in the FAQ under boot-floppies for Debian. Thank you very much, but, I don't remember having mirrored anything. :) I was so disappointed of another XFS installer I had used, that I hacked the boot-floppy sources and made my own installer. Unfortunately I had to drop maintaing it because I lost the patch and I don't want to start all over. :) The installer is still usable, however. Regards, Ionut -- *************** * Ionut Georgescu * http://www.physik.tu-cottbus.de/~george/ * Registered Linux User #244479 * * "In Windows you can do everything Microsoft wants you to do; in Unix you * can do anything the computer is able to do." From owner-linux-xfs@oss.sgi.com Wed Jun 25 12:25:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 12:25:49 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PJPX2x014020 for ; Wed, 25 Jun 2003 12:25: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.2/linux-outbound_gateway-1.2) with ESMTP id h5PJPRiY026137 for ; Wed, 25 Jun 2003 12:25:27 -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 h5PJORqX6308432; Wed, 25 Jun 2003 14:24: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 h5PJOQYl13070469; Wed, 25 Jun 2003 14:24:26 -0500 (CDT) Date: Wed, 25 Jun 2003 14:24:26 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Nicholas Wourms cc: linux-xfs@oss.sgi.com Subject: Re: XFS as a module for RH AS or ES In-Reply-To: <3EF9AEB7.1060501@myrealbox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4463 X-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 Nicholas - Any idea if they stripped just fs/xfs, or all of the xfs support infrastructure? (which is really not that much anymore). Having an "xfs-ready" kernel would be a very nice thing, you could then just load the module into it, even if they rm -rf'd fs/xfs. -Eric On Wed, 25 Jun 2003, Nicholas Wourms wrote: > Seth Mos wrote: > [SNIP] > > We bought the basic ES product for $350 only to find that it doesn't > > support the raid controller in the new server it is supposed to be > > installed on. Yay. Red Hat says that the machine is not listed in their > > hardware compatability list and as such will not do anything with the > > support call. To make it even sillier, the driver for the raid > > controller in question is in the rpm but not available during installer > > time... aaarrrgh. > > Hi Seth, > > I spoke with Rik van Riel the other day regarding an enterprise kernel > beta I found on rawhide and he said the 2.4.2{0|1} version of the Red > Hat enteprise kernel should be going into "official" freeze any day now. > Based on that, he predicts that a formal release of that kernel should > happen soon (mid July?) (I'm assuming a new version of the AS/ES product > will be released as well). Unfortunately, while it uses the more > current -rc-ac patchset (which had xfs support), apparently they > stripped the xfs bits from it. Still, it should be better then screwing > around with 2.4.9 :-). Perhaps you might want to e-mail him and express > interest in helping to get xfs support into anaconda (since xfs is > pretty popular in the enterprise). > > Cheers, > Nicholas > > > From owner-linux-xfs@oss.sgi.com Wed Jun 25 13:02:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 13:02:31 -0700 (PDT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PK292x018973 for ; Wed, 25 Jun 2003 13:02:15 -0700 Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19VGSB-0007zz-00 for ; Wed, 25 Jun 2003 22:01:15 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: linux-xfs@oss.sgi.com Received: from news by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 19VGRM-0007wD-00 for ; Wed, 25 Jun 2003 22:00:24 +0200 From: Nicholas Wourms Subject: Re: XFS as a module for RH AS or ES Date: Wed, 25 Jun 2003 16:00:26 -0400 Lines: 29 Message-ID: <3EF9FF5A.6000703@myrealbox.com> References: <3EF9AEB7.1060501@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@main.gmane.org Cc: Seth Mos User-Agent: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.0.2) Gecko/20030208 MultiZilla/v1.1.20 X-Accept-Language: en-us, en X-Enigmail-Version: 0.75.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime X-archive-position: 4464 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nwourms@myrealbox.com Precedence: bulk X-list: linux-xfs Eric Sandeen wrote: > Nicholas - > > Any idea if they stripped just fs/xfs, or all of the xfs support > infrastructure? (which is really not that much anymore). > > Having an "xfs-ready" kernel would be a very nice thing, you could then > just load the module into it, even if they rm -rf'd fs/xfs. Eric & Seth, I'm really sorry for spreading that FUD earlier, apparently my interdiff was acting up and not accurately reporting differences (and I didn't actually look in the patch to verify xfs' removal). So, in actuality, they have NOT stripped the xfs from the -ac series patch. So, long story short, it is in there. Unfortunately, the kernel configs still indicate that they aren't building any kernels (boot or otherwise) with modular or builtin xfs support :-/. XFS-ready is better than nothing, I suppose. To reiterate, this seems to be only applicable to their forthcoming Enterprise (ES/AS) kernels. I have no idea what Arjan is going to do with the regular kernel, the current rawhide for it is quite featureless... Cheers, Nicholas P.S. - Eric I can send you the source rpm I have, if you want. They took it off the mirrors, so you won't be able to get it there. From owner-linux-xfs@oss.sgi.com Wed Jun 25 13:48:16 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 13:48:33 -0700 (PDT) Received: from portageek.digitalroadkill.net (host-65-120-145-91.coremetrics.com [65.120.145.91] (may be forged)) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PKmE2x020429 for ; Wed, 25 Jun 2003 13:48:15 -0700 Received: from portageek.digitalroadkill.net (localhost.localdomain [127.0.0.1]) by portageek.digitalroadkill.net (8.12.8/8.12.8) with ESMTP id h5PKlkIF004854; Wed, 25 Jun 2003 15:47:46 -0500 Received: (from austin@localhost) by portageek.digitalroadkill.net (8.12.8/8.12.8/Submit) id h5PKljkg004852; Wed, 25 Jun 2003 15:47:45 -0500 X-Authentication-Warning: portageek.digitalroadkill.net: austin set sender to austin@coremetrics.com using -f Subject: Re: XFS as a module for RH AS or ES From: Austin Gonyou To: Seth Mos Cc: XFS List In-Reply-To: <4.3.2.7.2.20030625105031.039361b0@pop.xs4all.nl> References: <4.3.2.7.2.20030625105031.039361b0@pop.xs4all.nl> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Coremetrics, Inc. Message-Id: <1056574065.2140.29.camel@portageek.digitalroadkill.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 25 Jun 2003 15:47:45 -0500 X-archive-position: 4465 X-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 On Wed, 2003-06-25 at 04:07, Seth Mos wrote: > At 11:26 24-6-2003 -0500, Austin Gonyou wrote: > >I was curious as to the status of this possible effort. > > I am working on a installer but it will not use the 2.4.9 enterprise > kernel > as it originally did. I see. Ok. > >What parts would need to be stable before using in an enterprise > >production environmet, etc? (i.e. XFS environment module would need > to > >be created so one could use a binary only kernel + xfs without > patches) > >Which XFS codebase could be used as the module?(1.2+?) > > There is no way to make XFS possible as a module without patching the > kernel. Especially something as "old" as the 2.4.9 enterprise kernel. I was thinking that, but I wasn't sure of the approach to this problem. > What I am searching for is someone that would attempt fitting XFS 1.2 > (or > 1.3pre) into the 2.4.9 enterprise kernel. it won't be pretty. > You can fetch the Red Hat kernel from their ftp server. > ftp://updates.redhat.com/enterprise/2.1ES/en/os/SRPMS/kernel-2.4.9-e.25.src.rpm > > For now I stick with the 2.4.20-18 kernel with XFS during and after > installation. We're currently running 2.4.18-27 XFS enabled kernel. I'm not having a huge issue with all this, but the damn qlogic drivers we use keep shitting the bed on us. I'm not 100% sure why just yet, but something's afoot here. So, in an effort to have/get support for all pieces we're using, I was looking at potentially using RHAS 2.1. At least, at some level, we could know that this "configuration" *should* work. If it doesn't then it expands our troubleshooting capabilities so each organization RH/Dell/Oracle, can offer their aid as well. > >I ask all this because it would be very nice for us to use this if we > >could even possibly buy support or something to get all our server OS > >parts supported, that would be nice. > > As soon as you recompile a kernel or install a significant third party > library you will already void the support contract. > Red Hat only supports plain vanilla RHEL ES installs and I fully > understand > since support would otherwise be a nightmare. >From my understanding, RHAS recompiled kernels ,from their src rpm are supported. I will have a phone call with someone about this soon, but I had already contacted them about this. > We bought the basic ES product for $350 only to find that it doesn't > support the raid controller in the new server it is supposed to be > installed on. Yay. Red Hat says that the machine is not listed in > their > hardware compatability list and as such will not do anything with the > support call. To make it even sillier, the driver for the raid > controller > in question is in the rpm but not available during installer time... > aaarrrgh. Our bigger issue is the 2500/server/year support cost, plus NO XFS support. Bah..screw that! > Cheers > > -- > Seth > It might just be your lucky day, if you only knew. -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Wed Jun 25 13:57:02 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 13:57:05 -0700 (PDT) Received: from linux-sxs.org (dhcp065-024-128-253.columbus.rr.com [65.24.128.253]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PKv02x021230 for ; Wed, 25 Jun 2003 13:57:01 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.9/8.12.9) with ESMTP id h5PKuvH7027786 for ; Wed, 25 Jun 2003 16:56:57 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.9/8.12.9/Submit) with ESMTP id h5PKuv3L017476 for ; Wed, 25 Jun 2003 16:56:57 -0400 Date: Wed, 25 Jun 2003 16:56:57 -0400 (EDT) From: Net Llama! To: linux-xfs@oss.sgi.com Subject: 2.4.22-pre patches Message-ID: 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.34 X-archive-position: 4466 X-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 Anyone know if/when the cvs snapshots will cleanly apply against the 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is significantly better than what was in 2.4.21(-final). -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Wed Jun 25 13:58:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 13:58:04 -0700 (PDT) Received: from poptart.bithose.com (ip-204-97-176-41.modem.logical.net [204.97.176.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PKvx2x021603 for ; Wed, 25 Jun 2003 13:58:00 -0700 Received: from poptart.bithose.com (localhost [127.0.0.1]) by poptart.bithose.com (8.12.9/8.12.9) with ESMTP id h5PKvs0c148557; Wed, 25 Jun 2003 16:57:54 -0400 (EDT) Received: from localhost (jakari@localhost) by poptart.bithose.com (8.12.9/8.12.9/Submit) with ESMTP id h5PKvrak148626; Wed, 25 Jun 2003 16:57:54 -0400 (EDT) X-Authentication-Warning: poptart.bithose.com: jakari owned process doing -bs Date: Wed, 25 Jun 2003 16:57:53 -0400 (EDT) From: Jameel Akari To: Austin Gonyou cc: Seth Mos , XFS List Subject: Re: XFS as a module for RH AS or ES In-Reply-To: <1056574065.2140.29.camel@portageek.digitalroadkill.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4467 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jakari@bithose.com Precedence: bulk X-list: linux-xfs On 25 Jun 2003, Austin Gonyou wrote: > >From my understanding, RHAS recompiled kernels ,from their src rpm are > supported. I will have a phone call with someone about this soon, but I > had already contacted them about this. I had a phone call a few months ago with a Redhat sales guy who conferenced in an engineer, and it left we mith the impression that any 3rd party patches to the kernel (i.e. into it's SRPM and associated source tree) would render it unsupported. I can understand why they'd do that, of course. OTOH, you can understand why I had to politely turn down the RH sales guy.. the price issue was bad enough but the restrictions are what really killed it. -- #!/jameel/akari sleep 4800; make clean && make breakfast From owner-linux-xfs@oss.sgi.com Wed Jun 25 14:13:34 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 14:13:47 -0700 (PDT) Received: from phoenix.infradead.org (phoenix.infradead.org [195.224.96.167]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PLDW2x022615 for ; Wed, 25 Jun 2003 14:13:33 -0700 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 19VHa6-0003fM-00; Wed, 25 Jun 2003 22:13:30 +0100 Date: Wed, 25 Jun 2003 22:13:30 +0100 From: Christoph Hellwig To: Nicholas Wourms Cc: linux-xfs@oss.sgi.com, Seth Mos Subject: Re: XFS as a module for RH AS or ES Message-ID: <20030625221330.A14033@infradead.org> References: <3EF9AEB7.1060501@myrealbox.com> <3EF9FF5A.6000703@myrealbox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3EF9FF5A.6000703@myrealbox.com>; from nwourms@myrealbox.com on Wed, Jun 25, 2003 at 04:00:26PM -0400 X-archive-position: 4468 X-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 On Wed, Jun 25, 2003 at 04:00:26PM -0400, Nicholas Wourms wrote: > I'm really sorry for spreading that FUD earlier, apparently my interdiff > was acting up and not accurately reporting differences (and I didn't > actually look in the patch to verify xfs' removal). So, in actuality, > they have NOT stripped the xfs from the -ac series patch. So, long > story short, it is in there. Unfortunately, the kernel configs still > indicate that they aren't building any kernels (boot or otherwise) with > modular or builtin xfs support :-/. XFS-ready is better than nothing, I > suppose. To reiterate, this seems to be only applicable to their > forthcoming Enterprise (ES/AS) kernels. I have no idea what Arjan is > going to do with the regular kernel, the current rawhide for it is quite > featureless... The last RH AS3 kernel I have around here should be able to support a loadable, external XFS module out of the box. The XFS codebase would need some minor changes but it's definately doable. Let's see whether they use their chance to make even more a mess from their tree until the final release... From owner-linux-xfs@oss.sgi.com Wed Jun 25 14:19:40 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 14:19:43 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PLJd2x023064 for ; Wed, 25 Jun 2003 14:19:39 -0700 Received: from flecktone.americas.sgi.com (flecktone.americas.sgi.com [192.48.203.135]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5PLJYiY023197 for ; Wed, 25 Jun 2003 14:19:34 -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 h5PLIXqX6327154; Wed, 25 Jun 2003 16:18:33 -0500 (CDT) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-83.corp.sgi.com [134.15.64.83]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5PLIWRn139418751; Wed, 25 Jun 2003 16:18:32 -0500 (CDT) Subject: Re: 2.4.22-pre patches From: Steve Lord To: Net Llama! Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 25 Jun 2003 16:19:08 -0500 Message-Id: <1056575954.2047.29.camel@laptop.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 4469 X-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 On Wed, 2003-06-25 at 15:56, Net Llama! wrote: > Anyone know if/when the cvs snapshots will cleanly apply against the > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is > significantly better than what was in 2.4.21(-final). > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Lonni J Friedman netllama@linux-sxs.org > Linux Step-by-step & TyGeMo http://netllama.ipfox.com > Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre patch to it. Apart from kdb, it is usually pretty clean. Steve From owner-linux-xfs@oss.sgi.com Wed Jun 25 14:22:43 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 14:22:47 -0700 (PDT) Received: from phoenix.infradead.org (phoenix.infradead.org [195.224.96.167]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PLMf2x023521 for ; Wed, 25 Jun 2003 14:22:42 -0700 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 19VHit-0003ho-00; Wed, 25 Jun 2003 22:22:35 +0100 Date: Wed, 25 Jun 2003 22:22:35 +0100 From: Christoph Hellwig To: Steve Lord Cc: Net Llama! , linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches Message-ID: <20030625222235.A14214@infradead.org> References: <1056575954.2047.29.camel@laptop.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1056575954.2047.29.camel@laptop.americas.sgi.com>; from lord@sgi.com on Wed, Jun 25, 2003 at 04:19:08PM -0500 X-archive-position: 4470 X-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 On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: > On Wed, 2003-06-25 at 15:56, Net Llama! wrote: > > Anyone know if/when the cvs snapshots will cleanly apply against the > > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is > > significantly better than what was in 2.4.21(-final). > > > > -- > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Lonni J Friedman netllama@linux-sxs.org > > Linux Step-by-step & TyGeMo http://netllama.ipfox.com > > > > Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre > patch to it. Apart from kdb, it is usually pretty clean. I don't think it's that easy. 2.4.22-pre has the O_DIRECT changes from sct. Fixing XFS so that it compiles isn't that difficult (just some conflicts in filemap.c) but it's much more work to not cripple XFS O_DIRECT support due to these new locks. Without any changes all O_DIRECT I/O would happen with i_sem held now. From owner-linux-xfs@oss.sgi.com Wed Jun 25 14:29:33 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 14:29:36 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PLTX2x024035 for ; Wed, 25 Jun 2003 14:29: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.2/linux-outbound_gateway-1.2) with ESMTP id h5PLTRiY027277 for ; Wed, 25 Jun 2003 14:29:27 -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 h5PLTRqX6319404; Wed, 25 Jun 2003 16:29:27 -0500 (CDT) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-83.corp.sgi.com [134.15.64.83]) by daisy-e236.americas.sgi.com (8.12.9/SGI-server-1.8) with ESMTP id h5PLTPRn140192422; Wed, 25 Jun 2003 16:29:26 -0500 (CDT) Subject: Re: 2.4.22-pre patches From: Steve Lord To: Christoph Hellwig Cc: Net Llama! , linux-xfs@oss.sgi.com In-Reply-To: <20030625222235.A14214@infradead.org> References: <1056575954.2047.29.camel@laptop.americas.sgi.com> <20030625222235.A14214@infradead.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 25 Jun 2003 16:30:07 -0500 Message-Id: <1056576608.2047.32.camel@laptop.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 4471 X-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 On Wed, 2003-06-25 at 16:22, Christoph Hellwig wrote: > On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: > > Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre > > patch to it. Apart from kdb, it is usually pretty clean. > > I don't think it's that easy. 2.4.22-pre has the O_DIRECT changes from sct. > Fixing XFS so that it compiles isn't that difficult (just some conflicts > in filemap.c) but it's much more work to not cripple XFS O_DIRECT support > due to these new locks. Without any changes all O_DIRECT I/O would happen > with i_sem held now. Grr, forgot about that, I suppose we bounced off Marcello like water off a duck's back again - I saw you mention sending him infrastructure patches again? Steve From owner-linux-xfs@oss.sgi.com Wed Jun 25 14:56:49 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Jun 2003 14:56:53 -0700 (PDT) Received: from mail.vasoftware.com (mail@mail.vasoftware.com [198.186.202.175]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5PLun2x025446 for ; Wed, 25 Jun 2003 14:56:49 -0700 Received: from adsl-67-123-173-22.dsl.sntc01.pacbell.net ([67.123.173.22] helo=linux-sxs.org) by mail.vasoftware.com with asmtp (Cipher TLSv1:RC4-MD5:128) (Exim 3.31-VA-mm2 #1 (Debian)) id 19VIFh-0004ND-00 by VAauthid with fixed_plain; Wed, 25 Jun 2003 14:56:29 -0700 Message-ID: <3EFA1A66.6060403@linux-sxs.org> Date: Wed, 25 Jun 2003 14:55:50 -0700 From: "Net Llama!" Organization: HAL-III User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christoph Hellwig CC: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches References: <1056575954.2047.29.camel@laptop.americas.sgi.com> <20030625222235.A14214@infradead.org> In-Reply-To: <20030625222235.A14214@infradead.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4472 X-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 On 06/25/03 14:22, Christoph Hellwig wrote: > On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: >> On Wed, 2003-06-25 at 15:56, Net Llama! wrote: >> > Anyone know if/when the cvs snapshots will cleanly apply against the >> > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is >> > significantly better than what was in 2.4.21(-final). >> > >> > >> >> Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre >> patch to it. Apart from kdb, it is usually pretty clean. > > I don't think it's that easy. 2.4.22-pre has the O_DIRECT changes from sct. > Fixing XFS so that it compiles isn't that difficult (just some conflicts > in filemap.c) but it's much more work to not cripple XFS O_DIRECT support > due to these new locks. Without any changes all O_DIRECT I/O would happen > with i_sem held now. Ya, unfortunately, its not that easy. I gave it a run, and there were a handful of failed hunks, _alot_ of fuzz & offsets. thanks though. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo: http://netllama.ipfox.com 2:55pm up 10 days, 19:38, 1 user, load average: 0.29, 0.37, 0.34 From owner-linux-xfs@oss.sgi.com Thu Jun 26 00:08:22 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 00:08:44 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5Q78L2x010291 for ; Thu, 26 Jun 2003 00:08:22 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.54.149]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5Q78DiY015258 for ; Thu, 26 Jun 2003 00:08:15 -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 h5Q76vJA1494252 for ; Thu, 26 Jun 2003 17:06:57 +1000 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id h5Q76ufA1493013 for linux-xfs@oss.sgi.com; Thu, 26 Jun 2003 17:06:56 +1000 (EST) Date: Thu, 26 Jun 2003 17:06:56 +1000 (EST) From: Nathan Scott Message-Id: <200306260706.h5Q76ufA1493013@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs X-archive-position: 4473 X-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 Trivial warning fixup in log zeroing routine Date: Tue Jun 24 21:12:56 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:152022a cmd/xfsprogs/libxfs/rdwr.c - 1.20 Minor xfsprogs updates - add checks for pthreads lib, add missing stripe info init in libxfs_mount, testing script for large filesystems. Date: Thu Jun 26 00:05:59 PDT 2003 Workarea: snort.melbourne.sgi.com:/home/nathans/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:152091a cmd/xfstests/tools/ag-wipe - 1.1 - Test script for use with large loopback filesystems. cmd/xfstests/m4/package_pthread.m4 - 1.1 cmd/xfsprogs/m4/package_pthread.m4 - 1.1 - Macros for checking aspects of the installed pthreads library. cmd/xfsprogs/libxfs/init.c - 1.32 - Add missing stripe info initialisation in libxfs_mount. cmd/xfsprogs/configure.in - 1.29 cmd/xfsprogs/doc/CHANGES - 1.115 cmd/xfsprogs/include/builddefs.in - 1.36 cmd/xfsprogs/aclocal.m4 - 1.5 cmd/xfsprogs/m4/Makefile - 1.2 - Add in pthreads library checks. From owner-linux-xfs@oss.sgi.com Thu Jun 26 00:48:01 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 00:48:20 -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.9) with SMTP id h5Q7lx2x011277 for ; Thu, 26 Jun 2003 00:48:00 -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 h5Q7kpow030086; Thu, 26 Jun 2003 09:46:52 +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 h5Q7kpKx030083; Thu, 26 Jun 2003 09:46:51 +0200 X-Authentication-Warning: quasar.sif.it: matteo owned process doing -bs Date: Thu, 26 Jun 2003 09:46:51 +0200 (CEST) From: Matteo Centonza To: Net Llama! cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches In-Reply-To: <3EFA1A66.6060403@linux-sxs.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4474 X-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 Hi, On Wed, 25 Jun 2003, Net Llama! wrote: > On 06/25/03 14:22, Christoph Hellwig wrote: > > On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: > >> On Wed, 2003-06-25 at 15:56, Net Llama! wrote: > >> > Anyone know if/when the cvs snapshots will cleanly apply against the > >> > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is > >> > significantly better than what was in 2.4.21(-final). > >> > > >> > > >> > >> Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre > >> patch to it. Apart from kdb, it is usually pretty clean. > > > > I don't think it's that easy. 2.4.22-pre has the O_DIRECT changes from sct. > > Fixing XFS so that it compiles isn't that difficult (just some conflicts > > in filemap.c) but it's much more work to not cripple XFS O_DIRECT support > > due to these new locks. Without any changes all O_DIRECT I/O would happen > > with i_sem held now. > > Ya, unfortunately, its not that easy. I gave it a run, and there were a > handful of failed hunks, _alot_ of fuzz & offsets. thanks though. why not applying the acpi patch only? They have a pretty acpi-20030619-2.4.21.diff.gz on www.sf.net/projects/acpi Ciao, -m From owner-linux-xfs@oss.sgi.com Thu Jun 26 00:52:51 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 00:53:13 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5Q7qo2x011744 for ; Thu, 26 Jun 2003 00:52:50 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5Q7qo2l011743 for linux-xfs@oss.sgi.com; Thu, 26 Jun 2003 00:52:50 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5Q7ql2x011729 for ; Thu, 26 Jun 2003 00:52:47 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5Q7Ne67011087; Thu, 26 Jun 2003 00:23:40 -0700 Date: Thu, 26 Jun 2003 00:23:40 -0700 Message-Id: <200306260723.h5Q7Ne67011087@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 255] New: 2.5.72: kernel BUG at fs/xfs/pagebuf/page_buf.c:1288 X-Bugzilla-Reason: AssignedTo X-archive-position: 4475 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=255 Summary: 2.5.72: kernel BUG at fs/xfs/pagebuf/page_buf.c:1288 Product: Linux XFS Version: Current Platform: IA32 OS/Version: Linux Status: NEW Severity: critical Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: andreas.heilwagen@jamba.net CC: andreas.heilwagen@jamba.net I've found a bug in the XFS page buffer code which occured once a day with 2.5.66 and now every few days with 2.5.72. First the bug from the serial console which occured during high load: kernel BUG at fs/xfs/pagebuf/page_buf.c:1288! invalid operand: 0000 [#1] CPU: 1 EIP: 0060:[] Not tainted EFLAGS: 00010202 EIP is at bio_end_io_pagebuf+0xf8/0x154 eax: 01008009 ebx: f0497fd0 ecx: c14e86a8 edx: dcca3380 esi: f0497fdc edi: 00000001 ebp: f7ae9b84 esp: f7ae9b68 ds: 007b es: 007b ss: 0068 Process kswapd0 (pid: 11, threadinfo=f7ae8000 task=f7aed2e0) Stack: e1b91600 00000000 ce25bee0 c14e86a8 00000009 00001000 dcca3380 f7ae9ba0 c0156515 e1b91600 00001000 00000000 c8684ed0 cdeeb900 f7ae9bbc f8cbd1c5 e1b91600 00001000 00000000 cdeeb900 00000000 f7ae9bd8 c0156515 cdeeb900 Call Trace: [] bio_endio+0x51/0x5c [] clone_endio+0x9d/0xc4 [dm_mod] [] bio_endio+0x51/0x5c [] __end_that_request_first+0x107/0x1d8 [] end_that_request_first+0x17/0x1c [] scsi_end_request+0x29/0xc0 [] scsi_io_completion+0x1fa/0x460 [] sd_rw_intr+0x207/0x214 [] scsi_finish_command+0xc1/0xcc [] scsi_softirq+0xad/0xc4 [] do_softirq+0x6a/0xd0 [] do_IRQ+0x15a/0x174 [] common_interrupt+0x18/0x20 [] page_referenced+0x26/0xe0 [] shrink_list+0x11d/0x5e0 [] schedule+0x3f6/0x4e0 [] need_resched+0x27/0x32 [] shrink_cache+0x1b5/0x320 [] shrink_zone+0x7c/0x88 [] balance_pgdat+0xe1/0x174 [] kswapd+0x115/0x11c [] kswapd+0x0/0x11c [] autoremove_wake_function+0x0/0x3c [] autoremove_wake_function+0x0/0x3c [] kernel_thread_helper+0x5/0xc Code: 0f 0b 08 05 d4 29 44 c0 8b 4d 08 89 fa 89 f3 0f b7 41 18 39 <0>Kernel panic: Fatal exception in interrupt In interrupt handler - not syncing <0>Rebooting in 60 seconds.. I am in the unfortunate position to run a production server with 2.5.72 since the SuperMicro CSE-742S-500 has no working APIC support in the 2.4.x kernel series. Currently I have 2 XEON CPUs installed. 2.5.66 died once a day with "kernel panic: Aiee, killing interrupt handler" in fs/xfs/pagebuf/page_buf.c:1287. The reason is an "invalid operand:0000 #5" on CPU:0 with "EIP:0060:[] Not tainted". In one case slapd from the OpenLDAP package caused the crash. Now I run 2.5.72 and got the message above you see first. Furthermore the Arkeia backup hangs locally on the same volume every night. I have an 39320 Dual U320 SCSI controller in the machine with a Overland PowerLoader LTO-1 (17 slots) and a Infortrend IFT 6300-12 IDE-Raid with one 700G XFS volume configured. Please tell me what further tests I should conduct to help the analysis? ------- 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 Jun 26 04:38:39 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 04:38:58 -0700 (PDT) Received: from server1.bbb2.mdc-berlin.de (root@server1.bbb2.mdc-berlin.de [141.80.34.10]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5QBcb2x019351 for ; Thu, 26 Jun 2003 04:38:38 -0700 Received: from orion.bbb3.mdc-berlin.de (orion.bbb3.mdc-berlin.de [141.80.35.20]) by server1.bbb2.mdc-berlin.de (8.12.9/8.12.9) with ESMTP id h5QBcZeL007114 for ; Thu, 26 Jun 2003 13:38:35 +0200 (METDST) Received: from vilm.bioinf.mdc-berlin.de (IDENT:1203@vilm.bioinf.mdc-berlin.de [141.80.80.51]) by orion.bbb3.mdc-berlin.de (8.11.6/8.11.2) with ESMTP id h5QBcZX25005 for ; Thu, 26 Jun 2003 13:38:35 +0200 (MET DST) Subject: Can't mount xfs with log version=2 From: Juergen Rose To: linux-xfs@oss.sgi.com Content-Type: text/plain Organization: Max-Delbrueck-Zentrum Message-Id: <1056627514.12634.11.camel@vilm.bioinf.mdc-berlin.de> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.3.92 (Preview Release) Date: 26 Jun 2003 13:38:35 +0200 Content-Transfer-Encoding: 7bit X-archive-position: 4476 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rose@rz.uni-potsdam.de Precedence: bulk X-list: linux-xfs Hi, I have here a software raid device /dev/md/0. If I create the filesystem with: mkfs -t xfs -f /dev/md/0 I can mount the device, but I get a lot of "raid5: switching cache buffer size" warnings. If I create the filesystem with mkfs -t xrs -f -l version=2 /dev/md/0 I can't mount the device: I get: mount: wrong fs type, bad option, bad superblock on /dev/md/0, or too many mounted file systems I habe linux-2.4.21-ac2, which was configured with: CONFIG_XFS_FS=y # CONFIG_XFS_RT is not set # CONFIG_XFS_QUOTA is not set I would appreciate any hint very much. Please answer also to my email I don't follow this list. Regards Juergen -- Juergen Rose Max-Delbrueck-Zentrum From owner-linux-xfs@oss.sgi.com Thu Jun 26 04:51:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 04:51:29 -0700 (PDT) Received: from smtpzilla3.xs4all.nl (smtpzilla3.xs4all.nl [194.109.127.139]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5QBpE2x019956 for ; Thu, 26 Jun 2003 04:51:15 -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 h5QBpCX4069179; Thu, 26 Jun 2003 13:51:12 +0200 (CEST) Message-Id: <4.3.2.7.2.20030626134829.035221c8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 26 Jun 2003 13:50:35 +0200 To: Juergen Rose , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Can't mount xfs with log version=2 In-Reply-To: <1056627514.12634.11.camel@vilm.bioinf.mdc-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 4477 X-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 At 13:38 26-6-2003 +0200, Juergen Rose wrote: >Hi, > >I have here a software raid device /dev/md/0. If I create the filesystem >with: > mkfs -t xfs -f /dev/md/0 >I can mount the device, but I get a lot of "raid5: switching cache >buffer size" warnings. If I create the filesystem with > mkfs -t xrs -f -l version=2 /dev/md/0 >I can't mount the device: I get: > >mount: wrong fs type, bad option, bad superblock on /dev/md/0, > or too many mounted file systems It probably needs to be mounted with a larger buffer size. Try mount -o logbsize=64k /dev/foo /mnt/foo The version2 log automaticaly switches to a larger databuffer size for striping purposes. However if it is larger then 32k a mount option must be specified. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Thu Jun 26 06:26:57 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 06:27:17 -0700 (PDT) Received: from linux-sxs.org (dhcp065-024-128-253.columbus.rr.com [65.24.128.253]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5QDQt2x022384 for ; Thu, 26 Jun 2003 06:26:56 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.9/8.12.9) with ESMTP id h5QDQoH7007242; Thu, 26 Jun 2003 09:26:50 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.9/8.12.9/Submit) with ESMTP id h5QDQopH018578; Thu, 26 Jun 2003 09:26:50 -0400 Date: Thu, 26 Jun 2003 09:26:50 -0400 (EDT) From: Net Llama! To: Matteo Centonza cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches 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.34 X-archive-position: 4478 X-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 On Thu, 26 Jun 2003, Matteo Centonza wrote: > Hi, > > On Wed, 25 Jun 2003, Net Llama! wrote: > > > On 06/25/03 14:22, Christoph Hellwig wrote: > > > On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: > > >> On Wed, 2003-06-25 at 15:56, Net Llama! wrote: > > >> > Anyone know if/when the cvs snapshots will cleanly apply against the > > >> > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is > > >> > significantly better than what was in 2.4.21(-final). > > >> > > > >> > > > >> > > >> Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre > > >> patch to it. Apart from kdb, it is usually pretty clean. > > > > > > I don't think it's that easy. 2.4.22-pre has the O_DIRECT changes from sct. > > > Fixing XFS so that it compiles isn't that difficult (just some conflicts > > > in filemap.c) but it's much more work to not cripple XFS O_DIRECT support > > > due to these new locks. Without any changes all O_DIRECT I/O would happen > > > with i_sem held now. > > > > Ya, unfortunately, its not that easy. I gave it a run, and there were a > > handful of failed hunks, _alot_ of fuzz & offsets. thanks though. > > > why not applying the acpi patch only? > > They have a pretty acpi-20030619-2.4.21.diff.gz on www.sf.net/projects/acpi What do you mean by 'only'? That is the patch that i tried to apply, however i don't even think its neccesary in 2.4.22-pre1, because its already been updated with the same patches. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Thu Jun 26 06:58:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 06:58:26 -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.9) with SMTP id h5QDw62x029109 for ; Thu, 26 Jun 2003 06:58:07 -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 h5QDv1ow012105; Thu, 26 Jun 2003 15:57:01 +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 h5QDv1fE012102; Thu, 26 Jun 2003 15:57:01 +0200 X-Authentication-Warning: quasar.sif.it: matteo owned process doing -bs Date: Thu, 26 Jun 2003 15:57:01 +0200 (CEST) From: Matteo Centonza To: Net Llama! cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 4479 X-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 Hi, > > On Wed, 25 Jun 2003, Net Llama! wrote: > > > > > On 06/25/03 14:22, Christoph Hellwig wrote: > > > > On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: > > > >> On Wed, 2003-06-25 at 15:56, Net Llama! wrote: > > > >> > Anyone know if/when the cvs snapshots will cleanly apply against the > > > >> > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is > > > >> > significantly better than what was in 2.4.21(-final). > > > >> > > > > >> > > > > >> > > > >> Your best bet is to take the xfs cvs kernel, and apply the 2.4.22-pre > > > >> patch to it. Apart from kdb, it is usually pretty clean. > > > > > > > > I don't think it's that easy. 2.4.22-pre has the O_DIRECT changes from sct. > > > > Fixing XFS so that it compiles isn't that difficult (just some conflicts > > > > in filemap.c) but it's much more work to not cripple XFS O_DIRECT support > > > > due to these new locks. Without any changes all O_DIRECT I/O would happen > > > > with i_sem held now. > > > > > > Ya, unfortunately, its not that easy. I gave it a run, and there were a > > > handful of failed hunks, _alot_ of fuzz & offsets. thanks though. > > > > > > why not applying the acpi patch only? > > > > They have a pretty acpi-20030619-2.4.21.diff.gz on www.sf.net/projects/acpi > > What do you mean by 'only'? That is the patch that i tried to apply, > however i don't even think its neccesary in 2.4.22-pre1, because its > already been updated with the same patches. as i've understood it, if you're interested only in new acpi features of 2.4.22-pre1 (and of course in XFS), you can download the current XFS cvs kernel (2.4.21 based) and apply the latest acpi patch (against 2.4.21). This merge should have the acpi bits you want. You have to resolve 1 trivial reject (induced by KDB) in arch/i386/kernel/io_apic.c Ciao, -m From owner-linux-xfs@oss.sgi.com Thu Jun 26 07:00:36 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 07:00:40 -0700 (PDT) Received: from linux-sxs.org (dhcp065-024-128-253.columbus.rr.com [65.24.128.253]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5QE0Z2x029575 for ; Thu, 26 Jun 2003 07:00:35 -0700 Received: from linux-sxs.org (localhost [127.0.0.1]) by linux-sxs.org (8.12.9/8.12.9) with ESMTP id h5QE0TH7030550; Thu, 26 Jun 2003 10:00:29 -0400 Received: from localhost (netllama@localhost) by linux-sxs.org (8.12.9/8.12.9/Submit) with ESMTP id h5QE0TKn032404; Thu, 26 Jun 2003 10:00:29 -0400 Date: Thu, 26 Jun 2003 10:00:29 -0400 (EDT) From: Net Llama! To: Matteo Centonza cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches 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.34 X-archive-position: 4480 X-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 On Thu, 26 Jun 2003, Matteo Centonza wrote: > > > On Wed, 25 Jun 2003, Net Llama! wrote: > > > > On 06/25/03 14:22, Christoph Hellwig wrote: > > > > > On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: > > > > >> On Wed, 2003-06-25 at 15:56, Net Llama! wrote: > > > > >> > Anyone know if/when the cvs snapshots will cleanly apply against the > > > > >> > 2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is > > > > >> > significantly better than what was in 2.4.21(-final). > > > > >> > > > > > > > why not applying the acpi patch only? > > > > > > They have a pretty acpi-20030619-2.4.21.diff.gz on www.sf.net/projects/acpi > > > > What do you mean by 'only'? That is the patch that i tried to apply, > > however i don't even think its neccesary in 2.4.22-pre1, because its > > already been updated with the same patches. > > as i've understood it, if you're interested only in new acpi > features of 2.4.22-pre1 (and of course in XFS), you can download the > current XFS cvs kernel (2.4.21 based) and apply the latest acpi > patch (against 2.4.21). > > This merge should have the acpi bits you want. > > You have to resolve 1 trivial reject (induced by KDB) in > arch/i386/kernel/io_apic.c How trivial are we talking about? My C is about as good as 'hello world' :) -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Lonni J Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo http://netllama.ipfox.com From owner-linux-xfs@oss.sgi.com Thu Jun 26 18:49:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Jun 2003 18:49:21 -0700 (PDT) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5R1n62x010797 for ; Thu, 26 Jun 2003 18:49:06 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with SMTP id h5R1mxiY027813 for ; Thu, 26 Jun 2003 18:49: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 LAA14090; Fri, 27 Jun 2003 11:47:43 +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 h5R1lg3K043733; Fri, 27 Jun 2003 11:47:43 +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 h5R1laoo001224; Fri, 27 Jun 2003 11:47:36 +1000 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.9/8.12.9/Debian-3) id h5R1lZ3w001222; Fri, 27 Jun 2003 11:47:35 +1000 Date: Fri, 27 Jun 2003 11:47:35 +1000 From: Nathan Scott To: Juergen Rose Cc: linux-xfs@oss.sgi.com Subject: Re: Can't mount xfs with log version=2 Message-ID: <20030627014735.GD894@frodo> References: <1056627514.12634.11.camel@vilm.bioinf.mdc-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1056627514.12634.11.camel@vilm.bioinf.mdc-berlin.de> User-Agent: Mutt/1.5.3i X-archive-position: 4481 X-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 On Thu, Jun 26, 2003 at 01:38:35PM +0200, Juergen Rose wrote: > Hi, > > I have here a software raid device /dev/md/0. If I create the filesystem > with: > mkfs -t xfs -f /dev/md/0 > I can mount the device, but I get a lot of "raid5: switching cache > buffer size" warnings. If I create the filesystem with > mkfs -t xrs -f -l version=2 /dev/md/0 > > I can't mount the device: I get: > > mount: wrong fs type, bad option, bad superblock on /dev/md/0, > or too many mounted file systems What messages do you see in /var/log/messages when the mount fails at this point? > I habe linux-2.4.21-ac2, which was configured with: > CONFIG_XFS_FS=y > # CONFIG_XFS_RT is not set > # CONFIG_XFS_QUOTA is not set > > I would appreciate any hint very much. Please answer also to my email I > don't follow this list. > cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Jun 27 00:03:44 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 00:03:49 -0700 (PDT) Received: from khe-mailhub1.eigner.com (khe-mailhub1.eigner.com [194.120.231.246]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5R73g2x021146 for ; Fri, 27 Jun 2003 00:03:43 -0700 Received: from eigner.com (unknown [194.120.231.18]) by khe-mailhub1.eigner.com (Postfix) with ESMTP id AF7BC248; Fri, 27 Jun 2003 09:03:18 +0200 (CEST) Message-ID: <3EFBEC39.8070609@eigner.com> Date: Fri, 27 Jun 2003 09:03:21 +0200 From: Klaus Strebel Organization: EIGNER Germany GmbH User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: de, en MIME-Version: 1.0 To: "Net Llama!" , linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-MailScanner-Information: Please contact the ISP for more information X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-102.1, required 5, EMAIL_ATTRIBUTION, IN_REP_TO, REFERENCES, REPLY_WITH_QUOTES, USER_AGENT_MOZILLA_UA, USER_IN_WHITELIST, X_ACCEPT_LANG) X-archive-position: 4482 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: klaus.strebel@eigner.com Precedence: bulk X-list: linux-xfs Net Llama! wrote: > On Thu, 26 Jun 2003, Matteo Centonza wrote: > >>>>On Wed, 25 Jun 2003, Net Llama! wrote: >>>> >>>>>On 06/25/03 14:22, Christoph Hellwig wrote: >>>>> >>>>>>On Wed, Jun 25, 2003 at 04:19:08PM -0500, Steve Lord wrote: >>>>>> >>>>>>>On Wed, 2003-06-25 at 15:56, Net Llama! wrote: >>>>>>> >>>>>>>>Anyone know if/when the cvs snapshots will cleanly apply against the >>>>>>>>2.4.22-pre1 kernel? I'd really like to use it, as the acpi support is >>>>>>>>significantly better than what was in 2.4.21(-final). >>>>>>>> >>>> >>>>why not applying the acpi patch only? >>>> >>>>They have a pretty acpi-20030619-2.4.21.diff.gz on www.sf.net/projects/acpi >>> >>>What do you mean by 'only'? That is the patch that i tried to apply, >>>however i don't even think its neccesary in 2.4.22-pre1, because its >>>already been updated with the same patches. >> >>as i've understood it, if you're interested only in new acpi >>features of 2.4.22-pre1 (and of course in XFS), you can download the >>current XFS cvs kernel (2.4.21 based) and apply the latest acpi >>patch (against 2.4.21). >> >>This merge should have the acpi bits you want. >> >>You have to resolve 1 trivial reject (induced by KDB) in >>arch/i386/kernel/io_apic.c > > > How trivial are we talking about? My C is about as good as 'hello world' > :) > Its just adding 'include ' and you don't need to be a C master to find out where from the .rej file ;-) (better be vi-master, hahaha). Ciao Klaus -- Klaus Strebel UNIX-Engineer klaus.strebel@eigner.com EIGNER - Precision Lifecycle Management - From owner-linux-xfs@oss.sgi.com Fri Jun 27 00:07:27 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 00:07:51 -0700 (PDT) Received: from hob.acsalaska.net (hob.slb.nwc.acsalaska.net [209.112.155.42]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5R77Q2x021576 for ; Fri, 27 Jun 2003 00:07:27 -0700 Received: from erbenson.alaska.net (120-pm30.nwc.alaska.net [209.112.158.120]) by hob.acsalaska.net (8.12.9/8.12.9) with ESMTP id h5R77PHv007055 for ; Thu, 26 Jun 2003 23:07:25 -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 E93923A07 for ; Thu, 26 Jun 2003 23:07:23 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 816DA40FF44; Thu, 26 Jun 2003 23:07:23 -0800 (AKDT) Date: Thu, 26 Jun 2003 23:07:23 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches Message-ID: <20030627070723.GM1363@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="iKKZt69u2Wx/rspf" 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-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4483 X-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 --iKKZt69u2Wx/rspf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 26, 2003 at 10:00:29AM -0400, Net Llama! wrote: > > You have to resolve 1 trivial reject (induced by KDB) in > > arch/i386/kernel/io_apic.c >=20 > How trivial are we talking about? My C is about as good as 'hello world' > :) then use the xfs split patches against a mainline 2.4.21, and don't apply the kdb split patch. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --iKKZt69u2Wx/rspf 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 iEYEARECAAYFAj777SsACgkQJKx7GixEevw6EACeMWhZfMbJXysGr05VKlMKb5SW pswAn1bmhrQYzPugJDbPTYmP0xGflFN9 =rk+u -----END PGP SIGNATURE----- --iKKZt69u2Wx/rspf-- From owner-linux-xfs@oss.sgi.com Fri Jun 27 03:52:55 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 03:53:13 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RAqt2x030366 for ; Fri, 27 Jun 2003 03:52:55 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RAqt8n030365 for linux-xfs@oss.sgi.com; Fri, 27 Jun 2003 03:52:55 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RAqr2x030353 for ; Fri, 27 Jun 2003 03:52:53 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RAjbDf030315; Fri, 27 Jun 2003 03:45:37 -0700 Date: Fri, 27 Jun 2003 03:45:37 -0700 Message-Id: <200306271045.h5RAjbDf030315@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 256] New: Strange owner change using fakeroot X-Bugzilla-Reason: AssignedTo X-archive-position: 4484 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=256 Summary: Strange owner change using fakeroot Product: Linux XFS Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: major Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: duck@duckcorp.org I'm using kernel 2.4.21 with XFS patch ck3 from Con Kolivas (http://members.optusnet.com.au/ckolivas/kernel/). I'm packaging some softwares for the Debian distribution. As it is cleaner and more secure, i am using fakeroot to simulate root permissions over my build directory. So i am using a normal user, and the build directory and ALL the files and subdirectories inside are owned by this user. At the end of the packaging process, i see an error "permission denied" which only happen when building on my xfs partition. Looking for explanation, i found files previously owned by the normal user now owned by root !!! It happens either when doing su or when directly login with the normal user account. Thx for ur help ------- 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 Jun 27 06:21:31 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 06:21:50 -0700 (PDT) Received: from hermes.acsalaska.net (hermes.slb.nwc.acsalaska.net [209.112.155.38]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5RDLU2x004200 for ; Fri, 27 Jun 2003 06:21:30 -0700 Received: from erbenson.alaska.net (120-pm30.nwc.alaska.net [209.112.158.120]) by hermes.acsalaska.net (8.12.9/8.12.9) with ESMTP id h5RB5Uo0014433 for ; Fri, 27 Jun 2003 03:05:30 -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 BCEF73A07 for ; Fri, 27 Jun 2003 03:05:29 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 47EE440FF44; Fri, 27 Jun 2003 03:05:29 -0800 (AKDT) Date: Fri, 27 Jun 2003 03:05:29 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: [Bug 256] New: Strange owner change using fakeroot Message-ID: <20030627110529.GA1788@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200306271045.h5RAjbDf030315@oss.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <200306271045.h5RAjbDf030315@oss.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-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-archive-position: 4485 X-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 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2003 at 03:45:37AM -0700, bugzilla-daemon@oss.sgi.com wrote: > http://oss.sgi.com/bugzilla/show_bug.cgi?id=3D256 >=20 > Summary: Strange owner change using fakeroot > Product: Linux XFS > Version: unspecified > Platform: All > OS/Version: Linux > Status: NEW > Severity: major > Priority: High > Component: XFS kernel code > AssignedTo: xfs-master@oss.sgi.com > ReportedBy: duck@duckcorp.org >=20 >=20 > I'm using kernel 2.4.21 with XFS patch ck3 from Con Kolivas > (http://members.optusnet.com.au/ckolivas/kernel/). > I'm packaging some softwares for the Debian distribution. > As it is cleaner and more secure, i am using fakeroot to simulate root > permissions over my build directory. > So i am using a normal user, and the build directory and ALL the files and > subdirectories inside are owned by this user. > At the end of the packaging process, i see an error "permission denied" w= hich > only happen when building on my xfs partition. > Looking for explanation, i found files previously owned by the normal use= r now > owned by root !!! > It happens either when doing su or when directly login with the normal us= er account. it appears the default for the fs/xfs/restrict_chown sysctl is 0 in 2.4.21 split patches. this is wrong. for a quick workaround run: sysctl -w fs/xfs/restrict_chown=3D1 --=20 Ethan Benson http://www.alaska.net/~erbenson/ --bg08WKrSYDhXBjb5 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 iEYEARECAAYFAj78JPkACgkQJKx7GixEevyvYACfd7keu26ZPxeWSQ5k7IAhG3T+ H5EAnjVg90Hnwr4cJVSgkKh0rOxosG/8 =JMTj -----END PGP SIGNATURE----- --bg08WKrSYDhXBjb5-- From owner-linux-xfs@oss.sgi.com Fri Jun 27 07:52:56 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 07:53:11 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5REqu2x006007 for ; Fri, 27 Jun 2003 07:52:56 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5REqu0m006006 for linux-xfs@oss.sgi.com; Fri, 27 Jun 2003 07:52:56 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5REqs31005992 for ; Fri, 27 Jun 2003 07:52:54 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5REFoGh005123; Fri, 27 Jun 2003 07:15:50 -0700 Date: Fri, 27 Jun 2003 07:15:50 -0700 Message-Id: <200306271415.h5REFoGh005123@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 256] Strange owner change using fakeroot X-Bugzilla-Reason: AssignedTo X-archive-position: 4486 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=256 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From sandeen@sgi.com 2003-27-06 07:15 PDT ------- As Ethan wrote on the list: ============== it appears the default for the fs/xfs/restrict_chown sysctl is 0 in 2.4.21 split patches. this is wrong. for a quick workaround run: sysctl -w fs/xfs/restrict_chown=1 ============== this has been fixed in CVS. If the above workaround, or the CVS code does not fix it for you, please reopen this bug. ------- 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 Jun 27 12:33:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 12:33:24 -0700 (PDT) Received: from imf20aec.bellsouth.net (imf20aec.mail.bellsouth.net [205.152.59.68]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5RJX72x011411 for ; Fri, 27 Jun 2003 12:33:08 -0700 Received: from tiger2 ([66.156.0.98]) by imf20aec.bellsouth.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with SMTP id <20030627193302.SLMI24789.imf20aec.bellsouth.net@tiger2> for ; Fri, 27 Jun 2003 15:33:02 -0400 Date: Fri, 27 Jun 2003 15:41:24 -0400 From: Greg Freemyer Subject: XFSDUMP Warning To: xfs mailing list Mime-Version: 1.0 Organization: Norcross Group X-Mailer: GoldMine [6.00.21021] Content-Type: Text/plain Message-Id: <20030627193302.SLMI24789.imf20aec.bellsouth.net@tiger2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id h5RJX92x011412 X-archive-position: 4487 X-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 Last night I got an XFSDUMP warning I have never seen before: WARNING: getbmapx 1 ino 132 mode 0x000081f6 offset 0 failed: Unknown error 990 This was with XFS 1.2 as included in SuSE 8.2 (2.4.20 kernel) Does this mean I have a problem? Is it safe to assume the single file was skipped, but got backed up the next xfsdump run? >> Full XFS output /sbin/xfsdump: using file dump (drive_simple) strategy /sbin/xfsdump: version 2.2.6 (dump format 3.0) - Running single-threaded /sbin/xfsdump: level 2 incremental dump of DualStore2000:/data_snap based on level 1 dump begun Wed Jun 25 01:15:03 2003 /sbin/xfsdump: dump date: Thu Jun 26 01:15:03 2003 /sbin/xfsdump: session id: 846acc6e-1234-405f-95c7-941f81cc8c68 /sbin/xfsdump: session label: "/data" /sbin/xfsdump: ino map phase 1: skipping (no subtrees specified) /sbin/xfsdump: ino map phase 2: constructing initial dump list /sbin/xfsdump: ino map phase 3: pruning unneeded subtrees /sbin/xfsdump: ino map phase 4: estimating dump size /sbin/xfsdump: ino map phase 5: skipping (only one dump stream) /sbin/xfsdump: ino map construction complete /sbin/xfsdump: estimated dump size: 835461760 bytes /sbin/xfsdump: creating dump session media file 0 (media 0, file 0) /sbin/xfsdump: dumping ino map /sbin/xfsdump: dumping directories /sbin/xfsdump: dumping non-directory files /sbin/xfsdump: WARNING: getbmapx 1 ino 132 mode 0x000081f6 offset 0 failed: Unknown error 990 /sbin/xfsdump: ending media file /sbin/xfsdump: media file size 21640 bytes /sbin/xfsdump: dump size (non-dir files) : 0 bytes /sbin/xfsdump: dump complete: 6 seconds elapsed /sbin/xfsdump: Dump Status: SUCCESS >> Thanks Greg -- Greg Freemyer From owner-linux-xfs@oss.sgi.com Fri Jun 27 12:52:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 12:53:05 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RJqw2x012047 for ; Fri, 27 Jun 2003 12:52:58 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RJqw0s012046 for linux-xfs@oss.sgi.com; Fri, 27 Jun 2003 12:52:58 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RJqt39012004 for ; Fri, 27 Jun 2003 12:52:56 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RJchtf011895; Fri, 27 Jun 2003 12:38:43 -0700 Date: Fri, 27 Jun 2003 12:38:43 -0700 Message-Id: <200306271938.h5RJchtf011895@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 213] XFS kernel patch breaks kdemultimedia X-Bugzilla-Reason: AssignedTo X-archive-position: 4489 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=213 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From sandeen@sgi.com 2003-27-06 12:38 PDT ------- This is a KDE bug, not an xfs bug. Why kmultimedia is peering into kernel header files, I have no idea. ------- 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 Jun 27 12:52:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 12:53:05 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RJqw2x012048 for ; Fri, 27 Jun 2003 12:52:58 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RJqwoD012044 for linux-xfs@oss.sgi.com; Fri, 27 Jun 2003 12:52:58 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RJqt35012004 for ; Fri, 27 Jun 2003 12:52:55 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RJf6pY011928; Fri, 27 Jun 2003 12:41:06 -0700 Date: Fri, 27 Jun 2003 12:41:06 -0700 Message-Id: <200306271941.h5RJf6pY011928@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 221] reload xfs/dmapi module crash X-Bugzilla-Reason: AssignedTo X-archive-position: 4490 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=221 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Additional Comments From sandeen@sgi.com 2003-27-06 12:41 PDT ------- Dean fixed this one & checked it in, but the bug stayed open. ------- 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 Jun 27 12:52:58 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 12:53:05 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RJqw2x012049 for ; Fri, 27 Jun 2003 12:52:58 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RJqwuR012043 for linux-xfs@oss.sgi.com; Fri, 27 Jun 2003 12:52:58 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5RJqt31012004 for ; Fri, 27 Jun 2003 12:52:55 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5RJUpC7011396; Fri, 27 Jun 2003 12:30:51 -0700 Date: Fri, 27 Jun 2003 12:30:51 -0700 Message-Id: <200306271930.h5RJUpC7011396@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 234] test email X-Bugzilla-Reason: AssignedTo X-archive-position: 4488 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=234 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From sandeen@sgi.com 2003-27-06 12:30 PDT ------- Hey look, I'm closing a bug... :) ------- 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 Jun 27 19:14:03 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Jun 2003 19:14:24 -0700 (PDT) Received: from mail.vasoftware.com (mail@mail.vasoftware.com [198.186.202.175]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5S2E32x027669 for ; Fri, 27 Jun 2003 19:14:03 -0700 Received: from adsl-67-123-173-22.dsl.sntc01.pacbell.net ([67.123.173.22] helo=linux-sxs.org) by mail.vasoftware.com with asmtp (Cipher TLSv1:RC4-MD5:128) (Exim 3.31-VA-mm2 #1 (Debian)) id 19W5E0-00048N-00 by VAauthid with fixed_plain; Fri, 27 Jun 2003 19:14:00 -0700 Message-ID: <3EFCF9DE.60008@linux-sxs.org> Date: Fri, 27 Jun 2003 19:13:50 -0700 From: "Net Llama!" Organization: HAL-III User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ethan Benson CC: linux-xfs@oss.sgi.com Subject: Re: 2.4.22-pre patches References: <20030627070723.GM1363@plato.local.lan> In-Reply-To: <20030627070723.GM1363@plato.local.lan> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 4491 X-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 On 06/27/03 00:07, Ethan Benson wrote: > On Thu, Jun 26, 2003 at 10:00:29AM -0400, Net Llama! wrote: >> > You have to resolve 1 trivial reject (induced by KDB) in >> > arch/i386/kernel/io_apic.c >> >> How trivial are we talking about? My C is about as good as 'hello world' >> :) > > then use the xfs split patches against a mainline 2.4.21, and don't > apply the kdb split patch. OK, i'm trying that and not having much luck: # patch -p1 --dry-run < ../xfs-2.4.21-split-kernel patching file mm/filemap.c Hunk #2 FAILED at 2960. Hunk #3 FAILED at 2981. Hunk #4 FAILED at 3159. Hunk #5 succeeded at 3282 with fuzz 1 (offset 86 lines). 3 out of 5 hunks FAILED -- saving rejects to file mm/filemap.c.rej -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ L. Friedman netllama@linux-sxs.org Linux Step-by-step & TyGeMo: http://netllama.ipfox.com 7:10pm up 12 days, 23:53, 1 user, load average: 0.12, 0.18, 0.42 From owner-linux-xfs@oss.sgi.com Sat Jun 28 00:10:18 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Jun 2003 00:10:40 -0700 (PDT) Received: from malik.acsalaska.net (malik.slb.nwc.acsalaska.net [209.112.155.41]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5S7AH2x032219 for ; Sat, 28 Jun 2003 00:10:17 -0700 Received: from erbenson.alaska.net (178-pm15.nwc.alaska.net [209.112.141.178]) by malik.acsalaska.net (8.12.9/8.12.9) with ESMTP id h5S7ADpc088837 for ; Fri, 27 Jun 2003 23:10:15 -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 460A63A0C for ; Fri, 27 Jun 2003 23:10:12 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id D4BFA40FF44; Fri, 27 Jun 2003 23:10:11 -0800 (AKDT) Date: Fri, 27 Jun 2003 23:10:11 -0800 From: Ethan Benson To: xfs mailing list Subject: Re: XFSDUMP Warning Message-ID: <20030628071011.GB1788@plato.local.lan> Mail-Followup-To: xfs mailing list References: <20030627193302.SLMI24789.imf20aec.bellsouth.net@tiger2> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <20030627193302.SLMI24789.imf20aec.bellsouth.net@tiger2> 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-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4492 X-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 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2003 at 03:41:24PM -0400, Greg Freemyer wrote: >=20 > Last night I got an XFSDUMP warning I have never seen before: >=20 > WARNING: getbmapx 1 ino 132 mode 0x000081f6 offset 0 failed: Unknown e= rror 990 >=20 > This was with XFS 1.2 as included in SuSE 8.2 (2.4.20 kernel) >=20 > Does this mean I have a problem? >=20 > Is it safe to assume the single file was skipped, but got backed up the n= ext xfsdump run? no, errno 990 is EFSCORRUPTED, it only occurs when filesystem corruption is detected. you should umount the relevant filesystem and run xfs_repair on it. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --RASg3xLB4tUQ4RcS 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 iEYEARECAAYFAj79P1MACgkQJKx7GixEevxUAACdGUhQAQUPAeg9hgMEXD0bOjDy My0AmwdF/wgrFvfX+vnkssMcQuU7ulX6 =c1Cq -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS-- From owner-linux-xfs@oss.sgi.com Sat Jun 28 02:15:19 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Jun 2003 02:15:33 -0700 (PDT) Received: from quail.cita.utoronto.ca (quail.cita.utoronto.ca [128.100.76.6]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5S9FI2x002443 for ; Sat, 28 Jun 2003 02:15:19 -0700 Received: from cita.utoronto.ca (falcon.cita.utoronto.ca [128.100.76.51]) by quail.cita.utoronto.ca (8.12.8/8.12.8) with ESMTP id h5S9FDKX014624 for ; Sat, 28 Jun 2003 05:15:13 -0400 Received: from falcon.cita.utoronto.ca (localhost [127.0.0.1]) by cita.utoronto.ca (8.12.8/8.12.8) with ESMTP id h5S9FD9a025063 for ; Sat, 28 Jun 2003 05:15:13 -0400 Received: (from rjh@localhost) by falcon.cita.utoronto.ca (8.12.8/8.12.8/Submit) id h5S9FDdO025061 for linux-xfs@oss.sgi.com; Sat, 28 Jun 2003 05:15:13 -0400 Date: Sat, 28 Jun 2003 05:15:13 -0400 From: Robin Humble To: linux-xfs@oss.sgi.com Subject: 2.5 cvs confused? Message-ID: <20030628091513.GA25055@falcon.cita.utoronto.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-archive-position: 4493 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rjh@cita.utoronto.ca Precedence: bulk X-list: linux-xfs 2.5 cvs seems to have turned into the 2.4 tree: % head linux-2.5-xfs/linux/Makefile VERSION = 2 PATCHLEVEL = 4 SUBLEVEL = 21 EXTRAVERSION = -xfs ... perhaps it's a plot by SCO? :-) cheers, robin From owner-linux-xfs@oss.sgi.com Sat Jun 28 02:23:50 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Jun 2003 02:23:54 -0700 (PDT) Received: from hob.acsalaska.net (hob.slb.nwc.acsalaska.net [209.112.155.42]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5S9Nn2x004259 for ; Sat, 28 Jun 2003 02:23:50 -0700 Received: from erbenson.alaska.net (178-pm15.nwc.alaska.net [209.112.141.178]) by hob.acsalaska.net (8.12.9/8.12.9) with ESMTP id h5S9NlOT078951 for ; Sat, 28 Jun 2003 01:23:48 -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 451C53A0C for ; Sat, 28 Jun 2003 01:23:45 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id 0471940FF44; Sat, 28 Jun 2003 01:23:44 -0800 (AKDT) Date: Sat, 28 Jun 2003 01:23:44 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: [Bug 256] Strange owner change using fakeroot Message-ID: <20030628092344.GA21506@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200306271415.h5REFoGh005123@oss.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Yylu36WmvOXNoKYn" Content-Disposition: inline In-Reply-To: <200306271415.h5REFoGh005123@oss.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-Scanned-By: MIMEDefang 2.31 (www . roaringpenguin . com / mimedefang) X-archive-position: 4494 X-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 --Yylu36WmvOXNoKYn Content-Type: multipart/mixed; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jun 27, 2003 at 07:15:50AM -0700, bugzilla-daemon@oss.sgi.com wrote: > http://oss.sgi.com/bugzilla/show_bug.cgi?id=3D256 >=20 >=20 > sandeen@sgi.com changed: >=20 > What |Removed |Added > -------------------------------------------------------------------------= --- > Status|NEW |RESOLVED > Resolution| |FIXED >=20 >=20 >=20 >=20 > ------- Additional Comments From sandeen@sgi.com 2003-27-06 07:15 PDT --= ----- > As Ethan wrote on the list: >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > it appears the default for the fs/xfs/restrict_chown sysctl is 0 in > 2.4.21 split patches. >=20 > this is wrong. >=20 > for a quick workaround run: >=20 > sysctl -w fs/xfs/restrict_chown=3D1 >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > this has been fixed in CVS. If the above workaround, or the CVS code > does not fix it for you, please reopen this bug. for those who want to stick with split patches here is the relevant patch from cvs (attached). note that the default for irix_setgid was 1 not 0 as well. (im not sure what that one does, i think its basically just the bsdgroups mount option). --=20 Ethan Benson http://www.alaska.net/~erbenson/ --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xfs_globals.c.diff" Content-Transfer-Encoding: quoted-printable --- linux.orig/fs/xfs/linux/xfs_globals.c Sun Jun 22 20:00:02 2003 +++ linux/fs/xfs/linux/xfs_globals.c Fri Jun 27 23:59:20 2003 @@ -50,7 +50,17 @@ * Tunable XFS parameters. xfs_params is required even when CONFIG_SYSCTL= =3Dn, * other XFS code uses these values. */ -xfs_param_t xfs_params =3D { 128, 32, 0, 1, 0, 0, 3, 30 * HZ, 0 }; +xfs_param_t xfs_params =3D {=20 + refcache_size: 128, + refcache_purge: 32, + restrict_chown: 1, + sgid_inherit: 0, + symlink_mode: 0, + panic_mask: 0, + error_level: 3, + sync_interval: 30 * HZ, + stats_clear: 0, +}; =20 /* * Global system credential structure. --Dxnq1zWXvFF0Q93v-- --Yylu36WmvOXNoKYn 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 iEYEARECAAYFAj79XqAACgkQJKx7GixEevyhBgCeOc17HrfvOeli+hGYA5D4aRaW QBwAn3F7jyMdZ5irNiPb/RbaeFu4kk/K =x4WY -----END PGP SIGNATURE----- --Yylu36WmvOXNoKYn-- From owner-linux-xfs@oss.sgi.com Sat Jun 28 14:51:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Jun 2003 14:51:30 -0700 (PDT) Received: from wilma.widomaker.com (root@wilma.widomaker.com [204.17.220.5]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5SLpC2x017922 for ; Sat, 28 Jun 2003 14:51:13 -0700 Received: from [209.96.185.121] (helo=escape.shannon.net) by wilma.widomaker.com with esmtp (Exim 3.36 #1) id 19WNbC-000MmG-00 for linux-xfs@oss.sgi.com; Sat, 28 Jun 2003 17:51:10 -0400 Received: from daydream.shannon.net (IDENT:0@daydream.shannon.net [192.168.1.10]) by escape.shannon.net (8.11.6/8.11.3) with ESMTP id h5SLcEq21653 for ; Sat, 28 Jun 2003 17:38:14 -0400 (EDT) Received: from daydream.shannon.net (IDENT:1000@localhost [127.0.0.1]) by daydream.shannon.net (8.12.8/8.11.4) with ESMTP id h5SLcEXh012682 for ; Sat, 28 Jun 2003 17:38:14 -0400 Received: (from shannon@localhost) by daydream.shannon.net (8.12.8/8.12.4/Submit) id h5SLcE8b012681 for linux-xfs@oss.sgi.com; Sat, 28 Jun 2003 17:38:14 -0400 Date: Sat, 28 Jun 2003 17:38:14 -0400 From: Charles Shannon Hendrix To: linux-xfs@oss.sgi.com Subject: library errors building XFS tools... Message-ID: <20030628213811.GA5436@widomaker.com> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Message-Flag: Microsoft Loves You! User-Agent: Mutt/1.5.4i X-archive-position: 4495 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: shannon@widomaker.com Precedence: bulk X-list: linux-xfs Why does the xfs tool build mix library files between /lib and /usr/lib? The shared objects in /lib, the libtool stuff in /usr/lib... this seems to cause grief when building other xfs programs. It would be much nicer if you could just give a single prefix for those who want to store things in /usr/local, or somewhere else. In any case, I build attr and xfsprogs using the defaults and linking in xfsdump still fails: p.o var.o /usr/lib/libuuid.a /lib/libhandle.so /lib/libattr.so /lib/libdm.so ../librmt/.libs/librmt.al gcc: /lib/libhandle.so: No such file or directory gcc: /lib/libattr.so: No such file or directory gcc: /lib/libdm.so: No such file or directory First of all, shared libraries should be linked with -llib, secondly, none of the libraries appears to be installed properly. It seems like libtool is doing the wrong thing, and leaving out steps like linking the .so files with the .so; Sun, 29 Jun 2003 09:33:13 -0700 Received: from scaup.mail.pas.earthlink.net (scaup.mail.pas.earthlink.net [207.217.120.49]) by badboy.mail.pas.earthlink.net (8.11.6+Sun/8.11.6) with ESMTP id h5TGThK16523 for ; Sun, 29 Jun 2003 09:29:43 -0700 (PDT) Received: from user-v7kakra.dialup.mindspring.com ([207.69.83.106] helo=earthlink.net) by scaup.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 19Wevl-0004sE-00 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 09:21:33 -0700 Date: Sun, 29 Jun 2003 12:22:53 -0400 To: linux-xfs@oss.sgi.com Subject: [patch] reduce extra xfs recompilation Message-ID: <20030629162250.GA3332@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: 4496 X-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 Most of xfs recompiles during "make bzImage" because linux/include/linux/version.h is touched. The patch below eliminates most of the extra recompile and changes the boot message from: SGI XFS for Linux 2.5.73-mm1 with no debug enabled to SGI XFS for Linux with no debug enabled diff -u linux-2.5.73-mm1/fs/xfs/linux/xfs_version.h linux/fs/xfs/linux/xfs_version.h --- linux-2.5.73-mm1/fs/xfs/linux/xfs_version.h 2002-12-12 04:36:32.000000000 -0500 +++ linux/fs/xfs/linux/xfs_version.h 2003-06-29 12:16:48.000000000 -0400 @@ -39,8 +39,6 @@ #ifndef __XFS_VERSION_H__ #define __XFS_VERSION_H__ -#include - -#define XFS_VERSION_STRING "for Linux " UTS_RELEASE +#define XFS_VERSION_STRING "for Linux" #endif /* __XFS_VERSION_H__ */ -- Randy Hron http://home.earthlink.net/~rwhron/kernel/bigbox.html From owner-linux-xfs@oss.sgi.com Sun Jun 29 13:53:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 13:53:26 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5TKr62x012548 for ; Sun, 29 Jun 2003 13:53:06 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5TKr6gn012547 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 13:53:06 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5TKr431012533 for ; Sun, 29 Jun 2003 13:53:04 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5TKqTsJ012525; Sun, 29 Jun 2003 13:52:29 -0700 Date: Sun, 29 Jun 2003 13:52:29 -0700 Message-Id: <200306292052.h5TKqTsJ012525@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] New: XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4497 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 Summary: XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. Product: Linux XFS Version: Current Platform: All OS/Version: Linux Status: NEW Severity: critical Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: knutjbj@online.no I think it is a problem with unmount since /etc/fstab is replace by a binary files instead off a test config files with meaning. I fix this problem by rebooting from cd rom and replace fstab with a right fstab. ------- 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 Sun Jun 29 15:45:15 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 15:45:30 -0700 (PDT) Received: from hell.org.pl (qmailr@hell.org.pl [212.244.218.42]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5TMjD2x015498 for ; Sun, 29 Jun 2003 15:45:14 -0700 Received: (qmail 26868 invoked by uid 777); 29 Jun 2003 22:45:38 -0000 Date: Mon, 30 Jun 2003 00:45:38 +0200 From: Karol Kozimor To: linux-xfs@oss.sgi.com Subject: [PATCH] refrigerator support for xfssyncd Message-ID: <20030629224538.GA21312@hell.org.pl> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline User-Agent: Mutt/1.4.1i X-archive-position: 4498 X-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 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Hi, This patch provides refrigerator support for xfssyncd kernel threads, so that they are properly frozen during software suspend or one of the ACPI sleep states. A similar change is sufficient under 2.4.x. Please apply. BTW: Is there anyone with a spare machine and some time, who could test XFS interoperability with software suspend under 2.5.x kernels? I'm being plagued by -990 errors since the first time I started testing 2.5.x and can't really be sure whether it works or not. Best regards, -- Karol 'sziwan' Kozimor sziwan@hell.org.pl --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: attachment; filename="xfs-2.5.73-swsusp.patch" --- a/fs/xfs/linux/xfs_syncd.c 2003-06-24 20:52:04.000000000 +0200 +++ b/fs/xfs/linux/xfs_syncd.c 2003-06-24 20:52:20.000000000 +0200 @@ -32,6 +32,8 @@ #include +#include + #define SYNCD_FLAGS (SYNC_FSDATA|SYNC_BDFLUSH|SYNC_ATTR) int syncd(void *arg) @@ -48,6 +50,9 @@ for (;;) { set_current_state(TASK_INTERRUPTIBLE); schedule_timeout(xfs_params.sync_interval); + /* swsusp */ + if (current->flags & PF_FREEZE) + refrigerator(PF_IOTHREAD); if (vfsp->vfs_flag & VFS_UMOUNT) break; if (vfsp->vfs_flag & VFS_RDONLY); --- a/fs/xfs/linux/xfs_super.c 2003-06-24 20:52:16.000000000 +0200 +++ b/fs/xfs/linux/xfs_super.c 2003-06-24 20:52:25.000000000 +0200 @@ -71,6 +71,7 @@ #include #include #include +#include STATIC struct quotactl_ops linvfs_qops; STATIC struct super_operations linvfs_sops; @@ -401,6 +402,9 @@ for (;;) { set_current_state(TASK_INTERRUPTIBLE); schedule_timeout(xfs_params.sync_interval); + /* swsusp */ + if (current->flags & PF_FREEZE) + refrigerator(PF_IOTHREAD); if (vfsp->vfs_flag & VFS_UMOUNT) break; if (vfsp->vfs_flag & VFS_RDONLY) --oyUTqETQ0mS9luUI-- From owner-linux-xfs@oss.sgi.com Sun Jun 29 15:53:06 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 15:53:10 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5TMr62x015971 for ; Sun, 29 Jun 2003 15:53:06 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5TMr6SQ015970 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 15:53:06 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5TMr431015956 for ; Sun, 29 Jun 2003 15:53:05 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5TMnrOq015936; Sun, 29 Jun 2003 15:49:53 -0700 Date: Sun, 29 Jun 2003 15:49:53 -0700 Message-Id: <200306292249.h5TMnrOq015936@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 258] New: Kernel (smp) lockup: ioctl(XFS_IOC_RESVSP); truncate() on fs with unwritten=1 X-Bugzilla-Reason: AssignedTo X-archive-position: 4499 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=258 Summary: Kernel (smp) lockup: ioctl(XFS_IOC_RESVSP); truncate() on fs with unwritten=1 Product: Linux XFS Version: Current Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: mikes@av.com The following code seem to be causing kernel (cvs 2.4.21-xfs smp with highmem=1 and highio=1, SGI-XFS CVS-2003-06-24_05:00_UTC with no debug enabled) lockup. Machine is dual Pentium 3, 860 MHz 2Gb RAM. #define _GNU_SOURCE #define _FILE_OFFSET_BITS 64 #define _LARGEFILE_SOURCE #define LARGE_FILES #include #include #include #include #include #include #include #include int main(int argc, char** argv) { int fd; xfs_flock64_t req = { 0 }; const off_t len = (off_t)10 * ((off_t)1 << 30); const char* fn = argc > 1 ? argv[1] : "tt"; if ((fd = open(fn, O_RDWR | O_CREAT | O_EXCL, 0644)) < 0) { perror(fn); return 1; } req.l_start = 0; req.l_len = len; req.l_whence = SEEK_END; if (ioctl(fd, XFS_IOC_RESVSP, &req) != 0) { perror("XFS_IOC_RESVSP"); close(fd); return 1; } if (close(fd) != 0) { perror("close"); return 1; } if (truncate(fn, len) != 0) { perror("truncate"); return 1; } return 0; } Below is xfs_info ouptput meta-data=/mnt/raid1 isize=256 agcount=26, agsize=1048576 blks = sectsz=512 data = bsize=4096 blocks=26656912, imaxpct=25 = sunit=16 swidth=48 blks, unwritten=1 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=3264, version=1 = sectsz=512 sunit=0 blks realtime =none extsz=196608 blocks=0, rtextents=0 fs is on software raid (md) 0 with 3x36GB scsi drives. ------- 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 Sun Jun 29 19:53:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 19:53:21 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U2r72x019948 for ; Sun, 29 Jun 2003 19:53:07 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U2r7Nt019947 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 19:53:07 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U2r531019933 for ; Sun, 29 Jun 2003 19:53:05 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U2pNq1019922; Sun, 29 Jun 2003 19:51:23 -0700 Date: Sun, 29 Jun 2003 19:51:23 -0700 Message-Id: <200306300251.h5U2pNq1019922@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4500 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 ------- Additional Comments From knutjbj@online.no 2003-29-06 13:53 PDT ------- Created an attachment (id=82) --> (http://oss.sgi.com/bugzilla/attachment.cgi?id=82&action=view) repair seasion afte fixing /etc/fstab on xfs root partino ------- Additional Comments From sandeen@sgi.com 2003-29-06 19:51 PDT ------- We're going to need a lot more information than you have provided, to get anywhere with this bug. For starters, what kernel are you running, and where did the xfs code come from. Is this reproducible? If so, how? If not, what were you doing before you saw the problem? What did this "binary file" look like? With the bug as you have filed it, for all I know you copied /proc/kcore to /etc/fstab :) ------- 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 Sun Jun 29 20:53:07 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 20:53:21 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U3r72x023058 for ; Sun, 29 Jun 2003 20:53:07 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U3r7dN023057 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 20:53:07 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U3r631023043 for ; Sun, 29 Jun 2003 20:53:06 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U34qfw020458; Sun, 29 Jun 2003 20:04:52 -0700 Date: Sun, 29 Jun 2003 20:04:52 -0700 Message-Id: <200306300304.h5U34qfw020458@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4501 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 ------- Additional Comments From sandeen@sgi.com 2003-29-06 20:04 PDT ------- Unfortunately the attachment does not tell us very much. This part: 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 tells us that there was an existing lost+found/ directory, and that it was cleared. Anything that -was- there is later re-found in later phases. So, it is very likely that the repair output has nothing to do with the problem you saw. ------- 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 Sun Jun 29 22:53:10 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 22:53:28 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U5rA2x024218 for ; Sun, 29 Jun 2003 22:53:10 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U5rAaV024217 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 22:53:10 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U5r831024203 for ; Sun, 29 Jun 2003 22:53:08 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U5lCoZ024175; Sun, 29 Jun 2003 22:47:12 -0700 Date: Sun, 29 Jun 2003 22:47:12 -0700 Message-Id: <200306300547.h5U5lCoZ024175@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4502 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 ------- Additional Comments From knutjbj@online.no 2003-29-06 22:47 PDT ------- There was a lost+found dir before I ran xfs_repair. ------- 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 Sun Jun 29 23:20:26 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 23:20:30 -0700 (PDT) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5U6KP2x025051 for ; Sun, 29 Jun 2003 23:20:26 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.54.232]) by rj.sgi.com (8.12.9/8.12.2/linux-outbound_gateway-1.2) with ESMTP id h5U6JtWr019174 for ; Sun, 29 Jun 2003 23:19:55 -0700 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id h5U6JIv06741; Mon, 30 Jun 2003 16:19:18 +1000 Date: Mon, 30 Jun 2003 16:19:18 +1000 From: Keith Owens Message-Id: <200306300619.h5U6JIv06741@sherman.melbourne.sgi.com> Subject: TAKE - Correct i386 backtrace on out of line lock code using jmp disp8 to get back to mainline X-archive-position: 4503 X-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@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs When backtracing through i386 out of line lock code, any code that used jmp disp8 to get back to the mainline code resulted in an incorrect calculation for the new eip due to incorrect sign extension, which in turn messes up the backtrace. AFAICT it is only the XFS pagebuf lock code that hit this special case. --- /usr/tmp/TmpDir.6202-0/linux/arch/i386/kdb/kdba_bt.c_1.21 Mon Jun 30 16:11:16 2003 +++ linux/arch/i386/kdb/kdba_bt.c Mon Jun 30 16:11:03 2003 @@ -268,7 +268,7 @@ kdb_di.fprintf_func = save_fprintf_func; if (offsize) { - realeip += 1 + offsize + offset; + realeip += 1 + offsize + (offsize == 1 ? (s8)offset : (s32)(offset)); if (kdbnearsym(realeip, &lock_symtab)) { /* Print the stext entry without args */ bt_print_one(eip, NOBP, &ar, &symtab, 0); Date: Sun Jun 29 23:16:04 PDT 2003 Workarea: sherman.melbourne.sgi.com:/build/kaos/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:152253a linux/arch/i386/kdb/kdba_bt.c - 1.22 From owner-linux-xfs@oss.sgi.com Sun Jun 29 23:53:08 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Jun 2003 23:53:10 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U6r72x031250 for ; Sun, 29 Jun 2003 23:53:07 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U6r7se031249 for linux-xfs@oss.sgi.com; Sun, 29 Jun 2003 23:53:07 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U6r631031235 for ; Sun, 29 Jun 2003 23:53:06 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U6RuMc025518; Sun, 29 Jun 2003 23:27:56 -0700 Date: Sun, 29 Jun 2003 23:27:56 -0700 Message-Id: <200306300627.h5U6RuMc025518@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4504 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 ------- Additional Comments From knutjbj@online.no 2003-29-06 23:27 PDT ------- I think this bug is somehowe relative to bug 258, since I alsao have highio and highmemory enabled. ------- 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 Jun 30 02:53:10 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 02:53:31 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U9rA2x007613 for ; Mon, 30 Jun 2003 02:53:10 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U9rA2r007612 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 02:53:10 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5U9r731007597 for ; Mon, 30 Jun 2003 02:53:07 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5U8r8rG002973; Mon, 30 Jun 2003 01:53:08 -0700 Date: Mon, 30 Jun 2003 01:53:08 -0700 Message-Id: <200306300853.h5U8r8rG002973@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 213] XFS kernel patch breaks kdemultimedia X-Bugzilla-Reason: AssignedTo X-archive-position: 4505 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=213 kelledin@skarpsey.dyndns.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | ------- Additional Comments From kelledin@skarpsey.dyndns.org 2003-30-06 01:53 PDT ------- This is actually NOT a KDE bug. It's an XFS bug. The problem is that if gcc -ansi is used, the kernel headers do not define the __u64 type, yet the XFS-patched include/asm-i386/byteorder.h relies on __u64 being a defined type. The non-XFS-patched include/asm-i386/byteorder.h will not introduce this type dependency for userspace code built with gcc -ansi; it will quite sensibly refuse to provide swab64(). The XFS-patched include/asm-i386/byteorder.h should follow the same behavior. kdemultimedia's CD player app (KsCD IIRC) hits this because it includes , which indirectly includes . KsCD has a pretty obvious need to do this, I think. ;) I will attach a patch below that fixes this for XFS-patched 2.4.20. ------- 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 Jun 30 03:18:25 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 03:18:43 -0700 (PDT) Received: from hermod.slb.nwc.acsalaska.net (hermod.slb.nwc.acsalaska.net [209.112.155.45]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5UAIO2x008375 for ; Mon, 30 Jun 2003 03:18:25 -0700 Received: from erbenson.alaska.net (35-pm29.nwc.alaska.net [209.112.158.35]) by hermod.slb.nwc.acsalaska.net (8.12.9/8.12.9) with ESMTP id h5UAIMCw093586 for ; Mon, 30 Jun 2003 02:18:23 -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 17DFC3A05 for ; Mon, 30 Jun 2003 02:18:22 -0800 (AKDT) Received: by plato.local.lan (Postfix, from userid 1000) id D167140FF44; Mon, 30 Jun 2003 02:18:21 -0800 (AKDT) Date: Mon, 30 Jun 2003 02:18:21 -0800 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: [Bug 213] XFS kernel patch breaks kdemultimedia Message-ID: <20030630101821.GF930@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200306300853.h5U8r8rG002973@oss.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pql/uPZNXIm1JCle" Content-Disposition: inline In-Reply-To: <200306300853.h5U8r8rG002973@oss.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-Scanned-By: MIMEDefang 2.33 (www . roaringpenguin . com / mimedefang) X-archive-position: 4506 X-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 --Pql/uPZNXIm1JCle Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jun 30, 2003 at 01:53:08AM -0700, bugzilla-daemon@oss.sgi.com wrote: > http://oss.sgi.com/bugzilla/show_bug.cgi?id=3D213 >=20 >=20 > kelledin@skarpsey.dyndns.org changed: >=20 > What |Removed |Added > -------------------------------------------------------------------------= --- > Status|RESOLVED |REOPENED > Resolution|INVALID | >=20 >=20 >=20 >=20 > ------- Additional Comments From kelledin@skarpsey.dyndns.org 2003-30-06= 01:53 PDT ------- > This is actually NOT a KDE bug. It's an XFS bug. The problem is that if= gcc -ansi is used, the=20 yes it is a KDE bug. userspace shall NEVER include kernel headers, doing so is a bug. > kdemultimedia's CD player app (KsCD IIRC) hits this because it includes <= linux/cdrom.h>, which=20 which is a bug. > indirectly includes . KsCD has a pretty obvious need to= do this, I think. ;)=20 it should have its own local copies of whatever it needs then, it should NOT be including kernel headers directly. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --Pql/uPZNXIm1JCle 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 iEYEARECAAYFAj8ADm0ACgkQJKx7GixEevyRFgCcDw3mM/ZT8s5IXjF6sGi1tAVX geYAn0xtobioTkaHdx0wKwRc1jYm3dWt =5hfK -----END PGP SIGNATURE----- --Pql/uPZNXIm1JCle-- From owner-linux-xfs@oss.sgi.com Mon Jun 30 03:53:09 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 03:53:25 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UAr92x009417 for ; Mon, 30 Jun 2003 03:53:09 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UAr9gg009416 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 03:53:09 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UAr731009402 for ; Mon, 30 Jun 2003 03:53:07 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UAefk9008947; Mon, 30 Jun 2003 03:40:41 -0700 Date: Mon, 30 Jun 2003 03:40:41 -0700 Message-Id: <200306301040.h5UAefk9008947@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 213] XFS kernel patch breaks kdemultimedia X-Bugzilla-Reason: AssignedTo X-archive-position: 4507 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=213 kaos@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX ------- Additional Comments From kelledin@skarpsey.dyndns.org 2003-30-06 01:54 PDT ------- Created an attachment (id=83) --> (http://oss.sgi.com/bugzilla/attachment.cgi?id=83&action=view) swab64 fix ------- Additional Comments From kaos@sgi.com 2003-30-06 03:40 PDT ------- XFS does not touch byteorder.h. Any problems that userspace has from including the kernel's byteorder.h will occur with the pristine 2.4.21 kernel as well. Try sending your change to the linux-kernel list, but you will get the same response - "applications must not include kernel headers directly". In other words, this 'bug' has nothing to do with XFS. ------- 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 Jun 30 06:53:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 06:53:33 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UDrB2x022757 for ; Mon, 30 Jun 2003 06:53:11 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UDrBwN022755 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 06:53:11 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UDr835022727 for ; Mon, 30 Jun 2003 06:53:08 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UDPLL7015529; Mon, 30 Jun 2003 06:25:21 -0700 Date: Mon, 30 Jun 2003 06:25:21 -0700 Message-Id: <200306301325.h5UDPLL7015529@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4508 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 ------- Additional Comments From sandeen@sgi.com 2003-30-06 06:25 PDT ------- We cannot do anything with this bug until you provide some basic information as I have requested above. If you cannot provide any more information about what you were doing, or what your "fstab" looked like, or even what kernel you were running, I will have to close this bug as WORKSFORME. ------- 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 Jun 30 06:53:11 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 06:53:33 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UDrB2x022756 for ; Mon, 30 Jun 2003 06:53:11 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UDrBAp022754 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 06:53:11 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UDr831022727 for ; Mon, 30 Jun 2003 06:53:08 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UDIcZI015177; Mon, 30 Jun 2003 06:18:38 -0700 Date: Mon, 30 Jun 2003 06:18:38 -0700 Message-Id: <200306301318.h5UDIcZI015177@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 213] XFS kernel patch breaks kdemultimedia X-Bugzilla-Reason: AssignedTo X-archive-position: 4508 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=213 ------- Additional Comments From sandeen@sgi.com 2003-30-06 06:18 PDT ------- Including cdrom.h is a perfectly reasonable thing to do, but userspace should NOT be including this header from any kernel tree. It should be including the glibc kernel headers, for example on Red Hat this is in the glibc-kernheaders package, at /usr/include/linux/cdrom.h ------- 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 Jun 30 08:02:52 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 08:03:13 -0700 (PDT) Received: from ams002.ftl.affinity.com (lvs01-fl.valueweb.net [216.219.253.200]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5UF2n2x028998 for ; Mon, 30 Jun 2003 08:02:52 -0700 Received: from david.internal.NorcrossGroup.com ([66.156.1.196]) by ams.ftl.affinity.com with ESMTP id <557249-6956>; Mon, 30 Jun 2003 11:02:41 -0400 Subject: Re: XFSDUMP Warning From: Greg Freemyer Reply-To: freemyer-ml@NorcrossGroup.com To: Ethan Benson Cc: xfs mailing list In-Reply-To: <20030628071011.GB1788@plato.local.lan> References: <20030627193302.SLMI24789.imf20aec.bellsouth.net@tiger2> <20030628071011.GB1788@plato.local.lan> Content-Type: text/plain Organization: Message-Id: <1056985965.16995.5.camel@david.internal.NorcrossGroup.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.3 Date: 30 Jun 2003 11:12:45 -0400 Content-Transfer-Encoding: 7bit X-archive-position: 4509 X-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 Thanks I will do that tonight. FYI: I got the same error twice over the weekend, so it was definately not a one-time issue. Greg On Sat, 2003-06-28 at 03:10, Ethan Benson wrote: > On Fri, Jun 27, 2003 at 03:41:24PM -0400, Greg Freemyer wrote: > > > > Last night I got an XFSDUMP warning I have never seen before: > > > > WARNING: getbmapx 1 ino 132 mode 0x000081f6 offset 0 failed: Unknown error 990 > > > > This was with XFS 1.2 as included in SuSE 8.2 (2.4.20 kernel) > > > > Does this mean I have a problem? > > > > Is it safe to assume the single file was skipped, but got backed up the next xfsdump run? > > no, errno 990 is EFSCORRUPTED, it only occurs when filesystem > corruption is detected. you should umount the relevant filesystem and > run xfs_repair on it. From owner-linux-xfs@oss.sgi.com Mon Jun 30 10:53:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 10:53:28 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UHrD2x001506 for ; Mon, 30 Jun 2003 10:53:13 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UHrDvL001505 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 10:53:13 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UHrB37001475 for ; Mon, 30 Jun 2003 10:53:11 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UH0IHM000784; Mon, 30 Jun 2003 10:00:18 -0700 Date: Mon, 30 Jun 2003 10:00:18 -0700 Message-Id: <200306301700.h5UH0IHM000784@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4510 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 knutjbj@online.no changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From knutjbj@online.no 2003-30-06 10:00 PDT ------- I am unable to reproduce since I have turn off highmemio and highmemory. /etc/fstab contain just meanlinless binary. *** This bug has been marked as a duplicate of 258 *** ------- 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 Jun 30 10:53:13 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 10:53:29 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UHrD2x001507 for ; Mon, 30 Jun 2003 10:53:13 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UHrD50001504 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 10:53:13 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UHrB33001475 for ; Mon, 30 Jun 2003 10:53:11 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UH0JZh000788; Mon, 30 Jun 2003 10:00:19 -0700 Date: Mon, 30 Jun 2003 10:00:19 -0700 Message-Id: <200306301700.h5UH0JZh000788@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 258] Kernel (smp) lockup: ioctl(XFS_IOC_RESVSP); truncate() on fs with unwritten=1 X-Bugzilla-Reason: AssignedTo X-archive-position: 4511 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=258 knutjbj@online.no changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |knutjbj@online.no ------- Additional Comments From knutjbj@online.no 2003-30-06 10:00 PDT ------- *** Bug 257 has been marked as a duplicate of this bug. *** ------- 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 Jun 30 12:45:00 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 12:45:14 -0700 (PDT) Received: from THOR.goeci.com ([66.28.220.99]) by oss.sgi.com (8.12.9/8.12.9) with SMTP id h5UJj02x010520 for ; Mon, 30 Jun 2003 12:45:00 -0700 Received: by THOR.goeci.com with Internet Mail Service (5.5.2653.19) id ; Mon, 30 Jun 2003 15:44:54 -0400 Message-ID: <2D92FEBFD3BE1346A6C397223A8DD3FC092358@THOR.goeci.com> From: Murthy Kambhampaty To: "'Christoph Hellwig'" Cc: linux-xfs@oss.sgi.com Subject: Solved? /sbin/lvcreate -s hangs in xfs_check_frozen Date: Mon, 30 Jun 2003 15:44:54 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-archive-position: 4512 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: murthy.kambhampaty@goeci.com Precedence: bulk X-list: linux-xfs The problem I reported some time ago, with /sbin/lvcreate -s hanging in xfs_check_frozen (http://marc.theaimsgroup.com/?l=linux-xfs&m=105277405929107&w=2), has not appeared in over a week running the CVS kernel from June 19th. Thanks, Murthy From owner-linux-xfs@oss.sgi.com Mon Jun 30 12:53:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 12:53:31 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UJrC2x013750 for ; Mon, 30 Jun 2003 12:53:12 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UJrBal013746 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 12:53:11 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UJr937013706 for ; Mon, 30 Jun 2003 12:53:09 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UJ9Eap005803; Mon, 30 Jun 2003 12:09:14 -0700 Date: Mon, 30 Jun 2003 12:09:14 -0700 Message-Id: <200306301909.h5UJ9Eap005803@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4514 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Resolution|DUPLICATE | ------- 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 Jun 30 12:53:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 12:53:27 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UJrC2x013749 for ; Mon, 30 Jun 2003 12:53:12 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UJrBw2013745 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 12:53:11 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UJr935013706 for ; Mon, 30 Jun 2003 12:53:09 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UJ8JFL005752; Mon, 30 Jun 2003 12:08:19 -0700 Date: Mon, 30 Jun 2003 12:08:19 -0700 Message-Id: <200306301908.h5UJ8JFL005752@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4513 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Additional Comments From sandeen@sgi.com 2003-30-06 12:08 PDT ------- > I am unable to reproduce since I have turn off highmemio and highmemory. And you -can- reproduce it when they are turned on? If so, how? bug 258 is related to the XFS_IOC_RESERVSP ioctl, are you using that call? It also relates to a system lockup - did your system lock up before you saw your problems? Un-duping and closing this bug until we get some useful information. ------- 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 Jun 30 12:53:12 2003 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Jun 2003 12:53:27 -0700 (PDT) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UJrC2x013751 for ; Mon, 30 Jun 2003 12:53:12 -0700 Received: (from xfs@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UJrCAe013748 for linux-xfs@oss.sgi.com; Mon, 30 Jun 2003 12:53:12 -0700 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.9/8.12.9) with ESMTP id h5UJr939013706 for ; Mon, 30 Jun 2003 12:53:09 -0700 Received: (from apache@localhost) by oss.sgi.com (8.12.9/8.12.8/Submit) id h5UJ9Vkx005836; Mon, 30 Jun 2003 12:09:31 -0700 Date: Mon, 30 Jun 2003 12:09:31 -0700 Message-Id: <200306301909.h5UJ9Vkx005836@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 257] XFS umount leave a binary file in place off /etc/fstab and /etc/mtab, which cause LInux to be unable to boot. X-Bugzilla-Reason: AssignedTo X-archive-position: 4513 X-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 http://oss.sgi.com/bugzilla/show_bug.cgi?id=257 sandeen@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WORKSFORME ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.