From owner-linux-xfs@oss.sgi.com Sat Jun 30 23:59:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f616xv002227 for linux-xfs-outgoing; Sat, 30 Jun 2001 23:59:57 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f616xuV02224 for ; Sat, 30 Jun 2001 23:59:56 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f616xns00645 for linux-xfs@oss.sgi.com; Sun, 1 Jul 2001 02:59:49 -0400 Date: Sun, 1 Jul 2001 02:59:49 -0400 From: Alan Eldridge To: linux-xfs@oss.sgi.com Subject: compile failure in current CVSup Message-ID: <20010701025949.A3772@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Source file drivers/sound/cs46xx.c does not compile. It has static functions declared as void up top, and the definition of those same functions has them returning int. Given that I doubt you guys have been mucking with sound, the pre7 patch must be borked. -- Alan Eldridge "Gee, Bill, what do you want to do tonight?" "The same thing we do every night, Steve. Try to take over the world!" From owner-linux-xfs@oss.sgi.com Sun Jul 1 00:16:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f617G8q05040 for linux-xfs-outgoing; Sun, 1 Jul 2001 00:16:08 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f617G6V05032 for ; Sun, 1 Jul 2001 00:16:06 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f617Fu101025 for linux-xfs@oss.sgi.com; Sun, 1 Jul 2001 03:15:56 -0400 Date: Sun, 1 Jul 2001 03:15:55 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: patch for borked code Message-ID: <20010701031555.A1017@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I'm sure this will be fixed in the real kernel RSN. -- Alan Eldridge "Gee, Bill, what do you want to do tonight?" "The same thing we do every night, Steve. Try to take over the world!" --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="linux-2.4.6pre7-cs46xx.patch" --- linux/drivers/sound/cs46xx.c.or Thu Jun 28 06:10:19 2001 +++ linux/drivers/sound/cs46xx.c Sun Jul 1 03:13:41 2001 @@ -383,8 +383,10 @@ static int cs46xx_powerup(struct cs_card *card, unsigned int type); static int cs461x_powerdown(struct cs_card *card, unsigned int type, int suspendflag); static void cs461x_clear_serial_FIFOs(struct cs_card *card, int type); +#ifdef FIXME static void cs46xx_suspend_tbl(struct pci_dev *pcidev); static void cs46xx_resume_tbl(struct pci_dev *pcidev); +#endif /* FIXME */ static inline unsigned ld2(unsigned int x) { --IJpNTDwzlM2Ie8A6-- From owner-linux-xfs@oss.sgi.com Sun Jul 1 01:24:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f618OjK16532 for linux-xfs-outgoing; Sun, 1 Jul 2001 01:24:45 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f618OhV16529 for ; Sun, 1 Jul 2001 01:24:43 -0700 Received: (qmail 5008 invoked from network); 1 Jul 2001 08:24:36 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 1 Jul 2001 08:24:36 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Alan Eldridge cc: linux-xfs@oss.sgi.com Subject: Re: compile failure in current CVSup In-reply-to: Your message of "Sun, 01 Jul 2001 02:59:49 -0400." <20010701025949.A3772@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Jul 2001 18:24:34 +1000 Message-ID: <8138.993975874@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001 02:59:49 -0400, Alan Eldridge wrote: >Source file drivers/sound/cs46xx.c does not compile. http://marc.theaimsgroup.com/?l=linux-kernel&m=99395858522305&w=2 From owner-linux-xfs@oss.sgi.com Sun Jul 1 03:04:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61A4sV31349 for linux-xfs-outgoing; Sun, 1 Jul 2001 03:04:54 -0700 Received: from ente.berdmann.de (p3E9C25A1.dip.t-dialin.net [62.156.37.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61A4qV31334 for ; Sun, 1 Jul 2001 03:04:52 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Ge5t-0001QV-00 for linux-xfs@oss.sgi.com; Sun, 01 Jul 2001 12:04:45 +0200 Message-ID: <3B3EF5BD.7EE9AA5D@berdmann.de> Date: Sun, 01 Jul 2001 12:04:45 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: XFS vs. JFS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, how do you think about IBM's JFS for Linux version 1.0 released last friday? http://oss.software.ibm.com/jfs/ Is it or can it be a competitor for XFS? The papers mention JFS only journaling metadata, not the data itself. Does XFS also journal the data? From owner-linux-xfs@oss.sgi.com Sun Jul 1 04:00:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61B0Ru08557 for linux-xfs-outgoing; Sun, 1 Jul 2001 04:00:27 -0700 Received: from citadel.oehansen.pp.se (sdu152-234.ppp.algonet.se [195.163.234.152]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61B0PV08551 for ; Sun, 1 Jul 2001 04:00:25 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f61B2Fr07249; Sun, 1 Jul 2001 13:02:16 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: "Bernhard R. Erdmann" , Linux XFS Mailing List Subject: Re: XFS vs. JFS Date: Sun, 1 Jul 2001 13:02:15 +0200 X-Mailer: KMail [version 1.2] References: <3B3EF5BD.7EE9AA5D@berdmann.de> In-Reply-To: <3B3EF5BD.7EE9AA5D@berdmann.de> X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 X-MIME-Autoconverted: from 8bit to quoted-printable by citadel.oehansen.pp.se id f61B2Fr07249 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f61B0QV08553 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk sunnudagur 1. júlí 2001 12:04, Bernhard R. Erdmann skrifaði: > Hi, > > how do you think about IBM's JFS for Linux version 1.0 released last > friday? > http://oss.software.ibm.com/jfs/ > > Is it or can it be a competitor for XFS? > Competition is healthy. Orn From owner-linux-xfs@oss.sgi.com Sun Jul 1 04:06:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61B6BS09714 for linux-xfs-outgoing; Sun, 1 Jul 2001 04:06:11 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61B69V09710 for ; Sun, 1 Jul 2001 04:06:10 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15Gf35-0007Dr-00; Sun, 01 Jul 2001 23:05:55 +1200 Date: Sun, 1 Jul 2001 23:05:55 +1200 (NZST) From: Juha Saarinen To: "Orn E. Hansen" cc: "Bernhard R. Erdmann" , Linux XFS Mailing List Subject: Re: XFS vs. JFS In-Reply-To: <01070113021505.01354@citadel.oehansen.pp.se> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001, Orn E. Hansen wrote: > Competition is healthy. Maybe they could merge their efforts... XJFS or JXFS? ;-D -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Sun Jul 1 04:15:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61BFUj10972 for linux-xfs-outgoing; Sun, 1 Jul 2001 04:15:30 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61BFSV10968 for ; Sun, 1 Jul 2001 04:15:29 -0700 Received: (qmail 6603 invoked from network); 1 Jul 2001 11:15:12 -0000 Received: from srg.access.comstar.ru (HELO beta.namesys.com) (195.210.131.190) by thebsh.namesys.com with SMTP; 1 Jul 2001 11:15:12 -0000 Received: (from god@localhost) by beta.namesys.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id PAA02282; Sun, 1 Jul 2001 15:14:05 +0400 From: Nikita Danilov MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15167.1533.474006.929684@beta.namesys.com> Date: Sun, 1 Jul 2001 15:14:05 +0400 To: linux-xfs@oss.sgi.com CC: Nikita Danilov Subject: ACL_OTHER_OBJ? X-Mailer: VM 6.89 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I have been looking through XFS code and seen that include/acl.h declares ACL_OTHER_OBJ macro. My copy of POSIX.1e/D17 only mentions ACL_OTHER (23.2.5, table 23-3). Was there some further development of the standard or you just decided to make naming more consistent? BTW, is there some description of NT ACL API in more usable form than pages from msdn site? (Please, CC responses to NikitaDanilov@Yahoo.COM.) Nikita From owner-linux-xfs@oss.sgi.com Sun Jul 1 04:52:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61BqgK21173 for linux-xfs-outgoing; Sun, 1 Jul 2001 04:52:42 -0700 Received: from porgy.srv.nld.sonera.net (mbox-01.soneraplaza.nl [195.66.15.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61BqfV21170 for ; Sun, 1 Jul 2001 04:52:41 -0700 Received: from qn-212-58-163-247.quicknet.nl ([212.58.163.247]:61561 "EHLO auto-nb1.xs4all.nl") by soneramail.nl with ESMTP id ; Sun, 1 Jul 2001 13:52:47 +0200 Message-Id: <4.3.2.7.2.20010701135119.0398a690@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 01 Jul 2001 13:52:20 +0200 To: Alan Eldridge , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: compile failure in current CVSup In-Reply-To: <20010701025949.A3772@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 02:59 1-7-2001 -0400, Alan Eldridge wrote: >Source file drivers/sound/cs46xx.c does not compile. It has static functions >declared as void up top, and the definition of those same functions has them >returning int. Given that I doubt you guys have been mucking with sound, the >pre7 patch must be borked. True pre6 also had this. Wait for pre8 to be merged which might just fix it. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 1 04:58:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61Bwoq22263 for linux-xfs-outgoing; Sun, 1 Jul 2001 04:58:50 -0700 Received: from porgy.srv.nld.sonera.net (mbox-01.soneraplaza.nl [195.66.15.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61BwnV22257 for ; Sun, 1 Jul 2001 04:58:49 -0700 Received: from qn-212-58-163-247.quicknet.nl ([212.58.163.247]:61566 "EHLO auto-nb1.xs4all.nl") by soneramail.nl with ESMTP id ; Sun, 1 Jul 2001 13:58:56 +0200 Message-Id: <4.3.2.7.2.20010701135304.03a05bb0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 01 Jul 2001 13:58:24 +0200 To: "Bernhard R. Erdmann" , Linux XFS Mailing List From: Seth Mos Subject: Re: XFS vs. JFS In-Reply-To: <3B3EF5BD.7EE9AA5D@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:04 1-7-2001 +0200, Bernhard R. Erdmann wrote: >Hi, > >how do you think about IBM's JFS for Linux version 1.0 released last >friday? >http://oss.software.ibm.com/jfs/ It's great because now we really _do_ have 3 journaling fs. It gives people choice which is very important. Each has it's own merits but here are some: IBM has it's own userbase that has AIX with JFS. Don't know if the layout is compatible. SGI has a large userbase around Irix and XFS. This means that people don't have to reformat their 5TB disk storage just be using linux instead of irix. ext3 is backwardscompatible which means you don't have to reformat any existing ext2 systems for getting journaling to work. >Is it or can it be a competitor for XFS? No, it is not about competition. It's about choice. >The papers mention JFS only journaling metadata, not the data itself. >Does XFS also journal the data? No, only ext3 journals the full data when you ask it to function in version1 mode. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 1 04:59:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61BxeM22415 for linux-xfs-outgoing; Sun, 1 Jul 2001 04:59:40 -0700 Received: from mailout02.sul.t-online.de (mailout02.sul.t-online.com [194.25.134.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61BxcV22404 for ; Sun, 1 Jul 2001 04:59:39 -0700 Received: from fwd02.sul.t-online.de by mailout02.sul.t-online.de with smtp id 15Gft1-0003kY-0A; Sun, 01 Jul 2001 13:59:35 +0200 Received: from tower (340024412816-0001@[217.230.8.24]) by fwd02.sul.t-online.com with smtp id 15Gfsx-27yeKuC; Sun, 1 Jul 2001 13:59:31 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Nikita Danilov , linux-xfs@oss.sgi.com Subject: Re: ACL_OTHER_OBJ? Date: Sun, 1 Jul 2001 13:59:35 +0200 X-Mailer: KMail [version 1.2] Cc: Nikita Danilov References: <15167.1533.474006.929684@beta.namesys.com> In-Reply-To: <15167.1533.474006.929684@beta.namesys.com> MIME-Version: 1.0 Message-Id: <01070113593500.11331@tower> Content-Transfer-Encoding: 8bit X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Sonntag, 1. Juli 2001 13:14 schrieb Nikita Danilov: > Hello, > > I have been looking through XFS code and seen that include/acl.h > declares ACL_OTHER_OBJ macro. My copy of POSIX.1e/D17 only mentions > ACL_OTHER (23.2.5, table 23-3). Was there some further development of > the standard or you just decided to make naming more consistent? ACL_OTHER_OBJ was originally defined by SGI, while ACL_OTHER is how Posix calls it. It was added for compatibility. > BTW, is there some description of NT ACL API in more usable form than > pages from msdn site? You might ask the Samba people on the samba or samba-technical mailing list. ...Juergen From owner-linux-xfs@oss.sgi.com Sun Jul 1 05:09:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61C9Tj24227 for linux-xfs-outgoing; Sun, 1 Jul 2001 05:09:29 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61C9SV24222 for ; Sun, 1 Jul 2001 05:09:28 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id FAA09405 for ; Sun, 1 Jul 2001 05:09:27 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id HAA2277783; Sun, 1 Jul 2001 07:08:10 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id HAA04594; Sun, 1 Jul 2001 07:08:10 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f61C9UQ15023; Sun, 1 Jul 2001 07:09:30 -0500 Message-Id: <200107011209.f61C9UQ15023@jen.americas.sgi.com> To: Seth Mos cc: Alan Eldridge , linux-xfs@oss.sgi.com Subject: Re: compile failure in current CVSup References: <4.3.2.7.2.20010701135119.0398a690@pop.xs4all.nl> Comments: In-reply-to Seth Mos message dated "Sun, 01 Jul 2001 13:52:20 +0200." Date: Sun, 01 Jul 2001 07:09:29 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > At 02:59 1-7-2001 -0400, Alan Eldridge wrote: > >Source file drivers/sound/cs46xx.c does not compile. It has static functions > >declared as void up top, and the definition of those same functions has them > >returning int. Given that I doubt you guys have been mucking with sound, the > >pre7 patch must be borked. > > True pre6 also had this. Wait for pre8 to be merged which might just fix it. It does not contain this fix, and it is going to take a little while to merge pre8, Linus has been busy rewriting things..... In general I do not put generic linux fixes into the tree unless they are central to the code (i.e. core kernel build failures etc). I know this makes using XFS a bit more of a pain for some people, but I want to keep the tree as clean as possible. Steve > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 1 05:12:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61CCk524858 for linux-xfs-outgoing; Sun, 1 Jul 2001 05:12:46 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61CCjV24851 for ; Sun, 1 Jul 2001 05:12:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id FAA02337 for ; Sun, 1 Jul 2001 05:12:45 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id HAA2295773; Sun, 1 Jul 2001 07:11:22 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id HAA84966; Sun, 1 Jul 2001 07:11:22 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f61CCgM15038; Sun, 1 Jul 2001 07:12:42 -0500 Message-Id: <200107011212.f61CCgM15038@jen.americas.sgi.com> To: Seth Mos cc: "Bernhard R. Erdmann" , Linux XFS Mailing List Subject: Re: XFS vs. JFS References: <4.3.2.7.2.20010701135304.03a05bb0@pop.xs4all.nl> Comments: In-reply-to Seth Mos message dated "Sun, 01 Jul 2001 13:58:24 +0200." Date: Sun, 01 Jul 2001 07:12:42 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > At 12:04 1-7-2001 +0200, Bernhard R. Erdmann wrote: > >Hi, > > > >how do you think about IBM's JFS for Linux version 1.0 released last > >friday? > >http://oss.software.ibm.com/jfs/ > > It's great because now we really _do_ have 3 journaling fs. > It gives people choice which is very important. > > Each has it's own merits but here are some: > > IBM has it's own userbase that has AIX with JFS. Don't know if the layout > is compatible. The JFS IBM released for Linux comes from the OS/2 version, not AIX. I do not know if they are on disk compatible or not. Steve Best has given lots of talks, at least some of them should be out on the net for people to look at. I have not seen one of his talks for several months, so I cannot comment on features etc of the 1.0 release. Steve From owner-linux-xfs@oss.sgi.com Sun Jul 1 06:59:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61Dxbt09479 for linux-xfs-outgoing; Sun, 1 Jul 2001 06:59:37 -0700 Received: from mailhost.chi.ameritech.net (mpdr0.chicago.il.ameritech.net [206.141.239.142]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61DxaV09476 for ; Sun, 1 Jul 2001 06:59:36 -0700 Received: from musuko.uchicago.edu ([66.72.96.242]) by mailhost.chi.ameritech.net (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <20010701135930.ECLG29150.mailhost.chi.ameritech.net@musuko.uchicago.edu>; Sun, 1 Jul 2001 08:59:30 -0500 Message-ID: X-Mailer: XFMail 1.5.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B3DEF84.D2CC1B15@inter.nl.net> Date: Sun, 01 Jul 2001 09:00:38 -0500 (CDT) Reply-To: s-luppescu@uchicago.edu Organization: Univ of Chicago From: s-luppescu@uchicago.edu To: Jurgen Kramer Subject: Re: Filesystem on XFS partition no longer accessible afterwritin Cc: linux-xfs@oss.sgi.com, Seth Mos Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 30-Jun-2001 Jurgen Kramer wrote: > Hi, > > After getting the system back up online I checked the Makefile. It defaults > to using gcc which > is not a problem with RH7.1. After changing it back to kgcc and recompiling > the kernel it works > like a charm again. So confusing two different systems...;-). > > So there are no problems with XFS just the usual RH gcc stuff... This seems to be a very general problem. I built 2.4.5 in RH 7.1 with the xfs version 1.01 pre2 (I think) patches with gcc 2.96RH on my machine at work (Dell Optiplex with a P III) with absolutely no problems. I used the same RH7.1, with the same gcc 2.96RH, and the same kernel source and patches at home (a K6-2 with a VIA MVP3 chipset) and got fatal file system corruption within 15 minutes of turning it on. I rebuilt it with the same source and patches using kgcc and it seems fine (knock on wood). Go figure. ______________________________________________________________________ Stuart Luppescu -=-=- University of Chicago ºÍʸ ¤ÈÃÒÆàÈþ¤ÎÉã(EUC) -=-=- s-luppescu@uchicago.edu http://www.consortium-chicago.org/people/sl/sl.html PGP public key: www.consortium-chicago.org/people/sl/pubkey.asc ICQ #21172047 AIM: psycho7070 marriage, n.: Convertible bonds. >> Sent on 01-Jul-2001 at 08:51:47 with xfmail From owner-linux-xfs@oss.sgi.com Sun Jul 1 07:13:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61EDfH11950 for linux-xfs-outgoing; Sun, 1 Jul 2001 07:13:41 -0700 Received: from main.braxis.co.uk (main.braxis.co.uk [213.77.40.29]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61EDdV11944 for ; Sun, 1 Jul 2001 07:13:39 -0700 Received: (from kszysiu@localhost) by main.braxis.co.uk (8.9.3/8.9.3) id QAA27224 for linux-xfs@oss.sgi.com; Sun, 1 Jul 2001 16:13:26 +0200 Date: Sun, 1 Jul 2001 16:13:26 +0200 From: Krzysztof Rusocki To: linux-xfs@oss.sgi.com Subject: /proc/sys/vm/pagbuf entries Message-ID: <20010701161326.A27056@main.braxis.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Can I ask anybody for short description of /proc/sys/vm/paegubuf/* entries ? TIA. Cheers, Krzysztof From owner-linux-xfs@oss.sgi.com Sun Jul 1 08:22:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61FMEE21811 for linux-xfs-outgoing; Sun, 1 Jul 2001 08:22:14 -0700 Received: from isis.telemach.net (isis.telemach.net [213.143.65.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61FMCV21805 for ; Sun, 1 Jul 2001 08:22:12 -0700 Received: from telemach.net (TM-68-212.cable.telemach.net [213.143.68.212]) by isis.telemach.net (Postfix) with ESMTP id AE8787A102 for ; Sun, 1 Jul 2001 17:22:09 +0200 (CEST) Message-ID: <3B3F401C.977CC826@telemach.net> Date: Sun, 01 Jul 2001 17:22:04 +0200 From: Jure Pecar Organization: Select Technology X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.19 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfs + raid5 (not on ide) coruption Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Recent similliar thread pointed out that this might be a problem within linux ide subsystem. So i thought i might report my expirience. I have 8 80gb maxtor disks on 3ware 6800. Running bonnie++ with some wild parameters like -s 16384 -n 4096:1048576:2048:25 popped up this after a couple of hours: 'cmn_err level 4 Filesystem "md(9,8)": corrupt dinode 60680385, extent total = 1, nblocks = 0. Unmount and run xfs_repair.'. So i did. xfs_repair told me: # xfs_repair /dev/md8 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 correcting nblocks for inode 60680385, was 0 - counted 68 - agno = 4 - agno = 5 ... snip ... - agno = 130 - agno = 131 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - clear lost+found (if it exists) ... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 ... snip ... - agno = 130 - agno = 131 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - ensuring existence of lost+found directory - traversing filesystem starting at / ... - traversal finished ... - traversing all unattached subtrees ... - traversals finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... done Any comments on this? If someone wants, i can also try to run such bonnie++ on ext2 and maybe reiserfs. Well, at least the results would be interesting :) -- Jure Pecar From owner-linux-xfs@oss.sgi.com Sun Jul 1 09:18:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61GICN25222 for linux-xfs-outgoing; Sun, 1 Jul 2001 09:18:12 -0700 Received: from ente.berdmann.de (p3E9C25A1.dip.t-dialin.net [62.156.37.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61GIAV25219 for ; Sun, 1 Jul 2001 09:18:10 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Gjv8-00038u-00; Sun, 01 Jul 2001 18:18:02 +0200 Message-ID: <3B3F4D3A.C42FEA8C@berdmann.de> Date: Sun, 01 Jul 2001 18:18:02 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List , "jfs-discussion@oss.software.ibm.com" Subject: XFS marries JFS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I just managed to apply the IBM patches for JFS to SGI's CVS checkout of linux-2.4.6-pre7-xfs. jfs-common-v1.0.0-patch applied with no errors, but jfs-2.4.5-v1.0.0-patch forced me using emacs instead of patch for include/linux/fs.h (just to add four lines). Compiled JFS and LVM as a modules and XFS into the kernel as before. From owner-linux-xfs@oss.sgi.com Sun Jul 1 09:32:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61GW3W25407 for linux-xfs-outgoing; Sun, 1 Jul 2001 09:32:03 -0700 Received: from ente.berdmann.de (p3E9C25A1.dip.t-dialin.net [62.156.37.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61GVxV25404 for ; Sun, 1 Jul 2001 09:32:00 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Gk8X-0003D7-00; Sun, 01 Jul 2001 18:31:53 +0200 Message-ID: <3B3F5079.F1776C04@berdmann.de> Date: Sun, 01 Jul 2001 18:31:53 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List , "jfs-discussion@oss.software.ibm.com" Subject: xfsrestore freezes on restoring to JFS Content-Type: multipart/mixed; boundary="------------568E67039848571B0D83D9B0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------568E67039848571B0D83D9B0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, i'm able to lock up xfsrestore when restoring onto a JFS filesystem. xfsrestore becomes dead in ps and is unkillable (waiting for I/O to happen?): # /sbin/mkfs.jfs /dev/vg01/usrjfs # cd /tmp # mount -t jfs /dev/vg01/usrjfs /mnt/usr # strace /sbin/xfsrestore -f tmp.xfsd /mnt/usr [..bla..] open("/mnt/usr/xfsrestorehousekeepingdir/state", O_RDWR|O_CREAT|O_LARGEFILE, 0600) = 4 SYS_197(0x4, 0xbffff990, 0x4010cd40, 0, 0x4) = 0 _llseek(4, 20479, [20479], SEEK_SET) = 0 write(4, "\0", 1) = 1 SYS_192(0, 0x5000, 0x3, 0x1, 0x4) = 1073831936 geteuid() = 0 munmap(0x40016000, 20480) = 0 SYS_194(0x4, 0x5000, 0, 0, 0x4 ...and there it ends. See the complete output attached. /tmp is on XFS because xfsrestore wants CWD on XFS. It also happens when not using LVM (/dev/sda1 instead of /dev/vg01/... for the block device). $ ps auxw|grep xfsrestore root 882 0.0 0.2 1316 528 pts/0 S 18:21 0:00 strace /sbin/xfsrestore -f tmp.xfsd /mnt/usr root 883 0.0 0.3 1676 784 pts/0 D 18:21 0:00 /sbin/xfsrestore -f tmp.xfsd /mnt/usr --------------568E67039848571B0D83D9B0 Content-Type: text/plain; charset=us-ascii; name="strace.out" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="strace.out" # strace /sbin/xfsrestore -f tmp.xfsd /mnt/usr execve("/sbin/xfsrestore", ["/sbin/xfsrestore", "-f", "tmp.xfsd", "/mnt/usr"], [/* 36 vars */]) = 0 brk(0) = 0x8098064 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40014000 open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory) open("/etc/ld.so.cache", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=25469, ...}) = 0 mmap(0, 25469, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40015000 close(3) = 0 open("/lib/libc.so.6", O_RDONLY) = 3 fstat(3, {st_mode=S_IFREG|0755, st_size=4101836, ...}) = 0 read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\210\212"..., 4096) = 4096 mmap(0, 1001532, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001c000 mprotect(0x40109000, 30780, PROT_NONE) = 0 mmap(0x40109000, 16384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0xec000) = 0x40109000 mmap(0x4010d000, 14396, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4010d000 close(3) = 0 mprotect(0x4001c000, 970752, PROT_READ|PROT_WRITE) = 0 mprotect(0x4001c000, 970752, PROT_READ|PROT_EXEC) = 0 munmap(0x40015000, 25469) = 0 personality(0 /* PER_??? */) = 0 getpid() = 883 brk(0) = 0x8098064 brk(0x80980c4) = 0x80980c4 brk(0x8099000) = 0x8099000 getrlimit(RLIMIT_AS, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0 setrlimit(RLIMIT_STACK, {rlim_cur=32768*1024, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=32768*1024, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_DATA, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_FSIZE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 setrlimit(RLIMIT_FSIZE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 setrlimit(RLIMIT_FSIZE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_FSIZE, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_CPU, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 setrlimit(RLIMIT_CPU, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 getrlimit(RLIMIT_CPU, {rlim_cur=RLIM_INFINITY, rlim_max=RLIM_INFINITY}) = 0 getpid() = 883 brk(0x809b000) = 0x809b000 getcwd("/tmp", 4095) = 5 getpid() = 883 getpid() = 883 getrlimit(RLIMIT_STACK, {rlim_cur=32768*1024, rlim_max=RLIM_INFINITY}) = 0 getpid() = 883 SYS_195(0x8099400, 0xbffff9d0, 0x4010cd40, 0x8099401, 0x8099400) = 0 SYS_195(0x8099400, 0xbffff9c8, 0x4010cd40, 0x8099401, 0x8099400) = 0 lstat("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0 lstat("/tmp/tmp.xfsd", {st_mode=S_IFREG|0664, st_size=11768160, ...}) = 0 mmap(0, 270336, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40111000 SYS_195(0x8099400, 0xbffff9bc, 0x4010cd40, 0x8099401, 0x8099400) = 0 open("/tmp/tmp.xfsd", O_RDONLY|O_LARGEFILE) = 3 SYS_197(0x1, 0xbffffaf8, 0x4010cd40, 0x4000aea0, 0x1) = 0 ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0 getpid() = 883 SYS_197(0x1, 0xbffff2cc, 0x4010cd40, 0x4010a960, 0x1) = 0 mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40015000 ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0 write(1, "/sbin/xfsrestore: version 3.0", 29/sbin/xfsrestore: version 3.0) = 29 write(1, " - Running single-threaded\n", 27 - Running single-threaded ) = 27 time(NULL) = 994004480 SYS_195(0xbffffcfb, 0xbffffa60, 0x4010cd40, 0xbffffcfb, 0xbffffcfb) = 0 mkdir("/mnt/usr/xfsrestorehousekeepingdir", 0700) = 0 open("/mnt/usr/xfsrestorehousekeepingdir/state", O_RDWR|O_CREAT|O_LARGEFILE, 0600) = 4 SYS_197(0x4, 0xbffff990, 0x4010cd40, 0, 0x4) = 0 _llseek(4, 20479, [20479], SEEK_SET) = 0 write(4, "\0", 1) = 1 SYS_192(0, 0x5000, 0x3, 0x1, 0x4) = 1073831936 geteuid() = 0 munmap(0x40016000, 20480) = 0 SYS_194(0x4, 0x5000, 0, 0, 0x4 --------------568E67039848571B0D83D9B0-- From owner-linux-xfs@oss.sgi.com Sun Jul 1 09:49:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61Gnda25673 for linux-xfs-outgoing; Sun, 1 Jul 2001 09:49:39 -0700 Received: from ente.berdmann.de (p3E9C25A1.dip.t-dialin.net [62.156.37.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61GnbV25670 for ; Sun, 1 Jul 2001 09:49:37 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15GkPZ-0003IF-00 for linux-xfs@oss.sgi.com; Sun, 01 Jul 2001 18:49:29 +0200 Message-ID: <3B3F5498.14310158@berdmann.de> Date: Sun, 01 Jul 2001 18:49:28 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: Re: xfsrestore freezes on restoring to JFS References: <3B3F5079.F1776C04@berdmann.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Very strange - why was the To: line rewritten? To: Linux XFS Mailing List , "jfs-discussion@oss.software.ibm.com" The To: header I sent: To: Linux XFS Mailing List , "jfs-discussion@oss.software.ibm.com" From owner-linux-xfs@oss.sgi.com Sun Jul 1 10:34:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61HY3226173 for linux-xfs-outgoing; Sun, 1 Jul 2001 10:34:03 -0700 Received: from mail.gmx.net (mail.gmx.net [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61HY1V26169 for ; Sun, 1 Jul 2001 10:34:01 -0700 Received: (qmail 30558 invoked by uid 0); 1 Jul 2001 17:33:54 -0000 Received: from pd901b514.dip.t-dialin.net (HELO nexus.shadowrun.not) (217.1.181.20) by mail.gmx.net (mail10) with SMTP; 1 Jul 2001 17:33:54 -0000 Received: from nexus.shadowrun.not (localhost [127.0.0.1]) by nexus.shadowrun.not (8.12.0.Beta10/8.12.0.Beta10) with ESMTP id f61HWSAN004139 for ; Sun, 1 Jul 2001 19:32:28 +0200 Received: (from fastjack@localhost) by nexus.shadowrun.not (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) id f61HWRah004138 for linux-xfs@oss.sgi.com; Sun, 1 Jul 2001 19:32:27 +0200 From: Martin Maciaszek Date: Sun, 1 Jul 2001 19:32:26 +0200 To: linux-xfs@oss.sgi.com Subject: xfs_shrink? Message-ID: <20010701193226.A682@nexus.shadowrun.not> Mail-Followup-To: mmaciaszek@gmx.net, linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm running xfs on top of lvm without any problems so far. Now I want to remove one of the old drives and replace it with a new drive. As far as I understand it I need to move all PEs from the old drive to the other PVs and then shrink the fs to be able to remove the old drive from the LV. Is there any chance to exchange the old drive without having to do a backup/restore? Is someone working on xfs_shrink? I don't need the drive to be replaced soon, but I can see it coming on the horizon :) Cheers Martin --=20 Remember the good old days, when CPU was singular? --CE+1k2dSO48ffgeK 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 iD8DBQE7P16qtOa6aqYVgUYRAvZuAJwN8L6FAo/vp1YhHG9u4NQOVupsFQCeJnNF 06sYywEJ+ns0IBTIYCW+Ic4= =Sd09 -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-linux-xfs@oss.sgi.com Sun Jul 1 11:34:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61IYGY27692 for linux-xfs-outgoing; Sun, 1 Jul 2001 11:34:16 -0700 Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [212.227.116.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61IYFV27687 for ; Sun, 1 Jul 2001 11:34:15 -0700 Received: from smtp.web.de (smtp01.web.de [194.45.170.210]) by mailgate3.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id f61IYEF19143 for ; Sun, 1 Jul 2001 20:34:14 +0200 Received: from deep-thought by smtp.web.de with smtp (freemail 4.2.2.2 #11) id m15Gm2v-007o3cC; Sun, 1 Jul 2001 20:34 +0200 Date: Sun, 1 Jul 2001 20:34:41 +0200 From: Tilman Sauerbeck To: linux-xfs@oss.sgi.com Subject: root partition with xfs fails to boot correctly Message-Id: <20010701203441.32a5456f.tilman.sauerbeck@web.de> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi all, I have converted all of my partitions to XFS expect the root partition. I did the following to get a XFS based root partition: -did a exact copy on a second hdd -changed the root entry in /etc/lilo.conf -ran lilo -updated /etc/fstab According to the FAQ one can use XFS on a root partition with LILO when LILO is installed in the MBR, which is the case here. But when I want to boot with the XFS root partition, I get a bunch of errors: the system boots, and I get a login, but many services fail etc. I can try to get a more specific description of the errors. I am absolutely sure the copy is an exact one and I just don't know what I could have forgotten to consider :( I am using Kernel 2.4.5-xfs from www.markybob.com/xfsboot. The rest of my XFS partitions work flawlessly. btw: System is Debian testing/woody, LILO is version 21.7.5-1. Any ideas? Thanks in advance, Tilman From owner-linux-xfs@oss.sgi.com Sun Jul 1 11:39:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61IdPx28311 for linux-xfs-outgoing; Sun, 1 Jul 2001 11:39:25 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61IdOV28308 for ; Sun, 1 Jul 2001 11:39:24 -0700 Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id LAA08422 for ; Sun, 1 Jul 2001 11:39:22 -0700 (PDT) mail_from (keith_m@sweeney.demon.co.uk) Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 15Gm3v-000BHt-0V for linux-xfs@oss.sgi.com; Sun, 1 Jul 2001 19:35:15 +0100 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 6004427EF for ; Sun, 1 Jul 2001 19:33:44 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id E9B64125E6; Sun, 1 Jul 2001 19:33:06 +0100 (BST) Date: Sun, 1 Jul 2001 19:33:06 +0100 (BST) From: Keith Matthews Subject: Re[2]: XFS vs. JFS To: Linux XFS Mailing List In-Reply-To: <200107011212.f61CCgM15038@jen.americas.sgi.com> References: <4.3.2.7.2.20010701135304.03a05bb0@pop.xs4all.nl>, <200107011212.f61CCgM15038@jen.americas.sgi.com> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010701183306.E9B64125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f61IdOV28309 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 01 Jul 2001 07:12:42 -0500 Steve Lord > wrote: > The JFS IBM released for Linux comes from the OS/2 version, not AIX. I > do not know if they are on disk compatible or not. Steve Best has given > lots of talks, at least some of them should be out on the net for people > to look at. I have not seen one of his talks for several months, so I > cannot comment on features etc of the 1.0 release. Interestingly I was talking to an IBM guy this weekend at the Manchester Linux Developer's Conference (BTW Steve, David McAllister was there talking about his new outfit, had an interesting chat). The IBM guy was not aware of the OS/2 origin of Linux JFS, but I had heard of it from other sources (I had also heard that someone has back-ported the Linux version to OS/2 and come up with a better product than the original OS/2 one !!). -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:01:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61J1Mo30824 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:01:22 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61J1KV30819 for ; Sun, 1 Jul 2001 12:01:20 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA00266; Sun, 1 Jul 2001 21:01:19 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA16589; Sun, 1 Jul 2001 21:01:18 +0200 (CEST) Date: Sun, 1 Jul 2001 21:01:18 +0200 (CEST) From: Seth Mos To: Martin Maciaszek cc: linux-xfs@oss.sgi.com Subject: Re: xfs_shrink? In-Reply-To: <20010701193226.A682@nexus.shadowrun.not> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001, Martin Maciaszek wrote: > I'm running xfs on top of lvm without any problems so far. Now I > want to remove one of the old drives and replace it with a new > drive. As far as I understand it I need to move all PEs from the > old drive to the other PVs and then shrink the fs to be able to > remove the old drive from the LV. > > Is there any chance to exchange the old drive without having to > do a backup/restore? Is someone working on xfs_shrink? I don't > need the drive to be replaced soon, but I can see it coming on > the horizon :) See FAQ. Bye Seth From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:03:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61J3fk31110 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:03:41 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61J3dV31107 for ; Sun, 1 Jul 2001 12:03:39 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA00990; Sun, 1 Jul 2001 21:03:38 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA16708; Sun, 1 Jul 2001 21:03:38 +0200 (CEST) Date: Sun, 1 Jul 2001 21:03:37 +0200 (CEST) From: Seth Mos To: Tilman Sauerbeck cc: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly In-Reply-To: <20010701203441.32a5456f.tilman.sauerbeck@web.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001, Tilman Sauerbeck wrote: > Hi all, > I have converted all of my partitions to XFS expect the root partition. > I did the following to get a XFS based root partition: > -did a exact copy on a second hdd > -changed the root entry in /etc/lilo.conf > -ran lilo > -updated /etc/fstab > > According to the FAQ one can use XFS on a root partition with LILO when > LILO is installed in the MBR, which is the case here. Can you send the lilo.conf ? > But when I want to boot with the XFS root partition, I get a bunch of > errors: > the system boots, and I get a login, but many services fail etc. I can > try to get a more specific description of the errors. More input please. > I am absolutely sure the copy is an exact one and I just don't know what > I could have forgotten to consider :( making the direcory's for holding the /tmp /var /usr mountpoints or forgetting to make /tmp 777 > I am using Kernel 2.4.5-xfs from www.markybob.com/xfsboot. The rest of > my XFS partitions work flawlessly. > btw: System is Debian testing/woody, LILO is version 21.7.5-1. Should work. Cheers Seth From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:07:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61J7gj31606 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:07:42 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61J7eV31600 for ; Sun, 1 Jul 2001 12:07:41 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA01973; Sun, 1 Jul 2001 21:07:38 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA16944; Sun, 1 Jul 2001 21:07:38 +0200 (CEST) Date: Sun, 1 Jul 2001 21:07:38 +0200 (CEST) From: Seth Mos To: "Bernhard R. Erdmann" cc: Linux XFS Mailing List , "jfs-discussion@oss.software.ibm.com" Subject: Re: XFS marries JFS In-Reply-To: <3B3F4D3A.C42FEA8C@berdmann.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001, Bernhard R. Erdmann wrote: > Hi, > > I just managed to apply the IBM patches for JFS to SGI's CVS checkout of > linux-2.4.6-pre7-xfs. > > jfs-common-v1.0.0-patch applied with no errors, but > jfs-2.4.5-v1.0.0-patch forced me using emacs instead of patch for > include/linux/fs.h (just to add four lines). That's good news. Will take some before xfs apply's that cleanly. > Compiled JFS and LVM as a modules and XFS into the kernel as before. If you can put up the patch somewhere I'll add a link to the FAQ for people interested in getting both running for testing/benchmarketing/crashing/whatever. Cheers Seth From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:44:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61JiSe01571 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:44:28 -0700 Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [212.227.116.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61JiQV01567 for ; Sun, 1 Jul 2001 12:44:26 -0700 Received: from smtp.web.de (smtp01.web.de [194.45.170.210]) by mailgate3.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id f61JiOF08829 for ; Sun, 1 Jul 2001 21:44:24 +0200 Received: from deep-thought by smtp.web.de with smtp (freemail 4.2.2.2 #11) id m15Gn8q-007o51C; Sun, 1 Jul 2001 21:44 +0200 Date: Sun, 1 Jul 2001 21:44:53 +0200 From: Tilman Sauerbeck To: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Message-Id: <20010701214453.3e1bafa1.tilman.sauerbeck@web.de> In-Reply-To: References: <20010701203441.32a5456f.tilman.sauerbeck@web.de> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > According to the FAQ one can use XFS on a root partition with LILO > when > > LILO is installed in the MBR, which is the case here. > > Can you send the lilo.conf ? --- lba32 boot=/dev/hda root=/dev/hda3 install=/boot/boot.b map=/boot/map delay=20 vga=normal default=Linux image=/vmlinuz label=Linux read-only image=/vmlinuz.old label=LinuxOLD read-only optional --- That's it. [errors] > More input please. I could not get all of the errors, because there are many lines like this: changing ownership of /dev/tty* : read-only filesystem After this the system complains because /etc and /proc are not mounted. I think all of my partitions are not being mounted, e.g. binaries in /usr are not found. As /etc/fstab says for the root partition: defaults,errors=remount-ro This makes sense: The partitions cannot be mounted, but the root partition is remounted read only... Both XFS options are compiled into the kernel (i.e. page buffer support and xfs support). > > I am absolutely sure the copy is an exact one and I just don't know > what > > I could have forgotten to consider :( > > making the direcory's for holding the /tmp /var /usr mountpoints or > forgetting to make /tmp 777 No, all mount points exist. The permissions for /tmp are alright, too. From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:50:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61JoFS01990 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:50:15 -0700 Received: from ente.berdmann.de (p3E9C25A1.dip.t-dialin.net [62.156.37.161]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61JoDV01987 for ; Sun, 1 Jul 2001 12:50:13 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15GnEM-0004Ed-00; Sun, 01 Jul 2001 21:50:06 +0200 Message-ID: <3B3F7EEE.6752B5BF@berdmann.de> Date: Sun, 01 Jul 2001 21:50:06 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Seth Mos CC: Linux XFS Mailing List , "jfs-discussion@oss.software.ibm.com" Subject: Re: XFS marries JFS References: Content-Type: multipart/mixed; boundary="------------C901A676EF48C97EA9DB23A8" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------C901A676EF48C97EA9DB23A8 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > If you can put up the patch somewhere I'll add a link to the FAQ for > people interested in getting both running for > testing/benchmarketing/crashing/whatever. here it is... cd /usr/src/linux patch -p1 < /path/to/jfs-common-v1.0.0-patch patch -p1 < /path/to/jfs-2.4.5-v1.0.0-patch patch < /path/to/fs.h.4jfs.patch --------------C901A676EF48C97EA9DB23A8 Content-Type: text/plain; charset=us-ascii; name="fs.h.4jfs.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="fs.h.4jfs.patch" --- include/linux/fs.h.orig Thu Jun 14 10:08:17 2001 +++ include/linux/fs.h Sun Jul 1 14:32:30 2001 @@ -322,6 +322,7 @@ #include #include #include +#include /* * Attribute flags. These should be or-ed together to figure out what @@ -498,6 +499,7 @@ struct socket socket_i; struct usbdev_inode_info usbdev_i; struct xfs_inode_info xfs_i; + struct jfs_inode_info jfs_i; void *generic_ip; } u; }; @@ -675,6 +677,7 @@ #include #include #include +#include extern struct list_head super_blocks; @@ -728,6 +731,7 @@ struct ncp_sb_info ncpfs_sb; struct usbdev_sb_info usbdevfs_sb; struct xfs_sb_info xfs_sb; + struct jfs_sb_info jfs_sb; void *generic_sbp; } u; /* --------------C901A676EF48C97EA9DB23A8-- From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:52:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61JqjC02157 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:52:45 -0700 Received: from smtp1.cern.ch (smtp1.cern.ch [137.138.128.38]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61JqiV02152 for ; Sun, 1 Jul 2001 12:52:44 -0700 Received: from lxplus001.cern.ch (IDENT:root@lxplus001.cern.ch [137.138.161.126]) by smtp1.cern.ch (8.9.3/8.9.3) with ESMTP id VAA15772; Sun, 1 Jul 2001 21:52:37 +0200 (MET DST) Received: (from fuji@localhost) by lxplus001.cern.ch (8.9.3/8.9.3) id VAA00446; Sun, 1 Jul 2001 21:52:36 +0200 Date: Sun, 1 Jul 2001 21:52:36 +0200 From: Peter.Kelemen@cern.ch To: Keith Matthews Cc: linux-xfs@oss.sgi.com Subject: Re: XFS vs. JFS Message-ID: <20010701215236.A22808@lxplus001.cern.ch> Reply-To: Peter.Kelemen@cern.ch References: <4.3.2.7.2.20010701135304.03a05bb0@pop.xs4all.nl>, <200107011212.f61CCgM15038@jen.americas.sgi.com> <20010701183306.E9B64125E6@rebutia.sweeney.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20010701183306.E9B64125E6@rebutia.sweeney.demon.co.uk> User-Agent: Mutt/1.3.19i 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-MIME-Autoconverted: from 8bit to quoted-printable by smtp1.cern.ch id VAA15772 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f61JqjV02155 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk * Keith Matthews (keith_m@sweeney.demon.co.uk) [20010701 19:33]: > The IBM guy was not aware of the OS/2 origin of Linux JFS, but I > had heard of it from other sources (I had also heard that > someone has back-ported the Linux version to OS/2 and come up > with a better product than the original OS/2 one !!). I have talked with Steve Best and the AlinkA people couple of months ago to clarify the origin of JFS for Linux. Steve said that JFS for Linux was a direct port of OS/2 JFS which had been a project from scratch starting in 1995---it has no relations to the over 10 years old AIX JFS codebase. However, this new JFS codebase is expected to appear in IBM's AIX 5L product line as well. Peter -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen Péter / \ / \ Peter.Kelemen@cern.ch .+' `+...+' `+...+' `+...+' `+...+' From owner-linux-xfs@oss.sgi.com Sun Jul 1 12:54:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61Jslc02349 for linux-xfs-outgoing; Sun, 1 Jul 2001 12:54:47 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61JskV02345 for ; Sun, 1 Jul 2001 12:54:46 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA10456; Sun, 1 Jul 2001 21:54:45 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA20613; Sun, 1 Jul 2001 21:54:44 +0200 (CEST) Date: Sun, 1 Jul 2001 21:54:44 +0200 (CEST) From: Seth Mos To: Tilman Sauerbeck cc: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly In-Reply-To: <20010701214453.3e1bafa1.tilman.sauerbeck@web.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001, Tilman Sauerbeck wrote: > > > According to the FAQ one can use XFS on a root partition with LILO > > when > > > LILO is installed in the MBR, which is the case here. > > > > Can you send the lilo.conf ? > > --- > lba32 > boot=/dev/hda > root=/dev/hda3 > install=/boot/boot.b > map=/boot/map > delay=20 > vga=normal > default=Linux > > image=/vmlinuz > label=Linux > read-only > > image=/vmlinuz.old > label=LinuxOLD > read-only > optional > --- > > That's it. Nothing wrong... > [errors] > > More input please. > > I could not get all of the errors, because there are many lines like > this: > changing ownership of /dev/tty* : read-only filesystem > After this the system complains because /etc and /proc are not mounted. > I think all of my partitions are not being mounted, e.g. binaries in > /usr are not found. me thinking devfs. It didn't accidentaly get compiled in? It looks strange or I am missing something obvious. > As /etc/fstab says for the root partition: > defaults,errors=remount-ro > > This makes sense: The partitions cannot be mounted, but the root > partition is remounted read only... Seems like not finding the devices for mounting. > Both XFS options are compiled into the kernel (i.e. page buffer support > and xfs support). > > > > I am absolutely sure the copy is an exact one and I just don't know > > what > > > I could have forgotten to consider :( > > > > making the direcory's for holding the /tmp /var /usr mountpoints or > > forgetting to make /tmp 777 > > No, all mount points exist. The permissions for /tmp are alright, too. My brain is not quite working correctly at the moment so if anybody has a good idea they may stand up now. I have a bad headache all day long. So that does not make it easier. Cheers seth From owner-linux-xfs@oss.sgi.com Sun Jul 1 13:37:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61KbWm05432 for linux-xfs-outgoing; Sun, 1 Jul 2001 13:37:32 -0700 Received: from mail.gmx.net (mail.gmx.de [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61KbUV05429 for ; Sun, 1 Jul 2001 13:37:30 -0700 Received: (qmail 14918 invoked by uid 0); 1 Jul 2001 20:37:23 -0000 Received: from pd901b8b5.dip.t-dialin.net (HELO nexus.shadowrun.not) (217.1.184.181) by mail.gmx.net (mp004-rz3) with SMTP; 1 Jul 2001 20:37:23 -0000 Received: from nexus.shadowrun.not (localhost [127.0.0.1]) by nexus.shadowrun.not (8.12.0.Beta10/8.12.0.Beta10) with ESMTP id f61KaXAN005267 for ; Sun, 1 Jul 2001 22:36:33 +0200 Received: (from fastjack@localhost) by nexus.shadowrun.not (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) id f61KaX2l005266 for linux-xfs@oss.sgi.com; Sun, 1 Jul 2001 22:36:33 +0200 From: Martin Maciaszek Date: Sun, 1 Jul 2001 22:36:33 +0200 To: linux-xfs@oss.sgi.com Subject: Re: xfs_shrink? Message-ID: <20010701223633.B5176@nexus.shadowrun.not> Mail-Followup-To: mmaciaszek@gmx.net, linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xXmbgvnjoT4axfJE" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --xXmbgvnjoT4axfJE Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 01, 2001 at 09:01:18PM +0200, Seth Mos wrote: > On Sun, 1 Jul 2001, Martin Maciaszek wrote: >=20 > > I'm running xfs on top of lvm without any problems so far. Now I > > want to remove one of the old drives and replace it with a new > > drive. As far as I understand it I need to move all PEs from the > > old drive to the other PVs and then shrink the fs to be able to > > remove the old drive from the LV. > >=20 > > Is there any chance to exchange the old drive without having to > > do a backup/restore? Is someone working on xfs_shrink? I don't > > need the drive to be replaced soon, but I can see it coming on > > the horizon :) >=20 > See FAQ. >=20 I read the FAQ but this didn't satisfy me. I still have the hope that someone is working on it. I just like to know whether it will be possible in the (near) future to shrink the file system. Cheers Martin --=20 MAC user's dynamic debugging list evaluator? Never heard of that. --xXmbgvnjoT4axfJE 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 iD8DBQE7P4nRtOa6aqYVgUYRAnA0AKDs+Pug5ZsM4/RCC7qJTKYiz0TvHwCeN7QZ cebMCJtN7yGcyFhptSpeY9E= =ilpj -----END PGP SIGNATURE----- --xXmbgvnjoT4axfJE-- From owner-linux-xfs@oss.sgi.com Sun Jul 1 14:49:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61LnNM10271 for linux-xfs-outgoing; Sun, 1 Jul 2001 14:49:23 -0700 Received: from citadel.oehansen.pp.se (sdu164-205.ppp.algonet.se [195.163.205.164]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61LnKV10265 for ; Sun, 1 Jul 2001 14:49:21 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f61Lovd08371; Sun, 1 Jul 2001 23:50:59 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: Seth Mos , Tilman Sauerbeck Subject: Re: root partition with xfs fails to boot correctly Date: Sun, 1 Jul 2001 23:50:57 +0200 X-Mailer: KMail [version 1.2] Cc: linux-xfs@oss.sgi.com References: In-Reply-To: X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 X-MIME-Autoconverted: from 8bit to quoted-printable by citadel.oehansen.pp.se id f61Lovd08371 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f61LnMV10267 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk sunnudagur 1. júlí 2001 21:54, Seth Mos skrifaði: > On Sun, 1 Jul 2001, Tilman Sauerbeck wrote: > > changing ownership of /dev/tty* : read-only filesystem > > After this the system complains because /etc and /proc are not mounted. > > I think all of my partitions are not being mounted, e.g. binaries in > > /usr are not found. > > me thinking devfs. > It didn't accidentaly get compiled in? > It looks strange or I am missing something obvious. > I did the same over here, without problems... and my root partition is now XFS. However, I used a changed vanilla 2.4.5, and when I used the 2.4.2/3 production kernels, I got the same errors as in this case. The reason was LABEL mounted partitions. The answer was to remove the LABEL= from /etc/fstab and insert the partition names there instead. Orn From owner-linux-xfs@oss.sgi.com Sun Jul 1 15:04:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61M4mZ11656 for linux-xfs-outgoing; Sun, 1 Jul 2001 15:04:48 -0700 Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [212.227.116.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61M4kV11651 for ; Sun, 1 Jul 2001 15:04:46 -0700 Received: from smtp.web.de (smtp01.web.de [194.45.170.210]) by mailgate3.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id f61M4iF22135 for ; Mon, 2 Jul 2001 00:04:44 +0200 Received: from deep-thought by smtp.web.de with smtp (freemail 4.2.2.2 #11) id m15GpKd-007o4UC; Mon, 2 Jul 2001 00:04 +0200 Date: Mon, 2 Jul 2001 00:05:10 +0200 From: Tilman Sauerbeck To: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Message-Id: <20010702000510.3c4caf63.tilman.sauerbeck@web.de> In-Reply-To: References: <20010701214453.3e1bafa1.tilman.sauerbeck@web.de> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk [lilo.conf] > Nothing wrong... :) > > [errors] > me thinking devfs. > It didn't accidentaly get compiled in? > It looks strange or I am missing something obvious. Nope, I don't use devfs and it's not compiled into the kernel. > > As /etc/fstab says for the root partition: > > defaults,errors=remount-ro > > > > This makes sense: The partitions cannot be mounted, but the root > > partition is remounted read only... > > Seems like not finding the devices for mounting. > My brain is not quite working correctly at the moment so if anybody > has a > good idea they may stand up now. I have a bad headache all day long. > So > that does not make it easier. *sigh* I just don't see what I'm doing wrong... remember: The same data, the same kernel etc work with ext2 :( Tilman From owner-linux-xfs@oss.sgi.com Sun Jul 1 15:06:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61M6sU11924 for linux-xfs-outgoing; Sun, 1 Jul 2001 15:06:54 -0700 Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [212.227.116.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61M6qV11906 for ; Sun, 1 Jul 2001 15:06:53 -0700 Received: from smtp.web.de (smtp01.web.de [194.45.170.210]) by mailgate3.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id f61M6pF12528 for ; Mon, 2 Jul 2001 00:06:51 +0200 Received: from deep-thought by smtp.web.de with smtp (freemail 4.2.2.2 #11) id m15GpMg-007o4RC; Mon, 2 Jul 2001 00:06 +0200 Date: Mon, 2 Jul 2001 00:07:19 +0200 From: Tilman Sauerbeck To: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Message-Id: <20010702000719.7c6a0637.tilman.sauerbeck@web.de> In-Reply-To: <01070123505701.01719@citadel.oehansen.pp.se> References: <01070123505701.01719@citadel.oehansen.pp.se> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I did the same over here, without problems... and my root partition > is now > XFS. However, I used a changed vanilla 2.4.5, and when I used the > 2.4.2/3 > production kernels, I got the same errors as in this case. The reason > was > LABEL mounted partitions. The answer was to remove the LABEL= from > /etc/fstab and insert the partition names there instead. I don't use those labels. I'm going to patch the kernel on my own if there's no other solution... very strange... Tilman From owner-linux-xfs@oss.sgi.com Sun Jul 1 15:16:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61MG5213004 for linux-xfs-outgoing; Sun, 1 Jul 2001 15:16:05 -0700 Received: from citadel.oehansen.pp.se (sdu164-205.ppp.algonet.se [195.163.205.164]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61MG2V13000 for ; Sun, 1 Jul 2001 15:16:03 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f61MHld08477; Mon, 2 Jul 2001 00:17:47 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: Tilman Sauerbeck , linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Date: Mon, 2 Jul 2001 00:17:47 +0200 X-Mailer: KMail [version 1.2] References: <01070123505701.01719@citadel.oehansen.pp.se> <20010702000719.7c6a0637.tilman.sauerbeck@web.de> In-Reply-To: <20010702000719.7c6a0637.tilman.sauerbeck@web.de> X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 X-MIME-Autoconverted: from 8bit to quoted-printable by citadel.oehansen.pp.se id f61MHld08477 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f61MG4V13002 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk mánudagur 2. júlí 2001 00:07, Tilman Sauerbeck skrifaði: > > I did the same over here, without problems... and my root partition > > is now > > XFS. However, I used a changed vanilla 2.4.5, and when I used the > > 2.4.2/3 > > production kernels, I got the same errors as in this case. The reason > > was > > LABEL mounted partitions. The answer was to remove the LABEL= from > > /etc/fstab and insert the partition names there instead. > > I don't use those labels. > How did you backup/restore the root fs? Have you tried booting the system, in single user mode... that way it won't really matter if it doesn't find any partitions, as long as it finds the root partition (which lilo sets)? There you could *trace* the boot script, and see where it goes wrong? Orn From owner-linux-xfs@oss.sgi.com Sun Jul 1 15:28:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61MS0W14287 for linux-xfs-outgoing; Sun, 1 Jul 2001 15:28:00 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61MS0V14284 for ; Sun, 1 Jul 2001 15:28:00 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA02525 for ; Sun, 1 Jul 2001 15:27:59 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id PAA24026; Sun, 1 Jul 2001 15:27:26 -0700 (PDT) Message-ID: <3B3FA33D.3B46D94A@sgi.com> Date: Sun, 01 Jul 2001 17:25:01 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Martin Maciaszek CC: linux-xfs@oss.sgi.com Subject: Re: xfs_shrink? References: <20010701223633.B5176@nexus.shadowrun.not> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Martin Maciaszek wrote: > I read the FAQ but this didn't satisfy me. I still have the hope > that someone is working on it. I just like to know whether it > will be possible in the (near) future to shrink the file system. Ok, try the archives then. :) http://oss.sgi.com/projects/xfs/mail_archive/0102/msg00030.html -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 1 15:35:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61MZ7j15044 for linux-xfs-outgoing; Sun, 1 Jul 2001 15:35:07 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61MZ7V15040 for ; Sun, 1 Jul 2001 15:35:07 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA01029 for ; Sun, 1 Jul 2001 15:35:06 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id PAA71907; Sun, 1 Jul 2001 15:34:33 -0700 (PDT) Message-ID: <3B3FA4E8.6067E85A@sgi.com> Date: Sun, 01 Jul 2001 17:32:08 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Tilman Sauerbeck CC: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly References: <20010701203441.32a5456f.tilman.sauerbeck@web.de> <20010701214453.3e1bafa1.tilman.sauerbeck@web.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tilman Sauerbeck wrote: > > More input please. > > I could not get all of the errors, because there are many lines like > this: > changing ownership of /dev/tty* : read-only filesystem Is this the FIRST error in the log, or did something go wrong before this? What's the first thing that looks like trouble? Lots of people are running XFS on root, I don't expect that it's an XFS problem, but hopefully we can help get it sorted out. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 1 15:47:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61Ml8G16056 for linux-xfs-outgoing; Sun, 1 Jul 2001 15:47:08 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61Ml7V16053 for ; Sun, 1 Jul 2001 15:47:07 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip68.idcomm.com [209.60.72.195] (may be forged)) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f61Mmxl06166 for ; Sun, 1 Jul 2001 16:49:00 -0600 Message-ID: <3B3FA8DB.220C4937@idcomm.com> Date: Sun, 01 Jul 2001 16:48:59 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly References: <20010701214453.3e1bafa1.tilman.sauerbeck@web.de> <20010702000510.3c4caf63.tilman.sauerbeck@web.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tilman Sauerbeck wrote: > > [lilo.conf] > > > Nothing wrong... > > :) > > > > [errors] > > me thinking devfs. > > It didn't accidentaly get compiled in? > > It looks strange or I am missing something obvious. > > Nope, I don't use devfs and it's not compiled into the kernel. > > > > As /etc/fstab says for the root partition: > > > defaults,errors=remount-ro > > > > > > This makes sense: The partitions cannot be mounted, but the root > > > partition is remounted read only... > > > > Seems like not finding the devices for mounting. > > > My brain is not quite working correctly at the moment so if anybody > > has a > > good idea they may stand up now. I have a bad headache all day long. > > So > > that does not make it easier. > > *sigh* > I just don't see what I'm doing wrong... remember: > The same data, the same kernel etc work with ext2 :( > > Tilman When I used the copy of partition for migration, I discovered that the device special files were not correctly copied. I had to manually reconstruct this (some of it was not in MAKEDEV). I also found the better way to mirror was: find /SomeSource -print -xdev | cpio -pdm SomeDestination That works with device special files. I know you said you were positive about the copy of partitions, but it sounds like exact copy failed. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Sun Jul 1 16:04:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61N4lZ18259 for linux-xfs-outgoing; Sun, 1 Jul 2001 16:04:47 -0700 Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [212.227.116.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61N4jV18255 for ; Sun, 1 Jul 2001 16:04:46 -0700 Received: from smtp.web.de (smtp01.web.de [194.45.170.210]) by mailgate3.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id f61N4iF01660 for ; Mon, 2 Jul 2001 01:04:44 +0200 Received: from deep-thought by smtp.web.de with smtp (freemail 4.2.2.2 #11) id m15GqGh-007o4GC; Mon, 2 Jul 2001 01:04 +0200 Date: Mon, 2 Jul 2001 01:05:12 +0200 From: Tilman Sauerbeck To: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Message-Id: <20010702010512.122a1e4f.tilman.sauerbeck@web.de> In-Reply-To: <3B3FA8DB.220C4937@idcomm.com> References: <20010701214453.3e1bafa1.tilman.sauerbeck@web.de> <20010702000510.3c4caf63.tilman.sauerbeck@web.de> <3B3FA8DB.220C4937@idcomm.com> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > When I used the copy of partition for migration, I discovered that the > device special files were not correctly copied. I had to manually > reconstruct this (some of it was not in MAKEDEV). I also found the > better way to mirror was: > find /SomeSource -print -xdev | cpio -pdm SomeDestination > > That works with device special files. I know you said you were > positive > about the copy of partitions, but it sounds l When I copy the contents of the copy back to the ext2 partition, I can boot from it without any problems, so the data is okay. btw: I used "cp -dpR * dest/" Tilman From owner-linux-xfs@oss.sgi.com Sun Jul 1 16:37:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f61Nbeq22006 for linux-xfs-outgoing; Sun, 1 Jul 2001 16:37:40 -0700 Received: from piro.kabuki.sfarc.net (postfix@[203.36.158.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f61NbcV22003 for ; Sun, 1 Jul 2001 16:37:39 -0700 Received: by piro.kabuki.sfarc.net (Postfix, from userid 1000) id E5BFD14B52BB; Mon, 2 Jul 2001 09:37:54 +1000 (EST) Date: Mon, 2 Jul 2001 09:37:54 +1000 From: Daniel Stone To: Tilman Sauerbeck Cc: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Message-ID: <20010702093754.C12762@kabuki.sfarc.net> Mail-Followup-To: Tilman Sauerbeck , linux-xfs@oss.sgi.com References: <01070123505701.01719@citadel.oehansen.pp.se> <20010702000719.7c6a0637.tilman.sauerbeck@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010702000719.7c6a0637.tilman.sauerbeck@web.de> User-Agent: Mutt/1.3.18i Organisation: Sadly lacking Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 02, 2001 at 12:07:19AM +0200, Tilman Sauerbeck wrote: > > I did the same over here, without problems... and my root partition > > is now > > XFS. However, I used a changed vanilla 2.4.5, and when I used the > > 2.4.2/3 > > production kernels, I got the same errors as in this case. The reason > > was > > LABEL mounted partitions. The answer was to remove the LABEL= from > > /etc/fstab and insert the partition names there instead. > > I don't use those labels. > > I'm going to patch the kernel on my own if there's no other solution... > very strange... "Read-only file system" should be telling you something. Edit /etc/fstab, and change the options for /, to include rw, and remove the read-only line from lilo. :) d -- Daniel Stone "can NE1 help me aim nuclear weaponz????? /MSG ME!!" From owner-linux-xfs@oss.sgi.com Sun Jul 1 17:13:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f620DMF25944 for linux-xfs-outgoing; Sun, 1 Jul 2001 17:13:22 -0700 Received: from mail.rapidsite.net ([209.238.184.57]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f620DKV25940 for ; Sun, 1 Jul 2001 17:13:20 -0700 Received: from www.75andsunny.com (168.143.156.115) by mail13.ameritech-hosting.net (RS ver 1.0.57s) with SMTP id 013824061 for ; Sun, 1 Jul 2001 20:13:06 -0400 (EDT) Message-ID: <001001c1028b$c4577460$6401a8c0@bogus> From: "John Stevens" To: Subject: Install issue Date: Sun, 1 Jul 2001 17:13:05 -0700 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C10251.179853F0" 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 X-Loop-Detect: 1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C10251.179853F0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable installing RH 7.1 works fine. When I try to install from the SGI boot CD the install will fail. I = have tried increasing the swap space to 2047, I have selected a very = minimal installation (NFS and Samba only) and the installation still = fails. =20 After the X server starts during install I get the following messages = when the installation dies: python: header.c:241: regionSwab: Assertion `ie.info.type .=3D 0 && = ie.info.type ,=3D 9` failed. install exited abnormally sending termination signals...done sending kill signals...done disabling swap ... /tmp/swap/sda5 unmounting filesystems... /mnt/sysimage/boot /mnt/sysimage/proc /mnt/sysimage umount failed (16) /mnt/runtime /mnt/source /mnt/pts /proc you may safely reboot your system The hardware is an Intel SBT2 server board with dual 1 Ghz Xeon proc, 2 = x 256 MB Kingston memory. =20 Any ideas as to what to try?? If you need addational info or want me to = try something please let me know. John Stevens john@75andsunny.com Graphics Systems Engineer=20 Encore Video Hollywood 323-512-3532 jstevens@encorevideo.com ------=_NextPart_000_000D_01C10251.179853F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
installing RH 7.1 works = fine.
 
When I try to install from the SGI boot = CD the=20 install will fail.  I have tried increasing the swap space to 2047, = I have=20 selected a very minimal installation (NFS and Samba only)  and the=20 installation still fails. 
 
After the X server starts during = install I get the=20 following messages when the installation dies:
python: header.c:241: regionSwab: = Assertion=20 `ie.info.type .=3D 0 && ie.info.type ,=3D 9` = failed.
install exited abnormally
sending termination = signals...done
sending kill = signals...done
disabling swap ...
       =20 /tmp/swap/sda5
unmounting filesystems...
       =20 /mnt/sysimage/boot
       =20 /mnt/sysimage/proc
        = /mnt/sysimage=20 umount failed (16)
       =20 /mnt/runtime
       =20 /mnt/source
       =20 /mnt/pts
       =20 /proc
you may safely reboot your = system
 
 
The hardware is an Intel SBT2 server = board with=20 dual 1 Ghz Xeon proc, 2 x 256 MB Kingston = memory.  
 
Any ideas as to what to try??  If = you need=20 addational info or want me to try something please let me = know.
 
 
John Stevens
john@75andsunny.com
 
Graphics Systems Engineer
Encore Video
Hollywood
323-512-3532
jstevens@encorevideo.com
 
------=_NextPart_000_000D_01C10251.179853F0-- From owner-linux-xfs@oss.sgi.com Sun Jul 1 19:42:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f622go807076 for linux-xfs-outgoing; Sun, 1 Jul 2001 19:42:50 -0700 Received: from smoke.zoop.org (toad-1348-51.dslbr.toad.net [162.33.229.51] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f622gnV07070 for ; Sun, 1 Jul 2001 19:42:49 -0700 Received: from localhost (localhost [127.0.0.1]) by smoke.zoop.org (8.11.2/8.11.2) with ESMTP id f622gV813769 for ; Sun, 1 Jul 2001 22:42:42 -0400 Date: Sun, 1 Jul 2001 22:42:31 -0400 (EDT) From: Karl Hiramoto X-X-Sender: To: Subject: removeing a non existant file.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk how can i remove this file? I ran the latest version of xfs_repair after i booted from a cdrom already. [root@smoke /etc]# ls -la socks5.conf ls: socks5.conf: No such file or directory [root@smoke /etc]# ls -la socks5* -rw-r--r-- 1 root root 75 May 21 20:36 socks5.conf -rw-r--r-- 1 root root 109 May 23 19:13 socks5.conf2 -rw-r--r-- 1 root root 109 May 21 20:50 socks5.conf.bak [root@smoke /etc]# rm socks5.conf rm: cannot remove `socks5.conf': No such file or directory [root@smoke /etc]# rm -i socks5.conf rm: cannot remove `socks5.conf': No such file or directory [root@smoke /etc]# thanks.. === Karl Hiramoto Home: 978-266-1962 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.ws/ PGP key available Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 ICQ#'s = 52003056 & 16617452 --- inbox, n.: A catch basin for everything you don't want to deal with, but are afraid to throw away. From owner-linux-xfs@oss.sgi.com Sun Jul 1 19:54:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f622spK07875 for linux-xfs-outgoing; Sun, 1 Jul 2001 19:54:51 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f622soV07872 for ; Sun, 1 Jul 2001 19:54:50 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f622sEf29764; Sun, 1 Jul 2001 22:54:14 -0400 Date: Sun, 1 Jul 2001 22:54:14 -0400 From: Alan Eldridge To: Karl Hiramoto Cc: Linux XFS Mailing List Subject: Re: removeing a non existant file.. Message-ID: <20010701225414.A29761@wwweasel.geeksrus.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from karl@hiramoto.ws on Sun, Jul 01, 2001 at 10:42:31PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 01, 2001 at 10:42:31PM -0400, Karl Hiramoto wrote: > >how can i remove this file? I ran the latest version of xfs_repair >after i booted from a cdrom already. >[root@smoke /etc]# ls -la socks5.conf >ls: socks5.conf: No such file or directory >[root@smoke /etc]# ls -la socks5* >-rw-r--r-- 1 root root 75 May 21 20:36 socks5.conf >-rw-r--r-- 1 root root 109 May 23 19:13 socks5.conf2 >-rw-r--r-- 1 root root 109 May 21 20:50 Well, you've established that this works. I suspect the file might not be named what it looks like. Why not do "rm -i socks5*" and then answer y/n for each file? -- Alan Eldridge "Gee, Bill, what do you want to do tonight?" "The same thing we do every night, Steve. Try to take over the world!" From owner-linux-xfs@oss.sgi.com Sun Jul 1 19:55:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f622tjo07936 for linux-xfs-outgoing; Sun, 1 Jul 2001 19:55:45 -0700 Received: from duval.se.mediaone.net (duval.se.mediaone.net [24.129.0.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f622thV07932 for ; Sun, 1 Jul 2001 19:55:44 -0700 Received: from enterprise (rr-163-49-70.atl.mediaone.net [24.163.49.70]) by duval.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f622tJP07143; Sun, 1 Jul 2001 22:55:19 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: "'Karl Hiramoto'" , Subject: RE: removeing a non existant file.. Date: Sun, 1 Jul 2001 22:54:42 -0400 Message-ID: <000e01c102a2$58413330$0101a8c0@enterprise> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Outlook, Build 10.0.2616 Importance: High X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 In-Reply-To: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Try: rm -i socks5* Justin -----Original Message----- From: owner-linux-xfs@oss.sgi.com [mailto:owner-linux-xfs@oss.sgi.com] On Behalf Of Karl Hiramoto Sent: Sunday, July 01, 2001 10:43 PM To: linux-xfs@oss.sgi.com Subject: removeing a non existant file.. how can i remove this file? I ran the latest version of xfs_repair after i booted from a cdrom already. [root@smoke /etc]# ls -la socks5.conf ls: socks5.conf: No such file or directory [root@smoke /etc]# ls -la socks5* -rw-r--r-- 1 root root 75 May 21 20:36 socks5.conf -rw-r--r-- 1 root root 109 May 23 19:13 socks5.conf2 -rw-r--r-- 1 root root 109 May 21 20:50 socks5.conf.bak [root@smoke /etc]# rm socks5.conf rm: cannot remove `socks5.conf': No such file or directory [root@smoke /etc]# rm -i socks5.conf rm: cannot remove `socks5.conf': No such file or directory [root@smoke /etc]# thanks.. === Karl Hiramoto Home: 978-266-1962 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.ws/ PGP key available Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 ICQ#'s = 52003056 & 16617452 --- inbox, n.: A catch basin for everything you don't want to deal with, but are afraid to throw away. From owner-linux-xfs@oss.sgi.com Sun Jul 1 20:01:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62310v08332 for linux-xfs-outgoing; Sun, 1 Jul 2001 20:01:00 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6230wV08328 for ; Sun, 1 Jul 2001 20:00:58 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id UAA13643 for ; Sun, 1 Jul 2001 20:00:50 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 MAA15189; Mon, 2 Jul 2001 12:59:38 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Karl Hiramoto cc: linux-xfs@oss.sgi.com Subject: Re: removeing a non existant file.. In-reply-to: Your message of "Sun, 01 Jul 2001 22:42:31 -0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Jul 2001 12:59:38 +1000 Message-ID: <23061.994042778@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 1 Jul 2001 22:42:31 -0400 (EDT), Karl Hiramoto wrote: >how can i remove this file? I ran the latest version of xfs_repair >after i booted from a cdrom already. >[root@smoke /etc]# ls -la socks5.conf >ls: socks5.conf: No such file or directory >[root@smoke /etc]# ls -la socks5* >-rw-r--r-- 1 root root 75 May 21 20:36 socks5.conf >[root@smoke /etc]# rm socks5.conf >rm: cannot remove `socks5.conf': No such file or directory Is there any chance that the filename contains non-graphic characters? Does ls -lb socks5.conf* show any extra characters in the filename? From owner-linux-xfs@oss.sgi.com Sun Jul 1 20:14:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f623EoS08814 for linux-xfs-outgoing; Sun, 1 Jul 2001 20:14:50 -0700 Received: from smoke.zoop.org (toad-1348-51.dslbr.toad.net [162.33.229.51] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f623EmV08810 for ; Sun, 1 Jul 2001 20:14:48 -0700 Received: from localhost (localhost [127.0.0.1]) by smoke.zoop.org (8.11.2/8.11.2) with ESMTP id f623EV813910 for ; Sun, 1 Jul 2001 23:14:42 -0400 Date: Sun, 1 Jul 2001 23:14:31 -0400 (EDT) From: Karl Hiramoto X-X-Sender: To: Linux XFS Mailing List Subject: Re: removeing a non existant file.. In-Reply-To: <20010701225414.A29761@wwweasel.geeksrus.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk thanks.. I feel kinda dumb now.. I'm not sure on how it got that way in the first place though.. On Sun, 1 Jul 2001, Alan Eldridge wrote: > On Sun, Jul 01, 2001 at 10:42:31PM -0400, Karl Hiramoto wrote: > > > >how can i remove this file? I ran the latest version of xfs_repair > >after i booted from a cdrom already. > > >[root@smoke /etc]# ls -la socks5.conf > >ls: socks5.conf: No such file or directory > >[root@smoke /etc]# ls -la socks5* > >-rw-r--r-- 1 root root 75 May 21 20:36 socks5.conf > >-rw-r--r-- 1 root root 109 May 23 19:13 socks5.conf2 > >-rw-r--r-- 1 root root 109 May 21 20:50 > > Well, you've established that this works. I suspect the file might not be > named what it looks like. > > Why not do "rm -i socks5*" and then answer y/n for each file? > > -- === Karl Hiramoto Home: 978-266-1962 Cell: 508-517-4819 Personal web page: http://karl.hiramoto.ws/ PGP key available Zoop Productions: http://www.zoop.org/ KTEQ Rapid City: http://www.kteq.org/ AOL IM ID = KarlH420 ICQ#'s = 52003056 & 16617452 --- inbox, n.: A catch basin for everything you don't want to deal with, but are afraid to throw away. From owner-linux-xfs@oss.sgi.com Sun Jul 1 20:30:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f623UXp09575 for linux-xfs-outgoing; Sun, 1 Jul 2001 20:30:33 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f623UWV09572 for ; Sun, 1 Jul 2001 20:30:32 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA04494 for ; Sun, 1 Jul 2001 20:30:31 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id UAA82743; Sun, 1 Jul 2001 20:29:58 -0700 (PDT) Message-ID: <3B3FEA1D.2D4F8A03@sgi.com> Date: Sun, 01 Jul 2001 22:27:25 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: John Stevens CC: linux-xfs@oss.sgi.com Subject: Re: Install issue References: <001001c1028b$c4577460$6401a8c0@bogus> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > John Stevens wrote: > After the X server starts during install I get the following messages > when the installation dies: > python: header.c:241: regionSwab: Assertion `ie.info.type .= 0 && > ie.info.type ,= 9` failed. Hm, that's a new one... looks like Python itself is dying, not Anaconda. I don't have the Python source here to see what header.c is trying to do... Does a text-based install work? (Oh, and is this the 1.0 installer?) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 1 20:34:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f623Yjn10029 for linux-xfs-outgoing; Sun, 1 Jul 2001 20:34:45 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f623YhV10026 for ; Sun, 1 Jul 2001 20:34:43 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id FAA725680 for ; Mon, 2 Jul 2001 05:34:40 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id NAA06174 for linux-xfs@oss.sgi.com; Mon, 2 Jul 2001 13:33:23 +1000 (EST) Date: Mon, 2 Jul 2001 13:33:23 +1000 (EST) From: Nathan Scott Message-Id: <200107020333.NAA06174@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - ia64 + ACLs, extended attributes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk For Keith. Date: Sun Jul 1 20:31:14 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98035a linux/arch/ia64/kernel/entry.S - 1.13 linux/include/asm-ia64/unistd.h - 1.11 cmd/attr/libattr/attr.c - 1.7 cmd/attr/VERSION - 1.5 cmd/attr/debian/changelog - 1.4 cmd/attr/doc/CHANGES - 1.5 cmd/acl/VERSION - 1.9 cmd/acl/debian/changelog - 1.3 cmd/acl/libacl/acl.c - 1.12 cmd/acl/doc/CHANGES - 1.9 - workaround syscall number collision on recent ia64 kernels. From owner-linux-xfs@oss.sgi.com Sun Jul 1 23:25:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f626P4d18578 for linux-xfs-outgoing; Sun, 1 Jul 2001 23:25:04 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f626P2V18575 for ; Sun, 1 Jul 2001 23:25:03 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA09428; Mon, 2 Jul 2001 08:25:00 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA20784; Mon, 2 Jul 2001 08:25:00 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 4B45D57306; Mon, 2 Jul 2001 08:34:22 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 3ECD325835; Mon, 2 Jul 2001 08:42:28 +0200 (CEST) Message-ID: <3B4013D8.CCAB9312@ch.sauter-bc.com> Date: Mon, 02 Jul 2001 08:25:28 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: "Bernhard R. Erdmann" Cc: Linux XFS Mailing List Subject: Re: XFS vs. JFS References: <3B3EF5BD.7EE9AA5D@berdmann.de> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Bernhard R. Erdmann" schrieb: > > Hi, > > how do you think about IBM's JFS for Linux version 1.0 released last > friday? > http://oss.software.ibm.com/jfs/ > > Is it or can it be a competitor for XFS? > > The papers mention JFS only journaling metadata, not the data itself. > Does XFS also journal the data? At least JFS will give you another choice. That's a good thing. But for me it's not a choice because JFS lacks some features I like with XFS. To mention two of them: - RH-based Installer - Run's on Linux SoftRAID Simon From owner-linux-xfs@oss.sgi.com Mon Jul 2 00:30:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f627UO721237 for linux-xfs-outgoing; Mon, 2 Jul 2001 00:30:24 -0700 Received: from downtown.oche.de (root@downtown.oche.de [194.94.253.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f627UMV21228 for ; Mon, 2 Jul 2001 00:30:22 -0700 Received: (from uucp@localhost) by downtown.oche.de (8.9.3/8.9.3/Debian 8.9.3-21) with UUCP id JAA32253 for linux-xfs@oss.sgi.com; Mon, 2 Jul 2001 09:35:48 +0200 Received: from sirius (sirius.quickstep.oche.de [192.168.48.4]) by foehn.quickstep.oche.de (8.9.3/8.6.12) with ESMTP id JAA18729 for <@foehn.quickstep.oche.de:linux-xfs@oss.sgi.com>; Mon, 2 Jul 2001 09:28:22 +0200 (MET DST) Received: (from martin@localhost) by sirius (980427.SGI.8.8.8/980728.SGI.AUTOCF) id JAA06777; Mon, 2 Jul 2001 09:28:17 +0200 (CEST) Date: Mon, 2 Jul 2001 09:28:17 +0200 (CEST) Message-Id: <200107020728.JAA06777@sirius> From: Martin Spott To: linux-xfs@oss.sgi.com Subject: Re: XFS marries JFS X-Newsgroups: list.linux-xfs In-Reply-To: <9ho80f$1mm$1@foehn.quickstep.oche.de> User-Agent: tin/1.4.5-20010409 ("One More Nightmare") (UNIX) (IRIX64/6.5 (IP28)) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Sun, 1 Jul 2001, Bernhard R. Erdmann wrote: >> I just managed to apply the IBM patches for JFS to SGI's CVS checkout of >> linux-2.4.6-pre7-xfs. > If you can put up the patch somewhere I'll add a link to the FAQ for > people interested in getting both running for > testing/benchmarketing/crashing/whatever. I'm running such a setup for several months already. This only works, because Steve Best added a little tweak upon my request to get this going because XFS modifies some type declaration that JFS depends on. I'm maintaining patches with XFS plus JFS on my ftp server: ftp://ftp.uni-duisburg.de:/Linux/filesys/linux-2.4.5-fspatch.list ftp://ftp.uni-duisburg.de:/Linux/filesys/linux-2.4.5-fspatch.gz .... although I didn't have the time to upgrade to jfs-1.0 - will come soon, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Mon Jul 2 02:34:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f629YPg27326 for linux-xfs-outgoing; Mon, 2 Jul 2001 02:34:25 -0700 Received: from mailgate3.cinetic.de (mailgate3.cinetic.de [212.227.116.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f629YNV27320 for ; Mon, 2 Jul 2001 02:34:24 -0700 Received: from smtp.web.de (smtp01.web.de [194.45.170.210]) by mailgate3.cinetic.de (8.11.2/8.11.2/SuSE Linux 8.11.0-0.4) with SMTP id f629YMF01553 for ; Mon, 2 Jul 2001 11:34:22 +0200 Received: from deep-thought by smtp.web.de with smtp (freemail 4.2.2.2 #11) id m15H061-007nyCC; Mon, 2 Jul 2001 11:34 +0200 Date: Mon, 2 Jul 2001 11:34:51 +0200 From: Tilman Sauerbeck To: linux-xfs@oss.sgi.com Subject: Re: root partition with xfs fails to boot correctly Message-Id: <20010702113451.291edf86.tilman.sauerbeck@web.de> In-Reply-To: <01070123505701.01719@citadel.oehansen.pp.se> References: <01070123505701.01719@citadel.oehansen.pp.se> X-Mailer: Sylpheed version 0.4.64 (GTK+ 1.2.10; i386-debian-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > LABEL mounted partitions. The answer was to remove the LABEL= from > /etc/fstab and insert the partition names there instead. I know what went wrong when mounting the root partition: it said: "mount option error not found" or something similar. I /etc/fstab was: /dev/hda3 / xfs defaults, errors=remount-ro 01 So I simply deleted the "errors" option and know everything runs fine :) Thank you all for your hints, Tilman From owner-linux-xfs@oss.sgi.com Mon Jul 2 02:58:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f629wS728521 for linux-xfs-outgoing; Mon, 2 Jul 2001 02:58:28 -0700 Received: from mail.cc.kuleuven.ac.be (mail.cc.kuleuven.ac.be [134.58.10.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f629wQV28518 for ; Mon, 2 Jul 2001 02:58:27 -0700 Received: from pclab (pc-10-33-6-229.cc.kuleuven.ac.be [10.33.6.229]) by mail.cc.kuleuven.ac.be (8.9.3/8.9.0) with SMTP id LAA400154 for ; Mon, 2 Jul 2001 11:58:16 +0200 Message-Id: <3.0.6.32.20010702115815.007fa190@mail.cc.kuleuven.ac.be> X-Sender: pb429905@mail.cc.kuleuven.ac.be X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 02 Jul 2001 11:58:15 +0200 To: linux-xfs@oss.sgi.com From: werner maes Subject: XFS & ADSM Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, On a system with XFS installed (using the RH 7.1 iso) I'm not able to backup my files using ADSM (backup on tape). Without XFS there's no problem. I also tried disabling devfs but this did not work either. Has anybody else encountered this problem? Werner Maes LUDIT-KULeuven From owner-linux-xfs@oss.sgi.com Mon Jul 2 05:08:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62C86q02861 for linux-xfs-outgoing; Mon, 2 Jul 2001 05:08:06 -0700 Received: from studsv07.studserv.uni-stuttgart.de (studsv07.studserv.uni-stuttgart.de [129.69.21.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62C84V02858 for ; Mon, 2 Jul 2001 05:08:05 -0700 Received: from ysabell.wh.vaih [129.69.166.244] by studsv07.studserv.uni-stuttgart.de with ESMTP (SMTPD32-6.06) id A41718D40242; Mon, 02 Jul 2001 14:07:51 +0200 Received: from marcelo by ysabell.wh.vaih with local (Exim 3.22 #1 (Debian)) id 15H2Ua-0000Ly-00; Mon, 02 Jul 2001 14:07:52 +0200 Date: Mon, 2 Jul 2001 14:07:52 +0200 From: "Marcelo E. Magallon" To: werner maes Cc: linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM Message-ID: <20010702140752.A1180@ysabell.wh.vaih> Mail-Followup-To: werner maes , linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3.0.6.32.20010702115815.007fa190@mail.cc.kuleuven.ac.be> User-Agent: Mutt/1.3.18i X-Operating-System: Linux ysabell 2.4.4-xfs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >> werner maes writes: > On a system with XFS installed (using the RH 7.1 iso) I'm not able to > backup my files using ADSM (backup on tape). Without XFS there's no > problem. To put it midly, ADSM is a POS. For some reason it checks the filesystem type of the partition where the data it is trying to backup is located, finds it's "xfs", it has no idea what that is and bombs out. The local people in charge or the ADSM backups ended up exporting the filesystem to the same machine where it resides and mounting that over NFS (foo exports it's filesystems to foo). ADSM is happy with that. -- Marcelo From owner-linux-xfs@oss.sgi.com Mon Jul 2 05:45:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62CjXm05757 for linux-xfs-outgoing; Mon, 2 Jul 2001 05:45:33 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62CjTV05751 for ; Mon, 2 Jul 2001 05:45:29 -0700 Received: from gateway.mettler.ee.net (gateway.mettler.ee.net [206.222.20.2]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id FAB08071 for ; Mon, 2 Jul 2001 05:45:20 -0700 (PDT) mail_from (Craig.David@mt.com) Received: from s-mtao3.usa.mt.com by gateway.mettler.ee.net via smtpd (for mx.sgi.com [204.94.211.40]) with SMTP; 2 Jul 2001 12:45:20 UT Received: by s-mtao3.mtus.mtnet with Internet Mail Service (5.5.2653.19) id ; Mon, 2 Jul 2001 08:39:44 -0400 Message-ID: From: David Craig MTI-CF To: "'linux-xfs@oss.sgi.com'" Subject: Kickstart XFS Error - Error writing to Device Date: Mon, 2 Jul 2001 08:39:43 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C102F4.116F09D0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C102F4.116F09D0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C102F4.116F09D0" ------_=_NextPart_001_01C102F4.116F09D0 Content-Type: text/plain I have a problem with the kickstart install with the bootnet.img image from XFS version 1.0 ISO image. 1. I have created the boot disk from the ISO mage with the bootnet.img. 2. I have copied the ks.cfg that I use from a non XFS install onto the floppy. 3. I modified the part parameter to add -fs xfs. 4. I'm using FTP to get the images. 5. I have copied the base and redhat directories to the ftp site. 6. I have copied the original RPMS from the 7.1 disk1 and disk2 into the same RPMS directories (nothing overwritten) When I run the KS file I get the following errors. I get this message on the text screen. "Error loading ramdisk" "Unable to retrieve the first install image" Here is the snapshot of the screen F3 screen. * url address 172.18.33.53 * url prefix /redhat/7.1.xfs * transferring ftp://172.18.33.53//redhat/7.1xfs/RedHat/base/netstg1.img to a fd * created inode * error writing to device: No space left on Device * done loading 4719616 bytes. I have included the ks.cfg <> Is this a know problem or something that I'm doing wrong. Craig David ______________ Mettler-Toledo Inc. EDI Coordinator (North America) 1900 Polaris Parkway Columbus, Ohio USA Phone: +1 614 438 4668 Fax: +1 614 420 2512 Craig.David@mt.com ------_=_NextPart_001_01C102F4.116F09D0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable Kickstart XFS Error - Error writing to Device

I have a problem with = the kickstart install with the = bootnet.img image from XFS version 1.0 ISO image.

1.      I have created the boot disk from the ISO mage with the = bootnet.img.
2.      I have copied the ks.cfg that I use from a non XFS = install onto the floppy.
3.      I modified the part parameter to add -fs = xfs.
4.      I'm using FTP to get the images.
5.      I have copied the base and redhat directories to the ftp = site.
6.      I have copied the original RPMS from the 7.1 disk1 = and disk2 into the same RPMS = directories (nothing overwritten)

 

When I run the KS file I = get the following errors.

I get this message on the = text screen.

"Error loading ramdisk"

"Unable to retrieve = the first install image"

Here is the snapshot of = the screen F3 screen.

* url address 172.18.33.53

* url prefix = /redhat/7.1.xfs

* transferring ftp://172.18.33.53//redhat/7.1xfs/RedHat/base/netstg1.img= to a fd

* created = inode

* error writing to = device: No space left on Device

* done loading 4719616 = bytes.

I have included the = ks.cfg

= <<ks.cfg>>


Is this a know problem or = something that I'm doing wrong.

Craig David

______________

Mettler-Toledo Inc.

EDI = Coordinator (North America)

1900 = Polaris Parkway

Columbus, Ohio USA

Phone: = +1 614 438 4668

Fax:     +1 614 420 2512

Craig.David@mt.com


------_=_NextPart_001_01C102F4.116F09D0-- ------_=_NextPart_000_01C102F4.116F09D0 Content-Type: application/octet-stream; name="ks.cfg" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="ks.cfg" #Generated by Kickstart Configurator=0A= #=0A= # This disk installs redhat 7.1=0A= #=0A= # Created by Craig David - 29-June-2001=0A= #=0A= lang en_US=0A= keyboard us=0A= mouse generic3ps/2=0A= timezone --utc America/New_York=0A= rootpw password=0A= =0A= url --url ftp://172.18.33.53/redhat/7.1xfs=0A= network --bootproto dhcp --hostname us01sbxd01test=0A= #network --bootproto static --ip 172.18.33.87 --netmask 255.255.240.0 = --gateway 172.18.32.1 --nameserver 172.18.33.1 --hostname us01sbxd01=0A= #url --url ftp://edi01.mtus.mtnet/redhat/7.1xfs=0A= =0A= install=0A= auth --useshadow --enablemd5 --enablenis --nisdomain edi.nis = --nisserver edi01.mtus.mtnet=0A= =0A= firewall --disabled =0A= zerombr yes=0A= clearpart --linux=0A= part /boot --size 35=0A= part swap --size 128=0A= #part / --size 1000 --grow=0A= #part / --size 1000 --grow=0A= part /u00 --size 1000 --fs xfs --grow=0A= =0A= lilo --location partition=0A= %packages =0A= @Anonymous FTP Server=0A= @NFS Server=0A= @SMB (Samba) Server=0A= @Utilities=0A= @Web Server=0A= ntp=0A= am-utils=0A= yp-tools=0A= ypbind=0A= ypserv=0A= zlib=0A= zlib-devel=0A= =0A= %post=0A= mount /dev/fd0=0A= ftp -n < /mnt/floppy/ftp=0A= chmod 775 /conf=0A= ./conf=0A= =0A= ------_=_NextPart_000_01C102F4.116F09D0-- From owner-linux-xfs@oss.sgi.com Mon Jul 2 08:16:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62FGkX18052 for linux-xfs-outgoing; Mon, 2 Jul 2001 08:16:46 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62FGjV18049 for ; Mon, 2 Jul 2001 08:16:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA01718 for ; Mon, 2 Jul 2001 08:16:44 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2318728; Mon, 2 Jul 2001 10:15:29 -0500 (CDT) Received: from sgi.com (eagdhcp-187-26.americas.sgi.com [128.162.187.176]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA07826; Mon, 2 Jul 2001 10:15:28 -0500 (CDT) Message-ID: <3B408FC5.A4DC275F@sgi.com> Date: Mon, 02 Jul 2001 10:14:14 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-21mdk_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: David Craig MTI-CF CC: "'linux-xfs@oss.sgi.com'" Subject: Re: Kickstart XFS Error - Error writing to Device References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > David Craig MTI-CF wrote: > * transferring > ftp://172.18.33.53//redhat/7.1xfs/RedHat/base/netstg1.img to a fd > > * created inode > > * error writing to device: No space left on Device > > * done loading 4719616 bytes. > > I have included the ks.cfg > > <> > > Is this a know problem or something that I'm doing wrong. When it retrieves netsgt1.img, it has to put it _somewhere_ (I'm not sure offhand where it goes, i.e. on which partition). You have: part /boot --size 35 part swap --size 128 #part / --size 1000 --grow #part / --size 1000 --grow part /u00 --size 1000 --fs xfs --grow I'm not sure how the installer interprets this - you've only defined a /boot and /u00? How does "/" wind up getting sized then? It just sounds like you're running out of room somewhere. -Eric From owner-linux-xfs@oss.sgi.com Mon Jul 2 08:41:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62FfRE19266 for linux-xfs-outgoing; Mon, 2 Jul 2001 08:41:27 -0700 Received: from gateway.mettler.ee.net (gateway.mettler.ee.net [206.222.20.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62FfPV19263 for ; Mon, 2 Jul 2001 08:41:26 -0700 Received: from s-mtao3.usa.mt.com by gateway.mettler.ee.net via smtpd (for oss.sgi.com [216.32.174.27]) with SMTP; 2 Jul 2001 15:41:25 UT Received: by s-mtao3.mtus.mtnet with Internet Mail Service (5.5.2653.19) id ; Mon, 2 Jul 2001 11:41:24 -0400 Message-ID: From: David Craig MTI-CF To: "'Eric Sandeen'" Cc: "'linux-xfs@oss.sgi.com'" Subject: RE: Kickstart XFS Error - Error writing to Device Date: Mon, 2 Jul 2001 11:41:02 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm sorry that was a typo. Here is the crrect KS file. I have just tried this one and I get the same error as explained in the earlier email. ----------- #Generated by Kickstart Configurator # # This disk installs redhat 7.1 # # Created by Craig David - 29-June-2001 # lang en_US keyboard us mouse generic3ps/2 timezone --utc America/New_York rootpw password url --url ftp://172.18.33.53/redhat/7.1xfs network --bootproto dhcp --hostname us01sbxd01test install auth --useshadow --enablemd5 --enablenis --nisdomain edi.nis --nisserver edi01.mtus.mtnet firewall --disabled zerombr yes clearpart --linux part /boot --size 100 part swap --size 128 part / --size 1 --grow lilo --location partition %packages @Anonymous FTP Server @NFS Server @SMB (Samba) Server @Utilities @Web Server ntp am-utils yp-tools ypbind ypserv zlib zlib-devel %post mount /dev/fd0 ftp -n < /mnt/floppy/ftp chmod 775 /conf ./conf ----------- -----Original Message----- From: Eric Sandeen [mailto:sandeen@sgi.com] Sent: Monday, July 02, 2001 11:14 AM To: David Craig MTI-CF Cc: 'linux-xfs@oss.sgi.com' Subject: Re: Kickstart XFS Error - Error writing to Device > David Craig MTI-CF wrote: > * transferring > ftp://172.18.33.53//redhat/7.1xfs/RedHat/base/netstg1.img to a fd > > * created inode > > * error writing to device: No space left on Device > > * done loading 4719616 bytes. > > I have included the ks.cfg > > <> > > Is this a know problem or something that I'm doing wrong. When it retrieves netsgt1.img, it has to put it _somewhere_ (I'm not sure offhand where it goes, i.e. on which partition). You have: part /boot --size 35 part swap --size 128 #part / --size 1000 --grow #part / --size 1000 --grow part /u00 --size 1000 --fs xfs --grow I'm not sure how the installer interprets this - you've only defined a /boot and /u00? How does "/" wind up getting sized then? It just sounds like you're running out of room somewhere. -Eric From owner-linux-xfs@oss.sgi.com Mon Jul 2 09:04:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62G4Kg20163 for linux-xfs-outgoing; Mon, 2 Jul 2001 09:04:20 -0700 Received: from ns1.tricord.com (mx01.tricord.com [64.240.27.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62G4JV20158 for ; Mon, 2 Jul 2001 09:04:19 -0700 Received: FROM ns1.tricord.com BY ns1.tricord.com ; Mon Jul 02 11:05:38 2001 -0500 Received: by NS1 with Internet Mail Service (5.5.2650.21) id ; Mon, 2 Jul 2001 11:05:38 -0500 Message-ID: <6DEE94132593D41182D200508BDCA59050081C@mail.tricord.com> From: "Esh, Andrew" To: "'linux-xfs@oss.sgi.com'" Subject: ACL Support Date: Mon, 2 Jul 2001 11:04:18 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C10310.D5B5C450" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C10310.D5B5C450 Content-Type: text/plain; charset="iso-8859-1" I tried out Linux XFS with an eye toward using it for Access Control List (ACL) support under Samba. I had to give up because it doesn't appear that XFS has full Posix support for ACLs. When I tried to link the development version of Samba against the XFS include files and ACL library, there were a number of unresolved ACL-specific symbols. I switch to using a plain ext2fs kernel, with Posix ACL support patched in (see http://acl.bestbits.at), and Samba linked just fine. When Samba runs, the shares it provides cause NT to display the "Security" tab in the file/folder Properties, which is where ACLs are managed. Does this seem right? Is ACL support IRIX specific, or not-ready-for-prime-time on i386 Linux? I am asking just to see if it's worth my time to go back and try to find out what was going wrong with the Posix ACL support under XFS. --- Andrew C. Esh mail:Andrew.Esh@tricord.com Tricord Systems, Inc. 2905 Northwest Blvd., Suite 20 763-557-9005 (main) Plymouth, MN 55441-2644 USA 763-551-6418 (direct) http://www.tricord.com - Tricord Home Page ------_=_NextPart_001_01C10310.D5B5C450 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ACL Support

I tried out Linux XFS with an eye toward using it for = Access Control List (ACL) support under Samba. I had to give up because = it doesn't appear that XFS has full Posix support for ACLs. When I = tried to link the development version of Samba against the XFS include = files and ACL library, there were a number of unresolved ACL-specific = symbols. I switch to using a plain ext2fs kernel, with Posix ACL = support patched in (see http://acl.bestbits.at), and Samba linked just = fine. When Samba runs, the shares it provides cause NT to display the = "Security" tab in the file/folder Properties, which is where = ACLs are managed.

Does this seem right? Is ACL support IRIX specific, = or not-ready-for-prime-time on i386 Linux? I am asking just to see if = it's worth my time to go back and try to find out what was going wrong = with the Posix ACL support under XFS.

---
Andrew C. = Esh           &nb= sp;    mail:Andrew.Esh@tricord.com
Tricord Systems, Inc.
2905 Northwest Blvd., Suite = 20        763-557-9005 (main)
Plymouth, MN 55441-2644 = USA      763-551-6418 (direct)
http://www.tricord.com - Tricord Home Page


------_=_NextPart_001_01C10310.D5B5C450-- From owner-linux-xfs@oss.sgi.com Mon Jul 2 09:04:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62G4qW20242 for linux-xfs-outgoing; Mon, 2 Jul 2001 09:04:52 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62G4pV20233 for ; Mon, 2 Jul 2001 09:04:51 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA07853 for ; Mon, 2 Jul 2001 09:02:07 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2322309 for ; Mon, 2 Jul 2001 11:03:35 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA47638 for ; Mon, 2 Jul 2001 11:03:34 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f62G4br32294; Mon, 2 Jul 2001 11:04:37 -0500 Message-Id: <200107021604.f62G4br32294@jen.americas.sgi.com> Date: Mon, 2 Jul 2001 11:04:37 -0500 Subject: TAKE - merge up to 2.4.6-pre8 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Some fairly significant changes to how buffer flushing is done, and to the modes of operation in the memory allocator. This last one should fix a number of highmem related deadlocks. I have pounded on this, and XFS seems as stable as before, if not more so on highmem boxes. Date: Mon Jul 2 08:59:04 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-base The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98047a linux/net/x25/x25_subr.c - 1.5 linux/net/x25/x25_link.c - 1.9 linux/net/unix/garbage.c - 1.9 linux/net/unix/af_unix.c - 1.29 linux/net/sched/sch_red.c - 1.7 linux/net/rose/rose_subr.c - 1.4 linux/net/rose/rose_route.c - 1.7 linux/net/packet/af_packet.c - 1.23 linux/net/netlink/af_netlink.c - 1.15 linux/net/lapb/lapb_subr.c - 1.4 linux/net/ipx/af_spx.c - 1.13 linux/net/ipv4/tcp_output.c - 1.18 linux/net/ipv4/ipmr.c - 1.16 linux/net/core/sock.c - 1.20 linux/net/ax25/ax25_subr.c - 1.6 linux/net/ax25/ax25_in.c - 1.9 linux/net/appletalk/aarp.c - 1.11 linux/mm/vmscan.c - 1.61 linux/mm/page_alloc.c - 1.45 linux/include/linux/slab.h - 1.15 linux/include/linux/mm.h - 1.57 linux/include/linux/fs.h - 1.100 linux/fs/proc/generic.c - 1.21 linux/fs/proc/base.c - 1.26 linux/fs/buffer.c - 1.69 linux/fs/affs/file.c - 1.16 linux/drivers/sbus/char/zs.c - 1.17 linux/drivers/sbus/char/su.c - 1.17 linux/drivers/sbus/char/sab82532.c - 1.20 linux/drivers/net/sunhme.c - 1.27 linux/drivers/net/defxx.c - 1.16 linux/drivers/block/nbd.c - 1.20 linux/drivers/block/loop.c - 1.33 linux/arch/sparc64/defconfig - 1.39 linux/Makefile - 1.94 linux/Documentation/networking/alias.txt - 1.3 linux/arch/sparc64/kernel/pci_common.c - 1.13 linux/mm/highmem.c - 1.21 linux/net/ipv4/inetpeer.c - 1.5 linux/net/sched/sch_gred.c - 1.6 linux/lib/brlock.c - 1.4 linux/net/econet/af_econet.c - 1.8 linux/fs/pagebuf/page_buf.c - 1.88 linux/fs/pagebuf/page_buf_io.c - 1.87 linux/drivers/md/raid1.c - 1.10 linux/arch/i386/kernel/bluesmoke.c - 1.9 linux/fs/reiserfs/super.c - 1.5 linux/fs/reiserfs/namei.c - 1.4 linux/fs/reiserfs/journal.c - 1.4 linux/fs/reiserfs/fix_node.c - 1.5 linux/fs/reiserfs/dir.c - 1.3 linux/fs/xfs_support/kmem.c - 1.8 From owner-linux-xfs@oss.sgi.com Mon Jul 2 09:08:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62G8jW20537 for linux-xfs-outgoing; Mon, 2 Jul 2001 09:08:45 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62G8iV20534 for ; Mon, 2 Jul 2001 09:08:44 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA01812 for ; Mon, 2 Jul 2001 09:08:37 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2321820; Mon, 2 Jul 2001 11:07:26 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA86345; Mon, 2 Jul 2001 11:07:26 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f62G8Td32361; Mon, 2 Jul 2001 11:08:29 -0500 Message-Id: <200107021608.f62G8Td32361@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Esh, Andrew" cc: "'linux-xfs@oss.sgi.com'" Subject: Re: ACL Support In-Reply-To: Message from "Esh, Andrew" of "Mon, 02 Jul 2001 11:04:18 CDT." <6DEE94132593D41182D200508BDCA59050081C@mail.tricord.com> Date: Mon, 02 Jul 2001 11:08:29 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk There are people using XFS ACLs with Samba quite successfully, sounds like a configuration problem, or just the wrong version of the code to me. I will have to leave it up to someone using ACLs to describe what they are using and how they installed it. Steve > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > ------_=_NextPart_001_01C10310.D5B5C450 > Content-Type: text/plain; > charset="iso-8859-1" > > I tried out Linux XFS with an eye toward using it for Access Control List > (ACL) support under Samba. I had to give up because it doesn't appear that > XFS has full Posix support for ACLs. When I tried to link the development > version of Samba against the XFS include files and ACL library, there were a > number of unresolved ACL-specific symbols. I switch to using a plain ext2fs > kernel, with Posix ACL support patched in (see http://acl.bestbits.at), and > Samba linked just fine. When Samba runs, the shares it provides cause NT to > display the "Security" tab in the file/folder Properties, which is where > ACLs are managed. > > Does this seem right? Is ACL support IRIX specific, or > not-ready-for-prime-time on i386 Linux? I am asking just to see if it's > worth my time to go back and try to find out what was going wrong with the > Posix ACL support under XFS. > > --- > Andrew C. Esh mail:Andrew.Esh@tricord.com > Tricord Systems, Inc. > 2905 Northwest Blvd., Suite 20 763-557-9005 (main) > Plymouth, MN 55441-2644 USA 763-551-6418 (direct) > http://www.tricord.com - Tricord Home Page > > > > ------_=_NextPart_001_01C10310.D5B5C450 > Content-Type: text/html; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > > > > charset=3Diso-8859-1"> > 5.5.2650.12"> > ACL Support > > > >

I tried out Linux XFS with an eye toward using it for = > Access Control List (ACL) support under Samba. I had to give up because = > it doesn't appear that XFS has full Posix support for ACLs. When I = > tried to link the development version of Samba against the XFS include = > files and ACL library, there were a number of unresolved ACL-specific = > symbols. I switch to using a plain ext2fs kernel, with Posix ACL = > support patched in (see TARGET=3D"_blank">http://acl.bestbits.at), and Samba linked just = > fine. When Samba runs, the shares it provides cause NT to display the = > "Security" tab in the file/folder Properties, which is where = > ACLs are managed.

> >

Does this seem right? Is ACL support IRIX specific, = > or not-ready-for-prime-time on i386 Linux? I am asking just to see if = > it's worth my time to go back and try to find out what was going wrong = > with the Posix ACL support under XFS.

> >

--- >
Andrew C. = > Esh           &nb= > sp;    mail:Andrew.Esh@tricord.com >
Tricord Systems, Inc. >
2905 Northwest Blvd., Suite = > 20        763-557-9005 (main) >
Plymouth, MN 55441-2644 = > USA      763-551-6418 (direct) >
TARGET=3D"_blank">http://www.tricord.com - Tricord Home Page >

>
> > > > ------_=_NextPart_001_01C10310.D5B5C450-- From owner-linux-xfs@oss.sgi.com Mon Jul 2 09:11:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62GBMM20694 for linux-xfs-outgoing; Mon, 2 Jul 2001 09:11:22 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62GBLV20691 for ; Mon, 2 Jul 2001 09:11:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA04224 for ; Mon, 2 Jul 2001 09:08:37 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2315756 for ; Mon, 2 Jul 2001 11:10:05 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA68843 for ; Mon, 2 Jul 2001 11:10:04 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f62GB7n32581; Mon, 2 Jul 2001 11:11:07 -0500 Message-Id: <200107021611.f62GB7n32581@jen.americas.sgi.com> Date: Mon, 2 Jul 2001 11:11:07 -0500 Subject: TAKE - fix makefile checkin Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Accidentally turned on kgcc by default in the makefile. Date: Mon Jul 2 09:09:36 PDT 2001 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:98049a linux/Makefile - 1.95 - Woops, checked in with kgcc turned on by default, go back to gcc From owner-linux-xfs@oss.sgi.com Mon Jul 2 09:20:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62GKGD20907 for linux-xfs-outgoing; Mon, 2 Jul 2001 09:20:16 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62GKCV20903 for ; Mon, 2 Jul 2001 09:20:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA792888 for ; Mon, 2 Jul 2001 18:20:10 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2320067; Mon, 2 Jul 2001 11:18:42 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA08780; Mon, 2 Jul 2001 11:18:30 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f62GJXa32651; Mon, 2 Jul 2001 11:19:33 -0500 Message-Id: <200107021619.f62GJXa32651@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Krzysztof Rusocki cc: linux-xfs@oss.sgi.com Subject: Re: /proc/sys/vm/pagbuf entries In-Reply-To: Message from Krzysztof Rusocki of "Sun, 01 Jul 2001 16:13:26 +0200." <20010701161326.A27056@main.braxis.co.uk> Date: Mon, 02 Jul 2001 11:19:33 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi, > > Can I ask anybody for short description of > /proc/sys/vm/paegubuf/* entries ? > > TIA. > > Cheers, > Krzysztof cluster_limit - no longer used, will be going away debug - hmm, maybe should be conditional, turns on some debug tracing if the kernel has the correct code built in, which it usually does not. flush_age - Age in milliseconds that a metadata buffer has to have to be flushed. flush_int - how often we look for metadata to flush - in milliseconds max_dio_pages - the maximum number of pages in a direct I/O request which will be locked down at once. If a user request is larger than this then it will be split up into chunks. So only three of them really mean anything now. Steve From owner-linux-xfs@oss.sgi.com Mon Jul 2 09:38:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62GcpT21258 for linux-xfs-outgoing; Mon, 2 Jul 2001 09:38:51 -0700 Received: from mailout05.sul.t-online.de (mailout05.sul.t-online.com [194.25.134.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62GcoV21255 for ; Mon, 2 Jul 2001 09:38:50 -0700 Received: from fwd05.sul.t-online.de by mailout05.sul.t-online.de with smtp id 15H6ic-0007DC-0D; Mon, 02 Jul 2001 18:38:38 +0200 Received: from tower (340024412816-0001@[217.81.130.59]) by fwd05.sul.t-online.com with smtp id 15H6ia-0ljMLAC; Mon, 2 Jul 2001 18:38:36 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: "Marcelo E. Magallon" , werner maes Subject: Re: XFS & ADSM Date: Mon, 2 Jul 2001 18:38:42 +0200 X-Mailer: KMail [version 1.2] Cc: linux-xfs@oss.sgi.com References: <20010702140752.A1180@ysabell.wh.vaih> In-Reply-To: <20010702140752.A1180@ysabell.wh.vaih> MIME-Version: 1.0 Message-Id: <01070218384200.00622@tower> Content-Transfer-Encoding: 8bit X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Montag, 2. Juli 2001 14:07 schrieb Marcelo E. Magallon: > >> werner maes writes: > >> > > On a system with XFS installed (using the RH 7.1 iso) I'm not able to > > backup my files using ADSM (backup on tape). Without XFS there's no > > problem. > > To put it midly, ADSM is a POS. For some reason it checks the > filesystem type of the partition where the data it is trying to backup > is located, finds it's "xfs", it has no idea what that is and bombs > out. > > The local people in charge or the ADSM backups ended up exporting the > filesystem to the same machine where it resides and mounting that over > NFS (foo exports it's filesystems to foo). ADSM is happy with that. It's not that bad. If you use a more recent backup client, it should work. The most recent version 4.2.0 of TSM even supports XFS . ...Juergen From owner-linux-xfs@oss.sgi.com Mon Jul 2 10:21:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62HLXC22153 for linux-xfs-outgoing; Mon, 2 Jul 2001 10:21:33 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62HLVV22150 for ; Mon, 2 Jul 2001 10:21:31 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 381EB1E4D3; Mon, 2 Jul 2001 19:21:25 +0200 (MEST) Date: Mon, 2 Jul 2001 19:21:06 +0200 From: Andi Kleen To: Steve Lord Cc: Krzysztof Rusocki , linux-xfs@oss.sgi.com Subject: Re: /proc/sys/vm/pagbuf entries Message-ID: <20010702192106.A6555@gruyere.muc.suse.de> References: <200107021619.f62GJXa32651@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107021619.f62GJXa32651@jen.americas.sgi.com>; from lord@sgi.com on Mon, Jul 02, 2001 at 11:19:33AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I would suggest dropping that small sysctl description into a file somewhere in Documentation/ -Andi From owner-linux-xfs@oss.sgi.com Mon Jul 2 10:23:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62HNUk22273 for linux-xfs-outgoing; Mon, 2 Jul 2001 10:23:30 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62HNTV22270 for ; Mon, 2 Jul 2001 10:23:29 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 0D4B41E4DB; Mon, 2 Jul 2001 19:23:24 +0200 (MEST) Date: Mon, 2 Jul 2001 19:23:17 +0200 From: Andi Kleen To: "Marcelo E. Magallon" Cc: werner maes , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM Message-ID: <20010702192317.B6555@gruyere.muc.suse.de> References: <3.0.6.32.20010702115815.007fa190@mail.cc.kuleuven.ac.be> <20010702140752.A1180@ysabell.wh.vaih> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010702140752.A1180@ysabell.wh.vaih>; from marcelo.magallon@bigfoot.com on Mon, Jul 02, 2001 at 02:07:52PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 02, 2001 at 02:07:52PM +0200, Marcelo E. Magallon wrote: > >> werner maes writes: > > > On a system with XFS installed (using the RH 7.1 iso) I'm not able to > > backup my files using ADSM (backup on tape). Without XFS there's no > > problem. > > To put it midly, ADSM is a POS. For some reason it checks the > filesystem type of the partition where the data it is trying to backup > is located, finds it's "xfs", it has no idea what that is and bombs > out. It's unfortunately not even an ADSM only problem. e.g. Arkeia has the same one and even VMWare checks file system types for some unknown reason. -Andi From owner-linux-xfs@oss.sgi.com Mon Jul 2 10:26:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62HQ6C22401 for linux-xfs-outgoing; Mon, 2 Jul 2001 10:26:06 -0700 Received: from mail.cc.kuleuven.ac.be (mail.cc.kuleuven.ac.be [134.58.10.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62HQ5V22398 for ; Mon, 2 Jul 2001 10:26:05 -0700 Received: from cc.kuleuven.ac.be (kn-10-4-3-251.iverlek.kotnet.kuleuven.ac.be [10.4.3.251]) by mail.cc.kuleuven.ac.be (8.9.3/8.9.0) with ESMTP id TAA1514678; Mon, 2 Jul 2001 19:26:02 +0200 Message-ID: <3B40AEA5.FD0A3272@cc.kuleuven.ac.be> Date: Mon, 02 Jul 2001 19:25:58 +0200 From: Werner Maes X-Mailer: Mozilla 4.76 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Juergen Hasch CC: "Marcelo E. Magallon" , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM References: <20010702140752.A1180@ysabell.wh.vaih> <01070218384200.00622@tower> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > It's not that bad. If you use a more recent backup client, it should work. > The most recent version 4.2.0 of TSM even supports XFS . > > ...Juergen Sounds great, but if I check the website of Tivoli, the most recent version seems to be 4.1.2 (http://www.tivoli.com/support/storage_mgr/clients.html#clients). So where did you get version 4.2.0? Werner From owner-linux-xfs@oss.sgi.com Mon Jul 2 10:31:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62HVPT22632 for linux-xfs-outgoing; Mon, 2 Jul 2001 10:31:25 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62HVNV22629 for ; Mon, 2 Jul 2001 10:31:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA805966 for ; Mon, 2 Jul 2001 19:31:20 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2319009 for ; Mon, 2 Jul 2001 12:30:04 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA44265 for ; Mon, 2 Jul 2001 12:30:03 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f62HV6406325; Mon, 2 Jul 2001 12:31:06 -0500 Message-Id: <200107021731.f62HV6406325@jen.americas.sgi.com> Date: Mon, 2 Jul 2001 12:31:06 -0500 Subject: TAKE - remove unused sysctl for pagebuf Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Mon Jul 2 10:29:29 PDT 2001 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:98052a linux/include/linux/page_buf.h - 1.95 linux/fs/pagebuf/page_buf.c - 1.89 - Cleanup /proc/sys/vm/pagebuf entries From owner-linux-xfs@oss.sgi.com Mon Jul 2 10:44:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62Hi7922918 for linux-xfs-outgoing; Mon, 2 Jul 2001 10:44:07 -0700 Received: from mailout03.sul.t-online.de (mailout03.sul.t-online.com [194.25.134.81]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62Hi5V22915 for ; Mon, 2 Jul 2001 10:44:06 -0700 Received: from fwd07.sul.t-online.de by mailout03.sul.t-online.de with smtp id 15H7jt-0003r9-0A; Mon, 02 Jul 2001 19:44:01 +0200 Received: from tower (340024412816-0001@[217.81.130.59]) by fwd07.sul.t-online.com with smtp id 15H7jo-24oaSuC; Mon, 2 Jul 2001 19:43:56 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Werner Maes , Juergen Hasch Subject: Re: XFS & ADSM Date: Mon, 2 Jul 2001 19:44:01 +0200 X-Mailer: KMail [version 1.2] Cc: "Marcelo E. Magallon" , linux-xfs@oss.sgi.com References: <20010702140752.A1180@ysabell.wh.vaih> <01070218384200.00622@tower> <3B40AEA5.FD0A3272@cc.kuleuven.ac.be> In-Reply-To: <3B40AEA5.FD0A3272@cc.kuleuven.ac.be> MIME-Version: 1.0 Message-Id: <01070219440102.00622@tower> Content-Transfer-Encoding: 8bit X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Montag, 2. Juli 2001 19:25 schrieb Werner Maes: > > It's not that bad. If you use a more recent backup client, it should > > work. The most recent version 4.2.0 of TSM even supports XFS . > > > > ...Juergen > > Sounds great, but if I check the website of Tivoli, the most recent version > seems > to be 4.1.2 > (http://www.tivoli.com/support/storage_mgr/clients.html#clients). So where > did you get version 4.2.0? It was released on July 01 :-) Look at: ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/client/v4r2/Linux86/v420 The guy who told me this confused Reiserfs with XFS, therefore my misleading post at first. ...Juergen From owner-linux-xfs@oss.sgi.com Mon Jul 2 11:17:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62IHxd23377 for linux-xfs-outgoing; Mon, 2 Jul 2001 11:17:59 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62IHvV23374 for ; Mon, 2 Jul 2001 11:17:57 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id UAA808538 for ; Mon, 2 Jul 2001 20:17:55 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2305275 for ; Mon, 2 Jul 2001 13:16:39 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA02671 for ; Mon, 2 Jul 2001 13:16:38 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f62IHeh07616; Mon, 2 Jul 2001 13:17:40 -0500 Message-Id: <200107021817.f62IHeh07616@jen.americas.sgi.com> Date: Mon, 2 Jul 2001 13:17:40 -0500 Subject: TAKE - more xfs memory hardening Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Yet another change to make xfs cope better in low memory situations. This adds more cases where the allocator flags will allow for the flushing of delalloc data to disk. Date: Mon Jul 2 11:15:34 PDT 2001 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:98056a linux/fs/xfs/xfs_da_btree.c - 1.119 - More memory hardening for XFS - add more cases which can use different memory allocation flags based on being called from within a transaction or not. From owner-linux-xfs@oss.sgi.com Mon Jul 2 11:46:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62Ikka23988 for linux-xfs-outgoing; Mon, 2 Jul 2001 11:46:46 -0700 Received: from musique.teaser.fr (musique.teaser.net [213.91.2.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62IkiV23985 for ; Mon, 2 Jul 2001 11:46:44 -0700 Received: from lucas.loria (d35-181.ppp.teaser.fr [213.91.35.181]) by musique.teaser.fr (Postfix) with ESMTP id 96FF272525; Mon, 2 Jul 2001 20:46:21 +0200 (CEST) Received: by lucas.loria (Postfix, from userid 500) id 6A549A6D2; Mon, 2 Jul 2001 20:48:15 +0200 (CEST) Date: Mon, 2 Jul 2001 20:48:14 +0200 From: Vincent Bernat To: Keith Matthews Cc: Linux XFS Mailing List Subject: Re: XFS vs. JFS Message-ID: <20010702204814.S26900@lucas.loria> References: <4.3.2.7.2.20010701135304.03a05bb0@pop.xs4all.nl>, <200107011212.f61CCgM15038@jen.americas.sgi.com> <20010701183306.E9B64125E6@rebutia.sweeney.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010701183306.E9B64125E6@rebutia.sweeney.demon.co.uk>; from keith_m@sweeney.demon.co.uk on Sun, Jul 01, 2001 at 07:33:06PM +0100 X-PGP-KeyID: 0xF22A794E X-PGP-Fingerprint: 5854 AF2B 65B2 0E96 2161 E32B 285B D7A1 F22A 794E Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Le Sun Jul 01, 2001 at 19:33 +0100, Keith Matthews disait : > The IBM guy was not aware of the OS/2 origin of Linux JFS, > but I had heard of it from other sources (I had also heard > that someone has back-ported the Linux version to OS/2 and > come up with a better product than the original OS/2 one !!). The major interest of the backport to OS/2 is that JFS is not freely available for OS/2. It is in Aurora (Warp Server 5) and incoming eComStation but not for Warp 4. It is one of the curious strategy that IBM uses to signify that OS/2 is almost dead. From owner-linux-xfs@oss.sgi.com Mon Jul 2 11:51:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62Ipko24309 for linux-xfs-outgoing; Mon, 2 Jul 2001 11:51:46 -0700 Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62IpiV24306 for ; Mon, 2 Jul 2001 11:51:44 -0700 Received: from fwd03.sul.t-online.de by mailout06.sul.t-online.de with smtp id 15H6rz-0004jO-04; Mon, 02 Jul 2001 18:48:19 +0200 Received: from tower (340024412816-0001@[217.81.130.59]) by fwd03.sul.t-online.com with smtp id 15H6rw-1iyZe4C; Mon, 2 Jul 2001 18:48:16 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Hasch@t-online.de (Juergen Hasch), "Marcelo E. Magallon" , werner maes Subject: Re: XFS & ADSM Date: Mon, 2 Jul 2001 18:47:57 +0200 X-Mailer: KMail [version 1.2] Cc: linux-xfs@oss.sgi.com References: <20010702140752.A1180@ysabell.wh.vaih> <01070218384200.00622@tower> In-Reply-To: <01070218384200.00622@tower> MIME-Version: 1.0 Message-Id: <01070218475701.00622@tower> Content-Transfer-Encoding: 8bit X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Montag, 2. Juli 2001 18:38 schrieb Juergen Hasch: > > > The most recent version 4.2.0 of TSM even supports XFS . I guess I was a little to optimistic. I shouldn't write things I don't understand much of. ...Juergen From owner-linux-xfs@oss.sgi.com Mon Jul 2 13:03:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62K3eA25618 for linux-xfs-outgoing; Mon, 2 Jul 2001 13:03:40 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62K3dV25615 for ; Mon, 2 Jul 2001 13:03:39 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 94CF11E50A; Mon, 2 Jul 2001 22:03:33 +0200 (MEST) Date: Mon, 2 Jul 2001 22:03:32 +0200 From: Andi Kleen To: Juergen Hasch Cc: "Marcelo E. Magallon" , werner maes , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM Message-ID: <20010702220332.A8648@gruyere.muc.suse.de> References: <20010702140752.A1180@ysabell.wh.vaih> <01070218384200.00622@tower> <01070218475701.00622@tower> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01070218475701.00622@tower>; from Hasch@t-online.de on Mon, Jul 02, 2001 at 06:47:57PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 02, 2001 at 06:47:57PM +0200, Juergen Hasch wrote: > Am Montag, 2. Juli 2001 18:38 schrieb Juergen Hasch: > > > > > > The most recent version 4.2.0 of TSM even supports XFS . > I guess I was a little to optimistic. I shouldn't write > things I don't understand much of. I don't know much about TSM/ADSM, but if it's only checking the file system name in /etc/mtab you can probably fix it with a binary editor, replacing the name of an unused file system with the same length like ufs with xfs. Just be careful that you find the right occurrence of the ufs string; it is probably near other file system names. I've fixed at least one program this way. -Andi From owner-linux-xfs@oss.sgi.com Mon Jul 2 13:48:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62Kmr426331 for linux-xfs-outgoing; Mon, 2 Jul 2001 13:48:53 -0700 Received: from mailout01.sul.t-online.de (mailout01.sul.t-online.com [194.25.134.80]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62KmpV26328 for ; Mon, 2 Jul 2001 13:48:51 -0700 Received: from fwd01.sul.t-online.de by mailout01.sul.t-online.de with smtp id 15HAci-0000Vf-06; Mon, 02 Jul 2001 22:48:48 +0200 Received: from tower (340024412816-0001@[217.81.140.182]) by fwd01.sul.t-online.com with smtp id 15HAcV-0RmlP6C; Mon, 2 Jul 2001 22:48:35 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Andi Kleen , Juergen Hasch Subject: Re: XFS & ADSM Date: Mon, 2 Jul 2001 22:48:38 +0200 X-Mailer: KMail [version 1.2] Cc: "Marcelo E. Magallon" , werner maes , linux-xfs@oss.sgi.com References: <20010702140752.A1180@ysabell.wh.vaih> <01070218475701.00622@tower> <20010702220332.A8648@gruyere.muc.suse.de> In-Reply-To: <20010702220332.A8648@gruyere.muc.suse.de> MIME-Version: 1.0 Message-Id: <01070222483800.03380@tower> Content-Transfer-Encoding: 8bit X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Montag, 2. Juli 2001 22:03 schrieb Andi Kleen: > I don't know much about TSM/ADSM, but if it's only checking the file system > name in /etc/mtab you can probably fix it with a binary editor, replacing > the name of an unused file system with the same length like ufs with xfs. > Just be careful that you find the right occurrence of the ufs string; it is > probably near other file system names. > I've fixed at least one program this way. > > -Andi I looked at the release notes of the TSM client 4.2.0 and it states: o The functionality of the Tivoli Storage Manager Linux client is designed and tested to work on file systems of the common types EXT2, ReiserFS, VFAT, NFS (see under known problems and limitations for supported environment), and ISO9660 (CD-ROM). Backup and archive for other file system types is not excluded. They will be tolerated and performed in compatibility mode. This means that features of other file systems types may not be supported by the Linux client. These file system type information of such file systems will be forced to unknown. So I guess XFS will work with this version, but without support for ACL and extended attributes. I am using Legato Networker for my Linux machines with several XFS filesystems myself. It works without problems. I am not using ACLs or extended attributes right now. ...Juergen From owner-linux-xfs@oss.sgi.com Mon Jul 2 13:53:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62Kr7826454 for linux-xfs-outgoing; Mon, 2 Jul 2001 13:53:07 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62Kr6V26451 for ; Mon, 2 Jul 2001 13:53:06 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA01482 for ; Mon, 2 Jul 2001 13:50:22 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2297610; Mon, 2 Jul 2001 15:51:48 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA78058; Mon, 2 Jul 2001 15:51:48 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f62KqnZ09878; Mon, 2 Jul 2001 15:52:49 -0500 Message-Id: <200107022052.f62KqnZ09878@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Hasch@t-online.de (Juergen Hasch) cc: Andi Kleen , "Marcelo E. Magallon" , werner maes , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM In-Reply-To: Message from Hasch@t-online.de (Juergen Hasch) of "Mon, 02 Jul 2001 22:48:38 +0200." <01070222483800.03380@tower> Date: Mon, 02 Jul 2001 15:52:49 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Am Montag, 2. Juli 2001 22:03 schrieb Andi Kleen: > > I don't know much about TSM/ADSM, but if it's only checking the file system > > name in /etc/mtab you can probably fix it with a binary editor, replacing > > the name of an unused file system with the same length like ufs with xfs. > > Just be careful that you find the right occurrence of the ufs string; it is > > probably near other file system names. > > I've fixed at least one program this way. > > > > -Andi > > I looked at the release notes of the TSM client 4.2.0 and it states: > > o The functionality of the Tivoli Storage Manager Linux client is designed > and tested to work on file systems of the common types EXT2, ReiserFS, > VFAT, NFS (see under known problems and limitations for supported > environment), and ISO9660 (CD-ROM). Backup and archive for other file > system types is not excluded. They will be tolerated and performed in > compatibility mode. > This means that features of other file systems types may not be supported > by the Linux client. These file system type information of such file > systems will be forced to unknown. > > So I guess XFS will work with this version, but without support for ACL and > extended attributes. > > I am using Legato Networker for my Linux machines with several XFS > filesystems myself. It works without problems. I am not using ACLs or > extended attributes right now. > > ...Juergen I took a quick look around the download site this morning, and noticed that they have an Irix version. So it would not be a huge amount of effort to use the modified api we have in Linux to get to thinks like extended attributes as well. Note that this presumes the Irix version supports them. Steve From owner-linux-xfs@oss.sgi.com Mon Jul 2 13:53:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62KrOv26546 for linux-xfs-outgoing; Mon, 2 Jul 2001 13:53:24 -0700 Received: from mailout02.sul.t-online.de (mailout02.sul.t-online.com [194.25.134.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62KrNV26543 for ; Mon, 2 Jul 2001 13:53:23 -0700 Received: from fwd03.sul.t-online.de by mailout02.sul.t-online.de with smtp id 15HAh4-0004Gb-0F; Mon, 02 Jul 2001 22:53:18 +0200 Received: from tower (340024412816-0001@[217.81.140.182]) by fwd03.sul.t-online.com with smtp id 15HAgx-1MwjiqC; Mon, 2 Jul 2001 22:53:11 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: "Esh, Andrew" , "'linux-xfs@oss.sgi.com'" Subject: Re: ACL Support Date: Mon, 2 Jul 2001 22:53:16 +0200 X-Mailer: KMail [version 1.2] References: <6DEE94132593D41182D200508BDCA59050081C@mail.tricord.com> In-Reply-To: <6DEE94132593D41182D200508BDCA59050081C@mail.tricord.com> MIME-Version: 1.0 Message-Id: <01070222531601.03380@tower> Content-Transfer-Encoding: 8bit X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Montag, 2. Juli 2001 18:04 schrieb Esh, Andrew: > I tried out Linux XFS with an eye toward using it for Access Control List > (ACL) support under Samba. I had to give up because it doesn't appear that > XFS has full Posix support for ACLs. When I tried to link the development > version of Samba against the XFS include files and ACL library, there were > a number of unresolved ACL-specific symbols. I switch to using a plain > ext2fs kernel, with Posix ACL support patched in (see > http://acl.bestbits.at), and Samba linked just fine. When Samba runs, the > shares it provides cause NT to display the "Security" tab in the > file/folder Properties, which is where ACLs are managed. > > Does this seem right? Is ACL support IRIX specific, or > not-ready-for-prime-time on i386 Linux? I am asking just to see if it's > worth my time to go back and try to find out what was going wrong with the > Posix ACL support under XFS. I have XFS with Samba 2.2-CVS and ACL-support working. Make sure you have a recent version of the XFS support libraries (libacl). There have been a lot of changes in Samba after the 2.2.0 release, so you might want to wait for 2.2.1 or get a current CVS version. ...Juergen From owner-linux-xfs@oss.sgi.com Mon Jul 2 14:21:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62LLnJ27077 for linux-xfs-outgoing; Mon, 2 Jul 2001 14:21:49 -0700 Received: from ente.berdmann.de (pD9011840.dip.t-dialin.net [217.1.24.64]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62LLkV27074 for ; Mon, 2 Jul 2001 14:21:47 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15HB8V-0003Ug-00; Mon, 02 Jul 2001 23:21:39 +0200 Message-ID: <3B40E5E3.CE1F0D6F@berdmann.de> Date: Mon, 02 Jul 2001 23:21:39 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Andi Kleen CC: "Marcelo E. Magallon" , werner maes , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM References: <3.0.6.32.20010702115815.007fa190@mail.cc.kuleuven.ac.be> <20010702140752.A1180@ysabell.wh.vaih> <20010702192317.B6555@gruyere.muc.suse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > It's unfortunately not even an ADSM only problem. e.g. Arkeia has the > same one and even VMWare checks file system types for some unknown > reason. VMWare checks for locking capabilities - it doesn't know anything about XFS as a filesystem but it prints a helpful error message to add something to your blah.cfg and that helps. # Locking on XFS host.FSSupportLocking1 = 0x58465342 From owner-linux-xfs@oss.sgi.com Mon Jul 2 14:24:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62LOF327198 for linux-xfs-outgoing; Mon, 2 Jul 2001 14:24:15 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62LOEV27195 for ; Mon, 2 Jul 2001 14:24:14 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id D3C081E53A; Mon, 2 Jul 2001 23:24:02 +0200 (MEST) Date: Mon, 2 Jul 2001 23:23:58 +0200 From: Andi Kleen To: "Bernhard R. Erdmann" Cc: Andi Kleen , "Marcelo E. Magallon" , werner maes , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM Message-ID: <20010702232358.A9587@gruyere.muc.suse.de> References: <3.0.6.32.20010702115815.007fa190@mail.cc.kuleuven.ac.be> <20010702140752.A1180@ysabell.wh.vaih> <20010702192317.B6555@gruyere.muc.suse.de> <3B40E5E3.CE1F0D6F@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B40E5E3.CE1F0D6F@berdmann.de>; from be@berdmann.de on Mon, Jul 02, 2001 at 11:21:39PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 02, 2001 at 11:21:39PM +0200, Bernhard R. Erdmann wrote: > > It's unfortunately not even an ADSM only problem. e.g. Arkeia has the > > same one and even VMWare checks file system types for some unknown > > reason. > > VMWare checks for locking capabilities - it doesn't know anything about > XFS as a filesystem but it prints a helpful error message to add > something to your blah.cfg and that helps. > > # Locking on XFS > host.FSSupportLocking1 = 0x58465342 They fixed that when reiserfs became popular. Older vmware wasn't that helpful. It is the wrong way anyways to check for locking, instead they should just do a autoconf style runtime check if it works and be generic. -Andi From owner-linux-xfs@oss.sgi.com Mon Jul 2 15:34:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f62MYib30207 for linux-xfs-outgoing; Mon, 2 Jul 2001 15:34:44 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f62MYgV30200 for ; Mon, 2 Jul 2001 15:34:42 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id AAA824176 for ; Tue, 3 Jul 2001 00:34:39 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 IAA21435; Tue, 3 Jul 2001 08:33:22 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id IAA87518; Tue, 3 Jul 2001 08:33:21 +1000 (EST) Date: Tue, 3 Jul 2001 08:33:21 +1000 From: Nathan Scott To: Steve Lord Cc: stimits@idcomm.com, linux-xfs@oss.sgi.com Subject: Re: fatal error -- couldn't initialize XFS library Message-ID: <20010703083321.B187607@wobbly.melbourne.sgi.com> References: <200106281413.f5SEDWq15561@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200106281413.f5SEDWq15561@jen.americas.sgi.com>; from lord@sgi.com on Thu, Jun 28, 2001 at 09:13:32AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Thu, Jun 28, 2001 at 09:13:32AM -0500, Steve Lord wrote: > > ... > 3. edit /etc/mtab and make sure that / shows up with a ro mount: > > /dev/hda1 / xfs ro 0 0 > there's a couple of problems in the userspace code which we can fix up - firstly, there's a bug in the current readonly mount detection code; we can also do a better job to workaround the readonly-root-so-no-mtab-updates problem by using /proc/mounts if its there (falling back to /etc/mtab if its not). > ... > You can now run xfs_repair -n on the filesystem, it will still not let > you do an actual repair on it. > yup - for the record, thats the correct behaviour with -n (must be a readonly mount); and repair should not run at all on a mounted fs without the -n option (irrespective of readonly state). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 2 19:33:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f632XVk09506 for linux-xfs-outgoing; Mon, 2 Jul 2001 19:33:31 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f632XVV09503 for ; Mon, 2 Jul 2001 19:33:31 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA05312 for ; Mon, 2 Jul 2001 19:30:38 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id VAA2314871 for ; Mon, 2 Jul 2001 21:30:30 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id VAA94038 for ; Mon, 2 Jul 2001 21:30:30 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f632VSR01854; Mon, 2 Jul 2001 21:31:28 -0500 Message-Id: <200107030231.f632VSR01854@jen.americas.sgi.com> Date: Mon, 2 Jul 2001 21:31:28 -0500 Subject: TAKE - more memory pressure handling Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk XFS had no means to apply memory pressure to delwri metadata, this adds it. Date: Mon Jul 2 19:29:39 PDT 2001 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:98098a linux/include/linux/page_buf.h - 1.96 - prototype for delwri flush call linux/fs/pagebuf/page_buf.c - 1.91 - Add exported interface to flush metadata delwri queue, push out the delwri queue when page allocates start failing. linux/fs/xfs_support/kmem.c - 1.9 - push out the pagebuf delwri queue when page allocates start failing. From owner-linux-xfs@oss.sgi.com Mon Jul 2 19:38:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f632coa09963 for linux-xfs-outgoing; Mon, 2 Jul 2001 19:38:50 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f632cjV09959 for ; Mon, 2 Jul 2001 19:38:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id EAA822976 for ; Tue, 3 Jul 2001 04:38:43 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id VAA2325345 for ; Mon, 2 Jul 2001 21:37:27 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id VAA00370 for ; Mon, 2 Jul 2001 21:37:26 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f632cPO01935; Mon, 2 Jul 2001 21:38:25 -0500 Message-Id: <200107030238.f632cPO01935@jen.americas.sgi.com> Date: Mon, 2 Jul 2001 21:38:25 -0500 Subject: TAKE - merge up to 2.4.6-pre9 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Linus is getting busy! The only change which affects xfs here is a tweak to the new sync code. Date: Mon Jul 2 19:33:57 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-base The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98099a linux/arch/mips64/math-emu/sp_frexp.c - 1.1 linux/include/asm-mips/time.h - 1.1 linux/Documentation/DocBook/procfs-guide.tmpl - 1.1 linux/Documentation/DocBook/procfs_example.c - 1.1 linux/include/asm-mips/riscos-syscall.h - 1.1 linux/arch/mips/ld.script.in - 1.1 linux/include/asm-mips/tlb.h - 1.1 linux/include/asm-mips/tx3912.h - 1.1 linux/include/asm-mips/fpu_emulator.h - 1.1 linux/arch/mips64/math-emu/sp_tlong.c - 1.1 linux/arch/mips64/math-emu/sp_tint.c - 1.1 linux/arch/mips64/math-emu/sp_sub.c - 1.1 linux/arch/mips64/math-emu/sp_sqrt.c - 1.1 linux/arch/mips64/math-emu/sp_simple.c - 1.1 linux/arch/mips64/math-emu/sp_scalb.c - 1.1 linux/arch/mips64/math-emu/sp_mul.c - 1.1 linux/arch/mips64/math-emu/sp_modf.c - 1.1 linux/drivers/isdn/tpam/tpam_queues.c - 1.1 linux/arch/mips64/math-emu/sp_logb.c - 1.1 linux/drivers/isdn/tpam/tpam_nco.c - 1.1 linux/drivers/isdn/tpam/tpam_memory.c - 1.1 linux/drivers/isdn/tpam/tpam_main.c - 1.1 linux/drivers/isdn/tpam/tpam_hdlc.c - 1.1 linux/arch/mips64/math-emu/sp_flong.c - 1.1 linux/arch/mips64/math-emu/sp_fint.c - 1.1 linux/include/linux/isdn/tpam.h - 1.1 linux/arch/mips64/math-emu/sp_fdp.c - 1.1 linux/drivers/isdn/tpam/tpam_crcpc.c - 1.1 linux/drivers/isdn/tpam/tpam_commands.c - 1.1 linux/arch/mips64/math-emu/sp_div.c - 1.1 linux/arch/mips64/math-emu/sp_cmp.c - 1.1 linux/arch/mips64/math-emu/sp_add.c - 1.1 linux/arch/mips64/math-emu/kernel_linkage.c - 1.1 linux/arch/mips64/math-emu/ieee754xcpt.c - 1.1 linux/arch/mips64/math-emu/ieee754sp.h - 1.1 linux/drivers/isdn/tpam/tpam.h - 1.1 linux/drivers/isdn/tpam/Makefile - 1.1 linux/arch/mips64/math-emu/ieee754sp.c - 1.1 linux/drivers/isdn/hisax/md - 1.1 linux/arch/mips64/math-emu/ieee754m.c - 1.1 linux/arch/mips64/math-emu/ieee754int.h - 1.1 linux/fs/sysv/itree.c - 1.1 linux/arch/mips/kernel/i8259.c - 1.1 linux/arch/mips64/math-emu/ieee754dp.h - 1.1 linux/fs/sysv/super.c - 1.1 linux/arch/mips64/math-emu/ieee754dp.c - 1.1 linux/arch/mips/kernel/old-irq.c - 1.1 linux/arch/mips/kernel/old-time.c - 1.1 linux/arch/mips/kernel/pci-dma.c - 1.1 linux/arch/mips64/math-emu/ieee754d.c - 1.1 linux/arch/mips64/math-emu/ieee754.h - 1.1 linux/arch/mips64/math-emu/ieee754.c - 1.1 linux/arch/mips64/math-emu/dp_tlong.c - 1.1 linux/arch/mips64/math-emu/dp_tint.c - 1.1 linux/include/asm-mips/mips32_cache.h - 1.1 linux/arch/mips64/math-emu/dp_sub.c - 1.1 linux/arch/mips64/math-emu/dp_sqrt.c - 1.1 linux/arch/mips64/math-emu/dp_simple.c - 1.1 linux/arch/mips64/math-emu/dp_scalb.c - 1.1 linux/arch/mips/kernel/smp.c - 1.1 linux/arch/mips64/math-emu/dp_mul.c - 1.1 linux/include/asm-mips/pmc/ev64120.h - 1.1 linux/include/asm-mips/pmc/ev64120int.h - 1.1 linux/arch/ppc/mm/hashtable.S - 1.1 linux/arch/mips64/math-emu/dp_modf.c - 1.1 linux/arch/mips64/math-emu/dp_logb.c - 1.1 linux/arch/mips64/math-emu/dp_fsp.c - 1.1 linux/arch/mips64/math-emu/Makefile - 1.1 linux/arch/mips64/math-emu/dp_frexp.c - 1.1 linux/arch/mips64/math-emu/dp_flong.c - 1.1 linux/arch/mips64/math-emu/dp_fint.c - 1.1 linux/arch/mips64/math-emu/dp_cmp.c - 1.1 linux/arch/mips64/math-emu/cp1emu.c - 1.1 linux/arch/mips64/math-emu/dp_add.c - 1.1 linux/arch/mips64/math-emu/dp_div.c - 1.1 linux/scripts/header.tk - 1.7 linux/scripts/Menuconfig - 1.11 linux/scripts/Configure - 1.12 linux/net/ipx/af_spx.c - 1.14 linux/net/ax25/ax25_ip.c - 1.7 linux/mm/mmap.c - 1.37 linux/include/linux/sysv_fs_sb.h - 1.3 linux/include/linux/sysv_fs_i.h - 1.3 linux/include/linux/sysv_fs.h - 1.9 linux/include/linux/pci.h - 1.45 linux/include/linux/nfsd/nfsfh.h - 1.10 linux/include/linux/nfsd/nfsd.h - 1.12 linux/include/linux/isdnif.h - 1.11 linux/include/linux/isdn.h - 1.17 linux/include/asm-sparc/vaddrs.h - 1.6 linux/include/asm-sparc/hardirq.h - 1.11 linux/include/asm-ppc/prom.h - 1.11 linux/include/asm-ppc/processor.h - 1.25 linux/include/asm-ppc/pgtable.h - 1.26 linux/include/asm-ppc/mmu_context.h - 1.10 linux/include/asm-ppc/mmu.h - 1.9 linux/include/asm-ppc/machdep.h - 1.16 linux/include/asm-ppc/bootinfo.h - 1.7 linux/include/asm-mips/watch.h - 1.5 linux/include/asm-mips/unistd.h - 1.10 linux/include/asm-mips/unaligned.h - 1.5 linux/include/asm-mips/termios.h - 1.9 linux/include/asm-mips/system.h - 1.9 linux/include/asm-mips/stat.h - 1.5 linux/include/asm-mips/stackframe.h - 1.6 linux/include/asm-mips/spinlock.h - 1.7 linux/include/asm-mips/socket.h - 1.9 linux/include/asm-mips/sni.h - 1.6 linux/include/asm-mips/smp.h - 1.3 linux/include/asm-mips/sgialib.h - 1.6 linux/include/asm-mips/serial.h - 1.5 linux/include/asm-mips/semaphore.h - 1.8 linux/include/asm-mips/resource.h - 1.9 linux/include/asm-mips/ptrace.h - 1.8 linux/include/asm-mips/processor.h - 1.15 linux/include/asm-mips/pgtable.h - 1.13 linux/include/asm-mips/pci.h - 1.10 linux/include/asm-mips/param.h - 1.5 linux/include/asm-mips/mmu_context.h - 1.7 linux/include/asm-mips/mipsregs.h - 1.8 linux/include/asm-mips/mc146818rtc.h - 1.6 linux/include/asm-mips/keyboard.h - 1.8 linux/include/asm-mips/jazzdma.h - 1.5 linux/include/asm-mips/irq.h - 1.6 linux/include/asm-mips/ioctls.h - 1.5 linux/include/asm-mips/ioctl.h - 1.3 linux/include/asm-mips/io.h - 1.7 linux/include/asm-mips/inst.h - 1.3 linux/include/asm-mips/ide.h - 1.8 linux/include/asm-mips/hardirq.h - 1.9 linux/include/asm-mips/fcntl.h - 1.9 linux/include/asm-mips/errno.h - 1.4 linux/include/asm-mips/elf.h - 1.9 linux/include/asm-mips/delay.h - 1.8 linux/include/asm-mips/current.h - 1.5 linux/include/asm-mips/cpu.h - 1.5 linux/include/asm-mips/checksum.h - 1.6 linux/include/asm-mips/cache.h - 1.5 linux/include/asm-mips/bugs.h - 1.5 linux/include/asm-mips/bootinfo.h - 1.9 linux/include/asm-mips/bitops.h - 1.7 linux/include/asm-mips/bcache.h - 1.5 linux/include/asm-mips/atomic.h - 1.6 linux/include/asm-mips/asmmacro.h - 1.5 linux/include/asm-mips/addrspace.h - 1.3 linux/include/asm-i386/uaccess.h - 1.10 linux/include/asm-i386/elf.h - 1.7 linux/fs/sysv/truncate.c - 1.6 linux/fs/sysv/namei.c - 1.12 linux/fs/sysv/inode.c - 1.21 linux/fs/sysv/ialloc.c - 1.7 linux/fs/sysv/fsync.c - 1.6 linux/fs/sysv/file.c - 1.9 linux/fs/sysv/dir.c - 1.8 linux/fs/sysv/balloc.c - 1.5 linux/fs/sysv/Makefile - 1.5 linux/fs/proc/generic.c - 1.22 linux/fs/nfsd/vfs.c - 1.35 linux/fs/nfsd/nfsproc.c - 1.16 linux/fs/nfsd/nfsfh.c - 1.27 linux/fs/nfsd/nfs3xdr.c - 1.18 linux/fs/nfsd/nfs3proc.c - 1.9 linux/fs/nfsd/export.c - 1.19 linux/fs/buffer.c - 1.70 linux/fs/binfmt_elf.c - 1.28 linux/fs/Config.in - 1.64 linux/drivers/sound/cs4232.c - 1.9 linux/drivers/sound/Makefile - 1.29 linux/drivers/sound/Config.in - 1.24 linux/drivers/scsi/scsi_syms.c - 1.12 linux/drivers/pci/pci.c - 1.39 linux/drivers/net/yellowfin.c - 1.23 linux/drivers/net/wavelan.p.h - 1.12 linux/drivers/net/via-rhine.c - 1.25 linux/drivers/net/tlan.h - 1.12 linux/drivers/net/tlan.c - 1.21 linux/drivers/net/sk_g16.c - 1.12 linux/drivers/net/rcpci45.c - 1.19 linux/drivers/net/rclanmtl.h - 1.6 linux/drivers/net/rclanmtl.c - 1.7 linux/drivers/net/rcif.h - 1.3 linux/drivers/net/pcnet32.c - 1.24 linux/drivers/net/epic100.c - 1.22 linux/drivers/net/eepro100.c - 1.31 linux/drivers/net/dummy.c - 1.9 linux/drivers/net/defxx.c - 1.17 linux/drivers/net/Config.in - 1.42 linux/drivers/net/3c59x.c - 1.27 linux/drivers/macintosh/via-pmu.c - 1.14 linux/drivers/isdn/isdnloop/isdnloop.c - 1.6 linux/drivers/isdn/isdn_tty.c - 1.12 linux/drivers/isdn/isdn_net.c - 1.20 linux/drivers/isdn/isdn_common.c - 1.25 linux/drivers/isdn/icn/icn.c - 1.12 linux/drivers/isdn/hisax/netjet.c - 1.16 linux/drivers/isdn/hisax/isdnl3.c - 1.12 linux/drivers/isdn/hisax/isdnl2.c - 1.11 linux/drivers/isdn/hisax/isdnl1.c - 1.12 linux/drivers/isdn/hisax/isac.c - 1.10 linux/drivers/isdn/hisax/hscx.c - 1.9 linux/drivers/isdn/hisax/hisax.h - 1.18 linux/drivers/isdn/hisax/hfc_2bs0.c - 1.12 linux/drivers/isdn/hisax/hfc_2bds0.c - 1.12 linux/drivers/isdn/hisax/config.c - 1.19 linux/drivers/isdn/hisax/callc.c - 1.13 linux/drivers/isdn/hisax/amd7930.c - 1.10 linux/drivers/isdn/Makefile - 1.9 linux/drivers/isdn/Config.in - 1.17 linux/drivers/char/tty_io.c - 1.31 linux/drivers/char/rocket.c - 1.12 linux/drivers/char/random.c - 1.16 linux/drivers/char/defkeymap.c - 1.9 linux/drivers/char/Config.in - 1.43 linux/arch/sparc64/vmlinux.lds - 1.9 linux/arch/sparc/vmlinux.lds - 1.9 linux/arch/ppc/vmlinux.lds - 1.8 linux/arch/ppc/mm/init.c - 1.34 linux/arch/ppc/mm/fault.c - 1.16 linux/arch/ppc/mm/Makefile - 1.6 linux/arch/ppc/kernel/traps.c - 1.19 linux/arch/ppc/kernel/setup.c - 1.32 linux/arch/ppc/kernel/prom.c - 1.22 linux/arch/ppc/kernel/process.c - 1.28 linux/arch/ppc/kernel/ppc_ksyms.c - 1.32 linux/arch/ppc/kernel/ppc_htab.c - 1.13 linux/arch/ppc/kernel/pmac_pci.c - 1.14 linux/arch/ppc/kernel/pci.c - 1.20 linux/arch/ppc/kernel/mk_defs.c - 1.12 linux/arch/ppc/kernel/misc.S - 1.28 linux/arch/ppc/kernel/irq.c - 1.29 linux/arch/ppc/kernel/head.S - 1.26 linux/arch/ppc/kernel/feature.c - 1.12 linux/arch/ppc/kernel/chrp_pci.c - 1.17 linux/arch/ppc/kernel/Makefile - 1.22 linux/arch/ppc/config.in - 1.37 linux/arch/ppc/8xx_io/uart.c - 1.14 linux/arch/ppc/8xx_io/commproc.h - 1.9 linux/arch/ppc/8xx_io/commproc.c - 1.9 linux/arch/mips/tools/offset.c - 1.7 linux/arch/mips/mm/Makefile - 1.6 linux/arch/mips/lib/rtc-std.c - 1.5 linux/arch/mips/lib/rtc-no.c - 1.5 linux/arch/mips/lib/memset.S - 1.6 linux/arch/mips/lib/Makefile - 1.9 linux/arch/mips/ld.script.little - 1.5 linux/arch/mips/ld.script.big - 1.5 linux/arch/mips/kernel/unaligned.c - 1.6 linux/arch/mips/kernel/traps.c - 1.10 linux/arch/mips/kernel/time.c - 1.10 linux/arch/mips/kernel/sysmips.c - 1.7 linux/arch/mips/kernel/sysirix.c - 1.15 linux/arch/mips/kernel/syscalls.h - 1.10 linux/arch/mips/kernel/syscall.c - 1.9 linux/arch/mips/kernel/setup.c - 1.11 linux/arch/mips/kernel/scall_o32.S - 1.8 linux/arch/mips/kernel/r4k_switch.S - 1.7 linux/arch/mips/kernel/r4k_misc.S - 1.8 linux/arch/mips/kernel/r4k_fpu.S - 1.7 linux/arch/mips/kernel/r2300_switch.S - 1.7 linux/arch/mips/kernel/r2300_fpu.S - 1.7 linux/arch/mips/kernel/ptrace.c - 1.9 linux/arch/mips/kernel/process.c - 1.11 linux/arch/mips/kernel/proc.c - 1.5 linux/arch/mips/kernel/mips_ksyms.c - 1.10 linux/arch/mips/kernel/irq.c - 1.10 linux/arch/mips/kernel/irixsig.c - 1.10 linux/arch/mips/kernel/head.S - 1.9 linux/arch/mips/kernel/gdb-stub.c - 1.6 linux/arch/mips/kernel/entry.S - 1.7 linux/arch/mips/kernel/Makefile - 1.7 linux/arch/mips/config.in - 1.22 linux/arch/mips/boot/mkboot.c - 1.3 linux/arch/mips/Makefile - 1.9 linux/arch/m68k/vmlinux.lds - 1.9 linux/arch/i386/vmlinux.lds - 1.13 linux/arch/i386/lib/putuser.S - 1.3 linux/arch/i386/lib/Makefile - 1.15 linux/arch/i386/kernel/i386_ksyms.c - 1.38 linux/arch/i386/defconfig - 1.60 linux/arch/i386/boot/tools/build.c - 1.5 linux/arch/alpha/boot/bootloader.lds - 1.3 linux/Makefile - 1.96 linux/Documentation/fb/matroxfb.txt - 1.7 linux/Documentation/Configure.help - 1.86 linux/include/asm-mips/hdreg.h - 1.4 linux/drivers/isdn/hisax/md5sums.asc - 1.13 linux/drivers/isdn/hisax/isar.c - 1.12 linux/drivers/isdn/hisax/elsa_ser.c - 1.8 linux/drivers/isdn/hisax/avm_pci.c - 1.11 linux/arch/ppc/xmon/xmon.c - 1.16 linux/arch/ppc/xmon/Makefile - 1.5 linux/include/asm-mips/semaphore-helper.h - 1.5 linux/drivers/net/declance.c - 1.11 linux/arch/mips/lib/kbd-std.c - 1.5 linux/arch/mips/dec/boot/ld.ecoff - 1.2 linux/arch/mips/baget/ld.script.balo - 1.2 linux/arch/mips/arc/misc.c - 1.6 linux/arch/mips/arc/memory.c - 1.9 linux/arch/mips/arc/identify.c - 1.5 linux/arch/mips/arc/console.c - 1.6 linux/arch/mips/arc/cmdline.c - 1.6 linux/drivers/isdn/hisax/jade.c - 1.7 linux/drivers/isdn/hisax/hfc_pci.c - 1.16 linux/drivers/net/sis900.c - 1.24 linux/include/linux/atmdev.h - 1.8 linux/arch/ppc/kernel/head_8xx.S - 1.11 linux/arch/ppc/kernel/hashtable.S - 1.11 linux/arch/ppc/kernel/entry.S - 1.20 linux/arch/arm/vmlinux-armv.lds.in - 1.15 linux/arch/arm/vmlinux-armo.lds.in - 1.13 linux/arch/sh/vmlinux.lds.S - 1.11 linux/arch/m68k/vmlinux-sun3.lds - 1.6 linux/include/linux/udf_udf.h - 1.4 linux/fs/udf/ialloc.c - 1.10 linux/fs/udf/inode.c - 1.21 linux/include/linux/udf_fs_i.h - 1.5 linux/include/linux/udf_fs.h - 1.11 linux/fs/udf/udf_i.h - 1.5 linux/drivers/net/starfire.c - 1.15 linux/drivers/net/dmfe.c - 1.17 linux/drivers/net/ncr885e.c - 1.10 linux/arch/ppc/kernel/sleep.S - 1.4 linux/arch/ppc/kernel/m8xx_setup.c - 1.13 linux/include/linux/pci_ids.h - 1.38 linux/arch/arm/boot/compressed/vmlinux.lds.in - 1.4 linux/mm/bootmem.c - 1.15 linux/drivers/video/aty128fb.c - 1.21 linux/drivers/net/sis900.h - 1.9 linux/drivers/isdn/hisax/w6692.c - 1.9 linux/drivers/pci/pci.ids - 1.30 linux/Documentation/networking/sk98lin.txt - 1.5 linux/mm/numa.c - 1.8 linux/include/linux/agp_backend.h - 1.10 linux/drivers/net/aironet4500_proc.c - 1.7 linux/drivers/char/agp/agpgart_be.c - 1.17 linux/drivers/char/agp/agp.h - 1.12 linux/arch/ppc/kernel/ppc4xx_pic.h - 1.3 linux/arch/ia64/vmlinux.lds.S - 1.6 linux/arch/ia64/boot/bootloader.lds - 1.2 linux/drivers/sound/via82cxxx_audio.c - 1.16 linux/drivers/net/8139too.c - 1.21 linux/drivers/isdn/hisax/hfc_sx.c - 1.6 linux/drivers/net/tulip/tulip_core.c - 1.23 linux/include/asm-mips/wbflush.h - 1.3 linux/include/asm-mips/shmbuf.h - 1.2 linux/include/asm-mips/sgi/sgint23.h - 1.3 linux/include/asm-mips/pgalloc.h - 1.5 linux/include/asm-mips/div64.h - 1.3 linux/arch/mips64/ld.script.elf64 - 1.4 linux/arch/alpha/kernel/irq_alpha.c - 1.6 linux/drivers/sound/cs4232.h - 1.2 linux/Documentation/DocBook/Makefile - 1.15 linux/scripts/kernel-doc - 1.10 linux/drivers/sound/emu10k1/audio.c - 1.8 linux/arch/s390/vmlinux.lds - 1.3 linux/include/asm-sh/hitachi_se.h - 1.3 linux/include/asm-mips/hw_irq.h - 1.2 linux/include/asm-mips/orion.h - 1.2 linux/include/asm-ppc/time.h - 1.6 linux/drivers/char/drm/agpsupport.c - 1.4 linux/arch/alpha/vmlinux.lds.in - 1.4 linux/drivers/sound/cs46xx.c - 1.12 linux/drivers/isdn/hisax/icc.c - 1.4 linux/drivers/char/i810-tco.c - 1.6 linux/arch/i386/kernel/bluesmoke.c - 1.10 linux/drivers/block/cciss.c - 1.10 linux/drivers/md/md.c - 1.16 linux/drivers/net/hamachi.c - 1.8 linux/drivers/net/sundance.c - 1.8 linux/drivers/net/winbond-840.c - 1.9 linux/include/asm-ppc/highmem.h - 1.5 linux/include/asm-sparc64/starfire.h - 1.2 linux/drivers/net/lasi_82596.c - 1.4 linux/arch/parisc/vmlinux.lds - 1.2 linux/arch/mips64/ld.script.elf32.S - 1.2 linux/arch/ia64/sn/fprom/fprom.lds - 1.2 linux/fs/reiserfs/inode.c - 1.6 linux/arch/cris/boot/compressed/decompress.ld - 1.3 linux/arch/cris/cris.ld - 1.4 linux/drivers/net/pci-skeleton.c - 1.5 linux/arch/s390x/vmlinux.lds - 1.3 linux/drivers/net/saa9730.c - 1.3 linux/Documentation/networking/TODO - 1.3 linux/arch/mips/math-emu/dp_sub.c - 1.2 linux/arch/mips/math-emu/cp1emu.c - 1.2 linux/drivers/net/fealnx.c - 1.4 linux/drivers/net/wireless/orinoco_cs.c - 1.4 linux/arch/ppc/boot/utils/mkevimg - 1.2 linux/arch/ppc/boot/tree/main.c - 1.2 linux/arch/ppc/boot/tree/ld.script - 1.2 linux/arch/ppc/boot/tree/Makefile - 1.2 linux/arch/ppc/boot/prep/misc.c - 1.3 linux/arch/ppc/boot/prep/Makefile - 1.2 linux/arch/ppc/boot/pmac/ld.script - 1.2 linux/arch/ppc/boot/pmac/coffmain.c - 1.2 linux/arch/ppc/boot/pmac/chrpmain.c - 1.2 linux/arch/ppc/boot/common/misc-common.c - 1.3 linux/arch/ppc/boot/chrp/main.c - 1.2 linux/drivers/net/wireless/airo.c - 1.2 linux/drivers/usb/se401.c - 1.2 From owner-linux-xfs@oss.sgi.com Mon Jul 2 19:47:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f632l2o10695 for linux-xfs-outgoing; Mon, 2 Jul 2001 19:47:02 -0700 Received: from home.smithconcepts.com (ubr-35.28.151.oviedo.cfl.rr.com [65.35.28.151]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f632l1V10692 for ; Mon, 2 Jul 2001 19:47:01 -0700 Received: from ieee.org (IDENT:bjsmith@bitman.oviedo.smithconcepts.com [172.24.24.192]) by home.smithconcepts.com (8.9.3/8.9.3) with ESMTP id WAA23089; Mon, 2 Jul 2001 22:40:36 -0400 Message-ID: <3B4134E2.FA0D3DE3@ieee.org> Date: Mon, 02 Jul 2001 22:58:42 -0400 From: "Bryan J. Smith" Organization: SmithConcepts, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: s-luppescu@uchicago.edu CC: Jurgen Kramer , linux-xfs@oss.sgi.com, Seth Mos Subject: Re: Filesystem on XFS partition no longer accessible afterwritin References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk s-luppescu@uchicago.edu wrote: > home (a K6-2 with a VIA MVP3 chipset) and got fatal file > system corruption within 15 minutes of turning it on. Just FYI ... I have personally had issues with kernel 2.2 w/Hendrick's IDE backport as well as kernel 2.4 on even a late model ViA mVP3 chipset w/a 596A southbridge mainboard. Once I turn off DMA, 0 problems. No problems with newer P2/3/Athlon chipsets with the 596B/686A/686B southbrides though (except for a number of CRC fails/IDE resets on the 596B/686A -- but no data loss whatsoever). -- TheBS -- Bryan J. Smith mailto:b.j.smith@ieee.org chat:thebs413 SmithConcepts, Inc. http://www.SmithConcepts.com ========================================================== Linux 'Worms' exploit known security holes that were fixed 3-12 months earlier. NT/2000 'Worms' exploit unknown se- curity holes that won't be fixed for another 3-12 months. From owner-linux-xfs@oss.sgi.com Mon Jul 2 21:36:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f634aqp22109 for linux-xfs-outgoing; Mon, 2 Jul 2001 21:36:52 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f634apV22098 for ; Mon, 2 Jul 2001 21:36:51 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id VAA03793 for ; Mon, 2 Jul 2001 21:34:07 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA04735 for linux-xfs@oss.sgi.com; Tue, 3 Jul 2001 14:35:33 +1000 (EST) Date: Tue, 3 Jul 2001 14:35:33 +1000 (EST) From: Nathan Scott Message-Id: <200107030435.OAA04735@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs minor updates Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Mon Jul 2 21:33:45 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98108a cmd/xfsprogs/mkfs/mountinfo.h - 1.2 cmd/xfsprogs/mkfs/mountinfo.c - 1.3 - sync with recent changes to mount(8) code - includes ext3 and reiserfs probe changes, so mkfs should now do a better job of detecting these. cmd/xfsprogs/libxfs/init.c - 1.7 - fix a bug in the read-only mount detection code. also use procfs if its there as thats likely to be closer to reality than /etc/mtab. cmd/xfsprogs/include/xfs_mount.h - 1.5 - sync with benign kernel header change. cmd/xfsprogs/doc/CREDITS - 1.10 - update change of FAQ ownership. cmd/xfsprogs/doc/CHANGES - 1.21 cmd/xfsprogs/debian/changelog - 1.16 cmd/xfsprogs/VERSION - 1.19 - bump version to 1.2.8. From owner-linux-xfs@oss.sgi.com Tue Jul 3 00:40:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f637e9Z08229 for linux-xfs-outgoing; Tue, 3 Jul 2001 00:40:09 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f637e7V08226 for ; Tue, 3 Jul 2001 00:40:08 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id AAA03490 for ; Tue, 3 Jul 2001 00:40:05 -0700 (PDT) mail_from (ivanr@snort.melbourne.sgi.com) Received: (from ivanr@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA27000 for linux-xfs@oss.sgi.com; Tue, 3 Jul 2001 17:38:48 +1000 (EST) Date: Tue, 3 Jul 2001 17:38:48 +1000 (EST) From: Ivan Rayner Message-Id: <200107030738.RAA27000@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - improve error message in xfsinvutil Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Use a friendlier error message if inventory does not exist. Thanks to Simon Pabst for the bug report. Ivan Date: Tue Jul 3 00:36:42 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build6/ivanr/isms/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:98113a cmd/xfsdump/invutil/invutil.c - 1.3 From owner-linux-xfs@oss.sgi.com Tue Jul 3 03:53:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f63ArJQ22430 for linux-xfs-outgoing; Tue, 3 Jul 2001 03:53:19 -0700 Received: from mons.uio.no (IDENT:7411@mons.uio.no [129.240.130.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f63Ar4V22396 for ; Tue, 3 Jul 2001 03:53:04 -0700 Received: from tux.uio.no ([129.240.186.23]) by mons.uio.no with esmtp (Exim 2.12 #7) id 15HNnU-00071p-00; Tue, 3 Jul 2001 12:52:48 +0200 Received: from trondham by tux.uio.no with local (Exim 2.12 #1) id 15HNnT-0004JG-00; Tue, 3 Jul 2001 12:52:47 +0200 To: "Marcelo E. Magallon" Cc: werner maes , linux-xfs@oss.sgi.com Subject: Re: XFS & ADSM References: <20010702140752.A1180@ysabell.wh.vaih> From: Trond Hasle Amundsen Date: 03 Jul 2001 12:52:47 +0200 In-Reply-To: <20010702140752.A1180@ysabell.wh.vaih> Message-ID: <15tlmm6mghs.fsf@tux.uio.no> Lines: 25 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Marcelo E. Magallon" writes: > >> werner maes writes: > > > On a system with XFS installed (using the RH 7.1 iso) I'm not able to > > backup my files using ADSM (backup on tape). Without XFS there's no > > problem. > > To put it midly, ADSM is a POS. For some reason it checks the > filesystem type of the partition where the data it is trying to backup > is located, finds it's "xfs", it has no idea what that is and bombs > out. > > The local people in charge or the ADSM backups ended up exporting the > filesystem to the same machine where it resides and mounting that over > NFS (foo exports it's filesystems to foo). ADSM is happy with that. An easier solution is to configure TSM to assume that the partition is only a directory. For example, if you want backup of /var, which on your machine is a partition, put this in the config file: virtualmount /var -- Trond From owner-linux-xfs@oss.sgi.com Tue Jul 3 07:13:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f63EDvY17191 for linux-xfs-outgoing; Tue, 3 Jul 2001 07:13:57 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f63EDuV17188 for ; Tue, 3 Jul 2001 07:13:56 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 72E2E1AB0F for ; Tue, 3 Jul 2001 10:13:55 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 79647120B; Tue, 3 Jul 2001 10:13:54 -0400 (EDT) Date: Tue, 3 Jul 2001 10:13:54 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: xfs_shrink? Message-ID: <20010703101353.A11020@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010701193226.A682@nexus.shadowrun.not> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010701193226.A682@nexus.shadowrun.not> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 01, 2001 at 07:32:26PM +0200, Martin Maciaszek wrote: > I'm running xfs on top of lvm without any problems so far. Now > I want to remove one of the old drives and replace it with a > new drive. As far as I understand it I need to move all PEs > from the old drive to the other PVs and then shrink the fs to > be able to remove the old drive from the LV. > > Is there any chance to exchange the old drive without having > to do a backup/restore? Is someone working on xfs_shrink? I > don't need the drive to be replaced soon, but I can see it > coming on the horizon :) Can you add another drive before you take the old one out? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 3 08:28:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f63FSDX23023 for linux-xfs-outgoing; Tue, 3 Jul 2001 08:28:13 -0700 Received: from fnal.gov (heffalump.fnal.gov [131.225.9.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f63FSCV23018 for ; Tue, 3 Jul 2001 08:28:12 -0700 Received: from thwaite-clued0.fnal.gov ([131.225.224.130]) by smtp.fnal.gov (PMDF V6.0-24 #37519) with ESMTP id <0GFW00C2CLN0IV@smtp.fnal.gov> for linux-xfs@oss.sgi.com; Tue, 03 Jul 2001 10:28:12 -0500 (CDT) Date: Tue, 03 Jul 2001 10:28:12 -0500 (CDT) From: Roger Moore Subject: Re: [patch] Re: Label based mounts with fsck In-reply-to: <20010630075337.A165960@wobbly.melbourne.sgi.com> To: Nathan Scott Cc: linux-xfs@oss.sgi.com Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Great - thanks very much. I did upgrade to 1.22 and the patch worked perfectly. We can now use labels to mount all our volumes which is very useful for our SCSI machines! I can let you have the patched binary and source RPMs if you are interested? Thanks again, Roger On Sat, 30 Jun 2001, Nathan Scott wrote: > hi Roger, > > On Thu, Jun 28, 2001 at 04:46:02PM -0500, Roger Moore wrote: > > Hi, > > > > We've just updated our cluster to use XFS and have noticed a problem with > > using 'LABEL=xxx' in the fstab file. > > > > The 'mount' command works fine with XFS labels (once you turn off devfs!). > > However the problem lies with the fsck command. The RedHat 7.1 system we > > have runs 'fsck -A...' at boot time which is needed for the remaining ext2 > > partitions. This complains that it cannont find 'LABEL=xxx' for XFS > > partitions even when we configure /etc/fstab has f_passno=0 for the XFS > > mounts. Is there a patch out there for fsck to fix this problem? > > > > could you try the attached patch and let me know how it goes? > I think we're getting bitten by the use of DEFAULT_FSTYPE (ext2) > in the fsck_device() routine... this should fix that. > > > We are currently using e2fsprogs-1.21 from RawHide since it is needed for > > the 2.4.5-0.2.9 RawHide kernel which you have patched. > > > > the patch is against e2fsprogs-1.22, but this code doesn't seem > to have changed for awhile and should patch cleanly to 1.21 too. > > if it works, let me know & I'll forward on to Ted. > > thanks. > > -- > Nathan > From owner-linux-xfs@oss.sgi.com Tue Jul 3 09:24:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f63GOMY26282 for linux-xfs-outgoing; Tue, 3 Jul 2001 09:24:22 -0700 Received: from mail.k-net.cz (www.k-net.cz [195.250.131.251]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f63GO4V26277 for ; Tue, 3 Jul 2001 09:24:05 -0700 Message-Id: <200107031624.f63GO4V26277@oss.sgi.com> Received: from ([192.168.2.22]) by mail.k-net.cz (MERAK 3.00.130) with ESMTP id LTE36594 for ; Tue, 03 Jul 2001 14:16:48 +0200 From: "Jaroslav Lukesh" To: Subject: install fail in anaconda Date: Tue, 3 Jul 2001 14:19:39 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_01C103CB.323D3100" Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Toto je vícedílná zpráva formátu MIME. ------=_NextPart_000_01C103CB.323D3100 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Hi, I was try to install XFS with RH7.1, but install fail at sgi-RH CD. Anaconda dump is in attachment. Please note, that the (maybe) same fail was with kickstart (but in them I cannot save dump message). Regards Jaroslav Lukesh, K-net -------------------------------------------------- http://www.k-net.cz Multimedia, Networking, Communications Windows terminals, NC computer hardware and software -------------------------------------------------- note: Bill Gates to Hell! ------=_NextPart_000_01C103CB.323D3100 Content-Type: application/octet-stream; name="anacdump.txt" Content-Transfer-Encoding: quoted-printable Content-Description: anacdump.txt (textový dokument) Content-Disposition: attachment; filename="anacdump.txt" Traceback (innermost last):=0A= File "/usr/bin/anaconda", line 520, in ?=0A= intf.run(todo, test =3D test)=0A= File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 392, in = run=0A= self.icw.run ()=0A= File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 880, in = run=0A= mainloop ()=0A= File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in = mainloop=0A= _gtk.gtk_main()=0A= File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in = __call__=0A= ret =3D apply(self.func, a)=0A= File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 482, in = nextClicked=0A= next =3D self.currentScreen.getNext ()=0A= File = "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line = 130, in getNext=0A= rc =3D self.lba32Check ()=0A= File = "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line = 76, in lba32Check=0A= maxcyl =3D self.todo.fstab.getBootPartitionMaxCylFromDesired()=0A= File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 241, in = getBootPartitionMaxCylFromDesired=0A= bootpart =3D self.getBootDevice()=0A= File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, in = getBootDevice=0A= for (mntpoint, partition, fsystem, doFormat, size) in = self.mountList():=0A= File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1040, in = mountList=0A= self.fsCache[(device, mntpoint)] =3D (1, fsystem)=0A= NameError: fsystem=0A= =0A= Local variables in innermost frame:=0A= size: 3084417=0A= mntpoint: /boot=0A= makeup: ['Raid003', 'Raid007']=0A= device: md0=0A= raidType: 1=0A= start: 63=0A= sortMounts: =0A= fsType: xfs=0A= devices: [('sda1', 'Raid000', 7, 63, 3084417, 192, 1), ('sda5', = 'Raid001', 7, 3084543, 5510232, 535, 1), ('sda6', 'Raid002', 7, 8594838, = 273042, 552, 1), ('sda7', 'Raid003', 7, 8867943, 48132, 555, 1), = ('sdb1', 'Raid004', 7, 63, 3084417, 192, 1), ('sdb5', 'Raid005', 7, = 3084543, 5510232, 535, 1), ('sdb6', 'Raid006', 7, 8594838, 273042, 552, = 1), ('sdb7', 'Raid007', 7, 8867943, 48132, 555, 1)]=0A= fstab: []=0A= self: =0A= raid: [('/boot', 'md0', 'xfs', 1, 63, 3084417, ['Raid003', 'Raid007']), = ('/', 'md1', 'xfs', 1, 3084543, 5510232, ['Raid000', 'Raid004']), = ('/data', 'md2', 'xfs', 1, 8594838, 273042, ['Raid001', 'Raid005']), = ('', 'md3', 'swap', 1, 8867943, 48132, = ['Raid002', 'Raid006'])]=0A= skipExtra: 0=0A= =0A= ToDo object:=0A= (itodo=0A= ToDo=0A= p1=0A= (dp2=0A= S'resState'=0A= p3=0A= S''=0A= sS'progressWindow'=0A= p4=0A= NsS'setupFilesystems'=0A= p5=0A= I1=0A= sS'monitorVsync'=0A= p6=0A= S''=0A= sS'videoCardStateNode'=0A= p7=0A= S''=0A= sS'serial'=0A= p8=0A= I0=0A= sS'ddruidReadOnly'=0A= p9=0A= I0=0A= sS'bootdisk'=0A= p10=0A= I0=0A= sS'videoRamState'=0A= p11=0A= S''=0A= sS'monitorOriginalName'=0A= p12=0A= S''=0A= sS'language'=0A= p13=0A= (itodo=0A= Language=0A= (dp14=0A= S'langInfoByName'=0A= p15=0A= (dp16=0A= S'Arabic (Yemen)'=0A= p17=0A= (S'ar_YE'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Spanish (Argentina)'=0A= p18=0A= (S'es_AR'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Italian (Italy)'=0A= p19=0A= (S'it_IT@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Arabic (Lebanon)'=0A= p20=0A= (S'ar_LB'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Spanish (Guatemala)'=0A= p21=0A= (S'es_GT'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Arabic (Libyan Arab Jamahiriya)'=0A= p22=0A= (S'ar_LY'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Arabic (Oman)'=0A= p23=0A= (S'ar_OM'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Arabic (Iraq)'=0A= p24=0A= (S'ar_IQ'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Spanish (Chile)'=0A= p25=0A= (S'es_CL'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (South Africa)'=0A= p26=0A= (S'en_ZA'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'French (Switzerland)'=0A= p27=0A= (S'fr_CH'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Arabic (Bahrein)'=0A= p28=0A= (S'ar_BH'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Croatian'=0A= p29=0A= (S'hr_HR'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'French (France)'=0A= p30=0A= (S'fr_FR@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Greenlandic (Greenland)'=0A= p31=0A= (S'kl_GL'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Korean (Republic of Korea)'=0A= p32=0A= (S'ko_KR.euckr'=0A= S'iso01'=0A= S'lat0-16'=0A= tsS'Ukrainian'=0A= p33=0A= (S'uk_UA'=0A= S'koi8-u'=0A= S'cyr-sun16'=0A= tsS'Spanish (Mexico)'=0A= p34=0A= (S'es_MX'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Greek'=0A= p35=0A= (S'el_GR'=0A= S'iso07'=0A= S'gr.f16'=0A= tsS'Spanish (El Salvador)'=0A= p36=0A= (S'es_SV'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Honduras)'=0A= p37=0A= (S'es_HN'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Costa Rica)'=0A= p38=0A= (S'es_CR'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Dutch (Netherlands)'=0A= p39=0A= (S'nl_NL@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Serbian (Yugoslavia)'=0A= p40=0A= (S'sr_YU@cyrillic'=0A= S'iso05'=0A= S'cyr-sun16'=0A= tsS'Russian (Ukraine)'=0A= p41=0A= (S'ru_UA'=0A= S'koi8-u'=0A= S'cyr-sun16'=0A= tsS'Afrikaans (South Africa)'=0A= p42=0A= (S'af_ZA'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Norwegian'=0A= p43=0A= (S'no_NO'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Arabic (Morocco)'=0A= p44=0A= (S'ar_MA'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Portuguese (Portugal)'=0A= p45=0A= (S'pt_PT@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Arabic (Algeria)'=0A= p46=0A= (S'ar_DZ'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'French (Belgium)'=0A= p47=0A= (S'fr_BE@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Indonesian'=0A= p48=0A= (S'id_ID'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Danish'=0A= p49=0A= (S'da_DK'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (Denmark)'=0A= p50=0A= (S'en_DK'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Faroese (Faroe Islands)'=0A= p51=0A= (S'fo_FO'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Galician (Spain)'=0A= p52=0A= (S'gl_ES@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'English (New Zealand)'=0A= p53=0A= (S'en_NZ'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Bolivia)'=0A= p54=0A= (S'es_BO'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Cornish (Britain)'=0A= p55=0A= (S'kw_GB'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Arabic (United Arab Emirates)'=0A= p56=0A= (S'ar_AE'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'German (Austria)'=0A= p57=0A= (S'de_AT@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Romanian'=0A= p58=0A= (S'ro_RO'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'Spanish (Paraguay)'=0A= p59=0A= (S'es_PY'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Hebrew (Israel)'=0A= p60=0A= (S'he_IL'=0A= S'iso08'=0A= S'LatArCyrHeb-16'=0A= tsS'German (Luxemburg)'=0A= p61=0A= (S'de_LU@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Spanish (USA)'=0A= p62=0A= (S'es_US'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Portuguese (Brasil)'=0A= p63=0A= (S'pt_BR'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Equador)'=0A= p64=0A= (S'es_EC'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Polish'=0A= p65=0A= (S'pl_PL'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'Slovak'=0A= p66=0A= (S'sk_SK'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'Macedonian'=0A= p67=0A= (S'mk_MK'=0A= S'iso05'=0A= S'cyr-sun16'=0A= tsS'Spanish (Spain)'=0A= p68=0A= (S'es_ES@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Arabic (Syrian Arab Republic)'=0A= p69=0A= (S'ar_SY'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Czech'=0A= p70=0A= (S'cs_CZ'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'Irish'=0A= p71=0A= (S'ga_IE@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Arabic (Jordan)'=0A= p72=0A= (S'ar_JO'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Italian (Switzerland)'=0A= p73=0A= (S'it_CH'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'German (Belgium)'=0A= p74=0A= (S'de_BE@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Albanian'=0A= p75=0A= (S'sq_AL'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Finnish'=0A= p76=0A= (S'fi_FI@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Swedish (Sweden)'=0A= p77=0A= (S'sv_SE'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Peru)'=0A= p78=0A= (S'es_PE'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Dutch (Belgium)'=0A= p79=0A= (S'nl_BE@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Spanish (Panama)'=0A= p80=0A= (S'es_PA'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Venezuela)'=0A= p81=0A= (S'es_VE'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (Great Britain)'=0A= p82=0A= (S'en_GB'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Russian'=0A= p83=0A= (S'ru_RU.koi8r'=0A= S'koi8-u'=0A= S'cyr-sun16'=0A= tsS'Norwegian, Nynorsk (Norway)'=0A= p84=0A= (S'nn_NO'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (Zimbabwe)'=0A= p85=0A= (S'en_ZW'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (USA)'=0A= p86=0A= (S'en_US'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Spanish (Nicaragua)'=0A= p87=0A= (S'es_NI'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Arabic (Kuwait)'=0A= p88=0A= (S'ar_KW'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Spanish (Colombia)'=0A= p89=0A= (S'es_CO'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Basque (Spain)'=0A= p90=0A= (S'eu_ES@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Arabic (Qatar)'=0A= p91=0A= (S'ar_QA'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Arabic (Egypt)'=0A= p92=0A= (S'ar_EG'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'English (Ireland)'=0A= p93=0A= (S'en_IE@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Hungarian'=0A= p94=0A= (S'hu_HU'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'Arabic (Tunisia)'=0A= p95=0A= (S'ar_TN'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'French (Luxemburg)'=0A= p96=0A= (S'fr_LU@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Japanese'=0A= p97=0A= (S'ja_JP.eucJP'=0A= S'iso01'=0A= S'lat0-16'=0A= tsS'Swedish (Finland)'=0A= p98=0A= (S'sv_FI@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Arabic (Saudi Arabia)'=0A= p99=0A= (S'ar_SA'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Spanish (Dominican Republic)'=0A= p100=0A= (S'es_DO'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'French (Canada)'=0A= p101=0A= (S'fr_CA'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (Canada)'=0A= p102=0A= (S'en_CA'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'German (Germany)'=0A= p103=0A= (S'de_DE@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Slovenian (Slovenia)'=0A= p104=0A= (S'sl_SI'=0A= S'iso02'=0A= S'lat2-sun16'=0A= tsS'Spanish (Uruguay)'=0A= p105=0A= (S'es_UY'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'German (Switzerland)'=0A= p106=0A= (S'de_CH'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (Australia)'=0A= p107=0A= (S'en_AU'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Catalan (Spain)'=0A= p108=0A= (S'ca_ES@euro'=0A= S'iso15'=0A= S'lat0-sun16'=0A= tsS'Spanish (Puerto Rico)'=0A= p109=0A= (S'es_PR'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Turkish'=0A= p110=0A= (S'tr_TR'=0A= S'iso09'=0A= S'lat5-sun16'=0A= tsS'Estonian'=0A= p111=0A= (S'et_EE'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Arabic (Sudan)'=0A= p112=0A= (S'ar_SD'=0A= S'iso06'=0A= S'LatArCyrHeb-16'=0A= tsS'Icelandic'=0A= p113=0A= (S'is_IS'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'English (Botswana)'=0A= p114=0A= (S'en_BW'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tsS'Manx Gaelic (Britain)'=0A= p115=0A= (S'gv_GB'=0A= S'iso01'=0A= S'lat0-sun16'=0A= tssS'allSupportedLangs'=0A= p116=0A= (lp117=0A= g42=0A= ag75=0A= ag46=0A= ag28=0A= ag92=0A= ag24=0A= ag72=0A= ag88=0A= ag20=0A= ag22=0A= ag44=0A= ag23=0A= ag91=0A= ag99=0A= ag112=0A= ag69=0A= ag95=0A= ag56=0A= ag17=0A= ag90=0A= ag108=0A= ag55=0A= ag29=0A= ag70=0A= ag49=0A= ag79=0A= ag39=0A= ag107=0A= ag114=0A= ag102=0A= ag50=0A= ag82=0A= ag93=0A= ag53=0A= ag26=0A= ag86=0A= ag85=0A= ag111=0A= ag51=0A= ag76=0A= ag47=0A= ag101=0A= ag30=0A= ag96=0A= ag27=0A= ag52=0A= ag57=0A= ag74=0A= ag103=0A= ag61=0A= ag106=0A= ag35=0A= ag31=0A= ag60=0A= ag94=0A= ag113=0A= ag48=0A= ag71=0A= ag19=0A= ag73=0A= ag97=0A= ag32=0A= ag67=0A= ag115=0A= ag43=0A= ag84=0A= ag65=0A= ag63=0A= ag45=0A= ag58=0A= ag83=0A= ag41=0A= ag40=0A= ag66=0A= ag104=0A= ag18=0A= ag54=0A= ag25=0A= ag89=0A= ag38=0A= ag100=0A= ag36=0A= ag64=0A= ag21=0A= ag37=0A= ag34=0A= ag87=0A= ag80=0A= ag59=0A= ag78=0A= ag109=0A= ag68=0A= ag62=0A= ag105=0A= ag81=0A= ag98=0A= ag77=0A= ag110=0A= ag33=0A= asS'info'=0A= p118=0A= (dp119=0A= S'SUPPORTED'=0A= p120=0A= NssS'supported'=0A= p121=0A= (lsS'default'=0A= p122=0A= NsbsS'instClass'=0A= p123=0A= (icustom=0A= InstallClass=0A= (dp124=0A= S'rootPasswordCrypted'=0A= p125=0A= I0=0A= sS'raidList'=0A= p126=0A= (lsS'nameserver'=0A= p127=0A= S''=0A= sS'x'=0A= NsS'rootPassword'=0A= p128=0A= NsS'makeBootdisk'=0A= p129=0A= I0=0A= sS'installType'=0A= p130=0A= NsS'postScript'=0A= p131=0A= NsS'earlySwapOn'=0A= p132=0A= I0=0A= sS'networkDevice'=0A= p133=0A= NsS'fstab'=0A= p134=0A= (lsS'clearText'=0A= p135=0A= NsS'lilo'=0A= p136=0A= (S'mbr'=0A= p137=0A= I1=0A= S''=0A= tsg13=0A= NsS'name'=0A= p138=0A= S''=0A= sS'postInChroot'=0A= p139=0A= I0=0A= sS'pixmap'=0A= p140=0A= S''=0A= sS'partitions'=0A= p141=0A= (lp142=0A= (S'/boot'=0A= p143=0A= (I48=0A= I-1=0A= I0=0A= t(S''=0A= I-1=0A= I0=0A= t(I0=0A= S'xfs'=0A= p144=0A= I0=0A= tNta(S'/'=0A= (I700=0A= I-1=0A= I1=0A= t(S''=0A= I-1=0A= I0=0A= t(I0=0A= g144=0A= I0=0A= tNta(S'swap'=0A= p145=0A= (I128=0A= I256=0A= I1=0A= t(S''=0A= I-1=0A= I0=0A= t(I0=0A= NI0=0A= tNtasS'clearType'=0A= p146=0A= S'wkst'=0A= p147=0A= sS'gateway'=0A= p148=0A= S''=0A= sS'mouse'=0A= p149=0A= NsS'packages'=0A= p150=0A= NsS'timezone'=0A= p151=0A= NsS'zeroMbr'=0A= p152=0A= I0=0A= sS'keyboard'=0A= p153=0A= NsS'groups'=0A= p154=0A= NsS'bootProto'=0A= p155=0A= NsS'netmask'=0A= p156=0A= S''=0A= sS'langdefault'=0A= p157=0A= NsS'skipSteps'=0A= p158=0A= (dsS'auth'=0A= p159=0A= (I1=0A= I1=0A= I0=0A= S''=0A= I0=0A= S''=0A= I0=0A= I0=0A= S''=0A= S''=0A= I0=0A= S''=0A= S''=0A= S''=0A= I0=0A= S''=0A= S''=0A= tsS'hostname'=0A= p160=0A= NsS'langsupported'=0A= p161=0A= NsS'showgroups'=0A= p162=0A= NsS'ip'=0A= p163=0A= S''=0A= sS'firewall'=0A= p164=0A= (I-1=0A= I1=0A= (lp165=0A= S''=0A= I0=0A= I0=0A= I0=0A= I0=0A= I0=0A= I0=0A= tsS'defaultRunlevel'=0A= p166=0A= NsS'desktop'=0A= p167=0A= S''=0A= sS'clearPartText'=0A= p168=0A= S'Automatic partitioning will erase any preexisting Linux installations = on your system.'=0A= p169=0A= sS'clearParts'=0A= p170=0A= I2=0A= sbsS'bdstate'=0A= p171=0A= S''=0A= sS'extraModules'=0A= p172=0A= (lp173=0A= sS'rootpassword'=0A= p174=0A= NsS'fdDevice'=0A= p175=0A= S'fd0'=0A= p176=0A= sS'installSystem'=0A= p177=0A= I1=0A= sS'comps'=0A= p178=0A= NsS'verifiedState'=0A= p179=0A= Nsg159=0A= (itodo=0A= Authentication=0A= (dp180=0A= S'useNIS'=0A= p181=0A= I0=0A= sS'nisServer'=0A= p182=0A= S''=0A= sS'useLdap'=0A= p183=0A= I0=0A= sS'krb5Kdc'=0A= p184=0A= S''=0A= sS'ldapTLS'=0A= p185=0A= S''=0A= sS'useHesiod'=0A= p186=0A= I0=0A= sS'ldapServer'=0A= p187=0A= S''=0A= sS'nisDomain'=0A= p188=0A= S''=0A= sS'krb5Realm'=0A= p189=0A= S''=0A= sS'useLdapauth'=0A= p190=0A= I0=0A= sS'hesiodRhs'=0A= p191=0A= S''=0A= sS'useShadow'=0A= p192=0A= I1=0A= sS'nisuseBroadcast'=0A= p193=0A= I0=0A= sS'useKrb5'=0A= p194=0A= I0=0A= sS'useMD5'=0A= p195=0A= I1=0A= sS'ldapBasedn'=0A= p196=0A= S''=0A= sS'krb5Admin'=0A= p197=0A= S''=0A= sS'hesiodLhs'=0A= p198=0A= S''=0A= sS'hesiodDlhs'=0A= p199=0A= S''=0A= sbsS'users'=0A= p200=0A= NsS'hdList'=0A= p201=0A= NsS'dhcpState'=0A= p202=0A= S''=0A= sS'method'=0A= p203=0A= (iimage=0A= CdromInstallMethod=0A= p204=0A= (dp205=0A= g4=0A= =0A= =0A= ------=_NextPart_000_01C103CB.323D3100 Content-Type: application/octet-stream; name="KS.CFG" Content-Transfer-Encoding: quoted-printable Content-Description: Ks.cfg (CFG soubor) Content-Disposition: attachment; filename="KS.CFG" #komplet lang cs_CZ langsupport cs_CZ keyboard "us" mouse generic --emulthree --device ttyS0 timezone Europe/Prague rootpw hheslo cdrom xconfig --server "SVGA" --monitor "generic monitor" #xconfig --server "/etc/X11/X: symbolic link to = ../../usr/X11R6/bin/XFree86" --monitor "generic monitor" network --bootproto static --ip 192.168.2.63 --netmask 255.255.255.0 = --gateway 192.168.2.1 firewall --disabled zerombr yes clearpart --all #part /boot --size 20 #part / --size 1000 --grow #part swap --size 128 #part /data --size 1500 # device def. # /boot part raid.01 --size 20 --ondisk sda part raid.02 --size 20 --ondisk sdb raid /boot raid.01 raid.02 --level 1 --device md0 # NON-RAID #part /boot --size 20 --ondisk sda #part /boot2 --size 20 --ondisk sdb # /data - bude reiserfs part raid.03 --size 300 --ondisk sda --grow part raid.04 --size 300 --ondisk sdb --grow raid /data raid.03 raid.04 --level 1 --device md1 # swap part raid.05 --size 127 --ondisk sda part raid.06 --size 127 --ondisk sdb raid swap raid.05 raid.06 --level 1 --device md2 # / part raid.07 --size 1500 --ondisk sda part raid.08 --size 1500 --ondisk sdb=0A= raid / raid.07 raid.08 --level 1 --device md3=0A= lilo --location mbr #lilo --location mbr --append "mem=3D128M" install auth %packages @DOS/Windows Connectivity #@Development #@Kernel Development #@Network Management Workstation #@Networked Workstation @SMB (Samba) Server #@Utilities #@X Window System etcskel-czech-root etcskel-latin2-root mailcap man-pages-cs redhat-release filesystem glibc chkconfig cracklib db2 dosfstools eject file gdbm gmp iputils #libjpeg losetup mingetty net-tools nkf cstools pwdb rmt shadow-utils newt setuptool statserial tcl termcap bash bzip2 hotplug arts logrotate modutils info cpp ed at findutils gettext ash gzip m4 man openssl procmail psmisc readline rootfiles console-tools sharutils sysklogd tcsh textutils czech-adaptation mkinitrd mkbootdisk switchdesk tmpwatch traceroute utempter vim-minimal words pam cyrus-sasl kudzu passwd samba-client freetype krbafs autofs SysVinit gtk+ libungif tk tclx tix Xaw3d libmng gd libxml imlib gdk-pixbuf locale_config pygnome-libglade 4Suite pygtk pythonlib rpm-python ucd-snmp util-linux apmd kernel iptables lokkit openssh openssh-clients pciutils pump samba tcpdump usermode anacron chkfontpath XFree86 mkxauth urw-fonts-ISO8859-2 XFree86-100dpi-fonts XFree86-ISO8859-2-75dpi-fonts XFree86-twm samba-swat xinitrc xtt-fonts arpwatch automake dev86 fvwm2-icons glibc-devel gcc-g77 ksconfig libstdc++-devel libtool ltrace memprof nc nut-client parted pmake rpm-build rsync shapecfg strace sysctlconfig tripwire vnc WindowMaker wmconfig XFree86-ISO8859-2-100dpi-fonts etcskel-czech etcskel-latin2 glibc-common man-pages redhat-logos setup basesystem bdflush compat-libstdc++ db1 db3 e2fsprogs expat finger glib hdparm ksymoops libtool-libs mailx mktemp netpbm perl popt rdist setserial slang ntsysv specspo syslinux tcp_wrappers libtermcap audiofile esound libstdc++ groff MAKEDEV ncurses cpio diffutils fileutils dev gawk grep dhcpcd less make ncftp ORBit procps raidtools ftp sed kbdconfig slocate tar telnet apache mount lilo mouseconfig time crontabs unzip vim-common which cracklib-dicts authconfig gpm mc samba-common sh-utils krb5-libs #openldap #sendmail XFree86-libs control-panel rxvt expect timetool tksysv zlib libpng libtiff netpbm-progs gnome-libs libglade pygtk-libglade python alchemist pygnome rpm tkinter ucd-snmp-utils initscripts ipchains devfsd kernel-headers netcfg openssh-askpass openssh-server pidentd quota sysstat timeconfig vixie-cron XFree86-xfs urw-fonts Mesa qt Xconfigurator XFree86-75dpi-fonts XFree86-tools xinetd telnet-server XFree86-xdm VFlib2 autoconf binutils dump fvwm2 gcc iproute libPropList gcc-c++ lsof mawk mkkickstart ncompress nut-cgi nut patch rgrep rpmlint screen stat sudo sysreport unarj WindowMaker-libs wmakerconf xdelta xpdf linuxconf gnome-linuxconf lynx links netscape-common netscape-navigator logrotate tofrodos ext2ed reiserfs-utils %post ------=_NextPart_000_01C103CB.323D3100-- From owner-linux-xfs@oss.sgi.com Tue Jul 3 09:36:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f63GabQ26645 for linux-xfs-outgoing; Tue, 3 Jul 2001 09:36:37 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f63GaaV26642 for ; Tue, 3 Jul 2001 09:36:36 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA19332 for ; Tue, 3 Jul 2001 09:36:29 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2295820; Tue, 3 Jul 2001 11:35:20 -0500 (CDT) Received: from sgi.com (eagdhcp-187-24.americas.sgi.com [128.162.187.174]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA61516; Tue, 3 Jul 2001 11:35:20 -0500 (CDT) Message-ID: <3B41F3D8.4F76EB51@sgi.com> Date: Tue, 03 Jul 2001 22:33:28 +0600 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-xfs-1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jaroslav Lukesh CC: linux-xfs@oss.sgi.com Subject: Re: install fail in anaconda References: <200107031624.f63GO4V26277@oss.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jaroslav Lukesh wrote: > > Hi, > > I was try to install XFS with RH7.1, but install fail at sgi-RH CD. > Anaconda dump is in attachment. Hi Jaroslav - Please try either of these solultions: 1) use the update image at ftp://oss.sgi.com/projects/xfs/download/Release-1.0/updates/anaconda-update-May07-14.img by dd-ing it to a floppy, and typing "linux updates" at the install prompt 2) use the newer test ISO at ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/iso/xfs-1.0.1-PR3.iso Thanks, -Eric From owner-linux-xfs@oss.sgi.com Tue Jul 3 12:30:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f63JUxa29716 for linux-xfs-outgoing; Tue, 3 Jul 2001 12:30:59 -0700 Received: from merle.it.northwestern.edu (merle.acns.nwu.edu [129.105.16.57]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f63JUvV29713 for ; Tue, 3 Jul 2001 12:30:57 -0700 Received: from localhost (nch425@localhost) by merle.it.northwestern.edu (8.8.7/8.8.7) with SMTP id OAA09278; Tue, 3 Jul 2001 14:30:56 -0500 (CDT) Date: Tue, 3 Jul 2001 14:30:56 -0500 (CDT) From: "Ned C. Haubein" Reply-To: Ned Haubein To: linux-xfs@oss.sgi.com Subject: xfsdump: problems spanning tapes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, We've recently installed XFS on our system (Red Hat 7.1, kernel 2.4-5, xfsdump-1.0.9-0) and are having some problems dumping one of our filesystems. The dump won't fit on one tape but we're not prompted for a media change at the end of the dump - it just dies. The dump command line is: /usr/sbin/xfsdump -p 300 -l 0 -o -J -f machine:/dev/nrmt0h /home The remote device is a Seagate SCSI tape drive on a Tru64 system. Dumps on a single tape seem fine and dumps from our IRIX machines are fine (all fit on one tape, though), and regular dump on the Tru64 machines is able to span multiple tapes. Has anyone else seen this and if so come up with a work-around or solution? Finally, just as a note, when dumping the IRIX machines, we normally use the -m -b 245760 options, but these fail on the linux version with the error: xfsdump: drive_minrmt.c:2201: do_end_write: Assertion `first_rec_w_err >= 0' failed. Thanks for the help, - ned Output from multi-tape failure: ____________________________________________________ /usr/sbin/xfsdump: creating dump session media file 0 (media 0, file 0) /usr/sbin/xfsdump: dumping ino map /usr/sbin/xfsdump: dumping directories /usr/sbin/xfsdump: dumping non-directory files /usr/sbin/xfsdump: status at 10:51:11: 1095/66761 files dumped, 1.2% complete, 269 seconds elapsed /usr/sbin/xfsdump: status at 10:56:08: 2485/66761 files dumped, 3.1% complete, 566 seconds elapsed /usr/sbin/xfsdump: status at 11:01:02: 4447/66761 files dumped, 4.9% complete, 860 seconds elapsed /usr/sbin/xfsdump: WARNING: could not open regular file ino 1805058 mode 0x00008180: No such file or directory : not dumped /usr/sbin/xfsdump: status at 11:06:02: 6361/66761 files dumped, 6.8% complete, 1160 seconds elapsed . . . . /usr/sbin/xfsdump: status at 13:26:02: 37414/66761 files dumped, 58.2% complete, 9560 seconds elapsed /usr/sbin/xfsdump: status at 13:31:04: 39360/66761 files dumped, 60.4% complete, 9862 seconds elapsed /usr/sbin/xfsdump: WARNING: write to machine:/dev/nrmt0h failed: 5 (Input/output error) /usr/sbin/xfsdump: ending media file /usr/sbin/xfsdump: media file size 4854382592 bytes /usr/sbin/xfsdump: dump size (non-dir files) : 4838610896 bytes /usr/sbin/xfsdump: NOTE: dump interrupted: 10021 seconds elapsed _____________________________________________ From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:04:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6474DR27724 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:04:13 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6474BV27716 for ; Wed, 4 Jul 2001 00:04:12 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA10351 for ; Wed, 4 Jul 2001 08:31:31 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA06092 for linux-xfs@oss.sgi.com; Wed, 4 Jul 2001 08:31:30 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 1F8D157306 for ; Wed, 4 Jul 2001 08:40:50 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 389CE25835 for ; Wed, 4 Jul 2001 08:48:56 +0200 (CEST) Message-ID: <3B42B86D.8825D027@ch.sauter-bc.com> Date: Wed, 04 Jul 2001 08:32:13 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Processes don't get killed on shutdown now Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm using RH-7.1 XFS with kernel 2.4.3-SGI_XFS_1.0.1_PR3 and there is something I don't know whether it's XFS related. When I make a 'telinit 1' of 'shutdown now' system goes down to single user but several processes don't get killed and servies are not shut down as they are supposed to. I have read in the FAQ and on this list about hanging processes so I'm asking whether this could also be XFS related? Can someone confirm the same? Simon From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:05:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6475gr27901 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:05:42 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6475gV27898 for ; Wed, 4 Jul 2001 00:05:42 -0700 Received: from merle.it.northwestern.edu (merle.acns.nwu.edu [129.105.16.57]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id TAA08155 for ; Tue, 3 Jul 2001 19:05:53 -0700 (PDT) mail_from (nch425@merle.acns.nwu.edu) Received: from localhost (nch425@localhost) by merle.it.northwestern.edu (8.8.7/8.8.7) with SMTP id PAA05106; Tue, 3 Jul 2001 15:22:02 -0500 (CDT) Date: Tue, 3 Jul 2001 15:22:02 -0500 (CDT) From: "Ned C. Haubein" Reply-To: Ned Haubein To: linux-xfs@oss.sgi.com Subject: xfsdump: problems spanning tapes (more info) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk After my last message, I decided to try and use the -s flag to dump only 2 users directories to the tape. xfsdump failed again with the message: /usr/sbin/xfsdump: status at 15:09:28: 9782/29233 files dumped, 27.7% complete, 3282 seconds elapsed /usr/sbin/xfsdump: WARNING: write to machine:/dev/nrmt0h failed: 5 (Input/output error) /usr/sbin/xfsdump: ending media file /usr/sbin/xfsdump: media file size 1690304512 bytes /usr/sbin/xfsdump: dump size (non-dir files) : 1680453600 bytes /usr/sbin/xfsdump: NOTE: dump interrupted: 3516 seconds elapsed I noted the following messages in the log on the remote machine: Jul 3 15:13:22 machine vmunix: ITPSA0: HTH intr. on bus 0, SBCL = 0x20 Jul 3 15:13:24 machine vmunix: ITPSA0: SCSI Bus was reset My ability to debug SCSI problems isn't that great, so I don't know if this is a SCSI prob causing an xfsdump problem, or an xfsdump problem causing the SCSI bus reset. Any insight would be appreciated here. We'd like to avoid just dropping tar files directly on the tape. - ned From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:04:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6474C227717 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:04:12 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6474AV27712 for ; Wed, 4 Jul 2001 00:04:10 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA12716 for ; Wed, 4 Jul 2001 08:48:00 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA07511 for linux-xfs@oss.sgi.com; Wed, 4 Jul 2001 08:47:59 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 2B3F157306 for ; Wed, 4 Jul 2001 08:57:32 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 809CD25835 for ; Wed, 4 Jul 2001 09:05:38 +0200 (CEST) Message-ID: <3B42BC57.504A20FF@ch.sauter-bc.com> Date: Wed, 04 Jul 2001 08:48:55 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Could IDE UDMA corruption be kgcc related? Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I was disturbing this list with my IDE UDMA corruption problem several times now and I have another question about that. When I put heavy load on more than one IDE UDMA disk simultaneously, I get filesystem corruption. This happens on several IDE / Motherboard combinations. I have tried different kernels and until 2.4.3-SGI_XFS_1.0.1_PR3 it was all the same. Now, could it be that we have to blame egcs-2.91.66 for this? That's why I post to the XFS list because we are the people compiling the RH kernels with egcs-2.91.66 instead of gcc-2.96-85. As I read on this list XFS kernels can not be compiled with 2.96-85 because it breaks something, could it be that egcs-2.91.66 breaks something else in the RedHat Kernels. Why then does RedHat use 2.96-85 for the kernel? BTW unfortunately I don't have the failing systems available for more test. I'm just trying to find what went wrong. Simon From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:13:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f647D5K29013 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:13:05 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f647D3V29010 for ; Wed, 4 Jul 2001 00:13:03 -0700 Received: from mx.dc1.adelphia.net (mx.dc1.adelphia.net [64.8.25.34]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id VAA07433 for ; Tue, 3 Jul 2001 21:56:22 -0700 (PDT) mail_from (reefmaster@bigfoot.com) Received: from smtprelay2.adelphia.net (smtprelay2.adelphia.net [64.8.25.7] (may be forged)) by mx.dc1.adelphia.net (8.11.1/8.11.1) with ESMTP id f644tqH17185 for ; Wed, 4 Jul 2001 00:55:53 -0400 (EDT) Received: from gandalf ([24.51.35.173]) by smtprelay2.adelphia.net (Netscape Messaging Server 4.15) with SMTP id GFXN1C03.1BD for ; Wed, 4 Jul 2001 00:56:00 -0400 Content-Type: text/plain; charset="iso-8859-1" From: Dale Kosan To: linux-xfs@oss.sgi.com Subject: error Date: Wed, 4 Jul 2001 01:00:04 -0400 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01070401000401.01189@gandalf> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I installed Redhat 7.1 with your install disk and all is going smooth, sort of. I fixed the sound problem of module not loading and also the error of it trying to turn swap on twice, but I still have one error that is bugging me. When it gets to the updating fstab file I get "cannot stat /dev/sdo1:no such file or directory" Any clues? Thanks for any help in advance. From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:23:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f647NGw30371 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:23:16 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f647N7V30346 for ; Wed, 4 Jul 2001 00:23:08 -0700 Received: from blv-smtpout-01.boeing.com ([192.161.36.5]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA05851 for ; Tue, 3 Jul 2001 15:25:40 -0700 (PDT) mail_from (ric@pipcws.ca.boeing.com) Received: from blv-av-02.boeing.com ([192.54.3.92]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id PAA07025 for ; Tue, 3 Jul 2001 15:24:38 -0700 (PDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by blv-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-01) with ESMTP id PAA12608 for ; Tue, 3 Jul 2001 15:25:39 -0700 (PDT) Received: from [136.203.14.68] by blv-hub-01.boeing.com with ESMTP; Tue, 3 Jul 2001 15:25:25 -0700 Message-Id: <3B424654.6030902@pipcws.ca.boeing.com> Date: Tue, 03 Jul 2001 15:25:24 -0700 From: Ric Tibbetts User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: en-us MIME-Version: 1.0 To: Steve Lord CC: Seth Mos , "Bernhard R. Erdmann" , Linux XFS Mailing List Subject: Re: XFS vs. JFS References: <4.3.2.7.2.20010701135304.03a05bb0@pop.xs4all.nl> <200107011212.f61CCgM15038@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: >>At 12:04 1-7-2001 +0200, Bernhard R. Erdmann wrote: >> >>>Hi, >>> >>>how do you think about IBM's JFS for Linux version 1.0 released last >>>friday? >>>http://oss.software.ibm.com/jfs/ >>> >>It's great because now we really _do_ have 3 journaling fs. >>It gives people choice which is very important. >> >>Each has it's own merits but here are some: >> >>IBM has it's own userbase that has AIX with JFS. Don't know if the layout >>is compatible. >> > >The JFS IBM released for Linux comes from the OS/2 version, not AIX. I >do not know if they are on disk compatible or not. Steve Best has given >lots of talks, at least some of them should be out on the net for people >to look at. I have not seen one of his talks for several months, so I >cannot comment on features etc of the 1.0 release. > The last I heard, AIX JFS , and Linux JFS are not disk compatible "yet". Linux JFS is a port from OS./2, and has no roots in AIX. I suspect that what we will see happen is that the "new" Linux JFS will be ported over to AIX with AIX v5, and then we'll see disk compatabilitiy. This is what I've heard from the IBM community. Ric From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:24:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f647OR030609 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:24:27 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f647OQV30600 for ; Wed, 4 Jul 2001 00:24:26 -0700 Received: from blv-smtpout-01.boeing.com ([192.161.36.5]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA02857 for ; Tue, 3 Jul 2001 15:04:35 -0700 (PDT) mail_from (ric@pipcws.ca.boeing.com) Received: from blv-av-01.boeing.com ([192.54.3.60]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id PAA19307 for ; Tue, 3 Jul 2001 15:03:31 -0700 (PDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-01) with ESMTP id PAA13406 for ; Tue, 3 Jul 2001 15:04:31 -0700 (PDT) Received: from [136.203.14.68] by blv-hub-01.boeing.com with ESMTP for linux-xfs@oss.sgi.com; Tue, 3 Jul 2001 15:04:22 -0700 Message-Id: <3B424166.2020706@pipcws.ca.boeing.com> Date: Tue, 03 Jul 2001 15:04:22 -0700 From: Ric Tibbetts User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: en-us MIME-Version: 1.0 To: Linux XFS Mailing List Subject: XFS Size Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Are there an plans to reduce/optomize the compiles size of XFS so that if you compile it into the kernel it will fit on a floppy? I've run into resistance to using XFS because your only options for rescue are to build a boot CD, or set up an initrc.img to boot from. It would be far easier if an XFS enabled kernel would fit on a floppy. Thanks! Ric Tibbetts From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:25:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f647Pkt30831 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:25:46 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f647PkV30815 for ; Wed, 4 Jul 2001 00:25:46 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA01403 for ; Tue, 3 Jul 2001 15:13:08 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id PAA80829 for ; Tue, 3 Jul 2001 15:20:05 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id AF9F615A185 for ; Tue, 3 Jul 2001 15:14:27 -0700 (PDT) Subject: Re: 1.0.1-PR3 installer ISO (tested!) From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <3B3CD884.47AD4FC4@sgi.com> References: <3B3CD884.47AD4FC4@sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 03 Jul 2001 15:14:27 -0700 Message-Id: <994198467.7960.0.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 29 Jun 2001 14:35:32 -0500, Eric Sandeen wrote: > Ok, there's a new system installer iso at > > ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/iso/ > > for the new 1.0.1-PR3 XFS code. Now, guys, this is very nice, but why don't you loopback-mount the ISO so we can download only a piece of it, if we want to? ;-) -- Florin Andrei From owner-linux-xfs@oss.sgi.com Wed Jul 4 00:35:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f647Zts31807 for linux-xfs-outgoing; Wed, 4 Jul 2001 00:35:55 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f647ZqV31802 for ; Wed, 4 Jul 2001 00:35:54 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA08438 for ; Tue, 3 Jul 2001 20:14:29 -0700 (PDT) mail_from (alane@geeksrus.net) Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f643EMW02102 for linux-xfs@oss.sgi.com; Tue, 3 Jul 2001 23:14:22 -0400 Date: Tue, 3 Jul 2001 23:14:22 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: [dgilbert@interlog.com: Re: sg patches in ac18] Message-ID: <20010703231422.A2019@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Here's what Douglas Gilbert had to say about the SCSI generic driver patch: ----- Forwarded message from Douglas Gilbert ----- Alan Eldridge wrote: > > I ran into the process hang on allocation in the sg driver with 2.4.5. As > I'm using the SGI XFS-port tree, I have just patched in those two patches > (one just comments in the .h) in order to stabilize sg. > > There have been several persons asking about the applicability of that patch > backwards from 2.4.5, and its status re integration into Linus's tree. > > Could you comment on what versions of the kernel need this patch, and the > patch's integration status, so that I might post it back to the list? Or, if > you wish, post directly to linux-xfs@oss.sgi.com. Alan, The patch is in lk 2.4.5-ac18 and onwards. It is sg version 3.1.19 and is available as a source tarball at http://www.torque.net/sg Since Linus doesn't track the SCSI subsystem (and Alan Cox does) then I don't bother submitting bug fixes to Linus. Eric Youngdale and I still have bug fixes pending from January stranded in the "ac" tree. So I don't know whether it will make it into lk 2.4.6 Hopefully Linus will start the lk 2.5 tree and leave "ac" to do lk 2.4.7 . Any sg version 3.1.* can go in the lk 2.4 series. There has been _no_ introduced incompatibility that I am aware of that effects the sg driver across the lk 2.4 series. Therefore sg version 3.1.19 can be backported to lk 2.4.5 Feel free to pass this information back to linux-xfs@oss.sgi.com [I have enough lists to monitor already.] > Thanks much for your assistance. > > P.S. The way the hang happened to me was in cdda2wav, where it was trying to > increase a data buffer size. It only locked up the process under X; early on [...my own text elided...] Yep, that sounds like the one:-) Doug Gilbert ----- End forwarded message ----- -- Alan Eldridge "Gee, Bill, what do you want to do tonight?" "The same thing we do every night, Steve. Try to take over the world!" From owner-linux-xfs@oss.sgi.com Wed Jul 4 04:16:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64BGRn12759 for linux-xfs-outgoing; Wed, 4 Jul 2001 04:16:27 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64BGOV12751 for ; Wed, 4 Jul 2001 04:16:24 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id CAA06476 for ; Wed, 4 Jul 2001 02:23:48 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA02159; Wed, 4 Jul 2001 19:22:23 +1000 (EST) Date: Wed, 4 Jul 2001 19:22:23 +1000 From: Timothy Shimmin To: Ned Haubein Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump: problems spanning tapes (more info) Message-ID: <20010704192223.B1775@boing.melbourne.sgi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: ; from nch425@merle.acns.nwu.edu on Tue, Jul 03, 2001 at 03:22:02PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Ned, On Tue, Jul 03, 2001 at 03:22:02PM -0500, Ned C. Haubein wrote: > > After my last message, I decided to try and use the -s flag to dump only 2 > users directories to the tape. xfsdump failed again with the message: > > /usr/sbin/xfsdump: status at 15:09:28: 9782/29233 files dumped, 27.7% > complete, 3282 seconds elapsed > /usr/sbin/xfsdump: WARNING: write to machine:/dev/nrmt0h failed: 5 > (Input/output error) > /usr/sbin/xfsdump: ending media file > /usr/sbin/xfsdump: media file size 1690304512 bytes > /usr/sbin/xfsdump: dump size (non-dir files) : 1680453600 bytes > /usr/sbin/xfsdump: NOTE: dump interrupted: 3516 seconds elapsed > > I noted the following messages in the log on the remote machine: > > Jul 3 15:13:22 machine vmunix: ITPSA0: HTH intr. on bus 0, SBCL = 0x20 > Jul 3 15:13:24 machine vmunix: ITPSA0: SCSI Bus was reset > > My ability to debug SCSI problems isn't that great, so I don't know if > this is a SCSI prob causing an xfsdump problem, or an xfsdump problem > causing the SCSI bus reset. > > Any insight would be appreciated here. We'd like to avoid just dropping > tar files directly on the tape. > I don't think this would be an xfsdump problem in this case. We have tested the -s option of xfsdump on linux for QA tests of 022, 023 and 043 without any problems. It looks like your write to machine:/dev/nrmt0h just failed with an I/O error. Why don't you try it again with debugging turned on by adding the "-v5" option. SEE BELOW! On Tue, Jul 03, 2001 at 02:30:56PM -0500, Ned C. Haubein wrote: > Hi, > > We've recently installed XFS on our system (Red Hat 7.1, kernel 2.4-5, > xfsdump-1.0.9-0) and are having some problems dumping one of our > filesystems. The dump won't fit on one tape but we're not prompted for a > media change at the end of the dump - it just dies. The dump command line > is: > > /usr/sbin/xfsdump -p 300 -l 0 -o -J -f machine:/dev/nrmt0h /home > > The remote device is a Seagate SCSI tape drive on a Tru64 system. Dumps > on a single tape seem fine and dumps from our IRIX machines are fine (all > fit on one tape, though), and regular dump on the Tru64 machines is able > to span multiple tapes. Has anyone else seen this and if so come up with a > work-around or solution? > No I haven't seen this before. But then again I have never used a Tru64 system before. I have tested multiple tapes locally on Linux with success. Can you tell me all the messages you do get from xfsdump ? Could you run it with -v5 (or -v drive=debug) ? Looking at the code: * the remote writing routine librmt/rmtwrite.c will setoserror to EIO if the write fails to write out the requested nbytes. This seems pretty general - if any error then make it EIO. * in drive_scsitape.c, the write routines call write_record() which calls Write() and then calls determine_write_error(). determine_write_error() will return DRIVE_ERROR_EOM for error of EIO. * Any of the dumping functions called from content_stream_dump() in a loop, such as: inomap_dump() dump_dirs() bigstat_iter(...,dump_file,...) will call the writing routine and if it fails with DRIVE_ERROR_EOM will convert it to RV_EOM. * With the result of RV_EOM, content_stream_dump() will goto decision_more, which will call Media_mfile_end(...hiteom...) which will set cc_Media_begin_entry_state = BES_ENDEOM * Next we will go to the start of the dumping loop and call Media_mfile_begin(). It will notice the cc_Media_begin_entry_state equals BES_ENDEOM and will goto changemedia. * in changemedia, it does its stuff. However, if -F is used then it will not ask you to change. [Don't you just love the chain of calls....argh:-] Hmmmmm....wait a minute.... "write to machine:/dev/nrmt0h failed: 5" only gets produced by drive_simple. Arghhh!!!!!!! This means that drive_scsitape wasn't the chosen strategy ! Arghhh!!!!!!! This means that drive_scsitape.c/ds_match() scored badly. This means that rmtopen() or rmtioctl(fd, MTIOCGET, &mt_stat) failed. My bet, FOR SURE, is that rmtioctl(MTIOCGET) failed !!!!! Set the environment variable RMTDEBUG and watch the error messages. The rmtioctl code is in xfsdump/librmt/rmtioctl.c and is very UNIX specific. The "S" status command supported by rmt(1) varies quite a bit and there is special code in it for Linux and IRIX. For example, byte swapping may need to be done. If you want to use the scsitape strategy then the code in xfsdump/librmt/rmtioctl.c and rmtopen.c will have to be extended for Tru64. > Finally, just as a note, when dumping the IRIX machines, we normally use > the -m -b 245760 options, but these fail on the linux version with the > error: > > xfsdump: drive_minrmt.c:2201: do_end_write: Assertion `first_rec_w_err >= > 0' failed. > I'll have a look tomorrow - please redo with -v5. BTW, if one has probs with xfsdump/restore it's good to use "-v5" and send us all the msgs. Thanks. Hmmmm, I should have a look at producing some extra warning msgs for this case. Cheers, Tim. From owner-linux-xfs@oss.sgi.com Wed Jul 4 04:16:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64BGiJ12794 for linux-xfs-outgoing; Wed, 4 Jul 2001 04:16:44 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64BGQV12754 for ; Wed, 4 Jul 2001 04:16:26 -0700 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id CAA04536 for ; Wed, 4 Jul 2001 02:07:38 -0700 (PDT) mail_from (alciocca@ecetra.com) Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id LAA27228; Wed, 4 Jul 2001 11:07:28 +0200 Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.4/8.11.3) with ESMTP id f6497RU08217; Wed, 4 Jul 2001 11:07:27 +0200 Date: Wed, 4 Jul 2001 11:07:27 +0200 (CEST) From: Adam Cioccarelli To: Ric Tibbetts cc: Linux XFS Mailing List Subject: Re: XFS Size In-Reply-To: <3B424166.2020706@pipcws.ca.boeing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Ric, I have an XFS boot disk that I use for rescues, although I admit it has no scsi in the kernel. However it does have devfs and lvm compiled in... Regards, Adam On Tue, 3 Jul 2001, Ric Tibbetts wrote: > Are there an plans to reduce/optomize the compiles size of XFS so that > if you compile it into the kernel it will fit on a floppy? > I've run into resistance to using XFS because your only options for > rescue are to build a boot CD, or set up an initrc.img to boot from. > It would be far easier if an XFS enabled kernel would fit on a floppy. > > Thanks! > > Ric Tibbetts > From owner-linux-xfs@oss.sgi.com Wed Jul 4 04:19:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64BJej12979 for linux-xfs-outgoing; Wed, 4 Jul 2001 04:19:40 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64BJdV12970 for ; Wed, 4 Jul 2001 04:19:39 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id BAA09854 for ; Wed, 4 Jul 2001 01:42:53 -0700 (PDT) mail_from (juha@saarinen.org) Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15HiF8-00018n-00; Wed, 04 Jul 2001 20:42:42 +1200 Date: Wed, 4 Jul 2001 20:42:42 +1200 (NZST) From: Juha Saarinen To: Simon Matter cc: linux-xfs Subject: Re: Could IDE UDMA corruption be kgcc related? In-Reply-To: <3B42BC57.504A20FF@ch.sauter-bc.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 4 Jul 2001, Simon Matter wrote: > As I read on this list > XFS kernels can not be compiled with 2.96-85 because it breaks > something, could it be that egcs-2.91.66 breaks something else in the > RedHat Kernels. Possibly. I've got a stable system with gcc 2.96-88, however. Worth a try. I've abused it severely, with bonnies, tars, and fsstress. > Why then does RedHat use 2.96-85 for the kernel? Because it's a way to prepare for gcc 3.0 apparently, and the kernel does compile with it (some of the XFS code doesn't compile properly with -85, however). -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Wed Jul 4 04:34:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64BY5p13209 for linux-xfs-outgoing; Wed, 4 Jul 2001 04:34:05 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64BY3V13205 for ; Wed, 4 Jul 2001 04:34:04 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [144.253.131.5]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id TAA02401 for ; Tue, 3 Jul 2001 19:38:53 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id EAA923324 for ; Wed, 4 Jul 2001 04:37:31 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 MAA00990; Wed, 4 Jul 2001 12:36:13 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA89417; Wed, 4 Jul 2001 12:36:12 +1000 (EST) From: "Nathan Scott" Message-Id: <10107041236.ZM190543@wobbly.melbourne.sgi.com> Date: Wed, 4 Jul 2001 12:36:12 -0500 In-Reply-To: Roger Moore "Re: [patch] Re: Label based mounts with fsck" (Jul 3, 10:28am) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Roger Moore Subject: Re: [patch] Re: Label based mounts with fsck Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Jul 3, 10:28am, Roger Moore wrote: > Subject: Re: [patch] Re: Label based mounts with fsck > Great - thanks very much. I did upgrade to 1.22 and the patch worked > perfectly. We can now use labels to mount all our volumes which is very > useful for our SCSI machines! I can let you have the patched binary and > source RPMs if you are interested? > Not for me, thanks - but others may want them. I've just heard back from Ted & these changes will now be in the next version of e2fsprogs. Thanks for reporting the problem. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Jul 4 04:44:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64BiGH13415 for linux-xfs-outgoing; Wed, 4 Jul 2001 04:44:16 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64BiFV13412 for ; Wed, 4 Jul 2001 04:44:15 -0700 Received: from bakterius.eggenet.de (bakterius.eggenet.de [195.60.113.37]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id EAA04296 for ; Wed, 4 Jul 2001 04:03:14 -0700 (PDT) mail_from (s.koepfer@eggenet.com) Received: from koepfer (sven.eggenet.de [192.168.113.66]) by bakterius.eggenet.de (8.9.3/8.9.3) with ESMTP id MAA04479 for ; Wed, 4 Jul 2001 12:33:48 +0200 Message-Id: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> X-Sender: koepfer_firma@mail.eggenet.de X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Wed, 04 Jul 2001 11:04:04 +0000 To: linux-xfs@oss.sgi.com From: Sven Koepfer Subject: Kernel Version Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f64BiFV13413 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, i want to create an Linux Firewall with your XFS Filesystem for one of our customers. My Problem is the 2.4.3 Kernel Version. It is an firewall bug (ftp) in this Kernel Version that fixed in the 2.4.4 Version. What do you think about an patch for 2.4.4 or better 2.4.5 ???????? And how long must i wait ???? Thanks. Mit freundlichen Grüßen / Best regards / Muy Atentamente Sven Köpfer -------------------------------------------------------------- Sven Koepfer mailto:s.koepfer@eggenet.com Leiter IP-Systemtechnik http://www.eggenet.com EGGENET GmbH Tel: +49 (0)5251 8988-32 Rolandsweg 80 Fax: +49 (0)5251 8988-99 33102 Paderborn -------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 4 05:02:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64C2cK13815 for linux-xfs-outgoing; Wed, 4 Jul 2001 05:02:38 -0700 Received: from porgy.srv.nld.sonera.net (mbox-01.soneraplaza.nl [195.66.15.137]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64C2bV13812 for ; Wed, 4 Jul 2001 05:02:37 -0700 Received: from qn-212-58-163-110.quicknet.nl ([212.58.163.110]:61037 "EHLO auto-nb1.xs4all.nl") by soneramail.nl with ESMTP id ; Wed, 4 Jul 2001 14:02:47 +0200 Message-Id: <4.3.2.7.2.20010704140030.02e8c3d8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 04 Jul 2001 14:02:19 +0200 To: Ric Tibbetts , Linux XFS Mailing List From: Seth Mos Subject: Re: XFS Size In-Reply-To: <3B424166.2020706@pipcws.ca.boeing.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 15:04 3-7-2001 -0700, Ric Tibbetts wrote: >Are there an plans to reduce/optomize the compiles size of XFS so that if >you compile it into the kernel it will fit on a floppy? >I've run into resistance to using XFS because your only options for rescue >are to build a boot CD, or set up an initrc.img to boot from. >It would be far easier if an XFS enabled kernel would fit on a floppy. There is a link to a patch in the faq for mkbootdisk under redhat to make it format floppies larger. I use these larger floppy's myself to. YMMV. make sure to specify /dev/fd0u1680 so it gets formatted larger. >Thanks! > >Ric Tibbetts Good luck -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 4 05:11:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64CBVB14004 for linux-xfs-outgoing; Wed, 4 Jul 2001 05:11:31 -0700 Received: from main.braxis.co.uk (main.braxis.co.uk [213.77.40.29]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64CAeV13994 for ; Wed, 4 Jul 2001 05:10:40 -0700 Received: (from kszysiu@localhost) by main.braxis.co.uk (8.9.3/8.9.3) id OAA26893; Wed, 4 Jul 2001 14:07:40 +0200 Date: Wed, 4 Jul 2001 14:07:40 +0200 From: Krzysztof Rusocki To: Sven Koepfer Cc: linux-xfs@oss.sgi.com Subject: Re: Kernel Version Message-ID: <20010704140740.B16877@main.braxis.co.uk> References: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de>; from s.koepfer@eggenet.com on Wed, Jul 04, 2001 at 11:04:04AM +0000 X-MIME-Autoconverted: from 8bit to quoted-printable by main.braxis.co.uk id OAA26893 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f64CBVV14002 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 04, 2001 at 11:04:04AM +0000, Sven Koepfer wrote: Hi, CVS tree is currently based on 2.4.6-pre9 and as only Steve gets some time XFS will be merged with official 2.4.6 (for CVS instructions visit http://oss.sgi.com/projects/xfs/). You can also get patches at ftp://oss.sgi.com/projects/xfs/download/patches/ - actually I do not know status of any of these so the safest way would be grabbing CVS sources.... Seth, Steve - i think that it would be nice if some URL & info for patches would be put on XFS site... (if it is - sorry). Moreover it should be mentioned for which kernel version particular patch applies (linux-2.4.6-xfs-cvs-06212001.patch.gz applies to 2.4.6 ? seems strange for me since CVS is still -pre9 , or maybe i'm outta date here?) and if it contains cmd tree - AFAIK it does not.. so where do lie tarballed sources of cmd tree ? I think that putting such info and cleaning up that little mess would be good way of getting rid (didn't mean to be rude) of such posts... Cheers, Krzysztof > Hi, > > i want to create an Linux Firewall with your XFS Filesystem for one of our > customers. My Problem is the 2.4.3 Kernel Version. It is an firewall bug > (ftp) in this Kernel Version that fixed in the 2.4.4 Version. What do you > think about an patch for 2.4.4 or better 2.4.5 ???????? And how long must i > wait ???? > > Thanks. > > > Mit freundlichen Grüßen / Best regards / Muy Atentamente > > Sven Köpfer > > -------------------------------------------------------------- > Sven Koepfer mailto:s.koepfer@eggenet.com > Leiter IP-Systemtechnik http://www.eggenet.com > > EGGENET GmbH Tel: +49 (0)5251 8988-32 > Rolandsweg 80 Fax: +49 (0)5251 8988-99 > 33102 Paderborn > -------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 4 05:12:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64CCB714074 for linux-xfs-outgoing; Wed, 4 Jul 2001 05:12:11 -0700 Received: from zet.net (smtpout01.zet.net [195.189.9.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64CCAV14071 for ; Wed, 4 Jul 2001 05:12:10 -0700 Message-Id: <200107041212.f64CCAV14071@oss.sgi.com> Received: (COMMCENTER.MAIL 8071); 4 Jul 2001 12:12:02 -0000 Received: from (HELO sunray01) (193.218.126.167) by mail-cl19.cluster.zet.net with SMTP; 4 Jul 2001 12:12:02 -0000 From: Christian Gottschalch To: s.koepfer@eggenet.com Cc: linux-xfs@oss.sgi.com Subject: Re: Kernel Version In-Reply-To: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> Date: Wed, 04 Jul 2001 14:12:02 +0200 (MET DST) X-Mailer: XCmail 1.4devel (SunOS) X-Mailerorigin: http://www.js-home.org/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f64CCBV14072 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk reee ! ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/patches/ i know, i know, "testing" but works fine; if u plan to set up a FW, look also to http://www.getrewted.net/ nice security patch for linux, avalible for 2.4.5 ----------------------------------------------------------------- Christian Gottschalch ----/ / _ UNIX-Spezialist ---/ / (_)__ __ ____ __ --/ /__/ / _ \/ // /\ \/ / -/____/_/_//_/\_,_/ /_/\_\ -- ZET.NET AG -- Tel: +49 89 450652-35 Rosenheimer Staße 139 / 9th Floor Fax: +49 89 45098999069 81671 Munich email: gottschalch@zet.net Germany URL: www.zet.net ----------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 4 05:27:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64CR5v14443 for linux-xfs-outgoing; Wed, 4 Jul 2001 05:27:05 -0700 Received: from nevermore.toe.doomcom.org (IDENT:mail@dsl092-078-112.bos1.dsl.speakeasy.net [66.92.78.112]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64CR4V14440 for ; Wed, 4 Jul 2001 05:27:04 -0700 Received: by nevermore.toe.doomcom.org (Postfix, from userid 3499) id DD7D8206E8C; Tue, 3 Jul 2001 21:30:40 -0400 (EDT) Date: Tue, 3 Jul 2001 21:30:40 -0400 From: Gerald Britton To: linux-xfs@oss.sgi.com Subject: bug? Message-ID: <20010703213040.A15264@nevermore.toe.doomcom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Recently I shutdown by powerdown on a machine running kernel-2.4.2-SGI_XFS_1.0 on SMP. This was immediately after doing a "sync; sync; sync" ... shortly after the reboot and filesystems being mounted... No messages beyond this: Start mounting filesystem: ide1(22,3) Ending clean XFS mount for filesystem: ide1(22,3) ... I discovered that ".wgetrc" in my homedir nolonger contained what it used to. its contents were that of ".lessrc" I don't really have much more info beyond that, but I have seen this happen once or twice in the past as well. This machine was installed by simply using the installer for rh7.1. -- Gerald From owner-linux-xfs@oss.sgi.com Wed Jul 4 06:15:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f64DF2j15297 for linux-xfs-outgoing; Wed, 4 Jul 2001 06:15:02 -0700 Received: from mail.gmx.net (mail.gmx.de [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f64DF1V15284 for ; Wed, 4 Jul 2001 06:15:01 -0700 Received: (qmail 22831 invoked by uid 0); 4 Jul 2001 13:14:53 -0000 Received: from p3ee3c985.dip.t-dialin.net (HELO PowerBox.MysticWorld.de) (62.227.201.133) by mail.gmx.net (mp030-rz3) with SMTP; 4 Jul 2001 13:14:53 -0000 Received: from gmx.de (PowerBox.MysticWorld.de [192.168.1.1]) by PowerBox.MysticWorld.de (8.11.4/8.11.4) with ESMTP id f64DDul02647 for ; Wed, 4 Jul 2001 15:13:57 +0200 Message-ID: <3B431694.8040605@gmx.de> Date: Wed, 04 Jul 2001 15:13:56 +0200 From: Alexander Feigl User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010703 X-Accept-Language: de-de, en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: External log for rootfs possible? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViSperl10-milter (http://amavis.org/ Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello! Is it possible to have an external log (or a rt device) for the root filesystem? At boot kernel says I should put the log device in the mount command options but AFAIK there are no such options for the root fs. Alexander Feigl From owner-linux-xfs@oss.sgi.com Wed Jul 4 17:05:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6505Ja02210 for linux-xfs-outgoing; Wed, 4 Jul 2001 17:05:19 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6505IV02207 for ; Wed, 4 Jul 2001 17:05:18 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip34.idcomm.com [209.60.72.161]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f64KXTl07745 for ; Wed, 4 Jul 2001 14:33:30 -0600 Message-ID: <3B437D88.3B272793@idcomm.com> Date: Wed, 04 Jul 2001 14:33:12 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs Subject: Re: Could IDE UDMA corruption be kgcc related? References: <3B42BC57.504A20FF@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > > I was disturbing this list with my IDE UDMA corruption problem several > times now and I have another question about that. > > When I put heavy load on more than one IDE UDMA disk simultaneously, I > get filesystem corruption. This happens on several IDE / Motherboard > combinations. I have tried different kernels and until > 2.4.3-SGI_XFS_1.0.1_PR3 it was all the same. > > Now, could it be that we have to blame egcs-2.91.66 for this? That's why > I post to the XFS list because we are the people compiling the RH > kernels with egcs-2.91.66 instead of gcc-2.96-85. As I read on this list > XFS kernels can not be compiled with 2.96-85 because it breaks > something, could it be that egcs-2.91.66 breaks something else in the > RedHat Kernels. Why then does RedHat use 2.96-85 for the kernel? I personally have heard more about problems with people trying 2.96 than 2.91.66. From the kernel list, it seems unlikely that kgcc is at fault (that doesn't mean it can't be at fault). > > BTW unfortunately I don't have the failing systems available for more > test. I'm just trying to find what went wrong. > > Simon Probably someone has mentioned this already, I'm curious about what to use to check for bad blocks? Since fsck.xfs just returns, and I'm not sure if the blockmap in the man page for xfs_repair refers to the same thing as checking for bad blocks and marking them, what is the specifically recommended way to check for bad blocks on an XFS partition? Is the filesystem itself able to work around bad blocks (especially if the drive is degrading and new bad blocks are appearing)? If so, does it log a message to let the admin know of a degrading drive? D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Jul 4 17:31:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f650VDW02749 for linux-xfs-outgoing; Wed, 4 Jul 2001 17:31:13 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f650VCV02746 for ; Wed, 4 Jul 2001 17:31:12 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id OAA03906 for ; Wed, 4 Jul 2001 14:31:26 -0700 (PDT) mail_from (cattelan@thebarn.com) Received: from thebarn.com (nic-25-c96-156.mn.mediaone.net [24.25.96.156]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f64JLmNe047859; Wed, 4 Jul 2001 14:21:49 -0500 (CDT) Message-ID: <3B436CC7.69CD521B@thebarn.com> Date: Wed, 04 Jul 2001 14:21:43 -0500 From: Russell Cattelan X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Sven Koepfer CC: linux-xfs@oss.sgi.com Subject: Re: Kernel Version References: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by sgi.com id OAA03906 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f650VDV02747 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sven Koepfer wrote: > Hi, > > i want to create an Linux Firewall with your XFS Filesystem for one of our > customers. My Problem is the 2.4.3 Kernel Version. It is an firewall bug > (ftp) in this Kernel Version that fixed in the 2.4.4 Version. What do you > think about an patch for 2.4.4 or better 2.4.5 ???????? And how long must i > wait ???? > http://oss.sgi.com/projects/xfs/faq.html#xfspatches > > Thanks. > > Mit freundlichen Grüßen / Best regards / Muy Atentamente > > Sven Köpfer > > -------------------------------------------------------------- > Sven Koepfer mailto:s.koepfer@eggenet.com > Leiter IP-Systemtechnik http://www.eggenet.com > > EGGENET GmbH Tel: +49 (0)5251 8988-32 > Rolandsweg 80 Fax: +49 (0)5251 8988-99 > 33102 Paderborn > -------------------------------------------------------------- -- Russell Cattelan cattelan@thebarn.com From owner-linux-xfs@oss.sgi.com Wed Jul 4 17:32:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f650WM902848 for linux-xfs-outgoing; Wed, 4 Jul 2001 17:32:22 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f650WLV02845 for ; Wed, 4 Jul 2001 17:32:21 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [144.253.131.5]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id GAA01496 for ; Wed, 4 Jul 2001 06:55:56 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA967586 for ; Wed, 4 Jul 2001 15:55:52 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id GAA31311; Wed, 4 Jul 2001 06:55:18 -0700 (PDT) Message-ID: <3B431FA8.99E53484@sgi.com> Date: Wed, 04 Jul 2001 08:52:40 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Sven Koepfer CC: linux-xfs@oss.sgi.com Subject: Re: Kernel Version References: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sven Koepfer wrote: > What do you > think about an patch for 2.4.4 or better 2.4.5 ???????? I think it sounds like a good idea. > And how long must i > wait ???? Not long at all. ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/patches -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 4 17:50:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f650oXh03310 for linux-xfs-outgoing; Wed, 4 Jul 2001 17:50:33 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f650oWV03307 for ; Wed, 4 Jul 2001 17:50:32 -0700 Received: from dexter.esctelecom.com.br (dexter.esctelecom.com.br [200.206.107.5]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id LAA02750 for ; Wed, 4 Jul 2001 11:17:49 -0700 (PDT) mail_from (oluap@esctelecom.com.br) From: oluap@esctelecom.com.br Received: (from nobody@localhost) by dexter.esctelecom.com.br (8.11.3/8.11.3) id f64GC7L27148 for linux-xfs@oss.sgi.com; Wed, 4 Jul 2001 13:12:07 -0300 X-Authentication-Warning: dexter.esctelecom.com.br: nobody set sender to oluap@esctelecom.com.br using -f To: linux-xfs@oss.sgi.com Subject: Patch Message-ID: <994263127.3b434057c3d5c@www.esctelecom.com.br> Date: Wed, 04 Jul 2001 13:12:07 -0300 (BRT) MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit User-Agent: IMP/PHP IMAP webmail program 2.2.5 X-Originating-IP: 200.206.107.13 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk How can I patch official 2.4.6 kernel From owner-linux-xfs@oss.sgi.com Wed Jul 4 17:50:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f650oZk03343 for linux-xfs-outgoing; Wed, 4 Jul 2001 17:50:35 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f650oYV03332 for ; Wed, 4 Jul 2001 17:50:34 -0700 Received: from ledzep.americas.sgi.com (relay.sgi.com [137.38.226.97] (may be forged)) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA01279 for ; Wed, 4 Jul 2001 10:33:45 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA78117; Wed, 4 Jul 2001 12:32:28 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15HqVn-0000Up-00; Wed, 04 Jul 2001 12:32:27 -0500 Date: Wed, 4 Jul 2001 12:32:27 -0500 From: Nathan Straz To: Sven Koepfer Cc: linux-xfs@oss.sgi.com Subject: Re: Kernel Version Message-ID: <20010704123226.A1900@sgi.com> Mail-Followup-To: Sven Koepfer , linux-xfs@oss.sgi.com References: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 04, 2001 at 11:04:04AM +0000, Sven Koepfer wrote: > i want to create an Linux Firewall with your XFS Filesystem for one of our > customers. My Problem is the 2.4.3 Kernel Version. It is an firewall bug > (ftp) in this Kernel Version that fixed in the 2.4.4 Version. What do you > think about an patch for 2.4.4 or better 2.4.5 ???????? And how long must i > wait ???? You don't have to wait. You can use one of the prereleases. Take a look in ftp://oss.sgi.com/projects/xfs/download/testing/ at PR3. There is a 2.4.5 kernel based on Linus' tree. That kernel is pretty close to what the 1.0.1 release is going to be. -- 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 Jul 4 17:50:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f650ovP03510 for linux-xfs-outgoing; Wed, 4 Jul 2001 17:50:57 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f650oZV03342 for ; Wed, 4 Jul 2001 17:50:35 -0700 Received: from porgy.srv.nld.sonera.net (mbox-01.soneraplaza.nl [195.66.15.137]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA08559 for ; Wed, 4 Jul 2001 10:31:26 -0700 (PDT) mail_from (knuffie@xs4all.nl) Received: from qn-212-58-167-113.quicknet.nl ([212.58.167.113]:61177 "EHLO auto-nb1.xs4all.nl") by soneramail.nl with ESMTP id ; Wed, 4 Jul 2001 19:31:21 +0200 Message-Id: <4.3.2.7.2.20010704191705.00b60d08@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 04 Jul 2001 19:30:12 +0200 To: Krzysztof Rusocki , Sven Koepfer From: Seth Mos Subject: Re: Kernel Version Cc: linux-xfs@oss.sgi.com In-Reply-To: <20010704140740.B16877@main.braxis.co.uk> References: <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> <4.2.0.58.20010704092910.00ab8418@mail.eggenet.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:07 4-7-2001 +0200, Krzysztof Rusocki wrote: >On Wed, Jul 04, 2001 at 11:04:04AM +0000, Sven Koepfer wrote: > >Hi, > >CVS tree is currently based on 2.4.6-pre9 and as only Steve gets some time >XFS will be merged with official 2.4.6 (for CVS instructions visit >http://oss.sgi.com/projects/xfs/). This is also explained in the FAQ. I also added a link to the faq 2 weeks ago that points directly to the Makefile in CVS which has the kernel version number in it. >You can also get patches at ftp://oss.sgi.com/projects/xfs/download/patches/ >- actually I do not know status of any of these so the safest way would be >grabbing CVS sources.... These are made on a semi-regular basis when Steve has time. Sorry that I can't give you a better schedule about when these patches are made. >Seth, Steve - i think that it would be nice if some URL & info for patches >would be put on XFS site... (if it is - sorry). Moreover it should be Will add add a link for finding patches in the FAQ. >mentioned for which kernel version particular patch applies >(linux-2.4.6-xfs-cvs-06212001.patch.gz applies to 2.4.6 ? seems strange for pre patches are supposed to be patched against the lower version. eg 2.4.5. It's the same way it works with standard linux kernel patches. pre is relative to the lower version. >me since CVS is still -pre9 , or maybe i'm outta date here?) and if it If it is updated and you are on the list you will see the TAKE messages floating around. The moment they check it into their local repository it also get's pushed out. >contains cmd tree - AFAIK it does not.. so where do lie tarballed sources >of cmd tree ? This patch does not include the cmd tree and qa checks. This is to reduce the size of the patch that you need to download. The tarbals can be found on the FTP server in the testing and release directory's My ISP is currently having _serious_ problems with their backbone which results in latency times that are 10 times higher then normal. (20ms vs 200+ms) >I think that putting such info and cleaning up that little mess would be >good way of getting rid (didn't mean to be rude) of such posts... The more stuff we can filter out off the list means that Steve and his mery henchmen get more work done and the newer release out the door. >Cheers, >Krzysztof > > > Hi, > > > > i want to create an Linux Firewall with your XFS Filesystem for one of our > > customers. My Problem is the 2.4.3 Kernel Version. It is an firewall bug > > (ftp) in this Kernel Version that fixed in the 2.4.4 Version. What do you > > think about an patch for 2.4.4 or better 2.4.5 ???????? And how long > must i > > wait ???? Check out the CVS tree or download the rawhide RPMS those are 2.4.5 based and look a lot like standard redhat kernels. They are believed to be pretty well for everyday use. The newer 1.0.1-PR3 testing release also has newer and updated RPMS with 2.4.5 based kernels. Cheers and Good luck -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 4 18:26:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f651QL903921 for linux-xfs-outgoing; Wed, 4 Jul 2001 18:26:21 -0700 Received: from zet.net (smtpout01.zet.net [195.189.9.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f651QKV03918 for ; Wed, 4 Jul 2001 18:26:20 -0700 Message-Id: <200107050126.f651QKV03918@oss.sgi.com> Received: (COMMCENTER.MAIL 26521); 4 Jul 2001 14:19:32 -0000 Received: from (HELO sunray01) (193.218.126.167) by mail-cl18.cluster.zet.net with SMTP; 4 Jul 2001 14:19:32 -0000 From: Christian Gottschalch To: linux-xfs@oss.sgi.com Subject: strange output from df Date: Wed, 04 Jul 2001 16:19:31 +0200 (MET DST) X-Mailer: XCmail 1.4devel (SunOS) X-Mailerorigin: http://www.js-home.org/XCmail/ MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk i've run some checks on xfs: two x1 do the work over a mounted nfs Volume simultaneously creation test: 10000 fiels in 10000 Directorys copy these files to another directory move all to anotehr Directory delete all do it again Summary Datavolume ~ 40GB using an 2.4.5 kernel with xfsprogs-1.2.7.src.tar.gz and xfs patches: patch-xfs-1.0.1-only patch-2.4.5-bdev-ioctl patch-2.4.5-xfs-1.0.1-core so far, it works fine, now i stoped the scripts, deleted all manually from the working dirs, and now i got this output from "df" xfs Volume is mounted to /vol/xfs filer3:/vol # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda5 502M 81M 421M 16% / /dev/sda7 502M 384M 118M 77% /usr /dev/sda9 502M 50M 452M 10% /var /dev/sda2 102M 38M 64M 37% /boot /dev/sda11 5.3G 217M 5.0G 4% /daten /dev/sdb2 86G 108M 85G 1% /vol/xfs shmfs 305M 0 304M 0% /dev/shm filer3:/vol # cd xfs/ filer3:/vol/xfs > du -sh 8.0k . filer3:/vol/xfs > same result after a reboot, whats wrong ? From owner-linux-xfs@oss.sgi.com Wed Jul 4 18:40:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f651ecR04092 for linux-xfs-outgoing; Wed, 4 Jul 2001 18:40:38 -0700 Received: from smtp1.libero.it (smtp1.libero.it [193.70.192.51]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f651eaV04089 for ; Wed, 4 Jul 2001 18:40:36 -0700 Received: from libero.it (151.21.42.131) by smtp1.libero.it (5.5.025) id 3AE980E700F7AA2B for linux-xfs@oss.sgi.com; Wed, 4 Jul 2001 19:07:45 +0200 Message-ID: <3B434D4D.21FB2635@libero.it> Date: Wed, 04 Jul 2001 19:07:25 +0200 From: beevis@libero.it X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.5 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfs_fsr wierd bug? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello. I am running RH7.1 installed with the sgi boot disk. I am currently using kernel 2.4.5, compiled with kgcc. I have tried both patches for xfs 1.0 and 1.01, the same happens. I am using the latest rpm : xfsdump-1.0.5-0, xfsprogs-1.2.7-0. The problem: after trying to defrag a partition with xfs_fsr, /dev/hdc4 , and unmounting it, I am unable to remount it without rebooting. The same DOES NOT happen on other partitions, e.g. hdc2. To be more precise, I use as root: xfs_fsr v -t 200 /incoming and run it until I see the partition is not reorganised anymore. dmesg reports: xfs_unmount: xfs_ibusy says error/16 XFS unmount got error 16 linvfs_put_super: vfsp/0xc7f83a60 left dangling! VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... XFS: Filesystem has duplicate UUID - can't mount XFS: Filesystem has duplicate UUID - can't mount and so on, every attempt to remount the filesystem is useless. xfs_repair creates lost+found and puts in some files. One has to reboot, and afterwards everything is fine. I have tried to remount in several manners, with the same result (the usual: wrong filesystem, too many fs mounted et al.) I have tried this on other partitions and nothing wierd happens, I am able to remount it after reorganisation. Here is the relevant part of /etc/fstab /dev/hda2 / xfs defaults 1 1 /dev/hdc1 swap swap defaults 0 0 /dev/hda1 swap swap defaults 0 0 /dev/hdc2 /usr/local xfs exec,dev,suid,rw 1 1 /dev/hdc3 /home xfs exec,dev,suid,rw 1 1 /dev/hdc4 /incoming xfs exec,dev,suid,rw 1 1 LILO stanza: image=/boot/vmlinuz-2.4.5-xfs label=5 initrd=/boot/initrd-2.4.5-xfs.img read-only root=/dev/hda2 append="devfs=nomount,ramdisk_size=2500" I can reproduce easily the problem. The hardware is fine, no bad messages about a broken disk and so on. The hardware: AMD K6-III 450 MHz, MB Asus P5A, 128M , 2 hd hda: QUANTUM FIREBALL ST4.3A, ATA DISK drive hdc: QUANTUM FIREBALL EX6.4A, ATA DISK drive Thank you Nicola Fabiano From owner-linux-xfs@oss.sgi.com Wed Jul 4 19:26:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f652QIk04635 for linux-xfs-outgoing; Wed, 4 Jul 2001 19:26:18 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f652QHV04632 for ; Wed, 4 Jul 2001 19:26:17 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA06866 for ; Wed, 4 Jul 2001 19:23:34 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA03152; Thu, 5 Jul 2001 12:24:57 +1000 (EST) Date: Thu, 5 Jul 2001 12:24:56 +1000 From: Timothy Shimmin To: Ned Haubein Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump: problems spanning tapes (more info) Message-ID: <20010705122456.C1775@boing.melbourne.sgi.com> References: <20010704192223.B1775@boing.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010704192223.B1775@boing.melbourne.sgi.com>; from tes@boing.melbourne.sgi.com on Wed, Jul 04, 2001 at 07:22:23PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Ned, 'twas emailed: > > This means that drive_scsitape.c/ds_match() scored badly. > This means that > rmtopen() > or > rmtioctl(fd, MTIOCGET, &mt_stat) > failed. > > My bet, FOR SURE, is that rmtioctl(MTIOCGET) failed !!!!! > Set the environment variable RMTDEBUG > and watch the error messages. > The rmtioctl code is in xfsdump/librmt/rmtioctl.c > and is very UNIX specific. The "S" status command supported > by rmt(1) varies quite a bit and there is special code in it > for Linux and IRIX. For example, byte swapping may need > to be done. > If you want to use the scsitape strategy then the code in > xfsdump/librmt/rmtioctl.c and rmtopen.c will have to be > extended for Tru64. > > > Finally, just as a note, when dumping the IRIX machines, we normally use > > the -m -b 245760 options, but these fail on the linux version with the > > error: > > > > xfsdump: drive_minrmt.c:2201: do_end_write: Assertion `first_rec_w_err >= > > 0' failed. > > > I'll have a look tomorrow - please redo with -v5. > Looking at he assertion failure... If last write() succeeded then rval = 0, and first_rec_w_err = -1L; Then if mt_op(MTWEOF) failed then rval = DRIVE_ERROR_EOM. We would then have (first_rec_w_err == -1L && rval == DRIVE_ERROR_EOM) and the assertion would fire. My guess would be that mt_op(MTWEOF) failed. mt_op(MTWEOF) = rmtioctl(MTIOCTOP, MTWEOF) And for RMTHOST(filedes) == UNAME_UNKNOWN (in the case of Tru64, as it is not "Linux" or "IRIX") it does an rmt(1) command of "I" using the standard map of operations: #define STD_MTWEOF 0 /* write an end-of-file record */ #define STD_MTFSF 1 /* forward space file */ #define STD_MTBSF 2 /* backward space file */ #define STD_MTFSR 3 /* forward space record */ #define STD_MTBSR 4 /* backward space record */ #define STD_MTREW 5 /* rewind */ #define STD_MTOFFL 6 /* rewind and put the drive offline */ Check out /usr/include/sys/mtio.h and see what the values of the mt ops are for Tru64. On Linux MTWEOF is 5 and on IRIX MTWEOF is 0 and on an old HP box we have MTWEOF is 0, and on Linux, 0 is MTRESET, so you can see it is important to get the values right ! So again, one needs to update librmt/rmtopen.c and librmt/rmtioctl.c to add in a new host type for Tru64 and do all the necessary conversions and mappings. It's a real pain...but this is b/c no conventions were adopted for mt values. It would be good if a warning was generated for remote hosts which are not supported and trying to use the rmtioctl's. I'll look into this. --Tim From owner-linux-xfs@oss.sgi.com Wed Jul 4 19:29:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f652TM204759 for linux-xfs-outgoing; Wed, 4 Jul 2001 19:29:22 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f652TLV04756 for ; Wed, 4 Jul 2001 19:29:21 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA03486 for ; Wed, 4 Jul 2001 19:26:40 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id TAA31379; Wed, 4 Jul 2001 19:28:48 -0700 (PDT) Message-ID: <3B43D03F.DF17AD2@sgi.com> Date: Wed, 04 Jul 2001 21:26:07 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Christian Gottschalch CC: linux-xfs@oss.sgi.com Subject: Re: strange output from df References: <200107050126.f651QKV03918@oss.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Christian Gottschalch wrote: > creation test: 10000 fiels in 10000 Directorys > copy these files to another directory > move all to anotehr Directory > so far, it works fine, now i stoped the scripts, > deleted all manually from the working dirs, and now > i got this output from "df" > /dev/sdb2 86G 108M 85G 1% /vol/xfs > same result after a reboot, whats wrong ? I assume that the "strange" part of the output is that your "empty" filesystem shows 108M used? This is probably because XFS dynamically allocates inodes as it needs them, and you just created 40,000 inodes on your filesystem (10k files, 10k dirs, then copy). So what you are most likely seeing is the space allocated for inodes. XFS doesn't "reclaim" these inodes, so if you make 40,000 files, your filesystem now has 40,000 inodes permanently allocated. This isn't so bad, ext2 requires you to pre-allocate inodes, so on a filesystem where you wanted to use 40,000 files, you'd probably have to allocate 50,000 inodes to be safe. With XFS you get them as you need them, and no more. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 4 19:33:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f652XkP04888 for linux-xfs-outgoing; Wed, 4 Jul 2001 19:33:46 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f652XjV04884 for ; Wed, 4 Jul 2001 19:33:45 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA09904 for ; Wed, 4 Jul 2001 19:31:04 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id TAA66234; Wed, 4 Jul 2001 19:32:16 -0700 (PDT) Message-ID: <3B43D110.6CFCCF40@sgi.com> Date: Wed, 04 Jul 2001 21:29:36 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: oluap@esctelecom.com.br CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <994263127.3b434057c3d5c@www.esctelecom.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk oluap@esctelecom.com.br wrote: > > How can I patch official 2.4.6 kernel You'll have to wait, the CVS tree is at 2.4.6-pre9 currently, and the 2.4.6 merge is not trivial for XFS. The CVS tree will probably get to 2.4.6 (and 2.4.7-pre1) tomorrow, hopefully we can get a snapshot patch out for 2.4.6 in between the two. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 4 19:40:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f652e8C05048 for linux-xfs-outgoing; Wed, 4 Jul 2001 19:40:08 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f652e8V05045 for ; Wed, 4 Jul 2001 19:40:08 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA06864 for ; Wed, 4 Jul 2001 19:37:27 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id TAA61969; Wed, 4 Jul 2001 19:39:34 -0700 (PDT) Message-ID: <3B43D2C6.7AAAA585@sgi.com> Date: Wed, 04 Jul 2001 21:36:54 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs Subject: bad block (was: Could IDE UDMA corruption be kgcc related?) References: <3B42BC57.504A20FF@ch.sauter-bc.com> <3B437D88.3B272793@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > Probably someone has mentioned this already, I'm curious about what to > use to check for bad blocks? Since fsck.xfs just returns, and I'm not > sure if the blockmap in the man page for xfs_repair refers to the same > thing as checking for bad blocks and marking them, what is the > specifically recommended way to check for bad blocks on an XFS > partition? Is the filesystem itself able to work around bad blocks > (especially if the drive is degrading and new bad blocks are appearing)? > If so, does it log a message to let the admin know of a degrading drive? XFS doesn't have any bad-block tracking. See the archives for a couple discussions about this, but the consensus seems to be that drives are _always_ degrading, and bad blocks are _always_ appearing - it's just that the drive handles this internally, and rearranges things to protect the data. By the time the user actually sees bad blocks, the drive can no longer cope, and the game is pretty much over. Search for "ucsc-smartsuite" for a tool that will monitor the drive's coping ability, and warn the admin if things are getting too bad, hopefully before data is lost... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 4 20:58:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f653wW605927 for linux-xfs-outgoing; Wed, 4 Jul 2001 20:58:32 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f653wVV05924 for ; Wed, 4 Jul 2001 20:58:31 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id UAA12512 for ; Wed, 4 Jul 2001 20:58:22 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id NAA04684; Thu, 5 Jul 2001 13:58:26 +1000 Date: Thu, 5 Jul 2001 13:58:26 +1000 From: Keith Owens Message-Id: <200107050358.NAA04684@sherman.melbourne.sgi.com> Subject: TAKE - 2.4.6-pre9 to 2.4.6 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk 2.4.6-pre9 to 2.4.6 Date: Wed Jul 4 20:57:00 PDT 2001 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:98227a linux/mm/mmap.c - 1.38 linux/include/linux/pci.h - 1.46 linux/fs/proc/base.c - 1.27 linux/fs/namei.c - 1.32 linux/fs/ext2/ialloc.c - 1.16 linux/drivers/char/Config.in - 1.44 linux/Makefile - 1.97 linux/include/linux/pci_ids.h - 1.39 linux/drivers/pcmcia/yenta.c - 1.24 linux/drivers/sound/i810_audio.c - 1.12 linux/drivers/mtd/nand/spia.c - 1.2 linux/drivers/mtd/nand/Config.in - 1.2 From owner-linux-xfs@oss.sgi.com Wed Jul 4 22:16:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f655GxW07141 for linux-xfs-outgoing; Wed, 4 Jul 2001 22:16:59 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f655GvV07138 for ; Wed, 4 Jul 2001 22:16:57 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id HAA995004 for ; Thu, 5 Jul 2001 07:16:55 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id WAA76967 for ; Wed, 4 Jul 2001 22:16:22 -0700 (PDT) Message-ID: <3B43F785.DAE8277A@sgi.com> Date: Thu, 05 Jul 2001 00:13:41 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: 2.4.6 patch available Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk There is a 2.4.6 patch available in the patches/ directory of the ftp site, get the one dated July 5, linux-2.4.6-xfs-07052001.patch.bz2 Note that this is a SNAPSHOT of the DEVELOPMENT tree, and does not represent a stable code release. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 4 22:32:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f655WkM07328 for linux-xfs-outgoing; Wed, 4 Jul 2001 22:32:46 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f655WhV07325 for ; Wed, 4 Jul 2001 22:32:43 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA17892 for ; Wed, 4 Jul 2001 22:32:34 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id PAA01733 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 15:32:40 +1000 Date: Thu, 5 Jul 2001 15:32:40 +1000 From: Keith Owens Message-Id: <200107050532.PAA01733@sherman.melbourne.sgi.com> Subject: TAKE - 2.4.6 to 2.4.7-pre1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Note: This checkin compiles but has not been tested. It is just syncing up with Linus "I can issue patches faster than you can" Torvalds. Date: Wed Jul 4 22:29:17 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs-2.4.7-pre1 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98229a linux/include/asm-mips64/gcc/sgidefs.h - 1.1 linux/Documentation/README.nsp_cs.eng - 1.1 linux/drivers/net/irda/ali-ircc.c - 1.1 linux/drivers/net/sk98lin/h/skversion.h - 1.1 linux/drivers/net/sk98lin/skproc.c - 1.1 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.1 linux/drivers/scsi/pcmcia/nsp_cs.h - 1.1 linux/drivers/scsi/pcmcia/nsp_debug.c - 1.1 linux/drivers/scsi/pcmcia/nsp_io.h - 1.1 linux/arch/mips64/arc/arc_con.c - 1.1 linux/arch/mips/mm/sb1.c - 1.1 linux/arch/mips/mm/rm7k.c - 1.1 linux/arch/mips/mm/r5432.c - 1.1 linux/arch/mips/mm/mips32.c - 1.1 linux/arch/mips/mm/ioremap.c - 1.1 linux/include/asm-mips64/rrm.h - 1.1 linux/include/asm-s390/pci.h - 1.1 linux/include/net/irda/ali-ircc.h - 1.1 linux/arch/cris/kernel/entryoffsets.c - 1.1 linux/arch/cris/drivers/lpslave/Makefile - 1.1 linux/arch/cris/drivers/lpslave/bintocarr.pl - 1.1 linux/arch/cris/drivers/lpslave/e100lpslave.README - 1.1 linux/arch/cris/drivers/lpslave/e100lpslave.S - 1.1 linux/arch/cris/drivers/lpslave/e100lpslave.h - 1.1 linux/arch/cris/drivers/lpslave/e100lpslaveld - 1.1 linux/arch/cris/drivers/lpslave/e100lpslavenet.c - 1.1 linux/net/sunrpc/svcsock.c - 1.15 linux/net/irda/qos.c - 1.12 linux/net/irda/irttp.c - 1.14 linux/net/irda/irsysctl.c - 1.5 linux/net/irda/irqueue.c - 1.8 linux/net/irda/irproc.c - 1.10 linux/net/irda/irlmp_event.c - 1.10 linux/net/irda/irlmp.c - 1.12 linux/net/irda/irlap_frame.c - 1.13 linux/net/irda/irlap_event.c - 1.14 linux/net/irda/irlap_comp.c - 1.6 linux/net/irda/irlap.c - 1.12 linux/net/irda/irlan/irlan_common.c - 1.15 linux/net/irda/irias_object.c - 1.9 linux/net/irda/compressors/irda_deflate.c - 1.7 linux/net/irda/compressors/Makefile - 1.5 linux/net/irda/compressors/Config.in - 1.4 linux/net/irda/af_irda.c - 1.21 linux/net/irda/Makefile - 1.7 linux/mm/swapfile.c - 1.33 linux/kernel/sys.c - 1.21 linux/include/net/irda/qos.h - 1.8 linux/include/net/irda/irlap_comp.h - 1.3 linux/include/net/irda/irlap.h - 1.11 linux/include/linux/hdreg.h - 1.13 linux/include/linux/apm_bios.h - 1.10 linux/drivers/video/imsttfb.c - 1.14 linux/drivers/video/fbcon.c - 1.19 linux/drivers/sound/sb_common.c - 1.18 linux/drivers/sound/dev_table.h - 1.14 linux/drivers/sound/ad1848.c - 1.11 linux/drivers/sound/Config.in - 1.25 linux/drivers/scsi/ultrastor.c - 1.8 linux/drivers/scsi/sr_ioctl.c - 1.15 linux/drivers/scsi/megaraid.h - 1.10 linux/drivers/scsi/megaraid.c - 1.23 linux/drivers/scsi/hosts.c - 1.24 linux/drivers/pci/pci.c - 1.40 linux/drivers/net/sk_g16.c - 1.13 linux/drivers/net/rrunner.c - 1.16 linux/drivers/net/ppp_deflate.c - 1.5 linux/drivers/net/irda/irtty.c - 1.21 linux/drivers/net/irda/irport.c - 1.20 linux/drivers/net/irda/Makefile - 1.13 linux/drivers/net/irda/Config.in - 1.10 linux/drivers/cdrom/mcd.c - 1.10 linux/arch/ppc/kernel/pmac_pci.c - 1.15 linux/arch/mips/mm/umap.c - 1.7 linux/arch/mips/mm/r4xx0.c - 1.8 linux/arch/mips/mm/r2300.c - 1.9 linux/arch/mips/mm/loadmmu.c - 1.8 linux/arch/mips/mm/init.c - 1.12 linux/arch/mips/mm/fault.c - 1.11 linux/arch/mips/mm/extable.c - 1.4 linux/arch/mips/mm/andes.c - 1.8 linux/arch/alpha/kernel/traps.c - 1.12 linux/arch/alpha/kernel/time.c - 1.16 linux/Makefile - 1.98 linux/Documentation/networking/multicast.txt - 1.4 linux/CREDITS - 1.57 linux/net/decnet/sysctl_net_decnet.c - 1.10 linux/drivers/video/cyber2000fb.c - 1.22 linux/drivers/net/sk_mca.c - 1.12 linux/drivers/net/irda/toshoboe.c - 1.23 linux/drivers/net/irda/smc-ircc.c - 1.19 linux/Documentation/sound/CMI8338 - 1.4 linux/drivers/net/ppp_generic.c - 1.21 linux/drivers/net/ppp_async.c - 1.13 linux/net/atm/proc.c - 1.13 linux/net/atm/mpoa_proc.c - 1.8 linux/drivers/sound/maestro.c - 1.22 linux/net/irda/ircomm/ircomm_tty_ioctl.c - 1.6 linux/drivers/net/sun3lance.c - 1.9 linux/drivers/sound/nm256_audio.c - 1.12 linux/drivers/net/wan/Config.in - 1.11 linux/drivers/net/tokenring/ibmtr.c - 1.14 linux/drivers/video/tdfxfb.c - 1.10 linux/drivers/net/ppp_synctty.c - 1.9 linux/drivers/net/sk98lin/skxmac2.c - 1.4 linux/drivers/net/sk98lin/h/skgehwt.h - 1.3 linux/drivers/net/sk98lin/skgepnmi.c - 1.4 linux/drivers/net/sk98lin/h/skgeinit.h - 1.3 linux/drivers/net/sk98lin/skgesirq.c - 1.4 linux/drivers/net/sk98lin/Makefile - 1.4 linux/drivers/net/sk98lin/h/lm80.h - 1.4 linux/drivers/net/sk98lin/h/skaddr.h - 1.3 linux/drivers/net/sk98lin/h/skcsum.h - 1.3 linux/drivers/net/sk98lin/h/skdrv1st.h - 1.4 linux/drivers/net/sk98lin/h/skdrv2nd.h - 1.3 linux/drivers/net/sk98lin/skvpd.c - 1.4 linux/drivers/net/sk98lin/sktimer.c - 1.3 linux/drivers/net/sk98lin/skrlmt.c - 1.3 linux/drivers/net/sk98lin/h/skgehw.h - 1.4 linux/drivers/net/sk98lin/skgeinit.c - 1.4 linux/drivers/net/sk98lin/skge.c - 1.11 linux/drivers/net/sk98lin/skgehwt.c - 1.3 linux/drivers/net/sk98lin/h/skgepnm2.h - 1.3 linux/drivers/net/sk98lin/h/skgepnmi.h - 1.3 linux/drivers/net/sk98lin/h/skgesirq.h - 1.3 linux/drivers/net/sk98lin/skqueue.c - 1.4 linux/drivers/net/sk98lin/h/ski2c.h - 1.3 linux/drivers/net/sk98lin/h/skqueue.h - 1.3 linux/drivers/net/sk98lin/ski2c.c - 1.4 linux/drivers/net/sk98lin/h/skrlmt.h - 1.3 linux/drivers/net/sk98lin/h/sktimer.h - 1.3 linux/drivers/net/sk98lin/h/skvpd.h - 1.3 linux/drivers/net/sk98lin/h/xmac_ii.h - 1.4 linux/drivers/net/sk98lin/skaddr.c - 1.3 linux/drivers/net/sk98lin/skcsum.c - 1.3 linux/drivers/net/irda/nsc-ircc.c - 1.14 linux/drivers/scsi/pcmcia/Config.in - 1.3 linux/drivers/scsi/pcmcia/Makefile - 1.5 linux/drivers/net/skfp/ess.c - 1.3 linux/include/asm-mips64/ioctl.h - 1.3 linux/include/asm-mips64/io.h - 1.5 linux/include/asm-mips64/ide.h - 1.5 linux/include/asm-mips64/hdreg.h - 1.3 linux/include/asm-mips64/elf.h - 1.6 linux/include/asm-mips64/delay.h - 1.6 linux/include/asm-mips64/cpu.h - 1.3 linux/include/asm-mips64/checksum.h - 1.3 linux/include/asm-mips64/cache.h - 1.3 linux/include/asm-mips64/bootinfo.h - 1.4 linux/include/asm-mips64/bitops.h - 1.5 linux/include/asm-mips64/atomic.h - 1.5 linux/include/asm-mips64/irq.h - 1.5 linux/include/asm-mips64/siginfo.h - 1.4 linux/include/asm-mips64/sgiarcs.h - 1.3 linux/include/asm-mips64/sgialib.h - 1.3 linux/include/asm-mips64/sgi/sgint23.h - 1.4 linux/include/asm-mips64/semaphore.h - 1.5 linux/include/asm-mips64/semaphore-helper.h - 1.4 linux/include/asm-mips64/unaligned.h - 1.4 linux/include/asm-mips64/processor.h - 1.9 linux/include/asm-mips64/pgtable.h - 1.8 linux/include/asm-mips64/pgalloc.h - 1.7 linux/include/asm-mips64/pci.h - 1.6 linux/include/asm-mips64/termios.h - 1.5 linux/include/asm-mips64/system.h - 1.5 linux/include/asm-mips64/socket.h - 1.7 linux/include/asm-mips64/sn/types.h - 1.4 linux/include/asm-mips64/ioctls.h - 1.3 linux/include/asm-mips64/mipsregs.h - 1.6 linux/arch/mips64/defconfig - 1.14 linux/arch/mips64/arc/cmdline.c - 1.3 linux/arch/mips64/arc/console.c - 1.4 linux/arch/mips64/mm/umap.c - 1.5 linux/arch/mips64/arc/identify.c - 1.4 linux/arch/mips64/arc/memory.c - 1.5 linux/arch/mips64/mm/init.c - 1.6 linux/arch/mips64/mm/fault.c - 1.7 linux/arch/mips64/mm/extable.c - 1.3 linux/arch/mips64/lib/watch.S - 1.3 linux/arch/mips64/lib/rtc-std.c - 1.4 linux/arch/mips64/lib/memcpy.S - 1.4 linux/arch/mips64/lib/memset.S - 1.4 linux/arch/mips64/lib/rtc-no.c - 1.4 linux/arch/mips64/mm/andes.c - 1.6 linux/arch/mips64/kernel/traps.c - 1.5 linux/arch/mips64/kernel/unaligned.c - 1.4 linux/arch/mips64/arc/tree.c - 1.3 linux/arch/mips64/config.in - 1.14 linux/arch/mips64/defconfig-ip22 - 1.9 linux/arch/mips64/kernel/binfmt_elf32.c - 1.5 linux/arch/mips64/kernel/scall_o32.S - 1.6 linux/arch/mips64/Makefile - 1.7 linux/arch/mips64/arc/Makefile - 1.5 linux/arch/mips64/mm/r4xx0.c - 1.7 linux/arch/mips64/arc/printf.c - 1.4 linux/arch/mips64/kernel/setup.c - 1.6 linux/arch/mips64/kernel/linux32.c - 1.9 linux/arch/mips64/kernel/scall_64.S - 1.8 linux/arch/mips64/defconfig-ip27 - 1.8 linux/arch/mips64/kernel/branch.c - 1.3 linux/arch/mips64/kernel/entry.S - 1.5 linux/arch/mips64/kernel/head.S - 1.4 linux/arch/mips64/kernel/mips64_ksyms.c - 1.6 linux/arch/mips64/kernel/proc.c - 1.4 linux/arch/mips64/kernel/r4k_fpu.S - 1.3 linux/drivers/net/pcmcia/ibmtr_cs.c - 1.6 linux/include/linux/ibmtr.h - 1.3 linux/drivers/net/pppoe.c - 1.13 linux/include/asm-s390/ebcdic.h - 1.4 linux/arch/s390/kernel/entry.S - 1.9 linux/arch/s390/kernel/head.S - 1.4 linux/arch/s390/kernel/irq.c - 1.6 linux/include/asm-s390/bitops.h - 1.5 linux/arch/s390/kernel/reipl.S - 1.3 linux/arch/s390/kernel/smp.c - 1.6 linux/arch/mips64/kernel/smp.c - 1.7 linux/arch/mips64/kernel/ioctl32.c - 1.6 linux/include/asm-mips64/smp.h - 1.4 linux/fs/jffs/jffs_fm.c - 1.4 linux/arch/mips64/kernel/r4k_tlb.S - 1.2 linux/net/irda/irsyms.c - 1.2 linux/drivers/sound/ymfpci.h - 1.4 linux/drivers/sound/ymfpci.c - 1.8 linux/arch/s390x/kernel/smp.c - 1.3 linux/include/asm-s390x/irq.h - 1.3 linux/include/asm-s390x/ebcdic.h - 1.3 linux/arch/s390x/kernel/reipl.S - 1.2 linux/include/asm-s390x/byteorder.h - 1.2 linux/include/asm-s390x/bitops.h - 1.2 linux/arch/s390x/kernel/linux32.c - 1.4 linux/arch/s390x/kernel/irq.c - 1.3 linux/arch/s390x/kernel/head.S - 1.3 linux/arch/cris/Makefile - 1.4 linux/arch/cris/config.in - 1.4 linux/arch/cris/defconfig - 1.5 linux/arch/cris/drivers/Config.in - 1.4 linux/arch/cris/drivers/Makefile - 1.4 linux/arch/cris/drivers/axisflashmap.c - 1.4 linux/arch/cris/drivers/ethernet.c - 1.4 linux/arch/cris/drivers/ide.c - 1.4 linux/arch/cris/drivers/serial.c - 1.5 linux/arch/cris/kernel/Makefile - 1.3 linux/arch/cris/kernel/entry.S - 1.5 linux/arch/cris/kernel/head.S - 1.4 linux/arch/cris/kernel/irq.c - 1.4 linux/arch/cris/kernel/process.c - 1.4 linux/arch/cris/kernel/setup.c - 1.4 linux/arch/cris/kernel/signal.c - 1.4 linux/arch/cris/kernel/time.c - 1.2 linux/arch/cris/lib/checksum.S - 1.3 linux/arch/cris/lib/checksumcopy.S - 1.3 linux/arch/cris/lib/usercopy.c - 1.2 linux/arch/cris/mm/fault.c - 1.5 linux/arch/cris/mm/init.c - 1.4 linux/arch/cris/mm/tlb.c - 1.3 linux/drivers/s390/s390io.c - 1.3 linux/arch/s390x/kernel/entry.S - 1.4 linux/arch/s390x/mm/fault.c - 1.3 linux/include/asm-s390x/string.h - 1.2 linux/include/asm-cris/svinto.h - 1.2 linux/include/asm-cris/axisflashmap.h - 1.3 linux/include/asm-cris/bitops.h - 1.3 linux/include/asm-cris/delay.h - 1.3 linux/include/asm-cris/dma.h - 1.2 linux/include/asm-cris/ptrace.h - 1.4 linux/include/asm-cris/mmu_context.h - 1.2 linux/include/asm-cris/irq.h - 1.4 linux/include/asm-cris/io.h - 1.4 linux/drivers/video/maxinefb.c - 1.2 linux/include/asm-cris/etraxgpio.h - 1.3 linux/arch/cris/drivers/gpio.c - 1.3 linux/arch/cris/drivers/usb-host.c - 1.3 linux/arch/cris/lib/dram_init.S - 1.3 linux/Documentation/usb/philips.txt - 1.2 linux/arch/cris/drivers/ds1302.c - 1.2 linux/arch/cris/drivers/eeprom.c - 1.2 linux/arch/cris/drivers/parport.c - 1.2 linux/arch/cris/lib/hw_settings.S - 1.2 From owner-linux-xfs@oss.sgi.com Wed Jul 4 22:36:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f655anH07473 for linux-xfs-outgoing; Wed, 4 Jul 2001 22:36:49 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f655amV07470 for ; Wed, 4 Jul 2001 22:36:48 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id HAA21817; Thu, 5 Jul 2001 07:36:46 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id HAA25097; Thu, 5 Jul 2001 07:36:46 +0200 (CEST) Date: Thu, 5 Jul 2001 07:36:46 +0200 (CEST) From: Seth Mos To: Christian Gottschalch cc: linux-xfs@oss.sgi.com Subject: Re: strange output from df In-Reply-To: <200107050126.f651QKV03918@oss.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 4 Jul 2001, Christian Gottschalch wrote: > i've run some checks on xfs: > two x1 do the work over a mounted nfs Volume simultaneously > creation test: 10000 fiels in 10000 Directorys > copy these files to another directory > move all to anotehr Directory > delete all > do it again > Summary Datavolume ~ 40GB > > using an 2.4.5 kernel with xfsprogs-1.2.7.src.tar.gz and xfs patches: > > patch-xfs-1.0.1-only > patch-2.4.5-bdev-ioctl > patch-2.4.5-xfs-1.0.1-core > > so far, it works fine, now i stoped the scripts, > deleted all manually from the working dirs, and now > i got this output from "df" > > xfs Volume is mounted to /vol/xfs > filer3:/vol # df -h > Filesystem Size Used Avail Use% Mounted on > /dev/sda5 502M 81M 421M 16% / > /dev/sda7 502M 384M 118M 77% /usr > /dev/sda9 502M 50M 452M 10% /var > /dev/sda2 102M 38M 64M 37% /boot > /dev/sda11 5.3G 217M 5.0G 4% /daten > /dev/sdb2 86G 108M 85G 1% /vol/xfs > shmfs 305M 0 304M 0% /dev/shm > filer3:/vol # cd xfs/ > filer3:/vol/xfs > du -sh > 8.0k . > filer3:/vol/xfs > > > same result after a reboot, whats wrong ? Nothing is wrong. XFS allocates indoes when needed, once used you don't get the space back. On the other hand with ext2 you allocate the same amount of space when you format the partion Cheer Seth From owner-linux-xfs@oss.sgi.com Wed Jul 4 22:38:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f655cek07576 for linux-xfs-outgoing; Wed, 4 Jul 2001 22:38:40 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f655cdV07572 for ; Wed, 4 Jul 2001 22:38:39 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id HAA22243; Thu, 5 Jul 2001 07:38:37 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id HAA25150; Thu, 5 Jul 2001 07:38:37 +0200 (CEST) Date: Thu, 5 Jul 2001 07:38:37 +0200 (CEST) From: Seth Mos To: oluap@esctelecom.com.br cc: linux-xfs@oss.sgi.com Subject: Re: Patch In-Reply-To: <994263127.3b434057c3d5c@www.esctelecom.com.br> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 4 Jul 2001 oluap@esctelecom.com.br wrote: > How can I patch official 2.4.6 kernel > CVS is -pre9 based but I think 2.4.6 should be forthcoming soon. It will take a few days. Cheers Seth From owner-linux-xfs@oss.sgi.com Wed Jul 4 22:44:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f655imm07722 for linux-xfs-outgoing; Wed, 4 Jul 2001 22:44:48 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f655imV07719 for ; Wed, 4 Jul 2001 22:44:48 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id WAA09024 for ; Wed, 4 Jul 2001 22:42:06 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 PAA09032; Thu, 5 Jul 2001 15:43:25 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Seth Mos cc: oluap@esctelecom.com.br, linux-xfs@oss.sgi.com Subject: Re: Patch In-reply-to: Your message of "Thu, 05 Jul 2001 07:38:37 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Jul 2001 15:43:25 +1000 Message-ID: <29784.994311805@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 5 Jul 2001 07:38:37 +0200 (CEST), Seth Mos wrote: >On Wed, 4 Jul 2001 oluap@esctelecom.com.br wrote: > >> How can I patch official 2.4.6 kernel > >CVS is -pre9 based but I think 2.4.6 should be forthcoming soon. >It will take a few days. CVS was 2.4.6 for about 2 hours, it is now 2.4.7-pre1 and heading for 2.4.7-pre2 very soon. From owner-linux-xfs@oss.sgi.com Wed Jul 4 23:15:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f656FOO08205 for linux-xfs-outgoing; Wed, 4 Jul 2001 23:15:24 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f656FLV08202 for ; Wed, 4 Jul 2001 23:15:21 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id XAA09862 for ; Wed, 4 Jul 2001 23:15:19 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id QAA08761 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 16:15:16 +1000 Date: Thu, 5 Jul 2001 16:15:16 +1000 From: Keith Owens Message-Id: <200107050615.QAA08761@sherman.melbourne.sgi.com> Subject: TAKE - 2.4.7-pre1 to 2.4.7-pre2 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Note: This checkin compiles but has not been tested. It is just syncing up with Linus "I can issue patches faster than you can" Torvalds. Date: Wed Jul 4 23:13:42 PDT 2001 Workarea: sherman.melbourne.sgi.com:/build/kaos/2.4.x-xfs-2.4.7-pre2 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98230a linux/drivers/media/video/zoran.h - 1.1 linux/Documentation/sonypi.txt - 1.1 linux/Documentation/video4linux/Zoran - 1.1 linux/Documentation/video4linux/meye.txt - 1.1 linux/Documentation/video4linux/w9966.txt - 1.1 linux/include/linux/meye.h - 1.1 linux/drivers/char/sonypi.h - 1.1 linux/drivers/media/video/meye.h - 1.1 linux/drivers/media/video/meye.c - 1.1 linux/drivers/media/video/zoran_procfs.c - 1.1 linux/drivers/media/video/zr36067.c - 1.1 linux/drivers/net/au1000_eth.c - 1.1 linux/drivers/usb/usb-skeleton.c - 1.1 linux/drivers/net/au1000_eth.h - 1.1 linux/drivers/char/ser_a2232.c - 1.1 linux/drivers/net/lp486e.c - 1.1 linux/drivers/char/ser_a2232.h - 1.1 linux/include/linux/sonypi.h - 1.1 linux/drivers/char/ser_a2232fw.ax - 1.1 linux/drivers/char/ser_a2232fw.h - 1.1 linux/drivers/char/sonypi.c - 1.1 linux/drivers/char/w83877f_wdt.c - 1.1 linux/init/main.c - 1.56 linux/include/scsi/sg.h - 1.10 linux/include/linux/videodev.h - 1.16 linux/include/linux/tty.h - 1.16 linux/include/linux/timex.h - 1.4 linux/include/linux/swap.h - 1.30 linux/include/linux/proc_fs.h - 1.30 linux/include/linux/pci.h - 1.47 linux/include/linux/nls.h - 1.6 linux/include/asm-i386/processor.h - 1.23 linux/include/asm-arm/softirq.h - 1.5 linux/include/asm-arm/hardirq.h - 1.8 linux/include/asm-arm/arch-ebsa285/io.h - 1.11 linux/fs/locks.c - 1.17 linux/drivers/video/tgafb.c - 1.14 linux/drivers/usb/usb.c - 1.51 linux/drivers/usb/uhci.c - 1.45 linux/drivers/scsi/sg.c - 1.19 linux/drivers/scsi/Config.in - 1.21 linux/drivers/net/eth16i.c - 1.18 linux/drivers/net/eql.c - 1.13 linux/drivers/net/acenic.c - 1.28 linux/drivers/char/h8.c - 1.10 linux/drivers/char/dtlk.c - 1.13 linux/drivers/char/Makefile - 1.45 linux/drivers/char/Config.in - 1.45 linux/drivers/block/rd.c - 1.29 linux/drivers/block/ll_rw_blk.c - 1.70 linux/arch/i386/math-emu/reg_u_div.S - 1.5 linux/arch/i386/kernel/signal.c - 1.17 linux/arch/i386/kernel/setup.c - 1.47 linux/arch/i386/kernel/process.c - 1.32 linux/arch/arm/kernel/sys_arm.c - 1.18 linux/arch/arm/kernel/oldlatches.c - 1.8 linux/arch/arm/kernel/irq.c - 1.13 linux/arch/arm/kernel/head-armv.S - 1.15 linux/arch/arm/kernel/dma-arc.c - 1.10 linux/arch/arm/kernel/dec21285.c - 1.15 linux/Makefile - 1.99 linux/CREDITS - 1.58 linux/drivers/usb/acm.c - 1.39 linux/drivers/char/dz.c - 1.11 linux/drivers/net/arlan.c - 1.17 linux/drivers/char/sx.c - 1.19 linux/drivers/char/generic_serial.c - 1.11 linux/drivers/pnp/isapnp.c - 1.21 linux/drivers/char/ip2/i2cmd.c - 1.3 linux/arch/arm/kernel/bios32.c - 1.22 linux/include/linux/spinlock.h - 1.9 linux/drivers/net/dmfe.c - 1.18 linux/drivers/net/setup.c - 1.19 linux/drivers/pcmcia/yenta.c - 1.25 linux/drivers/usb/devices.c - 1.11 linux/drivers/usb/inode.c - 1.14 linux/drivers/char/moxa.c - 1.6 linux/drivers/net/ioc3-eth.c - 1.12 linux/include/asm-mips64/ioctls.h - 1.4 linux/include/linux/usb.h - 1.16 linux/drivers/ide/ide-tape.c - 1.12 linux/drivers/usb/mdc800.c - 1.11 linux/arch/i386/kernel/pci-irq.c - 1.16 linux/include/linux/usbdevice_fs.h - 1.5 linux/drivers/char/rio/riotty.c - 1.5 linux/drivers/char/rio/riotable.c - 1.4 linux/drivers/char/rio/linux_compat.h - 1.4 linux/drivers/char/rio/rioinit.c - 1.5 linux/drivers/char/rio/riodrvr.h - 1.2 linux/drivers/char/rio/riocmd.c - 1.5 linux/drivers/char/rio/rioboot.c - 1.5 linux/drivers/char/rio/rio_linux.h - 1.4 linux/drivers/char/rio/rio_linux.c - 1.9 linux/include/asm-arm/mach/pci.h - 1.3 linux/drivers/usb/storage/freecom.c - 1.5 linux/drivers/media/video/zr36060.h - 1.2 linux/drivers/media/video/zr36057.h - 1.2 linux/drivers/media/video/saa5249.c - 1.4 linux/drivers/media/video/buz.h - 1.2 linux/drivers/media/video/buz.c - 1.6 linux/drivers/media/video/Makefile - 1.4 linux/drivers/media/video/Config.in - 1.3 linux/arch/arm/tools/mach-types - 1.6 linux/arch/arm/mach-footbridge/personal-pci.c - 1.2 linux/arch/arm/mach-footbridge/netwinder-pci.c - 1.2 linux/arch/arm/mach-footbridge/ebsa285-pci.c - 1.2 linux/arch/arm/mach-footbridge/cats-pci.c - 1.2 linux/arch/arm/kernel/plx90x0.c - 1.2 linux/arch/i386/kernel/dmi_scan.c - 1.4 linux/drivers/scsi/osst.h - 1.3 linux/drivers/scsi/osst.c - 1.5 linux/include/asm-arm/arch-integrator/io.h - 1.2 linux/drivers/char/machzwd.c - 1.4 From owner-linux-xfs@oss.sgi.com Wed Jul 4 23:22:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f656Mps08498 for linux-xfs-outgoing; Wed, 4 Jul 2001 23:22:51 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f656MnV08495 for ; Wed, 4 Jul 2001 23:22:49 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA27622; Thu, 5 Jul 2001 08:22:48 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id IAA28090; Thu, 5 Jul 2001 08:22:48 +0200 (CEST) Date: Thu, 5 Jul 2001 08:22:48 +0200 (CEST) From: Seth Mos To: Keith Owens cc: oluap@esctelecom.com.br, linux-xfs@oss.sgi.com Subject: Re: Patch In-Reply-To: <29784.994311805@kao2.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 5 Jul 2001, Keith Owens wrote: > On Thu, 5 Jul 2001 07:38:37 +0200 (CEST), > Seth Mos wrote: > >On Wed, 4 Jul 2001 oluap@esctelecom.com.br wrote: > > > >> How can I patch official 2.4.6 kernel > > > >CVS is -pre9 based but I think 2.4.6 should be forthcoming soon. > >It will take a few days. > > CVS was 2.4.6 for about 2 hours, it is now 2.4.7-pre1 and heading for > 2.4.7-pre2 very soon. ye, flippin gods! Is linus now gone mad and imitate Alan Cox in a sudden change of heart? The previous assumption was legal for the old release pattern of whole kernel releases. I guess tracking the smaller changes in -pre kernels make it easier to keep up with... :) Cheer Seth From owner-linux-xfs@oss.sgi.com Wed Jul 4 23:27:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f656Rxb08645 for linux-xfs-outgoing; Wed, 4 Jul 2001 23:27:59 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f656RwV08642 for ; Wed, 4 Jul 2001 23:27:58 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id XAA20932 for ; Wed, 4 Jul 2001 23:27:50 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 QAA09417; Thu, 5 Jul 2001 16:26:39 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Seth Mos cc: linux-xfs@oss.sgi.com Subject: Re: Patch In-reply-to: Your message of "Thu, 05 Jul 2001 08:22:48 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Jul 2001 16:26:39 +1000 Message-ID: <30276.994314399@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 5 Jul 2001 08:22:48 +0200 (CEST), Seth Mos wrote: >On Thu, 5 Jul 2001, Keith Owens wrote: >> CVS was 2.4.6 for about 2 hours, it is now 2.4.7-pre1 and heading for >> 2.4.7-pre2 very soon. > >ye, flippin gods! Is linus now gone mad and imitate Alan Cox in a >sudden change of heart? Linus is grabbing large chunks from the -ac tree to get the two in sync (or as much as is safe). From owner-linux-xfs@oss.sgi.com Wed Jul 4 23:46:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f656keW09019 for linux-xfs-outgoing; Wed, 4 Jul 2001 23:46:40 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f656kdV09016 for ; Wed, 4 Jul 2001 23:46:39 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f656kXp22063 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 02:46:33 -0400 Date: Thu, 5 Jul 2001 02:46:32 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: KDB vs. X Message-ID: <20010705024632.B9350@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk ObStupidStory: I swapped out my keyboard, and the new one has the APCI keys (Wake/Sleep/Power) where the PrtSc/ScLck/Pause normally are. That latter trio is moved down to become part of the Ins/Home/PgUp/etc group, which now comprises three rows. So... the Pause key, which wakes up KDB, is where the PgUp key is normally found (especially by touch). KDB does not take you to a text console if you wake it when in X. You can figure out where this goes... So, Keith, once I've got myself into the state mentioned above - kernel is halted in KDB, console is in X, frozen - how can I possibly get control of the system again w/o hitting the Big Red Switch? And yes, I learned, put "kdb=off" in my lilo append line.... -- Alan Eldridge Adobe are harassing and demanding extortion payments from the author of KDE's Killustrator and from his employer. Please show support for KDE by not buying or using Adobe's software products. From owner-linux-xfs@oss.sgi.com Thu Jul 5 00:04:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6574TD09469 for linux-xfs-outgoing; Thu, 5 Jul 2001 00:04:29 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6574SV09466 for ; Thu, 5 Jul 2001 00:04:28 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id AAA09539 for ; Thu, 5 Jul 2001 00:01:45 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 RAA09671; Thu, 5 Jul 2001 17:03:04 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Alan Eldridge cc: Linux XFS Mailing List Subject: Re: KDB vs. X In-reply-to: Your message of "Thu, 05 Jul 2001 02:46:32 -0400." <20010705024632.B9350@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Jul 2001 17:03:04 +1000 Message-ID: <30829.994316584@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 5 Jul 2001 02:46:32 -0400, Alan Eldridge wrote: >So, Keith, once I've got myself into the state mentioned above - kernel is >halted in KDB, console is in X, frozen - how can I possibly get control of >the system again w/o hitting the Big Red Switch? Blind typing go and enter should work. kdb reads raw scancodes so the X input mappings should not matter. On my TODO list is "make the pause key exit kdb as well as enter it" so pressing pause again will do a clean continue. From owner-linux-xfs@oss.sgi.com Thu Jul 5 00:15:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f657FEh09733 for linux-xfs-outgoing; Thu, 5 Jul 2001 00:15:14 -0700 Received: from mx.linux.net.cn ([210.82.190.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f657FBV09729 for ; Thu, 5 Jul 2001 00:15:12 -0700 Received: from dfbbb.cn.mvd (unknown [211.99.247.66]) by mx.linux.net.cn (Postfix) with ESMTP id 94BB5B38 for ; Thu, 5 Jul 2001 15:11:57 +0800 (CST) Received: (from dfbb@localhost) by dfbbb.cn.mvd (8.11.2/8.11.2) id f657DwW02778 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 15:13:58 +0800 Date: Thu, 5 Jul 2001 15:13:57 +0800 From: Fang Han To: linux-xfs@oss.sgi.com Subject: When LVM-0.9.1beta7 will be merged to XFS cvs tree? Message-ID: <20010705151357.A2773@dfbbb.cn.mvd> 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.2.5i Organization: None X-Attribution: dfbb Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Now I use it myself, But it is very buggy, xfs_growfs can't work twice, mkfs.xfs can't set block size..... When XFS cvs tree will move to LVM-0.9.1_beta7? Regards dfbb From owner-linux-xfs@oss.sgi.com Thu Jul 5 00:18:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f657I2V09861 for linux-xfs-outgoing; Thu, 5 Jul 2001 00:18:02 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f657I1V09858 for ; Thu, 5 Jul 2001 00:18:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA18017 for ; Thu, 5 Jul 2001 09:17:59 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA19844 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 09:17:58 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 63CF757306 for ; Thu, 5 Jul 2001 09:27:33 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 8730625835 for ; Thu, 5 Jul 2001 09:35:38 +0200 (CEST) Message-ID: <3B4414DB.2C1385A3@ch.sauter-bc.com> Date: Thu, 05 Jul 2001 09:18:51 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: ARCserve 7 for Linux on XFS? Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk For some reason I have to install ARCserve 7 on new Linux servers. Has somebody ARCserve 7 running on an XFS Linux server? I'm interested to know how the following works: - does ARCserve save/restore XFS filesystems correct? - does ARCserve save/restore XFS ACL's correct? - does the disaster recovery work on an XFS / SoftRAID / whatelse server Simon From owner-linux-xfs@oss.sgi.com Thu Jul 5 00:33:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f657XbP10147 for linux-xfs-outgoing; Thu, 5 Jul 2001 00:33:37 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f657XXV10141 for ; Thu, 5 Jul 2001 00:33:33 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f657XJd02808; Thu, 5 Jul 2001 09:33:19 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id JAA14060; Thu, 5 Jul 2001 09:33:01 +0200 (MET DST) Message-ID: <3B4417D5.ECDC1125@god.bel.alcatel.be> Date: Thu, 05 Jul 2001 09:31:33 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Fang Han , "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? References: <20010705151357.A2773@dfbbb.cn.mvd> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Fang Han wrote: > > Now I use it myself, But it is very buggy, xfs_growfs can't work twice, Not entirely true, if U run an xfsrepair on a growed fs .. next time it'll work... Something in the cleanup of growfs is not happening I guess > mkfs.xfs can't set block size..... Which version... I can set block size's /// to any > > When XFS cvs tree will move to LVM-0.9.1_beta7? > > Regards > > dfbb From owner-linux-xfs@oss.sgi.com Thu Jul 5 00:35:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f657ZVd10268 for linux-xfs-outgoing; Thu, 5 Jul 2001 00:35:31 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f657ZSV10265 for ; Thu, 5 Jul 2001 00:35:29 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f657ZLI03229; Thu, 5 Jul 2001 09:35:21 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id JAA14123; Thu, 5 Jul 2001 09:35:03 +0200 (MET DST) Message-ID: <3B44184F.4CD7A506@god.bel.alcatel.be> Date: Thu, 05 Jul 2001 09:33:35 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Simon Matter , "linux-xfs@oss.sgi.com" Subject: Re: ARCserve 7 for Linux on XFS? References: <3B4414DB.2C1385A3@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > > For some reason I have to install ARCserve 7 on new Linux servers. Has > somebody ARCserve 7 running on an XFS Linux server? I'm interested to > know how the following works: > > - does ARCserve save/restore XFS filesystems correct? > - does ARCserve save/restore XFS ACL's correct? > - does the disaster recovery work on an XFS / SoftRAID / whatelse server > > Simon dunno, but I have set up amanda with xfsdump ... and it kinda works... sometimes indexes are getting thrown up, this is an interfacing issue, working on it. wrapper script... to take out the extra's xfsdump and xfsrestore generate. From owner-linux-xfs@oss.sgi.com Thu Jul 5 00:35:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f657Zf410367 for linux-xfs-outgoing; Thu, 5 Jul 2001 00:35:41 -0700 Received: from mx.linux.net.cn ([210.82.190.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f657ZcV10360 for ; Thu, 5 Jul 2001 00:35:38 -0700 Received: from dfbbb.cn.mvd (unknown [211.99.247.66]) by mx.linux.net.cn (Postfix) with ESMTP id 79ACBAE6 for ; Thu, 5 Jul 2001 15:33:04 +0800 (CST) Received: (from dfbb@localhost) by dfbbb.cn.mvd (8.11.2/8.11.2) id f657ZYG02968 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 15:35:34 +0800 Date: Thu, 5 Jul 2001 15:35:34 +0800 From: Fang Han To: "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? Message-ID: <20010705153534.B2773@dfbbb.cn.mvd> Mail-Followup-To: "linux-xfs@oss.sgi.com" References: <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B4417D5.ECDC1125@god.bel.alcatel.be>; from buggenkr@god.bel.alcatel.be on Thu, Jul 05, 2001 at 09:31:33AM +0200 Organization: None X-Attribution: dfbb Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 09:31:33AM +0200, kris buggenhout wrote: > Fang Han wrote: > > > > Now I use it myself, But it is very buggy, xfs_growfs can't work twice, > > Not entirely true, if U run an xfsrepair on a growed fs .. next time > it'll work... > Something in the cleanup of growfs is not happening I guess > > > mkfs.xfs can't set block size..... xfsprogs-1.2.8 LVM-0.9.1_beta7 linux-2.4.6pre9 plus LVM patch > > Which version... I can set block size's /// to any > > > > > When XFS cvs tree will move to LVM-0.9.1_beta7? > > > > Regards > > > > dfbb From owner-linux-xfs@oss.sgi.com Thu Jul 5 01:18:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f658ICX11055 for linux-xfs-outgoing; Thu, 5 Jul 2001 01:18:12 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f658I9V11052 for ; Thu, 5 Jul 2001 01:18:09 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id CCE4F1E11B; Thu, 5 Jul 2001 10:18:01 +0200 (MEST) Date: Thu, 5 Jul 2001 10:17:47 +0200 From: Andi Kleen To: kris buggenhout Cc: Fang Han , "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? Message-ID: <20010705101747.A32674@gruyere.muc.suse.de> References: <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B4417D5.ECDC1125@god.bel.alcatel.be>; from buggenkr@god.bel.alcatel.be on Thu, Jul 05, 2001 at 09:31:33AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 09:31:33AM +0200, kris buggenhout wrote: > Fang Han wrote: > > > > Now I use it myself, But it is very buggy, xfs_growfs can't work twice, > > Not entirely true, if U run an xfsrepair on a growed fs .. next time > it'll work... > Something in the cleanup of growfs is not happening I guess > > > mkfs.xfs can't set block size..... > > Which version... I can set block size's /// to any All block devices in a XFS kernel need a special patch to add an ioctl to set the logical block size. The original poster probably didn't add that ioctl to his new hacked in LVM; which will cause all kinds of problems with xfs user tools and also probably file system corruption. > > When XFS cvs tree will move to LVM-0.9.1_beta7? My guess is when Linus does; as maintaining any more changes to Linus than necessary is a lot of work. -Andi From owner-linux-xfs@oss.sgi.com Thu Jul 5 01:46:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f658kUL11552 for linux-xfs-outgoing; Thu, 5 Jul 2001 01:46:30 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f658kTV11549 for ; Thu, 5 Jul 2001 01:46:29 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id BAA09933 for ; Thu, 5 Jul 2001 01:46:09 -0700 (PDT) mail_from (tes@snort.melbourne.sgi.com) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA17689 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 18:44:48 +1000 (EST) Date: Thu, 5 Jul 2001 18:44:48 +1000 (EST) From: Timothy Shimmin Message-Id: <200107050844.SAA17689@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/restore/librmt Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This should output some librmt warnings when we have trouble talking to a host for remote dumping/restoring. Previously, these would only be seen by setting an environment variable - which is not always so useful. --Tim Date: Thu Jul 5 01:42:14 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/tes/slinx-xfs-acl The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98233a cmd/xfsdump/librmt/rmtmsg.c - 1.1 - Provide msg functions instead of macros. cmd/xfsdump/dump/inomap.c - 1.3 - Print out the inode#s that were in violation. This has been done in answer to a reported assertion failure. cmd/xfsdump/common/main.c - 1.4 - Turn on librmt warning messages. cmd/xfsdump/librmt/rmtopen.c - 1.4 - Update to use new msg functions. cmd/xfsdump/librmt/rmtlib.h - 1.2 - Update for new method of reporting msgs. cmd/xfsdump/librmt/Makefile - 1.3 - Add rmtmsg.c . cmd/xfsdump/librmt/rmtioctl.c - 1.3 - Change to use _rmt_msg() for msgs. No longer fallback to deciding on host type based on mtget size. This was essential prior to using uname. cmd/xfsdump/VERSION - 1.10 - Bump version for librmt changes. cmd/xfsdump/doc/CHANGES - 1.11 - For revision 10, we have librmt msg changes. cmd/xfsdump/doc/README.xfsdump - 1.3 - Update for RMT_TAPE_USER used in QA. From owner-linux-xfs@oss.sgi.com Thu Jul 5 02:16:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f659Gc512161 for linux-xfs-outgoing; Thu, 5 Jul 2001 02:16:38 -0700 Received: from melkor.dnp.fmph.uniba.sk (mail@atlas15.dnp.fmph.uniba.sk [158.195.25.215]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f659GaV12158 for ; Thu, 5 Jul 2001 02:16:36 -0700 Received: from garabik by melkor.dnp.fmph.uniba.sk with local (Exim 3.22 #1 (Debian)) id 15I5FF-0005NI-00 for ; Thu, 05 Jul 2001 11:16:21 +0200 Date: Thu, 5 Jul 2001 11:16:21 +0200 From: Radovan Garabik To: linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch available Message-ID: <20010705111621.A20639@melkor.dnp.fmph.uniba.sk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > There is a 2.4.6 patch available in the patches/ directory of the ftp > site, get the one dated July 5, linux-2.4.6-xfs-07052001.patch.bz2 just a small nitpick: could you please use another date format, such as 200010705, since it is really not clear whether it is from 5th July or 7th May (and I would expect the later....) -- ----------------------------------------------------------- | Radovan Garabik http://melkor.dnp.fmph.uniba.sk/~garabik/ | | __..--^^^--..__ garabik @ melkor.dnp.fmph.uniba.sk | ----------------------------------------------------------- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread! From owner-linux-xfs@oss.sgi.com Thu Jul 5 02:21:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f659LKN12367 for linux-xfs-outgoing; Thu, 5 Jul 2001 02:21:20 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f659LJV12364 for ; Thu, 5 Jul 2001 02:21:19 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip33.idcomm.com [209.60.72.160]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f659Ncl30161 for ; Thu, 5 Jul 2001 03:23:39 -0600 Message-ID: <3B443207.6A6E7E44@idcomm.com> Date: Thu, 05 Jul 2001 03:23:19 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Keith Owens wrote: > > On Thu, 5 Jul 2001 07:38:37 +0200 (CEST), > Seth Mos wrote: > >On Wed, 4 Jul 2001 oluap@esctelecom.com.br wrote: > > > >> How can I patch official 2.4.6 kernel > > > >CVS is -pre9 based but I think 2.4.6 should be forthcoming soon. > >It will take a few days. > > CVS was 2.4.6 for about 2 hours, it is now 2.4.7-pre1 and heading for > 2.4.7-pre2 very soon. Are tags issued as standard practice at each sync? E.G., is there any problem with naming a tag to get the 2.4.6-pre3-xfs or 2.4.6-xfs at any time, despite the fast changes? (what tag name scheme is used?) D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 04:37:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Bb2u14855 for linux-xfs-outgoing; Thu, 5 Jul 2001 04:37:02 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65Bb1V14852 for ; Thu, 5 Jul 2001 04:37:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id NAA08353 for ; Thu, 5 Jul 2001 13:36:59 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id NAA12311 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 13:36:58 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 1524C57306 for ; Thu, 5 Jul 2001 13:46:19 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id A005925835 for ; Thu, 5 Jul 2001 13:54:23 +0200 (CEST) Message-ID: <3B445180.70F021DB@ch.sauter-bc.com> Date: Thu, 05 Jul 2001 13:37:36 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Reserved space in XFS for super-user Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Sorry if this is somewhere in the docs but I didn't find it. Is there a way to reserve space on a XFS filesystem for the super-user, a la -m options in mke2fs, which reserves 5% per default for root? I was just wondering that I was able to fill a XFS partition as 'normal' user. Simon From owner-linux-xfs@oss.sgi.com Thu Jul 5 06:20:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65DKVd16562 for linux-xfs-outgoing; Thu, 5 Jul 2001 06:20:31 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65DKUV16558 for ; Thu, 5 Jul 2001 06:20:30 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id PAA21904; Thu, 5 Jul 2001 15:20:24 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id PAA14816; Thu, 5 Jul 2001 15:21:37 +0200 (CEST) Date: Thu, 5 Jul 2001 15:21:36 +0200 (CEST) From: Seth Mos To: Radovan Garabik cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch available In-Reply-To: <20010705111621.A20639@melkor.dnp.fmph.uniba.sk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 5 Jul 2001, Radovan Garabik wrote: > > > There is a 2.4.6 patch available in the patches/ directory of the ftp > > site, get the one dated July 5, linux-2.4.6-xfs-07052001.patch.bz2 > > > just a small nitpick: could you please use another date format, > such as 200010705, since it is really not clear whether it is > from 5th July or 7th May (and I would expect the later....) Europeans use %d%m%Y while in america they use %m%d%Y. It confuses me everytime I see it. Cheers Seth From owner-linux-xfs@oss.sgi.com Thu Jul 5 06:31:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65DVN516789 for linux-xfs-outgoing; Thu, 5 Jul 2001 06:31:23 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65DVIV16786 for ; Thu, 5 Jul 2001 06:31:19 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA1037820 for ; Thu, 5 Jul 2001 15:31:12 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2346987; Thu, 5 Jul 2001 08:29:49 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA30682; Thu, 5 Jul 2001 08:29:49 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f65DVU924817; Thu, 5 Jul 2001 08:31:30 -0500 Message-Id: <200107051331.f65DVU924817@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Keith Owens cc: Alan Eldridge , Linux XFS Mailing List Subject: Re: KDB vs. X In-Reply-To: Message from Keith Owens of "Thu, 05 Jul 2001 17:03:04 +1000." <30829.994316584@kao2.melbourne.sgi.com> Date: Thu, 05 Jul 2001 08:31:30 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, 5 Jul 2001 02:46:32 -0400, > Alan Eldridge wrote: > >So, Keith, once I've got myself into the state mentioned above - kernel is > >halted in KDB, console is in X, frozen - how can I possibly get control of > >the system again w/o hitting the Big Red Switch? > > Blind typing go and enter should work. kdb reads raw scancodes so the > X input mappings should not matter. On my TODO list is "make the pause > key exit kdb as well as enter it" so pressing pause again will do a > clean continue. Typing go does work from within X should you happen to drop into kdb by mistake. Keith, the really nice trick would be virtual console switching from within kdb so if I crash while X is on the screen I could at least go see what happened. Steve From owner-linux-xfs@oss.sgi.com Thu Jul 5 06:39:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Dd1N16960 for linux-xfs-outgoing; Thu, 5 Jul 2001 06:39:01 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65DcxV16957 for ; Thu, 5 Jul 2001 06:38:59 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.16 #1) id 15I9LD-0004B8-00; Thu, 05 Jul 2001 15:38:48 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f65DcFw02171; Thu, 5 Jul 2001 09:38:15 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Fang Han Cc: linux-xfs@oss.sgi.com Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? References: <20010705151357.A2773@dfbbb.cn.mvd> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 05 Jul 2001 09:38:14 -0400 In-Reply-To: <20010705151357.A2773@dfbbb.cn.mvd> Message-ID: Lines: 27 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "dfbb" == Fang Han writes: dfbb> Now I use it myself, But it is very buggy, xfs_growfs can't work dfbb> twice, mkfs.xfs can't set block size..... The LVM patch procedure will actually back out the XFS-specific changes. So merging LVM into our tree is more than just running make in the PATCHES directory. dfbb> When XFS cvs tree will move to LVM-0.9.1_beta7? Never. beta7 is broken, and the LVM development tree has alignment problems that the Sistina folks are working hard on fixing. So we'll keep what's currently in the XFS tree until LVM 1.0 gets out and we get a chance to poke a that. If you've been running LVM for a while and have existing volumes, stick with the stuff in the XFS tree. If you want to create a new LVM setup from scratch, I suggest you hold off at least until 1.0 gets out. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 06:40:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65DeOa17058 for linux-xfs-outgoing; Thu, 5 Jul 2001 06:40:24 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65DeMV17055 for ; Thu, 5 Jul 2001 06:40:22 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 1C7D11E205; Thu, 5 Jul 2001 15:40:17 +0200 (MEST) Date: Thu, 5 Jul 2001 15:40:09 +0200 From: Andi Kleen To: Steve Lord Cc: Keith Owens , Alan Eldridge , Linux XFS Mailing List Subject: Re: KDB vs. X Message-ID: <20010705154009.A8384@gruyere.muc.suse.de> References: <200107051331.f65DVU924817@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107051331.f65DVU924817@jen.americas.sgi.com>; from lord@sgi.com on Thu, Jul 05, 2001 at 08:31:30AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 08:31:30AM -0500, Steve Lord wrote: > Typing go does work from within X should you happen to drop into kdb by > mistake. Keith, the really nice trick would be virtual console switching from > within kdb so if I crash while X is on the screen I could at least go > see what happened. That would basically requiring duplicating a lot of the X server code into KDB (vty switching from X requires intimate knowledge about the chipset etc. and is handled in userspace). With fbcon it would be in theory possible, but that still is risky with X acceleration and worse fbcon and the console subsystem is a very complex beasts with lots of locks, so if KDB started to mess with that it would probably soon end in deadlock country. Your best bet is to always boot with a serial console enabled in addition to the normal console; and when you see the blinking keyboard lights switch on your laptop and connect it via a null modem to the serial port and edit from there. -Andi From owner-linux-xfs@oss.sgi.com Thu Jul 5 06:43:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65DhgK17187 for linux-xfs-outgoing; Thu, 5 Jul 2001 06:43:42 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65DhfV17184 for ; Thu, 5 Jul 2001 06:43:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id GAA22066 for ; Thu, 5 Jul 2001 06:43:34 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2348408; Thu, 5 Jul 2001 08:42:22 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA40649; Thu, 5 Jul 2001 08:42:21 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f65Di2X24878; Thu, 5 Jul 2001 08:44:02 -0500 Message-Id: <200107051344.f65Di2X24878@jen.americas.sgi.com> To: Andi Kleen cc: Steve Lord , Keith Owens , Alan Eldridge , Linux XFS Mailing List Subject: Re: KDB vs. X References: <200107051331.f65DVU924817@jen.americas.sgi.com> <20010705154009.A8384@gruyere.muc.suse.de> Comments: In-reply-to Andi Kleen message dated "Thu, 05 Jul 2001 15:40:09 +0200." Date: Thu, 05 Jul 2001 08:44:02 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, Jul 05, 2001 at 08:31:30AM -0500, Steve Lord wrote: > > Typing go does work from within X should you happen to drop into kdb by > > mistake. Keith, the really nice trick would be virtual console switching fr > om > > within kdb so if I crash while X is on the screen I could at least go > > see what happened. > > That would basically requiring duplicating a lot of the X server code into > KDB (vty switching from X requires intimate knowledge about the chipset etc. > and is handled in userspace). With fbcon it would be in theory possible, > but that still is risky with X acceleration and worse fbcon and the console > subsystem is a very complex beasts with lots of locks, so if KDB started to > mess with that it would probably soon end in deadlock country. I like giving Keith challenges! No this was not a serious request. Steve From owner-linux-xfs@oss.sgi.com Thu Jul 5 06:54:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65DsgW17443 for linux-xfs-outgoing; Thu, 5 Jul 2001 06:54:42 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65DsfV17440 for ; Thu, 5 Jul 2001 06:54:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id GAA23110 for ; Thu, 5 Jul 2001 06:54:33 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2339442; Thu, 5 Jul 2001 08:53:22 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA52977; Thu, 5 Jul 2001 08:53:22 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f65Dt3L28657; Thu, 5 Jul 2001 08:55:03 -0500 Message-Id: <200107051355.f65Dt3L28657@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Seth Mos cc: Radovan Garabik , linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch available In-Reply-To: Message from Seth Mos of "Thu, 05 Jul 2001 15:21:36 +0200." Date: Thu, 05 Jul 2001 08:55:03 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, 5 Jul 2001, Radovan Garabik wrote: > > > > > > There is a 2.4.6 patch available in the patches/ directory of the ftp > > > site, get the one dated July 5, linux-2.4.6-xfs-07052001.patch.bz2 > > > > > > just a small nitpick: could you please use another date format, > > such as 200010705, since it is really not clear whether it is > > from 5th July or 7th May (and I would expect the later....) > > Europeans use %d%m%Y while in america they use %m%d%Y. > It confuses me everytime I see it. > > Cheers > Seth And I am English and Keith is Australian, so go figure! Steve p.s. 4th of July here yesterday, and my patriotic duty as an Englishman to sow seeds of dissention amongst the colonists ;-). Actually the network link from home to work was out so I could not see or read email yesterday, for which my wife and son thank me. p.p.s doing an ls -l in ftp will tell you when the files were created which is a pretty good hint. From owner-linux-xfs@oss.sgi.com Thu Jul 5 07:13:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65EDop17885 for linux-xfs-outgoing; Thu, 5 Jul 2001 07:13:50 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65EDnV17882 for ; Thu, 5 Jul 2001 07:13:49 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA24827 for ; Thu, 5 Jul 2001 07:13:42 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id HAA25775; Thu, 5 Jul 2001 07:13:16 -0700 (PDT) Message-ID: <3B447559.780D502E@sgi.com> Date: Thu, 05 Jul 2001 09:10:33 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Radovan Garabik CC: linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch available References: <20010705111621.A20639@melkor.dnp.fmph.uniba.sk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Radovan Garabik wrote: > just a small nitpick: could you please use another date format, > such as 200010705, since it is really not clear whether it is > from 5th July or 7th May (and I would expect the later....) I'm generating that patch from a script, I will happily change the date to an ISO standard for our friends across the water... :) -Eric From owner-linux-xfs@oss.sgi.com Thu Jul 5 07:22:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65EMO918148 for linux-xfs-outgoing; Thu, 5 Jul 2001 07:22:24 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65EMNV18145 for ; Thu, 5 Jul 2001 07:22:23 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA25778 for ; Thu, 5 Jul 2001 07:22:16 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id HAA92692; Thu, 5 Jul 2001 07:21:50 -0700 (PDT) Message-ID: <3B44775B.2D49BD6B@sgi.com> Date: Thu, 05 Jul 2001 09:19:07 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > Are tags issued as standard practice at each sync? E.G., is there any > problem with naming a tag to get the 2.4.6-pre3-xfs or 2.4.6-xfs at any > time, despite the fast changes? (what tag name scheme is used?) I'll have to look into this, CVS is pushed out automatically from our own internal source code management tools, and I'm not sure if the concept of a CVS tag can make it from one to the other - it may take some manual manipulation of the CVS tree. A few people have asked for this, if there's a good way to do it, maybe we can get more diligent about it. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 5 07:43:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Eh2C18666 for linux-xfs-outgoing; Thu, 5 Jul 2001 07:43:02 -0700 Received: from musuko.uchicago.edu (musuko.uchicago.edu [128.135.39.147]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65Eh1V18663 for ; Thu, 5 Jul 2001 07:43:01 -0700 Received: (from sl70@localhost) by musuko.uchicago.edu (8.11.2/8.11.2) id f65Eh0h18741 for linux-xfs@oss.sgi.com; Thu, 5 Jul 2001 09:43:00 -0500 Message-ID: X-Mailer: XFMail 1.5.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 05 Jul 2001 09:43:00 -0500 (CDT) Reply-To: s-luppescu@uchicago.edu Organization: Univ of Chicago From: s-luppescu@uchicago.edu To: linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch available Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05-Jul-2001 Seth Mos wrote: > Europeans use %d%m%Y while in america they use %m%d%Y. > It confuses me everytime I see it. I thought the ISO standard was %Y%m%d. ______________________________________________________________________ Stuart Luppescu -=-=- University of Chicago $(B:MJ8$HCRF`H~$NIc(B -=-=- s-luppescu@uchicago.edu http://www.consortium-chicago.org/people/sl.html http://musuko.uchicago.edu/pubkey.asc for PGP Public Key ICQ #21172047 AIM: psycho7070 The pollution's at that awkward stage. Too thick to navigate and too thin to cultivate. -- Doug Sneyd >> Sent on 05-Jul-2001 at 09:42:02 with xfmail From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:02:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65F2nR19000 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:02:49 -0700 Received: from nwcst289.netaddress.usa.net (nwcst289.netaddress.usa.net [204.68.23.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65F2lV18997 for ; Thu, 5 Jul 2001 08:02:47 -0700 Received: (qmail 29891 invoked by uid 60001); 5 Jul 2001 15:02:47 -0000 Message-ID: <20010705150247.29890.qmail@nwcst289.netaddress.usa.net> Received: from 204.68.23.34 by nwcst289 for [204.210.236.21] via web-mailer(34FM.0700.18.03B) on Thu Jul 5 15:02:47 GMT 2001 Date: 5 Jul 2001 11:02:47 EDT From: Nathaniel Graham To: linux-xfs@oss.sgi.com Subject: Re: [Re: 2.4.6 patch available] X-Mailer: USANET web-mailer (34FM.0700.18.03B) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f65F2mV18998 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > On Thu, 5 Jul 2001, Radovan Garabik wrote: > > > > > > There is a 2.4.6 patch available in the patches/ directory of the ftp > > > site, get the one dated July 5, linux-2.4.6-xfs-07052001.patch.bz2 Someone mentioned xfs patches and how cleanly they tend to apply recently (during the jfs discussion, I believe)...the 2.4.6 patch went on perfectly for me (onto a vanilla 2.4.6 source, with the v4l2 patch applied afterwards). Builds perfectly with gcc-3.0, and so far is running fine. Awesome job guys! > > Europeans use %d%m%Y while in america they use %m%d%Y. > It confuses me everytime I see it. > > Cheers > Seth > Everybody uses their own special date thing...the Marine Corps and the Navy (US) have two different date formats, and naval medical personnel are always saying "and don't give that jacked-up Marine date either". Someone will be confused no matter what you do. Nathaniel Graham From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:18:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FI4B19292 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:18:04 -0700 Received: from m1.debitech.com ([212.209.112.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FI1V19289 for ; Thu, 5 Jul 2001 08:18:02 -0700 Received: (qmail 15209 invoked from network); 5 Jul 2001 15:19:15 -0000 Received: from mail.debitech.com (HELO debitech11.debitech.com) (212.209.112.12) by m1.debitech.com with SMTP; 5 Jul 2001 15:19:15 -0000 Received: by DEBITECH11 with Internet Mail Service (5.5.2650.21) id ; Thu, 5 Jul 2001 17:19:05 +0200 Message-ID: <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> From: Stephen Brewer To: "'linux-xfs@oss.sgi.com'" Subject: encryption Date: Thu, 5 Jul 2001 17:18:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk i am interested in encrypted filesystems and was wondering if xfs would be good to encrypt... my thoughts was to intercept the reading/writing of inodes from/to disk and doing the en-decryption there... the passphrase for the encryption would be entered during the mounting of the filesystem (and deleted from memory during the unmount!)... so my questions... is there a technical reason why xfs is unsuitable for this??? has anybody thought about this before??? i have found a method called 'xfs_iflush_int' does all writing to the hard disk go through here, or are there many places in the code that would need to be modified for decrypting/encrypting??? is this a stupid idea??? :) steve... ps i hope this is the right place to send this message... pps is there anybody else interesed??? From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:19:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FJWb19408 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:19:32 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FJUV19405 for ; Thu, 5 Jul 2001 08:19:30 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f65FJTNe057327; Thu, 5 Jul 2001 10:19:29 -0500 (CDT) Message-ID: <3B448571.525BB450@thebarn.com> Date: Thu, 05 Jul 2001 10:19:13 -0500 From: cattelan@thebarn.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > Keith Owens wrote: > > > > On Thu, 5 Jul 2001 07:38:37 +0200 (CEST), > > Seth Mos wrote: > > >On Wed, 4 Jul 2001 oluap@esctelecom.com.br wrote: > > > > > >> How can I patch official 2.4.6 kernel > > > > > >CVS is -pre9 based but I think 2.4.6 should be forthcoming soon. > > >It will take a few days. > > > > CVS was 2.4.6 for about 2 hours, it is now 2.4.7-pre1 and heading for > > 2.4.7-pre2 very soon. > > Are tags issued as standard practice at each sync? E.G., is there any > problem with naming a tag to get the 2.4.6-pre3-xfs or 2.4.6-xfs at any > time, despite the fast changes? (what tag name scheme is used?) If I had time to catch each release I would tag them but if the are going to go whizzing by so fast I don't have time to do the checkout and subsequent tag. If somebody has a census file at 2.4.6 send it to me and I'll apply the TAG to the tree. From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:37:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FbRR19908 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:37:27 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FbPV19905 for ; Thu, 5 Jul 2001 08:37:25 -0700 Received: (qmail 31542 invoked by uid 8); 5 Jul 2001 15:37:24 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: 2.4.6 patch available Date: Thu, 5 Jul 2001 15:37:23 +0000 (UTC) Organization: spoiled dot org Lines: 30 Distribution: local Message-ID: References: <200107051355.f65Dt3L28657@jen.americas.sgi.com> X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: >> On Thu, 5 Jul 2001, Radovan Garabik wrote: >> >> > >> > > There is a 2.4.6 patch available in the patches/ directory of the ftp >> > > site, get the one dated July 5, linux-2.4.6-xfs-07052001.patch.bz2 >> > >> > >> > just a small nitpick: could you please use another date format, >> > such as 200010705, since it is really not clear whether it is >> > from 5th July or 7th May (and I would expect the later....) >> >> Europeans use %d%m%Y while in america they use %m%d%Y. >> It confuses me everytime I see it. >> >> Cheers >> Seth > > And I am English and Keith is Australian, so go figure! Yeah, all fine, but using a sortable and more important ISO time stamp makes it easier for all. Just my two Euro cents... Back to lurking, Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:40:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FeSZ20019 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:40:28 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FeOV20016 for ; Thu, 5 Jul 2001 08:40:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA04557 for ; Thu, 5 Jul 2001 08:40:24 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2347137; Thu, 5 Jul 2001 10:39:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA37107; Thu, 5 Jul 2001 10:39:06 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f65Ff9F01529; Thu, 5 Jul 2001 10:41:09 -0500 Message-Id: <200107051541.f65Ff9F01529@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Stephen Brewer cc: "'linux-xfs@oss.sgi.com'" Subject: Re: encryption In-Reply-To: Message from Stephen Brewer of "Thu, 05 Jul 2001 17:18:57 +0200." <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> Date: Thu, 05 Jul 2001 10:41:09 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > i am interested in encrypted filesystems and was wondering if xfs would be > good to encrypt... It might be a little tough! > > my thoughts was to intercept the reading/writing of inodes from/to disk and > doing the en-decryption there... > > the passphrase for the encryption would be entered during the mounting of > the filesystem (and deleted from memory during the unmount!)... > > so my questions... > > is there a technical reason why xfs is unsuitable for this??? > If you have an encryption algorithm which does not change the size of the information, i.e. the encrypted data takes the same number of bytes as the non-encrypted data, then things are a lot easier. My memory of encryption says that this is not normally the case unless you are using very basic algorithms which are easy to crack. Once your algorithm changes the size of data it gets really hard to deal with managing disk layout. > has anybody thought about this before??? > > i have found a method called 'xfs_iflush_int' does all writing to the hard > disk go through here, or are there many places in the code that would need > to be modified for decrypting/encrypting??? The tricky part is the journal, do you want to protect the journal as well? Inodes written to the journal in a different format from the on disk format. XFS has in memory and on disk inodes, the on disk format is mapped to the internal format when we read in the buffer and the internal format is mapped back again when we write it out. So in principal there are not many places you need to change things, provided the disk layout does not have to change. > > is this a stupid idea??? :) Stupid no, ambitious yes. Steve > > steve... > > ps i hope this is the right place to send this message... > pps is there anybody else interesed??? From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:44:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FigX20138 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:44:42 -0700 Received: from relay01.cablecom.net (relay01.cablecom.net [62.2.33.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FifV20135 for ; Thu, 5 Jul 2001 08:44:41 -0700 Received: from mail.swissonline.ch (mail.swissonline.ch [62.2.32.83]) by relay01.cablecom.net (8.11.3/8.11.0/SOL/MXRELAY-1.03) with ESMTP id f65FiWh46068 for ; Thu, 5 Jul 2001 17:44:32 +0200 (CEST) Received: from asterix (dclient109-112.hispeed.ch [62.2.109.112]) by mail.swissonline.ch (8.11.4/8.11.4/MSOL-2.35/25-Jun-2001) with SMTP id f65FiSs08827 for ; Thu, 5 Jul 2001 17:44:32 +0200 (MET DST) Content-Type: text/plain; charset="iso-8859-1" From: Christian Widmer Reply-To: cwidmer@iiic.ethz.ch To: "'linux-xfs@oss.sgi.com'" Subject: Re: encryption Date: Thu, 5 Jul 2001 17:47:21 +0200 X-Mailer: KMail [version 1.2] References: <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> In-Reply-To: <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <0107051747210G.30268@asterix> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk the idea is not new (exept using xfs maybe). the new suse7.2 distribution has support for encryted file system. and it looks like it does't matter what filesystem you use. there is a description on their german homepage, un- fortunately in germen. it uses the loop device to add an additional layer. setup a encryted device: $modprobe loop_fish2 $losetup -e twofish /dev/loop0 /dev/hda3 $mkdir /topsecret $mkreiserfs /dev/loop0 $mount -t reiserfs /dev/loop0 /topsecret //chris On Thursday 05 July 2001 17:18, you wrote: > i am interested in encrypted filesystems and was wondering if xfs would be > good to encrypt... > > my thoughts was to intercept the reading/writing of inodes from/to disk and > doing the en-decryption there... > > the passphrase for the encryption would be entered during the mounting of > the filesystem (and deleted from memory during the unmount!)... > > so my questions... > > is there a technical reason why xfs is unsuitable for this??? > > has anybody thought about this before??? > > i have found a method called 'xfs_iflush_int' does all writing to the hard > disk go through here, or are there many places in the code that would need > to be modified for decrypting/encrypting??? > > is this a stupid idea??? :) > > steve... > > ps i hope this is the right place to send this message... > pps is there anybody else interesed??? -- christian widmer zurlindenstrasse 294, 8003 zurich, switzerland email: cwidmer@iiic.ethz.ch phone: ++41 (0)1 491 03 68 From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:45:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FjJk20252 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:45:19 -0700 Received: from relay03.cablecom.net (relay03.cablecom.net [62.2.33.103]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FjHV20249 for ; Thu, 5 Jul 2001 08:45:18 -0700 Received: from mail.swissonline.ch (mail.swissonline.ch [62.2.32.83]) by relay03.cablecom.net (8.11.3/8.11.0/SOL/MXRELAY-1.03) with ESMTP id f65FjBr84891 for ; Thu, 5 Jul 2001 17:45:11 +0200 (CEST) Received: from asterix (dclient109-112.hispeed.ch [62.2.109.112]) by mail.swissonline.ch (8.11.4/8.11.4/MSOL-2.35/25-Jun-2001) with SMTP id f65FjBs09965 for ; Thu, 5 Jul 2001 17:45:11 +0200 (MET DST) Content-Type: text/plain; charset="iso-8859-1" From: Christian Widmer Reply-To: cwidmer@iiic.ethz.ch To: "'linux-xfs@oss.sgi.com'" Subject: Re: [Re: 2.4.6 patch available] Date: Thu, 5 Jul 2001 17:48:04 +0200 X-Mailer: KMail [version 1.2] References: <20010705150247.29890.qmail@nwcst289.netaddress.usa.net> In-Reply-To: <20010705150247.29890.qmail@nwcst289.netaddress.usa.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <0107051748040H.30268@asterix> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Europeans use %d%m%Y while in america they use %m%d%Y. > > It confuses me everytime I see it. > > > > Everybody uses their own special date thing...the Marine Corps and > the Navy (US) have two different date formats, and naval medical > personnel are always saying "and don't give that jacked-up Marine > date either". Someone will be confused no matter what you do. > s it reay so difficult? whats about using 07Jul2001, Jul072001, ... or any permutation and no one will be confused any more. //chris From owner-linux-xfs@oss.sgi.com Thu Jul 5 08:58:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65FwNB20615 for linux-xfs-outgoing; Thu, 5 Jul 2001 08:58:23 -0700 Received: from main.braxis.co.uk (root@main.braxis.co.uk [213.77.40.29]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65FvrV20579 for ; Thu, 5 Jul 2001 08:57:55 -0700 Received: (from kszysiu@localhost) by main.braxis.co.uk (8.9.3/8.9.3) id RAA28478; Thu, 5 Jul 2001 17:56:12 +0200 Date: Thu, 5 Jul 2001 17:56:12 +0200 From: Krzysztof Rusocki To: Christian Widmer Cc: "'linux-xfs@oss.sgi.com'" Subject: Re: encryption Message-ID: <20010705175612.A27494@main.braxis.co.uk> References: <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> <0107051747210G.30268@asterix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <0107051747210G.30268@asterix>; from cwidmer@iiic.ethz.ch on Thu, Jul 05, 2001 at 05:47:21PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Steve, you may also take a look at Loopback-Encrypted-Filesystem-HOWTO on www.linuxdoc.org , you'll need to patch your kernel with encryption patch (available on ftp.kernel.org afaik).. However i do not know how is it going to interact with XFS - opinion of someone who did try to patch XFS tree with crypto patch would really be needed here... Cheers, Krzysztof On Thu, Jul 05, 2001 at 05:47:21PM +0200, Christian Widmer wrote: > the idea is not new (exept using xfs maybe). the new suse7.2 distribution > has support for encryted file system. and it looks like it does't matter what > filesystem you use. there is a description on their german homepage, un- > fortunately in germen. it uses the loop device to add an additional layer. > > setup a encryted device: > $modprobe loop_fish2 > $losetup -e twofish /dev/loop0 /dev/hda3 > $mkdir /topsecret > $mkreiserfs /dev/loop0 > $mount -t reiserfs /dev/loop0 /topsecret > > //chris > > On Thursday 05 July 2001 17:18, you wrote: > > i am interested in encrypted filesystems and was wondering if xfs would be > > good to encrypt... > > > > my thoughts was to intercept the reading/writing of inodes from/to disk and > > doing the en-decryption there... > > > > the passphrase for the encryption would be entered during the mounting of > > the filesystem (and deleted from memory during the unmount!)... > > > > so my questions... > > > > is there a technical reason why xfs is unsuitable for this??? > > > > has anybody thought about this before??? > > > > i have found a method called 'xfs_iflush_int' does all writing to the hard > > disk go through here, or are there many places in the code that would need > > to be modified for decrypting/encrypting??? > > > > is this a stupid idea??? :) > > > > steve... > > > > ps i hope this is the right place to send this message... > > pps is there anybody else interesed??? > > -- > christian widmer > zurlindenstrasse 294, 8003 zurich, switzerland > email: cwidmer@iiic.ethz.ch > phone: ++41 (0)1 491 03 68 From owner-linux-xfs@oss.sgi.com Thu Jul 5 09:01:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65G13020793 for linux-xfs-outgoing; Thu, 5 Jul 2001 09:01:03 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65G10V20785 for ; Thu, 5 Jul 2001 09:01:00 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 09A181E2D4; Thu, 5 Jul 2001 18:00:55 +0200 (MEST) Date: Thu, 5 Jul 2001 18:00:30 +0200 From: Andi Kleen To: Steve Lord Cc: Stephen Brewer , "'linux-xfs@oss.sgi.com'" Subject: Re: encryption Message-ID: <20010705180030.A11694@gruyere.muc.suse.de> References: <200107051541.f65Ff9F01529@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107051541.f65Ff9F01529@jen.americas.sgi.com>; from lord@sgi.com on Thu, Jul 05, 2001 at 10:41:09AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 10:41:09AM -0500, Steve Lord wrote: > If you have an encryption algorithm which does not change the size of > the information, i.e. the encrypted data takes the same number of > bytes as the non-encrypted data, then things are a lot easier. My > memory of encryption says that this is not normally the case unless > you are using very basic algorithms which are easy to crack. > Once your algorithm changes the size of data it gets really hard to > deal with managing disk layout. If your data is a multiply of the block cipher blocksize (normally 16 bytes on a AES style cipher or 8 bytes for DES) then the data size doesn't change. If it's not a multiple of a good block cipher size an stream cipher could be also used, which does not operate in fixed blocks (at least not blocks bigger than a byte); but it requires more complicated key management because you cannot reuse the key for two different disk blocks. As far as I can see all data structures in XFS on disk should be multiplies of 16 bytes. BTW; Linux already has an existing encryption interface for file systems via the loopback device; unfortunately the existing encryption modules all have various drawbacks and problems. This works only per block device of course and it is relatively hard to store any metadata which means e.g. it is impossible to check the user's password. An XFS based per file encryption mechanism would be definitely interesting. One problem is how to specify the password per file without having to patch all applications. I'm not sure why the inodes should be encrypted though (they really do not contain much sensitive data and encrypted inodes would make backup really hard); wouldn't it make more sense to encrypt directories and file data only? > > > has anybody thought about this before??? > > > > i have found a method called 'xfs_iflush_int' does all writing to the hard > > disk go through here, or are there many places in the code that would need > > to be modified for decrypting/encrypting??? > > The tricky part is the journal, do you want to protect the journal as well? > Inodes written to the journal in a different format from the on disk format. And the swap partition needs also be protected; otherwise your precious data could easily end up clear text there. -Andi From owner-linux-xfs@oss.sgi.com Thu Jul 5 09:21:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65GLra21315 for linux-xfs-outgoing; Thu, 5 Jul 2001 09:21:53 -0700 Received: from m1.debitech.com ([212.209.112.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65GLoV21311 for ; Thu, 5 Jul 2001 09:21:51 -0700 Received: (qmail 16266 invoked from network); 5 Jul 2001 16:23:08 -0000 Received: from mail.debitech.com (HELO debitech11.debitech.com) (212.209.112.12) by m1.debitech.com with SMTP; 5 Jul 2001 16:23:08 -0000 Received: by DEBITECH11 with Internet Mail Service (5.5.2650.21) id ; Thu, 5 Jul 2001 18:22:57 +0200 Message-ID: <47CB5BFBF511D411A3AC00508BC8636B267BD4@DEBITECH11> From: Stephen Brewer To: "'linux-xfs@oss.sgi.com'" Subject: RE: encryption Date: Thu, 5 Jul 2001 18:22:57 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk if i understand things correctly the journal is empty when the filesystem is unmounted, if this is the case then the data is not protected after a crash, this is something to live with... what is more important is the swap partition(s)... i guess a change to the unmount code for swaps could clean the partitions but this could take time when waiting for a computer to shut down... leaving unencrypted data in the swap after the protected data has been unmounted... or encrypt the swap... slowing it down... hmmm decisions... steve... -----Original Message----- From: Steve Lord To: Stephen Brewer Cc: 'linux-xfs@oss.sgi.com' Sent: 7/5/01 5:41 PM Subject: Re: encryption > i am interested in encrypted filesystems and was wondering if xfs would be > good to encrypt... It might be a little tough! > > my thoughts was to intercept the reading/writing of inodes from/to disk and > doing the en-decryption there... > > the passphrase for the encryption would be entered during the mounting of > the filesystem (and deleted from memory during the unmount!)... > > so my questions... > > is there a technical reason why xfs is unsuitable for this??? > If you have an encryption algorithm which does not change the size of the information, i.e. the encrypted data takes the same number of bytes as the non-encrypted data, then things are a lot easier. My memory of encryption says that this is not normally the case unless you are using very basic algorithms which are easy to crack. Once your algorithm changes the size of data it gets really hard to deal with managing disk layout. > has anybody thought about this before??? > > i have found a method called 'xfs_iflush_int' does all writing to the hard > disk go through here, or are there many places in the code that would need > to be modified for decrypting/encrypting??? The tricky part is the journal, do you want to protect the journal as well? Inodes written to the journal in a different format from the on disk format. XFS has in memory and on disk inodes, the on disk format is mapped to the internal format when we read in the buffer and the internal format is mapped back again when we write it out. So in principal there are not many places you need to change things, provided the disk layout does not have to change. > > is this a stupid idea??? :) Stupid no, ambitious yes. Steve > > steve... > > ps i hope this is the right place to send this message... > pps is there anybody else interesed??? From owner-linux-xfs@oss.sgi.com Thu Jul 5 09:31:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65GV4i21646 for linux-xfs-outgoing; Thu, 5 Jul 2001 09:31:04 -0700 Received: from m1.debitech.com ([212.209.112.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65GV1V21643 for ; Thu, 5 Jul 2001 09:31:01 -0700 Received: (qmail 16430 invoked from network); 5 Jul 2001 16:32:18 -0000 Received: from mail.debitech.com (HELO debitech11.debitech.com) (212.209.112.12) by m1.debitech.com with SMTP; 5 Jul 2001 16:32:18 -0000 Received: by DEBITECH11 with Internet Mail Service (5.5.2650.21) id ; Thu, 5 Jul 2001 18:32:08 +0200 Message-ID: <47CB5BFBF511D411A3AC00508BC8636B267BD5@DEBITECH11> From: Stephen Brewer To: "'linux-xfs@oss.sgi.com'" Subject: RE: encryption Date: Thu, 5 Jul 2001 18:32:02 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk i agree with the blocksize... i did think that i might have to force an inode size to match the encryption size... or vice versa... (not sure if i mean inode size here... still learning!!!) the benefit of encrypting the the inodes is that everything on the filesystem is encrypted... directorynames, filenames, the data in the files... all for the price of encrypting the data at such a low level... (i think???) i dont like loopback encryption... i guess it is mostly personal (or lack of knowledge)... but why attach encryption to a filesystem, would it not be faster safer to embed the security into the filesystem... steve... -----Original Message----- From: Andi Kleen To: Steve Lord Cc: Stephen Brewer; 'linux-xfs@oss.sgi.com' Sent: 7/5/01 6:00 PM Subject: Re: encryption On Thu, Jul 05, 2001 at 10:41:09AM -0500, Steve Lord wrote: > If you have an encryption algorithm which does not change the size of > the information, i.e. the encrypted data takes the same number of > bytes as the non-encrypted data, then things are a lot easier. My > memory of encryption says that this is not normally the case unless > you are using very basic algorithms which are easy to crack. > Once your algorithm changes the size of data it gets really hard to > deal with managing disk layout. If your data is a multiply of the block cipher blocksize (normally 16 bytes on a AES style cipher or 8 bytes for DES) then the data size doesn't change. If it's not a multiple of a good block cipher size an stream cipher could be also used, which does not operate in fixed blocks (at least not blocks bigger than a byte); but it requires more complicated key management because you cannot reuse the key for two different disk blocks. As far as I can see all data structures in XFS on disk should be multiplies of 16 bytes. BTW; Linux already has an existing encryption interface for file systems via the loopback device; unfortunately the existing encryption modules all have various drawbacks and problems. This works only per block device of course and it is relatively hard to store any metadata which means e.g. it is impossible to check the user's password. An XFS based per file encryption mechanism would be definitely interesting. One problem is how to specify the password per file without having to patch all applications. I'm not sure why the inodes should be encrypted though (they really do not contain much sensitive data and encrypted inodes would make backup really hard); wouldn't it make more sense to encrypt directories and file data only? > > > has anybody thought about this before??? > > > > i have found a method called 'xfs_iflush_int' does all writing to the hard > > disk go through here, or are there many places in the code that would need > > to be modified for decrypting/encrypting??? > > The tricky part is the journal, do you want to protect the journal as well? > Inodes written to the journal in a different format from the on disk format. And the swap partition needs also be protected; otherwise your precious data could easily end up clear text there. -Andi From owner-linux-xfs@oss.sgi.com Thu Jul 5 10:08:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65H8LC22426 for linux-xfs-outgoing; Thu, 5 Jul 2001 10:08:21 -0700 Received: from itcampus.de (www.itcampus.de [194.45.97.156]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65H8JV22423 for ; Thu, 5 Jul 2001 10:08:19 -0700 Received: from [62.208.91.225] (HELO itcampus.de) by itcampus.de (CommuniGate Pro SMTP 3.3.1) with ESMTP id 112294 for linux-xfs@oss.sgi.com; Thu, 05 Jul 2001 19:09:39 +0200 Message-ID: <3B44880E.5CA02498@itcampus.de> Date: Thu, 05 Jul 2001 17:30:22 +0200 From: Thomas Winkler X-Mailer: Mozilla 4.76 [de] (X11; U; Linux 2.2.16 i686) X-Accept-Language: de, ex-MX MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: encryption References: <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> <0107051747210G.30268@asterix> <20010705175612.A27494@main.braxis.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Krzysztof Rusocki wrote: > > Hi Steve, > > you may also take a look at Loopback-Encrypted-Filesystem-HOWTO on www.linuxdoc.org , > you'll need to patch your kernel with encryption patch (available on > ftp.kernel.org afaik).. However i do not know how is it going to interact > with XFS - opinion of someone who did try to patch XFS tree with crypto > patch would really be needed here... i did some testing with xfs kernel and crypto patch from http://www.kerneli.org . i guess thats the one you are talking about. but i was not able to make a xfs filesystem on the loopback, since the encrypted filesystems are mounted on loopback device. it worked fine with ext2, but some errors on making the xfs. when i remember right i was able to mount the loopback, but could not write on it. i also can't remember the errors (been quite a while). if someone is interested a could do some more testing. right now i am using ext2 on my encrypted filesystems. greetings thomas -------------------------------------- itCampus Software- und Systemhaus GmbH Leipzig - Halle - Wittenberg http://www.itcampus.de From owner-linux-xfs@oss.sgi.com Thu Jul 5 10:18:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65HIdY22680 for linux-xfs-outgoing; Thu, 5 Jul 2001 10:18:39 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65HIaV22677 for ; Thu, 5 Jul 2001 10:18:37 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA07823 for ; Thu, 5 Jul 2001 10:18:35 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2350685; Thu, 5 Jul 2001 12:17:17 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA09835; Thu, 5 Jul 2001 12:17:17 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f65HJK002081; Thu, 5 Jul 2001 12:19:20 -0500 Message-Id: <200107051719.f65HJK002081@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Thomas Winkler cc: linux-xfs@oss.sgi.com Subject: Re: encryption In-Reply-To: Message from Thomas Winkler of "Thu, 05 Jul 2001 17:30:22 +0200." <3B44880E.5CA02498@itcampus.de> Date: Thu, 05 Jul 2001 12:19:19 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hmm, xfs does work on loopback normally. Steve > Krzysztof Rusocki wrote: > > > > Hi Steve, > > > > you may also take a look at Loopback-Encrypted-Filesystem-HOWTO on www.linu > xdoc.org , > > you'll need to patch your kernel with encryption patch (available on > > ftp.kernel.org afaik).. However i do not know how is it going to interact > > with XFS - opinion of someone who did try to patch XFS tree with crypto > > patch would really be needed here... > > i did some testing with xfs kernel and crypto patch from > http://www.kerneli.org . i guess thats the one you are talking about. > but i was not able to make a xfs filesystem on the loopback, since the > encrypted filesystems are mounted on loopback device. it worked fine > with ext2, but some errors on making the xfs. when i remember right i > was able to mount the loopback, but could not write on it. i also can't > remember the errors (been quite a while). > > if someone is interested a could do some more testing. right now i am > using ext2 on my encrypted filesystems. > > greetings > thomas > > -------------------------------------- > itCampus Software- und Systemhaus GmbH > Leipzig - Halle - Wittenberg > http://www.itcampus.de From owner-linux-xfs@oss.sgi.com Thu Jul 5 11:52:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65IqcN24390 for linux-xfs-outgoing; Thu, 5 Jul 2001 11:52:38 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65IqZV24387 for ; Thu, 5 Jul 2001 11:52:35 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip85.idcomm.com [209.60.72.212] (may be forged)) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f65Isul06778 for ; Thu, 5 Jul 2001 12:54:56 -0600 Message-ID: <3B44B7EA.4BF37EEA@idcomm.com> Date: Thu, 05 Jul 2001 12:54:34 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> <3B44775B.2D49BD6B@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > > "D. Stimits" wrote: > > > Are tags issued as standard practice at each sync? E.G., is there any > > problem with naming a tag to get the 2.4.6-pre3-xfs or 2.4.6-xfs at any > > time, despite the fast changes? (what tag name scheme is used?) > > I'll have to look into this, CVS is pushed out automatically from our > own internal source code management tools, and I'm not sure if the > concept of a CVS tag can make it from one to the other - it may take > some manual manipulation of the CVS tree. A few people have asked for > this, if there's a good way to do it, maybe we can get more diligent > about it. > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. A temporary workaround (which could actually work for quite a while) would be if a web page gave the time/date to use for date-based checkout. Even without explicit tags at each stage, if you know the date/time, you can check out "the most current as of date/time being xxx". What I'm not too certain of is whether there is any problem with dates and times being set differently on different machines. In the latter case, there'd have to be some sort of conversion by each person; if a single README.SGI.cvsversion file was created, and the person checking in the final cvs change that officially syncs with a known kernel release version has that information placed in the README as the final checkin act, then it would be someone easy to know if things had been retrieved correctly. The README could contain something as simple as: "This is the final checking for 2.4.7 pre1 before beginning 2.4.7 pre2." (and the time/date might be interesting) Then one could check out based on that time/date, and verify any timezone differences this way. Once the README is set, the first checkin after that should probably alter the README to something like this: "This is an intermediate revision building towards 2.4.7 pre2." D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:04:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65J4Df24653 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:04:13 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65J4AV24650 for ; Thu, 5 Jul 2001 12:04:11 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip85.idcomm.com [209.60.72.212] (may be forged)) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f65J6Il09146 for ; Thu, 5 Jul 2001 13:06:18 -0600 Message-ID: <3B44BA94.46BCE15B@idcomm.com> Date: Thu, 05 Jul 2001 13:05:56 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "'linux-xfs@oss.sgi.com'" Subject: Re: encryption References: <47CB5BFBF511D411A3AC00508BC8636B267BD3@DEBITECH11> <0107051747210G.30268@asterix> <20010705175612.A27494@main.braxis.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Krzysztof Rusocki wrote: > > Hi Steve, > > you may also take a look at Loopback-Encrypted-Filesystem-HOWTO on www.linuxdoc.org , > you'll need to patch your kernel with encryption patch (available on > ftp.kernel.org afaik).. However i do not know how is it going to interact > with XFS - opinion of someone who did try to patch XFS tree with crypto > patch would really be needed here... There is already XOR based loopback support in the kernel, but the international crypto patches have some technical problems, they are pretty much considered "bad code" on the kernel dev list. Two problems they cite quite often is that the international crypto fails to be written for reentrancy in a reentrant portion of the kernel, as well as a hard coded requirement of a single block size (permanent assumption). Another minor complaint there is that the code should be user space and not a kernel patch. But in the end, you can bet the international crypto patch will never make it into the kernel as it is now. D. Stimits, stimits@idcomm.com > > Cheers, > Krzysztof > > On Thu, Jul 05, 2001 at 05:47:21PM +0200, Christian Widmer wrote: > > the idea is not new (exept using xfs maybe). the new suse7.2 distribution > > has support for encryted file system. and it looks like it does't matter what > > filesystem you use. there is a description on their german homepage, un- > > fortunately in germen. it uses the loop device to add an additional layer. > > > > setup a encryted device: > > $modprobe loop_fish2 > > $losetup -e twofish /dev/loop0 /dev/hda3 > > $mkdir /topsecret > > $mkreiserfs /dev/loop0 > > $mount -t reiserfs /dev/loop0 /topsecret > > > > //chris > > > > On Thursday 05 July 2001 17:18, you wrote: > > > i am interested in encrypted filesystems and was wondering if xfs would be > > > good to encrypt... > > > > > > my thoughts was to intercept the reading/writing of inodes from/to disk and > > > doing the en-decryption there... > > > > > > the passphrase for the encryption would be entered during the mounting of > > > the filesystem (and deleted from memory during the unmount!)... > > > > > > so my questions... > > > > > > is there a technical reason why xfs is unsuitable for this??? > > > > > > has anybody thought about this before??? > > > > > > i have found a method called 'xfs_iflush_int' does all writing to the hard > > > disk go through here, or are there many places in the code that would need > > > to be modified for decrypting/encrypting??? > > > > > > is this a stupid idea??? :) > > > > > > steve... > > > > > > ps i hope this is the right place to send this message... > > > pps is there anybody else interesed??? > > > > -- > > christian widmer > > zurlindenstrasse 294, 8003 zurich, switzerland > > email: cwidmer@iiic.ethz.ch > > phone: ++41 (0)1 491 03 68 From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:05:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65J5Ww24756 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:05:32 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65J5VV24753 for ; Thu, 5 Jul 2001 12:05:31 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA01855 for ; Thu, 5 Jul 2001 12:05:24 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA25683 for ; Thu, 5 Jul 2001 14:04:15 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15IEQ9-0000oq-00 for ; Thu, 05 Jul 2001 14:04:13 -0500 Date: Thu, 5 Jul 2001 14:04:13 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Patch Message-ID: <20010705140413.D883@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> <3B44775B.2D49BD6B@sgi.com> <3B44B7EA.4BF37EEA@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B44B7EA.4BF37EEA@idcomm.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 12:54:34PM -0600, D. Stimits wrote: > A temporary workaround (which could actually work for quite a while) > would be if a web page gave the time/date to use for date-based > checkout. Even without explicit tags at each stage, if you know the > date/time, you can check out "the most current as of date/time being > xxx". You should be able to do this already. Each "TAKE" message already included the date and time of the TAKE (a.k.a. commit). Just pick a time after that and before the next sync with Linus and you should have the kernel version you're looking for. So to get 2.4.6, you can use the date "Wed Jul 4 22:00:00 PDT 2001." You're going to have to look up how to mangle this date into the format CVS wants, but theoretically anyone should be able to do that. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:17:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65JHWf25177 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:17:32 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JHUV25174 for ; Thu, 5 Jul 2001 12:17:30 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA08836 for ; Thu, 5 Jul 2001 12:14:49 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA97221 for ; Thu, 5 Jul 2001 12:21:52 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 6416115A46B for ; Thu, 5 Jul 2001 12:16:13 -0700 (PDT) Subject: release 1.0.1-PR3 and AIC-78xx again :-( From: Florin Andrei To: linux-xfs@oss.sgi.com Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 05 Jul 2001 12:16:13 -0700 Message-Id: <994360573.12154.10.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ok, i try to install Release 1.0.1-PR3 on a SGI 1100 with on-board aic7xxx controller and a DAC960 RAID card. While booting the bootnet.img floppy, the system is totally frozen while loading the aic7xxx driver. Or maybe just before loading the DAC module? I'm not quite sure. I see a bunch of messages from the aic7xxx driver, then BANG! only the Reset button works. :-( I'll try some more things and i'll let you know. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:21:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65JL6X25315 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:21:06 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JL3V25312 for ; Thu, 5 Jul 2001 12:21:03 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip85.idcomm.com [209.60.72.212] (may be forged)) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f65JNPl12454 for ; Thu, 5 Jul 2001 13:23:25 -0600 Message-ID: <3B44BE97.5314932F@idcomm.com> Date: Thu, 05 Jul 2001 13:23:03 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> <3B44775B.2D49BD6B@sgi.com> <3B44B7EA.4BF37EEA@idcomm.com> <20010705140413.D883@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Straz wrote: > > On Thu, Jul 05, 2001 at 12:54:34PM -0600, D. Stimits wrote: > > A temporary workaround (which could actually work for quite a while) > > would be if a web page gave the time/date to use for date-based > > checkout. Even without explicit tags at each stage, if you know the > > date/time, you can check out "the most current as of date/time being > > xxx". > > You should be able to do this already. Each "TAKE" message already > included the date and time of the TAKE (a.k.a. commit). Just pick a > time after that and before the next sync with Linus and you should have > the kernel version you're looking for. > > So to get 2.4.6, you can use the date "Wed Jul 4 22:00:00 PDT 2001." > You're going to have to look up how to mangle this date into the format > CVS wants, but theoretically anyone should be able to do that. > > -- > Nate Straz nstraz@sgi.com > sgi, inc http://www.sgi.com/ > Linux Test Project http://ltp.sf.net/ Maybe this is already provided, but could the "TAKE" messages be made available via web page? Saving all the email is a bit of a problem; I, for one, recently lost all of my email due to a Netscape problem (pointed at an ext2 partition). And in the past I have lost email for other reasons, including POP3 death. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:25:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65JP3G25442 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:25:03 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JP1V25439 for ; Thu, 5 Jul 2001 12:25:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA06075 for ; Thu, 5 Jul 2001 12:22:20 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2353867; Thu, 5 Jul 2001 14:23:44 -0500 (CDT) Received: from sgi.com (lite.americas.sgi.com [128.162.187.4]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA44935; Thu, 5 Jul 2001 14:23:45 -0500 (CDT) Message-ID: <3B44BE49.D8F21386@sgi.com> Date: Thu, 05 Jul 2001 14:21:45 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3smp i686) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs@oss.sgi.com Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> <3B44775B.2D49BD6B@sgi.com> <3B44B7EA.4BF37EEA@idcomm.com> <20010705140413.D883@sgi.com> <3B44BE97.5314932F@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > Maybe this is already provided, but could the "TAKE" messages be made > available via web page? Already there, see the mailing list archives. -Eric From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:29:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65JTp825700 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:29:51 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JToV25694 for ; Thu, 5 Jul 2001 12:29:50 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA04869 for ; Thu, 5 Jul 2001 12:29:43 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA01544 for ; Thu, 5 Jul 2001 12:34:13 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 7DD4115A46B for ; Thu, 5 Jul 2001 12:28:34 -0700 (PDT) Subject: Re: release 1.0.1-PR3 and AIC-78xx again :-( From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <994360573.12154.10.camel@stantz.corp.sgi.com> References: <994360573.12154.10.camel@stantz.corp.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 05 Jul 2001 12:28:34 -0700 Message-Id: <994361314.12166.13.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05 Jul 2001 12:16:13 -0700, Florin Andrei wrote: > While booting the bootnet.img floppy, the system is totally frozen while > loading the aic7xxx driver. Or maybe just before loading the DAC module? > I'm not quite sure. I see a bunch of messages from the aic7xxx driver, > then BANG! only the Reset button works. :-( Now i tried "text noprobe ks=floppy", in order to manually insert the drivers. But, for some reason, if i put "noprobe" then the kickstart installer is dropped, and i get manual install instead! -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:36:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Ja0O25936 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:36:00 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JZwV25933 for ; Thu, 5 Jul 2001 12:35:58 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA1058140 for ; Thu, 5 Jul 2001 21:35:56 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2346160; Thu, 5 Jul 2001 14:34:39 -0500 (CDT) Received: from sgi.com (lite.americas.sgi.com [128.162.187.4]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA65196; Thu, 5 Jul 2001 14:34:39 -0500 (CDT) Message-ID: <3B44C0D8.4952C7EF@sgi.com> Date: Thu, 05 Jul 2001 14:32:40 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Florin Andrei CC: linux-xfs@oss.sgi.com Subject: Re: release 1.0.1-PR3 and AIC-78xx again :-( References: <994360573.12154.10.camel@stantz.corp.sgi.com> <994361314.12166.13.camel@stantz.corp.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei wrote: > Now i tried "text noprobe ks=floppy", in order to manually insert the > drivers. But, for some reason, if i put "noprobe" then the kickstart > installer is dropped, and i get manual install instead! I'm not that familiar with a "noprobe" install, but doesn't it sort of follow that if you have to _manually_ insert drivers, then you cannot do an _automated_ kickstart install? -Eric From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:38:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Jcnf26085 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:38:49 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JckV26082 for ; Thu, 5 Jul 2001 12:38:46 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA06078 for ; Thu, 5 Jul 2001 12:38:38 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA20207 for ; Thu, 5 Jul 2001 14:37:30 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15IEwK-0000rN-00 for ; Thu, 05 Jul 2001 14:37:28 -0500 Date: Thu, 5 Jul 2001 14:37:27 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Patch Message-ID: <20010705143727.E883@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> <3B44775B.2D49BD6B@sgi.com> <3B44B7EA.4BF37EEA@idcomm.com> <20010705140413.D883@sgi.com> <3B44BE97.5314932F@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B44BE97.5314932F@idcomm.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 01:23:03PM -0600, D. Stimits wrote: > Maybe this is already provided, but could the "TAKE" messages be made > available via web page? Saving all the email is a bit of a problem; I, > for one, recently lost all of my email due to a Netscape problem > (pointed at an ext2 partition). And in the past I have lost email for > other reasons, including POP3 death. http://oss.sgi.com/projects/xfs/ml.html Or do you mean a page with just a summary of all the TAKE messages? -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:41:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65JfAs26200 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:41:10 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65Jf6V26197 for ; Thu, 5 Jul 2001 12:41:07 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA1067659 for ; Thu, 5 Jul 2001 21:41:04 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA62861 for ; Thu, 5 Jul 2001 12:45:19 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 9463315A46B for ; Thu, 5 Jul 2001 12:39:40 -0700 (PDT) Subject: Re: release 1.0.1-PR3 and AIC-78xx again :-( From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <3B44C0D8.4952C7EF@sgi.com> References: <994360573.12154.10.camel@stantz.corp.sgi.com> <994361314.12166.13.camel@stantz.corp.sgi.com> <3B44C0D8.4952C7EF@sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 05 Jul 2001 12:39:40 -0700 Message-Id: <994361980.12166.15.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05 Jul 2001 14:32:40 -0500, Eric Sandeen wrote: > Florin Andrei wrote: > > > Now i tried "text noprobe ks=floppy", in order to manually insert the > > drivers. But, for some reason, if i put "noprobe" then the kickstart > > installer is dropped, and i get manual install instead! > > I'm not that familiar with a "noprobe" install, but doesn't it sort of > follow that if you have to _manually_ insert drivers, then you cannot do > an _automated_ kickstart install? Yeah, it absolutely makes sense, but sometimes it's useful to be able to override this. Like, for example, in my case. Anyway, is there any possible solution for the aic7xxx problem in the new release? Please, this is a long standing issue... Thanks. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:46:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Jkuh26456 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:46:56 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JksV26452 for ; Thu, 5 Jul 2001 12:46:54 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id MAA09602 for ; Thu, 5 Jul 2001 12:46:53 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA61399 for ; Thu, 5 Jul 2001 12:51:15 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 2B3D015A46B for ; Thu, 5 Jul 2001 12:45:37 -0700 (PDT) Subject: Re: release 1.0.1-PR3 and AIC-78xx again :-( From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <994360573.12154.10.camel@stantz.corp.sgi.com> References: <994360573.12154.10.camel@stantz.corp.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 05 Jul 2001 12:45:37 -0700 Message-Id: <994362337.12154.16.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05 Jul 2001 12:16:13 -0700, Florin Andrei wrote: > While booting the bootnet.img floppy, the system is totally frozen while > loading the aic7xxx driver. Or maybe just before loading the DAC module? > I'm not quite sure. I see a bunch of messages from the aic7xxx driver, > then BANG! only the Reset button works. :-( Ok, now i know what the problem is: I'm trying to install PR3 manually (no kickstart), and do not attempt to autodetect devices (this way i can avoid loading aic7xxx). When i specify to load the DAC960 driver - it's totally frozen! So, it's not aic7xxx, it's DAC960. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 5 12:47:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65JlxU26551 for linux-xfs-outgoing; Thu, 5 Jul 2001 12:47:59 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65JlwV26548 for ; Thu, 5 Jul 2001 12:47:58 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip85.idcomm.com [209.60.72.212] (may be forged)) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f65JoKl17680 for ; Thu, 5 Jul 2001 13:50:20 -0600 Message-ID: <3B44C4E6.D0B70A9B@idcomm.com> Date: Thu, 05 Jul 2001 13:49:58 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: Patch References: <29784.994311805@kao2.melbourne.sgi.com> <3B443207.6A6E7E44@idcomm.com> <3B44775B.2D49BD6B@sgi.com> <3B44B7EA.4BF37EEA@idcomm.com> <20010705140413.D883@sgi.com> <3B44BE97.5314932F@idcomm.com> <20010705143727.E883@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Straz wrote: > > On Thu, Jul 05, 2001 at 01:23:03PM -0600, D. Stimits wrote: > > Maybe this is already provided, but could the "TAKE" messages be made > > available via web page? Saving all the email is a bit of a problem; I, > > for one, recently lost all of my email due to a Netscape problem > > (pointed at an ext2 partition). And in the past I have lost email for > > other reasons, including POP3 death. > > http://oss.sgi.com/projects/xfs/ml.html > > Or do you mean a page with just a summary of all the TAKE messages? Yes, just TAKE messages. Basically a _small_ subset of messages. D. Stimits, stimits@idcomm.com > > -- > Nate Straz nstraz@sgi.com > sgi, inc http://www.sgi.com/ > Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 14:08:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65L8Wl01439 for linux-xfs-outgoing; Thu, 5 Jul 2001 14:08:32 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65L8UV01435 for ; Thu, 5 Jul 2001 14:08:30 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id OAA02062 for ; Thu, 5 Jul 2001 14:05:49 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2351310 for ; Thu, 5 Jul 2001 16:07:12 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA16316 for ; Thu, 5 Jul 2001 16:07:12 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f65L9DP32726; Thu, 5 Jul 2001 16:09:13 -0500 Message-Id: <200107052109.f65L9DP32726@jen.americas.sgi.com> Date: Thu, 5 Jul 2001 16:09:13 -0500 Subject: TAKE - merge up to 2.4.7-pre3 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mostly scsi updates, a deadlock fix in the latest memory allocation code, and a fix which makes fbcon.c compile again. Date: Thu Jul 5 14:03:50 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-base The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98280a linux/mm/vmscan.c - 1.62 linux/init/main.c - 1.57 linux/include/linux/serialP.h - 1.14 linux/fs/inode.c - 1.45 linux/fs/dcache.c - 1.26 linux/drivers/video/fbcon.c - 1.20 linux/drivers/scsi/sym53c8xx_defs.h - 1.9 linux/drivers/scsi/sym53c8xx.c - 1.25 linux/drivers/scsi/st.c - 1.29 linux/drivers/scsi/sr_vendor.c - 1.9 linux/drivers/scsi/sr_ioctl.c - 1.16 linux/drivers/scsi/sr.c - 1.26 linux/drivers/scsi/sd.c - 1.37 linux/drivers/scsi/scsi_obsolete.c - 1.11 linux/drivers/scsi/scsi_ioctl.c - 1.19 linux/drivers/scsi/scsi_error.c - 1.19 linux/drivers/scsi/scsi.h - 1.19 linux/drivers/scsi/scsi.c - 1.37 linux/drivers/scsi/qlogicpti.c - 1.14 linux/drivers/scsi/qlogicisp.c - 1.22 linux/drivers/scsi/ncr53c8xx.c - 1.21 linux/drivers/scsi/hosts.h - 1.17 linux/drivers/scsi/hosts.c - 1.25 linux/drivers/scsi/README.ncr53c8xx - 1.5 linux/drivers/scsi/README.aic7xxx - 1.6 linux/drivers/scsi/FlashPoint.c - 1.3 linux/drivers/scsi/Config.in - 1.22 linux/drivers/scsi/ChangeLog.sym53c8xx - 1.13 linux/drivers/scsi/ChangeLog.ncr53c8xx - 1.11 linux/drivers/scsi/BusLogic.h - 1.6 linux/drivers/scsi/BusLogic.c - 1.12 linux/drivers/char/serial.c - 1.41 linux/arch/i386/kernel/setup.c - 1.48 linux/arch/i386/boot/video.S - 1.7 linux/Makefile - 1.100 linux/drivers/scsi/dec_esp.c - 1.5 linux/drivers/scsi/scsi_merge.c - 1.28 linux/drivers/scsi/scsi_lib.c - 1.31 linux/drivers/scsi/scsi_scan.c - 1.16 linux/drivers/scsi/sym53c8xx_comm.h - 1.8 linux/drivers/scsi/aic7xxx_old/aic7xxx_seq.c - 1.2 linux/drivers/scsi/aic7xxx_old/aic7xxx_reg.h - 1.2 linux/drivers/scsi/aic7xxx_old/aic7xxx_proc.c - 1.2 linux/drivers/scsi/aic7xxx_old/aic7xxx.seq - 1.3 linux/drivers/scsi/aic7xxx_old/aic7xxx.reg - 1.3 linux/drivers/scsi/aic7xxx_old/README.aic7xxx - 1.2 linux/drivers/scsi/aic7xxx_old.c - 1.4 linux/drivers/scsi/aic7xxx/aic7xxx_linux_pci.c - 1.3 From owner-linux-xfs@oss.sgi.com Thu Jul 5 14:42:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Lggd03909 for linux-xfs-outgoing; Thu, 5 Jul 2001 14:42:42 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65LgeV03902 for ; Thu, 5 Jul 2001 14:42:40 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id XAA32629; Thu, 5 Jul 2001 23:41:38 +0200 Date: Thu, 5 Jul 2001 23:41:37 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Andi Kleen Cc: kris buggenhout , Fang Han , "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? Message-ID: <20010705234137.E28075@vestdata.no> References: <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> <20010705101747.A32674@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <20010705101747.A32674@gruyere.muc.suse.de>; from Andi Kleen on Thu, Jul 05, 2001 at 10:17:47AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 10:17:47AM +0200, Andi Kleen wrote: > All block devices in a XFS kernel need a special patch to add an ioctl > to set the logical block size. The original poster probably didn't add > that ioctl to his new hacked in LVM; which will cause all kinds of > problems with xfs user tools and also probably file system corruption. Is there a patch to add this ioctl to lvm? Exactly what filesystem corruption will it cause, and under what circumstances? If this is serious, maybe mkfs.xfs should refuse to build a filesystem on a device that doesn't support the ioctl? -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Thu Jul 5 14:45:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65LjfS04243 for linux-xfs-outgoing; Thu, 5 Jul 2001 14:45:41 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65LjeV04239 for ; Thu, 5 Jul 2001 14:45:40 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 83C211E6E3; Thu, 5 Jul 2001 23:45:34 +0200 (MEST) Date: Thu, 5 Jul 2001 23:45:32 +0200 From: Andi Kleen To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= Cc: Andi Kleen , kris buggenhout , Fang Han , "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? Message-ID: <20010705234532.A16619@gruyere.muc.suse.de> References: <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> <20010705101747.A32674@gruyere.muc.suse.de> <20010705234137.E28075@vestdata.no> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20010705234137.E28075@vestdata.no>; from xfs@ragnark.vestdata.no on Thu, Jul 05, 2001 at 11:41:37PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 11:41:37PM +0200, Ragnar Kjørstad wrote: > On Thu, Jul 05, 2001 at 10:17:47AM +0200, Andi Kleen wrote: > > All block devices in a XFS kernel need a special patch to add an ioctl > > to set the logical block size. The original poster probably didn't add > > that ioctl to his new hacked in LVM; which will cause all kinds of > > problems with xfs user tools and also probably file system corruption. > > Is there a patch to add this ioctl to lvm? Yes, just diff the XFS tree against a Linus tree. > > Exactly what filesystem corruption will it cause, and under what > circumstances? fsck can corrupt the file system. > If this is serious, maybe mkfs.xfs should refuse to build a filesystem > on a device that doesn't support the ioctl? Doesn't help, it depends on the running kernel which is a variable. fsck should probably refuse to run, but it currently doesn't I think. -Andi From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:13:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65MDQH06703 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:13:26 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65MDOV06700 for ; Thu, 5 Jul 2001 15:13:25 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip36.idcomm.com [209.60.72.163]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f65MFml13774 for ; Thu, 5 Jul 2001 16:15:48 -0600 Message-ID: <3B44E6FE.DCB78DE5@idcomm.com> Date: Thu, 05 Jul 2001 16:15:26 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: aid to iso download Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Being that the ISO images are rather large, it might be nice to have a duplicate of each current ISO available that is the gzip version. gzip is suggested instead of bzip2 because gzip can be decompressed with standard tools on most any machine, including with winzip on windows (unfortunately, I'm one of those people that do not have access to a burner on a linux machine). I'd strongly recommend using "gzip -9" since maximum compression is important. With 300 MB files, it'll probably take some time for compression to complete, but imagine how much it'll pay off against a slow Internet download. I'm hoping to set a slow computer downloading tonight from a windows machine, so I suspect compression could cut down the time by many hours. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:22:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65MMRX07444 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:22:27 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65MMQV07439 for ; Thu, 5 Jul 2001 15:22:26 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA03539 for ; Thu, 5 Jul 2001 15:19:45 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id RAA18099 for ; Thu, 5 Jul 2001 17:21:09 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15IHUh-00015x-00 for ; Thu, 05 Jul 2001 17:21:07 -0500 Date: Thu, 5 Jul 2001 17:21:06 -0500 From: Nathan Straz To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download Message-ID: <20010705172106.I883@sgi.com> Mail-Followup-To: "XFS: linux-xfs@oss.sgi.com" References: <3B44E6FE.DCB78DE5@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B44E6FE.DCB78DE5@idcomm.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > Being that the ISO images are rather large, it might be nice to have a > duplicate of each current ISO available that is the gzip version. Here's an old FTP trick, append a .gz to any filename on an FTP site and the FTP server will gzip it for you. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:34:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65MYB308258 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:34:11 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65MY8V08254 for ; Thu, 5 Jul 2001 15:34:09 -0700 Received: (qmail 16120 invoked from network); 5 Jul 2001 22:34:03 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 5 Jul 2001 22:34:03 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: linux-xfs@oss.sgi.com cc: yahya@cbn.net.id Reply-To: yahya@cbn.net.id Subject: Cannot mount XFS filessytem (fwd) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jul 2001 08:34:02 +1000 Message-ID: <3167.994372442@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Forwarded to XFS list, please cc yahya@cbn.net.id, not kaos. ------- Forwarded Message Date: Fri, 06 Jul 2001 04:23:54 +0700 To: ananth@sgi.com, kaos@melbourne.sgi.com From: Yahya Hi, I'm not on the list because my mail crash. I got this error in my box, using kernel 2.4.5: [root@home3 /]# mount /dev/rd/c0d0p1 /home/ mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d0p1, or too many mounted file systems - -- from /var/log/messages: Start mounting filesystem: dac960(48,1) Starting XFS recovery on filesystem: dac960(48,1) (dev: 48/1) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed Start mounting filesystem: dac960(48,1) Starting XFS recovery on filesystem: dac960(48,1) (dev: 48/1) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed How to overcome this problem? thanks. Regards. Yahya. ------- End of Forwarded Message From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:38:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65McX708709 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:38:33 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65McWV08703 for ; Thu, 5 Jul 2001 15:38:32 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip36.idcomm.com [209.60.72.163]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f65Merl18689; Thu, 5 Jul 2001 16:40:53 -0600 Message-ID: <3B44ECDF.70BC38A1@idcomm.com> Date: Thu, 05 Jul 2001 16:40:31 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nathan Straz CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Straz wrote: > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > Being that the ISO images are rather large, it might be nice to have a > > duplicate of each current ISO available that is the gzip version. > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > the FTP server will gzip it for you. > > -- > Nate Straz nstraz@sgi.com > sgi, inc http://www.sgi.com/ > Linux Test Project http://ltp.sf.net/ That is a nice trick. But one other thing...I doubt it would use the -9 for maximum compression. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:39:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Md5x08833 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:39:05 -0700 Received: from corp1.cbn.net.id (corp1.cbn.net.id [202.158.3.24]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65Md3V08826 for ; Thu, 5 Jul 2001 15:39:04 -0700 Received: from navajo.cbn.net.id (unknown [202.158.50.85]) by corp1.cbn.net.id (Postfix) with ESMTP id 467E568A70 for ; Fri, 6 Jul 2001 05:38:55 +0700 (JAVT) Message-Id: <5.1.0.14.2.20010706053818.031220e0@pop.cbn.net.id> X-Sender: yahya@pop.cbn.net.id X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 06 Jul 2001 05:39:20 +0700 To: linux-xfs@oss.sgi.com From: Yahya Subject: Help Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I got this error in my box, using kernel 2.4.5: [root@home3 /]# mount /dev/rd/c0d0p1 /home/ mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d0p1, or too many mounted file systems -- from /var/log/messages: Start mounting filesystem: dac960(48,1) Starting XFS recovery on filesystem: dac960(48,1) (dev: 48/1) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed Start mounting filesystem: dac960(48,1) Starting XFS recovery on filesystem: dac960(48,1) (dev: 48/1) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed how to recover the filesystem? thanks. Regards. Yahya. From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:42:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65MgMT09237 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:42:22 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65MgLV09234 for ; Thu, 5 Jul 2001 15:42:21 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f65MgKNe061541 for ; Thu, 5 Jul 2001 17:42:20 -0500 (CDT) Message-ID: <3B44ED39.20CF57C3@thebarn.com> Date: Thu, 05 Jul 2001 17:42:01 -0500 From: cattelan@thebarn.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Straz wrote: > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > Being that the ISO images are rather large, it might be nice to have a > > duplicate of each current ISO available that is the gzip version. > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > the FTP server will gzip it for you. > Good idea (I'll check to make sure oss is configed to do this) but I doubt this will save space, every file on the iso is already compressed. So about the only space to be gained would be in the cd9660 file system, which I very small to start with. > > -- > Nate Straz nstraz@sgi.com > sgi, inc http://www.sgi.com/ > Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:43:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65MhO809366 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:43:24 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65MhNV09361 for ; Thu, 5 Jul 2001 15:43:23 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA04681 for ; Thu, 5 Jul 2001 15:40:42 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id RAA26195 for ; Thu, 5 Jul 2001 17:42:06 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15IHoy-00018X-00 for ; Thu, 05 Jul 2001 17:42:04 -0500 Date: Thu, 5 Jul 2001 17:42:04 -0500 From: Nathan Straz To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download Message-ID: <20010705174204.J883@sgi.com> Mail-Followup-To: "XFS: linux-xfs@oss.sgi.com" References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ECDF.70BC38A1@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B44ECDF.70BC38A1@idcomm.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 04:40:31PM -0600, D. Stimits wrote: > Nathan Straz wrote: > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > > the FTP server will gzip it for you. > > That is a nice trick. But one other thing...I doubt it would use the -9 > for maximum compression. nstraz@maine /tmp% file RH7.1-SGI-XFS-1.0.iso.gz RH7.1-SGI-XFS-1.0.iso.gz: gzip compressed data, deflated, original filename, `RH7.1-SGI-XFS-1.0.iso', last modified: Fri Apr 27 20:16:35 2001, max compression, os: Unix -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 15:50:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Mohp09911 for linux-xfs-outgoing; Thu, 5 Jul 2001 15:50:43 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65MogV09907 for ; Thu, 5 Jul 2001 15:50:42 -0700 Received: from postofc.csd.sgi.com (postofc.csd.sgi.com [130.62.75.23]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA04889 for ; Thu, 5 Jul 2001 15:50:41 -0700 (PDT) mail_from (alambie@csd.sgi.com) Received: from localhost.localdomain (sshgate.corp.sgi.com [169.238.216.146]) by postofc.csd.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id PAA83612 for ; Thu, 5 Jul 2001 15:50:40 -0700 (PDT) Subject: Re: aid to iso download From: Alistair Lambie To: linux-xfs@oss.sgi.com In-Reply-To: <3B44ED39.20CF57C3@thebarn.com> References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ED39.20CF57C3@thebarn.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 06 Jul 2001 10:50:39 +1200 Message-Id: <994373441.5295.13.camel@ajllinux.wellington.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05 Jul 2001 17:42:01 -0500, cattelan@thebarn.com wrote: > Nathan Straz wrote: > > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > > Being that the ISO images are rather large, it might be nice to have a > > > duplicate of each current ISO available that is the gzip version. > > > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > > the FTP server will gzip it for you. > > > > Good idea (I'll check to make sure oss is configed to do this) > but I doubt this will save space, > every file on the iso is already compressed. > So about the only space to be gained would be in > the cd9660 file system, which I very small to start with. > I thought it wouldn't save much either, but I just did it on RH7.1-SGI-XFS-1.0.iso and it went from 299MB to 221MB. -- Alistair Lambie alambie@sgi.com SGI Global Product Support Phone: +64-21-635 262 New Zealand Fax: +64-4-234 8792 From owner-linux-xfs@oss.sgi.com Thu Jul 5 16:10:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65NA0V11695 for linux-xfs-outgoing; Thu, 5 Jul 2001 16:10:00 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65N9xV11690 for ; Thu, 5 Jul 2001 16:09:59 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Thu, 5 Jul 2001 16:07:38 -0700 Subject: minor typo in PR3 From: Thomas Duffy To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 05 Jul 2001 16:08:41 -0700 Message-Id: <994374521.32450.3.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 05 Jul 2001 23:07:38.0876 (UTC) FILETIME=[4931C3C0:01C105A7] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk at the first screen before kernel boots on the CD (the syslinux screen), it says GI XFS system RedHat 7.1... missing the "S". -tduffy From owner-linux-xfs@oss.sgi.com Thu Jul 5 16:13:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65NDoP12381 for linux-xfs-outgoing; Thu, 5 Jul 2001 16:13:50 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65NDmV12374 for ; Thu, 5 Jul 2001 16:13:49 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id BAA01814; Fri, 6 Jul 2001 01:13:26 +0200 Date: Fri, 6 Jul 2001 01:13:25 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Andi Kleen Cc: kris buggenhout , Fang Han , "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? Message-ID: <20010706011325.H28075@vestdata.no> References: <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> <20010705101747.A32674@gruyere.muc.suse.de> <20010705234137.E28075@vestdata.no> <20010705234532.A16619@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.95.5i In-Reply-To: <20010705234532.A16619@gruyere.muc.suse.de>; from Andi Kleen on Thu, Jul 05, 2001 at 11:45:32PM +0200 X-MIME-Autoconverted: from 8bit to quoted-printable by stine.vestdata.no id BAA01814 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f65NDnV12379 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 05, 2001 at 11:45:32PM +0200, Andi Kleen wrote: > On Thu, Jul 05, 2001 at 11:41:37PM +0200, Ragnar Kjørstad wrote: > > On Thu, Jul 05, 2001 at 10:17:47AM +0200, Andi Kleen wrote: > > > All block devices in a XFS kernel need a special patch to add an ioctl > > > to set the logical block size. The original poster probably didn't add > > > that ioctl to his new hacked in LVM; which will cause all kinds of > > > problems with xfs user tools and also probably file system corruption. > > > > Is there a patch to add this ioctl to lvm? > > Yes, just diff the XFS tree against a Linus tree. Now I'm confused. If the fix is in the XFS tree, why is it not in the XFS-patch? was the fix just commited? -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Thu Jul 5 16:25:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65NP7214448 for linux-xfs-outgoing; Thu, 5 Jul 2001 16:25:07 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65NP6V14442 for ; Thu, 5 Jul 2001 16:25:06 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Thu, 5 Jul 2001 16:22:45 -0700 Subject: scsi module sym53c8xx fails on 1.0.1 PR3 From: Thomas Duffy To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 05 Jul 2001 16:23:48 -0700 Message-Id: <994375428.32444.4.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 05 Jul 2001 23:22:45.0442 (UTC) FILETIME=[658CC220:01C105A9] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric, et al. I know this is probably not an XFS related thing, but a standard kernel breakage, but the sym53c8xx scsi module fails to load on 1.0.1 PR3 when booted off of the CD. This works fine with XFS 1.0 the module attempts to load and sits there spining on scsi timeouts. I cannot run the installer on this particular box without this module, so I will try to install with 1.0 and then boot off of new kernel or use a cvs version. -tduffy From owner-linux-xfs@oss.sgi.com Thu Jul 5 16:48:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Nmbk18417 for linux-xfs-outgoing; Thu, 5 Jul 2001 16:48:37 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65NmaV18410 for ; Thu, 5 Jul 2001 16:48:36 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15IIrC-000581-00; Fri, 06 Jul 2001 01:48:26 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f65NlrD02325; Thu, 5 Jul 2001 19:47:53 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Thomas Duffy Cc: linux-xfs@oss.sgi.com Subject: Re: scsi module sym53c8xx fails on 1.0.1 PR3 References: <994375428.32444.4.camel@tduffy-lnx.afara.com> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 05 Jul 2001 19:47:52 -0400 In-Reply-To: <994375428.32444.4.camel@tduffy-lnx.afara.com> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Tom" == Thomas Duffy writes: Tom> I know this is probably not an XFS related thing, but a standard Tom> kernel breakage, but the sym53c8xx scsi module fails to load on Tom> 1.0.1 PR3 when booted off of the CD. This works fine with XFS Tom> 1.0 Did PR3 installs on boxes with sym53c8xx modules both today and yesterday. Tried noapic? -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 16:49:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65Nn1D18573 for linux-xfs-outgoing; Thu, 5 Jul 2001 16:49:01 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65Nn0V18568 for ; Thu, 5 Jul 2001 16:49:00 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15IIqS-00057z-00; Fri, 06 Jul 2001 01:47:40 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f65NlAl02322; Thu, 5 Jul 2001 19:47:10 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Ragnar =?iso-8859-1?q?Kj=F8rstad?= Cc: "linux-xfs@oss.sgi.com" Subject: Re: When LVM-0.9.1beta7 will be merged to XFS cvs tree? References: <20010705151357.A2773@dfbbb.cn.mvd> <3B4417D5.ECDC1125@god.bel.alcatel.be> <20010705101747.A32674@gruyere.muc.suse.de> <20010705234137.E28075@vestdata.no> <20010705234532.A16619@gruyere.muc.suse.de> <20010706011325.H28075@vestdata.no> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 05 Jul 2001 19:47:10 -0400 In-Reply-To: <20010706011325.H28075@vestdata.no> Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Ragnar" == rstad writes: Ragnar> Now I'm confused. If the fix is in the XFS tree, why is it not Ragnar> in the XFS-patch? was the fix just commited? Fang Han had upgraded to LVM beta7, and the LVM patch procedure backs out our changes. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 16:49:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f65NnSD18741 for linux-xfs-outgoing; Thu, 5 Jul 2001 16:49:28 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f65NnRV18737 for ; Thu, 5 Jul 2001 16:49:27 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id QAA06459 for ; Thu, 5 Jul 2001 16:50:13 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id QAA67135; Thu, 5 Jul 2001 16:48:43 -0700 (PDT) Message-ID: <3B44FC36.CD9577FE@sgi.com> Date: Thu, 05 Jul 2001 18:45:58 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Duffy CC: linux-xfs@oss.sgi.com Subject: Re: minor typo in PR3 References: <994374521.32450.3.camel@tduffy-lnx.afara.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thomas Duffy wrote: > > at the first screen before kernel boots on the CD (the syslinux screen), > it says > > GI XFS system RedHat 7.1... > > missing the "S". The "S" got laid off last month... :) I'll fix it. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:08:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6608xO22296 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:08:59 -0700 Received: from groucho.maths.monash.edu.au (groucho.maths.monash.edu.au [130.194.160.211]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6608wV22285 for ; Thu, 5 Jul 2001 17:08:58 -0700 Received: (from rjh@localhost) by groucho.maths.monash.edu.au (8.8.8/8.8.8) id AAA22321 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 00:08:56 GMT From: Robin Humble Message-Id: <200107060008.AAA22321@groucho.maths.monash.edu.au> Subject: minor release notes bug in PR3 To: linux-xfs@oss.sgi.com Date: Fri, 6 Jul 2001 10:08:56 +1000 (EST) X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just a small bug: the release notes in PR3 (the ones you can read as it's installing) give you lots of info/warnings about devfs which shouldn't be there as devfs isn't turned on by default anymore. A PR3 install went very smoothly with no problems BTW. cheers, robin From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:09:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6609TO22432 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:09:29 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6609RV22423 for ; Thu, 5 Jul 2001 17:09:27 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id QAA03627 for ; Thu, 5 Jul 2001 16:53:50 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id QAA14923; Thu, 5 Jul 2001 16:52:20 -0700 (PDT) Message-ID: <3B44FD0F.456A3CA0@sgi.com> Date: Thu, 05 Jul 2001 18:49:35 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Duffy CC: linux-xfs@oss.sgi.com Subject: Re: scsi module sym53c8xx fails on 1.0.1 PR3 References: <994375428.32444.4.camel@tduffy-lnx.afara.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thomas Duffy wrote: > > Eric, et al. > > I know this is probably not an XFS related thing, but a standard kernel > breakage, but the sym53c8xx scsi module fails to load on 1.0.1 PR3 when > booted off of the CD. This works fine with XFS 1.0 > > the module attempts to load and sits there spining on scsi timeouts. I > cannot run the installer on this particular box without this module, so > I will try to install with 1.0 and then boot off of new kernel or use a > cvs version. Very odd... Since this is the Red Hat kernel, and it's not a rare scsi chipset, I'm surprised that there's a problem with it... Hrm. If you feel like experimenting, you might get the original 2.4.3-12 BOOT kernel from Red Hat, and see if it exhibits the same problem? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:16:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f660Gg323733 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:16:42 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f660GeV23730 for ; Thu, 5 Jul 2001 17:16:40 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id RAA21057 for ; Thu, 5 Jul 2001 17:16:33 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id RAA38099; Thu, 5 Jul 2001 17:16:08 -0700 (PDT) Message-ID: <3B4502A3.A6C942A6@sgi.com> Date: Thu, 05 Jul 2001 19:13:23 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Robin Humble CC: linux-xfs@oss.sgi.com Subject: Re: minor release notes bug in PR3 References: <200107060008.AAA22321@groucho.maths.monash.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Robin Humble wrote: > > Just a small bug: > the release notes in PR3 (the ones you can read as it's installing) > give you lots of info/warnings about devfs which shouldn't be there > as devfs isn't turned on by default anymore. Yep, I changed this today. PR3 was to get the code right, I didn't touch the docs. > A PR3 install went very smoothly with no problems BTW. Great! Thanks for the report... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:22:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f660M7524293 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:22:07 -0700 Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f660M6V24286 for ; Thu, 5 Jul 2001 17:22:06 -0700 Received: (qmail 28276 invoked by uid 0); 6 Jul 2001 00:21:58 -0000 Received: from b209e.pppool.de (HELO gmx.de) (213.7.32.158) by mail.gmx.net (mp008-rz3) with SMTP; 6 Jul 2001 00:21:58 -0000 Message-ID: <3B4504CC.BC1D3BAE@gmx.de> Date: Fri, 06 Jul 2001 02:22:36 +0200 From: Martin Stricker Organization: http://martin-stricker.de/ http://www.surfo.net/ http://www.masterportal24.com/cgi-bin/YaBB.cgi X-Mailer: Mozilla 4.75 [en]C-CCK-MCD BDP81800 (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ECDF.70BC38A1@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > > Nathan Straz wrote: > > > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > > Being that the ISO images are rather large, it might be nice to > > > have a duplicate of each current ISO available that is the gzip > > > version. > > > > Here's an old FTP trick, append a .gz to any filename on an FTP site > > and the FTP server will gzip it for you. > That is a nice trick. But one other thing...I doubt it would use the > -9 for maximum compression. Be happy to get any compression... OTOH rsync is a nice tool to download huge files: It can resume the download and even repairs damaged downloads by only redownloading the damaged/missing parts. Drawback: The server needs to support rsync (Question to SGI staff: Does oss.sgi.com support rsync?) See http://rsync.samba.org/ for details. -- Homepage: http://www.martin-stricker.de/ Registered Linux user #210635: http://counter.li.org/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:25:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f660P4V24607 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:25:04 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f660P3V24603 for ; Thu, 5 Jul 2001 17:25:03 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip23.idcomm.com [209.60.72.150]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f660RQl01877 for ; Thu, 5 Jul 2001 18:27:26 -0600 Message-ID: <3B4505D8.287A18C6@idcomm.com> Date: Thu, 05 Jul 2001 18:27:04 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ED39.20CF57C3@thebarn.com> <994373441.5295.13.camel@ajllinux.wellington.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Alistair Lambie wrote: > > On 05 Jul 2001 17:42:01 -0500, cattelan@thebarn.com wrote: > > Nathan Straz wrote: > > > > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > > > Being that the ISO images are rather large, it might be nice to have a > > > > duplicate of each current ISO available that is the gzip version. > > > > > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > > > the FTP server will gzip it for you. > > > > > > > Good idea (I'll check to make sure oss is configed to do this) > > but I doubt this will save space, > > every file on the iso is already compressed. > > So about the only space to be gained would be in > > the cd9660 file system, which I very small to start with. > > > > I thought it wouldn't save much either, but I just did it on > RH7.1-SGI-XFS-1.0.iso and it went from 299MB to 221MB. > > -- > Alistair Lambie alambie@sgi.com > SGI Global Product Support Phone: +64-21-635 262 > New Zealand Fax: +64-4-234 8792 The machine I hope to start the download on tonight receives at 26.4 kbps. Hmm. 78 MB might help :P The .gz notes show it runs max compression, so I'll use that if a gzip -9 isn't available. It would still be quite useful to have a precompressed image, since the cpu load to do a -9 compression is "significant", and a one-time compression is probably the better solution. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:31:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f660V1C25283 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:31:01 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f660UxV25276 for ; Thu, 5 Jul 2001 17:30:59 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip23.idcomm.com [209.60.72.150]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f660XNl02617 for ; Thu, 5 Jul 2001 18:33:23 -0600 Message-ID: <3B45073D.C29CC9ED@idcomm.com> Date: Thu, 05 Jul 2001 18:33:01 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ED39.20CF57C3@thebarn.com> <994373441.5295.13.camel@ajllinux.wellington.sgi.com> <3B4505D8.287A18C6@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > > Alistair Lambie wrote: > > > > On 05 Jul 2001 17:42:01 -0500, cattelan@thebarn.com wrote: > > > Nathan Straz wrote: > > > > > > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > > > > Being that the ISO images are rather large, it might be nice to have a > > > > > duplicate of each current ISO available that is the gzip version. > > > > > > > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > > > > the FTP server will gzip it for you. > > > > > > > > > > Good idea (I'll check to make sure oss is configed to do this) > > > but I doubt this will save space, > > > every file on the iso is already compressed. > > > So about the only space to be gained would be in > > > the cd9660 file system, which I very small to start with. > > > > > > > I thought it wouldn't save much either, but I just did it on > > RH7.1-SGI-XFS-1.0.iso and it went from 299MB to 221MB. > > > > -- > > Alistair Lambie alambie@sgi.com > > SGI Global Product Support Phone: +64-21-635 262 > > New Zealand Fax: +64-4-234 8792 > > The machine I hope to start the download on tonight receives at 26.4 > kbps. Hmm. 78 MB might help :P > > The .gz notes show it runs max compression, so I'll use that if a gzip > -9 isn't available. It would still be quite useful to have a > precompressed image, since the cpu load to do a -9 compression is > "significant", and a one-time compression is probably the better > solution. I just realized how poorly this last paragraph was written. To clarify, if the iso with .gz extension is not already available, I'll try adding it to get the server to do on-the-fly compression. But the compression itself is not trivial with 300 MB, so it would be better to have a precompressed image if possible. > > D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:36:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f660a2S25813 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:36:02 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f660a1V25810 for ; Thu, 5 Jul 2001 17:36:01 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15IJbE-0005AL-00; Fri, 06 Jul 2001 02:36:00 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f660ZUu02364; Thu, 5 Jul 2001 20:35:30 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Martin Stricker Cc: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ECDF.70BC38A1@idcomm.com> <3B4504CC.BC1D3BAE@gmx.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 05 Jul 2001 20:35:30 -0400 In-Reply-To: <3B4504CC.BC1D3BAE@gmx.de> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Martin" == Martin Stricker writes: Martin> Does oss.sgi.com support rsync?) Yep oss.sgi.com::xfsftp/ SunSITE.dk is probably faster for you, though: sunsite.dk::ftp/mirrors/xfs/ -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 17:55:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f660teb27870 for linux-xfs-outgoing; Thu, 5 Jul 2001 17:55:40 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f660tdV27860 for ; Thu, 5 Jul 2001 17:55:39 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id CAA11903; Fri, 6 Jul 2001 02:55:37 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id CAA11311; Fri, 6 Jul 2001 02:55:37 +0200 (CEST) Date: Fri, 6 Jul 2001 02:55:37 +0200 (CEST) From: Seth Mos To: "Martin K. Petersen" cc: Martin Stricker , linux-xfs@oss.sgi.com Subject: Re: aid to iso download In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 5 Jul 2001, Martin K. Petersen wrote: > >>>>> "Martin" == Martin Stricker writes: > > Martin> Does oss.sgi.com support rsync?) > > Yep > > oss.sgi.com::xfsftp/ > > SunSITE.dk is probably faster for you, though: > > sunsite.dk::ftp/mirrors/xfs/ Goo one, but the question is actually why I didn't notice that mirror before. Is it because it just got setup? btw I average about 50KB/s on a 1Mbit link in the Netherlands (DSL) with the xs4all internet provider. I will try this mirror on the next iso dump. btw, is ftp.sunet.se also available for mirroring? Cheers Seth From owner-linux-xfs@oss.sgi.com Thu Jul 5 18:04:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6614VT28985 for linux-xfs-outgoing; Thu, 5 Jul 2001 18:04:31 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6614TV28979 for ; Thu, 5 Jul 2001 18:04:29 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15IK2l-0005BB-00; Fri, 06 Jul 2001 03:04:27 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6613uq02372; Thu, 5 Jul 2001 21:03:56 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Seth Mos Cc: Martin Stricker , linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 05 Jul 2001 21:03:56 -0400 In-Reply-To: Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Seth" == Seth Mos writes: >> sunsite.dk::ftp/mirrors/xfs/ Seth> Goo one, but the question is actually why I didn't notice that Seth> mirror before. Is it because it just got setup? Nope. I set it up several months ago. Seth> btw, is ftp.sunet.se also available for mirroring? Dunno. Ask them :) -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Thu Jul 5 18:19:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f661JQi30497 for linux-xfs-outgoing; Thu, 5 Jul 2001 18:19:26 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f661JPV30494 for ; Thu, 5 Jul 2001 18:19:25 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id SAA02913 for ; Thu, 5 Jul 2001 18:19:40 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id SAA84026; Thu, 5 Jul 2001 18:18:52 -0700 (PDT) Message-ID: <3B451157.9A44E291@sgi.com> Date: Thu, 05 Jul 2001 20:16:07 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ED39.20CF57C3@thebarn.com> <994373441.5295.13.camel@ajllinux.wellington.sgi.com> <3B4505D8.287A18C6@idcomm.com> <3B45073D.C29CC9ED@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > I just realized how poorly this last paragraph was written. To clarify, > if the iso with .gz extension is not already available, I'll try adding > it to get the server to do on-the-fly compression. But the compression > itself is not trivial with 300 MB, so it would be better to have a > precompressed image if possible. Ok, I'm convinced. And now that the *.gz server trick is out, I don't want 100 people all hitting oss with gzip -9 on a 300meg file. :) The gzipped iso should be available in a few minutes. Also, if you get the PR3 iso, when it comes time to grab the final 1.0.1 version, remember that rsync is your friend in these situations... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 5 18:22:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f661MPF30798 for linux-xfs-outgoing; Thu, 5 Jul 2001 18:22:25 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f661MNV30783 for ; Thu, 5 Jul 2001 18:22:23 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id DAA1084771 for ; Fri, 6 Jul 2001 03:22:40 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 LAA16185; Fri, 6 Jul 2001 11:21:02 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA95032; Fri, 6 Jul 2001 11:21:01 +1000 (EST) From: "Nathan Scott" Message-Id: <10107061121.ZM194892@wobbly.melbourne.sgi.com> Date: Fri, 6 Jul 2001 11:21:00 -0500 In-Reply-To: Simon Matter "Reserved space in XFS for super-user" (Jul 5, 1:37pm) References: <3B445180.70F021DB@ch.sauter-bc.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Simon Matter , linux-xfs Subject: Re: Reserved space in XFS for super-user Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 5, 1:37pm, Simon Matter wrote: > Subject: Reserved space in XFS for super-user > Hello, > > Sorry if this is somewhere in the docs but I didn't find it. > Is there a way to reserve space on a XFS filesystem for the super-user, > a la -m options in mke2fs, which reserves 5% per default for root? I was > just wondering that I was able to fill a XFS partition as 'normal' user. > Not that I'm aware of, no - there's certainly no XFS mkfs option to do this. You may be able to use quotas if this is a problem, though. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 5 18:36:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f661aUf32112 for linux-xfs-outgoing; Thu, 5 Jul 2001 18:36:30 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f661aTV32109 for ; Thu, 5 Jul 2001 18:36:29 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id SAA01229 for ; Thu, 5 Jul 2001 18:36:22 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id SAA02874 for ; Thu, 5 Jul 2001 18:40:52 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 356BF15A46B for ; Thu, 5 Jul 2001 18:35:13 -0700 (PDT) Subject: Re: release 1.0.1-PR3 and AIC-78xx again :-( From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <994362337.12154.16.camel@stantz.corp.sgi.com> References: <994360573.12154.10.camel@stantz.corp.sgi.com> <994362337.12154.16.camel@stantz.corp.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 05 Jul 2001 18:35:13 -0700 Message-Id: <994383313.12166.25.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 05 Jul 2001 12:45:37 -0700, Florin Andrei wrote: > > So, it's not aic7xxx, it's DAC960. On the same system, i installed first v1.0, then upgraded all the RPMs to 1.0.1_PR3 (thanks Eric!) The system works fine after the upgrade to the kernel from 1.0.1_PR3. So, it's only the boot diskette that doesn't load correctly the DAC960 driver. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 5 18:38:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f661c1a32338 for linux-xfs-outgoing; Thu, 5 Jul 2001 18:38:01 -0700 Received: from groucho.maths.monash.edu.au (groucho.maths.monash.edu.au [130.194.160.211]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f661bxV32335 for ; Thu, 5 Jul 2001 18:37:59 -0700 Received: (from rjh@localhost) by groucho.maths.monash.edu.au (8.8.8/8.8.8) id BAA24931 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 01:37:58 GMT From: Robin Humble Message-Id: <200107060137.BAA24931@groucho.maths.monash.edu.au> Subject: Re: minor release notes bug in PR3 To: linux-xfs@oss.sgi.com Date: Fri, 6 Jul 2001 11:37:58 +1000 (EST) In-Reply-To: <3B4502A3.A6C942A6@sgi.com> from "Eric Sandeen" at Jul 05, 2001 07:13:23 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen writes: >Robin Humble wrote: >> A PR3 install went very smoothly with no problems BTW. >Great! Thanks for the report... no worries Although I would like to winge to someone about anaconda's crazy memory checks! I know it's nothing to do with XFS, but maybe having hacked anaconda you XFS folks can help out... or at least sympatise :) a) insisting on swap = 2x memory when you have heaps (384M) of ram installed and ~200M of swap seems silly. 2.4 kernels aren't that tragic (agressive) at using swap... and there's no way an install is going to fail with almost 500M of VM available, which is what anaconda misleadingly implies is going to happen. Is this suggestion actually based in reality?!? b) the 20-24M ram minimum before anaconda will run at all is also very annoying - my 16M laptop (200M+ of swap) runs 2.4-XFS happily... but I just can't upgrade from RH6.2 to 7.1 :-/ You'd think the installer could use the plentiful VM, and should work fine (although slowly). Do you think this ~20M limit in anaconda going to go away any time soon? I can try upgrading from 6.2 to 7.1 one-rpm-at-a-time but it'll be a real pain... From reading the anaconda src it looks like 'expert' install mode should override the 20M check but it doesn't. cheers, robin From owner-linux-xfs@oss.sgi.com Thu Jul 5 18:45:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f661jc300853 for linux-xfs-outgoing; Thu, 5 Jul 2001 18:45:38 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f661jbV00850 for ; Thu, 5 Jul 2001 18:45:37 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id SAA02113 for ; Thu, 5 Jul 2001 18:45:49 -0700 (PDT) mail_from (mg@smack.melbourne.sgi.com) Received: from smack.melbourne.sgi.com (smack.melbourne.sgi.com [134.14.55.210]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id LAA16327; Fri, 6 Jul 2001 11:44:16 +1000 Received: from localhost (mg@localhost) by smack.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id LAA52994; Fri, 6 Jul 2001 11:44:15 +1000 (EST) Date: Fri, 6 Jul 2001 11:44:15 +1000 From: Mike Gigante To: cattelan@thebarn.com cc: linux-xfs@oss.sgi.com Subject: Re: aid to iso download In-Reply-To: <3B44ED39.20CF57C3@thebarn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Well, IIRC bzip2 saved over 30% on the 1.0.1-pre3 iso image..... Mike On Thu, 5 Jul 2001 cattelan@thebarn.com wrote: > Nathan Straz wrote: > > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > > Being that the ISO images are rather large, it might be nice to have a > > > duplicate of each current ISO available that is the gzip version. > > > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > > the FTP server will gzip it for you. > > > > Good idea (I'll check to make sure oss is configed to do this) > but I doubt this will save space, > every file on the iso is already compressed. > So about the only space to be gained would be in > the cd9660 file system, which I very small to start with. > > > > > > -- > > Nate Straz nstraz@sgi.com > > sgi, inc http://www.sgi.com/ > > Linux Test Project http://ltp.sf.net/ > > From owner-linux-xfs@oss.sgi.com Thu Jul 5 20:12:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f663CwU04761 for linux-xfs-outgoing; Thu, 5 Jul 2001 20:12:58 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f663CvV04758 for ; Thu, 5 Jul 2001 20:12:57 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA07691 for ; Thu, 5 Jul 2001 20:13:11 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id UAA57315; Thu, 5 Jul 2001 20:12:24 -0700 (PDT) Message-ID: <3B452BF2.67606BBA@sgi.com> Date: Thu, 05 Jul 2001 22:09:38 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Robin Humble CC: linux-xfs@oss.sgi.com Subject: Re: minor release notes bug in PR3 References: <200107060137.BAA24931@groucho.maths.monash.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Robin Humble wrote: > I know it's nothing to do with XFS, but maybe having hacked anaconda > you XFS folks can help out... or at least sympatise :) I can sympathize, but the redhat-devel list would probably be a better place for answers... :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 5 22:21:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f665LJp14647 for linux-xfs-outgoing; Thu, 5 Jul 2001 22:21:19 -0700 Received: from mgate.lantana.net ([194.175.202.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f665LHV14644 for ; Thu, 5 Jul 2001 22:21:18 -0700 Received: from mail.rnb.de (unverified) by mgate.lantana.net (Content Technologies SMTPRS 4.1.5) with SMTP id for ; Fri, 6 Jul 2001 07:23:40 +0200 Received: from mailgate1.rnb.de ([194.49.51.139]) by mail.rnb.de (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 41256A81.001E9637; Fri, 6 Jul 2001 06:34:05 +0100 Received: from win2000-srv.rauheshaus.de ([192.168.252.106]) by mailgate1.rnb.de (Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) with SMTP id 41256A81.0021C9EE; Fri, 6 Jul 2001 07:09:03 +0100 Subject: multiple mount Date: Fri, 6 Jul 2001 07:25:38 +0200 Message-ID: <6A48864DC7CCF14E9500D91451458952C78F@WIN2000-SRV.WIN2000.rauheshaus.de> MIME-Version: 1.0 X-MS-Has-Attach: Content-Type: text/plain; charset="US-ASCII" X-MS-TNEF-Correlator: Thread-Topic: multiple mount Thread-Index: AcEF27t6eupBggMiTuueQV8A99sVrA== content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 From: "Jan Strohbehn" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f665LIV14645 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi !! The fact that it is possible to mount XFS partitions in a SAN on different machines without any warning led us into some problems with our servers. Is it possible to check if a partition is already mounted, without mounting it ;-) (e.g. under e2fs you get a warning like "not cleanly umounted") Thank you, Jan From owner-linux-xfs@oss.sgi.com Thu Jul 5 22:24:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f665OXv15055 for linux-xfs-outgoing; Thu, 5 Jul 2001 22:24:33 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f665OVV15051 for ; Thu, 5 Jul 2001 22:24:32 -0700 Received: from thebarn.com (nic-25-c96-156.mn.mediaone.net [24.25.96.156]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f665ORNe063851; Fri, 6 Jul 2001 00:24:28 -0500 (CDT) Message-ID: <3B454B86.8B203FB5@thebarn.com> Date: Fri, 06 Jul 2001 00:24:22 -0500 From: Russell Cattelan X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: stimits@idcomm.com, linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> <3B44ED39.20CF57C3@thebarn.com> <994373441.5295.13.camel@ajllinux.wellington.sgi.com> <3B4505D8.287A18C6@idcomm.com> <3B45073D.C29CC9ED@idcomm.com> <3B451157.9A44E291@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > "D. Stimits" wrote: > > > I just realized how poorly this last paragraph was written. To clarify, > > if the iso with .gz extension is not already available, I'll try adding > > it to get the server to do on-the-fly compression. But the compression > > itself is not trivial with 300 MB, so it would be better to have a > > precompressed image if possible. > > Ok, I'm convinced. And now that the *.gz server trick is out, I don't > want 100 people all hitting oss with gzip -9 on a 300meg file. :) Wouldn't worry about it, its not like the bottle neck going be cpu power any ways. Besides this would start consuming more disk space on oss if we have the compressed and non compressed images. Actually nix the second image we are completely out of ftp space on oss. Looks like I'm for some clean up. > > > The gzipped iso should be available in a few minutes. > > Also, if you get the PR3 iso, when it comes time to grab the final 1.0.1 > version, remember that rsync is your friend in these situations... > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. -- Russell Cattelan cattelan@thebarn.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 23:28:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f666S3X20597 for linux-xfs-outgoing; Thu, 5 Jul 2001 23:28:03 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f666S1V20594 for ; Thu, 5 Jul 2001 23:28:02 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA07901; Fri, 6 Jul 2001 08:27:59 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA27687; Fri, 6 Jul 2001 08:27:58 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 7BA5C57306; Fri, 6 Jul 2001 08:37:52 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id C034E25835; Fri, 6 Jul 2001 08:45:56 +0200 (CEST) Message-ID: <3B455AB2.A48928B3@ch.sauter-bc.com> Date: Fri, 06 Jul 2001 08:29:06 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: stimits@idcomm.com Cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk There is no reason to use gzip instead of bzip2. On wondows you can use PowerArchiver which will handle bzipped files as well. "D. Stimits" schrieb: > > Being that the ISO images are rather large, it might be nice to have a > duplicate of each current ISO available that is the gzip version. gzip > is suggested instead of bzip2 because gzip can be decompressed with > standard tools on most any machine, including with winzip on windows > (unfortunately, I'm one of those people that do not have access to a > burner on a linux machine). I'd strongly recommend using "gzip -9" since > maximum compression is important. With 300 MB files, it'll probably take > some time for compression to complete, but imagine how much it'll pay > off against a slow Internet download. I'm hoping to set a slow computer > downloading tonight from a windows machine, so I suspect compression > could cut down the time by many hours. > > D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Thu Jul 5 23:32:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f666W9421063 for linux-xfs-outgoing; Thu, 5 Jul 2001 23:32:09 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f666W8V21060 for ; Thu, 5 Jul 2001 23:32:08 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id XAA23308 for ; Thu, 5 Jul 2001 23:31:59 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA61126 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 16:30:49 +1000 (EST) Date: Fri, 6 Jul 2001 16:30:49 +1000 (EST) From: Nathan Scott Message-Id: <200107060630.QAA61126@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - startup message Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Implements the suggestion to display the enabled config options when the XFS code starts up. Date: Thu Jul 5 23:22:46 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98330a linux/fs/xfs/linux/xfs_super.h - 1.10 linux/fs/xfs/linux/xfs_super.c - 1.130 - startup message now shows which XFS options were enabled at build time. From owner-linux-xfs@oss.sgi.com Thu Jul 5 23:51:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f666p5J23055 for linux-xfs-outgoing; Thu, 5 Jul 2001 23:51:05 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f666p4V23051 for ; Thu, 5 Jul 2001 23:51:04 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA11055; Fri, 6 Jul 2001 08:51:02 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA29551; Fri, 6 Jul 2001 08:51:02 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B6A4957306; Fri, 6 Jul 2001 09:00:51 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id CD90B25835; Fri, 6 Jul 2001 09:08:55 +0200 (CEST) Message-ID: <3B456015.E9D92D88@ch.sauter-bc.com> Date: Fri, 06 Jul 2001 08:52:05 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Robin Humble Cc: linux-xfs@oss.sgi.com Subject: Re: minor release notes bug in PR3 References: <200107060137.BAA24931@groucho.maths.monash.edu.au> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Robin Humble schrieb: > > Eric Sandeen writes: > >Robin Humble wrote: > >> A PR3 install went very smoothly with no problems BTW. > >Great! Thanks for the report... > > no worries > > Although I would like to winge to someone about anaconda's crazy > memory checks! > I know it's nothing to do with XFS, but maybe having hacked anaconda > you XFS folks can help out... or at least sympatise :) > > a) insisting on swap = 2x memory when you have heaps (384M) of ram > installed and ~200M of swap seems silly. 2.4 kernels aren't that > tragic (agressive) at using swap... and there's no way an install is > going to fail with almost 500M of VM available, which is what > anaconda misleadingly implies is going to happen. > Is this suggestion actually based in reality?!? > I strongly suggest to not insist on a swap partition at all. Sometimes I want to install with swap located on SoftRAID1 and anaconda does not like that. Sometimes I don't have a swap partition free at install time so I want to be able to install without swap. > b) the 20-24M ram minimum before anaconda will run at all is also > very annoying - my 16M laptop (200M+ of swap) runs 2.4-XFS happily... > but I just can't upgrade from RH6.2 to 7.1 :-/ You'd think the > installer could use the plentiful VM, and should work fine (although > slowly). > Do you think this ~20M limit in anaconda going to go away any time soon? > I can try upgrading from 6.2 to 7.1 one-rpm-at-a-time but it'll be a > real pain... From reading the anaconda src it looks like 'expert' > install mode should override the 20M check but it doesn't. > > cheers, > robin -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 5 23:52:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f666qsV23273 for linux-xfs-outgoing; Thu, 5 Jul 2001 23:52:54 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f666qrV23266 for ; Thu, 5 Jul 2001 23:52:53 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA16617; Fri, 6 Jul 2001 08:52:52 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id IAA13083; Fri, 6 Jul 2001 08:52:51 +0200 (CEST) Date: Fri, 6 Jul 2001 08:52:51 +0200 (CEST) From: Seth Mos To: Robin Humble cc: linux-xfs@oss.sgi.com Subject: Re: minor release notes bug in PR3 In-Reply-To: <200107060137.BAA24931@groucho.maths.monash.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 6 Jul 2001, Robin Humble wrote: > > Eric Sandeen writes: > >Robin Humble wrote: > >> A PR3 install went very smoothly with no problems BTW. > >Great! Thanks for the report... > > no worries > > Although I would like to winge to someone about anaconda's crazy > memory checks! > I know it's nothing to do with XFS, but maybe having hacked anaconda > you XFS folks can help out... or at least sympatise :) > > a) insisting on swap = 2x memory when you have heaps (384M) of ram > installed and ~200M of swap seems silly. 2.4 kernels aren't that > tragic (agressive) at using swap... and there's no way an install is > going to fail with almost 500M of VM available, which is what > anaconda misleadingly implies is going to happen. > Is this suggestion actually based in reality?!? I have used it on machines with 192MB ram and 300 swap which was enough. > b) the 20-24M ram minimum before anaconda will run at all is also > very annoying - my 16M laptop (200M+ of swap) runs 2.4-XFS happily... > but I just can't upgrade from RH6.2 to 7.1 :-/ You'd think the > installer could use the plentiful VM, and should work fine (although > slowly). > Do you think this ~20M limit in anaconda going to go away any time soon? > I can try upgrading from 6.2 to 7.1 one-rpm-at-a-time but it'll be a > real pain... From reading the anaconda src it looks like 'expert' > install mode should override the 20M check but it doesn't. it worked for me on 1.0. I havn't burnt the iso yet to test it. Lack of time and too much sun. Cheers Seth From owner-linux-xfs@oss.sgi.com Thu Jul 5 23:57:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f666v2q23718 for linux-xfs-outgoing; Thu, 5 Jul 2001 23:57:02 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f666v1V23709 for ; Thu, 5 Jul 2001 23:57:01 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id IAA18106; Fri, 6 Jul 2001 08:56:59 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id IAA07028; Fri, 6 Jul 2001 08:56:59 +0200 (CEST) Date: Fri, 6 Jul 2001 08:56:59 +0200 (CEST) From: Seth Mos To: Jan Strohbehn cc: linux-xfs@oss.sgi.com Subject: Re: multiple mount In-Reply-To: <6A48864DC7CCF14E9500D91451458952C78F@WIN2000-SRV.WIN2000.rauheshaus.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 6 Jul 2001, Jan Strohbehn wrote: > Hi !! > > The fact that it is possible to mount XFS partitions in a SAN on > different machines without any warning led us into some problems with > our servers. Is it possible to check if a partition is already mounted, > without mounting it ;-) ehmm..... "mount"? You can mount multiple partitions on the same mountpoint. it's not an XFS problem but a feature of 2.4 > (e.g. under e2fs you get a warning like "not cleanly umounted") But it also mounts. So you want to see a warning of you mount it more then once? Cheers Seth From owner-linux-xfs@oss.sgi.com Fri Jul 6 00:05:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66753b24623 for linux-xfs-outgoing; Fri, 6 Jul 2001 00:05:03 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66751V24618 for ; Fri, 6 Jul 2001 00:05:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA13382; Fri, 6 Jul 2001 09:04:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA00630; Fri, 6 Jul 2001 09:04:58 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 4A1FE57306; Fri, 6 Jul 2001 09:14:04 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 66E7725836; Fri, 6 Jul 2001 09:22:08 +0200 (CEST) Message-ID: <3B45632E.3F7F41DB@ch.sauter-bc.com> Date: Fri, 06 Jul 2001 09:05:18 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Seth Mos Cc: Jan Strohbehn , linux-xfs@oss.sgi.com Subject: Re: multiple mount References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos schrieb: > > On Fri, 6 Jul 2001, Jan Strohbehn wrote: > > > Hi !! > > > > The fact that it is possible to mount XFS partitions in a SAN on > > different machines without any warning led us into some problems with > > our servers. Is it possible to check if a partition is already mounted, > > without mounting it ;-) > > ehmm..... "mount"? You can mount multiple partitions on the same > mountpoint. it's not an XFS problem but a feature of 2.4 I guess he means mounting of a shared disk on more than one computer at the same time. When using ext2 you get the "not cleanly umounted" because the shared filesystem is not marked clean when already mounted on another computer. > > > (e.g. under e2fs you get a warning like "not cleanly umounted") > > But it also mounts. So you want to see a warning of you mount it more then > once? > > Cheers > Seth From owner-linux-xfs@oss.sgi.com Fri Jul 6 00:06:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6676oG24839 for linux-xfs-outgoing; Fri, 6 Jul 2001 00:06:50 -0700 Received: from mgate.lantana.net ([194.175.202.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6676nV24836 for ; Fri, 6 Jul 2001 00:06:49 -0700 Received: from mail.rnb.de (unverified) by mgate.lantana.net (Content Technologies SMTPRS 4.1.5) with SMTP id for ; Fri, 6 Jul 2001 09:09:12 +0200 Received: from mailgate1.rnb.de ([194.49.51.139]) by mail.rnb.de (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 41256A81.00283FFC; Fri, 6 Jul 2001 08:19:38 +0100 Received: from win2000-srv.rauheshaus.de ([192.168.252.106]) by mailgate1.rnb.de (Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) with SMTP id 41256A81.002B77C0; Fri, 6 Jul 2001 08:54:47 +0100 Subject: Re: multiple mount Date: Fri, 6 Jul 2001 09:11:23 +0200 Message-ID: <6A48864DC7CCF14E9500D91451458952C791@WIN2000-SRV.WIN2000.rauheshaus.de> X-MS-Has-Attach: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MS-TNEF-Correlator: Thread-Topic: multiple mount Thread-Index: AcEF6cQZRcKDlIZ8QBOQZRvfzBtRQwAABAig content-class: urn:content-classes:message From: "Jan Strohbehn" X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 To: "Seth Mos" , Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6676nV24837 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi !! > > The fact that it is possible to mount XFS partitions in a SAN on > > different machines without any warning led us into some > > problems with > > our servers. Is it possible to check if a partition is > > already mounted, > > without mounting it ;-) > > ehmm..... "mount"? You can mount multiple partitions on the same > mountpoint. it's not an XFS problem but a feature of 2.4 > > > (e.g. under e2fs you get a warning like "not cleanly umounted") > > But it also mounts. So you want to see a warning of you mount > it more then > once? > Yes, that's what I want. Just to see if the filesystem is possibly mounted by another machine. Is this possible ?? Thanks, Jan From owner-linux-xfs@oss.sgi.com Fri Jul 6 00:09:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6679Mp25213 for linux-xfs-outgoing; Fri, 6 Jul 2001 00:09:22 -0700 Received: from mgate.lantana.net ([194.175.202.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6679KV25210 for ; Fri, 6 Jul 2001 00:09:21 -0700 Received: from mail.rnb.de (unverified) by mgate.lantana.net (Content Technologies SMTPRS 4.1.5) with SMTP id for ; Fri, 6 Jul 2001 09:11:43 +0200 Received: from mailgate1.rnb.de ([194.49.51.139]) by mail.rnb.de (Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) with SMTP id 41256A81.00287C90; Fri, 6 Jul 2001 08:22:13 +0100 Received: from win2000-srv.rauheshaus.de ([192.168.252.106]) by mailgate1.rnb.de (Lotus SMTP MTA v4.6.2 (693.3 8-11-1998)) with SMTP id 41256A81.002BB330; Fri, 6 Jul 2001 08:57:19 +0100 Subject: AW: multiple mount Date: Fri, 6 Jul 2001 09:14:09 +0200 Message-ID: <6A48864DC7CCF14E9500D91451458952246F@WIN2000-SRV.WIN2000.rauheshaus.de> X-MS-Has-Attach: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MS-TNEF-Correlator: Thread-Topic: multiple mount Thread-Index: AcEF6uIbOcaEKeOXRBmIIU/QsmeK3gAADf9w content-class: urn:content-classes:message From: "Jan Strohbehn" X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 To: "Simon Matter" , "Seth Mos" Cc: , Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6679LV25211 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > The fact that it is possible to mount XFS partitions in a SAN on > > > different machines without any warning led us into some > > > problems with > > > our servers. Is it possible to check if a partition is > > > already mounted, > > > without mounting it ;-) > > > > ehmm..... "mount"? You can mount multiple partitions on the same > > mountpoint. it's not an XFS problem but a feature of 2.4 > > I guess he means mounting of a shared disk on more than one > computer at > the > same time. When using ext2 you get the "not cleanly umounted" because > the > shared filesystem is not marked clean when already mounted on another > computer. > Yes, that's exactly what I mean ;-) Jan From owner-linux-xfs@oss.sgi.com Fri Jul 6 00:23:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f667NHY26886 for linux-xfs-outgoing; Fri, 6 Jul 2001 00:23:17 -0700 Received: from mx.gie-fs.net (WEB-A.GIE-FS.NET [62.4.25.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f667NEV26883 for ; Fri, 6 Jul 2001 00:23:16 -0700 Received: from sas-a.federalservice.fr (sas-a.federalservice.fr [10.154.13.30]) by mx.gie-fs.net (8.11.4/8.11.4/GIE-FS) with ESMTP id f667N8904457 for ; Fri, 6 Jul 2001 09:23:12 +0200 (MET DST) Received: from dns-platine-2.platine.federalservice.fr (sas-a.federalservice.fr [127.0.0.1]) by sas-a.federalservice.fr (8.11.3/8.11.3/GIE-FS/SAS-A) with ESMTP id f667N7S21022 for ; Fri, 6 Jul 2001 09:23:07 +0200 Received: from unknown by dns-platine-2.platine.federalservice.fr (8.9.1b+Sun/8.9.1) id JAA13521 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 09:23:07 +0200 (MET DST) Received: from cmb.fr by dns-platine-2.platine.federalservice.fr (8.9.1b+Sun/8.9.1) with ESMTP id JAA13517 for ; Fri, 6 Jul 2001 09:23:07 +0200 (MET DST) Message-ID: <3B45675A.5EEDBD0F@cmb.fr> Date: Fri, 06 Jul 2001 09:23:06 +0200 From: Mathias Herberts X-Mailer: Mozilla 4.7 [en]C-NSCPCD (WinNT; U) X-Accept-Language: en,en-US,en-GB,fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS compatibility with 2.4.6 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I gave 2.4.6 and XFS a few tries but to no avail, the 2.4.6 xfs-cvs patch available on your ftp site seems to break the kernel build process when jointly applied with JFS 1.0.0 and LVM 0.9.1b7. The 2.4.5 patch worked ok with the 2.4.5 kernel, but the 2.4.6 patch seems to be broken. Any hint on how to put JFS/XFS and the last LVM in the 2.4.6 kernel? JFS and LVM 0.9.1b7 do work ok in the 2.4.6 kernel. Best regards and thanks for releasing XFS for Linux. Mathias Herberts. -- Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisee est interdite. Tout message etant susceptible d'alteration, l'emetteur decline toute responsabilite au titre de ce message s'il a ete altere, deforme ou falsifie. ----------------------------------- This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised use or dissemination is prohibited. As e-mails are susceptible to alteration, the issuer shall not be liable for the message if altered, changed or falsified. From owner-linux-xfs@oss.sgi.com Fri Jul 6 00:36:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f667aOg28473 for linux-xfs-outgoing; Fri, 6 Jul 2001 00:36:24 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f667aNV28470 for ; Fri, 6 Jul 2001 00:36:23 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id JAA29995; Fri, 6 Jul 2001 09:36:21 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id JAA14205; Fri, 6 Jul 2001 09:36:20 +0200 (CEST) Date: Fri, 6 Jul 2001 09:36:20 +0200 (CEST) From: Seth Mos To: Mathias Herberts cc: linux-xfs@oss.sgi.com Subject: Re: XFS compatibility with 2.4.6 In-Reply-To: <3B45675A.5EEDBD0F@cmb.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 6 Jul 2001, Mathias Herberts wrote: > Hi, > > I gave 2.4.6 and XFS a few tries but to no avail, the 2.4.6 xfs-cvs > patch available on your ftp site seems to break the kernel build process > when jointly applied with JFS 1.0.0 and LVM 0.9.1b7. When patching in a newer LVM you have to watch out. XFS needs something more of LVM for the blksize ioctl. If you patch in a newer LVM you probably removed that. The only conflict that JFS and XFS have is in fs.h which can be solved by either finding the patch in the mailing list archive or handapplying the rejected lines. > The 2.4.5 patch worked ok with the 2.4.5 kernel, but the 2.4.6 patch > seems to be broken. Have not been able to test the 2.4.6 patch yet. > Any hint on how to put JFS/XFS and the last LVM in the 2.4.6 kernel? See the thread in the mailinglist archives "XFS mary's JFS" There were links to patches in there and discussion about both of them. > JFS and LVM 0.9.1b7 do work ok in the 2.4.6 kernel. Because JFS probably uses just one blksize and XFS switches between pagesize (4k) and 512bytes. > Best regards and thanks for releasing XFS for Linux. Ain't it great? Cheer Seth From owner-linux-xfs@oss.sgi.com Fri Jul 6 01:11:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f668BWa30274 for linux-xfs-outgoing; Fri, 6 Jul 2001 01:11:32 -0700 Received: from geulph.frogspace.net (IDENT:root@geulph.frogspace.net [64.6.226.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f668BWV30269 for ; Fri, 6 Jul 2001 01:11:32 -0700 Received: from [139.92.59.6] (helo=ergenekon) by geulph.frogspace.net with smtp (Exim 3.02 #1) id 15IQi0-0007OA-00 for linux-xfs@oss.sgi.com; Fri, 06 Jul 2001 01:11:29 -0700 Message-ID: <04cb01c105f3$41631990$0300a8c0@ergenekon> Reply-To: "Deniz Akkus Kanca" From: "Deniz Akkus Kanca" To: Subject: question about repartitioning/resizing XFS Date: Fri, 6 Jul 2001 11:11:22 +0300 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.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, First of all, my apologies for this question. I've never had to do this sort of re-partitioning before and probably my questions will seem pretty silly, but I really would appreciate a pointer to the right sources.. Hardware: SMP board, 3Ware ATA Raid, 240 Gig (8x30Gig) HD, running RAID 5, 1 Gig RAM OS: Redhat 7.1 Kernel: 2.4.2_SGI_XFS_1.0SMP -- kernel is too big to boot from floppy. Due to performance issues I need to increase RAM to 2 Gig and consequently increase the swap space to 4 Gig. Currently I have partitioned the RAID drive as: /boot 16 Meg -- ext2 / 20 Gig -- ext2 /swap 2 Gig /xfs remainder -- xfs I am not running LVM. Ideally I would like to "steal" 2 Gig or so from the xfs partition, and add it to the swap space. XFS partition has about 60 Gig or so of data on it, so it is pretty empty, but is too big to comfortably back-up. I have never repartitioned a linux disk. How do I do this? Again, my apologies for the newbie question, Best regards, Deniz From owner-linux-xfs@oss.sgi.com Fri Jul 6 01:22:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f668MSJ30919 for linux-xfs-outgoing; Fri, 6 Jul 2001 01:22:28 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f668MRV30916 for ; Fri, 6 Jul 2001 01:22:27 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip12.idcomm.com [209.60.72.139]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f668Orl12027 for ; Fri, 6 Jul 2001 02:24:53 -0600 Message-ID: <3B4575BC.2BBCE424@idcomm.com> Date: Fri, 06 Jul 2001 02:24:28 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: aid to iso download References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mike Gigante wrote: > > Well, > > IIRC bzip2 saved over 30% on the 1.0.1-pre3 iso image..... bzip2 is superior, except in one respect...you can't use common windows programs to decompress it and burn a linux cd on win; winzip will work fine with gzip and tar files though, so it is rather universal. D. Stimits, stimits@idcomm.com > > Mike > > On Thu, 5 Jul 2001 cattelan@thebarn.com wrote: > > > Nathan Straz wrote: > > > > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > > > Being that the ISO images are rather large, it might be nice to have a > > > > duplicate of each current ISO available that is the gzip version. > > > > > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > > > the FTP server will gzip it for you. > > > > > > > Good idea (I'll check to make sure oss is configed to do this) > > but I doubt this will save space, > > every file on the iso is already compressed. > > So about the only space to be gained would be in > > the cd9660 file system, which I very small to start with. > > > > > > > > > > -- > > > 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 Jul 6 01:23:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f668NsC31078 for linux-xfs-outgoing; Fri, 6 Jul 2001 01:23:54 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f668NrV31075 for ; Fri, 6 Jul 2001 01:23:53 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip12.idcomm.com [209.60.72.139]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f668QIl12121 for ; Fri, 6 Jul 2001 02:26:19 -0600 Message-ID: <3B457611.83E128AE@idcomm.com> Date: Fri, 06 Jul 2001 02:25:53 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <3B455AB2.A48928B3@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > > There is no reason to use gzip instead of bzip2. On wondows you can use > PowerArchiver which will handle bzipped files as well. I'm not familiar with PowerArchiver. Where is it available? Is it free? Does it work with win 2k? (perhaps not as relevant, but some might be interested, is there some sort of similar program to work with bzip2 on a Mac?) D. Stimits, stimits@idcomm.com > > "D. Stimits" schrieb: > > > > Being that the ISO images are rather large, it might be nice to have a > > duplicate of each current ISO available that is the gzip version. gzip > > is suggested instead of bzip2 because gzip can be decompressed with > > standard tools on most any machine, including with winzip on windows > > (unfortunately, I'm one of those people that do not have access to a > > burner on a linux machine). I'd strongly recommend using "gzip -9" since > > maximum compression is important. With 300 MB files, it'll probably take > > some time for compression to complete, but imagine how much it'll pay > > off against a slow Internet download. I'm hoping to set a slow computer > > downloading tonight from a windows machine, so I suspect compression > > could cut down the time by many hours. > > > > D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Fri Jul 6 02:12:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f669C3T01176 for linux-xfs-outgoing; Fri, 6 Jul 2001 02:12:03 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f669C1V01172 for ; Fri, 6 Jul 2001 02:12:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id LAA10368; Fri, 6 Jul 2001 11:11:59 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id LAA11462; Fri, 6 Jul 2001 11:11:58 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B855857306; Fri, 6 Jul 2001 11:21:44 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 283E125835; Fri, 6 Jul 2001 11:29:49 +0200 (CEST) Message-ID: <3B45811A.A5B82C1C@ch.sauter-bc.com> Date: Fri, 06 Jul 2001 11:12:58 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: stimits@idcomm.com Cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <3B455AB2.A48928B3@ch.sauter-bc.com> <3B457611.83E128AE@idcomm.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" schrieb: > > Simon Matter wrote: > > > > There is no reason to use gzip instead of bzip2. On wondows you can use > > PowerArchiver which will handle bzipped files as well. > > I'm not familiar with PowerArchiver. Where is it available? Is it free? > Does it work with win 2k? (perhaps not as relevant, but some might be > interested, is there some sort of similar program to work with bzip2 on > a Mac?) Until version 7.0, it was free. Now from 7.0 ongoing it's shareware. You can still use lastest free version which is 6.11. You can compare it with winzip but I think it's better! It understands more file formats than winzip. See http://www.powerarchiver.com/ for more info. Simon > > D. Stimits, stimits@idcomm.com > > > > > "D. Stimits" schrieb: > > > > > > Being that the ISO images are rather large, it might be nice to have a > > > duplicate of each current ISO available that is the gzip version. gzip > > > is suggested instead of bzip2 because gzip can be decompressed with > > > standard tools on most any machine, including with winzip on windows > > > (unfortunately, I'm one of those people that do not have access to a > > > burner on a linux machine). I'd strongly recommend using "gzip -9" since > > > maximum compression is important. With 300 MB files, it'll probably take > > > some time for compression to complete, but imagine how much it'll pay > > > off against a slow Internet download. I'm hoping to set a slow computer > > > downloading tonight from a windows machine, so I suspect compression > > > could cut down the time by many hours. > > > > > > D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Fri Jul 6 02:42:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f669gcB03466 for linux-xfs-outgoing; Fri, 6 Jul 2001 02:42:38 -0700 Received: from www1.tradepage.co.za ([196.25.96.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f669gaV03461 for ; Fri, 6 Jul 2001 02:42:37 -0700 Received: from ntsupport1 (tradepage.co.za [192.96.43.48]) by www1.tradepage.co.za (Rockliffe SMTPRA 3.4.2) with SMTP id for ; Fri, 6 Jul 2001 11:44:54 +0200 From: "Martin Potgieter" To: Subject: no keyboard Date: Fri, 6 Jul 2001 11:43:08 +0200 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) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I recently installed Redhat 7.1 with XFS support from the ISO installer I downloaded. The installation went smooth all the way through. When I rebooted all seemed fine aswell but when I came to the login prompt the keyboard was not responding. When I did the install I selected the default keyboard. I had Redhat running on the same machine without the XFS support and all worked ok so I assume it has something to do with the XFS support. I changed the keyboard 3 times to no avail. I ssh'ed into the machine and launched KDE which fired up with the mouse working fine but also no keyboard. I am using PC Chips m726 MB 128m ram 4.3 gig conner hd generic serial mouse 36x samsung cdrom realtek 8129 NIC Any help will be appreciated Martin Potgieter From owner-linux-xfs@oss.sgi.com Fri Jul 6 03:12:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66ACCl06296 for linux-xfs-outgoing; Fri, 6 Jul 2001 03:12:12 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66ACBV06292 for ; Fri, 6 Jul 2001 03:12:11 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id MAA14785; Fri, 6 Jul 2001 12:11:59 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id MAA16875; Fri, 6 Jul 2001 12:11:59 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id A1CE157306; Fri, 6 Jul 2001 12:22:00 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 7F92F25835; Fri, 6 Jul 2001 12:30:04 +0200 (CEST) Message-ID: <3B458F39.20A33D3D@ch.sauter-bc.com> Date: Fri, 06 Jul 2001 12:13:13 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Martin Potgieter Cc: linux-xfs@oss.sgi.com Subject: Re: no keyboard References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Martin Potgieter schrieb: > > I recently installed Redhat 7.1 with XFS support from the ISO installer I > downloaded. The installation went smooth all the way through. When I > rebooted all seemed fine aswell but when I came to the login prompt the > keyboard was not responding. When I did the install I selected the default > keyboard. I had Redhat running on the same machine without the XFS support > and all worked ok so I assume it has something to do with the XFS support. > I changed the keyboard 3 times to no avail. I ssh'ed into the machine and > launched KDE which fired up with the mouse working fine but also no > keyboard. > I am using > > PC Chips m726 MB > 128m ram > 4.3 gig conner hd > generic serial mouse > 36x samsung cdrom > realtek 8129 NIC > > Any help will be appreciated > > Martin Potgieter Maybe it a devfs issue. Just try to boot with devfs=nomount as kernel parameter. Greetings Simon From owner-linux-xfs@oss.sgi.com Fri Jul 6 04:23:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66BNni14446 for linux-xfs-outgoing; Fri, 6 Jul 2001 04:23:49 -0700 Received: from [196.25.235.9] ([196.25.235.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66BNlV14442 for ; Fri, 6 Jul 2001 04:23:47 -0700 Received: from ntsupport1 (unverified [192.96.43.48]) by (Rockliffe SMTPRA 3.4.2) with SMTP id ; Fri, 6 Jul 2001 13:22:47 +0200 From: "Martin Potgieter" To: "Simon Matter" Cc: Subject: RE: no keyboard Date: Fri, 6 Jul 2001 13:24:17 +0200 Message-ID: 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 IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <3B458F39.20A33D3D@ch.sauter-bc.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2462.0000 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >Maybe it a devfs issue. Just try to boot with devfs=nomount as kernel >parameter. >Greetings >Simon I just tried the above and still no luck????? Thanks Martin From owner-linux-xfs@oss.sgi.com Fri Jul 6 06:47:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66DlT032354 for linux-xfs-outgoing; Fri, 6 Jul 2001 06:47:29 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66DlSV32349 for ; Fri, 6 Jul 2001 06:47:28 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id GAA01168 for ; Fri, 6 Jul 2001 06:47:20 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2326597; Fri, 6 Jul 2001 08:46:09 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA11280; Fri, 6 Jul 2001 08:46:09 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66Dm3P07366; Fri, 6 Jul 2001 08:48:03 -0500 Message-Id: <200107061348.f66Dm3P07366@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Jan Strohbehn" cc: "Simon Matter" , "Seth Mos" , edv.rauheshaus@192.168.20.17.sgi.com, linux-xfs@oss.sgi.com Subject: Re: AW: multiple mount In-Reply-To: Message from "Jan Strohbehn" of "Fri, 06 Jul 2001 09:14:09 +0200." <6A48864DC7CCF14E9500D91451458952246F@WIN2000-SRV.WIN2000.rauheshaus.de> Date: Fri, 06 Jul 2001 08:48:03 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The short answer is there is no way to prevent this beyond being careful. The difference between xfs and ext2 here is that for an uncleanly unmounted ext2 partition you need to run a user space application to fix it up (fsck). For xfs there is no such requirement, the kernel detects the state, and replays the log to fix up the filesystem. Unfortunately this does mean that an XFS filesystem will just mount if you ask it to, which means on a SAN two hosts can mount it at the same time. There is no way to tell the difference between a filesystem which crashed and one which is active on another system. We do have logic to check for the same device already being mounted on the same host to avoid this very situation there, this depends on an in memory table though, so cannot be extended to multiple hosts. Steve > > > > > The fact that it is possible to mount XFS partitions in a SAN on > > > > different machines without any warning led us into some > > > > problems with > > > > our servers. Is it possible to check if a partition is > > > > already mounted, > > > > without mounting it ;-) > > > > > > ehmm..... "mount"? You can mount multiple partitions on the same > > > mountpoint. it's not an XFS problem but a feature of 2.4 > > > > I guess he means mounting of a shared disk on more than one > > computer at > > the > > same time. When using ext2 you get the "not cleanly umounted" because > > the > > shared filesystem is not marked clean when already mounted on another > > computer. > > > > Yes, that's exactly what I mean ;-) > > Jan From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:00:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66E0AV00973 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:00:10 -0700 Received: from ms1.adiis.net (root@ms1.adiis.net [207.177.36.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66E09V00969 for ; Fri, 6 Jul 2001 07:00:10 -0700 Received: from adiis.net (dialupoffice.adiis.net [207.177.36.9]) by ms1.adiis.net (8.9.3/8.9.3) with ESMTP id IAA09065; Fri, 6 Jul 2001 08:59:57 -0500 Message-ID: <3B45C45A.7000202@adiis.net> Date: Fri, 06 Jul 2001 08:59:54 -0500 From: Ryan Butler Organization: ADI Internet Solutions User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686; en-US; rv:0.9.1) Gecko/20010608 X-Accept-Language: en-us MIME-Version: 1.0 To: Deniz Akkus Kanca CC: linux-xfs@oss.sgi.com Subject: Re: question about repartitioning/resizing XFS References: <04cb01c105f3$41631990$0300a8c0@ergenekon> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Deniz Akkus Kanca wrote: > >Ideally I would like to "steal" 2 Gig or so from the xfs partition, and add >it to the swap space. XFS partition has about 60 Gig or so of data on it, >so it is pretty empty, but is too big to comfortably back-up. > > This is a FAQ entry, you cannot shrink an xfs partition in any way, however you can grow them. To "steal" 2 gig from the xfs partition would require a complete dump, repartition, restore operation. The FAQ is available from http://oss.sgi.com/projects/xfs Ryan Butler ADI Internet Solutions rbutler@adiis.net From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:06:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66E6sp01551 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:06:54 -0700 Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66E6qV01548 for ; Fri, 6 Jul 2001 07:06:52 -0700 Received: from fokus.gmd.de (dorian [193.175.135.179]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id QAA12727 for ; Fri, 6 Jul 2001 16:06:50 +0200 (MET DST) Message-ID: <3B45C5FA.BAC5FB56@fokus.gmd.de> Date: Fri, 06 Jul 2001 16:06:50 +0200 From: Andrei Pelinescu-Onciul X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre3-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: libgdbm open & xfs problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have encountered a strange problem trying to build a nis database on a xfs partition. For some values of sunit and swidth I cannot build the database. For example: echo "test test" | /usr/lib/yp/makedbm - /tmp/x fails with makedbm: Cannot open /tmp/x~. I've traced it down to a call to gdbm_open which fails. The strange thing is that if I mount the xfs filesystem with noalign, or I use mkfs.xfs with sunit=0 and swidth=0 it works. It works also for mkfs.xfs -f -d sunit=128,swidth=256, but it does not work for mkfs.xfs -f -d sunit=128,swidth=384. I tested it with 2.4.2-xfs, 2.4.6-pre3-xfs and 2.4.7-pre3-xfs. I use libgdbm 1.7.3. ltrace /usr/lib/yp/makedbm /tmp/test /var/tmp/x [...] fopen("/tmp/test", "r") = 0x0804b2b8 calloc(1, 13) = 0x0804b428 sprintf("/var/tmp/x~", "%s~", "/var/tmp/x") = 11 gdbm_open(0x0804b428, 0, 19, 384, 0) = 0 (here it fails, gdbm_open should return non-null) strace /usr/lib/yp/makedbm /tmp/test /var/tmp/x [...] open("/tmp/test", O_RDONLY) = 3 open("/var/tmp/x~", O_RDWR|O_CREAT, 0600) = 4 fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 fcntl64(0x4, 0x6, 0xbffffb54, 0xbffffb64) = 0 old_mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x4014b000 fsync(4) = 0 fcntl64(0x4, 0x6, 0xbffffadc, 0x40000) = 0 close(4) = 0 munmap(0x4014b000, 200704) = 0 write(2, "makedbm: Cannot open /var/tmp/x~" [...] Andrei From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:20:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66EKKp02892 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:20:20 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66EKDV02870 for ; Fri, 6 Jul 2001 07:20:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA1110269 for ; Fri, 6 Jul 2001 16:20:10 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2356354; Fri, 6 Jul 2001 09:18:50 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA28127; Fri, 6 Jul 2001 09:18:49 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66EKh108158; Fri, 6 Jul 2001 09:20:43 -0500 Message-Id: <200107061420.f66EKh108158@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mathias Herberts cc: linux-xfs@oss.sgi.com Subject: Re: XFS compatibility with 2.4.6 In-Reply-To: Message from Mathias Herberts of "Fri, 06 Jul 2001 09:23:06 +0200." <3B45675A.5EEDBD0F@cmb.fr> Date: Fri, 06 Jul 2001 09:20:43 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > > I gave 2.4.6 and XFS a few tries but to no avail, the 2.4.6 xfs-cvs > patch available on your ftp site seems to break the kernel build process > when jointly applied with JFS 1.0.0 and LVM 0.9.1b7. > > The 2.4.5 patch worked ok with the 2.4.5 kernel, but the 2.4.6 patch > seems to be broken. You need to be a bit more explicit in what you mean by breaks the build process, plus you are in effect applying two lvm patches. The xfs kernel contains 0.9.1_beta6 while the base kernel still contains 0.9.1_beta2, so applying 0.9.1b7 is not that straight forward, plus, as Seth already pointed out, we have more than just a different revision of lvm in there. Steve > > Any hint on how to put JFS/XFS and the last LVM in the 2.4.6 kernel? > > JFS and LVM 0.9.1b7 do work ok in the 2.4.6 kernel. > > Best regards and thanks for releasing XFS for Linux. > > Mathias Herberts. > > -- > Ce message et toutes les pieces jointes (ci-apres le "message") sont > confidentiels et etablis a l'intention exclusive de ses destinataires. > Toute utilisation ou diffusion non autorisee est interdite. Tout > message etant susceptible d'alteration, l'emetteur decline toute > responsabilite au titre de ce message s'il a ete altere, deforme ou > falsifie. > ----------------------------------- > This message and any attachments (the "message") are confidential and > intended solely for the addressees. Any unauthorised use or > dissemination is prohibited. As e-mails are susceptible to alteration, > the issuer shall not be liable for the message if altered, changed > or falsified. > From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:23:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66ENKc03196 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:23:20 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66ENIV03190 for ; Fri, 6 Jul 2001 07:23:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA1125897 for ; Fri, 6 Jul 2001 16:23:19 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2342064; Fri, 6 Jul 2001 09:21:48 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA50827; Fri, 6 Jul 2001 09:21:48 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66ENgS08175; Fri, 6 Jul 2001 09:23:42 -0500 Message-Id: <200107061423.f66ENgS08175@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Yahya cc: linux-xfs@oss.sgi.com Subject: Re: Help In-Reply-To: Message from Yahya of "Fri, 06 Jul 2001 05:39:20 +0700." <5.1.0.14.2.20010706053818.031220e0@pop.cbn.net.id> Date: Fri, 06 Jul 2001 09:23:41 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I got this error in my box, using kernel 2.4.5: > > [root@home3 /]# mount /dev/rd/c0d0p1 /home/ > mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d0p1, > or too many mounted file systems > > -- from /var/log/messages: > > Start mounting filesystem: dac960(48,1) > Starting XFS recovery on filesystem: dac960(48,1) (dev: 48/1) > XFS: xlog_recover_process_data: bad clientid > XFS: log mount/recovery failed > XFS: log mount failed > Start mounting filesystem: dac960(48,1) > Starting XFS recovery on filesystem: dac960(48,1) (dev: 48/1) > XFS: xlog_recover_process_data: bad clientid > XFS: log mount/recovery failed > XFS: log mount failed > > how to recover the filesystem? thanks. Ugh, can you try running xfs_logprint -t /dev/rd/c0d0p1 and sending me the output. Basically it looks like the log data is corrupted. I think your best bet in the end will be to run xfs_repair on the device, when you do please send me the output that produces as well. Steve > > Regards. > Yahya. From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:25:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66EP9P03417 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:25:09 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66EP7V03408 for ; Fri, 6 Jul 2001 07:25:07 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA07578 for ; Fri, 6 Jul 2001 07:25:06 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2356287; Fri, 6 Jul 2001 09:23:38 -0500 (CDT) Received: from sgi.com (lite.americas.sgi.com [128.162.187.4]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA92541; Fri, 6 Jul 2001 09:23:38 -0500 (CDT) Message-ID: <3B45C96D.D76BE29C@sgi.com> Date: Fri, 06 Jul 2001 09:21:33 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-xfs-1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: Mathias Herberts CC: linux-xfs@oss.sgi.com Subject: Re: XFS compatibility with 2.4.6 References: <3B45675A.5EEDBD0F@cmb.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mathias Herberts wrote: > The 2.4.5 patch worked ok with the 2.4.5 kernel, but the 2.4.6 patch > seems to be broken. Details, please! -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:35:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66EZVG04185 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:35:31 -0700 Received: from mercury.pricegrabber.com ([64.70.41.138]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66EZUV04182 for ; Fri, 6 Jul 2001 07:35:30 -0700 Received: from pricegrabber.com (noc.pricegrabber.com [24.8.138.101] (may be forged)) (authenticated) by mercury.pricegrabber.com (8.11.2/8.11.2) with ESMTP id f66EZVN26425 for ; Fri, 6 Jul 2001 07:35:31 -0700 Message-ID: <3B45CCB3.1090107@pricegrabber.com> Date: Fri, 06 Jul 2001 07:35:31 -0700 From: Christopher McCrory Organization: Pricegrabber.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010702 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs list Subject: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello... Sorry for the delay in sending this, I should have sent it last week. Two bugs: 1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid modules (aacraid is for adaptec oem hardware raid, used in all/most dell servers) 2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my production web servers running XFS. After ~15 minutes it crashed. I got someone to go to the colo and reset it. I watched it for a while and ~15 minutes later the load started shooting through the roof (~150). I took it out of the web rotation before it crashed and restarted back with kernel-smp-2.4.2-SGI_XFS_1.0. Now it is stable again. -- Christopher McCrory "The guy that keeps the servers running" chrismcc@pricegrabber.com http://www.pricegrabber.com I don't make jokes in base 13. Anyone who does should get help. --Douglas Adams From owner-linux-xfs@oss.sgi.com Fri Jul 6 07:59:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66Exa405791 for linux-xfs-outgoing; Fri, 6 Jul 2001 07:59:36 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66ExYV05788 for ; Fri, 6 Jul 2001 07:59:34 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f66ExSq11576 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 10:59:28 -0400 Date: Fri, 6 Jul 2001 10:59:28 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: Scsi Generic patch Message-ID: <20010706105928.A11573@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The Scsi Generic deadlock patch has made it into CVS. Steve, did you do it, or did Linus catch up? Either way, that bug is squashed. :) -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:05:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66F5mO06287 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:05:48 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66F5lV06284 for ; Fri, 6 Jul 2001 08:05:47 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA10944 for ; Fri, 6 Jul 2001 08:05:39 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2355244; Fri, 6 Jul 2001 10:04:29 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA81293; Fri, 6 Jul 2001 10:04:29 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66F6Ma08685; Fri, 6 Jul 2001 10:06:22 -0500 Message-Id: <200107061506.f66F6Ma08685@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrei Pelinescu-Onciul cc: linux-xfs@oss.sgi.com Subject: Re: libgdbm open & xfs problems In-Reply-To: Message from Andrei Pelinescu-Onciul of "Fri, 06 Jul 2001 16:06:50 +0200." <3B45C5FA.BAC5FB56@fokus.gmd.de> Date: Fri, 06 Jul 2001 10:06:22 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a very odd problem as stripe alignment should make no visible difference at the system call level. Can you please rerun the ltrace with the -S option to include system call output as well. We will attempt to replicate here. Thanks Steve > > > I have encountered a strange problem trying to build a nis database on > a xfs partition. For some values of sunit and swidth I cannot build the > database. > > For example: > echo "test test" | /usr/lib/yp/makedbm - /tmp/x > > fails with makedbm: Cannot open /tmp/x~. > I've traced it down to a call to gdbm_open which fails. > > The strange thing is that if I mount the xfs filesystem with noalign, or > I use mkfs.xfs with sunit=0 and swidth=0 it works. > > It works also for mkfs.xfs -f -d sunit=128,swidth=256, but it does not > work for > mkfs.xfs -f -d sunit=128,swidth=384. > > I tested it with 2.4.2-xfs, 2.4.6-pre3-xfs and 2.4.7-pre3-xfs. > I use libgdbm 1.7.3. > > > ltrace /usr/lib/yp/makedbm /tmp/test /var/tmp/x > [...] > fopen("/tmp/test", "r") = 0x0804b2b8 > calloc(1, 13) = 0x0804b428 > sprintf("/var/tmp/x~", "%s~", "/var/tmp/x") = 11 > gdbm_open(0x0804b428, 0, 19, 384, 0) = 0 > (here it fails, gdbm_open should return non-null) > > > strace /usr/lib/yp/makedbm /tmp/test /var/tmp/x > [...] > open("/tmp/test", O_RDONLY) = 3 > open("/var/tmp/x~", O_RDWR|O_CREAT, 0600) = 4 > fstat64(4, {st_mode=S_IFREG|0600, st_size=0, ...}) = 0 > fcntl64(0x4, 0x6, 0xbffffb54, 0xbffffb64) = 0 > old_mmap(NULL, 200704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, > -1, 0) = 0x4014b000 > fsync(4) = 0 > fcntl64(0x4, 0x6, 0xbffffadc, 0x40000) = 0 > close(4) = 0 > munmap(0x4014b000, 200704) = 0 > write(2, "makedbm: Cannot open /var/tmp/x~" > [...] > > > > Andrei From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:14:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FEGg06811 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:14:16 -0700 Received: from biobio.vexcel.com (biobio.vexcel.com [192.92.90.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FEEV06808 for ; Fri, 6 Jul 2001 08:14:14 -0700 Received: from [192.168.1.17] (router.vexcel.com [192.92.90.254]) by biobio.vexcel.com (8.9.3+Sun/8.9.1) with ESMTP id JAA04614; Fri, 6 Jul 2001 09:14:07 -0600 (MDT) Mime-Version: 1.0 X-Sender: brissing@mail.vexcel.com (Unverified) Message-Id: In-Reply-To: References: Date: Fri, 6 Jul 2001 09:07:04 -0600 To: , martin@tradepage.co.za From: Dean Brissinger Subject: Re: no keyboard Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I also have this problem on a Pentium 2 system (IWILL mainboard). Using USB keyboard/mouse works, but PS/2 doesn't. PS/2 works until X starts. The X server seems to cause the problem. I didn't find a cure and stuck with my USB devices. It doesn't appear to be devfs or XFS related, just some conflict with XFree and PS/2 on my mainboard. Unimportant to me but you could post to an XFree bug list if your problems persist. At 11:43 AM +0200 7/6/01, Martin Potgieter wrote: >I recently installed Redhat 7.1 with XFS support from the ISO installer I >downloaded. The installation went smooth all the way through. When I >rebooted all seemed fine aswell but when I came to the login prompt the >keyboard was not responding. When I did the install I selected the default >keyboard. I had Redhat running on the same machine without the XFS support >and all worked ok so I assume it has something to do with the XFS support. >I changed the keyboard 3 times to no avail. I ssh'ed into the machine and >launched KDE which fired up with the mouse working fine but also no >keyboard. >I am using > >PC Chips m726 MB >128m ram >4.3 gig conner hd >generic serial mouse >36x samsung cdrom >realtek 8129 NIC > > >Any help will be appreciated > > >Martin Potgieter -- . . . . . . . . ooo . . . . ooo . . . . . . . . . . . . Dean Brissinger - Systems Administrator . . Direct: 303-583-0278 Main: 303-444-0094 . . Fax: 303-583-0246 http://www.vexcel.com/ . . . . . . . . . . oOOo . . A . . oOOo . . . . . . . . 0 0 '```` From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:15:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FF3I06944 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:15:03 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FF2V06941 for ; Fri, 6 Jul 2001 08:15:02 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA04341 for ; Fri, 6 Jul 2001 08:12:22 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2357543; Fri, 6 Jul 2001 10:13:46 -0500 (CDT) Received: from sgi.com (lite.americas.sgi.com [128.162.187.4]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA93906; Fri, 6 Jul 2001 10:13:45 -0500 (CDT) Message-ID: <3B45D52C.D3B03246@sgi.com> Date: Fri, 06 Jul 2001 10:11:40 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-xfs-1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: Christopher McCrory CC: linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report References: <3B45CCB3.1090107@pricegrabber.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Christopher McCrory wrote: > 1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid > modules (aacraid is for adaptec oem hardware raid, used in all/most dell > servers) Hm, is aacraid even in 2.4.5? A grep through arch/i386/defconfig, drivers/scsi/Config.in, and drivers/scsi/aic7xxx/Config.in don't show any AACRAID entry.... > 2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my > production web servers running XFS. After ~15 minutes it crashed. I > got someone to go to the colo and reset it. I watched it for a while > and ~15 minutes later the load started shooting through the roof (~150). > I took it out of the web rotation before it crashed and restarted back > with kernel-smp-2.4.2-SGI_XFS_1.0. Now it is stable again. Not sure what to tell you on this one... any more info you can provide? -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:15:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FFKO07049 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:15:20 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FFJV07038 for ; Fri, 6 Jul 2001 08:15:19 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA08217 for ; Fri, 6 Jul 2001 08:12:39 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2332956 for ; Fri, 6 Jul 2001 10:14:02 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA63534 for ; Fri, 6 Jul 2001 10:14:02 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f66FFtV08770; Fri, 6 Jul 2001 10:15:55 -0500 Message-Id: <200107061515.f66FFtV08770@jen.americas.sgi.com> Date: Fri, 6 Jul 2001 10:15:55 -0500 Subject: TAKE - yet more out of memory handling cleanup Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is more logic to keep xfs functioning when memory is in short supply. It is still possible to push xfs into an oops if you try hard enough, but you have to do some really silly things now. Date: Fri Jul 6 07:31:37 PDT 2001 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:98353a linux/drivers/block/DAC960.c - 1.28 - Add BLKBSZGET which was missing for this driver. Subject: TAKE - Date: Fri Jul 6 08:12:37 PDT 2001 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:98356a linux/fs/pagebuf/page_buf.c - 1.92 - Fix the retry logic for failing to allocate a page, there was supposed to be a retry, but it was not quite there. On failure to allocate a page pagebuf will now start a flush of the delayed write metadata - which can free pages for reuse, pause, and retry. linux/fs/xfs_support/kmem.c - 1.10 - Remove some of the logic from the memory allocation retry logic, the underlying mechanisms are already doing this for us. From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:18:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FIff07311 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:18:41 -0700 Received: from sa-bwmail1.storageapps.com (smtp.storageapps.com [63.101.83.13]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FIeV07307 for ; Fri, 6 Jul 2001 08:18:40 -0700 Received: by SA-BWMAIL1 with Internet Mail Service (5.5.2653.19) id ; Fri, 6 Jul 2001 11:18:37 -0400 Message-ID: <23D04BDBA646D411BDDD00D0B774B539028C8A9B@SA-BWMAIL1> From: "Christian, Chip" To: "'Eric Sandeen'" , Christopher McCrory Cc: linux-xfs list Subject: RE: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report Date: Fri, 6 Jul 2001 11:18:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk It was added by RedHat, so I guess the expectation is that it exist in all kernel rpms? -----Original Message----- From: Eric Sandeen [mailto:sandeen@sgi.com] Sent: Friday, July 06, 2001 11:12 To: Christopher McCrory Cc: linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report Christopher McCrory wrote: > 1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid > modules (aacraid is for adaptec oem hardware raid, used in all/most dell > servers) Hm, is aacraid even in 2.4.5? A grep through arch/i386/defconfig, drivers/scsi/Config.in, and drivers/scsi/aic7xxx/Config.in don't show any AACRAID entry.... > 2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my > production web servers running XFS. After ~15 minutes it crashed. I > got someone to go to the colo and reset it. I watched it for a while > and ~15 minutes later the load started shooting through the roof (~150). > I took it out of the web rotation before it crashed and restarted back > with kernel-smp-2.4.2-SGI_XFS_1.0. Now it is stable again. Not sure what to tell you on this one... any more info you can provide? -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:23:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FNiE07663 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:23:44 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FNiV07659 for ; Fri, 6 Jul 2001 08:23:44 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA14180 for ; Fri, 6 Jul 2001 08:23:35 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2354591; Fri, 6 Jul 2001 10:22:26 -0500 (CDT) Received: from sgi.com (eagdhcp-187-26.americas.sgi.com [128.162.187.176]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA80797; Fri, 6 Jul 2001 10:22:26 -0500 (CDT) Message-ID: <3B45CFF5.C6D6B6E2@sgi.com> Date: Fri, 06 Jul 2001 09:49:25 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-21mdk_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "Christian, Chip" CC: Christopher McCrory , linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report References: <23D04BDBA646D411BDDD00D0B774B539028C8A9B@SA-BWMAIL1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Christian, Chip" wrote: > > It was added by RedHat, so I guess the expectation is that it exist in all kernel rpms? No, the 2.4.5 kernel RPMs are just vanilla 2.4.5 + XFS. The 2.4.3 RPMs are the only ones based on Red Hat kernels. -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:23:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FNlJ07710 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:23:47 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FNkV07695 for ; Fri, 6 Jul 2001 08:23:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA14189 for ; Fri, 6 Jul 2001 08:23:38 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2358005; Fri, 6 Jul 2001 10:22:26 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA82878; Fri, 6 Jul 2001 10:22:26 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66FOKr08831; Fri, 6 Jul 2001 10:24:20 -0500 Message-Id: <200107061524.f66FOKr08831@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Christian, Chip" cc: "'Eric Sandeen'" , Christopher McCrory , linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report In-Reply-To: Message from "Christian, Chip" of "Fri, 06 Jul 2001 11:18:36 EDT." <23D04BDBA646D411BDDD00D0B774B539028C8A9B@SA-BWMAIL1> Date: Fri, 06 Jul 2001 10:24:20 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > It was added by RedHat, so I guess the expectation is that it exist in all ke > rnel rpms? The 2.4.5 based kernel RPMs do not include any redhat patches, they are just a base kernel + XFS. Attempting to integrate redhat's patch set into a different kernel base is like juggling spaghetti! Steve > > -----Original Message----- > From: Eric Sandeen [mailto:sandeen@sgi.com] > Sent: Friday, July 06, 2001 11:12 > To: Christopher McCrory > Cc: linux-xfs list > Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report > > > Christopher McCrory wrote: > > > 1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid > > modules (aacraid is for adaptec oem hardware raid, used in all/most dell > > servers) > > Hm, is aacraid even in 2.4.5? A grep through arch/i386/defconfig, > drivers/scsi/Config.in, and drivers/scsi/aic7xxx/Config.in don't show > any AACRAID entry.... > > > 2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my > > production web servers running XFS. After ~15 minutes it crashed. I > > got someone to go to the colo and reset it. I watched it for a while > > and ~15 minutes later the load started shooting through the roof (~150). > > I took it out of the web rotation before it crashed and restarted back > > with kernel-smp-2.4.2-SGI_XFS_1.0. Now it is stable again. > > Not sure what to tell you on this one... any more info you can provide? > > -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:28:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FStn08108 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:28:55 -0700 Received: from sa-bwmail1.storageapps.com (smtp.storageapps.com [63.101.83.13]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FSsV08105 for ; Fri, 6 Jul 2001 08:28:54 -0700 Received: by SA-BWMAIL1 with Internet Mail Service (5.5.2653.19) id ; Fri, 6 Jul 2001 11:28:51 -0400 Message-ID: <23D04BDBA646D411BDDD00D0B774B539028C8A9C@SA-BWMAIL1> From: "Christian, Chip" To: "'Steve Lord'" , "Christian, Chip" Cc: "'Eric Sandeen'" , Christopher McCrory , linux-xfs list Subject: RE: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report Date: Fri, 6 Jul 2001 11:28:50 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk That's for damn sure. -----Original Message----- From: Steve Lord [mailto:lord@sgi.com] Sent: Friday, July 06, 2001 11:24 To: Christian, Chip Cc: 'Eric Sandeen'; Christopher McCrory; linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report > It was added by RedHat, so I guess the expectation is that it exist in all ke > rnel rpms? The 2.4.5 based kernel RPMs do not include any redhat patches, they are just a base kernel + XFS. Attempting to integrate redhat's patch set into a different kernel base is like juggling spaghetti! Steve > > -----Original Message----- > From: Eric Sandeen [mailto:sandeen@sgi.com] > Sent: Friday, July 06, 2001 11:12 > To: Christopher McCrory > Cc: linux-xfs list > Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report > > > Christopher McCrory wrote: > > > 1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid > > modules (aacraid is for adaptec oem hardware raid, used in all/most dell > > servers) > > Hm, is aacraid even in 2.4.5? A grep through arch/i386/defconfig, > drivers/scsi/Config.in, and drivers/scsi/aic7xxx/Config.in don't show > any AACRAID entry.... > > > 2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my > > production web servers running XFS. After ~15 minutes it crashed. I > > got someone to go to the colo and reset it. I watched it for a while > > and ~15 minutes later the load started shooting through the roof (~150). > > I took it out of the web rotation before it crashed and restarted back > > with kernel-smp-2.4.2-SGI_XFS_1.0. Now it is stable again. > > Not sure what to tell you on this one... any more info you can provide? > > -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:31:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FVDr08333 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:31:13 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FVCV08327 for ; Fri, 6 Jul 2001 08:31:12 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA1116262 for ; Fri, 6 Jul 2001 17:31:21 +0200 (CEST) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA12760; Fri, 6 Jul 2001 10:29:29 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15IXXs-00029e-00; Fri, 06 Jul 2001 10:29:28 -0500 Date: Fri, 6 Jul 2001 10:29:28 -0500 From: Nathan Straz To: Christopher McCrory Cc: linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report Message-ID: <20010706102928.L883@sgi.com> Mail-Followup-To: Christopher McCrory , linux-xfs list References: <3B45CCB3.1090107@pricegrabber.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B45CCB3.1090107@pricegrabber.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 06, 2001 at 07:35:31AM -0700, Christopher McCrory wrote: > 2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my > production web servers running XFS. After ~15 minutes it crashed. I > got someone to go to the colo and reset it. I watched it for a while > and ~15 minutes later the load started shooting through the roof (~150). Did you get a look at the process table before you took the machine down? Theorically, if some of the Apache processes hit a common deadlock, it would keep spawning new servers which would hit the same deadlock and the load would skyrocket like you describe. I don't remember if kdb is in PR3, but if you could get a back trace of the deadlocked processes, that might be helpful. -- 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 Jul 6 08:33:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66FX9u08526 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:33:09 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FX8V08521 for ; Fri, 6 Jul 2001 08:33:08 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id RAA08495; Fri, 6 Jul 2001 17:32:59 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706173005.02fc4558@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 17:32:51 +0200 To: Christopher McCrory , linux-xfs list From: Seth Mos Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report In-Reply-To: <3B45CCB3.1090107@pricegrabber.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 07:35 6-7-2001 -0700, Christopher McCrory wrote: >Hello... > > Sorry for the delay in sending this, I should have sent it last > week. Two bugs: > >1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid >modules (aacraid is for adaptec oem hardware raid, used in all/most dell >servers) Patches can be found on http://domsch.com/linux/ Matt Domsch has patches for these raid controllers. I will have to see if I can make a decent patch fit and make a clean patch. >2: I tried kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3.i686.rpm on one of my >production web servers running XFS. After ~15 minutes it crashed. I got >someone to go to the colo and reset it. I watched it for a while and ~15 >minutes later the load started shooting through the roof (~150). I took >it out of the web rotation before it crashed and restarted back with >kernel-smp-2.4.2-SGI_XFS_1.0. Now it is stable again. More details please, what does it do beside webserving in what setup is the machine configured. Do the logfiles or dmesg have any messages, are there hung processes is this a highmem machine? Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:36:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66Fadb08811 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:36:39 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FadV08808 for ; Fri, 6 Jul 2001 08:36:39 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA18477 for ; Fri, 6 Jul 2001 08:36:30 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2356668; Fri, 6 Jul 2001 10:35:21 -0500 (CDT) Received: from sgi.com (eagdhcp-187-26.americas.sgi.com [128.162.187.176]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA05055; Fri, 6 Jul 2001 10:35:20 -0500 (CDT) Message-ID: <3B45DAC2.209E6B94@sgi.com> Date: Fri, 06 Jul 2001 10:35:30 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-21mdk_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nathan Straz CC: Christopher McCrory , linux-xfs@oss.sgi.com Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report References: <3B45CCB3.1090107@pricegrabber.com> <20010706102928.L883@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Straz wrote: > I don't remember if kdb is in PR3, but if you could get a back trace of > the deadlocked processes, that might be helpful. It is. -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 08:36:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66Faql08903 for linux-xfs-outgoing; Fri, 6 Jul 2001 08:36:52 -0700 Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66FanV08882 for ; Fri, 6 Jul 2001 08:36:49 -0700 Received: from fokus.gmd.de (dorian [193.175.135.179]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id RAA22317; Fri, 6 Jul 2001 17:36:43 +0200 (MET DST) Message-ID: <3B45DB0B.611C18B1@fokus.gmd.de> Date: Fri, 06 Jul 2001 17:36:43 +0200 From: Andrei Pelinescu-Onciul X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre3-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: libgdbm open & xfs problems References: <200107061506.f66F6Ma08685@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > > This is a very odd problem as stripe alignment should make no visible > difference at the system call level. Can you please rerun the ltrace > with the -S option to include system call output as well. We will attempt > to replicate here. > 1. the not-working case mount /dev/sda10 /tmp ltrace -S /usr/lib/yp/makedbm /tmp/test /tmp/x [...] fopen("/tmp/test", "r" SYS_brk(NULL) = 0x0804b2b0 SYS_brk(0x0804b430) = 0x0804b430 SYS_brk(0x0804c000) = 0x0804c000 SYS_open("/tmp/test", 0, 0666) = 3 <... fopen resumed> ) = 0x0804b2b8 calloc(1, 9) = 0x0804b428 sprintf("/tmp/x~", "%s~", "/tmp/x") = 7 gdbm_open(0x0804b428, 0, 19, 384, 0 SYS_open("/tmp/x~", 66, 0600) = 4 SYS_fstat64(4, 0xbffffa6c, 0x0804b438, 0xbffffb84, 4) = 0 SYS_fcntl64(4, 6, 0xbffffb74, 0xbffffb84, 4) = 0 SYS_mmap(0xbffffa64, 196616, 0x40145b2c, 200704, 0x80000000) = 0x4014b000 SYS_fsync(4, 0x0804b438, 0x40033af8, 262144, 0x0804b438) = 0 SYS_fcntl64(4, 6, 0xbffffafc, 262144, 4) = 0 SYS_close(4) = 0 SYS_munmap(0x4014b000, 200704) = 0 <... gdbm_open resumed> ) = 0 fprintf(0x40143a40, "makedbm: Cannot open %s\n", "/tmp/x~" [...] 2. the working case umount /tmp mount /dev/sda10 /tmp -o noalign ltrace -S /usr/lib/yp/makedbm /tmp/test /tmp/x [...] fopen("/tmp/test", "r" SYS_brk(NULL) = 0x0804b2b0 SYS_brk(0x0804b430) = 0x0804b430 SYS_brk(0x0804c000) = 0x0804c000 SYS_open("/tmp/test", 0, 0666) = 3 <... fopen resumed> ) = 0x0804b2b8 calloc(1, 9) = 0x0804b428 sprintf("/tmp/x~", "%s~", "/tmp/x") = 7 gdbm_open(0x0804b428, 0, 19, 384, 0 SYS_open("/tmp/x~", 66, 0600) = 4 SYS_fstat64(4, 0xbffffa6c, 0x0804b438, 0xbffffb84, 4) = 0 SYS_fcntl64(4, 6, 0xbffffb74, 0xbffffb84, 4) = 0 SYS_brk(0x0804e000) = 0x0804e000 SYS_write(4, "\316\232W\023", 4096) = 4096 SYS_write(4, "", 4096) = 4096 SYS_write(4, "\001", 4096) = 4096 SYS_fsync(4, 0x0804b438, 0x40033af8, 0x0804b438, 0x0804b438) = 0 <... gdbm_open resumed> ) = 0x0804b438 (gdbm_open !=0 =>ok) gdbm_store(0x0804b438, 0x08049d14, 14, 0xbffffcf8, 8 [...] After the first fcntl64 the two traces are different. xfs_info /tmp meta-data=/tmp isize=256 agcount=8, agsize=15568 blks data = bsize=4096 blocks=124495, imaxpct=25 = sunit=16 swidth=48 blks, unwritten=0 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=4096 realtime =none extsz=65536 blocks=0, rtextents=0 Andrei From owner-linux-xfs@oss.sgi.com Fri Jul 6 09:46:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66GkIK11013 for linux-xfs-outgoing; Fri, 6 Jul 2001 09:46:18 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66GkGV11010 for ; Fri, 6 Jul 2001 09:46:16 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA24441; Fri, 6 Jul 2001 18:46:12 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706181241.00b5f188@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 18:17:50 +0200 To: Christopher McCrory , linux-xfs list From: Seth Mos Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report In-Reply-To: <4.3.2.7.2.20010706173005.02fc4558@pop.xs4all.nl> References: <3B45CCB3.1090107@pricegrabber.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:32 6-7-2001 +0200, Seth Mos wrote: >At 07:35 6-7-2001 -0700, Christopher McCrory wrote: >>Hello... >> >> Sorry for the delay in sending this, I should have sent it last >> week. Two bugs: >> >>1: kernel-2.4.5-SGI_XFS_1.0.1_PR3.i{3,5,6}86.rpm is missing the aacraid >>modules (aacraid is for adaptec oem hardware raid, used in all/most dell >>servers) > >Patches can be found on http://domsch.com/linux/ >Matt Domsch has patches for these raid controllers. > >I will have to see if I can make a decent patch fit and make a clean patch. I just looked and they have patches for everything ranging from 2.4.2 to 2.4.6 So I guess that it should be able to apply against the CVS tree or the 1.0.1 RPMS. The question is, is it already in the 2.4.3 kernel? I didn't noticed it being available yet. However the driver still is a port from the NT driver to Solaris to Linux. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:06:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66H6fs11359 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:06:41 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66H6cV11356 for ; Fri, 6 Jul 2001 10:06:38 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id B03911AB0F for ; Fri, 6 Jul 2001 13:06:37 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 192F58B2; Fri, 6 Jul 2001 13:06:36 -0400 (EDT) Date: Fri, 6 Jul 2001 13:06:36 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: More on write caching Message-ID: <20010706130636.C2814@dkp.com> 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.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've asked about write caching before, and now I've got another question. If I've got write caching turned on, and the power goes out, do I face the possibility of silent metadata corruption? With ext2, the fsck would attempt to fix metadata problems on bootup; on the other hand, with xfs, if write caching resulted in a corrupted log, would the simple log replay that xfs does on mount perhaps fail to catch possible metadata problems? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:29:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HTNU11727 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:29:23 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HTMV11724 for ; Fri, 6 Jul 2001 10:29:22 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Fri, 6 Jul 2001 10:26:59 -0700 Subject: Re: question about repartitioning/resizing XFS From: Thomas Duffy To: Deniz Akkus Kanca Cc: linux-xfs@oss.sgi.com In-Reply-To: <04cb01c105f3$41631990$0300a8c0@ergenekon> References: <04cb01c105f3$41631990$0300a8c0@ergenekon> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 06 Jul 2001 10:28:00 -0700 Message-Id: <994440480.10317.7.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 06 Jul 2001 17:26:59.0985 (UTC) FILETIME=[DD144010:01C10640] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 06 Jul 2001 11:11:22 +0300, Deniz Akkus Kanca wrote: > Due to performance issues I need to increase RAM to 2 Gig and consequently > increase the swap space to 4 Gig. your best bet is probably to just create a SWAP file on the xfs partition. in order to do this, dd if=/dev/zero of=/SWAP bs=1k count=2147483648. then mkswap it and add an entry to your /etc/fstab. that way, you do not need to move any partitions around. -tduffy From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:33:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HXJF11882 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:33:19 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HXIV11879 for ; Fri, 6 Jul 2001 10:33:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA05782 for ; Fri, 6 Jul 2001 10:30:32 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2359830; Fri, 6 Jul 2001 12:31:44 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA54410; Fri, 6 Jul 2001 12:31:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66HXbW09207; Fri, 6 Jul 2001 12:33:37 -0500 Message-Id: <200107061733.f66HXbW09207@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Thomas Duffy cc: Deniz Akkus Kanca , linux-xfs@oss.sgi.com Subject: Re: question about repartitioning/resizing XFS In-Reply-To: Message from Thomas Duffy of "06 Jul 2001 10:28:00 PDT." <994440480.10317.7.camel@tduffy-lnx.afara.com> Date: Fri, 06 Jul 2001 12:33:37 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On 06 Jul 2001 11:11:22 +0300, Deniz Akkus Kanca wrote: > > > Due to performance issues I need to increase RAM to 2 Gig and consequently > > increase the swap space to 4 Gig. > > your best bet is probably to just create a SWAP file on the xfs partition. i > n > order to do this, dd if=/dev/zero of=/SWAP bs=1k count=2147483648. then mksw > ap > it and add an entry to your /etc/fstab. > > that way, you do not need to move any partitions around. > > -tduffy Good idea, and if you use a big dd block size on an idle system, and type sync afterwards, there is a good chance XFS will lay out the swap file almost contiguous on disk. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:38:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HcKg12056 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:38:20 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HcIV12053 for ; Fri, 6 Jul 2001 10:38:19 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA1135811 for ; Fri, 6 Jul 2001 19:38:21 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2361310; Fri, 6 Jul 2001 12:36:59 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA09249; Fri, 6 Jul 2001 12:36:59 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66Hcpb09219; Fri, 6 Jul 2001 12:38:51 -0500 Message-Id: <200107061738.f66Hcpb09219@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Klaassen cc: linux-xfs@oss.sgi.com Subject: Re: More on write caching In-Reply-To: Message from Andrew Klaassen of "Fri, 06 Jul 2001 13:06:36 EDT." <20010706130636.C2814@dkp.com> Date: Fri, 06 Jul 2001 12:38:51 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I've asked about write caching before, and now I've got another > question. > > If I've got write caching turned on, and the power goes out, do > I face the possibility of silent metadata corruption? > > With ext2, the fsck would attempt to fix metadata problems on > bootup; on the other hand, with xfs, if write caching resulted > in a corrupted log, would the simple log replay that xfs does on > mount perhaps fail to catch possible metadata problems? Yes, and the same will be true for all write behind journalled filesystems, if the log does not make it to disk when the driver says it has then in theory a subsequent metadata write could make it out to the media. A crash at this point would mean that part of a transaction had made it to disk, but the rest which only existed in the disks internal cache would not. I would expect reiserfs, ext3 and jfs would all have the same issue. So I would not in general recommend write caching on a device, unless you know enough about it to be satisfied that its cache makes it out to disk on power down. Using the rotational power of the spindle to generate power to move the head to a special track and flush the cache is not unheard of for instance. Steve > > Andrew Klaassen From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:38:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HcfH12149 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:38:41 -0700 Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HcdV12146 for ; Fri, 6 Jul 2001 10:38:40 -0700 Received: from fokus.gmd.de (dorian [193.175.135.179]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id TAA13186; Fri, 6 Jul 2001 19:38:33 +0200 (MET DST) Message-ID: <3B45F799.E92C0CD@fokus.gmd.de> Date: Fri, 06 Jul 2001 19:38:33 +0200 From: Andrei Pelinescu-Onciul X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre3-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: libgdbm open & xfs problems References: <200107061506.f66F6Ma08685@jen.americas.sgi.com> <3B45DB0B.611C18B1@fokus.gmd.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I think I've found the problem. It's not an xfs bug, is a bug in libgdbm, gdbm_open: dbf->header->dir_size = 8 * sizeof (off_t); [...] while (dbf->header->dir_size < dbf->header->block_size) { dbf->header->dir_size <<= 1; dbf->header->dir_bits += 1; } /* Check for correct block_size. */ if (dbf->header->dir_size != dbf->header->block_size) { gdbm_close (dbf); gdbm_errno = GDBM_BLOCK_SIZE_ERROR; return NULL; } The initial dir_size is 8*4=32. dbf->header->block_size is the io block size returned by fstat. On my partition I use swidth=384 => block_size = 196608 = 3 * 65536. But in the piece of code above dir_size can be only of the form 2^n (dir_size<<=1), so in my case it will be always different from block_size :( I have to report this to libgdbm developers. Andrei From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:44:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HipJ12353 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:44:51 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HioV12350 for ; Fri, 6 Jul 2001 10:44:50 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id KAA29786 for ; Fri, 6 Jul 2001 10:44:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2361735; Fri, 6 Jul 2001 12:43:29 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA78987; Fri, 6 Jul 2001 12:43:29 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66HjLT09239; Fri, 6 Jul 2001 12:45:21 -0500 Message-Id: <200107061745.f66HjLT09239@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrei Pelinescu-Onciul cc: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: libgdbm open & xfs problems In-Reply-To: Message from Andrei Pelinescu-Onciul of "Fri, 06 Jul 2001 19:38:33 +0200." <3B45F799.E92C0CD@fokus.gmd.de> Date: Fri, 06 Jul 2001 12:45:21 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > I think I've found the problem. > It's not an xfs bug, is a bug in libgdbm, gdbm_open: > > dbf->header->dir_size = 8 * sizeof (off_t); > [...] > > while (dbf->header->dir_size < dbf->header->block_size) > { > dbf->header->dir_size <<= 1; > dbf->header->dir_bits += 1; > } > > /* Check for correct block_size. */ > if (dbf->header->dir_size != dbf->header->block_size) > { > gdbm_close (dbf); > gdbm_errno = GDBM_BLOCK_SIZE_ERROR; > return NULL; > } > > The initial dir_size is 8*4=32. dbf->header->block_size is the io block > size returned by fstat. > On my partition I use swidth=384 => block_size = 196608 = 3 * 65536. > But in the piece of code above dir_size can be only of the form 2^n > (dir_size<<=1), so in my case it will be always different from > block_size :( > > I have to report this to libgdbm developers. OK, good to hear, I suspect they may question the block_size being returned, but since this is supposed to be the optimal size for disk I/O and not an actual filesystem blocksize you are correct here. By the way, you are going to get some really big and inefficient dbm files on this filesystem, xfs used to default to reporting 64K and people complained about the time taken to rebuild an rpm database. Changing the default to be 4K, which is more in tune with reality in the linux implementation, fixed this. You might want to suggest to them that they put some sort of cap on the block size they use rather than blindly following the value reported by the kernel. Steve > > > Andrei From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:51:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HpvP12608 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:51:57 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HptV12605 for ; Fri, 6 Jul 2001 10:51:55 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id E92A51AB10 for ; Fri, 6 Jul 2001 13:51:54 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id AF6D68B2; Fri, 6 Jul 2001 13:51:54 -0400 (EDT) Date: Fri, 6 Jul 2001 13:51:54 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: More on write caching Message-ID: <20010706135154.D2814@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107061738.f66Hcpb09219@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107061738.f66Hcpb09219@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 06, 2001 at 12:38:51PM -0500, Steve Lord wrote: > > With ext2, the fsck would attempt to fix metadata problems > > on bootup; on the other hand, with xfs, if write caching > > resulted in a corrupted log, would the simple log replay > > that xfs does on mount perhaps fail to catch possible > > metadata problems? > Yes, and the same will be true for all write behind journalled > filesystems, if the log does not make it to disk when the > driver says it has then in theory a subsequent metadata write > could make it out to the media. A crash at this point would > mean that part of a transaction had made it to disk, but the > rest which only existed in the disks internal cache would not. I assume that a manual xfs_repair would be needed at that point... (?) Andrew Klaassen From owner-linux-xfs@oss.sgi.com Fri Jul 6 10:55:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66HtlV12731 for linux-xfs-outgoing; Fri, 6 Jul 2001 10:55:47 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66HtkV12728 for ; Fri, 6 Jul 2001 10:55:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id KAA03911 for ; Fri, 6 Jul 2001 10:55:35 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2358454; Fri, 6 Jul 2001 12:54:23 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA08189; Fri, 6 Jul 2001 12:54:23 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66HuF109266; Fri, 6 Jul 2001 12:56:15 -0500 Message-Id: <200107061756.f66HuF109266@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Klaassen cc: linux-xfs@oss.sgi.com Subject: Re: More on write caching In-Reply-To: Message from Andrew Klaassen of "Fri, 06 Jul 2001 13:51:54 EDT." <20010706135154.D2814@dkp.com> Date: Fri, 06 Jul 2001 12:56:15 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Fri, Jul 06, 2001 at 12:38:51PM -0500, > Steve Lord wrote: > > > > With ext2, the fsck would attempt to fix metadata problems > > > on bootup; on the other hand, with xfs, if write caching > > > resulted in a corrupted log, would the simple log replay > > > that xfs does on mount perhaps fail to catch possible > > > metadata problems? > > > Yes, and the same will be true for all write behind journalled > > filesystems, if the log does not make it to disk when the > > driver says it has then in theory a subsequent metadata write > > could make it out to the media. A crash at this point would > > mean that part of a transaction had made it to disk, but the > > rest which only existed in the disks internal cache would not. > > I assume that a manual xfs_repair would be needed at that > point... (?) Yes, a full consistency check is the only way out of this situation, pretty much the same think fsck is doing on ext2. Steve > > Andrew Klaassen From owner-linux-xfs@oss.sgi.com Fri Jul 6 11:15:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66IFgZ13150 for linux-xfs-outgoing; Fri, 6 Jul 2001 11:15:42 -0700 Received: from mercury.pricegrabber.com ([64.70.41.138]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66IFeV13147 for ; Fri, 6 Jul 2001 11:15:40 -0700 Received: from pricegrabber.com (noc.pricegrabber.com [24.8.138.101] (may be forged)) (authenticated) by mercury.pricegrabber.com (8.11.2/8.11.2) with ESMTP id f66IFeN29286 for ; Fri, 6 Jul 2001 11:15:41 -0700 Message-ID: <3B46004B.5000008@pricegrabber.com> Date: Fri, 06 Jul 2001 11:15:39 -0700 From: Christopher McCrory Organization: Pricegrabber.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010702 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs list Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello... To make it easier, I'll summarize several message posts: Steve Lord wrote: > The 2.4.5 based kernel RPMs do not include any redhat patches, they are > just a base kernel + XFS. Attempting to integrate redhat's patch set into > a different kernel base is like juggling spaghetti! D'oh. I should have actually looked at what was in them. I was guessing they were RH rawhide + XFS Eric Sandeen wrote: > Hm, is aacraid even in 2.4.5? From the other posts, apparently not. Oops Christian, Chip wrote: > It was added by RedHat, so I guess the expectation is that it exist in all kernel rpms? Actually, I thought they were in Linus's kernel already. Nathan Straz wrote: > Did you get a look at the process table before you took the machine > down? Theorically, if some of the Apache processes hit a common > deadlock, it would keep spawning new servers which would hit the same > deadlock and the load would skyrocket like you describe. > > I don't remember if kdb is in PR3, but if you could get a back trace of > the deadlocked processes, that might be helpful. Seth Mos wrote: > More details please, what does it do beside webserving in what setup is > the machine configured. > Do the logfiles or dmesg have any messages, are there hung processes is > this a highmem machine? This server is a web only server, part of a server farm behind a cisco LocalDirector. So if there was a php coding problem/apache problem, I would have probably seen it across all the servers. Also going back to XFS kernel rpm 1.0 made the problem go away. I have a devel machine I tested XFS on originally (and 1.0.1PR3 rpms). It runs fine. The server I had the problems on is a production server now. So I really can't test anything on it. No web trafic == No $$$ When this was happening, my main concern was getting the server back operational, not getting debug/process info. SOrry. But I did think it warrented at least a report to the developers. I'll try the next PR release and watch it. I'll try to be ready to get error messages and such. -- Christopher McCrory "The guy that keeps the servers running" chrismcc@pricegrabber.com http://www.pricegrabber.com I don't make jokes in base 13. Anyone who does should get help. --Douglas Adams From owner-linux-xfs@oss.sgi.com Fri Jul 6 11:37:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66Ib1H13826 for linux-xfs-outgoing; Fri, 6 Jul 2001 11:37:01 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66Ib0V13823 for ; Fri, 6 Jul 2001 11:37:00 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA00883; Fri, 6 Jul 2001 20:36:54 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706203315.02f8ef68@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 20:36:45 +0200 To: Christopher McCrory , linux-xfs list From: Seth Mos Subject: Re: kernel-smp-2.4.3-SGI_XFS_1.0.1_PR3 bug report In-Reply-To: <3B46004B.5000008@pricegrabber.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:15 6-7-2001 -0700, Christopher McCrory wrote: >Hello... > > To make it easier, I'll summarize several message posts: >Eric Sandeen wrote: > > Hm, is aacraid even in 2.4.5? > From the other posts, apparently not. Oops It probably won't be untill a rewrite of the driver. >Christian, Chip wrote: > > > It was added by RedHat, so I guess the expectation is that it exist in > all kernel rpms? > >Actually, I thought they were in Linus's kernel already. You've ever seen the driver?? Don't it will make your stomach turn. A ported NT driver is not and will not be included in the kernel. They are going to build a native linux driver but it will probably take a lot of time before that ever sees the daylight. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 11:51:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66IpVe14211 for linux-xfs-outgoing; Fri, 6 Jul 2001 11:51:31 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66IpUV14208 for ; Fri, 6 Jul 2001 11:51:30 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA01545 for ; Fri, 6 Jul 2001 11:48:51 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2353242 for ; Fri, 6 Jul 2001 13:50:14 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA39832 for ; Fri, 6 Jul 2001 13:50:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66Iq5r09647; Fri, 6 Jul 2001 13:52:05 -0500 Message-Id: <200107061852.f66Iq5r09647@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-xfs@oss.sgi.com Subject: XFS cvs updates Date: Fri, 06 Jul 2001 13:52:05 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We are experiencing technical difficulties (aka a head crash) and at the moment updates are not happening. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:00:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66K0KT15231 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:00:20 -0700 Received: from riadalxims03.clr.com ([164.57.13.77]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66K0IV15227 for ; Fri, 6 Jul 2001 13:00:19 -0700 Received: by RIADALXIMS03 with Internet Mail Service (5.5.2650.21) id ; Fri, 6 Jul 2001 15:03:18 -0500 Message-ID: From: Alan Eldridge To: "'linux-xfs@oss.sgi.com'" Subject: IBM DeveloperWorks: Advanced Filesystems on Linux article Date: Fri, 6 Jul 2001 15:01:04 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C10656.B2778FFE" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C10656.B2778FFE Content-Type: text/plain; charset="iso-8859-1" http://www-106.ibm.com/developerworks/linux/library/l-fs ------_=_NextPart_001_01C10656.B2778FFE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable IBM DeveloperWorks: Advanced Filesystems on Linux = article

http://www-106.ibm.com/developerworks/linux/library/l-= fs

------_=_NextPart_001_01C10656.B2778FFE-- From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:06:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66K6pA15371 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:06:51 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66K6oV15368 for ; Fri, 6 Jul 2001 13:06:50 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f66K6jx06231 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 16:06:45 -0400 Date: Fri, 6 Jul 2001 16:06:45 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: Sorry 'bout HTML crap Message-ID: <20010706160645.A6072@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I just sent a note to the list, with a link to an IBM devWorks article, from my office. Our mail system is MS Exchange-Me-For-A-Real-Mailer-Please. Apparently outlook included a bunch of html in a message that, to me, appeared to have 1 line of text. I know this because bernhard.erdmann's mailer just bounced it back to me. So, sorry 'bout that. I hate Outlook. Really. Here's the link, again, just for you, Bernhard :) http://www-106.ibm.com/developerworks/linux/library/l-fs -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:11:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KBB915519 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:11:11 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KB9V15516 for ; Fri, 6 Jul 2001 13:11:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id WAA1140278 for ; Fri, 6 Jul 2001 22:11:06 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2362356 for ; Fri, 6 Jul 2001 15:09:51 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA15116 for ; Fri, 6 Jul 2001 15:09:51 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f66KBg809932; Fri, 6 Jul 2001 15:11:42 -0500 Message-Id: <200107062011.f66KBg809932@jen.americas.sgi.com> Date: Fri, 6 Jul 2001 15:11:42 -0500 Subject: TAKE - fix repair bug Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Not a major problem, we just never walk down checking a specific part of the metadata (the unlinked inode list) without this change. Other code in repair deals with the unlinked inode. Date: Fri Jul 6 13:08:33 PDT 2001 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:98376a cmd/xfsprogs/repair/phase3.c - 1.3 - Fix negated case on check, gets rid of bogus error following ag xx unlinked list messages. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:15:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KFMP15654 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:15:22 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KFLV15651 for ; Fri, 6 Jul 2001 13:15:21 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA15436; Fri, 6 Jul 2001 22:15:17 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706221414.037a5730@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 22:15:08 +0200 To: Alan Eldridge , "'linux-xfs@oss.sgi.com'" From: Seth Mos Subject: Re: IBM DeveloperWorks: Advanced Filesystems on Linux article In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 15:01 6-7-2001 -0500, Alan Eldridge wrote: >http://www-106.ibm.com/developerworks/linux/library/l-fs > I have already sent them a feedback message with urls to the SGI XFS project page and the project status but have not received a reply yet. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:19:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KJ6F15791 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:19:06 -0700 Received: from wisdom.myplace.net (cc19815-a.zwoll1.ov.nl.home.com [212.204.138.247]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KJ5V15788 for ; Fri, 6 Jul 2001 13:19:05 -0700 Received: from ws1 (ws1.myplace.net [192.168.1.15]) by wisdom.myplace.net (Postfix) with SMTP id 7A5652008A for ; Fri, 6 Jul 2001 22:19:04 +0200 (CEST) Message-ID: <00d001c10658$e69ad500$0f01a8c0@ws1> From: "Bas" To: Subject: CVS Date: Fri, 6 Jul 2001 22:19:03 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I'm using XFS for a couple of months now and have had no real problems yet so, it rocks. I was wondering if it's possible to add another CVS tree, right now I've only got 2 options: an old kernel or a pre kernel (right ?). The other tree I would like to see is current kernel with enhancements. Is it possible ? Thanks, Bas. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:19:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KJDs15864 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:19:13 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KJCV15860 for ; Fri, 6 Jul 2001 13:19:12 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA06903 for ; Fri, 6 Jul 2001 13:19:04 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2358797; Fri, 6 Jul 2001 15:17:47 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA54667; Fri, 6 Jul 2001 15:17:47 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66KJcR09955; Fri, 6 Jul 2001 15:19:38 -0500 Message-Id: <200107062019.f66KJcR09955@jen.americas.sgi.com> To: Seth Mos cc: Alan Eldridge , "'linux-xfs@oss.sgi.com'" Subject: Re: IBM DeveloperWorks: Advanced Filesystems on Linux article References: <4.3.2.7.2.20010706221414.037a5730@pop.xs4all.nl> Comments: In-reply-to Seth Mos message dated "Fri, 06 Jul 2001 22:15:08 +0200." Date: Fri, 06 Jul 2001 15:19:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > At 15:01 6-7-2001 -0500, Alan Eldridge wrote: > > >http://www-106.ibm > .com/developerworks/linux/library/l-fs > > > > I have already sent them a feedback message with urls to the SGI XFS > project page and the project status but have not received a reply yet. > > Cheers > My take on this article when I saw it was it was the first in a series, and other filesystems would follow. There has been no contact from them however, which I hope there would be before releasing an article on xfs. Steve > > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:23:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KN8i16032 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:23:08 -0700 Received: from amoa.org (amoa.org [207.207.51.226]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KN6V16014 for ; Fri, 6 Jul 2001 13:23:06 -0700 Received: by amoa.org(Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) id 86256A81.0070057F ; Fri, 6 Jul 2001 15:23:34 -0500 X-Lotus-FromDomain: AMOA From: ctooley@amoa.org To: Steve Lord cc: Seth Mos , Alan Eldridge , "'linux-xfs@oss.sgi.com'" Message-ID: <86256A81.007004E4.00@amoa.org> Date: Fri, 6 Jul 2001 15:23:32 -0500 Subject: Re: IBM DeveloperWorks: Advanced Filesystems on Linux article Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The end of the article talked about it continuing with ReiserFS in the next article. That lead me to believe that it was going to be a series about how to use ReiserFS. Chris Steve Lord on 07/06/2001 03:19:38 PM To: Seth Mos cc: Alan Eldridge , "'linux-xfs@oss.sgi.com'" (bcc: Chris Tooley/AMOA) Subject Re: IBM DeveloperWorks: Advanced Filesystems : on Linux article > At 15:01 6-7-2001 -0500, Alan Eldridge wrote: > > >http://www-106.ibm > .com/developerworks/linux/library/l-fs > > > > I have already sent them a feedback message with urls to the SGI XFS > project page and the project status but have not received a reply yet. > > Cheers > My take on this article when I saw it was it was the first in a series, and other filesystems would follow. There has been no contact from them however, which I hope there would be before releasing an article on xfs. Steve > > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:23:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KN5Z16009 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:23:05 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KN4V16006 for ; Fri, 6 Jul 2001 13:23:04 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA16327 for ; Fri, 6 Jul 2001 22:23:02 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706221510.02feade0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 22:22:53 +0200 To: linux-xfs list From: Seth Mos Subject: 1.0.1 PR3 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have encountered a weird issue that after upgrading a 1.0 based system to 1.0.1 with the PR3 installer it waxed my lilo.conf The lilo.conf contained 2 entry's. One for booting windows and one for the 1.0 install kernel. After upgrading it installed everything OK but I had just 1 entry left in my lilo.conf which was the entry for booting windows. The kernel was installed OK and during the boot section of the installer I did see a linux entry and a dos entry and set the dos entry as default. My suprise was great when the system booted and lilo contained just one entry. I'll try a second time to reproduce it. Not sure what the problem is though. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:30:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KU4j16271 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:30:04 -0700 Received: from mail.get2chip.com ([64.169.83.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KU3V16268 for ; Fri, 6 Jul 2001 13:30:03 -0700 Subject: Re: IBM DeveloperWorks: Advanced Filesystems on Linux article To: Seth Mos Cc: Alan Eldridge , "'linux-xfs@oss.sgi.com'" Message-ID: From: ccroswhite@get2chip.com Date: Fri, 6 Jul 2001 13:25:10 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I was curious to see this considering the fact that IBM is pushing JFS. Chris Croswhite Get2Chip.com, Inc. 408.501.9525 Seth Mos , "'linux-xfs@oss.sgi.com'" ll.nl> cc: 07/06/2001 Subject: Re: IBM DeveloperWorks: Advanced Filesystems on Linux 01:15 PM article At 15:01 6-7-2001 -0500, Alan Eldridge wrote: >http://www-106.ibm.com/developerworks/linux/library/l-fs > I have already sent them a feedback message with urls to the SGI XFS project page and the project status but have not received a reply yet. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:38:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66KcoR16479 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:38:50 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KcnV16472 for ; Fri, 6 Jul 2001 13:38:49 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id NAA10576 for ; Fri, 6 Jul 2001 13:38:40 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2364507; Fri, 6 Jul 2001 15:37:31 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA10646; Fri, 6 Jul 2001 15:37:31 -0500 (CDT) Message-ID: <3B4621E3.9B5970BF@sgi.com> Date: Fri, 06 Jul 2001 15:38:59 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Bas CC: linux-xfs@oss.sgi.com Subject: Re: CVS References: <00d001c10658$e69ad500$0f01a8c0@ws1> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bas wrote: > > Hi, > > I'm using XFS for a couple of months now and have had no real problems yet > so, it rocks. > > I was wondering if it's possible to add another CVS tree, right now I've > only got 2 options: an old kernel or a pre kernel (right ?). The other tree > I would like to see is current kernel with enhancements. There has been some discussion on this... perhaps we can see what our users want. What I'm planning on doing is taking our 1.0.1 tree (which will be exported via CVS soon), and keep it up to date with "official" Linus kernels, i.e. 2.4.6, 2.4.7, 2.4.8 etc - until 1.0.2 comes out, which will then begin tracking 2.4.9, 2.4.10 (for example). And generate patches along the way (no RPMs for this, probably, too much work...) That way, people who don't necessarily want to track XFS development can still have stable XFS for the latest "Linus" kernel, and those who want to live on the edge can be swept along with the -preX kernels in the devel tree. -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 6 13:38:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66Kcl216445 for linux-xfs-outgoing; Fri, 6 Jul 2001 13:38:47 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66KckV16442 for ; Fri, 6 Jul 2001 13:38:46 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 6AE2F1AB0F for ; Fri, 6 Jul 2001 16:38:45 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 2E8108B2; Fri, 6 Jul 2001 16:38:45 -0400 (EDT) Date: Fri, 6 Jul 2001 16:38:45 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: CVS Message-ID: <20010706163844.E2814@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <00d001c10658$e69ad500$0f01a8c0@ws1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00d001c10658$e69ad500$0f01a8c0@ws1> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 06, 2001 at 10:19:03PM +0200, Bas wrote: > I was wondering if it's possible to add another CVS tree, > right now I've only got 2 options: an old kernel or a pre > kernel (right ?). The other tree I would like to see is > current kernel with enhancements. A CVS tag for the stable kernels would probably be what you're looking for. It's something that has been talked about, but I think the current word on that is something to the effect of, "Because of the way we've got things set up internally it'd be tricky, but we'll look into it if enough people ask for it." If it helps, I'm one more person myself who'd find a CVS tag for the stable kernels a handy thing... Andrew Klaassen From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:03:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66L3xQ16971 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:03:59 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66L3vV16968 for ; Fri, 6 Jul 2001 14:03:57 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA18182; Fri, 6 Jul 2001 23:03:51 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706230144.037add70@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 23:03:43 +0200 To: Eric Sandeen , Bas From: Seth Mos Subject: Re: CVS Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B4621E3.9B5970BF@sgi.com> References: <00d001c10658$e69ad500$0f01a8c0@ws1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 15:38 6-7-2001 -0500, Eric Sandeen wrote: >Bas wrote: > > > > Hi, > > > > I'm using XFS for a couple of months now and have had no real problems yet > > so, it rocks. > > > > I was wondering if it's possible to add another CVS tree, right now I've > > only got 2 options: an old kernel or a pre kernel (right ?). The other tree > > I would like to see is current kernel with enhancements. > >There has been some discussion on this... perhaps we can see what our >users want. > >What I'm planning on doing is taking our 1.0.1 tree (which will be >exported via CVS soon), and keep it up to date with "official" Linus >kernels, i.e. 2.4.6, 2.4.7, 2.4.8 etc - until 1.0.2 comes out, which >will then begin tracking 2.4.9, 2.4.10 (for example). And generate >patches along the way (no RPMs for this, probably, too much work...) me like This is a nice way to keep production systems up-to-date and keep the -devel tree for al the -pre versions on your test systems separated. >That way, people who don't necessarily want to track XFS development can >still have stable XFS for the latest "Linus" kernel, and those who want >to live on the edge can be swept along with the -preX kernels in the >devel tree. Yes Please! -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:13:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LD9n17250 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:13:09 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LD7V17245 for ; Fri, 6 Jul 2001 14:13:07 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15Icu8-0000lK-00; Sat, 07 Jul 2001 09:12:48 +1200 Date: Sat, 7 Jul 2001 09:12:48 +1200 (NZST) From: Juha Saarinen To: Steve Lord cc: Andrew Klaassen , "linux-xfs@oss.sgi.com" Subject: Re: More on write caching In-Reply-To: <200107061738.f66Hcpb09219@jen.americas.sgi.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 6 Jul 2001, Steve Lord wrote: > Using the rotational power of the spindle to > generate power to move the head to a special track and flush the cache > is not unheard of for instance. My systems integrator friend tells me that certain drives from IBM have large capacitors, which come in handy when the power goes out all of a sudden. For obvious reasons, if the drives are connected to a caching controller, make sure you have an UPS as well... -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:18:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LIae17406 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:18:36 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LIZV17403 for ; Fri, 6 Jul 2001 14:18:35 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15Iczc-0000lQ-00; Sat, 07 Jul 2001 09:18:28 +1200 Date: Sat, 7 Jul 2001 09:18:28 +1200 (NZST) From: Juha Saarinen To: Alan Eldridge cc: Linux XFS Mailing List Subject: Re: Sorry 'bout HTML crap In-Reply-To: <20010706160645.A6072@wwweasel.geeksrus.net> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 6 Jul 2001, Alan Eldridge wrote: > appeared to have 1 line of text. I know this because bernhard.erdmann's > mailer just bounced it back to me. At least Bernhard has stopped bouncing them to the various mailing lists he's subscribed to... -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:27:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LRt317613 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:27:55 -0700 Received: from woody.fsl.noaa.gov (IDENT:root@woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LRsV17609 for ; Fri, 6 Jul 2001 14:27:54 -0700 Received: (from tierney@localhost) by woody.fsl.noaa.gov (8.9.3/8.9.3) id PAA04529 for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 15:30:58 -0600 Date: Fri, 6 Jul 2001 15:30:58 -0600 From: Craig Tierney To: linux-xfs@oss.sgi.com Subject: Problem writing sparse files over NFS to xfs filesystem Message-ID: <20010706153058.D4348@hpti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am having a problem with exporting xfs over NFS. I have two servers that are exhibiting the same problem where a piece of code writing a sparse file gives the wrong filesize. x86, smp, linux-2.4.5, Trond's NFS patches, and linux-2.4.5-xfs-06112001.patch alpha, uniprocessor, linux-2.4.6, Trond's NFS patches, and linux-2.4.6-xfs-07052001.patch Both boxes are mounting luns from a fiber channel storage device (both use Qlogic 2200, v4.27beta driver). The filesystems on the x86 are lvm partitions (both xfs and ext2, striped). The filesystem on the alpha is not lvm. The size of the file written by the code below should be 40500 bytes. When this code is run on a xfs exported nfs filesystem, the filesize is 40960. This happens to both x86 and alpha NFS fileservers over NFSv3 (udp packets, rsize=wsize=8192). The code runs correctly when run on the xfs filesystem directly. The code run correctly to a ext2 exported nfs filesystem on the x86 box. /*********************/ #include #include main (int argc, char **argv) { int x[588]; long sA; FILE *f; int i; #define ByteCount 2352 #define SeekIncr (long) 3468 sA = 0; f = fopen ("test40500", "w"); sA = 0; for (i=0; i < 12; i++) { (void) fseek (f, sA, SEEK_SET); (void) fwrite (x, (size_t) ByteCount, (size_t) 1, f); sA += (SeekIncr); } (void) fclose(f); exit(0); } /**************************/ Thanks, Craig -- Craig Tierney (ctierney@hpti.com) phone: 303-497-3112 From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:31:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LVNG17768 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:31:23 -0700 Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LVLV17765 for ; Fri, 6 Jul 2001 14:31:21 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 15IdCK-000Ddr-0W for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 22:31:36 +0100 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id ADAB227EF for ; Fri, 6 Jul 2001 22:30:47 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id 473F4125E6; Fri, 6 Jul 2001 22:30:46 +0100 (BST) Date: Fri, 6 Jul 2001 22:30:45 +0100 (BST) From: Keith Matthews Subject: Re[2]: More on write caching To: "linux-xfs@oss.sgi.com" In-Reply-To: References: X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010706213046.473F4125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f66LVMV17766 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 7 Jul 2001 09:12:48 +1200 (NZST) Juha Saarinen > wrote: > On Fri, 6 Jul 2001, Steve Lord wrote: > > Using the rotational power of the spindle to > > generate power to move the head to a special track and flush the cache > > is not unheard of for instance. > My systems integrator friend tells me that certain drives from IBM have > large capacitors, which come in handy when the power goes out all of a > sudden. > For obvious reasons, if the drives are connected to a caching controller, > make sure you have an UPS as well... Or ensure it is a battery-backed cache on the controller. Problem is these are the expensive ones. If you do use an UPS, ensure it is a good one. I have seen large systems brought down just because one part of the UPS failed. I also know of a site that had a major fire caused by the UPS. -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:35:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LZnn17880 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:35:49 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LZlV17877 for ; Fri, 6 Jul 2001 14:35:47 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA05502; Fri, 6 Jul 2001 23:35:28 +0200 (CEST) Message-Id: <4.3.2.7.2.20010706233312.02fe9130@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Jul 2001 23:35:20 +0200 To: Juha Saarinen , Steve Lord From: Seth Mos Subject: Re: More on write caching Cc: Andrew Klaassen , "linux-xfs@oss.sgi.com" In-Reply-To: References: <200107061738.f66Hcpb09219@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 09:12 7-7-2001 +1200, Juha Saarinen wrote: >On Fri, 6 Jul 2001, Steve Lord wrote: > > > Using the rotational power of the spindle to > > generate power to move the head to a special track and flush the cache > > is not unheard of for instance. > >My systems integrator friend tells me that certain drives from IBM have >large capacitors, which come in handy when the power goes out all of a >sudden. > >For obvious reasons, if the drives are connected to a caching controller, >make sure you have an UPS as well... They have battery packs for caching raid controllers, well at least the decent ones. They can keep the data in there save for 72 hours untill you find time to spin up the disks adn write out the data when it is online again. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:37:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LboN18015 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:37:50 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LbnV18002 for ; Fri, 6 Jul 2001 14:37:49 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15IdIE-0000mC-00; Sat, 07 Jul 2001 09:37:42 +1200 From: "Juha Saarinen" To: "'Seth Mos'" , "'Steve Lord'" Cc: "'Andrew Klaassen'" , Subject: RE: More on write caching Date: Sat, 7 Jul 2001 09:37:51 +1200 Message-ID: <03d201c10663$e8669350$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <4.3.2.7.2.20010706233312.02fe9130@pop.xs4all.nl> Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk :: They have battery packs for caching raid controllers, well :: at least the :: decent ones. :: They can keep the data in there save for 72 hours untill you :: find time to :: spin up the disks adn write out the data when it is online again. Yep, I should've mentioned those as well... not enough caffeine in the bloodstream this morning. -- Juha From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:43:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LhOh18137 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:43:24 -0700 Received: from vertigo.incyte.com (master.incyte.com [198.31.37.253]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LhMV18134 for ; Fri, 6 Jul 2001 14:43:22 -0700 Received: from vertigo.incyte.com (wfrancis@localhost) by vertigo.incyte.com (8.11.0/8.11.0) with ESMTP id f66LhH207630 for ; Fri, 6 Jul 2001 14:43:17 -0700 Message-Id: <200107062143.f66LhH207630@vertigo.incyte.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-xfs@oss.sgi.com From: Will Francis Subject: minimum memory? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Jul 2001 14:43:17 -0700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have a 486/100 laptop which I'm going to turn into a sort of embedded device. I'd like to, if possible, run 7.1+XFS on it. It has only 8MB of memory though, so I'm curious if that would be an issue. If so, what would be the minimum recommended amount? It's going to be polling a device over the serial port at certain intervals, so I'm going to shut off as many other services and things like virtual terminals, etc as possible. Would I see much of a savings if I were to recompile the source and tweak, or are things already pretty well modularized? I know that XFS patch is pretty darn big... thanks, Will From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:45:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66Ljbm18258 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:45:37 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LjaV18254 for ; Fri, 6 Jul 2001 14:45:36 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f66LjYNe071223; Fri, 6 Jul 2001 16:45:34 -0500 (CDT) Message-ID: <3B463165.DECB0E14@thebarn.com> Date: Fri, 06 Jul 2001 16:45:09 -0500 From: cattelan@thebarn.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: XFS cvs updates References: <200107061852.f66Iq5r09647@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > We are experiencing technical difficulties (aka a head crash) and at the > moment updates are not happening. > Ok the hourly cvs pushed are back online. Both oss.sgi.com and lips.thebarn.com should be up-to-date -Russell at large From owner-linux-xfs@oss.sgi.com Fri Jul 6 14:48:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66LmFV18387 for linux-xfs-outgoing; Fri, 6 Jul 2001 14:48:15 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66LmDV18384 for ; Fri, 6 Jul 2001 14:48:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA1142209 for ; Fri, 6 Jul 2001 23:48:10 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2336450; Fri, 6 Jul 2001 16:46:54 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA83257; Fri, 6 Jul 2001 16:46:54 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66Lmih19480; Fri, 6 Jul 2001 16:48:44 -0500 Message-Id: <200107062148.f66Lmih19480@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Craig Tierney cc: linux-xfs@oss.sgi.com Subject: Re: Problem writing sparse files over NFS to xfs filesystem In-Reply-To: Message from Craig Tierney of "Fri, 06 Jul 2001 15:30:58 MDT." <20010706153058.D4348@hpti.com> Date: Fri, 06 Jul 2001 16:48:44 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Yes, there is a problem here, I have replicated it locally. Thanks for the info, I don't have the cause yet, but hopefully it will not take too long to fix. Steve > I am having a problem with exporting xfs over > NFS. I have two servers that are exhibiting the > same problem where a piece of code writing a sparse > file gives the wrong filesize. > > x86, smp, linux-2.4.5, Trond's NFS patches, > and linux-2.4.5-xfs-06112001.patch > alpha, uniprocessor, linux-2.4.6, Trond's NFS patches, > and linux-2.4.6-xfs-07052001.patch > > Both boxes are mounting luns from a fiber channel > storage device (both use Qlogic 2200, v4.27beta driver). > > The filesystems on the x86 are lvm partitions (both > xfs and ext2, striped). The filesystem on the alpha is not > lvm. > > The size of the file written by the code below should be 40500 bytes. > When this code is run on a xfs exported nfs filesystem, the filesize > is 40960. This happens to both x86 and alpha NFS fileservers > over NFSv3 (udp packets, rsize=wsize=8192). The code > runs correctly when run on the xfs filesystem directly. The code > run correctly to a ext2 exported nfs filesystem on the x86 box. > > > /*********************/ > #include > #include > > main (int argc, char **argv) > { > int x[588]; > long sA; > FILE *f; > int i; > #define ByteCount 2352 > #define SeekIncr (long) 3468 > sA = 0; > f = fopen ("test40500", "w"); > sA = 0; > > for (i=0; i < 12; i++) > { > (void) fseek (f, sA, SEEK_SET); > (void) fwrite (x, (size_t) ByteCount, (size_t) 1, f); > sA += (SeekIncr); > } > (void) fclose(f); > exit(0); > } > /**************************/ > > Thanks, > Craig > > -- > Craig Tierney (ctierney@hpti.com) > phone: 303-497-3112 From owner-linux-xfs@oss.sgi.com Fri Jul 6 15:08:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66M8A918709 for linux-xfs-outgoing; Fri, 6 Jul 2001 15:08:10 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66M88V18706 for ; Fri, 6 Jul 2001 15:08:08 -0700 Received: (qmail 13405 invoked by uid 8); 6 Jul 2001 22:08:07 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: CVS Date: Fri, 6 Jul 2001 22:08:07 +0000 (UTC) Organization: spoiled dot org Lines: 32 Distribution: local Message-ID: References: <00d001c10658$e69ad500$0f01a8c0@ws1> <4.3.2.7.2.20010706230144.037add70@pop.xs4all.nl> X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > At 15:38 6-7-2001 -0500, Eric Sandeen wrote: >>Bas wrote: >> > >> >>What I'm planning on doing is taking our 1.0.1 tree (which will be >>exported via CVS soon), and keep it up to date with "official" Linus >>kernels, i.e. 2.4.6, 2.4.7, 2.4.8 etc - until 1.0.2 comes out, which >>will then begin tracking 2.4.9, 2.4.10 (for example). And generate >>patches along the way (no RPMs for this, probably, too much work...) > > me like > This is a nice way to keep production systems up-to-date and keep the > -devel tree for al the -pre versions on your test systems separated. > >>That way, people who don't necessarily want to track XFS development can >>still have stable XFS for the latest "Linus" kernel, and those who want >>to live on the edge can be swept along with the -preX kernels in the >>devel tree. > > Yes Please! I'd like to second this! That is what I was always missing about XFS ;-) Keep on the great work, guys!!! Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Fri Jul 6 15:31:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66MVj019314 for linux-xfs-outgoing; Fri, 6 Jul 2001 15:31:45 -0700 Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [192.161.36.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66MViV19311 for ; Fri, 6 Jul 2001 15:31:44 -0700 Received: from blv-av-02.boeing.com ([192.54.3.92]) by blv-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id PAA06152 for ; Fri, 6 Jul 2001 15:30:36 -0700 (PDT) Received: from blv-hub-01.boeing.com (localhost [127.0.0.1]) by blv-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-01) with ESMTP id PAA12742 for ; Fri, 6 Jul 2001 15:31:42 -0700 (PDT) Received: from [136.203.14.68] by blv-hub-01.boeing.com with ESMTP for linux-xfs@oss.sgi.com; Fri, 6 Jul 2001 15:31:35 -0700 Message-Id: <3B463C47.3080603@pipcws.ca.boeing.com> Date: Fri, 06 Jul 2001 15:31:35 -0700 From: Ric Tibbetts User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: en-us MIME-Version: 1.0 To: "'linux-xfs@oss.sgi.com'" Subject: Re: IBM DeveloperWorks: Advanced Filesystems on Linux article References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk ccroswhite@get2chip.com wrote: >I was curious to see this considering the fact that IBM is pushing JFS. > I have to agree that this is the first in the series, and they'll talk about other FS's in subsequent articles. I think we can look forward to seeing both XFS, and JFS featured, although probably not to the depth they'll cover ReiserFS, only because of ReiserFS tends to be unique in it's approach. JMHO Ric From owner-linux-xfs@oss.sgi.com Fri Jul 6 15:53:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f66MrB519739 for linux-xfs-outgoing; Fri, 6 Jul 2001 15:53:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f66MrAV19736 for ; Fri, 6 Jul 2001 15:53:10 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA07454 for ; Fri, 6 Jul 2001 15:53:22 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2262594; Fri, 6 Jul 2001 17:51:52 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA44775; Fri, 6 Jul 2001 17:51:52 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f66Mrg422182; Fri, 6 Jul 2001 17:53:42 -0500 Message-Id: <200107062253.f66Mrg422182@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Craig Tierney , linux-xfs@oss.sgi.com Subject: Re: Problem writing sparse files over NFS to xfs filesystem In-Reply-To: Message from Steve Lord of "Fri, 06 Jul 2001 16:48:44 CDT." <200107062148.f66Lmih19480@jen.americas.sgi.com> Date: Fri, 06 Jul 2001 17:53:42 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Yes, there is a problem here, I have replicated it locally. Thanks for > the info, I don't have the cause yet, but hopefully it will not take > too long to fix. And the answer here is that nfs does not pay any attention to a filesystem which provides a revalidate function (which xfs does). NFS is reporting incorrect information from the linux inode on the server back to the client. If you look at the file locally on the server then it is OK, if you look at the file over nfs a few seconds later then it is also OK, it is only the state returned on the reply to the write which is incorrect (I looked at the protocol packets). I know how to fix this, but it is not going to happen today. Steve > > Steve > > > I am having a problem with exporting xfs over > > NFS. I have two servers that are exhibiting the > > same problem where a piece of code writing a sparse > > file gives the wrong filesize. > > > > x86, smp, linux-2.4.5, Trond's NFS patches, > > and linux-2.4.5-xfs-06112001.patch > > alpha, uniprocessor, linux-2.4.6, Trond's NFS patches, > > and linux-2.4.6-xfs-07052001.patch > > > > Both boxes are mounting luns from a fiber channel > > storage device (both use Qlogic 2200, v4.27beta driver). > > > > The filesystems on the x86 are lvm partitions (both > > xfs and ext2, striped). The filesystem on the alpha is not > > lvm. > > > > The size of the file written by the code below should be 40500 bytes. > > When this code is run on a xfs exported nfs filesystem, the filesize > > is 40960. This happens to both x86 and alpha NFS fileservers > > over NFSv3 (udp packets, rsize=wsize=8192). The code > > runs correctly when run on the xfs filesystem directly. The code > > run correctly to a ext2 exported nfs filesystem on the x86 box. > > > > > > /*********************/ > > #include > > #include > > > > main (int argc, char **argv) > > { > > int x[588]; > > long sA; > > FILE *f; > > int i; > > #define ByteCount 2352 > > #define SeekIncr (long) 3468 > > sA = 0; > > f = fopen ("test40500", "w"); > > sA = 0; > > > > for (i=0; i < 12; i++) > > { > > (void) fseek (f, sA, SEEK_SET); > > (void) fwrite (x, (size_t) ByteCount, (size_t) 1, f); > > sA += (SeekIncr); > > } > > (void) fclose(f); > > exit(0); > > } > > /**************************/ > > > > Thanks, > > Craig > > > > -- > > Craig Tierney (ctierney@hpti.com) > > phone: 303-497-3112 > From owner-linux-xfs@oss.sgi.com Fri Jul 6 20:50:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f673oiZ06943 for linux-xfs-outgoing; Fri, 6 Jul 2001 20:50:44 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f673ogV06939 for ; Fri, 6 Jul 2001 20:50:42 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip36.idcomm.com [209.60.72.163]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f673rEa32275 for ; Fri, 6 Jul 2001 21:53:14 -0600 Message-ID: <3B46878C.B6353F94@idcomm.com> Date: Fri, 06 Jul 2001 21:52:44 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: aid to iso download References: <3B44E6FE.DCB78DE5@idcomm.com> <20010705172106.I883@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan Straz wrote: > > On Thu, Jul 05, 2001 at 04:15:26PM -0600, D. Stimits wrote: > > Being that the ISO images are rather large, it might be nice to have a > > duplicate of each current ISO available that is the gzip version. > > Here's an old FTP trick, append a .gz to any filename on an FTP site and > the FTP server will gzip it for you. > > -- > Nate Straz nstraz@sgi.com > sgi, inc http://www.sgi.com/ > Linux Test Project http://ltp.sf.net/ I have heard there can be a problem with IE on win when downloading the .gz extension. Presumably, it might remove the extension, and a later rename to .gz would restore it? I'm going to begin my long modem download a bit later this evening, so I'm hoping to find out any snafu before I start. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Fri Jul 6 21:53:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f674roG10906 for linux-xfs-outgoing; Fri, 6 Jul 2001 21:53:50 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f674rdV10891 for ; Fri, 6 Jul 2001 21:53:39 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id VAA19514 for ; Fri, 6 Jul 2001 21:53:31 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id XAA84169 for ; Fri, 6 Jul 2001 23:52:22 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15Ik4q-00042h-00 for ; Fri, 06 Jul 2001 23:52:20 -0500 Date: Fri, 6 Jul 2001 23:52:20 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Deadlock while running on XFS Message-ID: <20010706235220.A15505@sgi.com> 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.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk While I was running regression tests last night on 2.4.3-SGI_XFS_1.0.1smp I hit a deadlock where 4-5 processes were all hung, but the system was still responsive. I think this may be related to the problems Christopher McCrory was having. Don't panic, I only caught this after over seven hours of constant regression testing. I was able to grab the system state using magic sysrq and Keith sent me a fresh copy of ksymoops that is supposed to handle it. I have included the output below, but I don't trust it. Keith, I'm using mangled kernel versions which I don't think depmod or ksymoops handles correctly. i.e. I specify depfile, generic_stringfile, path[toplevel], etc in /etc/modules.conf. Without further ado, here is the processed "Show State" data. I don't think it makes much sense, but I'll let the experts judge it. The processes "rm," "symlink02," "kupdated," "pmd," and "renamer" were all in the "D" state. ksymoops 2.4.2 on i686 2.4.3-SGI_XFS_1.0.1smp. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.3-SGI_XFS_1.0.1smp/ (default) -m /usr/src/linux/System.map (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. Error (expand_objects): cannot stat(/lib/qla1280.o) for qla1280 Error (expand_objects): cannot stat(/lib/ncr53c8xx.o) for ncr53c8xx Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod Error (pclose_local): find_objects pclose failed 0x100 Error (regular_file): read_system_map stat /usr/src/linux/System.map failed init S C476DF0C 0 1 0 19883 (NOTLB) Using defaults from ksymoops -t elf32-i386 -a i386 Call Trace: [] [] [] [] [] keventd S 00000000 0 2 1 (L-TLB) 3 Call Trace: [] [] kswapd S C4769FA0 0 3 1 (L-TLB) 4 2 Call Trace: [] [] [] [] [] [] kreclaimd S 00000286 0 4 1 (L-TLB) 5 3 Call Trace: [] [] [] [] [] bdflush S C477C000 0 5 1 (L-TLB) 6 4 Call Trace: [] [] [] [] kupdated D C477A000 0 6 1 (L-TLB) 7 5 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] pagebuf_daemon S 00000286 0 7 1 (L-TLB) 8 6 Call Trace: [] [] [] [] mdrecoveryd S F717C000 0 8 1 (L-TLB) 594 7 Call Trace: [] [] [] syslogd S 7FFFFFFF 0 594 1 (NOTLB) 599 8 Call Trace: [] [] [] [] [] klogd R F5E48000 4160 599 1 (NOTLB) 613 594 Call Trace: [] [] [] [] [] [] portmap S 7FFFFFFF 0 613 1 (NOTLB) 628 599 Call Trace: [] [] [] [] [] [] [] rpc.statd S 7FFFFFFF 0 628 1 (NOTLB) 717 613 Call Trace: [] [] [] [] [] [] ypbind S 7FFFFFFF 0 717 1 719 (NOTLB) 776 628 Call Trace: [] [] [] [] [] [] [] ypbind S F5F8BF10 4768 719 717 721 (NOTLB) Call Trace: [] [] [] [] [] [] [] [] ypbind S 00000000 4160 720 719 (NOTLB) 721 Call Trace: [] [] [] ypbind S F66B9F78 1392 721 719 (NOTLB) 720 Call Trace: [] [] [] [] [] [] [] automount S F64C2000 16 776 1 (NOTLB) 786 717 Call Trace: [] [] [] [] automount S F5CF2000 4160 786 1 (NOTLB) 796 776 Call Trace: [] [] [] [] automount S F5D56000 0 796 1 (NOTLB) 806 786 Call Trace: [] [] [] [] automount S F6712000 4488 806 1 (NOTLB) 816 796 Call Trace: [] [] [] [] automount S F5E2C000 4160 816 1 (NOTLB) 826 806 Call Trace: [] [] [] [] automount S F65B4000 0 826 1 (NOTLB) 836 816 Call Trace: [] [] [] [] automount S F66AC000 4 836 1 (NOTLB) 846 826 Call Trace: [] [] [] [] automount S F5D42000 4160 846 1 (NOTLB) 856 836 Call Trace: [] [] [] [] automount S C44F2000 0 856 1 (NOTLB) 866 846 Call Trace: [] [] [] [] automount S C44FE000 0 866 1 (NOTLB) 876 856 Call Trace: [] [] [] [] automount S C4504000 0 876 1 (NOTLB) 886 866 Call Trace: [] [] [] [] automount S C4608000 0 886 1 (NOTLB) 893 876 Call Trace: [] [] [] [] automount S F6454000 0 893 1 (NOTLB) 905 886 Call Trace: [] [] [] [] atd S F6689F78 0 905 1 (NOTLB) 1000 893 Call Trace: [] [] [] [] sshd S 7FFFFFFF 0 1000 1 (NOTLB) 1080 905 Call Trace: [] [] [] [] [] xinetd S 7FFFFFFF 0 1080 1 19899 (NOTLB) 1113 1000 Call Trace: [] [] [] [] [] [] sendmail S F5B1BF0C 2416 1113 1 (NOTLB) 1126 1080 Call Trace: [] [] [] [] [] [] crond S F5AFDF78 0 1126 1 19880 (NOTLB) 1165 1113 Call Trace: [] [] [] [] mingetty S 7FFFFFFF 0 1165 1 (NOTLB) 1166 1126 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1166 1 (NOTLB) 1167 1165 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1167 1 (NOTLB) 1168 1166 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1168 1 (NOTLB) 1169 1167 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1169 1 (NOTLB) 5626 1168 Call Trace: [] [] [] [] [] in.rlogind S 7FFFFFFF 0 1328 1080 1355 (NOTLB) 19750 Call Trace: [] [] [] [] [] [] login S 00000000 2416 1355 1328 1356 (NOTLB) Call Trace: [] [] [] tcsh S 00000000 0 1356 1355 5567 (NOTLB) Call Trace: [] [] [] su S 00000000 0 5567 1356 5568 (NOTLB) Call Trace: [] [] bash S 00000000 0 5568 5567 19749 (NOTLB) Call Trace: [] [] [] [] pmd S 7FFFFFFF 3608 5626 1 23861 (NOTLB) 5978 1169 Call Trace: [] [] [] [] [] [] getpgid2_01 S F4F8C000 0 5978 1 (NOTLB) 23496 5626 Call Trace: [] [] getpgid2_01 S F300C000 2416 23496 1 (NOTLB) 19776 5978 Call Trace: [] [] pmd S F43D8000 0 23861 5626 19698 (NOTLB) Call Trace: [] [] [] [] [] renamer01 S 00000000 0 19588 23861 19622 (NOTLB) 19659 Call Trace: [] [] [] renamer D F645C0E0 0 19622 19588 (NOTLB) Call Trace: [] [] [] [] [] [] [] rwtest S 00000000 0 19659 23861 19699 (NOTLB) 19698 19588 Call Trace: wait_on_irq, CPU 0: irq: 1 [ 0 1 0 0 ] bh: 1 [ 1 0 0 0 ] Stack dumps: CPU 1:6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] CPU 2:6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] CPU 3:6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db Call Trace: CPU 0:c02e3ecc c028d37d 00000000 00000000 00000000 c010832d c028d392 f7159ec0 00000004 00000090 00000001 c01fb677 c03691c0 00000000 c01fb640 00000286 c011e81c 00000000 00000001 00001020 c03691c0 c0388a80 00000000 c011eda9 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] symlink02 D E4744000 0 19698 23861 (NOTLB) 19659 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] rm D E42FA000 0 19699 19659 (NOTLB) Call Trace: [] [] [] [] [] [] [] [] [] [] top S F4A23F0C 0 19749 5568 (NOTLB) Call Trace: [] [] [] [] [] [] [] in.rlogind S 7FFFFFFF 0 19750 1080 19777 (NOTLB) 19899 1328 Call Trace: [] [] [] [] [] rpciod S E5922000 0 19775 1 (L-TLB) 19832 19776 Call Trace: [] [] [] [] [] [] [] [] [] [] lockd S 7FFFFFFF 0 19776 1 (L-TLB) 19775 23496 Call Trace: [] [] [] [] [] login S 00000000 4540 19777 19750 19778 (NOTLB) Call Trace: [] [] [] [] tcsh S 00000000 0 19778 19777 19802 (NOTLB) Call Trace: [] [] [] su S 00000000 1392 19802 19778 19803 (NOTLB) Call Trace: [] [] bash S 7FFFFFFF 0 19803 19802 19831 (NOTLB) Call Trace: [] [] [] [] [] strace T 00000014 4768 19831 19803 19700 (NOTLB) Call Trace: [] [] [] pmd D E2E6C000 0 19700 19831 (NOTLB) Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] mingetty S 7FFFFFFF 0 19832 1 (NOTLB) 19883 19775 Call Trace: [] [] [] [] [] [] crond S E3C84000 0 19880 1126 19881 (NOTLB) Call Trace: [] [] [] [] [] run-parts S 00000000 0 19881 19880 19884 (NOTLB) Call Trace: [] [] sa1 S 00000000 0 19883 1 19886 (NOTLB) 19832 Call Trace: [] [] awk S E4F86000 0 19884 19881 (NOTLB) Call Trace: [] [] [] [] [] sadc S E5C92000 0 19886 19883 (NOTLB) Call Trace: [] [] [] in.rlogind S 7FFFFFFF 0 19899 1080 19902 (NOTLB) 19750 Call Trace: [] [] [] [] [] login S 00000000 0 19902 19899 19903 (NOTLB) Call Trace: [] [] [] tcsh S 7FFFFFFF 0 19903 19902 (NOTLB) Call Trace: [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Proc; init >>EIP; c476df0c <___strtok+43aecc0/38440e14> <===== Trace; c0114691 Trace; c01145b4 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; keventd >>EIP; 00000000 Before first symbol Trace; c0122fc8 Trace; c0105643 Proc; kswapd >>EIP; c4769fa0 <___strtok+43aad54/38440e14> <===== Trace; c0114691 Trace; c01145b4 Trace; c0114f82 Trace; c029476e Trace; c012fbc9 Trace; c0105643 Proc; kreclaimd >>EIP; 00000286 Before first symbol <===== Trace; c0114f0d Trace; c0294778 Trace; c012fcbb Trace; c010563a Trace; c0105643 Proc; bdflush >>EIP; c477c000 <___strtok+43bcdb4/38440e14> <===== Trace; c029550e Trace; c012f813 Trace; c013b17e Trace; c0105643 Proc; kupdated >>EIP; c477a000 <___strtok+43badb4/38440e14> <===== Trace; c01d877e Trace; c01d885d Trace; c01d3e13 Trace; c01ad831 Trace; c01ad873 Trace; c01d3e13 Trace; c01d3e13 Trace; c01d27dd Trace; c016a910 Trace; c01d2760 Trace; c01c6037 Trace; c0169674 Trace; c01d2760 Trace; c01d293c Trace; c01d294f Trace; c01d2760 Trace; c01d293c Trace; c0127550 Trace; c01d293c Trace; c014b937 <__mark_inode_dirty+36f/840> Trace; c013af87 Trace; c013b28d Trace; c0105643 Proc; pagebuf_daemon >>EIP; 00000286 Before first symbol <===== Trace; c0114f0d Trace; c01685cc Trace; c01684d0 Trace; c0105643 Proc; mdrecoveryd >>EIP; f717c000 <___strtok+36dbcdb4/38440e14> <===== Trace; c02afdf1 Trace; c0230682 Trace; c0105643 Proc; syslogd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; klogd >>EIP; f5e48000 <___strtok+35a88db4/38440e14> <===== Trace; c0231ffd Trace; c0116ffc Trace; c01575e5 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; portmap >>EIP; 7fffffff Before first symbol <===== Trace; c024ebff Trace; c0232437 Trace; c0114627 Trace; c01473d3 <__pollwait+ab3/11c8> Trace; c014735f <__pollwait+a3f/11c8> Trace; c0147663 <__pollwait+d43/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; rpc.statd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0136607 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; ypbind >>EIP; 7fffffff Before first symbol <===== Trace; c024ebff Trace; c0232437 Trace; c0114627 Trace; c01473d3 <__pollwait+ab3/11c8> Trace; c014735f <__pollwait+a3f/11c8> Trace; c0147663 <__pollwait+d43/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; ypbind >>EIP; f5f8bf10 <___strtok+35bcccc4/38440e14> <===== Trace; c0114691 Trace; c01145b4 Trace; c014735f <__pollwait+a3f/11c8> Trace; c0147663 <__pollwait+d43/11c8> Trace; c01086c9 Trace; c01086e9 Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; ypbind >>EIP; 00000000 Before first symbol Trace; c0105fdb <__read_lock_failed+27b/2510> Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; ypbind >>EIP; f66b9f78 <___strtok+362fad2c/38440e14> <===== Trace; c0130870 Trace; c0146916 Trace; c0114691 Trace; c01145b4 Trace; c011f1ab Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; automount >>EIP; f64c2000 <___strtok+36102db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f5cf2000 <___strtok+35932db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f5d56000 <___strtok+35996db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f6712000 <___strtok+36352db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f5e2c000 <___strtok+35a6cdb4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f65b4000 <___strtok+361f4db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f66ac000 <___strtok+362ecdb4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f5d42000 <___strtok+35982db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; c44f2000 <___strtok+4132db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; c44fe000 <___strtok+413edb4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; c4504000 <___strtok+4144db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; c4608000 <___strtok+4248db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; automount >>EIP; f6454000 <___strtok+36094db4/38440e14> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; atd >>EIP; f6689f78 <___strtok+362cad2c/38440e14> <===== Trace; c0114691 Trace; c01145b4 Trace; c011f1ab Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; sshd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; xinetd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0136607 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; sendmail >>EIP; f5b1bf0c <___strtok+3575ccc0/38440e14> <===== Trace; c01469ae <__pollwait+8e/11c8> Trace; c0114691 Trace; c01145b4 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; crond >>EIP; f5afdf78 <___strtok+3573ed2c/38440e14> <===== Trace; c0114691 Trace; c01145b4 Trace; c011f1ab Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; in.rlogind >>EIP; 7fffffff Before first symbol <===== Trace; c01ef51c Trace; c0114627 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; login >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; tcsh >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c0105fdb <__read_lock_failed+27b/2510> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; su >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; bash >>EIP; 00000000 Before first symbol Trace; c01ea876 Trace; c01eac4d Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; pmd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; getpgid2_01 >>EIP; f4f8c000 <___strtok+34bccdb4/38440e14> <===== Trace; c010ca92 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; getpgid2_01 >>EIP; f300c000 <___strtok+32c4cdb4/38440e14> <===== Trace; c010ca92 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; pmd >>EIP; f43d8000 <___strtok+34018db4/38440e14> <===== Trace; c01145a7 Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; renamer01 >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c0105fdb <__read_lock_failed+27b/2510> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; renamer >>EIP; f645c0e0 <___strtok+3609ce94/38440e14> <===== Trace; c01d2555 Trace; c0141935 Trace; c0105b6b Trace; c0105d18 <__down_failed+8/c> Trace; c028799c Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; rwtest >>EIP; 00000000 Before first symbol Trace; c0166599 Trace; c0166599 Trace; c0166599 Trace; c0166599 Trace; c0166806 Trace; c0166806 Trace; c01675d7 Trace; c019386b Trace; c01145a7 Trace; c01b5ff4 Trace; c01b609d Trace; f880758a <[scsi_mod]scsi_queue_next_request+52/124> Trace; f88077c0 <[scsi_mod]__scsi_end_request+164/170> Trace; f8807a9a <[scsi_mod]scsi_io_completion+1da/3bc> Trace; f8817d86 <[sd_mod]rw_intr+1f6/204> Trace; f880671d <[scsi_mod]scsi_old_done+3d/600> Trace; f8806cc6 <[scsi_mod]scsi_old_done+5e6/600> Trace; c011eb87 Trace; c011eee0 Trace; c011ef63 Trace; c010c160 Trace; c01084d6 <__global_restore_flags+92/bc> Trace; c01086c9 Trace; c01086e9 Trace; c0106ee4 <__read_lock_failed+1184/2510> Trace; c0114b12 Trace; c0114691 Trace; c01145b4 Trace; c0114f82 Trace; c029476e Trace; c012fbc9 Trace; c0105643 Trace; c01001c8 Before first symbol Trace; c01effa0 Trace; c01f04e2 Trace; c0166599 Trace; c0166599 Trace; f9c04e6a Trace; c0166599 Trace; c0166599 Trace; f894b5b0 <[usbcore]proc_releaseinterface+30/40> Trace; f8945a36 <[usbcore]usb_find_interface_driver+3a/190> Trace; c02405e4 Trace; c0238d06 Trace; c0234312 Trace; c0262e2e Trace; c0263099 Trace; c02602cb Trace; f894b5b0 <[usbcore]proc_releaseinterface+30/40> Trace; f8945a36 <[usbcore]usb_find_interface_driver+3a/190> Trace; c02405e4 Trace; c0238d06 Trace; c024cca3 Trace; c023ef54 Trace; c024b722 Trace; c024cc00 Trace; c024b5cc Trace; c024bb0d Trace; c023ef54 Trace; c024b5cc Trace; c025f81d Trace; c025a59f Trace; c025a662 Trace; c025b18b Trace; c0258648 Trace; c01fff66 Trace; c0200000 Trace; c011731b Trace; c011737f Trace; c011745b Trace; c0117696 Trace; c011761e Trace; c01070bf <__read_lock_failed+135f/2510> Trace; c028cde0 Trace; c0107170 <__read_lock_failed+1410/2510> Trace; c0115783 Trace; c0115852 Trace; c0201b6d Trace; c0201d1c <__handle_sysrq_nolock+60/1440> Trace; c02a3b80 Trace; c02a3af6 Trace; c0201cb3 Trace; c02002fc Trace; c011eb87 Trace; c0201286 Trace; c0201314 Trace; c01084d6 <__global_restore_flags+92/bc> Trace; c01086c9 Trace; c0105280 Trace; c0105280 Trace; c0106ee4 <__read_lock_failed+1184/2510> Trace; c0105280 Trace; c0105280 Trace; c0100018 Before first symbol Trace; c01052ad Trace; c0105312 Trace; c011737f Trace; c028d37d Trace; c010832d <__global_cli+8d/12c> Trace; c028d392 Trace; c01fb677 Trace; c01fb640 Trace; c011e81c Trace; c011eda9 Trace; c011b552 Trace; c011b435 Trace; c011b2da Trace; c010870a Trace; c0105280 Trace; c0105280 Trace; c0106ee4 <__read_lock_failed+1184/2510> Trace; c0105280 Trace; c0105280 Trace; c0100018 Before first symbol Trace; c01052ad Trace; c0105312 Trace; c0105000 Trace; c01001cf Before first symbol Trace; c0114b12 Trace; c0105fdb <__read_lock_failed+27b/2510> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; symlink02 >>EIP; e4744000 <___strtok+24384db4/38440e14> <===== Trace; c01305b2 <__alloc_pages+6a/294> Trace; c01c2792 Trace; c01d877e Trace; c01d881c Trace; c01c74f2 Trace; c01ad856 Trace; c01ad873 Trace; c01c74f2 Trace; c01c74f2 Trace; c01d2555 Trace; c0141935 Trace; c0142459 Trace; c01428d8 <__user_walk+3c/58> Trace; c01360ba Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; rm >>EIP; e42fa000 <___strtok+23f3adb4/38440e14> <===== Trace; c01c312c Trace; c014b6da <__mark_inode_dirty+112/840> Trace; c014c7bc Trace; c01d7c22 Trace; c01ca027 Trace; c01ad99b Trace; c01d1e67 Trace; c0143c2f Trace; c0143d32 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; top >>EIP; f4a23f0c <___strtok+34664cc0/38440e14> <===== Trace; c01469ae <__pollwait+8e/11c8> Trace; c0114691 Trace; c01145b4 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; in.rlogind >>EIP; 7fffffff Before first symbol <===== Trace; c01ef51c Trace; c0114627 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; rpciod >>EIP; e5922000 <___strtok+25562db4/38440e14> <===== Trace; f89c4912 <[raid1]__module_using_checksums+f2e0/18a2e> Trace; f89bd2f0 <[raid1]__module_using_checksums+7cbe/18a2e> Trace; f89bde2b <[raid1]__module_using_checksums+87f9/18a2e> Trace; f89bdc4c <[raid1]__module_using_checksums+861a/18a2e> Trace; f89c6d84 <[raid1]__module_using_checksums+11752/18a2e> Trace; f89c6d7c <[raid1]__module_using_checksums+1174a/18a2e> Trace; f89c6d7c <[raid1]__module_using_checksums+1174a/18a2e> Trace; c0105643 Trace; f89c6d84 <[raid1]__module_using_checksums+11752/18a2e> Trace; f89c6d84 <[raid1]__module_using_checksums+11752/18a2e> Proc; lockd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0136607 Trace; f89c0cbe <[raid1]__module_using_checksums+b68c/18a2e> Trace; f898bc44 <[ipchains]__module_using_checksums+2a10e/3352a> Trace; c0105643 Proc; login >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Trace; c010002b Before first symbol Proc; tcsh >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c0105fdb <__read_lock_failed+27b/2510> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; su >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; bash >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; strace >>EIP; 00000014 Before first symbol <===== Trace; c0106c37 <__read_lock_failed+ed7/2510> Trace; c011a5c1 Trace; c0106e74 <__read_lock_failed+1114/2510> Proc; pmd >>EIP; e2e6c000 <___strtok+22aacdb4/38440e14> <===== Trace; c029abdc Trace; c029abdc Trace; c01d877e Trace; c01d881c Trace; c01c74f2 Trace; c01ad856 Trace; c01ad873 Trace; c01c74f2 Trace; c01c74f2 Trace; c01d2555 Trace; c0141935 Trace; c0142459 Trace; c013fbf1 Trace; c013fbff Trace; c01406c6 Trace; c01305b2 <__alloc_pages+6a/294> Trace; c0124cf8 Trace; c0124d0b Trace; c01254db Trace; c0113c9f <__verify_write+3cf/8f4> Trace; c0113b00 <__verify_write+230/8f4> Trace; c01207c4 Trace; c01417cb Trace; c0105a43 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01f5dae Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; crond >>EIP; e3c84000 <___strtok+238c4db4/38440e14> <===== Trace; c012634a Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; run-parts >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; sa1 >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; awk >>EIP; e4f86000 <___strtok+24bc6db4/38440e14> <===== Trace; c014a2f1 Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; sadc >>EIP; e5c92000 <___strtok+258d2db4/38440e14> <===== Trace; c0137f62 Trace; c010ca92 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; in.rlogind >>EIP; 7fffffff Before first symbol <===== Trace; c01ef51c Trace; c0114627 Trace; c0146b28 <__pollwait+208/11c8> Trace; c0147102 <__pollwait+7e2/11c8> Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; login >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c011a596 Trace; c0106e23 <__read_lock_failed+10c3/2510> Proc; tcsh >>EIP; 7fffffff Before first symbol <===== Trace; c01254db Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 <__read_lock_failed+10c3/2510> 2 warnings and 6 errors issued. Results may not be reliable. -- 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 Jul 6 22:26:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f675QnA13525 for linux-xfs-outgoing; Fri, 6 Jul 2001 22:26:49 -0700 Received: from horus.its.uow.edu.au (horus.its.uow.edu.au [130.130.68.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f675QlV13519 for ; Fri, 6 Jul 2001 22:26:47 -0700 Received: from uow.edu.au (wumpus.its.uow.edu.au [130.130.68.12]) by horus.its.uow.edu.au (8.9.3/8.9.3) with ESMTP id PAA05751; Sat, 7 Jul 2001 15:26:22 +1000 (EST) Message-ID: <3B469DDF.905AEC0B@uow.edu.au> Date: Sat, 07 Jul 2001 15:27:59 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching References: Message from Andrew Klaassen of "Fri, 06 Jul 2001 13:06:36 EDT." <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > > So I would not in general recommend write caching on a device, unless > you know enough about it to be satisfied that its cache makes it out > to disk on power down. Using the rotational power of the spindle to > generate power to move the head to a special track and flush the cache > is not unheard of for instance. It's my understanding (and ardent hope) that modern IDE disks do this. It's pretty simple - all they need to do when the power fails is to seek to the vendor area and squirt the write cache out in one big write - a few tens of milliseconds max. I'll be taking this up with some manufacturers, see if I can get a definitive answer. For more sophisticated storage systems such as RAID controllers, I guess we'd have to propagate a SCSI write barrier command down to the controller itself. I'm not sure that the Linux request and SCSI layers are up to doing that. Have you looked into it? From owner-linux-xfs@oss.sgi.com Fri Jul 6 23:35:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f676Zo219518 for linux-xfs-outgoing; Fri, 6 Jul 2001 23:35:50 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f676ZlV19508 for ; Fri, 6 Jul 2001 23:35:47 -0700 Received: (qmail 553 invoked from network); 7 Jul 2001 06:35:40 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 7 Jul 2001 06:35:40 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Nathan Straz cc: linux-xfs@oss.sgi.com Subject: Re: Deadlock while running on XFS In-reply-to: Your message of "Fri, 06 Jul 2001 23:52:20 EST." <20010706235220.A15505@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 07 Jul 2001 16:35:39 +1000 Message-ID: <15498.994487739@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 6 Jul 2001 23:52:20 -0500, Nathan Straz wrote: >I was able to grab the system state using magic sysrq and Keith sent me >a fresh copy of ksymoops that is supposed to handle it. I have included >the output below, but I don't trust it. Keith, I'm using mangled kernel >versions which I don't think depmod or ksymoops handles correctly. i.e. >I specify depfile, generic_stringfile, path[toplevel], etc in >/etc/modules.conf. > >ksymoops 2.4.2 on i686 2.4.3-SGI_XFS_1.0.1smp. Options used > -V (default) > -k /proc/ksyms (default) > -l /proc/modules (default) > -o /lib/modules/2.4.3-SGI_XFS_1.0.1smp/ (default) > -m /usr/src/linux/System.map (default) > >Error (expand_objects): cannot stat(/lib/qla1280.o) for qla1280 >Error (expand_objects): cannot stat(/lib/ncr53c8xx.o) for ncr53c8xx >Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod >Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod >Error (pclose_local): find_objects pclose failed 0x100 /proc/ksyms says that the modules were loaded from /lib but ksymoops cannot find them there. I guess that you are using initrd so /lib is pointing at the ramdisk /lib, not the real /lib. As a workaround, grep -v __insmod /proc/ksyms > /var/tmp/ksyms and run ksymoops with -k /var/tmp/ksyms. It will default to looking in /lib/modules/2.4.3-SGI_XFS_1.0.1smp/ for module objects instead of using the misleading names in /proc/ksyms. >Error (regular_file): read_system_map stat /usr/src/linux/System.map failed That is more of a problem. Without a valid System.map, ksymoops can only report using the symbols in ksyms. /proc/ksyms is not complete so the decoded oops has misleading names like pagebuf_unlock+68ecf/6cdbc. Run ksymoops with -m pointing to your current System.map. From owner-linux-xfs@oss.sgi.com Sat Jul 7 01:45:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f678jB332533 for linux-xfs-outgoing; Sat, 7 Jul 2001 01:45:11 -0700 Received: from ente.berdmann.de (p3EE0A880.dip.t-dialin.net [62.224.168.128]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f678j9V32524 for ; Sat, 7 Jul 2001 01:45:10 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Ini2-0007Yl-00 for linux-xfs@oss.sgi.com; Sat, 07 Jul 2001 10:45:02 +0200 Message-ID: <3B46CC0E.2826192A@berdmann.de> Date: Sat, 07 Jul 2001 10:45:02 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: XFS cvs updates References: <200107061852.f66Iq5r09647@jen.americas.sgi.com> <3B463165.DECB0E14@thebarn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk cattelan@thebarn.com wrote: > > Steve Lord wrote: > > > We are experiencing technical difficulties (aka a head crash) and at the > > moment updates are not happening. > > > > Ok the hourly cvs pushed are back online. > Both oss.sgi.com and lips.thebarn.com should be up-to-date > > -Russell at large $ cvs -z3 update -dP cvs server: Updating . cvs server: failed to create lock directory for `/cvs/linux-2.4-xfs' (/cvs/linux-2.4-xfs/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/cvs/linux-2.4-xfs' cvs [server aborted]: read lock failed - giving up From owner-linux-xfs@oss.sgi.com Sat Jul 7 01:45:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f678jrq32661 for linux-xfs-outgoing; Sat, 7 Jul 2001 01:45:53 -0700 Received: from ente.berdmann.de (p3EE0A880.dip.t-dialin.net [62.224.168.128]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f678jjV32621 for ; Sat, 7 Jul 2001 01:45:47 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15IniX-0007ZX-00 for linux-xfs@oss.sgi.com; Sat, 07 Jul 2001 10:45:33 +0200 Message-ID: <3B46CC2D.1C1DEBB9@berdmann.de> Date: Sat, 07 Jul 2001 10:45:33 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: Re: Sorry 'bout HTML crap References: <20010706160645.A6072@wwweasel.geeksrus.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Here's the link, again, just for you, Bernhard :) > > http://www-106.ibm.com/developerworks/linux/library/l-fs Thanks! ;-) From owner-linux-xfs@oss.sgi.com Sat Jul 7 02:54:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f679sGt10851 for linux-xfs-outgoing; Sat, 7 Jul 2001 02:54:16 -0700 Received: from rebel.net.au (IDENT:root@news.tellurian.com.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f679sEV10847 for ; Sat, 7 Jul 2001 02:54:14 -0700 Received: from rebel.net.au (dialup-6.rebel.net.au [203.20.69.76]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id TAA01555; Sat, 7 Jul 2001 19:24:00 +0930 Message-ID: <3B46DD0A.861BE23B@rebel.net.au> Date: Sat, 07 Jul 2001 19:27:30 +0930 From: David Lloyd X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: cwidmer@iiic.ethz.ch CC: "'linux-xfs@oss.sgi.com'" Subject: Re: [Re: 2.4.6 patch available] References: <20010705150247.29890.qmail@nwcst289.netaddress.usa.net> <0107051748040H.30268@asterix> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk LMAO > whats about using 07Jul2001, Jul072001, ... or any permutation and > no one will be confused any more. What about 7J00u01J2 then? DSL -- "The greatest thing you'll ever learn is just to love and to be loved in return." - David Bowie (Nature Boy from Moulin Rouge) From owner-linux-xfs@oss.sgi.com Sat Jul 7 04:16:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67BG2A24106 for linux-xfs-outgoing; Sat, 7 Jul 2001 04:16:02 -0700 Received: from virtualhost.dk (ns.virtualhost.dk [195.184.98.160]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67BF5V23944 for ; Sat, 7 Jul 2001 04:15:06 -0700 Received: from burns.home.kernel.dk ([192.168.0.2] ident=root) by virtualhost.dk with esmtp (Exim 3.22 #4) id 15Iq1k-0001cK-00; Sat, 07 Jul 2001 13:13:32 +0200 Received: from axboe by burns.home.kernel.dk with local (Exim 3.13 #1 (Debian)) id 15Iq1g-0004Qp-00; Sat, 07 Jul 2001 13:13:28 +0200 Date: Sat, 7 Jul 2001 13:13:28 +0200 From: Jens Axboe To: Andrew Morton Cc: Steve Lord , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching Message-ID: <20010707131328.F16505@suse.de> References: <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> <3B469DDF.905AEC0B@uow.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B469DDF.905AEC0B@uow.edu.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 07 2001, Andrew Morton wrote: > For more sophisticated storage systems such as RAID controllers, > I guess we'd have to propagate a SCSI write barrier command down to > the controller itself. I'm not sure that the Linux request > and SCSI layers are up to doing that. Have you looked into it? I have, I wrote a barrier write patch some time ago. SCSI support is the easy part, having the luxury of just setting a tag option. -- Jens Axboe From owner-linux-xfs@oss.sgi.com Sat Jul 7 04:23:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67BNsV25454 for linux-xfs-outgoing; Sat, 7 Jul 2001 04:23:54 -0700 Received: from horus.its.uow.edu.au (horus.its.uow.edu.au [130.130.68.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67BMuV25288 for ; Sat, 7 Jul 2001 04:22:56 -0700 Received: from uow.edu.au (wumpus.its.uow.edu.au [130.130.68.12]) by horus.its.uow.edu.au (8.9.3/8.9.3) with ESMTP id VAA20317; Sat, 7 Jul 2001 21:20:38 +1000 (EST) Message-ID: <3B46F0E5.77EAF1F9@uow.edu.au> Date: Sat, 07 Jul 2001 21:22:13 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jens Axboe CC: Steve Lord , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching References: <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> <3B469DDF.905AEC0B@uow.edu.au>, <3B469DDF.905AEC0B@uow.edu.au> <20010707131328.F16505@suse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jens Axboe wrote: > > On Sat, Jul 07 2001, Andrew Morton wrote: > > For more sophisticated storage systems such as RAID controllers, > > I guess we'd have to propagate a SCSI write barrier command down to > > the controller itself. I'm not sure that the Linux request > > and SCSI layers are up to doing that. Have you looked into it? > > I have, I wrote a barrier write patch some time ago. SCSI support is the > easy part, having the luxury of just setting a tag option. Good. Please keep that patch warm. Question is: does IDE need it at all? If we can assume that the data is safe once the drive has acked it, then that's all a journalling fs cares about, yes? From owner-linux-xfs@oss.sgi.com Sat Jul 7 04:23:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67BNwT25469 for linux-xfs-outgoing; Sat, 7 Jul 2001 04:23:58 -0700 Received: from virtualhost.dk (ns.virtualhost.dk [195.184.98.160]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67BN1V25307 for ; Sat, 7 Jul 2001 04:23:01 -0700 Received: from burns.home.kernel.dk ([192.168.0.2] ident=root) by virtualhost.dk with esmtp (Exim 3.22 #4) id 15IqAb-0001eR-00; Sat, 07 Jul 2001 13:22:41 +0200 Received: from axboe by burns.home.kernel.dk with local (Exim 3.13 #1 (Debian)) id 15IqAY-0004Sy-00; Sat, 07 Jul 2001 13:22:38 +0200 Date: Sat, 7 Jul 2001 13:22:38 +0200 From: Jens Axboe To: Andrew Morton Cc: Steve Lord , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching Message-ID: <20010707132238.G16505@suse.de> References: <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> <3B469DDF.905AEC0B@uow.edu.au>, <3B469DDF.905AEC0B@uow.edu.au> <20010707131328.F16505@suse.de> <3B46F0E5.77EAF1F9@uow.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B46F0E5.77EAF1F9@uow.edu.au> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 07 2001, Andrew Morton wrote: > Jens Axboe wrote: > > > > On Sat, Jul 07 2001, Andrew Morton wrote: > > > For more sophisticated storage systems such as RAID controllers, > > > I guess we'd have to propagate a SCSI write barrier command down to > > > the controller itself. I'm not sure that the Linux request > > > and SCSI layers are up to doing that. Have you looked into it? > > > > I have, I wrote a barrier write patch some time ago. SCSI support is the > > easy part, having the luxury of just setting a tag option. > > Good. Please keep that patch warm. I've tried to, and I'll put it in the bio-XX patches soon enough. > Question is: does IDE need it at all? If we can assume > that the data is safe once the drive has acked it, then that's > all a journalling fs cares about, yes? It would enable safe use of write caching, so yes. For a barrier write, do a sync flush following a write/write_dma/write_dma_queued command (yes dma_queued has no ordered/sync option, yay ide). -- Jens Axboe From owner-linux-xfs@oss.sgi.com Sat Jul 7 04:30:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67BUmj26786 for linux-xfs-outgoing; Sat, 7 Jul 2001 04:30:48 -0700 Received: from virtualhost.dk (ns.virtualhost.dk [195.184.98.160]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67BTpV26612 for ; Sat, 7 Jul 2001 04:29:51 -0700 Received: from burns.home.kernel.dk ([192.168.0.2] ident=root) by virtualhost.dk with esmtp (Exim 3.22 #4) id 15IqGQ-0001fF-00; Sat, 07 Jul 2001 13:28:43 +0200 Received: from axboe by burns.home.kernel.dk with local (Exim 3.13 #1 (Debian)) id 15IqGN-0004UJ-00; Sat, 07 Jul 2001 13:28:39 +0200 Date: Sat, 7 Jul 2001 13:28:39 +0200 From: Jens Axboe To: Andrew Morton Cc: Steve Lord , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching Message-ID: <20010707132839.H16505@suse.de> References: <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> <3B469DDF.905AEC0B@uow.edu.au>, <3B469DDF.905AEC0B@uow.edu.au> <20010707131328.F16505@suse.de> <3B46F0E5.77EAF1F9@uow.edu.au> <20010707132238.G16505@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010707132238.G16505@suse.de> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 07 2001, Jens Axboe wrote: > > Question is: does IDE need it at all? If we can assume > > that the data is safe once the drive has acked it, then that's > > all a journalling fs cares about, yes? Plus, BTW, this is what breaks too I'm afraid: 'If we can assume that the data is safe once the drive has acked it' is too easy to "optimize" by manufacturers. One can only hope and pray that they at least honor a sync cache flush, but hey... -- Jens Axboe From owner-linux-xfs@oss.sgi.com Sat Jul 7 04:31:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67BVxJ27032 for linux-xfs-outgoing; Sat, 7 Jul 2001 04:31:59 -0700 Received: from horus.its.uow.edu.au (horus.its.uow.edu.au [130.130.68.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67BV2V26831 for ; Sat, 7 Jul 2001 04:31:02 -0700 Received: from uow.edu.au (wumpus.its.uow.edu.au [130.130.68.12]) by horus.its.uow.edu.au (8.9.3/8.9.3) with ESMTP id VAA21930; Sat, 7 Jul 2001 21:30:53 +1000 (EST) Message-ID: <3B46F34D.2744AF68@uow.edu.au> Date: Sat, 07 Jul 2001 21:32:29 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Jens Axboe CC: Steve Lord , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching References: <20010706130636.C2814@dkp.com> <200107061738.f66Hcpb09219@jen.americas.sgi.com> <3B469DDF.905AEC0B@uow.edu.au>, <3B469DDF.905AEC0B@uow.edu.au> <20010707131328.F16505@suse.de> <3B46F0E5.77EAF1F9@uow.edu.au>, <3B46F0E5.77EAF1F9@uow.edu.au> <20010707132238.G16505@suse.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jens Axboe wrote: > > > Question is: does IDE need it at all? If we can assume > > that the data is safe once the drive has acked it, then that's > > all a journalling fs cares about, yes? > > It would enable safe use of write caching, so yes. For a barrier write, > do a sync flush following a write/write_dma/write_dma_queued command > (yes dma_queued has no ordered/sync option, yay ide). There was some discussion a while back, (triggered by someone's benchmark where IDE was thrashing SCSI) where it turned out that some IDE disks were simply ignoring the flush command. Which is a quite sane thing to do if the write cache integrity is guaranteed in this manner. What's the story with other storage interfaces apart from SCSI? Seems that most of them implement SCSI in some way anyway - are there other technologies that need thinking about? From owner-linux-xfs@oss.sgi.com Sat Jul 7 10:43:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67HhlO30645 for linux-xfs-outgoing; Sat, 7 Jul 2001 10:43:47 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67HhjV30642 for ; Sat, 7 Jul 2001 10:43:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA08700 for ; Sat, 7 Jul 2001 10:43:55 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2360722 for ; Sat, 7 Jul 2001 10:21:26 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA68510; Sat, 7 Jul 2001 09:09:25 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f67EB9323526; Sat, 7 Jul 2001 09:11:09 -0500 Message-Id: <200107071411.f67EB9323526@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Morton cc: Jens Axboe , Steve Lord , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching In-Reply-To: Message from Andrew Morton of "Sat, 07 Jul 2001 21:32:29 +1000." <3B46F34D.2744AF68@uow.edu.au> Date: Sat, 07 Jul 2001 09:11:09 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Jens Axboe wrote: > > > > > Question is: does IDE need it at all? If we can assume > > > that the data is safe once the drive has acked it, then that's > > > all a journalling fs cares about, yes? > > > > It would enable safe use of write caching, so yes. For a barrier write, > > do a sync flush following a write/write_dma/write_dma_queued command > > (yes dma_queued has no ordered/sync option, yay ide). > > There was some discussion a while back, (triggered by someone's > benchmark where IDE was thrashing SCSI) where it turned out that > some IDE disks were simply ignoring the flush command. I think the issue was that write caching was on on ide disks by default where on scsi it is usually off by default. The discussion was about O_SYNC, and they got the expected performance by disabling the caching. I think the only real answer is to write some tests which can be run on a raw disk. Work out the cache size of a device and push about that much data out to a raw disk, then drop the power. The tricky part is dropping the power quickly enough, is it possible to hook into apm or something and drop the power automatically? Then check that the data made it to disk after power up. You would need to run lots of cases to trust a device with write caching on. This would at least give us a testbed for drives and is somewhat similar to part of the process SGI uses to qualify scsi drives for hardware. Steve > > Which is a quite sane thing to do if the write cache integrity > is guaranteed in this manner. > > What's the story with other storage interfaces apart from SCSI? > Seems that most of them implement SCSI in some way anyway - are > there other technologies that need thinking about? From owner-linux-xfs@oss.sgi.com Sat Jul 7 10:46:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67HkBb30760 for linux-xfs-outgoing; Sat, 7 Jul 2001 10:46:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67HkAV30757 for ; Sat, 7 Jul 2001 10:46:10 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA01873 for ; Sat, 7 Jul 2001 10:46:14 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2367228 for ; Sat, 7 Jul 2001 10:18:56 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA00299; Sat, 7 Jul 2001 08:58:54 -0500 (CDT) From: lord@sgi.com Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f67E0c223479; Sat, 7 Jul 2001 09:00:38 -0500 Message-Id: <200107071400.f67E0c223479@jen.americas.sgi.com> Date: Sat, 7 Jul 2001 09:00:38 -0500 Subject: TAKE - fix writes to sparse files over nfs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I was wrong about who was at fault here, it was the pagebuf code in the case were we were zeroing holes in files, that path should not touch the inode size. Date: Sat Jul 7 06:57:13 PDT 2001 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:98440a linux/fs/pagebuf/page_buf_io.c - 1.88 - when writing a sparse file, do not change the inode size when zeroing buffers at the end of the file. This caused the linux inode size to get out of sync with the xfs inode size and confuse nfs. From owner-linux-xfs@oss.sgi.com Sat Jul 7 10:52:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67Hqtr30891 for linux-xfs-outgoing; Sat, 7 Jul 2001 10:52:55 -0700 Received: from ente.berdmann.de (p3EE0A880.dip.t-dialin.net [62.224.168.128]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67HqsV30888 for ; Sat, 7 Jul 2001 10:52:54 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15IwG8-0001pK-00 for linux-xfs@oss.sgi.com; Sat, 07 Jul 2001 19:52:48 +0200 Message-ID: <3B474C70.5D0C6549@berdmann.de> Date: Sat, 07 Jul 2001 19:52:48 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: something wrong with CVS? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk $ cvs -z3 update -dP cvs server: Updating . cvs server: failed to create lock directory for `/cvs/linux-2.4-xfs' (/cvs/linux-2.4-xfs/#cvs.lock): Permission denied cvs server: failed to obtain dir lock in repository `/cvs/linux-2.4-xfs' cvs [server aborted]: read lock failed - giving up From owner-linux-xfs@oss.sgi.com Sat Jul 7 12:34:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67JYvJ07349 for linux-xfs-outgoing; Sat, 7 Jul 2001 12:34:57 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67JYuV07346 for ; Sat, 7 Jul 2001 12:34:56 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 6ED8D1AB0F for ; Sat, 7 Jul 2001 15:34:55 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 0295E670; Sat, 7 Jul 2001 15:34:54 -0400 (EDT) Date: Sat, 7 Jul 2001 15:34:54 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Oops - 1.0.1-PR3 Message-ID: <20010707153454.G5712@dkp.com> 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.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk kbd> bt EBP EIP Function(args) 0xf7dbdf14 0xc01f274e rs_flush_chars+0x3a (0xf7dc0000, 0x0, 0x1) kernel .text 0xc0100000 0xc01f2714 0xc01f2758 0xf7dbdf60 0xc01e376f write_chan+0x17b (0xf7dc0000, 0xf7dc40c0, 0x80492ce, 0x1) kernel .text 0xc0100000 0xc01e35f4 0xc01e37e0 0xf7dbdf98 0xc01df6cb tty_write+0x19b (0xf7dc40c0, 0x80492ce, 0x1, 0xf7dc40e0) kernel .text 0xc0100000 0xc01df530 0xc01df70c 0xf7dbdfbc 0xc0132255 sys_write+0x95 (0x1, 0x80492ce, 0x1, 0x4, 0xbfff7f05) kernel .text 0xc0100000 0xc01321c0 0xc0132290 0xc0106c97 system_call+0x33 kernel .text 0xc0100000 0xc0106c64 0xc0106c9c Any idea what this might have been cause by? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Sat Jul 7 12:45:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f67JjO108636 for linux-xfs-outgoing; Sat, 7 Jul 2001 12:45:24 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f67JjNV08633 for ; Sat, 7 Jul 2001 12:45:23 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 3F9BF1AB0F for ; Sat, 7 Jul 2001 15:45:22 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id EFC5F670; Sat, 7 Jul 2001 15:45:21 -0400 (EDT) Date: Sat, 7 Jul 2001 15:45:21 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Oops - 1.0.1-PR3 Message-ID: <20010707154521.A6182@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010707153454.G5712@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010707153454.G5712@dkp.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry - should have been more specific on the kernel version. It's 2.4.3-SGI_XFS_1.0.1_PR3, from the i686 rpm. Andrew Klaassen On Sat, Jul 07, 2001 at 03:34:54PM -0400, Andrew Klaassen wrote: > kbd> bt > EBP EIP Function(args) > 0xf7dbdf14 0xc01f274e rs_flush_chars+0x3a (0xf7dc0000, 0x0, 0x1) > kernel .text 0xc0100000 0xc01f2714 0xc01f2758 > 0xf7dbdf60 0xc01e376f write_chan+0x17b (0xf7dc0000, 0xf7dc40c0, 0x80492ce, 0x1) > kernel .text 0xc0100000 0xc01e35f4 0xc01e37e0 > 0xf7dbdf98 0xc01df6cb tty_write+0x19b (0xf7dc40c0, 0x80492ce, 0x1, 0xf7dc40e0) > kernel .text 0xc0100000 0xc01df530 0xc01df70c > 0xf7dbdfbc 0xc0132255 sys_write+0x95 (0x1, 0x80492ce, 0x1, 0x4, 0xbfff7f05) > kernel .text 0xc0100000 0xc01321c0 0xc0132290 > 0xc0106c97 system_call+0x33 > kernel .text 0xc0100000 0xc0106c64 0xc0106c9c > > Any idea what this might have been cause by? > > Andrew Klaassen From owner-linux-xfs@oss.sgi.com Sat Jul 7 22:23:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f685Nbw22953 for linux-xfs-outgoing; Sat, 7 Jul 2001 22:23:37 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f685NaV22950 for ; Sat, 7 Jul 2001 22:23:36 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f685NTE30804 for linux-xfs@oss.sgi.com; Sun, 8 Jul 2001 01:23:29 -0400 Date: Sun, 8 Jul 2001 01:23:29 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: module versioning problem Message-ID: <20010708012329.A30799@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm using an RPM kernel built from CVS tree... no problems here, except when I tried to build the vmware kernel modules. My /usr/include/linux/version.h is: #define UTS_RELEASE "2.4.6-SGI_XFS_cvs.20010704.0" #define LINUX_VERSION_CODE 132102 #define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c)) The LINUX_VERSION_CODE is right (0x020406 == 132102). And I'm getting the following errors: Unable to make a vmmon module that can be loaded in the running kernel: /tmp/vmware-config4/vmmon.o: unresolved symbol __pollwait_R0b4cb329 /tmp/vmware-config4/vmmon.o: unresolved symbol mem_map_R20e49beb /tmp/vmware-config4/vmmon.o: unresolved symbol misc_deregister_Rc7297387 /tmp/vmware-config4/vmmon.o: unresolved symbol __free_pages_Rd9e8f857 /tmp/vmware-config4/vmmon.o: unresolved symbol irq_stat_R7035bb53 /tmp/vmware-config4/vmmon.o: unresolved symbol misc_register_R921a3ca3 There is probably a light difference of kernel configuration between the set of C header files you specified and your running kernel. You may want to rebuild a kernel based on that directory, or specify another directory. Any ideas what could be going wrong in the build? I'm using Eric's spec file from PR1 with only the sources/patches modified to be appropriate to the build at hand. Eric, you've got the spec file I'm using... -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Sat Jul 7 23:04:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6864Ck27957 for linux-xfs-outgoing; Sat, 7 Jul 2001 23:04:12 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6864BV27950 for ; Sat, 7 Jul 2001 23:04:11 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f68645i26674 for linux-xfs@oss.sgi.com; Sun, 8 Jul 2001 02:04:05 -0400 Date: Sun, 8 Jul 2001 02:04:05 -0400 From: Alan Eldridge To: Linux XFS Mailing List Subject: mod versions answer found sort of Message-ID: <20010708020405.A26464@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is weird.... the /boot/kernel.h file, which is created when building the kernel-headers package, of course is empty, because it's a i386 build, no smp, no enterprise, etc etc. But the actual kernel installed is the i686 kernel. This kernel needs to have the line: #define __MODULE_KERNEL_i686 1 included, since it's a 686 kernel. But since the kernel-headers package is only built on the i386 build, they're out of sync. Why does this matter? Well, the version string used in mangling module symbols is different for i386 and i5/686 kernels. This is, of course, the result of RH weirdness being imposed on a non-RH kernel. Seems to me that the right thing to do is to make the /boot/kernel.h file in the kernel rpm, not the headers rpm. Eric, whaddya you think? I'll have to test this out with your PR3 kernel and see if I get bit... PR1 worked ok, I seem to recall. Auuuuggghhhh! -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Sun Jul 8 03:41:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68AflL30657 for linux-xfs-outgoing; Sun, 8 Jul 2001 03:41:47 -0700 Received: from ente.berdmann.de (p3EE0A95C.dip.t-dialin.net [62.224.169.92]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68AfhV30653 for ; Sun, 8 Jul 2001 03:41:44 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15JC08-0007CS-00; Sun, 08 Jul 2001 12:41:20 +0200 Message-ID: <3B4838D0.5BAEDF4F@berdmann.de> Date: Sun, 08 Jul 2001 12:41:20 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre7-xfs-jfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: xfsrestore deletes files in cumulative restores Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, today I did some restore tests (do you really trust your backups?) The XFS filesystem /var/spool/imap (Cyrus IMAP spooldir) was backed up in level 0 on July, 2nd 1 3rd 1 4th 2 5th 2 6th 3 7th 3 8th. I restored from tape to /mnt/junk the xfsdump images level 0 of July, 2nd 1 4th 2 6th 3 8th. Then I used tar to compare the two directory trees: # (cd /var/spool/imap && tar cf - .) | tar df - [...] tar: ./user/be/Sent/xy/290.: Warning: Cannot stat: No such file or directory [...] Lots of files were missing (mostly due to reorganisation, aka moving mails to different folders). I traced the history of this particular file user/be/Sent/xy/290. It's not in the restored subtree: # ls -l user/be/Sent/xy/29* -rw------- 1 cyrus root 1243 Nov 30 2000 user/be/Sent/xy/29. -rw------- 1 cyrus root 775 Jul 5 15:52 user/be/Sent/xy/291. But it's still in the backed up spooldir: # ls -l /var/spool/imap/user/be/Sent/xy/29* -rw------- 1 cyrus root 1243 Nov 30 2000 /var/spool/imap/user/be/Sent/xy/29. -rw------- 2 cyrus root 885 Jul 4 18:47 /var/spool/imap/user/be/Sent/xy/290. -rw------- 2 cyrus root 775 Jul 5 15:52 /var/spool/imap/user/be/Sent/xy/291. What did xfsrestore do to my holy IMAP spool??? Amanda's index tells me this file was backed up on July 5th and 6th in level 2: $ zgrep Sent/xy/290 _var_spool_imap/200107* _var_spool_imap/20010705_2.gz:/user/be/Sent/xy/290. _var_spool_imap/20010706_2.gz:/user/be/Sent/xy/290. Then I restored that particular subtree user/be/Sent/xy with xfsrestore debug mode: # (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -s user/be/Sent/xy -v trace - .) > xfsrestore.debug.0 # (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.1 # (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.2 # (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.3 After applying level 2, the file was in the restored subtree: # ls -l user/be/Sent/xy/29* -rw------- 1 cyrus root 1243 Nov 30 2000 user/be/Sent/xy/29. -rw------- 1 cyrus root 885 Jul 4 18:47 user/be/Sent/xy/290. After applying level 3, it was missing: # ls -l user/be/Sent/xy/29* -rw------- 1 cyrus root 1243 Nov 30 2000 user/be/Sent/xy/29. -rw------- 1 cyrus root 775 Jul 5 15:52 user/be/Sent/xy/291. xfsrestore.debug.3 told me xfsrestore had deleted user/be/Sent/xy/290.: [...] /usr/sbin/xfsrestore: rename nondir user/be/Sent/xy/290. to orphanage/9074670.1 /usr/sbin/xfsrestore: unlink nondir orphanage/9074670.1 [...] /usr/sbin/xfsrestore: restoring user/be/Sent/xy/291. (9074676 0) /usr/sbin/xfsrestore: restoring regular file ino 9074676 user/be/Sent/xy/291. /usr/sbin/xfsrestore: truncating user/be/Sent/xy/291. from 0 to 775 /usr/sbin/xfsrestore: restore complete: 76 seconds elapsed What's going on here? I'm using xfsdump-1.0.9-0. From owner-linux-xfs@oss.sgi.com Sun Jul 8 05:21:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68CLuL18662 for linux-xfs-outgoing; Sun, 8 Jul 2001 05:21:56 -0700 Received: from ente.berdmann.de (p3EE0A95C.dip.t-dialin.net [62.224.169.92]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68CLqV18648 for ; Sun, 8 Jul 2001 05:21:53 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15JDZI-0007d7-00; Sun, 08 Jul 2001 14:21:44 +0200 Message-ID: <3B485058.9389834C@berdmann.de> Date: Sun, 08 Jul 2001 14:21:44 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre3-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: xfsdump/xfsrestore fails Zwicky's torture test Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I just did some torture testing with xfsdump/xfsrestore (Kernel linux-2.4.7-pre3-xfs, checkout 04:30 GMT). Using a perl script referenced from http://reality.sgi.com/zwicky_neu/testdump.doc.html (Torture-testing Backup and Archive Programs: Things You Ought to Know But Probably Would Rather Not, Elizabeth D. Zwicky, 1991) Cited from that article: 1.0 The Tests The test suite currently employs two sorts of test. First, there are static tests; files and directories with stressful names, contents, or permissions, which do not change while the program runs. Second, there are active tests; files that change while the program is running. Static tests: A file with a large hole in it. A file that contains a hole and a block's worth of nulls. Files with funny characters in their file names. 1025 hard links to the same file. 2911 hard links to different files. Files with long names. Symbolic links to long names. Symbolic links to names with funny characters in them. Unreadable and unwriteable files. Unreadable and unwriteable directories with normal files in them. A named pipe. A device. Active tests: A file that becomes a directory. A directory that becomes a file. A file that is deleted. A file that is created. A file that shrinks. Two files that grow at different rates. Some errors occur between multiple backups or during multiple restores, and the test suite does not test for them at this point. I will mention these conditions further later. The tests were run using a Perl program which created all the static files, and then forked to modify files in one process and run the program being tested on the other. All programs were tested through a pipe, rather than having them actually create and read from tape archives. There were no compatibility tests; the archives were always being read by the program that wrote them (or, in the case of dump, by restore.) Except where specified, they were run with no options beyond those required to archive to standard output and read from standard input. A modified version of GNU diff was used to compare the original directory with the restored one. [...] I gave a filesystem with the "directory from Hell" to xfsdump, but xfsrestore fails in content.c to read the directory index: # ~be/torture-new/torture.perl First guess at max component length is 255 max path length appears to be 4095 Type a command line which will run a backup program on the dump test directory: /sbin/xfsdump -J - /mnt/test1 | (cd /mnt/test2/linux-xfsrestore && /sbin/xfsrestore - .) Child 1 /sbin/xfsrestore: version 3.0 - Running single-threaded /sbin/xfsdump: version 3.0 - Running single-threaded /sbin/xfsdump: level 0 dump of apollo:/mnt/test1 /sbin/xfsdump: dump date: Sun Jul 8 13:59:01 2001 /sbin/xfsdump: session id: fd2f240d-6708-4785-8576-cae2ab0a8272 /sbin/xfsdump: session label: "" /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: skipping (no pruning necessary) /sbin/xfsdump: ino map phase 4: skipping (size estimated in phase 2) /sbin/xfsdump: ino map phase 5: skipping (only one dump stream) /sbin/xfsrestore: searching media for dump /sbin/xfsdump: ino map construction complete /sbin/xfsdump: estimated dump size: 6424640 bytes /sbin/xfsdump: creating dump session media file 0 (media 0, file 0) /sbin/xfsdump: dumping ino map /sbin/xfsdump: dumping directories /sbin/xfsrestore: examining media file 0 /sbin/xfsrestore: dump description: /sbin/xfsrestore: hostname: apollo /sbin/xfsrestore: mount point: /mnt/test1 /sbin/xfsrestore: volume: /dev/vg02/test1 /sbin/xfsrestore: session time: Sun Jul 8 13:59:01 2001 /sbin/xfsrestore: level: 0 /sbin/xfsrestore: session label: "" /sbin/xfsrestore: media label: "" /sbin/xfsrestore: file system id: 61c3ba48-82e8-4afc-a7b3-a61579d9ecd0 /sbin/xfsrestore: session id: fd2f240d-6708-4785-8576-cae2ab0a8272 /sbin/xfsrestore: media id: 12ac5d0e-0850-4ad1-91d9-58d803dd315f /sbin/xfsrestore: searching media for directory dump /sbin/xfsdump: dumping non-directory files /sbin/xfsrestore: reading directories xfsrestore: content.c:2942: applydirdump: Assertion `namelen < 255' failed. /sbin/xfsdump: ending media file /sbin/xfsdump: media file size 266240 bytes /sbin/xfsdump: dump size (non-dir files) : 544 bytes /sbin/xfsdump: NOTE: dump interrupted: 1 seconds elapsed Backup took 1.00 seconds of clock time and 0.00 seconds of cpu time # df /mnt/test? Filesystem 1k-blocks Used Available Use% Mounted on /dev/vg02/test1 93504 83516 9988 89% /mnt/test1 /dev/vg02/test2 93504 604 92900 1% /mnt/test2 I had to modify torture.perl (10 years old) in order to run with a modern linux system. You can download it from http://berdmann.dyndns.org/torture.tar.gz From owner-linux-xfs@oss.sgi.com Sun Jul 8 13:19:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68KJ3R15593 for linux-xfs-outgoing; Sun, 8 Jul 2001 13:19:03 -0700 Received: from mail.sidac.co.jp (dns.sidac.co.jp [211.6.163.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KIuV15580 for ; Sun, 8 Jul 2001 13:18:56 -0700 Received: from host (06-073.081.popsite.net [64.24.246.73]) by mail.sidac.co.jp (8.9.3/3.7Wpl2) with ESMTP id EAA06944; Mon, 9 Jul 2001 04:37:02 +0900 Message-Id: <200107081937.EAA06944@mail.sidac.co.jp> From: "West Quinn" Subject: Lower Your Monthly Payments #34C2 To: opt87y@mail.sidac.co.jp X-Mailer: Microsoft Outlook Express 4.72.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE VÐßD.1712.3 Mime-Version: 1.0 Date: Sun, 08 Jul 2001 13:48:53 -0500 Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a MIME Message ------=_NextPart_000_007F_01BDF6C7.FABAC1B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0" ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ***** This is an HTML Message ! ***** ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

We will help you= get the mortgage loan you want! 

Whether a new home loan is what you seek or
to refinance your current h= ome loan at a lower interest rate and payment, we can help!

Mortgage rates haven't been this low in the last 12 months, take action no= w!
 Refinance your home with us and include all of those pesky credit card bil= ls or
use the extra cash for that pool you've always wanted=2E=2E=2E&nbs= p;

 Where others says NO, we say YES!!!
 Even if you have been turned down elsewhere, we can help! 

 Easy terms! Our mortgage referral service combines the
highest quality loans wi= th most economical rates and the easiest qualification!

 Take just 2 minutes to complete the following form=2E
 There is no obligation, all information is= kept strictly confidential, and you must be at least 18 years of age=2E Service available within the United States only=2E This service is fast an= d free=2E

 

Free information= request form:

Loan Application Form

REMOVA= L INSTRUCTIONS: This message is being sent to you in compliance with the cu= rrent Federal legislation=2E You must have either posted an AD to my FFA si= te, web-site, or requested information, or responded to one of our email le= tters=2E If you do not want to receive further emails or any other informat= ion from us, or you have received this mail in error, or for immediate remo= val you may simply use reply on your email program with "Remove from y= our mailing list#99221" in the subject=2E

------=_NextPart_001_0080_01BDF6C7.FABAC1B0-- ------=_NextPart_000_007F_01BDF6C7.FABAC1B0-- From owner-linux-xfs@oss.sgi.com Sun Jul 8 13:35:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68KZUu16572 for linux-xfs-outgoing; Sun, 8 Jul 2001 13:35:30 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KZOV16568 for ; Sun, 8 Jul 2001 13:35:24 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip46.idcomm.com [209.60.72.173]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f68Kc5a15282 for ; Sun, 8 Jul 2001 14:38:05 -0600 Message-ID: <3B48C484.FCA7BDBC@idcomm.com> Date: Sun, 08 Jul 2001 14:37:24 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: spam Content-Type: multipart/mixed; boundary="------------CE315B0C21B904D494DB3468" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------CE315B0C21B904D494DB3468 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.idcomm.com id f68Kc5a15282 I'm forwarding something that apparently is from email harvesting. I doubt there is anything to be done to prevent spam harvesters, but considering how terrible it has become on gnu.org lists, I'll pose the question: is there anything, on a practical basis, that can help prevent spam email from being generated through this list? I suspect the answer is "no", but I thought I'd ask. I'm pasting the full header of the offending email below. I'd probably forward this to an abuse account at the sending location if not for the fact that it is a .jp, and Japan routinely supports spamming (there is no help in reporting spammers to Japanese ISP's it seems). D. Stimits, stimits@idcomm.com Return-Path:=20 Received:=20 from totalrecall.idcomm.com (totalrecall.idcomm.com [207.40.196.5]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f68KNCa14330 for ; Sun, 8 Jul 2001 14:23:12 -0600 Received:=20 from oss.sgi.com (oss.sgi.com [216.32.174.27]) by totalrecall.idcomm.com (8.9.3/8.9.3) with ESMTP id OAA29288 for ; Sun, 8 Jul 2001 14:20:24 -0600 Received:=20 from localhost (mail@localhost) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KK0Q15673; Sun, 8 Jul 2001 13:20:00 -0700 X-Authentication-Warning:=20 oss.sgi.com: mail owned process doing -bs Received:=20 by oss.sgi.com (bulk_mailer v1.13); Sun, 8 Jul 2001 13:19:03 -0700 Received:=20 (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68KJ3R15593 for linux-xfs-outgoing; Sun, 8 Jul 2001 13:19:03 -0700 Received:=20 from mail.sidac.co.jp (dns.sidac.co.jp [211.6.163.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KIuV15580 for ; Sun, 8 Jul 2001 13:18:56 -0700 Received:=20 from host (06-073.081.popsite.net [64.24.246.73]) by mail.sidac.co.jp (8.9.3/3.7Wpl2) with ESMTP id EAA06944; Mon, 9 Jul 2001 04:37:02 +0900 Message-ID:=20 <200107081937.EAA06944@mail.sidac.co.jp> From:=20 "West Quinn" Subject:=20 Lower Your Monthly Payments #34C2 To:=20 opt87y@mail.sidac.co.jp X-Mailer:=20 Microsoft Outlook Express 4.72.1712.3 X-MimeOLE:=20 Produced By Microsoft MimeOLE V=D0=DFD.1712.3 Mime-Version:=20 1.0 Date:=20 Sun, 08 Jul 2001 13:48:53 -0500 Content-Type:=20 multipart/mixed; =20 boundary=3D"----=3D_NextPart_000_007F_01BDF6C7.FABAC1B0" Sender:=20 owner-linux-xfs@oss.sgi.com Precedence:=20 bulk X-Mozilla-Status:=20 8001 X-Mozilla-Status2:=20 00000000 X-UIDL:=20 _8fD.wEMS7.mailhost --------------CE315B0C21B904D494DB3468 Content-Type: message/rfc822 Content-Disposition: inline Return-Path: Received: from totalrecall.idcomm.com (totalrecall.idcomm.com [207.40.196.5]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f68KNCa14330 for ; Sun, 8 Jul 2001 14:23:12 -0600 Received: from oss.sgi.com (oss.sgi.com [216.32.174.27]) by totalrecall.idcomm.com (8.9.3/8.9.3) with ESMTP id OAA29288 for ; Sun, 8 Jul 2001 14:20:24 -0600 Received: from localhost (mail@localhost) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KK0Q15673; Sun, 8 Jul 2001 13:20:00 -0700 X-Authentication-Warning: oss.sgi.com: mail owned process doing -bs Received: by oss.sgi.com (bulk_mailer v1.13); Sun, 8 Jul 2001 13:19:03 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68KJ3R15593 for linux-xfs-outgoing; Sun, 8 Jul 2001 13:19:03 -0700 Received: from mail.sidac.co.jp (dns.sidac.co.jp [211.6.163.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KIuV15580 for ; Sun, 8 Jul 2001 13:18:56 -0700 Received: from host (06-073.081.popsite.net [64.24.246.73]) by mail.sidac.co.jp (8.9.3/3.7Wpl2) with ESMTP id EAA06944; Mon, 9 Jul 2001 04:37:02 +0900 Message-Id: <200107081937.EAA06944@mail.sidac.co.jp> From: "West Quinn" Subject: Lower Your Monthly Payments #34C2 To: opt87y@mail.sidac.co.jp X-Mailer: Microsoft Outlook Express 4.72.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE VÐßD.1712.3 Mime-Version: 1.0 Date: Sun, 08 Jul 2001 13:48:53 -0500 Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk X-Mozilla-Status2: 00000000 This is a MIME Message ------=_NextPart_000_007F_01BDF6C7.FABAC1B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0" ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ***** This is an HTML Message ! ***** ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

We will help you= get the mortgage loan you want! 

Whether a new home loan is what you seek or
to refinance your current h= ome loan at a lower interest rate and payment, we can help!

Mortgage rates haven't been this low in the last 12 months, take action no= w!
 Refinance your home with us and include all of those pesky credit card bil= ls or
use the extra cash for that pool you've always wanted=2E=2E=2E&nbs= p;

 Where others says NO, we say YES!!!
 Even if you have been turned down elsewhere, we can help! 

 Easy terms! Our mortgage referral service combines the
highest quality loans wi= th most economical rates and the easiest qualification!

 Take just 2 minutes to complete the following form=2E
 There is no obligation, all information is= kept strictly confidential, and you must be at least 18 years of age=2E Service available within the United States only=2E This service is fast an= d free=2E

 

Free information= request form:

Loan Application Form


Pleas= e complete all the information below=2E
Our loan specialist will be con= tacting you at your convenience=2E
Thank You!

Plea= se use your mouse to navigate between fields=2E Thank You=2E


=
Your Full Name *
Address *
City *
State(US= A Only) * UNITED STATES ONLY!
Zip/Postal Code *
= Home Phone *
Work Phone *
Email Address <= input type=3D"text" size=3D"20" maxlength=3D"30" name=3D"Email"> *
= Best Time To Call *
Do You Own Your Home?
Property Value =3D 50000)) { alert('Not Valid! Please enter the approximate value of = current property or property you wish to purchase \n (greater than or equal= to 50000) using only number characters - 0123456789'); this=2Efocus(); thi= s=2Eselect(); return false; }"> * Please= use numbers only
Property Type *
Purchase= Price * Please use numb= ers only

Year Acquired

 *<= /td>
1st Mortgage-Balance Owed * Please use numbers only (ex:= 45000) enter 0 for none
1st Mortgage-In= terest Rate %
Is 1st Adjustable or = Fixed? *
Employer *
Monthly Gross House= hold Income * Please use numbers only
2nd Mortgage Balance owed > * Please use numbers only(ex:45000) enter 0 for none=
Amount You Wish To Borrow *
= = Credit Rating *
Monthly Debt= * Please use numbers only
Loan Interested In *
 

Fast & Easy -You Are Done !

REMOVA= L INSTRUCTIONS: This message is being sent to you in compliance with the cu= rrent Federal legislation=2E You must have either posted an AD to my FFA si= te, web-site, or requested information, or responded to one of our email le= tters=2E If you do not want to receive further emails or any other informat= ion from us, or you have received this mail in error, or for immediate remo= val you may simply use reply on your email program with "Remove from y= our mailing list#99221" in the subject=2E

------=_NextPart_001_0080_01BDF6C7.FABAC1B0-- ------=_NextPart_000_007F_01BDF6C7.FABAC1B0-- --------------CE315B0C21B904D494DB3468-- From owner-linux-xfs@oss.sgi.com Sun Jul 8 14:15:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68LF8718580 for linux-xfs-outgoing; Sun, 8 Jul 2001 14:15:08 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68LF6V18577 for ; Sun, 8 Jul 2001 14:15:07 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15JLtO-0003eQ-00; Mon, 09 Jul 2001 09:15:02 +1200 Date: Mon, 9 Jul 2001 09:15:02 +1200 (NZST) From: Juha Saarinen To: "D. Stimits" cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam In-Reply-To: <3B48C484.FCA7BDBC@idcomm.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 8 Jul 2001, D. Stimits wrote: > I'm forwarding something that apparently is from email harvesting. I > doubt there is anything to be done to prevent spam harvesters, but > considering how terrible it has become on gnu.org lists, I'll pose the > question: is there anything, on a practical basis, that can help prevent > spam email from being generated through this list? I suspect the answer > is "no", but I thought I'd ask. I'm pasting the full header of the > offending email below. I'd probably forward this to an abuse account at > the sending location if not for the fact that it is a .jp, and Japan > routinely supports spamming (there is no help in reporting spammers to > Japanese ISP's it seems). It didn't originate at a Japanese ISP -- if you look at the headers, the spammer appears to have used a Popsite dial-up. It might be a good idea if the linux-xfs list was set to use the MAPS DUL and RBL, not to mention RSS. -- Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:27:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68MR6b22563 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:27:06 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68MR5V22559 for ; Sun, 8 Jul 2001 15:27:05 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip35.idcomm.com [209.60.72.162]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f68MTpa22415 for ; Sun, 8 Jul 2001 16:29:51 -0600 Message-ID: <3B48DEB5.CAE7BE98@idcomm.com> Date: Sun, 08 Jul 2001 16:29:09 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Juha Saarinen wrote: > > On Sun, 8 Jul 2001, D. Stimits wrote: > > > I'm forwarding something that apparently is from email harvesting. I > > doubt there is anything to be done to prevent spam harvesters, but > > considering how terrible it has become on gnu.org lists, I'll pose the > > question: is there anything, on a practical basis, that can help prevent > > spam email from being generated through this list? I suspect the answer > > is "no", but I thought I'd ask. I'm pasting the full header of the > > offending email below. I'd probably forward this to an abuse account at > > the sending location if not for the fact that it is a .jp, and Japan > > routinely supports spamming (there is no help in reporting spammers to > > Japanese ISP's it seems). > > It didn't originate at a Japanese ISP -- if you look at the headers, the > spammer appears to have used a Popsite dial-up. > > It might be a good idea if the linux-xfs list was set to use the MAPS DUL > and RBL, not to mention RSS. > > -- Juha > > PGP fingerprint: > B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 Looking closer, I see that it was a "TO" address of Japan. More confusing is: Sender: owner-linux-xfs@oss.sgi.com Does that mean there was an attempt to forge the header? Or maybe sgi is being used as a relay? I see now the actual sender (and the ISP is about to get an email): "West Quinn" Spam is kind of ridiculous these days. :( D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:38:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68Mcmc22994 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:38:48 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68MckV22990 for ; Sun, 8 Jul 2001 15:38:46 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15JNCM-0003iR-00; Mon, 09 Jul 2001 10:38:42 +1200 Date: Mon, 9 Jul 2001 10:38:42 +1200 (NZST) From: Juha Saarinen To: "D. Stimits" cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam In-Reply-To: <3B48DEB5.CAE7BE98@idcomm.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 8 Jul 2001, D. Stimits wrote: > Looking closer, I see that it was a "TO" address of Japan. More > confusing is: > Sender: > owner-linux-xfs@oss.sgi.com > > Does that mean there was an attempt to forge the header? Or maybe sgi is > being used as a relay? No, the spammer sent the crap to the linux-xfs list, which then redistributed it to all the subscribers. You need to work your way down the Received from: chain to find the originating MTA or sending MUA. Some MTAs don't record the sender's IP of course... > I see now the actual sender (and the ISP is about > to get an email): > "West Quinn" Probably a forgery. I've deleted the spam, but IIRC it originated from a Popsite dial-up. > Spam is kind of ridiculous these days. :( Kind of huge... some spammers are getting into the ISP business. :-( -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:38:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68Mcul23073 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:38:56 -0700 Received: from ente.berdmann.de (p3EE0A95C.dip.t-dialin.net [62.224.169.92]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68McsV23054 for ; Sun, 8 Jul 2001 15:38:55 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15JNCT-0001jV-00 for linux-xfs@oss.sgi.com; Mon, 09 Jul 2001 00:38:49 +0200 Message-ID: <3B48E0F9.4F566FFA@berdmann.de> Date: Mon, 09 Jul 2001 00:38:49 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre3-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam References: <3B48DEB5.CAE7BE98@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Looking closer, I see that it was a "TO" address of Japan. More > confusing is: > Sender: > owner-linux-xfs@oss.sgi.com > > Does that mean there was an attempt to forge the header? Or maybe sgi is > being used as a relay? I see now the actual sender (and the ISP is about > to get an email): > "West Quinn" The From: line is forged, too. Look at the Received: lines: Received: from mail.sidac.co.jp (dns.sidac.co.jp [211.6.163.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KIuV15580 for ; Sun, 8 Jul 2001 13:18:56 -0700 Received: from host (06-073.081.popsite.net [64.24.246.73]) by mail.sidac.co.jp (8.9.3/3.7Wpl2) with ESMTP id EAA06944; Mon, 9 Jul 2001 04:37:02 +0900 This spam originated from 06-073.081.popsite.net and was relayed through dns.sidac.co.jp to oss.sgi.com. I already sent a complaint to abuse@popsite.net. From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:46:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68Mkop23918 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:46:50 -0700 Received: from duval.se.mediaone.net (duval.se.mediaone.net [24.129.0.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68MknV23913 for ; Sun, 8 Jul 2001 15:46:50 -0700 Received: from enterprise (rr-163-49-70.atl.mediaone.net [24.163.49.70]) by duval.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f68MkfP23343 for ; Sun, 8 Jul 2001 18:46:41 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: Subject: Help... Everything moved to lost&found Date: Sun, 8 Jul 2001 18:46:40 -0400 Message-ID: <001201c107ff$daf10cd0$0101a8c0@enterprise> 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.2616 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This cannot be good! I had a couple of messages about Dirs not being found when running du. I did an xfs_check /dev/vg04/lv_movies, got a lot of messages so I ran xfs_repair /dev/vg04/lv_movies. Now my filesystem has been moved to lost&found, and carefully encrypted using, I'm assuming, i-node numbers. Short of looking at every file & dir, is there an easy way to rebuild my file names? Thanks Justin From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:53:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68MraZ24505 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:53:36 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68MrZV24499 for ; Sun, 8 Jul 2001 15:53:35 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip35.idcomm.com [209.60.72.162]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f68MuLa24027 for ; Sun, 8 Jul 2001 16:56:21 -0600 Message-ID: <3B48E4EB.17478F80@idcomm.com> Date: Sun, 08 Jul 2001 16:55:39 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam References: <3B48DEB5.CAE7BE98@idcomm.com> <3B48E0F9.4F566FFA@berdmann.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Bernhard R. Erdmann" wrote: > > > Looking closer, I see that it was a "TO" address of Japan. More > > confusing is: > > Sender: > > owner-linux-xfs@oss.sgi.com > > > > Does that mean there was an attempt to forge the header? Or maybe sgi is > > being used as a relay? I see now the actual sender (and the ISP is about > > to get an email): > > "West Quinn" > > The From: line is forged, too. > > Look at the Received: lines: > > Received: from mail.sidac.co.jp (dns.sidac.co.jp [211.6.163.50]) > by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68KIuV15580 > for ; Sun, 8 Jul 2001 13:18:56 -0700 > Received: from host (06-073.081.popsite.net [64.24.246.73]) > by mail.sidac.co.jp (8.9.3/3.7Wpl2) with ESMTP id EAA06944; > Mon, 9 Jul 2001 04:37:02 +0900 > > This spam originated from 06-073.081.popsite.net and was relayed through > dns.sidac.co.jp to oss.sgi.com. > I already sent a complaint to abuse@popsite.net. You probably can't hear it, but I am cheering now. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:55:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68MtVU24685 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:55:31 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68MtUV24682 for ; Sun, 8 Jul 2001 15:55:30 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15JNSZ-0003jC-00; Mon, 09 Jul 2001 10:55:27 +1200 Date: Mon, 9 Jul 2001 10:55:27 +1200 (NZST) From: Juha Saarinen To: "D. Stimits" cc: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam In-Reply-To: <3B48E4EB.17478F80@idcomm.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 8 Jul 2001, D. Stimits wrote: > You probably can't hear it, but I am cheering now. Don't... it'll likely be a "whack-a-mole" cheap dial-up account bought with a stolen credit card number. The spammer will just get new ones... -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Sun Jul 8 15:55:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68Mtmo24796 for linux-xfs-outgoing; Sun, 8 Jul 2001 15:55:48 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68MtlV24793 for ; Sun, 8 Jul 2001 15:55:47 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA25621 for ; Sun, 8 Jul 2001 15:55:39 -0700 (PDT) mail_from (dxm@snort.melbourne.sgi.com) Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id IAA41825; Mon, 9 Jul 2001 08:54:28 +1000 (EST) Message-Id: <200107082254.IAA41825@snort.melbourne.sgi.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Will Francis cc: linux-xfs@oss.sgi.com Subject: Re: minimum memory? In-reply-to: Your message of "Fri, 06 Jul 2001 14:43:17 MST." <200107062143.f66LhH207630@vertigo.incyte.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 09 Jul 2001 08:54:28 +1000 From: Daniel Moore Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Will Francis writes: => => I have a 486/100 laptop which I'm going to turn into a => sort of embedded device. I'd like to, if possible, => run 7.1+XFS on it. It has only 8MB of memory though, => so I'm curious if that would be an issue. If so, => what would be the minimum recommended amount? It's going => to be polling a device over the serial port at certain => intervals, so I'm going to shut off as many other services => and things like virtual terminals, etc as possible. => Would I see much of a savings if I were to recompile the => source and tweak, or are things already pretty well => modularized? I know that XFS patch is pretty darn big... I suspect it will run ok - the only way to find out is to try. I've tested on a 16Mb P100 and it was fine. ----------------------------------------------------- Daniel Moore dxm@sgi.com R&D Software Engineer Phone: +61-3-98348209 SGI Performance Tools Group Fax: +61-3-98132378 ----------------------------------------------------- From owner-linux-xfs@oss.sgi.com Sun Jul 8 16:20:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68NKDj26632 for linux-xfs-outgoing; Sun, 8 Jul 2001 16:20:13 -0700 Received: from citadel.oehansen.pp.se (sdu61-205.ppp.algonet.se [195.163.205.61]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68NKAV26625 for ; Sun, 8 Jul 2001 16:20:11 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f68NMB222142 for ; Mon, 9 Jul 2001 01:22:11 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: "XFS: linux-xfs@oss.sgi.com" Subject: Re: spam Date: Mon, 9 Jul 2001 01:22:11 +0200 X-Mailer: KMail [version 1.2] References: In-Reply-To: X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 X-MIME-Autoconverted: from 8bit to quoted-printable by citadel.oehansen.pp.se id f68NMB222142 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f68NKCV26630 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk mánudagur 9. júlí 2001 00:55, Juha Saarinen skrifaði: > On Sun, 8 Jul 2001, D. Stimits wrote: > > You probably can't hear it, but I am cheering now. > > Don't... it'll likely be a "whack-a-mole" cheap dial-up account bought > with a stolen credit card number. The spammer will just get new ones... I don't know much about this stuff, but I always keep in mind an old saying "good or bad attention, as good advertisment if it catches attention". Meaning that *any* attention paid to it, means the spammer got what he wanted. I usually just hit *delete* and ignore them. From owner-linux-xfs@oss.sgi.com Sun Jul 8 16:25:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68NPel27151 for linux-xfs-outgoing; Sun, 8 Jul 2001 16:25:40 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68NPcV27148 for ; Sun, 8 Jul 2001 16:25:39 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15JNvk-0003lY-01; Mon, 09 Jul 2001 11:25:36 +1200 From: "Juha Saarinen" To: , Subject: RE: spam Date: Mon, 9 Jul 2001 11:25:42 +1200 Message-ID: <060001c10805$4e9b64f0$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <01070901221101.02036@citadel.oehansen.pp.se> Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk :: I don't know much about this stuff, but I always keep in :: mind an old saying :: "good or bad attention, as good advertisment if it catches :: attention". :: Meaning that *any* attention paid to it, means the spammer :: got what he wanted. Nope. I have no idea what he was spamvertising. I just looked at the headers and filed a complaint with Popsite. :: :: I usually just hit *delete* and ignore them. If everyone did that, email would be 99.9% spam. It's actually better to complain, and let ISPs know that you don't wish to receive spam. -- Juha From owner-linux-xfs@oss.sgi.com Sun Jul 8 16:42:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f68NgGW28653 for linux-xfs-outgoing; Sun, 8 Jul 2001 16:42:16 -0700 Received: from ente.berdmann.de (p3EE0A95C.dip.t-dialin.net [62.224.169.92]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f68NgEV28650 for ; Sun, 8 Jul 2001 16:42:15 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15JOBl-00021H-00 for linux-xfs@oss.sgi.com; Mon, 09 Jul 2001 01:42:09 +0200 Message-ID: <3B48EFD1.B5BF38D7@berdmann.de> Date: Mon, 09 Jul 2001 01:42:09 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre3-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Help... Everything moved to lost&found References: <001201c107ff$daf10cd0$0101a8c0@enterprise> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Now my filesystem has been moved to lost&found, and carefully encrypted > using, I'm assuming, i-node numbers. > > Short of looking at every file & dir, is there an easy way to rebuild my > file names? Maybe by restoring a backup? From owner-linux-xfs@oss.sgi.com Sun Jul 8 22:56:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f695uJg28558 for linux-xfs-outgoing; Sun, 8 Jul 2001 22:56:19 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f695uFV28548 for ; Sun, 8 Jul 2001 22:56:15 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA23929 for ; Sun, 8 Jul 2001 22:55:39 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA12545; Mon, 9 Jul 2001 15:54:29 +1000 (EST) Date: Mon, 9 Jul 2001 15:54:29 +1000 From: Timothy Shimmin To: "Bernhard R. Erdmann" Cc: Linux XFS Mailing List Subject: Re: xfsdump/xfsrestore fails Zwicky's torture test Message-ID: <20010709155428.C11622@boing.melbourne.sgi.com> References: <3B3F5079.F1776C04@berdmann.de> <3B4838D0.5BAEDF4F@berdmann.de> <3B485058.9389834C@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B485058.9389834C@berdmann.de>; from be@berdmann.de on Sun, Jul 08, 2001 at 02:21:44PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Bernard, You've had a few xfsdump/xfsrestore emails of late :) On Sun, Jul 08, 2001 at 02:21:44PM +0200, Bernhard R. Erdmann wrote: > I just did some torture testing with xfsdump/xfsrestore (Kernel > linux-2.4.7-pre3-xfs, checkout 04:30 GMT). > > Using a perl script referenced from > http://reality.sgi.com/zwicky_neu/testdump.doc.html (Torture-testing > Backup and Archive Programs: Things You Ought to Know But Probably Would > Rather Not, Elizabeth D. Zwicky, 1991) > > I had to modify torture.perl (10 years old) in order to run with a > modern linux system. You can download it from > http://berdmann.dyndns.org/torture.tar.gz > Sounds interesting - I like the title - I can relate to it (particularly the "But Probably Would Rather Not" part :) It sounds a good src of pv's (read that "bug reports") :) It would also be a good test program for cmd/xfstests. > > I gave a filesystem with the "directory from Hell" to xfsdump, but > xfsrestore fails in content.c to read the directory index: > > # ~be/torture-new/torture.perl > First guess at max component length is 255 > max path length appears to be 4095 > Type a command line which will run a backup program on the dump test > directory: /sbin/xfsdump -J - /mnt/test1 | (cd > /mnt/test2/linux-xfsrestore && /sbin/xfsrestore - .) > Child 1 > /sbin/xfsrestore: version 3.0 - Running single-threaded > /sbin/xfsrestore: reading directories > xfsrestore: content.c:2942: applydirdump: Assertion `namelen < 255' > failed. > Okay it looks like xfsdump is happy to dump files with names >= 255 in length, but xfsrestore is not happy to restore them. This bug would also occur in IRIX. I'll post a bug on this in SGI to be fixed. Thanks for the info. On Sun, Jul 08, 2001 at 12:41:20PM +0200, Bernhard R. Erdmann wrote: > > today I did some restore tests (do you really trust your backups?) > > Then I used tar to compare the two directory trees: > > # (cd /var/spool/imap && tar cf - .) | tar df - > [...] > tar: ./user/be/Sent/xy/290.: Warning: Cannot stat: No such file or > directory > [...] > > Lots of files were missing (mostly due to reorganisation, aka moving > mails to different folders). I traced the history of this particular > file user/be/Sent/xy/290. > > > What did xfsrestore do to my holy IMAP spool??? Don't know - deleted it perhaps :) > > > xfsrestore.debug.3 told me xfsrestore had deleted user/be/Sent/xy/290.: > > [...] > /usr/sbin/xfsrestore: rename nondir user/be/Sent/xy/290. to > orphanage/9074670.1 > /usr/sbin/xfsrestore: unlink nondir orphanage/9074670.1 > [...] > /usr/sbin/xfsrestore: restoring user/be/Sent/xy/291. (9074676 0) > /usr/sbin/xfsrestore: restoring regular file ino 9074676 > user/be/Sent/xy/291. > /usr/sbin/xfsrestore: truncating user/be/Sent/xy/291. from 0 to 775 > /usr/sbin/xfsrestore: restore complete: 76 seconds elapsed > > What's going on here? I'm using xfsdump-1.0.9-0. It looks like that this is happening in the function xfsdump/restore/tree.c/proc_hardlinks_cb(). I'm not sure what this code is trying to do ! However, I'll post a bug on this at SGI and look into it further. Thanks for the report. On Sun, Jul 01, 2001 at 06:31:53PM +0200, Bernhard R. Erdmann wrote: > Hi, > > i'm able to lock up xfsrestore when restoring onto a JFS filesystem. Bummer. Not likely to be a high priority for us though ;-) > xfsrestore becomes dead in ps and is unkillable (waiting for I/O to > happen?): > > # /sbin/mkfs.jfs /dev/vg01/usrjfs > # cd /tmp > # mount -t jfs /dev/vg01/usrjfs /mnt/usr > # strace /sbin/xfsrestore -f tmp.xfsd /mnt/usr > [..bla..] perspath = open_pathalloc( tranp->t_hkdir, persname, 0 ); tranp->t_persfd = open( perspath, O_CREAT | O_RDWR, S_IRUSR | S_IWUSR ); > open("/mnt/usr/xfsrestorehousekeepingdir/state", > O_RDWR|O_CREAT|O_LARGEFILE, 0600) = 4 persp = ( pers_t * ) mmap_autogrow(perssz, tranp->t_persfd, 0); mmap_autogrow(): > SYS_197(0x4, 0xbffff990, 0x4010cd40, 0, 0x4) = 0 fstat64() > _llseek(4, 20479, [20479], SEEK_SET) = 0 > write(4, "\0", 1) = 1 > SYS_192(0, 0x5000, 0x3, 0x1, 0x4) = 1073831936 mmap2() ownerpr = ( geteuid( ) == 0 ) ? BOOL_TRUE : ownerpr; > geteuid() = 0 rval = munmap( ( void * )persp, perssz ); > munmap(0x40016000, 20480) = 0 rval = ftruncate( tranp->t_persfd, ( off_t )perssz + ( off_t )( stpgcnt + descpgcnt ) * ( off_t )pgsz ); > SYS_194(0x4, 0x5000, 0, 0, 0x4 ftruncate64 > > ...and there it ends. It looks like it is hanging on line 1606 in a call to ftruncate() in xfsdump/restore/content.c/content_init(). It can't seem to ftruncate() /mnt/usr/xfsrestorehousekeepingdir/state. The file gets opened, written to, mapped, unmapped and then truncated, where it hangs. I don't know why it is hanging when truncating. Perhaps you could try a simple test program which does similar calls as xfsrestore. I doesn't look like an xfsrestore problem. Cheers, Tim. From owner-linux-xfs@oss.sgi.com Sun Jul 8 23:12:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f696CDs29249 for linux-xfs-outgoing; Sun, 8 Jul 2001 23:12:13 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f696CBV29246 for ; Sun, 8 Jul 2001 23:12:11 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA01973; Mon, 9 Jul 2001 08:12:09 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA08444; Mon, 9 Jul 2001 08:12:09 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id A542A57306; Mon, 9 Jul 2001 08:21:25 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 6C1D725835; Mon, 9 Jul 2001 08:29:26 +0200 (CEST) Message-ID: <3B494B4A.6F55C30C@ch.sauter-bc.com> Date: Mon, 09 Jul 2001 08:12:26 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Will Francis Cc: linux-xfs@oss.sgi.com Subject: Re: minimum memory? References: <200107062143.f66LhH207630@vertigo.incyte.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Will Francis schrieb: > > I have a 486/100 laptop which I'm going to turn into a > sort of embedded device. I'd like to, if possible, > run 7.1+XFS on it. It has only 8MB of memory though, > so I'm curious if that would be an issue. If so, > what would be the minimum recommended amount? It's going > to be polling a device over the serial port at certain > intervals, so I'm going to shut off as many other services > and things like virtual terminals, etc as possible. > Would I see much of a savings if I were to recompile the > source and tweak, or are things already pretty well > modularized? I know that XFS patch is pretty darn big... > > thanks, > > Will Hi I was running 7.1XFS on a P200MMX with mem=12M without any problem. It was like chewing gum but it has worked fine so far. I was even running it on SoftRAID 5 and tried to kill it with the power button while running some copy jobs. No problem at all. Didn't try with 8M. Simon From owner-linux-xfs@oss.sgi.com Sun Jul 8 23:30:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f696UCN30178 for linux-xfs-outgoing; Sun, 8 Jul 2001 23:30:12 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f696UBV30172 for ; Sun, 8 Jul 2001 23:30:11 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA04568; Mon, 9 Jul 2001 08:30:00 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA09695; Mon, 9 Jul 2001 08:29:59 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 2E90357306; Mon, 9 Jul 2001 08:39:09 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 8E0AF25835; Mon, 9 Jul 2001 08:47:08 +0200 (CEST) Message-ID: <3B494F6F.61CFB13A@ch.sauter-bc.com> Date: Mon, 09 Jul 2001 08:30:07 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Steve Lord Cc: Andrew Morton , Jens Axboe , Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: More on write caching References: <200107071411.f67EB9323526@jen.americas.sgi.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord schrieb: > > > Jens Axboe wrote: > > > > > > > Question is: does IDE need it at all? If we can assume > > > > that the data is safe once the drive has acked it, then that's > > > > all a journalling fs cares about, yes? > > > > > > It would enable safe use of write caching, so yes. For a barrier write, > > > do a sync flush following a write/write_dma/write_dma_queued command > > > (yes dma_queued has no ordered/sync option, yay ide). > > > > There was some discussion a while back, (triggered by someone's > > benchmark where IDE was thrashing SCSI) where it turned out that > > some IDE disks were simply ignoring the flush command. > > I think the issue was that write caching was on on ide disks by default > where on scsi it is usually off by default. The discussion was about O_SYNC, > and they got the expected performance by disabling the caching. > > I think the only real answer is to write some tests which can be run > on a raw disk. Work out the cache size of a device and push about that > much data out to a raw disk, then drop the power. The tricky part is > dropping the power quickly enough, is it possible to hook into apm > or something and drop the power automatically? Then check that the > data made it to disk after power up. You would need to run lots of > cases to trust a device with write caching on. > > This would at least give us a testbed for drives and is somewhat similar > to part of the process SGI uses to qualify scsi drives for hardware. > > Steve > > > > > Which is a quite sane thing to do if the write cache integrity > > is guaranteed in this manner. > > > > What's the story with other storage interfaces apart from SCSI? > > Seems that most of them implement SCSI in some way anyway - are > > there other technologies that need thinking about? I would never trust an IDE disk will flush the cache somewhere when power goes off. Some disks may do it, some will just use the capasitors energy to safely park the heads and some will not even do that. How can you know and how can one be sure? I remember a problem people were having with windows(don't know) on fast machines with soft power down. The machine was shutdown too fast and poweroff without giving enough time to flush the cache and data was lost. So how could this happen if the disk did write the cache out to disks somewhere when power went off? Simon From owner-linux-xfs@oss.sgi.com Mon Jul 9 01:27:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f698Rv503618 for linux-xfs-outgoing; Mon, 9 Jul 2001 01:27:57 -0700 Received: from server.hotswap (atbode95.informatik.tu-muenchen.de [131.159.32.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f698RtV03614 for ; Mon, 9 Jul 2001 01:27:55 -0700 Received: from cs.tum.edu (kuschel.hotswap [172.16.16.190]) by server.hotswap (swapfix) with ESMTP id D877139654CD for ; Mon, 9 Jul 2001 10:27:48 +0200 (CEST) Message-ID: <3B496B02.E35CFC07@cs.tum.edu> Date: Mon, 09 Jul 2001 10:27:46 +0200 From: Deti Fliegl X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre2-xfs i686) X-Accept-Language: en, de MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: XFS Crash with 2.4.6-pre9 (reproduceable) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This oops happens reproducabe every 2-3 days on a duron system with a 37Gbyte xfs-partition: ksymoops 0.7c on i686 2.4.6-pre9-xfs. Options used Unable to handle kernel NULL pointer dereference at virtual address 00000152 c01cfa32 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: 00000000 ebx: ffffffe8 ecx: c1235880 edx: c0358c60 esi: c219020c edi: c7c39000 ebp: 00000000 esp: c55cbce4 ds: 0018 es: 0018 ss: 0018 Process mot (pid: 11251, stackpage=c55cb000) Stack: 00009d7c 00000000 c7c39000 00000008 c01e65bc c7c39000 00000000 0118fad0 00000000 00000000 c55cbdc8 00000000 00000000 00000000 c55cbdd8 c55cbdc0 c55cbe94 c6d99f00 00000000 00000286 00000286 0006d990 c0185cf1 c7c39000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 66 83 bb 6a 01 00 00 00 75 10 80 a3 50 01 00 00 f7 53 e8 37 >>EIP; c01cfa32 <===== Trace; c01e65bc Trace; c0185cf1 <_pagebuf_get_pages+41/80> Trace; c01bade0 Trace; c01dfdfa Trace; c01e02d0 Trace; c01cf604 Trace; c01e0487 Trace; c01e02d0 Trace; c01e02d0 Trace; c014517b Trace; c01e65cc Trace; c01cfed6 Trace; c01cfef3 Trace; c01e4fe2 Trace; c01d002f Trace; c01e4fe2 Trace; c01d002f Trace; c01f4fd8 Trace; c01e02d0 Trace; c013d91e Trace; c013d9a9 Trace; c013dbac Trace; c0106e53 Code; c01cfa32 00000000 <_EIP>: Code; c01cfa32 <===== 0: 66 83 bb 6a 01 00 00 cmpw $0x0,0x16a(%ebx) <===== Code; c01cfa39 7: 00 Code; c01cfa3a 8: 75 10 jne 1a <_EIP+0x1a> c01cfa4c Code; c01cfa3c a: 80 a3 50 01 00 00 f7 andb $0xf7,0x150(%ebx) Code; c01cfa43 11: 53 push %ebx Code; c01cfa44 12: e8 37 00 00 00 call 4e <_EIP+0x4e> c01cfa80 From owner-linux-xfs@oss.sgi.com Mon Jul 9 01:54:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f698srg04940 for linux-xfs-outgoing; Mon, 9 Jul 2001 01:54:53 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f698spV04936 for ; Mon, 9 Jul 2001 01:54:51 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f698qmn23555; Mon, 9 Jul 2001 10:52:48 +0200 Message-Id: <4.3.2.7.2.20010709104934.029ef710@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 09 Jul 2001 10:52:38 +0200 To: Deti Fliegl , "linux-xfs@oss.sgi.com" From: Seth Mos Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) In-Reply-To: <3B496B02.E35CFC07@cs.tum.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 10:27 9-7-2001 +0200, Deti Fliegl wrote: >This oops happens reproducabe every 2-3 days on a duron system with a >37Gbyte xfs-partition: What compiler did you use? What system is this on? Did you encouter this with previous kernels? Does it also happen with 2.4.7-pre3? (CVS) A bit more details please. >ksymoops 0.7c on i686 2.4.6-pre9-xfs. Options used >Unable to handle kernel NULL pointer dereference at virtual address >00000152 >c01cfa32 >*pde = 00000000 >Oops: 0000 >CPU: 0 >EIP: 0010:[] >Using defaults from ksymoops -t elf32-i386 -a i386 >EFLAGS: 00010246 >eax: 00000000 ebx: ffffffe8 ecx: c1235880 edx: c0358c60 >esi: c219020c edi: c7c39000 ebp: 00000000 esp: c55cbce4 >ds: 0018 es: 0018 ss: 0018 >Process mot (pid: 11251, stackpage=c55cb000) >Stack: 00009d7c 00000000 c7c39000 00000008 c01e65bc c7c39000 00000000 >0118fad0 > 00000000 00000000 c55cbdc8 00000000 00000000 00000000 c55cbdd8 >c55cbdc0 > c55cbe94 c6d99f00 00000000 00000286 00000286 0006d990 c0185cf1 >c7c39000 >Call Trace: [] [] [] [] >[] [] [] > [] [] [] [] [] >[] [] [] > [] [] [] [] [] >[] [] [] >Code: 66 83 bb 6a 01 00 00 00 75 10 80 a3 50 01 00 00 f7 53 e8 37 > > >>EIP; c01cfa32 <===== >Trace; c01e65bc >Trace; c0185cf1 <_pagebuf_get_pages+41/80> >Trace; c01bade0 >Trace; c01dfdfa >Trace; c01e02d0 >Trace; c01cf604 >Trace; c01e0487 >Trace; c01e02d0 >Trace; c01e02d0 >Trace; c014517b >Trace; c01e65cc >Trace; c01cfed6 >Trace; c01cfef3 >Trace; c01e4fe2 >Trace; c01d002f >Trace; c01e4fe2 >Trace; c01d002f >Trace; c01f4fd8 >Trace; c01e02d0 >Trace; c013d91e >Trace; c013d9a9 >Trace; c013dbac >Trace; c0106e53 >Code; c01cfa32 >00000000 <_EIP>: >Code; c01cfa32 <===== > 0: 66 83 bb 6a 01 00 00 cmpw $0x0,0x16a(%ebx) <===== >Code; c01cfa39 > 7: 00 >Code; c01cfa3a > 8: 75 10 jne 1a <_EIP+0x1a> c01cfa4c > >Code; c01cfa3c > a: 80 a3 50 01 00 00 f7 andb $0xf7,0x150(%ebx) >Code; c01cfa43 > 11: 53 push %ebx >Code; c01cfa44 > 12: e8 37 00 00 00 call 4e <_EIP+0x4e> c01cfa80 > -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 9 01:56:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f698uUM05147 for linux-xfs-outgoing; Mon, 9 Jul 2001 01:56:30 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f698uTV05144 for ; Mon, 9 Jul 2001 01:56:29 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f698uNn23582; Mon, 9 Jul 2001 10:56:24 +0200 Message-Id: <4.3.2.7.2.20010709105253.02ac25e8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 09 Jul 2001 10:56:13 +0200 To: , From: Seth Mos Subject: Re: Help... Everything moved to lost&found In-Reply-To: <001201c107ff$daf10cd0$0101a8c0@enterprise> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 18:46 8-7-2001 -0400, Justin Hamilton wrote: >This cannot be good! > >I had a couple of messages about Dirs not being found when running du. > >I did an xfs_check /dev/vg04/lv_movies, got a lot of messages so I ran >xfs_repair /dev/vg04/lv_movies. > >Now my filesystem has been moved to lost&found, and carefully encrypted >using, I'm assuming, i-node numbers. correct >Short of looking at every file & dir, is there an easy way to rebuild my >file names? Not that I know of, A XFS guru is better educated at guessing what went wrong. Can you give me a bit more details about the system and what is was doing beforehand. Did you compile this kernel yourself or was this a SGI release? If you compiled it yourself I hope you did that using kgcc on redhat systems. gcc-2.96-whatever is still not safe for data integrity. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 9 02:04:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6994Oe05693 for linux-xfs-outgoing; Mon, 9 Jul 2001 02:04:24 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6994MV05690 for ; Mon, 9 Jul 2001 02:04:23 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15JWxa-0004BU-00; Mon, 09 Jul 2001 21:04:06 +1200 Date: Mon, 9 Jul 2001 21:04:06 +1200 (NZST) From: Juha Saarinen To: Seth Mos cc: "JHamilton@Earthling.Net" , "linux-xfs@oss.sgi.com" Subject: Re: Help... Everything moved to lost&found In-Reply-To: <4.3.2.7.2.20010709105253.02ac25e8@pop.xs4all.nl> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 9 Jul 2001, Seth Mos wrote: > If you compiled it yourself I hope you did that using kgcc on redhat systems. > gcc-2.96-whatever is still not safe for data integrity. Not sure -- my system's been OK with gcc 2.96-88 from Red Hat Rawhide. The stock RH gcc 2.96-85 isn't happy with XFS though. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Mon Jul 9 02:25:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f699PlK07548 for linux-xfs-outgoing; Mon, 9 Jul 2001 02:25:47 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f699PkV07541 for ; Mon, 9 Jul 2001 02:25:46 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f699PXn23834; Mon, 9 Jul 2001 11:25:35 +0200 Message-Id: <4.3.2.7.2.20010709112339.034083d8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 09 Jul 2001 11:25:23 +0200 To: Juha Saarinen From: Seth Mos Subject: Re: Help... Everything moved to lost&found Cc: "JHamilton@Earthling.Net" , "linux-xfs@oss.sgi.com" In-Reply-To: References: <4.3.2.7.2.20010709105253.02ac25e8@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:04 9-7-2001 +1200, Juha Saarinen wrote: >On Mon, 9 Jul 2001, Seth Mos wrote: > > > If you compiled it yourself I hope you did that using kgcc on redhat > systems. > > gcc-2.96-whatever is still not safe for data integrity. > >Not sure -- my system's been OK with gcc 2.96-88 from Red Hat Rawhide. The >stock RH gcc 2.96-85 isn't happy with XFS though. But in general XFS does not like 2.96 and you should avoid it for your critical data. Feel free to use it on your test machines but avoid it for production machines. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 9 02:28:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f699Shi08057 for linux-xfs-outgoing; Mon, 9 Jul 2001 02:28:43 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f699SfV08054 for ; Mon, 9 Jul 2001 02:28:42 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15JXLG-0004Bt-00; Mon, 09 Jul 2001 21:28:34 +1200 Date: Mon, 9 Jul 2001 21:28:34 +1200 (NZST) From: Juha Saarinen To: Seth Mos cc: "JHamilton@Earthling.Net" , "linux-xfs@oss.sgi.com" Subject: Re: Help... Everything moved to lost&found In-Reply-To: <4.3.2.7.2.20010709112339.034083d8@pop.xs4all.nl> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 9 Jul 2001, Seth Mos wrote: > But in general XFS does not like 2.96 and you should avoid it for your > critical data. Feel free to use it on your test machines but avoid it for > production machines. Yes... but if you say that, you should try to explain why. Unfortunately, I haven't been able to pinpoint the change between -85 and -88 that made all the difference between a stable system, and one that suffered file system corruption very easily. It could be the newer CVS code as well, but I don't know for sure. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Mon Jul 9 02:28:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f699Sw108150 for linux-xfs-outgoing; Mon, 9 Jul 2001 02:28:58 -0700 Received: from server.hotswap (atbode95.informatik.tu-muenchen.de [131.159.32.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f699SvV08147 for ; Mon, 9 Jul 2001 02:28:57 -0700 Received: from cs.tum.edu (kuschel.hotswap [172.16.16.190]) by server.hotswap (swapfix) with ESMTP id A154D39654CD; Mon, 9 Jul 2001 11:28:51 +0200 (CEST) Message-ID: <3B497953.F9D8ACE8@cs.tum.edu> Date: Mon, 09 Jul 2001 11:28:51 +0200 From: Deti Fliegl X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre2-xfs i686) X-Accept-Language: en, de MIME-Version: 1.0 To: Seth Mos Cc: "linux-xfs@oss.sgi.com" Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) References: <4.3.2.7.2.20010709104934.029ef710@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > At 10:27 9-7-2001 +0200, Deti Fliegl wrote: > >This oops happens reproducabe every 2-3 days on a duron system with a > >37Gbyte xfs-partition: > > What compiler did you use? What system is this on? kgcc-1.1.2-40 gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release) from redhat distribution, originally it is a SuSE 7.1 installation. > Did you encouter this with previous kernels? Does it also happen with > 2.4.7-pre3? (CVS) I just installed the latest CVS version on this machine (still waiting for errors :) On this particular filesystem are about 1.400.000 files and about 25.000 of them are created and removed within 24 hours. Deti From owner-linux-xfs@oss.sgi.com Mon Jul 9 02:48:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f699m3k09943 for linux-xfs-outgoing; Mon, 9 Jul 2001 02:48:03 -0700 Received: from dmz.tecosim.de ([194.24.222.241]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f699lxV09928 for ; Mon, 9 Jul 2001 02:48:00 -0700 Received: (from uucp@localhost) by dmz.tecosim.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) id f699YrT18790; Mon, 9 Jul 2001 11:34:53 +0200 Received: from ns.tecosim.de(194.24.222.9) via SMTP by dmz.tecosim.de, id smtpdnnUXjb; Mon Jul 9 11:34:47 2001 Received: from donner.tecosim.de (donner.tecosim.de [194.24.222.109]) by ns.tecosim.de (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id f699kHi08741; Mon, 9 Jul 2001 11:46:17 +0200 Received: (from leh@localhost) by donner.tecosim.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id f699kHY01570; Mon, 9 Jul 2001 11:46:17 +0200 Date: Mon, 9 Jul 2001 11:46:17 +0200 From: Utz Lehmann To: Timothy Shimmin Cc: "Bernhard R. Erdmann" , Linux XFS Mailing List Subject: Re: xfsdump/xfsrestore fails Zwicky's torture test Message-ID: <20010709114617.A1269@de.tecosim.com> References: <3B3F5079.F1776C04@berdmann.de> <3B4838D0.5BAEDF4F@berdmann.de> <3B485058.9389834C@berdmann.de> <20010709155428.C11622@boing.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010709155428.C11622@boing.melbourne.sgi.com>; from tes@boing.melbourne.sgi.com on Mon, Jul 09, 2001 at 03:54:29PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Timothy Shimmin [tes@boing.melbourne.sgi.com] wrote: > > i'm able to lock up xfsrestore when restoring onto a JFS filesystem. > Bummer. > Not likely to be a high priority for us though ;-) I have lockups with JFS too. Not using xfsrestore but other programms. Process hangs in D state (kflushd, sync too). With the Linux Test Project (http://ltp.sourceforge.net/) i get JFS lockups with 100% guarantee. I doubt xfsrestore is wrong here. utz From owner-linux-xfs@oss.sgi.com Mon Jul 9 03:29:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69ATJU14509 for linux-xfs-outgoing; Mon, 9 Jul 2001 03:29:19 -0700 Received: from server.hotswap (atbode95.informatik.tu-muenchen.de [131.159.32.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69ATIV14505 for ; Mon, 9 Jul 2001 03:29:18 -0700 Received: from cs.tum.edu (kuschel.hotswap [172.16.16.190]) by server.hotswap (swapfix) with ESMTP id E1DFD39654CD; Mon, 9 Jul 2001 12:29:11 +0200 (CEST) Message-ID: <3B498777.80724DE3@cs.tum.edu> Date: Mon, 09 Jul 2001 12:29:11 +0200 From: Deti Fliegl X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre2-xfs i686) X-Accept-Language: en, de MIME-Version: 1.0 To: Seth Mos Cc: "linux-xfs@oss.sgi.com" Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) References: <4.3.2.7.2.20010709104934.029ef710@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk with 2.4.7-pre3-xfs a syslog message is generated instead of oopsing: xfs_iunlink_remove: xfs_itobp() returned an error 990 on ide0(3,4). Returning error. xfs_inactive: xfs_ifree() returned an error = 990 on ide0(3,4) xfs_force_shutdown(ide0(3,4),0x1) called from line 1944 of file xfs_vnodeops.c. Return address = 0xc01eb429 I/O Error Detected. Shutting down filesystem: ide0(3,4) Please umount the filesystem, and rectify the problem(s) Now xfs_check is running... Deti From owner-linux-xfs@oss.sgi.com Mon Jul 9 03:42:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69AgYG14990 for linux-xfs-outgoing; Mon, 9 Jul 2001 03:42:34 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69AgWV14984 for ; Mon, 9 Jul 2001 03:42:32 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f69AeTn24222; Mon, 9 Jul 2001 12:40:29 +0200 Message-Id: <4.3.2.7.2.20010709123942.02ae9b28@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 09 Jul 2001 12:40:19 +0200 To: Deti Fliegl From: Seth Mos Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) Cc: "linux-xfs@oss.sgi.com" In-Reply-To: <3B497953.F9D8ACE8@cs.tum.edu> References: <4.3.2.7.2.20010709104934.029ef710@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:28 9-7-2001 +0200, Deti Fliegl wrote: >Seth Mos wrote: > > > > At 10:27 9-7-2001 +0200, Deti Fliegl wrote: > > >This oops happens reproducabe every 2-3 days on a duron system with a > > >37Gbyte xfs-partition: > > > > What compiler did you use? What system is this on? >kgcc-1.1.2-40 gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 >release) from redhat distribution, >originally it is a SuSE 7.1 installation. That should be fine. > > Did you encouter this with previous kernels? Does it also happen with > > 2.4.7-pre3? (CVS) >I just installed the latest CVS version on this machine (still waiting >for errors :) okidoki ;) >On this particular filesystem are about 1.400.000 files and about 25.000 >of them are created and removed within 24 hours. A news server? -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 9 03:45:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69AjGf15189 for linux-xfs-outgoing; Mon, 9 Jul 2001 03:45:16 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69AjEV15184 for ; Mon, 9 Jul 2001 03:45:14 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f69AhCn24254; Mon, 9 Jul 2001 12:43:12 +0200 Message-Id: <4.3.2.7.2.20010709124124.033b58a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 09 Jul 2001 12:43:02 +0200 To: Deti Fliegl From: Seth Mos Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) Cc: "linux-xfs@oss.sgi.com" In-Reply-To: <3B498777.80724DE3@cs.tum.edu> References: <4.3.2.7.2.20010709104934.029ef710@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:29 9-7-2001 +0200, Deti Fliegl wrote: >with 2.4.7-pre3-xfs a syslog message is generated instead of oopsing: > >xfs_iunlink_remove: xfs_itobp() returned an error 990 on ide0(3,4). >Returning error. >xfs_inactive: xfs_ifree() returned an error = 990 on ide0(3,4) >xfs_force_shutdown(ide0(3,4),0x1) called from line 1944 of file >xfs_vnodeops.c. Return address = 0xc01eb429 >I/O Error Detected. Shutting down filesystem: ide0(3,4) >Please umount the filesystem, and rectify the problem(s) > >Now xfs_check is running... Ah, so it could be that there is a corruption issue or otherwise damaged fs that panics tha machine. If you decide to repair it try with -n first to see what it wants to change. What chipset information and IDE details can you provide. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 9 07:06:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69E63r28127 for linux-xfs-outgoing; Mon, 9 Jul 2001 07:06:03 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69E61V28122 for ; Mon, 9 Jul 2001 07:06:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA02744 for ; Mon, 9 Jul 2001 07:05:53 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2380904; Mon, 9 Jul 2001 09:04:44 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA04353; Mon, 9 Jul 2001 09:04:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f69E68Y31781; Mon, 9 Jul 2001 09:06:08 -0500 Message-Id: <200107091406.f69E68Y31781@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Deti Fliegl cc: "linux-xfs@oss.sgi.com" Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) In-Reply-To: Message from Deti Fliegl of "Mon, 09 Jul 2001 10:27:46 +0200." <3B496B02.E35CFC07@cs.tum.edu> Date: Mon, 09 Jul 2001 09:06:08 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Could you run gdb on the vmlinux file in the build directory and disassemble xfs_iget_core and send me the output please? Obviously this needs to be on the vmlinux which goes with the kernel that crashed - same build, same compiler. Thanks Steve > This oops happens reproducabe every 2-3 days on a duron system with a > 37Gbyte xfs-partition: > > ksymoops 0.7c on i686 2.4.6-pre9-xfs. Options used > Unable to handle kernel NULL pointer dereference at virtual address > 00000152 > c01cfa32 > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[] > Using defaults from ksymoops -t elf32-i386 -a i386 > EFLAGS: 00010246 > eax: 00000000 ebx: ffffffe8 ecx: c1235880 edx: c0358c60 > esi: c219020c edi: c7c39000 ebp: 00000000 esp: c55cbce4 > ds: 0018 es: 0018 ss: 0018 > Process mot (pid: 11251, stackpage=c55cb000) > Stack: 00009d7c 00000000 c7c39000 00000008 c01e65bc c7c39000 00000000 > 0118fad0 > 00000000 00000000 c55cbdc8 00000000 00000000 00000000 c55cbdd8 > c55cbdc0 > c55cbe94 c6d99f00 00000000 00000286 00000286 0006d990 c0185cf1 > c7c39000 > Call Trace: [] [] [] [] > [] [] [] > [] [] [] [] [] > [] [] [] > [] [] [] [] [] > [] [] [] > Code: 66 83 bb 6a 01 00 00 00 75 10 80 a3 50 01 00 00 f7 53 e8 37 > > >>EIP; c01cfa32 <===== > Trace; c01e65bc > Trace; c0185cf1 <_pagebuf_get_pages+41/80> > Trace; c01bade0 > Trace; c01dfdfa > Trace; c01e02d0 > Trace; c01cf604 > Trace; c01e0487 > Trace; c01e02d0 > Trace; c01e02d0 > Trace; c014517b > Trace; c01e65cc > Trace; c01cfed6 > Trace; c01cfef3 > Trace; c01e4fe2 > Trace; c01d002f > Trace; c01e4fe2 > Trace; c01d002f > Trace; c01f4fd8 > Trace; c01e02d0 > Trace; c013d91e > Trace; c013d9a9 > Trace; c013dbac > Trace; c0106e53 > Code; c01cfa32 > 00000000 <_EIP>: > Code; c01cfa32 <===== > 0: 66 83 bb 6a 01 00 00 cmpw $0x0,0x16a(%ebx) <===== > Code; c01cfa39 > 7: 00 > Code; c01cfa3a > 8: 75 10 jne 1a <_EIP+0x1a> c01cfa4c > > Code; c01cfa3c > a: 80 a3 50 01 00 00 f7 andb $0xf7,0x150(%ebx) > Code; c01cfa43 > 11: 53 push %ebx > Code; c01cfa44 > 12: e8 37 00 00 00 call 4e <_EIP+0x4e> c01cfa80 > From owner-linux-xfs@oss.sgi.com Mon Jul 9 07:13:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69EDle29008 for linux-xfs-outgoing; Mon, 9 Jul 2001 07:13:47 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69EDbV28982 for ; Mon, 9 Jul 2001 07:13:37 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA05612 for ; Mon, 9 Jul 2001 07:11:00 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id JAA55289 for ; Mon, 9 Jul 2001 09:12:20 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15Jbls-0006u9-00 for ; Mon, 09 Jul 2001 09:12:20 -0500 Date: Mon, 9 Jul 2001 09:12:20 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Deadlock while running on XFS Message-ID: <20010709091219.R883@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <15498.994487739@ocs3.ocs-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <15498.994487739@ocs3.ocs-net> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Okay, second try at decoding the output. This one looks better, but I still don't like how some parts look. As a side note, I ran the same tests on 2.4.3-XFS-PR3 for 30 hours this weekend without hitting this deadlock. ksymoops 2.4.2 on i686 2.4.3-SGI_XFS_1.0.1smp. Options used -V (default) -k ksyms (specified) -l /proc/modules (default) -o /lib/modules/2.4.3-SGI_XFS_1.0.1smp_1_IA32_SMP_20010705135821/ (specified) -m /boot/System.map-2.4.3-SGI_XFS_1.0.1smp_1_IA32_SMP_20010705135821 (specified) Error (pclose_local): find_objects pclose failed 0x100 Warning (compare_ksyms_lsmod): module ipchains is in lsmod but not in ksyms, probably no symbols exported Warning (compare_ksyms_lsmod): module nfs is in lsmod but not in ksyms, probably no symbols exported Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c022c1d0, System.map says c01597b0. Ignoring ksyms_base entry init S C476DF0C 0 1 0 19883 (NOTLB) Using defaults from ksymoops -t elf32-i386 -a i386 Call Trace: [] [] [] [] [] keventd S 00000000 0 2 1 (L-TLB) 3 Call Trace: [] [] kswapd S C4769FA0 0 3 1 (L-TLB) 4 2 Call Trace: [] [] [] [] [] [] kreclaimd S 00000286 0 4 1 (L-TLB) 5 3 Call Trace: [] [] [] [] [] bdflush S C477C000 0 5 1 (L-TLB) 6 4 Call Trace: [] [] [] [] kupdated D C477A000 0 6 1 (L-TLB) 7 5 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] pagebuf_daemon S 00000286 0 7 1 (L-TLB) 8 6 Call Trace: [] [] [] [] mdrecoveryd S F717C000 0 8 1 (L-TLB) 594 7 Call Trace: [] [] [] syslogd S 7FFFFFFF 0 594 1 (NOTLB) 599 8 Call Trace: [] [] [] [] [] klogd R F5E48000 4160 599 1 (NOTLB) 613 594 Call Trace: [] [] [] [] [] [] portmap S 7FFFFFFF 0 613 1 (NOTLB) 628 599 Call Trace: [] [] [] [] [] [] [] rpc.statd S 7FFFFFFF 0 628 1 (NOTLB) 717 613 Call Trace: [] [] [] [] [] [] ypbind S 7FFFFFFF 0 717 1 719 (NOTLB) 776 628 Call Trace: [] [] [] [] [] [] [] ypbind S F5F8BF10 4768 719 717 721 (NOTLB) Call Trace: [] [] [] [] [] [] [] [] ypbind S 00000000 4160 720 719 (NOTLB) 721 Call Trace: [] [] [] ypbind S F66B9F78 1392 721 719 (NOTLB) 720 Call Trace: [] [] [] [] [] [] [] automount S F64C2000 16 776 1 (NOTLB) 786 717 Call Trace: [] [] [] [] automount S F5CF2000 4160 786 1 (NOTLB) 796 776 Call Trace: [] [] [] [] automount S F5D56000 0 796 1 (NOTLB) 806 786 Call Trace: [] [] [] [] automount S F6712000 4488 806 1 (NOTLB) 816 796 Call Trace: [] [] [] [] automount S F5E2C000 4160 816 1 (NOTLB) 826 806 Call Trace: [] [] [] [] automount S F65B4000 0 826 1 (NOTLB) 836 816 Call Trace: [] [] [] [] automount S F66AC000 4 836 1 (NOTLB) 846 826 Call Trace: [] [] [] [] automount S F5D42000 4160 846 1 (NOTLB) 856 836 Call Trace: [] [] [] [] automount S C44F2000 0 856 1 (NOTLB) 866 846 Call Trace: [] [] [] [] automount S C44FE000 0 866 1 (NOTLB) 876 856 Call Trace: [] [] [] [] automount S C4504000 0 876 1 (NOTLB) 886 866 Call Trace: [] [] [] [] automount S C4608000 0 886 1 (NOTLB) 893 876 Call Trace: [] [] [] [] automount S F6454000 0 893 1 (NOTLB) 905 886 Call Trace: [] [] [] [] atd S F6689F78 0 905 1 (NOTLB) 1000 893 Call Trace: [] [] [] [] sshd S 7FFFFFFF 0 1000 1 (NOTLB) 1080 905 Call Trace: [] [] [] [] [] xinetd S 7FFFFFFF 0 1080 1 19899 (NOTLB) 1113 1000 Call Trace: [] [] [] [] [] [] sendmail S F5B1BF0C 2416 1113 1 (NOTLB) 1126 1080 Call Trace: [] [] [] [] [] [] crond S F5AFDF78 0 1126 1 19880 (NOTLB) 1165 1113 Call Trace: [] [] [] [] mingetty S 7FFFFFFF 0 1165 1 (NOTLB) 1166 1126 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1166 1 (NOTLB) 1167 1165 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1167 1 (NOTLB) 1168 1166 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1168 1 (NOTLB) 1169 1167 Call Trace: [] [] [] [] [] mingetty S 7FFFFFFF 0 1169 1 (NOTLB) 5626 1168 Call Trace: [] [] [] [] [] in.rlogind S 7FFFFFFF 0 1328 1080 1355 (NOTLB) 19750 Call Trace: [] [] [] [] [] [] login S 00000000 2416 1355 1328 1356 (NOTLB) Call Trace: [] [] [] tcsh S 00000000 0 1356 1355 5567 (NOTLB) Call Trace: [] [] [] su S 00000000 0 5567 1356 5568 (NOTLB) Call Trace: [] [] bash S 00000000 0 5568 5567 19749 (NOTLB) Call Trace: [] [] [] [] pmd S 7FFFFFFF 3608 5626 1 23861 (NOTLB) 5978 1169 Call Trace: [] [] [] [] [] [] getpgid2_01 S F4F8C000 0 5978 1 (NOTLB) 23496 5626 Call Trace: [] [] getpgid2_01 S F300C000 2416 23496 1 (NOTLB) 19776 5978 Call Trace: [] [] pmd S F43D8000 0 23861 5626 19698 (NOTLB) Call Trace: [] [] [] [] [] renamer01 S 00000000 0 19588 23861 19622 (NOTLB) 19659 Call Trace: [] [] [] renamer D F645C0E0 0 19622 19588 (NOTLB) Call Trace: [] [] [] [] [] [] [] rwtest S 00000000 0 19659 23861 19699 (NOTLB) 19698 19588 Call Trace: wait_on_irq, CPU 0: irq: 1 [ 0 1 0 0 ] bh: 1 [ 1 0 0 0 ] Stack dumps: CPU 1:6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] CPU 2:6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] CPU 3:6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db 6db6db6d db6db6db Call Trace: CPU 0:c02e3ecc c028d37d 00000000 00000000 00000000 c010832d c028d392 f7159ec0 00000004 00000090 00000001 c01fb677 c03691c0 00000000 c01fb640 00000286 c011e81c 00000000 00000001 00001020 c03691c0 c0388a80 00000000 c011eda9 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] symlink02 D E4744000 0 19698 23861 (NOTLB) 19659 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] rm D E42FA000 0 19699 19659 (NOTLB) Call Trace: [] [] [] [] [] [] [] [] [] [] top S F4A23F0C 0 19749 5568 (NOTLB) Call Trace: [] [] [] [] [] [] [] in.rlogind S 7FFFFFFF 0 19750 1080 19777 (NOTLB) 19899 1328 Call Trace: [] [] [] [] [] rpciod S E5922000 0 19775 1 (L-TLB) 19832 19776 Call Trace: [] [] [] [] [] [] [] [] [] [] lockd S 7FFFFFFF 0 19776 1 (L-TLB) 19775 23496 Call Trace: [] [] [] [] [] login S 00000000 4540 19777 19750 19778 (NOTLB) Call Trace: [] [] [] [] tcsh S 00000000 0 19778 19777 19802 (NOTLB) Call Trace: [] [] [] su S 00000000 1392 19802 19778 19803 (NOTLB) Call Trace: [] [] bash S 7FFFFFFF 0 19803 19802 19831 (NOTLB) Call Trace: [] [] [] [] [] strace T 00000014 4768 19831 19803 19700 (NOTLB) Call Trace: [] [] [] pmd D E2E6C000 0 19700 19831 (NOTLB) Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] mingetty S 7FFFFFFF 0 19832 1 (NOTLB) 19883 19775 Call Trace: [] [] [] [] [] [] crond S E3C84000 0 19880 1126 19881 (NOTLB) Call Trace: [] [] [] [] [] run-parts S 00000000 0 19881 19880 19884 (NOTLB) Call Trace: [] [] sa1 S 00000000 0 19883 1 19886 (NOTLB) 19832 Call Trace: [] [] awk S E4F86000 0 19884 19881 (NOTLB) Call Trace: [] [] [] [] [] sadc S E5C92000 0 19886 19883 (NOTLB) Call Trace: [] [] [] in.rlogind S 7FFFFFFF 0 19899 1080 19902 (NOTLB) 19750 Call Trace: [] [] [] [] [] login S 00000000 0 19902 19899 19903 (NOTLB) Call Trace: [] [] [] tcsh S 7FFFFFFF 0 19903 19902 (NOTLB) Call Trace: [] [] [] [] [] [] Warning (Oops_read): Code line not seen, dumping what data is available Proc; init >>EIP; c476df0c <_end+43aecbc/38440e10> <===== Trace; c0114691 Trace; c01145b4 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Proc; keventd >>EIP; 00000000 Before first symbol Trace; c0122fc8 Trace; c0105643 Proc; kswapd >>EIP; c4769fa0 <_end+43aad50/38440e10> <===== Trace; c0114691 Trace; c01145b4 Trace; c0114f82 Trace; c029476e Trace; c012fbc9 Trace; c0105643 Proc; kreclaimd >>EIP; 00000286 Before first symbol <===== Trace; c0114f0d Trace; c0294778 Trace; c012fcbb Trace; c010563a Trace; c0105643 Proc; bdflush >>EIP; c477c000 <_end+43bcdb0/38440e10> <===== Trace; c029550e Trace; c012f813 Trace; c013b17e Trace; c0105643 Proc; kupdated >>EIP; c477a000 <_end+43badb0/38440e10> <===== Trace; c01d877e Trace; c01d885d Trace; c01d3e13 Trace; c01ad831 Trace; c01ad873 Trace; c01d3e13 Trace; c01d3e13 Trace; c01d27dd Trace; c016a910 Trace; c01d2760 Trace; c01c6037 Trace; c0169674 Trace; c01d2760 Trace; c01d293c Trace; c01d294f Trace; c01d2760 Trace; c01d293c Trace; c0127550 Trace; c01d293c Trace; c014b937 Trace; c013af87 Trace; c013b28d Trace; c0105643 Proc; pagebuf_daemon >>EIP; 00000286 Before first symbol <===== Trace; c0114f0d Trace; c01685cc Trace; c01684d0 Trace; c0105643 Proc; mdrecoveryd >>EIP; f717c000 <_end+36dbcdb0/38440e10> <===== Trace; c02afdf1 Trace; c0230682 Trace; c0105643 Proc; syslogd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Proc; klogd >>EIP; f5e48000 <_end+35a88db0/38440e10> <===== Trace; c0231ffd Trace; c0116ffc Trace; c01575e5 Trace; c0136a1a Trace; c0106e23 Trace; c010002b Proc; portmap >>EIP; 7fffffff Before first symbol <===== Trace; c024ebff Trace; c0232437 Trace; c0114627 Trace; c01473d3 Trace; c014735f Trace; c0147663 Trace; c0106e23 Proc; rpc.statd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 Trace; c0147102 Trace; c0136607 Trace; c0106e23 Proc; ypbind >>EIP; 7fffffff Before first symbol <===== Trace; c024ebff Trace; c0232437 Trace; c0114627 Trace; c01473d3 Trace; c014735f Trace; c0147663 Trace; c0106e23 Proc; ypbind >>EIP; f5f8bf10 <_end+35bcccc0/38440e10> <===== Trace; c0114691 Trace; c01145b4 Trace; c014735f Trace; c0147663 Trace; c01086c9 Trace; c01086e9 Trace; c0106e23 Trace; c010002b Proc; ypbind >>EIP; 00000000 Before first symbol Trace; c0105fdb Trace; c0106e23 Trace; c010002b Proc; ypbind >>EIP; f66b9f78 <_end+362fad28/38440e10> <===== Trace; c0130870 Trace; c0146916 Trace; c0114691 Trace; c01145b4 Trace; c011f1ab Trace; c0106e23 Trace; c010002b Proc; automount >>EIP; f64c2000 <_end+36102db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f5cf2000 <_end+35932db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f5d56000 <_end+35996db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f6712000 <_end+36352db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f5e2c000 <_end+35a6cdb0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f65b4000 <_end+361f4db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f66ac000 <_end+362ecdb0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f5d42000 <_end+35982db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; c44f2000 <_end+4132db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; c44fe000 <_end+413edb0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; c4504000 <_end+4144db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; c4608000 <_end+4248db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; automount >>EIP; f6454000 <_end+36094db0/38440e10> <===== Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; atd >>EIP; f6689f78 <_end+362cad28/38440e10> <===== Trace; c0114691 Trace; c01145b4 Trace; c011f1ab Trace; c0106e23 Proc; sshd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Proc; xinetd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 Trace; c0147102 Trace; c0136607 Trace; c0106e23 Proc; sendmail >>EIP; f5b1bf0c <_end+3575ccbc/38440e10> <===== Trace; c01469ae <__pollwait+8e/94> Trace; c0114691 Trace; c01145b4 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Proc; crond >>EIP; f5afdf78 <_end+3573ed28/38440e10> <===== Trace; c0114691 Trace; c01145b4 Trace; c011f1ab Trace; c0106e23 Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; in.rlogind >>EIP; 7fffffff Before first symbol <===== Trace; c01ef51c Trace; c0114627 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Trace; c010002b Proc; login >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c011a596 Trace; c0106e23 Proc; tcsh >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c0105fdb Trace; c0106e23 Proc; su >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 Proc; bash >>EIP; 00000000 Before first symbol Trace; c01ea876 Trace; c01eac4d Trace; c011a596 Trace; c0106e23 Proc; pmd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0232437 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Trace; c010002b Proc; getpgid2_01 >>EIP; f4f8c000 <_end+34bccdb0/38440e10> <===== Trace; c010ca92 Trace; c0106e23 Proc; getpgid2_01 >>EIP; f300c000 <_end+32c4cdb0/38440e10> <===== Trace; c010ca92 Trace; c0106e23 Proc; pmd >>EIP; f43d8000 <_end+34018db0/38440e10> <===== Trace; c01145a7 Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; renamer01 >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c0105fdb Trace; c0106e23 Proc; renamer >>EIP; f645c0e0 <_end+3609ce90/38440e10> <===== Trace; c01d2555 Trace; c0141935 Trace; c0105b6b <__down+73/d0> Trace; c0105d18 <__down_failed+8/c> Trace; c028799c Trace; c0106e23 Trace; c010002b Proc; rwtest >>EIP; 00000000 Before first symbol Trace; c0166599 Trace; c0166599 Trace; c0166599 Trace; c0166599 Trace; c0166806 Trace; c0166806 Trace; c01675d7 Trace; c019386b Trace; c01145a7 Trace; c01b5ff4 Trace; c01b609d Trace; f880758a <[scsi_mod]scsi_queue_next_request+52/124> Trace; f88077c0 <[scsi_mod]__scsi_end_request+164/170> Trace; f8807a9a <[scsi_mod]scsi_io_completion+1da/3bc> Trace; f8817d86 <[sd_mod]rw_intr+1f6/204> Trace; f880671d <[scsi_mod]scsi_old_done+3d/600> Trace; f8806cc6 <[scsi_mod]scsi_old_done+5e6/600> Trace; c011eb87 Trace; c011eee0 Trace; c011ef63 Trace; c010c160 Trace; c01084d6 Trace; c01086c9 Trace; c01086e9 Trace; c0106ee4 Trace; c0114b12 Trace; c0114691 Trace; c01145b4 Trace; c0114f82 Trace; c029476e Trace; c012fbc9 Trace; c0105643 Trace; c01001c8 Trace; c01effa0 Trace; c01f04e2 Trace; c0166599 Trace; c0166599 Trace; f9c04e6a Trace; c0166599 Trace; c0166599 Trace; f894b5b0 <[usbcore]proc_releaseinterface+30/40> Trace; f8945a36 <[usbcore]usb_find_interface_driver+3a/190> Trace; c02405e4 Trace; c0238d06 Trace; c0234312 Trace; c0262e2e Trace; c0263099 Trace; c02602cb Trace; f894b5b0 <[usbcore]proc_releaseinterface+30/40> Trace; f8945a36 <[usbcore]usb_find_interface_driver+3a/190> Trace; c02405e4 Trace; c0238d06 Trace; c024cca3 Trace; c023ef54 Trace; c024b722 Trace; c024cc00 Trace; c024b5cc Trace; c024bb0d Trace; c023ef54 Trace; c024b5cc Trace; c025f81d Trace; c025a59f Trace; c025a662 Trace; c025b18b Trace; c0258648 <__tcp_data_snd_check+50/c4> Trace; c01fff66 Trace; c0200000 Trace; c011731b <__call_console_drivers+3b/4c> Trace; c011737f <_call_console_drivers+53/58> Trace; c011745b Trace; c0117696 Trace; c011761e Trace; c01070bf Trace; c028cde0 Trace; c0107170 Trace; c0115783 Trace; c0115852 Trace; c0201b6d Trace; c0201d1c <__handle_sysrq_nolock+60/e4> Trace; c02a3b80 Trace; c02a3af6 Trace; c0201cb3 Trace; c02002fc Trace; c011eb87 Trace; c0201286 Trace; c0201314 Trace; c01084d6 Trace; c01086c9 Trace; c0105280 Trace; c0105280 Trace; c0106ee4 Trace; c0105280 Trace; c0105280 Trace; c0100018 Trace; c01052ad Trace; c0105312 Trace; c011737f <_call_console_drivers+53/58> Trace; c028d37d Trace; c010832d <__global_cli+8d/12c> Trace; c028d392 Trace; c01fb677 Trace; c01fb640 Trace; c011e81c <__run_timers+cc/110> Trace; c011eda9 Trace; c011b552 Trace; c011b435 Trace; c011b2da Trace; c010870a Trace; c0105280 Trace; c0105280 Trace; c0106ee4 Trace; c0105280 Trace; c0105280 Trace; c0100018 Trace; c01052ad Trace; c0105312 Trace; c0105000 Trace; c01001cf Trace; c0114b12 Trace; c0105fdb Trace; c0106e23 Proc; symlink02 >>EIP; e4744000 <_end+24384db0/38440e10> <===== Trace; c01305b2 <__alloc_pages+6a/294> Trace; c01c2792 Trace; c01d877e Trace; c01d881c Trace; c01c74f2 Trace; c01ad856 Trace; c01ad873 Trace; c01c74f2 Trace; c01c74f2 Trace; c01d2555 Trace; c0141935 Trace; c0142459 Trace; c01428d8 <__user_walk+3c/58> Trace; c01360ba Trace; c0106e23 Proc; rm >>EIP; e42fa000 <_end+23f3adb0/38440e10> <===== Trace; c01c312c Trace; c014b6da <__wait_on_inode+7a/98> Trace; c014c7bc Trace; c01d7c22 Trace; c01ca027 Trace; c01ad99b Trace; c01d1e67 Trace; c0143c2f Trace; c0143d32 Trace; c0106e23 Proc; top >>EIP; f4a23f0c <_end+34664cbc/38440e10> <===== Trace; c01469ae <__pollwait+8e/94> Trace; c0114691 Trace; c01145b4 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Trace; c010002b Proc; in.rlogind >>EIP; 7fffffff Before first symbol <===== Trace; c01ef51c Trace; c0114627 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Proc; rpciod >>EIP; e5922000 <_end+25562db0/38440e10> <===== Trace; f89c4912 <[sunrpc]proc_dodebug+1c4a2/25bf0> Trace; f89bd2f0 <[sunrpc]proc_dodebug+14e80/25bf0> Trace; f89bde2b <[sunrpc]proc_dodebug+159bb/25bf0> Trace; f89bdc4c <[sunrpc]proc_dodebug+157dc/25bf0> Trace; f89c6d84 <[sunrpc]proc_dodebug+1e914/25bf0> Trace; f89c6d7c <[sunrpc]proc_dodebug+1e90c/25bf0> Trace; f89c6d7c <[sunrpc]proc_dodebug+1e90c/25bf0> Trace; c0105643 Trace; f89c6d84 <[sunrpc]proc_dodebug+1e914/25bf0> Trace; f89c6d84 <[sunrpc]proc_dodebug+1e914/25bf0> Proc; lockd >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c0136607 Trace; f89c0cbe <[sunrpc]proc_dodebug+1884e/25bf0> Trace; f898bc44 <[usb-uhci]uhci_pci_driver+33da4/40dc0> Trace; c0105643 Proc; login >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c011a596 Trace; c0106e23 Trace; c010002b Proc; tcsh >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c0105fdb Trace; c0106e23 Proc; su >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 Proc; bash >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; strace >>EIP; 00000014 Before first symbol <===== Trace; c0106c37 Trace; c011a5c1 Trace; c0106e74 Proc; pmd >>EIP; e2e6c000 <_end+22aacdb0/38440e10> <===== Trace; c029abdc Trace; c029abdc Trace; c01d877e Trace; c01d881c Trace; c01c74f2 Trace; c01ad856 Trace; c01ad873 Trace; c01c74f2 Trace; c01c74f2 Trace; c01d2555 Trace; c0141935 Trace; c0142459 Trace; c013fbf1 Trace; c013fbff Trace; c01406c6 Trace; c01305b2 <__alloc_pages+6a/294> Trace; c0124cf8 Trace; c0124d0b Trace; c01254db Trace; c0113c9f Trace; c0113b00 Trace; c01207c4 Trace; c01417cb Trace; c0105a43 Trace; c0106e23 Proc; mingetty >>EIP; 7fffffff Before first symbol <===== Trace; c0114627 Trace; c01f5dae Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 Proc; crond >>EIP; e3c84000 <_end+238c4db0/38440e10> <===== Trace; c012634a Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; run-parts >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 Proc; sa1 >>EIP; 00000000 Before first symbol Trace; c011a596 Trace; c0106e23 Proc; awk >>EIP; e4f86000 <_end+24bc6db0/38440e10> <===== Trace; c014a2f1 Trace; c0140add Trace; c0140bb9 Trace; c0136a1a Trace; c0106e23 Proc; sadc >>EIP; e5c92000 <_end+258d2db0/38440e10> <===== Trace; c0137f62 Trace; c010ca92 Trace; c0106e23 Proc; in.rlogind >>EIP; 7fffffff Before first symbol <===== Trace; c01ef51c Trace; c0114627 Trace; c0146b28 Trace; c0147102 Trace; c0106e23 Proc; login >>EIP; 00000000 Before first symbol Trace; c0114b12 Trace; c011a596 Trace; c0106e23 Proc; tcsh >>EIP; 7fffffff Before first symbol <===== Trace; c01254db Trace; c0114627 Trace; c01ed24d Trace; c01e917c Trace; c0136a1a Trace; c0106e23 4 warnings and 1 error issued. Results may not be reliable. -- 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 Mon Jul 9 07:17:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69EHHE29509 for linux-xfs-outgoing; Mon, 9 Jul 2001 07:17:17 -0700 Received: from server.hotswap (atbode95.informatik.tu-muenchen.de [131.159.32.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69EHGV29506 for ; Mon, 9 Jul 2001 07:17:16 -0700 Received: from cs.tum.edu (kuschel.hotswap [172.16.16.190]) by server.hotswap (swapfix) with ESMTP id 8286039654CD; Mon, 9 Jul 2001 16:17:10 +0200 (CEST) Message-ID: <3B49BCE6.4C408041@cs.tum.edu> Date: Mon, 09 Jul 2001 16:17:10 +0200 From: Deti Fliegl X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre2-xfs i686) X-Accept-Language: en, de MIME-Version: 1.0 To: Seth Mos , "linux-xfs@oss.sgi.com" Subject: Re: XFS Crash with 2.4.6-pre9 (reproduceable) References: <4.3.2.7.2.20010709104934.029ef710@pop.xs4all.nl> <4.3.2.7.2.20010709124124.033b58a0@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Seth > Ah, so it could be that there is a corruption issue or otherwise damaged fs > that panics tha machine. > If you decide to repair it try with -n first to see what it wants to change. Ok - now the filesystem is repaired and the kernel built from the current CVS is running. Up to now no further problems occured and the system was running with XFS for about 8 month without any problem. > What chipset information and IDE details can you provide. 00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10) (prog-if 8a [Master SecP PriP]) The harddisk is a Maxtor 94098U8, ATA DISK drive, 80041248 sectors (40981 MB) w/2048KiB Cache, CHS=4982/255/63, UDMA(66) Maybe a XFS corruption happened by some Via chipset oddities - since 2.4.6 the pci latency hack should have been included into the kernel... so the corruption must have happened before :( Deti From owner-linux-xfs@oss.sgi.com Mon Jul 9 07:42:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69Eg5o31930 for linux-xfs-outgoing; Mon, 9 Jul 2001 07:42:05 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69Eg4V31927 for ; Mon, 9 Jul 2001 07:42:04 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA04069 for ; Mon, 9 Jul 2001 07:39:27 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2381413 for ; Mon, 9 Jul 2001 09:40:48 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA50386 for ; Mon, 9 Jul 2001 09:40:48 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f69EgBs32411; Mon, 9 Jul 2001 09:42:11 -0500 Message-Id: <200107091442.f69EgBs32411@jen.americas.sgi.com> Date: Mon, 9 Jul 2001 09:42:11 -0500 Subject: TAKE - add more error checking in O_SYNC write path Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Fix from Andi Kleen Date: Mon Jul 9 07:40:09 PDT 2001 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:98460a linux/fs/xfs/linux/xfs_lrw.c - 1.102 - Fix error handling for O_SYNC writes From owner-linux-xfs@oss.sgi.com Mon Jul 9 08:05:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69F5kK01348 for linux-xfs-outgoing; Mon, 9 Jul 2001 08:05:46 -0700 Received: from e31.bld.us.ibm.com (e31.co.us.ibm.com [32.97.110.129]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69F5iV01344 for ; Mon, 9 Jul 2001 08:05:45 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.99.140.23]) by e31.bld.us.ibm.com (8.9.3/8.9.3) with ESMTP id KAA16728 for ; Mon, 9 Jul 2001 10:57:44 -0400 Received: from f4n64e (d03nm080h.boulder.ibm.com [9.99.140.64]) by westrelay02.boulder.ibm.com (8.11.1m3/NCO v4.96.1.0) with ESMTP id f69F5df59198 for ; Mon, 9 Jul 2001 09:05:39 -0600 From: "James A Goodwin" Subject: DMAPI and dump/restore To: "linux-xfs@oss.sgi.com" X-Mailer: Lotus Notes Release 5.0.7 March 21, 2001 Message-ID: Date: Mon, 9 Jul 2001 10:05:37 -0500 X-MIMETrack: Serialize by Router on D03NM080/03/M/IBM(Release 5.0.6 |December 14, 2000) at 07/09/2001 09:05:38 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Does anyone know the extent to which DMAPI information is handled by xfsdump/xfsrestore? There are two things that worry me: 1. Are xfsdump/xfsrestore smart enough to realize when data is not resident on XFS disks? In other words, the data has been migrated by the DMAPI client, and dm_puch_hole() was used to free up the XFS disk resources. When doing a dump, I'd rather have xfsdump note that there is a hole rather than dredging all the migrated data back up through the DMAPI. 2. What do xfsdump/xfsrestore do with DM attributes, regions, and event lists? Are they stored, ignored, or something else? I've been able to find only a few clues here and there, though the FAQ wasn't very helpful. The xfsdump man page mentions a "-a" option for working with DMF that sounds a lot like an answer to #1, but I'd be surprised if there was any relationship between DMF and DMAPI. I would really appreciate any info regarding these questions. Thanks, -James Goodwin Software Engineer IBM Global Services - Federal jagoodwi@us.ibm.com Phone: (281) 336 2578 Fax: (281) 335 4231 T/L 260-2578 From owner-linux-xfs@oss.sgi.com Mon Jul 9 09:27:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69GR4m05869 for linux-xfs-outgoing; Mon, 9 Jul 2001 09:27:04 -0700 Received: from c0mailgw06.prontomail.com (mailgw.prontomail.com [216.163.180.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69GR2V05865 for ; Mon, 9 Jul 2001 09:27:02 -0700 Received: from c5web109 (216.163.180.10) by c0mailgw06.prontomail.com (NPlex 5.5.029) id 3B494F760001095E for linux-xfs@oss.sgi.com; Mon, 9 Jul 2001 09:22:01 -0700 X-Version: ireland 6.2.3.2329.0 From: "Juer Lee" Message-Id: Date: Mon, 9 Jul 2001 17:27:44 +0100 X-Priority: Normal Content-Type: text/plain; charset=iso-8859-1 To: linux-xfs@oss.sgi.com Subject: XFS ACL problem on PPC X-Mailer: Web Based Pronto Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, All, Does anybody know whether the XFS really supports ACL on PPC :) maybe it is a foolish question -- since SGI announce that they support PPC and ACL -- but they don't tell us about that when using them at the same time. I downloaded all the patch for XFS, and compiled successfully almost without any problems. The ACL utility is version 1.0.4, I downloaded the source code of it, compiled it successfully again. But after I read the source code of .../libacl/acl.c, I found that seemed not supporting PPC. So I have to try to find some version of ACL utility for PPC, this time I went to http://people.spoiled.org/tgr/unix/xfs/ppc/2.4.2/rpms, I downloaded acl-1.0.1-0.ppc.rpm and acl-devel-1.0.1-0.ppc.rpm, installed them on my PPC using LinuxPPC2000. I run 'chacl' again, I got the error message "libacl: acl_set system call not defined for this architecture" again, my god, I can not bear it now. I think it should be my PowerPC's problem... Who can help me? Thank you in advance. Juer _____________________________________ Get your free E-mail at http://www.ireland.com From owner-linux-xfs@oss.sgi.com Mon Jul 9 09:35:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69GZZ306088 for linux-xfs-outgoing; Mon, 9 Jul 2001 09:35:35 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69GZXV06085 for ; Mon, 9 Jul 2001 09:35:33 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA03258 for ; Mon, 9 Jul 2001 09:35:36 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2384150; Mon, 9 Jul 2001 11:34:14 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA89404; Mon, 9 Jul 2001 11:34:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f69GZaS01889; Mon, 9 Jul 2001 11:35:36 -0500 Message-Id: <200107091635.f69GZaS01889@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Juer Lee" cc: linux-xfs@oss.sgi.com Subject: Re: XFS ACL problem on PPC In-Reply-To: Message from "Juer Lee" of "Mon, 09 Jul 2001 17:27:44 BST." Date: Mon, 09 Jul 2001 11:35:36 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, All, > > Does anybody know whether the XFS really supports ACL on PPC :) maybe > it is a foolish question -- since SGI announce that they support PPC > and ACL -- but they don't tell us about that when using them at the > same time. SGI has never said anything about support and PPC to my knowledge, people have run XFS on the PPC architecture. Having said that, I am pretty sure that the system call numbers for extended attribute and acl support are only in the kernels for ia32 and ia64. For other platforms you would need to add the system calls to the kernel, and make sure that the user space commands use the correct system call numbers for your architecture. Steve > I downloaded all the patch for XFS, and compiled successfully almost > without any problems. > The ACL utility is version 1.0.4, I downloaded the source code of it, > compiled it successfully again. But after I read the source code > of .../libacl/acl.c, I found that seemed not supporting PPC. > So I have to try to find some version of ACL utility for PPC, this > time I went to http://people.spoiled.org/tgr/unix/xfs/ppc/2.4.2/rpms, > I downloaded acl-1.0.1-0.ppc.rpm and acl-devel-1.0.1-0.ppc.rpm, > installed them on my PPC using LinuxPPC2000. I run 'chacl' again, I > got the error message "libacl: acl_set system call not defined for > this architecture" again, my god, I can not bear it now. I think it > should be my PowerPC's problem... > Who can help me? > Thank you in advance. > > > Juer > > _____________________________________ > > Get your free E-mail at http://www.ireland.com From owner-linux-xfs@oss.sgi.com Mon Jul 9 12:03:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69J3GH08624 for linux-xfs-outgoing; Mon, 9 Jul 2001 12:03:16 -0700 Received: from pyre.virge.net (qmailr@cr541398-a.cambr1.on.wave.home.com [24.156.0.228]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69J3EV08621 for ; Mon, 9 Jul 2001 12:03:14 -0700 Received: (qmail 10472 invoked by uid 1000); 9 Jul 2001 19:03:13 -0000 From: "Norbert Veber" Date: Mon, 9 Jul 2001 15:03:13 -0400 To: linux-xfs@oss.sgi.com Subject: XFS Issues Message-ID: <20010709150313.A10426@pyre.virge.net> Mail-Followup-To: nveber@pyre.virge.net, linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have been running the 1.0 release for some time, with the 2.4.3 kernel, and all partitions formatted to xfs (except /boot since I'm using grub, not lilo). While upgrading to the 2.4.6 patch, and trying to delete the old source tree, I came across this: root@pyre[/usr/src]# rm -rf linux-2.4.3-XFS/ rm: cannot remove directory inux-2.4.3-XFS/fs/cramfs': Directory not empty rm: cannot remove directory inux-2.4.3-XFS/fs': Directory not empty rm: cannot remove directory inux-2.4.3-XFS': Directory not empty root@pyre[/usr/src]# ls -al linux-2.4.3-XFS/fs/cramfs/ total 0 drwxr-xr-x 3 root root 110 May 24 20:48 . It appers to be empty, yet it cannot be removed. I have since upgraded to 2.4.6-XFS, but I am still unable to delete the files. Another thing I noticed with both kernels is that the output of the "free" command always shows "buffers" as either 4 or 8. ie. pyre[~]# free total used free shared buffers cached Mem: 255580 251312 4268 0 4 214100 -/+ buffers/cache: 37208 218372 Swap: 789216 132180 657036 Is this normal? Does the XFS kernel not use buffers, or, is the output just wrong? Thanks, Norbert From owner-linux-xfs@oss.sgi.com Mon Jul 9 12:22:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69JM2708953 for linux-xfs-outgoing; Mon, 9 Jul 2001 12:22:02 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69JM1V08950 for ; Mon, 9 Jul 2001 12:22:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA15313 for ; Mon, 9 Jul 2001 12:21:52 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2383684; Mon, 9 Jul 2001 14:20:43 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA52124; Mon, 9 Jul 2001 14:20:43 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f69JM5O03020; Mon, 9 Jul 2001 14:22:05 -0500 Message-Id: <200107091922.f69JM5O03020@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Norbert Veber" cc: linux-xfs@oss.sgi.com Subject: Re: XFS Issues In-Reply-To: Message from "Norbert Veber" of "Mon, 09 Jul 2001 15:03:13 EDT." <20010709150313.A10426@pyre.virge.net> Date: Mon, 09 Jul 2001 14:22:05 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > > I have been running the 1.0 release for some time, with the 2.4.3 kernel, > and all partitions formatted to xfs (except /boot since I'm using grub, not > lilo). > > While upgrading to the 2.4.6 patch, and trying to delete the old source > tree, I came across this: > root@pyre[/usr/src]# rm -rf linux-2.4.3-XFS/ > rm: cannot remove directory inux-2.4.3-XFS/fs/cramfs': Directory not empty > rm: cannot remove directory inux-2.4.3-XFS/fs': Directory not empty > rm: cannot remove directory inux-2.4.3-XFS': Directory not empty > root@pyre[/usr/src]# ls -al linux-2.4.3-XFS/fs/cramfs/ > total 0 > drwxr-xr-x 3 root root 110 May 24 20:48 . > > It appers to be empty, yet it cannot be removed. Unmount the filesystem and run xfs_repair -n on the device, then send me the output. You should really be seeing a .. link for that ls output. I have been chasing something which might be related for a few days now. > > I have since upgraded to 2.4.6-XFS, but I am still unable to delete the > files. > > Another thing I noticed with both kernels is that the output of the "free" > command always shows "buffers" as either 4 or 8. > ie. > pyre[~]# free > total used free shared buffers cached > Mem: 255580 251312 4268 0 4 214100 > -/+ buffers/cache: 37208 218372 > Swap: 789216 132180 657036 > > Is this normal? Does the XFS kernel not use buffers, or, is the output just > wrong? This buffer count does not reflect buffers used for file data, just the block device cache - which xfs does not use. If you run a mkfs or xfs_repair type operation on the block device you will see the numbers go up. You are seeing normal values here, my box currently looks like this: total used free shared buffers cached Mem: 254140 250852 3288 0 0 172736 -/+ buffers/cache: 78116 176024 Swap: 265064 50360 214704 Steve > > Thanks, > > Norbert From owner-linux-xfs@oss.sgi.com Mon Jul 9 13:55:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69KtML17800 for linux-xfs-outgoing; Mon, 9 Jul 2001 13:55:22 -0700 Received: from citadel.oehansen.pp.se (sdu6-200.ppp.algonet.se [195.163.200.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69KtKV17794 for ; Mon, 9 Jul 2001 13:55:20 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f69Kv0R03583 for ; Mon, 9 Jul 2001 22:57:00 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: linux-xfs@oss.sgi.com Subject: Shadows, or two... Date: Mon, 9 Jul 2001 22:57:00 +0200 X-Mailer: KMail [version 1.2] X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Here are two issues, I've noticed on use of XFS 1.0.1-PR3, kernel 2.4.5 (vanilla + XFS patch). 1. Nightly cron-job, results in libGLcore file, to be unusable for some reason. Reboot fixes the problem... no re-occurance have occured, but I'm on a watchout for it. 2. A program makes a backup copy of a file, then somewhere in the process it dies unexpectedly (Program in question cups, file in question printers.conf.0 file. Later, viewing the file by 'vdir printers.conf.0' shows the file, and everything appears ok. But, 'rm printers.conf.0', says the file is non consistant, same applies to 'mv' (unlink). An hour or two later, I remove the file with 'rm' and it works ok. Orn From owner-linux-xfs@oss.sgi.com Mon Jul 9 14:11:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69LBYt20087 for linux-xfs-outgoing; Mon, 9 Jul 2001 14:11:34 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69LBXV20080 for ; Mon, 9 Jul 2001 14:11:33 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id OAA05638 for ; Mon, 9 Jul 2001 14:08:57 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2379877; Mon, 9 Jul 2001 16:10:11 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA75972; Mon, 9 Jul 2001 16:10:11 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f69LBW805096; Mon, 9 Jul 2001 16:11:32 -0500 Message-Id: <200107092111.f69LBW805096@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: oe.hansen@gamma.telenordia.se cc: linux-xfs@oss.sgi.com Subject: Re: Shadows, or two... In-Reply-To: Message from "Orn E. Hansen" of "Mon, 09 Jul 2001 22:57:00 +0200." <01070922570000.03403@citadel.oehansen.pp.se> Date: Mon, 09 Jul 2001 16:11:32 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Here are two issues, I've noticed on use of XFS 1.0.1-PR3, kernel 2.4.5 > (vanilla + XFS patch). > > 1. Nightly cron-job, results in libGLcore file, to be unusable for some > reason. Reboot fixes the problem... no re-occurance have occured, but I'm on > > a watchout for it. What do you have in the cron jobs - are you running xfs_fsr? I suppose it could have defragmented the file from underneath an mmap.... > > 2. A program makes a backup copy of a file, then somewhere in the process > it dies unexpectedly (Program in question cups, file in question > printers.conf.0 file. Later, viewing the file by 'vdir printers.conf.0' > shows the file, and everything appears ok. But, 'rm printers.conf.0', says > the file is non consistant, same applies to 'mv' (unlink). An hour or two > later, I remove the file with 'rm' and it works ok. Can you expand on the 'file is non consistant' message, is this printed by the rm command? Steve > > > > Orn From owner-linux-xfs@oss.sgi.com Mon Jul 9 15:09:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69M9Ln29824 for linux-xfs-outgoing; Mon, 9 Jul 2001 15:09:21 -0700 Received: from citadel.oehansen.pp.se (sdu98-205.ppp.algonet.se [195.163.205.98]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69M99V29784 for ; Mon, 9 Jul 2001 15:09:11 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f69MAMw03896; Tue, 10 Jul 2001 00:10:28 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: Steve Lord Subject: Re: Shadows, or two... Date: Tue, 10 Jul 2001 00:10:22 +0200 X-Mailer: KMail [version 1.2] Cc: linux-xfs@oss.sgi.com References: <200107092111.f69LBW805096@jen.americas.sgi.com> In-Reply-To: <200107092111.f69LBW805096@jen.americas.sgi.com> X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 X-MIME-Autoconverted: from 8bit to quoted-printable by citadel.oehansen.pp.se id f69MAMw03896 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f69M9JV29815 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk mánudagur 9. júlí 2001 23:11, Steve Lord skrifaði: > > What do you have in the cron jobs - are you running xfs_fsr? I suppose it > could have defragmented the file from underneath an mmap.... > This happened tonite, and there are only the standard RH cron jobs in the crontab. I'm *guessing* it's the weekly cronjob, although this happened at the night before monday, as its never happened as a result of the daily cronjobs. I *think* my system starts on a monday... in which case it would make the culprit the make-of-the-whatis-database. However, I'm not certain... I'm going to check again after the next run of the daily cron job, to see if it reoccurs... as I have a "notion" its one of those things that fixes itself after a time period? > > Can you expand on the 'file is non consistant' message, is this printed by > the rm command? > Now that you write this, I can't say for sure... I read it as 'non existant'. But 'non consistant' and 'non existant' sound alike and english is not my native language. So it, *could* have been... but I *think* it said 'non existant'. > Steve > > > Orn From owner-linux-xfs@oss.sgi.com Mon Jul 9 15:53:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69MrwS04860 for linux-xfs-outgoing; Mon, 9 Jul 2001 15:53:58 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69MruV04856 for ; Mon, 9 Jul 2001 15:53:57 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f69MrjI13511; Mon, 9 Jul 2001 18:53:45 -0400 Date: Mon, 9 Jul 2001 18:53:45 -0400 From: Alan Eldridge To: Arjan van de Ven Cc: SGI XFS Dev List Subject: Re: /boot/kernel.h Message-ID: <20010709185345.A13505@wwweasel.geeksrus.net> References: <20010709174000.D15119@devserv.devel.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010709174000.D15119@devserv.devel.redhat.com>; from arjanv@redhat.com on Mon, Jul 09, 2001 at 05:40:00PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 09, 2001 at 05:40:00PM -0400, Arjan van de Ven wrote: >Hi, > >I saw, while reading the XFS mailinglist, that you had some problems with >/boot/kernel.h. This file is created ON BOOT to represent the currently >running kernel, and also on rpm -i of a kernel rpm. Why your system doesn't >have a /boot/kernel.h is a big questionmark for me, but it has nothing to do >with which package has the file... Yup, /sbin/mkkerneldoth creates it. That was the piece of the puzzle I was having trouble finding. "find /etc/rc.d -type f |xargs grep kernel.h" didn't turn up anything. "find /sbin ...." did. Once I found that, the rest was easy. When you install a new kernel, it is supposed to get run as part of %post. When you erase a kernel RPM, rpm tries to get rid of the old one as part of %postun. Somehow, installing one kernel RPM and then erasing an earlier one led to the file getting zapped to empty. Happened a second time, too, same sequence of operations, but I was watching for it that time. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Mon Jul 9 16:39:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69NdDp12783 for linux-xfs-outgoing; Mon, 9 Jul 2001 16:39:13 -0700 Received: from woody.fsl.noaa.gov (IDENT:root@woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69NdBV12779 for ; Mon, 9 Jul 2001 16:39:11 -0700 Received: (from tierney@localhost) by woody.fsl.noaa.gov (8.9.3/8.9.3) id RAA11178 for linux-xfs@oss.sgi.com; Mon, 9 Jul 2001 17:41:39 -0600 Date: Mon, 9 Jul 2001 17:41:39 -0600 From: Craig Tierney To: linux-xfs@oss.sgi.com Subject: Problem with lvm in 2.4.6 and xfs Message-ID: <20010709174139.B11071@hpti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am trying to create an lvm partition (of one device). I have done this before under x86, but I am trying this on Alpha. I can run mkfs -t xfs, but when I try and mount the filesystem I get the error below. Setup: XP1000, Qlogic FC2220 linux-2.4.6 with Tronds latest NFS patches linux-2.4.6-xfs-07052001.patch Qlogic 4.27Beta driver mount has been upgraded to 2.11.2 (linux-util-2.11.2) LVM is kernel lvm only (0.9.1-6). I also added just the patch from page_buf_io.c to help with sparse files, but I have the same problem without that patch. I did not update the LVM in the 2.4.6 kernel (as that messes up the xfs patch). I am running xfs+lvm successfully under x86 with the FC drive setup. kernel BUG at ll_rw_blk.c:691! mount(974): Kernel Bug 1 pc = [] ra = [] ps = 0000 v0 = 000000000000001f t0 = 0000000000000001 t1 = 0000000000000001 t2 = 0000000000000000 t3 = fffffc0066708000 t4 = fffffc0000624b20 t5 = fffffc0000654558 t6 = 0000000000000001 t7 = fffffc0066708000 a0 = 0000000000000000 a1 = 0000000000000001 a2 = 0000000000000001 a3 = fffffffffffffff9 a4 = 0000000000000002 a5 = 0000000000000000 t8 = 0000000000003fff t9 = fffffc0000659ba8 t10= 0000000000000006 t11= 000000000000000a pv = fffffc0000328820 at = fffffc0000653400 gp = fffffc00006485c0 sp = fffffc006670b5b8 Code: 225f02b3 lda a2,691(zero) a77dae78 ldq pv,-20872(gp) 6b5b77df jsr ra,(pv) 27ba001c ldah gp,28(ra) 23bda75c lda gp,-22692(gp) 00000081 call_pal 129 *c3e0025f br .+2432 2fe00000 ldq_u zero,0(v0) Trace:48e974 340841 3d9c88 3d9f9c 3da510 3d9dc0 3da100 3d93dc 3d8994 451b34 43c7c8 446928 43be28 446824 446d3c 446db4 45b014 35ce50 3737d0 360504 35d1dc 35cdc8 35d23c 35e1c4 35e170 35e668 35e770 35e750 310ae0 Craig -- Craig Tierney (ctierney@hpti.com) phone: 303-497-3112 From owner-linux-xfs@oss.sgi.com Mon Jul 9 16:39:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f69NdTI12860 for linux-xfs-outgoing; Mon, 9 Jul 2001 16:39:29 -0700 Received: from main ([211.219.161.171]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f69NdFV12797; Mon, 9 Jul 2001 16:39:18 -0700 Received: from lonetear.com ([211.219.161.171]) by main (Lotus Domino Release 5.0.5) with SMTP id 2001070922215122:656 ; Mon, 9 Jul 2001 22:21:51 +0900 Message-ID: <00000c970a98$00004ff7$00007232@lonetear.com> To: From: c.calls@lonetear.com Subject: Confirming Your Link 29234 Date: Mon, 09 Jul 2001 06:23:55 -0700 MIME-Version: 1.0 X-Priority: 1 (High) X-MSMail-Priority: High X-MIMETrack: Itemize by SMTP Server on notes/sdj(Release 5.0.5 |September 22, 2000) at 2001-07-09 10:21:53 PM, Serialize by Router on notes/sdj(Release 5.0.5 |September 22, 2000) at 2001-07-10 08:39:32 AM, Serialize complete at 2001-07-10 08:39:32 AM Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Take Control Of Your Conference Calls



Pleas= e complete all the information below=2E
Our loan specialist will be con= tacting you at your convenience=2E
Thank You!

Plea= se use your mouse to navigate between fields=2E Thank You=2E


=
Your Full Name *
Address *
City *
State(US= A Only) * UNITED STATES ONLY!
Zip/Postal Code *
= Home Phone *
Work Phone *
Email Address <= input type=3D"text" size=3D"20" maxlength=3D"30" name=3D"Email"> *
= Best Time To Call *
Do You Own Your Home?
Property Value =3D 50000)) { alert('Not Valid! Please enter the approximate value of = current property or property you wish to purchase \n (greater than or equal= to 50000) using only number characters - 0123456789'); this=2Efocus(); thi= s=2Eselect(); return false; }"> * Please= use numbers only
Property Type *
Purchase= Price * Please use numb= ers only

Year Acquired

 *<= /td>
1st Mortgage-Balance Owed * Please use numbers only (ex:= 45000) enter 0 for none
1st Mortgage-In= terest Rate %
Is 1st Adjustable or = Fixed? *
Employer *
Monthly Gross House= hold Income * Please use numbers only
2nd Mortgage Balance owed > * Please use numbers only(ex:45000) enter 0 for none=
Amount You Wish To Borrow *
= = Credit Rating *
Monthly Debt= * Please use numbers only
Loan Interested In *
 

Fast & Easy -You Are Done !

Long Distance Conferencing
Only 18 Cents Per Minute

Connects Up To 100 Participants!<= /FONT>

<= /TABLE>

  • No setup fees
  • No contracts or monthly fees
  • Call anytime, from anywhere, to anywhere
  • International Dial In 18 cents per minute
  • Simplicity in set up and administration
  • Operator Help available 24/7
    • G= et the best quality, the easiest to use, and lowest rate in the industry.

    If you like saving m= oney, fill out the form below and one of our consultants will contact you.

    Required Input Field*

    Name*
    Web Address*
    Company Name*
    State*
    Business Phone*
    Home Phone
    Email Address*
    Type of Business

    This could be your ad!
    Click here to e-mail us your contact info.

    This email is to those persons that have contacted Conferen= ce Calls for Less regarding available services or product information. If thi= s email is reaching you in error and you feel that you have not contac= ted us, C= lick here. We will gladly remove you from our mailing list.

     From owner-linux-xfs@oss.sgi.com Mon Jul 9 18:38:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A1cIv27585 for linux-xfs-outgoing; Mon, 9 Jul 2001 18:38:18 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A1cFV27578 for ; Mon, 9 Jul 2001 18:38:16 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id DAA1268653 for ; Tue, 10 Jul 2001 03:38:16 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA14241; Tue, 10 Jul 2001 11:36:54 +1000 (EST) Date: Tue, 10 Jul 2001 11:36:53 +1000 From: Timothy Shimmin To: Juer Lee Cc: linux-xfs@oss.sgi.com Subject: Re: XFS ACL problem on PPC Message-ID: <20010710113653.J11622@boing.melbourne.sgi.com> References: <200107091635.f69GZaS01889@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200107091635.f69GZaS01889@jen.americas.sgi.com>; from lord@sgi.com on Mon, Jul 09, 2001 at 11:35:36AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Juer, On Mon, Jul 09, 2001 at 11:35:36AM -0500, Steve Lord wrote: > > > > Does anybody know whether the XFS really supports ACL on PPC :) maybe > > it is a foolish question -- since SGI announce that they support PPC > > and ACL -- but they don't tell us about that when using them at the > > same time. > > SGI has never said anything about support and PPC to my knowledge, people > have run XFS on the PPC architecture. Having said that, I am pretty sure > that the system call numbers for extended attribute and acl support are > only in the kernels for ia32 and ia64. Yep. We did this as we have no way of testing with PPC. We have mentioned before that if someone can make the changes and test them successfully on PPC, then we'll update the code. > For other platforms you would > need to add the system calls to the kernel, and make sure that the > user space commands use the correct system call numbers for your > architecture. Yep. And that's where the, "libacl: acl_set system call not defined for this architecture" message is coming from. One needs to update with acl sys call numbers: In userspace: cmd/acl/libacl/acl.c In kernelspace: linux/include/asm-ppc/unistd.h linux/arch/ppc/kernel/misc.S Check out the examples of: linux/include/asm-i386/unistd.h linux/arch/i386/kernel/entry.S Note that we have left a gap in the syscall numbering to try to avoid collisions with future syscalls which are being added. --Tim > > > I downloaded all the patch for XFS, and compiled successfully almost > > without any problems. > > The ACL utility is version 1.0.4, I downloaded the source code of it, > > compiled it successfully again. But after I read the source code > > of .../libacl/acl.c, I found that seemed not supporting PPC. > > So I have to try to find some version of ACL utility for PPC, this > > time I went to http://people.spoiled.org/tgr/unix/xfs/ppc/2.4.2/rpms, > > I downloaded acl-1.0.1-0.ppc.rpm and acl-devel-1.0.1-0.ppc.rpm, > > installed them on my PPC using LinuxPPC2000. I run 'chacl' again, I > > got the error message "libacl: acl_set system call not defined for > > this architecture" again, my god, I can not bear it now. I think it > > should be my PowerPC's problem... > > Who can help me? > > Thank you in advance. > > > > > > Juer From owner-linux-xfs@oss.sgi.com Mon Jul 9 19:36:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A2aHf32231 for linux-xfs-outgoing; Mon, 9 Jul 2001 19:36:17 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A2aGV32228 for ; Mon, 9 Jul 2001 19:36:16 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15JnNl-0008Em-00; Tue, 10 Jul 2001 04:36:14 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6A2aA117041; Mon, 9 Jul 2001 22:36:10 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Craig Tierney Cc: linux-xfs@oss.sgi.com Subject: Re: Problem with lvm in 2.4.6 and xfs References: <20010709174139.B11071@hpti.com> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 09 Jul 2001 22:36:10 -0400 In-Reply-To: <20010709174139.B11071@hpti.com> Message-ID: Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Craig" == Craig Tierney writes: Craig> kernel BUG at ll_rw_blk.c:691! Now, that is really, really odd. Could you try and add printk ("__make_request: rw = %d\n", rw); before BUG() (ll_rw_blk.c, line 691), reproduce the hang, and mail me the resulting output? I'm currently Alphally challenged as Compaq called my loaner boxes back so I can't check myself :| -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Mon Jul 9 19:49:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A2nKU00867 for linux-xfs-outgoing; Mon, 9 Jul 2001 19:49:20 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A2nIV00864 for ; Mon, 9 Jul 2001 19:49:18 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA02779 for ; Mon, 9 Jul 2001 19:46:42 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA14366; Tue, 10 Jul 2001 12:47:59 +1000 (EST) Date: Tue, 10 Jul 2001 12:47:59 +1000 From: Timothy Shimmin To: James A Goodwin Cc: "linux-xfs@oss.sgi.com" Subject: Re: DMAPI and dump/restore Message-ID: <20010710124759.K11622@boing.melbourne.sgi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: ; from jagoodwi@us.ibm.com on Mon, Jul 09, 2001 at 10:05:37AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi James, On Mon, Jul 09, 2001 at 10:05:37AM -0500, James A Goodwin wrote: > Does anyone know the extent to which DMAPI information is handled by > xfsdump/xfsrestore? There are two things that worry me: > > 1. Are xfsdump/xfsrestore smart enough to realize when data is not resident > on XFS disks? In other words, the data has been migrated by the DMAPI > client, and dm_puch_hole() was used to free up the XFS disk resources. > When doing a dump, I'd rather have xfsdump note that there is a hole rather > than dredging all the migrated data back up through the DMAPI. > > The xfsdump man page mentions a "-a" option for > working with DMF that sounds a lot like an answer to #1, but I'd be > surprised if there was any relationship between DMF and DMAPI. > I'm not that "au fait" with DMAPI stuff - Dean (roehrich@sgi.com) would be the one with answers to such questions :) However, the "-a" option is used to dump DMF dual-state and unmigrating files as offline (so no data is dumped). Looking at the code, - its extent data will be dumped as 1 extent with a hole (so the data aint dumped) - its DMF attributes won't be dumped but a replacement DMF attribute (i.e. DMF_ST_OFFLINE) will be dumped in its place - the stat buf's bs_devmask will be or'ed with DM_EVENT_READ (I don't know if this is enought for all DMAPI users or just DMF ?) Having said that, all the relevant code is #ifdef'ed out by the DMEXTATTR macro, and DMEXTATTR is commented out in the Makefile for LCFLAGS. Andrew Gildfind (ajag@sgi.com) did this, I believe as the DMAPI code wasn't complete at the time. Turning it back on may require some porting issues. Any comments, Andrew ? Someone should look into getting this going. > 2. What do xfsdump/xfsrestore do with DM attributes, regions, and event > lists? Are they stored, ignored, or something else? > I presumed all the DMAPI event stuff and other related data is in extended attributes. And all the extended attributes are dumped out (unless the -A option is used). Hmmmm....xfsrestore takes the -D option to restore DMAPI event settings. If F_FSSETDM macro is set then it uses fcntl(F_FSSETDM). All this code is #ifdef'ed out by the macro F_FSSETDM. This doesn't seem to be turned on in IRIX or Linux. Dean, is it not necessary to call fcntl(F_FSSETDM) ? Thanks. Cheers, --Tim From owner-linux-xfs@oss.sgi.com Mon Jul 9 22:23:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A5Nqf17613 for linux-xfs-outgoing; Mon, 9 Jul 2001 22:23:52 -0700 Received: from localhost.localdomain (cont01p53.ont.micron.net [204.228.207.55]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A5NnV17604 for ; Mon, 9 Jul 2001 22:23:50 -0700 Received: (from scott@localhost) by localhost.localdomain (8.11.2/8.11.2) id f6A5NZm01474; Mon, 9 Jul 2001 23:23:35 -0600 X-Authentication-Warning: localhost.localdomain: scott set sender to scott@jaderholm.com using -f To: linux-xfs@oss.sgi.com Subject: XFS and Emacs don't play nice From: Scott Jaderholm Date: 09 Jul 2001 23:23:33 -0600 Message-ID: Lines: 5 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.102 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, -- the sky is tired of being blue From owner-linux-xfs@oss.sgi.com Mon Jul 9 22:34:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A5YZn18314 for linux-xfs-outgoing; Mon, 9 Jul 2001 22:34:35 -0700 Received: from localhost.localdomain (cont01p53.ont.micron.net [204.228.207.55]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A5YWV18307 for ; Mon, 9 Jul 2001 22:34:32 -0700 Received: (from scott@localhost) by localhost.localdomain (8.11.2/8.11.2) id f6A5YJ101538; Mon, 9 Jul 2001 23:34:19 -0600 X-Authentication-Warning: localhost.localdomain: scott set sender to scott@jaderholm.com using -f To: linux-xfs@oss.sgi.com Cc: walters@cis.ohio-state.edu Subject: XFS and Emacs don't play nice From: Scott Jaderholm Date: 09 Jul 2001 23:34:18 -0600 Message-ID: Lines: 45 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.102 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry about the previous mostly blank message, I was trying to figure out how to add a CC header and pressed C-c (send). Hi, I am using XFS from the SGI RHL 7.1 installer. I'm using the smp kernel that comes with that system, Linux version 2.4.2-SGI_XFS_1.0smp (root@exclaim) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 SMP Fri Apr 27 17:52:42 CDT 2001 I am using FSF Emacs 21.0.102. My system just froze and when I rebooted I found this $ ls -l .emacs -rw-r--r-- 1 scott scott 29543 Jul 9 23:01 .emacs $ wc .emacs 0 0 29543 .emacs $ od .emacs ~/.backup 0000000 000000 000000 000000 000000 000000 000000 000000 000000 * 0071540 000000 000000 000000 000000 0071547 I was editing .emacs in Emacs when my computer froze. It looks like it's just 29kb of nul characters. Colin Walters (who I've CCed) has experienced similiar things with files being edited in emacs, and he is using version 21.0.103. Colin Walter is running Linux meta 2.4.3-xfs #1 SMP Fri Jun 1 15:56:17 EDT 2001 i686 unknown Colin thinks it has something to do with buffer cache corruption in the kernel. If you could please CC us on any discussion related to this we would appreciate it, we're not subscribed to the list. Sincerely, jsj -- the sky is tired of being blue From owner-linux-xfs@oss.sgi.com Tue Jul 10 00:27:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A7Rwv25503 for linux-xfs-outgoing; Tue, 10 Jul 2001 00:27:58 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A7RvV25498 for ; Tue, 10 Jul 2001 00:27:57 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6A7Rpn01294; Tue, 10 Jul 2001 09:27:52 +0200 Message-Id: <4.3.2.7.2.20010710092653.034b2830@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Jul 2001 09:27:41 +0200 To: Scott Jaderholm , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: XFS and Emacs don't play nice In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 23:23 9-7-2001 -0600, Scott Jaderholm wrote: >Hi, Hello. >the sky is tired of being blue What about red then? Details please. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Jul 10 01:33:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A8XBJ29526 for linux-xfs-outgoing; Tue, 10 Jul 2001 01:33:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A8X9V29523 for ; Tue, 10 Jul 2001 01:33:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id BAA03637 for ; Tue, 10 Jul 2001 01:33:10 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id DAA2391513; Tue, 10 Jul 2001 03:31:44 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id DAA10696; Tue, 10 Jul 2001 03:31:37 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6A8WrQ07640; Tue, 10 Jul 2001 03:32:53 -0500 Message-Id: <200107100832.f6A8WrQ07640@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Craig Tierney cc: linux-xfs@oss.sgi.com Subject: Re: Problem with lvm in 2.4.6 and xfs In-Reply-To: Message from Craig Tierney of "Mon, 09 Jul 2001 17:41:39 MDT." <20010709174139.B11071@hpti.com> Date: Tue, 10 Jul 2001 03:32:53 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is actually probably caused by the nfs sparse file change, I will be backing that code out and looking for a new solution to that particular problem. Despite beating the code to death, it appears other peoples systems can make this happen when mine cannot.... Steve > I am trying to create an lvm partition (of one device). > I have done this before under x86, but I am trying this > on Alpha. I can run mkfs -t xfs, but when I try and > mount the filesystem I get the error below. > > Setup: > > XP1000, Qlogic FC2220 > linux-2.4.6 with Tronds latest NFS patches > linux-2.4.6-xfs-07052001.patch > Qlogic 4.27Beta driver > mount has been upgraded to 2.11.2 (linux-util-2.11.2) > LVM is kernel lvm only (0.9.1-6). > > I also added just the patch from page_buf_io.c to help with > sparse files, but I have the same problem without that patch. > I did not update the LVM in the 2.4.6 kernel (as that messes > up the xfs patch). > > I am running xfs+lvm successfully under x86 with the FC drive setup. > > kernel BUG at ll_rw_blk.c:691! > mount(974): Kernel Bug 1 > pc = [] ra = [] ps = 0000 > v0 = 000000000000001f t0 = 0000000000000001 t1 = 0000000000000001 > t2 = 0000000000000000 t3 = fffffc0066708000 t4 = fffffc0000624b20 > t5 = fffffc0000654558 t6 = 0000000000000001 t7 = fffffc0066708000 > a0 = 0000000000000000 a1 = 0000000000000001 a2 = 0000000000000001 > a3 = fffffffffffffff9 a4 = 0000000000000002 a5 = 0000000000000000 > t8 = 0000000000003fff t9 = fffffc0000659ba8 t10= 0000000000000006 > t11= 000000000000000a pv = fffffc0000328820 at = fffffc0000653400 > gp = fffffc00006485c0 sp = fffffc006670b5b8 > Code: 225f02b3 lda a2,691(zero) > a77dae78 ldq pv,-20872(gp) > 6b5b77df jsr ra,(pv) > 27ba001c ldah gp,28(ra) > 23bda75c lda gp,-22692(gp) > 00000081 call_pal 129 > *c3e0025f br .+2432 > 2fe00000 ldq_u zero,0(v0) > > Trace:48e974 340841 3d9c88 3d9f9c 3da510 3d9dc0 3da100 3d93dc 3d8994 451b34 4 > 3c7c8 > 446928 43be28 446824 446d3c 446db4 45b014 35ce50 3737d0 360504 35d1dc 35cdc8 > 35d23c 35e1c4 35e170 35e668 35e770 35e750 310ae0 > > Craig > > -- > Craig Tierney (ctierney@hpti.com) > phone: 303-497-3112 From owner-linux-xfs@oss.sgi.com Tue Jul 10 02:17:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6A9HL932302 for linux-xfs-outgoing; Tue, 10 Jul 2001 02:17:21 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6A9HKV32299 for ; Tue, 10 Jul 2001 02:17:20 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id CAA09978 for ; Tue, 10 Jul 2001 02:17:11 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id EAA2392044; Tue, 10 Jul 2001 04:16:02 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id EAA39479; Tue, 10 Jul 2001 04:16:02 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6A9HIR14760; Tue, 10 Jul 2001 04:17:18 -0500 Message-Id: <200107100917.f6A9HIR14760@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Scott Jaderholm cc: linux-xfs@oss.sgi.com, walters@cis.ohio-state.edu Subject: Re: XFS and Emacs don't play nice In-Reply-To: Message from Scott Jaderholm of "09 Jul 2001 23:34:18 MDT." Date: Tue, 10 Jul 2001 04:17:17 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk First of all, I would encourage both of you to update to a more recent kernel. There are some new rpms on the ftp site, I would recommend these: ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/RPMS/RHlinux-2.4.3/ They are based on the updated kernel rpm from redhat 7.1, and contain a lot of xfs fixes. Secondly the cvs tree development tree is always a good thing to try when you have problems. As for what is happening to your file. This is not corruption per se, the updated inode size made it out to disk, but the data did not. If you do an xfs_bmap you will probably find there are are no extents in the file. (xfs_bmap .emacs). It is also not in in kernel buffer corruption problem, it is because the buffers were not written to disk before the crash, but the inode size was written in a transaction. Please try a later kernel as I have not seen reports like this in a while. Steve > Sorry about the previous mostly blank message, I was trying to figure > out how to add a CC header and pressed C-c (send). > > Hi, > > I am using XFS from the SGI RHL 7.1 installer. I'm using the smp > kernel that comes with that system, > > Linux version 2.4.2-SGI_XFS_1.0smp (root@exclaim) (gcc version > egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 SMP Fri Apr 27 > 17:52:42 CDT 2001 > > I am using FSF Emacs 21.0.102. > > My system just froze and when I rebooted I found this > > $ ls -l .emacs > -rw-r--r-- 1 scott scott 29543 Jul 9 23:01 .emacs > $ wc .emacs > 0 0 29543 .emacs > $ od .emacs ~/. > backup > 0000000 000000 000000 000000 000000 000000 000000 000000 000000 > * > 0071540 000000 000000 000000 000000 > 0071547 > > I was editing .emacs in Emacs when my computer froze. It looks like > it's just 29kb of nul characters. Colin Walters (who I've CCed) has > experienced similiar things with files being edited in emacs, and he > is using version 21.0.103. > > Colin Walter is running Linux meta 2.4.3-xfs #1 SMP Fri Jun 1 15:56:17 > EDT 2001 i686 unknown > > Colin thinks it has something to do with buffer cache corruption in > the kernel. > > If you could please CC us on any discussion related to this we would > appreciate it, we're not subscribed to the list. > > Sincerely, > jsj > > -- > the sky is tired of being blue From owner-linux-xfs@oss.sgi.com Tue Jul 10 04:28:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ABS7u09502 for linux-xfs-outgoing; Tue, 10 Jul 2001 04:28:07 -0700 Received: from piro.kabuki.sfarc.net (postfix@[203.36.158.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ABS4V09498 for ; Tue, 10 Jul 2001 04:28:05 -0700 Received: by piro.kabuki.sfarc.net (Postfix, from userid 1000) id B667814AC961; Tue, 10 Jul 2001 21:28:28 +1000 (EST) Date: Tue, 10 Jul 2001 21:28:28 +1000 From: Daniel Stone To: Steve Lord Cc: Scott Jaderholm , linux-xfs@oss.sgi.com, walters@cis.ohio-state.edu Subject: Re: XFS and Emacs don't play nice Message-ID: <20010710212828.B10357@kabuki.sfarc.net> Mail-Followup-To: Steve Lord , Scott Jaderholm , linux-xfs@oss.sgi.com, walters@cis.ohio-state.edu References: <200107100917.f6A9HIR14760@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107100917.f6A9HIR14760@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Organisation: Sadly lacking Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 10, 2001 at 04:17:17AM -0500, Steve Lord wrote: > As for what is happening to your file. This is not corruption per se, the > updated inode size made it out to disk, but the data did not. If you do > an xfs_bmap you will probably find there are are no extents in the file. > (xfs_bmap .emacs). It is also not in in kernel buffer corruption problem, > it is because the buffers were not written to disk before the crash, but > the inode size was written in a transaction. > > Please try a later kernel as I have not seen reports like this in a > while. Let me add my voice - I haven't posted this as yet, because I've been trying to track it down as to where it started, but I'm getting null-byte corruption through entire files (my entire /etc/mailcap got replaced with null bytes, as did the postinst's for a few packages). I'm tracking CVS, and it appears to only have happened with the -pre2 sync, everything previous seemed to work OK (though admittedly I haven't tried -pre1, and that was most likely the culprit, being a large -ac sync). The affected partitions are on IDE drives, not a VIA chipset or anything. :) d -- Daniel Stone "can NE1 help me aim nuclear weaponz????? /MSG ME!!" From owner-linux-xfs@oss.sgi.com Tue Jul 10 04:59:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ABxFZ20865 for linux-xfs-outgoing; Tue, 10 Jul 2001 04:59:15 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ABxEV20853 for ; Tue, 10 Jul 2001 04:59:14 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6ABx0x02137; Tue, 10 Jul 2001 13:59:01 +0200 Message-Id: <4.3.2.7.2.20010710133525.034cce10@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Jul 2001 13:58:50 +0200 To: Daniel Stone , Steve Lord From: Seth Mos Subject: Re: XFS and Emacs don't play nice Cc: Scott Jaderholm , linux-xfs@oss.sgi.com, walters@cis.ohio-state.edu In-Reply-To: <20010710212828.B10357@kabuki.sfarc.net> References: <200107100917.f6A9HIR14760@jen.americas.sgi.com> <200107100917.f6A9HIR14760@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:28 10-7-2001 +1000, Daniel Stone wrote: >On Tue, Jul 10, 2001 at 04:17:17AM -0500, Steve Lord wrote: > > As for what is happening to your file. This is not corruption per se, the > > updated inode size made it out to disk, but the data did not. If you do > > an xfs_bmap you will probably find there are are no extents in the file. > > (xfs_bmap .emacs). It is also not in in kernel buffer corruption problem, > > it is because the buffers were not written to disk before the crash, but > > the inode size was written in a transaction. > > > > Please try a later kernel as I have not seen reports like this in a > > while. > >Let me add my voice - I haven't posted this as yet, because I've been trying >to track it down as to where it started, but I'm getting null-byte >corruption through entire files (my entire /etc/mailcap got replaced with >null bytes, as did the postinst's for a few packages). I'm tracking CVS, and >it appears to only have happened with the -pre2 sync, everything previous >seemed to work OK (though admittedly I haven't tried -pre1, and that was >most likely the culprit, being a large -ac sync). The affected partitions >are on IDE drives, not a VIA chipset or anything. The source must be with you if you are running -pre kernels. This breakage can be expected, the TAKE message of the checkout specifically mentioned that it did compile but was not tested. Cheers Seth -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Jul 10 05:37:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ACbgN22238 for linux-xfs-outgoing; Tue, 10 Jul 2001 05:37:42 -0700 Received: from piro.kabuki.sfarc.net (postfix@[203.36.158.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ACbdV22235 for ; Tue, 10 Jul 2001 05:37:40 -0700 Received: by piro.kabuki.sfarc.net (Postfix, from userid 1000) id 29FCD14AC961; Tue, 10 Jul 2001 22:38:06 +1000 (EST) Date: Tue, 10 Jul 2001 22:38:06 +1000 From: Daniel Stone To: Seth Mos Cc: Steve Lord , Scott Jaderholm , linux-xfs@oss.sgi.com, walters@cis.ohio-state.edu Subject: Re: XFS and Emacs don't play nice Message-ID: <20010710223806.A11621@kabuki.sfarc.net> Mail-Followup-To: Seth Mos , Steve Lord , Scott Jaderholm , linux-xfs@oss.sgi.com, walters@cis.ohio-state.edu References: <200107100917.f6A9HIR14760@jen.americas.sgi.com> <200107100917.f6A9HIR14760@jen.americas.sgi.com> <4.3.2.7.2.20010710133525.034cce10@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.20010710133525.034cce10@pop.xs4all.nl> User-Agent: Mutt/1.3.18i Organisation: Sadly lacking Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 10, 2001 at 01:58:50PM +0200, Seth Mos wrote: > At 21:28 10-7-2001 +1000, Daniel Stone wrote: > >On Tue, Jul 10, 2001 at 04:17:17AM -0500, Steve Lord wrote: > > > As for what is happening to your file. This is not corruption per se, the > > > updated inode size made it out to disk, but the data did not. If you do > > > an xfs_bmap you will probably find there are are no extents in the file. > > > (xfs_bmap .emacs). It is also not in in kernel buffer corruption problem, > > > it is because the buffers were not written to disk before the crash, but > > > the inode size was written in a transaction. > > > > > > Please try a later kernel as I have not seen reports like this in a > > > while. > > > >Let me add my voice - I haven't posted this as yet, because I've been trying > >to track it down as to where it started, but I'm getting null-byte > >corruption through entire files (my entire /etc/mailcap got replaced with > >null bytes, as did the postinst's for a few packages). I'm tracking CVS, and > >it appears to only have happened with the -pre2 sync, everything previous > >seemed to work OK (though admittedly I haven't tried -pre1, and that was > >most likely the culprit, being a large -ac sync). The affected partitions > >are on IDE drives, not a VIA chipset or anything. > > The source must be with you if you are running -pre kernels. > This breakage can be expected, the TAKE message of the checkout > specifically mentioned that it did compile but was not tested. I'm aware of this. Not only am I running a pre kernel, from CVS, but it said that it wasn't tested. Fear. -- Daniel Stone "can NE1 help me aim nuclear weaponz????? /MSG ME!!" From owner-linux-xfs@oss.sgi.com Tue Jul 10 06:59:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ADxe024617 for linux-xfs-outgoing; Tue, 10 Jul 2001 06:59:40 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ADxcV24614 for ; Tue, 10 Jul 2001 06:59:38 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA1260486 for ; Tue, 10 Jul 2001 15:59:38 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2392411 for ; Tue, 10 Jul 2001 08:58:17 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA79850 for ; Tue, 10 Jul 2001 08:58:17 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6ADxVS04153; Tue, 10 Jul 2001 08:59:31 -0500 Message-Id: <200107101359.f6ADxVS04153@jen.americas.sgi.com> Date: Tue, 10 Jul 2001 08:59:31 -0500 Subject: TAKE - fix md block handling optimization Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The code checked in last week did not take into account the 64 bit nature of the fields being used. This will only affect md. Thanks to Mike Ovsiannikov for the fix. Date: Tue Jul 10 06:57:08 PDT 2001 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:98515a linux/fs/pagebuf/page_buf.c - 1.94 - Fix for field overflow in handling 64 bit value From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:01:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AE1ul24804 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:01:56 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AE1tV24801 for ; Tue, 10 Jul 2001 07:01:55 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA07737 for ; Tue, 10 Jul 2001 07:01:52 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2391662 for ; Tue, 10 Jul 2001 09:00:33 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA78186 for ; Tue, 10 Jul 2001 09:00:33 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6AE1mm06583; Tue, 10 Jul 2001 09:01:48 -0500 Message-Id: <200107101401.f6AE1mm06583@jen.americas.sgi.com> Date: Tue, 10 Jul 2001 09:01:48 -0500 Subject: TAKE - back out sparse nfs files fix Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This fix was working for me without problems, but it was driving Andi Kleen up the wall, and our own internal regression tests finally tripped it to. I will rework the nfs fix another way. Date: Tue Jul 10 06:59:30 PDT 2001 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:98516a linux/fs/pagebuf/page_buf_io.c - 1.89 - Remove the 'fix' for sparse files written by nfs, this broke other things by creating pages beyond the end of file. From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:21:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AELV525545 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:21:31 -0700 Received: from nbd.it.uc3m.es (nbd.it.uc3m.es [163.117.139.192]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AELSV25537 for ; Tue, 10 Jul 2001 07:21:28 -0700 Received: (from ptb@localhost) by nbd.it.uc3m.es (8.9.3/8.9.3/Debian 8.9.3-6) id QAA02118 for linux-xfs@oss.sgi.com; Tue, 10 Jul 2001 16:21:14 +0200 From: "Peter T. Breuer" Message-Id: <200107101421.QAA02118@nbd.it.uc3m.es> Subject: 2.4.6 patch does not apply cleanly to 2.4.6 To: linux-xfs@oss.sgi.com Date: Tue, 10 Jul 2001 16:21:13 +0200 (CEST) X-Anonymously-To: Reply-To: ptb@it.uc3m.es X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=UNKNOWN-8BIT X-MIME-Autoconverted: from 8bit to quoted-printable by nbd.it.uc3m.es id QAA02118 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6AELTV25542 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The 2.4.6 patch didn't apply cleanly to a pure kernel source .. ./fs/buffer.c.rej ./fs/namei.c.rej ./mm/vmscan.c.rej And in any case the patch I got hold of linux-2.4.6-xfs-cvs-06212001.patch contains all kinds of cvs and acl cmd extranea. Is there a clean kernel patch hanging around somewhere? The .rej's themselves are easy to mend, except for buffer.c, in which I can't find a likely referant for the failed block. And in any case compilation of the result fails in aic7xxx! make[4]: Entering directory `/usr/local/src/linux-2.4.6-xfs/drivers/scsi/aic7xxx' echo "Warning, generated aic7xxx firmware files may be out of date!\n" Warning, generated aic7xxx firmware files may be out of date!\n echo "Warning, generated aic7xxx firmware files may be out of date!\n" Warning, generated aic7xxx firmware files may be out of date!\n gcc -D__KERNEL__ -I/usr/local/src/linux-2.4.6-xfs/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o aic7xxx_linux.o aic7xxx_linux.c In file included from aic7xxx_osm.h:343, from aic7xxx_linux.c:133: aic7xxx.h:40: aic7xxx_reg.h: No such file or directory ^^^^^^^^^^^^^^^ In file included from aic7xxx_linux.c:133: aic7xxx_osm.h: In function àhc_flush_device_writes': aic7xxx_osm.h:901: `INTSTAT' undeclared (first use in this function) aic7xxx_osm.h:901: (Each undeclared identifier is reported only once aic7xxx_osm.h:901: for each function it appears in.) So I would guess random other patches have been applied. Fair 'nuff. Just give me a clue what they are! Moving the 2.4.5 aic7xxx_reg.h across almost does the trick, but not quite. aic7xxx_seq.h is also needed. That seems to fix it. But what happened? Peter From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:26:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AEQLQ25787 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:26:21 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AEQKV25782 for ; Tue, 10 Jul 2001 07:26:20 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA01304 for ; Tue, 10 Jul 2001 07:26:21 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2392488; Tue, 10 Jul 2001 09:25:03 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA88831; Tue, 10 Jul 2001 09:25:03 -0500 (CDT) Message-ID: <3B4B107A.60EB38AE@sgi.com> Date: Tue, 10 Jul 2001 09:26:02 -0500 From: sandeen@sgi.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Stone CC: linux-xfs@oss.sgi.com Subject: Re: XFS and Emacs don't play nice References: <200107100917.f6A9HIR14760@jen.americas.sgi.com> <20010710212828.B10357@kabuki.sfarc.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Daniel Stone wrote: > I'm getting null-byte > corruption through entire files (my entire /etc/mailcap got replaced with > null bytes, as did the postinst's for a few packages). Can this be traced to system hangs or crashes, or is this on a happily running system? If it's the former, then see Steve's explanation in this thread... -Eric From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:29:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AETpQ25996 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:29:51 -0700 Received: from piro.kabuki.sfarc.net (postfix@[203.36.158.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AETnV25993 for ; Tue, 10 Jul 2001 07:29:49 -0700 Received: by piro.kabuki.sfarc.net (Postfix, from userid 1000) id 066BC14AC961; Wed, 11 Jul 2001 00:30:14 +1000 (EST) Date: Wed, 11 Jul 2001 00:30:13 +1000 From: Daniel Stone To: sandeen@sgi.com Cc: Daniel Stone , linux-xfs@oss.sgi.com Subject: Re: XFS and Emacs don't play nice Message-ID: <20010711003013.B11621@kabuki.sfarc.net> Mail-Followup-To: sandeen@sgi.com, Daniel Stone , linux-xfs@oss.sgi.com References: <200107100917.f6A9HIR14760@jen.americas.sgi.com> <20010710212828.B10357@kabuki.sfarc.net> <3B4B107A.60EB38AE@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B4B107A.60EB38AE@sgi.com> User-Agent: Mutt/1.3.18i Organisation: Sadly lacking Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 10, 2001 at 09:26:02AM -0500, sandeen@sgi.com wrote: > Daniel Stone wrote: > > > I'm getting null-byte > > corruption through entire files (my entire /etc/mailcap got replaced with > > null bytes, as did the postinst's for a few packages). > > Can this be traced to system hangs or crashes, or is this on a happily > running system? If it's the former, then see Steve's explanation in > this thread... It has hung, but only after I've got the corruption. Probably due to heat, I don't know and don't particularly care, because it runs 99.9% of the time, and there's nothing I can do about the heat, short of ripping out a couple of hard drives, getting a bigger case and rearranging stuff. As for the null bytes, I knew what I was in for when I started tracking XFS CVS. *shrug* :) d -- Daniel Stone "can NE1 help me aim nuclear weaponz????? /MSG ME!!" From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:50:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AEoQw26573 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:50:26 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AEoOV26570 for ; Tue, 10 Jul 2001 07:50:24 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6AEoJx02841; Tue, 10 Jul 2001 16:50:19 +0200 Message-Id: <4.3.2.7.2.20010710164832.03481e90@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Jul 2001 16:50:09 +0200 To: ptb@it.uc3m.es, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 In-Reply-To: <200107101421.QAA02118@nbd.it.uc3m.es> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 16:21 10-7-2001 +0200, Peter T. Breuer wrote: >The 2.4.6 patch didn't apply cleanly to a pure kernel source .. > > ./fs/buffer.c.rej > ./fs/namei.c.rej > ./mm/vmscan.c.rej > >And in any case the patch I got hold of > > linux-2.4.6-xfs-cvs-06212001.patch > >contains all kinds of cvs and acl cmd extranea. Is there a clean kernel >patch hanging around somewhere? This was a snapshot of the CVS tree in between -pre merging. It was never really tested that much AFAIK. >The .rej's themselves are easy to mend, except for buffer.c, in which I >can't find a likely referant for the failed block. And in any case >compilation of the result fails in aic7xxx! See FAQ. This is not related to the XFS patch. >So I would guess random other patches have been applied. Fair 'nuff. >Just give me a clue what they are! Moving the 2.4.5 aic7xxx_reg.h >across almost does the trick, but not quite. aic7xxx_seq.h is also >needed. That seems to fix it. But what happened? The FAQ has a nic entry for this. CHeers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:52:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AEqTp26759 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:52:29 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AEqSV26755 for ; Tue, 10 Jul 2001 07:52:28 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA24135 for ; Tue, 10 Jul 2001 07:52:19 -0700 (PDT) mail_from (sandeen@sgi.com) From: sandeen@sgi.com Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2391568; Tue, 10 Jul 2001 09:51:11 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA83143; Tue, 10 Jul 2001 09:51:11 -0500 (CDT) Message-ID: <3B4B169A.A96AAAE4@sgi.com> Date: Tue, 10 Jul 2001 09:52:10 -0500 X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: ptb@it.uc3m.es CC: linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 References: <200107101421.QAA02118@nbd.it.uc3m.es> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Peter T. Breuer" wrote: > And in any case the patch I got hold of > > linux-2.4.6-xfs-cvs-06212001.patch > > contains all kinds of cvs and acl cmd extranea. Is there a clean kernel > patch hanging around somewhere? Yep, the xfs-cvs patches are designed to seed a whole CVS tree... and if that patch above was generated on 6/21, it was probably against a 2.4.6-preX kernel. Did you try ftp://oss.sgi.com/projects/xfs/download/patches/linux-2.4.6-xfs-07052001.patch.bz2? That should apply cleanly. Be warned, though, that this stuff is all just snapshots of the development tree, with all the usual dire warnings and caveats about such things... -Eric From owner-linux-xfs@oss.sgi.com Tue Jul 10 07:54:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AEsA426912 for linux-xfs-outgoing; Tue, 10 Jul 2001 07:54:10 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AEs9V26908 for ; Tue, 10 Jul 2001 07:54:09 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6AEs0x02847; Tue, 10 Jul 2001 16:54:00 +0200 Message-Id: <4.3.2.7.2.20010710165051.0348e580@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Jul 2001 16:53:50 +0200 To: Daniel Stone , sandeen@sgi.com From: Seth Mos Subject: Re: XFS and Emacs don't play nice Cc: Daniel Stone , linux-xfs@oss.sgi.com In-Reply-To: <20010711003013.B11621@kabuki.sfarc.net> References: <3B4B107A.60EB38AE@sgi.com> <200107100917.f6A9HIR14760@jen.americas.sgi.com> <20010710212828.B10357@kabuki.sfarc.net> <3B4B107A.60EB38AE@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:30 11-7-2001 +1000, Daniel Stone wrote: >On Tue, Jul 10, 2001 at 09:26:02AM -0500, sandeen@sgi.com wrote: > > Daniel Stone wrote: > > > > > I'm getting null-byte > > > corruption through entire files (my entire /etc/mailcap got replaced with > > > null bytes, as did the postinst's for a few packages). > > > > Can this be traced to system hangs or crashes, or is this on a happily > > running system? If it's the former, then see Steve's explanation in > > this thread... > >It has hung, but only after I've got the corruption. Probably due to heat, I >don't know and don't particularly care, because it runs 99.9% of the time, >and there's nothing I can do about the heat, short of ripping out a couple >of hard drives, getting a bigger case and rearranging stuff. I've got a big one to fit all my stuff in ;) http://www.yeongyang.com/products/yy0320-0330.htm >As for the null bytes, I knew what I was in for when I started tracking XFS >CVS. *shrug* Yay! -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Jul 10 08:15:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AFFgp27918 for linux-xfs-outgoing; Tue, 10 Jul 2001 08:15:42 -0700 Received: from mail.powerworkstation.de (mail.powerworkstation.de [195.145.22.147]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AFFcV27910 for ; Tue, 10 Jul 2001 08:15:39 -0700 Received: from no.name.available by mail.powerworkstation.de via smtpd (for oss.sgi.com [216.32.174.27]) with SMTP; 10 Jul 2001 15:13:56 UT Received: by srvellwangen.rand.de with Internet Mail Service (5.5.2653.19) id <34Q03Z4L>; Tue, 10 Jul 2001 17:18:35 +0200 Message-ID: <5243EBD6FB48D51184E200A0C9A9D56014543C@srvellwangen.rand.de> From: "Huettner, Ewald" To: "'linux-xfs@oss.sgi.com'" Subject: FW: nfsd-crash Date: Tue, 10 Jul 2001 17:18:34 +0200 Importance: high X-Priority: 1 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C10953.960B40E0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C10953.960B40E0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C10953.960B40E0" ------_=_NextPart_001_01C10953.960B40E0 Content-Type: text/plain; charset="iso-8859-1" <> Hallo, i have a Problem at an Customer, he has an lh3000 (HP) with Redhat Linux 7.1 and XFS 1.0 Kernerl 2.4.5 The Server runs some time and then the nfsd crash`s down with errors in messages. The nfsd can not be restartet at the system, only reboot and reset ist ok too restart the server and the nfsd. On this Server there are 8 HP-UX Workstations with NFS connectet to the Linux Server. At the Server there are the following filesystems: / ext2 /boot ext2 /data xfs Has anyone an workaround for this Problem???? Ewald Huettner email: ehuettner@rand.de Phone: 07961890186 <> ------_=_NextPart_001_01C10953.960B40E0 Content-Type: text/html; charset="iso-8859-1" FW: nfsd-crash

    <<crash.zip>>

     Hallo,
    i have a Problem at an Customer, he has an lh3000 (HP) with Redhat Linux
    7.1 and XFS 1.0
    Kernerl 2.4.5

    The Server runs some time and then the nfsd crash`s down with errors in
    messages. The nfsd can not be restartet at the system, only reboot and
    reset ist ok too restart the server and the nfsd. On this Server there
    are 8 HP-UX Workstations with NFS
    connectet to the Linux Server.
    At the Server there are the following filesystems:
    /       ext2
    /boot   ext2
    /data   xfs


    Has anyone an  workaround for this Problem????

    Ewald Huettner
    email: ehuettner@rand.de
    Phone: 07961890186

     <<crash.zip>>

    ------_=_NextPart_001_01C10953.960B40E0-- ------_=_NextPart_000_01C10953.960B40E0 Content-Type: application/x-zip-compressed; name="crash.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="crash.zip" UEsDBBQAAgAIABZw6ir2XuJiKxEAAOk3AAATAAAAbGluaXgtMjQ1LWRtZXNnLnR4dO1b+3PbRpKu e/yEv6Krsnch60hwAJAAyI1coUjK5lq0eKKseCvlUoHAgMQKBLAAKIn+6+/rAV9WJNt57G1Sa8aR gEF3T8/06+shdB4l6we6k3kRpQmZelvvNIVu6t2b2cvxzbuz2Y0phCFsw6Janqbl9366KqUv2nWq LXx/zykXftEEm6HbNhndbldYRrt1rqTX1ENDN3STchlLr5D1On1j0BCMf1nH1CGj0xMu/tFgNLsi nlI7HV/Mmlme3kWBDChbborI92K67E9o5WU9jRSBdE3RI/HoQ83joa5sY6i2Lrx5LOvPMVZUHzF6 SlYtl4XM72TwLKu0H7Ma4stYjcfqmmEYVqyfUndP9TFj6DNjfzAdU+CV3vO8ivDAa+22reJ9cz17 mjWE4R9NG8rgi5YaSvlT1vDLWMPw0QYbu0fHrGG6TgKaTaY0mTZL3jvySuYIHdsS2nLVoMxbyGqE eXesVN5HvtQ/pnA/S9H9HEVXfpYi/BxF5YGPKS4SStIABFSmpRczcdFD1Nmdrql9SBNZE/UetUXX VoIKvRo06kxkth8NmxgWu5FxUsqYJuu4jKZ56suiSHOaZdKPQoRfyaF+Z+htjfC5jvJyjZD8Icol IS9keD6P4qjc0ArqQc/RhMbDHr2aUvWByGDtl2rw/BWx31UP+tPxAOaCIg9no5GyrXaY/xtBU5mU 0XpVK1d1llIx7JKP4Wjj1kU1hrRyvR9WHgCJAyVRP6Iyn6QyFNV+Yt5U7bXME2wJ1rfy4GBxlMge eesypdOLi6ub8aT/cnQSq0QHvThHnriiUz08G5+PTlpzjLXuVkzzofnJFJt7qyAqbm+K6IM8MTvY hHESlZEXRx+iZEGD6dtvhDaUSMAlvKFrCmTbNk1efaBsp7OuDdKkSGMo6adxus7p+mX/f8gVD2ZH G0DSPIeZICyQsbehOE0zXdfJcK2ODmucpot0Mp7OtIlcpfmmR47dabfd25bj2pbt3pJ350Wxiq6a KTrOLd3u9ieQDTIQau3bvcNiQFi3Khk1yDTBHmE9DRK3tIwWy5Vc1bGcpMw3Td/zl5KWXrGkKnh5 OFJ+bRnCMamW5oHMe+Sy0LbbcWyab0pZ1LFHmPsTAuxOx7L3/E6DOmbbdN0d++kaCSb/Yn4bK7FN o93e8U8ROZ/g3hLv2LtgF13H6Jg7fli1R6cyTBFFdzIJ4PDVLvleBn5huU44D8N9PtxfNHbkJyQq KecGjUmpgm2zXzd4YHg0sKUyd0NmB2NVyK8wAtcmjPuwco47drM1lCrWWZbm8Dj9Sdpc8lN2KZnw 0gNCVClX1av5+mEp85+3tP0FSyA4E2KAkvVqDkGIEDXNVrpKH2qGhUxA6B9Jt75Aeo+OPwOEOdT/ mRKqbdnmKBqPx1QbpFkm8xW2qU5FKbOMN0jY2oj3iK9DryjpjFfn3aFUIbUgako4AYdjgMSsH2jX ycorbrGzs/FkqJjkgy8zlY631jlwDdgqzPXtMi6/xYYXZY6kC1qmuXiNBHcxG79DxCbwOSQ1XxIc UVlwvqG3b8Zn43faqszhrZzrBUc6EpRlOnW6jPyllwf0Mk39Jcrvgn9/75VJqPtFlKe6t65veYNd nuJbKjeZ3G6UNh2Me4Qfqtpj2XfRFn0aQsXNpsrIYdD1EC4xb9R8XZzYFePbgjVl7aPFOq9qEktH rq4E5+mcKXgC1vXey6X2NrlN0vuE5nkUoLRiq5EasXDgDK8o1itmKHMvKTJQJ+Wz9OYz9GrmYVT4 KYoS49U8WnlYSCbhmFAevkQ/ji//9/3xGnCPgrFm351xvsx/SPPbgn40DNtuCWz6+wrC9ESoCw1u nyVZj2a+lyTKgxBO02QKZ82DArbdU7xJaRqvF/Tf+IUcH2CDoboCSFoFyd+Mrtq6UBKqAZQl7RTA PKB1hv2c3WNp0qO3SaSKLEo6IiOrVE39SGIAMixdWN2Pa9TlFSWyhNfeUpH6t7LUvGzVqyydpGWl ha7NSq/KGbfFvZcF7Giu5sVxCpABJSyzAiQqLnAzXxYHFMRal5xtqxJCc4hE8dOwzhBReyfgR6Zy WiFs0/xCp91yc7G+SVVocQZ4MFV+n6/DKmdiG7JNjolLqvl11anQDJgH7kgvcy9bRn7RgJv7uobK TmEUy2KD+F/9DMasRN01UeN4+x+6LmGg2Du8DLRZlQ+DnI2zR0Go3515FatNAYhh1ek+Kpc06b/5 68304vJqRpO351djvqTZq/7l6IYdcDa6HPfPbzhaxrP+9M10l8a1stzMkOpULAordKkW5X9HsUHv F8EyKCidjuhXZMaWzDyQWR+TXUqofBWtsIWw8i0Nt9qjLxSBNuexHv19LdewcIHEAfiFQvPQitN7 6gjH7tq3py3LsW2zfXsKDMA1uYjTskCM5RWjhuZwOJ693u1MtHNMGXD5U70j46uC0pAYXr0mRlrA EyaqOWvAt4j9iBNjhYKbCKFS3Y6a4+FoJ/pym7SAB3TL0NCjos7tEoNlMSTb2p2Dv0AaqPx2Or5Q 4Lj4M3GmQHaRlZVwwTnu4UE7TgUXs9M2sibmhfnLPI1jzA1bs7VUVhEc3eR0n+BCjc4KWR7yq3iC iEMSqPe/KEEiRR1i3XrQKI4ZUs4lwZYFUjACX2F+qImUeTppDif9yuSG3xVN9QvISoU5JuXQRvgs A6+XRWkDF3O+2IkwfiLCrUSET4jwdyICJYJl0qvxVX/wakyD4WXTbVudBvWvAOxx3xpeD5uXF5PK UGyYrQcboVIzdBriwQpt3kX2U6NdSaz4LfMdZBz44WdArac04NjfO8YxxbErWLphamcxKv+melgr 0FuFgeBAQCVtT7Sz4YBEFRdvVOlCUMzkitMAd0bsIQPXsQAUVsFuAqF3BZL1pP/uZjK8GY6uZ+gN AENxMzu9YYfHgAMG3e8ph07D2irIboAMZH5T1jlk0Qtq3LRURVkl6v54CJyXe5tCPcnXCXERYZCw ux9evBnpGheL3rZOXA2mrfEUi6mKR1VHNIyg6pYpOg6YbDyYTBv0dogfIEdSezmZgqSnap2q3Y/B MsLRRWcKl+aKgTxot18rdKxBAKy9pzxOg1QDaGGAVCxxs8PkEQqGAuz1bamDbisOZJ9hxLbaYjvR A8cIoOl40pxNtkvkdAsQtfKiZFu82GyixYcKh1JZrVnfJZueqowoTlw8UfQX20rLXqdyCuLuLJeS F84JCXVote2tLAeNUIhngXZ9NuvRBHxc/biJxOoeSvOogNRRNAezMfDefJtZfuJ/0FVU+OJMacDp vas030IAhhIm7FWg7AmC0wdeBn+g/njgvHv3jkaoAK3r89MW5xc126vTPg0vx9ejywZPhGyHfG1p O7j83U6C2TVsQW9jYCK+ULyeepa/2FN7ke+4XUCoPd0PnP8GSwAa4Od+o+IbBydIJZbZMjsdjJwW GiRcq/YBeePN4NWkf/masFtoYQG6zq+MjyA864m97RqnYLtSsJMQY6gQCVeDZt/nTpl+8um/mW0X ne93VJjaSi683IsCBYaNDtUuqyNMGiIp9uhquaZ+lpPRJdHtWfjXodGwOsOsV8ZAXYgWiazs0fnI HlZPIGkczVG5jnhwhWv3kK66tuhFwQNwKqd7q8cVD79CIB7gXbajQTtzezSBHBXXR9WigtLCbVct I3ToUedoxh//899G1PuPfz+l9wfIblKcLtR5q3KyYj9TfzI+zMKcqKPt3eFIwUUWwG5RQAAgV1KQ S/E62bIjOe2gq781uXG0G4V+ZOb9kdHOzLP+2dXoz/QWXtOa0Ol0a2aUbuvIzIczo2c/z5j5OQ3N 30BD4x+i4d32+G2nKev5sdWO1d0bbafu+VCoGoDgcW3HudyqSzSiI3WHUQ6PeDZmPqHuJ6c21NQd srtt2/zNp+6XJVcY4EhsmUJ8VAQeR4Law8bBuA2gEUJUwEmRpp/km3+Oz6jy8jakCwYThuM4gs9Z O4bZ5EIG9HKf72FtrSuA6ienfHaELkh1sOospadRC3JaPF1rmRal0ULYmy2OKVmKFqYD+soMykz6 jrIOZTa9eDT9HNO3TbPjGs6z8zumC/TMCnx2PoPn+5LyBBN4QZrEG13jbVrIG6brURpvOVDvKbjx WciJqV3lG9VDp3y4wWMHQkYg6a232ZfNdbLm4ro9adxVT3WeWFXPfhAwHbrWTAWca5iorNxZNtGg Y1tq6MfTnNvYJrKyaj5Jzar66P0iEF1BzW0YTv3QoHIbB0dktL5h0PgUNdUCdmC3xZyjJPhFfAU2 C32m6kgs07HdBt1DTUs4JjwNrZCCDzrThGj5qN2gorWAURecd/VH3lt6GbyhFDvvFQfvFcp77Z3X Z17OB0iCj2SaRbnZfnHyYDku/TgdzKbT90c0fpbdBF5UwACeh8ZOhGHNcutHFJ4qdzdeEPAB+jNE v0pMlMGNElQ4D+iqZhtt64Ac212GgdituiYlWhg0N4DFKN2i+7dmSd2W2W11u/zVowd/O0XQoUYu yzLrtVpINAh6fVGEvp54hacv0ruWOtpvVViraO1lLstVfDwD/ekYhyG6/sQQQLQMA8blxBeFEWwz 31A/CXK5oWudZt5d6i9vgTa/K7z77/G/XtzrKKZ6sXihjj7ScolZP4vpbGA6WS6xa/yVS+QCODkt 9ctFOLSgIY1YUiL58F30LNGzRz1cDNyei2aavxfZdmLtCiNQl4vHpfSlwpiMY5vrDNu8IPkQFQDG zWZ1UMC+fo+Osunl1dEO0WnKpy0woFzN4w26d7vtOE2jA9HT3fe4bMBtOmLwDGzWo8u/tDsal8jq 7CxCtslDDl9uZatldWj66q/0jcHTvOTzXogqZBw2+QQTqYonVTpsz0iAlptbuPwkGR9I5tyE5XKB ZXFcPUnH/Z5K0Wjxf0pBNfEg2mG7Y7jz+pMbxztUbRB56L/uPHWcXh2Ubvhbmv0XOGhAZJF8W+4O dpEEolI24RXobbDZv4xJ5QQ+dIzlzm/wn43iVVPZodfv2XU+dUILISanraI63VSJpmZUo68+NNCp hXymYHT4u555VNYfpZ3tGTwVC+OJulllns428zSoOre1npVhPiHDeEbGO/5OMfX4ZQGP2+tVGqxj qR8VGq4VlKSJcmA43OFU9zt1lm+Zorm9sF78y8kLlzdw2ChERka15VSHJvuB1JcYhTo/Cr0oxlgD HuyfwAwyz9P8BN3gEatt+EI8eHwG6Qe5aTWl0fJuy7VEL9IM4PXJsxKt/y+JP3d5v3fL/d7l/Tae 9a/Eaht90+0bLStsmk63/Tz7szHzx+b/FVsHQCJXMm55cbzARZRIfhmIk8U/PE98Zf3K+pX1K+tX 1t8N632UzNG0tXQZr74W4S/g/71jyd+7vH+6x/9zWIssKj8s07yVFCuQ/0ux/4ptW6ZyEbf0RJaF z+e1v4z9wVuXyz+Gn3xl/cr6h2SNkjsvjgJKQewlQfXXKfvXh4U24vdb+EoYovfjd74w2m3PaL94 r43OzvsvZ8xg8ntmtia9h8Mft4BFznEfdA1D+FLd+3wvLbcr/TbfB4reYAqhySL6mDrY3Yvqfp59 fF9ke2m+FhRKlKse7C+L7eXuLx8oCYuAahm/HuAIp0FF6fm3/ELmiZIEvdUXZPzGXqg+0jvohLU7 Fi4PI9u1WiQ6wrIMR1Y0bdc+aLp7SWRPG0jHmWM3qW1vt6oaURdQImz7JEPHbXvViMN/m7RVx/Uf y9uq5YTtisnld7h32jz7erdxmJP/diKmq9zzZY+UgdUiX7zf3WA1hxvMs78xgk7ncOOEFm5YOx4w Pa/juYenHd/Y3YiO7cyZVBuod/JESGJOofqJawA6X5CrfuIWF0xgkFKe3IAci0xBVpcvNNL+D1BL AwQUAAIACAAgcOoquaa8llUGAABbLwAAEQAAAGxpbnV4LW1lcy0yNDUudHh07Vptb9s2EP6+X8Fv S5DE4pveiCZA0a1bigLtlg4oEAQGLdGJFlnSKDlL9ut3lOzYahNTbugiBSIEDknxnud4dzxRpN7N c4QihLnAVGCCknLWqARzVN/VeXmZIjLiR1ggrepG6mb007tnKhAjHAqChb8moKtkNCvnRZMKJOfN lSqaLJGNSlHbCgj/zAEETXU5QySmIxJEIz4iNBJhGKJpqZGXykZ6VZOgvba4j3ZDF+E1OqmTq+xm 14xkjXFeK10/RMiAMHRAGIBFI7tFHdL1xve4RV0y0kEW9QVlDgjDgRZ1RzfUog4ZB1nUxzAvHBD6 YFHfblGXdNEgi7pkjAdZlAjqrwivlS5ULtD0anyjdDa9E6gV9dRcq1tUKT3L6jorCzSVWQ5th0gm yTE5RErrUh8Tdo8dCRII6mLCcRgMs3nLLR0f4C23jL7dW0AYCk535C0G8NRR6AV2bxk6F7njy0h/ 3FsOGXvP8Ee8FQMbZMjvla3c0g3JVm4Z7dnKrIiw4NHaMnG+V8nZeF5kt/vnhDMaXAhUqy7ky0oV QG1QDR7SZdmgyR2SRaqVrPfmWXpMMd9fhye9CNkIn+Rl/SV8H4rxx6HC+ImaMoHxLhKBweaCbjBy T/WNViDCzDq2EzXhsUWEH+8IG5aKfLPeAXlNo9fEY9MjGsb8cXw2hCCXMC1mYFN5qWCaVKqdNQw1 GTSuiwXwzHEw4agIA1tGcUwX2DOKY8bQnlFgFjHByU6iCLADwYON2JM8UzOVezLPL6GQFeqokROV 56p4lOuhgII8THc100yOB3hbsMLaoR+t8FIf9haz28jRzWP5NysmKrn2RiqfbTWYIeBPmtpfEdin NtgIU+EHvQfGrEwrXU6UWCu9kcXPDcpLMwNM8zxXEEFlcn00k3+X+ojS543H2DPH498PLytqkBDI y7OJ18nWHoXc5R/hER3F47PfTsef356NKcYEB4R5XaR6qc5uzERuibzbdFQKAMuacQci0AeIV9mY aC1gGdEGbwMhZ1fl96xoxKLWBXaNElmgiYJ/c/OYhzVJViSl1ipplgOupJYz1YBKh+ZmPk+z4hJK NzLPUnT6AUEOPv3zj7V+380o7UDWHQKLOzODhxjjxS/Pyy/LPP35F4HelzKFUcsaycVoR3bBT/rO GKApYbGgFPigULdZ3ah2FVGXc50o9Aqbi1F8tCiwkx9Jo+eQ41+eGbvDe34R95ItX7LlS6T8QJEC 7ybw52Kb13rMt6Jzsek65JjPPaPlUKojZExwF6cA1k0Z93S2TRn3jJZNmQUhFyRyQGg9OHVONzBG XTIOi1EuKHdAaD2Kc09nO4pzz2g5ilsQ+oKFXz84n7jhZrDNMVVvB353H7c4p7N+3OKe0fJxCxAS LCgWxP02r8EmgsS9g1PX2CzaHTbffIZUV1nz31WpPVhaAN6W+Mbma7o/vBFK+xuhnRjdbM4nq2XB /3aTGuzN7roq1WXujQrV1Ims1K7wb8002h78oVcBN4YJBN6V0Tlk4u2OGYwcM2dND2Xw5VK+NO8V BWQk83JjF3vz8S+B4BrQ9dfTj11XWNSL87SaNwcUe4zQi21lXyWYcC4JPxki+vb969/OzHgowZQH dgklb7vhmwtI1QTqaUwITlRbT0xdsShWCTf1tO1PTI8BdlB11odLl3Xc1SdVv15X93SJHT6tW2Wi VvK+WC+KdvmPukwgjFAxrVO0V2UQCiEOD1HdyOS6gug6bnUB0+zbwc6MEAR8eym5GjZ4MGRQXLUs 7M0Q9jFjJFRdHx4FK2PYCRfXPViqwnACQYN4sPBn19IWYBhTniA1DSMuu5YwMbc6faNka8LFwMIp 71AjaLkfz32fLwtkpdSAGSfzHH3SMlECnRsnjadZkcJ7NywfDiihHqX4Ap2bxjEkmhSa9d2B72MP 1DE3lsnnwI+wR3AcXCxwKvD8+FI1smn0AeG+R3y6vJdmdSWb5AqmLPNYAAxbavpq6fGTi2UFXLuq gMnuKyT1/VUlnLKTIXRwndc3STsMCOCDIOIeYe2YzRAOWBB7ITXVTmLcXGklod33TKdhBKASldKX 0Uo/PyHLCvaDcDJI2QHWK1OwG54iPIF4NL9QjuFJhVHU/kIVCqYDQW0soShF8JpCMWKxKaxx+FHv I+D+xy1RhNm3fJfzP1BLAQIUABQAAgAIABZw6ir2XuJiKxEAAOk3AAATAAAAAAAAAAAAIAAAAAAA AABsaW5peC0yNDUtZG1lc2cudHh0UEsBAhQAFAACAAgAIHDqKrmmvJZVBgAAWy8AABEAAAAAAAAA AAAgAAAAXBEAAGxpbnV4LW1lcy0yNDUudHh0UEsFBgAAAAACAAIAgAAAAOAXAAAAAA== ------_=_NextPart_000_01C10953.960B40E0-- From owner-linux-xfs@oss.sgi.com Tue Jul 10 08:33:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AFXOl28457 for linux-xfs-outgoing; Tue, 10 Jul 2001 08:33:24 -0700 Received: from nbd.it.uc3m.es (nbd.it.uc3m.es [163.117.139.192]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AFXLV28454 for ; Tue, 10 Jul 2001 08:33:22 -0700 Received: (from ptb@localhost) by nbd.it.uc3m.es (8.9.3/8.9.3/Debian 8.9.3-6) id RAA05803; Tue, 10 Jul 2001 17:32:39 +0200 From: "Peter T. Breuer" Message-Id: <200107101532.RAA05803@nbd.it.uc3m.es> Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 In-Reply-To: <4.3.2.7.2.20010710164832.03481e90@pop.xs4all.nl> from "Seth Mos" at "Jul 10, 2001 04:50:09 pm" To: "Seth Mos" Date: Tue, 10 Jul 2001 17:32:39 +0200 (CEST) CC: ptb@it.uc3m.es, linux-xfs@oss.sgi.com X-Anonymously-To: Reply-To: ptb@it.uc3m.es X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "A month of sundays ago Seth Mos wrote:" > At 16:21 10-7-2001 +0200, Peter T. Breuer wrote: > >The 2.4.6 patch didn't apply cleanly to a pure kernel source .. > > linux-2.4.6-xfs-cvs-06212001.patch > > This was a snapshot of the CVS tree in between -pre merging. > It was never really tested that much AFAIK. Thanks. Where can I get hold of a clean patch for 2.4.6? I believe I saw some traffic on that recently, but didn't save the messages. The official site has: Current directory is /projects/xfs/download/patches Jul 5 12:11 text/plain MD5SUM 415 bytes Jun 9 17:08 text/plain README 439 bytes Jun 4 07:11 bzip2 linux-2.4.5-xfs-06042001.patch.bz2 816Kb Jun 4 07:11 GNU Compressed linux-2.4.5-xfs-06042001.patch.gz 1053Kb Jun 11 08:15 bzip2 linux-2.4.5-xfs-06112001.patch.bz2 816Kb Jun 11 08:15 GNU Compressed linux-2.4.5-xfs-06112001.patch.gz 1053Kb Jul 4 22:05 bzip2 linux-2.4.6-xfs-07052001.patch.bz2 817Kb Jul 5 12:10 GNU Compressed linux-2.4.7-xfs-cvs-07052001.patch.gz 2888Kb and as you see, there is hobson's choice here. Sgi's site is certainly not easy to search for this info .. I could find nothing else on the site that was not aimed at 2.4.2 or 2.4.3. The FAQ is wrong: There exists also another way to get an XFS ready kernel - you may get kernel patches relative to a official kernel from: ftp://oss.sgi.com/projects/xfs/download/ and apply then to the kernel sources the patch is for. This is a good way for all the people who don't want to use CVS or do not have the bandwidth to checkout the whole kernel tree. The patch doesn't work well .. and is unsuitable for application to a pure kernel tree anyway, as it contains the cmd stuff and is against cvs. > > >can't find a likely referant for the failed block. And in any case > >compilation of the result fails in aic7xxx! > > See FAQ. This is not related to the XFS patch. Well, I recall something about that too in recent list traffic, but didn't pay too much attention at the time. I don't mind whether I use the new or old aic7xxx driver, personally. > > >So I would guess random other patches have been applied. Fair 'nuff. > >Just give me a clue what they are! Moving the 2.4.5 aic7xxx_reg.h > >across almost does the trick, but not quite. aic7xxx_seq.h is also > >needed. That seems to fix it. But what happened? > > The FAQ has a nic entry for this. I can't find anything related to any of the problems I noted in the FAQ. Which section did you have in mind? There is a mention of the aic7xxx driver but not in connection with the problem I noted. Q: The Adaptec aic7xxx does not compile. It spits out the following error during compile gcc -I/usr/include -ldb1 aicasm_gram.c aicasm_scan.c aicasm.c aicasm_symbol.c -o aicasm aicasm_symbol.c:39: db1/db.h: No such file or directory make[5]: *** [aicasm] Error 1 The Adaptec driver in newer 2.4.2 kernels and later need to have the db headers. These can be found in the db-devel packages. As I mentioned, it compiled fine once I put in a couple of aic7xxx_FOO.h files that should have been there already. Without looking at the patch in detail, I would guess that the patch is against a kernel with a new aic7xxx driver patch applied, and somehow the patch has zeroed a couple of headers that it should have left in place? After slight mending I got a clean kernel compile (still had to fix a couple of things, but not much). However, building xfs as a module failed in page_buffer for lack of definitions of things like SLAB_IO. The basic problem seems to be that the patches are made against CVS. Is there a clean patch that I should be applying? I'll try patching up my existing 2.4.5 tree with the 2.4.6 increment, but I really wanted xfs improvements too. Peter From owner-linux-xfs@oss.sgi.com Tue Jul 10 08:57:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AFvJ929038 for linux-xfs-outgoing; Tue, 10 Jul 2001 08:57:19 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AFvIV29035 for ; Tue, 10 Jul 2001 08:57:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA01394 for ; Tue, 10 Jul 2001 08:54:43 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA1797728; Tue, 10 Jul 2001 10:56:01 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA96374; Tue, 10 Jul 2001 10:56:01 -0500 (CDT) Message-ID: <3B4B25CB.284B7822@sgi.com> Date: Tue, 10 Jul 2001 10:56:59 -0500 From: sandeen@sgi.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: ptb@it.uc3m.es CC: Seth Mos , linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 References: <200107101532.RAA05803@nbd.it.uc3m.es> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Peter T. Breuer" wrote: > Where can I get hold of a clean patch for 2.4.6? > > Current directory is /projects/xfs/download/patches > > Jul 5 12:11 text/plain MD5SUM 415 bytes > Jun 9 17:08 text/plain README 439 bytes > Jun 4 07:11 bzip2 linux-2.4.5-xfs-06042001.patch.bz2 816Kb > Jun 4 07:11 GNU Compressed linux-2.4.5-xfs-06042001.patch.gz 1053Kb > Jun 11 08:15 bzip2 linux-2.4.5-xfs-06112001.patch.bz2 816Kb > Jun 11 08:15 GNU Compressed linux-2.4.5-xfs-06112001.patch.gz 1053Kb > Jul 4 22:05 bzip2 linux-2.4.6-xfs-07052001.patch.bz2 817Kb ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ^ here ^ > Sgi's site is certainly not easy to search for this info .. I could > find nothing else on the site that was not aimed at 2.4.2 or 2.4.3. 2.4.2/2.4.3 is what XFS 1.0 was released against, so there is a lot more detailed (and organized) information on those kernels. But I agree, things are a bit disorganized at the moment. -Eric From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:02:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AG2Jl29270 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:02:19 -0700 Received: from server1.metrolink.com (server1.metrolink.com [216.242.72.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AG2GV29267 for ; Tue, 10 Jul 2001 09:02:17 -0700 Subject: Re: kernel build issues From: Rob Lembree To: Steve Lord Cc: linux-xfs@oss.sgi.com In-Reply-To: <200106292022.f5TKMhP03536@jen.americas.sgi.com> References: <200106292022.f5TKMhP03536@jen.americas.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: 10 Jul 2001 12:01:59 -0400 Message-Id: <994780926.2159.11.camel@ripple.nh.metrolink.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 29 Jun 2001 15:22:43 -0500, Steve Lord wrote: > > Hi, can I suggest you get a newer set of rpms from oss.sgi.com, the latest > stuff is here: > > ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/ > > This does compile with the redhat compiler (although the binary rpms > are still compiled with kgcc), although we still have had > problem reports on some architectures. Redhat did put out a newer > compiler last week which appeared to fix some peoples issues. Sorry it's taken a while, but here's a synopsis of what was going wrong. I erroneously made the assumption that RedHat 7.1 fixed the gcc kernel problems, but it didn't. Not only do you have to use kgcc on 7.0, but on 7.1 as well. Silly problem really. I did at one point switch to the kgcc, but didn't do a 'make mrproper', which did eventually make the difference. Thanks for the help, everyone who responded. > Steve > > > This is a multi-part message in MIME format. > > --------------6B9E4A412E0A6E5429BD992E > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > > > Hi there, > > I can't seem to build the XFS kernel properly > > on my RH 7.1 machine. > > > > When I can build the bzImage, I can't build the > > modules (it complains about hex values in the sources). > > > > When I adjust the compiler (using native gcc, not > > kgcc), the following build breakage happens. Do you have > > any reports of this, or workarounds to suggest? > > > > > > > > gcc -D__KERNEL__ -I/usr/src/linux-2.4/include -Wall -Wstrict-prototypes -O2 - > > fomit-frame-pointer -fno-strict-aliasing -Wno-unused -pipe -mpreferred-stack- > > boundary=2 -march=athlon -Wno-unused -Wno-parentheses -Wno-uninitialized - > > I. -I/usr/src/linux-2.4/fs -funsigned-char -Wno-unknown-pragmas -c -o xfs_b > > map.o xfs_bmap.c > > xfs_bmap.c:543:9: warning: pasting "." and "xs_add_exlist" does not give a va > > lid preprocessing token > > xfs_bmap.c:2830:9: warning: pasting "." and "xs_del_exlist" does not give a v > > alid preprocessing token > > xfs_bmap.c: In function `xfs_bmap_alloc': > > xfs_bmap.c:2721: Unrecognizable insn: > > (insn/i 137 3604 3598 (parallel[ > > (set (reg:SI 0 eax) > > (asm_operands ("") ("=a") 0[ > > (reg:DI 1 edx) > > ] > > [ > > (asm_input:DI ("A")) > > ] ("linux/xfs_linux.h") 287)) > > (set (reg:SI 1 edx) > > (asm_operands ("") ("=d") 1[ > > (reg:DI 1 edx) > > ] > > [ > > (asm_input:DI ("A")) > > ] ("linux/xfs_linux.h") 287)) > > (clobber (reg:QI 19 dirflag)) > > (clobber (reg:QI 18 fpsr)) > > (clobber (reg:QI 17 flags)) > > ] ) -1 (nil) > > (nil)) > > xfs_bmap.c:2721: confused by earlier errors, bailing out > > make[3]: *** [xfs_bmap.o] Error 2 > > make[3]: Leaving directory `/usr/src/linux-2.4.2/fs/xfs' > > make[2]: *** [first_rule] Error 2 > > make[2]: Leaving directory `/usr/src/linux-2.4.2/fs/xfs' > > make[1]: *** [_subdir_xfs] Error 2 > > make[1]: Leaving directory `/usr/src/linux-2.4.2/fs' > > make: *** [_dir_fs] Error 2 > > > > > > -- > > > > Rob Lembree Metro Link Incorporated > > 29 Milk St. lembree@metrolink.com > > Nashua, NH 03064-1651 http://www.metrolink.com > > Phone: 954.660.2460 Alternate: 603.577.9714 > > PGP: 1F EE F8 58 30 F1 B1 20 C5 4F 12 21 AD 0D 6B 29 > > --------------6B9E4A412E0A6E5429BD992E > > Content-Type: text/x-vcard; charset=us-ascii; > > name="lembree.vcf" > > Content-Transfer-Encoding: 7bit > > Content-Description: Card for Rob Lembree > > Content-Disposition: attachment; > > filename="lembree.vcf" > > > > begin:vcard > > n:Lembree;Robert > > tel;cell:603-494-0559 > > tel;fax:603-577-9714 > > tel;home:603-880-6768 > > tel;work:954-660-2460 > > x-mozilla-html:TRUE > > url:http://www.lembree.com/rob/ > > org:Metro Link, Inc.;Automation Technology Division > > adr:;;29 Milk St.;Nashua;NH;03064-1651;US > > version:2.1 > > email;internet:lembree@metrolink.com > > title:Technical Director > > note:PGP: 1F EE F8 58 30 F1 B1 20 C5 4F 12 21 AD 0D 6B 29 > > x-mozilla-cpt:;-31136 > > fn:Robert Lembree > > end:vcard > > > > --------------6B9E4A412E0A6E5429BD992E-- > -- Rob Lembree Metro Link Incorporated 29 Milk St. lembree@metrolink.com Nashua, NH 03064-1651 http://www.metrolink.com Phone: 954.660.2460 Alternate: 603.577.9714 PGP: 1F EE F8 58 30 F1 B1 20 C5 4F 12 21 AD 0D 6B 29 From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:11:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGB5S29581 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:11:05 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGB3V29578 for ; Tue, 10 Jul 2001 09:11:03 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA03172 for ; Tue, 10 Jul 2001 09:08:28 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2393651; Tue, 10 Jul 2001 11:09:45 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA71706; Tue, 10 Jul 2001 11:09:45 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6AGAxu21955; Tue, 10 Jul 2001 11:10:59 -0500 Message-Id: <200107101610.f6AGAxu21955@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: ptb@it.uc3m.es cc: "Seth Mos" , linux-xfs@oss.sgi.com Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 In-Reply-To: Message from "Peter T. Breuer" of "Tue, 10 Jul 2001 17:32:39 +0200." <200107101532.RAA05803@nbd.it.uc3m.es> Date: Tue, 10 Jul 2001 11:10:59 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just to add to Eric's comments > "A month of sundays ago Seth Mos wrote:" > > At 16:21 10-7-2001 +0200, Peter T. Breuer wrote: > > >The 2.4.6 patch didn't apply cleanly to a pure kernel source .. > > > > linux-2.4.6-xfs-cvs-06212001.patch > > > > This was a snapshot of the CVS tree in between -pre merging. > > It was never really tested that much AFAIK. > > Thanks. Where can I get hold of a clean patch for 2.4.6? I believe I > saw some traffic on that recently, but didn't save the messages. The > official site has: > > Current directory is /projects/xfs/download/patches > > Jul 5 12:11 text/plain MD5SUM 415 bytes > Jun 9 17:08 text/plain README 439 bytes > Jun 4 07:11 bzip2 linux-2.4.5-xfs-06042001.patch.bz2 816Kb > Jun 4 07:11 GNU Compressed linux-2.4.5-xfs-06042001.patch.gz 1053Kb > Jun 11 08:15 bzip2 linux-2.4.5-xfs-06112001.patch.bz2 816Kb > Jun 11 08:15 GNU Compressed linux-2.4.5-xfs-06112001.patch.gz 1053Kb > Jul 4 22:05 bzip2 linux-2.4.6-xfs-07052001.patch.bz2 817Kb ^^^^^^^^^^^^ Try this one, it applies cleanly and builds without problem for me, including the new aic driver and xfs as a module. > Jul 5 12:10 GNU Compressed linux-2.4.7-xfs-cvs-07052001.patch.gz 2888Kb > > > and as you see, there is hobson's choice here. And the README file says: linux-2.4.x-xfs-cvs-.patch.gz CVS seed patch: patch a vanilla linux 2.4.x tree to a "cvs update -d" capable tree. Do not use this patch unless you are willing stay up-to-date with "current". linux-2.4.x-xfs-.patch.gz linux-2.4.x-xfs-.patch.bz2 Patches to take a vanilla linux 2.4.x tree to an xfs capable kernel. Note that these are kernel only patches, command source can be obtained from the cmd_tars directory. Seems clean enough to me. There is currently no vanilla patch against 2.4.7-prex since it moves too fast, pre4 and pre5 came out within the last 24 hours. Generating patches against all sorts of kernel version every time we change xfs is a time consuming operation, we are working towards having a setup where we can offer a wider variety of options kept upto date. > > Sgi's site is certainly not easy to search for this info .. I could > find nothing else on the site that was not aimed at 2.4.2 or 2.4.3. > > The FAQ is wrong: > > There exists also another way to get an XFS ready kernel - you may get > kernel patches relative to a official kernel from: > ftp://oss.sgi.com/projects/xfs/download/ > > and apply then to the kernel sources the patch is for. This is a good > way for all the people who don't want to use CVS or do not have the > bandwidth to checkout the whole kernel tree. > > The patch doesn't work well .. and is unsuitable for application to a pure > kernel tree anyway, as it contains the cmd stuff and is against cvs. The linux-xfs patches are pure kernel patches, the cvs ones contain other information. The FAQ is correct, and the README file contains a description of what the various patches are. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:13:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGDjD29706 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:13:45 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGDiV29703 for ; Tue, 10 Jul 2001 09:13:44 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA10852 for ; Tue, 10 Jul 2001 09:13:35 -0700 (PDT) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2360095; Tue, 10 Jul 2001 11:12:27 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA14370; Tue, 10 Jul 2001 11:12:27 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id LAA22148; Tue, 10 Jul 2001 11:12:26 -0500 (CDT) Message-Id: <200107101612.LAA22148@slobber.americas.sgi.com> To: "linux-xfs@oss.sgi.com" cc: openxdsm-devel@lists.sourceforge.net Subject: Re: DMAPI and dump/restore Date: Tue, 10 Jul 2001 11:12:26 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: Timothy Shimmin >Hi James, > >On Mon, Jul 09, 2001 at 10:05:37AM -0500, James A Goodwin wrote: >> Does anyone know the extent to which DMAPI information is handled by >> xfsdump/xfsrestore? There are two things that worry me: >> >> 1. Are xfsdump/xfsrestore smart enough to realize when data is not resident >> on XFS disks? In other words, the data has been migrated by the DMAPI >> client, and dm_puch_hole() was used to free up the XFS disk resources. >> When doing a dump, I'd rather have xfsdump note that there is a hole rather >> than dredging all the migrated data back up through the DMAPI. >> >> The xfsdump man page mentions a "-a" option for >> working with DMF that sounds a lot like an answer to #1, but I'd be >> surprised if there was any relationship between DMF and DMAPI. xfsdump has to know how to unpack DMF's extended attributes so it can figure out if the file is online or offline, and do the intelligent thing when doing the backup. Other HSM's pack their extended attributes in different ways, and the XDSM (DMAPI) spec doesn't say the attributes have to be structured any particular way. Our DMAPI--and our HSM--does not yet support multiple managed regions, so xfsdump just has to figure out if the file, as a whole, is online or offline. So when you're reading xfsdump/restore code you're not going to find the stuff that punches holes whereever there's an offline region. So if you're on Irix and using an HSM other than DMF on an XFS filesystem then xfsdump is not going to do the right thing. >I'm not that "au fait" with DMAPI stuff - Dean (roehrich@sgi.com) >would be the one with answers to such questions :) > >However, >the "-a" option is used to dump DMF dual-state and unmigrating >files as offline (so no data is dumped). >Looking at the code, > - its extent data will be dumped as 1 extent with a hole > (so the data aint dumped) > - its DMF attributes won't be dumped but a replacement DMF attribute > (i.e. DMF_ST_OFFLINE) will be dumped in its place > - the stat buf's bs_devmask will be or'ed with DM_EVENT_READ > >(I don't know if this is enought for all DMAPI users or just DMF ?) It's not enough--other HSM's won't use the same DMF_ST_* values and they won't use the same format we have defined in XFSattrvalue1_t. The comments and symbol names early in dump/hsmapi.c make it clear this stuff is not expected to satisfy any other HSM. >> 2. What do xfsdump/xfsrestore do with DM attributes, regions, and event >> lists? Are they stored, ignored, or something else? >> >I presumed all the DMAPI event stuff and other related data is >in extended attributes. And all the extended attributes are >dumped out (unless the -A option is used). A couple of masks are in the inode: io_dmevmask/di_dmevmask and io_dmstate/di_dmstate. Any HSM using our DMAPI will rely on dmevmask and will build with /usr/include/xfs/dmapi.h to get the mask bits. The dmstate field is not used and the purpose for its presence in our inode, and any possible meaning it may have, is a piece of lost history. It's not part of the DMAPI spec. However, it's a couple of bits we own in the inode and we're reserving them. I noticed that on the Linux side xfsdump sets it to zero--the Irix xfsdump doesn't touch it. The confusion is not surprising, I guess. The rest of the information, as far as offline/online, region info...is in the extended attribute and so would be HSM-specific. This attribute is also given an HSM-specific name. >Hmmmm....xfsrestore takes the -D option to restore DMAPI event >settings. If F_FSSETDM macro is set then it uses fcntl(F_FSSETDM). >All this code is #ifdef'ed out by the macro F_FSSETDM. >This doesn't seem to be turned on in IRIX or Linux. >Dean, is it not necessary to call fcntl(F_FSSETDM) ? It is turned on in Irix. The makefile defines BANYAN unconditionally (found only in the Irix-side code), and F_FSSETDM is defined in --so that code is enabled on Irix. The stuff inside the #ifdef F_FSSETDM will have to be ported to use the XFS_IOC_FSSETDM ioctl on Linux. (I'm copying this to the openxdsm-devel mailing list...just in case anyone there is still alive.) Dean From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:15:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGFup29820 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:15:56 -0700 Received: from nbd.it.uc3m.es (nbd.it.uc3m.es [163.117.139.192]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGFrV29817 for ; Tue, 10 Jul 2001 09:15:54 -0700 Received: (from ptb@localhost) by nbd.it.uc3m.es (8.9.3/8.9.3/Debian 8.9.3-6) id SAA08092; Tue, 10 Jul 2001 18:14:36 +0200 From: "Peter T. Breuer" Message-Id: <200107101614.SAA08092@nbd.it.uc3m.es> Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 In-Reply-To: <3B4B25CB.284B7822@sgi.com> from "sandeen@sgi.com" at "Jul 10, 2001 10:56:59 am" To: sandeen@sgi.com Date: Tue, 10 Jul 2001 18:14:36 +0200 (CEST) CC: ptb@it.uc3m.es, "Seth Mos" , linux-xfs@oss.sgi.com X-Anonymously-To: Reply-To: ptb@it.uc3m.es X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "A month of sundays ago sandeen@sgi.com wrote:" > "Peter T. Breuer" wrote: > > Where can I get hold of a clean patch for 2.4.6? > > Current directory is /projects/xfs/download/patches > > > > Jun 11 08:15 GNU Compressed linux-2.4.5-xfs-06112001.patch.gz 1053Kb > > Jul 4 22:05 bzip2 linux-2.4.6-xfs-07052001.patch.bz2 817Kb > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ^ here ^ Yo! That's the one. Thanks! For some reason the german mirror (which I chose originally) has more patches, and includes cvs and non-cvs patches among them, and somehow I didn't notice the alternative to the 2.4.6 patch thanks to my lynx's fancy blue links on black bg color scheme .. ftp://ftp.mpg.goe.ni.schule.de/pub/linux/kernel/xfs/sgi .... Jun 4 14:11 GNU Compressed linux-2.4.5-xfs-06042001.patch.gz 1053Kb Jun 11 15:15 bzip2 linux-2.4.5-xfs-06112001.patch.bz2 816Kb Jun 11 15:15 GNU Compressed linux-2.4.5-xfs-06112001.patch.gz 1053Kb Jun 1 00:01 GNU Compressed linux-2.4.5-xfs-cvs-05312001.patch.gz 2834Kb Jul 5 05:05 bzip2 linux-2.4.6-xfs-07052001.patch.bz2 817Kb Jun 21 18:43 GNU Compressed linux-2.4.6-xfs-cvs-06212001.patch.gz 2956Kb Jul 5 19:10 GNU Compressed linux-2.4.7-xfs-cvs-07052001.patch.gz 2888Kb Aaaah, it's so easy to read now in white letters on a dark bg! > Thanks again. This saves me at least the next hour's patch hacking. Yep, now I recall that the 0705 patch has been mentioned recently. See, you really ought to use a 20010705-cvs name, just to get a nice ordering in listings :-). Petre From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:18:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGINu29952 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:18:23 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGIMV29949 for ; Tue, 10 Jul 2001 09:18:22 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA05047 for ; Tue, 10 Jul 2001 09:18:23 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2280900; Tue, 10 Jul 2001 11:17:04 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA52000; Tue, 10 Jul 2001 11:17:04 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6AGIHO21980; Tue, 10 Jul 2001 11:18:17 -0500 Message-Id: <200107101618.f6AGIHO21980@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Huettner, Ewald" cc: "'linux-xfs@oss.sgi.com'" Subject: Re: FW: nfsd-crash In-Reply-To: Message from "Huettner, Ewald" of "Tue, 10 Jul 2001 17:18:34 +0200." <5243EBD6FB48D51184E200A0C9A9D56014543C@srvellwangen.rand.de> Date: Tue, 10 Jul 2001 11:18:17 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hallo, > i have a Problem at an Customer, he has an lh3000 (HP) with Redhat Linux > 7.1 and XFS 1.0 > Kernerl 2.4.5 Hmm, XFS 1.0 was not released against a 2.4.5 kernel, so I am presuming this is a kernel you rebuilt yourself. For a more recent kernel which I think will fix this problem take a look here: ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/RPMS/linux-2.4.5/ This will probably turn into a real 1.0.1 release within a day or so. The stack trace does look familiar, but it is a long time since a fix was made in this area so my memory is hazy on that point. Steve > > The Server runs some time and then the nfsd crash`s down with errors in > messages. The nfsd can not be restartet at the system, only reboot and > reset ist ok too restart the server and the nfsd. On this Server there > are 8 HP-UX Workstations with NFS > connectet to the Linux Server. > At the Server there are the following filesystems: > / ext2 > /boot ext2 > /data xfs > > > Has anyone an workaround for this Problem???? > > Ewald Huettner > email: ehuettner@rand.de > Phone: 07961890186 > From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:20:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGK7B30069 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:20:07 -0700 Received: from woody.fsl.noaa.gov (IDENT:root@woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGK6V30066 for ; Tue, 10 Jul 2001 09:20:06 -0700 Received: (from tierney@localhost) by woody.fsl.noaa.gov (8.9.3/8.9.3) id KAA11818; Tue, 10 Jul 2001 10:22:24 -0600 Date: Tue, 10 Jul 2001 10:22:24 -0600 From: Craig Tierney To: "Martin K. Petersen" Cc: linux-xfs@oss.sgi.com Subject: Re: Problem with lvm in 2.4.6 and xfs Message-ID: <20010710102224.F11724@hpti.com> References: <20010709174139.B11071@hpti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: ; from mkp@linuxcare.com on Mon, Jul 09, 2001 at 10:36:10PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This bug didn't produce a hang perse. I would get the error from before, and the box would continue to operate. The next time I would try to access any of the fibre channel luns then things would start to hang (the window) because all the processes would get stuck in diskwait. Rebooting was the only solution to clean this up. Here is the result from the change you requested. __make_request: rw = 2068549824 Craig On Mon, Jul 09, 2001 at 10:36:10PM -0400, Martin K. Petersen wrote: > >>>>> "Craig" == Craig Tierney writes: > > Craig> kernel BUG at ll_rw_blk.c:691! > > Now, that is really, really odd. > > Could you try and add > > printk ("__make_request: rw = %d\n", rw); > > before BUG() (ll_rw_blk.c, line 691), reproduce the hang, and mail me > the resulting output? > > > I'm currently Alphally challenged as Compaq called my loaner boxes > back so I can't check myself :| > > -- > Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. > mkp@linuxcare.com, http://www.linuxcare.com/ > SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ -- Craig Tierney (ctierney@hpti.com) phone: 303-497-3112 From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:22:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGMu030226 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:22:56 -0700 Received: from nbd.it.uc3m.es (nbd.it.uc3m.es [163.117.139.192]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGMsV30223 for ; Tue, 10 Jul 2001 09:22:54 -0700 Received: (from ptb@localhost) by nbd.it.uc3m.es (8.9.3/8.9.3/Debian 8.9.3-6) id SAA08518; Tue, 10 Jul 2001 18:22:45 +0200 From: "Peter T. Breuer" Message-Id: <200107101622.SAA08518@nbd.it.uc3m.es> Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 In-Reply-To: <200107101610.f6AGAxu21955@jen.americas.sgi.com> from "Steve Lord" at "Jul 10, 2001 11:10:59 am" To: "Steve Lord" Date: Tue, 10 Jul 2001 18:22:45 +0200 (CEST) CC: linux-xfs@oss.sgi.com X-Anonymously-To: Reply-To: ptb@it.uc3m.es X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Steve Lord wrote:" > The linux-xfs patches are pure kernel patches, the cvs ones contain other > information. The FAQ is correct, and the README file contains a description > of what the various patches are. OK, thanks! Turns out I couldn't see the -cvs- part of the name because my browser has chosen blue links on a black background. The -cvs- bit reverses the alphabetic and numerical ordering, so that linux-2.4.6-xfs-cvs-06212001.patch.gz is listed after linux-2.4.6-xfs-07052001.patch.bz2, and the only bit in readable white text is the "bzip2" file type at left in the listing, so I wrongly got the impression that the patch was a bzip version of the patch directly above it, which was a 2.4.5 patch. If that makes sense ... (listing suppresed). Peter From owner-linux-xfs@oss.sgi.com Tue Jul 10 09:48:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AGmJJ31058 for linux-xfs-outgoing; Tue, 10 Jul 2001 09:48:19 -0700 Received: from woody.fsl.noaa.gov (IDENT:root@woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AGmIV31054 for ; Tue, 10 Jul 2001 09:48:18 -0700 Received: (from tierney@localhost) by woody.fsl.noaa.gov (8.9.3/8.9.3) id KAA11841; Tue, 10 Jul 2001 10:50:28 -0600 Date: Tue, 10 Jul 2001 10:50:28 -0600 From: Craig Tierney To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: Problem with lvm in 2.4.6 and xfs Message-ID: <20010710105027.B11822@hpti.com> References: <200107100832.f6A8WrQ07640@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.6i In-Reply-To: <200107100832.f6A8WrQ07640@jen.americas.sgi.com>; from lord@sgi.com on Tue, Jul 10, 2001 at 03:32:53AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I put back the page_buf_io.c file without the nfs sparse file change, and I still get the problem. Craig On Tue, Jul 10, 2001 at 03:32:53AM -0500, Steve Lord wrote: > > This is actually probably caused by the nfs sparse file change, I will > be backing that code out and looking for a new solution to that particular > problem. Despite beating the code to death, it appears other peoples systems > can make this happen when mine cannot.... > > Steve > > > I am trying to create an lvm partition (of one device). > > I have done this before under x86, but I am trying this > > on Alpha. I can run mkfs -t xfs, but when I try and > > mount the filesystem I get the error below. > > > > Setup: > > > > XP1000, Qlogic FC2220 > > linux-2.4.6 with Tronds latest NFS patches > > linux-2.4.6-xfs-07052001.patch > > Qlogic 4.27Beta driver > > mount has been upgraded to 2.11.2 (linux-util-2.11.2) > > LVM is kernel lvm only (0.9.1-6). > > > > I also added just the patch from page_buf_io.c to help with > > sparse files, but I have the same problem without that patch. > > I did not update the LVM in the 2.4.6 kernel (as that messes > > up the xfs patch). > > > > I am running xfs+lvm successfully under x86 with the FC drive setup. > > > > kernel BUG at ll_rw_blk.c:691! > > mount(974): Kernel Bug 1 > > pc = [] ra = [] ps = 0000 > > v0 = 000000000000001f t0 = 0000000000000001 t1 = 0000000000000001 > > t2 = 0000000000000000 t3 = fffffc0066708000 t4 = fffffc0000624b20 > > t5 = fffffc0000654558 t6 = 0000000000000001 t7 = fffffc0066708000 > > a0 = 0000000000000000 a1 = 0000000000000001 a2 = 0000000000000001 > > a3 = fffffffffffffff9 a4 = 0000000000000002 a5 = 0000000000000000 > > t8 = 0000000000003fff t9 = fffffc0000659ba8 t10= 0000000000000006 > > t11= 000000000000000a pv = fffffc0000328820 at = fffffc0000653400 > > gp = fffffc00006485c0 sp = fffffc006670b5b8 > > Code: 225f02b3 lda a2,691(zero) > > a77dae78 ldq pv,-20872(gp) > > 6b5b77df jsr ra,(pv) > > 27ba001c ldah gp,28(ra) > > 23bda75c lda gp,-22692(gp) > > 00000081 call_pal 129 > > *c3e0025f br .+2432 > > 2fe00000 ldq_u zero,0(v0) > > > > Trace:48e974 340841 3d9c88 3d9f9c 3da510 3d9dc0 3da100 3d93dc 3d8994 451b34 4 > > 3c7c8 > > 446928 43be28 446824 446d3c 446db4 45b014 35ce50 3737d0 360504 35d1dc 35cdc8 > > 35d23c 35e1c4 35e170 35e668 35e770 35e750 310ae0 > > > > Craig > > > > -- > > Craig Tierney (ctierney@hpti.com) > > phone: 303-497-3112 > -- Craig Tierney (ctierney@hpti.com) phone: 303-497-3112 From owner-linux-xfs@oss.sgi.com Tue Jul 10 10:32:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AHWVF32333 for linux-xfs-outgoing; Tue, 10 Jul 2001 10:32:31 -0700 Received: from lott.kelman.com ([198.161.93.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AHWUV32330 for ; Tue, 10 Jul 2001 10:32:30 -0700 Received: from lorette.kelman.com (lorette [198.161.93.92]) by lott.kelman.com (8.9.3/8.9.3) with ESMTP id LAA24778 for ; Tue, 10 Jul 2001 11:33:10 -0600 (MDT) Received: from tux by lorette.kelman.com (8.8.8+Sun/SMI-SVR4) id LAA16943; Tue, 10 Jul 2001 11:31:44 -0600 (MDT) Date: Tue, 10 Jul 2001 11:30:57 -0600 (MDT) From: Michal Kozlowski X-Sender: michal@localhost.localdomain To: linux-xfs@oss.sgi.com Subject: Patch for linux 2.4.6-ac* series? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I was wondering if someone could provide some hints on creating a xfs patch for the 2.4.6-ac2 kernel. I know the SGI team doesn't support it since Alan can release way to many updates, but I'm willing to try and get the 2 going together. I want to try the hpt370 raid-0 with xfs on it. How much effort would something like this take? I've modified source code many times to get things working but never attempted something like this. Maybe if I get good at this I could release regular updates, but for now I just want 2.4.6-ac2 to work. Thanks for all you help, Cheers Mike Kozlowski 4th Year CPSC, University of Calgary, Calgary, Alberta, Canada From owner-linux-xfs@oss.sgi.com Tue Jul 10 11:26:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AIQah00866 for linux-xfs-outgoing; Tue, 10 Jul 2001 11:26:36 -0700 Received: from local.iboats.com (local.iboats.com [64.78.130.68]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AIQZV00863 for ; Tue, 10 Jul 2001 11:26:35 -0700 Received: (qmail 12145 invoked from network); 10 Jul 2001 12:26:31 -0600 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by local.iboats.com with SMTP; 10 Jul 2001 12:26:31 -0600 Message-ID: <003f01c1096d$840cc840$50824e40@iboats.com> From: "Steve Wolfe" To: Subject: Source for xfsprogs-devel? Date: Tue, 10 Jul 2001 12:24:09 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Is there a place where I may obtain the xfsprogs-devel package without having to use RPM? The machine I'm working on does not have a new enough RPM version, and it would be much easier for me if I didn't have to upgrade the multitude of packages that RPM 4 wants.... Since the source for the other utilities (xfsdump, etc.) seem to rely on xfsprogs-devel, I'm kind of stuck for the moment. steve From owner-linux-xfs@oss.sgi.com Tue Jul 10 11:28:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AISGo00978 for linux-xfs-outgoing; Tue, 10 Jul 2001 11:28:16 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AISFV00975 for ; Tue, 10 Jul 2001 11:28:15 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA05010 for ; Tue, 10 Jul 2001 11:25:39 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2394942; Tue, 10 Jul 2001 13:26:57 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA10898; Tue, 10 Jul 2001 13:26:57 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6AIS9q06607; Tue, 10 Jul 2001 13:28:09 -0500 Message-Id: <200107101828.f6AIS9q06607@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Michal Kozlowski cc: linux-xfs@oss.sgi.com Subject: Re: Patch for linux 2.4.6-ac* series? In-Reply-To: Message from Michal Kozlowski of "Tue, 10 Jul 2001 11:30:57 MDT." Date: Tue, 10 Jul 2001 13:28:09 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, I was wondering if someone could provide some hints on creating a xfs > patch for the 2.4.6-ac2 kernel. I know the SGI team doesn't support it > since Alan can release way to many updates, but I'm willing to try and get > the 2 going together. I want to try the hpt370 raid-0 with xfs on it. > How much effort would something like this take? I've modified source code > many times to get things working but never attempted something like this. > Maybe if I get good at this I could release regular updates, but for now I > just want 2.4.6-ac2 to work. Thanks for all you help, > > Cheers > Mike Kozlowski > > 4th Year CPSC, > University of Calgary, > Calgary, Alberta, Canada > Well, your best bet would be to take the base kernel from kernel.org, and then get the xfs patch from here: ftp://oss.sgi.com/projects/xfs/download/patches/linux-2.4.6-xfs-07052001.patch.bz2 Apply this patch, then remove kdb from the tree, this will be the hard part, there is a 2.4.6 kdb patch here: ftp://oss.sgi.com/projects/kdb/download/ix86/kdb-v1.8-2.4.6.gz it will leave some junk behind which you should probably clean up. Then attempt to apply Alan's patch on top of this, the combination of ac2 and kdb may be more than you want to attempt which is why I suggest removing it. An alternative would be to use the tree created by removing kdb to create an xfs without kdb patch for the Linus kernel, then apply the ac patch followed by the xfs patch. I am not sure which method will produce the cleanest tree. Good luck! Steve From owner-linux-xfs@oss.sgi.com Tue Jul 10 11:33:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AIXPe01177 for linux-xfs-outgoing; Tue, 10 Jul 2001 11:33:25 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AIXOV01167 for ; Tue, 10 Jul 2001 11:33:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA08558 for ; Tue, 10 Jul 2001 11:30:40 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2394442; Tue, 10 Jul 2001 13:29:37 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA22727; Tue, 10 Jul 2001 13:29:37 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6AIUnZ07115; Tue, 10 Jul 2001 13:30:49 -0500 Message-Id: <200107101830.f6AIUnZ07115@jen.americas.sgi.com> To: "Steve Wolfe" cc: linux-xfs@oss.sgi.com Subject: Re: Source for xfsprogs-devel? References: <003f01c1096d$840cc840$50824e40@iboats.com> Comments: In-reply-to "Steve Wolfe" message dated "Tue, 10 Jul 2001 12:24:09 -0600." Date: Tue, 10 Jul 2001 13:30:49 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Is there a place where I may obtain the xfsprogs-devel package without > having to use RPM? The machine I'm working on does not have a new enough > RPM version, and it would be much easier for me if I didn't have to > upgrade the multitude of packages that RPM 4 wants.... > > Since the source for the other utilities (xfsdump, etc.) seem to rely on > xfsprogs-devel, I'm kind of stuck for the moment. > > steve > Try here: ftp://oss.sgi.com/projects/xfs/download/testing/Release-1.0.1-PR3/cmd_tars/ Steve From owner-linux-xfs@oss.sgi.com Tue Jul 10 11:33:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AIXOM01172 for linux-xfs-outgoing; Tue, 10 Jul 2001 11:33:24 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AIXOV01165 for ; Tue, 10 Jul 2001 11:33:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA08212 for ; Tue, 10 Jul 2001 11:30:42 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2394269; Tue, 10 Jul 2001 13:30:27 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id NAA84929; Tue, 10 Jul 2001 13:30:27 -0500 (CDT) Message-ID: <3B4B49FD.17B68EB2@sgi.com> Date: Tue, 10 Jul 2001 13:31:25 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Wolfe CC: linux-xfs@oss.sgi.com Subject: Re: Source for xfsprogs-devel? References: <003f01c1096d$840cc840$50824e40@iboats.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Wolfe wrote: > > Is there a place where I may obtain the xfsprogs-devel package without > having to use RPM? The machine I'm working on does not have a new enough > RPM version, and it would be much easier for me if I didn't have to > upgrade the multitude of packages that RPM 4 wants.... Just install the xfsprogs tarball from ftp://oss.sgi.com/projects/xfs/download/cmd_tars/ ...It should have the header files that you need. -Eric From owner-linux-xfs@oss.sgi.com Tue Jul 10 11:48:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AImEF01569 for linux-xfs-outgoing; Tue, 10 Jul 2001 11:48:14 -0700 Received: from local.iboats.com (www.local.iboats.com [64.78.130.68]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AImDV01565 for ; Tue, 10 Jul 2001 11:48:13 -0700 Received: (qmail 16052 invoked from network); 10 Jul 2001 12:48:10 -0600 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by local.iboats.com with SMTP; 10 Jul 2001 12:48:10 -0600 Message-ID: <002301c10970$89d7e860$50824e40@iboats.com> From: "Steve Wolfe" To: References: <003f01c1096d$840cc840$50824e40@iboats.com> <3B4B49FD.17B68EB2@sgi.com> Subject: Re: Source for xfsprogs-devel? Date: Tue, 10 Jul 2001 12:45:47 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Is there a place where I may obtain the xfsprogs-devel package without > > having to use RPM? The machine I'm working on does not have a new enough > > RPM version, and it would be much easier for me if I didn't have to > > upgrade the multitude of packages that RPM 4 wants.... > > Just install the xfsprogs tarball from > > ftp://oss.sgi.com/projects/xfs/download/cmd_tars/ > > ...It should have the header files that you need. Oh, boy, do I have egg on my face. Steve Lord kindly pointed out that "make install-dev" will install the header files. I'll go stand in a corner for an hour..... steve From owner-linux-xfs@oss.sgi.com Tue Jul 10 12:35:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AJZFo03212 for linux-xfs-outgoing; Tue, 10 Jul 2001 12:35:15 -0700 Received: from otto.cfht.hawaii.edu (otto.colonization.com [128.171.80.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AJZ9V03193 for ; Tue, 10 Jul 2001 12:35:14 -0700 Received: (from isani@localhost) by otto.cfht.hawaii.edu (8.8.8/8.8.8) id JAA10379 for linux-xfs@oss.sgi.com; Tue, 10 Jul 2001 09:35:02 -1000 From: Sidik Isani Message-Id: <200107101935.JAA10379@otto.cfht.hawaii.edu> Subject: XFS mobile To: linux-xfs@oss.sgi.com Date: Tue, 10 Jul 2001 09:35:02 -1000 (HST) X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello - Not sure if SGI has much interest in this, but XFS is very impressive on *laptops*. The tricky part was getting root mounted with "noatime" so the disk doesn't spin up all the time. XFS didn't let me change noatime,osyncisdsync after the initial mount. And the kernel, even with the normal initrd tricks, only supports flags for ro/rw. Fortunately, the New Way using pivot_root provides a solution (but you must NOT name the linuxrc "/linuxrc".) The initial RAM disk contains my fstab and a script which checks to see what type of root filesystem is required, loads the modules (this works for NFS-root too) mounts root with all desired options, calls pivot_root and continues booting. All this actually works, and provided a test for these things: - XFS as modules (CVS, and later linux-2.4.6-xfs-07052001.patch) - "noatime" and "osyncisdsync" mount options - running with zero swap space - kgcc=2.95.3 (and "-O", not "-O2"), "586 w/o TSC" set for CPU type. - gcc=3.0 for glibc-2.2.3 and everything else. So ... not too much fun, because nothing broke. Keep up the good work and thanks for providing Linux with a great filesystem. Be seeing you, - Sidik From owner-linux-xfs@oss.sgi.com Tue Jul 10 12:47:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AJlsa05200 for linux-xfs-outgoing; Tue, 10 Jul 2001 12:47:54 -0700 Received: from otto.cfht.hawaii.edu (otto.colonization.com [128.171.80.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AJlmV05179 for ; Tue, 10 Jul 2001 12:47:53 -0700 Received: (from isani@localhost) by otto.cfht.hawaii.edu (8.8.8/8.8.8) id JAA10430 for linux-xfs@oss.sgi.com; Tue, 10 Jul 2001 09:47:42 -1000 From: Sidik Isani Message-Id: <200107101947.JAA10430@otto.cfht.hawaii.edu> Subject: superbloatvision To: linux-xfs@oss.sgi.com Date: Tue, 10 Jul 2001 09:47:42 -1000 (HST) X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dear XFS - Is there some way to see how much of the memory XFS uses is memory which will be freed when other things need it? When running without swapspace, this is a useful diagnostic to have on the screen (e.g. XFS buffer/cache memory displayed in a different color from bloated user programs.) Here's an example of the problem. After running a command such as: find / -xdev -anewer /timestamp-file over 100 MB (!) gets "used" according to /proc/meminfo, but it doesn't show up differently from memory allocated by userspace programs. Is there anything else in /proc which might help? Thanks, - Sidik From owner-linux-xfs@oss.sgi.com Tue Jul 10 12:53:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AJrFW06050 for linux-xfs-outgoing; Tue, 10 Jul 2001 12:53:15 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AJrDV06046 for ; Tue, 10 Jul 2001 12:53:14 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id MAA07352 for ; Tue, 10 Jul 2001 12:53:11 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2393567; Tue, 10 Jul 2001 14:51:52 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA30317; Tue, 10 Jul 2001 14:51:52 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6AJr4M13800; Tue, 10 Jul 2001 14:53:04 -0500 Message-Id: <200107101953.f6AJr4M13800@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Sidik Isani cc: linux-xfs@oss.sgi.com Subject: Re: superbloatvision In-Reply-To: Message from Sidik Isani of "Tue, 10 Jul 2001 09:47:42 -1000." <200107101947.JAA10430@otto.cfht.hawaii.edu> Date: Tue, 10 Jul 2001 14:53:03 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Dear XFS - > > Is there some way to see how much of the memory XFS uses is memory > which will be freed when other things need it? When running without > swapspace, this is a useful diagnostic to have on the screen (e.g. > XFS buffer/cache memory displayed in a different color from bloated > user programs.) > > Here's an example of the problem. After running a command such as: > > find / -xdev -anewer /timestamp-file > > over 100 MB (!) gets "used" according to /proc/meminfo, but it > doesn't show up differently from memory allocated by userspace > programs. Is there anything else in /proc which might help? jen{lord}: cat /proc/meminfo total: used: free: shared: buffers: cached: Mem: 260239360 227917824 32321536 0 0 133148672 Swap: 271425536 31924224 239501312 MemTotal: 254140 kB MemFree: 31564 kB MemShared: 0 kB Buffers: 0 kB Cached: 130028 kB Active: 20412 kB Inact_dirty: 91572 kB Inact_clean: 18044 kB Inact_target: 20 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 254140 kB LowFree: 31564 kB SwapTotal: 265064 kB SwapFree: 233888 kB That line in there which says Cached: is data in the filesystem, it represents file data and metadata, once they are cleaned by being written to disk they can and will be reclaimed by the rest of the system on an as needed basis. Steve > > Thanks, > > - Sidik From owner-linux-xfs@oss.sgi.com Tue Jul 10 12:59:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AJx8s06926 for linux-xfs-outgoing; Tue, 10 Jul 2001 12:59:08 -0700 Received: from taz.cs.utah.edu (taz.cs.utah.edu [155.99.203.51]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AJx7V06923 for ; Tue, 10 Jul 2001 12:59:07 -0700 Received: by taz.cs.utah.edu (Mailer, from userid 1363) id 12623B27748; Tue, 10 Jul 2001 13:57:20 -0600 (MDT) Message-Id: <10107101357.ZM77097@taz.cs.utah.edu> In-Reply-To: Sidik Isani "XFS mobile" (Jul 10, 9:35am) References: <200107101935.JAA10379@otto.cfht.hawaii.edu> X-Mailer: Z-Mail-SGI (3.2S.3 08feb96 MediaMail) To: Sidik Isani , linux-xfs@oss.sgi.com Subject: Re: XFS mobile Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Jul 2001 13:57:20 -0600 (MDT) From: sparker@cs.utah.edu (Steven G. Parker) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I will second that. XFS is wonderful on a laptop. I have been too lazy to make it work on th root partition, but I have a 16G home dir, and it is mighty nice that I don't have to fsck the thing whenever I run the battery out. It drains a good percentage of the battery just running fsck on ext2! Again, good work guys. Steve On Jul 10, 9:35am, Sidik Isani wrote: > Subject: XFS mobile > Hello - > > Not sure if SGI has much interest in this, but XFS is very impressive > on *laptops*. The tricky part was getting root mounted with "noatime" > so the disk doesn't spin up all the time. XFS didn't let me change > noatime,osyncisdsync after the initial mount. And the kernel, even > with the normal initrd tricks, only supports flags for ro/rw. > > Fortunately, the New Way using pivot_root provides a solution (but you > must NOT name the linuxrc "/linuxrc".) The initial RAM disk contains > my fstab and a script which checks to see what type of root filesystem > is required, loads the modules (this works for NFS-root too) mounts > root with all desired options, calls pivot_root and continues booting. > All this actually works, and provided a test for these things: > > - XFS as modules (CVS, and later linux-2.4.6-xfs-07052001.patch) > - "noatime" and "osyncisdsync" mount options > - running with zero swap space > - kgcc=2.95.3 (and "-O", not "-O2"), "586 w/o TSC" set for CPU type. > - gcc=3.0 for glibc-2.2.3 and everything else. > > So ... not too much fun, because nothing broke. Keep up the good > work and thanks for providing Linux with a great filesystem. > > Be seeing you, > > - Sidik >-- End of excerpt from Sidik Isani From owner-linux-xfs@oss.sgi.com Tue Jul 10 13:07:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AK7RE08139 for linux-xfs-outgoing; Tue, 10 Jul 2001 13:07:27 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AK7PV08128 for ; Tue, 10 Jul 2001 13:07:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA03308 for ; Tue, 10 Jul 2001 13:07:26 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2396603 for ; Tue, 10 Jul 2001 15:06:09 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA54261 for ; Tue, 10 Jul 2001 15:06:08 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6AK7KT13914; Tue, 10 Jul 2001 15:07:20 -0500 Message-Id: <200107102007.f6AK7KT13914@jen.americas.sgi.com> Date: Tue, 10 Jul 2001 15:07:20 -0500 Subject: TAKE - close window between inode activation and deactivation Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk If one thread is removing an inode from the system via prune_icache and another thread is looking it up at the same time and then unlink it, it is possible for xfs to silently corrupt the filesystem by unlinking the inode but not returning it to the free pool. This does not cause problems except for the space leak and xfs_repair can fix it. This change should effectively remove the window. Date: Tue Jul 10 12:56:22 PDT 2001 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:98576a linux/fs/xfs/xfs_iget.c - 1.146 linux/fs/xfs/linux/xfs_vnode.c - 1.66 linux/fs/xfs/linux/xfs_vnode.h - 1.21 - Add more synchronization between the inactive path and threads activating vnodes. From owner-linux-xfs@oss.sgi.com Tue Jul 10 13:10:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AKAi608786 for linux-xfs-outgoing; Tue, 10 Jul 2001 13:10:44 -0700 Received: from otto.cfht.hawaii.edu (otto.colonization.com [128.171.80.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AKAbV08765 for ; Tue, 10 Jul 2001 13:10:42 -0700 Received: (from isani@localhost) by otto.cfht.hawaii.edu (8.8.8/8.8.8) id KAA10504; Tue, 10 Jul 2001 10:10:18 -1000 From: Sidik Isani Message-Id: <200107102010.KAA10504@otto.cfht.hawaii.edu> Subject: Re: superbloatvision To: lord@sgi.com (Steve Lord) Date: Tue, 10 Jul 2001 10:10:18 -1000 (HST) Cc: linux-xfs@oss.sgi.com In-Reply-To: <200107101953.f6AJr4M13800@jen.americas.sgi.com> from "Steve Lord" at Jul 10, 2001 02:53:03 PM X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello - Hmm, maybe I'm adding up the numbers in the wrong way, or maybe it is not XFS (though I don't remember this behavior with ext2). Here is what I see after booting[1]. X is running, about 32 MB is used, and half of that is cached. 160/192 MB is free. Then, after just running "find / -xdev -anewer /timestamp-file", the numbers look like this[2]. Cached memory has gone up to about 60 MB but used memory has gone up by 160. Where did the other ~100 MB go then? The numbers don't seem to add up. --[1]-- vaio# cat /proc/meminfo total: used: free: shared: buffers: cached: Mem: 196104192 31207424 164896768 0 4202496 15106048 Swap: 0 0 0 MemTotal: 191508 kB MemFree: 161032 kB MemShared: 0 kB Buffers: 4104 kB Cached: 14752 kB Active: 8680 kB Inact_dirty: 10176 kB Inact_clean: 0 kB Inact_target: 56 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 191508 kB LowFree: 161032 kB SwapTotal: 0 kB SwapFree: 0 kB --[2]-- vaio# find / -xdev -anewer /timestamp | wc 2962 2962 128947 vaio# cat /proc/meminfo total: used: free: shared: buffers: cached: Mem: 196104192 192974848 3129344 0 4198400 59138048 Swap: 0 0 0 MemTotal: 191508 kB MemFree: 3056 kB MemShared: 0 kB Buffers: 4100 kB Cached: 57752 kB Active: 57264 kB Inact_dirty: 3928 kB Inact_clean: 660 kB Inact_target: 1972 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 191508 kB LowFree: 3056 kB SwapTotal: 0 kB SwapFree: 0 kB | |> Dear XFS - |> |> Is there some way to see how much of the memory XFS uses is memory |> which will be freed when other things need it? When running without |> swapspace, this is a useful diagnostic to have on the screen (e.g. |> XFS buffer/cache memory displayed in a different color from bloated |> user programs.) |> |> Here's an example of the problem. After running a command such as: |> |> find / -xdev -anewer /timestamp-file |> |> over 100 MB (!) gets "used" according to /proc/meminfo, but it |> doesn't show up differently from memory allocated by userspace |> programs. Is there anything else in /proc which might help? | | |jen{lord}: cat /proc/meminfo | total: used: free: shared: buffers: cached: |Mem: 260239360 227917824 32321536 0 0 133148672 |Swap: 271425536 31924224 239501312 |MemTotal: 254140 kB |MemFree: 31564 kB |MemShared: 0 kB |Buffers: 0 kB |Cached: 130028 kB |Active: 20412 kB |Inact_dirty: 91572 kB |Inact_clean: 18044 kB |Inact_target: 20 kB |HighTotal: 0 kB |HighFree: 0 kB |LowTotal: 254140 kB |LowFree: 31564 kB |SwapTotal: 265064 kB |SwapFree: 233888 kB | |That line in there which says Cached: is data in the filesystem, |it represents file data and metadata, once they are cleaned by |being written to disk they can and will be reclaimed by the rest |of the system on an as needed basis. | |Steve | | |> |> Thanks, |> |> - Sidik | | From owner-linux-xfs@oss.sgi.com Tue Jul 10 13:54:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AKsSa14372 for linux-xfs-outgoing; Tue, 10 Jul 2001 13:54:28 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AKsQV14366 for ; Tue, 10 Jul 2001 13:54:26 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA04610; Tue, 10 Jul 2001 22:54:22 +0200 (CEST) Message-Id: <4.3.2.7.2.20010710225035.02c6c5c8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 10 Jul 2001 22:54:11 +0200 To: ptb@it.uc3m.es From: Seth Mos Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 Cc: ptb@it.uc3m.es, linux-xfs@oss.sgi.com In-Reply-To: <200107101532.RAA05803@nbd.it.uc3m.es> References: <4.3.2.7.2.20010710164832.03481e90@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:32 10-7-2001 +0200, Peter T. Breuer wrote: >"A month of sundays ago Seth Mos wrote:" > > >can't find a likely referant for the failed block. And in any case > > >compilation of the result fails in aic7xxx! > > > > See FAQ. This is not related to the XFS patch. > >Well, I recall something about that too in recent list traffic, but >didn't pay too much attention at the time. I don't mind whether I use >the new or old aic7xxx driver, personally. Crap, I missed the can not find *.h entry for aic7xxx. That should be saying [ ] Build Adapter Firmware with Kernel Build (NEW) Which is the solution to generating the .h files. >I can't find anything related to any of the problems I noted in the FAQ. >Which section did you have in mind? There is a mention of the aic7xxx >driver but not in connection with the problem I noted. You are correct. Memory corruption of a weeks vacation. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Tue Jul 10 14:03:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AL3hq15899 for linux-xfs-outgoing; Tue, 10 Jul 2001 14:03:43 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AL3fV15890 for ; Tue, 10 Jul 2001 14:03:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id OAA01648 for ; Tue, 10 Jul 2001 14:03:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2357162 for ; Tue, 10 Jul 2001 16:02:24 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA96706 for ; Tue, 10 Jul 2001 16:02:24 -0500 (CDT) Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6AL3am18531; Tue, 10 Jul 2001 16:03:36 -0500 Message-Id: <200107102103.f6AL3am18531@jen.americas.sgi.com> Date: Tue, 10 Jul 2001 16:03:36 -0500 From: Eric Sandeen To: linux-xfs@oss.sgi.com Subject: XFS for Linux 1.0.1 Released Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk SGI is pleased to announce the 1.0.1 release of XFS for Linux. The web pages will be updated in a short while, but in the meantime, files are available under ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/ This URL contains the following directories: kernel_rpms/linux-2.4.5/ The 2.4.5 kernel RPMS are vanilla 2.4.5 kernels (Linus' tree) with the XFS bits added. kernel_rpms/RHlinux-2.4.3/ The 2.4.3 kernel RPMS are based on Red Hat's 7.1 2.4.3 kernel version - only the XFS bits have been changed. These RPMS are intended for anyone using XFS on RH 7.1 in an environment where they need Red Hat's kernel improvements, and they do not wish to jump kernel versions to get XFS improvements. kernel_patches/ The patches provided are for linux-2.4.5. They are now broken into 2 patches, one for files unique to XFS, and one that modifies existing core Linux files. kdb patches are also provided for debugging. See the README file in the patches/ directory for patching instructions. cmd_tars/ cmd_rpms/ Userspace commands are provided both as tarballs and as RPMs. installer/ The installer/ directory contains a modified Red Hat 7.1 installer that will allow you to install a Red Hat 7.1 system on XFS. If you already used the XFS 1.0 system installer, there is no need to re-install, simply upgrade your RPMs. A new system installer was provided for a few people who, due to bugs in the 1.0 release, were unable to use the 1.0 installer. CHANGES since 1.0: ================== Some of the ACL library's functions have been changed to comply with the POSIX ACL (P1003.1e) withdrawn standard. These changes make it simpler for the Samba code to work with XFS. A bug was also fixed for chacl -d. General code cleanup unused code & gratuitous prototypes were removed unused debug checking were removed compiler warnings were fixed Irix DMAPI bug fix merged Unmount of dirty filesystem speeded up inode fields pared down, shrinking inode by 60-70 bytes Optimizations based on kernel profiling made Changes made to help with compiler independence (but egcs-2.91.66 is still preferred & tested at SGI) ATIME not updated for extended attribute or ACL changes Default BIOSIZE changed to 4k to fix some db-related size issues "Best" AG size changed from 1GB to 4GB when the filesystem exceeds 64GB Pick up mount options parsed by the VFS layer (noatime, readonly) LVM snapshotting capability added vnode tracing and xfs debug removed from config options Various memory handling improvements made NFS behavior improved Filesystem initialization messages removed Various changes andn enhancements made to xfs test scripts -L option added to mkfs.xfs to support filesystem labels Documentation updates added userspace man tools moved to /usr/share/man for most systems Looping bug in repquota under some glibc variants fixed xfsdump/restore fixes for remote tapes fixes for nfs server support including panics in during mixed local and remote access From owner-linux-xfs@oss.sgi.com Tue Jul 10 14:31:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ALVsD20489 for linux-xfs-outgoing; Tue, 10 Jul 2001 14:31:54 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ALVsV20486 for ; Tue, 10 Jul 2001 14:31:54 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Tue, 10 Jul 2001 14:29:23 -0700 Subject: Re: Patch for linux 2.4.6-ac* series? From: Thomas Duffy To: kozmomike@home.com Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 10 Jul 2001 14:30:12 -0700 Message-Id: <994800612.5792.2.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 10 Jul 2001 21:29:23.0096 (UTC) FILETIME=[6319E180:01C10987] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Jul 2001 11:30:57 -0600, Michal Kozlowski wrote: > Hi, I was wondering if someone could provide some hints on creating a xfs > patch for the 2.4.6-ac2 kernel. I know the SGI team doesn't support it > since Alan can release way to many updates, but I'm willing to try and get > the 2 going together. I want to try the hpt370 raid-0 with xfs on it. > How much effort would something like this take? I've modified source code > many times to get things working but never attempted something like this. > Maybe if I get good at this I could release regular updates, but for now I > just want 2.4.6-ac2 to work. Thanks for all you help, if you grabbed the patch of xfs from the kernel.src.rpm for 2.4.3, you should have a patch that works on top of some version of ac since redhat takes ac into it's kernel rpm. but, ac has probably changed a bit from 2.4.3 days to 2.4.6 days, so I don't know how hard the two would be to reconcile. I have done xfs/ac merges before so it is not impossible...sometimes you might have a weird conflict that only an expert (like steve) can tell you what you should do. -tduffy From owner-linux-xfs@oss.sgi.com Tue Jul 10 14:32:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ALWxc20749 for linux-xfs-outgoing; Tue, 10 Jul 2001 14:32:59 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ALWwV20746 for ; Tue, 10 Jul 2001 14:32:58 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Tue, 10 Jul 2001 14:30:27 -0700 Subject: Re: Source for xfsprogs-devel? From: Thomas Duffy To: nw@codon.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <003f01c1096d$840cc840$50824e40@iboats.com> References: <003f01c1096d$840cc840$50824e40@iboats.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 10 Jul 2001 14:31:16 -0700 Message-Id: <994800676.5785.4.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 10 Jul 2001 21:30:27.0329 (UTC) FILETIME=[89630F10:01C10987] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Jul 2001 12:24:09 -0600, Steve Wolfe wrote: > > Is there a place where I may obtain the xfsprogs-devel package without > having to use RPM? The machine I'm working on does not have a new enough > RPM version, and it would be much easier for me if I didn't have to > upgrade the multitude of packages that RPM 4 wants.... > > Since the source for the other utilities (xfsdump, etc.) seem to rely on > xfsprogs-devel, I'm kind of stuck for the moment. the other option is to update to rpm 3.0.5 which supports v4 rpms. -tduffy From owner-linux-xfs@oss.sgi.com Tue Jul 10 15:01:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AM1Jk24596 for linux-xfs-outgoing; Tue, 10 Jul 2001 15:01:19 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AM1HV24593 for ; Tue, 10 Jul 2001 15:01:17 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA07762 for ; Tue, 10 Jul 2001 15:01:08 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id PAA94784 for ; Tue, 10 Jul 2001 15:05:38 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 7AE2915A185 for ; Tue, 10 Jul 2001 14:59:55 -0700 (PDT) Subject: Re: XFS for Linux 1.0.1 Released From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <200107102103.f6AL3am18531@jen.americas.sgi.com> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 10 Jul 2001 14:59:55 -0700 Message-Id: <994802395.19620.19.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Jul 2001 16:03:36 -0500, Eric Sandeen wrote: > SGI is pleased to announce the 1.0.1 release of XFS for Linux. That's great news! Guys, can you please make the floppy images available, so one does not have to download the entire ISO just to test the new floppies. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Tue Jul 10 15:46:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AMkce30076 for linux-xfs-outgoing; Tue, 10 Jul 2001 15:46:38 -0700 Received: from oboe.it.uc3m.es (oboe.it.uc3m.es [163.117.139.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AMkaV30072 for ; Tue, 10 Jul 2001 15:46:37 -0700 Received: (from ptb@localhost) by oboe.it.uc3m.es (8.11.0/8.11.0) id f6AMjmc27835; Wed, 11 Jul 2001 00:45:48 +0200 From: "Peter T. Breuer" Message-Id: <200107102245.f6AMjmc27835@oboe.it.uc3m.es> Subject: Re: 2.4.6 patch does not apply cleanly to 2.4.6 In-Reply-To: <200107101610.f6AGAxu21955@jen.americas.sgi.com> from "Steve Lord" at "Jul 10, 2001 11:10:59 am" To: "Steve Lord" Date: Wed, 11 Jul 2001 00:45:48 +0200 (MET DST) CC: ptb@it.uc3m.es, "Seth Mos" , linux-xfs@oss.sgi.com X-Anonymously-To: Reply-To: ptb@it.uc3m.es X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "A month of sundays ago Steve Lord wrote:" > > Jul 4 22:05 bzip2 linux-2.4.6-xfs-07052001.patch.bz2 817Kb > > ^^^^^^^^^^^^ > > Try this one, it applies cleanly and builds without problem for > me, including the new aic driver and xfs as a module. Ditto. I didn't apply any further aic patch yet. My first impression is that there is some instability. I'm running on a dell smp machine, and with 2.4.3 + xfs I was getting about 1 hang a week (I know about them because the machine doesn't always reboot but hangs). I had about six today :-(. reboot system boot 2.4.6-SMP-XFS Tue Jul 10 20:16 (04:15) ptb ttyp2 :0.0 Tue Jul 10 19:56 - crash (00:20) ptb ttyp0 :0.0 Tue Jul 10 19:53 - crash (00:23) ptb :0 Tue Jul 10 19:53 - crash (00:23) reboot system boot 2.4.6-SMP-XFS Tue Jul 10 19:52 (04:39) reboot system boot 2.4.6-SMP-XFS Tue Jul 10 19:50 (00:00) ptb ttyp3 :0.0 Tue Jul 10 19:40 - crash (00:10) ptb ttyp2 :0.0 Tue Jul 10 19:39 - crash (00:11) ptb ttyp0 :0.0 Tue Jul 10 19:37 - crash (00:13) ptb :0 Tue Jul 10 19:37 - crash (00:13) reboot system boot 2.4.6-SMP-XFS Tue Jul 10 19:36 (00:14) reboot system boot 2.4.6-SMP-XFS Tue Jul 10 19:03 (00:47) reboot system boot 2.4.3-SMP-XFS Tue Jul 10 14:57 (04:03) I don't have a test yet. I get the impression that it hangs under load. I cut the speed of the 4 scsi lvd drives to 20MHz. I was runing raid5 over the scsi, with lvm managing the raid resource, and inside the lvm I had a pair of virtual partitions forming raid0 mirrors with nbd network devices. The xfs is on these. I'm pretty sure that syncing the higher level raid while the lower level raid was still syncing hung the machine. Ditto doing a mkraid on the higher level. Ditto doing it by hand with dd. I was able to dd to and from each subdevice separately with no problem. I was able to fsck.xfs the nbd device, and the raid device over it, but it hung later while doing nothing in particular. I haven't been able to test the raw 2.4.6 kernel. My impression is that this is a raid5 problem, but maybe the xfs patch has something to do with it? I recall accounting changes to make everything be computed in sectors coming in from xfs. Is all that still OK. And it was noticable that the scsi resync speed dropped by half over 2.4.3. That usually implies a change from counting in KB to counting in 512B. I'll try and do more testing tomorrow. Just a first impression ... Peter From owner-linux-xfs@oss.sgi.com Tue Jul 10 15:55:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6AMttP31492 for linux-xfs-outgoing; Tue, 10 Jul 2001 15:55:55 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6AMtsV31488 for ; Tue, 10 Jul 2001 15:55:54 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip17.idcomm.com [209.60.72.144]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6AMwta18826 for ; Tue, 10 Jul 2001 16:58:55 -0600 Message-ID: <3B4B887B.89A30E14@idcomm.com> Date: Tue, 10 Jul 2001 16:58:03 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei wrote: > > On 10 Jul 2001 16:03:36 -0500, Eric Sandeen wrote: > > SGI is pleased to announce the 1.0.1 release of XFS for Linux. > > That's great news! > > Guys, can you please make the floppy images available, so one does not > have to download the entire ISO just to test the new floppies. > > -- > Florin Andrei What I'd find more interesting (since floppy images can't work with some of the possible kernel options...size gets too large) would be an ISO CD image that is equivalent to Tom's Root Boot (rescue with everything under the sun), but XFS based (any rescue or repair tool would be nice, even if it is for other fs's like reiser or ext3). Such could be done with probably a 25 MB download (10 to 15 MB with gzip -9), and provide the ability to format, repair, etc. I mention this because I am still working on my own custom CD rescue (I recently discovered that one big problem was that my CD was not a "multiread" version, and could not handle CD-RW's, only CD-R's...duh). Add to that every test I do requiring upload/download through 56k/33k modems...I'm slowly getting there, but it is a lesson in humility. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Tue Jul 10 16:54:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ANsJW06885 for linux-xfs-outgoing; Tue, 10 Jul 2001 16:54:19 -0700 Received: from mail.computalog.com ([209.82.103.230]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ANsHV06876 for ; Tue, 10 Jul 2001 16:54:18 -0700 Received: from gerry.edmonton.computalog.com (mug.computalog.com [209.82.103.229]) by mail.computalog.com (8.8.8/8.8.8) with ESMTP id RAA15831 for ; Tue, 10 Jul 2001 17:54:10 -0600 Received: by gerry.edmonton.computalog.com (Postfix, from userid 1000) id 1F538165E45; Tue, 10 Jul 2001 17:56:45 -0600 (MDT) Date: Tue, 10 Jul 2001 17:56:45 -0600 From: "Gerard W. Patterson" To: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released Message-ID: <20010710175645.A22119@computalog.com> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> <3B4B887B.89A30E14@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B4B887B.89A30E14@idcomm.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 10, 2001 at 04:58:03PM -0600, D. Stimits wrote: > > What I'd find more interesting (since floppy images can't work with some > of the possible kernel options...size gets too large) would be an ISO CD > image that is equivalent to Tom's Root Boot (rescue with everything > under the sun), but XFS based (any rescue or repair tool would be nice, > even if it is for other fs's like reiser or ext3). Such could be done > with probably a 25 MB download (10 to 15 MB with gzip -9), and provide > the ability to format, repair, etc. I mention this because I am still > working on my own custom CD rescue (I recently discovered that one big > problem was that my CD was not a "multiread" version, and could not > handle CD-RW's, only CD-R's...duh). Add to that every test I do > requiring upload/download through 56k/33k modems...I'm slowly getting > there, but it is a lesson in humility. > > D. Stimits, stimits@idcomm.com Interestingly enough, this is exactly what I am working on for my current project. It is currently based on a 2.4.5 kernel with the xfs patch applied. (I started this a week and a bit ago and we are already at 2.4.6! jeezz). I have succeeded in getting a boot floppy image (I needed support for systems that didn't have CDROM drives) that contains the kernel (1015k) and a small ( <170k ) root file system. Go busy-box and uClibc! With this image, I can mount any large drive (magneto-optical) in this case and grab the rest of the system that I need (including binaries to replace the temporary busy-box ones. --vi is not vim and msh is not bash.) This image is also suitable for use to combine the floppy and the large drive onto a CDR for a complete, boot-able system. I plan on updating to a newer kernel and utilities once I am closer to release. (probably go for some type of auto-build). If you would like to collaborate let me know. Regards, Gerry -- Gerard W. Patterson, B.Sc | Computalog Ltd. Software Engineering | Edmonton, AB | Canada From owner-linux-xfs@oss.sgi.com Tue Jul 10 20:52:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B3qeX02641 for linux-xfs-outgoing; Tue, 10 Jul 2001 20:52:40 -0700 Received: from pyre.virge.net (qmailr@cr541398-a.cambr1.on.wave.home.com [24.156.0.228]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B3qcV02636 for ; Tue, 10 Jul 2001 20:52:38 -0700 Received: (qmail 694 invoked by uid 1000); 11 Jul 2001 03:52:36 -0000 Date: Tue, 10 Jul 2001 23:52:36 -0400 From: Norbert Veber To: linux-xfs@oss.sgi.com Subject: Re: XFS Issues Message-ID: <20010710235236.A654@pyre.virge.net> Mail-Followup-To: Norbert Veber , linux-xfs@oss.sgi.com References: <200107091922.f69JM5O03020@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107091922.f69JM5O03020@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 09, 2001 at 02:22:05PM -0500, Steve Lord wrote: > Unmount the filesystem and run xfs_repair -n on the device, then send me > the output. You should really be seeing a .. link for that ls output. I > have been chasing something which might be related for a few days > now. I just tried booting into single user mode, and running it, but it refuses to run even when the filesystem is mounted ro. I cannot unmount it because its my root (/) partition. Is there an option to force it to run? I dont see why it refuses to especially with the -n option.. > > Is this normal? Does the XFS kernel not use buffers, or, is the output just > > wrong? > > This buffer count does not reflect buffers used for file data, just the > block device cache - which xfs does not use. If you run a mkfs or > xfs_repair type operation on the block device you will see the numbers > go up. You are seeing normal values here, my box currently looks like > this: I actually have no idea what the difference between cache and buffers is. I was looking for some documentation with regards to that a while back but found none. Is it explained someplace? :) From owner-linux-xfs@oss.sgi.com Tue Jul 10 20:58:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B3wO803571 for linux-xfs-outgoing; Tue, 10 Jul 2001 20:58:24 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B3wNV03561 for ; Tue, 10 Jul 2001 20:58:23 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id UAA01151 for ; Tue, 10 Jul 2001 20:58:22 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 NAA18091; Wed, 11 Jul 2001 13:57:04 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id NAA03362; Wed, 11 Jul 2001 13:57:03 +1000 (EST) From: "Nathan Scott" Message-Id: <10107111357.ZM198806@wobbly.melbourne.sgi.com> Date: Wed, 11 Jul 2001 13:57:01 -0500 In-Reply-To: Norbert Veber "Re: XFS Issues" (Jul 10, 11:52pm) References: <200107091922.f69JM5O03020@jen.americas.sgi.com> <20010710235236.A654@pyre.virge.net> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Norbert Veber , linux-xfs@oss.sgi.com Subject: Re: XFS Issues Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Jul 10, 11:52pm, Norbert Veber wrote: > Subject: Re: XFS Issues > On Mon, Jul 09, 2001 at 02:22:05PM -0500, Steve Lord wrote: > > Unmount the filesystem and run xfs_repair -n on the device, then send me > > the output. You should really be seeing a .. link for that ls output. I > > have been chasing something which might be related for a few days > > now. > > I just tried booting into single user mode, and running it, but it refuses > to run even when the filesystem is mounted ro. I cannot unmount it because > its my root (/) partition. Is there an option to force it to run? I dont > see why it refuses to especially with the -n option.. > The userspace code wasn't very clever at detecting a readonly root filesystem - if you upgrade to the current rpms from the XFS 1.0.1 release, you should find this problem fixed there. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jul 10 21:16:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B4GMd05679 for linux-xfs-outgoing; Tue, 10 Jul 2001 21:16:22 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B4GKV05672 for ; Tue, 10 Jul 2001 21:16:20 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id VAA08188 for ; Tue, 10 Jul 2001 21:13:44 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA81889 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 14:15:02 +1000 (EST) Date: Wed, 11 Jul 2001 14:15:02 +1000 (EST) From: Nathan Scott Message-Id: <200107110415.OAA81889@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs-1.3.0-pre1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Bunch of changes to xfsprogs, which is undergoing a bit of (ongoing) surgery at the moment. Other projects/folk need these changes now, so checking in with intent to make some small adjustments later. Executive summary: - libtool changes from DeanR, reworked slightly by me, will almost certainly need more fine tuning; - libdisk added to get driver specific stuff out of mkfs, and to allow sharing of some code with other projects; - partition table detection heuristics to mkfs for added peace of mind; (guess who got bitten? ;) cheers. Date: Tue Jul 10 21:01:18 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/base-linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98626a cmd/xfsprogs/ltconfig - 1.1 cmd/xfsprogs/aclocal.m4 - 1.1 cmd/xfsprogs/config.guess - 1.1 cmd/xfsprogs/config.sub - 1.1 cmd/xfsprogs/ltmain.sh - 1.1 - new files added for libtool support. cmd/xfsprogs/libdisk/lvm_user.h - 1.1 cmd/xfsprogs/libdisk/drivers.c - 1.1 cmd/xfsprogs/libdisk/mountinfo.c - 1.1 cmd/xfsprogs/libdisk/lvm.h - 1.1 cmd/xfsprogs/libdisk/lvm.c - 1.1 cmd/xfsprogs/libdisk/liblvm.h - 1.1 cmd/xfsprogs/libdisk/fstype.h - 1.1 cmd/xfsprogs/libdisk/fstype.c - 1.1 cmd/xfsprogs/libdisk/md.h - 1.1 cmd/xfsprogs/libdisk/Makefile - 1.1 cmd/xfsprogs/include/volume.h - 1.1 cmd/xfsprogs/include/fstyp.h - 1.1 cmd/xfsprogs/libdisk/md.c - 1.1 cmd/xfsprogs/include/mountinfo.h - 1.1 cmd/xfsprogs/include/Makefile - 1.5 - move a bunch of code around so that driver specfic code is encapsulated in libdisk, install more headers for others to consume (esp. disk headers). cmd/xfsprogs/libdisk/xvm.h - 1.1 cmd/xfsprogs/libdisk/xvm.c - 1.1 - stubs for future xvm stripe info extraction support. cmd/xfsprogs/include/dvh.h - 1.1 - required by mkfs to detect SGI partition tables on a disk and not blow away the entire disk. cmd/xfsprogs/libdisk/pttype.h - 1.1 cmd/xfsprogs/libdisk/pttype.c - 1.1 - code for detecting partition tables so that mkfs wont nuke 'em unless forced. as with the filesystem detection code, most comes from util-linux package. cmd/xfsprogs/include/lvm_user.h - 1.4 cmd/xfsprogs/include/lvm.h - 1.4 cmd/xfsprogs/include/liblvm.h - 1.4 cmd/xfsprogs/include/lvm_log.h - 1.3 cmd/xfsprogs/include/lvm_config.h - 1.3 cmd/xfsprogs/include/md-int.h - 1.2 - moved into libdisk (private header, libdisk only). cmd/xfsprogs/include/buildrules - 1.3 cmd/xfsprogs/include/builddefs.in - 1.6 cmd/xfsprogs/growfs/Makefile - 1.3 cmd/xfsprogs/fsck/Makefile - 1.3 cmd/xfsprogs/doc/Makefile - 1.5 cmd/xfsprogs/db/Makefile - 1.3 cmd/xfsprogs/repair/Makefile - 1.3 cmd/xfsprogs/mkfs/Makefile - 1.4 cmd/xfsprogs/mkfile/Makefile - 1.3 cmd/xfsprogs/logprint/Makefile - 1.3 cmd/xfsprogs/libxfs/Makefile - 1.5 cmd/xfsprogs/bmap/Makefile - 1.3 cmd/xfsprogs/libhandle/Makefile - 1.4 cmd/xfsprogs/doc/CHANGES - 1.22 cmd/xfsprogs/debian/rules - 1.5 cmd/xfsprogs/configure.in - 1.7 cmd/xfsprogs/Makefile - 1.4 cmd/xfsprogs/debian/control - 1.5 cmd/xfsprogs/debian/changelog - 1.17 cmd/xfsprogs/rtcp/Makefile - 1.2 cmd/xfsprogs/freeze/Makefile - 1.2 - rework for libtool support. cmd/xfsprogs/mkfs/xfs_mkfs.c - 1.13 cmd/xfsprogs/mkfs/volume.h - 1.2 cmd/xfsprogs/mkfs/mountinfo.h - 1.3 cmd/xfsprogs/mkfs/mountinfo.c - 1.4 cmd/xfsprogs/mkfs/fstyp.c - 1.2 - some headers and functions moved in the libdisk reorganisation. cmd/xfsprogs/install-sh - 1.2 - very minor update after libtool changes. cmd/xfsprogs/doc/INSTALL - 1.2 - add words about "install-dev" make target. cmd/xfsprogs/VERSION - 1.20 - bump to 1.3.0-pre1, pkg being reworked for libtool support. From owner-linux-xfs@oss.sgi.com Tue Jul 10 21:17:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B4HJI05852 for linux-xfs-outgoing; Tue, 10 Jul 2001 21:17:19 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B4HIV05848 for ; Tue, 10 Jul 2001 21:17:18 -0700 Received: from thebarn.com (nic-25-c96-156.mn.mediaone.net [24.25.96.156]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6B4HFNe020169; Tue, 10 Jul 2001 23:17:15 -0500 (CDT) Message-ID: <3B4BD345.5549B23F@thebarn.com> Date: Tue, 10 Jul 2001 23:17:10 -0500 From: Russell Cattelan X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Florin Andrei CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei wrote: > On 10 Jul 2001 16:03:36 -0500, Eric Sandeen wrote: > > SGI is pleased to announce the 1.0.1 release of XFS for Linux. > > That's great news! > > Guys, can you please make the floppy images available, so one does not > have to download the entire ISO just to test the new floppies. > Did you look in? projects/xfs/download/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1/images > > -- > Florin Andrei -- Russell Cattelan cattelan@thebarn.com From owner-linux-xfs@oss.sgi.com Tue Jul 10 22:08:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B58Hu10522 for linux-xfs-outgoing; Tue, 10 Jul 2001 22:08:17 -0700 Received: from otto.cfht.hawaii.edu (otto.colonization.com [128.171.80.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B58BV10511 for ; Tue, 10 Jul 2001 22:08:16 -0700 Received: (from isani@localhost) by otto.cfht.hawaii.edu (8.8.8/8.8.8) id TAA12325 for linux-xfs@oss.sgi.com; Tue, 10 Jul 2001 19:07:47 -1000 From: Sidik Isani Message-Id: <200107110507.TAA12325@otto.cfht.hawaii.edu> Subject: Release 1.0.1 / superbloatvision To: linux-xfs@oss.sgi.com Date: Tue, 10 Jul 2001 19:07:47 -1000 (HST) X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello - Just in case some of the different options I use (see message w/ Subject: XFS mobile) were causing the problem, I've now built a 2.4.5 kernel with XFS release 1.0.1, the standard gcc options, and no extra options for mounting the filesystem. The system behaves fine, but memory usage is still a puzzle to me. Can anyone help me interpret the numbers in /proc/meminfo correctly. Is `Active:' not a subset of the `Cached:' memory? Sometimes it has been reported greater. Even if I add Active and Cached together, after running a command like find (especially with the -atime option) there's a lot of memory which top can't associate with a process but also doesn't appear anywhere else. Does anyone else see Used memory increase a lot more than Cached after running find/rsync/etc? Be seeing you, - Sidik From owner-linux-xfs@oss.sgi.com Tue Jul 10 22:22:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B5Mux11261 for linux-xfs-outgoing; Tue, 10 Jul 2001 22:22:56 -0700 Received: from exocore.com ([203.200.9.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B5MpV11252 for ; Tue, 10 Jul 2001 22:22:52 -0700 Received: (from shanu@localhost) by exocore.com (8.11.2/8.8.7) id f6B5Mkt03758 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 10:52:46 +0530 Date: Wed, 11 Jul 2001 10:52:45 +0530 From: Shanker Balan To: Linux-XFS Subject: FAQ: How do i use rsync? Message-ID: <20010711105245.A3329@exocore.com> Reply-To: Shanker Balan Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: Can anyone gimme the command line arguments for rsyncing the XFS Installer 1.0.1 with 1.0.0 iso image? How do i construct a rsync URL using "oss.sgi.com::xfsftp" as base? I tried this but it did not work: $ rsync -avuz oss.sgi.com::xfsftp/download/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso RH7.1-SGI-XFS-1.0.iso receiving file list ... link_stat /download/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso : No such file or directory done client: nothing to do I hope that the rsync procedure will be added to the FAQ! -- Shanu -- - - - - - - - - - - - ( Shanu ) - - Shanker Balan http://people.exocore.com/shanu shanu at exocore dot com From owner-linux-xfs@oss.sgi.com Tue Jul 10 22:31:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B5VP511906 for linux-xfs-outgoing; Tue, 10 Jul 2001 22:31:25 -0700 Received: from exocore.com ([203.200.9.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B5VNV11901 for ; Tue, 10 Jul 2001 22:31:23 -0700 Received: (from shanu@localhost) by exocore.com (8.11.2/8.8.7) id f6B5VHH03955 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 11:01:17 +0530 Date: Wed, 11 Jul 2001 11:01:17 +0530 From: Shanker Balan To: Linux-XFS Subject: Re: FAQ: How do i use rsync? Message-ID: <20010711110117.B3329@exocore.com> Reply-To: Shanker Balan References: <20010711105245.A3329@exocore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010711105245.A3329@exocore.com>; from shanu@exocore.com on Wed, Jul 11, 2001 at 10:52:45AM +0530 Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: Shanker Balan wrote, > I hope that the rsync procedure will be added to the FAQ! Oh, just runing "rsync oss.sgi.com::xfsftp" will give me a listing. But i have a new prblem now - $ rsync -avuz oss.sgi.com::xfsftp/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso RH7.1-SGI-XFS-1.0.iso receiving file list ... done RH7.1-SGI-XFS-1.0.iso inflate returned -3 (0 bytes) unexpected EOF in read_timeout Is this a firewall issue? -- Shanu -- - - - - - - - - - - - ( Shanu ) - - Shanker Balan http://people.exocore.com/shanu shanu at exocore dot com From owner-linux-xfs@oss.sgi.com Tue Jul 10 22:38:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B5cv012498 for linux-xfs-outgoing; Tue, 10 Jul 2001 22:38:57 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B5ctV12491 for ; Tue, 10 Jul 2001 22:38:56 -0700 Received: from thebarn.com (nic-25-c96-156.mn.mediaone.net [24.25.96.156]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6B5cpNe020849; Wed, 11 Jul 2001 00:38:51 -0500 (CDT) Message-ID: <3B4BE666.9972F23@thebarn.com> Date: Wed, 11 Jul 2001 00:38:46 -0500 From: Russell Cattelan X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Shanker Balan CC: Linux-XFS Subject: Re: FAQ: How do i use rsync? References: <20010711105245.A3329@exocore.com> <20010711110117.B3329@exocore.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Shanker Balan wrote: > Hello: > > Shanker Balan wrote, > > I hope that the rsync procedure will be added to the FAQ! > > Oh, just runing "rsync oss.sgi.com::xfsftp" will give me a listing. > > But i have a new prblem now - > > $ rsync -avuz oss.sgi.com::xfsftp/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso RH7.1-SGI-XFS-1.0.iso > receiving file list ... done > RH7.1-SGI-XFS-1.0.iso > inflate returned -3 (0 bytes) > unexpected EOF in read_timeout > > Is this a firewall issue? > Try dropping the -z (compression) and see what you get... That is and odd error... maybe you should upgrade your rsync? -- Russell Cattelan cattelan@thebarn.com From owner-linux-xfs@oss.sgi.com Tue Jul 10 22:50:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B5oWp13154 for linux-xfs-outgoing; Tue, 10 Jul 2001 22:50:32 -0700 Received: from exocore.com ([203.200.9.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B5o1V13139 for ; Tue, 10 Jul 2001 22:50:06 -0700 Received: (from shanu@localhost) by exocore.com (8.11.2/8.8.7) id f6B5nVc04572 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 11:19:31 +0530 Date: Wed, 11 Jul 2001 11:19:30 +0530 From: Shanker Balan To: Linux-XFS Subject: Re: FAQ: How do i use rsync? Message-ID: <20010711111930.C3329@exocore.com> Reply-To: Shanker Balan References: <20010711105245.A3329@exocore.com> <20010711110117.B3329@exocore.com> <3B4BE666.9972F23@thebarn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B4BE666.9972F23@thebarn.com>; from cattelan@thebarn.com on Wed, Jul 11, 2001 at 12:38:46AM -0500 Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: Russell Cattelan wrote, > Try dropping the -z (compression) and see what you get... That worked. $ls -la total 305960 -rw------- 1 shanu staff 676796 Jul 11 11:15 .RH7.1-SGI-XFS-1.0.iso.4kk6jd -rw-rw-r-- 1 shanu staff 313282560 Jun 23 10:22 RH7.1-SGI-XFS-1.0.iso Without "-z", wont things be slower? > That is and odd error... maybe you should upgrade your rsync? I am running the default rsync which came with RHL 7.1. If i interrupt rsync, will it resume? Thanx Russel! -- Shanu -- - - - - - - - - - - - ( Shanu ) - - Shanker Balan http://people.exocore.com/shanu shanu at exocore dot com From owner-linux-xfs@oss.sgi.com Tue Jul 10 23:08:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B68B214461 for linux-xfs-outgoing; Tue, 10 Jul 2001 23:08:11 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B689V14457 for ; Tue, 10 Jul 2001 23:08:09 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip25.idcomm.com [209.60.72.152]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6B6BBa03800 for ; Wed, 11 Jul 2001 00:11:12 -0600 Message-ID: <3B4BEDCA.9DD98228@idcomm.com> Date: Wed, 11 Jul 2001 00:10:18 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> <3B4B887B.89A30E14@idcomm.com> <20010710175645.A22119@computalog.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Gerard W. Patterson" wrote: > > On Tue, Jul 10, 2001 at 04:58:03PM -0600, D. Stimits wrote: > > > > What I'd find more interesting (since floppy images can't work with some > > of the possible kernel options...size gets too large) would be an ISO CD > > image that is equivalent to Tom's Root Boot (rescue with everything > > under the sun), but XFS based (any rescue or repair tool would be nice, > > even if it is for other fs's like reiser or ext3). Such could be done > > with probably a 25 MB download (10 to 15 MB with gzip -9), and provide > > the ability to format, repair, etc. I mention this because I am still > > working on my own custom CD rescue (I recently discovered that one big > > problem was that my CD was not a "multiread" version, and could not > > handle CD-RW's, only CD-R's...duh). Add to that every test I do > > requiring upload/download through 56k/33k modems...I'm slowly getting > > there, but it is a lesson in humility. > > > > D. Stimits, stimits@idcomm.com > > Interestingly enough, this is exactly what I am working on for my current > project. It is currently based on a 2.4.5 kernel with the xfs > patch applied. (I started this a week and a bit ago and we are already at > 2.4.6! jeezz). I have succeeded in getting a boot floppy image (I needed > support for systems that didn't have CDROM drives) that contains the kernel > (1015k) and a small ( <170k ) root file system. Go busy-box and uClibc! > With this image, I can mount any large drive (magneto-optical) in this case > and grab the rest of the system that I need (including binaries to replace > the temporary busy-box ones. --vi is not vim and msh is not bash.) This image > is also suitable for use to combine the floppy and the large drive onto a > CDR for a complete, boot-able system. > > I plan on updating to a newer kernel and utilities once I am closer to > release. (probably go for some type of auto-build). If you would like to > collaborate let me know. > > Regards, > > Gerry > > -- > Gerard W. Patterson, B.Sc | Computalog Ltd. > Software Engineering | Edmonton, AB > | Canada If you use a 2.4.5 kernel, or 2.4.6-pre1, be sure to manually add one patch...without this patch there are some serious problems under various circumstances, all of which are fatal. In kernel tree, fs/block_dev.c, approximately line 596, is this function (the line starting with "+" should be added, don't literally put in the "+"): int ioctl_by_bdev(struct block_device *bdev, unsigned cmd, unsigned long arg) { kdev_t rdev = to_kdev_t(bdev->bd_dev); struct inode inode_fake; int res; mm_segment_t old_fs = get_fs(); if (!bdev->bd_op->ioctl) return -EINVAL; inode_fake.i_rdev=rdev; + inode_fake.i_bdev=bdev; init_waitqueue_head(&inode_fake.i_wait); set_fs(KERNEL_DS); res = bdev->bd_op->ioctl(&inode_fake, NULL, cmd, arg); set_fs(old_fs); return res; } Use of loop devices is extremely risky without this. The first patches occured in Alan Cox's 2.4.5-ac3, and it also appeared at 2.4.6-pre2. Prior versions lack the fix. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Tue Jul 10 23:11:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B6BiT14827 for linux-xfs-outgoing; Tue, 10 Jul 2001 23:11:44 -0700 Received: from exocore.com ([203.200.9.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B6BDV14788 for ; Tue, 10 Jul 2001 23:11:14 -0700 Received: (from shanu@localhost) by exocore.com (8.11.2/8.8.7) id f6B6Adc05078 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 11:40:39 +0530 Date: Wed, 11 Jul 2001 11:40:39 +0530 From: Shanker Balan To: Linux-XFS Subject: Re: FAQ: How do i use rsync? Message-ID: <20010711114039.D3329@exocore.com> Reply-To: Shanker Balan References: <20010711105245.A3329@exocore.com> <20010711110117.B3329@exocore.com> <3B4BE666.9972F23@thebarn.com> <20010711111930.C3329@exocore.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010711111930.C3329@exocore.com>; from shanu@exocore.com on Wed, Jul 11, 2001 at 11:19:30AM +0530 Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: Shanker Balan wrote, > If i interrupt rsync, will it resume? >From the Rsync FAQ: Q. Is rsync useful for a single large file (like an iso image)? http://rsync.samba.org/rsync/fom-serve/cache/60.html I guess this clears all my doubts. -- Shanu -- - - - - - - - - - - - ( Shanu ) - - Shanker Balan http://people.exocore.com/shanu shanu at exocore dot com From owner-linux-xfs@oss.sgi.com Tue Jul 10 23:27:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B6R4D16070 for linux-xfs-outgoing; Tue, 10 Jul 2001 23:27:04 -0700 Received: from doppstadt-sbk.de ([194.173.186.8]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B6R2V16061 for ; Tue, 10 Jul 2001 23:27:02 -0700 Received: from svnt0002.doppstadt-sbk.de ([172.21.1.11]) by svfw0001.doppstadt-sbk.de with ESMTP id <119041>; Wed, 11 Jul 2001 08:26:47 +0200 Received: from pcli0001.doppstadt-sbk.de ([172.21.1.101]) by svnt0002.doppstadt-sbk.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 3SK4Q3WF; Wed, 11 Jul 2001 08:26:41 +0200 Subject: Installer for RH7.1 Alpha From: ThH To: linux-xfs@oss.sgi.com Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 11 Jul 2001 07:30:14 +0200 Message-Id: <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Is there a way to make an installer iso for RH7.1 Alpha? May be with SRPMS from 1.0.1 i386 installer. What I have to do for this way or other. From owner-linux-xfs@oss.sgi.com Tue Jul 10 23:53:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B6rQ718282 for linux-xfs-outgoing; Tue, 10 Jul 2001 23:53:26 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B6rNV18275 for ; Tue, 10 Jul 2001 23:53:24 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6B6rIx04914; Wed, 11 Jul 2001 08:53:19 +0200 Message-Id: <4.3.2.7.2.20010711085059.02b5d540@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 08:53:07 +0200 To: stimits@idcomm.com From: Seth Mos Subject: Re: XFS for Linux 1.0.1 Released Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B4B887B.89A30E14@idcomm.com> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 16:58 10-7-2001 -0600, D. Stimits wrote: >Florin Andrei wrote: > > > > On 10 Jul 2001 16:03:36 -0500, Eric Sandeen wrote: > > > SGI is pleased to announce the 1.0.1 release of XFS for Linux. > > > > That's great news! > > > > Guys, can you please make the floppy images available, so one does not > > have to download the entire ISO just to test the new floppies. > > > > -- > > Florin Andrei > >What I'd find more interesting (since floppy images can't work with some >of the possible kernel options...size gets too large) would be an ISO CD >image that is equivalent to Tom's Root Boot (rescue with everything >under the sun), but XFS based (any rescue or repair tool would be nice, >even if it is for other fs's like reiser or ext3). Such could be done >with probably a 25 MB download (10 to 15 MB with gzip -9), and provide >the ability to format, repair, etc. I mention this because I am still >working on my own custom CD rescue (I recently discovered that one big >problem was that my CD was not a "multiread" version, and could not >handle CD-RW's, only CD-R's...duh). Add to that every test I do >requiring upload/download through 56k/33k modems...I'm slowly getting >there, but it is a lesson in humility. http://www.lnx-bbc.org/ You might have more luck sticking xfs on this disk. These are 50MB large isos and contain lot's of client utils. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 00:05:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B75Ec19973 for linux-xfs-outgoing; Wed, 11 Jul 2001 00:05:14 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B75DV19965 for ; Wed, 11 Jul 2001 00:05:13 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6B756x05036; Wed, 11 Jul 2001 09:05:07 +0200 Message-Id: <4.3.2.7.2.20010711090425.03537c20@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 09:04:55 +0200 To: Shanker Balan , Linux-XFS From: Seth Mos Subject: Re: FAQ: How do i use rsync? In-Reply-To: <20010711105245.A3329@exocore.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 10:52 11-7-2001 +0530, Shanker Balan wrote: >Hello: > >Can anyone gimme the command line arguments for rsyncing the XFS >Installer 1.0.1 with 1.0.0 iso image? > >How do i construct a rsync URL using "oss.sgi.com::xfsftp" as base? > >I tried this but it did not work: > >$ rsync -avuz >oss.sgi.com::xfsftp/download/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso >RH7.1-SGI-XFS-1.0.iso >receiving file list ... link_stat >/download/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso : No such file >or directory >done >client: nothing to do > >I hope that the rsync procedure will be added to the FAQ! Will do. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 00:05:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B754u19928 for linux-xfs-outgoing; Wed, 11 Jul 2001 00:05:04 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B751V19911 for ; Wed, 11 Jul 2001 00:05:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA27108; Wed, 11 Jul 2001 09:04:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA26297; Wed, 11 Jul 2001 09:04:56 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id BCBD957306; Wed, 11 Jul 2001 09:14:06 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 55E8D25835; Wed, 11 Jul 2001 09:22:06 +0200 (CEST) Message-ID: <3B4BFA9B.EE2491E1@ch.sauter-bc.com> Date: Wed, 11 Jul 2001 09:04:59 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: "Huettner, Ewald" Cc: "'linux-xfs@oss.sgi.com'" Subject: Re: FW: nfsd-crash References: <5243EBD6FB48D51184E200A0C9A9D56014543C@srvellwangen.rand.de> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > "Huettner, Ewald" schrieb: > > <> > > Hallo, > i have a Problem at an Customer, he has an lh3000 (HP) with Redhat > Linux > 7.1 and XFS 1.0 > Kernerl 2.4.5 Did you try the provided 2.4.3 RPM's or is there a reason to use the 2.4.5? I think RedHat is 'tuning' the NFS stuff somehow. If the problem is XFS related then I don't know, didn' try it. But I have a server here in a mixed environment HP-UX/NFS, Solaris/NFS and WinNT/Samba on Mandrake-7.0 kernel 2.2.14-15mdksm without problems since more than a year now. > > The Server runs some time and then the nfsd crash`s down with errors > in > messages. The nfsd can not be restartet at the system, only reboot and What kind of errors do you get? > > reset ist ok too restart the server and the nfsd. On this Server there > > are 8 HP-UX Workstations with NFS > connectet to the Linux Server. > At the Server there are the following filesystems: > / ext2 > /boot ext2 > /data xfs > > Has anyone an workaround for this Problem???? > > Ewald Huettner > email: ehuettner@rand.de > Phone: 07961890186 > > <> > > Name: crash.zip > crash.zip Type: Zip Compressed Data > (application/x-zip-compressed) > Encoding: base64 -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Wed Jul 11 00:15:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B7Fnx21815 for linux-xfs-outgoing; Wed, 11 Jul 2001 00:15:49 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B7FlV21809 for ; Wed, 11 Jul 2001 00:15:47 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6B7FWx05094; Wed, 11 Jul 2001 09:15:35 +0200 Message-Id: <4.3.2.7.2.20010711091210.034e3590@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 09:15:22 +0200 To: Russell Cattelan , Shanker Balan From: Seth Mos Subject: Re: FAQ: How do i use rsync? Cc: Linux-XFS In-Reply-To: <3B4BE666.9972F23@thebarn.com> References: <20010711105245.A3329@exocore.com> <20010711110117.B3329@exocore.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:38 11-7-2001 -0500, Russell Cattelan wrote: >Shanker Balan wrote: > > > Hello: > > > > Shanker Balan wrote, > > > I hope that the rsync procedure will be added to the FAQ! > > > > Oh, just runing "rsync oss.sgi.com::xfsftp" will give me a listing. > > > > But i have a new prblem now - > > > > $ rsync -avuz > oss.sgi.com::xfsftp/Release-1.0.1/installer/RH7.1-SGI-XFS-1.0.1.iso > RH7.1-SGI-XFS-1.0.iso > > receiving file list ... done > > RH7.1-SGI-XFS-1.0.iso > > inflate returned -3 (0 bytes) > > unexpected EOF in read_timeout > > > > Is this a firewall issue? > > > >Try dropping the -z (compression) and see what you get... > >That is and odd error... maybe you should upgrade your rsync? rsync does not like compression in this case. Same error over here. Local copy with compression does seem to work. rsync version 2.4.6 protocol version 24 The standard included rsync with RH 7.1 Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 00:41:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B7fns24316 for linux-xfs-outgoing; Wed, 11 Jul 2001 00:41:49 -0700 Received: from cotse.com (packetderm.cotse.com [216.112.42.58]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B7fmV24312 for ; Wed, 11 Jul 2001 00:41:48 -0700 Received: from cotse.com (wetelephant.cotse.com [216.112.42.62]) by cotse.com (5.7.4/5.7.4) with SMTP id f6B7duR03325 for ; Wed, 11 Jul 2001 03:39:56 -0400 (EDT) From: alan@cotse.com Received: from Cotse Public Webmail (authenticated user alan) by freemail.cotse.com with HTTP; Wed, 11 Jul 2001 03:42:32 -0400 (EDT) Message-ID: <2bdb5efac4f0ea174353dc2735a93456@freemail.cotse.com> Date: Wed, 11 Jul 2001 03:42:32 -0400 (EDT) X-User-Agent: http://freemail.cotse.com X-Abuse-To: abuse@cotse.com Subject: xfs 1.0.1 and linux 2.4.6 To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Not to sound too bleeding edge, but I would like to begin a test project for work that involves, among other things, xfs as the filesystem. I see that there is an 8.0 mb patch difference between linux 2.4.5 and 2.4.6, so I'd prefer using the latter. The nfs and memory fixes that occurred in the days since the 2.4.6 patch was created and 2.4.5 1.0.1 release are what I am interested in really. Alternatively, does anyone know how I might convert a 2.4.5-xfs patched kernel to 2.4.6? After perusing manpages for patch, diff, and diff3, I haven't a clue as to how I could create a patch for one modified kernel version, that would take one set of modifications (xfs) and apply them to what is essentially a foriegn environment (2.4.6) for it. Ideas anyone From owner-linux-xfs@oss.sgi.com Wed Jul 11 01:05:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B858n26539 for linux-xfs-outgoing; Wed, 11 Jul 2001 01:05:08 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B856V26533 for ; Wed, 11 Jul 2001 01:05:06 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6B855x05368 for ; Wed, 11 Jul 2001 10:05:05 +0200 Message-Id: <4.3.2.7.2.20010711100317.035ea998@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 10:04:54 +0200 To: linux-xfs list From: Seth Mos Subject: FAQ update Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Added extra info about large files, added missing aic7xxx compile error, rsync instructions added for downloading from xfsftp. If I missed anything else, shout at me :D May I suggest setting up a symlink on the ftp site which is called "latest"? Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 01:13:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B8D1727293 for linux-xfs-outgoing; Wed, 11 Jul 2001 01:13:01 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B8CxV27289 for ; Wed, 11 Jul 2001 01:13:00 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6B8Cwx05398 for ; Wed, 11 Jul 2001 10:12:58 +0200 Message-Id: <4.3.2.7.2.20010711101131.03530578@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 10:12:47 +0200 To: linux-xfs list From: Seth Mos Subject: Folk project kernel Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk You need the latest kernel with lot's of patches? Maybe you should look up on th folk project. http://folk.sourceforge.net/ And XFS 1.0.1 is included as well as -ac1 according to the webpage. Have fun. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 02:02:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B92Bu31629 for linux-xfs-outgoing; Wed, 11 Jul 2001 02:02:11 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B92AV31624 for ; Wed, 11 Jul 2001 02:02:10 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip30.idcomm.com [209.60.72.157]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6B95Ea14134 for ; Wed, 11 Jul 2001 03:05:14 -0600 Message-ID: <3B4C1694.7FD04295@idcomm.com> Date: Wed, 11 Jul 2001 03:04:20 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> <4.3.2.7.2.20010711085059.02b5d540@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > At 16:58 10-7-2001 -0600, D. Stimits wrote: > >Florin Andrei wrote: > > > > > > On 10 Jul 2001 16:03:36 -0500, Eric Sandeen wrote: > > > > SGI is pleased to announce the 1.0.1 release of XFS for Linux. > > > > > > That's great news! > > > > > > Guys, can you please make the floppy images available, so one does not > > > have to download the entire ISO just to test the new floppies. > > > > > > -- > > > Florin Andrei > > > >What I'd find more interesting (since floppy images can't work with some > >of the possible kernel options...size gets too large) would be an ISO CD > >image that is equivalent to Tom's Root Boot (rescue with everything > >under the sun), but XFS based (any rescue or repair tool would be nice, > >even if it is for other fs's like reiser or ext3). Such could be done > >with probably a 25 MB download (10 to 15 MB with gzip -9), and provide > >the ability to format, repair, etc. I mention this because I am still > >working on my own custom CD rescue (I recently discovered that one big > >problem was that my CD was not a "multiread" version, and could not > >handle CD-RW's, only CD-R's...duh). Add to that every test I do > >requiring upload/download through 56k/33k modems...I'm slowly getting > >there, but it is a lesson in humility. > > http://www.lnx-bbc.org/ You might have more luck sticking xfs on this disk. > These are 50MB large isos and contain lot's of client utils. This seems rather interesting, I can see how it might prove incredibly flexible. I am curious about something (I did not download it yet)...it uses a compressed filesystem. What form of compression is this? Is it the same form as a bzImage uses? Is it some form of customized filesystem, or just the loopback changes to support it? Apparently lnx.img is an entire compressed filesystem, mounted as /boot/.....can any normal vmlinuz style image be used there (are there special naming restrictions too)? And biggest question...it seems that it is designed to run some of its commands directly on a CD, like makeBBC prep...is it mandatory to have the CD burner on the machine doing the creation, or can an iso simply be created on one machine and burned on another? It seems that it could make an excellent rescue system for every filesystem type under the sun. D. Stimits, stimits@idcomm.com > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 02:02:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B92iA31721 for linux-xfs-outgoing; Wed, 11 Jul 2001 02:02:44 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B92fV31715 for ; Wed, 11 Jul 2001 02:02:41 -0700 Received: from ii.uib.no (eik.ii.uib.no [129.177.16.3]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id CAA00566 for ; Wed, 11 Jul 2001 02:02:40 -0700 (PDT) mail_from (janfrode@ii.uib.no) Received: from apal-192.ii.uib.no (apal.ii.uib.no) [129.177.192.27] by ii.uib.no with esmtp (Exim 3.03) id 15KFlN-0006FO-00 for ; Wed, 11 Jul 2001 10:54:29 +0200 Received: (from janfrode@localhost) by apal.ii.uib.no (8.9.3+Sun/8.9.3) id KAA21846 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 10:54:29 +0200 (MEST) Date: Wed, 11 Jul 2001 10:54:29 +0200 From: Jan-Frode Myklebust To: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released Message-ID: <20010711105428.A21601@ii.uib.no> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107102103.f6AL3am18531@jen.americas.sgi.com>; from sandeen@sgi.com on Tue, Jul 10, 2001 at 04:03:36PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm trying to get this installed on a Dell PowerEdge 4400, and am having some problems. I never could get the XFS-1.0 release into this, so it's a standard RH 7.1 system at the moment. http://www.dell.com/us/en/esg/topics/esg_pedge_towermain_servers_1_pedge_4400.htm The kernel-smp-2.4.5-SGI_XFS_1.0.1.i686.rpm doesn't include the aacraid patch, so I have to use the kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm I Install the kernel: # rpm -ivh kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm make the initrd image, and move it to /boot: # mkinitrd initrd-2.4.3-SGI_XFS_1.0.1smp.img 2.4.3-SGI_XFS_1.0.1smp Add an entry to /etc/lilo.conf: image=/boot/vmlinux-2.4.3-SGI_XFS_1.0.1smp label=linux-xfs initrd=/boot/initrd-2.4.3-SGI_XFS_1.0.1smp.img read-only root=/dev/sda1 but when I run lilo I get the message: # lilo Added linux * Fatal: Kernel doesn't support initial RAM disks Will I have to build a new kernel from source to fix this? BTW: what's the latest "recommended" version in cvs? Does anybody know why the aacraid module isn't in the linus-tree? -jf From owner-linux-xfs@oss.sgi.com Wed Jul 11 02:10:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B9AwI32696 for linux-xfs-outgoing; Wed, 11 Jul 2001 02:10:58 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B9AuV32690 for ; Wed, 11 Jul 2001 02:10:56 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip30.idcomm.com [209.60.72.157]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6B9E1a14567 for ; Wed, 11 Jul 2001 03:14:01 -0600 Message-ID: <3B4C18A3.185769CD@idcomm.com> Date: Wed, 11 Jul 2001 03:13:07 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jan-Frode Myklebust wrote: > > I'm trying to get this installed on a Dell > PowerEdge 4400, and am having some problems. I never > could get the XFS-1.0 release into this, so it's a > standard RH 7.1 system at the moment. > > http://www.dell.com/us/en/esg/topics/esg_pedge_towermain_servers_1_pedge_4400.htm > > The kernel-smp-2.4.5-SGI_XFS_1.0.1.i686.rpm doesn't > include the aacraid patch, so I have to use the > kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm > > I Install the kernel: > > # rpm -ivh kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm > > make the initrd image, and move it to /boot: > > # mkinitrd initrd-2.4.3-SGI_XFS_1.0.1smp.img 2.4.3-SGI_XFS_1.0.1smp > > Add an entry to /etc/lilo.conf: > > image=/boot/vmlinux-2.4.3-SGI_XFS_1.0.1smp > label=linux-xfs > initrd=/boot/initrd-2.4.3-SGI_XFS_1.0.1smp.img > read-only > root=/dev/sda1 > > but when I run lilo I get the message: > > # lilo > Added linux * > Fatal: Kernel doesn't support initial RAM disks Don't trust rpm to update the kernel. Run rpm -i on the source rpm, then get the tarball out of /usr/src/redhat/SOURCES/, do a cp -adpR on whatever subdir it is to the usual /usr/src/ location after backing up (and completely moving out of the way) any old kernels. Then run make menuconfig (or some config) manually before doing the rest. You have to select initial ram disk support. I also don't know if it is a failure to run lilo and point it at an uncompressed kernel, but you probably should copy the bzImage over as vmlinuz and point lilo at that instead of the uncompressed vmlinux image (keep vmlinux for debugging). Building from source is about the only way to go for any kernel install at all. At least I think so. If you have a requirement to access your raid controller during bootup, you will want to specifically name any raid modules in your mkinitrd command (unless it is compiled directly in). D. Stimits, stimits@idcomm.com > > Will I have to build a new kernel from source to fix > this? BTW: what's the latest "recommended" version > in cvs? > > Does anybody know why the aacraid module isn't in the > linus-tree? > > -jf From owner-linux-xfs@oss.sgi.com Wed Jul 11 02:34:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6B9YBi02356 for linux-xfs-outgoing; Wed, 11 Jul 2001 02:34:11 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6B9Y6V02350 for ; Wed, 11 Jul 2001 02:34:07 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id LAA24465; Wed, 11 Jul 2001 11:34:03 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id LAA09470; Wed, 11 Jul 2001 11:34:03 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 3BD5357306; Wed, 11 Jul 2001 11:41:15 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id DC61225835; Wed, 11 Jul 2001 11:49:14 +0200 (CEST) Message-ID: <3B4C1D17.6FB2C582@ch.sauter-bc.com> Date: Wed, 11 Jul 2001 11:32:07 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Jan-Frode Myklebust Cc: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> Content-Type: multipart/mixed; boundary="------------E6ABE20AE9272B50F7A4CC5C" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dies ist eine mehrteilige Nachricht im MIME-Format. --------------E6ABE20AE9272B50F7A4CC5C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jan-Frode Myklebust schrieb: > > I'm trying to get this installed on a Dell > PowerEdge 4400, and am having some problems. I never > could get the XFS-1.0 release into this, so it's a > standard RH 7.1 system at the moment. > > http://www.dell.com/us/en/esg/topics/esg_pedge_towermain_servers_1_pedge_4400.htm > > The kernel-smp-2.4.5-SGI_XFS_1.0.1.i686.rpm doesn't > include the aacraid patch, so I have to use the > kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm > > I Install the kernel: > > # rpm -ivh kernel-smp-2.4.3-SGI_XFS_1.0.1.i686.rpm > > make the initrd image, and move it to /boot: > > # mkinitrd initrd-2.4.3-SGI_XFS_1.0.1smp.img 2.4.3-SGI_XFS_1.0.1smp > > Add an entry to /etc/lilo.conf: > > image=/boot/vmlinux-2.4.3-SGI_XFS_1.0.1smp > label=linux-xfs > initrd=/boot/initrd-2.4.3-SGI_XFS_1.0.1smp.img > read-only > root=/dev/sda1 > > but when I run lilo I get the message: > > # lilo > Added linux * > Fatal: Kernel doesn't support initial RAM disks Hm, your lilo.conf should look like this :-) image=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp ^ > > Will I have to build a new kernel from source to fix > this? BTW: what's the latest "recommended" version > in cvs? > > Does anybody know why the aacraid module isn't in the > linus-tree? As found in this list the aacraid is a port of the WinNT driver. Lets hope such thing will never go into the official kernel. > > -jf My tip: Dump the Adaptec RAID to /dev/null, connect the disks to the onboard UXXX SCSI and put SoftRAID 1,5 on it and enjoy. This is what I do with DELL servers and performance is impressive. I'm using the attached scripts to monitor the softraid. Simon -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] --------------E6ABE20AE9272B50F7A4CC5C Content-Type: application/octet-stream; name="raidmon.init-1.0.7" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="raidmon.init-1.0.7" IyEvYmluL3NoCiMKIyBjaGtjb25maWc6CTIzNDUgNDAgNjAKIyBkZXNjcmlwdGlvbjoJUmFp ZG1vbiBtb25pdG9ycyBhbGwgc29mdHdhcmUgUkFJRCBhcnJheXMgXAojCQlhbmQgc3RhcnRz IHRvIGJlZXAgd2hlbiBhIGRpc2sgZmFpbHMuCgojIEF1dGhvcjoJU2ltb24gTWF0dGVyIDxz aW1peEBkYXRhY29tbS5jaD4KIyBWZXJzaW9uOgkxLjAuNwoKIyBUbyBjaGVjayBwZXJpb2Rp Y2FsbHkgdGhhdCByYWlkbW9uIGlzIGFsaXZlLCBydW4gYSBjcm9uIGpvYgojIHdpdGggInRv dWNoIC92YXIvbG9jay9zdWJzeXMvcmFpZG1vbi5jcm9uIgoKIyBTb3VyY2UgZnVuY3Rpb24g bGlicmFyeQppZiBbIC1mIC9ldGMvaW5pdC5kL2Z1bmN0aW9ucyBdOyB0aGVuCiAgLiAvZXRj L2luaXQuZC9mdW5jdGlvbnMKZWxpZiBbIC1mIC9ldGMvcmMuZC9pbml0LmQvZnVuY3Rpb25z IF07IHRoZW4KICAuIC9ldGMvcmMuZC9pbml0LmQvZnVuY3Rpb25zCmVsc2UKICBleGl0IDAK ZmkKCiMgVGhpcyBpcyBvdXIgc2VydmljZSBuYW1lCkJBU0VOQU1FPWBiYXNlbmFtZSAkMGAK aWYgWyAtTCAkMCBdOyB0aGVuCiAgQkFTRU5BTUU9YGZpbmQgJDAgLW5hbWUgJEJBU0VOQU1F IC1wcmludGYgJWxgCiAgQkFTRU5BTUU9YGJhc2VuYW1lICRCQVNFTkFNRWAKZmkKCiMgU291 cmNlIHNlcnZpY2UgY29uZmlndXJhdGlvbi4KaWYgWyAtZiAvZXRjL3N5c2NvbmZpZy8kQkFT RU5BTUUgXTsgdGhlbgogIC4gL2V0Yy9zeXNjb25maWcvJEJBU0VOQU1FCmVsc2UKICBlY2hv ICIkQkFTRU5BTUU6IGNvbmZpZ2ZpbGUgL2V0Yy9zeXNjb25maWcvJEJBU0VOQU1FIGRvZXMg Tk9UIGV4aXN0ICEiCiAgZXhpdCAxCmZpCgpSRVRWQUw9MAoKc2VuZF9yZXBvcnQoKSB7CiAg aWYgWyAhIC16ICIkQURNSU4iIF07IHRoZW4KICAgIHsKICAgICAgZWNobyAiVG86ICRBRE1J TiIKICAgICAgaWYgWyAhIC16ICIkQ0NBRE1JTiIgXTsgdGhlbgogICAgICAgIGVjaG8gIkNj OiAkQ0NBRE1JTiIKICAgICAgZmkKICAgICAgZWNobyAiU3ViamVjdDogJEJBU0VOQU1FIG9u IGBob3N0bmFtZWAiCiAgICAgIGVjaG8gJCoKICAgICAgZWNobwogICAgICBpZiBbICRGQUlM RURESVNLUyAtZ3QgJERFQlVHIC1vICRSRVNZTkNESVNLUyAtZ3QgXAogICAgICAgICRERUJV RyBdOyB0aGVuCiAgICAgICAgZWNobyAiKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqIgogICAgICAgIGVjaG8gIioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKiIKICAgICAgICBlY2hvICIqKiAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKioiCiAgICAgICAgZWNobyAi KiogIFdBUk5JTkcgISEgV0FSTklORyAhISBXQVJOSU5HICEhIFdBUk5JTkcgICoqIgogICAg ICAgIGVjaG8gIioqICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAqKiIKICAgICAgICBlY2hvICIqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioiCiAgICAgICAgZWNobyAiKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqIgogICAgICAgIGVjaG8KICAgICAgZmkKICAgICAg ZWNobyAiRmFpbGVkIGRpc2tzIGluIGFycmF5cyAgICA6ICRGQUlMRURESVNLUyIKICAgICAg ZWNobyAiVW5zeW5jZWQgcmFpZCBhcnJheXMgICAgICA6ICRSRVNZTkNESVNLUyIKICAgICAg ZWNobyAiUnVubmluZyByYWlkIGFycmF5cyAgICAgICA6ICRSQUlERElTS1MiCiAgICAgIGVj aG8KICAgICAgZWNobyAiTWluLiByZWNvbnN0cnVjdGlvbiBzcGVlZCA6IGBzeXNjdGwgLW4g ZGV2LnJhaWQuc3BlZWRfbGltaXRfbWluYGsvc2VjIgogICAgICBlY2hvICJNYXguIHJlY29u c3RydWN0aW9uIHNwZWVkIDogYHN5c2N0bCAtbiBkZXYucmFpZC5zcGVlZF9saW1pdF9tYXhg ay9zZWMiCiAgICAgIGVjaG8KICAgICAgY2F0IC9wcm9jL21kc3RhdAogICAgfSB8ICRTRU5E TUFJTCAtdCAtZiAkRlJPTQogIGZpCn0KCnNhdmVfcmFpZHN0YXR1cygpIHsKICBMQVNURkFJ TEVERElTS1M9JEZBSUxFRERJU0tTCiAgTEFTVFJFU1lOQ0RJU0tTPSRSRVNZTkNESVNLUwog IExBU1RSQUlERElTS1M9JFJBSURESVNLUwp9CgpnZXRfcmFpZHN0YXR1cygpIHsKICBGQUlM RURESVNLUz1gZ3JlcCBibG9ja3MgL3Byb2MvbWRzdGF0IHwgZ3JlcCAtYyBfYAogIFJFU1lO Q0RJU0tTPWBncmVwIC1jIHJlc3luYyAvcHJvYy9tZHN0YXRgCiAgUkFJRERJU0tTPWBncmVw IC1jIG1kIC9wcm9jL21kc3RhdGAKfQoKcmFpZF9tb24oKSB7CiAgTEFTVEZBSUxFRERJU0tT PTAKICBMQVNUUkVTWU5DRElTS1M9MAogIExBU1RSQUlERElTS1M9MAogIGdldF9yYWlkc3Rh dHVzCiAgc2VuZF9yZXBvcnQgIkxpbnV4IFNvZnRSQUlEIG1vbml0b3Jpbmcgc2VydmljZSBo YXMgYmVlbiBzdGFydGVkIgogIHNhdmVfcmFpZHN0YXR1cwogIHdoaWxlIFsgLWYgL3Zhci9s b2NrL3N1YnN5cy8kQkFTRU5BTUUgXTsgZG8KICAgIGdldF9yYWlkc3RhdHVzCiAgICBpZiBb ICRGQUlMRURESVNLUyAtbmUgJExBU1RGQUlMRURESVNLUyAtbyAkUkVTWU5DRElTS1MgLW5l IFwKICAgICAgJExBU1RSRVNZTkNESVNLUyAtbyAkUkFJRERJU0tTIC1uZSAkTEFTVFJBSURE SVNLUyBdOyB0aGVuCiAgICAgIHNlbmRfcmVwb3J0ICJMaW51eCBTb2Z0UkFJRCBzdGF0dXMg aGFzIGNoYW5nZWQiCiAgICAgIHNhdmVfcmFpZHN0YXR1cwogICAgZmkKICAgIGlmIFsgLWYg L3Zhci9sb2NrL3N1YnN5cy8kQkFTRU5BTUUuY3JvbiBdOyB0aGVuCiAgICAgIHNlbmRfcmVw b3J0ICJMaW51eCBTb2Z0UkFJRCBzdGF0dXMgcmVwb3J0IgogICAgICBybSAtZiAvdmFyL2xv Y2svc3Vic3lzLyRCQVNFTkFNRS5jcm9uCiAgICBmaQogICAgaWYgWyAkRkFJTEVERElTS1Mg LWVxICRERUJVRyAtYSAkUkVTWU5DRElTS1MgLWVxICRERUJVRyBdOyB0aGVuCiAgICAgIHNs ZWVwIDUKICAgIGVsc2UKICAgICAgaWYgWyAiJFFVSUVUIiAhPSAieWVzIiBdOyB0aGVuCiAg ICAgICAgZWNobyAtZW4gJ1xhJwogICAgICBmaQogICAgICB1c2xlZXAgMzAwMDAwCiAgICBm aQogIGRvbmUKICBzZW5kX3JlcG9ydCAiTGludXggU29mdFJBSUQgbW9uaXRvcmluZyBzZXJ2 aWNlIGhhcyBiZWVuIHNodXRkb3duIgp9CgpzdGFydF9tb24oKSB7CiAgaWYgWyAhIC1mIC92 YXIvbG9jay9zdWJzeXMvJEJBU0VOQU1FIF07IHRoZW4KICAgIHRvdWNoIC92YXIvbG9jay9z dWJzeXMvJEJBU0VOQU1FCiAgICBhY3Rpb24gIlN0YXJ0aW5nICRCQVNFTkFNRSBzZXJ2aWNl czogIiB0cnVlCiAgICByYWlkX21vbiAmCiAgZmkKfQogCnN0b3BfbW9uKCkgewogIGlmIFsg LWYgL3Zhci9sb2NrL3N1YnN5cy8kQkFTRU5BTUUgXTsgdGhlbgogICAgcm0gLWYgL3Zhci9s b2NrL3N1YnN5cy8kQkFTRU5BTUUKICAgIGFjdGlvbiAiU2h1dHRpbmcgZG93biAkQkFTRU5B TUUgc2VydmljZXM6ICIgc2xlZXAgNgogIGZpCn0KCnJlc3RhcnQoKSB7CiAgc3RvcF9tb24K ICBzdGFydF9tb24KfQoKY29uZHJlc3RhcnQoKSB7CiAgWyAtZSAvdmFyL2xvY2svc3Vic3lz LyRCQVNFTkFNRSBdICYmIHJlc3RhcnQgfHwgOgp9CgpyaHN0YXR1cygpIHsKICBzdGF0dXMg JEJBU0VOQU1FCn0KCiMgU2VlIGhvdyB3ZSB3ZXJlIGNhbGxlZC4KY2FzZSAiJDEiIGluCiAg c3RhcnQpCiAgICBzdGFydF9tb24KICAgIDs7CiAgc3RvcCkKICAgIHN0b3BfbW9uCiAgICA7 OwogIHN0YXR1cykKICAgIHJoc3RhdHVzCiAgICA7OwogIHJlc3RhcnQpCiAgICByZXN0YXJ0 CiAgICA7OwogIGNvbmRyZXN0YXJ0KQogICAgY29uZHJlc3RhcnQKICAgIDs7CiAgKikKICAg IGVjaG8gIlVzYWdlOiAkQkFTRU5BTUUge3N0YXJ0fHN0b3B8c3RhdHVzfHJlc3RhcnR8Y29u ZHJlc3RhcnR9IgogICAgZXhpdCAxCmVzYWMKIApleGl0ICRSRVRWQUwK --------------E6ABE20AE9272B50F7A4CC5C Content-Type: application/octet-stream; name="sysctl.conf.raidsync" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="sysctl.conf.raidsync" IyBGb3JjZSBSQUlEIHJlY29uc3RydWN0aW9uIHRvIHJ1biB3aXRoIGhpZ2ggcHJpb3JpdHkK ZGV2LnJhaWQuc3BlZWRfbGltaXRfbWluID0gMTAwMDAKI2Rldi5yYWlkLnNwZWVkX2xpbWl0 X21heCA9IDEwMDAwMAo= --------------E6ABE20AE9272B50F7A4CC5C Content-Type: application/octet-stream; name="raidmon.cfg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="raidmon.cfg" IyBTeXN0ZW0gYWRtaW4gbWFpbCBhZHJlc3MsIGxlYXZlIGVtcHR5IHRvIGRpc2FibGUgbWFp bCBub3RpZmljYXRpb24uCkFETUlOPXJvb3RAbG9jYWxob3N0CiMgUGVyc29ucyB0byBDYyB0 aGUgbWVzc2FnZXMsIGV4LiAiam9lMUBsb2NhbGhvc3QsIGpvZTJAbG9jYWxob3N0IgpDQ0FE TUlOPQpGUk9NPXJhaWRtb25AbG9jYWxob3N0CiMKIyBTZW5kbWFpbCBiaW5hcnkKU0VORE1B SUw9L3Vzci9zYmluL3NlbmRtYWlsCiMKIyBUaGlzIGlzIDAgZm9yIG5vcm1hbCBvcGVyYXRp b24KREVCVUc9MAojIFRvIGRpc2FibGUgYmVlcGVyLCBzZXQgdGhpcyB0byAieWVzIgpRVUlF VD1ubwo= --------------E6ABE20AE9272B50F7A4CC5C-- From owner-linux-xfs@oss.sgi.com Wed Jul 11 03:06:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BA64x05553 for linux-xfs-outgoing; Wed, 11 Jul 2001 03:06:04 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BA61V05543 for ; Wed, 11 Jul 2001 03:06:01 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6BA5vx05917; Wed, 11 Jul 2001 12:05:57 +0200 Message-Id: <4.3.2.7.2.20010711120153.02a5d9a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 12:05:46 +0200 To: stimits@idcomm.com From: Seth Mos Subject: LNX-BBC rescue disk (Re: XFS for Linux 1.0.1 Released) Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B4C1694.7FD04295@idcomm.com> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <994802395.19620.19.camel@stantz.corp.sgi.com> <4.3.2.7.2.20010711085059.02b5d540@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 03:04 11-7-2001 -0600, D. Stimits wrote: >Seth Mos wrote: > > > > At 16:58 10-7-2001 -0600, D. Stimits wrote: > > >Florin Andrei wrote: > > http://www.lnx-bbc.org/ You might have more luck sticking xfs on this disk. > > These are 50MB large isos and contain lot's of client utils. > >This seems rather interesting, I can see how it might prove incredibly >flexible. I am curious about something (I did not download it yet)...it >uses a compressed filesystem. What form of compression is this? Is it it uses cloop which over time will be replaced with the now standard cramfs. cloop is originally from Rusty Russel but is not available for 2.4 IIRC. >the same form as a bzImage uses? Is it some form of customized >filesystem, or just the loopback changes to support it? Apparently >lnx.img is an entire compressed filesystem, mounted as /boot/.....can >any normal vmlinuz style image be used there (are there special naming >restrictions too)? With the patches to mount the cloop fs. >And biggest question...it seems that it is designed to run some of its >commands directly on a CD, like makeBBC prep...is it mandatory to have >the CD burner on the machine doing the creation, or can an iso simply be >created on one machine and burned on another? It seems that it could >make an excellent rescue system for every filesystem type under the sun. No, it makes a .iso file which you can then burn. They make nightly ISO images when their tree changes. I am looking into but I don't have everything setup yet to make a modified version of it. Greets -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 03:19:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BAJPm06757 for linux-xfs-outgoing; Wed, 11 Jul 2001 03:19:25 -0700 Received: from tiny.int.franksintl.nl (goblin.franksintl.nl [195.193.231.154]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BAJMV06753 for ; Wed, 11 Jul 2001 03:19:23 -0700 Received: from ries (cp35.int.franksintl.nl [192.168.4.249]) by tiny.int.franksintl.nl (8.11.4/8.11.4/Debian 8.9.3-21) with ESMTP id f6BABiD12851; Wed, 11 Jul 2001 12:11:44 +0200 From: "Ries van Twisk" To: Jan-Frode Myklebust , linux-xfs@oss.sgi.com Date: Wed, 11 Jul 2001 12:11:43 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: XFS for Linux 1.0.1 Released Reply-to: ries@franksintl.nl Message-ID: <3B4C427F.7702.448435@localhost> In-reply-to: <20010711105428.A21601@ii.uib.no> References: <200107102103.f6AL3am18531@jen.americas.sgi.com>; from sandeen@sgi.com on Tue, Jul 10, 2001 at 04:03:36PM -0500 X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have paches for the raid controllers. Currently it's runing for 14 day's now without problems. I also applied the XFS patch to the Linux 2.4.5 kernel. It all compiles fine now. It's not tested on my PE 2400 server yet but the kernel itself works great on a test IDE systeem. I'm currently buzy to compiling Samba aswell but I still have some problems with ACL. RIes From owner-linux-xfs@oss.sgi.com Wed Jul 11 03:56:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BAukV09545 for linux-xfs-outgoing; Wed, 11 Jul 2001 03:56:46 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BAuiV09540 for ; Wed, 11 Jul 2001 03:56:44 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6BAucx06269; Wed, 11 Jul 2001 12:56:38 +0200 Message-Id: <4.3.2.7.2.20010711124947.032a2cb0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 12:56:17 +0200 To: ries@franksintl.nl, Jan-Frode Myklebust , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: XFS for Linux 1.0.1 Released In-Reply-To: <3B4C427F.7702.448435@localhost> References: <20010711105428.A21601@ii.uib.no> <200107102103.f6AL3am18531@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:11 11-7-2001 +0200, Ries van Twisk wrote: >I have paches for the raid controllers. >Currently it's runing for 14 day's now without problems. The problem is not really with the raid hardware itself but the driver. When they resolve that we will use it again. There have been reports of corruption under high load. See http://domsch.com/linux/ >I also applied the XFS patch to the Linux 2.4.5 kernel. >It all compiles fine now. Always make sure to use kgcc for production systems. >It's not tested on my PE 2400 server yet but the kernel itself works great on >a test IDE systeem. It should work fine, we have two 2450 servers running at work but with a AMI megaraid. I got tired of each patching my kernel for every new version with the aacraid patch. >I'm currently buzy to compiling Samba aswell but I still have some problems >with ACL. 2.2.1 I presume? I did download it but I will have to see of it compiles under NCR Unix first. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 04:19:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BBJSW12400 for linux-xfs-outgoing; Wed, 11 Jul 2001 04:19:28 -0700 Received: from tiny.int.franksintl.nl (goblin.franksintl.nl [195.193.231.154]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BBJPV12388 for ; Wed, 11 Jul 2001 04:19:25 -0700 Received: from ries (cp35.int.franksintl.nl [192.168.4.249]) by tiny.int.franksintl.nl (8.11.4/8.11.4/Debian 8.9.3-21) with ESMTP id f6BBIgD13449; Wed, 11 Jul 2001 13:18:42 +0200 From: "Ries van Twisk" To: Seth Mos , linux-xfs@oss.sgi.com Date: Wed, 11 Jul 2001 13:18:40 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: XFS for Linux 1.0.1 Released Reply-to: ries@franksintl.nl Message-ID: <3B4C5230.17148.81D3D9@localhost> In-reply-to: <4.3.2.7.2.20010711124947.032a2cb0@pop.xs4all.nl> References: <3B4C427F.7702.448435@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk O>Currently it's runing for 14 day's now without problems. > > The problem is not really with the raid hardware itself but the driver. > When they resolve that we will use it again. There have been reports of > corruption under high load. See http://domsch.com/linux/ Th only problem with data curruption are the access database file but that is really a Samba problem. So far no problem found. But my system runs under low loads about 25 Samba users on a 10Mb network. > >I also applied the XFS patch to the Linux 2.4.5 kernel. > >It all compiles fine now. > > Always make sure to use kgcc for production systems. Never know that there was a kgcc version! I just use gcc version 2.95.2. > > >It's not tested on my PE 2400 server yet but the kernel itself works great on > >a test IDE systeem. > > It should work fine, we have two 2450 servers running at work but with a > AMI megaraid. I got tired of each patching my kernel for every new version > with the aacraid patch. I just upgraded it to 2.4.5 and want to install xfs on it as soon as Samba compiles fine with acl from xfs. That I'll leave it alone again. > > >I'm currently buzy to compiling Samba aswell but I still have some problems > >with ACL. > > 2.2.1 I presume? I did download it but I will have to see of it compiles > under NCR Unix first. Yes a 2.2.1 version. But it does not compile with acl support :-( Samba expect the files in sys/ and not in acl/ and the header file are different. Ries From owner-linux-xfs@oss.sgi.com Wed Jul 11 04:57:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BBvE116170 for linux-xfs-outgoing; Wed, 11 Jul 2001 04:57:14 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BBvCV16166 for ; Wed, 11 Jul 2001 04:57:12 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6BBv9x06561; Wed, 11 Jul 2001 13:57:09 +0200 Message-Id: <4.3.2.7.2.20010711135130.032a87d8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 13:56:47 +0200 To: ries@franksintl.nl, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: XFS for Linux 1.0.1 Released In-Reply-To: <3B4C5230.17148.81D3D9@localhost> References: <4.3.2.7.2.20010711124947.032a2cb0@pop.xs4all.nl> <3B4C427F.7702.448435@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 13:18 11-7-2001 +0200, Ries van Twisk wrote: >O>Currently it's runing for 14 day's now without problems. > > > > The problem is not really with the raid hardware itself but the driver. > > When they resolve that we will use it again. There have been reports of > > corruption under high load. See http://domsch.com/linux/ >Th only problem with data curruption are the access database file but that is >really a Samba problem. So far no problem found. But my system runs under >low loads about 25 Samba users on a 10Mb network. That is a low load. > > >I also applied the XFS patch to the Linux 2.4.5 kernel. > > >It all compiles fine now. > > > > Always make sure to use kgcc for production systems. >Never know that there was a kgcc version! I just use gcc version 2.95.2. What distribution is this? If it is debian or SuSE I recomend upgrading your compiler to at least 2.95.3 or 4. You can have hung processes or file system corruption when using the older compiler. kgcc is actually a redhat-ism. But it is just gcc 2.91-66 or egcs 1.1.2. If you can get that you are safe. > > >It's not tested on my PE 2400 server yet but the kernel itself works > great on > > >a test IDE systeem. > > > > It should work fine, we have two 2450 servers running at work but with a > > AMI megaraid. I got tired of each patching my kernel for every new version > > with the aacraid patch. >I just upgraded it to 2.4.5 and want to install xfs on it as soon as Samba >compiles fine with acl from xfs. That I'll leave it alone again. > > > > >I'm currently buzy to compiling Samba aswell but I still have some > problems > > >with ACL. > > > > 2.2.1 I presume? I did download it but I will have to see of it compiles > > under NCR Unix first. >Yes a 2.2.1 version. But it does not compile with acl support :-( > >Samba expect the files in sys/ and not in acl/ and the header file are >different. Yes these files have moved. You may be able to specify the location with a --with-acl=/usr/include/acl or something like that. If not, you will have to walk through the code to see where the configure script is looking and change that. I guess the samba folks were probably caught off guard. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 05:27:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BCRsN20354 for linux-xfs-outgoing; Wed, 11 Jul 2001 05:27:54 -0700 Received: from ii.uib.no (eik.ii.uib.no [129.177.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BCRqV20349 for ; Wed, 11 Jul 2001 05:27:52 -0700 Received: from apal-192.ii.uib.no (apal.ii.uib.no) [129.177.192.27] by ii.uib.no with esmtp (Exim 3.03) id 15KJ5r-0001Mh-00 for ; Wed, 11 Jul 2001 14:27:51 +0200 Received: (from janfrode@localhost) by apal.ii.uib.no (8.9.3+Sun/8.9.3) id OAA26967 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 14:27:51 +0200 (MEST) Date: Wed, 11 Jul 2001 14:27:50 +0200 From: Jan-Frode Myklebust To: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released Message-ID: <20010711142750.A26861@ii.uib.no> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C1D17.6FB2C582@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B4C1D17.6FB2C582@ch.sauter-bc.com>; from simon.matter@ch.sauter-bc.com on Wed, Jul 11, 2001 at 11:32:07AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hm, your lilo.conf should look like this :-) > image=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp Of course it had to be a stupid mistake like that when I finally tried to get help.. Thanks, and thanks for the monitor-scripts. -jf From owner-linux-xfs@oss.sgi.com Wed Jul 11 05:34:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BCYNh21375 for linux-xfs-outgoing; Wed, 11 Jul 2001 05:34:23 -0700 Received: from tiny.int.franksintl.nl (goblin.franksintl.nl [195.193.231.154]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BCYLV21371 for ; Wed, 11 Jul 2001 05:34:22 -0700 Received: from ries (cp35.int.franksintl.nl [192.168.4.249]) by tiny.int.franksintl.nl (8.11.4/8.11.4/Debian 8.9.3-21) with ESMTP id f6BCTKD16063; Wed, 11 Jul 2001 14:29:20 +0200 From: "Ries van Twisk" To: Seth Mos , linux-xfs@oss.sgi.com Date: Wed, 11 Jul 2001 14:29:18 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: XFS for Linux 1.0.1 Released Reply-to: ries@franksintl.nl Message-ID: <3B4C62BE.32738.C28124@localhost> In-reply-to: <4.3.2.7.2.20010711135130.032a87d8@pop.xs4all.nl> References: <3B4C5230.17148.81D3D9@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk (We are going a bit off topic here....) > > What distribution is this? If it is debian or SuSE I recomend upgrading > your compiler to at least 2.95.3 or 4. > You can have hung processes or file system corruption when using the older > compiler. kgcc is actually a redhat-ism. But it is just gcc 2.91-66 or egcs > 1.1.2. If you can get that you are safe. It's a Debian distro with gg verion 2.95.2, this version always worked for me. Is there any real good reason to upgrade to 2.95.3? > > Yes these files have moved. You may be able to specify the location with a > --with-acl=/usr/include/acl or something like that. If not, you will have > to walk through the code to see where the configure script is looking and > change that. I guess the samba folks were probably caught off guard. > I'll see what I can do but this really should go to the samba mailing list. Ries From owner-linux-xfs@oss.sgi.com Wed Jul 11 05:37:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BCb6621764 for linux-xfs-outgoing; Wed, 11 Jul 2001 05:37:06 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BCa8V21649 for ; Wed, 11 Jul 2001 05:36:09 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15KJDg-0000z6-00; Wed, 11 Jul 2001 14:36:02 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6BCZou18272; Wed, 11 Jul 2001 08:35:50 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: ThH Cc: linux-xfs@oss.sgi.com Subject: Re: Installer for RH7.1 Alpha References: <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 11 Jul 2001 08:35:49 -0400 In-Reply-To: <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> Message-ID: Lines: 16 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "ThH" == ThH writes: ThH> Is there a way to make an installer iso for RH7.1 Alpha? May be ThH> with SRPMS from 1.0.1 i386 installer. What I have to do for this ThH> way or other. It's on my list of things to do. Still waiting for my replacement Alpha to arrive, though. But yes. Effectively you need to respin the SRPMS on the XFS 1.0.1 iso for Alpha. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Wed Jul 11 06:33:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BDXRi27866 for linux-xfs-outgoing; Wed, 11 Jul 2001 06:33:27 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BDXPV27859 for ; Wed, 11 Jul 2001 06:33:26 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6BDXHx07185; Wed, 11 Jul 2001 15:33:17 +0200 Message-Id: <4.3.2.7.2.20010711144903.032add00@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 15:32:55 +0200 To: ThH From: Seth Mos Subject: Re: Installer for RH7.1 Alpha Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 08:35 11-7-2001 -0400, Martin K. Petersen wrote: > >>>>> "ThH" == ThH writes: > >ThH> Is there a way to make an installer iso for RH7.1 Alpha? May be >ThH> with SRPMS from 1.0.1 i386 installer. What I have to do for this >ThH> way or other. > >It's on my list of things to do. Still waiting for my replacement >Alpha to arrive, though. > >But yes. Effectively you need to respin the SRPMS on the XFS 1.0.1 >iso for Alpha. Would I need root for rebuilding SRPMS? I can check with my friend if he can make his alpha booting to test/rebuild it with. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:00:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BE0K930137 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:00:20 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BE0IV30133 for ; Wed, 11 Jul 2001 07:00:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA03161 for ; Wed, 11 Jul 2001 07:00:14 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2404739; Wed, 11 Jul 2001 08:58:57 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA93031; Wed, 11 Jul 2001 08:58:56 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6BE01t31125; Wed, 11 Jul 2001 09:00:01 -0500 Message-Id: <200107111400.f6BE01t31125@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Seth Mos cc: ThH , linux-xfs@oss.sgi.com Subject: Re: Installer for RH7.1 Alpha In-Reply-To: Message from Seth Mos of "Wed, 11 Jul 2001 15:32:55 +0200." <4.3.2.7.2.20010711144903.032add00@pop.xs4all.nl> Date: Wed, 11 Jul 2001 09:00:00 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > At 08:35 11-7-2001 -0400, Martin K. Petersen wrote: > > >>>>> "ThH" == ThH writes: > > > >ThH> Is there a way to make an installer iso for RH7.1 Alpha? May be > >ThH> with SRPMS from 1.0.1 i386 installer. What I have to do for this > >ThH> way or other. > > > >It's on my list of things to do. Still waiting for my replacement > >Alpha to arrive, though. > > > >But yes. Effectively you need to respin the SRPMS on the XFS 1.0.1 > >iso for Alpha. > > Would I need root for rebuilding SRPMS? > I can check with my friend if he can make his alpha booting to test/rebuild > it with. You do not need root, you need a .rpmmacros file in your home directory, mine contains this: %_topdir /xfs/redhat In this directory you need to do a mkdir for BUILD RPMS SOURCES SPECS SRPMS then install the source rpm and go build it. Steve > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:16:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BEGTk02299 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:16:29 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BEGRV02293 for ; Wed, 11 Jul 2001 07:16:27 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f6BEG0H13532 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 10:16:00 -0400 Date: Wed, 11 Jul 2001 10:16:00 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: RPM building as non-root Message-ID: <20010711101559.A13529@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="3V7upXqbjpZ4EhLz" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Since it's a pseudo-FAQ, here's a short bit of text I wrote on building RPMs as non-root. It uses the two files rpmrc and macros, which accompany this message. Build RPMs at $HOME and EARN BIG $$$: ===================================== Building RPMs as root is a nasty business. Try using the option "--buildroot=/" if you don't believe me. (You didn't really do that, did you? Oh, well, I guess you had it coming...) You can build RPMs in your own $HOME, logged in as $USER, in almost all cases. (For builds that want to create device nodes, there's the Debian program "fakeroot", but that's beyond the scope of this little tidbit.) First, create your build dir. Let's say it's "$HOME/rpm". That's how the sample files are set up. mkdir $HOME/rpm mkdir $HOME/rpm/{SPECS,SOURCES,SRPMS,RPMS,BUILD,tmp) mkdir $HOME/rpm/RPMS/{athlon,i386,i486,i586,i686,noarch} Next, copy the supplied sample files to ~/rpm, and link the rpmrc file to your $HOME. for i in rpmrc macros; do cp /path/to/rpm.$i ~/rpm/$i done cd $HOME ln -sf rpm/rpmrc .rpmrc Finally, edit the $HOME/rpm/macros file and insert your $HOME dir for the value of the %home macro. A NOTE FOR REDHAT 7.X USERS: RedHat ships with a library from AT&T Research called libsafe. Some (many?) of you will have it installed. It places a hook in /etc/profile.d, so that when you log in, the LD_PRELOAD variable is set to point to the libsafe.so library. Libsafe is wonderful. It prevents all sorts of nasty things like stack smashing from happening, by complaining and core dumping *before* the damage happens. Don't use libsafe with mozilla, or netscape, or ... rpm. The LD_PRELOAD environment variable confuses rpm's auto-dependency logic, and any binaries or libraries you compile will get a libsafe.so entry in the "Requires" list. You do *not* want this. Make a small script called "rpm", and put it in $HOME/bin, or somewhere else on your $PATH before /bin. This code is all you need: #!/usr/bin/env bash unset LD_PRELOAD unset LD_LIBRARY_PATH exec /bin/rpm ${1:+"$@"} That's it. You're now ready to MAKE RPM$$$ FA$$$T!!! -- Alan Eldridge from std_disclaimer import * --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rpm.rpmrc" # ~/.rpm/rpmrc for alane@wozzle.geeksrus.net # # set vars up for building software locally as non-root # include: /usr/lib/rpm/rpmrc macrofiles: /usr/lib/rpm/macros:/usr/lib/rpm/%{_target}/macros:/etc/rpm/macros.specspo:/etc/rpm/macros:/etc/rpm/%{_target}/macros:~/rpm/macros --3V7upXqbjpZ4EhLz Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="rpm.macros" # ~/.rpm/macros # # set up for building locally as non-root # %home /YOUR/HOME/DIR %_topdir %{home}/rpm %_tmppath %{home}/rpm/tmp --3V7upXqbjpZ4EhLz-- From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:19:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BEJjx02678 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:19:45 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BEJiV02674 for ; Wed, 11 Jul 2001 07:19:44 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15KKq4-0006sP-00 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 15:19:40 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id PAA03979 for ; Wed, 11 Jul 2001 15:19:40 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f6BEJej04268 for ; Wed, 11 Jul 2001 15:19:40 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Wed, 11 Jul 2001 15:19:40 +0100 (BST) From: "P.Dixon" To: Subject: xfs 1.0.1 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Shouldn't someone post to /. that XFS 1.0.1 is out? Cheerio, Paul ------------------------------------------------------------------------------- Paul Dixon Email: P.Dixon@qmw.ac.uk Department of Physics Phone: (020) 7882 5054 Queen Mary, University of London Fax : (020) 7882 5054 Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:36:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BEaOu05462 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:36:24 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BEaMV05456 for ; Wed, 11 Jul 2001 07:36:22 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA00528 for ; Wed, 11 Jul 2001 07:33:48 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2402357; Wed, 11 Jul 2001 09:35:05 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA44515; Wed, 11 Jul 2001 09:35:05 -0500 (CDT) Message-ID: <3B4C644B.D412025A@sgi.com> Date: Wed, 11 Jul 2001 09:35:55 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Shanker Balan CC: Linux-XFS Subject: Re: FAQ: How do i use rsync? References: <20010711105245.A3329@exocore.com> <20010711110117.B3329@exocore.com> <3B4BE666.9972F23@thebarn.com> <20010711111930.C3329@exocore.com> <20010711114039.D3329@exocore.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Shanker Balan wrote: > Q. Is rsync useful for a single large file (like an iso image)? > http://rsync.samba.org/rsync/fom-serve/cache/60.html > > I guess this clears all my doubts. Don't expect TOO much magic, though, because much of the image has changed (all the RPMS, which are compressed, so probably don't have many common bits with 1.0). We tried this internally, and it did save some transfer time, but the differences are significant enough that you don't get a HUGE advantage. -Eric From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:37:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BEbfo05591 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:37:41 -0700 Received: from chimta02 (chimta02.algx.net [216.99.233.77]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BEbEV05542 for ; Wed, 11 Jul 2001 07:37:16 -0700 Received: from localhost.localdomain (66-2-81-26.customer.algx.net [66.2.81.26]) by chimmx02.algx.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GGB003CJCLKON@chimmx02.algx.net> for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 09:36:56 -0500 (CDT) Date: Wed, 11 Jul 2001 10:36:33 -0400 (EDT) From: jtrostel@connex.com Subject: Re: XFS for Linux 1.0.1 Released In-reply-to: <4.3.2.7.2.20010711135130.032a87d8@pop.xs4all.nl> To: Seth Mos Cc: linux-xfs@oss.sgi.com, ries@franksintl.nl Reply-to: jtrostel@connex.com Message-id: Organization: Connex MIME-version: 1.0 X-Mailer: XFMail 1.5.0 on Linux Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-Priority: 3 (Normal) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 11-Jul-2001 Seth Mos wrote: > At 13:18 11-7-2001 +0200, Ries van Twisk wrote: Snip... >> > >I'm currently buzy to compiling Samba aswell but I still have some >> problems >> > >with ACL. >> > >> > 2.2.1 I presume? I did download it but I will have to see of it compiles >> > under NCR Unix first. >>Yes a 2.2.1 version. But it does not compile with acl support :-( >> >>Samba expect the files in sys/ and not in acl/ and the header file are >>different. > > Yes these files have moved. You may be able to specify the location with a > --with-acl=/usr/include/acl or something like that. If not, you will have > to walk through the code to see where the configure script is looking and > change that. I guess the samba folks were probably caught off guard. > > Cheers > Samba 2.2.1 expects libacl.a to be in /usr/lib and expects acl.h to be in /usr/include/sys. These are the same places that the bestbits ACL stuff goes and the detection and use of the ACL code is now identical between the two implementations. The 'best' way to run Samba and XFS is to get the latest versions of both (Samba 2.2.1 and XFS 1.0.1) and use them. They should have the components in the correct places and the XFS ACL library will have a more complete set of posix compliant functions built into it. If you are running a version of XFS with acl.h in /usr/include/acl, it is possible that your libacl.a also does not have all the necessary functionality. The missing functionality from the current libacl.a was written into Samba at an early stage before it was integrated into the libacl.a library. It is NOT possible to specify where to look for the acl.h header or the libacl.a library through configure parameters (unless you want to hack the configure scripts of course). It also would probably lead to other problems down the road. -- John M. Trostel Linux OS Engineer Connex jtrostel@connex.com From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:40:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BEe1805967 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:40:01 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BEe0V05958 for ; Wed, 11 Jul 2001 07:40:00 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA00846 for ; Wed, 11 Jul 2001 07:37:26 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2403100; Wed, 11 Jul 2001 09:38:44 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA41557; Wed, 11 Jul 2001 09:38:43 -0500 (CDT) Message-ID: <3B4C6525.7B874CEA@sgi.com> Date: Wed, 11 Jul 2001 09:39:33 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: alan@cotse.com CC: linux-xfs@oss.sgi.com Subject: Re: xfs 1.0.1 and linux 2.4.6 References: <2bdb5efac4f0ea174353dc2735a93456@freemail.cotse.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The XFS merge from 2.4.5 to 2.4.6 was non-trivial, luckily we had smart guys like Steve and Keith around to do it. :) If you're starting with the patch manpage, you may be in for a lot of work. I do plan to put out 2.4.6 patches, but I'd like to expose them to some internal testing before we slap "1.0.1" on it. After I get a bit of confidence in them, I can put them out as "testing." -Eric alan@cotse.com wrote: > > Not to sound too bleeding edge, but I would like to begin a test project for work that involves, among other things, xfs as the filesystem. > I see that there is an 8.0 mb patch difference between linux 2.4.5 and 2.4.6, so I'd prefer using the latter. The nfs and memory fixes that occurred in the days since the 2.4.6 patch was created and 2.4.5 1.0.1 release are what I am interested in really. > > Alternatively, does anyone know how I might convert a 2.4.5-xfs patched kernel to 2.4.6? After perusing manpages for patch, diff, and diff3, I haven't a clue as to how I could create a patch for one modified kernel version, that would take one set of modifications (xfs) and apply them to what is essentially a foriegn environment (2.4.6) for it. From owner-linux-xfs@oss.sgi.com Wed Jul 11 07:41:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BEf7S06161 for linux-xfs-outgoing; Wed, 11 Jul 2001 07:41:07 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BEf6V06157 for ; Wed, 11 Jul 2001 07:41:06 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6BEf3x07570; Wed, 11 Jul 2001 16:41:03 +0200 Message-Id: <4.3.2.7.2.20010711163944.03227dc0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 16:40:42 +0200 To: "P.Dixon" , From: Seth Mos Subject: Re: xfs 1.0.1 In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 15:19 11-7-2001 +0100, P.Dixon wrote: >Hi, > >Shouldn't someone post to /. that XFS 1.0.1 is out? And linuxtoday and linux-kernel linux-fs I already forwarded it to the CT magazine. Cheers Seth -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 08:09:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BF9GG08250 for linux-xfs-outgoing; Wed, 11 Jul 2001 08:09:16 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BF9EV08243 for ; Wed, 11 Jul 2001 08:09:15 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA14236 for ; Wed, 11 Jul 2001 08:09:05 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2405216; Wed, 11 Jul 2001 10:07:57 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA17503; Wed, 11 Jul 2001 10:07:57 -0500 (CDT) Message-ID: <3B4C6BFF.5939F32D@sgi.com> Date: Wed, 11 Jul 2001 10:08:47 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk D. Stimits" wrote: > Don't trust rpm to update the kernel. Run rpm -i on the source rpm, then > get the tarball out of /usr/src/redhat/SOURCES/, do a cp -adpR on > whatever subdir it is to the usual /usr/src/ location after backing up > (and completely moving out of the way) any old kernels. Then run make > menuconfig (or some config) manually before doing the rest. You have to > select initial ram disk support. Whoa... at that point, why use RPM? :) If you want to rebuild the kernel, just install the kernel-source RPM, and build it from /usr/src/linux-2.4 RPM kernel upgrades have always worked fine for me, just do an "rpm -i" (as opposed to -U, so you keep your old kernel around for good measure), then set up lilo to point to the new kernel image. Red Hat has a page on how to do this at http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html -Eric From owner-linux-xfs@oss.sgi.com Wed Jul 11 08:23:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BFNxH09350 for linux-xfs-outgoing; Wed, 11 Jul 2001 08:23:59 -0700 Received: from lott.kelman.com ([198.161.93.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BFNuV09343 for ; Wed, 11 Jul 2001 08:23:57 -0700 Received: from lorette.kelman.com (lorette [198.161.93.92]) by lott.kelman.com (8.9.3/8.9.3) with ESMTP id JAA01651 for ; Wed, 11 Jul 2001 09:24:16 -0600 (MDT) Received: from tux by lorette.kelman.com (8.8.8+Sun/SMI-SVR4) id JAA00214; Wed, 11 Jul 2001 09:22:50 -0600 (MDT) Date: Wed, 11 Jul 2001 09:22:02 -0600 (MDT) From: Michal Kozlowski X-Sender: michal@localhost.localdomain To: linux-xfs@oss.sgi.com Subject: Re: Patch for linux 2.4.6-ac* series? In-Reply-To: <994800612.5792.2.camel@tduffy-lnx.afara.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 10 Jul 2001, Thomas Duffy wrote: > On 10 Jul 2001 11:30:57 -0600, Michal Kozlowski wrote: > > Hi, I was wondering if someone could provide some hints on creating a xfs > > patch for the 2.4.6-ac2 kernel. I know the SGI team doesn't support it > > since Alan can release way to many updates, but I'm willing to try and get > > the 2 going together. I want to try the hpt370 raid-0 with xfs on it. > > How much effort would something like this take? I've modified source code > > many times to get things working but never attempted something like this. > > Maybe if I get good at this I could release regular updates, but for now I > > just want 2.4.6-ac2 to work. Thanks for all you help, > > if you grabbed the patch of xfs from the kernel.src.rpm for 2.4.3, you > should have a patch that works on top of some version of ac since redhat > takes ac into it's kernel rpm. > > but, ac has probably changed a bit from 2.4.3 days to 2.4.6 days, so I > don't know how hard the two would be to reconcile. I have done xfs/ac > merges before so it is not impossible...sometimes you might have a weird > conflict that only an expert (like steve) can tell you what you should > do. > > -tduffy > Hmm thanks for the tip, I've noticed all the kbd code in spots, which I think I'll keep in there. My biggest problem is the changes in the apic code and others under the arch/i386/kernel/. After the ac patch there are functions that don't exist or seem to be drastically different , I currently put them back in but I'm not sure if I'm doing the right thing. I haven't gotten the thing to compile yet. And under the md source tree their is some interesting changes in variable names, #define MAX_READAHEAD compared to int vm_max_readahead, other than that they're used exactly the same way. -Mike Kozlowski From owner-linux-xfs@oss.sgi.com Wed Jul 11 08:28:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BFSk509726 for linux-xfs-outgoing; Wed, 11 Jul 2001 08:28:46 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BFSjV09721 for ; Wed, 11 Jul 2001 08:28:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id IAA06057 for ; Wed, 11 Jul 2001 08:26:10 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2405315; Wed, 11 Jul 2001 10:27:26 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA47203; Wed, 11 Jul 2001 10:27:26 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6BFSTx31627; Wed, 11 Jul 2001 10:28:29 -0500 Message-Id: <200107111528.f6BFSTx31627@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Michal Kozlowski cc: linux-xfs@oss.sgi.com Subject: Re: Patch for linux 2.4.6-ac* series? In-Reply-To: Message from Michal Kozlowski of "Wed, 11 Jul 2001 09:22:02 MDT." Date: Wed, 11 Jul 2001 10:28:29 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hmm thanks for the tip, I've noticed all the kbd code in spots, which I > think I'll keep in there. My biggest problem is the changes in the apic > code and others under the arch/i386/kernel/. After the ac patch there are > functions that don't exist or seem to be drastically different , I > currently put them back in but I'm not sure if I'm doing the right thing. > I haven't gotten the thing to compile yet. And under the md source tree > their is some interesting changes in variable names, #define MAX_READAHEAD > compared to int vm_max_readahead, other than that they're used exactly the > same way. > > -Mike Kozlowski Keith Owens has a kdb patch for 2.4.6-ac1 which may help you out, look here: ftp://oss.sgi.com/projects/kdb/download/ix86/ Steve From owner-linux-xfs@oss.sgi.com Wed Jul 11 08:51:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BFpPM11225 for linux-xfs-outgoing; Wed, 11 Jul 2001 08:51:25 -0700 Received: from lott.kelman.com ([198.161.93.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BFpIV11220 for ; Wed, 11 Jul 2001 08:51:23 -0700 Received: from lorette.kelman.com (lorette [198.161.93.92]) by lott.kelman.com (8.9.3/8.9.3) with ESMTP id JAA01959; Wed, 11 Jul 2001 09:51:58 -0600 (MDT) Received: from tux by lorette.kelman.com (8.8.8+Sun/SMI-SVR4) id JAA00635; Wed, 11 Jul 2001 09:50:32 -0600 (MDT) Date: Wed, 11 Jul 2001 09:49:44 -0600 (MDT) From: Michal Kozlowski X-Sender: michal@localhost.localdomain To: Steve Lord cc: linux-xfs@oss.sgi.com Subject: Re: Patch for linux 2.4.6-ac* series? In-Reply-To: <200107111528.f6BFSTx31627@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 11 Jul 2001, Steve Lord wrote: > > > Hmm thanks for the tip, I've noticed all the kbd code in spots, which I > > think I'll keep in there. My biggest problem is the changes in the apic > > code and others under the arch/i386/kernel/. After the ac patch there are > > functions that don't exist or seem to be drastically different , I > > currently put them back in but I'm not sure if I'm doing the right thing. > > I haven't gotten the thing to compile yet. And under the md source tree > > their is some interesting changes in variable names, #define MAX_READAHEAD > > compared to int vm_max_readahead, other than that they're used exactly the > > same way. > > > > -Mike Kozlowski > > Keith Owens has a kdb patch for 2.4.6-ac1 which may help you out, look here: > > ftp://oss.sgi.com/projects/kdb/download/ix86/ > > Steve > > Thanks, I think that should work. If that doesn't work, i think the easiest way to go would be to download the 2.4.5 kernel, apply the official patch maybe even XFS 1.0.1. And since it doesn't contain kdb, less file would be modified. And the apply the the 2.4.5 ac24 patch, since it's the first one to have the hpt370 raid 0 patch. Mike Kozlowski From owner-linux-xfs@oss.sgi.com Wed Jul 11 09:34:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BGYmQ12771 for linux-xfs-outgoing; Wed, 11 Jul 2001 09:34:48 -0700 Received: from sunny.fishnet.com (sunny.fishnet.com [209.150.200.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BGYlV12757 for ; Wed, 11 Jul 2001 09:34:47 -0700 Received: from awm-laptop (209.150.207.51) by sunny.fishnet.com (5.0.048) id 3B49D9C400023105 for linux-xfs@oss.sgi.com; Wed, 11 Jul 2001 10:27:30 -0500 Content-Type: text/plain; charset="iso-8859-1" From: "Anthony W. Marino" Organization: AWMObjects To: linux-xfs@oss.sgi.com Subject: Kernel 2.4.6 and XFS Date: Wed, 11 Jul 2001 10:26:41 -0500 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01071110264100.01052@awm-laptop> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk What support is available for kernel 2.4.6? I'm going to start a fresh installation on a RH7.1 (intel) box with kernel 2.4.6. Thank You, Anthony From owner-linux-xfs@oss.sgi.com Wed Jul 11 09:37:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BGbTJ12941 for linux-xfs-outgoing; Wed, 11 Jul 2001 09:37:29 -0700 Received: from mail.edm-inc.com (mail.edm-inc.com [66.80.43.91]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BGbRV12937 for ; Wed, 11 Jul 2001 09:37:28 -0700 Received: (qmail 10047 invoked by uid 1005); 11 Jul 2001 11:37:22 -0500 Received: from ian.scott@edm-inc.com by mail with qmail-scanner-0.96 (fsecure: 4.10/3081/2001-07-09/2001-07-10/2001-07-09. inocucmd: 24.00/25.47. . Clean. Processed in 2.252058 secs); 11 Jul 2001 11:37:22 -0500 Received: from unknown (HELO admin.edm-inc.com) (10.10.10.58) by 0 with SMTP; 11 Jul 2001 11:37:19 -0500 Message-Id: <5.1.0.14.0.20010711113123.00afaca8@mail.edm-inc.com> X-Sender: ian.scott@mail.edm-inc.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Wed, 11 Jul 2001 11:37:10 -0500 To: linux-xfs@oss.sgi.com From: Ian Scott Subject: Source tarballs for 1.0.1 cmd_tars Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Would it be possible to add source tarballs to the cmd_tars directory for the 1.0.1 release? Right now there are only binaries and no devel headers, and I'm itching to get Samba 2.2.1 running with XFS support again. Thanks, Ian Scott From owner-linux-xfs@oss.sgi.com Wed Jul 11 10:17:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BHHrG13990 for linux-xfs-outgoing; Wed, 11 Jul 2001 10:17:53 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BHHqV13986 for ; Wed, 11 Jul 2001 10:17:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA07690 for ; Wed, 11 Jul 2001 10:17:44 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2406979; Wed, 11 Jul 2001 12:16:28 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA48488; Wed, 11 Jul 2001 12:16:27 -0500 (CDT) Message-ID: <3B4C8A1D.B8A4001D@sgi.com> Date: Wed, 11 Jul 2001 12:17:17 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Ian Scott CC: linux-xfs@oss.sgi.com Subject: Re: Source tarballs for 1.0.1 cmd_tars References: <5.1.0.14.0.20010711113123.00afaca8@mail.edm-inc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ian Scott wrote: > > Hello, > > Would it be possible to add source tarballs to the cmd_tars directory for > the 1.0.1 release? Right now there are only binaries and no devel headers, > and I'm itching to get Samba 2.2.1 running with XFS support again. Whoops! Sorry, didn't realize that the tarballs were binary only. I built them w/ scripts, and assumed that the tar.gz was source. I'll get them out in a few minutes. -Eric From owner-linux-xfs@oss.sgi.com Wed Jul 11 10:25:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BHPH614287 for linux-xfs-outgoing; Wed, 11 Jul 2001 10:25:17 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BHPGV14283 for ; Wed, 11 Jul 2001 10:25:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id KAA03338 for ; Wed, 11 Jul 2001 10:25:07 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2400010; Wed, 11 Jul 2001 12:24:00 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA60340; Wed, 11 Jul 2001 12:23:59 -0500 (CDT) Message-ID: <3B4C8BE0.262BDAD4@sgi.com> Date: Wed, 11 Jul 2001 12:24:48 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Anthony W. Marino" CC: linux-xfs@oss.sgi.com Subject: Re: Kernel 2.4.6 and XFS References: <01071110264100.01052@awm-laptop> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Anthony W. Marino" wrote: > > What support is available for kernel 2.4.6? I'm going to start a fresh > installation on a RH7.1 (intel) box with kernel 2.4.6. I do plan to put out a 2.4.6/1.0.1 patch, but until then your other option would be to do a CVS checkout as of the date of the 2.4.6 merge... or better yet, just before the 2.4.7-pre1 merge. Of course, you're just dealing with a snapshot at that point... -Eric From owner-linux-xfs@oss.sgi.com Wed Jul 11 10:33:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BHX6G14727 for linux-xfs-outgoing; Wed, 11 Jul 2001 10:33:06 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BHX5V14705 for ; Wed, 11 Jul 2001 10:33:05 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA01162 for ; Wed, 11 Jul 2001 10:30:27 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2404757; Wed, 11 Jul 2001 12:30:22 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA95647; Wed, 11 Jul 2001 12:30:22 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6BHVOO32536; Wed, 11 Jul 2001 12:31:24 -0500 Message-Id: <200107111731.f6BHVOO32536@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Eric Sandeen cc: "Anthony W. Marino" , linux-xfs@oss.sgi.com Subject: Re: Kernel 2.4.6 and XFS In-Reply-To: Message from Eric Sandeen of "Wed, 11 Jul 2001 12:24:48 CDT." <3B4C8BE0.262BDAD4@sgi.com> Date: Wed, 11 Jul 2001 12:31:24 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > "Anthony W. Marino" wrote: > > > > What support is available for kernel 2.4.6? I'm going to start a fresh > > installation on a RH7.1 (intel) box with kernel 2.4.6. > > I do plan to put out a 2.4.6/1.0.1 patch, but until then your other > option would be to do a CVS checkout as of the date of the 2.4.6 > merge... or better yet, just before the 2.4.7-pre1 merge. Of course, > you're just dealing with a snapshot at that point... > > -Eric There is a 2.4.6 patch in the patches directory as well. Steve p.s. the development tree is about to go to 2.4.7-pre6 From owner-linux-xfs@oss.sgi.com Wed Jul 11 10:57:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BHvQe15727 for linux-xfs-outgoing; Wed, 11 Jul 2001 10:57:26 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BHvMV15720 for ; Wed, 11 Jul 2001 10:57:22 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA43045 for ; Wed, 11 Jul 2001 19:57:20 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2403694 for ; Wed, 11 Jul 2001 12:56:03 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA33091 for ; Wed, 11 Jul 2001 12:56:03 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6BHv6R32718; Wed, 11 Jul 2001 12:57:06 -0500 Message-Id: <200107111757.f6BHv6R32718@jen.americas.sgi.com> Date: Wed, 11 Jul 2001 12:57:06 -0500 Subject: TAKE - merge up to 2.4.7-pre6 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Linus's code base plus a scheduler fix from Andrea Arcangeli, without this the tree hung hard for me during boot up. Some buffer code was modified again in this patch and xfs has code in the middle of there. I have been testing that code for a couple of days without problem. Date: Wed Jul 11 10:53:24 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98647a linux/drivers/message/fusion/scsiops.c - 1.1 linux/include/asm-alpha/rwsem.h - 1.1 linux/drivers/video/pvr2fb.c - 1.1 linux/drivers/parport/parport_serial.c - 1.1 linux/Documentation/fb/pvr2fb.txt - 1.1 linux/drivers/net/dl2k.h - 1.1 linux/Documentation/networking/dl2k.txt - 1.1 linux/drivers/net/dl2k.c - 1.1 linux/drivers/message/fusion/scsi3.h - 1.1 linux/drivers/message/fusion/mptscsih.h - 1.1 linux/drivers/message/fusion/mptscsih.c - 1.1 linux/drivers/message/fusion/mptlan.h - 1.1 linux/drivers/message/fusion/mptlan.c - 1.1 linux/drivers/message/fusion/mptctl.c - 1.1 linux/drivers/message/fusion/mptbase.h - 1.1 linux/drivers/message/fusion/mptbase.c - 1.1 linux/drivers/message/fusion/lsi/mpi_type.h - 1.1 linux/drivers/message/fusion/lsi/mpi_targ.h - 1.1 linux/drivers/message/fusion/lsi/mpi_lan.h - 1.1 linux/drivers/message/fusion/lsi/mpi_ioc.h - 1.1 linux/drivers/message/fusion/lsi/mpi_init.h - 1.1 linux/drivers/message/fusion/lsi/mpi_history.txt - 1.1 linux/drivers/message/fusion/lsi/mpi_fc.h - 1.1 linux/drivers/message/fusion/lsi/mpi_cnfg.h - 1.1 linux/drivers/message/fusion/lsi/mpi.h - 1.1 linux/drivers/message/fusion/Config.in - 1.1 linux/drivers/message/fusion/Makefile - 1.1 linux/drivers/message/fusion/ascq_tbl.c - 1.1 linux/drivers/message/fusion/ascq_tbl.sh - 1.1 linux/drivers/message/fusion/isense.c - 1.1 linux/drivers/message/fusion/isense.h - 1.1 linux/drivers/message/fusion/linux_compat.h - 1.1 linux/drivers/message/fusion/lsi/fc_log.h - 1.1 linux/net/unix/af_unix.c - 1.30 linux/net/netsyms.c - 1.33 linux/net/ipv4/tcp_output.c - 1.19 linux/net/ipv4/raw.c - 1.20 linux/net/ipv4/ip_output.c - 1.22 linux/net/core/skbuff.c - 1.20 linux/net/core/dev.c - 1.36 linux/mm/swap_state.c - 1.26 linux/mm/memory.c - 1.50 linux/mm/filemap.c - 1.78 linux/kernel/softirq.c - 1.11 linux/kernel/sched.c - 1.37 linux/kernel/ksyms.c - 1.95 linux/include/linux/skbuff.h - 1.20 linux/include/linux/parport.h - 1.18 linux/include/linux/netlink.h - 1.5 linux/include/linux/netdevice.h - 1.23 linux/include/linux/locks.h - 1.5 linux/include/linux/isdnif.h - 1.12 linux/include/linux/interrupt.h - 1.14 linux/include/linux/if_arp.h - 1.11 linux/include/linux/fs.h - 1.101 linux/include/asm-sparc64/softirq.h - 1.8 linux/include/asm-sparc64/hardirq.h - 1.12 linux/include/asm-sparc64/atomic.h - 1.7 linux/include/asm-sparc/vaddrs.h - 1.7 linux/include/asm-sparc/softirq.h - 1.9 linux/include/asm-sparc/hardirq.h - 1.12 linux/include/asm-sparc/bitops.h - 1.9 linux/include/asm-sparc/atomic.h - 1.8 linux/include/asm-ppc/softirq.h - 1.12 linux/include/asm-ppc/atomic.h - 1.7 linux/include/asm-mips/atomic.h - 1.7 linux/include/asm-m68k/atomic.h - 1.3 linux/include/asm-i386/softirq.h - 1.9 linux/include/asm-i386/hardirq.h - 1.15 linux/include/asm-i386/atomic.h - 1.12 linux/include/asm-arm/softirq.h - 1.6 linux/include/asm-alpha/softirq.h - 1.8 linux/include/asm-alpha/hardirq.h - 1.13 linux/include/asm-alpha/atomic.h - 1.7 linux/fs/sysv/dir.c - 1.9 linux/fs/nfsd/nfsfh.c - 1.28 linux/fs/buffer.c - 1.71 linux/drivers/video/imsttfb.c - 1.15 linux/drivers/video/fbmem.c - 1.37 linux/drivers/video/Makefile - 1.31 linux/drivers/video/Config.in - 1.26 linux/drivers/net/epic100.c - 1.23 linux/drivers/net/Makefile - 1.44 linux/drivers/net/Config.in - 1.43 linux/drivers/net/3c509.c - 1.23 linux/drivers/isdn/isdn_tty.c - 1.13 linux/drivers/isdn/hisax/config.c - 1.20 linux/drivers/char/serial.c - 1.42 linux/drivers/char/mem.c - 1.36 linux/drivers/char/lp.c - 1.20 linux/drivers/block/ps2esdi.c - 1.16 linux/drivers/block/ll_rw_blk.c - 1.71 linux/arch/ppc/kernel/prom.c - 1.23 linux/arch/i386/kernel/vm86.c - 1.9 linux/arch/i386/defconfig - 1.61 linux/arch/alpha/kernel/entry.S - 1.20 linux/arch/alpha/kernel/alpha_ksyms.c - 1.23 linux/arch/alpha/config.in - 1.32 linux/Makefile - 1.101 linux/MAINTAINERS - 1.63 linux/Documentation/fb/00-INDEX - 1.5 linux/Documentation/Configure.help - 1.87 linux/net/decnet/dn_dev.c - 1.12 linux/drivers/usb/printer.c - 1.37 linux/drivers/sbus/char/aurora.c - 1.9 linux/drivers/isdn/eicon/eicon.h - 1.11 linux/drivers/parport/parport_pc.c - 1.35 linux/drivers/parport/init.c - 1.11 linux/drivers/parport/Makefile - 1.7 linux/drivers/parport/Config.in - 1.12 linux/include/asm-sh/softirq.h - 1.8 linux/drivers/net/starfire.c - 1.16 linux/fs/proc/proc_misc.c - 1.19 linux/drivers/usb/scanner.c - 1.21 linux/drivers/usb/usb-ohci.c - 1.23 linux/include/asm-ia64/atomic.h - 1.5 linux/drivers/net/8139too.c - 1.22 linux/Documentation/networking/8139too.txt - 1.11 linux/include/asm-mips64/atomic.h - 1.6 linux/drivers/video/hgafb.c - 1.6 linux/drivers/parport/ChangeLog - 1.16 linux/Documentation/DocBook/Makefile - 1.16 linux/net/ipv4/netfilter/iptable_mangle.c - 1.6 linux/net/ipv4/netfilter/ipt_unclean.c - 1.5 linux/net/ipv4/netfilter/ip_queue.c - 1.9 linux/drivers/usb/serial/ftdi_sio.c - 1.19 linux/drivers/usb/serial/usbserial.c - 1.18 linux/drivers/net/pppoe.c - 1.14 linux/include/asm-s390/atomic.h - 1.4 linux/drivers/net/stnic.c - 1.7 linux/Documentation/DocBook/via-audio.tmpl - 1.3 linux/include/linux/irq_cpustat.h - 1.4 linux/drivers/md/raid5.c - 1.17 linux/include/asm-sparc64/starfire.h - 1.3 linux/mm/oom_kill.c - 1.4 linux/net/core/dv.c - 1.4 linux/drivers/usb/serial/empeg.c - 1.8 linux/mm/shmem.c - 1.7 linux/drivers/pcmcia/hd64465_ss.c - 1.3 linux/include/asm-s390x/atomic.h - 1.3 linux/drivers/scsi/aic7xxx_old.c - 1.5 linux/drivers/video/dcfb.c - 1.2 linux/lib/rwsem.c - 1.2 linux/drivers/isdn/hisax/md - 1.2 From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:03:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BK3xt19292 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:03:59 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BK3vV19288 for ; Wed, 11 Jul 2001 13:03:57 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA05289 for ; Wed, 11 Jul 2001 13:01:20 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2406496 for ; Wed, 11 Jul 2001 15:02:38 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA20175 for ; Wed, 11 Jul 2001 15:02:38 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6BK4kk01969; Wed, 11 Jul 2001 15:04:46 -0500 Message-Id: <200107112004.f6BK4kk01969@jen.americas.sgi.com> Date: Wed, 11 Jul 2001 15:04:46 -0500 Subject: TAKE - fix nfs related bug with sparse file size Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This version of the fix should be safer than the original, we still modify the inode size in the iozero path under the page lock, but we limit it to be less than or equal to the eventual size the write will get the file up to. This avoids the issue of creating pages beyond the eof which the original fix had. Date: Wed Jul 11 13:00:39 PDT 2001 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:98657a linux/fs/xfs/xfs_rw.c - 1.340 linux/fs/xfs/xfs_inode.c - 1.321 - Add inode size to zero_eof call linux/fs/xfs/linux/xfs_lrw.h - 1.17 - Changed prototypes for zero_eof functions linux/fs/xfs/linux/xfs_lrw.c - 1.104 - Pass the final inode size for a write through the zero_eof paths so that they can pass it onto pagebuf_iozero. linux/include/linux/page_buf.h - 1.97 - Changed prototype for pagebuf_iozero linux/fs/pagebuf/page_buf_io.c - 1.90 - Change pagebuf_iozero to set the inode size itself, and add a new parameter which is the maximum offset the size can be set to. This prevents the hole zeroing code from going out beyond the final end of file. From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:10:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BKAnF19574 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:10:49 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BKAkV19568 for ; Wed, 11 Jul 2001 13:10:46 -0700 Received: from verbum.org (root@gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id QAA03559 for ; Wed, 11 Jul 2001 16:10:44 -0400 (EDT) Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by verbum.org (Postfix (Debian/GNU)) with ESMTP id 8F8047222 for ; Wed, 11 Jul 2001 16:05:30 -0400 (EDT) Received: by space-ghost (Postfix, from userid 1000) id 39228622F55; Wed, 11 Jul 2001 16:05:26 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: Re: XFS and Emacs don't play nice References: <200107100917.f6A9HIR14760@jen.americas.sgi.com> X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Wed, 11 Jul 2001 16:05:26 -0400 In-Reply-To: <200107100917.f6A9HIR14760@jen.americas.sgi.com> (Steve Lord's message of "Tue, 10 Jul 2001 04:17:17 -0500") Message-ID: <87u20jcjuh.church.of.emacs@cis.ohio-state.edu> Lines: 18 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord writes: > First of all, I would encourage both of you to update to a more > recent kernel. Well, I just switched from ext2 to XFS on my laptop (TiBook), and it seems to work really well! I tried for a while to reproduce the problem I had on my other (desktop) system, with no luck. I'm currently running: Linux space-ghost 2.4.6+ipsec+xfs #1 Wed Jul 11 11:12:00 EDT 2001 ppc unknown I'll try updating to 2.4.6 on my ia32 box and see if I can reproduce the problem there again. Thanks for such a great filesystem, by the way! From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:41:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BKfKc20833 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:41:20 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BKfIV20828 for ; Wed, 11 Jul 2001 13:41:18 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip1.idcomm.com [209.60.72.128]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6BKiQa14715 for ; Wed, 11 Jul 2001 14:44:26 -0600 Message-ID: <3B4CBA71.D1D4E781@idcomm.com> Date: Wed, 11 Jul 2001 14:43:29 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > > D. Stimits" wrote: > > > Don't trust rpm to update the kernel. Run rpm -i on the source rpm, then > > get the tarball out of /usr/src/redhat/SOURCES/, do a cp -adpR on > > whatever subdir it is to the usual /usr/src/ location after backing up > > (and completely moving out of the way) any old kernels. Then run make > > menuconfig (or some config) manually before doing the rest. You have to > > select initial ram disk support. > > Whoa... at that point, why use RPM? :) > > If you want to rebuild the kernel, just install the kernel-source RPM, > and build it from /usr/src/linux-2.4 > > RPM kernel upgrades have always worked fine for me, just do an "rpm -i" > (as opposed to -U, so you keep your old kernel around for good measure), > then set up lilo to point to the new kernel image. > > Red Hat has a page on how to do this at > http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html > > -Eric That's basically what I said, rpm -i...but I didn't realize installing the source rpm to the kernel actually placed it in /usr/src/? I assume it'd have to be copied from /usr/src/redhat/SOURCES/something (the .tar.gz should be there, I made the mistake of suggesting it was also unpacked, which it wouldn't be). D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:45:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BKjN921119 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:45:23 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BKjMV21113 for ; Wed, 11 Jul 2001 13:45:22 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA08989 for ; Wed, 11 Jul 2001 13:45:15 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2406848; Wed, 11 Jul 2001 15:43:58 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA29087; Wed, 11 Jul 2001 15:43:58 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6BKk6G02080; Wed, 11 Jul 2001 15:46:06 -0500 Message-Id: <200107112046.f6BKk6G02080@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: stimits@idcomm.com cc: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released In-Reply-To: Message from "D. Stimits" of "Wed, 11 Jul 2001 14:43:29 MDT." <3B4CBA71.D1D4E781@idcomm.com> Date: Wed, 11 Jul 2001 15:46:06 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > That's basically what I said, rpm -i...but I didn't realize installing > the source rpm to the kernel actually placed it in /usr/src/? I assume > it'd have to be copied from /usr/src/redhat/SOURCES/something (the > .tar.gz should be there, I made the mistake of suggesting it was also > unpacked, which it wouldn't be). > > D. Stimits, stimits@idcomm.com There are two 'source' rpms, the true source rpm which can be used to create the binary rpms, and the source code rpm which installs a copy of the kernel source on the system. Steve From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:46:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BKkic21305 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:46:44 -0700 Received: from local.iboats.com (local.iboats.com [64.78.130.68]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BKkhV21301 for ; Wed, 11 Jul 2001 13:46:43 -0700 Received: (qmail 32223 invoked from network); 11 Jul 2001 14:46:45 -0600 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by local.iboats.com with SMTP; 11 Jul 2001 14:46:45 -0600 Message-ID: <000f01c10a4a$413a9320$50824e40@iboats.com> From: "Steve Wolfe" To: References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> <3B4CBA71.D1D4E781@idcomm.com> Subject: Re: XFS for Linux 1.0.1 Released Date: Wed, 11 Jul 2001 14:44:16 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > RPM kernel upgrades have always worked fine for me, just do an "rpm -i" > > (as opposed to -U, so you keep your old kernel around for good measure), > > then set up lilo to point to the new kernel image. At the risk of starting a flame-war, I avoid RedHat's "standard" kernels like the plague, as my network throughput is significantly slower. My compiling a kernel with exactly what I need, I get a much higher throughput - along the order of several megabytes per second. With everything that they enable in their kernels, I imagine that other aspects would also suffer. Whether that extra bit of performance is necessary depends, of course, on your situation. YMMV. steve From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:47:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BKlUd21452 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:47:30 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BKlTV21448 for ; Wed, 11 Jul 2001 13:47:29 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA07974 for ; Wed, 11 Jul 2001 13:47:25 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2408250; Wed, 11 Jul 2001 15:46:10 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA72584; Wed, 11 Jul 2001 15:46:09 -0500 (CDT) Message-ID: <3B4CBB41.1C863AB1@sgi.com> Date: Wed, 11 Jul 2001 15:46:57 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: stimits@idcomm.com CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> <3B4CBA71.D1D4E781@idcomm.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "D. Stimits" wrote: > That's basically what I said, rpm -i...but I didn't realize installing > the source rpm to the kernel actually placed it in /usr/src/? I assume > it'd have to be copied from /usr/src/redhat/SOURCES/something (the > .tar.gz should be there, I made the mistake of suggesting it was also > unpacked, which it wouldn't be). Ah, well - there's the "kernel-source-foo.i386.rpm" RPM which installs source for the user in /usr/src/linux-2.4, and then there's the "kernel-foo.src.rpm" SRPM which is the "source" from which you build all of the kernel RPMs are built, and installs source and patches in /usr/src/redhat/SOURCES. It does get tricky. :) kernel-source is for compiling kernels, kernel.src.rpm is for building RPMS. -Eric From owner-linux-xfs@oss.sgi.com Wed Jul 11 13:48:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BKmqr21644 for linux-xfs-outgoing; Wed, 11 Jul 2001 13:48:52 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BKmpV21640 for ; Wed, 11 Jul 2001 13:48:51 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA14409; Wed, 11 Jul 2001 22:48:46 +0200 (CEST) Message-Id: <4.3.2.7.2.20010711224438.0349e6a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 11 Jul 2001 22:48:07 +0200 To: stimits@idcomm.com From: Seth Mos Subject: Re: XFS for Linux 1.0.1 Released Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B4CBA71.D1D4E781@idcomm.com> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:43 11-7-2001 -0600, D. Stimits wrote: >Eric Sandeen wrote: > > > > D. Stimits" wrote: > > > > > Don't trust rpm to update the kernel. Run rpm -i on the source rpm, then > > > get the tarball out of /usr/src/redhat/SOURCES/, do a cp -adpR on > > > whatever subdir it is to the usual /usr/src/ location after backing up > > > (and completely moving out of the way) any old kernels. Then run make > > > menuconfig (or some config) manually before doing the rest. You have to > > > select initial ram disk support. > > > > Whoa... at that point, why use RPM? :) > > > > If you want to rebuild the kernel, just install the kernel-source RPM, > > and build it from /usr/src/linux-2.4 > > > > RPM kernel upgrades have always worked fine for me, just do an "rpm -i" > > (as opposed to -U, so you keep your old kernel around for good measure), > > then set up lilo to point to the new kernel image. > > > > Red Hat has a page on how to do this at > > http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html > > > > -Eric > >That's basically what I said, rpm -i...but I didn't realize installing >the source rpm to the kernel actually placed it in /usr/src/? I assume >it'd have to be copied from /usr/src/redhat/SOURCES/something (the >.tar.gz should be there, I made the mistake of suggesting it was also >unpacked, which it wouldn't be). no, kernel-source-x.y.z.i386.rpm is the complete source. You can not rebuild this. kernel-x.y.z.src.rpm is complete source but this is a SRPM. You can rebuild this one with rpm --rebuild. That is a big difference. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 14:52:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BLqH725882 for linux-xfs-outgoing; Wed, 11 Jul 2001 14:52:17 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BLqFV25875 for ; Wed, 11 Jul 2001 14:52:16 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip29.idcomm.com [209.60.72.156]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6BLtOa31166 for ; Wed, 11 Jul 2001 15:55:24 -0600 Message-ID: <3B4CCB12.BACABB56@idcomm.com> Date: Wed, 11 Jul 2001 15:54:26 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> <3B4CBA71.D1D4E781@idcomm.com> <000f01c10a4a$413a9320$50824e40@iboats.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Wolfe wrote: > > > > RPM kernel upgrades have always worked fine for me, just do an > "rpm -i" > > > (as opposed to -U, so you keep your old kernel around for good > measure), > > > then set up lilo to point to the new kernel image. > > At the risk of starting a flame-war, I avoid RedHat's "standard" kernels > like the plague, as my network throughput is significantly slower. My > compiling a kernel with exactly what I need, I get a much higher > throughput - along the order of several megabytes per second. With > everything that they enable in their kernels, I imagine that other aspects > would also suffer. Whether that extra bit of performance is necessary > depends, of course, on your situation. YMMV. > > steve I usually avoid kernel rpms also, but not necessarily because I dislike RH...they just don't keep up versions and features I'm interested in. On the other hand, I have currently the 2.4.6-pre1-xfs kernel, non-RH, and the eepro100 throughput is absolutely miserable. A while back, on earlier kernels (2.2.x), I was able to copy the entire X11 distribution (unpacked, untarred source) within a couple of seconds over the ethernet. I recently tried to copy kernel source the same way, and after many many hours (I watched a couple of two hour movies on television), gave up, it still was not finished. There have been other people talking about the issue on the kernel list, so I suspect this is fixed on newer kernels, but I have not yet got around to testing (lack of reasonable Internet connection in my area means downloading kernels and anything over a couple MB sucks, so I don't do it often) them. My primary concern with any kernel is stability above all else...the 2.4.6-pre1-xfs (with one hand edited patch to block_dev.c) has been very stable, so I don't put it on my high priority list to try the latest and greatest. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Jul 11 14:55:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6BLtIn26154 for linux-xfs-outgoing; Wed, 11 Jul 2001 14:55:18 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6BLtHV26149 for ; Wed, 11 Jul 2001 14:55:17 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip29.idcomm.com [209.60.72.156]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6BLwPa31860 for ; Wed, 11 Jul 2001 15:58:25 -0600 Message-ID: <3B4CCBC8.47F16937@idcomm.com> Date: Wed, 11 Jul 2001 15:57:28 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> <4.3.2.7.2.20010711224438.0349e6a0@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > At 14:43 11-7-2001 -0600, D. Stimits wrote: > >Eric Sandeen wrote: > > > > > > D. Stimits" wrote: > > > > > > > Don't trust rpm to update the kernel. Run rpm -i on the source rpm, then > > > > get the tarball out of /usr/src/redhat/SOURCES/, do a cp -adpR on > > > > whatever subdir it is to the usual /usr/src/ location after backing up > > > > (and completely moving out of the way) any old kernels. Then run make > > > > menuconfig (or some config) manually before doing the rest. You have to > > > > select initial ram disk support. > > > > > > Whoa... at that point, why use RPM? :) > > > > > > If you want to rebuild the kernel, just install the kernel-source RPM, > > > and build it from /usr/src/linux-2.4 > > > > > > RPM kernel upgrades have always worked fine for me, just do an "rpm -i" > > > (as opposed to -U, so you keep your old kernel around for good measure), > > > then set up lilo to point to the new kernel image. > > > > > > Red Hat has a page on how to do this at > > > http://www.redhat.com/support/docs/howto/kernel-upgrade/kernel-upgrade.html > > > > > > -Eric > > > >That's basically what I said, rpm -i...but I didn't realize installing > >the source rpm to the kernel actually placed it in /usr/src/? I assume > >it'd have to be copied from /usr/src/redhat/SOURCES/something (the > >.tar.gz should be there, I made the mistake of suggesting it was also > >unpacked, which it wouldn't be). > > no, > > kernel-source-x.y.z.i386.rpm is the complete source. You can not rebuild this. > kernel-x.y.z.src.rpm is complete source but this is a SRPM. You can rebuild > this one with rpm --rebuild. That is a big difference. When I said "source rpm" I meant the .src.rpm. With the kernel package, this seems to take on unusual meaning...since it is a source package to start with, no matter what you label it. I always prefer .src.rpm format due to the ability to --rebuild, but for kernels I'd just install it to get the tarball, and unpack it manually. I dislike rpm for anything more than that on a kernel. D. Stimits, stimits@idcomm.com > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 11 17:06:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C062Q29824 for linux-xfs-outgoing; Wed, 11 Jul 2001 17:06:02 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C061V29819 for ; Wed, 11 Jul 2001 17:06:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id RAA01093 for ; Wed, 11 Jul 2001 17:03:26 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 KAA24791; Thu, 12 Jul 2001 10:04:43 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA78284; Thu, 12 Jul 2001 10:04:42 +1000 (EST) From: "Nathan Scott" Message-Id: <10107121004.ZM205811@wobbly.melbourne.sgi.com> Date: Thu, 12 Jul 2001 10:04:40 -0500 In-Reply-To: Eric Sandeen "Re: Source tarballs for 1.0.1 cmd_tars" (Jul 11, 12:17pm) References: <5.1.0.14.0.20010711113123.00afaca8@mail.edm-inc.com> <3B4C8A1D.B8A4001D@sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Eric Sandeen Subject: Re: Source tarballs for 1.0.1 cmd_tars Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Jul 11, 12:17pm, Eric Sandeen wrote: > Subject: Re: Source tarballs for 1.0.1 cmd_tars > Ian Scott wrote: > > > > Hello, > > > > Would it be possible to add source tarballs to the cmd_tars directory for > > the 1.0.1 release? Right now there are only binaries and no devel headers, > > and I'm itching to get Samba 2.2.1 running with XFS support again. > > Whoops! Sorry, didn't realize that the tarballs were binary only. I > built them w/ scripts, and assumed that the tar.gz was source. > There are two tarballs produced by Makepkgs - eg. xfsprogs/build/tar/xfsprogs-1.2.8.tar.gz [binary] xfsprogs/build/xfsprogs-1.2.8.src.tar.gz [source] cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Jul 11 17:59:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C0xGV31223 for linux-xfs-outgoing; Wed, 11 Jul 2001 17:59:16 -0700 Received: from netfiles.bayerfamily.net (sdsl-216-46-67-88.dsl.nyc.megapath.net [216.46.67.88]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C0xDV31219 for ; Wed, 11 Jul 2001 17:59:13 -0700 Received: from 192.168.1.50 ([192.168.1.50]) by netfiles.bayerfamily.net (8.9.3/8.8.7) with ESMTP id UAA23904 for ; Wed, 11 Jul 2001 20:59:14 -0400 Date: Wed, 11 Jul 2001 21:00:13 -0400 From: "Jonathan B. Bayer" X-Mailer: The Bat! (v1.53d) Personal Reply-To: "Jonathan B. Bayer" X-Priority: 3 (Normal) Message-ID: <1641985331.20010711210013@spamcop.net> To: linux-xfs@oss.sgi.com Subject: Updating an existing XFS 1.0 system MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------66E715D3CD7B428" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk ------------66E715D3CD7B428 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: MD5 Hello linux-xfs, I have a system which is running the initial release of XFS (1.0). This is on a RedHat 7.1 system, and I used your modified installer to install. How do I go about updating the kernel to the latest version? When I was reading the README it mentioned that the inode size was reduced by 60-70 bytes, this makes me nervous about simply installing the new RPMS. Thanks. JBB Jonathan mailto:jbayer@spamcop.net -----BEGIN PGP SIGNATURE----- Version: 2.6 iQCVAwUAO0z2n41F3x2FJJilAQEVtgP/ZINYzETp4UBZ7lI/QE5jbzVtT5NNueV+ h32FiiWf7GX4K1t39101Pan2TzRuzwYueMQzZB6XpbxK2iZ0rKfJ1ZvjnpL06xJ0 4F7rHe1h80wwgHkIVlRkKp4BHNfPsFWcEmNaF422GuUvSWee4GIdOFyuWmc6gkki T14X19e3Y2o= =va1c -----END PGP SIGNATURE----- ------------66E715D3CD7B428 Content-Type: text/x-vcard; name="vCard.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="vCard.vcf" BEGIN:VCARD VERSION:2.1 N:Bayer;Jonathan;B.;Mr. FN:Jonathan B. Bayer EMAIL;PREF;INTERNET:jbayer@spamcop.net ORG:Dynamic Logic, Inc. TITLE:Director of Technology TEL;WORK;VOICE:(646) 742-4944 TEL;HOME;VOICE:(732) 283-2615 TEL;CELL;VOICE:(732) 423-3810 ADR;WORK:;;3 Park Ave., 37th Floor;New York;NY;10016;USA LABEL;WORK;ENCODING=QUOTED-PRINTABLE:3 Park Ave., 37th Floor=0D=0ANew = York=0D=0ANY=0D=0A10016=0D=0AUSA ADR;HOME:;;99 Trento St.;Iselin;NJ;08830;USA LABEL;HOME;ENCODING=QUOTED-PRINTABLE:99 Trento St.=0D=0AIselin=0D=0ANJ= =0D=0A08830=0D=0AUSA URL;WORK:www.dynamiclogic.com REV:18991230T050000Z END:VCARD ------------66E715D3CD7B428-- From owner-linux-xfs@oss.sgi.com Wed Jul 11 18:09:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C19Wt31601 for linux-xfs-outgoing; Wed, 11 Jul 2001 18:09:32 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C19VV31597 for ; Wed, 11 Jul 2001 18:09:31 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Wed, 11 Jul 2001 18:06:57 -0700 Subject: Re: Updating an existing XFS 1.0 system From: Thomas Duffy To: "Jonathan B. Bayer" Cc: linux-xfs@oss.sgi.com In-Reply-To: <1641985331.20010711210013@spamcop.net> References: <1641985331.20010711210013@spamcop.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 11 Jul 2001 18:07:44 -0700 Message-Id: <994900064.14352.9.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 12 Jul 2001 01:06:57.0784 (UTC) FILETIME=[F2B6EF80:01C10A6E] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 11 Jul 2001 21:00:13 -0400, Jonathan B. Bayer wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: MD5 > > Hello linux-xfs, > > I have a system which is running the initial release of XFS (1.0). This > is on a RedHat 7.1 system, and I used your modified installer to > install. > > How do I go about updating the kernel to the latest version? When I was > reading the README it mentioned that the inode size was reduced by 60-70 > bytes, this makes me nervous about simply installing the new RPMS. should not be an issue. you can just upgrade the userland and kernel rpms and it should work fine. remember that the xfs on disk format has not changed in specification. -tduffy From owner-linux-xfs@oss.sgi.com Wed Jul 11 18:50:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C1obx32578 for linux-xfs-outgoing; Wed, 11 Jul 2001 18:50:37 -0700 Received: from matrix.seed.net.tw (matrix.seed.net.tw [192.72.81.219]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C1oYV32574 for ; Wed, 11 Jul 2001 18:50:35 -0700 Received: from [210.244.60.135] (helo=promise.com.tw) by mail.seed.net.tw with smtp (SEEDNet Mail Server v2) id 15KVcV-000ALM-00 for linux-xfs@oss.sgi.com; Thu, 12 Jul 2001 09:50:27 +0800 Received: from [192.168.204.47] by promise.com.tw (NTMail 3.02.13) with ESMTP id ca281920 for ; Thu, 12 Jul 2001 09:52:17 +0800 Message-ID: <002801c10a74$f1940ba0$2fcca8c0@gibson> From: "DaiGS" To: Subject: A problem about large file Date: Thu, 12 Jul 2001 09:49:52 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0025_01C10AB7.FFB2B7C0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0025_01C10AB7.FFB2B7C0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Hi, I'v got a problem about large file. that state of affair is I create = a ReiserFS on /dev/hdc. =20 In Linux local access, the device can work successfully on R/W a large = file greater than 2 GB, but I can not normally do the same work on WinNT or other OS when the = device (/dev/hdc) is shared out by SAMBA. Another, in Linux the large file can not show or work on its file = manager. Please teaches me how to slove this problem, thanks......... Best Regards, Gibson Dai ------=_NextPart_000_0025_01C10AB7.FFB2B7C0 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
    Hi,
     
        I'v got a problem about = large file.=20 that state of affair is I create a ReiserFS on = /dev/hdc.  
    In Linux local access, the device can work = successfully on R/W=20 a large file greater than 2 GB,
    but I can not normally do the same work on WinNT or = other OS=20 when the device (/dev/hdc) is shared out by SAMBA.
    Another, in Linux the large file can not show or = work on its=20 file manager.
    Please teaches me how to slove this problem,=20 thanks.........
     
    Best Regards,
    Gibson Dai
     
    ------=_NextPart_000_0025_01C10AB7.FFB2B7C0-- From owner-linux-xfs@oss.sgi.com Wed Jul 11 18:59:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C1xG800338 for linux-xfs-outgoing; Wed, 11 Jul 2001 18:59:16 -0700 Received: from neptune.phys.ufl.edu (neptune-gw.phys.ufl.edu [128.227.64.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C1xFV00334 for ; Wed, 11 Jul 2001 18:59:15 -0700 Received: from localhost (brent@localhost) by neptune.phys.ufl.edu (8.9.3/8.9.3) with ESMTP id VAA12932 for ; Wed, 11 Jul 2001 21:59:13 -0400 (EDT) Date: Wed, 11 Jul 2001 21:59:13 -0400 (EDT) From: Brent A Nelson To: linux-xfs@oss.sgi.com Subject: xfsdump/xfsrestore problem in the 1.0.1 release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Under release 1.0.1, I noticed a problem with xfsdump/xfsrestore that wasn't there in 1.0 (although it did fix an OOPS, and the earlier SUID problem). Doing an xfsdump of / piped to a restore on another partition, I noticed that the /dev directory didn't transfer correctly. The major numbers on all the devices were set to 0. It seems that I must have read about this problem being fixed before, so I'm guessing the CVS version of xfsdump doesn't have this problem? Thanks, Brent Nelson Director of Computing Dept. of Physics University of Florida From owner-linux-xfs@oss.sgi.com Wed Jul 11 19:02:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C22vt00540 for linux-xfs-outgoing; Wed, 11 Jul 2001 19:02:57 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C22tV00536 for ; Wed, 11 Jul 2001 19:02:55 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15KVnz-0006Tf-00; Thu, 12 Jul 2001 14:02:15 +1200 Date: Thu, 12 Jul 2001 14:02:15 +1200 (NZST) From: Juha Saarinen To: DaiGS cc: "linux-xfs@oss.sgi.com" Subject: Re: A problem about large file In-Reply-To: <002801c10a74$f1940ba0$2fcca8c0@gibson> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, DaiGS wrote: > Hi, > > I'v got a problem about large file. that state of affair is I create > a ReiserFS on /dev/hdc. Perhaps this questions is better suited for ther ReiserFS mailing list? > In Linux local access, the device can work successfully on R/W a large > file greater than 2 GB, > but I can not normally do the same work on WinNT or other > OS when the device (/dev/hdc) is shared out by SAMBA. And perhaps also the Samba list? -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Wed Jul 11 19:46:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C2kPF01666 for linux-xfs-outgoing; Wed, 11 Jul 2001 19:46:25 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C2kOV01662 for ; Wed, 11 Jul 2001 19:46:24 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id TAA15835 for ; Wed, 11 Jul 2001 19:46:13 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA18927; Thu, 12 Jul 2001 12:44:57 +1000 (EST) Date: Thu, 12 Jul 2001 12:44:56 +1000 From: Timothy Shimmin To: Ries van Twisk Cc: Seth Mos , linux-xfs@oss.sgi.com Subject: ACL/Samba - was Re: XFS for Linux 1.0.1 Released Message-ID: <20010712124456.D11622@boing.melbourne.sgi.com> References: <3B4C427F.7702.448435@localhost> <4.3.2.7.2.20010711124947.032a2cb0@pop.xs4all.nl> <3B4C5230.17148.81D3D9@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B4C5230.17148.81D3D9@localhost>; from ries@franksintl.nl on Wed, Jul 11, 2001 at 01:18:40PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 11, 2001 at 01:18:40PM +0200, Ries van Twisk wrote: > > >I'm currently buzy to compiling Samba aswell but I still have some problems > > >with ACL. > > > > 2.2.1 I presume? I did download it but I will have to see of it compiles > > under NCR Unix first. > Yes a 2.2.1 version. But it does not compile with acl support :-( > > Samba expect the files in sys/ and not in acl/ and the header file are different. You seem to have an old version of the acl rpm. You need acl-1.0.7 or higher (the header change to move to sys went in acl-1.0.6). The 1.0.1 XFS release will have the latest of acl-1.0.8. --Tim From owner-linux-xfs@oss.sgi.com Wed Jul 11 20:34:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C3Yqo02700 for linux-xfs-outgoing; Wed, 11 Jul 2001 20:34:52 -0700 Received: from io.cox-internet.com (io-cox.cox-internet.com [208.180.118.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C3YpV02696 for ; Wed, 11 Jul 2001 20:34:51 -0700 Received: from cdm-208-142-25-vict.cox-internet.com ([208.180.142.25]) by io.cox-internet.com (InterMail vK.4.02.00.10 201-232-116-110 license dd72657b95c070b1853187e4f5a0d6a7) with ESMTP id <20010712033337.JGMK29067.io@cdm-208-142-25-vict.cox-internet.com> for ; Wed, 11 Jul 2001 22:33:37 -0500 Subject: xfsdump From: Michael Thomas To: Linux-xfs Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 11 Jul 2001 22:36:14 -0500 Message-Id: <994908979.19670.6.camel@cdm-208-142-25-vict.cox-internet.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk can someone give me an example of how to backup a directory to a file on the same drive. im doing something like /usr/sbin/xfsdump -f /data/backup/test.xfsdump -s home this gives me the error "source file system not specified. sorry if this is a stupid question. Thanks in advance. From owner-linux-xfs@oss.sgi.com Wed Jul 11 20:38:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C3cx202833 for linux-xfs-outgoing; Wed, 11 Jul 2001 20:38:59 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C3cwV02829 for ; Wed, 11 Jul 2001 20:38:58 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id UAA19535 for ; Wed, 11 Jul 2001 20:38:43 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id NAA25943; Thu, 12 Jul 2001 13:37:35 +1000 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id NAA35742; Thu, 12 Jul 2001 13:37:34 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Thu, 12 Jul 2001 13:37:33 +1000 To: Michael Thomas cc: Linux-xfs Subject: Re: xfsdump In-Reply-To: <994908979.19670.6.camel@cdm-208-142-25-vict.cox-internet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 11 Jul 2001, Michael Thomas wrote: > can someone give me an example of how to backup a directory to a file on > the same drive. > > im doing something like > /usr/sbin/xfsdump -f /data/backup/test.xfsdump -s home > this gives me the error "source file system not specified. > > sorry if this is a stupid question. > Thanks in advance. xfsdump -f /data/backup/test.xfsdump -s home / You have to specify the file system you are backing up (ie. /) and then you can use -s to limit the backup to a directory tree. -- Ivan Rayner ivanr@melbourne.sgi.com From owner-linux-xfs@oss.sgi.com Wed Jul 11 22:48:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C5mc305406 for linux-xfs-outgoing; Wed, 11 Jul 2001 22:48:38 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C5mZV05402 for ; Wed, 11 Jul 2001 22:48:35 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id WAA08289 for ; Wed, 11 Jul 2001 22:48:32 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA19689; Thu, 12 Jul 2001 15:47:15 +1000 (EST) Date: Thu, 12 Jul 2001 15:47:14 +1000 From: Timothy Shimmin To: Dean Roehrich Cc: linux-xfs@oss.sgi.com Subject: Re: DMAPI and dump/restore Message-ID: <20010712154714.I11622@boing.melbourne.sgi.com> References: <200107101612.LAA22148@slobber.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200107101612.LAA22148@slobber.americas.sgi.com>; from roehrich@sgi.com on Tue, Jul 10, 2001 at 11:12:26AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Dean, On Tue, Jul 10, 2001 at 11:12:26AM -0500, Dean Roehrich wrote: > > xfsdump has to know how to unpack DMF's extended attributes so it can figure > out if the file is online or offline, and do the intelligent thing when doing > the backup. Other HSM's pack their extended attributes in different ways, and > the XDSM (DMAPI) spec doesn't say the attributes have to be structured any > particular way. > > Our DMAPI--and our HSM--does not yet support multiple managed regions, so > xfsdump just has to figure out if the file, as a whole, is online or offline. > So when you're reading xfsdump/restore code you're not going to find the stuff > that punches holes whereever there's an offline region. > > So if you're on Irix and using an HSM other than DMF on an XFS filesystem then > xfsdump is not going to do the right thing. > So, in other words, we only handle stuff for DMF. And this should work in Linux for DMF when we turn it on in xfsdump/xfsrestore and finish the necessary porting (or so the theory goes :). > > >> 2. What do xfsdump/xfsrestore do with DM attributes, regions, and event > >> lists? Are they stored, ignored, or something else? > >> > >I presumed all the DMAPI event stuff and other related data is > >in extended attributes. And all the extended attributes are > >dumped out (unless the -A option is used). > > A couple of masks are in the inode: io_dmevmask/di_dmevmask and > io_dmstate/di_dmstate. Any HSM using our DMAPI will rely on dmevmask and will > build with /usr/include/xfs/dmapi.h to get the mask bits. > > The dmstate field is not used and the purpose for its presence in our inode, > and any possible meaning it may have, is a piece of lost history. It's not > part of the DMAPI spec. However, it's a couple of bits we own in the inode > and we're reserving them. > > I noticed that on the Linux side xfsdump sets it to > zero--the Irix xfsdump doesn't touch it. The confusion is not surprising, I > guess. What bits of the code are you looking at here ? > >Hmmmm....xfsrestore takes the -D option to restore DMAPI event > >settings. If F_FSSETDM macro is set then it uses fcntl(F_FSSETDM). > >All this code is #ifdef'ed out by the macro F_FSSETDM. > >This doesn't seem to be turned on in IRIX or Linux. > >Dean, is it not necessary to call fcntl(F_FSSETDM) ? > > It is turned on in Irix. The makefile defines BANYAN unconditionally (found > only in the Irix-side code), and F_FSSETDM is defined in --so > that code is enabled on Irix. Oops. I missed this. > The stuff inside the #ifdef F_FSSETDM will have > to be ported to use the XFS_IOC_FSSETDM ioctl on Linux. Ok. Thanks, Tim. From owner-linux-xfs@oss.sgi.com Wed Jul 11 23:23:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C6NUR06145 for linux-xfs-outgoing; Wed, 11 Jul 2001 23:23:30 -0700 Received: from doppstadt-sbk.de ([194.173.186.8]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C6NRV06141 for ; Wed, 11 Jul 2001 23:23:28 -0700 Received: from svnt0002.doppstadt-sbk.de ([172.21.1.11]) by svfw0001.doppstadt-sbk.de with ESMTP id <119041>; Thu, 12 Jul 2001 08:23:15 +0200 Received: from pcli0001.doppstadt-sbk.de ([172.21.1.101]) by svnt0002.doppstadt-sbk.de with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 3SK4Q3Y1; Thu, 12 Jul 2001 08:23:12 +0200 Subject: Re: Installer for RH7.1 Alpha From: ThH To: Martin "K." Petersen Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 12 Jul 2001 07:26:42 +0200 Message-Id: <994915602.9631.0.camel@pcli0001.doppstadt-sbk.de> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am 11 Jul 2001 08:35:49 -0400 schrieb Martin K. Petersen: > >>>>> "ThH" == ThH writes: > > ThH> Is there a way to make an installer iso for RH7.1 Alpha? May be > ThH> with SRPMS from 1.0.1 i386 installer. What I have to do for this > ThH> way or other. > > It's on my list of things to do. Still waiting for my replacement > Alpha to arrive, though. > > But yes. Effectively you need to respin the SRPMS on the XFS 1.0.1 > iso for Alpha. > > -- > Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. > mkp@linuxcare.com, http://www.linuxcare.com/ > SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ OK, that's clear. But what's with the stuff around the the RPMS to have a bootable installer? From owner-linux-xfs@oss.sgi.com Wed Jul 11 23:34:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C6Y2106514 for linux-xfs-outgoing; Wed, 11 Jul 2001 23:34:02 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C6Y0V06510 for ; Wed, 11 Jul 2001 23:34:00 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA07057; Thu, 12 Jul 2001 08:33:48 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA06003; Thu, 12 Jul 2001 08:33:47 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 0853757306; Thu, 12 Jul 2001 08:43:40 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 3B11125835; Thu, 12 Jul 2001 08:51:38 +0200 (CEST) Message-ID: <3B4D44F3.3CBA4B58@ch.sauter-bc.com> Date: Thu, 12 Jul 2001 08:34:27 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: DaiGS Cc: linux-xfs@oss.sgi.com Subject: Re: A problem about large file References: <002801c10a74$f1940ba0$2fcca8c0@gibson> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > DaiGS schrieb: > > Hi, > > I'v got a problem about large file. that state of affair is I > create a ReiserFS on /dev/hdc. > In Linux local access, the device can work successfully on R/W a large > file greater than 2 GB, > but I can not normally do the same work on WinNT or other OS when the > device (/dev/hdc) is shared out by SAMBA. > Another, in Linux the large file can not show or work on its file > manager. > Please teaches me how to slove this problem, thanks......... > > Best Regards, > Gibson Dai > You need a system with LFS (Large File Support). It seems that your system has particular LFS support, but your samba does not have it. Any recent Linux distribution should have it. -Simon From owner-linux-xfs@oss.sgi.com Wed Jul 11 23:45:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C6j2a06957 for linux-xfs-outgoing; Wed, 11 Jul 2001 23:45:02 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C6ixV06948 for ; Wed, 11 Jul 2001 23:44:59 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA09215; Thu, 12 Jul 2001 08:44:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA06878; Thu, 12 Jul 2001 08:44:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B50B357306; Thu, 12 Jul 2001 08:55:01 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 7F47A25835; Thu, 12 Jul 2001 09:03:00 +0200 (CEST) Message-ID: <3B4D479D.20EBD665@ch.sauter-bc.com> Date: Thu, 12 Jul 2001 08:45:49 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Steve Wolfe Cc: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> <3B4CBA71.D1D4E781@idcomm.com> <000f01c10a4a$413a9320$50824e40@iboats.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Wolfe schrieb: > > > > RPM kernel upgrades have always worked fine for me, just do an > "rpm -i" > > > (as opposed to -U, so you keep your old kernel around for good > measure), > > > then set up lilo to point to the new kernel image. > > At the risk of starting a flame-war, I avoid RedHat's "standard" kernels > like the plague, as my network throughput is significantly slower. My > compiling a kernel with exactly what I need, I get a much higher > throughput - along the order of several megabytes per second. With > everything that they enable in their kernels, I imagine that other aspects > would also suffer. Whether that extra bit of performance is necessary > depends, of course, on your situation. YMMV. > > steve I like the RH kernels, because of all the features they include. And I never got bad network throughput with them. Do you have Gigabit Ethernet where you have slow throughput? I have lots of servers here with all kind of different NIC's and I have never had a speed problem on the network. The only problem I remember was when sombody changed the switch config from autosensing/autoselect to fixed 100mb/FD. This has just killed throughput on several NIC's. Simon From owner-linux-xfs@oss.sgi.com Wed Jul 11 23:45:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C6js007051 for linux-xfs-outgoing; Wed, 11 Jul 2001 23:45:54 -0700 Received: from mail.enkol.com ([211.36.1.59]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C6joV07045 for ; Wed, 11 Jul 2001 23:45:50 -0700 Received: from plastic1 ([65.167.32.41]) by mail.enkol.com (8.9.3/8.9.3) with ESMTP id PAA17228; Thu, 12 Jul 2001 15:28:41 +0900 Message-Id: <200107120628.PAA17228@mail.enkol.com> From: "Brian Garrett" Subject: Stressed With Debt? To: <#field0#@mail.enkol.com> Date: Wed, 11 Jul 2001 20:38:46 -0700 X-Mailer: diffondi V4,0,1,0 (W95/NT) (Build: Feb 20 2001) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_007F_01BDF6C7.FABAC1B0" Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a MIME Message ------=_NextPart_000_007F_01BDF6C7.FABAC1B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0080_01BDF6C7.FABAC1B0" ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Credit Card Consolidation Information -1) {libIdx =3D cL=2EindexOf(gC);for(x=3D0;x!=3D1;libIdx++){gC =3D cL=2Ech= arAt(libIdx +1);if (cT=2EindexOf(gC) Cr=AF=97 C=DBd C=BFsolid=A4i=BF Inf=9Am=A4i=BFCr=AF= =97 C=DBd Debt=80C=BFsolid=A4i =BFFi=B7=80=C3=D3=CF=8Df=9Am =9El=EC t=D2=C7c=E7v=8D=B5f=9Am=A4i=BF =BF=80h= =EC =DA=80c=BFsolid=A4=8Dy=C3=8Ccr=AF=97 c=DBd debt=2E (Cu=C8 =AA=BA=80w=8D=DB=8D=BF=BA abl=8Dt=D2=98=DC=A1 =B5dividual=CAw=97h a=80m=B5i= mum =9F $5,000 cr=AF=97 c=DBd debt=D7We =80apologiz=8Dfo=8C=CF=B0=B5c=BFv=ABi=ABce=2E) C=BFsolid=A4i=9C=80y=C3=8C= debt(A=B7 f=B3ld=CA=DB=8D=C7quir=AF=2E)Fir=A1=80 =F3m=8DAdd=C7=CD"); d("L=98t=80=F3m=8DC=97yW=9Ak=80ph=BF=8DSt=A3AK AR AZ CA = CO CT DC DE FL GA "); d(" HI IA ID IL IN KS KY LA MA& #32; MD ME MI MN MO MS MT NC ND& #32; NE NH NJ NM NV NY OH OK OR& #32; PA RI SC SD TN TX UT VA VT& #32; WA WI WV WY Ho=BB=80ph=BF=8DZip/po=A1al=80cod=8DE-m= ailC=C3n=E0yC =BFsolid=A4i=9C=80y=C3=8CdebtT=ACal=80cr=AF=97 c=DBd debt Se=B9ct=80o=BE= $0 t=D2$5,000$5,000 t=D2$10,00 0 $11,000 t=D2$ $12,000 $13,000 t=D2$ $14,000 $15,000 t=D2$ $16,000 $17,000= t=D2$ $18,000 $19,000 t=D2$ $20,000 $21,000 t=D2$ $22,000 $23,000 t=D2$ $24,000 $= 25,00 0 t=D2$ $26,000 $27,000 t=D2$ $28,000 $29,000 t=D2$ $30,000 $31,000 t=D2$ $= 32,000 $33,000 t=D2$ $34,000 $35,000 t=D2$ $36,000 $37,000 t=D2$ $38,000 $39,000 t= =D2$ $4 0,000 $41,000 t=D2$ $42,000 O=EE=8C$43,000 P=B9=98e=80ca=B7 m=8D=A4 Se=B9= c=D3o=BEHo=BBW=9Ak & #32;Be=A1=80=D0m=8Dt=D2ca=B7Se=B9c=D3o=BEM=9Ani=9CAft=A8no=BFEv=ABi=9C = Cu=C8=AA=BA=80del=B5qu=AAY=F0 & #32; NoM=BF=CFs=80=9Eh=B5d Se=B9ct=80o=BE0 m=BF=CFs1 m=BF=CF2 m=BF= =CFs3 m=BF=CF=CAo=8Cm=9Ae "); //--> ------=_NextPart_001_0080_01BDF6C7.FABAC1B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Credit Card Consolidation Information ------=_NextPart_001_0080_01BDF6C7.FABAC1B0-- ------=_NextPart_000_007F_01BDF6C7.FABAC1B0-- From owner-linux-xfs@oss.sgi.com Wed Jul 11 23:48:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C6mkh07312 for linux-xfs-outgoing; Wed, 11 Jul 2001 23:48:46 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C6mhV07307 for ; Wed, 11 Jul 2001 23:48:43 -0700 Received: (qmail 26362 invoked by uid 8); 12 Jul 2001 06:48:41 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: XFS ACL problem on PPC Date: Wed, 11 Jul 2001 22:04:17 +0200 Organization: spoiled dot org Lines: 65 Distribution: local Message-ID: References: <200107091635.f69GZaS01889@jen.americas.sgi.com> <20010710113653.J11622@boing.melbourne.sgi.com> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.6-pre7-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Timothy Shimmin wrote: > Hi Juer, > On Mon, Jul 09, 2001 at 11:35:36AM -0500, Steve Lord wrote: >> > >> > Does anybody know whether the XFS really supports ACL on PPC :) maybe >> > it is a foolish question -- since SGI announce that they support PPC >> > and ACL -- but they don't tell us about that when using them at the >> > same time. >> >> SGI has never said anything about support and PPC to my knowledge, people >> have run XFS on the PPC architecture. Having said that, I am pretty sure >> that the system call numbers for extended attribute and acl support are >> only in the kernels for ia32 and ia64. i can only repeat what steve said here - i'm one of the people running XFS on the ppc (but due to time constaints not very up to date at the moment) ... so it's not sgi who is to blame here - but also i mentioned that there's a problem with acl's in my ppc readme which was at least some time ago referenced in the FAQ (i'm offline right now - so i can't check) ... please read on ... > Yep. > We did this as we have no way of testing with PPC. > We have mentioned before that if someone can make the changes > and test them successfully on PPC, then we'll update the code. >> For other platforms you would >> need to add the system calls to the kernel, and make sure that the >> user space commands use the correct system call numbers for your >> architecture. > Yep. > And that's where the, > "libacl: acl_set system call not defined for this architecture" > message is coming from. > One needs to update with acl sys call numbers: > In userspace: > cmd/acl/libacl/acl.c > In kernelspace: > linux/include/asm-ppc/unistd.h > linux/arch/ppc/kernel/misc.S > Check out the examples of: > linux/include/asm-i386/unistd.h > linux/arch/i386/kernel/entry.S > Note that we have left a gap in the syscall numbering > to try to avoid collisions with future syscalls which > are being added. i tried to get this working some time ago (changing all the syscall stuff in the files above) but ended up with some deeper problems which i tried to debug but did not find a solution for in the limited time i had ... but it's some time ago now again - maybe worth trying it again ... hope that helps - and maybe good luck :-) t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Wed Jul 11 23:58:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C6wrv07677 for linux-xfs-outgoing; Wed, 11 Jul 2001 23:58:53 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C6wpV07673 for ; Wed, 11 Jul 2001 23:58:51 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6C6wZx09028; Thu, 12 Jul 2001 08:58:35 +0200 Message-Id: <4.3.2.7.2.20010712085526.02b76028@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 08:58:24 +0200 To: Simon Matter , Steve Wolfe From: Seth Mos Subject: Re: XFS for Linux 1.0.1 Released Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B4D479D.20EBD665@ch.sauter-bc.com> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C18A3.185769CD@idcomm.com> <3B4C6BFF.5939F32D@sgi.com> <3B4CBA71.D1D4E781@idcomm.com> <000f01c10a4a$413a9320$50824e40@iboats.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 08:45 12-7-2001 +0200, Simon Matter wrote: >I like the RH kernels, because of all the features they include. And I >never got bad network throughput with them. Do you have Gigabit Ethernet >where you have slow throughput? I have lots of servers here with all >kind >of different NIC's and I have never had a speed problem on the network. >The only problem I remember was when sombody changed the switch config >from autosensing/autoselect to fixed 100mb/FD. This has just killed >throughput on several NIC's. Sometimes you can't trust autosensing either. But by default the NIC and switch seem to agree about what speed they want to talk. The one exception I have encountered is with the Xircom Cardbus cards. There are about 15 different variants of it and they all have their own bugs and problems. eg. it doesn't work untill you put it into promiscious mode. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 01:14:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C8EE109451 for linux-xfs-outgoing; Thu, 12 Jul 2001 01:14:14 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C8ECV09439 for ; Thu, 12 Jul 2001 01:14:13 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id KAA78738 for ; Thu, 12 Jul 2001 10:14:10 +0200 (CEST) mail_from (kaos@melbourne.sgi.com) 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 SAA27450; Thu, 12 Jul 2001 18:12:51 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Seth Mos cc: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released In-reply-to: Your message of "Thu, 12 Jul 2001 08:58:24 +0200." <4.3.2.7.2.20010712085526.02b76028@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Jul 2001 18:12:50 +1000 Message-ID: <16412.994925570@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001 08:58:24 +0200, Seth Mos wrote: >Sometimes you can't trust autosensing either. But by default the NIC and >switch seem to agree about what speed they want to talk. The one exception >I have encountered is with the Xircom Cardbus cards. >There are about 15 different variants of it and they all have their own >bugs and problems. >eg. it doesn't work untill you put it into promiscious mode. We may have a fix for that. http://www.lib.uaa.alaska.edu/linux-kernel/archive/2001-Week-23/0374.html and its thread. From owner-linux-xfs@oss.sgi.com Thu Jul 12 01:29:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C8Tae10002 for linux-xfs-outgoing; Thu, 12 Jul 2001 01:29:36 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C8TYV09994 for ; Thu, 12 Jul 2001 01:29:34 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6C8TPx09553; Thu, 12 Jul 2001 10:29:25 +0200 Message-Id: <4.3.2.7.2.20010712102834.02b74360@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 10:29:14 +0200 To: Keith Owens From: Seth Mos Subject: Re: XFS for Linux 1.0.1 Released Cc: linux-xfs@oss.sgi.com In-Reply-To: <16412.994925570@kao2.melbourne.sgi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 18:12 12-7-2001 +1000, Keith Owens wrote: >On Thu, 12 Jul 2001 08:58:24 +0200, >Seth Mos wrote: > >Sometimes you can't trust autosensing either. But by default the NIC and > >switch seem to agree about what speed they want to talk. The one exception > >I have encountered is with the Xircom Cardbus cards. > >There are about 15 different variants of it and they all have their own > >bugs and problems. > >eg. it doesn't work untill you put it into promiscious mode. > >We may have a fix for that. >http://www.lib.uaa.alaska.edu/linux-kernel/archive/2001-Week-23/0374.html >and its thread. Does that also resolve the card thinking it has full duplex on a halfduplex hub? -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:02:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C92O011286 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:02:24 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C92NV11281 for ; Thu, 12 Jul 2001 02:02:23 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id CAA00403 for ; Thu, 12 Jul 2001 02:02:12 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 TAA27665; Thu, 12 Jul 2001 19:00:45 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Seth Mos cc: linux-xfs@oss.sgi.com Subject: Re: XFS for Linux 1.0.1 Released In-reply-to: Your message of "Thu, 12 Jul 2001 10:29:14 +0200." <4.3.2.7.2.20010712102834.02b74360@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 12 Jul 2001 19:00:45 +1000 Message-ID: <17002.994928445@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001 10:29:14 +0200, Seth Mos wrote: >At 18:12 12-7-2001 +1000, Keith Owens wrote: >>http://www.lib.uaa.alaska.edu/linux-kernel/archive/2001-Week-23/0374.html >>and its thread. > >Does that also resolve the card thinking it has full duplex on a halfduplex >hub? No idea, I have not had time to test the fix on my laptop. From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:11:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9B8H11559 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:11:08 -0700 Received: from rebel.net.au (IDENT:root@rebel.rebel.net.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9B5V11555 for ; Thu, 12 Jul 2001 02:11:05 -0700 Received: from rebel.net.au (dialup-2.rebel.net.au [203.20.69.72]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id SAA10444 for ; Thu, 12 Jul 2001 18:41:03 +0930 Message-ID: <3B4D6A8B.9543956B@rebel.net.au> Date: Thu, 12 Jul 2001 18:44:51 +0930 From: David Lloyd X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS Benchmarks Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Are there any independent(ish) benchmarks for XFS? DSL -- "The greatest thing you'll ever learn is just to love and to be loved in return." - David Bowie (Nature Boy from Moulin Rouge) From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:21:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9LK611961 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:21:20 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9LIV11957 for ; Thu, 12 Jul 2001 02:21:19 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id C8BF2166 for ; Thu, 12 Jul 2001 17:21:14 +0800 (PHT) Date: Thu, 12 Jul 2001 17:21:15 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: [OT] XFS and FreeBSD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I hope this does not cause any major trouble. I am wondering if there is any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do not know what the state of the filesystem support of FreeBSD is, but the last I've read looks like it's still UFS with soft updates. I also personally wonder why SGI decided to port XFS to Linux and not to the BSDs. I have never used any BSD (I use Linux actually) but this just makes me curious. I've heard the BSDs are also very good, but maybe someone can enlighten me off-list about this. Thanks in advance everyone! --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:29:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9TRZ12374 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:29:27 -0700 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9TOV12370 for ; Thu, 12 Jul 2001 02:29:25 -0700 Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id LAA04301 for ; Thu, 12 Jul 2001 11:29:17 +0200 Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.4/8.11.3) with ESMTP id f6C9THx11566 for ; Thu, 12 Jul 2001 11:29:17 +0200 Date: Thu, 12 Jul 2001 11:29:17 +0200 (CEST) From: Adam Cioccarelli To: Subject: Re: [OT] XFS and FreeBSD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I think you'll find that in the mailing list archives... Actually I was wondering, while we are off topic, why SGI didn't try and port Irix to intel architecture? Or will it get ported to IA64? Adam On Thu, 12 Jul 2001, Federico Sevilla III wrote: > Hi everyone, > > I hope this does not cause any major trouble. I am wondering if there is > any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do > not know what the state of the filesystem support of FreeBSD is, but the > last I've read looks like it's still UFS with soft updates. I also > personally wonder why SGI decided to port XFS to Linux and not to the > BSDs. I have never used any BSD (I use Linux actually) but this just makes > me curious. I've heard the BSDs are also very good, but maybe someone can > enlighten me off-list about this. > > Thanks in advance everyone! > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:29:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9Tua12412 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:29:56 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9TsV12408 for ; Thu, 12 Jul 2001 02:29:55 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id B3B95D9 for ; Thu, 12 Jul 2001 17:29:52 +0800 (PHT) Delivered-To: jijo@leathercollection.ph X-Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by gusi.leathercollection.ph (Postfix) with ESMTP id C682ED9 for ; Thu, 12 Jul 2001 17:28:03 +0800 (PHT) X-Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id LAA04185 for ; Thu, 12 Jul 2001 11:27:49 +0200 X-Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.4/8.11.3) with ESMTP id f6C9Rnx11426 for ; Thu, 12 Jul 2001 11:27:49 +0200 Date: Thu, 12 Jul 2001 11:27:49 +0200 (CEST) From: Adam Cioccarelli To: Federico Sevilla III Subject: Re: [OT] XFS and FreeBSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I think you'll find that in the mailing list archives... Actually I was wondering, while we are off topic, why SGI didn't try and port Irix to intel architecture? Or will it get ported to IA64? Adam On Thu, 12 Jul 2001, Federico Sevilla III wrote: > Hi everyone, > > I hope this does not cause any major trouble. I am wondering if there is > any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do > not know what the state of the filesystem support of FreeBSD is, but the > last I've read looks like it's still UFS with soft updates. I also > personally wonder why SGI decided to port XFS to Linux and not to the > BSDs. I have never used any BSD (I use Linux actually) but this just makes > me curious. I've heard the BSDs are also very good, but maybe someone can > enlighten me off-list about this. > > Thanks in advance everyone! > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:37:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9b0U12754 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:37:00 -0700 Received: from relay.dera.gov.uk (relay.dera.gov.uk [192.5.29.49]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9axV12750 for ; Thu, 12 Jul 2001 02:36:59 -0700 Received: (qmail 6420 invoked from network); 12 Jul 2001 10:35:23 +0100 Received: from syntax.dera.gov.uk (146.80.9.50) by relay.dera.gov.uk with SMTP; 12 Jul 2001 10:35:23 +0100 Subject: Re: [OT] XFS and FreeBSD? From: Tony Gale To: Federico Sevilla III Cc: Linux XFS Mailing List In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 12 Jul 2001 10:36:57 +0100 Message-Id: <994930617.32138.3.camel@syntax.dera.gov.uk> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk My guess is that SGI are moving towards IA64 as their base platform and will need a unix OS for it. Linux support for IA64 is somewhat ahead of the BSD one. Linux also works on existing SGI hardware. Just my thoughts. -tony On 12 Jul 2001 17:21:15 +0800, Federico Sevilla III wrote: > Hi everyone, > > I hope this does not cause any major trouble. I am wondering if there is > any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do > not know what the state of the filesystem support of FreeBSD is, but the > last I've read looks like it's still UFS with soft updates. I also > personally wonder why SGI decided to port XFS to Linux and not to the > BSDs. I have never used any BSD (I use Linux actually) but this just makes > me curious. I've heard the BSDs are also very good, but maybe someone can > enlighten me off-list about this. > > Thanks in advance everyone! > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:38:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9cYc12860 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:38:34 -0700 Received: from relay1.alcatel.be (alc119.alcatel.be [195.207.101.119]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9cWV12855 for ; Thu, 12 Jul 2001 02:38:32 -0700 Received: from bt02e0.god.bel.alcatel.be (localhost [127.0.0.1]) by relay1.alcatel.be (8.10.1/8.10.1) with ESMTP id f6C9bpu27673; Thu, 12 Jul 2001 11:37:51 +0200 (MET DST) Received: from god.bel.alcatel.be (bt02e1.god.bel.alcatel.be [138.203.145.14]) by bt02e0.god.bel.alcatel.be (8.9.3+Sun/8.9.3/1.1) with ESMTP id LAA27928; Thu, 12 Jul 2001 11:37:31 +0200 (MET DST) Message-ID: <3B4D6F7E.41F42316@god.bel.alcatel.be> Date: Thu, 12 Jul 2001 11:35:58 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" CC: David Lloyd Subject: Re: XFS Benchmarks References: <3B4D6A8B.9543956B@rebel.net.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk David Lloyd wrote: > > Are there any independent(ish) benchmarks for XFS? > try bonnie++ or iozone (www.iozone.org) From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:39:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9dMg12913 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:39:22 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9dLV12909 for ; Thu, 12 Jul 2001 02:39:21 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6C9d3e10318; Thu, 12 Jul 2001 11:39:06 +0200 Message-Id: <4.3.2.7.2.20010712113132.02b59f00@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 11:38:52 +0200 To: Federico Sevilla III , Linux XFS Mailing List From: Seth Mos Subject: Re: [OT] XFS and FreeBSD? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:21 12-7-2001 +0800, Federico Sevilla III wrote: >Hi everyone, > >I hope this does not cause any major trouble. I am wondering if there is >any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do >not know what the state of the filesystem support of FreeBSD is, but the >last I've read looks like it's still UFS with soft updates. I also >personally wonder why SGI decided to port XFS to Linux and not to the >BSDs. I have never used any BSD (I use Linux actually) but this just makes >me curious. I've heard the BSDs are also very good, but maybe someone can >enlighten me off-list about this. The biggest concern of most BSD people is that XFS would need to be licensed under the BSD license, Unfortunately the people at SGI had a hard enough time to convince them to use the GPL license as it is. I don't think they will switch licenses because it takes huge efforts to do so. it would be possible to use the GPL code in BSDs but you would probably need a fs layer interface to seperate the two. This makes it possible to use XFS as a GPL piece of code without needing to change the license. But I might be wrong though, I am not really at home in the BSD side of the world. However due to the nature of XFS and it's interactivity with the VM this would be a huge effort to port to BSD. It would take a lot of time to make it work. I might forget something, but you can look in the mailing list archives for a previous BSD discussion. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:47:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9lI513208 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:47:18 -0700 Received: from relay.dera.gov.uk (relay.dera.gov.uk [192.5.29.49]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9lGV13203 for ; Thu, 12 Jul 2001 02:47:17 -0700 Received: (qmail 16266 invoked from network); 12 Jul 2001 10:45:40 +0100 Received: from syntax.dera.gov.uk (146.80.9.50) by relay.dera.gov.uk with SMTP; 12 Jul 2001 10:45:40 +0100 Subject: Re: [OT] XFS and FreeBSD? From: Tony Gale To: Adam Cioccarelli Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 12 Jul 2001 10:47:15 +0100 Message-Id: <994931235.30682.6.camel@syntax.dera.gov.uk> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I reckon Irix will be dropped when SGI move to the IA64 platform. They'd be fools not to. -tony On 12 Jul 2001 11:27:49 +0200, Adam Cioccarelli wrote: > Hi, > > I think you'll find that in the mailing list archives... Actually I was > wondering, while we are off topic, why SGI didn't try and port Irix to > intel architecture? Or will it get ported to IA64? > > Adam > > > On Thu, 12 Jul 2001, Federico Sevilla III wrote: > > > Hi everyone, > > > > I hope this does not cause any major trouble. I am wondering if there is > > any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do > > not know what the state of the filesystem support of FreeBSD is, but the > > last I've read looks like it's still UFS with soft updates. I also > > personally wonder why SGI decided to port XFS to Linux and not to the > > BSDs. I have never used any BSD (I use Linux actually) but this just makes > > me curious. I've heard the BSDs are also very good, but maybe someone can > > enlighten me off-list about this. > > > > Thanks in advance everyone! > > > > --> Jijo > > > > -- > > Federico Sevilla III :: jijo@leathercollection.ph > > Network Administrator :: The Leather Collection, Inc. > > > > From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:52:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9qTt13374 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:52:29 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9qSV13370 for ; Thu, 12 Jul 2001 02:52:28 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6C9qOe10358; Thu, 12 Jul 2001 11:52:24 +0200 Message-Id: <4.3.2.7.2.20010712115143.02b8f008@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 11:52:13 +0200 To: Adam Cioccarelli , From: Seth Mos Subject: Re: [OT] XFS and FreeBSD? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:29 12-7-2001 +0200, Adam Cioccarelli wrote: >Hi, > >I think you'll find that in the mailing list archives... Actually I was >wondering, while we are off topic, why SGI didn't try and port Irix to >intel architecture? Or will it get ported to IA64? Irix will not be ported to IA64 AFAIK. Linux will need to do the job. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 02:56:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6C9uRJ13562 for linux-xfs-outgoing; Thu, 12 Jul 2001 02:56:27 -0700 Received: from sunny.fishnet.com (sunny.fishnet.com [209.150.200.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6C9uPV13558 for ; Thu, 12 Jul 2001 02:56:25 -0700 Received: from awm-laptop (209.150.207.51) by sunny.fishnet.com (5.0.048) id 3B49D9C400032CEF for linux-xfs@oss.sgi.com; Thu, 12 Jul 2001 04:56:21 -0500 Content-Type: text/plain; charset="iso-8859-1" From: "Anthony W. Marino" Organization: AWMObjects To: linux-xfs@oss.sgi.com Subject: Download RPMs Date: Thu, 12 Jul 2001 04:55:34 -0500 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01071204553400.01042@awm-laptop> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The rpm link for RH7.1 doesn't work. Anthony From owner-linux-xfs@oss.sgi.com Thu Jul 12 03:25:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CAPwK14170 for linux-xfs-outgoing; Thu, 12 Jul 2001 03:25:58 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CAPuV14166 for ; Thu, 12 Jul 2001 03:25:56 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6CAPpe10546; Thu, 12 Jul 2001 12:25:52 +0200 Message-Id: <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 12:25:41 +0200 To: "Anthony W. Marino" , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Download RPMs In-Reply-To: <01071204553400.01042@awm-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 04:55 12-7-2001 -0500, Anthony W. Marino wrote: >The rpm link for RH7.1 doesn't work. >Anthony What link on which page? Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 04:02:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CB23d15035 for linux-xfs-outgoing; Thu, 12 Jul 2001 04:02:03 -0700 Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CB21V14998 for ; Thu, 12 Jul 2001 04:02:01 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 15KeEG-0009vV-0K for linux-xfs@oss.sgi.com; Thu, 12 Jul 2001 11:01:58 +0000 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 9E26427EF for ; Thu, 12 Jul 2001 09:46:26 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id D1DF2125E6; Thu, 12 Jul 2001 09:46:25 +0100 (BST) Date: Thu, 12 Jul 2001 09:46:25 +0100 (BST) From: Keith Matthews Subject: Re[2]: XFS for Linux 1.0.1 Released To: linux-xfs@oss.sgi.com In-Reply-To: <20010711142750.A26861@ii.uib.no> References: <200107102103.f6AL3am18531@jen.americas.sgi.com> <20010711105428.A21601@ii.uib.no> <3B4C1D17.6FB2C582@ch.sauter-bc.com>, <20010711142750.A26861@ii.uib.no> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010712084625.D1DF2125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f6CB22V15017 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 11 Jul 2001 14:27:50 +0200 Jan-Frode Myklebust > wrote: > > > > Hm, your lilo.conf should look like this :-) > > image=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp > Of course it had to be a stupid mistake like that > when I finally tried to get help.. Thanks, and > thanks for the monitor-scripts. This is probably not relevant to the 1.0.1 release which I have not yet had a chance to examine, but I found a small problem in the 1.0 isos that I do not remember being mentioned before. The top-level Makefile for the kernel has a line export INSTALL_PATH=/boot which is commented out (so the new kernel goes in / ). Lilo is still expecting the kernel to be in /boot (which is where the issue kernel is installed of course). Hence rebuilding the kernel and running lilo effectively does nothing! -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Thu Jul 12 04:17:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CBHHx15611 for linux-xfs-outgoing; Thu, 12 Jul 2001 04:17:17 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CBHFV15607 for ; Thu, 12 Jul 2001 04:17:15 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6CBHCe10871; Thu, 12 Jul 2001 13:17:12 +0200 Message-Id: <4.3.2.7.2.20010712131605.02c8ae38@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 13:16:51 +0200 To: "Anthony W. Marino" , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Download RPMs In-Reply-To: <01071206014402.01097@awm-laptop> References: <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 06:01 12-7-2001 -0500, Anthony W. Marino wrote: >http://oss.sgi.com/projects/xfs/1.0_rpm.html >There are several download options on this page. > >Thank you, >Anthony The link should be pointing here. ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/kernel_rpms/ I will update the link. >On Thursday 12 July 2001 05:25, Seth Mos wrote: > > At 04:55 12-7-2001 -0500, Anthony W. Marino wrote: > > >The rpm link for RH7.1 doesn't work. > > >Anthony > > > > What link on which page? > > > > Cheers > > > > > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 05:06:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CC6OS16901 for linux-xfs-outgoing; Thu, 12 Jul 2001 05:06:24 -0700 Received: from sunny.fishnet.com (sunny.fishnet.com [209.150.200.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CC6NV16897 for ; Thu, 12 Jul 2001 05:06:23 -0700 Received: from awm-laptop (209.150.207.51) by sunny.fishnet.com (5.0.048) id 3B49D9C400033114; Thu, 12 Jul 2001 06:02:31 -0500 Content-Type: text/plain; charset="iso-8859-1" From: "Anthony W. Marino" Organization: AWMObjects To: Seth Mos , linux-xfs@oss.sgi.com Subject: Re: Download RPMs Date: Thu, 12 Jul 2001 06:01:44 -0500 X-Mailer: KMail [version 1.2] References: <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> MIME-Version: 1.0 Message-Id: <01071206014402.01097@awm-laptop> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk http://oss.sgi.com/projects/xfs/1.0_rpm.html There are several download options on this page. Thank you, Anthony On Thursday 12 July 2001 05:25, Seth Mos wrote: > At 04:55 12-7-2001 -0500, Anthony W. Marino wrote: > >The rpm link for RH7.1 doesn't work. > >Anthony > > What link on which page? > > Cheers > > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 05:27:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CCRe717399 for linux-xfs-outgoing; Thu, 12 Jul 2001 05:27:40 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CCRcV17395 for ; Thu, 12 Jul 2001 05:27:38 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6CCRYe11276; Thu, 12 Jul 2001 14:27:34 +0200 Message-Id: <4.3.2.7.2.20010712142656.02bd7488@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 14:27:14 +0200 To: "Anthony W. Marino" , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Download RPMs In-Reply-To: <01071206014402.01097@awm-laptop> References: <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 06:01 12-7-2001 -0500, Anthony W. Marino wrote: >http://oss.sgi.com/projects/xfs/1.0_rpm.html >There are several download options on this page. The page is updated, they work now. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 06:19:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CDJ0p18752 for linux-xfs-outgoing; Thu, 12 Jul 2001 06:19:00 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CDIvV18746 for ; Thu, 12 Jul 2001 06:18:57 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6CDHte11865; Thu, 12 Jul 2001 15:17:55 +0200 Message-Id: <4.3.2.7.2.20010712151636.0357c050@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 15:17:35 +0200 To: "Anthony W. Marino" , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Download RPMs In-Reply-To: <01071208034101.01103@awm-laptop> References: <4.3.2.7.2.20010712142656.02bd7488@pop.xs4all.nl> <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> <4.3.2.7.2.20010712142656.02bd7488@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 08:03 12-7-2001 -0500, Anthony W. Marino wrote: >Thanks for fixing the link. Where's the kernel 2.4.6 stuff? There is no "1.0.1" for 2.4.6 yet although there is something in the pipeline. There are patches on the FTP site which can be used but are less tested. >Thank you very much, >Anthony > >On Thursday 12 July 2001 07:27, Seth Mos wrote: > > At 06:01 12-7-2001 -0500, Anthony W. Marino wrote: > > >http://oss.sgi.com/projects/xfs/1.0_rpm.html > > >There are several download options on this page. > > > > The page is updated, they work now. > > > > Cheers > > > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 06:22:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CDM9T18915 for linux-xfs-outgoing; Thu, 12 Jul 2001 06:22:09 -0700 Received: from merlin.giref.ulaval.ca (postfix@merlin.giref.ulaval.ca [132.203.7.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CDM8V18911 for ; Thu, 12 Jul 2001 06:22:08 -0700 Received: from giref.ulaval.ca (roederer.giref.ulaval.ca [132.203.7.24]) by merlin.giref.ulaval.ca (Postfix) with ESMTP id 98CD1F496 for ; Thu, 12 Jul 2001 09:22:07 -0400 (EDT) Message-ID: <3B4DA431.FB26BA96@giref.ulaval.ca> Date: Thu, 12 Jul 2001 09:20:49 -0400 From: Luc Lalonde X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: System locking: kernel-2.4.6pre3-xfs Content-Type: multipart/mixed; boundary="------------CB99C708E3D86F114834EA6E" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------CB99C708E3D86F114834EA6E Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Folks, I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS kernels. Every 10 days or so the systems locks and I have to reboot. I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and egcs-1.1.2 with the same results. I've been folllowing the XFS kernel development and have been trying updating since 2.4.2-XFS. I'm wondering at this point if it's not a hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx drivers? How can I find out if this is the problem? There doesn't seem to be any indication of the source of the problem in the log files. Cheers. -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: llalonde@giref.ulaval.ca --------------CB99C708E3D86F114834EA6E Content-Type: text/x-vcard; charset=us-ascii; name="llalonde.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Luc Lalonde Content-Disposition: attachment; filename="llalonde.vcf" begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;;;;;; version:2.1 email;internet:llalonde@giref.ulaval.ca title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard --------------CB99C708E3D86F114834EA6E-- From owner-linux-xfs@oss.sgi.com Thu Jul 12 06:38:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CDcQG19293 for linux-xfs-outgoing; Thu, 12 Jul 2001 06:38:26 -0700 Received: from sunny.fishnet.com (sunny.fishnet.com [209.150.200.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CDcOV19289 for ; Thu, 12 Jul 2001 06:38:24 -0700 Received: from awm-laptop (209.150.207.51) by sunny.fishnet.com (5.0.048) id 3B49D9C400033F9C; Thu, 12 Jul 2001 08:04:28 -0500 Content-Type: text/plain; charset="iso-8859-1" From: "Anthony W. Marino" Organization: AWMObjects To: Seth Mos , linux-xfs@oss.sgi.com Subject: Re: Download RPMs Date: Thu, 12 Jul 2001 08:03:41 -0500 X-Mailer: KMail [version 1.2] References: <4.3.2.7.2.20010712122523.03f37368@pop.xs4all.nl> <4.3.2.7.2.20010712142656.02bd7488@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20010712142656.02bd7488@pop.xs4all.nl> MIME-Version: 1.0 Message-Id: <01071208034101.01103@awm-laptop> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks for fixing the link. Where's the kernel 2.4.6 stuff? Thank you very much, Anthony On Thursday 12 July 2001 07:27, Seth Mos wrote: > At 06:01 12-7-2001 -0500, Anthony W. Marino wrote: > >http://oss.sgi.com/projects/xfs/1.0_rpm.html > >There are several download options on this page. > > The page is updated, they work now. > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 06:43:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CDhJQ19487 for linux-xfs-outgoing; Thu, 12 Jul 2001 06:43:19 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CDhHV19483 for ; Thu, 12 Jul 2001 06:43:17 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6CDh8e12098; Thu, 12 Jul 2001 15:43:11 +0200 Message-Id: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 15:42:48 +0200 To: Luc Lalonde , "linux-xfs@oss.sgi.com" From: Seth Mos Subject: Re: System locking: kernel-2.4.6pre3-xfs In-Reply-To: <3B4DA431.FB26BA96@giref.ulaval.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 09:20 12-7-2001 -0400, Luc Lalonde wrote: >Hello Folks, > >I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS >kernels. Every 10 days or so the systems locks and I have to reboot. >I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and >egcs-1.1.2 with the same results. > >I've been folllowing the XFS kernel development and have been trying >updating since 2.4.2-XFS. I'm wondering at this point if it's not a >hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx >drivers? How can I find out if this is the problem? There doesn't >seem to be any indication of the source of the problem in the log files. no errors or such in dmesg after a week? Have you tried the 1.0.1 rpms yet? That's weird, are you using a raid controller in this box or software raid? Bye -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 06:44:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CDi5W19593 for linux-xfs-outgoing; Thu, 12 Jul 2001 06:44:05 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CDi3V19589 for ; Thu, 12 Jul 2001 06:44:04 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id PAA23738; Thu, 12 Jul 2001 15:44:02 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id PAA14014; Thu, 12 Jul 2001 15:44:01 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 696DB57306; Thu, 12 Jul 2001 15:53:50 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id BD94E25835; Thu, 12 Jul 2001 16:01:47 +0200 (CEST) Message-ID: <3B4DA9C4.35AC5AF5@ch.sauter-bc.com> Date: Thu, 12 Jul 2001 15:44:36 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Luc Lalonde Cc: "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <3B4DA431.FB26BA96@giref.ulaval.ca> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Luc Lalonde schrieb: > > Hello Folks, > > I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > kernels. Every 10 days or so the systems locks and I have to reboot. > I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and > egcs-1.1.2 with the same results. How is your Server configured? Do you have aacraid or any other hardware Raid from DELL or do you have the disks connected to an onboard SCSI or$ additional SCSI controller? I have tried different Raid controllers and was not happy with them. SoftRAID5 on directly connected disks was my solution. Simon > > I've been folllowing the XFS kernel development and have been trying > updating since 2.4.2-XFS. I'm wondering at this point if it's not a > hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx > drivers? How can I find out if this is the problem? There doesn't > seem to be any indication of the source of the problem in the log files. > > Cheers. > > -- > Luc Lalonde, Responsable du reseau GIREF > > Telephone: (418) 656-2131 poste 6623 > Courriel: llalonde@giref.ulaval.ca -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 12 07:14:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CEEMB20450 for linux-xfs-outgoing; Thu, 12 Jul 2001 07:14:22 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CEEHV20446 for ; Thu, 12 Jul 2001 07:14:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA103474 for ; Thu, 12 Jul 2001 16:14:14 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2409724; Thu, 12 Jul 2001 09:12:57 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA08454; Thu, 12 Jul 2001 09:12:57 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6CEEwt03725; Thu, 12 Jul 2001 09:14:58 -0500 Message-Id: <200107121414.f6CEEwt03725@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: [OT] XFS and FreeBSD? In-Reply-To: Message from Federico Sevilla III of "Thu, 12 Jul 2001 17:21:15 +0800." Date: Thu, 12 Jul 2001 09:14:57 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi everyone, > > I hope this does not cause any major trouble. I am wondering if there is > any effort to get XFS working on FreeBSD complete with EAs and ACLs. I do > not know what the state of the filesystem support of FreeBSD is, but the > last I've read looks like it's still UFS with soft updates. I also > personally wonder why SGI decided to port XFS to Linux and not to the > BSDs. I have never used any BSD (I use Linux actually) but this just makes > me curious. I've heard the BSDs are also very good, but maybe someone can > enlighten me off-list about this. > > Thanks in advance everyone! XFS was ported to Linux because SGI has Linux platforms, we do not have BSD based platforms. Given the amount of effort to get the XFS code GPLed, we have no plans for any other licensing (unless someone pays us ;-). Now if someone wants to port XFS to BSD under the current license they are free to do so from SGI's point of view, it is only BSD licensing issues which prevent this from happening. You have to remember (and so do we occasionally) that SGI is a commercial company, it is supposed to make money (emphasis on the supposed to), so there really has to be some commercial reason for us doing things. Steve > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 12 07:16:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CEG2L20583 for linux-xfs-outgoing; Thu, 12 Jul 2001 07:16:02 -0700 Received: from merlin.giref.ulaval.ca (postfix@merlin.giref.ulaval.ca [132.203.7.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CEG0V20579 for ; Thu, 12 Jul 2001 07:16:01 -0700 Received: from giref.ulaval.ca (roederer.giref.ulaval.ca [132.203.7.24]) by merlin.giref.ulaval.ca (Postfix) with ESMTP id 4BFA41E03A for ; Thu, 12 Jul 2001 10:16:00 -0400 (EDT) Message-ID: <3B4DB0D1.FE016E3C@giref.ulaval.ca> Date: Thu, 12 Jul 2001 10:14:42 -0400 From: Luc Lalonde X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> Content-Type: multipart/mixed; boundary="------------AE19B04E9CC2F18647261DCC" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------AE19B04E9CC2F18647261DCC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Seth and Simon, I figured I'd answer both of you at the same time. First off, I do get some strange errors of this type: fh_verify: mail/:saved permission failure, acc=1, error=13 svc: unknown program 100227 (me 100003) However, when I searched on Google this was an NFS message that was harmless and could be ignored (is this right?). I looked this morning and I see this message (dmesg): st0: Block limits 1 - 16777215 bytes The crash always happens when the Amanda system is writting to tape. Could this be a hardware problem clue? I haven't tried the 1.01 RPMS yet. I'm on a SuSE7.1 system here so I compile my own kernels. I'm not using any kind of RAID on this system. It's got four SCSI disks connected to the onboard(Adaptec) SCSI controler and a tape (HP-DAT40) connected to an Adaptec-30160 controller. Thanks for your help. Seth Mos wrote: > At 09:20 12-7-2001 -0400, Luc Lalonde wrote: > >Hello Folks, > > > >I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > >kernels. Every 10 days or so the systems locks and I have to reboot. > >I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and > >egcs-1.1.2 with the same results. > > > >I've been folllowing the XFS kernel development and have been trying > >updating since 2.4.2-XFS. I'm wondering at this point if it's not a > >hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx > >drivers? How can I find out if this is the problem? There doesn't > >seem to be any indication of the source of the problem in the log files. > > no errors or such in dmesg after a week? > Have you tried the 1.0.1 rpms yet? > > That's weird, are you using a raid controller in this box or software raid? > > Bye > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: llalonde@giref.ulaval.ca --------------AE19B04E9CC2F18647261DCC Content-Type: text/x-vcard; charset=us-ascii; name="llalonde.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Luc Lalonde Content-Disposition: attachment; filename="llalonde.vcf" begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;;;;;; version:2.1 email;internet:llalonde@giref.ulaval.ca title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard --------------AE19B04E9CC2F18647261DCC-- From owner-linux-xfs@oss.sgi.com Thu Jul 12 07:35:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CEZhA21183 for linux-xfs-outgoing; Thu, 12 Jul 2001 07:35:43 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CEZfV21179 for ; Thu, 12 Jul 2001 07:35:41 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6CEZce12316; Thu, 12 Jul 2001 16:35:38 +0200 Message-Id: <4.3.2.7.2.20010712163042.0357d390@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 16:35:18 +0200 To: Luc Lalonde , "linux-xfs@oss.sgi.com" From: Seth Mos Subject: Re: System locking: kernel-2.4.6pre3-xfs In-Reply-To: <3B4DB0D1.FE016E3C@giref.ulaval.ca> References: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 10:14 12-7-2001 -0400, Luc Lalonde wrote: >Hello Seth and Simon, > >I figured I'd answer both of you at the same time. > >First off, I do get some strange errors of this type: > >fh_verify: mail/:saved permission failure, acc=1, error=13 >svc: unknown program 100227 (me 100003) > >However, when I searched on Google this was an NFS message that was harmless >and could be ignored (is this right?). Can't comment on this. >I looked this morning and I see this message (dmesg): > >st0: Block limits 1 - 16777215 bytes This equates to 15GB... rotten tape or drive going mad. It should read 20GB if I am correct. If I use 1GB = 1000MB it comes at 16GB which is still 4GB short. >The crash always happens when the Amanda system is writting to tape. Could >this be a hardware problem clue? possibly yes. >I haven't tried the 1.01 RPMS yet. I'm on a SuSE7.1 system here so I compile >my own kernels. Patches are available for building your own kernel the patches can be found at http://oss.sgi.com/projects/xfs/1.0_rpm.html >I'm not using any kind of RAID on this system. It's got four SCSI disks >connected to the onboard(Adaptec) SCSI controler and a tape (HP-DAT40) >connected to an Adaptec-30160 controller. That tape drive should work, you have 20GB uncompressed and 40GB compressed. We got tape full errors at about 30GB of data. Good luck -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 07:47:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CEl5221512 for linux-xfs-outgoing; Thu, 12 Jul 2001 07:47:05 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CEl1V21508 for ; Thu, 12 Jul 2001 07:47:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id QAA15669; Thu, 12 Jul 2001 16:46:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id QAA19228; Thu, 12 Jul 2001 16:46:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 2FFA057306; Thu, 12 Jul 2001 16:57:04 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id CFA7825835; Thu, 12 Jul 2001 17:05:02 +0200 (CEST) Message-ID: <3B4DB897.B910BC7F@ch.sauter-bc.com> Date: Thu, 12 Jul 2001 16:47:51 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Luc Lalonde Cc: "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> <3B4DB0D1.FE016E3C@giref.ulaval.ca> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Luc Lalonde schrieb: > > Hello Seth and Simon, > > I figured I'd answer both of you at the same time. > > First off, I do get some strange errors of this type: > > fh_verify: mail/:saved permission failure, acc=1, error=13 > svc: unknown program 100227 (me 100003) > > However, when I searched on Google this was an NFS message that was harmless > and could be ignored (is this right?). I get similar messages on a Mandrake 7.0 server where HP-UX and Solaris clients are connected. It just means someone tried to access NFS files with not having appropriate permissions. I think this has nothing to do with your crashes. > > I looked this morning and I see this message (dmesg): > > st0: Block limits 1 - 16777215 bytes I remember to have the same on my home system which has a Sony DAT drive connected. I don't see this here at work since DLT seem to be different. I guess the st kernel module just tells you what the valid blocksizes are for your DAT drive. > > The crash always happens when the Amanda system is writting to tape. Could > this be a hardware problem clue? What happens if you access the tape by creating a tar archive on it. Does it also crash? > > I haven't tried the 1.01 RPMS yet. I'm on a SuSE7.1 system here so I compile > my own kernels. Hmm, I don't know how SuSE handles tape drives. In redhat the st module gets loaded at bootup when a tape device is detected. I know that sometimes one can get problems when you try to load the st module on demand by kmod. I strongly suggest to make sure the st module is not loaded as autoclean. > > I'm not using any kind of RAID on this system. It's got four SCSI disks > connected to the onboard(Adaptec) SCSI controler and a tape (HP-DAT40) > connected to an Adaptec-30160 controller. Well, I love Adaptec like other companies like Microsoft, Intel... The cheap Symbios Logic SCSI have much less problems with Linux. > > Thanks for your help. > > Seth Mos wrote: > > > At 09:20 12-7-2001 -0400, Luc Lalonde wrote: > > >Hello Folks, > > > > > >I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > > >kernels. Every 10 days or so the systems locks and I have to reboot. > > >I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and > > >egcs-1.1.2 with the same results. > > > > > >I've been folllowing the XFS kernel development and have been trying > > >updating since 2.4.2-XFS. I'm wondering at this point if it's not a > > >hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx > > >drivers? How can I find out if this is the problem? There doesn't > > >seem to be any indication of the source of the problem in the log files. > > > > no errors or such in dmesg after a week? > > Have you tried the 1.0.1 rpms yet? > > > > That's weird, are you using a raid controller in this box or software raid? > > > > Bye > > > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. > > -- > Luc Lalonde, Responsable du reseau GIREF > > Telephone: (418) 656-2131 poste 6623 > Courriel: llalonde@giref.ulaval.ca -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 12 07:51:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CEpTK21688 for linux-xfs-outgoing; Thu, 12 Jul 2001 07:51:29 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CEpIV21679 for ; Thu, 12 Jul 2001 07:51:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA03047 for ; Thu, 12 Jul 2001 07:51:04 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2411850; Thu, 12 Jul 2001 09:49:47 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA18956; Thu, 12 Jul 2001 09:49:46 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6CEplS09516; Thu, 12 Jul 2001 09:51:47 -0500 Message-Id: <200107121451.f6CEplS09516@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Brent A Nelson cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump/xfsrestore problem in the 1.0.1 release In-Reply-To: Message from Brent A Nelson of "Wed, 11 Jul 2001 21:59:13 EDT." Date: Thu, 12 Jul 2001 09:51:46 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Under release 1.0.1, I noticed a problem with xfsdump/xfsrestore that > wasn't there in 1.0 (although it did fix an OOPS, and the earlier SUID > problem). Doing an xfsdump of / piped to a restore on another partition, > I noticed that the /dev directory didn't transfer correctly. The major > numbers on all the devices were set to 0. > > It seems that I must have read about this problem being fixed before, so > I'm guessing the CVS version of xfsdump doesn't have this problem? Yes, there is a problem here, I just replicated it locally on the current cvs kernel and xfsdump/restore packages. A mknod on its own creates the correct information, so this is either dump not getting the correct info out of the kernel, or an issue between dump and restore themselves. Steve > > Thanks, > > Brent Nelson > Director of Computing > Dept. of Physics > University of Florida From owner-linux-xfs@oss.sgi.com Thu Jul 12 07:57:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CEvcH21917 for linux-xfs-outgoing; Thu, 12 Jul 2001 07:57:38 -0700 Received: from femail1.rdc1.on.home.com (femail1.rdc1.on.home.com [24.2.9.88]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CEvbV21913 for ; Thu, 12 Jul 2001 07:57:37 -0700 Received: from cr598116-a.wlfdle1.on.wave.home.com ([24.112.74.120]) by femail1.rdc1.on.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010712145731.ZEIC20411.femail1.rdc1.on.home.com@cr598116-a.wlfdle1.on.wave.home.com> for ; Thu, 12 Jul 2001 07:57:31 -0700 From: Gerald Henriksen To: linux-xfs@oss.sgi.com Subject: Re: [OT] XFS and FreeBSD? Date: Thu, 12 Jul 2001 10:59:00 -0400 Message-ID: References: <994931235.30682.6.camel@syntax.dera.gov.uk> In-Reply-To: <994931235.30682.6.camel@syntax.dera.gov.uk> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6CEvbV21914 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 12 Jul 2001 10:47:15 +0100, you wrote: >I reckon Irix will be dropped when SGI move to the IA64 platform. They'd >be fools not to. SGI are not dropping MIPS/Irix. SGI is adding IA64/Linux to their product mix so that customers will have a choice of either MIPS or IA64 solutions. From owner-linux-xfs@oss.sgi.com Thu Jul 12 08:05:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CF5IZ22221 for linux-xfs-outgoing; Thu, 12 Jul 2001 08:05:18 -0700 Received: from femail1.rdc1.on.home.com (femail1.rdc1.on.home.com [24.2.9.88]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CF5GV22217 for ; Thu, 12 Jul 2001 08:05:16 -0700 Received: from cr598116-a.wlfdle1.on.wave.home.com ([24.112.74.120]) by femail1.rdc1.on.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with SMTP id <20010712150510.ZJEM20411.femail1.rdc1.on.home.com@cr598116-a.wlfdle1.on.wave.home.com> for ; Thu, 12 Jul 2001 08:05:10 -0700 From: Gerald Henriksen To: linux-xfs@oss.sgi.com Subject: Re: [OT] XFS and FreeBSD? Date: Thu, 12 Jul 2001 11:06:39 -0400 Message-ID: References: In-Reply-To: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6CF5GV22218 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001 11:29:17 +0200 (CEST), you wrote: >wondering, while we are off topic, why SGI didn't try and port Irix to >intel architecture? Or will it get ported to IA64? Irix will remain as MIPS only. My understanding is that it was decided it would take too much work to port Irix to a non-MIPS processor. Instead SGI decided to help in improving Linux in areas SGI felt were necessary for the Linux offerings by SGI. From owner-linux-xfs@oss.sgi.com Thu Jul 12 08:31:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CFVk522952 for linux-xfs-outgoing; Thu, 12 Jul 2001 08:31:46 -0700 Received: from merlin.giref.ulaval.ca (postfix@merlin.giref.ulaval.ca [132.203.7.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CFVhV22948 for ; Thu, 12 Jul 2001 08:31:43 -0700 Received: from giref.ulaval.ca (roederer.giref.ulaval.ca [132.203.7.24]) by merlin.giref.ulaval.ca (Postfix) with ESMTP id 3C9421E06E; Thu, 12 Jul 2001 11:31:42 -0400 (EDT) Message-ID: <3B4DC28F.FFF71727@giref.ulaval.ca> Date: Thu, 12 Jul 2001 11:30:23 -0400 From: Luc Lalonde X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Simon Matter Cc: "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> <3B4DB0D1.FE016E3C@giref.ulaval.ca> <3B4DB897.B910BC7F@ch.sauter-bc.com> Content-Type: multipart/mixed; boundary="------------7CEF505CB3D50404616FB316" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------7CEF505CB3D50404616FB316 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello Simon, I'm backing up every night to this tape drive. The system doesn't crash everytime I use the Tape drive...only every 10 days or so. I've got the AIC7XXX module loaded at boot time with INITRD. So I don't think that this is an autoclean problem. Cheers, Luc. Simon Matter wrote: > Luc Lalonde schrieb: > > > > Hello Seth and Simon, > > > > I figured I'd answer both of you at the same time. > > > > First off, I do get some strange errors of this type: > > > > fh_verify: mail/:saved permission failure, acc=1, error=13 > > svc: unknown program 100227 (me 100003) > > > > However, when I searched on Google this was an NFS message that was harmless > > and could be ignored (is this right?). > > I get similar messages on a Mandrake 7.0 server where HP-UX and Solaris > clients are connected. It just means someone tried to access NFS files > with not having appropriate permissions. I think this has nothing to do > with your crashes. > > > > > I looked this morning and I see this message (dmesg): > > > > st0: Block limits 1 - 16777215 bytes > > I remember to have the same on my home system which has a Sony DAT drive > connected. I don't see this here at work since DLT seem to be different. > I guess the st kernel module just tells you what the valid blocksizes > are for your DAT drive. > > > > The crash always happens when the Amanda system is writting to tape. Could > > this be a hardware problem clue? > > What happens if you access the tape by creating a tar archive on it. > Does > it also crash? > > > > > I haven't tried the 1.01 RPMS yet. I'm on a SuSE7.1 system here so I compile > > my own kernels. > > Hmm, I don't know how SuSE handles tape drives. In redhat the st module > gets > loaded at bootup when a tape device is detected. I know that sometimes > one can get problems when you try to load the st module on demand by > kmod. > I strongly suggest to make sure the st module is not loaded as > autoclean. > > > > > I'm not using any kind of RAID on this system. It's got four SCSI disks > > connected to the onboard(Adaptec) SCSI controler and a tape (HP-DAT40) > > connected to an Adaptec-30160 controller. > > Well, I love Adaptec like other companies like Microsoft, Intel... The > cheap > Symbios Logic SCSI have much less problems with Linux. > > > > > Thanks for your help. > > > > Seth Mos wrote: > > > > > At 09:20 12-7-2001 -0400, Luc Lalonde wrote: > > > >Hello Folks, > > > > > > > >I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > > > >kernels. Every 10 days or so the systems locks and I have to reboot. > > > >I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and > > > >egcs-1.1.2 with the same results. > > > > > > > >I've been folllowing the XFS kernel development and have been trying > > > >updating since 2.4.2-XFS. I'm wondering at this point if it's not a > > > >hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx > > > >drivers? How can I find out if this is the problem? There doesn't > > > >seem to be any indication of the source of the problem in the log files. > > > > > > no errors or such in dmesg after a week? > > > Have you tried the 1.0.1 rpms yet? > > > > > > That's weird, are you using a raid controller in this box or software raid? > > > > > > Bye > > > > > > -- > > > Seth > > > Every program has two purposes one for which > > > it was written and another for which it wasn't > > > I use the last kind. > > > > -- > > Luc Lalonde, Responsable du reseau GIREF > > > > Telephone: (418) 656-2131 poste 6623 > > Courriel: llalonde@giref.ulaval.ca > > -- > Simon Matter Tel: +41 61 695 57 35 > Fr.Sauter AG / CIT Fax: +41 61 695 53 30 > Im Surinam 55 > CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: llalonde@giref.ulaval.ca --------------7CEF505CB3D50404616FB316 Content-Type: text/x-vcard; charset=us-ascii; name="llalonde.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Luc Lalonde Content-Disposition: attachment; filename="llalonde.vcf" begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;;;;;; version:2.1 email;internet:llalonde@giref.ulaval.ca title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard --------------7CEF505CB3D50404616FB316-- From owner-linux-xfs@oss.sgi.com Thu Jul 12 08:36:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CFa2223100 for linux-xfs-outgoing; Thu, 12 Jul 2001 08:36:02 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CFZwV23096 for ; Thu, 12 Jul 2001 08:35:58 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id RAA23116; Thu, 12 Jul 2001 17:35:56 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id RAA23319; Thu, 12 Jul 2001 17:35:56 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 8834357306; Thu, 12 Jul 2001 17:45:57 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 33E6825835; Thu, 12 Jul 2001 17:53:56 +0200 (CEST) Message-ID: <3B4DC40C.B1D25CEA@ch.sauter-bc.com> Date: Thu, 12 Jul 2001 17:36:44 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Luc Lalonde Cc: "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> <3B4DB0D1.FE016E3C@giref.ulaval.ca> <3B4DB897.B910BC7F@ch.sauter-bc.com> <3B4DC28F.FFF71727@giref.ulaval.ca> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Luc Lalonde schrieb: > > Hello Simon, > > I'm backing up every night to this tape drive. The system doesn't crash > everytime I use the Tape drive...only every 10 days or so. > > I've got the AIC7XXX module loaded at boot time with INITRD. So I don't think > that this is an autoclean problem. The critical point is the st module, or is tape support compiled into the kernel? -Simon > > Cheers, Luc. > > Simon Matter wrote: > > > Luc Lalonde schrieb: > > > > > > Hello Seth and Simon, > > > > > > I figured I'd answer both of you at the same time. > > > > > > First off, I do get some strange errors of this type: > > > > > > fh_verify: mail/:saved permission failure, acc=1, error=13 > > > svc: unknown program 100227 (me 100003) > > > > > > However, when I searched on Google this was an NFS message that was harmless > > > and could be ignored (is this right?). > > > > I get similar messages on a Mandrake 7.0 server where HP-UX and Solaris > > clients are connected. It just means someone tried to access NFS files > > with not having appropriate permissions. I think this has nothing to do > > with your crashes. > > > > > > > > I looked this morning and I see this message (dmesg): > > > > > > st0: Block limits 1 - 16777215 bytes > > > > I remember to have the same on my home system which has a Sony DAT drive > > connected. I don't see this here at work since DLT seem to be different. > > I guess the st kernel module just tells you what the valid blocksizes > > are for your DAT drive. > > > > > > The crash always happens when the Amanda system is writting to tape. Could > > > this be a hardware problem clue? > > > > What happens if you access the tape by creating a tar archive on it. > > Does > > it also crash? > > > > > > > > I haven't tried the 1.01 RPMS yet. I'm on a SuSE7.1 system here so I compile > > > my own kernels. > > > > Hmm, I don't know how SuSE handles tape drives. In redhat the st module > > gets > > loaded at bootup when a tape device is detected. I know that sometimes > > one can get problems when you try to load the st module on demand by > > kmod. > > I strongly suggest to make sure the st module is not loaded as > > autoclean. > > > > > > > > I'm not using any kind of RAID on this system. It's got four SCSI disks > > > connected to the onboard(Adaptec) SCSI controler and a tape (HP-DAT40) > > > connected to an Adaptec-30160 controller. > > > > Well, I love Adaptec like other companies like Microsoft, Intel... The > > cheap > > Symbios Logic SCSI have much less problems with Linux. > > > > > > > > Thanks for your help. > > > > > > Seth Mos wrote: > > > > > > > At 09:20 12-7-2001 -0400, Luc Lalonde wrote: > > > > >Hello Folks, > > > > > > > > > >I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > > > > >kernels. Every 10 days or so the systems locks and I have to reboot. > > > > >I've tried compiling the kernels with gcc-2.95.2, gcc-2.95.3, and > > > > >egcs-1.1.2 with the same results. > > > > > > > > > >I've been folllowing the XFS kernel development and have been trying > > > > >updating since 2.4.2-XFS. I'm wondering at this point if it's not a > > > > >hardware problem. Could it be a problem with the new Adaptec AIC-7xxxx > > > > >drivers? How can I find out if this is the problem? There doesn't > > > > >seem to be any indication of the source of the problem in the log files. > > > > > > > > no errors or such in dmesg after a week? > > > > Have you tried the 1.0.1 rpms yet? > > > > > > > > That's weird, are you using a raid controller in this box or software raid? > > > > > > > > Bye > > > > > > > > -- > > > > Seth > > > > Every program has two purposes one for which > > > > it was written and another for which it wasn't > > > > I use the last kind. > > > > > > -- > > > Luc Lalonde, Responsable du reseau GIREF > > > > > > Telephone: (418) 656-2131 poste 6623 > > > Courriel: llalonde@giref.ulaval.ca > > > > -- > > Simon Matter Tel: +41 61 695 57 35 > > Fr.Sauter AG / CIT Fax: +41 61 695 53 30 > > Im Surinam 55 > > CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] > > -- > Luc Lalonde, Responsable du reseau GIREF > > Telephone: (418) 656-2131 poste 6623 > Courriel: llalonde@giref.ulaval.ca -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 12 09:12:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CGCmf23994 for linux-xfs-outgoing; Thu, 12 Jul 2001 09:12:48 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CGCkV23986 for ; Thu, 12 Jul 2001 09:12:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA113048 for ; Thu, 12 Jul 2001 18:12:42 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2405769; Thu, 12 Jul 2001 11:11:25 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA60882; Thu, 12 Jul 2001 11:11:24 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6CGDPt26134; Thu, 12 Jul 2001 11:13:25 -0500 Message-Id: <200107121613.f6CGDPt26134@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Steve Lord cc: Brent A Nelson , linux-xfs@oss.sgi.com Subject: Re: xfsdump/xfsrestore problem in the 1.0.1 release In-Reply-To: Message from Steve Lord of "Thu, 12 Jul 2001 09:51:46 CDT." <200107121451.f6CEplS09516@jen.americas.sgi.com> Date: Thu, 12 Jul 2001 11:13:25 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Under release 1.0.1, I noticed a problem with xfsdump/xfsrestore that > > wasn't there in 1.0 (although it did fix an OOPS, and the earlier SUID > > problem). Doing an xfsdump of / piped to a restore on another partition, > > I noticed that the /dev directory didn't transfer correctly. The major > > numbers on all the devices were set to 0. > > > > It seems that I must have read about this problem being fixed before, so > > I'm guessing the CVS version of xfsdump doesn't have this problem? > > Yes, there is a problem here, I just replicated it locally on the current > cvs kernel and xfsdump/restore packages. A mknod on its own creates the > correct information, so this is either dump not getting the correct info > out of the kernel, or an issue between dump and restore themselves. Hmm, I am pretty sure this would never have worked, the code to mknod the device in the restore program has always taken the unconverted device number from the archive and passed it to the kernel. Since this is a 32 bit value in Irix format the major number gets dropped by the kernel. I have a working version here now and just need to work out how to package it - since the xfsprog rpm where the source code should really reside for this just went through a major version change. I can certainly fix the cvs version though. Steve From owner-linux-xfs@oss.sgi.com Thu Jul 12 09:16:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CGG1H24174 for linux-xfs-outgoing; Thu, 12 Jul 2001 09:16:01 -0700 Received: from neptune.phys.ufl.edu (neptune-gw.phys.ufl.edu [128.227.64.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CGFxV24169 for ; Thu, 12 Jul 2001 09:15:59 -0700 Received: from bani.phys.ufl.edu (IDENT:root@bani.phys.ufl.edu [128.227.89.14]) by neptune.phys.ufl.edu (8.9.3/8.9.3) with ESMTP id MAA06015 for ; Thu, 12 Jul 2001 12:15:58 -0400 (EDT) Received: from localhost (brent@localhost) by bani.phys.ufl.edu (8.11.2/8.8.8) with ESMTP id f6CGFwG22963 for ; Thu, 12 Jul 2001 12:15:58 -0400 X-Authentication-Warning: bani.phys.ufl.edu: brent owned process doing -bs Date: Thu, 12 Jul 2001 12:15:58 -0400 (EDT) From: Brent A Nelson To: Subject: Re: xfsdump/xfsrestore problem in the 1.0.1 release In-Reply-To: <200107121613.f6CGDPt26134@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ah, yes, maybe it didn't work before. Since the old release used devfs, I would never have noticed if /dev on the filesystem was messed up. Thanks, Brent On Thu, 12 Jul 2001, Steve Lord wrote: > > > Under release 1.0.1, I noticed a problem with xfsdump/xfsrestore that > > > wasn't there in 1.0 (although it did fix an OOPS, and the earlier SUID > > > problem). Doing an xfsdump of / piped to a restore on another partition, > > > I noticed that the /dev directory didn't transfer correctly. The major > > > numbers on all the devices were set to 0. > > > > > > It seems that I must have read about this problem being fixed before, so > > > I'm guessing the CVS version of xfsdump doesn't have this problem? > > > > Yes, there is a problem here, I just replicated it locally on the current > > cvs kernel and xfsdump/restore packages. A mknod on its own creates the > > correct information, so this is either dump not getting the correct info > > out of the kernel, or an issue between dump and restore themselves. > > Hmm, I am pretty sure this would never have worked, the code to mknod the > device in the restore program has always taken the unconverted device > number from the archive and passed it to the kernel. Since this is a > 32 bit value in Irix format the major number gets dropped by the kernel. > I have a working version here now and just need to work out how to > package it - since the xfsprog rpm where the source code should really > reside for this just went through a major version change. I can > certainly fix the cvs version though. > > Steve > > > > From owner-linux-xfs@oss.sgi.com Thu Jul 12 09:53:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CGrRO25001 for linux-xfs-outgoing; Thu, 12 Jul 2001 09:53:27 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CGrPV24995 for ; Thu, 12 Jul 2001 09:53:26 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6CGrJNe037780; Thu, 12 Jul 2001 11:53:20 -0500 (CDT) Message-ID: <3B4DD5E2.F0A2B940@thebarn.com> Date: Thu, 12 Jul 2001 11:52:50 -0500 From: cattelan@thebarn.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Federico Sevilla III CC: Linux XFS Mailing List Subject: Re: [OT] XFS and FreeBSD? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Federico Sevilla III wrote: > Hi everyone, > > I hope this does not cause any major trouble. I am wondering if there is > any effort to get XFS working on FreeBSD Yes but it's all part time effort right now. More volunteers welcome. Actually the NT port using the FreeBSD 2.5 vfs/vnode interface is mounting and making directories. > complete with EAs and ACLs. This part will probably be quite a way out. > I do > not know what the state of the filesystem support of FreeBSD is, but the > last I've read looks like it's still UFS with soft updates. I also > personally wonder why SGI decided to port XFS to Linux and not to the > BSDs. I have never used any BSD (I use Linux actually) but this just makes > me curious. I've heard the BSDs are also very good, but maybe someone can > enlighten me off-list about this. > > Thanks in advance everyone! > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 12 10:27:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CHRcm25638 for linux-xfs-outgoing; Thu, 12 Jul 2001 10:27:38 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CHRaV25633 for ; Thu, 12 Jul 2001 10:27:36 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6CHRONe038143; Thu, 12 Jul 2001 12:27:29 -0500 (CDT) Message-ID: <3B4DDDDE.4574DCB@thebarn.com> Date: Thu, 12 Jul 2001 12:26:54 -0500 From: cattelan@thebarn.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos CC: Federico Sevilla III , Linux XFS Mailing List Subject: Re: [OT] XFS and FreeBSD? References: <4.3.2.7.2.20010712113132.02b59f00@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > The biggest concern of most BSD people is that XFS would need to be > licensed under the BSD license, Unfortunately the people at SGI had a hard > enough time to convince them to use the GPL license as it is. I don't think > they will switch licenses because it takes huge efforts to do so. read: huge = any SGI has no business interests in XFS on anything but IRIX and Linux and the also have a business inters test in XFS not ending up on things like Solaris, AIX... etc etc. It's questionable how much protection the GPL provides in preventing competitors from using the technology, but up to this point most vendors are afraid enough of the virus to choose abstinence as the preferred form of protection. So the GPL is a good choice for SGI at this time. > > it would be possible to use the GPL code in BSDs but you would probably > need a fs layer interface to seperate the two. This makes it possible to > use XFS as a GPL piece of code without needing to change the license. But I > might be wrong though, I am not really at home in the BSD side of the world. The BSDs us plenty of GPLed software most notably all the gnu devel tools gcc, gdb etc additionally has some GPLed kernel code e.g. /sys/gnu/ext2fs The trick is make clear lines in the sand as to what commercial ventures using BSD code can an can not ship. It is entirely possible to have a GPLed version of XFS for the Free BSD distributions by make clear dividing lines. Additionally the BSD boot loader is smart enough to load kernel modules prior to booting the kernel which would allow for XFS to only live as independent GPL infected module but still keep the core kernel protected. > > However due to the nature of XFS and it's interactivity with the VM this > would be a huge effort to port to BSD. It would take a lot of time to make > it work. Actually since the BSD vfs/vnode/VM interface is much closer to IRIX it shouldn't be nearly as much work. > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 10:34:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CHYc325851 for linux-xfs-outgoing; Thu, 12 Jul 2001 10:34:38 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CHYZV25847 for ; Thu, 12 Jul 2001 10:34:36 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA118390 for ; Thu, 12 Jul 2001 19:34:33 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2413874 for ; Thu, 12 Jul 2001 12:33:16 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA42187 for ; Thu, 12 Jul 2001 12:33:16 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6CHZGX05490; Thu, 12 Jul 2001 12:35:16 -0500 Message-Id: <200107121735.f6CHZGX05490@jen.americas.sgi.com> Date: Thu, 12 Jul 2001 12:35:16 -0500 Subject: TAKE - fix xfsrestore handling of devices Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Major device numbers were getting dropped on the floor by xfsrestore, this fixes it. I will get a new rpm out on oss soon. The kernel change in this mod is just to make the macros visible in the user space header. Date: Thu Jul 12 10:31:50 PDT 2001 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:98712a linux/fs/xfs/xfs_types.h - 1.52 - export dev_t conversion macros to user space, they are needed by xfsdump and xfsrestore. cmd/xfsdump/common/util.c - 1.3 - convert linux dev_t in stat64 return to irix format used in bulkstat output. cmd/xfsdump/restore/content.c - 1.9 - convert dump tape format dev_t into linux format dev_t before calling mknod. cmd/xfsdump/VERSION - 1.11 - Bump minor version number cmd/xfsdump/doc/CHANGES - 1.12 - Add new version number comment cmd/xfsprogs/include/xfs_types.h - 1.4 - export dev_t conversion macros to user space, they are needed by xfsdump and xfsrestore. cmd/xfsprogs/doc/CHANGES - 1.23 - Add new version number comment cmd/xfsprogs/VERSION - 1.21 - Bump minor version - revised xfs_types.h file From owner-linux-xfs@oss.sgi.com Thu Jul 12 10:43:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CHhsw26115 for linux-xfs-outgoing; Thu, 12 Jul 2001 10:43:54 -0700 Received: from fw.hel.fi.ssh.com (fw.hel.fi.ssh.com [193.64.193.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CHhqV26111 for ; Thu, 12 Jul 2001 10:43:52 -0700 Received: from viikuna.hel.fi.ssh.com (viikuna.hel.fi.ssh.com [10.1.0.46]) by fw.hel.fi.ssh.com (SSH-1.26) with SMTP id f6CHhop06899 for ; Thu, 12 Jul 2001 20:43:51 +0300 (EEST) Received: (qmail 19811 invoked from network); 12 Jul 2001 17:43:50 -0000 Received: from unknown (HELO torni.hel.fi.ssh.com) ([10.1.0.48]) (envelope-sender ) by viikuna.hel.fi.ssh.com (qmail-ldap-1.03) with SMTP for ; 12 Jul 2001 17:43:50 -0000 Date: Thu, 12 Jul 2001 20:43:50 +0300 (EET DST) From: Jarkko Santala X-X-Sender: To: "linux-xfs@oss.sgi.com" Subject: Another case of "getfh failed: Operation not permitted" Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 based system. When I tried to mount an xfs filesystem (which sits on top of lvm) exported from this box with NFS, I get a "Permission denied" on the client side and "rpc.mountd: getfh failed: Operation not permitted" on the server side. Mounting a reiserfs filesystem from the same box works fine. Now, I first had the problem with Linux 2.4.5 + linux-2.4.5-xfs-06112001.patch, so I figured that an upgrade to later versions would probably solve the problems. No such luck. I found some discussion on the subject on the linux-xfs mailing list archives, but no one had posted any reasons or location of patches. If you need debugging or more info on the systems, I'll help. -jake -- Jarkko Santala System Administrator Cell. +358407204512 SSH Communications Security Corp, Helsinki, Finland http://www.ssh.com "If only you had a personality instead of an attitude." From owner-linux-xfs@oss.sgi.com Thu Jul 12 10:51:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CHpAn26299 for linux-xfs-outgoing; Thu, 12 Jul 2001 10:51:10 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CHp8V26295 for ; Thu, 12 Jul 2001 10:51:08 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 7583F1E2A0; Thu, 12 Jul 2001 19:51:02 +0200 (MEST) Date: Thu, 12 Jul 2001 19:50:52 +0200 From: Andi Kleen To: cattelan@thebarn.com Cc: Seth Mos , Federico Sevilla III , Linux XFS Mailing List Subject: Re: [OT] XFS and FreeBSD? Message-ID: <20010712195052.A26122@gruyere.muc.suse.de> References: <4.3.2.7.2.20010712113132.02b59f00@pop.xs4all.nl> <3B4DDDDE.4574DCB@thebarn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B4DDDDE.4574DCB@thebarn.com>; from cattelan@thebarn.com on Thu, Jul 12, 2001 at 12:26:54PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 12, 2001 at 12:26:54PM -0500, cattelan@thebarn.com wrote: > Actually since the BSD vfs/vnode/VM interface is much closer to IRIX it > shouldn't be nearly as much work. It would be great if someone would do a FreeBSD port of XFS. Linux has benefitted a lot in the past from competive benchmarking and tuning with FreeBSD (and I guess FreeBSD has too). With a good file system like XFS on both Linux and FreeBSD it would be even easier to do that and get one variable out of the way. So I think even for completely selfish reasons on the Linux side a FreeBSD port would be a good thing. -Andi (back to lurking now) From owner-linux-xfs@oss.sgi.com Thu Jul 12 10:58:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CHw5926513 for linux-xfs-outgoing; Thu, 12 Jul 2001 10:58:05 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CHw3V26509 for ; Thu, 12 Jul 2001 10:58:03 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA02606 for ; Thu, 12 Jul 2001 10:58:02 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2413986; Thu, 12 Jul 2001 12:56:46 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA06978; Thu, 12 Jul 2001 12:56:46 -0500 (CDT) Message-ID: <3B4DE505.C9387EDD@sgi.com> Date: Thu, 12 Jul 2001 12:57:25 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Jarkko Santala CC: "linux-xfs@oss.sgi.com" Subject: Re: Another case of "getfh failed: Operation not permitted" References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jarkko Santala wrote: > I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 > based system. When I tried to mount an xfs filesystem (which sits > on top of lvm) exported from this box with NFS, I get a "Permission > denied" on the client side and "rpc.mountd: getfh failed: Operation not > permitted" on the server side. Hm, this again... at one point this was chalked up to the nfsd_operations patch that Mandrake was using, but it showed up on SuSE as well - but I never got very far with that. Is your RH7.1 system pretty much stock (nfs-utils version, etc)? I'll build up a kernel w/ that patch and take another look. -Eric From owner-linux-xfs@oss.sgi.com Thu Jul 12 11:05:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CI5Jv26812 for linux-xfs-outgoing; Thu, 12 Jul 2001 11:05:19 -0700 Received: from fw.hel.fi.ssh.com (fw.hel.fi.ssh.com [193.64.193.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CI5GV26808 for ; Thu, 12 Jul 2001 11:05:16 -0700 Received: from viikuna.hel.fi.ssh.com (viikuna.hel.fi.ssh.com [10.1.0.46]) by fw.hel.fi.ssh.com (SSH-1.26) with SMTP id f6CI5Ep07367 for ; Thu, 12 Jul 2001 21:05:14 +0300 (EEST) Received: (qmail 22805 invoked from network); 12 Jul 2001 18:05:13 -0000 Received: from unknown (HELO torni.hel.fi.ssh.com) ([10.1.0.48]) (envelope-sender ) by viikuna.hel.fi.ssh.com (qmail-ldap-1.03) with SMTP for ; 12 Jul 2001 18:05:13 -0000 Date: Thu, 12 Jul 2001 21:05:13 +0300 (EET DST) From: Jarkko Santala X-X-Sender: To: Eric Sandeen cc: "linux-xfs@oss.sgi.com" Subject: Re: Another case of "getfh failed: Operation not permitted" In-Reply-To: <3B4DE505.C9387EDD@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, Eric Sandeen wrote: > Jarkko Santala wrote: > > > I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 > > based system. When I tried to mount an xfs filesystem (which sits > > on top of lvm) exported from this box with NFS, I get a "Permission > > denied" on the client side and "rpc.mountd: getfh failed: Operation not > > permitted" on the server side. > > Hm, this again... at one point this was chalked up to the > nfsd_operations patch that Mandrake was using, but it showed up on SuSE > as well - but I never got very far with that. Is your RH7.1 system > pretty much stock (nfs-utils version, etc)? I'll build up a kernel w/ > that patch and take another look. It is pretty much stock, nfs-utils version is 0.3.1-5. There's of course the reiserfs stuff, xfs utils, new samba, but AFAIK nothing that should have any affect on this. I'm right now trying to compile with kgcc, doubt if it will help though. -jake -- Jarkko Santala System Administrator Cell. +358407204512 SSH Communications Security Corp, Helsinki, Finland http://www.ssh.com "If only you had a personality instead of an attitude." From owner-linux-xfs@oss.sgi.com Thu Jul 12 11:16:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CIGp627193 for linux-xfs-outgoing; Thu, 12 Jul 2001 11:16:51 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CIGnV27189 for ; Thu, 12 Jul 2001 11:16:49 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA12489 for ; Thu, 12 Jul 2001 11:16:40 -0700 (PDT) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2352215; Thu, 12 Jul 2001 13:15:32 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA89446; Thu, 12 Jul 2001 13:15:31 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id NAA08768; Thu, 12 Jul 2001 13:15:31 -0500 (CDT) Message-Id: <200107121815.NAA08768@fsgi158.americas.sgi.com> Subject: Re: Another case of "getfh failed: Operation not permitted" To: jake@ssh.com (Jarkko Santala) Date: Thu, 12 Jul 2001 13:15:30 -0500 (CDT) Cc: sandeen@sgi.com (Eric Sandeen), linux-xfs@oss.sgi.com (linux-xfs@oss.sgi.com) In-Reply-To: from "Jarkko Santala" at Jul 12, 2001 09:05:13 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > On Thu, 12 Jul 2001, Eric Sandeen wrote: > > > Jarkko Santala wrote: > > > > > I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 > > > based system. When I tried to mount an xfs filesystem (which sits > > > on top of lvm) exported from this box with NFS, I get a "Permission > > > denied" on the client side and "rpc.mountd: getfh failed: Operation not > > > permitted" on the server side. > > > > Hm, this again... at one point this was chalked up to the > > nfsd_operations patch that Mandrake was using, but it showed up on SuSE > > as well - but I never got very far with that. Is your RH7.1 system > > pretty much stock (nfs-utils version, etc)? I'll build up a kernel w/ > > that patch and take another look. > > It is pretty much stock, nfs-utils version is 0.3.1-5. There's of course > the reiserfs stuff, xfs utils, new samba, but AFAIK nothing that should > have any affect on this. > > I'm right now trying to compile with kgcc, doubt if it will help though. > Could you also supply the /etc/exports contents from the server and the mount command from the client? Also have you tried "exportfs -arv" on the server? Thanks, Tad From owner-linux-xfs@oss.sgi.com Thu Jul 12 11:21:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CILSN27389 for linux-xfs-outgoing; Thu, 12 Jul 2001 11:21:28 -0700 Received: from fw.hel.fi.ssh.com (fw.hel.fi.ssh.com [193.64.193.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CILQV27385 for ; Thu, 12 Jul 2001 11:21:26 -0700 Received: from viikuna.hel.fi.ssh.com (viikuna.hel.fi.ssh.com [10.1.0.46]) by fw.hel.fi.ssh.com (SSH-1.26) with SMTP id f6CILPp09164 for ; Thu, 12 Jul 2001 21:21:25 +0300 (EEST) Received: (qmail 27217 invoked from network); 12 Jul 2001 18:21:25 -0000 Received: from unknown (HELO torni.hel.fi.ssh.com) ([10.1.0.48]) (envelope-sender ) by viikuna.hel.fi.ssh.com (qmail-ldap-1.03) with SMTP for ; 12 Jul 2001 18:21:25 -0000 Date: Thu, 12 Jul 2001 21:21:24 +0300 (EET DST) From: Jarkko Santala X-X-Sender: To: Eric Sandeen cc: Subject: Re: Another case of "getfh failed: Operation not permitted" In-Reply-To: <3B4DE658.5DD13CB0@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, Eric Sandeen wrote: > > I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 > > based system. When I tried to mount an xfs filesystem (which sits > > on top of lvm) exported from this box with NFS, I get a "Permission > > denied" on the client side and "rpc.mountd: getfh failed: Operation not > > permitted" on the server side. > > Oh, and do you have any other patches besides XFS in this kernel? No, pure 2.4.6 and the xfs patch above, nothing else, but... You know what? I just put the kgcc compiled one in and now it seems to work! Ain't that a thing. The previous compile was done with RedHat package gcc-c++-2.96-81. Btw, when I was running 2.4.5 the whole thing with NFS worked fine for a couple hours of very light use. Then it just stopped and a message on the server console appeared, saying something about "bug in namei.c! Fsck?". There was also the usual large amount of numbers and stuff, but I couldn't be bothered to write it all down. After that it stopped working. Anyway, it seems to work now, compiled with compat-egcs-6.2-1.1.2.14. I'll let you know if there are problems. -jake -- Jarkko Santala System Administrator Cell. +358407204512 SSH Communications Security Corp, Helsinki, Finland http://www.ssh.com "If only you had a personality instead of an attitude." From owner-linux-xfs@oss.sgi.com Thu Jul 12 11:26:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CIQ6127545 for linux-xfs-outgoing; Thu, 12 Jul 2001 11:26:06 -0700 Received: from fw.hel.fi.ssh.com (fw.hel.fi.ssh.com [193.64.193.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CIQ4V27540 for ; Thu, 12 Jul 2001 11:26:04 -0700 Received: from viikuna.hel.fi.ssh.com (viikuna.hel.fi.ssh.com [10.1.0.46]) by fw.hel.fi.ssh.com (SSH-1.26) with SMTP id f6CIQ2p09525 for ; Thu, 12 Jul 2001 21:26:03 +0300 (EEST) Received: (qmail 28075 invoked from network); 12 Jul 2001 18:26:02 -0000 Received: from unknown (HELO torni.hel.fi.ssh.com) ([10.1.0.48]) (envelope-sender ) by viikuna.hel.fi.ssh.com (qmail-ldap-1.03) with SMTP for ; 12 Jul 2001 18:26:02 -0000 Date: Thu, 12 Jul 2001 21:26:01 +0300 (EET DST) From: Jarkko Santala X-X-Sender: To: Tad Dolphay cc: Eric Sandeen , "linux-xfs@oss.sgi.com" Subject: Re: Another case of "getfh failed: Operation not permitted" In-Reply-To: <200107121815.NAA08768@fsgi158.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, Tad Dolphay wrote: > > > > On Thu, 12 Jul 2001, Eric Sandeen wrote: > > > > > Jarkko Santala wrote: > > > > > > > I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 > > > > based system. When I tried to mount an xfs filesystem (which sits > > > > on top of lvm) exported from this box with NFS, I get a "Permission > > > > denied" on the client side and "rpc.mountd: getfh failed: Operation not > > > > permitted" on the server side. > > > > > > Hm, this again... at one point this was chalked up to the > > > nfsd_operations patch that Mandrake was using, but it showed up on SuSE > > > as well - but I never got very far with that. Is your RH7.1 system > > > pretty much stock (nfs-utils version, etc)? I'll build up a kernel w/ > > > that patch and take another look. > > > > It is pretty much stock, nfs-utils version is 0.3.1-5. There's of course > > the reiserfs stuff, xfs utils, new samba, but AFAIK nothing that should > > have any affect on this. > > > > I'm right now trying to compile with kgcc, doubt if it will help though. > > > > Could you also supply the /etc/exports contents from the server and the > mount command from the client? Also have you tried "exportfs -arv" on the > server? You probably got my previous mail already, that it works, at least for now, with kgcc compiled kernel. But here's stuff you asked anyway: ---cut--- vaasi:~$ cat /etc/exports # # Vitun NFS # /xfs curry(rw) ---cut--- curry:~# mount vaasi:/xfs /mnt/vaasi/xfs ---cut--- I tried all kinds of exportfs commands on the server, including that one, plus stopping and restarting nfs stuff, rebooting many times, mount & umounting the xfs volume, xfs_check and so on. Nothing helped then. -jake -- Jarkko Santala System Administrator Cell. +358407204512 SSH Communications Security Corp, Helsinki, Finland http://www.ssh.com "If only you had a personality instead of an attitude." From owner-linux-xfs@oss.sgi.com Thu Jul 12 12:38:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CJcoc29732 for linux-xfs-outgoing; Thu, 12 Jul 2001 12:38:50 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CJcmV29728 for ; Thu, 12 Jul 2001 12:38:48 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA06472; Thu, 12 Jul 2001 21:38:41 +0200 (CEST) Message-Id: <4.3.2.7.2.20010712213740.0355e758@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 21:38:29 +0200 To: Jarkko Santala , Eric Sandeen From: Seth Mos Subject: Re: Another case of "getfh failed: Operation not permitted" Cc: In-Reply-To: References: <3B4DE658.5DD13CB0@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:21 12-7-2001 +0300, Jarkko Santala wrote: >On Thu, 12 Jul 2001, Eric Sandeen wrote: > > > > I'm running Linux 2.4.6 + linux-2.4.6-xfs-07052001.patch on a RedHat 7.1 > > > based system. When I tried to mount an xfs filesystem (which sits > > > on top of lvm) exported from this box with NFS, I get a "Permission > > > denied" on the client side and "rpc.mountd: getfh failed: Operation not > > > permitted" on the server side. > > > > Oh, and do you have any other patches besides XFS in this kernel? > >No, pure 2.4.6 and the xfs patch above, nothing else, but... > >You know what? I just put the kgcc compiled one in and now it seems to >work! Ain't that a thing. The previous compile was done with RedHat >package gcc-c++-2.96-81. > >Btw, when I was running 2.4.5 the whole thing with NFS worked fine for a >couple hours of very light use. Then it just stopped and a message on the >server console appeared, saying something about "bug in namei.c! Fsck?". >There was also the usual large amount of numbers and stuff, but I couldn't >be bothered to write it all down. After that it stopped working. > >Anyway, it seems to work now, compiled with compat-egcs-6.2-1.1.2.14. I'll >let you know if there are problems. kgcc is a must for production systems. That is why I had put it in the FAQ. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 12:43:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CJhEx29900 for linux-xfs-outgoing; Thu, 12 Jul 2001 12:43:14 -0700 Received: from fw.hel.fi.ssh.com (fw.hel.fi.ssh.com [193.64.193.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CJhCV29896 for ; Thu, 12 Jul 2001 12:43:12 -0700 Received: from viikuna.hel.fi.ssh.com (viikuna.hel.fi.ssh.com [10.1.0.46]) by fw.hel.fi.ssh.com (SSH-1.26) with SMTP id f6CJhBp10704 for ; Thu, 12 Jul 2001 22:43:11 +0300 (EEST) Received: (qmail 6041 invoked from network); 12 Jul 2001 19:43:10 -0000 Received: from unknown (HELO torni.hel.fi.ssh.com) ([10.1.0.48]) (envelope-sender ) by viikuna.hel.fi.ssh.com (qmail-ldap-1.03) with SMTP for ; 12 Jul 2001 19:43:10 -0000 Date: Thu, 12 Jul 2001 22:43:09 +0300 (EET DST) From: Jarkko Santala X-X-Sender: To: Seth Mos cc: "linux-xfs@oss.sgi.com" Subject: Re: Another case of "getfh failed: Operation not permitted" In-Reply-To: <4.3.2.7.2.20010712213740.0355e758@pop.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, Seth Mos wrote: > kgcc is a must for production systems. That is why I had put it in the FAQ. Yep, I read it and that's why I tried it. ;) The linux/Makefile did claim the standard RedHat 7.1 gcc to be usable though... -jake -- Jarkko Santala System Administrator Cell. +358407204512 SSH Communications Security Corp, Helsinki, Finland http://www.ssh.com "If only you had a personality instead of an attitude." From owner-linux-xfs@oss.sgi.com Thu Jul 12 13:09:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CK9t732649 for linux-xfs-outgoing; Thu, 12 Jul 2001 13:09:55 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CK9sV32643 for ; Thu, 12 Jul 2001 13:09:55 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA00906 for ; Thu, 12 Jul 2001 13:09:53 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2387478; Thu, 12 Jul 2001 15:08:36 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA69781; Thu, 12 Jul 2001 15:08:36 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6CKAYU06031; Thu, 12 Jul 2001 15:10:34 -0500 Message-Id: <200107122010.f6CKAYU06031@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jarkko Santala cc: Seth Mos , "linux-xfs@oss.sgi.com" Subject: Re: Another case of "getfh failed: Operation not permitted" In-Reply-To: Message from Jarkko Santala of "Thu, 12 Jul 2001 22:43:09 +0300." Date: Thu, 12 Jul 2001 15:10:34 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, 12 Jul 2001, Seth Mos wrote: > > > kgcc is a must for production systems. That is why I had put it in the FAQ. > > Yep, I read it and that's why I tried it. ;) The linux/Makefile did claim > the standard RedHat 7.1 gcc to be usable though... > > -jake > There is an updated compiler from redhat, they released an update and there is an even more recent one in rawhide. I regularly compile with these and do nfs exports - it has been a long time since I used the original 7.1 gcc though, and I cannot say I ever compiled that particular code combination with that compiler. The fact that different build architectures exhibit different compiler issues does not help either. For the record I am running the cvs kernel compiled with gcc-2.96-88 on a dual processor i686 kernel. I have nfs exports from this box. Oh, another variable is if you build in kdb and tell it to put frame pointers in the kernel, this chews up more registers and changes the code quite a bit, I do not use the frame pointer option. Steve From owner-linux-xfs@oss.sgi.com Thu Jul 12 13:18:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CKIWs01155 for linux-xfs-outgoing; Thu, 12 Jul 2001 13:18:32 -0700 Received: from citadel.oehansen.pp.se (sdu209-201.ppp.algonet.se [195.163.201.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CKITV01150 for ; Thu, 12 Jul 2001 13:18:30 -0700 Received: from citadel.oehansen.pp.se (localhost.localdomain [127.0.0.1]) by citadel.oehansen.pp.se (8.11.2/8.11.2) with SMTP id f6CKJUk04212; Thu, 12 Jul 2001 22:19:31 +0200 Content-Type: text/plain; charset="iso-8859-1" From: "Orn E. Hansen" Reply-To: oe.hansen@gamma.telenordia.se To: Jarkko Santala , Seth Mos Subject: Re: Another case of "getfh failed: Operation not permitted" Date: Thu, 12 Jul 2001 22:19:29 +0200 X-Mailer: KMail [version 1.2] Cc: "linux-xfs@oss.sgi.com" References: In-Reply-To: X-Face: E_zcq`4tZ?pgKcXl2Vy?E.DsIl,aDED%mZEkq[i"_{2x`!#2uiyC(,`^P1u?ni#lDs+k4W.uCn!,W3ZKV0Tpu~p?jOKxKPUJnTZO%$^CW_2zcS\Nx2JJ0QlHJt,C#G+$YYcVcxf`%&@UT[q*4o5~Z>{WG]uJ--;VAJ31/$f`C}4D}F%cL~DS6MiL@gNa:wG_Z`T@b])f~LA_0nj6eB&O.Z$~VM|~jX1073)G6i3r$Z=IZy~=I|%_1 X-MIME-Autoconverted: from 8bit to quoted-printable by citadel.oehansen.pp.se id f6CKJUk04212 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6CKIWV01152 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk fimmtudagur 12. júlí 2001 21:43, Jarkko Santala skrifaði: > > Yep, I read it and that's why I tried it. ;) The linux/Makefile did claim > the standard RedHat 7.1 gcc to be usable though... > Compiling it with gcc does work for vanilla kernels, RH 7.1 on i386 (Athlon) and XFS-1.0.1. Orn From owner-linux-xfs@oss.sgi.com Thu Jul 12 13:19:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CKJu801393 for linux-xfs-outgoing; Thu, 12 Jul 2001 13:19:56 -0700 Received: from relay2.flashnet.it (libra.cyb.it [212.11.95.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CKJsV01389 for ; Thu, 12 Jul 2001 13:19:54 -0700 Received: from ip069.pool-01.cyb.it (ip069.pool-01.cyb.it [195.191.2.70]) by relay2.flashnet.it (EMS-RELAY/8.10.0) with SMTP id f6CKJc122875 for ; Thu, 12 Jul 2001 22:19:39 +0200 From: daedalus@freemail.it To: linux-xfs@oss.sgi.com Subject: slackware 8.0 Date: Thu, 12 Jul 2001 22:31:52 +0200 Message-ID: <4k0skt4o49j5h2d651sjd4is67to8injtl@4ax.com> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6CKJtV01390 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have made a new set of floppy disks (3 x 1.68 MB) based on 1.0.1 realease that could help you to install Slackware 8 on an xfs filesystem that you can create at installation time without dumping/restoring It is very far from a full featured installer but it is good enough to boot a system with / of type xfs it's still up to you to build and install (don't forget make install-dev) the cmd_tars of 1.0.1 release. pointers and informations at: http://village.flashnet.it/users/fn048069 From owner-linux-xfs@oss.sgi.com Thu Jul 12 13:34:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CKYrW02979 for linux-xfs-outgoing; Thu, 12 Jul 2001 13:34:53 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CKYpV02972 for ; Thu, 12 Jul 2001 13:34:51 -0700 Received: from auto-nb1.xs4all.nl (213-84-100-130.adsl.xs4all.nl [213.84.100.130]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA29313; Thu, 12 Jul 2001 22:33:30 +0200 (CEST) Message-Id: <4.3.2.7.2.20010712222855.03562670@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 12 Jul 2001 22:33:17 +0200 To: oe.hansen@gamma.telenordia.se, Jarkko Santala From: Seth Mos Subject: Re: Another case of "getfh failed: Operation not permitted" Cc: "linux-xfs@oss.sgi.com" In-Reply-To: <01071222192900.01654@citadel.oehansen.pp.se> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6CKYpV02976 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 22:19 12-7-2001 +0200, Orn E. Hansen wrote: >fimmtudagur 12. júlí 2001 21:43, Jarkko Santala skrifaði: > > > > Yep, I read it and that's why I tried it. ;) The linux/Makefile did claim > > the standard RedHat 7.1 gcc to be usable though... > > > > Compiling it with gcc does work for vanilla kernels, RH 7.1 on i386 >(Athlon) and XFS-1.0.1. It's machine dependent. There are people using this combination that exhibit problems. I even do, I don't use it because it tends to cause vague problems for which I don't have time to debug them. I have removed gcc from my test systems so I don't accidentally do. I was fighting weird problems to day with a utility that loads the firmware in Eicon Diva Server cards. It was givinginvalid argument messages untill I replaced the compiler with kgcc. I also have a number of userspace utility's that don't compile with gcc. Note that this is with gcc-2.96-85 So updated or not, it still sucks in my not so humble opinion. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 12 14:05:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CL5Xx06418 for linux-xfs-outgoing; Thu, 12 Jul 2001 14:05:33 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CL5WV06410 for ; Thu, 12 Jul 2001 14:05:32 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15Knb8-000759-00; Fri, 13 Jul 2001 09:02:10 +1200 Date: Fri, 13 Jul 2001 09:02:10 +1200 (NZST) From: Juha Saarinen To: Steve Lord cc: Jarkko Santala , Seth Mos , "linux-xfs@oss.sgi.com" Subject: Re: Another case of "getfh failed: Operation not permitted" In-Reply-To: <200107122010.f6CKAYU06031@jen.americas.sgi.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, Steve Lord wrote: > There is an updated compiler from redhat, they released an update and > there is an even more recent one in rawhide. I regularly compile with > these and do nfs exports - it has been a long time since I used the > original 7.1 gcc though, and I cannot say I ever compiled that > particular code combination with that compiler. The fact that different > build architectures exhibit different compiler issues does not help > either. For the record I am running the cvs kernel compiled with > gcc-2.96-88 on a dual processor i686 kernel. I have nfs exports from > this box. Oh, another variable is if you build in kdb and tell it to > put frame pointers in the kernel, this chews up more registers and > changes the code quite a bit, I do not use the frame pointer option. I've found that -88 builds a stable XFS system (this is using the CVS code), whereas earlier RHL 2.96 gccs didn't. My system's a dual P3 with SCSI and IDE drives. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Thu Jul 12 16:21:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6CNLUL22729 for linux-xfs-outgoing; Thu, 12 Jul 2001 16:21:30 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6CNLPV22709 for ; Thu, 12 Jul 2001 16:21:29 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Thu, 12 Jul 2001 16:18:50 -0700 Subject: Re: [OT] XFS and FreeBSD? From: Thomas Duffy To: Adam Cioccarelli Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 12 Jul 2001 16:19:34 -0700 Message-Id: <994979974.14346.23.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 12 Jul 2001 23:18:50.0789 (UTC) FILETIME=[0293CD50:01C10B29] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 12 Jul 2001 11:29:17 +0200, Adam Cioccarelli wrote: > Hi, > > I think you'll find that in the mailing list archives... Actually I was > wondering, while we are off topic, why SGI didn't try and port Irix to > intel architecture? Or will it get ported to IA64? way back when, IRIX was ported to ia32 (a skunxworks project called IRIX LE for little endian). but, then a bunch of Linux folks at SGI convinced the management that it made more sense to embrace Linux for the apps capture. this was also about the same time SGI abandoned NT (which also was slated to run on the big iron -- boy that would have been a mess! but there was a cool hack to make it work called crucible that allowed multiple copies of NT to run on shared hardware, but that is another story altogether). So, IRIX was decided to stick to MIPS and linux to stick to intel. this is the story that SGI is sticking to (even though conceivably, both OS's could run on both hardware platforms). -tduffy From owner-linux-xfs@oss.sgi.com Thu Jul 12 17:09:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D098130903 for linux-xfs-outgoing; Thu, 12 Jul 2001 17:09:08 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D097V30891 for ; Thu, 12 Jul 2001 17:09:07 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id RAA04345 for ; Thu, 12 Jul 2001 17:06:34 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA02513; Fri, 13 Jul 2001 10:07:50 +1000 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA38532; Fri, 13 Jul 2001 10:07:49 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Fri, 13 Jul 2001 10:07:48 +1000 To: Brent A Nelson cc: Subject: Re: xfsdump/xfsrestore problem in the 1.0.1 release In-Reply-To: <200107121451.f6CEplS09516@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 12 Jul 2001, Steve Lord wrote: > > Under release 1.0.1, I noticed a problem with xfsdump/xfsrestore that > > wasn't there in 1.0 (although it did fix an OOPS, and the earlier SUID > > problem). Doing an xfsdump of / piped to a restore on another partition, > > I noticed that the /dev directory didn't transfer correctly. The major > > numbers on all the devices were set to 0. > > > > It seems that I must have read about this problem being fixed before, so > > I'm guessing the CVS version of xfsdump doesn't have this problem? > > Yes, there is a problem here, I just replicated it locally on the current > cvs kernel and xfsdump/restore packages. A mknod on its own creates the > correct information, so this is either dump not getting the correct info > out of the kernel, or an issue between dump and restore themselves. I'll look into it. Ivan -- Ivan Rayner ivanr@melbourne.sgi.com From owner-linux-xfs@oss.sgi.com Thu Jul 12 17:17:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D0HYo32143 for linux-xfs-outgoing; Thu, 12 Jul 2001 17:17:34 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D0HWV32136 for ; Thu, 12 Jul 2001 17:17:32 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id CAA137936 for ; Fri, 13 Jul 2001 02:17:28 +0200 (CEST) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA02573; Fri, 13 Jul 2001 10:16:11 +1000 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA38725; Fri, 13 Jul 2001 10:16:11 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Fri, 13 Jul 2001 10:16:10 +1000 To: Brent A Nelson cc: Subject: Re: xfsdump/xfsrestore problem in the 1.0.1 release In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001, Ivan Rayner wrote: > On Thu, 12 Jul 2001, Steve Lord wrote: > > > > Under release 1.0.1, I noticed a problem with xfsdump/xfsrestore that > > > wasn't there in 1.0 (although it did fix an OOPS, and the earlier SUID > > > problem). Doing an xfsdump of / piped to a restore on another partition, > > > I noticed that the /dev directory didn't transfer correctly. The major > > > numbers on all the devices were set to 0. > > > > > > It seems that I must have read about this problem being fixed before, so > > > I'm guessing the CVS version of xfsdump doesn't have this problem? > > > > Yes, there is a problem here, I just replicated it locally on the current > > cvs kernel and xfsdump/restore packages. A mknod on its own creates the > > correct information, so this is either dump not getting the correct info > > out of the kernel, or an issue between dump and restore themselves. > > I'll look into it. No I wont ... But what I will do is read all my email in future before butting in. :) Ivan -- Ivan Rayner ivanr@melbourne.sgi.com From owner-linux-xfs@oss.sgi.com Thu Jul 12 17:56:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D0u6X03670 for linux-xfs-outgoing; Thu, 12 Jul 2001 17:56:06 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D0u5V03665 for ; Thu, 12 Jul 2001 17:56:05 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id CAA139522 for ; Fri, 13 Jul 2001 02:56:02 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 KAA02840; Fri, 13 Jul 2001 10:54:45 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA91905; Fri, 13 Jul 2001 10:54:44 +1000 (EST) From: "Nathan Scott" Message-Id: <10107131054.ZM208593@wobbly.melbourne.sgi.com> Date: Fri, 13 Jul 2001 10:54:42 -0500 In-Reply-To: Luc Lalonde "System locking: kernel-2.4.6pre3-xfs" (Jul 12, 9:20am) References: <3B4DA431.FB26BA96@giref.ulaval.ca> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Luc Lalonde , "linux-xfs@oss.sgi.com " Subject: Re: System locking: kernel-2.4.6pre3-xfs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Luc, On Jul 12, 9:20am, Luc Lalonde wrote: > Subject: System locking: kernel-2.4.6pre3-xfs > > Hello Folks, > > I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > kernels. Every 10 days or so the systems locks and I have to reboot. > ... > I've been folllowing the XFS kernel development and have been trying > updating since 2.4.2-XFS. Could you build a kernel with kdb enabled and dump the call stack ("bt" command) when the system hangs? That would give us a better idea as to whether or not your hang is related to XFS, and a better starting point for debugging. It would also probably be worthwhile moving up to the current development tree which is 2.4.7-pre6 based so that everyone is looking at the same code when you do extract some debug info. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 12 18:58:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D1wmk08529 for linux-xfs-outgoing; Thu, 12 Jul 2001 18:58:48 -0700 Received: from rebel.net.au (IDENT:root@rebel.rebel.net.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D1wkV08524 for ; Thu, 12 Jul 2001 18:58:47 -0700 Received: from rebel.net.au (dialup-2.rebel.net.au [203.20.69.72]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id LAA01241 for ; Fri, 13 Jul 2001 11:28:44 +0930 Message-ID: <3B4E568F.F3FE39C1@rebel.net.au> Date: Fri, 13 Jul 2001 11:31:51 +0930 From: David Lloyd X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: SysReq Magic Key Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk That's the third time I've had to reboot because of the SysReq Magic Key Debug which is enabled in the 1.0.1_PR3 Kernel. How do you turn it OFF without a kernel rebuild? DSL -- "The greatest thing you'll ever learn is just to love and to be loved in return." - David Bowie (Nature Boy from Moulin Rouge) From owner-linux-xfs@oss.sgi.com Thu Jul 12 19:09:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D29a809378 for linux-xfs-outgoing; Thu, 12 Jul 2001 19:09:36 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D29ZV09374 for ; Thu, 12 Jul 2001 19:09:35 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id TAA02093 for ; Thu, 12 Jul 2001 19:09:28 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id VAA2379139; Thu, 12 Jul 2001 21:08:11 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id VAA62149; Thu, 12 Jul 2001 21:08:11 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6D2A7506767; Thu, 12 Jul 2001 21:10:07 -0500 Message-Id: <200107130210.f6D2A7506767@jen.americas.sgi.com> To: David Lloyd cc: linux-xfs@oss.sgi.com Subject: Re: SysReq Magic Key References: <3B4E568F.F3FE39C1@rebel.net.au> Comments: In-reply-to David Lloyd message dated "Fri, 13 Jul 2001 11:31:51 +0930." Date: Thu, 12 Jul 2001 21:10:07 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > That's the third time I've had to reboot because of the SysReq Magic Key > Debug which is enabled in the 1.0.1_PR3 Kernel. How do you turn it OFF > without a kernel rebuild? > I think this will do the trick: echo 0 > /proc/sys/kernel/sysrq Steve From owner-linux-xfs@oss.sgi.com Thu Jul 12 19:19:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D2J8Y09982 for linux-xfs-outgoing; Thu, 12 Jul 2001 19:19:08 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D2J7V09978 for ; Thu, 12 Jul 2001 19:19:07 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id EAA142265 for ; Fri, 13 Jul 2001 04:19:05 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA10959 for linux-xfs@oss.sgi.com; Fri, 13 Jul 2001 12:17:47 +1000 (EST) Date: Fri, 13 Jul 2001 12:17:47 +1000 (EST) From: Nathan Scott Message-Id: <200107130217.MAA10959@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump configure.in Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Thu Jul 12 19:17:07 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98805a cmd/xfsdump/configure.in - 1.7 - add a check for the IRIX_MKDEV macro so that we know we are building against the correct XFS headers. this way we can give a meaningful error message and people will know what to do, rather than having a compile error later. From owner-linux-xfs@oss.sgi.com Thu Jul 12 19:31:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D2V9k10803 for linux-xfs-outgoing; Thu, 12 Jul 2001 19:31:09 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D2V7V10796 for ; Thu, 12 Jul 2001 19:31:07 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id EAA141990 for ; Fri, 13 Jul 2001 04:31:04 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA21671; Fri, 13 Jul 2001 12:29:21 +1000 (EST) Date: Fri, 13 Jul 2001 12:29:20 +1000 From: Timothy Shimmin To: Seth Mos Cc: Luc Lalonde , "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs Message-ID: <20010713122920.K11622@boing.melbourne.sgi.com> References: <4.3.2.7.2.20010712154129.02c85ee0@pop.xs4all.nl> <3B4DB0D1.FE016E3C@giref.ulaval.ca> <4.3.2.7.2.20010712163042.0357d390@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <4.3.2.7.2.20010712163042.0357d390@pop.xs4all.nl>; from knuffie@xs4all.nl on Thu, Jul 12, 2001 at 04:35:18PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Luc, On Thu, Jul 12, 2001 at 04:35:18PM +0200, Seth Mos wrote: > >I looked this morning and I see this message (dmesg): > > > >st0: Block limits 1 - 16777215 bytes > > This equates to 15GB... rotten tape or drive going mad. It should read 20GB > if I am correct. > If I use 1GB = 1000MB it comes at 16GB which is still 4GB short. Hmmm...sorry I don't understand this comment. The message is coming from the scsi tape driver (linux/drivers/scsi/st.c) and I believe it is printed the first time the tape device is opened. It specifies the limits on the block size - thus the size of a read or write have to be within these limits. In xfsdump/xfsrestore we use a read/write size of 1Mb. We have tested with an Archive Python DAT drive and we always seem to get that exact message i.e. 16Mb for max. block size (it is the result of a READ_BLOCK_LIMITS scsi cmd). So that msg looks normal to me :) (According to linux/drivers/scsi/README.st, you could define DEBUG in st.c and have it generate debugging messages. Don't know if this would help show anything useful though.) --Tim From owner-linux-xfs@oss.sgi.com Thu Jul 12 20:32:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D3WTA15489 for linux-xfs-outgoing; Thu, 12 Jul 2001 20:32:29 -0700 Received: from myth10.Stanford.EDU (myth10.Stanford.EDU [171.64.15.24]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D3WRV15484 for ; Thu, 12 Jul 2001 20:32:27 -0700 Received: (from smv@localhost) by myth10.Stanford.EDU (8.11.1/8.11.1) id f6D3WLC29889; Thu, 12 Jul 2001 20:32:21 -0700 (PDT) Date: Thu, 12 Jul 2001 20:32:21 -0700 (PDT) From: Sergei Morozov To: Subject: "LILO: /dev/sda: Read-only file system" after /boot flirted with xfs Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have managed to compile linux-2.4.6-pre9-xfs-smp kernel and converted /home and /projects to xfs, and it worked great. Then foolishly I repeated the exercise for /boot, and got LI on reboot. Using floppy with old non-xfs kernel I booted all non-xfs partitions; and turned /boot back to ext2 (but at the cost of its content), pulled xfs-aware kernel out of the depths of /usr/src/linux-2.4/ into /boot; and try to rerun lilo but it wouldn't install by saying #lilo -v LILO version 21.4-4 Copyright (C) 1992-1998 Werner Almesberger 'lba32' extensions Copyright (C) 1999,2000 John Coffman Reading boot sector from /dev/sda Merging with /boot/boot.b Fatal: read /dev/sda : Read-only file system #more /etc/lilo.conf boot=/dev/sda map=/boot/map install=/boot/boot.b prompt timeout=50 linear default=xfs message=/boot/message image=/boot/vmlinuz-2.4.6-pre9-xfs-smp label=xfs read-only root=/dev/sda5 #more /etc/mtab /dev/sda5 / ext2 rw 0 0 none /proc proc rw 0 0 /dev/sdb1 /usr ext2 rw 0 0 /dev/fd0 /mnt/floppy ext2 rw,noexec,nosuid,nodev 0 0 none /dev/pts devpts rw,gid=5,mode=620 0 0 /dev/sda1 /boot ext2 rw 0 0 #more /etc/fstab /dev/sda5 / ext2 rw 0 0 /dev/sda1 /boot ext2 rw 0 0 /dev/sdb6 /home xfs deafults 1 2 /dev/cdrom /mnt/cdrom iso9660 auto,user,ro 0 0 /dev/cdrom1 /mnt/cdrom1 iso9660 auto,user,ro 0 0 /dev/sda7 /projects xfs defaults 1 2 /dev/sdb1 /usr ext2 rw 0 0 /dev/fd0 /mnt/floppy auto auto,user 0 0 none /proc proc rw 0 0 none /dev/pts devpts gid=5,mode=620 0 0 /dev/sda6 swap swap defaults 0 0 /dev/sdb5 swap swap defaults 0 0 It doesn't seem that /boot is read only. How I now make lilo install somewhere, best of all to MBR and /boot and restore contents of /boot? And, yes, xfs kernel is too big for floppy. TIA, Sergei Writing is easy; all you do is sit staring at the blank sheet of paper until drops of blood form on your forehead. -- Gene Fowler Sergei Morozov Department of Economics Stanford University Stanford, CA, 94305-6072 ph: (650)-725-8984 (o) (650)-498-1248 (h) -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOH8VK3ZlrUSqDLbVAQFHIwP/dYGV0yV2AYoFWWfJDE6WMtYOLjUSebaV Mzv3ICK2SDPTQ6u3lKx/7VXdY1151pqRZ3Kn7Z8FPZ2KxjRIqeLtOsCMFPRXM234 j23RfBtNPzG2pTOciJvqh0uHxySMR7Dzee+gjniNJadXyE0Y2+C33HICuVVqDH8O ZEhGny68w7c= =sz39 -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Thu Jul 12 21:38:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D4c5F19881 for linux-xfs-outgoing; Thu, 12 Jul 2001 21:38:05 -0700 Received: from oboe.it.uc3m.es (oboe.it.uc3m.es [163.117.139.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D4c3V19871 for ; Thu, 12 Jul 2001 21:38:03 -0700 Received: (from ptb@localhost) by oboe.it.uc3m.es (8.11.0/8.11.0) id f6D4bjl07467; Fri, 13 Jul 2001 06:37:45 +0200 From: "Peter T. Breuer" Message-Id: <200107130437.f6D4bjl07467@oboe.it.uc3m.es> Subject: Re: System locking: kernel-2.4.6pre3-xfs In-Reply-To: <10107131054.ZM208593@wobbly.melbourne.sgi.com> from "Nathan Scott" at "Jul 13, 2001 10:54:42 am" To: "Nathan Scott" Date: Fri, 13 Jul 2001 06:37:45 +0200 (MET DST) CC: linux-xfs@oss.sgi.com X-Anonymously-To: Reply-To: ptb@it.uc3m.es X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "A month of sundays ago Nathan Scott wrote:" > hi Luc, > > On Jul 12, 9:20am, Luc Lalonde wrote: > > Subject: System locking: kernel-2.4.6pre3-xfs > > > > Hello Folks, > > > > I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > > kernels. Every 10 days or so the systems locks and I have to reboot. > > ... > > I've been folllowing the XFS kernel development and have been trying > > updating since 2.4.2-XFS. > > Could you build a kernel with kdb enabled and dump the call > stack ("bt" command) when the system hangs? That would give > us a better idea as to whether or not your hang is related to > XFS, and a better starting point for debugging. I have been having exactly the same symptom on my dell poweredge under 2.4.3 + xfs. I am not cinvinced it is xfs. I changed to 2.4.6 + xfs and the lockups increased in frequency. It's been up for a day now, but yesterday it locked several times in succession. On one occasion I saw the crash, and it was the NMI watchdog kicking in! It said that CPU 1 was locked. The trace was of the most active process at the time. > It would also probably be worthwhile moving up to the current > development tree which is 2.4.7-pre6 based so that everyone is > looking at the same code when you do extract some debug info. Peter From owner-linux-xfs@oss.sgi.com Thu Jul 12 22:32:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D5WPe24136 for linux-xfs-outgoing; Thu, 12 Jul 2001 22:32:25 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D5WNV24132 for ; Thu, 12 Jul 2001 22:32:23 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id HAA13386; Fri, 13 Jul 2001 07:32:21 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id HAA10669; Fri, 13 Jul 2001 07:32:21 +0200 (CEST) Date: Fri, 13 Jul 2001 07:32:21 +0200 (CEST) From: Seth Mos To: Timothy Shimmin cc: Luc Lalonde , "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs In-Reply-To: <20010713122920.K11622@boing.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001, Timothy Shimmin wrote: > Hi Luc, > > On Thu, Jul 12, 2001 at 04:35:18PM +0200, Seth Mos wrote: > > >I looked this morning and I see this message (dmesg): > > > > > >st0: Block limits 1 - 16777215 bytes > > > > This equates to 15GB... rotten tape or drive going mad. It should read 20GB > > if I am correct. > > If I use 1GB = 1000MB it comes at 16GB which is still 4GB short. > Hmmm...sorry I don't understand this comment. > > The message is coming from the scsi tape driver (linux/drivers/scsi/st.c) > and I believe it is printed the first time the tape device is opened. > It specifies the limits on the block size - thus the size of a read > or write have to be within these limits. > In xfsdump/xfsrestore we use a read/write size of 1Mb. > We have tested with an Archive Python DAT drive and we always > seem to get that exact message i.e. 16Mb for max. block size > (it is the result of a READ_BLOCK_LIMITS scsi cmd). > > So that msg looks normal to me :) Nevermind this message, I'm blaming the windows calc ;-) The coffee probably was not strong enough. > (According to linux/drivers/scsi/README.st, you could define > DEBUG in st.c and have it generate debugging messages. > Don't know if this would help show anything useful though.) > > --Tim From owner-linux-xfs@oss.sgi.com Thu Jul 12 23:03:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D63vw26005 for linux-xfs-outgoing; Thu, 12 Jul 2001 23:03:57 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D63uV26001 for ; Thu, 12 Jul 2001 23:03:56 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id XAA06853 for ; Thu, 12 Jul 2001 23:03:54 -0700 (PDT) mail_from (tes@snort.melbourne.sgi.com) Received: (from tes@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA06696 for linux-xfs@oss.sgi.com; Fri, 13 Jul 2001 16:02:37 +1000 (EST) Date: Fri, 13 Jul 2001 16:02:37 +1000 (EST) From: Timothy Shimmin Message-Id: <200107130602.QAA06696@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/xfsrestore rmt host debug files Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From changes file: xfsdump-1.0.12 (13 July 2001) - Fix mistake introduced in 1.0.10 whereby xfsdump/xfsrestore to remote tape drives will cause rmt debug messages to be written to the remote machine in: /server.XXX (where XXX = pid). These files will no longer be created via xfsdump/xfsrestore. The fix is in librmt - it should have only written out warning messages and not debug messages. If the debug environment variable is turned on for librmt then the debug file will go to /tmp/librmt_debug.XXX. --Tim Date: Thu Jul 12 23:00:21 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/tes/slinx-xfs-acl The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98812a cmd/xfsdump/librmt/rmtopen.c - 1.5 - Only output the remote rmt debug file if the mode is debug and not warning. Also change the path of the remote debug file to be more descriptive and in /tmp. cmd/xfsdump/VERSION - 1.12 - Bump version to 12 for debug msg fix. cmd/xfsdump/doc/CHANGES - 1.13 - Explain fix for revision 12 concening rmt host debug file. cmd/xfsdump/librmt/rmtmsg.c - 1.2 - Change function to return back debug code to determine if it is a warning or a debug msg. From owner-linux-xfs@oss.sgi.com Thu Jul 12 23:27:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D6RUu27459 for linux-xfs-outgoing; Thu, 12 Jul 2001 23:27:30 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D6RRV27453 for ; Thu, 12 Jul 2001 23:27:27 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA05903; Fri, 13 Jul 2001 08:27:22 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA15519; Fri, 13 Jul 2001 08:27:21 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 0B27957306; Fri, 13 Jul 2001 08:36:06 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id DA18925835; Fri, 13 Jul 2001 08:44:03 +0200 (CEST) Message-ID: <3B4E94A9.1D675A6E@ch.sauter-bc.com> Date: Fri, 13 Jul 2001 08:26:49 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Sergei Morozov Cc: linux-xfs@oss.sgi.com Subject: Re: "LILO: /dev/sda: Read-only file system" after /boot flirted withxfs References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sergei Morozov schrieb: > > Hi, > > I have managed to compile linux-2.4.6-pre9-xfs-smp kernel and converted > /home and /projects to xfs, and it worked great. Then foolishly I repeated > the exercise for /boot, and got LI on reboot. Using floppy with old > non-xfs kernel I booted all non-xfs partitions; and turned /boot back to > ext2 (but at the cost of its content), pulled xfs-aware kernel out of the > depths of /usr/src/linux-2.4/ into /boot; and try to rerun lilo > but it wouldn't install by saying > > #lilo -v > LILO version 21.4-4 Copyright (C) 1992-1998 Werner Almesberger > 'lba32' extensions Copyright (C) 1999,2000 John Coffman > > Reading boot sector from /dev/sda > Merging with /boot/boot.b > Fatal: read /dev/sda : Read-only file system > > #more /etc/lilo.conf > boot=/dev/sda > map=/boot/map > install=/boot/boot.b > prompt > timeout=50 > linear > default=xfs > message=/boot/message > image=/boot/vmlinuz-2.4.6-pre9-xfs-smp > label=xfs > read-only > root=/dev/sda5 > > #more /etc/mtab > /dev/sda5 / ext2 rw 0 0 > none /proc proc rw 0 0 > /dev/sdb1 /usr ext2 rw 0 0 > /dev/fd0 /mnt/floppy ext2 rw,noexec,nosuid,nodev 0 0 > none /dev/pts devpts rw,gid=5,mode=620 0 0 > /dev/sda1 /boot ext2 rw 0 0 > > #more /etc/fstab > /dev/sda5 / ext2 rw 0 0 > /dev/sda1 /boot ext2 rw 0 0 > /dev/sdb6 /home xfs deafults 1 2 > /dev/cdrom /mnt/cdrom iso9660 auto,user,ro 0 0 > /dev/cdrom1 /mnt/cdrom1 iso9660 auto,user,ro 0 0 > /dev/sda7 /projects xfs defaults 1 2 > /dev/sdb1 /usr ext2 rw 0 0 > /dev/fd0 /mnt/floppy auto auto,user 0 0 > none /proc proc rw 0 0 > none /dev/pts devpts gid=5,mode=620 0 0 > /dev/sda6 swap swap defaults 0 0 > /dev/sdb5 swap swap defaults 0 0 My tip: use something like swap to get better perfomance:-) /dev/sda6 swap swap defaults,pri=0 0 0 /dev/sdb5 swap swap defaults,pri=0 0 0 > > It doesn't seem that /boot is read only. One question, how did you boot with the floppy. Sometimes one does boot with something like init=/bin/sh and / is mounted ro, even when mount tells you it is rw. Maybe the problem was such thing. mtab will also report rw falsely, maybe cat /proc/mounts shows the truth. > How I now make lilo install somewhere, best of all to MBR and /boot and > restore contents of /boot? And, yes, xfs kernel is too big for floppy. > > TIA, > Sergei > > Writing is easy; > all you do is sit staring > at the blank sheet of paper until > drops of blood form on your forehead. > -- Gene Fowler > > Sergei Morozov > Department of Economics > Stanford University > Stanford, CA, 94305-6072 > ph: (650)-725-8984 (o) > (650)-498-1248 (h) > > -----BEGIN PGP SIGNATURE----- > Version: 2.6.2 > > iQCVAwUBOH8VK3ZlrUSqDLbVAQFHIwP/dYGV0yV2AYoFWWfJDE6WMtYOLjUSebaV > Mzv3ICK2SDPTQ6u3lKx/7VXdY1151pqRZ3Kn7Z8FPZ2KxjRIqeLtOsCMFPRXM234 > j23RfBtNPzG2pTOciJvqh0uHxySMR7Dzee+gjniNJadXyE0Y2+C33HICuVVqDH8O > ZEhGny68w7c= > =sz39 > -----END PGP SIGNATURE----- -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 12 23:32:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D6W7727886 for linux-xfs-outgoing; Thu, 12 Jul 2001 23:32:07 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D6W6V27881 for ; Thu, 12 Jul 2001 23:32:06 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA06387; Fri, 13 Jul 2001 08:31:57 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA15947; Fri, 13 Jul 2001 08:31:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 230AA57306; Fri, 13 Jul 2001 08:41:16 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id CE81125835; Fri, 13 Jul 2001 08:49:13 +0200 (CEST) Message-ID: <3B4E95DF.35676167@ch.sauter-bc.com> Date: Fri, 13 Jul 2001 08:31:59 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: ptb@it.uc3m.es Cc: Nathan Scott , linux-xfs@oss.sgi.com Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <200107130437.f6D4bjl07467@oboe.it.uc3m.es> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Peter T. Breuer" schrieb: > > "A month of sundays ago Nathan Scott wrote:" > > hi Luc, > > > > On Jul 12, 9:20am, Luc Lalonde wrote: > > > Subject: System locking: kernel-2.4.6pre3-xfs > > > > > > Hello Folks, > > > > > > I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > > > kernels. Every 10 days or so the systems locks and I have to reboot. > > > ... > > > I've been folllowing the XFS kernel development and have been trying > > > updating since 2.4.2-XFS. > > > > Could you build a kernel with kdb enabled and dump the call > > stack ("bt" command) when the system hangs? That would give > > us a better idea as to whether or not your hang is related to > > XFS, and a better starting point for debugging. > > I have been having exactly the same symptom on my dell poweredge > under 2.4.3 + xfs. I am not cinvinced it is xfs. > > I changed to 2.4.6 + xfs and the lockups increased in frequency. > It's been up for a day now, but yesterday it locked several times in > succession. On one occasion I saw the crash, and it was the NMI > watchdog kicking in! It said that CPU 1 was locked. The trace was Maybe you have to change some settings in the BIOS Setup. Some 'operating systems' need a watchdog to free them from showing a blue screen after some minutes or hours of operation :), but Linux does not need it usually and it's good to disable all those features in the setup (if they exist). > of the most active process at the time. > > > It would also probably be worthwhile moving up to the current > > development tree which is 2.4.7-pre6 based so that everyone is > > looking at the same code when you do extract some debug info. > > Peter -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 12 23:37:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D6b2a28297 for linux-xfs-outgoing; Thu, 12 Jul 2001 23:37:02 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D6b0V28291 for ; Thu, 12 Jul 2001 23:37:01 -0700 Received: from verbum.org (root@gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id CAA12938 for ; Fri, 13 Jul 2001 02:36:59 -0400 (EDT) Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by verbum.org (Postfix (Debian/GNU)) with ESMTP id 9799F6E28 for ; Fri, 13 Jul 2001 02:31:31 -0400 (EDT) Received: by space-ghost (Postfix (Debian/GNU), from userid 1000) id 2CAA9622F57; Fri, 13 Jul 2001 02:31:37 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: oops with 2.4.6 on ppc X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Fri, 13 Jul 2001 02:31:37 -0400 Message-ID: <87n169jq5y.church.of.emacs@cis.ohio-state.edu> Lines: 62 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk My kernel dropped me into mon today while reading email and doing an 'apt-get install agt'; From the output of ksymoops, it looks like a failure in the XFS code, so I'm posting it here. I looked around a bit inside mon, and then just exited, and the system appeared to mostly work. The dpkg process was in an uninterruptible state. /sbin/reboot just hung, I had to hard reboot (but no fsck! yay! :) ), one of the files dpkg was installing was just 100 null bytes. The rest of the filesystem seems fine, although I didn't do a thorough check. Here's the output of ksymoops: walters@space-ghost:~$ ksymoops -k /proc/ksyms /tmp/oops ksymoops 2.4.1 on ppc 2.4.6+ipsec+xfs. Options used -V (default) -k /proc/ksyms (specified) -l /proc/modules (default) -o /lib/modules/2.4.6+ipsec+xfs/ (default) -m /boot/System.map-2.4.6+ipsec+xfs (default) Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(rtc_lock) not found in System.map. Ignoring ksyms_base entry Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(shmem_file_setup) not found in System.map. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol xchg_u32 , ksyms_base says c000c24c, System.map says c0006820. Ignoring ksyms_base entry Jul 13 01:36:39 space-ghost kernel: Oops: kernel access of bad area, sig: 11 Jul 13 01:36:39 space-ghost kernel: NIP: C0086C88 XER: 20000000 LR: C0086C80 SP: C06F19D0 REGS: c06f1920 TRAP: 0300 Using defaults from ksymoops -t elf32-powerpc -a powerpc:common Jul 13 01:36:39 space-ghost kernel: MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 Jul 13 01:36:39 space-ghost kernel: TASK = c06f0000[5] 'bdflush' Last syscall: -1 Jul 13 01:36:39 space-ghost kernel: last math c5bf6000 last altivec 00000000 Jul 13 01:36:39 space-ghost kernel: GPR00: C0086C80 C06F19D0 C06F0000 C5C701C0 00000000 00000000 00000000 C1C8A420 Jul 13 01:36:39 space-ghost kernel: GPR08: C144A040 C5C70228 0000000A C5C70228 C1C8A244 01A3FE74 00000000 00000000 Jul 13 01:36:39 space-ghost kernel: GPR16: 00000000 00000000 00000000 C07DB000 00000000 C06F1A38 00000000 00000006 Jul 13 01:36:39 space-ghost kernel: GPR24: 00000000 C07DB000 00000001 00000001 00000000 00000000 00000000 C5C701C0 Jul 13 01:36:39 space-ghost kernel: Call backtrace: Jul 13 01:36:39 space-ghost kernel: C0086C80 C008816C C0083438 C0083CF4 C0083720 C00859E8 C0092D50 Jul 13 01:36:39 space-ghost kernel: C00960C8 C00E1A14 C00DFCB4 C00731D8 C0072D6C C00DFE70 C003A864 Jul 13 01:36:40 space-ghost kernel: C003E664 C003E95C C0006C0C Warning (Oops_read): Code line not seen, dumping what data is available >>NIP; c0086c88 <===== Trace; c0086c80 Trace; c008816c Trace; c0083438 Trace; c0083cf4 Trace; c0083720 Trace; c00859e8 Trace; c0092d50 Trace; c00960c8 Trace; c00e1a14 Trace; c00dfcb4 Trace; c00731d8 <__pb_block_prepare_write_async+c0/29c> Trace; c0072d6c Trace; c00dfe70 Trace; c003a864 <_write_buffer+b8/138> Trace; c003e664 Trace; c003e95c Trace; c0006c0c 4 warnings issued. Results may not be reliable. walters@space-ghost:~$ From owner-linux-xfs@oss.sgi.com Fri Jul 13 00:21:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D7LbB30190 for linux-xfs-outgoing; Fri, 13 Jul 2001 00:21:37 -0700 Received: from myth10.Stanford.EDU (myth10.Stanford.EDU [171.64.15.24]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D7LaV30186 for ; Fri, 13 Jul 2001 00:21:36 -0700 Received: (from smv@localhost) by myth10.Stanford.EDU (8.11.1/8.11.1) id f6D7LRW04111; Fri, 13 Jul 2001 00:21:27 -0700 (PDT) Date: Fri, 13 Jul 2001 00:21:26 -0700 (PDT) From: Sergei Morozov To: Simon Matter cc: Subject: Re: "LILO: /dev/sda: Read-only file system" after /boot flirted withxfs In-Reply-To: <3B4E94A9.1D675A6E@ch.sauter-bc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > It doesn't seem that /boot is read only. > > One question, how did you boot with the floppy. Sometimes one does A year ago bootdisk was created for then Red Hat 6.2 (now 7+changes) for the same machine except it had 1 cpu. So the kernel on that floppy is not xfs-aware, and it can boot other non xfs partitions. > boot with something like init=/bin/sh and / is mounted ro, even when > mount tells you it is rw. Maybe the problem was such thing. mtab > will also report rw falsely, maybe cat /proc/mounts shows the truth. cat /proc/mounts still shows rw; also I can write on / and /boot fine, but not lilo somehow. > > > How I now make lilo install somewhere, best of all to MBR and /boot and > > restore contents of /boot? And, yes, xfs kernel is too big for floppy. > > > > TIA, > > Sergei From owner-linux-xfs@oss.sgi.com Fri Jul 13 00:24:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D7OKG30360 for linux-xfs-outgoing; Fri, 13 Jul 2001 00:24:20 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D7OJV30356 for ; Fri, 13 Jul 2001 00:24:19 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id AAA08865 for ; Fri, 13 Jul 2001 00:21:46 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 RAA04972; Fri, 13 Jul 2001 17:22:58 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Simon Matter cc: ptb@it.uc3m.es, linux-xfs@oss.sgi.com Subject: Re: System locking: kernel-2.4.6pre3-xfs In-reply-to: Your message of "Fri, 13 Jul 2001 08:31:59 +0200." <3B4E95DF.35676167@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Jul 2001 17:22:58 +1000 Message-ID: <2866.995008978@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001 08:31:59 +0200, Simon Matter wrote: >"Peter T. Breuer" schrieb: >> succession. On one occasion I saw the crash, and it was the NMI >> watchdog kicking in! It said that CPU 1 was locked. The trace was > >Maybe you have to change some settings in the BIOS Setup. Some >'operating systems' need a watchdog to free them from showing >a blue screen after some minutes or hours of operation :), but >Linux does not need it usually and it's good to disable all >those features in the setup (if they exist). The NMI watchdog has nothing to do with the BIOS. It is a feature of Linux where we generate non maskable interrupts to catch disabled spinloops inside the kernel. With kdb compiled in and active, the NMI watchdog is a very useful debugging aid. From owner-linux-xfs@oss.sgi.com Fri Jul 13 00:48:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D7mpU31469 for linux-xfs-outgoing; Fri, 13 Jul 2001 00:48:51 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D7mmV31465 for ; Fri, 13 Jul 2001 00:48:49 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6D7mge13954; Fri, 13 Jul 2001 09:48:42 +0200 Message-Id: <4.3.2.7.2.20010713094103.030b3ff0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 13 Jul 2001 09:48:29 +0200 To: Sergei Morozov , Simon Matter From: Seth Mos Subject: Re: "LILO: /dev/sda: Read-only file system" after /boot flirted withxfs Cc: In-Reply-To: References: <3B4E94A9.1D675A6E@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:21 13-7-2001 -0700, Sergei Morozov wrote: > > > It doesn't seem that /boot is read only. > > > > One question, how did you boot with the floppy. Sometimes one does > >A year ago bootdisk was created for then Red Hat 6.2 (now 7+changes) for >the same machine except it had 1 cpu. So the kernel on that floppy is not >xfs-aware, and it can boot other non xfs partitions. There is a link in the FAQ to a xfs-aware rescue/boot floppy set. http://oss.sgi.com/projects/xfs/faq.html#xfsbootdisks > > boot with something like init=/bin/sh and / is mounted ro, even when > > mount tells you it is rw. Maybe the problem was such thing. mtab > > will also report rw falsely, maybe cat /proc/mounts shows the truth. > >cat /proc/mounts still shows rw; also I can write on / and /boot fine, but >not lilo somehow. If you can format /boot correctly and mount it. Put a xfs-aware kernel in there and run lilo. I don't know if lilo checks for the rootfs to be ro or the /boot. Otherwise use the bootdisks referenced above and fix it using that. If you have the installer iso available you can boot from that cdrom in rescue mode and fix up your system. I managed to fix mine that way. > > > How I now make lilo install somewhere, best of all to MBR and /boot and > > > restore contents of /boot? And, yes, xfs kernel is too big for floppy. if your lilo.conf has not changed it should go to the MBR. For making larger bootfloppy's see http://oss.sgi.com/projects/xfs/faq.html#xfsfitfloppy Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 13 01:19:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D8J4M00603 for linux-xfs-outgoing; Fri, 13 Jul 2001 01:19:04 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D8J1V00596 for ; Fri, 13 Jul 2001 01:19:01 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA15703; Fri, 13 Jul 2001 10:18:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA24640; Fri, 13 Jul 2001 10:18:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 43F3957306; Fri, 13 Jul 2001 10:28:44 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id C14E125835; Fri, 13 Jul 2001 10:36:41 +0200 (CEST) Message-ID: <3B4EAF0F.D98631AC@ch.sauter-bc.com> Date: Fri, 13 Jul 2001 10:19:27 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Keith Owens Cc: ptb@it.uc3m.es, linux-xfs@oss.sgi.com Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <2866.995008978@kao2.melbourne.sgi.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Keith Owens schrieb: > > On Fri, 13 Jul 2001 08:31:59 +0200, > Simon Matter wrote: > >"Peter T. Breuer" schrieb: > >> succession. On one occasion I saw the crash, and it was the NMI > >> watchdog kicking in! It said that CPU 1 was locked. The trace was > > > >Maybe you have to change some settings in the BIOS Setup. Some > >'operating systems' need a watchdog to free them from showing > >a blue screen after some minutes or hours of operation :), but > >Linux does not need it usually and it's good to disable all > >those features in the setup (if they exist). > > The NMI watchdog has nothing to do with the BIOS. It is a feature of > Linux where we generate non maskable interrupts to catch disabled > spinloops inside the kernel. With kdb compiled in and active, the NMI > watchdog is a very useful debugging aid. Sorry, I thought it is the watchdog of a 'server managment card' generating NMI's. Stupid question: what happens if for example Memory Error Correction generates an NMI because it detected an error? From owner-linux-xfs@oss.sgi.com Fri Jul 13 01:23:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D8NaX00941 for linux-xfs-outgoing; Fri, 13 Jul 2001 01:23:36 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D8NZV00937 for ; Fri, 13 Jul 2001 01:23:35 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15KyEJ-0002wy-00 for linux-xfs@oss.sgi.com; Fri, 13 Jul 2001 09:23:19 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id JAA02610 for ; Fri, 13 Jul 2001 09:23:20 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f6D8NFV29973 for ; Fri, 13 Jul 2001 09:23:15 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Fri, 13 Jul 2001 09:23:15 +0100 (BST) From: "P.Dixon" To: Subject: benchmarks Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Any idea why xfs appears to be very much slower than reiserfs with these benchmarks: http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html Admittedly, the benchmarks were done by namesys... -- Paul ------------------------------------------------------------------------------- Paul Dixon Email: P.Dixon@qmw.ac.uk Department of Physics Phone: (020) 7882 5054 Queen Mary, University of London Fax : (020) 7882 5054 Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Jul 13 01:28:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D8SuL01204 for linux-xfs-outgoing; Fri, 13 Jul 2001 01:28:56 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D8SuV01200 for ; Fri, 13 Jul 2001 01:28:56 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id BAA00280 for ; Fri, 13 Jul 2001 01:26:21 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 SAA05238; Fri, 13 Jul 2001 18:27:28 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Simon Matter cc: ptb@it.uc3m.es, linux-xfs@oss.sgi.com Subject: Re: System locking: kernel-2.4.6pre3-xfs In-reply-to: Your message of "Fri, 13 Jul 2001 10:19:27 +0200." <3B4EAF0F.D98631AC@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 13 Jul 2001 18:27:28 +1000 Message-ID: <3497.995012848@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001 10:19:27 +0200, Simon Matter wrote: >Sorry, I thought it is the watchdog of a 'server managment card' >generating NMI's. Stupid question: what happens if for example Memory >Error Correction generates an NMI because it detected an error? They are distinguished by the presence of error codes in port 0x61. See arch/i386/kernel/traps.c, do_nmi(). From owner-linux-xfs@oss.sgi.com Fri Jul 13 01:31:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D8VsV01476 for linux-xfs-outgoing; Fri, 13 Jul 2001 01:31:54 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D8VqV01472 for ; Fri, 13 Jul 2001 01:31:52 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6D8Vme14230; Fri, 13 Jul 2001 10:31:50 +0200 Message-Id: <4.3.2.7.2.20010713102909.031ec4f0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 13 Jul 2001 10:31:36 +0200 To: "P.Dixon" , From: Seth Mos Subject: Re: benchmarks In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 09:23 13-7-2001 +0100, P.Dixon wrote: >Hello, > >Any idea why xfs appears to be very much slower than reiserfs with these >benchmarks: > >http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > >Admittedly, the benchmarks were done by namesys... I don't know what mount options were used. if you have enough memory and mount the fs with logbufs=8 or 4 it goes faster. use mkfs -t xfs -l size=32768b /dev/hdn to create a larger log for increased speed. In short, we know the fs was xfs but that is about it. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 13 01:41:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D8f9w02056 for linux-xfs-outgoing; Fri, 13 Jul 2001 01:41:09 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D8f7V02051 for ; Fri, 13 Jul 2001 01:41:07 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA20240; Fri, 13 Jul 2001 10:41:04 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA26324; Fri, 13 Jul 2001 10:41:04 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id ABA1857306; Fri, 13 Jul 2001 10:49:05 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 7BD4825835; Fri, 13 Jul 2001 10:57:03 +0200 (CEST) Message-ID: <3B4EB3D5.ED80FC6B@ch.sauter-bc.com> Date: Fri, 13 Jul 2001 10:39:49 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: "P.Dixon" Cc: linux-xfs@oss.sgi.com Subject: Re: benchmarks References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "P.Dixon" schrieb: > > Hello, > > Any idea why xfs appears to be very much slower than reiserfs with these > benchmarks: > > http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > > Admittedly, the benchmarks were done by namesys... Maybe we have to ask Mindcraft for serious benchmarks :-) ReiserFS is good in handling large amount of small files, specially deleting them goes fast. That's all about it. The overall performance in real life is allmost the same with both filesystems. Its only one spcific situation where ReiserFS is really faster, but compare recovery time of both filesystems after a crash, XFS shows some 100% better perfomance than ReiserFS! Forget about benchmarks, run your on real life test and compare and cpu usage. Simon > > -- > > Paul > > ------------------------------------------------------------------------------- > Paul Dixon Email: P.Dixon@qmw.ac.uk > Department of Physics Phone: (020) 7882 5054 > Queen Mary, University of London Fax : (020) 7882 5054 > Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd > ------------------------------------------------------------------------------- -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Fri Jul 13 02:39:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6D9dQK04629 for linux-xfs-outgoing; Fri, 13 Jul 2001 02:39:26 -0700 Received: from tiny.int.franksintl.nl (goblin.franksintl.nl [195.193.231.154]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6D9dNV04622 for ; Fri, 13 Jul 2001 02:39:24 -0700 Received: from ries (cp35.int.franksintl.nl [192.168.4.249]) by tiny.int.franksintl.nl (8.11.4/8.11.4/Debian 8.9.3-21) with ESMTP id f6D9TpD25735 for ; Fri, 13 Jul 2001 11:29:51 +0200 From: "Ries van Twisk" To: linux-xfs@oss.sgi.com Date: Fri, 13 Jul 2001 11:29:45 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: xfsdump-1.0.9 does not compile Reply-to: ries@franksintl.nl Message-ID: <3B4EDBA9.24773.A6B3765@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I was just buzy compiling xfsdump but it doesn't because of a error: ...../arch_xlate.c:67: undefined reference to '__fswab64' I checked the Linux libs and the __swab64 macro is there. What else could be wrong? Ries From owner-linux-xfs@oss.sgi.com Fri Jul 13 04:22:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DBMOq09434 for linux-xfs-outgoing; Fri, 13 Jul 2001 04:22:24 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DBMNV09430 for ; Fri, 13 Jul 2001 04:22:23 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id EAA07032 for ; Fri, 13 Jul 2001 04:22:13 -0700 (PDT) mail_from (mg@smack.melbourne.sgi.com) Received: from smack.melbourne.sgi.com (smack.melbourne.sgi.com [134.14.55.210]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id VAA05957; Fri, 13 Jul 2001 21:21:00 +1000 Received: from localhost (mg@localhost) by smack.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id VAA74416; Fri, 13 Jul 2001 21:21:00 +1000 (EST) Date: Fri, 13 Jul 2001 21:20:59 +1000 From: Mike Gigante To: Simon Matter cc: "P.Dixon" , linux-xfs@oss.sgi.com Subject: Re: benchmarks In-Reply-To: <3B4EB3D5.ED80FC6B@ch.sauter-bc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk XFS is pretty tuneable - so you could play with inode size, log size number of allocation groups etc to best suit your usage. Such tuning doesn't seem possible with ReiserFS ... The mongo benchmarks use relatively small files. XFS scales very well to large files/directories, but that benchmark sticks to small scale stuff. It *seems* to show ReiserFS in the best possible light and the XFS results don't seem to reflect anything like real world experience (except that it correctly highlights the relatively slow delete performance of XFS!) I gave an XFS talk to the local Linux users group a couple of weeks ago and in response to a discussion about performance and the Mongo benchmarks (after the talk), I have been running some comprehensive benchmarks and simulations (in my own time). I'll post my results in a week or two. when the whole suite is finished. All I'll say at this point is "interesting..." Mike ----------------------------------------------------------------------- Michael Gigante R&D Software Engineer mg@melbourne.sgi.com SGI Performance Tools Group, +61 3 9834 8233 Melbourne Australia V-Net: 524-8233 On Fri, 13 Jul 2001, Simon Matter wrote: > "P.Dixon" schrieb: > > > > Hello, > > > > Any idea why xfs appears to be very much slower than reiserfs with these > > benchmarks: > > > > http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > > > > Admittedly, the benchmarks were done by namesys... > > Maybe we have to ask Mindcraft for serious benchmarks :-) > > ReiserFS is good in handling large amount of small files, specially > deleting them goes fast. That's all about it. The overall performance > in real life is allmost the same with both filesystems. Its only > one spcific situation where ReiserFS is really faster, but compare > recovery time of both filesystems after a crash, XFS shows some 100% > better perfomance than ReiserFS! > > Forget about benchmarks, run your on real life test and > compare and cpu usage. > > Simon > > > > > -- > > > > Paul > > > > ------------------------------------------------------------------------------- > > Paul Dixon Email: P.Dixon@qmw.ac.uk > > Department of Physics Phone: (020) 7882 5054 > > Queen Mary, University of London Fax : (020) 7882 5054 > > Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd > > ------------------------------------------------------------------------------- > > -- > Simon Matter Tel: +41 61 695 57 35 > Fr.Sauter AG / CIT Fax: +41 61 695 53 30 > Im Surinam 55 > CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] > > > From owner-linux-xfs@oss.sgi.com Fri Jul 13 05:21:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DCLts11046 for linux-xfs-outgoing; Fri, 13 Jul 2001 05:21:55 -0700 Received: from dmz.tecosim.de ([194.24.222.241]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DCLoV11038 for ; Fri, 13 Jul 2001 05:21:50 -0700 Received: (from uucp@localhost) by dmz.tecosim.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) id f6DC7IN06628; Fri, 13 Jul 2001 14:07:18 +0200 Received: from ns.tecosim.de(194.24.222.9) via SMTP by dmz.tecosim.de, id smtpdYaXhxL; Fri Jul 13 14:07:08 2001 Received: from donner.tecosim.de (donner.tecosim.de [194.24.222.109]) by ns.tecosim.de (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id f6DCJMi19932; Fri, 13 Jul 2001 14:19:22 +0200 Received: (from leh@localhost) by donner.tecosim.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id f6DCJMv14912; Fri, 13 Jul 2001 14:19:22 +0200 Date: Fri, 13 Jul 2001 14:19:22 +0200 From: Utz Lehmann To: "P.Dixon" Cc: linux-xfs@oss.sgi.com Subject: Re: benchmarks Message-ID: <20010713141922.G3181@de.tecosim.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from P.Dixon@qmw.ac.uk on Fri, Jul 13, 2001 at 09:23:15AM +0100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi My experience with fs benchmarking is, that under different conditions the results are different (and another filesystem wins). Nearly almost fs benchmark have nothing todo with real life. They are run on a freshly formated partition and so on... For the reiser vs. xfs case just make following: - Format a partition - Fillup the partition with garbage, lots of differnet sized files and simultaneous write (just a few untars in parallel) - Delete some files - Repeat the last 2 steps a few times - After this, the filesystem should filled 97-99% including the comming benchmark - Run the benchmark My guess: xfs will outperform reiser (and every other linux fs) Then publish the results on a webpage with the headline "xfs is 10 times faster as reiserfs!" utz P.Dixon [P.Dixon@qmw.ac.uk] wrote: > Hello, > > Any idea why xfs appears to be very much slower than reiserfs with these > benchmarks: > > http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > > Admittedly, the benchmarks were done by namesys... > > -- > > Paul > > ------------------------------------------------------------------------------- > Paul Dixon Email: P.Dixon@qmw.ac.uk > Department of Physics Phone: (020) 7882 5054 > Queen Mary, University of London Fax : (020) 7882 5054 > Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd > ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Jul 13 06:08:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DD8AZ12922 for linux-xfs-outgoing; Fri, 13 Jul 2001 06:08:10 -0700 Received: from relay.dera.gov.uk (relay.dera.gov.uk [192.5.29.49]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DD89V12918 for ; Fri, 13 Jul 2001 06:08:09 -0700 Received: (qmail 812 invoked from network); 13 Jul 2001 14:06:31 +0100 Received: from syntax.dera.gov.uk (146.80.9.50) by relay.dera.gov.uk with SMTP; 13 Jul 2001 14:06:31 +0100 Subject: Re: [OT] XFS and FreeBSD? From: Tony Gale To: Gerald Henriksen Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <994931235.30682.6.camel@syntax.dera.gov.uk> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 13 Jul 2001 14:08:07 +0100 Message-Id: <995029687.29184.4.camel@syntax.dera.gov.uk> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I can't see SGI maintaining a MIPS platform for very long after they are up and running with IA64. They don't make enough profit to support two such platforms :-) -tony On 12 Jul 2001 10:59:00 -0400, Gerald Henriksen wrote: > On 12 Jul 2001 10:47:15 +0100, you wrote: > > >I reckon Irix will be dropped when SGI move to the IA64 platform. They'd > >be fools not to. > > SGI are not dropping MIPS/Irix. > > SGI is adding IA64/Linux to their product mix so that customers will > have a choice of either MIPS or IA64 solutions. > From owner-linux-xfs@oss.sgi.com Fri Jul 13 06:31:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DDVtO13661 for linux-xfs-outgoing; Fri, 13 Jul 2001 06:31:55 -0700 Received: from merlin.giref.ulaval.ca (postfix@merlin.giref.ulaval.ca [132.203.7.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DDVrV13657 for ; Fri, 13 Jul 2001 06:31:53 -0700 Received: from giref.ulaval.ca (roederer.giref.ulaval.ca [132.203.7.24]) by merlin.giref.ulaval.ca (Postfix) with ESMTP id 17CA12D488; Fri, 13 Jul 2001 09:31:52 -0400 (EDT) Message-ID: <3B4EF7F8.3C5C033D@giref.ulaval.ca> Date: Fri, 13 Jul 2001 09:30:32 -0400 From: Luc Lalonde X-Mailer: Mozilla 4.77 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Nathan Scott Cc: "linux-xfs@oss.sgi.com" Subject: Re: System locking: kernel-2.4.6pre3-xfs References: <3B4DA431.FB26BA96@giref.ulaval.ca> <10107131054.ZM208593@wobbly.melbourne.sgi.com> Content-Type: multipart/mixed; boundary="------------4D64486A82DADA669F115440" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------4D64486A82DADA669F115440 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Nathan Scott wrote: > Hello Nathan, I updated the kernel to 2.4.7-pre6-xfs. However, I got your message to include kdb after I had already done so. I decided to revert to the aic7xxx_old. I suspect that the new Apaptec drivers that have gone through a major overhaul are not up to snuff. My failures always occur when by backup is writting to tape (Amanda). The next time it crashes and I upgrade the kernel I'll include kdb. I too suspect that this is not XFS related. Cheers. > hi Luc, > > On Jul 12, 9:20am, Luc Lalonde wrote: > > Subject: System locking: kernel-2.4.6pre3-xfs > > > > Hello Folks, > > > > I'm seem to be having problems on my DELL PowerEdge 2400 running the XFS > > kernels. Every 10 days or so the systems locks and I have to reboot. > > ... > > I've been folllowing the XFS kernel development and have been trying > > updating since 2.4.2-XFS. > > Could you build a kernel with kdb enabled and dump the call > stack ("bt" command) when the system hangs? That would give > us a better idea as to whether or not your hang is related to > XFS, and a better starting point for debugging. > > It would also probably be worthwhile moving up to the current > development tree which is 2.4.7-pre6 based so that everyone is > looking at the same code when you do extract some debug info. > > thanks. > > -- > Nathan -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: llalonde@giref.ulaval.ca --------------4D64486A82DADA669F115440 Content-Type: text/x-vcard; charset=us-ascii; name="llalonde.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Luc Lalonde Content-Disposition: attachment; filename="llalonde.vcf" begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;;;;;; version:2.1 email;internet:llalonde@giref.ulaval.ca title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard --------------4D64486A82DADA669F115440-- From owner-linux-xfs@oss.sgi.com Fri Jul 13 07:24:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DEO7A15159 for linux-xfs-outgoing; Fri, 13 Jul 2001 07:24:07 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DEO6V15155 for ; Fri, 13 Jul 2001 07:24:06 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA22920 for ; Fri, 13 Jul 2001 07:23:56 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2422570; Fri, 13 Jul 2001 09:22:49 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id JAA48633; Fri, 13 Jul 2001 09:22:47 -0500 (CDT) Message-ID: <3B4F0457.CF4BABCA@sgi.com> Date: Fri, 13 Jul 2001 09:23:19 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "P.Dixon" CC: linux-xfs@oss.sgi.com Subject: Re: benchmarks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "P.Dixon" wrote: > > Hello, > > Any idea why xfs appears to be very much slower than reiserfs with these > benchmarks: > > http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > > Admittedly, the benchmarks were done by namesys... More than _done_ by namesys, but _written_ by namesys. [eric@stout eric]$ tar xvzf mongo.tar.gz [eric@stout eric]$ cd mongo_pl [eric@stout mongo_pl]$ more mongo.pl #!/usr/bin/perl # # Copyright 2000 by Hans Reiser, licensing governed by reiserfs/README # # # Mongo.pl is reiserfs benchmark. # ... I'm not saying that there's anything sinister going on here (really!) but when you have a benchmark suite written by the filesystem author, it's probably not the most objective test of other filesystems. I don't know the history of mongo, but I'd be willing to guess that it's designed to test reiserfs performance, to be used in reiserfs testing, and it may not be the best thing to compare various filesystems. Anybody want to do some independent iozone (or other benchmark) testing? -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 13 07:52:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DEqee15875 for linux-xfs-outgoing; Fri, 13 Jul 2001 07:52:40 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DEqcV15871 for ; Fri, 13 Jul 2001 07:52:38 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ3DM>; Fri, 13 Jul 2001 09:52:04 -0500 Message-ID: <85063BBE668FD411944400D0B744267A6433C6@AUSMAIL> From: "Gonyou, Austin" To: linux-xfs@oss.sgi.com Subject: Hello? Date: Fri, 13 Jul 2001 09:52:03 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Is this list alive? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:35:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFZGU18033 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:35:16 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFZEV18029 for ; Fri, 13 Jul 2001 08:35:15 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ3HP>; Fri, 13 Jul 2001 10:34:40 -0500 Message-ID: <85063BBE668FD411944400D0B744267A6433CD@AUSMAIL> From: "Gonyou, Austin" To: linux-xfs@oss.sgi.com Subject: Mounting XFS volumes with uid= or gid= or both Date: Fri, 13 Jul 2001 10:34:39 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've run into a bit of a problem when trying to mount a filesystem as uid or gid=xxx. I just get an error which basically says I don't know what options you're trying to give me. What am I doing wrong? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:42:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFgFL18397 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:42:15 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFgDV18392 for ; Fri, 13 Jul 2001 08:42:13 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ32H>; Fri, 13 Jul 2001 10:41:29 -0500 Message-ID: <85063BBE668FD411944400D0B744267A6433CF@AUSMAIL> From: "Gonyou, Austin" To: "Gonyou, Austin" , linux-xfs@oss.sgi.com Subject: Scripted CVS updates? Date: Fri, 13 Jul 2001 10:41:27 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm trying to script cvs updates with cron for once every couple of days, or once a week. But, I must provide a login password to the cvs server. Is there a way to do that easily? perhaps something like? cvs login<< EOF password EOF Thanks in advance. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:42:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFgTL18502 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:42:29 -0700 Received: from musuko.uchicago.edu (musuko.uchicago.edu [128.135.39.147]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFgSV18497 for ; Fri, 13 Jul 2001 08:42:28 -0700 Received: (from sl70@localhost) by musuko.uchicago.edu (8.11.2/8.11.2) id f6DFgNY06128; Fri, 13 Jul 2001 10:42:23 -0500 Message-ID: X-Mailer: XFMail 1.5.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4.3.2.7.2.20010713102909.031ec4f0@pop.xs4all.nl> Date: Fri, 13 Jul 2001 10:42:23 -0500 (CDT) Reply-To: s-luppescu@uchicago.edu Organization: Univ of Chicago From: s-luppescu@uchicago.edu To: Seth Mos Subject: Re: benchmarks Cc: linux-xfs@oss.sgi.com, "P.Dixon" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 13-Jul-2001 Seth Mos wrote: > At 09:23 13-7-2001 +0100, P.Dixon wrote: >>Hello, >> >>Any idea why xfs appears to be very much slower than reiserfs with these >>benchmarks: >> >>http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html >> >>Admittedly, the benchmarks were done by namesys... > > I don't know what mount options were used. > if you have enough memory and mount the fs with logbufs=8 or 4 it goes > faster. > use mkfs -t xfs -l size=32768b /dev/hdn to create a larger log for > increased speed. This is very interesting, but as I've already made my filesystem (and don't relish the thought of wiping it out and doing it over again) the option on mkfs is not useful to me. But I might be able to use the logbufs option. Do I just put it in my /etc/fstab file and then reboot? How much memory is ``enough''? How do I tell how many log buffers I've got at present? Thanks. ______________________________________________________________________ Stuart Luppescu -=-=- University of Chicago $(B:MJ8$HCRF`H~$NIc(B -=-=- s-luppescu@uchicago.edu http://www.consortium-chicago.org/people/sl.html http://musuko.uchicago.edu/pubkey.asc for PGP Public Key ICQ #21172047 AIM: psycho7070 Imagination is the one weapon in the war against reality. -- Jules de Gaultier >> Sent on 13-Jul-2001 at 10:40:03 with xfmail From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:46:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFkZa18790 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:46:35 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFkYV18786 for ; Fri, 13 Jul 2001 08:46:34 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.2/8.11.2) with ESMTP id f6DFkQ412062; Fri, 13 Jul 2001 11:46:26 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Fri, 13 Jul 2001 11:46:26 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: "Gonyou, Austin" cc: Subject: Re: Mounting XFS volumes with uid= or gid= or both In-Reply-To: <85063BBE668FD411944400D0B744267A6433CD@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001 at 10:34am, Gonyou, Austin wrote > I've run into a bit of a problem when trying to mount a filesystem as uid or > gid=xxx. I just get an error which basically says I don't know what options > you're trying to give me. What am I doing wrong? Those options aren't supported by XFS. For a list of options specific to XFS, look in Documentation/filesystems/xfs.txt in your linux source tree. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:50:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFoBb19048 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:50:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFoAV19044 for ; Fri, 13 Jul 2001 08:50:10 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA02790 for ; Fri, 13 Jul 2001 08:50:10 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2424516; Fri, 13 Jul 2001 10:48:52 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA16563; Fri, 13 Jul 2001 10:48:52 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DFogU08171; Fri, 13 Jul 2001 10:50:42 -0500 Message-Id: <200107131550.f6DFogU08171@jen.americas.sgi.com> To: s-luppescu@uchicago.edu cc: Seth Mos , linux-xfs@oss.sgi.com, "P.Dixon" Subject: Re: benchmarks References: Comments: In-reply-to s-luppescu@uchicago.edu message dated "Fri, 13 Jul 2001 10:42:23 -0500." Date: Fri, 13 Jul 2001 10:50:42 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On 13-Jul-2001 Seth Mos wrote: > > At 09:23 13-7-2001 +0100, P.Dixon wrote: > >>Hello, > >> > >>Any idea why xfs appears to be very much slower than reiserfs with these > >>benchmarks: > >> > >>http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > >> > >>Admittedly, the benchmarks were done by namesys... > > > > I don't know what mount options were used. > > if you have enough memory and mount the fs with logbufs=8 or 4 it goes > > faster. > > use mkfs -t xfs -l size=32768b /dev/hdn to create a larger log for > > increased speed. > > This is very interesting, but as I've already made my filesystem (and don't > relish the thought of wiping it out and doing it over again) the option on mk > fs > is not useful to me. But I might be able to use the logbufs option. Do I just > put it in my /etc/fstab file and then reboot? How much memory is ``enough''? > How do I tell how many log buffers I've got at present? > An external log is growable, an internal one unfortunately is not, and we keep kicking SGI support people who build multi-terabyte filesystems without reading the man page. Unless you specified otherwise you have two logbufs, all you need to do to get the number changed is remount with the new option, so yes, edit fstab and reboot. If you use O_SYNC anywhere then osyncisdsync as a mount option will make xfs O_SYNC behave more like other linux filesystems. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:50:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFotY19189 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:50:55 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DForV19176 for ; Fri, 13 Jul 2001 08:50:53 -0700 Received: (qmail 28659 invoked by uid 8); 13 Jul 2001 15:50:52 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: Scripted CVS updates? Date: Fri, 13 Jul 2001 15:50:51 +0000 (UTC) Organization: spoiled dot org Lines: 19 Distribution: local Message-ID: References: <85063BBE668FD411944400D0B744267A6433CF@AUSMAIL> X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Gonyou, Austin" wrote: > I'm trying to script cvs updates with cron for once every couple of days, or > once a week. But, I must provide a login password to the cvs server. Is > there a way to do that easily? perhaps something like? > > cvs login<< EOF > password > > EOF Unless you don't checkout the complete tree over and over again you just have to supply the password on the first initial checkout. All following updates should run without the password. Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:50:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFosm19185 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:50:54 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DForV19177 for ; Fri, 13 Jul 2001 08:50:53 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ3JN>; Fri, 13 Jul 2001 10:50:20 -0500 Message-ID: <85063BBE668FD411944400D0B744267A6433D0@AUSMAIL> From: "Gonyou, Austin" To: "'Joshua Baker-LePain'" , "Gonyou, Austin" Cc: linux-xfs@oss.sgi.com Subject: RE: Mounting XFS volumes with uid= or gid= or both Date: Fri, 13 Jul 2001 10:50:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk That's what I was afraid of. OK, Thanks for the info. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Joshua Baker-LePain [mailto:jlb17@duke.edu] > Sent: Friday, July 13, 2001 10:46 AM > To: Gonyou, Austin > Cc: linux-xfs@oss.sgi.com > Subject: Re: Mounting XFS volumes with uid= or gid= or both > > > On Fri, 13 Jul 2001 at 10:34am, Gonyou, Austin wrote > > > I've run into a bit of a problem when trying to mount a > filesystem as uid or > > gid=xxx. I just get an error which basically says I don't > know what options > > you're trying to give me. What am I doing wrong? > > Those options aren't supported by XFS. For a list of options > specific to > XFS, look in Documentation/filesystems/xfs.txt in your linux > source tree. > > -- > Joshua Baker-LePain > Department of Biomedical Engineering > Duke University > From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:53:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFrJh19462 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:53:19 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFrIV19456 for ; Fri, 13 Jul 2001 08:53:18 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ3JY>; Fri, 13 Jul 2001 10:52:36 -0500 Message-ID: <85063BBE668FD411944400D0B744267A6433D1@AUSMAIL> From: "Gonyou, Austin" To: "'linux-xfs@oss.sgi.com'" Subject: RE: Scripted CVS updates? Date: Fri, 13 Jul 2001 10:52:35 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Normally that's what I thought, but for some reason, probably a screwed up CVS/Root file, I was unable to do that a couple of times. I do this with apache, and it's all good. :) Ok..I'll go about my business normally then. :) -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Juri Haberland [mailto:list-linux.sgi.xfs@spoiled.org] > Sent: Friday, July 13, 2001 10:51 AM > To: linux-xfs@oss.sgi.com > Subject: Re: Scripted CVS updates? > > > "Gonyou, Austin" wrote: > > I'm trying to script cvs updates with cron for once every > couple of days, or > > once a week. But, I must provide a login password to the > cvs server. Is > > there a way to do that easily? perhaps something like? > > > > cvs login<< EOF > > password > > > > EOF > > Unless you don't checkout the complete tree over and over > again you just > have to supply the password on the first initial checkout. > All following updates should run without the password. > > Juri > > -- > Juri Haberland > From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:53:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFri019579 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:53:44 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFrhV19573 for ; Fri, 13 Jul 2001 08:53:43 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA08714 for ; Fri, 13 Jul 2001 08:53:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2402352; Fri, 13 Jul 2001 10:52:25 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA89673; Fri, 13 Jul 2001 10:52:25 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DFsFa08205; Fri, 13 Jul 2001 10:54:15 -0500 Message-Id: <200107131554.f6DFsFa08205@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Gonyou, Austin" cc: linux-xfs@oss.sgi.com Subject: Re: Scripted CVS updates? In-Reply-To: Message from "Gonyou, Austin" of "Fri, 13 Jul 2001 10:41:27 CDT." <85063BBE668FD411944400D0B744267A6433CF@AUSMAIL> Date: Fri, 13 Jul 2001 10:54:15 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I'm trying to script cvs updates with cron for once every couple of days, or > once a week. But, I must provide a login password to the cvs server. Is > there a way to do that easily? perhaps something like? > > cvs login<< EOF > password > > EOF > I just cd into the cvs directory and run cvs update -d . no need for a password or anything else. Steve > Thanks in advance. > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Fri Jul 13 08:57:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DFv3G19797 for linux-xfs-outgoing; Fri, 13 Jul 2001 08:57:03 -0700 Received: from crdras.crd.ge.COM (crdras.crd.GE.COM [192.35.44.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DFv2V19793 for ; Fri, 13 Jul 2001 08:57:02 -0700 Received: from crdras.crd.ge.COM (localhost [127.0.0.1]) by crdras.crd.ge.COM (18xxx/8.9.3/8.9.3) with ESMTP id LAA00017 for ; Fri, 13 Jul 2001 11:57:01 -0400 (EDT) Received: from crdns.crd.ge.com (crdns [3.1.7.107]) by crdras.crd.ge.COM (25/8.9.3/8.9.3) with ESMTP id LAA00013 for ; Fri, 13 Jul 2001 11:57:00 -0400 (EDT) Received: from elmo (elmo.crd.ge.com [3.1.220.7]) by crdns.crd.ge.com (8.9.3/8.9.3) with ESMTP id LAA05863 for ; Fri, 13 Jul 2001 11:57:02 -0400 (EDT) Date: Fri, 13 Jul 2001 11:56:30 -0400 (EDT) From: Mark Tucker X-X-Sender: Reply-To: Mark Tucker To: Subject: XFS kernel problem with lilo Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have recently downloaded the Redhat SMP kernel pacakages (rpm) and xfs tools from oss.sgi.com. The packages installed without error. I created a ramdisk image from the new kernel and updated lilo with the following lines: image=/boot/vmlinux-2.4.2-SGI_XFS_1.0smp label=xfs initrd=/boot/initrd-2.4.2-SGI_XFS_1.0smp.img read-only root=/dev/sda8 append="hdc=ide-scsi" When I run lilo, I get the following output: [root@generic /boot]# lilo -t Added linux * Added linux-up Fatal: Kernel /boot/vmlinux-2.4.2-SGI_XFS_1.0smp is too big So far, I have not been able to work around this problem. The system is a dual P4 Xeon with 2GB RAM and 18GB ultra-3 scsi disk. Currently it is running Redhat 7.1 with the stock smp kernel. Any assistance with this will be appreciated. -- Mark Tucker GE Corporate Research and Development Unix Systems Consultant Logic Technology Inc. 518-387-6594 From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:02:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DG2c720221 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:02:38 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DG2aV20217 for ; Fri, 13 Jul 2001 09:02:37 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA04597 for ; Fri, 13 Jul 2001 09:02:27 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2425153; Fri, 13 Jul 2001 11:01:20 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA51197; Fri, 13 Jul 2001 11:01:20 -0500 (CDT) Message-ID: <3B4F1B6F.943C8889@sgi.com> Date: Fri, 13 Jul 2001 11:01:51 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Mark Tucker CC: linux-xfs@oss.sgi.com Subject: Re: XFS kernel problem with lilo References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Mark Tucker wrote: > When I run lilo, I get the following output: > > [root@generic /boot]# lilo -t > Added linux * > Added linux-up > Fatal: Kernel /boot/vmlinux-2.4.2-SGI_XFS_1.0smp is too big Use /boot/vmlinuz-2.4.2-SGI_XFS_1.0smp ^ not vmlinux... you might want to grab the 1.0.1 kernel as well, 1.0 is somewhat ancient at this point... -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:03:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DG3vi20318 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:03:57 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DG3uV20313 for ; Fri, 13 Jul 2001 09:03:56 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.2/8.11.2) with ESMTP id f6DG3mt12096; Fri, 13 Jul 2001 12:03:48 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Fri, 13 Jul 2001 12:03:48 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: Mark Tucker cc: Subject: Re: XFS kernel problem with lilo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001 at 11:56am, Mark Tucker wrote > image=/boot/vmlinux-2.4.2-SGI_XFS_1.0smp ^ That's the uncompressed image. You need to use vmlinuz. Oh, and you should probably grab the 1.0.1 release -- there have been a lot of fixes. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:04:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DG4q820422 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:04:52 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DG4pV20418 for ; Fri, 13 Jul 2001 09:04:51 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA04858 for ; Fri, 13 Jul 2001 09:04:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2421956; Fri, 13 Jul 2001 11:01:14 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA70935; Fri, 13 Jul 2001 11:01:14 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DG35p08259; Fri, 13 Jul 2001 11:03:05 -0500 Message-Id: <200107131603.f6DG35p08259@jen.americas.sgi.com> To: Mark Tucker cc: linux-xfs@oss.sgi.com Subject: Re: XFS kernel problem with lilo References: Comments: In-reply-to Mark Tucker message dated "Fri, 13 Jul 2001 11:56:30 -0400." Date: Fri, 13 Jul 2001 11:03:05 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > I have recently downloaded the Redhat SMP kernel pacakages (rpm) and xfs > tools from oss.sgi.com. The packages installed without error. I created a > ramdisk image from the new kernel and updated lilo with the following > lines: > > image=/boot/vmlinux-2.4.2-SGI_XFS_1.0smp > label=xfs > initrd=/boot/initrd-2.4.2-SGI_XFS_1.0smp.img > read-only > root=/dev/sda8 > append="hdc=ide-scsi" > > > When I run lilo, I get the following output: > > [root@generic /boot]# lilo -t > Added linux * > Added linux-up > Fatal: Kernel /boot/vmlinux-2.4.2-SGI_XFS_1.0smp is too big > > So far, I have not been able to work around this problem. > > The system is a dual P4 Xeon with 2GB RAM and 18GB ultra-3 scsi disk. > Currently it is running Redhat 7.1 with the stock smp kernel. > > Any assistance with this will be appreciated. First of all your timing was bad - 1.0.1 just came out, so there is a much more recent kernel out there in rpm format now. Secondly, you need to point lilo at the vmlinuz version of this file not the vmlinux version. Steve > > -- > Mark Tucker > GE Corporate Research and Development > Unix Systems Consultant > Logic Technology Inc. > 518-387-6594 From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:19:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DGJOe20808 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:19:24 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DGJMV20803 for ; Fri, 13 Jul 2001 09:19:22 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id JAA08317 for ; Fri, 13 Jul 2001 09:16:50 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2423414 for ; Fri, 13 Jul 2001 11:18:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA15637 for ; Fri, 13 Jul 2001 11:18:06 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DGJuw08383; Fri, 13 Jul 2001 11:19:56 -0500 Message-Id: <200107131619.f6DGJuw08383@jen.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: migrating from internal to external logs Date: Fri, 13 Jul 2001 11:19:56 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I just came up with this sequence for moving a filesystem with a small internal log to one with a larger external log. I have not tested it, and you should not test it without using a dummy partition. Steve ------- Forwarded Message Date: Fri, 13 Jul 2001 11:15:25 -0500 From: Steve Lord To: utz lehmann cc: Steve Lord Subject: Re: benchmarks > Hi Steve > > Steve Lord [lord@sgi.com] wrote: > > An external log is growable, an internal one unfortunately is not, and > > we keep kicking SGI support people who build multi-terabyte filesystems > > without reading the man page. > > Is it possible to switch an existing filesystem from internal to external > log? And maybe back? > > > utz You would need to format another partition with the correct log information, probably by using dd to get the original log out of the filesystem. Then take mount the filesystem with the mount option for the external log, then grow the log with xfs_growfs. In order to find the log on an existing filesystem do this: xfs_db /dev/hdc4 xfs_db: sb 0 xfs_db: print magicnum = 0x58465342 blocksize = 4096 dblocks = 1892898 rblocks = 0 rextents = 0 uuid = 0cf3fdce-8924-40c1-8fb5-6a8a0f137caa logstart = 1048580 rootino = 128 rbmino = 129 rsumino = 130 rextsize = 16 agblocks = 236613 agcount = 8 rbmblocks = 0 logblocks = 4096 versionnum = 0x2084 sectsize = 512 inodesize = 256 inopblock = 16 fname = "\000\000\000\000\000\000\000\000\000\000\000\000" blocklog = 12 sectlog = 9 inodelog = 8 inopblog = 4 agblklog = 18 rextslog = 0 inprogress = 0 imax_pct = 25 icount = 46080 ifree = 231 fdblocks = 1334163 frextents = 0 uquotino = 0 gquotino = 0 qflags = 0 flags = 0 shared_vn = 0 inoalignmt = 2 unit = 0 width = 0 dirblklog = 0 There is a logstart field in there and a logblocks, both are in filesystem block size units. You will need to modify the logstart field to zero before mounting the external log, for this you need the -x option on xfs_db to enable write mode. After printing out the superblock like this you would use this command: write logstart 0 To reset it. I have not tested any of this, you should definitely not do it on a filesystem you really want to keep. Going backwards would be possible, but you need to remember the original value for logstart and logblocks and reset them. Steve p.s. clean unmounts only, do not attempt this after a crash! ------- End of Forwarded Message From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:21:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DGLua20947 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:21:56 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DGLsV20943 for ; Fri, 13 Jul 2001 09:21:54 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15L5hO-00078u-00 for linux-xfs@oss.sgi.com; Fri, 13 Jul 2001 17:21:50 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id RAA08917 for ; Fri, 13 Jul 2001 17:21:51 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f6DGLpP00780 for ; Fri, 13 Jul 2001 17:21:51 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Fri, 13 Jul 2001 17:21:51 +0100 (BST) From: "P.Dixon" To: Subject: Re: benchmarks In-Reply-To: <200107131550.f6DFogU08171@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > I don't know what mount options were used. > This page is a bit more enlightening: http://www.linuxgazette.com/issue68/dellomodarme.html ...but the conclusions are all wrong. For files that are between 100 bytes and 1000 bytes (i.e. very small) ReiserFS does indeed look good. However, when you get to 10000 bytes (which is still small), xfs and ReiserFS are scoring about the same. If we extrapolate to larger file sizes, it's clear that xfs will be faster - which explains why in the real world (when you're usually manipulationg files much bigger tha 10K), xfs feels every bit as fast as the ext2 file system I was using before (if not faster). And when you consider how nice xfsdump and the other xfs tools are, the logical conclusion is that xfs wins out. I'm just happy that I now have a journaling filesytem with mature tools to go with it. Cheerio, Paul From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:24:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DGOUQ21159 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:24:30 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DGOTV21152 for ; Fri, 13 Jul 2001 09:24:29 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.2/8.11.2) id f6DGOLA25149; Fri, 13 Jul 2001 12:24:21 -0400 Date: Fri, 13 Jul 2001 12:24:21 -0400 From: Alan Eldridge To: "Gonyou, Austin" Cc: SGI XFS Dev List Subject: Re: Scripted CVS updates? Message-ID: <20010713122421.A25142@wwweasel.geeksrus.net> References: <85063BBE668FD411944400D0B744267A6433CF@AUSMAIL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <85063BBE668FD411944400D0B744267A6433CF@AUSMAIL>; from austin@coremetrics.com on Fri, Jul 13, 2001 at 10:41:27AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 13, 2001 at 10:41:27AM -0500, Gonyou, Austin wrote: >I'm trying to script cvs updates with cron for once every couple of days, or >once a week. But, I must provide a login password to the cvs server. Is >there a way to do that easily? perhaps something like? > >cvs login<< EOF >password > >EOF You should only have to do the "cvs login" magic once. Then do your initial checkout, using -dserver-address or with CVSROOT set to the appropriate value. After that, cvs update will "just work" for you. So just do it manually one time to "prime the pump", and off you go. -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Fri Jul 13 09:36:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DGa3821391 for linux-xfs-outgoing; Fri, 13 Jul 2001 09:36:03 -0700 Received: from crdras.crd.ge.COM (crdras.crd.GE.COM [192.35.44.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DGa1V21386 for ; Fri, 13 Jul 2001 09:36:01 -0700 Received: from crdras.crd.ge.COM (localhost [127.0.0.1]) by crdras.crd.ge.COM (18xxx/8.9.3/8.9.3) with ESMTP id MAA02206 for ; Fri, 13 Jul 2001 12:36:00 -0400 (EDT) Received: from crdns.crd.ge.com (crdns [3.1.7.107]) by crdras.crd.ge.COM (25/8.9.3/8.9.3) with ESMTP id MAA02199; Fri, 13 Jul 2001 12:35:58 -0400 (EDT) Received: from elmo (elmo.crd.ge.com [3.1.220.7]) by crdns.crd.ge.com (8.9.3/8.9.3) with ESMTP id MAA09031; Fri, 13 Jul 2001 12:36:00 -0400 (EDT) Date: Fri, 13 Jul 2001 12:35:29 -0400 (EDT) From: Mark Tucker X-X-Sender: Reply-To: Mark Tucker To: Joshua Baker-LePain cc: , Steve Lord , Eric Sandeen Subject: Re: XFS kernel problem with lilo In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > image=/boot/vmlinux-2.4.2-SGI_XFS_1.0smp > ^ > > That's the uncompressed image. You need to use vmlinuz. Thanks to all who pointed that out, it should have been obvious. I now have a working 1.0 kernel. > Oh, and you should probably grab the 1.0.1 release -- there have been a > lot of fixes. I'm in the middle of downloading it now. -- Mark Tucker GE Corporate Research and Development Unix Systems Consultant Logic Technology Inc. 518-387-6594 From owner-linux-xfs@oss.sgi.com Fri Jul 13 10:03:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DH3uB21897 for linux-xfs-outgoing; Fri, 13 Jul 2001 10:03:56 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DH3sV21893 for ; Fri, 13 Jul 2001 10:03:54 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15L6Lz-0002zX-00; Fri, 13 Jul 2001 19:03:47 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6DH3ea03290; Fri, 13 Jul 2001 13:03:40 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: ThH Cc: linux-xfs@oss.sgi.com Subject: Re: Installer for RH7.1 Alpha References: <994829414.5286.0.camel@pcli0001.doppstadt-sbk.de> <994915602.9631.0.camel@pcli0001.doppstadt-sbk.de> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 13 Jul 2001 13:03:40 -0400 In-Reply-To: <994915602.9631.0.camel@pcli0001.doppstadt-sbk.de> Message-ID: Lines: 14 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "ThH" == ThH writes: ThH> OK, that's clear. But what's with the stuff around the the RPMS ThH> to have a bootable installer? I'm working on it. Currently modifying our iso build system to work on Alpha. Barring problems, I should have a test iso out later today. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Jul 13 10:18:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DHIPD22269 for linux-xfs-outgoing; Fri, 13 Jul 2001 10:18:25 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DHINV22265 for ; Fri, 13 Jul 2001 10:18:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id KAA15739 for ; Fri, 13 Jul 2001 10:18:13 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2420746 for ; Fri, 13 Jul 2001 12:17:05 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA08177 for ; Fri, 13 Jul 2001 12:17:05 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DHIsT08622; Fri, 13 Jul 2001 12:18:54 -0500 Message-Id: <200107131718.f6DHIsT08622@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-xfs@oss.sgi.com Subject: Re: migrating from internal to external logs In-Reply-To: Message from Steve Lord of "Fri, 13 Jul 2001 11:19:56 CDT." <200107131619.f6DGJuw08383@jen.americas.sgi.com> Date: Fri, 13 Jul 2001 12:18:54 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Of course the thing I missed is that if you run growfs to grow a log it comes back and says: xfs_growfs: log growth not supported yet xfs_db also has some endian issues with the write command. I did however manage to grow a log: 1. select your partition to become the log and dd a bunch of zeros over the complete range you want to be the log, so 32768 blocks would be: dd if=/dev/zero of=/dev/XXX bs=32768 count=4096 2. run xfs_db -x on the original unmounted filesystem use sb 0 to get to the super block. 3. reset the log offset using write logstart 0 4. set the new log size using write logblocks xxxx where xxxx is the size in 4K blocks, xfs_db will come out with a new value which is different than this, feed this new value back into the same command and it will report the correct version. This is the endian conversion bug in xfs_db: xfs_db: write logblocks 32768 logblocks = 8388608 xfs_db: write logblocks 8388608 logblocks = 32768 5. mount the filesystem using the logdev option to point at the new log: mount -t xfs -o logbufs=4,osyncisdsync,logdev=/dev/sda6 /dev/sda5 /xfs You now have a filesystem with a new external log. Going back is harder since you need to zero the old log and reset the logstart and logblocks fields. It does occur to me that by using a different logstart than zero you could put two external logs on the same partition, not sure what happens with the device open close logic if you do this though. Steve > > I just came up with this sequence for moving a filesystem with a small > internal log to one with a larger external log. I have not tested it, and you > should not test it without using a dummy partition. > > Steve > > ------- Forwarded Message > > Date: Fri, 13 Jul 2001 11:15:25 -0500 > From: Steve Lord > To: utz lehmann > cc: Steve Lord > Subject: Re: benchmarks > > > Hi Steve > > > > Steve Lord [lord@sgi.com] wrote: > > > An external log is growable, an internal one unfortunately is not, and > > > we keep kicking SGI support people who build multi-terabyte filesystems > > > without reading the man page. > > > > Is it possible to switch an existing filesystem from internal to external > > log? And maybe back? > > > > > > utz > > You would need to format another partition with the correct log information, > probably by using dd to get the original log out of the filesystem. Then > take mount the filesystem with the mount option for the external log, > then grow the log with xfs_growfs. In order to find the log on an existing > filesystem do this: > > xfs_db /dev/hdc4 > xfs_db: sb 0 > xfs_db: print > magicnum = 0x58465342 > blocksize = 4096 > dblocks = 1892898 > rblocks = 0 > rextents = 0 > uuid = 0cf3fdce-8924-40c1-8fb5-6a8a0f137caa > logstart = 1048580 > rootino = 128 > rbmino = 129 > rsumino = 130 > rextsize = 16 > agblocks = 236613 > agcount = 8 > rbmblocks = 0 > logblocks = 4096 > versionnum = 0x2084 > sectsize = 512 > inodesize = 256 > inopblock = 16 > fname = "\000\000\000\000\000\000\000\000\000\000\000\000" > blocklog = 12 > sectlog = 9 > inodelog = 8 > inopblog = 4 > agblklog = 18 > rextslog = 0 > inprogress = 0 > imax_pct = 25 > icount = 46080 > ifree = 231 > fdblocks = 1334163 > frextents = 0 > uquotino = 0 > gquotino = 0 > qflags = 0 > flags = 0 > shared_vn = 0 > inoalignmt = 2 > unit = 0 > width = 0 > dirblklog = 0 > > There is a logstart field in there and a logblocks, both are in filesystem > block size units. You will need to modify the logstart field to zero before > mounting the external log, for this you need the -x option on xfs_db to > enable write mode. After printing out the superblock like this you would > use this command: > > write logstart 0 > > To reset it. > > I have not tested any of this, you should definitely not do it on a > filesystem you really want to keep. > > Going backwards would be possible, but you need to remember the original > value for logstart and logblocks and reset them. > > Steve > > p.s. clean unmounts only, do not attempt this after a crash! > > > ------- End of Forwarded Message From owner-linux-xfs@oss.sgi.com Fri Jul 13 10:21:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DHL1722406 for linux-xfs-outgoing; Fri, 13 Jul 2001 10:21:01 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DHL0V22402 for ; Fri, 13 Jul 2001 10:21:00 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6DHKwNe049434; Fri, 13 Jul 2001 12:20:58 -0500 (CDT) Message-ID: <3B4F2DD2.10306@thebarn.com> Date: Fri, 13 Jul 2001 12:20:18 -0500 From: cattelan@thebarn.com User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686; en-US; rv:0.9.1) Gecko/20010609 X-Accept-Language: en-us MIME-Version: 1.0 To: "Gonyou, Austin" CC: linux-xfs@oss.sgi.com Subject: Re: Scripted CVS updates? References: <85063BBE668FD411944400D0B744267A6433CF@AUSMAIL> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Gonyou, Austin wrote: >I'm trying to script cvs updates with cron for once every couple of days, or >once a week. But, I must provide a login password to the cvs server. Is >there a way to do that easily? perhaps something like? > > Encrypted passwd phrases are stored in ~/.cvspass after the first vaild login... so unless cvs can not write to that file the login process should only have to be done once. Note CVSUP is probably a better option for auto updates .... much faster also. http://oss.sgi.com/projects/xfs/cvsup.html > > From owner-linux-xfs@oss.sgi.com Fri Jul 13 10:25:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DHPYN22543 for linux-xfs-outgoing; Fri, 13 Jul 2001 10:25:34 -0700 Received: from postfix2-1.free.fr (postfix2-1.free.fr [213.228.0.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DHPWV22539 for ; Fri, 13 Jul 2001 10:25:33 -0700 Received: from lucas.loria (strasbourg-2-a7-50-125.dial.proxad.net [212.27.50.125]) by postfix2-1.free.fr (Postfix) with ESMTP id 4A3BCC177 for ; Fri, 13 Jul 2001 19:25:30 +0200 (CEST) Received: by lucas.loria (Postfix, from userid 500) id 0A9CDA8E8; Fri, 13 Jul 2001 18:48:01 +0200 (CEST) Date: Fri, 13 Jul 2001 18:48:01 +0200 From: Vincent Bernat To: linux-xfs@oss.sgi.com Subject: LVM status Message-ID: <20010713184801.D4738@lucas.loria> 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.2.5i X-PGP-KeyID: 0xF22A794E X-PGP-Fingerprint: 5854 AF2B 65B2 0E96 2161 E32B 285B D7A1 F22A 794E Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am a bit disappointed with LVM status with XFS. The FAQ states only LVM 0.7 must work. However, there are here various people using latest LVM beta with latest XFS. I have read that LVM status will be fixed when the 1.0 will be out. This release will happen in a week or a little more. After the release of LVM 1.0, how much time will elapse until an "LVM-compliant" XFS be released (as a patch, like current snapshots). One week ? Two weeks ? More ? Regards, From owner-linux-xfs@oss.sgi.com Fri Jul 13 10:35:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DHZ8j22802 for linux-xfs-outgoing; Fri, 13 Jul 2001 10:35:08 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DHZ6V22798 for ; Fri, 13 Jul 2001 10:35:06 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA07829 for ; Fri, 13 Jul 2001 10:32:33 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2415805; Fri, 13 Jul 2001 12:33:46 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA28590; Fri, 13 Jul 2001 12:33:46 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DHZae08718; Fri, 13 Jul 2001 12:35:36 -0500 Message-Id: <200107131735.f6DHZae08718@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Vincent Bernat cc: linux-xfs@oss.sgi.com Subject: Re: LVM status In-Reply-To: Message from Vincent Bernat of "Fri, 13 Jul 2001 18:48:01 +0200." <20010713184801.D4738@lucas.loria> Date: Fri, 13 Jul 2001 12:35:35 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I am a bit disappointed with LVM status with XFS. The FAQ states only > LVM 0.7 must work. However, there are here various people using latest > LVM beta with latest XFS. I have read that LVM status will be fixed > when the 1.0 will be out. This release will happen in a week or a little > more. > > After the release of LVM 1.0, how much time will elapse until an > "LVM-compliant" XFS be released (as a patch, like current snapshots). > One week ? Two weeks ? More ? > Regards, LVM development has tended to be rather unpredictable, and there have been some 'interesting' versions of LVM which kernel people have screamed about. LVM 1.0 has also been 1 week from release for several weeks now. So we have stayed put on a working version of LVM and we will revisit the issue when 1.0 finally comes out. Attempting to keep track of the LVM development and mainline kernel development at the same time is more than I want to attempt right now. Heinz has also stated on a couple of occasions that he will not take patches for making LVM work with XFS until post 1.0 - and this is the direction the patches (if any) will have to flow. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 13 10:37:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DHbGU22921 for linux-xfs-outgoing; Fri, 13 Jul 2001 10:37:16 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DHbGV22917 for ; Fri, 13 Jul 2001 10:37:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA01831 for ; Fri, 13 Jul 2001 10:34:42 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2425716; Fri, 13 Jul 2001 12:35:58 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA69293; Fri, 13 Jul 2001 12:35:57 -0500 (CDT) Message-ID: <3B4F319C.391BD31B@sgi.com> Date: Fri, 13 Jul 2001 12:36:28 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Vincent Bernat CC: linux-xfs@oss.sgi.com Subject: Re: LVM status References: <20010713184801.D4738@lucas.loria> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Vincent Bernat wrote: > > I am a bit disappointed with LVM status with XFS. The FAQ states only > LVM 0.7 must work. However, there are here various people using latest > LVM beta with latest XFS. I have read that LVM status will be fixed > when the 1.0 will be out. This release will happen in a week or a little > more. The latest LVM (0.9.1-beta7) is broken (according to Martin) and our tree is at 0.9.1-beta6 - which works. > After the release of LVM 1.0, how much time will elapse until an > "LVM-compliant" XFS be released (as a patch, like current snapshots). > One week ? Two weeks ? More ? XFS is "LVM compliant" today, several people are running with it. I imagine that when LVM 1.0 comes out, we'll do some testing and get it in our tree without too much delay. But of course that's pure speculation at this point... -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 13 11:44:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DIiYD24193 for linux-xfs-outgoing; Fri, 13 Jul 2001 11:44:34 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DIiXV24189 for ; Fri, 13 Jul 2001 11:44:33 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ36L>; Fri, 13 Jul 2001 13:43:59 -0500 Message-ID: <85063BBE668FD411944400D0B744267A6433E2@AUSMAIL> From: "Gonyou, Austin" To: "'linux-xfs@oss.sgi.com'" Subject: RE: Mounting XFS volumes with uid= or gid= or both Date: Fri, 13 Jul 2001 13:43:58 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Could chacl possibly be used to force files to be written as a specific UID/GID? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Fri Jul 13 11:53:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DIruu24510 for linux-xfs-outgoing; Fri, 13 Jul 2001 11:53:56 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DIrqV24491 for ; Fri, 13 Jul 2001 11:53:52 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 681EB166; Sat, 14 Jul 2001 02:53:47 +0800 (PHT) Received: from 192.168.0.90 ( [192.168.0.90]) as user jijo@localhost by horde.leathercollection.ph with HTTP; Sat, 14 Jul 2001 02:53:47 +0800 Message-ID: <995050427.3b4f43bb56ac3@horde.leathercollection.ph> Date: Sat, 14 Jul 2001 02:53:47 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Cc: reiserfs-list@namesys.com Subject: Re: benchmarks References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 192.168.0.90 X-Organization: The Leather Collection, Inc. X-URL: http X-Admin-Contact: root@leather-collection.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk (Note: original message seen in the XFS mailing list. Reply cross-posted to ReiserFS mailing list to prevent any occurences of "backstabbing" which I abhor) Quoting "P.Dixon" : > Any idea why xfs appears to be very much slower than reiserfs with these > benchmarks: > http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > Admittedly, the benchmarks were done by namesys... There are a number of reasons why this is so: Zeroth, XFS was probably not tweaked and was just the default, not to mention release 1.0 (although I cannot qualify this as I have not found any pertinent information). XFS has gone quite a significant distance since release 1.0 with release 1.0.1 and the current CVS snapshots. First the mongo.pl benchmark was written by Hans Reiser (I think, or at least his team) for testing ReiserFS in particular. It has been used for testing other filesystems as well, but it started out as a test for ReiserFS (comparing it with ext2fs, I think). Second, ReiserFS was developed when there was no other journalling filesystem available for Linux. It was an alternative to ext2fs that had (and still has) rather poor handling for a lot of small files. Poor handling in that because of static inode allocation you can only handle so many of these small files, and you waste a lot of space in the process. ReiserFS does not have any of these limitations. Together with tail packing, you can dramatically reduce the space used by directory trees with a lot of small files. ReiserFS is also fast compared to ext2fs, which was its initial objective. No, it's not just fast, it's MUCH MUCH FASTER (particularly on modern machines with ample CPU). Because ReiserFS was designed to handle the area where ext2fs was lacking (small files), the mongo.pl benchmark was designed to test this functionality. If you will notice the filesizes are unnaturally small, with the largest at 100kb. Not so small, but still relatively small, right? ReiserFS is ABSOLUTELY GREAT for what it was designed for: lots and lots of small files. These include Squid caches, especially. Because of XFS's slow deletes (which the mongo.pl correctly shows as previously mentioned), ReiserFS is also good when you will be deleting trees with a lot of files regularly. This includes my deleting /usr/src/linux-2.4.x-acy to create a new /usr/src/linux.vanilla which I will patch with a later ac patch. You will notice, however, that results comparing ReiserFS and XFS give XFS the lead as the filesizes increase particularly in create and read speeds. Although because the mongo.pl benchmark was not designed to handle large files, we don't see this data progress and cannot make ample hypotheses testing (with the null hypothesis of course that ReiserFS is much faster than XFS no matter what the filesize). As of yet I cannot qualify the discussions between both ReiserFS and XFS camps (I am part of both mailing lists as I use both filesystems) about the desireability of the fact that ReiserFS uses significantly much more CPU than XFS. I agree with the ReiserFS camp in that CPU useage is not bad per-se, because of the fact that CPU speed increases much more dramatically than drive- speed or seek time does (someone posted a statistic about this in the last decade in the ReiserFS list). If CPU can be used to increase the performance of the filesystem, why the hell not, I say. This does not imply that higher CPU use makes a filesystem better than the other, though. If XFS can outperform ReiserFS in larger files without having to use as much CPU then I think that is a great plus for XFS. I am of personal opinion that because XFS was designed to handle image files and other files larger than the small ones ReiserFS was designed for, we will see an increase in performance as size increases. For most database and data storage applications, this should be a plus. The fact that XFS is much MUCH slower than ReiserFS on deletes should not matter as large tree deletions should not be a part of normal day-to-day life of a data storage partition. I am truly interested to find out about the benchmark results that Mike Gigante mentioned he would post soon (on the XFS mailing list). I agree that they will be interesting. This doesn't make me look down on ReiserFS, though. I am sure it has its plusses. Then of course there's the fact that they're obviously designed to handle different load and file types. For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great job there. For your Samba or NFS partition, go XFS and not ReiserFS. Aside from the fact that ReiserFS is having problems with NFS (and SFS which runs on top of NFS), ReiserFS expects to have EA and ACL support only in ReiserFS v4 (which looks exciting, BTW) which is due at least a year from now as per Hans Reiser's estimations. For those interested, DARPA supposedly sponsored encryption support to be built into ReiserFS v4. Still to be seen, of course, but I think we should all be happy about this. Like the lead developers of both filesystems mentioned "threads ago", XFS and ReiserFS are not competition to each other. Instead they both provide what makes Linux a continually more viable platform in this world where greed and closed-source applications still take the lead in a number of ways. (Read: we're not fighting each other, we have a common alien enemy). :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 13 11:59:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DIxY524679 for linux-xfs-outgoing; Fri, 13 Jul 2001 11:59:34 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DIxWV24660 for ; Fri, 13 Jul 2001 11:59:32 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA01991 for ; Fri, 13 Jul 2001 11:59:23 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2418827; Fri, 13 Jul 2001 13:58:14 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA56686; Fri, 13 Jul 2001 13:58:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DJ02E14044; Fri, 13 Jul 2001 14:00:02 -0500 Message-Id: <200107131900.f6DJ02E14044@jen.americas.sgi.com> To: "Gonyou, Austin" cc: "'linux-xfs@oss.sgi.com'" Subject: Re: Mounting XFS volumes with uid= or gid= or both References: <85063BBE668FD411944400D0B744267A6433E2@AUSMAIL> Comments: In-reply-to "Gonyou, Austin" message dated "Fri, 13 Jul 2001 13:43:58 -0500." Date: Fri, 13 Jul 2001 14:00:02 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Could chacl possibly be used to force files to be written as a specific > UID/GID? > I do not think so, access control lists merely control who has access to files, not who owns them. I presume what you are attempting to do is create a filesystem where no matter who creates a file, it ends up with the specified uid instead of that of the user. A sort of msdos style of user id - i.e. none. I think the filesystems which support the uid and gid options are those which do not directly support storing uids and gids themselves. So the options are there to help non-unix filesystems function in a unix environment, not to dumb down a unix based filesystem. It would be possible to implement this, there are probably only a couple of key places in xfs which would need changing to place a uid/gid from the mount structure into an inode rather than that supplied by the caller. These would be create a new inode and setting the attributes of an existing one. However, I do not see this as something which should be folded back into the main xfs code base. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 13 12:04:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DJ4KA24875 for linux-xfs-outgoing; Fri, 13 Jul 2001 12:04:20 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DJ4HV24856 for ; Fri, 13 Jul 2001 12:04:18 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 350E6166 for ; Sat, 14 Jul 2001 03:04:16 +0800 (PHT) Received: from 192.168.0.90 ( [192.168.0.90]) as user jijo@localhost by horde.leathercollection.ph with HTTP; Sat, 14 Jul 2001 03:04:16 +0800 Message-ID: <995051056.3b4f46301dbf6@horde.leathercollection.ph> Date: Sat, 14 Jul 2001 03:04:16 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Re: benchmarks References: <200107131550.f6DFogU08171@jen.americas.sgi.com> In-Reply-To: <200107131550.f6DFogU08171@jen.americas.sgi.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 192.168.0.90 X-Organization: The Leather Collection, Inc. X-URL: http X-Admin-Contact: root@leather-collection.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Quoting Steve Lord : > An external log is growable, an internal one unfortunately is not, and > we keep kicking SGI support people who build multi-terabyte filesystems > without reading the man page. > > Unless you specified otherwise you have two logbufs, all you need to do > to get the number changed is remount with the new option, so yes, edit > fstab and reboot. Does mkfs default to create one or two logbufs? If it default to creating one, I presume that it creates an external log which you can then grow using the mount option? Is an internal logbuf much better (performance wise) compared to an external logbuf (I presume this, but ask anyway). Maybe we can include this in the FAQ together with the current entry about the mount options? Or is the presence in the man page good enough? :) > If you use O_SYNC anywhere then osyncisdsync as a mount option will > make xfs O_SYNC behave more like other linux filesystems. I'm a total ignoramus (;>) when it comes to these nitty-gritties about filesystem operation, but in a nutshell maybe we can have information about the consequences of this (aside from the already stated speed benefit) on the reliability of the data? When is O_SYNC normally called and what does O_DSYNC do in comparison with O_SYNC that will make it I/O sync less? :) :) Thanks a lot for this tweaking help. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 13 12:26:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DJQJo25285 for linux-xfs-outgoing; Fri, 13 Jul 2001 12:26:19 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DJQGV25266 for ; Fri, 13 Jul 2001 12:26:17 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 93B381E625; Fri, 13 Jul 2001 21:26:10 +0200 (MEST) Date: Fri, 13 Jul 2001 21:26:00 +0200 From: Andi Kleen To: Steve Lord Cc: "Gonyou, Austin" , "'linux-xfs@oss.sgi.com'" Subject: Re: Mounting XFS volumes with uid= or gid= or both Message-ID: <20010713212600.A21365@gruyere.muc.suse.de> References: <85063BBE668FD411944400D0B744267A6433E2@AUSMAIL> <200107131900.f6DJ02E14044@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107131900.f6DJ02E14044@jen.americas.sgi.com>; from lord@sgi.com on Fri, Jul 13, 2001 at 02:00:02PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 13, 2001 at 02:00:02PM -0500, Steve Lord wrote: > I presume what you are attempting to do is create a filesystem where > no matter who creates a file, it ends up with the specified uid > instead of that of the user. A sort of msdos style of user id - i.e. none. > I think the filesystems which support the uid and gid options are those > which do not directly support storing uids and gids themselves. So the > options are there to help non-unix filesystems function in a unix environment, > not to dumb down a unix based filesystem. Most unix file systems, it seems including XFS, support it for the GID at least. You just have to create a directory with that gid and set the setgroupid bit; then all files created below it get that gid by default. It is very useful for shared source repositories for example. Together with the right umask it'll very likely do what the original poster wants. -Andi From owner-linux-xfs@oss.sgi.com Fri Jul 13 12:45:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DJjp725888 for linux-xfs-outgoing; Fri, 13 Jul 2001 12:45:51 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DJjnV25867 for ; Fri, 13 Jul 2001 12:45:49 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA00485 for ; Fri, 13 Jul 2001 12:43:16 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2427659; Fri, 13 Jul 2001 14:44:30 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA44503; Fri, 13 Jul 2001 14:44:30 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6DJkJp14237; Fri, 13 Jul 2001 14:46:19 -0500 Message-Id: <200107131946.f6DJkJp14237@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Federico Sevilla III cc: linux-xfs@oss.sgi.com Subject: Re: benchmarks In-Reply-To: Message from Federico Sevilla III of "Sat, 14 Jul 2001 03:04:16 +0800." <995051056.3b4f46301dbf6@horde.leathercollection.ph> Date: Fri, 13 Jul 2001 14:46:19 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Quoting Steve Lord : > > An external log is growable, an internal one unfortunately is not, and > > we keep kicking SGI support people who build multi-terabyte filesystems > > without reading the man page. > > > > Unless you specified otherwise you have two logbufs, all you need to do > > to get the number changed is remount with the new option, so yes, edit > > fstab and reboot. > > Does mkfs default to create one or two logbufs? If it default to creating one > , > I presume that it creates an external log which you can then grow using the > mount option? Is an internal logbuf much better (performance wise) compared t > o > an external logbuf (I presume this, but ask anyway). You have your terminology crossed, logbufs are in memory buffers the number of which is configurable at mount time, they basically represent the number of buffers which can be in flight on their way to the on disk log at once. If you have more you can sustain a higher transaction rate without having to block waiting for a previous log write to complete. The log itself is constructed at mkfs time, and comes in two flavors, internal and external. The internal log is basically in the middle of the partition/volume which forms the filesystem and cannot be extended after mkfs. The external log is in theory easier to extend, and can certainly be on a device with different characteristics (e.g. an NVRAM disk). At the moment we do not really have the tools to extend this either, but the procedure I described could be used. The advantage of the internal log is you do not need anything more than a regular partition, it is the default. The external log takes a little work to setup (second device specified at mkfs time) and use (logdev=xxx) option at mount time, but is more flexible (there is no conflict between moving the head for the log and the data). Irix volume managers support having multiple 'subvolumes' within a volume, so mkfs and the kernel can find the log for themselves without the extra options. > > Maybe we can include this in the FAQ together with the current entry about th > e > mount options? Or is the presence in the man page good enough? :) > > > If you use O_SYNC anywhere then osyncisdsync as a mount option will > > make xfs O_SYNC behave more like other linux filesystems. > > I'm a total ignoramus (;>) when it comes to these nitty-gritties about > filesystem operation, but in a nutshell maybe we can have information about t > he > consequences of this (aside from the already stated speed benefit) on the > reliability of the data? When is O_SYNC normally called and what does O_DSYNC > > do in comparison with O_SYNC that will make it I/O sync less? :) :) > > Thanks a lot for this tweaking help. :) O_SYNC is used when you want to know on return from a write system call that the data you wrote will still be there after a crash. A mail program might use it when appending to a mailbox before removing the mail from the queue for instance. O_SYNC will always do a synchronous transaction to write out the inode to the log at the end of the write, it does this to guarantee the timestamps are recorded. O_DSYNC (on Irix) or the osyncisdsync mount option on linux will only log the inode if the size was changed by the write. The act of flushing this transaction to the log means all previous transactions which are still in memory for the inode are also flushed and hence safe from crash. In both cases the data is flushed. Steve > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 13 14:01:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DL1to27344 for linux-xfs-outgoing; Fri, 13 Jul 2001 14:01:55 -0700 Received: from wraith.engg.ksu.edu (wraith.engg.ksu.edu [129.130.81.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DL1rV27325 for ; Fri, 13 Jul 2001 14:01:53 -0700 Received: (from matthead@localhost) by wraith.engg.ksu.edu (8.11.2/8.11.2) id f6DL42j18041 for linux-xfs@oss.sgi.com; Fri, 13 Jul 2001 16:04:02 -0500 Message-Id: <200107132104.f6DL42j18041@wraith.engg.ksu.edu> Date: Fri, 13 Jul 2001 16:04:01 -0500 (CDT) From: Matt Stegman Subject: Re: Mounting XFS volumes with uid= or gid= or both To: linux-xfs@oss.sgi.com In-Reply-To: <20010713212600.A21365@gruyere.muc.suse.de> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 13 Jul, Andi Kleen wrote: > On Fri, Jul 13, 2001 at 02:00:02PM -0500, Steve Lord wrote: >> I presume what you are attempting to do is create a filesystem where >> no matter who creates a file, it ends up with the specified uid >> instead of that of the user. A sort of msdos style of user id - i.e. none. >> I think the filesystems which support the uid and gid options are those >> which do not directly support storing uids and gids themselves. So the >> options are there to help non-unix filesystems function in a unix environment, >> not to dumb down a unix based filesystem. > > Most unix file systems, it seems including XFS, support it for the GID at least. > You just have to create a directory with that gid and set the setgroupid bit; > then all files created below it get that gid by default. It is very useful > for shared source repositories for example. Together with the right umask > it'll very likely do what the original poster wants. Not if he wants to prevent people from changing the mode of the files they create, or doesn't want files in that directory to apply to their quota. Something like that is, I guess, pretty much impossible to do. -- -Matt Stegman From owner-linux-xfs@oss.sgi.com Fri Jul 13 14:50:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DLooR29551 for linux-xfs-outgoing; Fri, 13 Jul 2001 14:50:50 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DLomV29531 for ; Fri, 13 Jul 2001 14:50:48 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA201079 for ; Fri, 13 Jul 2001 23:50:46 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2428120 for ; Fri, 13 Jul 2001 16:49:29 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id QAA82740 for ; Fri, 13 Jul 2001 16:49:28 -0500 (CDT) Message-ID: <3B4F6D05.2103D00@sgi.com> Date: Fri, 13 Jul 2001 16:49:57 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: TAKE - fix endianness on xfs_db write Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Fri Jul 13 14:32:49 PDT 2001 Workarea: stout.americas.sgi.com:/localhome/eric/2.4.x-xfs/workarea The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98886a cmd/xfsprogs/db/bit.c - 1.2 - Fix endianness on write, comments said bytes, code said bits. We want bytes. :) From owner-linux-xfs@oss.sgi.com Fri Jul 13 15:32:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DMWl832102 for linux-xfs-outgoing; Fri, 13 Jul 2001 15:32:47 -0700 Received: from mailout03.sul.t-online.de (mailout03.sul.t-online.com [194.25.134.81]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DMWjV32079 for ; Fri, 13 Jul 2001 15:32:45 -0700 Received: from fwd00.sul.t-online.de by mailout03.sul.t-online.de with smtp id 15LBUJ-0000IH-01; Sat, 14 Jul 2001 00:32:43 +0200 Received: from deepthought.omnicore.com (310084855026-0001@[217.1.27.40]) by fmrl00.sul.t-online.com with esmtp id 15LBUA-1PqIeuC; Sat, 14 Jul 2001 00:32:34 +0200 Received: from talby (talby.omnicore.com [192.168.0.9]) by deepthought.omnicore.com (8.8.8/8.8.8) with SMTP id AAA18385 for ; Sat, 14 Jul 2001 00:32:28 +0200 Message-ID: <15ee01c10beb$b2dbe4a0$0900a8c0@talby> From: "Hans Kratz" To: Subject: Are directory operations synchronous with XFS? Date: Sat, 14 Jul 2001 00:32:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Sender: 310084855026-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi! Most mailers require that directory operations on their mail queue directories such as link()'ing and unlink()'ing are synchronous in order to ensure that mail is not lost in a power failure or server crash. Thus it depends on the filesystem on which the mail queue resides if mail delivery is safe. ReiserFS for example does not perform synchronous directory operations out of the box. More information can be found at http://cr.yp.to/qmail/faq/reliability.html#filesystems or at http://www.reiserfs.com/faq.html#qmail How about XFS? Is it safe to run a qmail queue on an XFS filesystem? Thanks for your answer. Best regards, Hans -- Hans Kratz phone: +49 721 9 37 58 40 fax: +47 721 9 37 58 46 From owner-linux-xfs@oss.sgi.com Fri Jul 13 16:00:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DN0nn01396 for linux-xfs-outgoing; Fri, 13 Jul 2001 16:00:49 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DN0kV01377 for ; Fri, 13 Jul 2001 16:00:46 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15LBvM-0008Vd-01; Sat, 14 Jul 2001 11:00:40 +1200 From: "Juha Saarinen" To: "'Gonyou, Austin'" , Subject: RE: Hello? Date: Sat, 14 Jul 2001 11:01:02 +1200 Message-ID: <002601c10bef$b03e5990$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <85063BBE668FD411944400D0B744267A6433C6@AUSMAIL> Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nope. It's a spam trap. -- ;-> :: -----Original Message----- :: From: owner-linux-xfs@oss.sgi.com :: [mailto:owner-linux-xfs@oss.sgi.com] On Behalf Of Gonyou, Austin :: Sent: Saturday, 14 July 2001 02:52 :: To: linux-xfs@oss.sgi.com :: Subject: Hello? :: :: :: Is this list alive? :: :: -- :: Austin Gonyou :: Systems Architect, CCNA :: Coremetrics, Inc. :: Phone: 512-796-9023 :: email: austin@coremetrics.com :: :: :: :: From owner-linux-xfs@oss.sgi.com Fri Jul 13 16:03:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DN3Rg01674 for linux-xfs-outgoing; Fri, 13 Jul 2001 16:03:27 -0700 Received: from myth7.Stanford.EDU (myth7.Stanford.EDU [171.64.15.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DN3QV01655 for ; Fri, 13 Jul 2001 16:03:26 -0700 Received: (from smv@localhost) by myth7.Stanford.EDU (8.11.1/8.11.1) id f6DN2pA18778; Fri, 13 Jul 2001 16:02:51 -0700 (PDT) Date: Fri, 13 Jul 2001 16:02:51 -0700 (PDT) From: Sergei Morozov To: Seth Mos cc: Simon Matter , Subject: Re: "LILO: /dev/sda: Read-only file system" after /boot flirted withxfs In-Reply-To: <4.3.2.7.2.20010713094103.030b3ff0@pop.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Problem solved by upgrading lilo to version 21.4-14 Apparently previous lilo was confused about the menaing of read-write. Thanks all for suggestions, even if none were to the root of the problem. > There is a link in the FAQ to a xfs-aware rescue/boot floppy set. > http://oss.sgi.com/projects/xfs/faq.html#xfsbootdisks didn't work - scsi driver bonked > > > > boot with something like init=/bin/sh and / is mounted ro, even when > > > mount tells you it is rw. Maybe the problem was such thing. mtab > > > will also report rw falsely, maybe cat /proc/mounts shows the truth. > > > >cat /proc/mounts still shows rw; also I can write on / and /boot fine, but > >not lilo somehow. > > If you can format /boot correctly and mount it. Put a xfs-aware kernel in > there and run lilo. > I don't know if lilo checks for the rootfs to be ro or the /boot. both / and /boot were truly rw, but lilo was confused about it. Sergei Writing is easy; all you do is sit staring at the blank sheet of paper until drops of blood form on your forehead. -- Gene Fowler Sergei Morozov Department of Economics Stanford University Stanford, CA, 94305-6072 ph: (650)-725-8984 (o) (650)-498-1248 (h) -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOH8VK3ZlrUSqDLbVAQFHIwP/dYGV0yV2AYoFWWfJDE6WMtYOLjUSebaV Mzv3ICK2SDPTQ6u3lKx/7VXdY1151pqRZ3Kn7Z8FPZ2KxjRIqeLtOsCMFPRXM234 j23RfBtNPzG2pTOciJvqh0uHxySMR7Dzee+gjniNJadXyE0Y2+C33HICuVVqDH8O ZEhGny68w7c= =sz39 -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Fri Jul 13 16:16:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6DNGTA02511 for linux-xfs-outgoing; Fri, 13 Jul 2001 16:16:29 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6DNGQV02489 for ; Fri, 13 Jul 2001 16:16:26 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15LC0m-00006Y-00; Sat, 14 Jul 2001 11:06:16 +1200 From: "Juha Saarinen" To: "'Steve Lord'" , "'Gonyou, Austin'" Cc: Subject: RE: Scripted CVS updates? Date: Sat, 14 Jul 2001 11:06:38 +1200 Message-ID: <003101c10bf0$78a488f0$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <200107131554.f6DFsFa08205@jen.americas.sgi.com> Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The password is actually stored in a file in your $HOME directory called .cvspass. The format is :pserver:loginname@fqdn:/directory As long as that's there, you should be able to run CVS from a script fine. -- Juha :: -----Original Message----- :: From: owner-linux-xfs@oss.sgi.com :: [mailto:owner-linux-xfs@oss.sgi.com] On Behalf Of Steve Lord :: Sent: Saturday, 14 July 2001 03:54 :: To: Gonyou, Austin :: Cc: linux-xfs@oss.sgi.com :: Subject: Re: Scripted CVS updates? :: :: :: > I'm trying to script cvs updates with cron for once every :: couple of days, or :: > once a week. But, I must provide a login password to the :: cvs server. Is :: > there a way to do that easily? perhaps something like? :: > :: > cvs login<< EOF :: > password :: > :: > EOF :: > :: :: I just cd into the cvs directory and run :: :: cvs update -d . :: :: no need for a password or anything else. :: :: Steve :: :: :: > Thanks in advance. :: > -- :: > Austin Gonyou :: > Systems Architect, CCNA :: > Coremetrics, Inc. :: > Phone: 512-796-9023 :: > email: austin@coremetrics.com :: :: :: :: From owner-linux-xfs@oss.sgi.com Fri Jul 13 19:24:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E2OIJ12900 for linux-xfs-outgoing; Fri, 13 Jul 2001 19:24:18 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E2OFV12878 for ; Fri, 13 Jul 2001 19:24:15 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id EAA209584 for ; Sat, 14 Jul 2001 04:24:11 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 MAA10320; Sat, 14 Jul 2001 12:22:45 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA99754; Sat, 14 Jul 2001 12:22:44 +1000 (AEST) Date: Sat, 14 Jul 2001 12:22:43 +1000 From: Nathan Scott To: Ries van Twisk Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump-1.0.9 does not compile Message-ID: <20010714122243.A210844@wobbly.melbourne.sgi.com> References: <3B4EDBA9.24773.A6B3765@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B4EDBA9.24773.A6B3765@localhost>; from ries@franksintl.nl on Fri, Jul 13, 2001 at 11:29:45AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Fri, Jul 13, 2001 at 11:29:45AM +0200, Ries van Twisk wrote: > Hi, > > I was just buzy compiling xfsdump but it doesn't because of a error: > > ...../arch_xlate.c:67: undefined reference to '__fswab64' > > I checked the Linux libs and the __swab64 macro is there. > What else could be wrong? > You need to install a more recent version of the XFS headers - usually via a newer version of the xfsprogs-devel rpm, or by doing a "make install-dev" in the xfsprogs directory. There was a portability change to the XFS headers several months ago now, and this compile error was an unfortunate side effect. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Jul 13 21:12:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E4C0q18473 for linux-xfs-outgoing; Fri, 13 Jul 2001 21:12:00 -0700 Received: from mail.corbett-msc.com (mail.corbett-msc.com [4.21.114.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E4BwV18454 for ; Fri, 13 Jul 2001 21:11:58 -0700 Received: (qmail 22630 invoked from network); 14 Jul 2001 04:11:53 -0000 Received: from 24-163-96-233.ff.cox.rr.com (HELO adampc) (apendlet@24.163.96.233) by mail.corbett-msc.com with SMTP; 14 Jul 2001 04:11:53 -0000 Message-ID: <003301c10c1a$83172660$650aa8c0@corbettmsc.com> From: "Adam H. Pendleton" To: Subject: RedHat RPM Upgrade Question Date: Sat, 14 Jul 2001 00:00:54 -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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk First, let me apologize if this question has been asked before, but since the archives aren't searchable, it was difficult for me to look for an answer to my question. Having said that, I'll ask away: I just installed RedHat 7.1, using the .iso image from oss.sgi.com. Everything installed okay, but now I have a question about package upgrade. I won't to upgrade as much of my RedHat .rpm's as I can, but I noticed that the XFS installed put some of it's own .rpms on the system. My question is this: What packages should I leave alone and not upgrade, and which packages are okay to upgrade. I would assume that "quota" is one of them, but what are the other ones? AP From owner-linux-xfs@oss.sgi.com Fri Jul 13 22:18:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E5Itl21553 for linux-xfs-outgoing; Fri, 13 Jul 2001 22:18:55 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E5IsV21531 for ; Fri, 13 Jul 2001 22:18:54 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id WAA07024 for ; Fri, 13 Jul 2001 22:18:44 -0700 (PDT) mail_from (mg@smack.melbourne.sgi.com) Received: from smack.melbourne.sgi.com (smack.melbourne.sgi.com [134.14.55.210]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA10797; Sat, 14 Jul 2001 15:17:31 +1000 Received: from localhost (mg@localhost) by smack.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id PAA77623; Sat, 14 Jul 2001 15:17:29 +1000 (EST) Date: Sat, 14 Jul 2001 15:17:29 +1000 From: Mike Gigante To: Tony Gale cc: Gerald Henriksen , linux-xfs@oss.sgi.com Subject: Re: [OT] XFS and FreeBSD? In-Reply-To: <995029687.29184.4.camel@syntax.dera.gov.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 13 Jul 2001, Tony Gale wrote: > > I can't see SGI maintaining a MIPS platform for very long after they are > up and running with IA64. They don't make enough profit to support two > such platforms :-) > > -tony Well, maybe, but there are a bunch of things about Irix that are important to our customers, and that Linux is a long way from doing as well. Some of those things may not be aligned with the interests of the rest of the Linux community (hence official progress may be slow???). At minimum they'd be an overlap of a few years. With that overlap, we are talking 4 or 5 years out so who can tell what the landscape would be like then... All of the above is "IMHO", and does not represent an official SGI viewpoint etc etc. Mike From owner-linux-xfs@oss.sgi.com Fri Jul 13 22:36:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E5aE522228 for linux-xfs-outgoing; Fri, 13 Jul 2001 22:36:14 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E5aDV22209 for ; Fri, 13 Jul 2001 22:36:13 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA08607 for ; Fri, 13 Jul 2001 22:36:04 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id WAA96683; Fri, 13 Jul 2001 22:35:40 -0700 (PDT) Message-ID: <3B4FD993.4AA9A529@sgi.com> Date: Sat, 14 Jul 2001 00:33:07 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Adam H. Pendleton" CC: linux-xfs@oss.sgi.com Subject: Re: RedHat RPM Upgrade Question References: <003301c10c1a$83172660$650aa8c0@corbettmsc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Adam H. Pendleton" wrote: > > My question is > this: What packages should I leave alone and not upgrade, and which > packages are okay to upgrade. Leave quota, and, of course, the kernel. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 13 22:39:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E5d3L22559 for linux-xfs-outgoing; Fri, 13 Jul 2001 22:39:03 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E5cxV22533 for ; Fri, 13 Jul 2001 22:38:59 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 9D1A62DF for ; Sat, 14 Jul 2001 13:38:57 +0800 (PHT) Date: Sat, 14 Jul 2001 13:39:00 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: Re: "LILO: /dev/sda: Read-only file system" after /boot flirted withxfs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 13 Jul 2001 at 16:02, Sergei Morozov wrote: > didn't work - scsi driver bonked Why don't you recompile a kernel with support for all your hardware and replace the one on the bootdisk? I normally do this. The fact that the bootdisk has the proper libraries and utilities to create XFS partitions is good enough for me. I handle the kernel to support my hardware 100%. :) > both / and /boot were truly rw, but lilo was confused about it. I don't know if you've tried this, but the read-write option for the image that loads the XFS-aware kernel should help you out. Don't forget to update your fstab, as well, to put "rw" in the default options. :) Just in case ... :-) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 13 23:03:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E63cq24089 for linux-xfs-outgoing; Fri, 13 Jul 2001 23:03:38 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E63XV24067 for ; Fri, 13 Jul 2001 23:03:34 -0700 Received: from verbum.org (root@gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id CAA16934 for ; Sat, 14 Jul 2001 02:03:32 -0400 (EDT) Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by verbum.org (Postfix (Debian/GNU)) with ESMTP id 2F226729C for ; Sat, 14 Jul 2001 01:57:55 -0400 (EDT) Received: by space-ghost (Postfix (Debian/GNU), from userid 1000) id B6836622F55; Sat, 14 Jul 2001 01:58:12 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: null character filesystem corruption with 2.4.6 X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Sat, 14 Jul 2001 01:58:11 -0400 Message-ID: <87y9psdpcc.church.of.emacs@cis.ohio-state.edu> Lines: 27 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --=-=-= When I tried to set up an 'at' command today, it told me I didn't have permissions; this confused me until I looked at /etc/at.deny, which was about 100 null characters. Following this, I noticed that one of my old emails had been destroyed too. So I wrote the attached program to search for non-empty files consisting entirely of null characters on XFS filesystems, which I'm posting in the hope that it will be useful for someone else. It revealed that my filesystem is pretty badly damaged (about 150 files were hit), so I'll probably have to restore from backups and switch back to ext2 for now. I'm running 2.4.6 from benh's tree on PowerPC. I did try an xfs_check on the filesystem, which reported no errors. Let me know if there's any more debugging information I can give; I really wish I could use XFS! --=-=-= Content-Type: text/x-csrc Content-Disposition: attachment; filename=findnull.c Content-Description: program to find null files /* findnull.c --- Find non-emtpy files consisting entirely of null bytes Copyright (C) 2001 Colin Walters This program is hereby placed in the public domain. */ #define _GNU_SOURCE #include #include #include #include #include #include #include #include #include #include void usage(void); void fatal_error(const char *__restrict format, ...); int null_file_p(const char *filename); int print_if_null_file(const char *filename, const struct stat *buf, int flag); void print_null_files_in_dir(const char *filename); static int n_excluded; static int max_excluded; static char **excluded; static int verbose = 0; int main(int argc, char **argv) { struct fstab *fsentry; if (argc > 1) verbose = !strcmp(argv[1], "-v"); if (argc > 2) verbose += !strcmp(argv[2], "-v"); n_excluded = 0; max_excluded = 8; if (!(excluded = malloc(sizeof(char *) * max_excluded))) fatal_error("malloc failed: %s", strerror(errno)); if (!setfsent()) fatal_error("setfsent failed: %s", strerror(errno)); while ((fsentry = getfsent()) != NULL) { if (strcmp(fsentry->fs_vfstype, "xfs") || strcmp(fsentry->fs_vfstype, "none")) { if (n_excluded++ > max_excluded) if (!(excluded = realloc(excluded, max_excluded *= 2))) fatal_error("realloc failed: %s", strerror(errno)); excluded[n_excluded-1] = strdup(fsentry->fs_file); if (verbose) fprintf(stderr, "excluding %s\n", excluded[n_excluded-1]); } } endfsent(); print_null_files_in_dir("/"); exit(0); } void fatal_error(const char *__restrict format, ...) { va_list args; va_start(args, format); vfprintf(stderr, format, args); exit(1); } int null_file_p(const char *filename) { static char buf[8192]; size_t num; int retval = 0; FILE *fp; if (!(fp = fopen(filename, "r"))) { perror("fopen"); return -1; } while ((num = fread(buf, sizeof(char), sizeof(buf), fp)) > 0) { size_t n; for (n = 0; n < num; n++) if (buf[n] != '\0') { retval = 0; goto cleanup; } } if (num < 0) { perror("fread"); retval = -1; goto cleanup; } retval = 1; cleanup: fclose(fp); return retval; } void print_null_files_in_dir(const char *filename) { struct dirent *ent; struct stat buf; int i; DIR *cur; if (verbose > 1) fprintf(stderr, "checking dir %s\n", filename); for (i = 0; i < n_excluded; i++) if (!strncmp(filename, excluded[i], strlen(excluded[i]))) { if (verbose) fprintf(stderr, "dir %s is excluded\n", filename); return; } if (!(cur = opendir(filename))) fatal_error("opendir failed on %s: %s", filename, strerror(errno)); while ((ent = readdir(cur)) != NULL) { int ret = 0; char *curname; if (ent->d_name[0] == '\0' || !strncmp(ent->d_name, ".", 2) || !strncmp(ent->d_name, "..", 3)) continue; if (! ({ /* Make things look a bit prettier */ if (!strncmp(filename, "/", 2)) asprintf(&curname, "/%s", ent->d_name); else asprintf(&curname, "%s/%s", filename, ent->d_name); curname; })) fatal_error("out of memory"); if (verbose > 1) fprintf(stderr, "checking entry %s\n", curname); if (lstat(curname, &buf)) perror("stat"); else if (S_ISDIR(buf.st_mode)) print_null_files_in_dir(curname); else if (S_ISREG(buf.st_mode) && buf.st_size > 0 && ((ret = null_file_p(curname)) == 1)) fprintf(stdout, "%s\n", curname); if (ret < 0) fprintf(stderr, "failed to test %s\n", curname); free(curname); } if (verbose > 1) fprintf(stderr, "exiting dir %s\n", filename); closedir(cur); } --=-=-=-- From owner-linux-xfs@oss.sgi.com Fri Jul 13 23:31:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E6Vxq25229 for linux-xfs-outgoing; Fri, 13 Jul 2001 23:31:59 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E6VvV25208 for ; Fri, 13 Jul 2001 23:31:57 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id CC441192 for ; Sat, 14 Jul 2001 14:31:55 +0800 (PHT) Date: Sat, 14 Jul 2001 14:31:58 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: Re: null character filesystem corruption with 2.4.6 In-Reply-To: <87y9psdpcc.church.of.emacs@cis.ohio-state.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001 at 01:58, Colin Walters wrote: > When I tried to set up an 'at' command today, it told me I didn't have > permissions; this confused me until I looked at /etc/at.deny, which > was about 100 null characters. Following this, I noticed that one of > my old emails had been destroyed too. I remember that this NULL character issue was widespread right after 1.0 was released. I was not able to update myself with the status of this issue, though, so maybe someone on the list can refresh us all as to what the known causes of the NULL character issue are, and what kernels and platforms are most susceptible? > It revealed that my filesystem is pretty badly damaged (about 150 > files were hit), so I'll probably have to restore from backups and > switch back to ext2 for now. This report by Colin Walter sounds rather alarming. I hope we can all help each other to find out how to work on this issue. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 13 23:36:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E6a1I25482 for linux-xfs-outgoing; Fri, 13 Jul 2001 23:36:01 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E6ZwV25462 for ; Fri, 13 Jul 2001 23:35:58 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id XAA03843 for ; Fri, 13 Jul 2001 23:33:24 -0700 (PDT) mail_from (mg@smack.melbourne.sgi.com) Received: from smack.melbourne.sgi.com (smack.melbourne.sgi.com [134.14.55.210]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA11015; Sat, 14 Jul 2001 16:33:08 +1000 Received: from localhost (mg@localhost) by smack.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id QAA65605; Sat, 14 Jul 2001 16:33:07 +1000 (EST) Date: Sat, 14 Jul 2001 16:33:07 +1000 From: Mike Gigante To: Federico Sevilla III cc: linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: benchmarks In-Reply-To: <995050427.3b4f43bb56ac3@horde.leathercollection.ph> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Good idea to cross-post! For the benefit of the Reiser list, I am running a diverse set of f/s benchmarks with a number of different XFS 'configurations'. I am doing so after some conversations at a local Linux users group - Neither mongo, nor iozone/bonnie are either comprehensive enough at measuring overall f/s performance or realistic simulations of real world file system usage (except in limited cases). I will be also running them with Ext2 and with reiserFS and will post the results somewhere. This will be in a week or two from now... Mike ----------------------------------------------------------------------- Michael Gigante R&D Software Engineer mg@melbourne.sgi.com SGI Performance Tools Group, +61 3 9834 8233 Melbourne Australia V-Net: 524-8233 On Sat, 14 Jul 2001, Federico Sevilla III wrote: > (Note: original message seen in the XFS mailing list. Reply cross-posted to > ReiserFS mailing list to prevent any occurences of "backstabbing" which I abhor) > > Quoting "P.Dixon" : > > Any idea why xfs appears to be very much slower than reiserfs with these > > benchmarks: > > http://www.namesys.com/benchmarks/mongo/2.4.5-xfs-ext2_vs_reiserfs.html > > Admittedly, the benchmarks were done by namesys... > > There are a number of reasons why this is so: > > Zeroth, XFS was probably not tweaked and was just the default, not to mention > release 1.0 (although I cannot qualify this as I have not found any pertinent > information). XFS has gone quite a significant distance since release 1.0 with > release 1.0.1 and the current CVS snapshots. > > First the mongo.pl benchmark was written by Hans Reiser (I think, or at least > his team) for testing ReiserFS in particular. It has been used for testing > other filesystems as well, but it started out as a test for ReiserFS (comparing > it with ext2fs, I think). > > Second, ReiserFS was developed when there was no other journalling filesystem > available for Linux. It was an alternative to ext2fs that had (and still has) > rather poor handling for a lot of small files. Poor handling in that because of > static inode allocation you can only handle so many of these small files, and > you waste a lot of space in the process. ReiserFS does not have any of these > limitations. Together with tail packing, you can dramatically reduce the space > used by directory trees with a lot of small files. ReiserFS is also fast > compared to ext2fs, which was its initial objective. No, it's not just fast, > it's MUCH MUCH FASTER (particularly on modern machines with ample CPU). > > Because ReiserFS was designed to handle the area where ext2fs was lacking > (small files), the mongo.pl benchmark was designed to test this functionality. > If you will notice the filesizes are unnaturally small, with the largest at > 100kb. Not so small, but still relatively small, right? > > ReiserFS is ABSOLUTELY GREAT for what it was designed for: lots and lots of > small files. These include Squid caches, especially. Because of XFS's slow > deletes (which the mongo.pl correctly shows as previously mentioned), ReiserFS > is also good when you will be deleting trees with a lot of files regularly. > This includes my deleting /usr/src/linux-2.4.x-acy to create a > new /usr/src/linux.vanilla which I will patch with a later ac patch. > > You will notice, however, that results comparing ReiserFS and XFS give XFS the > lead as the filesizes increase particularly in create and read speeds. Although > because the mongo.pl benchmark was not designed to handle large files, we don't > see this data progress and cannot make ample hypotheses testing (with the null > hypothesis of course that ReiserFS is much faster than XFS no matter what the > filesize). > > As of yet I cannot qualify the discussions between both ReiserFS and XFS camps > (I am part of both mailing lists as I use both filesystems) about the > desireability of the fact that ReiserFS uses significantly much more CPU than > XFS. I agree with the ReiserFS camp in that CPU useage is not bad per-se, > because of the fact that CPU speed increases much more dramatically than drive- > speed or seek time does (someone posted a statistic about this in the last > decade in the ReiserFS list). If CPU can be used to increase the performance of > the filesystem, why the hell not, I say. This does not imply that higher CPU > use makes a filesystem better than the other, though. If XFS can outperform > ReiserFS in larger files without having to use as much CPU then I think that is > a great plus for XFS. > > I am of personal opinion that because XFS was designed to handle image files > and other files larger than the small ones ReiserFS was designed for, we will > see an increase in performance as size increases. For most database and data > storage applications, this should be a plus. The fact that XFS is much MUCH > slower than ReiserFS on deletes should not matter as large tree deletions > should not be a part of normal day-to-day life of a data storage partition. > > I am truly interested to find out about the benchmark results that Mike Gigante > mentioned he would post soon (on the XFS mailing list). I agree that they will > be interesting. This doesn't make me look down on ReiserFS, though. I am sure > it has its plusses. Then of course there's the fact that they're obviously > designed to handle different load and file types. > > For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great > job there. For your Samba or NFS partition, go XFS and not ReiserFS. Aside from > the fact that ReiserFS is having problems with NFS (and SFS which runs on top > of NFS), ReiserFS expects to have EA and ACL support only in ReiserFS v4 (which > looks exciting, BTW) which is due at least a year from now as per Hans Reiser's > estimations. > > For those interested, DARPA supposedly sponsored encryption support to be built > into ReiserFS v4. Still to be seen, of course, but I think we should all be > happy about this. Like the lead developers of both filesystems > mentioned "threads ago", XFS and ReiserFS are not competition to each other. > Instead they both provide what makes Linux a continually more viable platform > in this world where greed and closed-source applications still take the lead in > a number of ways. (Read: we're not fighting each other, we have a common alien > enemy). :) > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > > From owner-linux-xfs@oss.sgi.com Fri Jul 13 23:57:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E6vR626312 for linux-xfs-outgoing; Fri, 13 Jul 2001 23:57:27 -0700 Received: from myth8.Stanford.EDU (myth8.Stanford.EDU [171.64.15.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E6vPV26293 for ; Fri, 13 Jul 2001 23:57:25 -0700 Received: (from smv@localhost) by myth8.Stanford.EDU (8.11.1/8.11.1) id f6E6v9C08936; Fri, 13 Jul 2001 23:57:09 -0700 (PDT) Date: Fri, 13 Jul 2001 23:57:09 -0700 (PDT) From: Sergei Morozov To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: "LILO: /dev/sda: Read-only file system" after /boot flirted withxfs In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > didn't work - scsi driver bonked > > Why don't you recompile a kernel with support for all your hardware and > replace the one on the bootdisk? I normally do this. The fact that the That's the xfs kernel that I had, and the kernel itself is just fine, it's that lilo didn't want to put loader where it should; but also xfs kernel would not fit on the disk. Anyway, once lilo's stupidity was punished by upgrading, the need to make floppy bootdisk is less urgent. > bootdisk has the proper libraries and utilities to create XFS partitions > is good enough for me. I handle the kernel to support my hardware 100%. > :) > > > both / and /boot were truly rw, but lilo was confused about it. > > I don't know if you've tried this, but the read-write option for the image > that loads the XFS-aware kernel should help you out. Don't forget to > update your fstab, as well, to put "rw" in the default options. :) /etc/fstab had rw too, just lilo was stupid :-) > Just in case ... :-) > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > Writing is easy; all you do is sit staring at the blank sheet of paper until drops of blood form on your forehead. -- Gene Fowler Sergei Morozov Department of Economics Stanford University Stanford, CA, 94305-6072 ph: (650)-725-8984 (o) (650)-498-1248 (h) -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOH8VK3ZlrUSqDLbVAQFHIwP/dYGV0yV2AYoFWWfJDE6WMtYOLjUSebaV Mzv3ICK2SDPTQ6u3lKx/7VXdY1151pqRZ3Kn7Z8FPZ2KxjRIqeLtOsCMFPRXM234 j23RfBtNPzG2pTOciJvqh0uHxySMR7Dzee+gjniNJadXyE0Y2+C33HICuVVqDH8O ZEhGny68w7c= =sz39 -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Sat Jul 14 00:40:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E7eNn28042 for linux-xfs-outgoing; Sat, 14 Jul 2001 00:40:23 -0700 Received: from rebel.net.au (IDENT:root@news.tellurian.com.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E7eLV28021 for ; Sat, 14 Jul 2001 00:40:21 -0700 Received: from rebel.net.au (dialup-2.rebel.net.au [203.20.69.72]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id RAA14324 for ; Sat, 14 Jul 2001 17:10:17 +0930 Message-ID: <3B4FF84E.A6E36574@rebel.net.au> Date: Sat, 14 Jul 2001 17:14:14 +0930 From: David Lloyd X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Web Page Banner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Could someone update it to say "Pleased to Announce the First Update Release 1.01" or something similar... DS; -- "The greatest thing you'll ever learn is just to love and to be loved in return." - David Bowie (Nature Boy from Moulin Rouge) From owner-linux-xfs@oss.sgi.com Sat Jul 14 00:43:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E7hJM28293 for linux-xfs-outgoing; Sat, 14 Jul 2001 00:43:19 -0700 Received: from rebel.net.au (IDENT:root@rebel.rebel.net.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E7hHV28274 for ; Sat, 14 Jul 2001 00:43:18 -0700 Received: from rebel.net.au (dialup-2.rebel.net.au [203.20.69.72]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id RAA14377; Sat, 14 Jul 2001 17:12:50 +0930 Message-ID: <3B4FF8E6.5103E59E@rebel.net.au> Date: Sat, 14 Jul 2001 17:16:46 +0930 From: David Lloyd X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: Mike Gigante CC: Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: benchmarks References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Excellent! I don't have the expertise to ensure they're fair. However, from just "using" them, ReiserFS and XFS both feel faster than ext2, but that's about all I can really say. DSL From owner-linux-xfs@oss.sgi.com Sat Jul 14 02:53:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6E9rl405384 for linux-xfs-outgoing; Sat, 14 Jul 2001 02:53:47 -0700 Received: from bobas.nowytarg.top.pl (ghostwheel.underley.eu.org [217.97.235.9]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6E9raV05354 for ; Sat, 14 Jul 2001 02:53:44 -0700 Received: by bobas.nowytarg.top.pl with BSMTP id ; Sat, 14 Jul 2001 11:55:06 +0200 Received: by witch.underley.eu.org id ; Sat, 14 Jul 2001 09:41:21 +0200 Date: Sat, 14 Jul 2001 09:41:21 +0200 From: Daniel Podlejski To: linux-xfs@oss.sgi.com Subject: mkfs.xfs compilationa failed Message-ID: <20010714094121.A30307@witch.underley.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i X-PGP-Fingerprint: 4D 72 53 F8 FE 8C 53 B9 66 AD F6 EA C9 17 CD 82 X-GPG-Fingerprint: 299F 1820 582B 283A 5F50 37D9 AA0B 6E10 03D4 EA5D X-Homepage: http://www.underley.eu.org/ X-Cert: http://www.brainbench.com/transcript.jsp?pid=124954 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk gcc -o mkfs.xfs xfs_mkfs.o proto.o ../libxfs/.libs/libxfs.a ../libdisk/.libs/libdisk.a /usr/lib/libuuid.a /lib/liblvm.a /lib/liblvm.a(debug.o): In function `lvm_debug': debug.o(.text+0x74): undefined reference to `opt_d' /lib/liblvm.a(debug.o): In function `lvm_debug_enter': debug.o(.text+0xc4): undefined reference to `opt_d' /lib/liblvm.a(debug.o): In function `lvm_debug_leave': debug.o(.text+0x104): undefined reference to `opt_d' collect2: ld returned 1 exit status make[2]: *** [mkfs.xfs] Error 1 make[1]: *** [default] Error 2 make[1]: Leaving directory `/arc/build/xfs/cmd/xfsprogs' make: *** [built] Error 2 Debian Woody, LVM 0.9 -- Daniel Podlejski ... We come from the land of the ice and snow, From the midnight sun where the hot springs blow ... From owner-linux-xfs@oss.sgi.com Sat Jul 14 03:50:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EAoMZ09134 for linux-xfs-outgoing; Sat, 14 Jul 2001 03:50:22 -0700 Received: from router.abc (pD4B9DB69.dip.t-dialin.net [212.185.219.105]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EAoGV09107 for ; Sat, 14 Jul 2001 03:50:19 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6EAnho26161; Sat, 14 Jul 2001 12:49:44 +0200 Message-ID: <3B5023C6.5A6333BC@baldauf.org> Date: Sat, 14 Jul 2001 12:49:42 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Federico Sevilla III CC: linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <995050427.3b4f43bb56ac3@horde.leathercollection.ph> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6EAoKV09116 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Federico Sevilla III wrote: > [...] > I am of personal opinion that because XFS was designed to handle image files > and other files larger than the small ones ReiserFS was designed for, we will > see an increase in performance as size increases. For most database and data > storage applications, this should be a plus. Maybe reiserfs manages to be faster than XFS for database applications, but not by being faster at large files, but by offering sophisticated transaction support and having database objects at the file-level (one object, one file) than at the in-file-level (many objects, one file). A filesystem is just a tree-oriented database. Maybe it is more efficient to have one database (the filesystem) than having one database (application) layered on top of another database (the filesystem). But maybe XFS can provide transactions and small fs objects at the filesystem level as well? > The fact that XFS is much MUCH > slower than ReiserFS on deletes should not matter as large tree deletions > should not be a part of normal day-to-day life of a data storage partition. > > I am truly interested to find out about the benchmark results that Mike Gigante > mentioned he would post soon (on the XFS mailing list). I agree that they will > be interesting. This doesn't make me look down on ReiserFS, though. I am sure > it has its plusses. Then of course there's the fact that they're obviously > designed to handle different load and file types. > > For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great > job there. For your Samba or NFS partition, go XFS and not ReiserFS. I do not use XFS, currently. Why is XFS better for Samba? > Aside from > the fact that ReiserFS is having problems with NFS (and SFS which runs on top > of NFS), NFS has problems with ReiserFS (NFS has design bugs which do not seem to matter on other filesystems). > ReiserFS expects to have EA and ACL support only in ReiserFS v4 (which > looks exciting, BTW) which is due at least a year from now as per Hans Reiser's > estimations. > > For those interested, DARPA supposedly sponsored encryption support to be built > into ReiserFS v4. Still to be seen, of course, but I think we should all be > happy about this. Like the lead developers of both filesystems > mentioned "threads ago", XFS and ReiserFS are not competition to each other. > Instead they both provide what makes Linux a continually more viable platform > in this world where greed and closed-source applications still take the lead in > a number of ways. (Read: we're not fighting each other, we have a common alien > enemy). :) > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. Xuân. From owner-linux-xfs@oss.sgi.com Sat Jul 14 08:54:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EFsS426394 for linux-xfs-outgoing; Sat, 14 Jul 2001 08:54:28 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EFsPV26370 for ; Sat, 14 Jul 2001 08:54:25 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id RAA03938; Sat, 14 Jul 2001 17:54:14 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id RAA21640; Sat, 14 Jul 2001 17:54:14 +0200 (CEST) Date: Sat, 14 Jul 2001 17:54:14 +0200 (CEST) From: Seth Mos To: Xuan Baldauf cc: Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks In-Reply-To: <3B5023C6.5A6333BC@baldauf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Xuan Baldauf wrote: > Federico Sevilla III wrote: > > For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great > > job there. For your Samba or NFS partition, go XFS and not ReiserFS. > > I do not use XFS, currently. Why is XFS better for Samba? Because word documents average 0.1 - 1MB. > > Aside from > > the fact that ReiserFS is having problems with NFS (and SFS which runs on top > > of NFS), > > NFS has problems with ReiserFS (NFS has design bugs which do not seem to matter on > other filesystems). Dare to say that it was designed for Unix like file systems with inodes? Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Jul 14 09:08:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EG8Sw26858 for linux-xfs-outgoing; Sat, 14 Jul 2001 09:08:28 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EG8QV26839 for ; Sat, 14 Jul 2001 09:08:26 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA05115; Sat, 14 Jul 2001 18:08:24 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id SAA22110; Sat, 14 Jul 2001 18:08:24 +0200 (CEST) Date: Sat, 14 Jul 2001 18:08:24 +0200 (CEST) From: Seth Mos To: Colin Walters cc: linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 In-Reply-To: <87y9psdpcc.church.of.emacs@cis.ohio-state.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Colin Walters wrote: > When I tried to set up an 'at' command today, it told me I didn't have > permissions; this confused me until I looked at /etc/at.deny, which > was about 100 null characters. Following this, I noticed that one of > my old emails had been destroyed too. I have had this corruption using bad memory in the 2.4.0-test releases. After replacing it I have not been able to replicate this. I have seen this behaviour on the list with kernels that have been compiled with gcc-2.96-rh. What compiler did you use.? > So I wrote the attached program to search for non-empty files > consisting entirely of null characters on XFS filesystems, which I'm > posting in the hope that it will be useful for someone else. > > It revealed that my filesystem is pretty badly damaged (about 150 > files were hit), so I'll probably have to restore from backups and > switch back to ext2 for now. Have you tried running an xfs_repair -n on th filesystem to see what it thinks of it. > I'm running 2.4.6 from benh's tree on PowerPC. I believe that the original report on PPC kernels were linus based. > I did try an xfs_check on the filesystem, which reported no errors. The extended attribute of the file is empty. That's why it is also giving back NULLS. This happens during recovery IIRC. So it is not really corrupt in the sense of the checker. Did you see this after XFS recovery of the filesystem? > Let me know if there's any more debugging information I can give; I > really wish I could use XFS! I don't know if there is something we can do about this except making EA work. It would probably be moot point then. I am not sure if I am coorect on this issue though. Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Jul 14 09:25:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EGPQL27184 for linux-xfs-outgoing; Sat, 14 Jul 2001 09:25:26 -0700 Received: from router.abc (pD4B9DBFB.dip.t-dialin.net [212.185.219.251]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EGPNV27165 for ; Sat, 14 Jul 2001 09:25:24 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6EGP1o00675; Sat, 14 Jul 2001 18:25:01 +0200 Message-ID: <3B507259.4436853E@baldauf.org> Date: Sat, 14 Jul 2001 18:24:57 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Seth Mos CC: Xuan Baldauf , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6EGPPV27166 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > On Sat, 14 Jul 2001, Xuan Baldauf wrote: > > Federico Sevilla III wrote: > > > For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great > > > job there. For your Samba or NFS partition, go XFS and not ReiserFS. > > > > I do not use XFS, currently. Why is XFS better for Samba? > > Because word documents average 0.1 - 1MB. Ah. So you just mean speed (quantity), not some features (quality)- > > > > > Aside from > > > the fact that ReiserFS is having problems with NFS (and SFS which runs on top > > > of NFS), > > > > NFS has problems with ReiserFS (NFS has design bugs which do not seem to matter on > > other filesystems). > > Dare to say that it was designed for Unix like file systems with inodes? It was designed for file systems which have directories which never shrink and are searched linearily rather then by other possible indexing methods (hashes, trees, etc.). It was designed for file systems where you can assume that the same file metadata has the same position over unlimited time into the future. It was designed for file systems where you can assume that the position occupied by metadata of one file may not be occupied by metadata of another file if the one file was deleted and the other file was created, for an unlimited time into the future. Due to its "stateless" nature, its restrictrions are applied to the whole filesystem rather than to a fancy NFS server which can handle the problems on a case-by-case basis. This is because without state, there is not known when and if a nfs client will access some resource of the filesystem (again), so optimzing for the cases where you can assume that some reference handle (like inode number, directory cookie, etc) once given to an NFS client will not be reused is not possible. I hope that someday, there will be an emancipation from NFS away (or an NFS without those problems). Maybe Samba|CIFS can be a replacement someday. CIFS has some overhead, too, due to it's windows origins, but this is per packed basis and not for an unlimited time into the future. Are there alternatives? Intermezzo does not seem to be developed anymore. Is Coda usable? Does XFS have dynamically shrinking directories? If yes, how does XFS handles limited 32bit NFS cookies? > > > Cheers > Seth Xuân. From owner-linux-xfs@oss.sgi.com Sat Jul 14 09:52:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EGqmY27468 for linux-xfs-outgoing; Sat, 14 Jul 2001 09:52:48 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EGqjV27449 for ; Sat, 14 Jul 2001 09:52:46 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id SAA08024; Sat, 14 Jul 2001 18:52:43 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id SAA24003; Sat, 14 Jul 2001 18:52:43 +0200 (CEST) Date: Sat, 14 Jul 2001 18:52:42 +0200 (CEST) From: Seth Mos To: Xuan Baldauf cc: Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks In-Reply-To: <3B507259.4436853E@baldauf.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Xuan Baldauf wrote: > Seth Mos wrote: > > > On Sat, 14 Jul 2001, Xuan Baldauf wrote: > > > Federico Sevilla III wrote: > > > > For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great > > > > job there. For your Samba or NFS partition, go XFS and not ReiserFS. > > > > > > I do not use XFS, currently. Why is XFS better for Samba? > > > > Because word documents average 0.1 - 1MB. > > Ah. So you just mean speed (quantity), not some features (quality)- Yes, windows stuff tends to bloat. Most stuff placed on windows networks are things like word and excel documents which average 0.5MB and powerpoint presentations of more the 5MB. But what do you mean with quality. Either it works or it doesn't. And in my case I don't see any difference between usning Samba over NFS, XFS, ReiserFS, JFS or ext2. It's rather the samba version that counts for the amount of speed and features. > I hope that someday, there will be an emancipation from NFS away (or an NFS without > those problems). > Maybe Samba|CIFS can be a replacement someday. CIFS has some overhead, too, due to it's > windows origins, but this is per packed basis and not for an unlimited time into the > future. It's not backward compatible. Our NCR MP-RAS SVR4 unix machine can't mount CIFS shares but it can mount NFS v2 and v3. A lot of systems out there can't mount CIFS shares. > Are there alternatives? Intermezzo does not seem to be developed anymore. Is Coda > usable? Don't know > Does XFS have dynamically shrinking directories? If yes, how does XFS handles limited > 32bit NFS cookies? You will have to wait untill a XFS developer comments. I just do the FAQ, I don't do the code. Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Jul 14 10:21:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EHLIV28001 for linux-xfs-outgoing; Sat, 14 Jul 2001 10:21:18 -0700 Received: from weta.f00f.org (weta.f00f.org [203.167.249.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EHLGV27981 for ; Sat, 14 Jul 2001 10:21:17 -0700 Received: by weta.f00f.org (Postfix, from userid 1000) id 49B6E13CC6; Sun, 15 Jul 2001 05:21:16 +1200 (NZST) Date: Sun, 15 Jul 2001 05:21:16 +1200 From: Chris Wedgwood To: Xuan Baldauf Cc: Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010715052116.E7056@weta.f00f.org> References: <3B507259.4436853E@baldauf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B507259.4436853E@baldauf.org> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 14, 2001 at 06:24:57PM +0200, Xuan Baldauf wrote: I hope that someday, there will be an emancipation from NFS away (or an NFS without those problems). Maybe Samba|CIFS can be a replacement someday. CIFS has some overhead, too, due to it's windows origins, but this is per packed basis and not for an unlimited time into the future. read the first chapter of tridges' Samba book about NFS and CIFS before saying things like that :) NFS is far from perfect, CIFS isn't a solution though. --cw From owner-linux-xfs@oss.sgi.com Sat Jul 14 10:33:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EHXUH28238 for linux-xfs-outgoing; Sat, 14 Jul 2001 10:33:30 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EHXSV28219 for ; Sat, 14 Jul 2001 10:33:28 -0700 Received: from verbum.org (root@gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id NAA10219 for ; Sat, 14 Jul 2001 13:33:27 -0400 (EDT) Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by verbum.org (Postfix (Debian/GNU)) with ESMTP id 41D3C6EA9 for ; Sat, 14 Jul 2001 13:27:45 -0400 (EDT) Received: by space-ghost (Postfix (Debian/GNU), from userid 1000) id AC5CF622F55; Sat, 14 Jul 2001 13:23:59 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 References: X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Sat, 14 Jul 2001 13:23:59 -0400 In-Reply-To: (Seth Mos's message of "Sat, 14 Jul 2001 18:08:24 +0200 (CEST)") Message-ID: <87lmlrbf0w.church.of.emacs@cis.ohio-state.edu> Lines: 40 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos writes: > I have had this corruption using bad memory in the 2.4.0-test > releases. After replacing it I have not been able to replicate > this. Well, I've dropped findnull into my /etc/cron.daily, and I'll see if all the null corruption was just from my last kernel crash, or whether it is continually happening. > I have seen this behaviour on the list with kernels that have been > compiled with gcc-2.96-rh. What compiler did you use.? Reading specs from /usr/lib/gcc-lib/powerpc-linux/2.95.4/specs gcc version 2.95.4 20010703 (Debian prerelease) > Have you tried running an xfs_repair -n on th filesystem to see what > it thinks of it. I didn't get any error messages from that (how does it differ from xfs_check?). > I believe that the original report on PPC kernels were linus based. Hm, more often than not, the linus tree doesn't even compile on ppc, at least last time I checked. > The extended attribute of the file is empty. That's why it is also > giving back NULLS. This happens during recovery IIRC. So it is not > really corrupt in the sense of the checker. > > Did you see this after XFS recovery of the filesystem? Yes, the files are still filled with nulls, past reboots. > I don't know if there is something we can do about this except > making EA work. It would probably be moot point then. I am not sure > if I am coorect on this issue though. EA? From owner-linux-xfs@oss.sgi.com Sat Jul 14 10:40:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EHeWZ28477 for linux-xfs-outgoing; Sat, 14 Jul 2001 10:40:32 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EHeUV28458 for ; Sat, 14 Jul 2001 10:40:30 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA225956 for ; Sat, 14 Jul 2001 19:40:27 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id KAA57104; Sat, 14 Jul 2001 10:39:54 -0700 (PDT) Message-ID: <3B50834F.3DA6115D@sgi.com> Date: Sat, 14 Jul 2001 12:37:19 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Colin Walters CC: linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 References: <87y9psdpcc.church.of.emacs@cis.ohio-state.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Colin Walters wrote: > > When I tried to set up an 'at' command today, it told me I didn't have > permissions; this confused me until I looked at /etc/at.deny, which > was about 100 null characters. How many times has this system crashed? The only time I have seen null characters is when I had a system crash, and some files which were being actively written to came up with nulls after recovery. This is because the metadata (size) had been written out to disk, but the data itself had not. xfs_check won't find any problems with this, it's a perfectly consistent filesystem, with some files that have nothing but nulls. Just saw your note that you'll put findnull in a cron job... if you see new files showing up with these nulls on a filesystem that has been happily running along, be sure and let us know... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sat Jul 14 12:49:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EJnfx29973 for linux-xfs-outgoing; Sat, 14 Jul 2001 12:49:41 -0700 Received: from wrath.cs.utah.edu (wrath.cs.utah.edu [155.99.198.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EJmeV29936 for ; Sat, 14 Jul 2001 12:48:40 -0700 Received: from espresso.cs.utah.edu (tino.cs.utah.edu [155.99.203.177]) by wrath.cs.utah.edu (8.11.1/8.11.1) with ESMTP id f6EJgur12606; Sat, 14 Jul 2001 13:43:05 -0600 (MDT) Date: Sat, 14 Jul 2001 13:42:56 -0600 (MDT) From: Jesse Hall X-Sender: jesse@espresso.cs.utah.edu To: Daniel Podlejski cc: linux-xfs@oss.sgi.com Subject: Re: mkfs.xfs compilationa failed In-Reply-To: <20010714094121.A30307@witch.underley.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1671147979-947883600-995138759=:10924" Content-ID: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --1671147979-947883600-995138759=:10924 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: This is a problem in the lvm package, not in xfs. The attached patch fixed it for me. It's against the lvm in unstable/sid (0.9.1beta7-2.1), and it looks like the woody version is older (0.8i-1) so it may not apply cleanly, but it should be obvious what to do -- just declare "int opt_d" in some .c file, inside an "#ifdef DEBUG" block; debug.c is the obvious choice. I've filed a bug report about this. Jesse On Sat, 14 Jul 2001, Daniel Podlejski wrote: > gcc -o mkfs.xfs xfs_mkfs.o proto.o ../libxfs/.libs/libxfs.a ../libdisk/.libs/libdisk.a /usr/lib/libuuid.a /lib/liblvm.a > /lib/liblvm.a(debug.o): In function `lvm_debug': > debug.o(.text+0x74): undefined reference to `opt_d' > /lib/liblvm.a(debug.o): In function `lvm_debug_enter': > debug.o(.text+0xc4): undefined reference to `opt_d' > /lib/liblvm.a(debug.o): In function `lvm_debug_leave': > debug.o(.text+0x104): undefined reference to `opt_d' > collect2: ld returned 1 exit status > make[2]: *** [mkfs.xfs] Error 1 > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/arc/build/xfs/cmd/xfsprogs' > make: *** [built] Error 2 > > Debian Woody, LVM 0.9 > > --1671147979-947883600-995138759=:10924 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME=lvm-patch Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME=lvm-patch ZGlmZiAtTmF1ciBsdm0tMC45LjFiZXRhNy90b29scy9saWIvZGVidWcuYyBs dm0tMC45LjFiZXRhNy5uZXcvdG9vbHMvbGliL2RlYnVnLmMNCi0tLSBsdm0t MC45LjFiZXRhNy90b29scy9saWIvZGVidWcuYwlTYXQgSnVsIDE0IDEzOjEx OjE1IDIwMDENCisrKyBsdm0tMC45LjFiZXRhNy5uZXcvdG9vbHMvbGliL2Rl YnVnLmMJU2F0IEp1bCAxNCAxMzowNjozNyAyMDAxDQpAQCAtNDAsNiArNDAs NyBAQA0KICNpbmNsdWRlICJsaWJsdm0uaCINCiAjZGVmaW5lCUJVRkxFTgk1 MTINCiBzdGF0aWMgaW50IGNhbGxfZGVwdGggPSAwOw0KK2ludCBvcHRfZDsN CiANCiBzdGF0aWMgdm9pZCBfZGVidWdfb3V0KGNoYXIgKm1lc3NhZ2UpIHsN CiAgICBjaGFyIGJ1ZmZlcls2NF0sICpwdHIsIGM7DQo= --1671147979-947883600-995138759=:10924-- From owner-linux-xfs@oss.sgi.com Sat Jul 14 13:28:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EKSLP30643 for linux-xfs-outgoing; Sat, 14 Jul 2001 13:28:21 -0700 Received: from mtiwmhc23.worldnet.att.net (mtiwmhc23.worldnet.att.net [204.127.131.48]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EKSIV30623 for ; Sat, 14 Jul 2001 13:28:19 -0700 Received: from 109.newark-05-10rs.nj.dial-access.att.net ([12.89.146.109]) by mtiwmhc23.worldnet.att.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP id <20010714202743.RPNF1777.mtiwmhc23.worldnet.att.net@109.newark-05-10rs.nj.dial-access.att.net>; Sat, 14 Jul 2001 20:27:43 +0000 Received: from photino.sid.rice.edu (rjain@localhost [127.0.0.1]) by localhost (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) with ESMTP id f6EK7VEN009004; Sat, 14 Jul 2001 16:07:31 -0400 Received: (from rjain@localhost) by photino.sid.rice.edu (8.12.0.Beta10/8.12.0.Beta10/Debian 8.12.0.Beta10) id f6EK6OMV008909; Sat, 14 Jul 2001 16:06:24 -0400 Date: Sat, 14 Jul 2001 16:05:44 -0400 From: Rahul Jain To: Xuan Baldauf Cc: Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010714160544.B8623@rice.edu> Reply-To: Rahul Jain Mail-Followup-To: Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com References: <3B507259.4436853E@baldauf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B507259.4436853E@baldauf.org> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 14, 2001 at 06:24:57PM +0200, Xuan Baldauf wrote: > > > Seth Mos wrote: > > > On Sat, 14 Jul 2001, Xuan Baldauf wrote: > > > Federico Sevilla III wrote: > > > > For your Squid cache, don't go XFS, but instead go ReiserFS. It will do a great > > > > job there. For your Samba or NFS partition, go XFS and not ReiserFS. > > > > > > I do not use XFS, currently. Why is XFS better for Samba? > > > > Because word documents average 0.1 - 1MB. > > Ah. So you just mean speed (quantity), not some features (quality)- > Actually, XFS supports full ACLs, which is a useful feature when serving up samba shares, especially to NT/2k clients. From owner-linux-xfs@oss.sgi.com Sat Jul 14 13:40:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EKeBx30898 for linux-xfs-outgoing; Sat, 14 Jul 2001 13:40:11 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EKe7V30879 for ; Sat, 14 Jul 2001 13:40:08 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA01427; Sat, 14 Jul 2001 22:40:06 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA08151; Sat, 14 Jul 2001 22:40:06 +0200 (CEST) Date: Sat, 14 Jul 2001 22:40:06 +0200 (CEST) From: Seth Mos To: Colin Walters cc: linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 In-Reply-To: <87lmlrbf0w.church.of.emacs@cis.ohio-state.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Colin Walters wrote: > Seth Mos writes: > > > I have had this corruption using bad memory in the 2.4.0-test > > releases. After replacing it I have not been able to replicate > > this. > > Well, I've dropped findnull into my /etc/cron.daily, and I'll see if > all the null corruption was just from my last kernel crash, or whether > it is continually happening. I believe it only happens after recovery from a dirty fs. > > I have seen this behaviour on the list with kernels that have been > > compiled with gcc-2.96-rh. What compiler did you use.? > > Reading specs from /usr/lib/gcc-lib/powerpc-linux/2.95.4/specs > gcc version 2.95.4 20010703 (Debian prerelease) That could be a hint but it will be a difficult on to trace. I don't know if this also happens with gcc-2.91-66 which I believe it does not. > > Have you tried running an xfs_repair -n on th filesystem to see what > > it thinks of it. > > I didn't get any error messages from that (how does it differ from > xfs_check?). xfs_repair can check or repair a filesystem. I'm not sure what the differences are. The filesystem could actually be fine eventhough you see null characters in your file. > > I believe that the original report on PPC kernels were linus based. > > Hm, more often than not, the linus tree doesn't even compile on ppc, > at least last time I checked. I was afraid that was the state of the linus tree yes. The big dived of linuxPPC. > > The extended attribute of the file is empty. That's why it is also > > giving back NULLS. This happens during recovery IIRC. So it is not > > really corrupt in the sense of the checker. > > > > Did you see this after XFS recovery of the filesystem? > > Yes, the files are still filled with nulls, past reboots. The file keeps consistent during reboots, with or without reboots. It's the recovery process AFAIK that put's them there after a unclean reboot. > > I don't know if there is something we can do about this except > > making EA work. It would probably be moot point then. I am not sure > > if I am coorect on this issue though. > > EA? Extended Attributes. The file got written or touched and to disk but after recovery it was given a number of empty extended attributes. This is what you are seeing. Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Jul 14 13:56:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EKupK31298 for linux-xfs-outgoing; Sat, 14 Jul 2001 13:56:51 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EKunV31278 for ; Sat, 14 Jul 2001 13:56:49 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA04811 for ; Sat, 14 Jul 2001 13:56:47 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id NAA79733; Sat, 14 Jul 2001 13:56:11 -0700 (PDT) Message-ID: <3B50B14F.5BEB4DBF@sgi.com> Date: Sat, 14 Jul 2001 15:53:35 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos CC: Colin Walters , linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > On Sat, 14 Jul 2001, Colin Walters wrote: > > > I don't know if there is something we can do about this except > > > making EA work. It would probably be moot point then. I am not sure > > > if I am coorect on this issue though. > > > > EA? > > Extended Attributes. The file got written or touched and to disk but after > recovery it was given a number of empty extended attributes. > This is what you are seeing. Seth, I think you're getting terms confused here... extended attributes don't have anything to do with the null characters in files that have a size, but no data. Extended attributes are extra pieces of information that can be attached to a file, this is how access control lists (ACLs) are implemented in XFS, for example. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sat Jul 14 14:12:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ELCAJ31671 for linux-xfs-outgoing; Sat, 14 Jul 2001 14:12:10 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ELC8V31648 for ; Sat, 14 Jul 2001 14:12:08 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA05691; Sat, 14 Jul 2001 23:12:07 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id XAA09940; Sat, 14 Jul 2001 23:12:07 +0200 (CEST) Date: Sat, 14 Jul 2001 23:12:06 +0200 (CEST) From: Seth Mos To: Eric Sandeen cc: Colin Walters , linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 In-Reply-To: <3B50B14F.5BEB4DBF@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Eric Sandeen wrote: > Seth Mos wrote: > > > > On Sat, 14 Jul 2001, Colin Walters wrote: > > > > > I don't know if there is something we can do about this except > > > > making EA work. It would probably be moot point then. I am not sure > > > > if I am coorect on this issue though. > > > > > > EA? > > > > Extended Attributes. The file got written or touched and to disk but after > > recovery it was given a number of empty extended attributes. > > This is what you are seeing. > > Seth, I think you're getting terms confused here... extended attributes > don't have anything to do with the null characters in files that have a > size, but no data. Extended attributes are extra pieces of information > that can be attached to a file, this is how access control lists (ACLs) > are implemented in XFS, for example. Whoops, sorry. I thought it was releated. I have also asked the people at marc.theaimsgroup.com to monitor the list for a searchable archive. Cheers Seth From owner-linux-xfs@oss.sgi.com Sat Jul 14 14:38:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ELcH732205 for linux-xfs-outgoing; Sat, 14 Jul 2001 14:38:17 -0700 Received: from cis.ohio-state.edu (root@mail.cis.ohio-state.edu [164.107.115.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ELcFV32186 for ; Sat, 14 Jul 2001 14:38:16 -0700 Received: from verbum.org (root@gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id RAA14913 for ; Sat, 14 Jul 2001 17:38:14 -0400 (EDT) Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by verbum.org (Postfix (Debian/GNU)) with ESMTP id 7FA2C6EA7 for ; Sat, 14 Jul 2001 17:31:21 -0400 (EDT) Received: by space-ghost (Postfix (Debian/GNU), from userid 1000) id 79FD3622F55; Sat, 14 Jul 2001 16:05:46 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: Re: null character filesystem corruption with 2.4.6 References: <87y9psdpcc.church.of.emacs@cis.ohio-state.edu> <3B50834F.3DA6115D@sgi.com> X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Sat, 14 Jul 2001 16:05:46 -0400 In-Reply-To: <3B50834F.3DA6115D@sgi.com> (Eric Sandeen's message of "Sat, 14 Jul 2001 12:37:19 -0500") Message-ID: <87elrjb7j9.church.of.emacs@cis.ohio-state.edu> Lines: 18 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen writes: > How many times has this system crashed? The only time I have seen > null characters is when I had a system crash, and some files which > were being actively written to came up with nulls after recovery. > This is because the metadata (size) had been written out to disk, > but the data itself had not. I see. It's only crashed once. It is probably (actually, certainly) my fault that the corruption was so severe; I just exited from the kernel debugger and continued reading my email, which was about the dumbest thing I could do. Oh, well. I've learned my lesson :) So far findnull hasn't found any new nulled files, so I think I'll continue using XFS. I will let you know if it does find new ones, though. Thanks! From owner-linux-xfs@oss.sgi.com Sat Jul 14 14:40:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ELeUP32333 for linux-xfs-outgoing; Sat, 14 Jul 2001 14:40:30 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ELeTV32313 for ; Sat, 14 Jul 2001 14:40:29 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15LX99-0006Fl-00; Sun, 15 Jul 2001 09:40:19 +1200 Date: Sun, 15 Jul 2001 09:40:19 +1200 (NZST) From: Juha Saarinen To: Seth Mos cc: Colin Walters , "linux-xfs@oss.sgi.com" Subject: Re: null character filesystem corruption with 2.4.6 In-Reply-To: Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Seth Mos wrote: > > > I don't know if there is something we can do about this except > > > making EA work. It would probably be moot point then. I am not sure > > > if I am coorect on this issue though. > > > > EA? > > Extended Attributes. The file got written or touched and to disk but after > recovery it was given a number of empty extended attributes. > This is what you are seeing. Ahh... probably not. EAs are used to store additional information about files; first time I came across EAs was in OS/2, where they were used to store things like long file names and shortcut location tracking. You had to be careful to use EA-cognisant tools to manipulate files, otherwise lots of "interesting" things happened ;-). I don't believe this applies to XFS. -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Sat Jul 14 14:42:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ELgtK32471 for linux-xfs-outgoing; Sat, 14 Jul 2001 14:42:55 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ELgsV32452 for ; Sat, 14 Jul 2001 14:42:54 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15LXBV-0006Fs-00; Sun, 15 Jul 2001 09:42:45 +1200 Date: Sun, 15 Jul 2001 09:42:45 +1200 (NZST) From: Juha Saarinen To: Eric Sandeen cc: Seth Mos , Colin Walters , "linux-xfs@oss.sgi.com" Subject: Re: null character filesystem corruption with 2.4.6 In-Reply-To: <3B50B14F.5BEB4DBF@sgi.com> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 14 Jul 2001, Eric Sandeen wrote: > Seth, I think you're getting terms confused here... extended attributes > don't have anything to do with the null characters in files that have a > size, but no data. Extended attributes are extra pieces of information > that can be attached to a file, this is how access control lists (ACLs) > are implemented in XFS, for example. I didn't actually know that XFS uses EAs for ACLs. What else is stored in there? Why not do it NTFS-style and use "streams"? ;-> -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Sat Jul 14 15:42:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EMgGl02496 for linux-xfs-outgoing; Sat, 14 Jul 2001 15:42:16 -0700 Received: from cu518.adelaide.adsl.on.net (cu518.adelaide.adsl.on.net [150.101.236.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EMgCV02473 for ; Sat, 14 Jul 2001 15:42:13 -0700 Received: from ns.aus.com (laptop.ns.aus.com [10.0.2.6]) by cu518.adelaide.adsl.on.net (8.11.0/8.11.0) with ESMTP id f6F1jkq26254; Sun, 15 Jul 2001 11:15:46 +0930 Message-ID: <3B50D058.3090008@ns.aus.com> Date: Sun, 15 Jul 2001 08:36:00 +0930 From: Richard Sharpe Reply-To: rsharpe@ns.aus.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010701 X-Accept-Language: en-us MIME-Version: 1.0 To: Chris Wedgwood CC: Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B507259.4436853E@baldauf.org> <20010715052116.E7056@weta.f00f.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Chris Wedgwood wrote: > On Sat, Jul 14, 2001 at 06:24:57PM +0200, Xuan Baldauf wrote: > > I hope that someday, there will be an emancipation from NFS away > (or an NFS without those problems). Maybe Samba|CIFS can be a > replacement someday. CIFS has some overhead, too, due to it's > windows origins, but this is per packed basis and not for an > unlimited time into the future. > > read the first chapter of tridges' Samba book about NFS and CIFS > before saying things like that :) Hmmm, I don't recall that Tridge has written a Samba book. Others have though. > NFS is far from perfect, CIFS isn't a solution though. Indeed, but NFS V4 has contributions from M$ and the UNIX community and Tridge seems happy with it, the last time I spoke to him. -- Richard Sharpe, rsharpe@ns.aus.com, LPIC1 www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba in 24 Hours, Special Edition, Using Samba From owner-linux-xfs@oss.sgi.com Sat Jul 14 16:05:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6EN5o404137 for linux-xfs-outgoing; Sat, 14 Jul 2001 16:05:50 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6EN5mV04117 for ; Sat, 14 Jul 2001 16:05:48 -0700 Received: (qmail 32425 invoked from network); 14 Jul 2001 23:05:13 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 14 Jul 2001 23:05:13 -0000 Message-ID: <3B50CFF6.4BE90AB0@namesys.com> Date: Sun, 15 Jul 2001 03:04:22 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: rsharpe@ns.aus.com CC: Chris Wedgwood , Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B507259.4436853E@baldauf.org> <20010715052116.E7056@weta.f00f.org> <3B50D058.3090008@ns.aus.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Richard Sharpe wrote: > Indeed, but NFS V4 has contributions from M$ and the UNIX community and > Tridge seems happy with it, the last time I spoke to him. > > -- > Richard Sharpe, rsharpe@ns.aus.com, LPIC1 > www.samba.org, www.ethereal.com, SAMS Teach Yourself Samba > in 24 Hours, Special Edition, Using Samba They still have cookies, so it is still a braindead protocol. Hans From owner-linux-xfs@oss.sgi.com Sat Jul 14 17:57:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F0vex11198 for linux-xfs-outgoing; Sat, 14 Jul 2001 17:57:40 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F0vbV11175 for ; Sat, 14 Jul 2001 17:57:37 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id CAA28109; Sun, 15 Jul 2001 02:57:26 +0200 Date: Sun, 15 Jul 2001 02:57:25 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Xuan Baldauf Cc: Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010715025723.I5103@vestdata.no> References: <3B507259.4436853E@baldauf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <3B507259.4436853E@baldauf.org>; from Xuan Baldauf on Sat, Jul 14, 2001 at 06:24:57PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 14, 2001 at 06:24:57PM +0200, Xuan Baldauf wrote: > > > I do not use XFS, currently. Why is XFS better for Samba? > > > > Because word documents average 0.1 - 1MB. > > Ah. So you just mean speed (quantity), not some features (quality)- Also XFS supports ACLs, that may be a important feature for some windows-users. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Sat Jul 14 18:13:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F1DcD12165 for linux-xfs-outgoing; Sat, 14 Jul 2001 18:13:38 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F1DaV12145 for ; Sat, 14 Jul 2001 18:13:37 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15LaTV-0006RW-00; Sun, 15 Jul 2001 13:13:33 +1200 From: "Juha Saarinen" To: Cc: Subject: Tulip driver in 2.4.7-pre6-xfs b0rken Date: Sun, 15 Jul 2001 13:13:56 +1200 Message-ID: <003601c10ccb$6bf53150$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk It loads, and the MAC address is visible with arp, but nothing comes in or goes out. The only error messages I can see in the logs are: Jul 15 11:21:40 localhost network: Bringing up interface eth0: succeeded Jul 15 11:21:41 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 15 11:22:13 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 15 11:22:13 localhost kernel: eth0: Out-of-sync dirty pointer, 0 vs. 17. Jul 15 11:22:29 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 15 11:22:37 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out Jul 15 11:22:37 localhost kernel: eth0: Out-of-sync dirty pointer, 16 vs. 33. The problematic version: #define DRV_VERSION "0.9.15-pre6" #define DRV_RELDATE "July 2, 2001" Whereas version 0.9.15-pre5 (June 16, 2001) works fine. Just a heads-up, in case someone else with a DEC chip NIC gets bitten by this. -- Juha "One pint leads to another." From owner-linux-xfs@oss.sgi.com Sat Jul 14 20:58:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F3w1I22250 for linux-xfs-outgoing; Sat, 14 Jul 2001 20:58:01 -0700 Received: from weta.f00f.org (weta.f00f.org [203.167.249.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F3vxV22228 for ; Sat, 14 Jul 2001 20:57:59 -0700 Received: by weta.f00f.org (Postfix, from userid 1000) id 224C213D2B; Sun, 15 Jul 2001 15:57:58 +1200 (NZST) Date: Sun, 15 Jul 2001 15:57:58 +1200 From: Chris Wedgwood To: Hans Reiser Cc: rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010715155758.G7624@weta.f00f.org> References: <3B507259.4436853E@baldauf.org> <20010715052116.E7056@weta.f00f.org> <3B50D058.3090008@ns.aus.com> <3B50CFF6.4BE90AB0@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B50CFF6.4BE90AB0@namesys.com> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 15, 2001 at 03:04:22AM +0400, Hans Reiser wrote: They still have cookies, so it is still a braindead protocol. NFS tries to solve some hard-problems. IMO, requiring the server be stateless sucks, the client IMO should be responsible for holding state and reaquiring any resources should it need to. --cw From owner-linux-xfs@oss.sgi.com Sat Jul 14 21:18:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F4IC723688 for linux-xfs-outgoing; Sat, 14 Jul 2001 21:18:12 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F4IAV23669 for ; Sat, 14 Jul 2001 21:18:11 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id VAA05090 for ; Sat, 14 Jul 2001 21:18:08 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 OAA15130; Sun, 15 Jul 2001 14:16:52 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA11083; Sun, 15 Jul 2001 14:16:50 +1000 (EST) From: "Nathan Scott" Message-Id: <10107151416.ZM202004@wobbly.melbourne.sgi.com> Date: Sun, 15 Jul 2001 14:16:46 -0500 In-Reply-To: Jesse Hall "Re: mkfs.xfs compilationa failed" (Jul 14, 1:42pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Jesse Hall , Daniel Podlejski Subject: Re: mkfs.xfs compilationa failed Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 14, 1:42pm, Jesse Hall wrote: > Subject: Re: mkfs.xfs compilationa failed > > This is a problem in the lvm package, not in xfs. The attached patch fixed > it for me. It's against the lvm in unstable/sid (0.9.1beta7-2.1), and it > looks like the woody version is older (0.8i-1) so it may not apply > cleanly, but it should be obvious what to do -- just declare "int opt_d" > in some .c file, inside an "#ifdef DEBUG" block; debug.c is the obvious > choice. I've filed a bug report about this. > Yes, Martin did implement a workaround for xfsprogs already - unfortunately I broke this recently in creating libdisk. I will put a fix in shortly - thanks for reporting the problem. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sat Jul 14 21:34:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F4YQT24700 for linux-xfs-outgoing; Sat, 14 Jul 2001 21:34:26 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F4YNV24681 for ; Sat, 14 Jul 2001 21:34:24 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id GAA240208 for ; Sun, 15 Jul 2001 06:34:20 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA87450 for linux-xfs@oss.sgi.com; Sun, 15 Jul 2001 14:33:04 +1000 (EST) Date: Sun, 15 Jul 2001 14:33:04 +1000 (EST) From: Nathan Scott Message-Id: <200107150433.OAA87450@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - mkfs/Makefile Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Sat Jul 14 21:32:35 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98908a cmd/xfsprogs/mkfs/Makefile - 1.5 - fix liblvm linking problem due to libdisk code reorg. see comment in the Makefile for more details. From owner-linux-xfs@oss.sgi.com Sun Jul 15 01:44:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F8ixb09077 for linux-xfs-outgoing; Sun, 15 Jul 2001 01:44:59 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F8iuV09058 for ; Sun, 15 Jul 2001 01:44:56 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 277781D6 for ; Sun, 15 Jul 2001 16:44:54 +0800 (PHT) Date: Sun, 15 Jul 2001 16:44:57 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: [SLIGHTLY OT] XFS ACL support in Samba Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, This is slightly off-topic in that it's more about Samba than it is about XFS. I hope this will be forgiven. I know that some XFS users have gotten Samba 2.2.x to work with XFS ACLs. I can't seem to get Samba 2.2.1a to compile properly (failing in the configure stage) with ACL support. I am using Debian with the 2.4.7-pre6 kernel from the XFS CVS. I have the following packages built and installed thanks to the wonderful Debian build scripts available in the XFS CVS tree (I thought you guys were RedHat-centric, but discovering these wonderful debian build scripts in the major cmd packages made me really happy): acl-dev_1.0.8_i386.deb acl_1.0.8_i386.deb attr-dev_1.0.4_i386.deb attr_1.0.4_i386.deb xfsdump_1.0.9_i386.deb xfslibs-dev_1.3.0_i386.deb xfsprogs_1.3.0_i386.deb These were all built (including my kernel) using the Debian prerelease of gcc 2.95.4. I have the latest source package of Samba 2.2.1a (with the Debian build scripts thanks to the maintainer). I modified the line calling configure to add the --with-acl-support parameter so it now reads: [ -f source/Makefile ] || (cd source && ./configure --with-fhs \ --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba \ --with-lockdir=/var/state/sa mba --localstatedir=/var --with-netatalk \ --with-smbmount --with-pam --with-syslo g --with-sambabook \ --with-utmp --with-readline --with-acl-support) Which looks correct. Unfortunately running debian/rules build from /usr/src/samba/samba-2.2.1a yields the following: ... checking for two-argument statfs with statfs.fsize member (4.4BSD and NetBSD)... no checking for two-argument statfs with struct fs_data (Ultrix)... no checking checking if large file support can be enabled... yes checking whether to support ACLs... checking for acl_get_file in -lacl... no checking for ACL support... no checking configure summary configure: error: summary failure. Aborting config make: *** [configure-stamp] Error 1 Note: part of the snipped output reported that checks for _acl and __acl yielded in "no" results. Hmm ... I wonder what I'm doing wrong. I do believe I have all the necessary packages properly installed. The acl-dev package contains /usr/include/sys/acl.h which I think is where the file should be. I hope someone who has done this before can help me out. Also, reading material on Samba and ACLs aside from http://acl.bestbits.at/ would be really great. Thanks in advance! --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 01:58:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F8wYs09986 for linux-xfs-outgoing; Sun, 15 Jul 2001 01:58:34 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F8wVV09965 for ; Sun, 15 Jul 2001 01:58:31 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id KAA22983; Sun, 15 Jul 2001 10:58:30 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id KAA04156; Sun, 15 Jul 2001 10:58:30 +0200 (CEST) Date: Sun, 15 Jul 2001 10:58:30 +0200 (CEST) From: Seth Mos To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 15 Jul 2001, Federico Sevilla III wrote: > Hi everyone, > > This is slightly off-topic in that it's more about Samba than it is about > XFS. I hope this will be forgiven. > > I know that some XFS users have gotten Samba 2.2.x to work with XFS ACLs. > I can't seem to get Samba 2.2.1a to compile properly (failing in the > configure stage) with ACL support. I am using Debian with the 2.4.7-pre6 > kernel from the XFS CVS. I have the following packages built and installed > thanks to the wonderful Debian build scripts available in the XFS CVS tree > (I thought you guys were RedHat-centric, but discovering these wonderful > debian build scripts in the major cmd packages made me really happy): Even some SGI people run debian I guess :-) > acl-dev_1.0.8_i386.deb > acl_1.0.8_i386.deb > attr-dev_1.0.4_i386.deb > attr_1.0.4_i386.deb > xfsdump_1.0.9_i386.deb > xfslibs-dev_1.3.0_i386.deb > xfsprogs_1.3.0_i386.deb > > These were all built (including my kernel) using the Debian prerelease of > gcc 2.95.4. Should be ok. > I have the latest source package of Samba 2.2.1a (with the Debian build > scripts thanks to the maintainer). I modified the line calling configure > to add the --with-acl-support parameter so it now reads: > > [ -f source/Makefile ] || (cd source && ./configure --with-fhs \ > --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba \ > --with-lockdir=/var/state/sa mba --localstatedir=/var --with-netatalk \ > --with-smbmount --with-pam --with-syslo g --with-sambabook \ > --with-utmp --with-readline --with-acl-support) > > Which looks correct. Unfortunately running debian/rules build from > /usr/src/samba/samba-2.2.1a yields the following: > > ... > checking for two-argument statfs with statfs.fsize member (4.4BSD and NetBSD)... no > checking for two-argument statfs with struct fs_data (Ultrix)... no > checking checking if large file support can be enabled... yes > checking whether to support ACLs... checking for acl_get_file in -lacl... no > checking for ACL support... no > checking configure summary > configure: error: summary failure. Aborting config > make: *** [configure-stamp] Error 1 > > Note: part of the snipped output reported that checks for _acl and __acl > yielded in "no" results. can you locate libacl.a? Maybe the lib ended up in the wrong place. You installed all the packages referenced above? If not you can decide to fix the packages or put the dir to the lib in your /etc/ld.so.conf and run ldconfig. > Hmm ... I wonder what I'm doing wrong. I do believe I have all the > necessary packages properly installed. The acl-dev package contains > /usr/include/sys/acl.h which I think is where the file should be. Correct. > I hope someone who has done this before can help me out. Also, reading > material on Samba and ACLs aside from http://acl.bestbits.at/ would be > really great. I don't really know if there are other locations for ACL information. Cheers Seth From owner-linux-xfs@oss.sgi.com Sun Jul 15 02:19:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F9J5011785 for linux-xfs-outgoing; Sun, 15 Jul 2001 02:19:05 -0700 Received: from piro.kabuki.sfarc.net (postfix@[203.36.158.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F9J1V11766 for ; Sun, 15 Jul 2001 02:19:01 -0700 Received: by piro.kabuki.sfarc.net (Postfix, from userid 1000) id 3950214ACA3C; Sun, 15 Jul 2001 08:43:35 +1000 (EST) Date: Sun, 15 Jul 2001 08:43:34 +1000 From: Daniel Stone To: linux-xfs@oss.sgi.com Subject: OOPS under 2.4.7-pre6 Message-ID: <20010715084334.A4389@kabuki.sfarc.net> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ZPt4rx8FFjLCG7dd" Content-Disposition: inline User-Agent: Mutt/1.3.18i Organisation: Sadly lacking Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline All, Got an OOPS while running 2.4.7-pre6. Mind that I'm both tracking with CVS, and I compiled this one with gcc3, so the results will probably be useless. :) d -- Daniel Stone "can NE1 help me aim nuclear weaponz????? /MSG ME!!" --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=oops Unable to handle kernel paging request at virtual address e4454f79 printing eip: c01e6982 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010246 eax: c5c3dc00 ebx: 00000008 ecx: c445152c edx: e4454e0c esi: 00000000 edi: 00004000 ebp: c5838000 esp: c45fde1c ds: 0018 es: 0018 ss: 0018 Process qmgr (pid: 388, stackpage=c45fd000) Stack: c4454e0c c020253a e4454e0c 00000000 00000000 00004000 c5838000 c4451420 c02063bc c4454e24 c45fdf3c c45fde80 c45fde74 c4451420 c4451490 c445147c c3a7eaa0 c02091bd 00004000 00000000 c445152c 00000000 00000000 c5838000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 80 ba 6d 01 00 00 03 75 0b f6 42 5a 02 75 05 bb 04 00 00 00 --ZPt4rx8FFjLCG7dd Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=oops-trace ksymoops 2.4.1 on i586 2.4.7-pre6-xfs-gcc3. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.7-pre6-xfs-gcc3/ (default) -m /boot/System.map-2.4.7-pre6-xfs-gcc3 (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. No modules in ksyms, skipping objects Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file? Warning (compare_maps): ksyms_base symbol __VERSIONED_SYMBOL(shmem_file_setup) not found in System.map. Ignoring ksyms_base entry Reading Oops report from the terminal Unable to handle kernel paging request at virtual address e4454f79 c01e6982 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010246 eax: c5c3dc00 ebx: 00000008 ecx: c445152c edx: e4454e0c esi: 00000000 edi: 00004000 ebp: c5838000 esp: c45fde1c ds: 0018 es: 0018 ss: 0018 Process qmgr (pid: 388, stackpage=c45fd000) Stack: c4454e0c c020253a e4454e0c 00000000 00000000 00004000 c5838000 c4451420 c02063bc c4454e24 c45fdf3c c45fde80 c45fde74 c4451420 c4451490 c445147c c3a7eaa0 c02091bd 00004000 00000000 c445152c 00000000 00000000 c5838000 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 80 ba 6d 01 00 00 03 75 0b f6 42 5a 02 75 05 bb 04 00 00 00 >>EIP; c01e6982 <===== Trace; c020253a Trace; c02063bc Trace; c02091bd Trace; c02c0370 Trace; c01f9fae Trace; c01fed76 Trace; c01e6b7f Trace; c01fed8e Trace; c01fed76 Trace; c01e6b7f Trace; c01fed8e Trace; c02091bd Trace; c013642f Trace; c0139e8b Trace; c013a1fc Trace; c013a357 Trace; c013a1fc Trace; c013986b Trace; c0106b43 Code; c01e6982 0000000000000000 <_EIP>: Code; c01e6982 <===== 0: 80 ba 6d 01 00 00 03 cmpb $0x3,0x16d(%edx) <===== Code; c01e6989 7: 75 0b jne 14 <_EIP+0x14> c01e6996 Code; c01e698b 9: f6 42 5a 02 testb $0x2,0x5a(%edx) Code; c01e698f d: 75 05 jne 14 <_EIP+0x14> c01e6996 Code; c01e6991 f: bb 04 00 00 00 mov $0x4,%ebx 3 warnings issued. Results may not be reliable. --ZPt4rx8FFjLCG7dd-- From owner-linux-xfs@oss.sgi.com Sun Jul 15 02:36:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F9aUl13606 for linux-xfs-outgoing; Sun, 15 Jul 2001 02:36:30 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F9aSV13583 for ; Sun, 15 Jul 2001 02:36:28 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id C836A2E for ; Sun, 15 Jul 2001 17:06:00 +0800 (PHT) Date: Sun, 15 Jul 2001 17:06:03 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 15 Jul 2001 at 10:58, Seth Mos wrote: > Even some SGI people run debian I guess :-) I'm glad to know of that. :) > can you locate libacl.a? Maybe the lib ended up in the wrong place. There are three instances of libacl.a in my system. One is in /usr/lib/ which belongs to the acl-dev package. The other is in /usr/src/linux-2.4-xfs-20010715/cmd/acl/debian/acl-dev/usr/lib and the other is in /usr/src/linux-2.4-xfs/20010715/cmd/acl/libacl/. The libacl.a in /usr/lib is the same as the one in .../acl-dev/usr/lib but different from the one in .../libacl. I do not know why but this is what diff reported. Of course it didn't tell me what was different about them because they're binary files. > You installed all the packages referenced above? I built all the abovementioned packages using my copy of the CVS tree which is exactly what I used to build the kernel I'm running on now. I also installed all the packages I mentioned by using 'dpkg --install'. :) > If not you can decide to fix the packages or put the dir to the lib in > your /etc/ld.so.conf and run ldconfig. /etc/ld.so.conf already contains /usr/lib where libacl.a is. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 02:46:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6F9k5j14848 for linux-xfs-outgoing; Sun, 15 Jul 2001 02:46:05 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6F9k3V14828 for ; Sun, 15 Jul 2001 02:46:03 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id LAA27524; Sun, 15 Jul 2001 11:46:02 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id LAA05786; Sun, 15 Jul 2001 11:46:02 +0200 (CEST) Date: Sun, 15 Jul 2001 11:46:01 +0200 (CEST) From: Seth Mos To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 15 Jul 2001, Federico Sevilla III wrote: > On Sun, 15 Jul 2001 at 10:58, Seth Mos wrote: > > Even some SGI people run debian I guess :-) > > I'm glad to know of that. :) > > > can you locate libacl.a? Maybe the lib ended up in the wrong place. > > There are three instances of libacl.a in my system. One is in /usr/lib/ > which belongs to the acl-dev package. The other is in > /usr/src/linux-2.4-xfs-20010715/cmd/acl/debian/acl-dev/usr/lib and the > other is in /usr/src/linux-2.4-xfs/20010715/cmd/acl/libacl/. > > The libacl.a in /usr/lib is the same as the one in .../acl-dev/usr/lib but > different from the one in .../libacl. I do not know why but this is what > diff reported. Of course it didn't tell me what was different about them > because they're binary files. I thought they would/should have been the same. > > You installed all the packages referenced above? > > I built all the abovementioned packages using my copy of the CVS tree > which is exactly what I used to build the kernel I'm running on now. I > also installed all the packages I mentioned by using 'dpkg --install'. :) That should work. > > If not you can decide to fix the packages or put the dir to the lib in > > your /etc/ld.so.conf and run ldconfig. > > /etc/ld.so.conf already contains /usr/lib where libacl.a is. And you ran ldconfig? Are you sure the headers also got installed? What does configure.log say about it. I compiled a samba 2.2.1 on my testbox at work and I followed the exact same steps and it compiled flawless after installing acl and acl-devel. Cheers Seth From owner-linux-xfs@oss.sgi.com Sun Jul 15 03:02:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FA2Dw16699 for linux-xfs-outgoing; Sun, 15 Jul 2001 03:02:13 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FA29V16672 for ; Sun, 15 Jul 2001 03:02:10 -0700 Received: (qmail 17526 invoked from network); 15 Jul 2001 10:02:03 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 15 Jul 2001 10:02:03 -0000 Message-ID: <3B5169E5.827BFED@namesys.com> Date: Sun, 15 Jul 2001 14:01:09 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Chris Wedgwood CC: rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B507259.4436853E@baldauf.org> <20010715052116.E7056@weta.f00f.org> <3B50D058.3090008@ns.aus.com> <3B50CFF6.4BE90AB0@namesys.com> <20010715155758.G7624@weta.f00f.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Chris Wedgwood wrote: > > On Sun, Jul 15, 2001 at 03:04:22AM +0400, Hans Reiser wrote: > > They still have cookies, so it is still a braindead protocol. > > NFS tries to solve some hard-problems. > > IMO, requiring the server be stateless sucks, the client IMO should be > responsible for holding state and reaquiring any resources should it > need to. > > --cw Making the server stateless is wrong, making the readdir a multioperation act is wrong, but making not letting the FS use filename as a cookie and making it use 64 bit byte offsets is the most wrong thing of all. Hans From owner-linux-xfs@oss.sgi.com Sun Jul 15 04:09:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FB9fl25189 for linux-xfs-outgoing; Sun, 15 Jul 2001 04:09:41 -0700 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FB9dV25169 for ; Sun, 15 Jul 2001 04:09:39 -0700 Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id NAA06413 for ; Sun, 15 Jul 2001 13:09:32 +0200 Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.4/8.11.3) with ESMTP id f6FB9Wx25929 for ; Sun, 15 Jul 2001 13:09:32 +0200 Date: Sun, 15 Jul 2001 13:09:32 +0200 (CEST) From: Adam Cioccarelli To: Subject: growfs and mount options Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, This is not really a big problem I just thought that I should point it out. I found that I couldn't grow one of my xfs filesystems that has an external log and is mounted with the option logbufs=4, I kept getting the following error, xfs_growfs: stat64 failed on /dev/data_vg/opt_lv_log,logbufs=4: No such file or directory This confused me a bit until I noticed logbufs=4 on the end and thought, why is that there? To cut a long story short it would only work if I put logdev= last in the mount options. Adam From owner-linux-xfs@oss.sgi.com Sun Jul 15 10:52:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FHqHl17104 for linux-xfs-outgoing; Sun, 15 Jul 2001 10:52:17 -0700 Received: from mail.gmx.net (pop.gmx.de [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FHqFV17085 for ; Sun, 15 Jul 2001 10:52:16 -0700 Received: (qmail 7859 invoked by uid 0); 15 Jul 2001 17:52:09 -0000 Received: from pd904ddb6.dip.t-dialin.net (HELO powstat) (217.4.221.182) by mail.gmx.net (mail10) with SMTP; 15 Jul 2001 17:52:09 -0000 From: "christian mueller" To: jijo@leathercollection.ph Date: Sun, 15 Jul 2001 19:25:21 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba CC: linux-xfs@oss.sgi.com, knuffie@xs4all.nl Message-ID: <3B51EE21.22982.3FC1ED@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, there is one thing left. have you checked that the chacl command works on your XFS ? (only a guess) is [x] POSIX Access Control List support enabled in you kernelconfig? i am running vanilla 2.4.6 patched with SGIs XFS-patch (linux-2.4.6-xfs-07052001.patch.bz2) samba-2.2.1a (nexus-tools work under w9x) no problems so far. chris From owner-linux-xfs@oss.sgi.com Sun Jul 15 10:59:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FHxGw17284 for linux-xfs-outgoing; Sun, 15 Jul 2001 10:59:16 -0700 Received: from hotmail.com (f258.law14.hotmail.com [64.4.20.133]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FHxFV17265 for ; Sun, 15 Jul 2001 10:59:15 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 15 Jul 2001 10:59:10 -0700 Received: from 207.241.189.250 by lw14fd.law14.hotmail.msn.com with HTTP; Sun, 15 Jul 2001 17:59:10 GMT X-Originating-IP: [207.241.189.250] From: "Eugeny Balakhonov" To: linux-xfs@oss.sgi.com Subject: Last version of XFS Date: Sun, 15 Jul 2001 20:59:10 +0300 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 15 Jul 2001 17:59:10.0375 (UTC) FILETIME=[D9662370:01C10D57] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello! Last version of XFS is 1.0? Only for 2.4.3 kernel? ;( Best regars Eugeny _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. From owner-linux-xfs@oss.sgi.com Sun Jul 15 11:34:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FIYMn17654 for linux-xfs-outgoing; Sun, 15 Jul 2001 11:34:22 -0700 Received: from mail.gmx.net (pop.gmx.net [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FIYKV17635 for ; Sun, 15 Jul 2001 11:34:20 -0700 Received: (qmail 26465 invoked by uid 0); 15 Jul 2001 18:34:14 -0000 Received: from pd904ddb6.dip.t-dialin.net (HELO powstat) (217.4.221.182) by mail.gmx.net (mp001-rz3) with SMTP; 15 Jul 2001 18:34:14 -0000 From: "christian mueller" To: johnball80@hotmail.com Date: Sun, 15 Jul 2001 20:07:29 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Last version of XFS CC: linux-xfs@oss.sgi.com Message-ID: <3B51F801.9886.6655CE@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, the webpage is currently not up to date. the latest 'official' release is XFS 1.0.1 --ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/-- this is up to kernel 2.4.5. further information is in the README file on ftp and on this mailing list (just browse). chris From owner-linux-xfs@oss.sgi.com Sun Jul 15 12:05:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FJ5hk18032 for linux-xfs-outgoing; Sun, 15 Jul 2001 12:05:43 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FJ5fV18013 for ; Sun, 15 Jul 2001 12:05:41 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA29439; Sun, 15 Jul 2001 21:05:39 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA28075; Sun, 15 Jul 2001 21:05:38 +0200 (CEST) Date: Sun, 15 Jul 2001 21:05:38 +0200 (CEST) From: Seth Mos To: Eugeny Balakhonov cc: linux-xfs@oss.sgi.com Subject: Re: Last version of XFS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 15 Jul 2001, Eugeny Balakhonov wrote: > Hello! > > Last version of XFS is 1.0? Only for 2.4.3 kernel? > ;( 1.0.1 is out which is an update to 1.0. It has both a 2.4.3 redhat kernel and a 2.4.5 linus based kernel. If you need newer then that you can use the CVS version which is 2.4.7-pre6 linus based kernel. You can also find patches on the FTP site for 2.4.6 kernel in ftp://oss.sgi.com/projects/xfs/download/patches/ Cheers Seth From owner-linux-xfs@oss.sgi.com Sun Jul 15 13:39:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FKdQG22902 for linux-xfs-outgoing; Sun, 15 Jul 2001 13:39:26 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FKdOV22879 for ; Sun, 15 Jul 2001 13:39:24 -0700 Received: from relay1.corp.sgi.com (corp.sgi.com [198.29.75.13]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAB03061 for ; Sun, 15 Jul 2001 13:39:20 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id NAA15405; Sun, 15 Jul 2001 13:38:50 -0700 (PDT) Message-ID: <3B51FEBA.A753EEE4@sgi.com> Date: Sun, 15 Jul 2001 15:36:10 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Adam Cioccarelli CC: linux-xfs@oss.sgi.com Subject: Re: growfs and mount options References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adam Cioccarelli wrote: > This confused me a bit until I noticed logbufs=4 on the end and thought, > why is that there? To cut a long story short it would only work if I put > logdev= last in the mount options. Yep, I can duplicate this here. It looks like the "hasmntopt" function that growfs uses isn't parsing things correctly 138 if ((logdev = hasmntopt(mnt, "logdev="))) { (gdb) print logdev $10 = 0x807a7f3 "logdev=/dev/sda3,logbufs=4" I'll take a look at this tomorrow, unless the Australians beat me to it... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 15:40:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6FMeQx30710 for linux-xfs-outgoing; Sun, 15 Jul 2001 15:40:26 -0700 Received: from postfix.informatik.uni-bonn.de (postfix.informatik.uni-bonn.de [131.220.131.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6FMeNV30679 for ; Sun, 15 Jul 2001 15:40:23 -0700 Received: from informatik.uni-bonn.de (pD900BAC8.dip.t-dialin.net [217.0.186.200]) by postfix.informatik.uni-bonn.de (Postfix) with ESMTP id E9B6070C72 for ; Mon, 16 Jul 2001 00:40:19 +0200 (MEST) (envelope-from brill@informatik.uni-bonn.de) (envelope-to linux-xfs@oss.sgi.com) (1) (internal use: ta=1, tu=1, te=1, am=P, au=brill) Message-ID: <3B521BF9.72879C44@informatik.uni-bonn.de> Date: Mon, 16 Jul 2001 00:40:57 +0200 From: Gerwin Brill X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-xfs i586) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: mounting XFS fails Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I've tried to mount an old IRIX 5.x disk using both your current kernel patch and the xfs enabled kernel souces (kernel 2.4.6). In all cases i get "wrong fs type, bad option, bad superblock on /dev/sdb1, or too many mounted file systems" when trying to mount with "mount -t xfs /dev/sdb1 /dir" xfs_repair can not find secondary superblock, fdisk gives the following informations on the disk ----- partitions ----- Device Info Start End Sectors Id System /dev/sdb1 boot 5 3424 1846576 a SGI xfs /dev/sdb2 swap 3425 3804 205408 3 SGI raw /dev/sdb9 0 4 2620 0 SGI volhdr /dev/sdb11 0 3804 2054604 6 SGI volume ----- bootinfo ----- Bootfile: /unix ----- directory entries ----- 0: sgilabel sector 2 size 512 1: sash sector 4 size 140800 2: ide sector 558 size 977920 Is there anything obvious I am missing? Regards Gerwin From owner-linux-xfs@oss.sgi.com Sun Jul 15 17:09:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G09Kc05053 for linux-xfs-outgoing; Sun, 15 Jul 2001 17:09:20 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G09IV05031 for ; Sun, 15 Jul 2001 17:09:18 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id RAA06611 for ; Sun, 15 Jul 2001 17:06:47 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id RAA47163; Sun, 15 Jul 2001 17:08:43 -0700 (PDT) Message-ID: <3B522FEA.37E14559@sgi.com> Date: Sun, 15 Jul 2001 19:06:02 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Adam Cioccarelli CC: linux-xfs@oss.sgi.com Subject: Re: growfs and mount options References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adam Cioccarelli wrote: > To cut a long story short it would only work if I put > logdev= last in the mount options. This seems to fix it; the code was parsing the mount options looking for " " as a delimiter, I added a comma and things seem happy again. --- xfs_growfs.c.orig Sun Jul 15 19:03:57 2001 +++ xfs_growfs.c Sun Jul 15 19:04:24 2001 @@ -137,11 +137,11 @@ datadev = mnt->mnt_fsname; if ((logdev = hasmntopt(mnt, "logdev="))) { logdev += 7; - logend = strtok(logdev, " "); + logend = strtok(logdev, " ,"); } if ((rtdev = hasmntopt(mnt, "rtdev="))) { rtdev += 6; - rtend = strtok(rtdev, " "); + rtend = strtok(rtdev, " ,"); } /* Do this only after we've finished processing mount options */ -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 17:59:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G0xBH08078 for linux-xfs-outgoing; Sun, 15 Jul 2001 17:59:11 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G0x2V08047 for ; Sun, 15 Jul 2001 17:59:05 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 08EC37D for ; Mon, 16 Jul 2001 08:58:50 +0800 (PHT) Date: Mon, 16 Jul 2001 08:58:54 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 15 Jul 2001 at 11:46, Seth Mos wrote: > I thought they would/should have been the same. Uh oh. I will probably do a 'dpkg --purge' of all my XFS-related packages (the kernel is not built as a package so that won't hurt my operations at all), rebuild all the packages from the sources using the Debian scripts, and then reinstall. I will let the list know if the libacl.a's match this time (and ultimately if I can compile Samba 2.2.1a with ACL support). > And you ran ldconfig? /usr/lib has been in my ld.so.conf for quite awhile now, and I've ran ldconfig a number of times since I put it there. :) > Are you sure the headers also got installed? What does configure.log > say about it. After doing a rebuild and reinstall of my XFS packages I will attempt to build Samba 2.2.1a again and will let you know what configure.log says that seems relevant to the situation. Thanks for the tips! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 18:00:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G10mo08304 for linux-xfs-outgoing; Sun, 15 Jul 2001 18:00:48 -0700 Received: from gusi.leathercollection.ph ([202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G10dV08274 for ; Sun, 15 Jul 2001 18:00:41 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 27F687D for ; Mon, 16 Jul 2001 09:00:27 +0800 (PHT) Date: Mon, 16 Jul 2001 09:00:31 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: <3B51EE21.22982.3FC1ED@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 15 Jul 2001 at 19:25, christian mueller wrote: > there is one thing left. have you checked that the chacl command works > on your XFS ? Yes, it does. 'chacl -l' shows empty arrays per directory/file in the current. :) > (only a guess) is [x] POSIX Access Control List support enabled in you > kernelconfig? Yup yup yup. I've got Quotas and XFS quotas enabled as well. :-) > i am running vanilla 2.4.6 patched with SGIs XFS-patch > (linux-2.4.6-xfs-07052001.patch.bz2) samba-2.2.1a (nexus-tools work > under w9x) Argh ... BTW this is really off-topic but what appropriate smb.conf flags did you put to enable nexus-tools to work on the ACLs of the Samba shares? :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 18:36:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G1aiE11053 for linux-xfs-outgoing; Sun, 15 Jul 2001 18:36:44 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G1acV11028 for ; Sun, 15 Jul 2001 18:36:38 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id SAA01403 for ; Sun, 15 Jul 2001 18:36:31 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 LAA19859; Mon, 16 Jul 2001 11:35:18 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA93140; Mon, 16 Jul 2001 11:35:16 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107161135.ZM212056@wobbly.melbourne.sgi.com> Date: Mon, 16 Jul 2001 11:35:15 +1000 In-Reply-To: Seth Mos "Re: [SLIGHTLY OT] XFS ACL support in Samba" (Jul 15, 11:46am) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Seth Mos , Federico Sevilla III Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba Cc: Linux XFS Mailing List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 15, 4:44pm, Federico Sevilla III wrote: > Subject: [SLIGHTLY OT] XFS ACL support in Samba > ... > I have the latest source package of Samba 2.2.1a (with the Debian build > scripts thanks to the maintainer). I modified the line calling configure > to add the --with-acl-support parameter so it now reads: > > [ -f source/Makefile ] || (cd source && ./configure --with-fhs \ > --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba \ > --with-lockdir=/var/state/sa mba --localstatedir=/var --with-netatalk \ > --with-smbmount --with-pam --with-syslo g --with-sambabook \ > --with-utmp --with-readline --with-acl-support) > did you cut&paste the above? ie. do you really have: "--with-lockdir=/var/state/sa mba" ^^^^^^ and "--with-syslo g" ^^^^ as you've written above? that would confuse "configure" no end. I just tried the following recipe and it Works For Me (tm). troppo# apt-get source samba [ build acl debs, then: ] troppo# dpkg -i ./acl-dev_1.0.8_i386.deb ./acl_1.0.8_i386.deb ... troppo# cd samba-2.2.1a [ vi ./debian/rules -> added --with-acl-support (see below) ] troppo# dpkg-buildpackage dpkg-buildpackage: source package is samba dpkg-buildpackage: source version is 2.2.1a-1 dpkg-buildpackage: source maintainer is Eloy A. Paris dpkg-buildpackage: host architecture is i386 ... debian/rules build dh_testdir # Add here commands to configure the package. [ -f source/Makefile ] || (cd source && ./configure --with-fhs --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba --with-lockdir=/var/state/samba --localstatedir=/var --with-netatalk --with-smbmount --with-pam --with-syslog --with-sambabook --with-utmp --with-readline --with-acl-support) creating cache ./config.cache checking for gcc... gcc ... checking for sys/syscall.h... yes checking for sys/acl.h... yes checking for sys/cdefs.h... yes ... checking statvfs64 function (SVR4)... yes checking checking if large file support can be enabled... yes checking whether to support ACLs... checking for acl_get_file in -lacl... yes checking for ACL support... yes Using posix ACLs checking for acl_get_perm_np... no checking configure summary configure OK ...[continues with build]... So that seems to have done the trick. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 15 18:48:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G1mVZ12203 for linux-xfs-outgoing; Sun, 15 Jul 2001 18:48:31 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G1mTV12181 for ; Sun, 15 Jul 2001 18:48:29 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id DAA263997 for ; Mon, 16 Jul 2001 03:48:23 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA17909; Mon, 16 Jul 2001 11:47:05 +1000 (EST) Date: Mon, 16 Jul 2001 11:47:05 +1000 From: Timothy Shimmin To: Juha Saarinen Cc: Eric Sandeen , Seth Mos , Colin Walters , "linux-xfs@oss.sgi.com" Subject: Re: null character filesystem corruption with 2.4.6 Message-ID: <20010716114705.Z11622@boing.melbourne.sgi.com> References: <3B50B14F.5BEB4DBF@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: ; from juha@saarinen.org on Sun, Jul 15, 2001 at 09:42:45AM +1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Juha, On Sun, Jul 15, 2001 at 09:42:45AM +1200, Juha Saarinen wrote: > On Sat, 14 Jul 2001, Eric Sandeen wrote: > > > Seth, I think you're getting terms confused here... extended attributes > > don't have anything to do with the null characters in files that have a > > size, but no data. Extended attributes are extra pieces of information > > that can be attached to a file, this is how access control lists (ACLs) > > are implemented in XFS, for example. > > I didn't actually know that XFS uses EAs for ACLs. Sure does. > What else is stored in there? DMAPI/DMF attributes. In IRIX we also use it for Capabilities and Manadatory Access Control info. --Tim From owner-linux-xfs@oss.sgi.com Sun Jul 15 18:59:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G1xkO12924 for linux-xfs-outgoing; Sun, 15 Jul 2001 18:59:46 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G1xbV12899 for ; Sun, 15 Jul 2001 18:59:40 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 07CD8B7 for ; Mon, 16 Jul 2001 09:59:27 +0800 (PHT) Date: Mon, 16 Jul 2001 09:59:31 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: DMAPI (was: null character filesystem corruption with 2.4.6) In-Reply-To: <20010716114705.Z11622@boing.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 16 Jul 2001 at 11:47, Timothy Shimmin wrote: > > What else is stored in there? > DMAPI/DMF attributes. Aside from what is in the Configure.help documentation, what exactly are DMAPI/DMF attributes and for what applications are these recommended to be enabled? My current kernel has this disabled and I did not build/install the dmapi cmd packages. I disabled DMAPI because I did not think I had a system that fit in the description "hierarchical storage management systems". Maybe someone can help me out and explain DMAPI/DMF and how one can benefit from it? :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 19:04:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G24Fg13385 for linux-xfs-outgoing; Sun, 15 Jul 2001 19:04:15 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G242V13352 for ; Sun, 15 Jul 2001 19:04:04 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 679B6B7 for ; Mon, 16 Jul 2001 10:03:45 +0800 (PHT) Date: Mon, 16 Jul 2001 10:03:49 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: A little bit more on mount options Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I have some minor questions as far as the tuning mount options are concerned. o nodiratime is not listed as one of the mount options in the mount manpage or in Documentation/filesystems/xfs.txt. Does XFS know about this at all? Or does noatime do the job for files as well as directories? o quota, usrquota, and uqnoenforce are all listed in one "entry". Where can I get more information on working quotas and XFS? And are these flags equivalent to each other or do they do different things? o kio looks interesting, is it significant to issue this or does XFS automatically choose whether to use kiobufs or buffer heads depending on the current system configuration hence being auto-optimizing? Thanks a lot for your patience everyone! --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 19:11:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G2BmH14055 for linux-xfs-outgoing; Sun, 15 Jul 2001 19:11:48 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G2BcV14025 for ; Sun, 15 Jul 2001 19:11:41 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 502104D4 for ; Mon, 16 Jul 2001 10:11:26 +0800 (PHT) Date: Mon, 16 Jul 2001 10:11:25 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: <10107161135.ZM212056@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 16 Jul 2001 at 11:35, Nathan Scott wrote: > did you cut&paste the above? ie. do you really have: > "--with-lockdir=/var/state/sa mba" > and "--with-syslo g" > ^^^^ I did a cut and paste but reformatted it a little after to fit nicely in my Pine screen and it looks like I missed out on a little. No, I don't have those spaces in the configure line. > troppo# dpkg-buildpackage Ahh, I learn something new everyday. I officially love Debian. ;> I ran dpkg-buildpackage and found out that I did not have some required dev packages: dpkg-checkbuilddeps: Unmet build dependencies: libpam0g-dev, libreadline4-dev, libcupsys2-dev I'm apt-getting those now and will do a Samba configure again. Hopefully it will work. Thank you everyone for helping me out with my not-exactly-XFS-related problems. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 15 20:04:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G34Uu18552 for linux-xfs-outgoing; Sun, 15 Jul 2001 20:04:30 -0700 Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G34RV18533 for ; Sun, 15 Jul 2001 20:04:27 -0700 Received: from walt400.localhost (user-uini6c1.dsl.mindspring.com [165.121.25.129]) by mclean.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id XAA02977 for ; Sun, 15 Jul 2001 23:04:25 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by walt400.localhost (Postfix) with ESMTP id AAF82A00B03; Sun, 15 Jul 2001 20:07:40 -0700 (PDT) Subject: Re: mounting XFS fails From: Walt H To: Gerwin Brill Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B521BF9.72879C44@informatik.uni-bonn.de> References: <3B521BF9.72879C44@informatik.uni-bonn.de> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 15 Jul 2001 20:07:40 -0700 Message-Id: <995252860.20116.0.camel@walt400.localhost> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 00:40:57 +0200, Gerwin Brill wrote: > Hi, > > I've tried to mount an old IRIX 5.x disk using both your current kernel > patch and the xfs enabled kernel souces (kernel 2.4.6). In all cases i > get "wrong fs type, bad option, bad superblock on /dev/sdb1, or too many > mounted file systems" when trying to mount with "mount -t xfs /dev/sdb1 > /dir" > > xfs_repair can not find secondary superblock, > > fdisk gives the following informations on the disk > > > ----- partitions ----- > Device Info Start End Sectors Id System > /dev/sdb1 boot 5 3424 1846576 a SGI xfs > /dev/sdb2 swap 3425 3804 205408 3 SGI raw > /dev/sdb9 0 4 2620 0 SGI volhdr > /dev/sdb11 0 3804 2054604 6 SGI volume > ----- bootinfo ----- > Bootfile: /unix > ----- directory entries ----- > 0: sgilabel sector 2 size 512 > 1: sash sector 4 size 140800 > 2: ide sector 558 size 977920 > > Is there anything obvious I am missing? > > Regards > Gerwin Did you remember to enable SGI partition support in the kernel config? I don't think it's enabled by default. That's all I can think of. Hope that helps. -Walt From owner-linux-xfs@oss.sgi.com Sun Jul 15 20:09:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G39S818980 for linux-xfs-outgoing; Sun, 15 Jul 2001 20:09:28 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G39RV18959 for ; Sun, 15 Jul 2001 20:09:27 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id UAA06301 for ; Sun, 15 Jul 2001 20:09:22 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 NAA20434; Mon, 16 Jul 2001 13:08:09 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id NAA03660; Mon, 16 Jul 2001 13:08:08 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107161308.ZM214734@wobbly.melbourne.sgi.com> Date: Mon, 16 Jul 2001 13:08:06 +1000 In-Reply-To: Federico Sevilla III "A little bit more on mount options" (Jul 16, 10:03am) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Federico Sevilla III , Linux XFS Mailing List Subject: Re: A little bit more on mount options Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 16, 10:03am, Federico Sevilla III wrote: > Subject: A little bit more on mount options > Hi everyone, > > I have some minor questions as far as the tuning mount options are > concerned. > > o nodiratime is not listed as one of the mount options in the mount > manpage or in Documentation/filesystems/xfs.txt. Does XFS know about this > at all? Or does noatime do the job for files as well as directories? > I'm not sure - Steve will know. > o quota, usrquota, and uqnoenforce are all listed in one "entry". Where > can I get more information on working quotas and XFS? And are these flags > equivalent to each other or do they do different things? > quota == usrquota != uqnoenforce. see README.quota in the xfsprogs package. > o kio looks interesting, is it significant to issue this or does XFS > automatically choose whether to use kiobufs or buffer heads depending on > the current system configuration hence being auto-optimizing? This mount option is no longer supported in XFS. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 15 21:55:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G4tl326139 for linux-xfs-outgoing; Sun, 15 Jul 2001 21:55:47 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G4tjV26119 for ; Sun, 15 Jul 2001 21:55:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id VAA03528 for ; Sun, 15 Jul 2001 21:55:32 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id XAA2439121 for ; Sun, 15 Jul 2001 23:53:59 -0500 (CDT) Received: from chuckle.americas.sgi.com (IDENT:root@chuckle.americas.sgi.com [128.162.211.44]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id XAA51333 for ; Sun, 15 Jul 2001 23:53:59 -0500 (CDT) Received: (from sandeen@localhost) by chuckle.americas.sgi.com (8.11.2/8.11.2) id f6G4rwI11132 for linux-xfs@oss.sgi.com; Sun, 15 Jul 2001 23:53:58 -0500 Date: Sun, 15 Jul 2001 23:53:58 -0500 From: Eric Sandeen Message-Id: <200107160453.f6G4rwI11132@chuckle.americas.sgi.com> Subject: TAKE - Fix xfs_growfs device extraction Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We were parsing mount options by splitting tokens on " " while Linux mount separates options by "," - so when xfs_growfs tried to identify the external log or realtime device, it got any following options as part of the device string (i.e. logdev looked like "/dev/sda1,logbufs=4"). Splitting mount options on "," solves this (but left the " " in for good measure.) Date: Sun Jul 15 21:48:00 PDT 2001 Workarea: chuckle.americas.sgi.com:/export/xfs1/eric/linux-2.4-xfs/workarea The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98916a cmd/xfsprogs/growfs/xfs_growfs.c - 1.5 - Correct parsing of mount options from hasmntopt() - parse on "," to split out individual mount options. From owner-linux-xfs@oss.sgi.com Sun Jul 15 22:49:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G5nVE30837 for linux-xfs-outgoing; Sun, 15 Jul 2001 22:49:31 -0700 Received: from mout1.freenet.de (exim@mout1.freenet.de [194.97.50.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G5nSV30817 for ; Sun, 15 Jul 2001 22:49:28 -0700 Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.30 #3) id 15M1G2-0000hQ-00 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 07:49:26 +0200 Received: from b6e73.pppool.de ([213.7.110.115] helo=lx1.thhmaus.de) by mx1.freenet.de with esmtp (Exim 3.30 #3) id 15M1G1-00088P-00 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 07:49:26 +0200 Subject: xfsdump on alpha From: ThH To: linux-xfs@oss.sgi.com Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 07:53:20 +0200 Message-Id: <995262801.828.0.camel@lx1.thhmaus.de> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've tried xfsdump-1.0.11 on my alpha. But there is the Assertion problem again. xfsdump: version 3.0 - Running single-threaded xfsdump: global.c:82 global_hdr_alloc: Assertion `sizeof( time_t ) == 4' failed. Aborted (core dumped) On alpha it is 8 instead of 4. I had corected this one Assertion manualy, but there are some others yet I don't know. ThH From owner-linux-xfs@oss.sgi.com Sun Jul 15 22:56:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G5uWx31612 for linux-xfs-outgoing; Sun, 15 Jul 2001 22:56:32 -0700 Received: from mout0.freenet.de (exim@mout0.freenet.de [194.97.50.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G5uVV31592 for ; Sun, 15 Jul 2001 22:56:31 -0700 Received: from [194.97.50.136] (helo=mx3.freenet.de) by mout0.freenet.de with esmtp (Exim 3.30 #3) id 15M1Mr-0007HO-00 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 07:56:29 +0200 Received: from b6e73.pppool.de ([213.7.110.115] helo=lx1.thhmaus.de) by mx3.freenet.de with esmtp (Exim 3.30 #3) id 15M1Mr-0002pk-00 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 07:56:29 +0200 Subject: xfsdump on alpha From: ThH To: linux-xfs@oss.sgi.com Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 08:00:24 +0200 Message-Id: <995263225.940.0.camel@lx1.thhmaus.de> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've tried xfsdump-1.0.11, but there is the Assertion problem yet. Look at this: xfsdump: version 3.0 - Running single-threaded xfsdump: global.c:82 global_hdr_alloc: Assertion `sizeof( time_t ) == 4' failed. Aborted (core dumped) I've changed this one maunaly from 4 to 8, but there are others yet I don't know to handle. ThH From owner-linux-xfs@oss.sgi.com Sun Jul 15 23:03:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G635u32512 for linux-xfs-outgoing; Sun, 15 Jul 2001 23:03:05 -0700 Received: from ms.svkuh.cz (ms.svkuh.cz [217.112.161.36]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G632V32489 for ; Sun, 15 Jul 2001 23:03:02 -0700 Received: from w102.svkuh.cz (w102.svkuh.cz [192.168.10.102]) by ms.svkuh.cz (Postfix) with SMTP id D6C40FFBA for ; Mon, 16 Jul 2001 08:03:00 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-2" From: David =?iso-8859-2?q?Luka=B9t=EDk?= To: linux-xfs@oss.sgi.com Subject: Lost data on XFS Date: Mon, 16 Jul 2001 08:03:00 +0200 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01071608030000.29569@w102.svkuh.cz> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have a problem with data on XFS. I find, that after reboot data are 14 days old. All files which were removed, added or modified are in the state before 14 days. It seems the data were rolled back, but I don't why. I don't know where the system find those data, because server was restarted 2 days before this disaster and everything was all right. I think, that all data are saved on the disk in the time of reboot. I have backup of the data, but I want to know what's happened. This happened in Friday. Regards, David Lukastik P.S.: Excuse my English. English is not my native language. From owner-linux-xfs@oss.sgi.com Sun Jul 15 23:18:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G6IYs01742 for linux-xfs-outgoing; Sun, 15 Jul 2001 23:18:34 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G6IWV01723 for ; Sun, 15 Jul 2001 23:18:32 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id XAA03324 for ; Sun, 15 Jul 2001 23:16:02 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 QAA21589; Mon, 16 Jul 2001 16:17:14 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA03748; Mon, 16 Jul 2001 16:17:13 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107161617.ZM208491@wobbly.melbourne.sgi.com> Date: Mon, 16 Jul 2001 16:17:12 +1000 In-Reply-To: ThH "xfsdump on alpha" (Jul 16, 7:53am) References: <995262801.828.0.camel@lx1.thhmaus.de> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: ThH , linux-xfs@oss.sgi.com Subject: Re: xfsdump on alpha Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 16, 7:53am, ThH wrote: > Subject: xfsdump on alpha > I've tried xfsdump-1.0.11 on my alpha. But there is the Assertion > problem again. > > xfsdump: version 3.0 - Running single-threaded > xfsdump: global.c:82 global_hdr_alloc: Assertion `sizeof( time_t ) == 4' > failed. > Aborted (core dumped) > > On alpha it is 8 instead of 4. > > I had corected this one Assertion manualy, Changing just the assert doesn't seem like the right thing to do - this looks like a data structure which gets written onto the tape, so it needs to be 4 bytes long. Will require an audit of the xfs{dump/restore} code to check all of the uses of time_t, I guess - does that sound right, Ivan/Tim? > but there are some others yet I don't know. Probably are. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 15 23:42:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G6gZo04239 for linux-xfs-outgoing; Sun, 15 Jul 2001 23:42:35 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G6gWV04215 for ; Sun, 15 Jul 2001 23:42:32 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id IAA269851 for ; Mon, 16 Jul 2001 08:42:27 +0200 (CEST) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id QAA21701; Mon, 16 Jul 2001 16:41:11 +1000 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id QAA02910; Mon, 16 Jul 2001 16:41:11 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Mon, 16 Jul 2001 16:41:10 +1000 To: ThH cc: Subject: Re: xfsdump on alpha In-Reply-To: <10107161617.ZM208491@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 16 Jul 2001, Nathan Scott wrote: > hi, > > On Jul 16, 7:53am, ThH wrote: > > Subject: xfsdump on alpha > > I've tried xfsdump-1.0.11 on my alpha. But there is the Assertion > > problem again. > > > > xfsdump: version 3.0 - Running single-threaded > > xfsdump: global.c:82 global_hdr_alloc: Assertion `sizeof( time_t ) == 4' > > failed. > > Aborted (core dumped) > > > > On alpha it is 8 instead of 4. > > > > I had corected this one Assertion manualy, > > Changing just the assert doesn't seem like the right thing > to do - this looks like a data structure which gets written > onto the tape, so it needs to be 4 bytes long. Will require > an audit of the xfs{dump/restore} code to check all of the > uses of time_t, I guess - does that sound right, Ivan/Tim? Sounds right to me. If you changed the header to include 8 byte time_t your dumps would be incompatible with anyone elses. However, you may not care about that so if it works, it may be fine for you. Just be sure not to lose your version of the source and binaries! If compatibilty is an issue, then you will need to do as Nathan suggests, and check every use of time_t in the code, and do conversions where appropriate. Unfortunately, we don't have the hardware nor people to port or test an alpha version, although, as always, we'd be happy to consider including any patches submitted to us. :) Ivan -- Ivan Rayner ivanr@melbourne.sgi.com From owner-linux-xfs@oss.sgi.com Mon Jul 16 00:19:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G7Jsb07171 for linux-xfs-outgoing; Mon, 16 Jul 2001 00:19:54 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G7JpV07151 for ; Mon, 16 Jul 2001 00:19:51 -0700 Received: (qmail 9254 invoked by uid 8); 16 Jul 2001 07:19:49 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: xfs on notebooks (noflushd etc.) Date: Sun, 15 Jul 2001 18:51:02 +0200 Organization: spoiled dot org Lines: 14 Distribution: local Message-ID: Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.6-pre7-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk just out of curiousity: how does xfs interact with things like noflushd which reduce the disk flushing for more effective ide poweroff possibilities ... is the flushing below the fs layer so that it should all work transparently or may it result in problems with xfs (or journaling fs in general)? a lot of thanks in advance t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Mon Jul 16 00:30:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G7U7h07816 for linux-xfs-outgoing; Mon, 16 Jul 2001 00:30:07 -0700 Received: from mail.gmx.net (mail.gmx.de [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G7U4V07797 for ; Mon, 16 Jul 2001 00:30:05 -0700 Received: (qmail 27802 invoked by uid 0); 16 Jul 2001 07:29:58 -0000 Received: from unknown (HELO gmx.de) (195.227.114.2) by mail.gmx.net (mp005-rz3) with SMTP; 16 Jul 2001 07:29:58 -0000 Message-ID: <3B52989F.AE251745@gmx.de> Date: Mon, 16 Jul 2001 09:32:47 +0200 From: Gerwin Brill Reply-To: brill@informatik.uni-bonn.de X-Mailer: Mozilla 4.73 [de] (WinNT; U) X-Accept-Language: de MIME-Version: 1.0 To: Walt H CC: linux-xfs@oss.sgi.com Subject: Re: Re: mounting XFS fails References: <3B521BF9.72879C44@informatik.uni-bonn.de> <995252860.20116.0.camel@walt400.localhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Walt H schrieb: > On 16 Jul 2001 00:40:57 +0200, Gerwin Brill wrote: > > Hi, > > > > I've tried to mount an old IRIX 5.x disk using both your current kernel > > patch and the xfs enabled kernel souces (kernel 2.4.6). In all cases i > > get "wrong fs type, bad option, bad superblock on /dev/sdb1, or too many > > mounted file systems" when trying to mount with "mount -t xfs /dev/sdb1 > > /dir" > > > > xfs_repair can not find secondary superblock, > > > > fdisk gives the following informations on the disk > > > > > > ----- partitions ----- > > Device Info Start End Sectors Id System > > /dev/sdb1 boot 5 3424 1846576 a SGI xfs > > /dev/sdb2 swap 3425 3804 205408 3 SGI raw > > /dev/sdb9 0 4 2620 0 SGI volhdr > > /dev/sdb11 0 3804 2054604 6 SGI volume > > ----- bootinfo ----- > > Bootfile: /unix > > ----- directory entries ----- > > 0: sgilabel sector 2 size 512 > > 1: sash sector 4 size 140800 > > 2: ide sector 558 size 977920 > > > > Is there anything obvious I am missing? > > > > Regards > > Gerwin > > Did you remember to enable SGI partition support in the kernel config? I > don't think it's enabled by default. That's all I can think of. Hope > that helps. > > -Walt Yes, I did remember to do this. Everything seems to be ok, but i am not able to mount this xfs-partition because of the bad superblock. I saw that there exists a patch for IRIX that fits to the same problem: bad superblock and fsck (xfs_repair) cannot find a valid secondary superblock. Maybe linux-xfs has the same problem?! Regards Gerwin From owner-linux-xfs@oss.sgi.com Mon Jul 16 00:34:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G7YZM08103 for linux-xfs-outgoing; Mon, 16 Jul 2001 00:34:35 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G7YXV08084 for ; Mon, 16 Jul 2001 00:34:33 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6G7YRe26777; Mon, 16 Jul 2001 09:34:27 +0200 Message-Id: <4.3.2.7.2.20010716092919.033f1890@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 16 Jul 2001 09:34:16 +0200 To: thomas graichen , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: xfs on notebooks (noflushd etc.) In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 18:51 15-7-2001 +0200, thomas graichen wrote: >just out of curiousity: how does xfs interact with things like >noflushd which reduce the disk flushing for more effective ide >poweroff possibilities ... is the flushing below the fs layer >so that it should all work transparently or may it result in >problems with xfs (or journaling fs in general)? If your journal does not get out to disk and the data does not get out to disk and the fs is not touched it would remain consistent. If the journal gets written and the data does not or vice versa you can probably imagine what happens. The question is if both the journal and data end up in the same layer and thus get written at the same time. I think that journal does not travel to disk in the same path that the data does. However this is a bit og guessing, let the brighter people answer this one. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 16 00:45:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G7jsC08859 for linux-xfs-outgoing; Mon, 16 Jul 2001 00:45:54 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G7jqV08840 for ; Mon, 16 Jul 2001 00:45:52 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id AAA26451 for ; Mon, 16 Jul 2001 00:45:41 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA90126 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 17:44:32 +1000 (EST) Date: Mon, 16 Jul 2001 17:44:32 +1000 (EST) From: Nathan Scott Message-Id: <200107160744.RAA90126@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs-1.3.1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tidying up after the introduction of libtool. It is now a requirement that libtool be installed in order to build xfsprogs. xfsdump and co will be converted later, but that should be trivial. cheers. Date: Sun Jul 15 16:29:14 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98913a cmd/xfsprogs/doc/PORTING - 1.2 - add a pointer to libtool documentation. Date: Sun Jul 15 20:09:05 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98915a linux/Documentation/filesystems/xfs.txt - 1.7 - remove the kio option for now as the current kernel doesn't support it. Date: Mon Jul 16 00:33:50 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98918a cmd/xfsprogs/include/builddefs.in - 1.7 - remove a now-redundant macro. cmd/xfsprogs/libxfs/init.c - 1.8 cmd/xfsprogs/libxfs/Makefile - 1.6 - make the BLKBSZSET ioctl use conditional on a compile-time macro (still use it though, till Eric is sure). cmd/xfsprogs/doc/Makefile - 1.6 cmd/xfsprogs/debian/Makefile - 1.2 cmd/xfsprogs/debian/rules - 1.6 cmd/xfsprogs/debian/changelog - 1.18 - tidying - rationalise the multiple changelogs, keep version numbering more consistent with other packages. cmd/xfsprogs/doc/CHANGES - 1.24 - update with recent changes -> 1.3.1. cmd/xfsprogs/configure.in - 1.8 - enforces the requirement to have libtool installed on the build machine. cmd/xfsprogs/Makefile - 1.5 - remove rules to tidy up tmp libtool files - we use the installed version now. cmd/xfsprogs/Makepkgs - 1.4 - use "distclean" not "clean" - ensures configure output updated each time (thanks Tim). cmd/xfsprogs/VERSION - 1.22 - make this a real release (toss the pre1 moniker). cmd/xfsprogs/ltconfig - 1.2 cmd/xfsprogs/aclocal.m4 - 1.2 cmd/xfsprogs/config.guess - 1.2 cmd/xfsprogs/config.sub - 1.2 cmd/xfsprogs/ltmain.sh - 1.2 - removed - libtool must come from the build machine now, we don't generate our own local version based on some arbitrary libtool version. cmd/xfsprogs/libdisk/xvm.h - 1.2 cmd/xfsprogs/libdisk/xvm.c - 1.3 - fill in the blanks with help from DeanJ. cmd/xfsprogs/include/volume.h - 1.2 cmd/xfsprogs/libdisk/drivers.c - 1.2 - add get_driver_block_major function to dynamically figure out driver majors if need be. cmd/xfsprogs/libdisk/md.c - 1.2 cmd/xfsprogs/libdisk/lvm.c - 1.2 - make each driver-specific file more consistent with the others. From owner-linux-xfs@oss.sgi.com Mon Jul 16 01:09:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G89Si11285 for linux-xfs-outgoing; Mon, 16 Jul 2001 01:09:28 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G89PV11263 for ; Mon, 16 Jul 2001 01:09:25 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA04369 for ; Mon, 16 Jul 2001 10:09:23 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA20923 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 10:09:23 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id EB13257306 for ; Mon, 16 Jul 2001 10:19:19 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 02A2125835 for ; Mon, 16 Jul 2001 10:27:15 +0200 (CEST) Message-ID: <3B52A14E.6D0D4FA5@ch.sauter-bc.com> Date: Mon, 16 Jul 2001 10:09:50 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Samba 2.2.1 RPMS with ACL Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I was just wondering whether someone has built Samba 2.2.1 RPMs with ACL suitable for RH-7.1 XFS. If yes, it would be nice to have them somewhere in a contrib area on the XFS ftp server. -Simon From owner-linux-xfs@oss.sgi.com Mon Jul 16 01:18:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G8IeH12091 for linux-xfs-outgoing; Mon, 16 Jul 2001 01:18:40 -0700 Received: from mout0.freenet.de (exim@mout0.freenet.de [194.97.50.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G8IcV12066 for ; Mon, 16 Jul 2001 01:18:38 -0700 Received: from [194.97.50.135] (helo=mx2.freenet.de) by mout0.freenet.de with esmtp (Exim 3.30 #3) id 15M3aL-0004OB-00; Mon, 16 Jul 2001 10:18:33 +0200 Received: from b6eb6.pppool.de ([213.7.110.182] helo=lx2.thhmaus.de) by mx2.freenet.de with esmtp (Exim 3.30 #3) id 15M3aK-0005Pz-00; Mon, 16 Jul 2001 10:18:33 +0200 Subject: Re: xfsdump on alpha From: ThH To: Nathan Scott Cc: linux-xfs@oss.sgi.com In-Reply-To: <10107161617.ZM208491@wobbly.melbourne.sgi.com> References: <995262801.828.0.camel@lx1.thhmaus.de> <10107161617.ZM208491@wobbly.melbourne.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 10:21:40 +0200 Message-Id: <995271702.989.0.camel@lx2.thhmaus.de> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am 16 Jul 2001 16:17:12 +1000 schrieb Nathan Scott: > hi, > > On Jul 16, 7:53am, ThH wrote: > > Subject: xfsdump on alpha > > I've tried xfsdump-1.0.11 on my alpha. But there is the Assertion > > problem again. > > > > xfsdump: version 3.0 - Running single-threaded > > xfsdump: global.c:82 global_hdr_alloc: Assertion `sizeof( time_t ) == 4' > > failed. > > Aborted (core dumped) > > > > On alpha it is 8 instead of 4. > > > > I had corected this one Assertion manualy, > > Changing just the assert doesn't seem like the right thing > to do - this looks like a data structure which gets written > onto the tape, so it needs to be 4 bytes long. Will require > an audit of the xfs{dump/restore} code to check all of the > uses of time_t, I guess - does that sound right, Ivan/Tim? > > > but there are some others yet I don't know. > > Probably are. > > cheers. > > -- > Nathan > You say it's an incompatibility of the dump data structure and the alpha system headers. What's with other 64bit systems like IA64, sparc64 or mips64, they might have the same problem. I'm right? I will use xfsdump. Can you tell me what I've to do, too solve this problem? ThH From owner-linux-xfs@oss.sgi.com Mon Jul 16 01:29:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G8TD712837 for linux-xfs-outgoing; Mon, 16 Jul 2001 01:29:13 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G8TBV12818 for ; Mon, 16 Jul 2001 01:29:11 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id BAA29710 for ; Mon, 16 Jul 2001 01:29:01 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 SAA22287; Mon, 16 Jul 2001 18:27:51 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA08125; Mon, 16 Jul 2001 18:27:50 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107161827.ZM215737@wobbly.melbourne.sgi.com> Date: Mon, 16 Jul 2001 18:27:48 +1000 In-Reply-To: ThH "Re: xfsdump on alpha" (Jul 16, 10:21am) References: <995262801.828.0.camel@lx1.thhmaus.de> <10107161617.ZM208491@wobbly.melbourne.sgi.com> <995271702.989.0.camel@lx2.thhmaus.de> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: ThH Subject: Re: xfsdump on alpha Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 16, 10:21am, ThH wrote: > Subject: Re: xfsdump on alpha > ... > You say it's an incompatibility of the dump data structure and the alpha > system headers. What's with other 64bit systems like IA64, sparc64 or > mips64, they might have the same problem. I'm right? Yes, you're right - they almost certainly will have this problem too. > > I will use xfsdump. Can you tell me what I've to do, too solve this > problem? > You'll need to audit all uses of time_t in xfsdump tools - if any of these are in data structures which are to be written on the tape, then you will need to make up a new type (eg. time32_t) and then change the code to use that instead of time_t, ensuring all the places where a 8byte time_t are needed (eg. libc entry points, syscalls, etc) still use that, but a conversion to a 32bit version must be done subsequently before the data structure is written anywhere permanently. At the same time, you'll need to ensure that the code for 32 bit platforms is effectively unchanged - eg. time32_t could equate to time_t on those platforms, thru use of cpp macros, etc. hope this helps. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 16 01:38:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G8cKF13314 for linux-xfs-outgoing; Mon, 16 Jul 2001 01:38:20 -0700 Received: from ms.svkuh.cz (ms.svkuh.cz [217.112.161.36]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G8cIV13294 for ; Mon, 16 Jul 2001 01:38:18 -0700 Received: from w102.svkuh.cz (w102.svkuh.cz [192.168.10.102]) by ms.svkuh.cz (Postfix) with SMTP id C2A66FFBA for ; Mon, 16 Jul 2001 10:38:15 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-2" From: David =?iso-8859-2?q?Luka=B9t=EDk?= To: linux-xfs@oss.sgi.com Subject: Re: Lost data on XFS Date: Mon, 16 Jul 2001 10:38:15 +0200 X-Mailer: KMail [version 1.2] References: <01071608030000.29569@w102.svkuh.cz> In-Reply-To: <01071608030000.29569@w102.svkuh.cz> MIME-Version: 1.0 Message-Id: <01071610381504.29569@w102.svkuh.cz> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Hmm, I found the problem. The second harddrive in the RAID wasn't plugged. But why the data aren't on mirrored, when I reboot computer?? Now I must restore data from backup. regards, David Lukastik From owner-linux-xfs@oss.sgi.com Mon Jul 16 02:00:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6G90Ui14777 for linux-xfs-outgoing; Mon, 16 Jul 2001 02:00:30 -0700 Received: from weta.f00f.org (weta.f00f.org [203.167.249.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6G90SV14758 for ; Mon, 16 Jul 2001 02:00:29 -0700 Received: by weta.f00f.org (Postfix, from userid 1000) id 77FBC27C1; Mon, 16 Jul 2001 21:00:29 +1200 (NZST) Date: Mon, 16 Jul 2001 21:00:29 +1200 From: Chris Wedgwood To: Hans Reiser Cc: rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010716210029.I11938@weta.f00f.org> References: <3B507259.4436853E@baldauf.org> <20010715052116.E7056@weta.f00f.org> <3B50D058.3090008@ns.aus.com> <3B50CFF6.4BE90AB0@namesys.com> <20010715155758.G7624@weta.f00f.org> <3B5169E5.827BFED@namesys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B5169E5.827BFED@namesys.com> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: Making the server stateless is wrong why? making the readdir a multioperation act is wrong why? i have 3M directories... ar you saying clients should read the whole things at once? but making not letting the FS use filename as a cookie and making it use 64 bit byte offsets is the most wrong thing of all. here i agree, smarter clients could/should hang onto the filename and revalidate if needed --- the only nasty things is REALLY deep directory trees --cw From owner-linux-xfs@oss.sgi.com Mon Jul 16 03:02:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GA2Fl16952 for linux-xfs-outgoing; Mon, 16 Jul 2001 03:02:15 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GA2BV16926 for ; Mon, 16 Jul 2001 03:02:12 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6GA26e27353; Mon, 16 Jul 2001 12:02:09 +0200 Message-Id: <4.3.2.7.2.20010716115857.02709240@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 16 Jul 2001 12:01:55 +0200 To: Gerwin Brill , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: mounting XFS fails In-Reply-To: <3B521BF9.72879C44@informatik.uni-bonn.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 00:40 16-7-2001 +0200, Gerwin Brill wrote: >Hi, > >I've tried to mount an old IRIX 5.x disk using both your current kernel >patch and the xfs enabled kernel souces (kernel 2.4.6). In all cases i >get "wrong fs type, bad option, bad superblock on /dev/sdb1, or too many >mounted file systems" when trying to mount with "mount -t xfs /dev/sdb1 >/dir" > >xfs_repair can not find secondary superblock, > >fdisk gives the following informations on the disk > > >----- partitions ----- > Device Info Start End Sectors Id System >/dev/sdb1 boot 5 3424 1846576 a SGI xfs >/dev/sdb2 swap 3425 3804 205408 3 SGI raw >/dev/sdb9 0 4 2620 0 SGI volhdr >/dev/sdb11 0 3804 2054604 6 SGI volume >----- bootinfo ----- >Bootfile: /unix >----- directory entries ----- > 0: sgilabel sector 2 size 512 > 1: sash sector 4 size 140800 > 2: ide sector 558 size 977920 > >Is there anything obvious I am missing? There is an answer to this in the FAQ. If this partition is formatted with another cluster size then 4K you can't read it (yet). Irix uses a default of 512Bytes. So if you want make it interchangeable you will need to format it with a 4K cluster size. This is because on ia32 Pagesize==Clustersize. And XFS currently can not mount disks where Clustersize is larger or smaller then pagesize. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 16 03:13:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GADVN17824 for linux-xfs-outgoing; Mon, 16 Jul 2001 03:13:31 -0700 Received: from ivanova.coker.com.au (postfix@ivanova.coker.com.au [203.36.46.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GADQV17801 for ; Mon, 16 Jul 2001 03:13:28 -0700 Received: from lyta.coker.com.au (ivanova [127.0.0.1]) by ivanova.coker.com.au (Postfix) with ESMTP id 27AD0FAC3; Mon, 16 Jul 2001 20:13:03 +1000 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id 2DC3E965; Mon, 16 Jul 2001 12:13:12 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Chris Wedgwood , Hans Reiser Subject: Re: [reiserfs-list] Re: benchmarks Date: Mon, 16 Jul 2001 12:13:05 +0200 X-Mailer: KMail [version 1.2.9] Cc: rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> In-Reply-To: <20010716210029.I11938@weta.f00f.org> MIME-Version: 1.0 Message-Id: <20010716101313.2DC3E965@lyta.coker.com.au> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GADUV17805 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > Making the server stateless is wrong > > why? Because it leads to all the problems we have seen! Why not have the client have an open file handle (the way Samba works and the way the Unix file system API works)? Then when the server goes down the client sends a request to open the file again... > making the readdir a multioperation act is wrong > > why? i have 3M directories... ar you saying clients should read the > whole things at once? No. findfirst()/findnext() is the correct way of doing this. Forcing the client to read through 3M directory entries to see if "foo.*" matches anything is just wrong. The client should be able to ask for a list of file names matching certain criteria (time stamp, name, ownership, etc). The findfirst() and findnext() APIs on DOS, OS/2, and Windows do this quite well. If you have 3M directory entries then SMB should kick butt over NFS. Also while we're at it, one of the worst things about NFS is the issue of delete. Because it's stateless NFS servers implement unlink as "mv" and things get nasty from there... -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page From owner-linux-xfs@oss.sgi.com Mon Jul 16 03:40:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GAepw19874 for linux-xfs-outgoing; Mon, 16 Jul 2001 03:40:51 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GAemV19855 for ; Mon, 16 Jul 2001 03:40:48 -0700 Received: (qmail 9580 invoked from network); 16 Jul 2001 10:40:37 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 16 Jul 2001 10:40:37 -0000 Message-ID: <3B52C49F.9FE1F503@namesys.com> Date: Mon, 16 Jul 2001 14:40:31 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Russell Coker CC: Chris Wedgwood , rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Russell Coker wrote: > > On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > Making the server stateless is wrong > > > > why? > > Because it leads to all the problems we have seen! Why not have the client > have an open file handle (the way Samba works and the way the Unix file > system API works)? Then when the server goes down the client sends a request > to open the file again... > > > making the readdir a multioperation act is wrong > > > > why? i have 3M directories... ar you saying clients should read the > > whole things at once? > > No. findfirst()/findnext() is the correct way of doing this. Forcing the > client to read through 3M directory entries to see if "foo.*" matches > anything is just wrong. The client should be able to ask for a list of file > names matching certain criteria (time stamp, name, ownership, etc). The > findfirst() and findnext() APIs on DOS, OS/2, and Windows do this quite well. there is a fundamental conflict between having cookies, shrinkable directories, and the ability to find foo.* without reading the whole directory, all at the same time. NFS V4 is designed by braindead twerps incapable of layering software when designing it. > > If you have 3M directory entries then SMB should kick butt over NFS. > > Also while we're at it, one of the worst things about NFS is the issue of > delete. Because it's stateless NFS servers implement unlink as "mv" and > things get nasty from there... > > -- > http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark > http://www.coker.com.au/projects.html Projects I am working on > http://www.coker.com.au/~russell/ My home page From owner-linux-xfs@oss.sgi.com Mon Jul 16 04:00:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GB0mG21194 for linux-xfs-outgoing; Mon, 16 Jul 2001 04:00:48 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GB0jV21175 for ; Mon, 16 Jul 2001 04:00:45 -0700 Received: (qmail 11046 invoked from network); 16 Jul 2001 11:00:38 -0000 Received: from srg.access.comstar.ru (HELO beta.namesys.com) (195.210.131.190) by thebsh.namesys.com with SMTP; 16 Jul 2001 11:00:38 -0000 Received: (from god@localhost) by beta.namesys.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id PAA27803; Mon, 16 Jul 2001 15:00:10 +0400 From: Nikita Danilov MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15186.51514.66966.458597@beta.namesys.com> Date: Mon, 16 Jul 2001 15:00:10 +0400 To: Hans Reiser Cc: Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks In-Reply-To: <3B52C49F.9FE1F503@namesys.com> References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> X-Mailer: VM 6.89 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hans Reiser writes: > Russell Coker wrote: > > > > On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > > > Making the server stateless is wrong > > > > > > why? > > > > Because it leads to all the problems we have seen! Why not have the client > > have an open file handle (the way Samba works and the way the Unix file > > system API works)? Then when the server goes down the client sends a request > > to open the file again... If you have 10000 clients each opening 100 files you got 1e6 opened files on the server---it wouldn't work. NFS was designed to be stateless to be scalable. > > > > > making the readdir a multioperation act is wrong > > > > > > why? i have 3M directories... ar you saying clients should read the > > > whole things at once? > > > > No. findfirst()/findnext() is the correct way of doing this. Forcing the > > client to read through 3M directory entries to see if "foo.*" matches > > anything is just wrong. The client should be able to ask for a list of file > > names matching certain criteria (time stamp, name, ownership, etc). The > > findfirst() and findnext() APIs on DOS, OS/2, and Windows do this quite well. > > there is a fundamental conflict between having cookies, shrinkable directories, and the ability to > find foo.* without reading the whole directory, all at the same time. > > NFS V4 is designed by braindead twerps incapable of layering software when designing it. Just cannot stand it. You mean that NFS v4 features database in a kernel too? (It's our insider joke.) > > > > > If you have 3M directory entries then SMB should kick butt over NFS. > > > > Also while we're at it, one of the worst things about NFS is the issue of > > delete. Because it's stateless NFS servers implement unlink as "mv" and > > things get nasty from there... > > > > -- > > http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark > > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark > > http://www.coker.com.au/projects.html Projects I am working on > > http://www.coker.com.au/~russell/ My home page Nikita. From owner-linux-xfs@oss.sgi.com Mon Jul 16 05:09:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GC9YP27450 for linux-xfs-outgoing; Mon, 16 Jul 2001 05:09:34 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GC9VV27428 for ; Mon, 16 Jul 2001 05:09:31 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id FAA01913 for ; Mon, 16 Jul 2001 05:09:20 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id WAA47912 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 22:08:04 +1000 (EST) Date: Mon, 16 Jul 2001 22:08:04 +1000 (EST) From: Nathan Scott Message-Id: <200107161208.WAA47912@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - more libtool Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Mon Jul 16 04:42:38 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98924a cmd/xfsprogs/include/builddefs.in - 1.8 cmd/xfsprogs/growfs/Makefile - 1.4 cmd/xfsprogs/fsck/Makefile - 1.4 cmd/xfsprogs/db/Makefile - 1.4 cmd/xfsprogs/repair/Makefile - 1.4 cmd/xfsprogs/mkfs/Makefile - 1.6 cmd/xfsprogs/mkfile/Makefile - 1.4 cmd/xfsprogs/logprint/Makefile - 1.4 cmd/xfsprogs/bmap/Makefile - 1.4 cmd/xfsprogs/rtcp/Makefile - 1.3 cmd/xfsprogs/freeze/Makefile - 1.3 - use LTINSTALL for libtool created binaries (wraps our install-sh). Date: Mon Jul 16 04:49:03 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98926a cmd/attr/libattr/Makefile - 1.3 cmd/attr/attr/Makefile - 1.3 cmd/attr/attr/attr.c - 1.2 cmd/attr/Makefile - 1.2 cmd/attr/Makepkgs - 1.4 cmd/attr/VERSION - 1.6 cmd/attr/configure.in - 1.5 cmd/attr/debian/Makefile - 1.2 cmd/attr/debian/changelog - 1.5 cmd/attr/debian/control - 1.3 cmd/attr/debian/rules - 1.4 cmd/attr/doc/CHANGES - 1.6 cmd/attr/doc/Makefile - 1.3 cmd/attr/doc/PORTING - 1.2 cmd/attr/include/builddefs.in - 1.3 cmd/attr/include/buildrules - 1.2 - updates to integrate libtool into the build throughout the package. Date: Mon Jul 16 04:50:50 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98927a cmd/acl/configure.in - 1.6 cmd/acl/libacl/Makefile - 1.2 cmd/acl/debian/Makefile - 1.2 cmd/acl/Makefile - 1.2 cmd/acl/Makepkgs - 1.3 cmd/acl/VERSION - 1.10 cmd/acl/debian/changelog - 1.4 cmd/acl/debian/rules - 1.4 cmd/acl/chacl/Makefile - 1.2 cmd/acl/doc/Makefile - 1.3 cmd/acl/debian/control - 1.2 cmd/acl/doc/CHANGES - 1.10 cmd/acl/include/buildrules - 1.2 cmd/acl/include/builddefs.in - 1.3 cmd/acl/doc/PORTING - 1.2 - updates to integrate libtool into the build throughout the package. Date: Mon Jul 16 05:07:02 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98928a cmd/xfsprogs/growfs/Makefile - 1.5 cmd/xfsprogs/logprint/Makefile - 1.5 - needed an LTDEPENDENCIES line for LIBXFS. From owner-linux-xfs@oss.sgi.com Mon Jul 16 06:02:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GD28431949 for linux-xfs-outgoing; Mon, 16 Jul 2001 06:02:08 -0700 Received: from mail.edm-inc.com (mail.edm-inc.com [66.80.43.91]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GD26V31930 for ; Mon, 16 Jul 2001 06:02:06 -0700 Received: (qmail 26385 invoked by uid 1005); 16 Jul 2001 08:02:00 -0500 Received: from ian.scott@edm-inc.com by mail with qmail-scanner-0.96 (fsecure: 4.10/3081/2001-07-13/2001-07-11/2001-07-13. inocucmd: 24.00/25.47. . Clean. Processed in 5.228783 secs); 16 Jul 2001 08:02:00 -0500 Received: from unknown (HELO admin.edm-inc.com) (10.10.10.58) by 0 with SMTP; 16 Jul 2001 08:01:54 -0500 Message-Id: <5.1.0.14.0.20010716075808.00ae22b0@mail.edm-inc.com> X-Sender: ian.scott@mail.edm-inc.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 16 Jul 2001 08:01:31 -0500 To: Federico Sevilla III , Linux XFS Mailing List From: Ian Scott Subject: Re: [SLIGHTLY OT] XFS ACL support in Samba In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 04:44 PM 7/15/2001 +0800, Federico Sevilla III wrote: ... >[ -f source/Makefile ] || (cd source && ./configure --with-fhs \ > --prefix=/usr --sysconfdir=/etc --with-privatedir=/etc/samba \ > --with-lockdir=/var/state/sa mba --localstatedir=/var --with-netatalk \ > --with-smbmount --with-pam --with-syslo g --with-sambabook \ > --with-utmp --with-readline --with-acl-support) ... I see you are also including PAM support in your Samba configuration. There is a problem with the configure process in Samba. While compiling the test program for ACL support, it also includes PAM. If your PAM dev files are missing, the ACL step will fail even if your ACL support is working. Make sure you have the libpam0g-dev Debian package installed. Ian From owner-linux-xfs@oss.sgi.com Mon Jul 16 06:32:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GDW7Y02240 for linux-xfs-outgoing; Mon, 16 Jul 2001 06:32:07 -0700 Received: from ivanova.coker.com.au (postfix@ivanova.coker.com.au [203.36.46.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GDW1V02214 for ; Mon, 16 Jul 2001 06:32:02 -0700 Received: from lyta.coker.com.au (ivanova [127.0.0.1]) by ivanova.coker.com.au (Postfix) with ESMTP id AA716FAC3; Mon, 16 Jul 2001 23:31:44 +1000 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id C4FDACB9; Mon, 16 Jul 2001 15:31:57 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Nikita Danilov , Hans Reiser Subject: Re: [reiserfs-list] Re: benchmarks Date: Mon, 16 Jul 2001 15:31:57 +0200 X-Mailer: KMail [version 1.2.9] Cc: Chris Wedgwood , rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com References: <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> In-Reply-To: <15186.51514.66966.458597@beta.namesys.com> MIME-Version: 1.0 Message-Id: <20010716133157.C4FDACB9@lyta.coker.com.au> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GDW5V02219 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 16 Jul 2001 13:00, Nikita Danilov wrote: > > > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > > > > > Making the server stateless is wrong > > > > > > > > why? > > > > > > Because it leads to all the problems we have seen! Why not have the > > > client have an open file handle (the way Samba works and the way the > > > Unix file system API works)? Then when the server goes down the > > > client sends a request to open the file again... > > If you have 10000 clients each opening 100 files you got 1e6 opened > files on the server---it wouldn't work. NFS was designed to be stateless > to be scalable. If you want performance from a file server that is almost bearable then you must have enough cache to handle all the open files. 10^6 files will not be workable anyway. If each file is accessed once per hour then the load might almost be bearable by high-end hardware. Memory is getting cheaper all the time. I've worked with many server machines that have 2G or more of RAM. Having enough kernel memory for 1M open files should be easy enough to manage (I could probably manage it on my laptop if I upgraded it). Being able to actually do anything with 1M processes accessing files at the same time is another issue. I am surprised to hear about NFS being stateless for large performance. I always thought that it was stateless because it pre-dates the common availability of UPSs and hardware RAID (or any RAID really). Also NFS pre-dates the availability of HACMP, E10K, and other systems to bring mainframe features of hot-swap hardware and high reliability to Unix systems. -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page From owner-linux-xfs@oss.sgi.com Mon Jul 16 07:15:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GEFVi05282 for linux-xfs-outgoing; Mon, 16 Jul 2001 07:15:31 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GEFQV05260 for ; Mon, 16 Jul 2001 07:15:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA297983 for ; Mon, 16 Jul 2001 16:15:19 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2442463; Mon, 16 Jul 2001 09:14:02 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA27154; Mon, 16 Jul 2001 09:14:02 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GEFN401346; Mon, 16 Jul 2001 09:15:23 -0500 Message-Id: <200107161415.f6GEFN401346@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: thomas graichen cc: linux-xfs@oss.sgi.com Subject: Re: xfs on notebooks (noflushd etc.) In-Reply-To: Message from thomas graichen of "Sun, 15 Jul 2001 18:51:02 +0200." Date: Mon, 16 Jul 2001 09:15:23 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > just out of curiousity: how does xfs interact with things like > noflushd which reduce the disk flushing for more effective ide > poweroff possibilities ... is the flushing below the fs layer > so that it should all work transparently or may it result in > problems with xfs (or journaling fs in general)? > > a lot of thanks in advance I have never tried noflushd, I see the FAQ says that it does not help with reiserfs because it bypasses normal delayed write mechanisms, xfs does the same type of thing, so there may be similar problems. Someone will have to try it and report back. Since noflushd appears to be intended to delay writes, and that the writes will eventually happen, I do not forsee major problems unless you happen to really lose power in the middle of this, and not have the system memory saved back to disk. In general when using my laptop with XFS the disk will spindown if I am just sitting staring at the screen. Turning on the noatime option (which requires jumping through some hoops for the root partition) will get rid of a lot of disk I/O. I am not convinced that noflushd will have much luck stopping XFS from writing to the disk though, file writes could be delayed, but all metadata and journal accesses are probably beyond its control. Steve > > t > > -- > thomas graichen ... perfection is reached, not > when there is no longer anything to add, but when there is no > longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Mon Jul 16 07:33:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GEXPh06661 for linux-xfs-outgoing; Mon, 16 Jul 2001 07:33:25 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GEXNV06634 for ; Mon, 16 Jul 2001 07:33:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA28713 for ; Mon, 16 Jul 2001 07:33:13 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2409518; Mon, 16 Jul 2001 09:32:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA67478; Mon, 16 Jul 2001 09:31:59 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GEXKU01530; Mon, 16 Jul 2001 09:33:20 -0500 Message-Id: <200107161433.f6GEXKU01530@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: DMAPI (was: null character filesystem corruption with 2.4.6) In-Reply-To: Message from Federico Sevilla III of "Mon, 16 Jul 2001 09:59:31 +0800." Date: Mon, 16 Jul 2001 09:33:20 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Mon, 16 Jul 2001 at 11:47, Timothy Shimmin wrote: > > > What else is stored in there? > > DMAPI/DMF attributes. > > Aside from what is in the Configure.help documentation, what exactly are > DMAPI/DMF attributes and for what applications are these recommended to be > enabled? My current kernel has this disabled and I did not build/install > the dmapi cmd packages. I disabled DMAPI because I did not think I had a > system that fit in the description "hierarchical storage management > systems". There is not really anything you can do with the DMAPI code unless you have a user space application for it - which I doubt you do. > > Maybe someone can help me out and explain DMAPI/DMF and how one can > benefit from it? :) > DMAPI is a set of callouts in the filesystem and an interface to user space which allows a special purpose application to intercept operations in the filesystem and take some action before the operation is allowed to complete. An example is to extend the filesystem to support some form of tertiary storage device such as tape, a request to read a file could then result in the user space app reading the files contents from tape and placing them on disk before allowing the read to proceed. DMAPI uses extended attributes to record the information it needs about the contents of a file. Linux XFS supports the DMAPI interface, but the user space application which uses this is still being ported and at the moment it is not planned to open source this. There is an open XDSM (same interface, new name) project on sourceforge, but I do not think it is very active. Steve > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Mon Jul 16 07:58:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GEww408879 for linux-xfs-outgoing; Mon, 16 Jul 2001 07:58:58 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GEwuV08856 for ; Mon, 16 Jul 2001 07:58:56 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA03471 for ; Mon, 16 Jul 2001 07:56:26 -0700 (PDT) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2436007 for ; Mon, 16 Jul 2001 09:57:39 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA80265 for ; Mon, 16 Jul 2001 09:57:39 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id JAA30728; Mon, 16 Jul 2001 09:57:39 -0500 (CDT) Message-Id: <200107161457.JAA30728@slobber.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: Re: DMAPI and dump/restore Date: Mon, 16 Jul 2001 09:57:38 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: Timothy Shimmin >> So if you're on Irix and using an HSM other than DMF on an XFS filesystem th >en >> xfsdump is not going to do the right thing. >> >So, in other words, we only handle stuff for DMF. >And this should work in Linux for DMF when we turn it on in >xfsdump/xfsrestore and finish the necessary porting >(or so the theory goes :). Yes, the stuff should just work when we turn it on :) xfsdump/xfsrestore can be used on filesystems managed by DMF, but they will not play nicely on filesystems managed by other vendors' HSMs (in their current state.) I'd mark this up as a consequence of proprietary systems, and now that we're in the brave new world of free software some of that's bound to change. >> I noticed that on the Linux side xfsdump sets it to >> zero--the Irix xfsdump doesn't touch it. The confusion is not surprising, I >> guess. >What bits of the code are you looking at here ? On Linux it's in dump/content.c: $ grep dmstate dump/* dump/content.c: dst->bs_dmstate = (u_int16_t) 0; /* dunno */ Dean From owner-linux-xfs@oss.sgi.com Mon Jul 16 08:58:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GFwfd13821 for linux-xfs-outgoing; Mon, 16 Jul 2001 08:58:41 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GFwcV13799 for ; Mon, 16 Jul 2001 08:58:38 -0700 Received: (qmail 28312 invoked by uid 8); 16 Jul 2001 15:58:37 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: xfs on notebooks (noflushd etc.) Date: Mon, 16 Jul 2001 15:58:36 +0000 (UTC) Organization: spoiled dot org Lines: 18 Distribution: local Message-ID: References: X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk thomas graichen wrote: > just out of curiousity: how does xfs interact with things like > noflushd which reduce the disk flushing for more effective ide > poweroff possibilities ... is the flushing below the fs layer > so that it should all work transparently or may it result in > problems with xfs (or journaling fs in general)? Hi Thomas, well, I cannot speak for xfs but with ext3 the disk will only spin down once; after this it will be constantly restarted by the update mechanisms of ext3 (commit interval is 5 seconds). Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Mon Jul 16 10:08:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GH8A015755 for linux-xfs-outgoing; Mon, 16 Jul 2001 10:08:10 -0700 Received: from server.hotswap (atbode95.informatik.tu-muenchen.de [131.159.32.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GH87V15736 for ; Mon, 16 Jul 2001 10:08:08 -0700 Received: from cs.tum.edu (kuschel.hotswap [172.16.16.190]) by server.hotswap (swapfix) with ESMTP id 2797B39654C7 for ; Mon, 16 Jul 2001 19:08:01 +0200 (CEST) Message-ID: <3B531F71.F952A247@cs.tum.edu> Date: Mon, 16 Jul 2001 19:08:01 +0200 From: Deti Fliegl X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre3-xfs i686) X-Accept-Language: en, de MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfsdump/xfsrestore fails on device nodes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi today I was using xfsdump and xfsrestore (both version 3 from the CVS tree) to backup a whole root FS. After the restore all device node majors were set to 0. I think there might be a problem with either the dump or the restore utility. Regards, Deti -- Detlef Fliegl, LRR, Technische Universitaet Muenchen Phone: +49-89-289-25770, Fax +49-1212-511090362, Room S3240 From owner-linux-xfs@oss.sgi.com Mon Jul 16 10:23:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GHNCh16089 for linux-xfs-outgoing; Mon, 16 Jul 2001 10:23:12 -0700 Received: from d0lxucr02.fnal.gov (IDENT:root@d0lxucr02.fnal.gov [131.225.221.43]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GHNAV16070 for ; Mon, 16 Jul 2001 10:23:10 -0700 Received: from localhost (vkuznet@localhost) by d0lxucr02.fnal.gov (8.9.3/8.9.3) with ESMTP id NAA05048 for ; Mon, 16 Jul 2001 13:23:09 -0400 X-Authentication-Warning: d0lxucr02.fnal.gov: vkuznet owned process doing -bs Date: Mon, 16 Jul 2001 12:23:08 -0500 (CDT) From: To: linux-xfs@oss.sgi.com Subject: XFS performance Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I'm got XFS working on my Linux workstation (dual PIII 550Mhz, 512Mb RAM). The only things I've noticed that my applications compiled by a factor of 2 slower compared to ext2. It is quite large set of libraries (around 300) and problem seems to be at linkage stage. My questions are the following: 1) which parameters will allow to tune XFS performance 2) is it possible to mount XFS with another parameters (such as logsize) compare to ones used during formatting (I've used default). Thank you, Valentine. ************************************************************* * Valentine Kouznetsov phone : (630) 840 2192 * * Fermilab MS352 fax : (630) 840 8886 * * P.O.Box 500 e-mail: vkuznet@fnal.gov * * Batavia IL, 60510 http://www-d0.fnal.gov/~vkuznet * ************************************************************* From owner-linux-xfs@oss.sgi.com Mon Jul 16 10:28:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GHSQX16322 for linux-xfs-outgoing; Mon, 16 Jul 2001 10:28:26 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GHSPV16303 for ; Mon, 16 Jul 2001 10:28:25 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id KAA09811 for ; Mon, 16 Jul 2001 10:25:56 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2435202; Mon, 16 Jul 2001 12:27:08 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA17385; Mon, 16 Jul 2001 12:27:08 -0500 (CDT) Message-ID: <3B5323EE.2D4438DC@sgi.com> Date: Mon, 16 Jul 2001 12:27:10 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Deti Fliegl CC: linux-xfs@oss.sgi.com Subject: Re: xfsdump/xfsrestore fails on device nodes References: <3B531F71.F952A247@cs.tum.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Deti Fliegl wrote: > > Hi > > today I was using xfsdump and xfsrestore (both version 3 from the CVS > tree) to backup a whole root FS. After the restore all device node > majors were set to 0. I think there might be a problem with either the > dump or the restore utility. This was recognized & fixed late last week (thursday), if you check out the latest CVS tree you should get an updated version... I believe that the RPMs and tarballs in cmd_rpms/ and cmd_tars/ have this fixed as well. -Eric From owner-linux-xfs@oss.sgi.com Mon Jul 16 10:34:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GHY1o16488 for linux-xfs-outgoing; Mon, 16 Jul 2001 10:34:01 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GHXxV16469 for ; Mon, 16 Jul 2001 10:33:59 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id TAA315081 for ; Mon, 16 Jul 2001 19:33:56 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2440345; Mon, 16 Jul 2001 12:32:36 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA29897; Mon, 16 Jul 2001 12:32:36 -0500 (CDT) Message-ID: <3B532536.BEEF7E3@sgi.com> Date: Mon, 16 Jul 2001 12:32:38 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: vkuznet@fnal.gov CC: linux-xfs@oss.sgi.com Subject: Re: XFS performance References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk vkuznet@fnal.gov wrote: > > Hi, > I'm got XFS working on my Linux workstation (dual PIII 550Mhz, > 512Mb RAM). The only things I've noticed that my applications > compiled by a factor of 2 slower compared to ext2. It is quite > large set of libraries (around 300) and problem seems to be > at linkage stage. My questions are the following: > 1) which parameters will allow to tune XFS performance > 2) is it possible to mount XFS with another parameters (such > as logsize) compare to ones used during formatting (I've used default). Changing an internal logsize is really not supported - the only "unofficial" way to do it is to convert to an external log (tricky!), see Steve's emails from last week. External logs can be grown with xfs_growfs, assuming there's space to grow into. Adding "logbufs=4" or "logbufs=8" as a mount option may help somewhat if there's a lot of log traffic. Although, I'm not sure offhand why linking in particular should be slow... -Eric From owner-linux-xfs@oss.sgi.com Mon Jul 16 11:30:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GIUUJ17465 for linux-xfs-outgoing; Mon, 16 Jul 2001 11:30:30 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GIUQV17446 for ; Mon, 16 Jul 2001 11:30:26 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id UAA314864 for ; Mon, 16 Jul 2001 20:30:23 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA97441; Mon, 16 Jul 2001 11:34:43 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id EEF1115A46C; Mon, 16 Jul 2001 11:28:55 -0700 (PDT) Subject: Re: [reiserfs-list] Re: benchmarks From: Florin Andrei To: Xuan Baldauf Cc: Seth Mos , Xuan Baldauf , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com In-Reply-To: <3B507259.4436853E@baldauf.org> References: <3B507259.4436853E@baldauf.org> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 11:28:55 -0700 Message-Id: <995308136.12677.4.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 14 Jul 2001 18:24:57 +0200, Xuan Baldauf wrote: > > Seth Mos wrote: > > > On Sat, 14 Jul 2001, Xuan Baldauf wrote: > > > > > > I do not use XFS, currently. Why is XFS better for Samba? > > > > Because word documents average 0.1 - 1MB. > > Ah. So you just mean speed (quantity), not some features (quality)- Features also: ACLs. ;-) -- Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 11:47:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GIl9017901 for linux-xfs-outgoing; Mon, 16 Jul 2001 11:47:09 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GIl6V17881 for ; Mon, 16 Jul 2001 11:47:07 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id UAA317187 for ; Mon, 16 Jul 2001 20:47:04 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA32783 for ; Mon, 16 Jul 2001 11:51:35 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 72AB615A46C for ; Mon, 16 Jul 2001 11:45:48 -0700 (PDT) Subject: fine-tuning XFS From: Florin Andrei To: linux-xfs@oss.sgi.com Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 11:45:48 -0700 Message-Id: <995309148.12677.5.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Can you give me, please, some hints on fine-tuning XFS for better performance for web caches? A typical Squid cache looks like this: - HDD size: 10...30 GB - average file size: 10...15 kB - 16 primary directories - each primary dir contains 256 secondary directories - each secondary dir can contain up to 256 actual files - the actual disk usage when the cache is "full" is ~80% (can be tuned from squid.conf) >From the FS point of view, the access to the files is quite random. The cache fills up first to the maximum size, and then the oldest files are deleted and replaced with newer files as the clients request them. At this point, the only option i use is "noatime". Do you have any suggestions to improve the speed? -- Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 11:55:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GItTs18302 for linux-xfs-outgoing; Mon, 16 Jul 2001 11:55:29 -0700 Received: from omecihuatl.rz.uni-osnabrueck.de (omecihuatl.rz.Uni-Osnabrueck.DE [131.173.17.35]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GItRV18283 for ; Mon, 16 Jul 2001 11:55:28 -0700 Received: from luna.rz.Uni-Osnabrueck.DE (luna.rz.Uni-Osnabrueck.DE [131.173.17.10]) by omecihuatl.rz.uni-osnabrueck.de (8.11.1/8.11.1) with ESMTP id f6GItP316994 for ; Mon, 16 Jul 2001 20:55:25 +0200 Date: Mon, 16 Jul 2001 20:55:25 +0200 (DFT) From: Yue Shi Lai To: Subject: Problems with the new 2.4.3-XFS kernel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dear XFS team, the new 2.4.3-XFS kernel seems to cause problems on my machine. If I use XMMS and Opera at the same time, there seems to be a point (after approx. 10-15 min) after which my system starts to swap constantly, lefting an unusable system with zero processor time. Interestingly, it is neccessary to run *both* application to have a reproducable hangup. The described problem does not happen if using 2.4.2-XFS. If one runs top with realtime priority in an terminal, one can see that the system memory is exausted. I have about 200 MB RAM, with 2.4.2-XFS and running both application, I still have about 40 MB RAM free (swap partition not used), with 2.4.3-XFS, on the other hand, the memory is used up until the observed swapping and the subsequent hangup. I am using Red Hat 7.1 and installed XFS from the installer 1.0 and updated the XFS associated packages to 1.0.1. I am asking you first because the problem does not happen if using 2.4.2-XFS, though I am not sure whether this problem is attributed to the orignal Red Hat kernel tree, the two applications or the XFS part. I also have a second problem with the XFS kernel. I have both a Matrox G-100 and 3dfx Voodoo 3 2000 graphics card. If I use the 2.4.2 kernel from Red Hat, the card runs under XFree86-4.0.3 (that came along the Red Hat distribution) with full 3D acceleration. If I use the 2.4.2-XFS kernel, most of the 3D intensive application (e. g. Loki games) crashes immediatly after starting or the system hangs up after a few seconds. Also the X server hangs up sometimes. Currently, I circumvent this problem by using the Matrix card. But I really would like to know why such wired things happen. Best regards, Yue Shi Lai From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:06:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJ6sB19222 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:06:54 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJ6qV19200 for ; Mon, 16 Jul 2001 12:06:53 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA09423 for ; Mon, 16 Jul 2001 12:06:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2429837; Mon, 16 Jul 2001 14:05:34 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA34983; Mon, 16 Jul 2001 14:05:33 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GJ6rt19078; Mon, 16 Jul 2001 14:06:53 -0500 Message-Id: <200107161906.f6GJ6rt19078@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Florin Andrei cc: linux-xfs@oss.sgi.com Subject: Re: fine-tuning XFS In-Reply-To: Message from Florin Andrei of "16 Jul 2001 11:45:48 PDT." <995309148.12677.5.camel@stantz.corp.sgi.com> Date: Mon, 16 Jul 2001 14:06:53 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Can you give me, please, some hints on fine-tuning XFS for better > performance for web caches? > A typical Squid cache looks like this: > > - HDD size: 10...30 GB > - average file size: 10...15 kB > - 16 primary directories > - each primary dir contains 256 secondary directories > - each secondary dir can contain up to 256 actual files > - the actual disk usage when the cache is "full" is ~80% (can be tuned > from squid.conf) > > >From the FS point of view, the access to the files is quite random. The > cache fills up first to the maximum size, and then the oldest files are > deleted and replaced with newer files as the clients request them. > > At this point, the only option i use is "noatime". > Do you have any suggestions to improve the speed? Using -o logbufs=8 may help. There is a perl script which is only in the cvs tree at cmd/xfsmisc/xfs_stats.pl If you run this script then it will produce a couple of pages of statistics, there is a section called Log Operations near the end of the first column, if xs_log_noiclogs is incrementing rapidly then the logbufs option will help. If you install pcp (and being internal to sgi you can get access to the graphical interface to this) you can look at these numbers in realtime. It would be interesting to see the rate at which the Directory Operations statistics move, these are where lookup, create and remove show up. In the Tail-Pushing Stats at the top of the second column the xs_sleep_logspace counter going up says that you are driving the log fairly hard and may benefit from a bigger log. I am not sure if you will benefit from using a larger inode size in this filesystem. Steve > > -- > Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:37:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJbLJ21558 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:37:21 -0700 Received: from router.abc (pD4B9D645.dip.t-dialin.net [212.185.214.69]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJbHV21532 for ; Mon, 16 Jul 2001 12:37:17 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6GJZ8o29300; Mon, 16 Jul 2001 21:35:12 +0200 Message-ID: <3B5341BA.1F68F755@baldauf.org> Date: Mon, 16 Jul 2001 21:34:18 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Nikita Danilov CC: Hans Reiser , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Xuan Baldauf , Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nikita Danilov wrote: > Hans Reiser writes: > > Russell Coker wrote: > > > > > > On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > > > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > > > > > Making the server stateless is wrong > > > > > > > > why? > > > > > > Because it leads to all the problems we have seen! Why not have the client > > > have an open file handle (the way Samba works and the way the Unix file > > > system API works)? Then when the server goes down the client sends a request > > > to open the file again... > > If you have 10000 clients each opening 100 files you got 1e6 opened > files on the server---it wouldn't work. NFS was designed to be stateless > to be scalable. Every existing file has at least one name (or is member of the hidden to-be-deleted-directory, and so has a name, too), and an object_id. Suppose the object_id is 32 bytes long. A virtual filedescriptor may be 4 bytes long, some housekeeping metadata 28 bytes, so we will have 64MB occupied in you scenario. Where's the problem? 80% of those 64MB can be swapped out. > > > > > > > > > making the readdir a multioperation act is wrong > > > > > > > > why? i have 3M directories... ar you saying clients should read the > > > > whole things at once? > > > > > > No. findfirst()/findnext() is the correct way of doing this. Forcing the > > > client to read through 3M directory entries to see if "foo.*" matches > > > anything is just wrong. The client should be able to ask for a list of file > > > names matching certain criteria (time stamp, name, ownership, etc). The > > > findfirst() and findnext() APIs on DOS, OS/2, and Windows do this quite well. > > > > there is a fundamental conflict between having cookies, shrinkable directories, and the ability to > > find foo.* without reading the whole directory, all at the same time. > > > > NFS V4 is designed by braindead twerps incapable of layering software when designing it. > > Just cannot stand it. You mean that NFS v4 features database in a kernel > too? (It's our insider joke.) NFS should not be kernel-bound. The nfs server application mimics the applications on the NFS clients. If this is not possible, something is wrong. > > > > > > > > > > If you have 3M directory entries then SMB should kick butt over NFS. > > > > > > Also while we're at it, one of the worst things about NFS is the issue of > > > delete. Because it's stateless NFS servers implement unlink as "mv" and > > > things get nasty from there... > > > > > > -- > > > http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark > > > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark > > > http://www.coker.com.au/projects.html Projects I am working on > > > http://www.coker.com.au/~russell/ My home page > > Nikita. Being "stateless" is only a weak way to implement disconnected operation. If there was state (if the server could know that a client has a filedescriptor to a file), the client could be informed that it's virtual file descriptors to the files to be deleted are invalid now. This only fails if the network is down, so this is a disconnected operation problem. By the way: if NFS was scaleable, why doesn't it allow every handle from the server (like inode numbers, directory position cookies) to be of variable, dynamic, server-determined size? This would be scaleable. P.S.: Hans, how do you prevent object_id|inode reusing? Using mount_id+generation counter per mount? From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:42:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJgqR22092 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:42:52 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJgoV22072 for ; Mon, 16 Jul 2001 12:42:50 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA03716 for ; Mon, 16 Jul 2001 12:40:21 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA82744 for ; Mon, 16 Jul 2001 12:47:21 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 4823C15A46C for ; Mon, 16 Jul 2001 12:41:34 -0700 (PDT) Subject: Re: fine-tuning XFS From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <200107161906.f6GJ6rt19078@jen.americas.sgi.com> References: <200107161906.f6GJ6rt19078@jen.americas.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 12:41:34 -0700 Message-Id: <995312494.12677.8.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 14:06:53 -0500, Steve Lord wrote: > > Using -o logbufs=8 may help. How about "osyncisdsync"? -- Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:46:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJksT22445 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:46:54 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJkqV22424 for ; Mon, 16 Jul 2001 12:46:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA319061 for ; Mon, 16 Jul 2001 21:46:49 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2440911; Mon, 16 Jul 2001 14:45:34 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA33257; Mon, 16 Jul 2001 14:45:33 -0500 (CDT) Subject: Re: fine-tuning XFS From: Eric Sandeen To: Florin Andrei Cc: linux-xfs@oss.sgi.com In-Reply-To: <995312494.12677.8.camel@stantz.corp.sgi.com> References: <200107161906.f6GJ6rt19078@jen.americas.sgi.com> <995312494.12677.8.camel@stantz.corp.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 16 Jul 2001 14:45:36 -0500 Message-Id: <995312736.1138.2.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 12:41:34 -0700, Florin Andrei wrote: > On 16 Jul 2001 14:06:53 -0500, Steve Lord wrote: > > > > Using -o logbufs=8 may help. > > How about "osyncisdsync"? Only matters if you're doing synchronous writes via O_SYNC... are you? -Eric From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:47:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJlid22548 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:47:44 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJlfV22527 for ; Mon, 16 Jul 2001 12:47:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA317829 for ; Mon, 16 Jul 2001 21:47:39 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2440875; Mon, 16 Jul 2001 14:46:23 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA82305; Mon, 16 Jul 2001 14:46:22 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GJlfE19212; Mon, 16 Jul 2001 14:47:41 -0500 Message-Id: <200107161947.f6GJlfE19212@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Florin Andrei cc: linux-xfs@oss.sgi.com Subject: Re: fine-tuning XFS In-Reply-To: Message from Florin Andrei of "16 Jul 2001 12:41:34 PDT." <995312494.12677.8.camel@stantz.corp.sgi.com> Date: Mon, 16 Jul 2001 14:47:41 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On 16 Jul 2001 14:06:53 -0500, Steve Lord wrote: > > > > Using -o logbufs=8 may help. > > How about "osyncisdsync"? This will only make a difference if the applications use O_SYNC Steve > > -- > Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:56:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJuh223376 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:56:43 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJugV23354 for ; Mon, 16 Jul 2001 12:56:42 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJTRM>; Mon, 16 Jul 2001 14:56:06 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643410@AUSMAIL> From: "Gonyou, Austin" To: linux-xfs@oss.sgi.com Subject: RE: fine-tuning XFS Date: Mon, 16 Jul 2001 14:56:06 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk What is a good example of programs which usually will use O_SYNC? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Steve Lord [mailto:lord@sgi.com] > Sent: Monday, July 16, 2001 2:48 PM > To: Florin Andrei > Cc: linux-xfs@oss.sgi.com > Subject: Re: fine-tuning XFS > > > > On 16 Jul 2001 14:06:53 -0500, Steve Lord wrote: > > > > > > Using -o logbufs=8 may help. > > > > How about "osyncisdsync"? > > This will only make a difference if the applications use O_SYNC > > Steve > > > > > -- > > Florin Andrei > > From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:58:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJwCg23615 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:58:12 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJw9V23576 for ; Mon, 16 Jul 2001 12:58:09 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJTRP>; Mon, 16 Jul 2001 14:57:22 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643412@AUSMAIL> From: "Gonyou, Austin" To: "'Xuan Baldauf'" , Nikita Danilov Cc: linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: RE: [reiserfs-list] Re: benchmarks Date: Mon, 16 Jul 2001 14:57:21 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Wouldn't GFS be a good idea then? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Xuan Baldauf [mailto:xuan--reiserfs@baldauf.org] > Sent: Monday, July 16, 2001 2:34 PM > To: Nikita Danilov > Cc: Hans Reiser; Russell Coker; Chris Wedgwood; > rsharpe@ns.aus.com; Xuan > Baldauf; Seth Mos; Federico Sevilla III; linux-xfs@oss.sgi.com; > reiserfs-list@namesys.com > Subject: Re: [reiserfs-list] Re: benchmarks > > > > > Nikita Danilov wrote: > > > Hans Reiser writes: > > > Russell Coker wrote: > > > > > > > > On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > > > > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > > > > > > > Making the server stateless is wrong > > > > > > > > > > why? > > > > > > > > Because it leads to all the problems we have seen! > Why not have the client > > > > have an open file handle (the way Samba works and the > way the Unix file > > > > system API works)? Then when the server goes down the > client sends a request > > > > to open the file again... > > > > If you have 10000 clients each opening 100 files you got 1e6 opened > > files on the server---it wouldn't work. NFS was designed to > be stateless > > to be scalable. > > Every existing file has at least one name (or is member of > the hidden to-be-deleted-directory, and so has > a name, too), and an object_id. Suppose the object_id is 32 > bytes long. A virtual filedescriptor may be 4 > bytes long, some housekeeping metadata 28 bytes, so we will > have 64MB occupied in you scenario. Where's > the problem? 80% of those 64MB can be swapped out. > > > > > > > > > > > > > > making the readdir a multioperation act is wrong > > > > > > > > > > why? i have 3M directories... ar you saying clients > should read the > > > > > whole things at once? > > > > > > > > No. findfirst()/findnext() is the correct way of > doing this. Forcing the > > > > client to read through 3M directory entries to see if > "foo.*" matches > > > > anything is just wrong. The client should be able to > ask for a list of file > > > > names matching certain criteria (time stamp, name, > ownership, etc). The > > > > findfirst() and findnext() APIs on DOS, OS/2, and > Windows do this quite well. > > > > > > there is a fundamental conflict between having cookies, > shrinkable directories, and the ability to > > > find foo.* without reading the whole directory, all at > the same time. > > > > > > NFS V4 is designed by braindead twerps incapable of > layering software when designing it. > > > > Just cannot stand it. You mean that NFS v4 features > database in a kernel > > too? (It's our insider joke.) > > NFS should not be kernel-bound. The nfs server application > mimics the applications on the NFS clients. If > this is not possible, something is wrong. > > > > > > > > > > > > > > > > If you have 3M directory entries then SMB should kick > butt over NFS. > > > > > > > > Also while we're at it, one of the worst things about > NFS is the issue of > > > > delete. Because it's stateless NFS servers implement > unlink as "mv" and > > > > things get nasty from there... > > > > > > > > -- > > > > http://www.coker.com.au/bonnie++/ Bonnie++ hard > drive benchmark > > > > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark > > > > http://www.coker.com.au/projects.html Projects I am working on > > > > http://www.coker.com.au/~russell/ My home page > > > > Nikita. > > Being "stateless" is only a weak way to implement > disconnected operation. If there was state (if the > server could know that a client has a filedescriptor to a > file), the client could be informed that it's > virtual file descriptors to the files to be deleted are > invalid now. This only fails if the network is > down, so this is a disconnected operation problem. > > By the way: if NFS was scaleable, why doesn't it allow every > handle from the server (like inode numbers, > directory position cookies) to be of variable, dynamic, > server-determined size? This would be scaleable. > > P.S.: Hans, how do you prevent object_id|inode reusing? Using > mount_id+generation counter per mount? > > > From owner-linux-xfs@oss.sgi.com Mon Jul 16 12:58:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GJwEt23645 for linux-xfs-outgoing; Mon, 16 Jul 2001 12:58:14 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GJwAV23599 for ; Mon, 16 Jul 2001 12:58:11 -0700 Received: (qmail 27654 invoked from network); 16 Jul 2001 19:58:03 -0000 Received: from srg.access.comstar.ru (HELO beta.namesys.com) (195.210.131.190) by thebsh.namesys.com with SMTP; 16 Jul 2001 19:58:03 -0000 Received: (from god@localhost) by beta.namesys.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id XAA06166; Mon, 16 Jul 2001 23:57:37 +0400 From: Nikita Danilov MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15187.18225.196286.123754@beta.namesys.com> Date: Mon, 16 Jul 2001 23:57:37 +0400 To: Xuan Baldauf Cc: Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks In-Reply-To: <3B5341BA.1F68F755@baldauf.org> References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> X-Mailer: VM 6.89 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Xuan Baldauf writes: > > > Nikita Danilov wrote: > > > Hans Reiser writes: > > > Russell Coker wrote: > > > > > > > > On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > > > > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > > > > > > > Making the server stateless is wrong > > > > > > > > > > why? > > > > > > > > Because it leads to all the problems we have seen! Why not have the client > > > > have an open file handle (the way Samba works and the way the Unix file > > > > system API works)? Then when the server goes down the client sends a request > > > > to open the file again... > > > > If you have 10000 clients each opening 100 files you got 1e6 opened > > files on the server---it wouldn't work. NFS was designed to be stateless > > to be scalable. > > Every existing file has at least one name (or is member of the hidden to-be-deleted-directory, and so has > a name, too), and an object_id. Suppose the object_id is 32 bytes long. A virtual filedescriptor may be 4 > bytes long, some housekeeping metadata 28 bytes, so we will have 64MB occupied in you scenario. Where's > the problem? 80% of those 64MB can be swapped out. For each open file you have: struct file (96b) struct inode (460b) struct dentry (112b) at least. This totals to 668M of kernel memory, that is, unpageable. All files are kept in several hash tables and hash-tables are known to degrade. Well, actually, I am afraid current Linux kernels cannot open 1e6 of files. > > > > > > > > > > > > > > making the readdir a multioperation act is wrong > > > > > > > > > > why? i have 3M directories... ar you saying clients should read the > > > > > whole things at once? > > > > > > > > No. findfirst()/findnext() is the correct way of doing this. Forcing the > > > > client to read through 3M directory entries to see if "foo.*" matches > > > > anything is just wrong. The client should be able to ask for a list of file > > > > names matching certain criteria (time stamp, name, ownership, etc). The > > > > findfirst() and findnext() APIs on DOS, OS/2, and Windows do this quite well. > > > > > > there is a fundamental conflict between having cookies, shrinkable directories, and the ability to > > > find foo.* without reading the whole directory, all at the same time. > > > > > > NFS V4 is designed by braindead twerps incapable of layering software when designing it. > > > > Just cannot stand it. You mean that NFS v4 features database in a kernel > > too? (It's our insider joke.) > > NFS should not be kernel-bound. The nfs server application mimics the applications on the NFS clients. If > this is not possible, something is wrong. > > > > > > > > > > > > > > > > If you have 3M directory entries then SMB should kick butt over NFS. > > > > > > > > Also while we're at it, one of the worst things about NFS is the issue of > > > > delete. Because it's stateless NFS servers implement unlink as "mv" and > > > > things get nasty from there... > > > > > > > > -- > > > > http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark > > > > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark > > > > http://www.coker.com.au/projects.html Projects I am working on > > > > http://www.coker.com.au/~russell/ My home page > > > > Nikita. > > Being "stateless" is only a weak way to implement disconnected > operation. If there was state (if the > server could know that a client has a filedescriptor to a file), the > client could be informed that it's > virtual file descriptors to the files to be deleted are invalid > now. This only fails if the network is > down, so this is a disconnected operation problem. > > By the way: if NFS was scaleable, why doesn't it allow every handle > from the server (like inode numbers, > directory position cookies) to be of variable, dynamic, > server-determined size? This would be scaleable. > > P.S.: Hans, how do you prevent object_id|inode reusing? Using > mount_id+generation counter per mount? There is generation counter stored persistently with super-block, incremented on each inode deletion. > Nikita. From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:01:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GK1mQ24128 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:01:48 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GK1kV24108 for ; Mon, 16 Jul 2001 13:01:46 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id WAA319336 for ; Mon, 16 Jul 2001 22:01:44 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id NAA80861 for ; Mon, 16 Jul 2001 13:06:15 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 94F5115A46C for ; Mon, 16 Jul 2001 13:00:27 -0700 (PDT) Subject: Re: fine-tuning XFS From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <995312736.1138.2.camel@stout.americas.sgi.com> References: <200107161906.f6GJ6rt19078@jen.americas.sgi.com> <995312494.12677.8.camel@stantz.corp.sgi.com> <995312736.1138.2.camel@stout.americas.sgi.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 13:00:27 -0700 Message-Id: <995313627.12676.9.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 14:45:36 -0500, Eric Sandeen wrote: > On 16 Jul 2001 12:41:34 -0700, Florin Andrei wrote: > > On 16 Jul 2001 14:06:53 -0500, Steve Lord wrote: > > > > > > Using -o logbufs=8 may help. > > > > How about "osyncisdsync"? > > Only matters if you're doing synchronous writes via O_SYNC... are you? No, i'm not. Thank you. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:03:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GK3Qa24352 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:03:26 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GK3OV24332 for ; Mon, 16 Jul 2001 13:03:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA09529 for ; Mon, 16 Jul 2001 13:00:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA1849864; Mon, 16 Jul 2001 15:00:26 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA30829; Mon, 16 Jul 2001 15:00:26 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GK1iB19259; Mon, 16 Jul 2001 15:01:44 -0500 Message-Id: <200107162001.f6GK1iB19259@jen.americas.sgi.com> To: "Gonyou, Austin" cc: linux-xfs@oss.sgi.com Subject: Re: fine-tuning XFS References: <85063BBE668FD411944400D0B744267A643410@AUSMAIL> Comments: In-reply-to "Gonyou, Austin" message dated "Mon, 16 Jul 2001 14:56:06 -0500." Date: Mon, 16 Jul 2001 15:01:44 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > What is a good example of programs which usually will use O_SYNC? > sendmail and xfsdump Steve From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:09:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GK9Ua24796 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:09:30 -0700 Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [12.13.237.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GK9QV24772 for ; Mon, 16 Jul 2001 13:09:26 -0700 Received: from slb-av-01.boeing.com ([129.172.13.4]) by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id NAA01156 for ; Mon, 16 Jul 2001 13:08:58 -0700 (PDT) Received: from slb-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-01) with ESMTP id NAA26564 for ; Mon, 16 Jul 2001 13:09:24 -0700 (PDT) Received: from [136.203.14.68] by slb-hub-01.boeing.com with ESMTP; Mon, 16 Jul 2001 13:09:14 -0700 Message-Id: <3B5349EA.7080900@pipcws.ca.boeing.com> Date: Mon, 16 Jul 2001 13:09:14 -0700 From: Ric Tibbetts User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: en-us MIME-Version: 1.0 To: Linux XFS Mailing List , JFS Discussion List Subject: LVM on Linux Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk For anyone considering using LVM on Linux. You might want to take a second to look at the following "short" article. It casts a questionalble light on the current state of the LVM code. ================================================ 0 Jun - 5 Jul (8 posts) Archive Link: [RFC][PATCH] first cut 64 bit block support Summary by Zack Brown Ben LaHaise posted a patch and announced, "Below is the first cut at making the block size limit configurable to 64 bits on x86, as well as always 64 bits on 64 bit machines. The audit isn't complete yet, but a good chunk of it is done." [..] "The following should be 64 bit clean now: nbd, loop, raid0, raid1, raid5." He gave links to two homepages at http://people.redhat.com/bcrl/lb/ and http://www.kvack.org/~blah/lb/. He added, "Ugly bits: I had to add libgcc.a to satisfy the need for 64 bit division. Yeah, it sucks, but RAID needs some more massaging before I can remove the 64 bit division completely. This will be fixed." Chris Wedgwood proposed some changes to libgcc.a to be less ugly, and Ben replied, "I'm getting rid of the need for libgcc entirely. That's what "This will be fixed" means. If you want to expedite the process, send a patch. Until then, this is Good Enough for testing purposes." Elsewhere, Ragnar Kjarstad was very happy about Ben's work, asking if LVM was also 64-bit clean. Ben replied cryptically, "Errr, I'll refrain from talking about LVM." Ragnar wanted some clarification, and Ben explained: Fixing LVM is not on the radar of my priorities. The code is sorely in need of a rewrite and violates several of the basic planning tenents that any good code in the block layer should follow. Namely, it should have 1) planned on supporting 64 bit offsets, 2) never used multiplication, division or modulus on block numbers, and 3) don't allocate memory structures that are indexed by block numbers. LVM failed on all three of these -- and this si just what I noticed in a quick 5 minute glance through the code. Sorry, but LVM is obsolete by design. It will continue to work on 32 bit block devices, but if you try to use it beyond that, it will fail. That said, we'll have to make sure these failures are graceful and occur prior to the user having a chance at loosing any data. Now, thankfully there are alternatives like ELVM, which are working on getting the details right from the lessons learned. Given that, I think we'll be in good shape during the 2.5 cycle. End Of Thread (tm). From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:25:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKPMj26010 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:25:22 -0700 Received: from router.abc (p3EE00E9E.dip.t-dialin.net [62.224.14.158]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKPIV25986 for ; Mon, 16 Jul 2001 13:25:18 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6GKGeo29690; Mon, 16 Jul 2001 22:16:40 +0200 Message-ID: <3B534B74.BDE19961@baldauf.org> Date: Mon, 16 Jul 2001 22:15:48 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Nikita Danilov CC: Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nikita Danilov wrote: > Xuan Baldauf writes: > > > > > > Nikita Danilov wrote: > > > > > Hans Reiser writes: > > > > Russell Coker wrote: > > > > > > > > > > On Mon, 16 Jul 2001 11:00, Chris Wedgwood wrote: > > > > > > On Sun, Jul 15, 2001 at 02:01:09PM +0400, Hans Reiser wrote: > > > > > > > > > > > > Making the server stateless is wrong > > > > > > > > > > > > why? > > > > > > > > > > Because it leads to all the problems we have seen! Why not have the client > > > > > have an open file handle (the way Samba works and the way the Unix file > > > > > system API works)? Then when the server goes down the client sends a request > > > > > to open the file again... > > > > > > If you have 10000 clients each opening 100 files you got 1e6 opened > > > files on the server---it wouldn't work. NFS was designed to be stateless > > > to be scalable. > > > > Every existing file has at least one name (or is member of the hidden to-be-deleted-directory, and so has > > a name, too), and an object_id. Suppose the object_id is 32 bytes long. A virtual filedescriptor may be 4 > > bytes long, some housekeeping metadata 28 bytes, so we will have 64MB occupied in you scenario. Where's > > the problem? 80% of those 64MB can be swapped out. > > For each open file you have: > > struct file (96b) > struct inode (460b) > struct dentry (112b) > > at least. This totals to 668M of kernel memory, that is, unpageable. As I said below, the NFS server should be a user-space daemon.. > > All files are kept in several hash tables and hash-tables are known to > degrade. Well, actually, I am afraid current Linux kernels cannot open > 1e6 of files. This is one thing I cannot understand, too. > > > > > > > > > > > > > > > > > > > > > making the readdir a multioperation act is wrong > > > > > > > > > > > > why? i have 3M directories... ar you saying clients should read the > > > > > > whole things at once? > > > > > > > > > > No. findfirst()/findnext() is the correct way of doing this. Forcing the > > > > > client to read through 3M directory entries to see if "foo.*" matches > > > > > anything is just wrong. The client should be able to ask for a list of file > > > > > names matching certain criteria (time stamp, name, ownership, etc). The > > > > > findfirst() and findnext() APIs on DOS, OS/2, and Windows do this quite well. > > > > > > > > there is a fundamental conflict between having cookies, shrinkable directories, and the ability to > > > > find foo.* without reading the whole directory, all at the same time. > > > > > > > > NFS V4 is designed by braindead twerps incapable of layering software when designing it. > > > > > > Just cannot stand it. You mean that NFS v4 features database in a kernel > > > too? (It's our insider joke.) > > > > NFS should not be kernel-bound. The nfs server application mimics the applications on the NFS clients. If > > this is not possible, something is wrong. > > > > > > > > > > > > > > > > > > > > > > If you have 3M directory entries then SMB should kick butt over NFS. > > > > > > > > > > Also while we're at it, one of the worst things about NFS is the issue of > > > > > delete. Because it's stateless NFS servers implement unlink as "mv" and > > > > > things get nasty from there... > > > > > > > > > > -- > > > > > http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark > > > > > http://www.coker.com.au/postal/ Postal SMTP/POP benchmark > > > > > http://www.coker.com.au/projects.html Projects I am working on > > > > > http://www.coker.com.au/~russell/ My home page > > > > > > Nikita. > > > > Being "stateless" is only a weak way to implement disconnected > > operation. If there was state (if the > > server could know that a client has a filedescriptor to a file), the > > client could be informed that it's > > virtual file descriptors to the files to be deleted are invalid > > now. This only fails if the network is > > down, so this is a disconnected operation problem. > > > > By the way: if NFS was scaleable, why doesn't it allow every handle > > from the server (like inode numbers, > > directory position cookies) to be of variable, dynamic, > > server-determined size? This would be scaleable. > > > > P.S.: Hans, how do you prevent object_id|inode reusing? Using > > mount_id+generation counter per mount? > > There is generation counter stored persistently with super-block, > incremented on each inode deletion. Is the superblock always logged on inode-deletion for other reasons than the generation counter? If not, would the above method be more efficient, because it does not require logging superblocks? > > > > > > Nikita. From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:28:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKSIl26377 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:28:18 -0700 Received: from cairn-gorm.cragtech.com (mail.connex.com [216.100.236.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKSFV26355 for ; Mon, 16 Jul 2001 13:28:15 -0700 Received: by cairn-gorm.cragtech.com with Internet Mail Service (5.5.2650.21) id ; Mon, 16 Jul 2001 13:25:44 -0700 Message-ID: From: Dale Stephenson To: Linux XFS Mailing List , JFS Discussion List Subject: RE: LVM on Linux Date: Mon, 16 Jul 2001 13:25:44 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GKSFV26356 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The article mentioned is from kernel-traffic. The thread continued on the linux-lvm list (though currently it has mutated into a interesting discussion of write caches on hard drives). Here's the most recent post on "state of the LVM code": http://lists.sistina.com/pipermail/linux-lvm/2001-July/007866.html ### BEGIN POST On Thu, Jul 05, 2001 at 03:35:31AM -0400, Ben LaHaise wrote: > On Thu, 5 Jul 2001, Ragnar Kjørstad wrote: > > > What do you mean? > > Is it not feasible to fix this in LVM as well, or do you just not know > > what needs to be done to LVM? > > Fixing LVM is not on the radar of my priorities. The code is sorely in > need of a rewrite and violates several of the basic planning tenents that > any good code in the block layer should follow. Namely, it should have 1) > planned on supporting 64 bit offsets, What is the particular problem with 1? Changes need to take place in the whole block device layer during 2.5 development in order to be 64 bit clean. LVM will just be one member of the bunch :-) > 2) never used multiplication, > division or modulus on block numbers, I assume that you mean an advice ("never use") rather than a statement that you never used it, right? FYI: this takes place in multiple block device layer functions. For sure you can argue that this is supposed to vanish in 2.5 but were's the document recommending this and defining how to do it? > and 3) don't allocate memory > structures that are indexed by block numbers. Why? Remapping block devices do that! Checks against index mismatches are in LVM already. > Even LVM failed on all three of > these -- and this si just what I noticed in a quick 5 minute glance > through the code. Sorry, but LVM is obsolete by design. Sorry but you are argueing weakly in a political manor. Please speak up clearly and talk about the caveats you see and change request you recommend as an expert or say nothing! > It will continue > to work on 32 bit block devices, but if you try to use it beyond that, it > will fail. As I said above. During the 2.5 development cycle it will be addressed. > That said, we'll have to make sure these failures are graceful > and occur prior to the user having a chance at loosing any data. Once 64 bit support will be implemented in the block device layer and the VFS, LVM as a block device layer entity will support it as well :-) > > Now, thankfully there are alternatives like ELVM, which are working on > getting the details right from the lessons learned. ELVM is not in production so far... If you would have read the EVMS kernel code, you had realized that they do modulo calculations as well and I think they are doing right! > Given that, I think > we'll be in good shape during the 2.5 cycle. I agree (from a different standpoint though ;-) Waiting for your serious advice... > > -ben > > _______________________________________________ > linux-lvm mailing list > linux-lvm@sistina.com > http://lists.sistina.com/mailman/listinfo/linux-lvm > read the LVM HOW-TO at http://www.sistina.com/lvm/Pages/howto.html -- Regards, Heinz -- The LVM Guy -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =- Heinz Mauelshagen Sistina Software Inc. Senior Consultant/Developer Am Sonnenhang 11 56242 Marienrachdorf Germany Mauelshagen@Sistina.com +49 2626 141200 FAX 924446 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =- ###END POST Ben LaHaise has not responded publicly. Dale Stephenson steph@connex.com From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:33:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKXhs27043 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:33:43 -0700 Received: from ns.tgs.org.za (ndf-dial-196-30-124-40.mweb.co.za [196.30.124.40]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKXUV26994 for ; Mon, 16 Jul 2001 13:33:33 -0700 Received: from yavin (yavin.tgs.org.za [10.0.0.2]) by ns.tgs.org.za (8.11.4/8.11.4) with SMTP id f6GKl4A01537; Mon, 16 Jul 2001 22:47:05 +0200 Reply-To: From: "Theo" To: "Ric Tibbetts" , "Linux XFS Mailing List" , "JFS Discussion List" Subject: RE: [Jfs-discussion] LVM on Linux Date: Mon, 16 Jul 2001 22:32:17 +0200 Message-ID: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-reply-to: <3B5349EA.7080900@pipcws.ca.boeing.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm using LVM. Only ext2 on the LVM volume. I have JFS & XFS on it's own. ELVM ?? Never knew something like that exists, where is it ? Probably only work on 64-bit bit block devices ? -----Original Message----- From: jfs-discussion-admin@oss.lotus.com [mailto:jfs-discussion-admin@oss.lotus.com]On Behalf Of Ric Tibbetts Sent: 16 July 2001 10:09 To: Linux XFS Mailing List; JFS Discussion List Subject: [Jfs-discussion] LVM on Linux For anyone considering using LVM on Linux. You might want to take a second to look at the following "short" article. It casts a questionalble light on the current state of the LVM code. ================================================ 0 Jun - 5 Jul (8 posts) Archive Link: [RFC][PATCH] first cut 64 bit block support Summary by Zack Brown Ben LaHaise posted a patch and announced, "Below is the first cut at making the block size limit configurable to 64 bits on x86, as well as always 64 bits on 64 bit machines. The audit isn't complete yet, but a good chunk of it is done." [..] "The following should be 64 bit clean now: nbd, loop, raid0, raid1, raid5." He gave links to two homepages at http://people.redhat.com/bcrl/lb/ and http://www.kvack.org/~blah/lb/. He added, "Ugly bits: I had to add libgcc.a to satisfy the need for 64 bit division. Yeah, it sucks, but RAID needs some more massaging before I can remove the 64 bit division completely. This will be fixed." Chris Wedgwood proposed some changes to libgcc.a to be less ugly, and Ben replied, "I'm getting rid of the need for libgcc entirely. That's what "This will be fixed" means. If you want to expedite the process, send a patch. Until then, this is Good Enough for testing purposes." Elsewhere, Ragnar Kjarstad was very happy about Ben's work, asking if LVM was also 64-bit clean. Ben replied cryptically, "Errr, I'll refrain from talking about LVM." Ragnar wanted some clarification, and Ben explained: Fixing LVM is not on the radar of my priorities. The code is sorely in need of a rewrite and violates several of the basic planning tenents that any good code in the block layer should follow. Namely, it should have 1) planned on supporting 64 bit offsets, 2) never used multiplication, division or modulus on block numbers, and 3) don't allocate memory structures that are indexed by block numbers. LVM failed on all three of these -- and this si just what I noticed in a quick 5 minute glance through the code. Sorry, but LVM is obsolete by design. It will continue to work on 32 bit block devices, but if you try to use it beyond that, it will fail. That said, we'll have to make sure these failures are graceful and occur prior to the user having a chance at loosing any data. Now, thankfully there are alternatives like ELVM, which are working on getting the details right from the lessons learned. Given that, I think we'll be in good shape during the 2.5 cycle. End Of Thread (tm). _______________________________________________ Jfs-discussion mailing list Jfs-discussion@oss.software.ibm.com http://oss.software.ibm.com/developerworks/opensource/mailman/listinfo/jfs-d iscussion From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:33:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKXl527103 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:33:47 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKXjV27069 for ; Mon, 16 Jul 2001 13:33:45 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id WAA31588; Mon, 16 Jul 2001 22:32:43 +0200 Date: Mon, 16 Jul 2001 22:32:42 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Xuan Baldauf Cc: Nikita Danilov , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010716223240.D14564@vestdata.no> References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <3B534B74.BDE19961@baldauf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <3B534B74.BDE19961@baldauf.org>; from Xuan Baldauf on Mon, Jul 16, 2001 at 10:15:48PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > For each open file you have: > > > > struct file (96b) > > struct inode (460b) > > struct dentry (112b) > > > > at least. This totals to 668M of kernel memory, that is, unpageable. > > As I said below, the NFS server should be a user-space daemon.. But the datastructures mentioned above would still be kernel-memory, so that will not solve the problem. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:41:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKfiZ27883 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:41:44 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKfdV27863 for ; Mon, 16 Jul 2001 13:41:39 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id WAA32279; Mon, 16 Jul 2001 22:41:27 +0200 Date: Mon, 16 Jul 2001 22:41:26 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Mike Gigante Cc: Simon Matter , "P.Dixon" , linux-xfs@oss.sgi.com Subject: Re: benchmarks Message-ID: <20010716224126.E14564@vestdata.no> References: <3B4EB3D5.ED80FC6B@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Mike Gigante on Fri, Jul 13, 2001 at 09:20:59PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 13, 2001 at 09:20:59PM +1000, Mike Gigante wrote: > > XFS is pretty tuneable - so you could play with inode size, log size > number of allocation groups etc to best suit your usage. > > Such tuning doesn't seem possible with ReiserFS ... Reiserfs doesn't have inodes or allocation groups, so naturally you can't change them. :-) However, it does use a pretty modular system for some datastructures - eg the stat-data and hashes. This means you can add a different hash og a different kind of stat-data (e.g. maybe you don't need timestamps for your files) rellatively easy. (yes, it requires changing kernel code, but is still rellatively easy). I believe you now can change the logsize though (maybe you still need a patch). > The mongo benchmarks use relatively small files. XFS scales very well to > large files/directories, but that benchmark sticks to small scale stuff. > It *seems* to show ReiserFS in the best possible light and the XFS results > don't seem to reflect anything like real world experience (except that it > correctly highlights the relatively slow delete performance of XFS!) I partly disagree. mongo tests filesystem performace - benchmarks that test writing really big files is mostly testing your hardware. The filesystem still matters, but not so much as on small files. I think the difference between ext2/xfs/reiserfs is less than 10%. (ext3 with datalogging may be a different story though). -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:47:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKl6728465 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:47:06 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKl4V28446 for ; Mon, 16 Jul 2001 13:47:04 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJTY2>; Mon, 16 Jul 2001 15:46:57 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643419@AUSMAIL> From: "Gonyou, Austin" To: "'Ric Tibbetts'" , Linux XFS Mailing List , JFS Discussion List Subject: RE: LVM on Linux Date: Mon, 16 Jul 2001 15:46:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk It would be much nicer to know, what frame the 64-bit is that he's talking about here. Also, If you have an enterprise storage system like EMC or Hitatchi, you're probably running hardware level mirroring/RAID anyway. At that point, there should be no need to worry if LVM is ready for that, since you'r probably going to concatenate anyway or do striping. (since that's all you need to do cause you're letting the hardware handle the other stuff for you) So I don't see a big issue here when doing this. Plus, you could always just use MD or RD anyway. For something like I use with EMC, and have mirrored disks anyway, It's not a problem, cause I just stripe. Everything else is already mirrored for me, so LVM is applying no major logic, other than what it was built to do. Also, ELVM? I believe it's EVMS, from IBM. The Enterprise Volume Management System. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Ric Tibbetts [mailto:ric@pipcws.ca.boeing.com] > Sent: Monday, July 16, 2001 3:09 PM > To: Linux XFS Mailing List; JFS Discussion List > Subject: LVM on Linux > > > For anyone considering using LVM on Linux. You might want to take a > second to look at the following "short" article. It casts a > questionalble light on the current state of the LVM code. > > ================================================ > > 0 Jun - 5 Jul (8 posts) Archive Link: [RFC][PATCH] first cut > 64 bit block > support > Summary by Zack Brown > > Ben LaHaise posted a patch and announced, "Below is the first > cut at making > the block size limit configurable to 64 bits on x86, as well > as always 64 > bits on 64 bit machines. The audit isn't complete yet, but a > good chunk of > it is done." [..] "The following should be 64 bit clean now: > nbd, loop, > raid0, raid1, raid5." He gave links to two homepages at > http://people.redhat.com/bcrl/lb/ and > http://www.kvack.org/~blah/lb/. He added, "Ugly bits: I had > to add libgcc.a > to satisfy the need for 64 bit division. Yeah, it sucks, but > RAID needs some > more massaging before I can remove the 64 bit division > completely. This will > be fixed." Chris Wedgwood proposed some changes to libgcc.a > to be less ugly, > and Ben replied, "I'm getting rid of the need for libgcc > entirely. That's > what "This will be fixed" means. If you want to expedite the > process, send a > patch. Until then, this is Good Enough for testing purposes." > > Elsewhere, Ragnar Kjarstad was very happy about Ben's work, > asking if LVM > was also 64-bit clean. Ben replied cryptically, "Errr, I'll > refrain from > talking about LVM." Ragnar wanted some clarification, and Ben > explained: > > Fixing LVM is not on the radar of my priorities. The code is > sorely in need > of a > rewrite and violates several of the basic planning tenents > that any good > code in the block layer should follow. Namely, it should have > 1) planned on > supporting 64 bit offsets, 2) never used multiplication, > division or modulus > on block numbers, and 3) don't allocate memory structures > that are indexed > by block numbers. LVM failed on all three of these -- and > this si just what > I noticed in a quick 5 minute glance through the code. Sorry, > but LVM is > obsolete by design. It will continue to work on 32 bit block > devices, but if > you try to use it beyond that, it will fail. That said, we'll > have to make > sure these failures are graceful and occur prior to the user > having a chance > at loosing any data. > > Now, thankfully there are alternatives like ELVM, which are working on > getting the > details right from the lessons learned. Given that, I think > we'll be in good > shape > during the 2.5 cycle. > > End Of Thread (tm). > > From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:49:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKnrR28852 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:49:53 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKnpV28830 for ; Mon, 16 Jul 2001 13:49:51 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id WAA00575; Mon, 16 Jul 2001 22:49:43 +0200 Date: Mon, 16 Jul 2001 22:49:42 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Theo Cc: Ric Tibbetts , Linux XFS Mailing List , JFS Discussion List Subject: Re: [Jfs-discussion] LVM on Linux Message-ID: <20010716224942.F14564@vestdata.no> References: <3B5349EA.7080900@pipcws.ca.boeing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Theo on Mon, Jul 16, 2001 at 10:32:17PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 16, 2001 at 10:32:17PM +0200, Theo wrote: > I'm using LVM. Only ext2 on the LVM volume. I have JFS & XFS on it's own. > > ELVM ?? Never knew something like that exists, where is it ? Probably only > work on 64-bit bit block devices ? He probably meant EVMS; http://sourceforge.net/projects/evms/ And no, it doesn't really exist - it's still pre-alpha. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:52:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKqCM29196 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:52:12 -0700 Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [12.13.237.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKqAV29176 for ; Mon, 16 Jul 2001 13:52:10 -0700 Received: from slb-av-01.boeing.com ([129.172.13.4]) by slb-smtpout-01.boeing.com (8.9.2/8.8.5-M2) with ESMTP id NAA11289 for ; Mon, 16 Jul 2001 13:51:41 -0700 (PDT) Received: from slb-hub-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.9.3/8.9.2/MBS-AV-01) with ESMTP id NAA14722 for ; Mon, 16 Jul 2001 13:52:08 -0700 (PDT) Received: from [136.203.14.68] by slb-hub-01.boeing.com with ESMTP; Mon, 16 Jul 2001 13:52:00 -0700 Message-Id: <3B5353EF.8010304@pipcws.ca.boeing.com> Date: Mon, 16 Jul 2001 13:52:00 -0700 From: Ric Tibbetts User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: en-us MIME-Version: 1.0 To: Linux XFS Mailing List , JFS Discussion List Subject: Re: LVM on Linux References: <3B5349EA.7080900@pipcws.ca.boeing.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I should have specified in my original post: The comments contained the the snippet of thread on this topic are not my own. The piece was taken directly from another conversation, between other individuals. I forwarded it along for the information of the folks here that were/are considering using LVM on their Linux boxes. Beyond that, I claim no responsibilty for the content. Ric Tibbetts wrote: > For anyone considering using LVM on Linux. You might want to take a > second to look at the following "short" article. It casts a > questionalble light on the current state of the LVM code. > > ================================================ > > 0 Jun - 5 Jul (8 posts) Archive Link: [RFC][PATCH] first cut 64 bit block > support > Summary by Zack Brown > > Ben LaHaise posted a patch and announced, "Below is the first cut at > making > the block size limit configurable to 64 bits on x86, as well as always 64 > bits on 64 bit machines. The audit isn't complete yet, but a good > chunk of > it is done." [..] "The following should be 64 bit clean now: nbd, loop, > raid0, raid1, raid5." He gave links to two homepages at > http://people.redhat.com/bcrl/lb/ and > http://www.kvack.org/~blah/lb/. He added, "Ugly bits: I had to add > libgcc.a > to satisfy the need for 64 bit division. Yeah, it sucks, but RAID > needs some > more massaging before I can remove the 64 bit division completely. > This will > be fixed." Chris Wedgwood proposed some changes to libgcc.a to be less > ugly, > and Ben replied, "I'm getting rid of the need for libgcc entirely. That's > what "This will be fixed" means. If you want to expedite the process, > send a > patch. Until then, this is Good Enough for testing purposes." > > Elsewhere, Ragnar Kjarstad was very happy about Ben's work, asking if LVM > was also 64-bit clean. Ben replied cryptically, "Errr, I'll refrain from > talking about LVM." Ragnar wanted some clarification, and Ben explained: > > Fixing LVM is not on the radar of my priorities. The code is sorely in > need > of a > rewrite and violates several of the basic planning tenents that any good > code in the block layer should follow. Namely, it should have 1) > planned on > supporting 64 bit offsets, 2) never used multiplication, division or > modulus > on block numbers, and 3) don't allocate memory structures that are > indexed > by block numbers. LVM failed on all three of these -- and this si just > what > I noticed in a quick 5 minute glance through the code. Sorry, but LVM is > obsolete by design. It will continue to work on 32 bit block devices, > but if > you try to use it beyond that, it will fail. That said, we'll have to > make > sure these failures are graceful and occur prior to the user having a > chance > at loosing any data. > > Now, thankfully there are alternatives like ELVM, which are working on > getting the > details right from the lessons learned. Given that, I think we'll be > in good > shape > during the 2.5 cycle. > > End Of Thread (tm). > > From owner-linux-xfs@oss.sgi.com Mon Jul 16 13:54:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GKsRJ29490 for linux-xfs-outgoing; Mon, 16 Jul 2001 13:54:27 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GKsPV29468 for ; Mon, 16 Jul 2001 13:54:25 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id WAA00966; Mon, 16 Jul 2001 22:54:19 +0200 Date: Mon, 16 Jul 2001 22:54:18 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: "Gonyou, Austin" Cc: "'Ric Tibbetts'" , Linux XFS Mailing List , JFS Discussion List Subject: Re: LVM on Linux Message-ID: <20010716225418.G14564@vestdata.no> References: <85063BBE668FD411944400D0B744267A643419@AUSMAIL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <85063BBE668FD411944400D0B744267A643419@AUSMAIL>; from Gonyou, Austin on Mon, Jul 16, 2001 at 03:46:57PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 16, 2001 at 03:46:57PM -0500, Gonyou, Austin wrote: > It would be much nicer to know, what frame the 64-bit is that he's talking > about here. Also, If you have an enterprise storage system like EMC or > Hitatchi, you're probably running hardware level mirroring/RAID anyway. At > that point, there should be no need to worry if LVM is ready for that, since > you'r probably going to concatenate anyway or do striping. (since that's all > you need to do cause you're letting the hardware handle the other stuff for > you) So I don't see a big issue here when doing this. Plus, you could always > just use MD or RD anyway. For something like I use with EMC, and have > mirrored disks anyway, It's not a problem, cause I just stripe. Everything > else is already mirrored for me, so LVM is applying no major logic, other > than what it was built to do. Also, ELVM? I believe it's EVMS, from IBM. The > Enterprise Volume Management System. Even for highend RAID's there are lots of reasons to use LVM/EVMS: * load balancing across multiple scsi-channels (not implemented yet) * Dynamic partitioning * Volumes spanning multiple physical devices * snapshotting. Basicly handling this is software adds a lot of flexibility. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:06:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GL66w30770 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:06:06 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GL63V30746 for ; Mon, 16 Jul 2001 14:06:03 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id OAA03422 for ; Mon, 16 Jul 2001 14:03:34 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2445465 for ; Mon, 16 Jul 2001 16:04:47 -0500 (CDT) Received: from chuckle.americas.sgi.com (IDENT:root@chuckle.americas.sgi.com [128.162.211.44]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA54993 for ; Mon, 16 Jul 2001 16:04:46 -0500 (CDT) Received: (from sandeen@localhost) by chuckle.americas.sgi.com (8.11.2/8.11.2) id f6GL4kp14037 for linux-xfs@oss.sgi.com; Mon, 16 Jul 2001 16:04:46 -0500 Date: Mon, 16 Jul 2001 16:04:46 -0500 From: Eric Sandeen Message-Id: <200107162104.f6GL4kp14037@chuckle.americas.sgi.com> Subject: TAKE - Don't use BLKBSZSET in xfsprogs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We originally used our added BLKBSZSET ioctl to set the blocksize on a device to 512 bytes during mkfs, this was in case we inherited another blocksize from a previous filesystem (i.e. 4k from ext2). Otherwise, some writes during mkfs.xfs time would fail. However, those writes are now gone from mkfs.xfs, and there doesn't seem to be any other compelling reason to do this. At this point, our added BLKBSZSET/BLKBSZGET ioctls just make our diff from Linus' kernel that much bigger. By turning this off in userspace now, we can start getting the updated tools to users before we take the ioctls back out of the kernel. If mkfs.xfs suddenly starts going wrong for you as a result, just set cmd/xfsprogs/libxfs/Makefile:LCFLAGS += -DHAVE_BLKBSZSET=0 back to cmd/xfsprogs/libxfs/Makefile:LCFLAGS += -DHAVE_BLKBSZSET=1 and post a bug to the list...! Date: Mon Jul 16 13:56:07 PDT 2001 Workarea: chuckle.americas.sgi.com:/export/xfs1/eric/linux-2.4-xfs/workarea The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98965a cmd/xfsprogs/libxfs/Makefile - 1.7 - Turn off use of the BLKBSZSET ioctl (which will likely go away soon) From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:11:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GLBck31306 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:11:38 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GLBYV31287 for ; Mon, 16 Jul 2001 14:11:34 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA323265 for ; Mon, 16 Jul 2001 23:11:31 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2445194; Mon, 16 Jul 2001 16:10:07 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA69503; Mon, 16 Jul 2001 16:10:07 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GLBPQ24732; Mon, 16 Jul 2001 16:11:25 -0500 Message-Id: <200107162111.f6GLBPQ24732@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= cc: Mike Gigante , Simon Matter , "P.Dixon" , linux-xfs@oss.sgi.com Subject: Re: benchmarks In-Reply-To: Message from =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= of "Mon, 16 Jul 2001 22:41:26 +0200." <20010716224126.E14564@vestdata.no> Date: Mon, 16 Jul 2001 16:11:25 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > The mongo benchmarks use relatively small files. XFS scales very well to > > large files/directories, but that benchmark sticks to small scale stuff. > > It *seems* to show ReiserFS in the best possible light and the XFS results > > don't seem to reflect anything like real world experience (except that it > > correctly highlights the relatively slow delete performance of XFS!) > > I partly disagree. mongo tests filesystem performace - benchmarks that > test writing really big files is mostly testing your hardware. The > filesystem still matters, but not so much as on small files. I think > the difference between ext2/xfs/reiserfs is less than 10%. (ext3 with > datalogging may be a different story though). > > mongo tests how the filesystem behaves under the endcase of continuous metadata load from an application which is doing nothing with the data except reading it and writing it. It is a rare application which behaves in this way, but it is a very common benchmark, the filesystem is there to provide service to applications, not to consume all the resources of the machine. Note that I am not arguing for one filesystem or another, just commenting on the nature of filesystem benchmarks, reiserfs is good for some things, XFS is good for others. Steve > > -- > Ragnar Kjorstad > Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:20:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GLKfv31895 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:20:41 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GLKdV31876 for ; Mon, 16 Jul 2001 14:20:39 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA16190; Mon, 16 Jul 2001 23:20:37 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id XAA11525; Mon, 16 Jul 2001 23:20:37 +0200 (CEST) Date: Mon, 16 Jul 2001 23:20:37 +0200 (CEST) From: Seth Mos To: Eric Sandeen cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - Don't use BLKBSZSET in xfsprogs In-Reply-To: <995318092.1481.1.camel@stout.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001, Eric Sandeen wrote: > On 16 Jul 2001 23:11:50 +0200, Seth Mos wrote: > > On Mon, 16 Jul 2001, Eric Sandeen wrote: > > > > > We originally used our added BLKBSZSET ioctl to set the blocksize on a device > > > to 512 bytes during mkfs, this was in case we inherited another blocksize > > > from a previous filesystem (i.e. 4k from ext2). Otherwise, some writes > > > during mkfs.xfs time would fail. However, those writes are now gone from > > > mkfs.xfs, and there doesn't seem to be any other compelling reason to do this. > > > > > > At this point, our added BLKBSZSET/BLKBSZGET ioctls just make our diff > > > from Linus' kernel that much bigger. > > > > Does that mean that the can't set blocksize erro on raid controllers and > > softraid will be eradicated? > > Hm, I didn't know those errors were still out there... I thought we > fixed all the raid controllers? but yes, it should. They were not, I just questioned if this is solved in some way? Does this mean we always use one size or still switch different sizes but in another place of the code. > I stared at it long and hard, I'm pretty sure it's safe to do, tested it > several ways, and Martin and Nathan concurred... so hopefully this is > not going to break anything. :) If you say so ;) Cross fingers. Seth From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:22:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GLMq532034 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:22:52 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GLMoV32015 for ; Mon, 16 Jul 2001 14:22:50 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id OAA05909 for ; Mon, 16 Jul 2001 14:22:49 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id OAA15656 for ; Mon, 16 Jul 2001 14:27:21 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id B870115A46C for ; Mon, 16 Jul 2001 14:21:33 -0700 (PDT) Subject: Re: LVM on Linux From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <20010716225418.G14564@vestdata.no> References: <85063BBE668FD411944400D0B744267A643419@AUSMAIL> <20010716225418.G14564@vestdata.no> Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/0.10 (Preview Release) Date: 16 Jul 2001 14:21:33 -0700 Message-Id: <995318493.12677.14.camel@stantz.corp.sgi.com> Mime-Version: 1.0 X-MIME-Autoconverted: from 8bit to quoted-printable by sgi.com id OAA05909 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GLMoV32016 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 22:54:18 +0200, Ragnar Kjørstad wrote: > > Even for highend RAID's there are lots of reasons to use LVM/EVMS: > * load balancing across multiple scsi-channels (not implemented yet) > * Dynamic partitioning > * Volumes spanning multiple physical devices > * snapshotting. > > Basicly handling this is software adds a lot of flexibility. But how about performance? Aren't these things supposed to be handled by the hardware? It's the same thing as for soft vs hard RAID. Hard should be faster (but, yeah, soft is easier to play with). -- Florin Andrei From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:29:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GLT8q32291 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:29:08 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GLT6V32271 for ; Mon, 16 Jul 2001 14:29:06 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id OAA01976 for ; Mon, 16 Jul 2001 14:29:04 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2444485; Mon, 16 Jul 2001 16:27:49 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id QAA37247; Mon, 16 Jul 2001 16:27:48 -0500 (CDT) Subject: Re: TAKE - Don't use BLKBSZSET in xfsprogs From: Eric Sandeen To: Seth Mos Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 16 Jul 2001 16:27:50 -0500 Message-Id: <995318870.1437.9.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 23:20:37 +0200, Seth Mos wrote: > On 16 Jul 2001, Eric Sandeen wrote: > > Hm, I didn't know those errors were still out there... I thought we > > fixed all the raid controllers? but yes, it should. > > They were not, I just questioned if this is solved in some way? > Does this mean we always use one size or still switch different sizes but > in another place of the code. The block size is always set correctly at mount time, so everything is fine from then on. The only trouble was in userspace, on a device which had some other blocksize previously, and had not yet been mounted as xfs - i.e. during mkfs.xfs time. So, I guess it's the latter - we switch to the correct size in another place in the code - at mount time, in the kernel - and it's no longer necessary to do it in userspace before this. -Eric From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:56:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GLu9j00310 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:56:09 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GLu6V32759 for ; Mon, 16 Jul 2001 14:56:06 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id XAA04079; Mon, 16 Jul 2001 23:56:04 +0200 Date: Mon, 16 Jul 2001 23:56:03 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Steve Lord Cc: Mike Gigante , Simon Matter , "P.Dixon" , linux-xfs@oss.sgi.com Subject: Re: benchmarks Message-ID: <20010716235603.J14564@vestdata.no> References: <200107162111.f6GLBPQ24732@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200107162111.f6GLBPQ24732@jen.americas.sgi.com>; from Steve Lord on Mon, Jul 16, 2001 at 04:11:25PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 16, 2001 at 04:11:25PM -0500, Steve Lord wrote: > > > The mongo benchmarks use relatively small files. XFS scales very well to > > > large files/directories, but that benchmark sticks to small scale stuff. > > > It *seems* to show ReiserFS in the best possible light and the XFS results > > > don't seem to reflect anything like real world experience (except that it > > > correctly highlights the relatively slow delete performance of XFS!) > > > > I partly disagree. mongo tests filesystem performace - benchmarks that > > test writing really big files is mostly testing your hardware. The > > filesystem still matters, but not so much as on small files. I think > > the difference between ext2/xfs/reiserfs is less than 10%. (ext3 with > > datalogging may be a different story though). > > mongo tests how the filesystem behaves under the endcase of continuous > metadata load from an application which is doing nothing with the data > except reading it and writing it. It is a rare application which behaves > in this way, but it is a very common benchmark, the filesystem is there > to provide service to applications, not to consume all the resources > of the machine. Yes, and reiserfs is more cpu-intensive than other filesystems, so benchmarks (wich are generally not very cpu-intensive) may indicate better performance on reiserfs than what is the case for real applications (wich may or may not be cpu-intesive). > Note that I am not arguing for one filesystem or another, just commenting > on the nature of filesystem benchmarks, reiserfs is good for some things, > XFS is good for others. No argument there. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 14:58:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GLw5u00471 for linux-xfs-outgoing; Mon, 16 Jul 2001 14:58:05 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GLw2V00452 for ; Mon, 16 Jul 2001 14:58:03 -0700 Received: (qmail 1669 invoked from network); 16 Jul 2001 21:57:56 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 16 Jul 2001 21:57:56 -0000 Message-ID: <3B536352.210A970E@namesys.com> Date: Tue, 17 Jul 2001 01:57:38 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Xuan Baldauf CC: Nikita Danilov , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Xuan Baldauf wrote: > P.S.: Hans, how do you prevent object_id|inode reusing? Using mount_id+generation counter per mount? I don't think we considered your approach. I wonder if it would work better than what we use? Comments Chris and Nikita? From owner-linux-xfs@oss.sgi.com Mon Jul 16 15:01:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GM1dl00716 for linux-xfs-outgoing; Mon, 16 Jul 2001 15:01:39 -0700 Received: from router.abc (p3EE0E524.dip.t-dialin.net [62.224.229.36]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GM1ZV00697 for ; Mon, 16 Jul 2001 15:01:36 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6GM0Vo00452; Tue, 17 Jul 2001 00:00:31 +0200 Message-ID: <3B5363FE.3A7D892F@baldauf.org> Date: Tue, 17 Jul 2001 00:00:30 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Ragnar =?iso-8859-1?Q?Kj=F8rstad?= CC: Nikita Danilov , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <3B534B74.BDE19961@baldauf.org> <20010716223240.D14564@vestdata.no> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GM1bV00698 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ragnar Kjørstad wrote: > > > For each open file you have: > > > > > > struct file (96b) > > > struct inode (460b) > > > struct dentry (112b) > > > > > > at least. This totals to 668M of kernel memory, that is, unpageable. > > > > As I said below, the NFS server should be a user-space daemon.. > > But the datastructures mentioned above would still be kernel-memory, so > that will not solve the problem. Actually, you are right. :-( But once there is a filesystem change notification API, a userspace NFS server application could create a "catch-all" notification rule which says that it should be informed about every change within the whole VFS, including deletion of objects (like a file or a filename). All the tracking and NFS client notification then becomes a swappable user space problem. If Nikita does not like 1M open files by filedescriptor on a server due to memory scalability reasons, maybe he does like 1M accessible files by object_id|inode. Then the server issues virtual NFS filehandles to clients and stores internally which inode number maps to which virtual NFS filehandles. For every file deleted, the NFS server checks which clients to notify using the network. If this is not possible, then it is a disconnected-operation-problem. Or let it say the other way around: an inode number is a "ticket for accessing a specified file on the server, issued by the server". This inode number is state. (The same applies to directory cookies). Just because currently the ticket cannot be invalidated by the server, it does not loose its property to be state, it only is state which is never released. Because the more files are opened by NFS on the server, the more state is given to the client. Because the state is not released (the server has to accept requests to files whose inode numbers have been sent some reboots before), NFS imposes the nfs server to have a memory leak by design - or to be broken in another way by design (like risking to refer a different file by the same object_id; requiring the server to have unique object_ids over indefinite space and time while object_ids are limited; requiring the server to use only a limited amount directory cookies over indefinite space and time, thus requiring reiserfs to be unneccessarily inefficient for directories (yet it is more efficient than many other filesystems)). Xuân. From owner-linux-xfs@oss.sgi.com Mon Jul 16 15:04:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GM48p00920 for linux-xfs-outgoing; Mon, 16 Jul 2001 15:04:08 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GM44V00901 for ; Mon, 16 Jul 2001 15:04:05 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id AAA04600; Tue, 17 Jul 2001 00:04:00 +0200 Date: Tue, 17 Jul 2001 00:03:59 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Florin Andrei Cc: linux-xfs@oss.sgi.com Subject: Re: LVM on Linux Message-ID: <20010717000359.K14564@vestdata.no> References: <85063BBE668FD411944400D0B744267A643419@AUSMAIL> <20010716225418.G14564@vestdata.no> <995318493.12677.14.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.95.5i In-Reply-To: <995318493.12677.14.camel@stantz.corp.sgi.com>; from Florin Andrei on Mon, Jul 16, 2001 at 02:21:33PM -0700 X-MIME-Autoconverted: from 8bit to quoted-printable by stine.vestdata.no id AAA04600 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GM46V00902 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 16, 2001 at 02:21:33PM -0700, Florin Andrei wrote: > On 16 Jul 2001 22:54:18 +0200, Ragnar Kjørstad wrote: > > > > Even for highend RAID's there are lots of reasons to use LVM/EVMS: > > * load balancing across multiple scsi-channels (not implemented yet) > > * Dynamic partitioning > > * Volumes spanning multiple physical devices > > * snapshotting. > > > > Basicly handling this is software adds a lot of flexibility. > > But how about performance? > Aren't these things supposed to be handled by the hardware? > It's the same thing as for soft vs hard RAID. Hard should be faster > (but, yeah, soft is easier to play with). There is a performance penalty, but if you're using LVM just for partitioning it's very small. (I believe ca 4% if you're using large extents). I'd assume the penalty for doing striping is approxemately the same, but haven't tested it. Basicly striping is a technology that give you better benchmarks results but often doesn't improve real-life performance. (because benchmarks are often a single process writing to a single file while real-life is multiple users writing to multiple files - so your load is distributed over the different devices anyway) For mirroring and even more so for raid5, it's a different story. If you want high performance, you don't want to do mirroring/raid5 in software. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 16 15:17:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GMHK101371 for linux-xfs-outgoing; Mon, 16 Jul 2001 15:17:20 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GMHJV01352 for ; Mon, 16 Jul 2001 15:17:19 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA00665 for ; Mon, 16 Jul 2001 15:14:49 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2446816; Mon, 16 Jul 2001 17:16:01 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA81012; Mon, 16 Jul 2001 17:16:00 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6GMHIg25515; Mon, 16 Jul 2001 17:17:18 -0500 Message-Id: <200107162217.f6GMHIg25515@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: vkuznet@fnal.gov cc: linux-xfs@oss.sgi.com Subject: Re: XFS performance In-Reply-To: Message from of "Mon, 16 Jul 2001 12:23:08 CDT." Date: Mon, 16 Jul 2001 17:17:18 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > I'm got XFS working on my Linux workstation (dual PIII 550Mhz, > 512Mb RAM). The only things I've noticed that my applications > compiled by a factor of 2 slower compared to ext2. It is quite > large set of libraries (around 300) and problem seems to be > at linkage stage. My questions are the following: > 1) which parameters will allow to tune XFS performance > 2) is it possible to mount XFS with another parameters (such > as logsize) compare to ones used during formatting (I've used default). How are you building your libraries, how much is usually running at once in terms of compilers and linkers. Also, which version of the code are you running? Thanks Steve > > Thank you, > Valentine. > > ************************************************************* > * Valentine Kouznetsov phone : (630) 840 2192 * > * Fermilab MS352 fax : (630) 840 8886 * > * P.O.Box 500 e-mail: vkuznet@fnal.gov * > * Batavia IL, 60510 http://www-d0.fnal.gov/~vkuznet * > ************************************************************* From owner-linux-xfs@oss.sgi.com Mon Jul 16 15:23:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GMN5X01566 for linux-xfs-outgoing; Mon, 16 Jul 2001 15:23:05 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GMN3V01547 for ; Mon, 16 Jul 2001 15:23:03 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ4BW>; Mon, 16 Jul 2001 17:22:29 -0500 Message-ID: <85063BBE668FD411944400D0B744267A64341E@AUSMAIL> From: "Gonyou, Austin" To: =?iso-8859-1?Q?=27Ragnar_Kj=F8rstad=27?= , "Gonyou, Austin" Cc: "'Ric Tibbetts'" , Linux XFS Mailing List , JFS Discussion List Subject: RE: LVM on Linux Date: Mon, 16 Jul 2001 17:22:28 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GMN3V01548 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Well, Here's something that I'm trying to get at, regardless if you go with EVMS or LVM, either one will offer you all of the things which you listed. (Not all are finished, on both parties, but they are planned) -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Ragnar Kjørstad [mailto:xfs@ragnark.vestdata.no] > Sent: Monday, July 16, 2001 3:54 PM > To: Gonyou, Austin > Cc: 'Ric Tibbetts'; Linux XFS Mailing List; JFS Discussion List > Subject: Re: LVM on Linux > > Even for highend RAID's there are lots of reasons to use LVM/EVMS: > * load balancing across multiple scsi-channels (not implemented yet) > * Dynamic partitioning > * Volumes spanning multiple physical devices > * snapshotting. > > Basicly handling this is software adds a lot of flexibility. > > > > -- > Ragnar Kjorstad > Big Storage > From owner-linux-xfs@oss.sgi.com Mon Jul 16 15:33:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GMXL802079 for linux-xfs-outgoing; Mon, 16 Jul 2001 15:33:21 -0700 Received: from ivanova.coker.com.au (postfix@ivanova.coker.com.au [203.36.46.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GMWVV02019 for ; Mon, 16 Jul 2001 15:32:33 -0700 Received: from lyta.coker.com.au (ivanova [127.0.0.1]) by ivanova.coker.com.au (Postfix) with ESMTP id 55D9BFB53; Tue, 17 Jul 2001 08:30:26 +1000 (EST) Received: from there (lyta [127.0.0.1]) by lyta.coker.com.au (Postfix) with SMTP id A9A225F70; Tue, 17 Jul 2001 00:29:27 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" From: Russell Coker Reply-To: Russell Coker To: Nikita Danilov , Xuan Baldauf Subject: Re: [reiserfs-list] Re: benchmarks Date: Tue, 17 Jul 2001 00:29:27 +0200 X-Mailer: KMail [version 1.2.9] Cc: Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com References: <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> In-Reply-To: <15187.18225.196286.123754@beta.namesys.com> MIME-Version: 1.0 Message-Id: <20010716222927.A9A225F70@lyta.coker.com.au> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6GMXKV02060 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 16 Jul 2001 21:57, Nikita Danilov wrote: > > > If you have 10000 clients each opening 100 files you got 1e6 opened > > > files on the server---it wouldn't work. NFS was designed to be > > > stateless to be scalable. > > > > Every existing file has at least one name (or is member of the hidden > > to-be-deleted-directory, and so has a name, too), and an object_id. > > Suppose the object_id is 32 bytes long. A virtual filedescriptor may be > > 4 bytes long, some housekeeping metadata 28 bytes, so we will have 64MB > > occupied in you scenario. Where's the problem? 80% of those 64MB can be > > swapped out. > > For each open file you have: > > struct file (96b) > struct inode (460b) > struct dentry (112b) > > at least. This totals to 668M of kernel memory, that is, unpageable. > All files are kept in several hash tables and hash-tables are known to > degrade. Well, actually, I am afraid current Linux kernels cannot open > 1e6 of files. Last time I tested this one process could only open slightly more than 80,000 files (I am not about to test this at the moment as doing so allocates a lot of kernel memory that can't be swapped and therefore requires a reboot to regain good performance). I am not sure why the limit is around 80K files, but I suspect that if I had more RAM the limit would be higher. 80K files takes 80M of unswappable RAM if the hash tables you refer to take 356 bytes per file. 80M of unswappable RAM is not a crushing burden on my Thinkpad which has 256M of RAM. On a large server machine 80M is no big deal at all. However most large servers will be killed by having even 10K files open and active at one time. I doubt that there exists a situation where the server has such a large amount of disk capacity that it can handle 100K files (how big would that be, 100 spindles? more?), yet it has such a small amount of RAM (by server standards) that it can't handle the file structures. When you have server machines with 8G of RAM if the kernel memory is the issue then you should be able to have 2M or 3M files open... -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page From owner-linux-xfs@oss.sgi.com Mon Jul 16 16:11:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GNBSg02587 for linux-xfs-outgoing; Mon, 16 Jul 2001 16:11:28 -0700 Received: from vertigo.incyte.com (master.incyte.com [198.31.37.253]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GNBQV02568 for ; Mon, 16 Jul 2001 16:11:26 -0700 Received: from vertigo.incyte.com (wfrancis@localhost) by vertigo.incyte.com (8.11.0/8.11.0) with ESMTP id f6GNBKT21957 for ; Mon, 16 Jul 2001 16:11:20 -0700 Message-Id: <200107162311.f6GNBKT21957@vertigo.incyte.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-xfs@oss.sgi.com From: Will Francis Subject: problems formatting partition via ks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 16 Jul 2001 16:11:20 -0700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hey listers. I've taken XFS 1.0.1 (the iso image) and placed it over an otherwise stock RH 7.1 directory tree. I'm doing a kickstart install from it, and have a bit of a problem. My kickstart file describes my partitions thusly: part / --size 350 --onprimary=1 part swap --size 256 part /usr --size 1000 part /usr/local/net --size 1000 --grow part /kickstart --size 2000 when making /usr/local/net, it fails with these errors: on F1 Error mounting device hda6 as /usr/local/net: Invalid argument on F4 XFS bad magic number XFS SB validate failed on F5 Illegal value /usr/local/net for -L option (then the usage statement for mkfs.xfs follows) It threw similar fits when I tried to put /boot on it's own partition so I've just put it back into / thoughts? Will From owner-linux-xfs@oss.sgi.com Mon Jul 16 16:15:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GNFPf02739 for linux-xfs-outgoing; Mon, 16 Jul 2001 16:15:25 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GNFNV02720 for ; Mon, 16 Jul 2001 16:15:23 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ4GX>; Mon, 16 Jul 2001 18:14:44 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643421@AUSMAIL> From: "Gonyou, Austin" To: "'Florin Andrei'" , linux-xfs@oss.sgi.com Subject: RE: LVM on Linux Date: Mon, 16 Jul 2001 18:14:43 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'd like to answer a couple of these things. > > * load balancing across multiple scsi-channels (not implemented yet) This is almost always at the driver level on the host. Since LVM is a sort of Driver, much like MD/RD, then it would be as though MD/RD had that kind of ability. Also, think of this like EMC's PowerPath(r). It will allow overloading a single scsi channel, and overflow goes to a secondary channel to ballance the bandwidth. > > * Dynamic partitioning This is something which can be done on the hardware side, but only at the disk level. Partitioning is still an OS level function, LVM/EVMS allows for this and other things too. Hardwar can do this if it is meant to, but that is expensive. LVM/EVMS is not. > > * Volumes spanning multiple physical devices Think of something like an EMC frame, where you've got 200 PVs. What do you do with them? You could MD, or RD, but LVM is much easier and closer to a Veritas type volume management. Nothing new here. > > * snapshotting. It may feel like hardware, but ist still software, even if a dedicated box is snapshotting for you. Moving the intelligence out of some storage box allows you to go cheaper on that storage if the host is performing that function instead. You do incurr increased costs however when you find that you don't have enough bandwidth to snapshot + do your business at the same time. More HBAs relieves this bottleneck. > > But how about performance? > Aren't these things supposed to be handled by the hardware? > It's the same thing as for soft vs hard RAID. Hard should be faster > (but, yeah, soft is easier to play with). > > -- > Florin Andrei > -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Mon Jul 16 16:22:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6GNMw102927 for linux-xfs-outgoing; Mon, 16 Jul 2001 16:22:58 -0700 Received: from weta.f00f.org (weta.f00f.org [203.167.249.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6GNMuV02908 for ; Mon, 16 Jul 2001 16:22:56 -0700 Received: by weta.f00f.org (Postfix, from userid 1000) id C651C2A25; Tue, 17 Jul 2001 11:23:00 +1200 (NZST) Date: Tue, 17 Jul 2001 11:23:00 +1200 From: Chris Wedgwood To: Russell Coker Cc: Nikita Danilov , Xuan Baldauf , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010717112300.A13374@weta.f00f.org> References: <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <20010716222927.A9A225F70@lyta.coker.com.au> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="lEGEL1/lMxI0MVQ2" Content-Disposition: inline In-Reply-To: <20010716222927.A9A225F70@lyta.coker.com.au> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --lEGEL1/lMxI0MVQ2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 17, 2001 at 12:29:27AM +0200, Russell Coker wrote: Last time I tested this one process could only open slightly more than 80,000 files (I am not about to test this at the moment as doing so allocates a lot of kernel memory that can't be swapped and therefore requires a reboot to regain good performance). FWIW, I am able to open 1e6 files without any effort whatsoever. Code attached (just wrote this now). You need to up /proc/sys/fs/file-max and your ulimit obiously. --cw --lEGEL1/lMxI0MVQ2 Content-Type: text/x-csrc; charset=us-ascii Content-Disposition: attachment; filename="open-me.c" #include #include #include #include #include int main() { int i; for(i=0;i < 1000*1000;++i){ if(-1 == open("/dev/null",O_RDONLY)){ break; } if(!(i & ~1023)) printf("%d\n", i); } printf("total opens %d\n", i); return 0; } --lEGEL1/lMxI0MVQ2-- From owner-linux-xfs@oss.sgi.com Mon Jul 16 17:07:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H07kD03595 for linux-xfs-outgoing; Mon, 16 Jul 2001 17:07:46 -0700 Received: from router.abc (p3EE0E379.dip.t-dialin.net [62.224.227.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H07gV03574 for ; Mon, 16 Jul 2001 17:07:43 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6H073o02044; Tue, 17 Jul 2001 02:07:03 +0200 Message-ID: <3B5381A5.365A8006@baldauf.org> Date: Tue, 17 Jul 2001 02:07:02 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Chris Wedgwood CC: Russell Coker , Nikita Danilov , Xuan Baldauf , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <20010716222927.A9A225F70@lyta.coker.com.au> <20010717112300.A13374@weta.f00f.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6H07iV03575 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Chris Wedgwood wrote: > On Tue, Jul 17, 2001 at 12:29:27AM +0200, Russell Coker wrote: > > Last time I tested this one process could only open slightly more > than 80,000 files (I am not about to test this at the moment as > doing so allocates a lot of kernel memory that can't be swapped > and therefore requires a reboot to regain good performance). > > FWIW, I am able to open 1e6 files without any effort whatsoever. Code > attached (just wrote this now). > > You need to up /proc/sys/fs/file-max and your ulimit obiously. > > --cw > > ------------------------------------------------------------ > > open-me.cName: open-me.c > Type: C source code (text/c) Maybe you're creating only one dentry-, inode-, whatever-in-kernel-object for one file. So you're maybe just increasing refcounters, not the amount of objects. What about creating 1M files and then opening all different files? Xuân. From owner-linux-xfs@oss.sgi.com Mon Jul 16 17:09:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H09Fv03709 for linux-xfs-outgoing; Mon, 16 Jul 2001 17:09:15 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H09DV03690 for ; Mon, 16 Jul 2001 17:09:13 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id CAA325453 for ; Tue, 17 Jul 2001 02:09:08 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA37403 for linux-xfs@oss.sgi.com; Tue, 17 Jul 2001 10:07:51 +1000 (EST) Date: Tue, 17 Jul 2001 10:07:51 +1000 (EST) From: Nathan Scott Message-Id: <200107170007.KAA37403@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - Don't use BLKBSZSET (really) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Mon Jul 16 17:05:37 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:98981a cmd/xfsprogs/libxfs/Makefile - 1.8 - Oops - sorry Eric - my Makefile conditional didn't match up with the way it was used in the code. This really switches off BLKSZSET now. cmd/xfsprogs/doc/CHANGES - 1.25 - refine the note re BLKSZSET change a little now it defaults to off. From owner-linux-xfs@oss.sgi.com Mon Jul 16 17:18:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H0I1d03963 for linux-xfs-outgoing; Mon, 16 Jul 2001 17:18:01 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H0HxV03944 for ; Mon, 16 Jul 2001 17:17:59 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id RAA09489 for ; Mon, 16 Jul 2001 17:15:30 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 KAA28133; Tue, 17 Jul 2001 10:16:41 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA12384; Tue, 17 Jul 2001 10:16:40 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107171016.ZM94725@wobbly.melbourne.sgi.com> Date: Tue, 17 Jul 2001 10:16:38 +1000 In-Reply-To: Will Francis "problems formatting partition via ks" (Jul 16, 4:11pm) References: <200107162311.f6GNBKT21957@vertigo.incyte.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Will Francis , linux-xfs@oss.sgi.com Subject: Re: problems formatting partition via ks Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Will, On Jul 16, 4:11pm, Will Francis wrote: > Subject: problems formatting partition via ks > ... > Illegal value /usr/local/net for -L option > (then the usage statement for mkfs.xfs follows) > > It threw similar fits when I tried to put /boot on it's > own partition so I've just put it back into / > > thoughts? > Yes - there is only space for 12 characters in the XFS fs label field, so the mkfs.xfs error you received above is correct (looks like you tried 14 - "/usr/local/net"). The /boot problem sounds like it might be different though? (need more details). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 16 17:49:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H0nMS04302 for linux-xfs-outgoing; Mon, 16 Jul 2001 17:49:22 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H0nIV04283 for ; Mon, 16 Jul 2001 17:49:18 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id CAA327745 for ; Tue, 17 Jul 2001 02:49:14 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA30998; Tue, 17 Jul 2001 10:47:46 +1000 (EST) Date: Tue, 17 Jul 2001 10:47:46 +1000 From: Timothy Shimmin To: ThH Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump on alpha Message-ID: <20010717104745.I11622@boing.melbourne.sgi.com> References: <995262801.828.0.camel@lx1.thhmaus.de> <10107161617.ZM208491@wobbly.melbourne.sgi.com> <995271702.989.0.camel@lx2.thhmaus.de> <10107161827.ZM215737@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <10107161827.ZM215737@wobbly.melbourne.sgi.com>; from nathans@wobbly.melbourne.sgi.com on Mon, Jul 16, 2001 at 06:27:48PM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 16, 2001 at 06:27:48PM +1000, Nathan Scott wrote: > > On Jul 16, 10:21am, ThH wrote: > > Subject: Re: xfsdump on alpha > > ... > > You say it's an incompatibility of the dump data structure and the alpha > > system headers. What's with other 64bit systems like IA64, sparc64 or > > mips64, they might have the same problem. I'm right? > > Yes, you're right - they almost certainly will have this > problem too. > On IRIX though, we currently only build xfsdump/xfsrestore N32 and not 64 bit. (Also on IRIX, time_t is defined as 32 bit for mips 32 and 64.) > > > > I will use xfsdump. Can you tell me what I've to do, too solve this > > problem? > > > > You'll need to audit all uses of time_t in xfsdump tools > - if any of these are in data structures which are to be > written on the tape, then you will need to make up a new > type (eg. time32_t) and then change the code to use that > instead of time_t, ensuring all the places where a 8byte > time_t are needed (eg. libc entry points, syscalls, etc) > still use that, but a conversion to a 32bit version must > be done subsequently before the data structure is written > anywhere permanently. > > At the same time, you'll need to ensure that the code for > 32 bit platforms is effectively unchanged - eg. time32_t > could equate to time_t on those platforms, thru use of cpp > macros, etc. > > hope this helps. There, of course, _could_ be other types with a similar fate to time_t. You need to ensure that the dump format (on tape or on file) remains unchanged to the 32 bit version (if you want compatibility). --Tim From owner-linux-xfs@oss.sgi.com Mon Jul 16 17:56:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H0uEN04484 for linux-xfs-outgoing; Mon, 16 Jul 2001 17:56:14 -0700 Received: from weta.f00f.org (weta.f00f.org [203.167.249.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H0uBV04465 for ; Mon, 16 Jul 2001 17:56:11 -0700 Received: by weta.f00f.org (Postfix, from userid 1000) id E82942A8E; Tue, 17 Jul 2001 12:56:15 +1200 (NZST) Date: Tue, 17 Jul 2001 12:56:15 +1200 From: Chris Wedgwood To: Xuan Baldauf Cc: Russell Coker , Nikita Danilov , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <20010717125615.A13573@weta.f00f.org> References: <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <20010716222927.A9A225F70@lyta.coker.com.au> <20010717112300.A13374@weta.f00f.org> <3B5381A5.365A8006@baldauf.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="VS++wcV0S1rZb1Fb" Content-Disposition: inline In-Reply-To: <3B5381A5.365A8006@baldauf.org> User-Agent: Mutt/1.3.18i X-No-Archive: Yes Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jul 17, 2001 at 02:07:02AM +0200, Xuan Baldauf wrote: Maybe you're creating only one dentry-, inode-, whatever-in-kernel-object for one file. So you're maybe just increasing refcounters, not the amount of objects. What about creating 1M files and then opening all different files? Ah, of course. The attached code really does create and hold open the files. I don't get to 1e6 though, in fact the system got sluggish so I stopped it after 624,596 files were created. Use with caution, if it eats you disk... don't blame me :) --cw --VS++wcV0S1rZb1Fb Content-Type: text/x-csrc; charset=us-ascii Content-Disposition: attachment; filename="create-me.c" /* create lots of file, into hashed directories to rm won't fail when I try to delete them! */ #include #include #include #include #include #include /* make dir structure */ void mkdirs() { int i, j; char path[128]; for(i=0;i<256;++i){ sprintf(path, "test/%02x", i); if(-1 == mkdir(path, 0755)){ if(errno == EEXIST) return; perror("mkdir"); exit(1); } for(j=0;j<256;++j){ sprintf(path, "test/%02x/%02x", i, j); if(-1 == mkdir(path, 0755)) break; } } } int main() { int i; char path[128]; mkdirs(); for(i=0;i < 1000*1000;++i){ sprintf(path, "test/%02x/%02x/%02x", i >> 16, (i >> 8) & 255, i & 255); if(!(i & 1023)) printf("%s\n", path); if(-1 == open(path, O_CREAT|O_RDONLY, 0644)) break; } printf("total opens %d\n", i); return 0; } --VS++wcV0S1rZb1Fb-- From owner-linux-xfs@oss.sgi.com Mon Jul 16 18:56:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H1uM105791 for linux-xfs-outgoing; Mon, 16 Jul 2001 18:56:22 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H1uIV05772 for ; Mon, 16 Jul 2001 18:56:18 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id DAA330943 for ; Tue, 17 Jul 2001 03:56:09 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 LAA28895; Tue, 17 Jul 2001 11:54:53 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA16991; Tue, 17 Jul 2001 11:54:52 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107171154.ZM193508@wobbly.melbourne.sgi.com> Date: Tue, 17 Jul 2001 11:54:51 +1000 In-Reply-To: Steve Lord "Re: fine-tuning XFS" (Jul 16, 2:06pm) References: <200107161906.f6GJ6rt19078@jen.americas.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Steve Lord , Florin Andrei Subject: Re: fine-tuning XFS Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 16, 2:06pm, Steve Lord wrote: > Subject: Re: fine-tuning XFS > ... > If you run this script then it will produce a couple of pages of statistics, > there is a section called Log Operations near the end of the first column, if > xs_log_noiclogs is incrementing rapidly then the logbufs option will help. > > If you install pcp (and being internal to sgi you can get access to the > graphical interface to this) you can look at these numbers in realtime. > It would be interesting to see the rate at which the Directory Operations > statistics move, these are where lookup, create and remove show up. > > In the Tail-Pushing Stats at the top of the second column the xs_sleep_logspace > counter going up says that you are driving the log fairly hard and may benefit > from a bigger log. > Just to add a few more points here (shameless PCP plug ;) ... With the open source bits you're still able to view the stats in realtime using the PCP tools like pmval, pmie and co., eg. [ print out the rate of change of xs_noiclogs every 3secs: ] # /usr/bin/pmval -t 3seconds xfs.log.noiclogs metric: xfs.log.noiclogs host: localhost semantics: cumulative counter (converting to rate) units: count (converting to count / sec) samples: all interval: 3.00 sec 0.0 0.0 0.0 [ ... etc, etc. Or, more interesting... ] # cat xfs.conf no_incore_logs = xfs.log.noiclogs :troppo; sleep_logspace = xfs.log_tail.sleep_logspace :troppo; hosts = ":troppo :soggy"; some_host ( xfs.log.noiclogs $hosts > 50 count/sec ) -> print " XFS log on host %h is on fire!"; some_host ( xfs.write_bytes $hosts > 500000 bytes/sec ) -> print "XFS doin' lots of writes (%v bytes/sec on %h)"; # /usr/bin/pmie -v -t 2sec < xfs.conf no_incore_logs: ? sleep_logspace: ? expr_1: ? expr_2: ? no_incore_logs: 0 sleep_logspace: 0 expr_1: false expr_2: false Tue Jul 17 11:39:24 2001: XFS doin' lots of writes (11564156 bytes/sec on troppo) no_incore_logs: 0 sleep_logspace: 0 expr_1: false expr_2: true [...etc, etc... most useful run as a daemon, writing to syslog]. Also useful for watching memory activity, eg. /proc/slabinfo: # pmval -i xfs_inode,xfs_buf_item mem.slabinfo.objects.active metric: mem.slabinfo.objects.active host: localhost semantics: instantaneous value units: none samples: all interval: 1.00 sec xfs_buf_item xfs_inode 0 3855 0 3855 0 3857 [...etc, etc...] And there is an open source GUI project out there (at http://k332.feld.cvut.cz/~lemming/projects/pcpmon.html); or SGI customers can get hold of the PCP GUI pieces. So, in summary, use PCP => fun for the whole family. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 16 19:09:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H29QD06132 for linux-xfs-outgoing; Mon, 16 Jul 2001 19:09:26 -0700 Received: from horus.its.uow.edu.au (horus.its.uow.edu.au [130.130.68.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H29NV06110 for ; Mon, 16 Jul 2001 19:09:23 -0700 Received: from uow.edu.au (wumpus.its.uow.edu.au [130.130.68.12]) by horus.its.uow.edu.au (8.9.3/8.9.3) with ESMTP id MAA14360; Tue, 17 Jul 2001 12:04:47 +1000 (EST) Message-ID: <3B539DA3.C773F59@uow.edu.au> Date: Tue, 17 Jul 2001 12:06:27 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Juri Haberland CC: linux-xfs@oss.sgi.com Subject: Re: xfs on notebooks (noflushd etc.) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Juri Haberland wrote: > > thomas graichen wrote: > > just out of curiousity: how does xfs interact with things like > > noflushd which reduce the disk flushing for more effective ide > > poweroff possibilities ... is the flushing below the fs layer > > so that it should all work transparently or may it result in > > problems with xfs (or journaling fs in general)? > > Hi Thomas, > > well, I cannot speak for xfs but with ext3 the disk will only spin > down once; after this it will be constantly restarted by the update > mechanisms of ext3 (commit interval is 5 seconds). ext3's commit only runs if there is dirty data to be committed. Running ext3 with a kupdate interval of 15 minutes lets the disks spin down nicely. From owner-linux-xfs@oss.sgi.com Mon Jul 16 22:33:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H5XnB09037 for linux-xfs-outgoing; Mon, 16 Jul 2001 22:33:49 -0700 Received: from exocore.com ([202.4.185.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H5XjV09017 for ; Mon, 16 Jul 2001 22:33:45 -0700 Received: (from shanu@localhost) by exocore.com (8.11.2/8.8.7) id f6H5Xaf05360 for linux-xfs@oss.sgi.com; Tue, 17 Jul 2001 11:03:36 +0530 Date: Tue, 17 Jul 2001 11:03:35 +0530 From: Shanker Balan To: Linux-XFS Subject: Eeeps, i deleted off the XFS ISO! Message-ID: <20010717110335.B3811@exocore.com> Reply-To: Shanker Balan Mail-Followup-To: Linux-XFS Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organisation: Exocore Consulting (P) Ltd Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello: I mistakenly deleted the 1.0.1 installer ISO instead of the 1.0 installer ISO! Is undelete possible? The FAQ does not mention anything on undeletion. Any help appreciated! -- Shanu -- ------------------------------------------( Shanu )----- Shanker Balan http://people.exocore.com/shanu God is silent. Now if we can only get Man to shut up. From owner-linux-xfs@oss.sgi.com Mon Jul 16 23:38:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H6c7O09945 for linux-xfs-outgoing; Mon, 16 Jul 2001 23:38:07 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H6c5V09926 for ; Mon, 16 Jul 2001 23:38:05 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA21081; Tue, 17 Jul 2001 08:37:56 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA21274; Tue, 17 Jul 2001 08:37:56 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id AF0AB57306; Tue, 17 Jul 2001 08:47:05 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id D1EC825835; Tue, 17 Jul 2001 08:54:59 +0200 (CEST) Message-ID: <3B53DD2C.4D6904F9@ch.sauter-bc.com> Date: Tue, 17 Jul 2001 08:37:32 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Florin Andrei Cc: linux-xfs@oss.sgi.com Subject: Re: LVM on Linux References: <85063BBE668FD411944400D0B744267A643419@AUSMAIL> <20010716225418.G14564@vestdata.no> <995318493.12677.14.camel@stantz.corp.sgi.com> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by relay.xlink.net id IAA21081 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6H6c5V09927 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei schrieb: > > On 16 Jul 2001 22:54:18 +0200, Ragnar Kjørstad wrote: > > > > Even for highend RAID's there are lots of reasons to use LVM/EVMS: > > * load balancing across multiple scsi-channels (not implemented yet) > > * Dynamic partitioning > > * Volumes spanning multiple physical devices > > * snapshotting. > > > > Basicly handling this is software adds a lot of flexibility. > > But how about performance? > Aren't these things supposed to be handled by the hardware? > It's the same thing as for soft vs hard RAID. Hard should be faster I have never seen a true hardware RAID. I mean every RAID I saw was having its own CPU (be it i960 or any newer generation of microprocessor or microcontroller from different vendors) and small operating system (firmware). So in fact it's always software but not running on you main CPU. However mainstream CPU's became powerful and very cheap so it's not a bad idea to let this CPU work for your RAID funtionality. In fact software RAID on modern CPU's has exiting performance. > (but, yeah, soft is easier to play with). Another good reason to use the really soft version. > > -- > Florin Andrei From owner-linux-xfs@oss.sgi.com Tue Jul 17 00:42:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H7g3k11560 for linux-xfs-outgoing; Tue, 17 Jul 2001 00:42:03 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H7g1V11540 for ; Tue, 17 Jul 2001 00:42:01 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip31.idcomm.com [209.60.72.158]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6H7joa11340 for ; Tue, 17 Jul 2001 01:45:50 -0600 Message-ID: <3B53ECD9.F7E204D4@idcomm.com> Date: Tue, 17 Jul 2001 01:44:25 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: Linux-XFS Subject: Re: Eeeps, i deleted off the XFS ISO! References: <20010717110335.B3811@exocore.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Shanker Balan wrote: > > Hello: > > I mistakenly deleted the 1.0.1 installer ISO instead of the 1.0 > installer ISO! Is undelete possible? The FAQ does not mention anything > on undeletion. > > Any help appreciated! I can offer consolation, I recently downloaded an ISO on a 26.4 kbps connection :( D. Stimits, stimits@idcomm.com > > -- Shanu > > -- > ------------------------------------------( Shanu )----- > Shanker Balan http://people.exocore.com/shanu > God is silent. Now if we can only get Man to shut up. From owner-linux-xfs@oss.sgi.com Tue Jul 17 01:03:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H83dO12033 for linux-xfs-outgoing; Tue, 17 Jul 2001 01:03:39 -0700 Received: from otto.cfht.hawaii.edu (otto.colonization.com [128.171.80.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H83bV12014 for ; Tue, 17 Jul 2001 01:03:37 -0700 Received: (from isani@localhost) by otto.cfht.hawaii.edu (8.8.8/8.8.8) id WAA32231; Mon, 16 Jul 2001 22:03:21 -1000 From: Sidik Isani Message-Id: <200107170803.WAA32231@otto.cfht.hawaii.edu> Subject: Re: xfs on notebooks (noflushd etc.) To: lord@sgi.com (Steve Lord) Date: Mon, 16 Jul 2001 22:03:21 -1000 (HST) Cc: tgr@spoiled.org (thomas graichen), linux-xfs@oss.sgi.com In-Reply-To: <200107161415.f6GEFN401346@jen.americas.sgi.com> from "Steve Lord" at Jul 16, 2001 09:15:23 AM X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk | |> just out of curiousity: how does xfs interact with things like |> noflushd which reduce the disk flushing for more effective ide |> poweroff possibilities ... is the flushing below the fs layer |> so that it should all work transparently or may it result in |> problems with xfs (or journaling fs in general)? |> |> a lot of thanks in advance | |I have never tried noflushd, I see the FAQ says that it does not help with |reiserfs because it bypasses normal delayed write mechanisms, xfs does the |same type of thing, so there may be similar problems. Someone will have |to try it and report back. I tried it a while back, but couldn't convince myself that it really helped much, or was safe for XFS. I also managed to get the disk to spin down _without_ noflushd, but there are a lot of things you need to check: - /tmp and /var are ramfs, and /dev is devfs on my system. - I "jumped through the hoops" Steve mentioned to get root mounted with noatime. Without this, it's hopeless to get the disk to spin down. - Check for loop-devices if you're still getting disk spin-up. - I'm using XEmacs with auto-save turned off. - I 'ls -l' and 'cat' a bunch of files > /dev/null on bootup to be sure all basic libraries and programs start out completely cached. - ~/.netscape/history.dat needs to be a symlink to a file on ramdisk if you intend to leave netscrape running. - The list goes on (but gets further off-topic for XFS.) It works with 2.4.6, but somehow the way I'm booting 2.4.5 I was getting disk spin-up again. It's a pain, basically. By the way, I solved my memory stats mystery. I found some info on the kernel list about /proc/slabinfo which indicated that the memory listed here is not included in caches/buffers or any other specific entry in /proc/meminfo. After adding up all the memory in /proc/slabinfo (which is a mess) and subtracting it from "used" memory, "used" memory is back to just process memory. Be seeing you, - Sidik P.S.: I glommed the adjacent partition onto my XFS root partition the other day with fdisk and ran "xfs_growfs /". Pretty easy. Cool stuff! Thanks again. From owner-linux-xfs@oss.sgi.com Tue Jul 17 01:21:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H8LcQ12444 for linux-xfs-outgoing; Tue, 17 Jul 2001 01:21:38 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H8LaV12425 for ; Tue, 17 Jul 2001 01:21:36 -0700 Received: (qmail 26930 invoked from network); 17 Jul 2001 08:21:30 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 17 Jul 2001 08:21:30 -0000 Message-ID: <3B53F575.E3ABB00A@namesys.com> Date: Tue, 17 Jul 2001 12:21:09 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Nikita Danilov CC: Xuan Baldauf , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nikita Danilov wrote: > For each open file you have: > > struct file (96b) > struct inode (460b) > struct dentry (112b) > > at least. This totals to 668M of kernel memory, that is, unpageable. > All files are kept in several hash tables and hash-tables are known to > degrade. Well, actually, I am afraid current Linux kernels cannot open > 1e6 of files. You don't have to do things this stupidly. But even if you do, you have shown that a server that cannot handle the load from a million files receiving IO would be burdened by the overhead of keeping them open. Not sure what your point is. Hans From owner-linux-xfs@oss.sgi.com Tue Jul 17 01:25:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H8PVx12582 for linux-xfs-outgoing; Tue, 17 Jul 2001 01:25:31 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H8PSV12563 for ; Tue, 17 Jul 2001 01:25:28 -0700 Received: (qmail 28157 invoked from network); 17 Jul 2001 08:25:22 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 17 Jul 2001 08:25:22 -0000 Message-ID: <3B53F65D.265034CB@namesys.com> Date: Tue, 17 Jul 2001 12:25:01 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Xuan Baldauf CC: Ragnar =?koi8-r?Q?Kj=F8rstad?= , Nikita Danilov , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <3B534B74.BDE19961@baldauf.org> <20010716223240.D14564@vestdata.no> <3B5363FE.3A7D892F@baldauf.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A file change notification API is an inherently reasonable thing to have, for use by more than just NFS (emacs for instance). Hans Xuan Baldauf wrote: > > Ragnar Kjørstad wrote: > > > > > For each open file you have: > > > > > > > > struct file (96b) > > > > struct inode (460b) > > > > struct dentry (112b) > > > > > > > > at least. This totals to 668M of kernel memory, that is, unpageable. > > > > > > As I said below, the NFS server should be a user-space daemon.. > > > > But the datastructures mentioned above would still be kernel-memory, so > > that will not solve the problem. > > Actually, you are right. :-( > > But once there is a filesystem change notification API, a userspace NFS > server application could create a "catch-all" notification rule which says > that it should be informed about every change within the whole VFS, > including deletion of objects (like a file or a filename). All the tracking > and NFS client notification then becomes a swappable user space problem. > > If Nikita does not like 1M open files by filedescriptor on a server due to > memory scalability reasons, maybe he does like 1M accessible files by > object_id|inode. Then the server issues virtual NFS filehandles to clients > and stores internally which inode number maps to which virtual NFS > filehandles. For every file deleted, the NFS server checks which clients to > notify using the network. If this is not possible, then it is a > disconnected-operation-problem. > > Or let it say the other way around: an inode number is a "ticket for > accessing a specified file on the server, issued by the server". This inode > number is state. (The same applies to directory cookies). Just because > currently the ticket cannot be invalidated by the server, it does not loose > its property to be state, it only is state which is never released. Because > the more files are opened by NFS on the server, the more state is given to > the client. Because the state is not released (the server has to accept > requests to files whose inode numbers have been sent some reboots before), > NFS imposes the nfs server to have a memory leak by design - or to be broken > in another way by design (like risking to refer a different file by the same > object_id; requiring the server to have unique object_ids over indefinite > space and time while object_ids are limited; requiring the server to use > only a limited amount directory cookies over indefinite space and time, thus > requiring reiserfs to be unneccessarily inefficient for directories (yet it > is more efficient than many other filesystems)). > > Xuân. From owner-linux-xfs@oss.sgi.com Tue Jul 17 02:58:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6H9wFw14242 for linux-xfs-outgoing; Tue, 17 Jul 2001 02:58:15 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6H9wDV14220 for ; Tue, 17 Jul 2001 02:58:13 -0700 Received: (qmail 25787 invoked by uid 8); 17 Jul 2001 09:58:11 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: xfs on notebooks (noflushd etc.) Date: Tue, 17 Jul 2001 09:58:11 +0000 (UTC) Organization: spoiled dot org Lines: 31 Distribution: local Message-ID: References: <3B539DA3.C773F59@uow.edu.au> X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andrew Morton wrote: > Juri Haberland wrote: >> >> thomas graichen wrote: >> > just out of curiousity: how does xfs interact with things like >> > noflushd which reduce the disk flushing for more effective ide >> > poweroff possibilities ... is the flushing below the fs layer >> > so that it should all work transparently or may it result in >> > problems with xfs (or journaling fs in general)? >> >> Hi Thomas, >> >> well, I cannot speak for xfs but with ext3 the disk will only spin >> down once; after this it will be constantly restarted by the update >> mechanisms of ext3 (commit interval is 5 seconds). > > ext3's commit only runs if there is dirty data to be committed. Well, on an idle machine I can see disk access every five seconds. This does not happen with ext2. > Running ext3 with a kupdate interval of 15 minutes lets the disks > spin down nicely. Is that safe? Anyway, I will give it a try. Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Tue Jul 17 06:29:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HDT7s19081 for linux-xfs-outgoing; Tue, 17 Jul 2001 06:29:07 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HDT5V19062 for ; Tue, 17 Jul 2001 06:29:06 -0700 Received: from kalapati.leathercollection.local (kalapati.leathercollection.local [192.168.0.2]) by gusi.leathercollection.ph (Postfix) with ESMTP id 804FF300D for ; Tue, 17 Jul 2001 21:29:03 +0800 (PHT) Date: Tue, 17 Jul 2001 21:29:01 +0800 (PHT) From: Federico Sevilla III X-Sender: jijo@kalapati.leathercollection.local To: Linux XFS Mailing List Subject: chacl questions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I wonder what's wrong with the way I'm doing things. I create a directory "test", owned by root, group root, perms u=rwx,g=,o=. I want to allow user "jijo" to access this, too, but to only read it, I try the following: chacl u::rwx,g::,o::,u:jijo:r-x,m::r-x test But it says: chacl: "u::rwx,g::,o::,u:jijo:r-x,m::r-x" is an invalid ACL specification. 'chacl -l test' output: test[] which (I think) verifies that ACLs are enabled and work. What am I doing wrong? Also, is it possible to just add an ACL? Let's say I already have ACLs set up, and just want to enable someone else to read and access this file, how do I do this? Do I have to list everyone else? Or if I want to revoke access from someone? It's my first time to handle ACLs. I hope you guys can be patient with this newbie. :) :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Tue Jul 17 06:34:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HDYd519259 for linux-xfs-outgoing; Tue, 17 Jul 2001 06:34:39 -0700 Received: from d0lxucr02.fnal.gov (IDENT:root@d0lxucr02.fnal.gov [131.225.221.43]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HDYbV19239 for ; Tue, 17 Jul 2001 06:34:37 -0700 Received: from localhost (vkuznet@localhost) by d0lxucr02.fnal.gov (8.9.3/8.9.3) with ESMTP id JAA12484; Tue, 17 Jul 2001 09:34:32 -0400 X-Authentication-Warning: d0lxucr02.fnal.gov: vkuznet owned process doing -bs Date: Tue, 17 Jul 2001 08:34:32 -0500 (CDT) From: To: Steve Lord cc: linux-xfs@oss.sgi.com Subject: Re: XFS performance In-Reply-To: <200107162217.f6GMHIg25515@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Steve, I need to appology for my first mail since the problem appears to be at the level of compiler flags. It was coinsedence that I setup XFS at those time when new release of software I used arrive with optimization turned on. Fixing that problem I don't see any difference in speed performance between XFS and ext2 right now. Thanks SGI and people who made it for great product. Valentine. On Mon, 16 Jul 2001, Steve Lord wrote: > > Hi, > > I'm got XFS working on my Linux workstation (dual PIII 550Mhz, > > 512Mb RAM). The only things I've noticed that my applications > > compiled by a factor of 2 slower compared to ext2. It is quite > > large set of libraries (around 300) and problem seems to be > > at linkage stage. My questions are the following: > > 1) which parameters will allow to tune XFS performance > > 2) is it possible to mount XFS with another parameters (such > > as logsize) compare to ones used during formatting (I've used default). > > How are you building your libraries, how much is usually running at once > in terms of compilers and linkers. Also, which version of the code are you > running? > > Thanks > > Steve > > > > > Thank you, > > Valentine. > > From owner-linux-xfs@oss.sgi.com Tue Jul 17 07:56:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HEuAY20586 for linux-xfs-outgoing; Tue, 17 Jul 2001 07:56:10 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HEu3V20567 for ; Tue, 17 Jul 2001 07:56:03 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 767B11E3FA; Tue, 17 Jul 2001 16:55:53 +0200 (MEST) Date: Tue, 17 Jul 2001 16:55:43 +0200 From: Andi Kleen To: Federico Sevilla III Cc: Linux XFS Mailing List Subject: [PATCH] Re: chacl question Message-ID: <20010717165543.A21737@gruyere.muc.suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jijo@leathercollection.ph on Tue, Jul 17, 2001 at 09:29:01PM +0800 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 17, 2001 at 09:29:01PM +0800, Federico Sevilla III wrote: > But it says: > > chacl: "u::rwx,g::,o::,u:jijo:r-x,m::r-x" is an invalid ACL specification. You cannot have multiple 'u' specifikations. > > 'chacl -l test' output: test[] which (I think) verifies that ACLs are > enabled and work. > > What am I doing wrong? Also, is it possible to just add an ACL? Let's say > I already have ACLs set up, and just want to enable someone else to read > and access this file, how do I do this? Do I have to list everyone else? > Or if I want to revoke access from someone? > > It's my first time to handle ACLs. I hope you guys can be patient with > this newbie. :) :) Similar problems have also annoyed, annoyed me enough to produce the following patch which adds somewhat usable error reporting to libacl. Just apply it below cmd/chacl and get at least usable error messages. It also fixes one bug in the manpage. -Andi Index: chacl/chacl.c =================================================================== RCS file: /cvs/linux-2.4-xfs/cmd/acl/chacl/chacl.c,v retrieving revision 1.5 diff -u -u -r1.5 chacl.c --- chacl/chacl.c 2001/06/11 20:48:59 1.5 +++ chacl/chacl.c 2001/07/17 14:50:52 @@ -165,7 +165,11 @@ acl = acl_from_text (argv[optind]); if (acl == NULL || acl_valid(acl) == -1) { + char *errs; + errs = acl_error_string(); fprintf (stderr, inv_acl, program, argv[optind]); + if (errs) + fprintf (stderr, "%s\n", errs); return (1); } optind++; Index: include/acl.h =================================================================== RCS file: /cvs/linux-2.4-xfs/cmd/acl/include/acl.h,v retrieving revision 1.6 diff -u -u -r1.6 acl.h --- include/acl.h 2001/06/06 04:55:01 1.6 +++ include/acl.h 2001/07/17 14:50:52 @@ -163,6 +163,7 @@ extern char *acl_to_short_text(acl_t, ssize_t *); extern char *acl_to_text(acl_t, ssize_t *); extern int acl_valid(acl_t); +extern char *acl_error_string(void); /* system calls */ extern int acl_get(const char *, int, struct acl *, struct acl *); Index: libacl/acl.c =================================================================== RCS file: /cvs/linux-2.4-xfs/cmd/acl/libacl/acl.c,v retrieving revision 1.12 diff -u -u -r1.12 acl.c --- libacl/acl.c 2001/07/02 03:31:14 1.12 +++ libacl/acl.c 2001/07/17 14:50:54 @@ -58,6 +58,18 @@ #define setoserror(E) errno = (E) +#ifdef __GNUC__ +#define PRINTFLIKE(a,b) __attribute((format(printf, a, b))) +#else +#define PRINTFLIKE(a,b) +#endif +static void +acl_verbose_error (void *b0, void *b1, int e, char *fmt, ...) PRINTFLIKE(4,5); + + +/* Not threadsafe, but overwriting is harmless */ +static char acl_error_buf[256]; + /* * Compatibility flag for IRIX functionality * Default is to support common Linux/Posix ACL functionality @@ -142,17 +154,33 @@ return 0; } + static void acl_error (void *b0, void *b1, int e) { - if (b0) free (b0); if (b1) free (b1); setoserror (e); + acl_error_buf[0] = 0; } + +static void +acl_verbose_error (void *b0, void *b1, int e, char *fmt, ...) +{ + va_list ap; + va_start(ap,fmt); + vsnprintf(acl_error_buf, sizeof(acl_error_buf), fmt, ap); + va_end(ap); + if (b0) + free (b0); + if (b1) + free (b1); + setoserror (e); +} + /* * Converts either long or short text form of ACL into internal representations * Input long text form lines are either @@ -173,8 +201,8 @@ char c; /* check args for bogosity */ - if (buf_p == NULL || *buf_p == '\0') { - acl_error (NULL, NULL, EINVAL); + if (buf_p == NULL || *buf_p == '\0') { + acl_verbose_error (NULL, NULL, EINVAL, "zero or empty acl string"); return (NULL); } @@ -210,7 +238,7 @@ char *tag, *qa, *perm; if (aclbuf->acl_cnt > ACL_MAX_ENTRIES) { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "too many acl entries"); return (NULL); } @@ -223,7 +251,7 @@ /* get qualifier */ if ((qa = skip_separator(fp)) == NULL) { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "cannot separate qualifier after char %d(%4s)", fp-bp, fp); return (NULL); } if (*qa == ':') { @@ -238,7 +266,7 @@ /* get permissions */ if ((perm = skip_separator(fp)) == NULL) { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "cannot separate permissions after char %d(%4s)", fp-bp, fp); return (NULL); } fp = skip_to_white(perm); @@ -254,13 +282,22 @@ if (qa == NULL || *qa == '\0') entry->ae_tag = ACL_USER_OBJ; else { + int olderrno = errno, e; entry->ae_tag = ACL_USER; - if ((pw = getpwnam(qa))) + + errno = 0; + pw = getpwnam(qa); + e = errno; + errno = olderrno; + if (!pw && e) { + acl_verbose_error(bp,aclbuf,EINVAL,"cannot find user %s: %s", qa, strerror(e)); + return NULL; + } else if (pw) entry->ae_id = pw->pw_uid; else if (isdigit(*qa)) entry->ae_id = atoi(qa); else { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "cannot parse user id %s", qa); return (NULL); } } @@ -271,13 +308,22 @@ if (qa == NULL || *qa == '\0') entry->ae_tag = ACL_GROUP_OBJ; else { + int olderrno=errno, e; entry->ae_tag = ACL_GROUP; - if ((gr = getgrnam (qa))) + errno = 0; + gr = getgrnam(qa); + e = errno; + errno = olderrno; + if (gr) entry->ae_id = gr->gr_gid; - else if (isdigit (*qa)) + else if (e) { + acl_verbose_error(bp,aclbuf,EINVAL, + "cannot find group %s:%s\n", qa, strerror(e)); + return NULL; + } else if (isdigit (*qa)) entry->ae_id = atoi(qa); else { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "invalid group %s", qa); return (NULL); } } @@ -287,7 +333,7 @@ if (!strcmp(tag, "other") || !strcmp(tag, "o")) { entry->ae_tag = ACL_OTHER_OBJ; if (qa != NULL && *qa != '\0') { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "garbage after other: %s", qa); return (NULL); } } @@ -296,19 +342,19 @@ if (!strcmp(tag, "mask") || !strcmp(tag, "m")) { entry->ae_tag = ACL_MASK; if (qa != NULL && *qa != '\0') { - acl_error (bp, aclbuf, EINVAL); + acl_verbose_error (bp, aclbuf, EINVAL, "garbage after mask: %s", qa); return (NULL); } } /* Process invalid tag keyword */ if (entry->ae_tag == -1) { - acl_error(bp, aclbuf, EINVAL); + acl_verbose_error(bp, aclbuf, EINVAL, "invalid tag"); return (NULL); } if (get_perm (perm, &entry->ae_perm) == -1) { - acl_error ((void *) bp, (void *) aclbuf, EINVAL); + acl_verbose_error ((void *) bp, (void *) aclbuf, EINVAL, "bad permission %s", perm); return (NULL); } } @@ -512,14 +558,18 @@ int user = 0, group = 0, other = 0, mask = 0, mask_required = 0; int i, j; - if (aclp == NULL) + if (aclp == NULL) { + acl_verbose_error(NULL,NULL,EINVAL,"no acl"); goto acl_invalid; - + } + if (aclp->acl_cnt == ACL_NOT_PRESENT) return 0; - if (aclp->acl_cnt < 0 || aclp->acl_cnt > ACL_MAX_ENTRIES) + if (aclp->acl_cnt < 0 || aclp->acl_cnt > ACL_MAX_ENTRIES) { + acl_verbose_error(NULL,NULL,EINVAL,"too many acl entries %d", aclp->acl_cnt); goto acl_invalid; + } for (i = 0; i < aclp->acl_cnt; i++) { @@ -529,39 +579,72 @@ switch (entry->ae_tag) { case ACL_USER_OBJ: - if (user++) + if (user++) { + acl_verbose_error(NULL,NULL,EINVAL,"multiple user entries"); goto acl_invalid; + } break; case ACL_GROUP_OBJ: - if (group++) + if (group++) { + acl_verbose_error(NULL,NULL,EINVAL,"multiple group entries"); goto acl_invalid; + } break; case ACL_OTHER_OBJ: - if (other++) + if (other++){ + acl_verbose_error(NULL,NULL,EINVAL,"multiple other entries"); goto acl_invalid; + } break; case ACL_USER: case ACL_GROUP: for (j = i + 1; j < aclp->acl_cnt; j++) { e = &aclp->acl_entry[j]; - if (e->ae_id == entry->ae_id && e->ae_tag == entry->ae_tag) + if (e->ae_id == entry->ae_id && e->ae_tag == entry->ae_tag) { + char *what = entry->ae_tag==ACL_USER ? "user":"group"; + acl_verbose_error(NULL,NULL, + EINVAL,"duplicate %s acl for %s %d", + what, + what, + e->ae_id); + goto acl_invalid; + } } mask_required++; break; case ACL_MASK: - if (mask++) + if (mask++) { + acl_verbose_error(NULL,NULL,EINVAL,"multiple masks specified"); goto acl_invalid; + } break; default: goto acl_invalid; } } - if (!user || !group || !other || (mask_required && !mask)) + if (!user) { + acl_verbose_error(NULL,NULL,EINVAL,"missing user rights entry in acl"); goto acl_invalid; - else - return 0; + } + if (!other) { + acl_verbose_error(NULL,NULL,EINVAL,"missing other rights entry in acl"); + goto acl_invalid; + } + if (!group) { + acl_verbose_error(NULL,NULL,EINVAL,"missing group entry in acl"); + goto acl_invalid; + } + if (!mask) { + acl_verbose_error(NULL,NULL,EINVAL,"missing mask in acl"); + goto acl_invalid; + } + if (mask_required && !mask) { + acl_verbose_error(NULL,NULL,EINVAL,"mask required and no mask"); + goto acl_invalid; + } + return 0; acl_invalid: setoserror (EINVAL); return (-1); @@ -1184,4 +1267,11 @@ "for this architecture\n"); return 0; #endif +} + +char *acl_error_string(void) +{ + if (acl_error_buf[0]) + return acl_error_buf; + return NULL; } Index: man/man5/acl.5 =================================================================== RCS file: /cvs/linux-2.4-xfs/cmd/acl/man/man5/acl.5,v retrieving revision 1.4 diff -u -u -r1.4 acl.5 --- man/man5/acl.5 2001/06/15 14:25:43 1.4 +++ man/man5/acl.5 2001/07/17 14:50:55 @@ -100,8 +100,7 @@ "user", "group", "other", "mask", "u", "g", "o", "m". .P The second field is a user name, numeric UID, group name, or numeric GID, depending -on the value of the first field. (\fIacl_from_text\fP(3c) supports only -the strings, not the numeric UID/GID values.) +on the value of the first field. If the second field is empty, it implies that the ACL entry is for the owning user or group of the file. Mask and other entries must have an empty second field. The third field is From owner-linux-xfs@oss.sgi.com Tue Jul 17 08:01:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HF1PU20865 for linux-xfs-outgoing; Tue, 17 Jul 2001 08:01:25 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HF1LV20846 for ; Tue, 17 Jul 2001 08:01:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA378858 for ; Tue, 17 Jul 2001 17:01:18 +0200 (CEST) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA1547040; Tue, 17 Jul 2001 09:59:42 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA33633; Tue, 17 Jul 2001 09:59:42 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id JAA33070; Tue, 17 Jul 2001 09:59:42 -0500 (CDT) Message-Id: <200107171459.JAA33070@fsgi158.americas.sgi.com> Subject: Re: chacl questions To: jijo@leathercollection.ph (Federico Sevilla III) Date: Tue, 17 Jul 2001 09:59:41 -0500 (CDT) Cc: linux-xfs@oss.sgi.com (Linux XFS Mailing List) In-Reply-To: from "Federico Sevilla III" at Jul 17, 2001 09:29:01 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi everyone, > > I wonder what's wrong with the way I'm doing things. > > I create a directory "test", owned by root, group root, perms u=rwx,g=,o=. > I want to allow user "jijo" to access this, too, but to only read it, I > try the following: > > chacl u::rwx,g::,o::,u:jijo:r-x,m::r-x test > > But it says: > > chacl: "u::rwx,g::,o::,u:jijo:r-x,m::r-x" is an invalid ACL specification. > > 'chacl -l test' output: test[] which (I think) verifies that ACLs are > enabled and work. > > What am I doing wrong? Also, is it possible to just add an ACL? Let's say > I already have ACLs set up, and just want to enable someone else to read > and access this file, how do I do this? Do I have to list everyone else? > Or if I want to revoke access from someone? > chacl u::rwx,g::---,o::---,u:jijo:r-x,m::r-x test ^^^ ^^^ I think you need to add the (empty) permissions. Yes, I think you need to list everyone on the chacl line. Tad > It's my first time to handle ACLs. I hope you guys can be patient with > this newbie. :) :) > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. > From owner-linux-xfs@oss.sgi.com Tue Jul 17 08:04:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HF4X520996 for linux-xfs-outgoing; Tue, 17 Jul 2001 08:04:33 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HF4TV20977 for ; Tue, 17 Jul 2001 08:04:29 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA366952 for ; Tue, 17 Jul 2001 17:04:27 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2448410; Tue, 17 Jul 2001 10:03:11 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA02528; Tue, 17 Jul 2001 10:03:10 -0500 (CDT) Subject: Re: problems formatting partition via ks From: Eric Sandeen To: Will Francis Cc: linux-xfs@oss.sgi.com In-Reply-To: <200107162311.f6GNBKT21957@vertigo.incyte.com> References: <200107162311.f6GNBKT21957@vertigo.incyte.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 17 Jul 2001 10:03:15 -0500 Message-Id: <995382195.1063.2.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 16 Jul 2001 16:11:20 -0700, Will Francis wrote: > when making /usr/local/net, it fails with these errors: Nathan's right, it's a limitation on the length of allowed labels in XFS... I put the labeling code into the XFS installer to make it behave more like the ext2 install, but didn't anticipate this. Whoops. I'll put out an update floppy to fix this (by turning labels back off, I suppose). > It threw similar fits when I tried to put /boot on it's > own partition so I've just put it back into / What happens when you remove the /usr/local/net partition - does /boot still complain? -Eric From owner-linux-xfs@oss.sgi.com Tue Jul 17 08:31:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HFV6x21458 for linux-xfs-outgoing; Tue, 17 Jul 2001 08:31:06 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HFV2V21439 for ; Tue, 17 Jul 2001 08:31:03 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6HFVdG13035 for ; Tue, 17 Jul 2001 18:31:43 +0300 Date: Tue, 17 Jul 2001 18:30:53 +0300 (EEST) From: Jani Jaakkola To: Subject: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk OK, this seems to be deterministic and not a HW-problem.. I am testing xfs on a brand new linux file server having a 1.1T xfs filesystem in dual processor (Intel III Xeon 1GHz) motherboard with 1G memory. When using xfs with linux kernel 2.4.6 (compiled with egcs-2.91.66) and Linux software RAID5 all processes accessing the /dev/md0 device lockup in D-state when trying to write files from network with tar (kupdated, tar, pagebuf_daemon and /bin/sync) typically after few hundred megabytes have been written. Kdb tells me that all processes are hanging forever in get_active_stripe(). All SCSI drives are still working, when accessed directly through /dev/sda-g.. Oops, seems that they too get stuck after a while (perhaps trying to write some pages to disk). The same problem does not come up when using ext2. /bin/free tells me this: total used free shared buffers cached Mem: 899328 324772 574556 0 134952 115272 -/+ buffers/cache: 74548 824780 Swap: 2097136 0 2097136 Only thing I can do, is to reboot with /sbin/reboot -nf. I've have seen other reports in mailing list with this kind of problem. Are there known solutions? I think I might try the cvs version... - Jani From owner-linux-xfs@oss.sgi.com Tue Jul 17 08:53:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HFrtF22148 for linux-xfs-outgoing; Tue, 17 Jul 2001 08:53:55 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HFrqV22126 for ; Tue, 17 Jul 2001 08:53:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA23754 for ; Tue, 17 Jul 2001 08:53:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2451248; Tue, 17 Jul 2001 10:52:31 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA84852; Tue, 17 Jul 2001 10:52:31 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HFrfZ01677; Tue, 17 Jul 2001 10:53:41 -0500 Message-Id: <200107171553.f6HFrfZ01677@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jani Jaakkola cc: linux-xfs@oss.sgi.com Subject: Re: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem In-Reply-To: Message from Jani Jaakkola of "Tue, 17 Jul 2001 18:30:53 +0300." Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_3528941910" Date: Tue, 17 Jul 2001 10:53:41 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multipart MIME message. --==_Exmh_3528941910 Content-Type: text/plain Could you possibly try the cvs tree, Linus was still working deadlocks out of the memory allocation/reclaim end of things up until 2.4.7-pre2. XFS and ext2 will almost certainly push things in different directions. Another issue here is that you may actually be creating inode numbers with greated than 32 bits in them with a filesystem this size. If you run xfs_growfs -n on the mount point of the filesystem and run the attached perl script with the following arguments it will tell you how many bits your inodes can consume. inode_size.pl blk-size inode-size agcount blocks xfs_growfs -n /usr meta-data=/usr isize=256 agcount=8, agsize=103670 blks data = bsize=4096 blocks=829355, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=1500 realtime =none extsz=65536 blocks=0, rtextents=0 inode_size.pl 4096 256 8 829355 Blocksize: 4096 Inodesize: 256 Number of allocation groups: 8 Number of data blocks (in filesystem blocks) : +829355 Number of inodes in a filesystem block: 16 - bits: 4 Number of datablocks in an allocation group +103669 - bits: 17 Number of allocation groups: 8 - bits: 3 Total number of bits required for an inode: 24 You can play with numbers to make the number of bits <= 32, increasing the inode size will be the thing which does it for you, also if you did not end up with 4GB allocation groups you should attempt to get them setup that way. Unfortunately this means mkfs to fix. I do have some plans to make this issue go away for large filesystems, but you beat me to it! Steve > > OK, this seems to be deterministic and not a HW-problem.. > > I am testing xfs on a brand new linux file server having a 1.1T xfs > filesystem in dual processor (Intel III Xeon 1GHz) motherboard > with 1G memory. > > When using xfs with linux kernel 2.4.6 (compiled with egcs-2.91.66) and > Linux software RAID5 all processes accessing the /dev/md0 device lockup in > D-state when trying to write files from network with tar (kupdated, tar, > pagebuf_daemon and /bin/sync) typically after few hundred megabytes have > been written. Kdb tells me that all processes are hanging forever in > get_active_stripe(). > > All SCSI drives are still working, when accessed directly > through /dev/sda-g.. Oops, seems that they too get stuck after a while > (perhaps trying to write some pages to disk). > > The same problem does not come up when using ext2. > > /bin/free tells me this: > total used free shared buffers cached > Mem: 899328 324772 574556 0 134952 115272 > -/+ buffers/cache: 74548 824780 > Swap: 2097136 0 2097136 > > > Only thing I can do, is to reboot with /sbin/reboot -nf. > > I've have seen other reports in mailing list with this kind of problem. > Are there known solutions? I think I might try the cvs version... > > - Jani --==_Exmh_3528941910 Content-Type: text/plain ; name="inode_size.pl" Content-Description: inode_size.pl Content-Disposition: attachment; filename="inode_size.pl" #!/usr/bin/perl # bryder@sgi.com hacked this up. # It predicts the size of an inode number in bits for an # xfs filesystem (as at 6.5.11 anyway). # # It is slightly conservative in that it assumes that he entire # disk is used for the data section which is incorrect because # the log region (if it is internal) will use some space. use POSIX; use Math::BigInt; sub max_bits($) { my $value = Math::BigInt->new(shift @_); my $bitcount = 0; while ($value != 0){ $value = $value / 2; $bitcount++; } return $bitcount; } $debug = 1 ; if ($#ARGV != 3){ print "Usage: perl inode_size.pl blocksize(bytes) inodesize(bytes) number_of_agroups(count) datablocks in filesystem(in fs blocks)\n"; exit; } $blocksize=$ARGV[0]; $inodesize=$ARGV[1]; $agcount=$ARGV[2]; $datablock_count=Math::BigInt->new($ARGV[3]); print "Blocksize: $blocksize\n"; print "Inodesize: $inodesize\n"; print "Number of allocation groups: $agcount\n"; print "Number of data blocks (in filesystem blocks) : $datablock_count\n"; print "\n"; $inopblock = $blocksize / $inodesize; $inopblog = max_bits($inopblock-1); print "Number of inodes in a filesystem block: $inopblock - bits: $inopblog\n"; $agblk = Math::BigInt->new(ceil($datablock_count / $agcount)); $agblklog = max_bits($agblk-1); print "Number of datablocks in an allocation group $agblk - bits: $agblklog \n"; $agcountlog = max_bits($agcount-1); print "Number of allocation groups: $agcount - bits: $agcountlog\n"; print "Total number of bits required for an inode: ", $agcountlog + $agblklog + $inopblog, "\n"; --==_Exmh_3528941910-- From owner-linux-xfs@oss.sgi.com Tue Jul 17 09:30:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HGUDk23339 for linux-xfs-outgoing; Tue, 17 Jul 2001 09:30:13 -0700 Received: from sws18.ctd.ornl.gov (sws18.ctd.ornl.gov [160.91.20.118]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HGUBV23320 for ; Tue, 17 Jul 2001 09:30:11 -0700 Received: (qmail 410184 invoked by uid 3995); 17 Jul 2001 16:30:10 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15188.26642.110967.520516@sws18.ctd.ornl.gov> Date: Tue, 17 Jul 2001 12:30:10 -0400 From: Dave Sill To: linux-xfs@oss.sgi.com Subject: RH kernel upgraded; can't boot X-Mailer: VM 6.76 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Organization: Oak Ridge National Lab, Oak Ridge, Tenn., USA X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Tue Jul 17 09:53:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HGrRD23859 for linux-xfs-outgoing; Tue, 17 Jul 2001 09:53:27 -0700 Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HGrOV23840 for ; Tue, 17 Jul 2001 09:53:24 -0700 Received: from iastate.edu (cousteau.eng.iastate.edu [129.186.23.164]) by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id LAA16378 for ; Tue, 17 Jul 2001 11:53:20 -0500 Message-ID: <3B546D7F.71D884B@iastate.edu> Date: Tue, 17 Jul 2001 11:53:19 -0500 From: Adrian Hill X-Mailer: Mozilla 4.75 [en] (X11; U; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Quota reporting for NFS mounts Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id f6HGrPV23841 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello All I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the one based on the redhat kernel). I'm also using quota-3.01-pre7 which I built from the source rpm. I have exported my /export partition over NFS which file system is XFS. I can mount this from client type machines, but when I try (on the client) to list my quota, the command just hangs. I've run snoop on the connection, and it appears that my server (sherlock) doesn't respond to the client's (cousteau) requests. I also verified that rpc.rquotad is running on my server. Any idea how I can get remote quota reporting working? Thanks in advance, Adrian Here is the snoop output: [cousteau ~ 7]# snoop sherlock Using device ec0 (promiscuous mode) cousteau -> sherlock TCP D=111 S=661 Syn Seq=1727695818 Len=0 Win=61440 cousteau -> sherlock TCP D=111 S=661 Syn Seq=1727695818 Len=0 Win=61440 sherlock -> cousteau TCP D=661 S=111 Syn Ack=1727695819 Seq=2875267868 Len=0 Win=5840 cousteau -> sherlock TCP D=111 S=661 Ack=2875267869 Seq=1727695819 Len=0 Win=61320 cousteau -> sherlock TCP D=111 S=661 Ack=2875267869 Seq=1727695819 Len=0 Win=61320 cousteau -> sherlock TCP D=111 S=661 Fin Ack=2875267869 Seq=1727695819 Len=0 Win=61320 cousteau -> sherlock TCP D=111 S=661 Fin Ack=2875267869 Seq=1727695819 Len=0 Win=61320 sherlock -> cousteau TCP D=661 S=111 Fin Ack=1727695820 Seq=2875267869 Len=0 Win=5840 cousteau -> sherlock TCP D=111 S=661 Ack=2875267870 Seq=1727695820 Len=0 Win=61320 cousteau -> sherlock TCP D=111 S=661 Ack=2875267870 Seq=1727695820 Len=0 Win=61320 cousteau -> sherlock PORTMAP C GETPORT prog=100011 (RQUOTA) vers=1 proto=UDP cousteau -> sherlock PORTMAP C GETPORT prog=100011 (RQUOTA) vers=1 proto=UDP (retransmit) sherlock -> cousteau PORTMAP R GETPORT port=838 cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export (retransmit) cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export (retransmit) cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export (retransmit) cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export (retransmit) cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export (retransmit) [cousteau ~ 8]# From owner-linux-xfs@oss.sgi.com Tue Jul 17 09:55:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HGtwX24026 for linux-xfs-outgoing; Tue, 17 Jul 2001 09:55:58 -0700 Received: from sws18.ctd.ornl.gov (sws18.ctd.ornl.gov [160.91.20.118]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HGtuV24007 for ; Tue, 17 Jul 2001 09:55:56 -0700 Received: (qmail 410372 invoked by uid 3995); 17 Jul 2001 16:55:56 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15188.28187.791550.917222@sws18.ctd.ornl.gov> Date: Tue, 17 Jul 2001 12:55:55 -0400 From: Dave Sill To: linux-xfs@oss.sgi.com Subject: Re: RH kernel upgraded; can't boot In-Reply-To: <15188.26642.110967.520516@sws18.ctd.ornl.gov> References: <15188.26642.110967.520516@sws18.ctd.ornl.gov> X-Mailer: VM 6.76 under 21.1 "20 Minutes to Nikko" XEmacs Lucid (patch 2) Organization: Oak Ridge National Lab, Oak Ridge, Tenn., USA X-Face: "p~Q]mg{;e*}YR|)&Q/&Q\*~5UWfZX34;5M; Tue, 17 Jul 2001 09:57:39 -0700 Message-Id: <200107171657.f6HGvdV24138@oss.sgi.com> Received: from there (10.26.109.242 [10.26.109.242]) by exchange.visa-austria.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 3NSC48AK; Tue, 17 Jul 2001 18:57:30 +0200 From: =?iso-8859-1?q?Kr=FCckel=20Oliver?= Reply-To: o.krueckel@visa-austria.com Organization: VISA To: linux-xfs@oss.sgi.com Subject: xfs kernel problem Date: Tue, 17 Jul 2001 18:57:38 +0200 X-Mailer: KMail [version 1.2.3] MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_24NM42YQ99BGNYRYE30D" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --------------Boundary-00=_24NM42YQ99BGNYRYE30D Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Hallo I'm new in this list, I have the follow problem on a, HW: HP Lp 2000r: CPU P III 866 MHz, 512 MByte Ram, Raid 5 Controler NetRaid 1i, 3x SCSI DISK a. 32 GByte SW: Linux SuSE-7.1 with servarel patches from the officel SuSE web-server gcc: version 2.95.2 19991024 (release) libc: version 2.95.2 xfs: utilitys tested with downloaded rpm and selv compiles src-files the filesystem: Raid 5 over the 3 disks /dev/sda1 -> 30 Mb, HP service partiton /dev/sda2 -> 8Mb fs: ext2 mounted at /boot /dev/sda3 -> 128Mb swap /dev/sda4 -> extended partition /dev/sda5 -> 1,5 Gb fs:reiserfs mounted at / /dev/sda6 -> the rest of the disk fs:reiserfs or xfs mounted at /daten I patch the officel linux kernel with the latest xfs patch 2.4.5 <- Release-1.0.1 and the 2.4.6 <- linux-2.4.6-xfs-07052001.patch.bz2 and also have the follow descripted error with the downloadet kernel-2.4.5-SGI_XFS_1.0.1.src.rpm file. I have attached the .config file of the kernel configuration The compilation of the kernel works fine also the first boot with the new kernel and now my problem: if i reboot the server with the xfs kernel and the server coms up there are sum files and executables witch i can't access ore execute, sum examples: the programms find, make, ... or file hosts, ... if i reboot the server again, there are much more files that can't access or execute, there are alwais other executebles and files by every test, but i didn't have this problems with the non patched kernel. i have also this error at the copy of a lot of file < 4.Gb via mounted nfs share to /daten after the first boot with the xfs-kernel, it is no matter if /daten is a reiserfs or a xfs filesystem (there are damged files on / and /daten). on a other server with GDT SCSI Disk Array Controller (it is a noname server) i havn't this problem so i think this is a problem with the xfs patch and the AMI MegaRAID Controller. is my supposition right or what is wrong at my configuration? mfg. O.K. --------------Boundary-00=_24NM42YQ99BGNYRYE30D Content-Type: text/plain; charset="iso-8859-1"; name="config" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="config" IwojIEF1dG9tYXRpY2FsbHkgZ2VuZXJhdGVkIGJ5IG1ha2UgbWVudWNvbmZpZzogZG9uJ3QgZWRp dAojCkNPTkZJR19YODY9eQpDT05GSUdfSVNBPXkKIyBDT05GSUdfU0JVUyBpcyBub3Qgc2V0CkNP TkZJR19VSUQxNj15CgojCiMgQ29kZSBtYXR1cml0eSBsZXZlbCBvcHRpb25zCiMKQ09ORklHX0VY UEVSSU1FTlRBTD15CgojCiMgTG9hZGFibGUgbW9kdWxlIHN1cHBvcnQKIwpDT05GSUdfTU9EVUxF Uz15CkNPTkZJR19NT0RWRVJTSU9OUz15CkNPTkZJR19LTU9EPXkKCiMKIyBQcm9jZXNzb3IgdHlw ZSBhbmQgZmVhdHVyZXMKIwojIENPTkZJR19NMzg2IGlzIG5vdCBzZXQKIyBDT05GSUdfTTQ4NiBp cyBub3Qgc2V0CiMgQ09ORklHX001ODYgaXMgbm90IHNldAojIENPTkZJR19NNTg2VFNDIGlzIG5v dCBzZXQKIyBDT05GSUdfTTU4Nk1NWCBpcyBub3Qgc2V0CiMgQ09ORklHX002ODYgaXMgbm90IHNl dApDT05GSUdfTVBFTlRJVU1JSUk9eQojIENPTkZJR19NUEVOVElVTTQgaXMgbm90IHNldAojIENP TkZJR19NSzYgaXMgbm90IHNldAojIENPTkZJR19NSzcgaXMgbm90IHNldAojIENPTkZJR19NQ1JV U09FIGlzIG5vdCBzZXQKIyBDT05GSUdfTVdJTkNISVBDNiBpcyBub3Qgc2V0CiMgQ09ORklHX01X SU5DSElQMiBpcyBub3Qgc2V0CiMgQ09ORklHX01XSU5DSElQM0QgaXMgbm90IHNldAojIENPTkZJ R19NQ1lSSVhJSUkgaXMgbm90IHNldApDT05GSUdfWDg2X1dQX1dPUktTX09LPXkKQ09ORklHX1g4 Nl9JTlZMUEc9eQpDT05GSUdfWDg2X0NNUFhDSEc9eQpDT05GSUdfWDg2X1hBREQ9eQpDT05GSUdf WDg2X0JTV0FQPXkKQ09ORklHX1g4Nl9QT1BBRF9PSz15CiMgQ09ORklHX1JXU0VNX0dFTkVSSUNf U1BJTkxPQ0sgaXMgbm90IHNldApDT05GSUdfUldTRU1fWENIR0FERF9BTEdPUklUSE09eQpDT05G SUdfWDg2X0wxX0NBQ0hFX1NISUZUPTUKQ09ORklHX1g4Nl9UU0M9eQpDT05GSUdfWDg2X0dPT0Rf QVBJQz15CkNPTkZJR19YODZfUEdFPXkKQ09ORklHX1g4Nl9VU0VfUFBST19DSEVDS1NVTT15CiMg Q09ORklHX1RPU0hJQkEgaXMgbm90IHNldAojIENPTkZJR19NSUNST0NPREUgaXMgbm90IHNldAoj IENPTkZJR19YODZfTVNSIGlzIG5vdCBzZXQKIyBDT05GSUdfWDg2X0NQVUlEIGlzIG5vdCBzZXQK Q09ORklHX05PSElHSE1FTT15CiMgQ09ORklHX0hJR0hNRU00RyBpcyBub3Qgc2V0CiMgQ09ORklH X0hJR0hNRU02NEcgaXMgbm90IHNldAojIENPTkZJR19NQVRIX0VNVUxBVElPTiBpcyBub3Qgc2V0 CkNPTkZJR19NVFJSPXkKIyBDT05GSUdfU01QIGlzIG5vdCBzZXQKQ09ORklHX1g4Nl9VUF9JT0FQ SUM9eQpDT05GSUdfWDg2X0lPX0FQSUM9eQpDT05GSUdfWDg2X0xPQ0FMX0FQSUM9eQpDT05GSUdf VVBfTk1JX1dBVENIRE9HPXkKCiMKIyBHZW5lcmFsIHNldHVwCiMKQ09ORklHX05FVD15CiMgQ09O RklHX1ZJU1dTIGlzIG5vdCBzZXQKQ09ORklHX1BDST15CiMgQ09ORklHX1BDSV9HT0JJT1MgaXMg bm90IHNldAojIENPTkZJR19QQ0lfR09ESVJFQ1QgaXMgbm90IHNldApDT05GSUdfUENJX0dPQU5Z PXkKQ09ORklHX1BDSV9CSU9TPXkKQ09ORklHX1BDSV9ESVJFQ1Q9eQpDT05GSUdfUENJX05BTUVT PXkKIyBDT05GSUdfRUlTQSBpcyBub3Qgc2V0CiMgQ09ORklHX01DQSBpcyBub3Qgc2V0CkNPTkZJ R19IT1RQTFVHPXkKCiMKIyBQQ01DSUEvQ2FyZEJ1cyBzdXBwb3J0CiMKIyBDT05GSUdfUENNQ0lB IGlzIG5vdCBzZXQKQ09ORklHX1NZU1ZJUEM9eQpDT05GSUdfQlNEX1BST0NFU1NfQUNDVD15CkNP TkZJR19TWVNDVEw9eQpDT05GSUdfS0NPUkVfRUxGPXkKIyBDT05GSUdfS0NPUkVfQU9VVCBpcyBu b3Qgc2V0CkNPTkZJR19CSU5GTVRfQU9VVD1tCkNPTkZJR19CSU5GTVRfRUxGPXkKQ09ORklHX0JJ TkZNVF9NSVNDPW0KIyBDT05GSUdfUE0gaXMgbm90IHNldAojIENPTkZJR19BQ1BJIGlzIG5vdCBz ZXQKIyBDT05GSUdfQVBNIGlzIG5vdCBzZXQKCiMKIyBNZW1vcnkgVGVjaG5vbG9neSBEZXZpY2Vz IChNVEQpCiMKIyBDT05GSUdfTVREIGlzIG5vdCBzZXQKCiMKIyBQYXJhbGxlbCBwb3J0IHN1cHBv cnQKIwpDT05GSUdfUEFSUE9SVD1tCkNPTkZJR19QQVJQT1JUX1BDPW0KIyBDT05GSUdfUEFSUE9S VF9QQ19GSUZPIGlzIG5vdCBzZXQKQ09ORklHX1BBUlBPUlRfUENfU1VQRVJJTz15CiMgQ09ORklH X1BBUlBPUlRfQU1JR0EgaXMgbm90IHNldAojIENPTkZJR19QQVJQT1JUX01GQzMgaXMgbm90IHNl dAojIENPTkZJR19QQVJQT1JUX0FUQVJJIGlzIG5vdCBzZXQKIyBDT05GSUdfUEFSUE9SVF9TVU5C UFAgaXMgbm90IHNldAojIENPTkZJR19QQVJQT1JUX09USEVSIGlzIG5vdCBzZXQKQ09ORklHX1BB UlBPUlRfMTI4ND15CgojCiMgUGx1ZyBhbmQgUGxheSBjb25maWd1cmF0aW9uCiMKIyBDT05GSUdf UE5QIGlzIG5vdCBzZXQKIyBDT05GSUdfSVNBUE5QIGlzIG5vdCBzZXQKCiMKIyBCbG9jayBkZXZp Y2VzCiMKQ09ORklHX0JMS19ERVZfRkQ9eQojIENPTkZJR19CTEtfREVWX1hEIGlzIG5vdCBzZXQK IyBDT05GSUdfUEFSSURFIGlzIG5vdCBzZXQKIyBDT05GSUdfQkxLX0NQUV9EQSBpcyBub3Qgc2V0 CiMgQ09ORklHX0JMS19DUFFfQ0lTU19EQSBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfREFD OTYwIGlzIG5vdCBzZXQKQ09ORklHX0JMS19ERVZfTE9PUD1tCiMgQ09ORklHX0JMS19ERVZfTkJE IGlzIG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9SQU0gaXMgbm90IHNldAojIENPTkZJR19CTEtf REVWX0lOSVRSRCBpcyBub3Qgc2V0CgojCiMgTXVsdGktZGV2aWNlIHN1cHBvcnQgKFJBSUQgYW5k IExWTSkKIwojIENPTkZJR19NRCBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfTUQgaXMgbm90 IHNldAojIENPTkZJR19NRF9MSU5FQVIgaXMgbm90IHNldAojIENPTkZJR19NRF9SQUlEMCBpcyBu b3Qgc2V0CiMgQ09ORklHX01EX1JBSUQxIGlzIG5vdCBzZXQKIyBDT05GSUdfTURfUkFJRDUgaXMg bm90IHNldAojIENPTkZJR19CTEtfREVWX0xWTSBpcyBub3Qgc2V0CgojCiMgTmV0d29ya2luZyBv cHRpb25zCiMKQ09ORklHX1BBQ0tFVD15CiMgQ09ORklHX1BBQ0tFVF9NTUFQIGlzIG5vdCBzZXQK Q09ORklHX05FVExJTks9eQojIENPTkZJR19SVE5FVExJTksgaXMgbm90IHNldAojIENPTkZJR19O RVRMSU5LX0RFViBpcyBub3Qgc2V0CiMgQ09ORklHX05FVEZJTFRFUiBpcyBub3Qgc2V0CiMgQ09O RklHX0ZJTFRFUiBpcyBub3Qgc2V0CkNPTkZJR19VTklYPXkKQ09ORklHX0lORVQ9eQpDT05GSUdf SVBfTVVMVElDQVNUPXkKIyBDT05GSUdfSVBfQURWQU5DRURfUk9VVEVSIGlzIG5vdCBzZXQKIyBD T05GSUdfSVBfUE5QIGlzIG5vdCBzZXQKIyBDT05GSUdfTkVUX0lQSVAgaXMgbm90IHNldAojIENP TkZJR19ORVRfSVBHUkUgaXMgbm90IHNldAojIENPTkZJR19JUF9NUk9VVEUgaXMgbm90IHNldAoj IENPTkZJR19JTkVUX0VDTiBpcyBub3Qgc2V0CiMgQ09ORklHX1NZTl9DT09LSUVTIGlzIG5vdCBz ZXQKIyBDT05GSUdfSVBWNiBpcyBub3Qgc2V0CiMgQ09ORklHX0tIVFRQRCBpcyBub3Qgc2V0CiMg Q09ORklHX0FUTSBpcyBub3Qgc2V0CiMgQ09ORklHX0lQWCBpcyBub3Qgc2V0CiMgQ09ORklHX0FU QUxLIGlzIG5vdCBzZXQKIyBDT05GSUdfREVDTkVUIGlzIG5vdCBzZXQKIyBDT05GSUdfQlJJREdF IGlzIG5vdCBzZXQKIyBDT05GSUdfWDI1IGlzIG5vdCBzZXQKIyBDT05GSUdfTEFQQiBpcyBub3Qg c2V0CiMgQ09ORklHX0xMQyBpcyBub3Qgc2V0CiMgQ09ORklHX05FVF9ESVZFUlQgaXMgbm90IHNl dAojIENPTkZJR19FQ09ORVQgaXMgbm90IHNldAojIENPTkZJR19XQU5fUk9VVEVSIGlzIG5vdCBz ZXQKIyBDT05GSUdfTkVUX0ZBU1RST1VURSBpcyBub3Qgc2V0CiMgQ09ORklHX05FVF9IV19GTE9X Q09OVFJPTCBpcyBub3Qgc2V0CgojCiMgUW9TIGFuZC9vciBmYWlyIHF1ZXVlaW5nCiMKIyBDT05G SUdfTkVUX1NDSEVEIGlzIG5vdCBzZXQKCiMKIyBUZWxlcGhvbnkgU3VwcG9ydAojCiMgQ09ORklH X1BIT05FIGlzIG5vdCBzZXQKIyBDT05GSUdfUEhPTkVfSVhKIGlzIG5vdCBzZXQKCiMKIyBBVEEv SURFL01GTS9STEwgc3VwcG9ydAojCkNPTkZJR19JREU9eQoKIwojIElERSwgQVRBIGFuZCBBVEFQ SSBCbG9jayBkZXZpY2VzCiMKQ09ORklHX0JMS19ERVZfSURFPW0KIyBDT05GSUdfQkxLX0RFVl9I RF9JREUgaXMgbm90IHNldAojIENPTkZJR19CTEtfREVWX0hEIGlzIG5vdCBzZXQKIyBDT05GSUdf QkxLX0RFVl9JREVESVNLIGlzIG5vdCBzZXQKIyBDT05GSUdfSURFRElTS19NVUxUSV9NT0RFIGlz IG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9JREVESVNLX1ZFTkRPUiBpcyBub3Qgc2V0CiMgQ09O RklHX0JMS19ERVZfSURFRElTS19GVUpJVFNVIGlzIG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9J REVESVNLX0lCTSBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfSURFRElTS19NQVhUT1IgaXMg bm90IHNldAojIENPTkZJR19CTEtfREVWX0lERURJU0tfUVVBTlRVTSBpcyBub3Qgc2V0CiMgQ09O RklHX0JMS19ERVZfSURFRElTS19TRUFHQVRFIGlzIG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9J REVESVNLX1dEIGlzIG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9DT01NRVJJQUwgaXMgbm90IHNl dAojIENPTkZJR19CTEtfREVWX1RJVk8gaXMgbm90IHNldAojIENPTkZJR19CTEtfREVWX0lERUNT IGlzIG5vdCBzZXQKQ09ORklHX0JMS19ERVZfSURFQ0Q9bQojIENPTkZJR19CTEtfREVWX0lERVRB UEUgaXMgbm90IHNldAojIENPTkZJR19CTEtfREVWX0lERUZMT1BQWSBpcyBub3Qgc2V0CiMgQ09O RklHX0JMS19ERVZfSURFU0NTSSBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfQ01ENjQwIGlz IG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9DTUQ2NDBfRU5IQU5DRUQgaXMgbm90IHNldAojIENP TkZJR19CTEtfREVWX0lTQVBOUCBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfUloxMDAwIGlz IG5vdCBzZXQKQ09ORklHX0JMS19ERVZfSURFUENJPXkKQ09ORklHX0lERVBDSV9TSEFSRV9JUlE9 eQpDT05GSUdfQkxLX0RFVl9JREVETUFfUENJPXkKIyBDT05GSUdfQkxLX0RFVl9PRkZCT0FSRCBp cyBub3Qgc2V0CkNPTkZJR19JREVETUFfUENJX0FVVE89eQpDT05GSUdfQkxLX0RFVl9JREVETUE9 eQojIENPTkZJR19JREVETUFfUENJX1dJUCBpcyBub3Qgc2V0CiMgQ09ORklHX0lERURNQV9ORVdf RFJJVkVfTElTVElOR1MgaXMgbm90IHNldAojIENPTkZJR19CTEtfREVWX0FFQzYyWFggaXMgbm90 IHNldAojIENPTkZJR19BRUM2MlhYX1RVTklORyBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZf QUxJMTVYMyBpcyBub3Qgc2V0CiMgQ09ORklHX1dEQ19BTEkxNVgzIGlzIG5vdCBzZXQKIyBDT05G SUdfQkxLX0RFVl9BTUQ3NDA5IGlzIG5vdCBzZXQKIyBDT05GSUdfQU1ENzQwOV9PVkVSUklERSBp cyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfQ01ENjRYIGlzIG5vdCBzZXQKIyBDT05GSUdfQkxL X0RFVl9DWTgyQzY5MyBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfQ1M1NTMwIGlzIG5vdCBz ZXQKIyBDT05GSUdfQkxLX0RFVl9IUFQzNFggaXMgbm90IHNldAojIENPTkZJR19IUFQzNFhfQVVU T0RNQSBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfSFBUMzY2IGlzIG5vdCBzZXQKQ09ORklH X0JMS19ERVZfUElJWD15CkNPTkZJR19QSUlYX1RVTklORz15CiMgQ09ORklHX0JMS19ERVZfTlM4 NzQxNSBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfT1BUSTYyMSBpcyBub3Qgc2V0CiMgQ09O RklHX0JMS19ERVZfUERDMjAyWFggaXMgbm90IHNldAojIENPTkZJR19QREMyMDJYWF9CVVJTVCBp cyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfT1NCNCBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19E RVZfU0lTNTUxMyBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfU0xDOTBFNjYgaXMgbm90IHNl dAojIENPTkZJR19CTEtfREVWX1RSTTI5MCBpcyBub3Qgc2V0CiMgQ09ORklHX0JMS19ERVZfVklB ODJDWFhYIGlzIG5vdCBzZXQKIyBDT05GSUdfSURFX0NISVBTRVRTIGlzIG5vdCBzZXQKQ09ORklH X0lERURNQV9BVVRPPXkKIyBDT05GSUdfSURFRE1BX0lWQiBpcyBub3Qgc2V0CiMgQ09ORklHX0RN QV9OT05QQ0kgaXMgbm90IHNldApDT05GSUdfQkxLX0RFVl9JREVfTU9ERVM9eQoKIwojIFNDU0kg c3VwcG9ydAojCkNPTkZJR19TQ1NJPXkKQ09ORklHX0JMS19ERVZfU0Q9eQpDT05GSUdfU0RfRVhU UkFfREVWUz00MAojIENPTkZJR19DSFJfREVWX1NUIGlzIG5vdCBzZXQKIyBDT05GSUdfQ0hSX0RF Vl9PU1NUIGlzIG5vdCBzZXQKIyBDT05GSUdfQkxLX0RFVl9TUiBpcyBub3Qgc2V0CiMgQ09ORklH X0NIUl9ERVZfU0cgaXMgbm90IHNldApDT05GSUdfU0NTSV9ERUJVR19RVUVVRVM9eQpDT05GSUdf U0NTSV9NVUxUSV9MVU49eQpDT05GSUdfU0NTSV9DT05TVEFOVFM9eQojIENPTkZJR19TQ1NJX0xP R0dJTkcgaXMgbm90IHNldAoKIwojIFNDU0kgbG93LWxldmVsIGRyaXZlcnMKIwojIENPTkZJR19C TEtfREVWXzNXX1hYWFhfUkFJRCBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfNzAwMEZBU1NUIGlz IG5vdCBzZXQKIyBDT05GSUdfU0NTSV9BQ0FSRCBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfQUhB MTUyWCBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfQUhBMTU0MiBpcyBub3Qgc2V0CiMgQ09ORklH X1NDU0lfQUhBMTc0MCBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfQUlDN1hYWCBpcyBub3Qgc2V0 CiMgQ09ORklHX1NDU0lfQUlDN1hYWF9PTEQgaXMgbm90IHNldAojIENPTkZJR19TQ1NJX0FEVkFO U1lTIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9JTjIwMDAgaXMgbm90IHNldAojIENPTkZJR19T Q1NJX0FNNTNDOTc0IGlzIG5vdCBzZXQKQ09ORklHX1NDU0lfTUVHQVJBSUQ9eQojIENPTkZJR19T Q1NJX0JVU0xPR0lDIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9DUFFGQ1RTIGlzIG5vdCBzZXQK IyBDT05GSUdfU0NTSV9ETVgzMTkxRCBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfRFRDMzI4MCBp cyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfRUFUQSBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfRUFU QV9ETUEgaXMgbm90IHNldAojIENPTkZJR19TQ1NJX0VBVEFfUElPIGlzIG5vdCBzZXQKIyBDT05G SUdfU0NTSV9GVVRVUkVfRE9NQUlOIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9HRFRIIGlzIG5v dCBzZXQKIyBDT05GSUdfU0NTSV9HRU5FUklDX05DUjUzODAgaXMgbm90IHNldAojIENPTkZJR19T Q1NJX0lQUyBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfSU5JVElPIGlzIG5vdCBzZXQKIyBDT05G SUdfU0NTSV9JTklBMTAwIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9QUEEgaXMgbm90IHNldAoj IENPTkZJR19TQ1NJX0lNTSBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfTkNSNTNDNDA2QSBpcyBu b3Qgc2V0CiMgQ09ORklHX1NDU0lfTkNSNTNDN3h4IGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9O Q1I1M0M4WFggaXMgbm90IHNldAojIENPTkZJR19TQ1NJX1NZTTUzQzhYWCBpcyBub3Qgc2V0CiMg Q09ORklHX1NDU0lfUEFTMTYgaXMgbm90IHNldAojIENPTkZJR19TQ1NJX1BDSTIwMDAgaXMgbm90 IHNldAojIENPTkZJR19TQ1NJX1BDSTIyMjBJIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9QU0ky NDBJIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9RTE9HSUNfRkFTIGlzIG5vdCBzZXQKIyBDT05G SUdfU0NTSV9RTE9HSUNfSVNQIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9RTE9HSUNfRkMgaXMg bm90IHNldAojIENPTkZJR19TQ1NJX1FMT0dJQ18xMjgwIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NT SV9TRUFHQVRFIGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9TSU03MTAgaXMgbm90IHNldAojIENP TkZJR19TQ1NJX1NZTTUzQzQxNiBpcyBub3Qgc2V0CiMgQ09ORklHX1NDU0lfREMzOTBUIGlzIG5v dCBzZXQKIyBDT05GSUdfU0NTSV9UMTI4IGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9VMTRfMzRG IGlzIG5vdCBzZXQKIyBDT05GSUdfU0NTSV9VTFRSQVNUT1IgaXMgbm90IHNldAojIENPTkZJR19T Q1NJX0RFQlVHIGlzIG5vdCBzZXQKCiMKIyBJRUVFIDEzOTQgKEZpcmVXaXJlKSBzdXBwb3J0CiMK IyBDT05GSUdfSUVFRTEzOTQgaXMgbm90IHNldAoKIwojIEkyTyBkZXZpY2Ugc3VwcG9ydAojCiMg Q09ORklHX0kyTyBpcyBub3Qgc2V0CiMgQ09ORklHX0kyT19QQ0kgaXMgbm90IHNldAojIENPTkZJ R19JMk9fQkxPQ0sgaXMgbm90IHNldAojIENPTkZJR19JMk9fTEFOIGlzIG5vdCBzZXQKIyBDT05G SUdfSTJPX1NDU0kgaXMgbm90IHNldAojIENPTkZJR19JMk9fUFJPQyBpcyBub3Qgc2V0CgojCiMg TmV0d29yayBkZXZpY2Ugc3VwcG9ydAojCkNPTkZJR19ORVRERVZJQ0VTPXkKCiMKIyBBUkNuZXQg ZGV2aWNlcwojCiMgQ09ORklHX0FSQ05FVCBpcyBub3Qgc2V0CkNPTkZJR19EVU1NWT1tCiMgQ09O RklHX0JPTkRJTkcgaXMgbm90IHNldAojIENPTkZJR19FUVVBTElaRVIgaXMgbm90IHNldAojIENP TkZJR19UVU4gaXMgbm90IHNldAojIENPTkZJR19FVEhFUlRBUCBpcyBub3Qgc2V0CiMgQ09ORklH X05FVF9TQjEwMDAgaXMgbm90IHNldAoKIwojIEV0aGVybmV0ICgxMCBvciAxMDBNYml0KQojCkNP TkZJR19ORVRfRVRIRVJORVQ9eQojIENPTkZJR19ORVRfVkVORE9SXzNDT00gaXMgbm90IHNldAoj IENPTkZJR19MQU5DRSBpcyBub3Qgc2V0CiMgQ09ORklHX05FVF9WRU5ET1JfU01DIGlzIG5vdCBz ZXQKIyBDT05GSUdfTkVUX1ZFTkRPUl9SQUNBTCBpcyBub3Qgc2V0CiMgQ09ORklHX0FUMTcwMCBp cyBub3Qgc2V0CiMgQ09ORklHX0RFUENBIGlzIG5vdCBzZXQKIyBDT05GSUdfSFAxMDAgaXMgbm90 IHNldAojIENPTkZJR19ORVRfSVNBIGlzIG5vdCBzZXQKQ09ORklHX05FVF9QQ0k9eQojIENPTkZJ R19QQ05FVDMyIGlzIG5vdCBzZXQKIyBDT05GSUdfQURBUFRFQ19TVEFSRklSRSBpcyBub3Qgc2V0 CiMgQ09ORklHX0FDMzIwMCBpcyBub3Qgc2V0CiMgQ09ORklHX0FQUklDT1QgaXMgbm90IHNldAoj IENPTkZJR19DUzg5eDAgaXMgbm90IHNldAojIENPTkZJR19UVUxJUCBpcyBub3Qgc2V0CiMgQ09O RklHX0RFNFg1IGlzIG5vdCBzZXQKIyBDT05GSUdfREdSUyBpcyBub3Qgc2V0CiMgQ09ORklHX0RN OTEwMiBpcyBub3Qgc2V0CkNPTkZJR19FRVBSTzEwMD15CiMgQ09ORklHX0VFUFJPMTAwX1BNIGlz IG5vdCBzZXQKIyBDT05GSUdfTE5FMzkwIGlzIG5vdCBzZXQKIyBDT05GSUdfRkVBTE5YIGlzIG5v dCBzZXQKIyBDT05GSUdfTkFUU0VNSSBpcyBub3Qgc2V0CiMgQ09ORklHX05FMktfUENJIGlzIG5v dCBzZXQKIyBDT05GSUdfTkUzMjEwIGlzIG5vdCBzZXQKIyBDT05GSUdfRVMzMjEwIGlzIG5vdCBz ZXQKIyBDT05GSUdfODEzOVRPTyBpcyBub3Qgc2V0CiMgQ09ORklHXzgxMzlUT09fUElPIGlzIG5v dCBzZXQKIyBDT05GSUdfODEzOVRPT19UVU5FX1RXSVNURVIgaXMgbm90IHNldAojIENPTkZJR184 MTM5VE9PXzgxMjkgaXMgbm90IHNldAojIENPTkZJR19TSVM5MDAgaXMgbm90IHNldAojIENPTkZJ R19FUElDMTAwIGlzIG5vdCBzZXQKIyBDT05GSUdfU1VOREFOQ0UgaXMgbm90IHNldAojIENPTkZJ R19UTEFOIGlzIG5vdCBzZXQKIyBDT05GSUdfVklBX1JISU5FIGlzIG5vdCBzZXQKIyBDT05GSUdf V0lOQk9ORF84NDAgaXMgbm90IHNldAojIENPTkZJR19IQVBQWU1FQUwgaXMgbm90IHNldAojIENP TkZJR19ORVRfUE9DS0VUIGlzIG5vdCBzZXQKCiMKIyBFdGhlcm5ldCAoMTAwMCBNYml0KQojCiMg Q09ORklHX0FDRU5JQyBpcyBub3Qgc2V0CiMgQ09ORklHX0hBTUFDSEkgaXMgbm90IHNldAojIENP TkZJR19ZRUxMT1dGSU4gaXMgbm90IHNldAojIENPTkZJR19TSzk4TElOIGlzIG5vdCBzZXQKIyBD T05GSUdfRkRESSBpcyBub3Qgc2V0CiMgQ09ORklHX0hJUFBJIGlzIG5vdCBzZXQKIyBDT05GSUdf UExJUCBpcyBub3Qgc2V0CiMgQ09ORklHX1BQUCBpcyBub3Qgc2V0CiMgQ09ORklHX1NMSVAgaXMg bm90IHNldAoKIwojIFdpcmVsZXNzIExBTiAobm9uLWhhbXJhZGlvKQojCiMgQ09ORklHX05FVF9S QURJTyBpcyBub3Qgc2V0CgojCiMgVG9rZW4gUmluZyBkZXZpY2VzCiMKIyBDT05GSUdfVFIgaXMg bm90IHNldAojIENPTkZJR19ORVRfRkMgaXMgbm90IHNldAojIENPTkZJR19SQ1BDSSBpcyBub3Qg c2V0CiMgQ09ORklHX1NIQVBFUiBpcyBub3Qgc2V0CgojCiMgV2FuIGludGVyZmFjZXMKIwojIENP TkZJR19XQU4gaXMgbm90IHNldAoKIwojIEFtYXRldXIgUmFkaW8gc3VwcG9ydAojCiMgQ09ORklH X0hBTVJBRElPIGlzIG5vdCBzZXQKCiMKIyBJckRBIChpbmZyYXJlZCkgc3VwcG9ydAojCiMgQ09O RklHX0lSREEgaXMgbm90IHNldAoKIwojIElTRE4gc3Vic3lzdGVtCiMKIyBDT05GSUdfSVNETiBp cyBub3Qgc2V0CgojCiMgT2xkIENELVJPTSBkcml2ZXJzIChub3QgU0NTSSwgbm90IElERSkKIwoj IENPTkZJR19DRF9OT19JREVTQ1NJIGlzIG5vdCBzZXQKCiMKIyBJbnB1dCBjb3JlIHN1cHBvcnQK IwojIENPTkZJR19JTlBVVCBpcyBub3Qgc2V0CgojCiMgQ2hhcmFjdGVyIGRldmljZXMKIwpDT05G SUdfVlQ9eQpDT05GSUdfVlRfQ09OU09MRT15CkNPTkZJR19TRVJJQUw9bQojIENPTkZJR19TRVJJ QUxfRVhURU5ERUQgaXMgbm90IHNldAojIENPTkZJR19TRVJJQUxfTk9OU1RBTkRBUkQgaXMgbm90 IHNldApDT05GSUdfVU5JWDk4X1BUWVM9eQpDT05GSUdfVU5JWDk4X1BUWV9DT1VOVD0yNTYKIyBD T05GSUdfUFJJTlRFUiBpcyBub3Qgc2V0CiMgQ09ORklHX1BQREVWIGlzIG5vdCBzZXQKCiMKIyBJ MkMgc3VwcG9ydAojCiMgQ09ORklHX0kyQyBpcyBub3Qgc2V0CgojCiMgTWljZQojCiMgQ09ORklH X0JVU01PVVNFIGlzIG5vdCBzZXQKQ09ORklHX01PVVNFPXkKQ09ORklHX1BTTU9VU0U9eQojIENP TkZJR184MkM3MTBfTU9VU0UgaXMgbm90IHNldAojIENPTkZJR19QQzExMF9QQUQgaXMgbm90IHNl dAoKIwojIEpveXN0aWNrcwojCiMgQ09ORklHX0pPWVNUSUNLIGlzIG5vdCBzZXQKIyBDT05GSUdf UUlDMDJfVEFQRSBpcyBub3Qgc2V0CgojCiMgV2F0Y2hkb2cgQ2FyZHMKIwojIENPTkZJR19XQVRD SERPRyBpcyBub3Qgc2V0CiMgQ09ORklHX0lOVEVMX1JORyBpcyBub3Qgc2V0CiMgQ09ORklHX05W UkFNIGlzIG5vdCBzZXQKIyBDT05GSUdfUlRDIGlzIG5vdCBzZXQKIyBDT05GSUdfRFRMSyBpcyBu b3Qgc2V0CiMgQ09ORklHX1IzOTY0IGlzIG5vdCBzZXQKIyBDT05GSUdfQVBQTElDT00gaXMgbm90 IHNldAoKIwojIEZ0YXBlLCB0aGUgZmxvcHB5IHRhcGUgZGV2aWNlIGRyaXZlcgojCiMgQ09ORklH X0ZUQVBFIGlzIG5vdCBzZXQKIyBDT05GSUdfQUdQIGlzIG5vdCBzZXQKIyBDT05GSUdfRFJNIGlz IG5vdCBzZXQKCiMKIyBNdWx0aW1lZGlhIGRldmljZXMKIwojIENPTkZJR19WSURFT19ERVYgaXMg bm90IHNldAoKIwojIEZpbGUgc3lzdGVtcwojCkNPTkZJR19RVU9UQT15CkNPTkZJR19GU19QT1NJ WF9BQ0w9eQojIENPTkZJR19BVVRPRlNfRlMgaXMgbm90IHNldApDT05GSUdfQVVUT0ZTNF9GUz15 CkNPTkZJR19SRUlTRVJGU19GUz15CiMgQ09ORklHX1JFSVNFUkZTX0NIRUNLIGlzIG5vdCBzZXQK IyBDT05GSUdfQURGU19GUyBpcyBub3Qgc2V0CiMgQ09ORklHX0FERlNfRlNfUlcgaXMgbm90IHNl dAojIENPTkZJR19BRkZTX0ZTIGlzIG5vdCBzZXQKIyBDT05GSUdfSEZTX0ZTIGlzIG5vdCBzZXQK IyBDT05GSUdfQkZTX0ZTIGlzIG5vdCBzZXQKIyBDT05GSUdfRkFUX0ZTIGlzIG5vdCBzZXQKIyBD T05GSUdfTVNET1NfRlMgaXMgbm90IHNldAojIENPTkZJR19VTVNET1NfRlMgaXMgbm90IHNldAoj IENPTkZJR19WRkFUX0ZTIGlzIG5vdCBzZXQKIyBDT05GSUdfRUZTX0ZTIGlzIG5vdCBzZXQKIyBD T05GSUdfSkZGU19GUyBpcyBub3Qgc2V0CiMgQ09ORklHX0NSQU1GUyBpcyBub3Qgc2V0CkNPTkZJ R19UTVBGUz15CiMgQ09ORklHX1JBTUZTIGlzIG5vdCBzZXQKQ09ORklHX0lTTzk2NjBfRlM9bQpD T05GSUdfSk9MSUVUPXkKQ09ORklHX01JTklYX0ZTPW0KIyBDT05GSUdfVlhGU19GUyBpcyBub3Qg c2V0CiMgQ09ORklHX05URlNfRlMgaXMgbm90IHNldAojIENPTkZJR19OVEZTX1JXIGlzIG5vdCBz ZXQKIyBDT05GSUdfSFBGU19GUyBpcyBub3Qgc2V0CkNPTkZJR19QUk9DX0ZTPXkKIyBDT05GSUdf REVWRlNfRlMgaXMgbm90IHNldAojIENPTkZJR19ERVZGU19NT1VOVCBpcyBub3Qgc2V0CiMgQ09O RklHX0RFVkZTX0RFQlVHIGlzIG5vdCBzZXQKQ09ORklHX0RFVlBUU19GUz15CiMgQ09ORklHX1FO WDRGU19GUyBpcyBub3Qgc2V0CiMgQ09ORklHX1FOWDRGU19SVyBpcyBub3Qgc2V0CiMgQ09ORklH X1JPTUZTX0ZTIGlzIG5vdCBzZXQKQ09ORklHX0VYVDJfRlM9eQojIENPTkZJR19TWVNWX0ZTIGlz IG5vdCBzZXQKIyBDT05GSUdfU1lTVl9GU19XUklURSBpcyBub3Qgc2V0CiMgQ09ORklHX1VERl9G UyBpcyBub3Qgc2V0CiMgQ09ORklHX1VERl9SVyBpcyBub3Qgc2V0CiMgQ09ORklHX1VGU19GUyBp cyBub3Qgc2V0CiMgQ09ORklHX1VGU19GU19XUklURSBpcyBub3Qgc2V0CkNPTkZJR19QQUdFX0JV Rj15CkNPTkZJR19YRlNfRlM9eQpDT05GSUdfSEFWRV9BVFRSQ1RMPXkKQ09ORklHX1hGU19ETUFQ ST15CkNPTkZJR19YRlNfUVVPVEE9eQoKIwojIE5ldHdvcmsgRmlsZSBTeXN0ZW1zCiMKIyBDT05G SUdfQ09EQV9GUyBpcyBub3Qgc2V0CkNPTkZJR19ORlNfRlM9bQpDT05GSUdfTkZTX1YzPXkKIyBD T05GSUdfUk9PVF9ORlMgaXMgbm90IHNldApDT05GSUdfTkZTRD1tCkNPTkZJR19ORlNEX1YzPXkK Q09ORklHX1NVTlJQQz1tCkNPTkZJR19MT0NLRD1tCkNPTkZJR19MT0NLRF9WND15CkNPTkZJR19T TUJfRlM9bQpDT05GSUdfU01CX05MU19ERUZBVUxUPXkKQ09ORklHX1NNQl9OTFNfUkVNT1RFPSJj cDQzNyIKIyBDT05GSUdfTkNQX0ZTIGlzIG5vdCBzZXQKIyBDT05GSUdfTkNQRlNfUEFDS0VUX1NJ R05JTkcgaXMgbm90IHNldAojIENPTkZJR19OQ1BGU19JT0NUTF9MT0NLSU5HIGlzIG5vdCBzZXQK IyBDT05GSUdfTkNQRlNfU1RST05HIGlzIG5vdCBzZXQKIyBDT05GSUdfTkNQRlNfTkZTX05TIGlz IG5vdCBzZXQKIyBDT05GSUdfTkNQRlNfT1MyX05TIGlzIG5vdCBzZXQKIyBDT05GSUdfTkNQRlNf U01BTExET1MgaXMgbm90IHNldAojIENPTkZJR19OQ1BGU19OTFMgaXMgbm90IHNldAojIENPTkZJ R19OQ1BGU19FWFRSQVMgaXMgbm90IHNldAoKIwojIFBhcnRpdGlvbiBUeXBlcwojCiMgQ09ORklH X1BBUlRJVElPTl9BRFZBTkNFRCBpcyBub3Qgc2V0CkNPTkZJR19NU0RPU19QQVJUSVRJT049eQpD T05GSUdfU01CX05MUz15CkNPTkZJR19OTFM9eQoKIwojIE5hdGl2ZSBMYW5ndWFnZSBTdXBwb3J0 CiMKQ09ORklHX05MU19ERUZBVUxUPSJpc284ODU5LTEiCkNPTkZJR19OTFNfQ09ERVBBR0VfNDM3 PW0KIyBDT05GSUdfTkxTX0NPREVQQUdFXzczNyBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19DT0RF UEFHRV83NzUgaXMgbm90IHNldApDT05GSUdfTkxTX0NPREVQQUdFXzg1MD1tCiMgQ09ORklHX05M U19DT0RFUEFHRV84NTIgaXMgbm90IHNldAojIENPTkZJR19OTFNfQ09ERVBBR0VfODU1IGlzIG5v dCBzZXQKIyBDT05GSUdfTkxTX0NPREVQQUdFXzg1NyBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19D T0RFUEFHRV84NjAgaXMgbm90IHNldAojIENPTkZJR19OTFNfQ09ERVBBR0VfODYxIGlzIG5vdCBz ZXQKIyBDT05GSUdfTkxTX0NPREVQQUdFXzg2MiBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19DT0RF UEFHRV84NjMgaXMgbm90IHNldAojIENPTkZJR19OTFNfQ09ERVBBR0VfODY0IGlzIG5vdCBzZXQK IyBDT05GSUdfTkxTX0NPREVQQUdFXzg2NSBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19DT0RFUEFH RV84NjYgaXMgbm90IHNldAojIENPTkZJR19OTFNfQ09ERVBBR0VfODY5IGlzIG5vdCBzZXQKIyBD T05GSUdfTkxTX0NPREVQQUdFXzkzNiBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19DT0RFUEFHRV85 NTAgaXMgbm90IHNldAojIENPTkZJR19OTFNfQ09ERVBBR0VfOTMyIGlzIG5vdCBzZXQKIyBDT05G SUdfTkxTX0NPREVQQUdFXzk0OSBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19DT0RFUEFHRV84NzQg aXMgbm90IHNldAojIENPTkZJR19OTFNfSVNPODg1OV84IGlzIG5vdCBzZXQKIyBDT05GSUdfTkxT X0NPREVQQUdFXzEyNTEgaXMgbm90IHNldApDT05GSUdfTkxTX0lTTzg4NTlfMT1tCiMgQ09ORklH X05MU19JU084ODU5XzIgaXMgbm90IHNldAojIENPTkZJR19OTFNfSVNPODg1OV8zIGlzIG5vdCBz ZXQKIyBDT05GSUdfTkxTX0lTTzg4NTlfNCBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19JU084ODU5 XzUgaXMgbm90IHNldAojIENPTkZJR19OTFNfSVNPODg1OV82IGlzIG5vdCBzZXQKIyBDT05GSUdf TkxTX0lTTzg4NTlfNyBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19JU084ODU5XzkgaXMgbm90IHNl dAojIENPTkZJR19OTFNfSVNPODg1OV8xMyBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19JU084ODU5 XzE0IGlzIG5vdCBzZXQKQ09ORklHX05MU19JU084ODU5XzE1PW0KIyBDT05GSUdfTkxTX0tPSThf UiBpcyBub3Qgc2V0CiMgQ09ORklHX05MU19LT0k4X1UgaXMgbm90IHNldAojIENPTkZJR19OTFNf VVRGOCBpcyBub3Qgc2V0CgojCiMgQ29uc29sZSBkcml2ZXJzCiMKQ09ORklHX1ZHQV9DT05TT0xF PXkKIyBDT05GSUdfVklERU9fU0VMRUNUIGlzIG5vdCBzZXQKIyBDT05GSUdfTURBX0NPTlNPTEUg aXMgbm90IHNldAoKIwojIEZyYW1lLWJ1ZmZlciBzdXBwb3J0CiMKIyBDT05GSUdfRkIgaXMgbm90 IHNldAoKIwojIFNvdW5kCiMKIyBDT05GSUdfU09VTkQgaXMgbm90IHNldAoKIwojIFVTQiBzdXBw b3J0CiMKQ09ORklHX1VTQj1tCiMgQ09ORklHX1VTQl9ERUJVRyBpcyBub3Qgc2V0CiMgQ09ORklH X1VTQl9ERVZJQ0VGUyBpcyBub3Qgc2V0CiMgQ09ORklHX1VTQl9CQU5EV0lEVEggaXMgbm90IHNl dApDT05GSUdfVVNCX1VIQ0lfQUxUPW0KQ09ORklHX1VTQl9PSENJPW0KIyBDT05GSUdfVVNCX0FV RElPIGlzIG5vdCBzZXQKIyBDT05GSUdfVVNCX0JMVUVUT09USCBpcyBub3Qgc2V0CkNPTkZJR19V U0JfU1RPUkFHRT1tCiMgQ09ORklHX1VTQl9TVE9SQUdFX0RFQlVHIGlzIG5vdCBzZXQKIyBDT05G SUdfVVNCX1NUT1JBR0VfRlJFRUNPTSBpcyBub3Qgc2V0CiMgQ09ORklHX1VTQl9TVE9SQUdFX0RQ Q00gaXMgbm90IHNldAojIENPTkZJR19VU0JfQUNNIGlzIG5vdCBzZXQKIyBDT05GSUdfVVNCX1BS SU5URVIgaXMgbm90IHNldAojIENPTkZJR19VU0JfREMyWFggaXMgbm90IHNldAojIENPTkZJR19V U0JfTURDODAwIGlzIG5vdCBzZXQKIyBDT05GSUdfVVNCX1NDQU5ORVIgaXMgbm90IHNldAojIENP TkZJR19VU0JfTUlDUk9URUsgaXMgbm90IHNldAojIENPTkZJR19VU0JfSUJNQ0FNIGlzIG5vdCBz ZXQKIyBDT05GSUdfVVNCX09WNTExIGlzIG5vdCBzZXQKIyBDT05GSUdfVVNCX1BXQyBpcyBub3Qg c2V0CiMgQ09ORklHX1VTQl9EU0JSIGlzIG5vdCBzZXQKIyBDT05GSUdfVVNCX0RBQlVTQiBpcyBu b3Qgc2V0CiMgQ09ORklHX1VTQl9QTFVTQiBpcyBub3Qgc2V0CiMgQ09ORklHX1VTQl9QRUdBU1VT IGlzIG5vdCBzZXQKIyBDT05GSUdfVVNCX05FVDEwODAgaXMgbm90IHNldAojIENPTkZJR19VU0Jf VVNTNzIwIGlzIG5vdCBzZXQKCiMKIyBVU0IgU2VyaWFsIENvbnZlcnRlciBzdXBwb3J0CiMKIyBD T05GSUdfVVNCX1NFUklBTCBpcyBub3Qgc2V0CiMgQ09ORklHX1VTQl9SSU81MDAgaXMgbm90IHNl dAoKIwojIEtlcm5lbCBoYWNraW5nCiMKIyBDT05GSUdfTUFHSUNfU1lTUlEgaXMgbm90IHNldAoj IENPTkZJR19LREIgaXMgbm90IHNldAojIENPTkZJR19LQUxMU1lNUyBpcyBub3Qgc2V0CiMgQ09O RklHX0ZSQU1FX1BPSU5URVIgaXMgbm90IHNldAo= --------------Boundary-00=_24NM42YQ99BGNYRYE30D-- From owner-linux-xfs@oss.sgi.com Tue Jul 17 10:29:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HHTs724915 for linux-xfs-outgoing; Tue, 17 Jul 2001 10:29:54 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HHTqV24896 for ; Tue, 17 Jul 2001 10:29:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAA08078 for ; Tue, 17 Jul 2001 10:29:36 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2449991 for ; Tue, 17 Jul 2001 12:28:35 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA82667 for ; Tue, 17 Jul 2001 12:28:34 -0500 (CDT) Subject: Re: xfs kernel problem From: Eric Sandeen Cc: linux-xfs@oss.sgi.com In-Reply-To: <200107171657.f6HGvdV24138@oss.sgi.com> References: <200107171657.f6HGvdV24138@oss.sgi.com> Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/0.10.99 (Preview Release) Date: 17 Jul 2001 12:28:38 -0500 Message-Id: <995390918.8982.6.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6HHTqV24897 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 17 Jul 2001 18:57:38 +0200, Krückel Oliver wrote: > Linux SuSE-7.1 with servarel patches from the officel SuSE web-server > gcc: version 2.95.2 19991024 (release) Can you try compiling with a 2.91.66 gcc version? This is the first thing I'd try, newer compilers still have not been producing consistently good code. > if i reboot the server with the xfs kernel and the server coms up there are > sum files and executables witch i can't access ore execute, > > sum examples: the programms find, make, ... or file hosts, ... > > if i reboot the server again, there are much more files that can't access or > execute, there are alwais other executebles and files by every test, Can you give any more information about "can't access" - do they not show up in the directory listing, do they seem to contain wrong data... ? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Tue Jul 17 10:38:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HHcax25169 for linux-xfs-outgoing; Tue, 17 Jul 2001 10:38:36 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HHcXV25150 for ; Tue, 17 Jul 2001 10:38:33 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6HHdFG29187 for ; Tue, 17 Jul 2001 20:39:16 +0300 Date: Tue, 17 Jul 2001 20:38:28 +0300 (EEST) From: Jani Jaakkola To: Subject: Re: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem In-Reply-To: <200107171553.f6HFrfZ01677@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 17 Jul 2001, Steve Lord wrote: > > Could you possibly try the cvs tree, Linus was still working deadlocks > out of the memory allocation/reclaim end of things up until 2.4.7-pre2. > XFS and ext2 will almost certainly push things in different directions. OK I'll try it.. Right, it has now been running longer than ever before without a lockup. However, the performance is very bad. But it just might be caused by the simultaneous RAID resync I am doing at the same time. I'll get back to this after the resync is done (or the machine has crashed). > Another issue here is that you may actually be creating inode numbers with > greated than 32 bits in them with a filesystem this size. If you run > xfs_growfs -n on the mount point of the filesystem and run the attached > perl script with the following arguments it will tell you how many bits > your inodes can consume. > You can play with numbers to make the number of bits <= 32, increasing > the inode size will be the thing which does it for you, also if you > did not end up with 4GB allocation groups you should attempt to get > them setup that way. Unfortunately this means mkfs to fix. > > I do have some plans to make this issue go away for large filesystems, but > you beat me to it! I had inode size exactly 32 bits and 4GB allocation groups, but I still recreated the file system (no problem, since I'm still only testing the sw and hw): # /sbin/mkfs.xfs -f -Lfs -dagsize=4g -isize=512 /dev/md0 meta-data=/dev/md0 isize=512 agcount=254, agsize=1048576 blks data = bsize=4096 blocks=265939776, imaxpct=25 = sunit=1 swidth=6 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=32463 realtime =none extsz=24576 blocks=0, rtextents=0 Thanks for the advice! - Jani From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:07:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HI7oQ25669 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:07:50 -0700 Received: from webmail.chimesnet.com (postfix@mail001.level3.chc-chimes.com [63.211.16.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HI7mV25650 for ; Tue, 17 Jul 2001 11:07:48 -0700 Received: from orbis.internal.chc-chimes.com (pixnat.chc-chimes.com [216.28.46.20]) by webmail.chimesnet.com (Postfix) with ESMTP id 853B7CAC507 for ; Tue, 17 Jul 2001 10:58:28 -0400 (EDT) Received: from tcarroll by orbis.internal.chc-chimes.com with local (Exim 3.22 #1 (Debian)) id 15MWHb-00045b-00 for ; Tue, 17 Jul 2001 10:57:07 -0400 Date: Tue, 17 Jul 2001 10:57:07 -0400 To: linux-xfs Subject: LVM snapshot and XFS Message-ID: <20010717105707.A15638@chimesnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i From: Tom Carroll Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello all, I did some searching around and I could not find the answer to this problem: I created a snapshot of an XFS parition under LVM. lvcreate -L1G -s -n bkup /dev/vol0/home Then I attempted to mount the snapshot: mount -oro /dev/vol0/bkup /mnt mount: wrong fs type, bad option, bad superblock on /dev/vol0/bkup, or too many mounted file systems klog states: XFS: Filesystem has duplicate UUID - can't mount When I attempt to change the UUID: xfs_db -c'uuid generate' /dev/vol0/bkup xfs_db: cannot open /dev/vol0/bkup: Permission denied Even though I am root. Will anyone give a helping hand? Thanks in advance -- Tom Carroll email: tcarroll@chimesnet.com pgp: mailto:pgp@chimesnet.com?subject=GET%20tcarroll@chimesnet.com From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:12:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HICb525908 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:12:37 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HICZV25888 for ; Tue, 17 Jul 2001 11:12:35 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA15672 for ; Tue, 17 Jul 2001 11:12:25 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2451109; Tue, 17 Jul 2001 13:11:18 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA34101; Tue, 17 Jul 2001 13:11:17 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HICRZ02249; Tue, 17 Jul 2001 13:12:27 -0500 Message-Id: <200107171812.f6HICRZ02249@jen.americas.sgi.com> To: Tom Carroll cc: linux-xfs Subject: Re: LVM snapshot and XFS References: <20010717105707.A15638@chimesnet.com> Comments: In-reply-to Tom Carroll message dated "Tue, 17 Jul 2001 10:57:07 -0400." Date: Tue, 17 Jul 2001 13:12:27 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hello all, > > I did some searching around and I could not find the answer to this problem: > > I created a snapshot of an XFS parition under LVM. > > lvcreate -L1G -s -n bkup /dev/vol0/home > > Then I attempted to mount the snapshot: > > mount -oro /dev/vol0/bkup /mnt > mount: wrong fs type, bad option, bad superblock on /dev/vol0/bkup, > or too many mounted file systems > > klog states: > XFS: Filesystem has duplicate UUID - can't mount > > When I attempt to change the UUID: > xfs_db -c'uuid generate' /dev/vol0/bkup > > xfs_db: cannot open /dev/vol0/bkup: Permission denied > > Even though I am root. > > Will anyone give a helping hand? Thanks in advance > > -- > Tom Carroll email: tcarroll@chimesnet.com > pgp: mailto:pgp@chimesnet.com?subject=GET%20t > carroll@chimesnet.com If you have a recent cvs kernel then there is a nouuid mount option which will let it mount without changing the uuid. Otherwise you need to make the backup lvm volume writable first - someone else will have to tell you how to do that. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:13:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HID4P26003 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:13:04 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HID2V25984 for ; Tue, 17 Jul 2001 11:13:03 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 545911E8CB; Tue, 17 Jul 2001 20:12:57 +0200 (MEST) Date: Tue, 17 Jul 2001 20:12:56 +0200 From: Andi Kleen To: Tom Carroll Cc: linux-xfs Subject: Re: LVM snapshot and XFS Message-ID: <20010717201256.A25801@gruyere.muc.suse.de> References: <20010717105707.A15638@chimesnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010717105707.A15638@chimesnet.com>; from tcarroll@chimesnet.com on Tue, Jul 17, 2001 at 10:57:07AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 17, 2001 at 10:57:07AM -0400, Tom Carroll wrote: > Will anyone give a helping hand? Thanks in advance If you're running a recent kernel (1.0.1 or newer) then you can use the nouuid mount option to prevent the uuid check. -Andi From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:14:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIE4k26130 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:14:04 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIE2V26111 for ; Tue, 17 Jul 2001 11:14:02 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id UAA31117; Tue, 17 Jul 2001 20:14:00 +0200 Date: Tue, 17 Jul 2001 20:13:59 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Tom Carroll Cc: linux-xfs Subject: Re: LVM snapshot and XFS Message-ID: <20010717201359.C29034@vestdata.no> References: <20010717105707.A15638@chimesnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <20010717105707.A15638@chimesnet.com>; from Tom Carroll on Tue, Jul 17, 2001 at 10:57:07AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 17, 2001 at 10:57:07AM -0400, Tom Carroll wrote: > Hello all, > > I did some searching around and I could not find the answer to this problem: > > I created a snapshot of an XFS parition under LVM. > > lvcreate -L1G -s -n bkup /dev/vol0/home > > Then I attempted to mount the snapshot: > > mount -oro /dev/vol0/bkup /mnt > mount: wrong fs type, bad option, bad superblock on /dev/vol0/bkup, > or too many mounted file systems > > klog states: > XFS: Filesystem has duplicate UUID - can't mount > > When I attempt to change the UUID: > xfs_db -c'uuid generate' /dev/vol0/bkup > > xfs_db: cannot open /dev/vol0/bkup: Permission denied > > Even though I am root. > > Will anyone give a helping hand? Thanks in advance The snapshot device is read-only, so you can't change the UUID. I believe there is a kernel patch floating around to allow you to mount multiple filesystems with the same UUID. You'll then run into the next problem: The snapshot is of an unclean XFS filesystem, and since the device is readonly you can't reply the journal or run fsck. For now the only way around this is to unmount your filesystem when taking the snapshot. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:19:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIJPA26470 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:19:25 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIJOV26451 for ; Tue, 17 Jul 2001 11:19:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA16685 for ; Tue, 17 Jul 2001 11:19:14 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2454577; Tue, 17 Jul 2001 13:18:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA08537; Tue, 17 Jul 2001 13:18:05 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HIJFc02271; Tue, 17 Jul 2001 13:19:15 -0500 Message-Id: <200107171819.f6HIJFc02271@jen.americas.sgi.com> To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= cc: Tom Carroll , linux-xfs Subject: Re: LVM snapshot and XFS References: <20010717105707.A15638@chimesnet.com> <20010717201359.C29034@vestdata.no> Comments: In-reply-to =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= message dated "Tue, 17 Jul 2001 20:13:59 +0200." Date: Tue, 17 Jul 2001 13:19:15 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > The snapshot device is read-only, so you can't change the UUID. > > I believe there is a kernel patch floating around to allow you to mount > multiple filesystems with the same UUID. > > You'll then run into the next problem: > The snapshot is of an unclean XFS filesystem, and since the device is > readonly you can't reply the journal or run fsck. For now the only way > around this is to unmount your filesystem when taking the snapshot. > It should be a clean filesystem, providing you use either the xfs_freeze command before the snapshot, or apply the lvm patch to have it call the filesystem to sync out to disk before the snapshot. Steve > > > -- > Ragnar Kjorstad > Big Storage From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:29:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HITlZ26739 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:29:47 -0700 Received: from roc-24-169-102-121.rochester.rr.com (roc-24-169-102-121.rochester.rr.com [24.169.102.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HITjV26720 for ; Tue, 17 Jul 2001 11:29:45 -0700 Received: from localhost ([127.0.0.1] helo=tiny) by roc-24-169-102-121.rochester.rr.com with esmtp (Exim 3.16 #4) id 15MZYH-0004cJ-00; Tue, 17 Jul 2001 14:26:34 -0400 Date: Tue, 17 Jul 2001 14:26:31 -0400 From: Chris Mason To: Xuan Baldauf , Nikita Danilov cc: Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <647920000.995394391@tiny> In-Reply-To: <3B534B74.BDE19961@baldauf.org> X-Mailer: Mulberry/2.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Monday, July 16, 2001 10:15:48 PM +0200 Xuan Baldauf wrote: [ nfs, benchmarks, reiserfs generation number support ] >> >> > P.S.: Hans, how do you prevent object_id|inode reusing? Using >> > mount_id+generation counter per mount? >> >> There is generation counter stored persistently with super-block, >> incremented on each inode deletion. > > Is the superblock always logged on inode-deletion for other reasons than > the generation counter? If not, would the above method be more efficient, > because it does not require logging superblocks? inode deletion requires updating the oid map, which lives in the superblock, so the super is always logged during an inode delete. deletion/creation usually also involve bitmap changes, which change the free block count, which ends up logging the super as well. -chris From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:33:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIXGx26935 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:33:16 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIXDV26916 for ; Tue, 17 Jul 2001 11:33:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA02206 for ; Tue, 17 Jul 2001 11:30:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2454781; Tue, 17 Jul 2001 13:29:28 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA97436; Tue, 17 Jul 2001 13:29:28 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HIUc502345; Tue, 17 Jul 2001 13:30:38 -0500 Message-Id: <200107171830.f6HIUc502345@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jani Jaakkola cc: linux-xfs@oss.sgi.com Subject: Re: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem In-Reply-To: Message from Jani Jaakkola of "Tue, 17 Jul 2001 20:38:28 +0300." Date: Tue, 17 Jul 2001 13:30:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Tue, 17 Jul 2001, Steve Lord wrote: > > > > > Could you possibly try the cvs tree, Linus was still working deadlocks > > out of the memory allocation/reclaim end of things up until 2.4.7-pre2. > > XFS and ext2 will almost certainly push things in different directions. > > OK I'll try it.. > > Right, it has now been running longer than ever before without a lockup. > However, the performance is very bad. But it just might be caused by the > simultaneous RAID resync I am doing at the same time. I'll get back to > this after the resync is done (or the machine has crashed). Yes, the resync will crucify performance until it is complete. I think you can control the rate it runs at - I would get it out of the way as soon as possible, I think it has nasty cache invalidation effects when running with XFS. Steve > > > Another issue here is that you may actually be creating inode numbers with > > greated than 32 bits in them with a filesystem this size. If you run > > xfs_growfs -n on the mount point of the filesystem and run the attached > > perl script with the following arguments it will tell you how many bits > > your inodes can consume. > > > > > You can play with numbers to make the number of bits <= 32, increasing > > the inode size will be the thing which does it for you, also if you > > did not end up with 4GB allocation groups you should attempt to get > > them setup that way. Unfortunately this means mkfs to fix. > > > > I do have some plans to make this issue go away for large filesystems, but > > you beat me to it! > > I had inode size exactly 32 bits and 4GB allocation groups, but I still > recreated the file system (no problem, since I'm still only testing the > sw and hw): > > # /sbin/mkfs.xfs -f -Lfs -dagsize=4g -isize=512 /dev/md0 > meta-data=/dev/md0 isize=512 agcount=254, agsize=1048576 > blks > data = bsize=4096 blocks=265939776, imaxpct=25 > = sunit=1 swidth=6 blks, unwritten=0 > naming =version 2 bsize=4096 > log =internal log bsize=4096 blocks=32463 > realtime =none extsz=24576 blocks=0, rtextents=0 > > Thanks for the advice! > > - Jani From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:39:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIdQA27210 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:39:26 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIdOV27191 for ; Tue, 17 Jul 2001 11:39:24 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJW3F>; Tue, 17 Jul 2001 13:39:00 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643435@AUSMAIL> From: "Gonyou, Austin" To: "'Simon Matter'" , Florin Andrei Cc: linux-xfs@oss.sgi.com Subject: RE: LVM on Linux Date: Tue, 17 Jul 2001 13:38:59 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6HIdPV27192 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk That is referred to as hardware RAID because most RAID card devices use an ASIC programmed to do ONLY that. Think of it, if you like, as a RAID appliance. :) -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Simon Matter [mailto:simon.matter@ch.sauter-bc.com] > Sent: Tuesday, July 17, 2001 1:38 AM > To: Florin Andrei > Cc: linux-xfs@oss.sgi.com > Subject: Re: LVM on Linux > > > Florin Andrei schrieb: > > > > On 16 Jul 2001 22:54:18 +0200, Ragnar Kjørstad wrote: > > > > > > Even for highend RAID's there are lots of reasons to use LVM/EVMS: > > > * load balancing across multiple scsi-channels (not > implemented yet) > > > * Dynamic partitioning > > > * Volumes spanning multiple physical devices > > > * snapshotting. > > > > > > Basicly handling this is software adds a lot of flexibility. > > > > But how about performance? > > Aren't these things supposed to be handled by the hardware? > > It's the same thing as for soft vs hard RAID. Hard should be faster > > I have never seen a true hardware RAID. I mean every RAID I saw > was having its own CPU (be it i960 or any newer generation of > microprocessor or microcontroller from different vendors) and > small operating system (firmware). So in fact it's always > software but not running on you main CPU. However > mainstream CPU's became powerful and very cheap so it's not > a bad idea to let this CPU work for your RAID funtionality. In > fact software RAID on modern CPU's has exiting performance. > > > (but, yeah, soft is easier to play with). > > Another good reason to use the really soft version. > > > > > -- > > Florin Andrei > > From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:46:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIktO27400 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:46:55 -0700 Received: from roc-24-169-102-121.rochester.rr.com (roc-24-169-102-121.rochester.rr.com [24.169.102.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIkqV27380 for ; Tue, 17 Jul 2001 11:46:52 -0700 Received: from localhost ([127.0.0.1] helo=tiny) by roc-24-169-102-121.rochester.rr.com with esmtp (Exim 3.16 #4) id 15MZrF-0004es-00; Tue, 17 Jul 2001 14:46:09 -0400 Date: Tue, 17 Jul 2001 14:46:08 -0400 From: Chris Mason To: Xuan Baldauf , Seth Mos , "Peter J. Braam" cc: Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks Message-ID: <653070000.995395568@tiny> In-Reply-To: <3B507259.4436853E@baldauf.org> X-Mailer: Mulberry/2.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Saturday, July 14, 2001 06:24:57 PM +0200 Xuan Baldauf wrote: [ NFS is the coolest network filesystem EVER! ] > Are there alternatives? Intermezzo does not seem to be developed anymore. > Is Coda usable? > intermezzo is still under development, and they are doing cool things for integration with the various journaled filesystems. The web pages don't say much about the current status, but the mailing list archive shows recent traffic. Looks like their CVS server is your best bet for getting recent stuff (www.inter-mezzo.org, not to be confused with www.intermezzo.org, which seems dedicated to finding housing in amsterdam ;-) -chris From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:47:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIlJZ27427 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:47:19 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIlHV27408 for ; Tue, 17 Jul 2001 11:47:17 -0700 Received: from [10.109.21.30] (IDENT:jjaakkol@adsl-2-5.cs.helsinki.fi [128.214.204.234]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6HIltG03020 for ; Tue, 17 Jul 2001 21:48:00 +0300 Date: Tue, 17 Jul 2001 21:47:09 +0300 (EEST) From: Jani Jaakkola To: Subject: Re: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem In-Reply-To: <200107171830.f6HIUc502345@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 17 Jul 2001, Steve Lord wrote: > > Right, it has now been running longer than ever before without a lockup. > > However, the performance is very bad. But it just might be caused by the > > simultaneous RAID resync I am doing at the same time. I'll get back to > > this after the resync is done (or the machine has crashed). > > Yes, the resync will crucify performance until it is complete. I think you > can control the rate it runs at - I would get it out of the way as soon > as possible, I think it has nasty cache invalidation effects when running > with XFS. Does that mean, that XFS could have problems with SW RAID rebuild after a disk failure? After I get things running, I'm going to test what happens when I remove a disk from hotswap and plug it back again in live system. I need to have that working before putting the system to use (even if it requires to spend some $$ on some RAID hardware). - Jani From owner-linux-xfs@oss.sgi.com Tue Jul 17 11:57:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HIvcJ27875 for linux-xfs-outgoing; Tue, 17 Jul 2001 11:57:38 -0700 Received: from cairn-gorm.cragtech.com (mail.connex.com [216.100.236.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HIvYV27853 for ; Tue, 17 Jul 2001 11:57:34 -0700 Received: by cairn-gorm.cragtech.com with Internet Mail Service (5.5.2650.21) id ; Tue, 17 Jul 2001 11:55:00 -0700 Message-ID: From: Dale Stephenson To: "'Tom Carroll '" Cc: "'linux-xfs '" Subject: RE: LVM snapshot and XFS Date: Tue, 17 Jul 2001 11:54:57 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C10EF1.F910F5B0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C10EF1.F910F5B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Here's two patches to allow writable snapshots. One is against the lvm = code in the kernel. I haven't updated it to apply against 1.0.1 yet, so you = may have to tweak it. The other is to allow the lvchange LVM tool to set snapshots to read/write (they are created read-only). Once you've changed it to read/write you can do replays and change the = uuid, though a combination of xfs_freeze and nouuid mount should be cleaner. I believe that the next generation of LVM (after 1.0 is finally out) = will have writeable snapshots and also file system sync before snapshot. Dale Stephenson steph@connex.com -----Original Message----- From: Ragnar Kj=F8rstad To: Tom Carroll Cc: linux-xfs Sent: 7/17/01 11:13 AM Subject: Re: LVM snapshot and XFS On Tue, Jul 17, 2001 at 10:57:07AM -0400, Tom Carroll wrote: > Hello all, >=20 > I did some searching around and I could not find the answer to this problem: >=20 > I created a snapshot of an XFS parition under LVM. >=20 > lvcreate -L1G -s -n bkup /dev/vol0/home >=20 > Then I attempted to mount the snapshot: >=20 > mount -oro /dev/vol0/bkup /mnt > mount: wrong fs type, bad option, bad superblock on /dev/vol0/bkup, > or too many mounted file systems >=20 > klog states: > XFS: Filesystem has duplicate UUID - can't mount >=20 > When I attempt to change the UUID: > xfs_db -c'uuid generate' /dev/vol0/bkup >=20 > xfs_db: cannot open /dev/vol0/bkup: Permission denied >=20 > Even though I am root. =20 >=20 > Will anyone give a helping hand? Thanks in advance The snapshot device is read-only, so you can't change the UUID. I believe there is a kernel patch floating around to allow you to mount multiple filesystems with the same UUID. You'll then run into the next problem: The snapshot is of an unclean XFS filesystem, and since the device is readonly you can't reply the journal or run fsck. For now the only way around this is to unmount your filesystem when taking the snapshot. --=20 Ragnar Kjorstad Big Storage ------_=_NextPart_000_01C10EF1.F910F5B0 Content-Type: application/octet-stream; name="lvm_0.9.djs.lvchange.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="lvm_0.9.djs.lvchange.patch" --- LVM_0_9/tools/lvchange.c.orig Thu Dec 14 11:29:30 2000=0A= +++ LVM_0_9/tools/lvchange.c Thu Dec 14 11:36:16 2000=0A= @@ -329,7 +330,8 @@=0A= continue;=0A= }=0A= =0A= - if ( lv->lv_access & LV_SNAPSHOT) {=0A= + if ( ( lv->lv_access & LV_SNAPSHOT) &&=0A= + ( (opt_C) || (opt_a) || (opt_r))) {=0A= fprintf ( stderr, "%s -- change on snapshot logical "=0A= "volume \"%s\" not allowed\n", cmd, = lv_name);=0A= continue;=0A= @@ -370,7 +372,12 @@=0A= =0A= if ( doit > 0) {=0A= doit_sum++;=0A= - lv->lv_access =3D lv_access;=0A= + /* don't clear access flags except for LV_WRITE and = LV_READ */=0A= + if (lv->lv_access & LV_WRITE)=0A= + lv->lv_access -=3D LV_WRITE;=0A= + if (lv->lv_access & LV_READ)=0A= + lv->lv_access -=3D LV_READ;=0A= + lv->lv_access |=3D lv_access;=0A= if ( opt_v > 0) printf ( "%s -- changing access = permissions "=0A= "of logical volume \"%s\"\n",=0A= cmd, lv_name);=0A= ------_=_NextPart_000_01C10EF1.F910F5B0 Content-Type: application/octet-stream; name="lvm-0.9.1beta7-writeable-snap.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="lvm-0.9.1beta7-writeable-snap.patch" --- linux/drivers/md/lvm.c.orig Fri May 18 19:04:30 2001=0A= +++ linux/drivers/md/lvm.c Fri May 18 19:30:44 2001=0A= @@ -1120,8 +1120,8 @@=0A= ulong pe_start;=0A= ulong size =3D bh->b_size >> 9;=0A= ulong rsector_org =3D bh->b_rsector;=0A= - ulong rsector_map;=0A= - kdev_t rdev_map;=0A= + ulong rsector_map, rsector_sav;=0A= + kdev_t rdev_map, rdev_sav;=0A= vg_t *vg_this =3D vg[VG_BLK(minor)];=0A= lv_t *lv =3D vg_this->lv[LV_BLK(minor)];=0A= =0A= @@ -1228,12 +1228,42 @@=0A= goto out;=0A= =0A= if (lv->lv_access & LV_SNAPSHOT) { /* remap snapshot */=0A= - if (lv->lv_block_exception)=0A= + if (lv->lv_block_exception) {=0A= + if (rw =3D=3D WRITE || rw =3D=3D WRITEA) {=0A= + /* Start of writeable snapshot portion */=0A= + rdev_sav =3D rdev_map;=0A= + rsector_sav =3D rsector_map;=0A= + =0A= + if (!lvm_snapshot_remap_block(&rdev_map,=0A= + &rsector_map,=0A= + pe_start,=0A= + lv)) {=0A= + /* create a new mapping */=0A= + if (lvm_snapshot_COW(rdev_map,=0A= + rsector_map,=0A= + pe_start,=0A= + rsector_sav,=0A= + vg_this,lv)) {=0A= + goto bad;=0A= + }=0A= + lvm_write_COW_table_block(vg_this,lv);=0A= + rdev_map =3D rdev_sav;=0A= + rsector_map =3D rsector_sav;=0A= + if (!lvm_snapshot_remap_block(&rdev_map,=0A= + &rsector_map,=0A= + pe_start,=0A= + lv)) {=0A= + goto bad;=0A= + }=0A= + }=0A= + /* End of writable snapshot portion */=0A= + }=0A= + else=0A= lvm_snapshot_remap_block(&rdev_map, &rsector_map,=0A= pe_start, lv);=0A= - else=0A= + }=0A= + else=0A= goto bad;=0A= -=0A= } else if(rw =3D=3D WRITE || rw =3D=3D WRITEA) { /* snapshot origin = */=0A= lv_t *snap;=0A= =0A= ------_=_NextPart_000_01C10EF1.F910F5B0-- From owner-linux-xfs@oss.sgi.com Tue Jul 17 12:06:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HJ6eG28193 for linux-xfs-outgoing; Tue, 17 Jul 2001 12:06:40 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HJ6bV28174 for ; Tue, 17 Jul 2001 12:06:37 -0700 Received: (qmail 22124 invoked from network); 17 Jul 2001 19:06:28 -0000 Received: from srg.access.comstar.ru (HELO beta.namesys.com) (195.210.131.190) by thebsh.namesys.com with SMTP; 17 Jul 2001 19:06:28 -0000 Received: (from god@localhost) by beta.namesys.com (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) id QAA09007; Tue, 17 Jul 2001 16:04:03 +0400 From: Nikita Danilov MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-ID: <15188.10675.283457.862145@beta.namesys.com> Date: Tue, 17 Jul 2001 16:04:03 +0400 To: Hans Reiser Cc: Xuan Baldauf , Ragnar =?koi8-r?Q?Kj=F8rstad?= , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks In-Reply-To: <3B53F65D.265034CB@namesys.com> References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <3B534B74.BDE19961@baldauf.org> <20010716223240.D14564@vestdata.no> <3B5363FE.3A7D892F@baldauf.org> <3B53F65D.265034CB@namesys.com> X-Mailer: VM 6.89 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hans Reiser writes: > A file change notification API is an inherently reasonable thing to have, for use by more than just > NFS (emacs for instance). What's wrong with fcntl( F_NOTIFY )? I mean, there is standard notification API (and several non-standard ones, stolen from BSD) in Linux. > > Hans Nikita. > > Xuan Baldauf wrote: > > > > Ragnar Kjørstad wrote: > > > > > > > For each open file you have: > > > > > > > > > > struct file (96b) Nikita. From owner-linux-xfs@oss.sgi.com Tue Jul 17 12:56:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HJuN829443 for linux-xfs-outgoing; Tue, 17 Jul 2001 12:56:23 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HJuIV29424 for ; Tue, 17 Jul 2001 12:56:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA385106 for ; Tue, 17 Jul 2001 21:56:01 +0200 (CEST) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2453006; Tue, 17 Jul 2001 14:54:57 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA13503; Tue, 17 Jul 2001 14:54:57 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id OAA33575; Tue, 17 Jul 2001 14:54:56 -0500 (CDT) Message-Id: <200107171954.OAA33575@fsgi158.americas.sgi.com> Subject: Re: Quota reporting for NFS mounts To: syrekron@iastate.edu (Adrian Hill) Date: Tue, 17 Jul 2001 14:54:56 -0500 (CDT) Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B546D7F.71D884B@iastate.edu> from "Adrian Hill" at Jul 17, 2001 11:53:19 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm able to report quotas over NFS with server running RH 7.1 and 1.0.1-2.4.3. It appears that rpc.rquotad is not responding at all. Could you try pinging it from the client with rpcinfo: rpcinfo -u sherlock 100011 1 to see if it is responding at all. If not maybe you could try restarting it on the server. Tad > > Hello All > > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > built from the source rpm. > > I have exported my /export partition over NFS which file system is XFS. > > I can mount this from client type machines, but when I try (on the > client) to list my quota, the command just hangs. I've run snoop on the > connection, and it appears that my server (sherlock) doesn't respond to > the client's (cousteau) requests. > > I also verified that rpc.rquotad is running on my server. > > Any idea how I can get remote quota reporting working? > > Thanks in advance, > > Adrian > > Here is the snoop output: > > [cousteau ~ 7]# snoop sherlock > Using device ec0 (promiscuous mode) > cousteau -> sherlock TCP D=111 S=661 Syn Seq=1727695818 Len=0 > Win=61440 > cousteau -> sherlock TCP D=111 S=661 Syn Seq=1727695818 Len=0 > Win=61440 > sherlock -> cousteau TCP D=661 S=111 Syn Ack=1727695819 > Seq=2875267868 Len=0 Win=5840 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Fin Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Fin Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > sherlock -> cousteau TCP D=661 S=111 Fin Ack=1727695820 > Seq=2875267869 Len=0 Win=5840 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267870 > Seq=1727695820 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267870 > Seq=1727695820 Len=0 Win=61320 > cousteau -> sherlock PORTMAP C GETPORT prog=100011 (RQUOTA) > vers=1 proto=UDP > cousteau -> sherlock PORTMAP C GETPORT prog=100011 (RQUOTA) > vers=1 proto=UDP (retransmit) > sherlock -> cousteau PORTMAP R GETPORT port=838 > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > [cousteau ~ 8]# > From owner-linux-xfs@oss.sgi.com Tue Jul 17 12:58:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HJwsB29725 for linux-xfs-outgoing; Tue, 17 Jul 2001 12:58:54 -0700 Received: from mailman.mnd.com ([208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HJwqV29705 for ; Tue, 17 Jul 2001 12:58:52 -0700 Received: from alpha2.production.mnd.com (alpha2.production.mnd.com [192.168.3.105]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id OAA20228 for ; Tue, 17 Jul 2001 14:58:23 -0500 Date: Tue, 17 Jul 2001 14:58:21 -0500 (CDT) From: Chris Bednar X-Sender: cjb@alpha2.production.mnd.com To: linux-xfs@oss.sgi.com Subject: xfsprogs large filesystem PATCH Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi The following is a tiny patch to libxfs/init.c to use `unsigned long' as the recipient in the BLKGETSIZE ioctl in findsize(). This ioctl can return a valid unsigned 32-bit quantity, and it does seem to be making mkfs.xfs work on a 1.2TB raid setup we have here, where it was failing with a negative number of blocks before. ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ ------------------------------------------------------- --- xfsprogs-1.3.1/libxfs/init.c.findsize Thu Jul 12 13:54:41 2001 +++ xfsprogs-1.3.1/libxfs/init.c Tue Jul 17 13:25:36 2001 @@ -132,7 +132,7 @@ { int fd; int error; - long size; + unsigned long size; struct stat64 st; /* Test to see if we are dealing with a regular file rather than a From owner-linux-xfs@oss.sgi.com Tue Jul 17 13:04:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HK4rN30126 for linux-xfs-outgoing; Tue, 17 Jul 2001 13:04:53 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HK4oV30107 for ; Tue, 17 Jul 2001 13:04:50 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA02036 for ; Tue, 17 Jul 2001 13:04:35 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2456623; Tue, 17 Jul 2001 15:03:14 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA50130; Tue, 17 Jul 2001 15:03:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HK4Mt02631; Tue, 17 Jul 2001 15:04:22 -0500 Message-Id: <200107172004.f6HK4Mt02631@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Chris Bednar cc: linux-xfs@oss.sgi.com Subject: Re: xfsprogs large filesystem PATCH In-Reply-To: Message from Chris Bednar of "Tue, 17 Jul 2001 14:58:21 CDT." Date: Tue, 17 Jul 2001 15:04:22 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi > > The following is a tiny patch to libxfs/init.c > to use `unsigned long' as the recipient in the > BLKGETSIZE ioctl in findsize(). This ioctl can > return a valid unsigned 32-bit quantity, and it > does seem to be making mkfs.xfs work on a 1.2TB > raid setup we have here, where it was failing > with a negative number of blocks before. Thanks for the patch. Hmm, I see you just joined the mailing list, so you probably missed the message I sent out to someone with a 1.1Tbyte raid earlier today. Take a look at this message or your inode numbers may end up overflowing 32 bits. http://oss.sgi.com/projects/xfs/mail_archive/0107/msg00727.html Steve > > > ---- > Chris J. Bednar > Director, Distributed Computing Product Group > http://AdvancedDataSolutions.com/ > ------------------------------------------------------- > > --- xfsprogs-1.3.1/libxfs/init.c.findsize Thu Jul 12 13:54:41 2001 > +++ xfsprogs-1.3.1/libxfs/init.c Tue Jul 17 13:25:36 2001 > @@ -132,7 +132,7 @@ > { > int fd; > int error; > - long size; > + unsigned long size; > struct stat64 st; > > /* Test to see if we are dealing with a regular file rather than a From owner-linux-xfs@oss.sgi.com Tue Jul 17 13:19:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HKJxa30744 for linux-xfs-outgoing; Tue, 17 Jul 2001 13:19:59 -0700 Received: from mailman.mnd.com ([208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HKJrV30724 for ; Tue, 17 Jul 2001 13:19:54 -0700 Received: from alpha2.production.mnd.com (alpha2.production.mnd.com [192.168.3.105]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id PAA21557 for ; Tue, 17 Jul 2001 15:19:24 -0500 Date: Tue, 17 Jul 2001 15:19:23 -0500 (CDT) From: Chris Bednar X-Sender: cjb@alpha2.production.mnd.com To: linux-xfs@oss.sgi.com Subject: am-utils xfs PATCH Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi The following are (1) a patch to am-utils-6.0.5 (a la RedHat 7.1) to get it to build on a system with XFS installed, and (2) a spec file for RPM with configure options to go with the patch. This is pretty kludgy, but it does work... it basically just adds an #include to amd/ops_xfs.c and adds --enable-am-cflags="-I/usr/include/xfs -Dxfs_args_t=xfs_da_args_t" to the configure. It's cheap and dirty, but it works. ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ --The patch:------------------------------- --- am-utils-6.0.5/amd/ops_xfs.c.xfslinux Sun Jul 15 16:39:52 2001 +++ am-utils-6.0.5/amd/ops_xfs.c Sun Jul 15 16:40:49 2001 @@ -52,6 +52,11 @@ #include #include +/* + * Need this for Linux XFS: + */ +#include + /* forward declarations */ static char *xfs_match(am_opts *fo); static int xfs_fmount(mntfs *mf); --The spec:--------------------------------- Summary: Automount utilities including an updated version of Amd. Name: am-utils Version: 6.0.5 Release: cjb1 Copyright: BSD Epoch: 5 Group: System Environment/Daemons URL: http://am-utils.org/ Source: ftp://ftp.am-utils.org/pub/am-utils/am-utils-%{version}.tar.gz Source1: am-utils.init Source2: am-utils.conf Source3: am-utils.sysconf Source4: am-utils.net.map Patch: am-utils-6.0.4-nfs3.patch Patch100: am-utils-6.0.5-xfslinux.patch BuildRoot: %{_tmppath}/%{name}-root BuildPrereq: openldap-devel Requires: portmap, grep, gawk, findutils Prereq: /sbin/install-info, /sbin/chkconfig, grep Obsoletes: amd %description Am-utils includes an updated version of Amd, the popular BSD automounter. An automounter is a program which maintains a cache of mounted filesystems. Filesystems are mounted when they are first referenced by the user and unmounted after a certain period of inactivity. Amd supports a variety of filesystems, including NFS, UFS, CD-ROMS and local drives. You should install am-utils if you need a program for automatically mounting and unmounting filesystems. %prep %setup -q %patch -p1 -b .nfs3 %patch100 -p1 -b .xfslinux autoheader autoconf %build %configure --enable-shared --enable-libs="-lnsl -lresolv" --disable-amq-mount --enable-am-cflags="-I/usr/include/xfs -Dxfs_args_t=xfs_da_args_t" make %install rm -rf $RPM_BUILD_ROOT %makeinstall mkdir -p $RPM_BUILD_ROOT/etc/{sysconfig,rc.d/init.d} install -m 755 $RPM_SOURCE_DIR/am-utils.sysconf $RPM_BUILD_ROOT/etc/sysconfig/amd install -m 755 $RPM_SOURCE_DIR/am-utils.init $RPM_BUILD_ROOT/etc/rc.d/init.d/amd strip $RPM_BUILD_ROOT/usr/sbin/* $RPM_BUILD_ROOT/usr/bin/* || : gzip -q9f $RPM_BUILD_ROOT/%{_infodir}/*info* mkdir -p $RPM_BUILD_ROOT/.automount rm -f $RPM_BUILD_ROOT/usr/sbin/ctl-amd # install the default config and map files install -m 600 %{SOURCE2} $RPM_BUILD_ROOT/etc/amd.conf install -m 640 %{SOURCE4} $RPM_BUILD_ROOT/etc/amd.net %clean rm -rf $RPM_BUILD_ROOT %pre # Check if we have an old fashioned amd.conf and rename if to amd.net if [ "$1" = "0" ] ; then if grep -q "auto_dir" /etc/amd.conf 2>/dev/null ; then # this is okay exit 0 else # this needs to be renamed. Still, if /etc/amd.net exists, then # don't bother renamig it. RPM will handle it better than us here. if [ -e /etc/amd.net ] ; then exit 0 else mv -f /etc/amd.conf /etc/amd.net fi fi fi exit 0 %post /sbin/ldconfig /sbin/chkconfig --add amd /sbin/install-info %{_infodir}/am-utils.info.gz %{_infodir}/dir %preun if [ $1 = 0 ]; then /sbin/install-info --delete %{_infodir}/am-utils.info.gz %{_infodir}/dir /sbin/service amd stop >/dev/null 2>&1 /sbin/chkconfig --del amd fi %postun if [ $1 -ge 1 ]; then /sbin/service amd condrestart >/dev/null 2>&1 fi /sbin/ldconfig %files %defattr(-,root,root) %doc doc/*.ps AUTHORS BUGS ChangeLog NEWS README* scripts/*-sample %dir /.automount /usr/bin/pawd /usr/sbin/* %{_mandir}/man[58]/* %{_mandir}/man1/pawd.1* %config(noreplace) /etc/amd.net %config(noreplace) /etc/amd.conf %config(noreplace) /etc/sysconfig/amd %config /etc/rc.d/init.d/amd %{_infodir}/*info*.gz /usr/lib/libamu.so.*.* %changelog * Sun Jul 15 2001 Chris J Bednar - Try to get past XFS. Need to do the following: - - 1) -I/usr/include/xfs - 2) amd/ops_xfs.c : #include - 3) #define xfs_args_t xfs_da_args_t - 4) Get configure to determine that xfs_args_t.flags exists * Sat Apr 7 2001 Nalin Dahyabhai - update to 6.0.5 - remove /net from the default MOUNTPTS * Tue Mar 13 2001 Nalin Dahyabhai - use MOUNTPTS when starting * Fri Mar 2 2001 Nalin Dahyabhai - rebuild in new environment * Wed Feb 14 2001 Nalin Dahyabhai - redo i18n for the init script * Tue Jan 23 2001 Nalin Dahyabhai - re-do workaround from advice from the am-utils maintainers - redo i18n for the init script * Sat Jan 20 2001 Nalin Dahyabhai - work around clash with nfs3_fh definition in 2.4 * Tue Jan 16 2001 Nalin Dahyabhai - gettextize the init script (#24087) * Tue Dec 19 2000 Nalin Dahyabhai - add ldconfig to %%postun - chuck the hesiod patch -- new bind-utils doesn't have the support for it * Fri Sep 8 2000 Nalin Dahyabhai - rebuild in new environment * Sat Jul 15 2000 Bill Nottingham - move initscript back * Wed Jul 12 2000 Prospector - automatic rebuild * Thu Jul 6 2000 Nalin Dahyabhai - only create /var/lock/subsys/amd if startup succeeds - revamp shutdown procedure to minimize time spent just spinning - change initscripts dependency to /etc/init.d * Tue Jul 4 2000 Florian La Roche - delete noreplace from initscript * Wed Jun 28 2000 Nalin Dahyabhai - fix postun script - add requires: initscripts * Tue Jun 27 2000 Nalin Dahyabhai - remove unnecessary libamu.so symlink * Mon Jun 26 2000 Nalin Dahyabhai - move init script to /etc/init.d - add URL: tag * Wed Jun 21 2000 Preston Brown - noreplace config files - gracefully stop/restart service * Fri Jun 16 2000 Matt Wilson - FHS paths - 6.0.4 snapshot (as it builds against kernel 2.4 headers) * Wed Feb 16 2000 Cristian Gafton - version 6.0.3 - enhance init script to be more wait4amd2die-like - make default map type to be file (#9185) - get rid of the kludges * Thu Feb 03 2000 Cristian Gafton - man pages are compressed - version 6.0.2 - fix descriptions * Mon Sep 13 1999 Cristian Gafton - version 6.0.1 final * Tue Aug 24 1999 Cristian Gafton - remove the noldap patch - add amd.net file as the default config map file - change the config file to teh new config file format instead of a simple map file name. - try to avoid some damage with a new %pre script - prereq grep now - modify the init file so it calls amd -F /etc/amd.conf now * Tue Aug 24 1999 Bill Nottingham - update to 6.0.1s11 * Fri Jun 19 1999 Bill Nottingham - don't run by default * Mon May 31 1999 Kenneth Skaar - Fixed amd -F core dump and related dumps by other programs * Thu Apr 08 1999 Preston Brown - kill -HUP on reload, restart does a real restart. * Fri Mar 26 1999 Bill Nottingham - twiddle an echo in initscript * Tue Mar 23 1999 Cristian Gafton - version 6.0 proper - Serial:1 because to enforce versioning * Sun Mar 21 1999 Cristian Gafton - auto rebuild in the new build environment (release 6) * Wed Jan 06 1999 Cristian Gafton - rebuild for glibc 2.1 - strip all binaries * Thu Aug 13 1998 Jeff Johnson - add missing ':' to default 'opts:=nosuid,nodev' - install info pages * Mon Jul 13 1998 Cristian Gafton - added the NIS support that the broken configure script failed to detect * Tue May 05 1998 Cristian Gafton - disabled autofs support on alpha - run ldconfig in postinstall * Mon May 04 1998 Cristian Gafton - new package to replace the old and unmaintained amd From owner-linux-xfs@oss.sgi.com Tue Jul 17 14:25:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HLPFk02435 for linux-xfs-outgoing; Tue, 17 Jul 2001 14:25:15 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HLP7V02412 for ; Tue, 17 Jul 2001 14:25:07 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15McKt-0000d7-00; Tue, 17 Jul 2001 23:24:55 +0200 Message-ID: <3B54AD27.F40A89@berdmann.de> Date: Tue, 17 Jul 2001 23:24:55 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Chris Bednar CC: linux-xfs@oss.sgi.com, "amd-dev@cs.columbia.edu" Subject: Re: am-utils xfs PATCH References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Great! It works with am-utils-6.0.7, too. Chris Bednar wrote: > > Hi > > The following are (1) a patch to am-utils-6.0.5 (a la > RedHat 7.1) to get it to build on a system with XFS installed, > and (2) a spec file for RPM with configure options to go with > the patch. > > This is pretty kludgy, but it does work... it basically just > adds an #include to amd/ops_xfs.c and adds > > --enable-am-cflags="-I/usr/include/xfs -Dxfs_args_t=xfs_da_args_t" > > to the configure. It's cheap and dirty, but it works. > > ---- > Chris J. Bednar > Director, Distributed Computing Product Group > http://AdvancedDataSolutions.com/ > > --The patch:------------------------------- > > --- am-utils-6.0.5/amd/ops_xfs.c.xfslinux Sun Jul 15 16:39:52 2001 > +++ am-utils-6.0.5/amd/ops_xfs.c Sun Jul 15 16:40:49 2001 > @@ -52,6 +52,11 @@ > #include > #include > > +/* > + * Need this for Linux XFS: > + */ > +#include > + > /* forward declarations */ > static char *xfs_match(am_opts *fo); > static int xfs_fmount(mntfs *mf); > > --The spec:--------------------------------- > Summary: Automount utilities including an updated version of Amd. > Name: am-utils > Version: 6.0.5 > Release: cjb1 > Copyright: BSD > Epoch: 5 > Group: System Environment/Daemons > URL: http://am-utils.org/ > Source: ftp://ftp.am-utils.org/pub/am-utils/am-utils-%{version}.tar.gz > Source1: am-utils.init > Source2: am-utils.conf > Source3: am-utils.sysconf > Source4: am-utils.net.map > Patch: am-utils-6.0.4-nfs3.patch > Patch100: am-utils-6.0.5-xfslinux.patch > BuildRoot: %{_tmppath}/%{name}-root > BuildPrereq: openldap-devel > Requires: portmap, grep, gawk, findutils > Prereq: /sbin/install-info, /sbin/chkconfig, grep > Obsoletes: amd > > %description > Am-utils includes an updated version of Amd, the popular BSD > automounter. An automounter is a program which maintains a cache > of mounted filesystems. Filesystems are mounted when they are > first referenced by the user and unmounted after a certain period of > inactivity. Amd supports a variety of filesystems, including NFS, UFS, > CD-ROMS and local drives. > > You should install am-utils if you need a program for automatically > mounting and unmounting filesystems. > > %prep > %setup -q > %patch -p1 -b .nfs3 > %patch100 -p1 -b .xfslinux > autoheader > autoconf > > %build > %configure --enable-shared --enable-libs="-lnsl -lresolv" --disable-amq-mount --enable-am-cflags="-I/usr/include/xfs -Dxfs_args_t=xfs_da_args_t" > make > > %install > rm -rf $RPM_BUILD_ROOT > %makeinstall > mkdir -p $RPM_BUILD_ROOT/etc/{sysconfig,rc.d/init.d} > install -m 755 $RPM_SOURCE_DIR/am-utils.sysconf $RPM_BUILD_ROOT/etc/sysconfig/amd > install -m 755 $RPM_SOURCE_DIR/am-utils.init $RPM_BUILD_ROOT/etc/rc.d/init.d/amd > strip $RPM_BUILD_ROOT/usr/sbin/* $RPM_BUILD_ROOT/usr/bin/* || : > gzip -q9f $RPM_BUILD_ROOT/%{_infodir}/*info* > mkdir -p $RPM_BUILD_ROOT/.automount > rm -f $RPM_BUILD_ROOT/usr/sbin/ctl-amd > > # install the default config and map files > install -m 600 %{SOURCE2} $RPM_BUILD_ROOT/etc/amd.conf > install -m 640 %{SOURCE4} $RPM_BUILD_ROOT/etc/amd.net > > %clean > rm -rf $RPM_BUILD_ROOT > > %pre > # Check if we have an old fashioned amd.conf and rename if to amd.net > if [ "$1" = "0" ] ; then > if grep -q "auto_dir" /etc/amd.conf 2>/dev/null ; then > # this is okay > exit 0 > else > # this needs to be renamed. Still, if /etc/amd.net exists, then > # don't bother renamig it. RPM will handle it better than us here. > if [ -e /etc/amd.net ] ; then > exit 0 > else > mv -f /etc/amd.conf /etc/amd.net > fi > fi > fi > exit 0 > > %post > /sbin/ldconfig > /sbin/chkconfig --add amd > /sbin/install-info %{_infodir}/am-utils.info.gz %{_infodir}/dir > > %preun > if [ $1 = 0 ]; then > /sbin/install-info --delete %{_infodir}/am-utils.info.gz %{_infodir}/dir > /sbin/service amd stop >/dev/null 2>&1 > /sbin/chkconfig --del amd > fi > > %postun > if [ $1 -ge 1 ]; then > /sbin/service amd condrestart >/dev/null 2>&1 > fi > /sbin/ldconfig > > %files > %defattr(-,root,root) > %doc doc/*.ps AUTHORS BUGS ChangeLog NEWS README* scripts/*-sample > %dir /.automount > /usr/bin/pawd > /usr/sbin/* > %{_mandir}/man[58]/* > %{_mandir}/man1/pawd.1* > %config(noreplace) /etc/amd.net > %config(noreplace) /etc/amd.conf > %config(noreplace) /etc/sysconfig/amd > %config /etc/rc.d/init.d/amd > %{_infodir}/*info*.gz > /usr/lib/libamu.so.*.* > > %changelog > * Sun Jul 15 2001 Chris J Bednar > - Try to get past XFS. Need to do the following: > - > - 1) -I/usr/include/xfs > - 2) amd/ops_xfs.c : #include > - 3) #define xfs_args_t xfs_da_args_t > - 4) Get configure to determine that xfs_args_t.flags exists > > * Sat Apr 7 2001 Nalin Dahyabhai > - update to 6.0.5 > - remove /net from the default MOUNTPTS > > * Tue Mar 13 2001 Nalin Dahyabhai > - use MOUNTPTS when starting > > * Fri Mar 2 2001 Nalin Dahyabhai > - rebuild in new environment > > * Wed Feb 14 2001 Nalin Dahyabhai > - redo i18n for the init script > > * Tue Jan 23 2001 Nalin Dahyabhai > - re-do workaround from advice from the am-utils maintainers > - redo i18n for the init script > > * Sat Jan 20 2001 Nalin Dahyabhai > - work around clash with nfs3_fh definition in 2.4 > > * Tue Jan 16 2001 Nalin Dahyabhai > - gettextize the init script (#24087) > > * Tue Dec 19 2000 Nalin Dahyabhai > - add ldconfig to %%postun > - chuck the hesiod patch -- new bind-utils doesn't have the support for it > > * Fri Sep 8 2000 Nalin Dahyabhai > - rebuild in new environment > > * Sat Jul 15 2000 Bill Nottingham > - move initscript back > > * Wed Jul 12 2000 Prospector > - automatic rebuild > > * Thu Jul 6 2000 Nalin Dahyabhai > - only create /var/lock/subsys/amd if startup succeeds > - revamp shutdown procedure to minimize time spent just spinning > - change initscripts dependency to /etc/init.d > > * Tue Jul 4 2000 Florian La Roche > - delete noreplace from initscript > > * Wed Jun 28 2000 Nalin Dahyabhai > - fix postun script > - add requires: initscripts > > * Tue Jun 27 2000 Nalin Dahyabhai > - remove unnecessary libamu.so symlink > > * Mon Jun 26 2000 Nalin Dahyabhai > - move init script to /etc/init.d > - add URL: tag > > * Wed Jun 21 2000 Preston Brown > - noreplace config files > - gracefully stop/restart service > > * Fri Jun 16 2000 Matt Wilson > - FHS paths > - 6.0.4 snapshot (as it builds against kernel 2.4 headers) > > * Wed Feb 16 2000 Cristian Gafton > - version 6.0.3 > - enhance init script to be more wait4amd2die-like > - make default map type to be file (#9185) > - get rid of the kludges > > * Thu Feb 03 2000 Cristian Gafton > - man pages are compressed > - version 6.0.2 > - fix descriptions > > * Mon Sep 13 1999 Cristian Gafton > - version 6.0.1 final > > * Tue Aug 24 1999 Cristian Gafton > - remove the noldap patch > - add amd.net file as the default config map file > - change the config file to teh new config file format instead of a > simple map file name. > - try to avoid some damage with a new %pre script > - prereq grep now > - modify the init file so it calls amd -F /etc/amd.conf now > > * Tue Aug 24 1999 Bill Nottingham > - update to 6.0.1s11 > > * Fri Jun 19 1999 Bill Nottingham > - don't run by default > > * Mon May 31 1999 Kenneth Skaar > - Fixed amd -F core dump and related dumps by other programs > > * Thu Apr 08 1999 Preston Brown > - kill -HUP on reload, restart does a real restart. > > * Fri Mar 26 1999 Bill Nottingham > - twiddle an echo in initscript > > * Tue Mar 23 1999 Cristian Gafton > - version 6.0 proper > - Serial:1 because to enforce versioning > > * Sun Mar 21 1999 Cristian Gafton > - auto rebuild in the new build environment (release 6) > > * Wed Jan 06 1999 Cristian Gafton > - rebuild for glibc 2.1 > - strip all binaries > > * Thu Aug 13 1998 Jeff Johnson > - add missing ':' to default 'opts:=nosuid,nodev' > - install info pages > > * Mon Jul 13 1998 Cristian Gafton > - added the NIS support that the broken configure script failed to detect > > * Tue May 05 1998 Cristian Gafton > - disabled autofs support on alpha > - run ldconfig in postinstall > > * Mon May 04 1998 Cristian Gafton > - new package to replace the old and unmaintained amd From owner-linux-xfs@oss.sgi.com Tue Jul 17 14:29:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HLTZ702878 for linux-xfs-outgoing; Tue, 17 Jul 2001 14:29:35 -0700 Received: from mail.corbett-msc.com (mail.corbett-msc.com [4.21.114.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HLTXV02859 for ; Tue, 17 Jul 2001 14:29:33 -0700 Received: (qmail 10060 invoked from network); 17 Jul 2001 21:29:27 -0000 Received: from 24-168-197-0.ff.cox.rr.com (HELO adampc) (apendlet@24.168.197.0) by mail.corbett-msc.com with SMTP; 17 Jul 2001 21:29:27 -0000 Message-ID: <005c01c10f06$e4af5200$650aa8c0@corbettmsc.com> From: "Adam H. Pendleton" To: Subject: Vmware and XFS Date: Tue, 17 Jul 2001 17:24:41 -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 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am wondering now that I have gone to XFS, if it is possible to extend a guest operating system partition in Vmware past the traditional 32-bit (2GB) limitation. If so, how? Adam Pendleton From owner-linux-xfs@oss.sgi.com Tue Jul 17 14:29:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HLTmk03000 for linux-xfs-outgoing; Tue, 17 Jul 2001 14:29:48 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HLTlV02979 for ; Tue, 17 Jul 2001 14:29:47 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJXCV>; Tue, 17 Jul 2001 16:28:56 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643446@AUSMAIL> From: "Gonyou, Austin" To: "'Chris Bednar'" , linux-xfs@oss.sgi.com Subject: Stopping Myself errors? Date: Tue, 17 Jul 2001 16:28:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I keep getting these odd errors: *ap++ = 0x55 Stopping myself... Sometimes when I start a process I get this, other times not. Any idea why I'd get this? I'm running an AMD Athlon-C 1.333Ghz 256MB PC-133 SDRAM and ATA100 IDE 40GB DeskStar. Kernel is 2.4.5 XFS tree. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Tue Jul 17 14:34:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HLYBe03476 for linux-xfs-outgoing; Tue, 17 Jul 2001 14:34:11 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HLYAV03456 for ; Tue, 17 Jul 2001 14:34:10 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.2/8.11.2) with ESMTP id f6HLXqn30748; Tue, 17 Jul 2001 17:33:52 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Tue, 17 Jul 2001 17:33:51 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: "Adam H. Pendleton" cc: Subject: Re: Vmware and XFS In-Reply-To: <005c01c10f06$e4af5200$650aa8c0@corbettmsc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 17 Jul 2001 at 5:24pm, Adam H. Pendleton wrote > I am wondering now that I have gone to XFS, if it is possible to extend a > guest operating system partition in Vmware past the traditional 32-bit (2GB) > limitation. If so, how? > The 2GB limit doesn't exist in ext2 either -- it was there due to limitations in glibc and some other bits. Most recent distros include large file support. To take advantage of this, an applications needs to compiled with the proper flags. And for that, of course, you'll need to talk to VMware. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Tue Jul 17 14:52:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HLqNF04866 for linux-xfs-outgoing; Tue, 17 Jul 2001 14:52:23 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HLqJV04840 for ; Tue, 17 Jul 2001 14:52:19 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MclE-0007wX-00; Tue, 17 Jul 2001 23:52:08 +0200 Message-ID: <3B54B387.520A4385@berdmann.de> Date: Tue, 17 Jul 2001 23:52:07 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: xfsrestore (Linux) generating Amanda's index Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I've experienced strange filenames in Amanda's index like " (offset 16769536)" in addition to "" for files on Linux XFS using xfsdump-1.0.9. The index is generated by client-src/sendbackup-dump.c: program->backup_name = XFSDUMP; program->restore_name = XFSRESTORE; indexcmd = vstralloc(XFSRESTORE, " -t", " -v", " silent", " -", " 2>/dev/null", " | sed", " -e", " \'s/^/\\//\'", NULL); write_tapeheader(); start_index(createindex, dumpout, mesgf, indexf, indexcmd); What's that offset about? $ zgrep -C "offset " ente/_usr/* ente/_usr/20010615_0.gz:/local/office52/help/49/shelp.dir ente/_usr/20010615_0.gz:/local/office52/help/49/shelp.dat ente/_usr/20010615_0.gz:/local/office52/help/49/shelp.dat (offset 16769536) ente/_usr/20010615_0.gz:/share/pixmaps/netscape.png ente/_usr/20010615_0.gz:/local/lib/perl5/man/man3/Cyrus::IMAP::Shell.3 ente/_usr/20010615_0.gz:-- ente/_usr/20010615_0.gz:/lib/libbsd-compat.a ente/_usr/20010615_0.gz:/lib/libc.a ente/_usr/20010615_0.gz:/lib/libc.a (offset 16777216) ente/_usr/20010615_0.gz:/lib/libc.so ente/_usr/20010615_0.gz:/lib/libc_nonshared.a ente/_usr/20010615_0.gz:-- ente/_usr/20010615_0.gz:/lib/libgrove.so.1.0.3 ente/_usr/20010615_0.gz:/lib/libsp.a ente/_usr/20010615_0.gz:/lib/libsp.a (offset 16777216) ente/_usr/20010615_0.gz:/lib/libsp.la ente/_usr/20010615_0.gz:/lib/libQwSpriteField.la ente/_usr/20010625_0.gz:/local/office52/help/49/shelp.dir ente/_usr/20010625_0.gz:/local/office52/help/49/shelp.dat ente/_usr/20010625_0.gz:/local/office52/help/49/shelp.dat (offset 16769536) ente/_usr/20010625_0.gz:/share/pixmaps/netscape.png ente/_usr/20010625_0.gz:/local/lib/perl5/man/man3/Cyrus::IMAP::Shell.3 ente/_usr/20010625_0.gz:-- ente/_usr/20010625_0.gz:/lib/libbsd-compat.a ente/_usr/20010625_0.gz:/lib/libc.a ente/_usr/20010625_0.gz:/lib/libc.a (offset 16777216) ente/_usr/20010625_0.gz:/lib/libc.so ente/_usr/20010625_0.gz:/lib/libc_nonshared.a ente/_usr/20010625_0.gz:-- ente/_usr/20010625_0.gz:/lib/libgrove.so.1.0.3 ente/_usr/20010625_0.gz:/lib/libsp.a ente/_usr/20010625_0.gz:/lib/libsp.a (offset 16777216) ente/_usr/20010625_0.gz:/lib/libsp.la ente/_usr/20010625_0.gz:/lib/libQwSpriteField.la ente/_usr/20010705_0.gz:/local/office52/help/49/shelp.dir ente/_usr/20010705_0.gz:/local/office52/help/49/shelp.dat ente/_usr/20010705_0.gz:/local/office52/help/49/shelp.dat (offset 16769536) ente/_usr/20010705_0.gz:/share/pixmaps/netscape.png ente/_usr/20010705_0.gz:/local/lib/perl5/man/man3/Cyrus::IMAP::Shell.3 ente/_usr/20010705_0.gz:-- ente/_usr/20010705_0.gz:/lib/libbsd-compat.a ente/_usr/20010705_0.gz:/lib/libc.a ente/_usr/20010705_0.gz:/lib/libc.a (offset 16777216) ente/_usr/20010705_0.gz:/lib/libc.so ente/_usr/20010705_0.gz:/lib/libc_nonshared.a ente/_usr/20010705_0.gz:-- ente/_usr/20010705_0.gz:/lib/libgrove.so.1.0.3 ente/_usr/20010705_0.gz:/lib/libsp.a ente/_usr/20010705_0.gz:/lib/libsp.a (offset 16777216) ente/_usr/20010705_0.gz:/lib/libsp.la ente/_usr/20010705_0.gz:/lib/libQwSpriteField.la ente/_usr/20010715_0.gz:/local/office52/help/49/shelp.dir ente/_usr/20010715_0.gz:/local/office52/help/49/shelp.dat ente/_usr/20010715_0.gz:/local/office52/help/49/shelp.dat (offset 16769536) ente/_usr/20010715_0.gz:/share/pixmaps/netscape.png ente/_usr/20010715_0.gz:/local/lib/perl5/man/man3/Cyrus::IMAP::Shell.3 ente/_usr/20010715_0.gz:-- ente/_usr/20010715_0.gz:/lib/libbsd-compat.a ente/_usr/20010715_0.gz:/lib/libc.a ente/_usr/20010715_0.gz:/lib/libc.a (offset 16777216) ente/_usr/20010715_0.gz:/lib/libc.so ente/_usr/20010715_0.gz:/lib/libc_nonshared.a ente/_usr/20010715_0.gz:-- ente/_usr/20010715_0.gz:/lib/libgrove.so.1.0.3 ente/_usr/20010715_0.gz:/lib/libsp.a ente/_usr/20010715_0.gz:/lib/libsp.a (offset 16777216) ente/_usr/20010715_0.gz:/lib/libsp.la ente/_usr/20010715_0.gz:/lib/libQwSpriteField.la From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:01:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HM1SA05568 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:01:28 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HM1PV05546 for ; Tue, 17 Jul 2001 15:01:25 -0700 Received: (qmail 5621 invoked from network); 17 Jul 2001 22:01:18 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 17 Jul 2001 22:01:18 -0000 Message-ID: <3B54B570.DF35CEDC@namesys.com> Date: Wed, 18 Jul 2001 02:00:16 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Federico Sevilla III CC: linux-xfs@oss.sgi.com, reiserfs-list@namesys.com, "Elena V. Gryaznova" Subject: Re: [reiserfs-list] Re: benchmarks References: <995050427.3b4f43bb56ac3@horde.leathercollection.ph> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk mongo was designed to show me what file size ranges reiserfs performance was weak at. Yes, if you look at one part of it, it shows you where reiserfs is fast at small files, but if you look at another part of it, it shows you where reiserfs is slower than XFS for very large files. We'll try to fix that in reiser4.....:-) (I think I know exactly what the problem is, we may even fix it in v3.) I think the most significant feature of mongo.pl though, is that it attempts to generate a realistic (and tunable) fileset that reflects the old 80/20 rule that 80% of the bytes are in 20% of the files, and it uses a fractal file size distribution function that I think is innovative in benchmarking. We should modify mongo.pl to both benchmark using that rule, and to benchmark with rigid file size ranges. Elena, I'd like to see that. XFS is a great filesystem, and reiser4 learns much from it. Hans From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:14:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMEvB06599 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:14:57 -0700 Received: from gandalf.cc.purdue.edu (root@gandalf.cc.purdue.edu [128.210.135.25]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMEtV06574 for ; Tue, 17 Jul 2001 15:14:55 -0700 Received: from gandalf.cc.purdue.edu (jrj@localhost [127.0.0.1]) by gandalf.cc.purdue.edu (8.9.1/8.9.1) with ESMTP id RAA19219; Tue, 17 Jul 2001 17:14:50 -0500 (EST) Message-Id: <200107172214.RAA19219@gandalf.cc.purdue.edu> To: "Bernhard R. Erdmann" cc: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index In-reply-to: Your message of "Tue, 17 Jul 2001 23:52:07 +0200." <3B54B387.520A4385@berdmann.de> Reply-to: jrj@cc.purdue.edu Date: Tue, 17 Jul 2001 17:14:49 -0500 From: "John R. Jackson" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >I've experienced strange filenames in Amanda's index like " >(offset 16769536)" in addition to "" for files on Linux XFS >using xfsdump-1.0.9. >... >What's that offset about? You're asking the wrong folks. Amanda only run xfs for you. If it's throwing crap around (which appears to be the case), you need to ask the xfsdump/xfsrestore folks. John R. Jackson, Technical Software Specialist, jrj@purdue.edu From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:30:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMUZN07828 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:30:35 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMUXV07805 for ; Tue, 17 Jul 2001 15:30:33 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MdMI-000886-00; Wed, 18 Jul 2001 00:30:26 +0200 Message-ID: <3B54BC82.1B7683F1@berdmann.de> Date: Wed, 18 Jul 2001 00:30:26 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: jrj@cc.purdue.edu CC: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index References: <200107172214.RAA19219@gandalf.cc.purdue.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > You're asking the wrong folks. Amanda only run xfs for you. If it's > throwing crap around (which appears to be the case), you need to ask > the xfsdump/xfsrestore folks. I know Amanda is just my beloved, best-ever-seen and you-made-my-day wrapper around dump/backup/xfsdump/tar... But maybe the Amanda folks got some nice ideas in addition to the xfs folks? From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:37:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMbYS08385 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:37:34 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMbWV08365 for ; Tue, 17 Jul 2001 15:37:32 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MdT3-00089R-00; Wed, 18 Jul 2001 00:37:25 +0200 Message-ID: <3B54BE25.7371BE2@berdmann.de> Date: Wed, 18 Jul 2001 00:37:25 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Ivan Rayner CC: Linux XFS Mailing List , "amanda-users@amanda.org" Subject: Re: Bug: xfsrestore -t insists on CWD being on a XFS filesystem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ivan Rayner wrote: > > On Mon, 28 May 2001, Bernhard R. Erdmann wrote: > > > Hi, > > > > xfsrestore for Linux in test mode (-t) stops at the beginning if CWD is > > not on a XFS filesystem: > > This is a known problem in xfsrestore which has been there since day 1 in > IRIX. It has only been a minor inconvenience in IRIX, since few sites > would use XFS and EFS together on the same system, but obviously it's a > bigger issue in Linux. > > I'll create an entry in SGI's internal bug database for this, and I'm sure > it'll get dealt with in due course. > > Of course, the workaround for this would be to convert /tmp to XFS. :) I've patched amverify (2.4.2p2) to do the trick. It cds to /tmp/amanda (on XFS) prior to start xfsrestore being fed by the xfsdump image: --- /usr/sbin/amverify.orig Mon May 21 22:48:37 2001 +++ /usr/sbin/amverify Sat Jun 2 00:20:19 2001 @@ -307,6 +307,12 @@ # DEFECTS defect list # REPORT report for mail +if [ -d /tmp/amanda ]; then + cd /tmp/amanda +else + echo "no dir /tmp/amanda" + exit 1 +fi TEMP=/tmp/amanda/amverify.$$ trap 'rm -fr $TEMP' 0 if ( umask 077 ; mkdir $TEMP ) ; then Ok, it's not the nice, general, amverify.in, testing-for-OS-and-xfsrestore solution but it works for me. From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:38:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMcqc08608 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:38:52 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMcnV08588 for ; Tue, 17 Jul 2001 15:38:49 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MdUJ-00089o-00; Wed, 18 Jul 2001 00:38:43 +0200 Message-ID: <3B54BE73.85CC7C36@berdmann.de> Date: Wed, 18 Jul 2001 00:38:43 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Ivan Rayner CC: Linux XFS Mailing List , "amanda-users@amanda.org" Subject: Re: Bug: xfsrestore -t insists on CWD being on a XFS filesystem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ivan Rayner wrote: > > On Mon, 28 May 2001, Bernhard R. Erdmann wrote: > > > Hi, > > > > xfsrestore for Linux in test mode (-t) stops at the beginning if CWD is > > not on a XFS filesystem: > > This is a known problem in xfsrestore which has been there since day 1 in > IRIX. It has only been a minor inconvenience in IRIX, since few sites > would use XFS and EFS together on the same system, but obviously it's a > bigger issue in Linux. > > I'll create an entry in SGI's internal bug database for this, and I'm sure > it'll get dealt with in due course. > > Of course, the workaround for this would be to convert /tmp to XFS. :) I've patched amverify (2.4.2p2) to do the trick. It cds to /tmp/amanda (on XFS) prior to start xfsrestore being fed by the xfsdump image: --- /usr/sbin/amverify.orig Mon May 21 22:48:37 2001 +++ /usr/sbin/amverify Sat Jun 2 00:20:19 2001 @@ -307,6 +307,12 @@ # DEFECTS defect list # REPORT report for mail +if [ -d /tmp/amanda ]; then + cd /tmp/amanda +else + echo "no dir /tmp/amanda" + exit 1 +fi TEMP=/tmp/amanda/amverify.$$ trap 'rm -fr $TEMP' 0 if ( umask 077 ; mkdir $TEMP ) ; then Ok, it's not the nice, general, amverify.in, testing-for-OS-and-xfsrestore solution but it works for me. From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:43:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMhDA09141 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:43:13 -0700 Received: from thebsh.namesys.com (thebsh.namesys.com [212.16.0.238]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMhAV09118 for ; Tue, 17 Jul 2001 15:43:10 -0700 Received: (qmail 8549 invoked from network); 17 Jul 2001 22:43:04 -0000 Received: from backtop.reiserfs.com (HELO namesys.com) (212.16.7.71) by thebsh.namesys.com with SMTP; 17 Jul 2001 22:43:04 -0000 Message-ID: <3B54BF39.4826A17A@namesys.com> Date: Wed, 18 Jul 2001 02:42:01 +0400 From: Hans Reiser Organization: Namesys X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4 i686) X-Accept-Language: en, ru MIME-Version: 1.0 To: Nikita Danilov CC: Xuan Baldauf , "Ragnar =?koi8-r?Q?Kj=F8rstad?=" , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <3B534B74.BDE19961@baldauf.org> <20010716223240.D14564@vestdata.no> <3B5363FE.3A7D892F@baldauf.org> <3B53F65D.265034CB@namesys.com> <15188.10675.283457.862145@beta.namesys.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nikita Danilov wrote: > > Hans Reiser writes: > > A file change notification API is an inherently reasonable thing to have, for use by more than just > > NFS (emacs for instance). > > What's wrong with fcntl( F_NOTIFY )? > I mean, there is standard notification API (and several non-standard > ones, stolen from BSD) in Linux. > > > > > Hans > > Nikita. > > > > > Xuan Baldauf wrote: > > > > > > Ragnar Kjørstad wrote: > > > > > > > > > For each open file you have: > > > > > > > > > > > > struct file (96b) > > Nikita. It might be perfect for NFS. My man page for fcntl doesn't list F_NOTIFY. I will guess at what it does though (yah, I know, I should read the source, but it is late), and say that it or something resembling it should be used by NFS. Generation numbers have the feel of a hack, to my mind. I would probably feel better about generation numbers if they didn't take up space in the stat data, but they would still feel like a hack. So, do I understand right that Xuan's solution could eliminate the need to store the generation number in the stat data? The problem with Xuan's solution though, is that it is easier to randomly obtain identical generation numbers for differing versions of the same file. Am I right? Maybe in V4 we can make the attribute holding generation numbers be dynamically allocated. That way, NFS doesn't burden other FS uses. I bet we won't have time for that extra touch of programming before we ship code though. Sigh. Hans From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:43:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMhLX09252 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:43:21 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMhHV09196 for ; Tue, 17 Jul 2001 15:43:18 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id AAA403471 for ; Wed, 18 Jul 2001 00:43:00 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2394964; Tue, 17 Jul 2001 17:41:56 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA31726; Tue, 17 Jul 2001 17:41:56 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HMh3K02985; Tue, 17 Jul 2001 17:43:03 -0500 Message-Id: <200107172243.f6HMh3K02985@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Bernhard R. Erdmann" cc: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index In-Reply-To: Message from "Bernhard R. Erdmann" of "Tue, 17 Jul 2001 23:52:07 +0200." <3B54B387.520A4385@berdmann.de> Date: Tue, 17 Jul 2001 17:43:03 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk It looks like xfsdump will break large files into chunks in the dump archive. This has more to do with not splitting a record in the dump archive between tape media than anything else I think. It is also possible for an interrupted dump to be restored, and really big files would tend to be a hinderence to this. I found this comment in the code: /* a regular file may be broken into several portions if its size * is large. Each portion begins with a filehdr_t and is followed by * several extents. */ It looks like the inventory list code is reporting each individual component of the file which it finds in the archive. Is this actually causing problems, or is it just a query as to why you see the odd names? Steve > Hi, > > I've experienced strange filenames in Amanda's index like " > (offset 16769536)" in addition to "" for files on Linux XFS > using xfsdump-1.0.9. > > The index is generated by client-src/sendbackup-dump.c: > > program->backup_name = XFSDUMP; > program->restore_name = XFSRESTORE; > > indexcmd = vstralloc(XFSRESTORE, > " -t", > " -v", " silent", > " -", > " 2>/dev/null", > " | sed", > " -e", " \'s/^/\\//\'", > NULL); > write_tapeheader(); > > start_index(createindex, dumpout, mesgf, indexf, indexcmd); > > What's that offset about? > From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:53:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMrXD10216 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:53:33 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMrVV10194 for ; Tue, 17 Jul 2001 15:53:31 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MdiW-0008E5-00; Wed, 18 Jul 2001 00:53:24 +0200 Message-ID: <3B54C1E4.ECD9EC9F@berdmann.de> Date: Wed, 18 Jul 2001 00:53:24 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Steve Lord CC: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index References: <200107172243.f6HMh3K02985@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Is this actually causing problems, or is it just a query as to why > you see the odd names? Just being curious... I haven't recognized any problems yet. It just causes an annoying listing of mangled filenames in addition to the original filename in the index, my SysOps will ask me "How can we rely on it if it's messing up the index? Does it mess up the backup, too?" and I have to write some more lines in the documentation just to ignore these offset names... From owner-linux-xfs@oss.sgi.com Tue Jul 17 15:57:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HMvkk10658 for linux-xfs-outgoing; Tue, 17 Jul 2001 15:57:46 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HMvjV10637 for ; Tue, 17 Jul 2001 15:57:45 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA01672 for ; Tue, 17 Jul 2001 15:57:31 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2457273; Tue, 17 Jul 2001 17:56:28 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA82270; Tue, 17 Jul 2001 17:56:28 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6HMvZu03041; Tue, 17 Jul 2001 17:57:35 -0500 Message-Id: <200107172257.f6HMvZu03041@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Bernhard R. Erdmann" cc: Steve Lord , "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index In-Reply-To: Message from "Bernhard R. Erdmann" of "Wed, 18 Jul 2001 00:53:24 +0200." <3B54C1E4.ECD9EC9F@berdmann.de> Date: Tue, 17 Jul 2001 17:57:35 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Is this actually causing problems, or is it just a query as to why > > you see the odd names? > > Just being curious... I haven't recognized any problems yet. It just > causes an annoying listing of mangled filenames in addition to the > original filename in the index, my SysOps will ask me "How can we rely > on it if it's messing up the index? Does it mess up the backup, too?" > and I have to write some more lines in the documentation just to ignore > these offset names... I guess if the dump was being split over multiple tape files then it would be useful to see the fact that a file was split between them. This may be the original intent of the output. Are you using real tape media, or a file, I suspect the file case could be smart enough not to do the split as it does not make a whole lot of sense there. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:04:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HN45B11318 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:04:05 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HN3uV11284 for ; Tue, 17 Jul 2001 16:03:58 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJXMX>; Tue, 17 Jul 2001 18:03:11 -0500 Message-ID: <85063BBE668FD411944400D0B744267A64344C@AUSMAIL> From: "Gonyou, Austin" To: Linux XFS Mailing List Subject: dumping multiple sessions to a single tape with XFS dump. Date: Tue, 17 Jul 2001 18:03:11 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I still can't do it. If anyone could show me their scripts or perhaps give a brief example, I'd like to see it. Thanks. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:04:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HN4Jm11461 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:04:19 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HN4HV11430 for ; Tue, 17 Jul 2001 16:04:17 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Mdsx-0008HR-00; Wed, 18 Jul 2001 01:04:11 +0200 Message-ID: <3B54C46A.D667F144@berdmann.de> Date: Wed, 18 Jul 2001 01:04:10 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Steve Lord CC: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index References: <200107172257.f6HMvZu03041@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Are you using real tape media, or a file, I suspect the file case could > be smart enough not to do the split as it does not make a whole lot > of sense there. Amanda triggers xfsdump to write to stdout while splitting it to go to tape or a file on the holding disk (via network) and to xfsrestore reading from stdin to generate an index. So xfsrestore shouldn't know anything of an actual tape media. From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:08:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HN8vi12089 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:08:57 -0700 Received: from router.abc (pD4B9DB91.dip.t-dialin.net [212.185.219.145]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HN8sV12069 for ; Tue, 17 Jul 2001 16:08:54 -0700 Received: from baldauf.org (notebook.abc [192.168.1.3]) by router.abc (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) with ESMTP id f6HN8Uo17313; Wed, 18 Jul 2001 01:08:30 +0200 Message-ID: <3B54C566.BE6B0C7D@baldauf.org> Date: Wed, 18 Jul 2001 01:08:22 +0200 From: Xuan Baldauf X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: de-DE,en MIME-Version: 1.0 To: Hans Reiser CC: Nikita Danilov , Xuan Baldauf , "Ragnar =?iso-8859-1?Q?Kj=F8rstad?=" , Russell Coker , Chris Wedgwood , rsharpe@ns.aus.com, Seth Mos , Federico Sevilla III , linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks References: <3B5169E5.827BFED@namesys.com> <20010716210029.I11938@weta.f00f.org> <20010716101313.2DC3E965@lyta.coker.com.au> <3B52C49F.9FE1F503@namesys.com> <15186.51514.66966.458597@beta.namesys.com> <3B5341BA.1F68F755@baldauf.org> <15187.18225.196286.123754@beta.namesys.com> <3B534B74.BDE19961@baldauf.org> <20010716223240.D14564@vestdata.no> <3B5363FE.3A7D892F@baldauf.org> <3B53F65D.265034CB@namesys.com> <15188.10675.283457.862145@beta.namesys.com> <3B54BF39.4826A17A@namesys.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6HN8tV12070 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hans Reiser wrote: > Nikita Danilov wrote: > > > > Hans Reiser writes: > > > A file change notification API is an inherently reasonable thing to have, for use by more than just > > > NFS (emacs for instance). > > > > What's wrong with fcntl( F_NOTIFY )? > > I mean, there is standard notification API (and several non-standard > > ones, stolen from BSD) in Linux. > > > > > > > > Hans > > > > Nikita. > > > > > > > > Xuan Baldauf wrote: > > > > > > > > Ragnar Kjørstad wrote: > > > > > > > > > > > For each open file you have: > > > > > > > > > > > > > > struct file (96b) > > > > Nikita. > It might be perfect for NFS. My man page for fcntl doesn't list F_NOTIFY. I will guess at what it > does though (yah, I know, I should read the source, but it is late), and say that it or something > resembling it should be used by NFS. Generation numbers have the feel of a hack, to my mind. I > would probably feel better about generation numbers if they didn't take up space in the stat data, > but they would still feel like a hack. > > So, do I understand right that Xuan's solution could eliminate the need to store the generation > number in the stat data? The problem with Xuan's solution though, is that it is easier to randomly > obtain identical generation numbers for differing versions of the same file. Am I right? > > Maybe in V4 we can make the attribute holding generation numbers be dynamically allocated. That > way, NFS doesn't burden other FS uses. I bet we won't have time for that extra touch of programming > before we ship code though. Sigh. > > Hans Maybe we're talking about different things, maybe not: You need generation numbers for not creating a filesystem object with the same object_id after deleting a filesystem object with that object_id? If this is the case, you apparently need to reserve some space within the object_id for the generation number (e.g. 32 bits should be sufficient). Because in this case, the generation number is part of the object_id, why do you need another stat data field? How long is the object_id? 16 bytes? The NFS filehandle is 32 bytes wide (at maximum), so where is the problem (except maybe that object_ids are converted to VFS inode numbers, which are exportet then by nfsd, but this is a linux-, not a NFS-problem)? Xuân. From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:10:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HNAQP12385 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:10:26 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HNAPV12362 for ; Tue, 17 Jul 2001 16:10:25 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Mdyo-0008K5-00; Wed, 18 Jul 2001 01:10:14 +0200 Message-ID: <3B54C5D5.D6CF42C8@berdmann.de> Date: Wed, 18 Jul 2001 01:10:13 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: "Gonyou, Austin" CC: Linux XFS Mailing List Subject: Re: dumping multiple sessions to a single tape with XFS dump. References: <85063BBE668FD411944400D0B744267A64344C@AUSMAIL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I still can't do it. If anyone could show me their scripts or perhaps give a > brief example, I'd like to see it. Thanks. Maybe you want to use the non-rewinding tape device when xfsdump does not directly access TAPE as -f? From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:15:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HNFlX13134 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:15:47 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HNFjV13111 for ; Tue, 17 Jul 2001 16:15:45 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6HNFbNe094561; Tue, 17 Jul 2001 18:15:37 -0500 (CDT) Message-ID: <3B54C6E5.D3BF97A@thebarn.com> Date: Tue, 17 Jul 2001 18:14:45 -0500 From: cattelan@thebarn.com X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1_PR3 i686) X-Accept-Language: en MIME-Version: 1.0 To: Eric Bayer CC: linux-xfs@oss.sgi.com Subject: Re: Feedback References: <200107172313.f6HND4Z12767@oss.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Bayer wrote: > This message was sent from http://linux-xfs.sgi.com/projects/xfs/index.html > > ---- > > Your webpages don't mention it so it may be an accidental omission but your Redhat 2.4.3 kernal rpm lacks the devfs support. I just thought I'd mention it as it should either be shown as a change or in there. Apparently security holes exist in the devfs code, so it was disabled until they have been plugged. But yes good point it would be good to mention that item on the web page. > > > -Eric von Bayer From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:22:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HNMxn14016 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:22:59 -0700 Received: from ente.berdmann.de (pD9011841.dip.t-dialin.net [217.1.24.65]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HNMvV13988 for ; Tue, 17 Jul 2001 16:22:57 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MeB1-0008Nh-00; Wed, 18 Jul 2001 01:22:51 +0200 Message-ID: <3B54C8CB.F916DEB7@berdmann.de> Date: Wed, 18 Jul 2001 01:22:51 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: "Gonyou, Austin" CC: Linux XFS Mailing List Subject: Re: dumping multiple sessions to a single tape with XFS dump. References: <85063BBE668FD411944400D0B744267A64344D@AUSMAIL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I've done xfsdump -f /dev/nst0 -L "Some Label1" -m "test" /filesystem1 > then xfsdump -f /dev/nst0 -L "Some Label2" -m "test" /filesystem2 > then mt /dev/st0 rewind > When I perform xfsrestore -t -f /dev/st0, I ONLY get the first FS dump. > Nothing else. What's up? You'll to use "mt fsf " to access the second, third, forth... xfsdump image on tape. From owner-linux-xfs@oss.sgi.com Tue Jul 17 16:39:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6HNdO115403 for linux-xfs-outgoing; Tue, 17 Jul 2001 16:39:24 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6HNdKV15381 for ; Tue, 17 Jul 2001 16:39:20 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id BAA404945 for ; Wed, 18 Jul 2001 01:39:03 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA34261; Wed, 18 Jul 2001 09:37:55 +1000 (EST) Date: Wed, 18 Jul 2001 09:37:55 +1000 From: Timothy Shimmin To: "Bernhard R. Erdmann" , Steve Lord Cc: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsrestore (Linux) generating Amanda's index Message-ID: <20010718093755.Q11622@boing.melbourne.sgi.com> References: <200107172243.f6HMh3K02985@jen.americas.sgi.com> <3B54C1E4.ECD9EC9F@berdmann.de> <200107172243.f6HMh3K02985@jen.americas.sgi.com> <200107172257.f6HMvZu03041@jen.americas.sgi.com> <3B54C46A.D667F144@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B54C46A.D667F144@berdmann.de>; from be@berdmann.de on Wed, Jul 18, 2001 at 01:04:10AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Bernhard, On Wed, Jul 18, 2001 at 01:04:10AM +0200, Bernhard R. Erdmann wrote: > > Are you using real tape media, or a file, I suspect the file case could > > be smart enough not to do the split as it does not make a whole lot > > of sense there. > > Amanda triggers xfsdump to write to stdout while splitting it to go to > tape or a file on the holding disk (via network) and to xfsrestore > reading from stdin to generate an index. So xfsrestore shouldn't know > anything of an actual tape media. > BTW, the dump format for file and tape are different. If you are dumping to a file or stdout then it is in file format. If this file-format dump is written to tape and you tried to restore using xfsrestore directly from the tape (-f /dev/st0) then it wouldn't work. If you convert it back to a file or give it to restore on stdin, then it will work fine. Just something to keep in mind. On Tue, Jul 17, 2001 at 05:43:03PM -0500, Steve Lord wrote: > > It looks like xfsdump will break large files into chunks in the > dump archive. This has more to do with not splitting a record > in the dump archive between tape media than anything else I think. > It is also possible for an interrupted dump to be restored, and > really big files would tend to be a hinderence to this. > > I found this comment in the code: > > /* a regular file may be broken into several portions if its size > * is large. Each portion begins with a filehdr_t and is followed by > * several extents. > */ > > It looks like the inventory list code is reporting each individual > component of the file which it finds in the archive. Yep. It's reporting for each file record it comes across in the dump. As far as I know a regular file can be split into multiple records if: (1) we have multiple streams and when the data size is divided among the streams, the file in question falls over the boundary of the streams (the algorithm for deciding to split is a bit more complicated than this); (2) the file is greater than 16Mb, it is then split into 16Mb chunks (or extent groups as the code calls them) For Linux, we don't do any multi-threading which means we don't do any multiple streams, which means case (1) won't happen. Case (2) is what you are seeing. I actually have web page notes on xfsdump mentioning this among other stuff, perhaps I will look into putting this on oss if people are interested. On Wed, Jul 18, 2001 at 12:53:24AM +0200, Bernhard R. Erdmann wrote: > > Is this actually causing problems, or is it just a query as to why > > you see the odd names? > > Just being curious... I haven't recognized any problems yet. It just > causes an annoying listing of mangled filenames in addition to the > original filename in the index, my SysOps will ask me "How can we rely > on it if it's messing up the index? > Does it mess up the backup, too?" I think this is a little unfair. It _is_ displaying the contents of the dump - it is showing where the file records are split. > Does it mess up the backup, too? > and I have to write some more lines in the documentation just to ignore > these offset names... > I guess one could change the code and find another option letter to stop this from being reported - I don't know if it's worth it. --Tim From owner-linux-xfs@oss.sgi.com Tue Jul 17 17:50:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I0oK918145 for linux-xfs-outgoing; Tue, 17 Jul 2001 17:50:20 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I0oIV18125 for ; Tue, 17 Jul 2001 17:50:18 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id RAA07796 for ; Tue, 17 Jul 2001 17:50:02 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA07222; Wed, 18 Jul 2001 10:48:56 +1000 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA03145; Wed, 18 Jul 2001 10:48:56 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Wed, 18 Jul 2001 10:48:55 +1000 To: "Gonyou, Austin" cc: Linux XFS Mailing List Subject: Re: dumping multiple sessions to a single tape with XFS dump. In-Reply-To: <85063BBE668FD411944400D0B744267A64344C@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 17 Jul 2001, Gonyou, Austin wrote: > I still can't do it. If anyone could show me their scripts or perhaps give a > brief example, I'd like to see it. Thanks. Perhaps you could give us a little more detail: - why do you think it is not working for you (ie. specific symptoms) - the xfsdump command line you use - the output from xfsdump - the output of xfsdump -I - what else/if anything do you store on the tape (eg. tar files, etc) - what kind of tape device and driver do you use (eg. scsi, ide, etc) Thanks, Ivan -- Ivan Rayner ivanr@melbourne.sgi.com From owner-linux-xfs@oss.sgi.com Tue Jul 17 18:04:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I14O218670 for linux-xfs-outgoing; Tue, 17 Jul 2001 18:04:24 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I14MV18650 for ; Tue, 17 Jul 2001 18:04:22 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id SAA14371 for ; Tue, 17 Jul 2001 18:04:10 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 LAA07346; Wed, 18 Jul 2001 11:02:57 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA02991; Wed, 18 Jul 2001 11:02:55 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107181102.ZM195527@wobbly.melbourne.sgi.com> Date: Wed, 18 Jul 2001 11:02:53 +1000 In-Reply-To: Chris Bednar "am-utils xfs PATCH" (Jul 17, 3:19pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Chris Bednar , linux-xfs@oss.sgi.com Subject: Re: am-utils xfs PATCH Cc: amd-dev@cs.columbia.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Chris, On Jul 17, 3:19pm, Chris Bednar wrote: > Subject: am-utils xfs PATCH > > Hi > > The following are (1) a patch to am-utils-6.0.5 (a la > RedHat 7.1) to get it to build on a system with XFS installed, > and (2) a spec file for RPM with configure options to go with > the patch. > > This is pretty kludgy, but it does work... it basically just > adds an #include to amd/ops_xfs.c and adds > > --enable-am-cflags="-I/usr/include/xfs -Dxfs_args_t=xfs_da_args_t" > > to the configure. It's cheap and dirty, but it works. This doesn't look quite right - the xfs_args struct in IRIX is used to pass the mount arguments across the mount syscall interface (as binary data), but in Linux each filesystem's options are passed in as a comma separated list (a string of characters). xfs_da_args_t is something unrelated to mount(2), and is only for use within the kernel and libxfs. In general, you don't want to be #include'ing files from /usr/include/xfs/* at all. The right way to implement this would be to figure out how the other Linux filesystems are handled and do XFS (Linux/XFS, that is) the same way, then make the existing amd code for XFS only be used on IRIX. I've only had a quick look at the am-utils code just now, so can't really give you more advice than that, I'm afraid. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jul 17 18:12:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I1CIq19020 for linux-xfs-outgoing; Tue, 17 Jul 2001 18:12:18 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I1CHV18999 for ; Tue, 17 Jul 2001 18:12:17 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id SAA02621 for ; Tue, 17 Jul 2001 18:09:48 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 LAA07420; Wed, 18 Jul 2001 11:10:57 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA14969; Wed, 18 Jul 2001 11:10:45 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107181110.ZM214271@wobbly.melbourne.sgi.com> Date: Wed, 18 Jul 2001 11:10:43 +1000 In-Reply-To: Eric Sandeen "Re: problems formatting partition via ks" (Jul 17, 10:03am) References: <200107162311.f6GNBKT21957@vertigo.incyte.com> <995382195.1063.2.camel@stout.americas.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Eric Sandeen , Will Francis Subject: Re: problems formatting partition via ks Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 17, 10:03am, Eric Sandeen wrote: > Subject: Re: problems formatting partition via ks > On 16 Jul 2001 16:11:20 -0700, Will Francis wrote: > > > when making /usr/local/net, it fails with these errors: > > Nathan's right, it's a limitation on the length of allowed labels in > XFS... I put the labeling code into the XFS installer to make it behave > more like the ext2 install, but didn't anticipate this. Whoops. I'll > put out an update floppy to fix this (by turning labels back off, I > suppose). > Is that necessary? Would you not get a similar error doing the same thing on ext2 (although with the upper limit at 16 rather than 12 chars)? I didn't see anything bad here, so far anyway... cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jul 17 18:23:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I1N4X19611 for linux-xfs-outgoing; Tue, 17 Jul 2001 18:23:04 -0700 Received: from age.cs.columbia.edu (IDENT:root@age.cs.columbia.edu [128.59.22.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I1N3V19591 for ; Tue, 17 Jul 2001 18:23:03 -0700 Received: from localhost (ionut@localhost) by age.cs.columbia.edu (8.11.2/8.9.3) with ESMTP id f6I1Muj03046; Tue, 17 Jul 2001 21:22:56 -0400 Date: Tue, 17 Jul 2001 21:22:55 -0400 (EDT) From: Ion Badulescu To: Nathan Scott cc: Chris Bednar , , Subject: Re: am-utils xfs PATCH In-Reply-To: <10107181102.ZM195527@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001, Nathan Scott wrote: > The right way to implement this would be to figure out how the > other Linux filesystems are handled and do XFS (Linux/XFS, that > is) the same way, then make the existing amd code for XFS only > be used on IRIX. I've only had a quick look at the am-utils > code just now, so can't really give you more advice than that, > I'm afraid. Can you guys check if this small patch fixes the compile? Thanks, Ion -- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt. ---------------------- Index: include/am_compat.h =================================================================== RCS file: /proj/bank/cvsroot/am-utils/include/am_compat.h,v retrieving revision 1.3.2.2 diff -u -r1.3.2.2 am_compat.h --- include/am_compat.h 2000/12/02 23:29:12 1.3.2.2 +++ include/am_compat.h 2001/07/18 01:21:47 @@ -265,6 +265,13 @@ # define efs_args_t u_int #endif /* defined(HAVE_FS_EFS) && !defined(efs_args_t) */ +/* + * if does not define struct xfs_args, assume integer bit-field (linux) + */ +#if defined(HAVE_FS_XFS) && !defined(xfs_args_t) +# define xfs_args_t u_int +#endif /* defined(HAVE_FS_XFS) && !defined(xfs_args_t) */ + #if defined(HAVE_FS_AUTOFS) && defined(MOUNT_TYPE_AUTOFS) && !defined(MNTTYPE_AUTOFS) # define MNTTYPE_AUTOFS "autofs" #endif /* defined(HAVE_FS_AUTOFS) && defined(MOUNT_TYPE_AUTOFS) && !defined(MNTTYPE_AUTOFS) */ From owner-linux-xfs@oss.sgi.com Tue Jul 17 18:29:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I1Txh19975 for linux-xfs-outgoing; Tue, 17 Jul 2001 18:29:59 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I1TvV19954 for ; Tue, 17 Jul 2001 18:29:57 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id DAA400914 for ; Wed, 18 Jul 2001 03:29:40 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA34621; Wed, 18 Jul 2001 11:28:35 +1000 (EST) Date: Wed, 18 Jul 2001 11:28:35 +1000 From: Timothy Shimmin To: Andi Kleen Cc: Federico Sevilla III , Linux XFS Mailing List Subject: Re: [PATCH] Re: chacl question Message-ID: <20010718112834.R11622@boing.melbourne.sgi.com> References: <20010717165543.A21737@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010717165543.A21737@gruyere.muc.suse.de>; from ak@suse.de on Tue, Jul 17, 2001 at 04:55:43PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 17, 2001 at 04:55:43PM +0200, Andi Kleen wrote: > On Tue, Jul 17, 2001 at 09:29:01PM +0800, Federico Sevilla III wrote: > > But it says: > > > > chacl: "u::rwx,g::,o::,u:jijo:r-x,m::r-x" is an invalid ACL specification. > > You cannot have multiple 'u' specifikations. Yes you can :) You can't have multiple USER_OBJ ACE specifications (i.e. 'u::') but you certainly need multiple USER ACE specs (hence the multiple 'u'). As already pointed out, you need permissions specified for all ACEs (i.e. for GROUP and OTHER as well). > > Similar problems have also annoyed, annoyed me enough to produce the following > patch which adds somewhat usable error reporting to libacl. > > Just apply it below cmd/chacl and get at least usable error messages. > > It also fixes one bug in the manpage. Thanks. I'll have a look over it soon, run the qa tests and check it in...:) --tim From owner-linux-xfs@oss.sgi.com Tue Jul 17 18:42:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I1guB20470 for linux-xfs-outgoing; Tue, 17 Jul 2001 18:42:56 -0700 Received: from neutral (postfix@dhcp233054.columbus.rr.com [204.210.233.54]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I1gmV20451 for ; Tue, 17 Jul 2001 18:42:48 -0700 Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by neutral (Postfix (Debian/GNU)) with ESMTP id 72EBBF4D5 for ; Tue, 17 Jul 2001 21:42:19 -0400 (EDT) Received: by space-ghost (Postfix (Debian/GNU), from userid 1000) id 18106622F55; Tue, 17 Jul 2001 21:37:08 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: kernel oops X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Tue, 17 Jul 2001 21:37:05 -0400 Message-ID: <87wv57vwzi.church.of.emacs@cis.ohio-state.edu> Lines: 10 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --=-=-= My kernel oopsed again; unfortunately this time it didn't make it to syslog, so I don't have a backtrace, but I've included the output of xfs_repair. Is this useful? The only thing I can think of in common between this crash and the previous one is that I was using "apt-get" to install a package, in this case the Emacs Lisp manual. --=-=-= Content-Disposition: attachment; filename=actual-repair.log Content-Description: XFS repair log Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... error following ag 1 unlinked list error following ag 4 unlinked list error following ag 5 unlinked list - process known inodes and perform inode discovery... - agno = 0 - agno = 1 data fork in ino 6427581 claims free block 401739 data fork in ino 6427581 claims free block 401740 data fork in ino 6427581 claims free block 401741 data fork in ino 6427581 claims free block 401742 data fork in ino 6427581 claims free block 401743 data fork in ino 6427581 claims free block 401744 data fork in ino 6427581 claims free block 401745 data fork in ino 6427581 claims free block 401746 data fork in ino 6427581 claims free block 401747 data fork in ino 6427581 claims free block 401748 data fork in ino 6427581 claims free block 401749 data fork in ino 6427581 claims free block 401750 data fork in ino 6427581 claims free block 401751 data fork in ino 6427581 claims free block 401752 data fork in ino 6427581 claims free block 401753 data fork in ino 6427581 claims free block 401754 data fork in ino 6427581 claims free block 401755 data fork in ino 6427581 claims free block 401756 data fork in ino 6427581 claims free block 401757 data fork in ino 6427581 claims free block 401758 data fork in ino 6427581 claims free block 401759 data fork in ino 6427581 claims free block 401760 data fork in ino 6427581 claims free block 401761 data fork in ino 6427581 claims free block 401762 data fork in ino 6427581 claims free block 401763 data fork in ino 6427581 claims free block 401764 data fork in ino 6427581 claims free block 401765 data fork in ino 6427581 claims free block 401766 data fork in ino 6427581 claims free block 401767 data fork in ino 6427581 claims free block 401768 data fork in ino 6427581 claims free block 401769 data fork in ino 6427581 claims free block 401770 data fork in ino 6427581 claims free block 401771 data fork in ino 6427581 claims free block 401772 data fork in ino 6427581 claims free block 401773 data fork in ino 6427581 claims free block 401774 data fork in ino 6427581 claims free block 401775 data fork in ino 6427581 claims free block 401776 data fork in ino 6427581 claims free block 401777 data fork in ino 6427581 claims free block 401778 data fork in ino 6427581 claims free block 401779 data fork in ino 6427581 claims free block 401780 data fork in ino 6427581 claims free block 401781 data fork in ino 6427581 claims free block 401782 data fork in ino 6427581 claims free block 401783 data fork in ino 6427581 claims free block 401784 data fork in ino 6427581 claims free block 401785 data fork in ino 6427581 claims free block 401786 data fork in ino 6427581 claims free block 401787 data fork in ino 6427581 claims free block 401788 data fork in ino 6427581 claims free block 401789 data fork in ino 6427581 claims free block 401790 data fork in ino 6427581 claims free block 401791 data fork in ino 6427581 claims free block 401792 data fork in ino 6427581 claims free block 401793 data fork in ino 6427581 claims free block 401794 data fork in ino 6427581 claims free block 401795 data fork in ino 6427581 claims free block 401796 data fork in ino 6427581 claims free block 401797 data fork in ino 6427581 claims free block 401798 data fork in ino 6427581 claims free block 401799 data fork in ino 6427581 claims free block 401800 data fork in ino 6427581 claims free block 401801 data fork in ino 6427581 claims free block 401802 data fork in ino 6427581 claims free block 401803 data fork in ino 6427581 claims free block 401804 data fork in ino 6427581 claims free block 401805 data fork in ino 6427581 claims free block 401806 data fork in ino 6427581 claims free block 401807 data fork in ino 6427581 claims free block 401808 data fork in ino 6427581 claims free block 401809 data fork in ino 6427581 claims free block 401810 data fork in ino 6427581 claims free block 401811 data fork in ino 6427581 claims free block 401812 data fork in ino 6427581 claims free block 401813 data fork in ino 6427581 claims free block 401814 data fork in ino 6427581 claims free block 401815 data fork in ino 6427581 claims free block 401816 data fork in ino 6427581 claims free block 401817 data fork in ino 6427581 claims free block 401818 data fork in ino 6427581 claims free block 401819 data fork in ino 6427581 claims free block 401820 data fork in ino 6427581 claims free block 401821 data fork in ino 6427581 claims free block 401822 data fork in ino 6427581 claims free block 401823 data fork in ino 6427581 claims free block 401824 data fork in ino 6427581 claims free block 401825 data fork in ino 6427581 claims free block 401826 data fork in ino 6427581 claims free block 401827 data fork in ino 6427581 claims free block 401828 data fork in ino 6427581 claims free block 401829 data fork in ino 6427581 claims free block 401830 data fork in ino 6427581 claims free block 401831 data fork in ino 6427581 claims free block 401832 data fork in ino 6427581 claims free block 401833 data fork in ino 6427581 claims free block 401834 data fork in ino 6427581 claims free block 401835 data fork in ino 6427581 claims free block 401836 data fork in ino 6427581 claims free block 401837 data fork in ino 6427581 claims free block 401838 data fork in ino 6427581 claims free block 401839 data fork in ino 6427581 claims free block 401840 data fork in ino 6427581 claims free block 401841 data fork in ino 6427581 claims free block 401842 data fork in ino 6427581 claims free block 401843 data fork in ino 6427581 claims free block 401844 data fork in ino 6427581 claims free block 401845 data fork in ino 6427581 claims free block 401846 data fork in ino 6427581 claims free block 401847 data fork in ino 6427581 claims free block 401848 data fork in ino 6427581 claims free block 401849 data fork in ino 6427581 claims free block 401850 data fork in ino 6427581 claims free block 401851 data fork in ino 6427581 claims free block 401852 data fork in ino 6427581 claims free block 401853 data fork in ino 6427581 claims free block 401854 data fork in ino 6427581 claims free block 401855 data fork in ino 6427581 claims free block 401856 data fork in ino 6427581 claims free block 401857 data fork in ino 6427581 claims free block 401858 data fork in ino 6427581 claims free block 401859 data fork in ino 6427581 claims free block 401860 data fork in ino 6427581 claims free block 401861 data fork in ino 6427581 claims free block 401862 data fork in ino 6427581 claims free block 401863 data fork in ino 6427581 claims free block 401864 data fork in ino 6427581 claims free block 401865 data fork in ino 6427581 claims free block 401866 data fork in ino 6427581 claims free block 401867 data fork in ino 6427581 claims free block 401868 data fork in ino 6427581 claims free block 401869 data fork in ino 6427581 claims free block 401870 data fork in ino 6427581 claims free block 401871 data fork in ino 6427581 claims free block 401872 - agno = 2 - agno = 3 imap claims a free inode 15878407 is in use, correcting imap and clearing inode - agno = 4 imap claims in-use inode 16892310 is free, correcting imap data fork in ino 16958562 claims free block 1136394 imap claims in-use inode 16958562 is free, correcting imap imap claims a free inode 16958563 is in use, correcting imap and clearing inode - agno = 5 imap claims a free inode 22263571 is in use, correcting imap and clearing inode imap claims a free inode 22263572 is in use, correcting imap and clearing inode imap claims a free inode 22263573 is in use, correcting imap and clearing inode imap claims a free inode 22263574 is in use, correcting imap and clearing inode imap claims a free inode 22263575 is in use, correcting imap and clearing inode - agno = 6 imap claims a free inode 26843552 is in use, correcting imap and clearing inode imap claims a free inode 26843553 is in use, correcting imap and clearing inode imap claims a free inode 26843554 is in use, correcting imap and clearing inode imap claims a free inode 26843555 is in use, correcting imap and clearing inode imap claims a free inode 26843556 is in use, correcting imap and clearing inode imap claims a free inode 26843557 is in use, correcting imap and clearing inode imap claims a free inode 26843558 is in use, correcting imap and clearing inode cleared inode 26843558 imap claims a free inode 26843559 is in use, correcting imap and clearing inode imap claims a free inode 26843560 is in use, correcting imap and clearing inode imap claims a free inode 26843561 is in use, correcting imap and clearing inode imap claims a free inode 26843562 is in use, correcting imap and clearing inode imap claims a free inode 26843563 is in use, correcting imap and clearing inode imap claims a free inode 26843564 is in use, correcting imap and clearing inode imap claims a free inode 26843649 is in use, correcting imap and clearing inode imap claims a free inode 26843650 is in use, correcting imap and clearing inode imap claims a free inode 26843651 is in use, correcting imap and clearing inode imap claims a free inode 26843652 is in use, correcting imap and clearing inode imap claims a free inode 26843653 is in use, correcting imap and clearing inode imap claims a free inode 26843654 is in use, correcting imap and clearing inode imap claims a free inode 26843655 is in use, correcting imap and clearing inode imap claims a free inode 26843656 is in use, correcting imap and clearing inode imap claims a free inode 26843657 is in use, correcting imap and clearing inode imap claims a free inode 26843658 is in use, correcting imap and clearing inode imap claims a free inode 26843659 is in use, correcting imap and clearing inode imap claims a free inode 26843660 is in use, correcting imap and clearing inode imap claims a free inode 26843661 is in use, correcting imap and clearing inode imap claims a free inode 26843662 is in use, correcting imap and clearing inode imap claims a free inode 26843663 is in use, correcting imap and clearing inode imap claims a free inode 26843664 is in use, correcting imap and clearing inode imap claims a free inode 26843665 is in use, correcting imap and clearing inode imap claims a free inode 26843666 is in use, correcting imap and clearing inode imap claims a free inode 26843667 is in use, correcting imap and clearing inode imap claims a free inode 26843668 is in use, correcting imap and clearing inode imap claims a free inode 26843669 is in use, correcting imap and clearing inode imap claims a free inode 26843670 is in use, correcting imap and clearing inode imap claims a free inode 26843671 is in use, correcting imap and clearing inode imap claims a free inode 26843672 is in use, correcting imap and clearing inode imap claims a free inode 26843673 is in use, correcting imap and clearing inode imap claims a free inode 26843674 is in use, correcting imap and clearing inode imap claims a free inode 26843675 is in use, correcting imap and clearing inode imap claims a free inode 26843676 is in use, correcting imap and clearing inode imap claims a free inode 26843677 is in use, correcting imap and clearing inode imap claims a free inode 26843678 is in use, correcting imap and clearing inode imap claims a free inode 26843679 is in use, correcting imap and clearing inode - agno = 7 - agno = 8 imap claims a free inode 36753560 is in use, correcting imap and clearing inode imap claims a free inode 36753561 is in use, correcting imap and clearing inode imap claims a free inode 36753562 is in use, correcting imap and clearing inode - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - clear lost+found (if it exists) ... - clearing existing "lost+found" inode - marking entry "lost+found" to be deleted - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 entry "elisp-manual" at block 0 offset 3048 in directory inode 4808987 references free inode 22263571 clearing inode number in entry at offset 3048... - agno = 2 - agno = 3 entry "elisp-manual.list" at block 4 offset 2752 in directory inode 15878388 references free inode 15878407 clearing inode number in entry at offset 2752... - agno = 4 entry ".saves-11142-space-ghost~" at block 1 offset 2320 in directory inode 16930949 references free inode 16958563 clearing inode number in entry at offset 2320... - agno = 5 - agno = 6 entry "elisp-13.gz" at block 5 offset 184 in directory inode 26847070 references free inode 26843652 clearing inode number in entry at offset 184... entry "elisp-15.gz" at block 5 offset 256 in directory inode 26847070 references free inode 26843653 clearing inode number in entry at offset 256... entry "elisp-16.gz" at block 5 offset 328 in directory inode 26847070 references free inode 26843654 clearing inode number in entry at offset 328... entry "elisp-17.gz" at block 5 offset 400 in directory inode 26847070 references free inode 26843655 clearing inode number in entry at offset 400... entry "elisp-18.gz" at block 5 offset 472 in directory inode 26847070 references free inode 26843656 clearing inode number in entry at offset 472... entry "elisp-2.gz" at block 5 offset 544 in directory inode 26847070 references free inode 26843657 clearing inode number in entry at offset 544... entry "elisp-5.gz" at block 5 offset 616 in directory inode 26847070 references free inode 26843679 clearing inode number in entry at offset 616... entry "elisp-6.gz" at block 5 offset 672 in directory inode 26847070 references free inode 26843552 clearing inode number in entry at offset 672... entry "elisp-8.gz" at block 5 offset 728 in directory inode 26847070 references free inode 26843553 clearing inode number in entry at offset 728... entry "elisp-20.gz" at block 5 offset 784 in directory inode 26847070 references free inode 26843658 clearing inode number in entry at offset 784... entry "elisp-9.gz" at block 5 offset 856 in directory inode 26847070 references free inode 26843554 clearing inode number in entry at offset 856... entry "elisp.gz" at block 5 offset 912 in directory inode 26847070 references free inode 26843555 clearing inode number in entry at offset 912... entry "elisp-1.gz" at block 5 offset 968 in directory inode 26847070 references free inode 26843556 clearing inode number in entry at offset 968... entry "elisp-14.gz" at block 5 offset 1024 in directory inode 26847070 references free inode 26843557 clearing inode number in entry at offset 1024... entry "elisp-19.gz" at block 5 offset 1080 in directory inode 26847070 references free inode 26843558 clearing inode number in entry at offset 1080... entry "elisp-23.gz" at block 5 offset 1136 in directory inode 26847070 references free inode 26843559 clearing inode number in entry at offset 1136... entry "elisp-28.gz" at block 5 offset 1192 in directory inode 26847070 references free inode 26843560 clearing inode number in entry at offset 1192... entry "elisp-32.gz" at block 5 offset 1248 in directory inode 26847070 references free inode 26843561 clearing inode number in entry at offset 1248... entry "elisp-37.gz" at block 5 offset 1304 in directory inode 26847070 references free inode 26843562 clearing inode number in entry at offset 1304... entry "elisp-41.gz" at block 5 offset 1360 in directory inode 26847070 references free inode 26843563 clearing inode number in entry at offset 1360... entry "elisp-7.gz" at block 5 offset 1416 in directory inode 26847070 references free inode 26843564 clearing inode number in entry at offset 1416... entry "elisp-21.gz" at block 5 offset 1640 in directory inode 26847070 references free inode 26843659 clearing inode number in entry at offset 1640... entry "elisp-22.gz" at block 5 offset 2104 in directory inode 26847070 references free inode 26843660 clearing inode number in entry at offset 2104... entry "elisp-24.gz" at block 5 offset 2176 in directory inode 26847070 references free inode 26843661 clearing inode number in entry at offset 2176... entry "elisp-25.gz" at block 5 offset 2248 in directory inode 26847070 references free inode 26843662 clearing inode number in entry at offset 2248... entry "elisp-26.gz" at block 5 offset 2320 in directory inode 26847070 references free inode 26843663 clearing inode number in entry at offset 2320... entry "elisp-27.gz" at block 5 offset 2392 in directory inode 26847070 references free inode 26843664 clearing inode number in entry at offset 2392... entry "elisp-29.gz" at block 5 offset 2520 in directory inode 26847070 references free inode 26843665 clearing inode number in entry at offset 2520... entry "elisp-3.gz" at block 5 offset 2592 in directory inode 26847070 references free inode 26843666 clearing inode number in entry at offset 2592... entry "elisp-30.gz" at block 5 offset 2664 in directory inode 26847070 references free inode 26843667 clearing inode number in entry at offset 2664... entry "elisp-31.gz" at block 5 offset 2736 in directory inode 26847070 references free inode 26843668 clearing inode number in entry at offset 2736... entry "elisp-33.gz" at block 5 offset 2808 in directory inode 26847070 references free inode 26843669 clearing inode number in entry at offset 2808... entry "elisp-34.gz" at block 5 offset 2936 in directory inode 26847070 references free inode 26843670 clearing inode number in entry at offset 2936... entry "elisp-35.gz" at block 5 offset 3008 in directory inode 26847070 references free inode 26843671 clearing inode number in entry at offset 3008... entry "elisp-36.gz" at block 5 offset 3080 in directory inode 26847070 references free inode 26843672 clearing inode number in entry at offset 3080... entry "elisp-38.gz" at block 5 offset 3152 in directory inode 26847070 references free inode 26843673 clearing inode number in entry at offset 3152... entry "elisp-39.gz" at block 5 offset 3280 in directory inode 26847070 references free inode 26843674 clearing inode number in entry at offset 3280... entry "elisp-4.gz" at block 5 offset 3352 in directory inode 26847070 references free inode 26843675 clearing inode number in entry at offset 3352... entry "elisp-40.gz" at block 5 offset 3424 in directory inode 26847070 references free inode 26843676 clearing inode number in entry at offset 3424... entry "elisp-42.gz" at block 5 offset 3720 in directory inode 26847070 references free inode 26843677 clearing inode number in entry at offset 3720... entry "elisp-43.gz" at block 5 offset 3792 in directory inode 26847070 references free inode 26843678 clearing inode number in entry at offset 3792... entry "elisp-10.gz" at block 5 offset 3896 in directory inode 26847070 references free inode 26843649 clearing inode number in entry at offset 3896... entry "elisp-11.gz" at block 5 offset 3952 in directory inode 26847070 references free inode 26843650 clearing inode number in entry at offset 3952... entry "elisp-12.gz" at block 5 offset 4008 in directory inode 26847070 references free inode 26843651 clearing inode number in entry at offset 4008... - agno = 7 - agno = 8 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - ensuring existence of lost+found directory - traversing filesystem starting at / ... rebuilding directory inode 128 rebuilding directory inode 15878388 rebuilding directory inode 26847070 rebuilding directory inode 4808987 rebuilding directory inode 16930949 - traversal finished ... - traversing all unattached subtrees ... - traversals finished ... - moving disconnected inodes to lost+found ... disconnected inode 4347291, moving to lost+found disconnected inode 17076037, moving to lost+found disconnected inode 17092632, moving to lost+found disconnected inode 17110563, moving to lost+found disconnected inode 17110572, moving to lost+found disconnected inode 21675682, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 16931969 nlinks from 1 to 2 resetting inode 16958520 nlinks from 1 to 2 done --=-=-=-- From owner-linux-xfs@oss.sgi.com Tue Jul 17 19:05:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I25aL21223 for linux-xfs-outgoing; Tue, 17 Jul 2001 19:05:36 -0700 Received: from cmmaustralia.com (IDENT:qmailr@[203.34.190.215]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I25XV21203 for ; Tue, 17 Jul 2001 19:05:33 -0700 Received: (qmail 12997 invoked by uid 506); 18 Jul 2001 02:05:10 -0000 Received: from list@fornax.net by cmma.cmmaustralia.com with qmail-scanner-0.94 (. Clean. Processed in 0.024371 secs); 18/07/2001 11:35:10 Received: from adl-office.airnet.com.au (HELO fornax.net) (203.34.190.136) by cmma.airnet.com.au with SMTP; 18 Jul 2001 02:05:09 -0000 Message-ID: <3B54EF89.9060806@fornax.net> Date: Wed, 18 Jul 2001 11:38:09 +0930 From: Andrew Hill User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.6 i686; en-US; rv:0.9.1) Gecko/20010622 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: mkfs.xfs: warning - cannot set blocksize on block device Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Firstly, my apologies if this has been covered before, but I'm new to XFS and couldn't see anything about this in the FAQ or the last couple of months of the mailing list archive - but I may have just missed it. I have just upgraded my Linux machine to RedHat 7.1, and installed a 2.4.6 kernel, which (yay!) has support for my Promise 20265 RAID controller. I have used the "snapshot" 2.4.6 kernel patch, and made sure that in the Filesystems section of the kernel, both "Page Buffer support" and "SGI XFS filesystem support" are selected. This seems to go okay, and the kernel boots without any apparent problem, including the 2 RAID devices on the Prmoise controller being available as /dev/hde and /dev/hdf (I am booting of a normal IDE drive.) I have then installed the following RPMs: acl-1.0.7-0.i386.rpm acl-devel-1.0.7-0.i386.rpm attr-1.0.3-0.i386.rpm attr-devel-1.0.3-0.i386.rpm dmapi-0.1.1-0.i386.rpm dmapi-devel-0.1.1-0.i386.rpm xfsdump-1.0.9-0.i386.rpm xfsprogs-1.2.8-0.i386.rpm xfsprogs-devel-1.2.8-0.i386.rpm So, I think that I should now be ready to create an XFS filesystem. I use fdisk to create a normal primary partition on /dev/hde, of type 83. This is fine. I can also test that the drive seems to be okay by creating an e2fs on this partition: ---- [root@slave-i /root]# mke2fs /dev/hde1 mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 4889248 inodes, 9770662 blocks 488533 blocks (5.00%) reserved for the super user First data block=0 299 block groups 32768 blocks per group, 32768 fragments per group 16352 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, 4096000, 7962624 Writing inode tables: done Writing superblocks and filesystem accounting information: done ---- However, when I try to create an XFS on the partition, I get the following error: ---- [root@slave-i /root]# mkfs -t xfs -f /dev/hde1 mkfs.xfs: warning - cannot set blocksize on block device /dev/hde1: Input/output error meta-data=/dev/hde1 isize=256 agcount=38, agsize=262144 blks data = bsize=4096 blocks=9770662, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=1200 realtime =none extsz=65536 blocks=0, rtextents=0 ---- If anyone has any ideas ahout what I am doing wrong/is going wrong, it would be greatly appreciated. Cheers, Andrew From owner-linux-xfs@oss.sgi.com Tue Jul 17 19:33:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I2XJc22278 for linux-xfs-outgoing; Tue, 17 Jul 2001 19:33:19 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I2XGV22259 for ; Tue, 17 Jul 2001 19:33:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id TAA04804 for ; Tue, 17 Jul 2001 19:30:48 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id VAA2430356; Tue, 17 Jul 2001 21:31:59 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id VAA05757; Tue, 17 Jul 2001 21:31:58 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6I2X5p03472; Tue, 17 Jul 2001 21:33:05 -0500 Message-Id: <200107180233.f6I2X5p03472@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Hill cc: linux-xfs@oss.sgi.com Subject: Re: mkfs.xfs: warning - cannot set blocksize on block device In-Reply-To: Message from Andrew Hill of "Wed, 18 Jul 2001 11:38:09 +0930." <3B54EF89.9060806@fornax.net> Date: Tue, 17 Jul 2001 21:33:04 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, You are doing nothing wrong. XFS is using an extra ioctl to set the block size of the device, it is not implemented for this device. However, a recent review of the code seems to show that we do not need actually need the ioctl anymore. Since the filesystem was made anyway, this is a message you should be able to ignore. Try mounting the filesystem and see what happens. Steve > Hi, > > Firstly, my apologies if this has been covered before, but I'm new to > XFS and couldn't see anything about this in the FAQ or the last couple > of months of the mailing list archive - but I may have just missed it. > > I have just upgraded my Linux machine to RedHat 7.1, and installed a > 2.4.6 kernel, which (yay!) has support for my Promise 20265 RAID > controller. I have used the "snapshot" 2.4.6 kernel patch, and made > sure that in the Filesystems section of the kernel, both "Page Buffer > support" and "SGI XFS filesystem support" are selected. > > This seems to go okay, and the kernel boots without any apparent > problem, including the 2 RAID devices on the Prmoise controller being > available as /dev/hde and /dev/hdf (I am booting of a normal IDE drive.) > > I have then installed the following RPMs: > > acl-1.0.7-0.i386.rpm > acl-devel-1.0.7-0.i386.rpm > attr-1.0.3-0.i386.rpm > attr-devel-1.0.3-0.i386.rpm > dmapi-0.1.1-0.i386.rpm > dmapi-devel-0.1.1-0.i386.rpm > xfsdump-1.0.9-0.i386.rpm > xfsprogs-1.2.8-0.i386.rpm > xfsprogs-devel-1.2.8-0.i386.rpm > > So, I think that I should now be ready to create an XFS filesystem. > > I use fdisk to create a normal primary partition on /dev/hde, of type > 83. This is fine. I can also test that the drive seems to be okay by > creating an e2fs on this partition: > > ---- > > [root@slave-i /root]# mke2fs /dev/hde1 > mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 > Filesystem label= > OS type: Linux > Block size=4096 (log=2) > Fragment size=4096 (log=2) > 4889248 inodes, 9770662 blocks > 488533 blocks (5.00%) reserved for the super user > First data block=0 > 299 block groups > 32768 blocks per group, 32768 fragments per group > 16352 inodes per group > Superblock backups stored on blocks: > 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208, > 4096000, 7962624 > > Writing inode tables: done > Writing superblocks and filesystem accounting information: done > > ---- > > However, when I try to create an XFS on the partition, I get the > following error: > > ---- > > [root@slave-i /root]# mkfs -t xfs -f /dev/hde1 > mkfs.xfs: warning - cannot set blocksize on block device /dev/hde1: > Input/output error > meta-data=/dev/hde1 isize=256 agcount=38, agsize=262144 blks > data = bsize=4096 blocks=9770662, imaxpct=25 > = sunit=0 swidth=0 blks, unwritten=0 > naming =version 2 bsize=4096 > log =internal log bsize=4096 blocks=1200 > realtime =none extsz=65536 blocks=0, rtextents=0 > > ---- > > If anyone has any ideas ahout what I am doing wrong/is going wrong, it > would be greatly appreciated. > > Cheers, > > Andrew From owner-linux-xfs@oss.sgi.com Tue Jul 17 19:43:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I2h9G22800 for linux-xfs-outgoing; Tue, 17 Jul 2001 19:43:09 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I2h6V22780 for ; Tue, 17 Jul 2001 19:43:07 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id EAA404734 for ; Wed, 18 Jul 2001 04:42:52 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id VAA2435588; Tue, 17 Jul 2001 21:41:47 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id VAA54887; Tue, 17 Jul 2001 21:41:47 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6I2grN03496; Tue, 17 Jul 2001 21:42:53 -0500 Message-Id: <200107180242.f6I2grN03496@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Colin Walters cc: linux-xfs@oss.sgi.com Subject: Re: kernel oops In-Reply-To: Message from Colin Walters of "Tue, 17 Jul 2001 21:37:05 EDT." <87wv57vwzi.church.of.emacs@cis.ohio-state.edu> Date: Tue, 17 Jul 2001 21:42:53 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > --=-=-= > > My kernel oopsed again; unfortunately this time it didn't make it to > syslog, so I don't have a backtrace, but I've included the output of > xfs_repair. Is this useful? > > The only thing I can think of in common between this crash and the > previous one is that I was using "apt-get" to install a package, in > this case the Emacs Lisp manual. > Hmm not sure what we can deduce from this unfortunately, I suspect you ran repair on the filesystem before it had been mounted again. It is a slightly non-obvious issue with repair that it does not replay the log, and if you had replayed the log the chances are that the filesystem would have been almost, if not completely, clean. So the repair output and the crash are probably totally unrelated. I will take a look at your original report tomorrow and see what I can deduce from that. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 17 20:52:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I3qqu26409 for linux-xfs-outgoing; Tue, 17 Jul 2001 20:52:52 -0700 Received: from neutral (postfix@dhcp233054.columbus.rr.com [204.210.233.54]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I3qnV26390 for ; Tue, 17 Jul 2001 20:52:49 -0700 Received: from space-ghost (space-ghost.verbum.org [192.168.5.90]) by neutral (Postfix (Debian/GNU)) with ESMTP id 216FAF4D5 for ; Tue, 17 Jul 2001 23:52:30 -0400 (EDT) Received: by space-ghost (Postfix (Debian/GNU), from userid 1000) id 61B57622F55; Tue, 17 Jul 2001 22:46:06 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: Re: kernel oops References: <200107180242.f6I2grN03496@jen.americas.sgi.com> X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Tue, 17 Jul 2001 22:46:06 -0400 In-Reply-To: <200107180242.f6I2grN03496@jen.americas.sgi.com> (Steve Lord's message of "Tue, 17 Jul 2001 21:42:53 -0500") Message-ID: <87ofqjvtsh.church.of.emacs@cis.ohio-state.edu> Lines: 22 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord writes: > Hmm not sure what we can deduce from this unfortunately, I suspect > you ran repair on the filesystem before it had been mounted again. > It is a slightly non-obvious issue with repair that it does not > replay the log, and if you had replayed the log the chances are that > the filesystem would have been almost, if not completely, clean. So > the repair output and the crash are probably totally unrelated. Oh. I indeed didn't realize that. Maybe if the log isn't empty, the repair program could issue a warning, or perhaps just replay the log itself? I'll be sure to mount the filesystem before doing xfs_repair in the future, though. > I will take a look at your original report tomorrow and see what I > can deduce from that. Ok. I notice that the PowerPC kernel maintainer has merged his changes up to Linus's 2.4.7-pre6; Is it worth upgrading, or should I just stick with 2.4.6? Thanks again for the help. From owner-linux-xfs@oss.sgi.com Tue Jul 17 20:58:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I3wC226863 for linux-xfs-outgoing; Tue, 17 Jul 2001 20:58:12 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I3w9V26844 for ; Tue, 17 Jul 2001 20:58:10 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id FAA393933 for ; Wed, 18 Jul 2001 05:57:54 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 NAA08490; Wed, 18 Jul 2001 13:56:49 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id NAA16569; Wed, 18 Jul 2001 13:56:48 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107181356.ZM220095@wobbly.melbourne.sgi.com> Date: Wed, 18 Jul 2001 13:56:46 +1000 In-Reply-To: Colin Walters "Re: kernel oops" (Jul 17, 10:46pm) References: <200107180242.f6I2grN03496@jen.americas.sgi.com> <87ofqjvtsh.church.of.emacs@cis.ohio-state.edu> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Colin Walters , linux-xfs@oss.sgi.com Subject: Re: kernel oops Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 17, 10:46pm, Colin Walters wrote: > Subject: Re: kernel oops > Steve Lord writes: > > > Hmm not sure what we can deduce from this unfortunately, I suspect > > you ran repair on the filesystem before it had been mounted again. > > It is a slightly non-obvious issue with repair that it does not > > replay the log, and if you had replayed the log the chances are that > > the filesystem would have been almost, if not completely, clean. So > > the repair output and the crash are probably totally unrelated. > > Oh. I indeed didn't realize that. Maybe if the log isn't empty, the > repair program could issue a warning, or perhaps just replay the log > itself? I'll be sure to mount the filesystem before doing xfs_repair > in the future, though. > There's a fix going into IRIX to do just this at the moment, I'll merge it across to the Linux userspace once thats done. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jul 17 21:07:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I473V27526 for linux-xfs-outgoing; Tue, 17 Jul 2001 21:07:03 -0700 Received: from cmmaustralia.com (IDENT:qmailr@[203.34.190.215]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I470V27507 for ; Tue, 17 Jul 2001 21:07:01 -0700 Received: (qmail 14821 invoked by uid 506); 18 Jul 2001 04:06:42 -0000 Received: from list@fornax.net by cmma.cmmaustralia.com with qmail-scanner-0.94 (. Clean. Processed in 0.023132 secs); 18/07/2001 13:36:42 Received: from adl-office.airnet.com.au (HELO fornax.net) (203.34.190.136) by cmma.airnet.com.au with SMTP; 18 Jul 2001 04:06:42 -0000 Message-ID: <3B550C06.3080706@fornax.net> Date: Wed, 18 Jul 2001 13:39:42 +0930 From: Andrew Hill User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.6-xfs i686; en-US; rv:0.9.1) Gecko/20010622 X-Accept-Language: en-us MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: mkfs.xfs: warning - cannot set blocksize on block device References: <200107180233.f6I2X5p03472@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > You are doing nothing wrong. Actaully, I was! > Try mounting the filesystem and see what happens. I did this, and it reported that xfs was not supported by the kernel. A quick look in /proc/filesystems confirmed this, and another quick look in /boot confirmed that the new kernel I had made was not installed where I thought it was! After fixing this, and rebooting, creating the XFS file system proceedes without an error message, and mounting the filesystem is fine. Thanks! Andrew. From owner-linux-xfs@oss.sgi.com Tue Jul 17 22:24:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I5OXP31791 for linux-xfs-outgoing; Tue, 17 Jul 2001 22:24:33 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I5OVV31771 for ; Tue, 17 Jul 2001 22:24:31 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id WAA01417 for ; Tue, 17 Jul 2001 22:24:17 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA03061; Wed, 18 Jul 2001 15:23:10 +1000 (EST) Date: Wed, 18 Jul 2001 15:23:10 +1000 (EST) From: Nathan Scott Message-Id: <200107180523.PAA03061@snort.melbourne.sgi.com> To: roehrich@sgi.com, linux-xfs@oss.sgi.com Subject: TAKE - misc, dmapi Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dean - could you check over the dmapi related change for me, pls? I think we missed that one syssgi originally... and there'll be a need for it down the track. -- thanks. Date: Tue Jul 17 16:53:16 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99048a cmd/xfsprogs/libxfs/init.c - 1.9 cmd/xfsprogs/doc/CHANGES - 1.26 - fix sign of BLKGETSIZE ioctl argument in libxfs. Date: Tue Jul 17 22:18:52 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99054a linux/include/linux/xfs_fs.h - 1.25 linux/fs/xfs/linux/xfs_ioctl.c - 1.42 cmd/xfsprogs/include/xfs_fs.h - 1.6 cmd/xfsprogs/doc/CHANGES - 1.27 - updated with DMAPI "setdm_by_handle" details for dump/restore; + couple of minor code consistency tidy ups too. linux/fs/xfs_support/kmem.c - 1.11 - fix compiler warning - "function declaration isn't a prototype". From owner-linux-xfs@oss.sgi.com Tue Jul 17 22:54:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I5sKP01485 for linux-xfs-outgoing; Tue, 17 Jul 2001 22:54:20 -0700 Received: from mailman.mnd.com (adsfw.mnd.com [208.226.69.17] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I5sIV01464 for ; Tue, 17 Jul 2001 22:54:18 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id AAA08092; Wed, 18 Jul 2001 00:53:47 -0500 Date: Wed, 18 Jul 2001 00:53:53 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: Nathan Scott cc: linux-xfs@oss.sgi.com, amd-dev@cs.columbia.edu Subject: Re: am-utils xfs PATCH In-Reply-To: <10107181102.ZM195527@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001, Nathan Scott wrote: > This doesn't look quite right - the xfs_args struct in IRIX > is used to pass the mount arguments across the mount syscall > interface (as binary data), but in Linux each filesystem's > options are passed in as a comma separated list (a string of > characters). > > xfs_da_args_t is something unrelated to mount(2), and is only > for use within the kernel and libxfs. In general, you don't > want to be #include'ing files from /usr/include/xfs/* at all. > > The right way to implement this would be to figure out how the > other Linux filesystems are handled and do XFS (Linux/XFS, that > is) the same way, then make the existing amd code for XFS only > be used on IRIX. I've only had a quick look at the am-utils > code just now, so can't really give you more advice than that, > I'm afraid. Yeah, it was really just a stab in the dark, to get it to compile on my ppc system. I have to confess, I only use amd for NFS and local symlink mounts, so I don't need any other FS-specific support. I ran out of energy trying to figure out how to do it right. ``Right'', in my case, would be to figure out how to disable XFS in the config scripts. ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ From owner-linux-xfs@oss.sgi.com Tue Jul 17 23:14:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I6EHk03084 for linux-xfs-outgoing; Tue, 17 Jul 2001 23:14:17 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I6EEV03060 for ; Tue, 17 Jul 2001 23:14:14 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA24029; Wed, 18 Jul 2001 08:13:56 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA27273; Wed, 18 Jul 2001 08:13:55 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 192C157306; Wed, 18 Jul 2001 08:23:52 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 7204D25835; Wed, 18 Jul 2001 08:31:45 +0200 (CEST) Message-ID: <3B552936.4664DEA3@ch.sauter-bc.com> Date: Wed, 18 Jul 2001 08:14:14 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: xfs kernel problem References: <200107171657.f6HGvdV24138@oss.sgi.com> <995390918.8982.6.camel@stout.americas.sgi.com> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by relay.xlink.net id IAA24029 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6I6EEV03061 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen schrieb: > > On 17 Jul 2001 18:57:38 +0200, Krückel Oliver wrote: > > > Linux SuSE-7.1 with servarel patches from the officel SuSE web-server > > gcc: version 2.95.2 19991024 (release) > > Can you try compiling with a 2.91.66 gcc version? This is the first > thing I'd try, newer compilers still have not been producing > consistently good code. > > > if i reboot the server with the xfs kernel and the server coms up > there are > > sum files and executables witch i can't access ore execute, > > > > sum examples: the programms find, make, ... or file hosts, ... > > Just try rpm -Va to check filesystem consistency (at least of system files). This should give you a short list of config files but no executable files. I guess the MegaRAID is going crazy with you. > > if i reboot the server again, there are much more files that can't > access or > > execute, there are alwais other executebles and files by every test, > > Can you give any more information about "can't access" - do they not > show up in the directory listing, do they seem to contain wrong data... > ? > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. -- Simon Matter From owner-linux-xfs@oss.sgi.com Tue Jul 17 23:14:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I6Elt03237 for linux-xfs-outgoing; Tue, 17 Jul 2001 23:14:47 -0700 Received: from mailman.mnd.com (adsfw.mnd.com [208.226.69.17] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I6EkV03218 for ; Tue, 17 Jul 2001 23:14:46 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id BAA08604; Wed, 18 Jul 2001 01:14:14 -0500 Date: Wed, 18 Jul 2001 01:14:19 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: Ion Badulescu cc: Nathan Scott , linux-xfs@oss.sgi.com, amd-dev@cs.columbia.edu Subject: Re: am-utils xfs PATCH In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 17 Jul 2001, Ion Badulescu wrote: > Can you guys check if this small patch fixes the compile? > diff -u -r1.3.2.2 am_compat.h > --- include/am_compat.h 2000/12/02 23:29:12 1.3.2.2 > +++ include/am_compat.h 2001/07/18 01:21:47 Yep. That hits the spot; thanks! ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ From owner-linux-xfs@oss.sgi.com Tue Jul 17 23:18:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I6I1O03542 for linux-xfs-outgoing; Tue, 17 Jul 2001 23:18:01 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I6HwV03518 for ; Tue, 17 Jul 2001 23:17:58 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA24470; Wed, 18 Jul 2001 08:17:56 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA27676; Wed, 18 Jul 2001 08:17:56 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id DC0C557306; Wed, 18 Jul 2001 08:27:20 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 4915025835; Wed, 18 Jul 2001 08:35:14 +0200 (CEST) Message-ID: <3B552A07.EA951D7E@ch.sauter-bc.com> Date: Wed, 18 Jul 2001 08:17:43 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Jani Jaakkola Cc: linux-xfs@oss.sgi.com Subject: Re: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jani Jaakkola schrieb: > > On Tue, 17 Jul 2001, Steve Lord wrote: > > > > > Could you possibly try the cvs tree, Linus was still working deadlocks > > out of the memory allocation/reclaim end of things up until 2.4.7-pre2. > > XFS and ext2 will almost certainly push things in different directions. > > OK I'll try it.. > > Right, it has now been running longer than ever before without a lockup. > However, the performance is very bad. But it just might be caused by the > simultaneous RAID resync I am doing at the same time. I'll get back to > this after the resync is done (or the machine has crashed). Until you force faster resync with the proc switches, it should not slow down usual operations as SoftRAID is using IO idle to resync. > > > Another issue here is that you may actually be creating inode numbers with > > greated than 32 bits in them with a filesystem this size. If you run > > xfs_growfs -n on the mount point of the filesystem and run the attached > > perl script with the following arguments it will tell you how many bits > > your inodes can consume. > > > > > You can play with numbers to make the number of bits <= 32, increasing > > the inode size will be the thing which does it for you, also if you > > did not end up with 4GB allocation groups you should attempt to get > > them setup that way. Unfortunately this means mkfs to fix. > > > > I do have some plans to make this issue go away for large filesystems, but > > you beat me to it! > > I had inode size exactly 32 bits and 4GB allocation groups, but I still > recreated the file system (no problem, since I'm still only testing the > sw and hw): > > # /sbin/mkfs.xfs -f -Lfs -dagsize=4g -isize=512 /dev/md0 > meta-data=/dev/md0 isize=512 agcount=254, agsize=1048576 > blks > data = bsize=4096 blocks=265939776, imaxpct=25 > = sunit=1 swidth=6 blks, unwritten=0 > naming =version 2 bsize=4096 > log =internal log bsize=4096 blocks=32463 > realtime =none extsz=24576 blocks=0, rtextents=0 > > Thanks for the advice! > > - Jani From owner-linux-xfs@oss.sgi.com Tue Jul 17 23:25:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I6PAI04160 for linux-xfs-outgoing; Tue, 17 Jul 2001 23:25:10 -0700 Received: from ente.berdmann.de (p3E9E732A.dip.t-dialin.net [62.158.115.42]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I6P8V04138 for ; Tue, 17 Jul 2001 23:25:08 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15MklY-0002Nf-00; Wed, 18 Jul 2001 08:25:00 +0200 Message-ID: <3B552BBC.C424C89B@berdmann.de> Date: Wed, 18 Jul 2001 08:25:00 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Ion Badulescu CC: Nathan Scott , Chris Bednar , linux-xfs@oss.sgi.com, amd-dev@cs.columbia.edu Subject: Re: am-utils xfs PATCH References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Can you guys check if this small patch fixes the compile? Yeah - it rocks to compile! From owner-linux-xfs@oss.sgi.com Tue Jul 17 23:29:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I6Tar04576 for linux-xfs-outgoing; Tue, 17 Jul 2001 23:29:36 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I6TYV04551 for ; Tue, 17 Jul 2001 23:29:34 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA26020; Wed, 18 Jul 2001 08:29:32 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA28445; Wed, 18 Jul 2001 08:29:31 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 297C157306; Wed, 18 Jul 2001 08:38:55 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id A3B5625835; Wed, 18 Jul 2001 08:46:48 +0200 (CEST) Message-ID: <3B552CBD.5BDA5DAF@ch.sauter-bc.com> Date: Wed, 18 Jul 2001 08:29:17 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Jani Jaakkola Cc: linux-xfs@oss.sgi.com Subject: Re: xfs lockup on 2.4.6-SMP kernel with 1.1TB filesystem References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Jani Jaakkola schrieb: > > On Tue, 17 Jul 2001, Steve Lord wrote: > > > > Right, it has now been running longer than ever before without a lockup. > > > However, the performance is very bad. But it just might be caused by the > > > simultaneous RAID resync I am doing at the same time. I'll get back to > > > this after the resync is done (or the machine has crashed). > > > > Yes, the resync will crucify performance until it is complete. I think you > > can control the rate it runs at - I would get it out of the way as soon > > as possible, I think it has nasty cache invalidation effects when running > > with XFS. > > Does that mean, that XFS could have problems with SW RAID rebuild > after a disk failure? After I get things running, I'm going to test what > happens when I remove a disk from hotswap and plug it back again in live > system. I need to have that working before putting the system to use (even > if it requires to spend some $$ on some RAID hardware). > > - Jani I did use sysctrl -w dev.raid.speed_limit_min=10000 to speed up RAID5 resync and I was afraid it could give me a problem but it did not. Whe forcing higher speed it does really slow down the system but I have never been able to produce an error. BTW: Is the RAID code in linus kernels the same like in RH kernels? I was using the RH-XFS 2.4.3-1.0.1 release. From owner-linux-xfs@oss.sgi.com Tue Jul 17 23:58:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I6wEq06565 for linux-xfs-outgoing; Tue, 17 Jul 2001 23:58:14 -0700 Received: from linuxone.co.kr (IDENT:postfix@[210.108.91.129]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I6wAV06543 for ; Tue, 17 Jul 2001 23:58:11 -0700 Received: from theadadv (unknown [61.74.150.119]) by linuxone.co.kr (Postfix) with SMTP id 7F32F3CC0 for ; Wed, 18 Jul 2001 15:58:08 +0900 (KST) Message-ID: <001201c10f57$0f660480$0a02a8c0@linuxone.co.kr> From: "Choi Moonbong" To: Subject: [Q] xfs_growfs error. Date: Wed, 18 Jul 2001 15:58:32 +0900 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01C10FA2.7ECF06A0" 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 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C10FA2.7ECF06A0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 SGkuDQoNCkkgc2V0dXAgU0dJIFhGUyBSZWxlYXNlIDEuMC4xICYgUmVkSGF0IDcuMSAmIExWTSAw LjkuMUJldGEuDQoNCkkgd2FudCB0byBncm93ICYgZGVjcmVhc2UgTFZNIFhGUyBwYXJ0aXRpb24u DQpJIG1ha2UgMTAyNE0gTFZNIHBhcnRpdGlvbiwgYW5kIHJ1biBta2ZzLnhmcy4NCkkgaGF2ZSAx MDI0TSB4ZnMgcGFydGl0aW9uLg0KQWZ0ZXIgSSAgdXNlICdsdmV4dGVuZCB0b29sJywgZ3JvdyBt eSB0ZXN0IGx2bSBwYXJ0aW9uICB0byAyMDQ4TS4NCkFuZCBJIHVzZSB4ZnNfZ3Jvd2ZzLCBncm93 IGJsb2NrIHNpemUgMzAwMDAwLg0KWEZTIHBhcnRpdGlvbiBpcyAxMTk1MjAwS2J5dGUgbm93Lg0K QW5kIEkgdGhpbmsgbW9yZSBiaWcgcGFydGlvbiwgYnV0IG15IGNvbXB1dGVyIGlzIGJlbG93IGVy cm9yLg0KDQp4ZnNfZ3Jvd2ZzIC1EIDMwMDAwMSAvbW50LzAxDQptZXRhLWRhdGE9L21udC8wMSAg ICAgICAgICAgICAgICBpc2l6ZT0yNTYgICAgYWdjb3VudD0xMCwgYWdzaXplPTMyNzY4IGJsa3MN CmRhdGEgICAgID0gICAgICAgICAgICAgICAgICAgICAgIGJzaXplPTQwOTYgICBibG9ja3M9MzAw MDAwLCBpbWF4cGN0PTI1DQogICAgICAgICAgICA9ICAgICAgICAgICAgICAgICAgICAgICBzdW5p dD0wICAgICAgc3dpZHRoPTAgYmxrcywgdW53cml0dGVuPTANCm5hbWluZyAgID12ZXJzaW9uIDIg ICAgICAgICAgICAgIGJzaXplPTQwOTYNCmxvZyAgICAgID1pbnRlcm5hbCAgICAgICAgICAgICAg IGJzaXplPTQwOTYgICBibG9ja3M9MTIwMA0KcmVhbHRpbWUgPW5vbmUgICAgICAgICAgICAgICAg ICAgZXh0c3o9NjU1MzYgIGJsb2Nrcz0wLCBydGV4dGVudHM9MA0KeGZzX2dyb3dmczogaW9jdGwg ZmFpbGVkIC0gWEZTX0lPQ19GU0dST1dGU0RBVEE6IFVua25vd24gZXJyb3IgOTkwDQoNCldoYXQg bWVhbnMgYWJvdmUgZXJyb3I/DQpXaGF0J3MgcHJvYmxlbT8NCg0KUGxlYXNlIFJlcGx5Lg0KVGhh bmsgeW91Lg0KDQpDaG9pIE1vb25ib25nLg0KDQo= ------=_NextPart_000_000F_01C10FA2.7ECF06A0 Content-Type: text/html; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWtz X2NfNTYwMS0xOTg3IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1T SFRNTCA1LjAwLjMzMTQuMjEwMCIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+PEZPTlQgc2l6ZT0yPkhpLjwvRk9O VD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZP TlQgc2l6ZT0yPkkgc2V0dXAgU0dJIFhGUyBSZWxlYXNlIDEuMC4xICZhbXA7IFJlZEhhdCA3LjEg JmFtcDsgTFZNIA0KMC45LjFCZXRhLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwv Rk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkkgd2FudCB0byBncm93ICZhbXA7 IGRlY3JlYXNlIExWTSBYRlMgcGFydGl0aW9uLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6 ZT0yPkkgbWFrZSAxMDI0TSBMVk0gcGFydGl0aW9uLCBhbmQgcnVuIG1rZnMueGZzLjwvRk9OVD48 L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkkgaGF2ZSAxMDI0TSB4ZnMgcGFydGl0aW9uLjwvRk9O VD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkFmdGVyIEkmbmJzcDsgdXNlICdsdmV4dGVuZCB0 b29sJywgZ3JvdyBteSB0ZXN0IGx2bSANCnBhcnRpb24mbmJzcDsgdG8gMjA0OE0uPC9GT05UPjwv RElWPg0KPERJVj48Rk9OVCBzaXplPTI+QW5kIEkgdXNlIHhmc19ncm93ZnMsIGdyb3cgYmxvY2sg c2l6ZSAzMDAwMDAuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+WEZTIHBhcnRpdGlv biBpcyAxMTk1MjAwS2J5dGUgbm93LjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkFu ZCBJIHRoaW5rIG1vcmUgYmlnIHBhcnRpb24sIGJ1dCBteSBjb21wdXRlciBpcyBiZWxvdyANCmVy cm9yLjwvRk9OVD48L0RJVj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj54 ZnNfZ3Jvd2ZzIC1EIDMwMDAwMSANCi9tbnQvMDE8QlI+bWV0YS1kYXRhPS9tbnQvMDEmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQppc2l6ZT0yNTYmbmJzcDsmbmJzcDsmbmJzcDsg YWdjb3VudD0xMCwgYWdzaXplPTMyNzY4IA0KYmxrczxCUj5kYXRhJm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7IA0KPSZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANCmJzaXplPTQwOTYmbmJzcDsmbmJzcDsgYmxv Y2tzPTMwMDAwMCwgaW1heHBjdD0yNTxCUj4mbmJzcDsmbmJzcDsgDQombmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQo9Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IA0K c3VuaXQ9MCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBzd2lkdGg9MCBibGtzLCANCnVu d3JpdHRlbj0wPEJSPm5hbWluZyZuYnNwOyZuYnNwOyA9dmVyc2lvbiANCjImbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz cDsmbmJzcDsgDQpic2l6ZT00MDk2PEJSPmxvZyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw OyANCj1pbnRlcm5hbCZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANCmJzaXplPTQwOTYmbmJz cDsmbmJzcDsgYmxvY2tzPTEyMDA8QlI+cmVhbHRpbWUgDQo9bm9uZSZuYnNwOyZuYnNwOyZuYnNw OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyANCmV4dHN6PTY1NTM2Jm5ic3A7IGJs b2Nrcz0wLCBydGV4dGVudHM9MDxCUj54ZnNfZ3Jvd2ZzOiBpb2N0bCBmYWlsZWQgLSANClhGU19J T0NfRlNHUk9XRlNEQVRBOiBVbmtub3duIGVycm9yIDk5MDwvRk9OVD48L0RJVj4NCjxESVY+Jm5i c3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5XaGF0IG1lYW5zIGFib3ZlIGVycm9yPzwvRk9O VD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPldoYXQncyBwcm9ibGVtPzwvRk9OVD48L0RJVj4N CjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5QbGVhc2UgUmVwbHkuPC9GT05U PjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+VGhhbmsgeW91LjwvRk9OVD48L0RJVj4NCjxESVY+ Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5DaG9pIE1vb25ib25nLjwvRk9OVD48L0RJ Vj4NCjxESVY+Jm5ic3A7PC9ESVY+PC9CT0RZPjwvSFRNTD4NCg== ------=_NextPart_000_000F_01C10FA2.7ECF06A0-- From owner-linux-xfs@oss.sgi.com Wed Jul 18 00:00:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6I70dI06850 for linux-xfs-outgoing; Wed, 18 Jul 2001 00:00:39 -0700 Received: from linuxone.co.kr (IDENT:postfix@[210.108.91.129]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6I70bV06831 for ; Wed, 18 Jul 2001 00:00:38 -0700 Received: from theadadv (unknown [61.74.150.119]) by linuxone.co.kr (Postfix) with SMTP id D04453CB0 for ; Wed, 18 Jul 2001 16:00:36 +0900 (KST) Message-ID: <001c01c10f57$67b0dca0$0a02a8c0@linuxone.co.kr> From: "Choi Moonbong" To: Subject: [Q] xfs_growfs erro Date: Wed, 18 Jul 2001 16:01:01 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" 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-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id f6I70cV06832 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi. I setup SGI XFS Release 1.0.1 & RedHat 7.1 & LVM 0.9.1Beta. I want to grow & decrease LVM XFS partition. I make 1024M LVM partition, and run mkfs.xfs. I have 1024M xfs partition. After I use 'lvextend tool', grow my test lvm partion to 2048M. And I use xfs_growfs, grow block size 300000. XFS partition is 1195200Kbyte now. And I think more big partion, but my computer is below error. xfs_growfs -D 300001 /mnt/01 meta-data=/mnt/01 isize=256 agcount=10, agsize=32768 blks data = bsize=4096 blocks=300000, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal bsize=4096 blocks=1200 realtime =none extsz=65536 blocks=0, rtextents=0 xfs_growfs: ioctl failed - XFS_IOC_FSGROWFSDATA: Unknown error 990 What means above error? What's problem? Please Reply. Thank you. Choi Moonbong. From owner-linux-xfs@oss.sgi.com Wed Jul 18 03:04:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IA4Kt19656 for linux-xfs-outgoing; Wed, 18 Jul 2001 03:04:20 -0700 Received: from relais-int8.globalintranet.net (mailgate.globalintranet.net [194.206.181.247]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IA4GV19629 for ; Wed, 18 Jul 2001 03:04:17 -0700 Received: from gglenat ([10.255.7.37]) by relais-int8.globalintranet.net (Netscape Messaging Server 4.15) with SMTP id GGNYM503.C4F for ; Wed, 18 Jul 2001 12:03:41 +0200 From: =?iso-8859-1?Q?GLENAT_Gr=E9gory?= To: Subject: Pb with XFS Date: Wed, 18 Jul 2001 12:03:50 +0200 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.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We encountered a big problem with the XFS Kernel ; in fact, we need to reboot the PC 5 times a day because it seems dead ... The Config : IBM Xserie 2 CPU P3 866 MHz 1 Go RAM tested with : Kernel XFS_enterprise 2.4 base SGi iso image Kernel XFS_enterprise 2.4.5 patch SGi Kernel XFS_SMP2.4 base SGi iso image A second Test with an other iBM eserver 2 CPU P3 1Ghz 1 Go RAm ..... I ll test it on Compaq proliant 2day ... RGDS From owner-linux-xfs@oss.sgi.com Wed Jul 18 03:35:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IAZNQ22062 for linux-xfs-outgoing; Wed, 18 Jul 2001 03:35:23 -0700 Received: from matrix.seed.net.tw (matrix.seed.net.tw [192.72.81.219]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IAZ9V22023 for ; Wed, 18 Jul 2001 03:35:20 -0700 Received: from [210.244.60.135] (helo=promise.com.tw) by mail.seed.net.tw with smtp (SEEDNet Mail Server v2.316f) id 15MofP-000Evz-00 for linux-xfs@oss.sgi.com; Wed, 18 Jul 2001 18:34:56 +0800 Received: from [192.168.204.47] by promise.com.tw (NTMail 3.02.13) with ESMTP id ga287280 for ; Wed, 18 Jul 2001 18:37:42 +0800 Message-ID: <010901c10f75$402b62e0$2fcca8c0@gibson> From: "DaiGS" To: Subject: how to grow my XFS Date: Wed, 18 Jul 2001 18:34:40 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0106_01C10FB8.4E37BF80" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0106_01C10FB8.4E37BF80 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable hi.... =20 Please teach me how to grow my XFS filesystem..... I had seen the manual of the xfs_growfs, but I got some problem on do it...... such as can not mount it , error code occur... Give me a direction for grow my XFS, or tell me what way to do = it... =20 Thank you very much....... ------=_NextPart_000_0106_01C10FB8.4E37BF80 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
    hi....
      
         Please teach me how to grow = my XFS=20 filesystem.....
         I had seen the manual of = the=20 xfs_growfs, but I got some problem
         on do it...... such as = can not=20 mount it ,  error code occur...
     
         Give me a=20 direction for grow my XFS, or tell me what way to do=20 it...
        
         Thank you very=20 much.......
    ------=_NextPart_000_0106_01C10FB8.4E37BF80-- From owner-linux-xfs@oss.sgi.com Wed Jul 18 03:56:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IAu8O24034 for linux-xfs-outgoing; Wed, 18 Jul 2001 03:56:08 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IAu6V24014 for ; Wed, 18 Jul 2001 03:56:06 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6IAu2e01908; Wed, 18 Jul 2001 12:56:02 +0200 Message-Id: <4.3.2.7.2.20010718125510.03406cd8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 12:55:18 +0200 To: GLENAT =?iso-8859-1?Q?Gr=E9gory?= , From: Seth Mos Subject: Re: Pb with XFS In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6IAu6V24016 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 12:03 18-7-2001 +0200, GLENAT Grégory wrote: >We encountered a big problem with the XFS Kernel ; in fact, we need to >reboot the PC 5 times a day because it seems dead ... >The Config : >IBM Xserie >2 CPU P3 866 MHz >1 Go RAM >tested with : >Kernel XFS_enterprise 2.4 base SGi iso image >Kernel XFS_enterprise 2.4.5 patch SGi >Kernel XFS_SMP2.4 base SGi iso image > >A second Test with an other iBM eserver >2 CPU P3 1Ghz >1 Go RAm > >..... > >I ll test it on Compaq proliant 2day ... > >RGDS Details please -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 03:56:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IAuWG24179 for linux-xfs-outgoing; Wed, 18 Jul 2001 03:56:32 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IAuUV24160 for ; Wed, 18 Jul 2001 03:56:30 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6IAtoe01900; Wed, 18 Jul 2001 12:55:54 +0200 Message-Id: <4.3.2.7.2.20010718125455.03401d08@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 12:55:06 +0200 To: "DaiGS" , From: Seth Mos Subject: Re: how to grow my XFS In-Reply-To: <010901c10f75$402b62e0$2fcca8c0@gibson> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 18:34 18-7-2001 +0800, DaiGS wrote: >hi.... > > Please teach me how to grow my XFS filesystem..... > I had seen the manual of the xfs_growfs, but I got some problem > on do it...... such as can not mount it , error code occur... > > Give me a direction for grow my XFS, or tell me what way to do it... > > Thank you very much....... Details please. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 04:32:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IBWOI27560 for linux-xfs-outgoing; Wed, 18 Jul 2001 04:32:24 -0700 Received: from wiley.ceo.com (66-2-81-28.customer.algx.net [66.2.81.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IBWLV27538 for ; Wed, 18 Jul 2001 04:32:21 -0700 Received: from mindspring.com (IDENT:danny@localhost [127.0.0.1]) by wiley.ceo.com (8.9.3/8.9.3) with ESMTP id HAA00961; Wed, 18 Jul 2001 07:51:22 -0400 Message-ID: <3B55783A.468D3C8B@mindspring.com> Date: Wed, 18 Jul 2001 07:51:22 -0400 From: Danny Cox Reply-To: dcox@connex.com Organization: Connex Inc X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: benchmarks (again) References: <995050427.3b4f43bb56ac3@horde.leathercollection.ph> <3B54B570.DF35CEDC@namesys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk All, One other point regarding benchmarks, it's relevancy depends upon the environment: when recovering from a "temporal power anomaly" [;-)] an XFS mount will usually take less than a second. Reiser can take several. Admittedly, I'm using Reiser as it exists on SuSE 7.1, and XFS as of this week's CVS, but an XFS mount was always quick (witnessed personally when I was helping to track down XFS/RAID5 incompatibilities...several times...every hour.... ;-). Yes, it's not the "normal mode", but when the system's down, and the users have their noses plastered on the glass staring at your back, that extra 4 seconds per filesystem can seem an eternity! -- "Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing had happened." -- Winston Churchill Danny From owner-linux-xfs@oss.sgi.com Wed Jul 18 05:21:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ICLEV32353 for linux-xfs-outgoing; Wed, 18 Jul 2001 05:21:14 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ICLDV32326 for ; Wed, 18 Jul 2001 05:21:13 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 7495F1AB0F for ; Wed, 18 Jul 2001 08:21:12 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id D9B246B2; Wed, 18 Jul 2001 08:21:11 -0400 (EDT) Date: Wed, 18 Jul 2001 08:21:11 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Pb with XFS Message-ID: <20010718082111.B28267@dkp.com> 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.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 18, 2001 at 12:03:50PM +0200, GLENAT Gr?gory wrote: > We encountered a big problem with the XFS Kernel ; in fact, we > need to reboot the PC 5 times a day because it seems dead ... We've had NIC related lockups; probably not what's causing your difficulty, but it might be something to look at anyway. Andrew Klaassen From owner-linux-xfs@oss.sgi.com Wed Jul 18 05:48:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ICmmM02431 for linux-xfs-outgoing; Wed, 18 Jul 2001 05:48:48 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ICmkV02412 for ; Wed, 18 Jul 2001 05:48:46 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6ICmje02436 for ; Wed, 18 Jul 2001 14:48:45 +0200 Message-Id: <4.3.2.7.2.20010718144631.034ba518@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 14:48:01 +0200 To: linux-xfs list From: GLENAT =?iso-8859-1?Q?Gr=E9gory?= (by way of Seth Mos ) Subject: RE: Pb with XFS Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk More Detail : Here what appairs in the boot (extract from dmsg ) ========== checking TSC synchronization across CPUs: passed. Setting commenced=1, go go go mtrr: your CPUs had inconsistent fixed MTRR settings mtrr: probably your BIOS does not setup all CPUs PCI: PCI BIOS revision 2.10 entry at 0xfd2fc, last bus=4 PCI: Using configuration type 1 ========== The BiPro 866 has a connected Raid 200Go formated with xfs . That's why I need that OS . The Other has no Raid . They have both 2 netwok adapter .One is the iBM product (drivers PCNet32) and the other is a gigabit ethernet (driver e1000) I make on one PC the 100BT as unique ethernet adapter and on the other it s the gigabit which is working .... I ve got SGi O2, O200, on the network and they reached the Raid with automount. On my IBM with the Raid, I ve installed amd (it s up) and nfs (up too), samba is up too. On the other PC, amd mount the file system of the Linux and of the O200 (which has a Raid connected to ) No message in var/log/messages !!!!!!!!!! What more detail do you need ? -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 06:02:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ID2uY03754 for linux-xfs-outgoing; Wed, 18 Jul 2001 06:02:56 -0700 Received: from skl1.ukl.uni-freiburg.de (skl1.ukl.uni-freiburg.de [193.196.199.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ID2rV03735 for ; Wed, 18 Jul 2001 06:02:53 -0700 Received: (qmail 29407 invoked by alias); 18 Jul 2001 13:02:50 -0000 Received: (qmail 29402 invoked from network); 18 Jul 2001 13:02:50 -0000 Received: from msm138.ukl.uni-freiburg.de (HELO ukl.uni-freiburg.de) (193.196.218.138) by skl1.ukl.uni-freiburg.de with SMTP; 18 Jul 2001 13:02:50 -0000 Message-ID: <3B5588FB.E24B23AD@ukl.uni-freiburg.de> Date: Wed, 18 Jul 2001 15:02:51 +0200 From: "Manfred W. Baumstark" Organization: Medizinische Universitaetsklink Freiburg X-Mailer: Mozilla 4.77 [en] (WinNT; U) X-Accept-Language: en,de MIME-Version: 1.0 To: linux-xfs list Subject: planing migration IRIX to Linux References: <4.3.2.7.2.20010718144631.034ba518@pop.xs4all.nl> Content-Type: multipart/mixed; boundary="------------EFEBA8C4B027CE20DD592B26" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------EFEBA8C4B027CE20DD592B26 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear Experts, I've got a new SCSII to IDE raid which I have to connect to an SGI O2 (IRIX) at present. Can you recommend me any mkfs, directory format, etc. options that are important if I want to be able to move the raid to a Linux box in the future? Thanks in advance Manfred --------------EFEBA8C4B027CE20DD592B26 Content-Type: text/x-vcard; charset=us-ascii; name="maba.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Manfred W. Baumstark Content-Disposition: attachment; filename="maba.vcf" begin:vcard n:Baumstark;Manfred tel;fax:+49 761 270 7470 tel;work:+49 761 270 7496 x-mozilla-html:TRUE org:University Hospital Freiburg;Rehabilitative and Preventive Sportsmedicine adr:;;Hugstetter Str. 55;Freiburg;;D-79106;Germany version:2.1 email;internet:manfred.baumstark@uni-freiburg.de title:Dr. x-mozilla-cpt:;29056 fn:Manfred Baumstark end:vcard --------------EFEBA8C4B027CE20DD592B26-- From owner-linux-xfs@oss.sgi.com Wed Jul 18 06:15:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IDFWP05118 for linux-xfs-outgoing; Wed, 18 Jul 2001 06:15:32 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IDFTV05098 for ; Wed, 18 Jul 2001 06:15:29 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6IDECe02552; Wed, 18 Jul 2001 15:14:12 +0200 Message-Id: <4.3.2.7.2.20010718151032.031c15f0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 15:13:28 +0200 To: "Manfred W. Baumstark" , linux-xfs list From: Seth Mos Subject: Re: planing migration IRIX to Linux In-Reply-To: <3B5588FB.E24B23AD@ukl.uni-freiburg.de> References: <4.3.2.7.2.20010718144631.034ba518@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 15:02 18-7-2001 +0200, Manfred W. Baumstark wrote: >Dear Experts, > >I've got a new SCSII to IDE raid which I have to connect to an SGI O2 >(IRIX) at present. Can you recommend me any mkfs, directory format, etc. >options that are important if I want to be able to move the raid to a Linux >box in the future? Make sure that the blocksize of the fs is the same as the pagesize under ia32. Which means you will need to mkfs.xfs it with 4K blocksize. Note that pagesize may vary depending on your system. A ia64 system probably comes with another page size like 8 or 16K. So you will need to anticipate what system you will be moving to. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 06:45:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IDjFT07736 for linux-xfs-outgoing; Wed, 18 Jul 2001 06:45:15 -0700 Received: from marraco.udl.es (gardeny.udl.es [193.144.12.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IDjBV07716 for ; Wed, 18 Jul 2001 06:45:12 -0700 Received: from eup.udl.es (fermat.udl.net [10.50.54.28]) by marraco.udl.es (8.9.3/8.8.5) with ESMTP id OAA16099; Wed, 18 Jul 2001 14:48:02 +0200 Received: by eup.udl.es (8.8.8+Sun/SMI-SVR4) id PAA17895; Wed, 18 Jul 2001 15:45:01 +0200 (MET DST) Date: Wed, 18 Jul 2001 15:45:01 +0200 (MET DST) From: fermin@eup.udl.es (Fermin Molina) Message-Id: <200107181345.PAA17895@eup.udl.es> To: linux-xfs@oss.sgi.com Subject: Re: Quota reporting for NFS mounts Cc: syrekron@iastate.edu X-Sun-Charset: US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > built from the source rpm. > > I have exported my /export partition over NFS which file system is XFS. > > I can mount this from client type machines, but when I try (on the > client) to list my quota, the command just hangs. I've run snoop on the > connection, and it appears that my server (sherlock) doesn't respond to > the client's (cousteau) requests. > > I also verified that rpc.rquotad is running on my server. > > Any idea how I can get remote quota reporting working? Similar configuration. My NFS-client machine is a Sun (Solaris 2.7). On my linux XFS-NFS server, rpc.rquotad segfaults when I run quota -v on the client (Sun). >From the Sun, I get a similar snoop trace... /Fermin > Here is the snoop output: > > [cousteau ~ 7]# snoop sherlock > Using device ec0 (promiscuous mode) > cousteau -> sherlock TCP D=111 S=661 Syn Seq=1727695818 Len=0 > Win=61440 > cousteau -> sherlock TCP D=111 S=661 Syn Seq=1727695818 Len=0 > Win=61440 > sherlock -> cousteau TCP D=661 S=111 Syn Ack=1727695819 > Seq=2875267868 Len=0 Win=5840 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Fin Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Fin Ack=2875267869 > Seq=1727695819 Len=0 Win=61320 > sherlock -> cousteau TCP D=661 S=111 Fin Ack=1727695820 > Seq=2875267869 Len=0 Win=5840 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267870 > Seq=1727695820 Len=0 Win=61320 > cousteau -> sherlock TCP D=111 S=661 Ack=2875267870 > Seq=1727695820 Len=0 Win=61320 > cousteau -> sherlock PORTMAP C GETPORT prog=100011 (RQUOTA) > vers=1 proto=UDP > cousteau -> sherlock PORTMAP C GETPORT prog=100011 (RQUOTA) > vers=1 proto=UDP (retransmit) > sherlock -> cousteau PORTMAP R GETPORT port=838 > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > cousteau -> sherlock RQUOTA C GETQUOTA Uid=0 Path=/export > (retransmit) > [cousteau ~ 8]# > > From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:08:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IE89P09569 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:08:09 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IE87V09550 for ; Wed, 18 Jul 2001 07:08:07 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6IE85e02828 for ; Wed, 18 Jul 2001 16:08:05 +0200 Message-Id: <4.3.2.7.2.20010718154812.033ffa00@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 16:07:22 +0200 To: linux-xfs list From: Seth Mos Subject: Alpha rpms Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have uploaded a few of the first rpms for alpha. These are not tested yet but they do install on a alpha machine. I am still working on getting a few kernel rpms compiled for the alpha. I have a bit of a problem testing these since the machines is not located anywhere near me. I expect to have something compiling this evening and packages later. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:10:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEATO09843 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:10:29 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEARV09824 for ; Wed, 18 Jul 2001 07:10:28 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6IEAQe02846 for ; Wed, 18 Jul 2001 16:10:26 +0200 Message-Id: <4.3.2.7.2.20010718160753.03e6c428@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 16:09:42 +0200 To: linux-xfs list From: Seth Mos Subject: Alpha packages Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk ehm... well... duh. http://iserv.nl/files/xfs/alpha The link to the files is always handy. I guess there was a error between the keyboard and the chair. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:20:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEKmK10590 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:20:48 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEKjV10565 for ; Wed, 18 Jul 2001 07:20:45 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6IELaG16043 for ; Wed, 18 Jul 2001 17:21:37 +0300 Date: Wed, 18 Jul 2001 17:19:30 +0300 (EEST) From: Jani Jaakkola To: Subject: Terrible xfs performance on current cvs kernel with sw RAID In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 17 Jul 2001, Jani Jaakkola wrote: > On Tue, 17 Jul 2001, Steve Lord wrote: > > > > > Could you possibly try the cvs tree, Linus was still working deadlocks > > out of the memory allocation/reclaim end of things up until 2.4.7-pre2. > > XFS and ext2 will almost certainly push things in different directions. > > OK I'll try it.. > > Right, it has now been running longer than ever before without a lockup. > However, the performance is very bad. But it just might be caused by the > simultaneous RAID resync I am doing at the same time. I'll get back to > this after the resync is done (or the machine has crashed). OK, no more lockups, but the horrible performance was not caused by RAID resync. It seems that the current cvs kernel has bad problems with sw RAID and xfs combined (and maybe SMP too). When untarring archive with lots of small files or using 'rm -r' I get 5 files created/removed per second, which is the performance of my last 286 with MSDOS :( The performance problem goes away if I don't use sw RAID. It also seems to be journal related, since there is no problems with just reading/writing big files. Bonnie tells me my block output is 37940K/sec and input is 133400K/sec with 4GB data. I must now leave this thing for a few days, but I guess I will try to find out what is wrong (however, I'm not a competent kernel hacker). - Jani From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:29:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IETpP11266 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:29:51 -0700 Received: from mgw-x1.nokia.com (mgw-x1.nokia.com [131.228.20.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IETmV11241 for ; Wed, 18 Jul 2001 07:29:49 -0700 Received: from esvir01nok.ntc.nokia.com (esvir01nokt.ntc.nokia.com [172.21.143.33]) by mgw-x1.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6IESe914733 for ; Wed, 18 Jul 2001 17:28:41 +0300 (EET DST) Received: from esebh24nok.ntc.nokia.com (unverified) by esvir01nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id for ; Wed, 18 Jul 2001 17:29:46 +0300 Received: by esebh24nok with Internet Mail Service (5.5.2652.78) id <3MSRSZK2>; Wed, 18 Jul 2001 17:29:46 +0300 Message-ID: <5EB7E309FC6E5C46A55F01B49E0CAE6D0553C5@esebe012.NOE.Nokia.com> From: Ext-Kamaljeet.Singh@nokia.com To: linux-xfs@oss.sgi.com Cc: Imad.Ossaily@nokia.com Subject: Xfs prblems with clearcase mvfs Date: Wed, 18 Jul 2001 17:29:41 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, We are facing problems with xfs version 1.0 (with kernel 2.4.2-2 on Redhat 7.1) with Clearcase version 4.1 for linux. when we try to load mvfs module, it gives structure check errors for following structures: Super-operations inode-operations File-operations Super-block inode dentry Could you please look into it and suggest us some good solution. We can provide more details if required. Thanks in Advance, Kamaljet Singh From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:34:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEYMR11630 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:34:22 -0700 Received: from roc-24-169-102-121.rochester.rr.com (roc-24-169-102-121.rochester.rr.com [24.169.102.121]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEYJV11603 for ; Wed, 18 Jul 2001 07:34:20 -0700 Received: from localhost ([127.0.0.1] helo=tiny) by roc-24-169-102-121.rochester.rr.com with esmtp (Exim 3.16 #4) id 15MsOb-0006hy-00; Wed, 18 Jul 2001 10:33:49 -0400 Date: Wed, 18 Jul 2001 10:33:49 -0400 From: Chris Mason To: dcox@connex.com, linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks (again) Message-ID: <224490000.995466829@tiny> In-Reply-To: <3B55783A.468D3C8B@mindspring.com> X-Mailer: Mulberry/2.0.8 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wednesday, July 18, 2001 07:51:22 AM -0400 Danny Cox wrote: > All, > > One other point regarding benchmarks, it's relevancy depends upon the > environment: when recovering from a "temporal power anomaly" [;-)] an > XFS mount will usually take less than a second. Reiser can take > several. > > Admittedly, I'm using Reiser as it exists on SuSE 7.1, and XFS as of > this week's CVS, but an XFS mount was always quick (witnessed personally > when I was helping to track down XFS/RAID5 incompatibilities...several > times...every hour.... ;-). > > Yes, it's not the "normal mode", but when the system's down, and the > users have their noses plastered on the glass staring at your back, that > extra 4 seconds per filesystem can seem an eternity! > ;-) XFS does logical logging, which allow them to use a very small log, and smaller logs take less time to process. reiserfs logs full blocks, and the journal code tries really hard to use the entire 32MB log before it starts flushing blocks to their real locations on disk. So, the reiserfs log replay time should be slightly longer than it takes your disk to read and write 32MB (in synchronous chunks from 12k to 4MB in size). -chris From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:34:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEYxi11679 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:34:59 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEYuV11657 for ; Wed, 18 Jul 2001 07:34:56 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA453258 for ; Wed, 18 Jul 2001 16:34:45 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2458033; Wed, 18 Jul 2001 09:33:36 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA72087; Wed, 18 Jul 2001 09:33:36 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IEYb804528; Wed, 18 Jul 2001 09:34:37 -0500 Message-Id: <200107181434.f6IEYb804528@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Seth Mos cc: "Manfred W. Baumstark" , linux-xfs list Subject: Re: planing migration IRIX to Linux In-Reply-To: Message from Seth Mos of "Wed, 18 Jul 2001 15:13:28 +0200." <4.3.2.7.2.20010718151032.031c15f0@pop.xs4all.nl> Date: Wed, 18 Jul 2001 09:34:37 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > At 15:02 18-7-2001 +0200, Manfred W. Baumstark wrote: > >Dear Experts, > > > >I've got a new SCSII to IDE raid which I have to connect to an SGI O2 > >(IRIX) at present. Can you recommend me any mkfs, directory format, etc. > >options that are important if I want to be able to move the raid to a Linux > >box in the future? > > Make sure that the blocksize of the fs is the same as the pagesize under ia32 > . > Which means you will need to mkfs.xfs it with 4K blocksize. > > Note that pagesize may vary depending on your system. A ia64 system > probably comes with another page size like 8 or 16K. So you will need to > anticipate what system you will be moving to. > > Cheers > And make sure you specify version 2 directories and turn off unwritten extents, so: mkfs -d unwritten=0 -n version=2 The default block size is 4K so that should be OK. Steve From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:35:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEZKJ11812 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:35:20 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEZIV11790 for ; Wed, 18 Jul 2001 07:35:18 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6IEZEe02933; Wed, 18 Jul 2001 16:35:15 +0200 Message-Id: <4.3.2.7.2.20010718163343.033e5ec8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 18 Jul 2001 16:34:31 +0200 To: Ext-Kamaljeet.Singh@nokia.com, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Xfs prblems with clearcase mvfs Cc: Imad.Ossaily@nokia.com In-Reply-To: <5EB7E309FC6E5C46A55F01B49E0CAE6D0553C5@esebe012.NOE.Nokia. com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:29 18-7-2001 +0300, Ext-Kamaljeet.Singh@nokia.com wrote: >Hi, >We are facing problems with xfs version 1.0 (with kernel 2.4.2-2 on Redhat >7.1) with Clearcase version 4.1 for linux. when we try to load mvfs module, >it gives structure check errors for following structures: >Super-operations >inode-operations >File-operations >Super-block >inode >dentry > >Could you please look into it and suggest us some good solution. We can >provide more details if required. Can you upgrade to the 1.0.1 release? That one has many fixes, tlhough I am not quite sure if it fixes this. Bye -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:36:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEai012077 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:36:44 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEafV12055 for ; Wed, 18 Jul 2001 07:36:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA453778 for ; Wed, 18 Jul 2001 16:36:30 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2462182; Wed, 18 Jul 2001 09:35:21 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA70439; Wed, 18 Jul 2001 09:35:21 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IEaMj04538; Wed, 18 Jul 2001 09:36:22 -0500 Message-Id: <200107181436.f6IEaMj04538@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jani Jaakkola cc: linux-xfs@oss.sgi.com Subject: Re: Terrible xfs performance on current cvs kernel with sw RAID In-Reply-To: Message from Jani Jaakkola of "Wed, 18 Jul 2001 17:19:30 +0300." Date: Wed, 18 Jul 2001 09:36:22 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Tue, 17 Jul 2001, Jani Jaakkola wrote: > > > On Tue, 17 Jul 2001, Steve Lord wrote: > > > > > > > > Could you possibly try the cvs tree, Linus was still working deadlocks > > > out of the memory allocation/reclaim end of things up until 2.4.7-pre2. > > > XFS and ext2 will almost certainly push things in different directions. > > > > OK I'll try it.. > > > > Right, it has now been running longer than ever before without a lockup. > > However, the performance is very bad. But it just might be caused by the > > simultaneous RAID resync I am doing at the same time. I'll get back to > > this after the resync is done (or the machine has crashed). > > OK, no more lockups, but the horrible performance was not caused by RAID > resync. It seems that the current cvs kernel has bad problems with sw > RAID and xfs combined (and maybe SMP too). When untarring archive with > lots of small files or using 'rm -r' I get 5 files created/removed per > second, which is the performance of my last 286 with MSDOS :( > > The performance problem goes away if I don't use sw RAID. It also seems > to be journal related, since there is no problems with just > reading/writing big files. Bonnie tells me my block output is 37940K/sec > and input is 133400K/sec with 4GB data. > > I must now leave this thing for a few days, but I guess I will try to find > out what is wrong (however, I'm not a competent kernel hacker). > > - Jani Can you email your raid configuration please, I don't have as many disks, but I can try things out with a similar if smaller config. Steve From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:38:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEcIF12270 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:38:18 -0700 Received: from orion.mc.duke.edu (IDENT:root@orion.mc.duke.edu [152.3.50.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEcFV12250 for ; Wed, 18 Jul 2001 07:38:15 -0700 Received: from orion.mc.duke.edu (leo [152.3.50.13]) by orion.mc.duke.edu (8.11.2/8.11.2) with ESMTP id f6IFeea23074; Wed, 18 Jul 2001 11:40:40 -0400 Message-ID: <3B55CAAA.F13DE913@orion.mc.duke.edu> Date: Wed, 18 Jul 2001 10:43:07 -0700 From: Lucy Upchurch Organization: DUMC - CIVM X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS on Linux Content-Type: multipart/alternative; boundary="------------0A667DF743B79280C4ACC962" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --------------0A667DF743B79280C4ACC962 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I am trying to install XFS filesystem on a linux box which was running Linux 7.4.2. I downloaded the ISO image from http://oss.sgi.com/projects/xfs/1.0_installer.html and made a bootable CD. I selected a custom system. Before installation, my system loooked like this: /dev/hda6 1517920 814808 626004 57% / /dev/hda1 23302 8667 13432 40% /boot /dev/hda10 65275692 10576328 51383552 18% /home /dev/sda1 73885280 20 70132076 1% /home2 /dev/hda7 1011928 624652 335872 66% /tmp /dev/hda5 4032092 2221300 1605968 59% /usr /dev/hda8 1011928 123832 836692 13% /var I tried numerous times to create an XFS filesystem on /home to no avail. I then tried installing XFS on all partitions. The main error I rec'd on various partitions is: Error mounting device hda1 as /boot: No such device This most likely means this partition has not been formatted. Press OK to reboot your system. Sometimes this error would be on /boot or on /. We were very excited about using an XFS filesystem on our linux box but we are having a very difficult time creating it. Any suggestions or directions would be greatly appreciated. Thank you for your prompt response. -- Lucy Upchurch - Associate in Research Department of Radiology - Center for In Vivo Microscopy Box 3302, Room 139 Bryan Research Building, Research Drive Durham, NC 27710 Telephone: 919-684-7781 For more information regarding our center, please see: http://wwwcivm.mc.duke.edu --------------0A667DF743B79280C4ACC962 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,

    I am trying to install XFS filesystem on a linux box which was running Linux 7.4.2.  I downloaded the ISO image from http://oss.sgi.com/projects/xfs/1.0_installer.html and made a bootable CD.  I selected a custom system.  Before installation, my system loooked like this:

    /dev/hda6        1517920         814808         626004    57%    /
    /dev/hda1            23302              8667          13432    40%    /boot
    /dev/hda10    65275692      10576328    51383552    18%    /home
    /dev/sda1      73885280                  20    70132076      1%    /home2
    /dev/hda7        1011928          624652        335872    66%    /tmp
    /dev/hda5        4032092        2221300      1605968    59%    /usr
    /dev/hda8        1011928          123832        836692    13%    /var

    I tried numerous times to create an XFS filesystem on /home to no avail.  I then tried installing XFS on all partitions.  The main error I rec'd on various partitions is:

    Error mounting device hda1 as /boot:  No such device
    This most likely means this partition has not been formatted.
    Press OK to reboot your system.

    Sometimes this error would be on /boot or on /.

    We were very excited about using an XFS filesystem on our linux box but we are having a very difficult time creating it.  Any suggestions or directions would be greatly appreciated.

    Thank you for your prompt response.
      

    -- 
Lucy Upchurch - Associate in Research
Department of Radiology - Center for In Vivo Microscopy
Box 3302, Room 139
Bryan Research Building, Research Drive
Durham, NC  27710
Telephone:  919-684-7781
For more information regarding our center, please see:
http://wwwcivm.mc.duke.edu
      --------------0A667DF743B79280C4ACC962-- From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:38:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEcVO12305 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:38:31 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEcSV12282 for ; Wed, 18 Jul 2001 07:38:28 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA450726 for ; Wed, 18 Jul 2001 16:38:17 +0200 (CEST) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2456402; Wed, 18 Jul 2001 09:37:08 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA14336; Wed, 18 Jul 2001 09:37:08 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id JAA35513; Wed, 18 Jul 2001 09:37:07 -0500 (CDT) Message-Id: <200107181437.JAA35513@fsgi158.americas.sgi.com> Subject: Re: Quota reporting for NFS mounts To: fermin@eup.udl.es (Fermin Molina) Date: Wed, 18 Jul 2001 09:37:06 -0500 (CDT) Cc: linux-xfs@oss.sgi.com, syrekron@iastate.edu In-Reply-To: <200107181345.PAA17895@eup.udl.es> from "Fermin Molina" at Jul 18, 2001 03:45:01 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi, > > > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > > built from the source rpm. > > > > I have exported my /export partition over NFS which file system is XFS. > > > > I can mount this from client type machines, but when I try (on the > > client) to list my quota, the command just hangs. I've run snoop on the > > connection, and it appears that my server (sherlock) doesn't respond to > > the client's (cousteau) requests. > > > > I also verified that rpc.rquotad is running on my server. > > > > Any idea how I can get remote quota reporting working? > > > Similar configuration. My NFS-client machine is a Sun (Solaris 2.7). > On my linux XFS-NFS server, rpc.rquotad segfaults when I run > quota -v on the client (Sun). > I'm able to use "quota -v " on a SUN client with an XFS-NFS server without any problems. I do find, though, that if I mount an NFS exported file system on IRIX or SUN with the quota option and the file system is not mounted on the server with the usrquota option then rpc.rquotad segfaults. This happens with both xfs and ext2 file systems. Could it be a similar problem? Tad From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:40:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEeAl12586 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:40:10 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEe8V12567 for ; Wed, 18 Jul 2001 07:40:08 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA00525 for ; Wed, 18 Jul 2001 07:39:58 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2447667; Wed, 18 Jul 2001 09:38:50 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA37086; Wed, 18 Jul 2001 09:38:50 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IEdpY04553; Wed, 18 Jul 2001 09:39:51 -0500 Message-Id: <200107181439.f6IEdpY04553@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Chris Mason cc: dcox@connex.com, linux-xfs@oss.sgi.com, reiserfs-list@namesys.com Subject: Re: [reiserfs-list] Re: benchmarks (again) In-Reply-To: Message from Chris Mason of "Wed, 18 Jul 2001 10:33:49 EDT." <224490000.995466829@tiny> Date: Wed, 18 Jul 2001 09:39:51 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > On Wednesday, July 18, 2001 07:51:22 AM -0400 Danny Cox > wrote: > > > All, > > > > One other point regarding benchmarks, it's relevancy depends upon the > > environment: when recovering from a "temporal power anomaly" [;-)] an > > XFS mount will usually take less than a second. Reiser can take > > several. > > > > Admittedly, I'm using Reiser as it exists on SuSE 7.1, and XFS as of > > this week's CVS, but an XFS mount was always quick (witnessed personally > > when I was helping to track down XFS/RAID5 incompatibilities...several > > times...every hour.... ;-). > > > > Yes, it's not the "normal mode", but when the system's down, and the > > users have their noses plastered on the glass staring at your back, that > > extra 4 seconds per filesystem can seem an eternity! > > > ;-) > > XFS does logical logging, which allow them to use a very small log, and > smaller logs take less time to process. > > reiserfs logs full blocks, and the journal code tries really hard to use > the entire 32MB log before it starts flushing blocks to their real > locations on disk. So, the reiserfs log replay time should be slightly > longer than it takes your disk to read and write 32MB (in synchronous > chunks from 12k to 4MB in size). And you can make xfs recovery slower by making a bigger log. The larger log means when you are running the filesystem there are less occasions when you run into the case where you need to flush metadata to get log space. The larger log though takes longer to process at recovery time. Steve From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:43:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEhBv12828 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:43:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEh9V12808 for ; Wed, 18 Jul 2001 07:43:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA01063 for ; Wed, 18 Jul 2001 07:43:00 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2461939; Wed, 18 Jul 2001 09:41:52 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA49480; Wed, 18 Jul 2001 09:41:52 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IEgqL04570; Wed, 18 Jul 2001 09:42:52 -0500 Message-Id: <200107181442.f6IEgqL04570@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Ext-Kamaljeet.Singh@nokia.com cc: linux-xfs@oss.sgi.com, Imad.Ossaily@nokia.com Subject: Re: Xfs prblems with clearcase mvfs In-Reply-To: Message from Ext-Kamaljeet.Singh@nokia.com of "Wed, 18 Jul 2001 17:29:41 +0300." <5EB7E309FC6E5C46A55F01B49E0CAE6D0553C5@esebe012.NOE.Nokia.com> Date: Wed, 18 Jul 2001 09:42:52 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > We are facing problems with xfs version 1.0 (with kernel 2.4.2-2 on Redhat > 7.1) with Clearcase version 4.1 for linux. when we try to load mvfs module, > it gives structure check errors for following structures: > Super-operations > inode-operations > File-operations > Super-block > inode > dentry > > Could you please look into it and suggest us some good solution. We can > provide more details if required. Since clearcase is a commercial product and we do not have access to it for linux you are going to have to provide a few more details. Clearcase on Irix on top of XFS was definitely a major pain to deal with. I would not be surprised if they do not have similar problems on Linux, but this sounds more like their binary module is not compatible with the kernel. Steve > > > Thanks in Advance, > Kamaljet Singh From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:47:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IElQN13118 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:47:26 -0700 Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IElOV13099 for ; Wed, 18 Jul 2001 07:47:24 -0700 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6IEnbG10182 for ; Wed, 18 Jul 2001 17:49:37 +0300 (EET DST) Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Wed, 18 Jul 2001 17:46:22 +0300 Received: by esebh25nok with Internet Mail Service (5.5.2652.78) id <3MSVBN61>; Wed, 18 Jul 2001 17:46:22 +0300 Message-ID: <62D73DD5B95CE14084EC17103E347B70060051@esebe014.NOE.Nokia.com> From: Imad.Ossaily@nokia.com To: knuffie@xs4all.nl, Ext-Kamaljeet.Singh@nokia.com, linux-xfs@oss.sgi.com Subject: RE: Xfs prblems with clearcase mvfs Date: Wed, 18 Jul 2001 17:46:14 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk we can't upgrade to XFS-1.0.1 because it's supported for kernel 2.4.5 and ClearCase 4.1 on linux is supported only for kernel 2.4.2, so we have to use this version of the kernel. regards, Imad. > -----Original Message----- > From: ext Seth Mos [mailto:knuffie@xs4all.nl] > Sent: Wednesday, July 18, 2001 5:35 PM > To: Singh Kamaljeet (EXT-TataCS/Helsinki); linux-xfs@oss.sgi.com > Cc: Ossaily Imad (NET/Helsinki) > Subject: Re: Xfs prblems with clearcase mvfs > > > At 17:29 18-7-2001 +0300, Ext-Kamaljeet.Singh@nokia.com wrote: > >Hi, > >We are facing problems with xfs version 1.0 (with kernel > 2.4.2-2 on Redhat > >7.1) with Clearcase version 4.1 for linux. when we try to > load mvfs module, > >it gives structure check errors for following structures: > >Super-operations > >inode-operations > >File-operations > >Super-block > >inode > >dentry > > > >Could you please look into it and suggest us some good > solution. We can > >provide more details if required. > > Can you upgrade to the 1.0.1 release? That one has many > fixes, tlhough I am > not quite sure if it fixes this. > > Bye > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. > From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:48:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEmFo13199 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:48:15 -0700 Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEmDV13173 for ; Wed, 18 Jul 2001 07:48:13 -0700 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6IEpBG10849 for ; Wed, 18 Jul 2001 17:51:11 +0300 (EET DST) Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Wed, 18 Jul 2001 17:48:01 +0300 Received: by esebh25nok with Internet Mail Service (5.5.2652.78) id <3MSVBN7C>; Wed, 18 Jul 2001 17:48:01 +0300 Message-ID: <62D73DD5B95CE14084EC17103E347B70060052@esebe014.NOE.Nokia.com> From: Imad.Ossaily@nokia.com To: lord@sgi.com, Ext-Kamaljeet.Singh@nokia.com Cc: linux-xfs@oss.sgi.com Subject: RE: Xfs prblems with clearcase mvfs Date: Wed, 18 Jul 2001 17:47:54 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk What kind of details do you need? We are not able to load the mvfs.o module when the kernel has XFS support. regards, Imad. > -----Original Message----- > From: ext Steve Lord [mailto:lord@sgi.com] > Sent: Wednesday, July 18, 2001 5:43 PM > To: Singh Kamaljeet (EXT-TataCS/Helsinki) > Cc: linux-xfs@oss.sgi.com; Ossaily Imad (NET/Helsinki) > Subject: Re: Xfs prblems with clearcase mvfs > > > > Hi, > > We are facing problems with xfs version 1.0 (with kernel > 2.4.2-2 on Redhat > > 7.1) with Clearcase version 4.1 for linux. when we try to > load mvfs module, > > it gives structure check errors for following structures: > > Super-operations > > inode-operations > > File-operations > > Super-block > > inode > > dentry > > > > Could you please look into it and suggest us some good > solution. We can > > provide more details if required. > > Since clearcase is a commercial product and we do not have > access to it > for linux you are going to have to provide a few more > details. Clearcase > on Irix on top of XFS was definitely a major pain to deal > with. I would > not be surprised if they do not have similar problems on Linux, but > this sounds more like their binary module is not compatible with > the kernel. > > Steve > > > > > > > Thanks in Advance, > > Kamaljet Singh > > From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:53:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IErIc13597 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:53:18 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IErGV13576 for ; Wed, 18 Jul 2001 07:53:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA12653 for ; Wed, 18 Jul 2001 07:53:06 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2452768; Wed, 18 Jul 2001 09:51:59 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA16608; Wed, 18 Jul 2001 09:51:59 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IEr0X04585; Wed, 18 Jul 2001 09:53:00 -0500 Message-Id: <200107181453.f6IEr0X04585@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Imad.Ossaily@nokia.com cc: knuffie@xs4all.nl, Ext-Kamaljeet.Singh@nokia.com, linux-xfs@oss.sgi.com Subject: Re: Xfs prblems with clearcase mvfs In-Reply-To: Message from Imad.Ossaily@nokia.com of "Wed, 18 Jul 2001 17:46:14 +0300." <62D73DD5B95CE14084EC17103E347B70060051@esebe014.NOE.Nokia.com> Date: Wed, 18 Jul 2001 09:53:00 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > we can't upgrade to XFS-1.0.1 because it's supported for kernel 2.4.5 and > ClearCase 4.1 on linux is supported only for kernel 2.4.2, so we have to use > this version of the kernel. And this is exactly your problem, if clearcase is built against the original kernel shipped by redhat then it will almost certainly not work with the xfs kernel. Running a binary kernel module against a different kernel than it was built for is almost certainly not going to work in this case the only people who can help you with this is clearcase. What I would like to see to confirm this is the exact error messages you are getting. Thanks Steve > > regards, > Imad. > > > -----Original Message----- > > From: ext Seth Mos [mailto:knuffie@xs4all.nl] > > Sent: Wednesday, July 18, 2001 5:35 PM > > To: Singh Kamaljeet (EXT-TataCS/Helsinki); linux-xfs@oss.sgi.com > > Cc: Ossaily Imad (NET/Helsinki) > > Subject: Re: Xfs prblems with clearcase mvfs > > > > > > At 17:29 18-7-2001 +0300, Ext-Kamaljeet.Singh@nokia.com wrote: > > >Hi, > > >We are facing problems with xfs version 1.0 (with kernel > > 2.4.2-2 on Redhat > > >7.1) with Clearcase version 4.1 for linux. when we try to > > load mvfs module, > > >it gives structure check errors for following structures: > > >Super-operations > > >inode-operations > > >File-operations > > >Super-block > > >inode > > >dentry > > > > > >Could you please look into it and suggest us some good > > solution. We can > > >provide more details if required. > > > > Can you upgrade to the 1.0.1 release? That one has many > > fixes, tlhough I am > > not quite sure if it fixes this. > > > > Bye > > > > -- > > Seth > > Every program has two purposes one for which > > it was written and another for which it wasn't > > I use the last kind. > > From owner-linux-xfs@oss.sgi.com Wed Jul 18 07:57:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IEv6h13893 for linux-xfs-outgoing; Wed, 18 Jul 2001 07:57:06 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IEv4V13873 for ; Wed, 18 Jul 2001 07:57:04 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.2/8.11.2) with ESMTP id f6IEuj402652; Wed, 18 Jul 2001 10:56:45 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Wed, 18 Jul 2001 10:56:44 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: Lucy Upchurch cc: Linux xfs mailing list Subject: Re: XFS on Linux In-Reply-To: <3B55CAAA.F13DE913@orion.mc.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001 at 10:43am, Lucy Upchurch wrote > Hi, Hi, from around the corner! > I am trying to install XFS filesystem on a linux box which was running > Linux 7.4.2. I downloaded the ISO image from Err, Redhat 7.1, kernel 2.4.2-2? > http://oss.sgi.com/projects/xfs/1.0_installer.html and made a bootable 1.0.1 has been released, and it's what you want. The installation iso is available here: ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer > CD. I selected a custom system. Before installation, my system loooked > like this: > > I tried numerous times to create an XFS filesystem on /home to no > avail. I then tried installing XFS on all partitions. The main error I > rec'd on various partitions is: The question is, do you want XFS on all partitions, or just certain ones? If you just want XFS on, e.g., /home, then I would 1) Install RedHat 7.1 2) Install the XFS 1.0.1 RPMs from and . 3) Unmount /home, mkfs.xfs it, and remount it (after changing the type in the fstab, of course). If you want XFS everywhere, then you'll need the installation ISO above in addition to the standard RedHat 7.1 CDs. Boot the SGI CD, and do the standard RedHat install two-step, selecting XFS for all your partitions at the proper point. Then enjoy! -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:07:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IF72P14626 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:07:02 -0700 Received: from mgw-x4.nokia.com (mgw-x4.nokia.com [131.228.20.27]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IF6wV14604 for ; Wed, 18 Jul 2001 08:06:59 -0700 Received: from esvir04nok.ntc.nokia.com (esvir04nokt.ntc.nokia.com [172.21.143.36]) by mgw-x4.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6IF9uG15961 for ; Wed, 18 Jul 2001 18:09:56 +0300 (EET DST) Received: from esebh25nok.ntc.nokia.com (unverified) by esvir04nok.ntc.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Wed, 18 Jul 2001 18:06:53 +0300 Received: by esebh25nok with Internet Mail Service (5.5.2652.78) id <3MSVB3GN>; Wed, 18 Jul 2001 18:06:30 +0300 Message-ID: <62D73DD5B95CE14084EC17103E347B700604A8@esebe014.NOE.Nokia.com> From: Imad.Ossaily@nokia.com To: lord@sgi.com Cc: knuffie@xs4all.nl, Ext-Kamaljeet.Singh@nokia.com, linux-xfs@oss.sgi.com Subject: RE: Xfs prblems with clearcase mvfs Date: Wed, 18 Jul 2001 18:06:20 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk we have recomiled the mvfs module against the running kernel version with XFS support, so this is not the source of the problem. The error messages that I'm getting while trying to load the module are: [root@t1-dhcp2-027231 mvfs]# insmod mvfs Using /lib/modules/fs/mvfs.o Structure_check error for struct super_operations. MVFS expected 56, got 64 Structure_check error for struct inode_operations. MVFS expected 64, got 76 Structure_check error for struct file_operations. MVFS expected 68, got 64 Structure_check error for struct super_block. MVFS expected 500, got 464 Structure_check error for struct inode. MVFS expected 472, got 456 Structure_check error for struct dentry. MVFS expected 116, got 112 ERROR: MVFS detected 6 structure size mismatches /lib/modules/fs/mvfs.o: init_module: Invalid argument Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters regards, Imad. > -----Original Message----- > From: ext Steve Lord [mailto:lord@sgi.com] > Sent: Wednesday, July 18, 2001 5:53 PM > To: Ossaily Imad (NET/Helsinki) > Cc: knuffie@xs4all.nl; Singh Kamaljeet (EXT-TataCS/Helsinki); > linux-xfs@oss.sgi.com > Subject: Re: Xfs prblems with clearcase mvfs > > > > we can't upgrade to XFS-1.0.1 because it's supported for > kernel 2.4.5 and > > ClearCase 4.1 on linux is supported only for kernel 2.4.2, > so we have to use > > this version of the kernel. > > And this is exactly your problem, if clearcase is built against the > original kernel shipped by redhat then it will almost certainly not > work with the xfs kernel. Running a binary kernel module against a > different kernel than it was built for is almost certainly not going > to work in this case the only people who can help you with > this is clearcase. > > What I would like to see to confirm this is the exact error > messages you > are getting. > > Thanks > > Steve > > > > > > regards, > > Imad. > > > > > -----Original Message----- > > > From: ext Seth Mos [mailto:knuffie@xs4all.nl] > > > Sent: Wednesday, July 18, 2001 5:35 PM > > > To: Singh Kamaljeet (EXT-TataCS/Helsinki); linux-xfs@oss.sgi.com > > > Cc: Ossaily Imad (NET/Helsinki) > > > Subject: Re: Xfs prblems with clearcase mvfs > > > > > > > > > At 17:29 18-7-2001 +0300, Ext-Kamaljeet.Singh@nokia.com wrote: > > > >Hi, > > > >We are facing problems with xfs version 1.0 (with kernel > > > 2.4.2-2 on Redhat > > > >7.1) with Clearcase version 4.1 for linux. when we try to > > > load mvfs module, > > > >it gives structure check errors for following structures: > > > >Super-operations > > > >inode-operations > > > >File-operations > > > >Super-block > > > >inode > > > >dentry > > > > > > > >Could you please look into it and suggest us some good > > > solution. We can > > > >provide more details if required. > > > > > > Can you upgrade to the 1.0.1 release? That one has many > > > fixes, tlhough I am > > > not quite sure if it fixes this. > > > > > > Bye > > > > > > -- > > > Seth > > > Every program has two purposes one for which > > > it was written and another for which it wasn't > > > I use the last kind. > > > > > From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:11:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFBt415018 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:11:55 -0700 Received: from marraco.udl.es (gardeny.udl.es [193.144.12.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFBrV14998 for ; Wed, 18 Jul 2001 08:11:53 -0700 Received: from eup.udl.es (fermat.udl.net [10.50.54.28]) by marraco.udl.es (8.9.3/8.8.5) with ESMTP id QAA18476; Wed, 18 Jul 2001 16:14:44 +0200 Received: by eup.udl.es (8.8.8+Sun/SMI-SVR4) id RAA18407; Wed, 18 Jul 2001 17:11:42 +0200 (MET DST) Date: Wed, 18 Jul 2001 17:11:42 +0200 (MET DST) From: fermin@eup.udl.es (Fermin Molina) Message-Id: <200107181511.RAA18407@eup.udl.es> To: tbd@sgi.com Subject: Re: Quota reporting for NFS mounts Cc: linux-xfs@oss.sgi.com, syrekron@iastate.edu X-Sun-Charset: US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > > > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > > > built from the source rpm. > > > > > > I have exported my /export partition over NFS which file system is XFS. > > > > > > I can mount this from client type machines, but when I try (on the > > > client) to list my quota, the command just hangs. I've run snoop on the > > > connection, and it appears that my server (sherlock) doesn't respond to > > > the client's (cousteau) requests. > > > > > > I also verified that rpc.rquotad is running on my server. > > > > > > Any idea how I can get remote quota reporting working? > > > > > > Similar configuration. My NFS-client machine is a Sun (Solaris 2.7). > > On my linux XFS-NFS server, rpc.rquotad segfaults when I run > > quota -v on the client (Sun). > > > I'm able to use "quota -v " on a SUN client with an XFS-NFS server > without any problems. I do find, though, that if I mount an NFS exported > file system on IRIX or SUN with the quota option and the file system is > not mounted on the server with the usrquota option then rpc.rquotad segfaults. > This happens with both xfs and ext2 file systems. Could it be a similar > problem? I'm not using the quota option when I mount on SUN. But I use usrquota on XFS-linux server. What quota options use you on client/server? I need to use "quota" option when I mount on SUN? (using snoop I see requests to the server without using it...) /Fermin From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:16:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFGlF15479 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:16:47 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFGgV15460 for ; Wed, 18 Jul 2001 08:16:43 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id RAA454312 for ; Wed, 18 Jul 2001 17:16:31 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2462405; Wed, 18 Jul 2001 10:15:22 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA88403; Wed, 18 Jul 2001 10:15:22 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IFGNa04739; Wed, 18 Jul 2001 10:16:23 -0500 Message-Id: <200107181516.f6IFGNa04739@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Imad.Ossaily@nokia.com cc: lord@sgi.com, knuffie@xs4all.nl, Ext-Kamaljeet.Singh@nokia.com, linux-xfs@oss.sgi.com Subject: Re: Xfs prblems with clearcase mvfs In-Reply-To: Message from Imad.Ossaily@nokia.com of "Wed, 18 Jul 2001 18:06:20 +0300." <62D73DD5B95CE14084EC17103E347B700604A8@esebe014.NOE.Nokia.com> Date: Wed, 18 Jul 2001 10:16:23 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > we have recomiled the mvfs module against the running kernel version with > XFS support, so this is not the source of the problem. > The error messages that I'm getting while trying to load the module are: > > [root@t1-dhcp2-027231 mvfs]# insmod mvfs > Using /lib/modules/fs/mvfs.o > Structure_check error for struct super_operations. MVFS expected 56, got 64 > Structure_check error for struct inode_operations. MVFS expected 64, got 76 > Structure_check error for struct file_operations. MVFS expected 68, got 64 > Structure_check error for struct super_block. MVFS expected 500, got 464 > Structure_check error for struct inode. MVFS expected 472, got 456 > Structure_check error for struct dentry. MVFS expected 116, got 112 > ERROR: MVFS detected 6 structure size mismatches > /lib/modules/fs/mvfs.o: init_module: Invalid argument > Hint: insmod errors can be caused by incorrect module parameters, including > invalid IO or IRQ parameters These error messages are coming out of the mvfs module itself, not the insmod utility. If this is part of the code which gets recompiled by mvfs then it suggests that the wrong set of header files were used, especially since we do not make any changes to the size of the inode, super_block or dentry. Can you double check that your mvfs build was looking at header files which match the kernel. Steve > > regards, > Imad. > > > -----Original Message----- > > From: ext Steve Lord [mailto:lord@sgi.com] > > Sent: Wednesday, July 18, 2001 5:53 PM > > To: Ossaily Imad (NET/Helsinki) > > Cc: knuffie@xs4all.nl; Singh Kamaljeet (EXT-TataCS/Helsinki); > > linux-xfs@oss.sgi.com > > Subject: Re: Xfs prblems with clearcase mvfs > > > > > > > we can't upgrade to XFS-1.0.1 because it's supported for > > kernel 2.4.5 and > > > ClearCase 4.1 on linux is supported only for kernel 2.4.2, > > so we have to use > > > this version of the kernel. > > > > And this is exactly your problem, if clearcase is built against the > > original kernel shipped by redhat then it will almost certainly not > > work with the xfs kernel. Running a binary kernel module against a > > different kernel than it was built for is almost certainly not going > > to work in this case the only people who can help you with > > this is clearcase. > > > > What I would like to see to confirm this is the exact error > > messages you > > are getting. > > > > Thanks > > > > Steve > > > > > > > > > > regards, > > > Imad. > > > > > > > -----Original Message----- > > > > From: ext Seth Mos [mailto:knuffie@xs4all.nl] > > > > Sent: Wednesday, July 18, 2001 5:35 PM > > > > To: Singh Kamaljeet (EXT-TataCS/Helsinki); linux-xfs@oss.sgi.com > > > > Cc: Ossaily Imad (NET/Helsinki) > > > > Subject: Re: Xfs prblems with clearcase mvfs > > > > > > > > > > > > At 17:29 18-7-2001 +0300, Ext-Kamaljeet.Singh@nokia.com wrote: > > > > >Hi, > > > > >We are facing problems with xfs version 1.0 (with kernel > > > > 2.4.2-2 on Redhat > > > > >7.1) with Clearcase version 4.1 for linux. when we try to > > > > load mvfs module, > > > > >it gives structure check errors for following structures: > > > > >Super-operations > > > > >inode-operations > > > > >File-operations > > > > >Super-block > > > > >inode > > > > >dentry > > > > > > > > > >Could you please look into it and suggest us some good > > > > solution. We can > > > > >provide more details if required. > > > > > > > > Can you upgrade to the 1.0.1 release? That one has many > > > > fixes, tlhough I am > > > > not quite sure if it fixes this. > > > > > > > > Bye > > > > > > > > -- > > > > Seth > > > > Every program has two purposes one for which > > > > it was written and another for which it wasn't > > > > I use the last kind. > > > > > > > > From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:17:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFHBZ15538 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:17:11 -0700 Received: from exchange.visa-austria.com (visa091.cybertron.at [212.236.12.91] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFH9V15519 for ; Wed, 18 Jul 2001 08:17:09 -0700 Received: by exchange.visa-austria.com with Internet Mail Service (5.5.2650.21) id <3NSC494R>; Wed, 18 Jul 2001 17:17:02 +0200 Message-ID: <4FF9029AF0C8D311B99D0050DA1CB9F4FB78F0@exchange.visa-austria.com> From: =?iso-8859-1?Q?KR=DCCKEL_OLIVER?= To: "'linux-xfs@oss.sgi.com'" Subject: AW: xfs kernel problem Date: Wed, 18 Jul 2001 17:16:56 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6IFHAV15520 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 17 Jul 2001 18:57:38 +0200, Krückel Oliver wrote: >> Linux SuSE-7.1 with servarel patches from the officel SuSE web-server >> gcc: version 2.95.2 19991024 (release) >Can you try compiling with a 2.91.66 gcc version? This is the first >thing I'd try, newer compilers still have not been producing >consistently good code. ok I get the egcs-1.1.2 (gcc 2.91.66) but I can't compile it. I test it also with the gcc 3.0, but with the sam results with the gcc 2.91.66 >> if i reboot the server with the xfs kernel and the server coms up there are >> sum files and executables witch i can't access ore execute, >> >> sum examples: the programms find, make, ... or file hosts, ... >> >> if i reboot the server again, there are much more files that can't access or >> execute, there are alwais other executebles and files by every test, >Can you give any more information about "can't access" - do they not >show up in the directory listing, do they seem to contain wrong data... >? I get at the startup process sum lines like the follow Initializing SMTP port. (sendmail)451 4.0.0 /etc/sendmail.cf: line 0: cannot open: Permission denied startproc: exit status of /usr/sbin/sendmail: 72 failed the file sendmail.cf hase the size 0 byte at sume other cases i can't access or list a file (i'm root) and I get the massage permisson denied. >-Eric I test my config also on an other hp lp2000r server and I have the same problems. From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:31:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFVTm16670 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:31:29 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFVRV16645 for ; Wed, 18 Jul 2001 08:31:27 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA19111 for ; Wed, 18 Jul 2001 08:31:17 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2459001; Wed, 18 Jul 2001 10:30:11 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA05086; Wed, 18 Jul 2001 10:30:09 -0500 (CDT) Subject: RE: Pb with XFS From: Eric Sandeen To: GLENAT =?ISO-8859-1?Q?Gr=C3=A9gory?= Cc: linux-xfs list In-Reply-To: <4.3.2.7.2.20010718144631.034ba518@pop.xs4all.nl> References: <4.3.2.7.2.20010718144631.034ba518@pop.xs4all.nl> Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 10:30:05 -0500 Message-Id: <995470205.9129.64.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6IFVRV16646 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 14:48:01 +0200, GLENAT Grégory wrote: > More Detail : > Here what appairs in the boot (extract from dmsg ) > ========== > checking TSC synchronization across CPUs: passed. > Setting commenced=1, go go go > mtrr: your CPUs had inconsistent fixed MTRR settings > mtrr: probably your BIOS does not setup all CPUs > PCI: PCI BIOS revision 2.10 entry at 0xfd2fc, last bus=4 > PCI: Using configuration type 1 > ========== I don't think any of this is particularly unusual. > What more detail do you need ? You said you tried 2 kernels on 2 different machines - do you see exactly the same behavior in all cases? Does this lockup seem to depend on whether nfs is enabled? Does it depend on samba? Does it only happen after a lot of nfs traffic? Etc... You can turn on kdb with $ echo 1 > /proc/sys/kernel/kdb then hit the Pause/Break key to get into kdb when things "seem dead" - "ps" will get you a list of what's running and what state things are in, "btp " will do a backtrace on any process... kdb is easiest to use if you're at a text console, don't start it from X. You can also do it via a serial console. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:34:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFYmu16980 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:34:48 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFYkV16961 for ; Wed, 18 Jul 2001 08:34:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA06586 for ; Wed, 18 Jul 2001 08:34:37 -0700 (PDT) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2460824; Wed, 18 Jul 2001 10:32:57 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA39171; Wed, 18 Jul 2001 10:32:57 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id KAA30810; Wed, 18 Jul 2001 10:32:56 -0500 (CDT) Message-Id: <200107181532.KAA30810@fsgi158.americas.sgi.com> Subject: Re: Quota reporting for NFS mounts To: fermin@eup.udl.es (Fermin Molina) Date: Wed, 18 Jul 2001 10:32:56 -0500 (CDT) Cc: tbd@sgi.com, linux-xfs@oss.sgi.com, syrekron@iastate.edu In-Reply-To: <200107181511.RAA18407@eup.udl.es> from "Fermin Molina" at Jul 18, 2001 05:11:42 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > > > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > > > > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > > > > built from the source rpm. > > > > > > > > I have exported my /export partition over NFS which file system is XFS. > > > > > > > > I can mount this from client type machines, but when I try (on the > > > > client) to list my quota, the command just hangs. I've run snoop on the > > > > connection, and it appears that my server (sherlock) doesn't respond to > > > > the client's (cousteau) requests. > > > > > > > > I also verified that rpc.rquotad is running on my server. > > > > > > > > Any idea how I can get remote quota reporting working? > > > > > > > > > Similar configuration. My NFS-client machine is a Sun (Solaris 2.7). > > > On my linux XFS-NFS server, rpc.rquotad segfaults when I run > > > quota -v on the client (Sun). > > > > > I'm able to use "quota -v " on a SUN client with an XFS-NFS server > > without any problems. I do find, though, that if I mount an NFS exported > > file system on IRIX or SUN with the quota option and the file system is > > not mounted on the server with the usrquota option then rpc.rquotad segfaults. > > This happens with both xfs and ext2 file systems. Could it be a similar > > problem? > > > I'm not using the quota option when I mount on SUN. > But I use usrquota on XFS-linux server. > I just tried that and that seems to kill rpc.rquotad for me too. > What quota options use you on client/server? > I need to use "quota" option when I mount on SUN? > (using snoop I see requests to the server without > using it...) > I use usrquota on server and quota option on SUN client and everything works fine for me. Tad From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:38:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFcQ417277 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:38:26 -0700 Received: from marilyn1.kirchgruppe.de (marilyn.kirchgruppe.de [193.101.184.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFcOV17257 for ; Wed, 18 Jul 2001 08:38:24 -0700 Received: by marilyn1.kirchgruppe.de (8.9.3/8.9.3) id RAA03153 for linux-xfs@oss.sgi.com; Wed, 18 Jul 2001 17:38:23 +0200 (CEST) Received: (from localhost) by marilyn1.kirchgruppe.de (MSCAN) id 3/marilyn1.kirchgruppe.de/smtp-gw/mscan; Wed Jul 18 17:38:22 2001 Message-ID: <3B55AD2F.C5F0154B@betaresearch.de> Date: Wed, 18 Jul 2001 17:37:19 +0200 From: Wolfgang Henselmann-Weiss X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi. I'm new in this mailing list :-) I have the following problem: I cannot mount an XFS partition after creation with mkfs.xfs on my ide hdd, running on a promise ultra100tx2 controller. But XFS works fine on hdc (ls120 atapi floppy) and scsi hdd (sda2) I'm using SUSE7.1 with 2.4.6 kernel with following patches patch-2.4.6-xfs-2001-07-05.bz2 # for xfs :-) ide.2.4.6.all.07042001.patch.bz2 #from linux-ide.org (enable bm dma for the promise 100tx2 controller) root ,usr partitions are on same ide disk (/dev/hde1, /dev/hde6 of type reiserfs) commands mkfs.xfs -f /dev/hde7 # no error message ... mount -t xfs /dev/hde7 /mnt #fails with > mount: wrong fs type, bad option , bad superblock on /dev/hde7, > or too many mounted filesystems It seems that /dev/hde7 partition is not altered in any way, so e.g. it is still possible to mount that partition with the previous formatted fs type, e.g ext2 or reiserfs. (all other common fstypes are working fine on that partition) any comments or suggestions to check? regards Wolfgang Henselmann From owner-linux-xfs@oss.sgi.com Wed Jul 18 08:41:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IFfvs17582 for linux-xfs-outgoing; Wed, 18 Jul 2001 08:41:57 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IFftV17560 for ; Wed, 18 Jul 2001 08:41:55 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA21224 for ; Wed, 18 Jul 2001 08:41:45 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2463232; Wed, 18 Jul 2001 10:40:39 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA82842; Wed, 18 Jul 2001 10:40:38 -0500 (CDT) Subject: Re: XFS on Linux From: Eric Sandeen To: Lucy Upchurch Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B55CAAA.F13DE913@orion.mc.duke.edu> References: <3B55CAAA.F13DE913@orion.mc.duke.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 10:40:33 -0500 Message-Id: <995470834.8982.91.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 10:43:07 -0700, Lucy Upchurch wrote: > Hi, > > I am trying to install XFS filesystem on a linux box which was running > Linux 7.4.2. I downloaded the ISO image from > http://oss.sgi.com/projects/xfs/1.0_installer.html and made a bootable > CD. I selected a custom system. Before installation, my system loooked > like this: > > /dev/hda6 1517920 814808 626004 57% / > /dev/hda1 23302 8667 13432 40% > /boot > /dev/hda10 65275692 10576328 51383552 18% /home > /dev/sda1 73885280 20 70132076 1% > /home2 > /dev/hda7 1011928 624652 335872 66% /tmp > /dev/hda5 4032092 2221300 1605968 59% /usr > /dev/hda8 1011928 123832 836692 13% /var > > I tried numerous times to create an XFS filesystem on /home to no > avail. I then tried installing XFS on all partitions. The main error I > rec'd on various partitions is: As Joshua said, it would be worth getting the 1.0.1 release for starters, but I don't think that's the root of your problem... When you say that you tried creating an XFS filesystem on /home and got the following message: > Error mounting device hda1 as /boot: No such device > This most likely means this partition has not been formatted. > Press OK to reboot your system. I'm assuming that you _did_ check the "format this partition" checkbox? Just double checking, since you seem to be on a previously set up system - you cannot "convert" an ext2 partition to xfs, you must reformat it. The 1.0.1 installer is a bit smarter about this, if you don't choose to format a partition, you cannot select the filesystem you want, since one follows from the other. :) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 18 09:15:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IGF3W19158 for linux-xfs-outgoing; Wed, 18 Jul 2001 09:15:03 -0700 Received: from kaplan.com (intgate.kaplan.com [204.177.145.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IGF1V19137 for ; Wed, 18 Jul 2001 09:15:01 -0700 Received: from cosmo4 (206.67.75.7) by kaplan.com (FirstClass Mail Server v5.50) with SMTP (Sender: fperin@kaplan.com) transient id 3148; Wed, 18 Jul 2001 12:13:45 -0400 Reply-To: From: "G. Francisco Perin" To: Subject: installer is not working Date: Wed, 18 Jul 2001 12:17:52 -0400 Message-ID: <001301c10fa5$32ba3890$9865fea9@COSMO4> 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 CWS, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk We are consistently getting the same error when using the RH7.1-SGI installer. When we get to the package installation portion of the process, it asks us to insert RH7.1 cd1 and we're getting "cd1 is not cd1" error. We are using an official RH7.1 release. Has anyone seen this before??? -- G. F. P. From owner-linux-xfs@oss.sgi.com Wed Jul 18 09:22:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IGM3619375 for linux-xfs-outgoing; Wed, 18 Jul 2001 09:22:03 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IGM1V19356 for ; Wed, 18 Jul 2001 09:22:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA460512 for ; Wed, 18 Jul 2001 18:21:51 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2460906; Wed, 18 Jul 2001 11:20:37 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA39680; Wed, 18 Jul 2001 11:20:36 -0500 (CDT) Subject: Re: installer is not working From: Eric Sandeen To: fperin@kaplan.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <001301c10fa5$32ba3890$9865fea9@COSMO4> References: <001301c10fa5$32ba3890$9865fea9@COSMO4> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 11:20:31 -0500 Message-Id: <995473231.8987.197.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 12:17:52 -0400, G. Francisco Perin wrote: > We are consistently getting the same error when using the RH7.1-SGI > installer. When we get to the package installation portion of the process, > it asks us to insert RH7.1 cd1 and we're getting "cd1 is not cd1" error. We > are using an official RH7.1 release. Has anyone seen this before??? The installer looks for a file called ".discX-i386" in the top dir of each CD to verify that it is the correct CD - this file (in your case, .disc1-i386) should contain "986787650.210260" - if your CD does not have this file, or the file does not contain the above data, then the installer will not recognize it. If for some reason you have a bona-fide Red hat 7.1 CD with a different ID in this file, I can suggest some ways to get around this. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 18 09:27:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IGRCH19568 for linux-xfs-outgoing; Wed, 18 Jul 2001 09:27:12 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IGRBV19549 for ; Wed, 18 Jul 2001 09:27:11 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA04479 for ; Wed, 18 Jul 2001 09:27:01 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2459309 for ; Wed, 18 Jul 2001 11:25:54 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA37799 for ; Wed, 18 Jul 2001 11:25:53 -0500 (CDT) Subject: Re: XFS problems From: Eric Sandeen Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B55AD2F.C5F0154B@betaresearch.de> References: <3B55AD2F.C5F0154B@betaresearch.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 11:25:48 -0500 Message-Id: <995473548.8982.209.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 17:37:19 +0200, Wolfgang Henselmann-Weiss wrote: > mkfs.xfs -f /dev/hde7 > # no error message ... Can you send the mkfs.xfs output that did appear? > mount -t xfs /dev/hde7 /mnt > #fails with > > mount: wrong fs type, bad option , bad superblock on /dev/hde7, > > or too many mounted filesystems Hm, wish this error was less Windows-like*. :) -Eric *(Random list of things that may or may not have gone wrong) -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, In From owner-linux-xfs@oss.sgi.com Wed Jul 18 10:41:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IHfrC21549 for linux-xfs-outgoing; Wed, 18 Jul 2001 10:41:53 -0700 Received: from anchor-post-32.mail.demon.net (anchor-post-32.mail.demon.net [194.217.242.90]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IHfpV21529 for ; Wed, 18 Jul 2001 10:41:51 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by anchor-post-32.mail.demon.net with esmtp (Exim 2.12 #1) id 15MvKX-0007kl-0W for linux-xfs@oss.sgi.com; Wed, 18 Jul 2001 18:41:50 +0100 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 50F4327EF for ; Wed, 18 Jul 2001 18:41:25 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id BAAB5125E6; Wed, 18 Jul 2001 18:41:24 +0100 (BST) Date: Wed, 18 Jul 2001 18:41:24 +0100 (BST) From: Keith Matthews Subject: [OT] -error messages was Re[2]: XFS problems To: linux-xfs@oss.sgi.com In-Reply-To: <995473548.8982.209.camel@stout.americas.sgi.com> References: <3B55AD2F.C5F0154B@betaresearch.de>, <995473548.8982.209.camel@stout.americas.sgi.com> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010718174124.BAAB5125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f6IHfpV21530 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 11:25:48 -0500 Eric Sandeen > wrote: > > > mount: wrong fs type, bad option , bad superblock on /dev/hde7, > > > or too many mounted filesystems > Hm, wish this error was less Windows-like*. :) > *(Random list of things that may or may not have gone wrong) Many years ago now I came across an Algol 60 compiler that produced the message 'The compiler has been confused by a previous error' I wish all comiler/OS developers could be so honest. -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Wed Jul 18 10:57:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IHvQi21966 for linux-xfs-outgoing; Wed, 18 Jul 2001 10:57:26 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IHvNV21947 for ; Wed, 18 Jul 2001 10:57:23 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id TAA24994; Wed, 18 Jul 2001 19:57:24 +0200 Date: Wed, 18 Jul 2001 19:57:23 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: kernel deadlock; xfs Message-ID: <20010718195723.A24237@vestdata.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi We're experiencing a deadlock on a NFS-server using a XFS filesystem. The kernel was originally running SGI XFS 1.0, but we've now tried 1.0.1 and the CVS-version (as of yesterday) - same problem. The deadlock appear to be happening when accessing big files over NFS, but we're not sure as we have not found a way to reproduce. There are no kernel messages written to syslog, and the kernel debugger does not start when pressing pause. I assume that means the problem is inside an interrupt handler? Does that exclude XFS as the potential problem? The system is using aic7xxx SCSI adapters and hamachi gigabit ethernet card. We're going to try with a different filesystem and a different gigabit card next, but if you have other suggestions for how to debug this, please let us know. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Wed Jul 18 11:15:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IIF7422336 for linux-xfs-outgoing; Wed, 18 Jul 2001 11:15:07 -0700 Received: from merlin.giref.ulaval.ca (postfix@merlin.giref.ulaval.ca [132.203.7.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IIF4V22317 for ; Wed, 18 Jul 2001 11:15:04 -0700 Received: from giref.ulaval.ca (roederer.giref.ulaval.ca [132.203.7.24]) by merlin.giref.ulaval.ca (Postfix) with ESMTP id 94CF42D4D2; Wed, 18 Jul 2001 14:15:02 -0400 (EDT) Message-ID: <3B55D226.714EFEE4@giref.ulaval.ca> Date: Wed, 18 Jul 2001 14:15:02 -0400 From: Luc Lalonde X-Mailer: Mozilla 4.76 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: Ragnar =?iso-8859-1?Q?Kj=F8rstad?= Cc: linux-xfs@oss.sgi.com Subject: Re: kernel deadlock; xfs References: <20010718195723.A24237@vestdata.no> Content-Type: multipart/mixed; boundary="------------B9287282ED0493E4171E4906" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. --------------B9287282ED0493E4171E4906 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello Ragnar, You wouldn't per chance be using an Adaptec-39160 or Adaptec-29160? If so try the aic7xxx_old instead of the aic7xxx. I've had the same problems and no lockups since I started using the old drivers. (I'm still crossing my fingers though ;-) Cheers, Luc. Ragnar Kjørstad wrote: > > Hi > > We're experiencing a deadlock on a NFS-server using a XFS filesystem. > The kernel was originally running SGI XFS 1.0, but we've now tried 1.0.1 > and the CVS-version (as of yesterday) - same problem. > > The deadlock appear to be happening when accessing big files over NFS, > but we're not sure as we have not found a way to reproduce. There are no > kernel messages written to syslog, and the kernel debugger does not > start when pressing pause. > > I assume that means the problem is inside an interrupt handler? Does > that exclude XFS as the potential problem? > > The system is using aic7xxx SCSI adapters and hamachi gigabit ethernet > card. > > We're going to try with a different filesystem and a different gigabit > card next, but if you have other suggestions for how to debug this, > please let us know. > > -- > Ragnar Kjorstad > Big Storage -- Luc Lalonde, Responsable du reseau GIREF Telephone: (418) 656-2131 poste 6623 Courriel: llalonde@giref.ulaval.ca --------------B9287282ED0493E4171E4906 Content-Type: text/x-vcard; charset=us-ascii; name="llalonde.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Luc Lalonde Content-Disposition: attachment; filename="llalonde.vcf" begin:vcard n:Lalonde;Luc x-mozilla-html:FALSE org:Universite Laval;GIREF adr:;;;;;; version:2.1 email;internet:llalonde@giref.ulaval.ca title:Administateur de reseau x-mozilla-cpt:;0 fn:Luc Lalonde end:vcard --------------B9287282ED0493E4171E4906-- From owner-linux-xfs@oss.sgi.com Wed Jul 18 11:33:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IIXSO22743 for linux-xfs-outgoing; Wed, 18 Jul 2001 11:33:28 -0700 Received: from nevermore.toe.doomcom.org (IDENT:mail@dsl092-078-112.bos1.dsl.speakeasy.net [66.92.78.112]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IIXQV22723 for ; Wed, 18 Jul 2001 11:33:27 -0700 Received: by nevermore.toe.doomcom.org (Postfix, from userid 3499) id 6243120BA0E; Wed, 18 Jul 2001 14:33:25 -0400 (EDT) Date: Wed, 18 Jul 2001 14:33:25 -0400 From: Gerald Britton To: linux-xfs@oss.sgi.com Subject: 2.4.3-SGI_XFS_1.0.1smp leaks? Message-ID: <20010718143325.A4607@nevermore.toe.doomcom.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I ran the 1.0 redhatish kernel for months with no major problems other than a few data corruption bugs on dirty recovery. I was hoping that upgrading to 1.0.1 would fix those issues, but now I seem to be running out of memory in the space of about 2 days. The "used" ammount of memory seems to be higher than the sum of all processes, so it seems like something is leaking userspace memory. Anyone else having these problems? Any fix available? -- Gerald From owner-linux-xfs@oss.sgi.com Wed Jul 18 11:39:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IIdv122954 for linux-xfs-outgoing; Wed, 18 Jul 2001 11:39:57 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IIdtV22934 for ; Wed, 18 Jul 2001 11:39:55 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA00821 for ; Wed, 18 Jul 2001 11:37:27 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2465555; Wed, 18 Jul 2001 13:38:37 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id NAA45515; Wed, 18 Jul 2001 13:38:37 -0500 (CDT) Subject: Re: kernel deadlock; xfs From: Eric Sandeen To: Ragnar =?ISO-8859-1?Q?Kj=C3=B8rstad?= Cc: linux-xfs@oss.sgi.com In-Reply-To: <20010718195723.A24237@vestdata.no> References: <20010718195723.A24237@vestdata.no> Content-Type: text/plain; charset=ISO-8859-1 X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 13:38:31 -0500 Message-Id: <995481511.8987.347.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6IIdtV22935 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 19:57:23 +0200, Ragnar Kjørstad wrote: > There are no > kernel messages written to syslog, and the kernel debugger does not > start when pressing pause. kdb is not turned on by default in 1.0.1, but you can $ echo 1 > /proc/sys/kernel/kdb to enable it... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 18 11:49:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IInt623234 for linux-xfs-outgoing; Wed, 18 Jul 2001 11:49:55 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IInqV23215 for ; Wed, 18 Jul 2001 11:49:52 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id UAA27021; Wed, 18 Jul 2001 20:47:33 +0200 Date: Wed, 18 Jul 2001 20:47:32 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: kernel deadlock; xfs Message-ID: <20010718204732.A26849@vestdata.no> References: <20010718195723.A24237@vestdata.no> <995481511.8987.347.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 0.95.5i In-Reply-To: <995481511.8987.347.camel@stout.americas.sgi.com>; from Eric Sandeen on Wed, Jul 18, 2001 at 01:38:31PM -0500 X-MIME-Autoconverted: from 8bit to quoted-printable by stine.vestdata.no id UAA27021 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6IInrV23216 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 18, 2001 at 01:38:31PM -0500, Eric Sandeen wrote: > On 18 Jul 2001 19:57:23 +0200, Ragnar Kjørstad wrote: > > > There are no > > kernel messages written to syslog, and the kernel debugger does not > > start when pressing pause. > > kdb is not turned on by default in 1.0.1, but you can > > $ echo 1 > /proc/sys/kernel/kdb > > to enable it... We did. My comment was unclear - kdb work except when the lockup occurs. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Wed Jul 18 12:34:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IJYCE24905 for linux-xfs-outgoing; Wed, 18 Jul 2001 12:34:12 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IJY7V24880 for ; Wed, 18 Jul 2001 12:34:07 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6IJXx016207; Wed, 18 Jul 2001 21:33:59 +0200 (CEST) Message-ID: <3B55E49E.5B4B6CEF@pasteur.fr> Date: Wed, 18 Jul 2001 21:33:50 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: nfs/local performance with software raid5 and xfs and SMP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, I would like to add to the xfs performance with sw raid discussion. I encounter the same kind of degraded performance with the following hardware/software combination. Although the degradation can be feel with the local access too, but there are no errors messages :( hardware config The nfs client is a plain redhat 7.1 hardware: K7-1.2GHz 2x256PC133 Abit KT7A motherboard with 2 3com 3c905C NICs (one to an isolated HP procurve switch and the other to a Cisco for the main campus network) The server is a dual P3-866MHz with 4x256PC133 (rocky 3732 mb - chipset Via VT82C694X/VT82C686B) with 1 ide-scsi controller 3ware 3w6800 with 8 IBM-DTLA-307075 72G HDs 20G system boot disk redhat 7.1+SGI xfs 1.0.1 3com 3c905C NICs to an isolated HP procurve switch 3com 3c905C NICs to a Cisco for the main campus network I tried with both kernel smp 2.4.3-2 from xfs-1.0.1 and 2.4.5 with xfs /dev/hda6 is a scratch partition on the system disk (ext2/xfs) /dev/mdo is the software raid device (450GB with xfs) when copying large directory fron the client to the server on the raid5 partition the following error is recorded in the syslog file (on either network HP/Cisco): Jul 18 20:19:44 jason.bis.pasteur.fr kernel: nfs: server nfs.cluster not responding, still trying Jul 18 20:20:08 jason.bis.pasteur.fr last message repeated 2 times Jul 18 20:20:08 jason.bis.pasteur.fr kernel: nfs: server nfs.cluster OK 1) When doing the very same copy to the nfs exported scratch partition either ext2 or xfs the copy is really fast and no error message are found. 2) Doing the same experiments with the UP kernel 2.4.5-xfs /2.4.3-xfs give no errors (xfs on sw raid5 and (xfs,ext2) on scracth partition) 3) with or without noapic does not help either... conclusions: ============ smp+swraid5+xfs : not ok up+swraid5+xfs : ok I will try the cvs version tomorrow Thank you for listening. Tru details: -------- /etc/raidtab file: ----------------- # Sample raid-5 configuration # raiddev /dev/md0 raid-level 5 nr-raid-disks 7 # Spare disks for hot reconstruction nr-spare-disks 1 persistent-superblock 1 chunk-size 64 # the best one for maximum performance: # parity-algorithm left-symmetric #parity-algorithm right-asymmetric #parity-algorithm right-symmetric device /dev/sdb1 raid-disk 0 device /dev/sdc1 raid-disk 1 device /dev/sdd1 raid-disk 2 device /dev/sde1 raid-disk 3 device /dev/sdf1 raid-disk 4 device /dev/sdg1 raid-disk 5 device /dev/sdh1 raid-disk 6 # device /dev/sda1 spare-disk 0 UP-2.4.5-xfs (rpm --rebuild --target=i686 kernel-2.4.5-SGI_XFS_1.0.1.src.rpm) [tru@sheridan ~]$ uname -a Linux sheridan.bis.pasteur.fr 2.4.5-SGI_XFS_1.0.1 #1 Wed Jul 18 15:03:15 CEST 2001 i686 unknown [tru@sheridan ~]$ cat /proc/cmdline auto BOOT_IMAGE=1-245xfs-101 ro root=301 BOOT_FILE=/boot/vmlinuz-2.4.5-SGI_XFS_1.0.1 ramdisk_size=2500 devfs=nomount SMP-2.4.5-xfs (rpm --rebuild --target=i686 kernel-2.4.5-SGI_XFS_1.0.1.src.rpm) [tru@sheridan ~]$ uname -a Linux sheridan.bis.pasteur.fr 2.4.5-SGI_XFS_1.0.1smp #1 SMP Wed Jul 18 14:50:17 [tru@sheridan tru]$ cat /proc/cmdline auto BOOT_IMAGE=1-xfs-101smp ro root=301 BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp ramdisk_size=2500 devfs=nomount UP-2.4.3-2 from the 1.0.2 iso [tru@sheridan ~]$ uname -a Linux sheridan.bis.pasteur.fr 2.4.3-SGI_XFS_1.0.1 #1 Mon Jul 9 14:27:56 CDT 2001 i686 unknown [tru@sheridan ~]$ cat /proc/cmdline auto BOOT_IMAGE=1-xfs-101 ro root=301 BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1 ramdisk_size=2500 devfs=nomount [tru@sheridan ~]$ cat /proc/version Linux version 2.4.3-SGI_XFS_1.0.1 (root@linux-xfs2.americas.sgi.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Jul 9 14:27:56 CDT 2001 SMP-2.4.3-2 from the 1.0.2 iso [tru@sheridan ~]$ uname -a Linux sheridan.bis.pasteur.fr 2.4.3-SGI_XFS_1.0.1smp #1 SMP Mon Jul 9 14:03:40 CDT 2001 i686 unknown [tru@sheridan ~]$ cat /proc/cmdline auto BOOT_IMAGE=1-xfs-101smp ro root=301 BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp ramdisk_size=2500 devfs=nomount -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Wed Jul 18 12:36:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IJadI25236 for linux-xfs-outgoing; Wed, 18 Jul 2001 12:36:39 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IJaPV25198 for ; Wed, 18 Jul 2001 12:36:26 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id MAA09169 for ; Wed, 18 Jul 2001 12:36:15 -0700 (PDT) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA86787; Wed, 18 Jul 2001 12:40:57 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 4837415A46C; Wed, 18 Jul 2001 12:35:08 -0700 (PDT) Subject: noapic strikes back From: Florin Andrei To: linux-xfs@oss.sgi.com, seawolf-list@redhat.com, dledford@redhat.com, linux-kernel@vger.kernel.org Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 18 Jul 2001 12:35:08 -0700 Message-Id: <995484908.1279.0.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to install at least one version of Red Hat 7.1 on it. The problem is, while booting up the installer, when it comes to loading up the SCSI driver (AIC7xxx) the system is frozen. I tried the following boot disks: - stock Red Hat 7.1 - Doug Ledford's updates from people.redhat.com - SGI XFS 1.0.1 I tried to boot the installer with and without "noapic" option. I tried to enable and disable the APIC option in BIOS ("PCI IRQs to IO-APIC Mapping"). I tried all the combinations of these. No luck. :-( Please, is there anything to do about this problem? I *have* to install something newer than RH7.0 on that system. Guys, i will try whatever boot disks you will send to me. I'm willing to be you guinea pig. :-) Just let's kill the APIC problem for good! -- Florin Andrei From owner-linux-xfs@oss.sgi.com Wed Jul 18 12:38:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IJcSm25476 for linux-xfs-outgoing; Wed, 18 Jul 2001 12:38:28 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IJcPV25453 for ; Wed, 18 Jul 2001 12:38:25 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA05912 for ; Wed, 18 Jul 2001 12:35:58 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2465340; Wed, 18 Jul 2001 14:37:07 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA70259; Wed, 18 Jul 2001 14:37:07 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IJc6D18922; Wed, 18 Jul 2001 14:38:06 -0500 Message-Id: <200107181938.f6IJc6D18922@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Gerald Britton cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.3-SGI_XFS_1.0.1smp leaks? In-Reply-To: Message from Gerald Britton of "Wed, 18 Jul 2001 14:33:25 EDT." <20010718143325.A4607@nevermore.toe.doomcom.org> Date: Wed, 18 Jul 2001 14:38:06 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I ran the 1.0 redhatish kernel for months with no major problems other than > a few data corruption bugs on dirty recovery. I was hoping that upgrading to > 1.0.1 would fix those issues, but now I seem to be running out of memory in > the space of about 2 days. The "used" ammount of memory seems to be higher > than the sum of all processes, so it seems like something is leaking userspac > e > memory. Anyone else having these problems? Any fix available? > > -- Gerald Hmm, maybe there is an interaction with changes from redhat, is the machine actually behaving worse? The oss website has been up and running on a 1.0.1 XFS kernel for nearly 31 days now and that machine is pretty busy. However, the kernel happens to be from just before the release and is still 2.4.2 based. Can you post some more info on what it is you are seeing. Thanks Steve From owner-linux-xfs@oss.sgi.com Wed Jul 18 12:40:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IJekF25736 for linux-xfs-outgoing; Wed, 18 Jul 2001 12:40:46 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IJeeV25712 for ; Wed, 18 Jul 2001 12:40:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA01055 for ; Wed, 18 Jul 2001 12:38:13 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2464297 for ; Wed, 18 Jul 2001 14:39:24 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA70478 for ; Wed, 18 Jul 2001 14:39:24 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6IJeN618934; Wed, 18 Jul 2001 14:40:23 -0500 Message-Id: <200107181940.f6IJeN618934@jen.americas.sgi.com> Date: Wed, 18 Jul 2001 14:40:23 -0500 Subject: TAKE - merge up to 2.4.7-pre7 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Lots of stuff in here, the only xfs relevent part of it is a change in mode bit manipulation. I think I got the changes for acls right, but people using default acls on directories may want to check that their mode bits come out as expected. Date: Wed Jul 18 12:32:37 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99116a linux/include/linux/completion.h - 1.1 linux/fs/ntfs/unistr.c - 1.1 linux/fs/ntfs/unistr.h - 1.1 linux/net/unix/af_unix.c - 1.31 linux/net/netsyms.c - 1.34 linux/net/core/dev.c - 1.37 linux/mm/memory.c - 1.51 linux/mm/filemap.c - 1.79 linux/mm/Makefile - 1.8 linux/kernel/sched.c - 1.38 linux/kernel/ksyms.c - 1.96 linux/kernel/kmod.c - 1.15 linux/kernel/fork.c - 1.33 linux/include/linux/sched.h - 1.40 linux/include/linux/ntfs_fs_sb.h - 1.7 linux/include/linux/ntfs_fs_i.h - 1.6 linux/include/linux/genhd.h - 1.13 linux/include/linux/ext2_fs_i.h - 1.3 linux/include/linux/ext2_fs.h - 1.15 linux/include/linux/cdrom.h - 1.19 linux/include/linux/amigaffs.h - 1.4 linux/fs/sysv/namei.c - 1.13 linux/fs/sysv/inode.c - 1.22 linux/fs/sysv/ialloc.c - 1.8 linux/fs/sysv/dir.c - 1.10 linux/fs/ntfs/util.h - 1.4 linux/fs/ntfs/util.c - 1.5 linux/fs/ntfs/sysctl.h - 1.4 linux/fs/ntfs/sysctl.c - 1.3 linux/fs/ntfs/support.h - 1.4 linux/fs/ntfs/support.c - 1.6 linux/fs/ntfs/super.h - 1.5 linux/fs/ntfs/super.c - 1.9 linux/fs/ntfs/struct.h - 1.5 linux/fs/ntfs/ntfstypes.h - 1.5 linux/fs/ntfs/ntfsendian.h - 1.4 linux/fs/ntfs/macros.h - 1.4 linux/fs/ntfs/inode.h - 1.4 linux/fs/ntfs/inode.c - 1.8 linux/fs/ntfs/fs.c - 1.26 linux/fs/ntfs/dir.h - 1.4 linux/fs/ntfs/dir.c - 1.4 linux/fs/ntfs/attr.h - 1.4 linux/fs/ntfs/attr.c - 1.4 linux/fs/ntfs/Makefile - 1.8 linux/fs/namei.c - 1.33 linux/fs/ext2/super.c - 1.18 linux/fs/ext2/inode.c - 1.28 linux/fs/ext2/file.c - 1.16 linux/fs/ext2/dir.c - 1.16 linux/fs/ext2/balloc.c - 1.13 linux/fs/exec.c - 1.42 linux/fs/dquot.c - 1.28 linux/fs/buffer.c - 1.72 linux/fs/binfmt_elf.c - 1.29 linux/fs/affs/namei.c - 1.12 linux/fs/affs/inode.c - 1.13 linux/fs/affs/file.c - 1.17 linux/fs/affs/dir.c - 1.10 linux/fs/affs/amigaffs.c - 1.5 linux/fs/affs/Changes - 1.5 linux/drivers/video/clgenfb.c - 1.19 linux/drivers/usb/usb.c - 1.52 linux/drivers/sound/wavfront.c - 1.17 linux/drivers/sound/msnd_pinnacle.c - 1.16 linux/drivers/scsi/fdomain.c - 1.15 linux/drivers/scsi/atp870u.c - 1.13 linux/drivers/scsi/aha152x.c - 1.20 linux/drivers/net/znet.c - 1.9 linux/drivers/net/yellowfin.c - 1.24 linux/drivers/net/wd.c - 1.14 linux/drivers/net/wavelan.c - 1.21 linux/drivers/net/via-rhine.c - 1.26 linux/drivers/net/smc9194.c - 1.15 linux/drivers/net/smc-ultra.c - 1.17 linux/drivers/net/plip.c - 1.20 linux/drivers/net/net_init.c - 1.20 linux/drivers/net/ne.c - 1.18 linux/drivers/net/loopback.c - 1.9 linux/drivers/net/lance.c - 1.20 linux/drivers/net/hp.c - 1.13 linux/drivers/net/hp-plus.c - 1.14 linux/drivers/net/fmv18x.c - 1.15 linux/drivers/net/eth16i.c - 1.19 linux/drivers/net/epic100.c - 1.24 linux/drivers/net/e2100.c - 1.14 linux/drivers/net/de620.c - 1.12 linux/drivers/net/de600.c - 1.13 linux/drivers/net/bsd_comp.c - 1.6 linux/drivers/net/auto_irq.c - 1.4 linux/drivers/net/at1700.c - 1.12 linux/drivers/net/ac3200.c - 1.15 linux/drivers/net/Space.c - 1.31 linux/drivers/net/Config.in - 1.44 linux/drivers/net/8390.c - 1.22 linux/drivers/net/82596.c - 1.18 linux/drivers/net/3c515.c - 1.19 linux/drivers/net/3c509.c - 1.24 linux/drivers/net/3c507.c - 1.19 linux/drivers/net/3c505.c - 1.20 linux/drivers/net/3c503.c - 1.18 linux/drivers/net/3c501.c - 1.14 linux/drivers/isdn/hisax/hisax.h - 1.19 linux/drivers/isdn/hisax/elsa.c - 1.12 linux/drivers/char/tty_io.c - 1.32 linux/drivers/char/istallion.c - 1.16 linux/drivers/char/esp.c - 1.11 linux/drivers/char/dsp56k.c - 1.14 linux/drivers/cdrom/sbpcd.c - 1.13 linux/drivers/cdrom/cdrom.c - 1.32 linux/drivers/block/rd.c - 1.30 linux/drivers/block/genhd.c - 1.15 linux/drivers/Makefile - 1.23 linux/arch/i386/kernel/setup.c - 1.49 linux/arch/i386/defconfig - 1.62 linux/arch/i386/config.in - 1.59 linux/Makefile - 1.102 linux/MAINTAINERS - 1.64 linux/Documentation/ioctl-number.txt - 1.18 linux/Documentation/filesystems/ntfs.txt - 1.6 linux/Documentation/Configure.help - 1.88 linux/drivers/isdn/isdn_bsdcomp.c - 1.5 linux/drivers/sound/esssolo1.c - 1.29 linux/fs/partitions/check.c - 1.25 linux/fs/partitions/Config.in - 1.12 linux/drivers/isdn/hisax/bkm_a8.c - 1.10 linux/drivers/isdn/hisax/bkm_a4t.c - 1.10 linux/drivers/net/sis900.c - 1.25 linux/drivers/atm/nicstar.c - 1.15 linux/drivers/pcmcia/rsrc_mgr.c - 1.13 linux/drivers/net/pcmcia/pcnet_cs.c - 1.15 linux/drivers/net/pcmcia/3c589_cs.c - 1.16 linux/drivers/char/drm/ioctl.c - 1.6 linux/drivers/char/drm/bufs.c - 1.9 linux/drivers/sound/ac97.c - 1.4 linux/drivers/net/tokenring/ibmtr.c - 1.15 linux/drivers/net/wan/sbni.c - 1.10 linux/drivers/net/pcmcia/3c574_cs.c - 1.14 linux/drivers/net/pcmcia/nmclan_cs.c - 1.12 linux/drivers/net/pcmcia/fmvj18x_cs.c - 1.11 linux/drivers/net/pcmcia/smc91c92_cs.c - 1.12 linux/drivers/net/sis900.h - 1.10 linux/drivers/sound/trident.h - 1.10 linux/drivers/sound/trident.c - 1.23 linux/drivers/net/aironet4500_core.c - 1.14 linux/drivers/net/aironet4500.h - 1.8 linux/drivers/i2c/i2c-dev.c - 1.10 linux/drivers/usb/ov511.c - 1.24 linux/drivers/usb/devio.c - 1.15 linux/drivers/net/8139too.c - 1.23 linux/drivers/isdn/avmb1/b1dma.c - 1.15 linux/Documentation/filesystems/devfs/ChangeLog - 1.10 linux/include/linux/devfs_fs_kernel.h - 1.6 linux/fs/devfs/util.c - 1.6 linux/fs/devfs/base.c - 1.18 linux/drivers/isdn/hysdn/boardergo.c - 1.10 linux/include/linux/lvm.h - 1.8 linux/drivers/net/tulip/tulip_core.c - 1.24 linux/drivers/net/tulip/media.c - 1.11 linux/drivers/net/tulip/21142.c - 1.10 linux/drivers/net/ioc3-eth.c - 1.13 linux/include/linux/usb.h - 1.17 linux/drivers/ide/piix.c - 1.11 linux/drivers/ide/pdc4030.h - 1.2 linux/drivers/ide/pdc4030.c - 1.6 linux/drivers/ide/ide-pmac.c - 1.6 linux/drivers/ide/ide-cd.c - 1.14 linux/drivers/ide/buddha.c - 1.6 linux/drivers/ide/alim15x3.c - 1.10 linux/drivers/ide/ali14xx.c - 1.4 linux/Documentation/DocBook/videobook.tmpl - 1.6 linux/drivers/usb/dsbr100.c - 1.11 linux/drivers/net/pcmcia/xircom_tulip_cb.c - 1.12 linux/include/linux/fs_struct.h - 1.5 linux/fs/xfs/xfs_types.h - 1.53 linux/fs/xfs/xfs_utils.c - 1.38 linux/drivers/char/drm/r128_bufs.c - 1.5 linux/drivers/char/drm/mga_bufs.c - 1.5 linux/drivers/char/drm/i810_dma.c - 1.7 linux/drivers/char/drm/i810_bufs.c - 1.3 linux/drivers/usb/bluetooth.c - 1.13 linux/drivers/net/natsemi.c - 1.10 linux/drivers/media/video/zr36120.c - 1.7 linux/drivers/media/video/bttv-driver.c - 1.10 linux/drivers/char/i810-tco.c - 1.7 linux/drivers/md/lvm.c - 1.13 linux/Documentation/filesystems/ext2.txt - 1.3 linux/drivers/net/hamachi.c - 1.9 linux/drivers/net/sundance.c - 1.9 linux/drivers/net/winbond-840.c - 1.10 linux/drivers/ide/slc90e66.c - 1.4 linux/drivers/net/isa-skeleton.c - 1.5 linux/drivers/net/tulip/ChangeLog - 1.8 linux/drivers/net/lasi_82596.c - 1.5 linux/drivers/usb/serial/Config.in - 1.6 linux/mm/shmem.c - 1.8 linux/drivers/char/drm/radeon_bufs.c - 1.4 linux/drivers/usb/serial/io_edgeport.c - 1.6 linux/drivers/net/wireless/airo.c - 1.3 linux/drivers/net/lp486e.c - 1.2 linux/drivers/net/dl2k.h - 1.2 linux/Documentation/networking/dl2k.txt - 1.2 linux/drivers/net/dl2k.c - 1.2 From owner-linux-xfs@oss.sgi.com Wed Jul 18 12:45:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IJjd726126 for linux-xfs-outgoing; Wed, 18 Jul 2001 12:45:39 -0700 Received: from lacrosse.corp.redhat.com (host154.207-175-42.redhat.com [207.175.42.154]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IJjaV26104 for ; Wed, 18 Jul 2001 12:45:36 -0700 Received: from redhat.com (dledford.cipe.redhat.com [10.0.0.84]) by lacrosse.corp.redhat.com (8.9.3/8.9.3) with ESMTP id PAA17149; Wed, 18 Jul 2001 15:45:30 -0400 Message-ID: <3B55E7A8.1786F70A@redhat.com> Date: Wed, 18 Jul 2001 15:46:48 -0400 From: Doug Ledford X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: Florin Andrei CC: linux-xfs@oss.sgi.com, seawolf-list@redhat.com, linux-kernel@vger.kernel.org Subject: Re: noapic strikes back References: <995484908.1279.0.camel@stantz.corp.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Florin Andrei wrote: > > I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to > install at least one version of Red Hat 7.1 on it. > The problem is, while booting up the installer, when it comes to loading > up the SCSI driver (AIC7xxx) the system is frozen. > > I tried the following boot disks: > - stock Red Hat 7.1 > - Doug Ledford's updates from people.redhat.com > - SGI XFS 1.0.1 > > I tried to boot the installer with and without "noapic" option. When using my boot disk, you have to use the "apic" option, not the "noapic" option. -- Doug Ledford http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems From owner-linux-xfs@oss.sgi.com Wed Jul 18 12:54:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IJs5Z26699 for linux-xfs-outgoing; Wed, 18 Jul 2001 12:54:05 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IJs1V26679 for ; Wed, 18 Jul 2001 12:54:01 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA18723; Wed, 18 Jul 2001 21:53:58 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA00315; Wed, 18 Jul 2001 21:53:58 +0200 (CEST) Date: Wed, 18 Jul 2001 21:53:58 +0200 (CEST) From: Seth Mos To: Tru Huynh cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: <3B55E49E.5B4B6CEF@pasteur.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001, Tru Huynh wrote: > Hello, > > I would like to add to the xfs performance with sw raid discussion. > I encounter the same kind of degraded performance with the > following hardware/software combination. > Although the degradation can be feel with the local access too, > but there are no errors messages :( > > hardware config > > The nfs client is a plain redhat 7.1 > hardware: K7-1.2GHz 2x256PC133 Abit KT7A motherboard > with 2 3com 3c905C NICs (one to an isolated HP procurve > switch and the other to a Cisco for the main campus network) > > The server is a dual P3-866MHz with 4x256PC133 > (rocky 3732 mb - chipset Via VT82C694X/VT82C686B) > with 1 ide-scsi controller 3ware 3w6800 with 8 IBM-DTLA-307075 72G HDs > 20G system boot disk redhat 7.1+SGI xfs 1.0.1 > 3com 3c905C NICs to an isolated HP procurve switch > 3com 3c905C NICs to a Cisco for the main campus network > > I tried with both kernel smp 2.4.3-2 from xfs-1.0.1 and 2.4.5 with xfs > > /dev/hda6 is a scratch partition on the system disk (ext2/xfs) > /dev/mdo is the software raid device (450GB with xfs) > > when copying large directory fron the client to the server > on the raid5 partition the following error is recorded in > the syslog file (on either network HP/Cisco): > Jul 18 20:19:44 jason.bis.pasteur.fr kernel: nfs: server nfs.cluster not > responding, still trying > Jul 18 20:20:08 jason.bis.pasteur.fr last message repeated 2 times > Jul 18 20:20:08 jason.bis.pasteur.fr kernel: nfs: server nfs.cluster OK This looks like packets getting lost. Do you see this one network in particular? I have had this exact problem with a rotten network cable. Yours might be fine but something is giving. It might be the driver for your network card dropping packets or something on the switch. I have used a 3c950b and a intel eepro 100 for respectively server and client. Have you tried running a bonnie over NFS and see what througput you are seeing? Does the NFS server become unavailable when running multiple bonnies? Something might be generating so much interrupts that it can't handle all of them resulting in packet loss. > 1) When doing the very same copy to the nfs exported scratch partition > either ext2 or xfs the copy is really fast and no error message are > found. This could be that your 3ware controller is interfering with your system. Did you try the latest cvs and firmware for your 3ware card? > 2) Doing the same experiments with the UP kernel 2.4.5-xfs /2.4.3-xfs > give no errors (xfs on sw raid5 and (xfs,ext2) on scracth partition) The 3ware driver does not like SMP perhaps? > 3) with or without noapic does not help either... Maybe you have found a combination of factors which your hardware or the linux kernel does not like. Cheers Seth From owner-linux-xfs@oss.sgi.com Wed Jul 18 13:03:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IK3rC27604 for linux-xfs-outgoing; Wed, 18 Jul 2001 13:03:53 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IK3oV27582 for ; Wed, 18 Jul 2001 13:03:51 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id WAA471637 for ; Wed, 18 Jul 2001 22:03:38 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2465637; Wed, 18 Jul 2001 15:02:31 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA62225; Wed, 18 Jul 2001 15:02:30 -0500 (CDT) Subject: Re: installer is not working From: Eric Sandeen To: fperin@kaplan.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <001301c10fa5$32ba3890$9865fea9@COSMO4> References: <001301c10fa5$32ba3890$9865fea9@COSMO4> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 15:02:24 -0500 Message-Id: <995486544.11035.23.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 12:17:52 -0400, G. Francisco Perin wrote: > We are consistently getting the same error when using the RH7.1-SGI > installer. When we get to the package installation portion of the process, > it asks us to insert RH7.1 cd1 and we're getting "cd1 is not cd1" error. We > are using an official RH7.1 release. Has anyone seen this before??? Ok, it looks like the media shipped from Dell is a little different, it has a different timestamp in the disk ID file. I have put an updated floppy image in ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer/updates Follow the README instructions to create an update disk, and the installer should continue; HOWEVER, since your CDs apparently are NOT exact copies of the CDs Red Hat ships, I can't guarantee that you won't run into another problem down the line... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 18 13:09:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IK9uR28087 for linux-xfs-outgoing; Wed, 18 Jul 2001 13:09:56 -0700 Received: from isis.telemach.net (isis.telemach.net [213.143.65.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IK9sV28062 for ; Wed, 18 Jul 2001 13:09:54 -0700 Received: from open (TM-68-212.cable.telemach.net [213.143.68.212]) by isis.telemach.net (Postfix) with SMTP id 8F9ED7A103; Wed, 18 Jul 2001 22:09:51 +0200 (CEST) Date: Wed, 18 Jul 2001 22:10:02 +0200 From: Jure Pecar To: Florin Andrei Cc: linux-xfs@oss.sgi.com, seawolf-list@redhat.com, dledford@redhat.com, linux-kernel@vger.kernel.org Subject: Re: noapic strikes back Message-Id: <20010718221002.76e7cca6.pegasus@telemach.net> In-Reply-To: <995484908.1279.0.camel@stantz.corp.sgi.com> References: <995484908.1279.0.camel@stantz.corp.sgi.com> Organization: Select Technology X-Mailer: Sylpheed version 0.5.0 (GTK+ 1.2.8; i586-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 12:35:08 -0700 Florin Andrei wrote: > I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to > install at least one version of Red Hat 7.1 on it. This is a known issue. Check RedHat's Bugzilla to find out more. -- Jure Pecar From owner-linux-xfs@oss.sgi.com Wed Jul 18 13:12:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IKCQa28386 for linux-xfs-outgoing; Wed, 18 Jul 2001 13:12:26 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IKCOV28365 for ; Wed, 18 Jul 2001 13:12:24 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA20825; Wed, 18 Jul 2001 22:12:22 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA02479; Wed, 18 Jul 2001 22:12:22 +0200 (CEST) Date: Wed, 18 Jul 2001 22:12:22 +0200 (CEST) From: Seth Mos To: Eric Sandeen cc: fperin@kaplan.com, linux-xfs@oss.sgi.com Subject: Re: installer is not working In-Reply-To: <995486544.11035.23.camel@stout.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001, Eric Sandeen wrote: > On 18 Jul 2001 12:17:52 -0400, G. Francisco Perin wrote: > > We are consistently getting the same error when using the RH7.1-SGI > > installer. When we get to the package installation portion of the process, > > it asks us to insert RH7.1 cd1 and we're getting "cd1 is not cd1" error. We > > are using an official RH7.1 release. Has anyone seen this before??? > > Ok, it looks like the media shipped from Dell is a little different, it > has a different timestamp in the disk ID file. > > I have put an updated floppy image in > ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer/updates > > Follow the README instructions to create an update disk, and the > installer should continue; HOWEVER, since your CDs apparently are NOT > exact copies of the CDs Red Hat ships, I can't guarantee that you won't > run into another problem down the line... The are remade redhat disks which they call SBE editions. That stands for System builder edition. They are different and updated to fit Dell Hardware. see http://domsch.com/linux for Dell related linux stuff. Cheers Seth From owner-linux-xfs@oss.sgi.com Wed Jul 18 13:44:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IKi9b30824 for linux-xfs-outgoing; Wed, 18 Jul 2001 13:44:09 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IKi8V30802 for ; Wed, 18 Jul 2001 13:44:08 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA02563 for ; Wed, 18 Jul 2001 13:18:13 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2442343; Wed, 18 Jul 2001 15:17:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id PAA46716; Wed, 18 Jul 2001 15:17:05 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IKI4W19114; Wed, 18 Jul 2001 15:18:04 -0500 Message-Id: <200107182018.f6IKI4W19114@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Tru Huynh of "Wed, 18 Jul 2001 21:33:50 +0200." <3B55E49E.5B4B6CEF@pasteur.fr> Date: Wed, 18 Jul 2001 15:18:04 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hello, > > I would like to add to the xfs performance with sw raid discussion. > I encounter the same kind of degraded performance with the > following hardware/software combination. > Although the degradation can be feel with the local access too, > but there are no errors messages :( > I have asked some internal testers here to try out some more raid5 stuff. We did do testing on it, but probably not performance testing. Steve From owner-linux-xfs@oss.sgi.com Wed Jul 18 13:48:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IKmPc31251 for linux-xfs-outgoing; Wed, 18 Jul 2001 13:48:25 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IKmNV31232 for ; Wed, 18 Jul 2001 13:48:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id NAA05436 for ; Wed, 18 Jul 2001 13:45:56 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2463271; Wed, 18 Jul 2001 15:47:06 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA54590; Wed, 18 Jul 2001 15:47:06 -0500 (CDT) Subject: Re: installer is not working From: Eric Sandeen To: Seth Mos Cc: fperin@kaplan.com, linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 18 Jul 2001 15:46:59 -0500 Message-Id: <995489219.11040.56.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 22:12:22 +0200, Seth Mos wrote: > The are remade redhat disks which they call SBE editions. That stands for > System builder edition. They are different and updated to fit Dell > Hardware. > > see http://domsch.com/linux for Dell related linux stuff. Ah, based on that information, these disks will not work with the XFS installer, since MANY of the RPMs have changed, and the installer won't find what it's expecting on the Dell CDs. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 18 14:00:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IL0fu32323 for linux-xfs-outgoing; Wed, 18 Jul 2001 14:00:41 -0700 Received: from studsv07.studserv.uni-stuttgart.de (studsv07.studserv.uni-stuttgart.de [129.69.21.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IL0cV32303 for ; Wed, 18 Jul 2001 14:00:39 -0700 Received: from ysabell.wh.vaih [129.69.166.244] by studsv07.studserv.uni-stuttgart.de with ESMTP (SMTPD32-6.06) id A8F5337026A; Wed, 18 Jul 2001 23:00:37 +0200 Received: from marcelo by ysabell.wh.vaih with local (Exim 3.22 #1 (Debian)) id 15MyR0-0004SX-00 for ; Wed, 18 Jul 2001 23:00:42 +0200 Date: Wed, 18 Jul 2001 23:00:42 +0200 From: "Marcelo E. Magallon" To: linux-xfs@oss.sgi.com Subject: libacl.a in /lib, xfstests looks for it in /usr/lib Message-ID: <20010718230042.A17135@ysabell.wh.vaih> 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.3.18i X-Operating-System: Linux ysabell 2.4.6-pre9-xfs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I think subject says it all. Skimming thru the build logs of the last few days I find: [...] Wrote: /somepath/acl/build/rpm/acl-1.1.0-0.i386.rpm Wrote: /somepath/build/rpm/acl-devel-1.1.0-0.i386.rpm install: acl-1.1.0-0 ok install: acl-devel-1.1.0-0 ok [...] checking for sys/acl.h... yes checking for acl_get in -lacl... yes [...] make[1]: Entering directory `/xfs-stress-test/test/xfstests' === include === make[2]: Nothing to be done for `default'. === src === gcc -O1 -g -DDEBUG -funsigned-char -Wall -I../include '-DVERSION="1.0.0"' -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/xfs -I/usr/include/attr alloc.c -o alloc gcc -O1 -g -DDEBUG -funsigned-char -Wall -I../include '-DVERSION="1.0.0"' -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/xfs -I/usr/include/attr -c -o acl_get.o acl_get.c make[2]: *** No rule to make target `/usr/lib/libacl.a', needed by `acl_get'. Stop. -- Marcelo From owner-linux-xfs@oss.sgi.com Wed Jul 18 14:04:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IL4x432767 for linux-xfs-outgoing; Wed, 18 Jul 2001 14:04:59 -0700 Received: from mail.websolut.net (gw-websolut.itnet.pt [212.54.140.241] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IL4qV32743 for ; Wed, 18 Jul 2001 14:04:54 -0700 Received: (from daniel@localhost) by mail.websolut.net (8.11.0/8.11.0) id f6IL4bk22248; Wed, 18 Jul 2001 22:04:38 +0100 Message-ID: X-Mailer: XFMail 1.4.7 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <995484908.1279.0.camel@stantz.corp.sgi.com> Date: Wed, 18 Jul 2001 22:04:37 +0100 (WEST) From: daniel@websolut.net To: Florin Andrei Subject: RE: noapic strikes back Cc: linux-kernel@vger.kernel.org, dledford@redhat.com, seawolf-list@redhat.com, linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there! I too have that problem on Intel ISP2150 servers (L440GX+ motherboard is the problem, of course) and I've seen even quite amazing things - there are boot disks that work (you don't see the message complaining about shared IRQ 11, whatever) but the kernel that is put on disk from the installation rpm is not coherent with the one made for the disk (apic'ed or not apic'ed), so I actually could install from the first redhat 7.1 xfs iso (xfs 1.0) and get that problem only upon the first boot from disk - systems hangs forever. With the problem of fitting a kernel image (with xfs and softraid gets too big) onto a disk, I could only solve this, compiling my own and putting it on a network tftp server and booting with PXE (intel servers -> intel NIC -> Fancy Network Boot); I suppose emulating a 2.88 disk and making a bootable CD would also do (if you have a CD-ROM). Cheers, Daniel Fonseca On 18-Jul-2001 Florin Andrei wrote: > I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to > install at least one version of Red Hat 7.1 on it. > The problem is, while booting up the installer, when it comes to loading > up the SCSI driver (AIC7xxx) the system is frozen. > > I tried the following boot disks: > - stock Red Hat 7.1 > - Doug Ledford's updates from people.redhat.com > - SGI XFS 1.0.1 > > I tried to boot the installer with and without "noapic" option. > > I tried to enable and disable the APIC option in BIOS ("PCI IRQs to > IO-APIC Mapping"). > > I tried all the combinations of these. No luck. :-( > > Please, is there anything to do about this problem? I *have* to install > something newer than RH7.0 on that system. > > Guys, i will try whatever boot disks you will send to me. I'm willing to > be you guinea pig. :-) Just let's kill the APIC problem for good! > > -- > Florin Andrei -- ---------------------------------- E-Mail: daniel@websolut.net Date: 18-Jul-2001 Time: 21:25:56 This message was sent by XFMail ---------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 18 14:12:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ILCjQ01028 for linux-xfs-outgoing; Wed, 18 Jul 2001 14:12:45 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ILCgV01006 for ; Wed, 18 Jul 2001 14:12:43 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id XAA470417 for ; Wed, 18 Jul 2001 23:12:30 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2464916; Wed, 18 Jul 2001 16:11:23 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA45458; Wed, 18 Jul 2001 16:11:23 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6ILCLj24838; Wed, 18 Jul 2001 16:12:21 -0500 Message-Id: <200107182112.f6ILCLj24838@jen.americas.sgi.com> To: "Marcelo E. Magallon" cc: linux-xfs@oss.sgi.com Subject: Re: libacl.a in /lib, xfstests looks for it in /usr/lib References: <20010718230042.A17135@ysabell.wh.vaih> Comments: In-reply-to "Marcelo E. Magallon" message dated "Wed, 18 Jul 2001 23:00:42 +0200." Date: Wed, 18 Jul 2001 16:12:21 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have hit the same thing, if you want to 'fix it' change the configure.in file in the cmd/xfstests directory: =========================================================================== Index: cmd/xfstests/configure.in =========================================================================== --- /usr/tmp/TmpDir.24826-0/cmd/xfstests/configure.in_1.8 Wed Jul 18 16:09:53 2001 +++ cmd/xfstests/configure.in Wed Jul 18 16:09:42 2001 @@ -176,7 +176,7 @@ echo 'Install either the acl-devel (rpm) or the acl-dev (deb) package.' exit 1 ]) -libacl="/usr/lib/libacl.a" +libacl="/lib/libacl.a" AC_SUBST(libacl) dnl Checks for GNU database manager header and library. Then rerun configure and rebuild the tests. I will see what Nathan wants to do with this, he has been restructuring packages recently. Steve > Hi, > > I think subject says it all. Skimming thru the build logs of the last > few days I find: > > [...] > Wrote: /somepath/acl/build/rpm/acl-1.1.0-0.i386.rpm > Wrote: /somepath/build/rpm/acl-devel-1.1.0-0.i386.rpm > > install: acl-1.1.0-0 ok > install: acl-devel-1.1.0-0 ok > [...] > checking for sys/acl.h... yes > checking for acl_get in -lacl... yes > [...] > make[1]: Entering directory `/xfs-stress-test/test/xfstests' > === include === > make[2]: Nothing to be done for `default'. > === src === > gcc -O1 -g -DDEBUG -funsigned-char -Wall -I../include '-DVERSION="1.0.0"' - > D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/xfs -I/usr/include/attr > alloc.c -o alloc > gcc -O1 -g -DDEBUG -funsigned-char -Wall -I../include '-DVERSION="1.0.0"' - > D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/xfs -I/usr/include/attr - > c -o acl_get.o acl_get.c > make[2]: *** No rule to make target `/usr/lib/libacl.a', needed by `acl_get' > . Stop. > > -- > Marcelo From owner-linux-xfs@oss.sgi.com Wed Jul 18 14:39:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ILdCQ03515 for linux-xfs-outgoing; Wed, 18 Jul 2001 14:39:12 -0700 Received: from dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ILd9V03496 for ; Wed, 18 Jul 2001 14:39:10 -0700 Received: (from ak@localhost) by dkp.com (8.9.3/8.9.3) id RAA00570 for linux-xfs@oss.sgi.com; Wed, 18 Jul 2001 17:39:08 -0400 Date: Wed, 18 Jul 2001 17:39:08 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Kernel Oops - 1.0.1 Message-ID: <20010718173908.B29096@key.dkp.com> 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.2i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just had this oops, with 2.4.3-SGI_XFS_1.0.1_PR3: kdb> bt EBP EIP Function(args) 0xc9023fbc 0xc0131d3f sys_open+0x53 (0x8081a78, 0x80c1, 0x1fd, 0x40016b64, 0xbf) kernel .text 0xc0100000 0xc0131cec 0xc0131d8c 0xc0106c97 system_call+0x33 kernel .text 0xc0100000 0xc0106c64 0xc0106c9c Any idea what this is? Has it been fixed in 1.0.1? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Wed Jul 18 15:45:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IMjbh09354 for linux-xfs-outgoing; Wed, 18 Jul 2001 15:45:37 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IMjaV09333 for ; Wed, 18 Jul 2001 15:45:36 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA12394 for ; Wed, 18 Jul 2001 15:45:24 -0700 (PDT) mail_from (dxm@snort.melbourne.sgi.com) Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id IAA21596; Thu, 19 Jul 2001 08:44:16 +1000 (EST) Message-Id: <200107182244.IAA21596@snort.melbourne.sgi.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Eric Sandeen cc: linux-xfs@oss.sgi.com Subject: Re: XFS problems In-reply-to: Your message of "18 Jul 2001 11:25:48 EST." <995473548.8982.209.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Jul 2001 08:44:15 +1000 From: Daniel Moore Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen writes: => Can you send the mkfs.xfs output that did appear? => => > mount -t xfs /dev/hde7 /mnt => > #fails with => > > mount: wrong fs type, bad option , bad superblock on /dev/hde7, => > > or too many mounted filesystems => => Hm, wish this error was less Windows-like*. :) => This is annoying message indeed, but XFS usually logs messages to to the console/syslog on mount errors (these should be more informative). I haven't been following this thread, but have you checked that XFS is enabled in the kernel/loaded? ----------------------------------------------------- Daniel Moore dxm@sgi.com R&D Software Engineer Phone: +61-3-98348209 SGI Performance Tools Group Fax: +61-3-98132378 ----------------------------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 18 15:51:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IMpPQ09956 for linux-xfs-outgoing; Wed, 18 Jul 2001 15:51:25 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IMpNV09934 for ; Wed, 18 Jul 2001 15:51:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA04332 for ; Wed, 18 Jul 2001 15:51:01 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2466071; Wed, 18 Jul 2001 17:49:53 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA45575; Wed, 18 Jul 2001 17:49:53 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6IMop325083; Wed, 18 Jul 2001 17:50:51 -0500 Message-Id: <200107182250.f6IMop325083@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Daniel Moore cc: Eric Sandeen , linux-xfs@oss.sgi.com Subject: Re: XFS problems In-Reply-To: Message from Daniel Moore of "Thu, 19 Jul 2001 08:44:15 +1000." <200107182244.IAA21596@snort.melbourne.sgi.com> Date: Wed, 18 Jul 2001 17:50:51 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Eric Sandeen writes: > > => Can you send the mkfs.xfs output that did appear? > => > => > mount -t xfs /dev/hde7 /mnt > => > #fails with > => > > mount: wrong fs type, bad option , bad superblock on /dev/hde7, > => > > or too many mounted filesystems > => > => Hm, wish this error was less Windows-like*. :) > => > > This is annoying message indeed, but XFS usually logs messages to to > the console/syslog on mount errors (these should be more informative). > > I haven't been following this thread, but have you checked that XFS is > enabled in the kernel/loaded? I would me more suspicous of mkfs not actually doing anything, until we see output along the lines of the usual: meta-data=/dev/hda6 isize=256 agcount=8, agsize=197800 blks data = bsize=4096 blocks=1582394, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=1200 realtime =none extsz=65536 blocks=0, rtextents=0 there is always a chance it core dumped and never actually got to change the filesystem - unless the ext2 metadata survived the mkfs enough to be mountable and useable. Steve > > ----------------------------------------------------- > Daniel Moore dxm@sgi.com > R&D Software Engineer Phone: +61-3-98348209 > SGI Performance Tools Group Fax: +61-3-98132378 > ----------------------------------------------------- > From owner-linux-xfs@oss.sgi.com Wed Jul 18 16:03:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6IN3H711173 for linux-xfs-outgoing; Wed, 18 Jul 2001 16:03:17 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6IN3FV11153 for ; Wed, 18 Jul 2001 16:03:15 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id QAA03169 for ; Wed, 18 Jul 2001 16:03:02 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 JAA15232; Thu, 19 Jul 2001 09:01:57 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA22357; Thu, 19 Jul 2001 09:01:53 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107190901.ZM222029@wobbly.melbourne.sgi.com> Date: Thu, 19 Jul 2001 09:01:51 +1000 In-Reply-To: Steve Lord "Re: libacl.a in /lib, xfstests looks for it in /usr/lib" (Jul 18, 4:12pm) References: <20010718230042.A17135@ysabell.wh.vaih> <200107182112.f6ILCLj24838@jen.americas.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Steve Lord , "Marcelo E. Magallon" Subject: Re: libacl.a in /lib, xfstests looks for it in /usr/lib Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 18, 4:12pm, Steve Lord wrote: > Subject: Re: libacl.a in /lib, xfstests looks for it in /usr/lib > > I have hit the same thing, if you want to 'fix it' change the configure.in > file in the cmd/xfstests directory: > ... > > Then rerun configure and rebuild the tests. > > I will see what Nathan wants to do with this, he has been restructuring > packages recently. > yup, will get to it in a tick. just wading through the final details of xfsdump & dmapi with Dean now. above fix looks good - I'll checkin the fix shortly (if that hasn't been done already). thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Jul 18 16:16:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6INGcH12601 for linux-xfs-outgoing; Wed, 18 Jul 2001 16:16:38 -0700 Received: from dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6INGaV12576 for ; Wed, 18 Jul 2001 16:16:36 -0700 Received: (from ak@localhost) by dkp.com (8.9.3/8.9.3) id TAA01915 for linux-xfs@oss.sgi.com; Wed, 18 Jul 2001 19:16:35 -0400 Date: Wed, 18 Jul 2001 19:16:35 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Kernel Debugger Message-ID: <20010718191635.A1810@key.dkp.com> 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.2i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I noticed that "Ctrl-A" at the console seems to dump me into the kernel debugger. Is there any way to turn this behaviour off? The program that I use to monitor the kernel on our fileservers via the serial port uses "Ctrl-A" as a command character, and I'm afraid that I'm going to accidentally type it twice in a row sometime, sending a "Ctrl-A" character down the wire... Andrew Klaassen From owner-linux-xfs@oss.sgi.com Wed Jul 18 16:16:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6INGmd12668 for linux-xfs-outgoing; Wed, 18 Jul 2001 16:16:48 -0700 Received: from storm.physik.tu-cottbus.de (storm.physik.TU-Cottbus.De [141.43.75.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6INGlV12649 for ; Wed, 18 Jul 2001 16:16:47 -0700 Received: by storm.physik.tu-cottbus.de (Postfix, from userid 7215) id 1E8656004D; Thu, 19 Jul 2001 01:16:43 +0200 (CEST) Date: Thu, 19 Jul 2001 01:16:42 +0200 To: linux-xfs@oss.sgi.com Subject: Re: Xfs prblems with clearcase mvfs Message-ID: <20010719011642.A8739@physik.tu-cottbus.de> References: <200107181516.f6IFGNa04739@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107181516.f6IFGNa04739@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i From: heinold@physik.tu-cottbus.de (H.Heinold) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I have to add that clearcase 4.1(I think 4.2 too) under linux 2.4.2 is not a good choice. If you setup views on the server there can bee oopes after sometime. As written on the clearcase-ml you need three patches to the stock 2.4.2 kernel to get the mvfs modules run. As I remember correctly the 2.4.2-ac3, the linux-2.4.2-tux-vfs.patch and the linux-2.4.2-zerocopy.patch. -- Henning Heinold From owner-linux-xfs@oss.sgi.com Wed Jul 18 16:45:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6INjOY16011 for linux-xfs-outgoing; Wed, 18 Jul 2001 16:45:24 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6INjMV15985 for ; Wed, 18 Jul 2001 16:45:22 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ5WF>; Wed, 18 Jul 2001 18:44:28 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643458@AUSMAIL> From: "Gonyou, Austin" To: "'ivanr@melbourne.sgi.com'" , "Gonyou, Austin" Cc: Linux XFS Mailing List Subject: RE: dumping multiple sessions to a single tape with XFS dump. Date: Wed, 18 Jul 2001 18:44:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk If I perform the following: xfsdump -f /dev/nst0 -L "Boot FS" -m "test1" /boot xfsdump -f /dev/nst0 -L "Home FS" -m "test1" /home mt /dev/st0 rewind then xfsrestore -f /dev/st0 -t I only get data from /boot listed..and thats all that xfsrestore says it has found. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: ivanr@melbourne.sgi.com [mailto:ivanr@melbourne.sgi.com] > Sent: Tuesday, July 17, 2001 7:49 PM > To: Gonyou, Austin > Cc: Linux XFS Mailing List > Subject: Re: dumping multiple sessions to a single tape with XFS dump. > > > On Tue, 17 Jul 2001, Gonyou, Austin wrote: > > > I still can't do it. If anyone could show me their scripts > or perhaps give a > > brief example, I'd like to see it. Thanks. > > Perhaps you could give us a little more detail: > > - why do you think it is not working for you (ie. specific symptoms) > - the xfsdump command line you use > - the output from xfsdump > - the output of xfsdump -I > - what else/if anything do you store on the tape (eg. tar files, etc) > - what kind of tape device and driver do you use (eg. scsi, ide, etc) > > Thanks, > Ivan > > -- > Ivan Rayner > ivanr@melbourne.sgi.com > From owner-linux-xfs@oss.sgi.com Wed Jul 18 17:11:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J0BhR18710 for linux-xfs-outgoing; Wed, 18 Jul 2001 17:11:43 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J0BcV18683 for ; Wed, 18 Jul 2001 17:11:38 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id RAA27491 for ; Wed, 18 Jul 2001 17:11:27 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 KAA15744; Thu, 19 Jul 2001 10:10:16 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA17978; Thu, 19 Jul 2001 10:10:05 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107191010.ZM220212@wobbly.melbourne.sgi.com> Date: Thu, 19 Jul 2001 10:10:03 +1000 In-Reply-To: Tad Dolphay "Re: Quota reporting for NFS mounts" (Jul 18, 10:32am) References: <200107181532.KAA30810@fsgi158.americas.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Jan Kara , Tad Dolphay , fermin@eup.udl.es (Fermin Molina) Subject: Re: Quota reporting for NFS mounts Cc: linux-xfs@oss.sgi.com, syrekron@iastate.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi all, On Jul 18, 10:32am, Tad Dolphay wrote: > Subject: Re: Quota reporting for NFS mounts > > > > > > > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > > > > > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > > > > > built from the source rpm. > > > > > > > > > > I have exported my /export partition over NFS which file system is XFS. > > > > > > > > > > I can mount this from client type machines, but when I try (on the > > > > > client) to list my quota, the command just hangs. I've run snoop on the > > > > > connection, and it appears that my server (sherlock) doesn't respond to > > > > > the client's (cousteau) requests. > > > > > > > > > > I also verified that rpc.rquotad is running on my server. > > > > > > > > > > Any idea how I can get remote quota reporting working? > > > > > > > > > > > > Similar configuration. My NFS-client machine is a Sun (Solaris 2.7). > > > > On my linux XFS-NFS server, rpc.rquotad segfaults when I run > > > > quota -v on the client (Sun). > > > > > > > I'm able to use "quota -v " on a SUN client with an XFS-NFS server > > > without any problems. I do find, though, that if I mount an NFS exported > > > file system on IRIX or SUN with the quota option and the file system is > > > not mounted on the server with the usrquota option then rpc.rquotad segfaults. > > > This happens with both xfs and ext2 file systems. Could it be a similar > > > problem? > > > > > > I'm not using the quota option when I mount on SUN. > > But I use usrquota on XFS-linux server. > > > > I just tried that and that seems to kill rpc.rquotad for me too. > Could you build & install a debug (-g) version of rpc.rquotad, attach to it with gdb while its running, then repeat the above and send the stack trace & any other interesting info gdb will give? I don't have access to any Sun machines, but I know that these combinations of client<->server work, and are tested: Linux<->Linux IRIX<->Linux Linux<->IRIX I assume this same problem will happen with ext2 quota (could someone confirm that?) - Jan, have you seen this issue before? [Jan - the mail thread is available here... http://oss.sgi.com/projects/xfs/mail_archive/0107/msg00730.html although I'm unsure whether or not the original problem involved a Sun machine] thanks. > > What quota options use you on client/server? > > I need to use "quota" option when I mount on SUN? > > (using snoop I see requests to the server without > > using it...) > > > I use usrquota on server and quota option on SUN client and everything > works fine for me. > > Tad > >-- End of excerpt from Tad Dolphay -- Nathan From owner-linux-xfs@oss.sgi.com Wed Jul 18 17:20:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J0KAD19499 for linux-xfs-outgoing; Wed, 18 Jul 2001 17:20:10 -0700 Received: from atrey.karlin.mff.cuni.cz (root@atrey.karlin.mff.cuni.cz [195.113.31.123]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J0K7V19479 for ; Wed, 18 Jul 2001 17:20:07 -0700 Received: (from jack@localhost) by atrey.karlin.mff.cuni.cz (8.9.3/8.9.3/Debian 8.9.3-21) id CAA28878; Thu, 19 Jul 2001 02:19:42 +0200 Date: Thu, 19 Jul 2001 02:19:42 +0200 From: Jan Kara To: Nathan Scott Cc: Tad Dolphay , Fermin Molina , linux-xfs@oss.sgi.com, syrekron@iastate.edu Subject: Re: Quota reporting for NFS mounts Message-ID: <20010719021942.A28795@atrey.karlin.mff.cuni.cz> References: <200107181532.KAA30810@fsgi158.americas.sgi.com> <10107191010.ZM220212@wobbly.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.15i In-Reply-To: <10107191010.ZM220212@wobbly.melbourne.sgi.com>; from nathans@wobbly.melbourne.sgi.com on Thu, Jul 19, 2001 at 10:10:03AM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, > On Jul 18, 10:32am, Tad Dolphay wrote: > > Subject: Re: Quota reporting for NFS mounts > > > > > > > > > I'm running redhat 7.1 with release 1.0.1 kernel 2.4.3 (IIRC, it is the > > > > > > one based on the redhat kernel). I'm also using quota-3.01-pre7 which I > > > > > > built from the source rpm. > > > > > > > > > > > > I have exported my /export partition over NFS which file system is XFS. > > > > > > > > > > > > I can mount this from client type machines, but when I try (on the > > > > > > client) to list my quota, the command just hangs. I've run snoop on the > > > > > > connection, and it appears that my server (sherlock) doesn't respond to > > > > > > the client's (cousteau) requests. > > > > > > > > > > > > I also verified that rpc.rquotad is running on my server. > > > > > > > > > > > > Any idea how I can get remote quota reporting working? > > > > > > > > > > > > > > > Similar configuration. My NFS-client machine is a Sun (Solaris 2.7). > > > > > On my linux XFS-NFS server, rpc.rquotad segfaults when I run > > > > > quota -v on the client (Sun). > > > > > > > > > I'm able to use "quota -v " on a SUN client with an XFS-NFS server > > > > without any problems. I do find, though, that if I mount an NFS exported > > > > file system on IRIX or SUN with the quota option and the file system is > > > > not mounted on the server with the usrquota option then rpc.rquotad segfaults. > > > > This happens with both xfs and ext2 file systems. Could it be a similar > > > > problem? > > > > > > > > > I'm not using the quota option when I mount on SUN. > > > But I use usrquota on XFS-linux server. > > > > > > > I just tried that and that seems to kill rpc.rquotad for me too. > > > > Could you build & install a debug (-g) version of rpc.rquotad, > attach to it with gdb while its running, then repeat the above > and send the stack trace & any other interesting info gdb will > give? I don't have access to any Sun machines, but I know that > these combinations of client<->server work, and are tested: > Linux<->Linux > IRIX<->Linux > Linux<->IRIX > > I assume this same problem will happen with ext2 quota (could > someone confirm that?) - Jan, have you seen this issue before? Actually I had some reports about rpc.rquotad SEGFAULTing. The bug should be fixed in -pre8 utils I released yesterday so please try those. If it doesn't help, tell me. Honza From owner-linux-xfs@oss.sgi.com Wed Jul 18 17:29:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J0TZS20322 for linux-xfs-outgoing; Wed, 18 Jul 2001 17:29:35 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J0TYV20303 for ; Wed, 18 Jul 2001 17:29:34 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id RAA00869 for ; Wed, 18 Jul 2001 17:27:06 -0700 (PDT) mail_from (ivanr@melbourne.sgi.com) Received: from omen.melbourne.sgi.com (omen.melbourne.sgi.com [134.14.55.139]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA15958; Thu, 19 Jul 2001 10:28:15 +1000 From: ivanr@melbourne.sgi.com (Ivan Rayner) Received: from localhost (ivanr@localhost) by omen.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id KAA06885; Thu, 19 Jul 2001 10:28:15 +1000 (EST) X-Authentication-Warning: omen.melbourne.sgi.com: ivanr owned process doing -bs Date: Thu, 19 Jul 2001 10:28:14 +1000 To: "Gonyou, Austin" cc: Linux XFS Mailing List Subject: RE: dumping multiple sessions to a single tape with XFS dump. In-Reply-To: <85063BBE668FD411944400D0B744267A643458@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001, Gonyou, Austin wrote: > If I perform the following: > > xfsdump -f /dev/nst0 -L "Boot FS" -m "test1" /boot > xfsdump -f /dev/nst0 -L "Home FS" -m "test1" /home I assume you used -M and not -m. Also, you don't need to use the non-rewind device here - xfsdump will take care of dumping /home after /boot on the tape. > mt /dev/st0 rewind > then > xfsrestore -f /dev/st0 -t > I only get data from /boot listed..and thats all that xfsrestore says it has > found. It would've examined the first dump. If you want it to examine the second dump, you will need to run xfsrestore again. Note also, that since you are using the rewinding tape device here, your second xfsrestore will also examine the first dump. However, xfsrestore should give you the option to skip that dump, and examine the next. Ivan -- Ivan Rayner ivanr@melbourne.sgi.com From owner-linux-xfs@oss.sgi.com Wed Jul 18 17:57:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J0vJJ21449 for linux-xfs-outgoing; Wed, 18 Jul 2001 17:57:19 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J0vHV21430 for ; Wed, 18 Jul 2001 17:57:17 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id RAA04674 for ; Wed, 18 Jul 2001 17:57:06 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA36816; Thu, 19 Jul 2001 10:55:58 +1000 (EST) Date: Thu, 19 Jul 2001 10:55:57 +1000 From: Timothy Shimmin To: austin@coremetrics.com Cc: linux-xfs@oss.sgi.com Subject: Re: dumping multiple sessions to a single tape with XFS dump. Message-ID: <20010719105557.W11622@boing.melbourne.sgi.com> References: <85063BBE668FD411944400D0B744267A643458@AUSMAIL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: ; from ivanr@melbourne.sgi.com on Thu, Jul 19, 2001 at 10:28:14AM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Just a couple of extra comments. On Thu, Jul 19, 2001 at 10:28:14AM +1000, Ivan Rayner wrote: > On Wed, 18 Jul 2001, Gonyou, Austin wrote: > > > If I perform the following: > > > > xfsdump -f /dev/nst0 -L "Boot FS" -m "test1" /boot > > xfsdump -f /dev/nst0 -L "Home FS" -m "test1" /home > > I assume you used -M and not -m. Also, you don't need to use the > non-rewind device here - xfsdump will take care of dumping /home after > /boot on the tape. If it finds an existing dump it will search for the stream terminator file (which marks the end of the dump) to start dumping a new session to. No rewinds or forward spacing is needed if all the tape has is xfs dumps. > > > mt /dev/st0 rewind > > then > > xfsrestore -f /dev/st0 -t > > I only get data from /boot listed..and thats all that xfsrestore says it has > > found. > > It would've examined the first dump. If you want it to examine the second > dump, you will need to run xfsrestore again. > > Note also, that since you are using the rewinding tape device here, your > second xfsrestore will also examine the first dump. However, xfsrestore > should give you the option to skip that dump, and examine the next. > Or you could have specified the session label for the one you wanted: xfsrestore -f /dev/st0 -t -L "Home FS" --Tim From owner-linux-xfs@oss.sgi.com Wed Jul 18 18:17:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J1HF121959 for linux-xfs-outgoing; Wed, 18 Jul 2001 18:17:15 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J1HCV21939 for ; Wed, 18 Jul 2001 18:17:13 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id SAA07360 for ; Wed, 18 Jul 2001 18:17:01 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA50591 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 11:15:54 +1000 (EST) Date: Thu, 19 Jul 2001 11:15:54 +1000 (EST) From: Nathan Scott Message-Id: <200107190115.LAA50591@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - dmapi/xfsdump packages Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The last of the libtool packaging changes, hopefully - passes QA for me. Re-establishes the link between dmapi and xfsdump packages (xfsdump now requires dmapi to be installed, at both build- and run-time). Merged a couple of xfsdump and fsr bug fixes over from IRIX too, and fixed that qa breakage Marcello reported. cheers. Date: Wed Jul 18 16:08:33 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99139a cmd/xfstests/configure.in - 1.9 - fix up use of libacl and libattr after recent package changes. Date: Wed Jul 18 18:00:14 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99161a cmd/xfsdump/restore/tree.c - 1.5 cmd/xfsdump/dump/hsmapi.c - 1.2 cmd/xfsdump/dump/getopt.h - 1.2 - port hidden dmapi code over to Linux (trivial). cmd/xfsdump/dump/inomap.c - 1.4 - merge fix for pv 781558 (phase 3 performance), change mallocs back to memaligns as in IRIX. cmd/xfsdump/common/archdep.h - 1.2 cmd/xfsdump/common/archdep.c - 1.2 cmd/xfsdump/common/Makefile - 1.4 - remove a couple of unused files (archdep.c|h). cmd/xfsdump/restore/content.c - 1.10 - insert a missing dmapi ioctl; port to Linux. cmd/xfsdump/copy/Makefile - 1.3 cmd/xfsdump/copy/locks.h - 1.2 cmd/xfsdump/copy/xfs_copy.c - 1.2 - fix compiler warnings - code was becoming moldy. still needs porting. cmd/xfsdump/fsr/xfs_fsr.c - 1.6 - merge a recent bug fix from IRIX. cmd/xfsdump/dump/Makefile - 1.4 cmd/xfsdump/restore/Makefile - 1.4 cmd/xfsdump/Makefile - 1.4 cmd/xfsdump/librmt/Makefile - 1.4 cmd/xfsdump/invutil/Makefile - 1.3 cmd/xfsdump/fsr/Makefile - 1.3 cmd/xfsdump/estimate/Makefile - 1.3 cmd/xfsdump/Makepkgs - 1.3 cmd/xfsdump/VERSION - 1.13 cmd/xfsdump/build/rpm/xfsdump.spec.in - 1.5 cmd/xfsdump/configure.in - 1.8 cmd/xfsdump/debian/Makefile - 1.2 cmd/xfsdump/debian/changelog - 1.7 cmd/xfsdump/debian/control - 1.6 cmd/xfsdump/debian/rules - 1.5 cmd/xfsdump/doc/CHANGES - 1.14 cmd/xfsdump/doc/Makefile - 1.3 cmd/xfsdump/doc/PORTING - 1.2 cmd/xfsdump/install-sh - 1.2 cmd/xfsdump/include/builddefs.in - 1.3 cmd/xfsdump/include/buildrules - 1.2 cmd/xfsdump/quota/Makefile - 1.2 - change the way we interact with libtool and do .deb packaging for consistency between all packages. cmd/xfsdump/doc/README.xfsdump - 1.4 - update to reflect current status. cmd/dmapi/libdm/Makefile - 1.4 cmd/dmapi/build/rpm/dmapi.spec.in - 1.5 cmd/dmapi/install-sh - 1.3 cmd/dmapi/include/buildrules - 1.3 cmd/dmapi/include/builddefs.in - 1.4 cmd/dmapi/doc/PORTING - 1.2 cmd/dmapi/doc/Makefile - 1.3 cmd/dmapi/Makefile - 1.3 cmd/dmapi/Makepkgs - 1.4 cmd/dmapi/VERSION - 1.5 cmd/dmapi/debian/changelog - 1.2 cmd/dmapi/doc/CHANGES - 1.4 cmd/dmapi/configure.in - 1.8 cmd/dmapi/debian/Makefile - 1.2 cmd/dmapi/debian/rules - 1.4 cmd/dmapi/debian/control - 1.3 cmd/dmapi/ltmain.sh - 1.2 cmd/dmapi/ltconfig - 1.2 cmd/dmapi/aclocal.m4 - 1.2 cmd/dmapi/config.sub - 1.2 cmd/dmapi/config.guess - 1.2 - change the way we interact with libtool and do .deb packaging for consistency between all packages. From owner-linux-xfs@oss.sgi.com Wed Jul 18 18:21:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J1L3I22132 for linux-xfs-outgoing; Wed, 18 Jul 2001 18:21:03 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J1L1V22112 for ; Wed, 18 Jul 2001 18:21:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id SAA02388 for ; Wed, 18 Jul 2001 18:18:33 -0700 (PDT) mail_from (kaos@melbourne.sgi.com) 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 LAA00984; Thu, 19 Jul 2001 11:19:35 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Andrew Klaassen cc: linux-xfs@oss.sgi.com Subject: Re: Kernel Debugger In-reply-to: Your message of "Wed, 18 Jul 2001 19:16:35 -0400." <20010718191635.A1810@key.dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Jul 2001 11:19:35 +1000 Message-ID: <24208.995505575@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001 19:16:35 -0400, Andrew Klaassen wrote: >I noticed that "Ctrl-A" at the console seems to dump me into the >kernel debugger. Only on serial consoles. >Is there any way to turn this behaviour off? The program that I >use to monitor the kernel on our fileservers via the serial port >uses "Ctrl-A" as a command character, and I'm afraid that I'm >going to accidentally type it twice in a row sometime, sending a >"Ctrl-A" character down the wire... echo "0" > /proc/sys/kernel/kdb, but that has the disadvantage that you cannot invoke kdb when the machine is hung. The best option is to edit drivers/char/serial.c and set kdb_serial_str to something different, some people like static char kdb_serial_str[] = "\eKdB"; (escape KdB) which is not something you type by mistake. From owner-linux-xfs@oss.sgi.com Wed Jul 18 18:38:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J1cIO22608 for linux-xfs-outgoing; Wed, 18 Jul 2001 18:38:18 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J1cGV22589 for ; Wed, 18 Jul 2001 18:38:16 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id DAA483031 for ; Thu, 19 Jul 2001 03:38:01 +0200 (CEST) mail_from (kaos@melbourne.sgi.com) 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 LAA01178; Thu, 19 Jul 2001 11:36:48 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: Ragnar Kj rstad cc: Eric Sandeen , linux-xfs@oss.sgi.com Subject: Re: kernel deadlock; xfs In-reply-to: Your message of "Wed, 18 Jul 2001 20:47:32 +0200." <20010718204732.A26849@vestdata.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Jul 2001 11:36:48 +1000 Message-ID: <24331.995506608@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 18 Jul 2001 20:47:32 +0200, Ragnar Kj rstad wrote: >On Wed, Jul 18, 2001 at 01:38:31PM -0500, Eric Sandeen wrote: >> $ echo 1 > /proc/sys/kernel/kdb >We did. >My comment was unclear - kdb work except when the lockup occurs. Probable cause: disabled spin loop. When that occurs, all interrupt handling is is dead, including the keyboard. You have to use a non maskable interrupt (NMI) source to break into disabled spin loops. If your box has an NMI button, use that button. Alas NMI buttons are very rare, mainly hobby boxes using a hacked PCI card. Without an external NMI source, use the software kernel NMI watchdog. Compile your kernel for one of these combinations: CONFIG_SMP=y CONFIG_SMP=n && CONFIG_X86_IO_APIC=y && CONFIG_UP_NMI_WATCHDOG=y All those options are on the processer menu. Boot the new kernel, cat /proc/interrupts must show the NMI counter increasing. When the machine hangs the NMI watchdog should kick in after 5 seconds. You still need echo 1 > /proc/sys/kernel/kdb, for both hardware and software NMI. Booting with kdb=on is even better. When the NMI is raised, it will drop into kdb. From owner-linux-xfs@oss.sgi.com Wed Jul 18 18:48:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J1mHN22986 for linux-xfs-outgoing; Wed, 18 Jul 2001 18:48:17 -0700 Received: from vortex.Inder.Net (cpe.atm0-0-0-126126.arcnxx2.customer.tele.dk [62.242.4.35]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J1mFV22967 for ; Wed, 18 Jul 2001 18:48:15 -0700 Received: from xfs.lists.logout.sh (7of9.labs.inder.net [192.168.2.7]) (authenticated (0 bits)) by vortex.Inder.Net (8.11.0/8.11.0) with ESMTP id f6J1mCf05930 for ; Thu, 19 Jul 2001 03:48:12 +0200 Message-ID: <3B563C52.A3101025@xfs.lists.logout.sh> Date: Thu, 19 Jul 2001 03:48:07 +0200 From: Mads Peter Bach X-Mailer: Mozilla 4.77 (Macintosh; U; PPC) X-Accept-Language: da,en,sv,no,de MIME-Version: 1.0 To: linux-xfs Subject: Re: Samba 2.2.1 RPMS with ACL References: <3B52A14E.6D0D4FA5@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii; x-mac-type="54455854"; x-mac-creator="4D4F5353" Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > Hello, > > I was just wondering whether someone has built Samba 2.2.1 RPMs with ACL > suitable for RH-7.1 XFS. If yes, it would be nice to have them somewhere > in a contrib area on the XFS ftp server. Well, I've built a RPM from the official Samba 2.2.1a tarball. It works for me on a RH-7.0 system, but YMMV. You can find it at http://www.hum.auc.dk/~mpb/samba-2.2.1a-20010711.i386.rpm If somebody would stick it on the SGI server, that would be fine. /Mads -- "I can hardly imagining a week-long black mass including welding equipment and diamond-cutters." "No, but if they tried, they'd probably get signed to release a CD of Industrial music. Or prosecuted for violating health & safety regulations." - Andreas Buzh Skau and Tanuki in Scary Devil Monastary From owner-linux-xfs@oss.sgi.com Wed Jul 18 19:41:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J2fFS24485 for linux-xfs-outgoing; Wed, 18 Jul 2001 19:41:15 -0700 Received: from mail.websolut.net (gw-websolut.itnet.pt [212.54.140.241] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J2fDV24463 for ; Wed, 18 Jul 2001 19:41:13 -0700 Received: (from daniel@localhost) by mail.websolut.net (8.11.0/8.11.0) id f6J2fAi22653; Thu, 19 Jul 2001 03:41:10 +0100 Message-ID: X-Mailer: XFMail 1.4.7 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B55CAAA.F13DE913@orion.mc.duke.edu> Date: Thu, 19 Jul 2001 03:41:10 +0100 (WEST) From: daniel@websolut.net To: Lucy Upchurch Subject: RE: XFS on Linux Cc: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18-Jul-2001 Lucy Upchurch wrote: > Hi, > > I am trying to install XFS filesystem on a linux box which was running > Linux 7.4.2. I downloaded the ISO image from > http://oss.sgi.com/projects/xfs/1.0_installer.html and made a bootable > CD. I selected a custom system. Before installation, my system loooked > like this: > > /dev/hda6 1517920 814808 626004 57% / > /dev/hda1 23302 8667 13432 40% > /boot > /dev/hda10 65275692 10576328 51383552 18% /home > /dev/sda1 73885280 20 70132076 1% > /home2 > /dev/hda7 1011928 624652 335872 66% /tmp > /dev/hda5 4032092 2221300 1605968 59% /usr > /dev/hda8 1011928 123832 836692 13% /var > > I tried numerous times to create an XFS filesystem on /home to no > avail. I then tried installing XFS on all partitions. The main error I > rec'd on various partitions is: > > Error mounting device hda1 as /boot: No such device > This most likely means this partition has not been formatted. > Press OK to reboot your system. > > Sometimes this error would be on /boot or on /. I got this error once and it had nothing to do with the partition not being formatted (although it tricked me for a little while). I would put it more in the fact (SCSI disk here) that the scsi module didn't load or the boot disk (network installation here) being damaged or just wrong - are you sure you're not booting from a non xfs disk? Because what happened to me was I tried using the network bootdisk from xfs 1.0 iso cd with a xfs 1.0.1 base install in nfs (didn't think it would make a difference, but it did). Don't let that generic message fool you. Go into the shell (Alt-F2) and see if you have the device indeed (my guess is you won't) - that should be your real problem. Hope to help, Daniel Fonseca -- ---------------------------------- E-Mail: daniel@websolut.net Date: 19-Jul-2001 Time: 03:33:08 This message was sent by XFMail ---------------------------------- From owner-linux-xfs@oss.sgi.com Wed Jul 18 21:02:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J42xV27813 for linux-xfs-outgoing; Wed, 18 Jul 2001 21:02:59 -0700 Received: from dcmtechdom.dcmtech.co.in ([216.6.80.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J42VV27780 for ; Wed, 18 Jul 2001 21:02:52 -0700 Received: by dcmtechdom.dcmtech.co.in with Internet Mail Service (5.5.2653.19) id ; Thu, 19 Jul 2001 09:30:55 +0530 Message-ID: <7FADCB99FC82D41199F9000629A85D1A01C6506A@dcmtechdom.dcmtech.co.in> From: Nitin Dhingra To: "'Florin Andrei'" , linux-xfs@oss.sgi.com, seawolf-list@redhat.com, dledford@redhat.com, linux-kernel@vger.kernel.org Subject: RE: noapic strikes back Date: Thu, 19 Jul 2001 09:30:54 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I guess the problem is mostly of the scsi driver. Get the latest version scsi driver of that particular card and then try again. Regards, Nitin -----Original Message----- From: Florin Andrei [mailto:florin@sgi.com] Sent: Thursday, July 19, 2001 1:05 AM To: linux-xfs@oss.sgi.com; seawolf-list@redhat.com; dledford@redhat.com; linux-kernel@vger.kernel.org Subject: noapic strikes back I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to install at least one version of Red Hat 7.1 on it. The problem is, while booting up the installer, when it comes to loading up the SCSI driver (AIC7xxx) the system is frozen. I tried the following boot disks: - stock Red Hat 7.1 - Doug Ledford's updates from people.redhat.com - SGI XFS 1.0.1 I tried to boot the installer with and without "noapic" option. I tried to enable and disable the APIC option in BIOS ("PCI IRQs to IO-APIC Mapping"). I tried all the combinations of these. No luck. :-( Please, is there anything to do about this problem? I *have* to install something newer than RH7.0 on that system. Guys, i will try whatever boot disks you will send to me. I'm willing to be you guinea pig. :-) Just let's kill the APIC problem for good! -- Florin Andrei - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ From owner-linux-xfs@oss.sgi.com Wed Jul 18 22:29:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J5TXF30924 for linux-xfs-outgoing; Wed, 18 Jul 2001 22:29:33 -0700 Received: from lacrosse.corp.redhat.com (host154.207-175-42.redhat.com [207.175.42.154]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J5TOV30903 for ; Wed, 18 Jul 2001 22:29:24 -0700 Received: from redhat.com (dledford.cipe.redhat.com [10.0.0.84]) by lacrosse.corp.redhat.com (8.9.3/8.9.3) with ESMTP id BAA24603; Thu, 19 Jul 2001 01:29:04 -0400 Message-ID: <3B56706C.893FD2AE@redhat.com> Date: Thu, 19 Jul 2001 01:30:20 -0400 From: Doug Ledford X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nitin Dhingra CC: "'Florin Andrei'" , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: noapic strikes back References: <7FADCB99FC82D41199F9000629A85D1A01C6506A@dcmtechdom.dcmtech.co.in> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nitin Dhingra wrote: > > I guess the problem is mostly of the scsi driver. > Get the latest version scsi driver of that particular > card and then try again. No, this has been gone over a thousand times already. It's the interrupt routing table in these particular Intel motherboard is busted. > -----Original Message----- > From: Florin Andrei [mailto:florin@sgi.com] > Sent: Thursday, July 19, 2001 1:05 AM > To: linux-xfs@oss.sgi.com; seawolf-list@redhat.com; dledford@redhat.com; > linux-kernel@vger.kernel.org > Subject: noapic strikes back > > I have a SGI 1200 (L440GX+ motherboard, dual PIII) and i'm trying to > install at least one version of Red Hat 7.1 on it. > The problem is, while booting up the installer, when it comes to loading > up the SCSI driver (AIC7xxx) the system is frozen. > > I tried the following boot disks: > - stock Red Hat 7.1 > - Doug Ledford's updates from people.redhat.com > - SGI XFS 1.0.1 > > I tried to boot the installer with and without "noapic" option. > > I tried to enable and disable the APIC option in BIOS ("PCI IRQs to > IO-APIC Mapping"). > > I tried all the combinations of these. No luck. :-( > > Please, is there anything to do about this problem? I *have* to install > something newer than RH7.0 on that system. > > Guys, i will try whatever boot disks you will send to me. I'm willing to > be you guinea pig. :-) Just let's kill the APIC problem for good! > > -- > Florin Andrei > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Doug Ledford http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems From owner-linux-xfs@oss.sgi.com Wed Jul 18 22:35:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J5Zjc31322 for linux-xfs-outgoing; Wed, 18 Jul 2001 22:35:45 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J5ZgV31303 for ; Wed, 18 Jul 2001 22:35:43 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id WAA00402 for ; Wed, 18 Jul 2001 22:33:15 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id PAA17263; Thu, 19 Jul 2001 15:35:39 +1000 Date: Thu, 19 Jul 2001 15:35:39 +1000 From: Keith Owens Message-Id: <200107190535.PAA17263@sherman.melbourne.sgi.com> Subject: TAKE - Merge to Linus 2.4.7-pre8 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk 2.4.7-pre7 breaks XFS qa when compiled with gcc 2.91.66. 2.4.7-pre8 has the workaround. Date: Wed Jul 18 22:33:10 PDT 2001 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:99169a linux/mm/swap_state.c - 1.27 linux/include/linux/fs.h - 1.102 linux/include/asm-ppc/softirq.h - 1.13 linux/include/asm-ppc/hardirq.h - 1.14 linux/include/asm-i386/processor.h - 1.24 linux/fs/buffer.c - 1.73 linux/drivers/isdn/hisax/sedlbauer.c - 1.15 linux/drivers/isdn/hisax/elsa.c - 1.13 linux/drivers/isdn/hisax/asuscom.c - 1.11 linux/drivers/char/lp.c - 1.21 linux/arch/ppc/kernel/prep_setup.c - 1.20 linux/arch/ppc/kernel/chrp_setup.c - 1.23 linux/arch/ppc/kernel/Makefile - 1.23 linux/arch/ppc/defconfig - 1.31 linux/arch/ppc/config.in - 1.38 linux/arch/ppc/boot/Makefile - 1.15 linux/arch/ppc/Makefile - 1.19 linux/Makefile - 1.103 linux/Documentation/sound/OPL3-SA2 - 1.7 linux/arch/ppc/kernel/m8xx_setup.c - 1.14 linux/arch/ppc/configs/walnut_defconfig - 1.11 linux/arch/ppc/configs/oak_defconfig - 1.11 linux/arch/ppc/configs/mbx_defconfig - 1.6 linux/arch/ppc/configs/gemini_defconfig - 1.13 linux/arch/ppc/configs/common_defconfig - 1.19 linux/arch/ppc/configs/apus_defconfig - 1.7 linux/drivers/isdn/hisax/hfc_sx.c - 1.7 linux/drivers/video/riva/fbdev.c - 1.11 linux/include/asm-ppc/immap_8260.h - 1.5 linux/arch/ppc/kernel/m8260_setup.c - 1.9 linux/arch/ppc/configs/rpxlite_defconfig - 1.6 linux/arch/ppc/configs/rpxcllf_defconfig - 1.7 linux/arch/ppc/configs/est8260_defconfig - 1.7 linux/arch/ppc/configs/bseip_defconfig - 1.6 linux/drivers/isdn/hisax/nj_u.c - 1.6 linux/drivers/isdn/hisax/nj_s.c - 1.6 linux/fs/reiserfs/stree.c - 1.5 linux/fs/reiserfs/namei.c - 1.5 linux/fs/reiserfs/journal.c - 1.5 linux/fs/reiserfs/inode.c - 1.7 linux/fs/reiserfs/fix_node.c - 1.6 linux/fs/reiserfs/do_balan.c - 1.2 linux/fs/reiserfs/dir.c - 1.4 linux/include/linux/reiserfs_fs.h - 1.5 linux/include/linux/reiserfs_fs_i.h - 1.3 linux/include/linux/reiserfs_fs_sb.h - 1.3 linux/arch/ppc/configs/power3_defconfig - 1.4 linux/arch/ppc/configs/ibmchrp_defconfig - 1.4 linux/arch/ppc/configs/TQM860L_defconfig - 1.4 linux/arch/ppc/configs/TQM850L_defconfig - 1.4 linux/arch/ppc/configs/TQM823L_defconfig - 1.4 linux/arch/ppc/configs/SPD823TS_defconfig - 1.4 linux/arch/ppc/configs/SM850_defconfig - 1.4 linux/arch/ppc/configs/IVMS8_defconfig - 1.4 linux/arch/ppc/boot/utils/Makefile - 1.2 linux/arch/ppc/boot/mbx/misc.c - 1.2 linux/arch/ppc/boot/common/misc-common.c - 1.4 linux/drivers/isdn/tpam/tpam_main.c - 1.2 From owner-linux-xfs@oss.sgi.com Wed Jul 18 22:53:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J5r5f31899 for linux-xfs-outgoing; Wed, 18 Jul 2001 22:53:05 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J5r2V31879 for ; Wed, 18 Jul 2001 22:53:02 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id HAA07795; Thu, 19 Jul 2001 07:52:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id HAA04785; Thu, 19 Jul 2001 07:52:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id A354E57306; Thu, 19 Jul 2001 08:02:23 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id C6EBA25836; Thu, 19 Jul 2001 08:10:15 +0200 (CEST) Message-ID: <3B5675A9.3C517A0D@ch.sauter-bc.com> Date: Thu, 19 Jul 2001 07:52:41 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: =?iso-8859-1?Q?KR=DCCKEL?= OLIVER Cc: "'linux-xfs@oss.sgi.com'" Subject: Re: AW: xfs kernel problem References: <4FF9029AF0C8D311B99D0050DA1CB9F4FB78F0@exchange.visa-austria.com> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by relay.xlink.net id HAA07795 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6J5r3V31881 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk KRÜCKEL OLIVER schrieb: > > On 17 Jul 2001 18:57:38 +0200, Krückel Oliver wrote: > > >> Linux SuSE-7.1 with servarel patches from the officel SuSE web-server > >> gcc: version 2.95.2 19991024 (release) > May I suggest you install RedHat 7.1-XFS on one machine just to make sure your hardware is okay? This could make your life much easier. > >Can you try compiling with a 2.91.66 gcc version? This is the first > >thing I'd try, newer compilers still have not been producing > >consistently good code. > > ok > > I get the egcs-1.1.2 (gcc 2.91.66) but I can't compile it. > I test it also with the gcc 3.0, but with the sam results with the gcc > 2.91.66 > > >> if i reboot the server with the xfs kernel and the server coms up there > are > >> sum files and executables witch i can't access ore execute, > >> > >> sum examples: the programms find, make, ... or file hosts, ... > >> > >> if i reboot the server again, there are much more files that can't access > or > >> execute, there are alwais other executebles and files by every test, > > >Can you give any more information about "can't access" - do they not > >show up in the directory listing, do they seem to contain wrong data... > >? > > I get at the startup process sum lines like the follow > > Initializing SMTP port. (sendmail)451 4.0.0 /etc/sendmail.cf: line 0: cannot > open: Permission denied > startproc: exit status of /usr/sbin/sendmail: 72 > failed > the file sendmail.cf hase the size 0 byte > > at sume other cases i can't access or list a file (i'm root) and I get the > massage permisson denied. > > >-Eric > > I test my config also on an other hp lp2000r server and I have the same > problems. From owner-linux-xfs@oss.sgi.com Wed Jul 18 23:28:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J6S6r00440 for linux-xfs-outgoing; Wed, 18 Jul 2001 23:28:06 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J6S2V00416 for ; Wed, 18 Jul 2001 23:28:02 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA16679; Thu, 19 Jul 2001 08:27:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA07205; Thu, 19 Jul 2001 08:27:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id C621657306; Thu, 19 Jul 2001 08:37:28 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 3DB7C25835; Thu, 19 Jul 2001 08:45:21 +0200 (CEST) Message-ID: <3B567DE2.90F09F41@ch.sauter-bc.com> Date: Thu, 19 Jul 2001 08:27:46 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Tru Huynh Cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tru Huynh schrieb: > > Hello, > > I would like to add to the xfs performance with sw raid discussion. > I encounter the same kind of degraded performance with the > following hardware/software combination. > Although the degradation can be feel with the local access too, > but there are no errors messages :( > > hardware config > > The nfs client is a plain redhat 7.1 > hardware: K7-1.2GHz 2x256PC133 Abit KT7A motherboard > with 2 3com 3c905C NICs (one to an isolated HP procurve > switch and the other to a Cisco for the main campus network) > > The server is a dual P3-866MHz with 4x256PC133 > (rocky 3732 mb - chipset Via VT82C694X/VT82C686B) > with 1 ide-scsi controller 3ware 3w6800 with 8 IBM-DTLA-307075 72G HDs Could you try RAID5/XFS with the onboard IDE controller and SMP Kernel? This way we could find out whether it's the 3ware / SMP / RAID5 combination that makes the problem. I'm running several servers here with RAID5 on IDE and SCSI with good results but all of them are single CPU systems. > 20G system boot disk redhat 7.1+SGI xfs 1.0.1 > 3com 3c905C NICs to an isolated HP procurve switch > 3com 3c905C NICs to a Cisco for the main campus network 3c905C NIC? I was having performance problems with them while the 3c905B were doing very fine. > > I tried with both kernel smp 2.4.3-2 from xfs-1.0.1 and 2.4.5 with xfs > > /dev/hda6 is a scratch partition on the system disk (ext2/xfs) > /dev/mdo is the software raid device (450GB with xfs) > > when copying large directory fron the client to the server > on the raid5 partition the following error is recorded in > the syslog file (on either network HP/Cisco): > Jul 18 20:19:44 jason.bis.pasteur.fr kernel: nfs: server nfs.cluster not > responding, still trying > Jul 18 20:20:08 jason.bis.pasteur.fr last message repeated 2 times > Jul 18 20:20:08 jason.bis.pasteur.fr kernel: nfs: server nfs.cluster OK > > 1) When doing the very same copy to the nfs exported scratch partition > either ext2 or xfs the copy is really fast and no error message are > found. > > 2) Doing the same experiments with the UP kernel 2.4.5-xfs /2.4.3-xfs > give no errors (xfs on sw raid5 and (xfs,ext2) on scracth partition) > > 3) with or without noapic does not help either... > > conclusions: > ============ > > smp+swraid5+xfs : not ok > up+swraid5+xfs : ok > > I will try the cvs version tomorrow > > Thank you for listening. > > Tru > > details: > -------- > /etc/raidtab file: > ----------------- > # Sample raid-5 configuration > # > raiddev /dev/md0 > raid-level 5 > nr-raid-disks 7 > # Spare disks for hot reconstruction > nr-spare-disks 1 > persistent-superblock 1 > > chunk-size 64 > > # the best one for maximum performance: > # > parity-algorithm left-symmetric > > #parity-algorithm right-asymmetric > #parity-algorithm right-symmetric > > > device /dev/sdb1 > raid-disk 0 > device /dev/sdc1 > raid-disk 1 > device /dev/sdd1 > raid-disk 2 > device /dev/sde1 > raid-disk 3 > device /dev/sdf1 > raid-disk 4 > device /dev/sdg1 > raid-disk 5 > device /dev/sdh1 > raid-disk 6 > # > device /dev/sda1 > spare-disk 0 > > UP-2.4.5-xfs (rpm --rebuild --target=i686 > kernel-2.4.5-SGI_XFS_1.0.1.src.rpm) > [tru@sheridan ~]$ uname -a > Linux sheridan.bis.pasteur.fr 2.4.5-SGI_XFS_1.0.1 #1 Wed Jul 18 15:03:15 > CEST 2001 i686 unknown > [tru@sheridan ~]$ cat /proc/cmdline > auto BOOT_IMAGE=1-245xfs-101 ro root=301 > BOOT_FILE=/boot/vmlinuz-2.4.5-SGI_XFS_1.0.1 ramdisk_size=2500 > devfs=nomount > > SMP-2.4.5-xfs (rpm --rebuild --target=i686 > kernel-2.4.5-SGI_XFS_1.0.1.src.rpm) > [tru@sheridan ~]$ uname -a > Linux sheridan.bis.pasteur.fr 2.4.5-SGI_XFS_1.0.1smp #1 SMP Wed Jul 18 > 14:50:17 > [tru@sheridan tru]$ cat /proc/cmdline > auto BOOT_IMAGE=1-xfs-101smp ro root=301 > BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp ramdisk_size=2500 > devfs=nomount > > UP-2.4.3-2 from the 1.0.2 iso > [tru@sheridan ~]$ uname -a > Linux sheridan.bis.pasteur.fr 2.4.3-SGI_XFS_1.0.1 #1 Mon Jul 9 14:27:56 > CDT 2001 i686 unknown > [tru@sheridan ~]$ cat /proc/cmdline > auto BOOT_IMAGE=1-xfs-101 ro root=301 > BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1 ramdisk_size=2500 > devfs=nomount > [tru@sheridan ~]$ cat /proc/version > Linux version 2.4.3-SGI_XFS_1.0.1 (root@linux-xfs2.americas.sgi.com) > (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon > Jul 9 14:27:56 CDT 2001 > > SMP-2.4.3-2 from the 1.0.2 iso > [tru@sheridan ~]$ uname -a > Linux sheridan.bis.pasteur.fr 2.4.3-SGI_XFS_1.0.1smp #1 SMP Mon Jul 9 > 14:03:40 CDT 2001 i686 unknown > [tru@sheridan ~]$ cat /proc/cmdline > auto BOOT_IMAGE=1-xfs-101smp ro root=301 > BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1smp ramdisk_size=2500 > devfs=nomount > -- > Dr Tru Huynh | Bioinformatique Structurale > mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 > Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Wed Jul 18 23:34:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J6YFk00737 for linux-xfs-outgoing; Wed, 18 Jul 2001 23:34:15 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J6YEV00712 for ; Wed, 18 Jul 2001 23:34:14 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id XAA02400 for ; Wed, 18 Jul 2001 23:31:46 -0700 (PDT) mail_from (ajag@snort.melbourne.sgi.com) Received: (from ajag@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA89457 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 16:32:55 +1000 (EST) Date: Thu, 19 Jul 2001 16:32:55 +1000 (EST) From: Andrew Gildfind Message-Id: <200107190632.QAA89457@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump/xfsrestore man pages Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Synch with IRIX.. Date: Wed Jul 18 23:31:45 PDT 2001 Workarea: snort.melbourne.sgi.com:/home/ajag/isms/slinx The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99172a cmd/xfsdump/man/man8/xfsdump.8 - 1.5 cmd/xfsdump/man/man8/xfsrestore.8 - 1.3 - reconcile with IRIX (clean up synopsis, add examples, explain verbosity, etc.) From owner-linux-xfs@oss.sgi.com Wed Jul 18 23:57:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J6vBC01789 for linux-xfs-outgoing; Wed, 18 Jul 2001 23:57:11 -0700 Received: from isis.its.uow.edu.au (isis.its.uow.edu.au [130.130.68.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J6v8V01767 for ; Wed, 18 Jul 2001 23:57:09 -0700 Received: from uow.edu.au (wumpus.its.uow.edu.au [130.130.68.12]) by isis.its.uow.edu.au (8.9.3/8.9.3) with ESMTP id QAA25479; Thu, 19 Jul 2001 16:56:45 +1000 (EST) Message-ID: <3B5684FC.C2C9875D@uow.edu.au> Date: Thu, 19 Jul 2001 16:58:04 +1000 From: Andrew Morton X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.7-pre6 i686) X-Accept-Language: en MIME-Version: 1.0 To: Simon Matter CC: Tru Huynh , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> <3B567DE2.90F09F41@ch.sauter-bc.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Simon Matter wrote: > > ... > Could you try RAID5/XFS with the onboard IDE controller and SMP Kernel? > This way we could find out whether it's the 3ware / SMP / RAID5 > combination that makes the problem. I'm running several servers here > with RAID5 on IDE and SCSI with good results but all of them are > single CPU systems. Some fairly significant RAID5 and RAID1 bugs were fixed in 2.4.7-pre5 or thereabouts. One of them could cause largish IO stalls. > > 3c905C NIC? I was having performance problems with them while the > 3c905B were doing very fine. 905C should be in good shape nowadays. There were some problems with the 3c905CX, but they were farily obvious - it didn't receive anything. Dr Huynh should run a few network tests - look at the output of `ifconfig' for errors, ping the server from another host while the NFS load is applied, etc. But I would mainly be suspecting the RAID5 timing problems. This is the magical chunk: Index: drivers/md/raid5.c =================================================================== RCS file: /opt/cvs/lk/drivers/md/raid5.c,v retrieving revision 1.17 retrieving revision 1.18 diff -u -u -r1.17 -r1.18 --- drivers/md/raid5.c 2001/06/21 17:50:29 1.17 +++ drivers/md/raid5.c 2001/07/10 12:34:44 1.18 @@ -66,10 +66,11 @@ BUG(); if (atomic_read(&conf->active_stripes)==0) BUG(); - if (test_bit(STRIPE_DELAYED, &sh->state)) - list_add_tail(&sh->lru, &conf->delayed_list); - else if (test_bit(STRIPE_HANDLE, &sh->state)) { - list_add_tail(&sh->lru, &conf->handle_list); + if (test_bit(STRIPE_HANDLE, &sh->state)) { + if (test_bit(STRIPE_DELAYED, &sh->state)) + list_add_tail(&sh->lru, &conf->delayed_list); + else + list_add_tail(&sh->lru, &conf->handle_list); md_wakeup_thread(conf->thread); } else { if (test_and_clear_bit(STRIPE_PREREAD_ACTIVE, &sh->state)) { @@ -1167,10 +1168,9 @@ raid5_activate_delayed(conf); - if (conf->plugged) { - conf->plugged = 0; - md_wakeup_thread(conf->thread); - } + conf->plugged = 0; + md_wakeup_thread(conf->thread); + spin_unlock_irqrestore(&conf->device_lock, flags); } From owner-linux-xfs@oss.sgi.com Thu Jul 19 00:08:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J78cu02382 for linux-xfs-outgoing; Thu, 19 Jul 2001 00:08:38 -0700 Received: from mgw-x2.nokia.com (mgw-x2.nokia.com [131.228.20.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J78UV02358 for ; Thu, 19 Jul 2001 00:08:30 -0700 Received: from esvir02nok.nokia.com (esvir02nokt.ntc.nokia.com [172.21.143.34]) by mgw-x2.nokia.com (Switch-2.1.0/Switch-2.1.0) with ESMTP id f6J78n316406 for ; Thu, 19 Jul 2001 10:08:49 +0300 (EET DST) Received: from esebh25nok.ntc.nokia.com (unverified) by esvir02nok.nokia.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Thu, 19 Jul 2001 10:08:28 +0300 Received: by esebh25nok with Internet Mail Service (5.5.2652.78) id <3MSVBVD0>; Thu, 19 Jul 2001 10:08:28 +0300 Message-ID: <62D73DD5B95CE14084EC17103E347B70060054@esebe014.NOE.Nokia.com> From: Imad.Ossaily@nokia.com To: lord@sgi.com Cc: knuffie@xs4all.nl, Ext-Kamaljeet.Singh@nokia.com, linux-xfs@oss.sgi.com Subject: RE: Xfs prblems with clearcase mvfs Date: Thu, 19 Jul 2001 10:08:21 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2652.78) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk You are right, the Structure_check function is from mvfs code itself. In the makefile for building mvfs you have to indicate the location of the kernel sources you are using. I have changed the makefile to the right kernel sources, and that should mean that I'm using the right kernel headers. Am I right? What about super_operations and file_operations? Imad. > -----Original Message----- > From: ext Steve Lord [mailto:lord@sgi.com] > Sent: Wednesday, July 18, 2001 6:16 PM > To: Ossaily Imad (NET/Helsinki) > Cc: lord@sgi.com; knuffie@xs4all.nl; Singh Kamaljeet > (EXT-TataCS/Helsinki); linux-xfs@oss.sgi.com > Subject: Re: Xfs prblems with clearcase mvfs > > > > we have recomiled the mvfs module against the running > kernel version with > > XFS support, so this is not the source of the problem. > > The error messages that I'm getting while trying to load > the module are: > > > > [root@t1-dhcp2-027231 mvfs]# insmod mvfs > > Using /lib/modules/fs/mvfs.o > > Structure_check error for struct super_operations. MVFS > expected 56, got 64 > > Structure_check error for struct inode_operations. MVFS > expected 64, got 76 > > Structure_check error for struct file_operations. MVFS > expected 68, got 64 > > Structure_check error for struct super_block. MVFS > expected 500, got 464 > > Structure_check error for struct inode. MVFS expected 472, got 456 > > Structure_check error for struct dentry. MVFS expected 116, got 112 > > ERROR: MVFS detected 6 structure size mismatches > > /lib/modules/fs/mvfs.o: init_module: Invalid argument > > Hint: insmod errors can be caused by incorrect module > parameters, including > > invalid IO or IRQ parameters > > These error messages are coming out of the mvfs module > itself, not the > insmod utility. If this is part of the code which gets > recompiled by mvfs > then it suggests that the wrong set of header files were > used, especially > since we do not make any changes to the size of the inode, super_block > or dentry. Can you double check that your mvfs build was looking at > header files which match the kernel. > > Steve > > > > > > regards, > > Imad. > > > > > -----Original Message----- > > > From: ext Steve Lord [mailto:lord@sgi.com] > > > Sent: Wednesday, July 18, 2001 5:53 PM > > > To: Ossaily Imad (NET/Helsinki) > > > Cc: knuffie@xs4all.nl; Singh Kamaljeet (EXT-TataCS/Helsinki); > > > linux-xfs@oss.sgi.com > > > Subject: Re: Xfs prblems with clearcase mvfs > > > > > > > > > > we can't upgrade to XFS-1.0.1 because it's supported for > > > kernel 2.4.5 and > > > > ClearCase 4.1 on linux is supported only for kernel 2.4.2, > > > so we have to use > > > > this version of the kernel. > > > > > > And this is exactly your problem, if clearcase is built > against the > > > original kernel shipped by redhat then it will almost > certainly not > > > work with the xfs kernel. Running a binary kernel module against a > > > different kernel than it was built for is almost > certainly not going > > > to work in this case the only people who can help you with > > > this is clearcase. > > > > > > What I would like to see to confirm this is the exact error > > > messages you > > > are getting. > > > > > > Thanks > > > > > > Steve > > > > > > > > > > > > > > regards, > > > > Imad. > > > > > > > > > -----Original Message----- > > > > > From: ext Seth Mos [mailto:knuffie@xs4all.nl] > > > > > Sent: Wednesday, July 18, 2001 5:35 PM > > > > > To: Singh Kamaljeet (EXT-TataCS/Helsinki); > linux-xfs@oss.sgi.com > > > > > Cc: Ossaily Imad (NET/Helsinki) > > > > > Subject: Re: Xfs prblems with clearcase mvfs > > > > > > > > > > > > > > > At 17:29 18-7-2001 +0300, Ext-Kamaljeet.Singh@nokia.com wrote: > > > > > >Hi, > > > > > >We are facing problems with xfs version 1.0 (with kernel > > > > > 2.4.2-2 on Redhat > > > > > >7.1) with Clearcase version 4.1 for linux. when we try to > > > > > load mvfs module, > > > > > >it gives structure check errors for following structures: > > > > > >Super-operations > > > > > >inode-operations > > > > > >File-operations > > > > > >Super-block > > > > > >inode > > > > > >dentry > > > > > > > > > > > >Could you please look into it and suggest us some good > > > > > solution. We can > > > > > >provide more details if required. > > > > > > > > > > Can you upgrade to the 1.0.1 release? That one has many > > > > > fixes, tlhough I am > > > > > not quite sure if it fixes this. > > > > > > > > > > Bye > > > > > > > > > > -- > > > > > Seth > > > > > Every program has two purposes one for which > > > > > it was written and another for which it wasn't > > > > > I use the last kind. > > > > > > > > > > > > > From owner-linux-xfs@oss.sgi.com Thu Jul 19 00:16:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J7GlG02920 for linux-xfs-outgoing; Thu, 19 Jul 2001 00:16:47 -0700 Received: from marilyn1.kirchgruppe.de (marilyn.kirchgruppe.de [193.101.184.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J7GhV02901 for ; Thu, 19 Jul 2001 00:16:43 -0700 Received: by marilyn1.kirchgruppe.de (8.9.3/8.9.3) id JAA18945; Thu, 19 Jul 2001 09:16:41 +0200 (CEST) Received: (from localhost) by marilyn1.kirchgruppe.de (MSCAN) id 3/marilyn1.kirchgruppe.de/smtp-gw/mscan; Thu Jul 19 09:16:41 2001 Message-ID: <3B568903.7376AC2B@betaresearch.de> Date: Thu, 19 Jul 2001 09:15:15 +0200 From: Wolfgang Henselmann-Weiss X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Daniel Moore CC: linux-xfs@oss.sgi.com Subject: Re: XFS problems References: <200107182244.IAA21596@snort.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Daniel, thanks for your reply. See my comments below bye -WHW- Daniel Moore wrote: > Eric Sandeen writes: > > => Can you send the mkfs.xfs output that did appear? > => > => > mount -t xfs /dev/hde7 /mnt > => > #fails with > => > > mount: wrong fs type, bad option , bad superblock on /dev/hde7, > => > > or too many mounted filesystems > => > => Hm, wish this error was less Windows-like*. :) > => > > This is annoying message indeed, but XFS usually logs messages to to > the console/syslog on mount errors (these should be more informative). > syslog output is ... |Jul 19 09:08:48 wolfi kernel: XFS: SB sanity check 2 failed |Jul 19 09:08:48 wolfi kernel: XFS: SB validate failed > > I haven't been following this thread, but have you checked that XFS is > enabled in the kernel/loaded? sure. (all xfs stuff loaded as modules) xfs works fine on other partitions :) prob: IMHO is combination with hde7 connected to a promise ide controller ... > > > ----------------------------------------------------- > Daniel Moore dxm@sgi.com > R&D Software Engineer Phone: +61-3-98348209 > SGI Performance Tools Group Fax: +61-3-98132378 > ----------------------------------------------------- From owner-linux-xfs@oss.sgi.com Thu Jul 19 00:19:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J7JVU03141 for linux-xfs-outgoing; Thu, 19 Jul 2001 00:19:31 -0700 Received: from marilyn1.kirchgruppe.de (marilyn.kirchgruppe.de [193.101.184.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J7JSV03118 for ; Thu, 19 Jul 2001 00:19:28 -0700 Received: (from root@localhost) by marilyn1.kirchgruppe.de (8.9.3/8.9.3) id JAA19354; Thu, 19 Jul 2001 09:19:26 +0200 (CEST) Received: (from localhost) by marilyn1.kirchgruppe.de (MSCAN) id 3/marilyn1.kirchgruppe.de/smtp-gw/mscan; Thu Jul 19 09:19:25 2001 Message-ID: <3B5689B3.B22C674C@betaresearch.de> Date: Thu, 19 Jul 2001 09:18:11 +0200 From: Wolfgang Henselmann-Weiss X-Mailer: Mozilla 4.72 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: linux-xfs@oss.sgi.com Subject: Re: XFS problems References: <3B55AD2F.C5F0154B@betaresearch.de> <995473548.8982.209.camel@stout.americas.sgi.com> Content-Type: multipart/alternative; boundary="------------B7599F0D1A822BC262F8A5BB" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --------------B7599F0D1A822BC262F8A5BB Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Eric Sandeen wrote: > On 18 Jul 2001 17:37:19 +0200, Wolfgang Henselmann-Weiss wrote: > > > mkfs.xfs -f /dev/hde7 > > # no error message ... > > Can you send the mkfs.xfs output that did appear? voila ... |wolfi:/etc # mkfs.xfs -f /dev/hde7 |meta-data=/dev/hde7 isize=256 agcount=16, agsize=262144 blks |data = bsize=4096 blocks=3932200, imaxpct=25 | = sunit=0 swidth=0 blks, unwritten=0 |naming =version 2 bsize=4096 |log =internal log bsize=4096 blocks=1200 |realtime =none extsz=65536 blocks=0, rtextents=0 |wolfi:/etc/ # no syslog error message after mkfs! hope it will help ... -Wolfgang > > > > mount -t xfs /dev/hde7 /mnt > > #fails with > > > mount: wrong fs type, bad option , bad superblock on /dev/hde7, > > > or too many mounted filesystems > > Hm, wish this error was less Windows-like*. :) > > -Eric > > * --------------B7599F0D1A822BC262F8A5BB Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

    Eric Sandeen wrote:

    On 18 Jul 2001 17:37:19 +0200, Wolfgang Henselmann-Weiss wrote:

    > mkfs.xfs -f  /dev/hde7
    > # no error message ...

    Can you send the mkfs.xfs output that did appear?

    voila ...
    |wolfi:/etc # mkfs.xfs -f /dev/hde7
    |meta-data=/dev/hde7              isize=256    agcount=16, agsize=262144 blks
    |data     =                       bsize=4096   blocks=3932200, imaxpct=25
    |         =                       sunit=0      swidth=0 blks, unwritten=0
    |naming   =version 2              bsize=4096
    |log      =internal log           bsize=4096   blocks=1200
    |realtime =none                   extsz=65536  blocks=0, rtextents=0
    |wolfi:/etc/ #

    no syslog error message after mkfs!
    hope it will help ...

    -Wolfgang

     

    > mount -t xfs /dev/hde7 /mnt
    > #fails with
    > > mount: wrong fs type, bad option , bad superblock on /dev/hde7,
    > > or too many mounted filesystems

    Hm, wish this error was less Windows-like*.  :)

    -Eric

    *

    --------------B7599F0D1A822BC262F8A5BB-- From owner-linux-xfs@oss.sgi.com Thu Jul 19 00:23:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J7NmJ03438 for linux-xfs-outgoing; Thu, 19 Jul 2001 00:23:48 -0700 Received: from mail.coltex.nl (IDENT:root@edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J7NjV03416 for ; Thu, 19 Jul 2001 00:23:45 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6J7Nfe04499; Thu, 19 Jul 2001 09:23:41 +0200 Message-Id: <4.3.2.7.2.20010719092018.031d1638@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 19 Jul 2001 09:23:29 +0200 To: Simon Matter , =?iso-8859-1?Q?KR=DCCKEL?= OLIVER From: Seth Mos Subject: Re: AW: xfs kernel problem Cc: "'linux-xfs@oss.sgi.com'" In-Reply-To: <3B5675A9.3C517A0D@ch.sauter-bc.com> References: <4FF9029AF0C8D311B99D0050DA1CB9F4FB78F0@exchange.visa-austria.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6J7NkV03417 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 07:52 19-7-2001 +0200, Simon Matter wrote: >KRÜCKEL OLIVER schrieb: > > > > On 17 Jul 2001 18:57:38 +0200, Krückel Oliver wrote: > > > > >> Linux SuSE-7.1 with servarel patches from the officel SuSE web-server > > >> gcc: version 2.95.2 19991024 (release) > > > >May I suggest you install RedHat 7.1-XFS on one machine just to make >sure >your hardware is okay? This could make your life much easier. If the machine is currently not used yet. Which I asume not because of the massive corruption. What kernel version are you currently using? Have you tried out checking out the CVS tree and see if that one compiles better (don't rembember if you already did that). You might also want to check the Ami website for firmware updates. Something is going horribly wrong but I don't have the slightest idea what. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 19 01:55:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J8tnn07197 for linux-xfs-outgoing; Thu, 19 Jul 2001 01:55:49 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J8tiV07175 for ; Thu, 19 Jul 2001 01:55:45 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6J8te0232802; Thu, 19 Jul 2001 10:55:40 +0200 (CEST) Message-ID: <3B56A07D.FDA92943@pasteur.fr> Date: Thu, 19 Jul 2001 10:55:25 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Thanks you for all your sugestions. If I try to summarise the issues raised: 1) 3ware driver 3w-xxxx is not(?) SMP aware? - current firmware - current 3w-xxxx drivers: 2.4.3-xfs-1.0.1 2.4.5-xfs-1.0.1 I guess the SMP kernel come with SMP aware driver :) 2) 3com cards not working properly (3c59x driver) packet losts, bonnie on nfs (too many interrupts?) - not errors reported on either cards and switch (no collisions, dropped. overruns/carriers on - ok for bonnie, will post the results ASAP. Do I need to run all 4 combinations UP/SMP 2.4.3/2.4.5? 3) testing kernel >= 2.4.7pre5 - will do after getting today's cvs update 4) try SMP+raid5 on local IDE HD to rule out 3ware issue - I just have a single HD on the primary IDE controller I can only repartion it by destroying the scratch partition. Will 3 logical partitions be ok for a minimal raid5 device? 5) change the chunk-size from 64 to 256/512. - I guess that is fine tuning :) I found the file server down this morning with a kernel panic and the following error on the console: Kernel panic scsi_free: Trying to free unused memory in Interrupt handler - not syncing I left the server rsincing 4 other clients. All rsincs finished properly. The kernel panic must have happen after while the server was mostly iddle! Kernel was 2.4.5-xfs-1.0.1 UP since SMP was not usable. Best regards, Tru Huynh -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 02:21:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J9Lrk08473 for linux-xfs-outgoing; Thu, 19 Jul 2001 02:21:53 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J9LpV08450 for ; Thu, 19 Jul 2001 02:21:51 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6J9LLe05255; Thu, 19 Jul 2001 11:21:32 +0200 Message-Id: <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 19 Jul 2001 11:21:08 +0200 To: Tru Huynh , "linux-xfs@oss.sgi.com" From: Seth Mos Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: <3B56A07D.FDA92943@pasteur.fr> References: <3B55E49E.5B4B6CEF@pasteur.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 10:55 19-7-2001 +0200, Tru Huynh wrote: >1) 3ware driver 3w-xxxx is not(?) SMP aware? >- current firmware >- current 3w-xxxx drivers: > 2.4.3-xfs-1.0.1 > 2.4.5-xfs-1.0.1 > I guess the SMP kernel come with SMP aware driver :) Maybe the people over at linux-ide.org have a newer 3ware driver. >2) 3com cards not working properly (3c59x driver) > packet losts, bonnie on nfs (too many interrupts?) > >- not errors reported on either cards and switch >(no collisions, dropped. overruns/carriers on That's good. >- ok for bonnie, will post the results ASAP. > Do I need to run all 4 combinations UP/SMP 2.4.3/2.4.5? Mainly the SMP ones. and one UP. Performance between UP kernels will probably be similar. >3) testing kernel >= 2.4.7pre5 >- will do after getting today's cvs update It's 2.4.7-pre8 at the moment. >4) try SMP+raid5 on local IDE HD to rule out 3ware issue >- I just have a single HD on the primary IDE controller > I can only repartion it by destroying the scratch partition. > Will 3 logical partitions be ok for a minimal raid5 device? Yes that will do >5) change the chunk-size from 64 to 256/512. >- I guess that is fine tuning :) Should be faster with large files. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 19 02:26:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J9QJQ08704 for linux-xfs-outgoing; Thu, 19 Jul 2001 02:26:19 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J9QHV08682 for ; Thu, 19 Jul 2001 02:26:17 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id LAA08511; Thu, 19 Jul 2001 11:25:56 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id LAA21838; Thu, 19 Jul 2001 11:25:54 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id DC19D57306; Thu, 19 Jul 2001 11:35:33 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 3C99525835; Thu, 19 Jul 2001 11:43:26 +0200 (CEST) Message-ID: <3B56A79F.EA8658D2@ch.sauter-bc.com> Date: Thu, 19 Jul 2001 11:25:51 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Seth Mos Cc: Tru Huynh , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos schrieb: > > At 10:55 19-7-2001 +0200, Tru Huynh wrote: > >1) 3ware driver 3w-xxxx is not(?) SMP aware? > >- current firmware > >- current 3w-xxxx drivers: > > 2.4.3-xfs-1.0.1 > > 2.4.5-xfs-1.0.1 > > I guess the SMP kernel come with SMP aware driver :) > > Maybe the people over at linux-ide.org have a newer 3ware driver. > > >2) 3com cards not working properly (3c59x driver) > > packet losts, bonnie on nfs (too many interrupts?) > > > >- not errors reported on either cards and switch > >(no collisions, dropped. overruns/carriers on > > That's good. > > >- ok for bonnie, will post the results ASAP. > > Do I need to run all 4 combinations UP/SMP 2.4.3/2.4.5? > > Mainly the SMP ones. and one UP. Performance between UP kernels will > probably be similar. > > >3) testing kernel >= 2.4.7pre5 > >- will do after getting today's cvs update > > It's 2.4.7-pre8 at the moment. > > >4) try SMP+raid5 on local IDE HD to rule out 3ware issue > >- I just have a single HD on the primary IDE controller > > I can only repartion it by destroying the scratch partition. > > Will 3 logical partitions be ok for a minimal raid5 device? > > Yes that will do But performance will be bad anyway with all partitions on the same physikal disk. > > >5) change the chunk-size from 64 to 256/512. > >- I guess that is fine tuning :) I was playing around with chunk-size but it didn't really change something for me. > > Should be faster with large files. > > Cheers > > -- > Seth > Every program has two purposes one for which > it was written and another for which it wasn't > I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 19 02:32:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J9WxZ09105 for linux-xfs-outgoing; Thu, 19 Jul 2001 02:32:59 -0700 Received: from serveur.creaweb.fr (mail.creaweb.fr [194.98.233.61]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J9WuV09085 for ; Thu, 19 Jul 2001 02:32:56 -0700 Received: from poste2.creaweb ([192.168.0.18]) by serveur.creaweb.fr (post.office MTA v2.0 0813 ID# 104-13810) with SMTP id AIR198 for ; Thu, 19 Jul 2001 11:33:25 +0100 From: info@internetsociete.com (Internet Societe : info) To: linux-xfs@oss.sgi.com Date: Thu, 19 Jul 2001 11:37:57 PDT Subject: Nouveau service gratuit MIME-Version: 1.0 Content-Type: text/html; charset=us-ascii Message-ID: <20010719102214741.AIR198@poste2.creaweb> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Untitled Document
    + de 500 sites sélectionnés
    gratuits et utiles

    Découvrez notre sélection de sites utiles à votre activité du Batiment

    CLIQUEZ ICI

    Recevez par e.mail des promotions de fournisseurs liées à votre activité

    CLIQUEZ ICI

     


    Votre communiqué
    d'entreprise gratuit
    sur Internet Societe

    Vous lancez:
    - Un nouveau service
    - Un nouveau produit
    - Une promotion

    ou

    - Vous avez un savoir faire spécifique
    - Vous obtenez de nouvelles références

    FAITE LE SAVOIR

    CLIQUEZ ICI

    ___________________________________
    Si vous ne désirez plus recevoir de courriers de cette liste :
    To remove your email address from this list :
    desabonnement@internetsociete.com From owner-linux-xfs@oss.sgi.com Thu Jul 19 02:46:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J9kBY09753 for linux-xfs-outgoing; Thu, 19 Jul 2001 02:46:11 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J9k9V09734 for ; Thu, 19 Jul 2001 02:46:09 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6J9jce05359; Thu, 19 Jul 2001 11:45:38 +0200 Message-Id: <4.3.2.7.2.20010719114143.03cfed10@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 19 Jul 2001 11:45:26 +0200 To: Simon Matter From: Seth Mos Subject: Re: nfs/local performance with software raid5 and xfs and SMP Cc: Tru Huynh , "linux-xfs@oss.sgi.com" In-Reply-To: <3B56A79F.EA8658D2@ch.sauter-bc.com> References: <3B55E49E.5B4B6CEF@pasteur.fr> <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:25 19-7-2001 +0200, Simon Matter wrote: >Seth Mos schrieb: > > >4) try SMP+raid5 on local IDE HD to rule out 3ware issue > > >- I just have a single HD on the primary IDE controller > > > I can only repartion it by destroying the scratch partition. > > > Will 3 logical partitions be ok for a minimal raid5 device? > > > > Yes that will do > >But performance will be bad anyway with all partitions on the >same physikal disk. That does _not_ matter. It is neccesary to see if the problem lies with the 3ware controller or not. This is not a matter of performance. Read the thread before giving hints. > > >5) change the chunk-size from 64 to 256/512. > > >- I guess that is fine tuning :) > >I was playing around with chunk-size but it didn't really change >something for me. It does if you have large files. The disks can read bigger chunks at once and improve throughput at the cost of latency. But with a 450GB you will probably want enough speed so you can actually fill it within 2 days. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 19 02:52:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6J9qKk10037 for linux-xfs-outgoing; Thu, 19 Jul 2001 02:52:20 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6J9qFV10015 for ; Thu, 19 Jul 2001 02:52:16 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6J9pT0301044; Thu, 19 Jul 2001 11:51:29 +0200 (CEST) Message-ID: <3B56AD91.FA721B93@pasteur.fr> Date: Thu, 19 Jul 2001 11:51:13 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos CC: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > > At 10:55 19-7-2001 +0200, Tru Huynh wrote: > >1) 3ware driver 3w-xxxx is not(?) SMP aware? > >- current firmware Monitor version: ME6X 1.01.00.024 Firmware version: FE6X 1.02.00.029 BIOS version: BEXX 1.07.00.009 PCB version: Rev2 Achip version: V4.40 Pchip version: V5.70 > >- current 3w-xxxx drivers: oops I forgot to fill the blanks: > > 2.4.3-xfs-1.0.1 1.02.00.007 the same as in the current cvs tree. > > 2.4.5-xfs-1.0.1 1.02.00.004 > Maybe the people over at linux-ide.org have a newer 3ware driver. The driver on the 3ware web page is 1.02.00.006 :( But the firmware is: Release 6.8 Version 1.02.03.053 I will flash it at the next reboot. > Mainly the SMP ones. I guess I will stick to 2.4.3-SGI-xfs-1.0.1 and the cvs because the driver for the 3ware cards are newer. > > It's 2.4.7-pre8 at the moment. I am building the SMP-kernel now > >4) try SMP+raid5 on local IDE HD to rule out 3ware issue I will cut the scratch partition in 3 even if the performance can not be really good. I will post ASAP Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 04:13:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JBDcP13877 for linux-xfs-outgoing; Thu, 19 Jul 2001 04:13:38 -0700 Received: from otto.cfht.hawaii.edu (otto.colonization.com [128.171.80.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JBDaV13856 for ; Thu, 19 Jul 2001 04:13:36 -0700 Received: (from isani@localhost) by otto.cfht.hawaii.edu (8.8.8/8.8.8) id BAA07232; Thu, 19 Jul 2001 01:13:22 -1000 From: Sidik Isani Message-Id: <200107191113.BAA07232@otto.cfht.hawaii.edu> Subject: Re: 2.4.3-SGI_XFS_1.0.1smp leaks? To: lord@sgi.com (Steve Lord) Date: Thu, 19 Jul 2001 01:13:22 -1000 (HST) Cc: gbritton@mit.edu (Gerald Britton), linux-xfs@oss.sgi.com In-Reply-To: <200107181938.f6IJc6D18922@jen.americas.sgi.com> from "Steve Lord" at Jul 18, 2001 02:38:06 PM X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello Gerald - The "used" memory reported by /proc/meminfo is apparently not a meaningful measurement of non-freeable memory when there are large values in /proc/slabinfo. There are some XFS and page_buf entries in there which can get quite high. However they go right back down if something else really needs the memory. So I don't think there's a leak. I'd sure like to understand what's really going on a bit better, but the only thing which seems broken is our ability to easily get an idea of how much free-able memory is left :-( Be seeing you, - Sidik | |> I ran the 1.0 redhatish kernel for months with no major problems other than |> a few data corruption bugs on dirty recovery. I was hoping that upgrading to |> 1.0.1 would fix those issues, but now I seem to be running out of memory in |> the space of about 2 days. The "used" ammount of memory seems to be higher |> than the sum of all processes, so it seems like something is leaking userspac |> e |> memory. Anyone else having these problems? Any fix available? |> |> -- Gerald | |Hmm, maybe there is an interaction with changes from redhat, is the machine |actually behaving worse? The oss website has been up and running on a 1.0.1 |XFS kernel for nearly 31 days now and that machine is pretty busy. However, |the kernel happens to be from just before the release and is still 2.4.2 |based. | |Can you post some more info on what it is you are seeing. | |Thanks | | | Steve | | From owner-linux-xfs@oss.sgi.com Thu Jul 19 04:35:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JBZCe15407 for linux-xfs-outgoing; Thu, 19 Jul 2001 04:35:12 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JBZAV15365 for ; Thu, 19 Jul 2001 04:35:10 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id EAA03631 for ; Thu, 19 Jul 2001 04:32:43 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 VAA04424; Thu, 19 Jul 2001 21:33:51 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id VAA14858; Thu, 19 Jul 2001 21:33:49 +1000 (AEST) Date: Thu, 19 Jul 2001 21:33:48 +1000 From: Nathan Scott To: Wolfgang Henselmann-Weiss Cc: Daniel Moore , linux-xfs@oss.sgi.com Subject: Re: XFS problems Message-ID: <20010719213347.A196344@wobbly.melbourne.sgi.com> References: <200107182244.IAA21596@snort.melbourne.sgi.com> <3B568903.7376AC2B@betaresearch.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B568903.7376AC2B@betaresearch.de>; from Wolfgang_Henselmann@betaresearch.de on Thu, Jul 19, 2001 at 09:15:15AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 19, 2001 at 09:15:15AM +0200, Wolfgang Henselmann-Weiss wrote: > > syslog output is ... > |Jul 19 09:08:48 wolfi kernel: XFS: SB sanity check 2 failed > |Jul 19 09:08:48 wolfi kernel: XFS: SB validate failed > Hmmm ... that looks grim - the error comes from here, in the XFS kernel code (xfs_mount.c): if (sbp->sb_dblocks == 0 || sbp->sb_dblocks > (xfs_drfsbno_t)sbp->sb_agcount * sbp->sb_agblocks || sbp->sb_dblocks < (xfs_drfsbno_t)(sbp->sb_agcount - 1) * sbp->sb_agblocks + XFS_MIN_AG_BLOCKS) { cmn_err(CE_WARN, "XFS: SB sanity check 2 failed"); return XFS_ERROR(EFSCORRUPTED); } So, it seems mkfs might be coming up with bad data.. haven't ever seen that before. Could you run xfs_db on the device, and print the superblock & send us that? Something like: # xfs_db -c sb -c p /dev/foo and we should be able to narrow it down to one of those 3 condition. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 19 05:35:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JCZs301850 for linux-xfs-outgoing; Thu, 19 Jul 2001 05:35:54 -0700 Received: from nevermore.toe.doomcom.org (IDENT:mail@dsl092-078-112.bos1.dsl.speakeasy.net [66.92.78.112]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JCZpV01826 for ; Thu, 19 Jul 2001 05:35:51 -0700 Received: by nevermore.toe.doomcom.org (Postfix, from userid 3499) id 6FDC320BA0E; Thu, 19 Jul 2001 08:35:50 -0400 (EDT) Date: Thu, 19 Jul 2001 08:35:50 -0400 From: Gerald Britton To: Sidik Isani Cc: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: 2.4.3-SGI_XFS_1.0.1smp leaks? Message-ID: <20010719083550.A6962@nevermore.toe.doomcom.org> References: <200107181938.f6IJc6D18922@jen.americas.sgi.com> <200107191113.BAA07232@otto.cfht.hawaii.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107191113.BAA07232@otto.cfht.hawaii.edu>; from isani@cfht.hawaii.edu on Thu, Jul 19, 2001 at 01:13:22AM -1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk here is a little more info from my machine.. i suspect the behavior will be more pronounced either this evening or tomorrow morning as my machine will have been up longer. The machine has been mostly idle, no processes appear to be leaking, yet more and more ends up being pushed into swap space. After a day or two more, the "free" memory listed in /proc/meminfo will drop to around 4M and the "cached" memory drops down to around 40M or so. The majority of process memory ends up being moved into swap space and the machine starts to slowly grind. I'll see if i can leave this up another day or two and post some more numbers then. % uname -r Linux nevermore.toe.doomcom.org 2.4.3-SGI_XFS_1.0.1smp #1 SMP Mon Jul 9 14:03:40 CDT 2001 i686 unknown % uptime 8:34am up 1 day, 11:15, 3 users, load average: 0.04, 0.05, 0.01 % cat /proc/meminfo total: used: free: shared: buffers: cached: Mem: 392212480 348160000 44052480 897024 0 109670400 Swap: 266256384 24064000 242192384 MemTotal: 383020 kB MemFree: 43020 kB MemShared: 876 kB Buffers: 0 kB Cached: 107100 kB Active: 84196 kB Inact_dirty: 20888 kB Inact_clean: 2892 kB Inact_target: 6408 kB HighTotal: 0 kB HighFree: 0 kB LowTotal: 383020 kB LowFree: 43020 kB SwapTotal: 260016 kB SwapFree: 236516 kB % cat /proc/slabinfo slabinfo - version: 1.1 (SMP) kmem_cache 102 102 232 6 6 1 : 252 126 ip_conntrack 50 50 384 5 5 1 : 124 62 ip_fib_hash 22 226 32 2 2 1 : 252 126 clip_arp_cache 0 0 128 0 0 1 : 252 126 ip_mrt_cache 0 0 96 0 0 1 : 252 126 tcp_tw_bucket 0 0 128 0 0 1 : 252 126 tcp_bind_bucket 15 226 32 2 2 1 : 252 126 tcp_open_request 0 0 96 0 0 1 : 252 126 inet_peer_cache 1 59 64 1 1 1 : 252 126 ip_dst_cache 37 140 192 7 7 1 : 252 126 arp_cache 7 30 128 1 1 1 : 252 126 xfs_chashlist 3368 8282 16 41 41 1 : 252 126 xfs_ili 324 588 136 21 21 1 : 252 126 xfs_ifork 2 134 56 2 2 1 : 252 126 xfs_efi_item 15 15 260 1 1 1 : 124 62 xfs_efd_item 15 15 260 1 1 1 : 124 62 xfs_buf_item 70 78 148 3 3 1 : 252 126 xfs_dabuf 202 202 16 1 1 1 : 252 126 xfs_da_state 0 11 340 0 1 1 : 124 62 xfs_trans 21 48 320 3 4 1 : 124 62 xfs_inode 32958 37384 468 4673 4673 1 : 124 62 xfs_btree_cur 28 28 140 1 1 1 : 252 126 xfs_bmap_free_item 126 202 16 1 1 1 : 252 126 page_buf_t 139 320 192 16 16 1 : 252 126 page_buf_reg_t 3 80 96 2 2 1 : 252 126 avl_object_t 3 226 32 2 2 1 : 252 126 avl_entry_t 127 452 32 4 4 1 : 252 126 blkdev_requests 3840 3880 96 97 97 1 : 252 126 dnotify cache 0 0 20 0 0 1 : 252 126 file lock cache 126 126 92 3 3 1 : 252 126 fasync cache 1 202 16 1 1 1 : 252 126 uid_cache 10 226 32 2 2 1 : 252 126 skbuff_head_cache 177 480 160 20 20 1 : 252 126 sock 209 270 1280 90 90 1 : 60 30 inode_cache 33171 37160 480 4645 4645 1 : 124 62 bdev_cache 23 118 64 2 2 1 : 252 126 sigqueue 261 261 132 9 9 1 : 252 126 kiobuf 0 0 128 0 0 1 : 252 126 dentry_cache 16941 27840 128 928 928 1 : 252 126 dquot 0 0 128 0 0 1 : 252 126 filp 2068 2080 96 52 52 1 : 252 126 names_cache 2 2 4096 2 2 1 : 60 30 buffer_head 11400 11400 96 285 285 1 : 252 126 mm_struct 191 210 128 7 7 1 : 252 126 vm_area_struct 2649 8319 64 102 141 1 : 252 126 fs_cache 191 236 64 4 4 1 : 252 126 files_cache 126 126 416 14 14 1 : 124 62 signal_act 99 99 1312 33 33 1 : 60 30 size-131072(DMA) 0 0 131072 0 0 32 : 0 0 size-131072 0 0 131072 0 0 32 : 0 0 size-65536(DMA) 0 0 65536 0 0 16 : 0 0 size-65536 7 7 65536 7 7 16 : 0 0 size-32768(DMA) 0 0 32768 0 0 8 : 0 0 size-32768 5 5 32768 5 5 8 : 0 0 size-16384(DMA) 0 0 16384 0 0 4 : 0 0 size-16384 4 5 16384 4 5 4 : 0 0 size-8192(DMA) 0 0 8192 0 0 2 : 0 0 size-8192 9 9 8192 9 9 2 : 0 0 size-4096(DMA) 0 0 4096 0 0 1 : 60 30 size-4096 54 54 4096 54 54 1 : 60 30 size-2048(DMA) 1 2 2048 1 1 1 : 60 30 size-2048 68 68 2048 34 34 1 : 60 30 size-1024(DMA) 0 0 1024 0 0 1 : 124 62 size-1024 268 268 1024 67 67 1 : 124 62 size-512(DMA) 0 0 512 0 0 1 : 124 62 size-512 216 216 512 27 27 1 : 124 62 size-256(DMA) 0 0 256 0 0 1 : 252 126 size-256 424 495 256 33 33 1 : 252 126 size-128(DMA) 0 0 128 0 0 1 : 252 126 size-128 1342 2160 128 72 72 1 : 252 126 size-64(DMA) 0 0 64 0 0 1 : 252 126 size-64 6485 6490 64 110 110 1 : 252 126 size-32(DMA) 0 0 32 0 0 1 : 252 126 size-32 1534 6102 32 54 54 1 : 252 126 From owner-linux-xfs@oss.sgi.com Thu Jul 19 05:44:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JCi8g04224 for linux-xfs-outgoing; Thu, 19 Jul 2001 05:44:08 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JCi6V04196 for ; Thu, 19 Jul 2001 05:44:06 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6JCi4e06165 for ; Thu, 19 Jul 2001 14:44:04 +0200 Message-Id: <4.3.2.7.2.20010719144015.032a79b0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 19 Jul 2001 14:43:36 +0200 To: linux-xfs list From: Seth Mos Subject: Searchable mail archive Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk For people that want a searchable archive you can find it here :-) http://marc.theaimsgroup.com/?l=linux-xfs&r=1&w=2 I will also add this link to the FAQ. Maybe it should also be linked somewhere on the mailinglist page. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 19 05:51:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JCp0S06203 for linux-xfs-outgoing; Thu, 19 Jul 2001 05:51:00 -0700 Received: from gusi.leathercollection.ph ([202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JCopV06147 for ; Thu, 19 Jul 2001 05:50:54 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 62308833 for ; Thu, 19 Jul 2001 20:50:24 +0800 (PHT) Date: Thu, 19 Jul 2001 20:50:24 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 19 Jul 2001 at 11:21, Seth Mos wrote: > Maybe the people over at linux-ide.org have a newer 3ware driver. The latest Linux drivers and firmware are maintained by the Linux team of 3ware. Maybe those interested can e-mail . I use a 3ware Escalade 6400 card doing RAID5 and it works well. Unfortunately (or fortunately) I do not have an SMP system so I haven't experienced any issues so far. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 19 05:54:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JCsTI07369 for linux-xfs-outgoing; Thu, 19 Jul 2001 05:54:29 -0700 Received: from matrix.seed.net.tw (matrix.seed.net.tw [192.72.81.219]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JCsJV07284 for ; Thu, 19 Jul 2001 05:54:25 -0700 Received: from [210.244.60.135] (helo=promise.com.tw) by mail.seed.net.tw with smtp (SEEDNet Mail Server v2.316f) id 15NDJP-000PK5-00 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 20:53:54 +0800 Received: from [192.168.204.47] by promise.com.tw (NTMail 3.02.13) with ESMTP id wa287790 for ; Thu, 19 Jul 2001 13:01:58 +0800 Message-ID: <019501c1100f$7b854550$2fcca8c0@gibson> From: "DaiGS" To: , Subject: RE:[Q] xfs_growfs erro Date: Thu, 19 Jul 2001 12:58:42 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0192_01C11052.8997BC70" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0192_01C11052.8997BC70 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable Hi. =20 I setup SGI XFS Release 1.0.1 & RedHat 7.1 & LVM 0.9.1Beta. =20 I want to grow & decrease LVM XFS partition. I make 1024M LVM partition, and run mkfs.xfs. I have 1024M xfs partition. After I use 'lvextend tool', grow my test lvm partion to 2048M. And I use xfs_growfs, grow block size 300000. XFS partition is 1195200Kbyte now. And I think more big partion, but my computer is below error. xfs_growfs -D 300001 /mnt/01 meta-data=3D/mnt/01 isize=3D256 agcount=3D10, = agsize=3D32768 blks data =3D bsize=3D4096 blocks=3D300000, = imaxpct=3D25 =3D sunit=3D0 swidth=3D0 blks, = unwritten=3D0 naming =3Dversion 2 bsize=3D4096 log =3Dinternal bsize=3D4096 blocks=3D1200 realtime =3Dnone extsz=3D65536 blocks=3D0, = rtextents=3D0 xfs_growfs: ioctl failed - XFS_IOC_FSGROWFSDATA: Unknown error 990 What means above error? What's problem? Please Reply. Thank you. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Hi..... The same to me ......I got the same problem like that "xfs_growfs: ioctl failed - XFS_IOC_FSGROWFSDATA: Unknown error = 990". In the following, I looked up many HOWTO about that.=20 And found some message in "XFS mailing list". The one is that after each xfs_growfs run xfs_repair. But on above situation, you can not successfully finish xfs_grow, which = the to me. At this time, I tried a way to successful growing, that is I run = xfs_repair before run xfs_growfs, and there=20 was a wonder result, I sloved the problem on run xfs_growfs. I can grow = my XFS arbitrarily now...... I did not stand to the normal setp to do it, but I did successfully, = WHY....????? ------=_NextPart_000_0192_01C11052.8997BC70 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable
    Hi.

    I setup SGI XFS Release 1.0.1 & = RedHat 7.1=20 & LVM 0.9.1Beta.

    I want to grow & decrease LVM XFS=20 partition.
    I make 1024M LVM partition, and run mkfs.xfs.
    I have = 1024M xfs=20 partition.
    After I  use 'lvextend tool', grow my test lvm = partion =20 to 2048M.
    And I use xfs_growfs, grow block size 300000.
    XFS = partition is=20 1195200Kbyte now.
    And I think more big partion, but my computer is = below=20 error.

    xfs_growfs -D 300001=20 /mnt/01
    meta-data=3D/mnt/01       &= nbsp;       =20 isize=3D256    agcount=3D10, agsize=3D32768=20 blks
    data    =20 =3D           &nbs= p;          =20 bsize=3D4096   blocks=3D300000,=20 imaxpct=3D25
             &nb= sp; =20 =3D           &nbs= p;          =20 sunit=3D0      swidth=3D0 blks,=20 unwritten=3D0
    naming   =3Dversion=20 2            =  =20 bsize=3D4096
    log     =20 =3Dinternal          &n= bsp;   =20 bsize=3D4096   blocks=3D1200
    realtime=20 =3Dnone           =        =20 extsz=3D65536  blocks=3D0, rtextents=3D0
    xfs_growfs: ioctl = failed -=20 XFS_IOC_FSGROWFSDATA: Unknown error 990

    What means above = error?
    What's=20 problem?

    Please Reply.
    Thank you.
    =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    =
     
    Hi.....
     
        The same to me ......I got the = same problem=20 like
     that "xfs_growfs: ioctl failed - = XFS_IOC_FSGROWFSDATA:=20 Unknown error 990".
     
    In the following, I looked up many HOWTO about that. =
    And found some message in "XFS mailing = list".
    The one is that after each xfs_growfs run=20 xfs_repair.
    But on above situation, you can not successfully = finish=20 xfs_grow, which the to me.
     At this time, I tried a way to successful = growing, that=20 is I run xfs_repair before run xfs_growfs, and there
    was a wonder result, I sloved the problem on run = xfs_growfs. I=20 can grow my XFS arbitrarily now......
     
    I did not stand to the normal setp to do it, but I = did=20 successfully, WHY....?????

     
     
    ------=_NextPart_000_0192_01C11052.8997BC70-- From owner-linux-xfs@oss.sgi.com Thu Jul 19 06:10:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JDAEG12393 for linux-xfs-outgoing; Thu, 19 Jul 2001 06:10:14 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JDA9V12353 for ; Thu, 19 Jul 2001 06:10:09 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id PAA09889; Thu, 19 Jul 2001 15:09:56 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id PAA10021; Thu, 19 Jul 2001 15:09:56 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id F119757306; Thu, 19 Jul 2001 15:19:18 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 6A8BC25835; Thu, 19 Jul 2001 15:27:10 +0200 (CEST) Message-ID: <3B56DC0F.FD406DC1@ch.sauter-bc.com> Date: Thu, 19 Jul 2001 15:09:35 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: DaiGS Cc: theadadv@linuxone.co.kr, linux-xfs@oss.sgi.com Subject: Re: [Q] xfs_growfs erro References: <019501c1100f$7b854550$2fcca8c0@gibson> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > DaiGS schrieb: > > Hi. > > I setup SGI XFS Release 1.0.1 & RedHat 7.1 & LVM 0.9.1Beta. > > I want to grow & decrease LVM XFS partition. > I make 1024M LVM partition, and run mkfs.xfs. > I have 1024M xfs partition. > After I use 'lvextend tool', grow my test lvm partion to 2048M. > And I use xfs_growfs, grow block size 300000. > XFS partition is 1195200Kbyte now. > And I think more big partion, but my computer is below error. > > xfs_growfs -D 300001 /mnt/01 > meta-data=/mnt/01 isize=256 agcount=10, agsize=32768 > blks > data = bsize=4096 blocks=300000, > imaxpct=25 > = sunit=0 swidth=0 blks, > unwritten=0 > naming =version 2 bsize=4096 > log =internal bsize=4096 blocks=1200 > realtime =none extsz=65536 blocks=0, rtextents=0 > xfs_growfs: ioctl failed - XFS_IOC_FSGROWFSDATA: Unknown error 990 > > What means above error? > What's problem? > > Please Reply. > Thank you. > =================================================================== > > Hi..... > > The same to me ......I got the same problem like > that "xfs_growfs: ioctl failed - XFS_IOC_FSGROWFSDATA: Unknown error > 990". > > In the following, I looked up many HOWTO about that. > And found some message in "XFS mailing list". > The one is that after each xfs_growfs run xfs_repair. > But on above situation, you can not successfully finish xfs_grow, > which the to me. > At this time, I tried a way to successful growing, that is I run > xfs_repair before run xfs_growfs, and there > was a wonder result, I sloved the problem on run xfs_growfs. I can > grow my XFS arbitrarily now...... > > I did not stand to the normal setp to do it, but I did successfully, > WHY....????? > Hi, I don't know what your problem is exactly but as stated in the FAQ at least someone was having problem with growing filsystems more than once. I did not get this problem even when growing 10 times but what I saw now is that you specified the amount to grow with the -D option and this could be the reason why it breaks. If the filesystem is okay and mountable now, could you try the following: - Reduce the Logical Volume to ~1500M - grow the fs with xfs_growfs /mnt/01 , fs should then be exactly the size of the volume. - Extend the volume to 1600M - grow the fs with xfs_growfs /mnt/01 - Extend the volume to 1700M - grow the fs with xfs_growfs /mnt/01 If this works it means that maybe the xfs_growfs -D option can be dangerous in certain situations. -Simon From owner-linux-xfs@oss.sgi.com Thu Jul 19 06:40:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JDeZ221328 for linux-xfs-outgoing; Thu, 19 Jul 2001 06:40:35 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JDeWV21298 for ; Thu, 19 Jul 2001 06:40:32 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6JDeV0335015; Thu, 19 Jul 2001 15:40:31 +0200 (CEST) Message-ID: <3B56E33E.B4465042@pasteur.fr> Date: Thu, 19 Jul 2001 15:40:14 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> <3B56AD91.FA721B93@pasteur.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, It looks like a kernel SMP issue more than a 3ware driver problem. - I have tried the following SMP kernels: 2.4.3-xfs-1.0.1 and 2.4.7pre8 cvs version which include the same 3ware 3w-xxxx driver. (I have not yet flash the firmware). - I can see it on a plain IDE raid5 partition. I will now flash the 3ware card firmware. but I don't know what that can change... Next step is rebooting with noapic. /dev/md1 is now a raid5-xfs on the system HD #------------------------------- # raid5 on hda #------------------------------- raiddev /dev/md1 raid-level 5 nr-raid-disks 3 persistent-superblock 1 chunk-size 64 parity-algorithm left-symmetric # device /dev/hda6 raid-disk 0 device /dev/hda7 raid-disk 1 device /dev/hda8 raid-disk 2 I can still see the nfs freeze (server nfs.cluster not responding) on both raid5 devices under 2.4.3-xfs. on the client side syslog reports a "nfs_statfs: statfs error = 116 ". I can still see it under 2.4.7pre8 on /dev/md0 or /dev/md1 but only after a little longer time... Off topic: One strange thing is the checksumming function: /var/log/messages kernel: raid5: measuring checksumming speed kernel: 8regs : 1169.200 MB/sec kernel: 32regs : 788.000 MB/sec kernel: pIII_sse : 1727.600 MB/sec kernel: pII_mmx : 1924.000 MB/sec kernel: p5_mmx : 2045.200 MB/sec kernel: raid5: using function: pIII_sse (1727.600 MB/sec) Why not using the faster p5_mmx ? > > >4) try SMP+raid5 on local IDE HD to rule out 3ware issue ruled out. :( Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 06:52:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JDqsf23672 for linux-xfs-outgoing; Thu, 19 Jul 2001 06:52:54 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JDqpV23650 for ; Thu, 19 Jul 2001 06:52:51 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id PAA23530; Thu, 19 Jul 2001 15:51:58 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id PAA13562; Thu, 19 Jul 2001 15:51:57 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id C223757306; Thu, 19 Jul 2001 16:02:00 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 151E425835; Thu, 19 Jul 2001 16:09:53 +0200 (CEST) Message-ID: <3B56E611.6939F07@ch.sauter-bc.com> Date: Thu, 19 Jul 2001 15:52:17 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Tru Huynh Cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <3B55E49E.5B4B6CEF@pasteur.fr> <4.3.2.7.2.20010719111805.03d75be0@pop.xs4all.nl> <3B56AD91.FA721B93@pasteur.fr> <3B56E33E.B4465042@pasteur.fr> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tru Huynh schrieb: > > Hello, > > It looks like a kernel SMP issue more than a 3ware driver > problem. > - I have tried the following SMP kernels: > 2.4.3-xfs-1.0.1 and 2.4.7pre8 cvs version which include > the same 3ware 3w-xxxx driver. (I have not yet flash the firmware). > - I can see it on a plain IDE raid5 partition. > > I will now flash the 3ware card firmware. but I don't > know what that can change... > > Next step is rebooting with noapic. > > /dev/md1 is now a raid5-xfs on the system HD > #------------------------------- > # raid5 on hda > #------------------------------- > raiddev /dev/md1 > raid-level 5 > nr-raid-disks 3 > persistent-superblock 1 > chunk-size 64 > parity-algorithm left-symmetric > # > device /dev/hda6 > raid-disk 0 > device /dev/hda7 > raid-disk 1 > device /dev/hda8 > raid-disk 2 > > I can still see the nfs freeze (server nfs.cluster not responding) > on both raid5 devices under 2.4.3-xfs. on the client side > syslog reports a "nfs_statfs: statfs error = 116 ". > > I can still see it under 2.4.7pre8 on /dev/md0 or /dev/md1 > but only after a little longer time... > > Off topic: One strange thing is the checksumming function: > /var/log/messages > kernel: raid5: measuring checksumming speed > kernel: 8regs : 1169.200 MB/sec > kernel: 32regs : 788.000 MB/sec > kernel: pIII_sse : 1727.600 MB/sec > kernel: pII_mmx : 1924.000 MB/sec > kernel: p5_mmx : 2045.200 MB/sec > kernel: raid5: using function: pIII_sse (1727.600 MB/sec) I'm not an expert but I think it has something to do with pIII_sse being cache friendly while the mmx functions are not. Maybe I'm wrong but I remember something like that. > > Why not using the faster p5_mmx ? > > > > >4) try SMP+raid5 on local IDE HD to rule out 3ware issue > ruled out. :( > > Tru > -- > Dr Tru Huynh | Bioinformatique Structurale > mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 > Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 19 06:52:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JDqkJ23624 for linux-xfs-outgoing; Thu, 19 Jul 2001 06:52:46 -0700 Received: from dmz.tecosim.de ([194.24.222.241]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JDqbV23589 for ; Thu, 19 Jul 2001 06:52:38 -0700 Received: (from uucp@localhost) by dmz.tecosim.de (8.11.0/8.11.0/SuSE Linux 8.11.0-0.4) id f6JDcLA31912 for ; Thu, 19 Jul 2001 15:38:21 +0200 Received: from ns.tecosim.de(194.24.222.9) via SMTP by dmz.tecosim.de, id smtpdImujZx; Thu Jul 19 15:38:12 2001 Received: from donner.tecosim.de (donner.tecosim.de [194.24.222.109]) by ns.tecosim.de (8.10.2/8.10.2/SuSE Linux 8.10.0-0.3) with ESMTP id f6JDpUi04644 for ; Thu, 19 Jul 2001 15:51:30 +0200 Received: (from leh@localhost) by donner.tecosim.de (8.11.2/8.11.2/SuSE Linux 8.11.1-0.5) id f6JDpUY06885 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 15:51:30 +0200 Date: Thu, 19 Jul 2001 15:51:30 +0200 From: Utz Lehmann To: linux-xfs@oss.sgi.com Subject: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid Message-ID: <20010719155130.D1330@de.tecosim.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="G4iJoqBmSsgzjUCe" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --G4iJoqBmSsgzjUCe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi I got an anaconda crash when i made a Raid 1 Partition for / and/or swap with Disk Druid. I think this has todo with the xfs fstype extension in anaconda: if fsType == "swap": continue NameError: fsType The original RH 7.1 works. The anaconda dumps are attached. utz --G4iJoqBmSsgzjUCe Content-Type: application/x-gunzip Content-Disposition: attachment; filename="anacdump.xfs-1.0.1-root_on_raid1.txt.gz" Content-Transfer-Encoding: base64 H4sICLDLVjsCA2FuYWNkdW1wLnhmcy0xLjAuMS1yb290X29uX3JhaWQxLnR4dACtWutz4riy /85f4dovyVRlEttgA6mzew+PPJgQkoVk58zcuuUSWIAOxmJlOwnz19/ulmTI7Cx495yqGce0 1A+1fv2w5SfFZnzKZivnVKQpV2uZ5U7CsvzDZc1xrkXCnZ8uikxdTEV6wVI2k2nMfjpzEpFy J/DdM0ekzv/AVAdu8vm5KtLTXMbyzMk5SPqZ/nzYiXph6iJfb0pRH5vn3gUpSMS0pF4sCnG+ 2Vo99bZPekA4acp4Mj8Xs1fU5pz+p9JbLfed9DUTaSLl5p1kK2OzzZcy9c6Di0zk/OMGPMcW PLtY5Ks9kX4QNEimlUWCI5wE/yOk/n3hnh+Q7CiasSSJIpKtODqbbTbJ9pTcMy/S2ZnD/lPn NFra9Sl/y3uJmK14TPrwNygkVbNCKZ7mk5niPD1f8HyEg39jX8TrhZIy3zCVi1zINHpvi1fX G2U06HXPrBXJlNX93pIjlP/rqpshad7pMEh5m20TawDC/nye5WyKPuiCtEcr7Z699bbJtZLr Ps+E4vHfsFBL3sNYw7PeOKyLTJ2axVljDVefv4gZ/29YEzb3rdFySfNcKud0neYbCQnizCk9 fObMs22W8/WZE8trqdYMRjPxjX9AOWTkWhZpPhRZfrqfjf6mhZ4baCiXUnXWmoMdT9sNd37+ 2fkpe2Wbny4dkJCLtOC1EVvzK6WkujSzarWhhLBzwAjBpgnPUOIuc84VMFzWcBmXjhfWW6Ff b9bIlEvnf/+vZv1w6VzUYvLRpbOOvVrplUsni1lQAwYFk8J6TTERo2IQV0OnXDr/0Cu7KcQ1 3oB2+JPOuMNyp9Voe822+4sRnoHS0xOQ6J2cOSdjEOW6LtzCXoX1s9JAuHMxlbsfzhycPt2b 7h2fzgKcPgHXaemBmVonJjd0fZ94WiHygBPYihcbMG3PolIbDOP+XDpGXs2g5NJ5m2fkDVrT BfKA5/APDMAf73sjfywe9GdS5feoJENnQp5Exzs7KjkydOt1r/VLLVuJzdVbrtil49ZqT7Iv HTn9N5/ll7VTgSFPtNrGq53GG782OVE8m+Qs5ye1TR1+ntSyyclGyQXQs88ijeUrjDRqIyBn PC82iGq9xAwGgtrAQ461TEG6+i3bpjMgh1bSi4i57DEVk46RjFFP045mHFCZAKVVG7hIiGNV iHjMWfyQJlsYaJsBzAexyFZA8lyjk2SP2dqa73lWrrHmQYmFSFmCUYHjvh1PWLoooFQhsW79 MjREdIzXqOlZg3Quu1srIKAxXFxHsamYOadf+JqnH3CsWTudnDAVfbk6gXGRSTfEmyHLO6q3 Vbd8+tEDSg7qJxuWimzpnHbUgmPkMpLQQgk8izpjK8E7ITNy92NWpJZ7kLNEMGgk8GZLnG3k FHk0ePonL5Q07F7wI3Zr+RDaqFSS7b5rbB92q9t+U4DX1ywh233P2H7zdND2e5i/dU7pTyY0 q4+s6yy6/3KQtbRbTLewevzpfGJrthRKbLWkul3Gl6PLsNIe1ky7oGF4H+4r8w4U+514A8M7 +LUy713xykRO3KHhvvt8lPsqXSTk/Iks8qXTmSsx00sn9PE0+to56MRraHxmyP8q8m9cAcJj YifozVXUu620B122VFxox7WN+d3bo+b3lGQ5QBdTDUFuqaLbEuy+0ej/yOBrhSUDFdY9Y+v1 +DjYb7DFw1Wi1eUPEkOwWyXRzfDgku+k4hhsY74pptBQOnLuEI2EEOJWMrobn/NitlJ/FGXl PK+gFqRm8QS2YhU9026tpGh9LPButlX7ustYu+dvYiZJY2AC7f5fB83GtWKyrBO6OCyz9HMT bxbqfP4HNVeJM2HJC4ulIl1No2vy20FdJf8jVwUx2kz2eFWN8RY6oEKxjJjbhvl2VI25B40M c8YmEhquYe8dzqJlKPV5umZqRbyeiaL+3UHefpEjJkc8X+oYIsMbhKg0iUbD48CccDWlJP6l WMgsYS86GTYIUBlUked/AhhEAoizpgQ/QMi4yDISo+FFAdIgdKniGLoeoYEoFgXPOOwc3bOE +Alimzx6rFJNIAWtGEuzP+akhk5s82M5aSTVK1/oyGgQ5FIZjR4qJaJ7qeRMR0ajZRLRfad6 Hn1cikRsNuA5vYVtA4DHanmwkyywg0HWwNbQ/tej6gfQVYFGveSAQCfiaNA/DDqCOzIQzmJ2 DKW9JS4LNveJiVfAyPj84bx3TrYSyr4to6fPmLby1z9PW9dMSRJCN84gK+EeEMzmMro+vFU3 0K3MCKMQsbpmBISwRRJdTY4jrNyrEX91vnJmE3gQmr0afa2WJ7oyESbMApvZuodt70lleJXI rfGEs9VrdNOthJFnaEV5rPuVq7VQ0DVp/9nC2TneMN7A4xp6sFNkucFbSHiLedSpEKVjCewa biHBTclo/HCw8O6SOlMM+mJqNEPfJvbDvRrYrmC3TgeZYpySSkiQW/JoUJbb1tHofJ50iLdh dvp5Um2nLZ+tlUf49hNhF6qQ0BaHJg12x9W0Xv1e2MoZWnxd9Y5oTnRMhwSqTRI9Dg/vSiJf GNb1kNCTraLJ3UGGezbjkGz03jcJM+tVdH93qKiUKyoDtmnb+yoBuyvMkFypIjUtbHrDSiEz gcpnW3zbd5Ec2+BPjjf4vW98hp5tEnhmoPvrQUcNlN6Jps5NLBpcVX+W+iRVrJ8jmrab//Rw vAzYB7nvuvFm0zzOHenGbVbo8mQhijWxtkxW6FaxPpnarNDUcPo96hzeoWuRmirUIizNRXQ9 qACJVx5rRMGNfl5uEaSyl2hyVa1Pm4h0wTbQeRO3b1LC5KZKp7bnoVbddGlVPLSXBFN41CT+ hk2BnWpp4Tee8m8F18/JLZuSfqu4aujjWe7slZ+WLXtHyo/pDJGjafrB8fM5NoPqYFdYdmNn zmibSpWtoPICTReAFuErTY/1Z6X9X8V6yqavetNsd/X1czXXjaCTpOKD3G3b2I8GlaJiWLzx 9bRQC2L2TFwMn/9KApOJXE91vW2XOezwyrss+73ge7mzTYDjRaXcaRPKryxnVEna9r3Er53K 7xauFtsNvVpo2xcTVzdHme2D9l6otEPzpF0lVModHyhuE1nbvpWokktvC4hvpSHbJpgti+j2 +WDStit+KmDDzD7ZtuppVHnN76Diua5ZdhWsfGIAFugciJFA9m8WfXrEtvrT45+31WVChIRq veW5vkmJVVJqWStZEQsqlXr9nlsWyU71l3l9uRYpRFv6rt56rk12/YdKr5V6kCZjY0ZgXyl1 qmWKfV6b447w2lDXf/WrULdpIr1fJb9DO8VTXYPNrRZC+MuSaDKo1iQ/q8L2yJ5rX2A8f6lk /XfV3/NsZ3+k/Jeeu5XpwrmDi2a3LzFu76qx00MFdiKa3VbWzvPhRyPIUMm7pzrPI+TN2F/r Eh8LrnKJ72+kllIW2MN991OhVroV8TzCWg4xX7K0DUvwbslZblthz9MYy6Orq2o9aWE6PK98 0z/pH2/xZly/fSRGQpXIosGk2s50ZZ7Bk7vZGFs9u5+PvGJP35wbeOyiF7W7xsHTb/kXL4c7 B5DAkmRSbKDVgudWPBTJiBtglcAfv7ZohDW2gI6RLQIXLj7eQamBO7w0cdSnC43W4dJo4V0D 5+EFcxRcwZEwHW/bJAwvRGvrYbwGdEH2OkprInvgw6VFcn2aqK/E7qLihocTQqLibRuFBjSC k1o430daiOJaxOjhcEC/UVGbuF1cUN2jW1oMGhIgMSRrWjRCJtMkD6l1ZK2jjpDWRpM84sRJ TWQnY5tNYkdiHWc2SQUthlzXwPEWMoZ0oQWQclofjjbQ4AYyh3r5pIx0kXNRWBsvDZeGcXqd Vo4Xn1QjYx3FtnFOC6eEyFLXhuPvJk4MyXCXPKhvaR/0wslRMBXgI9K5JMTU6bTMx6O0yfPj 48P46apPA0FthDjLLMiICPGY4Akgn7MiyYnUhHlTkpjlvYRlGogQRSLj6oWr2gCPkpOExrSy Np5o0ucFWfYKT2U9Bb2Q1gAA0meJeCiL5+lE9LRaaO+5FkrU8qTw7YROPvdF0oQ6kfFkuLt3 Mgke0EeTQhuGB+FED2j6Rmb41YnYaNUhETlTyRYPjx8oL8HuaCtTnoO2lf4ygUZaNJ9O0+l3 W5s+S0DEE38jobDPOCkRCe2BfqO9ntKqIFoG+og0zxaeXkFqTjYbu7NfMHKQ9pa4ZBppGIM2 4m3NNkQKysn2OwDaGnzjCzlCv8S9mFoBsGEDCK/BRw8l5afIW/6Ay4ROxHEmnfbmo5wh/wmw +cEBvsV3DEVGy8Q3sYMAkgLN9SowvjDN6P1VjUtpzoX9v6gSv9sgRoiRAWQhrfYo40IzYAz8 OcfIzC6hYUAYYCBmL3qpAe7eguUcHuyIEO7OzgvdzgZNDVrzVReRNARzsebfZKpntYkEDYy8 1zALbZyt+HYqmQ4YSFk4baFksSFR+CoRsBIi7iZl4IU6hSB0HpXMCcOhDh6IhzXTYRaG+wf5 exkj1CbjNxCTnBtFLX1oj5mBFfkSD9xnDDFLp/b6Y4IFRgreZHoSDSEciEoYPdn7Y+72iD/4 icV4CcFkQ6yJSSXBr3GQek53scRv62i0btfzLi02zZcXS/m68x2+owLfNdENd/0rIkE+17F0 M3q416RWLTe0fzn6Sw5nQh9u0GgbRuFxn79mzs7/WPuAeD3Zp3lI+8yn+zQfaZP7Lj6AwBP+ h/2xOo71RxMHP5vYHzD1gZDfKnPIXChAYZIQFTKIiSFcYau55/H9f/muUoyLNOEvXLNrfMY8 W+VSq2lbNRQL+NWZTZVt9EynyGELABG7D70EdNOvIkkcrljGnc5w6PQ7Tx1Hps5WFspZAqSd WIkX7kDfiiXAgVy5pg/HaMJQpMWbY0oAIe2c9HnvzKCdhNo8aNSoyE3jzH7H0i6TMccvee5l XCQ6APF1APilTeGrPwDcFaW2LijzeFcz2ujAeezSfWuvMu2AAL2XrlkzuSZ4+a6uIbBrYi54 bD+v8V2M4QXFhf5ipvMunOiDIhdBDglkhD0u/KzbaiayEgi+27Drg5nDmFKhD72WSRtqGtzF M6LtAh1mPQ21zOYe9y3PhIyJbL8hwql7ukoAgAl9G26+51oyqhtzlqyJ7H1nmUkGPuZ2kr4k heMlecqr702fLJn+WMr3bBsAKmGgqySLZ4waDt+zy4SBO1BNtHBHu+9rUtOIwNV0AYexNru1 b3YnXpvVlIvU5g21eb77ntxPDN2scqpVKk30adeXtjXyfd0hxMvZpoSAX+7cmudL7Xj8/EWI NX451YuVXJum7J4m4HhIyIBubtGo1f4xZyLh8S+1/wfvQ8X5yi0AAA== --G4iJoqBmSsgzjUCe Content-Type: application/x-gunzip Content-Disposition: attachment; filename="anacdump.xfs-1.0.1-swap_on_raid1.txt.gz" Content-Transfer-Encoding: base64 H4sICJTKVjsCA2FuYWNkdW1wLnhmcy0xLjAuMS1zd2FwX29uX3JhaWQxLnR4dACtWutz4rYW /85f4emXZGeyiW3AQKbtLY882BCShqR7dzsdj8ACdLEtKttJ2L/+nnMkGbLdgvuY2XXMkc5L +p2HLT8qNuNTNls5xyJNuUpkljsxy/J35zXHuRQxd747KzJ1NhXpGUvZTKYR++7EiUXKnabv njgidf4DUx24yeenqkiPcxnJEyfnIOkH+vNuK+qZqbM8WZei3rdOvTNSEItpST1bFOJ0vbF6 6h2f9IBw0pTxeH4qZi+ozTn+p9LbbfeN9ISJNJZy/UaylbHe5EuZeqfNs0zk/P0aVo4teHa2 yFc7Iv1ms0EyrSwSHOIk+B8i9e8L9/wmyQ7DGYvjMCTZiuNis/U63hzT8syLdHbisH+6OI22 XvqUv+b9WMxWPCJ9+BsUkqpZoRRP88lMcZ6eLng+xsG/sS/i5UxJma+ZykUuZBq+tcWr640y GrTfM2tFPGV1v7/kCOV/XXUrIM1bHQYpr7NNbA1A2J/Os5xNcQ16IO3eSrtlr/1NfKlkMuCZ UDz6GxZqyTsYa3h2NfbrIlOnxjlrrOEa8Gcx4/+GNUFr1xotlzTPpXKOkzRfS0gQJ065wifO PNtkOU9OnEheSpUwGM3EF/4O5ZCRiSzSfCSy/Hg3G/1NCz23qaFcStVZaw52PG7W3PnhB+e7 7IWtvzt3QEIu0oLXxizhF0pJdW5m1WojCWHngBGCTWOeocRt5pwrYDivoRvnjhfU24Ffb9Ws 9+fOWS1hK16sz51fjx6YiFzXPTpxzK139FstooU7d5LIqymgok6QVANnFPAH9VomVX6LLmTn zvcY5biYzpbqsNxpN+aMue0fjTiY+evxURYxb6sM9cKWBfWT0k64czGju+9OHJw+9XZtOzid NbfTfT2dptaJyQ1c3yeedrCjYoenfpDntxptKnjzWw0BggtAu3xViEu8gZ2AP+mM60XoeK2O +2PN4OzceZ1ntKi0HGeoGZYZ/8AA/PG+9u/be0Smfz8BpDhl0P2ohZE3iKF90vxdl38Dp7KV WF+85oqdO26t9igH0pHT//FZfl47FphViFZbe7XjaO3XJkeKZ5Oc5fyotq7Dz6NaNjlaK7kA evZRpJF8gZFGbQzkjOfFGgNHr0EGA83a0EOORKYgXf2SbdIZkAMr6VlEXPaZikjHWEaop2VH Mw7Aj4HSrg1dJESRKkT0wFl0l8YbGOiYAUw5kchWQPJco5NkP7DEmu95Vq6x5k6JhUhZjIGH 474dj1m6KKAaIrFu12VkiLgwXqOmZw3TuextrIAmjaFzXcWmYuYcf+IJT9/hWKt2PDliKvx0 cQTjIpNugDcjlndVf6Ou+fS9B5Qc1E/WLBXZ0jnuqgXH5MBIQhsl8CzsPlgJ3hGZkbvvsyK1 3MOcxYJBr4I3G+LsIKfIw+HjT7xQ0rB7zW+xW8tH0Kmlkmz3XWP7qFfd9qsCVj1hMdnue8b2 q8e9tt/C/I1zTH8yoVl9ZE2y8PbTXtbSbjHdgPf40/nAErYUSmy0pLp149NBN6y0u4TpJWgY 3rvbyrxDxX4n3qbhHf5cmfemeGEiJ+7AcN98PMh9kS5iWvyJLPKl050rMdOuE/p4Gn7u7l3E S+itZsj/IvIvXAHCI2In6M1V2L+utAc9tlRc6IXrGPN71wfN7yvJcoAuphqC3FKF1yXYfaPR /5bBlwozMSqse8bWy4fDYL/CLhK9RKvLHySGYLeKw6vRXpdvpOIYbA98XUyhZ3Xk3CEaCSHE rWR483DKi9lK/VGUlfO0gmKRGucJbMUqfKLdWknRfl/g3WyjdnWXsXbLX8VMksamCbTb/+41 G33FZFkndHFws1znFt4s1On8D2ouYmfC4mcWSUW6WkbX5Je9ukr+e64KYrSZ7P6iGuM1NFmF Yhkxdwzz9bgacx96JeY8mEhouIa9vz+LlqE04GnC1Ip4PRNFg5u9vIMiR0yOeb7UMUSGNwhR aRyOR4eBOeFqSkn8U7GQWcyedTJsEKAyqCJPPwEYRAyIs6Y0v4GQhyLLSIyGFwVIg9ClikPo uocur1gUPOOwc3TPYuIniK3z8L5KNYEUtGIszf6Ykxo6sc0P5aSxVC98oSOjQZBLZTi+q5SI bqWSMx0ZjbZJRLfd6nn0filisV7Dyukt7BgA3FfLg914gR0MsjZtDR18Pqh+CF0VaNQuNwl0 IgqHg/2gI7gjA+EsYodQ2l+iW7C5j0y8AEYeTu9O+6dkK6HsyzJ8/IhpK3/587R1yZQkIXTj DLMS7k2C2VyGl/u36gq6lRlhFCJW14wmIWwRhxeTwwgr92rMX5zPnNkE3gzMXo0/V8sTPRkL E2ZNm9l6+23vS2V4lcit8YSz1Ut41auEkSdoRXmk+5WLRCjomvT62cLZPdwwXsETIa5gt8hy g7eA8BbxsFshSh8ksGu4BQQ3JcOHu72Fd5vUmWLQF1OjGfg2se/v1cB2Bbt1PMwU45RUAoLc kofDsty2D0bn06RLvA2z00+Tajtt+WytPMC3mwh7UIWEtjgwabD3UE3rxe+FrZyBxddF/4Dm WMd0QKBax+H9aP+uxPKZYV0PCD3ZKpzc7GW4ZTMOyUbvfYswk6zC25t9RaX0qAzYlm3vqwTs tjBDcqWK1LKw6Y8qhcwEKp9t8W3fRXJsgz853OD3v/AZrmyLwDMD3Z/3LtRQ6Z1o6dzEwuFF 9WepD1JF+jmiZbv5D3eHy4B9kPuqG2+1zOPcgW7cZoUejxeiSIi1bbJCr4r18dRmhZaG0+9h d/8OXYrUVKE2YWkuwsthBUi88EgjCm7083KbIJU9h5OLan3aRKQLtobOm7h9kxImV1U6tZ0V atdNl1ZlhXaSYAqPmsTfsCmwWy0t/MJT/qXg+jm5bVPSLxW9hj6e5c5O+Wnbsneg/JjOEDla ph98eDrFZlDt7QrLbuzEGW9SqbIVVF6g6QLQJnyl6aH+rLT/s0imbPqiN812V58/Vlu6MXSS VHyQu2Mb+/GwUlSMileeTAu1IGbPxMXo6a8kMBnLZKrrbafMYfs977Hs94Lv5M4OAY4XlXKn TSg/s5xRJenY9xI/dyu/W7hYbNb0aqFjX0xcXB1ktg/aO6HSCcyTdpVQKXd8qLhNZB37VqJK Lr0uIL6VhmyHYLYswuunvUnbevxYwIaZfbJt1eO4ss9voOK5rnG7ClY+MAALdA7ESCD7Hws/ 3GNb/eH+z9vqMiFCQrWr5bm+SYlVUmpZK1kRCSqV2n/PLYtkt/rLvIFMRArRlr6pt55rk93g rtJrpT6kyciY0bSvlLrVMsUur81xB3htqOu/+lWo2zKRPqiS36Gd4qmuweZWCyH8ZXE4GVZr kp9UYXtkz7UvMJ4+VbL+q+rvebazP1D+y5W7lunCuYGLZrcvMa5vqrHTQwV2IprdVtbu0/5H I8hQ8ZunOs8j5M3YX+sS7wuuconvb6SWUhbY/X33Y6FWuhXxPMJaDjFfsnQMS/ONy1luW2HP 0xjLw4uLaj1pYTo8r3zTPxkcbvFmXL99JEZClcjC4aTazvRknsGTu9kYWz17Hw+8Yk9fnSt4 7KIXtdvGwdNv+RfP+zsHkMDieFKsodWC51Y8FMmIG2AVwx+/tmgENbaAjpEtmi5cfLyDUgN3 eGnhqE8XGq3DpdHGuwbOwwvmKLjCQsJ0vO2QMLwQraOH8dqkC7LXUVoL2Zs+XNok16eJ+krs LipueDghICredlBok0ZwUhvn+0gLUFybGD0cbtJvVNQhbhcdqnt0S86gIU0kBmRNm0bIZJrk IbWOrHXUEZBvNMkjTpzUQnYyttUidiTWcWaLVJAztHQNHG8jY0AXcoCUk3842kCDG8gcaPdJ GemixUVhHbw0XBrG6XXyHC8+qUbGOort4Jw2TgmQpa4Nx98tnBiQ4S6toL6lfdCO00LBVICP SOeSEFOn0zIfj9ImT/f3dw+PFwMaaNbGiLPMgoyIEI8xngDyOSvinEgtmDcliVnej1mmgQhR JDKunrmqDfGENo5pTCvr4IkmfcGQZS/wVNZX0AtpDQAgfZaIp7Z4ZE9ET6uF9p5roUQtTwpf j+jkc1ckTagTGc/fezsnk7AC+mhSaMPwwJ3oTZq+lhl+2CLWWnVARM5UvMED4DvKS7A72sqU 56BtpT9+oJE2zadDavrd0abPYhDxyF9JKOwzTopFTHug32gnU/IKomWoj0jzbOFpD1JzstnY nv2CkcO0v0SXaaRhDFqL14StidQsJ9sza9oafOMLOUK/xD2bWgGwYUMIr+F7DyXlx8hb/oDL hI7McSad9ubjnCH/EbD5zT18i68YiozcxDexwyYkBZrrVWB8ZprR+6sal9KcC/t/USUd6yMj xMgQspBWe5BxoRkwBv6cY2xml9AwIGxiIGbP2tUm7t6C5Rwe7IgQbM/OC93ONlsatObDMSJp COYi4V9kqmd1iAQNjLzVMAtsnK34ZiqZDhhIWThtoWSxJlH4KhGwEiDuJmXgBTqFIHTulcwJ w4EOHoiHhOkwC4Ldg/ydjBFok/EbiEnOjaK2PrTHzMCKfIkH7jOGmKVTe/0xwQIjBW8yPYmG EA5EJYwe7fwxdzvEb/zEYryEYLIh1sKkEuMHP0g9pbtI4ud7NFq3/rxJiy3z5cVSvmzXDt9R wdq1cBluBhdEgnyuY+lqfHerSe1abmj/dfSXHM6EPtyg0Q6MwuM+f8mc7fpj7QPi5WSX5iHt I5/u0nykTW57+AACT/jvdsfqODYYTxz8bGJ3wNQHQn67zCFzoQCFcUxUyCAmhtDDdmtnxXf/ 5dtK8VCkMX/mml3jM+LZKpdaTceqoVjAb2xsquzgynSLHLYAELH9lkxAN/0i4tjhimXc6Y5G zqD72HVk6mxkoZwlQNqJlHjmDvStWAIcyJUJfZtGE0YiLV4dUwIIaaekz3tjBu0k1OZho0ZF bhpl9juWTpmMOX7JcyujItYBiK8DYF06FL76G8NtUerogjKPtjWjgws4j1y6b+9Upi0QoPfS NWsmE4KX7+oaArsm5oJH9vMa38UYXlBc6C9mum/CiT4ochHkkEDG2OPCz7qtZiIrgeC7Desf zBxFlAp96LVM2lDT5k00I9o20GHW40jLbO1wX/NMyIjI9hsinLqjqwQAmDCw4eZ7riWjugfO 4oTI3leWmWTgY24n6UtS+LCklfLqO9MnS6Y/lvI92waAShjoKcmiGaOGw/esmzBwA6qJFmxp twNNahkR6E0PcBhps9u7ZnejxHhTOqnNG2nzfPcteRAbuvFyqlUqTfRp15e2NfJ93SFEy9m6 hIBf7lzC86VeePz8RYgEv5zqR0ompim7pQk4HhAyoJtbNGq17+dMxDz6sfZ/sT1rXi0uAAA= --G4iJoqBmSsgzjUCe-- From owner-linux-xfs@oss.sgi.com Thu Jul 19 07:40:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JEeFd28822 for linux-xfs-outgoing; Thu, 19 Jul 2001 07:40:15 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JEeCV28798 for ; Thu, 19 Jul 2001 07:40:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id HAA09534 for ; Thu, 19 Jul 2001 07:39:57 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2470400; Thu, 19 Jul 2001 09:38:47 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA32719; Thu, 19 Jul 2001 09:38:47 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6JEdcd31931; Thu, 19 Jul 2001 09:39:38 -0500 Message-Id: <200107191439.f6JEdcd31931@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Nathan Scott cc: Wolfgang Henselmann-Weiss , Daniel Moore , linux-xfs@oss.sgi.com Subject: Re: XFS problems In-Reply-To: Message from Nathan Scott of "Thu, 19 Jul 2001 21:33:48 +1000." <20010719213347.A196344@wobbly.melbourne.sgi.com> Date: Thu, 19 Jul 2001 09:39:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, Jul 19, 2001 at 09:15:15AM +0200, Wolfgang Henselmann-Weiss wrote: > > > > syslog output is ... > > |Jul 19 09:08:48 wolfi kernel: XFS: SB sanity check 2 failed > > |Jul 19 09:08:48 wolfi kernel: XFS: SB validate failed > > > > Hmmm ... that looks grim - the error comes from here, in the > XFS kernel code (xfs_mount.c): > > if (sbp->sb_dblocks == 0 || > sbp->sb_dblocks > > (xfs_drfsbno_t)sbp->sb_agcount * sbp->sb_agblocks || > sbp->sb_dblocks < (xfs_drfsbno_t)(sbp->sb_agcount - 1) * > sbp->sb_agblocks + XFS_MIN_AG_BLOCKS) { > cmn_err(CE_WARN, "XFS: SB sanity check 2 failed"); > return XFS_ERROR(EFSCORRUPTED); > } > > So, it seems mkfs might be coming up with bad data.. haven't ever > seen that before. Could you run xfs_db on the device, and print > the superblock & send us that? Something like: > > # xfs_db -c sb -c p /dev/foo > > and we should be able to narrow it down to one of those 3 condition. > > thanks. > > -- > Nathan OK, this is very interesting, the mkfs output: |wolfi:/etc # mkfs.xfs -f /dev/hde7 |meta-data=/dev/hde7 isize=256 agcount=16, agsize=262144 blks |data = bsize=4096 blocks=3932200, imaxpct=25 | = sunit=0 swidth=0 blks, unwritten=0 |naming =version 2 bsize=4096 |log =internal log bsize=4096 blocks=1200 |realtime =none extsz=65536 blocks=0, rtextents=0 This shows that mkfs picked an allocation group size which left a very small allocation group at the end of the filesystem. You have 16 allocation groups, 16 * 262144 = 4194304 file system blocks, but you only actually have 3932200 blocks. 15 allocation groups take 3932160 leaving a huge 40 blocks for the last one, this fails the test in the mount code which Nathan posted. You could fool mkfs into thinking the device is slightly smaller for now by doing this: mkfs -t xfs -f -d 3932160b /dev/hde7 I think this will then mount. Clearly mkfs should not be building a filesystem which does not mount! Steve From owner-linux-xfs@oss.sgi.com Thu Jul 19 07:53:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JErtb00763 for linux-xfs-outgoing; Thu, 19 Jul 2001 07:53:55 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JEroV00714 for ; Thu, 19 Jul 2001 07:53:50 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA12059 for ; Thu, 19 Jul 2001 07:53:40 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2464636; Thu, 19 Jul 2001 09:52:33 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA93404; Thu, 19 Jul 2001 09:52:33 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6JErOR31956; Thu, 19 Jul 2001 09:53:24 -0500 Message-Id: <200107191453.f6JErOR31956@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Gerald Britton cc: Sidik Isani , Steve Lord , linux-xfs@oss.sgi.com Subject: Re: 2.4.3-SGI_XFS_1.0.1smp leaks? In-Reply-To: Message from Gerald Britton of "Thu, 19 Jul 2001 08:35:50 EDT." <20010719083550.A6962@nevermore.toe.doomcom.org> Date: Thu, 19 Jul 2001 09:53:24 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > here is a little more info from my machine.. i suspect the behavior will be > more pronounced either this evening or tomorrow morning as my machine will ha > ve > been up longer. The machine has been mostly idle, no processes appear to be > leaking, yet more and more ends up being pushed into swap space. After a day > or two more, the "free" memory listed in /proc/meminfo will drop to around 4M > and the "cached" memory drops down to around 40M or so. The majority of > process memory ends up being moved into swap space and the machine starts to > slowly grind. I'll see if i can leave this up another day or two and post > some more numbers then. There is nothing wrong with the numbers you sent, here are mine - from a very responsive box (typing on it now) kmem_cache 102 102 232 6 6 1 : 252 126 nfs_read_data 150 150 384 15 15 1 : 124 62 nfs_write_data 128 190 384 14 19 1 : 124 62 nfs_page 274 400 96 7 10 1 : 252 126 tcp_tw_bucket 80 80 96 2 2 1 : 252 126 tcp_bind_bucket 226 226 32 2 2 1 : 252 126 tcp_open_request 59 59 64 1 1 1 : 252 126 inet_peer_cache 177 177 64 3 3 1 : 252 126 ip_fib_hash 10 226 32 2 2 1 : 252 126 ip_dst_cache 240 240 160 10 10 1 : 252 126 arp_cache 90 90 128 3 3 1 : 252 126 blkdev_requests 1536 1560 96 39 39 1 : 252 126 xfs_chashlist 3851 6464 16 32 32 1 : 252 126 xfs_ili 2839 3164 136 113 113 1 : 252 126 xfs_ifork 0 0 56 0 0 1 : 252 126 xfs_efi_item 75 75 260 5 5 1 : 124 62 xfs_efd_item 90 90 260 6 6 1 : 124 62 xfs_buf_item 208 208 148 8 8 1 : 252 126 xfs_dabuf 202 202 16 1 1 1 : 252 126 xfs_da_state 22 22 340 2 2 1 : 124 62 xfs_trans 134 252 320 16 21 1 : 124 62 xfs_inode 18405 46432 468 4764 5804 1 : 124 62 xfs_btree_cur 56 56 140 2 2 1 : 252 126 xfs_bmap_free_item 185 202 16 1 1 1 : 252 126 page_buf_t 299 540 192 26 27 1 : 252 126 page_buf_reg_t 3 40 96 1 1 1 : 252 126 avl_object_t 3 113 32 1 1 1 : 252 126 avl_entry_t 285 1130 32 6 10 1 : 252 126 dnotify cache 0 0 20 0 0 1 : 252 126 file lock cache 168 168 92 4 4 1 : 252 126 fasync cache 1 202 16 1 1 1 : 252 126 uid_cache 5 226 32 2 2 1 : 252 126 skbuff_head_cache 482 528 160 21 22 1 : 252 126 sock 225 225 832 25 25 2 : 124 62 sigqueue 261 261 132 9 9 1 : 252 126 cdev_cache 2810 3068 64 52 52 1 : 252 126 bdev_cache 9469 9735 64 164 165 1 : 252 126 mnt_cache 16 160 96 3 4 1 : 252 126 inode_cache 19838 38400 480 4800 4800 1 : 124 62 dentry_cache 9727 32580 128 1086 1086 1 : 252 126 dquot 0 0 96 0 0 1 : 252 126 filp 2329 2400 96 60 60 1 : 252 126 names_cache 33 33 4096 33 33 1 : 60 30 buffer_head 19064 28640 96 477 716 1 : 252 126 mm_struct 330 330 128 11 11 1 : 252 126 vm_area_struct 2523 3186 64 54 54 1 : 252 126 fs_cache 230 354 64 6 6 1 : 252 126 files_cache 207 207 416 23 23 1 : 124 62 signal_act 150 150 1312 50 50 1 : 60 30 size-131072(DMA) 0 0 131072 0 0 32 : 0 0 size-131072 0 0 131072 0 0 32 : 0 0 size-65536(DMA) 0 0 65536 0 0 16 : 0 0 size-65536 8 8 65536 8 8 16 : 0 0 size-32768(DMA) 0 0 32768 0 0 8 : 0 0 size-32768 0 3 32768 0 3 8 : 0 0 size-16384(DMA) 0 0 16384 0 0 4 : 0 0 size-16384 11 16 16384 11 16 4 : 0 0 size-8192(DMA) 0 0 8192 0 0 2 : 0 0 size-8192 3 6 8192 3 6 2 : 0 0 size-4096(DMA) 0 0 4096 0 0 1 : 60 30 size-4096 94 124 4096 94 124 1 : 60 30 size-2048(DMA) 0 0 2048 0 0 1 : 60 30 size-2048 122 152 2048 72 76 1 : 60 30 size-1024(DMA) 0 0 1024 0 0 1 : 124 62 size-1024 252 252 1024 63 63 1 : 124 62 size-512(DMA) 0 0 512 0 0 1 : 124 62 size-512 236 360 512 35 45 1 : 124 62 size-256(DMA) 0 0 256 0 0 1 : 252 126 size-256 723 975 256 65 65 1 : 252 126 size-128(DMA) 0 0 128 0 0 1 : 252 126 size-128 3219 3750 128 125 125 1 : 252 126 size-64(DMA) 0 0 64 0 0 1 : 252 126 size-64 1926 2714 64 46 46 1 : 252 126 size-32(DMA) 0 0 32 0 0 1 : 252 126 size-32 2184 9605 32 84 85 1 : 252 126 There are almost certainly cron jobs which run overnight and scan the whole disk looking for stuff, these push a lot of entries into the inode cache, and in your case a lot of data into the filesystem cache. This should all be reclaimable memory as soon as something else wants it. What concerns me is that this is forcing the system into swap instead of reclaiming some of the memory. I suspect this is a Redhat'ism so to speak, it is not behaviour I normally see, it seems to be hard to get things onto the swap device unless you really pound on the system. Could you try the 2.4.5 based rpm instead and see if this one exhibits the same behaviour? Thanks Steve > > % uname -r > Linux nevermore.toe.doomcom.org 2.4.3-SGI_XFS_1.0.1smp #1 SMP > Mon Jul 9 14:03:40 CDT 2001 i686 unknown > > % uptime > 8:34am up 1 day, 11:15, 3 users, load average: 0.04, 0.05, 0.01 > > % cat /proc/meminfo > total: used: free: shared: buffers: cached: > Mem: 392212480 348160000 44052480 897024 0 109670400 > Swap: 266256384 24064000 242192384 > MemTotal: 383020 kB > MemFree: 43020 kB > MemShared: 876 kB > Buffers: 0 kB > Cached: 107100 kB > Active: 84196 kB > Inact_dirty: 20888 kB > Inact_clean: 2892 kB > Inact_target: 6408 kB > HighTotal: 0 kB > HighFree: 0 kB > LowTotal: 383020 kB > LowFree: 43020 kB > SwapTotal: 260016 kB > SwapFree: 236516 kB > > % cat /proc/slabinfo > slabinfo - version: 1.1 (SMP) > kmem_cache 102 102 232 6 6 1 : 252 126 > ip_conntrack 50 50 384 5 5 1 : 124 62 > ip_fib_hash 22 226 32 2 2 1 : 252 126 > clip_arp_cache 0 0 128 0 0 1 : 252 126 > ip_mrt_cache 0 0 96 0 0 1 : 252 126 > tcp_tw_bucket 0 0 128 0 0 1 : 252 126 > tcp_bind_bucket 15 226 32 2 2 1 : 252 126 > tcp_open_request 0 0 96 0 0 1 : 252 126 > inet_peer_cache 1 59 64 1 1 1 : 252 126 > ip_dst_cache 37 140 192 7 7 1 : 252 126 > arp_cache 7 30 128 1 1 1 : 252 126 > xfs_chashlist 3368 8282 16 41 41 1 : 252 126 > xfs_ili 324 588 136 21 21 1 : 252 126 > xfs_ifork 2 134 56 2 2 1 : 252 126 > xfs_efi_item 15 15 260 1 1 1 : 124 62 > xfs_efd_item 15 15 260 1 1 1 : 124 62 > xfs_buf_item 70 78 148 3 3 1 : 252 126 > xfs_dabuf 202 202 16 1 1 1 : 252 126 > xfs_da_state 0 11 340 0 1 1 : 124 62 > xfs_trans 21 48 320 3 4 1 : 124 62 > xfs_inode 32958 37384 468 4673 4673 1 : 124 62 > xfs_btree_cur 28 28 140 1 1 1 : 252 126 > xfs_bmap_free_item 126 202 16 1 1 1 : 252 126 > page_buf_t 139 320 192 16 16 1 : 252 126 > page_buf_reg_t 3 80 96 2 2 1 : 252 126 > avl_object_t 3 226 32 2 2 1 : 252 126 > avl_entry_t 127 452 32 4 4 1 : 252 126 > blkdev_requests 3840 3880 96 97 97 1 : 252 126 > dnotify cache 0 0 20 0 0 1 : 252 126 > file lock cache 126 126 92 3 3 1 : 252 126 > fasync cache 1 202 16 1 1 1 : 252 126 > uid_cache 10 226 32 2 2 1 : 252 126 > skbuff_head_cache 177 480 160 20 20 1 : 252 126 > sock 209 270 1280 90 90 1 : 60 30 > inode_cache 33171 37160 480 4645 4645 1 : 124 62 > bdev_cache 23 118 64 2 2 1 : 252 126 > sigqueue 261 261 132 9 9 1 : 252 126 > kiobuf 0 0 128 0 0 1 : 252 126 > dentry_cache 16941 27840 128 928 928 1 : 252 126 > dquot 0 0 128 0 0 1 : 252 126 > filp 2068 2080 96 52 52 1 : 252 126 > names_cache 2 2 4096 2 2 1 : 60 30 > buffer_head 11400 11400 96 285 285 1 : 252 126 > mm_struct 191 210 128 7 7 1 : 252 126 > vm_area_struct 2649 8319 64 102 141 1 : 252 126 > fs_cache 191 236 64 4 4 1 : 252 126 > files_cache 126 126 416 14 14 1 : 124 62 > signal_act 99 99 1312 33 33 1 : 60 30 > size-131072(DMA) 0 0 131072 0 0 32 : 0 0 > size-131072 0 0 131072 0 0 32 : 0 0 > size-65536(DMA) 0 0 65536 0 0 16 : 0 0 > size-65536 7 7 65536 7 7 16 : 0 0 > size-32768(DMA) 0 0 32768 0 0 8 : 0 0 > size-32768 5 5 32768 5 5 8 : 0 0 > size-16384(DMA) 0 0 16384 0 0 4 : 0 0 > size-16384 4 5 16384 4 5 4 : 0 0 > size-8192(DMA) 0 0 8192 0 0 2 : 0 0 > size-8192 9 9 8192 9 9 2 : 0 0 > size-4096(DMA) 0 0 4096 0 0 1 : 60 30 > size-4096 54 54 4096 54 54 1 : 60 30 > size-2048(DMA) 1 2 2048 1 1 1 : 60 30 > size-2048 68 68 2048 34 34 1 : 60 30 > size-1024(DMA) 0 0 1024 0 0 1 : 124 62 > size-1024 268 268 1024 67 67 1 : 124 62 > size-512(DMA) 0 0 512 0 0 1 : 124 62 > size-512 216 216 512 27 27 1 : 124 62 > size-256(DMA) 0 0 256 0 0 1 : 252 126 > size-256 424 495 256 33 33 1 : 252 126 > size-128(DMA) 0 0 128 0 0 1 : 252 126 > size-128 1342 2160 128 72 72 1 : 252 126 > size-64(DMA) 0 0 64 0 0 1 : 252 126 > size-64 6485 6490 64 110 110 1 : 252 126 > size-32(DMA) 0 0 32 0 0 1 : 252 126 > size-32 1534 6102 32 54 54 1 : 252 126 From owner-linux-xfs@oss.sgi.com Thu Jul 19 08:04:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JF4SU04373 for linux-xfs-outgoing; Thu, 19 Jul 2001 08:04:28 -0700 Received: from nevermore.toe.doomcom.org (IDENT:mail@dsl092-078-112.bos1.dsl.speakeasy.net [66.92.78.112]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JF4QV04342 for ; Thu, 19 Jul 2001 08:04:26 -0700 Received: by nevermore.toe.doomcom.org (Postfix, from userid 3499) id 84B0820BA0E; Thu, 19 Jul 2001 11:04:25 -0400 (EDT) Date: Thu, 19 Jul 2001 11:04:25 -0400 From: Gerald Britton To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: 2.4.3-SGI_XFS_1.0.1smp leaks? Message-ID: <20010719110425.A7367@nevermore.toe.doomcom.org> References: <200107191453.f6JErOR31956@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107191453.f6JErOR31956@jen.americas.sgi.com>; from lord@sgi.com on Thu, Jul 19, 2001 at 09:53:24AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > What concerns me is that this is forcing the system into swap instead > of reclaiming some of the memory. I suspect this is a Redhat'ism so > to speak, it is not behaviour I normally see, it seems to be hard to > get things onto the swap device unless you really pound on the system. The last time the machine was up long enough to exhibit this behavior, it had about 100M in swap which could not manage to unswap. Summing over the SIZE of all processes gave about 150M or so (the machine has 384M of real ram). summing over the RSS of all processes gave about 80M, and starting anything new forced more and more out of real ram and into swap. > Could you try the 2.4.5 based rpm instead and see if this one exhibits > the same behaviour? I'm going to leave the system up for a day or two more to see if i can get the behavior to exhibit itself again, i'm already starting to experience slowdown, but it hasn't become severe. If the behavior does occur again, I'll post some stats then and try the 2.4.5 based rpms. -- Gerald From owner-linux-xfs@oss.sgi.com Thu Jul 19 09:19:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JGJDS30244 for linux-xfs-outgoing; Thu, 19 Jul 2001 09:19:13 -0700 Received: from meryl.it.uu.se (root@meryl.it.uu.se [130.238.12.42]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JGJAV30205 for ; Thu, 19 Jul 2001 09:19:11 -0700 Received: from Dumbo (Dumbo.DoCS.UU.SE [130.238.8.114]) by meryl.it.uu.se (8.8.5/8.8.5) with ESMTP id SAA25584; Thu, 19 Jul 2001 18:18:43 +0200 (MET DST) Received: (from johanb@localhost) by Dumbo (8.9.3/8.9.3/Debian 8.9.3-21) id SAA00747; Thu, 19 Jul 2001 18:19:00 +0200 Message-ID: <15191.2103.377219.94936@veda.it.uu.se> Date: Thu, 19 Jul 2001 18:17:59 +0200 From: Johan Bengtsson To: linux-xfs@oss.sgi.com Subject: root and xfsdump. X-Mailer: VM 6.90 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I noticed that xfsdump insist on being run only by root. Would things break if it was run by a normal user, given that this user can read the disk device? / Johan From owner-linux-xfs@oss.sgi.com Thu Jul 19 09:18:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JGITk29954 for linux-xfs-outgoing; Thu, 19 Jul 2001 09:18:29 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JGIQV29921 for ; Thu, 19 Jul 2001 09:18:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA07886 for ; Thu, 19 Jul 2001 09:18:10 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2466429; Thu, 19 Jul 2001 11:17:07 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA58691; Thu, 19 Jul 2001 11:17:07 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6JGHwk32337; Thu, 19 Jul 2001 11:17:58 -0500 Message-Id: <200107191617.f6JGHwk32337@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Tru Huynh of "Thu, 19 Jul 2001 15:40:14 +0200." <3B56E33E.B4465042@pasteur.fr> Date: Thu, 19 Jul 2001 11:17:58 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk SMP may be part of the problem here, but I think I have a work around for the underlying problem. The issue is I think that xfs log writes are somewhere between 512 bytes and 32K in size, and they vary in 512 byte multiples. This causes the log writes to trigger some code in raid5 which makes you wait for other I/O to complete. If you choose another partition (non raid5) for the log and make an external log instead of using an internal log then the issue should go away, we are going to test this here. I suppose a mirrored log would be the best solution here as you could still survive the loss of a drive with the log on it. In the meantime I am going to look at how we can stripe align the log writes which would be a good thing anyway. Steve > Hello, > > It looks like a kernel SMP issue more than a 3ware driver > problem. > - I have tried the following SMP kernels: > 2.4.3-xfs-1.0.1 and 2.4.7pre8 cvs version which include > the same 3ware 3w-xxxx driver. (I have not yet flash the firmware). > - I can see it on a plain IDE raid5 partition. > > I will now flash the 3ware card firmware. but I don't > know what that can change... > > Next step is rebooting with noapic. > > /dev/md1 is now a raid5-xfs on the system HD > #------------------------------- > # raid5 on hda > #------------------------------- > raiddev /dev/md1 > raid-level 5 > nr-raid-disks 3 > persistent-superblock 1 > chunk-size 64 > parity-algorithm left-symmetric > # > device /dev/hda6 > raid-disk 0 > device /dev/hda7 > raid-disk 1 > device /dev/hda8 > raid-disk 2 > > I can still see the nfs freeze (server nfs.cluster not responding) > on both raid5 devices under 2.4.3-xfs. on the client side > syslog reports a "nfs_statfs: statfs error = 116 ". > > I can still see it under 2.4.7pre8 on /dev/md0 or /dev/md1 > but only after a little longer time... > > Off topic: One strange thing is the checksumming function: > /var/log/messages > kernel: raid5: measuring checksumming speed > kernel: 8regs : 1169.200 MB/sec > kernel: 32regs : 788.000 MB/sec > kernel: pIII_sse : 1727.600 MB/sec > kernel: pII_mmx : 1924.000 MB/sec > kernel: p5_mmx : 2045.200 MB/sec > kernel: raid5: using function: pIII_sse (1727.600 MB/sec) > > Why not using the faster p5_mmx ? > > > > >4) try SMP+raid5 on local IDE HD to rule out 3ware issue > ruled out. :( > > Tru > -- > Dr Tru Huynh | Bioinformatique Structurale > mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 > Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 09:26:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JGQvM00343 for linux-xfs-outgoing; Thu, 19 Jul 2001 09:26:57 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JGQtV00311 for ; Thu, 19 Jul 2001 09:26:55 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA00480 for ; Thu, 19 Jul 2001 09:26:44 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2473050; Thu, 19 Jul 2001 11:25:24 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA20183; Thu, 19 Jul 2001 11:25:24 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6JGQEn32426; Thu, 19 Jul 2001 11:26:14 -0500 Message-Id: <200107191626.f6JGQEn32426@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Johan Bengtsson cc: linux-xfs@oss.sgi.com Subject: Re: root and xfsdump. In-Reply-To: Message from Johan Bengtsson of "Thu, 19 Jul 2001 18:17:59 +0200." <15191.2103.377219.94936@veda.it.uu.se> Date: Thu, 19 Jul 2001 11:26:14 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi, > I noticed that xfsdump insist on being run only by root. > Would things break if it was run by a normal user, given that this > user can read the disk device? > > / Johan xfsdump writes an inventory file out to /var/xfsdump/inventory/ this would fail if you were not root - unless you opened up permissions in there. There is a -J option which may surpress writing to this directory, I only read the man page, not the code. Steve From owner-linux-xfs@oss.sgi.com Thu Jul 19 09:29:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JGTTE01102 for linux-xfs-outgoing; Thu, 19 Jul 2001 09:29:29 -0700 Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JGTNV01052 for ; Thu, 19 Jul 2001 09:29:23 -0700 Received: from iastate.edu (cousteau.eng.iastate.edu [129.186.23.164]) by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id LAA16268; Thu, 19 Jul 2001 11:28:10 -0500 Message-ID: <3B570A9A.CE948CE5@iastate.edu> Date: Thu, 19 Jul 2001 11:28:10 -0500 From: Adrian Hill X-Mailer: Mozilla 4.75 [en] (X11; U; IRIX 6.5 IP22) X-Accept-Language: en MIME-Version: 1.0 To: Jan Kara CC: Nathan Scott , Tad Dolphay , Fermin Molina , linux-xfs@oss.sgi.com Subject: Re: Quota reporting for NFS mounts References: <200107181532.KAA30810@fsgi158.americas.sgi.com> <10107191010.ZM220212@wobbly.melbourne.sgi.com> <20010719021942.A28795@atrey.karlin.mff.cuni.cz> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id f6JGTNV01056 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello All, I have gotten quota reporting working, using the -pre7 utils. It seems that the problem was in hosts.allow / hosts.deny. We discovered that you need to specify which hosts (much like portmap) have are allowed to contact rpc.rquotad. After that adjustment, it seems to work like a charm! Thanks for all the advice, -Adrian > > Actually I had some reports about rpc.rquotad SEGFAULTing. The > bug should be fixed in -pre8 utils I released yesterday so please > try those. If it doesn't help, tell me. > > Honza From owner-linux-xfs@oss.sgi.com Thu Jul 19 10:13:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JHD7Q11619 for linux-xfs-outgoing; Thu, 19 Jul 2001 10:13:07 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JHD2V11589 for ; Thu, 19 Jul 2001 10:13:03 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6JHCO003401; Thu, 19 Jul 2001 19:12:24 +0200 (CEST) Message-ID: <3B5714E5.44966F10@pasteur.fr> Date: Thu, 19 Jul 2001 19:12:05 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <200107191617.f6JGHwk32337@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A little update, At least, some better news: I did *NOT* see the problem (yet!) with the noapic option with 2.4.7pre8-SMP Steve Lord wrote: > <...> > If you choose another partition (non raid5) for the log and make an external > log instead of using an internal log then the issue should go away, we > are going to test this here. I suppose a mirrored log would be the best > solution here as you could still survive the loss of a drive with the > log on it. I wish I could do that :) - hda and hdc on a raid 1 array (system disk) + mirrored xfs log - sda..sdh for a 7 disk + 1 hot spare disk for the raid5 array. The only issue is space, trying to squeeze a second IDE disk on the second IDE controller will not easily be manageable is the rack :( I do have a spare system disk on the shelf, and quick method to restore the system disk but I would not risk putting the xfs log on this lone disk. What if I cut the 8 disks in 2 parts 1st partition of sd[a..d] of 2 GB (enough?) for a raid10 array for the log 2nd partition of sd[a..g] for the main raid5 array sdh for the hot spare? Best regards, Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 10:20:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JHKgG13531 for linux-xfs-outgoing; Thu, 19 Jul 2001 10:20:42 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JHKeV13504 for ; Thu, 19 Jul 2001 10:20:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id KAA10522 for ; Thu, 19 Jul 2001 10:20:29 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2471299; Thu, 19 Jul 2001 12:19:23 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id MAA96941; Thu, 19 Jul 2001 12:19:22 -0500 (CDT) Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid From: Eric Sandeen To: Utz Lehmann Cc: linux-xfs@oss.sgi.com In-Reply-To: <20010719155130.D1330@de.tecosim.com> References: <20010719155130.D1330@de.tecosim.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 19 Jul 2001 12:19:07 -0500 Message-Id: <995563148.12920.41.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 19 Jul 2001 15:51:30 +0200, Utz Lehmann wrote: > Hi > > I got an anaconda crash when i made a Raid 1 Partition for / and/or swap > with Disk Druid. > I think this has todo with the xfs fstype extension in anaconda: > > if fsType == "swap": continue > NameError: fsType Ok, I put a new update disk in the updates/ directory under Release-1.0.1/installer/updates. This should fix things for you. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 19 11:13:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JIDQL29661 for linux-xfs-outgoing; Thu, 19 Jul 2001 11:13:26 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JIDOV29627 for ; Thu, 19 Jul 2001 11:13:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA08639 for ; Thu, 19 Jul 2001 11:10:57 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2476545; Thu, 19 Jul 2001 13:12:05 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA99988; Thu, 19 Jul 2001 13:12:05 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6JICsI32762; Thu, 19 Jul 2001 13:12:54 -0500 Message-Id: <200107191812.f6JICsI32762@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh , jjaakkol@cs.Helsinki.FI cc: Steve Lord , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Tru Huynh of "Thu, 19 Jul 2001 19:12:05 +0200." <3B5714E5.44966F10@pasteur.fr> Date: Thu, 19 Jul 2001 13:12:54 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > A little update, > > At least, some better news: > I did *NOT* see the problem (yet!) with the noapic option > with 2.4.7pre8-SMP I am informed that there is a fix in the latest kernels in the raid5 code to fix some stall issues which ext3 hit. So it maybe that the answer here is to run the latest kernels. I still do not like the fact we do non-stripe friendly I/O to the log, and want to look into that. Jani, this may also be the source of your problems, we did experience an almost complete lockup here with the 1.0.1 rpm kernel. If you get a chance can you run the latest cvs kernel? Steve > > Steve Lord wrote: > > > <...> > > > If you choose another partition (non raid5) for the log and make an externa > l > > log instead of using an internal log then the issue should go away, we > > are going to test this here. I suppose a mirrored log would be the best > > solution here as you could still survive the loss of a drive with the > > log on it. > > I wish I could do that :) > - hda and hdc on a raid 1 array (system disk) + mirrored xfs log > - sda..sdh for a 7 disk + 1 hot spare disk for the raid5 array. > > The only issue is space, trying to squeeze a second IDE disk > on the second IDE controller will not easily be manageable is > the rack :( > I do have a spare system disk on the shelf, and quick method to > restore the system disk but I would not risk putting the xfs log > on this lone disk. > > What if I cut the 8 disks in 2 parts > 1st partition of sd[a..d] of 2 GB (enough?) for a raid10 array for the > log > 2nd partition of sd[a..g] for the main raid5 array > sdh for the hot spare? > > Best regards, > > Tru > -- > Dr Tru Huynh | Bioinformatique Structurale > mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 > Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 11:36:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JIaQd04398 for linux-xfs-outgoing; Thu, 19 Jul 2001 11:36:26 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JIaJV04337 for ; Thu, 19 Jul 2001 11:36:19 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6JIaH0419913; Thu, 19 Jul 2001 20:36:17 +0200 (CEST) Message-ID: <3B57288E.83685922@pasteur.fr> Date: Thu, 19 Jul 2001 20:35:58 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: oops 2.4.7pre8 + xlog_recover_reorder_trans: unrecognized type of log operation (long) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Here is what I have done. I might have been stupic :| /dev/md0 raid5 array 7+1 hot spare # Sample raid-5 configuration # raiddev /dev/md0 raid-level 5 nr-raid-disks 7 # Spare disks for hot reconstruction #nr-spare-disks 1 persistent-superblock 1 chunk-size 64 # the best one for maximum performance: # parity-algorithm left-symmetric #parity-algorithm right-asymmetric #parity-algorithm right-symmetric device /dev/sdb1 raid-disk 0 device /dev/sdc1 raid-disk 1 device /dev/sdd1 raid-disk 2 device /dev/sde1 raid-disk 3 device /dev/sdf1 raid-disk 4 device /dev/sdg1 raid-disk 5 device /dev/sdh1 raid-disk 6 # device /dev/sda1 spare-disk 0 # 1) remove the hot spare #raidhotremove /dev/md0 /dev/sda1 2) put an xfs fs on the spare disk # mkfs.xfs -f /dev/sda1 3) rsyncing from the xfs raid5 array (/dev/md0->/raid4) to the new xfs partition (/dev/sda1 ->/sda1) # cd /raid5 # rsync -av * /sda1 there is about ~55 MB of data during the process rsync segfault :( then for each of the subdir under /raid5 I did one by one a # rsync dir1 /sda1 # rsync dir2 /sda1 ... # rsync -av tftpboot /sda1 building file list ... done tftpboot/ tftpboot/X86PC/ tftpboot/X86PC/UNDI/ tftpboot/X86PC/UNDI/BStrap/ tftpboot/X86PC/UNDI/BStrap/bstrap.0 tftpboot/X86PC/UNDI/linux-install/ tftpboot/X86PC/UNDI/linux-install/linux.0 Segmentation fault rsync segfault again and I got a oops: bash-2.04# ksymoops < /tmp/oops.txt ksymoops 2.4.0 on i686 2.4.7-pre8-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.7-pre8-xfs/ (default) -m /boot/System.map-2.4.7-pre8-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. Error (expand_objects): cannot stat(/lib/3w-xxxx.o) for 3w-xxxx ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod ksymoops: No such file or directory Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/cdrom/driver.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/char/drm/drm.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/media/radio/radio.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/media/video/video.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/media/media.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/misc/misc.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/net/appletalk/appletalk.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/net/fc/fc.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/net/pcmcia/pcmcia_net.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/net/tokenring/tr.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/net/wan/wan.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/net/wireless/wireless_net.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/parport/driver.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/drivers/sound/sounddrivers.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/net/ipv4/netfilter/netfilter.o Warning (read_object): no symbols in /lib/modules/2.4.7-pre8-xfs/build/net/ipv6/netfilter/netfilter.o Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c022d800, System.map says c01596f0. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol nlmsvc_grace_period , lockd says f8965234, /lib/modules/2.4.7-pre8-xfs/kernel/fs/lockd/lockd.o says f8964664. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/fs/lockd/lockd.o entry Warning (compare_maps): mismatch on symbol nlmsvc_ops , lockd says f8965230, /lib/modules/2.4.7-pre8-xfs/kernel/fs/lockd/lockd.o says f8964660. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/fs/lockd/lockd.o entry Warning (compare_maps): mismatch on symbol nlmsvc_timeout , lockd says f8965238, /lib/modules/2.4.7-pre8-xfs/kernel/fs/lockd/lockd.o says f8964668. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/fs/lockd/lockd.o entry Warning (compare_maps): mismatch on symbol nfs_debug , sunrpc says f8953c60, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f8953920. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol nfsd_debug , sunrpc says f8953c64, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f8953924. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol nlm_debug , sunrpc says f8953c68, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f8953928. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_debug , sunrpc says f8953c5c, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f895391c. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_garbage_args , sunrpc says f8953c3c, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f89538fc. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_success , sunrpc says f8953c2c, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f89538ec. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_system_err , sunrpc says f8953c40, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f8953900. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol xdr_one , sunrpc says f8953c24, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f89538e4. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol xdr_two , sunrpc says f8953c28, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f89538e8. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol xdr_zero , sunrpc says f8953c20, /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o says f89538e0. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/net/sunrpc/sunrpc.o entry Warning (map_ksym_to_module): cannot match loaded module 3w-xxxx to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module sd_mod to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module scsi_mod to a unique module object. Trace may not be reliable. Jul 19 19:24:14 sheridan kernel: Unable to handle kernel paging request at virtual address abdcee80 Jul 19 19:24:14 sheridan kernel: c023637c Jul 19 19:24:14 sheridan kernel: *pde = 00000000 Jul 19 19:24:14 sheridan kernel: Oops: 0002 Jul 19 19:24:14 sheridan kernel: CPU: 1 Jul 19 19:24:14 sheridan kernel: EIP: 0010:[alloc_skb+332/456] Jul 19 19:24:14 sheridan kernel: EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Jul 19 19:24:14 sheridan kernel: EFLAGS: 00010282 Jul 19 19:24:14 sheridan kernel: eax: abdcee80 ebx: ed5db480 ecx: abdcc000 edx: dc216c80 Jul 19 19:24:14 sheridan kernel: esi: 000000f0 edi: 00002f20 ebp: d3db6000 esp: d3db7eb4 Jul 19 19:24:14 sheridan kernel: ds: 0018 es: 0018 ss: 0018 Jul 19 19:24:14 sheridan kernel: Process rsync (pid: 8028, stackpage=d3db7000) Jul 19 19:24:14 sheridan kernel: Stack: d867fa40 00000000 00002e7c 00000002 00000000 c02358c1 00002e80 000000f0 Jul 19 19:24:14 sheridan kernel: d864ceec 00002e7c d67c7134 d67c70e0 d3db6000 c0279ab2 d867fa40 00002e7c Jul 19 19:24:14 sheridan kernel: 00000040 d3db7f1c d864ceec d3db7f84 c02799a0 d864ceec c0130fc4 00000000 Jul 19 19:24:14 sheridan kernel: Call Trace: [sock_alloc_send_skb+113/264] [unix_stream_sendmsg+274/828] [unix_stream_sendmsg+0/828] [free_pages+36/40] [sock_sendmsg+129/164] [unix_stream_sendmsg+0/828] [sock_write+163/172] Jul 19 19:24:14 sheridan kernel: Call Trace: [] [] [] [] [] [] [] Jul 19 19:24:14 sheridan kernel: [] [] Jul 19 19:24:14 sheridan kernel: Code: c7 00 01 00 00 00 8b 83 88 00 00 00 c7 40 04 00 00 00 00 8b >>EIP; c023637c <===== Trace; c02358c1 Trace; c0279ab2 Trace; c02799a0 Trace; c0130fc4 Trace; c023315d Trace; c02799a0 Trace; c023337b Trace; c013768a Trace; c0106fcb Code; c023637c 00000000 <_EIP>: Code; c023637c <===== 0: c7 00 01 00 00 00 movl $0x1,(%eax) <===== Code; c0236382 6: 8b 83 88 00 00 00 mov 0x88(%ebx),%eax Code; c0236388 c: c7 40 04 00 00 00 00 movl $0x0,0x4(%eax) Code; c023638f 13: 8b 00 mov (%eax),%eax Jul 19 19:45:10 sheridan kernel: Unable to handle kernel paging request at virtual address 3d537020 Jul 19 19:45:10 sheridan kernel: c023637c Jul 19 19:45:10 sheridan kernel: *pde = 00000000 Jul 19 19:45:10 sheridan kernel: Oops: 0002 Jul 19 19:45:10 sheridan kernel: CPU: 0 Jul 19 19:45:10 sheridan kernel: EIP: 0010:[alloc_skb+332/456] Jul 19 19:45:10 sheridan kernel: EIP: 0010:[] Jul 19 19:45:10 sheridan kernel: EFLAGS: 00010202 Jul 19 19:45:10 sheridan kernel: eax: 3d537020 ebx: f200e320 ecx: 3d534000 edx: dc216c80 Jul 19 19:45:10 sheridan kernel: esi: 000000f0 edi: 000030c0 ebp: f604c000 esp: f604deb4 Jul 19 19:45:10 sheridan kernel: ds: 0018 es: 0018 ss: 0018 Jul 19 19:45:10 sheridan kernel: Process rsync (pid: 8102, stackpage=f604d000) Jul 19 19:45:10 sheridan kernel: Stack: f74140e0 00000000 00003008 00000002 00000202 c02358c1 00003020 000000f0 Jul 19 19:45:10 sheridan kernel: eda6954c 00003008 f751f5d4 f751f580 f604c000 c0279ab2 f74140e0 00003008 Jul 19 19:45:10 sheridan kernel: 00000040 f604df1c eda6954c f604df84 c02799a0 eda6954c c0130fc4 00000000 Jul 19 19:45:10 sheridan kernel: Call Trace: [sock_alloc_send_skb+113/264] [unix_stream_sendmsg+274/828] [unix_stream_sendmsg+0/828] [free_pages+36/40] [sock_sendmsg+129/164] [unix_stream_sendmsg+0/828] [sock_write+163/172] Jul 19 19:45:10 sheridan kernel: Call Trace: [] [] [] [] [] [] [] Jul 19 19:45:10 sheridan kernel: [] [] Jul 19 19:45:10 sheridan kernel: Code: c7 00 01 00 00 00 8b 83 88 00 00 00 c7 40 04 00 00 00 00 8b >>EIP; c023637c <===== Trace; c02358c1 Trace; c0279ab2 Trace; c02799a0 Trace; c0130fc4 Trace; c023315d Trace; c02799a0 Trace; c023337b Trace; c013768a Trace; c0106fcb Code; c023637c 00000000 <_EIP>: Code; c023637c <===== 0: c7 00 01 00 00 00 movl $0x1,(%eax) <===== Code; c0236382 6: 8b 83 88 00 00 00 mov 0x88(%ebx),%eax Code; c0236388 c: c7 40 04 00 00 00 00 movl $0x0,0x4(%eax) Code; c023638f 13: 8b 00 mov (%eax),%eax 34 warnings and 3 errors issued. Results may not be reliable. 4) I umount both filesystems and run xfs_repair -n on them #xfs_repair -n /dev/md0 Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 <...> - agno = 107 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 <...> - agno = 107 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem starting at / ... - traversal finished ... - traversing all unattached subtrees ... - traversals finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. # xfs_repair -n /dev/sda1 Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 <...> - agno = 17 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 <...> - agno = 17 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem starting at / ... - traversal finished ... - traversing all unattached subtrees ... - traversals finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. 5) I could remount the plain xfs partition but not the raid5 array:( # mount /raid5/ mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many mounted file systems on the syslog file: Jul 19 20:16:56 nfs kernel: XFS: xlog_recover_reorder_trans: unrecognized type of log operation Any idea what are the next steps? Regards, Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 11:54:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JIsFA10171 for linux-xfs-outgoing; Thu, 19 Jul 2001 11:54:15 -0700 Received: from biobio.vexcel.com (biobio.vexcel.com [192.92.90.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JIsBV10133 for ; Thu, 19 Jul 2001 11:54:12 -0700 Received: from [192.168.1.17] (router.vexcel.com [192.92.90.254]) by biobio.vexcel.com (8.9.3+Sun/8.9.1) with ESMTP id MAA11367 for ; Thu, 19 Jul 2001 12:54:03 -0600 (MDT) Mime-Version: 1.0 X-Sender: brissing@mail.vexcel.com (Unverified) Message-Id: In-Reply-To: <200107191617.f6JGHwk32337@jen.americas.sgi.com> References: <200107191617.f6JGHwk32337@jen.americas.sgi.com> Date: Thu, 19 Jul 2001 12:48:31 -0600 To: "linux-xfs@oss.sgi.com" From: Dean Brissinger Subject: 1.0.1 on 2.4.6 RPMs Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Does anyone have RPMs built of the new kernel and 1.0.1 XFS? I didn't find anyon the web site. From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:02:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJ2Pk13118 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:02:25 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJ2MV13080 for ; Thu, 19 Jul 2001 12:02:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA560580 for ; Thu, 19 Jul 2001 21:02:07 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2475147; Thu, 19 Jul 2001 14:00:51 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA77221; Thu, 19 Jul 2001 14:00:43 -0500 (CDT) Subject: Re: 1.0.1 on 2.4.6 RPMs From: Eric Sandeen To: Dean Brissinger Cc: "linux-xfs@oss.sgi.com" In-Reply-To: References: <200107191617.f6JGHwk32337@jen.americas.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 19 Jul 2001 14:00:27 -0500 Message-Id: <995569228.13407.3.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 19 Jul 2001 12:48:31 -0600, Dean Brissinger wrote: > Does anyone have RPMs built of the new kernel and 1.0.1 XFS? I > didn't find anyon the web site. We don't currently have 1.0.1 available for 2.4.6, and probably won't in the future... I was merging the 2.4.6 changes into the 1.0.1 tree, but the underlying changes for the kernel required some changes to the XFS code - which makes it not "XFS 1.0.1" anymore. :) There is a 2.4.6 patch in the patches/ directory, though, which is a development snapshot after the 2.4.6 merge. Several people are using it. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:12:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJCc115432 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:12:38 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJCZV15413 for ; Thu, 19 Jul 2001 12:12:35 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA03574 for ; Thu, 19 Jul 2001 12:12:24 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2469439; Thu, 19 Jul 2001 14:11:17 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA68156; Thu, 19 Jul 2001 14:11:17 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6JJC6A00707; Thu, 19 Jul 2001 14:12:06 -0500 Message-Id: <200107191912.f6JJC6A00707@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh cc: "linux-xfs@oss.sgi.com" Subject: Re: oops 2.4.7pre8 + xlog_recover_reorder_trans: unrecognized type of log operation (long) In-Reply-To: Message from Tru Huynh of "Thu, 19 Jul 2001 20:35:58 +0200." <3B57288E.83685922@pasteur.fr> Date: Thu, 19 Jul 2001 14:12:06 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > > Here is what I have done. I might have been stupic :| > Well, your rsync appears to have died in the socket code, not xfs.... I am not sure we can help with that one. > 4) I umount both filesystems and run xfs_repair -n on them > > #xfs_repair -n /dev/md0 > Phase 1 - find and verify superblock... > Phase 2 - using internal log > - scan filesystem freespace and inode maps... > - found root inode chunk > Phase 3 - for each AG... > - scan (but don't clear) agi unlinked lists... > - process known inodes and perform inode discovery... > - agno = 0 > - agno = 1 > <...> > - agno = 107 > - process newly discovered inodes... > Phase 4 - check for duplicate blocks... > - setting up duplicate extent list... > - check for inodes claiming duplicate blocks... > - agno = 0 > <...> > - agno = 107 > No modify flag set, skipping phase 5 > Phase 6 - check inode connectivity... > - traversing filesystem starting at / ... > - traversal finished ... > - traversing all unattached subtrees ... > - traversals finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify link counts... > No modify flag set, skipping filesystem flush and exiting. > > # xfs_repair -n /dev/sda1 > Phase 1 - find and verify superblock... > Phase 2 - using internal log > - scan filesystem freespace and inode maps... > - found root inode chunk > Phase 3 - for each AG... > - scan (but don't clear) agi unlinked lists... > - process known inodes and perform inode discovery... > - agno = 0 > <...> > - agno = 17 > - process newly discovered inodes... > Phase 4 - check for duplicate blocks... > - setting up duplicate extent list... > - check for inodes claiming duplicate blocks... > - agno = 0 > <...> > - agno = 17 > No modify flag set, skipping phase 5 > Phase 6 - check inode connectivity... > - traversing filesystem starting at / ... > - traversal finished ... > - traversing all unattached subtrees ... > - traversals finished ... > - moving disconnected inodes to lost+found ... > Phase 7 - verify link counts... > No modify flag set, skipping filesystem flush and exiting. > > 5) I could remount the plain xfs partition but not the raid5 array:( > # mount /raid5/ > mount: wrong fs type, bad option, bad superblock on /dev/md0, > or too many mounted file systems > > on the syslog file: > Jul 19 20:16:56 nfs kernel: XFS: xlog_recover_reorder_trans: > unrecognized type of log > operation This error means it found something in the log which is could not understand. If you had actually run repair without the -n option then it would have zeroed out the log and you would never have seen this, that may be your only way of mounting the filesystem from here, however before you do so, could you run: xfs_logprint -t -b -i /dev/md0 if it core dumps try adding the -e option. and xfs_check /dev/md0 and send me the output. Steve > > > > Any idea what are the next steps? > > Regards, > > Tru > -- > Dr Tru Huynh | Bioinformatique Structurale > mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 > Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:13:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJDNC15489 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:13:23 -0700 Received: from drama.koli (mail@drama.obuda.kando.hu [193.224.41.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJDKV15470 for ; Thu, 19 Jul 2001 12:13:21 -0700 Received: from feczo by drama.koli with local (Exim 3.22 #1 (Debian)) id 15NJE7-0000Gh-00; Thu, 19 Jul 2001 21:12:47 +0200 Date: Thu, 19 Jul 2001 21:12:47 +0200 From: Feczak Szabolcs To: linux-xfs@oss.sgi.com, SmartList Subject: Fwd: [Re: Kernelbug] Message-ID: <20010719211247.A964@koli.kando.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Please cc me if you answer, I'm not on the list ... The kernel was compiled from todays cvs. ----- Forwarded message from Andi Kleen ----- Date: Thu, 19 Jul 2001 19:21:49 +0200 From: Andi Kleen Subject: Re: Kernelbug To: Andrea Arcangeli Cc: Feczak Szabolcs , axboe@suse.de, Andi Kleen On Thu, Jul 19, 2001 at 07:18:42PM +0200, Andrea Arcangeli wrote: > On Thu, Jul 19, 2001 at 06:27:13PM +0200, Feczak Szabolcs wrote: > > Hi major problem, with these: > > > > Linux drama 2.4.7-pre8-xfs #1 Thu Jul 19 16:53:25 CEST 2001 i686 unknown > > > > Please investigate > > sounds like a bug in xfs, I'm not involved with xfs developement but > maybe Andi is interested. Please send XFS bugs to the linux-xfs@oss.sgi.com list. You'll also need to run them through ksymoops so that someone can make sense of them. -Andi > > > > > kernel BUG at ll_rw_blk.c:1024! > > invalid operand: 0000 > > CPU: 0 > > EIP: 0010:[] > > EFLAGS: 00010286 > > eax: 00000020 ebx: c54955e0 ecx: c537c000 edx: c4b9f2c0 > > esi: 00000000 edi: 00000200 ebp: 00000001 esp: c537dce8 > > ds: 0018 es: 0018 ss: 0018 > > Process exim (pid: 1035, stackpage=c537d000) > > Stack: c02df377 c02df5c2 00000400 c54955e0 c5487f00 c54955e0 00000000 00001000 > > 00000001 ffffffff c7ecfd58 00000286 c0326a14 c0326ba0 c012f41e 00000001 > > 00000001 c537dd40 c54955e0 00000001 c032aa40 c3b73428 c5487f00 c4b9f2c0 > > Call Trace: [] [] [] [] [] [] [] > > [] [] [] [] [] [] [] [] > > [] [] [] [] [] [] [] [] > > [] > > > > Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c > > kernel BUG at ll_rw_blk.c:1024! > > invalid operand: 0000 > > CPU: 0 > > EIP: 0010:[] > > EFLAGS: 00010286 > > eax: 00000020 ebx: c5487f00 ecx: c12dc000 edx: 00000000 > > esi: 00000000 edi: 00000200 ebp: 00000001 esp: c12ddf78 > > ds: 0018 es: 0018 ss: 0018 > > Process kupdated (pid: 7, stackpage=c12dd000) > > Stack: c02df377 c02df5c2 00000400 c5487f00 00000017 c727de00 00000000 00001000 > > c12dc23b c01d631d 00000282 c032775c c55a1440 c7171258 c013124a 00000001 > > 00000001 c12ddfd4 c12dc000 c02c1e17 c12dc23b 0006e000 c12dc000 c5487f00 > > Call Trace: [] [] [] [] [] > > > > Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c > > > > Thanks for your time. > > > > Feczo > > > Andrea ----- End forwarded message ----- From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:23:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJNES15885 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:23:14 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJNCV15866 for ; Thu, 19 Jul 2001 12:23:12 -0700 Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA05867 for ; Thu, 19 Jul 2001 12:23:01 -0700 (PDT) mail_from (roehrich@clink-eth.americas.sgi.com) Received: from clink-eth.americas.sgi.com ([128.162.2.8]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f6JJMAf31227009 for ; Thu, 19 Jul 2001 12:22:10 -0700 (PDT) Received: (from roehrich@localhost) by clink-eth.americas.sgi.com (SGI-8.9.3/8.9.3) id OAA57819 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 14:20:53 -0500 (CDT) Date: Thu, 19 Jul 2001 14:20:53 -0500 (CDT) From: Dean Roehrich Message-Id: <200107191920.OAA57819@clink-eth.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - implement xfs_fssetdm_by_handle, to restore DMAPI event masks Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is used by xfsrestore to restore DMAPI event masks. Date: Thu Jul 19 12:18:54 PDT 2001 Workarea: clink-eth.americas.sgi.com:/data/clink/a/roehrich/2.4.x-xfsB The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99214a linux/include/linux/xfs_fs.h - 1.26 linux/fs/xfs/linux/xfs_ioctl.c - 1.43 - implement xfs_fssetdm_by_handle From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:26:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJQbP16046 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:26:37 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJQYV16027 for ; Thu, 19 Jul 2001 12:26:34 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA571627 for ; Thu, 19 Jul 2001 21:26:18 +0200 (CEST) mail_from (florin@sgi.com) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA36771 for ; Thu, 19 Jul 2001 12:31:04 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id E726B15A472 for ; Thu, 19 Jul 2001 12:25:14 -0700 (PDT) Subject: Re: noapic strikes back From: Florin Andrei To: linux-xfs@oss.sgi.com In-Reply-To: <3B55E7A8.1786F70A@redhat.com> References: <995484908.1279.0.camel@stantz.corp.sgi.com> <3B55E7A8.1786F70A@redhat.com> Content-Type: text/plain X-Mailer: Evolution/0.10 (Preview Release) Date: 19 Jul 2001 12:25:14 -0700 Message-Id: <995570714.1458.0.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 18 Jul 2001 15:46:48 -0400, Doug Ledford wrote: > > When using my boot disk, you have to use the "apic" option, not the "noapic" > option. This also works for SGI XFS-1.0.1 on a SGI 1200 server. So, this is my bad. Sorry. :-( -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:29:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJTSn16191 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:29:28 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJTQV16172 for ; Thu, 19 Jul 2001 12:29:26 -0700 Received: from clink-eth.americas.sgi.com (clink-eth.americas.sgi.com [128.162.2.8]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA07689 for ; Thu, 19 Jul 2001 12:27:00 -0700 (PDT) mail_from (roehrich@clink-eth.americas.sgi.com) Received: (from roehrich@localhost) by clink-eth.americas.sgi.com (SGI-8.9.3/8.9.3) id OAA13835 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 14:28:07 -0500 (CDT) Date: Thu, 19 Jul 2001 14:28:07 -0500 (CDT) From: Dean Roehrich Message-Id: <200107191928.OAA13835@clink-eth.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - fix up DMAPI/DMF stuff in xfsdump/xfsrestore Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Thu Jul 19 12:26:28 PDT 2001 Workarea: clink-eth.americas.sgi.com:/data/clink/a/roehrich/2.4.x-xfsB The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99215a cmd/xfsdump/restore/tree.c - 1.6 - Turn on the dmapi stuff. cmd/xfsdump/common/main.c - 1.5 - correct the DMAPI/DMF-related help for xfsdump/xfsrestore cmd/xfsdump/common/attr.c - 1.3 - add header cmd/xfsdump/restore/content.c - 1.11 - Turn on the dmapi stuff. Establish a filesystem handle for the destination dir, so libhandle is happy. cmd/xfsdump/man/man8/xfsdump.8 - 1.6 - remove comment about -a not being supported. cmd/xfsprogs/include/handle.h - 1.3 - add prototype for fssetdm_by_handle(). cmd/xfsprogs/include/xfs_fs.h - 1.7 - match for linux/include/linux/xfs_fs.h cmd/xfsprogs/libhandle/handle.c - 1.5 - implement fssetdm_by_handle() cmd/dmapi/libdm/dm_handle2path.c - 1.5 - add header From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:31:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJVk616347 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:31:46 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJVaV16327 for ; Thu, 19 Jul 2001 12:31:36 -0700 Received: from drama.koli (drama.obuda.kando.hu [193.224.41.14]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA07547 for ; Thu, 19 Jul 2001 12:31:24 -0700 (PDT) mail_from (feczo@koli.kando.hu) Received: from feczo by drama.koli with local (Exim 3.22 #1 (Debian)) id 15NJLz-0000My-00 for ; Thu, 19 Jul 2001 21:20:55 +0200 Date: Thu, 19 Jul 2001 21:20:55 +0200 From: Feczak Szabolcs To: linux-xfs@oss.sgi.com Subject: ksymoops result Message-ID: <20010719212055.B964@koli.kando.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Please cc me, if you answer. Thanks. ----- Forwarded message ------------------------------------------------- ksymoops 2.4.1 on i686 2.4.7-pre8-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.7-pre8-xfs/ (default) -m /boot/System.map-2.4.7-pre8-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. Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c0253b40, System.map says c014bd60. Ignoring ksyms_base entry Warning: buffer 0xc49841e0 with weird blockno (0) Warning: buffer 0xc49841e0 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010286 eax: 00000020 ebx: c4dacc20 ecx: c6d5a000 edx: c0325684 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c440bce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 484, stackpage=c440b000) Stack: c02df377 c02df5c2 00000400 c4dacc20 c49841e0 c4dacc20 00000000 00001000 c1134650 c01e26e0 c012e654 c1134650 c4dacc20 c48b2f60 c012f41e 00000001 00000001 c440bd40 c4dacc20 00000001 c032aa40 c4da62b4 c49841e0 c79d21c0 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c01e26e0 Trace; c012e654 <_write_buffer+74/c8> Trace; c012f41e Trace; c012f97a Trace; c0128b1a Trace; c012f65b Trace; c012f697 Trace; c0177162 Trace; c017754d <__pb_block_commit_write_async+45/4c> Trace; c017764c <__pagebuf_do_delwri+f8/22c> Trace; c01776ee <__pagebuf_do_delwri+19a/22c> Trace; c01778b7 <_pagebuf_file_write+137/1f0> Trace; c0121259 <__find_lock_page+41/b0> Trace; c0177bee Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c49841e0 ecx: c12dc000 edx: 00000000 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c12ddf78 ds: 0018 es: 0018 ss: 0018 Process kupdated (pid: 7, stackpage=c12dd000) Stack: c02df377 c02df5c2 00000400 c49841e0 00000017 c48b2f00 00000000 00001000 c12dc23b c01d631d 00000286 c032775c c6f69dc0 c6f66658 c013124a 00000001 00000001 c12ddfd4 c12dc000 c02c1e17 c12dc23b 0006e000 c12dc000 c49841e0 Call Trace: [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c01d631d Trace; c013124a Trace; c01312e2 Trace; c0131535 Trace; c010544c Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc5358e40 with weird blockno (0) Warning: buffer 0xc5358e40 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c3963440 ecx: c49b8000 edx: c79d2440 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c49b9ce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 603, stackpage=c49b9000) Stack: c02df377 c02df5c2 00000400 c3963440 c5358e40 c3963440 00000000 00001000 c11524f8 c01e26e0 c012e654 c11524f8 c3963440 c4d56b40 c012f41e 00000001 00000001 c49b9d40 c3963440 00000001 c032aa40 c546ad6c c5358e40 c79d2440 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c01e26e0 Trace; c012e654 <_write_buffer+74/c8> Trace; c012f41e Trace; c011eb5b Trace; c012f97a Trace; c0128b1a Trace; c012f65b Trace; c012f697 Trace; c0177162 Trace; c017754d <__pb_block_commit_write_async+45/4c> Trace; c017764c <__pagebuf_do_delwri+f8/22c> Trace; c01776ee <__pagebuf_do_delwri+19a/22c> Trace; c01778b7 <_pagebuf_file_write+137/1f0> Trace; c0121259 <__find_lock_page+41/b0> Trace; c0177bee Trace; c01c4733 Trace; c01bff11 Trace; c01c007b Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc4408e60 with weird blockno (0) Warning: buffer 0xc4408e60 with weird blockno (0) Warning: buffer 0xc4408e60 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c5a3d060 ecx: c516e000 edx: c7a0ad20 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c516fce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 608, stackpage=c516f000) Stack: c02df377 c02df5c2 00000400 c5a3d060 c4408e60 c5a3d060 00000000 00001000 00000001 ffffffff c7ee4558 00000286 c0326a14 c0326ba0 c012f41e 00000001 00000001 c516fd40 c5a3d060 00000001 c032aa40 c3e31b38 c4408e60 c7a0ad20 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c012f41e Trace; c011eb5b Trace; c011f14d Trace; c01f867b Trace; c024d6b7 Trace; c01f918e Trace; c01fc48e Trace; c0113260 Trace; c017724b Trace; c017726a Trace; c0177533 <__pb_block_commit_write_async+2b/4c> Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc49bf540 with weird blockno (0) Warning: buffer 0xc49bf540 with weird blockno (0) Warning: buffer 0xc49bf540 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c489a240 ecx: c4f46000 edx: c79d2740 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c4f47ce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 726, stackpage=c4f47000) Stack: c02df377 c02df5c2 00000400 c489a240 c49bf540 c489a240 00000000 00001000 c0372b60 00000013 c4f47d2c 00000046 c0107f6d c1132a28 c012f41e 00000001 00000001 c4f47d40 c489a240 00000001 c032aa40 c4f4163c c49bf540 c4826064 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c0107f6d Trace; c012f41e Trace; c011eb5b Trace; c011f14d Trace; c01f867b Trace; c024d6b7 Trace; c01f918e Trace; c01fc48e Trace; c0113260 Trace; c017724b Trace; c017726a Trace; c0177533 <__pb_block_commit_write_async+2b/4c> Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc48b2180 with weird blockno (0) Warning: buffer 0xc48b2180 with weird blockno (0) Warning: buffer 0xc48b2180 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c48b4280 ecx: c4f1c000 edx: c79d2140 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c4f1dce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 750, stackpage=c4f1d000) Stack: c02df377 c02df5c2 00000400 c48b4280 c48b2180 c48b4280 00000000 00001000 c7bee414 00000000 00000001 00000286 c0326a14 c0326ba0 c012f41e 00000001 00000001 c4f1dd40 c48b4280 00000001 c032aa40 c4f3ca04 c48b2180 c79d2140 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c012f41e Trace; c011eb5b Trace; c011f14d Trace; c01f867b Trace; c024d6b7 Trace; c01f918e Trace; c01fc48e Trace; c0113260 Trace; c017724b Trace; c017726a Trace; c0177533 <__pb_block_commit_write_async+2b/4c> Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc48b2240 with weird blockno (0) Warning: buffer 0xc48b2240 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c48a72c0 ecx: c4fa6000 edx: c79d21c0 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c4fa7ce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 778, stackpage=c4fa7000) Stack: c02df377 c02df5c2 00000400 c48a72c0 c48b2240 c48a72c0 00000000 00001000 c114f89c c01e26e0 c012e654 c114f89c c48a72c0 c490c440 c012f41e 00000001 00000001 c4fa7d40 c48a72c0 00000001 c032aa40 c4f3c0e0 c48b2240 c79d21c0 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c01e26e0 Trace; c012e654 <_write_buffer+74/c8> Trace; c012f41e Trace; c012f97a Trace; c0128b1a Trace; c012f65b Trace; c012f697 Trace; c0177162 Trace; c017754d <__pb_block_commit_write_async+45/4c> Trace; c017764c <__pagebuf_do_delwri+f8/22c> Trace; c01776ee <__pagebuf_do_delwri+19a/22c> Trace; c01778b7 <_pagebuf_file_write+137/1f0> Trace; c0121259 <__find_lock_page+41/b0> Trace; c0177bee Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc424bde0 with weird blockno (0) Warning: buffer 0xc424bde0 with weird blockno (0) Warning: buffer 0xc424bde0 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c3bf00e0 ecx: c4b4a000 edx: c79d2340 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c4b4bce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 911, stackpage=c4b4b000) Stack: c02df377 c02df5c2 00000400 c3bf00e0 c424bde0 c3bf00e0 00000000 00001000 c1381414 00000000 c4b4bde0 c41be4c0 c41be590 c03a6720 c012f41e 00000001 00000001 c4b4bd40 c3bf00e0 00000001 c032aa40 c3bfd7b0 c424bde0 00000004 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c012f41e Trace; c029609f Trace; c026ae83 Trace; c0264cc3 Trace; c02726fd Trace; c026a51e Trace; c027264d Trace; c0272668 Trace; c027034a Trace; c026a51e Trace; c02702a6 Trace; c0270300 Trace; c026f730 Trace; c026a51e Trace; c026f411 Trace; c026f5b8 Trace; c026520d Trace; c011692a Trace; c0107f6d Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc490c2c0 with weird blockno (0) Warning: buffer 0xc490c2c0 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c48c9220 ecx: c51ee000 edx: c79d21c0 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c51efce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 950, stackpage=c51ef000) Stack: c02df377 c02df5c2 00000400 c48c9220 c490c2c0 c48c9220 00000000 00001000 c115682c c01e26e0 c012e654 c115682c c48c9220 c4e1e840 c012f41e 00000001 00000001 c51efd40 c48c9220 00000001 c032aa40 c4a2fd0c c490c2c0 c3e26860 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c01e26e0 Trace; c012e654 <_write_buffer+74/c8> Trace; c012f41e Trace; c011f00b Trace; c012f97a Trace; c0128b1a Trace; c012f65b Trace; c012f697 Trace; c0177162 Trace; c017754d <__pb_block_commit_write_async+45/4c> Trace; c017764c <__pagebuf_do_delwri+f8/22c> Trace; c01776ee <__pagebuf_do_delwri+19a/22c> Trace; c01778b7 <_pagebuf_file_write+137/1f0> Trace; c0121259 <__find_lock_page+41/b0> Trace; c0177bee Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc4408ec0 with weird blockno (0) Warning: buffer 0xc4408ec0 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c488ddc0 ecx: c306c000 edx: c79d29c0 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c306dce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 1121, stackpage=c306d000) Stack: c02df377 c02df5c2 00000400 c488ddc0 c4408ec0 c488ddc0 00000000 00001000 c10c6acc c01e26e0 c012e654 c10c6acc c488ddc0 c24ffe00 c012f41e 00000001 00000001 c306dd40 c488ddc0 00000001 c032aa40 c4fa1d2c c4408ec0 c4cca9a0 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c01e26e0 Trace; c012e654 <_write_buffer+74/c8> Trace; c012f41e Trace; c011f00b Trace; c012f97a Trace; c0128b1a Trace; c012f65b Trace; c012f697 Trace; c0177162 Trace; c017754d <__pb_block_commit_write_async+45/4c> Trace; c017764c <__pagebuf_do_delwri+f8/22c> Trace; c01776ee <__pagebuf_do_delwri+19a/22c> Trace; c01778b7 <_pagebuf_file_write+137/1f0> Trace; c0121259 <__find_lock_page+41/b0> Trace; c0177bee Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 Warning: buffer 0xc4408c20 with weird blockno (0) Warning: buffer 0xc4408c20 with weird blockno (0) Warning: buffer 0xc4408c20 with weird blockno (0) kernel BUG at ll_rw_blk.c:1024! invalid operand: 0000 CPU: 0 EIP: 0010:[] EFLAGS: 00010286 eax: 00000020 ebx: c4f6c840 ecx: c2560000 edx: c7a0ac20 esi: 00000000 edi: 00000200 ebp: 00000001 esp: c2561ce8 ds: 0018 es: 0018 ss: 0018 Process exim (pid: 1208, stackpage=c2561000) Stack: c02df377 c02df5c2 00000400 c4f6c840 c4408c20 c4f6c840 00000000 00001000 00000001 ffffffff c7bc3558 00000286 c0326a14 c0326ba0 c012f41e 00000001 00000001 c2561d40 c4f6c840 00000001 c032aa40 c5362a44 c4408c20 c7a0ac20 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 83 c4 0c 46 3b 74 24 34 7c b7 f7 c5 01 00 00 00 74 3c >>EIP; c0204820 <===== Trace; c012f41e Trace; c011eb5b Trace; c011f14d Trace; c01f867b Trace; c01f9118 Trace; c01f9199 Trace; c01fc48e Trace; c0113260 Trace; c017724b Trace; c017726a Trace; c0177533 <__pb_block_commit_write_async+2b/4c> Trace; c01c4733 Trace; c01bff11 Trace; c01d32ce Trace; c01d32ce Trace; c01c007b Trace; c01dc484 Trace; c01e3cbf Trace; c01764f7 Trace; c01dfa5c Trace; c01d83ee Trace; c01df595 Trace; c012eb1f Trace; c0106aeb Code; c0204820 00000000 <_EIP>: Code; c0204820 <===== 0: 0f 0b ud2a <===== Code; c0204822 2: 83 c4 0c add $0xc,%esp Code; c0204825 5: 46 inc %esi Code; c0204826 6: 3b 74 24 34 cmp 0x34(%esp,1),%esi Code; c020482a a: 7c b7 jl ffffffc3 <_EIP+0xffffffc3> c02047e3 Code; c020482c c: f7 c5 01 00 00 00 test $0x1,%ebp Code; c0204832 12: 74 3c je 50 <_EIP+0x50> c0204870 2 warnings issued. Results may not be reliable. ----- End forwarded message ----- From owner-linux-xfs@oss.sgi.com Thu Jul 19 12:42:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JJgT916798 for linux-xfs-outgoing; Thu, 19 Jul 2001 12:42:29 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JJgPV16777 for ; Thu, 19 Jul 2001 12:42:26 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id VAA11669 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 21:42:29 +0200 Date: Thu, 19 Jul 2001 21:42:28 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: linux-xfs@oss.sgi.com Subject: Busy inodes after umount Message-ID: <20010719214228.A11236@vestdata.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk [root@ha2 /root]# mkfs -t xfs -f /dev/sdb1 meta-data=/dev/sdb1 isize=256 agcount=51, agsize=262144 blks data = bsize=4096 blocks=13305828, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=1624 realtime =none extsz=65536 blocks=0, rtextents=0 [root@ha2 /root]# mount -t xfs /dev/sdb1 /mnt/raid/ [root@ha2 /root]# umount /mnt/raid/ [root@ha2 /root]# mount -t xfs /dev/sdb1 /mnt/raid/ mount: wrong fs type, bad option, bad superblock on /dev/sdb1, or too many mounted file systems >From /var/log/messages: Jul 19 12:27:15 ha2 kernel: Start mounting filesystem: sd(8,17) Jul 19 12:27:16 ha2 kernel: Ending clean XFS mount for filesystem: sd(8,17) Jul 19 12:27:19 ha2 kernel: XFS unmount got error 16 Jul 19 12:27:19 ha2 kernel: linvfs_put_super: vfsp/0xc2ff71e0 left dangling! Jul 19 12:27:19 ha2 kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... Jul 19 12:27:21 ha2 kernel: XFS: Filesystem has duplicate UUID - can't mount This happens on a shared storage cluster with two nodes. The same thing happens on both nodes. (I'm only using the device from one device at the time) linux-2.4.5 with XFS patch from 06112001. After a reboot it works again, and I have not been able to reproduce yet. It first happened when I was testing NFS locks, so it could be related to that. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:03:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JK34g17533 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:03:04 -0700 Received: from biobio.vexcel.com (biobio.vexcel.com [192.92.90.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JK31V17514 for ; Thu, 19 Jul 2001 13:03:01 -0700 Received: from [192.168.1.17] (router.vexcel.com [192.92.90.254]) by biobio.vexcel.com (8.9.3+Sun/8.9.1) with ESMTP id OAA13562 for ; Thu, 19 Jul 2001 14:02:54 -0600 (MDT) Mime-Version: 1.0 X-Sender: brissing@mail.vexcel.com (Unverified) Message-Id: In-Reply-To: <3B39F478.77AEA2B@sgi.com> References: <17376.993612424@kao2.melbourne.sgi.com> <3B395DED.FDFC6C3D@sgi.com> <20010627011411.A17429@wwweasel.geeksrus.net> <3B39F478.77AEA2B@sgi.com> Date: Thu, 19 Jul 2001 14:02:45 -0600 To: linux-xfs@oss.sgi.com From: Dean Brissinger Subject: unable to open initial console [devfs?] Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I used the 2.4.5/1.0.1 RPM to upgrade my Redhat system (built w/ XFS 1.0 CD). The kernel seems happy but upon booting reports "unable to open initial console". I've seen this before when messing with devfs. It basically means /dev/ is missing device files. I read a while back that this kernel has devfs disabled by default. Is there a trick to get the standard /dev back when upgrading from 1.0 to 1.0.1 RPM's? From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:17:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKHUb18384 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:17:30 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKHSV18365 for ; Thu, 19 Jul 2001 13:17:28 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6JKHN0173135; Thu, 19 Jul 2001 22:17:23 +0200 (CEST) Message-ID: <3B57403E.DF39024A@pasteur.fr> Date: Thu, 19 Jul 2001 22:17:03 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: "linux-xfs@oss.sgi.com" Subject: end: xlog_recover_reorder_trans: unrecognized type of log operation (long) References: <200107191912.f6JJC6A00707@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > <...> > > on the syslog file: > > Jul 19 20:16:56 nfs kernel: XFS: xlog_recover_reorder_trans: > > unrecognized type of log > > operation > > This error means it found something in the log which is could not > understand. If you had actually run repair without the -n option > then it would have zeroed out the log and you would never have > seen this, that may be your only way of mounting the filesystem > from here, xfs_repair fixed the problem :) I could mount the array after. Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:22:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKMHR18689 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:22:17 -0700 Received: from sa-bwmail1.storageapps.com (smtp.storageapps.com [63.101.83.13]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKMFV18665 for ; Thu, 19 Jul 2001 13:22:15 -0700 Received: by SA-BWMAIL1 with Internet Mail Service (5.5.2653.19) id ; Thu, 19 Jul 2001 16:22:09 -0400 Message-ID: <23D04BDBA646D411BDDD00D0B774B53902963BE8@SA-BWMAIL1> From: "Christian, Chip" To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= , linux-xfs@oss.sgi.com Subject: RE: Busy inodes after umount Date: Thu, 19 Jul 2001 16:22:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6JKMFV18668 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I found the same thing happening. Tracked it down in our case to using fdisk to re-read disk size before mounting. Replaced it with "blockdev --readpt" and the problem seems to have gone away. YMMV. -Chip -----Original Message----- From: Ragnar Kjørstad [mailto:xfs@ragnark.vestdata.no] Sent: Thursday, July 19, 2001 15:42 To: linux-xfs@oss.sgi.com Subject: Busy inodes after umount [root@ha2 /root]# mkfs -t xfs -f /dev/sdb1 meta-data=/dev/sdb1 isize=256 agcount=51, agsize=262144 blks data = bsize=4096 blocks=13305828, imaxpct=25 = sunit=0 swidth=0 blks, unwritten=0 naming =version 2 bsize=4096 log =internal log bsize=4096 blocks=1624 realtime =none extsz=65536 blocks=0, rtextents=0 [root@ha2 /root]# mount -t xfs /dev/sdb1 /mnt/raid/ [root@ha2 /root]# umount /mnt/raid/ [root@ha2 /root]# mount -t xfs /dev/sdb1 /mnt/raid/ mount: wrong fs type, bad option, bad superblock on /dev/sdb1, or too many mounted file systems >From /var/log/messages: Jul 19 12:27:15 ha2 kernel: Start mounting filesystem: sd(8,17) Jul 19 12:27:16 ha2 kernel: Ending clean XFS mount for filesystem: sd(8,17) Jul 19 12:27:19 ha2 kernel: XFS unmount got error 16 Jul 19 12:27:19 ha2 kernel: linvfs_put_super: vfsp/0xc2ff71e0 left dangling! Jul 19 12:27:19 ha2 kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... Jul 19 12:27:21 ha2 kernel: XFS: Filesystem has duplicate UUID - can't mount This happens on a shared storage cluster with two nodes. The same thing happens on both nodes. (I'm only using the device from one device at the time) linux-2.4.5 with XFS patch from 06112001. After a reboot it works again, and I have not been able to reproduce yet. It first happened when I was testing NFS locks, so it could be related to that. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:30:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKUXZ19317 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:30:33 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKUUV19292 for ; Thu, 19 Jul 2001 13:30:30 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id WAA580627 for ; Thu, 19 Jul 2001 22:30:14 +0200 (CEST) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id PAA26981; Thu, 19 Jul 2001 15:29:07 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15NKQ0-0004lY-00; Thu, 19 Jul 2001 15:29:08 -0500 Date: Thu, 19 Jul 2001 15:29:08 -0500 From: Nathan Straz To: Dean Brissinger Cc: linux-xfs@oss.sgi.com Subject: Re: unable to open initial console [devfs?] Message-ID: <20010719152908.M701@sgi.com> Mail-Followup-To: Dean Brissinger , linux-xfs@oss.sgi.com References: <17376.993612424@kao2.melbourne.sgi.com> <3B395DED.FDFC6C3D@sgi.com> <20010627011411.A17429@wwweasel.geeksrus.net> <3B39F478.77AEA2B@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 19, 2001 at 02:02:45PM -0600, Dean Brissinger wrote: > I used the 2.4.5/1.0.1 RPM to upgrade my Redhat system (built > w/ XFS 1.0 CD). The kernel seems happy but upon booting reports > "unable to open initial console". I've seen this before when messing > with devfs. It basically means /dev/ is missing device files. I > read a while back that this kernel has devfs disabled by default. Is > there a trick to get the standard /dev back when upgrading from 1.0 > to 1.0.1 RPM's? I went through this pain already. What I ended up doing was booting from a rescue disk, removing the dev package and then installing it again. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:32:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKWJZ19498 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:32:19 -0700 Received: from ente.berdmann.de (pC19F20F0.dip.t-dialin.net [193.159.32.240]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKWFV19478 for ; Thu, 19 Jul 2001 13:32:15 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15NKSv-0004ka-00 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 22:32:09 +0200 Message-ID: <3B5743C9.49891146@berdmann.de> Date: Thu, 19 Jul 2001 22:32:09 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre8-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: 2.4.7-pre8-xfs breaks VMWare Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare can't compile it's modules anymore. Any hint? # vmware-config.pl Making sure VMware's services are stopped. Stopping VMware services: Virtual machine monitor [ OK ] Bridged networking on /dev/vmnet0 [ OK ] DHCP server on /dev/vmnet1 [ OK ] Host-only networking on /dev/vmnet1 [ OK ] Virtual ethernet [ OK ] Trying to find a suitable vmmon module for your running kernel. None of VMware's pre-built vmmon modules is suitable for your running kernel. Do you want this script to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] What is the location of the directory of C header files that match your running kernel? [/lib/modules/2.4.7-pre8-xfs/build/include] Extracting the sources of the vmmon module. Building the vmmon module. make: Entering directory `/tmp/vmware-config3/vmmon-only' make[1]: Entering directory `/tmp/vmware-config3/vmmon-only' make[2]: Entering directory `/tmp/vmware-config3/vmmon-only/driver-2.4.7-pre8-xfs' make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.4.7-pre8-xfs' make[2]: Entering directory `/tmp/vmware-config3/vmmon-only/driver-2.4.7-pre8-xfs' /lib/modules/2.4.7-pre8-xfs/build/include/asm/pgalloc.h: In function `get_pgd_slow': In file included from /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:5, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/pagemap.h:16, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/locks.h:8, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/devfs_fs_kernel.h:6, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/miscdevice.h:4, from ../linux/driver.h:10, from .././linux/driver.c:58: /lib/modules/2.4.7-pre8-xfs/build/include/asm/pgalloc.h:56: `PAGE_OFFSET' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/asm/pgalloc.h:56: (Each undeclared identifier is reported only once /lib/modules/2.4.7-pre8-xfs/build/include/asm/pgalloc.h:56: for each function it appears in.) /lib/modules/2.4.7-pre8-xfs/build/include/asm/pgalloc.h: In function `pte_alloc_one': /lib/modules/2.4.7-pre8-xfs/build/include/asm/pgalloc.h:103: `PAGE_SIZE' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h: In function `clear_user_highpage': In file included from /lib/modules/2.4.7-pre8-xfs/build/include/linux/pagemap.h:16, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/locks.h:8, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/devfs_fs_kernel.h:6, from /lib/modules/2.4.7-pre8-xfs/build/include/linux/miscdevice.h:4, from ../linux/driver.h:10, from .././linux/driver.c:58: /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:48: `PAGE_SIZE' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h: In function `clear_highpage': /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:54: `PAGE_SIZE' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h: In function `memclear_highpage': /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:62: `PAGE_SIZE' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h: In function `memclear_highpage_flush': /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:76: `PAGE_SIZE' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h: In function `copy_user_highpage': /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:90: `PAGE_SIZE' undeclared (first use in this function) /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h: In function `copy_highpage': /lib/modules/2.4.7-pre8-xfs/build/include/linux/highmem.h:101: `PAGE_SIZE' undeclared (first use in this function) make[2]: *** [driver.o] Error 1 make[2]: Leaving directory `/tmp/vmware-config3/vmmon-only/driver-2.4.7-pre8-xfs' make[1]: *** [driver] Error 2 make[1]: Leaving directory `/tmp/vmware-config3/vmmon-only' make: *** [auto-build] Error 2 make: Leaving directory `/tmp/vmware-config3/vmmon-only' Unable to build the vmmon module. For more information on how to troubleshoot module-related problems, please have a look at "http://www.vmware.com/download/modules/modules.html". Execution aborted. From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:34:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKYkU19812 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:34:46 -0700 Received: from local.iboats.com (www.local.iboats.com [64.78.130.68]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKYjV19789 for ; Thu, 19 Jul 2001 13:34:45 -0700 Received: (qmail 15021 invoked from network); 19 Jul 2001 14:34:47 -0600 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by local.iboats.com with SMTP; 19 Jul 2001 14:34:47 -0600 Message-ID: <004901c11091$e220fe80$50824e40@iboats.com> From: "Steve Wolfe" To: References: <17376.993612424@kao2.melbourne.sgi.com> <3B395DED.FDFC6C3D@sgi.com> <20010627011411.A17429@wwweasel.geeksrus.net> <3B39F478.77AEA2B@sgi.com> <20010719152908.M701@sgi.com> Subject: Re: unable to open initial console [devfs?] Date: Thu, 19 Jul 2001 14:32:07 -0600 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, Jul 19, 2001 at 02:02:45PM -0600, Dean Brissinger wrote: > > I used the 2.4.5/1.0.1 RPM to upgrade my Redhat system (built > > w/ XFS 1.0 CD). The kernel seems happy but upon booting reports > > "unable to open initial console". I've seen this before when messing > > with devfs. It basically means /dev/ is missing device files. I > > read a while back that this kernel has devfs disabled by default. Is > > there a trick to get the standard /dev back when upgrading from 1.0 > > to 1.0.1 RPM's? Without meaning to start a flame-war, this is just one more example of why letting other people make your decisions for you is not a good thing to do. RPM (and probably other package managers) go against many of the technical and idealogical reasons for which I use Unix. ; ) Yes, compiling from the source is sometimes more difficult - but making your own decisions is usually worth the extra effort. steve From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:37:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKbhi20123 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:37:43 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKbfV20101 for ; Thu, 19 Jul 2001 13:37:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA04126 for ; Thu, 19 Jul 2001 13:37:25 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id PAA2477311; Thu, 19 Jul 2001 15:36:23 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id PAA96330; Thu, 19 Jul 2001 15:36:23 -0500 (CDT) Subject: Re: unable to open initial console [devfs?] From: Eric Sandeen To: Dean Brissinger Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <17376.993612424@kao2.melbourne.sgi.com> <3B395DED.FDFC6C3D@sgi.com> <20010627011411.A17429@wwweasel.geeksrus.net> <3B39F478.77AEA2B@sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 19 Jul 2001 15:36:06 -0500 Message-Id: <995574967.16774.37.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The 1.0.1 kernel does not have devfs at all, so your standard on-disk /dev should be there waiting for you... So, I'm not sure why you're seeing this problem. /etc/rc.sysinit starts devfsd if it finds /dev/.devfsd - you might check to make sure it's not there for some strange reason. Hm, I just read Nate's suggestion of reinstalling the dev package... not sure what would have caused these problems though. You can do an rpm query / verify of the dev package to see if anything is amiss. -Eric On 19 Jul 2001 14:02:45 -0600, Dean Brissinger wrote: > I used the 2.4.5/1.0.1 RPM to upgrade my Redhat system (built > w/ XFS 1.0 CD). The kernel seems happy but upon booting reports > "unable to open initial console". I've seen this before when messing > with devfs. It basically means /dev/ is missing device files. I > read a while back that this kernel has devfs disabled by default. Is > there a trick to get the standard /dev back when upgrading from 1.0 > to 1.0.1 RPM's? -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:46:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKkYq20789 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:46:34 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKkWV20767 for ; Thu, 19 Jul 2001 13:46:32 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15NKgi-0004M6-00; Fri, 20 Jul 2001 08:46:24 +1200 Date: Fri, 20 Jul 2001 08:46:24 +1200 (NZST) From: Juha Saarinen To: "Bernhard R. Erdmann" cc: Linux XFS Mailing List Subject: Re: 2.4.7-pre8-xfs breaks VMWare In-Reply-To: <3B5743C9.49891146@berdmann.de> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 19 Jul 2001, Bernhard R. Erdmann wrote: > Hi, > > after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare > can't compile it's modules anymore. > Any hint? > For more information on how to troubleshoot module-related problems, > please have > a look at "http://www.vmware.com/download/modules/modules.html". That URL is probably a good start; contacting VMware or checking their news server would also be advisable. VMware has been troublesome for me in the past, and isn't really suitable to use in an environment where you upgrade the kernel source frequently -- it seems to make too many assumptions about the source... -- Regards, Juha PGP fingerprint: B7E1 CC52 5FCA 9756 B502 10C8 4CD8 B066 12F3 9544 From owner-linux-xfs@oss.sgi.com Thu Jul 19 13:52:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JKqYg21324 for linux-xfs-outgoing; Thu, 19 Jul 2001 13:52:34 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JKqWV21302 for ; Thu, 19 Jul 2001 13:52:32 -0700 Received: from auto-nb1.xs4all.nl (perle-wan1.coltex.nl [10.0.1.177]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6JKqTe07095; Thu, 19 Jul 2001 22:52:29 +0200 Message-Id: <4.3.2.7.2.20010719225110.030b7900@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 19 Jul 2001 22:52:14 +0200 To: "Bernhard R. Erdmann" , Linux XFS Mailing List From: Seth Mos Subject: Re: 2.4.7-pre8-xfs breaks VMWare In-Reply-To: <3B5743C9.49891146@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 22:32 19-7-2001 +0200, Bernhard R. Erdmann wrote: >Hi, > >after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare >can't compile it's modules anymore. >Any hint? I rather suspect normal kernel breakage that can be expected with things like vmware. I suggest complaining to vmware. I don't think this is xfs related. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 19 14:57:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JLvWV24378 for linux-xfs-outgoing; Thu, 19 Jul 2001 14:57:32 -0700 Received: from drama.koli (mail@drama.obuda.kando.hu [193.224.41.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JLvUV24358 for ; Thu, 19 Jul 2001 14:57:30 -0700 Received: from feczo by drama.koli with local (Exim 3.22 #1 (Debian)) id 15NLnP-000361-00 for ; Thu, 19 Jul 2001 23:57:23 +0200 Date: Thu, 19 Jul 2001 23:57:23 +0200 From: Feczak Szabolcs To: linux-xfs@oss.sgi.com Subject: Re: Kernelbug Message-ID: <20010719235723.A11861@koli.kando.hu> References: <20010719182713.A5562@koli.kando.hu> <20010719191842.D18183@athlon.random> <20010719192149.B5094@gruyere.muc.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010719192149.B5094@gruyere.muc.suse.de> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've just recompiled from the latest cvs and up to now it is working. From owner-linux-xfs@oss.sgi.com Thu Jul 19 15:21:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JMLZq25565 for linux-xfs-outgoing; Thu, 19 Jul 2001 15:21:35 -0700 Received: from biobio.vexcel.com (biobio.vexcel.com [192.92.90.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JMLWV25546 for ; Thu, 19 Jul 2001 15:21:33 -0700 Received: from [192.168.1.17] (router.vexcel.com [192.92.90.254]) by biobio.vexcel.com (8.9.3+Sun/8.9.1) with ESMTP id QAA23328 for ; Thu, 19 Jul 2001 16:21:23 -0600 (MDT) Mime-Version: 1.0 X-Sender: brissing@mail.vexcel.com (Unverified) Message-Id: In-Reply-To: <995574967.16774.37.camel@stout.americas.sgi.com> References: <17376.993612424@kao2.melbourne.sgi.com> <3B395DED.FDFC6C3D@sgi.com> <20010627011411.A17429@wwweasel.geeksrus.net> <3B39F478.77AEA2B@sgi.com> <995574967.16774.37.camel@stout.americas.sgi.com> Date: Thu, 19 Jul 2001 16:17:50 -0600 To: linux-xfs@oss.sgi.com From: Dean Brissinger Subject: Re: unable to open initial console [devfs?] Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Well, messing with .devfsd and rc.sysinit has no effect on the kernel failure. I may have to do what Nathan did. Has anyone else seen this problem and found an easy fix for it? At 3:36 PM -0500 7/19/01, Eric Sandeen wrote: >The 1.0.1 kernel does not have devfs at all, so your standard on-disk >/dev should be there waiting for you... > >So, I'm not sure why you're seeing this problem. /etc/rc.sysinit starts >devfsd if it finds /dev/.devfsd - you might check to make sure it's not >there for some strange reason. > >Hm, I just read Nate's suggestion of reinstalling the dev package... not >sure what would have caused these problems though. You can do an rpm >query / verify of the dev package to see if anything is amiss. > >-Eric > >On 19 Jul 2001 14:02:45 -0600, Dean Brissinger wrote: >> I used the 2.4.5/1.0.1 RPM to upgrade my Redhat system (built >> w/ XFS 1.0 CD). The kernel seems happy but upon booting reports >> "unable to open initial console". I've seen this before when messing >> with devfs. It basically means /dev/ is missing device files. I >> read a while back that this kernel has devfs disabled by default. Is >> there a trick to get the standard /dev back when upgrading from 1.0 >> to 1.0.1 RPM's? >-- >Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs >sandeen@sgi.com SGI, Inc. -- . . . . . . . . ooo . . . . ooo . . . . . . . . . . . . Dean Brissinger - Systems Administrator . . Direct: 303-583-0278 Main: 303-444-0094 . . Fax: 303-583-0246 http://www.vexcel.com/ . . . . . . . . . . oOOo . . A . . oOOo . . . . . . . . 0 0 '```` From owner-linux-xfs@oss.sgi.com Thu Jul 19 16:53:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JNriI29554 for linux-xfs-outgoing; Thu, 19 Jul 2001 16:53:44 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JNrfV29535 for ; Thu, 19 Jul 2001 16:53:41 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id BAA19786; Fri, 20 Jul 2001 01:53:44 +0200 Date: Fri, 20 Jul 2001 01:53:43 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: "Christian, Chip" Cc: linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: Busy inodes after umount Message-ID: <20010720015343.B11236@vestdata.no> References: <23D04BDBA646D411BDDD00D0B774B53902963BE8@SA-BWMAIL1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <23D04BDBA646D411BDDD00D0B774B53902963BE8@SA-BWMAIL1>; from Christian, Chip on Thu, Jul 19, 2001 at 04:22:07PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 19, 2001 at 04:22:07PM -0400, Christian, Chip wrote: > I found the same thing happening. Tracked it down in our case to using fdisk to re-read disk size before mounting. Replaced it with "blockdev --readpt" and the problem seems to have gone away. YMMV. I've now been able to reproduce: * make a filesystem * mount it * export it (nfs) * mount on remote machine * lock file (fcntl) * unexport * unmount Then you get the VFS message about self-destruct. Tested with both ext2 and xfs. The lock is still present in /proc/locks after the umount. With ext2 I can remount the filesystem successfully, but with XFS I get the message about duplicate UUIDs and the mount failes. I believe this is a totally different problem from the one you were experiencing. (and blockdev doesn't help for me) I suppose this is a generic kernel bug? -- Ragnar Kjorstad Big Storage > [root@ha2 /root]# mkfs -t xfs -f /dev/sdb1 > meta-data=/dev/sdb1 isize=256 agcount=51, agsize=262144 > blks > data = bsize=4096 blocks=13305828, > imaxpct=25 > = sunit=0 swidth=0 blks, unwritten=0 > naming =version 2 bsize=4096 > log =internal log bsize=4096 blocks=1624 > realtime =none extsz=65536 blocks=0, rtextents=0 > [root@ha2 /root]# mount -t xfs /dev/sdb1 /mnt/raid/ > [root@ha2 /root]# umount /mnt/raid/ > [root@ha2 /root]# mount -t xfs /dev/sdb1 /mnt/raid/ > mount: wrong fs type, bad option, bad superblock on /dev/sdb1, > or too many mounted file systems > > > >From /var/log/messages: > Jul 19 12:27:15 ha2 kernel: Start mounting filesystem: sd(8,17) > Jul 19 12:27:16 ha2 kernel: Ending clean XFS mount for filesystem: sd(8,17) > Jul 19 12:27:19 ha2 kernel: XFS unmount got error 16 > Jul 19 12:27:19 ha2 kernel: linvfs_put_super: vfsp/0xc2ff71e0 left dangling! > Jul 19 12:27:19 ha2 kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day... > Jul 19 12:27:21 ha2 kernel: XFS: Filesystem has duplicate UUID - can't mount > > > This happens on a shared storage cluster with two nodes. The same thing > happens on both nodes. (I'm only using the device from one device at the > time) > > linux-2.4.5 with XFS patch from 06112001. > > After a reboot it works again, and I have not been able to reproduce > yet. It first happened when I was testing NFS locks, so it could be > related to that. > > > > -- > Ragnar Kjorstad > Big Storage From owner-linux-xfs@oss.sgi.com Thu Jul 19 16:58:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6JNwuI29927 for linux-xfs-outgoing; Thu, 19 Jul 2001 16:58:56 -0700 Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6JNwsV29908 for ; Thu, 19 Jul 2001 16:58:54 -0700 Received: from wonky.feral.com (mjacob@wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6JNwjS71138; Thu, 19 Jul 2001 16:58:45 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Thu, 19 Jul 2001 16:58:36 -0700 (PDT) From: Matthew Jacob Reply-To: To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= cc: "Christian, Chip" , , Subject: Re: Busy inodes after umount In-Reply-To: <20010720015343.B11236@vestdata.no> Message-ID: <20010719165758.D50024-100000@wonky.feral.com> 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 f6JNwsV29909 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I reported this a couple of months back. It's reassuring to know that it's a consistent problem. On Fri, 20 Jul 2001, [iso-8859-1] Ragnar Kjørstad wrote: > On Thu, Jul 19, 2001 at 04:22:07PM -0400, Christian, Chip wrote: > > I found the same thing happening. Tracked it down in our case to using fdisk to re-read disk size before mounting. Replaced it with "blockdev --readpt" and the problem seems to have gone away. YMMV. > > I've now been able to reproduce: > > * make a filesystem > * mount it > * export it (nfs) > * mount on remote machine > * lock file (fcntl) > * unexport > * unmount > > Then you get the VFS message about self-destruct. Tested with both ext2 > and xfs. > > The lock is still present in /proc/locks after the umount. > > With ext2 I can remount the filesystem successfully, but with XFS I get > the message about duplicate UUIDs and the mount failes. I believe this is a totally > different problem from the one you were experiencing. (and blockdev doesn't help for me) > > I suppose this is a generic kernel bug? > > > From owner-linux-xfs@oss.sgi.com Thu Jul 19 17:04:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K04c830444 for linux-xfs-outgoing; Thu, 19 Jul 2001 17:04:38 -0700 Received: from cvo-exchange.cvo.roguewave.com (cvo-ext.roguewave.com [12.22.36.198]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K04aV30423 for ; Thu, 19 Jul 2001 17:04:36 -0700 Received: by cvo-exchange.roguewave.com with Internet Mail Service (5.5.2650.21) id ; Thu, 19 Jul 2001 17:04:26 -0700 Message-ID: From: Poul Petersen To: linux-xfs@oss.sgi.com, "'linux-kernel@vger.kernel.org'" Subject: Oops (NULL pointer dereference) with 2.4.5+xfs-1.0.1 Date: Thu, 19 Jul 2001 17:04:25 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm running RedHat 7.1 with the manually patched 2.4.5 kernel and xfs-1.0.1 on a dual PII (400) with 1 Gig of RAM. The XFS filesystems are located on a SAN RAID device accessed through a qlogic 2100 Fibre Channel card (using the qla2x00 module provided by Qlogic, ver 4.25). This system acts as a "gateway" by mounting the disks from the SAN and then exporting them to an array of hosts (Solaris, IRIX, Linux, AIX, etc) via NFS. The system has been stable through heavy read/write testing that moved approximately 5TB of data. Then we got an oops and the system locked up - we don't have the kernel debugger loaded and syslog didn't catch it, so I don't have a record of that oops. We hard rebooted the system and within 10 minutes while authenticating mount requests we got the same oops - rpc.mountd: authenticated mount request from 10.68.9.3:1022 for /san/devbuild (/san/devbuild) kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000009c kernel: printing eip: kernel: c01f1e98 kernel: *pde = 00000000 kernel: Oops: 0002 kernel: CPU: 0 kernel: EIP: 0010:[] kernel: EFLAGS: 00010002 kernel: eax: 00000074 ebx: 00000074 ecx: 00000004 edx: ffffffe8 kernel: esi: ffffffe8 edi: c01c88a9 ebp: f3f9a54c esp: f4ae5aac kernel: ds: 0018 es: 0018 ss: 0018 kernel: Process nfsd (pid: 682, stackpage=f4ae5000) kernel: Stack: 00000004 ffffffe8 c01c88a9 c01c8d94 00000074 00000288 ffffffe8 f3f9a560 kernel: c033bf20 c01c8de3 ffffffe8 00000004 c01c88a9 c01c88a9 ffffffe8 00000004 kernel: 00000000 00000000 10130323 f7c5d800 f3d14e40 00000004 c01ddb16 f7c5d800 kernel: Call Trace: [] [] [] [] [] [] [] kernel: [] [] [] [] [] [] [] [] kernel: [] [] [] [] [] [] [] [] kernel: [] [] [] [] [] [] [] kernel: kernel: Code: f0 fe 4b 28 0f 88 1a f3 0c 00 8b 0b 85 c9 74 20 8d 7b 28 8d This time the system did not crash, but the nfsd (pid 682) died and nfs was altogether broken. Since we couldn't get nfs to shut down, we rebooted again. At this point we reviewed changes to the system since the 5TB testing period and the only thing changed was we enabled quotas on one of the XFS partitions (Some of the testing was with quotas on, but not all). So, we removed "usrquota,grpquota" from /etc/fstab for that partition and the system has been fine since (31 hours now). I've dug through a vast amount of mailing list archives for both XFS and knfsd, but all of the similar problems were resolved with patches which seem to already be included in 2.4.5 and xfs-1.0.1 (I checked the code). We have since brought up another system with the same software configuration (hardware is a single PII-333 with 196 MB RAM). On this machine we enabled quotas and started hammering on it. It has been running for 24 hours and has moved almost 3/4 of a TB without any problems, so I'm not convinced that quotas was the problem. I'm not even really certain that this is an XFS problem, except we haven't seen this problem on other non-XFS files servers that we have and this problem seemed at least similar to a previous XFS problem: http://search.luky.org/linux-kernel.2001/msg12490.html Any insight would be greatly appreciated. Thanks, -poul From owner-linux-xfs@oss.sgi.com Thu Jul 19 17:31:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K0VE732117 for linux-xfs-outgoing; Thu, 19 Jul 2001 17:31:14 -0700 Received: from trillium-hollow.org (IDENT:root@trillium-hollow.org [209.180.166.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K0VBV32097 for ; Thu, 19 Jul 2001 17:31:12 -0700 Received: from erich (helo=trillium) by trillium-hollow.org with local-esmtp (Exim 3.20 #1) id 15NOCC-0000S2-00 for linux-xfs@oss.sgi.com; Thu, 19 Jul 2001 17:31:08 -0700 To: linux-xfs@oss.sgi.com Subject: FYI: Networking bug in RH 7.1 updated config files... Date: Thu, 19 Jul 2001 17:31:08 -0700 From: erich@uruk.org Message-Id: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk NOTE, this is a RH 7.1 problem fundamentally, but I'm mentioning it here because the compiled kernels provided by the SGI guys in the 1.0.1 release masked this problem by (I think) not being compiled with the config files provided. If this problem has been mentioned before and I just haven't noticed it, then sorry for the wasted bandwidth. ;) The kernel config files for the update to kernel 2.4.3-12 in RH 7.1 (as well as the XFS 1.0.1 release) have the "CONFIG_NET_ECN" option enabled ("Explicit Congestion Notification"), which marks the SYN packets of TCP connections in a way that causes some machines to simply refuse all connections from a Linux box configured in this way. The comment on the configuration parameter claims this is just "some firewalls" that won't work with it, and that is not true. I have had this problem with both at least one firewall product and several other machines refusing telnet and web connections. The most confusing thing was this only was happening on the newer kernels I was compiling myself, using the normal "make oldconfig", etc. sequence from the config files provided in the kernel sources dir so I kept as much else the same as possible. I tore my hair out for a bit until I figured out what was happening via tcpdump and realized what option was causing the problem, and more to the point, the pre-compiled kernels provided by the SGI guys don't seem to correspond to the config files provided... So, for those who care about TCP/IP compatibility and are compiling your own kernels, I suggest you remove this option from your config. -- Erich Stefan Boleyn http://www.uruk.org/ "Reality is truly stranger than fiction; Probably why fiction is so popular" From owner-linux-xfs@oss.sgi.com Thu Jul 19 17:39:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K0ddt32654 for linux-xfs-outgoing; Thu, 19 Jul 2001 17:39:39 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K0dbV32631 for ; Thu, 19 Jul 2001 17:39:37 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id RAA01393 for ; Thu, 19 Jul 2001 17:37:11 -0700 (PDT) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id TAA2476009; Thu, 19 Jul 2001 19:38:17 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id TAA65046; Thu, 19 Jul 2001 19:38:17 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id TAA40153; Thu, 19 Jul 2001 19:38:16 -0500 (CDT) Message-Id: <200107200038.TAA40153@fsgi158.americas.sgi.com> Subject: Re: Busy inodes after umount To: mjacob@feral.com Date: Thu, 19 Jul 2001 19:38:15 -0500 (CDT) Cc: xfs@ragnark.vestdata.no (=?iso-8859-1?Q?Ragnar_Kj=F8rstad?=), chip.christian@storageapps.com (Christian Chip), linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org In-Reply-To: <20010719165758.D50024-100000@wonky.feral.com> from "Matthew Jacob" at Jul 19, 2001 04:58:36 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by pneumatic-tube.sgi.com id RAA01393 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6K0dbV32632 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I know there was a fix for a "Busy inodes after unmount" problem in 2.4.6-pre3. Here's an excerpt from a posting to the NFS mailing list from Neil Brown: -------------Included message----------------------- Previously anonymous dentries were hashed (though with no name, the hash was pretty meaningless). This meant that they would hang around after the last reference was dropped. This was actually fairly pointless as they would never get referenced again, and caused a real problem as umount wouldn't discard them and so you got the message printk("VFS: Busy inodes after unmount. " "Self-destruct in 5 seconds. Have a nice day...\n"); In 2.4.6-pre3 I stopped hashing those dentries so now when the last reference is dropped, the dentry is freed. So now there will never be more anonymous dentries than there are active nfsd threads. ---------------end included message------------------- Tad > > I reported this a couple of months back. It's reassuring to know that it's a > consistent problem. > > On Fri, 20 Jul 2001, [iso-8859-1] Ragnar Kjørstad wrote: > > > On Thu, Jul 19, 2001 at 04:22:07PM -0400, Christian, Chip wrote: > > > I found the same thing happening. Tracked it down in our case to using fdisk to re-read disk size before mounting. Replaced it with "blockdev --readpt" and the problem seems to have gone away. YMMV. > > > > I've now been able to reproduce: > > > > * make a filesystem > > * mount it > > * export it (nfs) > > * mount on remote machine > > * lock file (fcntl) > > * unexport > > * unmount > > > > Then you get the VFS message about self-destruct. Tested with both ext2 > > and xfs. > > > > The lock is still present in /proc/locks after the umount. > > > > With ext2 I can remount the filesystem successfully, but with XFS I get > > the message about duplicate UUIDs and the mount failes. I believe this is a totally > > different problem from the one you were experiencing. (and blockdev doesn't help for me) > > > > I suppose this is a generic kernel bug? > > > > > > > From owner-linux-xfs@oss.sgi.com Thu Jul 19 17:39:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K0dnV32715 for linux-xfs-outgoing; Thu, 19 Jul 2001 17:39:49 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K0dlV32696 for ; Thu, 19 Jul 2001 17:39:47 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15NOKV-0004g1-00; Fri, 20 Jul 2001 12:39:43 +1200 From: "Juha Saarinen" To: , Subject: RE: Networking bug in RH 7.1 updated config files... Date: Fri, 20 Jul 2001 12:40:08 +1200 Message-ID: <033901c110b4$870bcde0$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk :: The comment on the configuration parameter claims this is just "some :: firewalls" that won't work with it, and that is not true. I :: have had this :: problem with both at least one firewall product and several other :: machines refusing telnet and web connections. I second that -- it also causes problems on email (SMTP) and NTP connections, against hosts and routers that don't yet grok ECN. Note that a quick workaround is to do: echo "0" > /proc/sys/net/ipv4/tcp_ecn which disables ECN. -- Juha From owner-linux-xfs@oss.sgi.com Thu Jul 19 17:50:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K0oDP00934 for linux-xfs-outgoing; Thu, 19 Jul 2001 17:50:13 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K0oAV00914 for ; Thu, 19 Jul 2001 17:50:10 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id CAA20925; Fri, 20 Jul 2001 02:49:57 +0200 Date: Fri, 20 Jul 2001 02:49:56 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Tad Dolphay Cc: mjacob@feral.com, Christian Chip , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org Subject: Re: Busy inodes after umount Message-ID: <20010720024956.B20732@vestdata.no> References: <20010719165758.D50024-100000@wonky.feral.com> <200107200038.TAA40153@fsgi158.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200107200038.TAA40153@fsgi158.americas.sgi.com>; from Tad Dolphay on Thu, Jul 19, 2001 at 07:38:15PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 19, 2001 at 07:38:15PM -0500, Tad Dolphay wrote: > I know there was a fix for a "Busy inodes after unmount" problem in > 2.4.6-pre3. Here's an excerpt from a posting to the NFS mailing list > from Neil Brown: Thanks. I'll try that and see if that solves the problem (also the XFS UUID problem). -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Thu Jul 19 17:56:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K0uU901215 for linux-xfs-outgoing; Thu, 19 Jul 2001 17:56:30 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K0uRV01195 for ; Thu, 19 Jul 2001 17:56:27 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id RAA09047 for ; Thu, 19 Jul 2001 17:54:01 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 KAA09180; Fri, 20 Jul 2001 10:55:06 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA13339; Fri, 20 Jul 2001 10:55:05 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107201055.ZM225557@wobbly.melbourne.sgi.com> Date: Fri, 20 Jul 2001 10:55:02 +1000 In-Reply-To: Poul Petersen "Oops (NULL pointer dereference) with 2.4.5+xfs-1.0.1" (Jul 19, 5:04pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Poul Petersen , linux-xfs@oss.sgi.com, "'linux-kernel@vger.kernel.org'" Subject: Re: Oops (NULL pointer dereference) with 2.4.5+xfs-1.0.1 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 19, 5:04pm, Poul Petersen wrote: > Subject: Oops (NULL pointer dereference) with 2.4.5+xfs-1.0.1 > I'm running RedHat 7.1 with the manually patched 2.4.5 kernel and > xfs-1.0.1 on a dual PII (400) with 1 Gig of RAM. The XFS filesystems are > located on a SAN RAID device accessed through a qlogic 2100 Fibre Channel > card (using the qla2x00 module provided by Qlogic, ver 4.25). This system > acts as a "gateway" by mounting the disks from the SAN and then exporting > them to an array of hosts (Solaris, IRIX, Linux, AIX, etc) via NFS. The > system has been stable through heavy read/write testing that moved > approximately 5TB of data. Then we got an oops and the system locked up - we > don't have the kernel debugger loaded and syslog didn't catch it, so I don't > have a record of that oops. I'm not sure I can help on this initial problem, too little information for a post mortum - but this one... > We hard rebooted the system and within 10 > minutes while authenticating mount requests we got the same oops - > > rpc.mountd: authenticated mount request from 10.68.9.3:1022 for > /san/devbuild (/san/devbuild) > kernel: Unable to handle kernel NULL pointer dereference at virtual address > 0000009c > kernel: printing eip: > kernel: c01f1e98 > kernel: *pde = 00000000 > kernel: Oops: 0002 > kernel: CPU: 0 > kernel: EIP: 0010:[] > kernel: EFLAGS: 00010002 > kernel: eax: 00000074 ebx: 00000074 ecx: 00000004 edx: ffffffe8 > kernel: esi: ffffffe8 edi: c01c88a9 ebp: f3f9a54c esp: f4ae5aac > kernel: ds: 0018 es: 0018 ss: 0018 > kernel: Process nfsd (pid: 682, stackpage=f4ae5000) > kernel: Stack: 00000004 ffffffe8 c01c88a9 c01c8d94 00000074 00000288 > ffffffe8 f3f9a560 > kernel: c033bf20 c01c8de3 ffffffe8 00000004 c01c88a9 c01c88a9 > ffffffe8 00000004 > kernel: 00000000 00000000 10130323 f7c5d800 f3d14e40 00000004 > c01ddb16 f7c5d800 > kernel: Call Trace: [] [] [] [] > [] [] [] > kernel: [] [] [] [] > [] [] [] [] > kernel: [] [] [] [] > [] [] [] [] > kernel: [] [] [] [] > [] [] [] > kernel: > kernel: Code: f0 fe 4b 28 0f 88 1a f3 0c 00 8b 0b 85 c9 74 20 8d 7b 28 8d > > This time the system did not crash, but the nfsd (pid 682) died and > nfs was altogether broken. Since we couldn't get nfs to shut down, we > rebooted again. At this point we reviewed changes to the system since the > 5TB testing period and the only thing changed was we enabled quotas on one > of the XFS partitions (Some of the testing was with quotas on, but not all). > So, we removed "usrquota,grpquota" from /etc/fstab for that partition and > the system has been fine since (31 hours now). I've dug through a vast > amount of mailing list archives for both XFS and knfsd, but all of the > similar problems were resolved with patches which seem to already be > included in 2.4.5 and xfs-1.0.1 (I checked the code). We have since brought > up another system with the same software configuration (hardware is a single > PII-333 with 196 MB RAM). On this machine we enabled quotas and started > hammering on it. It has been running for 24 hours and has moved almost 3/4 > of a TB without any problems, so I'm not convinced that quotas was the > problem. I'm not even really certain that this is an XFS problem, except we > haven't seen this problem on other non-XFS files servers that we have and > this problem seemed at least similar to a previous XFS problem: > http://search.luky.org/linux-kernel.2001/msg12490.html > > Any insight would be greatly appreciated. > There is one known problem where a mount with quota enabled has caused a panic on a local QA system, also with a NULL pointer dereference which may be causing this problem. I'm having the devil's own job trying to reproduce it - but will CC you when I do have a fix for it - may solve your problem. If you survived the mount (with quota enabled), then this is not the problem and there are no other known problems with XFS quota, so we'd need to extract some more information to diagnose further. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 19 20:26:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K3Q1311103 for linux-xfs-outgoing; Thu, 19 Jul 2001 20:26:01 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K3PxV11084 for ; Thu, 19 Jul 2001 20:25:59 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id UAA14484 for ; Thu, 19 Jul 2001 20:25:48 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id UAA18380; Thu, 19 Jul 2001 20:25:24 -0700 (PDT) Message-ID: <3B57A414.365082A@sgi.com> Date: Thu, 19 Jul 2001 22:23:00 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: erich@uruk.org CC: linux-xfs@oss.sgi.com Subject: Re: FYI: Networking bug in RH 7.1 updated config files... References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk erich@uruk.org wrote: > > NOTE, this is a RH 7.1 problem fundamentally, but I'm mentioning it here > because the compiled kernels provided by the SGI guys in the 1.0.1 release > masked this problem by (I think) not being compiled with the config > files provided. Actually, for the "Red Hat-ish" RPMs we took the config files "as-is" and just added the XFS bits... so it is enabled in our RPMs as well. [sandeen@stout /]$ cd /usr/src/linux-2.4/configs/ [sandeen@stout configs]$ grep INET_ECN *.config kernel-2.4.3-athlon.config:CONFIG_INET_ECN=y kernel-2.4.3-athlon-smp.config:CONFIG_INET_ECN=y kernel-2.4.3-i386-BOOT.config:# CONFIG_INET_ECN is not set kernel-2.4.3-i386.config:CONFIG_INET_ECN=y kernel-2.4.3-i386-smp.config:CONFIG_INET_ECN=y kernel-2.4.3-i586.config:CONFIG_INET_ECN=y kernel-2.4.3-i586-smp.config:CONFIG_INET_ECN=y kernel-2.4.3-i686.config:CONFIG_INET_ECN=y kernel-2.4.3-i686-enterprise.config:CONFIG_INET_ECN=y kernel-2.4.3-i686-smp.config:CONFIG_INET_ECN=y -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 19 20:37:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K3b3v11541 for linux-xfs-outgoing; Thu, 19 Jul 2001 20:37:03 -0700 Received: from saturn.mackay.tritus.ca (cr212927-a.slnt1.on.wave.home.com [24.112.218.180]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K3afV11521 for ; Thu, 19 Jul 2001 20:36:42 -0700 Received: (from adam@localhost) by saturn.mackay.tritus.ca (8.11.2/8.11.2) id f6K3aih10996; Thu, 19 Jul 2001 23:36:44 -0400 X-Authentication-Warning: saturn.mackay.tritus.ca: adam set sender to adam@tritus.ca using -f Date: Thu, 19 Jul 2001 23:36:44 -0400 From: Adam Sherman To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid Message-ID: <20010719233643.E9205@tritus.ca> References: <20010719155130.D1330@de.tecosim.com> <995563148.12920.41.camel@stout.americas.sgi.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="mSxgbZZZvrAyzONB" Content-Disposition: inline In-Reply-To: <995563148.12920.41.camel@stout.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --mSxgbZZZvrAyzONB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jul 19, 2001 at 12:19:07PM -0500, Eric Sandeen wrote: > Ok, I put a new update disk in the updates/ directory under > Release-1.0.1/installer/updates. This should fix things for you. I'm having possibly similar issues, with or without the Jul19-12 update disk. Here's my dump after clicking the next button of the disk druid screen: **start*dump** Traceback (innermost last): File "/usr/bin/anaconda", line 520, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 392, in run self.icw.run () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 880, in run mainloop () File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop _gtk.gtk_main() File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__ ret = apply(self.func, a) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 482, in nextClicked next = self.currentScreen.getNext () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 130, in getNext rc = self.lba32Check () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 76, in lba32Check maxcyl = self.todo.fstab.getBootPartitionMaxCylFromDesired() File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 241, in getBootPartitionMaxCylFromDesired bootpart = self.getBootDevice() File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, in getBootDevice for (mntpoint, partition, fsystem, doFormat, size) in self.mountList(): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1052, in mountList if fsType == "swap": continue NameError: fsType **end*dump** My setup is a smp box with two IDE disks, hda & hdc. It has 128MB of RAM and a tulip based NIC. I'm installing using the 1.0.1 release freshly downloaded and exported over NFS. I want RAID1 mirrored everything which amounts to a 32MB boot, 750MB root, 1.3GB var and 256MB swap. All using XFS. I get this error either right away when clicking next in the Disk Druid screen if I'm using standard 1.0.1 or after the format partitions screen if I'm using the Jul19-12 update. I'm attaching the dump from the standard install, but I couldn't get the Jul19-12 installer to save the dump to a floppy, it couldn't access "/tmp/floppy" for some reason. It's dump starts out similar then complains about and "AttributeError: set_active". Any suggestions? Thanks, A. P.S. I'm in a rush because I've got to have this box up by Friday... )-: -- Adam Sherman President & Technology Architect Tritus Consultant Group Inc. +1.613.255.5164 http://www.tritus.ca --mSxgbZZZvrAyzONB Content-Type: text/plain; charset=us-ascii Content-Description: Dump from standard 1.0.1 install Content-Disposition: inline; filename="anacdump1.txt" Traceback (innermost last): File "/usr/bin/anaconda", line 520, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 392, in run self.icw.run () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 880, in run mainloop () File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop _gtk.gtk_main() File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__ ret = apply(self.func, a) File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 482, in nextClicked next = self.currentScreen.getNext () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 130, in getNext rc = self.lba32Check () File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 76, in lba32Check maxcyl = self.todo.fstab.getBootPartitionMaxCylFromDesired() File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 241, in getBootPartitionMaxCylFromDesired bootpart = self.getBootDevice() File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, in getBootDevice for (mntpoint, partition, fsystem, doFormat, size) in self.mountList(): File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1052, in mountList if fsType == "swap": continue NameError: fsType Local variables in innermost frame: size: 66465 mntpoint: /boot makeup: ['Raid001', 'Raid000'] device: md0 raidType: 1 start: 63 sortMounts: devices: [('hdc1', 'Raid001', 7, 63, 66465, 66, 0), ('hda1', 'Raid000', 7, 63, 72513, 9, 0), ('hda5', 'Raid002', 7, 72639, 1540161, 200, 0), ('hdc5', 'Raid003', 7, 66591, 1536129, 1590, 0), ('hda6', 'Raid004', 7, 1612863, 532161, 266, 0), ('hdc6', 'Raid005', 7, 1602783, 525105, 2111, 0), ('hda7', 'Raid006', 7, 2145087, 2854593, 620, 0), ('hdc7', 'Raid007', 7, 2127951, 2998737, 5086, 0)] fstab: [] self: fsystem: xfs raid: [('/boot', 'md0', 'xfs', 1, 63, 66465, ['Raid001', 'Raid000']), ('/', 'md1', 'xfs', 1, 63, 72513, ['Raid002', 'Raid003']), ('', 'md3', 'swap', 1, 72639, 1540161, ['Raid004', 'Raid005']), ('/var', 'md2', 'xfs', 1, 66591, 1536129, ['Raid006', 'Raid007'])] skipExtra: 0 ToDo object: (itodo ToDo p1 (dp2 S'resState' p3 S'' sS'progressWindow' p4 NsS'setupFilesystems' p5 I1 sS'monitorVsync' p6 S'' sS'videoCardStateNode' p7 S'' sS'serial' p8 I0 sS'ddruidReadOnly' p9 I0 sS'bootdisk' p10 I0 sS'videoRamState' p11 S'' sS'monitorOriginalName' p12 S'' sS'language' p13 (itodo Language (dp14 S'langInfoByName' p15 (dp16 S'Arabic (Yemen)' p17 (S'ar_YE' S'iso06' S'LatArCyrHeb-16' tsS'Spanish (Argentina)' p18 (S'es_AR' S'iso01' S'lat0-sun16' tsS'Italian (Italy)' p19 (S'it_IT@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Lebanon)' p20 (S'ar_LB' S'iso06' S'LatArCyrHeb-16' tsS'Spanish (Guatemala)' p21 (S'es_GT' S'iso01' S'lat0-sun16' tsS'Malay (Malaysia)' p22 (S'ms_MY' S'iso01' S'lat0-sun16' tsS'Arabic (Libyan Arab Jamahiriya)' p23 (S'ar_LY' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Oman)' p24 (S'ar_OM' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Iraq)' p25 (S'ar_IQ' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Kuwait)' p26 (S'ar_KW' S'iso06' S'LatArCyrHeb-16' tsS'English (South Africa)' p27 (S'en_ZA' S'iso01' S'lat0-sun16' tsS'French (Switzerland)' p28 (S'fr_CH' S'iso01' S'lat0-sun16' tsS'Arabic (Bahrein)' p29 (S'ar_BH' S'iso06' S'LatArCyrHeb-16' tsS'Croatian' p30 (S'hr_HR' S'iso02' S'lat2-sun16' tsS'French (France)' p31 (S'fr_FR@euro' S'iso15' S'lat0-sun16' tsS'Greenlandic (Greenland)' p32 (S'kl_GL' S'iso01' S'lat0-sun16' tsS'Korean (Republic of Korea)' p33 (S'ko_KR.euckr' S'iso01' S'lat0-16' tsS'Ukrainian' p34 (S'uk_UA' S'koi8-u' S'cyr-sun16' tsS'Spanish (Mexico)' p35 (S'es_MX' S'iso01' S'lat0-sun16' tsS'Greek' p36 (S'el_GR' S'iso07' S'gr.f16' tsS'Spanish (El Salvador)' p37 (S'es_SV' S'iso01' S'lat0-sun16' tsS'Spanish (Peru)' p38 (S'es_PE' S'iso01' S'lat0-sun16' tsS'Spanish (Honduras)' p39 (S'es_HN' S'iso01' S'lat0-sun16' tsS'Spanish (Costa Rica)' p40 (S'es_CR' S'iso01' S'lat0-sun16' tsS'English (Denmark)' p41 (S'en_DK' S'iso01' S'lat0-sun16' tsS'Dutch (Netherlands)' p42 (S'nl_NL@euro' S'iso15' S'lat0-sun16' tsS'Serbian (Yugoslavia)' p43 (S'sr_YU@cyrillic' S'iso05' S'cyr-sun16' tsS'Russian (Ukraine)' p44 (S'ru_UA' S'koi8-u' S'cyr-sun16' tsS'Portuguese (Portugal)' p45 (S'pt_PT@euro' S'iso15' S'lat0-sun16' tsS'Afrikaans (South Africa)' p46 (S'af_ZA' S'iso01' S'lat0-sun16' tsS'Norwegian' p47 (S'no_NO' S'iso01' S'lat0-sun16' tsS'Arabic (Morocco)' p48 (S'ar_MA' S'iso06' S'LatArCyrHeb-16' tsS'English (Philippines)' p49 (S'en_PH' S'iso01' S'lat0-sun16' tsS'Arabic (Algeria)' p50 (S'ar_DZ' S'iso06' S'LatArCyrHeb-16' tsS'Indonesian' p51 (S'id_ID' S'iso01' S'lat0-sun16' tsS'Danish' p52 (S'da_DK' S'iso01' S'lat0-sun16' tsS'Chinese (Taiwan R.O.C.)' p53 (S'zh_TW.euctw' S'iso01' S'lat0-16' tsS'Faroese (Faroe Islands)' p54 (S'fo_FO' S'iso01' S'lat0-sun16' tsS'Galician (Spain)' p55 (S'gl_ES@euro' S'iso15' S'lat0-sun16' tsS'English (New Zealand)' p56 (S'en_NZ' S'iso01' S'lat0-sun16' tsS'Spanish (Bolivia)' p57 (S'es_BO' S'iso01' S'lat0-sun16' tsS'Cornish (Britain)' p58 (S'kw_GB' S'iso01' S'lat0-sun16' tsS'Arabic (United Arab Emirates)' p59 (S'ar_AE' S'iso06' S'LatArCyrHeb-16' tsS'German (Austria)' p60 (S'de_AT@euro' S'iso15' S'lat0-sun16' tsS'Romanian' p61 (S'ro_RO' S'iso02' S'lat2-sun16' tsS'Spanish (Paraguay)' p62 (S'es_PY' S'iso01' S'lat0-sun16' tsS'Hebrew (Israel)' p63 (S'he_IL' S'iso08' S'LatArCyrHeb-16' tsS'English (USA)' p64 (S'en_US' p65 S'iso01' p66 S'lat0-sun16' p67 tsS'Spanish (USA)' p68 (S'es_US' S'iso01' S'lat0-sun16' tsS'Portuguese (Brasil)' p69 (S'pt_BR' S'iso01' S'lat0-sun16' tsS'Spanish (Equador)' p70 (S'es_EC' S'iso01' S'lat0-sun16' tsS'Polish' p71 (S'pl_PL' S'iso02' S'lat2-sun16' tsS'Slovak' p72 (S'sk_SK' S'iso02' S'lat2-sun16' tsS'Macedonian' p73 (S'mk_MK' S'iso05' S'cyr-sun16' tsS'Spanish (Spain)' p74 (S'es_ES@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Chile)' p75 (S'es_CL' S'iso01' S'lat0-sun16' tsS'Arabic (Syrian Arab Republic)' p76 (S'ar_SY' S'iso06' S'LatArCyrHeb-16' tsS'Czech' p77 (S'cs_CZ' S'iso02' S'lat2-sun16' tsS'Irish' p78 (S'ga_IE@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Jordan)' p79 (S'ar_JO' S'iso06' S'LatArCyrHeb-16' tsS'Italian (Switzerland)' p80 (S'it_CH' S'iso01' S'lat0-sun16' tsS'German (Belgium)' p81 (S'de_BE@euro' S'iso15' S'lat0-sun16' tsS'Albanian' p82 (S'sq_AL' S'iso01' S'lat0-sun16' tsS'Finnish' p83 (S'fi_FI@euro' S'iso15' S'lat0-sun16' tsS'Swedish (Sweden)' p84 (S'sv_SE' S'iso01' S'lat0-sun16' tsS'English (Singapore)' p85 (S'en_SG' S'iso01' S'lat0-sun16' tsS'Dutch (Belgium)' p86 (S'nl_BE@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Panama)' p87 (S'es_PA' S'iso01' S'lat0-sun16' tsS'Spanish (Venezuela)' p88 (S'es_VE' S'iso01' S'lat0-sun16' tsS'English (Great Britain)' p89 (S'en_GB' S'iso01' S'lat0-sun16' tsS'Russian' p90 (S'ru_RU.koi8r' S'koi8-u' S'cyr-sun16' tsS'Norwegian, Nynorsk (Norway)' p91 (S'nn_NO' S'iso01' S'lat0-sun16' tsS'English (Zimbabwe)' p92 (S'en_ZW' S'iso01' S'lat0-sun16' tsS'Spanish (Nicaragua)' p93 (S'es_NI' S'iso01' S'lat0-sun16' tsS'German (Luxemburg)' p94 (S'de_LU@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Colombia)' p95 (S'es_CO' S'iso01' S'lat0-sun16' tsS'Basque (Spain)' p96 (S'eu_ES@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Qatar)' p97 (S'ar_QA' S'iso06' S'LatArCyrHeb-16' tsS'Arabic (Egypt)' p98 (S'ar_EG' S'iso06' S'LatArCyrHeb-16' tsS'French (Belgium)' p99 (S'fr_BE@euro' S'iso15' S'lat0-sun16' tsS'English (Ireland)' p100 (S'en_IE@euro' S'iso15' S'lat0-sun16' tsS'Hungarian' p101 (S'hu_HU' S'iso02' S'lat2-sun16' tsS'Arabic (Tunisia)' p102 (S'ar_TN' S'iso06' S'LatArCyrHeb-16' tsS'French (Luxemburg)' p103 (S'fr_LU@euro' S'iso15' S'lat0-sun16' tsS'Japanese' p104 (S'ja_JP.eucJP' S'iso01' S'lat0-16' tsS'Swedish (Finland)' p105 (S'sv_FI@euro' S'iso15' S'lat0-sun16' tsS'Arabic (Saudi Arabia)' p106 (S'ar_SA' S'iso06' S'LatArCyrHeb-16' tsS'Spanish (Dominican Republic)' p107 (S'es_DO' S'iso01' S'lat0-sun16' tsS'French (Canada)' p108 (S'fr_CA' S'iso01' S'lat0-sun16' tsS'English (Canada)' p109 (S'en_CA' S'iso01' S'lat0-sun16' tsS'German (Germany)' p110 (S'de_DE@euro' S'iso15' S'lat0-sun16' tsS'Slovenian (Slovenia)' p111 (S'sl_SI' S'iso02' S'lat2-sun16' tsS'Spanish (Uruguay)' p112 (S'es_UY' S'iso01' S'lat0-sun16' tsS'German (Switzerland)' p113 (S'de_CH' S'iso01' S'lat0-sun16' tsS'English (Hong Kong)' p114 (S'en_HK' S'iso01' S'lat0-sun16' tsS'English (Australia)' p115 (S'en_AU' S'iso01' S'lat0-sun16' tsS'Catalan (Spain)' p116 (S'ca_ES@euro' S'iso15' S'lat0-sun16' tsS'Spanish (Puerto Rico)' p117 (S'es_PR' S'iso01' S'lat0-sun16' tsS'Turkish' p118 (S'tr_TR' S'iso09' S'lat5-sun16' tsS'Estonian' p119 (S'et_EE' S'iso01' S'lat0-sun16' tsS'Arabic (Sudan)' p120 (S'ar_SD' S'iso06' S'LatArCyrHeb-16' tsS'Icelandic' p121 (S'is_IS' S'iso01' S'lat0-sun16' tsS'English (Botswana)' p122 (S'en_BW' S'iso01' S'lat0-sun16' tsS'Manx Gaelic (Britain)' p123 (S'gv_GB' S'iso01' S'lat0-sun16' tssS'allSupportedLangs' p124 (lp125 g46 ag82 ag50 ag29 ag98 ag25 ag79 ag26 ag20 ag23 ag48 ag24 ag97 ag106 ag120 ag76 ag102 ag59 ag17 ag96 ag116 ag53 ag58 ag30 ag77 ag52 ag86 ag42 ag115 ag122 ag109 ag41 ag89 ag114 ag100 ag56 ag49 ag85 ag27 ag64 ag92 ag119 ag54 ag83 ag99 ag108 ag31 ag103 ag28 ag55 ag60 ag81 ag110 ag94 ag113 ag36 ag32 ag63 ag101 ag121 ag51 ag78 ag19 ag80 ag104 ag33 ag73 ag22 ag123 ag47 ag91 ag71 ag69 ag45 ag61 ag90 ag44 ag43 ag72 ag111 ag18 ag57 ag75 ag95 ag40 ag107 ag37 ag70 ag21 ag39 ag35 ag93 ag87 ag62 ag38 ag117 ag74 ag68 ag112 ag88 ag105 ag84 ag118 ag34 asS'info' p126 (dp127 S'SYSFONT' p128 g67 sS'SUPPORTED' p129 NsS'SYSFONTACM' p130 g66 sS'LANG' p131 g65 ssS'supported' p132 (lsS'default' p133 g64 sbsS'instClass' p134 (icustom InstallClass (dp135 S'rootPasswordCrypted' p136 I0 sS'raidList' p137 (lsS'nameserver' p138 S'' sS'x' NsS'rootPassword' p139 NsS'makeBootdisk' p140 I0 sS'installType' p141 NsS'postScript' p142 NsS'earlySwapOn' p143 I0 sS'networkDevice' p144 NsS'fstab' p145 (lsS'clearText' p146 NsS'lilo' p147 (S'mbr' p148 I1 S'' tsg13 NsS'name' p149 S'' sS'postInChroot' p150 I0 sS'pixmap' p151 S'' sS'partitions' p152 (lp153 (S'/boot' p154 (I48 I-1 I0 t(S'' I-1 I0 t(I0 S'xfs' p155 I0 tNta(S'/' (I700 I-1 I1 t(S'' I-1 I0 t(I0 g155 I0 tNta(S'swap' p156 (I128 I256 I1 t(S'' I-1 I0 t(I0 NI0 tNtasS'clearType' p157 S'wkst' p158 sS'gateway' p159 S'' sS'mouse' p160 NsS'packages' p161 NsS'timezone' p162 NsS'zeroMbr' p163 I0 sS'keyboard' p164 NsS'groups' p165 NsS'bootProto' p166 NsS'netmask' p167 S'' sS'langdefault' p168 NsS'skipSteps' p169 (dsS'auth' p170 (I1 I1 I0 S'' I0 S'' I0 I0 S'' S'' I0 S'' S'' S'' I0 S'' S'' tsS'hostname' p171 NsS'langsupported' p172 NsS'showgroups' p173 NsS'ip' p174 S'' sS'firewall' p175 (I-1 I1 (lp176 S'' I0 I0 I0 I0 I0 I0 tsS'defaultRunlevel' p177 NsS'desktop' p178 S'' sS'clearPartText' p179 S'Automatic partitioning will erase any preexisting Linux installations on your system.' p180 sS'clearParts' p181 I2 sbsS'bdstate' p182 S'' sS'extraModules' p183 (lp184 sS'rootpassword' p185 NsS'fdDevice' p186 S'fd0' p187 sS'installSystem' p188 I1 sS'comps' p189 NsS'verifiedState' p190 Nsg170 (itodo Authentication (dp191 S'useNIS' p192 I0 sS'nisServer' p193 S'' sS'useLdap' p194 I0 sS'krb5Kdc' p195 S'' sS'ldapTLS' p196 S'' sS'useHesiod' p197 I0 sS'ldapServer' p198 S'' sS'nisDomain' p199 S'' sS'krb5Realm' p200 S'' sS'useLdapauth' p201 I0 sS'hesiodRhs' p202 S'' sS'useShadow' p203 I1 sS'nisuseBroadcast' p204 I0 sS'useKrb5' p205 I0 sS'useMD5' p206 I1 sS'ldapBasedn' p207 S'' sS'krb5Admin' p208 S'' sS'hesiodLhs' p209 S'' sS'hesiodDlhs' p210 S'' sbsS'users' p211 NsS'hdList' p212 NsS'dhcpState' p213 S'' sS'method' p214 (iimage NfsInstallMethod p215 (dp216 S'tree' p217 S'/mnt/source/.' sbsS'rebuildTime' p218 NsS'initlevel' p219 I3 sS'depthState' p220 S'' sS'isDDC' p221 S'' sS'monitorVsyncState' p222 S'' sS'initState' p223 I0 sS'videoCardOriginalNode' p224 S'' sS'monitorHsyncState' p225 S'' sS'lilostate' p226 S'' sg145 Nsg147 (ililo LiloConfiguration (dp227 S'liloDevice' p228 g148 sS'initrdsMade' p229 (dsS'liloImages' p230 (dsg133 NsS'edd' p231 I0 sS'liloLinear' p232 I1 sS'liloAppend' p233 S'' sbsS'monitorHsync' p234 S'' sS'expert' p235 I0 sS'network' p236 (itodo Network (dp237 S'netdevices' p238 (dp239 S'eth0' p240 (itodo NetworkDevice (dp241 g126 (dp242 S'BOOTPROTO' p243 S'dhcp' sS'ONBOOT' p244 S'yes' sS'DEVICE' p245 g240 ssbssg159 S'' sS'secondaryNS' p246 S'' sg171 S'ip129.mackay.tritus.ca' sS'primaryNS' p247 S'10.200.200.1' sS'domains' p248 (lp249 S'mackay.tritus.ca' asS'isConfigured' p250 I1 sS'readData' p251 I1 sS'ternaryNS' p252 S'' sbsS'probedFlag' p253 S'' sS'upgrade' p254 I0 sS'firewallState' p255 I0 sS'intf' p256 NsS'deadkeyState' p257 S'' sg160 (imouse Mouse p258 (dp259 S'device' p260 S'null' p261 sg126 (dp262 S'XMOUSETYPE' p263 S'none' p264 sS'FULLNAME' p265 S'None - None' sS'MOUSETYPE' p266 g264 ssS'emu' p267 I0 sS'wasProbed' p268 I1 sS'emulate' p269 I0 sbsS'ddruidAlreadySaved' p270 I0 sS'videoRamOriginal' p271 I2 sg162 Nsg163 I0 sg164 (ikbd Keyboard (dp272 S'layout' p273 NsS'model' p274 NsS'type' p275 S'PC' p276 sg126 (dp277 S'KEYBOARDTYPE' p278 S'pc' p279 sS'KEYTABLE' p280 S'us' p281 ssbsS'monitorOriginalNode' p282 S'' sg171 NsS'reconfigOnly' p283 I0 sS'x' (ixf86config XF86Config p284 (dp285 S'monlist' p286 (dsS'keyModel' p287 S'pc101' p288 sS'keyVariant' p289 S'' sS'monids' p290 (dsg260 NsS'monEisa' p291 NsS'state' p292 S'' sS'server' p293 S'XF86_FBDev' p294 sS'files' p295 S'\012# The location of the RGB database. Note, this is the name of the\012# file minus the extension (like ".txt" or ".db"). There is normally\012# no need to change the default.\012\012 RgbPath\011"/usr/X11R6/lib/X11/rgb"\012\012# Multiple FontPath entries are allowed (they are concatenated together)\012# By default, Red Hat 6.0 and later now use a font server independent of\012# the X server to render fonts.\012\012 FontPath "unix/:7100"\012' p296 sS'monHoriz' p297 S'31.5-48.5' p298 sS'devID' p299 S'ATI Mach64' p300 sS'res' p301 S'800x600' p302 sS'descr' p303 S'ATI|264VT [Mach64 VT]' p304 sS'modes' p305 (dp306 S'16' p307 (lp308 g302 assS'keyOptions' p309 S'' sS'vidRam' p310 S'2048' sS'monID' p311 S'Unprobed Monitor' p312 sS'keyLayout' p313 S'us' p314 sS'manualModes' p315 (dsg160 g258 sS'keyRules' p316 S'xfree86' p317 sS'monVert' p318 S'50-70' p319 sS'cardMan' p320 S'ATI MACH64' p321 sS'monSect' p322 S'' sS'primary' p323 I0 sS'skip' p324 I0 sS'probed' p325 I1 sS'monName' p326 NsS'vidCards' p327 (lp328 (dp329 S'SERVER' S'Mach64' sS'DRIVER' S'ati' sS'NOCLOCKPROBE' S'' sS'NAME' g300 sS'VENDOR' p330 g321 sS'CHIPSET' S'ati' sasS'fbDepth' p331 I16 sbsg175 (itodo Firewall (dp332 S'ports' p333 (lsS'trustdevs' p334 g176 sS'dhcp' p335 I0 sS'policy' p336 I1 sS'ssh' p337 I0 sS'telnet' p338 I0 sS'smtp' p339 I0 sS'enabled' p340 I-1 sS'portlist' p341 S'' sS'http' p342 I0 sS'ftp' p343 I0 sbsS'videoCardOriginalName' p344 S'' sS'instPath' p345 S'/mnt/sysimage' p346 sS'videoCardStateName' p347 S'' sS'instTimeLanguage' p348 (itodo InstallTimeLanguage (dp349 S'kbd' p350 (dp351 S'Italian' p352 S'it' sS'Serbian' p353 S'us' sS'Russian' p354 S'ru' sS'English' p355 S'us' sS'Slovak' p356 S'sk-qwerty' sS'Norwegian' p357 S'no-latin1' sS'Swedish' p358 S'se-latin1' sS'Slovenian' p359 S'slovene' sS'French' p360 S'fr-latin1' sS'Japanese' p361 S'jp106' sS'Danish' p362 S'us' sS'Romanian' p363 S'ro' sS'German' p364 S'de-latin1-nodeadkeys' sS'Turkish' p365 S'trq' sS'Hungarian' p366 S'hu' sS'Spanish' p367 S'es' sS'Ukrainian' p368 S'ua' sS'Czech' p369 S'cz-lat2' sS'Portuguese' p370 S'pt-latin1' sS'Icelandic' p371 S'is-latin1' ssS'font' p372 (dp373 g352 S'lat0-sun16' sg353 S'cyr-sun16' sg354 S'cyr-sun16' sg355 S'default8x16' sg356 S'lat2-sun16' sg357 S'lat0-sun16' sg358 S'lat0-sun16' sg359 S'lat2-sun16' sg360 S'lat0-sun16' sg361 S'None' sg362 S'lat0-sun16' sg363 S'lat2-sun16' sg364 S'lat0-16' sg365 S'lat5-sun16' sg366 S'lat2-sun16' sg367 S'lat0-sun16' sg368 S'cyr-sun16' sg369 S'lat2-sun16' sg370 S'lat0-sun16' sg371 S'lat0-sun16' ssS'langNicks' p374 (dp375 g352 S'it_IT' sg353 S'sr_YU' sg354 S'ru_RU.koi8r' sg355 S'en_US' p376 sg356 S'sk_SK' sg357 S'no_NO' sg358 S'sv_SE' sg359 S'sl_SI' sg360 S'fr_FR' sg361 S'ja_JP.eucJP' sg362 S'da_DK' sg363 S'ro_RO' sg364 S'de_DE' sg365 S'tr_TR' sg366 S'hu_HU' sg367 S'es_ES' sg368 S'uk_UA' sg369 S'cs_CZ' sg370 S'pt_PT' sg371 S'is_IS' ssS'tz' p377 (dp378 g352 S'Europe/Rome' sg353 S'Europe/Belgrade' sg354 S'Europe/Moscow' sg355 S'America/New_York' sg356 S'Europe/Bratislava' sg357 S'Europe/Oslo' sg358 S'Europe/Stockholm' sg359 S'Europe/Ljubljana' sg360 S'Europe/Paris' sg361 S'Asia/Tokyo' sg362 S'Europe/Copenhagen' sg363 S'Europe/Bucharest' sg364 S'Europe/Berlin' sg365 S'Europe/Istanbul' sg366 S'Europe/Budapest' sg367 S'Europe/Madrid' sg368 S'Europe/Kiev' sg369 S'Europe/Prague' sg370 S'Europe/Lisbon' sg371 S'Atlantic/Reykjavik' ssS'langList' p379 (lp380 g369 ag362 ag355 ag360 ag364 ag366 ag371 ag352 ag361 ag357 ag370 ag363 ag354 ag353 ag356 ag359 ag367 ag358 ag365 ag368 asS'tempDefault' p381 S'' sS'map' p382 (dp383 g352 S'iso15' sg353 S'iso05' sg354 S'koi8-r' sg355 S'iso01' sg356 S'iso02' sg357 S'iso15' sg358 S'iso15' sg359 S'iso02' sg360 S'iso15' sg361 S'None' sg362 S'iso15' sg363 S'iso02' sg364 S'iso09' sg365 S'iso09' sg366 S'iso02' sg367 S'iso15' sg368 S'koi8-u' sg369 S'iso02' sg370 S'iso15' sg371 S'iso15' ssbsb. --mSxgbZZZvrAyzONB-- From owner-linux-xfs@oss.sgi.com Thu Jul 19 20:56:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K3uWt12196 for linux-xfs-outgoing; Thu, 19 Jul 2001 20:56:32 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K3uTV12174 for ; Thu, 19 Jul 2001 20:56:29 -0700 Received: from ledzep.americas.sgi.com (relay.sgi.com [137.38.226.97] (may be forged)) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id UAA07715 for ; Thu, 19 Jul 2001 20:56:12 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id WAA46983 for ; Thu, 19 Jul 2001 22:55:07 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15NRNa-0000Mh-00 for ; Thu, 19 Jul 2001 22:55:06 -0500 Date: Thu, 19 Jul 2001 22:55:06 -0500 From: Nathan Straz To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP Message-ID: <20010719225506.A701@sgi.com> Mail-Followup-To: "linux-xfs@oss.sgi.com" References: <200107191617.f6JGHwk32337@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107191617.f6JGHwk32337@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 19, 2001 at 11:17:58AM -0500, Steve Lord wrote: > If you choose another partition (non raid5) for the log and make an external > log instead of using an internal log then the issue should go away, we > are going to test this here. I built a 2.4.7-pre8-xfs kernel from CVS + qlogicfc (from Data Foundation Inc.) and installed that on our test system with a 51GB RAID5 using 7 disks, no spares. I started out using an internal log. I used the OpenBSD 2.9 source tarball as test data to extract to the RAID over NFS. The internal log performance was pretty poor. It took me about 13 minutes to extract the whole thing and I got sick of waiting for the `rm -r` so I stopped it early and removed it locally, which was still slow. I remade the file system with an external 100M log. Extracting took 1:45 (that 1 minute, 45 seconds). Removal took 4:27. Still not the best, but considerably better. I still noticed some stalls along the way. XFS writes fluctuated between 1 MB/s and 5 MB/s. Removes where going at about 150/s. Granted, I'm using a totally different driver than I was before. I'm going to work on getting the official (beta 4.27) Qlogic driver working. -- Nate Straz nstraz@sgi.com sgi, inc http://www.sgi.com/ Linux Test Project http://ltp.sf.net/ From owner-linux-xfs@oss.sgi.com Thu Jul 19 22:47:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K5lqf18743 for linux-xfs-outgoing; Thu, 19 Jul 2001 22:47:52 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K5leV18706 for ; Thu, 19 Jul 2001 22:47:40 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id HAA23828 for ; Fri, 20 Jul 2001 07:47:24 +0200 (CEST) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id WAA67226; Thu, 19 Jul 2001 22:46:53 -0700 (PDT) Message-ID: <3B57C53C.CB467075@sgi.com> Date: Fri, 20 Jul 2001 00:44:28 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Adam Sherman CC: linux-xfs@oss.sgi.com Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid References: <20010719155130.D1330@de.tecosim.com> <995563148.12920.41.camel@stout.americas.sgi.com> <20010719233643.E9205@tritus.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adam Sherman wrote: > I couldn't get the Jul19-12 > installer to save the dump to a floppy, it couldn't access > "/tmp/floppy" for some reason. Probably because it had the update disk in there... :( > It's dump starts out similar then > complains about and "AttributeError: set_active". Can you send any more information on the dump with the update disk? A file and line number would be most helpful, or if you can deduce which variable seems to be lacking the "set_active" method. This is a different error than the raid problem, it seems. -Eric From owner-linux-xfs@oss.sgi.com Thu Jul 19 22:54:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K5seP19239 for linux-xfs-outgoing; Thu, 19 Jul 2001 22:54:40 -0700 Received: from camdb.vilcom.com (IDENT:root@[199.72.107.235]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K5sdV19220 for ; Thu, 19 Jul 2001 22:54:39 -0700 Received: from towerpc (64-40-83-60.mb.dsl.mebtel.net [64.40.83.60]) by camdb.vilcom.com (8.9.3/8.9.3) with ESMTP id CAA27389 for ; Fri, 20 Jul 2001 02:02:18 -0400 From: "Steven Tower" To: Subject: External log and possibilities. Date: Fri, 20 Jul 2001 01:54:42 -0400 Message-ID: <001d01c110e0$78a0b000$3c532840@towerpc> 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.2616 In-reply-to: <20010719225506.A701@sgi.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2505.0000 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I want wondering if anyone here was aware of non-volatile RAM devices 128m-1g and would such a device work with Linux and then allow you to use an external log to read/write to them. I would expect that if it's based on SDRAM, etc it would make for some interesting performance gains. Anyone have any thoughts on this? Steven From owner-linux-xfs@oss.sgi.com Thu Jul 19 23:17:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K6HEO20691 for linux-xfs-outgoing; Thu, 19 Jul 2001 23:17:14 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K6HBV20668 for ; Thu, 19 Jul 2001 23:17:12 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA15905; Fri, 20 Jul 2001 08:17:01 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA13790; Fri, 20 Jul 2001 08:17:00 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id E3FDC57306; Fri, 20 Jul 2001 08:26:11 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 20B6725835; Fri, 20 Jul 2001 08:34:03 +0200 (CEST) Message-ID: <3B57CCB9.4386DD23@ch.sauter-bc.com> Date: Fri, 20 Jul 2001 08:16:25 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Steve Lord Cc: Tru Huynh , jjaakkol@cs.Helsinki.FI, "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <200107191812.f6JICsI32762@jen.americas.sgi.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord schrieb: > > > A little update, > > > > At least, some better news: > > I did *NOT* see the problem (yet!) with the noapic option > > with 2.4.7pre8-SMP > > I am informed that there is a fix in the latest kernels in the raid5 code > to fix some stall issues which ext3 hit. So it maybe that the answer here > is to run the latest kernels. I still do not like the fact we do non-stripe > friendly I/O to the log, and want to look into that. > > Jani, this may also be the source of your problems, we did experience > an almost complete lockup here with the 1.0.1 rpm kernel. If you get a I'd like to reproduce this 'almost complete lockup' here, how can I do this. I mean do I need SMP to reproduce this and what kind operation did you do on the filesystem to force the lookup? Are we safe on UP? > chance can you run the latest cvs kernel? > > Steve > > > > > Steve Lord wrote: > > > > > <...> > > > > > If you choose another partition (non raid5) for the log and make an externa > > l > > > log instead of using an internal log then the issue should go away, we > > > are going to test this here. I suppose a mirrored log would be the best > > > solution here as you could still survive the loss of a drive with the > > > log on it. > > > > I wish I could do that :) > > - hda and hdc on a raid 1 array (system disk) + mirrored xfs log > > - sda..sdh for a 7 disk + 1 hot spare disk for the raid5 array. > > > > The only issue is space, trying to squeeze a second IDE disk > > on the second IDE controller will not easily be manageable is > > the rack :( > > I do have a spare system disk on the shelf, and quick method to > > restore the system disk but I would not risk putting the xfs log > > on this lone disk. > > > > What if I cut the 8 disks in 2 parts > > 1st partition of sd[a..d] of 2 GB (enough?) for a raid10 array for the > > log > > 2nd partition of sd[a..g] for the main raid5 array > > sdh for the hot spare? > > > > Best regards, > > > > Tru > > -- > > Dr Tru Huynh | Bioinformatique Structurale > > mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 > > Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Thu Jul 19 23:25:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K6P2p21129 for linux-xfs-outgoing; Thu, 19 Jul 2001 23:25:02 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K6P0V21110 for ; Thu, 19 Jul 2001 23:25:00 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA16704; Fri, 20 Jul 2001 08:24:57 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA14337; Fri, 20 Jul 2001 08:24:55 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 9BEE657306; Fri, 20 Jul 2001 08:34:47 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id D571C25835; Fri, 20 Jul 2001 08:42:38 +0200 (CEST) Message-ID: <3B57CEBD.DE8F911D@ch.sauter-bc.com> Date: Fri, 20 Jul 2001 08:25:01 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Dean Brissinger Cc: linux-xfs@oss.sgi.com Subject: Re: unable to open initial console [devfs?] References: <17376.993612424@kao2.melbourne.sgi.com> <3B395DED.FDFC6C3D@sgi.com> <20010627011411.A17429@wwweasel.geeksrus.net> <3B39F478.77AEA2B@sgi.com> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dean Brissinger schrieb: > > I used the 2.4.5/1.0.1 RPM to upgrade my Redhat system (built > w/ XFS 1.0 CD). The kernel seems happy but upon booting reports > "unable to open initial console". I've seen this before when messing > with devfs. It basically means /dev/ is missing device files. I > read a while back that this kernel has devfs disabled by default. Is > there a trick to get the standard /dev back when upgrading from 1.0 > to 1.0.1 RPM's? If devfs is not mounted you should have your old /dev visible. Did you delete /dev when messing with devfs? If so, you can just boot with devfs enabled, grab the hole /dev from somewhere and manage to put it on your disk. -Simon From owner-linux-xfs@oss.sgi.com Fri Jul 20 00:02:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K72eN23385 for linux-xfs-outgoing; Fri, 20 Jul 2001 00:02:40 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K72HV23348 for ; Fri, 20 Jul 2001 00:02:18 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA21368; Fri, 20 Jul 2001 09:02:04 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA17237; Fri, 20 Jul 2001 09:01:59 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id 2A17A57306; Fri, 20 Jul 2001 09:11:47 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 8208B25835; Fri, 20 Jul 2001 09:19:33 +0200 (CEST) Message-ID: <3B57D763.73DBB051@ch.sauter-bc.com> Date: Fri, 20 Jul 2001 09:01:56 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Adam Sherman Cc: Eric Sandeen , linux-xfs@oss.sgi.com Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid References: <20010719155130.D1330@de.tecosim.com> <995563148.12920.41.camel@stout.americas.sgi.com> <20010719233643.E9205@tritus.ca> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adam Sherman schrieb: > > On Thu, Jul 19, 2001 at 12:19:07PM -0500, Eric Sandeen wrote: > > Ok, I put a new update disk in the updates/ directory under > > Release-1.0.1/installer/updates. This should fix things for you. > > I'm having possibly similar issues, with or without the Jul19-12 > update disk. Here's my dump after clicking the next button of the > disk druid screen: > > **start*dump** > Traceback (innermost last): > File "/usr/bin/anaconda", line 520, in ? > intf.run(todo, test = test) > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 392, in > run > self.icw.run () > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 880, in > run > mainloop () > File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in > mainloop > _gtk.gtk_main() > File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in > __call__ > ret = apply(self.func, a) > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 482, in > nextClicked > next = self.currentScreen.getNext () > File > "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", > line 130, in getNext > rc = self.lba32Check () > File > "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", > line 76, in lba32Check > maxcyl = self.todo.fstab.getBootPartitionMaxCylFromDesired() > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 241, > in getBootPartitionMaxCylFromDesired > bootpart = self.getBootDevice() > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, > in getBootDevice > for (mntpoint, partition, fsystem, doFormat, size) in > self.mountList(): > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1052, > in mountList > if fsType == "swap": continue > NameError: fsType > **end*dump** > > My setup is a smp box with two IDE disks, hda & hdc. It has 128MB of > RAM and a tulip based NIC. I'm installing using the 1.0.1 release > freshly downloaded and exported over NFS. I want RAID1 mirrored > everything which amounts to a 32MB boot, 750MB root, 1.3GB var and > 256MB swap. All using XFS. > > I get this error either right away when clicking next in the Disk > Druid screen if I'm using standard 1.0.1 or after the format > partitions screen if I'm using the Jul19-12 update. I'm attaching the > dump from the standard install, but I couldn't get the Jul19-12 > installer to save the dump to a floppy, it couldn't access > "/tmp/floppy" for some reason. It's dump starts out similar then > complains about and "AttributeError: set_active". > > Any suggestions? I'm not sure whether I can help alot but I have made my own rules how to install my RAID systems: 1) When creating RAID, ALWAYS start with /dev/md0 and then md1 and so on. 2) Never put SWAP on RAID at install time. Make one of the RAID partitions (the one you want to use to build the swap raid) to be your swap. Reboot, swapoff, create the RAID by hand and create swap on it. Those are my own rules and it has always worked for me. -Simon > > Thanks, > > A. > > P.S. I'm in a rush because I've got to have this box up by Friday... )-: > > -- > Adam Sherman > President & Technology Architect > Tritus Consultant Group Inc. > +1.613.255.5164 > http://www.tritus.ca > > ------------------------------------------------------------------------ > Traceback (innermost last): > File "/usr/bin/anaconda", line 520, in ? > intf.run(todo, test = test) > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 392, in run > self.icw.run () > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 880, in run > mainloop () > File "/usr/lib/python1.5/site-packages/gtk.py", line 2554, in mainloop > _gtk.gtk_main() > File "/usr/lib/python1.5/site-packages/gtk.py", line 125, in __call__ > ret = apply(self.func, a) > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/gui.py", line 482, in nextClicked > next = self.currentScreen.getNext () > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 130, in getNext > rc = self.lba32Check () > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/iw/rootpartition_gui.py", line 76, in lba32Check > maxcyl = self.todo.fstab.getBootPartitionMaxCylFromDesired() > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 241, in getBootPartitionMaxCylFromDesired > bootpart = self.getBootDevice() > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 267, in getBootDevice > for (mntpoint, partition, fsystem, doFormat, size) in self.mountList(): > File "/var/tmp/anaconda-7.1//usr/lib/anaconda/fstab.py", line 1052, in mountList > if fsType == "swap": continue > NameError: fsType > > Local variables in innermost frame: > size: 66465 > mntpoint: /boot > makeup: ['Raid001', 'Raid000'] > device: md0 > raidType: 1 > start: 63 > sortMounts: > devices: [('hdc1', 'Raid001', 7, 63, 66465, 66, 0), ('hda1', 'Raid000', 7, 63, 72513, 9, 0), ('hda5', 'Raid002', 7, 72639, 1540161, 200, 0), ('hdc5', 'Raid003', 7, 66591, 1536129, 1590, 0), ('hda6', 'Raid004', 7, 1612863, 532161, 266, 0), ('hdc6', 'Raid005', 7, 1602783, 525105, 2111, 0), ('hda7', 'Raid006', 7, 2145087, 2854593, 620, 0), ('hdc7', 'Raid007', 7, 2127951, 2998737, 5086, 0)] > fstab: [] > self: > fsystem: xfs > raid: [('/boot', 'md0', 'xfs', 1, 63, 66465, ['Raid001', 'Raid000']), ('/', 'md1', 'xfs', 1, 63, 72513, ['Raid002', 'Raid003']), ('', 'md3', 'swap', 1, 72639, 1540161, ['Raid004', 'Raid005']), ('/var', 'md2', 'xfs', 1, 66591, 1536129, ['Raid006', 'Raid007'])] > skipExtra: 0 > > ToDo object: > (itodo > ToDo > p1 > (dp2 > S'resState' > p3 > S'' > sS'progressWindow' > p4 > NsS'setupFilesystems' > p5 > I1 > sS'monitorVsync' > p6 > S'' > sS'videoCardStateNode' > p7 > S'' > sS'serial' > p8 > I0 > sS'ddruidReadOnly' > p9 > I0 > sS'bootdisk' > p10 > I0 > sS'videoRamState' > p11 > S'' > sS'monitorOriginalName' > p12 > S'' > sS'language' > p13 > (itodo > Language > (dp14 > S'langInfoByName' > p15 > (dp16 > S'Arabic (Yemen)' > p17 > (S'ar_YE' > S'iso06' > S'LatArCyrHeb-16' > tsS'Spanish (Argentina)' > p18 > (S'es_AR' > S'iso01' > S'lat0-sun16' > tsS'Italian (Italy)' > p19 > (S'it_IT@euro' > S'iso15' > S'lat0-sun16' > tsS'Arabic (Lebanon)' > p20 > (S'ar_LB' > S'iso06' > S'LatArCyrHeb-16' > tsS'Spanish (Guatemala)' > p21 > (S'es_GT' > S'iso01' > S'lat0-sun16' > tsS'Malay (Malaysia)' > p22 > (S'ms_MY' > S'iso01' > S'lat0-sun16' > tsS'Arabic (Libyan Arab Jamahiriya)' > p23 > (S'ar_LY' > S'iso06' > S'LatArCyrHeb-16' > tsS'Arabic (Oman)' > p24 > (S'ar_OM' > S'iso06' > S'LatArCyrHeb-16' > tsS'Arabic (Iraq)' > p25 > (S'ar_IQ' > S'iso06' > S'LatArCyrHeb-16' > tsS'Arabic (Kuwait)' > p26 > (S'ar_KW' > S'iso06' > S'LatArCyrHeb-16' > tsS'English (South Africa)' > p27 > (S'en_ZA' > S'iso01' > S'lat0-sun16' > tsS'French (Switzerland)' > p28 > (S'fr_CH' > S'iso01' > S'lat0-sun16' > tsS'Arabic (Bahrein)' > p29 > (S'ar_BH' > S'iso06' > S'LatArCyrHeb-16' > tsS'Croatian' > p30 > (S'hr_HR' > S'iso02' > S'lat2-sun16' > tsS'French (France)' > p31 > (S'fr_FR@euro' > S'iso15' > S'lat0-sun16' > tsS'Greenlandic (Greenland)' > p32 > (S'kl_GL' > S'iso01' > S'lat0-sun16' > tsS'Korean (Republic of Korea)' > p33 > (S'ko_KR.euckr' > S'iso01' > S'lat0-16' > tsS'Ukrainian' > p34 > (S'uk_UA' > S'koi8-u' > S'cyr-sun16' > tsS'Spanish (Mexico)' > p35 > (S'es_MX' > S'iso01' > S'lat0-sun16' > tsS'Greek' > p36 > (S'el_GR' > S'iso07' > S'gr.f16' > tsS'Spanish (El Salvador)' > p37 > (S'es_SV' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Peru)' > p38 > (S'es_PE' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Honduras)' > p39 > (S'es_HN' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Costa Rica)' > p40 > (S'es_CR' > S'iso01' > S'lat0-sun16' > tsS'English (Denmark)' > p41 > (S'en_DK' > S'iso01' > S'lat0-sun16' > tsS'Dutch (Netherlands)' > p42 > (S'nl_NL@euro' > S'iso15' > S'lat0-sun16' > tsS'Serbian (Yugoslavia)' > p43 > (S'sr_YU@cyrillic' > S'iso05' > S'cyr-sun16' > tsS'Russian (Ukraine)' > p44 > (S'ru_UA' > S'koi8-u' > S'cyr-sun16' > tsS'Portuguese (Portugal)' > p45 > (S'pt_PT@euro' > S'iso15' > S'lat0-sun16' > tsS'Afrikaans (South Africa)' > p46 > (S'af_ZA' > S'iso01' > S'lat0-sun16' > tsS'Norwegian' > p47 > (S'no_NO' > S'iso01' > S'lat0-sun16' > tsS'Arabic (Morocco)' > p48 > (S'ar_MA' > S'iso06' > S'LatArCyrHeb-16' > tsS'English (Philippines)' > p49 > (S'en_PH' > S'iso01' > S'lat0-sun16' > tsS'Arabic (Algeria)' > p50 > (S'ar_DZ' > S'iso06' > S'LatArCyrHeb-16' > tsS'Indonesian' > p51 > (S'id_ID' > S'iso01' > S'lat0-sun16' > tsS'Danish' > p52 > (S'da_DK' > S'iso01' > S'lat0-sun16' > tsS'Chinese (Taiwan R.O.C.)' > p53 > (S'zh_TW.euctw' > S'iso01' > S'lat0-16' > tsS'Faroese (Faroe Islands)' > p54 > (S'fo_FO' > S'iso01' > S'lat0-sun16' > tsS'Galician (Spain)' > p55 > (S'gl_ES@euro' > S'iso15' > S'lat0-sun16' > tsS'English (New Zealand)' > p56 > (S'en_NZ' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Bolivia)' > p57 > (S'es_BO' > S'iso01' > S'lat0-sun16' > tsS'Cornish (Britain)' > p58 > (S'kw_GB' > S'iso01' > S'lat0-sun16' > tsS'Arabic (United Arab Emirates)' > p59 > (S'ar_AE' > S'iso06' > S'LatArCyrHeb-16' > tsS'German (Austria)' > p60 > (S'de_AT@euro' > S'iso15' > S'lat0-sun16' > tsS'Romanian' > p61 > (S'ro_RO' > S'iso02' > S'lat2-sun16' > tsS'Spanish (Paraguay)' > p62 > (S'es_PY' > S'iso01' > S'lat0-sun16' > tsS'Hebrew (Israel)' > p63 > (S'he_IL' > S'iso08' > S'LatArCyrHeb-16' > tsS'English (USA)' > p64 > (S'en_US' > p65 > S'iso01' > p66 > S'lat0-sun16' > p67 > tsS'Spanish (USA)' > p68 > (S'es_US' > S'iso01' > S'lat0-sun16' > tsS'Portuguese (Brasil)' > p69 > (S'pt_BR' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Equador)' > p70 > (S'es_EC' > S'iso01' > S'lat0-sun16' > tsS'Polish' > p71 > (S'pl_PL' > S'iso02' > S'lat2-sun16' > tsS'Slovak' > p72 > (S'sk_SK' > S'iso02' > S'lat2-sun16' > tsS'Macedonian' > p73 > (S'mk_MK' > S'iso05' > S'cyr-sun16' > tsS'Spanish (Spain)' > p74 > (S'es_ES@euro' > S'iso15' > S'lat0-sun16' > tsS'Spanish (Chile)' > p75 > (S'es_CL' > S'iso01' > S'lat0-sun16' > tsS'Arabic (Syrian Arab Republic)' > p76 > (S'ar_SY' > S'iso06' > S'LatArCyrHeb-16' > tsS'Czech' > p77 > (S'cs_CZ' > S'iso02' > S'lat2-sun16' > tsS'Irish' > p78 > (S'ga_IE@euro' > S'iso15' > S'lat0-sun16' > tsS'Arabic (Jordan)' > p79 > (S'ar_JO' > S'iso06' > S'LatArCyrHeb-16' > tsS'Italian (Switzerland)' > p80 > (S'it_CH' > S'iso01' > S'lat0-sun16' > tsS'German (Belgium)' > p81 > (S'de_BE@euro' > S'iso15' > S'lat0-sun16' > tsS'Albanian' > p82 > (S'sq_AL' > S'iso01' > S'lat0-sun16' > tsS'Finnish' > p83 > (S'fi_FI@euro' > S'iso15' > S'lat0-sun16' > tsS'Swedish (Sweden)' > p84 > (S'sv_SE' > S'iso01' > S'lat0-sun16' > tsS'English (Singapore)' > p85 > (S'en_SG' > S'iso01' > S'lat0-sun16' > tsS'Dutch (Belgium)' > p86 > (S'nl_BE@euro' > S'iso15' > S'lat0-sun16' > tsS'Spanish (Panama)' > p87 > (S'es_PA' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Venezuela)' > p88 > (S'es_VE' > S'iso01' > S'lat0-sun16' > tsS'English (Great Britain)' > p89 > (S'en_GB' > S'iso01' > S'lat0-sun16' > tsS'Russian' > p90 > (S'ru_RU.koi8r' > S'koi8-u' > S'cyr-sun16' > tsS'Norwegian, Nynorsk (Norway)' > p91 > (S'nn_NO' > S'iso01' > S'lat0-sun16' > tsS'English (Zimbabwe)' > p92 > (S'en_ZW' > S'iso01' > S'lat0-sun16' > tsS'Spanish (Nicaragua)' > p93 > (S'es_NI' > S'iso01' > S'lat0-sun16' > tsS'German (Luxemburg)' > p94 > (S'de_LU@euro' > S'iso15' > S'lat0-sun16' > tsS'Spanish (Colombia)' > p95 > (S'es_CO' > S'iso01' > S'lat0-sun16' > tsS'Basque (Spain)' > p96 > (S'eu_ES@euro' > S'iso15' > S'lat0-sun16' > tsS'Arabic (Qatar)' > p97 > (S'ar_QA' > S'iso06' > S'LatArCyrHeb-16' > tsS'Arabic (Egypt)' > p98 > (S'ar_EG' > S'iso06' > S'LatArCyrHeb-16' > tsS'French (Belgium)' > p99 > (S'fr_BE@euro' > S'iso15' > S'lat0-sun16' > tsS'English (Ireland)' > p100 > (S'en_IE@euro' > S'iso15' > S'lat0-sun16' > tsS'Hungarian' > p101 > (S'hu_HU' > S'iso02' > S'lat2-sun16' > tsS'Arabic (Tunisia)' > p102 > (S'ar_TN' > S'iso06' > S'LatArCyrHeb-16' > tsS'French (Luxemburg)' > p103 > (S'fr_LU@euro' > S'iso15' > S'lat0-sun16' > tsS'Japanese' > p104 > (S'ja_JP.eucJP' > S'iso01' > S'lat0-16' > tsS'Swedish (Finland)' > p105 > (S'sv_FI@euro' > S'iso15' > S'lat0-sun16' > tsS'Arabic (Saudi Arabia)' > p106 > (S'ar_SA' > S'iso06' > S'LatArCyrHeb-16' > tsS'Spanish (Dominican Republic)' > p107 > (S'es_DO' > S'iso01' > S'lat0-sun16' > tsS'French (Canada)' > p108 > (S'fr_CA' > S'iso01' > S'lat0-sun16' > tsS'English (Canada)' > p109 > (S'en_CA' > S'iso01' > S'lat0-sun16' > tsS'German (Germany)' > p110 > (S'de_DE@euro' > S'iso15' > S'lat0-sun16' > tsS'Slovenian (Slovenia)' > p111 > (S'sl_SI' > S'iso02' > S'lat2-sun16' > tsS'Spanish (Uruguay)' > p112 > (S'es_UY' > S'iso01' > S'lat0-sun16' > tsS'German (Switzerland)' > p113 > (S'de_CH' > S'iso01' > S'lat0-sun16' > tsS'English (Hong Kong)' > p114 > (S'en_HK' > S'iso01' > S'lat0-sun16' > tsS'English (Australia)' > p115 > (S'en_AU' > S'iso01' > S'lat0-sun16' > tsS'Catalan (Spain)' > p116 > (S'ca_ES@euro' > S'iso15' > S'lat0-sun16' > tsS'Spanish (Puerto Rico)' > p117 > (S'es_PR' > S'iso01' > S'lat0-sun16' > tsS'Turkish' > p118 > (S'tr_TR' > S'iso09' > S'lat5-sun16' > tsS'Estonian' > p119 > (S'et_EE' > S'iso01' > S'lat0-sun16' > tsS'Arabic (Sudan)' > p120 > (S'ar_SD' > S'iso06' > S'LatArCyrHeb-16' > tsS'Icelandic' > p121 > (S'is_IS' > S'iso01' > S'lat0-sun16' > tsS'English (Botswana)' > p122 > (S'en_BW' > S'iso01' > S'lat0-sun16' > tsS'Manx Gaelic (Britain)' > p123 > (S'gv_GB' > S'iso01' > S'lat0-sun16' > tssS'allSupportedLangs' > p124 > (lp125 > g46 > ag82 > ag50 > ag29 > ag98 > ag25 > ag79 > ag26 > ag20 > ag23 > ag48 > ag24 > ag97 > ag106 > ag120 > ag76 > ag102 > ag59 > ag17 > ag96 > ag116 > ag53 > ag58 > ag30 > ag77 > ag52 > ag86 > ag42 > ag115 > ag122 > ag109 > ag41 > ag89 > ag114 > ag100 > ag56 > ag49 > ag85 > ag27 > ag64 > ag92 > ag119 > ag54 > ag83 > ag99 > ag108 > ag31 > ag103 > ag28 > ag55 > ag60 > ag81 > ag110 > ag94 > ag113 > ag36 > ag32 > ag63 > ag101 > ag121 > ag51 > ag78 > ag19 > ag80 > ag104 > ag33 > ag73 > ag22 > ag123 > ag47 > ag91 > ag71 > ag69 > ag45 > ag61 > ag90 > ag44 > ag43 > ag72 > ag111 > ag18 > ag57 > ag75 > ag95 > ag40 > ag107 > ag37 > ag70 > ag21 > ag39 > ag35 > ag93 > ag87 > ag62 > ag38 > ag117 > ag74 > ag68 > ag112 > ag88 > ag105 > ag84 > ag118 > ag34 > asS'info' > p126 > (dp127 > S'SYSFONT' > p128 > g67 > sS'SUPPORTED' > p129 > NsS'SYSFONTACM' > p130 > g66 > sS'LANG' > p131 > g65 > ssS'supported' > p132 > (lsS'default' > p133 > g64 > sbsS'instClass' > p134 > (icustom > InstallClass > (dp135 > S'rootPasswordCrypted' > p136 > I0 > sS'raidList' > p137 > (lsS'nameserver' > p138 > S'' > sS'x' > NsS'rootPassword' > p139 > NsS'makeBootdisk' > p140 > I0 > sS'installType' > p141 > NsS'postScript' > p142 > NsS'earlySwapOn' > p143 > I0 > sS'networkDevice' > p144 > NsS'fstab' > p145 > (lsS'clearText' > p146 > NsS'lilo' > p147 > (S'mbr' > p148 > I1 > S'' > tsg13 > NsS'name' > p149 > S'' > sS'postInChroot' > p150 > I0 > sS'pixmap' > p151 > S'' > sS'partitions' > p152 > (lp153 > (S'/boot' > p154 > (I48 > I-1 > I0 > t(S'' > I-1 > I0 > t(I0 > S'xfs' > p155 > I0 > tNta(S'/' > (I700 > I-1 > I1 > t(S'' > I-1 > I0 > t(I0 > g155 > I0 > tNta(S'swap' > p156 > (I128 > I256 > I1 > t(S'' > I-1 > I0 > t(I0 > NI0 > tNtasS'clearType' > p157 > S'wkst' > p158 > sS'gateway' > p159 > S'' > sS'mouse' > p160 > NsS'packages' > p161 > NsS'timezone' > p162 > NsS'zeroMbr' > p163 > I0 > sS'keyboard' > p164 > NsS'groups' > p165 > NsS'bootProto' > p166 > NsS'netmask' > p167 > S'' > sS'langdefault' > p168 > NsS'skipSteps' > p169 > (dsS'auth' > p170 > (I1 > I1 > I0 > S'' > I0 > S'' > I0 > I0 > S'' > S'' > I0 > S'' > S'' > S'' > I0 > S'' > S'' > tsS'hostname' > p171 > NsS'langsupported' > p172 > NsS'showgroups' > p173 > NsS'ip' > p174 > S'' > sS'firewall' > p175 > (I-1 > I1 > (lp176 > S'' > I0 > I0 > I0 > I0 > I0 > I0 > tsS'defaultRunlevel' > p177 > NsS'desktop' > p178 > S'' > sS'clearPartText' > p179 > S'Automatic partitioning will erase any preexisting Linux installations on your system.' > p180 > sS'clearParts' > p181 > I2 > sbsS'bdstate' > p182 > S'' > sS'extraModules' > p183 > (lp184 > sS'rootpassword' > p185 > NsS'fdDevice' > p186 > S'fd0' > p187 > sS'installSystem' > p188 > I1 > sS'comps' > p189 > NsS'verifiedState' > p190 > Nsg170 > (itodo > Authentication > (dp191 > S'useNIS' > p192 > I0 > sS'nisServer' > p193 > S'' > sS'useLdap' > p194 > I0 > sS'krb5Kdc' > p195 > S'' > sS'ldapTLS' > p196 > S'' > sS'useHesiod' > p197 > I0 > sS'ldapServer' > p198 > S'' > sS'nisDomain' > p199 > S'' > sS'krb5Realm' > p200 > S'' > sS'useLdapauth' > p201 > I0 > sS'hesiodRhs' > p202 > S'' > sS'useShadow' > p203 > I1 > sS'nisuseBroadcast' > p204 > I0 > sS'useKrb5' > p205 > I0 > sS'useMD5' > p206 > I1 > sS'ldapBasedn' > p207 > S'' > sS'krb5Admin' > p208 > S'' > sS'hesiodLhs' > p209 > S'' > sS'hesiodDlhs' > p210 > S'' > sbsS'users' > p211 > NsS'hdList' > p212 > NsS'dhcpState' > p213 > S'' > sS'method' > p214 > (iimage > NfsInstallMethod > p215 > (dp216 > S'tree' > p217 > S'/mnt/source/.' > sbsS'rebuildTime' > p218 > NsS'initlevel' > p219 > I3 > sS'depthState' > p220 > S'' > sS'isDDC' > p221 > S'' > sS'monitorVsyncState' > p222 > S'' > sS'initState' > p223 > I0 > sS'videoCardOriginalNode' > p224 > S'' > sS'monitorHsyncState' > p225 > S'' > sS'lilostate' > p226 > S'' > sg145 > Nsg147 > (ililo > LiloConfiguration > (dp227 > S'liloDevice' > p228 > g148 > sS'initrdsMade' > p229 > (dsS'liloImages' > p230 > (dsg133 > NsS'edd' > p231 > I0 > sS'liloLinear' > p232 > I1 > sS'liloAppend' > p233 > S'' > sbsS'monitorHsync' > p234 > S'' > sS'expert' > p235 > I0 > sS'network' > p236 > (itodo > Network > (dp237 > S'netdevices' > p238 > (dp239 > S'eth0' > p240 > (itodo > NetworkDevice > (dp241 > g126 > (dp242 > S'BOOTPROTO' > p243 > S'dhcp' > sS'ONBOOT' > p244 > S'yes' > sS'DEVICE' > p245 > g240 > ssbssg159 > S'' > sS'secondaryNS' > p246 > S'' > sg171 > S'ip129.mackay.tritus.ca' > sS'primaryNS' > p247 > S'10.200.200.1' > sS'domains' > p248 > (lp249 > S'mackay.tritus.ca' > asS'isConfigured' > p250 > I1 > sS'readData' > p251 > I1 > sS'ternaryNS' > p252 > S'' > sbsS'probedFlag' > p253 > S'' > sS'upgrade' > p254 > I0 > sS'firewallState' > p255 > I0 > sS'intf' > p256 > NsS'deadkeyState' > p257 > S'' > sg160 > (imouse > Mouse > p258 > (dp259 > S'device' > p260 > S'null' > p261 > sg126 > (dp262 > S'XMOUSETYPE' > p263 > S'none' > p264 > sS'FULLNAME' > p265 > S'None - None' > sS'MOUSETYPE' > p266 > g264 > ssS'emu' > p267 > I0 > sS'wasProbed' > p268 > I1 > sS'emulate' > p269 > I0 > sbsS'ddruidAlreadySaved' > p270 > I0 > sS'videoRamOriginal' > p271 > I2 > sg162 > Nsg163 > I0 > sg164 > (ikbd > Keyboard > (dp272 > S'layout' > p273 > NsS'model' > p274 > NsS'type' > p275 > S'PC' > p276 > sg126 > (dp277 > S'KEYBOARDTYPE' > p278 > S'pc' > p279 > sS'KEYTABLE' > p280 > S'us' > p281 > ssbsS'monitorOriginalNode' > p282 > S'' > sg171 > NsS'reconfigOnly' > p283 > I0 > sS'x' > (ixf86config > XF86Config > p284 > (dp285 > S'monlist' > p286 > (dsS'keyModel' > p287 > S'pc101' > p288 > sS'keyVariant' > p289 > S'' > sS'monids' > p290 > (dsg260 > NsS'monEisa' > p291 > NsS'state' > p292 > S'' > sS'server' > p293 > S'XF86_FBDev' > p294 > sS'files' > p295 > S'\012# The location of the RGB database. Note, this is the name of the\012# file minus the extension (like ".txt" or ".db"). There is normally\012# no need to change the default.\012\012 RgbPath\011"/usr/X11R6/lib/X11/rgb"\012\012# Multiple FontPath entries are allowed (they are concatenated together)\012# By default, Red Hat 6.0 and later now use a font server independent of\012# the X server to render fonts.\012\012 FontPath "unix/:7100"\012' > p296 > sS'monHoriz' > p297 > S'31.5-48.5' > p298 > sS'devID' > p299 > S'ATI Mach64' > p300 > sS'res' > p301 > S'800x600' > p302 > sS'descr' > p303 > S'ATI|264VT [Mach64 VT]' > p304 > sS'modes' > p305 > (dp306 > S'16' > p307 > (lp308 > g302 > assS'keyOptions' > p309 > S'' > sS'vidRam' > p310 > S'2048' > sS'monID' > p311 > S'Unprobed Monitor' > p312 > sS'keyLayout' > p313 > S'us' > p314 > sS'manualModes' > p315 > (dsg160 > g258 > sS'keyRules' > p316 > S'xfree86' > p317 > sS'monVert' > p318 > S'50-70' > p319 > sS'cardMan' > p320 > S'ATI MACH64' > p321 > sS'monSect' > p322 > S'' > sS'primary' > p323 > I0 > sS'skip' > p324 > I0 > sS'probed' > p325 > I1 > sS'monName' > p326 > NsS'vidCards' > p327 > (lp328 > (dp329 > S'SERVER' > S'Mach64' > sS'DRIVER' > S'ati' > sS'NOCLOCKPROBE' > S'' > sS'NAME' > g300 > sS'VENDOR' > p330 > g321 > sS'CHIPSET' > S'ati' > sasS'fbDepth' > p331 > I16 > sbsg175 > (itodo > Firewall > (dp332 > S'ports' > p333 > (lsS'trustdevs' > p334 > g176 > sS'dhcp' > p335 > I0 > sS'policy' > p336 > I1 > sS'ssh' > p337 > I0 > sS'telnet' > p338 > I0 > sS'smtp' > p339 > I0 > sS'enabled' > p340 > I-1 > sS'portlist' > p341 > S'' > sS'http' > p342 > I0 > sS'ftp' > p343 > I0 > sbsS'videoCardOriginalName' > p344 > S'' > sS'instPath' > p345 > S'/mnt/sysimage' > p346 > sS'videoCardStateName' > p347 > S'' > sS'instTimeLanguage' > p348 > (itodo > InstallTimeLanguage > (dp349 > S'kbd' > p350 > (dp351 > S'Italian' > p352 > S'it' > sS'Serbian' > p353 > S'us' > sS'Russian' > p354 > S'ru' > sS'English' > p355 > S'us' > sS'Slovak' > p356 > S'sk-qwerty' > sS'Norwegian' > p357 > S'no-latin1' > sS'Swedish' > p358 > S'se-latin1' > sS'Slovenian' > p359 > S'slovene' > sS'French' > p360 > S'fr-latin1' > sS'Japanese' > p361 > S'jp106' > sS'Danish' > p362 > S'us' > sS'Romanian' > p363 > S'ro' > sS'German' > p364 > S'de-latin1-nodeadkeys' > sS'Turkish' > p365 > S'trq' > sS'Hungarian' > p366 > S'hu' > sS'Spanish' > p367 > S'es' > sS'Ukrainian' > p368 > S'ua' > sS'Czech' > p369 > S'cz-lat2' > sS'Portuguese' > p370 > S'pt-latin1' > sS'Icelandic' > p371 > S'is-latin1' > ssS'font' > p372 > (dp373 > g352 > S'lat0-sun16' > sg353 > S'cyr-sun16' > sg354 > S'cyr-sun16' > sg355 > S'default8x16' > sg356 > S'lat2-sun16' > sg357 > S'lat0-sun16' > sg358 > S'lat0-sun16' > sg359 > S'lat2-sun16' > sg360 > S'lat0-sun16' > sg361 > S'None' > sg362 > S'lat0-sun16' > sg363 > S'lat2-sun16' > sg364 > S'lat0-16' > sg365 > S'lat5-sun16' > sg366 > S'lat2-sun16' > sg367 > S'lat0-sun16' > sg368 > S'cyr-sun16' > sg369 > S'lat2-sun16' > sg370 > S'lat0-sun16' > sg371 > S'lat0-sun16' > ssS'langNicks' > p374 > (dp375 > g352 > S'it_IT' > sg353 > S'sr_YU' > sg354 > S'ru_RU.koi8r' > sg355 > S'en_US' > p376 > sg356 > S'sk_SK' > sg357 > S'no_NO' > sg358 > S'sv_SE' > sg359 > S'sl_SI' > sg360 > S'fr_FR' > sg361 > S'ja_JP.eucJP' > sg362 > S'da_DK' > sg363 > S'ro_RO' > sg364 > S'de_DE' > sg365 > S'tr_TR' > sg366 > S'hu_HU' > sg367 > S'es_ES' > sg368 > S'uk_UA' > sg369 > S'cs_CZ' > sg370 > S'pt_PT' > sg371 > S'is_IS' > ssS'tz' > p377 > (dp378 > g352 > S'Europe/Rome' > sg353 > S'Europe/Belgrade' > sg354 > S'Europe/Moscow' > sg355 > S'America/New_York' > sg356 > S'Europe/Bratislava' > sg357 > S'Europe/Oslo' > sg358 > S'Europe/Stockholm' > sg359 > S'Europe/Ljubljana' > sg360 > S'Europe/Paris' > sg361 > S'Asia/Tokyo' > sg362 > S'Europe/Copenhagen' > sg363 > S'Europe/Bucharest' > sg364 > S'Europe/Berlin' > sg365 > S'Europe/Istanbul' > sg366 > S'Europe/Budapest' > sg367 > S'Europe/Madrid' > sg368 > S'Europe/Kiev' > sg369 > S'Europe/Prague' > sg370 > S'Europe/Lisbon' > sg371 > S'Atlantic/Reykjavik' > ssS'langList' > p379 > (lp380 > g369 > ag362 > ag355 > ag360 > ag364 > ag366 > ag371 > ag352 > ag361 > ag357 > ag370 > ag363 > ag354 > ag353 > ag356 > ag359 > ag367 > ag358 > ag365 > ag368 > asS'tempDefault' > p381 > S'' > sS'map' > p382 > (dp383 > g352 > S'iso15' > sg353 > S'iso05' > sg354 > S'koi8-r' > sg355 > S'iso01' > sg356 > S'iso02' > sg357 > S'iso15' > sg358 > S'iso15' > sg359 > S'iso02' > sg360 > S'iso15' > sg361 > S'None' > sg362 > S'iso15' > sg363 > S'iso02' > sg364 > S'iso09' > sg365 > S'iso09' > sg366 > S'iso02' > sg367 > S'iso15' > sg368 > S'koi8-u' > sg369 > S'iso02' > sg370 > S'iso15' > sg371 > S'iso15' > ssbsb. -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Fri Jul 20 00:11:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K7BGl23976 for linux-xfs-outgoing; Fri, 20 Jul 2001 00:11:16 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K7BEV23956 for ; Fri, 20 Jul 2001 00:11:14 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6K7BAe08023; Fri, 20 Jul 2001 09:11:11 +0200 Message-Id: <4.3.2.7.2.20010720091018.030c56f8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 20 Jul 2001 09:10:56 +0200 To: erich@uruk.org, linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: FYI: Networking bug in RH 7.1 updated config files... In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:31 19-7-2001 -0700, erich@uruk.org wrote: >So, for those who care about TCP/IP compatibility and are compiling >your own kernels, I suggest you remove this option from your >config. I suggest switching it off via the sysctl or echo 0 > /proc/sys/net/ipv4/tcp_ecn Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 20 00:51:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K7p1i26660 for linux-xfs-outgoing; Fri, 20 Jul 2001 00:51:01 -0700 Received: from mail.1ar.org (IDENT:postfix@[202.88.157.33]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K7ouV26631 for ; Fri, 20 Jul 2001 00:50:57 -0700 Received: from localhost (localhost.1ar.org [127.0.0.1]) by mail.1ar.org (Postfix) with ESMTP id E9E041C68DD7 for ; Fri, 20 Jul 2001 13:21:03 +0530 (IST) Date: Fri, 20 Jul 2001 13:21:03 +0530 (IST) From: Ajay Ramaswamy Cc: Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid In-Reply-To: <3B57D763.73DBB051@ch.sauter-bc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The advice I have seen on the RedHat List and also LKML is dont bother with swap on RAID insetad set up multiple swap areas on the different disks the kernel can work out the details regards Ajay From owner-linux-xfs@oss.sgi.com Fri Jul 20 00:58:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K7waF27227 for linux-xfs-outgoing; Fri, 20 Jul 2001 00:58:36 -0700 Received: from tietoe03.tietoenator.com (mail2.tieto.com [194.110.47.97]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K7wXV27205 for ; Fri, 20 Jul 2001 00:58:34 -0700 Received: by mail2.tieto.com with Internet Mail Service (5.5.2653.19) id <3D6KZXLL>; Fri, 20 Jul 2001 10:58:32 +0300 Message-ID: <8E1BC9FC59EBD311917D00508B61B662036A86B5@ccimaex02.imt.carel.fi> From: Tuomas.Vitikainen@tietoenator.com To: linux-xfs@oss.sgi.com Subject: Isn't 32 MB enough? Date: Fri, 20 Jul 2001 10:53:53 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello! I've been trying to install a Red Hat system using ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer/RH7.1-SGI-XF S-1.0.1.iso to my old test PC but the install stops saying I don't have enough memory. Does your XFS-modified version require more RAM than the regular RH7.1 release since the regular version installs fine with 32 MB of RAM or is this some kind of a bug? The machine is P100 MHz with 32 Megs of RAM and a 6.4GB hard drive with a 3COM NIC so there's nothing special about it. Best regards, Tuomas Vitikainen From owner-linux-xfs@oss.sgi.com Fri Jul 20 01:08:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K88PC27733 for linux-xfs-outgoing; Fri, 20 Jul 2001 01:08:25 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K88NV27711 for ; Fri, 20 Jul 2001 01:08:23 -0700 Received: from suojelumies.in.helsinki.fi (IDENT:jjaakkol@suojelumies.in.helsinki.fi [128.214.204.92]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6K89NG17159 for ; Fri, 20 Jul 2001 11:09:25 +0300 Date: Fri, 20 Jul 2001 11:08:05 +0300 (EEST) From: Jani Jaakkola To: Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: <200107191812.f6JICsI32762@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 19 Jul 2001, Steve Lord wrote: > I am informed that there is a fix in the latest kernels in the raid5 code > to fix some stall issues which ext3 hit. So it maybe that the answer here > is to run the latest kernels. I still do not like the fact we do non-stripe > friendly I/O to the log, and want to look into that. > > Jani, this may also be the source of your problems, we did experience > an almost complete lockup here with the 1.0.1 rpm kernel. If you get a > chance can you run the latest cvs kernel? I am currently in a Jazz festival listening to Jazz :) and my only Internet connection is a GSM-phone, but I might be able to try it (remotely) tomorrow. Thanks! - Jani From owner-linux-xfs@oss.sgi.com Fri Jul 20 01:27:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K8Rrv29081 for linux-xfs-outgoing; Fri, 20 Jul 2001 01:27:53 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K8RoV29052 for ; Fri, 20 Jul 2001 01:27:50 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id KAA33928 for ; Fri, 20 Jul 2001 10:27:37 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA36970 for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 18:26:30 +1000 (EST) Date: Fri, 20 Jul 2001 18:26:30 +1000 (EST) From: Nathan Scott Message-Id: <200107200826.SAA36970@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - userspace Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Important change for xfsdump and xfsrestore (and libraries that they rely on)... we're now consistent with other backup/restore utilities which need be available when only the root filesystem is mounted. cheers. Date: Fri Jul 20 01:18:35 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99273a cmd/acl/doc/CHANGES - 1.11 cmd/attr/doc/CHANGES - 1.7 cmd/dmapi/doc/CHANGES - 1.5 cmd/xfsdump/doc/CHANGES - 1.16 - document the change in some libraries and binaries moving into "/" instead of /usr - these pieces need to be available on the root filesystem such the disaster recovery can be more easily performed. cmd/acl/install-sh - 1.2 cmd/attr/install-sh - 1.2 cmd/xfsdump/install-sh - 1.3 cmd/xfsprogs/install-sh - 1.3 cmd/acl/include/builddefs.in - 1.5 cmd/attr/include/builddefs.in - 1.5 cmd/xfsdump/include/builddefs.in - 1.5 cmd/xfsprogs/include/builddefs.in - 1.10 - merge Dean's changes to libtool build/install process from dmapi into the other XFS packages. also, install libs into /lib rather than /usr/lib. cmd/xfsdump/dump/Makefile - 1.6 cmd/xfsdump/quota/Makefile - 1.3 cmd/xfsdump/restore/Makefile - 1.6 - install binary into /sbin rather than /usr/sbin. cmd/xfsdump/configure.in - 1.10 - look for libtool archives in all the right places. cmd/dmapi/include/builddefs.in - 1.6 - install library into /lib rather than /usr/lib. From owner-linux-xfs@oss.sgi.com Fri Jul 20 02:48:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K9m3T04238 for linux-xfs-outgoing; Fri, 20 Jul 2001 02:48:03 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K9lmV04192 for ; Fri, 20 Jul 2001 02:47:57 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id D0ABE352D for ; Fri, 20 Jul 2001 17:47:38 +0800 (PHT) Date: Fri, 20 Jul 2001 17:47:38 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Anyone using XFS ACLs? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I am wondering if anybody on the list is currently using XFS ACLs in some sort of a production environment (although this term has to be qualified). I ask not because of concern with the stability of ACL support with XFS, but because I need help with implementing them. In particular a previous thread (Subject: chacl questions) did not progress enough for me to find a way to get to implement them on my system. I hope my rephrasing my questions will help me get some answers. What needs to be done: o Set the ACLs of a pretty large tree of files and directories recursively. o Find out how to manage ACLs for easy addition/removal of particular user privileges on a per-subtree/branch basis again recursively. o Get some tips from those who have already implemented ACLs for a large data share (something like what Samba can provide although to be accessed locally or via NFS). I hope that someone out there can help me out with this. Thank you very much in advance. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 02:48:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6K9mt604332 for linux-xfs-outgoing; Fri, 20 Jul 2001 02:48:55 -0700 Received: from marraco.udl.es (gardeny.udl.es [193.144.12.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6K9mqV04310 for ; Fri, 20 Jul 2001 02:48:53 -0700 Received: from eup.udl.es (fermat.udl.net [10.50.54.28]) by marraco.udl.es (8.9.3/8.8.5) with ESMTP id KAA10065 for ; Fri, 20 Jul 2001 10:51:53 +0200 Received: by eup.udl.es (8.8.8+Sun/SMI-SVR4) id LAA29984; Fri, 20 Jul 2001 11:48:44 +0200 (MET DST) Date: Fri, 20 Jul 2001 11:48:44 +0200 (MET DST) From: fermin@eup.udl.es (Fermin Molina) Message-Id: <200107200948.LAA29984@eup.udl.es> To: linux-xfs@oss.sgi.com Subject: Can't mount my raid5 with 2.4.7-pre8 X-Sun-Charset: US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Kernel: 2.4.7-pre8 (cvs from 19-07-2001 evening, CET) After an AC failure, I can't mount my raid5, I get (/users is on fstab: /dev/md0) juno-tty1:~# mount /users Start mounting filesystem: md(9,0) Starting XFS recovery on filesystem: md(9,0) (dev: 9/0) XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many mounted file systems And on the /var/log/messages: Jul 20 11:38:17 juno kernel: Start mounting filesystem: md(9,0) Jul 20 11:38:17 juno kernel: Starting XFS recovery on filesystem: md(9,0) (dev: 9/0) Jul 20 11:38:17 juno kernel: XFS: xlog_recover_process_data: bad clientid Jul 20 11:38:17 juno kernel: XFS: log mount/recovery failed Jul 20 11:38:17 juno kernel: XFS: log mount failed I run xfs_repair -n /dev/md0, but I don't see anything wrong... (I think...) What can I do? I've lost all my data? Thanx in advance. /Fermin From owner-linux-xfs@oss.sgi.com Fri Jul 20 03:02:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KA2TY05983 for linux-xfs-outgoing; Fri, 20 Jul 2001 03:02:29 -0700 Received: from webserver2.webhouse.dk (webserver2.webhouse.dk [193.88.249.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KA2PV05933 for ; Fri, 20 Jul 2001 03:02:26 -0700 Received: from mpb (mpb.webhouse.dk [193.88.249.45]) by webserver2.webhouse.dk (8.9.3/8.9.3) with SMTP id MAA17034; Fri, 20 Jul 2001 12:02:18 +0200 Message-ID: <010d01c11103$53d55af0$2df958c1@mpb> From: "Mads Peter Bach" To: "Joshua Penix" Cc: References: <3B52A14E.6D0D4FA5@ch.sauter-bc.com><3B563C52.A3101025@xfs.lists.logout.sh> <20010720010215.77ebf768.jpenix@projectdesign.com> Subject: Re: Samba 2.2.1 RPMS with ACL Date: Fri, 20 Jul 2001 12:04:12 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sure thing, It can now be found at http://www.hum.auc.dk/~mpb/samba-2.2.1a-20010711.src.rpm (surprise, surprise!) /Mads ----- Original Message ----- From: "Joshua Penix" To: "Mads Peter Bach" Sent: Friday, July 20, 2001 10:02 AM Subject: Re: Samba 2.2.1 RPMS with ACL > On Thu, 19 Jul 2001 03:48:07 +0200 > "Mads Peter Bach" wrote: > > > Well, I've built a RPM from the official Samba 2.2.1a tarball. It works > > for > > me on a RH-7.0 system, but YMMV. You can find it at > > http://www.hum.auc.dk/~mpb/samba-2.2.1a-20010711.i386.rpm If somebody > > would > > stick it on the SGI server, that would be fine. > > Any chance we could get you to post the .src.rpm? That way we could tweak > it if our mileage doesn't vary correctly :^) > > --Josh > From owner-linux-xfs@oss.sgi.com Fri Jul 20 04:00:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KB0UU13562 for linux-xfs-outgoing; Fri, 20 Jul 2001 04:00:30 -0700 Received: from finch-post-11.mail.demon.net (finch-post-11.mail.demon.net [194.217.242.39]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KB0RV13541 for ; Fri, 20 Jul 2001 04:00:28 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by finch-post-11.mail.demon.net with esmtp (Exim 2.12 #1) id 15NY1B-000FR8-0B for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 11:00:25 +0000 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id 2CA6127EF for ; Fri, 20 Jul 2001 08:33:57 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id A02EB125E6; Fri, 20 Jul 2001 08:33:56 +0100 (BST) Date: Fri, 20 Jul 2001 08:33:56 +0100 (BST) From: Keith Matthews Subject: Re: External log and possibilities. To: linux-xfs@oss.sgi.com In-Reply-To: <001d01c110e0$78a0b000$3c532840@towerpc> References: <001d01c110e0$78a0b000$3c532840@towerpc> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010720073356.A02EB125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f6KB0SV13542 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 20 Jul 2001 01:54:42 -0400 Steven Tower > wrote: > > I want wondering if anyone here was aware of non-volatile RAM devices > 128m-1g and would such a device work with Linux and then allow you to > use an external log to read/write to them. I would expect that if it's > based on SDRAM, etc it would make for some interesting performance > gains. > Anyone have any thoughts on this? If you are talking about Flash then it has the limitation of a fairly small max numbr of write cycles. I have heard 100,000 quoted - not much for a busy fileserver. -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Fri Jul 20 04:50:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KBoX119433 for linux-xfs-outgoing; Fri, 20 Jul 2001 04:50:33 -0700 Received: from unpsun2.cc.unp.ac.za (Unpsun2.cc.unp.ac.za [143.128.64.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KBoUV19413 for ; Fri, 20 Jul 2001 04:50:30 -0700 Received: from nu.ac.za (groupwise.unp.ac.za [143.128.64.19]) by unpsun2.cc.unp.ac.za (8.9.3/8.9.3) with SMTP id NAA08255 for ; Fri, 20 Jul 2001 13:36:51 +0200 (SATS) Received: from neutrino.phy.unp.ac.za by nu.ac.za; Fri, 20 Jul 2001 13:50:17 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Robert Lindebaum To: linux-xfs@oss.sgi.com Subject: Bug in RedHat 7.1 Installer 1.01 Date: Fri, 20 Jul 2001 13:50:29 +0200 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01072013502901.31344@neutrino.phy.unp.ac.za> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk There appears to be a bug in the RedHat 7.1 XFS installer that causes the system to fail if any Raid partitions are defined. I set up a / partition and a /home each as raid1 and a swap space on both disks ( not raid ). The installer crashes before the partition table is written ( using disk druid) ( If use fdisk partition get written but when click on next it crashes at the same place. ) The problem is that the symbol fsType is not defined Robert Lindebaum From owner-linux-xfs@oss.sgi.com Fri Jul 20 05:25:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KCPId23303 for linux-xfs-outgoing; Fri, 20 Jul 2001 05:25:18 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KCPFV23282 for ; Fri, 20 Jul 2001 05:25:15 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15NZLB-00029N-00; Fri, 20 Jul 2001 14:25:10 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6KCOfI18743; Fri, 20 Jul 2001 08:24:41 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Keith Matthews Cc: linux-xfs@oss.sgi.com Subject: Re: External log and possibilities. References: <001d01c110e0$78a0b000$3c532840@towerpc> <20010720073356.A02EB125E6@rebutia.sweeney.demon.co.uk> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 20 Jul 2001 08:24:41 -0400 In-Reply-To: <20010720073356.A02EB125E6@rebutia.sweeney.demon.co.uk> Message-ID: Lines: 42 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Keith" == Keith Matthews writes: >> I want wondering if anyone here was aware of non-volatile RAM >> devices 128m-1g and would such a device work with Linux and then >> allow you to use an external log to read/write to them. I would >> expect that if it's based on SDRAM, etc it would make for some >> interesting performance gains. >> Anyone have any thoughts on this? Logging to NVRAM is quite common on other systems (Sun PrestoServe, Compaqdecital has one, NetApp, and most hardware RAID solutions). Unfortunately, good boards are both expensive and hard to come by. I've tried to find one on several occasions, and I know Stephen Tweedie has done the same for his ext3 work. Another option is to use a solid state disk. But that will cost you an arm and a leg. Keith> If you are talking about Flash then it has the limitation of a Keith> fairly small max numbr of write cycles. I have heard 100,000 Keith> quoted - not much for a busy fileserver. It is correct that flash has limitations - often in the order of magnitude you quote there. However, NVRAM boards for logging use batteries to refresh regular memory, and consequently they don't suffer from the same problems. You need to get power back on the box within too long, though. On most systems within a 2-3 day period. For people interested in experimenting with the performance gains from using a memory based log device, I recommend you put the log on a ramdisk (Only for testing. Kids, do not try this at home!). -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Jul 20 05:35:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KCZ4i24653 for linux-xfs-outgoing; Fri, 20 Jul 2001 05:35:04 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KCZ2V24626 for ; Fri, 20 Jul 2001 05:35:02 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id FAA02601 for ; Fri, 20 Jul 2001 05:34:52 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id HAA59340 for ; Fri, 20 Jul 2001 07:33:45 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15NZTV-0001gh-00 for ; Fri, 20 Jul 2001 07:33:45 -0500 Date: Fri, 20 Jul 2001 07:33:45 -0500 From: Nathan Straz To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP Message-ID: <20010720073345.A6470@sgi.com> Mail-Followup-To: "linux-xfs@oss.sgi.com" References: <200107191812.f6JICsI32762@jen.americas.sgi.com> <3B57CCB9.4386DD23@ch.sauter-bc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B57CCB9.4386DD23@ch.sauter-bc.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 08:16:25AM +0200, Simon Matter wrote: > Steve Lord schrieb: > > Jani, this may also be the source of your problems, we did experience > > an almost complete lockup here with the 1.0.1 rpm kernel. If you get a > > I'd like to reproduce this 'almost complete lockup' here, how can I do > this. I mean do I need SMP to reproduce this and what kind operation > did you do on the filesystem to force the lookup? Are we safe on UP? The system was a 2p PIII 500 running RH2.4.3-XFS. I had 7 disks in a RAID5 configuration using left-symmetric for the parity algorithm. I believe the RAID was completely synced. The RAID was exported over NFS. I was running the `rm -r` stage of the untar-remove test over NFS. Steve started the untar stage locally in a separate directory on the RAID. -- 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 Jul 20 06:03:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KD3hn28055 for linux-xfs-outgoing; Fri, 20 Jul 2001 06:03:43 -0700 Received: from zeta.qmw.ac.uk (zeta.qmw.ac.uk [138.37.6.6]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KD3dV28020 for ; Fri, 20 Jul 2001 06:03:40 -0700 Received: from heppcl.ph.qmw.ac.uk ([138.37.50.187]) by zeta.qmw.ac.uk with esmtp (Exim 3.16 #1) id 15NZwP-0003Sy-00 for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 14:03:37 +0100 Received: from heppct.ph.qmw.ac.uk (heppct.ph.qmw.ac.uk [138.37.50.246]) by heppcl.ph.qmw.ac.uk (8.9.3/8.9.3) with ESMTP id OAA19320 for ; Fri, 20 Jul 2001 14:03:38 +0100 Received: from localhost (pd@localhost) by heppct.ph.qmw.ac.uk (8.11.2/8.9.3) with ESMTP id f6KD3c529589 for ; Fri, 20 Jul 2001 14:03:38 +0100 X-Authentication-Warning: heppct.ph.qmw.ac.uk: pd owned process doing -bs Date: Fri, 20 Jul 2001 14:03:38 +0100 (BST) From: "P.Dixon" To: Subject: testing memory Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Sorry to pollute the list... a few weeks agao someone mentioned some DOS software to test RAM. Could you tell me what it is? Cheers, Paul ------------------------------------------------------------------------------- Paul Dixon Email: P.Dixon@qmw.ac.uk Department of Physics Phone: (020) 7882 5054 Queen Mary, University of London Fax : (020) 7882 5054 Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Fri Jul 20 06:25:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KDPu030517 for linux-xfs-outgoing; Fri, 20 Jul 2001 06:25:56 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KDPsV30498 for ; Fri, 20 Jul 2001 06:25:54 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id GAA08126 for ; Fri, 20 Jul 2001 06:25:44 -0700 (PDT) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2481218; Fri, 20 Jul 2001 08:24:36 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA88916; Fri, 20 Jul 2001 08:24:36 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id IAA40182; Fri, 20 Jul 2001 08:24:35 -0500 (CDT) Message-Id: <200107201324.IAA40182@fsgi158.americas.sgi.com> Subject: Re: Anyone using XFS ACLs? To: jijo@leathercollection.ph (Federico Sevilla III) Date: Fri, 20 Jul 2001 08:24:35 -0500 (CDT) Cc: linux-xfs@oss.sgi.com (Linux XFS Mailing List) In-Reply-To: from "Federico Sevilla III" at Jul 20, 2001 05:47:38 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi everyone, > > I am wondering if anybody on the list is currently using XFS ACLs in some > sort of a production environment (although this term has to be qualified). > I ask not because of concern with the stability of ACL support with XFS, > but because I need help with implementing them. > > In particular a previous thread (Subject: chacl questions) did not > progress enough for me to find a way to get to implement them on my > system. > > I hope my rephrasing my questions will help me get some answers. > > What needs to be done: > > o Set the ACLs of a pretty large tree of files and directories > recursively. > I don't know if there's a more elegant way to do it but I think one could do it with xargs, for example from the top level directory: find . -print | xargs -i -t chacl {} > o Find out how to manage ACLs for easy addition/removal of particular > user privileges on a per-subtree/branch basis again recursively. > Again might be a more elegant way to do it but I think it could be done with xargs. > o Get some tips from those who have already implemented ACLs for a large > data share (something like what Samba can provide although to be accessed > locally or via NFS). > NFS does not support ACLs. Tad From owner-linux-xfs@oss.sgi.com Fri Jul 20 06:34:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KDYQK31557 for linux-xfs-outgoing; Fri, 20 Jul 2001 06:34:26 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KDYOV31538 for ; Fri, 20 Jul 2001 06:34:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id GAA07951 for ; Fri, 20 Jul 2001 06:31:59 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2481022; Fri, 20 Jul 2001 08:32:01 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA16042; Fri, 20 Jul 2001 08:31:53 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KDWaD01276; Fri, 20 Jul 2001 08:32:36 -0500 Message-Id: <200107201332.f6KDWaD01276@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: jijo@leathercollection.ph (Federico Sevilla III), linux-xfs@oss.sgi.com (Linux XFS Mailing List) Subject: Re: Anyone using XFS ACLs? In-Reply-To: Message from Tad Dolphay of "Fri, 20 Jul 2001 08:24:35 CDT." <200107201324.IAA40182@fsgi158.americas.sgi.com> Date: Fri, 20 Jul 2001 08:32:36 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tad Dolphay wrote: > > I don't know if there's a more elegant way to do it but I think one could > do it with xargs, for example from the top level directory: > > find . -print | xargs -i -t chacl {} The other option here is for someone to take the source of something like chown which has a -R option, and chacl which does not. Merge the two and send in a patch. This is the sort of project which would be fairly easy for someone to tackle, would solve a problem. We are very tight on resources here and cannot be relied upon for things like bells and whistle extensions to commands like this. > > > o Find out how to manage ACLs for easy addition/removal of particular > > user privileges on a per-subtree/branch basis again recursively. > > > > Again might be a more elegant way to do it but I think it could be done > with xargs. > > > o Get some tips from those who have already implemented ACLs for a large > > data share (something like what Samba can provide although to be accessed > > locally or via NFS). > > > > NFS does not support ACLs. No it does not, but XFS running under nfs will still impose the acls on accesses from NFS. Steve > > Tad From owner-linux-xfs@oss.sgi.com Fri Jul 20 06:47:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KDlol32686 for linux-xfs-outgoing; Fri, 20 Jul 2001 06:47:50 -0700 Received: from ns1.tricord.com (mx01.tricord.com [64.240.27.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KDllV32666 for ; Fri, 20 Jul 2001 06:47:47 -0700 Received: FROM ns1.tricord.com BY ns1.tricord.com ; Fri Jul 20 08:49:21 2001 -0500 Received: by mx01.tricord.com with Internet Mail Service (5.5.2650.21) id <3M9HZYV7>; Fri, 20 Jul 2001 08:49:21 -0500 Message-ID: <6DEE94132593D41182D200508BDCA590500873@mail.tricord.com> From: "Esh, Andrew" To: linux-xfs@oss.sgi.com Subject: RE: testing memory Date: Fri, 20 Jul 2001 08:47:47 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C11122.C69F21F0" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C11122.C69F21F0 Content-Type: text/plain; charset="iso-8859-1" Try this, I've used it for years. Put it in lilo, and dual boot to it whenever you want an OS-free memory test. http://www.teresaudio.com/memtest86/ -----Original Message----- From: P.Dixon [mailto:P.Dixon@qmw.ac.uk] Sent: Friday, July 20, 2001 8:04 AM To: linux-xfs@oss.sgi.com Subject: testing memory Hi, Sorry to pollute the list... a few weeks agao someone mentioned some DOS software to test RAM. Could you tell me what it is? Cheers, Paul ---------------------------------------------------------------------------- --- Paul Dixon Email: P.Dixon@qmw.ac.uk Department of Physics Phone: (020) 7882 5054 Queen Mary, University of London Fax : (020) 7882 5054 Mile End Road, London E1 4NS URL : http://hepwww.ph.qmw.ac.uk/~pd ---------------------------------------------------------------------------- --- ------_=_NextPart_001_01C11122.C69F21F0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: testing memory

    Try this, I've used it for years. Put it in lilo, and = dual boot to it whenever you want an OS-free memory test.

    http://www.teresaudio.com/memtest86/

    -----Original Message-----
    From: P.Dixon [mailto:P.Dixon@qmw.ac.uk]
    Sent: Friday, July 20, 2001 8:04 AM
    To: linux-xfs@oss.sgi.com
    Subject: testing memory


    Hi,

    Sorry to pollute the list... a few weeks agao someone = mentioned some
    DOS software to test RAM. Could you tell me what it = is?

    Cheers,
            =         =         =         =         Paul

    ---------------------------------------------------------------= ----------------
    Paul = Dixon           &= nbsp;           &= nbsp;   Email: P.Dixon@qmw.ac.uk
    Department of = Physics           = ;     Phone: (020) 7882 5054
    Queen Mary, University of = London     Fax  : (020) 7882 5054
    Mile End Road, London E1 = 4NS         URL  : http://hepwww.ph.qmw.ac.uk/~pd
    ---------------------------------------------------------------= ----------------

    ------_=_NextPart_001_01C11122.C69F21F0-- From owner-linux-xfs@oss.sgi.com Fri Jul 20 06:50:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KDo3h00518 for linux-xfs-outgoing; Fri, 20 Jul 2001 06:50:03 -0700 Received: from drakkar.med.uni-tuebingen.de (noir.zit.medizin.uni-tuebingen.de [134.2.188.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KDo0V00494 for ; Fri, 20 Jul 2001 06:50:00 -0700 Received: (from smap@localhost) by drakkar.med.uni-tuebingen.de (8.7.3/8.7.3) id PAA05042 for ; Fri, 20 Jul 2001 15:49:59 +0200 (MESZ) X-Authentication-Warning: drakkar.med.uni-tuebingen.de: smap set sender to using -f Received: from intwww(192.168.24.80) by drakkar via smap (V1.3) id sma005038; Fri Jul 20 15:49:38 2001 Received: from med.uni-tuebingen.de (ch1_28.allgchir.med.uni-tuebingen.de [10.10.1.28]) by intwww.zit.med.uni-tuebingen.de (8.8.8+Sun/8.7.3) with ESMTP id PAA09179 for ; Fri, 20 Jul 2001 15:49:37 +0200 (MET DST) Message-ID: <3B583748.3010808@med.uni-tuebingen.de> Date: Fri, 20 Jul 2001 15:51:04 +0200 From: Johannes Stickel User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: de,en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Anyone using XFS ACLs? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, Federico Sevilla III wrote: > I hope my rephrasing my questions will help me get some answers. > > What needs to be done: > > o Set the ACLs of a pretty large tree of files and directories > recursively. afaik there is no way to do that directly. Therefore I've written a tiny script(attached below). There may be a many better ways to do it, but it works fine for me ;-) > o Find out how to manage ACLs for easy addition/removal of particular > user privileges on a per-subtree/branch basis again recursively. I just copy the old acl, and add/remove the privileges, i want to change. If you don't like this method, take a look at the sed manpage... > o Get some tips from those who have already implemented ACLs for a large > data share (something like what Samba can provide although to be accessed > locally or via NFS). Well, this is a bit tricky. You may want to take a look at http://acl.bestbits.at/man/acl.5.html#DETERMINING%20ACCESS The problem is the ACL_MASK, which is affected by the create mode. Thus you have to use a ------------------------------------------------------------------------ #!/bin/bash export acl=$1 export dacl=$1 function foreach() { for name in * do if [ -d "$name" ] then chacl -b $acl $dacl "$name" cd "$name" foreach cd .. else chacl $acl "$name" fi done } if [ -z $2 ] then echo "usage: mchacl acl directory"; exit fi chacl -b $acl $dacl $2 cd $2 foreach cd .. From owner-linux-xfs@oss.sgi.com Fri Jul 20 06:55:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KDtdN01023 for linux-xfs-outgoing; Fri, 20 Jul 2001 06:55:39 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KDtbV00996 for ; Fri, 20 Jul 2001 06:55:37 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id GAA10950 for ; Fri, 20 Jul 2001 06:55:27 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id IAA66115 for ; Fri, 20 Jul 2001 08:54:20 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15NajU-0001jJ-00 for ; Fri, 20 Jul 2001 08:54:20 -0500 Date: Fri, 20 Jul 2001 08:54:20 -0500 From: Nathan Straz To: Linux XFS Mailing List Subject: Re: Anyone using XFS ACLs? Message-ID: <20010720085420.B701@sgi.com> Mail-Followup-To: Linux XFS Mailing List References: <200107201324.IAA40182@fsgi158.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107201324.IAA40182@fsgi158.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 08:24:35AM -0500, Tad Dolphay wrote: > > o Set the ACLs of a pretty large tree of files and directories > > recursively. > > > > I don't know if there's a more elegant way to do it but I think one could > do it with xargs, for example from the top level directory: > > find . -print | xargs -i -t chacl {} Try this: find . -exec chacl {} \; -- 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 Jul 20 07:01:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KE13l01406 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:01:03 -0700 Received: from m2.pp.htv.fi (m2ep.pp.htv.fi [212.90.64.98]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KE0xV01382 for ; Fri, 20 Jul 2001 07:00:59 -0700 Received: from m7.pp.htv.fi (m7.pp.htv.fi [212.90.64.22]) by m2.pp.htv.fi (8.9.3 (PHNE_22672)/8.8.6) with ESMTP id RAA25947 for ; Fri, 20 Jul 2001 17:00:52 +0300 (EETDST) Received: from kitsune (cs158008.pp.htv.fi [213.243.158.8]) by m7.pp.htv.fi (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id RAA01718 for ; Fri, 20 Jul 2001 17:00:51 +0300 (EETDST) Received: from viiru by kitsune with local (Exim 3.31 #1 (Debian)) id 15Napm-00009W-00 for ; Fri, 20 Jul 2001 17:00:50 +0300 Date: Fri, 20 Jul 2001 17:00:50 +0300 From: Arto Jantunen To: linux-xfs@oss.sgi.com Subject: Kernel BUG with 2.4.7-pre8-xfs Message-ID: <20010720170050.A573@welho.com> Mail-Followup-To: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I had this almost immediately after running xfs_fsr. The same kernel has been running happily for a while now, so I think this is directly related to xfs_fsr. Hardware is an old P120 with 48M ram. It has a 4.3G IDE disk partitioned to three parts: 10M /boot, 88M swap, and the rest as /. -- Arto Jantunen --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=ksymoops ksymoops 2.4.1 on i586 2.4.7-pre8-xfs. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.7-pre8-xfs/ (default) -m /boot/System.map-2.4.7-pre8-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. Warning (compare_maps): mismatch on symbol floppy , floppy says c3a60358, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/block/floppy.o says c3a5f6d8. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/block/floppy.o entry Warning (compare_maps): mismatch on symbol audio_devs , sound says c3a302c0, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fc40. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol midi_devs , sound says c3a30330, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fcb0. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol mixer_devs , sound says c3a302d8, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fc58. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol num_audiodevs , sound says c3a302d4, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fc54. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol num_midis , sound says c3a30348, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fcc8. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol num_mixers , sound says c3a302ec, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fc6c. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol num_synths , sound says c3a3032c, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fcac. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Warning (compare_maps): mismatch on symbol synth_devs , sound says c3a30300, /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o says c3a2fc80. Ignoring /lib/modules/2.4.7-pre8-xfs/kernel/drivers/sound/sound.o entry Jul 20 16:23:04 kitsune kernel: kernel BUG at dcache.c:345! Jul 20 16:23:04 kitsune kernel: invalid operand: 0000 Jul 20 16:23:04 kitsune kernel: CPU: 0 Jul 20 16:23:04 kitsune kernel: EIP: 0010:[prune_dcache+129/344] Jul 20 16:23:04 kitsune kernel: EFLAGS: 00010286 Jul 20 16:23:04 kitsune kernel: eax: 0000001c ebx: c1a4e738 ecx: c11ea000 edx: 00000000 Jul 20 16:23:04 kitsune kernel: esi: c1a4e720 edi: 00000000 ebp: 0000000a esp: c11ebf94 Jul 20 16:23:04 kitsune kernel: ds: 0018 es: 0018 ss: 0018 Jul 20 16:23:04 kitsune kernel: Process kswapd (pid: 4, stackpage=c11eb000) Jul 20 16:23:04 kitsune kernel: Stack: c022ba2a c022baa6 00000159 000000c0 0000005f 00000000 0008e000 c013ba41 Jul 20 16:23:04 kitsune kernel: 0000000a c0125453 00000006 000000c0 000000c0 00000000 c11ea000 c0228bb1 Jul 20 16:23:04 kitsune kernel: c11ea239 c01254de 000000c0 00000000 00010f00 c11f9fb8 00000000 c0105454 Jul 20 16:23:04 kitsune kernel: Call Trace: [shrink_dcache_memory+33/48] [do_try_to_free_pages+39/88] [kswapd+90/228] [kernel_thread+40/56] Jul 20 16:23:04 kitsune kernel: Code: 0f 0b 83 c4 0c 8d 46 10 8b 53 f8 8b 48 04 89 4a 04 89 11 89 Using defaults from ksymoops -t elf32-i386 -a i386 Code; 00000000 Before first symbol 00000000 <_EIP>: Code; 00000000 Before first symbol 0: 0f 0b ud2a Code; 00000002 Before first symbol 2: 83 c4 0c add $0xc,%esp Code; 00000005 Before first symbol 5: 8d 46 10 lea 0x10(%esi),%eax Code; 00000008 Before first symbol 8: 8b 53 f8 mov 0xfffffff8(%ebx),%edx Code; 0000000b Before first symbol b: 8b 48 04 mov 0x4(%eax),%ecx Code; 0000000e Before first symbol e: 89 4a 04 mov %ecx,0x4(%edx) Code; 00000011 Before first symbol 11: 89 11 mov %edx,(%ecx) Code; 00000013 Before first symbol 13: 89 00 mov %eax,(%eax) Jul 20 16:24:30 kitsune kernel: kernel BUG at dcache.c:345! Jul 20 16:24:30 kitsune kernel: invalid operand: 0000 Jul 20 16:24:30 kitsune kernel: CPU: 0 Jul 20 16:24:30 kitsune kernel: EIP: 0010:[prune_dcache+129/344] Jul 20 16:24:30 kitsune kernel: EFLAGS: 00010286 Jul 20 16:24:30 kitsune kernel: eax: 0000001c ebx: c1a4e338 ecx: c048c000 edx: c053b6c0 Jul 20 16:24:30 kitsune kernel: esi: c1a4e320 edi: c25d90c0 ebp: 0000000c esp: c048de4c Jul 20 16:24:30 kitsune kernel: ds: 0018 es: 0018 ss: 0018 Jul 20 16:24:30 kitsune kernel: Process zsh (pid: 1868, stackpage=c048d000) Jul 20 16:24:30 kitsune kernel: Stack: c022ba2a c022baa6 00000159 000000d2 000001f4 00000001 00000010 c013ba41 Jul 20 16:24:30 kitsune kernel: 0000000e c0125453 00000006 000000d2 000000d2 00000001 c048c000 c0259928 Jul 20 16:24:30 kitsune kernel: 00000000 c01255ae 000000d2 00000001 c048c000 c012624f 000000d2 000000d2 Jul 20 16:24:30 kitsune kernel: Call Trace: [shrink_dcache_memory+33/48] [do_try_to_free_pages+39/88] [try_to_free_pages+34/44] [__alloc_pages+455/628] [_alloc_pages+22/24] [do_wp_page+370/608] [handle_mm_fault+134/184] Jul 20 16:24:30 kitsune kernel: Code: 0f 0b 83 c4 0c 8d 46 10 8b 53 f8 8b 48 04 89 4a 04 89 11 89 Code; 00000000 Before first symbol 00000000 <_EIP>: Code; 00000000 Before first symbol 0: 0f 0b ud2a Code; 00000002 Before first symbol 2: 83 c4 0c add $0xc,%esp Code; 00000005 Before first symbol 5: 8d 46 10 lea 0x10(%esi),%eax Code; 00000008 Before first symbol 8: 8b 53 f8 mov 0xfffffff8(%ebx),%edx Code; 0000000b Before first symbol b: 8b 48 04 mov 0x4(%eax),%ecx Code; 0000000e Before first symbol e: 89 4a 04 mov %ecx,0x4(%edx) Code; 00000011 Before first symbol 11: 89 11 mov %edx,(%ecx) Code; 00000013 Before first symbol 13: 89 00 mov %eax,(%eax) 10 warnings issued. Results may not be reliable. --Nq2Wo0NMKNjxTN9z-- From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:01:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KE1js01540 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:01:45 -0700 Received: from drakkar.med.uni-tuebingen.de (noir.zit.medizin.uni-tuebingen.de [134.2.188.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KE1gV01521 for ; Fri, 20 Jul 2001 07:01:42 -0700 Received: (from smap@localhost) by drakkar.med.uni-tuebingen.de (8.7.3/8.7.3) id QAA05295 for ; Fri, 20 Jul 2001 16:01:41 +0200 (MESZ) X-Authentication-Warning: drakkar.med.uni-tuebingen.de: smap set sender to using -f Received: from intwww(192.168.24.80) by drakkar via smap (V1.3) id sma005292; Fri Jul 20 16:01:17 2001 Received: from med.uni-tuebingen.de (ch1_28.allgchir.med.uni-tuebingen.de [10.10.1.28]) by intwww.zit.med.uni-tuebingen.de (8.8.8+Sun/8.7.3) with ESMTP id QAA10546 for ; Fri, 20 Jul 2001 16:01:15 +0200 (MET DST) Message-ID: <3B583A03.1080706@med.uni-tuebingen.de> Date: Fri, 20 Jul 2001 16:02:43 +0200 From: Johannes Stickel User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:0.9.1) Gecko/20010607 X-Accept-Language: de,en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Anyone using XFS ACLs? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, sorry for polluting the list. But i accidently hit the sent button :-( Federico Sevilla III wrote: > I hope my rephrasing my questions will help me get some answers. > > What needs to be done: > > o Set the ACLs of a pretty large tree of files and directories > recursively. afaik there is no way to do that directly. Therefore I've written a tiny script(attached below). There may be a many better ways to do it, but it works fine for me ;-) > o Find out how to manage ACLs for easy addition/removal of particular > user privileges on a per-subtree/branch basis again recursively. I just copy the old acl, and add/remove the privileges, i want to change. If you don't like this method, take a look at the sed manpage... > o Get some tips from those who have already implemented ACLs for a large > data share (something like what Samba can provide although to be accessed > locally or via NFS). Well, this is a bit tricky. You may want to take a look at http://acl.bestbits.at/man/acl.5.html#DETERMINING%20ACCESS The problem is the ACL_MASK, which is affected by the create mode. Thus you have to use at least 770 as create mode. You need this in directories, which uses acls. In other directories, this is probably not what you want. With samba, you can set a create mask per share. This means, that you want to use acls on each subdirectory of the share, which uses alcs. Johannes ------------------------------------------------------------------------ #!/bin/bash export acl=$1 export dacl=$1 function foreach() { for name in * do if [ -d "$name" ] then chacl -b $acl $dacl "$name" cd "$name" foreach cd .. else chacl $acl "$name" fi done } if [ -z $2 ] then echo "usage: mchacl acl directory"; exit fi chacl -b $acl $dacl $2 cd $2 foreach cd .. From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:03:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KE3Es01726 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:03:14 -0700 Received: from chaos.egr.duke.edu (chaos.egr.duke.edu [152.3.195.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KE3DV01707 for ; Fri, 20 Jul 2001 07:03:13 -0700 Received: from localhost (jlb@localhost) by chaos.egr.duke.edu (8.11.2/8.11.2) with ESMTP id f6KE2iC18058; Fri, 20 Jul 2001 10:02:44 -0400 X-Authentication-Warning: chaos.egr.duke.edu: jlb owned process doing -bs Date: Fri, 20 Jul 2001 10:02:43 -0400 (EDT) From: Joshua Baker-LePain X-X-Sender: To: Nathan Straz cc: Linux XFS Mailing List Subject: Re: Anyone using XFS ACLs? In-Reply-To: <20010720085420.B701@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 20 Jul 2001 at 8:54am, Nathan Straz wrote > On Fri, Jul 20, 2001 at 08:24:35AM -0500, Tad Dolphay wrote: > > > o Set the ACLs of a pretty large tree of files and directories > > > recursively. > > > > > > > I don't know if there's a more elegant way to do it but I think one could > > do it with xargs, for example from the top level directory: > > > > find . -print | xargs -i -t chacl {} > > Try this: > > find . -exec chacl {} \; Actually, that does the exact same thing as 'find | xargs', only slower. ;) It constantly has to spawn new chacl processes, then return to the find, whereas 'find | xargs' finishes the find, then spawns one chacl process. I did some testing on this once, and the differences can be quite remarkable. Note that, in the above example, the '-i {}' is redundant, since the default behavior of xargs is to put stdin at the end of the specified command. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:09:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KE9oo02322 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:09:50 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KE9gV02287 for ; Fri, 20 Jul 2001 07:09:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA06464 for ; Fri, 20 Jul 2001 16:09:30 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2483587; Fri, 20 Jul 2001 09:08:20 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA85841; Fri, 20 Jul 2001 09:08:20 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KE92K01386; Fri, 20 Jul 2001 09:09:02 -0500 Message-Id: <200107201409.f6KE92K01386@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Martin K. Petersen" cc: Keith Matthews , linux-xfs@oss.sgi.com Subject: Re: External log and possibilities. In-Reply-To: Message from "Martin K. Petersen" of "20 Jul 2001 08:24:41 EDT." Date: Fri, 20 Jul 2001 09:09:02 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >>>>> "Keith" == Keith Matthews writes: > > >> I want wondering if anyone here was aware of non-volatile RAM > >> devices 128m-1g and would such a device work with Linux and then > >> allow you to use an external log to read/write to them. I would > >> expect that if it's based on SDRAM, etc it would make for some > >> interesting performance gains. > > >> Anyone have any thoughts on this? > > Logging to NVRAM is quite common on other systems (Sun PrestoServe, > Compaqdecital has one, NetApp, and most hardware RAID solutions). > Unfortunately, good boards are both expensive and hard to come by. > > I've tried to find one on several occasions, and I know Stephen > Tweedie has done the same for his ext3 work. > > Another option is to use a solid state disk. But that will cost you > an arm and a leg. A quick hunt on google found this for one, no price without a phone call though: http://www.durabledata.com and this web site: http://www.emjembedded.com actually has some prices, for a compact flash based 128M ide drive they want $362. I could not find prices for anything non-flash based. Most of these devices appear to be in the low Gbyte capacity and are several thousand dollars each. These people make solidstate disks: http://www.soliddatasystems.com - no prices except in a press release where they charge $9950 for a 536Mbyte drive! Basically this stuff is expensive! http://www.imperialtech.com - no prices or links to places you might buy one from except the big guys (sun, emc, veritas ....). The main problem appears to be that these are aimed at really high end apps, not for being a filesystem journal. Steve p.s. At Cray we used to have SSDs which went forupto several million dollars, but they were static ram, large (for the time), VERY VERY fast, and this was at least a decade ago. > > > Keith> If you are talking about Flash then it has the limitation of a > Keith> fairly small max numbr of write cycles. I have heard 100,000 > Keith> quoted - not much for a busy fileserver. > > It is correct that flash has limitations - often in the order of > magnitude you quote there. > > However, NVRAM boards for logging use batteries to refresh regular > memory, and consequently they don't suffer from the same problems. > You need to get power back on the box within too long, though. On > most systems within a 2-3 day period. > > > For people interested in experimenting with the performance gains from > using a memory based log device, I recommend you put the log on a > ramdisk (Only for testing. Kids, do not try this at home!). > > -- > Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. > mkp@linuxcare.com, http://www.linuxcare.com/ > SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:13:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEDX302789 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:13:33 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEDTV02760 for ; Fri, 20 Jul 2001 07:13:30 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA06730 for ; Fri, 20 Jul 2001 16:13:15 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2447562; Fri, 20 Jul 2001 09:12:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA84511; Fri, 20 Jul 2001 09:12:05 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KEClG01412; Fri, 20 Jul 2001 09:12:47 -0500 Message-Id: <200107201412.f6KEClG01412@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: fermin@eup.udl.es (Fermin Molina) cc: linux-xfs@oss.sgi.com Subject: Re: Can't mount my raid5 with 2.4.7-pre8 In-Reply-To: Message from fermin@eup.udl.es (Fermin Molina) of "Fri, 20 Jul 2001 11:48:44 +0200." <200107200948.LAA29984@eup.udl.es> Date: Fri, 20 Jul 2001 09:12:47 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This looks very like the log recovery code and the raid code are not playing well with each other - which is a problem. If you actually run repair on the filesystem, it will zero the log and you should be able to mount it. before doing that can you run: xfs_logprint -t -i -b -e /dev/md0 and send me the output, logprint may well crash doing this. Steve > Hi, > > Kernel: 2.4.7-pre8 (cvs from 19-07-2001 evening, CET) > > After an AC failure, I can't mount my raid5, I get > (/users is on fstab: /dev/md0) > > > juno-tty1:~# mount /users > Start mounting filesystem: md(9,0) > Starting XFS recovery on filesystem: md(9,0) (dev: 9/0) > XFS: xlog_recover_process_data: bad clientid > XFS: log mount/recovery failed > XFS: log mount failed > mount: wrong fs type, bad option, bad superblock on /dev/md0, > or too many mounted file systems > > > And on the /var/log/messages: > > > Jul 20 11:38:17 juno kernel: Start mounting filesystem: md(9,0) > Jul 20 11:38:17 juno kernel: Starting XFS recovery on filesystem: md(9,0) (de > v: 9/0) > Jul 20 11:38:17 juno kernel: XFS: xlog_recover_process_data: bad clientid > Jul 20 11:38:17 juno kernel: XFS: log mount/recovery failed > Jul 20 11:38:17 juno kernel: XFS: log mount failed > > > I run xfs_repair -n /dev/md0, but I don't see anything wrong... (I think...) > > What can I do? I've lost all my data? > > Thanx in advance. > > /Fermin From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:16:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEGQ403163 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:16:26 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEGOV03144 for ; Fri, 20 Jul 2001 07:16:24 -0700 Received: from mail.seefried.com ([205.215.35.60]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id HAA12583 for ; Fri, 20 Jul 2001 07:16:09 -0700 (PDT) mail_from (ken@mail.seefried.com) Received: (qmail 5260 invoked by uid 500); 20 Jul 2001 14:11:45 -0000 Message-ID: <20010720141145.5259.qmail@mail.seefried.com> References: <200107201409.f6KE92K01386@jen.americas.sgi.com> In-Reply-To: <200107201409.f6KE92K01386@jen.americas.sgi.com> From: "Ken Seefried" To: Steve Lord Cc: "Martin K. Petersen" , Keith Matthews , linux-xfs@oss.sgi.com Subject: Re: External log and possibilities. Date: Fri, 20 Jul 2001 14:11:45 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord writes: > > actually has some prices, for a compact flash based 128M ide drive they > want $362. I could not find prices for anything non-flash based. Most > of these devices appear to be in the low Gbyte capacity and are several > thousand dollars each. > You probably do not want to use flash for this, as flash has a limited number of read/write cycles. And I concur with your assessment of solid-state disks: relatively small and very, very expensive. Ken From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:19:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEJqD03595 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:19:52 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEJoV03569 for ; Fri, 20 Jul 2001 07:19:50 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15Nb89-0002F0-00; Fri, 20 Jul 2001 16:19:49 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6KEJOZ23783; Fri, 20 Jul 2001 10:19:24 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: fermin@eup.udl.es (Fermin Molina) Cc: linux-xfs@oss.sgi.com Subject: Re: Can't mount my raid5 with 2.4.7-pre8 References: <200107200948.LAA29984@eup.udl.es> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 20 Jul 2001 10:19:24 -0400 In-Reply-To: <200107200948.LAA29984@eup.udl.es> Message-ID: Lines: 18 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Fermin" == Fermin Molina writes: Fermin> juno-tty1:~# mount /users Start mounting filesystem: md(9,0) Fermin> Starting XFS recovery on filesystem: md(9,0) (dev: 9/0) XFS: Fermin> xlog_recover_process_data: bad clientid XFS: log Fermin> mount/recovery failed XFS: log mount failed mount: wrong fs Fermin> type, bad option, bad superblock on /dev/md0, Fermin> or too many mounted file systems Hmmm. This may be caused by the recent BLKBSZSET changes. IIrc we had this problem before they went in. I'll run a few tests here and have a look. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:34:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEYr904818 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:34:53 -0700 Received: from sa-bwmail1.storageapps.com (smtp.storageapps.com [63.101.83.13]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEYpV04787 for ; Fri, 20 Jul 2001 07:34:51 -0700 Received: by SA-BWMAIL1 with Internet Mail Service (5.5.2653.19) id ; Fri, 20 Jul 2001 10:34:44 -0400 Message-ID: <23D04BDBA646D411BDDD00D0B774B53904602458@SA-BWMAIL1> From: "Christian, Chip" To: "Linux XFS (E-mail)" Subject: Blocksize Date: Fri, 20 Jul 2001 10:34:33 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I know that the blocksize is currently fixed at the pagesize of 4K. Are there plans in the works to allow different blocksizes? Specifically smaller, like 512B? -Chip From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:36:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEaMH05086 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:36:22 -0700 Received: from saturn.mackay.tritus.ca (cr212927-a.slnt1.on.wave.home.com [24.112.218.180]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEaKV05055 for ; Fri, 20 Jul 2001 07:36:20 -0700 Received: (from adam@localhost) by saturn.mackay.tritus.ca (8.11.2/8.11.2) id f6KEacj02455; Fri, 20 Jul 2001 10:36:38 -0400 X-Authentication-Warning: saturn.mackay.tritus.ca: adam set sender to adam@tritus.ca using -f Date: Fri, 20 Jul 2001 10:36:38 -0400 From: Adam Sherman To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid Message-ID: <20010720103638.A1641@tritus.ca> References: <20010719155130.D1330@de.tecosim.com> <995563148.12920.41.camel@stout.americas.sgi.com> <20010719233643.E9205@tritus.ca> <3B57C53C.CB467075@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B57C53C.CB467075@sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 12:44:28AM -0500, Eric Sandeen wrote: > Adam Sherman wrote: > > > I couldn't get the Jul19-12 > > installer to save the dump to a floppy, it couldn't access > > "/tmp/floppy" for some reason. > > Probably because it had the update disk in there... :( Makes sense, I couldn't figure out why though. The shell doesn think /tmp/floppy ins mounted but gives me a read-only filesystem error when I try to format a floppy. > > It's dump starts out similar then > > complains about and "AttributeError: set_active". > > Can you send any more information on the dump with the update disk? A > file and line number would be most helpful, or if you can deduce which > variable seems to be lacking the "set_active" method. This is a > different error than the raid problem, it seems. Starts out the same but ends with something in lilo_gui.py at line 452 in getScreen -> self.part.set_active(1) Then on line 75 in gtk.py at __getattr__, raise attributeError, attr And finally: AttributeError: set_active Hope this helps! Thanks, A. -- Adam Sherman President & Technology Architect Tritus Consultant Group Inc. +1.613.255.5164 http://www.tritus.ca From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:39:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEdu605516 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:39:56 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEdsV05493 for ; Fri, 20 Jul 2001 07:39:54 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA08525 for ; Fri, 20 Jul 2001 16:39:43 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2478297; Fri, 20 Jul 2001 09:38:34 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA45945; Fri, 20 Jul 2001 09:38:34 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KEdG801460; Fri, 20 Jul 2001 09:39:16 -0500 Message-Id: <200107201439.f6KEdG801460@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Christian, Chip" cc: "Linux XFS (E-mail)" Subject: Re: Blocksize In-Reply-To: Message from "Christian, Chip" of "Fri, 20 Jul 2001 10:34:33 EDT." <23D04BDBA646D411BDDD00D0B774B53904602458@SA-BWMAIL1> Date: Fri, 20 Jul 2001 09:39:16 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I know that the blocksize is currently fixed at the pagesize of 4K. Are ther > e plans in the works to allow different blocksizes? Specifically smaller, li > ke 512B? > > -Chip There are plans, I keep starting work on it and getting other work to do, the code to do this is somewhat involved, localized, but involved. It will happen, but right now there is stuff I need to do which will actually make money for SGI..... Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:43:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEhSf05932 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:43:28 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEhQV05911 for ; Fri, 20 Jul 2001 07:43:26 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6KEhMe09810; Fri, 20 Jul 2001 16:43:22 +0200 Message-Id: <4.3.2.7.2.20010720164216.03c394d0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 20 Jul 2001 16:42:59 +0200 To: "Christian, Chip" , "Linux XFS (E-mail)" From: Seth Mos Subject: Re: Blocksize In-Reply-To: <23D04BDBA646D411BDDD00D0B774B53904602458@SA-BWMAIL1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 10:34 20-7-2001 -0400, Christian, Chip wrote: >I know that the blocksize is currently fixed at the pagesize of 4K. Are >there plans in the works to allow different blocksizes? Specifically >smaller, like 512B? Yes, this is on the todo list. See the todo list on the site. (it's not called todo list but I forgot). Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:52:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEqJZ06710 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:52:19 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEqEV06688 for ; Fri, 20 Jul 2001 07:52:15 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KEtYI06594 for ; Fri, 20 Jul 2001 07:55:34 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2478414; Fri, 20 Jul 2001 09:50:52 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA06636; Fri, 20 Jul 2001 09:50:52 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KEpY401493; Fri, 20 Jul 2001 09:51:34 -0500 Message-Id: <200107201451.f6KEpY401493@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Martin K. Petersen" cc: fermin@eup.udl.es (Fermin Molina), linux-xfs@oss.sgi.com Subject: Re: Can't mount my raid5 with 2.4.7-pre8 In-Reply-To: Message from "Martin K. Petersen" of "20 Jul 2001 10:19:24 EDT." Date: Fri, 20 Jul 2001 09:51:34 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >>>>> "Fermin" == Fermin Molina writes: > > Fermin> juno-tty1:~# mount /users Start mounting filesystem: md(9,0) > Fermin> Starting XFS recovery on filesystem: md(9,0) (dev: 9/0) XFS: > Fermin> xlog_recover_process_data: bad clientid XFS: log > Fermin> mount/recovery failed XFS: log mount failed mount: wrong fs > Fermin> type, bad option, bad superblock on /dev/md0, > Fermin> or too many mounted file systems > > Hmmm. This may be caused by the recent BLKBSZSET changes. IIrc we > had this problem before they went in. > > I'll run a few tests here and have a look. This has been reported twice in the last couple of days from the cvs kernel, one was after a clean unmount! Most of the log looks good, but something in there is invalid, xfs_logprint gets confused as well and core dumps or trips an assert. Long term it would be nice if we could make log writes stripe aligned which would probably also fix this (currently they are any old 512 byte multiple long on any 512 byte boundary). However, it should work without this. Try a default (small) log, zero it with xfs_repair, then mount, do something, unmount. Repeat until it does not mount, look at the log with xfs_logprint - there is a binary dump option which should not fail. If there are zeros in the middle of the log then we have a problem in the raid code. Steve Steve > > -- > Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. > mkp@linuxcare.com, http://www.linuxcare.com/ > SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:55:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEtjI07152 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:55:45 -0700 Received: from saturn.mackay.tritus.ca (cr212927-a.slnt1.on.wave.home.com [24.112.218.180]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEthV07133 for ; Fri, 20 Jul 2001 07:55:43 -0700 Received: (from adam@localhost) by saturn.mackay.tritus.ca (8.11.2/8.11.2) id f6KEtbr02519; Fri, 20 Jul 2001 10:55:37 -0400 X-Authentication-Warning: saturn.mackay.tritus.ca: adam set sender to adam@tritus.ca using -f Date: Fri, 20 Jul 2001 10:55:37 -0400 From: Adam Sherman To: Ajay Ramaswamy Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid Message-ID: <20010720105536.B1641@tritus.ca> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 01:21:03PM +0530, Ajay Ramaswamy wrote: > The advice I have seen on the RedHat List and also LKML is dont bother > with swap on RAID insetad set up multiple swap areas on the different > disks the kernel can work out the details Best be carefull with this as if you *don't* have your swap on RAID, and one of your disks dies your box is going down fast. A. P.S. I did try the install without swap on raid, same error -- Adam Sherman President & Technology Architect Tritus Consultant Group Inc. +1.613.255.5164 http://www.tritus.ca From owner-linux-xfs@oss.sgi.com Fri Jul 20 07:58:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KEwpq07560 for linux-xfs-outgoing; Fri, 20 Jul 2001 07:58:51 -0700 Received: from saturn.mackay.tritus.ca (cr212927-a.slnt1.on.wave.home.com [24.112.218.180]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KEwnV07537 for ; Fri, 20 Jul 2001 07:58:49 -0700 Received: (from adam@localhost) by saturn.mackay.tritus.ca (8.11.2/8.11.2) id f6KExGE02535; Fri, 20 Jul 2001 10:59:16 -0400 X-Authentication-Warning: saturn.mackay.tritus.ca: adam set sender to adam@tritus.ca using -f Date: Fri, 20 Jul 2001 10:59:16 -0400 From: Adam Sherman To: Eric Sandeen Cc: linux-xfs@oss.sgi.com Subject: Re: XFS Install 1.0.1 anaconda crash with Raid 1 made with Disk Druid Message-ID: <20010720105914.C1641@tritus.ca> References: <20010719155130.D1330@de.tecosim.com> <995563148.12920.41.camel@stout.americas.sgi.com> <20010719233643.E9205@tritus.ca> <3B57C53C.CB467075@sgi.com> <20010720103638.A1641@tritus.ca> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <20010720103638.A1641@tritus.ca> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Could this message also be related? Also, is the problem I was having *without* the update disk fixed in the update disk? Thanks, A. -- Adam Sherman President & Technology Architect Tritus Consultant Group Inc. +1.613.255.5164 http://www.tritus.ca --9amGYk9869ThD9tj Content-Type: message/rfc822 Content-Disposition: inline --9amGYk9869ThD9tj-- From owner-linux-xfs@oss.sgi.com Fri Jul 20 08:07:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KF7Y708582 for linux-xfs-outgoing; Fri, 20 Jul 2001 08:07:34 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KF7VV08561 for ; Fri, 20 Jul 2001 08:07:32 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15NbsH-0002Hs-00; Fri, 20 Jul 2001 17:07:30 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6KF76j23825; Fri, 20 Jul 2001 11:07:06 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: Steve Lord Cc: fermin@eup.udl.es (Fermin Molina), linux-xfs@oss.sgi.com Subject: Re: Can't mount my raid5 with 2.4.7-pre8 References: <200107201451.f6KEpY401493@jen.americas.sgi.com> From: "Martin K. Petersen" Organization: Linuxcare, Inc. Date: 20 Jul 2001 11:07:06 -0400 In-Reply-To: <200107201451.f6KEpY401493@jen.americas.sgi.com> Message-ID: Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "Steve" == Steve Lord writes: >> Hmmm. This may be caused by the recent BLKBSZSET changes. IIrc we >> had this problem before they went in. >> >> I'll run a few tests here and have a look. Steve> This has been reported twice in the last couple of days from Steve> the cvs kernel, one was after a clean unmount! Most of the log Steve> looks good, but something in there is invalid, xfs_logprint Steve> gets confused as well and core dumps or trips an assert. I just reproduced this in first attempt with a dirty fs on MD RAID5. Looking deeper... -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Fri Jul 20 08:20:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KFKtY09906 for linux-xfs-outgoing; Fri, 20 Jul 2001 08:20:55 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KFKqV09887 for ; Fri, 20 Jul 2001 08:20:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KFPFF07923 for ; Fri, 20 Jul 2001 08:25:15 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2484692; Fri, 20 Jul 2001 10:19:30 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA40451; Fri, 20 Jul 2001 10:19:28 -0500 (CDT) Subject: Re: Isn't 32 MB enough? From: Eric Sandeen To: Tuomas.Vitikainen@tietoenator.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <8E1BC9FC59EBD311917D00508B61B662036A86B5@ccimaex02.imt.carel.fi> References: <8E1BC9FC59EBD311917D00508B61B662036A86B5@ccimaex02.imt.carel.fi> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 20 Jul 2001 10:19:05 -0500 Message-Id: <995642346.18507.12.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 20 Jul 2001 10:53:53 +0300, Tuomas.Vitikainen@tietoenator.com wrote: > Hello! > > I've been trying to install a Red Hat system using > ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer/RH7.1-SGI-XF > S-1.0.1.iso to my old test PC but the install stops saying I don't have > enough memory. Does your XFS-modified version require more RAM than the > regular RH7.1 release since the regular version installs fine with 32 MB of > RAM or is this some kind of a bug? I don't believe that we explicitly put any extra memory constraints in our version... if you can give me the exact error message you get, I'll look and see what triggers it. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 08:23:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KFNGe10204 for linux-xfs-outgoing; Fri, 20 Jul 2001 08:23:16 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KFNEV10183 for ; Fri, 20 Jul 2001 08:23:14 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KFRcF08079 for ; Fri, 20 Jul 2001 08:27:38 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2477464; Fri, 20 Jul 2001 10:21:53 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id KAA36903; Fri, 20 Jul 2001 10:21:50 -0500 (CDT) Subject: Re: Bug in RedHat 7.1 Installer 1.01 From: Eric Sandeen To: Robert Lindebaum Cc: linux-xfs@oss.sgi.com In-Reply-To: <01072013502901.31344@neutrino.phy.unp.ac.za> References: <01072013502901.31344@neutrino.phy.unp.ac.za> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 20 Jul 2001 10:21:26 -0500 Message-Id: <995642489.18507.15.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 20 Jul 2001 13:50:29 +0200, Robert Lindebaum wrote: > The installer crashes before the partition table is written ( using disk > druid) ( If use fdisk partition get written but when click on next it > crashes at the same place. ) > The problem is that the symbol fsType is not defined Hi, if you grab the update image from the Release-1.0.1/installer/updates directory on the web site, it will fix this particular problem for you... but others with raid have subsequently run into another problem which I'm chasing down right now. Perhaps more raid testing would be in order next time around... :-) -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 08:46:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KFkZg11793 for linux-xfs-outgoing; Fri, 20 Jul 2001 08:46:35 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KFkUV11771 for ; Fri, 20 Jul 2001 08:46:30 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6KFkC0366679; Fri, 20 Jul 2001 17:46:12 +0200 (CEST) Message-ID: <3B585227.2715F310@pasteur.fr> Date: Fri, 20 Jul 2001 17:45:43 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Nathan Straz CC: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <200107191812.f6JICsI32762@jen.americas.sgi.com> <3B57CCB9.4386DD23@ch.sauter-bc.com> <20010720073345.A6470@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi On the same "benchmark" theads of Nate Straz ... (sotfware raid5 and xfs performance issue) How long does it take to extract the 2.4.6 linux kernel and delete it? | create | delete ------------------- a) | 0:17 | 0:07 b) | 0:24 | 0:25 c) | 1:51' | 16:45 d) | 2:54 | 8:08 [tru@adm ~/tmp]$ du -sk /tmp/linux-2.4.6.tar.gz ./linux/ 26312 /tmp/linux-2.4.6.tar.gz 130412 ./linux a) local xfs partition on the will become nfs client b) local xfs raid5 array on a single disk (/dev/md1) on the will become nfs server c) local xfs raid5 array on 3ware card 7disks (/dev/md0) on the will become nfs server d) nfs bonnie block (K/sec) |output|input |------------ c) |47340 |77559 d) | 4390 |10777 I will try to move the log out of the raid5 array as proposed by Steve. Regards, Tru ---- details ---- The server is running 2.4.7pre8 from yesterday's CVS cat /proc/version Linux version 2.4.7-pre8-xfs (tru@sheridan.bis.pasteur.fr) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #2 SMP Thu Jul 19 11:33:28 CEST 2001 [tru@sheridan ~]$ !98 cat /proc/cmdline BOOT_IMAGE=1-smp-cvs ro root=301 BOOT_FILE=/boot/bzImage-2.4.7-pre8-xfs ramdisk_size=2500 devfs=nomount noapic a) local xfs partition [tru@adm ~/tmp]$ date ; time tar xzf /tmp/linux-2.4.6.tar.gz ; date; time /bin/rm -rf linux ; date Fri Jul 20 15:49:33 CEST 2001 2.910u 2.400s 0:17.22 30.8% 0+0k 0+0io 325pf+0w Fri Jul 20 15:49:50 CEST 2001 0.080u 1.540s 0:06.81 23.7% 0+0k 0+0io 138pf+0w Fri Jul 20 15:49:57 CEST 2001 b) local ide raid5 xfs access on the server [tru@sheridan /scratch]$ date ; time tar xzf /tmp/linux-2.4.6.tar.gz ; date; time /bin/rm -rf linux ; date Fri Jul 20 15:54:35 CEST 2001 4.640u 4.380s 0:24.20 37.2% 0+0k 0+0io 327pf+0w Fri Jul 20 15:54:59 CEST 2001 0.060u 2.290s 0:25.06 9.3% 0+0k 0+0io 138pf+0w Fri Jul 20 15:55:24 CEST 2001 c) local 3ware raid5 xfs access on the server [tru@sheridan tru]$ date ; time tar xzf /tmp/linux-2.4.6.tar.gz ; date ; time /bin/rm -rf linux ; date Fri Jul 20 15:58:24 CEST 2001 4.540u 3.890s 1:51.42 7.5% 0+0k 0+0io 327pf+0w Fri Jul 20 16:00:16 CEST 2001 0.050u 5.230s 16:45.66 0.5% 0+0k 0+0io 138pf+0w Fri Jul 20 16:17:01 CEST 2001 [tru@sheridan tru]$ date ; ~tru/bonnie++-1.00g/bonnie++ -d /raid5/home/Bis/tru ; date Fri Jul 20 12:07:00 CEST 2001 Writing with putc()...done Writing intelligently...done Rewriting...done Reading with getc()...done Reading intelligently...done start 'em...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.00g ------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 sheridan.bis.pas 2G 10818 97 47340 85 23690 54 10329 97 77559 66 433.5 3 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 147 6 +++++ +++ 311 11 554 25 +++++ +++ 313 13 sheridan.bis.pasteur.fr,2G,10818,97,47340,85,23690,54,10329,97,77559,66,433.5,3,16,147,6,+++++,+++,311,11,554,25,+++++,+++,313,13 Fri Jul 20 12:20:43 CEST 2001 d) on nfs (/dev/md0 exported) case [tru@adm tru]$ date ; time tar xzf /tmp/linux-2.4.6.tar.gz ; date ; time /bin/rm -rf linux ; date Fri Jul 20 16:22:20 CEST 2001 2.730u 2.320s 2:54.08 2.9% 0+0k 0+0io 325pf+0w Fri Jul 20 16:25:14 CEST 2001 0.070u 0.740s 8:08.32 0.1% 0+0k 0+0io 138pf+0w Fri Jul 20 16:33:22 CEST 2001 [tru@adm ~/Desktop]$ date; ~/rh71/build/bonnie++-1.00g/bonnie++ -d /home/Bis/tru; date Fri Jul 20 13:26:11 CEST 2001 Writing with putc()...done Writing intelligently...done Rewriting...done Reading with getc()...done Reading intelligently...done start 'em...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.00g ------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 adm.cluster 1G 4013 29 4390 2 3109 3 10463 88 10777 4 567.1 3 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 506 1 4525 13 276 0 135 0 4931 6 319 1 adm.cluster,1G,4013,29,4390,2,3109,3,10463,88,10777,4,567.1,3,16,506,1,4525,13,276,0,135,0,4931,6,319,1 Fri Jul 20 13:48:11 CEST 2001 /etc/raidtab ------------ # Sample raid-5 configuration # raiddev /dev/md0 raid-level 5 nr-raid-disks 7 # Spare disks for hot reconstruction #nr-spare-disks 1 persistent-superblock 1 chunk-size 64 # the best one for maximum performance: # parity-algorithm left-symmetric #parity-algorithm right-asymmetric #parity-algorithm right-symmetric device /dev/sdb1 raid-disk 0 device /dev/sdc1 raid-disk 1 device /dev/sdd1 raid-disk 2 device /dev/sde1 raid-disk 3 device /dev/sdf1 raid-disk 4 device /dev/sdg1 raid-disk 5 device /dev/sdh1 raid-disk 6 # #device /dev/sda1 #spare-disk 0 # #------------------------------- # raid5 on hda #------------------------------- raiddev /dev/md1 raid-level 5 nr-raid-disks 3 persistent-superblock 1 chunk-size 64 parity-algorithm left-symmetric # device /dev/hda6 raid-disk 0 device /dev/hda7 raid-disk 1 device /dev/hda8 raid-disk 2 -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Fri Jul 20 09:01:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KG1Gp13388 for linux-xfs-outgoing; Fri, 20 Jul 2001 09:01:16 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KG1DV13368 for ; Fri, 20 Jul 2001 09:01:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id JAA22865 for ; Fri, 20 Jul 2001 09:01:02 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2481985; Fri, 20 Jul 2001 10:59:55 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA79252; Fri, 20 Jul 2001 10:59:55 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KG0aG32766; Fri, 20 Jul 2001 11:00:36 -0500 Message-Id: <200107201600.f6KG0aG32766@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh cc: Nathan Straz , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Tru Huynh of "Fri, 20 Jul 2001 17:45:43 +0200." <3B585227.2715F310@pasteur.fr> Date: Fri, 20 Jul 2001 11:00:36 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi > > On the same "benchmark" theads of Nate Straz ... > (sotfware raid5 and xfs performance issue) > > How long does it take to extract the 2.4.6 linux kernel and delete it? > > | create | delete > ------------------- > a) | 0:17 | 0:07 > b) | 0:24 | 0:25 > c) | 1:51' | 16:45 > d) | 2:54 | 8:08 > > [tru@adm ~/tmp]$ du -sk /tmp/linux-2.4.6.tar.gz ./linux/ > 26312 /tmp/linux-2.4.6.tar.gz > 130412 ./linux > > a) local xfs partition on the will become nfs client > b) local xfs raid5 array on a single disk (/dev/md1) on the will become > nfs server > c) local xfs raid5 array on 3ware card 7disks (/dev/md0) on the will > become nfs server > d) nfs > Just one comment here, the configuration in case c) is never a good idea, the raid code will automatically cause the disk head to thrash around that is why the performance is so bad there. I am not totally sure why we can do a reasonable job on deletes on a single disk, but not on a raid - there are synchronous writes in there. Unless your single disk xfs is on ide with write caching turned on. One more comment on xfs delete speed is that multiple parallel threads doing deletes will run faster than a single thread doing deletes, so lots of different threads doing deletes will not be as bad as a single large directory delete. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 09:07:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KG73E13830 for linux-xfs-outgoing; Fri, 20 Jul 2001 09:07:03 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KG71V13809 for ; Fri, 20 Jul 2001 09:07:01 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HJ0LM>; Fri, 20 Jul 2001 11:06:20 -0500 Message-ID: <85063BBE668FD411944400D0B744267A64348C@AUSMAIL> From: "Gonyou, Austin" To: "'Christian, Chip'" , "Linux XFS (E-mail)" Subject: RE: Blocksize Date: Fri, 20 Jul 2001 11:06:19 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have a question if we could possibly even go up to bs as large as 32k? -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Christian, Chip [mailto:chip.christian@storageapps.com] > Sent: Friday, July 20, 2001 9:35 AM > To: Linux XFS (E-mail) > Subject: Blocksize > > > I know that the blocksize is currently fixed at the pagesize > of 4K. Are there plans in the works to allow different > blocksizes? Specifically smaller, like 512B? > > -Chip > From owner-linux-xfs@oss.sgi.com Fri Jul 20 09:12:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KGCN214133 for linux-xfs-outgoing; Fri, 20 Jul 2001 09:12:23 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KGCKV14102 for ; Fri, 20 Jul 2001 09:12:20 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA14785 for ; Fri, 20 Jul 2001 18:10:48 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2484780; Fri, 20 Jul 2001 11:10:57 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA71068; Fri, 20 Jul 2001 11:10:56 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KGBcp04159; Fri, 20 Jul 2001 11:11:38 -0500 Message-Id: <200107201611.f6KGBcp04159@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Gonyou, Austin" cc: "'Christian, Chip'" , "Linux XFS (E-mail)" Subject: Re: Blocksize In-Reply-To: Message from "Gonyou, Austin" of "Fri, 20 Jul 2001 11:06:19 CDT." <85063BBE668FD411944400D0B744267A64348C@AUSMAIL> Date: Fri, 20 Jul 2001 11:11:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I have a question if we could possibly even go up to bs as large as 32k? Currently I only have plans to implement filesystem block size less than page cache size. The 2.5 kernel may bring along a page cache size larger than the page size. The combination of the two is how we get to the larger sizes, the xfs code itself supports 64K, it is the interface with the Linux page cache where we only implemented the one case of page size and block size being equal. Steve > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com > > > -----Original Message----- > > From: Christian, Chip [mailto:chip.christian@storageapps.com] > > Sent: Friday, July 20, 2001 9:35 AM > > To: Linux XFS (E-mail) > > Subject: Blocksize > > > > > > I know that the blocksize is currently fixed at the pagesize > > of 4K. Are there plans in the works to allow different > > blocksizes? Specifically smaller, like 512B? > > > > -Chip > > From owner-linux-xfs@oss.sgi.com Fri Jul 20 09:48:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KGmYb15238 for linux-xfs-outgoing; Fri, 20 Jul 2001 09:48:34 -0700 Received: from marraco.udl.es (gardeny.udl.es [193.144.12.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KGmVV15219 for ; Fri, 20 Jul 2001 09:48:32 -0700 Received: from eup.udl.es (fermat.udl.net [10.50.54.28]) by marraco.udl.es (8.9.3/8.8.5) with ESMTP id RAA21772; Fri, 20 Jul 2001 17:51:33 +0200 Received: by eup.udl.es (8.8.8+Sun/SMI-SVR4) id SAA02304; Fri, 20 Jul 2001 18:48:21 +0200 (MET DST) Date: Fri, 20 Jul 2001 18:48:21 +0200 (MET DST) From: fermin@eup.udl.es (Fermin Molina) Message-Id: <200107201648.SAA02304@eup.udl.es> To: jack@suse.cz, syrekron@iastate.edu Subject: Re: Quota reporting for NFS mounts Cc: nathans@wobbly.melbourne.sgi.com, tbd@sgi.com, linux-xfs@oss.sgi.com X-Sun-Charset: US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, > I have gotten quota reporting working, using the -pre7 utils. It seems that the problem > was in hosts.allow / hosts.deny. We discovered that you need to specify which hosts > (much like portmap) have are allowed to contact rpc.rquotad. After that adjustment, it > seems to work like a charm! > > Thanks for all the advice, > > -Adrian > > > > > > Actually I had some reports about rpc.rquotad SEGFAULTing. The > > bug should be fixed in -pre8 utils I released yesterday so please > > try those. If it doesn't help, tell me. I have -pre6, that have the problems commented before. I updated to -pre8 and all work ok!! Nothing changed in hosts.allow/deny. I use usrquota (of course) on linux-XFS server and, now, I use quota on NFS-client SUN to mount. But I think that this option is not related to the segfaults produced, because I have for the same server, linux NFS-clients (RH 6.1 clients with updates), and rpc.rquotad segfaults too. Now, all works ok. /Fermin From owner-linux-xfs@oss.sgi.com Fri Jul 20 09:54:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KGsZH15500 for linux-xfs-outgoing; Fri, 20 Jul 2001 09:54:35 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KGsWV15481 for ; Fri, 20 Jul 2001 09:54:33 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KGwuF19671 for ; Fri, 20 Jul 2001 09:58:56 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2462559 for ; Fri, 20 Jul 2001 11:53:11 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id LAA53171 for ; Fri, 20 Jul 2001 11:53:10 -0500 (CDT) Subject: New 1.0.1 installer update disk From: Eric Sandeen To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 20 Jul 2001 11:52:46 -0500 Message-Id: <995647966.19010.23.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk There's a new system installer installer update disk at ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer/updates This has 2 fixes for the raid install problems, Adam says it "works for him." :) -Eric Updates: o Do not use labels on XFS partitions to avoid running into 12 character limit. o s/fsType/fsystem in fstab.py for RAID code (fix NameError when making filesystems on RAID) o Change "lilo on /boot" option disabling so that it works with raid installs -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 10:36:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KHa7616185 for linux-xfs-outgoing; Fri, 20 Jul 2001 10:36:07 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KHa4V16166 for ; Fri, 20 Jul 2001 10:36:05 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id TAA19442; Fri, 20 Jul 2001 19:35:43 +0200 Date: Fri, 20 Jul 2001 19:35:42 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Steve Lord Cc: Federico Sevilla III , Linux XFS Mailing List Subject: Re: Anyone using XFS ACLs? Message-ID: <20010720193542.D19116@vestdata.no> References: <200107201332.f6KDWaD01276@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200107201332.f6KDWaD01276@jen.americas.sgi.com>; from Steve Lord on Fri, Jul 20, 2001 at 08:32:36AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 08:32:36AM -0500, Steve Lord wrote: > > NFS does not support ACLs. > > No it does not, but XFS running under nfs will still impose the acls on > accesses from NFS. Actually there is a SUN-extention for NFSv3 to support NFS, and NFSv4 support ACLs natively. I don't think the SUN-extention has been ported to linux, but NFSv4 is on it's way. I don't know what state it is in though. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Fri Jul 20 10:38:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KHcNO16317 for linux-xfs-outgoing; Fri, 20 Jul 2001 10:38:23 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KHcLV16298 for ; Fri, 20 Jul 2001 10:38:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KHgiF24413 for ; Fri, 20 Jul 2001 10:42:45 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2480241; Fri, 20 Jul 2001 12:36:58 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA16247; Fri, 20 Jul 2001 12:36:58 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KHbcL05108; Fri, 20 Jul 2001 12:37:38 -0500 Message-Id: <200107201737.f6KHbcL05108@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= cc: Steve Lord , Federico Sevilla III , Linux XFS Mailing List Subject: Re: Anyone using XFS ACLs? In-Reply-To: Message from =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= of "Fri, 20 Jul 2001 19:35:42 +0200." <20010720193542.D19116@vestdata.no> Date: Fri, 20 Jul 2001 12:37:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Fri, Jul 20, 2001 at 08:32:36AM -0500, Steve Lord wrote: > > > NFS does not support ACLs. > > > > No it does not, but XFS running under nfs will still impose the acls on > > accesses from NFS. > > Actually there is a SUN-extention for NFSv3 to support NFS, and NFSv4 > support ACLs natively. I don't think the SUN-extention has been ported > to linux, but NFSv4 is on it's way. I don't know what state it is in > though. > Still being ported, there may be a status update in Ottawa this month. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 10:44:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KHiXl16570 for linux-xfs-outgoing; Fri, 20 Jul 2001 10:44:33 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KHiVV16545 for ; Fri, 20 Jul 2001 10:44:31 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id KAB05143 for ; Fri, 20 Jul 2001 10:42:40 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id MAA2475688; Fri, 20 Jul 2001 12:43:10 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id MAA10378; Fri, 20 Jul 2001 12:43:10 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KHhpg06111; Fri, 20 Jul 2001 12:43:51 -0500 Message-Id: <200107201743.f6KHhpg06111@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh , Nathan Straz , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Steve Lord of "Fri, 20 Jul 2001 11:00:36 CDT." <200107201600.f6KG0aG32766@jen.americas.sgi.com> Date: Fri, 20 Jul 2001 12:43:51 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Just one comment here, the configuration in case c) is never a good idea, > the raid code will automatically cause the disk head to thrash around > that is why the performance is so bad there. I am not totally sure why > we can do a reasonable job on deletes on a single disk, but not on a > raid - there are synchronous writes in there. Unless your single disk > xfs is on ide with write caching turned on. One more comment on xfs > delete speed is that multiple parallel threads doing deletes will > run faster than a single thread doing deletes, so lots of different > threads doing deletes will not be as bad as a single large directory > delete. > > Steve > I made a mistake here I meant config b) not c) - it looks like write caching is on in this case. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 11:33:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KIXp017677 for linux-xfs-outgoing; Fri, 20 Jul 2001 11:33:51 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KIXiV17654 for ; Fri, 20 Jul 2001 11:33:44 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA08729 for ; Fri, 20 Jul 2001 11:33:32 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2486754 for ; Fri, 20 Jul 2001 13:32:27 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA04113 for ; Fri, 20 Jul 2001 13:32:27 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KIX7H08390; Fri, 20 Jul 2001 13:33:07 -0500 Message-Id: <200107201833.f6KIX7H08390@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-xfs@oss.sgi.com Subject: Re: Anyone using XFS ACLs? (fwd) Date: Fri, 20 Jul 2001 13:33:07 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This was sent privately, Danny later said he meant to send to the list, any message mangling is entirely the fault of my mail tool. I expect we will get something based on this into the tree fairly soon (is anyone in Australia listening? hint hint). Steve ------- Forwarded Message Date: Fri, 20 Jul 2001 12:35:35 -0400 From: Danny Cox To: Steve Lord Subject: Re: Anyone using XFS ACLs? This is a multi-part message in MIME format. - --------------4E072E6D209773EBBDAD1589 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Steve, Steve Lord wrote: > The other option here is for someone to take the source of something > like chown which has a -R option, and chacl which does not. Merge the > two and send in a patch. This is the sort of project which would be > fairly easy for someone to tackle, would solve a problem. We are > very tight on resources here and cannot be relied upon for things > like bells and whistle extensions to commands like this. Steve, here is a patch that adds an '-r' arg to chacl, and decends (depth first) a directory tree changing ACLs as it goes. It doesn't attempt to list them recursively, as that is a little trickier (and neither chown nor chmod attempt this). I did have a little problem. The "Makefile" uses the '-D_FILE_OFFSET_BITS=64' which comes from ../include/builddefs, which comes from ../include/builddefs.in, and causes the readdir to not work correctly. The included file "" gets the wrong size, which doesn't agree with my libc (I'm using RedHat 6.2, and it's standard glibc). When I recompiled without that flag, it works like a champ. Short of defining 'struct dirent' myself (HACK!), I don't know how to work around this other than how I did (remove the flag, which probably breaks something else). Anyway, the patch is attached. Oh, by the way, I did take the liberty of adding spaces where I thought they should be, providing a little more consistency. Ignore them if you wish. - -- "Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing had happened." -- Winston Churchill Danny - --------------4E072E6D209773EBBDAD1589 Content-Type: text/plain; charset=us-ascii; name="chacl.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="chacl.patch" - --- cmd/acl/chacl/chacl.c.orig Fri Jul 20 11:04:45 2001 +++ cmd/acl/chacl/chacl.c Fri Jul 20 12:30:09 2001 @@ -36,6 +36,7 @@ */ #include +#include #include #include #include @@ -43,10 +44,17 @@ #include #include #include +#include static int acl_delete_file (const char * path, acl_type_t type); - -static int list_acl(char *file); +static int list_acl (char *file); +static int set_acl (acl_t acl, acl_t dacl, const char *fname); +static int isdir (const char *fname); +static int walk_dir (acl_t acl, acl_t dacl, const char *fname); +static void *emalloc (int len); + static char *program; +static int Recurse = 0; static void usage (void) @@ -59,6 +67,7 @@ fprintf (stderr, "\t%s -D pathname ...\n", program); fprintf (stderr, "\t%s -B pathname ...\n", program); fprintf (stderr, "\t%s -l pathname ...\n", program); + fprintf (stderr, "\t%s -r pathname ...\n", program); exit (1); } @@ -70,7 +79,7 @@ int switch_flag = 0; /* ensure only one switch is used */ int args_required = 1; int failed = 0; /* exit status */ - - int c; /* For use by getopt(3) */ + int c; /* For use by getopt(3) */ int dflag = 0; /* a Default ACL is desired */ int bflag = 0; /* a both ACLs are desired */ int Rflag = 0; /* set to true to remove an acl */ @@ -82,25 +91,26 @@ /* create program name */ p = strrchr (argv[0], '/'); - - program = p != NULL ? p + 1 : argv[0]; + program = (p != NULL) ? p + 1 : argv[0]; - - acl_set_compat(ACL_COMPAT_IRIXGET); + acl_set_compat (ACL_COMPAT_IRIXGET); /* parse arguments */ - - while ((c = getopt (argc, argv, "bdlRDB")) != -1) + while ((c = getopt (argc, argv, "bdlRDBr")) != -1) { - - if (switch_flag) usage(); - - switch_flag=1; + if (switch_flag) + usage(); + switch_flag = 1; switch (c) { case 'b': bflag = 1; - - args_required=3; + args_required = 3; break; case 'd': dflag = 1; - - args_required=2; + args_required = 2; break; case 'R': Rflag = 1; @@ -114,6 +124,9 @@ case 'l': lflag = 1; break; + case 'r': + Recurse = 1; + break; default: usage (); break; @@ -121,16 +134,16 @@ } /* if not enough arguments quit */ - - if ((argc-optind) < args_required) + if ((argc - optind) < args_required) usage (); /* list the acls */ - - if ( lflag ) + if (lflag) { - - for (;optind < argc;optind++) + for (; optind < argc; optind++) { char *file = argv[optind]; - - if (!list_acl(file)) + if (!list_acl (file)) { failed++; } @@ -139,20 +152,20 @@ } /* remove the acls */ - - if ( Rflag || Dflag || Bflag ) + if (Rflag || Dflag || Bflag) { - - for (;optind < argc;optind++) + for (; optind < argc; optind++) { if (!Dflag && acl_delete_file (argv[optind], ACL_TYPE_A CCESS) == -1) { - - fprintf (stderr,"%s: error removing access acl on \"%s\": %s\n", - - program, argv[optind],strerror(errno)); + fprintf (stderr, "%s: error removing access acl on \"%s\": %s\n", + program, argv[optind], strerror (errno) ); failed++; } if (!Rflag && acl_delete_file (argv[optind], ACL_TYPE_D EFAULT) == -1) { - - fprintf (stderr,"%s: error removing default acl on \"%s\": %s\n", - - program, argv[optind],strerror(errno)); + fprintf (stderr, "%s: error removing default ac l on \"%s\": %s\n", + program, argv[optind], strerror (errno) ); failed++; } } @@ -163,7 +176,7 @@ /* file access acl */ if (! dflag) { acl = acl_from_text (argv[optind]); - - if (acl == NULL || acl_valid(acl) == -1) + if (acl == NULL || acl_valid (acl) == -1) { fprintf (stderr, inv_acl, program, argv[optind]); return (1); @@ -175,7 +188,7 @@ /* directory default acl */ if (bflag || dflag) { dacl = acl_from_text (argv[optind]); - - if (dacl == NULL || acl_valid(dacl) == -1) + if (dacl == NULL || acl_valid (dacl) == -1) { fprintf (stderr, inv_acl, program, argv[optind]); return (1); @@ -185,24 +198,9 @@ /* place acls on files */ - - for (;optind < argc;optind++) + for (; optind < argc; optind++) { - - /* set regular acl */ - - if (acl && - - acl_set_file (argv[optind], ACL_TYPE_ACCESS, acl) == -1) - - { - - fprintf (stderr,"%s: error setting access acl on \"%s\" : %s\n", - - program, argv[optind],strerror(errno)); - - failed++; - - } - - /* set default acl */ - - if (dacl && - - acl_set_file (argv[optind], ACL_TYPE_DEFAULT, dacl) == -1) - - { - - fprintf (stderr,"%s: error setting default acl on \"%s\ ": %s\n", - - program, argv[optind],strerror(errno)); - - failed++; - - } + failed += set_acl (acl, dacl, argv[optind]); } if (acl) @@ -220,11 +218,11 @@ acl_delete_file (const char * path, acl_type_t type) { struct acl acl; - - int error=0; + int error = 0; acl.acl_cnt = ACL_NOT_PRESENT; - - error = acl_set_file( path,type,&acl) ; + error = acl_set_file (path, type, &acl) ; return(error); } @@ -242,10 +240,10 @@ char *buf_acl = NULL; char *buf_dacl = NULL; - - acl = acl_get_file(file, ACL_TYPE_ACCESS); + acl = acl_get_file (file, ACL_TYPE_ACCESS); if (acl == NULL) { fprintf (stderr, "%s: error getting ACL on \"%s\": %s\n", - - program, file, strerror(errno)); + program, file, strerror (errno)); return 0; } if (acl->acl_cnt != ACL_NOT_PRESENT) { @@ -253,15 +251,15 @@ if (buf_acl == NULL) { fprintf (stderr, "%s: error converting ACL to short text " "for file \"%s\": %s\n", - - program, file, strerror(errno)); + program, file, strerror (errno)); return 0; } } - - dacl = acl_get_file(file, ACL_TYPE_DEFAULT); + dacl = acl_get_file (file, ACL_TYPE_DEFAULT); if (dacl == NULL) { fprintf (stderr, "%s: error getting default ACL on \"%s\": %s\n", - - program, file, strerror(errno)); + program, file, strerror (errno)); return 0; } if (dacl->acl_cnt > 0) { @@ -269,7 +267,7 @@ if (buf_dacl == NULL) { fprintf (stderr, "%s: error converting default ACL to short tex t " "for file \"%s\": %s\n", - - program, file, strerror(errno)); + program, file, strerror (errno)); return 0; } } @@ -294,5 +292,101 @@ if (buf_dacl) acl_free(buf_dacl); - - return(1); + return (1); +} + +static int +set_acl (acl_t acl, acl_t dacl, const char *fname) +{ + int failed = 0; + + /* set regular acl */ + if (acl && acl_set_file (fname, ACL_TYPE_ACCESS, acl) == -1) + { + fprintf (stderr,"%s: error setting access acl on \"%s\": %s\n", + program, fname, strerror (errno)); + failed++; + } + /* set default acl */ + if (dacl && acl_set_file (fname, ACL_TYPE_DEFAULT, dacl) == -1) + { + fprintf (stderr,"%s: error setting default acl on \"%s\": %s\n" , + program, fname, strerror (errno)); + failed++; + } + + if (Recurse && isdir (fname)) + { + failed += walk_dir (acl, dacl, fname); + } + + return (failed); +} + +/* is fname a directory? */ + +static int +isdir (const char *fname) +{ + struct stat st; + + if (stat (fname, &st) == -1) + { + return (0); + } + + return (S_ISDIR (st.st_mode)); +} + +/* step through entries in a directory */ + +static int +walk_dir (acl_t acl, acl_t dacl, const char *fname) +{ + int failed = 0; + DIR *dir; + struct dirent *d; + + if ((dir = opendir (fname)) == NULL) + { + fprintf (stderr, "%s: error opening \"%s\": %s\n", program, + fname, strerror (errno)); + return (0); + } + + while ((d = readdir (dir)) != NULL) + { + char *new; + + /* skip "." and ".." entries */ + if (strcmp (d->d_name, ".") == 0 || + strcmp (d->d_name, "..") == 0) + continue; + + new = emalloc (strlen (fname) + strlen (d->d_name) + 2); + sprintf (new, "%s/%s", fname, d->d_name); + + failed += set_acl (acl, dacl, new); + free (new); + } + + closedir (dir); + + return (failed); +} + +static void * +emalloc (int len) +{ + void *p; + + p = malloc (len); + if (p == NULL) + { + fprintf (stderr, "%s: malloc error: %s\n", program, + strerror (errno)); + exit (255); + } + + return (p); } - --------------4E072E6D209773EBBDAD1589-- ------- End of Forwarded Message From owner-linux-xfs@oss.sgi.com Fri Jul 20 11:35:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KIZfO17808 for linux-xfs-outgoing; Fri, 20 Jul 2001 11:35:41 -0700 Received: from pilot12.cl.msu.edu (pilot12.cl.msu.edu [35.9.5.32]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KIZeV17789 for ; Fri, 20 Jul 2001 11:35:40 -0700 Received: from msu.edu (loopback [127.0.0.1]) by pilot12.cl.msu.edu (8.10.2/8.10.2) with SMTP id f6KIZcD44700; Fri, 20 Jul 2001 14:35:38 -0400 Message-Id: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Date: Fri, 20 Jul 2001 14:35:38 EDT To: linux-xfs@oss.sgi.com Subject: XFS release 1.0.1 upgrade? From: Chris Szilagyi X-Mailer: TWIG 2.3.0 Cc: szilagy2@msu.edu Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I was just wondering if the quota problems from the 1.0 Release of the Red Hat 7.1 ISO have been fixed. And if so, what basic steps are necessary to update a system installed with the original Release 1.0 ISO CD for Red Hat 7.1. I am assuming all that would need to be done is to update all of the rpms with the new 1.0.1 rpms, and update to the appropriate 2.4.3- SGI_XFS_1.0.1 kernel rpm? Thanks in advance, -- Chris From owner-linux-xfs@oss.sgi.com Fri Jul 20 11:44:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KIifJ17994 for linux-xfs-outgoing; Fri, 20 Jul 2001 11:44:41 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KIiPV17975 for ; Fri, 20 Jul 2001 11:44:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KIlf903494 for ; Fri, 20 Jul 2001 11:47:41 -0700 Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2484155; Fri, 20 Jul 2001 13:42:58 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id NAA54878; Fri, 20 Jul 2001 13:42:57 -0500 (CDT) Subject: Re: XFS release 1.0.1 upgrade? From: Eric Sandeen To: Chris Szilagyi Cc: linux-xfs@oss.sgi.com In-Reply-To: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 20 Jul 2001 13:42:32 -0500 Message-Id: <995654553.19288.3.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 20 Jul 2001 14:35:38 -0400, Chris Szilagyi wrote: > I was just wondering if the quota problems from the 1.0 Release of the Red > Hat 7.1 ISO have been fixed. And if so, what basic steps are necessary to > update a system installed with the original Release 1.0 ISO CD for Red Hat > 7.1. I am assuming all that would need to be done is to update all of the > rpms with the new 1.0.1 rpms, and update to the appropriate 2.4.3- > SGI_XFS_1.0.1 kernel rpm? AFAIK, all the known quota problems are fixed in 1.0.1. Yes, you should be able to just upgrade the userspace RPMs and the kernel - if you're not sure how to do that, Red Hat has a document explaining RPM kernel upgrades. The short answer is do "rpm -ivh , make an initrd if you need it, and then edit & re-run lilo, and reboot. Some people have reported problems with /dev related issues, since devfs has been turned off in the 1.0.1 release - I didn't expect this, since the on-disk /dev should still be intact. Hopefully you won't run into this. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 12:21:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KJL6L20431 for linux-xfs-outgoing; Fri, 20 Jul 2001 12:21:06 -0700 Received: from trillium-hollow.org (IDENT:root@trillium-hollow.org [209.180.166.89]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KJL4V20412 for ; Fri, 20 Jul 2001 12:21:04 -0700 Received: from erich (helo=trillium) by trillium-hollow.org with local-esmtp (Exim 3.20 #1) id 15NfpU-0001Pg-00; Fri, 20 Jul 2001 12:20:52 -0700 To: Eric Sandeen cc: linux-xfs@oss.sgi.com Subject: Re: FYI: Networking bug in RH 7.1 updated config files... In-Reply-To: Your message of "Thu, 19 Jul 2001 22:23:00 CDT." <3B57A414.365082A@sgi.com> Date: Fri, 20 Jul 2001 12:20:52 -0700 From: erich@uruk.org Message-Id: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > erich@uruk.org wrote: > > > > NOTE, this is a RH 7.1 problem fundamentally, but I'm mentioning it here > > because the compiled kernels provided by the SGI guys in the 1.0.1 release > > masked this problem by (I think) not being compiled with the config > > files provided. > > Actually, for the "Red Hat-ish" RPMs we took the config files "as-is" > and just added the XFS bits... so it is enabled in our RPMs as well. Yeah, after looking at it a bit closer, the problem seems to be that in the later kernels (2.4.5+ are what I had tested with this config file), it's enabled at boot time, where it is not in the RedHat 2.4.3-12 kernel. I know how to shut it off via the proc interface, but the person who decided to change that behavior definitely goofed there, since I would imagine most people would prefer the default TCP/IP setup to have the widest possible compatibility. Sorry for the wasted bandwidth... ;) -- Erich Stefan Boleyn http://www.uruk.org/ "Reality is truly stranger than fiction; Probably why fiction is so popular" From owner-linux-xfs@oss.sgi.com Fri Jul 20 12:35:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KJZc021349 for linux-xfs-outgoing; Fri, 20 Jul 2001 12:35:38 -0700 Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KJZZV21330 for ; Fri, 20 Jul 2001 12:35:36 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 15Ng3e-000ClS-0U for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 20:35:31 +0100 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id F1F1627EF for ; Fri, 20 Jul 2001 20:34:58 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id 64CF4125E6; Fri, 20 Jul 2001 20:34:59 +0100 (BST) Date: Fri, 20 Jul 2001 20:34:58 +0100 (BST) From: Keith Matthews Subject: Re[2]: FYI: Networking bug in RH 7.1 updated config files... To: linux-xfs@oss.sgi.com In-Reply-To: References: X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010720193459.64CF4125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f6KJZaV21331 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 20 Jul 2001 12:20:52 -0700 wrote: > > I know how to shut it off via the proc interface, but the person who > decided to change that behavior definitely goofed there, since I would > imagine most people would prefer the default TCP/IP setup to have the > widest possible compatibility. I think they just followed the lead of vger.kernel.org. There has been plenty of discussion of this there. Andi, Keith - care to comment ? -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Fri Jul 20 12:38:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KJc4t21624 for linux-xfs-outgoing; Fri, 20 Jul 2001 12:38:04 -0700 Received: from biobio.vexcel.com (biobio.vexcel.com [192.92.90.108]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KJc2V21604 for ; Fri, 20 Jul 2001 12:38:02 -0700 Received: from [192.168.1.17] (router.vexcel.com [192.92.90.254]) by biobio.vexcel.com (8.9.3+Sun/8.9.1) with ESMTP id NAA11443 for ; Fri, 20 Jul 2001 13:37:52 -0600 (MDT) Mime-Version: 1.0 X-Sender: brissing@mail.vexcel.com (Unverified) Message-Id: In-Reply-To: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Date: Fri, 20 Jul 2001 13:35:17 -0600 To: linux-xfs@oss.sgi.com From: Dean Brissinger Subject: XFS 1.0.1 SuSE Port Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Has anyone attempted to get XFS working on SuSE? I need to get that going but don't want to invest time in something that's already been done. From owner-linux-xfs@oss.sgi.com Fri Jul 20 12:46:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KJkiT22581 for linux-xfs-outgoing; Fri, 20 Jul 2001 12:46:44 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KJkgV22559 for ; Fri, 20 Jul 2001 12:46:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA15838 for ; Fri, 20 Jul 2001 12:46:31 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2488822; Fri, 20 Jul 2001 14:45:25 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id OAA49873; Fri, 20 Jul 2001 14:45:24 -0500 (CDT) Subject: Re: XFS 1.0.1 SuSE Port From: Eric Sandeen To: Dean Brissinger Cc: linux-xfs@oss.sgi.com In-Reply-To: References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.10.99 (Preview Release) Date: 20 Jul 2001 14:44:57 -0500 Message-Id: <995658300.19288.8.camel@stout.americas.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 20 Jul 2001 13:35:17 -0600, Dean Brissinger wrote: > Has anyone attempted to get XFS working on SuSE? I need to get that > going but don't want to invest time in something that's already been > done. Several people are using XFS on SuSE-installed boxes, but with vanilla kernels, I believe. I don't know if anyone has made available RPMs of SuSE kernels with XFS merged in... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 12:50:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KJo4X22988 for linux-xfs-outgoing; Fri, 20 Jul 2001 12:50:04 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KJo2V22965 for ; Fri, 20 Jul 2001 12:50:02 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA16054 for ; Fri, 20 Jul 2001 12:49:50 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2487514; Fri, 20 Jul 2001 14:48:44 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA52642; Fri, 20 Jul 2001 14:48:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KJnNw08446; Fri, 20 Jul 2001 14:49:23 -0500 Message-Id: <200107201949.f6KJnNw08446@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Eric Sandeen cc: Dean Brissinger , linux-xfs@oss.sgi.com Subject: Re: XFS 1.0.1 SuSE Port In-Reply-To: Message from Eric Sandeen of "20 Jul 2001 14:44:57 CDT." <995658300.19288.8.camel@stout.americas.sgi.com> Date: Fri, 20 Jul 2001 14:49:23 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On 20 Jul 2001 13:35:17 -0600, Dean Brissinger wrote: > > Has anyone attempted to get XFS working on SuSE? I need to get that > > going but don't want to invest time in something that's already been > > done. > > Several people are using XFS on SuSE-installed boxes, but with vanilla > kernels, I believe. I don't know if anyone has made available RPMs of > SuSE kernels with XFS merged in... Andi Kleen lurks on this list, maybe he can answer this one. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 13:16:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KKGn625130 for linux-xfs-outgoing; Fri, 20 Jul 2001 13:16:49 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KKGlV25105 for ; Fri, 20 Jul 2001 13:16:48 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.2) id f6KKGgQ18056 for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 16:16:42 -0400 Date: Fri, 20 Jul 2001 16:16:41 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: build errors on current cvs Message-ID: <20010720161641.A11383@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Trying to build the current CVS kernel (20010720.1437), I'm getting undef'd syms in hisax.o when doing make_install. This is some sort of PCMCIA device driver. Any cluez? Or should I just pull cvs and try again? find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b /home/alane/rpm/tmp/kernel-2.4.7-root -r 2.4.7-SGI_XFS_cvs.20010720.0; fi depmod: *** Unresolved symbols in /home/alane/rpm/tmp/kernel-2.4.7-root/lib/modules/2.4.7-SGI_XFS_cvs.20010720.0/kernel/drivers/isdn/hisax/hisax.o depmod: jiftime make: *** [_modinst_post] Error 1 error: Bad exit status from /home/alane/rpm/tmp/rpm-tmp.32927 (%build) -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Fri Jul 20 13:30:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KKUaD25806 for linux-xfs-outgoing; Fri, 20 Jul 2001 13:30:36 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KKUYV25784 for ; Fri, 20 Jul 2001 13:30:34 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.2) id f6KKUSt19720 for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 16:30:28 -0400 Date: Fri, 20 Jul 2001 16:30:28 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: CVS Kernel is borken (not yer fault) Message-ID: <20010720163028.A19481@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The current (well, 2 hours ago) kernel has a bug in the isdn driver for hisax (wtf is that?). Configure HISAX out for now. [alane@wwweasel hisax]$ cd /usr/src/linux-2.4.7/drivers/isdn/hisax/ [alane@wwweasel hisax]$ grep jiftime *.c config.c:jiftime(char *s, long mark) config.c: p += jiftime(p, jiffies); q931.c: dp += jiftime(dp, jiffies); see, jiftime is global. that's cool. [alane@wwweasel alane]$ cd rpm/BUILD/kernel-2.4.7/linux/drivers/isdn/hisax/ [alane@wwweasel hisax]$ grep jiftime *c config.c:static inline int jiftime(char *s, long mark) config.c: p += jiftime(p, jiffies); q931.c: dp += jiftime(dp, jiffies); oops, jiftime is now static and what? q931.c wants to call it? houston, we have problem... -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Fri Jul 20 13:31:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KKV2F25931 for linux-xfs-outgoing; Fri, 20 Jul 2001 13:31:02 -0700 Received: from mail3.caramail.com (mail3.caramail.com [195.68.99.191]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KKV0V25911 for ; Fri, 20 Jul 2001 13:31:00 -0700 Received: from caramail.com (www35.caramail.com [195.68.99.214]) by mail3.caramail.com (8.8.8/8.8.8) with SMTP id WAA13652 for linux-xfs@oss.sgi.com; Fri, 20 Jul 2001 22:31:54 +0100 (WET DST) Posted-Date: Fri, 20 Jul 2001 22:31:54 +0100 (WET DST) From: LENHOF Jean-Yves To: linux-xfs@oss.sgi.com Message-ID: <995661056000029@caramail.com> X-Mailer: Caramail - www.caramail.com X-Originating-IP: [193.252.222.191] Mime-Version: 1.0 Subject: You can have a look on this test... Date: Fri, 20 Jul 2001 22:30:56 GMT+1 Content-Type: multipart/mixed; boundary="=_NextPart_Caramail_000029995661056_ID" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --=_NextPart_Caramail_000029995661056_ID Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable http://aurora.zemris.fer.hr/filesystems/final.html _________________________________________________________ Le journal des abonn=E9s Caramail - http://www.carazine.com --=_NextPart_Caramail_000029995661056_ID-- From owner-linux-xfs@oss.sgi.com Fri Jul 20 13:39:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KKdr526482 for linux-xfs-outgoing; Fri, 20 Jul 2001 13:39:53 -0700 Received: from mail.broadpark.no (mail.broadpark.no [217.13.4.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KKdoV26463 for ; Fri, 20 Jul 2001 13:39:50 -0700 Received: from online.no (217-13-10-85.dd.nextgentel.com [217.13.10.85]) by mail.broadpark.no (Postfix) with ESMTP id 22D127D3E; Fri, 20 Jul 2001 22:39:45 +0200 (MET DST) Message-ID: <3B58EADA.7D8121A9@online.no> Date: Fri, 20 Jul 2001 22:37:14 -0400 From: Knut J Bjuland X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-2 i686) X-Accept-Language: en MIME-Version: 1.0 To: Alan Eldridge Cc: SGI XFS Dev List Subject: Re: build errors on current cvs References: <20010720161641.A11383@wwweasel.geeksrus.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Alan Eldridge wrote: > Trying to build the current CVS kernel (20010720.1437), I'm getting undef'd > syms in hisax.o when doing make_install. This is some sort of PCMCIA device > driver. Any cluez? Or should I just pull cvs and try again? > > find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia > if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b > /home/alane/rpm/tmp/kernel-2.4.7-root -r 2.4.7-SGI_XFS_cvs.20010720.0; fi > depmod: *** Unresolved symbols in > /home/alane/rpm/tmp/kernel-2.4.7-root/lib/modules/2.4.7-SGI_XFS_cvs.20010720.0/kernel/drivers/isdn/hisax/hisax.o > depmod: jiftime > make: *** [_modinst_post] Error 1 > error: Bad exit status from /home/alane/rpm/tmp/rpm-tmp.32927 (%build) > > -- > Alan Eldridge > from std_disclaimer import * hisax.o is a driver isdn for simens chipset. I have build cvs kernel without errors by disabling passive isdn card. From owner-linux-xfs@oss.sgi.com Fri Jul 20 14:24:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KLO2J28496 for linux-xfs-outgoing; Fri, 20 Jul 2001 14:24:02 -0700 Received: from orion.ECE.McGill.CA (root@Orion.ECE.McGill.CA [132.206.75.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KLO0V28473 for ; Fri, 20 Jul 2001 14:24:00 -0700 Received: from proserpine (Proserpine.ECE.McGill.CA [132.206.31.219]) by orion.ECE.McGill.CA (8.9.1a/8.9.1) with ESMTP id RAA10673 for ; Fri, 20 Jul 2001 17:23:52 -0400 (EDT) Reply-To: From: "Hugo Levasseur" To: "LINUX-XFS" Subject: Problem compiling linux-2.4-xfs Date: Fri, 20 Jul 2001 17:25:03 -0400 Message-ID: <000001c11162$70aeb6d0$db1fce84@proserpine> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C11140.E99E9D70" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C11140.E99E9D70 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am trying to compile linux with xfs support but every time I get a error and the make bzImage fails: It seems to be compiling in /linux/arch/i386/kdb when it fails. Here's an example error I get: i386-dis.c:3538 parse error before 'ATTRIBUTE_UNUSED' i386-dis.c: In function 'OP_MMX' Like I said this is just an example.. but they pretty much look all the same.... i386-dis.c:somenumber parse error before 'ATTRIBUTE_UNUSED' i386-dis.c: In fuction 'somefunction' Any clues? ------------------------------------------------------------------------ ----------- Hugo Levasseur, System Administrator ECE Computing Labs, McGill University 3480 University Str. Montreal, Quebec tel:514-398-1691 ------------------------------------------------------------------------ ----------- ------=_NextPart_000_0001_01C11140.E99E9D70 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message
    I am = trying to=20 compile linux with xfs support but every time I get a error and the make = bzImage=20 fails:
     
    It = seems to be=20 compiling in /linux/arch/i386/kdb when it fails.  Here's an example = error I=20 get:
     
    i386-dis.c:3538=20 parse error before 'ATTRIBUTE_UNUSED'
    i386-dis.c: In=20 function 'OP_MMX'
     
    Like I = said this is=20 just an example.. but they pretty much look all the same....=20 i386-dis.c:somenumber parse error before = 'ATTRIBUTE_UNUSED'
    i386-dis.c: In=20 fuction 'somefunction'
     
    Any=20 clues?
     
    ----------------------------------------------------------------= -------------------
      Hugo = Levasseur, System=20 Administrator  
      ECE = Computing Labs,=20 McGill University 
      3480 University=20 Str. Montreal, Quebec 
      tel:514-398-1691
    ----------------------------------------------------------------= -------------------
     
    ------=_NextPart_000_0001_01C11140.E99E9D70-- From owner-linux-xfs@oss.sgi.com Fri Jul 20 14:30:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KLUTr28993 for linux-xfs-outgoing; Fri, 20 Jul 2001 14:30:29 -0700 Received: from ente.berdmann.de (pD90115B6.dip.t-dialin.net [217.1.21.182]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KLUPV28971 for ; Fri, 20 Jul 2001 14:30:27 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Nhqk-0003dn-00; Fri, 20 Jul 2001 23:30:18 +0200 Message-ID: <3B58A2EA.E97615C3@berdmann.de> Date: Fri, 20 Jul 2001 23:30:18 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre8-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: "P.Dixon" CC: linux-xfs@oss.sgi.com Subject: Re: testing memory References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Sorry to pollute the list... a few weeks agao someone mentioned some > DOS software to test RAM. Could you tell me what it is? memtest86? From owner-linux-xfs@oss.sgi.com Fri Jul 20 14:30:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KLUas29055 for linux-xfs-outgoing; Fri, 20 Jul 2001 14:30:36 -0700 Received: from orion.ECE.McGill.CA (root@Orion.ECE.McGill.CA [132.206.75.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KLUYV29021 for ; Fri, 20 Jul 2001 14:30:34 -0700 Received: from proserpine (Proserpine.ECE.McGill.CA [132.206.31.219]) by orion.ECE.McGill.CA (8.9.1a/8.9.1) with ESMTP id RAA10863 for ; Fri, 20 Jul 2001 17:30:27 -0400 (EDT) Reply-To: From: "Hugo Levasseur" To: "LINUX-XFS" Subject: Problems compiling linux-2.4-xfs Date: Fri, 20 Jul 2001 17:31:38 -0400 Message-ID: <000701c11163$5bd9f610$db1fce84@proserpine> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am trying to compile linux with xfs support but every time I get a error and the make bzImage fails: It seems to be compiling in /linux/arch/i386/kdb when it fails. Here's an example error I get: i386-dis.c:3538 parse error before 'ATTRIBUTE_UNUSED' i386-dis.c: In function 'OP_MMX' Like I said this is just an example.. but they pretty much look all the same.... i386-dis.c:somenumber parse error before 'ATTRIBUTE_UNUSED' i386-dis.c: In fuction 'somefunction' Any clues? ------------------------------------------------------------------------ ----------- Hugo Levasseur, System Administrator ECE Computing Labs, McGill University 3480 University Str. Montreal, Quebec tel:514-398-1691 ------------------------------------------------------------------------ ----------- From owner-linux-xfs@oss.sgi.com Fri Jul 20 14:34:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KLYa729620 for linux-xfs-outgoing; Fri, 20 Jul 2001 14:34:36 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KLYZV29600 for ; Fri, 20 Jul 2001 14:34:35 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KLbu911076 for ; Fri, 20 Jul 2001 14:37:56 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2459002; Fri, 20 Jul 2001 16:33:13 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA82967; Fri, 20 Jul 2001 16:33:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KLXqd09102; Fri, 20 Jul 2001 16:33:52 -0500 Message-Id: <200107202133.f6KLXqd09102@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: hugol@ece.mcgill.ca cc: "LINUX-XFS" Subject: Re: Problem compiling linux-2.4-xfs In-Reply-To: Message from "Hugo Levasseur" of "Fri, 20 Jul 2001 17:25:03 EDT." <000001c11162$70aeb6d0$db1fce84@proserpine> Date: Fri, 20 Jul 2001 16:33:52 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > This is a multi-part message in MIME format. > > ------=_NextPart_000_0001_01C11140.E99E9D70 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: 7bit > > I am trying to compile linux with xfs support but every time I get a > error and the make bzImage fails: > > It seems to be compiling in /linux/arch/i386/kdb when it fails. Here's > an example error I get: > > i386-dis.c:3538 parse error before 'ATTRIBUTE_UNUSED' > i386-dis.c: In function 'OP_MMX' > > Like I said this is just an example.. but they pretty much look all the > same.... i386-dis.c:somenumber parse error before 'ATTRIBUTE_UNUSED' > i386-dis.c: In fuction 'somefunction' > > Any clues? > I don't know exactly where this comes from, but the quick fix it to turn off kdb, you do not need it for xfs. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 14:43:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KLh8l30292 for linux-xfs-outgoing; Fri, 20 Jul 2001 14:43:08 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KLh5V30270 for ; Fri, 20 Jul 2001 14:43:05 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6KLlIF07103 for ; Fri, 20 Jul 2001 14:47:18 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2489925; Fri, 20 Jul 2001 16:41:31 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA31916; Fri, 20 Jul 2001 16:41:31 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6KLgAB10663; Fri, 20 Jul 2001 16:42:10 -0500 Message-Id: <200107202142.f6KLgAB10663@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: LENHOF Jean-Yves cc: linux-xfs@oss.sgi.com Subject: Re: You can have a look on this test... In-Reply-To: Message from LENHOF Jean-Yves of "Fri, 20 Jul 2001 22:30:56 GMT." <995661056000029@caramail.com> Date: Fri, 20 Jul 2001 16:42:10 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > This message is in MIME format. Since your mail reader does not understand > this format, some or all of this message may not be legible. > > --=_NextPart_Caramail_000029995661056_ID > Content-Type: text/plain; charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > > http://aurora.zemris.fer.hr/filesystems/final.html > _________________________________________________________ > Le journal des abonn=E9s Caramail - http://www.carazine.com > > > --=_NextPart_Caramail_000029995661056_ID-- Well, they could have made xfs go faster with some mkfs and mount options, this is usually what happens in benchmarks which just test out of the box performance. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 20 14:45:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KLj0930548 for linux-xfs-outgoing; Fri, 20 Jul 2001 14:45:00 -0700 Received: from mustang.centralnet.ch (mustang.centralnet.ch [193.135.146.12]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KLiwV30528 for ; Fri, 20 Jul 2001 14:44:58 -0700 Received: from vollmann.ch (luz146.centralnet.ch [193.135.147.146]) by mustang.centralnet.ch (8.9.3/8.9.3) with ESMTP id XAA68189 for ; Fri, 20 Jul 2001 23:44:53 +0200 (MES) Received: from two.vollmann.ch (localhost [127.0.0.1]) by vollmann.ch (8.8.6/8.8.5) with SMTP id VAA01958; Fri, 20 Jul 2001 21:45:43 GMT Message-ID: <3B58A687.1FDBD7A9@vollmann.ch> Date: Fri, 20 Jul 2001 21:45:43 +0000 From: Detlef Vollmann Organization: vollmann engineering gmbh X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.14-5.0 i586) MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: XFS 1.0.1 SuSE Port References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dean Brissinger wrote: > > Has anyone attempted to get XFS working on SuSE? I need to get that > going but don't want to invest time in something that's already been > done. The German "Linux Magazin" had an article on that in its July issue. They used SuSE 7.1 kernel 2.4.2 and used the patches for XFS 1.0. They reported one uncritical patch-reject and used gcc 2.95.2 (by manually changing the Linux top Makefile). For compiling xfsprogs, they had to install e2fsprogs-devel (as usual) and to comment out two includes (lvm_log.h and lvm_config.h) from include/lib/liblvm.h. After that, everything worked fine and they reported good performance. But don't know about 1.0.1. Detlef -- Detlef Vollmann vollmann engineering gmbh Tel: +41-41-4120911 P.O. Box 5106 Fax: +41-41-4120912 CH-6000 Luzern 5 / Switzerland eMail: dv@vollmann.ch From owner-linux-xfs@oss.sgi.com Fri Jul 20 15:02:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KM2lU32158 for linux-xfs-outgoing; Fri, 20 Jul 2001 15:02:47 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KM2hV32136 for ; Fri, 20 Jul 2001 15:02:43 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA05385 for ; Fri, 20 Jul 2001 15:00:44 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2488582 for ; Fri, 20 Jul 2001 16:59:30 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA83795 for ; Fri, 20 Jul 2001 16:59:30 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6KM09b10809; Fri, 20 Jul 2001 17:00:09 -0500 Message-Id: <200107202200.f6KM09b10809@jen.americas.sgi.com> Date: Fri, 20 Jul 2001 17:00:09 -0500 Subject: TAKE - merge up to 2.4.7-pre9 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk One more version..... this is Linus's patch, plus the fix he posted for the oops on startup. I have thrashed it most of the day here without problems. Steve Date: Fri Jul 20 14:54:16 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99335a linux/drivers/ieee1394/sbp2.c - 1.1 linux/drivers/ieee1394/sbp2.h - 1.1 linux/include/linux/cramfs_fs_sb.h - 1.1 linux/include/linux/cramfs_fs.h - 1.1 linux/scripts/cramfs/cramfsck.c - 1.1 linux/net/socket.c - 1.23 linux/net/ipv4/route.c - 1.23 linux/kernel/sys.c - 1.22 linux/include/net/route.h - 1.11 linux/include/linux/sched.h - 1.41 linux/include/linux/prctl.h - 1.7 linux/include/linux/netdevice.h - 1.24 linux/include/linux/mm.h - 1.58 linux/include/linux/fs.h - 1.103 linux/include/linux/blkdev.h - 1.32 linux/include/asm-sparc64/atomic.h - 1.8 linux/include/asm-sparc/bitops.h - 1.10 linux/fs/proc/base.c - 1.28 linux/fs/nfs/nfsroot.c - 1.9 linux/fs/exec.c - 1.43 linux/fs/binfmt_aout.c - 1.21 linux/fs/affs/amigaffs.c - 1.6 linux/drivers/scsi/st.h - 1.10 linux/drivers/scsi/st.c - 1.30 linux/drivers/scsi/scsi.c - 1.38 linux/drivers/scsi/gdth_proc.c - 1.9 linux/drivers/sbus/char/sunkbd.c - 1.16 linux/drivers/isdn/hisax/config.c - 1.21 linux/drivers/block/ll_rw_blk.c - 1.72 linux/drivers/block/genhd.c - 1.16 linux/arch/sparc64/kernel/ptrace.c - 1.9 linux/arch/sparc64/kernel/binfmt_aout32.c - 1.16 linux/arch/sparc64/defconfig - 1.40 linux/arch/sparc64/config.in - 1.41 linux/arch/sparc/mm/sun4c.c - 1.27 linux/arch/sparc/mm/srmmu.c - 1.25 linux/arch/sparc/mm/init.c - 1.25 linux/arch/sparc/mm/generic.c - 1.8 linux/arch/sparc/lib/bitops.S - 1.5 linux/arch/sparc/kernel/sun4d_irq.c - 1.11 linux/arch/sparc/kernel/sparc_ksyms.c - 1.25 linux/arch/sparc/kernel/rtrap.S - 1.8 linux/arch/sparc/kernel/ptrace.c - 1.9 linux/arch/sparc/kernel/irq.c - 1.17 linux/arch/sparc/defconfig - 1.24 linux/arch/ppc/kernel/ptrace.c - 1.9 linux/arch/ppc/kernel/process.c - 1.29 linux/arch/ppc/kernel/misc.S - 1.29 linux/arch/ppc/kernel/irq.c - 1.30 linux/arch/ppc/kernel/head.S - 1.27 linux/arch/mips/kernel/ptrace.c - 1.10 linux/arch/m68k/kernel/ptrace.c - 1.8 linux/arch/i386/kernel/ptrace.c - 1.14 linux/arch/arm/kernel/ptrace.c - 1.11 linux/arch/alpha/kernel/ptrace.c - 1.10 linux/Makefile - 1.104 linux/Documentation/Configure.help - 1.89 linux/drivers/i2o/i2o_block.c - 1.23 linux/kernel/ptrace.c - 1.13 linux/arch/ppc/kernel/ppc_asm.h - 1.7 linux/arch/ppc/kernel/entry.S - 1.21 linux/arch/sh/kernel/ptrace.c - 1.8 linux/drivers/net/starfire.c - 1.17 linux/drivers/scsi/scsi_lib.c - 1.32 linux/Documentation/filesystems/cramfs.txt - 1.4 linux/scripts/cramfs/mkcramfs.c - 1.6 linux/fs/cramfs/inode.c - 1.16 linux/fs/cramfs/cramfs.h - 1.3 linux/include/asm-sparc/pgalloc.h - 1.10 linux/drivers/ieee1394/raw1394.c - 1.10 linux/drivers/ieee1394/ieee1394_core.h - 1.5 linux/drivers/ieee1394/pcilynx.c - 1.9 linux/drivers/ieee1394/ieee1394_core.c - 1.8 linux/drivers/ieee1394/ohci1394.h - 1.10 linux/drivers/ieee1394/ohci1394.c - 1.12 linux/drivers/ieee1394/ieee1394_types.h - 1.7 linux/drivers/ieee1394/ieee1394_transactions.h - 1.3 linux/drivers/ieee1394/ieee1394_transactions.c - 1.6 linux/drivers/ieee1394/ieee1394_syms.c - 1.6 linux/drivers/ieee1394/hosts.h - 1.5 linux/drivers/ieee1394/hosts.c - 1.6 linux/drivers/ieee1394/highlevel.h - 1.3 linux/drivers/ieee1394/Config.in - 1.5 linux/drivers/ieee1394/csr.c - 1.6 linux/drivers/ieee1394/aic5800.h - 1.2 linux/drivers/ieee1394/Makefile - 1.6 linux/drivers/ieee1394/highlevel.c - 1.4 linux/drivers/ieee1394/aic5800.c - 1.6 linux/scripts/cramfs/GNUmakefile - 1.2 linux/fs/cramfs/README - 1.2 linux/arch/ia64/kernel/entry.S - 1.14 linux/arch/ia64/kernel/ptrace.c - 1.9 linux/include/asm-ia64/processor.h - 1.11 linux/arch/mips64/kernel/ptrace.c - 1.5 linux/drivers/ide/ide.c - 1.23 linux/drivers/ide/ide-cd.c - 1.15 linux/drivers/block/elevator.c - 1.9 linux/include/linux/if_pppox.h - 1.4 linux/drivers/net/pppox.c - 1.6 linux/drivers/net/pppoe.c - 1.15 linux/arch/s390/kernel/ptrace.c - 1.4 linux/kdb/modules/kdbm_vm.c - 1.10 linux/drivers/ieee1394/guid.c - 1.5 linux/drivers/ieee1394/video1394.c - 1.6 linux/drivers/ieee1394/video1394.h - 1.4 linux/drivers/scsi/cpqfcTSinit.c - 1.7 linux/include/linux/ethtool.h - 1.4 linux/arch/parisc/kernel/ptrace.c - 1.2 linux/drivers/scsi/osst.h - 1.4 linux/drivers/scsi/osst.c - 1.6 linux/arch/s390x/kernel/ptrace.c - 1.3 linux/arch/cris/kernel/ptrace.c - 1.3 linux/arch/ppc/boot/prep/Makefile - 1.3 linux/arch/ppc/boot/pmac/Makefile - 1.3 linux/arch/ppc/boot/chrp/Makefile - 1.2 From owner-linux-xfs@oss.sgi.com Fri Jul 20 15:19:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KMJ8o01039 for linux-xfs-outgoing; Fri, 20 Jul 2001 15:19:08 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KMJ6V01017 for ; Fri, 20 Jul 2001 15:19:06 -0700 Received: from auto-nb1.xs4all.nl (perle-wan1.coltex.nl [10.0.1.177]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6KMIte10414; Sat, 21 Jul 2001 00:18:59 +0200 Message-Id: <4.3.2.7.2.20010721001710.031e3538@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 21 Jul 2001 00:18:40 +0200 To: Detlef Vollmann , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: XFS 1.0.1 SuSE Port In-Reply-To: <3B58A687.1FDBD7A9@vollmann.ch> References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:45 20-7-2001 +0000, Detlef Vollmann wrote: >Dean Brissinger wrote: > > > > Has anyone attempted to get XFS working on SuSE? I need to get that > > going but don't want to invest time in something that's already been > > done. > >The German "Linux Magazin" had an article on that in its July issue. >They used SuSE 7.1 kernel 2.4.2 and used the patches for XFS 1.0. >They reported one uncritical patch-reject and used gcc 2.95.2 >(by manually changing the Linux top Makefile). >For compiling xfsprogs, they had to install e2fsprogs-devel >(as usual) and to comment out two includes (lvm_log.h and >lvm_config.h) from include/lib/liblvm.h. >After that, everything worked fine and they reported good >performance. > >But don't know about 1.0.1. You could try fetching all the 1.0.1 Source RPMS and rebuild those on your SuSE system. Try that first. I don't have SuSE so I can't make those. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 20 15:24:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KMOg601681 for linux-xfs-outgoing; Fri, 20 Jul 2001 15:24:42 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KMOdV01655 for ; Fri, 20 Jul 2001 15:24:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA00997 for ; Fri, 20 Jul 2001 15:24:28 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from poppy-e185.americas.sgi.com (poppy.americas.sgi.com [128.162.185.207]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2488817; Fri, 20 Jul 2001 17:23:22 -0500 (CDT) Received: from sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id RAA71192; Fri, 20 Jul 2001 17:23:21 -0500 (CDT) Message-ID: <3B58AF3D.2B1E3D89@sgi.com> Date: Fri, 20 Jul 2001 17:22:53 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1smp i686) X-Accept-Language: en MIME-Version: 1.0 To: Seth Mos CC: Detlef Vollmann , linux-xfs@oss.sgi.com Subject: Re: XFS 1.0.1 SuSE Port References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> <4.3.2.7.2.20010721001710.031e3538@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos wrote: > You could try fetching all the 1.0.1 Source RPMS and rebuild those on your > SuSE system. > > Try that first. I don't have SuSE so I can't make those. But that would give you Red Hat kernels on your SuSE system... I think what people may be looking for are SuSE kernels (w/ all their patches, etc) and XFS added on. Or maybe the original poster just wanted to run a generic kernel + XFS on his SuSE system, in which case we're all getting OT here. :) -Eric From owner-linux-xfs@oss.sgi.com Fri Jul 20 15:34:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KMYrP02637 for linux-xfs-outgoing; Fri, 20 Jul 2001 15:34:53 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KMYlV02611 for ; Fri, 20 Jul 2001 15:34:47 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id AAA21139; Sat, 21 Jul 2001 00:34:31 +0200 (CEST) Message-Id: <4.3.2.7.2.20010721002531.03c65210@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 21 Jul 2001 00:34:17 +0200 To: Eric Sandeen From: Seth Mos Subject: Re: XFS 1.0.1 SuSE Port Cc: Detlef Vollmann , linux-xfs@oss.sgi.com In-Reply-To: <3B58AF3D.2B1E3D89@sgi.com> References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> <4.3.2.7.2.20010721001710.031e3538@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 17:22 20-7-2001 -0500, Eric Sandeen wrote: >Seth Mos wrote: > > > You could try fetching all the 1.0.1 Source RPMS and rebuild those on your > > SuSE system. > > > > Try that first. I don't have SuSE so I can't make those. > >But that would give you Red Hat kernels on your SuSE system... I think >what people may be looking for are SuSE kernels (w/ all their patches, >etc) and XFS added on. > >Or maybe the original poster just wanted to run a generic kernel + XFS >on his SuSE system, in which case we're all getting OT here. :) Indeed, -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Fri Jul 20 16:01:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KN1nH10398 for linux-xfs-outgoing; Fri, 20 Jul 2001 16:01:49 -0700 Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KN1lV10379 for ; Fri, 20 Jul 2001 16:01:47 -0700 Received: from Hermes.suse.de (Hermes.suse.de [213.95.15.136]) by Cantor.suse.de (Postfix) with ESMTP id 672771E524; Sat, 21 Jul 2001 01:01:41 +0200 (MEST) Date: Sat, 21 Jul 2001 01:01:40 +0200 From: Andi Kleen To: Dean Brissinger Cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.0.1 SuSE Port Message-ID: <20010721010140.A32159@gruyere.muc.suse.de> References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from brissing@vexcel.com on Fri, Jul 20, 2001 at 01:35:17PM -0600 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 01:35:17PM -0600, Dean Brissinger wrote: > Has anyone attempted to get XFS working on SuSE? I need to get that > going but don't want to invest time in something that's already been > done. ftp.suse.com:/pub/people/ak/xfs/xfs-2.4.6-5.bz2 is a XFS patch against a recent SuSE kernel (slightly post 7.2). It should apply to the 2.4 kernel tree you find in ftp.suse.com:/pub/people/mantel/next/ (note I just put a new version up; it may take some time before it appears on the ftp server due to mirror delays) Hope it helps, -Andi From owner-linux-xfs@oss.sgi.com Fri Jul 20 16:26:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KNQpc10739 for linux-xfs-outgoing; Fri, 20 Jul 2001 16:26:51 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KNQmV10720 for ; Fri, 20 Jul 2001 16:26:48 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id QAA06899 for ; Fri, 20 Jul 2001 16:24:22 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id SAA2486221 for ; Fri, 20 Jul 2001 18:25:31 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id SAA46188 for ; Fri, 20 Jul 2001 18:25:30 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6KNQ9O32464; Fri, 20 Jul 2001 18:26:09 -0500 Message-Id: <200107202326.f6KNQ9O32464@jen.americas.sgi.com> Date: Fri, 20 Jul 2001 18:26:09 -0500 Subject: TAKE - merge up to 2.4.7 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I swear Linus must be subscribed to this list and watching! Not much in here beyond the fix I included in pre9. Time to go home. Steve Date: Fri Jul 20 16:22:26 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99339a linux/drivers/ieee1394/nodemgr.c - 1.1 linux/drivers/ieee1394/nodemgr.h - 1.1 linux/kernel/ksyms.c - 1.97 linux/include/linux/mm.h - 1.59 linux/fs/proc/base.c - 1.29 linux/fs/namei.c - 1.34 linux/arch/sparc64/kernel/ptrace.c - 1.10 linux/arch/sparc64/defconfig - 1.41 linux/arch/sparc64/config.in - 1.42 linux/arch/sparc/kernel/ptrace.c - 1.10 linux/arch/ppc/kernel/ptrace.c - 1.10 linux/arch/mips/kernel/ptrace.c - 1.11 linux/arch/m68k/kernel/ptrace.c - 1.9 linux/arch/i386/kernel/ptrace.c - 1.15 linux/arch/arm/kernel/ptrace.c - 1.12 linux/arch/alpha/kernel/ptrace.c - 1.11 linux/Makefile - 1.105 linux/kernel/ptrace.c - 1.14 linux/arch/sh/kernel/ptrace.c - 1.9 linux/drivers/ieee1394/pcilynx.c - 1.10 linux/drivers/ieee1394/ieee1394_core.c - 1.9 linux/drivers/ieee1394/ohci1394.c - 1.13 linux/drivers/ieee1394/ieee1394_syms.c - 1.7 linux/drivers/ieee1394/Makefile - 1.7 linux/arch/ia64/kernel/ptrace.c - 1.10 linux/arch/mips64/kernel/ptrace.c - 1.6 linux/drivers/ide/ide-tape.c - 1.13 linux/arch/s390/kernel/ptrace.c - 1.5 linux/drivers/ieee1394/guid.c - 1.6 linux/drivers/ieee1394/guid.h - 1.3 linux/include/linux/mtd/cfi.h - 1.5 linux/arch/parisc/kernel/ptrace.c - 1.3 linux/arch/s390x/kernel/ptrace.c - 1.4 linux/arch/cris/kernel/ptrace.c - 1.4 From owner-linux-xfs@oss.sgi.com Fri Jul 20 16:28:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KNSW410866 for linux-xfs-outgoing; Fri, 20 Jul 2001 16:28:32 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KNSUV10847 for ; Fri, 20 Jul 2001 16:28:30 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6KNVp914804 for ; Fri, 20 Jul 2001 16:31:52 -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 JAA16480; Sat, 21 Jul 2001 09:27:08 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA27908; Sat, 21 Jul 2001 09:27:07 +1000 (AEST) Date: Sat, 21 Jul 2001 09:27:06 +1000 From: Nathan Scott To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: Anyone using XFS ACLs? (fwd) Message-ID: <20010721092706.A202730@wobbly.melbourne.sgi.com> References: <200107201833.f6KIX7H08390@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200107201833.f6KIX7H08390@jen.americas.sgi.com>; from lord@sgi.com on Fri, Jul 20, 2001 at 01:33:07PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, Jul 20, 2001 at 01:33:07PM -0500, Steve Lord wrote: > > This was sent privately, Danny later said he meant to send to the list, > any message mangling is entirely the fault of my mail tool. I expect we > will get something based on this into the tree fairly soon (is anyone > in Australia listening? hint hint). It's early Saturday morning, so other than me - probably not. Tim/Andrew should be able to get this in on Monday. The FILE_OFFSET_BITS problem is odd ... will need investigating. I think it should be safe in the acl package to switch that option off though... I'll need to look into the others, & see if I can remember why it was switched on originally. cheers. From owner-linux-xfs@oss.sgi.com Fri Jul 20 16:36:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KNaYr11023 for linux-xfs-outgoing; Fri, 20 Jul 2001 16:36:34 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KNaWV11002 for ; Fri, 20 Jul 2001 16:36:32 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6KNaNNe026567; Fri, 20 Jul 2001 18:36:23 -0500 (CDT) Message-ID: <3B58C027.8070903@thebarn.com> Date: Fri, 20 Jul 2001 18:35:03 -0500 From: Russell Cattelan User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.3-21mdk_XFS_1.0 i686; en-US; 0.8) Gecko/20010409 X-Accept-Language: en MIME-Version: 1.0 To: Eric Sandeen CC: Tuomas.Vitikainen@tietoenator.com, linux-xfs@oss.sgi.com Subject: Re: Isn't 32 MB enough? References: <8E1BC9FC59EBD311917D00508B61B662036A86B5@ccimaex02.imt.carel.fi> <995642346.18507.12.camel@stout.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric Sandeen wrote: > On 20 Jul 2001 10:53:53 +0300, Tuomas.Vitikainen@tietoenator.com wrote: > >> Hello! >> >> I've been trying to install a Red Hat system using >> ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/installer/RH7.1-SGI-XF >> S-1.0.1.iso to my old test PC but the install stops saying I don't have >> enough memory. Does your XFS-modified version require more RAM than the >> regular RH7.1 release since the regular version installs fine with 32 MB of >> RAM or is this some kind of a bug? > > > I don't believe that we explicitly put any extra memory constraints in > our version... if you can give me the exact error message you get, I'll > look and see what triggers it. The XFS initial ram disks are significantly larger than the default RH7.1 rd's. 32 meg ends up tripping the resource to low calculation code. Probably not much that can be done short of disabling the check and rolling the dice. Note the Mandrake installer does work on a 32meg box, in text mode, but it does work. > > > -Eric > From owner-linux-xfs@oss.sgi.com Fri Jul 20 16:37:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KNbYr11144 for linux-xfs-outgoing; Fri, 20 Jul 2001 16:37:34 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KNbVV11125 for ; Fri, 20 Jul 2001 16:37:31 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id BAA30880 for ; Sat, 21 Jul 2001 01:35:41 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 JAA16529; Sat, 21 Jul 2001 09:36:11 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA27532; Sat, 21 Jul 2001 09:36:10 +1000 (AEST) Date: Sat, 21 Jul 2001 09:36:09 +1000 From: Nathan Scott To: Detlef Vollmann Cc: linux-xfs@oss.sgi.com Subject: Re: XFS 1.0.1 SuSE Port Message-ID: <20010721093609.B202730@wobbly.melbourne.sgi.com> References: <200107201835.f6KIZcD44700@pilot12.cl.msu.edu> <3B58A687.1FDBD7A9@vollmann.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B58A687.1FDBD7A9@vollmann.ch>; from dv@vollmann.ch on Fri, Jul 20, 2001 at 09:45:43PM +0000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Fri, Jul 20, 2001 at 09:45:43PM +0000, Detlef Vollmann wrote: > Dean Brissinger wrote: > > > > Has anyone attempted to get XFS working on SuSE? I need to get that > > going but don't want to invest time in something that's already been > > done. > > The German "Linux Magazin" had an article on that in its July issue. > They used SuSE 7.1 kernel 2.4.2 and used the patches for XFS 1.0. > They reported one uncritical patch-reject and used gcc 2.95.2 > (by manually changing the Linux top Makefile). > For compiling xfsprogs, they had to install e2fsprogs-devel > (as usual) and to comment out two includes (lvm_log.h and > lvm_config.h) from include/lib/liblvm.h. This got fixed recently - I came across it by chance. You're the first person to actually report the problem, so thanks. > > But don't know about 1.0.1. > This xfsprogs build problem exists in 1.0.1 too, but only if you - have liblvm.a installed; and - /usr/include/linux/* headers don't match the 2.4.x kernel headers. The liblvm headers seem to include alot of kernel headers, and we have copies of some of the lvm headers in our tree - these only get used if "configure" finds liblvm.a though. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Jul 20 16:54:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6KNsoj11386 for linux-xfs-outgoing; Fri, 20 Jul 2001 16:54:50 -0700 Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6KNskV11367 for ; Fri, 20 Jul 2001 16:54:46 -0700 Received: from arts.usyd.edu.au (IDENT:matthew@holly.aitch.ucc.usyd.edu.au [129.78.226.234]) by plato.arts.usyd.edu.au (8.9.3/8.9.3) with ESMTP id JAA30914 for ; Sat, 21 Jul 2001 09:54:42 +1000 (EST) Message-ID: <3B58C4BE.E2535CA0@arts.usyd.edu.au> Date: Sat, 21 Jul 2001 09:54:38 +1000 From: Matthew Geier Organization: Arts IT Unit, Sydney University X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre3-xfs i686) X-Accept-Language: en, pdf MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Samba 2.2.1 RPMS with ACL References: <3B52A14E.6D0D4FA5@ch.sauter-bc.com><3B563C52.A3101025@xfs.lists.logout.sh> <20010720010215.77ebf768.jpenix@projectdesign.com> <010d01c11103$53d55af0$2df958c1@mpb> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------msBAF4A62C59257E47E09BB48C" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------msBAF4A62C59257E47E09BB48C Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > > > > Well, I've built a RPM from the official Samba 2.2.1a tarball. It works > > > for > > > me on a RH-7.0 system, but YMMV. You can find it at > > > http://www.hum.auc.dk/~mpb/samba-2.2.1a-20010711.i386.rpm If somebody > > > would > > > stick it on the SGI server, that would be fine. > > > > Any chance we could get you to post the .src.rpm? That way we could tweak > > it if our mileage doesn't vary correctly :^) Im successfully compiled my own samba 2.2.1 on a RH 7.1 + XFS system. For 'historical' reasons I keep samba outside the RPM/Redhat configure system - all my scripts know about /usr/local/samba... I did notice one problem with Samba on XFS systems. Quota support doesn't work. After a look in smbd/quota.c, I see the quota's don't work as XFS doesn't fill out the standard linux quota data structure, you have to use XFS specfic structures. NetAtalk also has linux quota code that has exactly the same problem. Any particular reason why XFS doesn't fill out the 'standard' quota data structure. As it stands any linux application that checks quota's wont see XFS file system quotas with out modification. If you run multiple file systems the quota code then needs to know the file system type... Sure you might get more information out of the XFS specific one, but the basic info is the same. --------------msBAF4A62C59257E47E09BB48C Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIH0AYJKoZIhvcNAQcCoIIHwTCCB70CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BbswggKKMIIB86ADAgECAgMFMYswDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTA3MDkxOTEyNThaFw0wMjA3MDkxOTEyNTha MEoxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJzAlBgkqhkiG9w0BCQEWGG1h dHRoZXdAYXJ0cy51c3lkLmVkdS5hdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1H+o MQ4xn5lDS/7p9rYboPW7grw13lXOj7Xisip37QttkX7Ga3ITBXnsAKnuFK3Z7GtILACBXil1 BngLBOd0AlW9zqQBXEOP9aODNJzBsTb3+tOHwQo6shcORKQArKEinG00SuwBdzxALU3KWT6E yIUSvoz7q0PN4C8qUF3t00sCAwEAAaM1MDMwIwYDVR0RBBwwGoEYbWF0dGhld0BhcnRzLnVz eWQuZWR1LmF1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAiJu7SNBXsW7I+ZH9 e2+0M47BmR3DxV31VbW9mKcwuamusWSJJEy5MAKZc8b0snRX/XDkCpM+av3VxDJX8T3rxOE0 siyCC6Tclu6wjwjw0goXK4N6Xhsz+qwIfdoclNZkqK5yInEZtc5ijKr0IPRgch79f35WP82C SNHVYApmjzgwggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcN MDIwODI5MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmlj YXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMw MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNE KYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu 2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQAB o04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAcxtvJmWL/xU0 S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONntUPQ6bDSSrOaSnG7BIwHC CafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2lhglTWr0ncXDkS+p lrgFPFL83eliA0gxggHdMIIB2QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNV BAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS U0EgMjAwMC44LjMwAgMFMYswCQYFKw4DAhoFAKCBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0wMTA3MjAyMzU0MzlaMCMGCSqGSIb3DQEJBDEWBBTDhSgJ nhMyoKrglevSMcvv7ur78DA6BgkqhkiG9w0BCQ8xLTArMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgAnNHL5vOhOJfakkzbWT KYdyybwvsaIGhvNhrnSdYFwaSiPpyv+6yXjoaG6ax7Q5IWtVjeoe9dELE8yD0vK/JzFx/wOj 8TsAGJPN1BSNnYd5ltJzIfUn1X24tExO+jNBK6YSe0v4zBHakRHrNAk215qzi93oJB/UBlj0 cyr0qZ+L --------------msBAF4A62C59257E47E09BB48C-- From owner-linux-xfs@oss.sgi.com Fri Jul 20 20:00:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6L30ol13728 for linux-xfs-outgoing; Fri, 20 Jul 2001 20:00:50 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6L30jV13709 for ; Fri, 20 Jul 2001 20:00:46 -0700 Received: (qmail 29163 invoked from network); 21 Jul 2001 03:00:40 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 21 Jul 2001 03:00:40 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: hugol@ece.mcgill.ca cc: "LINUX-XFS" Subject: Re: Problem compiling linux-2.4-xfs In-reply-to: Your message of "Fri, 20 Jul 2001 17:25:03 -0400." <000001c11162$70aeb6d0$db1fce84@proserpine> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 21 Jul 2001 13:00:39 +1000 Message-ID: <16646.995684439@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 20 Jul 2001 17:25:03 -0400, "Hugo Levasseur" wrote: >i386-dis.c:3538 parse error before 'ATTRIBUTE_UNUSED' ATTRIBUTE_UNUSED is defined in /usr/include/ansidecl.h. You need a recent binutils, I run with with binutils-2.9.5.0.22-6. From owner-linux-xfs@oss.sgi.com Fri Jul 20 20:09:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6L39n613920 for linux-xfs-outgoing; Fri, 20 Jul 2001 20:09:49 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6L39iV13900 for ; Fri, 20 Jul 2001 20:09:45 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 059A8756 for ; Sat, 21 Jul 2001 11:09:39 +0800 (PHT) Date: Sat, 21 Jul 2001 11:09:39 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: TAKE - merge up to 2.4.7 In-Reply-To: <200107202326.f6KNQ9O32464@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Fri, 20 Jul 2001 at 18:26, Steve Lord wrote: > I swear Linus must be subscribed to this list and watching! I doubt he'd have the time/patience. Besides, if he joined this list he'd have to join the ReiserFS and JFS lists, too, and more, out of fairness. I've been noticing, though, that even ReiserFS has some problems getting some patches to him. I wonder what's up with "the big guy". Hmm. > Not much in here beyond the fix I included in pre9. But I guess this at least works as well as pre9 which you said you thrashed for most of the day without problems? > Time to go home. I hope you got a good night's (day's?) rest. I can imagine how tough it is to keep up with the Linux kernel changes. A number of mainstream developers have shied away from Linux because of having to keep up with this. Thanks for the great work, guys! :) --> Jijo --- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Fri Jul 20 20:43:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6L3h2S14213 for linux-xfs-outgoing; Fri, 20 Jul 2001 20:43:02 -0700 Received: from rebel.net.au (IDENT:root@mail.rebel.net.au [203.20.69.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6L3gxV14194 for ; Fri, 20 Jul 2001 20:43:00 -0700 Received: from rebel.net.au (dialup-7.rebel.net.au [203.20.69.77]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id NAA17730; Sat, 21 Jul 2001 13:12:35 +0930 Message-ID: <3B58FB27.3C82DDB2@rebel.net.au> Date: Sat, 21 Jul 2001 13:16:47 +0930 From: David Lloyd X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i586) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: You can have a look on this test... References: <200107202142.f6KLgAB10663@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve! > Well, they could have made xfs go faster with some mkfs and mount options, > this is usually what happens in benchmarks which just test out of the box > performance. Do you mean: * Well, they were capable of making xfs go faster with some mkfs and mount option but did not OR * they probably did make xfs go faster with some mkfs and mount options ?? Unfortunately could have is very ambiguous :-( DSL -- "The greatest thing you'll ever learn is just to love and to be loved in return." - David Bowie (Nature Boy from Moulin Rouge) From owner-linux-xfs@oss.sgi.com Fri Jul 20 22:38:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6L5cQR14944 for linux-xfs-outgoing; Fri, 20 Jul 2001 22:38:26 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6L5cOV14925 for ; Fri, 20 Jul 2001 22:38:24 -0700 Received: from there (localhost.localdomain [127.0.0.1]) by wwweasel.geeksrus.net (8.11.4/8.11.2) with SMTP id f6L5cHH24547 for ; Sat, 21 Jul 2001 01:38:17 -0400 Message-Id: <200107210538.f6L5cHH24547@wwweasel.geeksrus.net> Content-Type: text/plain; charset="iso-8859-1" From: Alan Eldridge To: XFS list Subject: Linux Magazine 7/2001 Date: Sat, 21 Jul 2001 01:38:17 -0400 X-Mailer: KMail [version 1.2.9] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The SGI XFS Release made "Zonker's Product Picks" in the July issue of LINUX Magazine. There's a nice little product blurb and a really cool "sgi XFS RELEASE 1.0" graphic. From owner-linux-xfs@oss.sgi.com Fri Jul 20 22:40:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6L5eN115063 for linux-xfs-outgoing; Fri, 20 Jul 2001 22:40:23 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6L5eLV15044 for ; Fri, 20 Jul 2001 22:40:22 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15NpUs-0005re-00; Sat, 21 Jul 2001 17:40:14 +1200 From: "Juha Saarinen" To: "'Alan Eldridge'" , "'XFS list'" Subject: RE: Linux Magazine 7/2001 Date: Sat, 21 Jul 2001 17:40:44 +1200 Message-ID: <000d01c111a7$af54deb0$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <200107210538.f6L5cHH24547@wwweasel.geeksrus.net> Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Ahhh... you know journos... anyone can buy a good review off them. ;-> -- Juha :: -----Original Message----- :: From: owner-linux-xfs@oss.sgi.com :: [mailto:owner-linux-xfs@oss.sgi.com] On Behalf Of Alan Eldridge :: Sent: Saturday, 21 July 2001 17:38 :: To: XFS list :: Subject: Linux Magazine 7/2001 :: :: :: The SGI XFS Release made "Zonker's Product Picks" in the :: July issue of LINUX :: Magazine. There's a nice little product blurb and a really :: cool "sgi XFS :: RELEASE 1.0" graphic. :: :: :: From owner-linux-xfs@oss.sgi.com Sat Jul 21 04:16:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LBGPB17532 for linux-xfs-outgoing; Sat, 21 Jul 2001 04:16:25 -0700 Received: from ente.berdmann.de (pD9011852.dip.t-dialin.net [217.1.24.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LBGMV17513 for ; Sat, 21 Jul 2001 04:16:22 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Nuk2-0001Xd-00 for linux-xfs@oss.sgi.com; Sat, 21 Jul 2001 13:16:14 +0200 Message-ID: <3B59647E.8F28594A@berdmann.de> Date: Sat, 21 Jul 2001 13:16:14 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: different modes for symlinks? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I'm wondering about different modes of symlinks on XFS filesystems: # ll /usr/tmp /usr/src/linux lrwxr-xr-x 1 root root 19 Jul 10 00:36 /usr/src/linux -> linux-2.4-xfs/linux lrwx------ 1 root root 10 Jul 10 00:27 /usr/tmp -> ../var/tmp # ll -d /var/tmp /usr/src/linux-2.4-xfs/linux drwxr-xr-x 16 root root 4096 Jul 21 09:09 /usr/src/linux-2.4-xfs/linux drwxrwxrwt 2 root root 4096 Jul 21 10:06 /var/tmp I'm used to mode 777 for a symlink. Why here 755 and 700 and only the mode of /usr/src/linux matching the mode of the dir it points to? From owner-linux-xfs@oss.sgi.com Sat Jul 21 05:08:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LC84S17978 for linux-xfs-outgoing; Sat, 21 Jul 2001 05:08:04 -0700 Received: from ente.berdmann.de (pD9011852.dip.t-dialin.net [217.1.24.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LC7wV17958 for ; Sat, 21 Jul 2001 05:07:59 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15NvXz-0001jR-00; Sat, 21 Jul 2001 14:07:51 +0200 Message-ID: <3B597097.6CBEC94D@berdmann.de> Date: Sat, 21 Jul 2001 14:07:51 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Timothy Shimmin CC: Linux XFS Mailing List Subject: Re: xfsrestore deletes files in cumulative restores (was: xfsdump/xfsrestore fails Zwicky's torture test) References: <3B3F5079.F1776C04@berdmann.de> <3B4838D0.5BAEDF4F@berdmann.de> <3B485058.9389834C@berdmann.de> <20010709155428.C11622@boing.melbourne.sgi.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Timothy, > You've had a few xfsdump/xfsrestore emails of late :) "No one cares if you can back up - only if you can recover.?" (W. Curtis Preston, Unix Backup & Recovery, O'Reilly, 1999, xiv) > > xfsrestore.debug.3 told me xfsrestore had deleted user/be/Sent/xy/290.: > > > > [...] > > /usr/sbin/xfsrestore: rename nondir user/be/Sent/xy/290. to > > orphanage/9074670.1 > > /usr/sbin/xfsrestore: unlink nondir orphanage/9074670.1 > > [...] > > /usr/sbin/xfsrestore: restoring user/be/Sent/xy/291. (9074676 0) > > /usr/sbin/xfsrestore: restoring regular file ino 9074676 > > user/be/Sent/xy/291. > > /usr/sbin/xfsrestore: truncating user/be/Sent/xy/291. from 0 to 775 > > /usr/sbin/xfsrestore: restore complete: 76 seconds elapsed > > > > What's going on here? I'm using xfsdump-1.0.9-0. > > It looks like that this is happening in the function > xfsdump/restore/tree.c/proc_hardlinks_cb(). > I'm not sure what this code is trying to do ! > However, I'll post a bug on this at SGI and > look into it further. > Thanks for the report. I just investigated it a little further. I did another cumulative restore of /var/spool/imap (based on level 0 on 2001-07-12). This time I'm using xfsdump-1.0.11-0. (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.0 (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.1 (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.2 (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.3 (/usr/sbin/amrestore -p $TAPE ente imap | /usr/sbin/xfsrestore -r -v trace - .) > xfsrestore.debug.4 One of the files missing after the complete restore is user/ap/in/52. xfsrestore told me it was deleted applying level 2: # grep user/ap/in/52. xfsrestore.debug.? xfsrestore.debug.0:/usr/sbin/xfsrestore: link user/ap/in/MKSports/21. to user/ap/in/52. (4504894 0) xfsrestore.debug.0:/usr/sbin/xfsrestore: linking user/ap/in/MKSports/21. to user/ap/in/52. xfsrestore.debug.2:/usr/sbin/xfsrestore: unlink user/ap/in/52. But it's still there in /var/spool/imap (where the dump was taken from): # ls -li /var/spool/imap/user/ap/in/52. 4504894 -rw------- 2 cyrus root 5464 Apr 13 14:12 /var/spool/imap/user/ap/in/52. So it has a hardlink to it. What's the other filename pointing to the inode 4504894? # find /var/spool/imap/user/ap -inum 4504894 -ls 4504894 8 -rw------- 2 cyrus root 5464 Apr 13 14:12 /var/spool/imap/user/ap/in/MKSports/21. 4504894 8 -rw------- 2 cyrus root 5464 Apr 13 14:12 /var/spool/imap/user/ap/in/52. In the restored tree, there's only user/ap/in/MKSports/21.: # ll user/ap/in/MKSports/21. -rw------- 1 cyrus root 5464 Apr 13 14:12 user/ap/in/MKSports/21. No other link to it. This file was restored in level 0, too: # grep user/ap/in/MKSports/21. xfsrestore.debug.? xfsrestore.debug.0:/usr/sbin/xfsrestore: restoring user/ap/in/MKSports/21. (4504894 0) xfsrestore.debug.0:/usr/sbin/xfsrestore: restoring regular file ino 4504894 user/ap/in/MKSports/21. xfsrestore.debug.0:/usr/sbin/xfsrestore: truncating user/ap/in/MKSports/21. from 0 to 5464 xfsrestore.debug.0:/usr/sbin/xfsrestore: link user/ap/in/MKSports/21. to user/ap/in/52. (4504894 0) xfsrestore.debug.0:/usr/sbin/xfsrestore: linking user/ap/in/MKSports/21. to user/ap/in/52. Ok, let's grep some more... # grep -n "unlink " /usr/src/linux-2.4-xfs/cmd/xfsdump/restore/* /usr/src/linux-2.4-xfs/cmd/xfsdump/restore/tree.c:1442: "unlink %s\n", (CVS checkout of this morning) This line is in the function noref_elim_recurse (line 1181 in tree.c) and there's a comment after the else in line 1330: /* determine if we can unlink this node. * if its not real, and not refed, simple. * if real and not refed and there is at least * one unreal refed node and no other real * nodes around, must put this one in orphanage * rather than unlinking it. */ So, what's an unreal node? And a node not referred to? Maybe this lost link user/ap/in/52. was not referred to in the level 0 dump? Who's doing the mess? xfsdump not referring to or telling xfsrestore of unreal nodes? Or does xfsrestore get things wrong? From owner-linux-xfs@oss.sgi.com Sat Jul 21 05:17:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LCHml18249 for linux-xfs-outgoing; Sat, 21 Jul 2001 05:17:48 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LCHkV18230 for ; Sat, 21 Jul 2001 05:17:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id FAA07894 for ; Sat, 21 Jul 2001 05:17:07 -0700 (PDT) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id HAA1586839; Sat, 21 Jul 2001 07:16:13 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id HAA97914; Sat, 21 Jul 2001 07:16:12 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id HAA42259; Sat, 21 Jul 2001 07:16:12 -0500 (CDT) Message-Id: <200107211216.HAA42259@fsgi158.americas.sgi.com> Subject: Re: different modes for symlinks? To: be@berdmann.de (Bernhard R. Erdmann) Date: Sat, 21 Jul 2001 07:16:11 -0500 (CDT) Cc: linux-xfs@oss.sgi.com (Linux XFS Mailing List) In-Reply-To: <3B59647E.8F28594A@berdmann.de> from "Bernhard R. Erdmann" at Jul 21, 2001 01:16:14 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Hi, > > I'm wondering about different modes of symlinks on XFS filesystems: > > # ll /usr/tmp /usr/src/linux > lrwxr-xr-x 1 root root 19 Jul 10 00:36 /usr/src/linux -> > linux-2.4-xfs/linux > lrwx------ 1 root root 10 Jul 10 00:27 /usr/tmp -> > ../var/tmp > # ll -d /var/tmp /usr/src/linux-2.4-xfs/linux > drwxr-xr-x 16 root root 4096 Jul 21 09:09 > /usr/src/linux-2.4-xfs/linux > drwxrwxrwt 2 root root 4096 Jul 21 10:06 /var/tmp > > I'm used to mode 777 for a symlink. Why here 755 and 700 and only the > mode of /usr/src/linux matching the mode of the dir it points to? > ll is probably an alias for "ls -l" which lists the status of the link itself and not the file or directory referenced by the symbolic link. "ls -lL " should list the status of the file or directory referenced by the link. Tad From owner-linux-xfs@oss.sgi.com Sat Jul 21 05:26:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LCQt118428 for linux-xfs-outgoing; Sat, 21 Jul 2001 05:26:55 -0700 Received: from ente.berdmann.de (pD9011852.dip.t-dialin.net [217.1.24.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LCQqV18407 for ; Sat, 21 Jul 2001 05:26:52 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15NvqC-0001oc-00; Sat, 21 Jul 2001 14:26:40 +0200 Message-ID: <3B5974DD.E108B2B9@berdmann.de> Date: Sat, 21 Jul 2001 14:26:05 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Juha Saarinen CC: Linux XFS Mailing List Subject: Re: 2.4.7-pre8-xfs breaks VMWare References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > after upgrading from 2.4.7-pre6-xfs to 2.4.7-pre8-xfs I found VMWare > > can't compile it's modules anymore. > > Any hint? There's a suggestion in vmware.for-linux.configuration, but it doesn't help: Path: news.vmware.com!not-for-mail Message-ID: <3B570E9C.E92BFE8A@vc.cvut.cz> From: Petr Vandrovec Newsgroups: vmware.for-linux.configuration Subject: Re: Build module vmmon fails Date: Thu, 19 Jul 2001 18:45:16 +0200 References: <9j55nc$drc$1@london.vmware.com> Lines: 25 Organization: Czech Technical University, Computing and Information Centre NNTP-Posting-Host: vanicka.vc.cvut.cz Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: cs,en Xref: ente.berdmann.de vmware.for-linux.configuration:413 Dirk Vornheder wrote: > > Hi ! > > After upgrading to kernel 2.4.7pre7 build of module And which vmware version do you have? > /lib/modules/2.4.7-pre7/build/include/asm/pgalloc.h: In function > `get_pgd_slow': > /lib/modules/2.4.7-pre7/build/include/asm/pgalloc.h:56: `PAGE_OFFSET' > undeclared (first use in this function) > /lib/modules/2.4.7-pre7/build/include/asm/pgalloc.h:56: (Each undeclared > identifier is reported only once > /lib/modules/2.4.7-pre7/build/include/asm/pgalloc.h:56: for each function > it appears in.) pgalloc.h forgot to include asm/page.h. Are you sure that you have /lib/modules/2.4.7-pre7/build/include/asm/page.h ? I do not know about any changes introduced in 2.4.7pre* which removed #include from somewhere... So if you are sure that you have vmware-2.0.4, Easiest thing is probably adding #include at the beginning of pgalloc.h ... Petr From owner-linux-xfs@oss.sgi.com Sat Jul 21 07:13:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LEDbe20326 for linux-xfs-outgoing; Sat, 21 Jul 2001 07:13:37 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LEDXV20307 for ; Sat, 21 Jul 2001 07:13:33 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA50213 for ; Sat, 21 Jul 2001 16:13:03 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2491861; Sat, 21 Jul 2001 09:12:14 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA73987; Sat, 21 Jul 2001 09:12:14 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6LECkj01007; Sat, 21 Jul 2001 09:12:46 -0500 Message-Id: <200107211412.f6LECkj01007@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: David Lloyd cc: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: You can have a look on this test... In-Reply-To: Message from David Lloyd of "Sat, 21 Jul 2001 13:16:47 +0930." <3B58FB27.3C82DDB2@rebel.net.au> Date: Sat, 21 Jul 2001 09:12:46 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Steve! > > > Well, they could have made xfs go faster with some mkfs and mount options, > > this is usually what happens in benchmarks which just test out of the box > > performance. > > > Do you mean: > > * Well, they were capable of making xfs go faster with some mkfs and > mount option but did not Yes, if they had used different mkfs options and mount options than the default then they could have made their tests go faster. I am not implying that they did or did not know they existed. The reason these options are not the default is that unless you are going to be pounding on the filesystem in a metadata intensive manner they will have a negative effect. A bigger log means slower mount and recovery, more incore log buffers means more memory chewed up. Steve > > OR > > * they probably did make xfs go faster with some mkfs and mount options > > ?? > > Unfortunately could have is very ambiguous :-( > > DSL > -- > "The greatest thing you'll ever learn is > just to love and to be loved in return." > - David Bowie (Nature Boy from Moulin Rouge) From owner-linux-xfs@oss.sgi.com Sat Jul 21 07:22:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LEMfP20589 for linux-xfs-outgoing; Sat, 21 Jul 2001 07:22:41 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LEMeV20568 for ; Sat, 21 Jul 2001 07:22:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6LEQ3921977 for ; Sat, 21 Jul 2001 07:26:03 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2492012; Sat, 21 Jul 2001 09:21:18 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA88608; Sat, 21 Jul 2001 09:21:18 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6LELoR01055; Sat, 21 Jul 2001 09:21:50 -0500 Message-Id: <200107211421.f6LELoR01055@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Alan Eldridge cc: XFS list Subject: Re: Linux Magazine 7/2001 In-Reply-To: Message from Alan Eldridge of "Sat, 21 Jul 2001 01:38:17 EDT." <200107210538.f6L5cHH24547@wwweasel.geeksrus.net> Date: Sat, 21 Jul 2001 09:21:50 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > The SGI XFS Release made "Zonker's Product Picks" in the July issue of LINUX > Magazine. There's a nice little product blurb and a really cool "sgi XFS > RELEASE 1.0" graphic. Ah ha, the infamous 1.0 logo, which marketing insisted we remove as it was not approved. They will be pleased ;-). If you have a copy of this save it for posterity, it may become a collectors item! Steve From owner-linux-xfs@oss.sgi.com Sat Jul 21 13:12:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LKCoB01392 for linux-xfs-outgoing; Sat, 21 Jul 2001 13:12:50 -0700 Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LKClV01370 for ; Sat, 21 Jul 2001 13:12:48 -0700 Received: from fwd01.sul.t-online.de by mailout06.sul.t-online.de with smtp id 15O37D-0002bt-04; Sat, 21 Jul 2001 22:12:43 +0200 Received: from there (340024412816-0001@[217.81.134.163]) by fwd01.sul.t-online.com with smtp id 15O37C-1kawUrC; Sat, 21 Jul 2001 22:12:42 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Nathan Scott , linux-xfs@oss.sgi.com Subject: Re: TAKE - userspace Date: Sat, 21 Jul 2001 22:12:59 +0200 X-Mailer: KMail [version 1.2.9] References: <200107200826.SAA36970@snort.melbourne.sgi.com> In-Reply-To: <200107200826.SAA36970@snort.melbourne.sgi.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <15O37C-1kawUrC@fwd01.sul.t-online.com> X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Freitag, 20. Juli 2001 10:26 schrieb Nathan Scott: > Important change for xfsdump and xfsrestore (and libraries that they > rely on)... we're now consistent with other backup/restore utilities > which need be available when only the root filesystem is mounted. What is the reason for putting libacl.a in /lib instead of leaving it in /usr/lib where it belongs IMHO ? This breaks all applications that try to link libacl.a at compiletime like Samba and Fileutils. Please move it back. ...Juergen From owner-linux-xfs@oss.sgi.com Sat Jul 21 13:36:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LKaed03408 for linux-xfs-outgoing; Sat, 21 Jul 2001 13:36:40 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LKacV03386 for ; Sat, 21 Jul 2001 13:36:38 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA15196; Sat, 21 Jul 2001 22:36:34 +0200 (CEST) Message-Id: <4.3.2.7.2.20010721222837.031d7178@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 21 Jul 2001 22:36:19 +0200 To: Hasch@t-online.de (Juergen Hasch), Nathan Scott , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: TAKE - userspace In-Reply-To: <15O37C-1kawUrC@fwd01.sul.t-online.com> References: <200107200826.SAA36970@snort.melbourne.sgi.com> <200107200826.SAA36970@snort.melbourne.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 22:12 21-7-2001 +0200, Juergen Hasch wrote: >Am Freitag, 20. Juli 2001 10:26 schrieb Nathan Scott: > > Important change for xfsdump and xfsrestore (and libraries that they > > rely on)... we're now consistent with other backup/restore utilities > > which need be available when only the root filesystem is mounted. > >What is the reason for putting libacl.a in /lib instead of leaving it in >/usr/lib where it belongs IMHO ? >This breaks all applications that try to link libacl.a at compiletime like >Samba and Fileutils. Please move it back. NO! If you only have your root filesystem, how would you then be able to run xfsdump or xfsrestore. let's see. You have a seriuous crash of your system and the /usr filesystem is lost. This means that you need to restore the /usr filesystem. Now comes the fun part, you run xfsrestore to get your /usr filesystem back but onfortunately you can't run xfs_repair to repair the fs or run xfsrestore to restore your backup. Now that would be stupid. Your system needs these utility's for minimal operation so they belong on / Check your utils for your ext2fs dump restore e2fscheck and others. Heck even chmod and co is sitting on the / fs. It's a pity that we need to move the lib because the rest of the "important" utils need to be on the root fs. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sat Jul 21 13:49:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LKnD504474 for linux-xfs-outgoing; Sat, 21 Jul 2001 13:49:13 -0700 Received: from mailout03.sul.t-online.de (mailout03.sul.t-online.com [194.25.134.81]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LKnBV04450 for ; Sat, 21 Jul 2001 13:49:11 -0700 Received: from fwd01.sul.t-online.de by mailout03.sul.t-online.de with smtp id 15O3gR-0007u3-07; Sat, 21 Jul 2001 22:49:07 +0200 Received: from there (340024412816-0001@[217.81.134.163]) by fwd01.sul.t-online.com with smtp id 15O3gO-0CJtrcC; Sat, 21 Jul 2001 22:49:04 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Seth Mos , Hasch@t-online.de (Juergen Hasch), Nathan Scott , linux-xfs@oss.sgi.com Subject: Re: TAKE - userspace Date: Sat, 21 Jul 2001 22:49:23 +0200 X-Mailer: KMail [version 1.2.9] References: <200107200826.SAA36970@snort.melbourne.sgi.com> <4.3.2.7.2.20010721222837.031d7178@pop.xs4all.nl> In-Reply-To: <4.3.2.7.2.20010721222837.031d7178@pop.xs4all.nl> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <15O3gO-0CJtrcC@fwd01.sul.t-online.com> X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello Seth, Am Samstag, 21. Juli 2001 22:36 schrieb Seth Mos: > At 22:12 21-7-2001 +0200, Juergen Hasch wrote: > >Am Freitag, 20. Juli 2001 10:26 schrieb Nathan Scott: > > > Important change for xfsdump and xfsrestore (and libraries that they > > > rely on)... we're now consistent with other backup/restore utilities > > > which need be available when only the root filesystem is mounted. > > > >What is the reason for putting libacl.a in /lib instead of leaving it in > >/usr/lib where it belongs IMHO ? > >This breaks all applications that try to link libacl.a at compiletime like > >Samba and Fileutils. Please move it back. > > NO! > > If you only have your root filesystem, how would you then be able to run > xfsdump or xfsrestore. > let's see. > > You have a seriuous crash of your system and the /usr filesystem is lost. > This means that you need to restore the /usr filesystem. > Now comes the fun part, you run xfsrestore to get your /usr filesystem back > but onfortunately you can't run xfs_repair to repair the fs or run > xfsrestore to restore your backup. libacl.a is a static library that is used only at compile time. This is because libacl.a contains only the stubs for libacl.so. No-one has *.a files in /lib, they are all in /usr/lib. Take a look in your /lib directory. You find the stubs for e.g. libc as /usr/lib/libc.a, but the actual libc.so in /lib. So you need libacl.so in /lib and libacl.a in /usr/lib. ...Juergen From owner-linux-xfs@oss.sgi.com Sat Jul 21 13:52:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LKqUB04877 for linux-xfs-outgoing; Sat, 21 Jul 2001 13:52:30 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LKqSV04852 for ; Sat, 21 Jul 2001 13:52:28 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.4) id f6LKqMe13697 for linux-xfs@oss.sgi.com; Sat, 21 Jul 2001 16:52:22 -0400 Date: Sat, 21 Jul 2001 16:52:08 -0400 From: Alan Eldridge To: Seth Mos Subject: Re: TAKE - userspace Message-ID: <20010721165208.A6472@wwweasel.geeksrus.net> References: <200107200826.SAA36970@snort.melbourne.sgi.com> <200107200826.SAA36970@snort.melbourne.sgi.com> <15O37C-1kawUrC@fwd01.sul.t-online.com> <4.3.2.7.2.20010721222837.031d7178@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.2.7.2.20010721222837.031d7178@pop.xs4all.nl>; from knuffie@xs4all.nl on Sat, Jul 21, 2001 at 10:36:19PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, Jul 21, 2001 at 10:36:19PM +0200, Seth Mos wrote: >>What is the reason for putting libacl.a in /lib instead of leaving it in >>/usr/lib where it belongs IMHO ? >>This breaks all applications that try to link libacl.a at compiletime like >>Samba and Fileutils. Please move it back. > >NO! > >If you only have your root filesystem, how would you then be able to run >xfsdump or xfsrestore. >let's see. D'ya think making the xfs* utils statically linked is a good compromise? Then the libs could go back in /usr/lib. PS I understand your point. How about Sun, where, for years, /bin => /usr/bin. Auuuggghhh!!!! -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Sat Jul 21 13:53:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LKrqF05144 for linux-xfs-outgoing; Sat, 21 Jul 2001 13:53:52 -0700 Received: from FW1.dt.navy.mil (FW1.dt.navy.mil [192.5.27.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LKroV05125 for ; Sat, 21 Jul 2001 13:53:50 -0700 Received: by FW1.dt.navy.mil; id QAA08202; Sat, 21 Jul 2001 16:54:19 -0400 (EDT) Received: from unknown(130.46.225.16) by FW1.dt.navy.mil via smap (V5.5) id xma008158; Sat, 21 Jul 01 16:53:36 -0400 Received: from NAVGATE.dt.navy.mil (navgate.dt.navy.mil [130.46.225.15]) by smtprelay.dt.navy.mil (8.9.3/8.9.3) with SMTP id QAA20646 for ; Sat, 21 Jul 2001 16:53:00 -0400 Received: from crbeex01.nswccd.navy.mil ([130.46.5.84]) by NAVGATE.dt.navy.mil (NAVIEG 2.1 bld 63) with SMTP id M2001072116525914995 ; Sat, 21 Jul 2001 16:52:59 -0400 Received: from PROFESSOR.dt.navy.mil ([157.187.160.235]) by crbeex01.nswccd.navy.mil with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PAXH3HJF; Sat, 21 Jul 2001 16:52:58 -0400 Received: from jtsdell (Bayview162-40.dt.navy.mil [157.187.162.40]) by professor.dt.navy.mil (8.8.8+Sun/8.8.8) with ESMTP id NAA16108; Sat, 21 Jul 2001 13:42:59 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.5.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15O37C-1kawUrC@fwd01.sul.t-online.com> Date: Sat, 21 Jul 2001 16:52:36 -0400 (EDT) Reply-To: John Trostel Organization: Connex From: John Trostel To: (Juergen Hasch) Subject: Re: TAKE - userspace Cc: linux-xfs@oss.sgi.com, Nathan Scott Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk It will NOT break Samba. The Samba check just looks to see if acl_get_file (or whatever) is available after a -lacl compile call. If your system looks for libraries in both /usr/lib and /lib, it will not break with the move. Another option, mentioned by Nathan, is to put a symbolic link in the /usr/lib directory to the real library residing in /lib. I tried the /lib location out with my Samba source here and it works fine. On 21-Jul-2001 Juergen Hasch wrote: > Am Freitag, 20. Juli 2001 10:26 schrieb Nathan Scott: >> Important change for xfsdump and xfsrestore (and libraries that they >> rely on)... we're now consistent with other backup/restore utilities >> which need be available when only the root filesystem is mounted. > > What is the reason for putting libacl.a in /lib instead of leaving it in > /usr/lib where it belongs IMHO ? > This breaks all applications that try to link libacl.a at compiletime like > Samba and Fileutils. Please move it back. > > ...Juergen -- John M. Trostel Linux OS Engineer Connex jtrostel@connex.com From owner-linux-xfs@oss.sgi.com Sat Jul 21 14:03:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LL35p05880 for linux-xfs-outgoing; Sat, 21 Jul 2001 14:03:05 -0700 Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LL33V05861 for ; Sat, 21 Jul 2001 14:03:04 -0700 Received: from fwd01.sul.t-online.de by mailout06.sul.t-online.de with smtp id 15O3ts-0006Jr-01; Sat, 21 Jul 2001 23:03:00 +0200 Received: from there (340024412816-0001@[217.81.134.163]) by fwd01.sul.t-online.com with smtp id 15O3tg-1LjfN2C; Sat, 21 Jul 2001 23:02:48 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: John Trostel , (Juergen Hasch) Subject: Re: TAKE - userspace Date: Sat, 21 Jul 2001 23:03:06 +0200 X-Mailer: KMail [version 1.2.9] Cc: linux-xfs@oss.sgi.com, Nathan Scott References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <15O3tg-1LjfN2C@fwd01.sul.t-online.com> X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello John, Am Samstag, 21. Juli 2001 22:52 schrieb John Trostel: > It will NOT break Samba. The Samba check just looks to see if acl_get_file > (or whatever) is available after a -lacl compile call. If your system > looks for libraries in both /usr/lib and /lib, it will not break with the > move. It breaks for me (SuSE system). Now I don't claim to be an LSB expert, but IMHO static libraries belong in /usr/lib and shared libraries can be in /lib (important ones) or sometimes in /usr/lib. ...Juergen From owner-linux-xfs@oss.sgi.com Sat Jul 21 14:20:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LLKBJ07000 for linux-xfs-outgoing; Sat, 21 Jul 2001 14:20:11 -0700 Received: from mailout06.sul.t-online.de (mailout06.sul.t-online.com [194.25.134.19]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LLK8V06981 for ; Sat, 21 Jul 2001 14:20:08 -0700 Received: from fwd01.sul.t-online.de by mailout06.sul.t-online.de with smtp id 15O4AO-0008Vj-01; Sat, 21 Jul 2001 23:20:04 +0200 Received: from there (340024412816-0001@[217.81.134.163]) by fwd01.sul.t-online.com with smtp id 15O4AF-0MsuMSC; Sat, 21 Jul 2001 23:19:55 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Hasch@t-online.de (Juergen Hasch), John Trostel , (Juergen Hasch) Subject: Re: TAKE - userspace Date: Sat, 21 Jul 2001 23:20:10 +0200 X-Mailer: KMail [version 1.2.9] Cc: linux-xfs@oss.sgi.com, Nathan Scott References: <15O3tg-1LjfN2C@fwd01.sul.t-online.com> In-Reply-To: <15O3tg-1LjfN2C@fwd01.sul.t-online.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <15O4AF-0MsuMSC@fwd01.sul.t-online.com> X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Samstag, 21. Juli 2001 23:03 schrieb Juergen Hasch: > Hello John, > > Am Samstag, 21. Juli 2001 22:52 schrieb John Trostel: > > It will NOT break Samba. The Samba check just looks to see if > > acl_get_file (or whatever) is available after a -lacl compile call. If > > your system looks for libraries in both /usr/lib and /lib, it will not > > break with the move. > > It breaks for me (SuSE system). > Now I don't claim to be an LSB expert, but IMHO static libraries belong in > /usr/lib and shared libraries can be in /lib (important ones) or sometimes > in /usr/lib. I don't want to be pedantic, but I have taken a look at the Filesystem Hierarchy Standard (FHS not LSB as I wrote): /lib : Essential shared libraries and kernel modules /usr/lib: Libraries for programming and packages I think storing a static libray in /lib and adding a symlink from /lib to /usr/lib is plain wrong. Let's keep the filesystem clean, or the distributions will do it for us when they include XFS :-) And now I go back to my glass of wine... ...Juergen From owner-linux-xfs@oss.sgi.com Sat Jul 21 14:23:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LLNC707289 for linux-xfs-outgoing; Sat, 21 Jul 2001 14:23:12 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LLNAV07269 for ; Sat, 21 Jul 2001 14:23:10 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA20028; Sat, 21 Jul 2001 23:23:06 +0200 (CEST) Message-Id: <4.3.2.7.2.20010721231237.03308ec0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 21 Jul 2001 23:22:52 +0200 To: Hasch@t-online.de (Juergen Hasch), John Trostel , (Juergen Hasch) From: Seth Mos Subject: Re: TAKE - userspace Cc: linux-xfs@oss.sgi.com, Nathan Scott In-Reply-To: <15O3tg-1LjfN2C@fwd01.sul.t-online.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 23:03 21-7-2001 +0200, Juergen Hasch wrote: >Hello John, > >Am Samstag, 21. Juli 2001 22:52 schrieb John Trostel: > > It will NOT break Samba. The Samba check just looks to see if acl_get_file > > (or whatever) is available after a -lacl compile call. If your system > > looks for libraries in both /usr/lib and /lib, it will not break with the > > move. >It breaks for me (SuSE system). >Now I don't claim to be an LSB expert, but IMHO static libraries belong in >/usr/lib and shared libraries can be in /lib (important ones) or sometimes >in /usr/lib. Ok, so we need some way of splitting this up. Build a patch if you want and submit it. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sat Jul 21 14:25:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LLPZd07536 for linux-xfs-outgoing; Sat, 21 Jul 2001 14:25:35 -0700 Received: from FW2.dt.navy.mil (FW2.dt.navy.mil [192.5.27.136]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LLPXV07517 for ; Sat, 21 Jul 2001 14:25:33 -0700 Received: by FW2.dt.navy.mil; id RAA11962; Sat, 21 Jul 2001 17:27:59 -0400 (EDT) Received: from unknown(130.46.225.16) by FW2.dt.navy.mil via smap (V5.5) id xma011952; Sat, 21 Jul 01 17:27:33 -0400 Received: from NAVGATE.dt.navy.mil (navgate.dt.navy.mil [130.46.225.15]) by smtprelay.dt.navy.mil (8.9.3/8.9.3) with SMTP id RAA20863 for ; Sat, 21 Jul 2001 17:25:02 -0400 Received: from crbeex01.nswccd.navy.mil ([130.46.5.84]) by NAVGATE.dt.navy.mil (NAVIEG 2.1 bld 63) with SMTP id M2001072117250021675 ; Sat, 21 Jul 2001 17:25:00 -0400 Received: from PROFESSOR.dt.navy.mil ([157.187.160.235]) by crbeex01.nswccd.navy.mil with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PAXH3HNJ; Sat, 21 Jul 2001 17:24:59 -0400 Received: from jtsdell (Bayview162-40.dt.navy.mil [157.187.162.40]) by professor.dt.navy.mil (8.8.8+Sun/8.8.8) with ESMTP id OAA16122; Sat, 21 Jul 2001 14:14:49 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.5.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15O3gO-0CJtrcC@fwd01.sul.t-online.com> Date: Sat, 21 Jul 2001 17:24:31 -0400 (EDT) Reply-To: John Trostel Organization: Connex From: John Trostel To: (Juergen Hasch) Subject: Re: TAKE - userspace Cc: linux-xfs@oss.sgi.com, Nathan Scott , Seth Mos Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Of course, I still haven't gotten around to making the libacl.so yet. Busy on a few other fronts right now. But... poking around on my Linux box reveals: [jt@jtsdell jt]$ cd /lib [jt@jtsdell /lib]$ ls *.a libacl.a liblvm.a libpam_misc.a libpwdb.a On a solaris box: bash-2.02$ pwd /lib bash-2.02$ ls *.a lib300.a libbsm.a libgenIO.a libnisdb.a libsocket.a lib300s.a libc.a libintl.a libnls.a libvolmgt.a lib4014.a libc2.a libkrb.a libnsl.a libvt0.a lib450.a libc2stubs.a libldfeature.a libpkg.a libw.a libTL.a libcmd.a libm.a libplot.a null.a libadm.a libcrypt.a libmail.a librac.a libauth.a libcrypt_i.a libmapmalloc.a librpcsvc.a libbsdmalloc.a libelf.a libmp.a libsec.a So the placement of *.a libs in /lib is not unheard of. On 21-Jul-2001 Juergen Hasch wrote: > Hello Seth, > > Am Samstag, 21. Juli 2001 22:36 schrieb Seth Mos: >> At 22:12 21-7-2001 +0200, Juergen Hasch wrote: >> >Am Freitag, 20. Juli 2001 10:26 schrieb Nathan Scott: >> > > Important change for xfsdump and xfsrestore (and libraries that they >> > > rely on)... we're now consistent with other backup/restore utilities >> > > which need be available when only the root filesystem is mounted. >> > >> >What is the reason for putting libacl.a in /lib instead of leaving it in >> >/usr/lib where it belongs IMHO ? >> >This breaks all applications that try to link libacl.a at compiletime like >> >Samba and Fileutils. Please move it back. >> >> NO! >> >> If you only have your root filesystem, how would you then be able to run >> xfsdump or xfsrestore. >> let's see. >> >> You have a seriuous crash of your system and the /usr filesystem is lost. >> This means that you need to restore the /usr filesystem. >> Now comes the fun part, you run xfsrestore to get your /usr filesystem back >> but onfortunately you can't run xfs_repair to repair the fs or run >> xfsrestore to restore your backup. > > libacl.a is a static library that is used only at compile time. This is > because libacl.a contains only the stubs for libacl.so. > No-one has *.a files in /lib, they are all in /usr/lib. Take a look in your > /lib directory. You find the stubs for e.g. libc as /usr/lib/libc.a, but > the actual libc.so in /lib. > So you need libacl.so in /lib and libacl.a in /usr/lib. > > ...Juergen -- John M. Trostel Linux OS Engineer Connex jtrostel@connex.com From owner-linux-xfs@oss.sgi.com Sat Jul 21 14:29:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LLTZ907807 for linux-xfs-outgoing; Sat, 21 Jul 2001 14:29:35 -0700 Received: from FW2.dt.navy.mil (FW2.dt.navy.mil [192.5.27.136]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LLTYV07780 for ; Sat, 21 Jul 2001 14:29:34 -0700 Received: by FW2.dt.navy.mil; id RAA12192; Sat, 21 Jul 2001 17:31:59 -0400 (EDT) Received: from unknown(130.46.225.16) by FW2.dt.navy.mil via smap (V5.5) id xma012135; Sat, 21 Jul 01 17:31:12 -0400 Received: from NAVGATE.dt.navy.mil (navgate.dt.navy.mil [130.46.225.15]) by smtprelay.dt.navy.mil (8.9.3/8.9.3) with SMTP id RAA20875 for ; Sat, 21 Jul 2001 17:28:41 -0400 Received: from crbeex01.nswccd.navy.mil ([130.46.5.84]) by NAVGATE.dt.navy.mil (NAVIEG 2.1 bld 63) with SMTP id M2001072117284024774 ; Sat, 21 Jul 2001 17:28:40 -0400 Received: from PROFESSOR.dt.navy.mil ([157.187.160.235]) by crbeex01.nswccd.navy.mil with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id PAXH3HNZ; Sat, 21 Jul 2001 17:28:40 -0400 Received: from jtsdell (Bayview162-40.dt.navy.mil [157.187.162.40]) by professor.dt.navy.mil (8.8.8+Sun/8.8.8) with ESMTP id OAA16127; Sat, 21 Jul 2001 14:18:49 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.5.0 on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15O3tg-1LjfN2C@fwd01.sul.t-online.com> Date: Sat, 21 Jul 2001 17:28:32 -0400 (EDT) Reply-To: John Trostel Organization: Connex From: John Trostel To: (Juergen Hasch) Subject: Re: TAKE - userspace Cc: Nathan Scott , linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Have you rerun ldconfig since moving around the libs? Did you recompile Samba after moving the libs and rerunning ldconfig? Can you send me a glass of that wine? On 21-Jul-2001 Juergen Hasch wrote: > Hello John, > > Am Samstag, 21. Juli 2001 22:52 schrieb John Trostel: >> It will NOT break Samba. The Samba check just looks to see if acl_get_file >> (or whatever) is available after a -lacl compile call. If your system >> looks for libraries in both /usr/lib and /lib, it will not break with the >> move. > It breaks for me (SuSE system). > Now I don't claim to be an LSB expert, but IMHO static libraries belong in > /usr/lib and shared libraries can be in /lib (important ones) or sometimes > in /usr/lib. > > ...Juergen -- John M. Trostel Linux OS Engineer Connex jtrostel@connex.com From owner-linux-xfs@oss.sgi.com Sat Jul 21 14:39:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6LLd6L08601 for linux-xfs-outgoing; Sat, 21 Jul 2001 14:39:06 -0700 Received: from localhost.localdomain ([63.161.143.84]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6LLd0V08578 for ; Sat, 21 Jul 2001 14:39:03 -0700 Received: (from scott@localhost) by meth (8.11.2/8.11.2) id f6LKTRv01743; Sat, 21 Jul 2001 14:29:27 -0600 X-Authentication-Warning: meth: scott set sender to scott@jaderholm.com using -f To: linux-xfs@oss.sgi.com Subject: resizing XFS From: Scott Jaderholm Date: 21 Jul 2001 14:28:26 -0600 Message-ID: Lines: 25 User-Agent: Gnus/5.090003 (Oort Gnus v0.03) Emacs/21.0.102 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I installed with the SGI RHL Linux 7.1 installer. Here's what p in fdisk says. Disk /dev/hda: 255 heads, 63 sectors, 5605 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 * 1 4 32098+ 83 Linux /dev/hda2 5 4466 35841015 f Win95 Ext'd (LBA) /dev/hda5 5 4466 35840983+ 83 Linux cfdisk shows 9360.60 MB free, after hda5. What I wanted to know is, since this hda5 is a logical partition, can I still resize it. AFAIK the SGI RHL 7.1 installer didn't install LVM so what I'm planning to do is delete hda5 w/ fdisk and then create a new one taking up the rest of the disk. Reboot, and run xfs_growfs /. Does this sound good? Thanks for any help and please CC. Sincerely, jsj -- the sky is tired of being blue From owner-linux-xfs@oss.sgi.com Sat Jul 21 18:02:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M12Aj25140 for linux-xfs-outgoing; Sat, 21 Jul 2001 18:02:10 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M128V25118 for ; Sat, 21 Jul 2001 18:02:08 -0700 Received: from vimfuego.saarinen.org ([192.168.1.1]) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15O4mh-0007mo-00; Sun, 22 Jul 2001 09:59:39 +1200 Date: Sun, 22 Jul 2001 09:59:19 +1200 (NZST) From: Juha Saarinen To: "Bernhard R. Erdmann" cc: Linux XFS Mailing List Subject: Re: 2.4.7-pre8-xfs breaks VMWare In-Reply-To: <3B5974DD.E108B2B9@berdmann.de> Message-ID: X-S: Always MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 21 Jul 2001, Bernhard R. Erdmann wrote: > pgalloc.h forgot to include asm/page.h. Are you sure that you have > /lib/modules/2.4.7-pre7/build/include/asm/page.h ? > > I do not know about any changes introduced in 2.4.7pre* which removed > #include from somewhere... So if you are sure that you > have vmware-2.0.4, Easiest thing is probably adding #include > > at the beginning of pgalloc.h ... > Petr Petr Vandrovec seems to know his stuff. ;-) I saw a message (think it was on /. of all places) in conjunction with the official 2.4.7 release, that it VMware breaks. Wait for an update from VMware, I guess. -- Regards, Juha From owner-linux-xfs@oss.sgi.com Sat Jul 21 20:42:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M3geX05848 for linux-xfs-outgoing; Sat, 21 Jul 2001 20:42:40 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M3gcV05829 for ; Sat, 21 Jul 2001 20:42:38 -0700 Received: from there (localhost.localdomain [127.0.0.1]) by wwweasel.geeksrus.net (8.11.4/8.11.4) with SMTP id f6M3fx106002; Sat, 21 Jul 2001 23:41:59 -0400 Message-Id: <200107220341.f6M3fx106002@wwweasel.geeksrus.net> Content-Type: text/plain; charset="iso-8859-1" From: Alan Eldridge To: "Juha Saarinen" Subject: Re: 2.4.7-pre8-xfs breaks VMWare Date: Sat, 21 Jul 2001 23:41:58 -0400 X-Mailer: KMail [version 1.2.9] References: <003001c11254$70ae0490$0a01a8c0@den2> In-Reply-To: <003001c11254$70ae0490$0a01a8c0@den2> Cc: XFS list MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Saturday 21 July 2001 10:17 pm, you wrote: > :: I cannot give any details due to NDA, but I am testing VMware's next > :: version, and I will make sure it works with current kernels. > :: I cannot, > :: however, discuss that work or anything related to VMware's > :: test software, > :: on this list or anywhere else. > > Oi! That doesn't sound very Open Sores to me! ;-) > > :: "FpmPpmfppmmmpffmpp mffpppmmfpmffmfmpmmppfmm fmmfmfpfmpfmppfpfffmp > :: mpfppfpff mfmmpppppmpppffmffmmf FmmMmfFmmMff, mmpmffmfm > :: fpmmffpfffmpfmfmmmpmf mpmmfffmmpmpfmm, FmfFmmMmp, mmmpppmpm > :: FppmffpppFpfPfm." > :: - kenny > > Yeah, I second that. But did you understand it? That is NOT gibberish. :) From owner-linux-xfs@oss.sgi.com Sat Jul 21 20:44:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M3iaW06152 for linux-xfs-outgoing; Sat, 21 Jul 2001 20:44:36 -0700 Received: from vimfuego.saarinen.org (saarinen.org [203.79.82.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M3iYV06129 for ; Sat, 21 Jul 2001 20:44:35 -0700 Received: from [192.168.1.10] (helo=den2) by vimfuego.saarinen.org with esmtp (Exim 3.22 #1 (Red Hack)) id 15OAAR-00089Z-00; Sun, 22 Jul 2001 15:44:31 +1200 From: "Juha Saarinen" To: "'Alan Eldridge'" Cc: "'XFS list'" Subject: RE: 2.4.7-pre8-xfs breaks VMWare Date: Sun, 22 Jul 2001 15:45:00 +1200 Message-ID: <006901c11260$aed5eba0$0a01a8c0@den2> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 In-Reply-To: <200107220341.f6M3fx106002@wwweasel.geeksrus.net> Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk :: But did you understand it? That is NOT gibberish. :) Yes, but as I don't wish to meet with Sklyarov's fate, I cannot explain how I broke the Kennycoding... ;-))) -- Juha From owner-linux-xfs@oss.sgi.com Sun Jul 22 00:00:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M702824809 for linux-xfs-outgoing; Sun, 22 Jul 2001 00:00:02 -0700 Received: from mail.unixcircle.com (adsl-63-193-121-28.dsl.snfc21.pacbell.net [63.193.121.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M6xxV24775 for ; Sat, 21 Jul 2001 23:59:59 -0700 Received: from unixcircle.com (pissboy.unixcircle.com [10.0.0.13]) by mail.unixcircle.com (8.12.0.Beta12/unixcircle) with ESMTP id f6M6xm4O002875 for ; Sat, 21 Jul 2001 23:59:48 -0700 (PDT) Message-ID: <3B5A799E.894F1AE4@unixcircle.com> Date: Sat, 21 Jul 2001 23:58:38 -0700 From: rollingblackout Organization: a fool with a tool is still a fool -- fool@unixcircle.org -- IRC unixcircle.org:6667 X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-UNIXCIRCLE i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: permission? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Folks, A fresh install from SGI XFS 1.0.1 gives: [root@cafe /etc]# ls -lart|grep "\-rw-rw-rw-" -rw-rw-rw- 1 root root 66 Jul 20 09:05 shells -rw-rw-rw- 1 root root 85 Jul 20 09:10 modules.conf -rw-rw-rw- 1 root root 94 Jul 20 23:53 resolv.conf -rw-rw-rw- 1 root root 194 Jul 21 12:37 hosts Are these considered "normal"? Any other place where world writable? Thanks, From owner-linux-xfs@oss.sgi.com Sun Jul 22 00:19:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M7JN626662 for linux-xfs-outgoing; Sun, 22 Jul 2001 00:19:23 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M7IRV26545 for ; Sun, 22 Jul 2001 00:18:34 -0700 Received: (qmail 4909 invoked from network); 22 Jul 2001 07:17:11 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 22 Jul 2001 07:17:11 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: rollingblackout cc: linux-xfs@oss.sgi.com Subject: Re: permission? In-reply-to: Your message of "Sat, 21 Jul 2001 23:58:38 MST." <3B5A799E.894F1AE4@unixcircle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 22 Jul 2001 17:17:09 +1000 Message-ID: <3572.995786229@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 21 Jul 2001 23:58:38 -0700, rollingblackout wrote: >A fresh install from SGI XFS 1.0.1 gives: > >[root@cafe /etc]# ls -lart|grep "\-rw-rw-rw-" >-rw-rw-rw- 1 root root 66 Jul 20 09:05 shells >-rw-rw-rw- 1 root root 85 Jul 20 09:10 modules.conf >-rw-rw-rw- 1 root root 94 Jul 20 23:53 resolv.conf >-rw-rw-rw- 1 root root 194 Jul 21 12:37 hosts > >Are these considered "normal"? Any other place where world writable? Which kernel? There was a kernel bug from 2.4.3-pre5 until 2.4.7-pre7 where the initscripts ran with umask 000 instead of 022, that would give the effect above. It is fixed in the XFS CVS tree because that is at 2.4.7, but the old releases might be bitten by this kernel bug. From owner-linux-xfs@oss.sgi.com Sun Jul 22 00:26:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M7QnM27302 for linux-xfs-outgoing; Sun, 22 Jul 2001 00:26:49 -0700 Received: from mail.unixcircle.com (adsl-63-193-121-28.dsl.snfc21.pacbell.net [63.193.121.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M7QlV27280 for ; Sun, 22 Jul 2001 00:26:47 -0700 Received: from unixcircle.com (pissboy.unixcircle.com [10.0.0.13]) by mail.unixcircle.com (8.12.0.Beta12/unixcircle) with ESMTP id f6M7Qk4O002899 for ; Sun, 22 Jul 2001 00:26:46 -0700 (PDT) Message-ID: <3B5A7FF0.C57DC825@unixcircle.com> Date: Sun, 22 Jul 2001 00:25:36 -0700 From: rollingblackout Organization: a fool with a tool is still a fool -- fool@unixcircle.org -- IRC unixcircle.org:6667 X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-UNIXCIRCLE i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: permission? References: <3572.995786229@ocs3.ocs-net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Keith Owens wrote: > > On Sat, 21 Jul 2001 23:58:38 -0700, > rollingblackout wrote: > >A fresh install from SGI XFS 1.0.1 gives: > > > >[root@cafe /etc]# ls -lart|grep "\-rw-rw-rw-" > >-rw-rw-rw- 1 root root 66 Jul 20 09:05 shells > >-rw-rw-rw- 1 root root 85 Jul 20 09:10 modules.conf > >-rw-rw-rw- 1 root root 94 Jul 20 23:53 resolv.conf > >-rw-rw-rw- 1 root root 194 Jul 21 12:37 hosts > > > >Are these considered "normal"? Any other place where world writable? > > Which kernel? There was a kernel bug from 2.4.3-pre5 until 2.4.7-pre7 > where the initscripts ran with umask 000 instead of 022, that would > give the effect above. It is fixed in the XFS CVS tree because that is > at 2.4.7, but the old releases might be bitten by this kernel bug. 2.4.3-SGI_XFS_1.0.1 btw, thanks for the great XFS works. back to lurking mode... From owner-linux-xfs@oss.sgi.com Sun Jul 22 01:12:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M8C8d30694 for linux-xfs-outgoing; Sun, 22 Jul 2001 01:12:08 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M8C6V30673 for ; Sun, 22 Jul 2001 01:12:06 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id BAA12247 for ; Sun, 22 Jul 2001 01:11:52 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 SAA22128; Sun, 22 Jul 2001 18:10:46 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA17291; Sun, 22 Jul 2001 18:10:44 +1000 (AEST) Date: Sun, 22 Jul 2001 18:10:44 +1000 From: Nathan Scott To: Juergen Hasch Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - userspace Message-ID: <20010722181043.A224198@wobbly.melbourne.sgi.com> References: <200107200826.SAA36970@snort.melbourne.sgi.com> <15O37C-1kawUrC@fwd01.sul.t-online.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <15O37C-1kawUrC@fwd01.sul.t-online.com>; from Hasch@t-online.de on Sat, Jul 21, 2001 at 10:12:59PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Sat, Jul 21, 2001 at 10:12:59PM +0200, Juergen Hasch wrote: > Am Freitag, 20. Juli 2001 10:26 schrieb Nathan Scott: > > Important change for xfsdump and xfsrestore (and libraries that they > > rely on)... we're now consistent with other backup/restore utilities > > which need be available when only the root filesystem is mounted. > > What is the reason for putting libacl.a in /lib instead of leaving it in > /usr/lib where it belongs IMHO ? The fundamental reason is "that's where libtool wants to put it" - my first thoughts were that this is a strange thing also, but I can't seem to find a way to get libtool to install the shared lib to /lib and the static lib to /usr/lib - it seems they both have to be in the same place. > This breaks all applications that try to link libacl.a at compiletime like > Samba and Fileutils. Please move it back. Can you elaborate on that? (how do they break?) They should not. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 22 01:16:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M8Gt231163 for linux-xfs-outgoing; Sun, 22 Jul 2001 01:16:55 -0700 Received: from ente.berdmann.de (p3E9E7351.dip.t-dialin.net [62.158.115.81]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M8GqV31141 for ; Sun, 22 Jul 2001 01:16:52 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15OEPt-0007v4-00 for linux-xfs@oss.sgi.com; Sun, 22 Jul 2001 10:16:45 +0200 Message-ID: <3B5A8BED.C9B8D5D@berdmann.de> Date: Sun, 22 Jul 2001 10:16:45 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Linux XFS Mailing List Subject: Re: 2.4.7-pre8-xfs breaks VMWare References: <3B5743C9.49891146@berdmann.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Path: news.t-online.com!newsmm00.sul.t-online.com!newsfeed01.sul.t-online.de!t-online.de!newsfeed.online.be!news-hog.berkeley.edu!ucberkeley!nntp-relay.ihug.net!newsfeeds.ihug.co.nz!ihug.co.nz!news.vmware.com!not-for-mail Message-ID: <9jc1nm$oe$1@london.vmware.com> From: Carl Livitt Newsgroups: vmware.for-linux.configuration Subject: Re: vmware 2.0.4 broken with linux 2.4.7 Date: Sat, 21 Jul 2001 14:56:02 +0100 References: <9jbl2k$pq1$1@london.vmware.com> Lines: 39 Organization: Organised? Me? NNTP-Posting-Host: host213-122-181-34.btinternet.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.4 Xref: ente.berdmann.de vmware.for-linux.configuration:509 Bryan wrote: > just upgraded to latest 2.4 series (2.4.7) and this is the first time > I've seen vmware-config.pl fail: > Same here. The Google groups has a link to a patch which addresses this issue. I've just installed it and whilst it gives compilation warnings, the modules build and install OK. I'm now happily running VMWare 2.0.4 under Linux 2.4.7. So, to make this work first download the patch: ftp://platan.vc.cvut.cz/pub/vmware/vmmon-for-2.4.7-only.tar.gz Then copy it to the '/usr/local/lib/vmware/modules/source' directory. Next, run: cd /usr/local/lib/vmware/modules/source gunzip vmmon-for-2.4.7-only.tar.gz After that, make a backup of the existing 'vmmon.tar' file and copy the new one into its place: cp vmmon.tar vmmon.tar.backup mv vmmon-for-2.4.7-only.tar vmmon.tar Finally, run: vmware-config.pl to set things up. That should give you a working VMWare installation again. Regards, Carl. -- Free Dmitri! http://www.boycottadobe.com Path: news.t-online.com!newsmm00.sul.t-online.com!newsfeed00.sul.t-online.de!t-online.de!nntp-relay.ihug.net!newsfeeds.ihug.co.nz!ihug.co.nz!news.vmware.com!not-for-mail Message-ID: <9jc37m$148$3@london.vmware.com> From: Carl Livitt Newsgroups: vmware.for-linux.configuration Subject: Re: vmware 2.0.4 broken with linux 2.4.7 Date: Sat, 21 Jul 2001 15:22:19 +0100 References: <9jbl2k$pq1$1@london.vmware.com> <9jc1nm$oe$1@london.vmware.com> Lines: 22 Organization: Organised? Me? NNTP-Posting-Host: host213-122-181-34.btinternet.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit User-Agent: KNode/0.4 Xref: ente.berdmann.de vmware.for-linux.configuration:510 Carl Livitt wrote: In my previous post, part of the fix consisted of: > cp vmmon.tar vmmon.tar.backup > mv vmmon-for-2.4.7-only.tar vmmon.tar Which is incorrect. It _should_ read: > mv vmmon.tar vmmon.tar.backup > mv vmmon-for-2.4.7-only.tar vmmon.tar Sorry for any confusion. In fact, I typoed an earlier correction to this (ctrl-enter instead of enter) and sent an incomplete message to the list. I cancelled it, but it still seems to be present so please ignore it.... I must need more caffeine! Carl. -- Free Dmitri! http://www.boycottadobe.com From owner-linux-xfs@oss.sgi.com Sun Jul 22 01:46:53 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M8krV01305 for linux-xfs-outgoing; Sun, 22 Jul 2001 01:46:53 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M8koV01283 for ; Sun, 22 Jul 2001 01:46:51 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id BAA01509 for ; Sun, 22 Jul 2001 01:44:26 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 SAA22231; Sun, 22 Jul 2001 18:45:33 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA29975; Sun, 22 Jul 2001 18:45:32 +1000 (AEST) Date: Sun, 22 Jul 2001 18:45:31 +1000 From: Nathan Scott To: Juergen Hasch Cc: Seth Mos , linux-xfs@oss.sgi.com Subject: Re: TAKE - userspace Message-ID: <20010722184531.B224198@wobbly.melbourne.sgi.com> References: <200107200826.SAA36970@snort.melbourne.sgi.com> <4.3.2.7.2.20010721222837.031d7178@pop.xs4all.nl> <15O3gO-0CJtrcC@fwd01.sul.t-online.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <15O3gO-0CJtrcC@fwd01.sul.t-online.com>; from Hasch@t-online.de on Sat, Jul 21, 2001 at 10:49:23PM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Sat, Jul 21, 2001 at 10:49:23PM +0200, Juergen Hasch wrote: > > libacl.a is a static library that is used only at compile time. This is > because libacl.a contains only the stubs for libacl.so. No, this is not correct. libacl.a provides everything that libacl.so does, in terms of ACL code. A program can link against either the shared or the static version of the library - it is not necessary to have the other present at all at build time. Previously we _only_ provided a static library for libacl (and libattr, and libdm, and...) but we now provide both. We now use the GNU libtool package to help with building these libraries, which we also did not do before. > No-one has *.a files in /lib, they are all in /usr/lib. Take a look in your > /lib directory. You find the stubs for e.g. libc as /usr/lib/libc.a, but > the actual libc.so in /lib. That may be how libc works (I don't know, the stubs thing sounds like a very strange thing to do), but that isn't how most static libraries work and is not how libacl.a works. > So you need libacl.so in /lib and libacl.a in /usr/lib. > This assertion is not correct - you may be misunderstanding some of the mechanics of libraries - the libtool documentation, ld(1), and ar(1) man pages might help. Having said all that, I do agree that the static libraries should go into /usr/lib - its just a matter of coercing libtool to put them there or changing our own install process - I'll have a look into it sometime this week. Thanks for the input. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 22 01:58:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M8wqT02424 for linux-xfs-outgoing; Sun, 22 Jul 2001 01:58:52 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M8wnV02399 for ; Sun, 22 Jul 2001 01:58:50 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.4) id f6M8vlZ23421 for linux-xfs@oss.sgi.com; Sun, 22 Jul 2001 04:57:47 -0400 Date: Sun, 22 Jul 2001 04:57:47 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: libtoolizing Message-ID: <20010722045746.A14821@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Who did the libtool work? Raise your hand please. Ah, yes, you in the back. Could you tell me what docs (hahahaha) you used to help you in this endeavor? I have a package I'm helping out the developers with (esoap) that needs automake-, autoconf-, and libtool-izing and I could use any and all suggestions. -- Alan Eldridge Down, not across From owner-linux-xfs@oss.sgi.com Sun Jul 22 02:40:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M9evX06111 for linux-xfs-outgoing; Sun, 22 Jul 2001 02:40:57 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M9etV06092 for ; Sun, 22 Jul 2001 02:40:55 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.4) id f6M9elW26833; Sun, 22 Jul 2001 05:40:47 -0400 Date: Sun, 22 Jul 2001 05:40:46 -0400 From: Alan Eldridge To: "Bernhard R. Erdmann" Cc: SGI XFS Dev List Subject: Re: 2.4.7-pre8-xfs breaks VMWare Message-ID: <20010722054046.A17705@wwweasel.geeksrus.net> References: <3B5743C9.49891146@berdmann.de> <3B5A8BED.C9B8D5D@berdmann.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B5A8BED.C9B8D5D@berdmann.de>; from be@berdmann.de on Sun, Jul 22, 2001 at 10:16:45AM +0200 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 22, 2001 at 10:16:45AM +0200, Bernhard R. Erdmann wrote: > >Same here. The Google groups has a link to a patch which addresses this >issue. I've just installed it and whilst it gives compilation warnings, >the >modules build and install OK. > >I'm now happily running VMWare 2.0.4 under Linux 2.4.7. So, to make this >work first download the patch: > > ftp://platan.vc.cvut.cz/pub/vmware/vmmon-for-2.4.7-only.tar.gz > Ok, this must have happened around 2.4.7pre6 or so. The earlier one that I'm running (2.4.6pre3 from cvs.20010708) is fine. Seems as though a structure changed. I've looked at the patch and it looks innocuous enogh. I'll make sure that the right patches continually get to VMware so that when 3.0 comes out, the drivers will likely build without being patched. Just keep adding to the pile of macros. And then, when we have a big enough pile .... -- Alan Eldridge "My brain hurts." -- D. P. Gumby From owner-linux-xfs@oss.sgi.com Sun Jul 22 02:57:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6M9vAe07196 for linux-xfs-outgoing; Sun, 22 Jul 2001 02:57:10 -0700 Received: from mailout05.sul.t-online.de (mailout05.sul.t-online.com [194.25.134.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6M9v8V07176 for ; Sun, 22 Jul 2001 02:57:08 -0700 Received: from fwd06.sul.t-online.de by mailout05.sul.t-online.de with smtp id 15OFyy-0003xx-05; Sun, 22 Jul 2001 11:57:04 +0200 Received: from there (340024412816-0001@[217.81.130.104]) by fwd06.sul.t-online.com with smtp id 15OFyw-18xRT6C; Sun, 22 Jul 2001 11:57:02 +0200 Content-Type: text/plain; charset="iso-8859-1" From: Hasch@t-online.de (Juergen Hasch) To: Nathan Scott , Juergen Hasch Subject: Re: TAKE - userspace Date: Sun, 22 Jul 2001 11:57:23 +0200 X-Mailer: KMail [version 1.2.9] Cc: Seth Mos , linux-xfs@oss.sgi.com References: <200107200826.SAA36970@snort.melbourne.sgi.com> <15O3gO-0CJtrcC@fwd01.sul.t-online.com> <20010722184531.B224198@wobbly.melbourne.sgi.com> In-Reply-To: <20010722184531.B224198@wobbly.melbourne.sgi.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: <15OFyw-18xRT6C@fwd06.sul.t-online.com> X-Sender: 340024412816-0001@t-dialin.net Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Am Sonntag, 22. Juli 2001 10:45 schrieb Nathan Scott: > hi, > > On Sat, Jul 21, 2001 at 10:49:23PM +0200, Juergen Hasch wrote: > > libacl.a is a static library that is used only at compile time. This is > > because libacl.a contains only the stubs for libacl.so. > > No, this is not correct. libacl.a provides everything that libacl.so > does, in terms of ACL code. A program can link against either the > shared or the static version of the library - it is not necessary to > have the other present at all at build time. Previously we _only_ > provided a static library for libacl (and libattr, and libdm, and...) > but we now provide both. We now use the GNU libtool package to help > with building these libraries, which we also did not do before. You are right. It used to be this way in some other system I used and I never cared to check if Linux works the same way. > Having said all that, I do agree that the static libraries should > go into /usr/lib - its just a matter of coercing libtool to put them > there or changing our own install process - I'll have a look into it > sometime this week. This is all I wanted to say before I got mislead in the technical details... Don't drink and email ;-) The patch below does work for me, it may be better to add symlinks of the libacl.so files to /usr/lib, too. ...Juergen --- builddefs.in.orig Fri Jul 20 16:51:24 2001 +++ builddefs.in Sun Jul 22 10:44:11 2001 @@ -136,9 +136,9 @@ ifeq ($(ENABLE_SHARED),yes) INSTALL_LTLIB_DEV = \ cd $(TOPDIR)/$(LIBNAME)/.libs; \ - ../$(INSTALL) -m 755 -d $(PKG_SLIB_DIR); \ - ../$(INSTALL) -m 644 -T old_lib $(LIBNAME).lai $(PKG_SLIB_DIR); \ - ../$(INSTALL) -m 644 $(LIBNAME).lai $(PKG_SLIB_DIR)/$(LIBNAME).la ; \ + ../$(INSTALL) -m 755 -d $(PKG_LIB_DIR); \ + ../$(INSTALL) -m 644 -T old_lib $(LIBNAME).lai $(PKG_LIB_DIR); \ + ../$(INSTALL) -m 644 $(LIBNAME).lai $(PKG_LIB_DIR)/$(LIBNAME).la ; \ ../$(INSTALL) -T so_base $(LIBNAME).lai $(PKG_SLIB_DIR) else INSTALL_LTLIB_DEV = $(INSTALL_LTLIB_STATIC) @@ -146,8 +146,8 @@ INSTALL_LTLIB_STATIC = \ cd $(TOPDIR)/$(LIBNAME)/.libs; \ - ../$(INSTALL) -m 755 -d $(PKG_SLIB_DIR); \ - ../$(INSTALL) -m 644 -T old_lib $(LIBNAME).lai $(PKG_SLIB_DIR) + ../$(INSTALL) -m 755 -d $(PKG_LIB_DIR); \ + ../$(INSTALL) -m 644 -T old_lib $(LIBNAME).lai $(PKG_LIB_DIR) INSTALL_MAN = \ @for d in $(MAN_PAGES); do \ From owner-linux-xfs@oss.sgi.com Sun Jul 22 03:31:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MAVjf10190 for linux-xfs-outgoing; Sun, 22 Jul 2001 03:31:45 -0700 Received: from ente.berdmann.de (p3E9E7351.dip.t-dialin.net [62.158.115.81]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MAVgV10168 for ; Sun, 22 Jul 2001 03:31:43 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15OGWK-0008SI-00; Sun, 22 Jul 2001 12:31:32 +0200 Message-ID: <3B5AAB84.B29CA123@berdmann.de> Date: Sun, 22 Jul 2001 12:31:32 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Alan Eldridge CC: SGI XFS Dev List Subject: Re: 2.4.7-pre8-xfs breaks VMWare References: <3B5743C9.49891146@berdmann.de> <3B5A8BED.C9B8D5D@berdmann.de> <20010722054046.A17705@wwweasel.geeksrus.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >I'm now happily running VMWare 2.0.4 under Linux 2.4.7. So, to make this > >work first download the patch: > > > > ftp://platan.vc.cvut.cz/pub/vmware/vmmon-for-2.4.7-only.tar.gz > > > > Ok, this must have happened around 2.4.7pre6 or so. The earlier one that I'm > running (2.4.6pre3 from cvs.20010708) is fine. Seems as though a structure > changed. 2.4.7-pre6-xfs was ok. I skipped pre7 and VMWare broke with pre8. From owner-linux-xfs@oss.sgi.com Sun Jul 22 03:35:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MAZi410759 for linux-xfs-outgoing; Sun, 22 Jul 2001 03:35:44 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MAZgV10717 for ; Sun, 22 Jul 2001 03:35:42 -0700 Received: (qmail 5623 invoked by uid 8); 22 Jul 2001 10:35:40 -0000 From: Juri Haberland Reply-To: Juri Haberland X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: libtoolizing Date: Sun, 22 Jul 2001 10:35:40 +0000 (UTC) Organization: spoiled dot org Lines: 19 Distribution: local Message-ID: References: <20010722045746.A14821@wwweasel.geeksrus.net> X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (OpenBSD/2.9 (i386)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Alan Eldridge wrote: > Who did the libtool work? > > Raise your hand please. > > Ah, yes, you in the back. Could you tell me what docs (hahahaha) you used to > help you in this endeavor? I have a package I'm helping out the developers > with (esoap) that needs automake-, autoconf-, and libtool-izing and I could > use any and all suggestions. Have a look at http://sources.redhat.com/projects.html especially http://sources.redhat.com/autobook/ Have fun, Juri -- Juri Haberland From owner-linux-xfs@oss.sgi.com Sun Jul 22 03:41:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MAfpD11443 for linux-xfs-outgoing; Sun, 22 Jul 2001 03:41:51 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MAfkV11417 for ; Sun, 22 Jul 2001 03:41:47 -0700 Received: from localhost (localhost [127.0.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 3EE1BC0837B for ; Sun, 22 Jul 2001 18:41:38 +0800 (PHT) Received: from 192.168.0.90 ( [192.168.0.90]) as user jijo@localhost by horde.leathercollection.local with HTTP; Sun, 22 Jul 2001 18:41:38 +0800 Message-ID: <995798498.3b5aade2132db@horde.leathercollection.local> Date: Sun, 22 Jul 2001 18:41:38 +0800 From: Federico Sevilla III To: linux-xfs@oss.sgi.com Subject: Performance of near-full filesystems MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs X-Originating-IP: 192.168.0.90 X-Organization: The Leather Collection, Inc. X-URL: http X-Admin-Contact: root@leather-collection.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I'm wondering if XFS has certain issues when dealing with a filesystem whose usage is nearing its capacity. I ask because I have a partition that's using XFS (of course) with a 32768b internal log and is mounted with "rw,noatime,nodiratime,logbufs=8,biosize=16,osyncisdsync". Its size is 53.74GB total, and is currently at 80% usage (43.20GB used, 10.54GB free). Total inodes used and free are not a problem in this case, though (only 1% used). I will still need to use more space on the hard drive in the near future, before I can delete some stuff and free up space. I remember with ReiserFS before (I have absolutely no idea if this still exists today) that there was a FAQ entry about a filesystem slowing down when it reached something like 85% usage. I hope this isn't an issue with XFS, but thought I'd ask anyway. Also, I remember with XFS before (in the mailing list) that there was an issue about inode allocation where if you delete a large file and then start filling up the disk with a lot of smaller files you'll be wasting space. Or maybe vise versa also. What's the current status of this? :) Thanks a lot for the great filesystem guys! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 22 06:04:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MD4XC24549 for linux-xfs-outgoing; Sun, 22 Jul 2001 06:04:33 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MD4UV24521 for ; Sun, 22 Jul 2001 06:04:31 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6MD7v930288 for ; Sun, 22 Jul 2001 06:07:57 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2498068; Sun, 22 Jul 2001 08:03:09 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA25190; Sun, 22 Jul 2001 08:03:09 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6MD3Ve09050; Sun, 22 Jul 2001 08:03:31 -0500 Message-Id: <200107221303.f6MD3Ve09050@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Federico Sevilla III cc: linux-xfs@oss.sgi.com Subject: Re: Performance of near-full filesystems In-Reply-To: Message from Federico Sevilla III of "Sun, 22 Jul 2001 18:41:38 +0800." <995798498.3b5aade2132db@horde.leathercollection.local> Date: Sun, 22 Jul 2001 08:03:31 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi everyone, > > I'm wondering if XFS has certain issues when dealing with a filesystem whose > usage is nearing its capacity. I ask because I have a partition that's using > XFS (of course) with a 32768b internal log and is mounted > with "rw,noatime,nodiratime,logbufs=8,biosize=16,osyncisdsync". Its size is > 53.74GB total, and is currently at 80% usage (43.20GB used, 10.54GB free). > Total inodes used and free are not a problem in this case, though (only 1% > used). I will still need to use more space on the hard drive in the near > future, before I can delete some stuff and free up space. > > I remember with ReiserFS before (I have absolutely no idea if this still exis > ts > today) that there was a FAQ entry about a filesystem slowing down when it > reached something like 85% usage. I hope this isn't an issue with XFS, but > thought I'd ask anyway. > > Also, I remember with XFS before (in the mailing list) that there was an issu > e > about inode allocation where if you delete a large file and then start fillin > g > up the disk with a lot of smaller files you'll be wasting space. Or maybe vis > e > versa also. What's the current status of this? :) > > Thanks a lot for the great filesystem guys! :) If you create a large number of files in XFS, inodes are allocated dynamically for them. If you remove all the files, the inodes are not returned to free space. On something like ext2 inodes are allocated at mkfs time and the space is never available for anything else. This I think is what you were referring to. XFS will slow down doing allocations when it is really full, you are no where near full, 99.x% full is nearly full. Basically XFS chops the filesystem into allocation groups (1 to 4 Gbytes each), free space is managed independently in each of these. The slowdown happens when you have to scan through lots of allocation groups looking for space to extend a file. There is an in memory summary structure which tells you if it is worth even looking in an allocation group, so it is not a major slowdown - unless you have lots of parallel allocation calls going on at the time. Steve > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 22 06:23:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MDN8u25616 for linux-xfs-outgoing; Sun, 22 Jul 2001 06:23:08 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MDN6V25597 for ; Sun, 22 Jul 2001 06:23:06 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6MDRbF26354 for ; Sun, 22 Jul 2001 06:27:37 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2430739; Sun, 22 Jul 2001 08:21:45 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA57360; Sun, 22 Jul 2001 08:21:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6MDM7P09095; Sun, 22 Jul 2001 08:22:07 -0500 Message-Id: <200107221322.f6MDM7P09095@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Scott Jaderholm cc: linux-xfs@oss.sgi.com Subject: Re: resizing XFS In-Reply-To: Message from Scott Jaderholm of "21 Jul 2001 14:28:26 MDT." Date: Sun, 22 Jul 2001 08:22:07 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi, > > I installed with the SGI RHL Linux 7.1 installer. Here's what p in > fdisk says. > > Disk /dev/hda: 255 heads, 63 sectors, 5605 cylinders > Units = cylinders of 16065 * 512 bytes > > Device Boot Start End Blocks Id System > /dev/hda1 * 1 4 32098+ 83 Linux > /dev/hda2 5 4466 35841015 f Win95 Ext'd (LBA) > /dev/hda5 5 4466 35840983+ 83 Linux > > cfdisk shows 9360.60 MB free, after hda5. > > What I wanted to know is, since this hda5 is a logical partition, can > I still resize it. AFAIK the SGI RHL 7.1 installer didn't install LVM > so what I'm planning to do is delete hda5 w/ fdisk and then create a > new one taking up the rest of the disk. Reboot, and run xfs_growfs /. > Does this sound good? Thanks for any help and please CC. Provided the new partition starts at exactly the same block and contains all the original partition this should work. Looks like you will need to extend partition 2 to be bigger and then recreate 5 within it. This is probably the only way you can get the exact alignment. Steve > > Sincerely, > jsj > -- > the sky is tired of being blue From owner-linux-xfs@oss.sgi.com Sun Jul 22 08:19:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MFJRm31646 for linux-xfs-outgoing; Sun, 22 Jul 2001 08:19:27 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MFJLV31620 for ; Sun, 22 Jul 2001 08:19:22 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 1CB7CC0008B for ; Sun, 22 Jul 2001 23:19:12 +0800 (PHT) Date: Sun, 22 Jul 2001 23:19:12 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: Performance of near-full filesystems In-Reply-To: <200107221303.f6MD3Ve09050@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 22 Jul 2001 at 08:03, Steve Lord wrote: > If you create a large number of files in XFS, inodes are allocated > dynamically for them. If you remove all the files, the inodes are not > returned to free space. On something like ext2 inodes are allocated at > mkfs time and the space is never available for anything else. This I > think is what you were referring to. Yes, this is what I was referring to. I was under the impression that this was "bad", though, and one effectively "lost space". Are inodes allocated dynamically for large files different from those allocated dynamically for a bunch of small files? Meaning, if inodes are allocated for a large file, then the large file is deleted, and the inodes are not returned to free space, will filling up these allocated inodes with small files be "bad" or would filling up the free space with small files (thus creating inodes for them) have had the same effect anyway? > XFS will slow down doing allocations when it is really full, you are > no where near full, 99.x% full is nearly full. Basically XFS chops the > filesystem into allocation groups (1 to 4 Gbytes each), free space is > managed independently in each of these. The slowdown happens when you > have to scan through lots of allocation groups looking for space to > extend a file. There is an in memory summary structure which tells you > if it is worth even looking in an allocation group, so it is not a > major slowdown - unless you have lots of parallel allocation calls > going on at the time. This is great! Perhaps we could have this information in the XFS FAQ under something like "when is my disk nearly full and what happens when it's nearly full"? Thanks a lot for the help! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 22 09:18:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MGIbD01443 for linux-xfs-outgoing; Sun, 22 Jul 2001 09:18:37 -0700 Received: from gusi.leathercollection.ph (postfix@[202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MGIYV01424 for ; Sun, 22 Jul 2001 09:18:34 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 4DA2BC0FF80 for ; Mon, 23 Jul 2001 00:18:32 +0800 (PHT) Date: Mon, 23 Jul 2001 00:18:32 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Finding out the mount options used Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I have a rather trivial concern, but I thought I'd ask the list in the hopes that it will turn out to be a significant question. I recently migrated from a ReiserFS-based root filesystem to XFS (now only my Squid cache is running on ReiserFS). So this is the first time I noticed this intriguing situation. Running "mount" returns the contents of /etc/mtab, which supposedly gets populated when a filesystem is mounted. Notice the results of /dev/sda6: jijo@gusi:~$ mount /dev/sda6 on / type xfs (rw,noatime,nodiratime,logbufs=8,biosize=16,osyncisdsync,logbufs=8,biosize=16,osyncisdsync) proc on /proc type proc (rw) /dev/sda1 on /boot type ext2 (rw) /dev/sda8 on /var type xfs (rw,noatime,nodiratime,logbufs=8,biosize=16) /dev/sda11 on /home type xfs (rw,noatime,nodiratime,logbufs=8,biosize=16,osyncisdsync) /dev/sda10 on /opt/samba type xfs (rw,noatime,nodiratime,logbufs=8,biosize=16,osyncisdsync) /dev/sda9 on /var/lib/postgres type xfs (rw,noatime,nodiratime,logbufs=8,biosize=16,osyncisdsync) /dev/sda7 on /var/spool/squid type reiserfs (rw,noatime,nodiratime,notail) Wierd that the options reported are as such. I check my /etc/fstab and, like the other XFS partitions, /dev/sda6 does not have "double entries". So I compare it by viewing /proc/mounts, which I'd think should be more accurate. Here's what I get: jijo@gusi:~$ cat /proc/mounts /dev/scsi/host0/bus0/target0/lun0/part6 / xfs rw,noatime,nodiratime 0 0 none /dev devfs rw 0 0 proc /proc proc rw 0 0 /dev/sda1 /boot ext2 rw 0 0 /dev/sda8 /var xfs rw,noatime,nodiratime 0 0 /dev/sda11 /home xfs rw,noatime,nodiratime 0 0 /dev/sda10 /opt/samba xfs rw,noatime,nodiratime 0 0 /dev/sda9 /var/lib/postgres xfs rw,noatime,nodiratime 0 0 /dev/sda7 /var/spool/squid reiserfs rw,noatime,nodiratime 0 0 Now the situations is even wierder: why does /proc/mounts not know about the other filesystem-specific options? In particular for XFS it doesn't know about osyncisdsync, logbufs, and biosize. For ReiserFS it doesn't know notail. I haven't ever dug into the XFS or the Linux kernel code, so I don't know if this is really how /proc/mounts is supposed to look. Hmm ... ? --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 22 09:36:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MGa2o01705 for linux-xfs-outgoing; Sun, 22 Jul 2001 09:36:02 -0700 Received: from zok.corp.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MGa1V01685 for ; Sun, 22 Jul 2001 09:36:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6MGeWF27273 for ; Sun, 22 Jul 2001 09:40:32 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2487833; Sun, 22 Jul 2001 11:34:39 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA11542; Sun, 22 Jul 2001 11:34:39 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6MGZ0r09257; Sun, 22 Jul 2001 11:35:00 -0500 Message-Id: <200107221635.f6MGZ0r09257@jen.americas.sgi.com> To: Federico Sevilla III cc: Linux XFS Mailing List Subject: Re: Performance of near-full filesystems References: Comments: In-reply-to Federico Sevilla III message dated "Sun, 22 Jul 2001 23:19:12 +0800." Date: Sun, 22 Jul 2001 11:35:00 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Sun, 22 Jul 2001 at 08:03, Steve Lord wrote: > > If you create a large number of files in XFS, inodes are allocated > > dynamically for them. If you remove all the files, the inodes are not > > returned to free space. On something like ext2 inodes are allocated at > > mkfs time and the space is never available for anything else. This I > > think is what you were referring to. > > Yes, this is what I was referring to. I was under the impression that this > was "bad", though, and one effectively "lost space". Are inodes allocated > dynamically for large files different from those allocated dynamically for > a bunch of small files? Meaning, if inodes are allocated for a large file, > then the large file is deleted, and the inodes are not returned to free > space, will filling up these allocated inodes with small files be "bad" or > would filling up the free space with small files (thus creating inodes for > them) have had the same effect anyway? There is no distinction in XFS, an inode is an inode, no matter what it is used for, they are all the same size (default 256 bytes on disk) and they are allocated in groups of 32 by default (2 filesystem blocks worth). Steve From owner-linux-xfs@oss.sgi.com Sun Jul 22 12:02:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MJ2Mm03150 for linux-xfs-outgoing; Sun, 22 Jul 2001 12:02:22 -0700 Received: from blitz-technology.net (qmailr@203-109-247-33.ihug.net [203.109.247.33]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MJ2JV03131 for ; Sun, 22 Jul 2001 12:02:20 -0700 Received: (qmail 13538 invoked by uid 1000); 22 Jul 2001 19:04:34 -0000 From: mjs@blitz-technology.net Date: Mon, 23 Jul 2001 05:04:34 +1000 To: linux-xfs@oss.sgi.com Subject: XFS / ReiserFS / JFS Message-ID: <20010723050434.A13507@blitz-technology.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi list, Can anyone direct me to some documentation where comparisons on the 3 major journaling filesystems have been done? Am just interested to know which would be better suted to spacific situations, ie on a database server or mail server, and under what situations the different filesystems perform better. Thanks for any info you can come up with. >From Mitchell From owner-linux-xfs@oss.sgi.com Sun Jul 22 12:50:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MJoxi03724 for linux-xfs-outgoing; Sun, 22 Jul 2001 12:50:59 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MJovV03705 for ; Sun, 22 Jul 2001 12:50:57 -0700 Received: from idcomm.com (IDENT:stimits@k56-pip35.idcomm.com [209.60.72.162]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6MJtRa08314 for ; Sun, 22 Jul 2001 13:55:27 -0600 Message-ID: <3B5B2EA4.BC769676@idcomm.com> Date: Sun, 22 Jul 2001 13:51:00 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: Linux XFS Mailing List Subject: Re: Performance of near-full filesystems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Federico Sevilla III wrote: > > On Sun, 22 Jul 2001 at 08:03, Steve Lord wrote: > > If you create a large number of files in XFS, inodes are allocated > > dynamically for them. If you remove all the files, the inodes are not > > returned to free space. On something like ext2 inodes are allocated at > > mkfs time and the space is never available for anything else. This I > > think is what you were referring to. > > Yes, this is what I was referring to. I was under the impression that this > was "bad", though, and one effectively "lost space". Are inodes allocated > dynamically for large files different from those allocated dynamically for > a bunch of small files? Meaning, if inodes are allocated for a large file, > then the large file is deleted, and the inodes are not returned to free > space, will filling up these allocated inodes with small files be "bad" or > would filling up the free space with small files (thus creating inodes for > them) have had the same effect anyway? I had a minor, nagging worry, that if there is no cap on inode density, that something like a fork bomb could become a denial of service attack...allocate till much of the system is inode, and no way to get it back. It would be good to have a cap on inode density, does something like that exist now? D. Stimits, stimits@idcomm.com > > > XFS will slow down doing allocations when it is really full, you are > > no where near full, 99.x% full is nearly full. Basically XFS chops the > > filesystem into allocation groups (1 to 4 Gbytes each), free space is > > managed independently in each of these. The slowdown happens when you > > have to scan through lots of allocation groups looking for space to > > extend a file. There is an in memory summary structure which tells you > > if it is worth even looking in an allocation group, so it is not a > > major slowdown - unless you have lots of parallel allocation calls > > going on at the time. > > This is great! Perhaps we could have this information in the XFS FAQ under > something like "when is my disk nearly full and what happens when it's > nearly full"? > > Thanks a lot for the help! :) > > --> Jijo > > -- > Federico Sevilla III :: jijo@leathercollection.ph > Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 22 13:52:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MKqeC06507 for linux-xfs-outgoing; Sun, 22 Jul 2001 13:52:40 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MKqbV06488 for ; Sun, 22 Jul 2001 13:52:37 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id NAA05519 for ; Sun, 22 Jul 2001 13:52:26 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 GAA24747; Mon, 23 Jul 2001 06:51:18 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id GAA25397; Mon, 23 Jul 2001 06:51:17 +1000 (AEST) Date: Mon, 23 Jul 2001 06:51:16 +1000 From: Nathan Scott To: Alan Eldridge Cc: SGI XFS Dev List Subject: Re: libtoolizing Message-ID: <20010723065116.A230215@wobbly.melbourne.sgi.com> References: <20010722045746.A14821@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <20010722045746.A14821@wwweasel.geeksrus.net>; from alane@geeksrus.net on Sun, Jul 22, 2001 at 04:57:47AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 22, 2001 at 04:57:47AM -0400, Alan Eldridge wrote: > Who did the libtool work? > > Raise your hand please. > Dean did the first iteration, then I made some changes, then he made some chages, then I made some changes, then ... we're almost done with the fine-tuning now I think. > Ah, yes, you in the back. Could you tell me what docs (hahahaha) you used to > help you in this endeavor? I have a package I'm helping out the developers > with (esoap) that needs automake-, autoconf-, and libtool-izing and I could > use any and all suggestions. > The GNU documentation is quite good - I added a pointer to the documentation for each of the tools in our userspace toolchain to cmd/*/doc/PORTING. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 22 14:50:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MLo6k10518 for linux-xfs-outgoing; Sun, 22 Jul 2001 14:50:06 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MLo3V10496 for ; Sun, 22 Jul 2001 14:50:03 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id OAA18426 for ; Sun, 22 Jul 2001 14:49:51 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 HAA24907; Mon, 23 Jul 2001 07:48:40 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id HAA17805; Mon, 23 Jul 2001 07:48:37 +1000 (AEST) Date: Mon, 23 Jul 2001 07:48:36 +1000 From: Nathan Scott To: Matthew Geier Cc: linux-xfs@oss.sgi.com, Jan Kara Subject: Re: Samba 2.2.1 RPMS with ACL Message-ID: <20010723074836.C230215@wobbly.melbourne.sgi.com> References: <3B52A14E.6D0D4FA5@ch.sauter-bc.com><3B563C52.A3101025@xfs.lists.logout.sh> <20010720010215.77ebf768.jpenix@projectdesign.com> <010d01c11103$53d55af0$2df958c1@mpb> <3B58C4BE.E2535CA0@arts.usyd.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B58C4BE.E2535CA0@arts.usyd.edu.au>; from matthew@arts.usyd.edu.au on Sat, Jul 21, 2001 at 09:54:38AM +1000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Sat, Jul 21, 2001 at 09:54:38AM +1000, Matthew Geier wrote: > ... > I did notice one problem with Samba on XFS systems. Quota support > doesn't work. After a look in smbd/quota.c, I see the quota's don't work > as XFS doesn't fill out the standard linux quota data structure, you > have to use XFS specfic structures. > Hmm - I had no idea samba had knowledge of quota. > NetAtalk also has linux quota code that has exactly the same problem. > > Any particular reason why XFS doesn't fill out the 'standard' quota > data structure. Yes, there are a number of reasons - the most important being that XFS use 64 bit numbers for a number of the key fields in a dquot, and that XFS logs all dquot changes (dquots are XFS metadata) which has fairly far reaching ramifications - bear in mind that dquot changes come in across the syscall interface as well. It is not so much that XFS has a different data structure, but more that XFS has a completely different implementation of quota. There is also no 'standard' quota data structure - as you'll see if you look through that file. In fact, having just looked through that file, I see the IRIX quota system call interface is recognised (which is quite similar to the Linux/XFS interface), so someone should be able to join the dots here and make this code work for Linux/XFS. > As it stands any linux application that checks quota's > wont see XFS file system quotas with out modification. If you run That is correct - and in 2.5 timeframe I expect that all of these programs will simply stop working, and start getting EINVAL back from quotactl, when Jan's changes to the quota subsystem go in. > multiple file systems the quota code then needs to know the file system > type... > It is actually even more involved that that. Jan has an entirely new implementation of quota (in the -ac series of kernels) which also has a different syscall interface. So, not only will they need to know what filesystem type, but also which kernel implementation. The quota-3.01 userspace package has all the changes needed to work with all three forms of quota transparently, so it shouldn't be too difficult for these affected packages' authors to to take that code and make the changes needed to their own code. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 22 15:11:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MMBh812445 for linux-xfs-outgoing; Sun, 22 Jul 2001 15:11:43 -0700 Received: from studsv07.studserv.uni-stuttgart.de (studsv07.studserv.uni-stuttgart.de [129.69.21.37]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MMBfV12425 for ; Sun, 22 Jul 2001 15:11:41 -0700 Received: from ysabell.wh.vaih [129.69.166.244] by studsv07.studserv.uni-stuttgart.de with ESMTP (SMTPD32-6.06) id AF9649902A8; Mon, 23 Jul 2001 00:11:34 +0200 Received: from marcelo by ysabell.wh.vaih with local (Exim 3.31 #1 (Debian)) id 15ORRr-0001va-00; Mon, 23 Jul 2001 00:11:39 +0200 Date: Mon, 23 Jul 2001 00:11:39 +0200 From: "Marcelo E. Magallon" To: Alan Eldridge , SGI XFS Dev List Subject: Re: libtoolizing Message-ID: <20010723001139.D6610@ysabell.wh.vaih> Mail-Followup-To: Alan Eldridge , SGI XFS Dev List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010723065116.A230215@wobbly.melbourne.sgi.com> User-Agent: Mutt/1.3.18i X-Operating-System: Linux ysabell 2.4.7-xfs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >> Nathan Scott writes: > The GNU documentation is quite good I concur. If the documentation isn't enough, there's the autobook, available either as dead trees, online[0] or, if you use Debian, in the autobook package. [0] http://sourceware.cygnus.com/autobook/ From owner-linux-xfs@oss.sgi.com Sun Jul 22 16:33:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6MNXCw20151 for linux-xfs-outgoing; Sun, 22 Jul 2001 16:33:12 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6MNX9V20125 for ; Sun, 22 Jul 2001 16:33:10 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id QAA02178 for ; Sun, 22 Jul 2001 16:30:45 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 JAA25333; Mon, 23 Jul 2001 09:31:45 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id JAA22156; Mon, 23 Jul 2001 09:31:43 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107230931.ZM222496@wobbly.melbourne.sgi.com> Date: Mon, 23 Jul 2001 09:31:39 +1000 In-Reply-To: Hasch@t-online.de (Juergen Hasch) "Re: TAKE - userspace" (Jul 22, 11:57am) References: <200107200826.SAA36970@snort.melbourne.sgi.com> <15O3gO-0CJtrcC@fwd01.sul.t-online.com> <20010722184531.B224198@wobbly.melbourne.sgi.com> <15OFyw-18xRT6C@fwd06.sul.t-online.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Hasch@t-online.de (Juergen Hasch) Subject: Re: TAKE - userspace Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 22, 11:57am, Juergen Hasch wrote: > Subject: Re: TAKE - userspace > > ... > > Having said all that, I do agree that the static libraries should > > go into /usr/lib - its just a matter of coercing libtool to put them > > there or changing our own install process - I'll have a look into it > > sometime this week. > > This is all I wanted to say before I got mislead in the technical details... > Don't drink and email ;-) :-) > The patch below does work for me, it may be better to add symlinks > of the libacl.so files to /usr/lib, too. > OK, will do. > ...Juergen > > --- builddefs.in.orig Fri Jul 20 16:51:24 2001 > +++ builddefs.in Sun Jul 22 10:44:11 2001 Yes, this was basically what I would've done too - I'm just not sure what will happen if the libtool archive (.la file) is installed into a different place to where its "supposed" to go - if you cat the .la file, you will see what I mean here (see "libdir="). thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 22 18:01:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N112P27990 for linux-xfs-outgoing; Sun, 22 Jul 2001 18:01:02 -0700 Received: from duval.se.mediaone.net (duval.se.mediaone.net [24.129.0.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N10iV27949 for ; Sun, 22 Jul 2001 18:00:57 -0700 Received: from enterprise (rr-163-49-140.atl.mediaone.net [24.163.49.140]) by duval.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f6N0xeP17928 for ; Sun, 22 Jul 2001 20:59:41 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: Subject: log mount/recovery failed Date: Sun, 22 Jul 2001 20:59:30 -0400 Organization: Linux-TechSupport.Com Message-ID: <000001c11312$c1093630$0101a8c0@enterprise> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01C112F1.39F79630" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2616 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0001_01C112F1.39F79630 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit After a system crash, I get the following message when trying to mount my filesystem: [root@Voyager /root]# mount /usr/fileserver/movies mount: wrong fs type, bad option, bad superblock on /dev/vg04/lv_movies, or too many mounted file systems [root@Voyager /root]# dmesg .... .... SGI XFS with ACLs, EAs, DMAPI, no debug enabled Start mounting filesystem: lvm(58,0) XFS: log has mismatched uuid - can't recover XFS: failed to find log head XFS: log mount/recovery failed XFS: log mount failed [root@Voyager /root]# uname -a Linux Voyager 2.4.7-xfs-1 #2 SMP Sat Jul 21 18:28:36 EDT 2001 i686 unknown This is a 14Gb disk configured as VG04. lv_movies is the only LV in the VG. I'm using the CVS patch I pulled from the FTP site just a day or so ago. I'm using an Abit BP6 Motherboard and this disk is hdg - HPT366 master, no slave disk attached. Any hope for recovering my data? Is it worth rebooting under an older (possibly more stable xfs release) kernel? Thanks Justin ------=_NextPart_000_0001_01C112F1.39F79630 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Message
    After = a system=20 crash, I get the following message when trying to mount my=20 filesystem:
     
    [root@Voyager /root]# mount /usr/fileserver/movies
    mount: = wrong fs=20 type, bad option, bad superblock on=20 /dev/vg04/lv_movies,
           or too many = mounted=20 file systems
     
    [root@Voyager /root]# dmesg
    ....
    ....
    SGI XFS with=20 ACLs, EAs, DMAPI, no debug enabled
    Start mounting filesystem:=20 lvm(58,0)
    XFS: log has mismatched uuid - can't recover
    XFS: failed = to find=20 log head
    XFS: log mount/recovery failed
    XFS: log mount=20 failed
     
    [root@Voyager /root]# uname -a
    Linux Voyager 2.4.7-xfs-1 #2 = SMP Sat=20 Jul 21 18:28:36 EDT 2001 i686 unknown
     
    This = is a 14Gb disk=20 configured as VG04.  lv_movies is the only LV in the=20 VG.
     
    I'm = using the CVS=20 patch I pulled from the FTP site just a day or so = ago.
     
    I'm = using an Abit=20 BP6 Motherboard and this disk is hdg - HPT366 master, no slave disk=20 attached.
     
    Any = hope for=20 recovering my data? 
     
    Is it = worth=20 rebooting under an older (possibly more stable xfs release)=20 kernel?
     
    Thanks
     
    Justin
    ------=_NextPart_000_0001_01C112F1.39F79630-- From owner-linux-xfs@oss.sgi.com Sun Jul 22 18:06:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N16mj28756 for linux-xfs-outgoing; Sun, 22 Jul 2001 18:06:48 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N16kV28734 for ; Sun, 22 Jul 2001 18:06:46 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id SAA07244 for ; Sun, 22 Jul 2001 18:04:22 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA41662 for linux-xfs@oss.sgi.com; Mon, 23 Jul 2001 11:05:21 +1000 (EST) Date: Mon, 23 Jul 2001 11:05:21 +1000 (EST) From: Nathan Scott Message-Id: <200107230105.LAA41662@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - static libs Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Installing the .la and .a files into /usr/lib, in spite of libtool, seems to work just fine. cheers. Date: Sun Jul 22 18:00:35 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99351a cmd/attr/VERSION - 1.7 cmd/attr/debian/changelog - 1.7 cmd/attr/doc/CHANGES - 1.8 cmd/attr/include/builddefs.in - 1.6 cmd/xfsdump/VERSION - 1.14 cmd/xfsdump/configure.in - 1.11 cmd/xfsdump/debian/changelog - 1.10 cmd/xfsdump/doc/CHANGES - 1.17 cmd/xfsdump/include/builddefs.in - 1.6 cmd/xfsprogs/include/builddefs.in - 1.11 cmd/xfsprogs/doc/CHANGES - 1.28 cmd/xfsprogs/debian/changelog - 1.20 cmd/xfsprogs/VERSION - 1.23 cmd/acl/VERSION - 1.11 cmd/acl/debian/changelog - 1.6 cmd/acl/doc/CHANGES - 1.12 cmd/acl/include/builddefs.in - 1.6 cmd/dmapi/include/builddefs.in - 1.7 cmd/dmapi/VERSION - 1.6 cmd/dmapi/debian/changelog - 1.4 cmd/dmapi/doc/CHANGES - 1.6 - install static libs and libtool archives into /usr/lib, not /lib. From owner-linux-xfs@oss.sgi.com Sun Jul 22 18:15:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N1FkC29639 for linux-xfs-outgoing; Sun, 22 Jul 2001 18:15:46 -0700 Received: from duval.se.mediaone.net (duval.se.mediaone.net [24.129.0.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N1FiV29620 for ; Sun, 22 Jul 2001 18:15:44 -0700 Received: from enterprise (rr-163-49-140.atl.mediaone.net [24.163.49.140]) by duval.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f6N1FHP25299 for ; Sun, 22 Jul 2001 21:15:17 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: "'xfs'" Subject: FW: log mount/recovery failed Date: Sun, 22 Jul 2001 21:15:09 -0400 Organization: Linux-TechSupport.Com Message-ID: <000801c11314$ef3bc570$0101a8c0@enterprise> 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.2616 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry for the HTML/MIME -----Original Message----- After a system crash, I get the following message when trying to mount my filesystem: [root@Voyager /root]# mount /usr/fileserver/movies mount: wrong fs type, bad option, bad superblock on /dev/vg04/lv_movies, or too many mounted file systems [root@Voyager /root]# dmesg .... .... SGI XFS with ACLs, EAs, DMAPI, no debug enabled Start mounting filesystem: lvm(58,0) XFS: log has mismatched uuid - can't recover XFS: failed to find log head XFS: log mount/recovery failed XFS: log mount failed [root@Voyager /root]# uname -a Linux Voyager 2.4.7-xfs-1 #2 SMP Sat Jul 21 18:28:36 EDT 2001 i686 unknown This is a 14Gb disk configured as VG04. lv_movies is the only LV in the VG. I'm using the CVS patch I pulled from the FTP site just a day or so ago. I'm using an Abit BP6 Motherboard and this disk is hdg - HPT366 master, no slave disk attached. Any hope for recovering my data? Is it worth rebooting under an older (possibly more stable xfs release) kernel? Thanks Justin From owner-linux-xfs@oss.sgi.com Sun Jul 22 18:16:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N1GYm29709 for linux-xfs-outgoing; Sun, 22 Jul 2001 18:16:34 -0700 Received: from duval.se.mediaone.net (duval.se.mediaone.net [24.129.0.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N1GWV29690 for ; Sun, 22 Jul 2001 18:16:32 -0700 Received: from enterprise (rr-163-49-140.atl.mediaone.net [24.163.49.140]) by duval.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f6N1G6P25804 for ; Sun, 22 Jul 2001 21:16:06 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: "'xfs'" Subject: FW: log mount/recovery failed Date: Sun, 22 Jul 2001 21:15:58 -0400 Organization: Linux-TechSupport.Com Message-ID: <000901c11315$0c565530$0101a8c0@enterprise> 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.2616 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry for the HTML/MIME -----Original Message----- After a system crash, I get the following message when trying to mount my filesystem: [root@Voyager /root]# mount /usr/fileserver/movies mount: wrong fs type, bad option, bad superblock on /dev/vg04/lv_movies, or too many mounted file systems [root@Voyager /root]# dmesg .... .... SGI XFS with ACLs, EAs, DMAPI, no debug enabled Start mounting filesystem: lvm(58,0) XFS: log has mismatched uuid - can't recover XFS: failed to find log head XFS: log mount/recovery failed XFS: log mount failed [root@Voyager /root]# uname -a Linux Voyager 2.4.7-xfs-1 #2 SMP Sat Jul 21 18:28:36 EDT 2001 i686 unknown This is a 14Gb disk configured as VG04. lv_movies is the only LV in the VG. I'm using the CVS patch I pulled from the FTP site just a day or so ago. I'm using an Abit BP6 Motherboard and this disk is hdg - HPT366 master, no slave disk attached. Any hope for recovering my data? Is it worth rebooting under an older (possibly more stable xfs release) kernel? Thanks Justin From owner-linux-xfs@oss.sgi.com Sun Jul 22 18:34:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N1YVZ30951 for linux-xfs-outgoing; Sun, 22 Jul 2001 18:34:31 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N1YTV30932 for ; Sun, 22 Jul 2001 18:34:29 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id SAA29523 for ; Sun, 22 Jul 2001 18:34:18 -0700 (PDT) mail_from (dxm@snort.melbourne.sgi.com) Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id LAA25997; Mon, 23 Jul 2001 11:33:10 +1000 (EST) Message-Id: <200107230133.LAA25997@snort.melbourne.sgi.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Justin@Linux-TechSupport.Com cc: linux-xfs@oss.sgi.com Subject: Re: FW: log mount/recovery failed In-reply-to: Your message of "Sun, 22 Jul 2001 21:15:58 -0400." <000901c11315$0c565530$0101a8c0@enterprise> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jul 2001 11:33:09 +1000 From: Daniel Moore Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Justin Hamilton" writes: => SGI XFS with ACLs, EAs, DMAPI, no debug enabled => Start mounting filesystem: lvm(58,0) => XFS: log has mismatched uuid - can't recover => XFS: failed to find log head => XFS: log mount/recovery failed => XFS: log mount failed The message "log has mismatched uuid" means that the uuid stored in the log isn't equal to that saved in the superblock. Could you try printing out the SB with xfs_db ('sb', 'print') and the log with xfs_logprint -t ? This shouldn't happen unless you're using a mismatched external log. ----------------------------------------------------- Daniel Moore dxm@sgi.com R&D Software Engineer Phone: +61-3-98348209 SGI Performance Tools Group Fax: +61-3-98132378 ----------------------------------------------------- From owner-linux-xfs@oss.sgi.com Sun Jul 22 23:02:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N62Hh10003 for linux-xfs-outgoing; Sun, 22 Jul 2001 23:02:17 -0700 Received: from duval.se.mediaone.net (duval.se.mediaone.net [24.129.0.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N62CV09982 for ; Sun, 22 Jul 2001 23:02:12 -0700 Received: from enterprise (rr-163-49-140.atl.mediaone.net [24.163.49.140]) by duval.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f6N61eP06473; Mon, 23 Jul 2001 02:01:40 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: "'Daniel Moore'" Cc: Subject: RE: FW: log mount/recovery failed Date: Mon, 23 Jul 2001 02:01:31 -0400 Organization: Linux-TechSupport.Com Message-ID: <000001c1133c$f34c1660$0101a8c0@enterprise> 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.2616 Importance: Normal In-Reply-To: <200107230133.LAA25997@snort.melbourne.sgi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Here's the logprint of my filesystem: [root@Voyager /]# xfs_logprint -t /dev/vg04/lv_movies xfs_logprint: data device: 0x3a07 log device: 0x3a07 daddr: 10485792 length: 9600 * ERROR: mismatched uuid in log * SB : 5a0fad57-e48c-41be-bee6-308250aecd17 * log: 00000100-0000-0100-0000-a00000000000 Bad log Looks like a problem... How do I set the UUID for the log? Here's the other piece of info: [root@Voyager /]# xfs_db /dev/vg04/lv_movies xfs_db: sb xfs_db: print magicnum = 0x58465342 blocksize = 4096 dblocks = 3750912 rblocks = 0 rextents = 0 uuid = 5a0fad57-e48c-41be-bee6-308250aecd17 logstart = 1310724 rootino = 128 rbmino = 129 rsumino = 130 rextsize = 16 agblocks = 262144 agcount = 15 rbmblocks = 0 logblocks = 1200 versionnum = 0x2084 sectsize = 512 inodesize = 256 inopblock = 16 fname = "\000\000\000\000\000\000\000\000\000\000\000\000" blocklog = 12 sectlog = 9 inodelog = 8 inopblog = 4 agblklog = 18 rextslog = 0 inprogress = 0 imax_pct = 25 icount = 2240 ifree = 812 fdblocks = 580716 frextents = 0 uquotino = 0 gquotino = 0 qflags = 0 flags = 0 shared_vn = 0 inoalignmt = 2 unit = 0 width = 0 dirblklog = 0 From owner-linux-xfs@oss.sgi.com Sun Jul 22 23:17:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N6Hne10419 for linux-xfs-outgoing; Sun, 22 Jul 2001 23:17:49 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N6HkV10400 for ; Sun, 22 Jul 2001 23:17:46 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id IAA134055 for ; Mon, 23 Jul 2001 08:17:34 +0200 (CEST) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA46904; Mon, 23 Jul 2001 16:16:22 +1000 (EST) Date: Mon, 23 Jul 2001 16:16:22 +1000 From: Timothy Shimmin To: "D. Stimits" Cc: Linux XFS Mailing List Subject: Re: Performance of near-full filesystems Message-ID: <20010723161622.M37341@boing.melbourne.sgi.com> References: <3B5B2EA4.BC769676@idcomm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Mailer: Mutt 1.0us In-Reply-To: <3B5B2EA4.BC769676@idcomm.com>; from stimits@idcomm.com on Sun, Jul 22, 2001 at 01:51:00PM -0600 X-MIME-Autoconverted: from 8bit to quoted-printable by yog-sothoth.sgi.com id IAA134055 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6N6HlV10401 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 22, 2001 at 01:51:00PM -0600, D. Stimits wrote: > Federico Sevilla III wrote: > > > > On Sun, 22 Jul 2001 at 08:03, Steve Lord wrote: > > > If you create a large number of files in XFS, inodes are allocated > > > dynamically for them. If you remove all the files, the inodes are not > > > returned to free space. On something like ext2 inodes are allocated at > > > mkfs time and the space is never available for anything else. This I > > > think is what you were referring to. > > > > Yes, this is what I was referring to. I was under the impression that this > > was "bad", though, and one effectively "lost space". Are inodes allocated > > dynamically for large files different from those allocated dynamically for > > a bunch of small files? Meaning, if inodes are allocated for a large file, > > then the large file is deleted, and the inodes are not returned to free > > space, will filling up these allocated inodes with small files be "bad" or > > would filling up the free space with small files (thus creating inodes for > > them) have had the same effect anyway? > > I had a minor, nagging worry, that if there is no cap on inode density, > that something like a fork bomb could become a denial of service > attack...allocate till much of the system is inode, and no way to get it > back. It would be good to have a cap on inode density, does something > like that exist now? >From mkfs.xfs(8): -i Inode options. [...stuff deleted] The option maxpct=value specifies the maximum per­ centage of space in the filesystem that can be allocated to inodes. The default value is 25%. Setting the value to 0 means that essentially all of the filesystem can become inode blocks. So by default you can only fill up an fs, with 25% worth of inodes. (I ran into this recently when testing xfsrestore on a small filesystem with heaps of inodes - I was doing this as I had a small test filesystem but wanted a lot of inodes to model a customer site.) --Tim From owner-linux-xfs@oss.sgi.com Sun Jul 22 23:19:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N6J2E10553 for linux-xfs-outgoing; Sun, 22 Jul 2001 23:19:02 -0700 Received: from zok.corp.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N6J0V10531 for ; Sun, 22 Jul 2001 23:19:00 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6N6NWF01992 for ; Sun, 22 Jul 2001 23:23:33 -0700 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id QAA50351; Mon, 23 Jul 2001 16:17:37 +1000 (EST) Message-Id: <200107230617.QAA50351@snort.melbourne.sgi.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Justin@Linux-TechSupport.Com cc: linux-xfs@oss.sgi.com Subject: Re: FW: log mount/recovery failed In-reply-to: Your message of "Mon, 23 Jul 2001 02:01:31 -0400." <000001c1133c$f34c1660$0101a8c0@enterprise> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jul 2001 16:17:36 +1000 From: Daniel Moore Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Justin Hamilton" writes: => Here's the logprint of my filesystem: => => [root@Voyager /]# xfs_logprint -t /dev/vg04/lv_movies => xfs_logprint: => data device: 0x3a07 => log device: 0x3a07 daddr: 10485792 length: 9600 => => * ERROR: mismatched uuid in log => * SB : 5a0fad57-e48c-41be-bee6-308250aecd17 => * log: 00000100-0000-0100-0000-a00000000000 => Bad log => => Looks like a problem... How do I set the UUID for the log? You can't and shouldn't have to set the uuid for the log. It gets written out in every log header and should always match the one in the SB. It looks like the log may have been clobbered somehow. You could try xfs_logprint with no '-t' and check out the uuids in the other log records. Maybe that would tell you something... If all else fails, you can run 'xfs_repair'. It will erase the log (NOT play it back) and repair the filesystem to a consistent state which should get you going again. But it would be nice to know what's going on here since this shouldn't happen. ----------------------------------------------------- Daniel Moore dxm@sgi.com R&D Software Engineer Phone: +61-3-98348209 SGI Performance Tools Group Fax: +61-3-98132378 ----------------------------------------------------- From owner-linux-xfs@oss.sgi.com Mon Jul 23 00:44:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N7iWP13302 for linux-xfs-outgoing; Mon, 23 Jul 2001 00:44:32 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N7iUV13283 for ; Mon, 23 Jul 2001 00:44:30 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id AAA19947 for ; Mon, 23 Jul 2001 00:44:17 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 RAA28342; Mon, 23 Jul 2001 17:43:09 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA31148; Mon, 23 Jul 2001 17:43:05 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107231743.ZM221213@wobbly.melbourne.sgi.com> Date: Mon, 23 Jul 2001 17:43:02 +1000 In-Reply-To: Steve Lord "Re: Anyone using XFS ACLs? (fwd)" (Jul 20, 1:33pm) References: <200107201833.f6KIX7H08390@jen.americas.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Danny Cox Subject: Re: Anyone using XFS ACLs? (fwd) Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Danny, On Jul 20, 1:33pm, Steve Lord wrote: > Subject: Re: Anyone using XFS ACLs? (fwd) > > This was sent privately, Danny later said he meant to send to the list, > any message mangling is entirely the fault of my mail tool. I expect we > will get something based on this into the tree fairly soon (is anyone > in Australia listening? hint hint). > > Steve > > > ------- Forwarded Message > > Date: Fri, 20 Jul 2001 12:35:35 -0400 > From: Danny Cox > To: Steve Lord > Subject: Re: Anyone using XFS ACLs? > > This is a multi-part message in MIME format. > - --------------4E072E6D209773EBBDAD1589 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > Steve, > > Steve Lord wrote: > > The other option here is for someone to take the source of something > > like chown which has a -R option, and chacl which does not. Merge the > > two and send in a patch. This is the sort of project which would be > > fairly easy for someone to tackle, would solve a problem. We are > > very tight on resources here and cannot be relied upon for things > > like bells and whistle extensions to commands like this. > > Steve, here is a patch that adds an '-r' arg to chacl, and decends > (depth first) a directory tree changing ACLs as it goes. It doesn't > attempt to list them recursively, as that is a little trickier (and > neither chown nor chmod attempt this). > > I did have a little problem. The "Makefile" uses the > '-D_FILE_OFFSET_BITS=64' which comes from ../include/builddefs, which > comes from ../include/builddefs.in, and causes the readdir to not work > correctly. The included file "" gets the wrong size, which > doesn't agree with my libc (I'm using RedHat 6.2, and it's standard > glibc). When I recompiled without that flag, it works like a champ. > > Short of defining 'struct dirent' myself (HACK!), I don't know how to > work around this other than how I did (remove the flag, which probably > breaks something else). > Tim and I were just having a look through this & we have a couple of questions/observations: - the descent algorithm you've used seems to be breadth-first, rather than depth-first ... was this your intention? (your mail suggests not). We agree it should be depth first (easily fixed by moving the call to walk_dir up to the top of set_acl); - trying to understand your '-D_FILE_OFFSET_BITS=64' problem - I think we do need this, I just can't understand how this was failing for you (can you give more details?) - I have a rh6.2 system here and it seems to work for the (limited) test cases we tried. We looked through the fileutils-4.1 code and that seems to define _FILE_OFFSET_BITS to 64 (via config.h) on redhat 6.2 also... Otherwise, the patch looks fine - I'll probably check it in shortly. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 23 01:30:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6N8U4C14932 for linux-xfs-outgoing; Mon, 23 Jul 2001 01:30:04 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6N8U0V14900 for ; Mon, 23 Jul 2001 01:30:01 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id KAA143018 for ; Mon, 23 Jul 2001 10:29:47 +0200 (CEST) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA61957 for linux-xfs@oss.sgi.com; Mon, 23 Jul 2001 18:28:36 +1000 (EST) Date: Mon, 23 Jul 2001 18:28:36 +1000 (EST) From: Nathan Scott Message-Id: <200107230828.SAA61957@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - chacl Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Mon Jul 23 01:27:49 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99359a cmd/xfstests/051.out - 1.9 cmd/xfstests/051 - 1.8 - test out the -r option to chacl. cmd/acl/chacl/chacl.c - 1.6 cmd/acl/doc/CHANGES - 1.13 - merge in a change from Danny Cox to add the -r option to chacl. fixed up a bunch of formatting inconsistencies while I was at it. From owner-linux-xfs@oss.sgi.com Mon Jul 23 03:37:49 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NAbnW19326 for linux-xfs-outgoing; Mon, 23 Jul 2001 03:37:49 -0700 Received: from jxmls04.se.mediaone.net (jxmls04.se.mediaone.net [24.129.0.51]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NAblV19300 for ; Mon, 23 Jul 2001 03:37:47 -0700 Received: from enterprise (rr-163-49-140.atl.mediaone.net [24.163.49.140]) by jxmls04.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f6NAaSH19161; Mon, 23 Jul 2001 06:36:29 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: "'Daniel Moore'" Cc: Subject: RE: FW: log mount/recovery failed Date: Mon, 23 Jul 2001 06:37:13 -0400 Organization: Linux-TechSupport.Com Message-ID: <000a01c11363$7387e360$0101a8c0@enterprise> 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.2616 Importance: Normal In-Reply-To: <200107230617.QAA50351@snort.melbourne.sgi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Here is the xfs_logprint: [root@Voyager /]# xfs_logprint /dev/vg04/lv_movies xfs_logprint: data device: 0x3a07 log device: 0x3a07 daddr: 10485792 length: 9600 Header 0xc wanted 0xfeedbabe ********************************************************************** * ERROR: header cycle=12 block=1463 * ********************************************************************** Bad log record header So somehow, it looks like the log is getting clobbered. Before I run the xfs_repair, is there any other info that will be useful to ensuring this get fixed? Justin -----Original Message----- From: owner-linux-xfs@oss.sgi.com [mailto:owner-linux-xfs@oss.sgi.com] On Behalf Of Daniel Moore Sent: Monday, July 23, 2001 2:18 AM To: Justin@Linux-TechSupport.Com Cc: linux-xfs@oss.sgi.com Subject: Re: FW: log mount/recovery failed "Justin Hamilton" writes: => Here's the logprint of my filesystem: => => [root@Voyager /]# xfs_logprint -t /dev/vg04/lv_movies => xfs_logprint: => data device: 0x3a07 => log device: 0x3a07 daddr: 10485792 length: 9600 => => * ERROR: mismatched uuid in log => * SB : 5a0fad57-e48c-41be-bee6-308250aecd17 => * log: 00000100-0000-0100-0000-a00000000000 => Bad log => => Looks like a problem... How do I set the UUID for the log? You can't and shouldn't have to set the uuid for the log. It gets written out in every log header and should always match the one in the SB. It looks like the log may have been clobbered somehow. You could try xfs_logprint with no '-t' and check out the uuids in the other log records. Maybe that would tell you something... If all else fails, you can run 'xfs_repair'. It will erase the log (NOT play it back) and repair the filesystem to a consistent state which should get you going again. But it would be nice to know what's going on here since this shouldn't happen. From owner-linux-xfs@oss.sgi.com Mon Jul 23 04:01:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NB1T020828 for linux-xfs-outgoing; Mon, 23 Jul 2001 04:01:29 -0700 Received: from exchange.visa-austria.com (visa091.cybertron.at [212.236.12.91] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NB1QV20805 for ; Mon, 23 Jul 2001 04:01:26 -0700 Received: by exchange.visa-austria.com with Internet Mail Service (5.5.2650.21) id <3NSCVD4A>; Mon, 23 Jul 2001 13:01:18 +0200 Message-ID: <4FF9029AF0C8D311B99D0050DA1CB9F4FB78F7@exchange.visa-austria.com> From: =?iso-8859-1?Q?KR=DCCKEL_OLIVER?= To: "'linux-xfs@oss.sgi.com'" Subject: WG: AW: xfs kernel problem Date: Mon, 23 Jul 2001 13:01:18 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6NB1RV20808 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hallo. The problem that i have with our server dosen't have anyhing to do with the xfs filesystem, there was a problem with the kerneldriver of the HP NetRAIN-1M controler (MegaRAID) and the HP server motherboard. This problem was fixed with kernel 2.4.7. since i use the kernel 2.4.7 with the xfs patch the server works fine Thanks for your assistance To info: megeraid.c #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,4,0) +#if 0 +/* + * This leads to corruption on some HP boards so disable it + */ pcibios_read_config_dword (pciBus, pciDevFun, PCI_CONF_AMISIG64, &magic64); if (magic64 == AMI_64BIT_SIGNATURE) flag |= BOARD_64BIT; +#endif -----Ursprüngliche Nachricht----- Von: Simon Matter [mailto:simon.matter@ch.sauter-bc.com] Gesendet: Donnerstag, 19. Juli 2001 07:53 An: KRÜCKEL OLIVER Cc: 'linux-xfs@oss.sgi.com' Betreff: Re: AW: xfs kernel problem KRÜCKEL OLIVER schrieb: > > On 17 Jul 2001 18:57:38 +0200, Krückel Oliver wrote: > > >> Linux SuSE-7.1 with servarel patches from the officel SuSE web-server > >> gcc: version 2.95.2 19991024 (release) > May I suggest you install RedHat 7.1-XFS on one machine just to make sure your hardware is okay? This could make your life much easier. > >Can you try compiling with a 2.91.66 gcc version? This is the first > >thing I'd try, newer compilers still have not been producing > >consistently good code. > > ok > > I get the egcs-1.1.2 (gcc 2.91.66) but I can't compile it. > I test it also with the gcc 3.0, but with the sam results with the gcc > 2.91.66 > > >> if i reboot the server with the xfs kernel and the server coms up there > are > >> sum files and executables witch i can't access ore execute, > >> > >> sum examples: the programms find, make, ... or file hosts, ... > >> > >> if i reboot the server again, there are much more files that can't access > or > >> execute, there are alwais other executebles and files by every test, > > >Can you give any more information about "can't access" - do they not > >show up in the directory listing, do they seem to contain wrong data... > >? > > I get at the startup process sum lines like the follow > > Initializing SMTP port. (sendmail)451 4.0.0 /etc/sendmail.cf: line 0: cannot > open: Permission denied > startproc: exit status of /usr/sbin/sendmail: 72 > failed > the file sendmail.cf hase the size 0 byte > > at sume other cases i can't access or list a file (i'm root) and I get the > massage permisson denied. > > >-Eric > > I test my config also on an other hp lp2000r server and I have the same > problems. From owner-linux-xfs@oss.sgi.com Mon Jul 23 04:31:57 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NBVvY23168 for linux-xfs-outgoing; Mon, 23 Jul 2001 04:31:57 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NBVsV23137 for ; Mon, 23 Jul 2001 04:31:54 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6NBXXG21239 for ; Mon, 23 Jul 2001 14:33:34 +0300 Date: Mon, 23 Jul 2001 14:31:49 +0300 (EEST) From: Jani Jaakkola To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: <200107191812.f6JICsI32762@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 19 Jul 2001, Steve Lord wrote: > > A little update, > > > > At least, some better news: > > I did *NOT* see the problem (yet!) with the noapic option > > with 2.4.7pre8-SMP > > > I am informed that there is a fix in the latest kernels in the raid5 code > to fix some stall issues which ext3 hit. So it maybe that the answer here > is to run the latest kernels. I still do not like the fact we do non-stripe > friendly I/O to the log, and want to look into that. > > Jani, this may also be the source of your problems, we did experience > an almost complete lockup here with the 1.0.1 rpm kernel. If you get a > chance can you run the latest cvs kernel? OK now I have the newest CVS kernel. Now I am getting the bad clientid mount problem on my sw RAID5 partition (this could be caused by the old kernel saving a garbled log) Mount says: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many mounted file systems And kernel says: XFS: xlog_recover_process_data: bad clientid XFS: log mount/recovery failed XFS: log mount failed In case anyone is interested, I have saved output of xfs_logprint and it is available from http://www.cs.helsinki.fi/u/jjaakkol/xfslog.txt I am starting xfs_repair on the RAID partition now.. It wen't through nicely and quickly and the files are still there. Hmm, the unlink() performance is definetely better, but still not very good (this just how it feels like, I have not yet done any real benchmarks). Hmm, I'll guess I have to get my hands on some other benchmark software than bonnie and try it with ext2, xfs+internal log and xfs+external log. - Jani From owner-linux-xfs@oss.sgi.com Mon Jul 23 04:36:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NBaC023503 for linux-xfs-outgoing; Mon, 23 Jul 2001 04:36:12 -0700 Received: from wiley.ceo.com (66-2-81-28.customer.algx.net [66.2.81.28]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NBa9V23483 for ; Mon, 23 Jul 2001 04:36:09 -0700 Received: from mindspring.com (IDENT:danny@localhost [127.0.0.1]) by wiley.ceo.com (8.9.3/8.9.3) with ESMTP id HAA01091; Mon, 23 Jul 2001 07:54:46 -0400 Message-ID: <3B5C1086.230C3AAA@mindspring.com> Date: Mon, 23 Jul 2001 07:54:46 -0400 From: Danny Cox Reply-To: dcox@connex.com Organization: Connex Inc X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Nathan Scott CC: linux-xfs@oss.sgi.com Subject: Re: Anyone using XFS ACLs? (fwd) References: <200107201833.f6KIX7H08390@jen.americas.sgi.com> <10107231743.ZM221213@wobbly.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Nathan, Nathan Scott wrote: > Tim and I were just having a look through this & we have a > couple of questions/observations: > > - the descent algorithm you've used seems to be breadth-first, > rather than depth-first ... was this your intention? (your > mail suggests not). We agree it should be depth first (easily > fixed by moving the call to walk_dir up to the top of set_acl); Hmm. Sorry. I'm mixing metaphors again. Then again, perhaps I just don't know my breadth from my depth ;-). Just after having submitted it, I realized that it would probably be more efficient to chdir into and out of directories. However, this is much more complicated, once having thought of it. You'd have to keep a directory stack, as ".." isn't always where you wish to "return" to (consider chacl -r u::rwx,g::rx,u::r w/x/y/z/). I'll leave implementation of that to the reader ;-). > - trying to understand your '-D_FILE_OFFSET_BITS=64' problem - > I think we do need this, I just can't understand how this was > failing for you (can you give more details?) - I have a rh6.2 > system here and it seems to work for the (limited) test cases > we tried. Okay, my /usr/include/dirent.h includes , in which I see: struct dirent { #ifndef __USE_FILE_OFFSET64 __ino_t d_ino; __off_t d_off; #else __ino64_t d_ino; __off64_t d_off; #endif unsigned short int d_reclen; unsigned char d_type; char d_name[256]; /* We must not include limits.h! */ }; Compiling chacl.c WITH -D_FILE_OFFSET_BITS=64 gets me file names of "". Using gdb, I can see "..", and later on, the other file names. Compiling WITHOUT -D_FILE_OFFSET_BITS=64 gets me proper file names. Searching /usr/include for "__USE_FILE_OFFSET64" yields (among others), "features.h". It is features.h that contains the snippet: #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 # define __USE_FILE_OFFSET64 1 #endif Thus, I conclude that chacl.c is using a struct dirent whose size doesn't match (is larger than) what readdir(3) is returning, no? > We looked through the fileutils-4.1 code and that seems to > define _FILE_OFFSET_BITS to 64 (via config.h) on redhat 6.2 > also... That's fine. I'm probably doing something wrong, but the fix is not obvious to me. > Otherwise, the patch looks fine - I'll probably check it in > shortly. Yep, at this time (Monday AM Eastern US Daylight), I can see your 'TAKE'. > thanks. Happy to be of service. -- "Men occasionally stumble over the truth, but most of them pick themselves up and hurry off as if nothing had happened." -- Winston Churchill Danny From owner-linux-xfs@oss.sgi.com Mon Jul 23 06:27:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NDRHS29921 for linux-xfs-outgoing; Mon, 23 Jul 2001 06:27:17 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NDRFV29902 for ; Mon, 23 Jul 2001 06:27:16 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id E2FF8C00087 for ; Mon, 23 Jul 2001 21:27:11 +0800 (PHT) Date: Mon, 23 Jul 2001 21:27:11 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: An interesting study on filesystem fragmentation Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, I stumbled upon this on the ReiserFS mailing list but I think it's something relevant that ought to be shared here. First the URL: The site says it all, but for those of you who want a preview first, Constantin Loizides is working on a study to do an artificial aging of a filesystem, and in the process is studying the effects of this aging on the internal and external fragmentation on the filesystem, and the effects of this on benchmark results. --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Mon Jul 23 06:58:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NDwUZ32626 for linux-xfs-outgoing; Mon, 23 Jul 2001 06:58:30 -0700 Received: from webmail.chimesnet.com (postfix@mail001.level3.chc-chimes.com [63.211.16.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NDwTV32606 for ; Mon, 23 Jul 2001 06:58:29 -0700 Received: from orbis.internal.chc-chimes.com (pixnat.chc-chimes.com [216.28.46.20]) by webmail.chimesnet.com (Postfix) with ESMTP id B65FECAC501 for ; Mon, 23 Jul 2001 09:58:27 -0400 (EDT) Received: from tcarroll by orbis.internal.chc-chimes.com with local (Exim 3.22 #1 (Debian)) id 15OgDv-000088-00 for ; Mon, 23 Jul 2001 09:58:15 -0400 Date: Mon, 23 Jul 2001 09:58:15 -0400 To: linux-xfs Subject: BSD system immutable flag Message-ID: <20010723095815.B402@chimesnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.18i From: Tom Carroll Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello everyone, Does xfs have anything like the BSD system immutable flag ( schg )? Is there any plans to add BSD extended attributes to xfs? Thanks in advance. -- Tom Carroll email: tcarroll@chimesnet.com pgp: mailto:pgp@chimesnet.com?subject=GET%20tcarroll@chimesnet.com From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:04:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NE4xZ00910 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:04:59 -0700 Received: from ns.caldera.de (ns.caldera.de [212.34.180.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NE4vV00887 for ; Mon, 23 Jul 2001 07:04:57 -0700 Received: (from hch@localhost) by ns.caldera.de (8.11.1/8.11.1) id f6NE4hn13759; Mon, 23 Jul 2001 16:04:43 +0200 Date: Mon, 23 Jul 2001 16:04:43 +0200 From: Christoph Hellwig To: Tom Carroll Cc: linux-xfs Subject: Re: BSD system immutable flag Message-ID: <20010723160443.B12987@caldera.de> References: <20010723095815.B402@chimesnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010723095815.B402@chimesnet.com>; from tcarroll@chimesnet.com on Mon, Jul 23, 2001 at 09:58:15AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 23, 2001 at 09:58:15AM -0400, Tom Carroll wrote: > Hello everyone, > > Does xfs have anything like the BSD system immutable flag ( schg )? Nope. > Is there any plans to add BSD extended attributes to xfs? BSD (that is besides FreeBSD -CURRENT) does not have extended attributes. Christoph -- Whip me. Beat me. Make me maintain AIX. From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:05:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NE5He01053 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:05:17 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NE5GV01034 for ; Mon, 23 Jul 2001 07:05:16 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA16292 for ; Mon, 23 Jul 2001 07:05:04 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2491231; Mon, 23 Jul 2001 09:03:59 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA25733; Mon, 23 Jul 2001 09:03:59 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NE4B010447; Mon, 23 Jul 2001 09:04:11 -0500 Message-Id: <200107231404.f6NE4B010447@jen.americas.sgi.com> To: Tom Carroll cc: linux-xfs Subject: Re: BSD system immutable flag References: <20010723095815.B402@chimesnet.com> Comments: In-reply-to Tom Carroll message dated "Mon, 23 Jul 2001 09:58:15 -0400." Date: Mon, 23 Jul 2001 09:04:11 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hello everyone, > > Does xfs have anything like the BSD system immutable flag ( schg )? > Is there any plans to add BSD extended attributes to xfs? No we do not, and there is no current plan to implement it, but if someone wants to try it I would be happy to help out. Note that ext2 has a similar feature, although I am told the bsd one is more flexible. Steve > > > Thanks in advance. > > -- > Tom Carroll email: tcarroll@chimesnet.com > pgp: mailto:pgp@chimesnet.com?subject=GET%20t > carroll@chimesnet.com From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:08:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NE8oa01447 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:08:50 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NE8mV01427 for ; Mon, 23 Jul 2001 07:08:49 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA16501 for ; Mon, 23 Jul 2001 07:08:37 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2503282; Mon, 23 Jul 2001 09:07:32 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA38363; Mon, 23 Jul 2001 09:07:32 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NE7iW10457; Mon, 23 Jul 2001 09:07:44 -0500 Message-Id: <200107231407.f6NE7iW10457@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jani Jaakkola cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Jani Jaakkola of "Mon, 23 Jul 2001 14:31:49 +0300." Date: Mon, 23 Jul 2001 09:07:44 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Thu, 19 Jul 2001, Steve Lord wrote: > > > > A little update, > > > > > > At least, some better news: > > > I did *NOT* see the problem (yet!) with the noapic option > > > with 2.4.7pre8-SMP > > > > > > I am informed that there is a fix in the latest kernels in the raid5 code > > to fix some stall issues which ext3 hit. So it maybe that the answer here > > is to run the latest kernels. I still do not like the fact we do non-stripe > > friendly I/O to the log, and want to look into that. > > > > Jani, this may also be the source of your problems, we did experience > > an almost complete lockup here with the 1.0.1 rpm kernel. If you get a > > chance can you run the latest cvs kernel? > > OK now I have the newest CVS kernel. Now I am getting the bad clientid > mount problem on my sw RAID5 partition (this could be caused by the old > kernel saving a garbled log) > > Mount says: > > mount: wrong fs type, bad option, bad superblock on /dev/md0, > or too many mounted file systems > > And kernel says: > > XFS: xlog_recover_process_data: bad clientid > XFS: log mount/recovery failed > XFS: log mount failed There is definitely a problem with the log on raid5 right now, we did not change anything on our end, so it looks like the underlying code may have broken things. We are looking into this. As for performance, the stall appears to be fixed, now we are just dealing with the issue of non-aligned and variable sized writes. We have some ideas about stripe aligning log writes, but this may take a while. An external log should go faster, on the delete end though, there is a synchronous write to the log in there, so the number of ops per second your journal device can do is important for delete performance. Steve > > In case anyone is interested, I have saved output of xfs_logprint > and it is available from http://www.cs.helsinki.fi/u/jjaakkol/xfslog.txt > > I am starting xfs_repair on the RAID partition now.. It wen't through > nicely and quickly and the files are still there. Hmm, the unlink() > performance is definetely better, but still not very good (this just how > it feels like, I have not yet done any real benchmarks). > > Hmm, I'll guess I have to get my hands on some other benchmark software > than bonnie and try it with ext2, xfs+internal log and xfs+external log. > > - Jani From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:29:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NETEa02773 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:29:14 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NESmV02752 for ; Mon, 23 Jul 2001 07:28:50 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6NESV0102285; Mon, 23 Jul 2001 16:28:31 +0200 (CEST) Message-ID: <3B5C3451.BC51BB63@pasteur.fr> Date: Mon, 23 Jul 2001 16:27:29 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: Jani Jaakkola , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP References: <200107231407.f6NE7iW10457@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > <...> > An external log should > go faster, on the delete end though, there is a synchronous write to the > log in there, so the number of ops per second your journal device can > do is important for delete performance. Hello, Updated data with e) /dev/md0 raid5 xfs with an external log on /dev/md4 (a 128MB raid1 array on hda and hdc) and f) over nfs. Everything being the same as in the previous mails. > How long does it take to extract the 2.4.6 linux kernel and delete it? > > | create | delete > ------------------- > a) | 0:17 | 0:07 > b) | 0:24 | 0:25 > c) | 1:51' | 16:45 > d) | 2:54 | 8:08 --------------------- e) | 0:10 | 0:02 to be compared with c) f) | 0:41 | 0:23 to be compared with d) > > [tru@adm ~/tmp]$ du -sk /tmp/linux-2.4.6.tar.gz ./linux/ > 26312 /tmp/linux-2.4.6.tar.gz > 130412 ./linux > > a) local xfs partition on the will become nfs client > b) local xfs raid5 array on a single disk (/dev/md1) on the will become > nfs server > c) local xfs raid5 array on 3ware card 7disks (/dev/md0) on the will > become nfs server > d) nfs e) local xfs raid5 array on 3ware card 7disks (/dev/md0) WITH external xfslog /dev/md5 (raid1) f) nfs exported /dev/md0 > bonnie block (K/sec) > |output|input > |------------ > c) |47340 |77559 > d) | 4390 |10777 --------------------- e) 45753 |10304 f) 4410 |10693 e) [tru@sheridan /raid5]$ date ; time tar xzf /tmp/linux-2.4.6.tar.gz ; date; time /bin/rm -rf linux ; date Mon Jul 23 15:03:02 CEST 2001 4.890u 3.920s 0:09.82 89.7% 0+0k 0+0io 327pf+0w Mon Jul 23 15:03:12 CEST 2001 0.060u 1.880s 0:02.21 87.7% 0+0k 0+0io 138pf+0w Mon Jul 23 15:03:14 CEST 2001 [tru@sheridan ~]$ ~/bonnie++-1.00g/bonnie++ -d /raid5 Writing with putc()...done Writing intelligently...done Rewriting...done Reading with getc()...done Reading intelligently...done start 'em...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.00g ------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 sheridan.bis.pas 2G 10753 97 45753 81 23834 56 10304 97 76821 68 469.3 3 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 2257 93 +++++ +++ 2032 84 2245 95 +++++ +++ 1624 87 sheridan.bis.pasteur.fr,2G,10753,97,45753,81,23834,56,10304,97,76821,68,469.3,3,16,2257,93,+++++,+++,2032,84,2245,95,+++++,+++,1624,87 f) [tru@adm tru]$ date ; time tar xzf /tmp/linux-2.4.6.tar.gz ; date; time /bin/rm -rf linux ; date Mon Jul 23 15:03:24 CEST 2001 2.770u 2.340s 0:41.12 12.4% 0+0k 0+0io 325pf+0w Mon Jul 23 15:04:05 CEST 2001 0.020u 0.380s 0:22.71 1.7% 0+0k 0+0io 138pf+0w Mon Jul 23 15:04:28 CEST 2001 [tru@adm tru]$ ~/rh71/build/bonnie++-1.00g/bonnie++ -d /home/Bis/tru/ Writing with putc()...done Writing intelligently...done Rewriting...done Reading with getc()...done Reading intelligently...done start 'em...done...done...done... Create files in sequential order...done. Stat files in sequential order...done. Delete files in sequential order...done. Create files in random order...done. Stat files in random order...done. Delete files in random order...done. Version 1.00g ------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 adm.cluster 1G 4393 32 4410 2 3092 3 10585 88 10693 4 644.3 3 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 1094 3 4499 14 1219 4 1147 4 4968 6 1084 4 adm.cluster,1G,4393,32,4410,2,3092,3,10585,88,10693,4,644.3,3,16,1094,3,4499,14,1219,4,1147,4,4968,6,1084,4 Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:34:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NEYKu03264 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:34:20 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NEYIV03241 for ; Mon, 23 Jul 2001 07:34:18 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6NEZxG14966 for ; Mon, 23 Jul 2001 17:36:00 +0300 Date: Mon, 23 Jul 2001 17:34:14 +0300 (EEST) From: Jani Jaakkola To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 23 Jul 2001, Jani Jaakkola wrote: > Hmm, I'll guess I have to get my hands on some other benchmark software > than bonnie and try it with ext2, xfs+internal log and xfs+external log. OK, it seems that create/delete performance on linux XFS with sw RAID is still bad with current cvs kernel (not terrible anymore, but bad enough that I would not put xfs with sw RAID to production use). I downloaded bonnie++ and did some tests This is an IDE drive with ext2 (without DMA, since the kernel turns it off with my IDE controller for some readon): -----snip------ Version 1.01b ------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 other-fs 2G 5970 93 8058 6 2981 12 5774 80 8553 63 109.1 2 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 912 100 +++++ +++ +++++ +++ 925 99 +++++ +++ 5245 99 -----snip------ This is the same IDE drive with xfs (without DMA also!). Not too bad when compared to ext2: -----snip------ Version 1.01b ------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 other-fs 2G 7691 99 11853 11 3999 31 6317 85 8652 65 112.4 3 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 730 57 +++++ +++ 781 61 735 54 +++++ +++ 366 26 -----snip------ And this is the RAID array with internal log -----snip------ Version 1.01b ------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 other-fs 2G 11253 96 39684 34 7829 8 10858 89 131226 83 320.2 2 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 75 1 +++++ +++ 114 2 91 2 +++++ +++ 61 1 -----snip------ So the RAID array is 5 times faster in pure write IO, but xfs with internal log kills create/delete performance with IO stalls. With external log the create/delete performance is again acceptable: -----snip------ Version 1.01b ------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 other-fs 2G 11235 96 43660 36 7728 8 10891 90 132525 81 322.1 2 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 854 66 +++++ +++ 793 66 833 64 +++++ +++ 691 58 -----snip------ So the sw RAID internal log performance is not fixed yet :( - Jani From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:35:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NEZJh03432 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:35:19 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NEZHV03406 for ; Mon, 23 Jul 2001 07:35:17 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA09295 for ; Mon, 23 Jul 2001 07:32:54 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2504320; Mon, 23 Jul 2001 09:32:43 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA71652; Mon, 23 Jul 2001 09:32:43 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NEWtY15667; Mon, 23 Jul 2001 09:32:55 -0500 Message-Id: <200107231432.f6NEWtY15667@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Tru Huynh cc: Steve Lord , Jani Jaakkola , "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Tru Huynh of "Mon, 23 Jul 2001 16:27:29 +0200." <3B5C3451.BC51BB63@pasteur.fr> Date: Mon, 23 Jul 2001 09:32:55 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Steve Lord wrote: > > > <...> > > An external log should > > go faster, on the delete end though, there is a synchronous write to the > > log in there, so the number of ops per second your journal device can > > do is important for delete performance. > > Hello, > > Updated data with e) /dev/md0 raid5 xfs with an external log > on /dev/md4 (a 128MB raid1 array on hda and hdc) and f) over nfs. > Everything being the same as in the previous mails. > > > How long does it take to extract the 2.4.6 linux kernel and delete it? > > > > | create | delete > > ------------------- > > a) | 0:17 | 0:07 > > b) | 0:24 | 0:25 > > c) | 1:51' | 16:45 > > d) | 2:54 | 8:08 > --------------------- > e) | 0:10 | 0:02 to be compared with c) > f) | 0:41 | 0:23 to be compared with d) These numbers look a lot better - clearly the log on raid5 is not operating well at all. Can you tell me if you have any problems with unmounting and remounting the filesystem with the external log? This will let us narrow down the log problems to raid5 - which I expect to be the only case with this problem. Thanks Steve From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:44:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NEiZD03998 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:44:35 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NEiUV03979 for ; Mon, 23 Jul 2001 07:44:31 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA182628 for ; Mon, 23 Jul 2001 16:44:21 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2494213; Mon, 23 Jul 2001 09:43:11 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA95806; Mon, 23 Jul 2001 09:43:11 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NEhNB15714; Mon, 23 Jul 2001 09:43:23 -0500 Message-Id: <200107231443.f6NEhNB15714@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Jani Jaakkola cc: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message from Jani Jaakkola of "Mon, 23 Jul 2001 17:34:14 +0300." Date: Mon, 23 Jul 2001 09:43:22 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Mon, 23 Jul 2001, Jani Jaakkola wrote: > > > Hmm, I'll guess I have to get my hands on some other benchmark software > > than bonnie and try it with ext2, xfs+internal log and xfs+external log. > > OK, it seems that create/delete performance on linux XFS with sw RAID is > still bad with current cvs kernel (not terrible anymore, but bad enough > that I would not put xfs with sw RAID to production use). I downloaded > bonnie++ and did some tests > > > So the RAID array is 5 times faster in pure write IO, but xfs with > internal log kills create/delete performance with IO stalls. With external > log the create/delete performance is again acceptable: > ..... > > So the sw RAID internal log performance is not fixed yet :( No performance is not 'fixed' but it is way better than it was in the earlier kernels, we had a scenario where it would just stop dead in its tracks and not make any forward progress. It is more complex to setup with the external log, but it looks like a pretty viable solution - see Tru Huynh's numbers with a raid1 journal, this config still has everything protected and is getting good numbers. Steve > > - Jani From owner-linux-xfs@oss.sgi.com Mon Jul 23 07:53:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NErsi04606 for linux-xfs-outgoing; Mon, 23 Jul 2001 07:53:54 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NErqV04587 for ; Mon, 23 Jul 2001 07:53:52 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6NEtYG17445 for ; Mon, 23 Jul 2001 17:55:35 +0300 Date: Mon, 23 Jul 2001 17:53:48 +0300 (EEST) From: Jani Jaakkola To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: <200107231443.f6NEhNB15714@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 23 Jul 2001, Steve Lord wrote: > No performance is not 'fixed' but it is way better than it was in the > earlier kernels, we had a scenario where it would just stop dead in > its tracks and not make any forward progress. Agreed. I did see that behavior with older kernels. > It is more complex to setup with the external log, but it looks like a > pretty viable solution - see Tru Huynh's numbers with a raid1 journal, > this config still has everything protected and is getting good numbers. Yes, I'm going to rebuild my RAID setup so that I have mirrored SCSI partitions for my external log (in the same SCSI disks where the RAID5 array lives, so the performance won't be optimal either, but I guess it's the best single disk failure protected setup I can manage with the hw I have). I'll post my benchmarks as soon as I get the new setup running. - Jani From owner-linux-xfs@oss.sgi.com Mon Jul 23 08:01:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NF1se05189 for linux-xfs-outgoing; Mon, 23 Jul 2001 08:01:54 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NF1iV05162 for ; Mon, 23 Jul 2001 08:01:44 -0700 Received: from chrystal-2.science.nd.edu (chrystal-2.science.nd.edu [129.74.40.3]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA02248 for ; Mon, 23 Jul 2001 08:01:24 -0700 (PDT) mail_from (matt@chrystal-2.science.nd.edu) Received: (from matt@localhost) by chrystal-2.science.nd.edu (8.11.2/8.11.2) id f6NElOZ25170 for linux-xfs@oss.sgi.com; Mon, 23 Jul 2001 09:47:24 -0500 Date: Mon, 23 Jul 2001 09:47:24 -0500 From: "Mathew A. Chrystal" To: linux-xfs@oss.sgi.com Subject: xfs bug ? Message-ID: <20010723094724.A25133@chrystal-2.science.nd.edu> Reply-To: matt@nd.edu Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi: I have been installing redhat 7.1 with the sgi-installer iso. After installation is complete and the machine boots for the first time everything is fine. When you reboot the second time thes messages start appearing: ... checking hardware touch creating '/var/lock/subsys/kudzu': unknown error 990 ... .. bringing up interface eth0 touch creating '/var/lock/subsys/network': unknown error 990 starting system logger.. there seems to be something wrong with the /var/lock/subsys directory. if you go into the subsys directory and try to make the files you get the same error 990 message. i will attach the dmesg and output from an ls on the subsys directory. ps. I am using a kickstart install and /var has its own partition. also if i umount the /var partition and run xfs_repair it fixes the problem. Matt Chrystal University of Notre Dame --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=prob Linux version 2.4.3-SGI_XFS_1.0.1 (root@linux-xfs2.americas.sgi.com) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Mon Jul 9 14:27:56 CDT 2001 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 00000000000a0000 (usable) BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 000000000ff87000 (usable) BIOS-e820: 000000000ff87000 - 000000000ffa6000 (ACPI data) BIOS-e820: 000000000ffa6000 - 0000000010000000 (reserved) BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved) found SMP MP-table at 000fe710 hm, page 000fe000 reserved twice. hm, page 000ff000 reserved twice. hm, page 00100000 reserved twice. hm, page 000f0000 reserved twice. hm, page 000f1000 reserved twice. On node 0 totalpages: 65415 zone(0): 4096 pages. zone(1): 61319 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.4 IMCR and PIC compatibility mode. OEM ID: DELL Product ID: Opti GX400 APIC at: 0x0 BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw vendor) Processors: 0 Kernel command line: auto BOOT_IMAGE=linux ro root=344 BOOT_FILE=/boot/vmlinuz-2.4.3-SGI_XFS_1.0.1 hdc=ide-scsi ide_setup: hdc=ide-scsi Initializing CPU#0 Detected 1285.364 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 2562.45 BogoMIPS Memory: 251808k/261660k available (2284k kernel code, 7424k reserved, 100k data, 232k init, 0k highmem) kdb version 1.8 by Scott Lurndal, Keith Owens. Copyright SGI, All Rights Reserved Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes) Buffer-cache hash table entries: 16384 (order: 4, 65536 bytes) Page-cache hash table entries: 65536 (order: 7, 524288 bytes) Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) VFS: Diskquotas version dquot_6.5.0 initialized CPU: Before vendor init, caps: 3febf9ff 00000000 00000000, vendor = 0 CPU: L1 I cache: 12K, L1 D cache: 8K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 3febf9ff 00000000 00000000 00000000 CPU: After generic, caps: 3febf9ff 00000000 00000000 00000000 CPU: Common caps: 3febf9ff 00000000 00000000 00000000 CPU: Intel(R) Pentium(R) 4 CPU 1300MHz stepping 07 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 0xfc0ce, last bus=2 PCI: Using configuration type 1 PCI: Probing PCI hardware Unknown bridge resource 0: assuming transparent Unknown bridge resource 2: assuming transparent PCI: Using IRQ router PIIX [8086/2440] at 00:1f.0 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.14) Starting kswapd v1.8 pty: 2048 Unix98 ptys configured block: queued sectors max/low 167194kB/55731kB, 512 slots per queue RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX4: IDE controller on PCI bus 00 dev f9 PIIX4: chipset revision 4 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:pio hda: QUANTUM FIREBALLP AS10.2, ATA DISK drive hdb: QUANTUM FIREBALLP AS10.2, ATA DISK drive hdc: SAMSUNG CDRW/DVD SM-308B, ATAPI CD/DVD-ROM drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 hda: 20066251 sectors (10274 MB) w/1902KiB Cache, CHS=1249/255/63, UDMA(100) hdb: 20066251 sectors (10274 MB) w/1902KiB Cache, CHS=1249/255/63, UDMA(100) Partition check: hda: hda1 hdb: hdb1 hdb2 hdb3 hdb4 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 Serial driver version 5.05a (2001-03-20) with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Real Time Clock Driver v1.10d md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md.c: sizeof(mdp_super_t) = 4096 autodetecting RAID arrays autorun ... ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 2048 buckets, 16Kbytes TCP: Hash tables configured (established 16384 bind 16384) Linux IP multicast router 0.06 plus PIM-SM NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Start mounting filesystem: ide0(3,68) Ending clean XFS mount for filesystem: ide0(3,68) VFS: Mounted root (xfs filesystem) readonly. Freeing unused kernel memory: 232k freed Adding Swap: 530136k swap-space (priority -1) usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb-uhci.c: $Revision: 1.251 $ time 14:45:43 Jul 9 2001 usb-uhci.c: High bandwidth mode enabled PCI: Found IRQ 11 for device 00:1f.2 PCI: Setting latency timer of device 00:1f.2 to 64 usb-uhci.c: USB UHCI at I/O 0xff80, 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 PCI: Found IRQ 9 for device 00:1f.4 PCI: Setting latency timer of device 00:1f.4 to 64 usb-uhci.c: USB UHCI at I/O 0xff60, IRQ 9 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 2 hub.c: USB hub found hub.c: 2 ports detected Start mounting filesystem: ide0(3,65) Ending clean XFS mount for filesystem: ide0(3,65) Start mounting filesystem: ide0(3,67) Starting XFS recovery on filesystem: ide0(3,67) (dev: 3/67) Ending XFS recovery on filesystem: ide0(3,67) (dev: 3/67) SCSI subsystem driver Revision: 1.00 scsi0 : SCSI host adapter emulation for IDE ATAPI devices Vendor: SAMSUNG Model: CDRW/DVD SM-308B Rev: M002 Type: CD-ROM ANSI SCSI revision: 02 Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ... SMSC Super-IO detection, now testing Ports 2F0, 370 ... 0x378: FIFO is 16 bytes 0x378: writeIntrThreshold is 8 0x378: readIntrThreshold is 8 0x378: PWord is 8 bits 0x378: Interrupts are ISA-Pulses 0x378: ECP port cfgA=0x14 cfgB=0x40 0x378: ECP settings irq= dma= parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,EPP,ECP] parport0: irq 7 detected parport0: cpp_daisy: aa5500ff(08) parport0: assign_addrs: aa5500ff(08) parport0: cpp_daisy: aa5500ff(08) parport0: assign_addrs: aa5500ff(08) xfs_create looping, dir ino 0x40089, ino 0x40092, ide0(3,67) ip_conntrack (2044 buckets, 16352 max) PCI: Found IRQ 11 for device 02:0c.0 3c59x.c:LK1.1.13 27 Jan 2001 Donald Becker and others. http://www.scyld.com/network/vortex.html See Documentation/networking/vortex.txt eth0: 3Com PCI 3c905C Tornado at 0xec80, 00:b0:d0:f5:1a:99, IRQ 11 product code 0000 rev 00.3 date 07-16-104 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. MII transceiver found at address 24, status 782d. Enabling bus-master transmits and whole-frame receives. eth0: scatter/gather disabled. h/w checksums enabled eth0: using NWAY device table, not 8 xfs_create looping, dir ino 0x40089, ino 0x40093, ide0(3,67) xfs_create looping, dir ino 0x140081, ino 0x14008b, ide0(3,67) xfs_create looping, dir ino 0x140081, ino 0x14008c, ide0(3,67) xfs_create looping, dir ino 0x40089, ino 0x40095, ide0(3,67) xfs_create looping, dir ino 0x40089, ino 0x40096, ide0(3,67) xfs_create looping, dir ino 0x40089, ino 0x40098, ide0(3,67) xfs_create looping, dir ino 0x40089, ino 0x40099, ide0(3,67) xfs_create looping, dir ino 0x40089, ino 0x4009a, ide0(3,67) xfs_create looping, dir ino 0x40089, ino 0x400a9, ide0(3,67) Intel 810 + AC97 Audio, version 0.02, 14:45:28 Jul 9 2001 PCI: Found IRQ 10 for device 00:1f.5 PCI: The same IRQ used for device 00:1f.3 PCI: Setting latency timer of device 00:1f.5 to 64 i810: Intel ICH2 found at IO 0xdc40 and 0xd800, IRQ 10 ac97_codec: AC97 Audio codec, id: 0x4144:0x5360 (Unknown) i810_audio: setting clocking to 41319 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=mprob ls: kudzu: No such file or directory ls: network: No such file or directory ls: syslog: No such file or directory ls: portmap: No such file or directory ls: nfslock: No such file or directory ls: random: No such file or directory ls: netfs: No such file or directory ls: apmd: No such file or directory ls: local: No such file or directory anacron autofs gpm linuxconf sendmail xfs atd crond keytable mprob sshd xinetd --d6Gm4EdcadzBjdND-- From owner-linux-xfs@oss.sgi.com Mon Jul 23 08:27:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NFRs806783 for linux-xfs-outgoing; Mon, 23 Jul 2001 08:27:54 -0700 Received: from porsta.cs.Helsinki.FI (root@porsta.cs.Helsinki.FI [128.214.48.124]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NFRqV06764 for ; Mon, 23 Jul 2001 08:27:52 -0700 Received: from hallikari.cs.Helsinki.FI (IDENT:jjaakkol@hallikari.cs.Helsinki.FI [128.214.11.27]) by porsta.cs.Helsinki.FI (8.11.3/8.11.3) with ESMTP id f6NFTWG20603 for ; Mon, 23 Jul 2001 18:29:33 +0300 Date: Mon, 23 Jul 2001 18:27:46 +0300 (EEST) From: Jani Jaakkola To: "linux-xfs@oss.sgi.com" Subject: Re: nfs/local performance with software raid5 and xfs and SMP In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 23 Jul 2001, Jani Jaakkola wrote: > I'll post my benchmarks as soon as I get the new setup running. Allright, now I did get very good benchmarks with external log, while the RAID resync is still running: -----snip----- Version 1.01b ------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 other-fs 2G 10161 97 42055 37 7527 8 10800 89 131575 82 317.0 1 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 2428 66 +++++ +++ 2192 57 2220 58 +++++ +++ 1510 43 -----snip----- - Jani From owner-linux-xfs@oss.sgi.com Mon Jul 23 08:29:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NFTxO07057 for linux-xfs-outgoing; Mon, 23 Jul 2001 08:29:59 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NFTuV07034 for ; Mon, 23 Jul 2001 08:29:57 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id RAA10513; Mon, 23 Jul 2001 17:29:54 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id RAA22619; Mon, 23 Jul 2001 17:29:54 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id E52A057306; Mon, 23 Jul 2001 17:39:45 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 13E1825835; Mon, 23 Jul 2001 17:47:34 +0200 (CEST) Message-ID: <3B5C42DE.607AF347@ch.sauter-bc.com> Date: Mon, 23 Jul 2001 17:29:34 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: matt@nd.edu Cc: linux-xfs@oss.sgi.com Subject: Re: xfs bug ? References: <20010723094724.A25133@chrystal-2.science.nd.edu> Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Mathew A. Chrystal" schrieb: > > Hi: > > I have been installing redhat 7.1 with the sgi-installer iso. After > installation is complete and the machine boots for the first time > everything is fine. When you reboot the second time thes messages start > appearing: > ... > checking hardware > touch creating '/var/lock/subsys/kudzu': unknown error 990 > ... > .. > bringing up interface eth0 > touch creating '/var/lock/subsys/network': unknown error 990 > starting system logger.. > there seems to be something wrong with the /var/lock/subsys directory. > > if you go into the subsys directory and try to make the files you get > the same error 990 message. > > i will attach the dmesg and output from an ls on the subsys directory. > > ps. I am using a kickstart install and /var has its own partition. > also if i umount the /var partition and run xfs_repair it fixes the > problem. > > Matt Chrystal > University of Notre Dame > > ------------------------------------------------------------------------ > > probName: prob > Type: Plain Text (text/plain) > > mprobName: mprob > Type: Plain Text (text/plain) Hi, I was having filesystem corruption on DELL Precision WS when using more than one disk, no matter whether in RAID configuration or just mounting different partitions on both disks. Can you try two things: 1) What does rpm -Va say. Do you see lot of corrupt files? 2) Can you remove the second drive and install on just the first drive? -Simon From owner-linux-xfs@oss.sgi.com Mon Jul 23 08:38:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NFcOQ07761 for linux-xfs-outgoing; Mon, 23 Jul 2001 08:38:24 -0700 Received: from zok.corp.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NFcLV07740 for ; Mon, 23 Jul 2001 08:38:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6NFgtm15431 for ; Mon, 23 Jul 2001 08:42:55 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2503056; Mon, 23 Jul 2001 10:36:59 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA25378; Mon, 23 Jul 2001 10:36:59 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NFbAv16292; Mon, 23 Jul 2001 10:37:10 -0500 Message-Id: <200107231537.f6NFbAv16292@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Simon Matter cc: matt@nd.edu, linux-xfs@oss.sgi.com Subject: Re: xfs bug ? In-Reply-To: Message from Simon Matter of "Mon, 23 Jul 2001 17:29:34 +0200." <3B5C42DE.607AF347@ch.sauter-bc.com> Date: Mon, 23 Jul 2001 10:37:10 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > "Mathew A. Chrystal" schrieb: > > > > Hi: > > > > I have been installing redhat 7.1 with the sgi-installer iso. After > > installation is complete and the machine boots for the first time > > everything is fine. When you reboot the second time thes messages start > > appearing: > > ... > > checking hardware > > touch creating '/var/lock/subsys/kudzu': unknown error 990 > > ... > > .. > > bringing up interface eth0 > > touch creating '/var/lock/subsys/network': unknown error 990 > > starting system logger.. > > there seems to be something wrong with the /var/lock/subsys directory. > > > > if you go into the subsys directory and try to make the files you get > > the same error 990 message. > > > > i will attach the dmesg and output from an ls on the subsys directory. > > > > ps. I am using a kickstart install and /var has its own partition. > > also if i umount the /var partition and run xfs_repair it fixes the > > problem. > > > > Matt Chrystal > > University of Notre Dame > > > > ------------------------------------------------------------------------ > > > > probName: prob > > Type: Plain Text (text/plain) > > > > mprobName: mprob > > Type: Plain Text (text/plain) > > Hi, > I was having filesystem corruption on DELL Precision WS when using > more than one disk, no matter whether in RAID configuration or > just mounting different partitions on both disks. > Can you try two things: > > 1) What does rpm -Va say. Do you see lot of corrupt files? > 2) Can you remove the second drive and install on just the > first drive? > > -Simon > I should add that error 990 is EFSCORRUPTED which usually means XFS has detected a metadata problem on the disk and has shut it down. There should have been a console message when this started, I did not see one in the output Mathew sent. The xfs_create looping error should not be happening either, this is another inconsistency between metadata in different locations - a lookup on a directory is failing to find an entry in a directory, but the create code says it is there. At this point I would distrust the hardware, Simon's suggestion would be a good one. Steve From owner-linux-xfs@oss.sgi.com Mon Jul 23 09:18:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NGIE510067 for linux-xfs-outgoing; Mon, 23 Jul 2001 09:18:14 -0700 Received: from pipt.oz.cc.utah.edu (jdr1529@pipt.oz.cc.utah.edu [155.99.2.7]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NGIDV10048 for ; Mon, 23 Jul 2001 09:18:13 -0700 Received: from localhost (jdr1529@localhost) by pipt.oz.cc.utah.edu (8.9.2/8.9.2) with ESMTP id KAA21323; Mon, 23 Jul 2001 10:17:47 -0600 (MDT) Date: Mon, 23 Jul 2001 10:17:46 -0600 (MDT) From: james rich To: Steve Lord cc: Federico Sevilla III , Linux XFS Mailing List Subject: Re: Performance of near-full filesystems In-Reply-To: <200107221635.f6MGZ0r09257@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 22 Jul 2001, Steve Lord wrote: > > On Sun, 22 Jul 2001 at 08:03, Steve Lord wrote: > > > If you create a large number of files in XFS, inodes are allocated > > > dynamically for them. If you remove all the files, the inodes are not > > > > Yes, this is what I was referring to. I was under the impression that this > > was "bad", though, and one effectively "lost space". Are inodes allocated > > dynamically for large files different from those allocated dynamically for > > a bunch of small files? Meaning, if inodes are allocated for a large file, > > There is no distinction in XFS, an inode is an inode, no matter what it > is used for, they are all the same size (default 256 bytes on disk) and > they are allocated in groups of 32 by default (2 filesystem blocks worth). I think the question is about density here. Two large files create two inodes in a certain amount of disk. If those files are deleted does xfs create more inodes in that same amount of disk if small files are placed there? Or are there large holes? James Rich james.rich@m.cc.utah.edu From owner-linux-xfs@oss.sgi.com Mon Jul 23 09:26:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NGQeY10302 for linux-xfs-outgoing; Mon, 23 Jul 2001 09:26:40 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NGQaV10281 for ; Mon, 23 Jul 2001 09:26:36 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id SAA192825 for ; Mon, 23 Jul 2001 18:26:25 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2504271; Mon, 23 Jul 2001 11:25:17 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA67042; Mon, 23 Jul 2001 11:25:17 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NGPSK16460; Mon, 23 Jul 2001 11:25:28 -0500 Message-Id: <200107231625.f6NGPSK16460@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: james rich cc: Steve Lord , Federico Sevilla III , Linux XFS Mailing List Subject: Re: Performance of near-full filesystems In-Reply-To: Message from james rich of "Mon, 23 Jul 2001 10:17:46 MDT." Date: Mon, 23 Jul 2001 11:25:28 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Sun, 22 Jul 2001, Steve Lord wrote: > > > > On Sun, 22 Jul 2001 at 08:03, Steve Lord wrote: > > > > If you create a large number of files in XFS, inodes are allocated > > > > dynamically for them. If you remove all the files, the inodes are not > > > > > > Yes, this is what I was referring to. I was under the impression that thi > s > > > was "bad", though, and one effectively "lost space". Are inodes allocated > > > dynamically for large files different from those allocated dynamically fo > r > > > a bunch of small files? Meaning, if inodes are allocated for a large file > , > > > > There is no distinction in XFS, an inode is an inode, no matter what it > > is used for, they are all the same size (default 256 bytes on disk) and > > they are allocated in groups of 32 by default (2 filesystem blocks worth). > > I think the question is about density here. Two large files create two > inodes in a certain amount of disk. If those files are deleted does xfs > create more inodes in that same amount of disk if small files are placed > there? Or are there large holes? OK, where the inodes live and where the file data lives are different things. As I mentioned in previous email, the filesystem is split into allocation groups, each allocation group is self contained when it comes to free space and free inodes. Within each allocation group free space is indexed as two btrees of extents. One is organized by disk location, one is organized by size of the space, the tree which is used for allocation depends on what you want, next to some other space, or of a certain size. As space is freed it is placed back into the tree, should it be next to other free space the two extents are coalesced into a single extent. Once space is released from a file, it is available for anyone else to use. If all the free space happens to be in one large chunk and we only want a small part of it we just use one end of the free space. So yes, there are large holes, but these holes can be carved up into lots of small chunks should the need arise, and in turn these small chunks can be put back together into a large chunk of free space should they all be freed again. Steve > > James Rich > james.rich@m.cc.utah.edu From owner-linux-xfs@oss.sgi.com Mon Jul 23 09:48:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NGmYJ10959 for linux-xfs-outgoing; Mon, 23 Jul 2001 09:48:34 -0700 Received: from roujin.gargoylecc.com (roujin.gargoylecc.com [65.100.85.34]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NGmWV10939 for ; Mon, 23 Jul 2001 09:48:32 -0700 Received: from roujin.gargoylecc.com ([65.100.85.34] ident=ringram) by roujin.gargoylecc.com with esmtp (Exim 3.13 #1) id 15Ojte-0002UM-00 for linux-xfs@oss.sgi.com; Mon, 23 Jul 2001 11:53:34 -0600 Date: Mon, 23 Jul 2001 11:53:34 -0600 (MDT) From: Russel Ingram To: Subject: Debian install on XFS? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I know a while back someone posted that there was an instal disk image available for installing Debian on XFS. Does anyone know if it has been updated for the 1.0.1 XFS or if it will be? Russ -- Russ Ingram Gargoyle Computer Consulting (307)742-1361 www.gargoylecc.com From owner-linux-xfs@oss.sgi.com Mon Jul 23 10:13:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NHDJI11729 for linux-xfs-outgoing; Mon, 23 Jul 2001 10:13:19 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NHDHV11710 for ; Mon, 23 Jul 2001 10:13:17 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6NHCvNe047842; Mon, 23 Jul 2001 12:12:57 -0500 (CDT) Message-ID: <3B5C5AB4.30507@thebarn.com> Date: Mon, 23 Jul 2001 12:11:16 -0500 From: Russell Cattelan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: Steve Lord CC: Alan Eldridge , XFS list Subject: Re: Linux Magazine 7/2001 References: <200107211421.f6LELoR01055@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: >>The SGI XFS Release made "Zonker's Product Picks" in the July issue of LINUX >>Magazine. There's a nice little product blurb and a really cool "sgi XFS >>RELEASE 1.0" graphic. >> > >Ah ha, the infamous 1.0 logo, which marketing insisted we remove as it >was not approved. They will be pleased ;-). If you have a copy of this >save it for posterity, it may become a collectors item! > or "accidently" click :-) http://oss.sgi.com/projects/xfs/images/XFSRelease1.0.jpg > From owner-linux-xfs@oss.sgi.com Mon Jul 23 13:10:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NKAQJ01029 for linux-xfs-outgoing; Mon, 23 Jul 2001 13:10:26 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NKAMX01010 for ; Mon, 23 Jul 2001 13:10:23 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id LAA06231 for ; Mon, 23 Jul 2001 11:51:17 -0700 (PDT) mail_from (roehrich@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2502487 for ; Mon, 23 Jul 2001 13:52:22 -0500 (CDT) Received: from slobber.americas.sgi.com (slobber.americas.sgi.com [128.162.187.52]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA01970 for ; Mon, 23 Jul 2001 13:52:22 -0500 (CDT) Received: from slobber.americas.sgi.com by slobber.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) via ESMTP id NAA01277; Mon, 23 Jul 2001 13:52:21 -0500 (CDT) Message-Id: <200107231852.NAA01277@slobber.americas.sgi.com> To: linux-xfs@oss.sgi.com Subject: Re: TAKE - static libs Date: Mon, 23 Jul 2001 13:52:21 -0500 From: Dean Roehrich Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >From: Nathan Scott >Installing the .la and .a files into /usr/lib, in spite of libtool, >seems to work just fine. No, it doesn't. Here's xfs_fsr, built static: /usr/bin/libtool --mode=link gcc -o xfs_fsr -static xfs_fsr.o \ /usr/lib/libhandle.la /usr/lib/libattr.la gcc -o xfs_fsr xfs_fsr.o /lib/libhandle.a /lib/libattr.a gcc: /lib/libhandle.a: No such file or directory gcc: /lib/libattr.a: No such file or directory I think for now we should leave it as you have it with your last mod, with the pieces split between /lib and /usr/lib and the rpath pointing to /lib where the shared libs are located. It's apparently rare that any of us tries to link these things with the static libs, and in that case we can do it without libtool. Add this to our growing "You've-got-to-be-kidding" list for libtool... Dean From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:16:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMGOa13967 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:16:24 -0700 Received: from mail.locasite.com.br ([200.183.0.21]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMGL713941 for ; Mon, 23 Jul 2001 15:16:21 -0700 Received: (qmail 12332 invoked by uid 1001); 23 Jul 2001 22:14:31 -0000 Received: from unknown (HELO pegasus.stat2.com.br) (200.228.48.171) by 200.183.0.20 with SMTP; 23 Jul 2001 22:14:31 -0000 Content-Type: text/plain; charset="iso-8859-1" From: =?iso-8859-1?q?Fl=E1vio=20Brito?= Reply-To: flavio@stat.com.br To: linux-xfs@oss.sgi.com Subject: depmod problem Date: Mon, 23 Jul 2001 19:18:53 -0300 X-Mailer: KMail [version 1.2] Organization: Stat Consultoria MIME-Version: 1.0 Message-Id: <01072319185300.02089@pegasus.stat2.com.br> Content-Transfer-Encoding: 8bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Dear Support, I installed the a new XFS System CD - Workstation option with GNOME, but now when it starts these messages appears : Please let me know if you have a solution Thanks Flávio Bito Rio de Janeiro - Brasil -------------------------------------------------------------------------------- depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/block/paride/paride.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/joystick/db9.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/joystick/gamecon.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/joystick/iforce.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/joystick/turbografx.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/lp.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/pcmcia/serial_cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/char/ppdev.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/i2c/i2c-philips-par.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/ide/ide-cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/isdn/avmb1/avm_cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/isdn/hisax/elsa_cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/isdn/hisax/sedlbauer_cs.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/radio/miropcm20.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/bw-qcam.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/c-qcam.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/cpia_pp.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/cpia_usb.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/i2c-parport.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/tvmixer.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/media/video/w9966.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/message/fusion/mptscsih.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/message/i2o/i2o_scsi.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/net/appletalk/ipddp.o depmod: *** Unresolved symbols in /lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/net/bsd_comp.o From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:21:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMLN614617 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:21:23 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMLM714586 for ; Mon, 23 Jul 2001 15:21:22 -0700 Received: from octobrx.com (ns.octobrx.com [63.196.111.2]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via SMTP id OAA07376 for ; Mon, 23 Jul 2001 14:00:24 -0700 (PDT) mail_from (zoltan@octobrx.com) From: zoltan@octobrx.com Received: (qmail 604 invoked by uid 1062); 23 Jul 2001 20:53:03 -0000 Date: Mon, 23 Jul 2001 13:53:03 -0700 To: Russel Ingram Cc: linux-xfs@oss.sgi.com Subject: Re: Debian install on XFS? Message-ID: <20010723135303.A29681@numb.octobrx.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.12i In-Reply-To: ; from ringram@gargoylecc.com on Mon, Jul 23, 2001 at 11:53:34AM -0600 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk No, I wont be updating the install any time soon. On Mon, Jul 23, 2001 at 11:53:34AM -0600, Russel Ingram wrote: > I know a while back someone posted that there was an instal disk image > available for installing Debian on XFS. Does anyone know if it has been > updated for the 1.0.1 XFS or if it will be? > > Russ > -- > Russ Ingram > Gargoyle Computer Consulting > (307)742-1361 > www.gargoylecc.com > From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:21:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMLQs14650 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:21:26 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMLO714629 for ; Mon, 23 Jul 2001 15:21:24 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA07676 for ; Mon, 23 Jul 2001 13:43:38 -0700 (PDT) mail_from (knuffie@xs4all.nl) Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA12748; Mon, 23 Jul 2001 22:43:44 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA16786; Mon, 23 Jul 2001 22:43:44 +0200 (CEST) Date: Mon, 23 Jul 2001 22:43:44 +0200 (CEST) From: Seth Mos To: Russell Cattelan cc: Steve Lord , Alan Eldridge , XFS list Subject: Re: Linux Magazine 7/2001 In-Reply-To: <3B5C5AB4.30507@thebarn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 23 Jul 2001, Russell Cattelan wrote: > Steve Lord wrote: > > >>The SGI XFS Release made "Zonker's Product Picks" in the July issue of LINUX > >>Magazine. There's a nice little product blurb and a really cool "sgi XFS > >>RELEASE 1.0" graphic. > >> > > > >Ah ha, the infamous 1.0 logo, which marketing insisted we remove as it > >was not approved. They will be pleased ;-). If you have a copy of this > >save it for posterity, it may become a collectors item! > > > or "accidently" click :-) > http://oss.sgi.com/projects/xfs/images/XFSRelease1.0.jpg We should make it a large logo for booting the pc during setup or afterwards. Maybe bring out a kernel with this logo and a progress bar during bootup. I really like that logo. Cheers Seth From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:31:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMVgE15977 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:31:42 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMVf715954 for ; Mon, 23 Jul 2001 15:31:41 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6NMZBU10881 for ; Mon, 23 Jul 2001 15:35:12 -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 IAA02842; Tue, 24 Jul 2001 08:29:58 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id IAA58393; Tue, 24 Jul 2001 08:29:37 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107240829.ZM231748@wobbly.melbourne.sgi.com> Date: Tue, 24 Jul 2001 08:29:35 +1000 In-Reply-To: Danny Cox "Re: Anyone using XFS ACLs? (fwd)" (Jul 23, 7:54am) References: <200107201833.f6KIX7H08390@jen.americas.sgi.com> <10107231743.ZM221213@wobbly.melbourne.sgi.com> <3B5C1086.230C3AAA@mindspring.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: dcox@connex.com Subject: Re: Anyone using XFS ACLs? (fwd) Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Danny, On Jul 23, 7:54am, Danny Cox wrote: > Subject: Re: Anyone using XFS ACLs? (fwd) > > ... > > - trying to understand your '-D_FILE_OFFSET_BITS=64' problem - > > I think we do need this, I just can't understand how this was > > failing for you (can you give more details?) - I have a rh6.2 > > system here and it seems to work for the (limited) test cases > > we tried. > > Okay, my /usr/include/dirent.h includes , in which I > see: > > struct dirent > { > #ifndef __USE_FILE_OFFSET64 > __ino_t d_ino; > __off_t d_off; > #else > __ino64_t d_ino; > __off64_t d_off; > #endif > unsigned short int d_reclen; > unsigned char d_type; > char d_name[256]; /* We must not include limits.h! */ > }; > > Compiling chacl.c WITH -D_FILE_OFFSET_BITS=64 gets me file names of > "". Using gdb, I can see "..", and later on, the other file names. > Compiling WITHOUT -D_FILE_OFFSET_BITS=64 gets me proper file names. > Searching /usr/include for "__USE_FILE_OFFSET64" yields (among others), > "features.h". It is features.h that contains the snippet: > > #if defined _FILE_OFFSET_BITS && _FILE_OFFSET_BITS == 64 > # define __USE_FILE_OFFSET64 1 > #endif > > Thus, I conclude that chacl.c is using a struct dirent whose size > doesn't match (is larger than) what readdir(3) is returning, no? > There's another piece to the puzzle you may have missed - the readdir syscall gets automagically remapped to readdir64 with this flag ... from a very quick scan through libc, we should be coming into the kernel via the getdents64 syscall, and we should be using the right-sized data structure. Do you have a reproducible test case under rh 6.2 which shows the problem, so I could try it out? I can't get this to fail on any machine, with a variety of distributions. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:32:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMWNe16099 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:32:23 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMWM716079 for ; Mon, 23 Jul 2001 15:32:22 -0700 Received: from mustang.centralnet.ch (mustang.centralnet.ch [193.135.146.12]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id NAA08443 for ; Mon, 23 Jul 2001 13:44:41 -0700 (PDT) mail_from (dv@vollmann.ch) Received: from vollmann.ch (luz2.centralnet.ch [193.246.195.2]) by mustang.centralnet.ch (8.9.3/8.9.3) with ESMTP id WAA163263 for ; Mon, 23 Jul 2001 22:44:45 +0200 (MES) Received: from two.vollmann.ch (localhost [127.0.0.1]) by vollmann.ch (8.8.6/8.8.5) with SMTP id UAA01700; Mon, 23 Jul 2001 20:42:42 GMT Message-ID: <3B5C8C42.3100875D@vollmann.ch> Date: Mon, 23 Jul 2001 20:42:42 +0000 From: Detlef Vollmann Organization: vollmann engineering gmbh X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.14-5.0 i586) MIME-Version: 1.0 To: XFS list Subject: Official patch against 2.4.7? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Are there any plans to release an official patch of XFS 1.0.1 against kernel 2.4.7 in the next few weeks? Detlef -- Detlef Vollmann vollmann engineering gmbh Tel: +41-41-4120911 P.O. Box 5106 Fax: +41-41-4120912 CH-6000 Luzern 5 / Switzerland eMail: dv@vollmann.ch From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:49:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMnDB18749 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:49:13 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMnA718727 for ; Mon, 23 Jul 2001 15:49:10 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id AAA209565 for ; Tue, 24 Jul 2001 00:48:57 +0200 (CEST) mail_from (dxm@snort.melbourne.sgi.com) Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id IAA33837; Tue, 24 Jul 2001 08:47:46 +1000 (EST) Message-Id: <200107232247.IAA33837@snort.melbourne.sgi.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Justin@Linux-TechSupport.Com cc: linux-xfs@oss.sgi.com Subject: Re: FW: log mount/recovery failed In-reply-to: Your message of "Mon, 23 Jul 2001 06:37:13 -0400." <000a01c11363$7387e360$0101a8c0@enterprise> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Jul 2001 08:47:45 +1000 From: Daniel Moore Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Justin Hamilton" writes: => Here is the xfs_logprint: => => [root@Voyager /]# xfs_logprint /dev/vg04/lv_movies => xfs_logprint: => data device: 0x3a07 => log device: 0x3a07 daddr: 10485792 length: 9600 => => Header 0xc wanted 0xfeedbabe => ********************************************************************** => * ERROR: header cycle=12 block=1463 * => ********************************************************************** => Bad log record header => => So somehow, it looks like the log is getting clobbered. => => Before I run the xfs_repair, is there any other info that will be useful => to ensuring this get fixed? Well actually xfs_logprint without '-t' will sometimes do this because the first block of the log doesn't always look like a valid log record (it can be the tail end of a record that started right at the end of the log - hence no 0xfeedbabe). So this doesn't really prove anything. I'd have to hand this off to someone else on the list at this point - I don't have time to follow though. But I can refer you to a comment from Steve: lord@sgi.com said: => There is definitely a problem with the log on raid5 right now, we did => not change anything on our end, so it looks like the underlying code => may have broken things. We are looking into this. As for performance, => the Are you using raid5? if so, this might explain it. If not, it might anyway. I've never seen this kind of symptom before. ----------------------------------------------------- Daniel Moore dxm@sgi.com R&D Software Engineer Phone: +61-3-98348209 SGI Performance Tools Group Fax: +61-3-98132378 ----------------------------------------------------- From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:54:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMsBl19721 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:54:11 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMs9719690 for ; Mon, 23 Jul 2001 15:54:09 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA03874 for ; Mon, 23 Jul 2001 15:54:02 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2509522; Mon, 23 Jul 2001 17:52:50 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA19686; Mon, 23 Jul 2001 17:52:50 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NMqwq22877; Mon, 23 Jul 2001 17:52:58 -0500 Message-Id: <200107232252.f6NMqwq22877@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Detlef Vollmann cc: XFS list Subject: Re: Official patch against 2.4.7? In-Reply-To: Message from Detlef Vollmann of "Mon, 23 Jul 2001 20:42:42 -0000." <3B5C8C42.3100875D@vollmann.ch> Date: Mon, 23 Jul 2001 17:52:58 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Are there any plans to release an official patch of XFS 1.0.1 > against kernel 2.4.7 in the next few weeks? > > Detlef > > -- > Detlef Vollmann > vollmann engineering gmbh Tel: +41-41-4120911 > P.O. Box 5106 Fax: +41-41-4120912 > CH-6000 Luzern 5 / Switzerland eMail: dv@vollmann.ch Well, it depends on what you call 1.0.1 .... Almost all the changes we have made to the development tree since the 1.0.1 release have been for one of three things: 1) to fix a bug 2) to move the port forwards to the next kernel version 3) to reduce the footprint of xfs changes in the main kernel code Unfortunately, items 2 and 3 got very tightly intertwined with each other which makes it difficult to move the code up to a new release level without bringing along other changes. So realistically speaking, all we can offer are the patches in this directory: ftp://oss.sgi.com/projects/xfs/download/patches/ There is a 2.4.7 patch called patch-2.4.7-xfs-2001-07-22.bz2 I am currently looking to two problems with this code, one of which I am sure is present in 1.0.1, one which may not be. o xfs_fsr will leave busy inodes in the filesystem, this is almost certainly in 1.0.1 o raid5 filesystems have log problems - the filesystem may not mount without running xfs_repair first, I am about to check in a fix for this. If I can find the script to regen the patch I will push out a new version. Now that there is another dot release we may do some more extensive testing on it than the pre series, but given the changes I am not sure it is really 1.0.1 any more. Steve From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:56:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMuCr20132 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:56:12 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMuA720101 for ; Mon, 23 Jul 2001 15:56:10 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA02261 for ; Mon, 23 Jul 2001 15:56:02 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2496815; Mon, 23 Jul 2001 17:54:51 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA97059; Mon, 23 Jul 2001 17:54:50 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6NMsxK22896; Mon, 23 Jul 2001 17:54:59 -0500 Message-Id: <200107232254.f6NMsxK22896@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Daniel Moore cc: Justin@linux-techsupport.com, linux-xfs@oss.sgi.com Subject: Re: FW: log mount/recovery failed In-Reply-To: Message from Daniel Moore of "Tue, 24 Jul 2001 08:47:45 +1000." <200107232247.IAA33837@snort.melbourne.sgi.com> Date: Mon, 23 Jul 2001 17:54:59 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > I'd have to hand this off to someone else on the list at this point - > I don't have time to follow though. But I can refer you to a comment from > Steve: > > lord@sgi.com said: > => There is definitely a problem with the log on raid5 right now, we did > => not change anything on our end, so it looks like the underlying code > => may have broken things. We are looking into this. As for performance, > => the > > Are you using raid5? if so, this might explain it. If not, it might anyway. > I've never seen this kind of symptom before. >From the device I assumed this to be lvm, so the raid5 thing does not apply here. Steve > > ----------------------------------------------------- > Daniel Moore dxm@sgi.com > R&D Software Engineer Phone: +61-3-98348209 > SGI Performance Tools Group Fax: +61-3-98132378 > ----------------------------------------------------- > > From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:59:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMxBj20644 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:59:11 -0700 Received: from vertigo.incyte.com (master.incyte.com [198.31.37.253]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMx9720624 for ; Mon, 23 Jul 2001 15:59:09 -0700 Received: from vertigo.incyte.com (wfrancis@localhost) by vertigo.incyte.com (8.11.0/8.11.0) with ESMTP id f6NMwvR01406; Mon, 23 Jul 2001 15:58:57 -0700 Message-Id: <200107232258.f6NMwvR01406@vertigo.incyte.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Steve Lord cc: Simon Matter , matt@nd.edu, linux-xfs@oss.sgi.com Subject: Re: xfs bug ? In-Reply-To: Message from Steve Lord of "Mon, 23 Jul 2001 10:37:10 CDT." <200107231537.f6NFbAv16292@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 23 Jul 2001 15:58:56 -0700 From: Will Francis Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I should add that error 990 is EFSCORRUPTED which usually means XFS has > detected a metadata problem on the disk and has shut it down. There should > have been a console message when this started, I did not see one in the > output Mathew sent. > > The xfs_create looping error should not be happening either, this is another > inconsistency between metadata in different locations - a lookup on a > directory is failing to find an entry in a directory, but the create code > says it is there. > > At this point I would distrust the hardware, Simon's suggestion would be > a good one. I think it's a bug with XFS and kickstart. I've been playing around with it extensively and have come across it. If you do a xfsrepair on the partition, it looks clean and then you can mount it without a problem. All that said, I've been changing and tweaking my kickstart script lots over the last two weeks and somewhere along the way the problem went away. Try changing your partitions as defined in the kickstart file. For grins, try these and see if the problem reappears: part / --size 350 --onprimary=1 part swap --size 256 part /usr --size 1000 --grow part /kickstart --size 2000 (I think I gave up trying to create a separate /var partition at this point). It's not always the /var partition though, since in one of the iterations of this it had the problem on the /kickstart partition. Remember when I first wrote in on the bug about not being able to create a /usr/local/net partition (it's been fixed in an update file just fine, but I don't have time to patch my current install) and I wrote I had similar problems with my /boot partition? I never got back to you, but it was this problem. It turned out to be a dissimilar problem to the /usr/local/net one, but a definite bug. lemme know how it goes. I'm quite certain it's not your hardware Will From owner-linux-xfs@oss.sgi.com Mon Jul 23 15:59:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NMxsn20806 for linux-xfs-outgoing; Mon, 23 Jul 2001 15:59:54 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NMxqO20775 for ; Mon, 23 Jul 2001 15:59:53 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id PAA11101 for ; Mon, 23 Jul 2001 15:59:39 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2508078 for ; Mon, 23 Jul 2001 17:58:34 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA13812 for ; Mon, 23 Jul 2001 17:58:34 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6NMwgk22946; Mon, 23 Jul 2001 17:58:42 -0500 Message-Id: <200107232258.f6NMwgk22946@jen.americas.sgi.com> Date: Mon, 23 Jul 2001 17:58:42 -0500 Subject: TAKE - fix raid5 journal problems Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Backing out an optimization, this code appears to make raid5 misbehave and fill the log with garbage. This caused recovery to fail, and sometimes a clean mount to fail. I am unable to replicate these problems once the code is removed. There will be a performance impact from this, but I am not sure how much. Hopefully in the long term we can find what is going wrong at the md layer and put this optimization back again. Steve p.s. for those of you not following the discussion recently, the best performance for raid5 is an external log on a non-raid5 device, raid1 if you want to maintain the backup copy of the data. Date: Mon Jul 23 15:54:45 PDT 2001 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:99431a linux/fs/pagebuf/page_buf.c - 1.95 - Backing out the change which made pagebuf do larger I/O on md devices in some cases. This will increase the cpu overhead in this case, but fix the log on these devices which was broken. From owner-linux-xfs@oss.sgi.com Mon Jul 23 16:06:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6NN69l22062 for linux-xfs-outgoing; Mon, 23 Jul 2001 16:06:09 -0700 Received: from mail.ocs.com.au (ppp0.ocs.com.au [203.34.97.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6NN66O22039 for ; Mon, 23 Jul 2001 16:06:06 -0700 Received: (qmail 21034 invoked from network); 23 Jul 2001 23:06:02 -0000 Received: from ocs3.ocs-net (192.168.255.3) by mail.ocs.com.au with SMTP; 23 Jul 2001 23:06:02 -0000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: flavio@stat.com.br cc: linux-xfs@oss.sgi.com Subject: Re: depmod problem In-reply-to: Your message of "Mon, 23 Jul 2001 19:18:53 -0300." <01072319185300.02089@pegasus.stat2.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Jul 2001 09:06:01 +1000 Message-ID: <19093.995929561@ocs3.ocs-net> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, 23 Jul 2001 19:18:53 -0300, Fl vio Brito wrote: >I installed the a new XFS System CD - Workstation option with GNOME, but now >when it starts these messages appears : >depmod: *** Unresolved symbols in >/lib/modules/2.4.3-SGI_XFS_1.0.1/kernel/drivers/block/paride/paride.o What does depmod -ae (as root) report? From owner-linux-xfs@oss.sgi.com Mon Jul 23 17:21:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O0LPk30138 for linux-xfs-outgoing; Mon, 23 Jul 2001 17:21:25 -0700 Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O0LNO30113 for ; Mon, 23 Jul 2001 17:21:23 -0700 Received: from thebarn.com ([63.231.179.33]) by lips.borg.umn.edu (8.12.0.Beta5/8.12.0.Beta5) with ESMTP id f6O0LKNe050392; Mon, 23 Jul 2001 19:21:20 -0500 (CDT) Message-ID: <3B5CBF17.6090409@thebarn.com> Date: Mon, 23 Jul 2001 19:19:35 -0500 From: Russell Cattelan User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010713 X-Accept-Language: en-us MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: TAKE - fix raid5 journal problems References: <200107232258.f6NMwgk22946@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Aggh, sorry I didn't notice this sooner.... haven't had much of a change to look at all the takes lately. I messed around quite a bit at one point trying to convince MD to take full page requests, but always eventually end up a with a corrupted log. If I remember right one of the log sectors would end up on a sector +1 to where is suppose to be. I finally gave up since I wasn't able to measure much performance difference, but I did have a limited # of fc disks so no idea if that will hold true for larger stripes. Steve Lord wrote: >Backing out an optimization, this code appears to make raid5 misbehave and >fill the log with garbage. This caused recovery to fail, and sometimes a >clean mount to fail. I am unable to replicate these problems once the code >is removed. There will be a performance impact from this, but I am not >sure how much. Hopefully in the long term we can find what is going wrong >at the md layer and put this optimization back again. > >Steve > >p.s. for those of you not following the discussion recently, the best >performance for raid5 is an external log on a non-raid5 device, raid1 >if you want to maintain the backup copy of the data. > > > >Date: Mon Jul 23 15:54:45 PDT 2001 >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:99431a >linux/fs/pagebuf/page_buf.c - 1.95 >http://gibble.americas.sgi.com/cgi-bin/cvsweb.cgi/slinx_2.4.x-xfs-nodel/linux/fs/pagebuf/page_buf.c.diff?r1=text&tr1=1.95&r2=text&tr2=1.94&f=h >http://oss.sgi.com/cgi-bin/cvsweb.cgi/linux-2.4-xfs/linux/fs/pagebuf/page_buf.c.diff?r1=text&tr1=1.95&r2=text&tr2=1.94&f=h > - Backing out the change which made pagebuf do larger I/O on md devices > in some cases. This will increase the cpu overhead in this case, but > fix the log on these devices which was broken. > From owner-linux-xfs@oss.sgi.com Mon Jul 23 19:55:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O2tf408751 for linux-xfs-outgoing; Mon, 23 Jul 2001 19:55:41 -0700 Received: from jxmls04.se.mediaone.net (jxmls04.se.mediaone.net [24.129.0.51]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O2tcO08720 for ; Mon, 23 Jul 2001 19:55:38 -0700 Received: from enterprise (rr-163-49-140.atl.mediaone.net [24.163.49.140]) by jxmls04.se.mediaone.net (8.11.1/8.11.1) with ESMTP id f6O2rZH28343; Mon, 23 Jul 2001 22:54:00 -0400 (EDT) Reply-To: From: "Justin Hamilton" To: "'Steve Lord'" , "'Daniel Moore'" Cc: Subject: RE: FW: log mount/recovery failed Date: Mon, 23 Jul 2001 22:54:12 -0400 Organization: Linux-TechSupport.Com Message-ID: <001c01c113ec$0ab50690$0101a8c0@enterprise> 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.2616 In-Reply-To: <200107232254.f6NMsxK22896@jen.americas.sgi.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Importance: Normal Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I this VG is a single disk, and the lv uses all PE's in the VG. I am running RAID5 root FS, so the RAID code is active, just not for this filesystem. I'm going to try xfs_repair and will report how I get on. Justin -----Original Message----- From: Steve Lord [mailto:lord@sgi.com] Sent: Monday, July 23, 2001 6:55 PM To: Daniel Moore Cc: Justin@linux-techsupport.com; linux-xfs@oss.sgi.com Subject: Re: FW: log mount/recovery failed > > I'd have to hand this off to someone else on the list at this point - > I don't have time to follow though. But I can refer you to a comment > from > Steve: > > lord@sgi.com said: > => There is definitely a problem with the log on raid5 right now, we > did => not change anything on our end, so it looks like the underlying > code => may have broken things. We are looking into this. As for > performance, => the > > Are you using raid5? if so, this might explain it. If not, it might > anyway. I've never seen this kind of symptom before. >From the device I assumed this to be lvm, so the raid5 thing does not apply here. Steve > > ----------------------------------------------------- > Daniel Moore dxm@sgi.com > R&D Software Engineer Phone: +61-3-98348209 > SGI Performance Tools Group Fax: +61-3-98132378 > ----------------------------------------------------- > > From owner-linux-xfs@oss.sgi.com Mon Jul 23 20:04:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O341n09485 for linux-xfs-outgoing; Mon, 23 Jul 2001 20:04:01 -0700 Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O33tO09463 for ; Mon, 23 Jul 2001 20:03:55 -0700 Received: from arts.usyd.edu.au (IDENT:matthew@whitestar.arts.usyd.edu.au [129.78.16.20]) by plato.arts.usyd.edu.au (8.9.3/8.9.3) with ESMTP id NAA03443; Tue, 24 Jul 2001 13:03:52 +1000 (EST) Message-ID: <3B5CE70E.943D51C7@arts.usyd.edu.au> Date: Tue, 24 Jul 2001 13:10:06 +1000 From: Matthew Geier Organization: Arts IT Unit, Sydney University X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-pre6-xfs i686) X-Accept-Language: en, pdf MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com, samba-technical@samba.org Subject: Re: Samba 2.2.1 and Linux XFS quota References: <3B52A14E.6D0D4FA5@ch.sauter-bc.com><3B563C52.A3101025@xfs.lists.logout.sh> <20010720010215.77ebf768.jpenix@projectdesign.com> <010d01c11103$53d55af0$2df958c1@mpb> <3B58C4BE.E2535CA0@arts.usyd.edu.au> <20010723074836.C230215@wobbly.melbourne.sgi.com> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms9C3DA28C80D14D7D1BAE4194" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms9C3DA28C80D14D7D1BAE4194 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Nathan Scott wrote: > On Sat, Jul 21, 2001 at 09:54:38AM +1000, Matthew Geier wrote: > > ... > > I did notice one problem with Samba on XFS systems. Quota support > > doesn't work. After a look in smbd/quota.c, I see the quota's don't work > look through that file. In fact, having just looked through that file, > I see the IRIX quota system call interface is recognised (which is quite > similar to the Linux/XFS interface), so someone should be able to join > the dots here and make this code work for Linux/XFS. > Here is a first attempt at it if any one is interested. Seems to work for me, but I havent tested it to hard. Im also not sure I did it the right way either :-) Its quite dumb - it assume XFS quotas or 'linux' quotas. I just wrapped the changes around #ifdefs. I didn't try and copy the irix code where it changes what structures it uses depending on the file system type it finds. Its also full of DEBUG(0 statements so I could 'trace' what ended up where. --- quotas.c.orig Fri Jul 6 12:02:03 2001 +++ quotas.c Mon Jul 23 18:44:19 2001 @@ -43,12 +43,18 @@ #ifdef LINUX +#define XFS /* MG - Tag XFS quota changes, dunno how to configure */ + /* Mostly pinched from the IRIX section */ + #include #include #include #include #include +#ifdef XFS +#include +#endif _syscall4(int, quotactl, int, cmd, const char *, special, int, id, caddr_t, addr); @@ -60,6 +66,9 @@ { int r; struct dqblk D; +#ifdef XFS + struct fs_disk_quota F; +#endif SMB_STRUCT_STAT S; FILE *fp; struct mntent *mnt; @@ -96,6 +105,50 @@ save_re_uid(); set_effective_uid(0); + +#ifdef XFS + r=quotactl (QCMD(Q_XGETQUOTA,USRQUOTA), mnt->mnt_fsname, euser_id, (caddr_t) &F); + + restore_re_uid(); +DEBUG(0,("xfs_quotas: %s, %i, used %i \n",mnt->mnt_fsname,euser_id,F.d_bcount)); +DEBUG(0,("xfs_quotas:r is %i\n",r)); +/* if (ret==-1) + { + DEBUG(0,("xfs_quotas: ret evaluated -1 r is %i\n",r)); + return(False); + } + */ + +DEBUG(0,("xfs_quotas: d_blk_softlimit %i, d_blk_hardlimit %i\n" + ,F.d_blk_softlimit,F.d_blk_hardlimit)); + /* Use softlimit to determine disk space, except when it has been exceeded */ + if ( + (F.d_blk_softlimit && F.d_bcount>=F.d_blk_softlimit) || + (F.d_blk_hardlimit && F.d_bcount>=F.d_blk_hardlimit) || + (F.d_ino_softlimit && F.d_icount>=F.d_ino_softlimit) || + (F.d_ino_hardlimit && F.d_icount>=F.d_ino_hardlimit) + ) + { +DEBUG(0,("xfs_quotas: No blocks free\n")); + + *dfree = 0; + *dsize = F.d_bcount; + } + else if (F.d_blk_softlimit==0 && F.d_blk_hardlimit==0) + { + return(False); + } + else + { + *dfree = (F.d_blk_softlimit - F.d_bcount); + *dsize = F.d_blk_softlimit; + } + + + return (True); + + +#else r=quotactl(QCMD(Q_GETQUOTA,USRQUOTA), mnt->mnt_fsname, euser_id, (caddr_t)&D); restore_re_uid(); @@ -133,6 +186,9 @@ *dsize = D.dqb_bsoftlimit; } return (True); + +#endif + } #elif defined(CRAY) sh-2.04# -- Matthew Geier matthew@arts.usyd.edu.au Arts IT Unit +61 2 9351 4713 Sydney University --------------ms9C3DA28C80D14D7D1BAE4194 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIH0AYJKoZIhvcNAQcCoIIHwTCCB70CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BbswggKKMIIB86ADAgECAgMFMYswDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTA3MDkxOTEyNThaFw0wMjA3MDkxOTEyNTha MEoxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJzAlBgkqhkiG9w0BCQEWGG1h dHRoZXdAYXJ0cy51c3lkLmVkdS5hdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1H+o MQ4xn5lDS/7p9rYboPW7grw13lXOj7Xisip37QttkX7Ga3ITBXnsAKnuFK3Z7GtILACBXil1 BngLBOd0AlW9zqQBXEOP9aODNJzBsTb3+tOHwQo6shcORKQArKEinG00SuwBdzxALU3KWT6E yIUSvoz7q0PN4C8qUF3t00sCAwEAAaM1MDMwIwYDVR0RBBwwGoEYbWF0dGhld0BhcnRzLnVz eWQuZWR1LmF1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAiJu7SNBXsW7I+ZH9 e2+0M47BmR3DxV31VbW9mKcwuamusWSJJEy5MAKZc8b0snRX/XDkCpM+av3VxDJX8T3rxOE0 siyCC6Tclu6wjwjw0goXK4N6Xhsz+qwIfdoclNZkqK5yInEZtc5ijKr0IPRgch79f35WP82C SNHVYApmjzgwggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcN MDIwODI5MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmlj YXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMw MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNE KYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu 2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQAB o04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAcxtvJmWL/xU0 S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONntUPQ6bDSSrOaSnG7BIwHC CafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2lhglTWr0ncXDkS+p lrgFPFL83eliA0gxggHdMIIB2QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNV BAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS U0EgMjAwMC44LjMwAgMFMYswCQYFKw4DAhoFAKCBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0wMTA3MjQwMzEwMDhaMCMGCSqGSIb3DQEJBDEWBBSJAL9V iUmycZ2DpTWJmDidLVe4KzA6BgkqhkiG9w0BCQ8xLTArMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgEFtWELHfJb+LRofIcAi AigzfwM+4//rpL6FA//6IlIqnQZP63FJMoZMAkpWPFPg8Y0xW9OzIxHynXlLUpyOguSTaJXK iRAP4IReytchLd8MuS8Snc+p1xzcafUzj8jawh9yeRikMhdhOoH89Cke4jfyNrtZhT9NF7GM 17Q4Zk3e --------------ms9C3DA28C80D14D7D1BAE4194-- From owner-linux-xfs@oss.sgi.com Mon Jul 23 22:19:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O5JPo16670 for linux-xfs-outgoing; Mon, 23 Jul 2001 22:19:25 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O5JNO16651 for ; Mon, 23 Jul 2001 22:19:23 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA07154 for ; Mon, 23 Jul 2001 22:19:10 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id PAA49255; Tue, 24 Jul 2001 15:17:59 +1000 (EST) Date: Tue, 24 Jul 2001 15:17:59 +1000 From: Timothy Shimmin To: Johan Bengtsson Cc: linux-xfs@oss.sgi.com Subject: Re: root and xfsdump. Message-ID: <20010724151759.T37341@boing.melbourne.sgi.com> References: <200107191626.f6JGQEn32426@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200107191626.f6JGQEn32426@jen.americas.sgi.com>; from lord@sgi.com on Thu, Jul 19, 2001 at 11:26:14AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Johan, On Thu, Jul 19, 2001 at 11:26:14AM -0500, Steve Lord wrote: > > > > Hi, > > I noticed that xfsdump insist on being run only by root. > > Would things break if it was run by a normal user, given that this > > user can read the disk device? > > > > / Johan > > > xfsdump writes an inventory file out to /var/xfsdump/inventory/ this > would fail if you were not root - unless you opened up permissions in > there. There is a -J option which may surpress writing to this directory, > I only read the man page, not the code. > > Steve > > Also, xfsdump uses bulkstat's (ioctl of XFS_IOC_FSBULKSTAT) to iterate through the inodes of the FS which require CAP_SYS_ADMIN capability in order to succeed. --Tim From owner-linux-xfs@oss.sgi.com Mon Jul 23 23:59:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O6x2820461 for linux-xfs-outgoing; Mon, 23 Jul 2001 23:59:02 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O6x0O20441 for ; Mon, 23 Jul 2001 23:59:00 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id XAA04598 for ; Mon, 23 Jul 2001 23:56:37 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA32511 for linux-xfs@oss.sgi.com; Tue, 24 Jul 2001 16:57:39 +1000 (EST) Date: Tue, 24 Jul 2001 16:57:39 +1000 (EST) From: Nathan Scott Message-Id: <200107240657.QAA32511@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Several xfsdump fixes coming from IRIX, from CHANGES file: - merge in phase 3 changes from review and further testing - merge in code to specify maximum file size for xfsdump (-z) - merge in code to specify media file size for xfsdump (-d) - merge in code to request single media file for xfsdump (-S) - merge a couple of minor bug fixes from IRIX cheers. Date: Mon Jul 23 23:55:40 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99441a cmd/xfsdump/dump/inomap.c - 1.6 cmd/xfsdump/dump/getopt.h - 1.3 cmd/xfsdump/dump/content.c - 1.6 cmd/xfsdump/common/main.c - 1.6 cmd/xfsdump/common/drive_scsitape.c - 1.2 cmd/xfsdump/common/drive_minrmt.c - 1.3 cmd/xfsdump/VERSION - 1.15 cmd/xfsdump/debian/changelog - 1.11 cmd/xfsdump/doc/CHANGES - 1.18 - merge in several missing fixes from IRIX. From owner-linux-xfs@oss.sgi.com Tue Jul 24 00:59:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O7xBT23480 for linux-xfs-outgoing; Tue, 24 Jul 2001 00:59:11 -0700 Received: from relay.kiev.sovam.com (mail@relay.kiev.sovam.com [212.109.32.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O7x5O23449 for ; Tue, 24 Jul 2001 00:59:07 -0700 Received: from [10.103.5.24] (helo=victoria) by relay.kiev.sovam.com with smtp (Exim 3.22 #4) id 15Ox5p-000GYh-00 for linux-xfs@oss.sgi.com; Tue, 24 Jul 2001 10:59:01 +0300 Message-ID: <012401c11417$0d495e80$1805670a@kiev.sovam.com> From: "Eugene Shramko" To: Subject: I receive error messages "__alloc_pages: 0-order allocation failed" Date: Tue, 24 Jul 2001 11:02:58 +0300 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0121_01C11430.328BE820" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_0121_01C11430.328BE820 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Hi,=20 I receive error messages "__alloc_pages: 0-order allocation failed" = when run small test. dd if=3D/dev/zero of=3D/u41/test/testfile bs=3D4096 count=3D524288 = and=20 dd if=3D/u41/test/testfile of =3D/dev/null bs=3D4096 count=3D524288. Is it dangerous? What can I do? I try to use xfs with Oracle , but i am not sure. RedHat 7.1 with kernel 2.4.5-SGI_XFS_1.0.1 Eugene ------=_NextPart_000_0121_01C11430.328BE820 Content-Type: text/html; charset="koi8-r" Content-Transfer-Encoding: quoted-printable
    Hi,
     
     I receive error messages = "__alloc_pages: 0-order allocation failed" when run small = test.
     
     dd if=3D/dev/zero=20 of=3D/u41/test/testfile  bs=3D4096 count=3D524288  and =
     dd if=3D/u41/test/testfile of =3D/dev/null bs=3D4096 = count=3D524288.
     
     Is it dangerous?  What can I do?
     
    I try to use xfs with Oracle , but i am not sure.
     
    RedHat 7.1 with  kernel = 2.4.5-SGI_XFS_1.0.1
     
    Eugene
     
     
    ------=_NextPart_000_0121_01C11430.328BE820-- From owner-linux-xfs@oss.sgi.com Tue Jul 24 01:06:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O86Q924020 for linux-xfs-outgoing; Tue, 24 Jul 2001 01:06:26 -0700 Received: from relay.kiev.sovam.com (mail@relay.kiev.sovam.com [212.109.32.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O86NO24000 for ; Tue, 24 Jul 2001 01:06:23 -0700 Received: from [10.103.5.24] (helo=victoria) by relay.kiev.sovam.com with smtp (Exim 3.22 #4) id 15OxCu-000HuB-00 for linux-xfs@oss.sgi.com; Tue, 24 Jul 2001 11:06:20 +0300 Message-ID: <015201c11418$12db3110$1805670a@kiev.sovam.com> From: "Eugene Shramko" To: Subject: I receive error messages "__alloc_pages: 0-order allocation failed" Date: Tue, 24 Jul 2001 11:10:17 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi,=20 I receive error messages "__alloc_pages: 0-order allocation failed" when run small test. dd if=/dev/zero of=3D/u41/test/testfile bs=3D4096 count=524288 and dd if=/u41/test/testfile of =3D/dev/null bs=3D4096 count=524288. Is it dangerous? What can I do? I try to use xfs with Oracle , but i am not sure. RedHat 7.1 with kernel 2.4.5-SGI_XFS_1.0.1 Eugene From owner-linux-xfs@oss.sgi.com Tue Jul 24 01:49:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6O8nhh26154 for linux-xfs-outgoing; Tue, 24 Jul 2001 01:49:43 -0700 Received: from mbox.ttm.bg (setcom.bg [195.230.0.14] (may be forged)) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6O8ndO26132 for ; Tue, 24 Jul 2001 01:49:39 -0700 Received: from setcom.bg (etg.setcom.bg [195.230.0.105]) by mbox.ttm.bg (8.11.3/8.11.3) with ESMTP id f6O8qO411757 for ; Tue, 24 Jul 2001 11:52:24 +0300 Message-ID: <3B5D35EA.A464402E@setcom.bg> Date: Tue, 24 Jul 2001 11:46:34 +0300 From: Evgeni Gechev Organization: SetCom Ltd. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3 i686) X-Accept-Language: bg, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: slackware 8.0 and jfs Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk http://slackjfs.setcom.bg/ From owner-linux-xfs@oss.sgi.com Tue Jul 24 06:26:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ODQuX09124 for linux-xfs-outgoing; Tue, 24 Jul 2001 06:26:56 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ODQsO09102 for ; Tue, 24 Jul 2001 06:26:54 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id B30541AB10 for ; Tue, 24 Jul 2001 09:26:53 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 507B5485; Tue, 24 Jul 2001 09:26:53 -0400 (EDT) Date: Tue, 24 Jul 2001 09:26:53 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Logdev size? Message-ID: <20010724092652.A31186@dkp.com> 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.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm going to be building an array later today, and, seeing as I won't have much time to test different combinations of options for performance (I'll be lucky, as usual, if I can get stability testing done before the box is wanted for production), I thought I'd ask about what might be good options to try performance-wise. The box will have... - 16 75G IDE drives in a single software RAID 5 array - 2 30G IDE drives containing the boot, root, and the big array's logdev on RAID 1 partitions. It'll mostly be film frames - 6MB to 12MB, or thereabouts - with a comparatively small amount of metadata activity (mostly compositing work). Any suggestions on a likely good logdev size? Any other suggestions to improve XFS performance for this setup? Thanks. Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 06:53:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ODrus11117 for linux-xfs-outgoing; Tue, 24 Jul 2001 06:53:56 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ODrrO11089 for ; Tue, 24 Jul 2001 06:53:53 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id PAA248562 for ; Tue, 24 Jul 2001 15:53:42 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2499158; Tue, 24 Jul 2001 08:52:33 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA96094; Tue, 24 Jul 2001 08:52:33 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6ODqZJ23995; Tue, 24 Jul 2001 08:52:35 -0500 Message-Id: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Klaassen cc: linux-xfs@oss.sgi.com Subject: Re: Logdev size? In-Reply-To: Message from Andrew Klaassen of "Tue, 24 Jul 2001 09:26:53 EDT." <20010724092652.A31186@dkp.com> Date: Tue, 24 Jul 2001 08:52:35 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I'm going to be building an array later today, and, seeing as I > won't have much time to test different combinations of options > for performance (I'll be lucky, as usual, if I can get stability > testing done before the box is wanted for production), I thought > I'd ask about what might be good options to try > performance-wise. > > The box will have... > > - 16 75G IDE drives in a single software RAID 5 array > - 2 30G IDE drives containing the boot, root, and the big > array's logdev on RAID 1 partitions. > > It'll mostly be film frames - 6MB to 12MB, or thereabouts - with > a comparatively small amount of metadata activity (mostly > compositing work). > > Any suggestions on a likely good logdev size? > > Any other suggestions to improve XFS performance for this setup? You may want to do a couple of experiments with different stripe sizes on the raid (except for the fact that this will mean doing rebuilds between tests). With this sort of large file you are probably doing large I/O and this may make a difference, although it is not something I have experimented with on Linux. Make sure you have the latest mkfs binary, more recent ones will make a better attempt at laying down the filesystem on a large setup like this. You will be crossing the 1 Tbyte limit with this filesystem, so you should use a larger than default inode size: mkfs -t xfs -f -i size=512 In general you will probably not need a huge log, in fact XFS logs are never more than 128 Mbytes in size on linux. A size of 64M is probably ample, you can get this with -l size=16384b So a mkfs line along the lines of: mkfs -t xfs -f -i size=512 -l size=16384b /dev/xxx would be a good starting point. I would mount with more than the default number of logbuffers: mount -o logbufs=4 Steve > > Thanks. > > Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:01:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OE13D11900 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:01:03 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OE12O11877 for ; Tue, 24 Jul 2001 07:01:02 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 9C2061AB10; Tue, 24 Jul 2001 10:01:01 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 32CFF486; Tue, 24 Jul 2001 10:01:01 -0400 (EDT) Date: Tue, 24 Jul 2001 10:01:00 -0400 From: Andrew Klaassen To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724100100.D31186@dkp.com> Mail-Followup-To: Steve Lord , linux-xfs@oss.sgi.com References: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 08:52:35AM -0500, Steve Lord wrote: > Make sure you have the latest mkfs binary, more recent ones > will make a better attempt at laying down the filesystem on a > large setup like this. Latest CVS for mkfs, then? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:02:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OE29r12101 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:02:09 -0700 Received: from gw.rupa.com (cx838204-a.alsv1.occa.home.com [24.16.83.66]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OE27O12080 for ; Tue, 24 Jul 2001 07:02:07 -0700 Received: from shakti.rupa.com (fw.rupa.com [192.168.1.253]) by gw.rupa.com (Postfix) with ESMTP id 8BFB8CE68D; Tue, 24 Jul 2001 07:02:06 -0700 (PDT) Received: by shakti.rupa.com (Postfix, from userid 500) id 1E5BDC0086; Tue, 24 Jul 2001 07:02:06 -0700 (PDT) To: Russel Ingram Cc: Subject: Re: Debian install on XFS? References: From: Rupa Schomaker Mail-Copies-To: never Date: Tue, 24 Jul 2001 07:02:06 -0700 In-Reply-To: (Russel Ingram's message of "Mon, 23 Jul 2001 11:53:34 -0600 (MDT)") Message-ID: Lines: 52 User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I just recently did an XFS install on my debian system. Since I wanted to build XFS over LVM, zoran's boot disk was of limited use. I did use it though! Some things I had to do: 1) the woody support script (find . -name woody after you boot from the floppy on VC2) needed to have the groff-base package added. 2) I installed woody to a scratch HD installed as hda 3) I had two 40G drives attached as hde and hdg on a promise ATA100 controller. 4) Boot from hda, build a new kernel with latest XFS with lvm enabled. 5) get lvm tools from the unstable tree 6) Identically partition the dual 40s into three slices. 1 small slice (50m) for boot, make it /dev/md0. 1 small slice (1G each) for swap, make it /dev/md1. The "rest" as a large slice and make it /dev/md2. 7) create a pv of /dev/md2, vgcreate on it, and then create lvs for whatever I neeed. 8) (still have to do) build a working recover disk for XFS+LVM. For now, I can just plug in my scratch disk and have a working debian with XFS+LVM. It is more drastic than just putting a floppy in, but... it works. tada! working system. Now, getting Oracle9i to install on woody is even more fun. :) Russel Ingram writes: > I know a while back someone posted that there was an instal disk image > available for installing Debian on XFS. Does anyone know if it has been > updated for the 1.0.1 XFS or if it will be? > > Russ > -- > Russ Ingram > Gargoyle Computer Consulting > (307)742-1361 > www.gargoylecc.com > -- -rupa From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:02:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OE2DK12188 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:02:13 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OE2BO12143 for ; Tue, 24 Jul 2001 07:02:11 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OE5jU29396 for ; Tue, 24 Jul 2001 07:05:45 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2514220; Tue, 24 Jul 2001 09:00:50 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA72491; Tue, 24 Jul 2001 09:00:49 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OE0qb24037; Tue, 24 Jul 2001 09:00:52 -0500 Message-Id: <200107241400.f6OE0qb24037@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Eugene Shramko" cc: linux-xfs@oss.sgi.com Subject: Re: I receive error messages "__alloc_pages: 0-order allocation failed" In-Reply-To: Message from "Eugene Shramko" of "Tue, 24 Jul 2001 11:10:17 +0300." <015201c11418$12db3110$1805670a@kiev.sovam.com> Date: Tue, 24 Jul 2001 09:00:52 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi,=20 > > I receive error messages "__alloc_pages: 0-order allocation failed" when > run small test. > > dd if=/dev/zero of=3D/u41/test/testfile bs=3D4096 count=524288 and > dd if=/u41/test/testfile of =3D/dev/null bs=3D4096 count=524288. > > Is it dangerous? What can I do? > > I try to use xfs with Oracle , but i am not sure. > > RedHat 7.1 with kernel 2.4.5-SGI_XFS_1.0.1 This message is only a warning that memory is running low, once it happens the kernel will attempt to find memory in other ways and free some space before trying again. What type of device is your filesystem built on? I am guessing some sort of software raid configuration? Also is this a highmem kernel? There were known mainline kernel deadlocks in this configuration up until 2.4.7. Steve > > > Eugene > From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:04:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OE4CN12466 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:04:12 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OE4BO12443 for ; Tue, 24 Jul 2001 07:04:11 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OE7iU29484 for ; Tue, 24 Jul 2001 07:07:44 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2500185 for ; Tue, 24 Jul 2001 09:02:50 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA68593; Tue, 24 Jul 2001 09:02:50 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OE2qD24056; Tue, 24 Jul 2001 09:02:52 -0500 Message-Id: <200107241402.f6OE2qD24056@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: Logdev size? In-Reply-To: Message from Andrew Klaassen of "Tue, 24 Jul 2001 10:01:00 EDT." <20010724100100.D31186@dkp.com> Date: Tue, 24 Jul 2001 09:02:52 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Tue, Jul 24, 2001 at 08:52:35AM -0500, > Steve Lord wrote: > > > Make sure you have the latest mkfs binary, more recent ones > > will make a better attempt at laying down the filesystem on a > > large setup like this. > > Latest CVS for mkfs, then? Hmm, 1.0.1 is probably good enough come to think of it, but I would probably go with the latest cvs kernel given the highmem/raid deadlocks which have been fixed post 1.0.1. Steve > > Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:25:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OEPbg14092 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:25:37 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OEPZO14073 for ; Tue, 24 Jul 2001 07:25:35 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 724281AB11 for ; Tue, 24 Jul 2001 10:25:34 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id D40B14C5; Tue, 24 Jul 2001 10:25:33 -0400 (EDT) Date: Tue, 24 Jul 2001 10:25:33 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724102533.F31186@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107241402.f6OE2qD24056@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 09:02:52AM -0500, Steve Lord wrote: > Hmm, 1.0.1 is probably good enough come to think of it, but I > would probably go with the latest cvs kernel given the > highmem/raid deadlocks which have been fixed post 1.0.1. Hmm. That makes me nervous; there isn't a tagged-and-tested CVS kernel, is there? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:30:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OEUaC14574 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:30:36 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OEUYO14554 for ; Tue, 24 Jul 2001 07:30:35 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 493CD1AB11 for ; Tue, 24 Jul 2001 10:30:34 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id E88CA4C5; Tue, 24 Jul 2001 10:30:33 -0400 (EDT) Date: Tue, 24 Jul 2001 10:30:33 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724103033.G31186@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <4.3.2.7.2.20010724155122.02c71748@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.20010724155122.02c71748@pop.xs4all.nl> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 03:55:13PM +0200, Seth Mos wrote: > At 09:26 24-7-2001 -0400, you wrote: > > I'm going to be building an array later today... > How many processes/users will be active at the same moment? There may be up to 12 composites running at once on separate compositing boxes, potentially all accessing the fileserver at the same time. > You could try the default mkfs and then mount it with > logbufs=8 if you have enough memory for extra throuhput. It'll have 1GB of memory. > Is it connected on gigabit or are you never going to pass the > 10MB/s off 100Mbit ethernet networks? The fileserver will have gigabit, and the clients 100Mbit. Later, we may move the fileserver to dual gigabit and the clients to gigabit. Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 07:38:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OEcMl15364 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:38:22 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OEcKO15345 for ; Tue, 24 Jul 2001 07:38:21 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OEgwm27257 for ; Tue, 24 Jul 2001 07:42:58 -0700 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id JAA19138 for ; Tue, 24 Jul 2001 09:36:59 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15P3Iw-0000pR-00 for ; Tue, 24 Jul 2001 09:36:58 -0500 Date: Tue, 24 Jul 2001 09:36:58 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724093658.B706@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724102533.F31186@dkp.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 10:25:33AM -0400, Andrew Klaassen wrote: > On Tue, Jul 24, 2001 at 09:02:52AM -0500, > Steve Lord wrote: > > > Hmm, 1.0.1 is probably good enough come to think of it, but I > > would probably go with the latest cvs kernel given the > > highmem/raid deadlocks which have been fixed post 1.0.1. > > Hmm. > > That makes me nervous; there isn't a tagged-and-tested CVS > kernel, is there? Nope, especially not on a 1TB IDE RAID5. -- 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 Jul 24 07:45:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OEj2315920 for linux-xfs-outgoing; Tue, 24 Jul 2001 07:45:02 -0700 Received: from rain.CC.Lehigh.EDU (rain.CC.Lehigh.EDU [128.180.39.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OEj0O15887 for ; Tue, 24 Jul 2001 07:45:00 -0700 Received: from Lehigh.EDU (hooch.CC.Lehigh.EDU [128.180.3.11]) by rain.CC.Lehigh.EDU (8.11.2/8.11.2) with ESMTP id f6OEis401618; Tue, 24 Jul 2001 10:44:54 -0400 Message-ID: <3B5D879A.E0FECD4E@Lehigh.EDU> Date: Tue, 24 Jul 2001 10:35:06 -0400 From: Jim Eshleman X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfsrestore assertion failure Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Greets! I'm receiving the following error using xfsrestore: # xfsrestore -t -f /dev/st0 xfsrestore: using online session inventory xfsrestore: searching media for directory dump xfsrestore: reading directories xfsrestore: directory post-processing xfsrestore: reading non-directory files [...long list of files ...] xfsrestore: examining media file 1 xfsrestore: seeking past media file directory dump xfsrestore: drive_scsitape.c:1461: do_next_mark: Assertion `rechdrp->first_mark_offset - rechdrp->file_offset <= ( off64_t ) ( contextp->dc_recsz )' failed. Aborted (core dumped) # This is happening on two different systems. System A is the stock SGI RH7.1 XFS 1.0.1 distribution running on a dual P2-333 with a DLT4000 drive. System B is RH7.1 + kernel 2.4.7 + patch-2.4.7-xfs-2001-07-22.bz2 running on a Netfinity x370 with a DLT7000. I've also tried (on System B) kernel 2.4.6 + linux-2.4.6-xfs-07052001.patch.bz2, and both xfsdump-1.0.9 and 1.0.11 RPMs. I've tried specifying a block size of 240K on the dump and restore. Same result. The dump runs with no errors as "xfsdump -l 0 -o -f /dev/st0 -s userdir /a" where /a/userdir is about 1.2G. FYI the Netfinity is an 8-way 700Mhz P3 Xeon (2M cache) with 8.5G memory, 650G disk, XFS on top of LVM and hardware raid. So far (excepting this problem) XFS has worked fine in testing with NFS and quotas. Jim From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:15:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFFsR18191 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:15:54 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFFqO18171 for ; Tue, 24 Jul 2001 08:15:52 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OFKTm29387 for ; Tue, 24 Jul 2001 08:20:30 -0700 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA26389 for ; Tue, 24 Jul 2001 10:14:31 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15P3tG-0000tr-00 for ; Tue, 24 Jul 2001 10:14:30 -0500 Date: Tue, 24 Jul 2001 10:14:30 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724101430.C706@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> <20010724093658.B706@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724093658.B706@sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 09:36:58AM -0500, Nathan Straz wrote: > On Tue, Jul 24, 2001 at 10:25:33AM -0400, Andrew Klaassen wrote: > > That makes me nervous; there isn't a tagged-and-tested CVS > > kernel, is there? > > Nope, especially not on a 1TB IDE RAID5. I'm going to work on running patch-2.4.7-xfs-2001-07-22 through some regression tests and if I have time today I'll try to get the top of the CVS tree built and tested too. I'll put out a quick report before I leave for OLS. -- 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 Jul 24 08:22:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFM2l18908 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:22:02 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFM0O18889 for ; Tue, 24 Jul 2001 08:22:00 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 19E0C6391E for ; Tue, 24 Jul 2001 16:24:22 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 24 Jul 2001 16:27:18 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Subject: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Tue, 24 Jul 2001 16:21:58 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUVGE3NJyyHT1TR2yjr/Mixi3OVw== From: "Juer Lee" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6OFM0O18890 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, All, Does anybody have experience in backup ACLs on XFS? I met some difficulties on that. >From FAQ of XFS, it says that we can use xfsdump to backup ACLs, the version of xfsdump I am using is 1.0.2. I tried them like this: 1. Create a XFS partition -- mkfs.xfs /dev/hda5 -f 2. Mount that partition to a directory mount -t xfs /dev/hda5 /test 3. Create some files and directories under test , use command chacl to set the ACLs for them 4. Under root / directory -- xfsdum -f /tmp/xfs_backup /test -- it is just a test, so I backup it as a file 5. Under directory test, I create another directory test-restore in advance 6. Under root / directory -- xfsrestore-f /tmp/xfs_backup /test/test-restore - After the step 6, I use command chacl -l * to list all files' ACLs, unfortunately, I couldn't get any of them. Thank for all in advance, I need help. Btw, my machine is power PC, my kernel is 2.4.5, I applied all patches for XFS already. Juer From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:32:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFWMX19978 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:32:22 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFWLO19950 for ; Tue, 24 Jul 2001 08:32:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OFZsU01700 for ; Tue, 24 Jul 2001 08:35:54 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2513576; Tue, 24 Jul 2001 10:29:44 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA94285; Tue, 24 Jul 2001 10:29:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OFTjc24955; Tue, 24 Jul 2001 10:29:45 -0500 Message-Id: <200107241529.f6OFTjc24955@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Juer Lee" cc: linux-xfs@oss.sgi.com Subject: Re: Backup ACLs In-Reply-To: Message from "Juer Lee" of "Tue, 24 Jul 2001 16:21:58 BST." Date: Tue, 24 Jul 2001 10:29:45 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hello, All, > > Does anybody have experience in backup ACLs on XFS? I met some > difficulties on that. > > >From FAQ of XFS, it says that we can use xfsdump to backup ACLs, the > version of xfsdump I am using is 1.0.2. Take a look on the ftp site, there is an rpm of 1.0.11 of xfsdump here: ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ Try this version. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:31:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFVx219904 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:31:59 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFVvO19880 for ; Tue, 24 Jul 2001 08:31:57 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 08C3B1AB11 for ; Tue, 24 Jul 2001 11:31:57 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 149CA562; Tue, 24 Jul 2001 11:31:42 -0400 (EDT) Date: Tue, 24 Jul 2001 11:31:38 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724113137.H31186@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> <20010724093658.B706@sgi.com> <20010724101430.C706@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724101430.C706@sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 10:14:30AM -0500, Nathan Straz wrote: > I'm going to work on running patch-2.4.7-xfs-2001-07-22 > through some regression tests and if I have time today I'll > try to get the top of the CVS tree built and tested too. I'll > put out a quick report before I leave for OLS. Regression tests? Anything I could add to my own test suite? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:36:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFaFw20469 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:36:15 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFaDO20449 for ; Tue, 24 Jul 2001 08:36:13 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 410B3638EA; Tue, 24 Jul 2001 16:38:28 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 24 Jul 2001 16:41:25 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Tue, 24 Jul 2001 16:36:03 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUVX9cxmqYPAwdTwy7vZNXezaRSgAADX/w From: "Juer Lee" To: "Steve Lord" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6OFaDO20450 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >> Hello, All, >> >> Does anybody have experience in backup ACLs on XFS? I met some >> difficulties on that. >> >> >From FAQ of XFS, it says that we can use xfsdump to backup ACLs, the >> version of xfsdump I am using is 1.0.2. > >Take a look on the ftp site, there is an rpm of 1.0.11 of xfsdump here: > >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ > >Try this version. > >Steve > Thanks. Ohmm, I have already downloaded it, but I failed to compile that version on my machine (Power PC). So I used version 1.0.2 as I mentioned before. Is it my version 2.95.2 GCC's problem? Juer From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:40:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFeJX20882 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:40:19 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFeHO20859 for ; Tue, 24 Jul 2001 08:40:17 -0700 Received: from ledzep.americas.sgi.com (relay.sgi.com [137.38.226.97] (may be forged)) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id IAA01732 for ; Tue, 24 Jul 2001 08:40:09 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA28341 for ; Tue, 24 Jul 2001 10:38:54 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15P4Gs-0000vG-00 for ; Tue, 24 Jul 2001 10:38:54 -0500 Date: Tue, 24 Jul 2001 10:38:54 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: XFS patch testing Message-ID: <20010724103854.D706@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> <20010724093658.B706@sgi.com> <20010724101430.C706@sgi.com> <20010724113137.H31186@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724113137.H31186@dkp.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 11:31:38AM -0400, Andrew Klaassen wrote: > On Tue, Jul 24, 2001 at 10:14:30AM -0500, > Nathan Straz wrote: > > > I'm going to work on running patch-2.4.7-xfs-2001-07-22 > > through some regression tests and if I have time today I'll > > try to get the top of the CVS tree built and tested too. I'll > > put out a quick report before I leave for OLS. > > Regression tests? Anything I could add to my own test suite? If you pull down the CVS tree, there are regression tests under cmd/xfstests/. There are some more in LTP and we have some that aren't open sourced. It's just a matter of doing lots of configurations to make sure we get good coverage. -- 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 Jul 24 08:48:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFmqQ21504 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:48:52 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFmoO21482 for ; Tue, 24 Jul 2001 08:48:51 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 4DA941AB11 for ; Tue, 24 Jul 2001 11:48:50 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id D3B3D624; Tue, 24 Jul 2001 11:48:44 -0400 (EDT) Date: Tue, 24 Jul 2001 11:48:43 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: XFS patch testing Message-ID: <20010724114843.I31186@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> <20010724093658.B706@sgi.com> <20010724101430.C706@sgi.com> <20010724113137.H31186@dkp.com> <20010724103854.D706@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724103854.D706@sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 10:38:54AM -0500, Nathan Straz wrote: > If you pull down the CVS tree, there are regression tests under > cmd/xfstests/. Yep... I've used those before. No problem. > There are some more in LTP... As in ltp.sourceforge.net? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:52:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFq0H21844 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:52:00 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFpwO21824 for ; Tue, 24 Jul 2001 08:51:58 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OFtWU02947 for ; Tue, 24 Jul 2001 08:55:32 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id KAA2510468; Tue, 24 Jul 2001 10:50:37 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id KAA13761; Tue, 24 Jul 2001 10:50:37 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OFoc925010; Tue, 24 Jul 2001 10:50:38 -0500 Message-Id: <200107241550.f6OFoc925010@jen.americas.sgi.com> To: "Juer Lee" cc: linux-xfs@oss.sgi.com Subject: Re: Backup ACLs References: Comments: In-reply-to "Juer Lee" message dated "Tue, 24 Jul 2001 16:36:03 +0100." Date: Tue, 24 Jul 2001 10:50:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > >Take a look on the ftp site, there is an rpm of 1.0.11 of xfsdump here: > > > >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ > > > >Try this version. > > > >Steve > > > Thanks. > > Ohmm, I have already downloaded it, but I failed to compile that version > on my machine (Power PC). So I used version 1.0.2 as I mentioned > before. Is it my version 2.95.2 GCC's problem?=20 > > Juer Hmm, we need more details than 'failed to compile' Steve From owner-linux-xfs@oss.sgi.com Tue Jul 24 08:59:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OFxaS22425 for linux-xfs-outgoing; Tue, 24 Jul 2001 08:59:36 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OFxXO22405 for ; Tue, 24 Jul 2001 08:59:33 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id D23EB6388C; Tue, 24 Jul 2001 17:00:19 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 24 Jul 2001 17:03:16 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Tue, 24 Jul 2001 16:57:56 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUWGRUBirl97UgSiGhV0vzg085rgAAJYaQ From: "Juer Lee" To: "Steve Lord" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6OFxYO22406 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >> > >> >Take a look on the ftp site, there is an rpm of 1.0.11 of >xfsdump here: >> > >> >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ >> > >> >Try this version. >> > >> >Steve >> > >> Thanks. >> >> Ohmm, I have already downloaded it, but I failed to compile >that version >> on my machine (Power PC). So I used version 1.0.2 as I mentioned >> before. Is it my version 2.95.2 GCC's problem?=20 >> >> Juer > >Hmm, we need more details than 'failed to compile' > >Steve > When I compiled it, I got error message as xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) Thougn I can modify some code for that, I am not sure if other problems I will meet. Juer From owner-linux-xfs@oss.sgi.com Tue Jul 24 09:01:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OG1eD22678 for linux-xfs-outgoing; Tue, 24 Jul 2001 09:01:40 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OG1dO22653 for ; Tue, 24 Jul 2001 09:01:39 -0700 Received: from ledzep.americas.sgi.com (relay.sgi.com [137.38.226.97] (may be forged)) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id JAA09978 for ; Tue, 24 Jul 2001 09:01:23 -0700 (PDT) mail_from (nstraz@sgi.com) Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA24348 for ; Tue, 24 Jul 2001 10:59:35 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15P4as-0000wu-00 for ; Tue, 24 Jul 2001 10:59:34 -0500 Date: Tue, 24 Jul 2001 10:59:34 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: XFS patch testing Message-ID: <20010724105934.E706@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> <20010724093658.B706@sgi.com> <20010724101430.C706@sgi.com> <20010724113137.H31186@dkp.com> <20010724103854.D706@sgi.com> <20010724114843.I31186@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724114843.I31186@dkp.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 11:48:43AM -0400, Andrew Klaassen wrote: > On Tue, Jul 24, 2001 at 10:38:54AM -0500, > Nathan Straz wrote: > > There are some more in LTP... > > As in ltp.sourceforge.net? That's the one. -- 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 Jul 24 09:03:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OG3AN22882 for linux-xfs-outgoing; Tue, 24 Jul 2001 09:03:10 -0700 Received: from mustang.centralnet.ch (mustang.centralnet.ch [193.135.146.12]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OG38O22863 for ; Tue, 24 Jul 2001 09:03:08 -0700 Received: from vollmann.ch (luz187.centralnet.ch [193.135.147.187]) by mustang.centralnet.ch (8.9.3/8.9.3) with ESMTP id SAA204920; Tue, 24 Jul 2001 18:03:04 +0200 (MES) Received: from two.vollmann.ch (localhost [127.0.0.1]) by vollmann.ch (8.8.6/8.8.5) with SMTP id QAA01319; Tue, 24 Jul 2001 16:03:22 GMT Message-ID: <3B5D9C4A.11FD8C07@vollmann.ch> Date: Tue, 24 Jul 2001 16:03:22 +0000 From: Detlef Vollmann Organization: vollmann engineering gmbh X-Mailer: Mozilla 3.04 (X11; U; Linux 2.2.14-5.0 i586) MIME-Version: 1.0 To: Steve Lord CC: XFS list Subject: Re: Official patch against 2.4.7? References: <200107232252.f6NMqwq22877@jen.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord wrote: > Well, it depends on what you call 1.0.1 .... The reason I asked was because I will setup a productive server and wondered about the kernel and xfs versions I'd use. BTW, I remember a mail some weeks ago when you(?) wrote that there would be an official patch against 2.4.6. What about that? Detlef -- Detlef Vollmann vollmann engineering gmbh Tel: +41-41-4120911 P.O. Box 5106 Fax: +41-41-4120912 CH-6000 Luzern 5 / Switzerland eMail: dv@vollmann.ch From owner-linux-xfs@oss.sgi.com Tue Jul 24 09:21:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OGLwI23415 for linux-xfs-outgoing; Tue, 24 Jul 2001 09:21:58 -0700 Received: from d13.com ([216.33.170.30]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OGLuO23390 for ; Tue, 24 Jul 2001 09:21:56 -0700 Received: (qmail 15109 invoked by uid 526); 24 Jul 2001 16:21:51 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Jul 2001 16:21:51 -0000 Date: Tue, 24 Jul 2001 09:21:51 -0700 (PDT) From: Mike Sklar X-X-Sender: To: XFS list Subject: newer *.img files than XFS-1.0.1? In-Reply-To: <3B5D9C4A.11FD8C07@vollmann.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am seeing the aic7xxx hangs on my VALinux 2200s using the bootnet.img provided with XFS-1.0.1 release. This problem did not exist in the 1.0 release (for me), but those older 1.0 images files have compatibility problems with the 1.0.1 installer. I don't suppose a updated set of XFS supported *.img files exists anywhere? my scsi controller info (lspci -vv): 00:0c.0 SCSI storage controller: Adaptec 7896 Subsystem: Adaptec: Unknown device 0053 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- [disabled] [size=128K] Capabilities: 00:0c.1 SCSI storage controller: Adaptec 7896 Subsystem: Adaptec: Unknown device 0053 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- From owner-linux-xfs@oss.sgi.com Tue Jul 24 09:35:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OGZR224073 for linux-xfs-outgoing; Tue, 24 Jul 2001 09:35:27 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OGZQO24054 for ; Tue, 24 Jul 2001 09:35:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OGe3m02468 for ; Tue, 24 Jul 2001 09:40:03 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2476947; Tue, 24 Jul 2001 11:34:04 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA06832; Tue, 24 Jul 2001 11:34:04 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OGY5O25538; Tue, 24 Jul 2001 11:34:05 -0500 Message-Id: <200107241634.f6OGY5O25538@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Juer Lee" cc: "Steve Lord" , linux-xfs@oss.sgi.com Subject: Re: Backup ACLs In-Reply-To: Message from "Juer Lee" of "Tue, 24 Jul 2001 16:57:56 BST." Date: Tue, 24 Jul 2001 11:34:05 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > When I compiled it, I got error message as=20 > xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) > > Thougn I can modify some code for that, I am not sure if other problems > I will meet. > > Juer O_DIRECT is probably not defined in the user space headers on powerpc, or you need a newer glibc. On my system it is defined in /usr/include/bits/fcntl.h I am using glibc-2.2.2 For the power pc the kernel is expecting to use the value 0400000 for O_DIRECT. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 24 09:36:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OGagF24156 for linux-xfs-outgoing; Tue, 24 Jul 2001 09:36:42 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OGaeO24136 for ; Tue, 24 Jul 2001 09:36:40 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OGfIm02544 for ; Tue, 24 Jul 2001 09:41:18 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2513826; Tue, 24 Jul 2001 11:35:19 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA97674; Tue, 24 Jul 2001 11:35:19 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OGZKu25549; Tue, 24 Jul 2001 11:35:20 -0500 Message-Id: <200107241635.f6OGZKu25549@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mike Sklar cc: XFS list Subject: Re: newer *.img files than XFS-1.0.1? In-Reply-To: Message from Mike Sklar of "Tue, 24 Jul 2001 09:21:51 PDT." Date: Tue, 24 Jul 2001 11:35:20 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > I am seeing the aic7xxx hangs on my VALinux 2200s using the bootnet.img > provided with XFS-1.0.1 release. > > This problem did not exist in the 1.0 release (for me), but those > older 1.0 images files have compatibility problems with the 1.0.1 > installer. I don't suppose a updated set of XFS supported *.img files > exists anywhere? > Sorry I cannot really answer this question, and Eric who perhaps could, is out all week. Steve From owner-linux-xfs@oss.sgi.com Tue Jul 24 11:48:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OImJs29301 for linux-xfs-outgoing; Tue, 24 Jul 2001 11:48:19 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OImHO29280 for ; Tue, 24 Jul 2001 11:48:17 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OIqtm11348 for ; Tue, 24 Jul 2001 11:52:55 -0700 Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA12971 for ; Tue, 24 Jul 2001 11:52:49 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 5B67B15A47E for ; Tue, 24 Jul 2001 11:46:56 -0700 (PDT) Subject: Re: newer *.img files than XFS-1.0.1? From: Florin Andrei To: XFS list In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11 (Beta Release) Date: 24 Jul 2001 11:46:56 -0700 Message-Id: <996000416.2103.3.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 24 Jul 2001 09:21:51 -0700, Mike Sklar wrote: > > I am seeing the aic7xxx hangs on my VALinux 2200s using the bootnet.img > provided with XFS-1.0.1 release. It worked for me on some SGI 1200 systems. The trick is to use "text apic" or "linux apic" when the install diskette boots up. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Tue Jul 24 12:15:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OJF8U30692 for linux-xfs-outgoing; Tue, 24 Jul 2001 12:15:08 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OJF4O30671 for ; Tue, 24 Jul 2001 12:15:04 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA07316; Tue, 24 Jul 2001 21:15:02 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id VAA04126; Tue, 24 Jul 2001 21:15:02 +0200 (CEST) Date: Tue, 24 Jul 2001 21:15:02 +0200 (CEST) From: Seth Mos To: Mike Sklar cc: XFS list Subject: Re: newer *.img files than XFS-1.0.1? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 24 Jul 2001, Mike Sklar wrote: > > I am seeing the aic7xxx hangs on my VALinux 2200s using the bootnet.img > provided with XFS-1.0.1 release. > > This problem did not exist in the 1.0 release (for me), but those > older 1.0 images files have compatibility problems with the 1.0.1 > installer. I don't suppose a updated set of XFS supported *.img files > exists anywhere? I do recall that there was an update disk image placed on the FTP site But I can't recall were it exactly went. Your best bet would probably to go to http://marc.theaimsgroup.com/?l=linux-xfs&r=1&w=2 and search for update disk the second from the top (or 3rd after this one) lists the name and location :-) Good luck > > my scsi controller info (lspci -vv): > > 00:0c.0 SCSI storage controller: Adaptec 7896 > Subsystem: Adaptec: Unknown device 0053 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (9750ns min, 6250ns max), cache line size 08 > Interrupt: pin A routed to IRQ 19 > BIST result: 00 > Region 0: I/O ports at 2000 [disabled] [size=256] > Region 1: Memory at f4100000 (64-bit, non-prefetchable) [size=4K] > Expansion ROM at [disabled] [size=128K] > Capabilities: > > 00:0c.1 SCSI storage controller: Adaptec 7896 > Subsystem: Adaptec: Unknown device 0053 > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 64 (9750ns min, 6250ns max), cache line size 08 > Interrupt: pin A routed to IRQ 19 > BIST result: 00 > Region 0: I/O ports at 2400 [disabled] [size=256] > Region 1: Memory at f4101000 (64-bit, non-prefetchable) [size=4K] > Capabilities: > > From owner-linux-xfs@oss.sgi.com Tue Jul 24 12:27:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OJR7i31382 for linux-xfs-outgoing; Tue, 24 Jul 2001 12:27:07 -0700 Received: from mail15a.boca15-verio.com ([208.55.91.57]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OJR5O31360 for ; Tue, 24 Jul 2001 12:27:05 -0700 Received: from www.sigmastorage.com (128.241.173.170) by mail15a.boca15-verio.com (RS ver 1.0.60s) with SMTP id 017312031; Tue, 24 Jul 2001 15:26:49 -0400 (EDT) Message-ID: <3B5DCB73.73557EE8@sigmastorage.com> Date: Tue, 24 Jul 2001 12:24:35 -0700 From: Matt Ryan X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-2-june14 i686) X-Accept-Language: en MIME-Version: 1.0 To: Steve Lord CC: linux-xfs@oss.sgi.com Subject: Re: TAKE - fix raid5 journal problems References: <200107232258.f6NMwgk22946@jen.americas.sgi.com> <3B5CBF17.6090409@thebarn.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Loop-Detect: 1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >p.s. for those of you not following the discussion recently, the best >performance for raid5 is an external log on a non-raid5 device, raid1 >if you want to maintain the backup copy of the data. does this statement apply equally well to, say, the 1.01 release kernels, in addition to the cvs tree? thanks, Matt From owner-linux-xfs@oss.sgi.com Tue Jul 24 12:38:52 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OJcqr31773 for linux-xfs-outgoing; Tue, 24 Jul 2001 12:38:52 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OJcoO31754 for ; Tue, 24 Jul 2001 12:38:50 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id MAA15863 for ; Tue, 24 Jul 2001 12:38:38 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2514717; Tue, 24 Jul 2001 14:37:33 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA67295; Tue, 24 Jul 2001 14:37:32 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6OJbW626575; Tue, 24 Jul 2001 14:37:32 -0500 Message-Id: <200107241937.f6OJbW626575@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Matt Ryan cc: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: TAKE - fix raid5 journal problems In-Reply-To: Message from Matt Ryan of "Tue, 24 Jul 2001 12:24:35 PDT." <3B5DCB73.73557EE8@sigmastorage.com> Date: Tue, 24 Jul 2001 14:37:32 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >p.s. for those of you not following the discussion recently, the best > >performance for raid5 is an external log on a non-raid5 device, raid1 > >if you want to maintain the backup copy of the data. > > does this statement apply equally well to, say, the 1.01 release > kernels, > in addition to the cvs tree? Probably even more so, with a combination of local and remote access we managed to hang a 1.0.1 raid volume pretty hard. Steve > > thanks, > Matt From owner-linux-xfs@oss.sgi.com Tue Jul 24 13:17:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OKHCU00988 for linux-xfs-outgoing; Tue, 24 Jul 2001 13:17:12 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OKHAO00966 for ; Tue, 24 Jul 2001 13:17:11 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA19311; Tue, 24 Jul 2001 22:17:09 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA11883; Tue, 24 Jul 2001 22:17:09 +0200 (CEST) Date: Tue, 24 Jul 2001 22:17:08 +0200 (CEST) From: Seth Mos To: Matt Ryan cc: Steve Lord , linux-xfs@oss.sgi.com Subject: Re: TAKE - fix raid5 journal problems In-Reply-To: <3B5DCB73.73557EE8@sigmastorage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, 24 Jul 2001, Matt Ryan wrote: > >p.s. for those of you not following the discussion recently, the best > >performance for raid5 is an external log on a non-raid5 device, raid1 > >if you want to maintain the backup copy of the data. > > does this statement apply equally well to, say, the 1.01 release > kernels, > in addition to the cvs tree? Yes. Software raid5 that is. Cheers Seth From owner-linux-xfs@oss.sgi.com Tue Jul 24 13:27:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OKRaF01620 for linux-xfs-outgoing; Tue, 24 Jul 2001 13:27:36 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OKRYO01601 for ; Tue, 24 Jul 2001 13:27:34 -0700 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [137.38.226.97]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6OKWCm16858 for ; Tue, 24 Jul 2001 13:32:12 -0700 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.191.42]) by ledzep.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id PAA61667 for ; Tue, 24 Jul 2001 15:26:12 -0500 (CDT) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.22 #1 (Debian)) id 15P8ku-0001lg-00 for ; Tue, 24 Jul 2001 15:26:12 -0500 Date: Tue, 24 Jul 2001 15:26:11 -0500 From: Nathan Straz To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010724152611.G706@sgi.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241402.f6OE2qD24056@jen.americas.sgi.com> <20010724102533.F31186@dkp.com> <20010724093658.B706@sgi.com> <20010724101430.C706@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010724101430.C706@sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 10:14:30AM -0500, Nathan Straz wrote: > I'm going to work on running patch-2.4.7-xfs-2001-07-22 through some > regression tests and if I have time today I'll try to get the top of the > CVS tree built and tested too. I'll put out a quick report before I > leave for OLS. Okay here's what I've done so far: - SGI Regression suites on non-RAID, RAID1, and RAID5 * There is one new broken test program on RAID1 and RAID5. Don't panic, it was one of those rare test cases. The test program couldn't copy itself (while running) to the RAID device. I don't know what the error is because the test program doesn't display it. - cmd/xfstests, still running on non-RAID. No problems yet. * This will take a while longer to finish. I'll try to run it on RAID1 and RAID5 while on the road, but I won't know what network connectivity I'll have until I get to Ottawa. -- 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 Jul 24 14:11:11 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OLBBu03894 for linux-xfs-outgoing; Tue, 24 Jul 2001 14:11:11 -0700 Received: from d13.com ([216.33.170.30]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OLBAO03875 for ; Tue, 24 Jul 2001 14:11:10 -0700 Received: (qmail 678 invoked by uid 526); 24 Jul 2001 21:11:05 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Jul 2001 21:11:05 -0000 Date: Tue, 24 Jul 2001 14:11:05 -0700 (PDT) From: Mike Sklar X-X-Sender: To: XFS list Subject: Re: newer *.img files than XFS-1.0.1? In-Reply-To: <996000416.2103.3.camel@stantz.corp.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 24 Jul 2001, Florin Andrei wrote: > On 24 Jul 2001 09:21:51 -0700, Mike Sklar wrote: > > > > I am seeing the aic7xxx hangs on my VALinux 2200s using the bootnet.img > > provided with XFS-1.0.1 release. > > It worked for me on some SGI 1200 systems. The trick is to use "text > apic" or "linux apic" when the install diskette boots up. The apic appendage worked for my VALinux 1200s. thanks From owner-linux-xfs@oss.sgi.com Tue Jul 24 14:34:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6OLYTL05255 for linux-xfs-outgoing; Tue, 24 Jul 2001 14:34:29 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6OLYRO05234 for ; Tue, 24 Jul 2001 14:34:27 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6OLd5m21048 for ; Tue, 24 Jul 2001 14:39:05 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id HAA11022; Wed, 25 Jul 2001 07:33:02 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id HAA77729; Wed, 25 Jul 2001 07:33:01 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107250733.ZM233714@wobbly.melbourne.sgi.com> Date: Wed, 25 Jul 2001 07:32:59 +1000 In-Reply-To: "Juer Lee" "RE: Backup ACLs" (Jul 24, 4:57pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: "Juer Lee" Subject: Re: Backup ACLs Cc: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 24, 4:57pm, Juer Lee wrote: > Subject: RE: Backup ACLs > > > >> > > >> >Take a look on the ftp site, there is an rpm of 1.0.11 of > >xfsdump here: > >> > > >> >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ > >> > > >> >Try this version. > >> > > >> >Steve > >> > > >> Thanks. > >> > >> Ohmm, I have already downloaded it, but I failed to compile > >that version > >> on my machine (Power PC). So I used version 1.0.2 as I mentioned > >> before. Is it my version 2.95.2 GCC's problem?=20 > >> > >> Juer > > > >Hmm, we need more details than 'failed to compile' > > > >Steve > > > > When I compiled it, I got error message as > xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) > > Thougn I can modify some code for that, I am not sure if other problems > I will meet. > If you compile against the XFS headers from the current xfsprogs-devel rpms, you should find this problem goes away. The Debian porters came across this problem and helped fix it quite awhile ago now. You will then run into the next problem, which is that there are no syscall entry points for the ACL and extended attribute system calls for the PowerPC architecture, so you will need to make changes to your kernel and to the libattr & libacl source to implement this. I'm surprised that the test you did (from your original mail) didn't give you errors when you ran "chacl" the first time... did you not see an error like: "libacl: acl_set system call not defined for this architecture"? cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Jul 24 16:12:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ONC0t09599 for linux-xfs-outgoing; Tue, 24 Jul 2001 16:12:00 -0700 Received: from chopin.cipic.ucdavis.edu (chopin.cipic.ucdavis.edu [169.237.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ONBxO09580 for ; Tue, 24 Jul 2001 16:11:59 -0700 Received: from chopin.cipic.ucdavis.edu (localhost [127.0.0.1]) by chopin.cipic.ucdavis.edu (8.11.2/8.11.2) with ESMTP id f6ONBwp08810 for ; Tue, 24 Jul 2001 16:11:58 -0700 (PDT) Message-Id: <200107242311.f6ONBwp08810@chopin.cipic.ucdavis.edu> X-Mailer: exmh version 2.3.1 03/13/2001 with nmh-1.0.3 To: linux-xfs@oss.sgi.com Subject: Patching vanilla 2.4.7 kernel Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 24 Jul 2001 16:11:58 -0700 From: Zhi-Wei Lu Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi linux-xfs experts, I have downloaded and unpacked the vanilla Linux 2.4.7 kernel. I also have downloaded patch-xfs-1.0.1-only.gz and patch-2.4.7-xfs-2001-07-22.bz2. Which patch should I apply first? If I apply patch-2.4.7-xfs-2001-07-22 first and the apply patch patch-xfs-1.0.1-only, I am getting messages like: The next patch would create the file Documentation/filesystems/xfs.txt, which already exists! Assume -R? [n] What should I type y or n? Do I type y or n all the time? Thanks for clearing this up for me! -- Zhi-Wei Lu CIPIC (Center for Image Processing and Integrated Computing) UC Davis Phone: (530)-752-0494 Davis, CA 95616 Fax: (530)-752-8894 From owner-linux-xfs@oss.sgi.com Tue Jul 24 21:39:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6P4djk24075 for linux-xfs-outgoing; Tue, 24 Jul 2001 21:39:45 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6P4dhO24051 for ; Tue, 24 Jul 2001 21:39:43 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id VAA04933 for ; Tue, 24 Jul 2001 21:37:21 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA51257; Wed, 25 Jul 2001 14:38:23 +1000 (EST) Date: Wed, 25 Jul 2001 14:38:23 +1000 From: Timothy Shimmin To: Jim Eshleman Cc: linux-xfs@oss.sgi.com Subject: Re: xfsrestore assertion failure Message-ID: <20010725143822.A37341@boing.melbourne.sgi.com> References: <3B5D879A.E0FECD4E@Lehigh.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <3B5D879A.E0FECD4E@Lehigh.EDU>; from jce0@Lehigh.EDU on Tue, Jul 24, 2001 at 10:35:06AM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi Jim, Having a quick look at this code I don't know what is happening here. I haven't seen this before. However, I'll post an SGI bug and look at the code in more detail. During the restore you could turn on full debugging with -v5 and send me the last 100 lines or so of output leading up to the core dump and perhaps the first 100 lines. Thanks. Cheers, Tim. On Tue, Jul 24, 2001 at 10:35:06AM -0400, Jim Eshleman wrote: > Greets! I'm receiving the following error using xfsrestore: > > # xfsrestore -t -f /dev/st0 > xfsrestore: using online session inventory > xfsrestore: searching media for directory dump > xfsrestore: reading directories > xfsrestore: directory post-processing > xfsrestore: reading non-directory files > [...long list of files ...] > xfsrestore: examining media file 1 > xfsrestore: seeking past media file directory dump > xfsrestore: drive_scsitape.c:1461: do_next_mark: Assertion > `rechdrp->first_mark_offset - rechdrp->file_offset <= ( off64_t ) > ( contextp->dc_recsz )' failed. > Aborted (core dumped) > # > > This is happening on two different systems. System A is the stock SGI > RH7.1 XFS 1.0.1 distribution running on a dual P2-333 with a DLT4000 > drive. System B is RH7.1 + kernel 2.4.7 + > patch-2.4.7-xfs-2001-07-22.bz2 > running on a Netfinity x370 with a DLT7000. > > > I've tried specifying a block size of 240K on the dump and restore. > Same > result. > > The dump runs with no errors as "xfsdump -l 0 -o -f /dev/st0 -s userdir > /a" > where /a/userdir is about 1.2G. > From owner-linux-xfs@oss.sgi.com Tue Jul 24 23:04:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6P64DC28811 for linux-xfs-outgoing; Tue, 24 Jul 2001 23:04:13 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6P647O28782 for ; Tue, 24 Jul 2001 23:04:07 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.4) id f6P641C04674 for linux-xfs@oss.sgi.com; Wed, 25 Jul 2001 02:04:01 -0400 Date: Wed, 25 Jul 2001 02:04:01 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: kit to build RPMS from CVS tree Message-ID: <20010725020401.A4574@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've made available a kit to build rpms from the CVS source tree at: http://wwweasel.geeksrus.net/~alane/cvs-kit-20010725.tar.bz2 It provides automated scripts to update the tree and build rpms. YMMV. It works for me in a daily cron job. This is a 600K download. Here's the README: ---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<--- README.cvs-kit by Alan Eldridge ==================================================== This kit is the result of my quest to automate building new kernels from SGI's XFS-enhanced linux CVS tree. All spec files and patches were correct as of 20010725. The directory structure: SGI |-- cvs.yyyymmdd.hhmm |-- RPMS |-- SPECS | `-- orig |-- bin |-- cvs -> cvs.yyyymmdd.hhmm |-- patches | |-- acl | |-- attr | |-- dmapi | |-- linux | |-- xfsdump | `-- xfsprogs `-- src ******* A Quick Tour ==================== * SGI/cvs directory where CVS tree lives * SGI/RPMS/{yyyymmdd.nn}/log * SGI/RPMS/{yyyymmdd.nn}/list * SGI/RPMS/{yyyymmdd.nn}/RPMS * SGI/RPMS/{yyyymmdd.nn}/SRPMS directories where logs, file lists, RPMs, and SRPMs are stored after being built * SGI/SPECS the spec files used to build the packages * SGI/SPECS/orig original spec files (for reference) * SGI/bin scripts used to do automated build; this directory can be added to your PATH, or you can copy its contents to a directory already on your PATH * SGI/patches/* source and patch files for each package; these are copied to $rpmdir/SOURCES prior to a build * SGI/src/{yyyymmdd.hhmm} directory where source tarballs from the CVS tree live ******* The SGI/patches/linux directory ======================================= Most of these files are included in the source RPM used to make linux-2.4.5-SGI_XFS_1.0.1_PR1 (and PR2). Here's a quick rundown: Files from SGI_XFS_1.0.1_PR1: ============================= devfsd-v1.3.11.tar.gz devfs daemon source code installkernel kernel installation script kernel-2.4.5-i386-BOOT.config kernel-2.4.5-i386.config kernel-2.4.5-i386-smp.config kernel-2.4.5-i586.config kernel-2.4.5-i586-smp.config kernel-2.4.5-i686.config kernel-2.4.5-i686-enterprise.config kernel-2.4.5-i686-smp.config RH kernel config files modified for XFS linux-2.4.0-nonintconfig.patch patch to do non-interactive config (RedHat) kernel-2.4-BuildASM.sh linux-merge-config.awk linux-merge-modules.awk linux-rhconfig.h module-info README.kernel-sources miscellaneous files from RedHat's SRPM New files: ========== config-2.4.6pre5.defaults config-2.4.6pre7.defaults config-2.4.6pre9.defaults config-2.4.7pre3.defaults [ any newer config-*.defaults files ] additions to config files to provide default (disabled) values for new drivers added in post 2.4.5 releases ******* The scripts in SGI/bin ============================== Each of these scripts takes the path to the SGI directory (the root of this kit) as its first argument. xx-update-sources ================= usage: xx-update-sources project-dir [options] Options: -h,--help show this message -f,--force get a new source tree -F,--FORCE get a new source tree do NOT ask for confirmation -c,--cvs use CVS, not CVSup Notes: 1. CVS will be used if there is no file project-dir/project-dir.cvsup 2. To use CVS, the project-dir/config.sh must have a "CVSROOT=..." entry. 3. The "force" options will save any existing tree using the name "cvs.old". 4. The current tree will be named cvs.yyyymmdd.hh.mm, and a link "cvs" will be made to point to it. Addiitional notes: This script runs the "cvs" or "cvsup" program and gets the latest kernel changes from Russell's cvsup mirror. See the SGI XFS website for info on using CVSup or using anonymous CVS xx-tar-sources ============== usage: xx-tar-sources project-dir [-x|-X] [-dYYYYMMDD.HHMM] Options: -x previous tarballs for same day will be erased -z all previous tarballs (all days) will be erased -dYYYYMMDD.HHMM fake the update time to be YYYYMMDD.HHMM; for example, if it's 00:03 and you'd like to make tarballs for the previous day's date Addiitional notes: The tarballs will end up in SGI/src/yyyymmdd.hhmm, where yyyymmdd.hhmm is the date and time that xx-tar-sources was run. A link, SGI/src/yyyymmdd will be created to point to the actual directory. Another link, current, will point to the link above. xx-build-rpms ============= usage: xx-build-rpms project-dir [options] package ... Options: -h,--help show this message -k,--keep keep existing RPMS -s,--save-root save $RPM_BUILD_ROOT for debugging -oOption pass Option to rpm -rString set RPM release to String default = 0 -bp|-ba|-bb|-bs|-bc|-bi pass this build option to rpm default = -ba -dCCYYMMDD build from this date default = 20010725 Addiitional notes: This script builds rpms from the newest tarball available, or the newest tarball on the date given as an option. If a date is given as an option, it may be shortened as long as the menaing is clear; e.g., -708 means July 8. The option -bp may be given to just run the rpm "prep" stage for each package. This is to make sure that all patches still apply correctly. The generated rpms will be placed as follows: SGI/RPMS/yyyymmdd.r/list => file lists SGI/RPMS/yyyymmdd.r/RPMS => binary RPMs SGI/RPMS/yyyymmdd.r/SRPMS => source RPMs The ".r" suffix is a the release number for the generated RPMs, which can be given with the -r option to xx-build-rpms. The "file lists" are just the lists of files that were in the "install" directory when the RPM was made (e.g., linux-inst.files), and the list of files in the actual RPMS (e.g., linux-rpms.files). A file named "*,missing" (e.g., linux.missing) is created that lists any files that were orphaned (not placed in an RPM). If these "*.missing" files are not empty, it probably indicates a problem. xx-auto-update ============== Usage: xx-auto-update project-dir [options] action [option ...] ... Options: -h,--help show this message and exit -V,--version print program version and exit -v,--verbose verbose output -n,--test do not execute, just show what would be done Action Options: -E,--exec run an outside program -C,--cvs update from cvs/cvsup -U,--update same as -C, --cvs -T,--tar make source tarballs -x delete previous sources for today -X delete previous sources for all days -B,--build perform RPM build -rString set rpm release to String -b[abcips] use RPM build option -bx, where x in [abcips] -P,--purge purge *ALL* files from rpm build dir (e.g., /usr/src/redhat or $HOME/rpm) Actions are executed in the order specified. Execution stops if any step fails. So, for example: -C -T -x -B -bp -B -ba will update the sources, create tarballs, run a "prep" build to make sure no patches are broken, and then run a real build if the prep succeeded. set-spec-version ================ This program reads the spec files in the CVS tree and sets the version for the SGI RPMs accordingly. It does NOT set the version for the kernel RPMs. alane.misc.func.sh ================== A bunch of shell functions needed by the scripts. ******* The "config.sh" file ============================ This file contains variable definitions that control the operation of the xx-* scripts. If you think you need to change this, you should probably read the scripts first. ---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<--- -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Tue Jul 24 23:56:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6P6ugr32333 for linux-xfs-outgoing; Tue, 24 Jul 2001 23:56:42 -0700 Received: from ente.berdmann.de (p3E9E7248.dip.t-dialin.net [62.158.114.72]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6P6udO32304 for ; Tue, 24 Jul 2001 23:56:39 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15PIar-00026D-00; Wed, 25 Jul 2001 08:56:29 +0200 Message-ID: <3B5E6D9D.53541623@berdmann.de> Date: Wed, 25 Jul 2001 08:56:29 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: jrj@cc.purdue.edu CC: "amanda-users@amanda.org" , Linux XFS Mailing List Subject: Re: xfsdump estimates sometimes fail References: <200107232132.QAA03943@gandalf.cc.purdue.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >on a particular host (Linux 2.4.6-prexy-xfs, RH 7.1 + LVM + XFS, Amanda > >2.4.2p2) sometimes sendsize fails to estimate sizes with xfsdump. I recognized kernel oopses in syslog when Amanda tried to backup this host (maxdumps=3): Jul 24 00:45:28 somehost kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000008 Jul 24 00:45:28 somehost kernel: printing eip: Jul 24 00:45:28 somehost kernel: c018debf Jul 24 00:45:28 somehost kernel: *pde = 00000000 Jul 24 00:45:28 somehost kernel: Oops: 0000 Jul 24 00:45:28 somehost kernel: CPU: 0 Jul 24 00:45:28 somehost kernel: EIP: 0010:[xfs_itobp+303/464] Jul 24 00:45:28 somehost kernel: EIP: 0010:[] Jul 24 00:45:28 somehost kernel: EFLAGS: 00010246 Jul 24 00:45:28 somehost kernel: eax: 00000000 ebx: 00000010 ecx: 00000282 edx: dce9fadc Jul 24 00:45:28 somehost kernel: esi: 00000000 edi: ef0ae800 ebp: 00000000 esp: dce9fad0 Jul 24 00:45:28 somehost kernel: ds: 0018 es: 0018 ss: 0018 Jul 24 00:45:28 somehost kernel: Process xfsdump (pid: 20983, stackpage=dce9f000) Jul 24 00:45:28 somehost kernel: Stack: 005422a0 00000000 e5085e40 00000000 00000286 00020000 a845a000 00000202 Jul 24 00:45:28 somehost kernel: 005422a0 00000000 00000010 00028454 00000000 00000202 e44bf234 e5085e40 Jul 24 00:45:28 somehost kernel: e44bf234 00000000 00000000 dce9fc08 c0192fb5 ef0ae800 00000000 e44bf234 Jul 24 00:45:28 somehost kernel: Call Trace: [xfs_bulkstat+2293/3104] [xfs_ioctl+1615/4768] [xfs_bulkstat_one+0/1344] [_xfs_imap_to_bmap+55/688] [xfs_bmbt_get_state+37/48] [avl_remove+201/224] [__alloc_pages+116/640] Jul 24 00:45:28 somehost kernel: Call Trace: [] [] [] [] [] [] [] Jul 24 00:45:28 somehost kernel: [do_anonymous_page+54/144] [update_process_times+32/128] [update_wall_time+22/80] [timer_bh+36/592] [__delete_from_swap_cache+126/144] [handle_IRQ_event+58/112] [tasklet_hi_action+137/176] [__alloc_pages_limit+112/160] Jul 24 00:45:28 somehost kernel: [] [] [] [] [] [] [] [] Jul 24 00:45:29 somehost kernel: [__alloc_pages+191/640] [do_anonymous_page+54/144] [do_no_page+48/192] [handle_mm_fault+97/208] [__up_wakeup+8/20] [stext_lock+3185/9300] [_end_pagebuf_page_io_multi+253/272] [dump_thread+37/288] Jul 24 00:45:29 somehost kernel: [] [] [] [] [] [] [] [] Jul 24 00:45:29 somehost kernel: [linvfs_ioctl+45/64] [dump_thread+37/288] [dump_thread+37/288] [sys_ioctl+375/400] [dump_thread+37/288] [system_call+51/56] [dump_thread+37/288] Jul 24 00:45:29 somehost kernel: [] [] [] [] [] [] [] Jul 24 00:45:29 somehost kernel: Same occured this morning when I drove sendsize by hand with maxdumps=3 but not with maxdumps=1. Ok, I'll upgrade the kernel from 2.4.6-pre5-xfs to 2.4.7-xfs before any further investigation... From owner-linux-xfs@oss.sgi.com Wed Jul 25 02:08:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6P987X10671 for linux-xfs-outgoing; Wed, 25 Jul 2001 02:08:07 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6P984O10646 for ; Wed, 25 Jul 2001 02:08:04 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 1FCC663920; Wed, 25 Jul 2001 10:08:42 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 25 Jul 2001 10:12:44 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Wed, 25 Jul 2001 10:00:24 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUiGmRXddmcIeWSE6y/OTZgkRjWwAXpRjg From: "Juer Lee" To: "Nathan Scott" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6P985O10647 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >hi, > >On Jul 24, 4:57pm, Juer Lee wrote: >> Subject: RE: Backup ACLs >> > >> >> > >> >> >Take a look on the ftp site, there is an rpm of 1.0.11 of >> >xfsdump here: >> >> > >> >> >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ >> >> > >> >> >Try this version. >> >> > >> >> >Steve >> >> > >> >> Thanks. >> >> >> >> Ohmm, I have already downloaded it, but I failed to compile >> >that version >> >> on my machine (Power PC). So I used version 1.0.2 as I mentioned >> >> before. Is it my version 2.95.2 GCC's problem?=20 >> >> >> >> Juer >> > >> >Hmm, we need more details than 'failed to compile' >> > >> >Steve >> > >> >> When I compiled it, I got error message as >> xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) >> >> Thougn I can modify some code for that, I am not sure if >other problems >> I will meet. >> > >If you compile against the XFS headers from the current >xfsprogs-devel rpms, you should find this problem goes away. >The Debian porters came across this problem and helped fix it >quite awhile ago now. > >You will then run into the next problem, which is that there >are no syscall entry points for the ACL and extended attribute >system calls for the PowerPC architecture, so you will need to >make changes to your kernel and to the libattr & libacl source >to implement this. > >I'm surprised that the test you did (from your original mail) >didn't give you errors when you ran "chacl" the first time... >did you not see an error like: >"libacl: acl_set system call not defined for this architecture"? > >cheers. > >-- >Nathan > Nathan, Oh, yes, I have already changed those code for ACl, but I forgot to mention all since I just met the problems when using xfsdump. So you needn't feel strange :) I am now using xfsprogs 1.3.1, need I add xfsprogs-devel rpms? Under ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/, But I find xfsprogs-1,3,1-pre1.sc.rpm and xfsprogs-devel-1.3.1-pre1.i386.rpm only there. Which one should I use? Juer From owner-linux-xfs@oss.sgi.com Wed Jul 25 02:12:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6P9CKA11202 for linux-xfs-outgoing; Wed, 25 Jul 2001 02:12:20 -0700 Received: from ip075217.hkicable.com (ip075217.hkicable.com [203.83.75.217]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6P9CAO11162 for ; Wed, 25 Jul 2001 02:12:11 -0700 Message-Id: Date: Wed, 25 Jul 2001 17:14:01 +0800 (CST) To: linux-xfs@oss.sgi.com From: Hing.Lung.Motor.Mfy@oss.sgi.com, Reply-To: hlmotor@hkstar.com Subject: DC MOTOR SALE Organization: Hing Lung Motor Mfy, X-mailer: Trade-Navigator 4.0 [CN] X-Priority: 2 Mime-Version: 1.0 Content-Type: text/html; charset="BIG5" Content-Transfer-Encoding: base64 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk DQo8aHRtbD4NCg0KPE1FVEEgSFRUUC1FUVVJVj0iQ29udGVudC1UeXBlIiBD T05URU5UPSJ0ZXh0L2h0bWw7Y2hhcnNldD1nYjIzMTIiPg0KPG1ldGEgaHR0 cC1lcXVpdj0iQ29udGVudC1MYW5ndWFnZSIgY29udGVudD0iZW4tdXMiPg0K PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0 L2h0bWw7IGNoYXJzZXQ9YmlnNSI+DQo8bWV0YSBuYW1lPSJHRU5FUkFUT1Ii IGNvbnRlbnQ9Ik1pY3Jvc29mdCBGcm9udFBhZ2UgNC4wIj4NCjxtZXRhIG5h bWU9IlByb2dJZCIgY29udGVudD0iRnJvbnRQYWdlLkVkaXRvci5Eb2N1bWVu dCI+DQo8dGl0bGU+SGluZyBMdW5nIE1vdG9yIE1meTwvdGl0bGU+DQoNCjxi b2R5Pg0KDQoNCg0KPHA+PGI+PGk+PGZvbnQgc2l6ZT0iNiIgY29sb3I9IiNG RjAwMDAiPkhpbmcgTHVuZyBNb3RvciBNZnksJm5ic3A7PC9mb250Pjxmb250 IHNpemU9IjYiIGNvbG9yPSIjMDAwMEZGIj5OZXcgICAgICAgICAgICAgICAN Ck9mZmVyJm5ic3A7PC9mb250Pjxmb250IHNpemU9IjYiIGNvbG9yPSIjRkYw MDAwIj4mbmJzcDs8L2ZvbnQ+PGZvbnQgY29sb3I9IiNGRjAwMDAiPjxmb250 IHNpemU9IjYiPkp1bHktMjAwMTwvZm9udD48Zm9udCBzaXplPSIzIiBjb2xv cj0iIzAwMDAwMCI+Jm5ic3A7IDwvZm9udD48L2ZvbnQ+PC9pPjwvYj48L3A+ ICAgICAgICAgICANCjxwPjxpPjxiPjxmb250IGNvbG9yPSIjMDAwMDAwIiBz aXplPSIyIj5UZWw6ODUyLTI0MjE4MzA5Jm5ic3A7Jm5ic3A7RmF4Ojg1Mi0y NDgxNzE0OCZuYnNwOyZuYnNwOzwvZm9udD48L2I+PC9pPjxmb250IGNvbG9y PSIjMDAwMDAwIiBzaXplPSIzIj4mbmJzcDs8YSBocmVmPSJodHRwOi8vaGlu Z2x1bmdtb3Rvci5jb20uaGsiPiAgICAgICAgICANCjwvYT48YSBocmVmPSJo dHRwOi8vaGluZ2x1bmdtb3Rvci5jb20uaGsiPmh0dHA6Ly93d3cuaGluZ2x1 bmdtb3Rvci5jb20uaGs8L2E+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICAgICAgICAg ICANCjxhIGhyZWY9Im1haWx0bzpobG1vdG9yQGhrc3Rhci5jb20iPmhsbW90 b3JAaGtzdGFyLmNvbTwvYT4mbmJzcDsgPGEgaHJlZj0ibWFpbHRvOmhsbW90 b3JAaS1jYWJsZS5jb20iPmhsbW90b3JAaS1jYWJsZS5jb208L2E+PC9mb250 PjwvcD4gICAgICAgICAgDQo8dGFibGUgYm9yZGVyPSIxIiB3aWR0aD0iMTAw JSI+ICAgICAgICAgIA0KICA8dHI+ICAgICAgICAgIA0KICAgIDx0ZCB3aWR0 aD0iNTAlIj48aW1nIHNyYz0iaHR0cDovL2hrLmdlb2NpdGllcy5jb20vaGxt b3Rvci8xMDExLkpQRyIgd2lkdGg9IjEyOCIgaGVpZ2h0PSIxMTkiIGFsaWdu PSJsZWZ0Ij48Zm9udCBzaXplPSIyIj48aT5OTy4gICAgICAgDQogICAgICBI TDEwMTEtREMgU0NPT1RFUiBNT1RPUjwvaT48L2ZvbnQ+ICAgICAgIA0KICAg ICAgPHA+PGZvbnQgc2l6ZT0iMiI+PGk+U0laRTombmJzcDsgRDEwME1NIFgg SDcwTU08L2k+PC9mb250PjwvcD4gICAgICAgIA0KICAgICAgPHA+PGZvbnQg c2l6ZT0iMiI+PGk+T1VUUFVUOiZuYnNwOyZuYnNwOyA5NVc8L2k+PC9mb250 PjwvcD4gICAgICAgIA0KICAgICAgPHA+PGZvbnQgc2l6ZT0iMiI+PGk+UFJJ Q0U6IFVTJCAxMy4yMC9QQzwvaT48L2ZvbnQ+PC9wPiAgICAgIA0KICAgIDwv dGQ+ICAgICAgIA0KICAgIDx0ZCB3aWR0aD0iNTAlIj48aW1nIHNyYz0iaHR0 cDovL2hrLmdlb2NpdGllcy5jb20vaGxtb3Rvci8xMDFjLkpQRyIgd2lkdGg9 IjEzMiIgaGVpZ2h0PSI5OSIgYWxpZ249ImxlZnQiPjxpPjxmb250IHNpemU9 IjIiPk5PLiAgICAgICANCiAgICAgIEhMMTAxLUQtRDggWCBINiZuYnNwOyZu YnNwOyBWSUJSQVRFUjwvZm9udD48L2k+ICAgICAgIA0KICAgICAgPHA+PGk+ PGZvbnQgc2l6ZT0iMiI+U0laRTogMjBNTSBYIDE1LjVNTSBYIEgyNU1NPC9m b250PjwvaT48L3A+ICAgICAgDQogICAgICA8cD48aT48Zm9udCBzaXplPSIy Ij5QUklDRTogVVMkIDAuMTMvUEM8L2ZvbnQ+PC9pPjwvcD4gICAgIA0KICAg ICAgPHA+PGk+PGI+PGZvbnQgc2l6ZT0iMiI+Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7PC9mb250 PjwvYj48L2k+PC9wPiAgICANCiAgICA8L3RkPiAgICAgDQogIDwvdHI+ICAg ICANCjwvdGFibGU+ICAgICANCjx0YWJsZSBib3JkZXI9IjEiIHdpZHRoPSIx MDAlIj4gICAgIA0KICA8dHI+ICAgICANCiAgICA8dGQgd2lkdGg9IjUwJSI+ PGltZyBzcmM9Imh0dHA6Ly9oay5nZW9jaXRpZXMuY29tL2hsbW90b3IvZ2Vu LkpQRyIgd2lkdGg9IjEyOSIgaGVpZ2h0PSIxMDUiIGFsaWduPSJsZWZ0Ij48 Zm9udCBzaXplPSIyIj48aT5OTy4gICAgICANCiAgICAgIEhMMjAwJm5ic3A7 Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IC1HRU5FUkFU T1IgTU9UT1ItPC9pPjwvZm9udD4gICAgIA0KICAgICAgPHA+PGZvbnQgc2l6 ZT0iMiI+PGk+U0laRTombmJzcDsmbmJzcDsgRDMwLjVNTSBYIEgxM01NPC9p PjwvZm9udD48L3A+ICAgIA0KICAgICAgPHA+PGZvbnQgc2l6ZT0iMiI+PGk+ UFJJQ0U6Jm5ic3A7IFVTJCZuYnNwOyAyLjMwL1BDPC9pPjwvZm9udD48L3A+ ICAgICANCiAgICA8L3RkPiAgICAgICANCiAgICA8dGQgd2lkdGg9IjUwJSI+ ICAgICAgDQogICAgICA8cCBhbGlnbj0ibGVmdCI+PGk+PGltZyBzcmM9Imh0 dHA6Ly9oay5nZW9jaXRpZXMuY29tL2hsbW90b3IvMzA3LkpQRyIgd2lkdGg9 IjExMyIgaGVpZ2h0PSI3NCIgYWxpZ249ImxlZnQiPjxmb250IHNpemU9IjIi Pk5PLiAgICAgIA0KICAgICAgSEwzMDc8L2ZvbnQ+PC9pPjwvcD4gICAgICAN CiAgICAgIDxwIGFsaWduPSJsZWZ0Ij48aT48Zm9udCBzaXplPSIyIj5TSVpF OiZuYnNwOyBEMTJNTU0gWCZuYnNwOyBIMTkuNU1NPC9mb250PjwvaT48L3A+ ICAgICANCiAgICAgIDxwIGFsaWduPSJsZWZ0Ij48aT48Zm9udCBzaXplPSIy Ij4mbmJzcDtQUklDRTogVVMkIDAuMzgvUEM8L2ZvbnQ+PC9pPjwvcD4gICAg IA0KICAgIDwvdGQ+ICAgICAgDQogIDwvdHI+ICAgICAgDQo8L3RhYmxlPiAg ICAgIA0KPHRhYmxlIGJvcmRlcj0iMSIgd2lkdGg9IjEwMCUiPiAgICAgIA0K ICA8dHI+ICAgICAgDQogICAgPHRkIHdpZHRoPSIxMDAlIj48aW1nIHNyYz0i aHR0cDovL2hrLmdlb2NpdGllcy5jb20vaGxtb3Rvci9oaW5nMC5qcGciIGFs aWduPSJsZWZ0IiB3aWR0aD0iMjgzIiBoZWlnaHQ9IjM5MiI+ICAgDQogICAg ICA8cCBhbGlnbj0iY2VudGVyIj48Yj48Zm9udCBzaXplPSI1Ij48aT5XRSBQ Uk9EVUNFIE1PUkUgVEhBTiA1MCBESUZGRVJFTlQgICANCiAgICAgIERFU0lH TiBBTkQgU0laRSBPRiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBB Qy8gREMgTU9UT1JTLjwvaT48L2ZvbnQ+PC9iPjwvcD4gIA0KICAgICAgPHAg YWxpZ249ImNlbnRlciI+PGI+PGZvbnQgc2l6ZT0iNSI+PGk+VEhFWSBBUkUg U1VJVEFCTEUgRk9SIE9QRVJBVElORyAgIA0KICAgICAgVE9ZUywgSE9VU0VI T0xEIEFQUExJQU5DRVMsIFJFQ09SRFMsIFNDT09URVJTLCBWSUJSQVRPUiwg R0VORVJBVE9SIEVUQy48L2k+PC9mb250PjwvYj48L3A+ICANCiAgICAgIDxw IGFsaWduPSJjZW50ZXIiPjxpPjxmb250IHNpemU9IjUiPjxiPldFIEFSRSBT VVJFIFRIQVQgT1VSIFBST0RVQ1RTIFdJTEwgICANCiAgICAgIEJFIE1PU1Qg U1VJVEFCTEUgRk9SIFlPVSBBTkQgV0lMTCBERUZJTklURUxZIFNBVElTRlk8 L2I+PC9mb250PiZuYnNwOyZuYnNwOyZuYnNwOzxmb250IHNpemU9IjUiPjxi PiAgIA0KICAgICAgWU9VUiBSRVFVRVNULjwvYj48L2ZvbnQ+PC9pPjwvcD4g IA0KICAgICAgPHAgYWxpZ249ImNlbnRlciI+PGI+PGZvbnQgc2l6ZT0iNSI+ PGk+Jm5ic3A7PC9pPjwvZm9udD48L2I+PC9wPiAgDQogICAgICA8cD6hQDwv cD4gICANCiAgICA8L3RkPiAgICANCiAgPC90cj4gICAgDQo8L3RhYmxlPiAg ICANCiAgICANCiANCg0KPC9ib2R5PjwvaHRtbD4NCg== From owner-linux-xfs@oss.sgi.com Wed Jul 25 03:04:48 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PA4mu15148 for linux-xfs-outgoing; Wed, 25 Jul 2001 03:04:48 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PA4iO15120 for ; Wed, 25 Jul 2001 03:04:44 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 6ED00638BD; Wed, 25 Jul 2001 11:07:04 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 25 Jul 2001 11:11:06 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Wed, 25 Jul 2001 11:04:14 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUiGmRXddmcIeWSE6y/OTZgkRjWwAXpRjgAAJxENA= From: "Juer Lee" To: "Nathan Scott" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6PA4jO15121 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >-----Original Message----- >From: Juer Lee >Sent: 25 July 2001 10:00 >To: Nathan Scott >Cc: linux-xfs@oss.sgi.com >Subject: RE: Backup ACLs > > >> >>hi, >> >>On Jul 24, 4:57pm, Juer Lee wrote: >>> Subject: RE: Backup ACLs >>> > >>> >> > >>> >> >Take a look on the ftp site, there is an rpm of 1.0.11 of >>> >xfsdump here: >>> >> > >>> >> >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ >>> >> > >>> >> >Try this version. >>> >> > >>> >> >Steve >>> >> > >>> >> Thanks. >>> >> >>> >> Ohmm, I have already downloaded it, but I failed to compile >>> >that version >>> >> on my machine (Power PC). So I used version 1.0.2 as I mentioned >>> >> before. Is it my version 2.95.2 GCC's problem?=20 >>> >> >>> >> Juer >>> > >>> >Hmm, we need more details than 'failed to compile' >>> > >>> >Steve >>> > >>> >>> When I compiled it, I got error message as >>> xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) >>> >>> Thougn I can modify some code for that, I am not sure if >>other problems >>> I will meet. >>> >> >>If you compile against the XFS headers from the current >>xfsprogs-devel rpms, you should find this problem goes away. >>The Debian porters came across this problem and helped fix it >>quite awhile ago now. >> >>You will then run into the next problem, which is that there >>are no syscall entry points for the ACL and extended attribute >>system calls for the PowerPC architecture, so you will need to >>make changes to your kernel and to the libattr & libacl source >>to implement this. >> >>I'm surprised that the test you did (from your original mail) >>didn't give you errors when you ran "chacl" the first time... >>did you not see an error like: >>"libacl: acl_set system call not defined for this architecture"? >> >>cheers. >> >>-- >>Nathan >> >Nathan, > >Oh, yes, I have already changed those code for ACl, but I forgot to >mention all since I just met the problems when using xfsdump. So you >needn't feel strange :) >I am now using xfsprogs 1.3.1, need I add xfsprogs-devel rpms? >Under ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/, But I find >xfsprogs-1,3,1-pre1.sc.rpm and xfsprogs-devel-1.3.1-pre1.i386.rpm only >there. Which one should I use? > >Juer > I tried to use a different version of xfs-progs-devel, 1.1.3.0-ppc. It still didn't work.:( Juer From owner-linux-xfs@oss.sgi.com Wed Jul 25 03:51:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PApXE18964 for linux-xfs-outgoing; Wed, 25 Jul 2001 03:51:33 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PApTO18942 for ; Wed, 25 Jul 2001 03:51:30 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 623C36394A; Wed, 25 Jul 2001 11:53:41 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 25 Jul 2001 11:57:43 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Wed, 25 Jul 2001 11:51:19 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUiGmRXddmcIeWSE6y/OTZgkRjWwAXpRjgAAJxENAAAXM20A== From: "Juer Lee" To: "Steve Lord" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6PApUO18943 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >>> >>>hi, >>> >>>On Jul 24, 4:57pm, Juer Lee wrote: >>>> Subject: RE: Backup ACLs >>>> > >>>> >> > >>>> >> >Take a look on the ftp site, there is an rpm of 1.0.11 of >>>> >xfsdump here: >>>> >> > >>>> >> >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ >>>> >> > >>>> >> >Try this version. >>>> >> > >>>> >> >Steve >>>> >> > >>>> >> Thanks. >>>> >> >>>> >> Ohmm, I have already downloaded it, but I failed to compile >>>> >that version >>>> >> on my machine (Power PC). So I used version 1.0.2 as I >mentioned >>>> >> before. Is it my version 2.95.2 GCC's problem?=20 >>>> >> >>>> >> Juer >>>> > >>>> >Hmm, we need more details than 'failed to compile' >>>> > >>>> >Steve >>>> > >>>> >>>> When I compiled it, I got error message as >>>> xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) >>>> >>>> Thougn I can modify some code for that, I am not sure if >>>other problems >>>> I will meet. >>>> >>> >>>If you compile against the XFS headers from the current >>>xfsprogs-devel rpms, you should find this problem goes away. >>>The Debian porters came across this problem and helped fix it >>>quite awhile ago now. >>> >>>You will then run into the next problem, which is that there >>>are no syscall entry points for the ACL and extended attribute >>>system calls for the PowerPC architecture, so you will need to >>>make changes to your kernel and to the libattr & libacl source >>>to implement this. >>> >>>I'm surprised that the test you did (from your original mail) >>>didn't give you errors when you ran "chacl" the first time... >>>did you not see an error like: >>>"libacl: acl_set system call not defined for this architecture"? >>> >>>cheers. >>> >>>-- >>>Nathan >>> >>Nathan, >> >>Oh, yes, I have already changed those code for ACl, but I forgot to >>mention all since I just met the problems when using xfsdump. So you >>needn't feel strange :) >>I am now using xfsprogs 1.3.1, need I add xfsprogs-devel rpms? >>Under ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/, But I find >>xfsprogs-1,3,1-pre1.sc.rpm and xfsprogs-devel-1.3.1-pre1.i386.rpm only >>there. Which one should I use? >> >>Juer >> > >I tried to use a different version of xfs-progs-devel, 1.1.3.0-ppc. It >still didn't work.:( > >Juer > I used some foolish ways to solve that compiling problem, it works. But when I run xfsrestore, I got WARNING like : xfsrestore: WARNINING: unable to set root extended attribute for 'test': Function not implemented (38) --- 'test' is a directory I created with some ACLs before I run command xfsdump. After I restore them, I can't get the ACLs for them. I think it just that WARNINING means.Right? I am sure that my kernel has XFS patched already. My question is: How can I fix it? Juer From owner-linux-xfs@oss.sgi.com Wed Jul 25 04:46:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PBkQt24954 for linux-xfs-outgoing; Wed, 25 Jul 2001 04:46:26 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PBkOO24935 for ; Wed, 25 Jul 2001 04:46:24 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6PBo1U14558 for ; Wed, 25 Jul 2001 04:50:01 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id GAA2523615; Wed, 25 Jul 2001 06:45:02 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id GAA71212; Wed, 25 Jul 2001 06:45:02 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6PBit729490; Wed, 25 Jul 2001 06:44:55 -0500 Message-Id: <200107251144.f6PBit729490@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Zhi-Wei Lu cc: linux-xfs@oss.sgi.com Subject: Re: Patching vanilla 2.4.7 kernel In-Reply-To: Message from Zhi-Wei Lu of "Tue, 24 Jul 2001 16:11:58 PDT." <200107242311.f6ONBwp08810@chopin.cipic.ucdavis.edu> Date: Wed, 25 Jul 2001 06:44:55 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi linux-xfs experts, > > I have downloaded and unpacked the vanilla Linux 2.4.7 kernel. > I also have downloaded patch-xfs-1.0.1-only.gz and > patch-2.4.7-xfs-2001-07-22.bz2. > > Which patch should I apply first? > If I apply patch-2.4.7-xfs-2001-07-22 first and the apply patch > patch-xfs-1.0.1-only, I am getting messages like: > > The next patch would create the file Documentation/filesystems/xfs.txt, > which already exists! Assume -R? [n] > > What should I type y or n? Do I type y or n all the time? The patch-2.4.7-xfs-2001-07-22.bz2 patch includes everything you need, the patch-xfs-1.0.1-only is not required. Steve > > Thanks for clearing this up for me! > > > -- > Zhi-Wei Lu > CIPIC (Center for Image Processing and Integrated Computing) > UC Davis Phone: (530)-752-0494 > Davis, CA 95616 Fax: (530)-752-8894 > From owner-linux-xfs@oss.sgi.com Wed Jul 25 05:33:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PCXVY29387 for linux-xfs-outgoing; Wed, 25 Jul 2001 05:33:31 -0700 Received: from smtpstore.strencom.net ([217.75.0.68]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PCXRO29367 for ; Wed, 25 Jul 2001 05:33:27 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 216C463953 for ; Wed, 25 Jul 2001 13:35:47 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 25 Jul 2001 13:39:49 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Wed, 25 Jul 2001 13:33:04 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEUiGmRXddmcIeWSE6y/OTZgkRjWwAXpRjgAAJxENAAAXM20AADq/Hw From: "Juer Lee" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6PCXSO29368 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >-----Original Message----- >From: Juer Lee >Sent: 25 July 2001 11:51 >To: Steve Lord >Cc: linux-xfs@oss.sgi.com >Subject: RE: Backup ACLs > > >> >>>> >>>>hi, >>>> >>>>On Jul 24, 4:57pm, Juer Lee wrote: >>>>> Subject: RE: Backup ACLs >>>>> > >>>>> >> > >>>>> >> >Take a look on the ftp site, there is an rpm of 1.0.11 of >>>>> >xfsdump here: >>>>> >> > >>>>> >> >ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/ >>>>> >> > >>>>> >> >Try this version. >>>>> >> > >>>>> >> >Steve >>>>> >> > >>>>> >> Thanks. >>>>> >> >>>>> >> Ohmm, I have already downloaded it, but I failed to compile >>>>> >that version >>>>> >> on my machine (Power PC). So I used version 1.0.2 as I >>mentioned >>>>> >> before. Is it my version 2.95.2 GCC's problem?=20 >>>>> >> >>>>> >> Juer >>>>> > >>>>> >Hmm, we need more details than 'failed to compile' >>>>> > >>>>> >Steve >>>>> > >>>>> >>>>> When I compiled it, I got error message as >>>>> xfs_fsr.c:156: 'O_DIRECT' undeclared here (not in a function) >>>>> >>>>> Thougn I can modify some code for that, I am not sure if >>>>other problems >>>>> I will meet. >>>>> >>>> >>>>If you compile against the XFS headers from the current >>>>xfsprogs-devel rpms, you should find this problem goes away. >>>>The Debian porters came across this problem and helped fix it >>>>quite awhile ago now. >>>> >>>>You will then run into the next problem, which is that there >>>>are no syscall entry points for the ACL and extended attribute >>>>system calls for the PowerPC architecture, so you will need to >>>>make changes to your kernel and to the libattr & libacl source >>>>to implement this. >>>> >>>>I'm surprised that the test you did (from your original mail) >>>>didn't give you errors when you ran "chacl" the first time... >>>>did you not see an error like: >>>>"libacl: acl_set system call not defined for this architecture"? >>>> >>>>cheers. >>>> >>>>-- >>>>Nathan >>>> >>>Nathan, >>> >>>Oh, yes, I have already changed those code for ACl, but I forgot to >>>mention all since I just met the problems when using xfsdump. So you >>>needn't feel strange :) >>>I am now using xfsprogs 1.3.1, need I add xfsprogs-devel rpms? >>>Under ftp://oss.sgi.com/projects/xfs/download/cmd_rpms/, But I find >>>xfsprogs-1,3,1-pre1.sc.rpm and >xfsprogs-devel-1.3.1-pre1.i386.rpm only >>>there. Which one should I use? >>> >>>Juer >>> >> >>I tried to use a different version of xfs-progs-devel, 1.1.3.0-ppc. It >>still didn't work.:( >> >>Juer >> > >I used some foolish ways to solve that compiling problem, it works. >But when I run xfsrestore, I got WARNING like : >xfsrestore: WARNINING: unable to set root extended attribute >for 'test': >Function not implemented (38) >--- 'test' is a directory I created with some ACLs before I >run command >xfsdump. >After I restore them, I can't get the ACLs for them. I think it just >that WARNINING means.Right? >I am sure that my kernel has XFS patched already. > >My question is: >How can I fix it? > >Juer > > I think that WARNNING is from 'attr_set' function,because I compiled attr-1.0.3, when I want to list the attributes of a directory, I got the same error message... It's PPC's problem as ACL I think. But does it affect ACLs? I am confusing. I mean that I couldn't get error or warning message of ACL. Juer From owner-linux-xfs@oss.sgi.com Wed Jul 25 05:43:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PChSx30295 for linux-xfs-outgoing; Wed, 25 Jul 2001 05:43:28 -0700 Received: from rain.CC.Lehigh.EDU (rain.CC.Lehigh.EDU [128.180.39.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PChPO30270 for ; Wed, 25 Jul 2001 05:43:25 -0700 Received: from Lehigh.EDU (hooch.CC.Lehigh.EDU [128.180.3.11]) by rain.CC.Lehigh.EDU (8.11.2/8.11.2) with ESMTP id f6PChG406259; Wed, 25 Jul 2001 08:43:16 -0400 Message-ID: <3B5EBC8F.E3B05ED1@Lehigh.EDU> Date: Wed, 25 Jul 2001 08:33:19 -0400 From: Jim Eshleman X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Timothy Shimmin CC: linux-xfs@oss.sgi.com Subject: Re: xfsrestore assertion failure References: <3B5D879A.E0FECD4E@Lehigh.EDU> <20010725143822.A37341@boing.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Thanks Tim. I also tried the xfsdump-1.0.11 tarball with the same results. I'm sending you the output directly. Let me know if you need anything else. Jim > Hi Jim, > > Having a quick look at this code I don't know what > is happening here. I haven't seen this before. > However, I'll post an SGI bug and look at the > code in more detail. > > During the restore you could turn on full debugging > with -v5 and send me the last 100 lines or so of output > leading up to the core dump and perhaps the first 100 lines. > Thanks. > > Cheers, > Tim. > > On Tue, Jul 24, 2001 at 10:35:06AM -0400, Jim Eshleman wrote: > > Greets! I'm receiving the following error using xfsrestore: > > > > # xfsrestore -t -f /dev/st0 > > xfsrestore: using online session inventory > > xfsrestore: searching media for directory dump > > xfsrestore: reading directories > > xfsrestore: directory post-processing > > xfsrestore: reading non-directory files > > [...long list of files ...] > > xfsrestore: examining media file 1 > > xfsrestore: seeking past media file directory dump > > xfsrestore: drive_scsitape.c:1461: do_next_mark: Assertion > > `rechdrp->first_mark_offset - rechdrp->file_offset <= ( off64_t ) > > ( contextp->dc_recsz )' failed. > > Aborted (core dumped) > > # > > > > This is happening on two different systems. System A is the stock SGI > > RH7.1 XFS 1.0.1 distribution running on a dual P2-333 with a DLT4000 > > drive. System B is RH7.1 + kernel 2.4.7 + > > patch-2.4.7-xfs-2001-07-22.bz2 > > running on a Netfinity x370 with a DLT7000. > > > > > > I've tried specifying a block size of 240K on the dump and restore. > > Same > > result. > > > > The dump runs with no errors as "xfsdump -l 0 -o -f /dev/st0 -s userdir > > /a" > > where /a/userdir is about 1.2G. > > From owner-linux-xfs@oss.sgi.com Wed Jul 25 07:47:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PEllV10528 for linux-xfs-outgoing; Wed, 25 Jul 2001 07:47:47 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PElkO10509 for ; Wed, 25 Jul 2001 07:47:46 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id HAA25324 for ; Wed, 25 Jul 2001 07:47:34 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2521556; Wed, 25 Jul 2001 09:46:29 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA96532; Wed, 25 Jul 2001 09:46:29 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6PEkLL02425; Wed, 25 Jul 2001 09:46:21 -0500 Message-Id: <200107251446.f6PEkLL02425@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Juer Lee" cc: linux-xfs@oss.sgi.com Subject: Re: Backup ACLs In-Reply-To: Message from "Juer Lee" of "Wed, 25 Jul 2001 13:33:04 BST." Date: Wed, 25 Jul 2001 09:46:20 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Attempting to respond to several messages here..... The devel part of the various user space packages is included in the one source package, it is just a different build target. If you use the Makepkg script it builds the devel rpms, if you just use make there is an install-dev target. You said that you had implemented the system calls for acls and extended attributes for the powerpc platform, I presume you have the user space changes as well so that the library calls in the acl package work. I would concentrate on getting the chacl command to work in all modes before moving to xfsdump/restore. Make sure that the system call numbers at the end of acl/libacl/acl.c are defined correctly for the ppc. Finally make sure you are linking xfsdump with the modified libacl. OK, mostly fairly obvious stuff. Oh, and when you have kernel and user space working for ppc, can you send in a patch so we can add the support to the packages on oss. Thanks Steve From owner-linux-xfs@oss.sgi.com Wed Jul 25 12:30:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PJUiX20664 for linux-xfs-outgoing; Wed, 25 Jul 2001 12:30:44 -0700 Received: from user4.orgio.net (root@[211.115.216.234]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PJUfO20643 for ; Wed, 25 Jul 2001 12:30:41 -0700 Received: (from nobody@localhost) by user4.orgio.net (8.9.3/8.9.3) id EAA25532 for linux-xfs@oss.sgi.com.outgoing; Thu, 26 Jul 2001 04:30:34 +0900 Message-Id: <200107251930.EAA25532@user4.orgio.net> Received: (from nobody@localhost) by user4.orgio.net (8.9.3/8.9.3) id EAA25528; Thu, 26 Jul 2001 04:30:34 +0900 From: "¿À½Â¿µ" To: linux-xfs@oss.sgi.com Subject: about the new 1.0.1 installer update disk X-Priority: 3 MIME-Version: 1.0 Date: Thu, 26 Jul 2001 04:30:34 KST Content-Type: text/html; X-Mailer: Orgio Mail Webmail Interface Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Since I don't use RAID now, my concern is; Do not use labels on XFS partitions to avoid running into 12 character limit. What does it mean? Sorry if this is a stupid question... I'm new at this :-) I'd appreciate any input. Thank you.
    From owner-linux-xfs@oss.sgi.com Wed Jul 25 12:52:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PJqOe22723 for linux-xfs-outgoing; Wed, 25 Jul 2001 12:52:24 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PJqLO22701 for ; Wed, 25 Jul 2001 12:52:21 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id VAA73093 for ; Wed, 25 Jul 2001 21:51:54 +0200 (CEST) mail_from (tbd@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2497416; Wed, 25 Jul 2001 14:51:02 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA67652; Wed, 25 Jul 2001 14:51:02 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id OAA56131; Wed, 25 Jul 2001 14:51:01 -0500 (CDT) Message-Id: <200107251951.OAA56131@fsgi158.americas.sgi.com> Subject: Re: about the new 1.0.1 installer update disk To: so1713@orgio.net (¿À½Â¿µ) Date: Wed, 25 Jul 2001 14:51:00 -0500 (CDT) Cc: linux-xfs@oss.sgi.com In-Reply-To: <200107251930.EAA25532@user4.orgio.net> from "¿À½Â¿µ" at Jul 26, 2001 04:30:34 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Do not use labels on XFS partitions to avoid running into 12 character limit. > > What does it mean? Sorry if this is a stupid question... I'm new at this :-) > I'd appreciate any input. Thank you. > The -L parameter on mkfs.xfs (refer to the man page) which can then be used on the mount command. Tad From owner-linux-xfs@oss.sgi.com Wed Jul 25 13:07:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PK7al24199 for linux-xfs-outgoing; Wed, 25 Jul 2001 13:07:36 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PK7ZO24180 for ; Wed, 25 Jul 2001 13:07:35 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id NAA01283 for ; Wed, 25 Jul 2001 13:07:23 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id NAA01430; Wed, 25 Jul 2001 13:06:54 -0700 (PDT) Message-ID: <3B5F2644.190762C8@sgi.com> Date: Wed, 25 Jul 2001 15:04:20 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Tad Dolphay CC: =?iso-8859-1?Q?=BF=C0=BD=C2=BF=B5?= , linux-xfs@oss.sgi.com Subject: Re: about the new 1.0.1 installer update disk References: <200107251951.OAA56131@fsgi158.americas.sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Tad Dolphay wrote: > The -L parameter on mkfs.xfs (refer to the man page) which can then be used on > the mount command. Yep, and implementing this in the installer was a bit trickier than expected, so the ISO image won't install if you have a mount point with more than 12 characters in it. So, this update disk fixes that problem. However, if you just have short, standard, [/boot / /usr /usr/local etc] mountpoints, it shouldn't be an issue for you. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Wed Jul 25 15:13:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PMDLJ06057 for linux-xfs-outgoing; Wed, 25 Jul 2001 15:13:21 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PMDGO06024 for ; Wed, 25 Jul 2001 15:13:17 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id AAA80038 for ; Thu, 26 Jul 2001 00:12:48 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 IAA19348; Thu, 26 Jul 2001 08:11:51 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id IAA36885; Thu, 26 Jul 2001 08:11:48 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107260811.ZM177430@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 08:11:45 +1000 In-Reply-To: Steve Lord "Re: Backup ACLs" (Jul 25, 9:46am) References: <200107251446.f6PEkLL02425@jen.americas.sgi.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: "Juer Lee" Subject: Re: Backup ACLs Cc: linux-xfs@oss.sgi.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 25, 9:46am, Steve Lord wrote: > Subject: Re: Backup ACLs > ... > You said that you had implemented the system calls for acls and > extended attributes for the powerpc platform, I presume you have the > user space changes as well so that the library calls in the acl > package work. I would concentrate on getting the chacl command > to work in all modes before moving to xfsdump/restore. Make sure > that the system call numbers at the end of acl/libacl/acl.c are > defined correctly for the ppc. > > Finally make sure you are linking xfsdump with the modified libacl. > > OK, mostly fairly obvious stuff. > Yup, good summary - one extra thing though - you must also have a working attr command (once you have chacl working), otherwise xfsdump/restore are not going to be able to backup your ACLs (as these link with libattr - attr/libattr/attr.c - rather than libacl). On Jul 25, 11:51am, Juer Lee wrote: > Subject: RE: Backup ACLs >I tried to use a different version of xfs-progs-devel, 1.1.3.0-ppc. It >still didn't work.:( Can you verify whether your /usr/include/xfs/platform_defs.h has references to O_DIRECT or not for powerpc (around line 58)? I'd like to understand why this doesn't work for you, because it should. Could you post the gcc error & that header to me? thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Wed Jul 25 16:17:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6PNHGl15002 for linux-xfs-outgoing; Wed, 25 Jul 2001 16:17:16 -0700 Received: from mailhost.idcomm.com (mailhost.idcomm.com [207.40.196.14]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6PNHFO14979 for ; Wed, 25 Jul 2001 16:17:15 -0700 Received: from idcomm.com (IDENT:5lolVcK0boYqxc+ow7k72dFSa+WAahx9@k56-pip12.idcomm.com [209.60.72.139]) by mailhost.idcomm.com (8.10.2/8.10.0) with ESMTP id f6PNM8I24061 for ; Wed, 25 Jul 2001 17:22:09 -0600 Message-ID: <3B5F5386.83A0B0B7@idcomm.com> Date: Wed, 25 Jul 2001 17:17:26 -0600 From: "D. Stimits" Reply-To: stimits@idcomm.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.6-pre1-xfs-4 i686) X-Accept-Language: en MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: about the new 1.0.1 installer update disk References: <200107251930.EAA25532@user4.orgio.net> Content-Type: text/plain; charset=iso-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.idcomm.com id f6PNM8I24061 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6PNHFO14984 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "¿À½Â¿µ" wrote: > > [Image] > > Hello, > Since I don't use RAID now, my concern is; > > Do not use labels on XFS partitions to avoid running into 12 character limit. > > What does it mean? Sorry if this is a stupid question... I'm new at this :-) > I'd appreciate any input. Thank you. > > I don't know why, by the message I am replying to, when I try to read it, triggers an attempt to access an outside web site, 211.115.216.234, which traceroutes to the origio.net in the header. I find it a bit disconcerting when something is embedded in email that otherwise appears to be plain text, and it attempts to open a web site. I even have the /16 banned for both input and output due to the number of scans I received from this. Lately I have found it pays to be careful, and I wonder what goes on. D. Stimits, stimits@idcomm.com From owner-linux-xfs@oss.sgi.com Wed Jul 25 17:39:59 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q0dxM25405 for linux-xfs-outgoing; Wed, 25 Jul 2001 17:39:59 -0700 Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q0dvO25386 for ; Wed, 25 Jul 2001 17:39:57 -0700 Received: by lists.samba.org (Postfix, from userid 1002) id 26B7B4603; Wed, 25 Jul 2001 17:34:54 -0700 (PDT) From: Andrew Tridgell To: linux-xfs@oss.sgi.com Subject: umask bug Reply-To: tridge@valinux.com Message-Id: <20010726003454.26B7B4603@lists.samba.org> Date: Wed, 25 Jul 2001 17:34:54 -0700 (PDT) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm testing SPECsfs against the 2.4.7 cvs XFS patch and it's failing the validation phase. The problem is that directories are being created with the wrong permissions. You can see it like this: mount localhost:/export /mnt cd /mnt umask 0 mkdir foo ls -ld foo I thought initially it was a nfsd bug, perhaps getting the umask wrong, but I found that the bug doesn't happen with ext2. Also, creating files does get the right permisisons, but directories are wrong. Any ideas? Known problem perhaps? I'm new to XFS. Cheers, Tridge From owner-linux-xfs@oss.sgi.com Wed Jul 25 17:52:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q0qWT26976 for linux-xfs-outgoing; Wed, 25 Jul 2001 17:52:32 -0700 Received: from afara-gw.afara.com (mx1.afara.com [63.113.218.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q0qVO26955 for ; Wed, 25 Jul 2001 17:52:31 -0700 Received: from tduffy-lnx.afara.com ([10.2.4.191]) by afara-gw.afara.com with Microsoft SMTPSVC(5.0.2195.1600); Wed, 25 Jul 2001 17:49:30 -0700 Subject: Re: about the new 1.0.1 installer update disk From: Thomas Duffy To: stimits@idcomm.com Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B5F5386.83A0B0B7@idcomm.com> References: <200107251930.EAA25532@user4.orgio.net> <3B5F5386.83A0B0B7@idcomm.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11.99 (Preview Release) Date: 25 Jul 2001 17:52:41 -0700 Message-Id: <996108761.23081.17.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 X-OriginalArrivalTime: 26 Jul 2001 00:49:30.0920 (UTC) FILETIME=[D484AA80:01C1156C] Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk if you look at the source of the email, it has two urls embedded in it... and interesting enough, the xmailer shows X-Mailer: Orgio Mail Webmail Interface so, this mailer must be trying to stick adds into its emails...yuck! -tduffy From owner-linux-xfs@oss.sgi.com Wed Jul 25 17:53:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q0r3J27161 for linux-xfs-outgoing; Wed, 25 Jul 2001 17:53:03 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q0r1O27141 for ; Wed, 25 Jul 2001 17:53:01 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 0D1691AB10 for ; Wed, 25 Jul 2001 20:53:01 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 21B7C828; Wed, 25 Jul 2001 20:52:59 -0400 (EDT) Date: Wed, 25 Jul 2001 20:52:59 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010725205259.C2291@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Tue, Jul 24, 2001 at 08:52:35AM -0500, Steve Lord wrote: > So a mkfs line along the lines of: > > mkfs -t xfs -f -i size=512 -l size=16384b /dev/xxx Hmmm. size 16384b specified for log subvolume is too large, maximum is 16032 blocks Is this a hard limit? (This is with the latest mkfs from a CVS from today.) Andrew Klaassen From owner-linux-xfs@oss.sgi.com Wed Jul 25 19:07:41 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q27fE01847 for linux-xfs-outgoing; Wed, 25 Jul 2001 19:07:41 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q27cV01818 for ; Wed, 25 Jul 2001 19:07:38 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 8372C1AB10 for ; Wed, 25 Jul 2001 22:07:32 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 1AE83828; Wed, 25 Jul 2001 22:07:32 -0400 (EDT) Date: Wed, 25 Jul 2001 22:07:32 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: about the new 1.0.1 installer update disk Message-ID: <20010725220731.A13260@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107251930.EAA25532@user4.orgio.net> <3B5F5386.83A0B0B7@idcomm.com> <996108761.23081.17.camel@tduffy-lnx.afara.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <996108761.23081.17.camel@tduffy-lnx.afara.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 25, 2001 at 05:52:41PM -0700, Thomas Duffy wrote: > if you look at the source of the email, it has two urls > embedded in it... There was an interesting attack described on BugTraq recently in which the possibility of embedding a link in an email image tag to anything you've got autologin from your browser set up for was discussed. The most interesting musing was something like embedding a "sell stock X" link or the like in an image tag; you'd simply have to open the email for reading and, if you've made things more convenient for yourself by having your password remembered by your browser/email client, the stock would be sold, without your knowledge or consent (or, for that matter, the attacker's knowledge). I've obviously simplified, and I've obviously drifted off topic. Those interested might like to check out the full discussion: http://www.securityfocus.com/templates/archive.pike?list=1&mid=191390 Andrew Klaassen From owner-linux-xfs@oss.sgi.com Wed Jul 25 19:29:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q2TOd03756 for linux-xfs-outgoing; Wed, 25 Jul 2001 19:29:24 -0700 Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q2TLV03737 for ; Wed, 25 Jul 2001 19:29:21 -0700 Received: by lists.samba.org (Postfix, from userid 1002) id ECC8144E0; Wed, 25 Jul 2001 19:24:17 -0700 (PDT) From: Andrew Tridgell To: linux-xfs@oss.sgi.com Subject: umask fix (patch) Reply-To: tridge@valinux.com Message-Id: <20010726022417.ECC8144E0@lists.samba.org> Date: Wed, 25 Jul 2001 19:24:17 -0700 (PDT) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The problem turned out to be in the nfsd code. The following fixes it: --- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 +++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 @@ -150,6 +150,7 @@ MOD_INC_USE_COUNT; lock_kernel(); daemonize(); + current->fs->umask = 0; sprintf(current->comm, "nfsd"); current->rlim[RLIMIT_FSIZE].rlim_cur = RLIM_INFINITY; From owner-linux-xfs@oss.sgi.com Wed Jul 25 20:13:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q3DNG05952 for linux-xfs-outgoing; Wed, 25 Jul 2001 20:13:23 -0700 Received: from rj.corp.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q3DLV05933 for ; Wed, 25 Jul 2001 20:13:21 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6Q3GxU21025 for ; Wed, 25 Jul 2001 20:16:59 -0700 Received: from kao2.melbourne.sgi.com (kao2.melbourne.sgi.com [134.14.55.180]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id NAA21283; Thu, 26 Jul 2001 13:11:56 +1000 X-Mailer: exmh version 2.1.1 10/15/1999 From: Keith Owens To: tridge@valinux.com cc: linux-xfs@oss.sgi.com Subject: Re: umask fix (patch) In-reply-to: Your message of "Wed, 25 Jul 2001 19:24:17 MST." <20010726022417.ECC8144E0@lists.samba.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Jul 2001 13:11:56 +1000 Message-ID: <18265.996117116@kao2.melbourne.sgi.com> Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 25 Jul 2001 19:24:17 -0700 (PDT), Andrew Tridgell wrote: >The problem turned out to be in the nfsd code. The following fixes it: > >--- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 >+++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 >@@ -150,6 +150,7 @@ > MOD_INC_USE_COUNT; > lock_kernel(); > daemonize(); >+ current->fs->umask = 0; > sprintf(current->comm, "nfsd"); > current->rlim[RLIMIT_FSIZE].rlim_cur = RLIM_INFINITY; Kernel threads share the init task fs context. That change makes all future kernel threads run with umask 0, a big security exposure. This problem was supposed to have been fixed in 2.4.7-pre7. From owner-linux-xfs@oss.sgi.com Thu Jul 26 00:01:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q71Jv28761 for linux-xfs-outgoing; Thu, 26 Jul 2001 00:01:19 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q71GV28739 for ; Thu, 26 Jul 2001 00:01:16 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id JAA28878 for ; Thu, 26 Jul 2001 09:01:13 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id JAA06104 for linux-xfs@oss.sgi.com; Thu, 26 Jul 2001 09:01:12 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id EDC1157306 for ; Thu, 26 Jul 2001 08:59:39 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id B3C7A25835 for ; Thu, 26 Jul 2001 08:59:39 +0200 (CEST) Message-ID: <3B5FBFDB.B15604A2@ch.sauter-bc.com> Date: Thu, 26 Jul 2001 08:59:39 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Export log of an existing XFS filesystem Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Is it possible to export the log of an existing XFS filesystem to an external device? I'd like to change my configuration without having to recreate the filesystem. Simon From owner-linux-xfs@oss.sgi.com Thu Jul 26 00:21:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q7LYV31378 for linux-xfs-outgoing; Thu, 26 Jul 2001 00:21:34 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q7LTV31346 for ; Thu, 26 Jul 2001 00:21:30 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id E8862C08377 for ; Thu, 26 Jul 2001 15:21:25 +0800 (PHT) Date: Thu, 26 Jul 2001 15:21:25 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: xfsdump looking for libhandle.la in /lib Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi everyone, Just thought I'd let you know that in the current CVS xfsdump looks for libhandle.la in /lib, while xfslibs-dev puts it in /usr/lib. What has been the decision about where to really put the files? Should they be in /usr/lib or in /lib? Anyway, I am temporary creating a symlink in /usr/lib for libhandle.la to be able to work around this. --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 00:25:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q7PUQ32014 for linux-xfs-outgoing; Thu, 26 Jul 2001 00:25:30 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q7PNV31976 for ; Thu, 26 Jul 2001 00:25:23 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 069D5C0FFA0 for ; Thu, 26 Jul 2001 15:25:22 +0800 (PHT) Date: Thu, 26 Jul 2001 15:25:22 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001 at 15:21, Federico Sevilla III wrote: > Anyway, I am temporary creating a symlink in /usr/lib for libhandle.la > to be able to work around this. Grr, in /lib pointing to /usr/lib/libhandle.la I mean. Built the xfsprogs package successfully with this. BTW, what's the current status of xfs_fsr? I don't know how stable it is, and how it handles changes in the filesystem (since the filesystem will be mounted) while it is in operation. Is it safe to run this in a cron job, for example? And how much improvement can one typically get from running xfs_fsr to reorganize a filesystem's contents? Thanks in advance! :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 00:47:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q7lYk02211 for linux-xfs-outgoing; Thu, 26 Jul 2001 00:47:34 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q7lWV02190 for ; Thu, 26 Jul 2001 00:47:32 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via SMTP id AAA09974 for ; Thu, 26 Jul 2001 00:45:12 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 RAA22909; Thu, 26 Jul 2001 17:46:14 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA20089; Thu, 26 Jul 2001 17:46:13 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107261746.ZM214654@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 17:46:12 +1000 In-Reply-To: Federico Sevilla III "Re: xfsdump looking for libhandle.la in /lib" (Jul 26, 3:25pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Federico Sevilla III , Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 26, 3:25pm, Federico Sevilla III wrote: > Subject: Re: xfsdump looking for libhandle.la in /lib > On Thu, 26 Jul 2001 at 15:21, Federico Sevilla III wrote: > > Anyway, I am temporary creating a symlink in /usr/lib for libhandle.la > > to be able to work around this. > > Grr, in /lib pointing to /usr/lib/libhandle.la I mean. Built the xfsprogs > package successfully with this. > Current xfsdump/configure.in in cvs looks in /usr/lib/libhandle.la - but even if it doesn't find this, it will fall back to -lhandle, so I'm not sure what the problem is? (error message?) Perhaps you have some residual state from an earlier build & need to do a "make realclean"? /usr/lib is where the .la and .a ended up. > BTW, what's the current status of xfs_fsr? I don't know how stable it is, > and how it handles changes in the filesystem (since the filesystem will be > mounted) while it is in operation. Is it safe to run this in a cron job, > for example? And how much improvement can one typically get from running > xfs_fsr to reorganize a filesystem's contents? > There have been some reports of fsr causing kernel panics - I saw some mail fly by in the last couple of days stating that problem was on Steve's work-in-progress list. I think that in the general case, the improvement from fsr is relatively small - but believe there are corner cases where it makes a big difference. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 01:50:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q8ob006374 for linux-xfs-outgoing; Thu, 26 Jul 2001 01:50:37 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q8oWV06350 for ; Thu, 26 Jul 2001 01:50:32 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via SMTP id KAA103308 for ; Thu, 26 Jul 2001 10:50:04 +0200 (CEST) mail_from (nathans@wobbly.melbourne.sgi.com) 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 SAA23126; Thu, 26 Jul 2001 18:49:09 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id SAA38904; Thu, 26 Jul 2001 18:49:08 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107261849.ZM223612@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 18:49:07 +1000 In-Reply-To: Simon Matter "Export log of an existing XFS filesystem" (Jul 26, 8:59am) References: <3B5FBFDB.B15604A2@ch.sauter-bc.com> X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Simon Matter , linux-xfs Subject: Re: Export log of an existing XFS filesystem Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 26, 8:59am, Simon Matter wrote: > Subject: Export log of an existing XFS filesystem > Is it possible to export the log of an existing XFS filesystem > to an external device? I'd like to change my configuration > without having to recreate the filesystem. > Steve sent some mail the other day describing a procedure for converting an internal log to an external log using xfs_db - it should be in the mail archive, somewhere quite recent. He also gave lots of caveats, saying test it first, its risky, etc, and you'll need Eric's endian bugfix in the current version of xfs_db (see xfsprogs CHANGES file). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 01:55:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q8tgn06957 for linux-xfs-outgoing; Thu, 26 Jul 2001 01:55:42 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q8tdV06938 for ; Thu, 26 Jul 2001 01:55:40 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 4479BC0FFA6 for ; Thu, 26 Jul 2001 16:55:38 +0800 (PHT) Date: Thu, 26 Jul 2001 16:55:38 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib In-Reply-To: <10107261746.ZM214654@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001 at 17:46, Nathan Scott wrote: > Current xfsdump/configure.in in cvs looks in /usr/lib/libhandle.la - > but even if it doesn't find this, it will fall back to -lhandle, so > I'm not sure what the problem is? (error message?) I'm building a Debian package so I run "debian/rules build". It failed saying it could not find /lib/libhandle.la. > Perhaps you have some residual state from an earlier build & need to > do a "make realclean"? /usr/lib is where the .la and .a ended up. There was no residual state. I have a copy of the CVS tree that I update, and a copy I use to build kernels. I deleted the old tree that I worked on, updated my "updated" copy, then copied that to a new working tree. :) > There have been some reports of fsr causing kernel panics - I saw some > mail fly by in the last couple of days stating that problem was on > Steve's work-in-progress list. I remember this, too, which is why I asked to find out if maybe someone had an update. Perhaps we can wait for Steve to let us know about how his work-in-progress is doing. :) > I think that in the general case, the improvement from fsr is > relatively small - but believe there are corner cases where it makes a > big difference. Okay. I wonder if someone has ever written a paper or something about the fragmentation in XFS and hence the situations where fsr really helps. There is a current filesystem fragmentation study being done comparing JFS, XFS and ReiserFS by a student taking his masters, but I don't think it's finished so we can wait for that, too. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 02:13:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q9Dhu08941 for linux-xfs-outgoing; Thu, 26 Jul 2001 02:13:43 -0700 Received: from rj.corp.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q9DeV08920 for ; Thu, 26 Jul 2001 02:13:40 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6Q9HJU26065 for ; Thu, 26 Jul 2001 02:17:19 -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 TAA23194; Thu, 26 Jul 2001 19:12:18 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA29774; Thu, 26 Jul 2001 19:12:17 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107261912.ZM235472@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 19:12:15 +1000 In-Reply-To: Federico Sevilla III "Re: xfsdump looking for libhandle.la in /lib" (Jul 26, 4:55pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Federico Sevilla III , Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 26, 4:55pm, Federico Sevilla III wrote: > Subject: Re: xfsdump looking for libhandle.la in /lib > On Thu, 26 Jul 2001 at 17:46, Nathan Scott wrote: > > Current xfsdump/configure.in in cvs looks in /usr/lib/libhandle.la - > > but even if it doesn't find this, it will fall back to -lhandle, so > > I'm not sure what the problem is? (error message?) > > I'm building a Debian package so I run "debian/rules build". It failed > saying it could not find /lib/libhandle.la. > Without the actual error message though, I can't tell if its failing in the "configure" stage or the "build" stage. If its in the "configure" stage, your xfsdump is out of date, if its the "build" stage then your xfslibs-dev is out of date. Basically, get the latest of both of these and it will work. Or use the packages which are already in unstable, and you can dodge the problem entirely... ;-) cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 02:16:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q9GjO09370 for linux-xfs-outgoing; Thu, 26 Jul 2001 02:16:45 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q9GhV09347 for ; Thu, 26 Jul 2001 02:16:43 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id F0423C00AC3 for ; Thu, 26 Jul 2001 17:16:41 +0800 (PHT) Date: Thu, 26 Jul 2001 17:16:41 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib In-Reply-To: <10107261912.ZM235472@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001 at 19:12, Nathan Scott wrote: > If its in the "configure" stage, your xfsdump is out of date How can the CVS copy be out of date? I just did a cvs update. :) > if its the "build" stage then your xfslibs-dev is out of date I just built xfsprogs from the same CVS copy. How can THAT be out of date? > Basically, get the latest of both of these and it will work. I already do. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 02:28:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q9Sgb10142 for linux-xfs-outgoing; Thu, 26 Jul 2001 02:28:42 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q9SdV10119 for ; Thu, 26 Jul 2001 02:28:39 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 855AB6391E; Thu, 26 Jul 2001 10:30:56 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 26 Jul 2001 10:36:04 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Thu, 26 Jul 2001 10:28:34 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEVVwM0j3I4Iy+ySROBbmTb9DShBwAWkCSQ From: "Juer Lee" To: "Nathan Scott" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6Q9SeV10122 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >hi, > >On Jul 25, 9:46am, Steve Lord wrote: >> Subject: Re: Backup ACLs >> ... >> You said that you had implemented the system calls for acls and >> extended attributes for the powerpc platform, I presume you have the >> user space changes as well so that the library calls in the acl >> package work. I would concentrate on getting the chacl command >> to work in all modes before moving to xfsdump/restore. Make sure >> that the system call numbers at the end of acl/libacl/acl.c are >> defined correctly for the ppc. >> >> Finally make sure you are linking xfsdump with the modified libacl. >> >> OK, mostly fairly obvious stuff. >> > >Yup, good summary - one extra thing though - you must also >have a working attr command (once you have chacl working), >otherwise xfsdump/restore are not going to be able to backup >your ACLs (as these link with libattr - attr/libattr/attr.c - >rather than libacl). > >On Jul 25, 11:51am, Juer Lee wrote: >> Subject: RE: Backup ACLs >>I tried to use a different version of xfs-progs-devel, 1.1.3.0-ppc. It >>still didn't work.:( > >Can you verify whether your /usr/include/xfs/platform_defs.h >has references to O_DIRECT or not for powerpc (around line 58)? >I'd like to understand why this doesn't work for you, because >it should. Could you post the gcc error & that header to me? > >thanks. > >-- >Nathan > Nathan, Oh, yes, I can not find the references in /usr/include/xfs/platform_defs.h. But I am sure that I appplied xfs-progs-devel-1.1.3.0-ppc, it seemed that in this version O_DIRECT is still not defined. As I want to use the 1.0.11 xfsdump right away, I used some way to clear those compiling error, after that I can run xfsdump/xfsrestore But I think it is not the right away to fix it. And, I added the system call number for attr in attr utility and kernel code after sys_acl_get and sys_acl_set . It seemed work, I am still testing it. At the same time, can you please help me to fix the compiling error first? If haven't modifid any code, the error message will be --- sorry, it is not the truth: I added "#define O_DIRECT 0400000" in the code, otherwise, the gcc(2.95.2) will complain "undefined reference to 'O_DIRECT' ------------------------------------------------------------------------ ------------------------------------------------------------------------ ---------------------------------- gcc -O1 -g -DDEBUG -funsigned-char -Wall -DDUMP -DRMT -DBASED -DDOSOCKS -DINVCONVFIX -DSIZEEST -DPIPEINVFIX -DEXTATTR -I/usr/include/xfs -I/usr/include/attr '-DVERSION="1.0.11"' -D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -DXFS_BIG_FILES=1 -DXFS_BIG_FILESYSTEMS=1 -o xfsdump arch_xlate.o cldmgr.o content_common.o dlog.o drive.o drive_scsitape.o drive_simple.o drive_minrmt.o fs.o getdents.o global.o lock.o main.o mlog.o openutil.o qlock.o path.o ring.o stkchk.o stream.o util.o sproc.o attr.o inv_api.o inv_core.o inv_fstab.o inv_idx.o inv_mgr.o inv_stobj.o content.o inomap.o var.o -lhandle /usr/lib/libuuid.a ../librmt/librmt.a /usr/lib/libattr.a util.o: In function `stat64_to_xfsbstat': /export/xfsdump-1.0.11/dump/util.c:137: undefined reference to `IRIX_MKDEV' /export/xfsdump-1.0.11/dump/util.c:137: relocation truncated to fit: R_PPC_REL24 IRIX_MKDEV collect2: ld returned 1 exit status make[1]: *** [xfsdump] Error 1 make: *** [default] Error 2 ------------------------------------------------------------------------ ------------------------------------------------------------------------ ---------------------------------- Juer From owner-linux-xfs@oss.sgi.com Thu Jul 26 02:43:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q9hc710988 for linux-xfs-outgoing; Thu, 26 Jul 2001 02:43:38 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q9haV10965 for ; Thu, 26 Jul 2001 02:43:36 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6Q9mJm21568 for ; Thu, 26 Jul 2001 02:48:19 -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 TAA23313; Thu, 26 Jul 2001 19:42:14 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA15059; Thu, 26 Jul 2001 19:42:13 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107261942.ZM238837@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 19:42:11 +1000 In-Reply-To: Federico Sevilla III "Re: xfsdump looking for libhandle.la in /lib" (Jul 26, 5:16pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Federico Sevilla III , Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Jul 26, 5:16pm, Federico Sevilla III wrote: > Subject: Re: xfsdump looking for libhandle.la in /lib > > ... > > Basically, get the latest of both of these and it will work. > > I already do. :) > Oh - I just tried it, & you're right [sheepish grin]. Something must have been changed underneath me ... I'll go have another look. Actually, I should probably go home now. ;) thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 02:45:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6Q9jLa11170 for linux-xfs-outgoing; Thu, 26 Jul 2001 02:45:21 -0700 Received: from rj.corp.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6Q9jKV11150 for ; Thu, 26 Jul 2001 02:45:20 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6Q9mwU26444 for ; Thu, 26 Jul 2001 02:48:59 -0700 Received: from wobbly.melbourne.sgi.com (wobbly.melbourne.sgi.com [134.14.55.135]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA23316; Thu, 26 Jul 2001 19:43:57 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id TAA34755; Thu, 26 Jul 2001 19:43:56 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107261943.ZM239000@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 19:43:55 +1000 In-Reply-To: "Juer Lee" "RE: Backup ACLs" (Jul 26, 10:28am) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: "Juer Lee" Subject: Re: Backup ACLs Cc: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 26, 10:28am, Juer Lee wrote: > Subject: RE: Backup ACLs > > Nathan, > > Oh, yes, I can not find the references in > /usr/include/xfs/platform_defs.h. But I am sure that I appplied > xfs-progs-devel-1.1.3.0-ppc, it seemed that in this version O_DIRECT is > still not defined. Oh, just noticed this - sorry, thought you wrote "1.3.1". You will need a more recent version of xfsprogs-devel - if you are using the CVS tree, the xfsprogs/doc/INSTALL document will help you get there. Having a more recent xfsprogs-devel will also fix this next problem... > /export/xfsdump-1.0.11/dump/util.c:137: undefined reference to > `IRIX_MKDEV' Hope this helps. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 03:05:02 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QA52113199 for linux-xfs-outgoing; Thu, 26 Jul 2001 03:05:02 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QA4xV13176 for ; Thu, 26 Jul 2001 03:05:00 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 6EBF7C00AC3 for ; Thu, 26 Jul 2001 18:04:58 +0800 (PHT) Date: Thu, 26 Jul 2001 18:04:58 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib In-Reply-To: <10107261942.ZM238837@wobbly.melbourne.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001 at 19:42, Nathan Scott wrote: > Oh - I just tried it, & you're right [sheepish grin]. Something must > have been changed underneath me ... I'll go have another look. Hehehe. Oops. You've been working too hard, I guess. Glad I was able to broadcast a heads up. :) > Actually, I should probably go home now. ;) Yes, you probably should. I remember running "rm -fR *" from / once when I was tired. I forgot I wasn't in the directory I should've deleted. I had too many darned xterms open. :( --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 03:35:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QAZaV17415 for linux-xfs-outgoing; Thu, 26 Jul 2001 03:35:36 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QAZYV17395 for ; Thu, 26 Jul 2001 03:35:34 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6QAeHm22770 for ; Thu, 26 Jul 2001 03:40:17 -0700 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id UAA66443 for linux-xfs@oss.sgi.com; Thu, 26 Jul 2001 20:34:11 +1000 (EST) Date: Thu, 26 Jul 2001 20:34:11 +1000 (EST) From: Nathan Scott Message-Id: <200107261034.UAA66443@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - build Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk The build fix is at the end, Federico -- thanks again. First steps in trying to ensure our libacl doesn't become even more divergent from the acl.bestbits.at ACL version is also in here, but more on that some other time. cheers. Date: Tue Jul 24 22:03:04 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99520a cmd/xfstests/tools/srcdiff - 1.8 - spilt acl kernel and user headers apart - no point keeping in sync. linux/fs/xfs/xfs_acl.c - 1.5 - add two XFS-specific macros in here - implementation details, not needed by anyone but this .c file. linux/fs/xfs/linux/acl.h - 1.3 - remove all the userspace gunk, get XFS-specific stuff out as well. Date: Wed Jul 25 17:39:39 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99593a cmd/acl/man/man5/acl.5 - 1.5 cmd/acl/man/man3/acl_from_text.3 - 1.4 cmd/acl/man/man3/acl_free.3 - 1.4 - fix typos. cmd/acl/man/man1/chacl.1 - 1.3 - add documentation for -r, format options better. Date: Thu Jul 26 03:26:39 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99597a cmd/attr/include/builddefs.in - 1.9 cmd/xfsdump/include/builddefs.in - 1.9 cmd/xfsprogs/include/builddefs.in - 1.14 cmd/acl/include/builddefs.in - 1.9 cmd/dmapi/include/builddefs.in - 1.10 - use the same symlink trick we just put int for .a, in the .la install case. fixes an xfsdump build problem. From owner-linux-xfs@oss.sgi.com Thu Jul 26 03:39:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QAdNP18123 for linux-xfs-outgoing; Thu, 26 Jul 2001 03:39:23 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QAdLV18092 for ; Thu, 26 Jul 2001 03:39:21 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 9E89E6391E; Thu, 26 Jul 2001 11:35:34 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 26 Jul 2001 11:40:42 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Thu, 26 Jul 2001 11:33:09 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEVt7LLPpx0rXjkRCyYzrWKkwerGgAAQ8iw From: "Juer Lee" To: "Nathan Scott" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6QAdMV18093 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >hi, > >On Jul 26, 10:28am, Juer Lee wrote: >> Subject: RE: Backup ACLs >> >> Nathan, >> >> Oh, yes, I can not find the references in >> /usr/include/xfs/platform_defs.h. But I am sure that I appplied >> xfs-progs-devel-1.1.3.0-ppc, it seemed that in this version >O_DIRECT is >> still not defined. > >Oh, just noticed this - sorry, thought you wrote "1.3.1". >You will need a more recent version of xfsprogs-devel - >if you are using the CVS tree, the xfsprogs/doc/INSTALL >document will help you get there. > >Having a more recent xfsprogs-devel will also fix this >next problem... > >> /export/xfsdump-1.0.11/dump/util.c:137: undefined reference to >> `IRIX_MKDEV' > >Hope this helps. > >cheers. > >-- >Nathan Thanks. I fixed that. I am now adding sys_attrctl, after I success, I'll share my happiness with all who are helping me. :) Juer From owner-linux-xfs@oss.sgi.com Thu Jul 26 04:26:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QBQsc24962 for linux-xfs-outgoing; Thu, 26 Jul 2001 04:26:54 -0700 Received: from m2.pp.htv.fi (m2ep.pp.htv.fi [212.90.64.98]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QBQqV24940 for ; Thu, 26 Jul 2001 04:26:52 -0700 Received: from m7.pp.htv.fi (m7.pp.htv.fi [212.90.64.22]) by m2.pp.htv.fi (8.9.3 (PHNE_22672)/8.8.6) with ESMTP id OAA01905 for ; Thu, 26 Jul 2001 14:26:45 +0300 (EETDST) Received: from kitsune (cs158041.pp.htv.fi [213.243.158.41]) by m7.pp.htv.fi (8.8.6 (PHNE_14041)/8.8.6) with ESMTP id OAA00466 for ; Thu, 26 Jul 2001 14:26:36 +0300 (EETDST) Received: from viiru by kitsune with local (Exim 3.31 #1 (Debian)) id 15PjHo-0000DR-00 for ; Thu, 26 Jul 2001 14:26:36 +0300 Date: Thu, 26 Jul 2001 14:26:36 +0300 From: Arto Jantunen To: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib Message-ID: <20010726142636.A695@welho.com> Mail-Followup-To: Linux XFS Mailing List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 26, 2001 at 04:55:38PM +0800, Federico Sevilla III wrote: > > There have been some reports of fsr causing kernel panics - I saw some > > mail fly by in the last couple of days stating that problem was on > > Steve's work-in-progress list. > > I remember this, too, which is why I asked to find out if maybe someone > had an update. Perhaps we can wait for Steve to let us know about how his > work-in-progress is doing. :) I mailed this list about a kernel panic caused by xfs_fsr, but after upgrading to version 1.1.0 this problem disapeared. The changelog for that version says "merge fsr bug fixes from IRIX" and I think these fix the problem I was having. After that xfs_fsr has been running perfectly for me. YMMV. -- Arto Jantunen From owner-linux-xfs@oss.sgi.com Thu Jul 26 05:26:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QCQIr30414 for linux-xfs-outgoing; Thu, 26 Jul 2001 05:26:18 -0700 Received: from msg.ecetra.com (dollar.ecetra.com [193.164.224.209]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QCQGV30383 for ; Thu, 26 Jul 2001 05:26:16 -0700 Received: from vie-ac.office.ecetra.com (vie-ac.office.ecetra.com [10.251.148.147] (may be forged)) by msg.ecetra.com (8.9.3/8.9.3) with ESMTP id OAA16883 for ; Thu, 26 Jul 2001 14:26:09 +0200 Received: from localhost (localhost [127.0.0.1]) by vie-ac.office.ecetra.com (8.11.4/8.11.3) with ESMTP id f6QCQ9x17596 for ; Thu, 26 Jul 2001 14:26:09 +0200 Date: Thu, 26 Jul 2001 14:26:09 +0200 (CEST) From: Adam Cioccarelli To: Subject: more comparisons... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I can't remember but has this been on the list? http://aurora.zemris.fer.hr/filesystems XFS seems to score very well... ------------------------------------------------------------------------------- Adam Cioccarelli (B.E Mechanical) Adam.Cioccarelli@ecetra.com Database Administrator Phone: +43 1 536 89 7725 Fax: +43 1 536 89 7719 ecetra Central European e-Finance AG Mobile:+43 664 181 4195 ------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Thu Jul 26 05:43:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QChI032241 for linux-xfs-outgoing; Thu, 26 Jul 2001 05:43:18 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QChDV32195 for ; Thu, 26 Jul 2001 05:43:14 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 2CDC7C00AC4 for ; Thu, 26 Jul 2001 20:43:08 +0800 (PHT) Date: Thu, 26 Jul 2001 20:43:08 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: more comparisons... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001 at 14:26, Adam Cioccarelli wrote: > I can't remember but has this been on the list? > http://aurora.zemris.fer.hr/filesystems I posted this URL on the list before, and on XFS there haven't been too many negative comments, although we cannot tell what moun options and mkfs.xfs options were used. This could have improved the performance. On the ReiserFS list, though, the report is not very well accepted (especially by Hans Reiser). Aside from the fact that ReiserFS does not score well except on deletes, the ReiserFS team has as of yet not been able to reproduce the results of this tests, and therefore cannot accept its results. Even on the mongo.pl tests, though, we will see that starting at files of size 10000 bytes XFS slowly gains speed over ReiserFS. On personal tests with files of size 600MB, the results are significant. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 05:51:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QCp1t00466 for linux-xfs-outgoing; Thu, 26 Jul 2001 05:51:01 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QCoxV00447 for ; Thu, 26 Jul 2001 05:50:59 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6QCore06511; Thu, 26 Jul 2001 14:50:54 +0200 Message-Id: <4.3.2.7.2.20010726144937.02bc29a8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 26 Jul 2001 14:50:38 +0200 To: Adam Cioccarelli , From: Seth Mos Subject: Re: more comparisons... In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:26 26-7-2001 +0200, Adam Cioccarelli wrote: >Hi, > >I can't remember but has this been on the list? > >http://aurora.zemris.fer.hr/filesystems > >XFS seems to score very well... I see that they also have a noce section on patching and compiling a xfs kernel. It might be handy to include it in the FAQ if people think it's worth something. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 26 06:05:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QD5pw02109 for linux-xfs-outgoing; Thu, 26 Jul 2001 06:05:51 -0700 Received: from mail.coltex.nl (edge.coltex.nl [194.151.97.115]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QD5nV02089 for ; Thu, 26 Jul 2001 06:05:49 -0700 Received: from auto-nb1.xs4all.nl (auto-nb1.coltex.nl [10.0.1.171]) by mail.coltex.nl (8.11.2/8.11.2) with ESMTP id f6QD5be06610; Thu, 26 Jul 2001 15:05:38 +0200 Message-Id: <4.3.2.7.2.20010726150324.02b960c8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Thu, 26 Jul 2001 15:05:21 +0200 To: Federico Sevilla III , Linux XFS Mailing List From: Seth Mos Subject: Re: more comparisons... In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 20:43 26-7-2001 +0800, Federico Sevilla III wrote: >On Thu, 26 Jul 2001 at 14:26, Adam Cioccarelli wrote: > > I can't remember but has this been on the list? > > http://aurora.zemris.fer.hr/filesystems > >I posted this URL on the list before, and on XFS there haven't been too >many negative comments, although we cannot tell what moun options and >mkfs.xfs options were used. This could have improved the performance. I will ask them. Or degrade it depending on the mis-use. >On the ReiserFS list, though, the report is not very well accepted >(especially by Hans Reiser). Aside from the fact that ReiserFS does not >score well except on deletes, the ReiserFS team has as of yet not been >able to reproduce the results of this tests, and therefore cannot accept >its results. Great, so they don't have the same environment that the user actually uses and decide that results better not be accepted ;) >Even on the mongo.pl tests, though, we will see that starting at files of >size 10000 bytes XFS slowly gains speed over ReiserFS. On personal tests >with files of size 600MB, the results are significant. :) XFS is a nice fs for a ftp mirror with ISO images and distributions. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Thu Jul 26 06:12:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QDCXr02806 for linux-xfs-outgoing; Thu, 26 Jul 2001 06:12:33 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QDCTV02778 for ; Thu, 26 Jul 2001 06:12:30 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 4167DC000BC for ; Thu, 26 Jul 2001 21:12:25 +0800 (PHT) Date: Thu, 26 Jul 2001 21:12:25 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: more comparisons... In-Reply-To: <4.3.2.7.2.20010726150324.02b960c8@pop.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001 at 15:05, Seth Mos wrote: > Great, so they don't have the same environment that the user actually > uses and decide that results better not be accepted ;) Well, I wouldn't like to start ranting and ranting about them, but I think ReiserFS is great for small files and for the rest, XFS. :) > XFS is a nice fs for a ftp mirror with ISO images and distributions. Not only that, it's great if you're burning CDs from ISOs in them over a network. I noticed ReiserFS is rather jerky when it comes to this, and jerkiness leads to underruns that leads to coasters. Of course this is all unofficial. I don't have statistical data to back me up. I have personal experience, though. And for that only my Squid cache remains on ReiserFS. :) --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 06:50:21 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QDoL806037 for linux-xfs-outgoing; Thu, 26 Jul 2001 06:50:21 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QDoIV06018 for ; Thu, 26 Jul 2001 06:50:18 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 3DF7563939 for ; Thu, 26 Jul 2001 14:44:26 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 26 Jul 2001 14:49:34 UT content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: Backup ACLs X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Date: Thu, 26 Jul 2001 14:42:05 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEVt7LLPpx0rXjkRCyYzrWKkwerGgAAQ8iwAAfbBQA= From: "Juer Lee" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6QDoJV06019 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >-----Original Message----- >From: Juer Lee >Sent: 26 July 2001 11:33 >To: Nathan Scott >Cc: linux-xfs@oss.sgi.com >Subject: RE: Backup ACLs > > > >>hi, >> >>On Jul 26, 10:28am, Juer Lee wrote: >>> Subject: RE: Backup ACLs >>> >>> Nathan, >>> >>> Oh, yes, I can not find the references in >>> /usr/include/xfs/platform_defs.h. But I am sure that I appplied >>> xfs-progs-devel-1.1.3.0-ppc, it seemed that in this version >>O_DIRECT is >>> still not defined. >> >>Oh, just noticed this - sorry, thought you wrote "1.3.1". >>You will need a more recent version of xfsprogs-devel - >>if you are using the CVS tree, the xfsprogs/doc/INSTALL >>document will help you get there. >> >>Having a more recent xfsprogs-devel will also fix this >>next problem... >> >>> /export/xfsdump-1.0.11/dump/util.c:137: undefined reference to >>> `IRIX_MKDEV' >> >>Hope this helps. >> >>cheers. >> >>-- >>Nathan > > >Thanks. >I fixed that. >I am now adding sys_attrctl, after I success, I'll share my happiness >with all who are helping me. :) > >Juer > > Unfortuanately, I have some problems in adding attr. I updated the code for attr utiltiy and kernel. The ways is same as that I used for adding ACL When I run "attr -l file", error message like : attr_list: Bad address -- I think it is produced by syscall.. I checked it many times, I couldn't find the reason. :( Juer From owner-linux-xfs@oss.sgi.com Thu Jul 26 07:51:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QEp3c10257 for linux-xfs-outgoing; Thu, 26 Jul 2001 07:51:03 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QEp1V10237 for ; Thu, 26 Jul 2001 07:51:01 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id HAA00115 for ; Thu, 26 Jul 2001 07:48:42 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2537185; Thu, 26 Jul 2001 09:49:40 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA82748; Thu, 26 Jul 2001 09:49:40 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6QEnMW16753; Thu, 26 Jul 2001 09:49:22 -0500 Message-Id: <200107261449.f6QEnMW16753@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Nathan Scott" cc: Federico Sevilla III , Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib In-Reply-To: Message from "Nathan Scott" of "Thu, 26 Jul 2001 17:46:12 +1000." <10107261746.ZM214654@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 09:49:22 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > > BTW, what's the current status of xfs_fsr? I don't know how stable it is, > > and how it handles changes in the filesystem (since the filesystem will be > > mounted) while it is in operation. Is it safe to run this in a cron job, > > for example? And how much improvement can one typically get from running > > xfs_fsr to reorganize a filesystem's contents? > > > > There have been some reports of fsr causing kernel panics - I > saw some mail fly by in the last couple of days stating that > problem was on Steve's work-in-progress list. > > I think that in the general case, the improvement from fsr is > relatively small - but believe there are corner cases where it > makes a big difference. > > cheers. xfs_fsr currently appears to create filesystems which will not unmount correctly. There is a reference count leak in there. It is on the todo list, but right now Eric is out with a new baby, and I have three meetings about other stuff today. Steve > > -- > Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 07:56:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QEuVd10645 for linux-xfs-outgoing; Thu, 26 Jul 2001 07:56:31 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QEuPV10625 for ; Thu, 26 Jul 2001 07:56:26 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA129547 for ; Thu, 26 Jul 2001 16:55:58 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2499103; Thu, 26 Jul 2001 09:55:01 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA44850; Thu, 26 Jul 2001 09:55:01 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6QEshE16781; Thu, 26 Jul 2001 09:54:43 -0500 Message-Id: <200107261454.f6QEshE16781@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Nathan Scott" cc: Simon Matter , linux-xfs Subject: Re: Export log of an existing XFS filesystem In-Reply-To: Message from "Nathan Scott" of "Thu, 26 Jul 2001 18:49:07 +1000." <10107261849.ZM223612@wobbly.melbourne.sgi.com> Date: Thu, 26 Jul 2001 09:54:43 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > hi, > > On Jul 26, 8:59am, Simon Matter wrote: > > Subject: Export log of an existing XFS filesystem > > Is it possible to export the log of an existing XFS filesystem > > to an external device? I'd like to change my configuration > > without having to recreate the filesystem. > > > > Steve sent some mail the other day describing a procedure > for converting an internal log to an external log using > xfs_db - it should be in the mail archive, somewhere quite > recent. He also gave lots of caveats, saying test it first, > its risky, etc, and you'll need Eric's endian bugfix in the > current version of xfs_db (see xfsprogs CHANGES file). Yes, it should be in the list archive somewhere, if you do a clean unmount and use a recent xfs_db to relocate the log then you can run xfs_repair to zero it before the first mount. You can ignore the endian flipping stuff in the email if you have a recent xfs_db. Note that this procedure does not fix up the backup superblocks and if you ever need to recover the filesystem from these you may run into problems. Steve > > cheers. > > -- > Nathan From owner-linux-xfs@oss.sgi.com Thu Jul 26 07:58:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QEwZP10853 for linux-xfs-outgoing; Thu, 26 Jul 2001 07:58:35 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QEwWV10831 for ; Thu, 26 Jul 2001 07:58:32 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id QAA122119 for ; Thu, 26 Jul 2001 16:58:06 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2534849; Thu, 26 Jul 2001 09:57:13 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA72550; Thu, 26 Jul 2001 09:57:13 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6QEutx16789; Thu, 26 Jul 2001 09:56:55 -0500 Message-Id: <200107261456.f6QEutx16789@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: tridge@valinux.com cc: linux-xfs@oss.sgi.com Subject: Re: umask bug In-Reply-To: Message from Andrew Tridgell of "Wed, 25 Jul 2001 17:34:54 PDT." <20010726003454.26B7B4603@lists.samba.org> Date: Thu, 26 Jul 2001 09:56:55 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I'm testing SPECsfs against the 2.4.7 cvs XFS patch and it's failing > the validation phase. The problem is that directories are being > created with the wrong permissions. You can see it like this: > > mount localhost:/export /mnt > cd /mnt > umask 0 > mkdir foo > ls -ld foo > > I thought initially it was a nfsd bug, perhaps getting the umask > wrong, but I found that the bug doesn't happen with ext2. Also, > creating files does get the right permisisons, but directories are > wrong. > > Any ideas? Known problem perhaps? I'm new to XFS. > > Cheers, Tridge Wow, famous people! Hmm, I read this message and the fix message, I will take a look later today, the fact that this does not happen to ext2 suggests there is still something wrong in xfs - why would a fix in the nfs code be the correct one if different filesystems exhibit different behaviors? Steve From owner-linux-xfs@oss.sgi.com Thu Jul 26 08:03:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QF34u11221 for linux-xfs-outgoing; Thu, 26 Jul 2001 08:03:04 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QF33V11200 for ; Thu, 26 Jul 2001 08:03:03 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HKMHK>; Thu, 26 Jul 2001 10:02:16 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643521@AUSMAIL> From: "Gonyou, Austin" To: linux-xfs Subject: Boot Failure after installing 1.0.1 Date: Thu, 26 Jul 2001 10:02:12 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A tech here has 2 hdd's on his system, hda and hdb. hda is full with windows 2k, hdb is RH 7.1. All boot partitions are on hdb for linux. No LILO installed on hda. When installed with RH 7.1 SGI XFS installer 1.0.1, the system will not boot at all from hdb, not even with a floppy. If using no XFS, it will boot no problem. What is causing this behaviour? Is it something to do with the way XFS needs to find it's boot device? Thanks for the help. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com From owner-linux-xfs@oss.sgi.com Thu Jul 26 08:31:15 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QFVF512647 for linux-xfs-outgoing; Thu, 26 Jul 2001 08:31:15 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QFVDV12622 for ; Thu, 26 Jul 2001 08:31:13 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id IAA06636 for ; Thu, 26 Jul 2001 08:31:00 -0700 (PDT) mail_from (sandeen@sgi.com) Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id IAA34548; Thu, 26 Jul 2001 08:29:45 -0700 (PDT) Message-ID: <3B6036D3.999B5AAF@sgi.com> Date: Thu, 26 Jul 2001 10:27:15 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: "Gonyou, Austin" CC: linux-xfs Subject: Re: Boot Failure after installing 1.0.1 References: <85063BBE668FD411944400D0B744267A643521@AUSMAIL> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Gonyou, Austin" wrote: > > A tech here has 2 hdd's on his system, hda and hdb. hda is full with windows > 2k, hdb is RH 7.1. All boot partitions are on hdb for linux. No LILO > installed on hda. When installed with RH 7.1 SGI XFS installer 1.0.1, the > system will not boot at all from hdb, not even with a floppy. If using no > XFS, it will boot no problem. What is causing this behaviour? Is it > something to do with the way XFS needs to find it's boot device? Thanks for > the help. The only unique thing about XFS is that you cannot put lilo in the first sector of an XFS partition - it has to be in the MBR,* and the 1.0.1 installer won't let you do it any other way. You say "no LILO is installed on hda" - so how is booting set up? What error do you get when it fails? Also, not surprising that you can't boot from a floppy, since an XFS-capable kernel is tough to fit on a floppy. Should have put that info in the installer, I suppose. You can boot the CD and type "linux rescue" to poke around and re-configure the system if you need to... *This is because XFS puts data where LILO would otherwise go. I think this is in the FAQ. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 08:36:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QFaZF13061 for linux-xfs-outgoing; Thu, 26 Jul 2001 08:36:35 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QFaYV13041 for ; Thu, 26 Jul 2001 08:36:34 -0700 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6QFfIm32288 for ; Thu, 26 Jul 2001 08:41:18 -0700 Received: from sgi.com (root@chuckle.americas.sgi.com [128.162.211.44]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id IAA29872; Thu, 26 Jul 2001 08:35:57 -0700 (PDT) Message-ID: <3B603846.5B6A6980@sgi.com> Date: Thu, 26 Jul 2001 10:33:26 -0500 From: Eric Sandeen X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.2-SGI_XFS_1.0 i586) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Klaassen CC: linux-xfs@oss.sgi.com Subject: Re: Logdev size? References: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> <20010725205259.C2291@dkp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andrew Klaassen wrote: > > So a mkfs line along the lines of: > > > > mkfs -t xfs -f -i size=512 -l size=16384b /dev/xxx > > Hmmm. > > size 16384b specified for log subvolume is too large, maximum is 16032 blocks > > Is this a hard limit? Shouldn't be. How big is the partition you're putting it on? -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Jul 26 09:12:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QGCXl14761 for linux-xfs-outgoing; Thu, 26 Jul 2001 09:12:33 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QGCVV14742 for ; Thu, 26 Jul 2001 09:12:31 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 1E8FD1AB10 for ; Thu, 26 Jul 2001 12:12:30 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id BD6C1725; Thu, 26 Jul 2001 12:12:29 -0400 (EDT) Date: Thu, 26 Jul 2001 12:12:29 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Logdev size? Message-ID: <20010726121229.A2656@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> <20010725205259.C2291@dkp.com> <3B603846.5B6A6980@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B603846.5B6A6980@sgi.com> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 26, 2001 at 10:33:26AM -0500, Eric Sandeen wrote: > Andrew Klaassen wrote: > > Hmmm. > > > > size 16384b specified for log subvolume is too large, maximum is 16032 blocks > > > > Is this a hard limit? > Shouldn't be. How big is the partition you're putting it on? A little over a terabyte. One more logdev optimization question: does it make a big difference to overall filesystem performance whether the logdev is on a fast disk or a slow disk? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Thu Jul 26 09:27:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QGRj915033 for linux-xfs-outgoing; Thu, 26 Jul 2001 09:27:45 -0700 Received: from ausmail.coremetrics.com ([209.184.141.185]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QGRhV15014 for ; Thu, 26 Jul 2001 09:27:43 -0700 Received: by AUSMAIL with Internet Mail Service (5.5.2653.19) id <3N3HKMQP>; Thu, 26 Jul 2001 11:27:38 -0500 Message-ID: <85063BBE668FD411944400D0B744267A643526@AUSMAIL> From: "Gonyou, Austin" To: linux-xfs Subject: RE: Boot Failure after installing 1.0.1 Date: Thu, 26 Jul 2001 11:27:32 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk No lilo is installed on the system, for what ever reason. Right now the guy's trying to boot from a floppy, but has never been able to boot the system at all from the second disk. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: austin@coremetrics.com > -----Original Message----- > From: Eric Sandeen [mailto:sandeen@sgi.com] > Sent: Thursday, July 26, 2001 10:27 AM > To: Gonyou, Austin > Cc: linux-xfs > Subject: Re: Boot Failure after installing 1.0.1 > > > "Gonyou, Austin" wrote: > > > > A tech here has 2 hdd's on his system, hda and hdb. hda is > full with windows > > 2k, hdb is RH 7.1. All boot partitions are on hdb for linux. No LILO > > installed on hda. When installed with RH 7.1 SGI XFS > installer 1.0.1, the > > system will not boot at all from hdb, not even with a > floppy. If using no > > XFS, it will boot no problem. What is causing this behaviour? Is it > > something to do with the way XFS needs to find it's boot > device? Thanks for > > the help. > > The only unique thing about XFS is that you cannot put lilo > in the first > sector of an XFS partition - it has to be in the MBR,* and the 1.0.1 > installer won't let you do it any other way. You say "no LILO is > installed on hda" - so how is booting set up? What error do you get > when it fails? > > Also, not surprising that you can't boot from a floppy, since an > XFS-capable kernel is tough to fit on a floppy. Should have put that > info in the installer, I suppose. > > You can boot the CD and type "linux rescue" to poke around and > re-configure the system if you need to... > > *This is because XFS puts data where LILO would otherwise go. I think > this is in the FAQ. > > -Eric > > -- > Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs > sandeen@sgi.com SGI, Inc. > From owner-linux-xfs@oss.sgi.com Thu Jul 26 09:30:37 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QGUb315170 for linux-xfs-outgoing; Thu, 26 Jul 2001 09:30:37 -0700 Received: from rj.corp.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QGUZV15151 for ; Thu, 26 Jul 2001 09:30:35 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6QGYFU07376 for ; Thu, 26 Jul 2001 09:34:16 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2526725; Thu, 26 Jul 2001 11:29:14 -0500 (CDT) Received: from fsgi158.americas.sgi.com (fsgi158.americas.sgi.com [128.162.191.39]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA48988; Thu, 26 Jul 2001 11:29:13 -0500 (CDT) From: Tad Dolphay Received: by fsgi158.americas.sgi.com (SGI-8.9.3/SGI-client-1.7) id LAA54566; Thu, 26 Jul 2001 11:29:13 -0500 (CDT) Message-Id: <200107261629.LAA54566@fsgi158.americas.sgi.com> Subject: Re: umask bug To: lord@sgi.com (Steve Lord) Date: Thu, 26 Jul 2001 11:29:12 -0500 (CDT) Cc: tridge@valinux.com, linux-xfs@oss.sgi.com In-Reply-To: <200107261456.f6QEutx16789@jen.americas.sgi.com> from "Steve Lord" at Jul 26, 2001 09:56:55 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a known NFS problem and has been discussed in the NFS list. see http://www.geocrawler.com/archives/3/35/2001/7/1550 and look for Bug in NFS - should init be allowed to set umask Tad > > > I'm testing SPECsfs against the 2.4.7 cvs XFS patch and it's failing > > the validation phase. The problem is that directories are being > > created with the wrong permissions. You can see it like this: > > > > mount localhost:/export /mnt > > cd /mnt > > umask 0 > > mkdir foo > > ls -ld foo > > > > I thought initially it was a nfsd bug, perhaps getting the umask > > wrong, but I found that the bug doesn't happen with ext2. Also, > > creating files does get the right permisisons, but directories are > > wrong. > > > > Any ideas? Known problem perhaps? I'm new to XFS. > > > > Cheers, Tridge > > Wow, famous people! > > Hmm, I read this message and the fix message, I will take a look later > today, the fact that this does not happen to ext2 suggests there is > still something wrong in xfs - why would a fix in the nfs code be the > correct one if different filesystems exhibit different behaviors? > > Steve > > > From owner-linux-xfs@oss.sgi.com Thu Jul 26 09:44:54 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QGis915475 for linux-xfs-outgoing; Thu, 26 Jul 2001 09:44:54 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QGiqV15456 for ; Thu, 26 Jul 2001 09:44:52 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6QGnam03644 for ; Thu, 26 Jul 2001 09:49:36 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id LAA2536922; Thu, 26 Jul 2001 11:43:30 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id LAA10205; Thu, 26 Jul 2001 11:43:30 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6QGhCu16902; Thu, 26 Jul 2001 11:43:12 -0500 Message-Id: <200107261643.f6QGhCu16902@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Andrew Klaassen cc: linux-xfs@oss.sgi.com Subject: Re: Logdev size? In-Reply-To: Message from Andrew Klaassen of "Thu, 26 Jul 2001 12:12:29 EDT." <20010726121229.A2656@dkp.com> Date: Thu, 26 Jul 2001 11:43:12 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > Shouldn't be. How big is the partition you're putting it on? > > A little over a terabyte. > > One more logdev optimization question: does it make a big > difference to overall filesystem performance whether the logdev > is on a fast disk or a slow disk? > > Andrew Klaassen I made a log bigger than this just now. The important thing about the log device is a good transaction rate - ops per second matters, data rate does not really. Steve (in a hurry) From owner-linux-xfs@oss.sgi.com Thu Jul 26 11:03:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QI3a719999 for linux-xfs-outgoing; Thu, 26 Jul 2001 11:03:36 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QI3XV19968 for ; Thu, 26 Jul 2001 11:03:33 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id AEBCD1AB12 for ; Thu, 26 Jul 2001 14:03:32 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 64C57725; Thu, 26 Jul 2001 14:03:32 -0400 (EDT) Date: Thu, 26 Jul 2001 14:03:32 -0400 From: Andrew Klaassen To: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib Message-ID: <20010726140332.B2656@dkp.com> Mail-Followup-To: Linux XFS Mailing List References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 26, 2001 at 05:16:41PM +0800, Federico Sevilla III wrote: > On Thu, 26 Jul 2001 at 19:12, Nathan Scott wrote: > > If its in the "configure" stage, your xfsdump is out of date > How can the CVS copy be out of date? I just did a cvs update. :) > > if its the "build" stage then your xfslibs-dev is out of date > I just built xfsprogs from the same CVS copy. How can THAT be out of date? > > Basically, get the latest of both of these and it will work. > I already do. :) I noticed last night that I had some problems with "can't find libhandle", etc., after updating my CVS tree; there were some directories missing that cvs didn't grab, for some reason. I had to pull down a brand new CVS tree, start from scratch; then everything worked. Andrew Klaassen From owner-linux-xfs@oss.sgi.com Thu Jul 26 11:35:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QIZad25383 for linux-xfs-outgoing; Thu, 26 Jul 2001 11:35:36 -0700 Received: from rj.corp.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QIZYV25351 for ; Thu, 26 Jul 2001 11:35:34 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6QIdFU14119 for ; Thu, 26 Jul 2001 11:39:15 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f6QIYTf32111033 for ; Thu, 26 Jul 2001 11:34:29 -0700 (PDT) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA13671 for ; Thu, 26 Jul 2001 11:39:03 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 6198415A47E for ; Thu, 26 Jul 2001 11:33:08 -0700 (PDT) Subject: Re: Boot Failure after installing 1.0.1 From: Florin Andrei To: linux-xfs In-Reply-To: <85063BBE668FD411944400D0B744267A643521@AUSMAIL> References: <85063BBE668FD411944400D0B744267A643521@AUSMAIL> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11 (Beta Release) Date: 26 Jul 2001 11:33:08 -0700 Message-Id: <996172388.10185.37.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 26 Jul 2001 10:02:12 -0500, Gonyou, Austin wrote: > A tech here has 2 hdd's on his system, hda and hdb. hda is full with windows > 2k, hdb is RH 7.1. All boot partitions are on hdb for linux. No LILO > installed on hda. When installed with RH 7.1 SGI XFS installer 1.0.1, the > system will not boot at all from hdb, not even with a floppy. If using no > XFS, it will boot no problem. What is causing this behaviour? Is it > something to do with the way XFS needs to find it's boot device? Thanks for > the help. After having lots of problem with multiboot systems, i realised it's always better to keep a small (50 MB) /boot partition on /dev/hda no matter how you distribute everything else (for example: /dev/hda1 is /boot, put vindoze on /dev/hda2 and Linux on /dev/hdb*), make /boot partition Ext2, mark it with the "bootable" flag in fdisk, and install lilo on /boot's superblock. This way, i was able to have many OSs on my computer, all of them booted from lilo. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 26 11:42:26 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QIgQ126604 for linux-xfs-outgoing; Thu, 26 Jul 2001 11:42:26 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QIgOV26585 for ; Thu, 26 Jul 2001 11:42:24 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6QIl8m09664 for ; Thu, 26 Jul 2001 11:47:08 -0700 Received: from crom.corp.sgi.com (crom.corp.sgi.com [130.62.63.32]) by nodin.corp.sgi.com (8.11.4/8.11.2/nodin-1.0) with ESMTP id f6QIfIf32751073 for ; Thu, 26 Jul 2001 11:41:18 -0700 (PDT) Received: from stantz.corp.sgi.com (stantz.corp.sgi.com [130.62.175.86]) by crom.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id LAA33358 for ; Thu, 26 Jul 2001 11:45:57 -0700 (PDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 692F215A47E for ; Thu, 26 Jul 2001 11:40:02 -0700 (PDT) Subject: Re: more comparisons... From: Florin Andrei To: linux-xfs In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11 (Beta Release) Date: 26 Jul 2001 11:40:02 -0700 Message-Id: <996172802.10323.44.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On 26 Jul 2001 21:12:25 +0800, Federico Sevilla III wrote: > > Well, I wouldn't like to start ranting and ranting about them, but I think > ReiserFS is great for small files and for the rest, XFS. :) 100% agree. > > XFS is a nice fs for a ftp mirror with ISO images and distributions. > > Not only that, it's great if you're burning CDs from ISOs in them over a > network. I noticed ReiserFS is rather jerky when it comes to this, and > jerkiness leads to underruns that leads to coasters. XFS seems to be nice also for databases, like when you have large MySQL tables. ;-) It looks like i will convert var.corp (SGI's big logging server) to a Linux machine running msyslog (new syslog, better than syslog-ng, much better than traditional syslog) and MySQL, and redirect all logs into MySQL tables. Everything will be on XFS. When this baby will start kicking, i'll give you some more feedback. ;-) msyslog: http://www.corest.com/download/download1.html > Of course this is all unofficial. I don't have statistical data to back me > up. I have personal experience, though. And for that only my Squid cache > remains on ReiserFS. :) Like i said, 100% agree. -- Florin Andrei From owner-linux-xfs@oss.sgi.com Thu Jul 26 12:55:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QJt8k06823 for linux-xfs-outgoing; Thu, 26 Jul 2001 12:55:08 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QJt5V06792 for ; Thu, 26 Jul 2001 12:55:05 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id MAA08471 for ; Thu, 26 Jul 2001 12:52:46 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id OAA2539007; Thu, 26 Jul 2001 14:53:45 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id OAA73232; Thu, 26 Jul 2001 14:53:44 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6QJrO518223; Thu, 26 Jul 2001 14:53:24 -0500 Message-Id: <200107261953.f6QJrO518223@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Keith Owens , tridge@valinux.com cc: linux-xfs@oss.sgi.com Subject: Re: umask fix (patch) In-Reply-To: Message from Keith Owens of "Thu, 26 Jul 2001 13:11:56 +1000." <18265.996117116@kao2.melbourne.sgi.com> Date: Thu, 26 Jul 2001 14:53:24 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > On Wed, 25 Jul 2001 19:24:17 -0700 (PDT), > Andrew Tridgell wrote: > >The problem turned out to be in the nfsd code. The following fixes it: > > > >--- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 > >+++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 > >@@ -150,6 +150,7 @@ > > MOD_INC_USE_COUNT; > > lock_kernel(); > > daemonize(); > >+ current->fs->umask = 0; > > sprintf(current->comm, "nfsd"); > > current->rlim[RLIMIT_FSIZE].rlim_cur = RLIM_INFINITY; > > Kernel threads share the init task fs context. That change makes all > future kernel threads run with umask 0, a big security exposure. This > problem was supposed to have been fixed in 2.4.7-pre7. There is an XFS bug in here, I am not quite sure how to fix it at the moment though.... Basically the fix which went into 2.4.7-pre7 moved where the process umask was applied to the creation mask to be outside of vfs_create and vfs_mkdir, NFS gets to pass in its own mask - presumably passed along from the client with that umask applied. The problem is the acl code added in the xfs patch. There is code in the mainline kernel which skips the umask if the filesystem has acl support defined in a superblock flag, the filesystem then applies the umask itself if there is no default acl for that directory. So this chunk of code in the xfs create path: fs/xfs/linux/xfs_iops.c have_default_acl = _ACL_GET_DEFAULT(dvp, &pdacl); if (!have_default_acl) { mode &= ~current->fs->umask; } Will be applying the process umask even if we are coming from nfs, negating the fix in the vfs & nfs code. So far the only 'workaround' I can come up with is this: have_default_acl = _ACL_GET_DEFAULT(dvp, &pdacl); if (strcmp(current->comm, "nfsd") && !have_default_acl) { mode &= ~current->fs->umask; } I think that would fix it, but I really don't like it. Steve From owner-linux-xfs@oss.sgi.com Thu Jul 26 13:08:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QK8HP09157 for linux-xfs-outgoing; Thu, 26 Jul 2001 13:08:17 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QK8EV09135 for ; Thu, 26 Jul 2001 13:08:15 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA26697; Thu, 26 Jul 2001 22:08:12 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA10030; Thu, 26 Jul 2001 22:08:12 +0200 (CEST) Date: Thu, 26 Jul 2001 22:08:12 +0200 (CEST) From: Seth Mos To: "Gonyou, Austin" cc: linux-xfs Subject: Re: Boot Failure after installing 1.0.1 In-Reply-To: <85063BBE668FD411944400D0B744267A643521@AUSMAIL> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001, Gonyou, Austin wrote: > A tech here has 2 hdd's on his system, hda and hdb. hda is full with windows > 2k, hdb is RH 7.1. All boot partitions are on hdb for linux. No LILO > installed on hda. When installed with RH 7.1 SGI XFS installer 1.0.1, the > system will not boot at all from hdb, not even with a floppy. If using no > XFS, it will boot no problem. What is causing this behaviour? Is it > something to do with the way XFS needs to find it's boot device? Thanks for > the help. You can not install lilo on a XFS partition. It's in the FAQ. > > -- > Austin Gonyou > Systems Architect, CCNA > Coremetrics, Inc. > Phone: 512-796-9023 > email: austin@coremetrics.com > > From owner-linux-xfs@oss.sgi.com Thu Jul 26 13:15:17 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QKFHi10450 for linux-xfs-outgoing; Thu, 26 Jul 2001 13:15:17 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QKFFV10430 for ; Thu, 26 Jul 2001 13:15:15 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA27655; Thu, 26 Jul 2001 22:15:13 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA10501; Thu, 26 Jul 2001 22:15:13 +0200 (CEST) Date: Thu, 26 Jul 2001 22:15:13 +0200 (CEST) From: Seth Mos To: Steve Lord cc: Andrew Klaassen , linux-xfs@oss.sgi.com Subject: Re: Logdev size? In-Reply-To: <200107261643.f6QGhCu16902@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001, Steve Lord wrote: > > > > Shouldn't be. How big is the partition you're putting it on? > > > > A little over a terabyte. > > > > One more logdev optimization question: does it make a big > > difference to overall filesystem performance whether the logdev > > is on a fast disk or a slow disk? > > > > Andrew Klaassen > > I made a log bigger than this just now. The important thing about the > log device is a good transaction rate - ops per second matters, data > rate does not really. I have already made logs larger then this on a 30GB partition so it should be possible unless you are running in to some weird kfs issues. There was one problem on a terabyte setup but those were inode problems. A 15K RPM Cheetah or a solid state disk was probably the best after much discussion :-) So I'd say, yes, the faster disk. The raid array can probably work out the throughput problems using many disks. Cheers Seth From owner-linux-xfs@oss.sgi.com Thu Jul 26 13:16:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QKG0E10695 for linux-xfs-outgoing; Thu, 26 Jul 2001 13:16:00 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QKFvV10668 for ; Thu, 26 Jul 2001 13:15:58 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA27808; Thu, 26 Jul 2001 22:15:56 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id WAA10529; Thu, 26 Jul 2001 22:15:56 +0200 (CEST) Date: Thu, 26 Jul 2001 22:15:56 +0200 (CEST) From: Seth Mos To: Andrew Klaassen cc: Linux XFS Mailing List Subject: Re: xfsdump looking for libhandle.la in /lib In-Reply-To: <20010726140332.B2656@dkp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001, Andrew Klaassen wrote: > On Thu, Jul 26, 2001 at 05:16:41PM +0800, > Federico Sevilla III wrote: > > > On Thu, 26 Jul 2001 at 19:12, Nathan Scott wrote: > > > > If its in the "configure" stage, your xfsdump is out of date > > > How can the CVS copy be out of date? I just did a cvs update. :) > > > > if its the "build" stage then your xfslibs-dev is out of date > > > I just built xfsprogs from the same CVS copy. How can THAT be out of date? > > > > Basically, get the latest of both of these and it will work. > > > I already do. :) > > I noticed last night that I had some problems with "can't find > libhandle", etc., after updating my CVS tree; there were some > directories missing that cvs didn't grab, for some reason. I > had to pull down a brand new CVS tree, start from scratch; then > everything worked. update with the -d option to fetch new directories. Cheers Seth From owner-linux-xfs@oss.sgi.com Thu Jul 26 15:26:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QMQPM32467 for linux-xfs-outgoing; Thu, 26 Jul 2001 15:26:25 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QMQMV32438 for ; Thu, 26 Jul 2001 15:26:22 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id PAA01868 for ; Thu, 26 Jul 2001 15:24:03 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2540676 for ; Thu, 26 Jul 2001 17:25:06 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA38452 for ; Thu, 26 Jul 2001 17:25:06 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6QMOiv20189; Thu, 26 Jul 2001 17:24:44 -0500 Message-Id: <200107262224.f6QMOiv20189@jen.americas.sgi.com> Date: Thu, 26 Jul 2001 17:24:44 -0500 Subject: TAKE - fix up merge cruft Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Eric pointed out that the patch appeared larger than it should be, inspection showed that the following files were in there with different rcs revisions, looks like my merge tool automatically skips this. So this is a zero sum mod, it changes some rcs version strings and that is about it. Date: Thu Jul 26 15:21:59 PDT 2001 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:99665a linux/drivers/isdn/hisax/sedlbauer.c - 1.16 linux/drivers/isdn/hisax/hisax.h - 1.20 linux/drivers/isdn/hisax/elsa.c - 1.14 linux/drivers/isdn/hisax/config.c - 1.22 linux/drivers/isdn/hisax/asuscom.c - 1.12 linux/drivers/isdn/hisax/bkm_a8.c - 1.11 linux/drivers/isdn/hisax/bkm_a4t.c - 1.11 linux/drivers/net/sk98lin/skxmac2.c - 1.5 linux/drivers/net/sk98lin/skgepnmi.c - 1.5 linux/drivers/net/sk98lin/h/skgeinit.h - 1.4 linux/drivers/net/sk98lin/skgesirq.c - 1.5 linux/drivers/net/sk98lin/h/skaddr.h - 1.4 linux/drivers/net/sk98lin/h/skcsum.h - 1.4 linux/drivers/net/sk98lin/h/skdrv1st.h - 1.5 linux/drivers/net/sk98lin/h/skdrv2nd.h - 1.4 linux/drivers/net/sk98lin/skrlmt.c - 1.4 linux/drivers/net/sk98lin/h/skgehw.h - 1.5 linux/drivers/net/sk98lin/skgeinit.c - 1.5 linux/drivers/net/sk98lin/skge.c - 1.12 linux/drivers/net/sk98lin/h/skgepnm2.h - 1.4 linux/drivers/net/sk98lin/h/skgepnmi.h - 1.4 linux/drivers/net/sk98lin/h/skgesirq.h - 1.4 linux/drivers/net/sk98lin/h/ski2c.h - 1.4 linux/drivers/net/sk98lin/h/skrlmt.h - 1.4 linux/drivers/net/sk98lin/h/skvpd.h - 1.4 linux/drivers/net/sk98lin/h/xmac_ii.h - 1.5 linux/drivers/net/sk98lin/skaddr.c - 1.4 linux/drivers/net/sk98lin/skcsum.c - 1.4 linux/drivers/isdn/hisax/hfc_sx.c - 1.8 linux/drivers/isdn/avmb1/b1dma.c - 1.16 linux/drivers/isdn/hysdn/boardergo.c - 1.11 linux/drivers/isdn/hisax/nj_u.c - 1.7 linux/drivers/isdn/hisax/nj_s.c - 1.7 linux/arch/cris/Makefile - 1.5 linux/arch/cris/drivers/ethernet.c - 1.5 linux/arch/cris/drivers/ide.c - 1.5 linux/arch/cris/drivers/serial.c - 1.6 linux/arch/cris/kernel/Makefile - 1.4 linux/arch/cris/kernel/entry.S - 1.6 linux/arch/cris/kernel/head.S - 1.5 linux/arch/cris/kernel/irq.c - 1.5 linux/arch/cris/kernel/process.c - 1.5 linux/arch/cris/kernel/setup.c - 1.5 linux/arch/cris/kernel/sys_cris.c - 1.5 linux/arch/cris/kernel/time.c - 1.3 linux/arch/cris/kernel/traps.c - 1.4 linux/arch/cris/lib/checksum.S - 1.4 linux/arch/cris/lib/checksumcopy.S - 1.4 linux/include/asm-cris/semaphore.h - 1.3 linux/include/asm-cris/delay.h - 1.4 linux/include/asm-cris/dma.h - 1.3 linux/include/asm-cris/irq.h - 1.5 linux/arch/cris/drivers/gpio.c - 1.4 linux/arch/cris/drivers/usb-host.c - 1.4 linux/arch/cris/lib/dram_init.S - 1.4 linux/arch/cris/drivers/ds1302.c - 1.3 linux/arch/cris/drivers/parport.c - 1.3 linux/drivers/mtd/nand/spia.c - 1.3 linux/drivers/mtd/nand/Config.in - 1.3 linux/drivers/isdn/tpam/tpam_main.c - 1.3 linux/drivers/net/sk98lin/h/skversion.h - 1.2 linux/drivers/net/sk98lin/skproc.c - 1.2 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.2 linux/drivers/scsi/pcmcia/nsp_cs.h - 1.2 linux/drivers/scsi/pcmcia/nsp_debug.c - 1.2 linux/drivers/scsi/pcmcia/nsp_io.h - 1.2 linux/arch/cris/drivers/lpslave/bintocarr.pl - 1.2 linux/arch/cris/drivers/lpslave/e100lpslave.S - 1.2 linux/arch/cris/drivers/lpslave/e100lpslavenet.c - 1.2 linux/drivers/char/ser_a2232.c - 1.2 linux/drivers/char/ser_a2232.h - 1.2 linux/drivers/char/ser_a2232fw.h - 1.2 From owner-linux-xfs@oss.sgi.com Thu Jul 26 15:40:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6QMeMR02502 for linux-xfs-outgoing; Thu, 26 Jul 2001 15:40:22 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6QMeKV02477 for ; Thu, 26 Jul 2001 15:40:20 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id AAA174937 for ; Fri, 27 Jul 2001 00:39:54 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2540143 for ; Thu, 26 Jul 2001 17:39:01 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA75731 for ; Thu, 26 Jul 2001 17:39:01 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6QMcej20281; Thu, 26 Jul 2001 17:38:40 -0500 Message-Id: <200107262238.f6QMcej20281@jen.americas.sgi.com> Date: Thu, 26 Jul 2001 17:38:40 -0500 Subject: TAKE - fix direct I/O read beyond eof Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Date: Thu Jul 26 15:37:58 PDT 2001 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:99666a linux/fs/pagebuf/page_buf_io.c - 1.91 - Endcase check for direct read From owner-linux-xfs@oss.sgi.com Thu Jul 26 17:28:45 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6R0SjG20785 for linux-xfs-outgoing; Thu, 26 Jul 2001 17:28:45 -0700 Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6R0ShV20760 for ; Thu, 26 Jul 2001 17:28:43 -0700 Received: by lists.samba.org (Postfix, from userid 1002) id BDAD34599; Thu, 26 Jul 2001 17:23:42 -0700 (PDT) From: Andrew Tridgell To: lord@sgi.com Cc: kaos@melbourne.sgi.com, linux-xfs@oss.sgi.com In-reply-to: <200107261953.f6QJrO518223@jen.americas.sgi.com> (message from Steve Lord on Thu, 26 Jul 2001 14:53:24 -0500) Subject: Re: umask fix (patch) Reply-To: tridge@valinux.com References: <200107261953.f6QJrO518223@jen.americas.sgi.com> Message-Id: <20010727002342.BDAD34599@lists.samba.org> Date: Thu, 26 Jul 2001 17:23:42 -0700 (PDT) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I think that nfsd should always run with a umask of 0, its umask should not depend on what umask was set in the sysadmins shell when it was launched. So nfsd should get its own fs context when it starts up (preferably in daemonise()) then it should set the umask to 0. Running nfsd with some random umask is just asking for trouble in the future. If we _really_ want to do that then we should force the umask to 0777 in nfsd so that we at least catch these bugs quickly. > if (strcmp(current->comm, "nfsd") && !have_default_acl) { > mode &= ~current->fs->umask; > } > > I think that would fix it, but I really don't like it. arrgh - that is truly awful! Don't be tempted :) btw, to see a related problem with sharing fs/file contexts in the kernel try this: ls -l /proc/*/fd | grep initctl I submitted a patch to Linus a few weeks back to try to fix this by not using CLONE_* flags so agressively for kernel threads. I'll try submitting it again when I get time. From owner-linux-xfs@oss.sgi.com Thu Jul 26 18:21:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6R1L3s29103 for linux-xfs-outgoing; Thu, 26 Jul 2001 18:21:03 -0700 Received: from lists.samba.org (samba.sourceforge.net [198.186.203.85]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6R1L1V29080 for ; Thu, 26 Jul 2001 18:21:01 -0700 Received: by lists.samba.org (Postfix, from userid 1002) id 6F2D345EA; Thu, 26 Jul 2001 18:16:01 -0700 (PDT) From: Andrew Tridgell To: linux-xfs@oss.sgi.com In-reply-to: <20010726121229.A2656@dkp.com> (message from Andrew Klaassen on Thu, 26 Jul 2001 12:12:29 -0400) Subject: Re: Logdev size? Reply-To: tridge@samba.org References: <200107241352.f6ODqZJ23995@jen.americas.sgi.com> <20010725205259.C2291@dkp.com> <3B603846.5B6A6980@sgi.com> <20010726121229.A2656@dkp.com> Message-Id: <20010727011601.6F2D345EA@lists.samba.org> Date: Thu, 26 Jul 2001 18:16:01 -0700 (PDT) Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk A related question about logdev sizes ... I've noticed that mkfs.xfs refuses to make a logdev bigger than 128M. Have anyone done any work on upping this limit? I'd like to put the logdev on a 1G ram card so that I can do really large netbench runs without hitting the real disks. I'm testing at the moment with the logdev on a ramdisk (see http://samba.org/ftp/unpacked/junkcode/trd/) but the 130M limit means those pesky disk lights come on with even quite small runs. also, is there any work being done to use the same logdev for multiple filesystems? Having to know in advance how to split up a valuable nv ram area over lots of filsystems can be tricky. From owner-linux-xfs@oss.sgi.com Thu Jul 26 19:50:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6R2oaA04957 for linux-xfs-outgoing; Thu, 26 Jul 2001 19:50:36 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6R2oWV04938 for ; Thu, 26 Jul 2001 19:50:32 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id SAA05481 for ; Thu, 26 Jul 2001 18:41:55 -0700 (PDT) mail_from (tes@boing.melbourne.sgi.com) Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA48282; Fri, 27 Jul 2001 11:40:55 +1000 (EST) Date: Fri, 27 Jul 2001 11:40:55 +1000 From: Timothy Shimmin To: Steve Lord Cc: Keith Owens , tridge@valinux.com, linux-xfs@oss.sgi.com, ag@bestbits.at Subject: Re: umask fix (patch) Message-ID: <20010727114055.N37341@boing.melbourne.sgi.com> References: <200107261953.f6QJrO518223@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200107261953.f6QJrO518223@jen.americas.sgi.com>; from lord@sgi.com on Thu, Jul 26, 2001 at 02:53:24PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, On Thu, Jul 26, 2001 at 02:53:24PM -0500, Steve Lord wrote: > > On Wed, 25 Jul 2001 19:24:17 -0700 (PDT), > > Andrew Tridgell wrote: > > >The problem turned out to be in the nfsd code. The following fixes it: > > > > > >--- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 > > >+++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 > > >@@ -150,6 +150,7 @@ > > > MOD_INC_USE_COUNT; > > > lock_kernel(); > > > daemonize(); > > >+ current->fs->umask = 0; > > > sprintf(current->comm, "nfsd"); > > > current->rlim[RLIMIT_FSIZE].rlim_cur = RLIM_INFINITY; > > > > Kernel threads share the init task fs context. That change makes all > > future kernel threads run with umask 0, a big security exposure. This > > problem was supposed to have been fixed in 2.4.7-pre7. > > There is an XFS bug in here, I am not quite sure how to fix it at the > moment though.... > > Basically the fix which went into 2.4.7-pre7 moved where the process > umask was applied to the creation mask to be outside of vfs_create > and vfs_mkdir, NFS gets to pass in its own mask - presumably passed > along from the client with that umask applied. > So where did this application of the umask get moved to ? Can the acl default test be moved to the new point where the umask is applied ? This ACL code had to be added because we don't want the umask applied to the mode if the parent directory has default ACLs to apply. (following 1003.1e standard) So if the mode has the umask applied to it before we get to play with ACLs then we're stuffed. We have to stop the mode being changed at that point. Andreas did the same sort of thing with his EA/ACL patch; we checked with his code before doing this. (So I'm not sure how we are going to keep to the standard if NFS clients are going to modify the mode with the umask before we get to see the mode - if that's what's happening) --Tim > The problem is the acl code added in the xfs patch. There is code in > the mainline kernel which skips the umask if the filesystem has acl > support defined in a superblock flag, the filesystem then applies the > umask itself if there is no default acl for that directory. So this > chunk of code in the xfs create path: > > > fs/xfs/linux/xfs_iops.c > have_default_acl = _ACL_GET_DEFAULT(dvp, &pdacl); > if (!have_default_acl) { > mode &= ~current->fs->umask; > } > > Will be applying the process umask even if we are coming from nfs, > negating the fix in the vfs & nfs code. > > So far the only 'workaround' I can come up with is this: > > have_default_acl = _ACL_GET_DEFAULT(dvp, &pdacl); > > if (strcmp(current->comm, "nfsd") && !have_default_acl) { > mode &= ~current->fs->umask; > } > > I think that would fix it, but I really don't like it. > > Steve From owner-linux-xfs@oss.sgi.com Thu Jul 26 23:13:12 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6R6DC616398 for linux-xfs-outgoing; Thu, 26 Jul 2001 23:13:12 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6R6D9V16379 for ; Thu, 26 Jul 2001 23:13:09 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA18600 for ; Fri, 27 Jul 2001 08:13:07 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA05589 for linux-xfs@oss.sgi.com; Fri, 27 Jul 2001 08:13:07 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id AD85857306 for ; Fri, 27 Jul 2001 08:12:32 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 9B45D25836 for ; Fri, 27 Jul 2001 08:12:32 +0200 (CEST) Message-ID: <3B610650.3F882DD4@ch.sauter-bc.com> Date: Fri, 27 Jul 2001 08:12:32 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: Install hangs at end of postinstall configuration Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have installed a new server (7.1-XFS 1.0.1) via NFS yesterday. everything went fine except at the end of the 'Postinstall configuration', it was hanging and I couldn't figure out what happened. It was a server type install with only NFS server selected. When it was hanging I just switched to a console and made a chroot /mnt/sysimage /sbin/lilo to make sure lilo is installed. After that I just killed the hanging processes and the system rebooted and is fine now. Did anybody notice this kind of hanger before and how can I find out what's wrong when something like that happens again. I mean where do I find logs created by anaconda and co? Simon -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Fri Jul 27 01:13:27 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6R8DRI21803 for linux-xfs-outgoing; Fri, 27 Jul 2001 01:13:27 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.5]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6R8DOV21782 for ; Fri, 27 Jul 2001 01:13:24 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id KAA04206 for ; Fri, 27 Jul 2001 10:13:22 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id KAA15511 for linux-xfs@oss.sgi.com; Fri, 27 Jul 2001 10:13:21 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id B279F57306 for ; Fri, 27 Jul 2001 10:12:50 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id C7C6425835 for ; Fri, 27 Jul 2001 10:12:49 +0200 (CEST) Message-ID: <3B612281.F91E7FB8@ch.sauter-bc.com> Date: Fri, 27 Jul 2001 10:12:49 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: linux-xfs Subject: New XFS aware RPMs for mkinitrd and mkbootdisk Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I have just built patched RPM's to solve two well known problems with the XFS 1.0 and 1.0.1 installer. mkinitrd-3.0.10-1XFS.i386.rpm: Fixed initrd for those who are running softRAID with devfs enabled. The raidautorun was not successful with the initial ramdisk created whith devfs enabled. mkbootdisk-1.4.2-1XFS.i386.rpm: Incorporates the patch to enable creation of overformated bootdisks with something like mkbootdisk --device /dev/fd0u1722 XXX. Would be nice if somebody could integrate this into the installer and build new iso's so we could resync. Oh yes, here it is [http://home.datacomm.ch/~simix/XFS/] -Simon -- Simon Matter Tel: +41 61 695 57 35 Fr.Sauter AG / CIT Fax: +41 61 695 53 30 Im Surinam 55 CH-4016 Basel [mailto:simon.matter@ch.sauter-bc.com] From owner-linux-xfs@oss.sgi.com Fri Jul 27 04:11:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RBBD900739 for linux-xfs-outgoing; Fri, 27 Jul 2001 04:11:13 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RBBBV00720 for ; Fri, 27 Jul 2001 04:11:11 -0700 Received: from xs4.xs4all.nl (xs4.xs4all.nl [194.109.6.45]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA05691; Fri, 27 Jul 2001 13:11:09 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs4.xs4all.nl (8.9.0/8.9.0) with ESMTP id NAA01691; Fri, 27 Jul 2001 13:11:09 +0200 (CEST) Date: Fri, 27 Jul 2001 13:11:09 +0200 (CEST) From: Seth Mos To: tridge@samba.org cc: linux-xfs@oss.sgi.com Subject: Re: Logdev size? In-Reply-To: <20010727011601.6F2D345EA@lists.samba.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, 26 Jul 2001, Andrew Tridgell wrote: > A related question about logdev sizes ... > > I've noticed that mkfs.xfs refuses to make a logdev bigger than > 128M. Have anyone done any work on upping this limit? Not that I know off. I believe it's the upper limit. > I'd like to put the logdev on a 1G ram card so that I can do really > large netbench runs without hitting the real disks. I'm testing at the > moment with the logdev on a ramdisk (see > http://samba.org/ftp/unpacked/junkcode/trd/) but the 130M limit means > those pesky disk lights come on with even quite small runs. Yes. The log is a write through construction. Even if you have a 1G log the linux kernel will put pressure on getting the data to the actual disk. I am afraid that will be very hard to avoid. The log is only a intermediate area where metadata gets stored before it is commited. You might try making the fs on the 1G solid state disk. Using it just for the logdev won't make the IO for the data go away. > also, is there any work being done to use the same logdev for multiple > filesystems? Having to know in advance how to split up a valuable nv > ram area over lots of filsystems can be tricky. That would be hard to do, reiserfs is stilling working on making wandering logs so the log activity will be spread throughout the partition instead of working on the same spot over and over. They don't have external logs either untill v4. From owner-linux-xfs@oss.sgi.com Fri Jul 27 05:01:07 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RC17t06830 for linux-xfs-outgoing; Fri, 27 Jul 2001 05:01:07 -0700 Received: from smtp-1.worldonline.cz (smtp-1.worldonline.cz [195.146.100.76]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RC13V06797 for ; Fri, 27 Jul 2001 05:01:04 -0700 Received: from gw (ppp1132.brno.worldonline.cz [212.90.229.229]) by smtp-1.worldonline.cz (8.9.3 (WOL 1.2.3)/8.9.3) with ESMTP id NAA03279 for ; Fri, 27 Jul 2001 13:59:56 +0200 (MET DST) Message-Id: <200107271159.NAA03279@smtp-1.worldonline.cz> From: "Jaroslav Lukesh" To: Subject: XFX1.0.1, partition "/" and Update disk 20/07/2001 Date: Fri, 27 Jul 2001 13:46:37 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1155 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi all, I cannot make bigger than 1024MB partition "/" from disk druid at SGI-XFX 1.0.1 with Update disk 20/07/2001. Installation is without "/boot" partition due following: The "/boot" partition was created at wrong place (/dev/sda7 instead of /dev/sda1) with disk druid, but it does original REdHat too. Solution: using fdisk instead ddruid or kickstart with "--onprimary 1", but I want to install system and then make kickstart. (and Iam not familiar with plain fdisk). Should someone make new update disk that will fix maximal size of bootable partition? Sincerelly Jaroslav Lukesh, K-net -------------------------------------------------- http://www.k-net.cz Multimedia, Networking, Communications Windows terminals, NC computer hardware and software -------------------------------------------------- note: Bill Gates to Hell! PS: part of Kickstart for RAID-1 who interested: # /boot part raid.01 --size 20 --ondisk sda --onprimary 1 part raid.02 --size 20 --ondisk sdb --onprimary 1 raid /boot raid.01 raid.02 --level 1 --device md0 # /data part raid.03 --size 300 --ondisk sda --grow part raid.04 --size 300 --ondisk sdb --grow raid /data raid.03 raid.04 --level 1 --device md1 # swap part raid.05 --size 127 --ondisk sda part raid.06 --size 127 --ondisk sdb raid swap raid.05 raid.06 --level 1 --device md2 # / part raid.07 --size 1500 --ondisk sda part raid.08 --size 1500 --ondisk sdb raid / raid.07 raid.08 --level 1 --device md3 lilo --location mbr From owner-linux-xfs@oss.sgi.com Fri Jul 27 05:13:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RCDij08377 for linux-xfs-outgoing; Fri, 27 Jul 2001 05:13:44 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RCDfV08350 for ; Fri, 27 Jul 2001 05:13:41 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6RCISm04828 for ; Fri, 27 Jul 2001 05:18:28 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id HAA2500995; Fri, 27 Jul 2001 07:12:20 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id HAA86669; Fri, 27 Jul 2001 07:12:20 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6RCBrm22376; Fri, 27 Jul 2001 07:11:53 -0500 Message-Id: <200107271211.f6RCBrm22376@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: tridge@samba.org cc: linux-xfs@oss.sgi.com Subject: Re: Logdev size? In-Reply-To: Message from Andrew Tridgell of "Thu, 26 Jul 2001 18:16:01 PDT." <20010727011601.6F2D345EA@lists.samba.org> Date: Fri, 27 Jul 2001 07:11:52 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > A related question about logdev sizes ... > > I've noticed that mkfs.xfs refuses to make a logdev bigger than > 128M. Have anyone done any work on upping this limit? In general XFS logs are fairly compact - we only log deltas to buffers not whole buffers, and if something is changed a second time whilst there is still a copy in the log we relog and free the old space. so once you get to the state where you are doing sufficient work to fill a big log you are doing so much disk I/O in other places it does not matter. The other issue with bigger logs is mount gets slower - there is a binary chop search of the log looking for its head and tail at mount time. Clearly, more time is required for recovery too - probably not a huge issue with a ram disk. An issue with internal log size is it must fit within an allocation group in the filesystem (an allocation group is an internal division of the disk space into a self managed chunk of space) we usually have 8 on a small filesystem, this is the limiting factor there. Once the log is external or the allocation groups big (4G max) this goes away. The real answer about growing the max size is I cannot think of a field size which will be exceeded by growing beyond this, but I have my suspicions you will hit something. I did a quick test with a 256M log and it appeared to function - I crashed it and recovery ran fine. No guarantees, but try this patch and rebuild mkfs (do a make clean, it does not appear to do header file dependencies): =========================================================================== Index: cmd/xfsprogs/include/xfs_fs.h =========================================================================== --- /usr/tmp/TmpDir.22316-0/cmd/xfsprogs/include/xfs_fs.h_1.7 Fri Jul 27 06:56:45 2001 +++ cmd/xfsprogs/include/xfs_fs.h Fri Jul 27 06:56:26 2001 @@ -231,9 +231,9 @@ */ #define XFS_MIN_AG_BLOCKS 64 #define XFS_MIN_LOG_BLOCKS 512 -#define XFS_MAX_LOG_BLOCKS (64 * 1024) +#define XFS_MAX_LOG_BLOCKS (256 * 1024) #define XFS_MIN_LOG_BYTES (256 * 1024) -#define XFS_MAX_LOG_BYTES (128 * 1024 * 1024) +#define XFS_MAX_LOG_BYTES (1024 * 1024 * 1024) /* * XFS_IOC_FSGROWFSDATA I have to think about this somemore and ask around, I may be missing something. > > I'd like to put the logdev on a 1G ram card so that I can do really > large netbench runs without hitting the real disks. I'm testing at the > moment with the logdev on a ramdisk (see > http://samba.org/ftp/unpacked/junkcode/trd/) but the 130M limit means > those pesky disk lights come on with even quite small runs. All I can say is you lucky dog! > > also, is there any work being done to use the same logdev for multiple > filesystems? Having to know in advance how to split up a valuable nv > ram area over lots of filsystems can be tricky. There is no way to share a log between filesystems, there is no identification in the log records as to who they belong to. I did work out how to edit a filesystem to put multiple logs into one partition, but I suspect your ram device could just be partitioned. Here for the record is a pointer to how to move a log - this should really be done in a utility program: http://oss.sgi.com/projects/xfs/mail_archive/0107/msg00564.html At the end of this there is a comment about how to make multiple logs on one device. I do not anticipate being able to share a single log across filesystems, Stephen Tweedie architected this in from the start for ext3, in XFS it was never even thought about. Steve From owner-linux-xfs@oss.sgi.com Fri Jul 27 05:16:50 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RCGoa08787 for linux-xfs-outgoing; Fri, 27 Jul 2001 05:16:50 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RCGmV08762 for ; Fri, 27 Jul 2001 05:16:48 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6RCLZm04906 for ; Fri, 27 Jul 2001 05:21:35 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id HAA2528726; Fri, 27 Jul 2001 07:15:16 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id HAA43891; Fri, 27 Jul 2001 07:15:15 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6RCEmD22386; Fri, 27 Jul 2001 07:14:48 -0500 Message-Id: <200107271214.f6RCEmD22386@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Timothy Shimmin cc: Steve Lord , Keith Owens , tridge@valinux.com, linux-xfs@oss.sgi.com, ag@bestbits.at Subject: Re: umask fix (patch) In-Reply-To: Message from Timothy Shimmin of "Fri, 27 Jul 2001 11:40:55 +1000." <20010727114055.N37341@boing.melbourne.sgi.com> Date: Fri, 27 Jul 2001 07:14:48 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hi there, > > On Thu, Jul 26, 2001 at 02:53:24PM -0500, Steve Lord wrote: > > > On Wed, 25 Jul 2001 19:24:17 -0700 (PDT), > > > Andrew Tridgell wrote: > > > >The problem turned out to be in the nfsd code. The following fixes it: > > > > > > > >--- fs/nfsd/nfssvc.c 2001/05/29 19:53:13 1.13 > > > >+++ fs/nfsd/nfssvc.c 2001/07/26 02:27:26 > > > >@@ -150,6 +150,7 @@ > > > > MOD_INC_USE_COUNT; > > > > lock_kernel(); > > > > daemonize(); > > > >+ current->fs->umask = 0; > > > > sprintf(current->comm, "nfsd"); > > > > current->rlim[RLIMIT_FSIZE].rlim_cur = RLIM_INFINITY; > > > > > > Kernel threads share the init task fs context. That change makes all > > > future kernel threads run with umask 0, a big security exposure. This > > > problem was supposed to have been fixed in 2.4.7-pre7. > > > > There is an XFS bug in here, I am not quite sure how to fix it at the > > moment though.... > > > > Basically the fix which went into 2.4.7-pre7 moved where the process > > umask was applied to the creation mask to be outside of vfs_create > > and vfs_mkdir, NFS gets to pass in its own mask - presumably passed > > along from the client with that umask applied. > > > So where did this application of the umask get moved to ? > Can the acl default test be moved to the new point where > the umask is applied ? Take a look at the callers of vfs_create and vfs_mknod in the current tree, when coming from local accesses the umask is only applied if there is no acl support in the filesystem, from NFS is is never applied - but I presume the NFS client has already applied it. So I have no idea how to make nfs client's behave correctly, they are somewhat out of our control and the nfs spec probably says they are supposed to do this. Steve > > This ACL code had to be added because we don't want > the umask applied to the mode if the parent directory has > default ACLs to apply. (following 1003.1e standard) > So if the mode has the umask applied to it before we get to > play with ACLs then we're stuffed. > We have to stop the mode being changed at that point. > Andreas did the same sort of thing with his EA/ACL patch; > we checked with his code before doing this. > > (So I'm not sure how we are going to keep to the standard > if NFS clients are going to modify the mode with the umask > before we get to see the mode - if that's what's happening) > > --Tim > Steve From owner-linux-xfs@oss.sgi.com Fri Jul 27 07:53:25 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RErPd12849 for linux-xfs-outgoing; Fri, 27 Jul 2001 07:53:25 -0700 Received: from lars.internetia.pl (lars.internetia.pl [195.114.173.133]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RErIV12819 for ; Fri, 27 Jul 2001 07:53:23 -0700 Received: from (ginger.loc.internetia.pl) [10.0.1.72] (helo=ginger.loc.internetia.pl) by lars.internetia.pl with esmtp (Exim 3.12 #1) for linux-xfs@oss.sgi.com id 15Q8zK-0006b9-00; Fri, 27 Jul 2001 16:53:14 +0200 Date: Fri, 27 Jul 2001 16:53:16 +0200 (CEST) From: Piotr Roszatycki X-X-Sender: To: Subject: Disappearing files Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I've installed CVS snapshot (20010725). This version produces strange behaviour. # ls /home/dexter/www index.html # ls -l /home/dexter/www ls: /home/dexter/www/index.html: No such file or directory It seems like the file exists as an entry in directory but can't be stated. After remounting filesystem this file appears. -- Piotr Roszatycki, Netia Telekom S.A. .''`. mailto:Piotr_Roszatycki@netia.net.pl : :' : mailto:dexter@debian.org `. `' `- From owner-linux-xfs@oss.sgi.com Fri Jul 27 11:35:51 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RIZpS17637 for linux-xfs-outgoing; Fri, 27 Jul 2001 11:35:51 -0700 Received: from yog-sothoth.sgi.com (eugate.sgi.com [192.48.160.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RIZmV17618 for ; Fri, 27 Jul 2001 11:35:49 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by yog-sothoth.sgi.com (980305.SGI.8.8.8-aspam-6.2/980304.SGI-aspam-europe) via ESMTP id UAA231250 for ; Fri, 27 Jul 2001 20:35:23 +0200 (CEST) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA2547519 for ; Fri, 27 Jul 2001 13:34:28 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA91404 for ; Fri, 27 Jul 2001 13:34:28 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6RIXwR19889; Fri, 27 Jul 2001 13:33:58 -0500 Message-Id: <200107271833.f6RIXwR19889@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: linux-xfs@oss.sgi.com Subject: New kernel patches on ftp site Date: Fri, 27 Jul 2001 13:33:58 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am about to bump the cvs tree to 2.4.8-pre1, I have updated the 2.4.7 patches to be current with the tree now. These files were uploaded: patches/patch-2.4.7-xfs-2001-07-27.bz2 patches/patch-2.4.7-xfs-cvs-2001-07-27.bz2 Steve From owner-linux-xfs@oss.sgi.com Fri Jul 27 11:47:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RIlKq17874 for linux-xfs-outgoing; Fri, 27 Jul 2001 11:47:20 -0700 Received: from rj.corp.sgi.com (rj.sgi.com [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RIlDV17855 for ; Fri, 27 Jul 2001 11:47:13 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6RIovU25531 for ; Fri, 27 Jul 2001 11:50:57 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id NAA1753943 for ; Fri, 27 Jul 2001 13:45:52 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id NAA42236 for ; Fri, 27 Jul 2001 13:45:52 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6RIjMM19983; Fri, 27 Jul 2001 13:45:22 -0500 Message-Id: <200107271845.f6RIjMM19983@jen.americas.sgi.com> Date: Fri, 27 Jul 2001 13:45:22 -0500 Subject: TAKE - merge up to 2.4.8-pre1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Adds go faster stripes to xfs... There are some kernel changes which do improve performance under load in here. Unless you sit down and benchmark you probably will not notice. Date: Fri Jul 27 11:37:53 PDT 2001 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99696a linux/fs/partitions/ldm.h - 1.1 linux/Documentation/s390/CommonIO - 1.1 linux/include/asm-s390x/pci.h - 1.1 linux/fs/partitions/ldm.c - 1.1 linux/drivers/s390/char/tape3590.h - 1.1 linux/drivers/s390/char/hwc_cpi.c - 1.1 linux/drivers/s390/char/tape3590.c - 1.1 linux/arch/cris/lib/csumcpfruser.S - 1.1 linux/mm/vmscan.c - 1.63 linux/mm/swap.c - 1.9 linux/mm/page_alloc.c - 1.46 linux/mm/memory.c - 1.52 linux/mm/filemap.c - 1.80 linux/kernel/sys.c - 1.23 linux/kernel/softirq.c - 1.12 linux/include/linux/videodev.h - 1.17 linux/include/linux/tty_flip.h - 1.3 linux/include/linux/sysv_fs.h - 1.10 linux/include/linux/swap.h - 1.31 linux/include/linux/sunrpc/types.h - 1.3 linux/include/linux/sunrpc/stats.h - 1.3 linux/include/linux/sunrpc/sched.h - 1.9 linux/include/linux/sunrpc/clnt.h - 1.6 linux/include/linux/rtnetlink.h - 1.9 linux/include/linux/quotaops.h - 1.9 linux/include/linux/poll.h - 1.4 linux/include/linux/parport_pc.h - 1.9 linux/include/linux/parport.h - 1.19 linux/include/linux/pagemap.h - 1.26 linux/include/linux/nubus.h - 1.5 linux/include/linux/nfsd/nfsfh.h - 1.11 linux/include/linux/netlink.h - 1.6 linux/include/linux/loop.h - 1.4 linux/include/linux/locks.h - 1.6 linux/include/linux/lockd/lockd.h - 1.6 linux/include/linux/kernel_stat.h - 1.7 linux/include/linux/kbd_kern.h - 1.6 linux/include/linux/isicom.h - 1.4 linux/include/linux/ipsec.h - 1.3 linux/include/linux/init.h - 1.14 linux/include/linux/inetdevice.h - 1.6 linux/include/linux/fs.h - 1.104 linux/include/linux/byteorder/swabb.h - 1.5 linux/include/linux/byteorder/swab.h - 1.5 linux/include/asm-i386/uaccess.h - 1.11 linux/include/asm-i386/system.h - 1.18 linux/include/asm-i386/string.h - 1.11 linux/include/asm-i386/smplock.h - 1.10 linux/include/asm-i386/smp.h - 1.10 linux/include/asm-i386/signal.h - 1.5 linux/include/asm-i386/siginfo.h - 1.6 linux/include/asm-i386/processor.h - 1.25 linux/include/asm-i386/page.h - 1.16 linux/include/asm-i386/mmu_context.h - 1.13 linux/include/asm-i386/locks.h - 1.3 linux/include/asm-i386/lithium.h - 1.3 linux/include/asm-i386/io.h - 1.15 linux/include/asm-i386/fixmap.h - 1.8 linux/include/asm-i386/desc.h - 1.7 linux/include/asm-i386/cobalt.h - 1.3 linux/include/asm-i386/checksum.h - 1.5 linux/fs/proc/array.c - 1.30 linux/fs/ntfs/inode.c - 1.9 linux/fs/ntfs/dir.c - 1.5 linux/fs/fat/inode.c - 1.24 linux/fs/fat/cvf.c - 1.6 linux/fs/fat/buffer.c - 1.7 linux/fs/autofs/autofs_i.h - 1.8 linux/drivers/usb/usb.c - 1.53 linux/drivers/sound/sb_mixer.c - 1.9 linux/drivers/sound/sb_card.c - 1.26 linux/drivers/scsi/ultrastor.c - 1.9 linux/drivers/scsi/megaraid.h - 1.11 linux/drivers/scsi/megaraid.c - 1.24 linux/drivers/scsi/gdth_proc.c - 1.10 linux/drivers/scsi/g_NCR5380.c - 1.11 linux/drivers/scsi/atp870u.c - 1.14 linux/drivers/pnp/Config.in - 1.6 linux/drivers/char/synclink.c - 1.16 linux/drivers/char/serial.c - 1.43 linux/drivers/char/riscom8.c - 1.10 linux/arch/ppc/kernel/misc.S - 1.30 linux/arch/i386/math-emu/poly.h - 1.5 linux/arch/i386/kernel/process.c - 1.33 linux/arch/i386/kernel/ldt.c - 1.9 linux/arch/alpha/kernel/entry.S - 1.21 linux/Makefile - 1.106 linux/Documentation/Configure.help - 1.90 linux/include/linux/i2o.h - 1.13 linux/drivers/block/ida_ioctl.h - 1.3 linux/drivers/block/ida_cmd.h - 1.3 linux/drivers/block/cpqarray.c - 1.23 linux/include/asm-i386/apic.h - 1.11 linux/include/linux/isapnp.h - 1.10 linux/fs/partitions/check.c - 1.26 linux/fs/partitions/Makefile - 1.6 linux/fs/partitions/Config.in - 1.13 linux/net/irda/ircomm/ircomm_tty_attach.c - 1.8 linux/net/irda/ircomm/ircomm_tty.c - 1.13 linux/include/asm-i386/pci.h - 1.10 linux/drivers/pcmcia/i82365.c - 1.19 linux/drivers/net/wan/sbni.h - 1.4 linux/drivers/net/wan/sbni.c - 1.11 linux/include/asm-i386/pgtable-3level.h - 1.7 linux/include/asm-i386/pgtable-2level.h - 1.7 linux/drivers/net/sk98lin/skge.c - 1.13 linux/include/asm-i386/pgalloc.h - 1.10 linux/include/linux/i2c-dev.h - 1.6 linux/drivers/usb/scanner.c - 1.22 linux/drivers/usb/ov511.c - 1.25 linux/drivers/char/moxa.c - 1.7 linux/include/linux/pm.h - 1.8 linux/drivers/usb/usb-ohci.h - 1.12 linux/drivers/usb/usb-ohci.c - 1.24 linux/drivers/usb/scanner.h - 1.14 linux/drivers/usb/ibmcam.c - 1.14 linux/drivers/sound/via82cxxx_audio.c - 1.17 linux/include/linux/raid/md_k.h - 1.11 linux/include/linux/raid/md_compatible.h - 1.4 linux/drivers/usb/rio500.c - 1.12 linux/include/linux/netfilter_ipv4/listhelp.h - 1.2 linux/include/linux/netfilter_ipv4/ip_tables.h - 1.6 linux/include/linux/netfilter_ipv4/ip_conntrack_tuple.h - 1.4 linux/arch/s390/kernel/process.c - 1.6 linux/include/asm-s390/page.h - 1.5 linux/arch/s390/boot/Makefile - 1.4 linux/arch/s390/Makefile - 1.4 linux/include/asm-s390/uaccess.h - 1.5 linux/arch/s390/config.in - 1.8 linux/arch/s390/defconfig - 1.6 linux/include/asm-s390/irq.h - 1.5 linux/include/asm-s390/lowcore.h - 1.5 linux/include/asm-s390/io.h - 1.3 linux/include/asm-s390/system.h - 1.5 linux/include/asm-s390/hardirq.h - 1.4 linux/include/asm-s390/checksum.h - 1.4 linux/include/asm-s390/chandev.h - 1.4 linux/include/asm-s390/softirq.h - 1.3 linux/include/asm-s390/cache.h - 1.2 linux/include/asm-s390/byteorder.h - 1.2 linux/include/asm-s390/setup.h - 1.4 linux/arch/s390/kernel/entry.S - 1.10 linux/arch/s390/kernel/head.S - 1.5 linux/include/asm-s390/atomic.h - 1.5 linux/drivers/s390/net/iucv.c - 1.4 linux/drivers/s390/net/iucv.h - 1.3 linux/drivers/s390/net/Makefile - 1.4 linux/drivers/s390/misc/chandev.c - 1.5 linux/drivers/s390/char/hwc_rw.c - 1.4 linux/drivers/s390/char/hwc_tty.c - 1.5 linux/drivers/s390/char/hwc_rw.h - 1.3 linux/drivers/s390/char/hwc_con.c - 1.5 linux/drivers/s390/char/Makefile - 1.4 linux/drivers/s390/char/hwc.h - 1.4 linux/drivers/s390/char/con3215.c - 1.7 linux/arch/s390/kernel/irq.c - 1.7 linux/drivers/s390/block/dasd_eckd.c - 1.4 linux/include/asm-s390/s390dyn.h - 1.4 linux/drivers/s390/block/dasd.c - 1.7 linux/drivers/s390/Makefile - 1.4 linux/drivers/s390/Config.in - 1.6 linux/arch/s390/tools/silo/silo.conf - 1.2 linux/arch/s390/tools/silo/cfg.c - 1.2 linux/include/asm-s390/queue.h - 1.4 linux/include/asm-s390/processor.h - 1.6 linux/arch/s390/tools/silo/cfg.h - 1.2 linux/include/asm-s390/pgtable.h - 1.7 linux/include/asm-s390/init.h - 1.2 linux/include/asm-s390/div64.h - 1.3 linux/include/asm-s390/bitops.h - 1.6 linux/include/asm-s390/current.h - 1.3 linux/arch/s390/tools/silo/silo.c - 1.4 linux/arch/s390/kernel/time.c - 1.3 linux/arch/s390/kernel/traps.c - 1.6 linux/arch/s390/kernel/s390_ksyms.c - 1.4 linux/arch/s390/kernel/setup.c - 1.4 linux/arch/s390/kernel/signal.c - 1.6 linux/arch/s390/kernel/smp.c - 1.7 linux/arch/s390/tools/silo/Makefile - 1.3 linux/arch/s390/mm/Makefile - 1.3 linux/arch/s390/tools/dasdfmt/dasdfmt.c - 1.5 linux/arch/s390/mm/fault.c - 1.6 linux/arch/s390/tools/dasdfmt/Makefile - 1.3 linux/arch/s390/tools/dasdfmt/dasdfmt.8 - 1.3 linux/include/linux/netfilter_ipv6/ip6_tables.h - 1.3 linux/arch/i386/kernel/msr.c - 1.8 linux/arch/i386/kernel/cpuid.c - 1.4 linux/fs/pagebuf/page_buf_io.c - 1.92 linux/drivers/usb/serial/empeg.c - 1.9 linux/arch/i386/kernel/dmi_scan.c - 1.5 linux/include/asm-i386/mmu.h - 1.2 linux/include/linux/reiserfs_fs.h - 1.6 linux/include/asm-s390/dasd.h - 1.3 linux/include/asm-s390x/queue.h - 1.3 linux/arch/s390x/tools/dasdfmt/dasdfmt.8 - 1.2 linux/arch/s390x/kernel/traps.c - 1.2 linux/arch/s390x/kernel/time.c - 1.2 linux/arch/s390x/kernel/smp.c - 1.4 linux/include/asm-s390x/processor.h - 1.2 linux/include/asm-s390x/pgtable.h - 1.3 linux/include/asm-s390x/pgalloc.h - 1.3 linux/arch/s390x/kernel/signal.c - 1.3 linux/arch/s390x/kernel/setup.c - 1.3 linux/include/asm-s390x/page.h - 1.3 linux/Documentation/s390/TAPE - 1.2 linux/Documentation/s390/chandev.8 - 1.3 linux/include/asm-s390x/lowcore.h - 1.3 linux/include/asm-s390x/irq.h - 1.4 linux/include/asm-s390x/io.h - 1.2 linux/include/asm-s390x/init.h - 1.2 linux/include/asm-s390x/idals.h - 1.2 linux/include/asm-s390x/hardirq.h - 1.2 linux/include/asm-s390x/debug.h - 1.3 linux/arch/s390x/kernel/s390_ksyms.c - 1.3 linux/arch/s390x/kernel/s390_ext.c - 1.3 linux/include/asm-s390x/dasd.h - 1.4 linux/include/asm-s390x/current.h - 1.2 linux/include/asm-s390x/checksum.h - 1.2 linux/include/asm-s390x/chandev.h - 1.3 linux/include/asm-s390x/cache.h - 1.2 linux/include/asm-s390x/s390dyn.h - 1.3 linux/arch/s390x/kernel/process.c - 1.3 linux/arch/s390x/kernel/linux32.c - 1.5 linux/arch/s390x/kernel/irq.c - 1.4 linux/arch/s390x/kernel/head.S - 1.4 linux/include/asm-s390x/setup.h - 1.3 linux/include/asm-s390x/signal.h - 1.3 linux/drivers/s390/s390mach.c - 1.3 linux/arch/cris/Makefile - 1.6 linux/arch/cris/boot/compressed/decompress.ld - 1.4 linux/arch/cris/config.in - 1.5 linux/arch/cris/cris.ld - 1.5 linux/arch/cris/kernel/Makefile - 1.5 linux/arch/cris/kernel/entry.S - 1.7 linux/arch/cris/kernel/head.S - 1.6 linux/arch/cris/kernel/irq.c - 1.6 linux/arch/cris/kernel/process.c - 1.6 linux/arch/cris/kernel/ptrace.c - 1.5 linux/arch/cris/kernel/setup.c - 1.6 linux/arch/cris/kernel/sys_cris.c - 1.6 linux/arch/cris/kernel/time.c - 1.4 linux/arch/cris/kernel/traps.c - 1.5 linux/arch/cris/lib/Makefile - 1.2 linux/arch/cris/lib/checksumcopy.S - 1.5 linux/arch/cris/mm/fault.c - 1.6 linux/arch/cris/mm/init.c - 1.5 linux/arch/cris/mm/tlb.c - 1.4 linux/drivers/s390/s390io.c - 1.4 linux/drivers/s390/s390dyn.c - 1.3 linux/drivers/s390/net/netiucv.c - 1.4 linux/drivers/s390/net/fsm.h - 1.2 linux/drivers/s390/net/fsm.c - 1.2 linux/drivers/s390/net/ctcmain.c - 1.3 linux/drivers/s390/idals.c - 1.3 linux/drivers/s390/char/tapedefs.h - 1.3 linux/drivers/s390/char/tapechar.h - 1.3 linux/drivers/s390/char/tapechar.c - 1.3 linux/arch/s390x/kernel/entry.S - 1.5 linux/drivers/s390/char/tapeblock.h - 1.3 linux/drivers/s390/char/tapeblock.c - 1.3 linux/drivers/s390/char/tape34xx.h - 1.3 linux/drivers/s390/char/tape34xx.c - 1.4 linux/drivers/s390/char/tape3490.h - 1.3 linux/drivers/s390/char/tape3490.c - 1.3 linux/drivers/s390/char/tape3480.h - 1.3 linux/drivers/s390/char/tape3480.c - 1.3 linux/drivers/s390/char/tape.h - 1.3 linux/drivers/s390/char/tape.c - 1.3 linux/arch/s390x/kernel/debug.c - 1.3 linux/arch/s390x/defconfig - 1.4 linux/arch/s390x/config.in - 1.3 linux/arch/s390x/tools/dasdfmt/Makefile - 1.3 linux/arch/s390x/mm/fault.c - 1.4 linux/include/asm-s390x/softirq.h - 1.2 linux/drivers/s390/ccwcache.c - 1.3 linux/drivers/s390/block/xpram.c - 1.3 linux/include/asm-s390x/system.h - 1.3 linux/include/asm-s390x/termios.h - 1.4 linux/drivers/s390/block/dasd_fba.c - 1.3 linux/drivers/s390/block/dasd_diag.c - 1.3 linux/include/asm-s390x/uaccess.h - 1.3 linux/include/asm-s390x/unistd.h - 1.3 linux/include/asm-cris/softirq.h - 1.2 linux/include/asm-cris/socket.h - 1.4 linux/include/asm-s390x/atomic.h - 1.4 linux/include/asm-s390/idals.h - 1.2 linux/include/asm-s390/debug.h - 1.3 linux/include/asm-cris/atomic.h - 1.2 linux/include/asm-cris/axisflashmap.h - 1.4 linux/include/asm-cris/checksum.h - 1.2 linux/include/asm-cris/delay.h - 1.5 linux/arch/s390/kernel/debug.c - 1.3 linux/include/asm-cris/ptrace.h - 1.5 linux/include/asm-cris/processor.h - 1.4 linux/include/asm-cris/hardirq.h - 1.2 linux/arch/s390/kernel/s390_ext.c - 1.3 linux/include/asm-cris/irq.h - 1.6 linux/include/asm-cris/io.h - 1.5 linux/arch/s390x/tools/silo/silo.conf - 1.2 linux/arch/s390x/tools/silo/Makefile - 1.3 linux/arch/s390x/tools/silo/silo.c - 1.3 linux/arch/s390x/tools/silo/cfg.h - 1.2 linux/arch/s390x/tools/silo/cfg.c - 1.2 linux/arch/s390x/tools/dasdfmt/dasdfmt.c - 1.4 linux/arch/s390x/Makefile - 1.3 linux/include/linux/hdlc.h - 1.2 linux/drivers/s390/char/ctrlchar.c - 1.2 linux/drivers/s390/char/ctrlchar.h - 1.2 linux/drivers/s390/char/tuball.c - 1.2 linux/drivers/s390/char/tubfs.c - 1.2 linux/drivers/s390/char/tubio.h - 1.2 linux/drivers/s390/char/tubtty.c - 1.2 linux/drivers/s390/char/tubttyscl.c - 1.2 linux/drivers/s390/char/tubttysiz.c - 1.2 linux/drivers/s390/net/ctctty.c - 1.2 linux/drivers/s390/net/ctctty.h - 1.2 linux/Documentation/s390/Debugging390.txt - 1.2 linux/arch/cris/drivers/eeprom.c - 1.3 linux/arch/cris/drivers/parport.c - 1.4 linux/drivers/usb/se401.c - 1.3 linux/drivers/net/sk98lin/skproc.c - 1.3 linux/arch/cris/kernel/entryoffsets.c - 1.2 linux/arch/cris/drivers/lpslave/e100lpslave.S - 1.3 linux/arch/cris/drivers/lpslave/e100lpslavenet.c - 1.3 linux/drivers/media/video/zr36067.c - 1.2 From owner-linux-xfs@oss.sgi.com Fri Jul 27 14:45:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RLjlN02092 for linux-xfs-outgoing; Fri, 27 Jul 2001 14:45:47 -0700 Received: from codon.com (stampingcentral.com [64.78.130.125]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RLjjV02061 for ; Fri, 27 Jul 2001 14:45:45 -0700 Received: (qmail 29671 invoked by uid 516); 27 Jul 2001 21:53:23 -0000 Received: from nw@codon.com by helix with qmail-scanner-0.96 (. Clean. Processed in 0.044799 secs); 27 Jul 2001 21:53:23 -0000 Received: from weasel.local.iboats.com (HELO weasel) (64.78.130.80) by codon.com with SMTP; 27 Jul 2001 21:53:22 -0000 Message-ID: <007101c116e5$125d22a0$50824e40@iboats.com> From: "Steve Wolfe" To: References: <200107271159.NAA03279@smtp-1.worldonline.cz> Subject: Re: XFX1.0.1, partition "/" and Update disk 20/07/2001 Date: Fri, 27 Jul 2001 15:42:35 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-2" Content-Transfer-Encoding: 7bit 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 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I want to install system and then make kickstart. (and Iam not familiar > with plain fdisk). fdisk is your friend. You use Unix for powerful tools that give you control, not for wimpy tools that take it away, don't you? ; ) steve From owner-linux-xfs@oss.sgi.com Fri Jul 27 15:44:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6RMiir09324 for linux-xfs-outgoing; Fri, 27 Jul 2001 15:44:44 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6RMigV09301 for ; Fri, 27 Jul 2001 15:44:42 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id PAA01800 for ; Fri, 27 Jul 2001 15:44:20 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id RAA2540587 for ; Fri, 27 Jul 2001 17:43:25 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id RAA23103 for ; Fri, 27 Jul 2001 17:43:25 -0500 (CDT) From: Steve Lord Received: by jen.americas.sgi.com (8.11.2/SGI-client-1.7) id f6RMgs825920; Fri, 27 Jul 2001 17:42:54 -0500 Message-Id: <200107272242.f6RMgs825920@jen.americas.sgi.com> Date: Fri, 27 Jul 2001 17:42:54 -0500 Subject: TAKE - turn raid I/O optimization back on Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a modified version of the code which was breaking XFS journal on raid5. By reducing the number of cases where we use a single buffer head on a page to the cases where the page is being completely written and is aligned on a 4K disk boundary, we are avoiding the problem. Log recovery on raid5 does work with this combination. Most filesystem I/O on raid5 will be able to use the speedup. Date: Fri Jul 27 15:39:54 PDT 2001 Workarea: 128.162.187.49:/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:99721a linux/fs/pagebuf/page_buf.c - 1.96 - Turn back on the md optimization for doing larger writes, only allow completely aligned pages. From owner-linux-xfs@oss.sgi.com Fri Jul 27 18:23:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6S1Ndk28132 for linux-xfs-outgoing; Fri, 27 Jul 2001 18:23:39 -0700 Received: from neutral.verbum.org (postfix@dhcp233054.columbus.rr.com [204.210.233.54]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6S1NaV28112 for ; Fri, 27 Jul 2001 18:23:37 -0700 Received: from space-ghost.verbum.org (space-ghost.verbum.org [192.168.5.90]) by neutral.verbum.org (Postfix (Debian/GNU)) with ESMTP id 45688F5A7 for ; Fri, 27 Jul 2001 21:21:55 -0400 (EDT) Received: by space-ghost.verbum.org (Postfix (Debian/GNU), from userid 1000) id 6225F620C0B; Fri, 27 Jul 2001 21:22:12 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: bad clientid? X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Fri, 27 Jul 2001 21:22:12 -0400 Message-ID: <87pual7sqj.church.of.emacs@space-ghost.verbum.org> Lines: 25 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I'm building an ia32 server which will be running RAID 5 over three 40 GB disks. We're using 4 RAID partitions (/var, /home, /usr, and /), all using XFS. We booted using an NFS root, initialized the RAID devices, made an XFS filesystem on all of them, mounted them, then rsynced over our NFS root image to the target filesystems. This all worked fine. However, after rebooting, when we tried to mount one of the arrays (which was /var), we got: Jul 28 01:03:27 debian kernel: Start mounting filesystem: md(9,1) Jul 28 01:03:31 debian kernel: Starting XFS recovery on filesystem: md(9,1) (dev: 9/1) Jul 28 01:03:31 debian kernel: XFS: xlog_recover_process_data: bad clientid Jul 28 01:03:31 debian kernel: XFS: log mount/recovery failed Jul 28 01:03:31 debian kernel: XFS: log mount failed The other partitions mounted correctly; I am confused as to why just one of the partitions would fail. We ran xfs_repair /dev/md2, and it didn't report any errors. After that, mounting the partition worked just fine: Jul 28 01:03:49 debian kernel: Start mounting filesystem: md(9,1) Jul 28 01:04:04 debian kernel: Ending clean XFS mount for filesystem: md(9,1) Any ideas? From owner-linux-xfs@oss.sgi.com Sat Jul 28 04:58:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6SBwwO21163 for linux-xfs-outgoing; Sat, 28 Jul 2001 04:58:58 -0700 Received: from legba.tvnet.hu (legba.tvnet.hu [195.38.96.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6SBwuV21141 for ; Sat, 28 Jul 2001 04:58:56 -0700 Received: from dumballah.tvnet.hu (zeus.city.tvnet.hu [195.38.100.182]) by legba.tvnet.hu (8.9.3+Sun/8.9.3) with ESMTP id NAA00187 for ; Sat, 28 Jul 2001 13:58:54 +0200 (MEST) Message-ID: <3B62A96E.8030207@dumballah.tvnet.hu> Date: Sat, 28 Jul 2001 14:00:46 +0200 From: Sipos Ferenc User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010701 X-Accept-Language: en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: 2.4.8-pre1 compile problems Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi! Does anybody have the same compile problems? During module compilation, the process stops by parport_pc, with dual definition or similar message, I know it's not xfs related. Paco From owner-linux-xfs@oss.sgi.com Sat Jul 28 05:43:47 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6SChlI26028 for linux-xfs-outgoing; Sat, 28 Jul 2001 05:43:47 -0700 Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6SChhV25995 for ; Sat, 28 Jul 2001 05:43:43 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id OAA19494; Sat, 28 Jul 2001 14:43:39 +0200 (CEST) Message-Id: <4.3.2.7.2.20010728144227.02c96b20@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 28 Jul 2001 14:43:24 +0200 To: Sipos Ferenc , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: 2.4.8-pre1 compile problems In-Reply-To: <3B62A96E.8030207@dumballah.tvnet.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 14:00 28-7-2001 +0200, Sipos Ferenc wrote: >Hi! > >Does anybody have the same compile problems? During module compilation, >the process stops by parport_pc, with dual definition or similar message, >I know it's not xfs related. Remove the definitions from the c source code. Patch below, I hope it is still ok after copy and paste. Cheers Seth diff -u --recursive --new-file v2.4.7/linux/drivers/parport/parport_pc.c linux/drivers/parport/parport_pc.c --- v2.4.7/linux/drivers/parport/parport_pc.c Wed Jul 11 01:07:46 2001 +++ linux/drivers/parport/parport_pc.c Fri Jul 27 09:24:50 2001 @@ -253,94 +253,6 @@ parport_generic_irq(irq, (struct parport *) dev_id, regs); } -void parport_pc_write_data(struct parport *p, unsigned char d) -{ - outb (d, DATA (p)); -} - -unsigned char parport_pc_read_data(struct parport *p) -{ - return inb (DATA (p)); -} - -void parport_pc_write_control(struct parport *p, unsigned char d) -{ - const unsigned char wm = (PARPORT_CONTROL_STROBE | - PARPORT_CONTROL_AUTOFD | - PARPORT_CONTROL_INIT | - PARPORT_CONTROL_SELECT); - - /* Take this out when drivers have adapted to the newer interface. */ - if (d & 0x20) { - printk (KERN_DEBUG "%s (%s): use data_reverse for this!\n", - p->name, p->cad->name); - parport_pc_data_reverse (p); - } - - __parport_pc_frob_control (p, wm, d & wm); -} - -unsigned char parport_pc_read_control(struct parport *p) -{ - const unsigned char wm = (PARPORT_CONTROL_STROBE | - PARPORT_CONTROL_AUTOFD | - PARPORT_CONTROL_INIT | - PARPORT_CONTROL_SELECT); - const struct parport_pc_private *priv = p->physport->private_data; - return priv->ctr & wm; /* Use soft copy */ -} - -unsigned char parport_pc_frob_control (struct parport *p, unsigned char mask, - unsigned char val) -{ - const unsigned char wm = (PARPORT_CONTROL_STROBE | - PARPORT_CONTROL_AUTOFD | - PARPORT_CONTROL_INIT | - PARPORT_CONTROL_SELECT); - - /* Take this out when drivers have adapted to the newer interface. */ - if (mask & 0x20) { - printk (KERN_DEBUG "%s (%s): use data_%s for this!\n", - p->name, p->cad->name, - (val & 0x20) ? "reverse" : "forward"); - if (val & 0x20) - parport_pc_data_reverse (p); - else - parport_pc_data_forward (p); - } - - /* Restrict mask and val to control lines. */ - mask &= wm; - val &= wm; - - return __parport_pc_frob_control (p, mask, val); -} - -unsigned char parport_pc_read_status(struct parport *p) -{ - return inb (STATUS (p)); -} - -void parport_pc_disable_irq(struct parport *p) -{ - __parport_pc_frob_control (p, 0x10, 0); -} - -void parport_pc_enable_irq(struct parport *p) -{ - __parport_pc_frob_control (p, 0x10, 0x10); -} - -void parport_pc_data_forward (struct parport *p) -{ - __parport_pc_frob_control (p, 0x20, 0); -} - -void parport_pc_data_reverse (struct parport *p) -{ - __parport_pc_frob_control (p, 0x20, 0x20); -} - void parport_pc_init_state(struct pardevice *dev, struct parport_state *s) { s->u.pc.ctr = 0xc | (dev->irq_func ? 0x10 : 0x0); -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sat Jul 28 18:28:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6T1S8u09052 for linux-xfs-outgoing; Sat, 28 Jul 2001 18:28:08 -0700 Received: from mailman.mnd.com ([208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6T1S4V09018 for ; Sat, 28 Jul 2001 18:28:04 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id UAA30342 for ; Sat, 28 Jul 2001 20:27:35 -0500 Date: Sat, 28 Jul 2001 20:27:00 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: linux-xfs@oss.sgi.com Subject: Houston Summer -> duplicate inode range Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Today, I had a disk overheat, which led to severe corruption on an XFS volume. At the end of quite a lot of output from xfs_repair, imap claims in-use inode 201384383 is free, correcting imap avl_insert: Warning! duplicate range [0xe1e0,0xe220) fatal error -- xfs_repair: duplicate inode range and an attempt to mount it read-only gets me a XFS: failed to read root inode On the first pass thru, it had to hunt down a backup superblock; some severely snipped output from a later run of xfs_repair is to be found at the end of this message. I do have some things I'd like to recover from this volume, so if anyone can offer a hint, I'd be grateful. By the way, this is on a 100-GB IDE disk at home, not on either of our 1.2TB raids, so nobody's having a cow ;) ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ ----output from xfs_repair---------------------------- Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 inconsistent with calculated value 549755813896 resetting superblock root inode pointer to 384399556312 sb realtime bitmap inode 18446744073709551615 inconsistent with calculated value 554050781185 resetting superblock realtime bitmap ino pointer to 405874392792 sb realtime summary inode 18446744073709551615 inconsistent with calculated value 558345748481 resetting superblock realtime summary ino pointer to 410169360088 Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... block (0,247146) multiply claimed by bno space tree, state - 1 block (0,247147) multiply claimed by bno space tree, state - 1 block (0,247148) multiply claimed by bno space tree, state - 1 block (0,247149) multiply claimed by bno space tree, state - 1 block (0,247150) multiply claimed by bno space tree, state - 1 block (0,247151) multiply claimed by bno space tree, state - 1 block (0,247152) multiply claimed by bno space tree, state - 1 block (0,247153) multiply claimed by bno space tree, state - 1 block (0,247154) multiply claimed by bno space tree, state - 1 block (0,247155) multiply claimed by bno space tree, state - 1 block (0,247156) multiply claimed by bno space tree, state - 1 block (0,247157) multiply claimed by bno space tree, state - 1 block (0,247158) multiply claimed by bno space tree, state - 1 block (0,243006) already used, state 2 block (0,243007) already used, state 2 block (0,243008) already used, state 2 block (0,243009) already used, state 2 block (0,243010) already used, state 2 block (0,243011) already used, state 2 block (0,243012) already used, state 2 block (0,243013) already used, state 2 block (0,243014) already used, state 2 bad agbno 0 for inobt root, agno 0 bad agbno 1380929631 for inobt root, agno 1 bad magic # 0x4580fc01 in btcnt block 2/6 expected level 0 got 30001 in btcnt block 2/6 bad agbno 1380929631 for inobt root, agno 2 bad agbno 1157650541 for inobt root, agno 3 bad agbno 1953723489 in agfl, agno 4 bad agbno 1946157056 in agfl, agno 4 bad agbno 71365155 in agfl, agno 4 bad agbno 91054441 in agfl, agno 4 bad magic # 0 in btcnt block 4/257449 bad agbno 0 for inobt root, agno 4 bad magic # 0xd8eb118b in btbno block 5/4 expected level 0 got 17176 in btbno block 5/4 bad magic # 0x562a761a in inobt block 5/268470 expected level 8 got 34767 in inobt block 5/268470 bad magic # 0x4d616769 in inobt block 5/415589 bad magic # 0x8d in btbno block 6/327375 expected level 0 got 28314 in btbno block 6/327375 bad agbno 0 for inobt root, agno 6 bad agbno 0 for inobt root, agno 7 bad magic # 0xd5ca7976 in inobt block 8/269656 expected level 12 got 62387 in inobt block 8/269656 bad agbno 538976288 for inobt root, agno 9 bad magic # 0 in btbno block 10/160520 block (10,6528) multiply claimed by bno space tree, state - 1 block (10,47377) multiply claimed by bno space tree, state - 1 bad magic # 0x2afef in btcnt block 10/160519 bad agbno 0 for inobt root, agno 10 bad agbno 1667956851 for inobt root, agno 11 bad agbno 100663529 for inobt root, agno 12 bad agbno 1583203209 for inobt root, agno 13 bad magic # 0x8a in btcnt block 14/6 expected level 0 got 4329 in btcnt block 14/6 bad magic # 0x8a in btcnt block 14/123180 block (14,138) already used, state 2 block (20,115335) multiply claimed by bno space tree, state - 1 bad agbno 1718185061 for inobt root, agno 20 bad agbno 1718185061 for inobt root, agno 21 bad agbno 4280619158 for inobt root, agno 22 bad agbno 4280619158 for inobt root, agno 23 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims in-use inode 131 is free, correcting imap imap claims in-use inode 191 is free, correcting imap - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 bad magic number 0x0 on inode 288657248 bad version number 0x0 on inode 288657248 bad inode format in inode 288657248 bad magic number 0x6900 on inode 288657375 bad version number 0x0 on inode 288657375 bad (negative) size -2624707291143733120 on inode 288657375 imap claims a free inode 288657504 is in use, correcting imap and clearing inode imap claims a free inode 288657535 is in use, correcting imap and clearing inode data fork in ino 288657536 claims free block 18071151 data fork in ino 288657544 claims free block 18071219 imap claims a free inode 288657552 is in use, correcting imap and clearing inode imap claims a free inode 288657736 is in use, correcting imap and clearing inode - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - process newly discovered inodes... imap claims in-use inode 255361 is free, correcting imap imap claims in-use inode 34231592 is free, correcting imap data fork in ino 34231593 claims free block 2158083 imap claims in-use inode 201384383 is free, correcting imap avl_insert: Warning! duplicate range [0xe1e0,0xe220) fatal error -- xfs_repair: duplicate inode range From owner-linux-xfs@oss.sgi.com Sat Jul 28 20:16:30 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6T3GU219084 for linux-xfs-outgoing; Sat, 28 Jul 2001 20:16:30 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6T3GSV19055 for ; Sat, 28 Jul 2001 20:16:28 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id DFC511AB10 for ; Sat, 28 Jul 2001 23:16:26 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 973A3723; Sat, 28 Jul 2001 23:16:25 -0400 (EDT) Date: Sat, 28 Jul 2001 23:16:25 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Everyone's favorite offtopic topic Message-ID: <20010728231625.C19907@dkp.com> 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.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, all. A number of times, questions have popped up on this list about building really large arrays of IDE disks. Does anybody know if there's a list dedicated to that? If not, does anybody have suggestions as to the best way to get something like that set up? I ask because I haven't really found an appropriate forum for it; the range of issues that come up (filesystems, hardware, RAID) cut across so many boundaries that it's difficult to keep from going wildly offtopic no matter which list(s) one is on. And most of the people building these arrays are venturing into the unknown; it'd be handy to have a place to swap experience about hardware weirdnesses and filesystem quirks and performance notes, to inform others about successful configurations and failures. Anybody else think there might be enough interest to make something like this a go? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Sun Jul 29 03:24:01 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TAO1t23073 for linux-xfs-outgoing; Sun, 29 Jul 2001 03:24:01 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TANvV23047 for ; Sun, 29 Jul 2001 03:23:58 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id MAA05078; Sun, 29 Jul 2001 12:23:52 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 12:23:36 +0200 To: Andrew Klaassen , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Everyone's favorite offtopic topic In-Reply-To: <20010728231625.C19907@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 23:16 28-7-2001 -0400, Andrew Klaassen wrote: >Hi, all. > >A number of times, questions have popped up on this list about >building really large arrays of IDE disks. Does anybody know if >there's a list dedicated to that? If not, does anybody have >suggestions as to the best way to get something like that set >up? > >I ask because I haven't really found an appropriate forum for >it; the range of issues that come up (filesystems, hardware, >RAID) cut across so many boundaries that it's difficult to keep >from going wildly offtopic no matter which list(s) one is on. >And most of the people building these arrays are venturing into >the unknown; it'd be handy to have a place to swap experience >about hardware weirdnesses and filesystem quirks and performance >notes, to inform others about successful configurations and >failures. > >Anybody else think there might be enough interest to make >something like this a go? There recently was a message about building a $5000 dollar IDE raid on slashdot IIRC. Don't know the URL anymore. Basic configuration was purchasing a large case which can house 16 disks Purchase 16 100GB Maxtor IDE disks (the 540DX uses less power) Purchase 2 3ware Escalade 6800 controllers A PC for booting the machine. That's about it. My home PC can house 16 3.5"x1.0" disks but it's not really a standard atx enclosure. http://www.yeongyang.com/products/yy0320-0330.htm But you will rather soon run into powersupply problems if you use more power hungry IDE disk. If you think about using 7200RPM disks you better start looking for multiple 400W powersupply's. IDE disks tend to have the problem to all start to spin up at boot. Scsi does this when asked to :-) Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 03:35:16 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TAZG524928 for linux-xfs-outgoing; Sun, 29 Jul 2001 03:35:16 -0700 Received: from darwin.ntu.edu.au (darwin.ntu.edu.au [138.80.128.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TAZBV24894 for ; Sun, 29 Jul 2001 03:35:11 -0700 Received: (qmail 20494 invoked by uid 1128); 29 Jul 2001 10:35:03 -0000 Date: Sun, 29 Jul 2001 20:05:03 +0930 From: Anthony W Hornby To: linux-xfs@oss.sgi.com Cc: anthony.hornby@ntu.edu.au Subject: Where is ACL information stored with XFS? Message-ID: <20010729200503.A20045@ntu.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3us Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi, I am considering using XFS as the base filesystem for our SAN as it supports ACL's and will integrate well with samba to provide fine grained control over file access for users. What I need to know is where is the ACL information saved? If I back up my filesystem onto tape using regular backup software (veritas,tivoli, arkeia etc etc) will the ACL information be restored when i restore the files from tape? If not what's involved in preserving /restoring it? All information greatly appreciated. Please send replies to me directly anthony.hornby@ntu.edu.au and I'll summarise to the list. Regards Anthony. -- ************************************** * Mr Anthony Hornby * * Systems Engineer * * Information Technology Services * * Northern Territory University * * * * anthony.hornby@ntu.edu.au * * +61 8 8946 6167 * * * * "To understand recursion, * * we must first understand * * recursion" * ************************************** From owner-linux-xfs@oss.sgi.com Sun Jul 29 03:46:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TAkMa26748 for linux-xfs-outgoing; Sun, 29 Jul 2001 03:46:22 -0700 Received: from finch-post-12.mail.demon.net (finch-post-12.mail.demon.net [194.217.242.41]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TAkKV26728 for ; Sun, 29 Jul 2001 03:46:21 -0700 Received: from sweeney.demon.co.uk ([158.152.71.87] helo=pereskia.sweeney.demon.co.uk) by finch-post-12.mail.demon.net with esmtp (Exim 2.12 #1) id 15Qo5T-000Mjq-0C for linux-xfs@oss.sgi.com; Sun, 29 Jul 2001 10:46:19 +0000 Received: from rebutia.sweeney.demon.co.uk (rebutia.sweeney.demon.co.uk [10.0.0.3]) by pereskia.sweeney.demon.co.uk (Postfix) with ESMTP id B515D27EF for ; Sun, 29 Jul 2001 11:45:56 +0100 (BST) Received: by rebutia.sweeney.demon.co.uk (Postfix, from userid 1001) id D85CE125E6; Sun, 29 Jul 2001 11:45:54 +0100 (BST) Date: Sun, 29 Jul 2001 11:45:53 +0100 (BST) From: Keith Matthews Subject: Re[2]: Everyone's favorite offtopic topic To: linux-xfs@oss.sgi.com In-Reply-To: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> References: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> X-Mailer: Mahogany, 0.60 'Redmond', compiled for Linux 2.2.13 i686 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Disposition: INLINE Message-Id: <20010729104554.D85CE125E6@rebutia.sweeney.demon.co.uk> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by oss.sgi.com id f6TAkLV26729 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 29 Jul 2001 12:23:36 +0200 Seth Mos > wrote: > If you think about using 7200RPM disks you better start looking for > multiple 400W powersupply's. IDE disks tend to have the problem to all > start to spin up at boot. Scsi does this when asked to :-) Only if specifcally configured to do so I believe. Mine have always come to auto spin-up on power-up and needed reconfiguring (IBM Ultrastar etc). -- Keith Matthews Spam trap - my real account at this node is keith_m Frequentous Consultants - Linux Services, Oracle development & database administration From owner-linux-xfs@oss.sgi.com Sun Jul 29 04:07:22 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TB7MO30238 for linux-xfs-outgoing; Sun, 29 Jul 2001 04:07:22 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TB7IV30216 for ; Sun, 29 Jul 2001 04:07:18 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA01733; Sun, 29 Jul 2001 13:07:07 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729125821.02ca37e0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 13:06:51 +0200 To: Anthony W Hornby , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Where is ACL information stored with XFS? Cc: anthony.hornby@ntu.edu.au In-Reply-To: <20010729200503.A20045@ntu.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 20:05 29-7-2001 +0930, Anthony W Hornby wrote: >Hi, >I am considering using XFS as the base filesystem for our SAN as >it supports ACL's and will integrate well with samba to provide >fine grained control over file access for users. >What I need to know is where is the ACL information saved? Extended attributes. >If I back up my filesystem onto tape using regular backup >software (veritas,tivoli, arkeia etc etc) >will the ACL information be restored when i restore the files from tape? probably not. Amanda can be made to work with xfsdump. Some of them are actually working on supporting it natively. >If not what's involved in preserving /restoring it? use xfsdump/xfsrestore. >All information greatly appreciated. >Please send replies to me directly anthony.hornby@ntu.edu.au and I'll >summarise to the list. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 04:11:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TBBDk30979 for linux-xfs-outgoing; Sun, 29 Jul 2001 04:11:13 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TBBBV30954 for ; Sun, 29 Jul 2001 04:11:11 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id NAA02405; Sun, 29 Jul 2001 13:11:06 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729130728.02a69fe8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 13:10:51 +0200 To: Keith Matthews , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re[2]: Everyone's favorite offtopic topic In-Reply-To: <20010729104554.D85CE125E6@rebutia.sweeney.demon.co.uk> References: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:45 29-7-2001 +0100, Keith Matthews wrote: >On Sun, 29 Jul 2001 12:23:36 +0200 Seth Mos > >wrote: > > If you think about using 7200RPM disks you better start looking for > > multiple 400W powersupply's. IDE disks tend to have the problem to all > > start to spin up at boot. Scsi does this when asked to :-) > >Only if specifcally configured to do so I believe. Mine have always >come to auto spin-up on power-up and needed reconfiguring (IBM >Ultrastar etc). Depends on disk manufacturer. Most are default to spin on boot. In raid arrays this is often disabled. I believe IDE disks don't support delayed start. So it's with scsi you can and with IDE you can't. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 04:32:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TBWcW06615 for linux-xfs-outgoing; Sun, 29 Jul 2001 04:32:38 -0700 Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TBWZV06596 for ; Sun, 29 Jul 2001 04:32:35 -0700 Received: from arts.usyd.edu.au (IDENT:matthew@holly.aitch.ucc.usyd.edu.au [129.78.226.234]) by plato.arts.usyd.edu.au (8.9.3/8.9.3) with ESMTP id VAA11231 for ; Sun, 29 Jul 2001 21:32:30 +1000 (EST) Message-ID: <3B63F443.E70EFC7F@arts.usyd.edu.au> Date: Sun, 29 Jul 2001 21:32:19 +1000 From: Matthew Geier Organization: Arts IT Unit, Sydney University X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i686) X-Accept-Language: en, pdf MIME-Version: 1.0 CC: linux-xfs@oss.sgi.com Subject: Re: Where is ACL information stored with XFS? References: <4.3.2.7.2.20010729125821.02ca37e0@pop.xs4all.nl> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms5B5693AD55DDC164C045E308" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms5B5693AD55DDC164C045E308 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Seth Mos wrote: > >If I back up my filesystem onto tape using regular backup > >software (veritas,tivoli, arkeia etc etc) > >will the ACL information be restored when i restore the files from tape? > > probably not. Amanda can be made to work with xfsdump. > Some of them are actually working on supporting it natively. > We use Legato networker. I assume Networker 6 will not backup XFS extended attributes as until now Linux hasn't really had them. However IRIX is a supported OS for Networker. What I need is for some one at SGI to lean on networker to port the XFS bits of the IRIX client to Linux, I can then get the update through our usual software maintence channels... I assume under Irix , networker backs up the EAs. --------------ms5B5693AD55DDC164C045E308 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIH0AYJKoZIhvcNAQcCoIIHwTCCB70CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BbswggKKMIIB86ADAgECAgMFMYswDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTA3MDkxOTEyNThaFw0wMjA3MDkxOTEyNTha MEoxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJzAlBgkqhkiG9w0BCQEWGG1h dHRoZXdAYXJ0cy51c3lkLmVkdS5hdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1H+o MQ4xn5lDS/7p9rYboPW7grw13lXOj7Xisip37QttkX7Ga3ITBXnsAKnuFK3Z7GtILACBXil1 BngLBOd0AlW9zqQBXEOP9aODNJzBsTb3+tOHwQo6shcORKQArKEinG00SuwBdzxALU3KWT6E yIUSvoz7q0PN4C8qUF3t00sCAwEAAaM1MDMwIwYDVR0RBBwwGoEYbWF0dGhld0BhcnRzLnVz eWQuZWR1LmF1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAiJu7SNBXsW7I+ZH9 e2+0M47BmR3DxV31VbW9mKcwuamusWSJJEy5MAKZc8b0snRX/XDkCpM+av3VxDJX8T3rxOE0 siyCC6Tclu6wjwjw0goXK4N6Xhsz+qwIfdoclNZkqK5yInEZtc5ijKr0IPRgch79f35WP82C SNHVYApmjzgwggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcN MDIwODI5MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmlj YXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMw MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNE KYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu 2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQAB o04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAcxtvJmWL/xU0 S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONntUPQ6bDSSrOaSnG7BIwHC CafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2lhglTWr0ncXDkS+p lrgFPFL83eliA0gxggHdMIIB2QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNV BAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS U0EgMjAwMC44LjMwAgMFMYswCQYFKw4DAhoFAKCBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0wMTA3MjkxMTMyMjBaMCMGCSqGSIb3DQEJBDEWBBRALsBM gn628/o4Xu0/YvLekHKYDzA6BgkqhkiG9w0BCQ8xLTArMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgE77oPjkbg6hv9wBA5AU fDK8pji5M5+Xz4WT3FXIlPlHbUgvMo71WxpqTTIOA45x7WT0mbQAFpfuT+QXf8Gq1u2G08yu ykxDEBFTrcGNq4m6qsfNJTCwDT7qtcUNUtbxXdEulQFpOPTgcMyx7w+3cqWEiPQAE4s82SKP VkErOanB --------------ms5B5693AD55DDC164C045E308-- From owner-linux-xfs@oss.sgi.com Sun Jul 29 04:44:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TBiAZ08261 for linux-xfs-outgoing; Sun, 29 Jul 2001 04:44:10 -0700 Received: from gusi.leathercollection.ph (postfix@gusi.leathercollection.ph [202.163.192.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TBi8V08236 for ; Sun, 29 Jul 2001 04:44:08 -0700 Received: from gusi.leathercollection.local (gusi.leathercollection.local [192.168.0.1]) by gusi.leathercollection.ph (Postfix) with ESMTP id 27DCEC08298 for ; Sun, 29 Jul 2001 19:44:06 +0800 (PHT) Date: Sun, 29 Jul 2001 19:44:06 +0800 (PHT) From: Federico Sevilla III X-X-Sender: To: Linux XFS Mailing List Subject: Re: Houston Summer -> duplicate inode range In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sat, 28 Jul 2001 at 20:27, Chris Bednar wrote: > Today, I had a disk overheat, which led to severe corruption on an XFS > volume. I have absolutely no experience or knowledge enough to help you out with your problem, but I was wondering: how does one monitor the temperature of the hard drives? I have sensors on my motherboard that I presume get the ambient temperature readings inside the case, and my hard drives are not too far away, but I was wondering if maybe hard drives have embedded thermal sensors? Or should the paranoid install some thermal sensor plastered on each drive? --> Jijo -- Federico Sevilla III :: jijo@leathercollection.ph Network Administrator :: The Leather Collection, Inc. From owner-linux-xfs@oss.sgi.com Sun Jul 29 04:47:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TBlT508885 for linux-xfs-outgoing; Sun, 29 Jul 2001 04:47:29 -0700 Received: from groucho.maths.monash.edu.au (groucho.maths.monash.edu.au [130.194.160.211]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TBlNV08848 for ; Sun, 29 Jul 2001 04:47:24 -0700 Received: (from rjh@localhost) by groucho.maths.monash.edu.au (8.8.8/8.8.8) id LAA16285 for linux-xfs@oss.sgi.com; Sun, 29 Jul 2001 11:47:20 GMT From: Robin Humble Message-Id: <200107291147.LAA16285@groucho.maths.monash.edu.au> Subject: Re: Everyone's favorite offtopic topic To: linux-xfs@oss.sgi.com Date: Sun, 29 Jul 2001 21:47:20 +1000 (EST) In-Reply-To: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> from "Seth Mos" at Jul 29, 2001 12:23:36 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seth Mos writes: >There recently was a message about building a $5000 dollar IDE raid on >slashdot IIRC. >Don't know the URL anymore. http://staff.sdsc.edu/its/terafile/ >Basic configuration was purchasing a large case which can house 16 disks >Purchase 16 100GB Maxtor IDE disks (the 540DX uses less power) >Purchase 2 3ware Escalade 6800 controllers >A PC for booting the machine. I was disapointed by this article. It was way more than $5k (probably that was Slashdot's mistake) which is to be expected for 16 disks I guess, however their performance barchart (which looks impressive) bears little relation to the numbers in their spreadsheet. In particular their RAID5 write numbers are kinda low at ~18MB/s. The newer 7000 series 3ware cards might be better??? Anyway - our latest datapoint: Initial setup tests of our XFS RAID box with a lowly pentium 450, eight 75G 7200rpm IBM drives, and two Promise Ultra100 Tx2 controller cards, cvs xfs kernel, seem to indicate that we can get around 40MB/s RAID5 writes. Alternatively we can double their 50-60MB/s RAID0 reads to around 110MB/s(!). We were pretty happy to see those numbers :) We're still setting up the machine (these are from late last night so should maybe be taken with a grain of salt) and are moving to faster memory and cpu soon, so hope to see them improve. Also one of our disks is misbehaving and probably is dragging the numbers down. I should try bonnie++ with 4x memory size and not just the default 2x also - that may lower our numbers a bit and remove more caching effects. We haven't played with chunk sizes, mkfs options, mount options, or external logs yet. I also tried the SDSC folks 'fastest' 2xRAID5 + RAID0 configuration, but it was no quicker than just a RAID5 over all 8 disks. I guess they're seeing some artifacts from their 3ware cards/drivers. XFS seemed slightly slower (5%?) than ext2 for the tests we've run so far. We're running some NFS tests over 100Mbit now. Gigabit will follow once we have another cat5 gigabit card somewhere to write from! :) cheers, robin From owner-linux-xfs@oss.sgi.com Sun Jul 29 04:53:05 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TBr5S09903 for linux-xfs-outgoing; Sun, 29 Jul 2001 04:53:05 -0700 Received: from hermes.ntu.edu.au (hermes.ntu.edu.au [138.80.128.30]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TBr3V09883 for ; Sun, 29 Jul 2001 04:53:03 -0700 Received: from [138.80.49.10] (unknown [138.80.49.10]) by hermes.ntu.edu.au (Postfix) with ESMTP id 1F6431F5AF for ; Sun, 29 Jul 2001 21:23:01 +0930 (CST) Subject: Re: Where is ACL information stored with XFS? From: Mark Bradbury To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Evolution/0.11.99 (Preview Release) Date: 29 Jul 2001 21:26:40 +0930 Message-Id: <996407801.3095.9.camel@pluto.ntu.edu.au> Mime-Version: 1.0 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Yes I would also like to know dump and restore are OK for small systems but what about a 1 TB system SGI have been using this filesystem for a while so there must be a better solution. We have just had to restore 100GB of files after a (2)discs failed on us this was with a ext2 filesystem If we had XSF and samba 2.2.1a how would we restore the ACL's ? From owner-linux-xfs@oss.sgi.com Sun Jul 29 05:42:55 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TCgtE16906 for linux-xfs-outgoing; Sun, 29 Jul 2001 05:42:55 -0700 Received: from camdb.vilcom.com (IDENT:root@[199.72.107.235]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TCgrV16883 for ; Sun, 29 Jul 2001 05:42:53 -0700 Received: from towerpc (64-40-83-60.mb.dsl.mebtel.net [64.40.83.60]) by camdb.vilcom.com (8.9.3/8.9.3) with ESMTP id IAA16512; Sun, 29 Jul 2001 08:50:44 -0400 From: "Steven Tower" To: "'Keith Matthews'" , Subject: RE: Re[2]: Everyone's favorite offtopic topic Date: Sun, 29 Jul 2001 08:41:44 -0400 Message-ID: <000c01c1182b$d37eafc0$3c532840@towerpc> 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.2616 In-Reply-To: <20010729104554.D85CE125E6@rebutia.sweeney.demon.co.uk> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2505.0000 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > If you think about using 7200RPM disks you better start looking for > > multiple 400W powersupply's. IDE disks tend to have the problem to all > > start to spin up at boot. Scsi does this when asked to :-) > > Only if specifcally configured to do so I believe. Mine have always > come to auto spin-up on power-up and needed reconfiguring (IBM > Ultrastar etc). Did you actually find a solution to have them power up in sequence or at least on a delay? (Sorry for continuing the thread, I just ordered 2 3ware controllers with IBM Deskstar drives 4 each) Steven From owner-linux-xfs@oss.sgi.com Sun Jul 29 05:54:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TCs0w18314 for linux-xfs-outgoing; Sun, 29 Jul 2001 05:54:00 -0700 Received: from ente.berdmann.de (pD90115F3.dip.t-dialin.net [217.1.21.243]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TCrvV18292 for ; Sun, 29 Jul 2001 05:53:57 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15Qq4n-000814-00; Sun, 29 Jul 2001 14:53:45 +0200 Message-ID: <3B640759.631134E8@berdmann.de> Date: Sun, 29 Jul 2001 14:53:45 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: "amanda-users@amanda.org" CC: jrj@cc.purdue.edu, Linux XFS Mailing List Subject: Re: xfsdump estimates sometimes fail References: <200107232132.QAA03943@gandalf.cc.purdue.edu> <3B5E6D9D.53541623@berdmann.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > >on a particular host (Linux 2.4.6-prexy-xfs, RH 7.1 + LVM + XFS, Amanda > > >2.4.2p2) sometimes sendsize fails to estimate sizes with xfsdump. > > I recognized kernel oopses in syslog when Amanda tried to backup this > host (maxdumps=3): [...] > Ok, I'll upgrade the kernel from 2.4.6-pre5-xfs to 2.4.7-xfs before any > further investigation... Boy, that was a story... - Upgraded to Kernel 2.4.7-xfs and rebooted. - Mounting of /var failed with OOPS (sorry, no copy) - Rebooted to single user mode - "xfs_repair /dev/vg1/var" ran forever (> 30 min) with no output. Instead, each RAID array on that Compaq ML 530 containing 13 hard disks was read sequentially (that's what the LED's suggested). - xfs_repair of other XFS filesystems showed that same behaviour - no interruption possible, had to power off to reboot - Commented out the XFS filesystems in /etc/fstab avoiding them to be mounted by RedHat's init scripts even in single user mode - / was still on ext2fs - Reboot (i.e., power off) - xfs_repair for the /var filesystem produced a very ugly output (sorry, no copy) - xfs_repair of other XFS filesystems was ok - After editing /etc/fstab again I rebooted and went back to normal operation Conclusions: - Under rare circumstances it is possible to crash the kernel by trying to mount a damaged XFS filesystem with no chance to further xfs_repair with that kernel Many thanks to John R. Jackson for his help how to drive Amanda's sendsize by hand. From owner-linux-xfs@oss.sgi.com Sun Jul 29 06:00:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TD0We19344 for linux-xfs-outgoing; Sun, 29 Jul 2001 06:00:32 -0700 Received: from ente.berdmann.de (pD90115F3.dip.t-dialin.net [217.1.21.243]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TD0TV19324 for ; Sun, 29 Jul 2001 06:00:29 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15QqB8-00083a-00; Sun, 29 Jul 2001 15:00:18 +0200 Message-ID: <3B6408C9.A37CBD50@berdmann.de> Date: Sun, 29 Jul 2001 14:59:53 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Federico Sevilla III CC: Linux XFS Mailing List Subject: Re: Houston Summer -> duplicate inode range References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I have absolutely no experience or knowledge enough to help you out with > your problem, but I was wondering: how does one monitor the temperature of > the hard drives? I have sensors on my motherboard that I presume get the > ambient temperature readings inside the case, and my hard drives are not > too far away, but I was wondering if maybe hard drives have embedded > thermal sensors? Or should the paranoid install some thermal sensor > plastered on each drive? Maybe you can use S.M.A.R.T. for that purpose (smartd, smartctl): # /usr/sbin/smartctl -a /dev/hdb Device: IBM-DTLA-307045 Supports ATA Version 5 Drive supports S.M.A.R.T. and is enabled Check S.M.A.R.T. Passed General Smart Values: Off-line data collection status: (0x00) Offline data collection activity was never started Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run Total time to complete off-line data collection: (2294) Seconds Offline data collection Capabilities: (0x1b) SMART EXECUTE OFF-LINE IMMEDIATE Automatic timer ON/OFF support Suspend Offline Collection upon new command Offline surface scan supported Self-test supported Smart Capablilities: (0x0003) Saves SMART data before entering power-saving mode Supports SMART auto save timer Error logging capability: (0x01) Error logging supported Short self-test routine recommended polling time: ( 2) Minutes Extended self-test routine recommended polling time: ( 28) Minutes Vendor Specific SMART Attributes with Thresholds: Revision Number: 16 Attribute Flag Value Worst Threshold Raw Value ( 1)Raw Read Error Rate 0x000b 100 100 060 000000000000 ( 2)Throughput Performance 0x0005 132 132 050 000000000157 ( 3)Spin Up Time 0x0007 090 090 024 00060143013e ( 4)Start Stop Count 0x0012 100 100 000 00000000000b ( 5)Reallocated Sector Ct 0x0033 100 100 005 000000000000 ( 7)Seek Error Rate 0x000b 100 100 067 000000000000 ( 8)Seek Time Preformance 0x0005 130 130 020 000000000022 ( 9)Power On Hours 0x0012 100 100 000 000000000450 ( 10)Spin Retry Count 0x0013 100 100 060 000000000000 ( 12)Power Cycle Count 0x0032 100 100 000 00000000000b (192)Unknown Attribute 0x0032 100 100 050 00000000000b (193)Unknown Attribute 0x0012 100 100 050 00000000000b (194)Unknown Attribute 0x0002 105 105 000 000000000034 (196)Reallocated Event Count 0x0032 100 100 000 000000000000 (197)Current Pending Sector 0x0022 100 100 000 000000000000 (198)Offline Uncorrectable 0x0008 100 100 000 000000000000 (199)UDMA CRC Error Count 0x000a 200 200 000 000000000000 SMART Error Log: SMART Error Logging Version: 1 No Errors Logged From owner-linux-xfs@oss.sgi.com Sun Jul 29 06:02:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TD2u819773 for linux-xfs-outgoing; Sun, 29 Jul 2001 06:02:56 -0700 Received: from ente.berdmann.de (pD90115F3.dip.t-dialin.net [217.1.21.243]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TD2rV19753 for ; Sun, 29 Jul 2001 06:02:54 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15QqDT-000841-00; Sun, 29 Jul 2001 15:02:43 +0200 Message-ID: <3B640973.F9E2C8F4@berdmann.de> Date: Sun, 29 Jul 2001 15:02:43 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Keith Matthews CC: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic References: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> <20010729104554.D85CE125E6@rebutia.sweeney.demon.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > If you think about using 7200RPM disks you better start looking for > > multiple 400W powersupply's. IDE disks tend to have the problem to all > > start to spin up at boot. Scsi does this when asked to :-) > > Only if specifcally configured to do so I believe. Mine have always > come to auto spin-up on power-up and needed reconfiguring (IBM > Ultrastar etc). IBM's SCSI disks usually have a jumper for that purpose (auto spin enable). From owner-linux-xfs@oss.sgi.com Sun Jul 29 06:06:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TD6Wk20304 for linux-xfs-outgoing; Sun, 29 Jul 2001 06:06:32 -0700 Received: from ente.berdmann.de (pD90115F3.dip.t-dialin.net [217.1.21.243]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TD6UV20285 for ; Sun, 29 Jul 2001 06:06:30 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15QqGx-00085H-00; Sun, 29 Jul 2001 15:06:19 +0200 Message-ID: <3B640A4B.99B59006@berdmann.de> Date: Sun, 29 Jul 2001 15:06:19 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Seth Mos CC: Anthony W Hornby , linux-xfs@oss.sgi.com Subject: Re: Where is ACL information stored with XFS? References: <4.3.2.7.2.20010729125821.02ca37e0@pop.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >If I back up my filesystem onto tape using regular backup > >software (veritas,tivoli, arkeia etc etc) > >will the ACL information be restored when i restore the files from tape? > > probably not. Amanda can be made to work with xfsdump. > Some of them are actually working on supporting it natively. Amanda works great with xfsdump/xfsrestore. You just have to have xfsdump in place before running ./configure. From owner-linux-xfs@oss.sgi.com Sun Jul 29 07:38:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TEcDi28530 for linux-xfs-outgoing; Sun, 29 Jul 2001 07:38:13 -0700 Received: from wwweasel.geeksrus.net (wwweasel.geeksrus.net [64.67.200.82]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TEcBV28511 for ; Sun, 29 Jul 2001 07:38:12 -0700 Received: (from alane@localhost) by wwweasel.geeksrus.net (8.11.4/8.11.4) id f6TEc5N21568 for linux-xfs@oss.sgi.com; Sun, 29 Jul 2001 10:38:05 -0400 Date: Sun, 29 Jul 2001 10:38:05 -0400 From: Alan Eldridge To: SGI XFS Dev List Subject: patch to build current cvs Message-ID: <20010729103805.A20499@wwweasel.geeksrus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Seems as though we need this to compile. ---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<--- --- linux/arch/i386/kernel/msr.c.or Sat Jul 28 07:15:20 2001 +++ linux/arch/i386/kernel/msr.c Sun Jul 29 02:18:57 2001 @@ -39,6 +39,7 @@ #include #include #include +#include #ifdef CONFIG_SMP ---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<-snip---8<--- -- Alan Eldridge from std_disclaimer import * From owner-linux-xfs@oss.sgi.com Sun Jul 29 08:34:31 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TFYVN32540 for linux-xfs-outgoing; Sun, 29 Jul 2001 08:34:31 -0700 Received: from ente.berdmann.de (pD90115F3.dip.t-dialin.net [217.1.21.243]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TFYTV32521 for ; Sun, 29 Jul 2001 08:34:29 -0700 Received: from apollo.berdmann.de ([192.168.1.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.16 #2) id 15QsaF-0000DG-00; Sun, 29 Jul 2001 17:34:23 +0200 Message-ID: <3B642CFF.DD5F8938@berdmann.de> Date: Sun, 29 Jul 2001 17:34:23 +0200 From: "Bernhard R. Erdmann" X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i586) X-Accept-Language: de, en, fr MIME-Version: 1.0 To: Alan Eldridge CC: Linux XFS Mailing List Subject: Re: Houston Summer -> duplicate inode range References: <3B6408C9.A37CBD50@berdmann.de> <20010729090441.A30391@wwweasel.geeksrus.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > >Maybe you can use S.M.A.R.T. for that purpose (smartd, smartctl): > > > ># /usr/sbin/smartctl -a /dev/hdb > >Device: IBM-DTLA-307045 Supports ATA Version 5 > >Drive supports S.M.A.R.T. and is enabled > >Check S.M.A.R.T. Passed > > URL! URL! http://csl.cse.ucsc.edu/smart.shtml From owner-linux-xfs@oss.sgi.com Sun Jul 29 08:59:10 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TFxAs02138 for linux-xfs-outgoing; Sun, 29 Jul 2001 08:59:10 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TFx6V02112 for ; Sun, 29 Jul 2001 08:59:07 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id E3522638DB for ; Sun, 29 Jul 2001 17:01:16 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 29 Jul 2001 17:09:41 UT Subject: RE: Backup ACLs MIME-Version: 1.0 Date: Sun, 29 Jul 2001 16:59:04 +0100 Content-Type: text/plain; charset="iso-8859-1" Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEVt7LLPpx0rXjkRCyYzrWKkwerGgAAQ8iwAKHk+QA= From: "Juer Lee" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6TFx7V02114 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > >>hi, >> >>On Jul 26, 10:28am, Juer Lee wrote: >>> Subject: RE: Backup ACLs >>> >>> Nathan, >>> >>> Oh, yes, I can not find the references in >>> /usr/include/xfs/platform_defs.h. But I am sure that I appplied >>> xfs-progs-devel-1.1.3.0-ppc, it seemed that in this version >>O_DIRECT is >>> still not defined. >> >>Oh, just noticed this - sorry, thought you wrote "1.3.1". >>You will need a more recent version of xfsprogs-devel - >>if you are using the CVS tree, the xfsprogs/doc/INSTALL >>document will help you get there. >> >>Having a more recent xfsprogs-devel will also fix this >>next problem... >> >>> /export/xfsdump-1.0.11/dump/util.c:137: undefined reference to >>> `IRIX_MKDEV' >> >>Hope this helps. >> >>cheers. >> >>-- >>Nathan > > >Thanks. >I fixed that. >I am now adding sys_attrctl, after I success, I'll share my happiness >with all who are helping me. :) > >Juer > > News: It is my first time to look into the kernel code :( There are some errors when I run 'attr -l juer' --- ' attr_list: Bad address'. It seemed that the error is occured when calling function __user_walk(...) ( sys_attrctl --> user_path_walk ) int __user_walk(const char *name, unsigned flags, struct nameidata *nd) { char *tmp; int err; tmp = getname(name); err = PTR_ERR(tmp); /* Debug */ if( err == -14) printk("Attr Debug 1: Bad address!\n"); if (!IS_ERR(tmp)) { err = 0; if (path_init(tmp, flags, nd)) err = path_walk(tmp, nd); /* Debug */ if( err == -14) printk("Attr Debug 1: Bad address!\n"); putname(tmp); } return err; } I saw the error message "Attr Debug 1:Bad address!" when I ran that command. Did any expert :) meet this similar problem? Juer From owner-linux-xfs@oss.sgi.com Sun Jul 29 09:54:29 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TGsTi03379 for linux-xfs-outgoing; Sun, 29 Jul 2001 09:54:29 -0700 Received: from mailman.mnd.com (adsfw.mnd.com [208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TGsQV03360 for ; Sun, 29 Jul 2001 09:54:26 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id LAA21848 for ; Sun, 29 Jul 2001 11:54:03 -0500 Date: Sun, 29 Jul 2001 11:53:27 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: Linux XFS Mailing List Subject: raid5 resync aborted under heavy XFS use Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi. I still haven't determined whether this is an XFS problem, or a raid5 problem, but here's a situation I see if raid5 is trying to resync an XFS volume while people are thrashing it: Jul 26 14:55:38 gigem101 kernel: raid5: in raid5_sync_request, bufsize=512 redone=6 rtrn=-5 Jul 26 14:55:38 gigem101 kernel: md: sync_request returned sectors=-5 (j=296588438) ... exiting Jul 26 14:55:38 gigem101 kernel: raid5: resync aborted (err=-5)! I'm running a 2.4.5-SGI_XFS_1.0.1 kernel, with md patched up to print errors (patch at end). The default behaviour was just to print `raid5: resync aborted' with no other indication (which definitely needs to be fixed in the md driver anyway). As you can see, the chunk-size on the volume in question is 512k. We have another one (identical hw, 128k chunk) that synced without trouble, since I kept users off it. This has only happened during periods of heavy read/write activity. I'm starting this on the XFS list only, since I know there have been issues with chunk sizes >256k elsewhere. It doesn't look to me like this kernel has the I/O optimization problem that's been discussed of late, since that seems to be turned off for ALL md devices here. The basic setup is 8 u160-scsi 180GB Seagate disks on an adaptec 29160 controller, 512k chunk, left-sym parity, 1.2 TB XFS filesystem. ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ -kernel-2.4.5-raid5.printerr.patch--------- --- linux/drivers/md/md.c.printerr Sat Jul 21 05:25:52 2001 +++ linux/drivers/md/md.c Tue Jul 24 23:04:29 2001 @@ -3248,7 +3248,10 @@ err = down_interruptible(&mddev->resync_sem); if (err) + { + printk ("md: down_interruptible err=%d ... exiting\n", err); goto out_nolock; + } recheck: serialize = 0; @@ -3309,6 +3312,7 @@ sectors = mddev->pers->sync_request(mddev, j); if (sectors < 0) { + printk ("md: sync_request returned sectors=%d (j=%d) ... exiting\n", sectors, j); err = sectors; goto out; } --- linux/drivers/md/raid5.c.printerr Sat Jul 21 05:25:52 2001 +++ linux/drivers/md/raid5.c Tue Jul 24 23:06:42 2001 @@ -1167,6 +1167,7 @@ int data_disks = raid_disks-1; int redone = 0; int bufsize; + int rtrn; sh = get_active_stripe(conf, sector_nr, 0, 0); bufsize = sh->size; @@ -1183,7 +1184,11 @@ handle_stripe(sh); release_stripe(sh); - return (bufsize>>9)-redone; + if ((rtrn = (bufsize>>9) - redone) < 0) + { + printk ("raid5: in raid5_sync_request, bufsize=%d redone=%d rtrn=%d\n", bufsize, redone, rtrn); + } + return rtrn; } /* @@ -1241,15 +1246,16 @@ { raid5_conf_t *conf = data; mddev_t *mddev = conf->mddev; + int errval = 0; if (!conf->resync_parity) return; if (conf->resync_parity == 2) return; down(&mddev->recovery_sem); - if (md_do_sync(mddev,NULL)) { + if ((errval = md_do_sync(mddev,NULL))) { up(&mddev->recovery_sem); - printk("raid5: resync aborted!\n"); + printk("raid5: resync aborted (err=%d)!\n", errval); return; } conf->resync_parity = 0; From owner-linux-xfs@oss.sgi.com Sun Jul 29 11:30:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TIUwI13470 for linux-xfs-outgoing; Sun, 29 Jul 2001 11:30:58 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TIUuV13448 for ; Sun, 29 Jul 2001 11:30:56 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA11547; Sun, 29 Jul 2001 20:30:47 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729202627.0384c340@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 20:30:31 +0200 To: Chris Bednar , Linux XFS Mailing List From: Seth Mos Subject: Re: raid5 resync aborted under heavy XFS use In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 11:53 29-7-2001 -0500, Chris Bednar wrote: > Hi. I still haven't determined whether this is an XFS problem, or a > raid5 problem, >but here's a situation I see if raid5 is trying to resync an XFS volume >while people >are thrashing it: > > Jul 26 14:55:38 gigem101 kernel: raid5: in raid5_sync_request, > bufsize=512 redone=6 rtrn=-5 > Jul 26 14:55:38 gigem101 kernel: md: sync_request returned sectors=-5 > (j=296588438) ... exiting > Jul 26 14:55:38 gigem101 kernel: raid5: resync aborted (err=-5)! > >I'm running a 2.4.5-SGI_XFS_1.0.1 kernel, with md patched up to print >errors (patch at end). >The default behaviour was just to print `raid5: resync aborted' with no >other indication (which >definitely needs to be fixed in the md driver anyway). As you can see, >the chunk-size on >the volume in question is 512k. We have another one (identical hw, 128k >chunk) that synced >without trouble, since I kept users off it. This has only happened during >periods of heavy >read/write activity. there are some slight problems with xfs over software raid5 that have just been fixed in the CVS tree. There were also IO stall problems with this setup when you have a internal log. Basically you also want to make the log an external log which has a large performance boost. Search the archive for discussion about this. 1 week ago it was discussed and it has some bencmarks to back it up. > I'm starting this on the XFS list only, since I know there have been > issues with >chunk sizes >256k elsewhere. It doesn't look to me like this kernel has >the I/O optimization >problem that's been discussed of late, since that seems to be turned off >for ALL md devices >here. > > The basic setup is 8 u160-scsi 180GB Seagate disks on an adaptec > 29160 controller, >512k chunk, left-sym parity, 1.2 TB XFS filesystem. Can't comment on that. -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 11:33:04 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TIX4S13920 for linux-xfs-outgoing; Sun, 29 Jul 2001 11:33:04 -0700 Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.132]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TIX2V13900 for ; Sun, 29 Jul 2001 11:33:02 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA23900; Sun, 29 Jul 2001 20:32:52 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729203051.03933198@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 20:32:36 +0200 To: Matthew Geier From: Seth Mos Subject: Re: Where is ACL information stored with XFS? Cc: linux-xfs@oss.sgi.com In-Reply-To: <3B63F443.E70EFC7F@arts.usyd.edu.au> References: <4.3.2.7.2.20010729125821.02ca37e0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:32 29-7-2001 +1000, Matthew Geier wrote: >Seth Mos wrote: > > > >If I back up my filesystem onto tape using regular backup > > >software (veritas,tivoli, arkeia etc etc) > > >will the ACL information be restored when i restore the files from tape? > > > > probably not. Amanda can be made to work with xfsdump. > > Some of them are actually working on supporting it natively. > > > > We use Legato networker. I assume Networker 6 will not backup XFS >extended attributes as until now Linux hasn't really had them. It is also a work in progress for acls on ext2. They also use extended attributes. > However IRIX is a supported OS for Networker. What I need is for some >one at SGI to lean on networker to port the XFS bits of the IRIX client >to Linux, I can then get the update through our usual software maintence >channels... The source is out there and they know the on-disk format, which is a 100% mirror of the Irix disk spec. > I assume under Irix , networker backs up the EAs. Better ask them then to assume. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 11:45:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TIjaP15859 for linux-xfs-outgoing; Sun, 29 Jul 2001 11:45:36 -0700 Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.133]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TIjXV15833 for ; Sun, 29 Jul 2001 11:45:33 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp7.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA27853; Sun, 29 Jul 2001 20:44:09 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729203245.0392e988@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 20:43:52 +0200 To: Robin Humble , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Everyone's favorite offtopic topic In-Reply-To: <200107291147.LAA16285@groucho.maths.monash.edu.au> References: <4.3.2.7.2.20010729113909.03a12bc8@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:47 29-7-2001 +1000, Robin Humble wrote: >Seth Mos writes: > >There recently was a message about building a $5000 dollar IDE raid on > >slashdot IIRC. > >Don't know the URL anymore. > > http://staff.sdsc.edu/its/terafile/ > > >Basic configuration was purchasing a large case which can house 16 disks > >Purchase 16 100GB Maxtor IDE disks (the 540DX uses less power) > >Purchase 2 3ware Escalade 6800 controllers > >A PC for booting the machine. > >I was disapointed by this article. It was way more than $5k (probably >that was Slashdot's mistake) which is to be expected for 16 disks They had 3 different models. The one they built was 6000 or so. >I guess, however their performance barchart (which looks impressive) >bears little relation to the numbers in their spreadsheet. >In particular their RAID5 write numbers are kinda low at ~18MB/s. >The newer 7000 series 3ware cards might be better??? Write perfomance of raid5 always sucks. Tried doing heavy database work on a raid5 volume? Don't! Every database server I have built uses either raid 1 or raid10. >Anyway - our latest datapoint: >Initial setup tests of our XFS RAID box with a lowly pentium 450, eight >75G 7200rpm IBM drives, and two Promise Ultra100 Tx2 controller cards, >cvs xfs kernel, seem to indicate that we can get around 40MB/s RAID5 aha, different raid controller. >writes. Alternatively we can double their 50-60MB/s RAID0 reads to around >110MB/s(!). We were pretty happy to see those numbers :) But you probably can't go faster. The PCI bus does not go faster. Otherwise use a serverworks chipset with a dual PCI bus. Then you can go past the illusive 133MB/s. I believe that there are other motherboards out there that have 2 PCI busses. Even a Dell PowerEdge 1300 with a serverworks chipset had a dual PCI bus ($2000 machine) >We're still setting up the machine (these are from late last night so >should maybe be taken with a grain of salt) and are moving to faster >memory and cpu soon, so hope to see them improve. Also one of our >disks is misbehaving and probably is dragging the numbers down. How do you do that? bad cable perhaps (I've seen this with IDE before). > I >should try bonnie++ with 4x memory size and not just the default 2x >also - that may lower our numbers a bit and remove more caching effects. >We haven't played with chunk sizes, mkfs options, mount options, or >external logs yet. External logs make a huge difference and using more logbufs during mount will probably help if you have a busy filesystem. Make sure you have more the 256MB of ram. >I also tried the SDSC folks 'fastest' 2xRAID5 + RAID0 configuration, >but it was no quicker than just a RAID5 over all 8 disks. I guess >they're seeing some artifacts from their 3ware cards/drivers. 2 cards, 2 different raidsets, no problems. I think they are having a hard time living together on the bus. >XFS seemed slightly slower (5%?) than ext2 for the tests we've run so >far. We're running some NFS tests over 100Mbit now. Gigabit will follow >once we have another cat5 gigabit card somewhere to write from! :) It might be sligthly slower but it is possible that you are getting bitten by the internal log on the raid device. How many ethernetcards does the machine contain and wat network are you connected to? It might well be that you are not hitting the stalls yet because you are not pushing harder then 10MB/s over NFS. Cheers Seth -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 11:47:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TIli016288 for linux-xfs-outgoing; Sun, 29 Jul 2001 11:47:44 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TIlgV16257 for ; Sun, 29 Jul 2001 11:47:42 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA11431; Sun, 29 Jul 2001 20:47:36 +0200 (CEST) Message-Id: <4.3.2.7.2.20010729204417.03932f48@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sun, 29 Jul 2001 20:47:19 +0200 To: Mark Bradbury , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Where is ACL information stored with XFS? In-Reply-To: <996407801.3095.9.camel@pluto.ntu.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 21:26 29-7-2001 +0930, Mark Bradbury wrote: >Yes I would also like to know >dump and restore are OK for small systems use xfsdump and xfsrestore instead. >but what about a 1 TB system >SGI have been using this filesystem for a while so there must be a >better solution. I don't see how. If you have a tape that contains your data you can just restore it. You might be interested in checking out amanda as a frontend for restoring files and xfsdump and xfsrestore for the backend. >We have just had to restore 100GB of files after a (2)discs failed on us >this was with a ext2 filesystem ? >If we had XSF and samba 2.2.1a how would we restore the ACL's ? Using xfsrestore ofcourse :-) the xfs dump/restore utilities know about acls and extended attrributes so they will happily back them up. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Sun Jul 29 13:33:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TKXWG32134 for linux-xfs-outgoing; Sun, 29 Jul 2001 13:33:32 -0700 Received: from mailman.mnd.com (adsfw.mnd.com [208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TKXTV32109 for ; Sun, 29 Jul 2001 13:33:29 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id PAA27162; Sun, 29 Jul 2001 15:33:03 -0500 Date: Sun, 29 Jul 2001 15:32:28 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: Seth Mos cc: Linux XFS Mailing List Subject: Re: raid5 resync aborted under heavy XFS use In-Reply-To: <4.3.2.7.2.20010729202627.0384c340@pop.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > there are some slight problems with xfs over software raid5 that have just > been fixed in the CVS tree. There were also IO stall problems with this > setup when you have a internal log. Basically you also want to make the log > an external log which has a large performance boost. > > Search the archive for discussion about this. 1 week ago it was discussed > and it has some bencmarks to back it up. I've seen them. For some reason, I'm suspicious that this is a different problem. An external log is scary to me; I can afford lackluster write performance easier than I can afford: ``You know that $16k RAID setup you bought? it's gone to Hell because the one disk I was using for the log croaked.'' or: ``You know that big RAID system? Well, I moved it from one machine to another, and now it won't work.'' In my opinion, an internal log has to work reasonably well for XFS to be viable. It's fine, of course, if an external log works better, and I don't mind doing that on my own systems. I'll take a shot at CVS... by the way, is an internal log also a performance issue on IRIX systems? ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ From owner-linux-xfs@oss.sgi.com Sun Jul 29 13:54:24 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TKsOJ02808 for linux-xfs-outgoing; Sun, 29 Jul 2001 13:54:24 -0700 Received: from mailman.mnd.com (adsfw.mnd.com [208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TKsMV02789 for ; Sun, 29 Jul 2001 13:54:22 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id PAA27658; Sun, 29 Jul 2001 15:53:54 -0500 Date: Sun, 29 Jul 2001 15:53:18 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: Seth Mos cc: Linux XFS Mailing List Subject: Re: raid5 resync aborted under heavy XFS use In-Reply-To: <4.3.2.7.2.20010729202627.0384c340@pop.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorry for the followup followup... > there are some slight problems with xfs over software raid5 that have just > been fixed in the CVS tree. There were also IO stall problems with this The only fix I saw for this was to linux/fs/pagebuf/page_buf.c, mentioned in and of course the code has changed quite a bit between the 1.0.1 release and this patch, but it looked for all the World to me like the thing this was undoing wasn't being done in 1.0.1, so I'm not convinced this is the same bug, fixed tho it may be elsewhere. ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ From owner-linux-xfs@oss.sgi.com Sun Jul 29 14:07:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TL73r04942 for linux-xfs-outgoing; Sun, 29 Jul 2001 14:07:03 -0700 Received: from groucho.maths.monash.edu.au (groucho.maths.monash.edu.au [130.194.160.211]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TL71V04916 for ; Sun, 29 Jul 2001 14:07:01 -0700 Received: (from rjh@localhost) by groucho.maths.monash.edu.au (8.8.8/8.8.8) id VAA07381 for linux-xfs@oss.sgi.com; Sun, 29 Jul 2001 21:06:59 GMT From: Robin Humble Message-Id: <200107292106.VAA07381@groucho.maths.monash.edu.au> Subject: Re: raid5 resync aborted under heavy XFS use To: linux-xfs@oss.sgi.com Date: Mon, 30 Jul 2001 07:06:59 +1000 (EST) In-Reply-To: from "Chris Bednar" at Jul 29, 2001 03:32:28 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Chris J. Bednar writes: > An external log is scary to me; I can afford lackluster >write performance easier than I can afford: > ``You know that $16k RAID setup you bought? it's gone to Hell > because the one disk I was using for the log croaked.'' I think the idea is that you put the log on a RAID1 device. >or: > ``You know that big RAID system? Well, I moved it from one > machine to another, and now it won't work.'' You can even put the log onto a different partition of your existing RAID5 disks. eg. RAID5 on /dev/sd*1 and RAID1 over /dev/sda2 + /dev/sdb2. Obviously this'll get you less performance as the log and data are going to the same disks, but it may make it more cohesive and portable for you. You still gain in that xfs and md don't have to go through hoops to write journal-sized chunks and data-sized chunks to the same place any more. At least that's what I understand from reading this list. This may be more of a gain when NFS is involved? I have yet to try it out - but will soon :) cheers, robin From owner-linux-xfs@oss.sgi.com Sun Jul 29 14:46:38 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TLkcF11234 for linux-xfs-outgoing; Sun, 29 Jul 2001 14:46:38 -0700 Received: from mail.gmx.net (sproxy.gmx.de [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TLkaV11203 for ; Sun, 29 Jul 2001 14:46:36 -0700 Received: (qmail 27481 invoked by uid 0); 29 Jul 2001 21:46:28 -0000 Received: from ae5e1.pppool.de (HELO gmx.de) (213.6.229.225) by mail.gmx.net (mp006-rz3) with SMTP; 29 Jul 2001 21:46:28 -0000 Message-ID: <3B64842E.2D60EE37@gmx.de> Date: Sun, 29 Jul 2001 23:46:22 +0200 From: Martin Stricker Organization: http://martin-stricker.de/ http://www.surfo.net/ http://www.masterportal24.com/cgi-bin/YaBB.cgi X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic References: <20010728231625.C19907@dkp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andrew Klaassen wrote: > > Hi, all. > > A number of times, questions have popped up on this list about > building really large arrays of IDE disks. Does anybody know if > there's a list dedicated to that? If not, does anybody have > suggestions as to the best way to get something like that set > up? I don't know one. > Anybody else think there might be enough interest to make > something like this a go? I'm interested, I'm looking forward to do this myself in the near future. Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Registered Linux user #210635: http://counter.li.org/ From owner-linux-xfs@oss.sgi.com Sun Jul 29 15:12:32 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TMCW815640 for linux-xfs-outgoing; Sun, 29 Jul 2001 15:12:32 -0700 Received: from smtp9.xs4all.nl (smtp9.xs4all.nl [194.109.127.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TMCTV15620 for ; Sun, 29 Jul 2001 15:12:29 -0700 Received: from xs3.xs4all.nl (xs3.xs4all.nl [194.109.6.44]) by smtp9.xs4all.nl (8.9.3/8.9.3) with ESMTP id AAA09352; Mon, 30 Jul 2001 00:12:27 +0200 (CEST) Received: from localhost (knuffie@localhost) by xs3.xs4all.nl (8.9.0/8.9.0) with ESMTP id AAA04380; Mon, 30 Jul 2001 00:12:27 +0200 (CEST) Date: Mon, 30 Jul 2001 00:12:27 +0200 (CEST) From: Seth Mos To: Chris Bednar cc: Linux XFS Mailing List Subject: Re: raid5 resync aborted under heavy XFS use In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, 29 Jul 2001, Chris Bednar wrote: > > there are some slight problems with xfs over software raid5 that have just > > been fixed in the CVS tree. There were also IO stall problems with this > > setup when you have a internal log. Basically you also want to make the log > > an external log which has a large performance boost. > > > > Search the archive for discussion about this. 1 week ago it was discussed > > and it has some bencmarks to back it up. > > I've seen them. For some reason, I'm suspicious that this > is a different problem. > > An external log is scary to me; I can afford lackluster > write performance easier than I can afford: > > ``You know that $16k RAID setup you bought? it's gone to Hell > because the one disk I was using for the log croaked.'' > > or: > > ``You know that big RAID system? Well, I moved it from one > machine to another, and now it won't work.'' Then make sure it's on a raid1 disk. And mark it with bright red labels. Otherwise you have a $16k raid setup that won't perform. Btw, if you do a clean umount and then move it you might have lost the log but you won't have lost the files. > In my opinion, an internal log has to work reasonably well for > XFS to be viable. It's fine, of course, if an external log works > better, and I don't mind doing that on my own systems. It's called flexibility ;) There must be a reason that it was originally thought off. > I'll take a shot at CVS... by the way, is an internal log > also a performance issue on IRIX systems? The issue with a log on raid5 is only valid for software raid5. I have seen no such issues with a hardware raid5 IIRC. It's just that the md raid code got in the way of the log. Cheers From owner-linux-xfs@oss.sgi.com Sun Jul 29 16:51:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6TNpkv32248 for linux-xfs-outgoing; Sun, 29 Jul 2001 16:51:46 -0700 Received: from plato.arts.usyd.edu.au (plato.arts.usyd.edu.au [129.78.16.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6TNpgV32216 for ; Sun, 29 Jul 2001 16:51:43 -0700 Received: from arts.usyd.edu.au (IDENT:matthew@holly.aitch.ucc.usyd.edu.au [129.78.226.234]) by plato.arts.usyd.edu.au (8.9.3/8.9.3) with ESMTP id JAA00087; Mon, 30 Jul 2001 09:51:31 +1000 (EST) Message-ID: <3B64A178.15BAC2F8@arts.usyd.edu.au> Date: Mon, 30 Jul 2001 09:51:20 +1000 From: Matthew Geier Organization: Arts IT Unit, Sydney University X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i686) X-Accept-Language: en, pdf MIME-Version: 1.0 To: Federico Sevilla III CC: Linux XFS Mailing List Subject: Re: Houston Summer -> duplicate inode range References: Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms8358E8831D0966FC94404638" Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk This is a cryptographically signed message in MIME format. --------------ms8358E8831D0966FC94404638 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Federico Sevilla III wrote: > > On Sat, 28 Jul 2001 at 20:27, Chris Bednar wrote: > > Today, I had a disk overheat, which led to severe corruption on an XFS > > volume. > > I have absolutely no experience or knowledge enough to help you out with > your problem, but I was wondering: how does one monitor the temperature of > the hard drives? I've just put into service a linux/XFS server based on the Intel SC5000 server chassis. The 'hot swap' scsi bays have a scsi management device on the bus. Among other things it monitors the temperature of the drive enclosure. The Mylex hardware RAID driver reports back when the system boots that the 'enclosure temperature is OK'. So the higher end stuff has things like disk bay temperature monitoring. --------------ms8358E8831D0966FC94404638 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIIH0AYJKoZIhvcNAQcCoIIHwTCCB70CAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC BbswggKKMIIB86ADAgECAgMFMYswDQYJKoZIhvcNAQECBQAwgZIxCzAJBgNVBAYTAlpBMRUw EwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUgVG93bjEPMA0GA1UEChMGVGhh d3RlMR0wGwYDVQQLExRDZXJ0aWZpY2F0ZSBTZXJ2aWNlczEoMCYGA1UEAxMfUGVyc29uYWwg RnJlZW1haWwgUlNBIDIwMDAuOC4zMDAeFw0wMTA3MDkxOTEyNThaFw0wMjA3MDkxOTEyNTha MEoxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxJzAlBgkqhkiG9w0BCQEWGG1h dHRoZXdAYXJ0cy51c3lkLmVkdS5hdTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA1H+o MQ4xn5lDS/7p9rYboPW7grw13lXOj7Xisip37QttkX7Ga3ITBXnsAKnuFK3Z7GtILACBXil1 BngLBOd0AlW9zqQBXEOP9aODNJzBsTb3+tOHwQo6shcORKQArKEinG00SuwBdzxALU3KWT6E yIUSvoz7q0PN4C8qUF3t00sCAwEAAaM1MDMwIwYDVR0RBBwwGoEYbWF0dGhld0BhcnRzLnVz eWQuZWR1LmF1MAwGA1UdEwEB/wQCMAAwDQYJKoZIhvcNAQECBQADgYEAiJu7SNBXsW7I+ZH9 e2+0M47BmR3DxV31VbW9mKcwuamusWSJJEy5MAKZc8b0snRX/XDkCpM+av3VxDJX8T3rxOE0 siyCC6Tclu6wjwjw0goXK4N6Xhsz+qwIfdoclNZkqK5yInEZtc5ijKr0IPRgch79f35WP82C SNHVYApmjzgwggMpMIICkqADAgECAgEMMA0GCSqGSIb3DQEBBAUAMIHRMQswCQYDVQQGEwJa QTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoT EVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERp dmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG 9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDAwODMwMDAwMDAwWhcN MDIwODI5MjM1OTU5WjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTES MBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNVBAsTFENlcnRpZmlj YXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBSU0EgMjAwMC44LjMw MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeMzKmY8cJJUU+0m54J2eBxdqIGYKXDuNE KYpjNSptcDz63K737nRvMLwzkH/5NHGgo22Y8cNPomXbDfpL8dbdYaX5hc1VmjUanZJ1qCeu 2HL5ugL217CR3hzpq+AYA6h8Q0JQUYeDPPA5tJtUihOH/7ObnUlmAC0JieyUa+mhaQIDAQAB o04wTDApBgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMS0yOTcwEgYDVR0T AQH/BAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwDQYJKoZIhvcNAQEEBQADgYEAcxtvJmWL/xU0 S1liiu1EvknH6A27j7kNaiYqYoQfuIdjdBxtt88aU5FL4c3mONntUPQ6bDSSrOaSnG7BIwHC CafvS65y3QZn9VBvLli4tgvBUFe17BzX7xe21Yibt6KIGu05Wzl9NPy2lhglTWr0ncXDkS+p lrgFPFL83eliA0gxggHdMIIB2QIBATCBmjCBkjELMAkGA1UEBhMCWkExFTATBgNVBAgTDFdl c3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMQ8wDQYDVQQKEwZUaGF3dGUxHTAbBgNV BAsTFENlcnRpZmljYXRlIFNlcnZpY2VzMSgwJgYDVQQDEx9QZXJzb25hbCBGcmVlbWFpbCBS U0EgMjAwMC44LjMwAgMFMYswCQYFKw4DAhoFAKCBmTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcN AQcBMBwGCSqGSIb3DQEJBTEPFw0wMTA3MjkyMzUxMjJaMCMGCSqGSIb3DQEJBDEWBBQQql0F WaxqWwsn9AYZDqrGwRvOGTA6BgkqhkiG9w0BCQ8xLTArMAoGCCqGSIb3DQMHMA4GCCqGSIb3 DQMCAgIAgDANBggqhkiG9w0DAgIBQDANBgkqhkiG9w0BAQEFAASBgD5SZWn4TxYMNVpYbcse cH4zY4370F0Yoykaf8ngQAy2yGQ0j+NkpV2yeNUFCJOkNJt8Kl4xpX6/LcPlErCajOB+xMbj VTPKQ88C0oPEWwP5P4TiS1dFzqpO6AHcdaQkvDmgMx+foqflaXcAYnl8EzNFi7fhMFcpe9L/ aP5tOH7C --------------ms8358E8831D0966FC94404638-- From owner-linux-xfs@oss.sgi.com Sun Jul 29 17:20:23 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6U0KNN04743 for linux-xfs-outgoing; Sun, 29 Jul 2001 17:20:23 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6U0KIV04708 for ; Sun, 29 Jul 2001 17:20:18 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6U0O8U23732 for ; Sun, 29 Jul 2001 17:24:08 -0700 Received: from fudge.melbourne.sgi.com (fudge.melbourne.sgi.com [134.14.55.184]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA15001; Mon, 30 Jul 2001 10:18:52 +1000 Received: (from ajag@localhost) by fudge.melbourne.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) id KAA89744; Mon, 30 Jul 2001 10:18:50 +1000 (EST) Date: Mon, 30 Jul 2001 10:18:49 +1000 From: Andrew Gildfind To: Juer Lee Cc: linux-xfs@oss.sgi.com Subject: Re: Backup ACLs Message-ID: <20010730101849.M46618@fudge.melbourne.sgi.com> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="y0ulUmNC+osPPQO6" X-Mailer: Mutt 1.0us In-Reply-To: ; from Juer.Lee@raidtec.ie on Sun, Jul 29, 2001 at 04:59:04PM +0100 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii > News: > > > It is my first time to look into the kernel code :( > There are some errors when I run 'attr -l juer' --- ' attr_list: Bad > address'. It seemed that the error is occured when calling function > __user_walk(...) ( sys_attrctl --> user_path_walk ) > > int __user_walk(const char *name, unsigned flags, struct nameidata *nd) > { > char *tmp; > int err; > > tmp = getname(name); > err = PTR_ERR(tmp); > > /* Debug */ > if( err == -14) > printk("Attr Debug 1: Bad address!\n"); > > if (!IS_ERR(tmp)) { > err = 0; > if (path_init(tmp, flags, nd)) > err = path_walk(tmp, nd); > > /* Debug */ > if( err == -14) > printk("Attr Debug 1: Bad address!\n"); > > putname(tmp); > } > return err; > } > > I saw the error message "Attr Debug 1:Bad address!" when I ran that > command. > Did any expert :) meet this similar problem? > > Juer > Hi Juer, This has come up before when Thomas Graichen was trying to get attrctl working on PowerPC. My best guess at the time was that it was something todo with the structure passed into the attrctl syscall doing something funny on ppc. Check out the list archive around 7 Dec 2001, I'll attach the last post I sent Thomas. We needed a few printk's added to check what was happening. Andrew -- Andrew Gildfind - R&D Software Engineer - SGI Melbourne Australia email: ajag@sgi.com - work: +61.3.9834.8200 mobile: 0412.834.183 --y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=ppc From owner-linux-xfs@oss.sgi.com Thu Dec 7 12:27:46 2000 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by fudge.melbourne.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via SMTP id MAA03273 for ; Thu, 7 Dec 2000 12:27:46 +1100 (EST) Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA02269; Thu, 7 Dec 2000 12:27:41 +1100 Received: from sgi.com (sgi.sgi.com [192.26.80.37]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id RAA30123; Wed, 6 Dec 2000 17:27:39 -0800 (PST) Received: from oss.sgi.com (oss.sgi.com [216.32.174.190]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id RAA06125; Wed, 6 Dec 2000 17:27:38 -0800 (PST) mail_from (owner-linux-xfs@oss.sgi.com) Received: by oss.sgi.com id ; Wed, 6 Dec 2000 17:27:05 -0800 Received: from deliverator.sgi.com ([204.94.214.10]:61489 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Wed, 6 Dec 2000 17:26:44 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id RAA21196 for ; Wed, 6 Dec 2000 17:26:42 -0800 (PST) mail_from (ajag@fudge.melbourne.sgi.com) Received: from fudge.melbourne.sgi.com (fudge.melbourne.sgi.com [134.14.55.184]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id MAA02257; Thu, 7 Dec 2000 12:24:09 +1100 Received: (from ajag@localhost) by fudge.melbourne.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) id MAA02973; Thu, 7 Dec 2000 12:24:05 +1100 (EST) Date: Thu, 7 Dec 2000 12:24:05 +1100 From: Andrew Gildfind To: thomas.graichen@innominate.de Cc: linux-xfs@oss.sgi.com Subject: Re: sys_attrctl not working on ppc Message-Id: <20001207122405.A2872@fudge.melbourne.sgi.com> References: <10011101103.ZM113097@wobbly.melbourne.sgi.com> <20001110094151.C333@ysabell> <10011110006.ZM127189@wobbly.melbourne.sgi.com> <10011141059.ZM128320@wobbly.melbourne.sgi.com> <20001201122045.G32822@fudge.melbourne.sgi.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: ; from news-innominate.list.sgi.xfs@innominate.de on Fri, Dec 01, 2000 at 08:05:15AM +0000 X-Orcpt: rfc822;linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: RO Content-Length: 4098 Lines: 145 On Fri, Dec 01, 2000 at 08:05:15AM +0000, Thomas Graichen wrote: > [also changed the subject to something more useful here] > > Andrew Gildfind wrote: > > > Hi Thomas, > > > Could you put a printk at the start of the sys_attrctl function defined > > in linux/fs/stat.c, and rerun the QA test 020, or drive the attribute code > > directly using xfs_attr, and check whether the printk actually gets called. > > > If it doesn't then we know for sure it's the syscall that isn't hooked up > > correctly. unistd.h and entry.S looked like the only places which needed > > to be changed but I may have missed something. If it does hit the the attribute > > syscall, then there's a more serious problem somewhere else in the code. > > looks like this is the case: > > ... > Start mounting filesystem: ide0(3,8) > Ending clean XFS mount for filesystem: ide0(3,8) > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > here is sys_attrctl > Start mounting filesystem: ide0(3,8) > Ending clean XFS mount for filesystem: ide0(3,8) > ppc:/usr/src/xfs/cmd/xfs/stress # > > this is the dmesg of check 020 - it gets called - so the problem is > somethere deeper ... maybe anykind of endian stuff of the parameters? > (just an idea) ... do you have any other idea? > > t > > -- > thomas.graichen@innominate.com > technical director innominate AG > clustering & security the linux architects > tel: +49-30-308806-13 fax: -77 http://www.innominate.com Couple of observations first: - xfs_attr always calls the attr_* and therefore the system call with a path, rather than a file descriptor. - xfs_attr is always called with ATTR_DONT_FOLLOW - that is it never follows symlinks The code looks like: asmlinkage long sys_attrctl(attr_obj_t obj, int type, attr_op_t *ops, int count) { int error = 0; struct inode *inode; struct dentry *dentry; struct file *f = NULL; struct nameidata nd; if (count <= 0) return -EINVAL; lock_kernel(); switch (type) { case ATTR_TYPE_FD: if (! (f = fget(obj.fd))) { error = -ENOENT; goto unlock; } dentry = f->f_dentry; break; case ATTR_TYPE_PATH: /* follow symlinks */ error = user_path_walk(obj.path, &nd); if (error) goto unlock; dentry = nd.dentry; break; case ATTR_TYPE_LPATH: error = user_path_walk_link(obj.path, &nd); if (error) goto unlock; dentry = nd.dentry; break; case ATTR_TYPE_PID: error = -ENOSYS; goto unlock; default: error = -EINVAL; goto unlock; } Which means that on the way in (and we know that at least its hitting the syscall), it will always take the ATTR_TYPE_LPATH case. I've had another look at your QA results (ppc.15-11-2000) they give the following: QA output created by 020 *** list non-existant file *** print attributes attr_list: Bad address Could not list attributes for !!! error return *** list non-xfs file (in /proc) *** print attributes attr_list: Bad address ... The first test checks the non-existent file case, which means that we should come into the syscall, walk the path and die immediately with an ENOENT, ie. we should never get into XFS code at all. The fact that we are getting a bad address even in this case suggests to me that there maybe something weird happening because the path comes out of an attr_obj_t structure - are we sure that those structures are the same size in userland/kernel on PPC? So... can you whack in another printk just after the switch and check whether the path lookup ever works - if it does I'm back in stumped-land, if not we have our culprit.. Andrew -- Andrew Gildfind - R&D Software Engineer - SGI PTG Melbourne Australia email: ajag@melbourne.sgi.com - work: +61.3.9834.8200 home: +61.3.9421.5335 --y0ulUmNC+osPPQO6-- From owner-linux-xfs@oss.sgi.com Sun Jul 29 17:21:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6U0La705005 for linux-xfs-outgoing; Sun, 29 Jul 2001 17:21:36 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6U0LYV04983 for ; Sun, 29 Jul 2001 17:21:34 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with SMTP id f6U0QSm25591 for ; Sun, 29 Jul 2001 17:26:29 -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 KAA15010; Mon, 30 Jul 2001 10:20:11 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA18574; Mon, 30 Jul 2001 10:20:11 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107301020.ZM246528@wobbly.melbourne.sgi.com> Date: Mon, 30 Jul 2001 10:20:10 +1000 In-Reply-To: "Juer Lee" "RE: Backup ACLs" (Jul 29, 4:59pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: "Juer Lee" , Subject: Re: Backup ACLs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi, On Jul 29, 4:59pm, Juer Lee wrote: > Subject: RE: Backup ACLs > > News: > > It is my first time to look into the kernel code :( > There are some errors when I run 'attr -l juer' --- ' attr_list: Bad > address'. It seemed that the error is occured when calling function > __user_walk(...) ( sys_attrctl --> user_path_walk ) > > int __user_walk(const char *name, unsigned flags, struct nameidata *nd) > { > char *tmp; > int err; > > tmp = getname(name); > err = PTR_ERR(tmp); > > /* Debug */ > if( err == -14) > printk("Attr Debug 1: Bad address!\n"); > > if (!IS_ERR(tmp)) { > err = 0; > if (path_init(tmp, flags, nd)) > err = path_walk(tmp, nd); > > /* Debug */ > if( err == -14) > printk("Attr Debug 1: Bad address!\n"); [side-note: you probably want to use different printk strings so that its easier to see which part of the code is actually failing]. > > putname(tmp); > } > return err; > } > > I saw the error message "Attr Debug 1:Bad address!" when I ran that > command. > Did any expert :) meet this similar problem? > Now that I think back, I remember Thomas came across this problem on ppc a while back also, I don't think it was ever resolved. What you've started doing above is probably the simplest way to go - I'd suggest keep doing that. You'll need to find the exact point in the code where the kernel is deciding to return EFAULT ... from a quick peek, I see there's one case in getname() - perhaps thats it. Once you find the offending line, you'll need to understand the conditional statement just prior to EFAULT being set; eg. use a few more printks before the condition to see what the values of the variables involved are and which part of it is evaluating to true (and then, hopefully, why). cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Jul 29 22:29:56 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6U5TuM25344 for linux-xfs-outgoing; Sun, 29 Jul 2001 22:29:56 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6U5TsV25325 for ; Sun, 29 Jul 2001 22:29:55 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id WAA19377 for ; Sun, 29 Jul 2001 22:29:41 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id PAA14841; Mon, 30 Jul 2001 15:29:51 +1000 Date: Mon, 30 Jul 2001 15:29:51 +1000 From: Keith Owens Message-Id: <200107300529.PAA14841@sherman.melbourne.sgi.com> Subject: TAKE - Sync XFS with kdb v1.8-2.4.8-pre1 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sync with kdb v1.8-2.4.8-pre1 Date: Sun Jul 29 22:28:27 PDT 2001 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:99742a linux/include/asm-i386/apic.h - 1.12 linux/arch/i386/kernel/msr.c - 1.9 linux/include/linux/dis-asm.h - 1.8 linux/kernel/kallsyms.c - 1.11 From owner-linux-xfs@oss.sgi.com Sun Jul 29 22:47:36 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6U5la625963 for linux-xfs-outgoing; Sun, 29 Jul 2001 22:47:36 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6U5lYV25943 for ; Sun, 29 Jul 2001 22:47:34 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id WAA00882 for ; Sun, 29 Jul 2001 22:45:18 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id PAA32748; Mon, 30 Jul 2001 15:47:31 +1000 Date: Mon, 30 Jul 2001 15:47:31 +1000 From: Keith Owens Message-Id: <200107300547.PAA32748@sherman.melbourne.sgi.com> Subject: TAKE - Sync XFS to kernel 2.4.8-pre2 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sync XFS to kernel 2.4.8-pre2 Date: Sun Jul 29 22:46:18 PDT 2001 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:99745a linux/net/ipv4/igmp.c - 1.14 linux/net/core/sock.c - 1.21 linux/net/core/dev.c - 1.38 linux/mm/page_alloc.c - 1.47 linux/kernel/softirq.c - 1.13 linux/kernel/ksyms.c - 1.98 linux/include/linux/parport_pc.h - 1.10 linux/include/linux/netdevice.h - 1.25 linux/include/linux/interrupt.h - 1.15 linux/include/linux/blkdev.h - 1.33 linux/include/asm-sparc/bitops.h - 1.11 linux/include/asm-i386/softirq.h - 1.10 linux/include/asm-i386/math_emu.h - 1.3 linux/drivers/video/cgfourteenfb.c - 1.8 linux/drivers/net/sunhme.c - 1.28 linux/drivers/isdn/isdn_tty.c - 1.14 linux/drivers/isdn/isdn_ppp.c - 1.16 linux/drivers/isdn/isdn_net.c - 1.21 linux/drivers/isdn/hisax/Makefile - 1.12 linux/drivers/char/mem.c - 1.37 linux/arch/sparc64/kernel/ptrace.c - 1.11 linux/arch/sparc64/kernel/ioctl32.c - 1.36 linux/arch/sparc64/Makefile - 1.11 linux/arch/sparc/mm/fault.c - 1.15 linux/arch/sparc/kernel/ptrace.c - 1.11 linux/arch/sparc/Makefile - 1.9 linux/Makefile - 1.107 linux/Documentation/Configure.help - 1.91 linux/drivers/isdn/hisax/md5sums.asc - 1.14 linux/drivers/isdn/hisax/cert.c - 1.5 linux/Documentation/isdn/HiSax.cert - 1.4 linux/fs/partitions/msdos.c - 1.14 linux/drivers/isdn/hisax/hfc_pci.c - 1.17 linux/drivers/block/DAC960.h - 1.7 linux/drivers/block/DAC960.c - 1.29 linux/drivers/isdn/hisax/sedlbauer_cs.c - 1.2 linux/include/linux/mii.h - 1.3 linux/drivers/media/video/meye.h - 1.2 linux/drivers/media/video/meye.c - 1.2 From owner-linux-xfs@oss.sgi.com Sun Jul 29 23:56:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6U6uIn28425 for linux-xfs-outgoing; Sun, 29 Jul 2001 23:56:18 -0700 Received: from relay.xlink.net (relay.xlink.net [193.141.40.4]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6U6uEV28406 for ; Sun, 29 Jul 2001 23:56:14 -0700 Received: from lizard.webland.de (lizard.webland.de [194.122.76.201]) by relay.xlink.net (8.9.3/8.8.7) with ESMTP id IAA04872; Mon, 30 Jul 2001 08:56:12 +0200 (MET DST) Received: (from uucp@localhost) by lizard.webland.de (8.8.8/8.8.7) id IAA17258; Mon, 30 Jul 2001 08:56:10 +0200 (MET DST) >Received: from mobile.sauter-bc.com (unknown [10.1.6.21]) by basel1.sauter-bc.com (Postfix) with ESMTP id F14CA57306; Mon, 30 Jul 2001 08:55:19 +0200 (CEST) Received: from ch.sauter-bc.com (support.cad.sba [10.1.200.117]) by mobile.sauter-bc.com (Postfix) with ESMTP id 5668925835; Mon, 30 Jul 2001 08:55:19 +0200 (CEST) Message-ID: <3B6504D7.712BB31F@ch.sauter-bc.com> Date: Mon, 30 Jul 2001 08:55:19 +0200 From: Simon Matter Organization: Sauter AG, Basel X-Mailer: Mozilla 4.77 [de] (X11; U; Linux 2.2.19-6.2.7 i686) X-Accept-Language: de-CH, en MIME-Version: 1.0 To: Chris Bednar Cc: Linux XFS Mailing List Subject: Re: raid5 resync aborted under heavy XFS use References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Chris Bednar schrieb: > > Hi. I still haven't determined whether this is an XFS problem, or a raid5 problem, > but here's a situation I see if raid5 is trying to resync an XFS volume while people > are thrashing it: Are you sure resync is aborted because of heavy load. I was having a similar situation where I thought resync aborted because of stress but I had to find out later that a broken disk was the culprit. > > Jul 26 14:55:38 gigem101 kernel: raid5: in raid5_sync_request, bufsize=512 redone=6 rtrn=-5 > Jul 26 14:55:38 gigem101 kernel: md: sync_request returned sectors=-5 (j=296588438) ... exiting > Jul 26 14:55:38 gigem101 kernel: raid5: resync aborted (err=-5)! > > I'm running a 2.4.5-SGI_XFS_1.0.1 kernel, with md patched up to print errors (patch at end). > The default behaviour was just to print `raid5: resync aborted' with no other indication (which > definitely needs to be fixed in the md driver anyway). As you can see, the chunk-size on > the volume in question is 512k. We have another one (identical hw, 128k chunk) that synced > without trouble, since I kept users off it. This has only happened during periods of heavy > read/write activity. > > I'm starting this on the XFS list only, since I know there have been issues with > chunk sizes >256k elsewhere. It doesn't look to me like this kernel has the I/O optimization > problem that's been discussed of late, since that seems to be turned off for ALL md devices > here. > > The basic setup is 8 u160-scsi 180GB Seagate disks on an adaptec 29160 controller, > 512k chunk, left-sym parity, 1.2 TB XFS filesystem. > > ---- > Chris J. Bednar > Director, Distributed Computing Product Group > http://AdvancedDataSolutions.com/ > > -kernel-2.4.5-raid5.printerr.patch--------- > > --- linux/drivers/md/md.c.printerr Sat Jul 21 05:25:52 2001 > +++ linux/drivers/md/md.c Tue Jul 24 23:04:29 2001 > @@ -3248,7 +3248,10 @@ > > err = down_interruptible(&mddev->resync_sem); > if (err) > + { > + printk ("md: down_interruptible err=%d ... exiting\n", err); > goto out_nolock; > + } > > recheck: > serialize = 0; > @@ -3309,6 +3312,7 @@ > sectors = mddev->pers->sync_request(mddev, j); > > if (sectors < 0) { > + printk ("md: sync_request returned sectors=%d (j=%d) ... exiting\n", sectors, j); > err = sectors; > goto out; > } > --- linux/drivers/md/raid5.c.printerr Sat Jul 21 05:25:52 2001 > +++ linux/drivers/md/raid5.c Tue Jul 24 23:06:42 2001 > @@ -1167,6 +1167,7 @@ > int data_disks = raid_disks-1; > int redone = 0; > int bufsize; > + int rtrn; > > sh = get_active_stripe(conf, sector_nr, 0, 0); > bufsize = sh->size; > @@ -1183,7 +1184,11 @@ > handle_stripe(sh); > release_stripe(sh); > > - return (bufsize>>9)-redone; > + if ((rtrn = (bufsize>>9) - redone) < 0) > + { > + printk ("raid5: in raid5_sync_request, bufsize=%d redone=%d rtrn=%d\n", bufsize, redone, rtrn); > + } > + return rtrn; > } > > /* > @@ -1241,15 +1246,16 @@ > { > raid5_conf_t *conf = data; > mddev_t *mddev = conf->mddev; > + int errval = 0; > > if (!conf->resync_parity) > return; > if (conf->resync_parity == 2) > return; > down(&mddev->recovery_sem); > - if (md_do_sync(mddev,NULL)) { > + if ((errval = md_do_sync(mddev,NULL))) { > up(&mddev->recovery_sem); > - printk("raid5: resync aborted!\n"); > + printk("raid5: resync aborted (err=%d)!\n", errval); > return; > } > conf->resync_parity = 0; From owner-linux-xfs@oss.sgi.com Mon Jul 30 02:42:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6U9gZF32084 for linux-xfs-outgoing; Mon, 30 Jul 2001 02:42:35 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6U9gTV32064 for ; Mon, 30 Jul 2001 02:42:29 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6U9gNP50444; Mon, 30 Jul 2001 11:42:24 +0200 (CEST) Message-ID: <3B652B74.670A1D1D@pasteur.fr> Date: Mon, 30 Jul 2001 11:40:04 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: oops on 2.4.7 (july 27th) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, Is there any kernel guru would could give me a hint on what could have caused this oops? The server was not buzy at that time. Kernel version 2.4.7 from CVS (july 27th) built with kgcc. Hardware dual P3-866Mhz/2x256 PC133 hda/hdc are used as software raid1 array for root and the external xfslog device (md1/md2) 7+1 hotspare on a 3ware 6800 card (JBOD+software raid5: md0). [tru@sheridan ~]$ cat /proc/cmdline BOOT_IMAGE=rd1-247xfs-smp ro root=902 BOOT_FILE=/boot/bzImage-2.4.7-xfs-23072001 ramdisk_size=2500 devfs=nomount noapic [tru@sheridan ~]$ cat /proc/version Linux version 2.4.7-xfs-23072001 (tru@sheridan.bis.pasteur.fr) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #5 SMP Mon Jul 23 22:40:02 CEST 2001 [tru@sheridan /tmp]$ ksymoops < oops.txt ksymoops 2.4.0 on i686 2.4.7-xfs-23072001. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.7-xfs-23072001/ (default) -m /boot/System.map-2.4.7-xfs-23072001 (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. Error (expand_objects): cannot stat(/lib/raid5.o) for raid5 ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/xor.o) for xor ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/raid1.o) for raid1 ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/3w-xxxx.o) for 3w-xxxx ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod ksymoops: No such file or directory Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/char/drm/drm.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/cdrom/driver.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/media/radio/radio.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/media/video/video.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/media/media.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/misc/misc.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/net/appletalk/appletalk.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/net/fc/fc.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/net/pcmcia/pcmcia_net.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/net/wan/wan.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/net/tokenring/tr.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/net/wireless/wireless_net.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/parport/driver.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/drivers/sound/sounddrivers.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/net/ipv4/netfilter/netfilter.o Warning (read_object): no symbols in /lib/modules/2.4.7-xfs-23072001/build/net/ipv6/netfilter/netfilter.o Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c022dae0, System.map says c01597d0. Ignoring ksyms_base entry Warning (compare_maps): mismatch on symbol nlmsvc_grace_period , lockd says f8a84234, /lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o says f8a83668. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o entry Warning (compare_maps): mismatch on symbol nlmsvc_ops , lockd says f8a84230, /lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o says f8a83664. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o entry Warning (compare_maps): mismatch on symbol nlmsvc_timeout , lockd says f8a84238, /lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o says f8a8366c. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o entry Warning (compare_maps): mismatch on symbol nfs_debug , sunrpc says f8aaac60, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa920. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol nfsd_debug , sunrpc says f8aaac64, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa924. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol nlm_debug , sunrpc says f8aaac68, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa928. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_debug , sunrpc says f8aaac5c, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa91c. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_garbage_args , sunrpc says f8aaac3c, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa8fc. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_success , sunrpc says f8aaac2c, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa8ec. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol rpc_system_err , sunrpc says f8aaac40, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa900. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol xdr_one , sunrpc says f8aaac24, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa8e4. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol xdr_two , sunrpc says f8aaac28, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa8e8. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (compare_maps): mismatch on symbol xdr_zero , sunrpc says f8aaac20, /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o says f8aaa8e0. Ignoring /lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o entry Warning (map_ksym_to_module): cannot match loaded module raid5 to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module xor to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module raid1 to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module 3w-xxxx to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module sd_mod to a unique module object. Trace may not be reliable. Warning (map_ksym_to_module): cannot match loaded module scsi_mod to a unique module object. Trace may not be reliable. Jul 19 19:24:14 sheridan kernel: Unable to handle kernel paging request at virtual address abdcee80 Jul 19 19:24:14 sheridan kernel: c023637c Jul 19 19:24:14 sheridan kernel: *pde = 00000000 Jul 19 19:24:14 sheridan kernel: Oops: 0002 Jul 19 19:24:14 sheridan kernel: CPU: 1 Jul 19 19:24:14 sheridan kernel: EIP: 0010:[alloc_skb+332/456] Jul 19 19:24:14 sheridan kernel: EIP: 0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Jul 19 19:24:14 sheridan kernel: EFLAGS: 00010282 Jul 19 19:24:14 sheridan kernel: eax: abdcee80 ebx: ed5db480 ecx: abdcc000 edx: dc216c80 Jul 19 19:24:14 sheridan kernel: esi: 000000f0 edi: 00002f20 ebp: d3db6000 esp: d3db7eb4 Jul 19 19:24:14 sheridan kernel: ds: 0018 es: 0018 ss: 0018 Jul 19 19:24:14 sheridan kernel: Process rsync (pid: 8028, stackpage=d3db7000) Jul 19 19:24:14 sheridan kernel: Stack: d867fa40 00000000 00002e7c 00000002 00000000 c02358c1 00002e80 000000f0 Jul 19 19:24:14 sheridan kernel: d864ceec 00002e7c d67c7134 d67c70e0 d3db6000 c0279ab2 d867fa40 00002e7c Jul 19 19:24:14 sheridan kernel: 00000040 d3db7f1c d864ceec d3db7f84 c02799a0 d864ceec c0130fc4 00000000 Jul 19 19:24:14 sheridan kernel: Call Trace: [sock_alloc_send_skb+113/264] [unix_stream_sendmsg+274/828] [unix_stream_sendmsg+0/828] [free_pages+36/40] [sock_sendmsg+129/164] [unix_stream_sendmsg+0/828] [sock_write+163/172] Jul 19 19:24:14 sheridan kernel: Call Trace: [] [] [] [] [] [] [] Jul 19 19:24:14 sheridan kernel: [] [] Jul 19 19:24:14 sheridan kernel: Code: c7 00 01 00 00 00 8b 83 88 00 00 00 c7 40 04 00 00 00 00 8b >>EIP; c023637c <===== Trace; c02358c1 Trace; c0279ab2 Trace; c02799a0 Trace; c0130fc4 <__alloc_pages+280/28c> Trace; c023315d Trace; c02799a0 Trace; c023337b Trace; c013768a Trace; c0106fcb Code; c023637c 00000000 <_EIP>: Code; c023637c <===== 0: c7 00 01 00 00 00 movl $0x1,(%eax) <===== Code; c0236382 6: 8b 83 88 00 00 00 mov 0x88(%ebx),%eax Code; c0236388 c: c7 40 04 00 00 00 00 movl $0x0,0x4(%eax) Code; c023638f 13: 8b 00 mov (%eax),%eax Jul 19 19:45:10 sheridan kernel: Unable to handle kernel paging request at virtual address 3d537020 Jul 19 19:45:10 sheridan kernel: c023637c Jul 19 19:45:10 sheridan kernel: *pde = 00000000 Jul 19 19:45:10 sheridan kernel: Oops: 0002 Jul 19 19:45:10 sheridan kernel: CPU: 0 Jul 19 19:45:10 sheridan kernel: EIP: 0010:[alloc_skb+332/456] Jul 19 19:45:10 sheridan kernel: EIP: 0010:[] Jul 19 19:45:10 sheridan kernel: EFLAGS: 00010202 Jul 19 19:45:10 sheridan kernel: eax: 3d537020 ebx: f200e320 ecx: 3d534000 edx: dc216c80 Jul 19 19:45:10 sheridan kernel: esi: 000000f0 edi: 000030c0 ebp: f604c000 esp: f604deb4 Jul 19 19:45:10 sheridan kernel: ds: 0018 es: 0018 ss: 0018 Jul 19 19:45:10 sheridan kernel: Process rsync (pid: 8102, stackpage=f604d000) Jul 19 19:45:10 sheridan kernel: Stack: f74140e0 00000000 00003008 00000002 00000202 c02358c1 00003020 000000f0 Jul 19 19:45:10 sheridan kernel: eda6954c 00003008 f751f5d4 f751f580 f604c000 c0279ab2 f74140e0 00003008 Jul 19 19:45:10 sheridan kernel: 00000040 f604df1c eda6954c f604df84 c02799a0 eda6954c c0130fc4 00000000 Jul 19 19:45:10 sheridan kernel: Call Trace: [sock_alloc_send_skb+113/264] [unix_stream_sendmsg+274/828] [unix_stream_sendmsg+0/828] [free_pages+36/40] [sock_sendmsg+129/164] [unix_stream_sendmsg+0/828] [sock_write+163/172] Jul 19 19:45:10 sheridan kernel: Call Trace: [] [] [] [] [] [] [] Jul 19 19:45:10 sheridan kernel: [] [] Jul 19 19:45:10 sheridan kernel: Code: c7 00 01 00 00 00 8b 83 88 00 00 00 c7 40 04 00 00 00 00 8b >>EIP; c023637c <===== Trace; c02358c1 Trace; c0279ab2 Trace; c02799a0 Trace; c0130fc4 <__alloc_pages+280/28c> Trace; c023315d Trace; c02799a0 Trace; c023337b Trace; c013768a Trace; c0106fcb Code; c023637c 00000000 <_EIP>: Code; c023637c <===== 0: c7 00 01 00 00 00 movl $0x1,(%eax) <===== Code; c0236382 6: 8b 83 88 00 00 00 mov 0x88(%ebx),%eax Code; c0236388 c: c7 40 04 00 00 00 00 movl $0x0,0x4(%eax) Code; c023638f 13: 8b 00 mov (%eax),%eax 37 warnings and 6 errors issued. Results may not be reliable. Regards, Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Mon Jul 30 03:21:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UALgu01117 for linux-xfs-outgoing; Mon, 30 Jul 2001 03:21:42 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UALdV01098 for ; Mon, 30 Jul 2001 03:21:39 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 3C2A1638CC; Mon, 30 Jul 2001 11:23:47 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 30 Jul 2001 11:33:15 UT Subject: RE: Backup ACLs MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 30 Jul 2001 11:21:37 +0100 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEYjZbf57XlfQqfR6in0nOjrWsB2gATkFkQ From: "Juer Lee" To: "Nathan Scott" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6UALdV01099 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >-----Original Message----- >From: Nathan Scott [mailto:nathans@wobbly.melbourne.sgi.com] >Sent: 30 July 2001 01:20 >To: Juer Lee; linux-xfs@oss.sgi.com >Subject: Re: Backup ACLs > > >hi, > >On Jul 29, 4:59pm, Juer Lee wrote: >> Subject: RE: Backup ACLs >> >> News: >> >> It is my first time to look into the kernel code :( >> There are some errors when I run 'attr -l juer' --- ' attr_list: Bad >> address'. It seemed that the error is occured when calling function >> __user_walk(...) ( sys_attrctl --> user_path_walk ) >> >> int __user_walk(const char *name, unsigned flags, struct >nameidata *nd) >> { >> char *tmp; >> int err; >> >> tmp = getname(name); >> err = PTR_ERR(tmp); >> >> /* Debug */ >> if( err == -14) >> printk("Attr Debug 1: Bad address!\n"); >> >> if (!IS_ERR(tmp)) { >> err = 0; >> if (path_init(tmp, flags, nd)) >> err = path_walk(tmp, nd); >> >> /* Debug */ >> if( err == -14) >> printk("Attr Debug 1: Bad address!\n"); > >[side-note: you probably want to use different printk >strings so that its easier to see which part of the code >is actually failing]. > >> >> putname(tmp); >> } >> return err; >> } >> >> I saw the error message "Attr Debug 1:Bad address!" when I ran that >> command. >> Did any expert :) meet this similar problem? >> > >Now that I think back, I remember Thomas came across this >problem on ppc a while back also, I don't think it was ever >resolved. What you've started doing above is probably the >simplest way to go - I'd suggest keep doing that. You'll >need to find the exact point in the code where the kernel >is deciding to return EFAULT ... from a quick peek, I see >there's one case in getname() - perhaps thats it. > >Once you find the offending line, you'll need to understand >the conditional statement just prior to EFAULT being set; >eg. use a few more printks before the condition to see what >the values of the variables involved are and which part of >it is evaluating to true (and then, hopefully, why). > >cheers. > >-- >Nathan Thanks. I am sure that the EFAULT is returned by __strncpy_from_user in arch/ppc/lib/string.S.But I am not familiar with PPC asm language, so .... :( I am sure that those structures used when calling sys_attrctl are the same in userland/kernel on PPC. Actually userland/kernel code are using same attr_kern.h and attributes.h. Juer From owner-linux-xfs@oss.sgi.com Mon Jul 30 05:07:43 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UC7hp02639 for linux-xfs-outgoing; Mon, 30 Jul 2001 05:07:43 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UC7aV02620 for ; Mon, 30 Jul 2001 05:07:36 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6UBK4P17344; Mon, 30 Jul 2001 13:20:04 +0200 (CEST) Message-ID: <3B654258.8C0BCDE6@pasteur.fr> Date: Mon, 30 Jul 2001 13:17:44 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: "linux-xfs@oss.sgi.com" Subject: Re: oops on 2.4.7 (july 27th) References: <3B652B74.670A1D1D@pasteur.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sorrry (shame on me for a too fast cut and paste oops.txt) Jul 28 09:11:38 sheridan kernel: Unable to handle kernel paging request at virtual address 84d7cc58 Jul 28 09:11:38 sheridan kernel: printing eip: Jul 28 09:11:38 sheridan kernel: c012d806 Jul 28 09:11:38 sheridan kernel: *pde = 00000000 Jul 28 09:11:38 sheridan kernel: Oops: 0000 Jul 28 09:11:38 sheridan kernel: CPU: 1 Jul 28 09:11:38 sheridan kernel: EIP: 0010:[kmem_cache_alloc_batch+70/128] Jul 28 09:11:38 sheridan kernel: EIP: 0010:[] Jul 28 09:11:38 sheridan kernel: EFLAGS: 00010087 Jul 28 09:11:38 sheridan kernel: eax: f095d000 ebx: f7df0d60 ecx: 8e562000 edx: c2808c40 Jul 28 09:11:38 sheridan kernel: esi: 00000011 edi: c210bb40 ebp: c210bba8 esp: d3e1de48 Jul 28 09:11:38 sheridan kernel: ds: 0018 es: 0018 ss: 0018 Jul 28 09:11:38 sheridan kernel: Process bpbkar (pid: 4474, stackpage=d3e1d000) Jul 28 09:11:38 sheridan kernel: Stack: c210bb40 000000f0 00000001 c012da4f c210bb40 000000f0 f3c22700 000000f0 Jul 28 09:11:38 sheridan kernel: c9acfc18 d3e1c000 c210bb40 00000286 d3e1c000 c0236626 000006dc 000000f0 Jul 28 09:11:38 sheridan kernel: ef2624a0 c9acfae0 c9acfc18 00000000 00000001 c0253a31 000006a0 000000f0 Jul 28 09:11:38 sheridan kernel: Call Trace: [kmalloc+123/264] [alloc_skb+262/456] [tcp_sendmsg+569/4636] [inet_sendmsg+0/64] [generic_file_read+99/128] [inet_sendmsg+58/64] [sock_sendmsg+129/164] Jul 28 09:11:38 sheridan kernel: Call Trace: [] [] [] [] [] [] [] Jul 28 09:11:38 sheridan kernel: [inet_sendmsg+0/64] [sock_write+163/172] [sys_write+142/196] [system_call+51/56] Jul 28 09:11:38 sheridan kernel: [] [] [] [] Jul 28 09:11:38 sheridan kernel: Jul 28 09:11:38 sheridan kernel: Code: 8b 44 82 18 89 42 14 83 f8 ff 75 05 8b 02 89 47 08 8b 03 89 [tru@sheridan /tmp]$ ksyms < oops2.txt > oops2.ksyms [tru@sheridan /tmp]$ cat !$ cat oops2.ksyms Address Symbol Defined by f8ab0000 __insmod_nfsd_O/lib/modules/2.4.7-xfs-23072001/kernel/fs/nfsd/nfsd.o_M3B5C8DBA_V132103 [nfsd] f8ab0060 __insmod_nfsd_S.text_L54000 [nfsd] f8abd560 __insmod_nfsd_S.rodata_L14208 [nfsd] f8ac0ce0 __insmod_nfsd_S.data_L2208 [nfsd] f8ac1660 __insmod_nfsd_S.bss_L1760 [nfsd] f8a79d48 lockd_up_Rsmp_f6933c48 [lockd] f8a79e54 lockd_down_Rsmp_a7b91a7b [lockd] f8a78434 nlmclnt_proc_Rsmp_622bddb6 [lockd] f8a7c0a4 nlmsvc_invalidate_client_Rsmp_b1c3f825 [lockd] f8a84230 nlmsvc_ops_Rsmp_f8199231 [lockd] f8a84234 nlmsvc_grace_period_Rsmp_f6177768 [lockd] f8a84238 nlmsvc_timeout_Rsmp_44b40505 [lockd] f8a78000 __insmod_lockd_O/lib/modules/2.4.7-xfs-23072001/kernel/fs/lockd/lockd.o_M3B5C8DB9_V132103 [lockd] f8a78060 __insmod_lockd_S.text_L28944 [lockd] f8a7f360 __insmod_lockd_S.rodata_L16096 [lockd] f8a83454 __insmod_lockd_S.data_L3020 [lockd] f8a84020 __insmod_lockd_S.bss_L1760 [lockd] f8a9e98c rpc_allocate_Rsmp_0cd1c989 [sunrpc] f8a9ea58 rpc_free_Rsmp_f9d1164c [sunrpc] f8a9e740 rpc_execute_Rsmp_4c253740 [sunrpc] f8a9f7fc rpc_init_task_Rsmp_e95f36a4 [sunrpc] f8a9dd70 rpc_sleep_on_Rsmp_01560f70 [sunrpc] f8a9e1c4 rpc_wake_up_next_Rsmp_ab8e791f [sunrpc] f8a9e154 rpc_wake_up_task_Rsmp_496b3ff1 [sunrpc] f8a9eec4 rpc_new_child_Rsmp_eb5e8519 [sunrpc] f8a9eefc rpc_run_child_Rsmp_b67fa76d [sunrpc] f8a9f5cc rpciod_down_Rsmp_babf0f35 [sunrpc] f8a9f4f0 rpciod_up_Rsmp_375492a4 [sunrpc] f8a9eab0 rpc_new_task_Rsmp_e6133e53 [sunrpc] f8a9e2cc rpc_wake_up_status_Rsmp_b5819d81 [sunrpc] f8a9ec30 rpc_release_task_Rsmp_27b0e917 [sunrpc] f8a9a060 rpc_create_client_Rsmp_3cd41ac2 [sunrpc] f8a9a260 rpc_destroy_client_Rsmp_54f6d1d5 [sunrpc] f8a9a1e8 rpc_shutdown_client_Rsmp_4f02a6d5 [sunrpc] f8a9f0f8 rpc_killall_tasks_Rsmp_dc4adb61 [sunrpc] f8a9a41c rpc_call_sync_Rsmp_4b18ff67 [sunrpc] f8a9a4b8 rpc_call_async_Rsmp_4eed8e06 [sunrpc] f8a9a558 rpc_call_setup_Rsmp_3e362067 [sunrpc] f8a9a314 rpc_clnt_sigmask_Rsmp_2df8ac99 [sunrpc] f8a9a3b8 rpc_clnt_sigunmask_Rsmp_b613491c [sunrpc] f8a9e3f4 rpc_delay_Rsmp_60fbfb53 [sunrpc] f8a9a5c8 rpc_restart_call_Rsmp_bae6442b [sunrpc] f8a9d700 xprt_create_proto_Rsmp_f6ebf998 [sunrpc] f8a9d808 xprt_destroy_Rsmp_c43c2210 [sunrpc] f8a9d284 xprt_set_timeout_Rsmp_64e486c2 [sunrpc] f8a9f930 rpcauth_register_Rsmp_6f5770b9 [sunrpc] f8a9f95c rpcauth_unregister_Rsmp_6cc06204 [sunrpc] f8a9f9d4 rpcauth_init_credcache_Rsmp_575be941 [sunrpc] f8a9f9fc rpcauth_free_credcache_Rsmp_5cd437d8 [sunrpc] f8a9fb18 rpcauth_insert_credcache_Rsmp_dbe6ef64 [sunrpc] f8a9fc54 rpcauth_lookupcred_Rsmp_9470a3a7 [sunrpc] f8a9fc88 rpcauth_bindcred_Rsmp_845f517e [sunrpc] f8a9fce4 rpcauth_matchcred_Rsmp_c7295d88 [sunrpc] f8a9fd90 rpcauth_releasecred_Rsmp_33192460 [sunrpc] f8aa05e0 svc_create_Rsmp_4029b273 [sunrpc] f8aa0740 svc_create_thread_Rsmp_d11051c0 [sunrpc] f8aa0818 svc_exit_thread_Rsmp_e9ff1bcc [sunrpc] f8aa0668 svc_destroy_Rsmp_97db3a9b [sunrpc] f8aa2850 svc_drop_Rsmp_2814db92 [sunrpc] f8aa097c svc_process_Rsmp_e89d6615 [sunrpc] f8aa2350 svc_recv_Rsmp_2cecfb17 [sunrpc] f8aa0fdc svc_wake_up_Rsmp_3d5b58bb [sunrpc] f8aa2fc4 svc_makesock_Rsmp_c3fd6f5d [sunrpc] f8aa3d04 rpc_proc_register_Rsmp_f2a1c89e [sunrpc] f8aa3d54 rpc_proc_unregister_Rsmp_5bd26000 [sunrpc] f8aa3a80 rpc_proc_read_Rsmp_8e20de34 [sunrpc] f8aa3d68 svc_proc_register_Rsmp_e363ca9d [sunrpc] f8aa3db4 svc_proc_unregister_Rsmp_12e280e3 [sunrpc] f8aa3bbc svc_proc_read_Rsmp_866b52d3 [sunrpc] f8aa386c xdr_encode_array_Rsmp_716530af [sunrpc] f8aa38b0 xdr_encode_string_Rsmp_abc0fe0c [sunrpc] f8aa38d8 xdr_decode_string_Rsmp_6755aa62 [sunrpc] f8aa3844 xdr_decode_netobj_Rsmp_1be57115 [sunrpc] f8aa37b8 xdr_encode_netobj_Rsmp_29c6f164 [sunrpc] f8aaac20 xdr_zero_Rsmp_56773c08 [sunrpc] f8aaac24 xdr_one_Rsmp_43e0cbe8 [sunrpc] f8aaac28 xdr_two_Rsmp_2de06b03 [sunrpc] f8aa3948 xdr_shift_iovec_Rsmp_20fb9f87 [sunrpc] f8aa39ec xdr_zero_iovec_Rsmp_b1bb4dfe [sunrpc] f8aaac2c rpc_success_Rsmp_c05e6f43 [sunrpc] f8aaac3c rpc_garbage_args_Rsmp_a0111550 [sunrpc] f8aaac40 rpc_system_err_Rsmp_c39cf57e [sunrpc] f8aaac5c rpc_debug_Rsmp_31a89d59 [sunrpc] f8aaac60 nfs_debug_Rsmp_af5bf6ef [sunrpc] f8aaac64 nfsd_debug_Rsmp_bf9d1b96 [sunrpc] f8aaac68 nlm_debug_Rsmp_53445f68 [sunrpc] f8a9a000 __insmod_sunrpc_O/lib/modules/2.4.7-xfs-23072001/kernel/net/sunrpc/sunrpc.o_M3B5C8DBE_V132103 [sunrpc] f8a9a060 __insmod_sunrpc_S.text_L40992 [sunrpc] f8aa49e0 __insmod_sunrpc_S.rodata_L16832 [sunrpc] f8aa9820 __insmod_sunrpc_S.data_L828 [sunrpc] f8aa9b60 __insmod_sunrpc_S.bss_L4368 [sunrpc] f8a758f4 __insmod_3c59x_S.bss_L40 [3c59x] f8a73380 __insmod_3c59x_S.rodata_L7328 [3c59x] f8a6f060 __insmod_3c59x_S.text_L17008 [3c59x] f8a6f000 __insmod_3c59x_O/lib/modules/2.4.7-xfs-23072001/kernel/drivers/net/3c59x.o_M3B5C8DB3_V132103 [3c59x] f8a75040 __insmod_3c59x_S.data_L2016 [3c59x] f8a65000 __insmod_eepro100_O/lib/modules/2.4.7-xfs-23072001/kernel/drivers/net/eepro100.o_M3B5C8DB3_V132103 [eepro100] f8a65060 __insmod_eepro100_S.text_L11184 [eepro100] f8a68fe0 speedo_debug [eepro100] f8a67ca0 __insmod_eepro100_S.rodata_L4832 [eepro100] f8a69214 __insmod_eepro100_S.bss_L16 [eepro100] f8a68f80 __insmod_eepro100_S.data_L416 [eepro100] f8832000 __insmod_raid5_O/lib/raid5.o_M3B5C8DB2_V132103 [raid5] f8832060 __insmod_raid5_S.text_L16496 [raid5] f8836ce0 __insmod_raid5_S.data_L64 [raid5] f8834c40 device_bsize [raid5] f8836240 __insmod_raid5_S.rodata_L2720 [raid5] f882ff08 xor_block_Rsmp_7fd752b5 [xor] f882e000 __insmod_xor_O/lib/xor.o_M3B5C8DB2_V132103 [xor] f882e060 __insmod_xor_S.text_L8608 [xor] f8830200 __insmod_xor_S.rodata_L832 [xor] f883061c __insmod_xor_S.data_L140 [xor] f88306a8 __insmod_xor_S.bss_L8 [xor] f88297ec raid1_end_request [raid1] f882c520 __insmod_raid1_S.data_L96 [raid1] f882bca0 __insmod_raid1_S.rodata_L2176 [raid1] f8829000 __insmod_raid1_O/lib/raid1.o_M3B5C8DB2_V132103 [raid1] f882c658 __insmod_raid1_S.bss_L4 [raid1] f8829060 __insmod_raid1_S.text_L10816 [raid1] f882c524 raid1_retry_list [raid1] f882c658 raid1_retry_tail [raid1] f88220f4 tw_reset_device_extension [3w-xxxx] f8822da8 tw_scsiop_read_write [3w-xxxx] f882246c tw_scsi_eh_reset [3w-xxxx] f88207dc tw_enable_interrupts [3w-xxxx] f8822330 tw_scsi_eh_abort [3w-xxxx] f88236e0 __insmod_3w-xxxx_S.rodata_L10656 [3w-xxxx] f8821fe4 tw_post_command_packet [3w-xxxx] f882077c tw_empty_response_que [3w-xxxx] f8823200 tw_scsiop_request_sense [3w-xxxx] f882608c tw_driver_version [3w-xxxx] f8822510 tw_scsi_proc_info [3w-xxxx] f8820060 __insmod_3w-xxxx_S.text_L13872 [3w-xxxx] f8820104 tw_aen_drain_queue [3w-xxxx] f8823624 tw_unmask_command_interrupt [3w-xxxx] f88232e0 tw_setfeature [3w-xxxx] f88221d4 tw_reset_sequence [3w-xxxx] f8823534 tw_state_request_finish [3w-xxxx] f882063c tw_check_bits [3w-xxxx] f88206b4 tw_clear_host_interrupt [3w-xxxx] f88227bc tw_scsi_queue [3w-xxxx] f8820cac tw_free_device_extension [3w-xxxx] f8820000 __insmod_3w-xxxx_O/lib/3w-xxxx.o_M3B5C8DB6_V132103 [3w-xxxx] f88265a0 __insmod_3w-xxxx_S.bss_L128 [3w-xxxx] f882056c tw_allocate_memory [3w-xxxx] f8821f3c tw_mask_command_interrupt [3w-xxxx] f8820674 tw_check_errors [3w-xxxx] f88207ec tw_findcards [3w-xxxx] f88235a0 tw_state_request_start [3w-xxxx] f88234d4 tw_shutdown_device [3w-xxxx] f88206a4 tw_clear_attention_interrupt [3w-xxxx] f8822c04 tw_scsiop_read_capacity [3w-xxxx] f88229c8 tw_scsi_release [3w-xxxx] f8826080 __insmod_3w-xxxx_S.data_L160 [3w-xxxx] f8826090 tw_device_extension_count [3w-xxxx] f8820e84 tw_initialize_device_extension [3w-xxxx] f8822a18 tw_scsiop_inquiry [3w-xxxx] f8821e9c tw_ioctl_complete [3w-xxxx] f8821978 tw_ioctl [3w-xxxx] f8822b0c tw_scsiop_inquiry_complete [3w-xxxx] f8822304 tw_scsi_detect [3w-xxxx] f8821f4c tw_poll_status [3w-xxxx] f88222b8 tw_scsi_biosparam [3w-xxxx] f8823478 tw_setup_irq [3w-xxxx] f882041c tw_aen_read_queue [3w-xxxx] f882076c tw_disable_interrupts [3w-xxxx] f88265a0 tw_device_extension_list [3w-xxxx] f8820d58 tw_initconnection [3w-xxxx] f8820060 tw_aen_complete [3w-xxxx] f8823294 tw_scsiop_test_unit_ready [3w-xxxx] f882103c tw_initialize_units [3w-xxxx] f8823524 tw_soft_reset [3w-xxxx] f8822ce4 tw_scsiop_read_capacity_complete [3w-xxxx] f881b000 __insmod_sd_mod_O/lib/sd_mod.o_M3B5C8DB6_V132103 [sd_mod] f881db84 __insmod_sd_mod_S.bss_L24 [sd_mod] f881da20 __insmod_sd_mod_S.data_L160 [sd_mod] f881d360 __insmod_sd_mod_S.rodata_L1632 [sd_mod] f881ce3c revalidate_scsidisk [sd_mod] f881db84 sd [sd_mod] f881b060 __insmod_sd_mod_S.text_L8864 [sd_mod] f88026d0 scsi_register_module_Rsmp_fa20b7b0 [scsi_mod] f880272c scsi_unregister_module_Rsmp_81d85a75 [scsi_mod] f880957c scsi_free_Rsmp_475dddfa [scsi_mod] f8809480 scsi_malloc_Rsmp_1cce3f92 [scsi_mod] f8802db8 scsi_register_Rsmp_f4070a37 [scsi_mod] f8802d00 scsi_unregister_Rsmp_fc41627c [scsi_mod] f88041c0 scsicam_bios_param_Rsmp_cb36aefd [scsi_mod] f88042bc scsi_partsize_Rsmp_d6790a29 [scsi_mod] f8800130 scsi_allocate_device_Rsmp_3d7a999f [scsi_mod] f8800acc scsi_do_cmd_Rsmp_7f5eb9b3 [scsi_mod] f880b0f4 scsi_command_size_Rsmp_9b05ea5c [scsi_mod] f880375c scsi_ioctl_Rsmp_0d22e567 [scsi_mod] f8803b60 print_command_Rsmp_528232e7 [scsi_mod] f8803e64 print_sense_Rsmp_04f7b8b3 [scsi_mod] f8803e88 print_req_sense_Rsmp_6f31af5f [scsi_mod] f8803ea4 print_msg_Rsmp_8cc5ae07 [scsi_mod] f8803bb8 print_status_Rsmp_e4c08ccd [scsi_mod] f881695c scsi_dma_free_sectors_Rsmp_e930b3cb [scsi_mod] f8803ac4 kernel_scsi_ioctl_Rsmp_822cc5fe [scsi_mod] f8816960 scsi_need_isa_buffer_Rsmp_e22bca98 [scsi_mod] f88003b0 scsi_release_command_Rsmp_4cc5d9e8 [scsi_mod] f8804064 print_Scsi_Cmnd_Rsmp_cdd2bba3 [scsi_mod] f8804c20 scsi_block_when_processing_errors_Rsmp_993fb039 [scsi_mod] f8806dbc scsi_mark_host_reset_Rsmp_4e40c855 [scsi_mod] f88033a0 scsi_ioctl_send_command_Rsmp_ff7058d5 [scsi_mod] f8816e8c scsi_logging_level_Rsmp_af3dd7dc [scsi_mod] f88000a8 scsi_allocate_request_Rsmp_d8104977 [scsi_mod] f8800108 scsi_release_request_Rsmp_47761011 [scsi_mod] f8800738 scsi_wait_req_Rsmp_b0706f75 [scsi_mod] f88007e0 scsi_do_req_Rsmp_670353f0 [scsi_mod] f8807fa8 scsi_report_bus_reset_Rsmp_ffbf5966 [scsi_mod] f8807f70 scsi_block_requests_Rsmp_34c7c00f [scsi_mod] f8807f7c scsi_unblock_requests_Rsmp_b312acc8 [scsi_mod] f8802b3c scsi_get_host_dev_Rsmp_05449b04 [scsi_mod] f8802bb8 scsi_free_host_dev_Rsmp_23f59d47 [scsi_mod] f8805158 scsi_sleep_Rsmp_35962bf8 [scsi_mod] f88048a8 proc_print_scsidevice_Rsmp_fc0c77d5 [scsi_mod] f8816e90 proc_scsi_Rsmp_f603fe39 [scsi_mod] f88077fc scsi_io_completion_Rsmp_8703dc44 [scsi_mod] f8807710 scsi_end_request_Rsmp_e8d54af0 [scsi_mod] f8807fd0 scsi_register_blocked_host_Rsmp_953868a4 [scsi_mod] f8807fd4 scsi_deregister_blocked_host_Rsmp_ee821c19 [scsi_mod] f8816eb8 scsi_hostlist_Rsmp_e95b9d45 [scsi_mod] f8816ec0 scsi_hosts_Rsmp_d4480787 [scsi_mod] f8816ebc scsi_devicelist_Rsmp_1ee06b99 [scsi_mod] f880b100 scsi_device_types_Rsmp_d54b74ac [scsi_mod] f8804ad0 scsi_add_timer_Rsmp_530418c6 [scsi_mod] f8804b38 scsi_delete_timer_Rsmp_78fa9615 [scsi_mod] f8800000 __insmod_scsi_mod_O/lib/scsi_mod.o_M3B5C8DB6_V132103 [scsi_mod] f8800060 __insmod_scsi_mod_S.text_L43824 [scsi_mod] f880af20 __insmod_scsi_mod_S.rodata_L40352 [scsi_mod] f8815724 __insmod_scsi_mod_S.data_L5992 [scsi_mod] f8816e8c __insmod_scsi_mod_S.bss_L64 [scsi_mod] Tru Huynh wrote: > > Hello, > > Is there any kernel guru would could give me a hint on > what could have caused this oops? > The server was not buzy at that time. > > Kernel version 2.4.7 from CVS (july 27th) built with kgcc. > > Hardware dual P3-866Mhz/2x256 PC133 > hda/hdc are used as software raid1 array for root and > the external xfslog device (md1/md2) > 7+1 hotspare on a 3ware 6800 card (JBOD+software raid5: md0). > > [tru@sheridan ~]$ cat /proc/cmdline > BOOT_IMAGE=rd1-247xfs-smp ro root=902 > BOOT_FILE=/boot/bzImage-2.4.7-xfs-23072001 ramdisk_size=2500 > devfs=nomount noapic > [tru@sheridan ~]$ cat /proc/version > Linux version 2.4.7-xfs-23072001 (tru@sheridan.bis.pasteur.fr) (gcc > version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #5 SMP Mon Jul > 23 22:40:02 CEST 2001 > Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Mon Jul 30 06:53:28 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UDrS804346 for linux-xfs-outgoing; Mon, 30 Jul 2001 06:53:28 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UDrPV04327 for ; Mon, 30 Jul 2001 06:53:25 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6UDvIU04010 for ; Mon, 30 Jul 2001 06:57:18 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2562421; Mon, 30 Jul 2001 08:52:03 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA82501; Mon, 30 Jul 2001 08:52:03 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6UDp6J04035; Mon, 30 Jul 2001 08:51:06 -0500 Message-Id: <200107301351.f6UDp6J04035@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Chris Bednar cc: Seth Mos , Linux XFS Mailing List Subject: Re: raid5 resync aborted under heavy XFS use In-Reply-To: Message from Chris Bednar of "Sun, 29 Jul 2001 15:32:28 CDT." Date: Mon, 30 Jul 2001 08:51:05 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > > there are some slight problems with xfs over software raid5 that have just > > been fixed in the CVS tree. There were also IO stall problems with this > > setup when you have a internal log. Basically you also want to make the log > > > an external log which has a large performance boost. > > > > Search the archive for discussion about this. 1 week ago it was discussed > > and it has some bencmarks to back it up. > > I've seen them. For some reason, I'm suspicious that this > is a different problem. > > An external log is scary to me; I can afford lackluster > write performance easier than I can afford: > > ``You know that $16k RAID setup you bought? it's gone to Hell > because the one disk I was using for the log croaked.'' > > or: > > ``You know that big RAID system? Well, I moved it from one > machine to another, and now it won't work.'' > > In my opinion, an internal log has to work reasonably well for > XFS to be viable. It's fine, of course, if an external log works > better, and I don't mind doing that on my own systems. > > I'll take a shot at CVS... by the way, is an internal log > also a performance issue on IRIX systems? Looks like there has been some 'discussion' over the weekend. There have been two bugs with the raid5 code, one of which is in the 1.0.1 release, the other was not. o There was a stall problem where the raid would just grind to a halt, this was fixed by a kernel change in the 2.4.7-pre series. This was in the 1.0.1 release and would exhibit itself as a filesystem which just ground to a halt. o The second was a problem writing out an internal log. The log was not getting written correctly on raid5 devices, which meant you could not always mount the filesystem again without running xfs_repair. This problem was introduced and fixed in the cvs tree after the 1.0.1 release. As for internal vs external log. XFS has always had support for an external log, but on Irix the volume managers support building a volume with separate 'sub-volumes' which can have different layout characteristics from each other. Internally within the XFS code this is identical to the external log device on Linux, the only difference being that on Linux the log device must be specified by the administrator making and mounting the filesystem. As for raid5 log performance, the log is written in chunks of upto 32Kbytes, but these chunks can be any 512 byte multiple long, and start on any 512 byte boundary. This does not appear to be well treated by the raid5 code and results in less than optimal performance. A raid1 external log works much better and is still safe against a single failure. This appears to be an interaction with the linux raid5 software, Irix does not have software raid5, it always uses hardware for raid combinations which include parity. Can try the 2.4.7 patch which is on the ftp site, it has fixes to both raid5 problems. ftp://oss.sgi.com/projects/xfs/download/patches/patch-2.4.7-xfs-2001-07-27.bz2 It may be that your problem is still there and is being caused by the layout of the xfs logwrites, in which case the only fix may be to move to an external log until we can do something about the alignment of the log writes. Steve > > > ---- > Chris J. Bednar > Director, Distributed Computing Product Group > http://AdvancedDataSolutions.com/ From owner-linux-xfs@oss.sgi.com Mon Jul 30 06:56:00 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UDu0x04529 for linux-xfs-outgoing; Mon, 30 Jul 2001 06:56:00 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UDtwV04507 for ; Mon, 30 Jul 2001 06:55:58 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6UDxpU04164 for ; Mon, 30 Jul 2001 06:59:51 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id IAA2560950; Mon, 30 Jul 2001 08:54:36 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id IAA22278; Mon, 30 Jul 2001 08:54:36 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6UDrc004046; Mon, 30 Jul 2001 08:53:38 -0500 Message-Id: <200107301353.f6UDrc004046@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Mark Bradbury cc: linux-xfs@oss.sgi.com Subject: Re: Where is ACL information stored with XFS? In-Reply-To: Message from Mark Bradbury of "29 Jul 2001 21:26:40 +0930." <996407801.3095.9.camel@pluto.ntu.edu.au> Date: Mon, 30 Jul 2001 08:53:38 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Yes I would also like to know > dump and restore are OK for small systems > but what about a 1 TB system > SGI have been using this filesystem for a while so there must be a > better solution. > > We have just had to restore 100GB of files after a (2)discs failed on us > this was with a ext2 filesystem > > If we had XSF and samba 2.2.1a how would we restore the ACL's ? > > > Other folks have already said use xfsdump/xfsrestore if you want your ACLs backed up, and that Amanda does support them. I am not actually sure if any of the other backup products which run on xfs have the ability to back them up. And if they do, SGI has little influence with folks like Legato when it comes to getting features into their products! Steve From owner-linux-xfs@oss.sgi.com Mon Jul 30 07:02:40 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UE2eI04830 for linux-xfs-outgoing; Mon, 30 Jul 2001 07:02:40 -0700 Received: from zok.corp.sgi.com (zok.sgi.com [204.94.215.101]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UE2cV04810 for ; Mon, 30 Jul 2001 07:02:38 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by zok.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6UE7Zm05382 for ; Mon, 30 Jul 2001 07:07:35 -0700 Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id JAA2560179; Mon, 30 Jul 2001 09:01:17 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id JAA78960; Mon, 30 Jul 2001 09:01:16 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6UE0J104068; Mon, 30 Jul 2001 09:00:19 -0500 Message-Id: <200107301400.f6UE0J104068@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Colin Walters cc: linux-xfs@oss.sgi.com Subject: Re: bad clientid? In-Reply-To: Message from Colin Walters of "Fri, 27 Jul 2001 21:22:12 EDT." <87pual7sqj.church.of.emacs@space-ghost.verbum.org> Date: Mon, 30 Jul 2001 09:00:19 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > I'm building an ia32 server which will be running RAID 5 over three 40 > GB disks. We're using 4 RAID partitions (/var, /home, /usr, and /), > all using XFS. We booted using an NFS root, initialized the RAID > devices, made an XFS filesystem on all of them, mounted them, then > rsynced over our NFS root image to the target filesystems. > > This all worked fine. However, after rebooting, when we tried to > mount one of the arrays (which was /var), we got: > > Jul 28 01:03:27 debian kernel: Start mounting filesystem: md(9,1) > Jul 28 01:03:31 debian kernel: Starting XFS recovery on filesystem: md(9,1) ( > dev: 9/1) > Jul 28 01:03:31 debian kernel: XFS: xlog_recover_process_data: bad clientid > Jul 28 01:03:31 debian kernel: XFS: log mount/recovery failed > Jul 28 01:03:31 debian kernel: XFS: log mount failed > > The other partitions mounted correctly; I am confused as to why just > one of the partitions would fail. We ran xfs_repair /dev/md2, and it > didn't report any errors. After that, mounting the partition worked > just fine: > > Jul 28 01:03:49 debian kernel: Start mounting filesystem: md(9,1) > Jul 28 01:04:04 debian kernel: Ending clean XFS mount for filesystem: md(9,1) > > Any ideas? My guess is you are running a CVS or patch based kernel from sometime after the 1.0.1 release. There was a period of a couple of weeks where raid5 had this problem. If you update to the latest CVS (2.4.8-pre2 now) or get the latest 2.4.7 patch from the ftp site: ftp://oss.sgi.com/projects/xfs/download/patches/patch-2.4.7-xfs-2001-07-27.bz2 This should be fixed. What you did was the correct workaround for the kernel you have. Steve From owner-linux-xfs@oss.sgi.com Mon Jul 30 07:15:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UEFgu05292 for linux-xfs-outgoing; Mon, 30 Jul 2001 07:15:42 -0700 Received: from mailman.mnd.com ([208.226.69.17]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UEFdV05267 for ; Mon, 30 Jul 2001 07:15:39 -0700 Received: from linux1.production.mnd.com (IDENT:cjb@linux1.production.mnd.com [192.168.3.103]) by mailman.mnd.com (8.9.3/8.9.3) with ESMTP id EAA04430; Mon, 30 Jul 2001 04:50:14 -0500 Date: Mon, 30 Jul 2001 09:14:21 -0500 (CDT) From: Chris Bednar X-Sender: cjb@linux1.production.mnd.com To: Steve Lord cc: Seth Mos , Linux XFS Mailing List Subject: Re: raid5 resync aborted under heavy XFS use In-Reply-To: <200107301351.f6UDp6J04035@jen.americas.sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Looks like there has been some 'discussion' over the weekend. There have I'd put it without the quotes... it was useful to me, anyway. > o There was a stall problem where the raid would just grind to a halt, > this was fixed by a kernel change in the 2.4.7-pre series. This was > in the 1.0.1 release and would exhibit itself as a filesystem which > just ground to a halt. That's the one I couldn't find in the list; thanks. > o The second was a problem writing out an internal log. The log was > not getting written correctly on raid5 devices, which meant you > could not always mount the filesystem again without running > xfs_repair. This problem was introduced and fixed in the cvs tree > after the 1.0.1 release. After the weekend's discussion, I had a `clever' idea. Each disk in the array has a 128 MB partition, and a ~180 GB partition. The former are in a raid1 array with the log, the latter raid5 with the main XFS. Assuming this is a correct solution, it answers all my concerns; Everything is on the same array, and moving it means moving the raidtab and fstab entries, which one would have to do, anyway. And, of course, it's at least as safe as raid5 by itself. > As for raid5 log performance, the log is written in chunks of upto 32Kbytes, > but these chunks can be any 512 byte multiple long, and start on any 512 > byte boundary. This does not appear to be well treated by the raid5 code > and results in less than optimal performance. A raid1 external log works For our use pattern (avg file size ~1GB, near-WORM usage) performance is not nearly the issue that stability and safety are. I'll care a lot more about this when we get round to using it for home directories. > It may be that your problem is still there and is being caused by the > layout of the xfs logwrites, in which case the only fix may be to move > to an external log until we can do something about the alignment of the > log writes. Well, we have one system loaded up with a TB of data, which can just be mounted read-only until we're done processing it, and the other system now has an external log, since it wasn't in production yet. Also, it doesn't look to me like XFS is doing anything illegal; linux raid5 is kinda new as far as the 2.4 kernels are concerned... Just to be sure... thanks, Seth and Steve, for the discussion 8) ---- Chris J. Bednar Director, Distributed Computing Product Group http://AdvancedDataSolutions.com/ From owner-linux-xfs@oss.sgi.com Mon Jul 30 07:33:19 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UEXJZ05701 for linux-xfs-outgoing; Mon, 30 Jul 2001 07:33:19 -0700 Received: from babel.spoiled.org (babel.spoiled.org [212.84.234.227]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UEXHV05678 for ; Mon, 30 Jul 2001 07:33:17 -0700 Received: (qmail 3737 invoked by uid 8); 30 Jul 2001 14:33:16 -0000 From: thomas graichen Reply-To: thomas graichen X-Newsgroups: spoiled.linux.sgi.xfs Subject: Re: Backup ACLs Date: Mon, 30 Jul 2001 08:16:30 +0200 Organization: spoiled dot org Lines: 25 Distribution: local Message-ID: References: <10107301020.ZM246528@wobbly.melbourne.sgi.com> Reply-To: thomas graichen X-Complaints-To: newsmaster@spoiled.org User-Agent: tin/1.4.4-20000803 ("Vet for the Insane") (UNIX) (Linux/2.4.7-pre8-xfs (i686)) To: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk "Nathan Scott" wrote: > Now that I think back, I remember Thomas came across this > problem on ppc a while back also, I don't think it was ever > resolved. What you've started doing above is probably the > simplest way to go - I'd suggest keep doing that. You'll > need to find the exact point in the code where the kernel > is deciding to return EFAULT ... from a quick peek, I see > there's one case in getname() - perhaps thats it. > Once you find the offending line, you'll need to understand > the conditional statement just prior to EFAULT being set; > eg. use a few more printks before the condition to see what > the values of the variables involved are and which part of > it is evaluating to true (and then, hopefully, why). yes - i was the onwhich had this problem once - i also tried the printk's but ended up at very strange things ... maybe i should try again ... t -- thomas graichen ... perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away. --- antoine de saint-exupery From owner-linux-xfs@oss.sgi.com Mon Jul 30 11:08:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UI8DG08941 for linux-xfs-outgoing; Mon, 30 Jul 2001 11:08:13 -0700 Received: from smtpstore.strencom.net ([217.75.0.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UI89V08922 for ; Mon, 30 Jul 2001 11:08:09 -0700 Received: from raptor.raidtec.ie (unknown [217.75.2.18]) by smtpstore.strencom.net (Postfix) with SMTP id 9A304638A0 for ; Mon, 30 Jul 2001 19:08:56 +0100 (IST) Received: from no.name.available by raptor.raidtec.ie via smtpd (for [217.75.0.68]) with SMTP; 30 Jul 2001 19:18:25 UT Subject: RE: Backup ACLs MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 30 Jul 2001 19:06:47 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 content-class: urn:content-classes:message Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Backup ACLs Thread-Index: AcEVt7LLPpx0rXjkRCyYzrWKkwerGgAAQ8iwAKHk+QAAOGLBQA== From: "Juer Lee" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6UI8AV08923 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >-----Original Message----- >From: Juer Lee >Sent: 29 July 2001 16:59 >To: linux-xfs@oss.sgi.com >Subject: RE: Backup ACLs > > >> >> >>>hi, >>> >>>On Jul 26, 10:28am, Juer Lee wrote: >>>> Subject: RE: Backup ACLs >>>> >>>> Nathan, >>>> >>>> Oh, yes, I can not find the references in >>>> /usr/include/xfs/platform_defs.h. But I am sure that I appplied >>>> xfs-progs-devel-1.1.3.0-ppc, it seemed that in this version >>>O_DIRECT is >>>> still not defined. >>> >>>Oh, just noticed this - sorry, thought you wrote "1.3.1". >>>You will need a more recent version of xfsprogs-devel - >>>if you are using the CVS tree, the xfsprogs/doc/INSTALL >>>document will help you get there. >>> >>>Having a more recent xfsprogs-devel will also fix this >>>next problem... >>> >>>> /export/xfsdump-1.0.11/dump/util.c:137: undefined reference to >>>> `IRIX_MKDEV' >>> >>>Hope this helps. >>> >>>cheers. >>> >>>-- >>>Nathan >> >> >>Thanks. >>I fixed that. >>I am now adding sys_attrctl, after I success, I'll share my happiness >>with all who are helping me. :) >> >>Juer >> >> > >News: > > >It is my first time to look into the kernel code :( >There are some errors when I run 'attr -l juer' --- ' attr_list: Bad >address'. It seemed that the error is occured when calling function >__user_walk(...) ( sys_attrctl --> user_path_walk ) > >int __user_walk(const char *name, unsigned flags, struct nameidata *nd) >{ > char *tmp; > int err; > > tmp = getname(name); > err = PTR_ERR(tmp); > > /* Debug */ > if( err == -14) > printk("Attr Debug 1: Bad address!\n"); > > if (!IS_ERR(tmp)) { > err = 0; > if (path_init(tmp, flags, nd)) > err = path_walk(tmp, nd); > > /* Debug */ > if( err == -14) > printk("Attr Debug 1: Bad address!\n"); > > putname(tmp); > } > return err; >} > >I saw the error message "Attr Debug 1:Bad address!" when I ran that >command. >Did any expert :) meet this similar problem? > >Juer > > Good news! Try to update the function attrctl(...) like this, it seemed that it works :) I will explain it in detail tomorrow. return syscall(SYS__attrctl, obj, type,ops,count) before updating, it is : return syscall(SYS__attrctl, *(long *)&obj, type,ops,count) Juer Lee From owner-linux-xfs@oss.sgi.com Mon Jul 30 12:25:39 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UJPdp10488 for linux-xfs-outgoing; Mon, 30 Jul 2001 12:25:39 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UJPbV10469 for ; Mon, 30 Jul 2001 12:25:37 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id 5CC581AB10 for ; Mon, 30 Jul 2001 15:25:36 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 1E9E4729; Mon, 30 Jul 2001 15:25:36 -0400 (EDT) Date: Mon, 30 Jul 2001 15:25:36 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic Message-ID: <20010730152535.D5581@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B64842E.2D60EE37@gmx.de> User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Sun, Jul 29, 2001 at 11:46:22PM +0200, Martin Stricker wrote: > Andrew Klaassen wrote: > > A number of times, questions have popped up on this list > > about building really large arrays of IDE disks. Does > > anybody know if there's a list dedicated to that? > > Anybody else think there might be enough interest to make > > something like this a go? > I'm interested, I'm looking forward to do this myself in the > near future. So... if I decide to get something like this set up... anybody know who might be willing to host such a mailing list? (Any chance that oss.sgi.com would? Or the ReiserFS folks?) Andrew Klaassen From owner-linux-xfs@oss.sgi.com Mon Jul 30 12:59:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UJx9f11079 for linux-xfs-outgoing; Mon, 30 Jul 2001 12:59:09 -0700 Received: from homer.mkintl.com (cloven-ext.nks.net [216.139.204.130]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UJx7V11060 for ; Mon, 30 Jul 2001 12:59:07 -0700 Received: from illusionary.com (two.nks.net [192.168.1.22]) by homer.mkintl.com (8.9.3/8.9.3) with ESMTP id PAA30780 for ; Mon, 30 Jul 2001 15:59:01 -0400 Message-ID: <3B65BC85.280D74F5@illusionary.com> Date: Mon, 30 Jul 2001 15:59:01 -0400 From: Derek Glidden X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.7-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> <20010730152535.D5581@dkp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andrew Klaassen wrote: > > On Sun, Jul 29, 2001 at 11:46:22PM +0200, > Martin Stricker wrote: > > > Andrew Klaassen wrote: > > > > A number of times, questions have popped up on this list > > > about building really large arrays of IDE disks. Does > > > anybody know if there's a list dedicated to that? > > > > Anybody else think there might be enough interest to make > > > something like this a go? > > > I'm interested, I'm looking forward to do this myself in the > > near future. > > So... if I decide to get something like this set up... anybody > know who might be willing to host such a mailing list? > > (Any chance that oss.sgi.com would? Or the ReiserFS folks?) Since this is something I'm interested in too, and have a colocated machine capable of running mailman, I'd be willing to give it a shot as long as it doesn't turn into too high a traffic list, and nobody would mind a fairly inexperienced listmgr running the list. (But to clarify: I'm definitely not an inexperienced sysadmin, I've just never run a big list before.) -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- #!/usr/bin/perl -w $_='while(read+STDIN,$_,2048){$a=29;$b=73;$c=142;$t=255;@t=map {$_%16or$t^=$c^=($m=(11,10,116,100,11,122,20,100)[$_/16%8])&110; $t^=(72,@z=(64,72,$a^=12*($_%16-2?0:$m&17)),$b^=$_%64?12:0,@z) [$_%8]}(16..271);if((@a=unx"C*",$_)[20]&48){$h=5;$_=unxb24,join "",@b=map{xB8,unxb8,chr($_^$a[--$h+84])}@ARGV;s/...$/1$&/;$d= unxV,xb25,$_;$e=256|(ord$b[4])<<9|ord$b[3];$d=$d>>8^($f=$t&($d >>12^$d>>4^$d^$d/8))<<17,$e=$e>>8^($t&($g=($q=$e>>14&7^$e)^$q* 8^$q<<6))<<9,$_=$t[$_]^(($h>>=8)+=$f+(~$g&$t))for@a[128..$#a]} print+x"C*",@a}';s/x/pack+/g;eval usage: qrpff 153 2 8 105 225 < /mnt/dvd/VOB_FILENAME \ | extract_mpeg2 | mpeg2dec - http://www.eff.org/ http://www.opendvd.org/ http://www.cs.cmu.edu/~dst/DeCSS/Gallery/ From owner-linux-xfs@oss.sgi.com Mon Jul 30 13:12:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UKCE611610 for linux-xfs-outgoing; Mon, 30 Jul 2001 13:12:14 -0700 Received: from picard.skynet.be (picard.skynet.be [195.238.3.131]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UKCCV11591 for ; Mon, 30 Jul 2001 13:12:12 -0700 Received: from skynet.be (adsl-45604.turboline.skynet.be [217.136.50.36]) by picard.skynet.be (8.11.2/8.11.2/Skynet-OUT-2.11) with ESMTP id f6UKBvY03555; Mon, 30 Jul 2001 22:11:57 +0200 (MET DST) (envelope-from ) Message-ID: <3B65BE5E.B708970E@skynet.be> Date: Mon, 30 Jul 2001 22:06:54 +0200 From: kris buggenhout X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.4-xfs i686) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Klaassen , "linux-xfs@oss.sgi.com" Subject: Re: Everyone's favorite offtopic topic References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> <20010730152535.D5581@dkp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andrew Klaassen wrote: > On Sun, Jul 29, 2001 at 11:46:22PM +0200, > Martin Stricker wrote: > > > Andrew Klaassen wrote: > > > > A number of times, questions have popped up on this list > > > about building really large arrays of IDE disks. Does > > > anybody know if there's a list dedicated to that? > > > > Anybody else think there might be enough interest to make > > > something like this a go? > > > I'm interested, I'm looking forward to do this myself in the > > near future. > > So... if I decide to get something like this set up... anybody > know who might be willing to host such a mailing list? > > (Any chance that oss.sgi.com would? Or the ReiserFS folks?) > > Andrew Klaassen check out raidzone they have implemented NAS and SAN solutions based on ATA100 raid systems.. with a dedicated controller board.... From owner-linux-xfs@oss.sgi.com Mon Jul 30 13:19:08 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UKJ8x11785 for linux-xfs-outgoing; Mon, 30 Jul 2001 13:19:08 -0700 Received: from epithumia.math.uh.edu (IDENT:root@epithumia.math.uh.edu [129.7.128.2]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UKJ7V11766 for ; Mon, 30 Jul 2001 13:19:07 -0700 Received: (from tibbs@localhost) by epithumia.math.uh.edu (8.11.0/8.11.1) id f6UKJ4L01143; Mon, 30 Jul 2001 15:19:04 -0500 To: Andrew Klaassen Cc: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> <20010730152535.D5581@dkp.com> From: Jason L Tibbitts III Date: 30 Jul 2001 15:19:04 -0500 In-Reply-To: Andrew Klaassen's message of "Mon, 30 Jul 2001 15:25:36 -0400" Message-ID: Lines: 16 User-Agent: Gnus/5.0807 (Gnus v5.8.7) Emacs/20.7 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk >>>>> "AK" == Andrew Klaassen writes: AK> So... if I decide to get something like this set up... anybody know who AK> might be willing to host such a mailing list? If you still need a list server, I've created linux-ide-arrays@lists.math.uh.edu. It's run by Majordomo; you can join the normal way or by sending an empty message to: - - linux-ide-arrays-subscribe@lists.math.uh.edu -- Jason L Tibbitts III - tibbs@math.uh.edu - 713/743-3486 - 660PGH - 94 PC800 System Manager: University of Houston Department of Mathematics And your voice is vast and achromatic. But still so precious... From owner-linux-xfs@oss.sgi.com Mon Jul 30 13:36:14 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UKaEq12048 for linux-xfs-outgoing; Mon, 30 Jul 2001 13:36:14 -0700 Received: from mail.dkp.com ([204.191.16.3]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UKaCV12029 for ; Mon, 30 Jul 2001 13:36:12 -0700 Received: from ranma.dkp.com (ranma.dkp.com [205.150.40.12]) by mail.dkp.com (Postfix) with ESMTP id F2E2B1AB10 for ; Mon, 30 Jul 2001 16:36:11 -0400 (EDT) Received: by ranma.dkp.com (Postfix, from userid 168) id 99EFC729; Mon, 30 Jul 2001 16:36:11 -0400 (EDT) Date: Mon, 30 Jul 2001 16:36:11 -0400 From: Andrew Klaassen To: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic Message-ID: <20010730163611.E5581@dkp.com> Mail-Followup-To: linux-xfs@oss.sgi.com References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> <20010730152535.D5581@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 30, 2001 at 03:19:04PM -0500, Jason L Tibbitts III wrote: > If you still need a list server, I've created > linux-ide-arrays@lists.math.uh.edu. It's run by Majordomo; > you can join the normal way or by sending an empty message to: > > - > - > linux-ide-arrays-subscribe@lists.math.uh.edu Well... there we go. Sounds good. Thanks. Think we should let the Reiser people know, too? Anybody else? Andrew Klaassen From owner-linux-xfs@oss.sgi.com Mon Jul 30 14:33:33 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6ULXXQ13052 for linux-xfs-outgoing; Mon, 30 Jul 2001 14:33:33 -0700 Received: from smtp8.xs4all.nl (smtp8.xs4all.nl [194.109.127.134]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6ULXUV13033 for ; Mon, 30 Jul 2001 14:33:31 -0700 Received: from auto-nb1.xs4all.nl (qn-212-58-163-110.quicknet.nl [212.58.163.110]) by smtp8.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA11696; Mon, 30 Jul 2001 23:33:26 +0200 (CEST) Message-Id: <4.3.2.7.2.20010730232959.034539b8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 30 Jul 2001 23:33:05 +0200 To: Andrew Klaassen , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Everyone's favorite offtopic topic Cc: reiserfs-list@namesys.com In-Reply-To: <20010730163611.E5581@dkp.com> References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> <20010730152535.D5581@dkp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk At 16:36 30-7-2001 -0400, Andrew Klaassen wrote: >On Mon, Jul 30, 2001 at 03:19:04PM -0500, >Jason L Tibbitts III wrote: > > > If you still need a list server, I've created > > linux-ide-arrays@lists.math.uh.edu. It's run by Majordomo; > > you can join the normal way or by sending an empty message to: > > > > - > > - > > linux-ide-arrays-subscribe@lists.math.uh.edu > >Well... there we go. Sounds good. Thanks. > >Think we should let the Reiser people know, too? Anybody else? That is often used in the same setups as well. I'll cc their list. Note to the reiserfs folks: The following list is for discussion about IDE raid arrays and around a TB in size :-) Using software raid or hardware raid or anything else deemed neccesary for the cause. Cheers -- Seth Every program has two purposes one for which it was written and another for which it wasn't I use the last kind. From owner-linux-xfs@oss.sgi.com Mon Jul 30 15:27:58 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6UMRw514076 for linux-xfs-outgoing; Mon, 30 Jul 2001 15:27:58 -0700 Received: from mail.gmx.net (sproxy.gmx.net [194.221.183.20]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6UMRuV14057 for ; Mon, 30 Jul 2001 15:27:56 -0700 Received: (qmail 15324 invoked by uid 0); 30 Jul 2001 22:27:48 -0000 Received: from b1e4e.pppool.de (HELO gmx.de) (213.7.30.78) by mail.gmx.net (mail02) with SMTP; 30 Jul 2001 22:27:48 -0000 Message-ID: <3B65DF5B.83EA2F8D@gmx.de> Date: Tue, 31 Jul 2001 00:27:39 +0200 From: Martin Stricker Organization: http://martin-stricker.de/ http://www.surfo.net/ http://www.masterportal24.com/cgi-bin/YaBB.cgi X-Mailer: Mozilla 4.77 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Everyone's favorite offtopic topic References: <20010728231625.C19907@dkp.com> <3B64842E.2D60EE37@gmx.de> <20010730152535.D5581@dkp.com> <20010730163611.E5581@dkp.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Andrew Klaassen wrote: > Think we should let the Reiser people know, too? Anybody else? I'll post it to the mailing list for Red Hat Linux 7.1 and the Red Hat ext3fs-Mailing list. Sometimes this topic came up there, too. Best regards, Martin Stricker -- Homepage: http://www.martin-stricker.de/ Registered Linux user #210635: http://counter.li.org/ From owner-linux-xfs@oss.sgi.com Mon Jul 30 17:17:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6V0H3U17188 for linux-xfs-outgoing; Mon, 30 Jul 2001 17:17:03 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6V0H0V17169 for ; Mon, 30 Jul 2001 17:17:00 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id CAA11028; Tue, 31 Jul 2001 02:15:51 +0200 Date: Tue, 31 Jul 2001 02:15:47 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Tad Dolphay Cc: mjacob@feral.com, Christian Chip , linux-xfs@oss.sgi.com, linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net Subject: Re: Busy inodes after umount Message-ID: <20010731021546.A7750@vestdata.no> References: <20010719165758.D50024-100000@wonky.feral.com> <200107200038.TAA40153@fsgi158.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <200107200038.TAA40153@fsgi158.americas.sgi.com>; from Tad Dolphay on Thu, Jul 19, 2001 at 07:38:15PM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Thu, Jul 19, 2001 at 07:38:15PM -0500, Tad Dolphay wrote: > > > I've now been able to reproduce: > > > > > > * make a filesystem > > > * mount it > > > * export it (nfs) > > > * mount on remote machine > > > * lock file (fcntl) > > > * unexport > > > * unmount > > > > > > Then you get the VFS message about self-destruct. Tested with both ext2 > > > and xfs. > > > > > > The lock is still present in /proc/locks after the umount. > > > > > > With ext2 I can remount the filesystem successfully, but with XFS I get > > > the message about duplicate UUIDs and the mount failes. I believe this is a totally > > > different problem from the one you were experiencing. (and blockdev doesn't help for me) > > > > > > I suppose this is a generic kernel bug? > > I know there was a fix for a "Busy inodes after unmount" problem in > 2.4.6-pre3. Here's an excerpt from a posting to the NFS mailing list > from Neil Brown: > > -------------Included message----------------------- > Previously anonymous dentries were hashed (though with no name, the > hash was pretty meaningless). This meant that they would hang around > after the last reference was dropped. This was actually fairly > pointless as they would never get referenced again, and caused a real > problem as umount wouldn't discard them and so you got the message > printk("VFS: Busy inodes after unmount. " > "Self-destruct in 5 seconds. Have a nice day...\n"); > > In 2.4.6-pre3 I stopped hashing those dentries so now when the last > reference is dropped, the dentry is freed. So now there will never be > more anonymous dentries than there are active nfsd threads. > ---------------end included message------------------- I just tested with 2.4.7, and the problem remains. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 30 17:17:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6V0HZ217288 for linux-xfs-outgoing; Mon, 30 Jul 2001 17:17:35 -0700 Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6V0HWV17258 for ; Mon, 30 Jul 2001 17:17:32 -0700 Received: (from ragnark@localhost) by stine.vestdata.no (8.9.3/8.9.3) id CAA11047; Tue, 31 Jul 2001 02:17:27 +0200 Date: Tue, 31 Jul 2001 02:17:25 +0200 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Luc Lalonde Cc: linux-xfs@oss.sgi.com Subject: Re: kernel deadlock; xfs Message-ID: <20010731021725.B7750@vestdata.no> References: <20010718195723.A24237@vestdata.no> <3B55D226.714EFEE4@giref.ulaval.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: <3B55D226.714EFEE4@giref.ulaval.ca>; from Luc Lalonde on Wed, Jul 18, 2001 at 02:15:02PM -0400 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, Jul 18, 2001 at 02:15:02PM -0400, Luc Lalonde wrote: > Hello Ragnar, > > You wouldn't per chance be using an Adaptec-39160 or Adaptec-29160? If > so try the aic7xxx_old instead of the aic7xxx. > > I've had the same problems and no lockups since I started using the old > drivers. > (I'm still crossing my fingers though ;-) It turned out it was neither the adaptec or XFS - it was the gigabit ethernet card. Thanks for all the tips though. -- Ragnar Kjorstad Big Storage From owner-linux-xfs@oss.sgi.com Mon Jul 30 17:31:13 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6V0VDQ17966 for linux-xfs-outgoing; Mon, 30 Jul 2001 17:31:13 -0700 Received: from rj.corp.sgi.com (rj.SGI.COM [204.94.215.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6V0VBV17947 for ; Mon, 30 Jul 2001 17:31:12 -0700 Received: from boing.melbourne.sgi.com (boing.melbourne.sgi.com [134.14.55.141]) by rj.corp.sgi.com (8.11.4/8.11.4/linux-outbound_gateway-1.0) with ESMTP id f6V0Z5U04905 for ; Mon, 30 Jul 2001 17:35:06 -0700 Received: (from tes@localhost) by boing.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA63342; Tue, 31 Jul 2001 10:29:47 +1000 (EST) Date: Tue, 31 Jul 2001 10:29:47 +1000 From: Timothy Shimmin To: Steve Lord Cc: Mark Bradbury , linux-xfs@oss.sgi.com Subject: Re: Where is ACL information stored with XFS? Message-ID: <20010731102946.I62222@boing.melbourne.sgi.com> References: <200107301353.f6UDrc004046@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0us In-Reply-To: <200107301353.f6UDrc004046@jen.americas.sgi.com>; from lord@sgi.com on Mon, Jul 30, 2001 at 08:53:38AM -0500 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Mon, Jul 30, 2001 at 08:53:38AM -0500, Steve Lord wrote: > > Yes I would also like to know > > dump and restore are OK for small systems > > but what about a 1 TB system > > SGI have been using this filesystem for a while so there must be a > > better solution. > > > > We have just had to restore 100GB of files after a (2)discs failed on us > > this was with a ext2 filesystem > > > > If we had XSF and samba 2.2.1a how would we restore the ACL's ? > > > > > > > > Other folks have already said use xfsdump/xfsrestore if you want your > ACLs backed up, and that Amanda does support them. I am not actually > sure if any of the other backup products which run on xfs have the > ability to back them up. And if they do, SGI has little influence with > folks like Legato when it comes to getting features into their > products! > I asked someone at SGI involved with backup s/ware, and was told that Networker 6.0 does NOT backup extended attributes on XFS. --Tim From owner-linux-xfs@oss.sgi.com Mon Jul 30 17:39:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6V0d3c18736 for linux-xfs-outgoing; Mon, 30 Jul 2001 17:39:03 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6V0d1V18711 for ; Mon, 30 Jul 2001 17:39:01 -0700 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via SMTP id RAA02880 for ; Mon, 30 Jul 2001 17:38:48 -0700 (PDT) mail_from (nathans@wobbly.melbourne.sgi.com) 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 KAA22128; Tue, 31 Jul 2001 10:37:43 +1000 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA33218; Tue, 31 Jul 2001 10:37:42 +1000 (AEST) From: "Nathan Scott" Message-Id: <10107311037.ZM249164@wobbly.melbourne.sgi.com> Date: Tue, 31 Jul 2001 10:37:40 +1000 In-Reply-To: Chris Bednar "Houston Summer -> duplicate inode range" (Jul 28, 8:27pm) References: X-Mailer: Z-Mail (3.2.3 08feb96 MediaMail) To: Chris Bednar , linux-xfs@oss.sgi.com Subject: Re: Houston Summer -> duplicate inode range Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk hi Chris, On Jul 28, 8:27pm, Chris Bednar wrote: > Subject: Houston Summer -> duplicate inode range > > Today, I had a disk overheat, which led to severe corruption > on an XFS volume. At the end of quite a lot of output from xfs_repair, > ... I'm guessing this is going to be incredibly difficult to reproduce and its also in an area of the xfs_repair code that I've never had to go look before ... so, is there any chance you could gzip up the filesystem blk device contents and put the image somewhere so I could download it? [if so, send me a pointer privately] This assumes you still have this filesystem, of course, and that you trust me with whatever data remains on it. It would be a _very_ important debugging aid though, and this problem might go undiagnosed without it. thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Jul 30 17:56:42 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6V0ugR19682 for linux-xfs-outgoing; Mon, 30 Jul 2001 17:56:42 -0700 Received: from tux.mkp.net (tux.mkp.net [130.225.60.11]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6V0ueV19657 for ; Mon, 30 Jul 2001 17:56:40 -0700 Received: from tux.mkp.net ([130.225.60.11] helo=jcb.mkp.net) by tux.mkp.net with esmtp (Exim 3.31 #1) id 15RNpu-0005Om-00; Tue, 31 Jul 2001 02:56:39 +0200 Received: (from mkp@localhost) by jcb.mkp.net (8.11.0/8.9.3) id f6V0u8f15690; Mon, 30 Jul 2001 20:56:08 -0400 X-Authentication-Warning: jcb.mkp.net: mkp set sender to mkp@mkp.net using -f To: linux-xfs@oss.sgi.com, axp-list@redhat.com Subject: SGI XFS Red Hat 7.1 Installer for Alpha From: "Martin K. Petersen" Organization: mkp.net Date: 30 Jul 2001 20:56:08 -0400 Message-ID: Lines: 57 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Copyleft) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk I am happy to announce the first prerelease of the SGI XFS Red Hat 7.1 Installer for the Alpha architecture. This code is derived from the ia32-based installer we released as part of XFS 1.0.1. The Alpha installer is not supported by SGI, however. Use it at your own risk. Oh, and this is a prerelease. This means that it may potentially corrupt your data. Tread cautiously. In order to install you need the Red Hat 7.1 Alpha Disc 1 and 2 media. Get them from your local Red Hat mirror or buy the boxed set. The Alpha XFS installer ISO is available here: ftp://oss.sgi.com/projects/xfs/download/Release-1.0.1/unsupported/ Alpha-specific caveats: - Neither aboot nor MILO support XFS. Consequently, /boot must reside on an ext2 filesystem. The installer will attempt to enforce this. - aboot install fails silently on my Miata. This happens with a clean RH7.1 too. If your machine can't boot after a successful install, boot in rescue mode using the XFS install CD and do something like: # cd /mnt/sysimage/boot # swriteboot /dev/sda1 bootlx -f3 (Assuming your system disk is sda, that you have enough room at the beginning of the disk, and that you are using aboot.) - I haven't tried installing using MILO. Let me know how it goes. - Alphas use 8KB pages whereas PCs use 4K. Currently XFS on Linux requires that the filesystem block size matches the memory page size. I.e. you can't move XFS filesystems created on an Alpha to a PC and vice versa. For non-Alpha caveats and information about XFS in general please read: http://oss.sgi.com/projects/xfs/ Enjoy! PS. Go find 'em bugs before I have to return my Alpha to its rightful owner. -- Martin K. Petersen, Principal Linux Consultant, Linuxcare, Inc. mkp@linuxcare.com, http://www.linuxcare.com/ SGI XFS for Linux Developer, http://oss.sgi.com/projects/xfs/ From owner-linux-xfs@oss.sgi.com Mon Jul 30 19:19:06 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6V2J6g22280 for linux-xfs-outgoing; Mon, 30 Jul 2001 19:19:06 -0700 Received: from sgi.com (sgi.SGI.COM [192.48.153.1]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6V2J4V22259 for ; Mon, 30 Jul 2001 19:19:04 -0700 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.175]) by sgi.com (980327.SGI.8.8.8-aspam/980304.SGI-aspam: SGI does not authorize the use of its proprietary systems or networks for unsolicited or bulk email from the Internet.) via ESMTP id TAA06933 for ; Mon, 30 Jul 2001 19:18:45 -0700 (PDT) mail_from (kaos@sherman.melbourne.sgi.com) Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.9.3/8.9.3) id MAA07379; Tue, 31 Jul 2001 12:19:01 +1000 Date: Tue, 31 Jul 2001 12:19:01 +1000 From: Keith Owens Message-Id: <200107310219.MAA07379@sherman.melbourne.sgi.com> Subject: TAKE - Sync XFS to 2.4.8-pre3 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Sync to 2.4.8-pre3 Date: Mon Jul 30 19:17:26 PDT 2001 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:99817a linux/drivers/usb/storage/jumpshot.c - 1.1 linux/drivers/usb/storage/jumpshot.h - 1.1 linux/drivers/usb/storage/isd200.h - 1.1 linux/drivers/usb/storage/isd200.c - 1.1 linux/drivers/usb/storage/datafab.h - 1.1 linux/drivers/usb/storage/datafab.c - 1.1 linux/mm/vmscan.c - 1.64 linux/mm/swap.c - 1.10 linux/mm/memory.c - 1.53 linux/include/linux/swap.h - 1.32 linux/include/asm-i386/softirq.h - 1.11 linux/Makefile - 1.108 linux/drivers/net/starfire.c - 1.18 linux/drivers/ieee1394/pcilynx.c - 1.11 linux/drivers/ieee1394/ieee1394_core.c - 1.10 linux/drivers/ieee1394/ohci1394.c - 1.14 linux/drivers/ieee1394/ieee1394_syms.c - 1.8 linux/drivers/ieee1394/hosts.c - 1.7 linux/drivers/usb/storage/usb.h - 1.8 linux/drivers/usb/storage/usb.c - 1.10 linux/drivers/usb/storage/transport.h - 1.6 linux/drivers/usb/storage/transport.c - 1.9 linux/drivers/usb/storage/scsiglue.c - 1.10 linux/drivers/usb/storage/protocol.h - 1.3 linux/drivers/usb/storage/protocol.c - 1.5 linux/drivers/usb/storage/debug.c - 1.5 linux/drivers/usb/storage/Makefile - 1.5 linux/drivers/ieee1394/video1394.c - 1.7 linux/drivers/usb/storage/shuttle_usbat.c - 1.5 linux/drivers/usb/storage/sddr09.c - 1.6 linux/drivers/usb/storage/unusual_devs.h - 1.3 linux/drivers/ieee1394/nodemgr.c - 1.2 linux/drivers/ieee1394/nodemgr.h - 1.2 From owner-linux-xfs@oss.sgi.com Tue Jul 31 05:59:20 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VCxKi25502 for linux-xfs-outgoing; Tue, 31 Jul 2001 05:59:20 -0700 Received: from merlin.giref.ulaval.ca (postfix@merlin.giref.ulaval.ca [132.203.7.100]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VCxIV25482 for ; Tue, 31 Jul 2001 05:59:18 -0700 Received: from roederer.giref.ulaval.ca (roederer.giref.ulaval.ca [132.203.7.24]) by merlin.giref.ulaval.ca (Postfix) with ESMTP id 94386F2C6; Tue, 31 Jul 2001 08:59:17 -0400 (EDT) Date: Tue, 31 Jul 2001 08:59:17 -0400 (EDT) From: Luc Lalonde To: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= Cc: linux-xfs@oss.sgi.com Subject: Re: kernel deadlock; xfs In-Reply-To: <20010731021725.B7750@vestdata.no> 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 f6VCxIV25484 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello Ragnar, I've come to the same conclusion as you. I'm trying the Intel driver for my network card instead of the one that comes with the kernel. There's a lot of complaints on the "eepro" mailing list about the Intel Pro 10/100+ cards. Lots of workarounds for lock-ups...some issues still unresolved. I'm hoping that the driver Intel put out resolves these issues. Otherwise I'm disabling the onboard NIC and I'm going to put another card in there. Can someone suggest a rock-solid 10/100 NIC to use? I'm thinking of getting a tulip or a 3com card. Cheers, Luc. On Tue, 31 Jul 2001, [iso-8859-1] Ragnar Kjørstad wrote: > On Wed, Jul 18, 2001 at 02:15:02PM -0400, Luc Lalonde wrote: > > Hello Ragnar, > > > > You wouldn't per chance be using an Adaptec-39160 or Adaptec-29160? If > > so try the aic7xxx_old instead of the aic7xxx. > > > > I've had the same problems and no lockups since I started using the old > > drivers. > > (I'm still crossing my fingers though ;-) > > > It turned out it was neither the adaptec or XFS - it was the gigabit > ethernet card. Thanks for all the tips though. > > > > -- > Ragnar Kjorstad > Big Storage > > From owner-linux-xfs@oss.sgi.com Tue Jul 31 06:09:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VD9Za26246 for linux-xfs-outgoing; Tue, 31 Jul 2001 06:09:35 -0700 Received: from electre.pasteur.fr (electre.pasteur.fr [157.99.64.120]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VD9WV26223 for ; Tue, 31 Jul 2001 06:09:32 -0700 Received: from pasteur.fr (xiii.bis.pasteur.fr [157.99.90.14]) by electre.pasteur.fr (8.11.4/8.11.4) with ESMTP id f6VD93P299551; Tue, 31 Jul 2001 15:09:03 +0200 (CEST) Message-ID: <3B66ADEF.66F50DAB@pasteur.fr> Date: Tue, 31 Jul 2001 15:09:03 +0200 From: Tru Huynh Organization: Institut Pasteur X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.4.3-SGI_XFS_1.0.1 i686) X-Accept-Language: en MIME-Version: 1.0 To: Luc Lalonde CC: Ragnar =?iso-8859-1?Q?Kj=F8rstad?= , linux-xfs@oss.sgi.com Subject: Re: kernel deadlock; xfs References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Luc Lalonde wrote: > > Hello Ragnar, > > I'm hoping that the driver Intel put out resolves these issues. Otherwise > I'm disabling the onboard NIC and I'm going to put another card in > there. I had to go for this solution for my dual onboard intel card :( YMMV, but I have been happy with the 3com 3c905x cards (knock on wood). sincerely, Tru -- Dr Tru Huynh | Bioinformatique Structurale mailto:tru@pasteur.fr | tel/fax +33 1 45 68 87 37/19 Institut Pasteur, 25-28 rue du Docteur Roux, 75724 Paris CEDEX 15 France From owner-linux-xfs@oss.sgi.com Tue Jul 31 11:05:09 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VI59705633 for linux-xfs-outgoing; Tue, 31 Jul 2001 11:05:09 -0700 Received: from neutral.verbum.org (postfix@dhcp233054.columbus.rr.com [204.210.233.54]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VI55V05613 for ; Tue, 31 Jul 2001 11:05:05 -0700 Received: from space-ghost.verbum.org (space-ghost.verbum.org [192.168.5.90]) by neutral.verbum.org (Postfix (Debian/GNU)) with ESMTP id EB667F5B7 for ; Tue, 31 Jul 2001 14:01:36 -0400 (EDT) Received: by space-ghost.verbum.org (Postfix (Debian/GNU), from userid 1000) id 195B96213A5; Tue, 31 Jul 2001 03:12:07 -0400 (EDT) To: linux-xfs@oss.sgi.com Subject: Re: bad clientid? References: <200107301400.f6UE0J104068@jen.americas.sgi.com> X-Attribution: Colin X-Face: %'w-_>8Mj2_'=;I$myE#]G"'D>x3CY_rk,K06:mXFUvWy>;3I"BW3_-MAiUby{O(mn"wV@m dd`)Vk[27^^Sa Date: Tue, 31 Jul 2001 03:12:06 -0400 In-Reply-To: <200107301400.f6UE0J104068@jen.americas.sgi.com> (Steve Lord's message of "Mon, 30 Jul 2001 09:00:19 -0500") Message-ID: <87itg9k1x5.church.of.emacs@space-ghost.verbum.org> Lines: 19 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Steve Lord writes: > My guess is you are running a CVS or patch based kernel from > sometime after the 1.0.1 release. There was a period of a couple of > weeks where raid5 had this problem. Yeah, I forgot to mention the kernel version. Your guess is correct, I applied an older 2.4.7 patch. > If you update to the latest CVS (2.4.8-pre2 now) or get the latest > 2.4.7 patch from the ftp site: > > ftp://oss.sgi.com/projects/xfs/download/patches/patch-2.4.7-xfs-2001-07-27.bz2 > > This should be fixed. What you did was the correct workaround for > the kernel you have. Yep, it appears to work now, and has been holding up quite well under my stress tests. Thanks! From owner-linux-xfs@oss.sgi.com Tue Jul 31 11:51:03 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VIp3i06793 for linux-xfs-outgoing; Tue, 31 Jul 2001 11:51:03 -0700 Received: from ADSL-Bergs.RZ.RWTH-Aachen.DE (adsl-bergs.rz.RWTH-Aachen.DE [137.226.80.218]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VIp0V06770 for ; Tue, 31 Jul 2001 11:51:01 -0700 Received: from [192.168.1.2] (helo=ralf) by ADSL-Bergs.RZ.RWTH-Aachen.DE with smtp (Exim 3.12 #1) id 15RebW-0007RT-00 for linux-xfs@oss.sgi.com; Tue, 31 Jul 2001 20:50:54 +0200 From: "Ralf G. R. Bergs" To: "Linux XFS Mailing List" Date: Tue, 31 Jul 2001 20:50:53 +0200 Reply-To: "Ralf G. R. Bergs" X-Mailer: PMMail 2000 Professional (2.20.2200) For Windows 2000 (5.0.2195;2) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: xfs_force_shutdown with linux-2.4.6-xfs-07052001? Message-Id: Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hi there, I'm running Debian/GNU Linux (unstable) on a PC equipped with a Pentium III-450 (Katmai), 192 M of RAM, and a RAID (easyRAID II) with 165 GB hooked to an Adaptec AIC-7881U SCSI host adapter. The kernel I'm using is 2.4.6 with XFS patch "linux-2.4.6-xfs-07052001" applied. Soon after I've written some gigs of data I'm seeing the following in /var/log/messages: Jul 31 14:06:43 server kernel: xfs_force_shutdown(sd(8,5),0x1) called from line 1013 of file xfs_trans.c. Return address = 0xcc8e71b3 Jul 31 14:06:43 server kernel: I/O Error Detected. Shutting down filesystem: sd (8,5) Jul 31 14:06:43 server kernel: Please umount the filesystem, and rectify the problem(s) Do you have any idea what could be causing this? Or any hints how to further investigate the problem? Thanks, Ralf -- Sign the EU petition against SPAM: L I N U X .~. http://www.politik-digital.de/spam/ The Choice /V\ of a GNU /( )\ Generation ^^-^^ From owner-linux-xfs@oss.sgi.com Tue Jul 31 13:16:34 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VKGYd10298 for linux-xfs-outgoing; Tue, 31 Jul 2001 13:16:34 -0700 Received: from smtp3.cern.ch (smtp3.cern.ch [137.138.131.164]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VKGVV10279 for ; Tue, 31 Jul 2001 13:16:31 -0700 Received: from lxplus039.cern.ch (IDENT:root@lxplus039.cern.ch [137.138.161.91]) by smtp3.cern.ch (8.11.3/8.11.3) with ESMTP id f6VKGOw17828 for ; Tue, 31 Jul 2001 22:16:24 +0200 (MET DST) Received: (from fuji@localhost) by lxplus039.cern.ch (8.9.3/8.9.3) id WAA16549 for linux-xfs@oss.sgi.com; Tue, 31 Jul 2001 22:16:24 +0200 Date: Tue, 31 Jul 2001 22:16:24 +0200 From: Peter.Kelemen@cern.ch To: linux-xfs@oss.sgi.com Subject: Re: xfs_force_shutdown with linux-2.4.6-xfs-07052001? Message-ID: <20010731221624.A7007@lxplus039.cern.ch> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.19i 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-MIME-Autoconverted: from 8bit to quoted-printable by smtp3.cern.ch id f6VKGOw17828 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id f6VKGWV10280 Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk * Ralf G. R. Bergs (rabe@rwth-aachen.de) [20010731 20:50]: > Jul 31 14:06:43 server kernel: xfs_force_shutdown(sd(8,5),0x1) called from > line 1013 of file xfs_trans.c. Return address = 0xcc8e71b3 > Jul 31 14:06:43 server kernel: I/O Error Detected. Shutting down filesystem: > sd (8,5) > Jul 31 14:06:43 server kernel: Please umount the filesystem, and rectify the > problem(s) > Do you have any idea what could be causing this? Or any hints > how to further investigate the problem? Linux nope 2.4.7-xfs #1 Sun Jul 22 14:59:11 CEST 2001 i686 unknown Not much, but I experienced a similar event with very light load today, running CVS 2.4.7 as of 2001/07/22: Jul 31 12:52:51 nope kernel: xfs_force_shutdown(lvm(58,0),0x1) called from line 4069 of file xfs_bmap.c. Return address = 0xc01863ab Jul 31 12:52:51 nope kernel: Fatal error on root filesystem Jul 31 12:52:51 nope kernel: I/O Error Detected. Shutting down filesystem: lvm(58,0) Jul 31 12:52:51 nope kernel: Please umount the filesystem, and rectify the problem(s) I upgraded couple of Debian packages while running X, then this error occured, forcing me to reboot. xfs_repair complained about inodes not belonging to any files. Some of my shared libs turned into collection of binary zeroes, my /etc/inetd.conf got linked (!) to /lib/libkdb.so.1 (and yes, I have *never* had a file with that name -- weird?!). Otherwise everything seems to be intact. Sorry for not being able to provide more exact debugging terms and not preserving the damaged filesystem, but I had to come around this as it actually was my workstation's root filesystem. Peter PS: egcs-1.1.2 and all that funky approved-by-Steve devel stuff. -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen Péter / \ / \ Peter.Kelemen@cern.ch .+' `+...+' `+...+' `+...+' `+...+' From owner-linux-xfs@oss.sgi.com Tue Jul 31 13:59:44 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VKxiq11384 for linux-xfs-outgoing; Tue, 31 Jul 2001 13:59:44 -0700 Received: from kaperfahrt.nebelschwaden.de ([62.16.151.47]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VKxeV11365 for ; Tue, 31 Jul 2001 13:59:40 -0700 Received: from nazgul.nebelschwaden.de (nazgul.nebelschwaden.de [172.16.36.10]) by kaperfahrt.nebelschwaden.de (Postfix) with ESMTP id 3B236CF7 for ; Tue, 31 Jul 2001 22:23:32 +0200 (CEST) Received: from nebelschwaden.de (nazgul.nebelschwaden.de [172.16.36.10]) by nazgul.nebelschwaden.de (Postfix) with ESMTP id C52EE5836 for ; Tue, 31 Jul 2001 22:23:48 +0200 (CEST) Message-ID: <3B6713D4.9040904@nebelschwaden.de> Date: Tue, 31 Jul 2001 22:23:48 +0200 From: List Account Reply-To: listac@nebelschwaden.de User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.2) Gecko/20010729 X-Accept-Language: de, en-us MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Cannot compile xfsdump References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Hello, the configure script fails when looking for libxfs.h. I have compiled and installed the xfsprogs, but those did for what reason ever not install the header files - not even after recompiling. The xfslib.h is only existent in the xfsprogrogs source/include directory. Also, specifying this dir as includedir or oldincludedir to the xfsdump configure script does not help. Neither does a plain copy into /usr/include (my --prefix for all xfs related software) or into xfsdump/include. What went wrong ? I am running a Slack8 box which does not support rpm or deb (and I would like to keep it that way. Not to flame, just for Info. ) Regards Klaus root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# find /usr -name libxfs.h /usr/src/xfs/xfsdump-1.0.9/include/xfs/libxfs.h /usr/src/xfs/xfsdump-1.0.9/include/libxfs.h /usr/src/xfs/xfsdump-1.0.9/xfs/libxfs.h /usr/src/xfs/xfsprogs-1.2.7/include/libxfs.h /usr/include/libxfs.h root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# ---------------------- root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# ./configure --prefix=/usr checking for gcc... gcc checking for C compiler default output... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for executable suffix... checking for object suffix... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for make... /usr/bin/make checking for ld... /usr/bin/ld checking for tar... /bin/tar checking for gzip... /bin/gzip checking for rpm... /bin/rpm checking for makedepend... /bin/true checking whether ln -s works... yes checking for awk... /usr/bin/awk checking for sed... /usr/bin/sed checking for echo... /usr/bin/echo checking how to run the C preprocessor... gcc -E checking for uuid/uuid.h... yes checking for uuid_generate in -luuid... yes checking for xfs/libxfs.h... no FATAL ERROR: could not find a valid XFS library header. Install either the xfsprogs-devel (rpm) or the xfslibs-dev (deb) package. root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# From owner-linux-xfs@oss.sgi.com Tue Jul 31 14:15:18 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f6VLFIY12061 for linux-xfs-outgoing; Tue, 31 Jul 2001 14:15:18 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f6VLFFV12042 for ; Tue, 31 Jul 2001 14:15:15 -0700 Received: from zeus-fddi.americas.sgi.com (zeus-fddi.americas.sgi.com [128.162.8.103]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id OAA03107 for ; Tue, 31 Jul 2001 14:13:02 -0700 (PDT) mail_from (lord@sgi.com) Received: from daisy-e185.americas.sgi.com (daisy.americas.sgi.com [128.162.185.214]) by zeus-fddi.americas.sgi.com (8.9.3/americas-smart-nospam1.1) with ESMTP id QAA2575922; Tue, 31 Jul 2001 16:13:58 -0500 (CDT) Received: from jen.americas.sgi.com (IDENT:root@jen.americas.sgi.com [128.162.187.49]) by daisy-e185.americas.sgi.com (SGI-8.9.3/SGI-server-1.7) with ESMTP id QAA78764; Tue, 31 Jul 2001 16:13:58 -0500 (CDT) Received: from jen.americas.sgi.com by jen.americas.sgi.com (8.11.2/SGI-client-1.7) via ESMTP id f6VLEmT01740; Tue, 31 Jul 2001 16:14:48 -0500 Message-Id: <200107312114.f6VLEmT01740@jen.americas.sgi.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: listac@nebelschwaden.de cc: linux-xfs@oss.sgi.com Subject: Re: Cannot compile xfsdump In-Reply-To: Message from List Account of "Tue, 31 Jul 2001 22:23:48 +0200." <3B6713D4.9040904@nebelschwaden.de> Date: Tue, 31 Jul 2001 16:14:48 -0500 From: Steve Lord Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk > Hello, > > > the configure script fails when looking for libxfs.h. I have compiled > and installed the xfsprogs, but those did for what reason ever not > install the header files - not even after recompiling. The xfslib.h is > only existent in the xfsprogrogs source/include directory. Also, > specifying this dir as includedir or oldincludedir to the xfsdump > configure script does not help. Neither does a plain copy into > /usr/include (my --prefix for all xfs related software) or into > xfsdump/include. You need to run make install_dev to get header files installed Steve > > What went wrong ? I am running a Slack8 box which does not support rpm > or deb (and I would like to keep it that way. Not to flame, just for Info. ) > > Regards > > Klaus > > > root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# find /usr -name libxfs.h > /usr/src/xfs/xfsdump-1.0.9/include/xfs/libxfs.h > /usr/src/xfs/xfsdump-1.0.9/include/libxfs.h > /usr/src/xfs/xfsdump-1.0.9/xfs/libxfs.h > /usr/src/xfs/xfsprogs-1.2.7/include/libxfs.h > /usr/include/libxfs.h > root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# > > ---------------------- > > root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# ./configure --prefix=/usr > checking for gcc... gcc > checking for C compiler default output... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for executable suffix... > checking for object suffix... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for make... /usr/bin/make > checking for ld... /usr/bin/ld > checking for tar... /bin/tar > checking for gzip... /bin/gzip > checking for rpm... /bin/rpm > checking for makedepend... /bin/true > checking whether ln -s works... yes > checking for awk... /usr/bin/awk > checking for sed... /usr/bin/sed > checking for echo... /usr/bin/echo > checking how to run the C preprocessor... gcc -E > checking for uuid/uuid.h... yes > checking for uuid_generate in -luuid... yes > checking for xfs/libxfs.h... no > > FATAL ERROR: could not find a valid XFS library header. > Install either the xfsprogs-devel (rpm) or the xfslibs-dev (deb) package. > root@kaperfahrt:/usr/src/xfs/xfsdump-1.0.9# From owner-linux-xfs@oss.sgi.com Tue Jul 31 21:10:46 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f714Akk20888 for linux-xfs-outgoing; Tue, 31 Jul 2001 21:10:46 -0700 Received: from pneumatic-tube.sgi.com (pneumatic-tube.sgi.com [204.94.214.22]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f714AiV20868 for ; Tue, 31 Jul 2001 21:10:44 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by pneumatic-tube.sgi.com (980327.SGI.8.8.8-aspam/980310.SGI-aspam) via ESMTP id VAA07414 for ; Tue, 31 Jul 2001 21:08:30 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA15685 for linux-xfs@oss.sgi.com; Wed, 1 Aug 2001 14:08:51 +1000 (EST) Date: Wed, 1 Aug 2001 14:08:51 +1000 (EST) From: Nathan Scott Message-Id: <200108010408.OAA15685@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - doc Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk [Steve, to answer your question - yes, these options do work; I think Martin wrote this code, a long time ago now]. Date: Tue Jul 31 21:06:06 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99931a cmd/xfsprogs/man/man8/xfs_repair.8 - 1.2 cmd/xfsprogs/man/man8/xfs_logprint.8 - 1.2 cmd/xfsprogs/man/man8/xfs_db.8 - 1.3 - add description of the -l option for external logs. From owner-linux-xfs@oss.sgi.com Tue Jul 31 21:32:35 2001 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f714WZh21636 for linux-xfs-outgoing; Tue, 31 Jul 2001 21:32:35 -0700 Received: from deliverator.sgi.com (deliverator.sgi.com [204.94.214.10]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f714WWV21617 for ; Tue, 31 Jul 2001 21:32:32 -0700 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id VAA04924 for ; Tue, 31 Jul 2001 21:32:19 -0700 (PDT) mail_from (nathans@snort.melbourne.sgi.com) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id OAA50479 for linux-xfs@oss.sgi.com; Wed, 1 Aug 2001 14:31:14 +1000 (EST) Date: Wed, 1 Aug 2001 14:31:14 +1000 (EST) From: Nathan Scott Message-Id: <200108010431.OAA50479@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - ia64 user build Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk If you came across this build failure (from cvs code only) when building the XFS userspace on an ia64 box, it is now fixed... /usr/bin/libtool --mode=link gcc -rpath /lib -version-info 0:1:0 -o libdm.la dmapi_lib.lo dm_attr.lo dm_bulkattr.lo dm_config.lo dm_dmattr.lo dm_event.lo dm_handle.lo dm_handle2path.lo dm_hole.lo dm_mountinfo.lo dm_region.lo dm_right.lo dm_rdwr.lo dm_session.lo -lhandle rm -fr .libs/libdm.la .libs/libdm.* .libs/libdm.* gcc -shared dmapi_lib.lo dm_attr.lo dm_bulkattr.lo dm_config.lo dm_dmattr.lo dm_event.lo dm_handle.lo dm_handle2path.lo dm_hole.lo dm_mountinfo.lo dm_region.lo dm_right.lo dm_rdwr.lo dm_session.lo -lhandle -lc -Wl,-soname -Wl,libdm.so.0 -o .libs/libdm.so.0.0.1 /usr/lib/gcc-lib/ia64-redhat-linux/2.96-ia64-000717/../../../../ia64-redhat-linux/bin/ld: handle.o: @gprel relocation against dynamic symbol fdhash_head /usr/lib/gcc-lib/ia64-redhat-linux/2.96-ia64-000717/../../../../ia64-redhat-linux/bin/ld: handle.o: @gprel relocation against dynamic symbol fdhash_head /usr/lib/gcc-lib/ia64-redhat-linux/2.96-ia64-000717/../../../../ia64-redhat-linux/bin/ld: handle.o: @gprel relocation against dynamic symbol fdhash_head collect2: ld returned 1 exit status make[2]: *** [libdm.la] Error 1 make[1]: *** [default] Error 2 make[1]: Leaving directory `/build4/nathans/linux-xfs/cmd/dmapi' cheers. Date: Tue Jul 31 21:25:55 PDT 2001 Workarea: snort.melbourne.sgi.com:/diskb/build4/nathans/linux-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:99932a cmd/xfsdump/dump/content.c - 1.7 - 64bit compiler warnings - fix two uninited variables (two bugs). cmd/xfsdump/common/util.c - 1.4 - 64bit compiler warnings - ensure args match the syscall interface. cmd/xfsdump/common/Makefile - 1.5 - common/content.c is not used at all, nuke it. cmd/xfsdump/fsr/xfs_fsr.c - 1.7 - 64bit compiler warnings - fix an uninited variable (benign). cmd/acl/include/builddefs.in - 1.11 cmd/attr/include/builddefs.in - 1.11 cmd/dmapi/include/builddefs.in - 1.12 cmd/xfsdump/include/builddefs.in - 1.11 cmd/xfsprogs/include/builddefs.in - 1.16 - add -fno-strict-aliasing for shared lib objects, rationalise multiple dirt entries and cosmetic change in libtool macros ordering. cmd/xfsprogs/doc/CHANGES - 1.30 - add an entry for these few minor items. cmd/xfsprogs/rtcp/xfs_rtcp.c - 1.2 - 64bit compiler warnings fixup (printf args). cmd/xfsprogs/libdisk/drivers.c - 1.3 cmd/xfsprogs/libdisk/lvm.h - 1.2 cmd/xfsprogs/libdisk/liblvm.h - 1.2 cmd/xfsprogs/libdisk/md.c - 1.3 cmd/xfsprogs/mkfs/fstyp.c - 1.3 - 64bit compiler warnings fixup (headers).