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) > >