From owner-linux-xfs@oss.sgi.com Sun Dec 1 11:29:17 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Dec 2002 11:29:20 -0800 (PST) Received: from antares.cedar.buffalo.edu (antares.cedar.Buffalo.EDU [128.205.33.2]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB1JTHuR005564 for ; Sun, 1 Dec 2002 11:29:17 -0800 Received: (qmail 2838 invoked from network); 1 Dec 2002 19:32:13 -0000 Received: from zaurak.cedar.buffalo.edu (128.205.33.110) by antares.cedar.buffalo.edu with SMTP; 1 Dec 2002 19:32:13 -0000 Received: from zaurak.cedar.Buffalo.EDU (localhost.localdomain [127.0.0.1]) by zaurak.cedar.Buffalo.EDU (8.12.5/8.12.5) with ESMTP id gB1JWC4p029485; Sun, 1 Dec 2002 14:32:12 -0500 Received: (from ajay@localhost) by zaurak.cedar.Buffalo.EDU (8.12.5/8.12.5/Submit) id gB1JWCPd029483; Sun, 1 Dec 2002 14:32:12 -0500 Date: Sun, 1 Dec 2002 14:32:12 -0500 From: Ajay Shekhawat To: Keith Owens Cc: linux-xfs@oss.sgi.com Subject: Re: XFS trouble (!) Message-ID: <20021201193211.GD18501@zaurak.cedar.Buffalo.EDU> References: <20021130180602.GC18501@zaurak.cedar.Buffalo.EDU> <3030.1038699885@ocs3.intra.ocs.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3030.1038699885@ocs3.intra.ocs.com.au> User-Agent: Mutt/1.4i Organization: Center for Document Analysis and Recognition X-OfficePhone: +1 (716)-645-6164 ext. 101 X-Fax-Number: +1 (716)-645-6176 X-archive-position: 1909 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ajay@cedar.buffalo.edu Precedence: bulk X-list: linux-xfs On Sun, Dec 01, 2002 at 10:44:45AM +1100, Keith Owens wrote: > The 2.4.19 XFS patches have been respun several times, when did you > download? The XFS version message at boot time will tell you, all bug > reports should include that message. > > >(well, "was" would be the operative word now that 2.4.20 is out :-/) > > There are also split patches against 2.4.20, they are the equivalent > of the XFS CVS tree as of 2002-11-29_01:21_UTC. I downloaded all of the stuff yesterday. The status now is: the filesystem is mounted and looks OK. The kernel is 2.4.19, with the 1.2pre3 patches (from the FTP site). Dec 1 14:23:33 xXxXx kernel: SGI XFS SGI XFS 1.2pre3 with ACLs, no debug enabled Ajay From owner-linux-xfs@oss.sgi.com Sun Dec 1 15:19:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Dec 2002 15:19:09 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB1NJ5uR009141 for ; Sun, 1 Dec 2002 15:19:05 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gB1NQlkq007872 for ; Sun, 1 Dec 2002 17:26:48 -0600 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 KAA19169; Mon, 2 Dec 2002 10:20:39 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA17893; Mon, 2 Dec 2002 10:20:38 +1100 (EST) Date: Mon, 2 Dec 2002 10:20:38 +1100 From: Nathan Scott To: Ajay Shekhawat Cc: linux-xfs@oss.sgi.com Subject: Re: XFS trouble (!) Message-ID: <20021202102038.B536043@wobbly.melbourne.sgi.com> References: <20021130000059.GA18501@zaurak.cedar.Buffalo.EDU> <20021130135526.A526752@wobbly.melbourne.sgi.com> <20021130035148.GB18501@zaurak.cedar.Buffalo.EDU> <20021130154031.B526752@wobbly.melbourne.sgi.com> <20021130180602.GC18501@zaurak.cedar.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20021130180602.GC18501@zaurak.cedar.Buffalo.EDU>; from ajay@cedar.buffalo.edu on Sat, Nov 30, 2002 at 01:06:02PM -0500 X-archive-position: 1910 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs On Sat, Nov 30, 2002 at 01:06:02PM -0500, Ajay Shekhawat wrote: > I gave the command > uuid > in xfs_db, and it was able to mount the filesystem. Everything _appears_ > to be there, though it is difficult to check quickly. > > So what are my options now: should I do a 'xfs_check' again? Since your last run didn't seem to report any problems and the log is no longer corrupt, I would say there is unlikely to be any benefit from running it again (esp. since it takes so long for you). > Should I migrate to the latest CVS branch? It is a production machine, > though, and I'm not sure if the latest bleeding edge release is > the way to go (if something happens, a lot of sharp soon-to-be-bleeding > edges will head my way). I would stick with the 1.2[pre] tree for a production machine, there are still known issues in the development CVS tree which are not present in 1.2. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Sun Dec 1 15:24:31 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Dec 2002 15:24:33 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB1NOVuR009569 for ; Sun, 1 Dec 2002 15:24:31 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB1LRNG8006549 for ; Sun, 1 Dec 2002 13:27:27 -0800 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA99851 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 10:26:02 +1100 (EST) Date: Mon, 2 Dec 2002 10:26:02 +1100 (EST) From: Nathan Scott Message-Id: <200212012326.KAA99851@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - acl/attr I18N updates (final) X-archive-position: 1911 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Updates to acl/attr I18N (final). Sync up dmapi scripts with the I18N aware versions - dmapi doesn't have any strings, so this is just keeping scripts in sync. Date: Sun Dec 1 15:24:42 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:134052a cmd/acl/chacl/chacl.c - 1.18 cmd/attr/attr/attr.c - 1.11 cmd/attr/setfattr/setfattr.c - 1.12 cmd/attr/getfattr/getfattr.c - 1.18 cmd/acl/setfacl/setfacl.c - 1.7 cmd/acl/getfacl/getfacl.c - 1.8 - Updates to acl/attr I18N (final). cmd/dmapi/configure.in - 1.17 cmd/dmapi/include/buildrules - 1.9 cmd/dmapi/include/builddefs.in - 1.18 cmd/dmapi/include/buildmacros - 1.5 - Sync up dmapi scripts with the I18N aware versions - dmapi doesn't have any strings (just a library), so this is just keeping scripts in sync. From owner-linux-xfs@oss.sgi.com Sun Dec 1 16:02:38 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Dec 2002 16:02:42 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB202cuR010270 for ; Sun, 1 Dec 2002 16:02:38 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB20AKkq008250 for ; Sun, 1 Dec 2002 18:10:21 -0600 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id LAA08758; Mon, 2 Dec 2002 11:04:12 +1100 (EST) Date: Mon, 2 Dec 2002 11:04:12 +1100 (EST) From: Nathan Scott Message-Id: <200212020004.LAA08758@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com, agruen@suse.de Subject: TAKE - attr I18N changes X-archive-position: 1912 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Date: Sun Dec 1 16:03:07 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:134053a cmd/attr/po/de.po - 1.1 cmd/attr/doc/CHANGES - 1.35 cmd/attr/po/Makefile - 1.2 - German translation for attr package from Andreas. From owner-linux-xfs@oss.sgi.com Sun Dec 1 17:21:45 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Dec 2002 17:21:50 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB21LjuR011095 for ; Sun, 1 Dec 2002 17:21:45 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB21TPkq008928 for ; Sun, 1 Dec 2002 19:29:28 -0600 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id MAA23965 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 12:23:17 +1100 (EST) Date: Mon, 2 Dec 2002 12:23:17 +1100 (EST) From: Nathan Scott Message-Id: <200212020123.MAA23965@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - cleanup X-archive-position: 1913 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Cleanup after initially investigating unwritten extents. Date: Sun Dec 1 17:18:39 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:134059a linux/fs/xfs/xfs_buf.h - 1.99 - Make the XFS_BUF_ISUNINITIAL macro correct, and no longer refering to pagebuf flags which no longer exist. linux/fs/xfs/xfs_buf_item.c - 1.134 - Uncomment an assert which now makes sense with other fixes. linux/fs/xfs/xfs_bmap_btree.h - 1.55 - Make the ISUNWRITTEN macro a bit more useful. linux/fs/xfs/xfs_bmap.c - 1.297 - Set bmv_oflags flag BMV_OF_PREALLOC when the extent is unwritten (was IRIX mod irix6.5m:irix:120255a originally, not yet merged?). Cleanup code formatting a bit here, it was all over the show. linux/fs/xfs/linux/xfs_lrw.c - 1.176 - Fix several incorrect comments. linux/fs/xfs/linux/xfs_ioctl.c - 1.85 - Make several routines static, make declarations consistent. linux/fs/xfs/pagebuf/Makefile - 1.17 linux/fs/xfs/pagebuf/page_buf.c - 1.81 - Rationalise tracking debugging, tidy tracing debugging. linux/fs/xfs/linux/xfs_aops.c - 1.14 - Remove an incorrect assert relating to mapping unwritten extents. Fix several typos in comments, make comments & code fit in 80 columns. linux/fs/xfs/linux/xfs_iomap.c - 1.2 - Fix several incorrect comments, make declarations consistent. From owner-linux-xfs@oss.sgi.com Sun Dec 1 22:04:11 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 01 Dec 2002 22:04:15 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB264BuR015396 for ; Sun, 1 Dec 2002 22:04:11 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB2479G8020736 for ; Sun, 1 Dec 2002 20:07:09 -0800 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id RAA51112 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 17:05:48 +1100 (EST) Date: Mon, 2 Dec 2002 17:05:48 +1100 (EST) From: Nathan Scott Message-Id: <200212020605.RAA51112@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - sector size updates X-archive-position: 1914 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Sector size updates - macros for calculating address/size of sector-sized data structures (sb,agf,agi,agfl) are now sector size aware. Cleaned up the early mount code dealing with log devices and logsectsize. Should be it for awhile in terms of kernel changes related to sector sizes (the log is on the TODO list, somewhere). cheers. Date: Sun Dec 1 21:34:30 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:134064a linux/fs/xfs/xfs_trans.h - 1.115 - Remove an unused function prototype from xfs_trans.h. Date: Sun Dec 1 21:53:26 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:134065a linux/fs/xfs/xfsidbg.c - 1.211 - Report the sectorsize too from the mount structure. linux/fs/xfs/xfs_vfsops.c - 1.400 linux/fs/xfs/xfs_mount.c - 1.314 - Cleaned up the early mount code dealing with log devices and the log sector size. linux/fs/xfs/xfs_ialloc.c - 1.162 linux/fs/xfs/xfs_macros.c - 1.47 linux/fs/xfs/xfs_ag.h - 1.46 linux/fs/xfs/xfs_sb.h - 1.55 linux/fs/xfs/xfs_rtalloc.c - 1.84 linux/fs/xfs/xfs_ialloc_btree.c - 1.71 linux/fs/xfs/xfs_log_recover.c - 1.252 linux/fs/xfs/xfs_inode.c - 1.360 linux/fs/xfs/xfs_alloc.c - 1.162 linux/fs/xfs/xfs_fsops.c - 1.88 - Macros for calculating address/size of sector-sized data structures (sb,agf,agi,agfl) are now sector size aware. linux/fs/xfs/xfs_alloc.h - 1.53 - Remove an extern declaration of a now-static function. linux/fs/xfs/linux/xfs_super.c - 1.230 - Don't unilaterally set the sector size to 512 bytes, remove some unneeded code. linux/fs/xfs/xfs_fs.h - 1.7 - Add a geometry flag for non-512-byte sector sizes. From owner-linux-xfs@oss.sgi.com Mon Dec 2 00:30:07 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 00:30:21 -0800 (PST) Received: from banna (fb170065.ot.FreeBit.NE.JP [61.203.170.65]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB28SZuR019677 for ; Mon, 2 Dec 2002 00:29:15 -0800 Received: from D ([192.168.0.2]) by banna (8.9.3+3.2W/3.7W) with SMTP id RAA16282; Mon, 2 Dec 2002 17:30:35 +0900 Message-Id: <200212020830.RAA16282@banna> From: =?iso-2022-jp?B?aG1haWwxMTExanA=?= To: =?iso-2022-jp?B?MDA1?=@banna.sgi.com Reply-To: hmail1111jp@yahoo.co.jp Date: Mon, 02 Dec 2002 17:28:54 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoRUU7UiVhITwlazktOXAbKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 1915 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hmail1111jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望しない方はここへ (必ず本文にあなたのメールアドレスのみをお書き下さい） fmail9999jp@yahoo.co.jp メールアドレスをご記入してください。 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218 =============================================================== 問題商品ばかり集めましたので、消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Mon Dec 2 04:14:23 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 04:14:25 -0800 (PST) Received: from mail.tvol.net (pr-66-150-46-254.wgate.com [66.150.46.254]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB2CEMuR030443 for ; Mon, 2 Dec 2002 04:14:22 -0800 Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 41A6ZLKQ; Mon, 2 Dec 2002 07:17:42 -0500 Received: from wgate.com (sinz.eng.tvol.net [127.0.0.1]) by sinz.eng.tvol.net (8.12.5/8.12.5) with ESMTP id gB2CGcGT018863 for ; Mon, 2 Dec 2002 07:16:38 -0500 Message-ID: <3DEB4F26.5010608@wgate.com> Date: Mon, 02 Dec 2002 07:16:38 -0500 From: Michael Sinz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021111 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfs_check exit code? References: <20021129063350.35728.qmail@web15205.mail.bjs.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 1916 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: msinz@wgate.com Precedence: bulk X-list: linux-xfs I have been, it seems wrongly, assuming that if xfs_check finds a problem on the disk that the exit code is non-zero. (And, conversely, if all is well, that the exit code is zero) Anyway, I have, this weekend, had some problems with one of my machines. (I have not fully diagnosed the problem so I don't want to point fingers at XFS yet). During the recovery process, I used my /boot recovery script and, while xfs_check found errors, the exit code of xfs_check was zero. This prevented auto-recovery from working. Is the exit code part of the defined API for xfs_check? Could it be part of the defined behavior? For now I will need to check if xfs_check has any output - which is almost as good as long as that behavior is "defined" -- Michael Sinz -- Director, Systems Engineering -- Worldgate Communications A master's secrets are only as good as the master's ability to explain them to others. From owner-linux-xfs@oss.sgi.com Mon Dec 2 10:24:32 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 10:24:34 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB2IOWuR012434 for ; Mon, 2 Dec 2002 10:24:32 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB2IWMkq022007 for ; Mon, 2 Dec 2002 12:32:23 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA12083 for ; Mon, 2 Dec 2002 11:55:10 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA00116 for ; Mon, 2 Dec 2002 12:27:22 -0600 (CST) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id gB2IRLx05624; Mon, 2 Dec 2002 12:27:21 -0600 Message-Id: <200212021827.gB2IRLx05624@jen.americas.sgi.com> Date: Mon, 2 Dec 2002 12:27:21 -0600 Subject: TAKE - performance work for O_SYNC writes To: linux-xfs@oss.sgi.com X-archive-position: 1917 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs for synchronous transactions, allow the in core log buffer to wait around in active state for as long as possible. This allows us to coalesce several transactions into one buffer and reduce the disk traffic. Date: Mon Dec 2 10:26:49 PST 2002 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:134077a linux/fs/xfs/xfs_log.c - 1.262 - Introduce a new sync variable in the iclog structure to sync between the last log write and the next one in the case of sync transactions forcing iclogs out to disk early. linux/fs/xfs/xfs_log_priv.h - 1.85 - new sync variable in the iclog structure From owner-linux-xfs@oss.sgi.com Mon Dec 2 11:21:18 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 11:21:20 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB2JLIuR013767 for ; Mon, 2 Dec 2002 11:21:18 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB2ISOKp001125 for ; Mon, 2 Dec 2002 10:28:24 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA27662 for ; Mon, 2 Dec 2002 12:51:43 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA04238 for ; Mon, 2 Dec 2002 13:24:06 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB32cEF30432 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 21:38:14 -0500 Resent-Message-Id: <200212030238.gB32cEF30432@taclab54.munich.sgi.com> Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA00784 for ; Mon, 2 Dec 2002 13:15:48 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB32TtE30416 for hch@sgi.com; Mon, 2 Dec 2002 21:29:55 -0500 Date: Mon, 2 Dec 2002 21:29:55 -0500 From: Christoph Hellwig Message-Id: <200212030229.gB32TtE30416@taclab54.munich.sgi.com> Subject: TAKE - remove unused function pagebuf_queue_task Resent-From: hch@sgi.com Resent-Date: Mon, 2 Dec 2002 21:38:14 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1918 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Mon Dec 2 11:14:50 PST 2002 Workarea: taclab54.munich.sgi.com:/home/hch/repo/slinx/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:134086a linux/fs/xfs/pagebuf/page_buf.c - 1.82 linux/fs/xfs/pagebuf/page_buf.h - 1.50 - remove unused function pagebuf_queue_task From owner-linux-xfs@oss.sgi.com Mon Dec 2 12:28:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 12:28:49 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB2KShuR014841 for ; Mon, 2 Dec 2002 12:28:43 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB2KaYkq024545 for ; Mon, 2 Dec 2002 14:36:34 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id NAA21238 for ; Mon, 2 Dec 2002 13:59:04 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA94491 for ; Mon, 2 Dec 2002 14:31:39 -0600 (CST) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id gB2KVcs13886; Mon, 2 Dec 2002 14:31:38 -0600 Message-Id: <200212022031.gB2KVcs13886@jen.americas.sgi.com> Date: Mon, 2 Dec 2002 14:31:38 -0600 Subject: TAKE - fix bug 193, oops in fsstress on extended attributes X-archive-position: 1919 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs when logging attribute extents, use the correct size for the allocation! This got introduced back on Oct 10th when in memory extents where changed to be host byte ordered. An incorrect size was used on an allocation. Date: Mon Dec 2 12:28:05 PST 2002 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.4 The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:134098a linux/fs/xfs/xfs_inode_item.c - 1.109 - use attribute fork size in allocation rather than data fork size From owner-linux-xfs@oss.sgi.com Mon Dec 2 12:44:09 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 12:44:14 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2Ki9uR015379 for ; Mon, 2 Dec 2002 12:44:09 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2Ki8D7015378 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 12:44:08 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2KhwuV015352 for ; Mon, 2 Dec 2002 12:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2KUvhB015276; Mon, 2 Dec 2002 12:30:57 -0800 Date: Mon, 2 Dec 2002 12:30:57 -0800 Message-Id: <200212022030.gB2KUvhB015276@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 193] when tested with fsstress in scsi, the process is locked. X-Bugzilla-Reason: AssignedTo X-archive-position: 1920 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=193 lord@sgi.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED ------- Additional Comments From lord@sgi.com 2002-12-02 12:30 ------- Fixed by mod 2.4.x-xfs:slinx:134098a a bad size on a memory allocation. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Mon Dec 2 14:14:00 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 14:14:06 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2ME0uR016648 for ; Mon, 2 Dec 2002 14:14:00 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2ME079016647 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 14:14:00 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2MDwuT016633 for ; Mon, 2 Dec 2002 14:13:58 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2MA3Vp016589; Mon, 2 Dec 2002 14:10:03 -0800 Date: Mon, 2 Dec 2002 14:10:03 -0800 Message-Id: <200212022210.gB2MA3Vp016589@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 200] New: xfs_check should set the exit code to non-zero if the filesystem does not check out X-Bugzilla-Reason: AssignedTo X-archive-position: 1921 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=200 Summary: xfs_check should set the exit code to non-zero if the filesystem does not check out Product: Linux XFS Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: Medium Component: xfsprogs AssignedTo: xfs-master@oss.sgi.com ReportedBy: michael.sinz@sinz.org Using the current (from CVS as of 11/30) xfs_check, a filesystem that has "errors" does not cause xfs_check to exit with an exit code greater than 0. I had assumed that this was the behavior as it would allow for automatic recovery scripts to run. If the exit code is not supposed to signal a need for xfs_repair, is there a way to programmatically get that signal? (Or an option to xfs_check that says "run xfs_repair if needed") ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Mon Dec 2 14:44:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 14:44:13 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2Mi2uR017452 for ; Mon, 2 Dec 2002 14:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2Mi20S017450 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 14:44:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2MhwuZ017419 for ; Mon, 2 Dec 2002 14:43:58 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2MHiYJ017028; Mon, 2 Dec 2002 14:17:44 -0800 Date: Mon, 2 Dec 2002 14:17:44 -0800 Message-Id: <200212022217.gB2MHiYJ017028@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 200] xfs_check should set the exit code to non-zero if the filesystem does not check out X-Bugzilla-Reason: AssignedTo X-archive-position: 1923 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=200 msinz@wgate.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msinz@wgate.com ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Mon Dec 2 14:44:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 14:44:08 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2Mi2uR017451 for ; Mon, 2 Dec 2002 14:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2Mi2RQ017449 for linux-xfs@oss.sgi.com; Mon, 2 Dec 2002 14:44:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB2MhwuX017419 for ; Mon, 2 Dec 2002 14:43:58 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB2MHAIR016942; Mon, 2 Dec 2002 14:17:10 -0800 Date: Mon, 2 Dec 2002 14:17:10 -0800 Message-Id: <200212022217.gB2MHAIR016942@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 200] xfs_check should set the exit code to non-zero if the filesystem does not check out X-Bugzilla-Reason: AssignedTo X-archive-position: 1922 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=200 ------- Additional Comments From msinz@wgate.com 2002-12-02 14:17 ------- Created an attachment (id=54) --> (http://oss.sgi.com/bugzilla/attachment.cgi?id=54&action=view) Example recovery tool The attachment is an example recovery tool installer (and the recovery scripts) that use (or, would use) the exit/return code from xfs_check. Note that these scripts already deal with the mount/log replay issue and checking for XFS filesystems. If the filesystem is so far gone that the checks fail then the manual recovery is needed but for many cases that I have run into during the XFS development period, the automatic mechanism works as long as xfs_check gets me the exit code correctly. (I look for "any output" from xfs_check to determin if there was a problem in the "production" version) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Mon Dec 2 18:46:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 18:47:05 -0800 (PST) Received: from dynamic.galis.org (ool-4350143e.dyn.optonline.net [67.80.20.62]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB32kwuR020098 for ; Mon, 2 Dec 2002 18:46:58 -0800 Received: (qmail 29342 invoked by uid 1010); 3 Dec 2002 02:52:41 -0000 Date: Mon, 2 Dec 2002 21:52:41 -0500 From: George Georgalis To: linux-xfs@oss.sgi.com Subject: Re: TAKE - fix bug 193, oops in fsstress on extended attributes Message-ID: <20021203025241.GO25947@trot.local> References: <200212022031.gB2KVcs13886@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200212022031.gB2KVcs13886@jen.americas.sgi.com> User-Agent: Mutt/1.3.28i X-archive-position: 1924 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgw@galis.org Precedence: bulk X-list: linux-xfs On Mon, Dec 02, 2002 at 02:31:38PM -0600, Steve Lord wrote: >when logging attribute extents, use the correct size for the allocation! >This got introduced back on Oct 10th when in memory extents where >changed to be host byte ordered. An incorrect size was used on an allocation. Just curious, what sort of bugs might surface on a heavily stressed disk that would not otherwise come up? I know this is a very general question, sorry, I'm only looking for comments; nothing comes to mind, short of a 'data is faster than the disk' scenario, but even then wouldn't the problem be handed to memory/virtual memory? // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:george@galis.org Multimedia, DB, DNS and Metrics. http://www.galis.org/george From owner-linux-xfs@oss.sgi.com Mon Dec 2 20:38:52 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 02 Dec 2002 20:38:58 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB34cquR022788 for ; Mon, 2 Dec 2002 20:38:52 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gB32fsG8002275 for ; Mon, 2 Dec 2002 18:41:55 -0800 Received: from frodo.melbourne.sgi.com (frodo.melbourne.sgi.com [134.14.55.153]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id PAA01030; Tue, 3 Dec 2002 15:40:31 +1100 Received: from frodo.melbourne.sgi.com (nathans@localhost [127.0.0.1]) by frodo.melbourne.sgi.com (8.12.6/8.12.6/Debian-8) with ESMTP id gB34eAv1008292; Tue, 3 Dec 2002 15:40:10 +1100 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.6/8.12.6/Debian-8) id gB34e9pw008290; Tue, 3 Dec 2002 15:40:09 +1100 Date: Tue, 3 Dec 2002 15:40:09 +1100 From: Nathan Scott To: Michael Sinz Cc: linux-xfs@oss.sgi.com Subject: Re: xfs_check exit code? Message-ID: <20021203044009.GD6391@frodo.melbourne.sgi.com> References: <20021129063350.35728.qmail@web15205.mail.bjs.yahoo.com> <3DEB4F26.5010608@wgate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DEB4F26.5010608@wgate.com> User-Agent: Mutt/1.4i X-archive-position: 1925 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs On Mon, Dec 02, 2002 at 07:16:38AM -0500, Michael Sinz wrote: > I have been, it seems wrongly, assuming that if xfs_check finds > a problem on the disk that the exit code is non-zero. (And, > conversely, if all is well, that the exit code is zero) > > Anyway, I have, this weekend, had some problems with one of my machines. > (I have not fully diagnosed the problem so I don't want to point fingers > at XFS yet). During the recovery process, I used my /boot recovery > script and, while xfs_check found errors, the exit code of xfs_check > was zero. This prevented auto-recovery from working. > > Is the exit code part of the defined API for xfs_check? Could it be > part of the defined behavior? > > For now I will need to check if xfs_check has any output - which is > almost as good as long as that behavior is "defined" This is what is currently used in the XFS regression tests. From a quick look in the cmd/xfsprogs/db/check.c source, it looks like the intent was that an error would be flagged with an exit code of 2, and a serious_error with a code of 3. Looks like somewhere on the way, this is getting lost. If you're keen to make this work, it shouldn't be too difficult to figure out where things are going astray... I don't have much time to spend on it right now though. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Tue Dec 3 03:47:50 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 03:47:54 -0800 (PST) Received: from mail.tvol.net (pr-66-150-46-254.wgate.com [66.150.46.254]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3BlnuR030254 for ; Tue, 3 Dec 2002 03:47:50 -0800 Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 41A6ZZCX; Tue, 3 Dec 2002 06:51:14 -0500 Received: from wgate.com (sinz.eng.tvol.net [127.0.0.1]) by sinz.eng.tvol.net (8.12.5/8.12.5) with ESMTP id gB3BojGT031438; Tue, 3 Dec 2002 06:50:45 -0500 Message-ID: <3DEC9A95.7010302@wgate.com> Date: Tue, 03 Dec 2002 06:50:45 -0500 From: Michael Sinz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021111 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nathan Scott CC: linux-xfs@oss.sgi.com Subject: Re: xfs_check exit code? References: <20021129063350.35728.qmail@web15205.mail.bjs.yahoo.com> <3DEB4F26.5010608@wgate.com> <20021203044009.GD6391@frodo.melbourne.sgi.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 1926 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: msinz@wgate.com Precedence: bulk X-list: linux-xfs Nathan Scott wrote: > On Mon, Dec 02, 2002 at 07:16:38AM -0500, Michael Sinz wrote: > >>I have been, it seems wrongly, assuming that if xfs_check finds >>a problem on the disk that the exit code is non-zero. (And, >>conversely, if all is well, that the exit code is zero) >> >>Anyway, I have, this weekend, had some problems with one of my machines. >>(I have not fully diagnosed the problem so I don't want to point fingers >>at XFS yet). During the recovery process, I used my /boot recovery >>script and, while xfs_check found errors, the exit code of xfs_check >>was zero. This prevented auto-recovery from working. >> >>Is the exit code part of the defined API for xfs_check? Could it be >>part of the defined behavior? >> >>For now I will need to check if xfs_check has any output - which is >>almost as good as long as that behavior is "defined" > > > This is what is currently used in the XFS regression tests. From > a quick look in the cmd/xfsprogs/db/check.c source, it looks like > the intent was that an error would be flagged with an exit code of > 2, and a serious_error with a code of 3. Looks like somewhere on > the way, this is getting lost. If you're keen to make this work, > it shouldn't be too difficult to figure out where things are going > astray... I don't have much time to spend on it right now though. When I can come up for some air on the current project at work I will have a look at it. Since this was the intent then I can at least try to make it do that without going against the intent. -- Michael Sinz -- Director, Systems Engineering -- Worldgate Communications A master's secrets are only as good as the master's ability to explain them to others. From owner-linux-xfs@oss.sgi.com Tue Dec 3 09:30:10 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 09:30:20 -0800 (PST) Received: from ahriman.bucharest.roedu.net (ahriman.bucharest.roedu.net [141.85.128.71]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3HU9uR007603 for ; Tue, 3 Dec 2002 09:30:09 -0800 Received: (qmail 10342 invoked by uid 1000); 3 Dec 2002 17:50:50 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 3 Dec 2002 17:50:50 -0000 Date: Tue, 3 Dec 2002 19:50:50 +0200 (EET) From: Mihai RUSU X-X-Sender: To: Linux XFS List cc: Keith Owens Subject: kdb for 1.1 release Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 1927 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dizzy@roedu.net Precedence: bulk X-list: linux-xfs Hi We are using 2.4.9-31SGI_XFS_1.1 kernel release and we hadnt any problems on any of our production machines since the release. Recently on some of newer machines we hit some strange (XFS related?) problems. Processes that try to access FS (like /bin/ls) block in D state indefinetly. This processes exit when sent a TERM signal (no need for KILL). The only change (other that hardware) from the older systems is that we now use external log (maximum 128M size). After "some" time the machine stoped responding at all (was responding on ping but not other services), but we lost any "kernel panic" messages. That wont happen again :) Because some time ago we hit a similar problem (2.4.10 xfs kernel with DMAPI problem), and we used kdb to hunt down the problem we want now to try the same thing. Problem is I dont seem to find a proper kdb patch for 2.4.9-31SGI_XFS_1.1 kernel. Can somebody help me ? Thanks ---------------------------- Mihai RUSU Disclaimer: Any views or opinions presented within this e-mail are solely those of the author and do not necessarily represent those of any company, unless otherwise specifically stated. From owner-linux-xfs@oss.sgi.com Tue Dec 3 09:42:22 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 09:42:25 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3HgMuR008075 for ; Tue, 3 Dec 2002 09:42:22 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3FjRG8015691 for ; Tue, 3 Dec 2002 07:45:28 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA77194 for ; Tue, 3 Dec 2002 11:10:02 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA39564 for ; Tue, 3 Dec 2002 11:45:20 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB40xQq00332 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 19:59:26 -0500 Resent-Message-Id: <200212040059.gB40xQq00332@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA21040 for ; Tue, 3 Dec 2002 11:44:22 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3HiKQb38963986 for ; Tue, 3 Dec 2002 09:44:21 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3HgeZG001344 for ; Tue, 3 Dec 2002 18:42:40 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3Hgecu001343 for hch@sgi.com; Tue, 3 Dec 2002 18:42:40 +0100 Date: Tue, 3 Dec 2002 18:42:40 +0100 From: Christoph Hellwig Message-Id: <200212031742.gB3Hgecu001343@lab343.munich.sgi.com> Subject: TAKE - bring 2.5 back in line with 2.4 To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 19:59:25 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1928 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs port forward a large number of missing mods. Implement xfs_panic_mask Date: Tue Dec 3 07:31:41 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Merged by: hch Merged mods: 2.4.x-xfs:slinx:131027a,2.4.x-xfs:slinx:131040a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134172a linux/fs/xfs/xfs_rw.c - 1.373 - Merge of 2.4.x-xfs:slinx:131027a originally by sandeen on 10/24/02 Implement xfs_panic_mask hook forced shutdown into panic_mask handling linux/fs/xfs/xfs_error.c - 1.36 - Merge of 2.4.x-xfs:slinx:131027a originally by sandeen on 10/24/02 Implement xfs_panic_mask linux/fs/xfs/xfs_error.h - 1.28 - Merge of 2.4.x-xfs:slinx:131027a originally by sandeen on 10/24/02 Implement xfs_panic_mask define more panic tags for force shutdown linux/fs/xfs/linux/xfs_globals.c - 1.39 - Merge of 2.4.x-xfs:slinx:131027a originally by sandeen on 10/24/02 Implement xfs_panic_mask linux/fs/xfs/linux/xfs_linux.h - 1.94 - Merge of 2.4.x-xfs:slinx:131027a originally by sandeen on 10/24/02 Implement xfs_panic_mask #define xfs_panic_mask as a sysctl parameter linux/fs/xfs/linux/xfs_sysctl.h - 1.8 - Merge of 2.4.x-xfs:slinx:131040a originally by sandeen on 10/24/02 Missing bit of xfs_panic_mask linux/fs/xfs/linux/xfs_sysctl.c - 1.11 - Merge of 2.4.x-xfs:slinx:131027a originally by sandeen on 10/24/02 Implement xfs_panic_mask set up xfs_panic_mask sysctl add a field to the iclog output Date: Tue Dec 3 07:53:23 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: lord Merged by: hch Merged mods: 2.4.x-xfs:slinx:132911a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:132911a linux/fs/xfs/xfsidbg.c - 1.213 - Merge of 2.4.x-xfs:slinx:132911a by hch. No need to set task state back to TASK_RUNNING after returning from schedule() Date: Tue Dec 3 08:20:41 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Merged by: hch Merged mods: 2.4.x-xfs:slinx:132934a,2.4.x-xfs:slinx:133235a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134176a linux/fs/xfs/support/sv.h - 1.10 - Merge of 2.4.x-xfs:slinx:132934a originally by lord on 11/12/02 No need to set task state back to TASK_RUNNING after returning from schedule() set_current_state(TASK_RUNNING); Merge of 2.4.x-xfs:slinx:133235a originally by lord on 11/15/02 go back to using macros to set task state linux/fs/xfs/support/mrlock.c - 1.12 - Merge of 2.4.x-xfs:slinx:132934a originally by lord on 11/12/02 No need to set task state back to TASK_RUNNING after returning from schedule() remove set_current_state(TASK_RUNNING); Merge of 2.4.x-xfs:slinx:133235a originally by lord on 11/15/02 go back to using macros to set task state clean up use of run_task_queue in xfs Date: Tue Dec 3 08:45:57 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: lord Merged by: hch Merged mods: 2.4.x-xfs:slinx:133254a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:133254a linux/fs/xfs/xfsidbg.c - 1.214 - Merge of 2.4.x-xfs:slinx:133254a by hch. fix up pagebuf debug function linux/fs/xfs/xfs_buf.h - 1.102 linux/fs/xfs/pagebuf/page_buf_locking.c - 1.32 - Merge of 2.4.x-xfs:slinx:133254a by hch. call pagebuf_run_task_queue linux/fs/xfs/pagebuf/page_buf.c - 1.81 - Merge of 2.4.x-xfs:slinx:133254a by hch. we had one unneeded run_task_queue in here, kill it, also wrap run_task_queue in a test to see if there is pending I/O on the buffer in question. Make it possible to run th io completion code locally rather than scheduling it, for the cases where we are not in interrupt context. linux/fs/xfs/pagebuf/page_buf.h - 1.54 - Merge of 2.4.x-xfs:slinx:133254a by hch. move pb_io_remaining here from the private structure and create pagebuf_run_task_queue as an inline function. linux/fs/xfs/pagebuf/page_buf_internal.h - 1.17 - Merge of 2.4.x-xfs:slinx:133254a by hch. move pb_io_remaining from here to public pagebuf structure remove some unused code paths from the log flushing paths, and remove the callback processing from the log write path, we only do callbacks on I/O completion now. Date: Tue Dec 3 08:55:13 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: lord Merged by: hch Merged mods: 2.4.x-xfs:slinx:133285a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:133285a linux/fs/xfs/xfs_log.c - 1.261 - Merge of 2.4.x-xfs:slinx:133285a by hch. cleanup and remove xlog_state_do_callback from iclog space reservation code. avoid need to remap pages when discarding attribute space Date: Tue Dec 3 09:04:33 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: lord Merged by: hch Merged mods: 2.4.x-xfs:slinx:133408a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:133408a linux/fs/xfs/xfs_attr_leaf.c - 1.65 - Merge of 2.4.x-xfs:slinx:133408a by hch. pass explicit flags into trans_get_buf cleanup user path walking code Date: Tue Dec 3 09:15:05 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Merged by: hch Merged mods: 2.4.x-xfs:slinx:133881a,2.4.x-xfs:slinx:133953a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134179a linux/fs/xfs/linux/xfs_ioctl.c - 1.90 - Merge of 2.4.x-xfs:slinx:133881a originally by hch on 11/22/02 cleanup user path walking code use user_path_walk_link Merge of 2.4.x-xfs:slinx:133953a originally by nathans on 11/24/02 Fix cleanup of path walking by handle - use hreq.path, not local path variable. for synchronous transactions, allow the in core log buffer to wait around in active state for as long as possible. This allows us to coalesce several transactions into one buffer and reduce the disk traffic. Date: Tue Dec 3 09:36:03 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: lord Merged by: hch Merged mods: 2.4.x-xfs:slinx:134077a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134077a linux/fs/xfs/xfs_log.c - 1.262 - Merge of 2.4.x-xfs:slinx:134077a by hch. Introduce a new sync variable in the iclog structure to sync between the last log write and the next one in the case of sync transactions forcing iclogs out to disk early. linux/fs/xfs/xfs_log_priv.h - 1.86 - Merge of 2.4.x-xfs:slinx:134077a by hch. new sync variable in the iclog structure when logging attribute extents, use the correct size for the allocation! Date: Tue Dec 3 09:42:33 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: lord Merged by: hch Merged mods: 2.4.x-xfs:slinx:134098a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134098a linux/fs/xfs/xfs_inode_item.c - 1.107 - Merge of 2.4.x-xfs:slinx:134098a by hch. use attribute fork size in allocation rather than data fork size From owner-linux-xfs@oss.sgi.com Tue Dec 3 10:13:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 10:13:39 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3IDZuR008856 for ; Tue, 3 Dec 2002 10:13:35 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3GGfG8017709 for ; Tue, 3 Dec 2002 08:16:41 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA77341 for ; Tue, 3 Dec 2002 11:41:11 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA42224 for ; Tue, 3 Dec 2002 12:16:34 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB41UeT00761 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 20:30:40 -0500 Resent-Message-Id: <200212040130.gB41UeT00761@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA36540 for ; Tue, 3 Dec 2002 12:01:07 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3I15Qb39041909 for ; Tue, 3 Dec 2002 10:01:05 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3HxPNE001035 for ; Tue, 3 Dec 2002 18:59:25 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3HxPuq001034 for hch@sgi.com; Tue, 3 Dec 2002 18:59:25 +0100 Date: Tue, 3 Dec 2002 18:59:25 +0100 From: Christoph Hellwig Message-Id: <200212031759.gB3HxPuq001034@lab343.munich.sgi.com> Subject: TAKE - bring ACL ifdefs in line with 2.5 To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 20:30:40 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1929 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 10:00:04 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134183a linux/fs/Config.in - 1.88 linux/arch/sparc64/defconfig - 1.60 linux/arch/sparc/defconfig - 1.32 linux/arch/ppc/defconfig - 1.39 linux/arch/mips/defconfig - 1.25 linux/arch/m68k/defconfig - 1.13 linux/arch/i386/defconfig - 1.89 linux/arch/arm/defconfig - 1.20 linux/arch/alpha/defconfig - 1.22 linux/Documentation/Configure.help - 1.141 linux/arch/sh/defconfig - 1.19 linux/arch/ppc/configs/walnut_defconfig - 1.18 linux/arch/ppc/configs/pmac_defconfig - 1.7 linux/arch/ppc/configs/oak_defconfig - 1.18 linux/arch/ppc/configs/mbx_defconfig - 1.13 linux/arch/ppc/configs/gemini_defconfig - 1.21 linux/arch/ppc/configs/common_defconfig - 1.27 linux/arch/ppc/configs/apus_defconfig - 1.14 linux/arch/ia64/defconfig - 1.14 linux/arch/mips64/defconfig - 1.21 linux/arch/s390/defconfig - 1.13 linux/fs/xfs/Makefile - 1.152 linux/fs/xfs/linux/xfs_super.h - 1.34 linux/fs/xfs/linux/xfs_super.c - 1.232 linux/fs/xfs/linux/xfs_iops.c - 1.183 linux/arch/ppc/configs/rpxlite_defconfig - 1.13 linux/arch/ppc/configs/rpxcllf_defconfig - 1.14 linux/arch/ppc/configs/est8260_defconfig - 1.14 linux/arch/ppc/configs/bseip_defconfig - 1.13 linux/arch/parisc/defconfig - 1.6 linux/fs/xfs/xfs_acl.h - 1.22 linux/arch/ppc/configs/power3_defconfig - 1.12 linux/arch/ppc/configs/ibmchrp_defconfig - 1.12 linux/arch/cris/defconfig - 1.11 linux/arch/s390x/defconfig - 1.12 linux/arch/ppc/configs/TQM860L_defconfig - 1.12 linux/arch/ppc/configs/TQM850L_defconfig - 1.11 linux/arch/ppc/configs/TQM823L_defconfig - 1.11 linux/arch/ppc/configs/SPD823TS_defconfig - 1.11 linux/arch/ppc/configs/SM850_defconfig - 1.11 linux/arch/ppc/configs/IVMS8_defconfig - 1.12 linux/arch/ppc/configs/spruce_defconfig - 1.2 linux/arch/ppc/configs/pal4_defconfig - 1.2 linux/arch/ppc/configs/briq_defconfig - 1.2 - s/CONFIG_FS_POSIX_ACL/CONFIG_XFS_POSIX_ACL/g From owner-linux-xfs@oss.sgi.com Tue Dec 3 10:13:48 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 10:13:50 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3IDmuR008911 for ; Tue, 3 Dec 2002 10:13:48 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3GGnG8017733 for ; Tue, 3 Dec 2002 08:16:49 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA57180 for ; Tue, 3 Dec 2002 11:41:18 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA41360 for ; Tue, 3 Dec 2002 12:16:42 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB41Um800767 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 20:30:48 -0500 Resent-Message-Id: <200212040130.gB41Um800767@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA87483 for ; Tue, 3 Dec 2002 12:16:07 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3IG6Qb39220290 for ; Tue, 3 Dec 2002 10:16:06 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3IEQNE003041 for ; Tue, 3 Dec 2002 19:14:26 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3IEQ4p003040 for hch@sgi.com; Tue, 3 Dec 2002 19:14:26 +0100 Date: Tue, 3 Dec 2002 19:14:26 +0100 From: Christoph Hellwig Message-Id: <200212031814.gB3IEQ4p003040@lab343.munich.sgi.com> Subject: TAKE - make pagebuf_workqueue private to page_buf.c To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 20:30:48 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1930 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 10:15:04 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134185a linux/fs/xfs/pagebuf/page_buf.c - 1.82 linux/fs/xfs/pagebuf/page_buf.h - 1.55 - make pagebuf_workqueue private to page_buf.c From owner-linux-xfs@oss.sgi.com Tue Dec 3 10:47:26 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 10:47:29 -0800 (PST) Received: from banna (f010.ag238.FreeBit.NE.JP [219.109.238.10]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3IkouR010440 for ; Tue, 3 Dec 2002 10:47:12 -0800 Received: from wing-2f8mswpeuw ([192.168.0.5]) by banna (8.9.3+3.2W/3.7W) with SMTP id DAA25103; Wed, 4 Dec 2002 03:49:49 +0900 Message-Id: <200212031849.DAA25103@banna> From: =?iso-2022-jp?B?aG1haWw=?= To: =?iso-2022-jp?B?MDYwMA==?=@banna.sgi.com Reply-To: hmail1111@yahoo.co.jp Date: Wed, 04 Dec 2002 03:47:01 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoRUU7UiVhITwlazktOXAbKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 1931 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hmail1111@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望しない方はここへ (必ず本文にあなたのメールアドレスのみをお書き下さい） fmail9999jp@yahoo.co.jp メールアドレスをご記入してください。 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218 =============================================================== 問題商品ばかり集めましたので、消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Tue Dec 3 11:23:18 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 11:23:21 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3JNHuR011320 for ; Tue, 3 Dec 2002 11:23:17 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3IUZKp025105 for ; Tue, 3 Dec 2002 10:30:35 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA70123 for ; Tue, 3 Dec 2002 12:50:44 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA54181 for ; Tue, 3 Dec 2002 13:26:16 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB42eMA01306 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 21:40:22 -0500 Resent-Message-Id: <200212040240.gB42eMA01306@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA50835 for ; Tue, 3 Dec 2002 13:25:57 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3JPtQb38980408 for ; Tue, 3 Dec 2002 11:25:56 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3JOF6U001105 for ; Tue, 3 Dec 2002 20:24:15 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3JOF9g001104 for hch@sgi.com; Tue, 3 Dec 2002 20:24:15 +0100 Date: Tue, 3 Dec 2002 20:24:15 +0100 From: Christoph Hellwig Message-Id: <200212031924.gB3JOF9g001104@lab343.munich.sgi.com> Subject: TAKE - add missing LOOKUP_POSITIVE to path_lookup calls To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 21:40:22 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1932 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs We only want existing dentries in our lookups. This got lost due to a number of messy 2.4/2.5 differences. Date: Tue Dec 3 11:24:48 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134198a linux/fs/xfs/linux/xfs_super.c - 1.249 linux/fs/xfs/dmapi/dmapi_register.c - 1.22 - add missing LOOKUP_POSITIVE From owner-linux-xfs@oss.sgi.com Tue Dec 3 11:25:12 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 11:25:13 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3JPBuR011753 for ; Tue, 3 Dec 2002 11:25:12 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3JXAkq010681 for ; Tue, 3 Dec 2002 13:33:10 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA38844 for ; Tue, 3 Dec 2002 12:52:37 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA49595 for ; Tue, 3 Dec 2002 13:28:09 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB42gFg01311 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 21:42:15 -0500 Resent-Message-Id: <200212040242.gB42gFg01311@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA51755 for ; Tue, 3 Dec 2002 13:20:17 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3JKFQb39159256 for ; Tue, 3 Dec 2002 11:20:16 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3JIa6U001005 for ; Tue, 3 Dec 2002 20:18:36 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3JIZsR001004 for hch@sgi.com; Tue, 3 Dec 2002 20:18:35 +0100 Date: Tue, 3 Dec 2002 20:18:35 +0100 From: Christoph Hellwig Message-Id: <200212031918.gB3JIZsR001004@lab343.munich.sgi.com> Subject: TAKE - always use path_lookup instead of path_init + path_walk To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 21:42:15 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1933 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 10:49:02 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134191a linux/kernel/ksyms.c - 1.139 - export path_lookup as in 2.5 linux/fs/xfs/linux/xfs_super.c - 1.233 linux/fs/xfs/dmapi/dmapi_register.c - 1.20 - use path_lookup instead of path_init + path_walk Subject: TAKE - use find_trylock_page instead of find_get_page + TryLockPage Date: Tue Dec 3 10:58:29 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134193a linux/kernel/ksyms.c - 1.140 - export find_trylock_page as in 2.5 linux/fs/xfs/linux/xfs_aops.c - 1.15 - use find_trylock_page instead of find_get_page + TryLockPage Subject: TAKE - small syncups with 2.5 Date: Tue Dec 3 11:19:47 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134197a linux/fs/xfs/xfs_vfsops.c - 1.401 - remove useless initialization linux/fs/xfs/linux/xfs_linux.h - 1.95 - include major.h (some ports don't get it implicitly) include mm.h instead of fs.h (includes fs.h implicitly) linux/fs/xfs/linux/xfs_super.c - 1.234 - use NODEV instead of 0 for a nil kdev_t assignment use sb_min_blocksize as in 2.5 linux/fs/xfs/dmapi/dmapi_sysent.c - 1.18 - include major.h (some ports don't get it implicitly) From owner-linux-xfs@oss.sgi.com Tue Dec 3 11:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 11:44:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3Ji1uR012423 for ; Tue, 3 Dec 2002 11:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3Ji1bs012420 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 11:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3Jhwuf012372 for ; Tue, 3 Dec 2002 11:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3JamXW012321; Tue, 3 Dec 2002 11:36:48 -0800 Date: Tue, 3 Dec 2002 11:36:48 -0800 Message-Id: <200212031936.gB3JamXW012321@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 200] xfs_check should set the exit code to non-zero if the filesystem does not check out X-Bugzilla-Reason: AssignedTo X-archive-position: 1936 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=200 cattelan@thebarn.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 3 11:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 11:44:03 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3Ji1uR012421 for ; Tue, 3 Dec 2002 11:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3Ji1ff012418 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 11:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3JhwuZ012372 for ; Tue, 3 Dec 2002 11:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3Jbqmj012336; Tue, 3 Dec 2002 11:37:52 -0800 Date: Tue, 3 Dec 2002 11:37:52 -0800 Message-Id: <200212031937.gB3Jbqmj012336@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 198] file corruption over NFSv3 UDP using 1.2pre3 X-Bugzilla-Reason: AssignedTo X-archive-position: 1934 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=198 cattelan@thebarn.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|xfs-master@oss.sgi.com |cattelan@thebarn.com ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 3 11:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 11:44:03 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3Ji1uR012422 for ; Tue, 3 Dec 2002 11:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3Ji1x6012419 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 11:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3JhwuX012372 for ; Tue, 3 Dec 2002 11:43:58 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3JaR0b012314; Tue, 3 Dec 2002 11:36:27 -0800 Date: Tue, 3 Dec 2002 11:36:27 -0800 Message-Id: <200212031936.gB3JaR0b012314@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 198] file corruption over NFSv3 UDP using 1.2pre3 X-Bugzilla-Reason: AssignedTo X-archive-position: 1935 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=198 ------- Additional Comments From cattelan@thebarn.com 2002-12-03 11:36 ------- Additional comments from Stephane I do have one bit of positive progress to report (finally)! I commented out the purging of the XFS refcache and got no corruption (ran about 56 hours). As you know, the refcache is just a table of open files kept by XFS, specifically to speedup nfsd. Otherwise, whenever a file is closed XFS does a truncate (and perhaps other stuff, probably to clear out any over allocation...) and the truncate takes a bit of time as it goes through all the file's pages. So by keeping them open, this penalty is avoided. To make sure that file info gets flushed, entries are purged regularly from the refcache: in short our files get closed every 30seconds. Well I just commented that part out. That's a test of course, not a solution. --- linux/fs/xfs/xfs_vfsops.c.orig Sat Nov 30 01:09:15 2002 +++ linux/fs/xfs/xfs_vfsops.c Sat Nov 30 01:09:43 2002 @@ -1515,7 +1515,7 @@ * eventually kicked out of the cache. */ if (flags & SYNC_BDFLUSH) { - xfs_refcache_purge_some(mp); + //xfs_refcache_purge_some(mp); } /* I'll look at the code this morning and try to understand what's going on. My guess is that the file is being closed (truncated and perhaps other stuff) and at the same time some other request is extending it, and this confuses XFS somehow, perhaps some locking is missing. It's still surprising that data jumps from one file to another though. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 3 12:18:18 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 12:18:21 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3KIIuR013923 for ; Tue, 3 Dec 2002 12:18:18 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3ILNG8026702 for ; Tue, 3 Dec 2002 10:21:24 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id NAA75348 for ; Tue, 3 Dec 2002 13:45:37 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA54599 for ; Tue, 3 Dec 2002 14:21:16 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB43ZMY01405 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 22:35:22 -0500 Resent-Message-Id: <200212040335.gB43ZMY01405@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA52327 for ; Tue, 3 Dec 2002 14:17:03 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3KH1Qb39235955 for ; Tue, 3 Dec 2002 12:17:02 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3KFL6U002916 for ; Tue, 3 Dec 2002 21:15:21 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3KFLL9002915 for hch@sgi.com; Tue, 3 Dec 2002 21:15:21 +0100 Date: Tue, 3 Dec 2002 21:15:21 +0100 From: Christoph Hellwig Message-Id: <200212032015.gB3KFLL9002915@lab343.munich.sgi.com> Subject: TAKE - misc tidyups To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 22:35:22 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1937 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 12:15:17 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134216a linux/fs/xfs/xfs_dmapi.c - 1.92 - tidy up prohibited_mr_events linux/fs/xfs/pagebuf/page_buf.c - 1.84 - don't include compiler.h include workqueue.h directly linux/fs/xfs/pagebuf/page_buf.h - 1.57 - don't include workqueue.h here small comment fix From owner-linux-xfs@oss.sgi.com Tue Dec 3 12:37:08 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 12:37:13 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3Kb7uR014964 for ; Tue, 3 Dec 2002 12:37:08 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3IeDG8027790 for ; Tue, 3 Dec 2002 10:40:13 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA84113 for ; Tue, 3 Dec 2002 14:04:25 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA36957 for ; Tue, 3 Dec 2002 14:40:07 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB43sDC01419 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 22:54:13 -0500 Resent-Message-Id: <200212040354.gB43sDC01419@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA53966 for ; Tue, 3 Dec 2002 14:34:56 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3KYsQb39268414 for ; Tue, 3 Dec 2002 12:34:55 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3KXE6U003597 for ; Tue, 3 Dec 2002 21:33:14 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3KXEEp003596 for hch@sgi.com; Tue, 3 Dec 2002 21:33:14 +0100 Date: Tue, 3 Dec 2002 21:33:14 +0100 From: Christoph Hellwig Message-Id: <200212032033.gB3KXEEp003596@lab343.munich.sgi.com> Subject: TAKE - remove two dead members from pagebuf_daemon To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 22:54:12 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1938 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 12:34:11 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134222a linux/fs/xfs/pagebuf/page_buf.c - 1.84 - don't reference write-only io_active and pb_delwri_cnt members of pagebuf_daemon linux/fs/xfs/pagebuf/page_buf_internal.h - 1.19 - remove io_active and pb_delwri_cnt members from pagebuf_daemon_t From owner-linux-xfs@oss.sgi.com Tue Dec 3 12:40:20 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 12:40:23 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3KeKuR015411 for ; Tue, 3 Dec 2002 12:40:20 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3IhPG8027987 for ; Tue, 3 Dec 2002 10:43:26 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA89007 for ; Tue, 3 Dec 2002 14:07:36 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA57464 for ; Tue, 3 Dec 2002 14:43:17 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB43vNv01427 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 22:57:23 -0500 Resent-Message-Id: <200212040357.gB43vNv01427@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA58859 for ; Tue, 3 Dec 2002 14:43:05 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3Kh4Qb39284868 for ; Tue, 3 Dec 2002 12:43:04 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3KfN6U004661 for ; Tue, 3 Dec 2002 21:41:23 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3KfNrS004660 for hch@sgi.com; Tue, 3 Dec 2002 21:41:23 +0100 Date: Tue, 3 Dec 2002 21:41:23 +0100 From: Christoph Hellwig Message-Id: <200212032041.gB3KfNrS004660@lab343.munich.sgi.com> Subject: TAKE - fix denywrite check in prohibited_mr_events() To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 3 Dec 2002 22:57:23 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1939 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 12:42:11 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134225a linux/fs/xfs/xfs_dmapi.c - 1.87 - fix denywrite check in prohibited_mr_events() From owner-linux-xfs@oss.sgi.com Tue Dec 3 13:14:00 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 13:14:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3LE0uR016546 for ; Tue, 3 Dec 2002 13:14:00 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3LE0UO016545 for linux-xfs@oss.sgi.com; Tue, 3 Dec 2002 13:14:00 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB3LDwuV016529 for ; Tue, 3 Dec 2002 13:13:58 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB3LAcDK016516; Tue, 3 Dec 2002 13:10:38 -0800 Date: Tue, 3 Dec 2002 13:10:38 -0800 Message-Id: <200212032110.gB3LAcDK016516@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 200] xfs_check should set the exit code to non-zero if the filesystem does not check out X-Bugzilla-Reason: AssignedTo X-archive-position: 1940 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=200 ------- Additional Comments From c.pascoe@itee.uq.edu.au 2002-12-03 13:10 ------- Created an attachment (id=55) --> (http://oss.sgi.com/bugzilla/attachment.cgi?id=55&action=view) Alters error exit codes from xfs_check xfs_check returns success when the superblock magic is invalid - this makes it return the serious error exit code (3) for this case, and the invalid arguments exit code (1) if the arguments to xfs_check were wrong. A glance at the code suggests that other xfs_check failures appear to return the correct error codes. Chris ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 3 15:33:49 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 03 Dec 2002 15:33:54 -0800 (PST) Received: from verein.lst.de (verein.lst.de [212.34.181.86]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB3NXluR019153 for ; Tue, 3 Dec 2002 15:33:48 -0800 Received: (from hch@localhost) by verein.lst.de (8.11.6/8.11.6) id gB3Nara12475 for linux-xfs@oss.sgi.com; Wed, 4 Dec 2002 00:36:53 +0100 Resent-Message-Id: <200212032336.gB3Nara12475@verein.lst.de> Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by verein.lst.de (8.11.6/8.11.6) with ESMTP id gB3N3Mu12290 for ; Wed, 4 Dec 2002 00:03:22 +0100 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB3N8Ekq015192 for ; Tue, 3 Dec 2002 17:08:14 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id QAA04032 for ; Tue, 3 Dec 2002 16:27:08 -0600 (CST) Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id RAA68731 for ; Tue, 3 Dec 2002 17:03:10 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB3N38Qb39291174 for ; Tue, 3 Dec 2002 15:03:09 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB3N1SC7001807 for ; Wed, 4 Dec 2002 00:01:28 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB3N1SIj001806 for hch@sgi.com; Wed, 4 Dec 2002 00:01:28 +0100 Date: Wed, 4 Dec 2002 00:01:28 +0100 From: Christoph Hellwig Message-Id: <200212032301.gB3N1SIj001806@lab343.munich.sgi.com> Subject: TAKE - fix small typo in rtdev mount code To: undisclosed-recipients:; Resent-From: hch@lst.de Resent-Date: Wed, 4 Dec 2002 00:36:53 +0100 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1941 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@lst.de Precedence: bulk X-list: linux-xfs Date: Tue Dec 3 15:02:40 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134254a linux/fs/xfs/xfs_vfsops.c - 1.402 - fix small typo in rtdev mount code From owner-linux-xfs@oss.sgi.com Wed Dec 4 05:52:37 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 05:52:41 -0800 (PST) Received: from indonesia.kscanners.no (indonesia.kscanners.no [193.214.130.21]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4DqYuR028836 for ; Wed, 4 Dec 2002 05:52:36 -0800 Received: from localhost.localdomain ([127.0.0.1] helo=indonesia) by indonesia.kscanners.no with esmtp (Exim 3.33 #1) id 18JZzy-0007NX-00 for linux-xfs@oss.sgi.com; Wed, 04 Dec 2002 14:55:34 +0100 Date: Wed, 4 Dec 2002 14:55:33 +0100 From: Toralf Lund To: linux-xfs@oss.sgi.com Subject: Red Hat 7.3 installation. What version? Message-ID: <20021204135533.GA27650@indonesia.kscanners.no> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=ISO-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-Mailer: Balsa 1.4.1 Lines: 14 X-archive-position: 1942 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: toralf@procaptura.com Precedence: bulk X-list: linux-xfs I have a Red Hat 7.2 system running XFS 1.0.2; kernel version is kernel-2.4.9-31SGI_XFS_1.0.2. I'm planning to upgrade to version 7.3 (not 8.0 yet, as I'm not quite prepared for an upgrade to GNOME 2.) What XFS/kernel versions would you recommend installing? - The obvious alternatives seem to be XFS 1.1/2.4.18-4-RH (contrib RPMS) and Release-1.2pre3/2.4.18-17SGI_XFS. Both seem to have some drawbacks; the former kernel does not contain the latest Red Hat patches (we are using kernel-2.4.18-17.7.x on other hosts) while the latter is presumable less stable. -- Toralf Lund +47 66 85 51 22 ProCaptura AS +47 66 85 51 00 (switchboard) http://www.procaptura.com/~toralf +47 66 85 51 01 (fax) From owner-linux-xfs@oss.sgi.com Wed Dec 4 08:06:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 08:06:40 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4G6XuR004495 for ; Wed, 4 Dec 2002 08:06:33 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB4E9dG8018441 for ; Wed, 4 Dec 2002 06:09:39 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA96492; Wed, 4 Dec 2002 10:09:32 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id KAA70605; Wed, 4 Dec 2002 10:09:26 -0600 (CST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by rose.americas.sgi.com (8.12.5/8.12.5) with ESMTP id gB4HAEIx021442; Wed, 4 Dec 2002 11:10:16 -0600 Subject: Re: Red Hat 7.3 installation. What version? From: Russell Cattelan To: Toralf Lund Cc: linux-xfs@oss.sgi.com In-Reply-To: <20021204135533.GA27650@indonesia.kscanners.no> References: <20021204135533.GA27650@indonesia.kscanners.no> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 04 Dec 2002 11:10:13 -0600 Message-Id: <1039021816.19930.89.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 1943 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs On Wed, 2002-12-04 at 07:55, Toralf Lund wrote: > I have a Red Hat 7.2 system running XFS 1.0.2; kernel version is > kernel-2.4.9-31SGI_XFS_1.0.2. I'm planning to upgrade to version 7.3 (not > 8.0 yet, as I'm not quite prepared for an upgrade to GNOME 2.) What > XFS/kernel versions would you recommend installing? - The obvious > alternatives seem to be XFS 1.1/2.4.18-4-RH (contrib RPMS) and > Release-1.2pre3/2.4.18-17SGI_XFS. Both seem to have some drawbacks; the > former kernel does not contain the latest Red Hat patches (we are using > kernel-2.4.18-17.7.x on other hosts) while the latter is presumable less > stable. > The pre3 kernel has been quite stable. In fact except for one small aim 7 performance change that is going into pre4 we will probably release 1.2 after that. > -- > Toralf Lund +47 66 85 51 22 > ProCaptura AS +47 66 85 51 00 (switchboard) > http://www.procaptura.com/~toralf +47 66 85 51 01 (fax) > From owner-linux-xfs@oss.sgi.com Wed Dec 4 08:59:42 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 08:59:48 -0800 (PST) Received: from beta (p5085AA2B.dip.t-dialin.net [80.133.170.43]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4GxeuR006063 for ; Wed, 4 Dec 2002 08:59:41 -0800 Received: from athlon ([192.168.1.10]) by beta with smtp (Exim 3.35 #1 (Debian)) id 18Jcv6-0000RO-00 for ; Wed, 04 Dec 2002 18:02:44 +0100 Message-ID: <01a801c29bb6$faa892e0$0a01a8c0@athlon> From: "Christoph Bayer" To: Subject: Unable to activate Quota on root filesystem Date: Wed, 4 Dec 2002 18:02:20 +0100 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=SHA1; protocol="application/x-pkcs7-signature"; boundary="----=_NextPart_000_0197_01C29BBF.4A789330" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 1944 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Christoph.Bayer@alpha.dyndns.tv Precedence: bulk X-list: linux-xfs This is a multi-part message in MIME format. ------=_NextPart_000_0197_01C29BBF.4A789330 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hello everybody, I am using kernel 2.4.20 + xfs cvs patch from 12/2/2002. I have activated quota for linux and for the xfs filesystem. I can activate quotasupport on all but the root partition. I get the foloowing warning: Enabling group quota on root filesystem (reboot to take effect) quotaon: quotactl on /dev/hde1: Invalid argument Enabling user quota on root filesystem (reboot to take effect) quotaon: quotactl on /dev/hde1: Invalid argument The root fs was created with 2.4.18 with xfs release 1.0.2... Best regards, Christoph ------=_NextPart_000_0197_01C29BBF.4A789330 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEH AQAAoIIFwDCCAtgwggJBoAMCAQICAQIwDQYJKoZIhvcNAQEEBQAwgZsxCzAJ BgNVBAYTAkRFMQwwCgYDVQQIEwNOUlcxDzANBgNVBAcTBkxpbmRlbjEUMBIG A1UEChMLQ0JBIFJvb3QgQ0ExGDAWBgNVBAsTD1NlY3VyaXR5IEFnZW5jeTEY MBYGA1UEAxMPYWxwaGEuZHluZG5zLnR2MSMwIQYJKoZIhvcNAQkBFhRJbmZv QGFscGhhLmR5bmRucy50djAeFw0wMjAxMjcxODAxMjhaFw0wMzAxMjcxODAx MjhaMEoxGDAWBgNVBAMTD0NocmlzdG9waCBCYXllcjEuMCwGCSqGSIb3DQEJ ARYfQ2hyaXN0b3BoLkJheWVyQGFscGhhLmR5bmRucy50djCBnzANBgkqhkiG 9w0BAQEFAAOBjQAwgYkCgYEA8I0v0U9ma5amDuFvBB3GeOs6txd9StrT+A8s 6wRUf+mM/rtQ8+qq+q/cjvqIexOgK1oug2HpSKM6Tau2B3BSAXRNpIRyh2JL IC0tlDF2PVMtk3ZfBaAuimOAd6o0Oj3yPO3lkeAVOwkQLQqmQb0BeS7SNH/D nRAiNcOf1P9gaD0CAwEAAaN8MHowKgYDVR0RBCMwIYEfQ2hyaXN0b3BoLkJh eWVyQGFscGhhLmR5bmRucy50djAMBgNVHRMBAf8EAjAAMB8GA1UdIwQYMBaA FG+/Z1P1XVVNHmQv6FhjSGcg6Jc8MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggr BgEFBQcDBDANBgkqhkiG9w0BAQQFAAOBgQB6FlLieMgPs2+WO63yZXqnQYxI Zed+0nZb8yAc25w0+61FKqkjXztm2WVxirm4E8u/CRz9dTA9BI/GPfQPcBbc IpYDSPwW+bYJ/GQD/ERWp/y8z3mSVZ8c11ME6Shw2Nq/tCtYvr/jp4IZCGkz ItEr66x/bs/k9HPv7r2M8bUIQzCCAuAwggJJoAMCAQICAQAwDQYJKoZIhvcN AQEEBQAwgZsxCzAJBgNVBAYTAkRFMQwwCgYDVQQIEwNOUlcxDzANBgNVBAcT BkxpbmRlbjEUMBIGA1UEChMLQ0JBIFJvb3QgQ0ExGDAWBgNVBAsTD1NlY3Vy aXR5IEFnZW5jeTEYMBYGA1UEAxMPYWxwaGEuZHluZG5zLnR2MSMwIQYJKoZI hvcNAQkBFhRJbmZvQGFscGhhLmR5bmRucy50djAeFw0wMjAxMjcxNzAwMjRa Fw0xMjAxMjUxNzAwMjRaMIGbMQswCQYDVQQGEwJERTEMMAoGA1UECBMDTlJX MQ8wDQYDVQQHEwZMaW5kZW4xFDASBgNVBAoTC0NCQSBSb290IENBMRgwFgYD VQQLEw9TZWN1cml0eSBBZ2VuY3kxGDAWBgNVBAMTD2FscGhhLmR5bmRucy50 djEjMCEGCSqGSIb3DQEJARYUSW5mb0BhbHBoYS5keW5kbnMudHYwgZ8wDQYJ KoZIhvcNAQEBBQADgY0AMIGJAoGBAMXCl8ra2QNXm0nRejHRr1IfRoD2vTAs ZvGSN8cDoF0N5JHmuHNMaAfUpAj6AG/R7oOJlSwm57ZewOZr0JP/PmauXDMq 4z3Ao/JV2g50THYVAnXkH54NyWJhQkB9SkLCqicHju1mvpFGByLOd3yAq4lq ZNTF23+53jDpiraOXWtNAgMBAAGjMjAwMA8GA1UdEwEB/wQFMAMBAf8wHQYD VR0OBBYEFG+/Z1P1XVVNHmQv6FhjSGcg6Jc8MA0GCSqGSIb3DQEBBAUAA4GB AB6YpiUITBOh6HeAlhhAqccN3ZNiZH1Ah0B6becAzjug/i7JO/XcOTgnamdi CgKJaoSPdGtooEw06Qabbiy5qMR5QUkhV5WNa/dozm72hA2cNR9n0GZxfZKr Fn95dl7x8Vxs8ZTw9P+lyEWW0hRynmCD99+UFMCRli/L0d2uQwZNMYICBTCC AgECAQEwgaEwgZsxCzAJBgNVBAYTAkRFMQwwCgYDVQQIEwNOUlcxDzANBgNV BAcTBkxpbmRlbjEUMBIGA1UEChMLQ0JBIFJvb3QgQ0ExGDAWBgNVBAsTD1Nl Y3VyaXR5IEFnZW5jeTEYMBYGA1UEAxMPYWxwaGEuZHluZG5zLnR2MSMwIQYJ KoZIhvcNAQkBFhRJbmZvQGFscGhhLmR5bmRucy50dgIBAjAJBgUrDgMCGgUA oIG6MBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8X DTAyMTIwNDE3MDIyMFowIwYJKoZIhvcNAQkEMRYEFAdSDVoqrFYtSJ1C6Uuy 2v7dWK2aMFsGCSqGSIb3DQEJDzFOMEwwCgYIKoZIhvcNAwcwDgYIKoZIhvcN AwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEo MAcGBSsOAwIdMA0GCSqGSIb3DQEBAQUABIGAIKaNYaHxbY3t9jd9PfvDptrW pKlDMCVKmwLhEk+Bi4Bl2Uh0IceQoIrZGeqi+yndFdH8oOSFObva+ZywV6B5 YTQOothsZiKLruX3ktv/Hcq5PwR7KG+ntpC9tZzQmWvTkqwA+VCUwC15ESEo gmTJvpX+CtrneVNBNRY0CdVP4zUAAAAAAAA= ------=_NextPart_000_0197_01C29BBF.4A789330-- From owner-linux-xfs@oss.sgi.com Wed Dec 4 09:12:42 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 09:12:43 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4HCfuR006973 for ; Wed, 4 Dec 2002 09:12:41 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB4HKlkq028823 for ; Wed, 4 Dec 2002 11:20:47 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA13878 for ; Wed, 4 Dec 2002 11:15:45 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA60469 for ; Wed, 4 Dec 2002 11:15:44 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB50TmW03468 for linux-xfs@oss.sgi.com; Wed, 4 Dec 2002 19:29:48 -0500 Resent-Message-Id: <200212050029.gB50TmW03468@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA71383 for ; Wed, 4 Dec 2002 11:14:52 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB4HEoQb38483568 for ; Wed, 4 Dec 2002 09:14:51 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB4HD9kF020469 for ; Wed, 4 Dec 2002 18:13:09 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB4HD9kw020468 for hch@sgi.com; Wed, 4 Dec 2002 18:13:09 +0100 Date: Wed, 4 Dec 2002 18:13:09 +0100 From: Christoph Hellwig Message-Id: <200212041713.gB4HD9kw020468@lab343.munich.sgi.com> Subject: TAKE - QA Test 032: mkfs.msdos doesn't support large filesystems either To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Wed, 4 Dec 2002 19:29:48 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1945 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Wed Dec 4 09:14:14 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:134316a cmd/xfstests/032 - 1.7 - extend the minix large filesystem special casing to msdos From owner-linux-xfs@oss.sgi.com Wed Dec 4 09:17:52 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 09:17:54 -0800 (PST) Received: from phoenix.infradead.org (phoenix.mvhi.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4HHouR007808 for ; Wed, 4 Dec 2002 09:17:51 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18JdCl-0005kx-00; Wed, 04 Dec 2002 17:20:59 +0000 Date: Wed, 4 Dec 2002 17:20:59 +0000 From: Christoph Hellwig To: Christoph Bayer Cc: linux-xfs@oss.sgi.com Subject: Re: Unable to activate Quota on root filesystem Message-ID: <20021204172059.A22050@infradead.org> References: <01a801c29bb6$faa892e0$0a01a8c0@athlon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <01a801c29bb6$faa892e0$0a01a8c0@athlon>; from Christoph.Bayer@alpha.dyndns.tv on Wed, Dec 04, 2002 at 06:02:20PM +0100 X-archive-position: 1946 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Wed, Dec 04, 2002 at 06:02:20PM +0100, Christoph Bayer wrote: > Hello everybody, > > I am using kernel 2.4.20 + xfs cvs patch from 12/2/2002. I have > activated quota for linux and for the xfs filesystem. > I can activate quotasupport on all but the root partition. I get > the foloowing warning: > > Enabling group quota on root filesystem (reboot to take effect) > quotaon: quotactl on /dev/hde1: Invalid argument > Enabling user quota on root filesystem (reboot to take effect) > quotaon: quotactl on /dev/hde1: Invalid argument > > The root fs was created with 2.4.18 with xfs release 1.0.2... 2.4.18 with XFS 1.0.2? Where's that one from? :) Anyway, add rootflags=quota to your lilo/grub command line, the special casing for quotas on root has been removed in the CVS tree. Also make sure you update to quota-tools 3.0.8. From owner-linux-xfs@oss.sgi.com Wed Dec 4 11:01:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 11:01:05 -0800 (PST) Received: from beta (p5085B4A5.dip.t-dialin.net [80.133.180.165]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4J10uR013241 for ; Wed, 4 Dec 2002 11:01:01 -0800 Received: from athlon ([192.168.1.10]) by beta with smtp (Exim 3.35 #1 (Debian)) id 18JeoB-0000TN-00; Wed, 04 Dec 2002 20:03:43 +0100 Message-ID: <002301c29bc7$e1efedf0$0a01a8c0@athlon> From: "Christoph Bayer" To: Cc: "Christoph Hellwig" References: <01a801c29bb6$faa892e0$0a01a8c0@athlon> <20021204172059.A22050@infradead.org> Subject: Re: Unable to activate Quota on root filesystem Date: Wed, 4 Dec 2002 20:03:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 1947 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Christoph.Bayer@alpha.dyndns.tv Precedence: bulk X-list: linux-xfs Hello Christoph, > > The root fs was created with 2.4.18 with xfs release 1.0.2... > > 2.4.18 with XFS 1.0.2? Where's that one from? :) It is used for this Debian Boot CD (2.4.18 + XFS source patch 1.0.2): http://people.debian.org/~blade/XFS-Install/ > Anyway, add rootflags=quota to your lilo/grub command line, the > special casing for quotas on root has been removed in the CVS tree. > > Also make sure you update to quota-tools 3.0.8. Ok, that helped :-) I have update my quota tools to 3.0.7, this is the last Version I found in Debian. Are there maior changes from 3.0.7 to 3.0.8? Best regards, Christoph From owner-linux-xfs@oss.sgi.com Wed Dec 4 11:03:07 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 11:03:09 -0800 (PST) Received: from phoenix.infradead.org (carisma.slowglass.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4J36uR013659 for ; Wed, 4 Dec 2002 11:03:07 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18Jeqd-0006YS-00; Wed, 04 Dec 2002 19:06:15 +0000 Date: Wed, 4 Dec 2002 19:06:15 +0000 From: Christoph Hellwig To: Christoph Bayer Cc: linux-xfs@oss.sgi.com, Christoph Hellwig Subject: Re: Unable to activate Quota on root filesystem Message-ID: <20021204190615.A24875@infradead.org> References: <01a801c29bb6$faa892e0$0a01a8c0@athlon> <20021204172059.A22050@infradead.org> <002301c29bc7$e1efedf0$0a01a8c0@athlon> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <002301c29bc7$e1efedf0$0a01a8c0@athlon>; from Christoph.Bayer@alpha.dyndns.tv on Wed, Dec 04, 2002 at 08:03:21PM +0100 X-archive-position: 1948 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Wed, Dec 04, 2002 at 08:03:21PM +0100, Christoph Bayer wrote: > I have update my quota tools to 3.0.7, this is the last Version > I found in Debian. Are there maior changes from 3.0.7 to 3.0.8? Yes. Only quota-tools 3.0.8 can fully deal with the new xfs root quotas From owner-linux-xfs@oss.sgi.com Wed Dec 4 14:02:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 14:02:10 -0800 (PST) Received: from imf07bis.bellsouth.net (mail207.mail.bellsouth.net [205.152.58.147]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4M25uR010437 for ; Wed, 4 Dec 2002 14:02:05 -0800 Received: from TAZ2 ([66.156.1.10]) by imf07bis.bellsouth.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021204220659.BFKC20506.imf07bis.bellsouth.net@TAZ2> for ; Wed, 4 Dec 2002 17:06:59 -0500 Date: Wed, 4 Dec 2002 17:05:06 -0500 From: Greg Freemyer Subject: GCC and 1.2pre3 To: xfs mailing list Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain Message-Id: <20021204220659.BFKC20506.imf07bis.bellsouth.net@TAZ2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB4M26uR010438 X-archive-position: 1949 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs My test system is SuSE 8.0 based and it comes with GCC 2.95.3 It seems to compile reasonable CVS kernels. I am trying to load XFS 1.2pre3 onto it. When I do a "rpm --rebuild kernel-2.4.19-SGI_XFS_1.2pre3.src.rpm" I get: === david:/data2/XFS source # rpm --rebuild kernel-2.4.19-SGI_XFS_1.2pre3.src.rpm Installing kernel-2.4.19-SGI_XFS_1.2pre3.src.rpm error: failed build dependencies: modutils >= 2.4.18 is needed by kernel-2.4.19-SGI_XFS_1.2pre3 dev is needed by kernel-2.4.19-SGI_XFS_1.2pre3 gcc >= 2.96-98 is needed by kernel-2.4.19-SGI_XFS_1.2pre3 === So what is the recommended compiler? And is it available from http://gcc.gnu.org/releases.html, because there is not a 2.96 listed. Also, where do I get the package "dev". TIA, Greg ========= Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Wed Dec 4 14:06:40 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 04 Dec 2002 14:06:44 -0800 (PST) Received: from phoenix.infradead.org (carisma.slowglass.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB4M6duR010899 for ; Wed, 4 Dec 2002 14:06:39 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18JhiH-0008MX-00; Wed, 04 Dec 2002 22:09:49 +0000 Date: Wed, 4 Dec 2002 22:09:49 +0000 From: Christoph Hellwig To: Greg Freemyer Cc: xfs mailing list Subject: Re: GCC and 1.2pre3 Message-ID: <20021204220948.A32083@infradead.org> References: <20021204220659.BFKC20506.imf07bis.bellsouth.net@TAZ2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20021204220659.BFKC20506.imf07bis.bellsouth.net@TAZ2>; from freemyer@NorcrossGroup.com on Wed, Dec 04, 2002 at 05:05:06PM -0500 X-archive-position: 1950 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Wed, Dec 04, 2002 at 05:05:06PM -0500, Greg Freemyer wrote: > > My test system is SuSE 8.0 based and it comes with GCC 2.95.3 > > It seems to compile reasonable CVS kernels. > > I am trying to load XFS 1.2pre3 onto it. > > When I do a "rpm --rebuild kernel-2.4.19-SGI_XFS_1.2pre3.src.rpm" I get: The XFS kernel RPMs are specific to redhat. Just patch xfs into a normal source tree and use that. It might also be worth to try a make rpm in the toplevel kernel source dir, but I'm not sure whether that works with SuSE diverged rpm setup. From owner-linux-xfs@oss.sgi.com Thu Dec 5 02:08:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 02:08:08 -0800 (PST) Received: from alphaserv2.aei-potsdam.mpg.de (alphaserv2.aei-potsdam.mpg.de [194.94.224.102]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5A7xuR020217 for ; Thu, 5 Dec 2002 02:08:03 -0800 Received: from aei.mpg.de (holodec19.aei-potsdam.mpg.de [194.94.224.150]) by alphaserv2.aei-potsdam.mpg.de (8.9.1a/8.9.1) with ESMTP id LAA08287 for ; Thu, 5 Dec 2002 11:11:06 +0100 (MET) Message-ID: <3DEF263A.5F750276@aei.mpg.de> Date: Thu, 05 Dec 2002 11:11:06 +0100 From: Steffen Grunewald Organization: MPI fuer Gravitationsphysik Potsdam-Golm X-Mailer: Mozilla 4.75 [en] (X11; U; OSF1 V4.0 alpha) X-Accept-Language: en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: XFS patches for 2.4.20? Content-Type: text/plain; charset=iso-8859-15 X-MIME-Autoconverted: from 8bit to quoted-printable by alphaserv2.aei-potsdam.mpg.de id LAA08287 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB5A85uR020224 X-archive-position: 1951 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: steffen.grunewald@aei-potsdam.mpg.de Precedence: bulk X-list: linux-xfs Hello, will there be XFS patches for the 2.4.20 kernel available soon? We're using XFS on a huge computer cluster and have to fix some driver problems (network-wise) by upgrading to 2.4.20 RSN... Would the 2.4.19 patches apply cleanly (1.2pre3) ? Best, Steffen -- Steffen Grunewald * * * Merlin cluster admin (http://pandora.aei.mpg.de) MPI fr Gravitationsphysik (Albert-Einstein-Institut) Am Mhlenberg 1, 14476 Golm, Germany (http://www.aei.mpg.de) e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298} From owner-linux-xfs@oss.sgi.com Thu Dec 5 02:20:08 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 02:20:12 -0800 (PST) Received: from iris.acsalaska.net (iris.slb.nwc.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5AK7uR020760 for ; Thu, 5 Dec 2002 02:20:07 -0800 Received: from erbenson.alaska.net (91-pm30.nwc.alaska.net [209.112.158.91]) by iris.acsalaska.net (8.12.5/8.12.5) with ESMTP id gB5ANJi1042929 for ; Thu, 5 Dec 2002 01:23:19 -0900 (AKST) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 72AE43A17 for ; Thu, 5 Dec 2002 01:23:18 -0900 (AKST) Received: by plato.local.lan (Postfix, from userid 1000) id 4B0F74104E2; Thu, 5 Dec 2002 01:23:18 -0900 (AKST) Date: Thu, 5 Dec 2002 01:23:18 -0900 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: XFS patches for 2.4.20? Message-ID: <20021205102318.GD21273@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <3DEF263A.5F750276@aei.mpg.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZARJHfwaSJQLOEUz" Content-Disposition: inline In-Reply-To: <3DEF263A.5F750276@aei.mpg.de> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-archive-position: 1952 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs --ZARJHfwaSJQLOEUz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 05, 2002 at 11:11:06AM +0100, Steffen Grunewald wrote: > Hello, >=20 > will there be XFS patches for the 2.4.20 kernel available soon? > We're using XFS on a huge computer cluster and have to fix some > driver problems (network-wise) by upgrading to 2.4.20 RSN... there have been since 2.4.20 was released: ftp://oss.sgi.com/projects/xfs/download/patches/2.4.20/ > Would the 2.4.19 patches apply cleanly (1.2pre3) ? no i doubt it, and even if they did it would be a very bad idea (there are often changes which affect XFS but don't directly conflict with the patches, so you don't immediatly see the problem, until its too late). note the above patches are a cvs snapshot taken on 11/29. i won't speak for SGI but my read is 1.2 release will only support 2.4.19. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --ZARJHfwaSJQLOEUz 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 iEYEARECAAYFAj3vKRYACgkQJKx7GixEevx9NgCfVm14KTMCSTcAHFRqfLlIU9ng QlgAn0p7+Dvnoj3apqFPtVdwkomE/ycK =5L8s -----END PGP SIGNATURE----- --ZARJHfwaSJQLOEUz-- From owner-linux-xfs@oss.sgi.com Thu Dec 5 02:20:21 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 02:20:23 -0800 (PST) Received: from zork.zork.net (mail@zork.zork.net [66.92.188.166]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5AKLuR020849 for ; Thu, 5 Dec 2002 02:20:21 -0800 Received: from sneakums by zork.zork.net with local (Exim 3.35 #1 (Debian)) id 18JtAM-0005G5-00; Thu, 05 Dec 2002 02:23:34 -0800 To: linux-xfs@oss.sgi.com Subject: Re: XFS patches for 2.4.20? References: <3DEF263A.5F750276@aei.mpg.de> From: Sean Neakums X-Worst-Pick-Up-Line-Ever: "Hey baby, wanna peer with my leafnode instance?" X-Message-Flag: Message text advisory: HEINOUS SELF-AGGRANDIZATION, ULTERIOR MOTIVES X-Mailer: Norman X-Groin-Mounted-Steering-Wheel: "Arrrr... it's driving me nuts!" X-Alameda: WHY DOESN'T ANYONE KNOW ABOUT ALAMEDA? IT'S RIGHT NEXT TO OAKLAND!!! Organization: The Emadonics Institute Mail-Followup-To: linux-xfs@oss.sgi.com Date: Thu, 05 Dec 2002 10:23:34 +0000 In-Reply-To: <3DEF263A.5F750276@aei.mpg.de> (Steffen Grunewald's message of "Thu, 05 Dec 2002 11:11:06 +0100") Message-ID: <6u7keozrvd.fsf@zork.zork.net> User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-debian-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 1953 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sneakums@zork.net Precedence: bulk X-list: linux-xfs commence Steffen Grunewald quotation: > will there be XFS patches for the 2.4.20 kernel available soon? There are CVS snapshot patches here: ftp://oss.sgi.com/projects/xfs/download/patches/2.4.20/ -- / | [|] Sean Neakums | Questions are a burden to others; [|] | answers a prison for oneself. \ | From owner-linux-xfs@oss.sgi.com Thu Dec 5 03:18:10 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 03:18:12 -0800 (PST) Received: from alanis.wronline.net (alanis.wronline.net [213.252.139.70]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5BI9uR023260 for ; Thu, 5 Dec 2002 03:18:10 -0800 Received: (qmail 7034 invoked from network); 5 Dec 2002 11:21:21 -0000 Received: from servnix.wronline.de (80.65.32.162) by alanis.wronline.net with QMQP; 5 Dec 2002 11:21:21 -0000 Message-ID: <20021205112049.16873.qmail@lolita.WRonline.de> Date: Thu, 5 Dec 2002 12:20:49 +0100 To: linux-xfs@oss.sgi.com Subject: issues after xfs_growfs fixed since 2.4.19-2002-08-03_04:15_UTC? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-BND-Fodder: Heroin Bombe Echelon missile Plutonium iraq NSA Mitnick Chaos carnivore defense systems military attack elections policital embassy comint X-PGP-Id: 1024D/9F9F9022 2002-08-07 Stefan Paletta X-PGP-Fingerprint: DDDC B1DB 83BB F0D4 B2DB 8DAA 9404 2CCE 9F9F 9022 X-NCC-Regid: de.wronline From: Stefan Paletta X-Delivery-Agent: TMDA/0.59 X-archive-position: 1954 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stefanp-dated-1039519249.8e74af@cabal1.com Precedence: bulk X-list: linux-xfs Dear all, on two out of two occasions when I performed xfs_growfs, processes would get stuck in D state when accessing some areas of xfs file- systems (those not touched by the xfs_growfs) starting some hours after the xfs_growfs run. No oops or kernel messages occured. I am preparing to test Release-1.2.0-pre3 but I was wondering if this problem was known and possibly fixed since. Running 2.4.19 SMP on an UP i686 with XFS 2.4.19-2002-08-03_04:15_UTC; LVM on 3ware RAID; compiled with gcc 2.95.3; xfsprogs 2.2.2. -Stefan From owner-linux-xfs@oss.sgi.com Thu Dec 5 06:24:52 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 06:24:56 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5EOpuR004996 for ; Thu, 5 Dec 2002 06:24:52 -0800 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5EX4kq013623 for ; Thu, 5 Dec 2002 08:33:05 -0600 Received: from Liberator (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id GAA25666; Thu, 5 Dec 2002 06:27:27 -0800 (PST) Subject: Re: issues after xfs_growfs fixed since 2.4.19-2002-08-03_04:15_UTC? From: Eric Sandeen To: Stefan Paletta Cc: linux-xfs@oss.sgi.com In-Reply-To: <20021205112049.16873.qmail@lolita.WRonline.de> References: <20021205112049.16873.qmail@lolita.WRonline.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 05 Dec 2002 08:27:23 -0600 Message-Id: <1039098445.26230.16.camel@Liberator> Mime-Version: 1.0 X-archive-position: 1955 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs I don't think this is a known problem; if it still exists in the 1.2-pre3 kernel please let us know, and if you have a repeatable testcase please include that info as well. Thanks, -Eric On Thu, 2002-12-05 at 05:20, Stefan Paletta wrote: > Dear all, > > on two out of two occasions when I performed xfs_growfs, processes > would get stuck in D state when accessing some areas of xfs file- > systems (those not touched by the xfs_growfs) starting some hours > after the xfs_growfs run. No oops or kernel messages occured. > I am preparing to test Release-1.2.0-pre3 but I was wondering if > this problem was known and possibly fixed since. > > Running 2.4.19 SMP on an UP i686 with XFS 2.4.19-2002-08-03_04:15_UTC; > LVM on 3ware RAID; compiled with gcc 2.95.3; xfsprogs 2.2.2. > > -Stefan > From owner-linux-xfs@oss.sgi.com Thu Dec 5 06:38:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 06:38:39 -0800 (PST) Received: from 31.05.41.05 (pcp862617pcs.proctr01.fl.comcast.net [68.56.112.143]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5EcWuR005516 for ; Thu, 5 Dec 2002 06:38:33 -0800 Message-Id: <200212051438.gB5EcWuR005516@oss.sgi.com> From: "Avatier.com" To: linux-xfs@oss.sgi.com Reply-To: avatier@hotmail.com Subject: CLOSE YOUR NUMBER #1 SECURITY HOLE Date: Thu, 05 Dec 2002 07:05:42 -0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="6a7039d9-7585-4e3e-8abb-027bd5ba8547" X-archive-position: 1956 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: avatier@hotmail.com Precedence: bulk X-list: linux-xfs This is a multi-part message in MIME format --6a7039d9-7585-4e3e-8abb-027bd5ba8547 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable www.passwordbouncer.com/stophackers After all the security measures taken to make your network impenetrable, th= ere is one liability could undermine your entire operation. Allowing weak network logon password policies on your network is like givin= g a stranger the keys to the front door of your home. Strict logon password= policy is your first line of defense. Password Bouncer delivers stronger password enforcement than Win2K/NT, by p= reventing users from selecting vulnerable passwords that can be easily gues= sed or cracked by hackers. Passwords are screened and validated against a 3= 00,000-word English wordlist and a 4,000-word proper noun wordlist in addit= ion to highly configurable password rules. START DEFEATING HACKERS TODAY, DOWNLOAD YOUR FREE TRIAL NOW: www.passwordbo= uncer.com/stophackers Remove yourself from our email list by: Sending a blank email to the following address: unsubscribe@avatier.com=20= =20=20 --6a7039d9-7585-4e3e-8abb-027bd5ba8547-- From owner-linux-xfs@oss.sgi.com Thu Dec 5 08:41:11 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 08:41:16 -0800 (PST) Received: from mailbox.office.aol.com (x98A3A058.pix.aol.com [152.163.160.88]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5GfBuR012493 for ; Thu, 5 Dec 2002 08:41:11 -0800 Received: from PCSN653911 (dhcp0-031-094.office.aol.com [10.0.31.94]) by mailbox.office.aol.com (8.9.3 (PHNE_18979)/8.9.3) with SMTP id LAA20183 for ; Thu, 5 Dec 2002 11:44:19 -0500 (EST) From: "N. Richard Solis" To: Subject: Clustered XFS? Date: Thu, 5 Dec 2002 11:43:20 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-archive-position: 1957 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nrsolis@aol.net Precedence: bulk X-list: linux-xfs Is anyone working on adding clustering/SAN support to XFS on Linux? I was looking at the GFS software from Sistina and the OpenGFS project. I'm wondering if it's possible to merge the codebases of XFS and OpenGFS to provide the clustering functionality on XFS. Am I crazy? From owner-linux-xfs@oss.sgi.com Thu Dec 5 08:47:41 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 08:47:44 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5GlfuR013477 for ; Thu, 5 Dec 2002 08:47:41 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5FtCKp000905 for ; Thu, 5 Dec 2002 07:55:12 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA58411; Thu, 5 Dec 2002 10:50:48 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id KAA69841; Thu, 5 Dec 2002 10:50:48 -0600 (CST) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id gB5GomP03972; Thu, 5 Dec 2002 10:50:48 -0600 Subject: Re: Clustered XFS? From: Steve Lord To: "N. Richard Solis" Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1039107047.1726.4.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 05 Dec 2002 10:50:47 -0600 X-archive-position: 1958 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > Is anyone working on adding clustering/SAN support to XFS on Linux? > > I was looking at the GFS software from Sistina and the OpenGFS project. I'm > wondering if it's possible to merge the codebases of XFS and OpenGFS to > provide the clustering functionality on XFS. Am I crazy? Go look for CXFS on SGI's home page. There will be something available for Linux, but it will not be open source, and what parts of it are available for hardware other than SGI's is under discussion. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 09:10:38 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 09:10:43 -0800 (PST) Received: from mail.aem.umn.edu (mail.aem.umn.edu [128.101.142.239]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5HAbuR016564 for ; Thu, 5 Dec 2002 09:10:38 -0800 Received: from lightning.aem.umn.edu (lightning.aem.umn.edu [128.101.143.49]) by mail.aem.umn.edu (8.11.3/8.11.3) with ESMTP id gB5HDni26032; Thu, 5 Dec 2002 11:13:49 -0600 (CST) (envelope-from muno@aem.umn.edu) Received: (from muno@localhost) by lightning.aem.umn.edu (8.11.6/8.9.1) id gB5HDp818878; Thu, 5 Dec 2002 11:13:51 -0600 Date: Thu, 5 Dec 2002 11:13:51 -0600 From: Ray Muno To: Steve Lord Cc: "N. Richard Solis" , linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? Message-ID: <20021205171351.GJ17923@aem.umn.edu> References: <1039107047.1726.4.camel@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1039107047.1726.4.camel@jen.americas.sgi.com> User-Agent: Mutt/1.5.1i X-archive-position: 1959 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: muno@aem.umn.edu Precedence: bulk X-list: linux-xfs The promise of a Linux client has been out there as long as CXFS has been around as far as I recall. When is it going to materialize? It has seemed strange to me that SGI can Support Solaris and Windows NT with this environment but Linux support has never been made available. On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > I was looking at the GFS software from Sistina and the OpenGFS project. I'm > > wondering if it's possible to merge the codebases of XFS and OpenGFS to > > provide the clustering functionality on XFS. Am I crazy? > > Go look for CXFS on SGI's home page. There will be something available > for Linux, but it will not be open source, and what parts of it are > available for hardware other than SGI's is under discussion. > > Steve > > -- > > Steve Lord voice: +1-651-683-3511 > Principal Engineer, Filesystem Software email: lord@sgi.com > ============================================================================= Ray Muno http://www.aem.umn.edu/people/staff/muno University of Minnesota e-mail: muno@aem.umn.edu Aerospace Engineering and Mechanics Phone: (612) 625-9531 110 Union St. S.E. FAX: (612) 626-1558 Minneapolis, Mn 55455 ============================================================================= From owner-linux-xfs@oss.sgi.com Thu Dec 5 09:15:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 09:15:37 -0800 (PST) Received: from HPTI_MAIN.hpti.com ([208.20.6.213]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5HFVuR017423 for ; Thu, 5 Dec 2002 09:15:32 -0800 Received: by hpti_main.hpti.com with Internet Mail Service (5.5.2653.19) id ; Thu, 5 Dec 2002 11:59:14 -0500 Message-ID: <22699FB2708ED611ADA100105AC5C9A05B02C6@hpti_main.hpti.com> From: "Tierney, Craig" To: "'Ray Muno '" , "'Steve Lord '" Cc: "'N. Richard Solis '" , "'linux-xfs@oss.sgi.com '" Subject: RE: Clustered XFS? Date: Thu, 5 Dec 2002 11:59:13 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 1887 X-archive-position: 1960 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ctierney@HPTI.com Precedence: bulk X-list: linux-xfs SGI demoed the linux client at SC2002. The server though is still not ready. I think the person I talked to said 'in 6 months' but I could be off there. Craig -----Original Message----- From: Ray Muno To: Steve Lord Cc: N. Richard Solis; linux-xfs@oss.sgi.com Sent: 12/5/02 12:13 PM Subject: Re: Clustered XFS? The promise of a Linux client has been out there as long as CXFS has been around as far as I recall. When is it going to materialize? It has seemed strange to me that SGI can Support Solaris and Windows NT with this environment but Linux support has never been made available. On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > I was looking at the GFS software from Sistina and the OpenGFS project. I'm > > wondering if it's possible to merge the codebases of XFS and OpenGFS to > > provide the clustering functionality on XFS. Am I crazy? > > Go look for CXFS on SGI's home page. There will be something available > for Linux, but it will not be open source, and what parts of it are > available for hardware other than SGI's is under discussion. > > Steve > > -- > > Steve Lord voice: +1-651-683-3511 > Principal Engineer, Filesystem Software email: lord@sgi.com > ======================================================================== ===== Ray Muno http://www.aem.umn.edu/people/staff/muno University of Minnesota e-mail: muno@aem.umn.edu Aerospace Engineering and Mechanics Phone: (612) 625-9531 110 Union St. S.E. FAX: (612) 626-1558 Minneapolis, Mn 55455 ======================================================================== ===== [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Thu Dec 5 09:23:06 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 09:23:07 -0800 (PST) Received: from mailbox.office.aol.com (x98A3A058.pix.aol.com [152.163.160.88]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5HN5uR019264 for ; Thu, 5 Dec 2002 09:23:05 -0800 Received: from PCSN653911 (dhcp0-031-094.office.aol.com [10.0.31.94]) by mailbox.office.aol.com (8.9.3 (PHNE_18979)/8.9.3) with SMTP id MAA25950; Thu, 5 Dec 2002 12:23:22 -0500 (EST) From: "N. Richard Solis" To: "Tierney, Craig" , "'Ray Muno '" , "'Steve Lord '" Cc: Subject: RE: Clustered XFS? Date: Thu, 5 Dec 2002 12:22:31 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <22699FB2708ED611ADA100105AC5C9A05B02C6@hpti_main.hpti.com> X-archive-position: 1961 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nrsolis@aol.net Precedence: bulk X-list: linux-xfs Client? Server? Please correct me if I'm wrong but should there be a distinction? My understanding of CXFS was that there were enhancements made to XFS to cupport concurrent access to a storage pool via a SAN. To do this, you'd need locking/recovery, and some way to ensure that metadata changes were visible to all the servers that had the same filesystem mounted. Where does a client fit into all of this? -----Original Message----- From: linux-xfs-bounce@oss.sgi.com [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig Sent: Thursday, December 05, 2002 11:59 AM To: 'Ray Muno '; 'Steve Lord ' Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' Subject: RE: Clustered XFS? SGI demoed the linux client at SC2002. The server though is still not ready. I think the person I talked to said 'in 6 months' but I could be off there. Craig -----Original Message----- From: Ray Muno To: Steve Lord Cc: N. Richard Solis; linux-xfs@oss.sgi.com Sent: 12/5/02 12:13 PM Subject: Re: Clustered XFS? The promise of a Linux client has been out there as long as CXFS has been around as far as I recall. When is it going to materialize? It has seemed strange to me that SGI can Support Solaris and Windows NT with this environment but Linux support has never been made available. On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > I was looking at the GFS software from Sistina and the OpenGFS project. I'm > > wondering if it's possible to merge the codebases of XFS and OpenGFS to > > provide the clustering functionality on XFS. Am I crazy? > > Go look for CXFS on SGI's home page. There will be something available > for Linux, but it will not be open source, and what parts of it are > available for hardware other than SGI's is under discussion. > > Steve > > -- > > Steve Lord voice: +1-651-683-3511 > Principal Engineer, Filesystem Software email: lord@sgi.com > ======================================================================== ===== Ray Muno http://www.aem.umn.edu/people/staff/muno University of Minnesota e-mail: muno@aem.umn.edu Aerospace Engineering and Mechanics Phone: (612) 625-9531 110 Union St. S.E. FAX: (612) 626-1558 Minneapolis, Mn 55455 ======================================================================== ===== [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Thu Dec 5 09:55:27 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 09:55:32 -0800 (PST) Received: from mailbox.office.aol.com (x98A3A058.pix.aol.com [152.163.160.88]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5HtRuR024156 for ; Thu, 5 Dec 2002 09:55:27 -0800 Received: from PCSN653911 (dhcp0-031-094.office.aol.com [10.0.31.94]) by mailbox.office.aol.com (8.9.3 (PHNE_18979)/8.9.3) with SMTP id MAA29961; Thu, 5 Dec 2002 12:55:00 -0500 (EST) From: "N. Richard Solis" To: "Craig Tierney" Cc: "'Ray Muno '" , "'Steve Lord '" , Subject: RE: Clustered XFS? Date: Thu, 5 Dec 2002 12:54:30 -0500 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20021205174104.GB16809@hpti.com> X-archive-position: 1962 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nrsolis@aol.net Precedence: bulk X-list: linux-xfs Sounds more like a Clustered NFS solution to me? Would I be on target with that one? -----Original Message----- From: Craig Tierney [mailto:ctierney@hpti.com] Sent: Thursday, December 05, 2002 12:41 PM To: N. Richard Solis Cc: 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? The client provides the interface so that when a user does a read or write, it translates the commands. The server takes care of the layout and locking (if supported). Right now you can have a linux box access the shared filesystem, but you still need an Irix box to take care of the metadata and locking. I have not worked with CXFS, so I might have exact terminology wrong but I think I have the idea right. Craig On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: > Client? Server? Please correct me if I'm wrong but should there be a > distinction? My understanding of CXFS was that there were enhancements made > to XFS to cupport concurrent access to a storage pool via a SAN. To do > this, you'd need locking/recovery, and some way to ensure that metadata > changes were visible to all the servers that had the same filesystem > mounted. Where does a client fit into all of this? > > > -----Original Message----- > From: linux-xfs-bounce@oss.sgi.com > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig > Sent: Thursday, December 05, 2002 11:59 AM > To: 'Ray Muno '; 'Steve Lord ' > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' > Subject: RE: Clustered XFS? > > > > SGI demoed the linux client at SC2002. The server though is still not > ready. I think the person I talked to said 'in 6 months' but I could > be off there. > > Craig > -----Original Message----- > From: Ray Muno > To: Steve Lord > Cc: N. Richard Solis; linux-xfs@oss.sgi.com > Sent: 12/5/02 12:13 PM > Subject: Re: Clustered XFS? > > The promise of a Linux client has been out there as long as CXFS has > been > around as far as I recall. When is it going to materialize? > > It has seemed strange to me that SGI can Support Solaris and Windows NT > with this environment but Linux support has never been made available. > > > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > > > I was looking at the GFS software from Sistina and the OpenGFS > project. I'm > > > wondering if it's possible to merge the codebases of XFS and OpenGFS > to > > > provide the clustering functionality on XFS. Am I crazy? > > > > Go look for CXFS on SGI's home page. There will be something available > > for Linux, but it will not be open source, and what parts of it are > > available for hardware other than SGI's is under discussion. > > > > Steve > > > > -- > > > > Steve Lord voice: +1-651-683-3511 > > Principal Engineer, Filesystem Software email: lord@sgi.com > > > ======================================================================== > ===== > > Ray Muno > http://www.aem.umn.edu/people/staff/muno > University of Minnesota e-mail: > muno@aem.umn.edu > Aerospace Engineering and Mechanics Phone: (612) > 625-9531 > 110 Union St. S.E. FAX: (612) > 626-1558 > Minneapolis, Mn 55455 > > ======================================================================== > ===== > > > > > > > [[HTML alternate version deleted]] > > > > > -- Craig Tierney (ctierney@hpti.com) From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:05:25 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:05:27 -0800 (PST) Received: from phoenix.infradead.org (phoenix.infradead.org [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5I5OuR025855 for ; Thu, 5 Dec 2002 10:05:25 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18K0QM-0000EH-00; Thu, 05 Dec 2002 18:08:34 +0000 Date: Thu, 5 Dec 2002 18:08:34 +0000 From: Christoph Hellwig To: "N. Richard Solis" Cc: Craig Tierney , "'Ray Muno '" , "'Steve Lord '" , linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? Message-ID: <20021205180834.A724@infradead.org> References: <20021205174104.GB16809@hpti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from nrsolis@aol.net on Thu, Dec 05, 2002 at 12:54:30PM -0500 X-archive-position: 1963 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Thu, Dec 05, 2002 at 12:54:30PM -0500, N. Richard Solis wrote: > Sounds more like a Clustered NFS solution to me? Would I be on target with > that one? I suggest you contact your SGI sales representative. At least the ones next to me seem to like talking about cxfs a lot.. From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:43:41 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:43:44 -0800 (PST) Received: from woody.fsl.noaa.gov (woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5IheuR031073 for ; Thu, 5 Dec 2002 10:43:41 -0800 Received: from woody.fsl.noaa.gov (woody.fsl.noaa.gov [127.0.0.1]) by woody.fsl.noaa.gov (8.12.5/8.12.5) with ESMTP id gB5Iksbl016859; Thu, 5 Dec 2002 11:46:54 -0700 Received: (from tierney@localhost) by woody.fsl.noaa.gov (8.12.5/8.12.5/Submit) id gB5Ikss2016857; Thu, 5 Dec 2002 11:46:54 -0700 Date: Thu, 5 Dec 2002 11:46:53 -0700 From: Craig Tierney To: "N. Richard Solis" Cc: linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? Message-ID: <20021205184653.GC16117@hpti.com> References: <20021205174104.GB16809@hpti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-archive-position: 1964 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ctierney@hpti.com Precedence: bulk X-list: linux-xfs I have heard the term clustered NFS but I have never seen an actual implementation. In a clustered NFS solution, is every node actually talking SCSI (Fibre channel usually) to the disk? That is what CXFS is doing. Each node physically hits each disk. The metadata server keep track of what everyone is doing and prevents them from stomping on each other. Craig On Thu, Dec 05, 2002 at 12:54:30PM -0500, N. Richard Solis wrote: > Sounds more like a Clustered NFS solution to me? Would I be on target with > that one? > > -----Original Message----- > From: Craig Tierney [mailto:ctierney@hpti.com] > Sent: Thursday, December 05, 2002 12:41 PM > To: N. Richard Solis > Cc: 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com > Subject: Re: Clustered XFS? > > > The client provides the interface so that when a user does a read > or write, it translates the commands. The server takes care of the layout > and locking (if supported). Right now you can have a linux box access > the shared filesystem, but you still need an Irix box to take care of > the metadata and locking. > > I have not worked with CXFS, so I might have exact terminology wrong > but I think I have the idea right. > > Craig > > On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: > > Client? Server? Please correct me if I'm wrong but should there be a > > distinction? My understanding of CXFS was that there were enhancements > made > > to XFS to cupport concurrent access to a storage pool via a SAN. To do > > this, you'd need locking/recovery, and some way to ensure that metadata > > changes were visible to all the servers that had the same filesystem > > mounted. Where does a client fit into all of this? > > > > > > -----Original Message----- > > From: linux-xfs-bounce@oss.sgi.com > > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig > > Sent: Thursday, December 05, 2002 11:59 AM > > To: 'Ray Muno '; 'Steve Lord ' > > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' > > Subject: RE: Clustered XFS? > > > > > > > > SGI demoed the linux client at SC2002. The server though is still not > > ready. I think the person I talked to said 'in 6 months' but I could > > be off there. > > > > Craig > > -----Original Message----- > > From: Ray Muno > > To: Steve Lord > > Cc: N. Richard Solis; linux-xfs@oss.sgi.com > > Sent: 12/5/02 12:13 PM > > Subject: Re: Clustered XFS? > > > > The promise of a Linux client has been out there as long as CXFS has > > been > > around as far as I recall. When is it going to materialize? > > > > It has seemed strange to me that SGI can Support Solaris and Windows NT > > with this environment but Linux support has never been made available. > > > > > > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > > > > > I was looking at the GFS software from Sistina and the OpenGFS > > project. I'm > > > > wondering if it's possible to merge the codebases of XFS and OpenGFS > > to > > > > provide the clustering functionality on XFS. Am I crazy? > > > > > > Go look for CXFS on SGI's home page. There will be something available > > > for Linux, but it will not be open source, and what parts of it are > > > available for hardware other than SGI's is under discussion. > > > > > > Steve > > > > > > -- > > > > > > Steve Lord voice: +1-651-683-3511 > > > Principal Engineer, Filesystem Software email: lord@sgi.com > > > > > ======================================================================== > > ===== > > > > Ray Muno > > http://www.aem.umn.edu/people/staff/muno > > University of Minnesota e-mail: > > muno@aem.umn.edu > > Aerospace Engineering and Mechanics Phone: (612) > > 625-9531 > > 110 Union St. S.E. FAX: (612) > > 626-1558 > > Minneapolis, Mn 55455 > > > > ======================================================================== > > ===== > > > > > > > > > > > > > > [[HTML alternate version deleted]] > > > > > > > > > > > > -- > Craig Tierney (ctierney@hpti.com) > > > -- Craig Tierney (ctierney@hpti.com) From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:46:53 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:46:55 -0800 (PST) Received: from mailbox.office.aol.com (x98A3A058.pix.aol.com [152.163.160.88]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5IkruR031793 for ; Thu, 5 Dec 2002 10:46:53 -0800 Received: from PCSN653911 (dhcp0-031-094.office.aol.com [10.0.31.94]) by mailbox.office.aol.com (8.9.3 (PHNE_18979)/8.9.3) with SMTP id NAA08150; Thu, 5 Dec 2002 13:50:01 -0500 (EST) From: "N. Richard Solis" To: "Craig Tierney" Cc: Subject: RE: Clustered XFS? Date: Thu, 5 Dec 2002 13:49:16 -0500 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20021205184653.GC16117@hpti.com> X-archive-position: 1965 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nrsolis@aol.net Precedence: bulk X-list: linux-xfs So it's more like DAFS then? -----Original Message----- From: linux-xfs-bounce@oss.sgi.com [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Craig Tierney Sent: Thursday, December 05, 2002 1:47 PM To: N. Richard Solis Cc: linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? I have heard the term clustered NFS but I have never seen an actual implementation. In a clustered NFS solution, is every node actually talking SCSI (Fibre channel usually) to the disk? That is what CXFS is doing. Each node physically hits each disk. The metadata server keep track of what everyone is doing and prevents them from stomping on each other. Craig On Thu, Dec 05, 2002 at 12:54:30PM -0500, N. Richard Solis wrote: > Sounds more like a Clustered NFS solution to me? Would I be on target with > that one? > > -----Original Message----- > From: Craig Tierney [mailto:ctierney@hpti.com] > Sent: Thursday, December 05, 2002 12:41 PM > To: N. Richard Solis > Cc: 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com > Subject: Re: Clustered XFS? > > > The client provides the interface so that when a user does a read > or write, it translates the commands. The server takes care of the layout > and locking (if supported). Right now you can have a linux box access > the shared filesystem, but you still need an Irix box to take care of > the metadata and locking. > > I have not worked with CXFS, so I might have exact terminology wrong > but I think I have the idea right. > > Craig > > On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: > > Client? Server? Please correct me if I'm wrong but should there be a > > distinction? My understanding of CXFS was that there were enhancements > made > > to XFS to cupport concurrent access to a storage pool via a SAN. To do > > this, you'd need locking/recovery, and some way to ensure that metadata > > changes were visible to all the servers that had the same filesystem > > mounted. Where does a client fit into all of this? > > > > > > -----Original Message----- > > From: linux-xfs-bounce@oss.sgi.com > > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig > > Sent: Thursday, December 05, 2002 11:59 AM > > To: 'Ray Muno '; 'Steve Lord ' > > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' > > Subject: RE: Clustered XFS? > > > > > > > > SGI demoed the linux client at SC2002. The server though is still not > > ready. I think the person I talked to said 'in 6 months' but I could > > be off there. > > > > Craig > > -----Original Message----- > > From: Ray Muno > > To: Steve Lord > > Cc: N. Richard Solis; linux-xfs@oss.sgi.com > > Sent: 12/5/02 12:13 PM > > Subject: Re: Clustered XFS? > > > > The promise of a Linux client has been out there as long as CXFS has > > been > > around as far as I recall. When is it going to materialize? > > > > It has seemed strange to me that SGI can Support Solaris and Windows NT > > with this environment but Linux support has never been made available. > > > > > > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > > > > > I was looking at the GFS software from Sistina and the OpenGFS > > project. I'm > > > > wondering if it's possible to merge the codebases of XFS and OpenGFS > > to > > > > provide the clustering functionality on XFS. Am I crazy? > > > > > > Go look for CXFS on SGI's home page. There will be something available > > > for Linux, but it will not be open source, and what parts of it are > > > available for hardware other than SGI's is under discussion. > > > > > > Steve > > > > > > -- > > > > > > Steve Lord voice: +1-651-683-3511 > > > Principal Engineer, Filesystem Software email: lord@sgi.com > > > > > ======================================================================== > > ===== > > > > Ray Muno > > http://www.aem.umn.edu/people/staff/muno > > University of Minnesota e-mail: > > muno@aem.umn.edu > > Aerospace Engineering and Mechanics Phone: (612) > > 625-9531 > > 110 Union St. S.E. FAX: (612) > > 626-1558 > > Minneapolis, Mn 55455 > > > > ======================================================================== > > ===== > > > > > > > > > > > > > > [[HTML alternate version deleted]] > > > > > > > > > > > > -- > Craig Tierney (ctierney@hpti.com) > > > -- Craig Tierney (ctierney@hpti.com) From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:48:42 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:48:44 -0800 (PST) Received: from mx1.tippett.com (user-112vvgq.biz.mindspring.com [66.47.254.26]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5ImfuR032445 for ; Thu, 5 Dec 2002 10:48:42 -0800 Received: from hermes.tippett.com (hermes.tippett.com [192.168.2.20]) by mx1.tippett.com (Postfix) with ESMTP id 459731821224 for ; Thu, 5 Dec 2002 11:45:19 -0800 (PST) Received: from tippett.com (felix.tippett.com [192.168.2.32]) by hermes.tippett.com (980427.SGI.8.8.8/8.7.3) with ESMTP id KAA11984 for ; Thu, 5 Dec 2002 10:49:26 -0800 (PST) Message-ID: <3DEFA043.5080109@tippett.com> Date: Thu, 05 Dec 2002 10:51:47 -0800 From: Christian Rice Organization: Tippett Studio User-Agent: Mozilla/5.0 (X11; U; IRIX64 IP28; en-US; rv:1.1b) Gecko/20020723 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: latest i386 cmd_rpms and RedHat 7.3 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 1966 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xian@tippett.com Precedence: bulk X-list: linux-xfs Pardon me if this has been dealt with previously-- The i386 xfs progs seem to require a newer glibc, like that available on RedHat 8? error: failed dependencies: libc.so.6(GLIBC_2.3) is needed by attr-2.1.1-0 libc.so.6(GLIBC_2.3) is needed by xfsdump-2.2.4-0 libc.so.6(GLIBC_2.3) is needed by xfsprogs-2.3.6-0 Should I be updating my hundreds of machines to get this (not interested at this point due to production demands), or are my current versions considered nominally good for use with 2.4.20 and latest cvs snapshot kernel patches? Currently using: attr-2.0.11-0.i386.rpm xfsdump-2.2.1-0.i386.rpm xfsprogs-2.3.3-0.i386.rpm Hey--xfs has come a long way this year. Around May timeframe, we were losing a disk or two a day to xfs log corruption when workstations would crash (using A|W Maya). That data loss simply is not happening any more for us. Perhaps I don't need to update anything, but I'd like to have a few development machines to continually test things out, of course. -- christian rice director of technology tippett studio 510.649.9711 l--xr----- From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:48:48 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:48:50 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5ImluR032459 for ; Thu, 5 Dec 2002 10:48:48 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5HuIKp008685 for ; Thu, 5 Dec 2002 09:56:19 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA92698 for ; Thu, 5 Dec 2002 12:51:55 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA28767 for ; Thu, 5 Dec 2002 12:51:48 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB625pJ06557 for linux-xfs@oss.sgi.com; Thu, 5 Dec 2002 21:05:51 -0500 Resent-Message-Id: <200212060205.gB625pJ06557@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA01874 for ; Thu, 5 Dec 2002 12:48:32 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB5ImVQb26580077 for ; Thu, 5 Dec 2002 10:48:31 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB5IkmKK031539 for ; Thu, 5 Dec 2002 19:46:48 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB5Ikm35031538 for hch@sgi.com; Thu, 5 Dec 2002 19:46:48 +0100 Date: Thu, 5 Dec 2002 19:46:48 +0100 From: Christoph Hellwig Message-Id: <200212051846.gB5Ikm35031538@lab343.munich.sgi.com> Subject: TAKE - backport Hugh Dickins's loop fix from 2.5.48 To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Thu, 5 Dec 2002 21:05:51 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1967 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs This is needed to get working loop (and pass all QA tests again together with my next mod) Date: Thu Dec 5 10:45:46 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134449a linux/drivers/block/loop.c - 1.75 - fix sendfile use From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:49:41 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:49:43 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5InfuR000860 for ; Thu, 5 Dec 2002 10:49:41 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5HvCKp008758 for ; Thu, 5 Dec 2002 09:57:12 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA05536 for ; Thu, 5 Dec 2002 12:52:44 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA20122 for ; Thu, 5 Dec 2002 12:52:43 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB626kt06562 for linux-xfs@oss.sgi.com; Thu, 5 Dec 2002 21:06:46 -0500 Resent-Message-Id: <200212060206.gB626kt06562@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA31319 for ; Thu, 5 Dec 2002 12:51:56 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB5IpsQb39973846 for ; Thu, 5 Dec 2002 10:51:55 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB5IoCKK031603 for ; Thu, 5 Dec 2002 19:50:12 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB5IoCFi031602 for hch@sgi.com; Thu, 5 Dec 2002 19:50:12 +0100 Date: Thu, 5 Dec 2002 19:50:12 +0100 From: Christoph Hellwig Message-Id: <200212051850.gB5IoCFi031602@lab343.munich.sgi.com> Subject: TAKE - final sendfile bits To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Thu, 5 Dec 2002 21:06:46 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1968 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs This will let all QA tests pass again on 2.5. Date: Thu Dec 5 10:50:54 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134450a linux/fs/xfs/xfs_vnodeops.c - 1.575 - adds sendfile to the vnode operation vector linux/fs/xfs/linux/xfs_lrw.h - 1.32 - add an extern for xfs_sendfile linux/fs/xfs/linux/xfs_lrw.c - 1.178 - last fixups for xfs_sendfile From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:50:03 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:50:05 -0800 (PST) Received: from imf13bis.bellsouth.net (mail213.mail.bellsouth.net [205.152.58.153]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5Io2uR001131 for ; Thu, 5 Dec 2002 10:50:03 -0800 Received: from TAZ2 ([66.156.1.10]) by imf13bis.bellsouth.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021205185501.UCJU19084.imf13bis.bellsouth.net@TAZ2>; Thu, 5 Dec 2002 13:55:01 -0500 Date: Thu, 5 Dec 2002 13:53:08 -0500 From: Greg Freemyer Subject: re[2]: Clustered XFS? To: "N. Richard Solis" cc: Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain Message-Id: <20021205185501.UCJU19084.imf13bis.bellsouth.net@TAZ2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB5Io3uR001185 X-archive-position: 1969 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs I don't know cxfs, but it sounds like the Tru64 clustered filesystem, not like NFS. i.e. Access to data is distributed to all cluster members. Access to Meta-Data / Locking is handled by one node in the cluster. GFS/OpenGFS also fully distributes the meta-data updates, but relies on an external lock server. :( Greg >> Sounds more like a Clustered NFS solution to me? Would I be on target >> with >> that one? >> -----Original Message----- >> From: Craig Tierney [mailto:ctierney@hpti.com] >> Sent: Thursday, December 05, 2002 12:41 PM >> To: N. Richard Solis >> Cc: 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com >> Subject: Re: Clustered XFS? >> The client provides the interface so that when a user does a read >> or write, it translates the commands. The server takes care of the layout >> and locking (if supported). Right now you can have a linux box access >> the shared filesystem, but you still need an Irix box to take care of >> the metadata and locking. >> I have not worked with CXFS, so I might have exact terminology wrong >> but I think I have the idea right. >> Craig >> On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: >> > Client? Server? Please correct me if I'm wrong but should there be a >> > distinction? My understanding of CXFS was that there were enhancements >> made >> > to XFS to cupport concurrent access to a storage pool via a SAN. To do >> > this, you'd need locking/recovery, and some way to ensure that metadata >> > changes were visible to all the servers that had the same filesystem >> > mounted. Where does a client fit into all of this? >> > >> > >> > -----Original Message----- >> > From: linux-xfs-bounce@oss.sgi.com >> > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig >> > Sent: Thursday, December 05, 2002 11:59 AM >> > To: 'Ray Muno '; 'Steve Lord ' >> > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' >> > Subject: RE: Clustered XFS? >> > >> > >> > >> > SGI demoed the linux client at SC2002. The server though is still not >> > ready. I think the person I talked to said 'in 6 months' but I could >> > be off there. >> > >> > Craig >> > -----Original Message----- >> > From: Ray Muno >> > To: Steve Lord >> > Cc: N. Richard Solis; linux-xfs@oss.sgi.com >> > Sent: 12/5/02 12:13 PM >> > Subject: Re: Clustered XFS? >> > >> > The promise of a Linux client has been out there as long as CXFS has >> > been >> > around as far as I recall. When is it going to materialize? >> > >> > It has seemed strange to me that SGI can Support Solaris and Windows NT >> > with this environment but Linux support has never been made available. >> > >> > >> > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: >> > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: >> > > > Is anyone working on adding clustering/SAN support to XFS on Linux? >> > > > >> > > > I was looking at the GFS software from Sistina and the OpenGFS >> > project. I'm >> > > > wondering if it's possible to merge the codebases of XFS and OpenGFS >> > to >> > > > provide the clustering functionality on XFS. Am I crazy? >> > > >> > > Go look for CXFS on SGI's home page. There will be something available >> > > for Linux, but it will not be open source, and what parts of it are >> > > available for hardware other than SGI's is under discussion. >> > > >> > > Steve >> > > >> > > -- >> > > >> > > Steve Lord voice: +1-651-683-3511 >> > > Principal Engineer, Filesystem Software email: lord@sgi.com >> > > >> > ======================================================================== >> > ===== >> > >> > Ray Muno >> > http://www.aem.umn.edu/people/staff/muno >> > University of Minnesota e-mail: >> > muno@aem.umn.edu >> > Aerospace Engineering and Mechanics Phone: (612) >> > 625-9531 >> > 110 Union St. S.E. FAX: (612) >> > 626-1558 >> > Minneapolis, Mn 55455 >> > >> > ======================================================================== >> > ===== >> > >> > >> > >> > >> > >> > >> > [[HTML alternate version deleted]] >> > >> > >> > >> > >> > >> -- >> Craig Tierney (ctierney@hpti.com) Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:51:47 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:51:49 -0800 (PST) Received: from phoenix.infradead.org (phoenix.mvhi.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5IpkuR002137 for ; Thu, 5 Dec 2002 10:51:46 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18K19H-0000sE-00; Thu, 05 Dec 2002 18:54:59 +0000 Date: Thu, 5 Dec 2002 18:54:59 +0000 From: Christoph Hellwig To: Christian Rice Cc: linux-xfs@oss.sgi.com Subject: Re: latest i386 cmd_rpms and RedHat 7.3 Message-ID: <20021205185459.A3283@infradead.org> References: <3DEFA043.5080109@tippett.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3DEFA043.5080109@tippett.com>; from xian@tippett.com on Thu, Dec 05, 2002 at 10:51:47AM -0800 X-archive-position: 1970 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Thu, Dec 05, 2002 at 10:51:47AM -0800, Christian Rice wrote: > Pardon me if this has been dealt with previously-- > > The i386 xfs progs seem to require a newer glibc, like that available on > RedHat 8? Yes. > error: failed dependencies: > libc.so.6(GLIBC_2.3) is needed by attr-2.1.1-0 > libc.so.6(GLIBC_2.3) is needed by xfsdump-2.2.4-0 > libc.so.6(GLIBC_2.3) is needed by xfsprogs-2.3.6-0 > > Should I be updating my hundreds of machines to get this (not interested > at this point due to production demands), or are my current versions > considered nominally good for use with 2.4.20 and latest cvs snapshot > kernel patches? Currently using: > > attr-2.0.11-0.i386.rpm > xfsdump-2.2.1-0.i386.rpm > xfsprogs-2.3.3-0.i386.rpm They should be fine. ALternatively you can just rebuild the .src.rpms on older machines (at least any Red Hat 7.x should do it) From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:54:55 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:54:57 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5IstuR003034 for ; Thu, 5 Dec 2002 10:54:55 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5I2QKp009127 for ; Thu, 5 Dec 2002 10:02:26 -0800 Received: from localhost (mg@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id FAA27354; Fri, 6 Dec 2002 05:56:45 +1100 (EST) X-Authentication-Warning: snort.melbourne.sgi.com: mg owned process doing -bs Date: Fri, 6 Dec 2002 05:56:45 +1100 From: Mike Gigante X-X-Sender: mg@snort.melbourne.sgi.com To: Christoph Hellwig cc: "N. Richard Solis" , Craig Tierney , "'Ray Muno '" , "'Steve Lord '" , Subject: Re: Clustered XFS? In-Reply-To: <20021205180834.A724@infradead.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 1971 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mg@sgi.com Precedence: bulk X-list: linux-xfs On Thu, Dec 05, 2002 at 12:54:30PM -0500, N. Richard Solis wrote: > Sounds more like a Clustered NFS solution to me? Would I be on target with > that one? > No, In NFS data travels over the wire, in CXFS data is direct access via the SAN. NFS is not posix compliant, CXFS is. Think of CXFS as a local filesystem for all intensive puposes - both performance and semantics. The client/server distinction is only with respect to maintaining a coherent cluster-wide view of filesystem by providing consistency of metadata. There are some things that must be coordinated such as extent allocation, kernel filesystem caches, memory mapped files etc etc. The CXFS server is the gatekeeper in this respect. Apart from the consistency management both the CXFS client and server can be considered local XFS. Oh, and there is no single point of failure -- clients can become the server (if they are capable). There are some docs on the SGI website that describe CXFS. Check that out if you want more info. Mike From owner-linux-xfs@oss.sgi.com Thu Dec 5 10:55:41 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 10:55:43 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5ItfuR003388 for ; Thu, 5 Dec 2002 10:55:41 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5I3BKp009176 for ; Thu, 5 Dec 2002 10:03:12 -0800 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.232.87]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA11866; Thu, 5 Dec 2002 12:58:47 -0600 (CST) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 18K1Cx-000346-00; Thu, 05 Dec 2002 12:58:47 -0600 Date: Thu, 5 Dec 2002 12:58:47 -0600 From: Nathan Straz To: Christian Rice Cc: linux-xfs@oss.sgi.com Subject: Re: latest i386 cmd_rpms and RedHat 7.3 Message-ID: <20021205185847.GB8704@sgi.com> Mail-Followup-To: Christian Rice , linux-xfs@oss.sgi.com References: <3DEFA043.5080109@tippett.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DEFA043.5080109@tippett.com> User-Agent: Mutt/1.4i X-archive-position: 1972 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nstraz@sgi.com Precedence: bulk X-list: linux-xfs On Thu, Dec 05, 2002 at 10:51:47AM -0800, Christian Rice wrote: > The i386 xfs progs seem to require a newer glibc, like that available on > RedHat 8? Yes, we're compiling new user tools and kernel on RedHat 8. > Should I be updating my hundreds of machines to get this (not interested > at this point due to production demands), or are my current versions > considered nominally good for use with 2.4.20 and latest cvs snapshot > kernel patches? Currently using: > > attr-2.0.11-0.i386.rpm > xfsdump-2.2.1-0.i386.rpm > xfsprogs-2.3.3-0.i386.rpm I think you need to get an updated xfsdump rpm. What you can do is download the source rpms (in the SRPM directory) and run `rpmbuild --rebuild` on them. That should give you updated XFS tools for the release of RedHat you're using. -- 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 Dec 5 11:29:11 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 11:29:13 -0800 (PST) Received: from mailbox.office.aol.com (x98A3A058.pix.aol.com [152.163.160.88]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5JTAuR007799 for ; Thu, 5 Dec 2002 11:29:11 -0800 Received: from PCSN653911 (dhcp0-031-094.office.aol.com [10.0.31.94]) by mailbox.office.aol.com (8.9.3 (PHNE_18979)/8.9.3) with SMTP id OAA13884; Thu, 5 Dec 2002 14:31:38 -0500 (EST) From: "N. Richard Solis" To: "Greg Freemyer" Cc: Subject: RE: re[2]: Clustered XFS? Date: Thu, 5 Dec 2002 14:31:01 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: <20021205185501.UCJU19084.imf13bis.bellsouth.net@TAZ2> X-archive-position: 1973 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nrsolis@aol.net Precedence: bulk X-list: linux-xfs I think they were planning on using that DLM from IBM to replace their own lock server implementation. From what I can gather, IBM isn't puting any resources into that DLM project so I'm not sure where it stands. My only experience with Clustered Filesystems is with GFS. I guess what I'm trying to say is it worth exploring the possibility of adding some of those clustering features to Linux XFS? Using the OpenGFS code, the project could stay "open". Of course, not being a filesystem coding expert, I'm not the right person to judge the effort required. I was trying to see if anyone had thought about doing it or something similar. -----Original Message----- From: Greg Freemyer [mailto:freemyer@NorcrossGroup.com] Sent: Thursday, December 05, 2002 1:53 PM To: N. Richard Solis Cc: linux-xfs@oss.sgi.com Subject: re[2]: Clustered XFS? I don't know cxfs, but it sounds like the Tru64 clustered filesystem, not like NFS. i.e. Access to data is distributed to all cluster members. Access to Meta-Data / Locking is handled by one node in the cluster. GFS/OpenGFS also fully distributes the meta-data updates, but relies on an external lock server. :( Greg >> Sounds more like a Clustered NFS solution to me? Would I be on target >> with >> that one? >> -----Original Message----- >> From: Craig Tierney [mailto:ctierney@hpti.com] >> Sent: Thursday, December 05, 2002 12:41 PM >> To: N. Richard Solis >> Cc: 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com >> Subject: Re: Clustered XFS? >> The client provides the interface so that when a user does a read >> or write, it translates the commands. The server takes care of the layout >> and locking (if supported). Right now you can have a linux box access >> the shared filesystem, but you still need an Irix box to take care of >> the metadata and locking. >> I have not worked with CXFS, so I might have exact terminology wrong >> but I think I have the idea right. >> Craig >> On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: >> > Client? Server? Please correct me if I'm wrong but should there be a >> > distinction? My understanding of CXFS was that there were enhancements >> made >> > to XFS to cupport concurrent access to a storage pool via a SAN. To do >> > this, you'd need locking/recovery, and some way to ensure that metadata >> > changes were visible to all the servers that had the same filesystem >> > mounted. Where does a client fit into all of this? >> > >> > >> > -----Original Message----- >> > From: linux-xfs-bounce@oss.sgi.com >> > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig >> > Sent: Thursday, December 05, 2002 11:59 AM >> > To: 'Ray Muno '; 'Steve Lord ' >> > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' >> > Subject: RE: Clustered XFS? >> > >> > >> > >> > SGI demoed the linux client at SC2002. The server though is still not >> > ready. I think the person I talked to said 'in 6 months' but I could >> > be off there. >> > >> > Craig >> > -----Original Message----- >> > From: Ray Muno >> > To: Steve Lord >> > Cc: N. Richard Solis; linux-xfs@oss.sgi.com >> > Sent: 12/5/02 12:13 PM >> > Subject: Re: Clustered XFS? >> > >> > The promise of a Linux client has been out there as long as CXFS has >> > been >> > around as far as I recall. When is it going to materialize? >> > >> > It has seemed strange to me that SGI can Support Solaris and Windows NT >> > with this environment but Linux support has never been made available. >> > >> > >> > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: >> > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: >> > > > Is anyone working on adding clustering/SAN support to XFS on Linux? >> > > > >> > > > I was looking at the GFS software from Sistina and the OpenGFS >> > project. I'm >> > > > wondering if it's possible to merge the codebases of XFS and OpenGFS >> > to >> > > > provide the clustering functionality on XFS. Am I crazy? >> > > >> > > Go look for CXFS on SGI's home page. There will be something available >> > > for Linux, but it will not be open source, and what parts of it are >> > > available for hardware other than SGI's is under discussion. >> > > >> > > Steve >> > > >> > > -- >> > > >> > > Steve Lord voice: +1-651-683-3511 >> > > Principal Engineer, Filesystem Software email: lord@sgi.com >> > > >> > ======================================================================== >> > ===== >> > >> > Ray Muno >> > http://www.aem.umn.edu/people/staff/muno >> > University of Minnesota e-mail: >> > muno@aem.umn.edu >> > Aerospace Engineering and Mechanics Phone: (612) >> > 625-9531 >> > 110 Union St. S.E. FAX: (612) >> > 626-1558 >> > Minneapolis, Mn 55455 >> > >> > ======================================================================== >> > ===== >> > >> > >> > >> > >> > >> > >> > [[HTML alternate version deleted]] >> > >> > >> > >> > >> > >> -- >> Craig Tierney (ctierney@hpti.com) Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 11:34:24 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 11:34:26 -0800 (PST) Received: from mailbox.office.aol.com (x98A3A058.pix.aol.com [152.163.160.88]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5JYOuR008839 for ; Thu, 5 Dec 2002 11:34:24 -0800 Received: from PCSN653911 (dhcp0-031-094.office.aol.com [10.0.31.94]) by mailbox.office.aol.com (8.9.3 (PHNE_18979)/8.9.3) with SMTP id OAA14016; Thu, 5 Dec 2002 14:34:37 -0500 (EST) From: "N. Richard Solis" To: "Mike Gigante" , "Christoph Hellwig" Cc: "Craig Tierney" , "'Ray Muno '" , "'Steve Lord '" , Subject: RE: Clustered XFS? Date: Thu, 5 Dec 2002 14:33:55 -0500 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.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 In-Reply-To: X-archive-position: 1974 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nrsolis@aol.net Precedence: bulk X-list: linux-xfs I took a look at the documents and they explain some of the questions I had. Seems like coordination occurs via the LAN and not the disk/SAN interface. I'm wondering why? From what I remember, the GFS people kept the locks on the drives themselves. -----Original Message----- From: linux-xfs-bounce@oss.sgi.com [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Mike Gigante Sent: Thursday, December 05, 2002 1:57 PM To: Christoph Hellwig Cc: N. Richard Solis; Craig Tierney; 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? On Thu, Dec 05, 2002 at 12:54:30PM -0500, N. Richard Solis wrote: > Sounds more like a Clustered NFS solution to me? Would I be on target with > that one? > No, In NFS data travels over the wire, in CXFS data is direct access via the SAN. NFS is not posix compliant, CXFS is. Think of CXFS as a local filesystem for all intensive puposes - both performance and semantics. The client/server distinction is only with respect to maintaining a coherent cluster-wide view of filesystem by providing consistency of metadata. There are some things that must be coordinated such as extent allocation, kernel filesystem caches, memory mapped files etc etc. The CXFS server is the gatekeeper in this respect. Apart from the consistency management both the CXFS client and server can be considered local XFS. Oh, and there is no single point of failure -- clients can become the server (if they are capable). There are some docs on the SGI website that describe CXFS. Check that out if you want more info. Mike From owner-linux-xfs@oss.sgi.com Thu Dec 5 11:58:15 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 11:58:20 -0800 (PST) Received: from imf16bis.bellsouth.net (mail116.mail.bellsouth.net [205.152.58.56]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5JwFuR012705 for ; Thu, 5 Dec 2002 11:58:15 -0800 Received: from TAZ2 ([66.156.1.10]) by imf16bis.bellsouth.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021205200314.WMRT29303.imf16bis.bellsouth.net@TAZ2> for ; Thu, 5 Dec 2002 15:03:14 -0500 Date: Thu, 5 Dec 2002 15:01:21 -0500 From: Greg Freemyer Subject: Troubleshooting? To: xfs mailing list Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain Message-Id: <20021205200314.WMRT29303.imf16bis.bellsouth.net@TAZ2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB5JwFuR012718 X-archive-position: 1975 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs I've just installed the xfs 1.2pre3 kernel on my test server. In the 3 hours I've had it installed, I've had 3 lockups. When these occur I do NOT get an OOPS nor do I get kicked into KDB. I've tried alt-sysrq-s just to see if the kernel was alive at all and there was no response. (It does work prior to the lockup). I also don't see anything interesting in the logs. I'm not sure the XFS filesystems are totally clean, but they do mount with no problems and mapcheck shows nothing. I have no idea if this is a XFS issue or not. How do I proceed to troubleshoot from here? Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 12:34:49 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 12:34:52 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5KYmuR017768 for ; Thu, 5 Dec 2002 12:34:48 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB5Ic3G8016223 for ; Thu, 5 Dec 2002 10:38:03 -0800 Received: from maine.americas.sgi.com (maine.americas.sgi.com [128.162.232.87]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA13454; Thu, 5 Dec 2002 14:37:51 -0600 (CST) Received: from nstraz by maine.americas.sgi.com with local (Exim 3.36 #1 (Debian)) id 18K2kp-0003bc-00; Thu, 05 Dec 2002 14:37:51 -0600 Date: Thu, 5 Dec 2002 14:37:51 -0600 From: Nathan Straz To: Greg Freemyer Cc: xfs mailing list Subject: Re: Troubleshooting? Message-ID: <20021205203751.GC8704@sgi.com> Mail-Followup-To: Greg Freemyer , xfs mailing list References: <20021205200314.WMRT29303.imf16bis.bellsouth.net@TAZ2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021205200314.WMRT29303.imf16bis.bellsouth.net@TAZ2> User-Agent: Mutt/1.4i X-archive-position: 1976 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nstraz@sgi.com Precedence: bulk X-list: linux-xfs On Thu, Dec 05, 2002 at 03:01:21PM -0500, Greg Freemyer wrote: > I've just installed the xfs 1.2pre3 kernel on my test server. > > In the 3 hours I've had it installed, I've had 3 lockups. That's not a very good record. What kind of workload are you putting on them? Are you doing the same thing when they lock up? > When these occur I do NOT get an OOPS nor do I get kicked into KDB. [...] > How do I proceed to troubleshoot from here? I don't think KDB is compiled into the kernels. You'll want to grab the source and recompile with KDB. -- 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 Dec 5 12:59:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 12:59:34 -0800 (PST) Received: from tota.ulatina.ac.cr ([196.40.5.138]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5KxVuR021079 for ; Thu, 5 Dec 2002 12:59:32 -0800 Received: from fuerzag.ulatina.ac.cr (fuerzag.ulatina.ac.cr [163.178.60.45]) by tota.ulatina.ac.cr (Postfix) with ESMTP id B07EC1FE53 for ; Thu, 5 Dec 2002 15:05:54 -0600 (CST) Received: from localhost.localdomain ([163.178.60.3]) by fuerzag.ulatina.ac.cr (8.12.4/8.12.4) with ESMTP id gB5L8pRq030697 for ; Thu, 5 Dec 2002 15:08:51 -0600 Subject: Re: Clustered XFS? From: Alvaro Figueroa To: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Dec 2002 15:14:08 -0600 Message-Id: <1039122849.6697.47.camel@supokanaima> Mime-Version: 1.0 X-archive-position: 1978 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: fede2@fuerzag.ulatina.ac.cr Precedence: bulk X-list: linux-xfs > I was looking at the GFS software from Sistina and the OpenGFS project. I'm > wondering if it's possible to merge the codebases of XFS and OpenGFS to > provide the clustering functionality on XFS. Am I crazy? Have you tought up some initial design on how to do this? What GFS functions can be extracted out of it to be shared with other filesystems? And, can they be (ab|ex)tracted to a point where it becomes a generic layer for other (or all other) filesystems in the Linux kernel? -- Alvaro Figueroa From owner-linux-xfs@oss.sgi.com Thu Dec 5 12:59:13 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 12:59:16 -0800 (PST) Received: from imf11bis.bellsouth.net (mail311.mail.bellsouth.net [205.152.58.171]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5KxDuR020956 for ; Thu, 5 Dec 2002 12:59:13 -0800 Received: from TAZ2 ([66.156.1.10]) by imf11bis.bellsouth.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021205210410.YHRY22031.imf11bis.bellsouth.net@TAZ2>; Thu, 5 Dec 2002 16:04:10 -0500 Date: Thu, 5 Dec 2002 16:02:16 -0500 From: Greg Freemyer Subject: re[2]: Troubleshooting? To: Nathan Straz cc: xfs mailing list Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain Message-Id: <20021205210410.YHRY22031.imf11bis.bellsouth.net@TAZ2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB5KxDuR020965 X-archive-position: 1977 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs >> On Thu, Dec 05, 2002 at 03:01:21PM -0500, Greg Freemyer wrote: >> > I've just installed the xfs 1.2pre3 kernel on my test server. >> > >> > In the 3 hours I've had it installed, I've had 3 lockups. >> That's not a very good record. What kind of workload are you putting on >> them? Are you doing the same thing when they lock up? Yes, I have a backup script that uses LVM snapshots. I have found this to be problematic in the past, so I have been running it by hand, just to see if it will complete. It takes about 5 minutes to do the backup. (The data itself is not changing very much and they are incrementals.) It succeeded the first several times I tried it, but since then I get lockups. (I quit at 3). >> > When these occur I do NOT get an OOPS nor do I get kicked into KDB. >> [...] >> > How do I proceed to troubleshoot from here? >> I don't think KDB is compiled into the kernels. You'll want to grab >> the source and recompile with KDB. You are correct. I am using the vanilla 2.4.19 patched with the 2 patches at ftp://oss.sgi.com/projects/xfs/Release-1.2pre3/kernel_patches/ So I will get the kdb patch and add it in. Thanks >> -- >> Nate Straz nstraz@sgi.com >> sgi, inc http://www.sgi.com/ >> Linux Test Project http://ltp.sf.net/ Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 13:05:00 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 13:05:04 -0800 (PST) Received: from tota.ulatina.ac.cr ([196.40.5.138]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5L4xuR022397 for ; Thu, 5 Dec 2002 13:05:00 -0800 Received: from fuerzag.ulatina.ac.cr (fuerzag.ulatina.ac.cr [163.178.60.45]) by tota.ulatina.ac.cr (Postfix) with ESMTP id 19E1C1FE53 for ; Thu, 5 Dec 2002 15:11:27 -0600 (CST) Received: from localhost.localdomain ([163.178.60.3]) by fuerzag.ulatina.ac.cr (8.12.4/8.12.4) with ESMTP id gB5LEORq030813 for ; Thu, 5 Dec 2002 15:14:24 -0600 Subject: Re: Clustered XFS? From: Alvaro Figueroa To: linux-xfs@oss.sgi.com In-Reply-To: <1039107047.1726.4.camel@jen.americas.sgi.com> References: <1039107047.1726.4.camel@jen.americas.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 05 Dec 2002 15:19:40 -0600 Message-Id: <1039123181.6558.53.camel@supokanaima> Mime-Version: 1.0 X-archive-position: 1979 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: fede2@fuerzag.ulatina.ac.cr Precedence: bulk X-list: linux-xfs > Go look for CXFS on SGI's home page. There will be something available > for Linux, but it will not be open source Steve (or anyone else how knows), do you think that there is enough domentation available (or that can become available) about how CXFS works in order to start an GPLed proyect that enables CXFS to the Linux kernel? -- Alvaro Figueroa From owner-linux-xfs@oss.sgi.com Thu Dec 5 13:26:39 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 13:26:41 -0800 (PST) Received: from relay04.valueweb.net (relay04.valueweb.net [216.219.253.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5LQcuR025571 for ; Thu, 5 Dec 2002 13:26:38 -0800 Received: from thor.valueweb.net ([216.219.254.23]:27870 "EHLO thor.valueweb.net") by relay04.valueweb.net with ESMTP id ; Thu, 5 Dec 2002 16:27:59 -0500 Received: from adsl-156-1-10.asm.bellsouth.net ([66.156.1.10]:36685 "HELO TAZ2") by thor.valueweb.net with SMTP id convert rfc822-to-8bit; Thu, 5 Dec 2002 16:32:26 -0500 Date: Thu, 5 Dec 2002 16:29:16 -0500 From: Greg Freemyer Subject: re[3]: Troubleshooting? To: Greg Freemyer cc: xfs mailing list Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Message-Id: <20021205213236Z297489-6171+2@thor.valueweb.net> X-archive-position: 1980 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs This is not looking like an XFS issue. I downloaded the kdb patch and installed it. My kernel source tree is on an ext3 drive. I've had 2 lockups in the process of trying to compile the new kernel. :( I'll switch to a different kernel, get kdb compiled in and see what it shows shortly. >> >> On Thu, Dec 05, 2002 at 03:01:21PM -0500, Greg Freemyer wrote: >> >> > I've just installed the xfs 1.2pre3 kernel on my test server. >> >> > >> >> > In the 3 hours I've had it installed, I've had 3 lockups. >> >> That's not a very good record. What kind of workload are you putting >> on >> >> them? Are you doing the same thing when they lock up? >> Yes, I have a backup script that uses LVM snapshots. >> I have found this to be problematic in the past, so I have been running it >> by hand, just to see if it will complete. >> It takes about 5 minutes to do the backup. (The data itself is not >> changing very much and they are incrementals.) >> It succeeded the first several times I tried it, but since then I get >> lockups. (I quit at 3). >> >> > When these occur I do NOT get an OOPS nor do I get kicked into KDB. >> >> [...] >> >> > How do I proceed to troubleshoot from here? >> >> I don't think KDB is compiled into the kernels. You'll want to grab >> >> the source and recompile with KDB. >> You are correct. I am using the vanilla 2.4.19 patched with the 2 patches >> at >> ftp://oss.sgi.com/projects/xfs/Release-1.2pre3/kernel_patches/ >> So I will get the kdb patch and add it in. >> Thanks >> >> -- >> >> Nate Straz >> nstraz@sgi.com >> >> sgi, inc >> http://www.sgi.com/ >> >> Linux Test Project >> http://ltp.sf.net/ >> Greg Freemyer >> Internet Engineer >> Deployment and Integration Specialist >> Compaq ASE - Tru64 v4, v5 >> Compaq Master ASE - SAN Architect >> The Norcross Group >> www.NorcrossGroup.com Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 14:24:23 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 14:24:29 -0800 (PST) Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5MOLuR002456 for ; Thu, 5 Dec 2002 14:24:22 -0800 Received: (qmail 21120 invoked from network); 5 Dec 2002 22:27:35 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 5 Dec 2002 22:27:35 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id 985EF300087; Fri, 6 Dec 2002 09:27:32 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 60B8285; Fri, 6 Dec 2002 09:27:32 +1100 (EST) X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Greg Freemyer Cc: xfs mailing list Subject: Re: Troubleshooting? In-reply-to: Your message of "Thu, 05 Dec 2002 15:01:21 CDT." <20021205200314.WMRT29303.imf16bis.bellsouth.net@TAZ2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 06 Dec 2002 09:27:27 +1100 Message-ID: <637.1039127247@ocs3.intra.ocs.com.au> X-archive-position: 1981 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kaos@sgi.com Precedence: bulk X-list: linux-xfs On Thu, 5 Dec 2002 15:01:21 -0500, Greg Freemyer wrote: >I've just installed the xfs 1.2pre3 kernel on my test server. >In the 3 hours I've had it installed, I've had 3 lockups. >When these occur I do NOT get an OOPS nor do I get kicked into KDB. Boot with nmi_watchdog=1 (SMP) or nmi_watchdog=2 (UP). 5 seconds after the hang it should spit out some trace data, run that through ksymoops. If your kernel has kdb (/proc/sys/kernel/kdb contains 1) then the nmi watchdog will drop into kdb. From owner-linux-xfs@oss.sgi.com Thu Dec 5 14:41:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 14:41:35 -0800 (PST) Received: from imf25bis.bellsouth.net (mail227.mail.bellsouth.net [205.152.58.197]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5MfXuR002988 for ; Thu, 5 Dec 2002 14:41:33 -0800 Received: from TAZ2 ([66.156.1.10]) by imf25bis.bellsouth.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021205224632.FSA3653.imf25bis.bellsouth.net@TAZ2>; Thu, 5 Dec 2002 17:46:32 -0500 Date: Thu, 5 Dec 2002 17:44:39 -0500 From: Greg Freemyer Subject: re[2]: Troubleshooting? To: Keith Owens cc: xfs mailing list Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain Message-Id: <20021205224632.FSA3653.imf25bis.bellsouth.net@TAZ2> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB5MfXuR002989 X-archive-position: 1982 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs >> On Thu, 5 Dec 2002 15:01:21 -0500, >> Greg Freemyer wrote: >> >I've just installed the xfs 1.2pre3 kernel on my test server. >> >In the 3 hours I've had it installed, I've had 3 lockups. >> >When these occur I do NOT get an OOPS nor do I get kicked into KDB. >> Boot with nmi_watchdog=1 (SMP) or nmi_watchdog=2 (UP). 5 seconds after >> the hang it should spit out some trace data, run that through ksymoops. >> If your kernel has kdb (/proc/sys/kernel/kdb contains 1) then the nmi >> watchdog will drop into kdb. Keith, Thanks a lot for that. I have installed kdb and am getting the same problem, but I have not tried the above yet. I don't think it is XFS related at this point, because it happens even if I am only exercising an ext3 FS. This server must be incompatible with a vanilla 2.4.19 kernel. It has worked well in the past with SuSE patched kernels. Greg Freemyer Internet Engineer Deployment and Integration Specialist Compaq ASE - Tru64 v4, v5 Compaq Master ASE - SAN Architect The Norcross Group www.NorcrossGroup.com From owner-linux-xfs@oss.sgi.com Thu Dec 5 15:41:12 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 05 Dec 2002 15:41:16 -0800 (PST) Received: from woody.fsl.noaa.gov (woody.fsl.noaa.gov [137.75.132.225]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB5NfBuR004147 for ; Thu, 5 Dec 2002 15:41:11 -0800 Received: from woody.fsl.noaa.gov (woody.fsl.noaa.gov [127.0.0.1]) by woody.fsl.noaa.gov (8.12.5/8.12.5) with ESMTP id gB5Hf4bl016827; Thu, 5 Dec 2002 10:41:04 -0700 Received: (from tierney@localhost) by woody.fsl.noaa.gov (8.12.5/8.12.5/Submit) id gB5Hf40h016825; Thu, 5 Dec 2002 10:41:04 -0700 Date: Thu, 5 Dec 2002 10:41:04 -0700 From: Craig Tierney To: "N. Richard Solis" Cc: "'Ray Muno '" , "'Steve Lord '" , linux-xfs@oss.sgi.com Subject: Re: Clustered XFS? Message-ID: <20021205174104.GB16809@hpti.com> References: <22699FB2708ED611ADA100105AC5C9A05B02C6@hpti_main.hpti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-archive-position: 1983 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ctierney@hpti.com Precedence: bulk X-list: linux-xfs The client provides the interface so that when a user does a read or write, it translates the commands. The server takes care of the layout and locking (if supported). Right now you can have a linux box access the shared filesystem, but you still need an Irix box to take care of the metadata and locking. I have not worked with CXFS, so I might have exact terminology wrong but I think I have the idea right. Craig On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: > Client? Server? Please correct me if I'm wrong but should there be a > distinction? My understanding of CXFS was that there were enhancements made > to XFS to cupport concurrent access to a storage pool via a SAN. To do > this, you'd need locking/recovery, and some way to ensure that metadata > changes were visible to all the servers that had the same filesystem > mounted. Where does a client fit into all of this? > > > -----Original Message----- > From: linux-xfs-bounce@oss.sgi.com > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig > Sent: Thursday, December 05, 2002 11:59 AM > To: 'Ray Muno '; 'Steve Lord ' > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' > Subject: RE: Clustered XFS? > > > > SGI demoed the linux client at SC2002. The server though is still not > ready. I think the person I talked to said 'in 6 months' but I could > be off there. > > Craig > -----Original Message----- > From: Ray Muno > To: Steve Lord > Cc: N. Richard Solis; linux-xfs@oss.sgi.com > Sent: 12/5/02 12:13 PM > Subject: Re: Clustered XFS? > > The promise of a Linux client has been out there as long as CXFS has > been > around as far as I recall. When is it going to materialize? > > It has seemed strange to me that SGI can Support Solaris and Windows NT > with this environment but Linux support has never been made available. > > > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > > > I was looking at the GFS software from Sistina and the OpenGFS > project. I'm > > > wondering if it's possible to merge the codebases of XFS and OpenGFS > to > > > provide the clustering functionality on XFS. Am I crazy? > > > > Go look for CXFS on SGI's home page. There will be something available > > for Linux, but it will not be open source, and what parts of it are > > available for hardware other than SGI's is under discussion. > > > > Steve > > > > -- > > > > Steve Lord voice: +1-651-683-3511 > > Principal Engineer, Filesystem Software email: lord@sgi.com > > > ======================================================================== > ===== > > Ray Muno > http://www.aem.umn.edu/people/staff/muno > University of Minnesota e-mail: > muno@aem.umn.edu > Aerospace Engineering and Mechanics Phone: (612) > 625-9531 > 110 Union St. S.E. FAX: (612) > 626-1558 > Minneapolis, Mn 55455 > > ======================================================================== > ===== > > > > > > > [[HTML alternate version deleted]] > > > > > -- Craig Tierney (ctierney@hpti.com) From owner-linux-xfs@oss.sgi.com Fri Dec 6 01:28:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 01:28:45 -0800 (PST) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB69SguR016998 for ; Fri, 6 Dec 2002 01:28:42 -0800 Received: from auto-nb1.xs4all.nl (host-4.coltex.demon.nl [212.238.252.68]) by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id gB69Vufo097070; Fri, 6 Dec 2002 10:31:56 +0100 (CET) Message-Id: <4.3.2.7.2.20021206102733.041252e8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Dec 2002 10:31:49 +0100 To: Greg Freemyer , xfs mailing list From: Seth Mos Subject: Re: Troubleshooting? In-Reply-To: <20021205200314.WMRT29303.imf16bis.bellsouth.net@TAZ2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 1984 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs At 15:01 5-12-2002 -0500, Greg Freemyer wrote: >I've just installed the xfs 1.2pre3 kernel on my test server. > >In the 3 hours I've had it installed, I've had 3 lockups. >When these occur I do NOT get an OOPS nor do I get kicked into KDB. >I've tried alt-sysrq-s just to see if the kernel was alive at all and >there was no response. (It does work prior to the lockup). >I also don't see anything interesting in the logs. >I'm not sure the XFS filesystems are totally clean, but they do mount with >no problems and mapcheck shows nothing. >I have no idea if this is a XFS issue or not. >How do I proceed to troubleshoot from here? Are you using a broadcom 5700 card with the tg3 driver? You need a newer tg3.[ch] that fixes this lockup. http://people.redhat.com/jgarzik/tg3/tg3-1.2/ Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Fri Dec 6 01:55:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 01:56:03 -0800 (PST) Received: from mail.macroware.co.jp (gibraltar.fs.ksi.ne.jp [164.46.151.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB69twuR018204 for ; Fri, 6 Dec 2002 01:55:59 -0800 Received: from pcm03 (YahooBB219051136098.bbtec.net [219.51.136.98]) (authenticated) by mail.macroware.co.jp (8.11.6/8.11.3) with ESMTP id gB69xFI05402 for ; Fri, 6 Dec 2002 18:59:15 +0900 Message-ID: <001501c29d0d$a5877990$2401a8c0@pcm03> From: "Sakata" To: Subject: Can I change XFS_NAME? Date: Fri, 6 Dec 2002 18:55:45 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 1985 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sakata@macroware.co.jp Precedence: bulk X-list: linux-xfs Hello. I made a change to XFS_NAME in xfs_fs.h like this: #define XFS_NAME "xfs" -> #define XFS_NAME "xxxxx_xfs" Kernel compiled ok and boots normally. But can't mount xfs partition. Is it possible to make a change to XFS_NAME in xfs_fs.h? If Possible, to mount xfs partition what should I do? Hisamitsu Sakata Macroware Co., Ltd. Japan From owner-linux-xfs@oss.sgi.com Fri Dec 6 02:13:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 02:13:47 -0800 (PST) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6ADguR019018 for ; Fri, 6 Dec 2002 02:13:42 -0800 Received: from auto-nb1.xs4all.nl (host-4.coltex.demon.nl [212.238.252.68]) by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id gB6AGsVP020932; Fri, 6 Dec 2002 11:16:54 +0100 (CET) Message-Id: <4.3.2.7.2.20021206111526.040a76a0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Dec 2002 11:16:47 +0100 To: "Sakata" , From: Seth Mos Subject: Re: Can I change XFS_NAME? In-Reply-To: <001501c29d0d$a5877990$2401a8c0@pcm03> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 1986 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs At 18:55 6-12-2002 +0900, Sakata wrote: >Hello. > >I made a change to XFS_NAME in xfs_fs.h like this: >#define XFS_NAME "xfs" -> #define XFS_NAME "xxxxx_xfs" > >Kernel compiled ok and boots normally. But can't mount xfs partition. My best guess is that mount needs to check for this signature as well. Have you tried an strace on the mount command? >Is it possible to make a change to XFS_NAME in xfs_fs.h? >If Possible, to mount xfs partition what should I do? Maybe one of the other developers can comment on this. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Fri Dec 6 02:29:27 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 02:29:29 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6ATQuR020464 for ; Fri, 6 Dec 2002 02:29:26 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gB6Abikq031205 for ; Fri, 6 Dec 2002 04:37:45 -0600 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 VAA05670; Fri, 6 Dec 2002 21:31:20 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id VAA49474; Fri, 6 Dec 2002 21:31:19 +1100 (EST) Date: Fri, 6 Dec 2002 21:31:19 +1100 From: Nathan Scott To: Seth Mos , Sakata Cc: linux-xfs@oss.sgi.com Subject: Re: Can I change XFS_NAME? Message-ID: <20021206213119.A557863@wobbly.melbourne.sgi.com> References: <001501c29d0d$a5877990$2401a8c0@pcm03> <4.3.2.7.2.20021206111526.040a76a0@pop.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <4.3.2.7.2.20021206111526.040a76a0@pop.xs4all.nl>; from knuffie@xs4all.nl on Fri, Dec 06, 2002 at 11:16:47AM +0100 X-archive-position: 1987 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs On Fri, Dec 06, 2002 at 11:16:47AM +0100, Seth Mos wrote: > At 18:55 6-12-2002 +0900, Sakata wrote: > >Hello. > > > >I made a change to XFS_NAME in xfs_fs.h like this: > >#define XFS_NAME "xfs" -> #define XFS_NAME "xxxxx_xfs" > > > >Kernel compiled ok and boots normally. But can't mount xfs partition. Need more details to diagnose this... what command did you try? And exactly what errors do you see (from mount or in syslog)? > My best guess is that mount needs to check for this signature as well. Have > you tried an strace on the mount command? > > >Is it possible to make a change to XFS_NAME in xfs_fs.h? > >If Possible, to mount xfs partition what should I do? > > Maybe one of the other developers can comment on this. XFS_NAME isn't actually used everywhere it perhaps could be, one spot its not used is in the structure passed into the register_filesystem call... -- Nathan From owner-linux-xfs@oss.sgi.com Fri Dec 6 02:40:06 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 02:40:09 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6Ae6uR021024 for ; Fri, 6 Dec 2002 02:40:06 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB69lgKp022336 for ; Fri, 6 Dec 2002 01:47:42 -0800 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id EAA17129; Fri, 6 Dec 2002 04:43:17 -0600 (CST) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-9.corp.sgi.com [134.15.64.9]) by tulip-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id EAA70417; Fri, 6 Dec 2002 04:42:48 -0600 (CST) Subject: Re: Can I change XFS_NAME? From: Stephen Lord To: Sakata Cc: linux-xfs@oss.sgi.com In-Reply-To: <001501c29d0d$a5877990$2401a8c0@pcm03> References: <001501c29d0d$a5877990$2401a8c0@pcm03> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 06 Dec 2002 04:37:15 -0600 Message-Id: <1039171037.1374.25.camel@localhost.localdomain> Mime-Version: 1.0 X-archive-position: 1988 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Fri, 2002-12-06 at 03:55, Sakata wrote: > Hello. > > I made a change to XFS_NAME in xfs_fs.h like this: > #define XFS_NAME "xfs" -> #define XFS_NAME "xxxxx_xfs" > > Kernel compiled ok and boots normally. But can't mount xfs partition. > > Is it possible to make a change to XFS_NAME in xfs_fs.h? > If Possible, to mount xfs partition what should I do? Hmm, not sure I want people renaming the filesystem to something else, why do you want to do this? However, the reason it did not work is that the part of the kernel which cares about the name of the filesystem is not using that constant. In fs/xfs/linux/xfs_super.c look for this: STATIC struct file_system_type xfs_fs_type = { .owner = THIS_MODULE, .name = "xfs", .read_super = linvfs_read_super, .fs_flags = FS_REQUIRES_DEV, }; That string in there is the fstype used by mount. You would have to use mount -t to make this work I think. I am not sure where the string is coming from when mount works out the fs type by itself - probably it is hard coded into the mount source code. Steve From owner-linux-xfs@oss.sgi.com Fri Dec 6 03:53:13 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 03:53:15 -0800 (PST) Received: from hotmail.com (bay1-f140.bay1.hotmail.com [65.54.245.140]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6BrCuR023179 for ; Fri, 6 Dec 2002 03:53:13 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 6 Dec 2002 03:56:25 -0800 Received: from 12.236.101.144 by by1fd.bay1.hotmail.msn.com with HTTP; Fri, 06 Dec 2002 11:56:25 GMT X-Originating-IP: [12.236.101.144] From: "John Haverty" To: linux-xfs@oss.sgi.com Subject: Do releases have same or different on disk format? Date: Fri, 06 Dec 2002 03:56:25 -0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 06 Dec 2002 11:56:25.0718 (UTC) FILETIME=[80E9C960:01C29D1E] X-archive-position: 1989 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: zeio@hotmail.com Precedence: bulk X-list: linux-xfs Do releases have the same or different on disk format? I want to start off with a RH71 [for reasons out of my control] box and put my own kernel on. Say, I get the snapshot patches for 2.4.20, will this be equivalent if I installed XFS R1.0 on 7.1, then upgrade to 2.4.0+snapshot XFS OR Make my own bootable-CD, using the latest kerel+xfs and utilities, and make the filesystems and say rsync the system I want on there? [this does work, but its more time consuming] Am I losing anything by not using the mkfs from say -current or release 1.2? _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail From owner-linux-xfs@oss.sgi.com Fri Dec 6 04:08:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 04:08:47 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6C8guR024174 for ; Fri, 6 Dec 2002 04:08:43 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB6CH3kq031995 for ; Fri, 6 Dec 2002 06:17:03 -0600 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id GAA04422; Fri, 6 Dec 2002 06:11:53 -0600 (CST) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-9.corp.sgi.com [134.15.64.9]) by tulip-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id GAA81599; Fri, 6 Dec 2002 06:11:53 -0600 (CST) Subject: Re: Do releases have same or different on disk format? From: Stephen Lord To: John Haverty Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 06 Dec 2002 06:06:20 -0600 Message-Id: <1039176382.1374.51.camel@localhost.localdomain> Mime-Version: 1.0 X-archive-position: 1990 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Fri, 2002-12-06 at 05:56, John Haverty wrote: > Do releases have the same or different on disk format? I want to start off > with a RH71 [for reasons out of my control] box and put my own kernel on. > > Say, I get the snapshot patches for 2.4.20, will this be equivalent if I > installed XFS R1.0 on 7.1, then upgrade to 2.4.0+snapshot XFS > OR > Make my own bootable-CD, using the latest kerel+xfs and utilities, and make > the filesystems and say rsync the system I want on there? [this does work, > but its more time consuming] > > Am I losing anything by not using the mkfs from say -current or release 1.2? > On disk format has not changed at all, we have added some new features along the way, it is possible to mkfs a filesystem with new commands which an old kernel cannot mount. But default mkfs options will not do that. A newer kernel should always be able to mount an older filesystem. I would recommend recent commands though, a lot of fixes have gone into them over time. In 2.4 XFS we have a number of core kernel changes which have been modified over time. Getting a patch from one kernel version to apply to another one requires a fair amount of knowledge of how things work and probably a fair amount of editing. Similarly, getting an xfs code base from one kernel version to work with another one is not always simple. I may just be mis-interpreting your intentions here, I have been up since 4am and have not drunk any coffee yet. Steve From owner-linux-xfs@oss.sgi.com Fri Dec 6 04:13:10 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 04:13:12 -0800 (PST) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6CD9uR027938 for ; Fri, 6 Dec 2002 04:13:10 -0800 Received: from auto-nb1.xs4all.nl (host-4.coltex.demon.nl [212.238.252.68]) by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id gB6CGP7l078243; Fri, 6 Dec 2002 13:16:25 +0100 (CET) Message-Id: <4.3.2.7.2.20021206130600.02db16c0@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 06 Dec 2002 13:16:20 +0100 To: "John Haverty" , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: Do releases have same or different on disk format? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 1991 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs At 03:56 6-12-2002 -0800, John Haverty wrote: >Do releases have the same or different on disk format? I want to start off >with a RH71 [for reasons out of my control] box and put my own kernel on. The on-disk format will not change. The only change so far was in the log format. Make sure that you mount a "clean" fs when changing the kernel version. (was some time ago) And update the userspace utilities for quota and acls. That has changed. >Say, I get the snapshot patches for 2.4.20, will this be equivalent if I >installed XFS R1.0 on 7.1, then upgrade to 2.4.0+snapshot XFS >OR Install the thingie and just update the kernel and userspace utilities. That is more then enough. >Make my own bootable-CD, using the latest kerel+xfs and utilities, and >make the filesystems and say rsync the system I want on there? [this does >work, but its more time consuming] > >Am I losing anything by not using the mkfs from say -current or release 1.2? If you are making a large filesystem >1TB or have some other exotice needs it might be wise to create those filesystems with a newer mkfs. For just the normal / /usr or /var it doesn't matter much. There are some mkfs options that benefit busy filesystems or special needs. If you want version2 log support which is faster for use on EVMS or md software raid5 partitions you will also need to do this manually. And you need a new mfs.xfs for v2 logs. and >= 2.4.19-xfs Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Fri Dec 6 06:31:31 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 06:31:35 -0800 (PST) Received: from b64198.tod.net (oh-clevelandheights4a-205.clvhoh.adelphia.net [24.50.237.205]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6EVUuR030432 for ; Fri, 6 Dec 2002 06:31:31 -0800 Received: from tod.net (sasami.CNS.CWRU.Edu [129.22.115.137]) (authenticated bits=0) by b64198.tod.net (8.12.6/8.12.6/Debian-8) with SMTP id gB6EYw0f016059 for ; Fri, 6 Dec 2002 09:34:58 -0500 Date: Fri, 6 Dec 2002 09:35:16 -0500 Mime-Version: 1.0 (Apple Message framework v548) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: xfs_growfs, lvm, and sparcs.... From: Tod Detre To: linux-xfs@oss.sgi.com Content-Transfer-Encoding: 7bit Message-Id: X-Mailer: Apple Mail (2.548) X-archive-position: 1992 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tod@tod.net Precedence: bulk X-list: linux-xfs I've been using xfs on linux lvm for quite a while now without any problems on both i386 and alpha systems. I've recently install this on a sparcstation I want to use as a file server and didn't run into any problems until I tried to grow a filesystem. when I try xfs_growfs I get this error: xfs_growfs /usr xfs_growfs: cannot determine geometry of filesystem mounted at /usr: Invalid argument Any ideas on why this is happening or a way around it? INFO: Debian/sid xfs kernel from cvs 2.4.20-xfs xfsprogs from cvs (same as kernel) Sparcstation 5, ide disks -- Tod Detre Unix Technical Support Case Western Reserve University usworkstation@po.cwru.edu 216-368-3060 From owner-linux-xfs@oss.sgi.com Fri Dec 6 07:06:15 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 07:06:17 -0800 (PST) Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6F6EuR031147 for ; Fri, 6 Dec 2002 07:06:14 -0800 Received: from kanpc.gte.com (localhost [IPv6:::1]) by h132-197-179-27.gte.com (8.12.6/8.12.6) with ESMTP id gB6F9ReJ007384; Fri, 6 Dec 2002 10:09:27 -0500 (EST) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.6/8.12.6/Submit) id gB6F9RXa007380; Fri, 6 Dec 2002 10:09:27 -0500 (EST) Date: Fri, 6 Dec 2002 10:09:27 -0500 From: Alexander Kabaev To: linux-xfs@oss.sgi.com Cc: Russell Cattelan Subject: Re: TAKE - final sendfile bits Message-Id: <20021206100927.31ac6b4e.ak03@gte.com> In-Reply-To: <200212051850.gB5IoCFi031602@lab343.munich.sgi.com> References: <200212051850.gB5IoCFi031602@lab343.munich.sgi.com> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.8.6claws35 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 1993 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak03@gte.com Precedence: bulk X-list: linux-xfs On Thu, 5 Dec 2002 19:50:12 +0100 Christoph Hellwig wrote: > This will let all QA tests pass again on 2.5. > > > Date: Thu Dec 5 10:50:54 PST 2002 > Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs > > The following file(s) were checked into: > bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs > > > Modid: 2.5.x-xfs:slinx:134450a > linux/fs/xfs/xfs_vnodeops.c - 1.575 > - adds sendfile to the vnode operation vector > > linux/fs/xfs/linux/xfs_lrw.h - 1.32 > - add an extern for xfs_sendfile > > linux/fs/xfs/linux/xfs_lrw.c - 1.178 > - last fixups for xfs_sendfile > I noticed that CVS tree exported from ftp.thebarn.com via CVSup is stable linux-2.4-xfs version. Can CVSup be configured to provide development linux-2.5-xfs tree too? -- Alexander Kabaev From owner-linux-xfs@oss.sgi.com Fri Dec 6 09:32:23 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 09:32:28 -0800 (PST) Received: from server4.adrenamail.com ([67.41.175.41]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6HWLuR000748 for ; Fri, 6 Dec 2002 09:32:22 -0800 Received: from adrenamail.com (unknown [192.168.38.74]) by server4.adrenamail.com (Postfix) with ESMTP id B59F851C021; Fri, 6 Dec 2002 12:27:02 -0500 (EST) To: David@adrenamail.com Subject: Thank you for downloading U-harvest MIME-Version: 1.0 In-Reply-To: David@adrenamail.com Message-Id: <20021206172702.B59F851C021@server4.adrenamail.com> Date: Fri, 6 Dec 2002 12:27:02 -0500 (EST) From: David@adrenamail.com Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 560 X-archive-position: 1994 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: David@adrenamail.com Precedence: bulk X-list: linux-xfs Hello Thank you for downloading U-harvest. We would love to hear from you and get your feedback from using U-harvest You may also contact us and get a certificate. Any user referred by yourself who enters your certificate at the time of purchasing will credit your account with our gift of appreciation of $100 (hundred US dollars). If you have any questions please do not hesitate to contact us at the phone number list below or by responding to this message. Thank you David Evgey www.Uharvest.com Phone: 410-358 4499 [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Fri Dec 6 09:32:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 09:32:36 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6HWXuR000784 for ; Fri, 6 Dec 2002 09:32:34 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB6GeBKp010664 for ; Fri, 6 Dec 2002 08:40:11 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA55792; Fri, 6 Dec 2002 11:35:43 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA18724; Fri, 6 Dec 2002 11:35:45 -0600 (CST) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by rose.americas.sgi.com (8.12.5/8.12.5) with ESMTP id gB6HZpIx025713; Fri, 6 Dec 2002 11:35:52 -0600 Subject: RE: Clustered XFS? From: Russell Cattelan To: "N. Richard Solis" Cc: Craig Tierney , linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 06 Dec 2002 11:35:51 -0600 Message-Id: <1039196152.23896.56.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 1995 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs On Thu, 2002-12-05 at 12:49, N. Richard Solis wrote: > So it's more like DAFS then? No. DAFS is somewhat misnamed actually there are multiple aspect called DDAFS Device (Direct Access FileSystem) UDAFS User and FDAFS File I don't know what progress has been made with UDAFS or FDAFS but DDAFS is simple a protocol to map a remote file (server) to a local device (client) which is really only interesting to things that talk block; like data bases. Note main point of DAFS is to implement a zero copy block transfer mechanism, which isn't to say it can't be used as part of a shared filesystem but DAFS itself isn't intended to provide any of the sharing supported need to do a share file system. > > -----Original Message----- > From: linux-xfs-bounce@oss.sgi.com > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Craig Tierney > Sent: Thursday, December 05, 2002 1:47 PM > To: N. Richard Solis > Cc: linux-xfs@oss.sgi.com > Subject: Re: Clustered XFS? > > > I have heard the term clustered NFS but I have never seen an actual > implementation. In a clustered NFS solution, is every node actually > talking SCSI (Fibre channel usually) to the disk? That is what CXFS > is doing. Each node physically hits each disk. The metadata server > keep track of what everyone is doing and prevents them from stomping on > each other. > > Craig > > > > > On Thu, Dec 05, 2002 at 12:54:30PM -0500, N. Richard Solis wrote: > > Sounds more like a Clustered NFS solution to me? Would I be on target > with > > that one? > > > > -----Original Message----- > > From: Craig Tierney [mailto:ctierney@hpti.com] > > Sent: Thursday, December 05, 2002 12:41 PM > > To: N. Richard Solis > > Cc: 'Ray Muno '; 'Steve Lord '; linux-xfs@oss.sgi.com > > Subject: Re: Clustered XFS? > > > > > > The client provides the interface so that when a user does a read > > or write, it translates the commands. The server takes care of the layout > > and locking (if supported). Right now you can have a linux box access > > the shared filesystem, but you still need an Irix box to take care of > > the metadata and locking. > > > > I have not worked with CXFS, so I might have exact terminology wrong > > but I think I have the idea right. > > > > Craig > > > > On Thu, Dec 05, 2002 at 12:22:31PM -0500, N. Richard Solis wrote: > > > Client? Server? Please correct me if I'm wrong but should there be a > > > distinction? My understanding of CXFS was that there were enhancements > > made > > > to XFS to cupport concurrent access to a storage pool via a SAN. To do > > > this, you'd need locking/recovery, and some way to ensure that metadata > > > changes were visible to all the servers that had the same filesystem > > > mounted. Where does a client fit into all of this? > > > > > > > > > -----Original Message----- > > > From: linux-xfs-bounce@oss.sgi.com > > > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Tierney, Craig > > > Sent: Thursday, December 05, 2002 11:59 AM > > > To: 'Ray Muno '; 'Steve Lord ' > > > Cc: 'N. Richard Solis '; 'linux-xfs@oss.sgi.com ' > > > Subject: RE: Clustered XFS? > > > > > > > > > > > > SGI demoed the linux client at SC2002. The server though is still not > > > ready. I think the person I talked to said 'in 6 months' but I could > > > be off there. > > > > > > Craig > > > -----Original Message----- > > > From: Ray Muno > > > To: Steve Lord > > > Cc: N. Richard Solis; linux-xfs@oss.sgi.com > > > Sent: 12/5/02 12:13 PM > > > Subject: Re: Clustered XFS? > > > > > > The promise of a Linux client has been out there as long as CXFS has > > > been > > > around as far as I recall. When is it going to materialize? > > > > > > It has seemed strange to me that SGI can Support Solaris and Windows NT > > > with this environment but Linux support has never been made available. > > > > > > > > > On Thu, Dec 05, 2002 at 10:50:47AM -0600, Steve Lord wrote: > > > > On Thu, 2002-12-05 at 10:43, N. Richard Solis wrote: > > > > > Is anyone working on adding clustering/SAN support to XFS on Linux? > > > > > > > > > > I was looking at the GFS software from Sistina and the OpenGFS > > > project. I'm > > > > > wondering if it's possible to merge the codebases of XFS and OpenGFS > > > to > > > > > provide the clustering functionality on XFS. Am I crazy? > > > > > > > > Go look for CXFS on SGI's home page. There will be something available > > > > for Linux, but it will not be open source, and what parts of it are > > > > available for hardware other than SGI's is under discussion. > > > > > > > > Steve > > > > > > > > -- > > > > > > > > Steve Lord voice: +1-651-683-3511 > > > > Principal Engineer, Filesystem Software email: lord@sgi.com > > > > > > > ======================================================================== > > > ===== > > > > > > Ray Muno > > > http://www.aem.umn.edu/people/staff/muno > > > University of Minnesota e-mail: > > > muno@aem.umn.edu > > > Aerospace Engineering and Mechanics Phone: (612) > > > 625-9531 > > > 110 Union St. S.E. FAX: (612) > > > 626-1558 > > > Minneapolis, Mn 55455 > > > > > > ======================================================================== > > > ===== > > > > > > > > > > > > > > > > > > > > > [[HTML alternate version deleted]] > > > > > > > > > > > > > > > > > > > -- > > Craig Tierney (ctierney@hpti.com) > > > > > > > > -- > Craig Tierney (ctierney@hpti.com) > > > From owner-linux-xfs@oss.sgi.com Fri Dec 6 09:41:58 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 09:42:00 -0800 (PST) Received: from server4.adrenamail.com ([67.41.175.41]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6HfuuR001784 for ; Fri, 6 Dec 2002 09:41:57 -0800 Received: from adrenamail.com (unknown [192.168.38.74]) by server4.adrenamail.com (Postfix) with ESMTP id 5E8BD51C04F; Fri, 6 Dec 2002 12:38:23 -0500 (EST) To: David@adrenamail.com Subject: Apology MIME-Version: 1.0 In-Reply-To: David@adrenamail.com Message-Id: <20021206173823.5E8BD51C04F@server4.adrenamail.com> Date: Fri, 6 Dec 2002 12:38:23 -0500 (EST) From: David@adrenamail.com Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 198 X-archive-position: 1996 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: David@adrenamail.com Precedence: bulk X-list: linux-xfs Hello I have just sent you a message by mistake. I am terribly sorry. Please ignore that message completely. David Evgey- www.U-harevst.com Phone: 410-358 4499 [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Fri Dec 6 10:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 10:44:05 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB6Ii1uR002948 for ; Fri, 6 Dec 2002 10:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB6Ii1pK002947 for linux-xfs@oss.sgi.com; Fri, 6 Dec 2002 10:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gB6IhxuT002933 for ; Fri, 6 Dec 2002 10:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gB6IJAvh002722; Fri, 6 Dec 2002 10:19:10 -0800 Date: Fri, 6 Dec 2002 10:19:10 -0800 Message-Id: <200212061819.gB6IJAvh002722@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 201] New: The procedure described in the document "Making a Linux XFS Root filesystem" yield an unbootable system. X-Bugzilla-Reason: AssignedTo X-archive-position: 1997 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=201 Summary: The procedure described in the document "Making a Linux XFS Root filesystem" yield an unbootable system. Product: Linux XFS Version: 1.1.x Platform: All OS/Version: All Status: NEW Severity: normal Priority: High Component: xfsprogs AssignedTo: xfs-master@oss.sgi.com ReportedBy: ttruong@broadcom.com If this is a userspace bug, what version of the package are you using: 1.1 What kernel are you using: 2.4.18-4SGI_XFS_1.1 Where did the XFS code come from? (CVS, Linus, your distribution, etc): http://oss.sgi.com under the link 'Making a Linux XFS Root filesystem" Description of Problem: The procedure to install XFS on the root file system is erronous. The user will end up in a non-bootable system if the steps described therein was followed. Step 8 says: 8. Install the new lilo configuration lilo -r /mnt However, at this time, the old boot disk 9say /dev/hda1) is still specified in lilo.conf. Doing "lilo -r /mnt" would write the disk boot sector to /dev/hda1 and not to /dev/hdb1 (/mnt) as was intended. How Reproducible: Just follow the steps described in the document step by step. Steps to Reproduce: 1. 2. 3. Actual Results: User ends up with an un-bootable system. Expected Results: user able to boot from the new disk with XFS as root. Additional Information: To fix the problem, I had to create a boot diskette as follows: Step 7.1: Assuming the old EXT2 boot disk is at /dev/hda1, and the new XFS disk has been sucessfully copied, and that the new fstab reflecting the changes have been made in stepo 7.0. 7.1 Save the old fstab from the old EXT2 boot disk: # cd /etc # cp fstab fstab.ext2 Copy the new fstab over since mkbootdisk will use this info to create the boot diskette # cp /mnt/etc/fstab ./fstab # mkbootdisk --compact `uname -r` Restored old fstab # cp fstab.ext2 fstab 8. Install the enw lilo configuration: Boot from the newly created diskette and configure lilo: # /sbin/lilo -v -v -v ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Fri Dec 6 13:57:20 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 13:57:24 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6LvKuR021761 for ; Fri, 6 Dec 2002 13:57:20 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB6K0cG8029593 for ; Fri, 6 Dec 2002 12:00:39 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id QAA70808 for ; Fri, 6 Dec 2002 16:00:25 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id QAA96246 for ; Fri, 6 Dec 2002 16:00:26 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gB75ERU10632 for linux-xfs@oss.sgi.com; Sat, 7 Dec 2002 00:14:27 -0500 Resent-Message-Id: <200212070514.gB75ERU10632@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id PAA95462 for ; Fri, 6 Dec 2002 15:58:18 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB6Lw9Qb40366708 for ; Fri, 6 Dec 2002 13:58:16 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB6LuQaM020802 for ; Fri, 6 Dec 2002 22:56:26 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB6LuQRj020801 for hch@sgi.com; Fri, 6 Dec 2002 22:56:26 +0100 Date: Fri, 6 Dec 2002 22:56:26 +0100 From: Christoph Hellwig Message-Id: <200212062156.gB6LuQRj020801@lab343.munich.sgi.com> Subject: TAKE - remove linvfs_put_inode To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Sat, 7 Dec 2002 00:14:26 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 1998 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs This one was superflous. We already call VOP_RELEASE in linvfs_release. Date: Fri Dec 6 13:56:35 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134630a linux/fs/xfs/linux/xfs_super.c - 1.235 - remove linvfs_put_inode From owner-linux-xfs@oss.sgi.com Fri Dec 6 15:15:38 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 15:15:44 -0800 (PST) Received: from quartz.hknet.com (quartz.hknet.com [202.67.213.10]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB6NFbuR022828 for ; Fri, 6 Dec 2002 15:15:38 -0800 Received: from localhost.localdomain (nweb.hknetmail.com [202.67.240.32]) by quartz.hknet.com (8.12.6/8.12.6) with ESMTP id gB6NVgKd002970; Sat, 7 Dec 2002 07:31:42 +0800 (HKT) Received: (from virtual@localhost) by localhost.localdomain (8.11.2/8.11.2) id gB6N8kZ14044; Sat, 7 Dec 2002 07:08:46 +0800 X-Authentication-Warning: localhost.localdomain: virtual set sender to ma_ha_aba@hknetmail.com using -f Received: from 66.133.58.203 ( [66.133.58.203]) as user ma_ha_aba@nweb.hknet.com by www.hknetmail.com with HTTP; Sat, 7 Dec 2002 07:08:46 +0800 Message-ID: <1039216126.3df12dfe7e141@www.hknetmail.com> Date: Sat, 7 Dec 2002 07:08:46 +0800 From: ma_ha_aba@hknetmail.com To: ma_ha_aba@hknetmail.com Subject: THANK YOU MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.1 X-Originating-IP: 66.133.58.203 X-archive-position: 1999 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ma_ha_aba@hknetmail.com Precedence: bulk X-list: linux-xfs Greetings, Following the sudden death of my husband General Sani Abacha the former head of state of Nigeria in August 1998, I have been thrown into a state of utter confusion, frustration and hopelessness by the present civilian administration, I have been subjected to physical and psychological torture by the security agents in the country. My son is still under detention arraigned before the federal high courtof Nigeria for an offence he did not commit even though the government might release him soon. As a widow that is so traumatized, I have lost confidence with anybody within the country. You must have heard over the media reports and the internet on the recovery of various huge sums of money deposited by my husband in different security firms abroad, Some companies willingly gave up their secrets and disclosed our money confidently lodged there or many outright blackmail. In fact the total sum discovered by the Government so far is in the tune of $700. Million dollars. And they are not relenting to make me poor for life. I got your contacts through my personal research,and out of desperation decided to reach you through this medium.I will give you more information as to this regard as soon as you reply. I repose great confidence in you hence my approach to you due to security network placed on my day to day affairs I cannot afford to visit the embassy so that is why I decided to contact you and Ihope you will not betray my confidence in you. I have deposited the sumof 40 million dollars with a security firm abroad whose name is witheld for now until we open communication. I shall be grateful if you could receive this fund into your account for safe keeping. This arrangement is known to you and my son Mustapha alone, so my son will deal directly with you as security is up my whole being. I am seriously considering to settle down abroad in a friendly atmosphere like yours as soon as this fund get into your account so that I can start all over again if only you wish, but if it is impossible,just help me in diverting this fund into your account which will accrue you 30% of this fund . Please honesty is the watch word in this transaction. I will require your telephone and fax numbers so that we can commence communication immediately and I will give you a more detailed picture of things. In case you dont accept please do not let me out to the security as I am giving you this information in total trust and confidence I will greatly appreciate if you accept my proposal in good faith. Please expedite action. Sincerely yours, Hajia Mariam Abacha. N/B: Please copy your response to:maryamhaaba@lycos.co.uk ------------------------------------------------- HKNETMAIL.COM Free WEB MAIL Service by HKNET From owner-linux-xfs@oss.sgi.com Fri Dec 6 19:21:57 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 19:22:01 -0800 (PST) Received: from banna (pl109.nas926.o-tokyo.nttpc.ne.jp [210.165.109.109]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB73LPuR026735 for ; Fri, 6 Dec 2002 19:21:51 -0800 Received: from wing-2f8mswpeuw ([192.168.0.5]) by banna (8.9.3+3.2W/3.7W) with SMTP id MAA25458; Sat, 7 Dec 2002 12:25:26 +0900 Message-Id: <200212070325.MAA25458@banna> From: =?iso-2022-jp?B?aG1haWw5OTk5?= To: =?iso-2022-jp?B?NTU1NQ==?=@banna.sgi.com Reply-To: hmail9999@yahoo.co.jp Date: Sat, 07 Dec 2002 12:22:44 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoRUU7UiVhITwlazktOXAbKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2000 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hmail9999@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望しない方はここへ (必ず本文にあなたのメールアドレスのみをお書き下さい） info_ssh@yahoo.co.jp メールアドレスをご記入してください。 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218 =============================================================== 問題商品ばかり集めましたので、消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Fri Dec 6 23:05:41 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 06 Dec 2002 23:05:46 -0800 (PST) Received: from web10006.mail.yahoo.com (web10006.mail.yahoo.com [216.136.130.42]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB775fuR028705 for ; Fri, 6 Dec 2002 23:05:41 -0800 Message-ID: <20021207070902.37078.qmail@web10006.mail.yahoo.com> Received: from [67.80.20.62] by web10006.mail.yahoo.com via HTTP; Fri, 06 Dec 2002 23:09:02 PST Date: Fri, 6 Dec 2002 23:09:02 -0800 (PST) From: George Georgalis Subject: corrupted partition with grub in hda1 To: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 2001 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgalis@yahoo.com Precedence: bulk X-list: linux-xfs XFS: bad magic number XFS: SB validate failed Kernel panic: VFS Unable to mount root fs on 03:01 Looks like I blew it. Trying to get grub installed, I must have installed it on the root partition not the MBR, corrupting the fs in the process. So is there a fix? How? // George __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com From owner-linux-xfs@oss.sgi.com Sat Dec 7 01:21:00 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 01:21:02 -0800 (PST) Received: from mx0.gmx.net (mx0.gmx.de [213.165.64.100]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB79KxuR029995 for ; Sat, 7 Dec 2002 01:21:00 -0800 Received: (qmail 9591 invoked by uid 0); 7 Dec 2002 09:24:14 -0000 Date: Sat, 7 Dec 2002 10:24:14 +0100 (MET) From: christian mueller To: George Georgalis Cc: linux-xfs@oss.sgi.com MIME-Version: 1.0 Subject: Re: corrupted partition with grub in hda1 X-Priority: 3 (Normal) X-Authenticated-Sender: #0002001279@gmx.net X-Authenticated-IP: [217.84.168.128] Message-ID: <31634.1039253054@www20.gmx.net> X-Mailer: WWW-Mail 1.6 (Global Message Exchange) X-Flags: 0001 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-archive-position: 2002 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: christian.mueller1@gmx.de Precedence: bulk X-list: linux-xfs Hi, on 2002-12-07 7:09:02 George Georgalis wrote: > XFS: bad magic number > XFS: SB validate failed > Kernel panic: VFS Unable to mount root fs on 03:01 > > Looks like I blew it. Trying to get grub installed, I must have installed > it on the root > partition not the MBR, corrupting the fs in the process. > > So is there a fix? How? There are 2 Superblocks on the partition. Use 'xfsrepair' (included in the xfsprogs-pck) to fix this. It should find the second SB and recover from that. The partition has to be unmounted for this action, of course. -chris -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr fr 1 ct/ Min. surfen! From owner-linux-xfs@oss.sgi.com Sat Dec 7 07:26:48 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 07:26:52 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB7FQluR011495 for ; Sat, 7 Dec 2002 07:26:48 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB7EYVKp030046 for ; Sat, 7 Dec 2002 06:34:32 -0800 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id JAA69759; Sat, 7 Dec 2002 09:30:03 -0600 (CST) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-32.corp.sgi.com [134.15.64.32]) by tulip-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id JAA91157; Sat, 7 Dec 2002 09:30:02 -0600 (CST) Subject: Re: corrupted partition with grub in hda1 From: Stephen Lord To: George Georgalis Cc: christian mueller , linux-xfs@oss.sgi.com In-Reply-To: <31634.1039253054@www20.gmx.net> References: <31634.1039253054@www20.gmx.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 07 Dec 2002 09:24:26 -0600 Message-Id: <1039274667.1408.5.camel@localhost.localdomain> Mime-Version: 1.0 X-archive-position: 2003 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Sat, 2002-12-07 at 03:24, christian mueller wrote: > Hi, > > on 2002-12-07 7:09:02 George Georgalis wrote: > > XFS: bad magic number > > XFS: SB validate failed > > Kernel panic: VFS Unable to mount root fs on 03:01 > > > > Looks like I blew it. Trying to get grub installed, I must have installed > > it on the root > > partition not the MBR, corrupting the fs in the process. > > > > So is there a fix? How? > > There are 2 Superblocks on the partition. > Use 'xfsrepair' (included in the xfsprogs-pck) to fix this. > It should find the second SB and recover from that. > The partition has to be unmounted for this action, of course. It depends how far into the partition grub writes, but right after the superblock is going to be the root inode. If you are lucky it will have survived, if not everything in the filesystem will have been moved into lost+found by repair. Good luck, Steve From owner-linux-xfs@oss.sgi.com Sat Dec 7 09:52:10 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 09:52:13 -0800 (PST) Received: from waltsathlon.localhost.net (h-66-167-49-200.STTNWAHO.covad.net [66.167.49.200]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB7Hq9uR013252 for ; Sat, 7 Dec 2002 09:52:09 -0800 Received: from mindspring.com (localhost.localhost.net [127.0.0.1]) by waltsathlon.localhost.net (Postfix) with ESMTP id F1A7EABD0; Sat, 7 Dec 2002 09:55:26 -0800 (PST) Message-ID: <3DF2360D.6000806@mindspring.com> Date: Sat, 07 Dec 2002 09:55:25 -0800 From: Walt H User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021126 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Greg Freemyer Cc: Karl Ran , austin@coremetrics.com, linux-xfs@oss.sgi.com Subject: [OT] Re: Choosing the right kernel for XFS References: <20021121171708.CVEG17441.imf11bis.bellsouth.net@TAZ2> In-Reply-To: <20021121171708.CVEG17441.imf11bis.bellsouth.net@TAZ2> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2004 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: waltabbyh@mindspring.com Precedence: bulk X-list: linux-xfs I know this is a late reply and is somewhat off topic for the list, however, just wanted to chime in for completeness re: the opensource Promise drivers. Yes, there are some "partially opensource drivers". They are packaged very similar to the Nvidia drivers. There is a binary only portion that you compile a wrapper around so it will work within your kernel version/config. I've found performance to be rather good, however, I can't vouch for stability yet. Also, at least in my case, getting them installed was quite a bear. You really need the combined documentation from one of their full installs targeted at Redhat or Suse as well as the small readme file that is part of the archive. Following their instructions to the letter, I was still left with many undefined symbols in the module, regardless of whether I compiled with or without dependencies. At any rate, once you get the module actually compiled and loadable at boot time, they work rather nicely and in my case using two 7200 RPM IDE drives as a raid0 array, offer better performance than the md software raid in linux. -Walt Greg Freemyer wrote: > >> Sounds too good to be true! > > >> Anybody knows where I can find 'the promise patch' for 2.4.18? > > > >> Karl > > Try http://www.promise.com/support/support_eng.asp > > FYI: > Traditionally the promise patches have been binary only. > > They are built to apply to specific kernels. I don't know if they support a vanilla kernels or not. > > On another mailing list I read "Finally 2 days ago promise released a opensource module for Fasttrak100 raid > controller." > > Maybe that means that promise is finally seeing the light. > > Greg Freemyer > Internet Engineer > Deployment and Integration Specialist > Compaq ASE - Tru64 v4, v5 > Compaq Master ASE - SAN Architect > The Norcross Group > www.NorcrossGroup.com > > From owner-linux-xfs@oss.sgi.com Sat Dec 7 12:01:50 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 12:01:52 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB7K1nuR014253 for ; Sat, 7 Dec 2002 12:01:50 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gB7J9YKp004907 for ; Sat, 7 Dec 2002 11:09:35 -0800 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 HAA15905; Sun, 8 Dec 2002 07:03:51 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id HAA40082; Sun, 8 Dec 2002 07:03:49 +1100 (EST) Date: Sun, 8 Dec 2002 07:03:48 +1100 From: Nathan Scott To: Tod Detre Cc: linux-xfs@oss.sgi.com Subject: Re: xfs_growfs, lvm, and sparcs.... Message-ID: <20021208070348.A551887@wobbly.melbourne.sgi.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from tod@tod.net on Fri, Dec 06, 2002 at 09:35:16AM -0500 X-archive-position: 2005 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs On Fri, Dec 06, 2002 at 09:35:16AM -0500, Tod Detre wrote: > I've been using xfs on linux lvm for quite a while now without any > problems on both i386 and alpha systems. I've recently install this on > a sparcstation I want to use as a file server and didn't run into any > problems until I tried to grow a filesystem. when I try xfs_growfs I > get this error: > > xfs_growfs /usr > xfs_growfs: cannot determine geometry of filesystem mounted at /usr: > Invalid argument > > Any ideas on why this is happening or a way around it? There was a problem like this a few weeks/months back in the way the tools were handling a new ioctl version; but it should be fixed now (definately in the versions you've listed here...) > Debian/sid > xfs kernel from cvs 2.4.20-xfs > xfsprogs from cvs (same as kernel) > Sparcstation 5, ide disks What does xfs_growfs -V say, and what's the XFS CVS version/date timestamp from your system log? Could you send me strace output on your failing growfs command too, as a starting point? thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Sat Dec 7 13:41:04 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 13:41:08 -0800 (PST) Received: from banna (pl374.nas926.o-tokyo.nttpc.ne.jp [210.165.238.118]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB7Lf0uR015219 for ; Sat, 7 Dec 2002 13:41:02 -0800 Received: from 5-C ([192.168.0.2]) by banna (8.9.3+3.2W/3.7W) with SMTP id GAA16288; Sun, 8 Dec 2002 06:45:02 +0900 Message-Id: <200212072145.GAA16288@banna> From: =?iso-2022-jp?B?aGFtaWw5OTk5anA=?= To: =?iso-2022-jp?B?MDU=?=@banna.sgi.com Reply-To: hmail9999jp@yahoo.co.jp Date: Sun, 08 Dec 2002 06:43:14 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2006 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hmail9999jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_h@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Sat Dec 7 13:51:12 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 13:51:14 -0800 (PST) Received: from phoenix.infradead.org (carisma.slowglass.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB7LpBuR015696 for ; Sat, 7 Dec 2002 13:51:12 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18Kmu9-0006Cg-00; Sat, 07 Dec 2002 21:54:33 +0000 Date: Sat, 7 Dec 2002 21:54:32 +0000 From: Christoph Hellwig To: Tod Detre Cc: linux-xfs@oss.sgi.com Subject: Re: xfs_growfs, lvm, and sparcs.... Message-ID: <20021207215432.A23843@infradead.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from tod@tod.net on Fri, Dec 06, 2002 at 09:35:16AM -0500 X-archive-position: 2007 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Fri, Dec 06, 2002 at 09:35:16AM -0500, Tod Detre wrote: > xfs kernel from cvs 2.4.20-xfs > xfsprogs from cvs (same as kernel) > Sparcstation 5, ide disks how did you get ide disks connected to a SS5? Sounds more like a Ultra5 to me. If it's really an Ultra5 and you use a sparc64 kernel with a 32bit userland the error is expected. From owner-linux-xfs@oss.sgi.com Sat Dec 7 15:49:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 07 Dec 2002 15:50:03 -0800 (PST) Received: from iris.acsalaska.net (iris.slb.nwc.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB7NnxuR021088 for ; Sat, 7 Dec 2002 15:49:59 -0800 Received: from erbenson.alaska.net (123-pm30.nwc.alaska.net [209.112.158.123]) by iris.acsalaska.net (8.12.5/8.12.5) with ESMTP id gB7NrLVe010952 for ; Sat, 7 Dec 2002 14:53:22 -0900 (AKST) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 90C9F3A0A for ; Sat, 7 Dec 2002 14:53:20 -0900 (AKST) Received: by plato.local.lan (Postfix, from userid 1000) id B2D714104E2; Sat, 7 Dec 2002 14:53:20 -0900 (AKST) Date: Sat, 7 Dec 2002 14:53:20 -0900 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: corrupted partition with grub in hda1 Message-ID: <20021207235320.GL21273@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <31634.1039253054@www20.gmx.net> <1039274667.1408.5.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pz0BBB9QxoYXlT+x" Content-Disposition: inline In-Reply-To: <1039274667.1408.5.camel@localhost.localdomain> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-archive-position: 2008 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs --Pz0BBB9QxoYXlT+x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 07, 2002 at 09:24:26AM -0600, Stephen Lord wrote: >=20 > It depends how far into the partition grub writes, but right > after the superblock is going to be the root inode. If you are > lucky it will have survived, if not everything in the filesystem > will have been moved into lost+found by repair. probably only 446 bytes since its most likly just the same first stage loader as goes in the MBR, but im sure it assumes it has a full 1K to play with in partitions since `they are always ext2' it looks like its time for another patch to make grub check and refuse to install on XFS partitions, i think it already checks filesystem type, and its already aware of XFS, it just needs to be taught not to stomp all over XFS. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --Pz0BBB9QxoYXlT+x 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 iEYEARECAAYFAj3yifAACgkQJKx7GixEevxVOACfUJ8GKtcV7Vne7oBJ7kHn6PJn 8xEAn0ZxmG9EblI7PUFiv23+Ky76wYJc =SH4o -----END PGP SIGNATURE----- --Pz0BBB9QxoYXlT+x-- From owner-linux-xfs@oss.sgi.com Sun Dec 8 02:29:21 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Dec 2002 02:29:24 -0800 (PST) Received: from gk.ka.epigenomics.net (qmailr@gk.ka.epigenomics.net [62.159.77.106]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB8ATJuR026714 for ; Sun, 8 Dec 2002 02:29:20 -0800 Received: (qmail 7442 invoked from network); 8 Dec 2002 10:32:40 -0000 Received: from einstein.epigenomics.epi (qmailr@192.168.1.4) by weinberg.epigenomics.epi with SMTP; 8 Dec 2002 10:32:40 -0000 Received: (qmail 23506 invoked from network); 8 Dec 2002 10:32:39 -0000 Received: from broglie.epigenomics.epi (qmailr@192.168.1.5) by einstein.epigenomics.epi with SMTP; 8 Dec 2002 10:32:39 -0000 Received: (qmail 1048 invoked by uid 9); 8 Dec 2002 10:32:39 -0000 From: Robert Sander Reply-To: Robert Sander X-Newsgroups: epi.ml.linux.xfs Subject: Debian XFS boot image at markybob.com Date: Sun, 8 Dec 2002 10:32:39 +0000 (UTC) Organization: Epigenomics AG Lines: 13 Message-ID: X-Complaints-To: usenet@epigenomics.com User-Agent: slrn/0.9.7.3 (Linux) To: linux-xfs@oss.sgi.com X-archive-position: 2009 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ml-linux-xfs@epigenomics.com Precedence: bulk X-list: linux-xfs Hi! http://www.markybob.com/xfsboot/ is currently unreachable (name does not resolve). Does anybody have any details about that? It's linked from the downloads section on the XFS page. Greetings -- Robert Sander Manager Information Systems www.epigenomics.com Kastanienallee 24 +493024345330 10435 Berlin From owner-linux-xfs@oss.sgi.com Sun Dec 8 04:10:39 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Dec 2002 04:10:43 -0800 (PST) Received: from ente.berdmann.de (frnk-d514e176.dsl.mediaWays.net [213.20.225.118]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB8CAbuR029350 for ; Sun, 8 Dec 2002 04:10:38 -0800 Received: from indigo-3.berdmann.de ([192.168.5.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.35 #1) id 18L0Jq-0001or-00 for linux-xfs@oss.sgi.com; Sun, 08 Dec 2002 13:13:58 +0100 Message-ID: <3DF33785.7060101@berdmann.de> Date: Sun, 08 Dec 2002 13:13:57 +0100 From: Bernhard Erdmann User-Agent: Mozilla/5.0 (X11; U; IRIX64 IP28; en-US; rv:1.3a) Gecko/20021206 X-Accept-Language: de, en, fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: xfsdump: drive_minrmt.c:1862: do_get_write_buf: Assertion `contextp->dc_nextp < contextp->dc_recendp' failed. Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2010 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: be@berdmann.de Precedence: bulk X-list: linux-xfs Hi, xfsdump 2.0.1 of 2.4.18-SGI_XFS_1.1 crashes when using the minimal tape protocol and a blocksize of 512 bytes: # xfsdump -J -F -b 512 -m -f /dev/st0 / xfsdump: using minimum scsi tape (drive_minrmt) strategy xfsdump: version 3.0 - Running single-threaded xfsdump: WARNING: no session label specified xfsdump: level 0 dump of apollo.berdmann.de:/ xfsdump: dump date: Sun Dec 8 13:07:17 2002 xfsdump: session id: 8b6fcdc9-f0cf-4367-86f4-7807cab42e09 xfsdump: session label: "" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: ino map phase 3: skipping (no pruning necessary) xfsdump: ino map phase 4: skipping (size estimated in phase 2) xfsdump: ino map phase 5: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 142520256 bytes xfsdump: preparing drive xfsdump: bad media file header at BOT indicates foreign or corrupted tape xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump media file header at beginning of media xfsdump: WARNING: repositioning to overwrite xfsdump: creating dump session media file 0 (media 0, file 1) xfsdump: dumping ino map xfsdump: drive_minrmt.c:1862: do_get_write_buf: Assertion `contextp->dc_nextp < contextp->dc_recendp' failed. Aborted (core dumped) It does work well using a blocksize of 32 KB: # xfsdump -J -F -b 32768 -m -f /dev/st0 / xfsdump: using minimum scsi tape (drive_minrmt) strategy xfsdump: version 3.0 - Running single-threaded xfsdump: WARNING: no session label specified xfsdump: level 0 dump of apollo.berdmann.de:/ xfsdump: dump date: Sun Dec 8 12:52:31 2002 xfsdump: session id: c94b4dc2-67a9-4837-95ec-c93c5a81bf81 xfsdump: session label: "" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: ino map phase 3: skipping (no pruning necessary) xfsdump: ino map phase 4: skipping (size estimated in phase 2) xfsdump: ino map phase 5: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 142106560 bytes xfsdump: preparing drive xfsdump: bad media file header at BOT indicates foreign or corrupted tape xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump media file header at beginning of media xfsdump: WARNING: repositioning to overwrite xfsdump: creating dump session media file 0 (media 0, file 1) xfsdump: dumping ino map xfsdump: dumping directories xfsdump: dumping non-directory files xfsdump: dump size (non-dir files) : 62014080 bytes xfsdump: NOTE: dump interrupted: 747 seconds elapsed xfsdump: Dump Status: INTERRUPT The tape drive is a Tandberg TDC 3820: # mt status SCSI 1 tape drive: File number=0, block number=0. Tape block size 512 bytes. Density code 0x10 (QIC-150/250 (GCR 10000 bpi)). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN (gdb) bt #0 0x40061921 in __kill () at __kill:-1 #1 0x4006169d in raise (sig=6) at ../sysdeps/posix/raise.c:27 #2 0x40062d08 in abort () at ../sysdeps/generic/abort.c:88 #3 0x4005ada1 in __assert_fail ( assertion=0x80784c0 "contextp->dc_nextp < contextp->dc_recendp", file=0x807b8ba "drive_minrmt.c", line=1862, function=0x8077223 "do_get_write_buf") at assert.c:74 #4 0x08058f25 in strcpy () at ../sysdeps/generic/strcpy.c:31 #5 0x08061b4a in strcpy () at ../sysdeps/generic/strcpy.c:31 #6 0x080722d7 in strcpy () at ../sysdeps/generic/strcpy.c:31 #7 0x0806adef in strcpy () at ../sysdeps/generic/strcpy.c:31 #8 0x0805cf02 in strcpy () at ../sysdeps/generic/strcpy.c:31 #9 0x4004f336 in __libc_start_main (main=0x805c46c , argc=9, ubp_av=0xbffffc54, init=0x80499ec <_init>, fini=0x80752d0 <_fini>, rtld_fini=0x4000d2fc <_dl_fini>, stack_end=0xbffffc4c) at ../sysdeps/generic/libc-start.c:129 From owner-linux-xfs@oss.sgi.com Sun Dec 8 04:21:25 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Dec 2002 04:21:26 -0800 (PST) Received: from ente.berdmann.de (frnk-d514e176.dsl.mediaWays.net [213.20.225.118]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB8CLNuR029795 for ; Sun, 8 Dec 2002 04:21:24 -0800 Received: from indigo-3.berdmann.de ([192.168.5.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.35 #1) id 18L0UG-0001pq-00 for linux-xfs@oss.sgi.com; Sun, 08 Dec 2002 13:24:44 +0100 Message-ID: <3DF33A0C.2090002@berdmann.de> Date: Sun, 08 Dec 2002 13:24:44 +0100 From: Bernhard Erdmann User-Agent: Mozilla/5.0 (X11; U; IRIX64 IP28; en-US; rv:1.3a) Gecko/20021206 X-Accept-Language: de, en, fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: xfsdump: drive_minrmt.c:1862: do_get_write_buf: Assertion `contextp->dc_nextp < contextp->dc_recendp' failed. References: <3DF33785.7060101@berdmann.de> In-Reply-To: <3DF33785.7060101@berdmann.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2011 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: be@berdmann.de Precedence: bulk X-list: linux-xfs > The tape drive is a Tandberg TDC 3820: > > # mt status > SCSI 1 tape drive: > File number=0, block number=0. > Tape block size 512 bytes. Density code 0x10 (QIC-150/250 (GCR 10000 bpi)). > Soft error count since last status=0 > General status bits on (41010000): > BOT ONLINE IM_REP_EN Reading further down the man page for xfsdump I discovered -q for QIC drives: -q Destination tape drive is a QIC tape. QIC tapes only use a 512 byte blocksize, for which xfsdump must make special allowances. Using this option xfsdump works properly: # xfsdump -J -F -q -f /dev/st0 /var/mrtg xfsdump: using scsi tape (drive_scsitape) strategy xfsdump: version 3.0 - Running single-threaded xfsdump: WARNING: no session label specified xfsdump: level 0 dump of apollo.berdmann.de:/var/mrtg xfsdump: dump date: Sun Dec 8 13:20:36 2002 xfsdump: session id: 5e94e959-40c2-4f11-ae7f-056d6eae5780 xfsdump: session label: "" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: ino map phase 3: skipping (no pruning necessary) xfsdump: ino map phase 4: skipping (size estimated in phase 2) xfsdump: ino map phase 5: skipping (only one dump stream) xfsdump: ino map construction complete xfsdump: estimated dump size: 4899584 bytes xfsdump: preparing drive xfsdump: bad media file header at BOT indicates foreign or corrupted tape xfsdump: WARNING: media contains non-xfsdump data or a corrupt xfsdump media file header at beginning of media xfsdump: WARNING: repositioning to overwrite xfsdump: creating dump session media file 0 (media 0, file 1) xfsdump: dumping ino map xfsdump: dumping directories xfsdump: dumping non-directory files xfsdump: ending media file xfsdump: media file size 8388608 bytes xfsdump: dump size (non-dir files) : 5388560 bytes xfsdump: dump complete: 129 seconds elapsed xfsdump: Dump Status: INCOMPLETE From owner-linux-xfs@oss.sgi.com Sun Dec 8 04:40:14 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 08 Dec 2002 04:40:19 -0800 (PST) Received: from vault8.local.pl (valis.net.pl [217.153.21.210]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB8Ce6uR002569 for ; Sun, 8 Dec 2002 04:40:12 -0800 Received: from 2p.pl (lupercal.local.pl [10.98.2.9]) by vault8.local.pl (Postfix) with ESMTP id 3A9E8A102 for ; Sun, 8 Dec 2002 13:31:51 +0100 (CET) Message-ID: <3DF33E8D.2090201@2p.pl> Date: Sun, 08 Dec 2002 13:43:57 +0100 From: Wojtek Aleksander User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020913 Debian/1.1-1 X-Accept-Language: pl, en-gb MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2012 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: dormitor@2p.pl Precedence: bulk X-list: linux-xfs Robert Sander wrote: > http://www.markybob.com/xfsboot/ is currently unreachable (name does not > resolve). Does anybody have any details about that? > > It's linked from the downloads section on the XFS page. Depending on what you want to do, you may want to try some other images or the Knoppix CD (this is full distibution which supports XFS and is based on Debian). For Debian install I succesfully used this image: http://people.debian.org/~blade/XFS-Install/download/ Visit the Debian website for more information: http://www.debian.org/CD/netinst/ DebianPlanet may also guide to some other interesting links. cheers! -- madman!? what madman!? thousands of madmen!!! From owner-linux-xfs@oss.sgi.com Mon Dec 9 06:26:29 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 06:26:33 -0800 (PST) Received: from b64198.tod.net (oh-clevelandheights4a-205.clvhoh.adelphia.net [24.50.237.205]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9EQSuR021299 for ; Mon, 9 Dec 2002 06:26:29 -0800 Received: from tod.net ([10.10.0.53]) (authenticated bits=0) by b64198.tod.net (8.12.6/8.12.6/Debian-8) with SMTP id gB9EUA0f009437 for ; Mon, 9 Dec 2002 09:30:10 -0500 Date: Mon, 9 Dec 2002 09:29:57 -0500 Subject: Re: xfs_growfs, lvm, and sparcs.... Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) From: Tod Detre To: linux-xfs@oss.sgi.com Content-Transfer-Encoding: 7bit In-Reply-To: <20021207215432.A23843@infradead.org> Message-Id: X-Mailer: Apple Mail (2.548) X-archive-position: 2013 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tod@tod.net Precedence: bulk X-list: linux-xfs oops, sorry, you're right it's an Ultrasparc 5 with 64bit kernel. Is there a way around this issue with the 64/32 bit difference? On Saturday, December 7, 2002, at 04:54 PM, Christoph Hellwig wrote: > On Fri, Dec 06, 2002 at 09:35:16AM -0500, Tod Detre wrote: >> xfs kernel from cvs 2.4.20-xfs >> xfsprogs from cvs (same as kernel) >> Sparcstation 5, ide disks > > how did you get ide disks connected to a SS5? Sounds more like a > Ultra5 > to me. If it's really an Ultra5 and you use a sparc64 kernel with a > 32bit userland the error is expected. > -- Tod Detre Unix Technical Support Case Western Reserve University usworkstation@po.cwru.edu 216-368-3060 From owner-linux-xfs@oss.sgi.com Mon Dec 9 06:57:58 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 06:58:02 -0800 (PST) Received: from trot (ool-4350143e.dyn.optonline.net [67.80.20.62]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9EvvuR022647 for ; Mon, 9 Dec 2002 06:57:57 -0800 Received: (qmail 28364 invoked by uid 1010); 9 Dec 2002 15:04:48 -0000 Date: Mon, 9 Dec 2002 10:04:48 -0500 From: George Georgalis To: linux-xfs@oss.sgi.com Subject: Re: corrupted partition with grub in hda1 Message-ID: <20021209150448.GA15645@trot.local> References: <31634.1039253054@www20.gmx.net> <1039274667.1408.5.camel@localhost.localdomain> <20021207235320.GL21273@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021207235320.GL21273@plato.local.lan> User-Agent: Mutt/1.3.28i X-archive-position: 2014 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgw@galis.org Precedence: bulk X-list: linux-xfs On Sat, Dec 07, 2002 at 02:53:20PM -0900, Ethan Benson wrote: >On Sat, Dec 07, 2002 at 09:24:26AM -0600, Stephen Lord wrote: >> >> It depends how far into the partition grub writes, but right >> after the superblock is going to be the root inode. If you are >> lucky it will have survived, if not everything in the filesystem >> will have been moved into lost+found by repair. > >probably only 446 bytes since its most likly just the same first stage >loader as goes in the MBR, but im sure it assumes it has a full 1K to >play with in partitions since `they are always ext2' > >it looks like its time for another patch to make grub check and refuse >to install on XFS partitions, i think it already checks filesystem >type, and its already aware of XFS, it just needs to be taught not to >stomp all over XFS. > That would be nice :) // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:george@galis.org Multimedia, DB, DNS and Metrics. http://www.galis.org/george From owner-linux-xfs@oss.sgi.com Mon Dec 9 07:34:51 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 07:34:55 -0800 (PST) Received: from trot (ool-4350143e.dyn.optonline.net [67.80.20.62]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9FYouR023556 for ; Mon, 9 Dec 2002 07:34:51 -0800 Received: (qmail 28689 invoked by uid 1010); 9 Dec 2002 15:41:41 -0000 Date: Mon, 9 Dec 2002 10:41:41 -0500 From: George Georgalis To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com Message-ID: <20021209154141.GB15645@trot.local> References: <3DF33E8D.2090201@2p.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DF33E8D.2090201@2p.pl> User-Agent: Mutt/1.3.28i X-archive-position: 2015 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgw@galis.org Precedence: bulk X-list: linux-xfs On Sun, Dec 08, 2002 at 01:43:57PM +0100, Wojtek Aleksander wrote: >Robert Sander wrote: >>http://www.markybob.com/xfsboot/ is currently unreachable (name does not >>resolve). Does anybody have any details about that? >> >>It's linked from the downloads section on the XFS page. > >Depending on what you want to do, you may want to try some other images >or the Knoppix CD (this is full distibution which supports XFS and is >based on Debian). For Debian install I succesfully used this image: >http://people.debian.org/~blade/XFS-Install/download/ I did some resesearch and found blade's images the best for a debian xfs woody install. There are a couple problems with them though (didn't try the cdrom, only the floppies): - you must make/use all 5 driver floppies even if you don't need extra drivers, I'm kinda new to debian, maybe I missed something... - the kernel is optimized for install bootstraping, recompile one for regular use, I think blade's uses udma 33, but there might have been other slow down factors. - the rescue image does not have xfsrestore or any xfsprogs on it. It would be good to note also that in the xfsprogs deb package /usr/sbin/xfsrestore is a symlink to /sbin/xfsrestore ...so if you hose your root partition with grub you can't use it. ;^) Cheers, // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:george@galis.org Multimedia, DB, DNS and Metrics. http://www.galis.org/george From owner-linux-xfs@oss.sgi.com Mon Dec 9 07:55:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 07:55:35 -0800 (PST) Received: from void.mpcf.com ([209.215.137.164]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9FtWuR024098 for ; Mon, 9 Dec 2002 07:55:33 -0800 Received: from mpcf.com (4thdimension.mpcf.com [209.215.137.190]) by void.mpcf.com (Postfix) with SMTP id CE21E292BF2 for ; Mon, 9 Dec 2002 08:49:29 -0500 (EST) Date: Sun, 8 Dec 2002 22:59:10 -0500 From: Kevin To: linux-xfs@oss.sgi.com Subject: XFS and kernel 2.4.18 error... need help Message-Id: <20021208225910.14793543.kevin@mpcf.com> Organization: MPCF X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 2016 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kevin@mpcf.com Precedence: bulk X-list: linux-xfs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 My primary file server crashed today. Upon reboot it couldn't mount the XFS partition. I am running 2.4.18 (compiling 2.4.19 right now, hoping it will work). I am not currently subbed to the list (doing so now). Any help would be GREATLY appreciated. Thanks, Kevin R. Marshall The following is from the syslog. Dec 9 10:40:31 filebox kernel: XFS mounting filesystem sd(8,4) Dec 9 10:40:34 filebox kernel: Starting XFS recovery on filesystem: sd(8,4) (dev: 8/4) Dec 9 10:40:34 filebox kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000010 Dec 9 10:40:34 filebox kernel: printing eip: Dec 9 10:40:34 filebox kernel: c02cfeba Dec 9 10:40:34 filebox kernel: *pde = 00000000 Dec 9 10:40:34 filebox kernel: Oops: 0000 Dec 9 10:40:34 filebox kernel: CPU: 1 Dec 9 10:40:34 filebox kernel: EIP: 0010:[] Not tainted Dec 9 10:40:34 filebox kernel: EFLAGS: 00010297 Dec 9 10:40:34 filebox kernel: eax: 00000010 ebx: ef3ad76c ecx: 00000010 edx: fffffffe Dec 9 10:40:34 filebox kernel: esi: ef3ad824 edi: 00000010 ebp: ffffffff esp: ef3ad6bc Dec 9 10:40:34 filebox kernel: ds: 0018 es: 0018 ss: 0018 Dec 9 10:40:34 filebox kernel: Process mount (pid: 260, stackpage=ef3ad000) Dec 9 10:40:34 filebox kernel: Stack: ef3ad70c 00000004 00000000 ef999800 ef999800 ef3ad73c ffffffff 00000000 Dec 9 10:40:34 filebox kernel: ffffffff c02d08b2 ef3ad70c 10c528f4 c02ebb7b ef3ad818 c01fcc62 ef3ad70c Dec 9 10:40:34 filebox kernel: c02ebb20 ef3ad818 00000000 07f98010 5f736678 746f6e69 3a70626f 6f6e6920 Dec 9 10:40:34 filebox kernel: Call Trace: [] [] [] [] [] Dec 9 10:40:34 filebox kernel: [] [] [] [] [] [] Dec 9 10:40:34 filebox kernel: [] [] [] [] [] [] Dec 9 10:40:35 filebox kernel: [] [] [] [] [] [] Dec 9 10:40:35 filebox kernel: [] [] [] [] [] [] Dec 9 10:40:35 filebox kernel: [] [] [] [] Dec 9 10:40:35 filebox kernel: Dec 9 10:40:35 filebox kernel: Code: 80 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 89 44 24 10 8b 44 - -- keyserver: http://pgp.mit.edu/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE99BUO4pH/bZtToq0RAmYOAJwPr1RNkrA9r7UKto6q+kapChEYeACfQmaJ FSLcbiAzt4DojA9fZlbjvMA= =mP76 -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Mon Dec 9 08:05:58 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 08:06:00 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9G5tuR024651 for ; Mon, 9 Dec 2002 08:05:56 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9FDrKp000458 for ; Mon, 9 Dec 2002 07:13:54 -0800 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA63412; Mon, 9 Dec 2002 10:09:15 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id KAA49593; Mon, 9 Dec 2002 10:09:14 -0600 (CST) Subject: Re: XFS and kernel 2.4.18 error... need help From: Eric Sandeen To: Kevin Cc: linux-xfs@oss.sgi.com In-Reply-To: <20021208225910.14793543.kevin@mpcf.com> References: <20021208225910.14793543.kevin@mpcf.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 09 Dec 2002 10:05:44 -0600 Message-Id: <1039449945.8142.2.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 2017 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Hi Kevin - Running your oops through ksymoops would give some clue about where things blew up. There is something in the log replay that is going wrong. As a last resort, you can use xfs_repair to zero out the log, but throwing away the log is a bit of a drastic step, so hold off on that until you try a newer kernel, I think. Was your 2.4.18 kernel the 1.1 release? And if you're upgrading to 2.4.19, I'd try the 1.2-pre3 release for that. Let us know what you find, -Eric On Sun, 2002-12-08 at 21:59, Kevin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > My primary file server crashed today. Upon reboot it > couldn't mount the XFS partition. > > I am running 2.4.18 (compiling 2.4.19 right now, hoping it > will work). > > I am not currently subbed to the list (doing so now). > > Any help would be GREATLY appreciated. > > Thanks, > Kevin R. Marshall > > The following is from the syslog. > > Dec 9 10:40:31 filebox kernel: XFS mounting filesystem > sd(8,4) Dec 9 10:40:34 filebox kernel: Starting XFS recovery > on filesystem: sd(8,4) (dev: 8/4) Dec 9 10:40:34 filebox > kernel: Unable to handle kernel NULL pointer dereference at > virtual address 00000010 Dec 9 10:40:34 filebox kernel: > printing eip: Dec 9 10:40:34 filebox kernel: c02cfeba > Dec 9 10:40:34 filebox kernel: *pde = 00000000 > Dec 9 10:40:34 filebox kernel: Oops: 0000 > Dec 9 10:40:34 filebox kernel: CPU: 1 > Dec 9 10:40:34 filebox kernel: EIP: 0010:[] > Not tainted Dec 9 10:40:34 filebox kernel: EFLAGS: 00010297 > Dec 9 10:40:34 filebox kernel: eax: 00000010 ebx: ef3ad76c > ecx: 00000010 edx: fffffffe Dec 9 10:40:34 filebox kernel: > esi: ef3ad824 edi: 00000010 ebp: ffffffff esp: ef3ad6bc > Dec 9 10:40:34 filebox kernel: ds: 0018 es: 0018 ss: 0018 > Dec 9 10:40:34 filebox kernel: Process mount (pid: 260, > stackpage=ef3ad000) Dec 9 10:40:34 filebox kernel: Stack: > ef3ad70c 00000004 00000000 ef999800 ef999800 ef3ad73c ffffffff > 00000000 Dec 9 10:40:34 filebox kernel: ffffffff > c02d08b2 ef3ad70c 10c528f4 c02ebb7b ef3ad818 c01fcc62 ef3ad70c > Dec 9 10:40:34 filebox kernel: c02ebb20 ef3ad818 > 00000000 07f98010 5f736678 746f6e69 3a70626f 6f6e6920 Dec 9 > 10:40:34 filebox kernel: Call Trace: [] [] > [] [] [] Dec 9 10:40:34 filebox > kernel: [] [] [] [] > [] [] Dec 9 10:40:34 filebox kernel: > [] [] [] [] > [] [] Dec 9 10:40:35 filebox kernel: > [] [] [] [] > [] [] Dec 9 10:40:35 filebox kernel: > [] [] [] [] > [] [] Dec 9 10:40:35 filebox kernel: > [] [] [] [] Dec 9 > 10:40:35 filebox kernel: Dec 9 10:40:35 filebox kernel: Code: > 80 38 00 74 07 40 4a 83 fa ff 75 f4 29 c8 89 44 24 10 8b 44 > > > - -- > keyserver: http://pgp.mit.edu/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.7 (GNU/Linux) > > iD8DBQE99BUO4pH/bZtToq0RAmYOAJwPr1RNkrA9r7UKto6q+kapChEYeACfQmaJ > FSLcbiAzt4DojA9fZlbjvMA= > =mP76 > -----END PGP SIGNATURE----- > -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Mon Dec 9 08:50:45 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 08:50:47 -0800 (PST) Received: from banna (pl374.nas926.o-tokyo.nttpc.ne.jp [210.165.238.118]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9GoJuR025463 for ; Mon, 9 Dec 2002 08:50:42 -0800 Received: from 5-C ([192.168.0.2]) by banna (8.9.3+3.2W/3.7W) with SMTP id BAA24364; Tue, 10 Dec 2002 01:54:40 +0900 Message-Id: <200212091654.BAA24364@banna> From: =?iso-2022-jp?B?aG1haWw4ODg4anA=?= To: =?iso-2022-jp?B?MDU=?=@banna.sgi.com Reply-To: hmail8888jp@yahoo.co.jp Date: Tue, 10 Dec 2002 01:52:54 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2018 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hmail8888jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_h@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Mon Dec 9 09:58:18 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 09:58:22 -0800 (PST) Received: from mailout1.echostar.com (mailout1.echostar.com [204.76.128.100]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9HwHuR026743 for ; Mon, 9 Dec 2002 09:58:18 -0800 Received: by riv-exchcon.echostar.com with Internet Mail Service (5.5.2653.19) id ; Mon, 9 Dec 2002 11:01:25 -0700 Received: from echostar.com (linux1.echostar.com [10.79.98.101]) by riv-exchcon.echostar.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YPPCG2WW; Mon, 9 Dec 2002 11:01:22 -0700 From: "Buzbee, James" To: linux-xfs@oss.sgi.com Message-ID: <3DF4DA72.3040905@echostar.com> Date: Mon, 09 Dec 2002 11:01:22 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 X-Accept-Language: en-us, en MIME-Version: 1.0 Subject: XFS and O_STREAMING X-Enigmail-Version: 0.62.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2019 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: James.Buzbee@echostar.com Precedence: bulk X-list: linux-xfs I've been looking at Robert Love's O_STREAMING patch for the kernel : http://www.kernel.org/pub/linux/kernel/people/rml/O_STREAMING/v2.4/O_STREAMING-rml-2.4.20-pre9-1.patch I find that it doesn't quite work as expected with XFS. It patches the generic_file_read/write routines to drop pages from cache list when a file is marked as O_STREAMING, but it appears to me as if XFS doesn't use the generic_file_write routine, but has its own version. I have a few questions. First, does this patch make sense for XFS? Could XFS's version of the generic_file_write routine be patched the same way? Or perhaps there is an equivalent way to accomplish the same thing using standard XFS. Jim From owner-linux-xfs@oss.sgi.com Mon Dec 9 10:27:54 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 10:27:57 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9IRsuR027349 for ; Mon, 9 Dec 2002 10:27:54 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9Iaekq017742 for ; Mon, 9 Dec 2002 12:36:40 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA87753 for ; Mon, 9 Dec 2002 12:31:14 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA98462 for ; Mon, 9 Dec 2002 12:31:13 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBA1jAw24059 for linux-xfs@oss.sgi.com; Mon, 9 Dec 2002 20:45:10 -0500 Resent-Message-Id: <200212100145.gBA1jAw24059@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA74793 for ; Mon, 9 Dec 2002 12:09:43 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB9I9gQb41045753 for ; Mon, 9 Dec 2002 10:09:42 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB9I7ua2021103 for ; Mon, 9 Dec 2002 19:07:56 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB9I7uW9021102 for hch@sgi.com; Mon, 9 Dec 2002 19:07:56 +0100 Date: Mon, 9 Dec 2002 19:07:56 +0100 From: Christoph Hellwig Message-Id: <200212091807.gB9I7uW9021102@lab343.munich.sgi.com> Subject: TAKE - rationalize pagebuf_iomove To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Mon, 9 Dec 2002 20:45:10 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2020 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs It's interesting how much code can go away if you merge a helper used by only one function into the latter.. Date: Mon Dec 9 10:03:59 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134775a linux/fs/xfs/pagebuf/page_buf.c - 1.85 - merge pagebuf_iomove and pagebuf_segment, get rid of off_t abuse in it linux/fs/xfs/pagebuf/page_buf.h - 1.52 - pagebuf_iomove doesn't take an off_t anymore From owner-linux-xfs@oss.sgi.com Mon Dec 9 11:55:53 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 11:55:55 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9JtruR031008 for ; Mon, 9 Dec 2002 11:55:53 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9K4ekq019668 for ; Mon, 9 Dec 2002 14:04:40 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id NAA86447 for ; Mon, 9 Dec 2002 13:59:18 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA89728 for ; Mon, 9 Dec 2002 13:59:16 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBA3DDf25867 for linux-xfs@oss.sgi.com; Mon, 9 Dec 2002 22:13:13 -0500 Resent-Message-Id: <200212100313.gBA3DDf25867@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA88748 for ; Mon, 9 Dec 2002 13:52:09 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gB9Jq7Qb31048098 for ; Mon, 9 Dec 2002 11:52:08 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gB9JoLK6021113 for ; Mon, 9 Dec 2002 20:50:21 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gB9JoLRl021112 for hch@sgi.com; Mon, 9 Dec 2002 20:50:21 +0100 Date: Mon, 9 Dec 2002 20:50:21 +0100 From: Christoph Hellwig Message-Id: <200212091950.gB9JoLRl021112@lab343.munich.sgi.com> Subject: TAKE - get rid of pb_daemon/pagebuf_daemon_t To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Mon, 9 Dec 2002 22:13:13 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2021 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Mon Dec 9 11:51:36 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134787a linux/fs/xfs/pagebuf/page_buf.c - 1.86 - replace pb_daemon with three individual variables, fix up sleep_on mess in the module unload path linux/fs/xfs/pagebuf/page_buf_internal.h - 1.20 - remove pagebuf_daemon_t From owner-linux-xfs@oss.sgi.com Mon Dec 9 11:56:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 11:56:04 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9Ju2uR031042 for ; Mon, 9 Dec 2002 11:56:02 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9K4nkq019676 for ; Mon, 9 Dec 2002 14:04:49 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id NAA96197 for ; Mon, 9 Dec 2002 13:59:28 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA83430 for ; Mon, 9 Dec 2002 13:59:25 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBA3DNV25872 for linux-xfs@oss.sgi.com; Mon, 9 Dec 2002 22:13:23 -0500 Resent-Message-Id: <200212100313.gBA3DNV25872@taclab54.munich.sgi.com> Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA67390 for ; Mon, 9 Dec 2002 13:56:10 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBA3A0T25748 for hch@sgi.com; Mon, 9 Dec 2002 22:10:00 -0500 Date: Mon, 9 Dec 2002 22:10:00 -0500 From: Christoph Hellwig Message-Id: <200212100310.gBA3A0T25748@taclab54.munich.sgi.com> Subject: TAKE - add a new xfs_mount parameter to xfs_blkdev_get Resent-From: hch@sgi.com Resent-Date: Mon, 9 Dec 2002 22:13:23 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2022 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Mon Dec 9 11:55:07 PST 2002 Workarea: taclab54.munich.sgi.com:/home/hch/repo/slinx/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:134788a linux/fs/xfs/xfs_vfsops.c - 1.403 - allocate struct xfs_mount early, pass it down to xfs_blkdev_get linux/fs/xfs/xfs_mount.h - 1.164 - remove second copy of a few prototypes linux/fs/xfs/linux/xfs_super.h - 1.35 - add a new xfs_mount parameter to xfs_blkdev_get linux/fs/xfs/linux/xfs_super.c - 1.236 - add a new xfs_mount parameter to xfs_blkdev_get. It's unused so far but will be needed for proper kernel-level exclusion in 2.5 From owner-linux-xfs@oss.sgi.com Mon Dec 9 12:01:46 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 12:01:47 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9K1juR032127 for ; Mon, 9 Dec 2002 12:01:45 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9KAWkq019768 for ; Mon, 9 Dec 2002 14:10:32 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA07483; Mon, 9 Dec 2002 14:05:08 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA35491; Mon, 9 Dec 2002 14:05:07 -0600 (CST) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id gB9K57102234; Mon, 9 Dec 2002 14:05:07 -0600 Subject: Re: XFS and O_STREAMING From: Steve Lord To: "Buzbee, James" Cc: linux-xfs@oss.sgi.com In-Reply-To: <3DF4DA72.3040905@echostar.com> References: <3DF4DA72.3040905@echostar.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1039464307.1381.11.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 09 Dec 2002 14:05:07 -0600 X-archive-position: 2023 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Mon, 2002-12-09 at 12:01, Buzbee, James wrote: > I've been looking at Robert Love's O_STREAMING patch for the kernel : > > http://www.kernel.org/pub/linux/kernel/people/rml/O_STREAMING/v2.4/O_STREAMING-rml-2.4.20-pre9-1.patch > > I find that it doesn't quite work as expected with XFS. It patches the > generic_file_read/write routines to drop pages from cache list when a > file is marked as O_STREAMING, but it appears to me as if XFS doesn't > use the generic_file_write routine, but has its own version. > > I have a few questions. First, does this patch make sense for XFS? > Could XFS's version of the generic_file_write routine be patched the > same way? Or perhaps there is an equivalent way to accomplish the same > thing using standard XFS. We do use generic_file_write, it is just buried underneath our own layer. O_STREAMING sounds like the old dropbehind stuff and should work just fine. One issue is that we do allocation of the actual blocks at flush time, we end up in writepage rather than in submit_bh. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Mon Dec 9 12:42:06 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 12:42:10 -0800 (PST) Received: from mailout1.echostar.com (mailout1.echostar.com [204.76.128.100]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9Kg5uR000422 for ; Mon, 9 Dec 2002 12:42:05 -0800 Received: by riv-exchcon.echostar.com with Internet Mail Service (5.5.2653.19) id ; Mon, 9 Dec 2002 13:45:26 -0700 Received: from echostar.com (linux1.echostar.com [10.79.98.101]) by riv-exchcon.echostar.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id YPPCGWQZ; Mon, 9 Dec 2002 13:45:21 -0700 From: "Buzbee, James" To: Steve Lord Cc: linux-xfs@oss.sgi.com Message-ID: <3DF500E1.3020401@echostar.com> Date: Mon, 09 Dec 2002 13:45:21 -0700 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 X-Accept-Language: en-us, en MIME-Version: 1.0 Subject: Re: XFS and O_STREAMING References: <3DF4DA72.3040905@echostar.com> <1039464307.1381.11.camel@jen.americas.sgi.com> X-Enigmail-Version: 0.62.4.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2024 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: James.Buzbee@echostar.com Precedence: bulk X-list: linux-xfs Steve Lord wrote: > On Mon, 2002-12-09 at 12:01, Buzbee, James wrote: > >>I've been looking at Robert Love's O_STREAMING patch for the kernel : >> >>http://www.kernel.org/pub/linux/kernel/people/rml/O_STREAMING/v2.4/O_STREAMING-rml-2.4.20-pre9-1.patch >> >>I find that it doesn't quite work as expected with XFS. It patches the >>generic_file_read/write routines to drop pages from cache list when a >>file is marked as O_STREAMING, but it appears to me as if XFS doesn't >>use the generic_file_write routine, but has its own version. >> >>I have a few questions. First, does this patch make sense for XFS? >>Could XFS's version of the generic_file_write routine be patched the >>same way? Or perhaps there is an equivalent way to accomplish the same >>thing using standard XFS. > > > We do use generic_file_write, it is just buried underneath our own > layer. O_STREAMING sounds like the old dropbehind stuff and should > work just fine. Hmmm... I'm trying it with 2.4.18 and xfs 1.1 For debugging, I put "printk's" at the top of generic_file_read and generic_file_write in linux/mm/filemap.c (the patched file) and I never see any output from the generic_file_write, just from the generic_file_read. > > One issue is that we do allocation of the actual blocks at flush time, > we end up in writepage rather than in submit_bh. I afraid I don't understand the ramifications of this with respect to the patch :-( Jim > > Steve > From owner-linux-xfs@oss.sgi.com Mon Dec 9 12:45:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 12:46:01 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9KjxuR000910 for ; Mon, 9 Dec 2002 12:45:59 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9Kskkq020745 for ; Mon, 9 Dec 2002 14:54:46 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA03706; Mon, 9 Dec 2002 14:49:24 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA31154; Mon, 9 Dec 2002 14:49:18 -0600 (CST) Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id gB9KnHI05881; Mon, 9 Dec 2002 14:49:17 -0600 Subject: Re: XFS and O_STREAMING From: Steve Lord To: "Buzbee, James" Cc: linux-xfs@oss.sgi.com In-Reply-To: <3DF500E1.3020401@echostar.com> References: <3DF4DA72.3040905@echostar.com> <1039464307.1381.11.camel@jen.americas.sgi.com> <3DF500E1.3020401@echostar.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1039466957.1384.14.camel@jen.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 09 Dec 2002 14:49:17 -0600 X-archive-position: 2025 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Mon, 2002-12-09 at 14:45, Buzbee, James wrote: > Steve Lord wrote: > > > > We do use generic_file_write, it is just buried underneath our own > > layer. O_STREAMING sounds like the old dropbehind stuff and should > > work just fine. > > > Hmmm... I'm trying it with 2.4.18 and xfs 1.1 For debugging, I put > "printk's" at the top of generic_file_read and generic_file_write in > linux/mm/filemap.c (the patched file) and I never see any output from > the generic_file_write, just from the generic_file_read. Ah, you mean back in ancient history we did not use it, we do in more recent code. To be honest I cannot remember what the code might have been doing in 1.1 anymore. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@sgi.com From owner-linux-xfs@oss.sgi.com Mon Dec 9 12:58:22 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 12:58:24 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9KwLuR001453 for ; Mon, 9 Dec 2002 12:58:21 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gB9K6KKp021890 for ; Mon, 9 Dec 2002 12:06:20 -0800 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 IAA29360; Tue, 10 Dec 2002 08:00:31 +1100 Received: (from nathans@localhost) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) id IAA71657; Tue, 10 Dec 2002 08:00:29 +1100 (EST) Date: Tue, 10 Dec 2002 08:00:29 +1100 From: Nathan Scott To: Steve Lord Cc: "Buzbee, James" , linux-xfs@oss.sgi.com Subject: Re: XFS and O_STREAMING Message-ID: <20021210080029.A172393@wobbly.melbourne.sgi.com> References: <3DF4DA72.3040905@echostar.com> <1039464307.1381.11.camel@jen.americas.sgi.com> <3DF500E1.3020401@echostar.com> <1039466957.1384.14.camel@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: <1039466957.1384.14.camel@jen.americas.sgi.com>; from lord@sgi.com on Mon, Dec 09, 2002 at 02:49:17PM -0600 X-archive-position: 2026 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs On Mon, Dec 09, 2002 at 02:49:17PM -0600, Steve Lord wrote: > On Mon, 2002-12-09 at 14:45, Buzbee, James wrote: > > Steve Lord wrote: > > > > > > We do use generic_file_write, it is just buried underneath our own > > > layer. O_STREAMING sounds like the old dropbehind stuff and should > > > work just fine. > > > > > > Hmmm... I'm trying it with 2.4.18 and xfs 1.1 For debugging, I put > > "printk's" at the top of generic_file_read and generic_file_write in > > linux/mm/filemap.c (the patched file) and I never see any output from > > the generic_file_write, just from the generic_file_read. > > Ah, you mean back in ancient history we did not use it, we do in > more recent code. To be honest I cannot remember what the code > might have been doing in 1.1 anymore. We also use generic_file_write_nolock() directly, rather than using generic_file_write (a thin wrapper around generic_file_write_nolock with added i_sem locking), so a printk in generic_file_write is not going to be tripped for an XFS filesystem. cheers. -- Nathan From owner-linux-xfs@oss.sgi.com Mon Dec 9 13:22:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 13:22:10 -0800 (PST) Received: from iris.acsalaska.net (iris.slb.nwc.acsalaska.net [209.112.155.43]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9LM4uR002064 for ; Mon, 9 Dec 2002 13:22:04 -0800 Received: from erbenson.alaska.net (250-pm16.nwc.alaska.net [209.112.141.250]) by iris.acsalaska.net (8.12.6/8.12.5) with ESMTP id gB9LPYDN036519 for ; Mon, 9 Dec 2002 12:25:35 -0900 (AKST) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id AED003A11 for ; Mon, 9 Dec 2002 11:52:41 -0900 (AKST) Received: by plato.local.lan (Postfix, from userid 1000) id 2A6C94104E2; Mon, 9 Dec 2002 11:52:41 -0900 (AKST) Date: Mon, 9 Dec 2002 11:52:41 -0900 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com Message-ID: <20021209205241.GC10532@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <3DF33E8D.2090201@2p.pl> <20021209154141.GB15645@trot.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bKyqfOwhbdpXa4YI" Content-Disposition: inline In-Reply-To: <20021209154141.GB15645@trot.local> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-archive-position: 2027 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs --bKyqfOwhbdpXa4YI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 09, 2002 at 10:41:41AM -0500, George Georgalis wrote: > On Sun, Dec 08, 2002 at 01:43:57PM +0100, Wojtek Aleksander wrote: > >Robert Sander wrote: > >>http://www.markybob.com/xfsboot/ is currently unreachable (name does not > >>resolve). Does anybody have any details about that? > >> > >>It's linked from the downloads section on the XFS page. > > > >Depending on what you want to do, you may want to try some other images= =20 > >or the Knoppix CD (this is full distibution which supports XFS and is=20 > >based on Debian). For Debian install I succesfully used this image: > >http://people.debian.org/~blade/XFS-Install/download/ >=20 >=20 > I did some resesearch and found blade's images the best for a debian xfs > woody install. >=20 > There are a couple problems with them though (didn't try the cdrom, only > the floppies): >=20 > - you must make/use all 5 driver floppies even if you don't need extra > drivers, I'm kinda new to debian, maybe I missed something... >=20 > - the kernel is optimized for install bootstraping, recompile one for > regular use, I think blade's uses udma 33, but there might have been > other slow down factors. >=20 > - the rescue image does not have xfsrestore or any xfsprogs on it. >=20 >=20 > It would be good to note also that in the xfsprogs deb package > /usr/sbin/xfsrestore is a symlink to /sbin/xfsrestore ...so if you hose > your root partition with grub you can't use it. ;^) ext2 dump/restore are also in /sbin as they should be. the idea is keep your / small and contained, then you can restore /usr and other large filesystems. screwing over / usually means your hosed anyway. --=20 Ethan Benson http://www.alaska.net/~erbenson/ --bKyqfOwhbdpXa4YI 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 iEYEARECAAYFAj31ApgACgkQJKx7GixEevycEwCeMSO+wlZH2tnhrZv7gShevYf/ 1OwAn3QRcs6WRvvxSG+175m0r71lh/JH =7Phd -----END PGP SIGNATURE----- --bKyqfOwhbdpXa4YI-- From owner-linux-xfs@oss.sgi.com Mon Dec 9 13:44:38 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 13:44:41 -0800 (PST) Received: from trot (ool-4350143e.dyn.optonline.net [67.80.20.62]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9LibuR002604 for ; Mon, 9 Dec 2002 13:44:38 -0800 Received: (qmail 9441 invoked by uid 1010); 9 Dec 2002 21:51:31 -0000 Date: Mon, 9 Dec 2002 16:51:31 -0500 From: George Georgalis To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com Message-ID: <20021209215131.GA9333@trot.local> References: <3DF33E8D.2090201@2p.pl> <20021209154141.GB15645@trot.local> <20021209205241.GC10532@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021209205241.GC10532@plato.local.lan> User-Agent: Mutt/1.3.28i X-archive-position: 2028 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgw@galis.org Precedence: bulk X-list: linux-xfs On Mon, Dec 09, 2002 at 11:52:41AM -0900, Ethan Benson wrote: >On Mon, Dec 09, 2002 at 10:41:41AM -0500, George Georgalis wrote: >> On Sun, Dec 08, 2002 at 01:43:57PM +0100, Wojtek Aleksander wrote: >> >Robert Sander wrote: >> >>http://www.markybob.com/xfsboot/ is currently unreachable (name does not >> >>resolve). Does anybody have any details about that? >> >> >> >>It's linked from the downloads section on the XFS page. >> > >> >Depending on what you want to do, you may want to try some other images >> >or the Knoppix CD (this is full distibution which supports XFS and is >> >based on Debian). For Debian install I succesfully used this image: >> >http://people.debian.org/~blade/XFS-Install/download/ >> >> >> I did some resesearch and found blade's images the best for a debian xfs >> woody install. >> >> There are a couple problems with them though (didn't try the cdrom, only >> the floppies): >> >> - you must make/use all 5 driver floppies even if you don't need extra >> drivers, I'm kinda new to debian, maybe I missed something... >> >> - the kernel is optimized for install bootstraping, recompile one for >> regular use, I think blade's uses udma 33, but there might have been >> other slow down factors. >> >> - the rescue image does not have xfsrestore or any xfsprogs on it. >> >> >> It would be good to note also that in the xfsprogs deb package >> /usr/sbin/xfsrestore is a symlink to /sbin/xfsrestore ...so if you hose >> your root partition with grub you can't use it. ;^) > >ext2 dump/restore are also in /sbin as they should be. the idea is >keep your / small and contained, then you can restore /usr and other >large filesystems. screwing over / usually means your hosed anyway. yes, accept in this case it looks as if /sbin/xfsrestore would have fixed my / quickly and easily, however it was easier to rebuild the os than to get xfsrestore on a running xfs compatible rescue image. In retrospect, I think it makes good sense to keep fs repair tools on both /sbin and /usr/sbin no need to link -s /usr/sbin/xfsrestore /sbin/xfsrestore when cp can save your arse. // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:george@galis.org Multimedia, DB, DNS and Metrics. http://www.galis.org/george From owner-linux-xfs@oss.sgi.com Mon Dec 9 14:08:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 14:08:38 -0800 (PST) Received: from K-7.stesmi.com (IDENT:ZttrRSeDx/0h9L+UNr0MAjY75GZGeAse@as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9M8XuR003212 for ; Mon, 9 Dec 2002 14:08:34 -0800 Received: from stesmi.com (IDENT:I5U7yZEp5PMDDGtp3qC+wpwWHP1KUnkR@as4-1-7.has.s.bonet.se [217.215.31.238]) by K-7.stesmi.com (8.12.4/8.12.4) with ESMTP id gB9MAwJP020963 for ; Mon, 9 Dec 2002 23:10:58 +0100 Message-ID: <3DF514F1.3050605@stesmi.com> Date: Mon, 09 Dec 2002 23:10:57 +0100 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: RH8 XFS 1.2pre3 DVD Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2029 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stesmi@stesmi.com Precedence: bulk X-list: linux-xfs Hi again people. I've now successfully played around a bit and managed to create an XFS enabled Redhat 8.0 DVD with all the latest updates. It's basically RH8 + all updates as of yesterday morning and 1.2pre3 kernel and tools. But, now to the two issues that exist with it: Can someone please tell me why the languages to choose from are limited to English languages in the XFS installer (you can select all in the original)? Also, what's the issue with grub? Why doesn't it work the way it should? Apart from these minor issues I can just push in the DVD and it autoboots and everything just like the originals do, except that it uses the 1.2pre3 kernel both for install and then to run, so it's really a RH8 + XFS 1.2pre3 DVD. I can even do the mediacheck. If anyone would want an iso I don't think it's that easy. It IS 3.5 GiB after all, but I might be able to put together some kind of script that would make all the steps necessary, it's a bit of manual patching in at least one step. Unless someone of course has the bandwidth available to serve 3.5 GiB files ... Thanx go out to the people that responded to my mails before, you know who you are. Especially the middle link from one of the mails (the one to personam.it) helped alot, although I didn't do it totally like they do :). // Stefan From owner-linux-xfs@oss.sgi.com Mon Dec 9 14:31:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 14:31:08 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9MV4uR003792 for ; Mon, 9 Dec 2002 14:31:04 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gB9Mdpkq022848 for ; Mon, 9 Dec 2002 16:39:51 -0600 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id QAA98663; Mon, 9 Dec 2002 16:34:25 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id QAA70007; Mon, 9 Dec 2002 16:34:25 -0600 (CST) Subject: Re: RH8 XFS 1.2pre3 DVD From: Eric Sandeen To: Stefan Smietanowski Cc: linux-xfs@oss.sgi.com In-Reply-To: <3DF514F1.3050605@stesmi.com> References: <3DF514F1.3050605@stesmi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 09 Dec 2002 16:30:52 -0600 Message-Id: <1039473052.8166.47.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-archive-position: 2030 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs On Mon, 2002-12-09 at 16:10, Stefan Smietanowski wrote: > Can someone please tell me why the languages to choose from are limited > to English languages in the XFS installer (you can select all in the > original)? It was certainly not intentional; perhaps it had to do with the installed locales on the build machine? > Also, what's the issue with grub? Why doesn't it work the way it should? I don't know -why- it doesn't work, but the grub data doesn't seem to hit the disk before the machine reboots. There was some discussion of this on the grub mailing list a while back... -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. 651-683-3102 From owner-linux-xfs@oss.sgi.com Mon Dec 9 14:35:39 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 14:35:40 -0800 (PST) Received: from K-7.stesmi.com (IDENT:gDcUaYA1WzJNRVpnzxl6IdRDuP0fQgBa@as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9MZbuR004225 for ; Mon, 9 Dec 2002 14:35:38 -0800 Received: from stesmi.com (IDENT:WfnVcxHBRt4ZY5T5dsXB6EJsWwaceIwd@as4-1-7.has.s.bonet.se [217.215.31.238]) by K-7.stesmi.com (8.12.4/8.12.4) with ESMTP id gB9Mc2JP021079; Mon, 9 Dec 2002 23:38:02 +0100 Message-ID: <3DF51B4A.2000808@stesmi.com> Date: Mon, 09 Dec 2002 23:38:02 +0100 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Sandeen CC: linux-xfs@oss.sgi.com Subject: Re: RH8 XFS 1.2pre3 DVD References: <3DF514F1.3050605@stesmi.com> <1039473052.8166.47.camel@stout.americas.sgi.com> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2031 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stesmi@stesmi.com Precedence: bulk X-list: linux-xfs Hi Eric. >>Can someone please tell me why the languages to choose from are limited >>to English languages in the XFS installer (you can select all in the >>original)? > > > It was certainly not intentional; perhaps it had to do with the > installed locales on the build machine? Hmm. That would make both the SGI machine and my machine to bork the same way and I find it hard to believe. My XFS DVD has the same problem as the SGI CD. >>Also, what's the issue with grub? Why doesn't it work the way it should? > > > I don't know -why- it doesn't work, but the grub data doesn't seem to > hit the disk before the machine reboots. There was some discussion of > this on the grub mailing list a while back... Starting grub manually and running those lines produce an error also, when one switches to a console and runs their commands. I don't have the error here of course, but since I'm running a test-install this moment I should have it in a few minutes. // Stefan From owner-linux-xfs@oss.sgi.com Mon Dec 9 15:05:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 15:05:38 -0800 (PST) Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gB9N5VuR005061 for ; Mon, 9 Dec 2002 15:05:32 -0800 Received: (from ragnark@localhost) by stine.vestdata.no (8.11.6/8.11.2) id gB9N91U03920; Tue, 10 Dec 2002 00:09:01 +0100 Date: Tue, 10 Dec 2002 00:09:01 +0100 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Stefan Smietanowski Cc: linux-xfs@oss.sgi.com Subject: Re: RH8 XFS 1.2pre3 DVD Message-ID: <20021210000901.F26400@vestdata.no> References: <3DF514F1.3050605@stesmi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3DF514F1.3050605@stesmi.com>; from stesmi@stesmi.com on Mon, Dec 09, 2002 at 11:10:57PM +0100 X-MIME-Autoconverted: from 8bit to quoted-printable by stine.vestdata.no id gB9N91U03920 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gB9N5XuR005062 X-archive-position: 2032 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xfs@ragnark.vestdata.no Precedence: bulk X-list: linux-xfs On Mon, Dec 09, 2002 at 11:10:57PM +0100, Stefan Smietanowski wrote: > If anyone would want an iso I don't think it's that easy. It IS 3.5 GiB > after all, but I might be able to put together some kind of script that > would make all the steps necessary, it's a bit of manual patching in at > least one step. Unless someone of course has the bandwidth available to > serve 3.5 GiB files ... Sure, if you just make the file available somewhere so it can be downloaded first. -- Ragnar Kjrstad From owner-linux-xfs@oss.sgi.com Mon Dec 9 17:27:51 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 09 Dec 2002 17:27:55 -0800 (PST) Received: from web20203.mail.yahoo.com (web20203.mail.yahoo.com [216.136.226.58]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBA1RguR007780 for ; Mon, 9 Dec 2002 17:27:51 -0800 Message-ID: <20021210013105.951.qmail@web20203.mail.yahoo.com> Received: from [202.219.216.203] by web20203.mail.yahoo.com via HTTP; Mon, 09 Dec 2002 17:31:05 PST Date: Mon, 9 Dec 2002 17:31:05 -0800 (PST) From: Allan Tang Subject: data journal with XFS To: linux-xfs@oss.sgi.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 2033 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tang_lingbo@yahoo.com Precedence: bulk X-list: linux-xfs Hi sirs, I have a question about the data journal under xfs. As I know, xfs only do meta-data journal when user changed the FS. Then when I want to write about 200 bytes to a file, the system crash happened at this point. What will happen on these data? Is it possible to see the partial data in this file? If the system crash happened immediately after the write system call returned, Is it possible to see the corrupt data the next time? If we can't guarantee the data consistency, how to improve the reliability of data, use O_SYNC or other ways? Thanks for any help. Regards, Allan __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com From owner-linux-xfs@oss.sgi.com Tue Dec 10 00:45:50 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 00:45:52 -0800 (PST) Received: from hob.prv.nwc.acsalaska.net (hob.slb.nwc.acsalaska.net [209.112.155.42]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBA8jnuR012931 for ; Tue, 10 Dec 2002 00:45:49 -0800 Received: from erbenson.alaska.net (95-pm30.nwc.alaska.net [209.112.158.95]) by hob.prv.nwc.acsalaska.net (8.12.6/8.12.6) with ESMTP id gBA8ne7f019108 for ; Mon, 9 Dec 2002 23:49:40 -0900 (AKST) (envelope-from erbenson@alaska.net) Received: from plato.local.lan (plato.local.lan [192.168.0.4]) by erbenson.alaska.net (Postfix) with ESMTP id 2778B3A11 for ; Mon, 9 Dec 2002 23:49:21 -0900 (AKST) Received: by plato.local.lan (Postfix, from userid 1000) id 2A2314104E2; Mon, 9 Dec 2002 23:49:21 -0900 (AKST) Date: Mon, 9 Dec 2002 23:49:21 -0900 From: Ethan Benson To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com Message-ID: <20021210084921.GD10532@plato.local.lan> Mail-Followup-To: linux-xfs@oss.sgi.com References: <3DF33E8D.2090201@2p.pl> <20021209154141.GB15645@trot.local> <20021209205241.GC10532@plato.local.lan> <20021209215131.GA9333@trot.local> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="at6+YcpfzWZg/htY" Content-Disposition: inline In-Reply-To: <20021209215131.GA9333@trot.local> User-Agent: Mutt/1.3.28i X-OS: Debian GNU X-gpg-fingerprint: E3E4 D0BC 31BC F7BB C1DD C3D6 24AC 7B1A 2C44 7AFC X-gpg-key: http://www.alaska.net/~erbenson/gpg/key.asc Mail-Copies-To: nobody X-No-CC: I subscribe to this list; do not CC me on replies. X-archive-position: 2034 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: erbenson@alaska.net Precedence: bulk X-list: linux-xfs --at6+YcpfzWZg/htY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 09, 2002 at 04:51:31PM -0500, George Georgalis wrote: >=20 > yes, accept in this case it looks as if /sbin/xfsrestore would have > fixed my / quickly and easily, however it was easier to rebuild the os > than to get xfsrestore on a running xfs compatible rescue image. >=20 > In retrospect, I think it makes good sense to keep fs repair tools > on both /sbin and /usr/sbin no need to link -s /usr/sbin/xfsrestore > /sbin/xfsrestore when cp can save your arse. no that makes no sense at all, if / is hosed your box won't boot, if you don't have a rescue disk with xfs_repair (or whatever fsck goes with the filesystem your using) your a loon. xfsrestore would not have helped you anyway, unless you had a dump of / handy. xfs_repair has no symlinks in /usr (neither should dump/restore, Nate just did that because his original packages were broken and put them in /usr, he just didn't want to break anyones scripts when fixing it). --=20 Ethan Benson http://www.alaska.net/~erbenson/ --at6+YcpfzWZg/htY 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 iEYEARECAAYFAj31qpAACgkQJKx7GixEevyZ/ACgiiT1jJhr/mY0zIblI+NvAjms 0XwAnjLNeTBGkv9KybV7DjJLHJWa5DDb =2GDx -----END PGP SIGNATURE----- --at6+YcpfzWZg/htY-- From owner-linux-xfs@oss.sgi.com Tue Dec 10 06:14:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 06:14:06 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAEE2uR031262 for ; Tue, 10 Dec 2002 06:14:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAEE2Yx031261 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 06:14:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAEE0uT031247 for ; Tue, 10 Dec 2002 06:14:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAE0NqF026522; Tue, 10 Dec 2002 06:00:23 -0800 Date: Tue, 10 Dec 2002 06:00:23 -0800 Message-Id: <200212101400.gBAE0NqF026522@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 197] stalled files in /var/lock, data fork in ino 79692177 claims free block 5040984 X-Bugzilla-Reason: AssignedTo X-archive-position: 2035 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=197 ------- Additional Comments From knutjbj@online.no 2002-12-10 06:00 ------- I think I have found away to reproduce this error by having a active v4l devices as I shutdown. The workaround is to first shutdown to init 1 and then do hdbparm -f /dev/hdb2. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 07:41:38 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 07:41:43 -0800 (PST) Received: from trot (ool-4350143e.dyn.optonline.net [67.80.20.62]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBAFfbuR032713 for ; Tue, 10 Dec 2002 07:41:37 -0800 Received: (qmail 22428 invoked by uid 1010); 10 Dec 2002 15:48:38 -0000 Date: Tue, 10 Dec 2002 10:48:38 -0500 From: George Georgalis To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com Message-ID: <20021210154838.GC20901@trot.local> References: <3DF33E8D.2090201@2p.pl> <20021209154141.GB15645@trot.local> <20021209205241.GC10532@plato.local.lan> <20021209215131.GA9333@trot.local> <20021210084921.GD10532@plato.local.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021210084921.GD10532@plato.local.lan> User-Agent: Mutt/1.3.28i X-archive-position: 2036 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgw@galis.org Precedence: bulk X-list: linux-xfs On Mon, Dec 09, 2002 at 11:49:21PM -0900, Ethan Benson wrote: >On Mon, Dec 09, 2002 at 04:51:31PM -0500, George Georgalis wrote: >> >> yes, accept in this case it looks as if /sbin/xfsrestore would have >> fixed my / quickly and easily, however it was easier to rebuild the os >> than to get xfsrestore on a running xfs compatible rescue image. >> >> In retrospect, I think it makes good sense to keep fs repair tools >> on both /sbin and /usr/sbin no need to link -s /usr/sbin/xfsrestore >> /sbin/xfsrestore when cp can save your arse. > >no that makes no sense at all, if / is hosed your box won't boot, if >you don't have a rescue disk with xfs_repair (or whatever fsck goes >with the filesystem your using) your a loon. I beg your pardon? Indeed /sbin/xfs_repair was the recommended tool. If I had copied it to /usr/sbin I (supposidly) could have repaired my root partition in no time. Oddly, I still think it makes good sence, even if I have lost my loon. // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:george@galis.org Multimedia, DB, DNS and Metrics. http://www.galis.org/george From owner-linux-xfs@oss.sgi.com Tue Dec 10 09:47:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 09:47:40 -0800 (PST) Received: from 61.51.21.10 (node-c-1d6b.a2000.nl [62.194.29.107]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBAHlUuR006366 for ; Tue, 10 Dec 2002 09:47:31 -0800 Message-Id: <200212101747.gBAHlUuR006366@oss.sgi.com> From: agata To: linux-xfs@oss.sgi.com Reply-To: agata@rediff.com Subject: URGENT ASSISTANCE Date: Tue, 10 Dec 2002 17:51:22 +0000 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="4aa268f9-cfed-41e7-9ace-bfcf7bc01a07" X-archive-position: 2037 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: agata@rediff.com Precedence: bulk X-list: linux-xfs This is a multi-part message in MIME format --4aa268f9-cfed-41e7-9ace-bfcf7bc01a07 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable FROM:MRS. A SESE-SEKO ATTN: I AM MRS.AGATA SESE-SEKO WIDOW OF LATE PRESIDENT MOBUTU SESE-SEKO OF ZAIRE? NOW KNOWN AS DEMOCRATIC REPUBLIC OF CONGO (DRC). I AM MOVED TO WRITE YOU THIS LETTER, THIS WAS IN CONFIDENCE CONSIDERING MY PRESENT CIRCUMSTANCE AND SITUATION. I ESCAPED ALONG WITH MY HUSBAND AND TWO OF OUR SONS TIMOTHY AND BASHER OUT OF DEMOCRATIC REPUBLIC OF CONGO (DRC) TO ABIDJAN,COTE D'IVOIRE WHERE MY FAMILY AND I SETTLED, WHILE WE LATER MOVED TO SETTLED IN MORROCO WHERE MY HUSBAND LATER DIED OF CANCER DISEASE. HOWEVER DUE TO THIS SITUATION WE DECIDED TO CHANGED MOST OF MY HUSBAND'S BILLIONS OF DOLLARS DEPOSITED IN SWISS BANK AND OTHER COUNTRIES INTO OTHER FORMS OF MONEY CODED FOR SAFE PURPOSE BECAUSE THE NEW HEAD OF STATE OF (DR) MR LAURENT KABILA HAS MADE ARRANGEMENT WITH THE SWISS GOVERNMENT AND OTHER EUROPEAN COUNTRIES TO FREEZE ALL MY LATE HUSBAND'TREASURES DEPOSITED IN SOME EUROPEAN COUNTRIES. HENCE MY CHILDREN AND I DECIDED LAYING LOW IN AFRICA TO STUDY THE SITUATION TILL WHEN THINGS GETS BETTER, LIKE NOW THAT PRESIDENT KABILA IS DEAD AND THE SON TAKING OVER(JOSEPH KABILA). ONE OF MY LATE HUSBAND'S CHATEAUX IN SOUTHERN FRANCE WAS CONFISCATED BY THE FRENCH GOVERNMENT, AND AS SUCH I HAD TO CHANGE MY IDENTITY SO THAT MY INVESTMENT WILL NOT BE TRACED AND CONFISCATED. I HAVE DEPOSITED THE SUM OF SEVENTY FIVE MLLION UNITED STATE DOLLARS (US$35,000,000,00.) WITH A SECURITY COMPANY , FOR SAFEKEEPING. THE FUNDS ARE SECURITY CODED TO PREVENT THEM FROM KNOWING THE CONTENT. WHAT I WANT YOU TO DO IS TO INDICATE YOUR INTEREST THAT YOU WILL ASSIST US BY RECEIVING THE MONEY ON OUR BEHALF IN EUROPE. I WANT YOU TO ASSIST IN INVESTING THIS MONEY, BUT I WILL NOT WANT MY IDENTITY REVEALED. I WILL ALSO WANT TO BUY PROPERTIES AND STOCK IN MULTI-NATIONAL COMPANIES AND TO ENGAGE IN OTHER SAFE AND NON-SPECULATIVE INVESTMENTS. MAY I AT THIS POINT EMPHASIS THE HIGH LEVEL OF CONFIDENTIALITY, WHICH THIS BUSINESS DEMANDS, AND HOPE YOU WILL NOT BETRAY THE TRUST AND CONFIDENCE, WHICH I REPOSE IN YOU IN CONCLUSION, IN THE EVENT YOU ARE INTERESTED TO ASSIST US I WILL LIKE YOU TO CONTACT MY LAWYER WHO I HAVE STATIONED IN HOLLAND TO WITHNESS THE TRANSACTION TO IS CONCLUTION.YOU CAN REACH HIM ON IS DIRECT LINE WHICH IS +31-613-904-392 OR VIA MAIL ADAMS_PHIL@REDIFFMAIL.COM HIS NAME IS ADAMS_PHIL@REDIFFMAIL.COM I HAVE FULL= TRUST IN HIM. I SINCERELY WILL ACKNOWLEGE YOUR RESPONSE TO THIS MAIL. BEST REGARDS, MRS A. SESE SEKO.=20=20 --4aa268f9-cfed-41e7-9ace-bfcf7bc01a07-- From owner-linux-xfs@oss.sgi.com Tue Dec 10 10:26:10 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 10:26:13 -0800 (PST) Received: from trot (ool-4350143e.dyn.optonline.net [67.80.20.62]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBAIQ9uR007115 for ; Tue, 10 Dec 2002 10:26:10 -0800 Received: (qmail 23885 invoked by uid 1010); 10 Dec 2002 18:33:12 -0000 Date: Tue, 10 Dec 2002 13:33:12 -0500 From: George Georgalis To: linux-xfs@oss.sgi.com Subject: Re: Debian XFS boot image at markybob.com Message-ID: <20021210183312.GB23550@trot.local> References: <3DF33E8D.2090201@2p.pl> <20021209154141.GB15645@trot.local> <20021209205241.GC10532@plato.local.lan> <20021209215131.GA9333@trot.local> <20021210084921.GD10532@plato.local.lan> <20021210154838.GC20901@trot.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021210154838.GC20901@trot.local> User-Agent: Mutt/1.3.28i X-archive-position: 2038 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: georgw@galis.org Precedence: bulk X-list: linux-xfs On Tue, Dec 10, 2002 at 10:48:38AM -0500, George Georgalis wrote: >On Mon, Dec 09, 2002 at 11:49:21PM -0900, Ethan Benson wrote: >>On Mon, Dec 09, 2002 at 04:51:31PM -0500, George Georgalis wrote: >>> >>> yes, accept in this case it looks as if /sbin/xfsrestore would have >>> fixed my / quickly and easily, however it was easier to rebuild the os >>> than to get xfsrestore on a running xfs compatible rescue image. >>> >>> In retrospect, I think it makes good sense to keep fs repair tools >>> on both /sbin and /usr/sbin no need to link -s /usr/sbin/xfsrestore >>> /sbin/xfsrestore when cp can save your arse. >> >>no that makes no sense at all, if / is hosed your box won't boot, if >>you don't have a rescue disk with xfs_repair (or whatever fsck goes >>with the filesystem your using) your a loon. > >I beg your pardon? > >Indeed /sbin/xfs_repair was the recommended tool. If I had copied it to >/usr/sbin I (supposidly) could have repaired my root partition in no >time. Oddly, I still think it makes good sence, even if I have lost my >loon. Then again maybe you are right, I am a duck, and not sure why xfs repair utilities are not on blade's rescue. http://people.debian.org/~blade/XFS-Install/download/floppies/root1440bf2.4-xfs.bin $ mv root1440bf2.4-xfs.bin root1440bf2.4-xfs.bin.gz $ gzip -d root1440bf2.4-xfs.bin.gz $ mkdir mnt # mount -oloop root1440bf2.4-xfs.bin mnt $ find mnt/ -type f | grep sbin mnt/sbin/udbootstrap mnt/sbin/lilo mnt/sbin/MAKEDEV mnt/sbin/badblocks mnt/sbin/depmod mnt/sbin/dhclient-2.2.x mnt/sbin/e2fsck mnt/sbin/tune2fs mnt/sbin/insmod mnt/sbin/ksyms mnt/sbin/lsmod mnt/sbin/modprobe mnt/sbin/mke2fs mnt/sbin/mkfs.ext2 mnt/sbin/rmmod mnt/sbin/update-modules mnt/sbin/losetup mnt/sbin/cfdisk mnt/sbin/fdisk mnt/sbin/mkreiserfs mnt/sbin/mkfs.xfs mnt/sbin/dbootstrap mnt/sbin/halt mnt/sbin/ifconfig mnt/sbin/init mnt/sbin/klogd mnt/sbin/loadkmap mnt/sbin/mkswap mnt/sbin/poweroff mnt/sbin/reboot mnt/sbin/route mnt/sbin/swapoff mnt/sbin/swapon mnt/sbin/syslogd mnt/usr/sbin/debootstrap mnt/usr/sbin/rdev mnt/usr/sbin/chroot Regards, // George -- GEORGE GEORGALIS, System Admin/Architect cell: 347-451-8229 Security Services, Web, Mail, mailto:george@galis.org Multimedia, DB, DNS and Metrics. http://www.galis.org/george From owner-linux-xfs@oss.sgi.com Tue Dec 10 12:01:03 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 12:01:05 -0800 (PST) Received: from anor.ics.muni.cz (root@relay.muni.cz [147.251.4.35]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBAK11uR011077 for ; Tue, 10 Dec 2002 12:01:02 -0800 Received: from anxur.fi.muni.cz (IDENT:0@anxur.fi.muni.cz [147.251.48.3]) by anor.ics.muni.cz (8.12.1/8.12.1) with ESMTP id gBAK4bx3024675 for ; Tue, 10 Dec 2002 21:04:37 +0100 Received: from aisa.fi.muni.cz (IDENT:12847@aisa [147.251.48.1]) by anxur.fi.muni.cz (8.11.6+Sun/8.8.5) with ESMTP id gBAK4a626698 for ; Tue, 10 Dec 2002 21:04:36 +0100 (MET) Received: (from xhejtman@localhost) by aisa.fi.muni.cz (8.8.5/8.8.5) id VAA64744345 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 21:04:35 +0100 (MET) Date: Tue, 10 Dec 2002 21:04:35 +0100 From: Lukas Hejtmanek To: linux-xfs@oss.sgi.com Subject: Re: XFS data corruption 2 Message-ID: <20021210210435.A65753608@aisa.fi.muni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Muni-Virus-Test: Clean X-MIME-Autoconverted: from 8bit to quoted-printable by anor.ics.muni.cz id gBAK4bx3024675 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBAK13uR011078 X-archive-position: 2039 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xhejtman@informatics.muni.cz Precedence: bulk X-list: linux-xfs Hello, today we've had power failure again I've noticed that I've got binary nulls in files last modified 19 minutes ago the power failure. Is that ok? Or there is a bug in xfs recovery? I'm using kernel 2.4.20 with xfs SGI XFS snapshot 2.4.20-2002-11-29_01:21_UTC with no debug enabled. -- Luk盪 Hejtm疣ek From owner-linux-xfs@oss.sgi.com Tue Dec 10 12:15:47 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 12:15:51 -0800 (PST) Received: from ubergeek ([209.184.141.189]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBAKFkuR011592 for ; Tue, 10 Dec 2002 12:15:47 -0800 Received: (qmail 164 invoked by uid 500); 10 Dec 2002 20:18:18 -0000 Subject: Re: XFS data corruption 2 From: Austin Gonyou To: Lukas Hejtmanek Cc: XFS List In-Reply-To: <20021210210435.A65753608@aisa.fi.muni.cz> References: <20021210210435.A65753608@aisa.fi.muni.cz> Content-Type: text/plain; charset=UTF-8 Organization: Coremetrics, Inc. Message-Id: <1039551498.31134.87.camel@UberGeek> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 10 Dec 2002 14:18:18 -0600 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBAKFluR011593 X-archive-position: 2040 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: austin@coremetrics.com Precedence: bulk X-list: linux-xfs On Tue, 2002-12-10 at 14:04, Lukas Hejtmanek wrote: > Hello, > > today we've had power failure again I've noticed that I've got binary > nulls in > files last modified 19 minutes ago the power failure. Is that ok? Or > there is > a bug in xfs recovery? I actually had a similar error recently. My DB server crashed, I then brought it back up, and had the dba's start oracle. It so happened that the Database thought it was still at 1AM, but the db didn't crash until 9AM. So we had to recover from archive logs several hours before. If we'd not had them, it could've been a frightful situation. Problem is, I'm using xfs 1.1. Anyone got data around that? > I'm using kernel 2.4.20 with xfs SGI XFS snapshot > 2.4.20-2002-11-29_01:21_UTC > with no debug enabled. > > -- > Lukﾃ｡ﾅ｡ Hejtmﾃ｡nek -- Austin Gonyou Coremetrics, Inc. From owner-linux-xfs@oss.sgi.com Tue Dec 10 12:47:39 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 12:47:41 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBAKlduR015684 for ; Tue, 10 Dec 2002 12:47:39 -0800 Received: by tapu.f00f.org (Postfix, from userid 1000) id 926781F18E2; Tue, 10 Dec 2002 12:51:15 -0800 (PST) Date: Tue, 10 Dec 2002 12:51:15 -0800 From: Chris Wedgwood To: Lukas Hejtmanek Cc: linux-xfs@oss.sgi.com Subject: Re: XFS data corruption 2 Message-ID: <20021210205115.GA2505@tapu.f00f.org> References: <200211201852.gAKIq1uR019332@oss.sgi.com> <20021120213842.GA21792@tapu.f00f.org> <20021120221435.GE3360@mail.muni.cz> <20021120224649.GA22116@tapu.f00f.org> <20021120231518.GH3360@mail.muni.cz> <20021120232013.GB22245@tapu.f00f.org> <20021120233618.GI3360@mail.muni.cz> <20021121001616.GA22564@tapu.f00f.org> <20021210194100.GB646@mail.muni.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021210194100.GB646@mail.muni.cz> User-Agent: Mutt/1.4i X-No-Archive: Yes X-archive-position: 2041 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Tue, Dec 10, 2002 at 08:41:00PM +0100, Lukas Hejtmanek wrote: > today we've had power failure again I've noticed that I've got > binary nulls in files last modified 19 minutes ago the power > failure. metadata is journalled --- not data; if you write to a file and crash (for example) you may see null bytes at the end of the file or similar > Is that ok? depends on your application; many applications know about these things and will deal with it one way or another (eg. mail software and databases). > Or there is a bug in xfs recovery? no --cw From owner-linux-xfs@oss.sgi.com Tue Dec 10 14:14:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 14:14:05 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAME1uR016782 for ; Tue, 10 Dec 2002 14:14:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAME1Ia016781 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 14:14:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAMDxuR016767 for ; Tue, 10 Dec 2002 14:13:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBALjukB016561; Tue, 10 Dec 2002 13:45:56 -0800 Date: Tue, 10 Dec 2002 13:45:56 -0800 Message-Id: <200212102145.gBALjukB016561@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] New: XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2042 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 Summary: XFS data corruption Product: Linux XFS Version: Current Platform: IA32 OS/Version: Linux Status: NEW Severity: critical Priority: High Component: XFS kernel code AssignedTo: xfs-master@oss.sgi.com ReportedBy: xhejtman@hell.ascs.muni.cz If this is a userspace bug, what version of the package are you using: What kernel are you using: 2.4.20. Where did the XFS code come from? (CVS, Linus, your distribution, etc): SGI XFS snapshot 2.4.20-2002-11-29_01:21_UTC with no debug enabled. From sgi ftp archive for kernel 2.4.20. Description of Problem: old closed files showing nulls on reboot if system crashed (power failure). so TeX source files. example.mf.old had time 19:51 example.mf had time 20:00 example.tex had time 20:10 power failure was at 20:11 and all that files contained only binary nulls. tex edited with vim, mf created with xfig then moved to *.old and example.mf extracted from mutt (mail). How Reproducible: just unplug power :-) Additional Information: I try to make some experiments in single mode and add some more info. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 14:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 14:44:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAMi1uR017431 for ; Tue, 10 Dec 2002 14:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAMi1aw017428 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 14:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAMhxuT017401 for ; Tue, 10 Dec 2002 14:44:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAMVFXJ017328; Tue, 10 Dec 2002 14:31:15 -0800 Date: Tue, 10 Dec 2002 14:31:15 -0800 Message-Id: <200212102231.gBAMVFXJ017328@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2043 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-10 14:31 ------- So, experiment I did: 1. turn on PC. Started X server and gnome environment. In my home I've created file xfs-test and edited with vim and write down about 10 chars and save it. Than I did gnome-session-save. I've waited about 1 minute and unplug power. After new startup I found xfs-test had only binary nulls, gnome did not start at all - session save had also only binary nulls. 2. the same as above but before unplugging the power I did sync manually. After startup everyting was ok. xfs-test and gnome session both correct. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 14:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 14:44:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAMi1uR017430 for ; Tue, 10 Dec 2002 14:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAMi1Xj017429 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 14:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBAMhxuR017401 for ; Tue, 10 Dec 2002 14:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBAMUxfg017319; Tue, 10 Dec 2002 14:30:59 -0800 Date: Tue, 10 Dec 2002 14:30:59 -0800 Message-Id: <200212102230.gBAMUxfg017319@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2043 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-10 14:30 ------- So, experiment I did: 1. turn on PC. Started X server and gnome environment. In my home I've created file xfs-test and edited with vim and write down about 10 chars and save it. Than I did gnome-session-save. I've waited about 1 minute and unplug power. After new startup I found xfs-test had only binary nulls, gnome did not start at all - session save had also only binary nulls. 2. the same as above but before unplugging the power I did sync manually. After startup everyting was ok. xfs-test and gnome session both correct. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 16:14:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 16:14:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBB0E1uR020112 for ; Tue, 10 Dec 2002 16:14:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBB0E1P6020111 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 16:14:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBB0DxuR020097 for ; Tue, 10 Dec 2002 16:13:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBB0CAm7020089; Tue, 10 Dec 2002 16:12:10 -0800 Date: Tue, 10 Dec 2002 16:12:10 -0800 Message-Id: <200212110012.gBB0CAm7020089@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2044 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 cattelan@thebarn.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Additional Comments From cattelan@thebarn.com 2002-12-10 16:12 ------- From FAQ Note time to sync is a functions of bdflush sync times. Q: Why do I see binary NULLS in some files after recovery when I unplugged the power? If it hurts don't do that! * NOTE: XFS 1.1 and kernels => 2.4.18 has the asynchronous delete path which means that you will see a lot less of these problems. If you still have not updated to the 1.1 release or later, now would be a good time! Basically this is normal behavior. XFS journals metadata updates, not data updates. After a crash you are supposed to get a consistent filesystem which looks like the state sometime shortly before the crash, NOT what the in memory image looked like the instant before the crash. Since XFS does not write data out to disk immediately unless you tell it to with fsync or an O_SYNC open (the same is true of other filesystems), you are looking at an inode which was flushed out to disk, but for which the data was never flushed to disk. You will find that the inode is not taking any disk space since all it has is a size, there are no disk blocks allocated for it yet. This same will apply to other metadata only journaling filesystems. The current linux kernel VM will write out the metadata after 1/60th of a second and the data after 30 seconds. So the possibility of losing data when unplugging the power within 30 seconds is quite large. The only way of being sure that your data will get to the disk is using fsync in the program of sync after closing the program. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 16:44:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 16:44:07 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBB0i2uR020856 for ; Tue, 10 Dec 2002 16:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBB0i2s1020855 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 16:44:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBB0hxuR020840 for ; Tue, 10 Dec 2002 16:44:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBB0J5HG020572; Tue, 10 Dec 2002 16:19:05 -0800 Date: Tue, 10 Dec 2002 16:19:05 -0800 Message-Id: <200212110019.gBB0J5HG020572@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2045 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 xhejtman@hell.ascs.muni.cz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-10 16:19 ------- That nothing to do with that FAQ. Don't you see that I'm reporting that corruption is on much more older data than last 30seconds?? Even 20minutes old data gets corrupted on onpluged power. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 16:45:36 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 16:45:37 -0800 (PST) Received: from srv.jp.mvd ([210.196.157.115]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBB0jYuR021052 for ; Tue, 10 Dec 2002 16:45:35 -0800 Received: from test2 (Juns.dyn.jp.mvd [10.2.11.143]) by srv.jp.mvd (8.11.6/3.7Wpl2-12) with SMTP id gBB0Xc412372; Wed, 11 Dec 2002 09:33:38 +0900 From: "Tang Lingbo\(Allan\)" To: "Chris Wedgwood" Cc: Subject: RE: XFS data corruption 2 Date: Wed, 11 Dec 2002 09:27:54 +0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <20021210205115.GA2505@tapu.f00f.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Importance: Normal Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by oss.sgi.com id gBB0jauR021263 X-archive-position: 2046 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: allan@mountainviewdata.com Precedence: bulk X-list: linux-xfs > -----Original Message----- > From: linux-xfs-bounce@oss.sgi.com > [mailto:linux-xfs-bounce@oss.sgi.com]On Behalf Of Chris Wedgwood > Sent: Wednesday, December 11, 2002 4:51 AM > To: Lukas Hejtmanek > Cc: linux-xfs@oss.sgi.com > Subject: Re: XFS data corruption 2 > > > On Tue, Dec 10, 2002 at 08:41:00PM +0100, Lukas Hejtmanek wrote: > > > today we've had power failure again I've noticed that I've got > > binary nulls in files last modified 19 minutes ago the power > > failure. > > metadata is journalled --- not data; if you write to a file and crash > (for example) you may see null bytes at the end of the file or similar > How about to use O_SYNC for file data change? It's also impossible to make sure the last write? > > Is that ok? > > depends on your application; many applications know about these things > and will deal with it one way or another (eg. mail software and > databases). > > > Or there is a bug in xfs recovery? > > no > > > > --cw > > From owner-linux-xfs@oss.sgi.com Tue Dec 10 17:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 17:44:05 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBB1i1uR022588 for ; Tue, 10 Dec 2002 17:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBB1i1pl022587 for linux-xfs@oss.sgi.com; Tue, 10 Dec 2002 17:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBB1hxuR022573 for ; Tue, 10 Dec 2002 17:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBB1Q9av022416; Tue, 10 Dec 2002 17:26:09 -0800 Date: Tue, 10 Dec 2002 17:26:09 -0800 Message-Id: <200212110126.gBB1Q9av022416@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2047 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-10 17:26 ------- I've changed xfs_sync in xfs_vfsops.c in sources to print some info whenever it is called. So I've started X server and gnome (in single user mode it seems to work correctly, no data corruption) and edited xfs-test file. Then I watched logs: Dec 11 02:11:26 hell kernel: XFS Sync called with flag BDFLUSH ATTR FSDATA Dec 11 02:12:16 hell kernel: XFS Sync called with flag BDFLUSH ATTR FSDATA Dec 11 02:12:51 hell kernel: XFS Sync called with flag BDFLUSH ATTR FSDATA Dec 11 02:12:56 hell kernel: XFS Sync called with flag BDFLUSH ATTR FSDATA Dec 11 02:13:01 hell kernel: XFS Sync called with flag BDFLUSH ATTR FSDATA Dec 11 02:14:11 hell kernel: XFS Sync called with flag BDFLUSH ATTR FSDATA The first you could see -- not each 30 seconds the flush is done. I've edited xfs-test file at 02:11:30. Then I've waited till 02:14:11 and unpluged power. After reboot as expected xfs-test contained just binary nulls. Is THAT OK? (There was no high load or i/o traffic that could delayed bdflush. The thing I've noticed -- after start it really do sync more often than 30 secs. But after some apps are started it slows down. Do not know why.) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Tue Dec 10 21:06:55 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 10 Dec 2002 21:06:57 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBB56tuR024779 for ; Tue, 10 Dec 2002 21:06:55 -0800 Received: by tapu.f00f.org (Postfix, from userid 1000) id 2CDD81FA346; Tue, 10 Dec 2002 21:10:33 -0800 (PST) Date: Tue, 10 Dec 2002 21:10:33 -0800 From: Chris Wedgwood To: "Tang Lingbo(Allan)" Cc: linux-xfs@oss.sgi.com Subject: Re: XFS data corruption 2 Message-ID: <20021211051033.GA4034@tapu.f00f.org> References: <20021210205115.GA2505@tapu.f00f.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-No-Archive: Yes X-archive-position: 2048 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Wed, Dec 11, 2002 at 09:27:54AM +0800, Tang Lingbo(Allan) wrote: > How about to use O_SYNC for file data change? Sure, that should work. Performance will suck. > It's also impossible to make sure the last write? I would *guess* it will work, but it should be tested. However, if it does work, don't expect it to always work. You *cannot* assume that writing to a file is the be-all-and-end-all for data security --- it's not. Mail Transfer Agents know this and have code to deal with this as appropriate. --cw From owner-linux-xfs@oss.sgi.com Wed Dec 11 08:14:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 08:14:06 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBGE1uR021579 for ; Wed, 11 Dec 2002 08:14:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBGE1To021578 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 08:14:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBGE0uR021564 for ; Wed, 11 Dec 2002 08:14:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBFmW6f021334; Wed, 11 Dec 2002 07:48:32 -0800 Date: Wed, 11 Dec 2002 07:48:32 -0800 Message-Id: <200212111548.gBBFmW6f021334@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2049 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From lord@sgi.com 2002-12-11 07:48 ------- Just a comment on the xfs_sync trace points. We will only get into xfs_sync code when there is metadata to sync, this is the reason you do not see one call every 30 seconds. File data does not make it out to disk via xfs_sync on linux, but via buffer head flushing activity from the bdflush daemon. One factor you have not reported on is the type of drive you are using here, and if it is IDE, is write caching turned on. Remember, a power cycle on an IDE device with write caching can lose you data. I do agree that this should not have been closed - you are running current code here. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Wed Dec 11 08:44:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 08:44:07 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBGi2uR022272 for ; Wed, 11 Dec 2002 08:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBGi2wp022271 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 08:44:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBGi0uR022257 for ; Wed, 11 Dec 2002 08:44:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBGYmQu022150; Wed, 11 Dec 2002 08:34:48 -0800 Date: Wed, 11 Dec 2002 08:34:48 -0800 Message-Id: <200212111634.gBBGYmQu022150@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2050 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-11 08:34 ------- All the drives are IDE drives with 2MB cache. Writecache is enabled by default, but if I've disabled it, it did the same - file corruption. I will do one more test, run script with disabled cache. I think that corruption occours only if I'm running X server (with closed source nvidia driver). By the way my friend with ide drive and write cache enabled does not see so much corruption. Currently I'm testing it with this script: ---- #!/bin/sh i=0; while [ $i != 100 ]; do echo fjhskjfhewk > /opt/tmp/xfstest.$i; sleep 1; echo $i; i=$[$i+1]; done sleep 40 echo "finished" ---- when I see finished, I unplug power and after start all files /opt/tmp/xfstest are full of binary nulls. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Wed Dec 11 09:24:57 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 09:25:02 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBBHOuuR023112 for ; Wed, 11 Dec 2002 09:24:56 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBBHXwkq026657 for ; Wed, 11 Dec 2002 11:33:58 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA02405 for ; Wed, 11 Dec 2002 11:28:31 -0600 (CST) Received: from jen.americas.sgi.com (jen.americas.sgi.com [128.162.232.100]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA09225 for ; Wed, 11 Dec 2002 11:28:31 -0600 (CST) From: Steve Lord Received: by jen.americas.sgi.com (8.11.6/SGI-client-1.7) id gBBHSVL04012; Wed, 11 Dec 2002 11:28:31 -0600 Message-Id: <200212111728.gBBHSVL04012@jen.americas.sgi.com> Date: Wed, 11 Dec 2002 11:28:31 -0600 Subject: TAKE - xfs iocore rework To: linux-xfs@oss.sgi.com X-archive-position: 2051 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs rework iocore infrastructure, remove some code and make it more orthogonal. In addition, add some of the hooks for unwritten extents. Date: Wed Dec 11 09:27:32 PST 2002 Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.4 Author: lord Merged by: lord Merged mods: 2.4.x-xfs-dev:slinx:134603a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:134603a linux/fs/xfs/xfs_iocore.c - 1.37 - Merge of 2.4.x-xfs-dev:slinx:134603a by lord. revamped iocore functions linux/fs/xfs/xfs_mount.h - 1.165 - Merge of 2.4.x-xfs-dev:slinx:134603a by lord. revamped iocore vector linux/fs/xfs/linux/xfs_lrw.h - 1.31 - Merge of 2.4.x-xfs-dev:slinx:134603a by lord. externs for iocore functions linux/fs/xfs/linux/xfs_lrw.c - 1.177 - Merge of 2.4.x-xfs-dev:slinx:134603a by lord. add xfs_bmap as a thin wrapper around xfs_iomap linux/fs/xfs/linux/xfs_aops.c - 1.16 - Merge of 2.4.x-xfs-dev:slinx:134603a by lord. some speedups of O_DIRECT and O_SYNC - in terms of allocating larger chunks of space. Also some unwritten extent hooks. linux/fs/xfs/linux/xfs_iomap.c - 1.3 - Merge of 2.4.x-xfs-dev:slinx:134603a by lord. rework iocore to be more orthogonal, add an unwritten extent conversion operation. From owner-linux-xfs@oss.sgi.com Wed Dec 11 09:35:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 09:35:39 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBBHZXuR023582 for ; Wed, 11 Dec 2002 09:35:33 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBBHiZkq026857 for ; Wed, 11 Dec 2002 11:44:35 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id LAA19287 for ; Wed, 11 Dec 2002 11:39:08 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA08936 for ; Wed, 11 Dec 2002 11:39:07 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBC0r1o29566 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 19:53:01 -0500 Resent-Message-Id: <200212120053.gBC0r1o29566@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA60933 for ; Wed, 11 Dec 2002 11:19:50 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBBHJnQb41774104 for ; Wed, 11 Dec 2002 09:19:49 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBBHI2Z9032719 for ; Wed, 11 Dec 2002 18:18:02 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBBHI1FJ032562 for hch@sgi.com; Wed, 11 Dec 2002 18:18:01 +0100 Date: Wed, 11 Dec 2002 18:18:01 +0100 From: Christoph Hellwig Message-Id: <200212111718.gBBHI1FJ032562@lab343.munich.sgi.com> Subject: TAKE - merge page_buf_private_t into page_buf_t To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Wed, 11 Dec 2002 19:53:00 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2052 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs The abstraction didn't buy us anything, all accesses from XFS code to pagebuf's are through the xfs_buf.h macros anyway. Date: Wed Dec 11 09:18:29 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:134949a linux/fs/xfs/xfsidbg.c - 1.212 - use page_buf_t instead of page_buf_private_t linux/fs/xfs/pagebuf/page_buf_locking.c - 1.35 linux/fs/xfs/pagebuf/page_buf.c - 1.87 - get rid of PBP() uses linux/fs/xfs/pagebuf/page_buf.h - 1.53 - add fields formerly in page_buf_private_t to page_buf_t linux/fs/xfs/pagebuf/page_buf_internal.h - 1.21 - remove page_buf_private_t From owner-linux-xfs@oss.sgi.com Wed Dec 11 10:44:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 10:44:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBIi1uR025318 for ; Wed, 11 Dec 2002 10:44:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBIi1NW025317 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 10:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBIhxuR025303 for ; Wed, 11 Dec 2002 10:43:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBIEj84025071; Wed, 11 Dec 2002 10:14:45 -0800 Date: Wed, 11 Dec 2002 10:14:45 -0800 Message-Id: <200212111814.gBBIEj84025071@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2053 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-11 10:14 ------- this script creates always correct files: ---- #!/bin/sh i=0; while [ $i != 100 ]; do dd if=/dev/urandom of=/opt/tmp/xfstest.$i bs=1k count=40; sleep 1; echo $i; i=$[$i+1]; done dd if=/dev/zero of=/opt/tmp/flush bs=1M count=4 sleep 40 echo "finished" ---- while this does not: ---- #!/bin/sh i=0; while [ $i != 100 ]; do echo "sjdfhakfj" > /opt/tmp/xfstest.$i; sleep 1; echo $i; i=$[$i+1]; done dd if=/dev/zero of=/opt/tmp/flush bs=1M count=4 sleep 40 echo "finished" ---- I've tried the second one to run 2 times and all 200 files were corrupted and the last one file 'flush' had zero length. By the way how can on disc cache to cache only data but not metadata? I've found out that on disc cache cannot be turned off with hdparm -W0 /dev/hdc, it says turnin off write cache but hdparm -i /dev/hdc says writecache enabled. Is is possible to do ordered writes as ext3 does? I've reformated /home partition to ext3 to avoid data looses and so far it looks pretty good however I would rather prefer xfs. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Wed Dec 11 10:52:26 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 10:52:27 -0800 (PST) Received: from phoenix.infradead.org (phoenix.mvhi.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBBIqOuR025806 for ; Wed, 11 Dec 2002 10:52:25 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18MC1b-0008Bl-00; Wed, 11 Dec 2002 18:56:03 +0000 Date: Wed, 11 Dec 2002 18:56:03 +0000 From: Christoph Hellwig To: Steve Lord Cc: linux-xfs@oss.sgi.com Subject: Re: TAKE - xfs iocore rework Message-ID: <20021211185603.A31466@infradead.org> References: <200212111728.gBBHSVL04012@jen.americas.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200212111728.gBBHSVL04012@jen.americas.sgi.com>; from lord@sgi.com on Wed, Dec 11, 2002 at 11:28:31AM -0600 X-archive-position: 2054 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Wed, Dec 11, 2002 at 11:28:31AM -0600, Steve Lord wrote: > rework iocore infrastructure, remove some code and make it more > orthogonal. In addition, add some of the hooks for unwritten extents. > > Date: Wed Dec 11 09:27:32 PST 2002 > Workarea: jen.americas.sgi.com:/src/lord/xfs-merge.2.4 > Author: lord > Merged by: lord > Merged mods: 2.4.x-xfs-dev:slinx:134603a As I'm preparing an update for Linus should I just modmerge it over to 2.5? From owner-linux-xfs@oss.sgi.com Wed Dec 11 10:53:55 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 10:53:56 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBBIrsuR026265 for ; Wed, 11 Dec 2002 10:53:54 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBBI27Kp029422 for ; Wed, 11 Dec 2002 10:02:07 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA26558 for ; Wed, 11 Dec 2002 12:57:29 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA45475 for ; Wed, 11 Dec 2002 12:57:28 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBC2BNA31441 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 21:11:23 -0500 Resent-Message-Id: <200212120211.gBC2BNA31441@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA15348 for ; Wed, 11 Dec 2002 12:48:16 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBBImFQb41274693 for ; Wed, 11 Dec 2002 10:48:15 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBBIkRcZ002134 for ; Wed, 11 Dec 2002 19:46:27 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBBIkRgG002133 for hch@sgi.com; Wed, 11 Dec 2002 19:46:27 +0100 Date: Wed, 11 Dec 2002 19:46:27 +0100 From: Christoph Hellwig Message-Id: <200212111846.gBBIkRgG002133@lab343.munich.sgi.com> Subject: TAKE - remove some dead code from pagebuf To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Wed, 11 Dec 2002 21:11:22 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2055 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Wed Dec 11 10:47:17 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:134960a linux/fs/xfs/pagebuf/page_buf.c - 1.89 linux/fs/xfs/pagebuf/page_buf.h - 1.60 - remove pagebuf_lookup and references to _PBF_PRIVATE_BH From owner-linux-xfs@oss.sgi.com Wed Dec 11 11:14:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 11:14:03 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBJE0uR001352 for ; Wed, 11 Dec 2002 11:14:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBJE01B001351 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 11:14:00 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBJDxuR001337 for ; Wed, 11 Dec 2002 11:13:59 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBIsIWs026465; Wed, 11 Dec 2002 10:54:18 -0800 Date: Wed, 11 Dec 2002 10:54:18 -0800 Message-Id: <200212111854.gBBIsIWs026465@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2056 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From michel@digirati.com.br 2002-12-11 10:54 ------- With workaround, try mount -odefaults,sync /home. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Wed Dec 11 12:44:03 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 12:44:08 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBKi2uR002722 for ; Wed, 11 Dec 2002 12:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBKi22e002721 for linux-xfs@oss.sgi.com; Wed, 11 Dec 2002 12:44:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBBKi0uR002707 for ; Wed, 11 Dec 2002 12:44:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBBKMAre002618; Wed, 11 Dec 2002 12:22:10 -0800 Date: Wed, 11 Dec 2002 12:22:10 -0800 Message-Id: <200212112022.gBBKMAre002618@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2057 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-11 12:22 ------- mount with sync helped. No file corruption at all. I can also hear drive working after each file is created. However sync decreases performance :-( ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Wed Dec 11 13:32:25 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 11 Dec 2002 13:32:29 -0800 (PST) Received: from banna (pl234.nas925.o-tokyo.nttpc.ne.jp [210.165.105.234]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBBLW2uR003472 for ; Wed, 11 Dec 2002 13:32:22 -0800 Received: from D ([192.168.0.2]) by banna (8.9.3+3.2W/3.7W) with SMTP id GAA18007; Thu, 12 Dec 2002 06:37:15 +0900 Message-Id: <200212112137.GAA18007@banna> From: =?iso-2022-jp?B?aW5mb3dlYm1haWxqcA==?= To: =?iso-2022-jp?B?MDU=?=@banna.sgi.com Reply-To: infowebmailjp@yahoo.co.jp Date: Thu, 12 Dec 2002 06:33:50 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2058 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: infowebmailjp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_ssn@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Thu Dec 12 06:55:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 06:55:42 -0800 (PST) Received: from smtp3.libero.it (smtp3.libero.it [193.70.192.127]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCEtYuR002272 for ; Thu, 12 Dec 2002 06:55:35 -0800 Received: from flameeyes.is-a-geek.org (151.25.17.252) by smtp3.libero.it (6.7.015) id 3DF0A6F4002CE832 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 15:37:08 +0100 Message-ID: Date: Thu, 12 Dec 2002 15:35:55 +0100 From: Flameeyes User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: it, en, fr, es MIME-Version: 1.0 X-Newsgroups: mls.linux.xfs Subject: Kernel 2.4.20 and XFS 1.2pre3 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit To: linux-xfs@oss.sgi.com X-Gate: Hamster/1.3.23.210 NewsToMail-Gate X-archive-position: 2059 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: diego_p@libero.it Precedence: bulk X-list: linux-xfs There's some patches for use XFS 1.2pre3 under 2.4.20? Or the only release for 2.4.20 is the 1.1 stable? Thanks, -- Flameeyes http://drakeadmin.sourceforge.net/ From owner-linux-xfs@oss.sgi.com Thu Dec 12 07:35:54 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 07:36:00 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCFZsuR003956 for ; Thu, 12 Dec 2002 07:35:54 -0800 Received: from relay1.corp.sgi.com (spindle.corp.sgi.com [198.29.75.13]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBCEiDKp022447 for ; Thu, 12 Dec 2002 06:44:13 -0800 Received: from Liberator (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id HAA18794; Thu, 12 Dec 2002 07:39:02 -0800 (PST) Subject: Re: Kernel 2.4.20 and XFS 1.2pre3 From: Eric Sandeen To: Flameeyes Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 12 Dec 2002 09:38:56 -0600 Message-Id: <1039707538.8783.76.camel@Liberator> Mime-Version: 1.0 X-archive-position: 2060 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs There are only cvs snapshots for 2.4.20. The 1.2pre3 patches are for 2.4.19, the 1.1 stable patches are for 2.4.18. -Eric On Thu, 2002-12-12 at 08:35, Flameeyes wrote: > There's some patches for use XFS 1.2pre3 under 2.4.20? > Or the only release for 2.4.20 is the 1.1 stable? > Thanks, > > -- > Flameeyes > http://drakeadmin.sourceforge.net/ > From owner-linux-xfs@oss.sgi.com Thu Dec 12 08:10:37 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 08:10:39 -0800 (PST) Received: from asterix.spider-net.de (pD952AACE.dip.t-dialin.net [217.82.170.206]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCGAOuR006481 for ; Thu, 12 Dec 2002 08:10:27 -0800 Received: by asterix.spider-net.de (Postfix, from userid 501) id 53F151082; Thu, 12 Dec 2002 17:13:58 +0100 (CET) X-Priority: 2 (High) Priority: urgent Received: from outgoing.securityfocus.com (outgoing3.securityfocus.com [66.38.151.27]) by odin.spider-net.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id UAA30144 for ; Tue, 16 Apr 2002 20:56:38 +0200 Received: from lists.securityfocus.com (lists.securityfocus.com [66.38.151.19]) by outgoing.securityfocus.com (Postfix) with QMQP id 176EAA3199; Tue, 16 Apr 2002 10:52:43 -0600 (MDT) Mailing-List: contact bugtraq-help@securityfocus.com; run by ezmlm Precedence: bulk Delivered-To: mailing list bugtraq@securityfocus.com Delivered-To: moderator for bugtraq@securityfocus.com Received: (qmail 8733 invoked from network); 15 Apr 2002 23:30:13 -0000 Content-Type: text/plain; charset="iso-8859-1" Date: Mon, 15 Apr 2002 18:32:38 -0500 X-Mailer: XFMail 1.4.0 on Linux References: <10204151449.ZM268355@einstein.csd.sgi.com> In-Reply-To: <10204151449.ZM268355@einstein.csd.sgi.com> X-DigitalOffense: TRUE MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200204151832.38497.sflist@digitaloffense.net> X-UIDL: af6fa726298b5ea78d5ebc12c9ba9a35 From: H D Moore To: agent99@sgi.com, linux-xfs@oss.sgi.com, bugtraq@securityfocus.com Subject: Re: IRIX XFS filesystem denial of service attack X-archive-position: 2062 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sflist@digitaloffense.net Precedence: bulk X-list: linux-xfs Does this vulnerability affect the Linux XFS port? The XFS page has no information about this or whether there is a fix available: http://oss.sgi.com/projects/xfs/ -HD On Monday 15 April 2002 04:49 pm, SGI Security Coordinator wrote: > > SGI Security Advisory > > Title: IRIX XFS filesystem denial of service attack > Number: 20020402-01-P > Date: April 15, 2002 > Reference: CAN-2002-0042 > ----------------------- > --- Issue Specifics --- > ----------------------- > > It has been reported that there is a vulnerability in IRIX's XFS > filesystem. Under some circumstances, a user can create a file that would > hang any application that would try to access it. This has the potential > to be used to create a Denial of Service attack. From owner-linux-xfs@oss.sgi.com Thu Dec 12 08:10:28 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 08:10:33 -0800 (PST) Received: from asterix.spider-net.de (pD952AACE.dip.t-dialin.net [217.82.170.206]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCGAOuR006480 for ; Thu, 12 Dec 2002 08:10:27 -0800 Received: by asterix.spider-net.de (Postfix, from userid 501) id 44AC21081; Thu, 12 Dec 2002 17:13:58 +0100 (CET) X-Priority: 2 (High) Priority: urgent Received: from outgoing.securityfocus.com (outgoing3.securityfocus.com [66.38.151.27]) by odin.spider-net.de (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id AAA30562 for ; Wed, 17 Apr 2002 00:07:00 +0200 Received: from lists.securityfocus.com (lists.securityfocus.com [66.38.151.19]) by outgoing.securityfocus.com (Postfix) with QMQP id B4ADCA33C9; Tue, 16 Apr 2002 15:44:14 -0600 (MDT) Mailing-List: contact bugtraq-help@securityfocus.com; run by ezmlm Precedence: bulk Delivered-To: mailing list bugtraq@securityfocus.com Delivered-To: moderator for bugtraq@securityfocus.com Received: (qmail 11500 invoked from network); 16 Apr 2002 21:37:35 -0000 In-Reply-To: <200204151832.38497.sflist@digitaloffense.net> References: <10204151449.ZM268355@einstein.csd.sgi.com> <200204151832.38497.sflist@digitaloffense.net> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: XFMail 1.4.0 on Linux Date: 16 Apr 2002 16:40:00 -0500 Message-Id: <1018993200.8789.377.camel@stout.americas.sgi.com> Mime-Version: 1.0 X-UIDL: d71837bf52882729dd9ea2b4ad8019dd From: Eric Sandeen To: H D Moore Subject: Re: IRIX XFS filesystem denial of service attack Cc: agent99@sgi.com, linux-xfs@oss.sgi.com, bugtraq@securityfocus.com X-archive-position: 2061 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs hi HD - I don't believe that Linux is affected. I've been told that the Linux I/O path was written specifically to avoid this problem, and I have run some test cases from our original bug report, and did not see the described behavior. I'll look a bit more and reply when I know for sure. -Eric On Mon, 2002-04-15 at 18:32, H D Moore wrote: > Does this vulnerability affect the Linux XFS port? The XFS page has no > information about this or whether there is a fix available: -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@sgi.com SGI, Inc. From owner-linux-xfs@oss.sgi.com Thu Dec 12 10:44:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 10:44:06 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBCIi2uR013234 for ; Thu, 12 Dec 2002 10:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBCIi1Xr013233 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 10:44:01 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBCIi0uR013219 for ; Thu, 12 Dec 2002 10:44:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBCINuwY013099; Thu, 12 Dec 2002 10:23:56 -0800 Date: Thu, 12 Dec 2002 10:23:56 -0800 Message-Id: <200212121823.gBCINuwY013099@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2063 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From cattelan@thebarn.com 2002-12-12 10:23 ------- Ran script several times on TOT and was able to recover with all files containing correct data. This was on ide with and without write cacheing and scsi. I suggest run on as minimal kernel as possible just to see if something else if factoring into the problem. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Thu Dec 12 11:14:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 11:14:03 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBCJE2uR014265 for ; Thu, 12 Dec 2002 11:14:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBCJE2LU014264 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 11:14:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBCJE0uR014250 for ; Thu, 12 Dec 2002 11:14:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBCImE8J013650; Thu, 12 Dec 2002 10:48:14 -0800 Date: Thu, 12 Dec 2002 10:48:14 -0800 Message-Id: <200212121848.gBCImE8J013650@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2064 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-12 10:48 ------- Maybe NVidia driver causes file corruption in some way (both closed and open source) or AGP and Athlon cpu. (Using AMD Thunderbird 1200MHz and ASUS A7V motherboard). I'm unable to corrupt files in text mode after system is up. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Thu Dec 12 11:36:50 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 11:36:54 -0800 (PST) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.58.33]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCJanuR014854 for ; Thu, 12 Dec 2002 11:36:50 -0800 Received: from Shiva (shiva [192.168.3.20]) by ishtar.tlinx.org (8.12.6/8.12.2/SuSE Linux 0.6) with ESMTP id gBCIgu7x005081 for ; Thu, 12 Dec 2002 10:42:56 -0800 From: "LA Walsh" To: Subject: FW: xfs crashes; 2.4.19; both times started with xfsdump level 0; Date: Thu, 12 Dec 2002 10:42:56 -0800 Message-ID: <000d01c2a20e$49994ae0$1403a8c0@sc.tlinx.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBCJaouR014855 X-archive-position: 2065 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: law@tlinx.org Precedence: bulk X-list: linux-xfs This may be worthless news since its from a September xfs version, but I thought I'd at least mention it. xfs sources dated around 9-27-02 (latest dated .h, xfs_arch, latest before that was 9-19. It was a "all" patch, I believe, the first for 2.4.19. I've sorta been waiting on update for 2.4.20 before trying another update but this is also the kernel that can take a long time to umount an otherwise quiet xfs disk and the one that seems to lose memory to xfs over time. I don't have a cvs source tree that I make kernels from (am not quite that flush with extra time and disk space right now)... Linda Dec 12 09:41:01 ishtar kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on sd(8,3). Returning error. Dec 12 09:41:01 ishtar kernel: xfs_inactive: xfs_ifree() returned an error = 22 on sd(8,3) Dec 12 09:41:01 ishtar kernel: xfs_force_shutdown(sd(8,3),0x1) called from line 1906 of file xfs_vnodeops.c. Return address = 0xc01ef1f4 Dec 12 09:41:01 ishtar kernel: Fatal error on root filesystem Dec 12 09:41:01 ishtar kernel: kernel BUG at debug.c:101! Dec 12 09:41:01 ishtar kernel: invalid operand: 0000 Dec 12 09:41:01 ishtar kernel: CPU: 1 Dec 12 09:41:01 ishtar kernel: EIP: 0010:[cmn_err+100/120] Not tainted Dec 12 09:41:01 ishtar kernel: EIP: 0010:[] Not tainted Dec 12 09:41:01 ishtar kernel: EFLAGS: 00010246 Dec 12 09:41:01 ishtar kernel: eax: 0000001f ebx: ec59fa08 ecx: 00000001 edx: 00000001 Dec 12 09:41:01 ishtar kernel: esi: 00000000 edi: 00000000 ebp: 00000001 esp: ec59fa00 Dec 12 09:41:01 ishtar kernel: ds: 0018 es: 0018 ss: 0018 Dec 12 09:41:01 ishtar kernel: Process xfsdump (pid: 4615, stackpage=ec59f000) Dec 12 09:41:01 ishtar kernel: Stack: f7d39c00 00000000 61746146 7265206c 20726f72 72206e6f 20746f6f 656c6966 Dec 12 09:41:01 ishtar kernel: 74737973 30006d65 666f2036 6c696620 66782065 6e765f73 6f65646f 632e7370 Dec 12 09:41:01 ishtar kernel: 5220202e 72757465 6461206e 73657264 203d2073 30637830 31666531 20003466 Dec 12 09:41:01 ishtar kernel: Call Trace: [xfs_inotobp+304/496] [xfs_trans_read_buf+677/748] [xfs_iunlink_remove+105/908] [xfs_iunlink_remove+630/908] [xfs_iunlink_remove+808/908] Dec 12 09:41:01 ishtar kernel: Call Trace: [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [xfs_do_force_shutdown+61/232] [xfs_do_force_shutdown+109/232] [xfs_inactive+968/1040] [vn_rele+53/132] [linvfs_clear_inode+19/36] [clear_inode+101/172] Dec 12 09:41:01 ishtar kernel: [] [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [iput+226/472] [xfs_iput+28/36] [xfs_bulkstat_one+1215/1240] [huft_build+1458/1480] [xfs_bulkstat_single+63/352] [huft_build+1458/1480] Dec 12 09:41:01 ishtar kernel: [] [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [xfs_ioctl+1425/5379] [extract_entropy+729/836] [xfs_bmap_do_search_extents+676/856] [xfs_bmbt_get_state+51/60] [alloc_inode+48/300] [__alloc_pages+67/372] Dec 12 09:41:01 ishtar kernel: [] [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [proc_root_lookup+57/72] [_alloc_pages+22/24] [do_anonymous_page+239/268] [do_no_page+51/492] [handle_mm_fault+92/188] [__alloc_pages+67/372] Dec 12 09:41:01 ishtar kernel: [] [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [_alloc_pages+22/24] [do_anonymous_page+239/268] [handle_mm_fault+92/188] [do_page_fault+383/1201] [do_page_fault+0/1201] [do_brk+280/536] Dec 12 09:41:01 ishtar kernel: [] [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [linvfs_ioctl+35/72] [huft_build+1458/1480] [huft_build+1458/1480] [sys_ioctl+685/746] [huft_build+1458/1480] [error_code+52/60] Dec 12 09:41:01 ishtar kernel: [] [] [] [] [] [] Dec 12 09:41:01 ishtar kernel: [system_call+51/56] [huft_build+1458/1480] Dec 12 09:41:01 ishtar kernel: [] [] Dec 12 09:41:01 ishtar kernel: Dec 12 09:41:01 ishtar kernel: Code: 0f 0b 65 00 ae 8c 33 c0 5b 5e 81 c4 00 01 00 00 c3 8d 76 00 ---------------------------------------------------------------------------------- Dec 12 00:28:13 ishtar kernel: xfs_inotobp: xfs_imap() returned an error 22 on sd(8,3). Returning error. Dec 12 00:28:13 ishtar kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on sd(8,3). Returning error. Dec 12 00:28:13 ishtar kernel: xfs_inactive: xfs_ifree() returned an error = 22 on sd(8,3) Dec 12 00:28:13 ishtar kernel: xfs_force_shutdown(sd(8,3),0x1) called from line 1906 of file xfs_vnodeops.c. Return address = 0xc01ef1f4 Dec 12 00:28:13 ishtar kernel: Fatal error on root filesystem Dec 12 00:28:13 ishtar kernel: kernel BUG at debug.c:101! Dec 12 00:28:13 ishtar kernel: invalid operand: 0000 Dec 12 00:28:13 ishtar kernel: CPU: 1 Dec 12 00:28:13 ishtar kernel: EIP: 0010:[cmn_err+100/120] Not tainted Dec 12 00:28:13 ishtar kernel: EIP: 0010:[] Not tainted Dec 12 00:28:13 ishtar kernel: EFLAGS: 00010246 Dec 12 00:28:13 ishtar kernel: eax: 0000001f ebx: da68da08 ecx: 00000001 edx: 00000001 Dec 12 00:28:13 ishtar kernel: esi: 00000000 edi: 00000000 ebp: 00000001 esp: da68da00 Dec 12 00:28:13 ishtar kernel: ds: 0018 es: 0018 ss: 0018 Dec 12 00:28:13 ishtar kernel: Process xfsdump (pid: 19577, stackpage=da68d000) Dec 12 00:28:13 ishtar kernel: Stack: f7d39c00 00000000 61746146 7265206c 20726f72 72206e6f 20746f6f 656c6966 Dec 12 00:28:13 ishtar kernel: 74737973 30006d65 666f2036 6c696620 66782065 6e765f73 6f65646f 632e7370 Dec 12 00:28:13 ishtar kernel: 5220202e 72757465 6461206e 73657264 203d2073 30637830 31666531 20003466 Dec 12 00:28:13 ishtar kernel: Call Trace: [xfs_inotobp+304/496] [xfs_trans_read_buf+677/748] [xfs_iunlink_remove+105/908] [xfs_iunlink_remove+630/908] [xfs_iunlink_remove+808/908] Dec 12 00:28:13 ishtar kernel: Call Trace: [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [xfs_do_force_shutdown+61/232] [xfs_do_force_shutdown+109/232] [xfs_inactive+968/1040] [vn_rele+53/132] [linvfs_clear_inode+19/36] [clear_inode+101/172] Dec 12 00:28:13 ishtar kernel: [] [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [iput+226/472] [xfs_iput+28/36] [xfs_bulkstat_one+1215/1240] [huft_build+1458/1480] [xfs_bulkstat_single+63/352] [huft_build+1458/1480] Dec 12 00:28:13 ishtar kernel: [] [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [xfs_ioctl+1425/5379] [_pagebuf_free_object+237/244] [pagebuf_rele+158/176] [xfs_bmbt_get_state+51/60] [reschedule_idle+98/616] [alloc_inode+48/300] Dec 12 00:28:13 ishtar kernel: [] [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [kill_fasync+45/58] [n_tty_receive_buf+4045/4168] [n_tty_receive_buf+4109/4168] [kill_fasync+45/58] [n_tty_receive_buf+4045/4168] [n_tty_receive_buf+4109/4168] Dec 12 00:28:13 ishtar kernel: [] [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [handle_mm_fault+92/188] [__alloc_pages+67/372] [_alloc_pages+22/24] [do_anonymous_page+239/268] [handle_mm_fault+92/188] [do_page_fault+383/1201] Dec 12 00:28:13 ishtar kernel: [] [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [do_page_fault+0/1201] [do_brk+280/536] [linvfs_ioctl+35/72] [huft_build+1458/1480] [huft_build+1458/1480] [sys_ioctl+685/746] Dec 12 00:28:13 ishtar kernel: [] [] [] [] [] [] Dec 12 00:28:13 ishtar kernel: [huft_build+1458/1480] [error_code+52/60] [system_call+51/56] [huft_build+1458/1480] Dec 12 00:28:13 ishtar kernel: [] [] [] [] Dec 12 00:28:13 ishtar kernel: Dec 12 00:28:13 ishtar kernel: Code: 0f 0b 65 00 ae 8c 33 c0 5b 5e 81 c4 00 01 00 00 c3 8d 76 00 From owner-linux-xfs@oss.sgi.com Thu Dec 12 12:30:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 12:30:46 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCKUguR015886 for ; Thu, 12 Dec 2002 12:30:43 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBCKdrkq018472 for ; Thu, 12 Dec 2002 14:39:53 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA06973 for ; Thu, 12 Dec 2002 14:34:22 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA65541 for ; Thu, 12 Dec 2002 14:34:21 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBD3mDi01340 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 22:48:13 -0500 Resent-Message-Id: <200212130348.gBD3mDi01340@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id LAA70045 for ; Thu, 12 Dec 2002 11:05:04 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBCH52Qb42169722 for ; Thu, 12 Dec 2002 09:05:02 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBCH37g7031257 for ; Thu, 12 Dec 2002 18:03:07 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBCH37TH031256 for hch@sgi.com; Thu, 12 Dec 2002 18:03:07 +0100 Date: Thu, 12 Dec 2002 18:03:07 +0100 From: Christoph Hellwig Message-Id: <200212121703.gBCH37TH031256@lab343.munich.sgi.com> Subject: TAKE - remove xfs_dm_send_create_event To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Thu, 12 Dec 2002 22:48:13 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2066 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Thu Dec 12 09:04:17 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:135038a linux/fs/xfs/xfs_vnodeops.c - 1.575 - call dm_send_send_create_event instead of xfs_dm_send_create_event linux/fs/xfs/xfs_dmapi.h - 1.33 linux/fs/xfs/xfs_dmapi.c - 1.88 - remove xfs_dm_send_create_event From owner-linux-xfs@oss.sgi.com Thu Dec 12 12:44:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 12:44:04 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBCKi2uR016622 for ; Thu, 12 Dec 2002 12:44:02 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBCKi2DN016621 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 12:44:02 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBCKi0uR016607 for ; Thu, 12 Dec 2002 12:44:00 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBCKTYWV015696; Thu, 12 Dec 2002 12:29:34 -0800 Date: Thu, 12 Dec 2002 12:29:34 -0800 Message-Id: <200212122029.gBCKTYWV015696@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2067 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-12 12:29 ------- Huh, the only time I can reproduce these file corruptions is when I'm running full desktop environment. In text mode or with just X and xterm I cannot reproduce this bug. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Thu Dec 12 15:27:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 15:27:36 -0800 (PST) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCNRYuR019269 for ; Thu, 12 Dec 2002 15:27:34 -0800 Received: from gateway-1237.mvista.com ([12.44.186.158] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (Exim 3.33 #1) id 18McnV-0002g1-00 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 15:31:17 -0800 Message-ID: <410-2200212412233115567@mindspring.com> X-Priority: Reply-To: blairbarnett@mindspring.com X-Mailer: EarthLink MailBox 2003.1.12.0 (Windows) From: "Blair Barnett" Cc: linux-xfs@oss.sgi.com Subject: GRIO support Date: Thu, 12 Dec 2002 15:31:15 -0800 MIME-Version: 1.0 Content-Type: text/html; charset=US-ASCII X-ELNK-Trace: 714d70eeb430e5e5a8c030553ce7b694f402879cecb40bd5ec181ad0463dccd7b3b2905513ff981ca77e91dfd1c243de350badd9bab72f9c350badd9bab72f9c X-archive-position: 2068 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: blairbarnett@mindspring.com Precedence: bulk X-list: linux-xfs

Is there any plan to support GRIO on Linux XFS? Video-on-demand could sure use this support. How difficult is it to port this code from IRIX?
 
Thanks,
 
Blair

From owner-linux-xfs@oss.sgi.com Thu Dec 12 15:45:30 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 15:45:34 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBCNjTuR019797 for ; Thu, 12 Dec 2002 15:45:29 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gBCLnEG8025984 for ; Thu, 12 Dec 2002 13:49:15 -0800 Received: from animal.melbourne.sgi.com (animal.melbourne.sgi.com [134.14.55.156]) by larry.melbourne.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id KAA03808; Fri, 13 Dec 2002 10:47:53 +1100 Received: (from ajag@localhost) by animal.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA37662; Fri, 13 Dec 2002 10:47:52 +1100 (AEDT) Date: Fri, 13 Dec 2002 10:47:52 +1100 From: Andrew Gildfind To: Blair Barnett Cc: linux-xfs@oss.sgi.com Subject: Re: GRIO support Message-ID: <20021213104752.B35876@animal.melbourne.sgi.com> References: <410-2200212412233115567@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <410-2200212412233115567@mindspring.com>; from blairbarnett@mindspring.com on Thu, Dec 12, 2002 at 03:31:15PM -0800 X-archive-position: 2069 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ajag@animal.melbourne.sgi.com Precedence: bulk X-list: linux-xfs > > Is there any plan to support GRIO on Linux XFS? Video-on-demand could sure > use this support. How difficult is it to port this code from IRIX? > > Blair > When setting up a guaranteed rate stream, the current GRIO implementation on IRIX uses detailed knowledge of every piece of hardware down the entire IO path. At this point it is tied to SGI hardware and would be difficult to port. There is no current plan to support it under linux. Andrew -- Andrew Gildfind - R&D Software Engineer - SGI Melbourne Australia email: ajag@sgi.com - work: +61.3.9834.8200 mobile: 0412.834.183 From owner-linux-xfs@oss.sgi.com Thu Dec 12 16:56:15 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 12 Dec 2002 16:56:21 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBD0uFuR021545 for ; Thu, 12 Dec 2002 16:56:15 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBCN01G8030221 for ; Thu, 12 Dec 2002 15:00:01 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id SAA14023 for ; Thu, 12 Dec 2002 18:59:55 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id SAA56651 for ; Thu, 12 Dec 2002 18:59:55 -0600 (CST) Received: from rose.americas.sgi.com (localhost [127.0.0.1]) by rose.americas.sgi.com (8.12.6/8.12.5) with ESMTP id gBD0xtB0002512 for ; Thu, 12 Dec 2002 18:59:55 -0600 Received: (from cattelan@localhost) by rose.americas.sgi.com (8.12.6/8.12.6/Submit) id gBD0xt8p002510 for linux-xfs@oss.sgi.com; Thu, 12 Dec 2002 18:59:55 -0600 Date: Thu, 12 Dec 2002 18:59:55 -0600 From: Rusell Cattelan Message-Id: <200212130059.gBD0xt8p002510@rose.americas.sgi.com> Subject: TAKE - first pass at xfs_copy X-archive-position: 2070 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@rose.americas.sgi.com Precedence: bulk X-list: linux-xfs Started messing with this the other night. I've tested this on a small FS dumping to a file and then mounting it back on a loop device, and everything seems to work. I have not tested multiple targets so I don't know if the thread code is working totally. There may be some endian conversion issues yet. Date: Thu Dec 12 16:59:14 PST 2002 Workarea: rose.americas.sgi.com:/misc/xfs2/XFS/x2.4-xfs-devel The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135102a cmd/xfsdump/copy/xfs_copy.c - 1.7 - Convert to us*sema to pthread* Endian convert the nessesary values cmd/xfsdump/copy/locks.h - 1.6 - Convert to us*sema to pthread* cmd/xfsdump/copy/locks.c - 1.5 - Convert to us*sema to pthread* cmd/xfsdump/copy/Makefile - 1.8 - Pull in lib pthread and libxfs headers From owner-linux-xfs@oss.sgi.com Fri Dec 13 09:58:54 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 09:59:01 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBDHwsuR004686 for ; Fri, 13 Dec 2002 09:58:54 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.3/Submit) id gBDHwsgX004685 for linux-xfs@oss.sgi.com; Fri, 13 Dec 2002 09:58:54 -0800 Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBDHwpuR004673 for ; Fri, 13 Dec 2002 09:58:52 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBDG2fG8008856 for ; Fri, 13 Dec 2002 08:02:41 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA61347; Fri, 13 Dec 2002 12:02:31 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA36611; Fri, 13 Dec 2002 12:02:31 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by rose.americas.sgi.com (8.12.6/8.12.5) with ESMTP id gBDI2aB0003670; Fri, 13 Dec 2002 12:02:37 -0600 Subject: [Bug 198 ] Re: Ok never mind that other patch From: Russell Cattelan To: Stephane Harnois In-Reply-To: <3DFA087D.9060506@videotron.ca> References: <1039564804.6424.5.camel@rose.americas.sgi.com> <3DFA087D.9060506@videotron.ca> Content-Type: text/plain Organization: Message-Id: <1039802554.1273.180.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) Date: 13 Dec 2002 12:02:36 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 2071 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs On Fri, 2002-12-13 at 10:19, Stephane Harnois wrote: > Ok, > > This fixes the corruption locally for out test case but "not" over > NFS. I've ran the corrupter over night without a failure but got > corruption over NFS the same as before. It was hard to find out on > which kernel this would apply but tuesday's CVS worked. The latest > CVS tree has part of the patch but not all of it. Steve gave me an early copy of what he eventually checked in so I could send it your way. But yes running TOT is effectively the same as the patch I sent. > > The difference between the test program and nfs is that nfsd uses > linvfs_open(inode, *fd) and the test program goes via libc from user > space. Hmm good good point. We think this is file size update issue and there might be a revalidation that needs to be done someplace that isn't currently being done. I was talking with Steve some more. When an file is closed the VOP_RELEASE path is called that cleans up EOF blocks, basically blocks allocated beyond the end of file. VOP_INACTIVE will get called when the dcache is flushed thus releasing it's reference count on the file. Since commenting the refcache purge some call out of they sync path there by preventing the release path from being called until the file is truly closed. I need to look through the code path a bit Note I think the reason corrruptor doesn't mess up with the latest path is because Steve extended these values -#define XFS_READIO_LOG_LARGE 12 > -#define XFS_WRITEIO_LOG_LARGE 12 > +#define XFS_READIO_LOG_LARGE 16 > +#define XFS_WRITEIO_LOG_LARGE 16 Try setting them back to 12 and see if the local problem comes back. Sorry I don't have more time to dig into this right now... got several other pressing issues for internal projects. Note: We will probably release 1.2 before this problem is fully resolved. Since it appears to be an old bug from at least 1.1 days we feel it a common enough problem to hold the release. 1.2.1 will have it :-) > > Russell Cattelan wrote: > > I won't appply to anything but the internal tree > > try this patch > > > > > > > > ____________________________________________________________________ > > > > =========================================================================== > > Index: linux/fs/xfs/linux/xfs_aops.c > > =========================================================================== > > > > --- /usr/tmp/TmpDir.21760-0/linux/fs/xfs/linux/xfs_aops.c_1.15 Tue Dec 10 17:48:43 2002 > > +++ linux/fs/xfs/linux/xfs_aops.c Tue Dec 10 17:25:38 2002 > > @@ -54,6 +54,9 @@ > > vnode_t *vp = LINVFS_GET_VP(inode); > > int error, nmaps = 1; > > > > + if (((flags & (PBF_DIRECT|PBF_SYNC)) == PBF_DIRECT) && > > + (offset >= inode->i_size)) > > + count = max(count, XFS_WRITE_IO_LOG); > > retry: > > VOP_BMAP(vp, offset, count, flags, pbmapp, &nmaps, error); > > if (flags & PBF_WRITE) { > > @@ -504,7 +507,7 @@ > > /* If we are doing writes at the end of the file, > > * allocate in chunks > > */ > > - if (create && (offset >= inode->i_size) && !(flags & PBF_SYNC)) > > + if (create && (offset >= inode->i_size) /* && !(flags & PBF_SYNC) */) > > size = 1 << XFS_WRITE_IO_LOG; > > else > > size = 1 << inode->i_blkbits; > > @@ -522,14 +525,19 @@ > > page_buf_daddr_t bn; > > loff_t delta; > > > > - delta = offset - pbmap.pbm_offset; > > - delta >>= inode->i_blkbits; > > + /* For unwritten extents do not report a disk address on > > + * the read case. > > + */ > > + if (create || ((pbmap.pbm_flags & PBMF_UNWRITTEN) == 0)) { > > + delta = offset - pbmap.pbm_offset; > > + delta >>= inode->i_blkbits; > > > > - bn = pbmap.pbm_bn >> (inode->i_blkbits - 9); > > - bn += delta; > > + bn = pbmap.pbm_bn >> (inode->i_blkbits - 9); > > + bn += delta; > > > > - bh_result->b_blocknr = bn; > > - set_bit(BH_Mapped, &bh_result->b_state); > > + bh_result->b_blocknr = bn; > > + set_bit(BH_Mapped, &bh_result->b_state); > > + } > > } > > > > /* If we previously allocated a block out beyond eof and > > > > =========================================================================== > > Index: linux/fs/xfs/linux/xfs_iomap.c > > =========================================================================== > > > > --- /usr/tmp/TmpDir.21760-0/linux/fs/xfs/linux/xfs_iomap.c_1.2 Tue Dec 10 17:48:43 2002 > > +++ linux/fs/xfs/linux/xfs_iomap.c Tue Dec 10 17:28:11 2002 > > @@ -30,361 +30,18 @@ > > * http://oss.sgi.com/projects/GenInfo/SGIGPLNoticeExplan/ > > */ > > /* > > - * fs/xfs/linux/xfs_lrw.c (Linux Read Write stuff) > > + * fs/xfs/linux/xfs_iomap.c (Linux Read Write stuff) > > * > > */ > > > > #include > > #include > > -#include > > > > > > #define XFS_WRITEIO_ALIGN(mp,off) (((off) >> mp->m_writeio_log) \ > > << mp->m_writeio_log) > > #define XFS_STRAT_WRITE_IMAPS 2 > > > > -STATIC int xfs_iomap_read(xfs_iocore_t *, loff_t, size_t, int, page_buf_bmap_t *, > > - int *); > > -STATIC int xfs_iomap_write(xfs_iocore_t *, loff_t, size_t, page_buf_bmap_t *, > > - int *, int); > > -STATIC int xfs_iomap_write_delay(xfs_iocore_t *, loff_t, size_t, page_buf_bmap_t *, > > - int *, int, int); > > -STATIC int xfs_iomap_write_direct(xfs_iocore_t *, loff_t, size_t, page_buf_bmap_t *, > > - int *, int, int); > > -STATIC int _xfs_imap_to_bmap(xfs_iocore_t *, xfs_off_t, xfs_bmbt_irec_t *, > > - page_buf_bmap_t *, int, int); > > - > > - > > -int > > -xfs_strategy( > > - xfs_inode_t *ip, > > - xfs_off_t offset, > > - ssize_t count, > > - int flags, > > - page_buf_bmap_t *pbmapp, > > - int *npbmaps) > > -{ > > - xfs_iocore_t *io; > > - xfs_mount_t *mp; > > - int error; > > - xfs_fileoff_t offset_fsb; > > - xfs_fileoff_t end_fsb; > > - xfs_fileoff_t map_start_fsb; > > - xfs_fileoff_t last_block; > > - xfs_fsblock_t first_block; > > - xfs_bmap_free_t free_list; > > - xfs_filblks_t count_fsb; > > - int committed, i, loops, nimaps; > > - int is_xfs; > > - xfs_bmbt_irec_t imap[XFS_MAX_RW_NBMAPS]; > > - xfs_trans_t *tp; > > - > > - mp = ip->i_mount; > > - io = &ip->i_iocore; > > - is_xfs = IO_IS_XFS(io); > > - ASSERT((ip->i_d.di_mode & IFMT) == IFREG); > > - ASSERT(((ip->i_d.di_flags & XFS_DIFLAG_REALTIME) != 0) == > > - ((io->io_flags & XFS_IOCORE_RT) != 0)); > > - > > - if (XFS_FORCED_SHUTDOWN(mp)) > > - return XFS_ERROR(EIO); > > - > > - offset_fsb = XFS_B_TO_FSBT(mp, offset); > > - nimaps = min(XFS_MAX_RW_NBMAPS, *npbmaps); > > - end_fsb = XFS_B_TO_FSB(mp, ((xfs_ufsize_t)(offset + count))); > > - first_block = NULLFSBLOCK; > > - > > - XFS_ILOCK(mp, io, XFS_ILOCK_SHARED | XFS_EXTSIZE_RD); > > - error = XFS_BMAPI(mp, NULL, io, offset_fsb, > > - (xfs_filblks_t)(end_fsb - offset_fsb), > > - XFS_BMAPI_ENTIRE, &first_block, 0, imap, > > - &nimaps, NULL); > > - XFS_IUNLOCK(mp, io, XFS_ILOCK_SHARED | XFS_EXTSIZE_RD); > > - if (error) { > > - return XFS_ERROR(error); > > - } > > - > > - if (nimaps && !ISNULLSTARTBLOCK(imap[0].br_startblock)) { > > - *npbmaps = _xfs_imap_to_bmap(&ip->i_iocore, offset, imap, > > - pbmapp, nimaps, *npbmaps); > > - return 0; > > - } > > - > > - /* > > - * Make sure that the dquots are there. > > - */ > > - > > - if (XFS_IS_QUOTA_ON(mp)) { > > - if (XFS_NOT_DQATTACHED(mp, ip)) { > > - if ((error = xfs_qm_dqattach(ip, 0))) { > > - return XFS_ERROR(error); > > - } > > - } > > - } > > - XFS_STATS_ADD(xfsstats.xs_xstrat_bytes, > > - XFS_FSB_TO_B(mp, imap[0].br_blockcount)); > > - > > - offset_fsb = imap[0].br_startoff; > > - count_fsb = imap[0].br_blockcount; > > - map_start_fsb = offset_fsb; > > - while (count_fsb != 0) { > > - /* > > - * Set up a transaction with which to allocate the > > - * backing store for the file. Do allocations in a > > - * loop until we get some space in the range we are > > - * interested in. The other space that might be allocated > > - * is in the delayed allocation extent on which we sit > > - * but before our buffer starts. > > - */ > > - nimaps = 0; > > - loops = 0; > > - while (nimaps == 0) { > > - if (is_xfs) { > > - tp = xfs_trans_alloc(mp, XFS_TRANS_STRAT_WRITE); > > - error = xfs_trans_reserve(tp, 0, > > - XFS_WRITE_LOG_RES(mp), > > - 0, XFS_TRANS_PERM_LOG_RES, > > - XFS_WRITE_LOG_COUNT); > > - if (error) { > > - xfs_trans_cancel(tp, 0); > > - goto error0; > > - } > > - xfs_ilock(ip, XFS_ILOCK_EXCL); > > - xfs_trans_ijoin(tp, ip, > > - XFS_ILOCK_EXCL); > > - xfs_trans_ihold(tp, ip); > > - } else { > > - tp = NULL; > > - XFS_ILOCK(mp, io, XFS_ILOCK_EXCL | > > - XFS_EXTSIZE_WR); > > - } > > - > > - > > - /* > > - * Allocate the backing store for the file. > > - */ > > - XFS_BMAP_INIT(&(free_list), > > - &(first_block)); > > - nimaps = XFS_STRAT_WRITE_IMAPS; > > - > > - /* > > - * Ensure we don't go beyond eof - it is possible > > - * the extents changed since we did the read call, > > - * we dropped the ilock in the interim. > > - */ > > - > > - end_fsb = XFS_B_TO_FSB(mp, XFS_SIZE(mp, io)); > > - xfs_bmap_last_offset(NULL, ip, &last_block, > > - XFS_DATA_FORK); > > - last_block = XFS_FILEOFF_MAX(last_block, end_fsb); > > - if ((map_start_fsb + count_fsb) > last_block) { > > - count_fsb = last_block - map_start_fsb; > > - if (count_fsb == 0) { > > - if (is_xfs) { > > - xfs_bmap_cancel(&free_list); > > - xfs_trans_cancel(tp, > > - (XFS_TRANS_RELEASE_LOG_RES | > > - XFS_TRANS_ABORT)); > > - } > > - XFS_IUNLOCK(mp, io, XFS_ILOCK_EXCL | > > - XFS_EXTSIZE_WR); > > - return XFS_ERROR(EAGAIN); > > - } > > - } > > - > > - error = XFS_BMAPI(mp, tp, io, map_start_fsb, count_fsb, > > - XFS_BMAPI_WRITE, &first_block, 1, > > - imap, &nimaps, &free_list); > > - if (error) { > > - xfs_bmap_cancel(&free_list); > > - xfs_trans_cancel(tp, > > - (XFS_TRANS_RELEASE_LOG_RES | > > - XFS_TRANS_ABORT)); > > - XFS_IUNLOCK(mp, io, XFS_ILOCK_EXCL | > > - XFS_EXTSIZE_WR); > > - > > - goto error0; > > - } > > - > > - if (is_xfs) { > > - error = xfs_bmap_finish(&(tp), &(free_list), > > - first_block, &committed); > > - if (error) { > > - xfs_bmap_cancel(&free_list); > > - xfs_trans_cancel(tp, > > - (XFS_TRANS_RELEASE_LOG_RES | > > - XFS_TRANS_ABORT)); > > - xfs_iunlock(ip, XFS_ILOCK_EXCL); > > - goto error0; > > - } > > - > > - error = xfs_trans_commit(tp, > > - XFS_TRANS_RELEASE_LOG_RES, > > - NULL); > > - if (error) { > > - xfs_iunlock(ip, XFS_ILOCK_EXCL); > > - goto error0; > > - } > > - } > > - > > - if (nimaps == 0) { > > - XFS_IUNLOCK(mp, io, > > - XFS_ILOCK_EXCL|XFS_EXTSIZE_WR); > > - } /* else hold 'till we maybe loop again below */ > > - } > > - > > - /* > > - * See if we were able to allocate an extent that > > - * covers at least part of the user's requested size. > > - */ > > - > > - offset_fsb = XFS_B_TO_FSBT(mp, offset); > > - for (i = 0; i < nimaps; i++) { > > - int maps; > > - > > - if ((offset_fsb >= imap[i].br_startoff) && > > - (offset_fsb < > > - (imap[i].br_startoff + imap[i].br_blockcount))) { > > - > > - XFS_IUNLOCK(mp, io, > > - XFS_ILOCK_EXCL|XFS_EXTSIZE_WR); > > - maps = min(nimaps, *npbmaps); > > - *npbmaps = _xfs_imap_to_bmap(io, offset, > > - &imap[i], pbmapp, > > - maps, *npbmaps); > > - XFS_STATS_INC(xfsstats.xs_xstrat_quick); > > - return 0; > > - } > > - count_fsb -= imap[i].br_blockcount; /* for next bmapi, > > - if needed. */ > > - } > > - > > - /* > > - * We didn't get an extent the caller can write into so > > - * loop around and try starting after the last imap we got back. > > - */ > > - > > - nimaps--; /* Index of last entry */ > > - ASSERT(nimaps >= 0); > > - ASSERT(offset_fsb >= > > - imap[nimaps].br_startoff + imap[nimaps].br_blockcount); > > - ASSERT(count_fsb); > > - offset_fsb = > > - imap[nimaps].br_startoff + imap[nimaps].br_blockcount; > > - map_start_fsb = offset_fsb; > > - XFS_STATS_INC(xfsstats.xs_xstrat_split); > > - XFS_IUNLOCK(mp, io, XFS_ILOCK_EXCL|XFS_EXTSIZE_WR); > > - } > > - > > - ASSERT(0); /* Should never get here */ > > - > > - error0: > > - if (error) { > > - ASSERT(count_fsb != 0); > > - ASSERT(is_xfs || XFS_FORCED_SHUTDOWN(mp)); > > - } > > - > > - return XFS_ERROR(error); > > -} > > - > > - > > -/* > > - * xfs_bmap() is the same as the irix xfs_bmap from xfs_rw.c > > - * execpt for slight changes to the params > > - */ > > -int > > -xfs_bmap(bhv_desc_t *bdp, > > - xfs_off_t offset, > > - ssize_t count, > > - int flags, > > - page_buf_bmap_t *pbmapp, > > - int *npbmaps) > > -{ > > - xfs_inode_t *ip; > > - int error; > > - int lockmode; > > - int fsynced = 0; > > - vnode_t *vp; > > - > > - ip = XFS_BHVTOI(bdp); > > - ASSERT((ip->i_d.di_mode & IFMT) == IFREG); > > - ASSERT(((ip->i_d.di_flags & XFS_DIFLAG_REALTIME) != 0) == > > - ((ip->i_iocore.io_flags & XFS_IOCORE_RT) != 0)); > > - > > - if (XFS_FORCED_SHUTDOWN(ip->i_iocore.io_mount)) > > - return XFS_ERROR(EIO); > > - > > - if (flags & PBF_READ) { > > - lockmode = xfs_ilock_map_shared(ip); > > - error = xfs_iomap_read(&ip->i_iocore, offset, count, > > - XFS_BMAPI_ENTIRE, pbmapp, npbmaps); > > - xfs_iunlock_map_shared(ip, lockmode); > > - } else if (flags & PBF_FILE_ALLOCATE) { > > - error = xfs_strategy(ip, offset, count, flags, > > - pbmapp, npbmaps); > > - } else { /* PBF_WRITE */ > > - ASSERT(flags & PBF_WRITE); > > - vp = BHV_TO_VNODE(bdp); > > - xfs_ilock(ip, XFS_ILOCK_EXCL); > > - > > - /* > > - * Make sure that the dquots are there. This doesn't hold > > - * the ilock across a disk read. > > - */ > > - > > - if (XFS_IS_QUOTA_ON(ip->i_mount)) { > > - if (XFS_NOT_DQATTACHED(ip->i_mount, ip)) { > > - if ((error = xfs_qm_dqattach(ip, XFS_QMOPT_ILOCKED))) { > > - xfs_iunlock(ip, XFS_ILOCK_EXCL); > > - return XFS_ERROR(error); > > - } > > - } > > - } > > -retry: > > - error = xfs_iomap_write(&ip->i_iocore, offset, count, > > - pbmapp, npbmaps, flags); > > - /* xfs_iomap_write unlocks/locks/unlocks */ > > - > > - if (error == ENOSPC) { > > - switch (fsynced) { > > - case 0: > > - if (ip->i_delayed_blks) { > > - fsync_inode_data_buffers(LINVFS_GET_IP(vp)); > > - fsynced = 1; > > - } else { > > - fsynced = 2; > > - flags |= PBF_SYNC; > > - } > > - error = 0; > > - xfs_ilock(ip, XFS_ILOCK_EXCL); > > - goto retry; > > - case 1: > > - fsynced = 2; > > - if (!(flags & PBF_SYNC)) { > > - flags |= PBF_SYNC; > > - error = 0; > > - xfs_ilock(ip, XFS_ILOCK_EXCL); > > - goto retry; > > - } > > - case 2: > > - fsync_no_super(LINVFS_GET_IP(vp)->i_dev); > > - xfs_log_force(ip->i_mount, (xfs_lsn_t)0, > > - XFS_LOG_FORCE|XFS_LOG_SYNC); > > - > > - error = 0; > > -/** > > - delay(HZ); > > -**/ > > - fsynced++; > > - xfs_ilock(ip, XFS_ILOCK_EXCL); > > - goto retry; > > - } > > - } > > - } > > - > > - return XFS_ERROR(error); > > -} > > - > > > > STATIC int > > _xfs_imap_to_bmap( > > @@ -397,7 +54,7 @@ > > { > > xfs_mount_t *mp; > > xfs_fsize_t nisize; > > - int im, pbm; > > + int pbm; > > xfs_fsblock_t start_block; > > > > mp = io->io_mount; > > @@ -405,7 +62,7 @@ > > if (io->io_new_size > nisize) > > nisize = io->io_new_size; > > > > - for (im=pbm=0; im < imaps && pbm < pbmaps; im++,pbmapp++,imap++,pbm++) { > > + for (pbm = 0; imaps && pbm < pbmaps; imaps--, pbmapp++, imap++, pbm++) { > > pbmapp->pbm_target = io->io_flags & XFS_IOCORE_RT ? > > mp->m_rtdev_targp : mp->m_ddev_targp; > > pbmapp->pbm_offset = XFS_FSB_TO_B(mp, imap->br_startoff); > > @@ -422,9 +79,8 @@ > > pbmapp->pbm_flags = PBMF_DELAY; > > } else { > > pbmapp->pbm_bn = XFS_FSB_TO_DB_IO(io, start_block); > > - if (ISUNWRITTEN(imap)) { > > + if (ISUNWRITTEN(imap)) > > pbmapp->pbm_flags |= PBMF_UNWRITTEN; > > - } > > } > > > > if ((pbmapp->pbm_offset + pbmapp->pbm_bsize) >= nisize) { > > @@ -436,149 +92,340 @@ > > return pbm; /* Return the number filled */ > > } > > > > -STATIC int > > -xfs_iomap_read( > > - xfs_iocore_t *io, > > - loff_t offset, > > - size_t count, > > +int > > +xfs_iomap(xfs_iocore_t *io, > > + xfs_off_t offset, > > + ssize_t count, > > int flags, > > page_buf_bmap_t *pbmapp, > > int *npbmaps) > > { > > - xfs_fileoff_t offset_fsb; > > - xfs_fileoff_t end_fsb; > > - int nimaps; > > + xfs_mount_t *mp = io->io_mount; > > + xfs_fileoff_t offset_fsb, end_fsb; > > int error; > > - xfs_mount_t *mp; > > - xfs_bmbt_irec_t imap[XFS_MAX_RW_NBMAPS]; > > + int lockmode = 0; > > + xfs_bmbt_irec_t imap; > > + int nimaps = 1; > > + int bmap_flags = 0; > > > > - ASSERT(ismrlocked(io->io_lock, MR_UPDATE | MR_ACCESS) != 0); > > + if (XFS_FORCED_SHUTDOWN(mp)) > > + return XFS_ERROR(EIO); > > + > > + switch (flags & (PBF_READ|PBF_WRITE|PBF_FILE_ALLOCATE)) { > > + case PBF_READ: > > + lockmode = XFS_LCK_MAP_SHARED(mp, io); > > + bmap_flags = XFS_BMAPI_ENTIRE; > > + break; > > + case PBF_WRITE: > > + lockmode = XFS_ILOCK_EXCL|XFS_EXTSIZE_WR; > > + bmap_flags = 0; > > + XFS_ILOCK(mp, io, lockmode); > > + break; > > + case PBF_FILE_ALLOCATE: > > + lockmode = XFS_ILOCK_SHARED|XFS_EXTSIZE_RD; > > + bmap_flags = XFS_BMAPI_ENTIRE; > > + XFS_ILOCK(mp, io, lockmode); > > + break; > > + default: > > + ASSERT(flags & (PBF_READ|PBF_WRITE|PBF_FILE_ALLOCATE)); > > + } > > > > - mp = io->io_mount; > > offset_fsb = XFS_B_TO_FSBT(mp, offset); > > - nimaps = sizeof(imap) / sizeof(imap[0]); > > - nimaps = min(nimaps, *npbmaps); /* Don't ask for more than caller has */ > > end_fsb = XFS_B_TO_FSB(mp, ((xfs_ufsize_t)(offset + count))); > > + > > error = XFS_BMAPI(mp, NULL, io, offset_fsb, > > - (xfs_filblks_t)(end_fsb - offset_fsb), > > - flags, NULL, 0, imap, > > - &nimaps, NULL); > > - if (error) { > > - return XFS_ERROR(error); > > + (xfs_filblks_t)(end_fsb - offset_fsb) , > > + bmap_flags, NULL, 0, &imap, > > + &nimaps, NULL); > > + > > + if (error) > > + goto out; > > + > > + switch (flags & (PBF_WRITE|PBF_FILE_ALLOCATE)) { > > + case PBF_WRITE: > > + /* If we found an extent, return it */ > > + if (nimaps && (imap.br_startblock != HOLESTARTBLOCK)) > > + break; > > + > > + if (flags & PBF_DIRECT) { > > + error = XFS_IOMAP_WRITE_DIRECT(mp, io, offset, > > + count, flags, &imap, &nimaps, nimaps); > > + } else { > > + error = XFS_IOMAP_WRITE_DELAY(mp, io, offset, count, > > + flags, &imap, &nimaps); > > + } > > + break; > > + case PBF_FILE_ALLOCATE: > > + /* If we found an extent, return it */ > > + XFS_IUNLOCK(mp, io, lockmode); > > + lockmode = 0; > > + > > + if (nimaps && !ISNULLSTARTBLOCK(imap.br_startblock)) > > + break; > > + > > + error = XFS_IOMAP_WRITE_ALLOCATE(mp, io, &imap, &nimaps); > > + break; > > } > > > > - if(nimaps) { > > - *npbmaps = _xfs_imap_to_bmap(io, offset, imap, pbmapp, nimaps, > > - *npbmaps); > > - } else > > + if (nimaps) { > > + *npbmaps = _xfs_imap_to_bmap(io, offset, &imap, > > + pbmapp, nimaps, *npbmaps); > > + } else { > > *npbmaps = 0; > > + } > > + > > +out: > > + if (lockmode) > > + XFS_IUNLOCK(mp, io, lockmode); > > return XFS_ERROR(error); > > } > > > > -/* > > - * xfs_iomap_write: return pagebuf_bmap_t's telling higher layers > > - * where to write. > > - * There are 2 main cases: > > - * 1 the extents already exist > > - * 2 must allocate. > > - * There are 3 cases when we allocate: > > - * delay allocation (doesn't really allocate or use transactions) > > - * direct allocation (no previous delay allocation) > > - * convert delay to real allocations > > - */ > > +static int > > +xfs_flush_space( > > + xfs_inode_t *ip, > > + int *fsynced, > > + int *ioflags) > > +{ > > + vnode_t *vp = XFS_ITOV(ip); > > > > -STATIC int > > -xfs_iomap_write( > > - xfs_iocore_t *io, > > + switch (*fsynced) { > > + case 0: > > + if (ip->i_delayed_blks) { > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + fsync_inode_data_buffers(LINVFS_GET_IP(vp)); > > + xfs_ilock(ip, XFS_ILOCK_EXCL); > > + *fsynced = 1; > > + } else { > > + *ioflags |= PBF_SYNC; > > + *fsynced = 2; > > + } > > + return 0; > > + case 1: > > + *fsynced = 2; > > + *ioflags |= PBF_SYNC; > > + return 0; > > + case 2: > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + fsync_no_super(LINVFS_GET_IP(vp)->i_dev); > > + xfs_log_force(ip->i_mount, (xfs_lsn_t)0, > > + XFS_LOG_FORCE|XFS_LOG_SYNC); > > + xfs_ilock(ip, XFS_ILOCK_EXCL); > > + *fsynced = 3; > > + return 0; > > + } > > + return 1; > > +} > > + > > +int > > +xfs_iomap_write_direct( > > + xfs_inode_t *ip, > > loff_t offset, > > size_t count, > > - page_buf_bmap_t *pbmapp, > > - int *npbmaps, > > - int ioflag) > > + int ioflag, > > + xfs_bmbt_irec_t *ret_imap, > > + int *nmaps, > > + int found) > > { > > - int maps; > > - int error = 0; > > - int found; > > - int flags = 0; > > + xfs_mount_t *mp = ip->i_mount; > > + xfs_iocore_t *io = &ip->i_iocore; > > + xfs_fileoff_t offset_fsb; > > + xfs_fileoff_t last_fsb; > > + xfs_filblks_t count_fsb; > > + xfs_fsize_t isize; > > + xfs_fsblock_t firstfsb; > > + int nimaps, maps; > > + int error; > > + int bmapi_flag; > > + int rt; > > + xfs_trans_t *tp; > > > > - maps = *npbmaps; > > - if (!maps) > > - goto out; > > +#define XFS_WRITE_IMAPS 2 > > + xfs_bmbt_irec_t imap[XFS_WRITE_IMAPS], *imapp; > > + xfs_bmap_free_t free_list; > > + int aeof; > > + xfs_filblks_t datablocks; > > + int committed; > > + int numrtextents; > > + uint resblks; > > + > > + /* > > + * Make sure that the dquots are there. This doesn't hold > > + * the ilock across a disk read. > > + */ > > + > > + if (XFS_IS_QUOTA_ON(mp) && XFS_NOT_DQATTACHED(mp, ip)) { > > + if ((error = xfs_qm_dqattach(ip, XFS_QMOPT_ILOCKED))) { > > + return XFS_ERROR(error); > > + } > > + } > > + maps = min(XFS_WRITE_IMAPS, *nmaps); > > + nimaps = maps; > > + > > + isize = ip->i_d.di_size; > > + aeof = (offset + count) > isize; > > + > > + if (io->io_new_size > isize) > > + isize = io->io_new_size; > > + > > + offset_fsb = XFS_B_TO_FSBT(mp, offset); > > + last_fsb = XFS_B_TO_FSB(mp, ((xfs_ufsize_t)(offset + count))); > > + count_fsb = last_fsb - offset_fsb; > > + if (found && (ret_imap->br_startblock == HOLESTARTBLOCK)) { > > + xfs_fileoff_t map_last_fsb; > > + > > + map_last_fsb = ret_imap->br_blockcount + ret_imap->br_startoff; > > + > > + if (map_last_fsb < last_fsb) { > > + last_fsb = map_last_fsb; > > + count_fsb = last_fsb - offset_fsb; > > + } > > + ASSERT(count_fsb > 0); > > + } > > > > /* > > - * If we have extents that are allocated for this range, > > - * return them. > > + * determine if reserving space on > > + * the data or realtime partition. > > */ > > + if ((rt = ip->i_d.di_flags & XFS_DIFLAG_REALTIME)) { > > + int sbrtextsize, iprtextsize; > > > > - found = 0; > > - error = xfs_iomap_read(io, offset, count, flags, pbmapp, npbmaps); > > + sbrtextsize = mp->m_sb.sb_rextsize; > > + iprtextsize = > > + ip->i_d.di_extsize ? ip->i_d.di_extsize : sbrtextsize; > > + numrtextents = (count_fsb + iprtextsize - 1); > > + do_div(numrtextents, sbrtextsize); > > + datablocks = 0; > > + } else { > > + datablocks = count_fsb; > > + numrtextents = 0; > > + } > > + > > + /* > > + * allocate and setup the transaction > > + */ > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + tp = xfs_trans_alloc(mp, XFS_TRANS_DIOSTRAT); > > + > > + resblks = XFS_DIOSTRAT_SPACE_RES(mp, datablocks); > > + > > + error = xfs_trans_reserve(tp, resblks, > > + XFS_WRITE_LOG_RES(mp), numrtextents, > > + XFS_TRANS_PERM_LOG_RES, > > + XFS_WRITE_LOG_COUNT); > > + > > + /* > > + * check for running out of space > > + */ > > if (error) > > - goto out; > > + /* > > + * Free the transaction structure. > > + */ > > + xfs_trans_cancel(tp, 0); > > + > > + xfs_ilock(ip, XFS_ILOCK_EXCL); > > + > > + if (error) > > + goto error_out; /* Don't return in above if .. trans .., > > + need lock to return */ > > + > > + if (XFS_IS_QUOTA_ON(mp)) { > > + if (xfs_trans_reserve_blkquota(tp, ip, resblks)) { > > + error = (EDQUOT); > > + goto error1; > > + } > > + } > > + nimaps = 1; > > + > > + bmapi_flag = XFS_BMAPI_WRITE; > > + xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL); > > + xfs_trans_ihold(tp, ip); > > + > > + if (offset < ip->i_d.di_size || rt) > > + bmapi_flag |= XFS_BMAPI_PREALLOC; > > > > /* > > - * If we found mappings and they can just have data written > > - * without conversion, > > - * let the caller write these and call us again. > > - * > > - * If we have a HOLE or UNWRITTEN, proceed down lower to > > - * get the space or to convert to written. > > + * issue the bmapi() call to allocate the blocks > > + */ > > + XFS_BMAP_INIT(&free_list, &firstfsb); > > + imapp = &imap[0]; > > + error = xfs_bmapi(tp, ip, offset_fsb, count_fsb, > > + bmapi_flag, &firstfsb, 0, imapp, &nimaps, &free_list); > > + if (error) { > > + goto error0; > > + } > > + > > + /* > > + * complete the transaction > > */ > > > > - if (*npbmaps) { > > - if (!(pbmapp->pbm_flags & PBMF_HOLE)) { > > - *npbmaps = 1; /* Only checked the first one. */ > > - /* We could check more, ... */ > > - goto out; > > - } > > + error = xfs_bmap_finish(&tp, &free_list, firstfsb, &committed); > > + if (error) { > > + goto error0; > > } > > - found = *npbmaps; > > - *npbmaps = maps; /* Restore to original requested */ > > > > - if (ioflag & PBF_DIRECT) { > > - error = xfs_iomap_write_direct(io, offset, count, pbmapp, > > - npbmaps, ioflag, found); > > - } else { > > - error = xfs_iomap_write_delay(io, offset, count, pbmapp, > > - npbmaps, ioflag, found); > > + error = xfs_trans_commit(tp, XFS_TRANS_RELEASE_LOG_RES, NULL); > > + if (error) { > > + goto error_out; > > } > > > > -out: > > - XFS_IUNLOCK(io->io_mount, io, XFS_ILOCK_EXCL); > > + /* copy any maps to caller's array and return any error. */ > > + if (nimaps == 0) { > > + error = (ENOSPC); > > + goto error_out; > > + } > > + > > + *ret_imap = imap[0]; > > + *nmaps = 1; > > + return 0; > > + > > + error0: /* Cancel bmap, unlock inode, and cancel trans */ > > + xfs_bmap_cancel(&free_list); > > + > > + error1: /* Just cancel transaction */ > > + xfs_trans_cancel(tp, XFS_TRANS_RELEASE_LOG_RES | XFS_TRANS_ABORT); > > + *nmaps = 0; /* nothing set-up here */ > > + > > +error_out: > > return XFS_ERROR(error); > > } > > > > -STATIC int > > +int > > xfs_iomap_write_delay( > > - xfs_iocore_t *io, > > + xfs_inode_t *ip, > > loff_t offset, > > size_t count, > > - page_buf_bmap_t *pbmapp, > > - int *npbmaps, > > int ioflag, > > - int found) > > + xfs_bmbt_irec_t *ret_imap, > > + int *nmaps) > > { > > + xfs_mount_t *mp = ip->i_mount; > > + xfs_iocore_t *io = &ip->i_iocore; > > xfs_fileoff_t offset_fsb; > > - xfs_fileoff_t ioalign; > > xfs_fileoff_t last_fsb; > > - xfs_fileoff_t start_fsb; > > - xfs_filblks_t count_fsb; > > - xfs_off_t aligned_offset; > > xfs_fsize_t isize; > > xfs_fsblock_t firstblock; > > int nimaps; > > int error; > > - int n; > > - unsigned int iosize; > > - xfs_mount_t *mp; > > #define XFS_WRITE_IMAPS XFS_BMAP_MAX_NMAP > > xfs_bmbt_irec_t imap[XFS_WRITE_IMAPS]; > > int aeof; > > + int fsynced = 0; > > > > - ASSERT(ismrlocked(io->io_lock, MR_UPDATE) != 0); > > + ASSERT(ismrlocked(&ip->i_lock, MR_UPDATE) != 0); > > > > - mp = io->io_mount; > > + /* > > + * Make sure that the dquots are there. This doesn't hold > > + * the ilock across a disk read. > > + */ > > > > - isize = XFS_SIZE(mp, io); > > + if (XFS_IS_QUOTA_ON(mp) && XFS_NOT_DQATTACHED(mp, ip)) { > > + if ((error = xfs_qm_dqattach(ip, XFS_QMOPT_ILOCKED))) { > > + return XFS_ERROR(error); > > + } > > + } > > + > > +retry: > > + isize = ip->i_d.di_size; > > if (io->io_new_size > isize) { > > isize = io->io_new_size; > > } > > @@ -591,50 +438,22 @@ > > * then extend the allocation (and the buffer used for the write) > > * out to the file system's write iosize. We clean up any extra > > * space left over when the file is closed in xfs_inactive(). > > - * We can only do this if we are sure that we will create buffers > > - * over all of the space we allocate beyond the end of the file. > > - * Not doing so would allow us to create delalloc blocks with > > - * no pages in memory covering them. So, we need to check that > > - * there are not any real blocks in the area beyond the end of > > - * the file which we are optimistically going to preallocate. If > > - * there are then our buffers will stop when they encounter them > > - * and we may accidentally create delalloc blocks beyond them > > - * that we never cover with a buffer. All of this is because > > - * we are not actually going to write the extra blocks preallocated > > - * at this point. > > * > > * We don't bother with this for sync writes, because we need > > * to minimize the amount we write for good performance. > > */ > > - if (!(ioflag & PBF_SYNC) && ((offset + count) > XFS_SIZE(mp, io))) { > > - start_fsb = XFS_B_TO_FSBT(mp, > > - ((xfs_ufsize_t)(offset + count - 1))); > > - count_fsb = mp->m_writeio_blocks; > > - while (count_fsb > 0) { > > - nimaps = XFS_WRITE_IMAPS; > > - error = XFS_BMAPI(mp, NULL, io, start_fsb, count_fsb, > > - 0, NULL, 0, imap, &nimaps, > > - NULL); > > - if (error) { > > - return error; > > - } > > - for (n = 0; n < nimaps; n++) { > > - if ((imap[n].br_startblock != HOLESTARTBLOCK) && > > - (imap[n].br_startblock != DELAYSTARTBLOCK)) { > > - goto write_map; > > - } > > - start_fsb += imap[n].br_blockcount; > > - count_fsb -= imap[n].br_blockcount; > > - ASSERT(count_fsb < 0xffff000); > > - } > > - } > > + if (!(ioflag & PBF_SYNC) && ((offset + count) > ip->i_d.di_size)) { > > + xfs_off_t aligned_offset; > > + unsigned int iosize; > > + xfs_fileoff_t ioalign; > > + > > iosize = mp->m_writeio_blocks; > > aligned_offset = XFS_WRITEIO_ALIGN(mp, (offset + count - 1)); > > ioalign = XFS_B_TO_FSBT(mp, aligned_offset); > > last_fsb = ioalign + iosize; > > aeof = 1; > > } > > - write_map: > > + > > nimaps = XFS_WRITE_IMAPS; > > firstblock = NULLFSBLOCK; > > > > @@ -642,11 +461,11 @@ > > * roundup the allocation request to m_dalign boundary if file size > > * is greater that 512K and we are allocating past the allocation eof > > */ > > - if (mp->m_dalign && (XFS_SIZE(mp, io) >= mp->m_dalign) && aeof) { > > + if (mp->m_dalign && (isize >= mp->m_dalign) && aeof) { > > int eof; > > xfs_fileoff_t new_last_fsb; > > new_last_fsb = roundup_64(last_fsb, mp->m_dalign); > > - error = XFS_BMAP_EOF(mp, io, new_last_fsb, XFS_DATA_FORK, &eof); > > + error = xfs_bmap_eof(ip, new_last_fsb, XFS_DATA_FORK, &eof); > > if (error) { > > return error; > > } > > @@ -655,7 +474,7 @@ > > } > > } > > > > - error = XFS_BMAPI(mp, NULL, io, offset_fsb, > > + error = xfs_bmapi(NULL, ip, offset_fsb, > > (xfs_filblks_t)(last_fsb - offset_fsb), > > XFS_BMAPI_DELAY | XFS_BMAPI_WRITE | > > XFS_BMAPI_ENTIRE, &firstblock, 1, imap, > > @@ -663,235 +482,257 @@ > > /* > > * This can be EDQUOT, if nimaps == 0 > > */ > > - if (error) { > > + if (error && (error != ENOSPC)) { > > return XFS_ERROR(error); > > } > > /* > > * If bmapi returned us nothing, and if we didn't get back EDQUOT, > > * then we must have run out of space. > > */ > > + > > if (nimaps == 0) { > > - return XFS_ERROR(ENOSPC); > > + if (xfs_flush_space(ip, &fsynced, &ioflag)) > > + return XFS_ERROR(ENOSPC); > > + > > + error = 0; > > + goto retry; > > } > > > > - /* > > - * Now map our desired I/O size and alignment over the > > - * extents returned by xfs_bmapi(). > > - */ > > - *npbmaps = _xfs_imap_to_bmap(io, offset, imap, pbmapp, > > - nimaps, *npbmaps); > > + *ret_imap = imap[0]; > > + *nmaps = 1; > > return 0; > > } > > > > -STATIC int > > -xfs_iomap_write_direct( > > - xfs_iocore_t *io, > > - loff_t offset, > > - size_t count, > > - page_buf_bmap_t *pbmapp, > > - int *npbmaps, > > - int ioflag, > > - int found) > > + > > +/* > > + * Pass in a delayed allocate extent, convert it to real extents > > + * return the to the caller the extent we create which maps on > > + * top of the originating callers request. > > + * > > + * Called without a lock on the inode. > > + */ > > +int > > +xfs_iomap_write_allocate( > > + xfs_inode_t *ip, > > + xfs_bmbt_irec_t *map, > > + int *retmap) > > { > > - xfs_inode_t *ip = XFS_IO_INODE(io); > > - xfs_mount_t *mp; > > - xfs_fileoff_t offset_fsb; > > - xfs_fileoff_t last_fsb; > > + xfs_mount_t *mp = ip->i_mount; > > + xfs_fileoff_t offset_fsb, last_block; > > + xfs_fileoff_t end_fsb, map_start_fsb; > > + xfs_fsblock_t first_block; > > + xfs_bmap_free_t free_list; > > xfs_filblks_t count_fsb; > > - xfs_fsize_t isize; > > - xfs_fsblock_t firstfsb; > > - int nimaps, maps; > > - int error; > > + xfs_bmbt_irec_t imap[XFS_STRAT_WRITE_IMAPS]; > > xfs_trans_t *tp; > > + int i, nimaps, committed; > > + int error = 0; > > > > -#define XFS_WRITE_IMAPS XFS_BMAP_MAX_NMAP > > - xfs_bmbt_irec_t imap[XFS_WRITE_IMAPS], *imapp; > > - xfs_bmap_free_t free_list; > > - int aeof; > > - int bmapi_flags; > > - xfs_filblks_t datablocks; > > - int rt; > > - int committed; > > - int numrtextents; > > - uint resblks; > > - int rtextsize; > > + *retmap = 0; > > > > - maps = min(XFS_WRITE_IMAPS, *npbmaps); > > - nimaps = maps; > > + /* > > + * Make sure that the dquots are there. > > + */ > > > > - mp = io->io_mount; > > - isize = XFS_SIZE(mp, io); > > - if (io->io_new_size > isize) > > - isize = io->io_new_size; > > + if (XFS_IS_QUOTA_ON(mp) && XFS_NOT_DQATTACHED(mp, ip)) { > > + if ((error = xfs_qm_dqattach(ip, 0))) { > > + return XFS_ERROR(error); > > + } > > + } > > > > - aeof = ((offset + count) > isize) ? 1 : 0; > > + offset_fsb = map->br_startoff; > > + count_fsb = map->br_blockcount; > > + map_start_fsb = offset_fsb; > > > > - offset_fsb = XFS_B_TO_FSBT(mp, offset); > > - last_fsb = XFS_B_TO_FSB(mp, ((xfs_ufsize_t)(offset + count))); > > - count_fsb = last_fsb - offset_fsb; > > - if (found && (pbmapp->pbm_flags & PBMF_HOLE)) { > > - xfs_fileoff_t map_last_fsb; > > + XFS_STATS_ADD(xfsstats.xs_xstrat_bytes, XFS_FSB_TO_B(mp, count_fsb)); > > > > - map_last_fsb = XFS_B_TO_FSB(mp, > > - (pbmapp->pbm_bsize + pbmapp->pbm_offset)); > > + while (count_fsb != 0) { > > + /* > > + * Set up a transaction with which to allocate the > > + * backing store for the file. Do allocations in a > > + * loop until we get some space in the range we are > > + * interested in. The other space that might be allocated > > + * is in the delayed allocation extent on which we sit > > + * but before our buffer starts. > > + */ > > > > - if (map_last_fsb < last_fsb) { > > - last_fsb = map_last_fsb; > > - count_fsb = last_fsb - offset_fsb; > > - } > > - ASSERT(count_fsb > 0); > > - } > > + nimaps = 0; > > + while (nimaps == 0) { > > + tp = xfs_trans_alloc(mp, XFS_TRANS_STRAT_WRITE); > > + error = xfs_trans_reserve(tp, 0, XFS_WRITE_LOG_RES(mp), > > + 0, XFS_TRANS_PERM_LOG_RES, > > + XFS_WRITE_LOG_COUNT); > > + if (error) { > > + xfs_trans_cancel(tp, 0); > > + return XFS_ERROR(error); > > + } > > + xfs_ilock(ip, XFS_ILOCK_EXCL); > > + xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL); > > + xfs_trans_ihold(tp, ip); > > > > - /* > > - * roundup the allocation request to m_dalign boundary if file size > > - * is greater that 512K and we are allocating past the allocation eof > > - */ > > - if (!found && mp->m_dalign && (isize >= 524288) && aeof) { > > - int eof; > > - xfs_fileoff_t new_last_fsb; > > + XFS_BMAP_INIT(&free_list, &first_block); > > > > - new_last_fsb = roundup_64(last_fsb, mp->m_dalign); > > - printk("xfs_iomap_write_direct: about to XFS_BMAP_EOF %Ld\n", > > - new_last_fsb); > > - error = XFS_BMAP_EOF(mp, io, new_last_fsb, XFS_DATA_FORK, &eof); > > - if (error) > > - goto error_out; > > - if (eof) > > - last_fsb = new_last_fsb; > > - } > > + nimaps = XFS_STRAT_WRITE_IMAPS; > > + /* > > + * Ensure we don't go beyond eof - it is possible > > + * the extents changed since we did the read call, > > + * we dropped the ilock in the interim. > > + */ > > > > - bmapi_flags = XFS_BMAPI_WRITE|XFS_BMAPI_DIRECT_IO|XFS_BMAPI_ENTIRE; > > - bmapi_flags &= ~XFS_BMAPI_DIRECT_IO; > > + end_fsb = XFS_B_TO_FSB(mp, ip->i_d.di_size); > > + xfs_bmap_last_offset(NULL, ip, &last_block, > > + XFS_DATA_FORK); > > + last_block = XFS_FILEOFF_MAX(last_block, end_fsb); > > + if ((map_start_fsb + count_fsb) > last_block) { > > + count_fsb = last_block - map_start_fsb; > > + if (count_fsb == 0) { > > + error = EAGAIN; > > + goto trans_cancel; > > + } > > + } > > > > - /* > > - * determine if this is a realtime file > > - */ > > - if ((rt = (ip->i_d.di_flags & XFS_DIFLAG_REALTIME)) != 0) { > > - rtextsize = mp->m_sb.sb_rextsize; > > - } else > > - rtextsize = 0; > > + /* Go get the actual blocks */ > > + error = xfs_bmapi(tp, ip, map_start_fsb, count_fsb, > > + XFS_BMAPI_WRITE, &first_block, 1, > > + imap, &nimaps, &free_list); > > > > - error = 0; > > + if (error) > > + goto trans_cancel; > > > > - /* > > - * allocate file space for the bmapp entries passed in. > > - */ > > + error = xfs_bmap_finish(&tp, &free_list, > > + first_block, &committed); > > > > - /* > > - * determine if reserving space on > > - * the data or realtime partition. > > - */ > > - if (rt) { > > - numrtextents = (count_fsb + rtextsize - 1); > > - do_div(numrtextents, rtextsize); > > - datablocks = 0; > > - } else { > > - datablocks = count_fsb; > > - numrtextents = 0; > > - } > > + if (error) > > + goto trans_cancel; > > > > - /* > > - * allocate and setup the transaction > > - */ > > - tp = xfs_trans_alloc(mp, XFS_TRANS_DIOSTRAT); > > - resblks = XFS_DIOSTRAT_SPACE_RES(mp, datablocks); > > + error = xfs_trans_commit(tp, > > + XFS_TRANS_RELEASE_LOG_RES, NULL); > > > > - xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + if (error) > > + goto error0; > > > > - error = xfs_trans_reserve(tp, > > - resblks, > > - XFS_WRITE_LOG_RES(mp), > > - numrtextents, > > - XFS_TRANS_PERM_LOG_RES, > > - XFS_WRITE_LOG_COUNT); > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + } > > > > - /* > > - * check for running out of space > > - */ > > - if (error) { > > /* > > - * Free the transaction structure. > > + * See if we were able to allocate an extent that > > + * covers at least part of the callers request > > */ > > - xfs_trans_cancel(tp, 0); > > - } > > > > - xfs_ilock(ip, XFS_ILOCK_EXCL); > > + for (i = 0; i < nimaps; i++) { > > + if ((map->br_startoff >= imap[i].br_startoff) && > > + (map->br_startoff < (imap[i].br_startoff + > > + imap[i].br_blockcount))) { > > + *map = imap[i]; > > + *retmap = 1; > > + XFS_STATS_INC(xfsstats.xs_xstrat_quick); > > + return 0; > > + } > > + count_fsb -= imap[i].br_blockcount; > > + } > > > > - if (error) { > > - goto error_out; /* Don't return in above if .. trans .., > > - need lock to return */ > > + /* So far we have not mapped the requested part of the > > + * file, just surrounding data, try again. > > + */ > > + nimaps--; > > + offset_fsb = imap[nimaps].br_startoff + > > + imap[nimaps].br_blockcount; > > + map_start_fsb = offset_fsb; > > } > > > > - if (XFS_IS_QUOTA_ON(mp)) { > > - if (xfs_trans_reserve_quota(tp, > > - ip->i_udquot, > > - ip->i_gdquot, > > - resblks, 0, 0)) { > > - error = (EDQUOT); > > - goto error1; > > - } > > - nimaps = 1; > > - } else { > > - nimaps = 2; > > - } > > +trans_cancel: > > + xfs_bmap_cancel(&free_list); > > + xfs_trans_cancel(tp, XFS_TRANS_RELEASE_LOG_RES | XFS_TRANS_ABORT); > > +error0: > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + return XFS_ERROR(error); > > +} > > > > - xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL); > > - xfs_trans_ihold(tp, ip); > > +int > > +xfs_iomap_write_unwritten( > > + xfs_inode_t *ip, > > + loff_t offset, > > + size_t count) > > +{ > > + xfs_mount_t *mp = ip->i_mount; > > + xfs_trans_t *tp; > > + xfs_fileoff_t offset_fsb; > > + xfs_filblks_t count_fsb; > > + xfs_filblks_t numblks_fsb; > > + xfs_bmbt_irec_t imap; > > + int committed; > > + int error; > > + int nres; > > + int nimaps; > > + xfs_fsblock_t firstfsb; > > + xfs_bmap_free_t free_list; > > > > - /* > > - * issue the bmapi() call to allocate the blocks > > - */ > > - XFS_BMAP_INIT(&free_list, &firstfsb); > > - imapp = &imap[0]; > > - error = XFS_BMAPI(mp, tp, io, offset_fsb, count_fsb, > > - bmapi_flags, &firstfsb, 1, imapp, &nimaps, &free_list); > > - if (error) { > > - goto error0; > > - } > > + offset_fsb = XFS_B_TO_FSBT(mp, offset); > > + count_fsb = XFS_B_TO_FSB(mp, count); > > > > - /* > > - * complete the transaction > > - */ > > + do { > > + nres = XFS_DIOSTRAT_SPACE_RES(mp, 0); > > > > - error = xfs_bmap_finish(&tp, &free_list, firstfsb, &committed); > > - if (error) { > > - goto error0; > > - } > > + /* > > + * set up a transaction to convert the range of extents > > + * from unwritten to real. Do allocations in a loop until > > + * we have covered the range passed in. > > + */ > > > > - error = xfs_trans_commit(tp, XFS_TRANS_RELEASE_LOG_RES, NULL); > > - if (error) { > > - goto error_out; > > - } > > + tp = xfs_trans_alloc(mp, XFS_TRANS_STRAT_WRITE); > > + error = xfs_trans_reserve(tp, nres, > > + XFS_WRITE_LOG_RES(mp), 0, > > + XFS_TRANS_PERM_LOG_RES, > > + XFS_WRITE_LOG_COUNT); > > + if (error) { > > + xfs_trans_cancel(tp, 0); > > + goto error0; > > + } > > > > - /* copy any maps to caller's array and return any error. */ > > - if (nimaps == 0) { > > - error = (ENOSPC); > > - goto error_out; > > - } > > + xfs_ilock(ip, XFS_ILOCK_EXCL); > > + xfs_trans_ijoin(tp, ip, XFS_ILOCK_EXCL); > > + xfs_trans_ihold(tp, ip); > > > > - maps = min(nimaps, maps); > > - *npbmaps = _xfs_imap_to_bmap(io, offset, &imap[0], pbmapp, maps, > > - *npbmaps); > > - if (*npbmaps) { > > /* > > - * this is new since xfs_iomap_read > > - * didn't find it. > > + * Modify the unwritten extent state of the buffer. > > */ > > - if (*npbmaps != 1) { > > - /* NEED MORE WORK FOR MULTIPLE BMAPS (which are new) */ > > - BUG(); > > - } > > - } > > - goto out; > > + XFS_BMAP_INIT(&free_list, &firstfsb); > > + nimaps = 1; > > + error = xfs_bmapi(tp, ip, offset_fsb, count_fsb, > > + XFS_BMAPI_WRITE, &firstfsb, > > + 1, &imap, &nimaps, &free_list); > > + if (error) > > + goto error_on_bmapi_transaction; > > > > - error0: /* Cancel bmap, unlock inode, and cancel trans */ > > - xfs_bmap_cancel(&free_list); > > + error = xfs_bmap_finish(&(tp), &(free_list), > > + firstfsb, &committed); > > + if (error) > > + goto error_on_bmapi_transaction; > > > > - error1: /* Just cancel transaction */ > > - xfs_trans_cancel(tp, XFS_TRANS_RELEASE_LOG_RES | XFS_TRANS_ABORT); > > - *npbmaps = 0; /* nothing set-up here */ > > + error = xfs_trans_commit(tp, XFS_TRANS_RELEASE_LOG_RES, NULL); > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > + if (error) > > + goto error0; > > > > -error_out: > > -out: /* Just return error and any tracing at end of routine */ > > + if ((numblks_fsb = imap.br_blockcount) == 0) { > > + /* > > + * The extent size should alway get bigger > > + * otherwise the loop is stuck. > > + */ > > + ASSERT(imap.br_blockcount); > > + break; > > + } > > + offset_fsb += numblks_fsb; > > + count_fsb -= numblks_fsb; > > + } while (count_fsb > 0); > > + > > + return 0; > > + > > +error_on_bmapi_transaction: > > + xfs_bmap_cancel(&free_list); > > + xfs_trans_cancel(tp, (XFS_TRANS_RELEASE_LOG_RES | XFS_TRANS_ABORT)); > > + xfs_iunlock(ip, XFS_ILOCK_EXCL); > > +error0: > > return XFS_ERROR(error); > > } > > + > > > > =========================================================================== > > Index: linux/fs/xfs/linux/xfs_lrw.c > > =========================================================================== > > > > --- /usr/tmp/TmpDir.21760-0/linux/fs/xfs/linux/xfs_lrw.c_1.176 Tue Dec 10 17:48:43 2002 > > +++ linux/fs/xfs/linux/xfs_lrw.c Tue Dec 10 17:25:38 2002 > > @@ -709,6 +709,25 @@ > > } > > } > > > > + > > +int > > +xfs_bmap(bhv_desc_t *bdp, > > + xfs_off_t offset, > > + ssize_t count, > > + int flags, > > + page_buf_bmap_t *pbmapp, > > + int *npbmaps) > > +{ > > + xfs_inode_t *ip = XFS_BHVTOI(bdp); > > + xfs_iocore_t *io = &ip->i_iocore; > > + > > + ASSERT((ip->i_d.di_mode & IFMT) == IFREG); > > + ASSERT(((ip->i_d.di_flags & XFS_DIFLAG_REALTIME) != 0) == > > + ((ip->i_iocore.io_flags & XFS_IOCORE_RT) != 0)); > > + > > + return xfs_iomap(io, offset, count, flags, pbmapp, npbmaps); > > +} > > + > > /* > > * Wrapper around bdstrat so that we can stop data > > * from going to disk in case we are shutting down the filesystem. > > > > =========================================================================== > > Index: linux/fs/xfs/linux/xfs_lrw.h > > =========================================================================== > > > > --- /usr/tmp/TmpDir.21760-0/linux/fs/xfs/linux/xfs_lrw.h_1.30 Tue Dec 10 17:48:43 2002 > > +++ linux/fs/xfs/linux/xfs_lrw.h Tue Dec 10 17:25:38 2002 > > @@ -36,6 +36,8 @@ > > struct bhv_desc; > > struct xfs_mount; > > struct xfs_iocore; > > +struct xfs_inode; > > +struct xfs_bmbt_irec; > > struct page_buf_s; > > struct page_buf_bmap_s; > > > > @@ -57,6 +59,16 @@ > > extern ssize_t xfs_write (struct bhv_desc *, struct file *, const char *, > > size_t, loff_t *, struct cred *); > > > > +extern int xfs_iomap (struct xfs_iocore *, xfs_off_t, ssize_t, int, > > + struct page_buf_bmap_s *, int *); > > +extern int xfs_iomap_write_direct (struct xfs_inode *, loff_t, size_t, > > + int, struct xfs_bmbt_irec *, int *, int); > > +extern int xfs_iomap_write_delay (struct xfs_inode *, loff_t, size_t, > > + int, struct xfs_bmbt_irec *, int *); > > +extern int xfs_iomap_write_allocate (struct xfs_inode *, > > + struct xfs_bmbt_irec *, int *); > > +extern int xfs_iomap_write_unwritten (struct xfs_inode *, loff_t, size_t); > > + > > extern int xfs_dev_is_read_only (struct xfs_mount *, char *); > > > > extern void XFS_log_write_unmount_ro (struct bhv_desc *); > > > > =========================================================================== > > Index: linux/fs/xfs/xfs_iocore.c > > =========================================================================== > > > > --- /usr/tmp/TmpDir.21760-0/linux/fs/xfs/xfs_iocore.c_1.36 Tue Dec 10 17:48:43 2002 > > +++ linux/fs/xfs/xfs_iocore.c Tue Dec 10 17:25:38 2002 > > @@ -43,12 +43,20 @@ > > xfs_ioops_t xfs_iocore_xfs = { > > .xfs_bmapi_func = (xfs_bmapi_t) xfs_bmapi, > > .xfs_bmap_eof_func = (xfs_bmap_eof_t) xfs_bmap_eof, > > + .xfs_iomap_write_direct = > > + (xfs_iomap_write_direct_t) xfs_iomap_write_direct, > > + .xfs_iomap_write_delay = > > + (xfs_iomap_write_delay_t) xfs_iomap_write_delay, > > + .xfs_iomap_write_allocate = > > + (xfs_iomap_write_allocate_t) xfs_iomap_write_allocate, > > + .xfs_iomap_write_unwritten = > > + (xfs_iomap_write_unwritten_t) xfs_iomap_write_unwritten, > > .xfs_ilock = (xfs_lock_t) xfs_ilock, > > + .xfs_lck_map_shared = (xfs_lck_map_shared_t) xfs_ilock_map_shared, > > .xfs_ilock_demote = (xfs_lock_demote_t) xfs_ilock_demote, > > .xfs_ilock_nowait = (xfs_lock_nowait_t) xfs_ilock_nowait, > > .xfs_unlock = (xfs_unlk_t) xfs_iunlock, > > .xfs_size_func = (xfs_size_t) xfs_size_fn, > > - .xfs_lastbyte = (xfs_lastbyte_t) xfs_file_last_byte, > > }; > > > > void > > > > =========================================================================== > > Index: linux/fs/xfs/xfs_mount.h > > =========================================================================== > > > > --- /usr/tmp/TmpDir.21760-0/linux/fs/xfs/xfs_mount.h_1.164 Tue Dec 10 17:48:43 2002 > > +++ linux/fs/xfs/xfs_mount.h Tue Dec 10 17:41:55 2002 > > @@ -101,24 +101,37 @@ > > struct xfs_bmbt_irec *, int *, > > struct xfs_bmap_free *); > > typedef int (*xfs_bmap_eof_t)(void *, xfs_fileoff_t, int, int *); > > +typedef int (*xfs_iomap_write_direct_t)( > > + void *, loff_t, size_t, int, > > + struct xfs_bmbt_irec *, int *, int); > > +typedef int (*xfs_iomap_write_delay_t)( > > + void *, loff_t, size_t, int, > > + struct xfs_bmbt_irec *, int *); > > +typedef int (*xfs_iomap_write_allocate_t)( > > + void *, struct xfs_bmbt_irec *, int *); > > +typedef int (*xfs_iomap_write_unwritten_t)( > > + void *, loff_t, size_t); > > +typedef int (*xfs_lck_map_shared_t)(void *); > > typedef void (*xfs_lock_t)(void *, uint); > > typedef void (*xfs_lock_demote_t)(void *, uint); > > typedef int (*xfs_lock_nowait_t)(void *, uint); > > typedef void (*xfs_unlk_t)(void *, unsigned int); > > -typedef void (*xfs_chgtime_t)(void *, int); > > typedef xfs_fsize_t (*xfs_size_t)(void *); > > typedef xfs_fsize_t (*xfs_lastbyte_t)(void *); > > > > typedef struct xfs_ioops { > > - xfs_bmapi_t xfs_bmapi_func; > > - xfs_bmap_eof_t xfs_bmap_eof_func; > > - xfs_lock_t xfs_ilock; > > - xfs_lock_demote_t xfs_ilock_demote; > > - xfs_lock_nowait_t xfs_ilock_nowait; > > - xfs_unlk_t xfs_unlock; > > - xfs_chgtime_t xfs_chgtime; > > - xfs_size_t xfs_size_func; > > - xfs_lastbyte_t xfs_lastbyte; > > + xfs_bmapi_t xfs_bmapi_func; > > + xfs_bmap_eof_t xfs_bmap_eof_func; > > + xfs_iomap_write_direct_t xfs_iomap_write_direct; > > + xfs_iomap_write_delay_t xfs_iomap_write_delay; > > + xfs_iomap_write_allocate_t xfs_iomap_write_allocate; > > + xfs_iomap_write_unwritten_t xfs_iomap_write_unwritten; > > + xfs_lock_t xfs_ilock; > > + xfs_lck_map_shared_t xfs_lck_map_shared; > > + xfs_lock_demote_t xfs_ilock_demote; > > + xfs_lock_nowait_t xfs_ilock_nowait; > > + xfs_unlk_t xfs_unlock; > > + xfs_size_t xfs_size_func; > > } xfs_ioops_t; > > > > > > @@ -130,9 +143,31 @@ > > (*(mp)->m_io_ops.xfs_bmap_eof_func) \ > > ((io)->io_obj, endoff, whichfork, eof) > > > > +#define XFS_IOMAP_WRITE_DIRECT(mp, io, offset, count, flags, mval, nmap, found)\ > > + (*(mp)->m_io_ops.xfs_iomap_write_direct) \ > > + ((io)->io_obj, offset, count, flags, mval, nmap, found) > > + > > +#define XFS_IOMAP_WRITE_DELAY(mp, io, offset, count, flags, mval, nmap) \ > > + (*(mp)->m_io_ops.xfs_iomap_write_delay) \ > > + ((io)->io_obj, offset, count, flags, mval, nmap) > > + > > +#define XFS_IOMAP_WRITE_ALLOCATE(mp, io, mval, nmap) \ > > + (*(mp)->m_io_ops.xfs_iomap_write_allocate) \ > > + ((io)->io_obj, mval, nmap) > > + > > +#define XFS_IOMAP_WRITE_UNWRITTEN(mp, io, offset, count) \ > > + (*(mp)->m_io_ops.xfs_iomap_write_unwritten) \ > > + ((io)->io_obj, offset, count) > > + > > +#define XFS_LCK_MAP_SHARED(mp, io) \ > > + (*(mp)->m_io_ops.xfs_lck_map_shared)((io)->io_obj) > > + > > #define XFS_ILOCK(mp, io, mode) \ > > (*(mp)->m_io_ops.xfs_ilock)((io)->io_obj, mode) > > > > +#define XFS_ILOCK_NOWAIT(mp, io, mode) \ > > + (*(mp)->m_io_ops.xfs_ilock)((io)->io_obj, mode) > > + > > #define XFS_IUNLOCK(mp, io, mode) \ > > (*(mp)->m_io_ops.xfs_unlock)((io)->io_obj, mode) > > > > @@ -142,8 +177,6 @@ > > #define XFS_SIZE(mp, io) \ > > (*(mp)->m_io_ops.xfs_size_func)((io)->io_obj) > > > > -#define XFS_LASTBYTE(mp, io) \ > > - (*(mp)->m_io_ops.xfs_lastbyte)((io)->io_obj) > > > > > > typedef struct xfs_mount { > > @@ -305,8 +338,8 @@ > > /* > > * Default minimum read and write sizes. > > */ > > -#define XFS_READIO_LOG_LARGE 12 > > -#define XFS_WRITEIO_LOG_LARGE 12 > > +#define XFS_READIO_LOG_LARGE 16 > > +#define XFS_WRITEIO_LOG_LARGE 16 > > /* > > * Default allocation size > > */ > > -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Fri Dec 13 11:55:14 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 11:55:16 -0800 (PST) Received: from packet.digeo.com (packet.digeo.com [12.110.80.53]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBDJtDuR006537 for ; Fri, 13 Dec 2002 11:55:13 -0800 Received: from digeo-nav01.digeo.com (digeo-nav01.digeo.com [192.168.1.233]) by packet.digeo.com (8.9.3+Sun/8.9.3) with SMTP id LAA27497 for ; Fri, 13 Dec 2002 11:58:56 -0800 (PST) Received: from digeo-e2k04.digeo.com ([192.168.2.24]) by digeo-nav01.digeo.com (NAVGW 2.5.2.12) with SMTP id M2002121312005018495 ; Fri, 13 Dec 2002 12:00:50 -0800 Received: from pao-ex01.pao.digeo.com ([172.17.144.34]) by digeo-e2k04.digeo.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 13 Dec 2002 11:58:57 -0800 Received: from digeo.com ([172.17.140.150]) by pao-ex01.pao.digeo.com with Microsoft SMTPSVC(5.0.2195.4905); Fri, 13 Dec 2002 11:58:56 -0800 Message-ID: <3DFA3BFC.525D1B3@digeo.com> Date: Fri, 13 Dec 2002 11:58:52 -0800 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.5.46 i686) X-Accept-Language: en MIME-Version: 1.0 To: Christoph Hellwig , "linux-xfs@oss.sgi.com" CC: lkml , linux-mm@kvack.org Subject: Re: 2.5.50-mm2 References: <3DF453C8.18B24E66@digeo.com> <20021213175526.C2581@sgi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 13 Dec 2002 19:58:56.0836 (UTC) FILETIME=[12041040:01C2A2E2] X-archive-position: 2072 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: akpm@digeo.com Precedence: bulk X-list: linux-xfs Christoph Hellwig wrote: > > On Mon, Dec 09, 2002 at 12:26:48AM -0800, Andrew Morton wrote: > > +remove-PF_SYNC.patch > > > > remove the current->flags:PF_SYNC abomination. Adds a `sync' arg to > > all writepage implementations to tell them whether they are being > > called for memory cleansing or for data integrity. > > Any chance you could pass down a struct writeback_control instead of > just the sync flag? XFS always used ->writepage similar to the > ->vm_writeback in older kernel releases because writing out more > than one page of delalloc space is really needed to be efficient and > this would allow us to get a few more hints about the VM's intentions. Yup, no probs. It would be good to measure how often that codepath actually gets invoked during testing and use. It's typically quite rare. It should be just MAP_SHARED stuff, although there are probably some highmem-related scenarii in which it will happen. I'll add a writeback_control.for_reclaim boolean so we don't have to play games with PF_MEMALLOC to reverse engineer the calling context. If XFS is going to writearound extra pages in ->writepage() then it would be best to set PG_reclaim (if wbc->for_reclaim) so end_page_writeback() will rotate them. From owner-linux-xfs@oss.sgi.com Fri Dec 13 12:10:36 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 12:10:39 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBDKAZuR007559 for ; Fri, 13 Dec 2002 12:10:36 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBDIEPG8016192 for ; Fri, 13 Dec 2002 10:14:25 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA29421 for ; Fri, 13 Dec 2002 14:14:19 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA16414 for ; Fri, 13 Dec 2002 14:14:17 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBE3S8h04851 for linux-xfs@oss.sgi.com; Fri, 13 Dec 2002 22:28:08 -0500 Resent-Message-Id: <200212140328.gBE3S8h04851@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA17416 for ; Fri, 13 Dec 2002 14:14:03 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBDKE1Qb42590476 for ; Fri, 13 Dec 2002 12:14:02 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBDKCC3J001171 for ; Fri, 13 Dec 2002 21:12:12 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBDKCCFY001170 for hch@sgi.com; Fri, 13 Dec 2002 21:12:12 +0100 Date: Fri, 13 Dec 2002 21:12:12 +0100 From: Christoph Hellwig Message-Id: <200212132012.gBDKCCFY001170@lab343.munich.sgi.com> Subject: TAKE - remove unused debugging code To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Fri, 13 Dec 2002 22:28:08 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2073 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Fri Dec 13 10:01:28 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:135137a linux/fs/xfs/xfs_vnodeops.c - 1.576 - remove some unused debugging code Subject: TAKE - more dead code removal Date: Fri Dec 13 12:12:46 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:135153a linux/fs/xfs/xfs_vnodeops.c - 1.577 - remove a bunch of checks that aren't needed on linux From owner-linux-xfs@oss.sgi.com Fri Dec 13 12:53:42 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 12:53:47 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBDKrg3v008611 for ; Fri, 13 Dec 2002 12:53:42 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBDIvVG8018399 for ; Fri, 13 Dec 2002 10:57:31 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA34741 for ; Fri, 13 Dec 2002 14:57:23 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA60206 for ; Fri, 13 Dec 2002 14:57:24 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBE4BFA08297 for linux-xfs@oss.sgi.com; Fri, 13 Dec 2002 23:11:15 -0500 Resent-Message-Id: <200212140411.gBE4BFA08297@taclab54.munich.sgi.com> Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA53305 for ; Fri, 13 Dec 2002 14:49:45 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBE43bQ08221 for hch@sgi.com; Fri, 13 Dec 2002 23:03:37 -0500 Date: Fri, 13 Dec 2002 23:03:37 -0500 From: Christoph Hellwig Message-Id: <200212140403.gBE43bQ08221@taclab54.munich.sgi.com> Subject: TAKE - back out the start_aggressive_readahead hack again Resent-From: hch@sgi.com Resent-Date: Fri, 13 Dec 2002 23:11:15 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2074 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs We have the proper fix now, so we don't need this anymore. Date: Fri Dec 13 12:48:42 PST 2002 Workarea: taclab54.munich.sgi.com:/home/hch/repo/slinx/2.4.x-xfs Undoes mod: 2.4.x-xfs:slinx:133397a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135161a linux/mm/page_alloc.c - 1.77 linux/kernel/ksyms.c - 1.141 linux/include/linux/mm.h - 1.87 linux/fs/xfs/pagebuf/page_buf.c - 1.88 From owner-linux-xfs@oss.sgi.com Fri Dec 13 13:03:44 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 13:03:46 -0800 (PST) Received: from poptart.bithose.com (ip-204-97-176-41.modem.logical.net [204.97.176.41]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBDL3g3v009279 for ; Fri, 13 Dec 2002 13:03:43 -0800 Received: from poptart.bithose.com (localhost [127.0.0.1]) by poptart.bithose.com (8.12.2/8.12.2) with ESMTP id gBDL7VvC016979 for ; Fri, 13 Dec 2002 16:07:31 -0500 (EST) Received: from localhost (jakari@localhost) by poptart.bithose.com (8.12.2/8.12.2/Submit) with ESMTP id gBDL7VLQ016964 for ; Fri, 13 Dec 2002 16:07:31 -0500 (EST) X-Authentication-Warning: poptart.bithose.com: jakari owned process doing -bs Date: Fri, 13 Dec 2002 16:07:31 -0500 (EST) From: Jameel Akari To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2075 Subject: (no subject) X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jakari@bithose.com Precedence: bulk X-list: linux-xfs Is there a Redhat 8.0 boot/install CD for 1.2pre3? I see the older 1.2pre1 ISO at : ftp://oss.sgi.com/projects/xfs/Release-1.2pre1/installer/forRH-8.0-SGI-XFS-1.2pre1.isoftp://oss.sgi.com/projects/xfs/Release-1.2pre1/installer/forRH-8.0-SGI-XFS-1.2pre1.iso I'm also aware of the DVD that has been worked out.. but between a 3.5GB download and a lack of a DVD writer, it isn't going to help much. #!/jameel/akari sleep 4800; make clean && make breakfast From owner-linux-xfs@oss.sgi.com Fri Dec 13 13:30:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 13:30:36 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBDLUX3v010214 for ; Fri, 13 Dec 2002 13:30:33 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBDKd0Kp015650 for ; Fri, 13 Dec 2002 12:39:00 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id PAA34484 for ; Fri, 13 Dec 2002 15:34:16 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id PAA44329 for ; Fri, 13 Dec 2002 15:34:16 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBE4m7c08586 for linux-xfs@oss.sgi.com; Fri, 13 Dec 2002 23:48:07 -0500 Resent-Message-Id: <200212140448.gBE4m7c08586@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id PAA66091 for ; Fri, 13 Dec 2002 15:33:55 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBDLXsQb40558823 for ; Fri, 13 Dec 2002 13:33:54 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBDLW44g025577 for ; Fri, 13 Dec 2002 22:32:04 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBDLW4eb025576 for hch@sgi.com; Fri, 13 Dec 2002 22:32:04 +0100 Date: Fri, 13 Dec 2002 22:32:04 +0100 From: Christoph Hellwig Message-Id: <200212132132.gBDLW4eb025576@lab343.munich.sgi.com> Subject: TAKE - remove superlous MAXNAMELEN checks To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Fri, 13 Dec 2002 23:48:07 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2076 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Fri Dec 13 13:27:14 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:135168a linux/fs/xfs/xfs_rename.c - 1.45 linux/fs/xfs/xfs_vnodeops.c - 1.578 - don't check for MAXNAMELEN in the individual VOPs - we never enter them with longer names linux/fs/xfs/xfs_dir.c - 1.147 linux/fs/xfs/xfs_dir2.c - 1.41 - don't check for MAXNAMELEN in lowlevel directory code - we never enter it with longer names linux/fs/xfs/linux/xfs_linux.h - 1.96 - remove second (identical) MAXNAMELEN define From owner-linux-xfs@oss.sgi.com Fri Dec 13 16:24:56 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 16:24:58 -0800 (PST) Received: from banna (fb175194.ot.FreeBit.NE.JP [61.203.175.194]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBE0OM3v012120 for ; Fri, 13 Dec 2002 16:24:48 -0800 Received: from 5-C ([192.168.0.2]) by banna (8.9.3+3.2W/3.7W) with SMTP id JAA26769; Sat, 14 Dec 2002 09:28:25 +0900 Message-Id: <200212140028.JAA26769@banna> From: =?iso-2022-jp?B?am1haWw2NjY2anA=?= To: =?iso-2022-jp?B?MDU=?=@banna.sgi.com Reply-To: jmail6666jp@yahoo.co.jp Date: Sat, 14 Dec 2002 09:26:44 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2077 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jmail6666jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_ssu@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.xx-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.ww-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Fri Dec 13 22:50:07 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 22:50:11 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBE6o73v022400 for ; Fri, 13 Dec 2002 22:50:07 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBE6o7Po022399 for linux-xfs@oss.sgi.com; Fri, 13 Dec 2002 22:50:07 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBE6o53v022385 for ; Fri, 13 Dec 2002 22:50:05 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBE6n494022371; Fri, 13 Dec 2002 22:49:04 -0800 Date: Fri, 13 Dec 2002 22:49:04 -0800 Message-Id: <200212140649.gBE6n494022371@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2078 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From cattelan@thebarn.com 2002-12-13 22:49 ------- This will probably linked to one app doing something strange. look at the process table when your desktop is running, make a list and then start running stuff one at a time. Run the test and pull the plug ofcourse. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Fri Dec 13 23:03:58 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 23:04:01 -0800 (PST) Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBE73w3v022923 for ; Fri, 13 Dec 2002 23:03:58 -0800 Received: from [10.0.0.10] (c-24-245-56-70.mn.client2.attbi.com [24.245.56.70]) by lips.thebarn.com (8.12.6/8.12.6) with ESMTP id gBE77TLu075596; Sat, 14 Dec 2002 01:07:31 -0600 (CST) (envelope-from cattelan@thebarn.com) Subject: Re: (no subject) From: Russell Cattelan To: Jameel Akari Cc: linux-xfs@oss.sgi.com In-Reply-To: References: Content-Type: text/plain Organization: Message-Id: <1039849648.240.6.camel@lupo.thebarn.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 14 Dec 2002 01:07:28 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 2079 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs No a new installer has not re-spun. At this point I doubt it will be, it's a simple process of updating the kernel to the newer version once you have the system installed. On Fri, 2002-12-13 at 15:07, Jameel Akari wrote: > Is there a Redhat 8.0 boot/install CD for 1.2pre3? I see the older > 1.2pre1 ISO at : > > ftp://oss.sgi.com/projects/xfs/Release-1.2pre1/installer/forRH-8.0-SGI-XFS-1.2pre1.isoftp://oss.sgi.com/projects/xfs/Release-1.2pre1/installer/forRH-8.0-SGI-XFS-1.2pre1.iso > > I'm also aware of the DVD that has been worked out.. but between a 3.5GB > download and a lack of a DVD writer, it isn't going to help much. > > > #!/jameel/akari > sleep 4800; > make clean && make breakfast -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Fri Dec 13 23:14:04 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 23:14:09 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBE7E43v023442 for ; Fri, 13 Dec 2002 23:14:04 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBE7E3fE023441 for linux-xfs@oss.sgi.com; Fri, 13 Dec 2002 23:14:03 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBE7E13x023427 for ; Fri, 13 Dec 2002 23:14:01 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBE6t0fD022833; Fri, 13 Dec 2002 22:55:00 -0800 Date: Fri, 13 Dec 2002 22:55:00 -0800 Message-Id: <200212140655.gBE6t0fD022833@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 197] stalled files in /var/lock, data fork in ino 79692177 claims free block 5040984 X-Bugzilla-Reason: AssignedTo X-archive-position: 2080 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=197 ------- Additional Comments From cattelan@thebarn.com 2002-12-13 22:54 ------- This looks similar to some internal problems we are having. Was this box running anything but pre3? any current code? e.g. a cvs checkout ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Fri Dec 13 23:40:37 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 13 Dec 2002 23:40:40 -0800 (PST) Received: from mail.kaloudis.net (dpvc-141-156-112-29.res.east.verizon.net [141.156.112.29]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBE7ea3v023970 for ; Fri, 13 Dec 2002 23:40:37 -0800 Received: from visual (dsl092-103-153.nyc2.dsl.speakeasy.net [66.92.103.153]) by mail.kaloudis.net (iPlanet Messaging Server 5.2 (built Feb 21 2002)) with ESMTPSA id <0H730037AMTT2R@mail.kaloudis.net> for linux-xfs@oss.sgi.com; Sat, 14 Dec 2002 02:44:19 -0500 (EST) Date: Sat, 14 Dec 2002 02:50:10 -0500 From: alex Subject: broken ibm 75gxp -> xfs_repair -sectorSkipper3000 To: linux-xfs@oss.sgi.com Reply-to: alex@kaloudis.net Message-id: <001a01c2a345$6e40b300$9600a8c0@visual> Organization: slinc. MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Mailer: Microsoft Outlook, Build 10.0.2616 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-archive-position: 2081 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: alex@kaloudis.net Precedence: bulk X-list: linux-xfs hey guys. i've got a broken ibm 75gxp. this is my second and last 75gxp to go down. it's still got a few things on it that i would love to grab. i tried doing a restore and was told to rebuild the log (-L). and so i did and after doing so it seems to die in the same spot every time. the death is definitely hw related seeing as how the drive makes a very scary noise every time it reaches the same spot. what i'm wondering is if there is a way to skip this part of the drive in a repair. thanks.alex. here is the output from xfs_repair... ------------------------------------------------------- [root@spade mnt]# /sbin/xfs_repair /dev/hde5 Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 inconsistent with calculated value 13835049053030711424 resetting superblock root inode pointer to 18446744069414584448 sb realtime bitmap inode 18446744073709551615 inconsistent with calculated value 13835049053030711425 resetting superblock realtime bitmap ino pointer to 18446744069414584449 sb realtime summary inode 18446744073709551615 inconsistent with calculated value 13835049053030711426 resetting superblock realtime summary ino pointer to 18446744069414584450 Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... bad agbno 0 for btbno root, agno 0 bad agbno 0 for btbcnt root, agno 0 bad agbno 0 for inobt root, agno 0 root inode chunk not found Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 imap claims in-use inode 131 is free, correcting imap imap claims in-use inode 132 is free, correcting imap imap claims in-use inode 133 is free, correcting imap imap claims in-use inode 134 is free, correcting imap imap claims in-use inode 135 is free, correcting imap imap claims in-use inode 136 is free, correcting imap imap claims in-use inode 137 is free, correcting imap imap claims in-use inode 138 is free, correcting imap imap claims in-use inode 139 is free, correcting imap imap claims in-use inode 140 is free, correcting imap imap claims in-use inode 141 is free, correcting imap imap claims in-use inode 142 is free, correcting imap imap claims in-use inode 143 is free, correcting imap imap claims in-use inode 144 is free, correcting imap imap claims in-use inode 145 is free, correcting imap imap claims in-use inode 146 is free, correcting imap imap claims in-use inode 147 is free, correcting imap imap claims in-use inode 148 is free, correcting imap imap claims in-use inode 149 is free, correcting imap imap claims in-use inode 150 is free, correcting imap imap claims in-use inode 151 is free, correcting imap imap claims in-use inode 152 is free, correcting imap imap claims in-use inode 153 is free, correcting imap imap claims in-use inode 154 is free, correcting imap imap claims in-use inode 155 is free, correcting imap imap claims in-use inode 156 is free, correcting imap imap claims in-use inode 157 is free, correcting imap imap claims in-use inode 158 is free, correcting imap imap claims in-use inode 159 is free, correcting imap imap claims in-use inode 160 is free, correcting imap imap claims in-use inode 161 is free, correcting imap imap claims in-use inode 162 is free, correcting imap imap claims in-use inode 163 is free, correcting imap imap claims in-use inode 164 is free, correcting imap imap claims in-use inode 165 is free, correcting imap imap claims in-use inode 166 is free, correcting imap imap claims in-use inode 167 is free, correcting imap imap claims in-use inode 168 is free, correcting imap imap claims in-use inode 169 is free, correcting imap imap claims in-use inode 170 is free, correcting imap imap claims in-use inode 171 is free, correcting imap imap claims in-use inode 172 is free, correcting imap imap claims in-use inode 173 is free, correcting imap imap claims in-use inode 174 is free, correcting imap imap claims in-use inode 175 is free, correcting imap imap claims in-use inode 176 is free, correcting imap imap claims in-use inode 177 is free, correcting imap imap claims in-use inode 178 is free, correcting imap imap claims in-use inode 179 is free, correcting imap imap claims in-use inode 180 is free, correcting imap imap claims in-use inode 181 is free, correcting imap imap claims in-use inode 182 is free, correcting imap imap claims in-use inode 183 is free, correcting imap imap claims in-use inode 184 is free, correcting imap imap claims in-use inode 185 is free, correcting imap imap claims in-use inode 186 is free, correcting imap imap claims in-use inode 187 is free, correcting imap imap claims in-use inode 188 is free, correcting imap imap claims in-use inode 189 is free, correcting imap imap claims in-use inode 190 is free, correcting imap imap claims in-use inode 191 is free, correcting imap - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - agno = 17 - agno = 18 - agno = 19 - agno = 20 - agno = 21 - agno = 22 - agno = 23 - agno = 24 - agno = 25 - agno = 26 - agno = 27 - agno = 28 - agno = 29 - agno = 30 - agno = 31 - agno = 32 - agno = 33 - agno = 34 - agno = 35 - agno = 36 - agno = 37 - agno = 38 - agno = 39 From owner-linux-xfs@oss.sgi.com Sat Dec 14 05:56:55 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 05:57:01 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBEDut3v030374 for ; Sat, 14 Dec 2002 05:56:55 -0800 Received: from relay1.corp.sgi.com (ether-spindle.corp.sgi.com [192.26.51.29]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBEC0mG8024375 for ; Sat, 14 Dec 2002 04:00:48 -0800 Received: from Liberator (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id GAA22908; Sat, 14 Dec 2002 06:00:09 -0800 (PST) Subject: Re: broken ibm 75gxp -> xfs_repair -sectorSkipper3000 From: Eric Sandeen To: alex@kaloudis.net Cc: linux-xfs@oss.sgi.com In-Reply-To: <001a01c2a345$6e40b300$9600a8c0@visual> References: <001a01c2a345$6e40b300$9600a8c0@visual> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 14 Dec 2002 07:59:49 -0600 Message-Id: <1039874395.12439.13.camel@Liberator> Mime-Version: 1.0 X-archive-position: 2082 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs On Sat, 2002-12-14 at 01:50, alex wrote: > hey guys. i've got a broken ibm 75gxp. this is my second and > last 75gxp to go down. it's still got a few things on it that > i would love to grab. i tried doing a restore and was told to > rebuild the log (-L). and so i did and after doing so it seems > to die in the same spot every time. repair -L does not rebuild the log! It zeroes it, obliterates it, throws it away, discards valuable log data. If repair said anything about -L, it also told you to mount & unmount the filesystem first. If you zeroed the log, then repair -will- find problems, because the log is the only thing that was keeping the filesystem in a consistent state. Anyway... > the death is definitely hw > related seeing as how the drive makes a very scary noise every > time it reaches the same spot. what i'm wondering is if there > is a way to skip this part of the drive in a repair. If you have enough spare space on a good drive, I would use dd to create an image of the partition on the bad disk; there are options to dd that let you skip over bad blocks, and replace them with zeroes in the output image. Then you can try running repair on that filesystem image. -Eric From owner-linux-xfs@oss.sgi.com Sat Dec 14 07:17:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 07:17:07 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBEFH13v032037 for ; Sat, 14 Dec 2002 07:17:01 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBEFH199032036 for linux-xfs@oss.sgi.com; Sat, 14 Dec 2002 07:17:01 -0800 Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBEFGw3v032022; Sat, 14 Dec 2002 07:16:59 -0800 Received: by tapu.f00f.org (Postfix, from userid 1000) id 09B2C670F; Sat, 14 Dec 2002 07:20:50 -0800 (PST) Date: Sat, 14 Dec 2002 07:20:50 -0800 From: Chris Wedgwood To: bugzilla-daemon@oss.sgi.com Cc: xfs-master@oss.sgi.com Subject: Re: [Bug 202] XFS data corruption Message-ID: <20021214152050.GA17850@tapu.f00f.org> References: <200212140649.gBE6n494022371@oss.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200212140649.gBE6n494022371@oss.sgi.com> User-Agent: Mutt/1.4i X-No-Archive: Yes X-archive-position: 2083 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Fri, Dec 13, 2002 at 10:49:04PM -0800, bugzilla-daemon@oss.sgi.com wrote: > This will probably linked to one app doing something strange. look > at the process table when your desktop is running, make a list and > then start running stuff one at a time. Run the test and pull the > plug ofcourse. apps doing strange things shouldn't cause problems like this however, the nvidia binary only module might ... (although i've not seen this myself personally) unless someone can confirm this happens without the nv module loaded (or having been so) i would close this --cw From owner-linux-xfs@oss.sgi.com Sat Dec 14 12:07:25 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 12:07:28 -0800 (PST) Received: from hammail1.truenorth.com (h-213.61.138.102.host.de.colt.net [213.61.138.102]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBEK7N3v009974 for ; Sat, 14 Dec 2002 12:07:24 -0800 Received: from hamburg.fcb.com ([170.200.67.23]) by hammail1.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id H74LEC00.21J for ; Sat, 14 Dec 2002 21:11:00 +0100 Date: Sat, 14 Dec 2002 21:11:14 +0100 Subject: xfs installer errors Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) From: Harald Wagener To: linux-xfs@oss.sgi.com Content-Transfer-Encoding: 7bit In-Reply-To: <1039849648.240.6.camel@lupo.thebarn.com> Message-Id: <32274989-0FA0-11D7-9106-003065DC18B8@hamburg.fcb.com> X-Mailer: Apple Mail (2.548) X-archive-position: 2084 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hwagener@hamburg.fcb.com Precedence: bulk X-list: linux-xfs I just wanted to report two errors with the xfs installer: - text based install dies with a python error in /usr/lib/anaconda/textw/welcome_text.pyc, line 23. This is the dialog where You are hinted at redhat's non-responsibility for this installation. graphical installation works. I am no good at python, so I can't provide a fix here. - using lilo as the boot manager fails because the labels used by the installer are too long for lilo. The maximum length is 12 characters, IIRC, and the original label is something like 'Linux-XFS-2.4.18-SGI-1.2a1', which is too long. Other than that, I can report a (so far) successful update from SGI/1.0(based on RedHat 7.1) to SGI/1.2pre3(based on RedHat 8.0). Regards, Harald -- Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg From owner-linux-xfs@oss.sgi.com Sat Dec 14 12:16:52 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 12:16:54 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBEKGp3v010418 for ; Sat, 14 Dec 2002 12:16:52 -0800 Received: from relay1.corp.sgi.com (ether-spindle.corp.sgi.com [192.26.51.29]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBEIKkG8002364 for ; Sat, 14 Dec 2002 10:20:46 -0800 Received: from Liberator (sshgate.corp.sgi.com [169.238.216.146]) by relay1.corp.sgi.com (980427.SGI.8.8.8/970903.SGI.AUTOCF) via ESMTP id MAA34867; Sat, 14 Dec 2002 12:20:09 -0800 (PST) Subject: Re: xfs installer errors From: Eric Sandeen To: Harald Wagener Cc: linux-xfs@oss.sgi.com In-Reply-To: <32274989-0FA0-11D7-9106-003065DC18B8@hamburg.fcb.com> References: <32274989-0FA0-11D7-9106-003065DC18B8@hamburg.fcb.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 14 Dec 2002 14:19:50 -0600 Message-Id: <1039897192.12386.49.camel@Liberator> Mime-Version: 1.0 X-archive-position: 2085 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Hi Harald - On Sat, 2002-12-14 at 14:11, Harald Wagener wrote: > I just wanted to report two errors with the xfs installer: > > - text based install dies with a python error in > /usr/lib/anaconda/textw/welcome_text.pyc, line 23. This is the dialog > where You are hinted at redhat's non-responsibility for this > installation. graphical installation works. I am no good at python, so > I can't provide a fix here. This one is a problem with a format string / argument count mismatch in a print statement. I suppose we should respin or put out an updates disk for this one. > - using lilo as the boot manager fails because the labels used by the > installer are too long for lilo. The maximum length is 12 characters, > IIRC, and the original label is something like > 'Linux-XFS-2.4.18-SGI-1.2a1', which is too long. Hm, will have to look at this one. Thanks, -Eric From owner-linux-xfs@oss.sgi.com Sat Dec 14 12:24:24 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 12:24:26 -0800 (PST) Received: from hammail1.truenorth.com (h-213.61.138.102.host.de.colt.net [213.61.138.102]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBEKOM3v010852 for ; Sat, 14 Dec 2002 12:24:23 -0800 Received: from hamburg.fcb.com ([170.200.67.23]) by hammail1.truenorth.com (Netscape Messaging Server 4.15) with ESMTP id H74M6O00.H1Q for ; Sat, 14 Dec 2002 21:28:00 +0100 Date: Sat, 14 Dec 2002 21:28:13 +0100 Subject: Re: xfs installer errors Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) From: Harald Wagener To: linux-xfs@oss.sgi.com Content-Transfer-Encoding: 7bit In-Reply-To: <1039897192.12386.49.camel@Liberator> Message-Id: <91E1B93A-0FA2-11D7-9106-003065DC18B8@hamburg.fcb.com> X-Mailer: Apple Mail (2.548) X-archive-position: 2086 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hwagener@hamburg.fcb.com Precedence: bulk X-list: linux-xfs one more addition: The rpm database seems to be corrupt after the installation completes (observed on the updated machine as well as a fresh install done earlier for another machine, thought it to be a freak error at the first time). I do a db_recover in /var/lib/rpm, which deletes all __db.nnn files, and after that a 'rpm --rebuilddb' - after that, all works (reasonably) well. I didn't check if this is a problem with a pure redhat install, but people might get stuck on this. Regards, Harald -- Harald Wagener * FCB/Wilkens * An der Alster 42 * 20099 Hamburg From owner-linux-xfs@oss.sgi.com Sat Dec 14 14:43:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 14:44:04 -0800 (PST) Received: from longsword.omniti.com (ip-66-80-117-3.nyc.megapath.net [66.80.117.3]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBEMhw3v012391 for ; Sat, 14 Dec 2002 14:43:59 -0800 Received: from scout-5.omniti.com ([216.0.51.175] helo=omniti.com) by longsword.omniti.com with asmtp (Exim 3.36 #9) id 18NL4a-0000bH-00; Sat, 14 Dec 2002 17:47:52 -0500 Date: Sat, 14 Dec 2002 17:50:09 -0500 Subject: XFS on Linux on Alpha Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v548) Cc: Theo Schlossnagle To: linux-xfs@oss.sgi.com From: Theo Schlossnagle Content-Transfer-Encoding: 7bit Message-Id: <65D6BBEA-0FB6-11D7-9C5D-00039358205C@omniti.com> X-Mailer: Apple Mail (2.548) X-archive-position: 2087 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jesus@omniti.com Precedence: bulk X-list: linux-xfs I know that I have run XFS on Linux on Alpha in the past. However, I switched to Tru64 for a while and was using advfs. However, I am back to Linux and I would like to run XFS on my dual ev67 box. The patches have changed a bit since I last tried XFS on non-i386 machines. I notice an ia64 patch, but no alpha patch. Is there something I have to do specific to my alpha to get it to run? I was planning on snagging the patch against 2.4.20 and applying that. Should I fetch all the split parts and leave out the i386 and ia64 parts? Thanks in advance, -- Theo Schlossnagle Principal Consultant OmniTI Computer Consulting, Inc. -- http://www.omniti.com/ 1024D/82844984/95FD 30F1 489E 4613 F22E 491A 7E88 364C 8284 4984 2047R/33131B65/71 F7 95 64 49 76 5D BA 3D 90 B9 9F BE 27 24 E7 From owner-linux-xfs@oss.sgi.com Sat Dec 14 20:03:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 20:04:02 -0800 (PST) Received: from jaguar.mkp.net (jaguar.mkp.net [66.11.169.42]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBF43w3v016357 for ; Sat, 14 Dec 2002 20:03:58 -0800 Received: from mojo.mkp.net (localhost.mkp.net [127.0.0.1]) by jaguar.mkp.net (Postfix) with ESMTP id 62109177CF; Sat, 14 Dec 2002 23:07:52 -0500 (EST) Received: by mojo.mkp.net (Postfix, from userid 1654) id 22CF3200182; Sat, 14 Dec 2002 23:06:40 -0500 (EST) To: Theo Schlossnagle Cc: linux-xfs@oss.sgi.com Subject: Re: XFS on Linux on Alpha From: "Martin K. Petersen" Organization: mkp.net References: <65D6BBEA-0FB6-11D7-9C5D-00039358205C@omniti.com> Date: 14 Dec 2002 23:06:40 -0500 In-Reply-To: <65D6BBEA-0FB6-11D7-9C5D-00039358205C@omniti.com> Message-ID: Lines: 17 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 2088 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mkp@mkp.net Precedence: bulk X-list: linux-xfs >>>>> "Theo" == Theo Schlossnagle writes: Theo> Is there something I have to do specific to my alpha to get it Theo> to run? Not really. Theo> I was planning on snagging the patch against 2.4.20 and applying Theo> that. Should I fetch all the split parts and leave out the i386 Theo> and ia64 parts? I recommend grabbing the CVS tree instead. -- Martin K. Petersen http://mkp.net/ From owner-linux-xfs@oss.sgi.com Sat Dec 14 20:28:51 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 14 Dec 2002 20:28:53 -0800 (PST) Received: from mail.ocs.com.au (mail.ocs.com.au [203.34.97.2]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBF4Sm3v016877 for ; Sat, 14 Dec 2002 20:28:49 -0800 Received: (qmail 17153 invoked from network); 15 Dec 2002 04:32:41 -0000 Received: from ocs3.intra.ocs.com.au (192.168.255.3) by mail.ocs.com.au with SMTP; 15 Dec 2002 04:32:41 -0000 Received: by ocs3.intra.ocs.com.au (Postfix, from userid 16331) id AAA723000B8; Sun, 15 Dec 2002 15:32:38 +1100 (EST) Received: from ocs3.intra.ocs.com.au (localhost [127.0.0.1]) by ocs3.intra.ocs.com.au (Postfix) with ESMTP id 2806185; Sun, 15 Dec 2002 15:32:38 +1100 (EST) X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 From: Keith Owens To: Theo Schlossnagle Cc: linux-xfs@oss.sgi.com Subject: Re: XFS on Linux on Alpha In-reply-to: Your message of "Sat, 14 Dec 2002 17:50:09 CDT." <65D6BBEA-0FB6-11D7-9C5D-00039358205C@omniti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 15 Dec 2002 15:32:32 +1100 Message-ID: <31082.1039926752@ocs3.intra.ocs.com.au> X-archive-position: 2089 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kaos@sgi.com Precedence: bulk X-list: linux-xfs On Sat, 14 Dec 2002 17:50:09 -0500, Theo Schlossnagle wrote: >The patches have changed a bit since I last tried XFS on non-i386 >machines. I notice an ia64 patch, but no alpha patch. Is there >something I have to do specific to my alpha to get it to run? I was >planning on snagging the patch against 2.4.20 and applying that. >Should I fetch all the split parts and leave out the i386 and ia64 >parts? That depends on how close your alpha kernel tree is to Marcelo's 2.4.20. If alpha is close to 2.4.20 then start with XFS CVS and apply any diffs required for a normal alpha build. If alpha is significantly different from standard 2.4.20 then applying the split patches to a working alpha kernel might be a better option. In either case, you need to define the xattr syscall numbers on alpha, neither the CVS nor split patches contain alpha syscall updates. The ia64 split patch only contains default config and syscall changes, you need to develop the equivalent for alpha. There may be a respin of the XFS split patches this week, to bring the snapshot in sync with CVS, but no promises. From owner-linux-xfs@oss.sgi.com Sun Dec 15 00:11:25 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 00:11:31 -0800 (PST) Received: from least.beast ([195.128.153.227]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBF8BN3v018705 for ; Sun, 15 Dec 2002 00:11:24 -0800 Received: from least.beast (unknown [127.0.0.1]) by least.beast (Postfix) with SMTP id 5A63EB77E for ; Sun, 15 Dec 2002 12:16:18 +0400 (SAMT) Date: Sun, 15 Dec 2002 12:16:17 +0400 From: Peter Vereshagin To: linux-xfs@oss.sgi.com Message-Id: <20021215121617.28cc0b92.petr999@hotbox.ru> Organization: Nevermind X-Mailer: Sylpheed version 0.8.1 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 2090 Subject: (no subject) X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: petr999@hotbox.ru Precedence: bulk X-list: linux-xfs From owner-linux-xfs@oss.sgi.com Sun Dec 15 11:03:44 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 11:03:47 -0800 (PST) Received: from banna (fb172047.ot.FreeBit.NE.JP [61.203.172.47]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBFJ3e3v032615 for ; Sun, 15 Dec 2002 11:03:44 -0800 Received: from C ([192.168.0.4]) by banna (8.9.3+3.2W/3.7W) with SMTP id EAA24700; Mon, 16 Dec 2002 04:11:10 +0900 Message-Id: <200212151911.EAA24700@banna> From: =?iso-2022-jp?B?amFtaWw1NTU1anA=?= To: =?iso-2022-jp?B?NTAwMDA=?=@banna.sgi.com Reply-To: jmail5555jp@yahoo.co.jp Date: Mon, 16 Dec 2002 04:10:27 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2091 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jmail5555jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_sst@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.xx-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.ww-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Sun Dec 15 13:52:40 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 13:52:44 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBFLqd3v004161 for ; Sun, 15 Dec 2002 13:52:40 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBFM2Dkq002184 for ; Sun, 15 Dec 2002 16:02:14 -0600 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id IAA61455 for linux-xfs@oss.sgi.com; Mon, 16 Dec 2002 08:55:15 +1100 (EST) Date: Mon, 16 Dec 2002 08:55:15 +1100 (EST) From: Nathan Scott Message-Id: <200212152155.IAA61455@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - rt size check X-archive-position: 2092 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Fix size check for realtime devices. -- thanks Eric. Date: Sun Dec 15 13:51:35 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/pagebuf The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135199a linux/fs/xfs/xfs_rtalloc.c - 1.85 - Fix size check for realtime devices. From owner-linux-xfs@oss.sgi.com Sun Dec 15 15:31:11 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 15:31:13 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBFNVA3v006982 for ; Sun, 15 Dec 2002 15:31:10 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBFMdpKp012512 for ; Sun, 15 Dec 2002 14:39:51 -0800 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id KAA74564; Mon, 16 Dec 2002 10:33:45 +1100 (EST) Date: Mon, 16 Dec 2002 10:33:45 +1100 (EST) From: Nathan Scott Message-Id: <200212152333.KAA74564@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Cc: agruen@suse.de Subject: TAKE - acl X-archive-position: 2093 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Minor Debian-related packaging and doc fixups. Date: Sun Dec 15 15:33:11 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135200a cmd/acl/VERSION - 1.40 cmd/acl/doc/CHANGES - 1.47 cmd/acl/man/man5/acl.5 - 1.15 cmd/acl/debian/changelog - 1.35 cmd/acl/debian/rules - 1.11 From owner-linux-xfs@oss.sgi.com Sun Dec 15 16:21:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 16:21:41 -0800 (PST) Received: from smtp2.libero.it (smtp2.libero.it [193.70.192.52]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBG0LX3v007712 for ; Sun, 15 Dec 2002 16:21:34 -0800 Received: from flameeyes.is-a-geek.org (151.25.11.141) by smtp2.libero.it (6.7.015) id 3DE353230080ED86 for linux-xfs@oss.sgi.com; Sat, 14 Dec 2002 17:57:08 +0100 Message-ID: Date: Sat, 14 Dec 2002 17:48:54 +0100 From: Flameeyes User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: it, en, fr, es MIME-Version: 1.0 X-Newsgroups: mls.linux.xfs Subject: Re: [Bug 202] XFS data corruption References: <200212140649.gBE6n494022371@oss.sgi.com> <20021214152050.GA17850@tapu.f00f.org> In-Reply-To: <20021214152050.GA17850@tapu.f00f.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit To: linux-xfs@oss.sgi.com X-Gate: Hamster/1.3.23.210 NewsToMail-Gate X-archive-position: 2094 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: diego_p@libero.it Precedence: bulk X-list: linux-xfs Chris Wedgwood wrote: > unless someone can confirm this happens without the nv module loaded > (or having been so) i would close this I have had similar problems and I have NVdriver installed, but I don't know when exactly the corruption was made. -- Flameeyes http://drakeadmin.sourceforge.net/ From owner-linux-xfs@oss.sgi.com Sun Dec 15 21:45:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 21:46:03 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBG5jw3v031662 for ; Sun, 15 Dec 2002 21:45:58 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBG5tWkq007617 for ; Sun, 15 Dec 2002 23:55:34 -0600 Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.9.3/8.9.3) id QAA65052 for linux-xfs@oss.sgi.com; Mon, 16 Dec 2002 16:48:31 +1100 (EST) Date: Mon, 16 Dec 2002 16:48:31 +1100 (EST) From: Nathan Scott Message-Id: <200212160548.QAA65052@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - unwritten extent changes, cleanup X-archive-position: 2095 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Some cleanup and some more unwritten extent related changes. Date: Sun Dec 15 21:46:35 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135207a linux/fs/xfs/xfs_alloc_btree.h - 1.23 - Cleanup whitespace botch. linux/fs/xfs/pagebuf/page_buf.h - 1.54 linux/fs/xfs/linux/xfs_iomap.c - 1.4 - Minor cleanup and some unwritten extent related changes. From owner-linux-xfs@oss.sgi.com Sun Dec 15 22:41:17 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 15 Dec 2002 22:41:20 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBG6fH3v032355 for ; Sun, 15 Dec 2002 22:41:17 -0800 Received: by tapu.f00f.org (Postfix, from userid 1000) id CBD801E1AD4; Sun, 15 Dec 2002 22:45:16 -0800 (PST) Date: Sun, 15 Dec 2002 22:45:16 -0800 From: Chris Wedgwood To: Flameeyes Cc: linux-xfs@oss.sgi.com Subject: Re: [Bug 202] XFS data corruption Message-ID: <20021216064516.GA23463@tapu.f00f.org> References: <200212140649.gBE6n494022371@oss.sgi.com> <20021214152050.GA17850@tapu.f00f.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-No-Archive: Yes X-archive-position: 2096 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Sat, Dec 14, 2002 at 05:48:54PM +0100, Flameeyes wrote: > I have had similar problems and I have NVdriver installed, but I > don't know when exactly the corruption was made. What kernel version and what NVdriver version? --cw From owner-linux-xfs@oss.sgi.com Mon Dec 16 04:20:09 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Dec 2002 04:20:14 -0800 (PST) Received: from mail.tvol.net (pr-66-150-46-254.wgate.com [66.150.46.254]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBGCK83v010686 for ; Mon, 16 Dec 2002 04:20:09 -0800 Received: from sinz.eng.tvol.net ([10.32.2.99]) by mail.tvol.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id 41A60JGM; Mon, 16 Dec 2002 07:23:46 -0500 Received: from wgate.com (sinz.eng.tvol.net [127.0.0.1]) by sinz.eng.tvol.net (8.12.5/8.12.5) with ESMTP id gBGCKtr2027160; Mon, 16 Dec 2002 07:20:56 -0500 Message-ID: <3DFDC527.7080208@wgate.com> Date: Mon, 16 Dec 2002 07:20:55 -0500 From: Michael Sinz User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20021111 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Harald Wagener CC: linux-xfs@oss.sgi.com Subject: Re: xfs installer errors References: <91E1B93A-0FA2-11D7-9106-003065DC18B8@hamburg.fcb.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2097 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: msinz@wgate.com Precedence: bulk X-list: linux-xfs Harald Wagener wrote: > one more addition: The rpm database seems to be corrupt after the > installation completes (observed on the updated machine as well as a > fresh install done earlier for another machine, thought it to be a freak > error at the first time). I do a db_recover in /var/lib/rpm, which > deletes all __db.nnn files, and after that a 'rpm --rebuilddb' - after > that, all works (reasonably) well. > > I didn't check if this is a problem with a pure redhat install, but > people might get stuck on this. I have not noticed this in the many installs I have done. (Most of them are network/NFS installs with my own kickstart config) BTW - Doing a full kickstart install in text mode works fine even if the disk is brand new/empty. (Non-interactive kickstart mode) I keep wanting to take the time to respin an installer with our packages in it but it has been just as simple to add in a kickstart post-install script to install those things that are not part of the distribution. (And install a new kernel, etc) -- Michael Sinz -- Director, Systems Engineering -- Worldgate Communications A master's secrets are only as good as the master's ability to explain them to others. From owner-linux-xfs@oss.sgi.com Mon Dec 16 05:49:55 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Dec 2002 05:50:00 -0800 (PST) Received: from smtp1.libero.it (smtp1.libero.it [193.70.192.51]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBGDns3v015621 for ; Mon, 16 Dec 2002 05:49:55 -0800 Received: from flameeyes.is-a-geek.org (151.25.17.250) by smtp1.libero.it (6.7.015) id 3DE22B8100923FAA for linux-xfs@oss.sgi.com; Mon, 16 Dec 2002 12:55:12 +0100 Message-ID: Date: Mon, 16 Dec 2002 12:41:40 +0100 From: Flameeyes User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: it, en, fr, es MIME-Version: 1.0 X-Newsgroups: mls.linux.xfs Subject: Re: [Bug 202] XFS data corruption References: <200212140649.gBE6n494022371@oss.sgi.com> <20021214152050.GA17850@tapu.f00f.org> <20021216064516.GA23463@tapu.f00f.org> In-Reply-To: <20021216064516.GA23463@tapu.f00f.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit To: linux-xfs@oss.sgi.com X-Gate: Hamster/1.3.23.210 NewsToMail-Gate X-archive-position: 2098 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: diego_p@libero.it Precedence: bulk X-list: linux-xfs Chris Wedgwood wrote: > What kernel version and what NVdriver version? kernel 2.4.20-xfs [with patches from bytesex.org for the bttv drivers] NVdriver version 1.0-41.91 [released Dec 11 2002] I don't know if the corruption depends on this, actually, I'm not sure if is a corruption comparable to the one reported in the bug: after a power failure, some files in my home folder was "empty" (I only tried to cat them). -- Flameeyes http://drakeadmin.sourceforge.net/ From owner-linux-xfs@oss.sgi.com Mon Dec 16 08:28:27 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Dec 2002 08:28:31 -0800 (PST) Received: from esds.vss.fsi.com (adsl-66-136-174-212.dsl.stlsmo.swbell.net [66.136.174.212]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBGGSQ3v032518 for ; Mon, 16 Dec 2002 08:28:26 -0800 Received: from mosix (mosix [198.51.26.70]) by esds.vss.fsi.com (8.9.1a/8.9.1) with ESMTP id KAA04105 for ; Mon, 16 Dec 2002 10:32:22 -0600 (CST) Subject: redhat-8.0 From: Matt Schillinger To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 16 Dec 2002 10:34:28 -0600 Message-Id: <1040056469.28990.6.camel@mosix> Mime-Version: 1.0 X-archive-position: 2099 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mschilli@vss.fsi.com Precedence: bulk X-list: linux-xfs Is there any chance that a redhat 8.0 install iso would be made to support XFS? Thanks for you help, -- Matt Schillinger msschilli@vss.fsi.com From owner-linux-xfs@oss.sgi.com Mon Dec 16 08:33:06 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Dec 2002 08:33:08 -0800 (PST) Received: from burgers.bubbanfriends.org (IDENT:postfix@dhcp024-208-195-177.indy.rr.com [24.208.195.177]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBGGX53v000484 for ; Mon, 16 Dec 2002 08:33:06 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 87CF34B7E7A; Mon, 16 Dec 2002 11:37:19 -0500 (EST) Received: by burgers.bubbanfriends.org (Postfix, from userid 500) id 58B954B7E79; Mon, 16 Dec 2002 11:37:18 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by burgers.bubbanfriends.org (Postfix) with ESMTP id 4A482C026A5; Mon, 16 Dec 2002 11:37:18 -0500 (EST) Date: Mon, 16 Dec 2002 11:37:18 -0500 (EST) From: Mike Burger To: Matt Schillinger Cc: linux-xfs@oss.sgi.com Subject: Re: redhat-8.0 In-Reply-To: <1040056469.28990.6.camel@mosix> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 2100 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mburger@bubbanfriends.org Precedence: bulk X-list: linux-xfs It's already there. On 16 Dec 2002, Matt Schillinger wrote: > Is there any chance that a redhat 8.0 install iso would be made to > support XFS? > > Thanks for you help, > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 From owner-linux-xfs@oss.sgi.com Mon Dec 16 08:56:28 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Dec 2002 08:56:30 -0800 (PST) Received: from K-7.stesmi.com (IDENT:86yjKAlEFA/zDxotvOzm2K3KpjUBiUPC@as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBGGuQ3v001568 for ; Mon, 16 Dec 2002 08:56:27 -0800 Received: from stesmi.com (IDENT:Z/tTlUbLt30CEIObIaN4Ae4PVCDZL3t3@as4-1-7.has.s.bonet.se [217.215.31.238]) by K-7.stesmi.com (8.12.4/8.12.4) with ESMTP id gBGGxPJP014930; Mon, 16 Dec 2002 17:59:25 +0100 Message-ID: <3DFE066D.20107@stesmi.com> Date: Mon, 16 Dec 2002 17:59:25 +0100 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matt Schillinger , linux-xfs@oss.sgi.com Subject: Re: redhat-8.0 References: <1040056469.28990.6.camel@mosix> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2101 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stesmi@stesmi.com Precedence: bulk X-list: linux-xfs Matt Schillinger wrote: > Is there any chance that a redhat 8.0 install iso would be made to > support XFS? > > Thanks for you help, There exists one based on XFS 1.2pre1 and there is also a DVD that will be available from an ftp site within a few days. The DVD is NOT from SGI. It is based on their work of course but they didn't do it, so any bug reports should go to ME and not them. It's based on XFS 1.2pre3 and has all latest updates including today. It includes the whole RH8 so there is no DVD-swapping. Insert it, boot from it and off you go. // Stefan From owner-linux-xfs@oss.sgi.com Mon Dec 16 14:40:37 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 16 Dec 2002 14:40:44 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBGMeb3v005587 for ; Mon, 16 Dec 2002 14:40:37 -0800 Received: by tapu.f00f.org (Postfix, from userid 1000) id BF1251DA2F9; Mon, 16 Dec 2002 14:44:37 -0800 (PST) Date: Mon, 16 Dec 2002 14:44:37 -0800 From: Chris Wedgwood To: Flameeyes Cc: linux-xfs@oss.sgi.com Subject: Re: [Bug 202] XFS data corruption Message-ID: <20021216224437.GA26678@tapu.f00f.org> References: <200212140649.gBE6n494022371@oss.sgi.com> <20021214152050.GA17850@tapu.f00f.org> <20021216064516.GA23463@tapu.f00f.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i X-No-Archive: Yes X-archive-position: 2102 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Mon, Dec 16, 2002 at 12:41:40PM +0100, Flameeyes wrote: > kernel 2.4.20-xfs [with patches from bytesex.org for the bttv > drivers] ok > NVdriver version 1.0-41.91 [released Dec 11 2002] i'm surpised that's causing problems ... i have a very slightly different version here i'm using and i don't see it > I don't know if the corruption depends on this, actually, I'm not > sure if is a corruption comparable to the one reported in the bug: > after a power failure, some files in my home folder was "empty" (I > only tried to cat them). well, this may *not* be a bug i think there is confusion as to what the journalling does and what people can expect from it i've yet been unable to reproduce a 'bug' as reported --cw From owner-linux-xfs@oss.sgi.com Tue Dec 17 04:37:12 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 04:37:16 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBHCbB3v018919 for ; Tue, 17 Dec 2002 04:37:12 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBHCkxkq032463 for ; Tue, 17 Dec 2002 06:46:59 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id GAA03342 for ; Tue, 17 Dec 2002 06:41:11 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id GAA82074 for ; Tue, 17 Dec 2002 06:41:10 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBHJsu421705 for linux-xfs@oss.sgi.com; Tue, 17 Dec 2002 14:54:56 -0500 Resent-Message-Id: <200212171954.gBHJsu421705@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id GAA77473 for ; Tue, 17 Dec 2002 06:12:14 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBHCCCQb43477055 for ; Tue, 17 Dec 2002 04:12:13 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBHC9nRX011094 for ; Tue, 17 Dec 2002 13:09:49 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBHC9no2011093 for hch@sgi.com; Tue, 17 Dec 2002 13:09:49 +0100 Date: Tue, 17 Dec 2002 13:09:49 +0100 From: Christoph Hellwig Message-Id: <200212171209.gBHC9no2011093@lab343.munich.sgi.com> Subject: TAKE - fix an out-of-date comment To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 17 Dec 2002 14:54:55 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2103 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 17 04:10:47 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:135307a linux/fs/xfs/xfs_iget.c - 1.180 - fix an out-of-date comment From owner-linux-xfs@oss.sgi.com Tue Dec 17 04:37:19 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 04:37:21 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBHCbI3v018929 for ; Tue, 17 Dec 2002 04:37:19 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBHCl6kq032466 for ; Tue, 17 Dec 2002 06:47:06 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id GAA03224 for ; Tue, 17 Dec 2002 06:41:18 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id GAA81643 for ; Tue, 17 Dec 2002 06:41:16 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBHJt3H21710 for linux-xfs@oss.sgi.com; Tue, 17 Dec 2002 14:55:03 -0500 Resent-Message-Id: <200212171955.gBHJt3H21710@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id GAA79557 for ; Tue, 17 Dec 2002 06:20:53 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBHCKpQb43557805 for ; Tue, 17 Dec 2002 04:20:52 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBHCISRX012093 for ; Tue, 17 Dec 2002 13:18:28 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBHCISIW012092 for hch@sgi.com; Tue, 17 Dec 2002 13:18:28 +0100 Date: Tue, 17 Dec 2002 13:18:28 +0100 From: Christoph Hellwig Message-Id: <200212171218.gBHCISIW012092@lab343.munich.sgi.com> Subject: TAKE - remove references to i_dev, it's gone in recent kernels To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 17 Dec 2002 14:55:03 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2104 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 17 04:20:14 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:135308a linux/fs/xfs/xfsidbg.c - 1.216 - remove references to i_dev, it's gone in recent kernels From owner-linux-xfs@oss.sgi.com Tue Dec 17 08:46:01 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 08:46:13 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBHGju3v028365 for ; Tue, 17 Dec 2002 08:45:59 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBHFsnKp027011 for ; Tue, 17 Dec 2002 07:54:50 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id KAA54871 for ; Tue, 17 Dec 2002 10:49:55 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id KAA11910 for ; Tue, 17 Dec 2002 10:49:52 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBI03c022437 for linux-xfs@oss.sgi.com; Tue, 17 Dec 2002 19:03:38 -0500 Resent-Message-Id: <200212180003.gBI03c022437@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (nodin.corp.sgi.com [192.26.51.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id KAA09667 for ; Tue, 17 Dec 2002 10:44:39 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBHGiZQb43450733 for ; Tue, 17 Dec 2002 08:44:36 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBHGghj3020814 for ; Tue, 17 Dec 2002 17:42:43 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBHGggIF020813 for hch@sgi.com; Tue, 17 Dec 2002 17:42:42 +0100 Date: Tue, 17 Dec 2002 17:42:42 +0100 From: Christoph Hellwig Message-Id: <200212171642.gBHGggIF020813@lab343.munich.sgi.com> Subject: TAKE - merge up to 2.5.52 To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Tue, 17 Dec 2002 19:03:38 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2105 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs kdb is disabled as it doesn't like rusty's cheap kallsyms imitation, everything else seems fine. There are two mods due to my script not liking more modified files than the allowed argument list.. Date: Tue Dec 17 08:06:38 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.52-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:135323a linux/init/main.c - 1.97 linux/Makefile - 1.232 linux/arch/i386/kernel/smpboot.c - 1.52 linux/fs/xfs/xfs_trans_dquot.c - 1.38 linux/fs/xfs/xfsidbg.c - 1.217 linux/fs/xfs/Makefile - 1.162 linux/fs/xfs/xfs_iget.c - 1.177 linux/fs/xfs/xfs_dquot.c - 1.71 linux/fs/xfs/xfs_inode.c - 1.360 linux/fs/xfs/linux/xfs_vnode.c - 1.109 linux/fs/xfs/linux/xfs_super.c - 1.253 linux/fs/xfs/linux/xfs_iops.c - 1.189 linux/kdb/modules/kdbm_vm.c - 1.28 linux/kdb/Makefile - 1.18 linux/kdb/modules/Makefile - 1.17 linux/arch/i386/kdb/Makefile - 1.13 linux/fs/xfs/linux/xfs_ioctl.c - 1.91 linux/kdb/modules/kdbm_pg.c - 1.69 linux/fs/xfs/dmapi/dmapi_register.c - 1.24 linux/fs/xfs/support/move.c - 1.10 linux/fs/xattr.c - 1.10 linux/fs/xfs/linux/xfs_aops.c - 1.23 linux/arch/i386/Kconfig - 1.4 linux/arch/i386/kernel/cpu/mcheck/mce.c - 1.2 Date: Tue Dec 17 08:34:29 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.52-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:135332a linux/drivers/s390/net/cu3088.c - 1.1 linux/drivers/scsi/scsi_sysfs.c - 1.1 linux/security/root_plug.c - 1.1 linux/scripts/per-cpu-check.awk - 1.1 linux/arch/i386/kernel/suspend_asm.S - 1.1 linux/include/linux/compat.h - 1.1 linux/scripts/kallsyms.c - 1.1 linux/drivers/pnp/card.c - 1.1 linux/drivers/s390/char/sclp.c - 1.1 linux/include/asm-v850/as85ep1.h - 1.1 linux/drivers/s390/char/sclp.h - 1.1 linux/drivers/s390/char/sclp_con.c - 1.1 linux/drivers/s390/char/sclp_cpi.c - 1.1 linux/drivers/serial/mux.c - 1.1 linux/drivers/s390/char/sclp_rw.c - 1.1 linux/drivers/mca/Kconfig - 1.1 linux/Documentation/fb/sstfb.txt - 1.1 linux/drivers/s390/char/sclp_rw.h - 1.1 linux/drivers/mca/Makefile - 1.1 linux/drivers/mca/mca-bus.c - 1.1 linux/drivers/mca/mca-device.c - 1.1 linux/drivers/mca/mca-driver.c - 1.1 linux/drivers/s390/char/sclp_tty.c - 1.1 linux/drivers/mca/mca-legacy.c - 1.1 linux/drivers/mca/mca-proc.c - 1.1 linux/drivers/s390/char/sclp_tty.h - 1.1 linux/drivers/media/dvb/frontends/alps_tdlb7.c - 1.1 linux/drivers/s390/char/tape_34xx.c - 1.1 linux/drivers/s390/char/tape_block.c - 1.1 linux/drivers/ide/pci/sc1200.c - 1.1 linux/Documentation/s390/driver-model.txt - 1.1 linux/drivers/media/dvb/frontends/alps_tdmb7.c - 1.1 linux/drivers/acpi/namespace/nsparse.c - 1.1 linux/Documentation/scsi/00-INDEX - 1.1 linux/Documentation/scsi/53c700.txt - 1.1 linux/Documentation/scsi/AM53C974.txt - 1.1 linux/Documentation/scsi/BusLogic.txt - 1.1 linux/Documentation/scsi/ChangeLog - 1.1 linux/Documentation/scsi/ChangeLog.ips - 1.1 linux/Documentation/scsi/ChangeLog.ncr53c8xx - 1.1 linux/Documentation/scsi/ChangeLog.sym53c8xx - 1.1 linux/Documentation/scsi/ChangeLog.sym53c8xx_2 - 1.1 linux/Documentation/scsi/FlashPoint.txt - 1.1 linux/Documentation/scsi/LICENSE.FlashPoint - 1.1 linux/Documentation/scsi/Mylex.txt - 1.1 linux/Documentation/scsi/NinjaSCSI.txt - 1.1 linux/Documentation/scsi/aha152x.txt - 1.1 linux/Documentation/scsi/aic7xxx.txt - 1.1 linux/Documentation/scsi/aic7xxx_old.txt - 1.1 linux/Documentation/scsi/cpqfc.txt - 1.1 linux/Documentation/scsi/dpti.txt - 1.1 linux/Documentation/scsi/dtc3x80.txt - 1.1 linux/Documentation/scsi/g_NCR5380.txt - 1.1 linux/Documentation/scsi/ibmmca.txt - 1.1 linux/Documentation/scsi/in2000.txt - 1.1 linux/Documentation/scsi/ncr53c7xx.txt - 1.1 linux/Documentation/scsi/ncr53c8xx.txt - 1.1 linux/Documentation/scsi/osst.txt - 1.1 linux/Documentation/scsi/ppa.txt - 1.1 linux/Documentation/scsi/qlogicfas.txt - 1.1 linux/Documentation/scsi/qlogicisp.txt - 1.1 linux/Documentation/scsi/scsi-generic.txt - 1.1 linux/Documentation/scsi/scsi.txt - 1.1 linux/Documentation/scsi/scsi_mid_low_api.txt - 1.1 linux/Documentation/scsi/st.txt - 1.1 linux/Documentation/scsi/sym53c8xx_2.txt - 1.1 linux/Documentation/scsi/tmscsim.txt - 1.1 linux/drivers/ide/pci/sc1200.h - 1.1 linux/drivers/usb/serial/bus.c - 1.1 linux/drivers/s390/char/tape_char.c - 1.1 linux/arch/sparc64/kernel/module.c - 1.1 linux/include/asm-sparc64/compat.h - 1.1 linux/drivers/usb/serial/ezusb.c - 1.1 linux/drivers/usb/serial/generic.c - 1.1 linux/drivers/usb/serial/kobil_sct.c - 1.1 linux/arch/sparc64/kernel/profile.c - 1.1 linux/drivers/usb/serial/kobil_sct.h - 1.1 linux/drivers/video/68328fb.c - 1.1 linux/drivers/video/console/Kconfig - 1.1 linux/drivers/video/console/Makefile - 1.1 linux/drivers/video/console/dummycon.c - 1.1 linux/drivers/s390/char/tape_core.c - 1.1 linux/drivers/video/console/fbcon-sti.c - 1.1 linux/drivers/video/console/fbcon.c - 1.1 linux/drivers/video/console/fbcon.h - 1.1 linux/drivers/video/console/font.h - 1.1 linux/drivers/video/console/font_6x11.c - 1.1 linux/drivers/video/console/font_8x16.c - 1.1 linux/drivers/video/console/font_8x8.c - 1.1 linux/drivers/video/console/font_acorn_8x8.c - 1.1 linux/drivers/char/drm/r128_irq.c - 1.1 linux/drivers/video/console/font_mini_4x6.c - 1.1 linux/drivers/char/drm/mga_irq.c - 1.1 linux/drivers/video/console/font_pearl_8x8.c - 1.1 linux/drivers/ieee1394/dma.c - 1.1 linux/drivers/video/console/font_sun12x22.c - 1.1 linux/drivers/video/console/font_sun8x16.c - 1.1 linux/drivers/ieee1394/dma.h - 1.1 linux/arch/sparc64/oprofile/Kconfig - 1.1 linux/drivers/video/console/fonts.c - 1.1 linux/drivers/video/console/mdacon.c - 1.1 linux/drivers/video/console/newport_con.c - 1.1 linux/drivers/video/console/prom.uni - 1.1 linux/drivers/video/console/promcon.c - 1.1 linux/arch/sparc64/oprofile/Makefile - 1.1 linux/arch/sparc64/oprofile/init.c - 1.1 linux/drivers/video/console/sti.h - 1.1 linux/drivers/video/console/sticon.c - 1.1 linux/arch/sparc64/oprofile/timer_int.c - 1.1 linux/drivers/video/console/sticore.c - 1.1 linux/drivers/s390/char/tape_proc.c - 1.1 linux/drivers/s390/char/tape_std.c - 1.1 linux/drivers/video/console/vgacon.c - 1.1 linux/drivers/acpi/events/evgpe.c - 1.1 linux/drivers/video/macmodes.h - 1.1 linux/drivers/acpi/dispatcher/dsinit.c - 1.1 linux/drivers/char/agp/amd-k7-agp.c - 1.1 linux/drivers/video/sis/sis_accel.c - 1.1 linux/drivers/char/agp/amd-k8-agp.c - 1.1 linux/drivers/char/agp/backend.c - 1.1 linux/drivers/char/agp/generic.c - 1.1 linux/crypto/twofish.c - 1.1 linux/arch/arm/kernel/module.c - 1.1 linux/drivers/s390/char/tape_std.h - 1.1 linux/drivers/video/softcursor.c - 1.1 linux/crypto/serpent.c - 1.1 linux/crypto/proc.c - 1.1 linux/drivers/video/sticore.h - 1.1 linux/drivers/ide/pci/cs5520.h - 1.1 linux/crypto/crypto_null.c - 1.1 linux/drivers/video/vgastate.c - 1.1 linux/drivers/ide/pci/cs5520.c - 1.1 linux/fs/compat.c - 1.1 linux/drivers/s390/cio/ccwgroup.c - 1.1 linux/drivers/s390/cio/css.c - 1.1 linux/drivers/s390/cio/css.h - 1.1 linux/drivers/s390/cio/device.c - 1.1 linux/net/ipv4/xfrm_user.c - 1.1 linux/drivers/s390/cio/device.h - 1.1 linux/drivers/s390/cio/device_fsm.c - 1.1 linux/drivers/s390/cio/device_id.c - 1.1 linux/include/asm-s390x/cio.h - 1.1 linux/include/asm-s390x/ccwgroup.h - 1.1 linux/include/asm-s390x/ccwdev.h - 1.1 linux/fs/jfs/acl.c - 1.1 linux/include/asm-s390/cio.h - 1.1 linux/include/linux/mca-legacy.h - 1.1 linux/include/asm-s390/ccwgroup.h - 1.1 linux/include/asm-s390/ccwdev.h - 1.1 linux/include/asm-ppc64/compat.h - 1.1 linux/include/linux/moduleloader.h - 1.1 linux/arch/v850/kernel/module.c - 1.1 linux/drivers/char/agp/intel-agp.c - 1.1 linux/include/linux/moduleparam.h - 1.1 linux/include/asm-mips64/compat.h - 1.1 linux/net/core/link_watch.c - 1.1 linux/drivers/s390/cio/device_ops.c - 1.1 linux/drivers/s390/cio/device_pgid.c - 1.1 linux/drivers/s390/cio/device_status.c - 1.1 linux/drivers/s390/cio/ioasm.h - 1.1 linux/drivers/s390/cio/qdio.c - 1.1 linux/arch/s390x/kernel/module.c - 1.1 linux/arch/s390/kernel/module.c - 1.1 linux/arch/ppc64/oprofile/timer_int.c - 1.1 linux/arch/ppc64/oprofile/init.c - 1.1 linux/include/asm-i386/mca.h - 1.1 linux/drivers/s390/cio/qdio.h - 1.1 linux/drivers/char/watchdog/Kconfig - 1.1 linux/drivers/s390/net/cu3088.h - 1.1 linux/drivers/s390/net/lcs.h - 1.1 linux/arch/ppc/kernel/module.c - 1.1 linux/drivers/s390/s390mach.h - 1.1 linux/drivers/char/watchdog/Makefile - 1.1 linux/drivers/ieee1394/iso.c - 1.1 linux/drivers/ieee1394/iso.h - 1.1 linux/drivers/char/watchdog/acquirewdt.c - 1.1 linux/mm/nommu.c - 1.1 linux/drivers/char/watchdog/advantechwdt.c - 1.1 linux/drivers/ieee1394/oui.db - 1.1 linux/drivers/char/watchdog/eurotechwdt.c - 1.1 linux/include/linux/radeonfb.h - 1.1 linux/drivers/char/watchdog/i810-tco.c - 1.1 linux/drivers/ieee1394/oui2c.sh - 1.1 linux/fs/intermezzo/intermezzo_upcall.h - 1.1 linux/fs/intermezzo/intermezzo_psdev.h - 1.1 linux/drivers/ide/ide-io.c - 1.1 linux/fs/intermezzo/intermezzo_lib.h - 1.1 linux/kernel/compat.c - 1.1 linux/fs/intermezzo/intermezzo_kml.h - 1.1 linux/arch/um/drivers/xterm.h - 1.1 linux/arch/v850/kernel/as85ep1.c - 1.1 linux/arch/um/drivers/xterm_kern.c - 1.1 linux/kernel/params.c - 1.1 linux/drivers/net/r8169.c - 1.1 linux/fs/intermezzo/intermezzo_journal.h - 1.1 linux/arch/i386/kernel/module.c - 1.1 linux/kernel/intermodule.c - 1.1 linux/fs/intermezzo/intermezzo_idl.h - 1.1 linux/kernel/extable.c - 1.1 linux/fs/intermezzo/intermezzo_fs.h - 1.1 linux/drivers/char/watchdog/i810-tco.h - 1.1 linux/drivers/input/misc/gsc_ps2.c - 1.1 linux/drivers/char/drm/drm_sarea.h - 1.1 linux/drivers/char/watchdog/ib700wdt.c - 1.1 linux/drivers/char/watchdog/machzwd.c - 1.1 linux/drivers/char/watchdog/mixcomwd.c - 1.1 linux/include/asm-alpha/suspend.h - 1.1 linux/drivers/char/watchdog/pcwd.c - 1.1 linux/include/video/iga.h - 1.1 linux/arch/sparc/kernel/module.c - 1.1 linux/drivers/char/watchdog/sbc60xxwdt.c - 1.1 linux/include/video/vga.h - 1.1 linux/include/video/radeon.h - 1.1 linux/arch/ppc64/oprofile/Makefile - 1.1 linux/arch/ppc64/kernel/profile.c - 1.1 linux/drivers/char/watchdog/wdt977.c - 1.1 linux/arch/ppc64/oprofile/Kconfig - 1.1 linux/arch/v850/as85ep1.ld - 1.1 linux/drivers/char/watchdog/wdt_pci.c - 1.1 linux/drivers/char/watchdog/shwdt.c - 1.1 linux/drivers/char/watchdog/scx200_wdt.c - 1.1 linux/include/linux/xfrm.h - 1.1 linux/drivers/char/watchdog/softdog.c - 1.1 linux/drivers/char/watchdog/wdt285.c - 1.1 linux/drivers/char/watchdog/wdt.c - 1.1 linux/drivers/char/watchdog/w83877f_wdt.c - 1.1 linux/drivers/char/watchdog/wd501p.h - 1.1 linux/arch/arm/mm/tlb-v4wbi.S - 1.1 linux/scripts/lxdialog/util.c - 1.3 linux/scripts/lxdialog/Makefile - 1.9 linux/scripts/Makefile - 1.14 linux/net/x25/Makefile - 1.8 linux/net/wanrouter/wanmain.c - 1.17 linux/net/wanrouter/Makefile - 1.7 linux/net/unix/af_unix.c - 1.50 linux/net/unix/Makefile - 1.7 linux/net/sunrpc/xprt.c - 1.37 linux/net/sunrpc/xdr.c - 1.11 linux/net/sunrpc/svcsock.c - 1.26 linux/net/sunrpc/svc.c - 1.19 linux/net/sunrpc/sunrpc_syms.c - 1.18 linux/net/sunrpc/sched.c - 1.34 linux/net/sunrpc/pmap_clnt.c - 1.10 linux/net/sunrpc/clnt.c - 1.25 linux/net/sunrpc/Makefile - 1.9 linux/net/socket.c - 1.48 linux/net/sched/sch_sfq.c - 1.9 linux/net/sched/sch_prio.c - 1.9 linux/net/sched/Makefile - 1.9 linux/net/rose/Makefile - 1.7 linux/net/packet/Makefile - 1.6 linux/net/netsyms.c - 1.56 linux/net/netrom/Makefile - 1.7 linux/net/netlink/netlink_dev.c - 1.18 linux/net/netlink/af_netlink.c - 1.23 linux/net/netlink/Makefile - 1.7 linux/net/lapb/Makefile - 1.6 linux/net/irda/irlan/Makefile - 1.6 linux/net/irda/ircomm/Makefile - 1.10 linux/net/irda/af_irda.c - 1.43 linux/net/irda/Makefile - 1.12 linux/net/ipx/Makefile - 1.11 linux/net/ipv6/mcast.c - 1.22 linux/net/ipv6/ip6_input.c - 1.12 linux/net/ipv6/af_inet6.c - 1.28 linux/net/ipv6/Makefile - 1.9 linux/net/ipv4/udp.c - 1.37 linux/net/ipv4/tcp_ipv4.c - 1.55 linux/net/ipv4/route.c - 1.40 linux/net/ipv4/raw.c - 1.29 linux/net/ipv4/proc.c - 1.15 linux/net/ipv4/ip_sockglue.c - 1.23 linux/net/ipv4/ip_output.c - 1.40 linux/net/ipv4/fib_hash.c - 1.9 linux/net/ipv4/arp.c - 1.27 linux/net/ipv4/af_inet.c - 1.46 linux/net/ipv4/Makefile - 1.15 linux/net/ethernet/Makefile - 1.6 linux/net/econet/Makefile - 1.8 linux/net/core/scm.c - 1.9 linux/net/core/neighbour.c - 1.18 linux/net/core/dev.c - 1.64 linux/net/core/Makefile - 1.13 linux/net/bridge/Makefile - 1.8 linux/net/ax25/ax25_route.c - 1.9 linux/net/ax25/Makefile - 1.7 linux/net/appletalk/Makefile - 1.8 linux/net/Makefile - 1.29 linux/net/802/tr.c - 1.13 linux/net/802/Makefile - 1.11 linux/mm/vmscan.c - 1.121 linux/mm/swapfile.c - 1.69 linux/mm/swap_state.c - 1.55 linux/mm/swap.c - 1.31 linux/mm/slab.c - 1.46 linux/mm/page_io.c - 1.32 linux/mm/page_alloc.c - 1.101 linux/mm/mremap.c - 1.38 linux/mm/mprotect.c - 1.37 linux/mm/mmap.c - 1.67 linux/mm/memory.c - 1.98 linux/mm/filemap.c - 1.144 linux/mm/Makefile - 1.22 linux/lib/string.c - 1.15 linux/lib/Makefile - 1.16 linux/kernel/time.c - 1.13 linux/kernel/sysctl.c - 1.62 linux/kernel/sys.c - 1.45 linux/kernel/signal.c - 1.47 linux/kernel/sched.c - 1.90 linux/kernel/printk.c - 1.26 linux/kernel/module.c - 1.32 linux/kernel/ksyms.c - 1.176 linux/kernel/kmod.c - 1.27 linux/kernel/fork.c - 1.78 linux/kernel/exit.c - 1.59 linux/kernel/exec_domain.c - 1.20 linux/kernel/capability.c - 1.11 linux/kernel/acct.c - 1.22 linux/kernel/Makefile - 1.40 linux/ipc/util.c - 1.23 linux/ipc/shm.c - 1.60 linux/ipc/sem.c - 1.24 linux/ipc/msg.c - 1.17 linux/ipc/Makefile - 1.5 linux/init/main.c - 1.98 linux/include/video/macmodes.h - 1.6 linux/include/video/font.h - 1.4 linux/include/video/fbcon.h - 1.14 linux/include/video/fbcon-vga.h - 1.3 linux/include/video/fbcon-mfb.h - 1.3 linux/include/video/fbcon-mac.h - 1.3 linux/include/video/fbcon-iplan2p8.h - 1.3 linux/include/video/fbcon-iplan2p4.h - 1.3 linux/include/video/fbcon-iplan2p2.h - 1.3 linux/include/video/fbcon-ilbm.h - 1.3 linux/include/video/fbcon-cfb8.h - 1.3 linux/include/video/fbcon-cfb4.h - 1.3 linux/include/video/fbcon-cfb32.h - 1.3 linux/include/video/fbcon-cfb24.h - 1.3 linux/include/video/fbcon-cfb2.h - 1.3 linux/include/video/fbcon-cfb16.h - 1.3 linux/include/video/fbcon-afb.h - 1.3 linux/include/scsi/sg.h - 1.19 linux/include/scsi/scsi_ioctl.h - 1.4 linux/include/net/udp.h - 1.12 linux/include/net/sock.h - 1.41 linux/include/net/route.h - 1.21 linux/include/net/ip_fib.h - 1.9 linux/include/linux/wanpipe.h - 1.9 linux/include/linux/wait.h - 1.18 linux/include/linux/vt_kern.h - 1.9 linux/include/linux/umsdos_fs_i.h - 1.5 linux/include/linux/umsdos_fs.p - 1.7 linux/include/linux/udp.h - 1.5 linux/include/linux/tty.h - 1.19 linux/include/linux/time.h - 1.9 linux/include/linux/sysctl.h - 1.67 linux/include/linux/swap.h - 1.69 linux/include/linux/sunrpc/xdr.h - 1.11 linux/include/linux/sunrpc/stats.h - 1.5 linux/include/linux/sunrpc/sched.h - 1.14 linux/include/linux/sunrpc/clnt.h - 1.13 linux/include/linux/string.h - 1.11 linux/include/linux/stat.h - 1.4 linux/include/linux/soundmodem.h - 1.3 linux/include/linux/smb.h - 1.10 linux/include/linux/signal.h - 1.9 linux/include/linux/serial.h - 1.17 linux/include/linux/sem.h - 1.10 linux/include/linux/sched.h - 1.93 linux/include/linux/reboot.h - 1.5 linux/include/linux/poll.h - 1.7 linux/include/linux/pci.h - 1.69 linux/include/linux/parport.h - 1.24 linux/include/linux/nfsd/nfsfh.h - 1.17 linux/include/linux/nfsd/cache.h - 1.5 linux/include/linux/nfs_fs.h - 1.30 linux/include/linux/netlink.h - 1.11 linux/include/linux/netdevice.h - 1.40 linux/include/linux/ncp_fs_sb.h - 1.10 linux/include/linux/nbd.h - 1.20 linux/include/linux/msdos_fs_sb.h - 1.12 linux/include/linux/msdos_fs.h - 1.25 linux/include/linux/mroute.h - 1.6 linux/include/linux/module.h - 1.39 linux/include/linux/mm.h - 1.109 linux/include/linux/mca.h - 1.5 linux/include/linux/major.h - 1.30 linux/include/linux/lockd/debug.h - 1.4 linux/include/linux/kmod.h - 1.10 linux/include/linux/kernel_stat.h - 1.14 linux/include/linux/kernel.h - 1.40 linux/include/linux/isdnif.h - 1.17 linux/include/linux/isdn.h - 1.31 linux/include/linux/interrupt.h - 1.25 linux/include/linux/init.h - 1.22 linux/include/linux/in.h - 1.8 linux/include/linux/i2c.h - 1.16 linux/include/linux/hfs_sysdep.h - 1.12 linux/include/linux/hdlcdrv.h - 1.10 linux/include/linux/ftape.h - 1.4 linux/include/linux/fs.h - 1.200 linux/include/linux/file.h - 1.16 linux/include/linux/fb.h - 1.27 linux/include/linux/ext2_fs.h - 1.24 linux/include/linux/errno.h - 1.5 linux/include/linux/elf.h - 1.18 linux/include/linux/dcache.h - 1.31 linux/include/linux/console_struct.h - 1.6 linux/include/linux/console.h - 1.10 linux/include/linux/coda_psdev.h - 1.9 linux/include/linux/coda_linux.h - 1.17 linux/include/linux/blkdev.h - 1.79 linux/include/linux/binfmts.h - 1.14 linux/include/linux/amigaffs.h - 1.12 linux/include/linux/acct.h - 1.4 linux/include/asm-sparc64/unistd.h - 1.29 linux/include/asm-sparc64/ttable.h - 1.10 linux/include/asm-sparc64/system.h - 1.26 linux/include/asm-sparc64/stat.h - 1.5 linux/include/asm-sparc64/signal.h - 1.6 linux/include/asm-sparc64/processor.h - 1.27 linux/include/asm-sparc64/posix_types.h - 1.6 linux/include/asm-sparc64/irq.h - 1.16 linux/include/asm-sparc64/floppy.h - 1.17 linux/include/asm-sparc64/elf.h - 1.16 linux/include/asm-sparc64/current.h - 1.5 linux/include/asm-sparc/vaddrs.h - 1.8 linux/include/asm-sparc/unistd.h - 1.27 linux/include/asm-sparc/system.h - 1.17 linux/include/asm-sparc/stat.h - 1.6 linux/include/asm-sparc/processor.h - 1.21 linux/include/asm-sparc/pgtsrmmu.h - 1.6 linux/include/asm-sparc/page.h - 1.18 linux/include/asm-sparc/irq.h - 1.11 linux/include/asm-sparc/io.h - 1.12 linux/include/asm-sparc/hardirq.h - 1.16 linux/include/asm-sparc/elf.h - 1.7 linux/include/asm-sparc/current.h - 1.4 linux/include/asm-ppc/unistd.h - 1.29 linux/include/asm-ppc/stat.h - 1.9 linux/include/asm-ppc/processor.h - 1.37 linux/include/asm-ppc/page.h - 1.19 linux/include/asm-ppc/hardirq.h - 1.23 linux/include/asm-ppc/errno.h - 1.6 linux/include/asm-ppc/atomic.h - 1.13 linux/include/asm-mips/stat.h - 1.6 linux/include/asm-m68k/stat.h - 1.8 linux/include/asm-m68k/signal.h - 1.5 linux/include/asm-i386/unistd.h - 1.32 linux/include/asm-i386/uaccess.h - 1.17 linux/include/asm-i386/system.h - 1.29 linux/include/asm-i386/string.h - 1.13 linux/include/asm-i386/string-486.h - 1.9 linux/include/asm-i386/stat.h - 1.5 linux/include/asm-i386/signal.h - 1.7 linux/include/asm-i386/processor.h - 1.46 linux/include/asm-i386/pgtable.h - 1.40 linux/include/asm-i386/msr.h - 1.16 linux/include/asm-i386/ipc.h - 1.3 linux/include/asm-i386/desc.h - 1.15 linux/include/asm-i386/current.h - 1.4 linux/include/asm-i386/bitops.h - 1.17 linux/include/asm-arm/unistd.h - 1.25 linux/include/asm-arm/stat.h - 1.8 linux/include/asm-arm/signal.h - 1.6 linux/include/asm-arm/proc-armv/pgtable.h - 1.19 linux/include/asm-arm/proc-armv/elf.h - 1.7 linux/include/asm-arm/ecard.h - 1.5 linux/include/asm-arm/bitops.h - 1.13 linux/include/asm-arm/arch-rpc/memory.h - 1.9 linux/include/asm-arm/arch-nexuspci/memory.h - 1.9 linux/include/asm-arm/arch-ebsa285/memory.h - 1.12 linux/include/asm-arm/arch-ebsa110/memory.h - 1.10 linux/include/asm-alpha/unistd.h - 1.26 linux/include/asm-alpha/processor.h - 1.18 linux/include/asm-alpha/hardirq.h - 1.16 linux/include/asm-alpha/current.h - 1.4 linux/include/asm-alpha/core_cia.h - 1.12 linux/fs/vfat/namei.c - 1.38 linux/fs/vfat/Makefile - 1.5 linux/fs/umsdos/namei.c - 1.16 linux/fs/umsdos/ioctl.c - 1.10 linux/fs/umsdos/Makefile - 1.9 linux/fs/ufs/super.c - 1.39 linux/fs/ufs/namei.c - 1.20 linux/fs/ufs/inode.c - 1.28 linux/fs/ufs/ialloc.c - 1.17 linux/fs/ufs/balloc.c - 1.17 linux/fs/ufs/Makefile - 1.6 linux/fs/sysv/namei.c - 1.21 linux/fs/sysv/inode.c - 1.35 linux/fs/sysv/balloc.c - 1.10 linux/fs/sysv/Makefile - 1.8 linux/fs/super.c - 1.94 linux/fs/stat.c - 1.30 linux/fs/smbfs/sock.c - 1.17 linux/fs/smbfs/proc.c - 1.24 linux/fs/smbfs/ioctl.c - 1.11 linux/fs/smbfs/inode.c - 1.44 linux/fs/smbfs/file.c - 1.34 linux/fs/smbfs/dir.c - 1.26 linux/fs/smbfs/cache.c - 1.16 linux/fs/smbfs/Makefile - 1.11 linux/fs/select.c - 1.21 linux/fs/romfs/inode.c - 1.41 linux/fs/romfs/Makefile - 1.5 linux/fs/readdir.c - 1.18 linux/fs/read_write.c - 1.30 linux/fs/qnx4/inode.c - 1.40 linux/fs/qnx4/Makefile - 1.6 linux/fs/proc/inode.c - 1.27 linux/fs/proc/generic.c - 1.34 linux/fs/proc/base.c - 1.45 linux/fs/proc/array.c - 1.52 linux/fs/proc/Makefile - 1.12 linux/fs/pipe.c - 1.38 linux/fs/open.c - 1.45 linux/fs/ntfs/inode.c - 1.25 linux/fs/ntfs/Makefile - 1.26 linux/fs/nls/Makefile - 1.11 linux/fs/nfsd/vfs.c - 1.61 linux/fs/nfsd/nfsxdr.c - 1.20 linux/fs/nfsd/nfsfh.c - 1.47 linux/fs/nfsd/nfscache.c - 1.13 linux/fs/nfsd/nfs3xdr.c - 1.33 linux/fs/nfsd/lockd.c - 1.13 linux/fs/nfsd/export.c - 1.45 linux/fs/nfsd/Makefile - 1.7 linux/fs/nfs/write.c - 1.46 linux/fs/nfs/proc.c - 1.20 linux/fs/nfs/nfs3xdr.c - 1.19 linux/fs/nfs/nfs2xdr.c - 1.23 linux/fs/nfs/mount_clnt.c - 1.10 linux/fs/nfs/inode.c - 1.59 linux/fs/nfs/dir.c - 1.47 linux/fs/nfs/Makefile - 1.12 linux/fs/ncpfs/ncplib_kernel.h - 1.11 linux/fs/ncpfs/inode.c - 1.40 linux/fs/ncpfs/dir.c - 1.33 linux/fs/ncpfs/Makefile - 1.7 linux/fs/namei.c - 1.63 linux/fs/msdos/namei.c - 1.36 linux/fs/msdos/Makefile - 1.5 linux/fs/minix/namei.c - 1.23 linux/fs/minix/inode.c - 1.38 linux/fs/minix/Makefile - 1.7 linux/fs/locks.c - 1.36 linux/fs/lockd/xdr.c - 1.17 linux/fs/lockd/mon.c - 1.12 linux/fs/lockd/clntproc.c - 1.18 linux/fs/lockd/Makefile - 1.6 linux/fs/isofs/rock.c - 1.24 linux/fs/isofs/inode.c - 1.41 linux/fs/isofs/Makefile - 1.9 linux/fs/ioctl.c - 1.17 linux/fs/inode.c - 1.87 linux/fs/hpfs/Makefile - 1.6 linux/fs/hfs/sysdep.c - 1.9 linux/fs/hfs/inode.c - 1.20 linux/fs/hfs/file_hdr.c - 1.17 linux/fs/hfs/file_cap.c - 1.16 linux/fs/hfs/file.c - 1.22 linux/fs/hfs/Makefile - 1.5 linux/fs/filesystems.c - 1.24 linux/fs/file_table.c - 1.28 linux/fs/fifo.c - 1.18 linux/fs/fcntl.c - 1.29 linux/fs/fat/inode.c - 1.53 linux/fs/fat/dir.c - 1.23 linux/fs/fat/Makefile - 1.8 linux/fs/ext2/super.c - 1.40 linux/fs/ext2/namei.c - 1.29 linux/fs/ext2/ioctl.c - 1.13 linux/fs/ext2/inode.c - 1.61 linux/fs/ext2/ialloc.c - 1.32 linux/fs/ext2/dir.c - 1.26 linux/fs/ext2/balloc.c - 1.24 linux/fs/ext2/Makefile - 1.8 linux/fs/exec.c - 1.73 linux/fs/dquot.c - 1.64 linux/fs/devpts/inode.c - 1.20 linux/fs/devpts/Makefile - 1.6 linux/fs/devices.c - 1.22 linux/fs/dcache.c - 1.44 linux/fs/coda/upcall.c - 1.20 linux/fs/coda/psdev.c - 1.25 linux/fs/coda/dir.c - 1.29 linux/fs/coda/coda_linux.c - 1.12 linux/fs/coda/Makefile - 1.5 linux/fs/buffer.c - 1.143 linux/fs/block_dev.c - 1.69 linux/fs/binfmt_misc.c - 1.28 linux/fs/binfmt_elf.c - 1.50 linux/fs/bad_inode.c - 1.15 linux/fs/autofs/root.c - 1.21 linux/fs/autofs/inode.c - 1.16 linux/fs/autofs/autofs_i.h - 1.14 linux/fs/autofs/Makefile - 1.6 linux/fs/attr.c - 1.20 linux/fs/affs/super.c - 1.29 linux/fs/affs/inode.c - 1.24 linux/fs/affs/file.c - 1.33 linux/fs/affs/Makefile - 1.6 linux/fs/adfs/inode.c - 1.29 linux/fs/adfs/Makefile - 1.6 linux/fs/Makefile - 1.75 linux/drivers/zorro/proc.c - 1.15 linux/drivers/zorro/Makefile - 1.13 linux/drivers/video/virgefb.c - 1.19 linux/drivers/video/vgacon.c - 1.20 linux/drivers/video/vfb.c - 1.19 linux/drivers/video/vesafb.c - 1.26 linux/drivers/video/valkyriefb.c - 1.20 linux/drivers/video/tgafb.c - 1.21 linux/drivers/video/skeletonfb.c - 1.14 linux/drivers/video/sgivwfb.c - 1.18 linux/drivers/video/sbusfb.c - 1.25 linux/drivers/video/retz3fb.c - 1.20 linux/drivers/video/q40fb.c - 1.16 linux/drivers/video/promcon.c - 1.10 linux/drivers/video/prom.uni - 1.3 linux/drivers/video/pm2fb.c - 1.18 linux/drivers/video/platinumfb.c - 1.19 linux/drivers/video/offb.c - 1.24 linux/drivers/video/newport_con.c - 1.11 linux/drivers/video/mdacon.c - 1.12 linux/drivers/video/macmodes.c - 1.11 linux/drivers/video/macfb.c - 1.17 linux/drivers/video/imsttfb.c - 1.26 linux/drivers/video/igafb.c - 1.20 linux/drivers/video/iga.h - 1.4 linux/drivers/video/hpfb.c - 1.18 linux/drivers/video/g364fb.c - 1.15 linux/drivers/video/fonts.c - 1.7 linux/drivers/video/font_sun8x16.c - 1.3 linux/drivers/video/font_sun12x22.c - 1.3 linux/drivers/video/font_pearl_8x8.c - 1.3 linux/drivers/video/font_acorn_8x8.c - 1.3 linux/drivers/video/font_8x8.c - 1.3 linux/drivers/video/font_8x16.c - 1.3 linux/drivers/video/font_6x11.c - 1.4 linux/drivers/video/fm2fb.c - 1.18 linux/drivers/video/fbmem.c - 1.55 linux/drivers/video/fbgen.c - 1.12 linux/drivers/video/fbcon.c - 1.31 linux/drivers/video/fbcon-mfb.c - 1.9 linux/drivers/video/fbcon-iplan2p8.c - 1.9 linux/drivers/video/fbcon-iplan2p4.c - 1.9 linux/drivers/video/fbcon-iplan2p2.c - 1.9 linux/drivers/video/fbcon-ilbm.c - 1.9 linux/drivers/video/fbcon-cfb8.c - 1.9 linux/drivers/video/fbcon-cfb4.c - 1.9 linux/drivers/video/fbcon-cfb32.c - 1.9 linux/drivers/video/fbcon-cfb24.c - 1.9 linux/drivers/video/fbcon-cfb2.c - 1.9 linux/drivers/video/fbcon-cfb16.c - 1.9 linux/drivers/video/fbcon-afb.c - 1.9 linux/drivers/video/fbcmap.c - 1.8 linux/drivers/video/dummycon.c - 1.10 linux/drivers/video/dnfb.c - 1.18 linux/drivers/video/cyberfb.c - 1.19 linux/drivers/video/controlfb.c - 1.25 linux/drivers/video/chipsfb.c - 1.22 linux/drivers/video/atafb.c - 1.19 linux/drivers/video/amifb.c - 1.26 linux/drivers/video/S3triofb.c - 1.15 linux/drivers/video/Makefile - 1.47 linux/drivers/usb/Makefile - 1.58 linux/drivers/sgi/char/usema.c - 1.9 linux/drivers/sgi/char/streamable.c - 1.9 linux/drivers/sgi/char/shmiq.c - 1.20 linux/drivers/sgi/char/sgiserial.c - 1.14 linux/drivers/sgi/char/graphics.c - 1.20 linux/drivers/sgi/char/Makefile - 1.7 linux/drivers/sgi/Makefile - 1.7 linux/drivers/scsi/wd7000.h - 1.9 linux/drivers/scsi/wd7000.c - 1.21 linux/drivers/scsi/wd33c93.c - 1.10 linux/drivers/scsi/ultrastor.h - 1.6 linux/drivers/scsi/ultrastor.c - 1.17 linux/drivers/scsi/u14-34f.h - 1.16 linux/drivers/scsi/u14-34f.c - 1.28 linux/drivers/scsi/tmscsim.c - 1.20 linux/drivers/scsi/t128.h - 1.8 linux/drivers/scsi/t128.c - 1.13 linux/drivers/scsi/sym53c8xx.h - 1.13 linux/drivers/scsi/sym53c8xx.c - 1.38 linux/drivers/scsi/st.c - 1.59 linux/drivers/scsi/sr_ioctl.c - 1.31 linux/drivers/scsi/sr.c - 1.60 linux/drivers/scsi/sgiwd93.h - 1.7 linux/drivers/scsi/sg.c - 1.45 linux/drivers/scsi/seagate.h - 1.7 linux/drivers/scsi/seagate.c - 1.22 linux/drivers/scsi/sd.c - 1.80 linux/drivers/scsi/scsi_syms.c - 1.25 linux/drivers/scsi/scsi_proc.c - 1.13 linux/drivers/scsi/scsi_ioctl.c - 1.27 linux/drivers/scsi/scsi_error.c - 1.35 linux/drivers/scsi/scsi_debug.h - 1.12 linux/drivers/scsi/scsi_debug.c - 1.27 linux/drivers/scsi/scsi.h - 1.41 linux/drivers/scsi/scsi.c - 1.67 linux/drivers/scsi/qlogicpti.c - 1.24 linux/drivers/scsi/qlogicisp.h - 1.6 linux/drivers/scsi/qlogicisp.c - 1.31 linux/drivers/scsi/qlogicfc.h - 1.13 linux/drivers/scsi/qlogicfc.c - 1.32 linux/drivers/scsi/qlogicfas.h - 1.6 linux/drivers/scsi/qlogicfas.c - 1.19 linux/drivers/scsi/psi240i.h - 1.7 linux/drivers/scsi/psi240i.c - 1.11 linux/drivers/scsi/ppa.h - 1.13 linux/drivers/scsi/ppa.c - 1.21 linux/drivers/scsi/pluto.h - 1.6 linux/drivers/scsi/pluto.c - 1.16 linux/drivers/scsi/pci2220i.h - 1.10 linux/drivers/scsi/pci2220i.c - 1.26 linux/drivers/scsi/pci2000.h - 1.9 linux/drivers/scsi/pci2000.c - 1.23 linux/drivers/scsi/pas16.h - 1.7 linux/drivers/scsi/pas16.c - 1.14 linux/drivers/scsi/ncr53c8xx.h - 1.9 linux/drivers/scsi/ncr53c8xx.c - 1.29 linux/drivers/scsi/mvme16x.h - 1.6 linux/drivers/scsi/mesh.h - 1.8 linux/drivers/scsi/megaraid.h - 1.18 linux/drivers/scsi/megaraid.c - 1.40 linux/drivers/scsi/mca_53c9x.h - 1.4 linux/drivers/scsi/mca_53c9x.c - 1.11 linux/drivers/scsi/mac_scsi.h - 1.5 linux/drivers/scsi/mac_esp.h - 1.5 linux/drivers/scsi/mac53c94.h - 1.7 linux/drivers/scsi/jazz_esp.h - 1.5 linux/drivers/scsi/inia100.h - 1.14 linux/drivers/scsi/inia100.c - 1.24 linux/drivers/scsi/ini9100u.h - 1.13 linux/drivers/scsi/ini9100u.c - 1.21 linux/drivers/scsi/in2000.h - 1.13 linux/drivers/scsi/in2000.c - 1.15 linux/drivers/scsi/imm.h - 1.12 linux/drivers/scsi/imm.c - 1.21 linux/drivers/scsi/ide-scsi.c - 1.49 linux/drivers/scsi/ibmmca.h - 1.10 linux/drivers/scsi/ibmmca.c - 1.21 linux/drivers/scsi/i60uscsi.c - 1.9 linux/drivers/scsi/hosts.h - 1.32 linux/drivers/scsi/hosts.c - 1.37 linux/drivers/scsi/gvp11.h - 1.4 linux/drivers/scsi/gdth_proc.c - 1.14 linux/drivers/scsi/gdth.h - 1.11 linux/drivers/scsi/gdth.c - 1.23 linux/drivers/scsi/g_NCR5380.h - 1.10 linux/drivers/scsi/g_NCR5380.c - 1.18 linux/drivers/scsi/fdomain.h - 1.8 linux/drivers/scsi/fdomain.c - 1.25 linux/drivers/scsi/fd_mcs.h - 1.7 linux/drivers/scsi/fd_mcs.c - 1.11 linux/drivers/scsi/fcal.h - 1.6 linux/drivers/scsi/fcal.c - 1.12 linux/drivers/scsi/fastlane.h - 1.5 linux/drivers/scsi/esp.c - 1.29 linux/drivers/scsi/eata_pio_proc.c - 1.3 linux/drivers/scsi/eata_pio.h - 1.5 linux/drivers/scsi/eata_pio.c - 1.18 linux/drivers/scsi/eata_dma_proc.c - 1.8 linux/drivers/scsi/eata_dma.h - 1.5 linux/drivers/scsi/eata.h - 1.16 linux/drivers/scsi/eata.c - 1.31 linux/drivers/scsi/dtc.h - 1.7 linux/drivers/scsi/dtc.c - 1.13 linux/drivers/scsi/dc390.h - 1.9 linux/drivers/scsi/cyberstormII.h - 1.5 linux/drivers/scsi/cyberstorm.h - 1.5 linux/drivers/scsi/bvme6000.h - 1.6 linux/drivers/scsi/blz2060.h - 1.5 linux/drivers/scsi/blz1230.h - 1.5 linux/drivers/scsi/atp870u.h - 1.9 linux/drivers/scsi/atp870u.c - 1.24 linux/drivers/scsi/atari_scsi.h - 1.5 linux/drivers/scsi/amiga7xx.h - 1.6 linux/drivers/scsi/aha1740.h - 1.7 linux/drivers/scsi/aha1740.c - 1.14 linux/drivers/scsi/aha1542.h - 1.9 linux/drivers/scsi/aha1542.c - 1.30 linux/drivers/scsi/aha152x.h - 1.11 linux/drivers/scsi/aha152x.c - 1.34 linux/drivers/scsi/advansys.h - 1.10 linux/drivers/scsi/advansys.c - 1.31 linux/drivers/scsi/a3000.h - 1.6 linux/drivers/scsi/a2091.h - 1.6 linux/drivers/scsi/README.tmscsim - 1.5 linux/drivers/scsi/README.st - 1.12 linux/drivers/scsi/README.qlogicisp - 1.3 linux/drivers/scsi/README.qlogicfas - 1.3 linux/drivers/scsi/README.ppa - 1.3 linux/drivers/scsi/README.ncr53c8xx - 1.7 linux/drivers/scsi/README.ncr53c7xx - 1.3 linux/drivers/scsi/README.in2000 - 1.3 linux/drivers/scsi/README.ibmmca - 1.7 linux/drivers/scsi/README.g_NCR5380 - 1.3 linux/drivers/scsi/README.dtc3x80 - 1.3 linux/drivers/scsi/README.aic7xxx - 1.7 linux/drivers/scsi/README.Mylex - 1.3 linux/drivers/scsi/README.FlashPoint - 1.3 linux/drivers/scsi/README.BusLogic - 1.3 linux/drivers/scsi/README.AM53C974 - 1.3 linux/drivers/scsi/NCR53c406a.c - 1.17 linux/drivers/scsi/NCR53C9x.c - 1.19 linux/drivers/scsi/NCR5380.c - 1.15 linux/drivers/scsi/Makefile - 1.45 linux/drivers/scsi/LICENSE.FlashPoint - 1.3 linux/drivers/scsi/ChangeLog.sym53c8xx - 1.14 linux/drivers/scsi/ChangeLog.ncr53c8xx - 1.12 linux/drivers/scsi/ChangeLog - 1.3 linux/drivers/scsi/BusLogic.h - 1.12 linux/drivers/scsi/BusLogic.c - 1.21 linux/drivers/scsi/AM53C974.h - 1.6 linux/drivers/scsi/53c7,8xx.h - 1.7 linux/drivers/sbus/char/vfc_dev.c - 1.17 linux/drivers/sbus/char/vfc.h - 1.4 linux/drivers/sbus/char/bpp.c - 1.23 linux/drivers/sbus/char/Makefile - 1.15 linux/drivers/sbus/Makefile - 1.10 linux/drivers/pnp/Makefile - 1.17 linux/drivers/pci/quirks.c - 1.33 linux/drivers/pci/proc.c - 1.31 linux/drivers/pci/pci.c - 1.64 linux/drivers/pci/compat.c - 1.11 linux/drivers/pci/Makefile - 1.28 linux/drivers/nubus/Makefile - 1.6 linux/drivers/net/znet.c - 1.13 linux/drivers/net/wd.c - 1.20 linux/drivers/net/via-rhine.c - 1.38 linux/drivers/net/sunqe.c - 1.23 linux/drivers/net/sunlance.c - 1.29 linux/drivers/net/sunhme.c - 1.40 linux/drivers/net/sunbmac.c - 1.24 linux/drivers/net/smc9194.c - 1.22 linux/drivers/net/smc-ultra32.c - 1.17 linux/drivers/net/smc-ultra.c - 1.24 linux/drivers/net/smc-mca.c - 1.16 linux/drivers/net/slip.c - 1.22 linux/drivers/net/slhc.c - 1.13 linux/drivers/net/sk_g16.c - 1.17 linux/drivers/net/shaper.c - 1.22 linux/drivers/net/sgiseeq.c - 1.18 linux/drivers/net/seeq8005.c - 1.16 linux/drivers/net/rrunner.h - 1.5 linux/drivers/net/rrunner.c - 1.22 linux/drivers/net/rcpci45.c - 1.25 linux/drivers/net/plip.c - 1.26 linux/drivers/net/pcnet32.c - 1.38 linux/drivers/net/ni65.c - 1.18 linux/drivers/net/ni52.c - 1.18 linux/drivers/net/net_init.c - 1.22 linux/drivers/net/ne3210.c - 1.17 linux/drivers/net/ne2k-pci.c - 1.26 linux/drivers/net/ne2.c - 1.18 linux/drivers/net/ne.c - 1.22 linux/drivers/net/myri_sbus.c - 1.17 linux/drivers/net/lne390.c - 1.18 linux/drivers/net/lance.c - 1.27 linux/drivers/net/irda/w83977af_ir.c - 1.27 linux/drivers/net/irda/tekram.c - 1.12 linux/drivers/net/irda/girbil.c - 1.13 linux/drivers/net/irda/esi.c - 1.10 linux/drivers/net/irda/actisys.c - 1.13 linux/drivers/net/irda/Makefile - 1.22 linux/drivers/net/hydra.c - 1.17 linux/drivers/net/hplance.c - 1.13 linux/drivers/net/hp100.c - 1.24 linux/drivers/net/hp.c - 1.16 linux/drivers/net/hp-plus.c - 1.19 linux/drivers/net/hamradio/soundmodem/smdma.h - 1.4 linux/drivers/net/hamradio/soundmodem/sm_wss.c - 1.9 linux/drivers/net/hamradio/soundmodem/sm_sbc.c - 1.8 linux/drivers/net/hamradio/soundmodem/sm_psk4800.c - 1.3 linux/drivers/net/hamradio/soundmodem/sm_hapn4800.c - 1.3 linux/drivers/net/hamradio/soundmodem/sm_fsk9600.c - 1.3 linux/drivers/net/hamradio/soundmodem/sm_afsk2666.c - 1.4 linux/drivers/net/hamradio/soundmodem/sm_afsk2400_8.c - 1.4 linux/drivers/net/hamradio/soundmodem/sm_afsk2400_7.c - 1.4 linux/drivers/net/hamradio/soundmodem/sm_afsk1200.c - 1.4 linux/drivers/net/hamradio/soundmodem/sm.h - 1.10 linux/drivers/net/hamradio/soundmodem/sm.c - 1.14 linux/drivers/net/hamradio/soundmodem/gentbl.c - 1.4 linux/drivers/net/hamradio/soundmodem/Makefile - 1.10 linux/drivers/net/hamradio/scc.c - 1.28 linux/drivers/net/hamradio/dmascc.c - 1.13 linux/drivers/net/hamradio/baycom_par.c - 1.17 linux/drivers/net/hamradio/baycom_epp.c - 1.24 linux/drivers/net/hamradio/Makefile - 1.11 linux/drivers/net/fmv18x.c - 1.18 linux/drivers/net/ewrk3.c - 1.26 linux/drivers/net/eth16i.c - 1.22 linux/drivers/net/es3210.c - 1.18 linux/drivers/net/eexpress.c - 1.21 linux/drivers/net/eepro100.c - 1.53 linux/drivers/net/eepro.c - 1.28 linux/drivers/net/e2100.c - 1.18 linux/drivers/net/dgrs.c - 1.22 linux/drivers/net/depca.c - 1.23 linux/drivers/net/defxx.c - 1.24 linux/drivers/net/de620.c - 1.17 linux/drivers/net/de600.c - 1.20 linux/drivers/net/cs89x0.c - 1.27 linux/drivers/net/atp.c - 1.21 linux/drivers/net/atarilance.c - 1.14 linux/drivers/net/at1700.c - 1.22 linux/drivers/net/ariadne2.c - 1.13 linux/drivers/net/ariadne.c - 1.17 linux/drivers/net/apne.c - 1.12 linux/drivers/net/am79c961a.c - 1.15 linux/drivers/net/ac3200.c - 1.20 linux/drivers/net/a2065.c - 1.19 linux/drivers/net/Space.c - 1.38 linux/drivers/net/Makefile - 1.65 linux/drivers/net/82596.c - 1.22 linux/drivers/net/7990.c - 1.10 linux/drivers/net/3c59x.c - 1.42 linux/drivers/net/3c527.c - 1.20 linux/drivers/net/3c523.c - 1.17 linux/drivers/net/3c515.c - 1.25 linux/drivers/net/3c509.c - 1.38 linux/drivers/net/3c507.c - 1.23 linux/drivers/net/3c505.c - 1.31 linux/drivers/net/3c503.c - 1.24 linux/drivers/net/3c501.c - 1.22 linux/drivers/misc/Makefile - 1.12 linux/drivers/macintosh/via-pmu.c - 1.22 linux/drivers/macintosh/nvram.c - 1.12 linux/drivers/macintosh/mediabay.c - 1.15 linux/drivers/macintosh/macserial.c - 1.25 linux/drivers/macintosh/adb.c - 1.21 linux/drivers/macintosh/Makefile - 1.17 linux/drivers/isdn/sc/init.c - 1.8 linux/drivers/isdn/sc/command.c - 1.8 linux/drivers/isdn/pcbit/drv.c - 1.16 linux/drivers/isdn/pcbit/capi.h - 1.5 linux/drivers/isdn/isdnloop/isdnloop.c - 1.17 linux/drivers/isdn/icn/icn.c - 1.21 linux/drivers/isdn/hisax/teles3.c - 1.17 linux/drivers/isdn/hisax/teles0.c - 1.15 linux/drivers/isdn/hisax/teleint.c - 1.14 linux/drivers/isdn/hisax/sportster.c - 1.14 linux/drivers/isdn/hisax/sedlbauer.c - 1.21 linux/drivers/isdn/hisax/niccy.c - 1.19 linux/drivers/isdn/hisax/netjet.c - 1.24 linux/drivers/isdn/hisax/mic.c - 1.13 linux/drivers/isdn/hisax/ix1_micro.c - 1.14 linux/drivers/isdn/hisax/isdnl2.c - 1.16 linux/drivers/isdn/hisax/isdnl1.h - 1.7 linux/drivers/isdn/hisax/isdnl1.c - 1.19 linux/drivers/isdn/hisax/isac.h - 1.7 linux/drivers/isdn/hisax/isac.c - 1.16 linux/drivers/isdn/hisax/hscx_irq.c - 1.10 linux/drivers/isdn/hisax/hscx.h - 1.7 linux/drivers/isdn/hisax/hscx.c - 1.15 linux/drivers/isdn/hisax/hisax.h - 1.32 linux/drivers/isdn/hisax/hfc_2bs0.c - 1.18 linux/drivers/isdn/hisax/hfc_2bds0.c - 1.18 linux/drivers/isdn/hisax/elsa.c - 1.22 linux/drivers/isdn/hisax/diva.c - 1.18 linux/drivers/isdn/hisax/config.c - 1.34 linux/drivers/isdn/hisax/callc.c - 1.20 linux/drivers/isdn/hisax/avm_a1.c - 1.14 linux/drivers/isdn/hisax/asuscom.c - 1.17 linux/drivers/isdn/hisax/amd7930.c - 1.15 linux/drivers/isdn/act2000/module.c - 1.12 linux/drivers/fc4/fc.c - 1.14 linux/drivers/fc4/Makefile - 1.9 linux/drivers/dio/Makefile - 1.4 linux/drivers/char/wdt.c - 1.18 linux/drivers/char/wd501p.h - 1.5 linux/drivers/char/vt.c - 1.30 linux/drivers/char/vc_screen.c - 1.16 linux/drivers/char/tty_io.c - 1.58 linux/drivers/char/tpqic02.c - 1.25 linux/drivers/char/sysrq.c - 1.33 linux/drivers/char/synclink.c - 1.31 linux/drivers/char/stallion.c - 1.26 linux/drivers/char/softdog.c - 1.17 linux/drivers/char/selection.c - 1.7 linux/drivers/char/rtc.c - 1.34 linux/drivers/char/rocket.c - 1.21 linux/drivers/char/random.c - 1.36 linux/drivers/char/pcwd.c - 1.21 linux/drivers/char/mem.c - 1.50 linux/drivers/char/lp.c - 1.36 linux/drivers/char/keyboard.c - 1.31 linux/drivers/char/istallion.c - 1.26 linux/drivers/char/isicom.c - 1.23 linux/drivers/char/ftape/zftape/zftape-init.h - 1.3 linux/drivers/char/ftape/zftape/zftape-init.c - 1.15 linux/drivers/char/ftape/zftape/zftape-ctl.c - 1.5 linux/drivers/char/ftape/zftape/Makefile - 1.5 linux/drivers/char/ftape/lowlevel/ftape-init.h - 1.4 linux/drivers/char/ftape/lowlevel/Makefile - 1.7 linux/drivers/char/ftape/compressor/zftape-compress.c - 1.7 linux/drivers/char/ftape/compressor/Makefile - 1.5 linux/drivers/char/ftape/Makefile - 1.5 linux/drivers/char/epca.c - 1.24 linux/drivers/char/dtlk.c - 1.21 linux/drivers/char/dsp56k.c - 1.22 linux/drivers/char/cyclades.c - 1.26 linux/drivers/char/consolemap.c - 1.5 linux/drivers/char/acquirewdt.c - 1.20 linux/drivers/char/Makefile - 1.79 linux/drivers/cdrom/sonycd535.c - 1.33 linux/drivers/cdrom/sjcd.c - 1.28 linux/drivers/cdrom/sbpcd.c - 1.34 linux/drivers/cdrom/optcd.c - 1.29 linux/drivers/cdrom/mcdx.c - 1.24 linux/drivers/cdrom/mcd.c - 1.29 linux/drivers/cdrom/gscd.c - 1.29 linux/drivers/cdrom/cm206.c - 1.30 linux/drivers/cdrom/aztcd.c - 1.31 linux/drivers/cdrom/Makefile - 1.7 linux/drivers/block/z2ram.c - 1.25 linux/drivers/block/xd.c - 1.51 linux/drivers/block/swim3.c - 1.26 linux/drivers/block/rd.c - 1.69 linux/drivers/block/ps2esdi.c - 1.55 linux/drivers/block/paride/pt.c - 1.20 linux/drivers/block/paride/pseudo.h - 1.10 linux/drivers/block/paride/pg.c - 1.20 linux/drivers/block/paride/pf.c - 1.34 linux/drivers/block/paride/pd.c - 1.42 linux/drivers/block/paride/pcd.c - 1.30 linux/drivers/block/paride/paride.h - 1.4 linux/drivers/block/paride/paride.c - 1.15 linux/drivers/block/paride/on26.c - 1.8 linux/drivers/block/paride/on20.c - 1.7 linux/drivers/block/paride/ktti.c - 1.7 linux/drivers/block/paride/kbic.c - 1.7 linux/drivers/block/paride/frpw.c - 1.7 linux/drivers/block/paride/friq.c - 1.7 linux/drivers/block/paride/fit3.c - 1.7 linux/drivers/block/paride/fit2.c - 1.7 linux/drivers/block/paride/epia.c - 1.7 linux/drivers/block/paride/epat.c - 1.9 linux/drivers/block/paride/dstr.c - 1.7 linux/drivers/block/paride/comm.c - 1.7 linux/drivers/block/paride/bpck.c - 1.7 linux/drivers/block/paride/aten.c - 1.7 linux/drivers/block/paride/Makefile - 1.11 linux/drivers/block/nbd.c - 1.49 linux/drivers/block/loop.c - 1.76 linux/drivers/block/ll_rw_blk.c - 1.124 linux/drivers/block/genhd.c - 1.43 linux/drivers/block/floppy.c - 1.60 linux/drivers/block/ataflop.c - 1.35 linux/drivers/block/amiflop.c - 1.35 linux/drivers/block/acsi_slm.c - 1.13 linux/drivers/block/acsi.c - 1.44 linux/drivers/block/Makefile - 1.31 linux/drivers/acorn/scsi/queue.h - 1.6 linux/drivers/acorn/scsi/queue.c - 1.8 linux/drivers/acorn/scsi/powertec.c - 1.19 linux/drivers/acorn/scsi/oak.c - 1.14 linux/drivers/acorn/scsi/fas216.h - 1.7 linux/drivers/acorn/scsi/fas216.c - 1.15 linux/drivers/acorn/scsi/eesox.c - 1.19 linux/drivers/acorn/scsi/ecoscsi.c - 1.15 linux/drivers/acorn/scsi/cumana_2.c - 1.19 linux/drivers/acorn/scsi/cumana_1.c - 1.13 linux/drivers/acorn/scsi/acornscsi.c - 1.22 linux/drivers/acorn/scsi/Makefile - 1.10 linux/drivers/acorn/net/etherh.c - 1.19 linux/drivers/acorn/net/ether3.c - 1.16 linux/drivers/acorn/net/ether1.c - 1.16 linux/drivers/acorn/net/Makefile - 1.8 linux/drivers/acorn/char/Makefile - 1.16 linux/drivers/acorn/block/mfmhd.c - 1.36 linux/drivers/acorn/block/fd1772.c - 1.29 linux/drivers/acorn/block/Makefile - 1.10 linux/drivers/Makefile - 1.40 linux/arch/sparc64/solaris/timod.c - 1.22 linux/arch/sparc64/solaris/socksys.c - 1.19 linux/arch/sparc64/solaris/socket.c - 1.11 linux/arch/sparc64/solaris/misc.c - 1.28 linux/arch/sparc64/solaris/ioctl.c - 1.14 linux/arch/sparc64/solaris/fs.c - 1.21 linux/arch/sparc64/solaris/Makefile - 1.9 linux/arch/sparc64/prom/Makefile - 1.13 linux/arch/sparc64/mm/modutil.c - 1.12 linux/arch/sparc64/mm/init.c - 1.54 linux/arch/sparc64/mm/extable.c - 1.6 linux/arch/sparc64/mm/Makefile - 1.11 linux/arch/sparc64/math-emu/Makefile - 1.7 linux/arch/sparc64/lib/Makefile - 1.14 linux/arch/sparc64/kernel/time.c - 1.26 linux/arch/sparc64/kernel/systbls.S - 1.36 linux/arch/sparc64/kernel/sys_sunos32.c - 1.41 linux/arch/sparc64/kernel/sys_sparc32.c - 1.64 linux/arch/sparc64/kernel/sys32.S - 1.7 linux/arch/sparc64/kernel/sparc64_ksyms.c - 1.51 linux/arch/sparc64/kernel/smp.c - 1.50 linux/arch/sparc64/kernel/signal32.c - 1.30 linux/arch/sparc64/kernel/signal.c - 1.28 linux/arch/sparc64/kernel/setup.c - 1.36 linux/arch/sparc64/kernel/ptrace.c - 1.21 linux/arch/sparc64/kernel/process.c - 1.43 linux/arch/sparc64/kernel/ioctl32.c - 1.62 linux/arch/sparc64/kernel/head.S - 1.20 linux/arch/sparc64/kernel/entry.S - 1.28 linux/arch/sparc64/kernel/ebus.c - 1.19 linux/arch/sparc64/kernel/binfmt_elf32.c - 1.10 linux/arch/sparc64/kernel/Makefile - 1.27 linux/arch/sparc64/defconfig - 1.84 linux/arch/sparc64/boot/Makefile - 1.4 linux/arch/sparc64/Makefile - 1.24 linux/arch/sparc/prom/Makefile - 1.7 linux/arch/sparc/mm/sun4c.c - 1.40 linux/arch/sparc/mm/srmmu.c - 1.42 linux/arch/sparc/mm/iommu.c - 1.14 linux/arch/sparc/mm/io-unit.c - 1.14 linux/arch/sparc/mm/init.c - 1.33 linux/arch/sparc/mm/extable.c - 1.7 linux/arch/sparc/mm/Makefile - 1.13 linux/arch/sparc/math-emu/Makefile - 1.11 linux/arch/sparc/lib/Makefile - 1.13 linux/arch/sparc/kernel/tick14.c - 1.4 linux/arch/sparc/kernel/systbls.S - 1.29 linux/arch/sparc/kernel/sys_sunos.c - 1.39 linux/arch/sparc/kernel/sun4c_irq.c - 1.10 linux/arch/sparc/kernel/sparc_ksyms.c - 1.33 linux/arch/sparc/kernel/signal.c - 1.31 linux/arch/sparc/kernel/ptrace.c - 1.18 linux/arch/sparc/kernel/process.c - 1.33 linux/arch/sparc/kernel/irq.c - 1.26 linux/arch/sparc/kernel/ioport.c - 1.24 linux/arch/sparc/kernel/entry.S - 1.16 linux/arch/sparc/kernel/devices.c - 1.6 linux/arch/sparc/kernel/Makefile - 1.20 linux/arch/sparc/defconfig - 1.38 linux/arch/sparc/boot/Makefile - 1.11 linux/arch/sparc/Makefile - 1.21 linux/arch/ppc/mm/extable.c - 1.7 linux/arch/ppc/mm/Makefile - 1.14 linux/arch/ppc/lib/Makefile - 1.13 linux/arch/ppc/kernel/smp.c - 1.45 linux/arch/ppc/kernel/signal.c - 1.21 linux/arch/ppc/kernel/ptrace.c - 1.17 linux/arch/ppc/kernel/process.c - 1.45 linux/arch/ppc/kernel/misc.S - 1.52 linux/arch/ppc/kernel/head.S - 1.38 linux/arch/ppc/kernel/Makefile - 1.35 linux/arch/ppc/boot/Makefile - 1.21 linux/arch/ppc/amiga/amiints.c - 1.15 linux/arch/ppc/amiga/Makefile - 1.11 linux/arch/ppc/Makefile - 1.34 linux/arch/ppc/8xx_io/Makefile - 1.11 linux/arch/mips/tools/Makefile - 1.7 linux/arch/mips/sni/Makefile - 1.10 linux/arch/mips/sgi/kernel/Makefile - 1.12 linux/arch/mips/mm/Makefile - 1.9 linux/arch/mips/lib/rtc-no.c - 1.6 linux/arch/mips/lib/Makefile - 1.12 linux/arch/mips/kernel/sysirix.c - 1.19 linux/arch/mips/kernel/gdb-stub.c - 1.8 linux/arch/mips/kernel/Makefile - 1.13 linux/arch/mips/jazz/Makefile - 1.9 linux/arch/mips/boot/Makefile - 1.13 linux/arch/m68k/sun3x/Makefile - 1.7 linux/arch/m68k/q40/Makefile - 1.5 linux/arch/m68k/mvme16x/Makefile - 1.6 linux/arch/m68k/mvme147/Makefile - 1.5 linux/arch/m68k/mm/Makefile - 1.7 linux/arch/m68k/mac/Makefile - 1.7 linux/arch/m68k/lib/checksum.c - 1.5 linux/arch/m68k/lib/Makefile - 1.11 linux/arch/m68k/kernel/Makefile - 1.13 linux/arch/m68k/ifpsp060/Makefile - 1.8 linux/arch/m68k/hp300/Makefile - 1.7 linux/arch/m68k/fpsp040/Makefile - 1.8 linux/arch/m68k/bvme6000/Makefile - 1.5 linux/arch/m68k/atari/Makefile - 1.8 linux/arch/m68k/apollo/Makefile - 1.6 linux/arch/m68k/amiga/Makefile - 1.5 linux/arch/i386/mm/init.c - 1.49 linux/arch/i386/mm/fault.c - 1.30 linux/arch/i386/mm/extable.c - 1.6 linux/arch/i386/mm/Makefile - 1.12 linux/arch/i386/math-emu/Makefile - 1.9 linux/arch/i386/lib/Makefile - 1.20 linux/arch/i386/kernel/vm86.c - 1.21 linux/arch/i386/kernel/traps.c - 1.68 linux/arch/i386/kernel/sys_i386.c - 1.12 linux/arch/i386/kernel/signal.c - 1.30 linux/arch/i386/kernel/ptrace.c - 1.26 linux/arch/i386/kernel/process.c - 1.62 linux/arch/i386/kernel/mca.c - 1.17 linux/arch/i386/kernel/io_apic.c - 1.49 linux/arch/i386/kernel/head.S - 1.29 linux/arch/i386/kernel/entry.S - 1.69 linux/arch/i386/kernel/apm.c - 1.55 linux/arch/i386/kernel/Makefile - 1.41 linux/arch/i386/boot/compressed/Makefile - 1.14 linux/arch/i386/boot/Makefile - 1.20 linux/arch/i386/Makefile - 1.41 linux/arch/arm/mm/proc-sa110.S - 1.29 linux/arch/arm/mm/mm-armv.c - 1.32 linux/arch/arm/mm/init.c - 1.35 linux/arch/arm/mm/fault-armv.c - 1.29 linux/arch/arm/mm/extable.c - 1.5 linux/arch/arm/mm/Makefile - 1.23 linux/arch/arm/lib/Makefile - 1.26 linux/arch/arm/kernel/traps.c - 1.32 linux/arch/arm/kernel/time.c - 1.20 linux/arch/arm/kernel/sys_arm.c - 1.22 linux/arch/arm/kernel/setup.c - 1.38 linux/arch/arm/kernel/ptrace.c - 1.24 linux/arch/arm/kernel/process.c - 1.34 linux/arch/arm/kernel/irq.c - 1.25 linux/arch/arm/kernel/entry-armv.S - 1.38 linux/arch/arm/kernel/ecard.c - 1.24 linux/arch/arm/kernel/dma.c - 1.13 linux/arch/arm/kernel/dma-isa.c - 1.10 linux/arch/arm/kernel/calls.S - 1.20 linux/arch/arm/kernel/armksyms.c - 1.31 linux/arch/arm/kernel/Makefile - 1.24 linux/arch/arm/boot/compressed/Makefile - 1.26 linux/arch/arm/boot/Makefile - 1.22 linux/arch/arm/Makefile - 1.39 linux/arch/alpha/mm/init.c - 1.25 linux/arch/alpha/mm/Makefile - 1.5 linux/arch/alpha/math-emu/Makefile - 1.9 linux/arch/alpha/lib/stxncpy.S - 1.8 linux/arch/alpha/lib/io.c - 1.7 linux/arch/alpha/lib/Makefile - 1.20 linux/arch/alpha/kernel/time.c - 1.25 linux/arch/alpha/kernel/sys_sio.c - 1.17 linux/arch/alpha/kernel/sys_jensen.c - 1.14 linux/arch/alpha/kernel/smp.c - 1.39 linux/arch/alpha/kernel/smc37c669.c - 1.7 linux/arch/alpha/kernel/signal.c - 1.21 linux/arch/alpha/kernel/setup.c - 1.33 linux/arch/alpha/kernel/process.c - 1.32 linux/arch/alpha/kernel/osf_sys.c - 1.36 linux/arch/alpha/kernel/irq.c - 1.27 linux/arch/alpha/kernel/entry.S - 1.34 linux/arch/alpha/kernel/core_cia.c - 1.27 linux/arch/alpha/kernel/Makefile - 1.27 linux/arch/alpha/defconfig - 1.34 linux/Rules.make - 1.36 linux/Makefile - 1.233 linux/MAINTAINERS - 1.127 linux/Documentation/sysctl/kernel.txt - 1.6 linux/Documentation/scsi.txt - 1.5 linux/Documentation/scsi-generic.txt - 1.11 linux/Documentation/networking/soundmodem.txt - 1.5 linux/Documentation/networking/00-INDEX - 1.7 linux/Documentation/magic-number.txt - 1.5 linux/Documentation/filesystems/vfs.txt - 1.7 linux/Documentation/filesystems/vfat.txt - 1.8 linux/Documentation/fb/internals.txt - 1.4 linux/Documentation/devices.txt - 1.14 linux/Documentation/00-INDEX - 1.15 linux/CREDITS - 1.93 linux/net/decnet/af_decnet.c - 1.36 linux/net/decnet/Makefile - 1.10 linux/include/video/fbcon-vga-planes.h - 1.2 linux/include/linux/ide.h - 1.71 linux/fs/hpfs/super.c - 1.23 linux/fs/hpfs/namei.c - 1.19 linux/fs/hpfs/inode.c - 1.24 linux/fs/hpfs/hpfs_fn.h - 1.21 linux/fs/hpfs/file.c - 1.23 linux/fs/hpfs/dir.c - 1.17 linux/fs/efs/inode.c - 1.14 linux/fs/efs/Makefile - 1.4 linux/drivers/video/vga16fb.c - 1.17 linux/drivers/video/fbcon-vga-planes.c - 1.8 linux/drivers/net/sk_mca.c - 1.14 linux/drivers/net/irda/toshoboe.c - 1.32 linux/drivers/net/irda/litelink.c - 1.10 linux/drivers/isdn/hisax/telespci.c - 1.13 linux/drivers/isdn/hisax/s0box.c - 1.11 linux/drivers/isdn/hisax/isar.c - 1.21 linux/drivers/isdn/hisax/elsa_ser.c - 1.13 linux/drivers/isdn/hisax/avm_pci.c - 1.18 linux/drivers/isdn/hisax/avm_a1p.c - 1.11 linux/drivers/isdn/eicon/eicon_mod.c - 1.20 linux/drivers/acorn/scsi/arxescsi.h - 1.6 linux/drivers/acorn/scsi/arxescsi.c - 1.16 linux/arch/ppc/xmon/Makefile - 1.8 linux/arch/i386/vmlinux.lds.S - 1.14 linux/arch/arm/nwfpe/fpa11.c - 1.11 linux/arch/arm/nwfpe/Makefile - 1.9 linux/arch/arm/kernel/arthur.c - 1.9 linux/Documentation/kernel-parameters.txt - 1.20 linux/drivers/tc/zs.c - 1.11 linux/drivers/tc/Makefile - 1.6 linux/drivers/sgi/char/ds1286.c - 1.10 linux/drivers/net/jazzsonic.c - 1.11 linux/drivers/net/declance.c - 1.16 linux/drivers/net/bagetlance.c - 1.13 linux/arch/mips/dec/promcon.c - 1.5 linux/arch/mips/dec/prom/Makefile - 1.8 linux/arch/mips/dec/boot/Makefile - 1.6 linux/arch/mips/dec/Makefile - 1.8 linux/arch/mips/baget/vacserial.c - 1.13 linux/arch/mips/baget/prom/Makefile - 1.6 linux/arch/mips/baget/Makefile - 1.8 linux/arch/mips/arc/Makefile - 1.7 linux/drivers/char/ppdev.c - 1.35 linux/drivers/block/cpqarray.c - 1.63 linux/kernel/ptrace.c - 1.28 linux/drivers/parport/probe.c - 1.7 linux/drivers/parport/parport_pc.c - 1.50 linux/drivers/parport/ieee1284_ops.c - 1.17 linux/drivers/parport/ieee1284.c - 1.14 linux/drivers/parport/daisy.c - 1.8 linux/drivers/parport/Makefile - 1.11 linux/drivers/char/raw.c - 1.34 linux/include/asm-sparc64/parport.h - 1.12 linux/drivers/net/ppp_generic.c - 1.32 linux/drivers/net/mvme147.c - 1.10 linux/drivers/net/macsonic.c - 1.15 linux/drivers/char/sxboards.h - 1.3 linux/drivers/char/sx.h - 1.6 linux/drivers/char/sx.c - 1.28 linux/include/linux/logibusmouse.h - 1.2 linux/drivers/pci/names.c - 1.12 linux/fs/partitions/check.c - 1.61 linux/fs/partitions/Makefile - 1.12 linux/drivers/video/vga.h - 1.7 linux/drivers/scsi/sun3x_esp.h - 1.3 linux/drivers/scsi/oktagon_esp.h - 1.3 linux/drivers/isdn/hisax/saphir.c - 1.12 linux/drivers/isdn/hisax/jade_irq.c - 1.9 linux/drivers/isdn/hisax/jade.h - 1.5 linux/drivers/isdn/hisax/jade.c - 1.13 linux/drivers/isdn/hisax/isurf.c - 1.14 linux/drivers/isdn/hisax/hfc_pci.c - 1.27 linux/drivers/isdn/hisax/gazel.c - 1.16 linux/drivers/isdn/hisax/bkm_a8.c - 1.15 linux/drivers/isdn/hisax/bkm_a4t.c - 1.15 linux/arch/m68k/math-emu/Makefile - 1.8 linux/arch/i386/kernel/i8259.c - 1.35 linux/drivers/video/modedb.c - 1.8 linux/drivers/net/sis900.c - 1.38 linux/drivers/net/sb1000.c - 1.19 linux/drivers/net/fc/iph5526_scsi.h - 1.3 linux/drivers/net/fc/iph5526.c - 1.22 linux/drivers/net/fc/Makefile - 1.6 linux/drivers/char/ip2main.c - 1.23 linux/drivers/char/ip2/i2ellis.h - 1.6 linux/drivers/atm/horizon.h - 1.4 linux/drivers/atm/horizon.c - 1.15 linux/drivers/atm/atmtcp.c - 1.11 linux/drivers/atm/atmdev_init.c - 1.11 linux/drivers/atm/ambassador.h - 1.7 linux/drivers/atm/ambassador.c - 1.19 linux/drivers/atm/Makefile - 1.23 linux/arch/i386/kernel/semaphore.c - 1.20 linux/net/sched/sch_atm.c - 1.9 linux/net/atm/proc.c - 1.18 linux/net/atm/mpc.c - 1.11 linux/net/atm/common.c - 1.19 linux/net/atm/Makefile - 1.12 linux/include/linux/atmdev.h - 1.12 linux/arch/ppc/math-emu/Makefile - 1.6 linux/arch/ppc/kernel/entry.S - 1.31 linux/arch/arm/kernel/bios32.c - 1.32 linux/arch/alpha/kernel/pci.c - 1.27 linux/drivers/block/DAC960.h - 1.21 linux/drivers/block/DAC960.c - 1.63 linux/arch/sparc64/kernel/power.c - 1.12 linux/arch/sparc64/kernel/pci_sabre.c - 1.32 linux/arch/sparc64/kernel/pci_psycho.c - 1.30 linux/arch/sparc64/kernel/pci_common.c - 1.19 linux/arch/sparc64/kernel/pci.c - 1.33 linux/arch/sh/mm/Makefile - 1.8 linux/arch/sh/lib/Makefile - 1.10 linux/arch/sh/kernel/Makefile - 1.17 linux/include/asm-arm/cpu-single.h - 1.13 linux/include/asm-arm/cpu-multi32.h - 1.13 linux/drivers/scsi/ips.h - 1.19 linux/drivers/scsi/ips.c - 1.33 linux/drivers/scsi/ChangeLog.serverraid - 1.3 linux/drivers/char/applicom.c - 1.14 linux/include/math-emu/op-4.h - 1.5 linux/include/asm-sh/stat.h - 1.4 linux/include/asm-sh/signal.h - 1.4 linux/include/asm-sh/processor.h - 1.20 linux/drivers/pcmcia/tcic.c - 1.19 linux/fs/udf/udftime.c - 1.7 linux/drivers/pcmcia/rsrc_mgr.c - 1.17 linux/drivers/pcmcia/i82365.c - 1.29 linux/drivers/pcmcia/ds.c - 1.24 linux/drivers/pcmcia/cs.c - 1.32 linux/drivers/pcmcia/cistpl.c - 1.15 linux/include/pcmcia/mem_op.h - 1.6 linux/drivers/pcmcia/cardbus.c - 1.23 linux/drivers/pcmcia/Makefile - 1.21 linux/drivers/net/sun3lance.c - 1.14 linux/drivers/block/swim_iop.c - 1.22 linux/arch/m68k/sun3/prom/Makefile - 1.4 linux/arch/m68k/sun3/Makefile - 1.10 linux/fs/udf/ialloc.c - 1.17 linux/include/linux/udf_fs_sb.h - 1.8 linux/fs/udf/file.c - 1.31 linux/fs/udf/directory.c - 1.10 linux/fs/udf/dir.c - 1.22 linux/fs/udf/inode.c - 1.35 linux/include/linux/udf_fs_i.h - 1.8 linux/fs/udf/lowlevel.c - 1.12 linux/fs/udf/balloc.c - 1.15 linux/include/linux/udf_fs.h - 1.16 linux/fs/udf/Makefile - 1.5 linux/fs/udf/misc.c - 1.12 linux/fs/udf/namei.c - 1.26 linux/fs/udf/super.c - 1.35 linux/fs/udf/truncate.c - 1.12 linux/fs/udf/symlink.c - 1.19 linux/fs/udf/unicode.c - 1.7 linux/fs/udf/udf_i.h - 1.8 linux/fs/udf/udfdecl.h - 1.22 linux/include/linux/spinlock.h - 1.21 linux/drivers/net/starfire.c - 1.28 linux/drivers/net/pcmcia/ray_cs.c - 1.27 linux/drivers/net/pcmcia/pcnet_cs.c - 1.22 linux/drivers/net/pcmcia/Makefile - 1.23 linux/drivers/net/pcmcia/3c589_cs.c - 1.24 linux/drivers/char/drm/Makefile - 1.16 linux/include/linux/acpi.h - 1.32 linux/Documentation/filesystems/proc.txt - 1.15 linux/drivers/net/wan/cosa.c - 1.27 linux/drivers/net/wan/Makefile - 1.20 linux/drivers/net/tokenring/olympic.c - 1.24 linux/drivers/net/tokenring/ibmtr.c - 1.22 linux/drivers/net/tokenring/Makefile - 1.12 linux/arch/i386/kernel/smpboot.c - 1.53 linux/include/linux/pci_ids.h - 1.79 linux/drivers/net/wan/x25_asy.c - 1.9 linux/drivers/net/wan/syncppp.c - 1.17 linux/drivers/net/wan/sealevel.c - 1.12 linux/drivers/net/wan/sdlamain.c - 1.14 linux/drivers/net/wan/sdla_ppp.c - 1.20 linux/drivers/net/wan/sdla_fr.c - 1.20 linux/drivers/net/wan/sdla.c - 1.15 linux/drivers/net/wan/sbni.c - 1.19 linux/drivers/net/wan/lapbether.c - 1.14 linux/drivers/net/wan/hostess_sv11.c - 1.11 linux/drivers/net/wan/dlci.c - 1.10 linux/drivers/video/tdfxfb.c - 1.25 linux/drivers/scsi/sim710.h - 1.8 linux/drivers/scsi/dec_esp.h - 1.4 linux/drivers/scsi/ChangeLog.ips - 1.6 linux/drivers/net/tokenring/tms380tr.c - 1.18 linux/drivers/net/pcmcia/xirc2ps_cs.c - 1.19 linux/drivers/net/pcmcia/3c574_cs.c - 1.22 linux/drivers/net/pcmcia/nmclan_cs.c - 1.16 linux/drivers/net/pcmcia/fmvj18x_cs.c - 1.20 linux/drivers/net/pcmcia/smc91c92_cs.c - 1.19 linux/mm/bootmem.c - 1.24 linux/include/asm-arm/proc-armv/cache.h - 1.16 linux/include/asm-arm/arch-sa1100/memory.h - 1.8 linux/drivers/video/aty128fb.c - 1.30 linux/fs/proc/proc_misc.c - 1.50 linux/fs/bfs/inode.c - 1.29 linux/fs/bfs/file.c - 1.25 linux/fs/bfs/Makefile - 1.4 linux/drivers/net/setup.c - 1.21 linux/drivers/char/pcmcia/Makefile - 1.9 linux/drivers/isdn/hisax/w6692.c - 1.16 linux/drivers/pci/pci.ids - 1.55 linux/drivers/net/sk98lin/Makefile - 1.8 linux/drivers/net/sk98lin/h/skgehw.h - 1.6 linux/drivers/net/sk98lin/skge.c - 1.21 linux/include/asm-arm/arch-cl7500/memory.h - 1.6 linux/arch/alpha/lib/fpreg.c - 1.2 linux/arch/alpha/kernel/sys_nautilus.c - 1.11 linux/include/linux/mmzone.h - 1.33 linux/include/linux/agp_backend.h - 1.22 linux/drivers/net/pcmcia/aironet4500_cs.c - 1.16 linux/drivers/net/aironet4500_proc.c - 1.14 linux/drivers/net/aironet4500_core.c - 1.21 linux/drivers/net/aironet4500_card.c - 1.19 linux/drivers/char/agp/Makefile - 1.10 linux/kernel/timer.c - 1.38 linux/drivers/scsi/scsi_lib.c - 1.55 linux/drivers/char/agp/agp.h - 1.29 linux/include/linux/i2c-id.h - 1.13 linux/drivers/i2c/i2c-elektor.c - 1.13 linux/drivers/i2c/i2c-dev.c - 1.22 linux/drivers/i2c/i2c-core.c - 1.18 linux/drivers/i2c/Makefile - 1.9 linux/drivers/pcmcia/yenta.c - 1.35 linux/drivers/pcmcia/pci_socket.c - 1.13 linux/drivers/net/irda/old_belkin.c - 1.5 linux/arch/sparc64/kernel/sbus.c - 1.17 linux/arch/i386/kernel/acpi.c - 1.31 linux/fs/openpromfs/Makefile - 1.4 linux/fs/cramfs/Makefile - 1.7 linux/include/linux/input.h - 1.23 linux/drivers/telephony/phonedev.c - 1.10 linux/drivers/telephony/ixj.c - 1.25 linux/drivers/telephony/Makefile - 1.6 linux/drivers/scsi/README.aha152x - 1.2 linux/drivers/net/pcmcia/com20020_cs.c - 1.9 linux/drivers/net/arcnet/com20020-pci.c - 1.14 linux/drivers/net/arcnet/Makefile - 1.5 linux/net/ipv4/inetpeer.c - 1.9 linux/Documentation/usb/usb-serial.txt - 1.23 linux/Documentation/usb/ov511.txt - 1.20 linux/drivers/net/tokenring/smctr.c - 1.17 linux/drivers/pnp/quirks.c - 1.12 linux/net/sched/sch_gred.c - 1.11 linux/kernel/uid16.c - 1.3 linux/drivers/ieee1394/raw1394.h - 1.6 linux/drivers/ieee1394/raw1394.c - 1.22 linux/drivers/ieee1394/ieee1394_core.h - 1.16 linux/drivers/ieee1394/pcilynx.c - 1.25 linux/drivers/ieee1394/ieee1394_core.c - 1.25 linux/drivers/ieee1394/ohci1394.h - 1.17 linux/drivers/ieee1394/ohci1394.c - 1.26 linux/drivers/ieee1394/ieee1394_types.h - 1.17 linux/drivers/ieee1394/ieee1394_transactions.h - 1.6 linux/drivers/ieee1394/ieee1394_transactions.c - 1.13 linux/drivers/ieee1394/csr.h - 1.5 linux/drivers/ieee1394/ieee1394.h - 1.5 linux/drivers/ieee1394/hosts.h - 1.13 linux/drivers/ieee1394/hosts.c - 1.15 linux/drivers/ieee1394/csr.c - 1.10 linux/drivers/char/mxser.c - 1.21 linux/drivers/ieee1394/Makefile - 1.17 linux/drivers/ieee1394/highlevel.c - 1.10 linux/include/asm-i386/mpspec.h - 1.13 linux/include/asm-i386/io_apic.h - 1.9 linux/drivers/pci/setup-res.c - 1.12 linux/drivers/pci/setup-irq.c - 1.3 linux/drivers/pci/setup-bus.c - 1.8 linux/drivers/scsi/scsi_scan.c - 1.36 linux/drivers/scsi/3w-xxxx.h - 1.16 linux/drivers/scsi/3w-xxxx.c - 1.25 linux/drivers/net/wan/sdla_chdlc.c - 1.20 linux/drivers/net/tokenring/tmspci.c - 1.9 linux/drivers/net/tokenring/madgemc.c - 1.6 linux/drivers/net/tokenring/abyss.c - 1.9 linux/drivers/char/mixcomwd.c - 1.14 linux/fs/autofs4/expire.c - 1.10 linux/fs/autofs4/autofs_i.h - 1.11 linux/fs/autofs4/Makefile - 1.5 linux/fs/autofs4/root.c - 1.18 linux/drivers/net/mac89x0.c - 1.12 linux/arch/ia64/kernel/entry.S - 1.32 linux/arch/ia64/kernel/Makefile - 1.16 linux/arch/ia64/ia32/sys_ia32.c - 1.36 linux/drivers/acorn/char/i2c.c - 1.7 linux/arch/ia64/ia32/Makefile - 1.11 linux/arch/ia64/vmlinux.lds.S - 1.18 linux/arch/ia64/dig/Makefile - 1.8 linux/arch/arm/kernel/time-acorn.c - 1.5 linux/arch/ia64/lib/Makefile - 1.17 linux/arch/ia64/kernel/ptrace.c - 1.19 linux/arch/ia64/kernel/perfmon.c - 1.19 linux/arch/ia64/mm/Makefile - 1.5 linux/drivers/scsi/qla1280.h - 1.10 linux/fs/adfs/dir_f.c - 1.10 linux/fs/adfs/dir_fplus.c - 1.9 linux/drivers/scsi/qla1280.c - 1.23 linux/include/asm-ia64/processor.h - 1.28 linux/include/asm-ia64/stat.h - 1.3 linux/include/asm-ia64/unistd.h - 1.27 linux/drivers/video/sun3fb.c - 1.12 linux/drivers/net/8139too.c - 1.46 linux/drivers/macintosh/via-pmu68k.c - 1.7 linux/drivers/isdn/hisax/hfc_sx.c - 1.16 linux/arch/i386/kernel/microcode.c - 1.21 linux/include/linux/devfs_fs_kernel.h - 1.15 linux/drivers/scsi/pcmcia/qlogic_stub.c - 1.8 linux/drivers/scsi/pcmcia/fdomain_stub.c - 1.8 linux/fs/devfs/util.c - 1.16 linux/fs/devfs/base.c - 1.48 linux/drivers/scsi/pcmcia/Makefile - 1.7 linux/drivers/scsi/pcmcia/aha152x_stub.c - 1.9 linux/fs/devfs/Makefile - 1.5 linux/drivers/net/skfp/Makefile - 1.7 linux/drivers/net/skfp/skfddi.c - 1.14 linux/drivers/net/skfp/h/skfbi.h - 1.3 linux/fs/lockd/xdr4.c - 1.12 linux/net/bridge/br_if.c - 1.9 linux/arch/mips/ddb5074/Makefile - 1.7 linux/drivers/video/matrox/matroxfb_misc.c - 1.7 linux/drivers/video/matrox/matroxfb_crtc2.c - 1.12 linux/drivers/video/matrox/matroxfb_base.c - 1.21 linux/drivers/video/matrox/matroxfb_accel.c - 1.9 linux/drivers/video/matrox/i2c-matroxfb.c - 1.6 linux/drivers/video/matrox/Makefile - 1.8 linux/drivers/net/tulip/tulip_core.c - 1.44 linux/drivers/net/tulip/media.c - 1.14 linux/drivers/net/tulip/Makefile - 1.8 linux/drivers/char/wdt977.c - 1.13 linux/drivers/char/wdt285.c - 1.13 linux/include/linux/ac97_codec.h - 1.13 linux/include/asm-mips64/posix_types.h - 1.4 linux/include/asm-mips64/stat.h - 1.5 linux/arch/mips64/sgi-ip22/Makefile - 1.7 linux/arch/mips64/mm/Makefile - 1.6 linux/arch/mips64/lib/Makefile - 1.7 linux/arch/mips64/tools/Makefile - 1.6 linux/arch/mips64/sgi-ip27/ip27-rtc.c - 1.9 linux/arch/mips64/sgi-ip27/Makefile - 1.10 linux/arch/mips64/kernel/scall_o32.S - 1.10 linux/arch/mips64/arc/Makefile - 1.7 linux/arch/mips64/kernel/signal32.c - 1.12 linux/arch/mips64/boot/Makefile - 1.10 linux/arch/mips64/kernel/linux32.c - 1.14 linux/arch/mips64/kernel/Makefile - 1.8 linux/drivers/net/bonding.c - 1.16 linux/drivers/video/riva/riva_hw.h - 1.4 linux/drivers/video/riva/fbdev.c - 1.19 linux/drivers/video/riva/Makefile - 1.5 linux/include/video/fbcon-hga.h - 1.2 linux/drivers/video/hgafb.c - 1.17 linux/drivers/video/fbcon-hga.c - 1.7 linux/drivers/net/appletalk/ltpc.c - 1.13 linux/drivers/net/appletalk/cops.c - 1.15 linux/drivers/net/appletalk/Makefile - 1.5 linux/include/linux/usb.h - 1.50 linux/drivers/usb/serial/usb-serial.h - 1.25 linux/drivers/usb/serial/usb-serial.c - 1.8 linux/drivers/usb/serial/Makefile - 1.23 linux/drivers/parport/ChangeLog - 1.30 linux/drivers/ide/ide.c - 1.78 linux/drivers/ide/ide-tape.c - 1.40 linux/drivers/ide/ide-probe.c - 1.47 linux/drivers/ide/ide-geometry.c - 1.19 linux/drivers/ide/ide-floppy.c - 1.41 linux/drivers/ide/ide-dma.c - 1.34 linux/drivers/ide/ide-disk.c - 1.54 linux/drivers/ide/ide-cd.c - 1.56 linux/drivers/ide/Makefile - 1.32 linux/drivers/net/wan/comx-proto-fr.c - 1.12 linux/drivers/net/wan/comx-hw-mixcom.c - 1.10 linux/drivers/net/wan/comx-hw-locomx.c - 1.8 linux/drivers/net/wan/comx-hw-comx.c - 1.9 linux/drivers/net/tokenring/lanstreamer.c - 1.14 linux/Documentation/DocBook/kernel-api.tmpl - 1.24 linux/net/ipv4/netfilter/Makefile - 1.19 linux/drivers/scsi/dmx3191d.h - 1.6 linux/drivers/scsi/dmx3191d.c - 1.11 linux/drivers/net/pcmcia/ibmtr_cs.c - 1.11 linux/drivers/char/wdt_pci.c - 1.15 linux/include/linux/nfs_xdr.h - 1.13 linux/include/asm-arm/arch-shark/timex.h - 1.4 linux/include/asm-arm/arch-rpc/vmalloc.h - 1.4 linux/include/asm-arm/arch-sa1100/vmalloc.h - 1.3 linux/include/asm-arm/arch-nexuspci/vmalloc.h - 1.2 linux/include/asm-arm/arch-ebsa285/vmalloc.h - 1.4 linux/include/asm-arm/arch-ebsa110/vmalloc.h - 1.4 linux/include/asm-arm/arch-cl7500/vmalloc.h - 1.3 linux/include/asm-arm/arch-shark/memory.h - 1.8 linux/include/asm-arm/arch-shark/irqs.h - 1.4 linux/fs/ramfs/inode.c - 1.34 linux/fs/ramfs/Makefile - 1.4 linux/drivers/video/sa1100fb.c - 1.18 linux/fs/nfs/nfs3proc.c - 1.18 linux/drivers/usb/serial/keyspan_pda.c - 1.33 linux/drivers/usb/serial/ftdi_sio.c - 1.44 linux/drivers/usb/serial/whiteheat.c - 1.35 linux/drivers/usb/serial/visor.h - 1.14 linux/drivers/usb/serial/visor.c - 1.46 linux/include/asm-arm/arch-shark/ide.h - 1.6 linux/drivers/usb/serial/omninet.c - 1.32 linux/drivers/net/wan/lmc/lmc_proto.c - 1.6 linux/drivers/net/wan/lmc/lmc_media.c - 1.5 linux/drivers/net/wan/lmc/lmc_main.c - 1.12 linux/drivers/net/wan/lmc/lmc_debug.c - 1.3 linux/drivers/net/wan/lmc/Makefile - 1.6 linux/include/linux/fs_struct.h - 1.8 linux/include/linux/if_pppox.h - 1.8 linux/drivers/usb/serial/digi_acceleport.c - 1.33 linux/drivers/net/pppox.c - 1.9 linux/drivers/net/pppoe.c - 1.24 linux/drivers/char/rio/Makefile - 1.4 linux/arch/ppc/8260_io/Makefile - 1.7 linux/drivers/char/rio/riocmd.c - 1.8 linux/drivers/char/rio/rio_linux.c - 1.17 linux/arch/s390/kernel/process.c - 1.16 linux/include/asm-s390/page.h - 1.8 linux/arch/s390/boot/Makefile - 1.11 linux/arch/s390/Makefile - 1.13 linux/include/asm-s390/unistd.h - 1.13 linux/include/asm-s390/uaccess.h - 1.8 linux/include/asm-s390/types.h - 1.3 linux/arch/s390/defconfig - 1.16 linux/include/asm-s390/irq.h - 1.9 linux/include/asm-s390/lowcore.h - 1.9 linux/arch/s390/kernel/Makefile - 1.11 linux/include/asm-s390/ebcdic.h - 1.6 linux/include/asm-s390/chandev.h - 1.6 linux/include/asm-s390/stat.h - 1.4 linux/include/asm-s390/smp.h - 1.7 linux/include/asm-s390/setup.h - 1.6 linux/arch/s390/kernel/entry.S - 1.22 linux/arch/s390/kernel/head.S - 1.10 linux/drivers/s390/net/iucv.c - 1.12 linux/drivers/s390/net/Makefile - 1.8 linux/drivers/s390/misc/chandev.c - 1.13 linux/drivers/s390/misc/Makefile - 1.5 linux/drivers/s390/char/hwc_rw.c - 1.8 linux/drivers/s390/char/hwc_tty.c - 1.8 linux/drivers/s390/char/hwc_rw.h - 1.5 linux/drivers/s390/char/hwc_con.c - 1.7 linux/drivers/s390/char/Makefile - 1.9 linux/drivers/s390/char/hwc.h - 1.7 linux/drivers/s390/char/con3215.c - 1.11 linux/include/asm-s390/s390mach.h - 1.4 linux/include/asm-s390/s390io.h - 1.6 linux/drivers/s390/block/dasd_eckd.c - 1.12 linux/include/asm-s390/s390dyn.h - 1.5 linux/drivers/s390/block/dasd.c - 1.34 linux/drivers/s390/block/dasd_erp.c - 1.4 linux/drivers/s390/Makefile - 1.10 linux/include/asm-s390/posix_types.h - 1.2 linux/include/asm-s390/poll.h - 1.2 linux/include/asm-s390/pgtable.h - 1.17 linux/Documentation/s390/cds.txt - 1.8 linux/include/asm-s390/mman.h - 1.3 linux/include/asm-s390/bitops.h - 1.9 linux/include/asm-s390/current.h - 1.6 linux/drivers/s390/block/dasd_proc.c - 1.9 linux/drivers/s390/block/Makefile - 1.9 linux/arch/s390/kernel/time.c - 1.9 linux/arch/s390/kernel/traps.c - 1.13 linux/arch/s390/kernel/ptrace.c - 1.11 linux/arch/s390/kernel/s390_ksyms.c - 1.9 linux/arch/s390/kernel/setup.c - 1.11 linux/arch/s390/kernel/signal.c - 1.14 linux/arch/s390/kernel/smp.c - 1.17 linux/arch/s390/mm/extable.c - 1.5 linux/arch/s390/lib/Makefile - 1.7 linux/arch/s390/mm/Makefile - 1.5 linux/arch/s390/mm/init.c - 1.13 linux/net/ipv6/netfilter/Makefile - 1.12 linux/Documentation/DocBook/kernel-locking.tmpl - 1.8 linux/arch/mips64/kernel/ioctl32.c - 1.14 linux/drivers/net/stnic.c - 1.9 linux/include/asm-arm/arch-l7200/vmalloc.h - 1.2 linux/include/asm-arm/arch-l7200/memory.h - 1.6 linux/include/linux/sisfb.h - 1.4 linux/fs/xfs/Makefile - 1.163 linux/include/linux/profile.h - 1.4 linux/kernel/profile.c - 1.5 linux/kernel/kallsyms.c - 1.15 linux/include/linux/kallsyms.h - 1.11 linux/Documentation/DocBook/mousedrivers.tmpl - 1.4 linux/Documentation/filesystems/Locking - 1.19 linux/drivers/char/drm/r128_drv.h - 1.11 linux/drivers/video/hitfb.c - 1.10 linux/drivers/char/drm/r128_drm.h - 1.6 linux/drivers/char/drm/mga_state.c - 1.11 linux/drivers/char/drm/mga_drv.h - 1.11 linux/drivers/char/drm/mga_drm.h - 1.5 linux/drivers/char/drm/mga_dma.c - 1.10 linux/drivers/char/drm/i810_drv.h - 1.4 linux/drivers/char/drm/i810_dma.c - 1.18 linux/drivers/char/drm/ffb_drv.c - 1.11 linux/drivers/usb/storage/usb.h - 1.20 linux/drivers/usb/storage/usb.c - 1.33 linux/drivers/usb/storage/transport.h - 1.14 linux/drivers/usb/storage/transport.c - 1.35 linux/drivers/usb/storage/scsiglue.c - 1.28 linux/drivers/char/sbc60xxwdt.c - 1.16 linux/drivers/usb/storage/Makefile - 1.12 linux/drivers/usb/serial/keyspan.h - 1.14 linux/drivers/usb/serial/keyspan.c - 1.37 linux/drivers/acpi/tables/tbxface.c - 1.13 linux/drivers/acpi/tables/tbinstal.c - 1.14 linux/drivers/acpi/tables/tbget.c - 1.15 linux/drivers/acpi/resources/rsutils.c - 1.11 linux/drivers/acpi/resources/rsirq.c - 1.11 linux/drivers/acpi/resources/rscreate.c - 1.13 linux/drivers/acpi/resources/rscalc.c - 1.12 linux/drivers/acpi/resources/rsaddr.c - 1.9 linux/drivers/acpi/parser/psparse.c - 1.16 linux/drivers/acpi/parser/psopcode.c - 1.15 linux/drivers/acpi/parser/psargs.c - 1.14 linux/drivers/acpi/namespace/nsxfname.c - 1.11 linux/drivers/acpi/namespace/nsutils.c - 1.15 linux/drivers/acpi/namespace/nssearch.c - 1.15 linux/drivers/acpi/namespace/nsobject.c - 1.13 linux/drivers/acpi/namespace/nsnames.c - 1.13 linux/drivers/acpi/namespace/nsload.c - 1.14 linux/fs/jffs/Makefile - 1.8 linux/fs/jffs/inode-v23.c - 1.34 linux/drivers/acpi/namespace/nseval.c - 1.15 linux/drivers/acpi/namespace/nsalloc.c - 1.13 linux/drivers/acpi/namespace/nsaccess.c - 1.15 linux/fs/jffs/intrep.c - 1.19 linux/arch/arm/mm/proc-arm720.S - 1.16 linux/arch/i386/kernel/i387.c - 1.12 linux/drivers/acpi/include/amlcode.h - 1.13 linux/drivers/acpi/include/actypes.h - 1.16 linux/drivers/acpi/include/actables.h - 1.12 linux/drivers/acpi/include/acpixf.h - 1.14 linux/drivers/acpi/include/acpiosxf.h - 1.13 linux/drivers/acpi/include/acobject.h - 1.14 linux/drivers/acpi/include/acexcep.h - 1.11 linux/drivers/acpi/hardware/hwregs.c - 1.14 linux/drivers/acpi/hardware/hwacpi.c - 1.12 linux/drivers/acpi/events/evxfevnt.c - 1.11 linux/drivers/acpi/events/evxface.c - 1.14 linux/drivers/acpi/events/evrgnini.c - 1.12 linux/drivers/acpi/events/evregion.c - 1.14 linux/drivers/acpi/events/evmisc.c - 1.13 linux/drivers/acpi/events/evevent.c - 1.17 linux/drivers/acpi/ec.c - 1.13 linux/drivers/acpi/dispatcher/dswstate.c - 1.15 linux/drivers/acpi/dispatcher/dswload.c - 1.18 linux/drivers/acpi/dispatcher/dswexec.c - 1.13 linux/drivers/acpi/dispatcher/dsutils.c - 1.15 linux/drivers/acpi/dispatcher/dsopcode.c - 1.16 linux/drivers/acpi/dispatcher/dsobject.c - 1.19 linux/lib/cmdline.c - 1.4 linux/drivers/acpi/dispatcher/dsmthdat.c - 1.13 linux/drivers/acpi/dispatcher/dsmethod.c - 1.13 linux/drivers/acpi/dispatcher/dsfield.c - 1.13 linux/drivers/acpi/Makefile - 1.22 linux/arch/ia64/kernel/palinfo.c - 1.9 linux/drivers/ieee1394/video1394.c - 1.24 linux/drivers/mtd/Makefile - 1.12 linux/drivers/mtd/mtdblock.c - 1.28 linux/drivers/mtd/mtdchar.c - 1.11 linux/drivers/net/ibmlana.c - 1.9 linux/include/linux/serio.h - 1.8 linux/drivers/net/tun.c - 1.18 linux/include/asm-sparc/highmem.h - 1.9 linux/fs/smbfs/getopt.c - 1.4 linux/fs/nfs/unlink.c - 1.8 linux/drivers/usb/storage/freecom.c - 1.18 linux/drivers/sbus/char/display7seg.c - 1.7 linux/drivers/media/video/zr36120.c - 1.15 linux/drivers/media/video/vino.c - 1.4 linux/drivers/media/video/videodev.c - 1.16 linux/drivers/media/video/tvmixer.c - 1.10 linux/drivers/media/video/tuner.c - 1.13 linux/drivers/media/video/stradis.c - 1.10 linux/drivers/media/video/saa7185.c - 1.8 linux/drivers/media/video/saa7111.c - 1.7 linux/drivers/media/video/saa5249.c - 1.11 linux/drivers/media/video/pms.c - 1.10 linux/drivers/media/video/planb.c - 1.13 linux/drivers/media/video/msp3400.c - 1.13 linux/drivers/media/video/cpia_usb.c - 1.16 linux/drivers/media/video/cpia.c - 1.17 linux/drivers/media/video/c-qcam.c - 1.11 linux/drivers/media/video/bw-qcam.c - 1.11 linux/drivers/media/video/bttv-if.c - 1.7 linux/drivers/media/video/bttv-driver.c - 1.25 linux/drivers/media/video/bttv-cards.c - 1.15 linux/drivers/media/video/Makefile - 1.12 linux/drivers/media/radio/radio-zoltrix.c - 1.11 linux/drivers/media/radio/radio-typhoon.c - 1.11 linux/drivers/media/radio/radio-trust.c - 1.11 linux/drivers/media/radio/radio-terratec.c - 1.11 linux/drivers/media/radio/radio-sf16fmi.c - 1.15 linux/drivers/media/radio/radio-rtrack2.c - 1.11 linux/drivers/media/radio/radio-gemtek.c - 1.11 linux/drivers/media/radio/radio-cadet.c - 1.11 linux/drivers/media/radio/radio-aztech.c - 1.11 linux/drivers/media/radio/radio-aimslab.c - 1.11 linux/drivers/media/radio/Makefile - 1.11 linux/drivers/media/Makefile - 1.7 linux/drivers/isdn/hisax/nj_u.c - 1.12 linux/drivers/isdn/hisax/nj_s.c - 1.13 linux/drivers/isdn/hisax/icc.h - 1.4 linux/drivers/isdn/hisax/icc.c - 1.10 linux/drivers/isdn/eicon/uxio.h - 1.6 linux/drivers/isdn/eicon/linio.c - 1.7 linux/drivers/isdn/eicon/lincfg.c - 1.6 linux/drivers/isdn/eicon/divas.h - 1.4 linux/arch/arm/boot/bootp/Makefile - 1.7 linux/drivers/input/mousedev.c - 1.16 linux/drivers/input/joydev.c - 1.14 linux/drivers/input/evdev.c - 1.15 linux/drivers/input/Makefile - 1.9 linux/drivers/char/i810-tco.h - 1.4 linux/drivers/char/i810-tco.c - 1.13 linux/arch/arm/tools/mach-types - 1.20 linux/arch/arm/mach-footbridge/netwinder-pci.c - 1.6 linux/arch/arm/mach-footbridge/netwinder-hw.c - 1.4 linux/arch/arm/mach-footbridge/cats-hw.c - 1.2 linux/arch/arm/mach-footbridge/Makefile - 1.9 linux/drivers/md/raid5.c - 1.38 linux/arch/arm/def-configs/shark - 1.12 linux/arch/arm/kernel/plx90x0.c - 1.4 linux/arch/arm/kernel/via82c505.c - 1.8 linux/arch/arm/mach-sa1100/Makefile - 1.16 linux/arch/arm/mach-shark/Makefile - 1.7 linux/arch/arm/mach-shark/dma.c - 1.4 linux/arch/arm/mm/proc-arm920.S - 1.13 linux/arch/arm/mm/proc-syms.c - 1.5 linux/drivers/acpi/dispatcher/Makefile - 1.7 linux/drivers/acpi/events/Makefile - 1.7 linux/drivers/acpi/hardware/Makefile - 1.7 linux/drivers/acpi/include/acconfig.h - 1.21 linux/drivers/acpi/include/acdebug.h - 1.14 linux/drivers/acpi/include/acdispat.h - 1.10 linux/drivers/acpi/include/acevents.h - 1.11 linux/drivers/acpi/include/acglobal.h - 1.15 linux/drivers/acpi/include/acinterp.h - 1.14 linux/drivers/acpi/include/aclocal.h - 1.17 linux/drivers/acpi/include/acmacros.h - 1.14 linux/drivers/acpi/include/acnamesp.h - 1.14 linux/drivers/acpi/include/acoutput.h - 1.10 linux/drivers/acpi/include/acparser.h - 1.12 linux/drivers/acpi/include/actbl.h - 1.9 linux/drivers/acpi/namespace/Makefile - 1.7 linux/drivers/acpi/namespace/nsdump.c - 1.14 linux/drivers/acpi/parser/Makefile - 1.7 linux/drivers/acpi/resources/Makefile - 1.7 linux/drivers/acpi/tables/Makefile - 1.7 linux/drivers/block/cciss.c - 1.50 linux/drivers/block/cciss.h - 1.18 linux/drivers/char/toshiba.c - 1.8 linux/drivers/macintosh/adbhid.c - 1.9 linux/drivers/md/Makefile - 1.12 linux/drivers/md/linear.c - 1.17 linux/drivers/md/md.c - 1.65 linux/drivers/md/raid0.c - 1.16 linux/drivers/media/radio/radio-maestro.c - 1.9 linux/drivers/net/hamachi.c - 1.19 linux/drivers/net/sundance.c - 1.21 linux/drivers/scsi/cpqfc.Readme - 1.9 linux/drivers/scsi/cpqfcTS.h - 1.7 linux/drivers/scsi/cpqfcTSinit.c - 1.23 linux/drivers/scsi/cpqfcTSworker.c - 1.13 linux/include/asm-arm/arch-shark/vmalloc.h - 1.2 linux/include/asm-arm/arch-tbox/memory.h - 1.5 linux/include/asm-arm/arch-tbox/vmalloc.h - 1.3 linux/drivers/net/isa-skeleton.c - 1.9 linux/mm/oom_kill.c - 1.19 linux/drivers/usb/serial/belkin_sa.c - 1.26 linux/drivers/video/sis/Makefile - 1.6 linux/drivers/video/sis/sis_main.c - 1.15 linux/Documentation/networking/netdevices.txt - 1.2 linux/drivers/media/video/tvaudio.c - 1.12 linux/include/asm-alpha/module.h - 1.3 linux/net/irda/irnet/irnet_ppp.h - 1.4 linux/net/irda/irnet/Makefile - 1.4 linux/include/asm-alpha/xor.h - 1.2 linux/include/asm-arm/module.h - 1.3 linux/include/asm-i386/module.h - 1.3 linux/include/asm-i386/xor.h - 1.9 linux/include/asm-ppc/module.h - 1.5 linux/include/asm-s390/module.h - 1.3 linux/include/asm-sparc/module.h - 1.3 linux/include/asm-sparc64/module.h - 1.3 linux/drivers/video/fbcon-sti.c - 1.7 linux/drivers/parport/parport_gsc.c - 1.8 linux/drivers/video/sti-bmode.h - 1.2 linux/drivers/video/sti.h - 1.2 linux/drivers/video/sticon-bmode.c - 1.7 linux/drivers/video/sticon.c - 1.4 linux/drivers/video/sticore.c - 1.6 linux/drivers/video/stifb.c - 1.6 linux/arch/alpha/lib/ev6-stxncpy.S - 1.5 linux/drivers/net/lasi_82596.c - 1.14 linux/drivers/usb/serial/mct_u232.c - 1.27 linux/drivers/usb/serial/empeg.c - 1.32 linux/drivers/scsi/mvme147.h - 1.2 linux/arch/parisc/kernel/keyboard.c - 1.4 linux/arch/parisc/kernel/irq.c - 1.7 linux/arch/parisc/kernel/Makefile - 1.6 linux/arch/mips64/sgi-ip27/ip27-console.c - 1.3 linux/include/asm-parisc/stat.h - 1.3 linux/drivers/acpi/tables/tbconvrt.c - 1.12 linux/drivers/acpi/tables/tbxfroot.c - 1.10 linux/drivers/acpi/namespace/nsinit.c - 1.12 linux/drivers/acpi/include/actbl2.h - 1.9 linux/drivers/acpi/include/actbl1.h - 1.6 linux/include/asm-i386/mmu.h - 1.5 linux/mm/shmem.c - 1.52 linux/drivers/acpi/power.c - 1.9 linux/drivers/scsi/osst.h - 1.7 linux/drivers/scsi/osst.c - 1.20 linux/drivers/scsi/README.osst - 1.2 linux/drivers/char/drm/r128_state.c - 1.7 linux/arch/ia64/sn/io/Makefile - 1.7 linux/arch/ia64/sn/io/hcl.c - 1.6 linux/fs/reiserfs/super.c - 1.30 linux/drivers/acpi/acpi_ksyms.c - 1.14 linux/drivers/char/drm/radeon_drm.h - 1.8 linux/drivers/char/drm/radeon_drv.h - 1.10 linux/drivers/char/drm/radeon_state.c - 1.9 linux/drivers/acpi/hardware/hwsleep.c - 1.11 linux/fs/reiserfs/namei.c - 1.27 linux/arch/sparc64/kernel/pci_schizo.c - 1.18 linux/fs/reiserfs/journal.c - 1.37 linux/fs/reiserfs/inode.c - 1.36 linux/fs/reiserfs/dir.c - 1.16 linux/include/linux/reiserfs_fs.h - 1.35 linux/fs/reiserfs/bitmap.c - 1.21 linux/fs/reiserfs/Makefile - 1.9 linux/drivers/usb/storage/unusual_devs.h - 1.14 linux/include/asm-s390/dasd.h - 1.9 linux/arch/s390x/kernel/traps.c - 1.9 linux/arch/s390x/kernel/time.c - 1.8 linux/arch/s390x/kernel/smp.c - 1.14 linux/include/asm-s390x/posix_types.h - 1.2 linux/include/asm-s390x/poll.h - 1.2 linux/include/asm-s390x/pgtable.h - 1.13 linux/drivers/video/riva/rivafb.h - 1.3 linux/arch/s390x/kernel/signal.c - 1.11 linux/arch/s390x/kernel/setup.c - 1.10 linux/include/asm-s390x/module.h - 1.3 linux/drivers/video/riva/accel.c - 1.4 linux/Documentation/s390/chandev.8 - 1.6 linux/include/asm-s390x/mman.h - 1.3 linux/include/asm-s390x/lowcore.h - 1.7 linux/include/asm-s390x/irq.h - 1.8 linux/include/asm-s390x/idals.h - 1.4 linux/include/asm-s390x/ebcdic.h - 1.5 linux/include/asm-s390x/debug.h - 1.8 linux/arch/s390x/kernel/s390_ksyms.c - 1.7 linux/include/asm-s390x/dasd.h - 1.10 linux/include/asm-s390x/current.h - 1.5 linux/arch/arm/boot/compressed/ofw-shark.c - 1.6 linux/include/asm-s390x/chandev.h - 1.5 linux/include/asm-s390x/s390dyn.h - 1.4 linux/include/asm-s390x/s390io.h - 1.5 linux/include/asm-s390x/s390mach.h - 1.3 linux/include/asm-s390x/bitops.h - 1.5 linux/arch/s390x/kernel/ptrace.c - 1.10 linux/arch/s390x/kernel/process.c - 1.13 linux/arch/s390x/kernel/linux32.c - 1.19 linux/arch/s390x/kernel/ioctl32.c - 1.8 linux/arch/s390x/kernel/head.S - 1.9 linux/include/asm-s390x/setup.h - 1.6 linux/drivers/s390/s390mach.c - 1.8 linux/arch/cris/drivers/Makefile - 1.6 linux/arch/cris/drivers/axisflashmap.c - 1.8 linux/arch/cris/kernel/Makefile - 1.13 linux/arch/cris/kernel/debugport.c - 1.4 linux/arch/cris/kernel/setup.c - 1.11 linux/arch/cris/lib/Makefile - 1.5 linux/arch/cris/mm/Makefile - 1.4 linux/drivers/s390/s390dyn.c - 1.5 linux/drivers/s390/net/netiucv.c - 1.12 linux/drivers/s390/net/fsm.h - 1.4 linux/drivers/s390/net/fsm.c - 1.5 linux/drivers/s390/net/ctcmain.c - 1.10 linux/drivers/s390/char/tapedefs.h - 1.6 linux/drivers/s390/char/tapechar.h - 1.5 linux/drivers/s390/char/tapechar.c - 1.8 linux/arch/s390x/kernel/entry.S - 1.16 linux/drivers/s390/char/tapeblock.h - 1.5 linux/drivers/s390/char/tapeblock.c - 1.14 linux/drivers/s390/char/tape34xx.h - 1.5 linux/drivers/s390/char/tape34xx.c - 1.11 linux/drivers/s390/char/tape3490.h - 1.5 linux/drivers/s390/char/tape3490.c - 1.5 linux/drivers/s390/char/tape3480.h - 1.5 linux/drivers/s390/char/tape3480.c - 1.5 linux/drivers/s390/char/tape.h - 1.5 linux/drivers/s390/char/tape.c - 1.6 linux/arch/s390x/kernel/debug.c - 1.9 linux/arch/s390x/kernel/Makefile - 1.11 linux/arch/s390x/defconfig - 1.15 linux/include/asm-cris/stat.h - 1.3 linux/arch/s390x/mm/extable.c - 1.4 linux/include/asm-s390x/stat.h - 1.2 linux/arch/s390x/mm/Makefile - 1.4 linux/drivers/s390/block/xpram.c - 1.30 linux/drivers/s390/block/dasd_fba.h - 1.5 linux/drivers/s390/block/dasd_fba.c - 1.10 linux/drivers/s390/block/dasd_eckd.h - 1.7 linux/drivers/s390/block/dasd_diag.h - 1.5 linux/drivers/s390/block/dasd_diag.c - 1.10 linux/arch/s390x/lib/uaccess.S - 1.3 linux/arch/s390x/lib/Makefile - 1.7 linux/include/asm-s390x/uaccess.h - 1.5 linux/arch/s390x/kernel/wrapper32.S - 1.8 linux/drivers/s390/block/dasd_9343_erp.c - 1.5 linux/drivers/s390/block/dasd_9336_erp.c - 1.5 linux/drivers/s390/block/dasd_3990_erp.h - 1.6 linux/drivers/s390/block/dasd_3990_erp.c - 1.10 linux/drivers/s390/block/dasd_3370_erp.c - 1.5 linux/include/asm-cris/unistd.h - 1.10 linux/include/asm-s390x/unistd.h - 1.10 linux/drivers/pcmcia/hd64465_ss.c - 1.7 linux/drivers/net/tokenring/tmsisa.c - 1.5 linux/include/asm-s390/idals.h - 1.4 linux/include/asm-s390/debug.h - 1.8 linux/arch/s390/kernel/debug.c - 1.9 linux/arch/s390/lib/uaccess.S - 1.3 linux/arch/s390x/boot/Makefile - 1.11 linux/arch/s390x/Makefile - 1.14 linux/net/ipv4/netfilter/ipt_TCPMSS.c - 1.7 linux/include/asm-arm/arch-integrator/vmalloc.h - 1.2 linux/include/asm-arm/arch-integrator/memory.h - 1.4 linux/drivers/usb/serial/io_tables.h - 1.8 linux/drivers/usb/serial/io_edgeport.c - 1.30 linux/drivers/scsi/aic7xxx_old/aic7xxx_proc.c - 1.6 linux/drivers/scsi/aic7xxx_old/aic7xxx.h - 1.8 linux/drivers/scsi/aic7xxx_old/README.aic7xxx - 1.3 linux/drivers/scsi/aic7xxx_old.c - 1.25 linux/drivers/scsi/aic7xxx/aic7xxx_osm.h - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_linux_host.h - 1.9 linux/drivers/scsi/aic7xxx/aic7xxx_linux.c - 1.21 linux/arch/arm/mach-integrator/Makefile - 1.6 linux/arch/arm/mach-integrator/arch.c - 1.8 linux/arch/arm/mach-integrator/dma.c - 1.3 linux/arch/arm/mach-integrator/pci.c - 1.8 linux/arch/arm/mach-integrator/pci_v3.c - 1.12 linux/arch/arm/mach-integrator/time.c - 1.3 linux/drivers/scsi/aic7xxx/aic7770.c - 1.5 linux/drivers/net/wan/n2.c - 1.7 linux/arch/arm/tools/Makefile - 1.8 linux/drivers/net/sungem.c - 1.22 linux/drivers/media/radio/radio-maxiradio.c - 1.8 linux/drivers/char/machzwd.c - 1.12 linux/drivers/char/advantechwdt.c - 1.9 linux/drivers/net/wan/wanpipe_multppp.c - 1.8 linux/drivers/s390/block/dasd_9343_erp.h - 1.5 linux/drivers/s390/char/ctrlchar.c - 1.6 linux/drivers/s390/char/ctrlchar.h - 1.4 linux/drivers/s390/char/tubfs.c - 1.8 linux/drivers/s390/net/ctctty.c - 1.6 linux/drivers/s390/net/ctctty.h - 1.3 linux/drivers/sbus/char/bbc_i2c.c - 1.2 linux/drivers/net/gt96100eth.c - 1.7 linux/Documentation/s390/Debugging390.txt - 1.6 linux/drivers/video/epson1355fb.c - 1.7 linux/drivers/video/maxinefb.c - 1.8 linux/drivers/video/pmag-ba-fb.c - 1.7 linux/drivers/video/pmagb-b-fb.c - 1.7 linux/drivers/char/qtronix.c - 1.6 linux/drivers/block/paride/bpck6.c - 1.5 linux/arch/sh/kernel/hd64465_gpio.c - 1.4 linux/arch/s390/math-emu/Makefile - 1.4 linux/arch/arm/mach-ebsa110/Makefile - 1.5 linux/arch/arm/mach-ebsa110/time.c - 1.2 linux/arch/arm/mach-footbridge/irq.c - 1.4 linux/arch/arm/mach-footbridge/mm.c - 1.5 linux/include/asm-arm/proc-armv/pgalloc.h - 1.6 linux/arch/mips/mips-boards/malta/Makefile - 1.4 linux/net/ipv4/netfilter/ip_nat_helper.c - 1.6 linux/arch/mips/mips-boards/generic/Makefile - 1.5 linux/arch/mips/mips-boards/atlas/Makefile - 1.5 linux/arch/cris/drivers/gpio.c - 1.8 linux/arch/cris/drivers/i2c.c - 1.4 linux/arch/cris/drivers/sync_serial.c - 1.5 linux/arch/mips/math-emu/Makefile - 1.4 linux/arch/mips/ite-boards/qed-4n-s01b/Makefile - 1.6 linux/arch/mips/ite-boards/generic/Makefile - 1.6 linux/arch/mips/ddb5476/Makefile - 1.5 linux/arch/ia64/kernel/efivars.c - 1.8 linux/include/asm-sparc64/rwsem.h - 1.4 linux/arch/ia64/sn/io/pciba.c - 1.4 linux/include/linux/if_wanpipe_common.h - 1.3 linux/arch/sparc64/kernel/isa.c - 1.3 linux/drivers/net/fealnx.c - 1.17 linux/drivers/media/video/w9966.c - 1.6 linux/drivers/net/irda/irda-usb.c - 1.27 linux/fs/freevxfs/vxfs_inode.c - 1.11 linux/drivers/net/wireless/Makefile - 1.7 linux/fs/freevxfs/vxfs_fshead.c - 1.6 linux/drivers/net/wireless/airport.c - 1.10 linux/include/asm-sparc64/isa.h - 1.2 linux/drivers/net/wireless/orinoco.c - 1.13 linux/drivers/net/wireless/orinoco_cs.c - 1.13 linux/drivers/media/video/adv7175.c - 1.8 linux/fs/freevxfs/Makefile - 1.3 linux/fs/char_dev.c - 1.5 linux/arch/alpha/mm/numa.c - 1.7 linux/arch/ppc/boot/utils/Makefile - 1.5 linux/arch/ppc/boot/prep/misc.c - 1.11 linux/arch/ppc/boot/prep/Makefile - 1.13 linux/arch/cris/drivers/ds1302.c - 1.5 linux/arch/cris/drivers/eeprom.c - 1.7 linux/arch/ppc/boot/lib/Makefile - 1.4 linux/arch/ppc/boot/images/Makefile - 1.5 linux/arch/ppc/boot/common/Makefile - 1.5 linux/include/linux/netfilter_bridge.h - 1.4 linux/drivers/bluetooth/hci_usb.c - 1.18 linux/drivers/bluetooth/Makefile - 1.9 linux/net/bluetooth/Makefile - 1.9 linux/drivers/mtd/nand/Makefile - 1.5 linux/drivers/mtd/maps/Makefile - 1.7 linux/drivers/mtd/devices/Makefile - 1.4 linux/drivers/mtd/chips/Makefile - 1.6 linux/drivers/media/radio/miropcm20-rds.c - 1.3 linux/drivers/media/radio/miropcm20-radio.c - 1.7 linux/drivers/acpi/executer/exstore.c - 1.13 linux/drivers/acpi/utilities/utobject.c - 1.8 linux/drivers/acpi/utilities/utmisc.c - 1.11 linux/drivers/acpi/utilities/utinit.c - 1.8 linux/drivers/acpi/utilities/utglobal.c - 1.14 linux/drivers/acpi/utilities/uteval.c - 1.9 linux/drivers/acpi/utilities/utdelete.c - 1.9 linux/drivers/acpi/utilities/utdebug.c - 1.9 linux/drivers/acpi/utilities/utcopy.c - 1.11 linux/drivers/acpi/utilities/utalloc.c - 1.6 linux/drivers/acpi/utilities/Makefile - 1.5 linux/drivers/acpi/include/acstruct.h - 1.8 linux/drivers/net/wireless/airo_cs.c - 1.4 linux/drivers/usb/serial/pl2303.h - 1.6 linux/drivers/acpi/include/acutils.h - 1.12 linux/drivers/acpi/include/platform/acgcc.h - 1.9 linux/drivers/acpi/include/platform/aclinux.h - 1.9 linux/drivers/acpi/executer/exutils.c - 1.10 linux/drivers/acpi/executer/exsystem.c - 1.5 linux/drivers/acpi/executer/exstorob.c - 1.8 linux/drivers/acpi/executer/exstoren.c - 1.9 linux/drivers/acpi/executer/Makefile - 1.5 linux/drivers/acpi/executer/exconvrt.c - 1.11 linux/drivers/acpi/executer/excreate.c - 1.10 linux/drivers/acpi/executer/exdump.c - 1.13 linux/drivers/acpi/executer/exfield.c - 1.7 linux/drivers/acpi/executer/exfldio.c - 1.10 linux/drivers/acpi/executer/exmisc.c - 1.11 linux/drivers/acpi/executer/exmutex.c - 1.6 linux/drivers/acpi/executer/exnames.c - 1.6 linux/drivers/acpi/executer/exprep.c - 1.10 linux/drivers/acpi/executer/exregion.c - 1.8 linux/drivers/acpi/executer/exresnte.c - 1.13 linux/drivers/acpi/executer/exresolv.c - 1.11 linux/drivers/acpi/executer/exresop.c - 1.13 linux/arch/sh/stboards/Makefile - 1.4 linux/drivers/usb/serial/cyberjack.c - 1.21 linux/drivers/usb/serial/pl2303.c - 1.24 linux/Documentation/DocBook/procfs_example.c - 1.3 linux/drivers/isdn/tpam/tpam_main.c - 1.9 linux/drivers/isdn/tpam/tpam_commands.c - 1.6 linux/fs/sysv/itree.c - 1.10 linux/fs/sysv/super.c - 1.14 linux/arch/mips64/math-emu/Makefile - 1.4 linux/Documentation/README.nsp_cs.eng - 1.3 linux/drivers/net/irda/ali-ircc.c - 1.12 linux/drivers/scsi/pcmcia/nsp_cs.c - 1.13 linux/arch/cris/drivers/lpslave/Makefile - 1.3 linux/Documentation/sonypi.txt - 1.9 linux/Documentation/video4linux/meye.txt - 1.5 linux/include/linux/meye.h - 1.2 linux/drivers/char/sonypi.h - 1.11 linux/drivers/media/video/meye.h - 1.6 linux/drivers/media/video/meye.c - 1.12 linux/drivers/media/video/zr36067.c - 1.10 linux/drivers/net/au1000_eth.c - 1.8 linux/drivers/usb/usb-skeleton.c - 1.18 linux/drivers/net/au1000_eth.h - 1.3 linux/drivers/net/lp486e.c - 1.7 linux/include/linux/sonypi.h - 1.6 linux/drivers/char/sonypi.c - 1.11 linux/drivers/char/w83877f_wdt.c - 1.10 linux/drivers/video/pvr2fb.c - 1.7 linux/drivers/parport/parport_serial.c - 1.8 linux/drivers/net/dl2k.c - 1.20 linux/drivers/message/fusion/mptscsih.h - 1.9 linux/drivers/message/fusion/mptscsih.c - 1.13 linux/drivers/message/fusion/mptlan.h - 1.7 linux/drivers/message/fusion/mptlan.c - 1.8 linux/drivers/message/fusion/mptctl.c - 1.11 linux/drivers/message/fusion/mptbase.h - 1.8 linux/drivers/message/fusion/mptbase.c - 1.8 linux/drivers/message/fusion/Makefile - 1.10 linux/include/linux/completion.h - 1.2 linux/drivers/ieee1394/sbp2.c - 1.17 linux/drivers/ieee1394/sbp2.h - 1.12 linux/drivers/ieee1394/nodemgr.c - 1.13 linux/drivers/ieee1394/nodemgr.h - 1.7 linux/fs/partitions/ldm.c - 1.9 linux/drivers/s390/char/hwc_cpi.c - 1.5 linux/drivers/usb/storage/isd200.c - 1.12 linux/drivers/video/aty/mach64_gx.c - 1.5 linux/drivers/video/aty/Makefile - 1.6 linux/drivers/video/aty/atyfb.h - 1.4 linux/drivers/video/aty/atyfb_base.c - 1.14 linux/drivers/video/aty/mach64_ct.c - 1.4 linux/drivers/video/aty/mach64_cursor.c - 1.5 linux/drivers/media/radio/radio-gemtek-pci.c - 1.7 linux/drivers/s390/block/dasd_3370_erp.h - 1.3 linux/drivers/s390/block/dasd_int.h - 1.10 linux/drivers/s390/block/dasd_9336_erp.h - 1.3 linux/drivers/char/drm/radeon.h - 1.6 linux/drivers/char/drm/r128.h - 1.3 linux/drivers/char/drm/mga.h - 1.3 linux/drivers/char/drm/drm_vm.h - 1.14 linux/drivers/net/irda/vlsi_ir.c - 1.13 linux/arch/alpha/kernel/srm_env.c - 1.6 linux/arch/arm/mm/discontig.c - 1.2 linux/arch/arm/mach-sa1100/sa1111.c - 1.12 linux/arch/arm/mach-sa1100/sa1111-pcibuf.c - 1.6 linux/include/asm-arm/arch-anakin/memory.h - 1.3 linux/include/asm-arm/arch-anakin/vmalloc.h - 1.2 linux/arch/arm/mach-sa1100/neponset.c - 1.14 linux/arch/arm/mach-anakin/Makefile - 1.4 linux/arch/arm/mach-anakin/irq.c - 1.3 linux/arch/arm/mach-integrator/cpu.c - 1.8 linux/arch/arm/mach-sa1100/irq.c - 1.8 linux/arch/arm/mach-sa1100/graphicsclient.c - 1.12 linux/arch/arm/mach-sa1100/assabet.c - 1.15 linux/arch/arm/mach-sa1100/cpu-sa1100.c - 1.7 linux/arch/arm/mach-sa1100/cpu-sa1110.c - 1.9 linux/arch/arm/mach-sa1100/generic.h - 1.5 linux/arch/arm/mach-sa1100/generic.c - 1.12 linux/arch/arm/mach-sa1100/flexanet.c - 1.9 linux/drivers/tc/lk201.c - 1.2 linux/include/asm-ppc/cputable.h - 1.4 linux/arch/ppc/kernel/cputable.c - 1.8 linux/drivers/video/tx3912fb.c - 1.7 linux/drivers/video/sstfb.c - 1.9 linux/drivers/video/radeonfb.c - 1.12 linux/Documentation/fb/README-sstfb.txt - 1.4 linux/drivers/video/radeon.h - 1.4 linux/drivers/scsi/dpti.h - 1.6 linux/drivers/scsi/dpt_i2o.c - 1.17 linux/drivers/scsi/dpt/dpti_ioctl.h - 1.2 linux/arch/mips/au1000/common/Makefile - 1.6 linux/arch/mips/au1000/common/serial.c - 1.5 linux/arch/mips/au1000/pb1000/Makefile - 1.5 linux/arch/mips/ite-boards/ivr/Makefile - 1.5 linux/arch/mips64/sgi-ip32/Makefile - 1.5 linux/arch/mips/ddb5xxx/common/Makefile - 1.4 linux/arch/mips/ddb5xxx/ddb5477/Makefile - 1.5 linux/arch/mips/philips/nino/ramdisk/Makefile - 1.3 linux/arch/mips/gt64120/common/Makefile - 1.4 linux/arch/mips/gt64120/momenco_ocelot/Makefile - 1.5 linux/arch/mips/philips/nino/Makefile - 1.5 linux/arch/mips64/mips-boards/malta/Makefile - 1.5 linux/arch/mips64/mips-boards/atlas/Makefile - 1.5 linux/drivers/isdn/hisax/st5481_b.c - 1.7 linux/drivers/isdn/hisax/st5481_usb.c - 1.12 linux/drivers/scsi/README.53c700 - 1.3 linux/drivers/net/ns83820.c - 1.17 linux/drivers/scsi/53c700.c - 1.12 linux/drivers/scsi/NCR_D700.c - 1.4 linux/drivers/scsi/NCR_D700.h - 1.2 linux/drivers/scsi/README.dpti - 1.2 linux/drivers/scsi/lasi700.h - 1.3 linux/arch/mips64/mips-boards/generic/Makefile - 1.5 linux/include/linux/hiddev.h - 1.5 linux/fs/jffs2/Makefile - 1.7 linux/fs/jffs2/TODO - 1.4 linux/fs/jffs2/background.c - 1.15 linux/fs/jffs2/build.c - 1.4 linux/fs/jffs2/dir.c - 1.12 linux/fs/jffs2/erase.c - 1.8 linux/fs/jffs2/file.c - 1.11 linux/fs/jffs2/gc.c - 1.10 linux/fs/jffs2/nodelist.c - 1.7 linux/fs/jffs2/nodelist.h - 1.7 linux/fs/jffs2/nodemgmt.c - 1.7 linux/fs/jffs2/read.c - 1.6 linux/fs/jffs2/readinode.c - 1.7 linux/fs/jffs2/scan.c - 1.7 linux/fs/jffs2/super.c - 1.15 linux/fs/jffs2/write.c - 1.8 linux/include/linux/jffs2_fs_sb.h - 1.8 linux/include/linux/jffs2_fs_i.h - 1.4 linux/include/linux/jffs2.h - 1.5 linux/drivers/char/mwave/tp3780i.c - 1.2 linux/drivers/char/mwave/mwavedd.c - 1.5 linux/drivers/char/mwave/Makefile - 1.3 linux/fs/smbfs/proto.h - 1.7 linux/drivers/mtd/devices/blkmtd.c - 1.17 linux/fs/namespace.c - 1.24 linux/drivers/usb/serial/ir-usb.c - 1.23 linux/fs/quota.c - 1.16 linux/drivers/pcmcia/sa1100_assabet.c - 1.6 linux/drivers/char/ib700wdt.c - 1.6 linux/arch/arm/mach-sa1100/h3600.c - 1.12 linux/arch/arm/mach-sa1100/graphicsmaster.c - 1.15 linux/arch/arm/mach-sa1100/adsbitsy.c - 1.13 linux/drivers/message/i2o/i2o_scsi.c - 1.11 linux/drivers/message/i2o/i2o_pci.c - 1.6 linux/drivers/message/i2o/i2o_core.c - 1.8 linux/drivers/message/i2o/i2o_config.c - 1.7 linux/drivers/message/i2o/i2o_block.c - 1.28 linux/drivers/message/i2o/Makefile - 1.4 linux/drivers/char/shwdt.c - 1.8 linux/drivers/char/eurotechwdt.c - 1.7 linux/drivers/net/irda/ep7211_ir.c - 1.3 linux/drivers/pcmcia/i82092.c - 1.8 linux/arch/arm/mach-epxa10db/Makefile - 1.4 linux/arch/arm/mach-epxa10db/arch.c - 1.5 linux/arch/arm/mach-epxa10db/dma.c - 1.3 linux/arch/arm/mach-epxa10db/time.c - 1.2 linux/drivers/acpi/executer/exoparg3.c - 1.5 linux/drivers/acpi/executer/exoparg2.c - 1.10 linux/drivers/acpi/executer/exoparg1.c - 1.11 linux/include/asm-arm/arch-epxa10db/memory.h - 1.3 linux/arch/arm/mach-sa1100/pm.c - 1.8 linux/include/asm-arm/arch-epxa10db/vmalloc.h - 1.2 linux/net/8021q/vlan_dev.c - 1.6 linux/net/8021q/vlan.c - 1.7 linux/net/8021q/Makefile - 1.3 linux/drivers/atm/idt77252.c - 1.8 linux/drivers/scsi/sym53c8xx_2/Makefile - 1.6 linux/drivers/scsi/sym53c8xx_2/sym53c8xx.h - 1.6 linux/drivers/scsi/sym53c8xx_2/sym_glue.c - 1.10 linux/drivers/scsi/sym53c8xx_2/sym_glue.h - 1.7 linux/arch/arm/mm/proc-arm1020.S - 1.9 linux/arch/arm/mm/proc-arm926.S - 1.9 linux/fs/ext3/ialloc.c - 1.19 linux/fs/ext3/inode.c - 1.28 linux/fs/ext3/namei.c - 1.15 linux/fs/ext3/super.c - 1.28 linux/fs/intermezzo/ext_attr.c - 1.5 linux/fs/intermezzo/file.c - 1.6 linux/fs/intermezzo/inode.c - 1.7 linux/fs/intermezzo/journal.c - 1.6 linux/drivers/hotplug/pci_hotplug_core.c - 1.14 linux/drivers/hotplug/cpqphp_nvram.c - 1.5 linux/drivers/hotplug/cpqphp_core.c - 1.10 linux/drivers/hotplug/Makefile - 1.7 linux/fs/intermezzo/journal_ext2.c - 1.7 linux/fs/intermezzo/journal_ext3.c - 1.7 linux/fs/intermezzo/journal_obdfs.c - 1.7 linux/fs/intermezzo/journal_reiserfs.c - 1.7 linux/fs/intermezzo/journal_xfs.c - 1.9 linux/drivers/char/hp_psaux.c - 1.3 linux/drivers/char/hp_keyb.c - 1.2 linux/fs/intermezzo/kml.c - 1.3 linux/fs/intermezzo/kml_decode.c - 1.2 linux/fs/intermezzo/kml_reint.c - 1.6 linux/fs/intermezzo/kml_setup.c - 1.2 linux/fs/intermezzo/kml_utils.c - 1.3 linux/fs/intermezzo/methods.c - 1.7 linux/fs/intermezzo/presto.c - 1.10 linux/fs/intermezzo/psdev.c - 1.9 linux/fs/intermezzo/super.c - 1.9 linux/fs/intermezzo/sysctl.c - 1.7 linux/fs/intermezzo/upcall.c - 1.6 linux/fs/intermezzo/vfs.c - 1.12 linux/include/linux/intermezzo_upcall.h - 1.2 linux/include/linux/intermezzo_psdev.h - 1.4 linux/include/linux/intermezzo_kml.h - 1.2 linux/include/linux/intermezzo_journal.h - 1.2 linux/include/linux/intermezzo_fs.h - 1.7 linux/include/linux/ext3_fs.h - 1.13 linux/fs/reiserfs/procfs.c - 1.11 linux/fs/ext3/balloc.c - 1.10 linux/drivers/scsi/sym53c8xx_2/ChangeLog.txt - 1.3 linux/drivers/scsi/sym53c8xx_2/Documentation.txt - 1.2 linux/fs/ext3/Makefile - 1.6 linux/fs/jbd/Makefile - 1.3 linux/fs/intermezzo/cache.c - 1.8 linux/fs/intermezzo/Makefile - 1.4 linux/fs/intermezzo/dir.c - 1.9 linux/fs/intermezzo/dcache.c - 1.7 linux/drivers/net/pcmcia/axnet_cs.c - 1.5 linux/drivers/isdn/hisax/hisax_fcpcipnp.c - 1.8 linux/include/linux/device.h - 1.24 linux/init/do_mounts.c - 1.22 linux/mm/mempool.c - 1.14 linux/drivers/usb/serial/ipaq.c - 1.17 linux/drivers/usb/serial/kl5kusb105.c - 1.16 linux/arch/arm/mach-iop310/arch.c - 1.5 linux/arch/arm/mm/proc-xscale.S - 1.10 linux/arch/arm/mm/proc-arm922.S - 1.8 linux/arch/arm/mm/alignment.c - 1.6 linux/arch/arm/mach-tbox/core.c - 1.3 linux/arch/arm/mach-tbox/Makefile - 1.4 linux/arch/arm/mach-sa1100/system3.c - 1.13 linux/include/asm-arm/arch-adifcc/memory.h - 1.3 linux/include/asm-arm/arch-iop310/vmalloc.h - 1.2 linux/include/asm-arm/arch-iop310/memory.h - 1.4 linux/arch/arm/mach-adifcc/Makefile - 1.4 linux/arch/arm/mach-adifcc/arch.c - 1.5 linux/arch/arm/mach-adifcc/irq.c - 1.3 linux/arch/arm/mach-arc/Makefile - 1.4 linux/arch/arm/mach-arc/dma.c - 1.5 linux/arch/arm/mach-arc/oldlatches.c - 1.2 linux/arch/arm/mach-clps711x/Makefile - 1.6 linux/arch/arm/mach-clps711x/autcpu12.c - 1.4 linux/arch/arm/mach-clps711x/cdb89712.c - 1.6 linux/arch/arm/mach-clps711x/dma.c - 1.3 linux/arch/arm/mach-clps711x/mm.c - 1.3 linux/arch/arm/mach-clps711x/p720t.c - 1.4 linux/arch/arm/mach-clps711x/time.c - 1.3 linux/arch/arm/mach-clps7500/Makefile - 1.4 linux/include/asm-arm/arch-adifcc/vmalloc.h - 1.2 linux/arch/arm/mach-ftvpci/Makefile - 1.4 linux/arch/arm/mach-ftvpci/core.c - 1.4 linux/arch/arm/mach-iop310/Makefile - 1.4 linux/arch/arm/mach-iop310/iop310-irq.c - 1.5 linux/arch/arm/mach-iop310/iop310-pci.c - 1.7 linux/arch/arm/mach-iop310/iq80310-irq.c - 1.5 linux/arch/arm/mach-iop310/iq80310-time.c - 1.7 linux/arch/arm/mach-iop310/xs80200-irq.c - 1.5 linux/arch/arm/mach-l7200/Makefile - 1.4 linux/arch/arm/mach-rpc/Makefile - 1.4 linux/include/asm-arm/arch-clps711x/vmalloc.h - 1.2 linux/include/asm-arm/arch-clps711x/memory.h - 1.6 linux/arch/arm/mach-sa1100/dma.c - 1.3 linux/arch/arm/mach-footbridge/dma.c - 1.3 linux/arch/arm/mach-footbridge/dc21285.c - 1.4 linux/arch/arm/mach-rpc/dma.c - 1.5 linux/drivers/block/cciss_scsi.c - 1.7 linux/drivers/net/Makefile.lib - 1.3 linux/drivers/ide/ide-taskfile.c - 1.26 linux/drivers/ieee1394/dv1394-private.h - 1.6 linux/drivers/ieee1394/dv1394.c - 1.10 linux/net/core/wireless.c - 1.5 linux/fs/ext2/ext2.h - 1.9 linux/drivers/net/wireless/netwave_cs.c - 1.5 linux/drivers/isdn/hisax/hisax_hscx.c - 1.2 linux/drivers/video/neofb.c - 1.11 linux/drivers/base/interface.c - 1.11 linux/drivers/base/core.c - 1.20 linux/drivers/base/Makefile - 1.10 linux/drivers/pci/pci-driver.c - 1.13 linux/fs/xattr.c - 1.11 linux/lib/zlib_inflate/Makefile - 1.3 linux/lib/zlib_deflate/Makefile - 1.3 linux/include/linux/pnpbios.h - 1.6 linux/drivers/input/joystick/Makefile - 1.6 linux/drivers/input/gameport/ns558.c - 1.5 linux/drivers/input/gameport/emu10k1-gp.c - 1.6 linux/drivers/input/gameport/Makefile - 1.4 linux/include/linux/thread_info.h - 1.3 linux/drivers/input/serio/Makefile - 1.6 linux/drivers/input/serio/serio.c - 1.7 linux/include/asm-i386/thread_info.h - 1.6 linux/include/asm-sparc64/thread_info.h - 1.5 linux/sound/synth/emux/emux.c - 1.4 linux/sound/synth/emux/Makefile - 1.5 linux/sound/synth/Makefile - 1.7 linux/sound/sound_core.c - 1.6 linux/sound/ppc/Makefile - 1.5 linux/sound/pci/ymfpci/ymfpci_main.c - 1.9 linux/sound/pci/ymfpci/Makefile - 1.4 linux/sound/pci/trident/trident_main.c - 1.7 linux/sound/pci/trident/Makefile - 1.4 linux/sound/pci/sonicvibes.c - 1.9 linux/sound/pci/rme9652/rme9652.c - 1.12 linux/sound/pci/rme9652/Makefile - 1.5 linux/sound/pci/rme96.c - 1.11 linux/sound/pci/nm256/Makefile - 1.4 linux/sound/pci/korg1212/korg1212.c - 1.12 linux/sound/pci/korg1212/Makefile - 1.4 linux/arch/ppc/4xx_io/Makefile - 1.4 linux/sound/pci/fm801.c - 1.9 linux/sound/pci/es1938.c - 1.9 linux/arch/ppc/8xx_io/cs4218_tdm.c - 1.4 linux/sound/pci/emu10k1/emu10k1_main.c - 1.7 linux/sound/pci/emu10k1/Makefile - 1.5 linux/sound/pci/cs46xx/cs46xx_lib.c - 1.9 linux/sound/pci/cs46xx/Makefile - 1.5 linux/sound/pci/cs4281.c - 1.12 linux/sound/pci/ali5451/Makefile - 1.4 linux/sound/pci/ac97/Makefile - 1.9 linux/sound/pci/Makefile - 1.8 linux/sound/oss/ymfpci.c - 1.3 linux/sound/oss/wf_midi.c - 1.3 linux/sound/oss/vidc_fill.S - 1.3 linux/arch/ppc/boot/simple/Makefile - 1.9 linux/sound/oss/vidc.c - 1.4 linux/sound/oss/via82cxxx_audio.c - 1.8 linux/sound/oss/uart6850.c - 1.4 linux/sound/oss/uart401.c - 1.3 linux/sound/oss/trident.c - 1.8 linux/sound/oss/soundcard.c - 1.5 linux/sound/oss/sonicvibes.c - 1.5 linux/sound/oss/sb_ess.c - 1.2 linux/sound/oss/sb_common.c - 1.3 linux/sound/oss/sb_card.c - 1.3 linux/sound/oss/sb_audio.c - 1.4 linux/sound/oss/rme96xx.c - 1.5 linux/arch/ppc/iSeries/Makefile - 1.4 linux/sound/oss/pss.c - 1.4 linux/sound/oss/pas2_card.c - 1.3 linux/sound/oss/opl3sa2.c - 1.5 linux/sound/oss/nm256_audio.c - 1.3 linux/sound/oss/mpu401.h - 1.3 linux/sound/oss/mpu401.c - 1.4 linux/sound/oss/maui.c - 1.2 linux/sound/oss/maestro3.c - 1.6 linux/sound/oss/maestro.c - 1.5 linux/sound/oss/i810_audio.c - 1.8 linux/sound/oss/gus_wave.c - 1.4 linux/sound/oss/gus_card.c - 1.3 linux/sound/oss/esssolo1.c - 1.6 linux/sound/oss/es1371.c - 1.6 linux/sound/oss/es1370.c - 1.6 linux/sound/oss/emu10k1/Makefile - 1.4 linux/sound/oss/dmasound/Makefile - 1.4 linux/arch/ppc/platforms/Makefile - 1.9 linux/arch/ppc/platforms/pmac_pic.c - 1.7 linux/arch/ppc/platforms/residual.c - 1.4 linux/sound/oss/cs46xx.c - 1.6 linux/sound/oss/cs4281/cs4281pm-24.c - 1.2 linux/sound/oss/cs4281/cs4281m.c - 1.5 linux/sound/oss/cs4281/cs4281_wrapper-24.c - 1.2 linux/sound/oss/cs4281/Makefile - 1.4 linux/sound/oss/cs4232.c - 1.4 linux/sound/oss/cmpci.c - 1.4 linux/arch/x86_64/boot/Makefile - 1.9 linux/arch/x86_64/boot/compressed/Makefile - 1.4 linux/arch/x86_64/ia32/Makefile - 1.8 linux/arch/x86_64/ia32/sys_ia32.c - 1.10 linux/arch/x86_64/kernel/Makefile - 1.10 linux/arch/x86_64/kernel/ptrace.c - 1.6 linux/arch/x86_64/lib/Makefile - 1.8 linux/arch/x86_64/mm/Makefile - 1.4 linux/sound/oss/ad1848.c - 1.6 linux/sound/oss/ad1816.c - 1.3 linux/sound/oss/ac97_codec.c - 1.4 linux/sound/oss/Makefile - 1.9 linux/sound/isa/wavefront/wavefront_midi.c - 1.5 linux/sound/isa/wavefront/wavefront.c - 1.9 linux/sound/isa/wavefront/Makefile - 1.5 linux/sound/isa/sb/sb_common.c - 1.8 linux/sound/isa/sb/sb8_midi.c - 1.4 linux/sound/isa/sb/Makefile - 1.9 linux/sound/isa/opti9xx/Makefile - 1.4 linux/sound/isa/opl3sa2.c - 1.12 linux/sound/isa/gus/gus_main.c - 1.5 linux/sound/isa/gus/Makefile - 1.6 linux/sound/isa/es1688/es1688_lib.c - 1.5 linux/sound/isa/es1688/Makefile - 1.4 linux/sound/isa/cs423x/cs4236.c - 1.10 linux/sound/isa/cs423x/cs4231_lib.c - 1.8 linux/sound/isa/cs423x/Makefile - 1.6 linux/sound/isa/ad1848/ad1848_lib.c - 1.8 linux/sound/isa/ad1848/Makefile - 1.6 linux/sound/isa/ad1816a/ad1816a_lib.c - 1.6 linux/sound/isa/ad1816a/Makefile - 1.4 linux/sound/isa/Makefile - 1.8 linux/sound/i2c/Makefile - 1.8 linux/sound/drivers/serial-u16550.c - 1.11 linux/sound/drivers/opl3/opl3_seq.c - 1.5 linux/sound/drivers/opl3/Makefile - 1.8 linux/sound/drivers/mtpav.c - 1.9 linux/sound/drivers/mpu401/mpu401_uart.c - 1.8 linux/sound/drivers/mpu401/Makefile - 1.9 linux/sound/drivers/dummy.c - 1.10 linux/sound/drivers/Makefile - 1.6 linux/sound/core/sound.c - 1.11 linux/sound/core/seq/oss/Makefile - 1.7 linux/sound/core/seq/instr/Makefile - 1.9 linux/sound/core/seq/Makefile - 1.15 linux/sound/core/pcm_native.c - 1.11 linux/sound/core/oss/Makefile - 1.5 linux/sound/core/info.c - 1.10 linux/sound/core/Makefile - 1.15 linux/sound/Makefile - 1.12 linux/include/sound/initval.h - 1.3 linux/include/sound/core.h - 1.14 linux/include/asm-x86_64/signal.h - 1.4 linux/include/asm-ppc/thread_info.h - 1.7 linux/include/asm-x86_64/stat.h - 1.2 linux/include/asm-alpha/thread_info.h - 1.4 linux/include/asm-x86_64/unistd.h - 1.9 linux/include/asm-ppc64/hardirq.h - 1.8 linux/arch/ppc64/mm/init.c - 1.12 linux/include/asm-ppc64/errno.h - 1.3 linux/include/asm-ppc64/eeh.h - 1.4 linux/include/asm-ppc64/io.h - 1.4 linux/arch/ppc64/Makefile - 1.13 linux/arch/ppc64/defconfig - 1.12 linux/arch/ppc64/kernel/LparData.c - 1.6 linux/arch/ppc64/kernel/Makefile - 1.10 linux/arch/ppc64/kernel/binfmt_elf32.c - 1.3 linux/arch/ppc64/kernel/chrp_setup.c - 1.9 linux/arch/ppc64/kernel/eeh.c - 1.6 linux/arch/ppc64/kernel/entry.S - 1.10 linux/arch/ppc64/kernel/htab.c - 1.8 linux/arch/ppc64/kernel/iSeries_pci.c - 1.7 linux/arch/ppc64/kernel/ioctl32.c - 1.11 linux/arch/ppc64/kernel/mf.c - 1.3 linux/arch/ppc64/kernel/misc.S - 1.11 linux/arch/ppc64/kernel/open_pic.c - 1.7 linux/arch/ppc64/kernel/pSeries_pci.c - 1.8 linux/arch/ppc64/kernel/pci.c - 1.9 linux/arch/ppc64/kernel/pci.h - 1.4 linux/arch/ppc64/kernel/pci_dma.c - 1.6 linux/arch/ppc64/kernel/pci_dn.c - 1.6 linux/arch/ppc64/kernel/ppc_ksyms.c - 1.8 linux/arch/ppc64/kernel/process.c - 1.10 linux/arch/ppc64/kernel/prom.c - 1.9 linux/arch/ppc64/kernel/ptrace.c - 1.6 linux/arch/ppc64/kernel/ptrace32.c - 1.7 linux/arch/ppc64/kernel/setup.c - 1.9 linux/arch/ppc64/kernel/signal.c - 1.11 linux/arch/ppc64/kernel/signal32.c - 1.10 linux/arch/ppc64/kernel/smp.c - 1.11 linux/arch/ppc64/kernel/sys32.S - 1.5 linux/arch/ppc64/kernel/sys_ppc32.c - 1.12 linux/arch/ppc64/kernel/time.c - 1.9 linux/arch/ppc64/kernel/traps.c - 1.9 linux/arch/ppc64/kernel/xics.c - 1.8 linux/arch/ppc64/lib/Makefile - 1.6 linux/arch/ppc64/mm/Makefile - 1.4 linux/arch/ppc64/xmon/Makefile - 1.3 linux/include/asm-ppc64/hw_irq.h - 1.6 linux/include/asm-ppc64/iSeries/HvCall.h - 1.4 linux/include/asm-ppc64/unistd.h - 1.10 linux/include/asm-ppc64/thread_info.h - 1.6 linux/include/asm-ppc64/system.h - 1.8 linux/include/asm-ppc64/stat.h - 1.3 linux/include/asm-ppc64/ppc32.h - 1.3 linux/include/asm-ppc64/prom.h - 1.4 linux/include/asm-ppc64/pci.h - 1.3 linux/include/asm-ppc64/pci-bridge.h - 1.4 linux/include/asm-ppc64/page.h - 1.9 linux/drivers/net/e1000/Makefile - 1.6 linux/drivers/isdn/hisax/hisax_hfcpci.c - 1.4 linux/drivers/net/tokenring/3c359.c - 1.5 linux/drivers/net/e1000/e1000_param.c - 1.6 linux/fs/jfs/jfs_metapage.h - 1.7 linux/drivers/hotplug/ibmphp_ebda.c - 1.5 linux/fs/jfs/Makefile - 1.6 linux/fs/jfs/file.c - 1.14 linux/fs/jfs/inode.c - 1.19 linux/fs/jfs/jfs_debug.c - 1.5 linux/fs/jfs/jfs_dtree.c - 1.11 linux/fs/jfs/jfs_inode.c - 1.5 linux/fs/jfs/jfs_incore.h - 1.14 linux/fs/jfs/jfs_imap.c - 1.11 linux/arch/arm/mach-clps711x/fortunet.c - 1.3 linux/fs/jfs/namei.c - 1.14 linux/arch/arm/mach-sa1100/stork.c - 1.5 linux/fs/jfs/jfs_xtree.c - 1.7 linux/arch/arm/mach-footbridge/isa-irq.c - 1.4 linux/fs/jfs/jfs_logmgr.c - 1.21 linux/fs/jfs/super.c - 1.18 linux/arch/arm/mm/tlb-v4wb.S - 1.6 linux/fs/jfs/jfs_txnmgr.c - 1.20 linux/fs/jfs/jfs_metapage.c - 1.12 linux/fs/quota_v2.c - 1.7 linux/drivers/net/tg3.h - 1.12 linux/sound/core/ioctl32/timer32.c - 1.5 linux/drivers/net/tg3.c - 1.14 linux/sound/core/ioctl32/rawmidi32.c - 1.5 linux/drivers/pcmcia/sa1111_generic.c - 1.5 linux/drivers/net/tulip/de2104x.c - 1.7 linux/drivers/net/tulip/de4x5.c - 1.7 linux/drivers/net/tulip/dmfe.c - 1.4 linux/drivers/net/tulip/winbond-840.c - 1.7 linux/drivers/pcmcia/sa1100_badge4.c - 1.5 linux/drivers/net/tulip/xircom_cb.c - 1.5 linux/sound/core/ioctl32/ioctl32.c - 1.7 linux/drivers/net/wan/hdlc_x25.c - 1.4 linux/drivers/net/wan/hdlc_cisco.c - 1.4 linux/sound/core/ioctl32/Makefile - 1.6 linux/drivers/net/wan/hdlc_fr.c - 1.4 linux/drivers/net/wan/hdlc_generic.c - 1.4 linux/drivers/net/wan/hdlc_ppp.c - 1.4 linux/drivers/net/e100/Makefile - 1.4 linux/drivers/net/wan/hdlc_raw.c - 1.4 linux/drivers/net/e100/e100_main.c - 1.11 linux/fs/jffs2/writev.c - 1.3 linux/arch/ia64/sn/kernel/sn2/Makefile - 1.5 linux/arch/ia64/sn/kernel/sn1/synergy.c - 1.2 linux/arch/ia64/sn/kernel/sn1/Makefile - 1.5 linux/fs/jffs2/wbuf.c - 1.4 linux/fs/jffs2/os-linux.h - 1.5 linux/kernel/futex.c - 1.13 linux/fs/jffs2/fs.c - 1.5 linux/arch/ia64/kernel/salinfo.c - 1.2 linux/arch/ia64/sn/kernel/Makefile - 1.5 linux/arch/ia64/sn/fakeprom/Makefile - 1.5 linux/fs/nfsctl.c - 1.4 linux/drivers/media/video/video-buf.c - 1.6 linux/fs/udf/osta_udf.h - 1.2 linux/arch/i386/kernel/acpi_wakeup.S - 1.6 linux/drivers/acpi/acpi_drivers.h - 1.7 linux/drivers/media/video/bttv-vbi.c - 1.5 linux/drivers/net/wan/comx-hw-munich.c - 1.7 linux/fs/libfs.c - 1.10 linux/sound/core/ioctl32/seq32.c - 1.4 linux/lib/radix-tree.c - 1.8 linux/drivers/ieee1394/eth1394.c - 1.4 linux/Documentation/BK-usage/unbz64wrap - 1.2 linux/drivers/net/tc35815.c - 1.6 linux/drivers/ide/ide-tcq.c - 1.5 linux/drivers/usb/image/Makefile - 1.5 linux/drivers/usb/class/Makefile - 1.6 linux/drivers/usb/image/microtek.c - 1.6 linux/drivers/usb/class/audio.c - 1.10 linux/drivers/usb/class/bluetty.c - 1.12 linux/drivers/usb/class/cdc-acm.c - 1.11 linux/drivers/usb/core/Makefile - 1.10 linux/drivers/usb/core/devio.c - 1.13 linux/drivers/usb/core/hcd.c - 1.14 linux/drivers/usb/core/hcd.h - 1.10 linux/drivers/usb/core/hub.c - 1.16 linux/drivers/usb/core/inode.c - 1.11 linux/include/asm-arm/arch-pxa/vmalloc.h - 1.2 linux/include/asm-arm/arch-pxa/pxa-regs.h - 1.4 linux/include/asm-arm/arch-pxa/memory.h - 1.3 linux/drivers/usb/input/hid-core.c - 1.11 linux/drivers/usb/core/usb.c - 1.23 linux/drivers/usb/host/Makefile - 1.9 linux/drivers/usb/media/konicawc.c - 1.8 linux/drivers/usb/host/ehci-dbg.c - 1.8 linux/arch/arm/mach-pxa/Makefile - 1.5 linux/arch/arm/mach-pxa/dma.c - 1.3 linux/arch/arm/mach-pxa/idp.c - 1.6 linux/arch/arm/mach-pxa/irq.c - 1.3 linux/arch/arm/mach-pxa/lubbock.c - 1.6 linux/drivers/usb/media/pwc-misc.c - 1.2 linux/drivers/usb/host/ehci-hcd.c - 1.13 linux/drivers/usb/host/ehci-hub.c - 1.6 linux/drivers/usb/host/ehci-mem.c - 1.4 linux/drivers/usb/host/ehci-q.c - 1.13 linux/drivers/usb/host/ehci-sched.c - 1.11 linux/drivers/usb/host/ehci.h - 1.6 linux/drivers/usb/host/ohci-dbg.c - 1.9 linux/drivers/usb/host/ohci-hcd.c - 1.14 linux/drivers/usb/host/ohci-mem.c - 1.8 linux/drivers/usb/host/ohci-q.c - 1.16 linux/drivers/usb/host/ohci.h - 1.9 linux/drivers/usb/media/stv680.c - 1.9 linux/drivers/base/sys.c - 1.7 linux/drivers/base/power.c - 1.7 linux/drivers/base/base.h - 1.12 linux/drivers/usb/media/usbvideo.c - 1.10 linux/drivers/usb/image/hpusbscsi.c - 1.8 linux/drivers/usb/image/hpusbscsi.h - 1.3 linux/drivers/usb/image/mdc800.c - 1.9 linux/drivers/ieee1394/cmp.c - 1.4 linux/drivers/usb/image/microtek.h - 1.3 linux/drivers/usb/image/scanner.c - 1.13 linux/drivers/usb/image/scanner.h - 1.8 linux/drivers/usb/input/Makefile - 1.7 linux/drivers/ieee1394/amdtp.c - 1.5 linux/drivers/usb/input/hid-debug.h - 1.3 linux/drivers/usb/input/hid-input.c - 1.5 linux/drivers/usb/input/hid.h - 1.5 linux/drivers/usb/input/hiddev.c - 1.11 linux/drivers/usb/input/usbkbd.c - 1.7 linux/drivers/usb/input/usbmouse.c - 1.6 linux/drivers/usb/input/wacom.c - 1.8 linux/drivers/usb/media/Makefile - 1.6 linux/drivers/usb/media/dabusb.c - 1.11 linux/drivers/usb/media/dsbr100.c - 1.5 linux/drivers/usb/media/ov511.c - 1.9 linux/drivers/usb/media/ov511.h - 1.5 linux/drivers/usb/media/pwc-ctrl.c - 1.3 linux/drivers/usb/media/pwc-if.c - 1.7 linux/drivers/video/clps711xfb.c - 1.8 linux/drivers/video/anakinfb.c - 1.7 linux/drivers/usb/media/pwc-uncompress.c - 1.2 linux/drivers/usb/media/pwc-uncompress.h - 1.2 linux/drivers/usb/media/pwc.h - 1.3 linux/drivers/usb/serial/safe_serial.c - 1.9 linux/drivers/usb/media/se401.c - 1.11 linux/drivers/usb/net/usbnet.c - 1.14 linux/drivers/usb/net/rtl8150.c - 1.10 linux/drivers/usb/net/pegasus.h - 1.9 linux/drivers/usb/net/pegasus.c - 1.10 linux/drivers/usb/media/vicam.c - 1.8 linux/drivers/usb/net/kaweth.c - 1.11 linux/drivers/usb/net/cdc-ether.c - 1.9 linux/drivers/usb/net/catc.c - 1.6 linux/drivers/usb/net/Makefile - 1.4 linux/mm/readahead.c - 1.13 linux/mm/pdflush.c - 1.9 linux/drivers/usb/misc/Makefile - 1.6 linux/drivers/usb/misc/auerswald.c - 1.10 linux/drivers/usb/misc/tiglusb.c - 1.10 linux/drivers/usb/misc/tiglusb.h - 1.3 linux/drivers/isdn/i4l/isdn_ppp.c - 1.12 linux/fs/exportfs/Makefile - 1.3 linux/drivers/isdn/i4l/isdn_common.c - 1.11 linux/arch/ia64/hp/zx1/Makefile - 1.4 linux/arch/ia64/hp/sim/simscsi.c - 1.6 linux/arch/ia64/hp/sim/Makefile - 1.3 linux/arch/ia64/hp/common/Makefile - 1.4 linux/drivers/usb/misc/brlvger.c - 1.9 linux/drivers/isdn/capi/capi.c - 1.7 linux/drivers/isdn/capi/capidrv.c - 1.3 linux/drivers/video/fbcon-accel.h - 1.3 linux/fs/ntfs/time.c - 1.2 linux/drivers/scsi/scsi_mid_low_api.txt - 1.6 linux/sound/i2c/l3/Makefile - 1.3 linux/sound/pci/rme32.c - 1.7 linux/sound/arm/Makefile - 1.4 linux/drivers/char/pcmcia/synclink_cs.c - 1.6 linux/sound/arm/sa11xx-uda1341.c - 1.7 linux/fs/ntfs/aops.c - 1.11 linux/drivers/video/fbcon-accel.c - 1.4 linux/drivers/block/umem.c - 1.17 linux/drivers/bluetooth/bluecard_cs.c - 1.6 linux/drivers/usb/host/uhci-hcd.c - 1.14 linux/drivers/macintosh/ans-lcd.c - 1.2 linux/drivers/usb/host/uhci-hcd.h - 1.5 linux/arch/i386/pci/Makefile - 1.4 linux/drivers/macintosh/apm_emu.c - 1.3 linux/drivers/message/Makefile - 1.4 linux/drivers/net/irda/mcp2120.c - 1.4 linux/drivers/net/wan/pc300_drv.c - 1.5 linux/drivers/net/wan/pc300_tty.c - 1.4 linux/arch/i386/pci/direct.c - 1.5 linux/drivers/net/wireless/orinoco_pci.c - 1.4 linux/net/ipv6/ipv6_syms.c - 1.3 linux/drivers/pci/probe.c - 1.9 linux/fs/fs-writeback.c - 1.11 linux/arch/i386/pci/numa.c - 1.5 linux/include/linux/page-flags.h - 1.16 linux/drivers/bluetooth/dtl1_cs.c - 1.5 linux/drivers/bluetooth/hci_h4.c - 1.7 linux/mm/page-writeback.c - 1.16 linux/include/linux/buffer_head.h - 1.14 linux/include/linux/backing-dev.h - 1.4 linux/init/Makefile - 1.12 linux/arch/sparc/kernel/apc.c - 1.3 linux/include/linux/writeback.h - 1.11 linux/include/asm-i386/suspend.h - 1.5 linux/Documentation/block/biodoc.txt - 1.2 linux/kernel/suspend.c - 1.18 linux/drivers/video/cfbcopyarea.c - 1.4 linux/drivers/base/bus.c - 1.9 linux/drivers/char/drm/i830_drv.h - 1.3 linux/drivers/char/drm/i830_dma.c - 1.5 linux/drivers/base/driver.c - 1.8 linux/drivers/usb/host/hc_simple.c - 1.5 linux/drivers/usb/host/hc_sl811_rh.c - 1.4 linux/drivers/video/cfbfillrect.c - 1.3 linux/drivers/video/cfbimgblt.c - 1.4 linux/drivers/video/tridentfb.c - 1.3 linux/include/linux/suspend.h - 1.7 linux/drivers/video/pm3fb.c - 1.3 linux/fs/mpage.c - 1.15 linux/drivers/usb/storage/raw_bulk.c - 1.6 linux/drivers/acpi/pci_bind.c - 1.4 linux/drivers/usb/core/message.c - 1.12 linux/drivers/acpi/ac.c - 1.6 linux/drivers/usb/core/config.c - 1.3 linux/drivers/acpi/battery.c - 1.7 linux/drivers/acpi/bus.c - 1.10 linux/drivers/acpi/fan.c - 1.5 linux/drivers/acpi/button.c - 1.6 linux/drivers/acpi/pci_irq.c - 1.9 linux/drivers/acpi/thermal.c - 1.8 linux/drivers/acpi/processor.c - 1.11 linux/drivers/acpi/osl.c - 1.9 linux/drivers/s390/cio/cio_debug.h - 1.3 linux/include/asm-s390/tlbflush.h - 1.3 linux/drivers/s390/cio/ioinfo.c - 1.3 linux/include/asm-s390x/rwsem.h - 1.3 linux/include/asm-s390x/qdio.h - 1.3 linux/drivers/s390/cio/cio_debug.c - 1.3 linux/drivers/s390/cio/cio.h - 1.2 linux/drivers/isdn/hisax/amd7930_fn.c - 1.6 linux/drivers/isdn/hisax/enternow_pci.c - 1.4 linux/drivers/isdn/hisax/ipacx.c - 1.7 linux/drivers/isdn/hisax/ipacx.h - 1.2 linux/drivers/usb/host/ohci-sa1111.c - 1.9 linux/drivers/usb/class/usb-midi.c - 1.7 linux/drivers/s390/cio/blacklist.c - 1.3 linux/include/asm-s390x/thread_info.h - 1.3 linux/drivers/s390/cio/ioinfo.h - 1.2 linux/drivers/s390/cio/airq.h - 1.2 linux/drivers/s390/cio/airq.c - 1.3 linux/drivers/usb/class/usb-midi.h - 1.2 linux/drivers/s390/cio/misc.c - 1.3 linux/drivers/s390/cio/Makefile - 1.4 linux/include/asm-s390x/tlbflush.h - 1.3 linux/drivers/s390/qdio.c - 1.4 linux/drivers/s390/net/lcs.c - 1.6 linux/drivers/s390/cio/misc.h - 1.2 linux/drivers/s390/cio/chsc.c - 1.3 linux/drivers/s390/cio/proc.c - 1.3 linux/drivers/usb/core/hcd-pci.c - 1.6 linux/drivers/s390/cio/s390io.h - 1.2 linux/arch/i386/kernel/suspend.c - 1.8 linux/include/video/neomagic.h - 1.2 linux/drivers/s390/cio/s390io.c - 1.4 linux/include/asm-s390/thread_info.h - 1.3 linux/arch/i386/kernel/cpu/umc.c - 1.3 linux/include/asm-s390/rwsem.h - 1.3 linux/arch/i386/kernel/cpu/rise.c - 1.3 linux/include/asm-s390/qdio.h - 1.3 linux/drivers/usb/host/ohci-pci.c - 1.5 linux/arch/i386/kernel/cpu/nexgen.c - 1.3 linux/arch/i386/kernel/cpu/intel.c - 1.10 linux/drivers/s390/cio/cio.c - 1.4 linux/arch/i386/kernel/cpu/cyrix.c - 1.5 linux/drivers/s390/cio/chsc.h - 1.3 linux/drivers/s390/block/dasd_devmap.c - 1.3 linux/drivers/s390/block/dasd_genhd.c - 1.13 linux/drivers/s390/block/dasd_ioctl.c - 1.7 linux/drivers/s390/cio/proc.h - 1.2 linux/drivers/s390/char/tape_idalbuf.h - 1.2 linux/drivers/s390/cio/requestirq.c - 1.3 linux/arch/i386/kernel/cpu/Makefile - 1.5 linux/arch/i386/kernel/cpu/amd.c - 1.7 linux/drivers/usb/input/aiptek.c - 1.8 linux/drivers/net/irda/act200l.c - 1.4 linux/drivers/net/irda/ma600.c - 1.3 linux/arch/x86_64/pci/Makefile - 1.3 linux/arch/arm/mm/proc-arm6_7.S - 1.4 linux/net/llc/Makefile - 1.6 linux/net/llc/llc_main.c - 1.9 linux/sound/pci/rme9652/hdsp.c - 1.6 linux/drivers/message/fusion/mptctl.h - 1.3 linux/sound/pci/rme9652/hammerfall_mem.c - 1.5 linux/drivers/input/keyboard/atkbd.c - 1.8 linux/drivers/input/tsdev.c - 1.5 linux/drivers/input/touchscreen/Makefile - 1.3 linux/drivers/input/serio/rpckbd.c - 1.5 linux/drivers/input/serio/i8042.c - 1.8 linux/drivers/input/serio/ct82c710.c - 1.4 linux/drivers/input/evbug.c - 1.5 linux/drivers/input/gameport/fm801-gp.c - 1.3 linux/drivers/input/gameport/vortex.c - 1.3 linux/drivers/input/mouse/rpcmouse.c - 1.6 linux/drivers/input/mouse/psmouse.c - 1.8 linux/drivers/input/mouse/pc110pad.c - 1.3 linux/drivers/input/joystick/iforce/Makefile - 1.4 linux/drivers/input/mouse/logibm.c - 1.4 linux/drivers/input/mouse/inport.c - 1.4 linux/drivers/input/mouse/Makefile - 1.3 linux/drivers/input/keyboard/Makefile - 1.4 linux/drivers/acpi/tables/tbrsdt.c - 1.5 linux/drivers/acpi/toshiba_acpi.c - 1.3 linux/drivers/acpi/tables/tbgetall.c - 1.4 linux/fs/direct-io.c - 1.13 linux/include/asm-arm/suspend.h - 1.2 linux/drivers/usb/input/pid.c - 1.2 linux/drivers/usb/input/powermate.c - 1.7 linux/drivers/usb/input/xpad.c - 1.6 linux/fs/smbfs/smbiod.c - 1.4 linux/fs/smbfs/request.h - 1.2 linux/fs/smbfs/request.c - 1.3 linux/security/security.c - 1.4 linux/security/dummy.c - 1.5 linux/security/capability.c - 1.5 linux/security/Makefile - 1.2 linux/drivers/usb/serial/io_ti.c - 1.6 linux/drivers/serial/uart00.c - 1.5 linux/drivers/serial/core.c - 1.6 linux/drivers/char/agp/agp.c - 1.6 linux/drivers/char/agp/ali-agp.c - 1.2 linux/drivers/char/agp/amd-agp.c - 1.2 linux/drivers/char/agp/sis-agp.c - 1.2 linux/drivers/char/agp/frontend.c - 1.2 linux/drivers/char/agp/hp-agp.c - 1.2 linux/drivers/char/agp/i460-agp.c - 1.2 linux/drivers/char/agp/i810-agp.c - 1.2 linux/drivers/char/agp/i8x0-agp.c - 1.3 linux/drivers/acpi/namespace/nsxfeval.c - 1.4 linux/drivers/serial/Makefile - 1.7 linux/drivers/acpi/include/acdisasm.h - 1.4 linux/mm/rmap.c - 1.9 linux/drivers/serial/8250_pnp.c - 1.3 linux/drivers/serial/8250_pci.c - 1.5 linux/drivers/char/agp/sworks-agp.c - 1.2 linux/drivers/char/agp/via-agp.c - 1.2 linux/drivers/serial/8250.c - 1.11 linux/include/linux/serial_core.h - 1.8 linux/include/linux/security.h - 1.5 linux/arch/ppc64/kernel/rtas_flash.c - 1.4 linux/drivers/bluetooth/bt3c_cs.c - 1.5 linux/drivers/base/fs/Makefile - 1.5 linux/drivers/base/fs/device.c - 1.5 linux/drivers/serial/sunzilog.c - 1.6 linux/arch/arm/mach-pxa/pm.c - 1.2 linux/drivers/serial/sunsu.c - 1.6 linux/include/asm-sparc/thread_info.h - 1.2 linux/include/linux/pagevec.h - 1.7 linux/drivers/usb/misc/speedtouch.c - 1.5 linux/drivers/usb/class/usblp.c - 1.4 linux/drivers/input/misc/uinput.c - 1.3 linux/drivers/input/misc/Makefile - 1.4 linux/drivers/i2c/i2c-rpx.c - 1.2 linux/drivers/i2c/i2c-frodo.c - 1.2 linux/drivers/base/intf.c - 1.3 linux/arch/i386/kernel/cpu/mtrr/Makefile - 1.2 linux/drivers/base/class.c - 1.5 linux/fs/jfs/jfs_xattr.h - 1.3 linux/fs/jfs/xattr.c - 1.7 linux/net/sctp/protocol.c - 1.9 linux/net/sctp/Makefile - 1.3 linux/include/net/sctp/sctp.h - 1.6 linux/net/sctp/associola.c - 1.6 linux/net/sctp/bind_addr.c - 1.5 linux/net/sctp/endpointola.c - 1.4 linux/net/sctp/input.c - 1.6 linux/net/sctp/ipv6.c - 1.6 linux/net/sctp/output.c - 1.5 linux/net/sctp/outqueue.c - 1.7 linux/net/sctp/primitive.c - 1.3 linux/drivers/input/misc/sparcspkr.c - 1.2 linux/include/net/sctp/sm.h - 1.6 linux/net/sctp/sm_make_chunk.c - 1.7 linux/include/net/sctp/command.h - 1.2 linux/net/sctp/sm_sideeffect.c - 1.8 linux/net/sctp/sm_statefuns.c - 1.7 linux/include/net/sctp/structs.h - 1.7 linux/net/sctp/sm_statetable.c - 1.5 linux/net/sctp/socket.c - 1.8 linux/net/sctp/transport.c - 1.4 linux/arch/um/ptproxy/Makefile - 1.4 linux/drivers/ide/setup-pci.c - 1.7 linux/drivers/ide/ppc/Makefile - 1.4 linux/include/asm-ppc64/hvcall.h - 1.2 linux/drivers/ide/pci/via82cxxx.h - 1.4 linux/drivers/ide/pci/via82cxxx.c - 1.5 linux/drivers/ide/pci/trm290.h - 1.4 linux/drivers/ide/pci/trm290.c - 1.6 linux/drivers/ide/pci/slc90e66.h - 1.4 linux/drivers/ide/pci/sl82c105.h - 1.4 linux/drivers/ide/pci/sis5513.h - 1.4 linux/drivers/ide/pci/sis5513.c - 1.6 linux/drivers/ide/pci/siimage.h - 1.4 linux/drivers/ide/pci/siimage.c - 1.6 linux/drivers/ide/pci/serverworks.h - 1.4 linux/drivers/ide/pci/serverworks.c - 1.5 linux/drivers/ide/pci/rz1000.h - 1.4 linux/drivers/ide/pci/piix.h - 1.4 linux/drivers/ide/pci/piix.c - 1.5 linux/drivers/ide/pci/pdcadma.h - 1.4 linux/drivers/ide/pci/pdcadma.c - 1.5 linux/drivers/ide/pci/pdc202xx_old.h - 1.4 linux/drivers/ide/pci/pdc202xx_old.c - 1.5 linux/drivers/ide/pci/pdc202xx_new.h - 1.4 linux/drivers/ide/pci/pdc202xx_new.c - 1.5 linux/drivers/ide/pci/opti621.h - 1.4 linux/drivers/ide/pci/opti621.c - 1.5 linux/drivers/ide/pci/nvidia.h - 1.4 linux/drivers/ide/pci/nvidia.c - 1.5 linux/drivers/ide/pci/ns87415.h - 1.4 linux/drivers/ide/pci/ns87415.c - 1.5 linux/drivers/ide/pci/it8172.h - 1.4 linux/drivers/ide/pci/it8172.c - 1.5 linux/drivers/ide/pci/hpt366.h - 1.4 linux/drivers/ide/pci/hpt366.c - 1.6 linux/drivers/ide/pci/hpt34x.h - 1.4 linux/drivers/ide/pci/hpt34x.c - 1.5 linux/drivers/ide/pci/generic.h - 1.4 linux/drivers/ide/pci/generic.c - 1.5 linux/drivers/ide/pci/cy82c693.h - 1.5 linux/drivers/ide/pci/cy82c693.c - 1.7 linux/drivers/ide/pci/cs5530.h - 1.4 linux/drivers/ide/pci/cs5530.c - 1.5 linux/drivers/ide/pci/cmd64x.h - 1.4 linux/drivers/ide/pci/cmd64x.c - 1.5 linux/include/asm-um/unistd.h - 1.3 linux/include/asm-um/system-generic.h - 1.2 linux/drivers/ide/pci/cmd640.h - 1.2 linux/drivers/ide/pci/cmd640.c - 1.2 linux/drivers/ide/pci/amd74xx.h - 1.4 linux/drivers/ide/pci/amd74xx.c - 1.5 linux/drivers/ide/pci/alim15x3.h - 1.4 linux/drivers/ide/pci/alim15x3.c - 1.5 linux/drivers/ide/pci/aec62xx.h - 1.4 linux/drivers/ide/pci/aec62xx.c - 1.5 linux/drivers/ide/pci/adma100.h - 1.3 linux/drivers/ide/pci/Makefile - 1.5 linux/drivers/ide/legacy/ide-cs.c - 1.3 linux/drivers/ide/legacy/hd.c - 1.10 linux/drivers/ide/legacy/Makefile - 1.5 linux/drivers/ide/ide-lib.c - 1.6 linux/arch/um/Makefile - 1.7 linux/arch/um/Makefile-i386 - 1.3 linux/arch/um/defconfig - 1.4 linux/arch/um/drivers/Makefile - 1.4 linux/arch/um/drivers/mconsole_kern.c - 1.4 linux/arch/um/drivers/port_kern.c - 1.4 linux/arch/um/drivers/ssl.c - 1.3 linux/arch/um/drivers/stdio_console.c - 1.3 linux/arch/um/drivers/ubd_kern.c - 1.7 linux/arch/um/drivers/xterm.c - 1.3 linux/arch/um/include/chan_user.h - 1.2 linux/arch/um/include/kern_util.h - 1.3 linux/arch/um/kernel/Makefile - 1.6 linux/arch/um/kernel/irq_user.c - 1.4 linux/arch/um/kernel/ksyms.c - 1.3 linux/arch/um/kernel/process_kern.c - 1.5 linux/arch/um/kernel/ptrace.c - 1.2 linux/arch/um/kernel/reboot.c - 1.3 linux/arch/um/kernel/signal_user.c - 1.3 linux/arch/um/kernel/smp.c - 1.3 linux/arch/um/kernel/sys_call_table.c - 1.3 linux/arch/um/kernel/sysrq.c - 1.2 linux/arch/um/kernel/trap_kern.c - 1.3 linux/arch/um/os-Linux/Makefile - 1.3 linux/arch/um/os-Linux/drivers/Makefile - 1.3 linux/arch/um/os-Linux/file.c - 1.3 linux/drivers/ide/ide-iops.c - 1.3 linux/arch/um/sys-i386/Makefile - 1.4 linux/arch/um/sys-i386/util/Makefile - 1.3 linux/arch/um/sys-ia64/Makefile - 1.3 linux/arch/um/sys-ppc/Makefile - 1.3 linux/arch/um/util/Makefile - 1.4 linux/include/asm-um/irq.h - 1.3 linux/drivers/ide/arm/Makefile - 1.4 linux/drivers/char/vt_ioctl.c - 1.3 linux/arch/ppc64/vmlinux.lds.S - 1.3 linux/arch/sparc64/vmlinux.lds.S - 1.5 linux/arch/sparc/vmlinux.lds.S - 1.5 linux/arch/s390x/vmlinux.lds.S - 1.5 linux/arch/ppc/vmlinux.lds.S - 1.5 linux/arch/s390/vmlinux.lds.S - 1.5 linux/arch/i386/mm/hugetlbpage.c - 1.6 linux/drivers/acpi/sleep.c - 1.3 linux/net/bridge/netfilter/ebtables.c - 1.3 linux/net/bridge/netfilter/ebt_vlan.c - 1.2 linux/arch/i386/mach-generic/Makefile - 1.4 linux/arch/i386/mach-visws/Makefile - 1.3 linux/arch/ppc/boot/of1275/Makefile - 1.3 linux/net/bridge/netfilter/Makefile - 1.2 linux/mm/madvise.c - 1.3 linux/drivers/acpi/scan.c - 1.3 linux/arch/ppc/boot/openfirmware/Makefile - 1.4 linux/arch/ia64/pci/Makefile - 1.2 linux/drivers/char/agp/k8-agp.c - 1.2 linux/drivers/base/hotplug.c - 1.6 linux/drivers/base/cpu.c - 1.3 linux/include/linux/cpu.h - 1.3 linux/sound/sparc/cs4231.c - 1.3 linux/drivers/usb/core/driverfs.c - 1.4 linux/sound/sparc/amd7930.c - 1.4 linux/Documentation/cpufreq - 1.2 linux/sound/sparc/Makefile - 1.2 linux/fs/smbfs/symlink.c - 1.3 linux/include/asm-alpha/topology.h - 1.2 linux/kernel/cpufreq.c - 1.4 linux/arch/um/uml.lds.S - 1.3 linux/include/linux/cpufreq.h - 1.4 linux/arch/i386/kernel/cpu/cpufreq/powernow-k6.c - 1.2 linux/arch/i386/kernel/cpu/cpufreq/p4-clockmod.c - 1.3 linux/arch/i386/kernel/cpu/cpufreq/speedstep.c - 1.3 linux/arch/i386/kernel/cpu/cpufreq/elanfreq.c - 1.2 linux/arch/i386/kernel/cpu/cpufreq/Makefile - 1.2 linux/arch/i386/kernel/cpu/cpufreq/longrun.c - 1.3 linux/arch/i386/kernel/cpu/cpufreq/longhaul.c - 1.3 linux/sound/usb/usbmidi.c - 1.4 linux/sound/usb/usbaudio.c - 1.5 linux/sound/usb/Makefile - 1.3 linux/sound/pci/ice1712/Makefile - 1.2 linux/mm/truncate.c - 1.3 linux/drivers/char/scx200_gpio.c - 1.2 linux/drivers/char/scx200_wdt.c - 1.3 linux/drivers/video/font_mini_4x6.c - 1.2 linux/drivers/usb/misc/usbtest.c - 1.6 linux/drivers/scsi/nsp32.c - 1.3 linux/drivers/scsi/aacraid/linit.c - 1.5 linux/drivers/scsi/aacraid/aacraid.h - 1.3 linux/drivers/scsi/aacraid/aachba.c - 1.5 linux/drivers/i2c/scx200_acb.c - 1.2 linux/drivers/scsi/aacraid/Makefile - 1.4 linux/drivers/isdn/i4l/isdn_net_lib.c - 1.5 linux/net/bluetooth/rfcomm/Makefile - 1.4 linux/net/bluetooth/bnep/Makefile - 1.4 linux/arch/sparc/mm/highmem.c - 1.2 linux/fs/cifs/Makefile - 1.2 linux/Documentation/DocBook/journal-api.tmpl - 1.3 linux/Documentation/DocBook/lsm.tmpl - 1.2 linux/fs/cifs/README - 1.2 linux/fs/cifs/cifs_debug.c - 1.4 linux/fs/cifs/cifsfs.c - 1.3 linux/fs/nfsd/nfs4xdr.c - 1.4 linux/fs/cifs/cifspdu.h - 1.2 linux/fs/cifs/cifsproto.h - 1.3 linux/fs/cifs/cifssmb.c - 1.4 linux/fs/cifs/connect.c - 1.4 linux/fs/cifs/dir.c - 1.2 linux/fs/cifs/file.c - 1.4 linux/fs/cifs/inode.c - 1.4 linux/arch/alpha/kernel/systbls.S - 1.3 linux/fs/cifs/link.c - 1.2 linux/fs/cifs/md5.c - 1.2 linux/fs/nfsd/nfs4proc.c - 1.3 linux/fs/cifs/netmisc.c - 1.3 linux/drivers/isdn/hardware/eicon/xdi_msg.h - 1.2 linux/drivers/isdn/hardware/eicon/xdi_adapter.h - 1.2 linux/drivers/isdn/hardware/eicon/um_xdi.h - 1.2 linux/net/sunrpc/cache.c - 1.3 linux/drivers/isdn/hardware/eicon/um_idi.h - 1.2 linux/fs/cifs/CHANGES - 1.3 linux/drivers/isdn/hardware/eicon/um_idi.c - 1.2 linux/drivers/isdn/hardware/eicon/s_pri.c - 1.2 linux/drivers/isdn/hardware/eicon/s_bri.c - 1.2 linux/arch/i386/kernel/timers/Makefile - 1.2 linux/arch/i386/kernel/timers/timer_tsc.c - 1.4 linux/drivers/isdn/hardware/eicon/s_4bri.c - 1.2 linux/drivers/isdn/hardware/eicon/platform.h - 1.2 linux/drivers/isdn/hardware/eicon/os_pri.h - 1.2 linux/drivers/isdn/hardware/eicon/os_pri.c - 1.2 linux/drivers/isdn/hardware/eicon/os_bri.h - 1.2 linux/drivers/isdn/hardware/eicon/os_bri.c - 1.2 linux/drivers/isdn/hardware/eicon/adapter.h - 1.2 linux/drivers/isdn/hardware/eicon/os_4bri.h - 1.2 linux/drivers/isdn/hardware/eicon/os_4bri.c - 1.2 linux/drivers/isdn/hardware/eicon/mntfunc.c - 1.2 linux/drivers/isdn/hardware/eicon/mi_pc.h - 1.2 linux/drivers/isdn/hardware/eicon/idifunc.c - 1.2 linux/drivers/isdn/hardware/eicon/i4lididrv.c - 1.2 linux/drivers/isdn/hardware/eicon/entity.h - 1.2 linux/drivers/isdn/hardware/eicon/dsp_tst.h - 1.2 linux/drivers/isdn/hardware/eicon/capifunc.c - 1.3 linux/drivers/isdn/hardware/eicon/capifunc.h - 1.2 linux/drivers/isdn/hardware/eicon/dqueue.h - 1.2 linux/drivers/isdn/hardware/eicon/dqueue.c - 1.2 linux/drivers/isdn/hardware/eicon/dlist.h - 1.2 linux/drivers/isdn/hardware/eicon/dlist.c - 1.2 linux/include/linux/nfs4.h - 1.2 linux/include/linux/nfsd/xdr4.h - 1.4 linux/arch/ppc/platforms/4xx/Makefile - 1.2 linux/drivers/isdn/hardware/eicon/capimain.c - 1.2 linux/drivers/isdn/hardware/eicon/divasfunc.c - 1.2 linux/drivers/isdn/hardware/eicon/divasproc.c - 1.2 linux/drivers/isdn/hardware/eicon/divasmain.c - 1.3 linux/drivers/isdn/hardware/eicon/divasi.c - 1.2 linux/drivers/isdn/hardware/eicon/diva_didd.c - 1.2 linux/drivers/isdn/hardware/eicon/divamnt.c - 1.2 linux/drivers/isdn/hardware/eicon/diva_pci.h - 1.2 linux/drivers/isdn/hardware/eicon/diva.h - 1.2 linux/drivers/isdn/hardware/eicon/diddfunc.c - 1.2 linux/drivers/isdn/hardware/eicon/diva.c - 1.2 linux/fs/nfs/nfs4xdr.c - 1.3 linux/drivers/oprofile/buffer_sync.c - 1.4 linux/drivers/oprofile/cpu_buffer.c - 1.2 linux/drivers/oprofile/cpu_buffer.h - 1.2 linux/drivers/serial/8250_acorn.c - 1.2 linux/fs/afs/Makefile - 1.3 linux/net/rxrpc/connection.c - 1.3 linux/drivers/char/tipar.c - 1.4 linux/net/rxrpc/Makefile - 1.3 linux/fs/afs/inode.c - 1.3 linux/arch/i386/oprofile/Makefile - 1.3 linux/arch/i386/oprofile/nmi_int.c - 1.3 linux/drivers/block/scsi_ioctl.c - 1.4 linux/fs/intermezzo/replicator.c - 1.2 linux/fs/nfs/nfs4proc.c - 1.3 linux/fs/intermezzo/kml_unpack.c - 1.2 linux/fs/intermezzo/journal_tmpfs.c - 1.2 linux/fs/intermezzo/fileset.c - 1.2 linux/fs/afs/vlclient.c - 1.3 linux/arch/ppc/boot/simple/misc.c - 1.2 linux/drivers/pnp/pnpbios/core.c - 1.3 linux/drivers/pnp/resource.c - 1.3 linux/drivers/pnp/names.c - 1.3 linux/fs/sysfs/Makefile - 1.2 linux/drivers/pnp/base.h - 1.3 linux/drivers/pnp/core.c - 1.3 linux/drivers/pnp/driver.c - 1.3 linux/drivers/pnp/pnpbios/Makefile - 1.2 linux/fs/sysfs/inode.c - 1.3 linux/arch/i386/kernel/edd.c - 1.4 linux/drivers/pnp/isapnp/proc.c - 1.2 linux/drivers/pnp/system.c - 1.2 linux/drivers/pnp/isapnp/core.c - 1.3 linux/drivers/pnp/isapnp/Makefile - 1.3 linux/drivers/pnp/interface.c - 1.2 linux/include/linux/pnp.h - 1.3 linux/include/linux/kobject.h - 1.3 linux/drivers/media/dvb/Makefile - 1.2 linux/drivers/media/dvb/av7110/av7110.c - 1.2 linux/Documentation/crypto/api-intro.txt - 1.3 linux/drivers/net/Kconfig - 1.4 linux/Documentation/kobject.txt - 1.2 linux/drivers/net/hamradio/Kconfig - 1.2 linux/drivers/net/tokenring/Kconfig - 1.2 linux/arch/alpha/Kconfig - 1.4 linux/arch/arm/Kconfig - 1.4 linux/security/Kconfig - 1.2 linux/drivers/md/dm-linear.c - 1.2 linux/scripts/kconfig/zconf.y - 1.2 linux/scripts/kconfig/zconf.tab.c_shipped - 1.3 linux/scripts/kconfig/zconf.l - 1.3 linux/scripts/kconfig/symbol.c - 1.2 linux/scripts/kconfig/qconf.h - 1.2 linux/scripts/kconfig/qconf.cc - 1.3 linux/scripts/kconfig/mconf.c - 1.3 linux/arch/cris/Kconfig - 1.3 linux/net/ipv4/Kconfig - 1.3 linux/include/linux/eventpoll.h - 1.4 linux/arch/i386/Kconfig - 1.5 linux/net/bridge/netfilter/Kconfig - 1.2 linux/net/bridge/br_netfilter.c - 1.3 linux/include/linux/dvb/osd.h - 1.2 linux/scripts/kconfig/lkc.h - 1.2 linux/include/linux/dvb/ca.h - 1.2 linux/drivers/media/dvb/frontends/ves1820.c - 1.2 linux/drivers/media/dvb/frontends/grundig_29504-491.c - 1.2 linux/drivers/media/dvb/frontends/grundig_29504-401.c - 1.2 linux/scripts/kconfig/lex.zconf.c_shipped - 1.3 linux/drivers/media/dvb/frontends/alps_bsrv2.c - 1.2 linux/drivers/media/dvb/frontends/alps_bsru6.c - 1.2 linux/arch/i386/mach-voyager/Makefile - 1.2 linux/drivers/media/dvb/frontends/Makefile - 1.2 linux/scripts/kconfig/expr.h - 1.3 linux/drivers/media/dvb/frontends/Kconfig - 1.2 linux/drivers/media/dvb/dvb-core/dvbdev.h - 1.2 linux/scripts/kconfig/confdata.c - 1.3 linux/scripts/kconfig/conf.c - 1.3 linux/include/linux/crypto.h - 1.3 linux/arch/ia64/Kconfig - 1.3 linux/drivers/media/dvb/dvb-core/dvbdev.c - 1.2 linux/drivers/media/dvb/dvb-core/dvb_net.h - 1.2 linux/drivers/media/dvb/dvb-core/dvb_net.c - 1.2 linux/drivers/media/dvb/dvb-core/dvb_ksyms.c - 1.2 linux/drivers/media/dvb/dvb-core/dvb_i2c.h - 1.2 linux/scripts/kconfig/Makefile - 1.3 linux/scripts/Makefile.modver - 1.2 linux/scripts/Makefile.modinst - 1.2 linux/scripts/Makefile.lib - 1.2 linux/drivers/media/dvb/dvb-core/dvb_i2c.c - 1.2 linux/drivers/media/dvb/dvb-core/dvb_frontend.h - 1.2 linux/drivers/media/dvb/dvb-core/dvb_frontend.c - 1.2 linux/drivers/media/dvb/dvb-core/dvb_filter.h - 1.2 linux/drivers/media/dvb/dvb-core/dvb_filter.c - 1.2 linux/scripts/Makefile.build - 1.3 linux/drivers/char/Kconfig - 1.2 linux/arch/m68k/Kconfig - 1.4 linux/drivers/media/dvb/dvb-core/dvb_demux.h - 1.2 linux/arch/mips/Kconfig - 1.4 linux/drivers/media/dvb/dvb-core/dvb_demux.c - 1.2 linux/arch/mips64/Kconfig - 1.4 linux/arch/parisc/Kconfig - 1.4 linux/drivers/media/dvb/dvb-core/dmxdev.h - 1.2 linux/drivers/media/dvb/dvb-core/dmxdev.c - 1.2 linux/drivers/media/dvb/dvb-core/Makefile - 1.2 linux/drivers/media/dvb/av7110/saa7146_v4l.c - 1.2 linux/drivers/media/dvb/av7110/saa7146_core.h - 1.2 linux/drivers/media/dvb/av7110/saa7146_core.c - 1.2 linux/drivers/media/dvb/av7110/saa7146.c - 1.2 linux/drivers/media/dvb/av7110/av7110_ir.c - 1.2 linux/drivers/media/dvb/av7110/av7110.h - 1.2 linux/drivers/media/dvb/av7110/Makefile - 1.2 linux/drivers/pnp/Kconfig - 1.2 linux/drivers/s390/Kconfig - 1.2 linux/arch/parisc/kernel/sys_parisc32.c - 1.3 linux/drivers/md/dm.h - 1.2 linux/drivers/md/dm.c - 1.2 linux/drivers/md/dm-table.c - 1.2 linux/drivers/md/dm-stripe.c - 1.2 linux/drivers/md/dm-ioctl.c - 1.2 linux/drivers/scsi/Kconfig - 1.3 linux/drivers/isdn/i4l/Kconfig - 1.2 linux/drivers/char/agp/Kconfig - 1.2 linux/arch/ppc/Kconfig - 1.4 linux/arch/ppc64/Kconfig - 1.4 linux/arch/s390/Kconfig - 1.4 linux/net/ipv4/ah.c - 1.3 linux/arch/s390x/Kconfig - 1.4 linux/arch/sh/Kconfig - 1.4 linux/arch/sparc/Kconfig - 1.4 linux/drivers/scsi/pcmcia/Kconfig - 1.2 linux/arch/sparc64/Kconfig - 1.3 linux/drivers/ide/Kconfig - 1.2 linux/drivers/usb/host/Kconfig - 1.2 linux/fs/befs/linuxvfs.c - 1.2 linux/arch/x86_64/Kconfig - 1.4 linux/fs/befs/datastream.c - 1.2 linux/fs/befs/Makefile - 1.2 linux/fs/Kconfig - 1.7 linux/drivers/input/Kconfig - 1.2 linux/drivers/input/keyboard/Kconfig - 1.2 linux/lib/kobject.c - 1.3 linux/drivers/ieee1394/Kconfig - 1.2 linux/crypto/Kconfig - 1.3 linux/crypto/Makefile - 1.3 linux/crypto/api.c - 1.3 linux/crypto/cipher.c - 1.3 linux/crypto/compress.c - 1.2 linux/crypto/digest.c - 1.3 linux/crypto/internal.h - 1.3 linux/crypto/tcrypt.c - 1.3 linux/crypto/tcrypt.h - 1.3 linux/net/Kconfig - 1.3 linux/net/ipv4/xfrm_policy.c - 1.3 linux/drivers/input/misc/Kconfig - 1.2 linux/drivers/input/mouse/Kconfig - 1.3 linux/drivers/serial/Kconfig - 1.3 linux/drivers/isdn/hisax/Kconfig - 1.2 linux/drivers/acpi/Kconfig - 1.2 linux/drivers/video/Kconfig - 1.3 linux/net/ipv4/xfrm_input.c - 1.3 linux/net/ipv4/xfrm_state.c - 1.3 linux/drivers/usb/serial/Kconfig - 1.2 linux/drivers/isdn/hardware/avm/Kconfig - 1.2 linux/sound/oss/Kconfig - 1.2 linux/drivers/usb/net/Kconfig - 1.2 linux/drivers/usb/class/Kconfig - 1.3 linux/drivers/usb/core/Kconfig - 1.2 linux/include/net/xfrm.h - 1.3 linux/drivers/input/serio/Kconfig - 1.3 linux/drivers/isdn/Kconfig - 1.2 linux/init/Kconfig - 1.2 linux/drivers/usb/media/Kconfig - 1.2 linux/fs/mbcache.c - 1.3 linux/include/asm-v850/nb85e_uart.h - 1.2 linux/fs/hugetlbfs/inode.c - 1.3 linux/fs/hugetlbfs/Makefile - 1.2 linux/fs/ext3/xattr.h - 1.2 linux/fs/ext3/xattr.c - 1.2 linux/arch/alpha/kernel/err_common.c - 1.2 linux/arch/alpha/kernel/err_impl.h - 1.2 linux/fs/ext2/xattr.h - 1.2 linux/fs/ext2/xattr.c - 1.2 linux/fs/eventpoll.c - 1.3 linux/include/asm-m68knommu/current.h - 1.2 linux/fs/binfmt_som.c - 1.2 linux/include/asm-m68knommu/elf.h - 1.2 linux/include/asm-m68knommu/hardirq.h - 1.2 linux/init/initramfs.c - 1.2 linux/drivers/serial/8250_gsc.c - 1.2 linux/include/linux/videodev2.h - 1.2 linux/drivers/parisc/power.c - 1.2 linux/drivers/parisc/led.c - 1.3 linux/include/linux/mbcache.h - 1.2 linux/drivers/parisc/eisa.c - 1.3 linux/drivers/parisc/dino.c - 1.3 linux/drivers/parisc/ccio-dma.c - 1.3 linux/include/linux/hugetlb.h - 1.3 linux/drivers/net/mac8390.c - 1.2 linux/include/asm-v850/unistd.h - 1.2 linux/drivers/net/fec.c - 1.2 linux/drivers/net/68360enet.c - 1.2 linux/arch/i386/mach-generic/topology.c - 1.2 linux/include/asm-v850/stat.h - 1.2 linux/include/asm-v850/sim85e2c.h - 1.2 linux/drivers/media/video/saa7134/saa7134.h - 1.2 linux/include/asm-v850/sim.h - 1.2 linux/drivers/media/video/saa7134/saa7134-video.c - 1.2 linux/drivers/media/video/saa7134/saa7134-vbi.c - 1.2 linux/drivers/media/video/saa7134/saa7134-tvaudio.c - 1.2 linux/drivers/media/video/saa7134/saa7134-ts.c - 1.2 linux/drivers/media/video/saa7134/saa7134-oss.c - 1.2 linux/drivers/media/video/saa7134/saa7134-i2c.c - 1.2 linux/drivers/media/video/saa7134/saa7134-core.c - 1.2 linux/drivers/media/video/saa7134/saa7134-cards.c - 1.2 linux/drivers/media/video/saa7134/Makefile - 1.2 linux/include/asm-m68knommu/processor.h - 1.2 linux/drivers/base/node.c - 1.2 linux/drivers/base/memblk.c - 1.2 linux/include/asm-m68knommu/thread_info.h - 1.2 linux/arch/v850/vmlinux.lds.S - 1.2 linux/arch/v850/sim85e2c.ld - 1.2 linux/arch/v850/sim.ld - 1.2 linux/arch/v850/rte_ma1_cb.ld - 1.2 linux/arch/v850/rte_ma1_cb-rom.ld - 1.2 linux/arch/v850/rte_ma1_cb-ksram.ld - 1.2 linux/arch/v850/lib/Makefile - 1.2 linux/arch/v850/kernel/v850_ksyms.c - 1.2 linux/arch/m68knommu/Kconfig - 1.3 linux/arch/m68knommu/Makefile - 1.2 linux/arch/m68knommu/kernel/Makefile - 1.2 linux/arch/m68knommu/kernel/asm-offsets.c - 1.2 linux/arch/m68knommu/kernel/ints.c - 1.2 linux/arch/m68knommu/kernel/m68k_ksyms.c - 1.2 linux/arch/m68knommu/kernel/process.c - 1.2 linux/arch/m68knommu/kernel/signal.c - 1.2 linux/arch/m68knommu/kernel/syscalltable.S - 1.2 linux/arch/m68knommu/lib/Makefile - 1.2 linux/arch/m68knommu/mm/Makefile - 1.2 linux/arch/m68knommu/platform/5206/Makefile - 1.2 linux/arch/m68knommu/platform/5206e/Makefile - 1.2 linux/arch/m68knommu/platform/5249/Makefile - 1.2 linux/arch/m68knommu/platform/5272/Makefile - 1.2 linux/arch/m68knommu/platform/5307/Makefile - 1.2 linux/arch/m68knommu/platform/5407/Makefile - 1.2 linux/arch/m68knommu/platform/68328/Makefile - 1.2 linux/arch/m68knommu/platform/68360/Makefile - 1.2 linux/arch/m68knommu/platform/68EZ328/Makefile - 1.2 linux/arch/m68knommu/platform/68VZ328/Makefile - 1.2 linux/arch/m68knommu/platform/Makefile - 1.2 linux/arch/v850/kernel/simcons.c - 1.2 linux/arch/v850/kernel/sim85e2c.c - 1.2 linux/arch/v850/kernel/sim.c - 1.2 linux/arch/v850/kernel/signal.c - 1.2 linux/arch/v850/kernel/setup.c - 1.2 linux/arch/v850/kernel/rte_mb_a_pci.c - 1.2 linux/arch/v850/kernel/rte_cb_leds.c - 1.2 linux/arch/v850/kernel/rte_cb.c - 1.2 linux/arch/v850/kernel/procfs.c - 1.2 linux/include/asm-v850/processor.h - 1.2 linux/include/asm-v850/percpu.h - 1.2 linux/include/asm-v850/module.h - 1.2 linux/arch/v850/kernel/process.c - 1.2 linux/arch/v850/kernel/nb85e_utils.c - 1.2 linux/include/asm-v850/machdep.h - 1.2 linux/include/asm-v850/irq.h - 1.2 linux/arch/v850/kernel/nb85e_intc.c - 1.2 linux/arch/v850/kernel/memcons.c - 1.2 linux/include/asm-v850/hardirq.h - 1.2 linux/include/asm-v850/gbus_int.h - 1.2 linux/include/asm-v850/fpga85e2c.h - 1.2 linux/arch/v850/kernel/irq.c - 1.2 linux/arch/v850/kernel/intv.S - 1.2 linux/include/asm-v850/elf.h - 1.2 linux/include/asm-v850/asm.h - 1.2 linux/include/asm-v850/clinkage.h - 1.2 linux/arch/v850/kernel/gbus_int.c - 1.2 linux/arch/v850/kernel/head.S - 1.2 linux/arch/v850/kernel/fpga85e2c.c - 1.2 linux/include/asm-v850/anna.h - 1.2 linux/arch/v850/kernel/entry.S - 1.2 linux/arch/v850/kernel/bug.c - 1.2 linux/arch/v850/kernel/anna.c - 1.2 linux/arch/v850/kernel/Makefile - 1.2 linux/arch/v850/Kconfig - 1.3 linux/arch/v850/anna.ld - 1.2 linux/arch/v850/Makefile - 1.2 linux/arch/v850/anna-rom.ld - 1.2 linux/drivers/net/b44.c - 1.2 linux/drivers/net/irda/sir_kthread.c - 1.2 linux/drivers/hotplug/cpci_hotplug_pci.c - 1.2 linux/drivers/hotplug/cpci_hotplug_core.c - 1.2 linux/drivers/serial/68328serial.c - 1.2 linux/drivers/serial/68360serial.c - 1.2 linux/drivers/serial/mcfserial.c - 1.2 linux/drivers/serial/nb85e_uart.c - 1.2 linux/crypto/hmac.c - 1.2 linux/arch/i386/kernel/cpu/mcheck/Makefile - 1.2 linux/arch/i386/kernel/cpu/mcheck/mce.c - 1.3 linux/arch/i386/kernel/cpu/mcheck/non-fatal.c - 1.2 linux/net/key/af_key.c - 1.2 linux/net/key/Makefile - 1.2 linux/arch/ppc/syslib/open_pic.c - 1.2 linux/arch/ppc/syslib/i8259.c - 1.2 linux/arch/ppc/syslib/Makefile - 1.2 linux/arch/ppc/kernel/ppc6xx_idle.c - 1.2 linux/net/ipv4/esp.c - 1.2 From owner-linux-xfs@oss.sgi.com Tue Dec 17 11:43:15 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 11:43:18 -0800 (PST) Received: from hotmail.com (bay1-dav52.bay1.hotmail.com [65.54.244.41]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBHJhE3v031984 for ; Tue, 17 Dec 2002 11:43:15 -0800 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 17 Dec 2002 11:47:16 -0800 X-Originating-IP: [141.217.84.15] From: "WM" To: Subject: RH-7.3 xdelta patch error Date: Tue, 17 Dec 2002 14:53:09 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: X-OriginalArrivalTime: 17 Dec 2002 19:47:16.0350 (UTC) FILETIME=[1A2561E0:01C2A605] Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 670 X-archive-position: 2106 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: maverick_wayne@hotmail.com Precedence: bulk X-list: linux-xfs Hi, I was trying to update the RedHat 7.3 installer by following the readme (ftp://oss.sgi.com/projects/xfs/download/Release-1.1/installer/installer/i386/README-RH-VERSIONS). I downloaded both of the files: new-rh-7.3-patch.xdelta RH7.3-SGI-XFS-1.1.iso I followed the instruction on the readme, but I didn't have success. Following are the output of my attempts: # xdelta patch new-rh-7.3-patch.xdelta RH7.3-SGI-XFS-1.1.iso [root@host] xdelta: wrong number of arguments # xdelta patch new-rh-7.3-patch.xdelta RH7.3-SGI-XFS-1.1.iso RH7.3.2-SGI-XFS-1.1.iso [root@host] xdelta: invalid patch What am I doing wrong? Thanks [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Tue Dec 17 18:05:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 18:05:41 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBI25Y3v011497 for ; Tue, 17 Dec 2002 18:05:35 -0800 Received: from sherman.melbourne.sgi.com (sherman.melbourne.sgi.com [134.14.55.232]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBI09dG8003164 for ; Tue, 17 Dec 2002 16:09:41 -0800 Received: (from kaos@localhost) by sherman.melbourne.sgi.com (8.11.6/8.11.6) id gBI28Td27741; Wed, 18 Dec 2002 13:08:29 +1100 Date: Wed, 18 Dec 2002 13:08:29 +1100 From: Keith Owens Message-Id: <200212180208.gBI28Td27741@sherman.melbourne.sgi.com> Subject: TAKE - Minor cleanups for split patches X-archive-position: 2107 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kaos@sherman.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Delete a spurious whitespace change from fs/Config.in. Move the ACL Configure.help entry away from DMAPI's entry, so the acl split patch is applied first and requires a clean context. Date: Tue Dec 17 18:06:13 PST 2002 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:135446a linux/fs/Config.in - 1.89 linux/Documentation/Configure.help - 1.142 From owner-linux-xfs@oss.sgi.com Tue Dec 17 18:13:26 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 18:13:32 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBI2DP3v011984 for ; Tue, 17 Dec 2002 18:13:26 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gBI1MKKp028406 for ; Tue, 17 Dec 2002 17:22:21 -0800 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 NAA19941; Wed, 18 Dec 2002 13:16:11 +1100 Received: by kao2.melbourne.sgi.com (Postfix, from userid 16331) id A7B4D300087; Wed, 18 Dec 2002 13:16:06 +1100 (EST) Received: from kao2.melbourne.sgi.com (localhost [127.0.0.1]) by kao2.melbourne.sgi.com (Postfix) with ESMTP id 3D57D85; Wed, 18 Dec 2002 13:16:06 +1100 (EST) X-Mailer: exmh version 2.4 06/23/2000 with nmh-1.0.4 From: Keith Owens To: linux-xfs@oss.sgi.com Cc: linux-kernel@vger.kernel.org Subject: Announce: XFS split patches for 2.4.20 - respin Date: Wed, 18 Dec 2002 13:16:00 +1100 Message-ID: <6153.1040177760@kao2.melbourne.sgi.com> X-archive-position: 2108 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: kaos@sgi.com Precedence: bulk X-list: linux-xfs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii ftp://oss.sgi.com/projects/xfs/download/patches/2.4.20. The xfs patches for 2.4.20 have been respun as of 2002-12-18 02:00 UTC. For some time the XFS group have been producing split patches for XFS, separating the core XFS changes from additional patches such as kdb, xattr, acl, dmapi. The split patches are released to the world with the hope that developers and distributors will find them useful. Read the README in each directory very carefully, the split patch format has changed over a few kernel releases. Any questions that are covered by the README will be ignored. There is even a 2.4.21/README for the terminally impatient :). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Exmh version 2.1.1 10/15/1999 iD8DBQE9/9pdi4UHNye0ZOoRAjd7AKCUGoWqZ3SJGRj2d7ssCEsiZb03vwCdFm4J 5ymEscu9jY2EEZuwz2NwPK0= =0KMC -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Tue Dec 17 19:59:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 19:59:47 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBI3xg3v015452 for ; Tue, 17 Dec 2002 19:59:43 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBI38cKp032241 for ; Tue, 17 Dec 2002 19:08:39 -0800 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id gBI42Q2s306543 for ; Wed, 18 Dec 2002 15:02:26 +1100 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id gBI42Qpg306462 for linux-xfs@oss.sgi.com; Wed, 18 Dec 2002 15:02:26 +1100 (EST) Date: Wed, 18 Dec 2002 15:02:26 +1100 (EST) From: Nathan Scott Message-Id: <200212180402.gBI42Qpg306462@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - sector fixup X-archive-position: 2109 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Fix up setting up of sector size for the superblock buffer after the very first read on mount. Make some of the surrounding code dealing with buffers consistent. Date: Tue Dec 17 19:51:45 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/pagebuf The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135452a linux/fs/xfs/xfs_buf.h - 1.102 linux/fs/xfs/xfs_vfsops.c - 1.404 linux/fs/xfs/xfs_mount.c - 1.315 linux/fs/xfs/linux/xfs_super.h - 1.36 linux/fs/xfs/linux/xfs_super.c - 1.237 From owner-linux-xfs@oss.sgi.com Tue Dec 17 20:28:22 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 20:28:25 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBI4SL3v016063 for ; Tue, 17 Dec 2002 20:28:21 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBI4cDkq015224 for ; Tue, 17 Dec 2002 22:38:14 -0600 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id gBI4V52s310309 for ; Wed, 18 Dec 2002 15:31:05 +1100 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id gBI4V5eg307791 for linux-xfs@oss.sgi.com; Wed, 18 Dec 2002 15:31:05 +1100 (EST) Date: Wed, 18 Dec 2002 15:31:05 +1100 (EST) From: Nathan Scott Message-Id: <200212180431.gBI4V5eg307791@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - fix setxattr warnings X-archive-position: 2110 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Date: Tue Dec 17 20:29:38 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.5.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:135453a linux/fs/xfs/linux/xfs_iops.c - 1.190 - Fix some setxattr compiler warnings (const). From owner-linux-xfs@oss.sgi.com Tue Dec 17 20:58:55 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 17 Dec 2002 20:59:00 -0800 (PST) Received: from tolkor.sgi.com ([198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBI4ws3v016670 for ; Tue, 17 Dec 2002 20:58:54 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBI58lkq015494 for ; Tue, 17 Dec 2002 23:08:47 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id XAA33506 for ; Tue, 17 Dec 2002 23:02:56 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id XAA30199 for ; Tue, 17 Dec 2002 23:02:57 -0600 (CST) From: Eric Sandeen Received: by stout.americas.sgi.com (8.11.6/SGI-client-1.7) id gBI4w2l08162; Tue, 17 Dec 2002 22:58:02 -0600 Message-Id: <200212180458.gBI4w2l08162@stout.americas.sgi.com> Date: Tue, 17 Dec 2002 22:58:02 -0600 Subject: TAKE - Change some %x formats to %p for pointers X-archive-position: 2111 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Change some %x formats to %p for pointers Date: Tue Dec 17 21:02:23 PST 2002 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135454a linux/fs/xfs/xfs_rw.c - 1.370 linux/fs/xfs/xfs_inode.c - 1.361 linux/fs/xfs/xfs_trans_buf.c - 1.109 From owner-linux-xfs@oss.sgi.com Wed Dec 18 04:12:10 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 04:12:15 -0800 (PST) Received: from banna (pl940.nas927.o-tokyo.nttpc.ne.jp [61.197.109.172]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBICBw3v024845 for ; Wed, 18 Dec 2002 04:12:05 -0800 Received: from C ([192.168.0.3]) by banna (8.9.3+3.2W/3.7W) with SMTP id VAA09667; Wed, 18 Dec 2002 21:18:39 +0900 Message-Id: <200212181218.VAA09667@banna> From: =?iso-2022-jp?B?am1haWw=?= To: =?iso-2022-jp?B?NDAwNA==?=@banna.sgi.com Reply-To: jmail7777jp@yahoo.co.jp Date: Wed, 18 Dec 2002 21:16:05 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2112 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jmail7777jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_sst@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　03-3544-6222 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.ss-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.pp-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Wed Dec 18 06:23:33 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 06:23:38 -0800 (PST) Received: from federazione.fmbcc.fm ([195.223.139.226]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBIENM3v026693 for ; Wed, 18 Dec 2002 06:23:30 -0800 Received: from Qmail-Mail-Server ([10.113.160.207]) by federazione.fmbcc.fm (Lotus SMTP MTA v4.6.5 (863.2 5-20-1999)) with SMTP id 41256C93.004F7B8A; Wed, 18 Dec 2002 15:28:09 +0100 Received: (qmail 14836 invoked from network); 18 Dec 2002 14:20:35 -0000 Received: from unknown (HELO FI0P38) (10.113.160.38) by 0 with SMTP; 18 Dec 2002 14:20:35 -0000 Message-ID: <001901c2a6a1$39f3f530$26a0710a@FI0P38> From: "Fabio Baiocco" To: Subject: When Xfs 1.2 Stable? Date: Wed, 18 Dec 2002 15:24:50 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 76 X-archive-position: 2113 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: baiocco.f@filottrano.bcc.it Precedence: bulk X-list: linux-xfs When XFS 1.2 will be a stable version? [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Wed Dec 18 12:29:37 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 12:29:41 -0800 (PST) Received: from ADSL-Bergs.RZ.RWTH-Aachen.DE (adsl-bergs.rz.RWTH-Aachen.DE [137.226.80.218]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBIKTZ3v010843 for ; Wed, 18 Dec 2002 12:29:36 -0800 Received: from ralf.wg ([192.168.2.2]:3466) by ADSL-Bergs.RZ.RWTH-Aachen.DE with esmtp (Exim 4.10) id 18Okt2-0003qn-00; Wed, 18 Dec 2002 21:33:48 +0100 From: "Ralf G. R. Bergs" To: "Linux XFS Mailing List" Date: Wed, 18 Dec 2002 21:33:40 +0100 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2660) For Windows 2000 (5.0.2195;3) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: EVMS v1.2.0 + XFS 1.2: RAID5: always unclean after proper shutdown (Debian 3.0) Message-Id: X-archive-position: 2114 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: rabe@RWTH-Aachen.DE Precedence: bulk X-list: linux-xfs Hi there, I'm a lil' bit puzzled about this strange scenario: I've installed XFS 1.2 and EVMS 1.2.0 on a Debian/GNU Linux 3.0 (i386) box running 2.4.19. I've created a RAID5 storage region from four 9 gig SCSI drives, upon which I created a container, and inside this region I've created individual regions which finally make up the logical volumes. I put XFS on these logical volumes. After a clean shutdown I will always see messages like the following in syslog: kernel: evms: md core: [md0, level=5] raid array is not clean -- starting background reconstruction This usually took only moments, but after I had added two more SCSI drives (with IDs below the IDs of the existing drives, in case that matters) the whole thing became MUCH more time-consuming: kernel: evms: md core: [md0, level=5] raid array is not clean -- starting background reconstruction kernel: evms: md raid5: raid5_run: device sdf operational as raid disk 3 kernel: evms: md raid5: raid5_run: device sde operational as raid disk 2 kernel: evms: md raid5: raid5_run: device sdd operational as raid disk 1 kernel: evms: md raid5: raid5_run: device sdc operational as raid disk 0 kernel: evms: md raid5: raid5_run: raid set md0 not clean; reconstructing parity kernel: evms: md raid5: RAID5 conf printout: kernel: evms: md raid5: --- rd:4 wd:4 fd:0 kernel: evms: md raid5: disk 0, s:0, o:1, n:0 rd:0 us:1 dev:sdc kernel: evms: md raid5: disk 1, s:0, o:1, n:1 rd:1 us:1 dev:sdd kernel: evms: md raid5: disk 2, s:0, o:1, n:2 rd:2 us:1 dev:sde kernel: evms: md raid5: disk 3, s:0, o:1, n:3 rd:3 us:1 dev:sdf #cat /proc/evms/mdstat Enterprise Volume Management System: MD Status Personalities : [evms_linear] [evms_raid0] [evms_raid1] [evms_raid5] md0 : active evms_raid5 sdf[3] sde[2] sdd[1] sdc[0] 26674560 blocks 35765568 blocks level 5, 32k chunk, algorithm 2 [4/4] [UUUU] [=====>...............] resync = 27.6% (2461276/8891520) recovery = 27.6% (2461276/8891520) finish=103.1min speed=1036K/sec Any idea what could be going wrong?! Thanks, Ralf -- L I N U X .~. The Choice /V\ of a GNU /( )\ Generation ^^-^^ From owner-linux-xfs@oss.sgi.com Wed Dec 18 13:31:29 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 13:31:33 -0800 (PST) Received: from jello277.jellocom.de (root@jello277.jellocom.de [217.17.194.152]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBILVR3v011729 for ; Wed, 18 Dec 2002 13:31:28 -0800 Received: from cobonote.intranet.cobonet.de (ptp97-el-r03-J.eastlink.de [213.187.89.97]) (authenticated bits=0) by jello277.jellocom.de (8.12.6/8.12.1) with ESMTP id gBILZZjB007650 for ; Wed, 18 Dec 2002 22:35:36 +0100 Content-Type: text/plain; charset="us-ascii" From: Thomas Bittermann To: linux-xfs@oss.sgi.com Subject: xfs version in 2.4.18-17SGI_XFS_1.2pre4 Date: Wed, 18 Dec 2002 22:34:26 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 Message-Id: <200212182234.48190.t.bittermann@jetzweb.de> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBILVT3v011730 X-archive-position: 2115 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: t.bittermann@jetzweb.de Precedence: bulk X-list: linux-xfs -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hello, i found this: [...] # # Patches 990200 to 990299 are for SGI XFS # Patch990200: linux-2.4.19-xfs-config_stuff-pre2.patch Patch990201: linux-2.4.19-xfs-sysctl.patch Patch990202: linux-2.4.19-xfs-exports.patch #Patch990203: linux-2.4.19-xfs-1.2pre3.patch Patch990203: linux-2.4.19-xfs-20020922.patch Patch990204: linux-2.4.19-aggressive_readahead.patch [...] in kernel-2.4.18-17SGI_XFS_1.2pre4.spec file. is the right patch included? linux-2.4.19-xfs-20020922 sounds quite old and not like 1.2pre4 ... thanks [for this great and reliable fs] thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+AOnn3E3TGgPB70IRAoJaAKCnGHPNtw38QDLo+b+zZO2mWx6aRgCbBmIA G913Kz4qa1UVELFAK5hrDoQ= =0uyj -----END PGP SIGNATURE----- From owner-linux-xfs@oss.sgi.com Wed Dec 18 15:36:14 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 15:36:17 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBINaD3v014571 for ; Wed, 18 Dec 2002 15:36:14 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBILeQG8004831 for ; Wed, 18 Dec 2002 13:40:26 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id RAA39745; Wed, 18 Dec 2002 17:40:18 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id RAA03463; Wed, 18 Dec 2002 17:40:19 -0600 (CST) Received: from rose.americas.sgi.com (localhost [127.0.0.1]) by rose.americas.sgi.com (8.12.6/8.12.5) with ESMTP id gBINeYkx006189; Wed, 18 Dec 2002 17:40:34 -0600 Received: (from cattelan@localhost) by rose.americas.sgi.com (8.12.6/8.12.6/Submit) id gBINeXgF006187; Wed, 18 Dec 2002 17:40:33 -0600 X-Authentication-Warning: rose.americas.sgi.com: cattelan set sender to cattelan@thebarn.com using -f Subject: Re: xfs version in 2.4.18-17SGI_XFS_1.2pre4 From: Russell Cattelan To: Thomas Bittermann Cc: linux-xfs@oss.sgi.com In-Reply-To: <200212182234.48190.t.bittermann@jetzweb.de> References: <200212182234.48190.t.bittermann@jetzweb.de> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1040254833.4524.30.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) Date: 18 Dec 2002 17:40:33 -0600 X-archive-position: 2116 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs Doh... Ya that looks like cut-n-past error on my part. Ok folks ignore the RH kenels for the moment, I'll start the build over and have the ready sometime tomorrow. On Wed, 2002-12-18 at 15:34, Thomas Bittermann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hello, > > i found this: > > [...] > # > # Patches 990200 to 990299 are for SGI XFS > # > > Patch990200: linux-2.4.19-xfs-config_stuff-pre2.patch > Patch990201: linux-2.4.19-xfs-sysctl.patch > Patch990202: linux-2.4.19-xfs-exports.patch > #Patch990203: linux-2.4.19-xfs-1.2pre3.patch > Patch990203: linux-2.4.19-xfs-20020922.patch > Patch990204: linux-2.4.19-aggressive_readahead.patch > [...] > > in kernel-2.4.18-17SGI_XFS_1.2pre4.spec file. > > is the right patch included? linux-2.4.19-xfs-20020922 sounds quite > old and not like 1.2pre4 ... > > thanks [for this great and reliable fs] > > thomas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.1 (GNU/Linux) > > iD8DBQE+AOnn3E3TGgPB70IRAoJaAKCnGHPNtw38QDLo+b+zZO2mWx6aRgCbBmIA > G913Kz4qa1UVELFAK5hrDoQ= > =0uyj > -----END PGP SIGNATURE----- -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Wed Dec 18 16:51:28 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 16:51:34 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJ0pR3v016471 for ; Wed, 18 Dec 2002 16:51:28 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBIMtdG8008655 for ; Wed, 18 Dec 2002 14:55:40 -0800 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id gBJ0sF3s071329 for ; Thu, 19 Dec 2002 11:54:16 +1100 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id gBJ0sEjw071110 for linux-xfs@oss.sgi.com; Thu, 19 Dec 2002 11:54:14 +1100 (EST) Date: Thu, 19 Dec 2002 11:54:14 +1100 (EST) From: Nathan Scott Message-Id: <200212190054.gBJ0sEjw071110@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsprogs X-archive-position: 2117 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Flush out my xfsprogs backlog a bit - bunch of I18N and sector size related changes mainly, also some build minor build cleanups here and there. Trivial sync ups with kernel header/source changes too. Since this has a bunch of the same I18N configure-related changes that recently went into acl/attr, "make distclean" is your friend. cheers. Date: Tue Dec 17 15:59:44 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135423a cmd/xfsprogs/include/xfs_dir2_block.h - 1.7 cmd/xfsprogs/include/xfs_dir2_sf.h - 1.8 cmd/xfsprogs/include/xfs_dir_leaf.h - 1.9 cmd/xfsprogs/include/xfs_dir2_leaf.h - 1.7 cmd/xfsprogs/include/xfs_dir2_node.h - 1.7 cmd/xfsprogs/include/xfs_dir2.h - 1.8 cmd/xfsprogs/include/xfs_acl.h - 1.7 Date: Tue Dec 17 17:14:02 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135430a cmd/xfsprogs/libxlog/xfs_log_recover.c - 1.18 Date: Tue Dec 17 22:31:29 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135455a cmd/xfsprogs/libxfs/xfs_dir.c - 1.12 cmd/xfsprogs/libxfs/xfs_dir2.c - 1.12 Date: Wed Dec 18 16:38:27 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135515a cmd/xfsprogs/VERSION - 1.63 cmd/xfsprogs/doc/CHANGES - 1.88 cmd/xfsprogs/debian/changelog - 1.56 - Bump version for I18N and sector related changes. cmd/xfsprogs/db/xfs_admin.sh - 1.7 cmd/xfsprogs/db/xfs_check.sh - 1.6 cmd/xfsprogs/db/xfs_check64.sh - 1.6 cmd/xfsprogs/db/xfs_ncheck.sh - 1.6 cmd/xfsprogs/db/xfs_ncheck64.sh - 1.6 cmd/xfsprogs/growfs/xfs_info.sh - 1.6 - Report version if asked. cmd/xfsprogs/db/sb.c - 1.7 cmd/xfsprogs/mkfs/trtab.c - 1.1 cmd/xfsprogs/db/faddr.c - 1.5 cmd/xfsprogs/db/uuid.c - 1.7 cmd/xfsprogs/db/agf.c - 1.5 cmd/xfsprogs/db/frag.c - 1.8 cmd/xfsprogs/db/freesp.c - 1.8 cmd/xfsprogs/db/agi.c - 1.5 cmd/xfsprogs/db/agfl.c - 1.5 cmd/xfsprogs/db/check.c - 1.11 cmd/xfsprogs/mkfs/maxtrres.c - 1.6 cmd/xfsprogs/mkfs/Makefile - 1.13 cmd/xfsprogs/man/man8/mkfs.xfs.8 - 1.14 - Changes to support sector sizes large than 512 bytes. cmd/xfsprogs/mkfs/xfs_mkfs.c - 1.38 - Changes to support sector sizes large than 512 bytes. Changes for I18N support. cmd/xfsprogs/configure.in - 1.18 cmd/xfsprogs/Makefile - 1.15 cmd/xfsprogs/po/Makefile - 1.1 cmd/xfsprogs/bmap/xfs_bmap.c - 1.12 cmd/xfsprogs/imap/xfs_imap.c - 1.7 cmd/xfsprogs/mkfs/proto.c - 1.10 cmd/xfsprogs/rtcp/xfs_rtcp.c - 1.10 cmd/xfsprogs/libdisk/md.c - 1.9 cmd/xfsprogs/libdisk/drivers.c - 1.11 cmd/xfsprogs/libdisk/lvm.c - 1.9 cmd/xfsprogs/freeze/xfs_freeze.c - 1.7 cmd/xfsprogs/growfs/xfs_growfs.c - 1.16 cmd/xfsprogs/include/buildrules - 1.10 cmd/xfsprogs/include/builddefs.in - 1.26 cmd/xfsprogs/libxlog/util.c - 1.6 - Changes for I18N support. cmd/xfsprogs/growfs/Makefile - 1.10 cmd/xfsprogs/libxfs/Makefile - 1.13 cmd/xfsprogs/libdisk/Makefile - 1.8 - Build cleanups. cmd/xfsprogs/include/swab.h - 1.1 cmd/xfsprogs/mkfs/xfs_mkfs.h - 1.7 - Build cleanups. Reduce our dependency on kernel headers a bit. cmd/xfsprogs/include/libxfs.h - 1.20 - Cleanup handling of libxfs flags parameters. Changes to support sector sizes large than 512 bytes. cmd/xfsprogs/include/Makefile - 1.15 cmd/xfsprogs/include/platform_defs.h.in - 1.15 - Build cleanups, reduce our dependency on kernel headers. Changes for I18N support. cmd/xfsprogs/include/xfs_ag.h - 1.11 cmd/xfsprogs/include/xfs_sb.h - 1.8 cmd/xfsprogs/include/xfs_fs.h - 1.23 cmd/xfsprogs/include/xfs_bmap_btree.h - 1.7 cmd/xfsprogs/include/xfs_mount.h - 1.31 cmd/xfsprogs/include/xfs_types.h - 1.16 cmd/xfsprogs/include/xfs_trans.h - 1.10 cmd/xfsprogs/include/xfs_alloc.h - 1.8 cmd/xfsprogs/include/xfs_alloc_btree.h - 1.7 cmd/xfsprogs/libxfs/xfs_ialloc.c - 1.16 cmd/xfsprogs/libxfs/xfs_mount.c - 1.13 cmd/xfsprogs/libxfs/xfs_alloc.c - 1.16 - Sync up with current versions of kernel sources. cmd/xfsprogs/debian/rules - 1.14 - When building mkfs for Debian boot floppies, disable gettext support to make the binary a little smaller. cmd/xfsprogs/repair/phase5.c - 1.5 cmd/xfsprogs/repair/agheader.c - 1.9 cmd/xfsprogs/repair/phase3.c - 1.7 cmd/xfsprogs/repair/scan.c - 1.6 - Changes to support sector sizes large than 512 bytes. cmd/xfsprogs/libxfs/rdwr.c - 1.14 cmd/xfsprogs/libxfs/trans.c - 1.10 cmd/xfsprogs/libxfs/init.c - 1.23 cmd/xfsprogs/libxfs/util.c - 1.11 cmd/xfsprogs/mkfile/xfs_mkfile.c - 1.12 cmd/xfsprogs/include/buildmacros - 1.5 cmd/xfsprogs/growfs/explore.c - 1.2 - Changes for I18N support. cmd/xfsprogs/mkfs/proto.h - 1.5 - Deleted, no longer needed. From owner-linux-xfs@oss.sgi.com Wed Dec 18 17:44:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 17:44:48 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJ1ih3v018153 for ; Wed, 18 Dec 2002 17:44:43 -0800 Received: from bruce.melbourne.sgi.com (bruce.melbourne.sgi.com [134.14.55.176]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBINmtG8010865 for ; Wed, 18 Dec 2002 15:48:56 -0800 Received: (from fsgqa@localhost) by bruce.melbourne.sgi.com (8.9.3/8.9.3) id MAA22418 for linux-xfs@oss.sgi.com; Thu, 19 Dec 2002 12:47:48 +1100 Date: Thu, 19 Dec 2002 12:47:48 +1100 From: FSG QA Message-Id: <200212190147.MAA22418@bruce.melbourne.sgi.com> Subject: TAKE - qa/bench X-archive-position: 2118 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: fsgqa@bruce.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Allow for use of an external log device in benchmarks. Date: Tue Dec 17 17:10:06 PST 2002 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135429a cmd/xfstests/common.rc - 1.19 cmd/xfstests/bench - 1.14 Work to get QA to run successfully on filesystems with non-default inode sizes. Date: Wed Dec 18 17:46:51 PST 2002 Workarea: bruce.melbourne.sgi.com:/home/fsgqa/qa/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135521a cmd/xfstests/018 - 1.16 cmd/xfstests/033 - 1.9 cmd/xfstests/common.repair - 1.7 cmd/xfstests/033.out - 1.2 From owner-linux-xfs@oss.sgi.com Wed Dec 18 18:14:26 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 18 Dec 2002 18:14:28 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJ2EP3v020469 for ; Wed, 18 Dec 2002 18:14:26 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBJ0IcG8012139 for ; Wed, 18 Dec 2002 16:18:38 -0800 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id gBJ2HF3s082353 for ; Thu, 19 Dec 2002 13:17:15 +1100 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id gBJ2HFPc082342 for linux-xfs@oss.sgi.com; Thu, 19 Dec 2002 13:17:15 +1100 (EST) Date: Thu, 19 Dec 2002 13:17:15 +1100 (EST) From: Nathan Scott Message-Id: <200212190217.gBJ2HFPc082342@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump X-archive-position: 2119 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Fix build fallout from recent sync-up with kernel headers in xfsprogs - configure checks for old headers now & refuses to run if the current headers aren't installed. cheers. Date: Wed Dec 18 18:15:07 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/sector-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135526a cmd/xfsdump/configure.in - 1.26 cmd/xfsdump/VERSION - 1.44 cmd/xfsdump/doc/CHANGES - 1.52 cmd/xfsdump/copy/xfs_copy.c - 1.8 cmd/xfsdump/debian/control - 1.13 cmd/xfsdump/debian/changelog - 1.35 From owner-linux-xfs@oss.sgi.com Thu Dec 19 01:49:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 01:49:08 -0800 (PST) Received: from K-7.stesmi.com (IDENT:Dnr6jO+EcN69v+txA2Y6MfccVN8bSnYC@as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJ9n33v002760 for ; Thu, 19 Dec 2002 01:49:04 -0800 Received: from stesmi.com (IDENT:OOu5tuNZGIWFt2LIgalev8RIlU452pUj@as4-1-7.has.s.bonet.se [217.215.31.238]) by K-7.stesmi.com (8.12.4/8.12.4) with ESMTP id gBJ9pZJP030076 for ; Thu, 19 Dec 2002 10:51:35 +0100 Message-ID: <3E0196A7.4060407@stesmi.com> Date: Thu, 19 Dec 2002 10:51:35 +0100 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: Re: xfs version in 2.4.18-17SGI_XFS_1.2pre4 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2120 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stesmi@stesmi.com Precedence: bulk X-list: linux-xfs Russell Cattelan wrote: > Doh... > Ya that looks like cut-n-past error on my part. > > Ok folks ignore the RH kenels for the moment, I'll start the build over > and have the ready sometime tomorrow. > > On Wed, 2002-12-18 at 15:34, Thomas Bittermann wrote: > >>-----BEGIN PGP SIGNED MESSAGE----- >>Hash: SHA1 >> >>hello, >> >>i found this: >> >>[...] >># >># Patches 990200 to 990299 are for SGI XFS >># >> >>Patch990200: linux-2.4.19-xfs-config_stuff-pre2.patch >>Patch990201: linux-2.4.19-xfs-sysctl.patch >>Patch990202: linux-2.4.19-xfs-exports.patch >>#Patch990203: linux-2.4.19-xfs-1.2pre3.patch >>Patch990203: linux-2.4.19-xfs-20020922.patch >>Patch990204: linux-2.4.19-aggressive_readahead.patch >>[...] >> >>in kernel-2.4.18-17SGI_XFS_1.2pre4.spec file. >> >>is the right patch included? linux-2.4.19-xfs-20020922 sounds quite >>old and not like 1.2pre4 ... >> >>thanks [for this great and reliable fs] >> >>thomas >>-----BEGIN PGP SIGNATURE----- >>Version: GnuPG v1.2.1 (GNU/Linux) >> >>iD8DBQE+AOnn3E3TGgPB70IRAoJaAKCnGHPNtw38QDLo+b+zZO2mWx6aRgCbBmIA >>G913Kz4qa1UVELFAK5hrDoQ= >>=0uyj >>-----END PGP SIGNATURE----- > Yay! And I built my XFS DVD with those kernels already :) No problem, I'll just replace the kernels when they come :) On a second note (this is to all interested) I've gotten hold of an ftp that the DVD iso's will be available from shortly. No specifics but it's got a fat pipe from what I understand :) // Stefan From owner-linux-xfs@oss.sgi.com Thu Dec 19 13:40:16 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 13:45:06 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJLeF3v021709; Thu, 19 Dec 2002 13:40:16 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBJKnNKp032403; Thu, 19 Dec 2002 12:49:24 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id PAA72243; Thu, 19 Dec 2002 15:44:25 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id PAA01504; Thu, 19 Dec 2002 15:44:25 -0600 (CST) Received: from rose.americas.sgi.com (localhost [127.0.0.1]) by rose.americas.sgi.com (8.12.6/8.12.5) with ESMTP id gBJLikkx007825; Thu, 19 Dec 2002 15:44:46 -0600 Received: (from cattelan@localhost) by rose.americas.sgi.com (8.12.6/8.12.6/Submit) id gBJLijKv007823; Thu, 19 Dec 2002 15:44:45 -0600 X-Authentication-Warning: rose.americas.sgi.com: cattelan set sender to cattelan@thebarn.com using -f Subject: Correct RedHat based XFS 1.2pre4 RPMs available From: Russell Cattelan To: linux-xfs@oss.sgi.com Cc: linux-xfs-announce@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1040334285.4524.107.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) Date: 19 Dec 2002 15:44:45 -0600 X-archive-position: 2121 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs Ok so after fat fingering the SPEC file and using a really old 1.2 patch for the RedHat kernel builds Everything has be rebuilt and has been pushed out to oss. Please test this things a much as possible as we don't have much spare testing resources right now. Barring any major problems this will probably be bit for 1.2 final. -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Thu Dec 19 14:11:30 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 14:11:34 -0800 (PST) Received: from f1n1.spenet.wfu.edu (f1n1.sp2net.wfu.edu [152.17.8.11]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJMBT3v025725 for ; Thu, 19 Dec 2002 14:11:30 -0800 Received: from localhost (f1n11.sp2net.wfu.edu [152.17.8.21]) by f1n1.spenet.wfu.edu (8.11.6/8.11.6) with ESMTP id gBJMFfH31792; Thu, 19 Dec 2002 17:15:41 -0500 Subject: Re: Correct RedHat based XFS 1.2pre4 RPMs available From: "Timothy E. Miller" To: linux-xfs@oss.sgi.com In-Reply-To: <1040334285.4524.107.camel@rose.americas.sgi.com> References: <1040334285.4524.107.camel@rose.americas.sgi.com> Content-Type: text/plain Organization: Wake Forest University Message-Id: <1040336205.1698.363.camel@millerte-pc.computer.wfu.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 19 Dec 2002 17:16:46 -0500 Content-Transfer-Encoding: 7bit X-archive-position: 2122 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: millerte@wfu.edu Precedence: bulk X-list: linux-xfs On Thu, 2002-12-19 at 16:44, Russell Cattelan wrote: > Ok so after fat fingering the SPEC file and using a really old > 1.2 patch for the RedHat kernel builds > Everything has be rebuilt and has been pushed out to oss. Not that I'm complaining about 1.2pre4 being out, but did I miss an announcement? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Timothy E. Miller voice: (336)758-3257 Parallel Computing Systems Administrator fax: (336)758-7127 Wake Forest University cell: (336)782-6987 Computer Science, Information Systems, Public Health Sciences ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-linux-xfs@oss.sgi.com Thu Dec 19 14:47:56 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 14:48:00 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBJMlt3v029102 for ; Thu, 19 Dec 2002 14:47:56 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBJKqBG8008655 for ; Thu, 19 Dec 2002 12:52:12 -0800 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id gBJMon3s180184 for ; Fri, 20 Dec 2002 09:50:49 +1100 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id gBJMomuN180192 for linux-xfs@oss.sgi.com; Fri, 20 Dec 2002 09:50:48 +1100 (EST) Date: Fri, 20 Dec 2002 09:50:48 +1100 (EST) From: Nathan Scott Message-Id: <200212192250.gBJMomuN180192@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - xfsdump X-archive-position: 2123 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Flush out the rest of my userspace backlog - I18N support for utilities in the xfsdump package. Do "make distclean" first.. Date: Thu Dec 19 14:44:59 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135592a cmd/xfsdump/po/Makefile - 1.1 cmd/xfsdump/po/xfsdump.pot - 1.1 cmd/xfsdump/configure.in - 1.27 cmd/xfsdump/Makefile - 1.12 cmd/xfsdump/VERSION - 1.45 cmd/xfsdump/doc/CHANGES - 1.53 cmd/xfsdump/fsr/xfs_fsr.c - 1.14 cmd/xfsdump/copy/xfs_copy.c - 1.9 cmd/xfsdump/dump/var.c - 1.7 cmd/xfsdump/dump/content.c - 1.24 cmd/xfsdump/dump/inomap.c - 1.17 cmd/xfsdump/quota/xfsdq.c - 1.11 cmd/xfsdump/include/buildrules - 1.7 cmd/xfsdump/include/builddefs.in - 1.20 cmd/xfsdump/restore/namreg.c - 1.6 cmd/xfsdump/restore/node.c - 1.6 cmd/xfsdump/restore/tree.c - 1.17 cmd/xfsdump/restore/content.c - 1.25 cmd/xfsdump/restore/dirattr.c - 1.7 cmd/xfsdump/restore/win.c - 1.7 cmd/xfsdump/restore/inomap.c - 1.5 cmd/xfsdump/debian/control - 1.14 cmd/xfsdump/debian/changelog - 1.36 cmd/xfsdump/inventory/inv_core.c - 1.5 cmd/xfsdump/inventory/inv_stobj.c - 1.9 cmd/xfsdump/inventory/inv_mgr.c - 1.7 cmd/xfsdump/inventory/inv_fstab.c - 1.5 cmd/xfsdump/inventory/inv_api.c - 1.8 cmd/xfsdump/librmt/rmtopen.c - 1.12 cmd/xfsdump/librmt/rmtmsg.c - 1.6 cmd/xfsdump/librmt/rmtioctl.c - 1.9 cmd/xfsdump/estimate/xfs_estimate.c - 1.6 cmd/xfsdump/common/namreg.c - 1.5 cmd/xfsdump/common/content_common.c - 1.6 cmd/xfsdump/common/global.c - 1.6 cmd/xfsdump/common/openutil.c - 1.6 cmd/xfsdump/common/drive.c - 1.7 cmd/xfsdump/common/fs.c - 1.7 cmd/xfsdump/common/mlog.c - 1.12 cmd/xfsdump/common/dlog.c - 1.7 cmd/xfsdump/common/media.c - 1.5 cmd/xfsdump/common/drive_scsitape.c - 1.9 cmd/xfsdump/common/qlock.c - 1.7 cmd/xfsdump/common/util.c - 1.12 cmd/xfsdump/common/cldmgr.c - 1.9 cmd/xfsdump/common/drive_minrmt.c - 1.9 cmd/xfsdump/common/main.c - 1.24 cmd/xfsdump/common/drive_simple.c - 1.7 cmd/xfsdump/include/buildmacros - 1.5 cmd/xfsdump/include/config.h.in - 1.2 From owner-linux-xfs@oss.sgi.com Thu Dec 19 15:44:05 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 15:44:08 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBJNi43v000351 for ; Thu, 19 Dec 2002 15:44:04 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBJNi4ua000350 for linux-xfs@oss.sgi.com; Thu, 19 Dec 2002 15:44:04 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBJNi23v000331 for ; Thu, 19 Dec 2002 15:44:02 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBJNMSkQ031559; Thu, 19 Dec 2002 15:22:28 -0800 Date: Thu, 19 Dec 2002 15:22:28 -0800 Message-Id: <200212192322.gBJNMSkQ031559@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 202] XFS data corruption X-Bugzilla-Reason: AssignedTo X-archive-position: 2124 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=202 ------- Additional Comments From cw@f00f.org 2002-12-14 07:17 ------- Subject: Re: XFS data corruption On Fri, Dec 13, 2002 at 10:49:04PM -0800, bugzilla-daemon@oss.sgi.com wrote: > This will probably linked to one app doing something strange. look > at the process table when your desktop is running, make a list and > then start running stuff one at a time. Run the test and pull the > plug ofcourse. apps doing strange things shouldn't cause problems like this however, the nvidia binary only module might ... (although i've not seen this myself personally) unless someone can confirm this happens without the nv module loaded (or having been so) i would close this --cw ------- Additional Comments From xhejtman@hell.ascs.muni.cz 2002-12-19 15:22 ------- Today I've finally succeed to run 2.5.x series kernel. With default 2.5.52-bk4 I did the same test.It seems to be working ok with the last 2.5.x kernel. I'll make some more tests for sure although. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Thu Dec 19 16:32:18 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 16:32:22 -0800 (PST) Received: from andrei.myip.org (12-234-116-173.client.attbi.com [12.234.116.173]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBK0WI3v004618 for ; Thu, 19 Dec 2002 16:32:18 -0800 Received: from spampd.localdomain (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 3B5992FB3B for ; Thu, 19 Dec 2002 16:36:34 -0800 (PST) Received: from stantz.corp.sgi.com (unknown [130.62.4.42]) by andrei.myip.org (Postfix) with ESMTP id 888942FB3B for ; Thu, 19 Dec 2002 16:36:33 -0800 (PST) Received: from localhost.localdomain (localhost [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 0BB081967B for ; Thu, 19 Dec 2002 16:36:23 -0800 (PST) Subject: Re: Correct RedHat based XFS 1.2pre4 RPMs available From: Florin Andrei To: linux-xfs In-Reply-To: <1040334285.4524.107.camel@rose.americas.sgi.com> References: <1040334285.4524.107.camel@rose.americas.sgi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 19 Dec 2002 16:36:22 -0800 Message-Id: <1040344583.15731.162.camel@stantz.corp.sgi.com> Mime-Version: 1.0 X-archive-position: 2125 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: florin@sgi.com Precedence: bulk X-list: linux-xfs On Thu, 2002-12-19 at 13:44, Russell Cattelan wrote: > Ok so after fat fingering the SPEC file and using a really old > 1.2 patch for the RedHat kernel builds > Everything has be rebuilt and has been pushed out to oss. Cool! Now, i don't want to be a nitpicker, but is it possible to build these things based on the latest RH kernel update? (2.4.18-18.8.0) From what i can tell, usually the drivers, modified kernels and other kernel stuff made by third parties, either supports all kernel releases with the distribution up to date (messy and difficult), or support only the original kernel provided by the initial distribution release + the latest update available at the moment of release. The latter is what nVidia does. If i were to choose between supporting the initial kernel release and the latest update, i'll choose the update. -- Florin Andrei "And the man in the rain picked up his bag of secrets, and journeyed up the mountainside, far above the clouds, and nothing was ever heard from him again, except for the sound of Tubular Bells." - Mike Oldfield From owner-linux-xfs@oss.sgi.com Thu Dec 19 16:35:51 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 16:35:53 -0800 (PST) Received: from andrei.myip.org (12-234-116-173.client.attbi.com [12.234.116.173]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBK0Zp3v005291 for ; Thu, 19 Dec 2002 16:35:51 -0800 Received: from spampd.localdomain (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 1E8D52FB3B for ; Thu, 19 Dec 2002 16:40:07 -0800 (PST) Received: from stantz.corp.sgi.com (unknown [130.62.4.42]) by andrei.myip.org (Postfix) with ESMTP id 913382FB3B for ; Thu, 19 Dec 2002 16:40:06 -0800 (PST) Received: from localhost.localdomain (localhost [127.0.0.1]) by stantz.corp.sgi.com (Postfix) with ESMTP id 3C6DE1967B for ; Thu, 19 Dec 2002 16:39:56 -0800 (PST) Subject: Re: redhat-8.0 From: Florin Andrei To: linux-xfs In-Reply-To: <1040056469.28990.6.camel@mosix> References: <1040056469.28990.6.camel@mosix> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 19 Dec 2002 16:39:56 -0800 Message-Id: <1040344796.14990.166.camel@stantz.corp.sgi.com> Mime-Version: 1.0 X-archive-position: 2126 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: florin@sgi.com Precedence: bulk X-list: linux-xfs On Mon, 2002-12-16 at 08:34, Matt Schillinger wrote: > Is there any chance that a redhat 8.0 install iso would be made to > support XFS? (alternative solution) If having a / partition formatted in something other than XFS is acceptable for you (it sometimes really is, depending on what you're doing), then you could simply use the original RH installer and partition just the / and let the rest of the space unpartitioned, install the distribution, then download and install the XFS kernel and tools, partition the rest (/var, /home or whatever you need), format those things as XFS, mount'em and that's it. -- Florin Andrei "And the man in the rain picked up his bag of secrets, and journeyed up the mountainside, far above the clouds, and nothing was ever heard from him again, except for the sound of Tubular Bells." - Mike Oldfield From owner-linux-xfs@oss.sgi.com Thu Dec 19 23:39:14 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 19 Dec 2002 23:39:17 -0800 (PST) Received: from phoenix.infradead.org (phoenix.mvhi.com [195.224.96.167]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBK7dC3v011691 for ; Thu, 19 Dec 2002 23:39:13 -0800 Received: from hch by phoenix.infradead.org with local (Exim 4.10) id 18PHod-00061K-00; Fri, 20 Dec 2002 07:43:27 +0000 Date: Fri, 20 Dec 2002 07:43:27 +0000 From: Christoph Hellwig To: Florin Andrei Cc: linux-xfs Subject: Re: Correct RedHat based XFS 1.2pre4 RPMs available Message-ID: <20021220074327.A23139@infradead.org> References: <1040334285.4524.107.camel@rose.americas.sgi.com> <1040344583.15731.162.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1040344583.15731.162.camel@stantz.corp.sgi.com>; from florin@sgi.com on Thu, Dec 19, 2002 at 04:36:22PM -0800 X-archive-position: 2127 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@infradead.org Precedence: bulk X-list: linux-xfs On Thu, Dec 19, 2002 at 04:36:22PM -0800, Florin Andrei wrote: > On Thu, 2002-12-19 at 13:44, Russell Cattelan wrote: > > Ok so after fat fingering the SPEC file and using a really old > > 1.2 patch for the RedHat kernel builds > > Everything has be rebuilt and has been pushed out to oss. > > Cool! > > Now, i don't want to be a nitpicker, but is it possible to build these > things based on the latest RH kernel update? (2.4.18-18.8.0) > > >From what i can tell, usually the drivers, modified kernels and other > kernel stuff made by third parties, either supports all kernel releases > with the distribution up to date (messy and difficult), or support only > the original kernel provided by the initial distribution release + the > latest update available at the moment of release. We already support 2.4.18-17.8.0 and 2.4.18-18.8.0 is not that different. I will update the rpm for 1.2-final, but there are rumours that there will be new errata kernel from RH soon for the ext3 data=journal issue.. From owner-linux-xfs@oss.sgi.com Fri Dec 20 00:58:30 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Dec 2002 00:58:35 -0800 (PST) Received: from K-7.stesmi.com (IDENT:ftC1ICP3P7HnGkgsnTcgRAf5FCcUDF3y@as4-1-7.has.s.bonet.se [217.215.31.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBK8wL3v012807 for ; Fri, 20 Dec 2002 00:58:26 -0800 Received: from stesmi.com (IDENT:2uNT+d3bNBCjFPf/9WEmWp1CNXQ0s90L@as4-1-7.has.s.bonet.se [217.215.31.238]) by K-7.stesmi.com (8.12.4/8.12.4) with ESMTP id gBK90pJP003649 for ; Fri, 20 Dec 2002 10:00:51 +0100 Message-ID: <3E02DC43.4000003@stesmi.com> Date: Fri, 20 Dec 2002 10:00:51 +0100 From: Stefan Smietanowski User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: RedHat 8.0 XFS DVD v0.0.7 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2128 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stesmi@stesmi.com Precedence: bulk X-list: linux-xfs I am proud to announce the first public release of the RedHat 8.0 XFS DVD v0.0.7! The image is available from http://www.stud.ntnu.no/~ragnarkj/download/RH-XFS-DVD/ or should be in a few hours anyway. What's on this DVD: * RedHat 8.0 "Psyche" CDs 1-5, including the SRPMS. * All updates that were released up to and including 2002-12-19 at 22:00 GMT. They are installed automatically when the system is installed. The DVD does not contain the old RPMS. * The installer from the XFS 1.2pre1 release from SGI. * All RPMS from the XFS 1.2pre4 release from SGI. The contrib directory on the DVD contains extra files that are not installed by default. Currently contains an alternate 2.4.19-based kernel released by SGI. Known Bugs: - Doesn't work. + Contains a bugfix but needs to be tested by more people. * Fixed ? Unknown if bug still exists. Usually a new bug found in an older version. - You can only select English languages to install. Same bug exists in the original XFS installer CD. - GRUB won't install properly at all for some reason. Exists in XFS installer CD. + When you verify the MD5 sum using the installer it afterwards asks you to insert the SGI CD and does not accept this DVD. ? A system installed with 0.0.2 had problems in konsole. When writing "foo" it came out "f o o". xterm worked fine. Haven't tried a later release in konsole so I don't know if it's still there. Might also be the kde update. Version history: 0.0.1 2002-12-xx Initial version. Not released. Worked fine. I could even verify the DVD with the MD5 function of the installer. Had the bug that made it ask for the XFS CD after verifying MD5. 0.0.2 2002-12-xx Updated version. Contained a few extra RPMS in the contrib directory. Minor tweaks. Not released. Had a fix for the problem above. 0.0.3 2002-12-xx Same as 0.0.2 but this time I didn't forget to implant the MD5 sum into the image (stupid me). Not released. 0.0.4 2002-12-12 Added latest updates. Verified it works from a DVD-RW. Not released. 0.0.5 2002-12-13 Added latest updates: httpd and mod_ssl. Finished my script that I use to build the DVD with. Not released. 0.0.6 2002-12-18 The ethernet and pcmcia on the laptop died and I had the whole build system on there. Took some time to get the relevant info off of it and start building again. SGI also released 1.2pre4 of the kernel so I updated all files to that. Added updated net-snmp. Not released. 0.0.7 2002-12-20 Found out that the kernel from 1.2pre4 is wrong so I waited for the respin to come out and released it when it had. No other changes. Please download and test and read the README-XFS-DVD. Also please mail me if it works or not or any issues you have with it! This release is not endorsed nor supported by either RedHat or SGI. If it doesn't work, don't bug them about it. // Stefan From owner-linux-xfs@oss.sgi.com Fri Dec 20 10:50:52 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Dec 2002 10:50:57 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBKIop3v032575 for ; Fri, 20 Dec 2002 10:50:52 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBKJ15kq009742 for ; Fri, 20 Dec 2002 13:01:05 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id MAA54208 for ; Fri, 20 Dec 2002 12:55:05 -0600 (CST) Received: from taclab54.munich.sgi.com (taclab54.munich.sgi.com [144.253.195.54]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA94947 for ; Fri, 20 Dec 2002 12:55:04 -0600 (CST) Received: (from hch@localhost) by taclab54.munich.sgi.com (8.11.6/8.11.6) id gBL2A0M02027 for linux-xfs@oss.sgi.com; Fri, 20 Dec 2002 21:10:00 -0500 Resent-Message-Id: <200212210210.gBL2A0M02027@taclab54.munich.sgi.com> Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id MAA98290 for ; Fri, 20 Dec 2002 12:53:30 -0600 (CST) Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by nodin.corp.sgi.com (8.12.3/8.11.4/nodin-1.0) with ESMTP id gBKIrTQb44124211 for ; Fri, 20 Dec 2002 10:53:29 -0800 (PST) Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBKIpYKP001429 for ; Fri, 20 Dec 2002 19:51:34 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBKIpX1t001428 for hch@sgi.com; Fri, 20 Dec 2002 19:51:33 +0100 Date: Fri, 20 Dec 2002 19:51:33 +0100 From: Christoph Hellwig Message-Id: <200212201851.gBKIpX1t001428@lab343.munich.sgi.com> Subject: TAKE - To: undisclosed-recipients:; Resent-From: hch@sgi.com Resent-Date: Fri, 20 Dec 2002 21:10:00 -0500 Resent-To: linux-xfs@oss.sgi.com X-archive-position: 2129 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@sgi.com Precedence: bulk X-list: linux-xfs "merge" the 2.4 fsx fix for block size < page size to 2.5. This needed major changes to actually fit. Date: Fri Dec 20 10:51:34 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/2.5.x-xfs Author: cattelan Merged by: hch Merged mods: 2.4.x-xfs:slinx:132210a The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.5.x-xfs Modid: 2.5.x-xfs:slinx:132210a linux/fs/buffer.c - 1.144 - Merge of 2.4.x-xfs:slinx:132210a by hch. 2 parts to this patch. The first part is making buffer.c aware of delay buffers, this allows us to remove BH_Uptodate from linvfs_get_block_core. The second part is a fix to end_buffer_io_async; it was checking all the buffer heads on a page but not if they were uptodate or not, and therefore incorrectly setting the page uptodate. Stale data was then exposed on portions of page not correctly cleared because only part of the page was actually valid. linux/fs/xfs/Makefile - 1.164 linux/fs/xfs/pagebuf/page_buf.h - 1.62 linux/include/linux/buffer_head.h - 1.15 linux/fs/xfs/linux/xfs_aops.c - 1.24 - Merge of 2.4.x-xfs:slinx:132210a by hch. Remove BH_uptodate from get block. Rework the logic a bit in delalloc_convert. From owner-linux-xfs@oss.sgi.com Fri Dec 20 11:15:22 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Dec 2002 11:15:24 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBKJFL3v000763 for ; Fri, 20 Dec 2002 11:15:22 -0800 Received: from lab343.munich.sgi.com (lab343.munich.sgi.com [144.253.195.43]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBKHJfG8012179 for ; Fri, 20 Dec 2002 09:19:42 -0800 Received: from lab343.munich.sgi.com (localhost [127.0.0.1]) by lab343.munich.sgi.com (8.12.3/8.12.2/SuSE Linux 0.6) with ESMTP id gBKJHAKP001566 for ; Fri, 20 Dec 2002 20:17:10 +0100 Received: (from hch@localhost) by lab343.munich.sgi.com (8.12.3/8.12.2/Submit) id gBKJHATE001565 for linux-xfs@oss.sgi.com; Fri, 20 Dec 2002 20:17:10 +0100 Date: Fri, 20 Dec 2002 20:17:10 +0100 From: Christoph Hellwig Message-Id: <200212201917.gBKJHATE001565@lab343.munich.sgi.com> Subject: TAKE 876844 - fix too long current->comm for pagebuf worker threads (and use the 2.5 naming) To: undisclosed-recipients:; X-archive-position: 2130 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: hch@lab343.munich.sgi.com Precedence: bulk X-list: linux-xfs Date: Fri Dec 20 11:18:03 PST 2002 Workarea: lab343.munich.sgi.com:/home/hch/repo/slinx/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:135674a linux/fs/xfs/pagebuf/page_buf.c - 1.89 - fix too long current->comm for pagebuf worker threads (and use the 2.5 naming) From owner-linux-xfs@oss.sgi.com Fri Dec 20 13:10:30 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 20 Dec 2002 13:10:35 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.183]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBKLAT3v004926 for ; Fri, 20 Dec 2002 13:10:30 -0800 Received: from [212.227.126.162] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18PSZ2-0004q2-00 for linux-xfs@oss.sgi.com; Fri, 20 Dec 2002 20:12:04 +0100 Received: from [80.140.33.245] (helo=idoru) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18PSZ2-0002yB-00 for linux-xfs@oss.sgi.com; Fri, 20 Dec 2002 20:12:04 +0100 Date: Fri, 20 Dec 2002 20:13:02 +0100 From: Tobias Eichert To: linux-xfs@oss.sgi.com Subject: XFS + grsecurity + linux kernel 2.4.20 Message-Id: <20021220201302.4690e042.tobias@databoogie.net> X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="=.Gal5_(nEL:1Sh," X-archive-position: 2131 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tobias@databoogie.net Precedence: bulk X-list: linux-xfs --=.Gal5_(nEL:1Sh, Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hello everybody, regarding the latest Linux kernel version, 2.4.20, I considered if someone already has created an XFS - grsecurity combopatch like the one for kernel version 2.4.19 by www.lbsd.net. The problem is that XFS's ACL and grsecurity's internal one won't coexist peacefully by default. :/ Keep up the good work. Best Regards, Tobias Eichert --=.Gal5_(nEL:1Sh, Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+A2vFB8K6Qr5hQAMRApjxAJ9kNJTUFzuUiuGjKPj74/Q3VAByZwCbBeY1 fTesLBnY+FcToqpjKWFny9k= =jePO -----END PGP SIGNATURE----- --=.Gal5_(nEL:1Sh,-- From owner-linux-xfs@oss.sgi.com Sat Dec 21 04:33:23 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Dec 2002 04:33:29 -0800 (PST) Received: from stine.vestdata.no (IDENT:0@stine.vestdata.no [195.204.68.10]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBLCXL3v032584 for ; Sat, 21 Dec 2002 04:33:22 -0800 Received: (from ragnark@localhost) by stine.vestdata.no (8.11.6/8.11.2) id gBLCbca27855; Sat, 21 Dec 2002 13:37:38 +0100 Date: Sat, 21 Dec 2002 13:37:38 +0100 From: =?iso-8859-1?Q?Ragnar_Kj=F8rstad?= To: Stefan Smietanowski Cc: linux-xfs@oss.sgi.com Subject: Re: RedHat 8.0 XFS DVD v0.0.7 Message-ID: <20021221133738.M1813@vestdata.no> References: <3E02DC43.4000003@stesmi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <3E02DC43.4000003@stesmi.com>; from stesmi@stesmi.com on Fri, Dec 20, 2002 at 10:00:51AM +0100 X-MIME-Autoconverted: from 8bit to quoted-printable by stine.vestdata.no id gBLCbca27855 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBLCXN3v032585 X-archive-position: 2132 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: xfs@ragnark.vestdata.no Precedence: bulk X-list: linux-xfs On Fri, Dec 20, 2002 at 10:00:51AM +0100, Stefan Smietanowski wrote: > The image is available from > http://www.stud.ntnu.no/~ragnarkj/download/RH-XFS-DVD/ > or should be in a few hours anyway. Unfortenately fmirror failed to download > 2GB files, so it's still not there. I've started a manual download now, so in an estimated 10 hours the files should be available. -- Ragnar Kjrstad From owner-linux-xfs@oss.sgi.com Sat Dec 21 05:37:49 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Dec 2002 05:37:54 -0800 (PST) Received: from banna (fe239189.ot.FreeBit.NE.JP [219.109.239.189]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBLDbR3v000896 for ; Sat, 21 Dec 2002 05:37:44 -0800 Received: from C ([192.168.0.4]) by banna (8.9.3+3.2W/3.7W) with SMTP id WAA27407; Sat, 21 Dec 2002 22:40:03 +0900 Message-Id: <200212211340.WAA27407@banna> From: =?iso-2022-jp?B?am1haWw4ODg4anA=?= To: =?iso-2022-jp?B?NTAwMDA=?=@banna.sgi.com Reply-To: jmail8888jp@yahoo.co.jp Date: Sat, 21 Dec 2002 22:39:20 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2133 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jmail8888jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info_sssjp@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　001-373-188-8477 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.xx-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.ww-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Sat Dec 21 13:20:09 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 21 Dec 2002 13:20:12 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBLLK93v004741 for ; Sat, 21 Dec 2002 13:20:09 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBLLK9b2004740 for linux-xfs@oss.sgi.com; Sat, 21 Dec 2002 13:20:09 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBLLK73x004726 for ; Sat, 21 Dec 2002 13:20:07 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBLLGHeL004711; Sat, 21 Dec 2002 13:16:17 -0800 Date: Sat, 21 Dec 2002 13:16:17 -0800 Message-Id: <200212212116.gBLLGHeL004711@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 197] stalled files in /var/lock, data fork in ino 79692177 claims free block 5040984 X-Bugzilla-Reason: AssignedTo X-archive-position: 2134 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=197 ------- Additional Comments From knutjbj@online.no 2002-12-21 13:16 ------- My pc was running 1.2pre3 with redhat 7.3 kernel. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Sun Dec 22 04:14:06 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Dec 2002 04:14:12 -0800 (PST) Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBMCE63v013332 for ; Sun, 22 Dec 2002 04:14:06 -0800 Received: (from xfs-master@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBMCE666013331 for linux-xfs@oss.sgi.com; Sun, 22 Dec 2002 04:14:06 -0800 Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.5/8.12.5) with ESMTP id gBMCE33x013317 for ; Sun, 22 Dec 2002 04:14:03 -0800 Received: (from apache@localhost) by oss.sgi.com (8.12.5/8.12.5/Submit) id gBMBrU0m012722; Sun, 22 Dec 2002 03:53:30 -0800 Date: Sun, 22 Dec 2002 03:53:30 -0800 Message-Id: <200212221153.gBMBrU0m012722@oss.sgi.com> From: bugzilla-daemon@oss.sgi.com To: xfs-master@oss.sgi.com Subject: [Bug 197] stalled files in /var/lock, data fork in ino 79692177 claims free block 5040984 X-Bugzilla-Reason: AssignedTo X-archive-position: 2135 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: bugzilla-daemon@oss.sgi.com Precedence: bulk X-list: linux-xfs http://oss.sgi.com/bugzilla/show_bug.cgi?id=197 ------- Additional Comments From knutjbj@online.no 2002-12-22 03:53 ------- wrong redhat 8.0 with 1.2pre3. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. From owner-linux-xfs@oss.sgi.com Sun Dec 22 08:42:19 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Dec 2002 08:42:23 -0800 (PST) Received: from spf1.us.outblaze.com (205-158-62-139.outblaze.com [205.158.62.139]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBMGgJ3v025321 for ; Sun, 22 Dec 2002 08:42:19 -0800 Received: (qmail 27598 invoked from network); 22 Dec 2002 16:46:31 -0000 Received: from unknown (205.158.62.68) by 205-158-62-139.outblaze.com with QMQP; 22 Dec 2002 16:46:31 -0000 Received: (qmail 6874 invoked from network); 22 Dec 2002 16:46:25 -0000 Received: from unknown (HELO ws5-1.us4.outblaze.com) (205.158.62.131) by 205-158-62-153.outblaze.com with SMTP; 22 Dec 2002 16:46:25 -0000 Received: (qmail 17496 invoked by uid 1001); 22 Dec 2002 16:46:23 -0000 Message-ID: <20021222164623.17494.qmail@linuxmail.org> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [217.228.202.175] by ws5-1.us4.outblaze.com with http for mrich@linuxmail.org; Mon, 23 Dec 2002 00:46:23 +0800 From: "Philipp H" To: linux-xfs@oss.sgi.com Date: Mon, 23 Dec 2002 00:46:23 +0800 Subject: bad primary superblock - bad magic number X-Originating-Ip: 217.228.202.175 X-Originating-Server: ws5-1.us4.outblaze.com X-archive-position: 2136 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mrich@linuxmail.org Precedence: bulk X-list: linux-xfs Hello! Today I reinstalled my gentoo system... so I have a new kernel version 2.4.19-xfs-r2 instead of 2.4.19-xfs-r1! But now, I am unable to mount my home partition!!! :( plinux011 root # losetup -a /dev/loop/0: [0008]:375 (/dev/hdc7) offset 0, AES128 encryption plinux011 root # mount /dev/loop/0 /home/phil -t xfs mount: wrong fs type, bad option, bad superblock on /dev/loop0, or too many mounted file systems plinux011 root # xfs_repair /dev/loop/0 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .............................................................................................................................Sorry, could not find valid secondary superblock Exiting now. Any iedeas? Please help me! MrIch -- ______________________________________________ http://www.linuxmail.org/ Now with POP3/IMAP access for only US$19.95/yr Powered by Outblaze From owner-linux-xfs@oss.sgi.com Sun Dec 22 19:07:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 22 Dec 2002 19:07:39 -0800 (PST) Received: from zok.sgi.com (zok.SGI.COM [204.94.215.101]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBN37Y3v000404 for ; Sun, 22 Dec 2002 19:07:34 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by zok.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBN2H5Kp018151 for ; Sun, 22 Dec 2002 18:17:05 -0800 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id VAA27359; Sun, 22 Dec 2002 21:11:57 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id VAA16126; Sun, 22 Dec 2002 21:11:57 -0600 (CST) Date: Sun, 22 Dec 2002 21:06:17 -0600 (CST) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Philipp H cc: linux-xfs@oss.sgi.com Subject: Re: bad primary superblock - bad magic number In-Reply-To: <20021222164623.17494.qmail@linuxmail.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2137 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs I have no idea what gentoo uses for xfs code, so I'm not sure what to tell you. Very odd that it couldn't even find a backup superblock. For starters, you're certain that /dev/hdc7 is an xfs filesystem? Try xfs_db /dev/hdc7 and type: xfs_db: sb 0 xfs_db: p and see what it gives you, that way we can see what the primary superblock looks like. -Eric On Mon, 23 Dec 2002, Philipp H wrote: > Hello! > > Today I reinstalled my gentoo system... so I have a new kernel version 2.4.19-xfs-r2 instead of 2.4.19-xfs-r1! > But now, I am unable to mount my home partition!!! :( > > plinux011 root # losetup -a > /dev/loop/0: [0008]:375 (/dev/hdc7) offset 0, AES128 encryption > > plinux011 root # mount /dev/loop/0 /home/phil -t xfs > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > or too many mounted file systems > > plinux011 root # xfs_repair /dev/loop/0 > Phase 1 - find and verify superblock... > bad primary superblock - bad magic number !!! > > attempting to find secondary superblock... > .............................................................................................................................Sorry, could not find valid secondary > superblock > Exiting now. > > Any iedeas? Please help me! > > MrIch > -- > ______________________________________________ > http://www.linuxmail.org/ > Now with POP3/IMAP access for only US$19.95/yr > > Powered by Outblaze > > From owner-linux-xfs@oss.sgi.com Mon Dec 23 00:10:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 00:11:06 -0800 (PST) Received: from spf1.us.outblaze.com (205-158-62-139.outblaze.com [205.158.62.139]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBN8Ax3v004289 for ; Mon, 23 Dec 2002 00:10:59 -0800 Received: (qmail 15783 invoked from network); 23 Dec 2002 08:15:24 -0000 Received: from unknown (205.158.62.68) by 205-158-62-139.outblaze.com with QMQP; 23 Dec 2002 08:15:24 -0000 Received: (qmail 31554 invoked from network); 23 Dec 2002 08:15:24 -0000 Received: from unknown (HELO ws5-2.us4.outblaze.com) (205.158.62.133) by 205-158-62-153.outblaze.com with SMTP; 23 Dec 2002 08:15:24 -0000 Received: (qmail 30229 invoked by uid 1001); 23 Dec 2002 08:15:24 -0000 Message-ID: <20021223081524.30228.qmail@linuxmail.org> Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [195.145.160.218] by ws5-3.us4.outblaze.com with http for mrich@linuxmail.org; Mon, 23 Dec 2002 16:15:24 +0800 From: "Philipp H" To: linux-xfs@oss.sgi.com Date: Mon, 23 Dec 2002 16:15:24 +0800 Subject: Re: bad primary superblock - bad magic number X-Originating-Ip: 195.145.160.218 X-Originating-Server: ws5-3.us4.outblaze.com X-archive-position: 2138 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mrich@linuxmail.org Precedence: bulk X-list: linux-xfs Yesterday evening, I booted from a Knoppix Live CD... Knoppix supports loop AES encryption too! So I set up the loop device and mounted the partition successfully! Then I copyed everything to a backup partition and recreate ( on gentoo) the XFS filesystem (mkfs.xfs) and everything is fine... I have absolutely no idea why the old xfs partition was not "mountable"! Very suspect for me... but now I am happy to have my data back! ----- Original Message ----- From: Eric Sandeen Date: Sun, 22 Dec 2002 21:06:17 -0600 (CST) To: Philipp H Subject: Re: bad primary superblock - bad magic number > I have no idea what gentoo uses for xfs code, so I'm not sure what > to tell you. Very odd that it couldn't even find a backup superblock. > > For starters, you're certain that /dev/hdc7 is an xfs filesystem? > > Try xfs_db /dev/hdc7 and type: > > xfs_db: sb 0 > xfs_db: p > > and see what it gives you, that way we can see what the primary > superblock looks like. > > -Eric > > On Mon, 23 Dec 2002, Philipp H wrote: > > > Hello! > > > > Today I reinstalled my gentoo system... so I have a new kernel version 2.4.19-xfs-r2 instead of 2.4.19-xfs-r1! > > But now, I am unable to mount my home partition!!! :( > > > > plinux011 root # losetup -a > > /dev/loop/0: [0008]:375 (/dev/hdc7) offset 0, AES128 encryption > > > > plinux011 root # mount /dev/loop/0 /home/phil -t xfs > > mount: wrong fs type, bad option, bad superblock on /dev/loop0, > > or too many mounted file systems > > > > plinux011 root # xfs_repair /dev/loop/0 > > Phase 1 - find and verify superblock... > > bad primary superblock - bad magic number !!! > > > > attempting to find secondary superblock... > > .............................................................................................................................Sorry, could not find valid secondary > > superblock > > Exiting now. > > > > Any iedeas? Please help me! > > > > MrIch > > -- > > ______________________________________________ > > http://www.linuxmail.org/ > > Now with POP3/IMAP access for only US$19.95/yr > > > > Powered by Outblaze > > > > > > -- ______________________________________________ http://www.linuxmail.org/ Now with POP3/IMAP access for only US$19.95/yr Powered by Outblaze From owner-linux-xfs@oss.sgi.com Mon Dec 23 06:21:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 06:21:08 -0800 (PST) Received: from esds.vss.fsi.com (adsl-66-136-174-212.dsl.stlsmo.swbell.net [66.136.174.212]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNEL13v013156 for ; Mon, 23 Dec 2002 06:21:02 -0800 Received: from mosix (mosix [198.51.26.70]) by esds.vss.fsi.com (8.9.1a/8.9.1) with ESMTP id IAA06756 for ; Mon, 23 Dec 2002 08:25:26 -0600 (CST) Subject: System Lockups From: Matt Schillinger To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 23 Dec 2002 08:27:43 -0600 Message-Id: <1040653664.24033.19.camel@mosix> Mime-Version: 1.0 X-archive-position: 2139 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mschilli@vss.fsi.com Precedence: bulk X-list: linux-xfs Just wondering if anyone knows of any reason why a xfs redhat 8.0 would just lock up, and leave no log traces in the messages file.. I do not really have any data that says that it is XFS related (in fact I doubt it). I am just not sure where to go for answers.. I've looked on the web and never found anything relevant. From what I can gather, the machine dies on its network connection, and all keyboard activity locks up. The screen continues to display the last thing that occured before the lockup, but there is no additional input/output. From what I can tell, it has only happened in periods of inactivity (this is a new development machine). thanks for any help anyone can offer. And sorry if i'm spamming this list.. Any responses, please email me directly, unless it is felt that the problem relates to the xfs kernel. Thanks, -- Matt Schillinger mschilli@vss.fsi.com From owner-linux-xfs@oss.sgi.com Mon Dec 23 06:40:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 06:40:37 -0800 (PST) Received: from mail.lbsd.net (mail.lbsd.net [196.25.111.97]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNEeW3v013675 for ; Mon, 23 Dec 2002 06:40:34 -0800 Received: from localhost (nkukard@localhost) by mail.lbsd.net (8.12.1/8.12.1) with ESMTP id gBNEj2a1005384; Mon, 23 Dec 2002 16:45:03 +0200 Date: Mon, 23 Dec 2002 16:45:02 +0200 (SAST) From: Nigel Kukard To: Tobias Eichert cc: Subject: Re: XFS + grsecurity + linux kernel 2.4.20 In-Reply-To: <20021220201302.4690e042.tobias@databoogie.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2140 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nkukard@lbsd.net Precedence: bulk X-list: linux-xfs HI Tobias, The moment XFS 1.2 is relesed and the beta grsecurity patch becomes stable we will release the updated patches for 2.4.20. Kind Regards Nigel Kukard LBSD On Fri, 20 Dec 2002, Tobias Eichert wrote: > Hello everybody, > regarding the latest Linux kernel version, > 2.4.20, I considered if someone already > has created an XFS - grsecurity combopatch > like the one for kernel version 2.4.19 by > www.lbsd.net. > The problem is that XFS's ACL > and grsecurity's internal one won't coexist > peacefully by default. :/ > > Keep up the good work. > > Best Regards, > Tobias Eichert > -- Nigel Kukard (Chief Executive Officer) Lando Technologies Africa (Pty) Ltd nigel@lando.co.za www.lando.co.za Tel: 083 399 5822 Fax: 086 1100036 Hoheisen Park Bellville, Cape Town National Internet Service Provider The best language to use is the language that was designed for what you want to use it for - 1997 ===================================================================== Disclaimer ---------- The contents of this message and any attachments are intended solely for the addressee's use and may be legally privileged and/or confidential information. This message may not be retained, distributed, copied or used if you are not he addressee of this message. If this message was sent to you in error, please notify the sender immediately by reply e-mail and then destroy the message and any copies thereof. Opinions, conclusions and other information in this message may be personal to the sender and is not that of Lando Technologies Africa or any of it's subsideries, associated companies or principals and is therefore not endorsed by any of the Lando groups of companies. Due to e-maill communication being insecure, Lando groups of companies do not guarantee confidentiality, security, accuracy or performance of the e-mail. Any liability for viruses is excluded to the fullest extent. From owner-linux-xfs@oss.sgi.com Mon Dec 23 06:48:43 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 06:48:46 -0800 (PST) Received: from shade.globe.cz (ondrej.sury.org [193.85.29.133]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNEmf3v014215 for ; Mon, 23 Dec 2002 06:48:42 -0800 Received: (qmail 11597 invoked by uid 1000); 23 Dec 2002 14:53:07 -0000 To: linux-xfs@oss.sgi.com Subject: zombie processes on SMP kernel under high load (kernel2.4.18 + xfs1.1) From: Ondrej Sury Date: Mon, 23 Dec 2002 15:53:07 +0100 Message-ID: <87vg1kaiss.fsf@globe.cz> Lines: 30 User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 2141 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sury.ondrej@globe.cz Precedence: bulk X-list: linux-xfs Hello, maybe not XFS related, but it happens when XFS is present. System is: 2x P4 Xeon board is Intel serverboard RAID-5 on Adaptec 2110S. This bugs reveals only under high load (CPU), suddenly there started to be zombie (D state) processes which had init as parent, and I was unable to do anything else then reboot. There was no syslog/klog message. I use this server as NFS backend to mail service and since frontend which is delivering mail had failure on one disk in array I switched delivery to backend and it ended with 5k+ zombie processes of kavdaemon and other processes. This bug seem to be ACL related since there was report in czech linux mailing list about same experience on ext3+xattr+acl. I am not able to do destructive tests on this machine since it holds customer data, but I am willing to cooperate since I would like to use XFS as file server file system. Had anyone same experience or I am alone? O. -- Ondrej Sury - CIO Globe Internet s.r.o. http://globe.cz/ Tel: +420(2)35365000 Fax: +420(2)35365009 Planickova 1, 162 00 Praha 6 From owner-linux-xfs@oss.sgi.com Mon Dec 23 06:55:45 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 06:55:47 -0800 (PST) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNEti3v014695 for ; Mon, 23 Dec 2002 06:55:45 -0800 Received: from auto-nb1.xs4all.nl (host-4.coltex.demon.nl [212.238.252.68]) by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id gBNF0E9h013847; Mon, 23 Dec 2002 16:00:15 +0100 (CET) Message-Id: <4.3.2.7.2.20021223155754.042fb0f8@pop.xs4all.nl> X-Sender: knuffie@pop.xs4all.nl X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 23 Dec 2002 16:00:08 +0100 To: Matt Schillinger , linux-xfs@oss.sgi.com From: Seth Mos Subject: Re: System Lockups In-Reply-To: <1040653664.24033.19.camel@mosix> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-archive-position: 2142 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: knuffie@xs4all.nl Precedence: bulk X-list: linux-xfs At 08:27 23-12-2002 -0600, Matt Schillinger wrote: >Just wondering if anyone knows of any reason why a xfs redhat 8.0 would >just lock up, and leave no log traces in the messages file.. I do not >really have any data that says that it is XFS related (in fact I doubt >it). I am just not sure where to go for answers.. I've looked on the web >and never found anything relevant. From what I can gather, the machine >dies on its network connection, and all keyboard activity locks up. >The screen continues to display the last thing that occured before the >lockup, but there is no additional input/output. From what I can tell, >it has only happened in periods of inactivity (this is a new development >machine). Does it have a broadcom gigabit card (bcm5700). If so try either the 1.2 tg3 driver from Jeff Garzik or switch to the bcm5700 which is already available on your machine. It's a known problem and 2.4.18-19 is supposed to fix this. But there is no XFS kernel from that errata release yet. Cheers -- Seth It might just be your lucky day, if you only knew. From owner-linux-xfs@oss.sgi.com Mon Dec 23 07:19:32 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 07:19:36 -0800 (PST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNFJU3v015285 for ; Mon, 23 Dec 2002 07:19:31 -0800 Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 18QUQw-0003Ls-00; Mon, 23 Dec 2002 16:23:58 +0100 Received: from [80.140.39.46] (helo=idoru) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 18QUQw-000781-00; Mon, 23 Dec 2002 16:23:58 +0100 Date: Mon, 23 Dec 2002 16:24:54 +0100 From: Tobias Eichert To: Nigel Kukard Cc: linux-xfs@oss.sgi.com Subject: Re: XFS + grsecurity + linux kernel 2.4.20 Message-Id: <20021223162454.5c9f32c8.tobias@databoogie.net> In-Reply-To: References: <20021220201302.4690e042.tobias@databoogie.net> X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; ) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 2143 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: tobias@databoogie.net Precedence: bulk X-list: linux-xfs Ah, thanks a lot. I really like your combopatch. :) Best Regards, Tobias On Mon, 23 Dec 2002 16:45:02 +0200 (SAST) Nigel Kukard wrote: > HI Tobias, > > The moment XFS 1.2 is relesed and the beta grsecurity > patch becomes stable we will release the updated > patches for 2.4.20. > > > Kind Regards > Nigel Kukard > LBSD > > On Fri, 20 Dec 2002, Tobias Eichert wrote: > > > Hello everybody, > > regarding the latest Linux kernel version, > > 2.4.20, I considered if someone already > > has created an XFS - grsecurity combopatch > > like the one for kernel version 2.4.19 by > > www.lbsd.net. > > The problem is that XFS's ACL > > and grsecurity's internal one won't coexist > > peacefully by default. :/ > > > > Keep up the good work. > > > > Best Regards, > > Tobias Eichert > > > > -- > > > Nigel Kukard (Chief Executive Officer) > Lando Technologies Africa (Pty) Ltd > nigel@lando.co.za www.lando.co.za > Tel: 083 399 5822 Fax: 086 1100036 > Hoheisen Park Bellville, Cape Town > National Internet Service Provider > > > The best language to use is the language that was designed for > what you want to use it for - 1997 > > > ===================================================================== > > Disclaimer > ---------- > The contents of this message and any attachments are intended > solely for the addressee's use and may be legally privileged and/or > confidential information. This message may not be retained, > distributed, copied or used if you are not he addressee of this > message. If this message was sent to you in error, please notify > the sender immediately by reply e-mail and then destroy the message > and any copies thereof. > > Opinions, conclusions and other information in this message may be > personal to the sender and is not that of Lando Technologies Africa > or any of it's subsideries, associated companies or principals and > is therefore not endorsed by any of the Lando groups of companies. > Due to e-maill communication being insecure, Lando groups of > companies do not guarantee confidentiality, security, accuracy or > performance of the e-mail. Any liability for viruses is excluded > to the fullest extent. > -- Tobias Eichert Developer Gentoo Linux http://www.gentoo.org/~viz/ From owner-linux-xfs@oss.sgi.com Mon Dec 23 09:59:40 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 09:59:45 -0800 (PST) Received: from imf10bis.bellsouth.net (mail110.mail.bellsouth.net [205.152.58.50]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNHxd3v018282 for ; Mon, 23 Dec 2002 09:59:39 -0800 Received: from marsha ([66.156.1.22]) by imf10bis.bellsouth.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with SMTP id <20021223180558.NMQH12552.imf10bis.bellsouth.net@marsha>; Mon, 23 Dec 2002 13:05:58 -0500 Date: Mon, 23 Dec 2002 13:04:08 -0500 From: Greg Freemyer Subject: re: System Lockups To: Matt Schillinger , Mime-Version: 1.0 Organization: The NorcrossGroup X-Mailer: GoldMine [5.70.11111] Content-Type: Text/plain Message-Id: <20021223180558.NMQH12552.imf10bis.bellsouth.net@marsha> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBNHxe3v018283 X-archive-position: 2144 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: freemyer@NorcrossGroup.com Precedence: bulk X-list: linux-xfs My test server started behaving like that a few weeks ago. In my case I became convinced that the CPU had overheated at some point. I ended up putting in a new MB and CPU. Since then all is fine, but I changed from AMD to Intel, so it that does not mean too much. I formed my opinion when kernels I had tested with before had become unreliable. Greg Freemyer >> Just wondering if anyone knows of any reason why a xfs redhat 8.0 would >> just lock up, and leave no log traces in the messages file.. I do not >> really have any data that says that it is XFS related (in fact I doubt >> it). I am just not sure where to go for answers.. I've looked on the web >> and never found anything relevant. From what I can gather, the machine >> dies on its network connection, and all keyboard activity locks up. >> The screen continues to display the last thing that occured before the >> lockup, but there is no additional input/output. From what I can tell, >> it has only happened in periods of inactivity (this is a new development >> machine). >> thanks for any help anyone can offer. And sorry if i'm spamming this >> list.. Any responses, please email me directly, unless it is felt that >> the problem relates to the xfs kernel. >> Thanks, >> -- >> Matt Schillinger >> mschilli@vss.fsi.com From owner-linux-xfs@oss.sgi.com Mon Dec 23 10:59:36 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 10:59:38 -0800 (PST) Received: from banna (fb169203.ot.FreeBit.NE.JP [61.203.169.203]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNIwO3v021317 for ; Mon, 23 Dec 2002 10:59:33 -0800 Received: from C ([192.168.0.4]) by banna (8.9.3+3.2W/3.7W) with SMTP id EAA26512; Tue, 24 Dec 2002 04:02:15 +0900 Message-Id: <200212231902.EAA26512@banna> From: =?iso-2022-jp?B?bW1haWw1NTU1anA=?= To: =?iso-2022-jp?B?NQ==?=@banna.sgi.com Reply-To: mmail5555jp@yahoo.co.jp Date: Tue, 24 Dec 2002 04:01:28 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2145 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mmail5555jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info5555jp@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　001-373-188-8477 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.xx-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.ww-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Mon Dec 23 11:56:31 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 11:56:36 -0800 (PST) Received: from mail.lbsd.net (mail.lbsd.net [196.25.111.97]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNJuS3v022170 for ; Mon, 23 Dec 2002 11:56:30 -0800 Received: from localhost (nkukard@localhost) by mail.lbsd.net (8.12.1/8.12.1) with ESMTP id gBNK0xsU006830; Mon, 23 Dec 2002 22:00:59 +0200 Date: Mon, 23 Dec 2002 22:00:59 +0200 (SAST) From: Nigel Kukard To: Tobias Eichert cc: Subject: Re: XFS + grsecurity + linux kernel 2.4.20 In-Reply-To: <20021223162454.5c9f32c8.tobias@databoogie.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2146 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nkukard@lbsd.net Precedence: bulk X-list: linux-xfs Its only but a pleasure, i'm glad that you like it :) Just let me know if you experience any problems ... etc Regards Nigel On Mon, 23 Dec 2002, Tobias Eichert wrote: > Ah, thanks a lot. I really like your combopatch. :) > > Best Regards, > Tobias > > > On Mon, 23 Dec 2002 16:45:02 +0200 (SAST) > Nigel Kukard wrote: > > > HI Tobias, > > > > The moment XFS 1.2 is relesed and the beta grsecurity > > patch becomes stable we will release the updated > > patches for 2.4.20. > > > > > > Kind Regards > > Nigel Kukard > > LBSD > > > > On Fri, 20 Dec 2002, Tobias Eichert wrote: > > > > > Hello everybody, > > > regarding the latest Linux kernel version, > > > 2.4.20, I considered if someone already > > > has created an XFS - grsecurity combopatch > > > like the one for kernel version 2.4.19 by > > > www.lbsd.net. > > > The problem is that XFS's ACL > > > and grsecurity's internal one won't coexist > > > peacefully by default. :/ > > > > > > Keep up the good work. > > > > > > Best Regards, > > > Tobias Eichert > > > > > > > -- > > > > > > Nigel Kukard (Chief Executive Officer) > > Lando Technologies Africa (Pty) Ltd > > nigel@lando.co.za www.lando.co.za > > Tel: 083 399 5822 Fax: 086 1100036 > > Hoheisen Park Bellville, Cape Town > > National Internet Service Provider > > > > > > The best language to use is the language that was designed for > > what you want to use it for - 1997 > > > > > > ===================================================================== > > > > Disclaimer > > ---------- > > The contents of this message and any attachments are intended > > solely for the addressee's use and may be legally privileged and/or > > confidential information. This message may not be retained, > > distributed, copied or used if you are not he addressee of this > > message. If this message was sent to you in error, please notify > > the sender immediately by reply e-mail and then destroy the message > > and any copies thereof. > > > > Opinions, conclusions and other information in this message may be > > personal to the sender and is not that of Lando Technologies Africa > > or any of it's subsideries, associated companies or principals and > > is therefore not endorsed by any of the Lando groups of companies. > > Due to e-maill communication being insecure, Lando groups of > > companies do not guarantee confidentiality, security, accuracy or > > performance of the e-mail. Any liability for viruses is excluded > > to the fullest extent. > > > > > -- Nigel Kukard (Chief Executive Officer) Lando Technologies Africa (Pty) Ltd nigel@lando.co.za www.lando.co.za Tel: 083 399 5822 Fax: 086 1100036 Hoheisen Park Bellville, Cape Town National Internet Service Provider The best language to use is the language that was designed for what you want to use it for - 1997 ===================================================================== Disclaimer ---------- The contents of this message and any attachments are intended solely for the addressee's use and may be legally privileged and/or confidential information. This message may not be retained, distributed, copied or used if you are not he addressee of this message. If this message was sent to you in error, please notify the sender immediately by reply e-mail and then destroy the message and any copies thereof. Opinions, conclusions and other information in this message may be personal to the sender and is not that of Lando Technologies Africa or any of it's subsideries, associated companies or principals and is therefore not endorsed by any of the Lando groups of companies. Due to e-maill communication being insecure, Lando groups of companies do not guarantee confidentiality, security, accuracy or performance of the e-mail. Any liability for viruses is excluded to the fullest extent. From owner-linux-xfs@oss.sgi.com Mon Dec 23 12:32:45 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 12:32:46 -0800 (PST) Received: from esds.vss.fsi.com (adsl-66-136-174-212.dsl.stlsmo.swbell.net [66.136.174.212]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNKWh3v024095 for ; Mon, 23 Dec 2002 12:32:44 -0800 Received: from mosix (mosix [198.51.26.70]) by esds.vss.fsi.com (8.9.1a/8.9.1) with ESMTP id OAA14403 for ; Mon, 23 Dec 2002 14:37:10 -0600 (CST) Subject: Kernel recompile problems on RH8.0 From: Matt Schillinger To: linux-xfs@oss.sgi.com Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 23 Dec 2002 14:39:32 -0600 Message-Id: <1040675973.24032.26.camel@mosix> Mime-Version: 1.0 X-archive-position: 2147 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mschilli@vss.fsi.com Precedence: bulk X-list: linux-xfs Spamming the list again.. I am unable to compile a kernel in RH8.0. The install was done with a XFS enabled RH8.0 boot cd. Particularly, make modules fails. Is this an XFS issue, or is it something else, such as gcc 3.2? The only things that i need is SCSI support for LUNs higher than 0, and i'd like to try scsimon.. Thanks, -- Matt Schillinger mschilli@vss.fsi.com From owner-linux-xfs@oss.sgi.com Mon Dec 23 13:32:32 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 23 Dec 2002 13:32:36 -0800 (PST) Received: from poptart.bithose.com (ip-204-97-176-41.modem.logical.net [204.97.176.41]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBNLWV3v026882 for ; Mon, 23 Dec 2002 13:32:32 -0800 Received: from poptart.bithose.com (localhost [127.0.0.1]) by poptart.bithose.com (8.12.2/8.12.2) with ESMTP id gBNLb3Wu028912; Mon, 23 Dec 2002 16:37:03 -0500 (EST) Received: from localhost (jakari@localhost) by poptart.bithose.com (8.12.2/8.12.2/Submit) with ESMTP id gBNLb3am028908; Mon, 23 Dec 2002 16:37:03 -0500 (EST) X-Authentication-Warning: poptart.bithose.com: jakari owned process doing -bs Date: Mon, 23 Dec 2002 16:37:03 -0500 (EST) From: Jameel Akari To: Matt Schillinger cc: Subject: Re: Kernel recompile problems on RH8.0 In-Reply-To: <1040675973.24032.26.camel@mosix> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2148 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jakari@bithose.com Precedence: bulk X-list: linux-xfs On 23 Dec 2002, Matt Schillinger wrote: > Spamming the list again.. I am unable to compile a kernel in RH8.0. The > install was done with a XFS enabled RH8.0 boot cd. Particularly, make > modules fails. Is this an XFS issue, or is it something else, such as > gcc 3.2? The only things that i need is SCSI support for LUNs higher > than 0, and i'd like to try scsimon.. I just installed 8.0 with the 1.2pre2 boot CD, and then upgraded to the 1.2pre3 kernels before grabbing the XFS + 2.4.20 CVS source. It built just fine. I didn't make any other changes to the machine before doing it. Where exactly does your fail? Granted the kernel I built was so misconfigured that I couldn't get into the machine (wrong framebuffer mode and something else that broke it before network came up) but that would be entirely my fault. ;) #!/jameel/akari sleep 4800; make clean && make breakfast From owner-linux-xfs@oss.sgi.com Tue Dec 24 08:35:47 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Dec 2002 08:35:53 -0800 (PST) Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBOGZk3v017283 for ; Tue, 24 Dec 2002 08:35:47 -0800 Received: from kanpc.gte.com (localhost [IPv6:::1]) by h132-197-179-27.gte.com (8.12.6/8.12.6) with ESMTP id gBOGeHoc000969 for ; Tue, 24 Dec 2002 11:40:17 -0500 (EST) (envelope-from ak03@kanpc.gte.com) Received: (from ak03@localhost) by kanpc.gte.com (8.12.6/8.12.6/Submit) id gBOGeHEC000964; Tue, 24 Dec 2002 11:40:17 -0500 (EST) Date: Tue, 24 Dec 2002 11:40:16 -0500 From: Alexander Kabaev To: linux-xfs@oss.sgi.com Subject: mrlocks vs. rw_semaphores Message-Id: <20021224114016.133029de.ak03@gte.com> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.8.6claws35 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-archive-position: 2149 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ak03@gte.com Precedence: bulk X-list: linux-xfs Looking through XFS change history, I noticed that several uses of mrlocks in the tree have been replaced with Linux's native rw_semaphores. What was the reason for this? Are rw_semaphores performing significantly better than mrlocks, or is there a subtle difference in their semantics which make rw_semaphores more suitable for the places they are used in now? -- Alexander Kabaev From owner-linux-xfs@oss.sgi.com Tue Dec 24 23:43:08 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 24 Dec 2002 23:43:12 -0800 (PST) Received: from TYO201.gate.nec.co.jp (TYO201.gate.nec.co.jp [202.32.8.214]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBP7h63v024196 for ; Tue, 24 Dec 2002 23:43:07 -0800 Received: from mailgate3.nec.co.jp ([10.7.69.194]) by TYO201.gate.nec.co.jp (8.11.6/3.7W01080315) with ESMTP id gBP7ldw02834 for ; Wed, 25 Dec 2002 16:47:39 +0900 (JST) Received: from mailsv4.nec.co.jp (mailgate52.nec.co.jp [10.7.69.191]) by mailgate3.nec.co.jp (8.11.6/3.7W-MAILGATE-NEC) with ESMTP id gBP7ldi04457 for ; Wed, 25 Dec 2002 16:47:39 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp (secsv2.tnes.nec.co.jp [10.1.101.4]) by mailsv4.nec.co.jp (8.11.6/3.7W-MAILSV4-NEC) with ESMTP id gBP7lcH09955 for ; Wed, 25 Dec 2002 16:47:39 +0900 (JST) Received: from thktnes98740.tnes.nec.co.jp ([10.1.101.4]) by thktnes98740.tnes.nec.co.jp (Post.Office MTA v3.1.2J release 205-101A-J ID# 0-0U10L2S100) with SMTP id AAA103 for ; Wed, 25 Dec 2002 16:47:38 +0900 Received: FROM mailsv.tnes.nec.co.jp BY thktnes98740.tnes.nec.co.jp ; Wed Dec 25 16:47:37 2002 +0900 Received: from rifu.bsd.tnes.nec.co.jp (rifu.bsd.tnes.nec.co.jp [10.1.104.1]) by mailsv.tnes.nec.co.jp (8.11.6/3.7W01031510) with ESMTP id gBP7lbb86317 for ; Wed, 25 Dec 2002 16:47:37 +0900 (JST) Received: from localhost (IDENT:masano@noshiro.bsd.tnes.nec.co.jp [10.1.104.24]) by rifu.bsd.tnes.nec.co.jp (8.11.6/3.7W/BSD-TNES-MX01) with ESMTP id gBP7lbI19308 for ; Wed, 25 Dec 2002 16:47:37 +0900 To: linux-xfs@oss.sgi.com Subject: xfsprogs man page X-Mailer: Mew version 1.94.2 on XEmacs 21.4 (Informed Management) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20021225164737V.masano@tnes.nec.co.jp> Date: Wed, 25 Dec 2002 16:47:37 +0900 (JST) From: ASANO Masahiro X-Dispatcher: imput version 20000228(IM140) Lines: 14 X-archive-position: 2150 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: masano@tnes.nec.co.jp Precedence: bulk X-list: linux-xfs Hi, XFS_IOC_[GS]ETBIOSIZE were removed from cvs kernel source at 2002/02/26. So I guess xfs(5) man page should be reflected. Current xfs(5) says: > XFS_IOC_GETBIOSIZE > This command gets information about the preferred ... > XFS_IOC_SETBIOSIZE > This command the preferred buffered I/O size used ^^^^ sets information about -- Masano From owner-linux-xfs@oss.sgi.com Wed Dec 25 02:27:40 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Dec 2002 02:27:46 -0800 (PST) Received: from banna (f113.ag233.FreeBit.NE.JP [219.109.233.113]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBPARL3v028565 for ; Wed, 25 Dec 2002 02:27:29 -0800 Received: from C ([192.168.0.4]) by banna (8.9.3+3.2W/3.7W) with SMTP id TAA11064; Wed, 25 Dec 2002 19:31:43 +0900 Message-Id: <200212251031.TAA11064@banna> From: =?iso-2022-jp?B?bW1haWw2NjY2anA=?= To: =?iso-2022-jp?B?NTU1?=@banna.sgi.com Reply-To: mmail6666jp@yahoo.co.jp Date: Wed, 25 Dec 2002 19:29:32 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2151 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mmail6666jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info5555jp@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　001-373-188-8477 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.xx-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.ww-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Wed Dec 25 16:45:40 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Wed, 25 Dec 2002 16:45:46 -0800 (PST) Received: from mailproxy1.netcologne.de (mailproxy1.netcologne.de [194.8.194.222]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBQ0jc3v004111 for ; Wed, 25 Dec 2002 16:45:39 -0800 Received: from jungle (xdsl-195-14-205-88.netcologne.de [195.14.205.88]) by mailproxy1.netcologne.de (Postfix) with ESMTP id 3B45AC7365; Thu, 26 Dec 2002 01:50:14 +0100 (MET) Content-Type: text/plain; charset="iso-8859-15" From: =?iso-8859-15?q?J=F6rg=20Prante?= Reply-To: joergprante@netcologne.de Subject: 2.4.21pre2 + preempt + xfs BUG? Date: Thu, 26 Dec 2002 01:49:11 +0100 User-Agent: KMail/1.4.3 MIME-Version: 1.0 To: linux-kernel@vger.kernel.org Cc: linux-xfs@oss.sgi.com, rml@tech9.net Message-Id: <200212260149.11718.joergprante@netcologne.de> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by oss.sgi.com id gBQ0je3v004112 X-archive-position: 2152 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: joergprante@netcologne.de Precedence: bulk X-list: linux-xfs Hello, in my 2.4.21-pre2 based -jp15 kernel patch set I can't boot with XFS and preemptive kernel enabled. I use: - 2.4.21pre2 - preempt 2.4.20-ac1 - XFS snapshot 2.4.20-2002-11-29_01:21_UTC - and a lot of other patches, see http://infolinux.de/jp15 The kernel boots ok for a long time, but when it enters the init process run level 5, it throws a kernel BUG in the O(1) scheduler code in schedule() at the first statement when it checks for interrupt code. I guess it performs a sync on the XFS root file system for the first time. You can find a ksymoops message below. Here are my observations after several changes in the configuration: - if preemptive kernel is disabled, XFS can boot successfully. So, the bug is triggered by the preemptive kernel patch. - with preemptive kernel enabled and reiserfs, booting is no problem. So, the bug is specific to the combination XFS and preempt. Is it just me with this BUG or can it be reproduced? A release of the patch set is available at http://infolinux.de/jp15/patchset-2.4.21-pre2-jp15.tar.bz2 Best regards, Jrg -----------------------snip----------------------- kernel BUG at sched.c:811! invalid operand: 0000 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010202 eax: 00000001 ebx: c1a42000 ecx: 00000001 edx: 00000001 esi: c051cac0 edi: fffffffe ebp: c1a43e50 esp: c1a43e34 ds: 0018 es: 0018 ss: 0018 Process init (pid: 1, stackpage=c1a43000) Stack: c01204b0 c1a0a580 c0534a0c c0534a0c c1a42000 c051cac0 fffffffe c1a43e5c c0116694 c0525200 00000046 c0120296 00000001 00000001 c01200dd c051cac0 c1a42000 c0518900 00000000 c04a5df0 c010a8ff 00000000 c1a43eac c04a5df0 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 2b 03 bf 72 43 c0 e9 23 fd ff ff 90 89 f6 55 89 e5 53 >>EIP; c0116660 <===== >>ebx; c1a42000 <_end+14e4170/16a21d0> >>esi; c051cac0 >>edi; fffffffe >>ebp; c1a43e50 <_end+14e5fc0/16a21d0> >>esp; c1a43e34 <_end+14e5fa4/16a21d0> Trace; c01204b0 <__run_task_queue+60/80> Trace; c0116694 Trace; c0120296 Trace; c01200dd Trace; c010a8ff Trace; c010d153 Trace; c021f614 Trace; c021c1db Trace; c0116694 Trace; c0130c2d Trace; c021f479 Trace; c0235cec Trace; c014dccf Trace; c014976b Trace; c014989f Trace; c01090cf Code; c0116660 00000000 <_EIP>: Code; c0116660 <===== 0: 0f 0b ud2a <===== Code; c0116662 2: 2b 03 sub (%ebx),%eax Code; c0116664 4: bf 72 43 c0 e9 mov $0xe9c04372,%edi Code; c0116669 9: 23 fd and %ebp,%edi Code; c011666b b: ff (bad) Code; c011666c c: ff 90 89 f6 55 89 call *0x8955f689(%eax) Code; c0116672 12: e5 53 in $0x53,%eax <0>Kernel panic: Aiee, killing interrupt handler! From owner-linux-xfs@oss.sgi.com Thu Dec 26 07:55:50 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Dec 2002 07:55:55 -0800 (PST) Received: from netmail.amdocs.com (netmail.amdocs.com [194.90.254.138]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBQFtm3v023358 for ; Thu, 26 Dec 2002 07:55:50 -0800 Received: from amdocs.com (soint4.amdocs.com [199.203.109.226]) by netmail.amdocs.com (8.12.4/8.12.4) with ESMTP id gBQFxSvK030151 for ; Thu, 26 Dec 2002 17:59:28 +0200 Received: from rgmail4.corp.amdocs.com (localhost [127.0.0.1]) by amdocs.com (8.9.3+Sun/8.9.3) with ESMTP id RAA14862 for ; Thu, 26 Dec 2002 17:59:44 +0200 (IST) Received: by rgmail4.corp.amdocs.com with Internet Mail Service (5.5.2653.19) id ; Thu, 26 Dec 2002 17:59:29 +0200 Message-ID: <759D44F33CA3D41187E300508BAFA7A5057E31F7@mailsrv7.corp.amdocs.com> From: Doron Rabia To: "'linux-xfs@oss.sgi.com'" Subject: XFS 1.2 for RH 8.0 installation iso. Date: Thu, 26 Dec 2002 17:59:27 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary" X-archive-position: 2153 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: DoronR@Amdocs.com Precedence: bulk X-list: linux-xfs --=_IS_MIME_Boundary Content-Type: text/plain; charset="iso-8859-1" Hi, I noticed on the mail archive that an installer for RH 8.0 (XFS 1.2-pre4) exists, however i'm not able to find it on your site. Can you help and tell me where can i find it? Thanks and happy holidays, Doron Rabia, --=_IS_MIME_Boundary Content-Type: text/plain;charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------------- The information contained in this message is proprietary of Amdocs, protected from disclosure, and may be privileged. The information is intended to be conveyed only to the designated recipient(s) of the message. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, use, distribution or copying of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. Thank you. ------------------------------------------------------------------------------------- --=_IS_MIME_Boundary-- From owner-linux-xfs@oss.sgi.com Thu Dec 26 08:34:20 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Dec 2002 08:34:25 -0800 (PST) Received: from localhost.localdomain (amoa.org [207.207.51.226]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBQGYJ3v023977 for ; Thu, 26 Dec 2002 08:34:19 -0800 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.5/8.12.5) with ESMTP id gBQGcaDZ002171; Thu, 26 Dec 2002 10:38:46 -0600 Received: (from ctooley@localhost) by localhost.localdomain (8.12.5/8.12.5/Submit) id gBQGc6Jx001908; Thu, 26 Dec 2002 10:38:06 -0600 X-Authentication-Warning: localhost.localdomain: ctooley set sender to ctooley@amoa.org using -f Subject: Re: XFS 1.2 for RH 8.0 installation iso. From: Chris Tooley To: Doron Rabia Cc: "'linux-xfs@oss.sgi.com'" In-Reply-To: <759D44F33CA3D41187E300508BAFA7A5057E31F7@mailsrv7.corp.amdocs.com> References: <759D44F33CA3D41187E300508BAFA7A5057E31F7@mailsrv7.corp.amdocs.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 (1.0.8-10) Date: 26 Dec 2002 10:38:05 -0600 Message-Id: <1040920685.1881.3.camel@itspec.amoa.org> Mime-Version: 1.0 X-archive-position: 2154 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: ctooley@amoa.org Precedence: bulk X-list: linux-xfs Use the XFS 1.2a1 installer you must. Trivial to update the kernel aftwards it is. Archives are your friends. :) Chris On Thu, 2002-12-26 at 09:59, Doron Rabia wrote: > Hi, > > I noticed on the mail archive that an installer for RH 8.0 (XFS 1.2-pre4) > exists, however i'm not able to find it on your site. > Can you help and tell me where can i find it? > > Thanks and happy holidays, > > Doron Rabia, > > ---- > > ------------------------------------------------------------------------------------- > > The information contained in this message is proprietary of Amdocs, > > protected from disclosure, and may be privileged. > > The information is intended to be conveyed only to the designated recipient(s) > > of the message. If the reader of this message is not the intended recipient, > > you are hereby notified that any dissemination, use, distribution or copying of > > this communication is strictly prohibited and may be unlawful. > > If you have received this communication in error, please notify us immediately > > by replying to the message and deleting it from your computer. > > Thank you. > > > ------------------------------------------------------------------------------------- From owner-linux-xfs@oss.sgi.com Thu Dec 26 13:58:35 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Thu, 26 Dec 2002 13:58:41 -0800 (PST) Received: from rj.sgi.com (rj.sgi.com [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBQLwY3v026429 for ; Thu, 26 Dec 2002 13:58:35 -0800 Received: from larry.melbourne.sgi.com (larry.melbourne.sgi.com [134.14.52.130]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with SMTP id gBQK3LG8010013 for ; Thu, 26 Dec 2002 12:03:21 -0800 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 JAA20641; Fri, 27 Dec 2002 09:01:58 +1100 Received: from frodo.melbourne.sgi.com (root@frodo.melbourne.sgi.com [134.14.55.153]) by wobbly.melbourne.sgi.com (SGI-8.9.3/8.9.3) with ESMTP id JAA45432; Fri, 27 Dec 2002 09:01:57 +1100 (AEDT) Received: from frodo.melbourne.sgi.com (nathans@localhost [127.0.0.1]) by frodo.melbourne.sgi.com (8.12.6/8.12.6/Debian-8) with ESMTP id gBQM14Q5001806; Fri, 27 Dec 2002 09:01:04 +1100 Received: (from nathans@localhost) by frodo.melbourne.sgi.com (8.12.6/8.12.6/Debian-8) id gBQM12K9001804; Fri, 27 Dec 2002 09:01:02 +1100 Date: Fri, 27 Dec 2002 09:01:02 +1100 From: Nathan Scott To: ASANO Masahiro Cc: linux-xfs@oss.sgi.com Subject: Re: xfsprogs man page Message-ID: <20021226220102.GA1773@frodo.melbourne.sgi.com> References: <20021225164737V.masano@tnes.nec.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021225164737V.masano@tnes.nec.co.jp> User-Agent: Mutt/1.4i X-archive-position: 2155 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@sgi.com Precedence: bulk X-list: linux-xfs On Wed, Dec 25, 2002 at 04:47:37PM +0900, ASANO Masahiro wrote: > Hi, > > XFS_IOC_[GS]ETBIOSIZE were removed from cvs kernel source at > 2002/02/26. So I guess xfs(5) man page should be reflected. > fixed now, thanks. -- Nathan From owner-linux-xfs@oss.sgi.com Fri Dec 27 18:19:36 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Fri, 27 Dec 2002 18:19:42 -0800 (PST) Received: from apan (f238.ag238.FreeBit.NE.JP [219.109.238.238]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBS2IQ3v007564 for ; Fri, 27 Dec 2002 18:19:17 -0800 Received: from D ([192.168.0.2]) by apan (8.9.3+3.2W/3.7W) with SMTP id LAA07940; Sat, 28 Dec 2002 11:20:42 +0900 Message-Id: <200212280220.LAA07940@apan> From: =?iso-2022-jp?B?bW1haWw3Nzc3anA=?= To: =?iso-2022-jp?B?NA==?=@apan.sgi.com Reply-To: mmail7777jp@yahoo.co.jp Date: Sat, 28 Dec 2002 11:19:58 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoSSw4KyEqTiI+cEpzISobKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2156 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mmail7777jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs <送信者> 電子メール広告社 今後、広告をご希望されない方はここへ info2222jp@yahoo.co.jp 必ず本文にあなたのメールアドレスのみをお書き下さい =============================================================== 当社の強大な広告力を活かしませんか！ 配信業務からホームページ製作まで格安にてお受け致します。 下記ＦＡＸにてお申し込み下さい。 =============================================================== 〒104-0061 東京都中央区銀座8-19-3 第2ウイングビル　3F メールマガジン発行 TEL　001-373-188-8477 FAX　03-3544-6218　　 =============================================================== 問題商品ばかり集めました。消される恐れがありますので お申込みはお早めに！ ================================================================= ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 裏ビデオ販売・特殊ダッチワイフ・ＳＭクラブ 　　 ＡＶ男優募集・援助交際・ＳＥＸフレンド・アダルトグッズなど ★　アダルト関連の情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 　　　http://www.xx-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ 　　開運グッズ・極秘情報誌・防犯グッズ・金儲け情報など　 　　　　　　　　　★　その他情報満載　★ ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 　　お申込み・ご注文・商品詳細等は　 　　　　　下記ＵＲＬをクリックしてご覧下さい。 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ ↓　　　　↓　　　　↓　 http://www.ww-koukoku.com/ ☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆―――☆ From owner-linux-xfs@oss.sgi.com Sat Dec 28 02:05:15 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Dec 2002 02:05:24 -0800 (PST) Received: from ente.berdmann.de (frnk-d514e17a.dsl.mediaWays.net [213.20.225.122]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBSA5D3v010433 for ; Sat, 28 Dec 2002 02:05:15 -0800 Received: from indigo-3.berdmann.de ([192.168.5.2] helo=berdmann.de) by ente.berdmann.de with esmtp (Exim 3.35 #1) id 18SDuq-0000Vc-00 for linux-xfs@oss.sgi.com; Sat, 28 Dec 2002 11:10:00 +0100 Message-ID: <3E0D7877.5010806@berdmann.de> Date: Sat, 28 Dec 2002 11:09:59 +0100 From: Bernhard Erdmann User-Agent: Mozilla/5.0 (X11; U; IRIX64 IP28; en-US; rv:1.3b) Gecko/20021227 X-Accept-Language: de, en, fr MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: nfsd crashes regularly (Oops) Content-Type: multipart/mixed; boundary="------------080105060808060603020901" X-archive-position: 2157 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: be@berdmann.de Precedence: bulk X-list: linux-xfs This is a multi-part message in MIME format. --------------080105060808060603020901 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, I have a box running kernel 2.4.18 (SGI XFS 1.1). Say twice a week the NFS server crashes with Oops, i.e. NFS service is blocked but the box is still running a mail server and you can log in. $ gcc --version egcs-2.91.66 /var/log/messages of this week was fed to ksymoops and the result is attached. --------------080105060808060603020901 Content-Type: text/plain; name="nfsd.oops.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="nfsd.oops.txt" ksymoops 2.4.8 on i586 2.4.18-xfs-1.1. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.18-xfs-1.1 (specified) -m /boot/System.map (specified) Dec 25 02:54:50 ente kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Dec 25 02:54:50 ente kernel: 00000000 Dec 25 02:54:50 ente kernel: *pde = 00000000 Dec 25 02:54:50 ente kernel: Oops: 0000 Dec 25 02:54:50 ente kernel: CPU: 0 Dec 25 02:54:50 ente kernel: EIP: 0010:[<00000000>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 Dec 25 02:54:50 ente kernel: EFLAGS: 00010282 Dec 25 02:54:50 ente kernel: eax: 00000000 ebx: ced5ace0 ecx: 00000000 edx: c0325ba0 Dec 25 02:54:50 ente kernel: esi: ced5ade0 edi: ced5ace0 ebp: ced5ace0 esp: cd017ec4 Dec 25 02:54:50 ente kernel: ds: 0018 es: 0018 ss: 0018 Dec 25 02:54:50 ente kernel: Process nfsd (pid: 679, stackpage=cd017000) Dec 25 02:54:50 ente kernel: Stack: c0163700 cc1469c0 ced5ade0 cd0c6c04 cfd9b800 c0163b16 ced5ace0 cd0c6c04 Dec 25 02:54:50 ente kernel: 00000002 cd04e800 11270000 c52dc520 cfd9ba10 00000002 c0163e29 cfd9b800 Dec 25 02:54:50 ente kernel: cd0c6c14 00000002 00000001 00000001 cd0c6c04 cd0c6a90 cd0c6c94 cd0c6c00 Dec 25 02:54:50 ente kernel: Call Trace: [nfsd_findparent+56/212] [find_fh_dentry+502/776] [fh_verify+513/1000] [nfsd3_proc_getattr+149/160] [nfsd_dispatch+211/416] Dec 25 02:54:50 ente kernel: Code: Bad EIP value. >>EIP; 00000000 Before first symbol >>ebx; ced5ace0 <_end+ea0c57c/1054289c> >>edx; c0325ba0 >>esi; ced5ade0 <_end+ea0c67c/1054289c> >>edi; ced5ace0 <_end+ea0c57c/1054289c> >>ebp; ced5ace0 <_end+ea0c57c/1054289c> >>esp; cd017ec4 <_end+ccc9760/1054289c> Dec 26 20:39:18 ente kernel: SGI XFS with no debug enabled Dec 26 20:39:18 ente kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html Dec 28 02:51:28 ente kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000 Dec 28 02:51:28 ente kernel: 00000000 Dec 28 02:51:28 ente kernel: *pde = 00000000 Dec 28 02:51:28 ente kernel: Oops: 0000 Dec 28 02:51:28 ente kernel: CPU: 0 Dec 28 02:51:29 ente kernel: EIP: 0010:[<00000000>] Not tainted Dec 28 02:51:29 ente kernel: EFLAGS: 00010282 Dec 28 02:51:29 ente kernel: eax: 00000000 ebx: c5cf6420 ecx: 00000000 edx: c0325ba0 Dec 28 02:51:29 ente kernel: esi: cd89e820 edi: c5cf6420 ebp: c5cf6420 esp: cd327ec4 Dec 28 02:51:29 ente kernel: ds: 0018 es: 0018 ss: 0018 Dec 28 02:51:29 ente kernel: Process nfsd (pid: 667, stackpage=cd327000) Dec 28 02:51:29 ente kernel: Stack: c0163700 caf12060 cd89e820 cd3f2204 cfd82800 c0163b16 c5cf6420 cd3f2204 Dec 28 02:51:29 ente kernel: 00000002 cd34f800 11270000 00000246 cfd82a10 00000002 c0163e29 cfd82800 Dec 28 02:51:29 ente kernel: cd3f2214 00000002 00000001 00000001 cd3f2204 cd3f2090 cd3f2294 cd3f2200 Dec 28 02:51:29 ente kernel: Call Trace: [nfsd_findparent+56/212] [find_fh_dentry+502/776] [fh_verify+513/1000] [nfsd3_proc_getattr+149/160] [nfsd_dispatch+211/416] Dec 28 02:51:29 ente kernel: Code: Bad EIP value. >>EIP; 00000000 Before first symbol >>ebx; c5cf6420 <_end+59a7cbc/1054289c> >>edx; c0325ba0 >>esi; cd89e820 <_end+d5500bc/1054289c> >>edi; c5cf6420 <_end+59a7cbc/1054289c> >>ebp; c5cf6420 <_end+59a7cbc/1054289c> >>esp; cd327ec4 <_end+cfd9760/1054289c> Dec 28 10:03:07 ente kernel: SGI XFS with no debug enabled Dec 28 10:03:08 ente kernel: 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html --------------080105060808060603020901-- From owner-linux-xfs@oss.sgi.com Sat Dec 28 03:22:32 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Dec 2002 03:22:37 -0800 (PST) Received: from stout.sif.it (IDENT:ketPd+ztbd0g9UZ5p8BqCzozwmC72Ia9@ppp-172-138.28-151.libero.it [151.28.138.172]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBSBMS3v013698 for ; Sat, 28 Dec 2002 03:22:30 -0800 Received: from stout.sif.it (localhost.localdomain [127.0.0.1]) by stout.sif.it (8.12.5/8.12.5) with ESMTP id gBSBRPCG017514; Sat, 28 Dec 2002 12:27:26 +0100 Received: from localhost (matteo@localhost) by stout.sif.it (8.12.5/8.12.5/Submit) with ESMTP id gBSBRMdh017480; Sat, 28 Dec 2002 12:27:23 +0100 X-Authentication-Warning: stout.sif.it: matteo owned process doing -bs Date: Sat, 28 Dec 2002 12:27:22 +0100 (CET) From: Matteo Centonza To: Bernhard Erdmann cc: linux-xfs@oss.sgi.com Subject: Re: nfsd crashes regularly (Oops) In-Reply-To: <3E0D7877.5010806@berdmann.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2158 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: matteo@sif.it Precedence: bulk X-list: linux-xfs Hi Bernhard, > I have a box running kernel 2.4.18 (SGI XFS 1.1). Say twice a week the > NFS server crashes with Oops, i.e. NFS service is blocked but the box is > still running a mail server and you can log in. if xfsdump was running, probably it's a known problem: http://marc.theaimsgroup.com/?l=linux-xfs&m=100339196420164&w=2 solved in the current CVS or 1.2 prereleases: http://marc.theaimsgroup.com/?l=linux-xfs&m=102036006319547&w=2 Ciao, -m From owner-linux-xfs@oss.sgi.com Sat Dec 28 06:02:26 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Dec 2002 06:02:33 -0800 (PST) Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBSE2P3v015546 for ; Sat, 28 Dec 2002 06:02:26 -0800 Received: from fwd05.sul.t-online.de by mailout05.sul.t-online.com with smtp id 18SHcR-0004Ox-04; Sat, 28 Dec 2002 15:07:15 +0100 Received: from puariko.homeip.net (520039812576-0001@[217.231.221.198]) by fmrl05.sul.t-online.com with esmtp id 18SHcN-1QnhDsC; Sat, 28 Dec 2002 15:07:11 +0100 Received: (from thimm@localhost) by bonzo.nirvana (8.12.5/8.12.5/Submit) id gBSE754Z017942; Sat, 28 Dec 2002 15:07:05 +0100 Date: Sat, 28 Dec 2002 15:07:05 +0100 From: Axel Thimm To: linux-xfs Cc: Florin Andrei Subject: kernel-2.4.18-19.8.0at6 and 1.2pre4 Message-ID: <20021228140705.GA17731@bonzo.nirvana> References: <1040334285.4524.107.camel@rose.americas.sgi.com> <1040344583.15731.162.camel@stantz.corp.sgi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <1040344583.15731.162.camel@stantz.corp.sgi.com> User-Agent: Mutt/1.4i X-Sender: 520039812576-0001@t-dialin.net X-archive-position: 2159 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: Axel.Thimm@physik.fu-berlin.de Precedence: bulk X-list: linux-xfs --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have adjusted the XFS patches from 1.2pre4 to the latest release RedHat k= ernel for RedHat 8.0 (linux-2.4.19-kdb.patch and linux-2.4.19-quotabackport.patch had to be tweaked a litte for redhat's 19.8.0 kernel release). =20 You can find them under http://atrpms.physik.fu-berlin.de/kernel/. Note that there are also some additional patches, which you can easily remove from the src.rpm. o base kernel sources: Taken from latest redhat errata (2.4.18-19.8.0) o XFS: merged patches found in 1.2pre4 o i2c-2.6.5 and lm_sensors-2.6.5. You should also get the updated userland tools. o 3ware 1.02.00.027 kernel driver for Escalade 7xxx series. Try to keep in sync with your firmware and userland tools. o v4l2-api (backported from http://bytesex.org/patches/2.4/11-v4l2-api-2.4.20-pre11.diff.gz) On Thu, Dec 19, 2002 at 04:36:22PM -0800, Florin Andrei wrote: > On Thu, 2002-12-19 at 13:44, Russell Cattelan wrote: > > Ok so after fat fingering the SPEC file and using a really old > > 1.2 patch for the RedHat kernel builds=20 > > Everything has be rebuilt and has been pushed out to oss. > Now, i don't want to be a nitpicker, but is it possible to build these > things based on the latest RH kernel update? (2.4.18-18.8.0) --=20 Axel.Thimm@physik.fu-berlin.de --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+DbAJQBVS1GOamfERAiybAJ9TaTyE3FHUk5MmiUL44Y5Pncj/vQCeJOGb MQQe/VMkkxhmg2mF8JNaz5I= =+aME -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-linux-xfs@oss.sgi.com Sat Dec 28 13:26:41 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sat, 28 Dec 2002 13:26:46 -0800 (PST) Received: from banna (pl462.nas926.o-tokyo.nttpc.ne.jp [210.165.238.206]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBSLQ63v020540 for ; Sat, 28 Dec 2002 13:26:25 -0800 Received: from 5-C ([192.168.0.2]) by banna (8.9.3+3.2W/3.7W) with SMTP id GAA04605; Sun, 29 Dec 2002 06:31:59 +0900 Message-Id: <200212282131.GAA04605@banna> From: =?iso-2022-jp?B?bWFpbDQ0NGpw?= To: =?iso-2022-jp?B?NQ==?=@banna.sgi.com Reply-To: mail4444jp@yahoo.co.jp Date: Sun, 29 Dec 2002 06:28:54 +0900 Subject: =?iso-2022-jp?B?GyRCTCQ+NUJ6OS05cCIoJWEhPCVrJEckKjZiISkbKEo=?= Content-Type: text/plain Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-archive-position: 2160 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: mail4444jp@yahoo.co.jp Precedence: bulk X-list: linux-xfs ＜送信者＞モモコクラブ ☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆ 　　　　　　過去最高換金率　１Ｐで３円！ 　　　１回のメールの受信で３円が貰えちゃう！ 　サイドビジネス？　副収入？　もう貴方はメールまかせ★ ☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆―☆ この企画に参加希望の方は下記のメールアドレスに貴方のメールアドレスを返信してください。 　　　　　　momoko_club2003@yahoo.co.jp ◆◇◆◇◆◇◆◇◆新 企 画◆◇◆◇◆◇◆◇◆ 日本最大のチャットルームがＯＰＥＮしました。（もちろん無料） 様々な出会いを求めるあなた是非ご利用下さい。 http://www.gg-koukoku.com/index.html ◆◇◆◇◆◇◆◇◆◆◇◆◇◆◇◆◇◆◆◇◆◇◆ メールの受信を希望しない方は下記まで返信下さい。 http://koukoku.dynup.net/kaijo/ 住　所　東京都渋谷区宇田川町1-10-13-203 ＴＥＬ　090-1214-7883 モモコの部屋 From owner-linux-xfs@oss.sgi.com Sun Dec 29 04:48:49 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Sun, 29 Dec 2002 04:48:55 -0800 (PST) Received: from fukuro.momonga-linux.org (flt-168-069.kyoto-inet.or.jp [163.208.168.69]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBTCmm3v005633 for ; Sun, 29 Dec 2002 04:48:49 -0800 Received: from fukuro.momonga-linux.org.localdomain (fukuro.momonga-linux.org [127.0.0.1]) by fukuro.momonga-linux.org (Postfix) with ESMTP id CBB1D34657CE for ; Sun, 29 Dec 2002 21:53:43 +0900 (JST) Date: Sun, 29 Dec 2002 21:53:43 +0900 Message-ID: From: Kazuhiko To: linux-xfs@oss.sgi.com Subject: version typo in '2002-12-18 02:00 UTC' patch User-Agent: Wanderlust/2.8.1 (Something) XEmacs/21.4 (Military Intelligence) X-Face: )]%ppBP=:^Yt>BSd3H"[I5jK[Ro\RHx2%QcY-?L1my]*SHg(.'lYS*+4Xc'[R/.JI,Cn*}v u8.|5W!$i,_t836],oi^"+Dk,FaeeSGRH^CP9n+Zqzwj'l4#t9z,rmU-&U(p\(8#_s'D; Mon, 30 Dec 2002 13:04:51 -0800 Received: from attbi.com (12-253-73-46.client.attbi.com[12.253.73.46]) by sccrmhc01.attbi.com (sccrmhc01) with SMTP id <20021229041721001003m8qie>; Sun, 29 Dec 2002 04:17:21 +0000 Message-ID: <3E0E7798.70601@attbi.com> Date: Sat, 28 Dec 2002 21:18:32 -0700 From: "D. Stimits" Reply-To: stimits@attbi.com User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021018 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "XFS: linux-xfs@oss.sgi.com" Subject: spam from banna.sgi.com via yahoo.co.jp Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-archive-position: 2162 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: stimits@attbi.com Precedence: bulk X-list: linux-xfs I can't read Japanese, so maybe I'm jumping the gun here. But is there any way that email being sent to this list from pattern "mail[0-9][0-9][0-9][0-9]jp@yahoo.co.jp" can be squashed? It certainly looks (from the html URL's) like it is spam. For now I'll just killfile all yahoo.co.jp and banna.sgi.com, but it seems like this isn't quite the correct approach. D. Stimits, stimits AT attbi DOT com From owner-linux-xfs@oss.sgi.com Mon Dec 30 13:20:24 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 13:20:30 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBULKN3v028569 for ; Mon, 30 Dec 2002 13:20:24 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBUJPSG8008590 for ; Mon, 30 Dec 2002 11:25:29 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id PAA37895; Mon, 30 Dec 2002 15:25:20 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id PAA03117; Mon, 30 Dec 2002 15:25:20 -0600 (CST) Received: from rose.americas.sgi.com (localhost [127.0.0.1]) by rose.americas.sgi.com (8.12.6/8.12.5) with ESMTP id gBULR3kx003116; Mon, 30 Dec 2002 15:27:03 -0600 Received: (from cattelan@localhost) by rose.americas.sgi.com (8.12.6/8.12.6/Submit) id gBULR2ZT003114; Mon, 30 Dec 2002 15:27:02 -0600 X-Authentication-Warning: rose.americas.sgi.com: cattelan set sender to cattelan@thebarn.com using -f Subject: Re: spam from banna.sgi.com via yahoo.co.jp From: Russell Cattelan To: stimits@attbi.com Cc: "XFS: ""linux-xfs@oss.sgi.com" In-Reply-To: <3E0E7798.70601@attbi.com> References: <3E0E7798.70601@attbi.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1041283621.2520.4.camel@rose.americas.sgi.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 (1.2.0-3) Date: 30 Dec 2002 15:27:02 -0600 X-archive-position: 2163 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs Ya that spam was pissing me off. I added razor filtering to spamassassin on oss yesterday. I think that will catch those messages? but we'll have to wait and see. On Sat, 2002-12-28 at 22:18, D. Stimits wrote: > I can't read Japanese, so maybe I'm jumping the gun here. But is there > any way that email being sent to this list from pattern > "mail[0-9][0-9][0-9][0-9]jp@yahoo.co.jp" can be squashed? It certainly > looks (from the html URL's) like it is spam. For now I'll just killfile > all yahoo.co.jp and banna.sgi.com, but it seems like this isn't quite > the correct approach. > > D. Stimits, stimits AT attbi DOT com -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Mon Dec 30 15:01:13 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 15:01:21 -0800 (PST) Received: from shade.globe.cz (prahac-5-108.dialup.vol.cz [212.20.105.240]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBUN1A3v029542 for ; Mon, 30 Dec 2002 15:01:12 -0800 Received: (qmail 10334 invoked by uid 1000); 30 Dec 2002 23:06:05 -0000 To: Subject: Re: spam from banna.sgi.com via yahoo.co.jp References: <3E0E7798.70601@attbi.com> <1041283621.2520.4.camel@rose.americas.sgi.com> From: Ondrej Sury In-Reply-To: <1041283621.2520.4.camel@rose.americas.sgi.com> (Russell Cattelan's message of "30 Dec 2002 15:27:02 -0600") Date: Tue, 31 Dec 2002 00:06:05 +0100 Message-ID: <871y3zt8de.fsf@globe.cz> Lines: 22 User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-archive-position: 2164 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sury.ondrej@globe.cz Precedence: bulk X-list: linux-xfs Russell Cattelan writes: Since I have SA on my mail and I didn't received any of those emails you are talking about I think it will work... ;-) O. > Ya that spam was pissing me off. > I added razor filtering to spamassassin on oss yesterday. > I think that will catch those messages? but we'll have to wait and see. > > On Sat, 2002-12-28 at 22:18, D. Stimits wrote: >> I can't read Japanese, so maybe I'm jumping the gun here. But is there >> any way that email being sent to this list from pattern >> "mail[0-9][0-9][0-9][0-9]jp@yahoo.co.jp" can be squashed? It certainly >> looks (from the html URL's) like it is spam. For now I'll just killfile >> all yahoo.co.jp and banna.sgi.com, but it seems like this isn't quite >> the correct approach. -- Ondrej Sury - CIO Globe Internet s.r.o. http://globe.cz/ Tel: +420(2)35365000 Fax: +420(2)35365009 Planickova 1, 162 00 Praha 6 From owner-linux-xfs@oss.sgi.com Mon Dec 30 18:49:23 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 18:49:31 -0800 (PST) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.58.33]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV2nM3v031232 for ; Mon, 30 Dec 2002 18:49:22 -0800 Received: from Shiva (shiva [192.168.3.20]) by ishtar.tlinx.org (8.12.6/8.12.2/SuSE Linux 0.6) with ESMTP id gBV2sLxO011590 for ; Mon, 30 Dec 2002 18:54:21 -0800 From: "LA Walsh" To: Subject: xfsdump... Date: Mon, 30 Dec 2002 18:54:21 -0800 Message-ID: <000801c2b077$eb2b8590$1403a8c0@sc.tlinx.org> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-archive-position: 2165 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: law@tlinx.org Precedence: bulk X-list: linux-xfs I got the new version of the xfs patch. Seems an older version xfsdump can have nasty consequences (I assume I need a newer xfsdump...?)... xfsdump: using file dump (drive_simple) strategy xfsdump: version 2.1.3 (dump format 3.0) - Running single-threaded xfsdump: level 0 dump of ishtar:/ xfsdump: dump date: Mon Dec 30 18:47:46 2002 xfsdump: session id: 1e34cbd9-9335-4ef4-b33f-bfcbeaaa22b3 xfsdump: session label: "root" xfsdump: ino map phase 1: skipping (no subtrees specified) xfsdump: ino map phase 2: constructing initial dump list xfsdump: WARNING: failed to get bulkstat information for inode 1590 xfsdump: syssgi( SGI_FS_BULKSTAT ) on fsroot failed: Input/output error ishtar:root/bin# top bash: top: command not found ishtar:root/bin# ls bash: /bin/ls: Input/output error ishtar:root/bin# /bin/reboot bash: /bin/reboot: Input/output error ---- Good thing I'm using a journalling file system....:-/ -l From owner-linux-xfs@oss.sgi.com Mon Dec 30 19:26:59 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 19:27:02 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV3Qx3v032224 for ; Mon, 30 Dec 2002 19:26:59 -0800 Received: from localhost (localhost [127.0.0.1]) by tapu.f00f.org (Postfix) with ESMTP id 4AF0A2021CE; Mon, 30 Dec 2002 19:32:03 -0800 (PST) Received: by tapu.f00f.org (Postfix, from userid 1000) id BFDBD202211; Mon, 30 Dec 2002 19:32:02 -0800 (PST) Date: Mon, 30 Dec 2002 19:32:02 -0800 From: Chris Wedgwood To: LA Walsh Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump... Message-ID: <20021231033202.GA17409@tapu.f00f.org> References: <000801c2b077$eb2b8590$1403a8c0@sc.tlinx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000801c2b077$eb2b8590$1403a8c0@sc.tlinx.org> User-Agent: Mutt/1.4i X-No-Archive: Yes X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 2166 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Mon, Dec 30, 2002 at 06:54:21PM -0800, LA Walsh wrote: > I got the new version of the xfs patch. Seems an older version > xfsdump can have nasty consequences (I assume I need a newer > xfsdump...?)... xfsdump run many times a day for me... it has done for some time. > xfsdump: syssgi( SGI_FS_BULKSTAT ) on fsroot failed: Input/output error more details please? kernel messages? --cw From owner-linux-xfs@oss.sgi.com Mon Dec 30 20:09:02 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 20:09:12 -0800 (PST) Received: from tolkor.sgi.com (tolkor.SGI.COM [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV4913v000406 for ; Mon, 30 Dec 2002 20:09:02 -0800 Received: from snort.melbourne.sgi.com (snort.melbourne.sgi.com [134.14.55.149]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBV4Kakq016746 for ; Mon, 30 Dec 2002 22:20:37 -0600 Received: from snort.melbourne.sgi.com (localhost [127.0.0.1]) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5) with ESMTP id gBV4Cg3s697324 for ; Tue, 31 Dec 2002 15:12:42 +1100 (EST) Received: (from nathans@localhost) by snort.melbourne.sgi.com (SGI-8.12.5/8.12.5/Submit) id gBV4CfAR697116 for linux-xfs@oss.sgi.com; Tue, 31 Dec 2002 15:12:41 +1100 (EST) Date: Tue, 31 Dec 2002 15:12:41 +1100 (EST) From: Nathan Scott Message-Id: <200212310412.gBV4CfAR697116@snort.melbourne.sgi.com> To: linux-xfs@oss.sgi.com Subject: TAKE - repair X-archive-position: 2167 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: nathans@snort.melbourne.sgi.com Precedence: bulk X-list: linux-xfs Merge Glen's fix from IRIX - checking for a v2 dir block with no entries. Also an endian bug I came across while doing the merge (also in v2 dirs). Date: Mon Dec 23 20:56:40 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135764a cmd/xfsprogs/repair/phase6.c - 1.11 Comment out the setbiosize/getbiosize ioctls descriptions as these have now been removed. Date: Thu Dec 26 14:02:36 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135785a cmd/xfsprogs/man/man5/xfs.5 - 1.5 xfs_repair updates - i18n changes, detection of readonly mounts fixed up. Date: Mon Dec 30 20:09:59 PST 2002 Workarea: snort.melbourne.sgi.com:/home/nathans/2.4.x-xfs The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: xfs-cmds:slinx:135843a cmd/xfsprogs/VERSION - 1.64 cmd/xfsprogs/doc/CHANGES - 1.89 cmd/xfsprogs/debian/changelog - 1.57 - bump version, document changes. cmd/xfsprogs/repair/bmap.c - 1.5 cmd/xfsprogs/repair/phase6.c - 1.12 cmd/xfsprogs/repair/phase7.c - 1.5 cmd/xfsprogs/repair/avl64.c - 1.8 cmd/xfsprogs/repair/dir2.c - 1.12 cmd/xfsprogs/repair/sb.c - 1.9 cmd/xfsprogs/repair/dir.c - 1.11 cmd/xfsprogs/repair/phase4.c - 1.10 cmd/xfsprogs/repair/dinode.c - 1.10 cmd/xfsprogs/repair/phase5.c - 1.6 cmd/xfsprogs/repair/agheader.c - 1.10 cmd/xfsprogs/repair/dir_stack.c - 1.6 cmd/xfsprogs/repair/init.c - 1.7 cmd/xfsprogs/repair/rt.c - 1.5 cmd/xfsprogs/repair/versions.c - 1.6 cmd/xfsprogs/repair/phase2.c - 1.8 cmd/xfsprogs/repair/phase3.c - 1.8 cmd/xfsprogs/repair/incore_ext.c - 1.5 cmd/xfsprogs/repair/phase1.c - 1.6 cmd/xfsprogs/repair/xfs_repair.c - 1.10 cmd/xfsprogs/repair/dino_chunks.c - 1.7 cmd/xfsprogs/repair/incore.c - 1.7 cmd/xfsprogs/repair/avl.c - 1.8 cmd/xfsprogs/repair/incore_ino.c - 1.8 cmd/xfsprogs/repair/scan.c - 1.7 cmd/xfsprogs/repair/attr_repair.c - 1.13 cmd/xfsprogs/repair/io.c - 1.7 cmd/xfsprogs/po/Makefile - 1.3 cmd/xfsprogs/po/xfsprogs.pot - 1.2 - i18n updates for xfs_repair. cmd/xfsprogs/libxfs/init.c - 1.24 cmd/xfsprogs/libxfs/linux.c - 1.2 - fix detection of readonly mounts. From owner-linux-xfs@oss.sgi.com Mon Dec 30 21:53:39 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 21:53:49 -0800 (PST) Received: from mail.mnsu.edu (Mail.MNSU.EDU [134.29.1.12]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV5rV3v001531 for ; Mon, 30 Dec 2002 21:53:31 -0800 Received: from mnsu.edu (dyn3226.MavNet.MNSU.EDU [134.29.69.123]) by mail.mnsu.edu (8.9.3/8.9.3) with ESMTP id XAA25368 for ; Mon, 30 Dec 2002 23:58:25 -0600 (CST) Message-ID: <3E1131FE.6060900@mnsu.edu> Date: Mon, 30 Dec 2002 23:58:22 -0600 From: "Jeffrey E. Hundstad" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: linux-xfs@oss.sgi.com Subject: linux-2.4.20-xfs CVS:20021230 Content-Type: multipart/mixed; boundary="------------020102030309030605040300" X-archive-position: 2168 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: jeffrey.hundstad@mnsu.edu Precedence: bulk X-list: linux-xfs This is a multi-part message in MIME format. --------------020102030309030605040300 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit The CVS version as of 20021230 of the linux-2.4.20-xfs tree gives me errors. The .config is attached. This same .config worked with the CVS version of 20021130. Errors from 20021230 CVS linux-2.4.20-xfs tree: make[4]: Entering directory `/home/j3gum/src/linux/fs/xfs/support' gcc -D__KERNEL__ -I/home/j3gum/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -I.. -nostdinc -iwithprefix include -DKBUILD_BASENAME=debug -c -o debug.o debug.c debug.c:45: `XFS_MAX_ERR_LEVEL' undeclared here (not in a function) debug.c:45: size of array `err_level' has non-integer type debug.c:46: warning: excess elements in array initializer debug.c:46: warning: (near initialization for `err_level') debug.c:46: warning: excess elements in array initializer debug.c:46: warning: (near initialization for `err_level') debug.c:47: warning: excess elements in array initializer debug.c:47: warning: (near initialization for `err_level') debug.c:47: warning: excess elements in array initializer debug.c:47: warning: (near initialization for `err_level') debug.c:47: warning: excess elements in array initializer debug.c:47: warning: (near initialization for `err_level') debug.c:48: warning: excess elements in array initializer debug.c:48: warning: (near initialization for `err_level') debug.c:48: warning: excess elements in array initializer debug.c:48: warning: (near initialization for `err_level') debug.c: In function `cmn_err': debug.c:89: `XFS_MAX_ERR_LEVEL' undeclared (first use in this function) debug.c:89: (Each undeclared identifier is reported only once debug.c:89: for each function it appears in.) debug.c: In function `icmn_err': debug.c:107: `XFS_MAX_ERR_LEVEL' undeclared (first use in this function) make[4]: *** [debug.o] Error 1 make[4]: Leaving directory `/home/j3gum/src/linux/fs/xfs/support' make[3]: *** [first_rule] Error 2 make[3]: Leaving directory `/home/j3gum/src/linux/fs/xfs/support' make[2]: *** [_subdir_support] Error 2 make[2]: Leaving directory `/home/j3gum/src/linux/fs/xfs' make[1]: *** [_subdir_xfs] Error 2 make[1]: Leaving directory `/home/j3gum/src/linux/fs' make: *** [_dir_fs] Error 2 make: *** Waiting for unfinished jobs.... --------------020102030309030605040300 Content-Type: application/gzip; name="config-2.4.20-xfs-20021230.gz" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="config-2.4.20-xfs-20021230.gz" H4sICHUxET4CA2NvbmZpZy0yLjQuMjAteGZzLTIwMDIxMjMwAIxcS3PbuLLe z69gzSxupmoyESlZlk9VFhAISohIgiZAPbJhaWwm0Y0t+crynPjf3wYpWXyg IS+mMsL34dVooBuNpv/47Q+HvBx2j+vD5m798PDqfC+2xX59KO6dx/XPwrnb bb9tvv/Hud9t/+fgFPebw29//EZFHPBJvhwNP79CA8efcpxJZ/PsbHcH57k4 nFgZ913Ng3pA3d0X0PDhZb85vDoPxb/Fg7N7Omx22+dzu2yZsJRHLFYkPFUM d+v79T8PUHl3/wL/PL88Pe32tcFEws9CJusDgqI5SyUXsWlcM4BPrSf73V3x /LzbO4fXp8JZb++db4UeZfFcDfvYYH80rLd0BgYYcGUBlKQoFkVLMzbEGkxA XjyLOOdWfGBGZ0ODiKLZdUOeLCSxuTpNMymYGVvwmE55QodW2LOifR/pd5Xy ZWvKZ+3MF0m+EOlM5mIGE6kBPJ6HyaRZRqNkSaetwiXx/WbJWC5I0ixKREL8 qo+3oaULyaJ8wmJQZZrLhMehoDPDOCui7hm6ykk4ESlX06jZQ+jmlNApy+WU B+rzsI5NicxBlZoVJkJAYwlvFWeS5X0/FovWBCasy0uSVOTQJ53JrDWcoNcL EMlGlNXFoASMeEyMq8dHM/OqcpoKKnyzPpWdyBTFaAInjkHOsZjyyTRiUX14 x6LBxNjcER3aYfMciJrmLMpCouD8Me0tlaaN0zNKECXOEtNCJjkX3WLQMRIa 6FycChuyArXJfS7JOGRI55VilYfgpLQMD5rx8nQ+eGOmzn0llNf7gJ+giWMu pFFIFezzlFFl6L+CSbxqtJ/r5polVQvnMphRkxCTqGkaGFCQE4UYRjIVKgmz yZu5oBHl5BNd7+/HL881W1SbmWbUWzpW5M50d3h6ePnuyG6tYzd6yGaFO+M5 FVFCbt9Jy+N5SqKLZD6+zCE0MZ22ciXncMbXZTyWfg5HCGVSQi3jCkMtqsLz Ws2oSFnOwqDeTlVIRKaMgxvzOIhUB2+irSaPpRFHLHBilkN77megWaFc06h4 3O1fHVXc/djuHnbfXx2/+HcDbobzIVL+nw2/QvldVVnDXnsA90griVHFSJqI VHUrauXSHkzysH49+m8v4NGBj3XetEmcfH6sbZfqd1l//LC7++ncV2M91xiH s9xn8zzwG4I8li7N9hnGyJFjXNekyW3uEytMOWgPwikxSSXPFUnwXvT4fEJv hj0rJWsd5S04FKJm9U+l8dg/y/FUCFuty4TCXPKv7POgdzNsgzzmKu0IViqi ZFevXh4Om4/V+pz0wvmQEjB6etXDedTULd86awSO/DzkMSMphur+ejbQtYFX GAgGU/EEbKd10DDHjlji4vDf3f7nZvu9e6FICJ01rFT5O4+i0pF7ax4sGUy6 7MLkPzAV8FCxtFWlKoRK42xiqPZW53QdivmyZqkq63l2iZJKBJRI82kHBOLP SUwZSBKOPJZiNNjSRgh6BJjbwElq3k1w4pjVRU8jZzQ2HvExGCEx46UBLpfK cXjyH71g3zYPh2IPl0LjGQVziAOoG8cqhQWrnVclEKikXcRT2i66zVjGOrxE aZdHtsvBaaNTUPyIKzMUEWoGkplSq4RhtdIZgpTqDqe4GQbn2QyAqM2AL2li RgjUkggWsniipsgYwD6bAZpEEhnflIVwhTdj+lRDBIWudQVnMQ0ZQWYuFnG3 x+Pma5Uqkk5AX1P2RXuNZjDiaSo6NWOiDEWwa5jPatfEZktEghKmxGfoOI7+ 62Nj/x7bLj16w746M2QcJfmYSE5NYzPsCV1s2D0RiSchNkiDKh4Rgy4eEZMy vgmluyWOUCgmCJLhkFkZ4bwyb3QA3lSjJfPSYdaHIJ0SHkvsdK0zgwXxI4Q4 N0c9ZlOlkLOUKHNb85DE+ajnubcd2+fUDT5Plki7JJx1qpKnp4fisH6oe3xv VbStJUkSsnbVGoPC0W821uD6TZArvGd2AEKSjM1ASFFz5fM5S81DYPAvMroF CNNiP3XDAdjgkoIypos8CMUCSoAYdmR7u5PaJfu02zvf1pu9838vxUsBDkpd xLoZSafMxxwa51A8HwyVwOJMWNyppYqH4unHbvtqul8mU5CH2VHXSM6XX+wo dq8F3foEjv6nKIg+pWHYjc4CeLL+8L9/6Qqltwr/wpXqwpWjVjl5KNbP4PYW hePv7l4ei+2h9Bo+be6Lvw+/Ds43EPaP4uHp02b7befstro7536/+bep2aem p35uu6BUFMutACr7XNZCYMeCyrLrCHQjGnZCtWLN7N2eqHMW+yJ9FzXIvnAl s3dxsat+mxeRpXpn97cZiVX2vmYlIxOi3ieBhf0GA8dwxFLeNJIdluJzcak3 Ku0rTQ13PSjWl08jAGdDkqyMkL61NmyPz8CU6XURVHVPEq2jdz82T1Bw2luf /nn5/m3zy6zWNPKHA/t1t6LkLJ6Wlwm7bMoAgZWSfnV7vZ5dflVw8DxjHU6S U5LC0ZLedm/Mev0j0g4pnlARBGNBUv+iCkETgUhbU6ztx6qLnGRKNLcxACIO V8393Wy5U0G3tOCJacBHhuIRM4eqjoSYLXI/BaMGFxGpeDyR3d5J1XenD8Lo 0Fsi9r/CcgU30HhiFRsJuXu17JsNp0+t+FsbkX89wIZSYbkAy51eOn9LRV1e pIwuqPtq5NHhjX3MVF5d9e3tTBPVR0ZTQaUiwfJcbGU4tFISzs3daOA9ixjL 0fXAvbJyRKL40HPtA/Gp18OU6gTm4yxFIhZvlHIXWruS88VM2hkclsi1r6IM 6U2PXRCvSiPvxnZezTkBjVkuly37nevnSMmUxHew8Sjh83G9pXKni7gV6e8e GaULIY17Ha4+hNvPvyNHr8G7eKCXHdujTVXXoTsasA6jekD/cL95/vmXc1g/ FX851P+YijIo2V6omj2Vfs6WcPfXgPw86NWivNO0YpvV6wQLKZVFlLJx1TuX Gvyr04jS+oi839rDmbxNf/dYVDK4PwX4i7+//w3zdv735Wfxz+7Xn2/SedTB W7hxOWEWNyx3GcYuY4hVyMqkXiWnciyheuPxUCPw/1KBC2beQSUFLtCT1rlx XsGH3X8/VhkZpb+8N3oW/UUOe2KZo6pX9nMNvgBcn5AlKymEYsa7gqfEvfKW FwgDz064RpygikCofRaE0+vlcnmRkIvQ0oqfqJx7wtKKjufKlWXZeOy1nKtW C9FVn95cD3BGxCbEPtlxJkE7OMUZNLkNqE27/GjZd29cmywU7Xsjy0yYvhha 0RyzrWdGwi3SDjKVgcfpi4jwGKdNfOQNokKPaR0xTa/6tvmAqbAtK1e2oQJO XNu6l93TQW9ILnGuf/3CKXKl9WcEiuxdamdk2w5v7eCUhEh3aIEpt2u6Jnhe j1sYknsDG+G2VHMd3bnI4TK53A69SHGtKm+7ClcEHl27vUtiH9jk6tP+Tc9y GCsYIo5m7iDvDwILIQQ7KbE4wdm0dexO8PK82W2dCNyO5oNm3fQEmWyl0LSg fCyEsuFcslgyG6N16W7Drby36k7OGHPc/s3A+RBs9sUC/jvb+Q/1HMbGe6yu VtbqtAc2AhcCZkGgHE0X0di4nXXWQLF8Po2VPgHaZSooGrHszOIctgQXgtPz SyBJ6bY4mELPgLRCtyfHOYuiVcOXE7GP3YXYbQZ31a9IkBcuUeZaaspSRfAX UjluBzvKobPDj2Kv5/MBtutu7wAp+mdz+LMhgar11rOvzOJQh2HM90qSJKuI IQEuqDqOCMWwW4YhE2O6gx5h5RLnfSoauXIsNF8UWegh5UmYSQRCTisWmu92 fXqFXGVZGFEUyI2ZoXORKras6xAu/Jo8ZEQvUVJCkWUiyr1GDJsOhBEkooCZ //KdHklhK18HkCOhxITOfrBqL/R60txa8hOLEffQDz3zGcNczJpHq5R3MsbP w5Sj/sjrIdsB1H1qnt6KhaFYBJhjN7sZhQim+ETEZt0LfB9Jx+MJkg+WhNyU zZkkSV3r4Gd1ndNZJ+Z2gFE9VJpby4lcxbTdpi7LlVqhTerQNOZyaHwsff24 ieFIordsTbpUHm0WH4rnZ0ebmg/b3fbjj/Xjfn2/2f3ZftFKid/0hqsHrd3P YuukOq/HYCaU5fnOrKspxfaGhIO2KehqBuuts9keiv23davzhcErII/rQ/Gy d1I9RZMhB/U1T5TvfeJ82Gy/7df74v5PoxOQ+t23Ny79GMj/PL8+H4rHBl0j bbp4uD9GZE7XfL0shzIE8FdJ5T5rrA3181icHi263W+fXg7O3W5vMPg8TrJm WoMuyGdsNW7lWLUYkcgkM6dhVYQvYgVwt2k2b9WqJvJjvV/f6VSjzhvjvJYW NldlDEWEtWR4WT4t1TuqSnRsCM585OHkyImriIzfinTUMsFuRnmiVrKZHlYV wliyWH32roYn/5AaJOzVszs8Wn4/MOZNoUNxMoVDJpEJktCnKSyco9gczlUW oc5i1W1CAxSnU5CBeT316MCbPEXTIlifRuApk6U2mFLodXktq0+eCt4qjzwK V6e800AtT9sFPCFIFuTs2vW6tcvhfdnBftvc/XxuqXs+IRE7pnS1lDOWV1cj i9aHfDJVaFy/4sDhpTuwMKgcDN2lhcCizO3NXAtDq6+w48bUY1QmJCZV7k6r IdL3Ld0QxO4e5ynGKbHgkwBxSo5wiqRAVjCPwegSqiwUFSFR9aOQ4MRccDgi Uls35aNInsnxZZLX9yykBUlh0Wx9RWQC2xjbxNWYE/DyRDq+RBmTMLRx9LOl dd7++Ma2NqDhVNgGqrJ0LCYpCcyKfstpz+tkhR/N+eHux/3uu6O/3miZc0Wn vphgT5Z5iu5MxUIU1TWT6Hpo3vmdDzNObopqfEvhKyQBK+3fDAfINwnghYIb ZzZQIl4lXWMeVC82cBNwvj3snp5eyyec04W+8hcaoZm2iE99TxpP4PCzEpJ5 oBoduT1zO/ohrt0WQbLWj1g+cq9clCC5xCuHHK9Xfu9mikikjWsy/Gw/CJQi g3Jn8Ldbe1ypVYjZot2G8hHl1mDaCtjVIeIzEdfPWl3aFnAHzJdBylg+cC2s Pt5ENCEohkk8WpA5M3/f8Fjcb9YGbw3OVJFXnl9Jnm/ui50T7PZOuNm+/Goz tWORB43n09LfQD6dqVoj9+unQ2OFqsbGajQY1eV67CMyz65CacKJBZaEXHmD Gyw8xdK83+sPbQ0ofZuwjeCrSJEzv4aDm/X1IseniA7VSWEU9vs2Vtofup6t nYitulpR3adqS3M+AfVtKqeg9WZjXeFpmVd+keBZGOSrYnRqIUxYpNjsIgEN zlSkiCx554bY4TCdQmhj8BQc8ggRdIuTp7608GTgDoPINmbwlVIC0rFR0kza FkitkqlAbH7F+CpClTaTYiqjtdF/D6C8/db27G0mVMNw3Oov/ubm463CPMSX CMDjOWZ7m61DpkQg4ZyxoAMMThkHdxqv/oaXX2LbKeVxx+PArBjEtwyywvJ0 YYaDTtVTOKMEGvF4hndTYp2noDOM9QKX7X51jh8LvowbX8vBT/wDLP21Q61q JH0hW0YhOxWaosXHBmpTtMzwS2DHPAyk4AcikIoS48jKGvWvnsXNcNirxnrq UoS8/uXbVyA1p/7FNl7bYmlUf8ujkxQpYuB5zJdY6/Ml3nOsLmCInk4TTIMM ngC4EXgvFRjpEIwFx3QO0ES1lew2Xg7wDo8oMrFURJa94bV60h9jY/1kfmCD kP4zfOAVlC9Srox/RCCQje2nfydCgl4QGjb+HoGevUJaOJ3mtSI/IglvN4Cr awK333EWIA/Rp6fL0pbIN1ty3p3CJ5gAylBBxL5+FajKWrQZoHkfWXOhNI7V 81EAa7HEFE2wJ8E0MVtw/YZsimDKaNw4bfTvONSrEJAsrB07JyBlkVDs8+93 T4P+9e+1gdEEFRDVe/r4xa7kEzQ+VhHL/PlywHaedp+sBL0wsW1IAs5yK0FG JAx9YaOATCxomX5o2vLVKV6J/vTHAg4b/R2Mo16fmo8UcNdROs0ofvtu2BRJ Lc3fG7WzcOeC6ke1Z9YHuMk64Xr7/WX9vah9cHTmvqnC75vn3Wh0dfPR/b0O 67/yondmDvpQt7AN7Lp/bZZSg3R9dZk0uuq9h+S9h/Su7t4x8NHwPWMauu8h vWfgw/57SIP3kN4jAiQPu0W6uUy66b+jpZv3LPBN/x1yuhm8Y0yja1xOsEe1 wuejy8243nuGDSzXlLFR68tt76ET4F0cZv8i4/JUry4yhhcZ1xcZNxcZ7uXJ uJdn4+LTmQk+ylM7nKFwpoJR941yt33ePRTd8OB8QrrPksfgDwurv3tU+xMa b+TuPXm/fiw+/vPy7Vux774kBuNz62WOVa3Tc7x3nKd8bg5oAUbD1iepdTCJ PBzqo02uxixFc0KBMGcSHQ+IDskzAnA6Mf2lJ0ywUCEi4DMsseZIM9+iJrAq HvvaZmMpl4BiAVOAYiYigqVpA97HosZaHEL4QrgYrPSnWMh1R9fmqcqQ7KZg TO0ORkWgwXh01rK3svLPQ7YLvYGhsO815aiLAxGrBffVdFR+rod2rnmNW5Iu yEe/THH0I+QOO3zwknW5WQpHguv98jycMfzlujiaMJKG7WE1KYSKNG5Tjp+i vGzvax/pwPXVb+Qu6AL9ynE1QPyXijFWo+uRBacRmkRT4rYn5oj73EqomrBk /R7HIAfeyNYCk27/2vSqVIPdrnSYlHDsCVvLtvBrg9G3TVBnIVpwjsSaKxQu nDdDLNO+ZEgRczrnYyYtJNueP85Exj4NibxASXiMSvr8Kd3bTbFUgvondo0K Qsruuuj4PNOfTKD9+K2/53TUdt8dYbnxlaAmJCTLlYVB/JCPbTjlMKOlMUvv rKxweHUmJSXF/nRZRZhkNsnPtRzty7u0LpxERxwl2aBn2B5x5F0NrZrvW6Wd IKoE5TqrSwcTZ7bqliHLcS0UUS3MgvU9nQ9Z/nWjVlP69TFIhV37ScbR/lZR f+QaFlUkYV8S2wFSMTwLYxUF9iO2IuQhmxBq090MLvVD7N57lBLzZWJdNDXv qHdpb3TeSseTzOrrAD+qkNspahBtnu/+v5GrWW4UhsGvkkdoM5Nt9mhsNnZj fgZDMtMb7TBtZmmYIeSwb7+SEygGi/aQHCzJyLJsGfNJVV2X56q5XmwHs3Jt NxlMFBhfHGJrwGJhY71zeQ8EncQ7X2r9oKVsLh2esbu2qWs4/4p5iiP2E0qw qeReuB6QCyCP57tvg5Dq9yJkSCRXXp1u9SBXvC4vF1/OJQqzgvoSaNWN1PoX SQ10EeZJQiSyIcd0+xiRMJ0H3jrdmbw3DjPqdDYQWc7+sIB8aM+HeAMKnzLm U0asifO/89iUf9+XTLfQV/UtnxEie/j9Izb3IOVhei6i1Mgkn9qL8YiQTDN7 p9zf7ln/vX6W55XqcchftUSlcmuJorwkEj3vNAuhWmKgwLlI3gd03zTO0o5X pdTncSQf2cQZhrGrz/KdwH/brYJT1QmsToJvl7yHszgmoGq3FcKzZEltmcK/ FxmNqi+BWVBaBRFn0XRLSQ4b4hXBeseR08MJIWgvuO2BqpOBZNhxGb2EhAlo MwkWTDCMgwn6TyslYjea+Q6XQgQzxCkH6Vmut48bWus9BPmFLY6znDYXF9ym Y5EM8ItDf0SxeX7Erl0Y87R+8IqZqj2VNYYiEOycm5jJTE5rGn05lRNCCRUy lWwW/J4VYWaOTNOLOVc7TYeWTB92C3bTfA6AC+pr1TVN9+EbMsaql5nIHjOS 6tVH+fZ3UgLtViphj5l0cyPp02tbtv9WbXPtTufxmnuBgzwiJLRTg9K23pNi oPU/CAZ6DRVjAAA= --------------020102030309030605040300-- From owner-linux-xfs@oss.sgi.com Mon Dec 30 22:17:58 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 22:18:05 -0800 (PST) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.58.33]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV6Hv3v002131 for ; Mon, 30 Dec 2002 22:17:58 -0800 Received: from Shiva (shiva [192.168.3.20]) by ishtar.tlinx.org (8.12.6/8.12.2/SuSE Linux 0.6) with ESMTP id gBV6MqjF003796; Mon, 30 Dec 2002 22:22:52 -0800 From: "LA Walsh" To: "'Chris Wedgwood'" Cc: Subject: RE: xfsdump... Date: Mon, 30 Dec 2002 22:22:52 -0800 Message-ID: <000001c2b095$0cc4e080$1403a8c0@sc.tlinx.org> 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.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <20021231033202.GA17409@tapu.f00f.org> X-archive-position: 2169 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: law@tlinx.org Precedence: bulk X-list: linux-xfs Not a lot to go on, since when it died, it appears to have shutdown the root file system. Dec 30 18:47:46 ishtar kernel: xfs_inotobp: xfs_imap() returned an error 22 on sd(8,3). Returning error. Dec 30 18:47:46 ishtar kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on sd(8,3). Returning error. Dec 30 18:47:46 ishtar kernel: klogd 1.4.1, ---------- state change ---------- Dec 30 18:47:46 ishtar kernel: Inspecting /boot/System.map-2.4.20-xfs Dec 30 18:47:46 ishtar kernel: Loaded 22282 symbols from /boot/System.map-2.4.20-xfs. Dec 30 18:47:46 ishtar kernel: Symbols match kernel version 2.4.20. Dec 30 18:47:46 ishtar kernel: Loaded 6 symbols from 1 module. Dec 30 18:47:46 ishtar kernel: xfs_inactive: xfs_ifree() returned an error = 22 on sd(8,3) Dec 30 18:47:46 ishtar kernel: xfs_force_shutdown(sd(8,3),0x1) called from line 1835 of file xfs_vnodeops.c. Return address = 0xc021370a Dec 30 18:47:46 ishtar kernel: Filesystem "sd(8,3)": I/O Error Detected. Shutting down filesystem: sd(8,3) Dec 30 18:47:46 ishtar kernel: Please umount the filesystem, and rectify the problem(s) Dec 30 18:48:38 ishtar xinetd[11572]: warning: cannot open /etc/hosts.allow: Input/output error Dec 30 18:48:38 ishtar xinetd[11572]: warning: cannot open /etc/hosts.deny: Input/output error Dec 30 18:48:38 ishtar xinetd[11572]: execv( /usr/sbin/imapds ) failed: Input/output error (errno = 5) Dec 30 18:48:38 ishtar xinetd[11573]: warning: cannot open /etc/hosts.allow: Input/output error Dec 30 18:48:38 ishtar xinetd[11573]: warning: cannot open /etc/hosts.deny: Input/output error Dec 30 18:48:38 ishtar xinetd[11573]: execv( /usr/sbin/imapds ) failed: Input/output error (errno = 5) Dec 30 18:48:38 ishtar xinetd[11574]: warning: cannot open /etc/hosts.allow: Input/output error Dec 30 18:48:38 ishtar xinetd[11574]: warning: cannot open /etc/hosts.deny: Input/output error Dec 30 18:48:38 ishtar xinetd[11574]: execv( /usr/sbin/imapds ) failed: Input/output error (errno = 5) Dec 30 18:48:38 ishtar xinetd[11575]: warning: cannot open /etc/hosts.allow: Input/output error Dec 30 18:48:38 ishtar xinetd[11575]: warning: cannot open /etc/hosts.deny: Input/output error Dec 30 18:48:38 ishtar xinetd[11575]: execv( /usr/sbin/imapds ) failed: Input/output error (errno = 5) Dec 30 18:49:43 ishtar named-xfer[11434]: [198.41.0.10] not authoritative for GOV, SOA query got rcode 0, aa 0, ancount 0, aucount 9 Dec 30 18:49:52 ishtar named-xfer[11434]: [193.0.14.129] not authoritative for GOV, SOA query got rcode 0, aa 0, ancount 0, aucount 9 Dec 30 18:50:00 ishtar /USR/SBIN/CRON[11582]: (root) CMD ( /usr/lib/sa/sa1 ) Dec 30 18:57:31 ishtar syslogd 1.4.1: restart (remote reception). Here's dmesg after it comes back up: Linux ishtar 2.4.20-xfs #1 SMP Sun Dec 29 08:25:19 PST 2002 i686 unknown ishtar:/var/log> dmesg BIOS-e820: 000000003fffe000 - 0000000040000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved) BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved) 127MB HIGHMEM available. 896MB LOWMEM available. found SMP MP-table at 000fe710 hm, page 000fe000 reserved twice. hm, page 000ff000 reserved twice. hm, page 000f0000 reserved twice. On node 0 totalpages: 262142 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 32766 pages. Intel MultiProcessor Specification v1.4 Virtual Wire compatibility mode. OEM ID: DELL Product ID: WS 410 APIC at: 0xFEE00000 Processor #0 Pentium(tm) Pro APIC version 17 Processor #1 Pentium(tm) Pro APIC version 17 I/O APIC #2 Version 17 at 0xFEC00000. Processors: 2 Kernel command line: auto BOOT_IMAGE=2420-xfs ro root=803 vga=0x0303 Initializing CPU#0 Detected 994.885 MHz processor. Console: colour VGA+ 80x50 Calibrating delay loop... 1985.74 BogoMIPS Memory: 1031304k/1048568k available (2508k kernel code, 16880k reserved, 1220k data, 308k init, 131064k highmem) kdb version 2.5 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode cache hash table entries: 65536 (order: 7, 524288 bytes) Mount-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 65536 (order: 6, 262144 bytes) Page-cache hash table entries: 262144 (order: 8, 1048576 bytes) CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 0383fbff 00000000 00000000 00000000 CPU: Common caps: 0383fbff 00000000 00000000 00000000 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch (rgooch@atnf.csiro.au) mtrr: detected mtrr type: Intel CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check reporting enabled on CPU#0. CPU: After generic, caps: 0383fbff 00000000 00000000 00000000 CPU: Common caps: 0383fbff 00000000 00000000 00000000 CPU0: Intel Pentium III (Coppermine) stepping 06 per-CPU timeslice cutoff: 731.65 usecs. enabled ExtINT on CPU#0 ESR value before enabling vector: 00000040 ESR value after enabling vector: 00000000 Booting processor 1/1 eip 2000 Initializing CPU#1 masked ExtINT on CPU#1 ESR value before enabling vector: 00000000 ESR value after enabling vector: 00000000 Calibrating delay loop... 1985.74 BogoMIPS CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 256K Intel machine check reporting enabled on CPU#1. CPU: After generic, caps: 0383fbff 00000000 00000000 00000000 CPU: Common caps: 0383fbff 00000000 00000000 00000000 CPU1: Intel Pentium III (Coppermine) stepping 06 Total of 2 processors activated (3971.48 BogoMIPS). ENABLING IO-APIC IRQs Setting 2 in the phys_id_present_map ...changing IO-APIC physical APIC ID to 2 ... ok. init IO_APIC IRQs IO-APIC (apicid-pin) 2-0, 2-13, 2-20, 2-21, 2-22, 2-23 not connected. ..TIMER: vector=0x31 pin1=2 pin2=0 number of MP IRQ sources: 41. number of IO-APIC #2 registers: 24. testing the IO APIC....................... IO APIC #2...... .... register #00: 02000000 ....... : physical APIC id: 02 .... register #01: 00170011 ....... : max redirection entries: 0017 ....... : PRQ implemented: 0 ....... : IO APIC version: 0011 .... register #02: 00000000 ....... : arbitration: 00 .... IRQ redirection table: NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: 00 000 00 1 0 0 0 0 0 0 00 01 003 03 0 0 0 0 0 1 1 39 02 003 03 0 0 0 0 0 1 1 31 03 003 03 0 0 0 0 0 1 1 41 04 003 03 0 0 0 0 0 1 1 49 05 003 03 0 0 0 0 0 1 1 51 06 003 03 0 0 0 0 0 1 1 59 07 003 03 0 0 0 0 0 1 1 61 08 003 03 0 0 0 0 0 1 1 69 09 003 03 0 0 0 0 0 1 1 71 0a 003 03 0 0 0 0 0 1 1 79 0b 003 03 0 0 0 0 0 1 1 89 0c 003 03 0 0 0 0 0 1 1 91 0d 000 00 1 0 0 0 0 0 0 00 0e 003 03 0 0 0 0 0 1 1 99 0f 003 03 0 0 0 0 0 1 1 A1 10 003 03 1 1 0 1 0 1 1 A9 11 003 03 1 1 0 1 0 1 1 B1 12 003 03 1 1 0 1 0 1 1 B9 13 003 03 1 1 0 1 0 1 1 C1 14 000 00 1 0 0 0 0 0 0 00 15 000 00 1 0 0 0 0 0 0 00 16 000 00 1 0 0 0 0 0 0 00 17 000 00 1 0 0 0 0 0 0 00 IRQ to pin mappings: IRQ0 -> 0:2 IRQ1 -> 0:1 IRQ3 -> 0:3 IRQ4 -> 0:4 IRQ5 -> 0:5 IRQ6 -> 0:6 IRQ7 -> 0:7 IRQ8 -> 0:8 IRQ9 -> 0:9 IRQ10 -> 0:10 IRQ11 -> 0:11 IRQ12 -> 0:12 IRQ14 -> 0:14 IRQ15 -> 0:15 IRQ16 -> 0:16 IRQ17 -> 0:17 IRQ18 -> 0:18 IRQ19 -> 0:19 .................................... done. Using local APIC timer interrupts. calibrating APIC timer ... ..... CPU clock speed is 994.8832 MHz. ..... host bus clock speed is 99.4880 MHz. cpu: 0, clocks: 994880, slice: 331626 CPU0 cpu: 1, clocks: 994880, slice: 331626 CPU1 checking TSC synchronization across CPUs: passed. Waiting on wait_init_idle (map = 0x2) All processors have done init_idle PCI: PCI BIOS revision 2.10 entry at 0xfcf1e, last bus=4 PCI: Using configuration type 1 PCI: Probing PCI hardware PCI: Using IRQ router PIIX [8086/7110] at 00:07.0 PCI->APIC IRQ transform: (B0,I7,P3) -> 19 PCI->APIC IRQ transform: (B0,I14,P0) -> 17 PCI->APIC IRQ transform: (B0,I17,P0) -> 19 PCI->APIC IRQ transform: (B1,I0,P0) -> 16 PCI: using PPB(B0,I16,P0) to get irq 19 PCI->APIC IRQ transform: (B2,I4,P0) -> 19 PCI: using PPB(B0,I16,P1) to get irq 16 PCI->APIC IRQ transform: (B2,I5,P1) -> 16 PCI->APIC IRQ transform: (B3,I9,P0) -> 17 PCI->APIC IRQ transform: (B3,I10,P0) -> 18 PCI->APIC IRQ transform: (B3,I14,P0) -> 18 Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket apm: BIOS version 1.2 Flags 0x03 (Driver version 1.16) apm: disabled - APM is not SMP safe. Starting kswapd allocated 32 pages and 32 bhs reserved for the highmem bounces devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au) devfs: boot_options: 0x0 Installing knfsd (copyright (C) 1996 okir@monad.swb.de). SGI XFS snapshot 2.4.20-2002-11-29_01:21_UTC with ACLs, no debug enabled ACPI: Core Subsystem version [20011018] ACPI: Subsystem enabled ACPI: System firmware supports S0 S1 S4 S5 Processor[0]: C0 C1 Processor[1]: C0 C1 ACPI: Power Button (FF) found pty: 256 Unix98 ptys configured Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A Real Time Clock Driver v1.10e Uniform Multi-Platform E-IDE driver Revision: 6.31 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx PIIX4: IDE controller on PCI bus 00 dev 39 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA hda: WDC WD1000JB-00CRA1, ATA DISK drive hdb: ATAPI DVD-ROM 16X, ATAPI CD/DVD-ROM drive hdc: WDC WD800BB-32BSA0, ATA DISK drive hdd: QUANTUM FIREBALLP AS60.0, ATA DISK drive ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 ide1 at 0x170-0x177,0x376 on irq 15 blk: queue c054a404, I/O limit 4095Mb (mask 0xffffffff) hda: 195371568 sectors (100030 MB) w/8192KiB Cache, CHS=12161/255/63, UDMA(33) blk: queue c054a768, I/O limit 4095Mb (mask 0xffffffff) hdc: 156301488 sectors (80026 MB) w/2048KiB Cache, CHS=155061/16/63, UDMA(33) blk: queue c054a8b4, I/O limit 4095Mb (mask 0xffffffff) hdd: 117266688 sectors (60041 MB) w/1902KiB Cache, CHS=116336/16/63, UDMA(33) hdb: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33) Uniform CD-ROM driver Revision: 3.12 Partition check: /dev/ide/host0/bus0/target0/lun0:<7>ldm_validate_partition_table(): Found an MS-DOS partition table, not a dynamic disk. p1 /dev/ide/host0/bus1/target0/lun0:<7>ldm_validate_partition_table(): Found an MS-DOS partition table, not a dynamic disk. [PTBL] [9729/255/63] p1 p3 /dev/ide/host0/bus1/target1/lun0:<7>ldm_validate_partition_table(): Found an MS-DOS partition table, not a dynamic disk. p1 Floppy drive(s): fd0 is 1.44M FDC 0 is a National Semiconductor PC87306 loop: loaded (max 8 devices) 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html 00:11.0: 3Com PCI 3c905B Cyclone 100baseTx at 0xcc00. Vers LK1.1.16 eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin and others eth1: OEM i82557/i82558 10/100 Ethernet, 00:90:27:0B:E4:50, IRQ 19. Receiver lock-up bug exists -- enabling work-around. Board assembly 715191-003, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x24c9f043). Receiver lock-up workaround activated. eth2: OEM i82557/i82558 10/100 Ethernet, 00:90:27:0B:E4:51, IRQ 16. Receiver lock-up bug exists -- enabling work-around. Board assembly 715191-003, Physical connectors present: RJ45 Primary interface chip i82555 PHY #1. General self-test: passed. Serial sub-system self-test: passed. Internal registers self-test: passed. ROM checksum self-test: passed (0x24c9f043). Receiver lock-up workaround activated. PPP generic driver version 2.4.2 PPP Deflate Compression module registered Universal TUN/TAP device driver 1.5 (C)1999-2002 Maxim Krasnyansky Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 941M agpgart: Detected Intel 440BX chipset agpgart: AGP aperture is 64M @ 0xe8000000 SCSI subsystem driver Revision: 1.00 scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.8 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs blk: queue f7ddbe18, I/O limit 4095Mb (mask 0xffffffff) Vendor: SEAGATE Model: ST318452LC Rev: EE31 Type: Direct-Access ANSI SCSI revision: 03 blk: queue f7ddbc18, I/O limit 4095Mb (mask 0xffffffff) Vendor: SEAGATE Model: ST118202LC Rev: 0006 Type: Direct-Access ANSI SCSI revision: 02 blk: queue f7ddb818, I/O limit 4095Mb (mask 0xffffffff) scsi0:A:0:0: Tagged Queuing enabled. Depth 253 scsi0:A:1:0: Tagged Queuing enabled. Depth 253 Vendor: PLEXTOR Model: CD-R PX-R820T Rev: 1.03 Type: CD-ROM ANSI SCSI revision: 02 blk: queue f7dcd618, I/O limit 4095Mb (mask 0xffffffff) Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Attached scsi disk sdb at scsi0, channel 0, id 1, lun 0 (scsi0:A:0): 80.000MB/s transfers (40.000MHz, offset 63, 16bit) SCSI device sda: 35843670 512-byte hdwr sectors (18352 MB) /dev/scsi/host0/bus0/target0/lun0:<7>ldm_validate_partition_table(): Found an MS-DOS partition table, not a dynamic disk. p1 p2 p3 p4 < p5 p6 p7 > (scsi0:A:1): 80.000MB/s transfers (40.000MHz, offset 15, 16bit) SCSI device sdb: 35566480 512-byte hdwr sectors (18210 MB) /dev/scsi/host0/bus0/target1/lun0:<7>ldm_validate_partition_table(): Found an MS-DOS partition table, not a dynamic disk. p1 p2 p3 p4 < p5 p6 p7 > Attached scsi CD-ROM sr0 at scsi1, channel 0, id 6, lun 0 (scsi1:A:6): 10.000MB/s transfers (10.000MHz, offset 8) sr0: scsi3-mmc drive: 20x/20x writer cd/rw xa/form2 cdda tray usb.c: registered new driver usbdevfs usb.c: registered new driver hub Initializing USB Mass Storage driver... usb.c: registered new driver usb-storage USB Mass Storage support registered. md: raid0 personality registered as nr 2 md: raid1 personality registered as nr 3 md: raid5 personality registered as nr 4 raid5: measuring checksumming speed 8regs : 1836.400 MB/sec 32regs : 958.000 MB/sec pIII_sse : 2048.000 MB/sec pII_mmx : 2244.400 MB/sec p5_mmx : 2379.600 MB/sec raid5: using function: pIII_sse (2048.000 MB/sec) md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP IP: routing cache hash table of 8192 buckets, 64Kbytes TCP: Hash tables configured (established 262144 bind 65536) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. FAT: bogus logical sector size 0 FAT: bogus logical sector size 0 XFS mounting filesystem sd(8,3) Starting XFS recovery on filesystem: sd(8,3) (dev: 8/3) Ending XFS recovery on filesystem: sd(8,3) (dev: 8/3) VFS: Mounted root (xfs filesystem) readonly. Freeing unused kernel memory: 308k freed md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. Adding Swap: 265064k swap-space (priority -1) XFS mounting filesystem sd(8,1) Starting XFS recovery on filesystem: sd(8,1) (dev: 8/1) Ending XFS recovery on filesystem: sd(8,1) (dev: 8/1) XFS mounting filesystem sd(8,5) Starting XFS recovery on filesystem: sd(8,5) (dev: 8/5) Ending XFS recovery on filesystem: sd(8,5) (dev: 8/5) XFS mounting filesystem sd(8,6) Starting XFS recovery on filesystem: sd(8,6) (dev: 8/6) Ending XFS recovery on filesystem: sd(8,6) (dev: 8/6) XFS mounting filesystem sd(8,7) Starting XFS recovery on filesystem: sd(8,7) (dev: 8/7) Ending XFS recovery on filesystem: sd(8,7) (dev: 8/7) XFS mounting filesystem ide1(22,3) Starting XFS recovery on filesystem: ide1(22,3) (dev: 22/3) Ending XFS recovery on filesystem: ide1(22,3) (dev: 22/3) XFS mounting filesystem ide0(3,1) Starting XFS recovery on filesystem: ide0(3,1) (dev: 3/1) Ending XFS recovery on filesystem: ide0(3,1) (dev: 3/1) > -----Original Message----- > From: Chris Wedgwood [mailto:cw@f00f.org] > Sent: December 30, 2002 07:32p > To: LA Walsh > Cc: linux-xfs@oss.sgi.com > Subject: Re: xfsdump... > > > On Mon, Dec 30, 2002 at 06:54:21PM -0800, LA Walsh wrote: > > > I got the new version of the xfs patch. Seems an older version > > xfsdump can have nasty consequences (I assume I need a newer > > xfsdump...?)... > > xfsdump run many times a day for me... it has done for some time. > > > xfsdump: syssgi( SGI_FS_BULKSTAT ) on fsroot failed: Input/output > > error > > more details please? kernel messages? > > > > --cw > From owner-linux-xfs@oss.sgi.com Mon Dec 30 23:07:29 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 23:07:37 -0800 (PST) Received: from lips.thebarn.com (lips.borg.umn.edu [160.94.232.50]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV77S3v002801 for ; Mon, 30 Dec 2002 23:07:28 -0800 Received: from [10.0.0.10] (c-24-245-56-70.mn.client2.attbi.com [24.245.56.70]) by lips.thebarn.com (8.12.6/8.12.6) with ESMTP id gBV7CULu040629; Tue, 31 Dec 2002 01:12:31 -0600 (CST) (envelope-from cattelan@thebarn.com) Subject: Re: linux-2.4.20-xfs CVS:20021230 From: Russell Cattelan To: "Jeffrey E. Hundstad" Cc: linux-xfs@oss.sgi.com In-Reply-To: <3E1131FE.6060900@mnsu.edu> References: <3E1131FE.6060900@mnsu.edu> Content-Type: text/plain Organization: Message-Id: <1041318750.55808.7.camel@lupo.thebarn.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.0 Date: 31 Dec 2002 01:12:30 -0600 Content-Transfer-Encoding: 7bit X-archive-position: 2170 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@thebarn.com Precedence: bulk X-list: linux-xfs Looks like eric missed something. Just define XFS_MAX_ERR_LEVEL to 7 in debug.c for now. On Mon, 2002-12-30 at 23:58, Jeffrey E. Hundstad wrote: > The CVS version as of 20021230 of the linux-2.4.20-xfs tree gives me > errors. The .config is attached. This same .config worked with the CVS > version of 20021130. > > Errors from 20021230 CVS linux-2.4.20-xfs tree: > > make[4]: Entering directory `/home/j3gum/src/linux/fs/xfs/support' > gcc -D__KERNEL__ -I/home/j3gum/src/linux/include -Wall > -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common > -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686 > -malign-functions=4 -I.. -nostdinc -iwithprefix include > -DKBUILD_BASENAME=debug -c -o debug.o debug.c > debug.c:45: `XFS_MAX_ERR_LEVEL' undeclared here (not in a function) > debug.c:45: size of array `err_level' has non-integer type > debug.c:46: warning: excess elements in array initializer > debug.c:46: warning: (near initialization for `err_level') > debug.c:46: warning: excess elements in array initializer > debug.c:46: warning: (near initialization for `err_level') > debug.c:47: warning: excess elements in array initializer > debug.c:47: warning: (near initialization for `err_level') > debug.c:47: warning: excess elements in array initializer > debug.c:47: warning: (near initialization for `err_level') > debug.c:47: warning: excess elements in array initializer > debug.c:47: warning: (near initialization for `err_level') > debug.c:48: warning: excess elements in array initializer > debug.c:48: warning: (near initialization for `err_level') > debug.c:48: warning: excess elements in array initializer > debug.c:48: warning: (near initialization for `err_level') > debug.c: In function `cmn_err': > debug.c:89: `XFS_MAX_ERR_LEVEL' undeclared (first use in this function) > debug.c:89: (Each undeclared identifier is reported only once > debug.c:89: for each function it appears in.) > debug.c: In function `icmn_err': > debug.c:107: `XFS_MAX_ERR_LEVEL' undeclared (first use in this function) > make[4]: *** [debug.o] Error 1 > make[4]: Leaving directory `/home/j3gum/src/linux/fs/xfs/support' > make[3]: *** [first_rule] Error 2 > make[3]: Leaving directory `/home/j3gum/src/linux/fs/xfs/support' > make[2]: *** [_subdir_support] Error 2 > make[2]: Leaving directory `/home/j3gum/src/linux/fs/xfs' > make[1]: *** [_subdir_xfs] Error 2 > make[1]: Leaving directory `/home/j3gum/src/linux/fs' > make: *** [_dir_fs] Error 2 > make: *** Waiting for unfinished jobs.... -- Russell Cattelan From owner-linux-xfs@oss.sgi.com Mon Dec 30 23:08:40 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 23:08:42 -0800 (PST) Received: from ishtar.tlinx.org (ishtar.tlinx.org [64.81.58.33]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV78e3v003126 for ; Mon, 30 Dec 2002 23:08:40 -0800 Received: from Shiva (shiva [192.168.3.20]) by ishtar.tlinx.org (8.12.6/8.12.2/SuSE Linux 0.6) with ESMTP id gBV7DajF004160; Mon, 30 Dec 2002 23:13:40 -0800 From: "LA Walsh" To: Cc: "'Chris Wedgwood'" Subject: RE: xfsdump... Date: Mon, 30 Dec 2002 23:13:36 -0800 Message-ID: <000301c2b09c$255c7c00$1403a8c0@sc.tlinx.org> 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.4510 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: <000001c2b095$0cc4e080$1403a8c0@sc.tlinx.org> X-archive-position: 2171 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: law@tlinx.org Precedence: bulk X-list: linux-xfs Sigh... Seems like the current rev of the xfs utils are bound to GLIB2_3? Seems like the latest SuSE_81 version is at 2.2.5. Is there a need to bind the rpms and tars to 2.3? I guess I can try a recompile. Not much in life is simple. XFS used to be...now I have to *grumble, Fezerfigmumblemumble...* -l Hey...howz about porting xfs to Win32 in your spare time as well? :-) NT needs a real fs...sigh. Given the work it has taken to get to linux... Of course it might have helped if Rick hadn't taken a liking to Bill's posterior for a waste of 2 years. Of course, _now_ he sees the light... sigh. From owner-linux-xfs@oss.sgi.com Mon Dec 30 23:42:17 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 23:42:21 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV7gG3v003733 for ; Mon, 30 Dec 2002 23:42:17 -0800 Received: from localhost (localhost [127.0.0.1]) by tapu.f00f.org (Postfix) with ESMTP id D459C201CFF; Mon, 30 Dec 2002 23:47:21 -0800 (PST) Received: by tapu.f00f.org (Postfix, from userid 1000) id 54C68201CBC; Mon, 30 Dec 2002 23:47:21 -0800 (PST) Date: Mon, 30 Dec 2002 23:47:21 -0800 From: Chris Wedgwood To: LA Walsh Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump... Message-ID: <20021231074721.GA18584@tapu.f00f.org> References: <20021231033202.GA17409@tapu.f00f.org> <000001c2b095$0cc4e080$1403a8c0@sc.tlinx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c2b095$0cc4e080$1403a8c0@sc.tlinx.org> User-Agent: Mutt/1.4i X-No-Archive: Yes X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 2172 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Mon, Dec 30, 2002 at 10:22:52PM -0800, LA Walsh wrote: > Not a lot to go on, since when it died, it appears to have shutdown > the root file system. dmesg should (may?) have reported something useful did you see why you got the IO error? does a check of the media show anything? --cw From owner-linux-xfs@oss.sgi.com Mon Dec 30 23:44:17 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Mon, 30 Dec 2002 23:44:19 -0800 (PST) Received: from tapu.f00f.org (tapu.f00f.org [202.49.232.129]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBV7iH3v004141 for ; Mon, 30 Dec 2002 23:44:17 -0800 Received: from localhost (localhost [127.0.0.1]) by tapu.f00f.org (Postfix) with ESMTP id 68091201CBC; Mon, 30 Dec 2002 23:49:22 -0800 (PST) Received: by tapu.f00f.org (Postfix, from userid 1000) id DCEF5201CFE; Mon, 30 Dec 2002 23:49:21 -0800 (PST) Date: Mon, 30 Dec 2002 23:49:21 -0800 From: Chris Wedgwood To: LA Walsh Cc: linux-xfs@oss.sgi.com Subject: Re: xfsdump... Message-ID: <20021231074921.GB18584@tapu.f00f.org> References: <000001c2b095$0cc4e080$1403a8c0@sc.tlinx.org> <000301c2b09c$255c7c00$1403a8c0@sc.tlinx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000301c2b09c$255c7c00$1403a8c0@sc.tlinx.org> User-Agent: Mutt/1.4i X-No-Archive: Yes X-Virus-Scanned: by AMaViS new-20020517 X-archive-position: 2173 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cw@f00f.org Precedence: bulk X-list: linux-xfs On Mon, Dec 30, 2002 at 11:13:36PM -0800, LA Walsh wrote: > Hey...howz about porting xfs to Win32 in your spare time as well? > :-) off you go then :) > NT needs a real fs...sigh. for windows ntfs works good enough > Given the work it has taken to get to linux... ? > Of course it might have helped if Rick hadn't taken a liking to > Bill's posterior for a waste of 2 years. Of course, _now_ he sees > the light... sigh. try not to drink the paint thinners --cw From owner-linux-xfs@oss.sgi.com Tue Dec 31 04:52:47 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 04:52:54 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVCqk3v012608 for ; Tue, 31 Dec 2002 04:52:47 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBVD4Pkq020898 for ; Tue, 31 Dec 2002 07:04:25 -0600 Received: from poppy-e236.americas.sgi.com (poppy-e236.americas.sgi.com [128.162.236.207]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id GAA53606; Tue, 31 Dec 2002 06:57:46 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by poppy-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id GAA11687; Tue, 31 Dec 2002 06:57:46 -0600 (CST) Date: Tue, 31 Dec 2002 06:50:46 -0600 (CST) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Russell Cattelan cc: "Jeffrey E. Hundstad" , Subject: Re: linux-2.4.20-xfs CVS:20021230 In-Reply-To: <1041318750.55808.7.camel@lupo.thebarn.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-archive-position: 2174 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs On 31 Dec 2002, Russell Cattelan wrote: > Looks like eric missed something. > Just define XFS_MAX_ERR_LEVEL to 7 in debug.c for now. Argh... I swear, I compiled it before I checked it in! :) Checking in a fix now. -Eric From owner-linux-xfs@oss.sgi.com Tue Dec 31 04:59:34 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 04:59:40 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVCxX3v013113 for ; Tue, 31 Dec 2002 04:59:34 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBVDBCkq020960 for ; Tue, 31 Dec 2002 07:11:12 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id HAA26036 for ; Tue, 31 Dec 2002 07:04:33 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id HAA70166 for ; Tue, 31 Dec 2002 07:04:34 -0600 (CST) From: Eric Sandeen Received: by stout.americas.sgi.com (8.11.6/SGI-client-1.7) id gBVCvYs19964; Tue, 31 Dec 2002 06:57:34 -0600 Message-Id: <200212311257.gBVCvYs19964@stout.americas.sgi.com> Date: Tue, 31 Dec 2002 06:57:34 -0600 Subject: TAKE - Fix dyslexic definition of XFS_MAX_ERR_LEVEL X-archive-position: 2175 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Whoops. Fix dyslexic definition of XFS_MAX_ERR_LEVEL... Date: Tue Dec 31 05:03:50 PST 2002 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135847a linux/fs/xfs/support/debug.c - 1.13 From owner-linux-xfs@oss.sgi.com Tue Dec 31 05:02:04 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 05:02:06 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVD243v013545 for ; Tue, 31 Dec 2002 05:02:04 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBVDDhkq020976 for ; Tue, 31 Dec 2002 07:13:43 -0600 Received: from tulip-e236.americas.sgi.com (tulip-e236.americas.sgi.com [128.162.236.208]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id HAA14297; Tue, 31 Dec 2002 07:07:04 -0600 (CST) Received: from [192.168.1.100] (cf-vpn-sw-corp-64-61.corp.sgi.com [134.15.64.61]) by tulip-e236.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.8) with ESMTP id HAA11343; Tue, 31 Dec 2002 07:07:03 -0600 (CST) Subject: Re: mrlocks vs. rw_semaphores From: Stephen Lord To: Alexander Kabaev Cc: linux-xfs@oss.sgi.com In-Reply-To: <20021224114016.133029de.ak03@gte.com> References: <20021224114016.133029de.ak03@gte.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 (1.0.3-6) Date: 31 Dec 2002 07:01:01 -0600 Message-Id: <1041339663.1368.3.camel@localhost.localdomain> Mime-Version: 1.0 X-archive-position: 2176 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: lord@sgi.com Precedence: bulk X-list: linux-xfs On Tue, 2002-12-24 at 10:40, Alexander Kabaev wrote: > Looking through XFS change history, I noticed that several uses of mrlocks in > the tree have been replaced with Linux's native rw_semaphores. What was the > reason for this? Are rw_semaphores performing significantly better than > mrlocks, or is there a subtle difference in their semantics which make > rw_semaphores more suitable for the places they are used in now? > rw_semaphores are lighter weight than mrlocks, and suitable for use as a replacement for them in some cases. In other cases we use semantics not available with rw_semaphores, we have also found that if we add these semantics, we run into starvation problems with the locks. This is why mrlocks still exist in the linux code. Steve From owner-linux-xfs@oss.sgi.com Tue Dec 31 06:31:03 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 06:31:05 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVEV33v014552 for ; Tue, 31 Dec 2002 06:31:03 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBVCaBG8011759 for ; Tue, 31 Dec 2002 04:36:11 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id IAA30521 for ; Tue, 31 Dec 2002 08:36:03 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id IAA84317 for ; Tue, 31 Dec 2002 08:36:03 -0600 (CST) From: Eric Sandeen Received: by stout.americas.sgi.com (8.11.6/SGI-client-1.7) id gBVET3N21492; Tue, 31 Dec 2002 08:29:03 -0600 Message-Id: <200212311429.gBVET3N21492@stout.americas.sgi.com> Date: Tue, 31 Dec 2002 08:29:03 -0600 Subject: TAKE - Define XFS_MAX_FILE_OFFSET to MAX_LFS_FILESIZE X-archive-position: 2177 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Define XFS_MAX_FILE_OFFSET to MAX_LFS_FILESIZE, not our home-brewed limit. Date: Tue Dec 31 06:35:42 PST 2002 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135850a linux/fs/xfs/xfs_inode.h - 1.174 From owner-linux-xfs@oss.sgi.com Tue Dec 31 09:54:47 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 09:54:54 -0800 (PST) Received: from webserver (216-211-196-130.noviant.com [216.211.196.130] (may be forged)) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVHsi3v016868 for ; Tue, 31 Dec 2002 09:54:46 -0800 Received: from mail pickup service by webserver with Microsoft SMTPSVC; Tue, 31 Dec 2002 12:55:26 -0500 From: To: Subject: =?iso-8859-1?Q?call_china_6.2=A2_www.callez.com?= Date: Tue, 31 Dec 2002 12:55:25 -0500 MIME-Version: 1.0 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: X-OriginalArrivalTime: 31 Dec 2002 17:55:26.0156 (UTC) FILETIME=[CC5788C0:01C2B0F5] Content-Disposition: inline Content-Type: text/plain Content-Transfer-Encoding: 7bit Content-length: 40 X-archive-position: 2178 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: promotion@callez.com Precedence: bulk X-list: linux-xfs [[HTML alternate version deleted]] From owner-linux-xfs@oss.sgi.com Tue Dec 31 11:04:58 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 11:05:11 -0800 (PST) Received: from tolkor.sgi.com (tolkor.sgi.com [198.149.18.6]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVJ4v3v017670 for ; Tue, 31 Dec 2002 11:04:58 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by tolkor.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBVJGdkq026988 for ; Tue, 31 Dec 2002 13:16:39 -0600 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id NAA53687 for ; Tue, 31 Dec 2002 13:09:59 -0600 (CST) Received: from rose.americas.sgi.com (rose.americas.sgi.com [128.162.232.98]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id NAA69991 for ; Tue, 31 Dec 2002 13:09:59 -0600 (CST) Received: from rose.americas.sgi.com (localhost [127.0.0.1]) by rose.americas.sgi.com (8.12.6/8.12.5) with ESMTP id gBVJBmkx031804 for ; Tue, 31 Dec 2002 13:11:49 -0600 Received: (from cattelan@localhost) by rose.americas.sgi.com (8.12.6/8.12.6/Submit) id gBVJBmsq031802 for linux-xfs@oss.sgi.com; Tue, 31 Dec 2002 13:11:48 -0600 Date: Tue, 31 Dec 2002 13:11:48 -0600 From: Rusell Cattelan Message-Id: <200212311911.gBVJBmsq031802@rose.americas.sgi.com> Subject: TAKE - fix the err level stuff again :-/ X-archive-position: 2179 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: cattelan@rose.americas.sgi.com Precedence: bulk X-list: linux-xfs Fix the cmn_err stuff to mask the error level before it checks for max value Date: Tue Dec 31 11:09:32 PST 2002 Workarea: rose.americas.sgi.com:/usr/src/2.4.x-xfs/find The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135869a linux/fs/xfs/support/debug.c - 1.14 From owner-linux-xfs@oss.sgi.com Tue Dec 31 11:57:07 2002 Received: with ECARTIS (v1.0.0; list linux-xfs); Tue, 31 Dec 2002 11:57:13 -0800 (PST) Received: from rj.sgi.com (rj.SGI.COM [192.82.208.96]) by oss.sgi.com (8.12.5/8.12.5) with SMTP id gBVJv73v029701 for ; Tue, 31 Dec 2002 11:57:07 -0800 Received: from ledzep.americas.sgi.com (ledzep.americas.sgi.com [192.48.203.134]) by rj.sgi.com (8.12.2/8.12.2/linux-outbound_gateway-1.2) with ESMTP id gBVI2GG8027194 for ; Tue, 31 Dec 2002 10:02:16 -0800 Received: from daisy-e236.americas.sgi.com (daisy-e236.americas.sgi.com [128.162.236.214]) by ledzep.americas.sgi.com (SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id OAA64563 for ; Tue, 31 Dec 2002 14:02:08 -0600 (CST) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.232.50]) by daisy-e236.americas.sgi.com (SGI-8.9.3/SGI-server-1.8) with ESMTP id OAA17028 for ; Tue, 31 Dec 2002 14:02:08 -0600 (CST) From: Eric Sandeen Received: by stout.americas.sgi.com (8.11.6/SGI-client-1.7) id gBVJt6U28608; Tue, 31 Dec 2002 13:55:06 -0600 Message-Id: <200212311955.gBVJt6U28608@stout.americas.sgi.com> Date: Tue, 31 Dec 2002 13:55:06 -0600 Subject: TAKE - fix my max offset change... X-archive-position: 2180 X-ecartis-version: Ecartis v1.0.0 Sender: linux-xfs-bounce@oss.sgi.com Errors-to: linux-xfs-bounce@oss.sgi.com X-original-sender: sandeen@sgi.com Precedence: bulk X-list: linux-xfs Ok, I'll stop messing with your filesystem for a while. ;-) (Hint, when test-compiling changes, don't just build modules if the code you changed is not in a module!) #include pagemap.h for new max file offset macro Date: Tue Dec 31 12:01:01 PST 2002 Workarea: stout.americas.sgi.com:/localhome/src/sandeen/2.4.x-xfs/workarea-alwaysclean The following file(s) were checked into: bonnie.engr.sgi.com:/isms/slinx/2.4.x-xfs Modid: 2.4.x-xfs:slinx:135878a linux/fs/xfs/linux/xfs_linux.h - 1.97